+- [61] 3GPP TR 22.904: "Study on user centric identifiers and authentication".
+- [62] GSMA SGP.21: "RSP Architecture".
+- [63] GSMA SGP.01: "Embedded SIM Remote Provisioning Architecture".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [29] 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 [29].
+
+**3GPP SSO Authentication:** Authentication performed between an SSO-capable UE and 3GPP SSO Identity Provider using Operator-controlled credentials and without requiring user involvement.
+
+**3GPP SSO Identity Provider:** An entity that maintains Operator-controlled identity and credential information for a user, performs 3GPP SSO Authentication, and asserts the user's identity to a Data Application Provider.
+
+**3rd Party SSO Identity Provider:** An entity that maintains identity and credential information (that is not Operator-controlled) for a user, performs authentication, and asserts the user's identity to a Data Application Provider.
+
+**Attended Data Traffic:** Data traffic of which the user is aware he/she initiated, e.g. based on the screen/keypad lock being deactivated, length of time since the UE last received any input from the user, known type of application (e.g. an application monitoring a user's health – "mHealth" – which may need its data always treated as Attended Data Traffic.)
+
+**eCall:** A manually or automatically initiated emergency call (TS12 or IMS emergency call), from a vehicle, supplemented with a minimum set of emergency related data (MSD).
+
+**Data Application Provider:** An entity that offers data application services to users (e.g., over the public Internet). The data applications can be browser or non-browser based services.
+
+**Free-to-air (FTA) TV:** A TV service characterised by no content encryption and being made available at no additional cost to the end user.
+
+**Free-to-view (FTV) TV:** A TV service characterised by optional content encryption and being made available at no additional cost to the end user.
+
+**Gateway UE:** a UE, which acts as a gateway providing access to and from the 3GPP network for one or more non-3GPP devices that are connected to the gateway UE.
+
+**GERAN or UTRAN Sharing:** The sharing of GERAN or UTRAN among a number of operators.
+
+**Hosting E-UTRAN/NG-RAN Operator:** The Operator that has operational control of a Shared E-UTRAN and/or NG-RAN. With regard to management of the Shared E-UTRAN the Hosting E-UTRAN/NG-RAN Operator is a Master Operator [64].
+
+**Hosting RAN:** The Shared RAN that is owned or controlled by the Hosting RAN Operator.
+
+**Hosting RAN Operator:** The Operator that has operational control of a Shared NG-RAN, Shared E-UTRAN, Shared GERAN or UTRAN.
+
+**IMS Centralized Services:** The provision of communication services wherein services and service control are based on IMS mechanisms and enablers, and support is provided for a diversity of access networks (including CS domain and IP based, wireless and wireline), and for service continuity between access networks.
+
+**MSD:** The Minimum Set of Data [46] forming the data component of an eCall sent from a vehicle to a Public Safety Answering Point or other designated emergency call centre. The MSD has a maximum size of 140 bytes and includes, for example, vehicle identity, location information and time-stamp.
+
+**NG-RAN:** A radio access network connecting to the 5G core network which uses NR, E-UTRA, or both.
+
+**Participating Operator:** Authorized operator that is using Shared NG-RAN, Shared E-UTRAN, Shared GERAN or UTRAN resources provided by a Hosting RAN Operator.
+
+**RAN user plane congestion:** The situation where the demand for RAN resources to transfer user data exceeds the available RAN capacity to deliver the user data for a significant period of time in the order of few seconds or longer.
+
+**(S)Gi-LAN:** The network infrastructure connecting to 3GPP network over the SGi or Gi reference point that provides various IP-based services (e.g. NAT, antimalware, parental control, DDoS protection, video optimization).
+
+**Shared E-UTRAN:** E-UTRAN that is shared among a number of operators.
+
+**Shared RAN:** GERAN, UTRAN, E-UTRAN or NG-RAN that is shared among a number of operators.
+
+**Shared GERAN or UTRAN:** GERAN or UTRAN that is shared among a number of operators.
+
+**Shared NG-RAN:** NG-RAN that is shared among a number of operators.
+
+**SSO Provider:** An entity that provides SSO Service. The SSO Provider enables a user to authenticate to an IdP and thereby to have their identity asserted to a DAP. Each data application, whether provided by different DAPs or the same DAP, may have its own policy regarding authentication. In the 3GPP SSO Service, the SSO Provider is the 3GPP Operator.
+
+**SSO Service:** A service in which the user of a data application is authenticated once, and as a result of that authentication is provided with seamless and transparent access to multiple data applications offered by one or more Data Application Providers.
+
+**SSO Local User Authentication:** Authentication performed by the UE that establishes the presence of the registered user of the data application by requiring input which only the registered user would be able to provide.
+
+**Subscribed TV service:** A TV service which is characterised by requiring a subscription (to content owner, content provider, or MNO) in order to access the service.
+
+**Unattended Data Traffic:** Data traffic of which the user is unaware he/she initiated, e.g. based on the screen/keypad lock being activated, length of time since the UE last received any input from the user, known type of app (e.g. an application monitoring a user's health – "mHealth" – may need its data never treated as Unattended Data Traffic.)
+
+**User:** As defined in TR 21.905 [29]: An entity, not part of the 3GPP System, which uses 3GPP System services. Example: a person using a 3GPP System mobile station as a portable telephone.
+
+Additional examples for a user in the context of this TS: a non-3GPP device connected to the 3GPP system via a gateway, or an application running on a UE.
+
+**User Identity:** information representing a user in a specific context. A user can have several user identities, e.g. a User Identity in the context of his profession, or a private User Identity for some aspects of private life.
+
+**User Identifier:** a piece of information used to identify one specific User Identity in one or more systems.
+
+**User Identity Profile:** A collection of information associated with the User Identities of a user.
+
+**MUSIM UE:** An ME with multiple USIMs.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [29] 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 [29].
+
+| | |
+|-----|--------------------------------------------------------------------------|
+| DAP | Data Application Provider |
+| IdP | Identity Provider |
+| IVS | In Vehicle System (eCall terminal and associated sub-systems in vehicle) |
+| ME | Mobile Equipment |
+| OTT | Over The Top |
+| PC | Personal Computer |
+| SSO | Single Sign-On |
+
+# --- 4 General
+
+## 4.1 Aims of 3GPP specifications
+
+It shall be capable of delivering audio, text, video and graphics direct to people and provide them with access to the next generation of information-based services. It moves mobile and personal communications forward from existing systems, delivering mass market low-cost digital telecommunication and IP-based multimedia services.
+
+The aims are:
+
+- to enable users to access a wide range of telecommunications services, including many that are today undefined as well as multi-media and high data rates.
+- to facilitate the provision of a high quality of service (particularly speech quality) similar to that provided by fixed networks;
+- to facilitate the provision of small, easy to use, low cost terminals with long talk time and long standby operation;
+- to provide an efficient means of using network resources (particularly radio spectrum).
+
+## 4.2 Standardisation of Service Capabilities
+
+Existing systems have traditionally standardised the complete sets of teleservices, applications and supplementary services which they provide. As a consequence, substantial efforts are often required to introduce new services or simply to modify the existing one (customisation). This makes it more difficult for operators to differentiate their services. At the same time however, this may reduce the complexity of providing a service across different operators' networks.
+
+3GPP shall therefore preferentially standardise service capabilities. In circumstances where the service is meant to be used across different operators' networks, hence a common specification set is of paramount importance, the service should be standardised to a level of detail sufficient to ensure interoperability and interworking across different operators' networks. Service capabilities consist of bearers defined by QoS parameters and the mechanisms needed to realise services. These mechanisms include the functionality provided by various network elements, the communication between them and the storage of associated data. This TS provides a conceptual description of a service architecture and architecture requirements which aim to provide service capabilities. It is intended that these standardised capabilities should provide a defined platform which will enable the support of speech, video, multi-media, messaging, data, teleservices, user applications and supplementary services and enable the market for services to be determined by users and home environments.
+
+### 4.2.1 Provision of service capabilities in shared networks
+
+The provision of services and service capabilities that is possible to offer in a network shall not be restricted by the existence of the network sharing. It shall be possible for a core network operator to differentiate its service offering from other core network operators within the shared network.
+
+It shall be possible to control the access to service capabilities offered by a shared network according to the core network operator the user is subscribed to.
+
+## 4.3 Efficient Use of Network Resources
+
+### 4.3.1 Network Traffic Patterns
+
+Service capabilities shall take account of the discontinuous and asymmetric nature of most teleservices, multimedia services and user applications and consider the overheads and signalling surge caused by frequent transmissions of small amount of data by mobile data application, in order to make efficient use of network resources (particularly radio resources).
+
+### 4.3.2 Mass Simultaneous Registration
+
+When a large number of subscribers enter in a registration area in which they have not registered, the core and radio access network shall be able to provide a capability to optimize the mass simultaneous registration traffic at a given instance of time. The core and radio access network shall be able to keep providing the service (e.g. mobile originated and mobile terminated services) without interruption for those subscribers who are originally in the cell which receive the mass simultaneous registration traffic.
+
+### 4.3.3 Radio Interface
+
+Service capabilities shall be provided in a wide range of radio operating environments (where a radio environment is characterised in terms of propagation environment, mobile equipment relative speeds and traffic characteristics). Although 3GPP aims to minimise the number of radio interfaces and to maximise commonality between them, it may utilise several radio interfaces, each optimised for different environments. Each radio interface may provide differing service capabilities. 3GPP specifications include UTRA(N) radio interface supporting two modes (TDD and FDD), an Evolved UTRA(N) radio interface and GERAN radio interface. Additionally, it may be possible to connect to the 3GPP system using radio interfaces and fixed access technologies specified outside of 3GPP.
+
+3GPP specifications shall provide a mechanism which will enable a piece of user equipment (UE) to adapt to different radio interfaces as necessary and to determine the service capabilities available. The specifications shall also provide a mechanism which will enable a UE to select radio interfaces capable of providing appropriate service capabilities and support mobility between multiple radio interfaces.
+
+### 4.3.4 Real-time Resource Usage
+
+To enable network operators to render services efficiently, dimension their networks and set tariffs that more accurately reflect radio resource usage, real time information on resource usage is needed. When requested, it shall be possible for the serving cell type (e.g. RAT), cell ID / UTRAN Service Area Identity and cell / Service Area capability usage (e.g. HSDPA, E-DCH) information to be made available to the core network. Cell / Service Area capability usage information may include, for example, user(s) identity, start and finish time of data transfer, up-link and down-link data rates, volumes of data and other statistical information.
+
+### 4.3.5 Selected IP Traffic Offload (SIPTO) for PS Domain only
+
+#### 4.3.5.1 Common Requirements for SIPTO in the Mobile Operator Network and SIPTO at the Local Network
+
+The 3GPP system shall be able to offload selected traffic (e.g. internet) towards a defined IP network close to the UE's point of attachment to the access network.
+
+The following requirements apply to Selected IP Traffic Offload:
+
+- The mobile operator may enable/disable Selected IP Traffic Offload on a per UE per defined IP network basis (e.g. based on tariff, subscription type etc.).
+- It shall be possible for IP traffic of a UE associated with a particular defined IP network to be offloaded while IP traffic of that same UE associated with other defined IP network(s) is not offloaded.
+- It shall be possible to perform Selected IP Traffic Offload for pre-Release 10 UEs.
+- Offloading selected IP traffic for a UE shall not affect services running in parallel for the same UE.
+- The mobile operator shall be able to collect signalling performance measurements (e.g. session connection/disconnection, etc) related to Selected IP Traffic Offload for each user.
+- Selected IP Traffic Offload shall not compromise the security of the mobile operator's network.
+- Service Continuity of IP data session(s) for Selected IP Traffic Offload may be supported during the following mobility events:
+ - mobility between the macro network and H(e)NBs; and
+
+- mobility between H(e)NBs.
+
+During both these mobility events, based on home mobile operator policies, the impact of mobility events as perceived by the user shall be reduced by minimising any interruption to the data flow.
+
+- It shall be possible for the HPLMN to provide the VPLMN with the following information for a particular user:
+ - An indication of whether the user's IP traffic is permitted to be subjected to Selected IP Traffic Offload in the visited network;
+ - The defined IP network(s) for which Selected IP Traffic Offload is permitted.
+
+Requirements specific to SIPTO at the local residential/enterprise IP network can be found in section 5.9 in [48].
+
+Some types of services (e.g. streaming services, VOIP, VPN, HTTPS-Based Services) cannot tolerate a change of IP address of the UE without disruption of the service.
+
+SIPTO can be performed with or without coordination between the UE and the network. The following requirements apply to coordinated SIPTO:
+
+- The 3GPP system shall be able to support multiple connections that are associated with the same defined IP network where each connection may or may not support IP address preservation.
+- The 3GPP system shall be able to determine if an IP flow requires IP address preservation or not. Based on this determination, the 3GPP network shall be able to offload selected IP traffic in coordinated manner between UE and the network, in order to minimize service disruption.
+- The 3GPP system shall be able to detect when a connection becomes suboptimal and decide when to establish a new optimal connection to the same defined IP network or use an existing connection.
+
+Note 1: The definition of optimal and suboptimal can be based on a number of implementation criteria like geography, topology and load balancing etc.
+
+- The 3GPP system shall minimize the number of connections of a UE without disrupting the UE's services, e.g. to ensure economical use of network resources.
+- The 3GPP system shall be able to ensure that the actual average aggregate bit rate for IP flows of packet data network connections associated with the same packet data network does not significantly exceed the subscribed aggregate maximum bit rate for this packet data network when two connections are used with the same defined IP network.
+
+Note 2: Requirements for Coordinated SIPTO do not apply to IMS.
+
+#### 4.3.5.2 Requirements for SIPTO in the Mobile Operator Network
+
+The following requirements apply to Selected IP Traffic Offload in the mobile operator network:
+
+- The mobile operator shall be able to enable/disable Selected IP Traffic Offload for certain parts of the network.
+- Selected IP Traffic Offload shall not compromise integrity and confidentiality of offloaded traffic.
+- The mobile operator shall be able to collect statistics for the offloaded traffic for each user.
+- The network shall be able to perform Selected IP Traffic Offload without any user interaction based on mobile operator policies.
+- Service Continuity of IP data session(s) within the mobile operator network shall be supported for Selected IP Traffic Offload. Based on home mobile operator policies, the impact of mobility events within the macro network as perceived by the user shall be reduced by either:
+ - minimising any interruption to the data flow; or
+ - preventing interruption to the data flow e.g. for voice services.
+- Service Continuity of IP data session(s) for Selected IP Traffic Offload may be supported during the following mobility events:
+
+- mobility between the macro network and H(e)NBs; and
+- mobility between H(e)NBs.
+
+During both these mobility events, based on home mobile operator policies, the impact of mobility events as perceived by the user shall be reduced by preventing interruption to the data flow e.g. for voice services.
+
+### 4.3.6 Paging policy selection for LTE
+
+The 3GPP core network shall be able to use these additional criteria for selecting a paging policy:
+
+- mobility information on the UE (e.g. the UE is stationary, or moving only in a specified area)
+- application characteristics that are known and trusted at the serving network (e.g. communication pattern, expected QoS (e.g. latency, reliability), and priority)
+- likely location of the UE within the paging area
+
+## 4.4 Compatibility with Global Standards
+
+3GPP specifications aim to be compatible with IMT-2000 and to provide global terminal mobility (roaming), enabling the user to take his/her terminal to different regions of the world and to be provided with services. It is probable that different regions of the world will adopt different radio interface technologies. IMT-2000, as a global standard, should therefore enable a IMT-2000 terminal to determine the radio interface technology and the radio interface standard used in a region. Global terminal roaming also requires the global standardisation of service capabilities. As far as possible the method of indication of the radio interface standard and available service capabilities shall be aligned with IMT-2000.
+
+3GPP specifications shall enable users to access the services provided by their home environment in the same way via any serving network provided the necessary service capabilities are available in the serving network.
+
+The 3GPP specifications will be available for the partner organisations to adopt as their regional standards. For example in Europe, ETSI may adopt them as standards for both GSM and UMTS.
+
+## 4.5 Void
+
+## 4.6 Functionality of Serving Network and Home Environment
+
+The following functionality shall be the responsibility of the home environment:
+
+- User Authentication.
+- SIM/USIM Issue.
+- Billing.
+- User Profile/VHE Management.
+
+The following functionality shall be the responsibility of the serving network:
+
+- Radio or other means of access.
+- Transport and signalling.
+
+The following functionality may be the responsibility of either the serving network, the home environment or an appropriate combination of both
+
+- Service Control.
+- QoS negotiation.
+- Mobility management, including roaming.
+
+- Automatic establishment of roaming agreements.
+
+## 4.7 PLMN Architecture
+
+The network is logically divided into a radio access network and a core network, connected via an open interface. From a functional point of view the core network is divided into a Packet Switched CN Domain, IP Multimedia (IM) CN subsystem [27] and a Circuit Switched CN Domain. IM CN subsystem utilises PS CN domain bearer services.
+
+CS CN domain supports bearer independent transport. There is no difference in service offering or UE functionality due to different transport.
+
+A PS only 3GPP core network is possible as defined within the specification for the Evolved Packet System (EPS) [42].
+
+For further information see 3GPP TS 23.221 [20].
+
+## 4.8 Interworking Between PLMN and Wireless LANs
+
+Aspects related to interworking between PLMN and WLAN are captured in TS 22.234 [35].
+
+## 4.9 Network Sharing
+
+Network sharing shall be transparent to the user.
+
+The specifications shall support both the sharing of:
+
+- (i) radio access network only;
+- (ii) radio access network and core network entities connected to radio access network
+
+NOTE: In a normal deployment scenario only one or the other option will be implemented.
+
+It shall be possible to support different mobility management rules, service capabilities and access rights as a function of the home PLMN of the subscribers.
+
+## 4.10 The Evolved Packet System
+
+Evolved Packet System is an evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs. The Evolved Packet System comprises the Evolved Packet Core together with the evolved radio access network (E-UTRA and E-UTRAN). The service requirements for the Evolved Packet System are specified in TS22.278 [42].
+
+## 4.11 User Data Convergence
+
+### 4.11.1 Introduction
+
+The UDC concept [45] supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends. And such unique repository shall be possible to be shared among different PLMNs that have trusted relationships.
+
+Network elements and functionalities should be designed to access profile data remotely and without storing them permanently locally, i.e. the front-ends shall work in a subscriber data-less configuration.
+
+In some cases, services may depend on user data scattered over UDC and other network elements. UDC may support the ability to access necessary network elements to fetch user data on behalf of these services, while minimizing impacts on existing Network Elements in which the data is located.
+
+Applications can subscribe to specific events which will likely occur on specific user data, and those should be notified when those events do appear. The events can be changes on existing user data, addition of user data, and so on.
+
+Third-party applications and non-trusted network elements should only be able to access the user data after proper authentication and authorization taking into account security and privacy requirements, i.e. it should be possible to present different views on the data to the parties which require access, dependent on the authorization. UDC concept is backwards compatible with 3GPP systems, i.e. it does not have an impact on traffic mechanisms, reference points and protocols of existing network elements.
+
+The UDC concept preserves user authentication and authorization of services across domains, ensuring secured users' access to network.
+
+### 4.11.2 Management of user data
+
+Due to the logical centralization of user data, it is necessary for UDC to support the provisioning of the user data, that is, user data manipulation like creation, deletion, reading, modification and other operations. Provisioning shall be possible via an external system, self-care or dynamically via applications offering e.g. user service configuration facilities.
+
+Operations carried out in the framework of UDC shall support the ACID (Atomicity, Consistency, Isolation, and Durability) characteristics.
+
+### 4.11.3 User Data Modelling
+
+User Data Modelling refers to the different models that apply to user data convergence: Information Models and Data Models.
+
+An Information Model denotes an abstract, formal representation of entity types, including their properties and relationships, the operations (e.g. read, write...) that can be performed on them, and related rules and constraints. In the information model, entities might have network topology relationship with each other.
+
+In order to accommodate multiple applications and services, existing and new ones, a common baseline information model shall be developed and shall, at minimum, clearly distinguish a number of concepts as entity types:
+
+- Subscriber with relation to several users (e.g. a company and its employees),
+- A user attached to different subscriptions (e.g. for a private and a professional service usage)
+- A user using multiple devices (e.g. mobiles or fixed)
+- Grouping of users to certain categories
+- A particular user as member of a certain group
+- Service providers' services provided by network operators
+- Enterprise services provided by network operators
+
+The baseline information model shall be future proof. It shall not be tied to any specific implementation of the data base or its interfaces. It shall provide flexibility (in its data structure and content), extensibility and multi-application approach.
+
+By extensible, it shall be understood that new applications and/or new service profiles can be added by the operator, if necessary. The flexibility shall permit new data for existing applications to be introduced, or modified.
+
+Data Models are practical implementations of the information model, e.g. Tree-like modelling. The common information model shall allow deriving one or more data models. A reference data model shall be standardized for the message exchange over Ud interface [50], in order to enable multivendor interoperability.
+
+Each application shall only interface the UDC for the data it is dealing with, and not be impacted by other data that UDC stores for other applications. It corresponds to the concept of a data view specific to a given application.
+
+An application can allow access by other applications to data for which it is responsible. This can be done under certain constraint customized by operators.
+
+Access to the UDC data shall be independent of the structure of the data models, i.e. the changes in the data models shall not affect the interface.
+
+# --- 5 Evolution
+
+## 5.1 Support of 2G services
+
+The 3GPP specifications shall be capable of supporting existing 2G services in a manner which is transparent to the users of these services.
+
+## 5.2 Provision and evolution of services
+
+Since a phased approach has been adopted, the same general service principles shall apply to each phase. Support of services from an end user perspective is understood to be an important driver for established mobile users to stay with their existing operator while taking the new services into use. It is therefore important to enable operators to offer continued support of legacy services in future releases. Previous release services shall as a principle also be supported in the following releases.
+
+Networks shall be capable of providing a specified core set of capabilities.
+
+The core set of capabilities should permit home environment to offer a range of distinctive services including those which cannot be implemented on systems based on previous release specifications.
+
+It shall be possible for the home environment to develop services with full roaming capability.
+
+The radio interface should not unnecessarily restrict the development of new services (within physical limitations).
+
+The standard shall provide a mechanism which allows a terminal to be easily upgraded so that it can access new services which are within the physical limitations of the terminal.
+
+# 6 Classification of services
+
+In the CS CN domain, the basic services are divided into circuit teleservices (3GPP TS 22.003 [14]) and bearer services (3GPP TS 22.002 [21]) and they can utilise standardised supplementary services (3GPP TS 22.004 [5]).
+
+The PS CN Domain provides IP bearer services. SMS, USSD and UUS can also be considered as bearer services for some applications.
+
+IP multimedia services are the IP based session related services, including voice communications. IP multimedia sessions use IP bearer services provided by the PS CN Domain.
+
+Value added non-call related services include a large variety of different operator specific services/applications. They are usually not specified by 3GPP. The services can be based on fully proprietary protocols or standardised protocols outside 3GPP.
+
+In order to create or modify the above services (both call and non-call related services) operators may utilise toolkits standardised by 3GPP (such as CAMEL or LCS) or external solutions (e.g. Internet mechanisms). Pre-paid is an example of an application created with toolkits that may apply to all of the above services categories.
+
+
+
+The diagram illustrates the classification of services into different categories and their relationship to toolkits. It is structured as follows:
+
+- Supplementary services (22.004)**: A box at the top right, with a line connecting it to the **Circuit teleservices (22.003)** box below it.
+- Circuit teleservices (22.003)**: A box containing the sub-services: **Telephony**, **FAX**, and **SMS**.
+- Circuit Bearer services (22.002)**: A box at the bottom right, positioned below the Circuit teleservices box.
+- Other Bearer services**: A box at the bottom center, containing **SMS, UUS, USSD**.
+- IP bearer services**: A large box at the bottom left, spanning under the IP multimedia and Value added non-call related services boxes.
+- IP multimedia services (SIP)**: A box on the left, containing examples: **(e.g. telephony, chat, whiteboards)**.
+- Value added non-call related services**: A box in the center, containing examples: **(e.g. eMail, MMS, WWW, News, etc..)**.
+- Toolkits:**: A large box on the far right, containing a list of toolkits: **CAMEL**, **MXE**, **(U)SAT**, **ASP**, **LCS**, **"Internet tools"**, and **etc...**
+
+Figure 1: Service classification diagram showing the hierarchy of services in a telecommunications network.
+
+Figure 1: Service classification
+
+# --- 7 Principles for new service capabilities
+
+## 7.1 General
+
+3GPP specifications shall enable the user of a single terminal to establish and maintain several connections simultaneously. It shall efficiently cater for applications which have variable requirements relating to specific QoS parameters (e.g. throughput) whilst meeting other QoS targets. It shall also cater for applications which are able to take adapt to a range of variations in QoS.
+
+## 7.2 Multimedia
+
+3GPP specifications shall support development of multimedia services and provide the necessary capabilities.
+
+Multimedia services combine two or more media components (e.g. voice, audio, data, video, pictures, text) within one call. A multimedia service may involve several parties and connections (different parties may provide different media components) and therefore flexibility is required in order to add and delete both resources and parties.
+
+Multimedia services are typically classified as interactive or distribution services.
+
+Interactive services are typically subdivided into conversational, messaging and retrieval services:
+
+Conversational services are real time (no store and forward), usually bi-directional where low end to end delays ( $< 100$ ms) and a high degree of synchronisation between media components (implying low delay variation) are required. Video telephony and video conferencing are typical conversational services."
+
+Messaging services offer user to user communication via store and forward units (mailbox or message handling devices). Messaging services might typically provide combined voice and text, audio and high-resolution images.
+
+Retrieval services enable a user to retrieve information stored in one or many information centres. The start at which an information sequence is sent by an information centre to the user is under control of the user. Each information centre accessed may provide a different media component, e.g. high-resolution images, audio and general archival information.
+
+Distribution services are typically subdivided into those providing user presentation control and those without user presentation control.
+
+Distribution services without user control are broadcast services where information is supplied by a central source and where the user can access the flow of information without any ability to control the start or order of presentation e.g. television or audio broadcast services.
+
+Distribution services with user control are broadcast services where information is broadcast as a repetitive sequence and the ability to access sequence numbering allocated to frames of information enables the user (or the user's terminal) to control the start and order of presentation of information.
+
+### 7.2.1 Circuit Switched (CS) multimedia calls
+
+CS multimedia call is a Bearer Service which utilises Synchronous Transparent Data service. The following basic requirements shall be supported for CS multimedia calls [24]:
+
+- CS multimedia call shall be based on a 3GPP specific subset of H.324M.
+- All call scenarios shall be supported, i.e. Mobile Originating and Mobile Terminating call against Mobile, ISDN and PSTN call party.
+- Single and multiple numbering schemes shall be supported.
+- Fallback to speech (TS 11 [14]) shall be supported from 3.1kHz Ext. PLMN multimedia bearer, i.e. if setup of the multimedia call fails the call will be set up as a speech call.
+
+- Service change and fallback shall be supported for UDI/RDI multimedia bearer and speech, to allow fallback to a less preferred service if the preferred service is unsupported, and to change the service between speech and multimedia during the call.
+- In the case where a CS multimedia call includes speech (e.g. video call) then the following requirements apply:
+ - A user shall be able to change between a speech and CS multimedia call, when desired.
+ - When the CS multimedia call is no longer supported, for example due to degraded coverage conditions (including UTRAN to GERAN only transitions), service change shall occur automatically from a CS multimedia call to speech.
+ - When a CS multimedia call can be supported, for example due to improved coverage conditions (including GERAN only to UTRAN or UTRAN/GERAN transitions), service change back to the CS multimedia call may be initiated by the network.
+ - Other services than CS multimedia call may exist which utilise the Synchronous Transparent Data service. Service transition to/from speech described for CS multimedia call in this clause shall only apply to CS multimedia call and not Synchronous Transparent Data services in general.
+- Different bitrates as specified at 3GPP TS 22.002 [21] shall be supported.
+- Supplementary services apply to multimedia calls as for Synchronous Transparent Data service according to 3GPP TS 22.004[5].
+- When accepting a multimedia call, the user shall be able to request a service change to speech before the call is answered, such that the multimedia path is never actually connected through to the user's phone.
+- The user shall be able to deny a service change to multimedia during the call.
+
+### 7.2.2 IP multimedia (IM) sessions
+
+IP multimedia services are not the evolution of the circuit switched services but represent a new category of services, mobile terminals, services capabilities, and user expectations. Any new multimedia service, which may have a similar name or functionality to a comparable standardised service, does not necessarily have to have the same look and feel from the user's perspective of the standardised service. Voice communications (IP telephony) is one example of real-time service that would be provided as an IP multimedia application.
+
+The following basic requirements are supported for IP multimedia [27]:
+
+- IP multimedia session control shall be based on SIP [28].
+- All session scenarios shall be supported; i.e. Mobile Originating and Mobile Terminating sessions against Internet/Intranet, CS or IM Mobile, ISDN, PSTN call party.
+- MSISDN and SIP URL numbering and addressing schemes shall be supported.
+- IP multimedia applications shall as a principle, not be standardised, allowing service provider specific variations.
+
+### 7.2.3 Multimedia Messaging Service (MMS)
+
+The following basic requirements are supported for MMS:
+
+- Store-and-forward multimedia messaging service with mobile and non-mobile users [25].
+- MMS shall be capable of supporting integration of different types of messaging (e.g. fax, SMS, Multimedia, voicemail, e-mail etc.) in a consistent manner.
+- Streamed and batch delivery for both message download from the network to the terminal, and messages upload from the terminal to the network.
+
+### 7.2.4 Real-Time Text Conversation
+
+Real-Time Text (RTT) conversation is a service enabled in 3GPP networks by the Global Text Telephony ( GTT ) [26].
+
+- GTT enables real time, character by character, text conversation to be included in any conversational service, Circuit Switched as well as IP based.
+- It is possible to use the text component in a session together with other media components, especially video and voice.
+- Interworking with existing text telephony in PSTN as well as emerging forms of standardised text conversation in all networks is within the scope of this feature.
+- The text media component can be included initially in the session, or added at any stage during the session.
+- The text component is intended for human input and reading, and therefore supports human capabilities in text input speed. The character set support is suitable for the languages the users communicate in.
+- GTT specifies limited interoperation with Multimedia Messaging Services including a possibility to divert to messaging in case of call failure and sharing user interface equipment and external UE interfaces.
+
+### 7.2.5 Packet Switched Streaming Service
+
+The following basic requirements are to be supported for streaming:
+
+- The streaming service uses a client / server model which is transparent to the PLMN. The client controls the initiation and execution of the service.
+- The streaming service [30] shall use existing standards (codecs and protocols [31]) where these are available.
+- The streaming service utilises the PS Domain with the QoS requirements as specified in 3GPP TS 22.105 [1].
+
+## 7.3 Service Management Requirements
+
+3GPP specifications shall include standardised protocols enabling service management. It shall enable control, creation and subscription of service capabilities and services, and the management of user profiles.
+
+## 7.4 Automatic Device Detection
+
+The home environment should be automatically notified when a user, identified by a SIM/USIM, has changed ME and should be informed of the identity of the new ME. This should be applicable to any ME. It should also be possible to achieve Automatic Device Detection for users using any SIM/USIM.
+
+- NOTE: The purpose of this is to enable an automatic configuration of terminals by the operator for specific applications/services if so needed. The procedure for such an automatic configuration need not to be standardized by 3GPP.
+
+The notification that a user has changed ME shall be given as early as possible.
+
+# 8 Service architecture
+
+In order to provide standardisation of service capabilities a service architecture shown by Figure 2 is envisaged
+
+
+
+```
+
+graph TD
+ subgraph TopLevel [ ]
+ direction TB
+ MMI[MMI]
+ UIM[UIM]
+ SS[Suppl. Service]
+ TMSA[Teleservice/
+Multimedia service/
+Application]
+ end
+ TopLevel --- SP[Service Platform]
+ SP --- MC[ ]
+ subgraph MC [ ]
+ direction TB
+ MM[Mobility Man.]
+ CC[Call Control]
+ BC[Bearer Control]
+ end
+ MC --- WS[ ]
+ subgraph WS [ ]
+ direction TB
+ WS1[Wired Subnetwork]
+ WS2[Wireless Subnetwork]
+ end
+ style TopLevel fill:none,stroke:none
+ style MC fill:none,stroke:none
+ style WS fill:none,stroke:none
+
+```
+
+The diagram illustrates the Service Architecture hierarchy. At the top, four user-facing components (MMI, UIM, Suppl. Service, and Teleservice/Multimedia service/Application) are connected to a central 'Service Platform'. Below the Service Platform, three functional blocks (Mobility Man., Call Control, and Bearer Control) are connected. These three blocks are then connected to a combined 'Wired Subnetwork' and 'Wireless Subnetwork' at the bottom.
+
+Figure 2: Service Architecture diagram showing the hierarchy from user interfaces down to subnetworks.
+
+Figure 2: Service Architecture
+
+**Figure 2: Service Architecture**
+
+A number of bearers shall be provided that can differ in flexibility and offer different capabilities. Bearers may be characterised by parameters such as "throughput", "delay tolerance", "maximum bit error rate", "symmetry" etc. These bearers enable information to be transferred appropriate to the provision of teleservices, multimedia services and end user applications generally, via subnetworks which typically provide different specified qualities of service.
+
+The assignment and release of bearers is provided by the bearer control function. Provision should be made for several bearers to be associated with a call and for bearers to be added to a call and/or to be released from a call following call establishment. The bearers should be independent of radio environments, radio interface technology and fixed wire transmission systems.
+
+Adaptation/Interworking functions are required in order to take account of the differences between the bearers used for the provision of a teleservice/multimedia service/application in the fixed network and the bearers.
+
+Adaptation/Interworking functions are required which take account of the discontinuous and/or asymmetrical nature of most teleservices/multimedia services/applications.
+
+The service platform shall provide interfaces (to serving networks and home environments) appropriate to the support, creation and control of supplementary services, teleservices, multimedia services and user applications. The service platform will also provide interfaces enabling subscribers to control supplementary services, teleservices, multimedia services and user applications.
+
+Supplementary service provision and control will be independent of radio operating environment, radio interface technology and fixed wire transmission systems.
+
+As far as possible, the service platform is required to enable new supplementary services, teleservices, multimedia services and/or end user applications to be supported at minimum cost, with minimum disruption of service and within the shortest possible time.
+
+# --- 9 Quality of Service (QoS)
+
+The Quality of Service (QoS) parameters should be identified together with appropriate parameter values which set targets to be reached when designing 3GPP specifications, and which also will serve as guidelines for network design and service provision.
+
+The QoS for call set-up time, as an example, can be defined in terms of a mean value and as a percentage of cases which should not exceed a certain time limit. Further information can be found in 3GPP TS 22.105 [1].
+
+The performance requirements for the All-IP Network can be found in 3GPP TS 22.278 [42].
+
+For UE initiated QoS control OMA device management shall be the primary method for provisioning QoS parameters.
+
+# 10 Emergency Calls
+
+## 10.1 General requirements
+
+It shall be possible to establish an emergency speech call or GTT [26] call (subject to national requirements). The term 'Emergency call' henceforth refers to speech calls, and GTT Emergency calls if applicable. The term "other media" henceforth refers to media other than speech and GTT. Support of other media types during an emergency call when the IM CN subsystem is used is referred to as 'IMS Multimedia Emergency Session' (MES) and is specified in subclause 10.4.2. Emergency calls will be routed to the emergency services in accordance with national regulations for where the subscriber is located. This may be based upon one or more default emergency call numbers stored in the ME. It shall be allowed to establish an emergency call without the need to dial a dedicated number to avoid the mis-connection in roaming case, such as menu, by use of a 'red button', or a linkage to a car air bag control. Emergency calls shall be supported by the UE without a SIM/USIM/ISIM being present. No other type shall be accepted without a SIM/USIM/ISIM than emergency calls and subject to operator policy and regional regulations, restricted local operator service access.
+
+Emergency calls shall be supported by UEs that are subject to service restrictions, e.g. for UEs camping on a cell in a forbidden PLMN or in a forbidden LA (see 3GPP TS 22.011 [11]), or on a CSG cell without the subscriber being a member of that CSG (see 3GPP TS 22.220 [48]). Such emergency calls shall be accepted by the network if required by local regulation.
+
+The Emergency service is required only if the UE supports voice.
+
+Note 1: It will be left to the national authorities to decide whether the network accepts emergency calls without the SIM/USIM/ISIM.
+
+It shall be possible to initiate emergency calls to different emergency call centres, depending on the type of emergency. The following types of emergency calls shall be possible:
+
+- Police
+- Ambulance
+- Fire Brigade
+- Marine Guard
+- Mountain Rescue
+- Manually Initiated eCall (MIEC)
+- Automatically Initiated eCall (AIEC)
+- Spare
+
+When a SIM/USIM is present, subscriber specific emergency call set-up MMI shall be provided. The Home Environment operator shall specify preferred emergency call numbers (e.g. 999 for UK citizens or 110, 118 and 119 for Japanese citizens). These emergency call numbers shall be stored in the SIM/USIM and the ME shall read this and use any entry of these digits to set up an emergency call. It shall be possible to store more than one instance of this field.
+
+Note 2: Release '98 and earlier SIM cards have the capability to store additional emergency call numbers. However in many cases this has not been used.
+
+It shall be possible to tie any emergency call number to any single emergency call type or to any combination of emergency call types. The association between emergency call numbers and emergency call type shall be able to be programmed by the Home Environment operator into the SIM/USIM.
+
+Example:
+
+- 19 Police (Albania)
+- 100 Police and Fire Brigade (Greek cities)
+
+| | |
+|-----|-------------------------------------------------|
+| 100 | Ambulance and Fire Brigade (Belgium) |
+| 112 | Police and Ambulance (Italy) |
+| 112 | General emergency call, all categories (Sweden) |
+| 115 | Fire Brigade (Italy) |
+| 144 | Ambulance (Austria) |
+
+If the UE does not recognise the emergency call numbers but the serving network recognises the dialled number as an emergency call number used in the country, a normal call set up shall take place over the radio interface and after the serving network has recognised the emergency number the call shall be routed as an emergency call.
+
+The user friendly MMI that specifies the type of emergency call directly (e.g. menu) should be supported for use in any (i.e. home or visited) PLMN to avoid the misconnection in roaming case. This shall be allowed both with and without SIM/USIM being present.
+
+When emergency call establishment is initiated, the emergency call type shall be sent by the UE if it is available.
+
+The serving network may download emergency call numbers to the UE in order to ensure that local emergency call numbers are known to the UE. In case of PLMN, the UE shall regard these emergency numbers as valid in that country only (as identified by the MCC) and shall discard them when a new country is entered.
+
+Note 3: The UE can inform the user if the emergency call type for an emergency number received from the serving network differs from that configured on the USIM/SIM for the same number. How this is implemented is outside the scope of 3GPP and takes into consideration operator policy and regulatory requirements.
+
+If permitted by local regulation, it shall be possible for the user to prevent the sending of his public user identifiers and the location information to the PSAP (i.e. emergency response centre).
+
+Note 4: Operator policies (e.g. requirements for support of emergency communications) may over-ride the user request for suppression.
+
+Emergency calls over WLAN shall be supported as above with the following caveats:
+
+- The UE issues an Emergency session over WLAN access to EPC only when 3GPP access for emergency call is not possible or available (e.g. no 3GPP coverage).
+- UEs shall only be able to establish an Emergency session over WLAN when the UE has been provisioned with the WLAN access parameters.
+- Service continuity for an Emergency voice call moving from 3GPP access CS domain to WLAN access IMS domain is not supported.
+- The level of security should not be less than that which is currently applied to authenticated and unauthenticated CS or IMS emergency calls.
+- Emergency call numbers downloaded to the UE over WLAN from untrusted sources shall not be used by the UE.
+
+NOTE 5: TS 23.402 [57] establishes when WLAN is trusted or not.
+
+- Subject to local 3GPP operator policy, the UE may use additional emergency call number(s) received via WLAN access for emergency calls via 3GPP access or WLAN access, while in the country for which the numbers were received.
+
+### 10.1.1 Identification of emergency numbers
+
+The ME shall identify an emergency number dialled by the end user as a valid emergency number and initiate emergency call establishment if it occurs under one or more of the following conditions. If it occurs outside of the following conditions, the ME should not initiate emergency call establishment but normal call establishment. Emergency number identification takes place before and takes precedence over any other (e.g. supplementary service related) number analysis.
+
+- a) 112 and 911 shall always be available. These numbers shall be stored on the ME.
+- b) Any emergency call number stored on a SIM/USIM when the SIM/USIM is present.
+- c) 000, 08, 110, 999, 118 and 119 when a SIM/USIM is not present. These numbers shall be stored on the ME.
+- d) Additional emergency call numbers that may have been downloaded by the serving network when the SIM/USIM is present.
+
+### 10.1.2 Domains priority and selection for UE attempts to emergency call
+
+#### 10.1.2.1 Voice and GTT only
+
+A UE that is connected to a domain in which it is possible for the UE to make non emergency calls using the particular media requested by the user, shall use that domain to attempt an emergency call unless serving network policy (based on regulatory requirements and operator needs) requires the UE, including an unauthenticated UE, to attempt the emergency call on a specific domain first.
+
+If the UE is connected to more than one domain in which it is possible for the UE to make non emergency calls using the particular media requested by the user, the UE shall attempt an emergency call on the same domain it would use to originate a non-emergency call using the same media unless serving network policy (based on regulatory requirements and operator needs) requires the UE, including an unauthenticated UE, to attempt the emergency call on a specific domain first.
+
+In the case where an emergency call attempt by a UE fails, the UE should automatically make a second attempt on the other domain if the UE supports it.
+
+If the user aborts the emergency call setup during the subsequent automatic attempt and immediately tries to set up an emergency call again, then the UE shall immediately attempt in the domain in which the user aborted the emergency call.
+
+#### 10.1.2.2 Other media
+
+The following applies in addition to 10.1.2.1.
+
+If an emergency call attempt that includes a request for both (i) voice and/or GTT and (ii) other media cannot be supported or fails in all connected access types in the PS CN domain, the UE shall attempt the emergency call in the CS domain if available and shall only include the request for voice and/or GTT.
+
+### 10.1.3 Call-Back Requirements
+
+Subject to local/regional regulations the network shall support a call-back from a PSAP.
+
+It shall be possible to supply the user's Directory Number/MSISDN/SIP URI as the CLI to the PSAP to facilitate call-back. The CLI used on call-back shall allow the PSAP to contact the same terminal that originated the emergency call.
+
+If the incoming call can be identified by the core network as a call-back to an emergency call (i.e. coming from a PSAP) then supplementary services at the terminating party shall be handled as described in TS 22.173 [40] for Multimedia Telephony (e.g. Communication Diversion, Communication Hold, Communication Barring).
+
+NOTE: There is no specific callback requirement for CS supplementary services.
+
+A call-back may be attempted for a period of time defined by local regulations after the emergency call release. In case of a UE in limited service state, call-back is not required.
+
+## 10.2 Emergency calls in the CS CN Domain
+
+A CS CN Domain shall support the emergency call teleservice as defined in 3GPP TS 22.003 [14] (TS12).
+
+If a UE supports TS11(Telephony)[14], then it shall also support TS12(Emergency Calls)[14]. It shall be possible to set up emergency calls initiated by an emergency call number.
+
+## 10.3 Emergency Calls in the PS CN Domain
+
+Without the IM CN subsystem, emergency calls are not supported in the PS CN domain.
+
+## 10.4 Emergency calls in the IM CN subsystem
+
+### 10.4.1 General
+
+The IM CN subsystem shall support IMS emergency calls. It shall be possible to set up emergency calls initiated by an emergency call number.
+
+If a UE supports IMS Multimedia Telephony service with speech media as specified in TS 22.173 [40] via an access network, then it shall also support IMS emergency calls via that access network.
+
+Subject to the regulatory requirement, the IM CN subsystem shall be able to unambiguously identify each emergency service defined in the national numbering plan for the country in which the UE is located.
+
+In accordance with national regulations for where the subscriber is located, if the UE does not recognise a dialled number as an emergency call number but the IM CN where the subscriber is located does recognise the dialled number as an emergency call number (e.g. a number used in the local emergency numbering plan) then the call shall be routed as an emergency call indicating the type of emergency service to the correct PSAP. Subject to operator setting the call may be prioritized.
+
+Note 1: The above does not preclude the network rejecting the call and requesting the UE to setup a new emergency call to the same emergency service.
+
+The serving network may download emergency call numbers and emergency call types, together with a validity indication of this list, for use in the IM CN subsystem so that local emergency call numbers are made known to the UE. Depending on the validity indication, the UE shall regard these emergency numbers and emergency call types as valid in that country (as identified by the MCC) and shall discard them when a new country is entered, or the UE shall regard these emergency numbers and emergency call types as valid in that serving network, which can be a PLMN (as identified by the MCC and MNC) or an NPN, and shall discard them when the UE enters a new PLMN or NPN.
+
+Emergency calls may be initiated using a private numbering plan [49].
+
+Note 2: There can be an overlap between the private numbering plan of a hosted enterprise and the public numbering plan, which makes translation of emergency numbers necessary.
+
+Emergency calls may be initiated by a service when requested by the user.
+
+Note 3: It is not intended to enable automatic setup of emergency calls.
+
+Note 4: Only speech and GTT-IP [47] media are supported, when required per subclause 10.1, for emergency services towards a CS PSAP.
+
+An emergency call shall take precedence over any other services a UE may be engaged in, if required by local regulation.
+
+Emergency calls from an unauthenticated UE (as far as the IM CN is concerned) shall be supported by the IM CN subsystem, if required by local regulation.
+
+Subject to regulatory requirements, when UEs must be authenticated, both the network and the UE shall support the same authentication and security methods that are used for non-emergency sessions.
+
+### 10.4.2 IMS Multimedia Emergency Sessions
+
+#### 10.4.2.1 General
+
+For IMS emergency calls towards IP PSAPs, other media types may be supported by the UE and the IMS, subject to regulatory requirements.
+
+The media types that may be supported during an IMS MES include:
+
+- Real time video (simplex, full duplex), synchronized with speech if present;
+- Session mode text-based instant messaging;
+- File transfer;
+- Video clip sharing, picture sharing, audio clip sharing;
+- Voice; and
+- Real-Time Text .
+
+Note 1: An IMS MES need not contain voice or Real-Time Text .
+
+To avoid interworking issues, a UE and IMS that supports text based instant messaging shall support a common session mode text-based instant messaging protocol.
+
+IMS MES does not include support for legacy store and forward messaging such as the Short Messaging Service (SMS).
+
+Calls from non-human associated devices (e.g. fire alarms) are outside the scope of this specification.
+
+Adding, removing and modifying individual media to/from an IMS MES shall be supported.
+
+An IMS MES is not a subscription service. A UE capable of IMS emergency calls and capable of supporting the other media types should also be able to support initiation of an IMSMES.
+
+An IMS MES from an unauthenticated UE (as far as the IM CN is concerned) shall be supported by the IM CN subsystem, if required by local regulation.
+
+IMS MES shall be supported by UEs that are subject to service restrictions, e.g. for UEs camping on a cell in a forbidden PLMN or in a forbidden LA (see 3GPP TS 22.011 [11]), or on a CSG cell without the subscriber being a member of that CSG (see 3GPP TS 22.220 [48]). Such IMS MES shall be accepted by the network if required by local regulation.
+
+An IMS MES shall support providing the location of the UE, in a manner similar to IMS emergency voice calls.
+
+An IMS UE that supports IMS MES shall identify an emergency number dialled by the end user as a valid emergency number utilizing the same mechanisms as used for IMS emergency voice calls as defined in subclause 10.1.1.
+
+Note 2: This capability supports the general public, including facilitating emergency communications by individuals with disabilities (e.g. persons who are deaf, deaf-blind, hard of hearing, or have a speech disability).
+
+An originating network and UE may support some or all of these other media types, and support of any specific media by an originating network or UE may be subject to regulatory requirements.
+
+Voice call continuity per clause 21 shall be supported when a UE with an active IMS MES with voice and other media moves out of IMS voice coverage and voice call continuity is supported by the UE and network. The remaining media (i.e. voice call) then becomes a CS emergency call e.g. TS12 call for 3GPP systems as defined in 3GPP TS 22.003 [14].
+
+Other media shall be dropped when a UE with an active IMS MES moves out of IMS voice coverage, irrespective of whether or not there is an active voice session.
+
+#### 10.4.2.2 UE Requirements
+
+When IMS MES are supported by the UE, the following apply:
+
+- An IMS UE that supports IMS MES shall also support IMS emergency voice calls.
+- Once a UE is aware that an IMS MES has been initiated, the UE shall be able to (subject to user configuration) avoid drawing unnecessary attention to the user (e.g., playing audible tones or flashing brightly) and should confirm this to the user in as private a manner as is reasonable e.g. using text on the screen or audio if headphones are already connected. UE behaviour in an IMS MES may need to be different relative to the normal configuration.
+
+- The UE should clearly differentiate IMS emergency session-mode text based instant messaging from IMS non-emergency session-mode text based instant messaging on the user display.
+- The IMS UE supporting video transfer during an IMS MES should be able to deliver recorded media in a form that allows progressive playback. (It is desirable that all pre-recorded media sent during an emergency session be progressively viewable.)
+- When an IP PSAP attempts to add additional media to an existing IMS MES, the user shall be made aware of this. When additional media is requested by the PSAP, the user shall be able to permit or deny it.
+- The UE shall provide an indication to the user for each requested media, whether it was successfully or unsuccessfully established.
+- Further notifications of added and removed media shall be indicated to the user while the IMS MES is active.
+- If none of the media requested by the UE is successfully established, the IMS MES will fail and an IMS MES failure indication shall be provided to the user.
+- In handover of an IMS MES where other media is dropped when IMS MES is not supported, the UE shall indicate to the end user that the other media is not supported in this area.
+
+The following requirements for IMS emergency voice calls also apply when an IMS MES is supported by the UE:
+
+- An IMS UE that supports IMS MES shall indicate to the network that the call is an IMS emergency call as is done for an IMS emergency voice call.
+- An IMS UE that supports IMS MES shall be able to receive an IMS call-back from a PSAP per clause 10.1.3 with voice, GTT or other media per clause 10.4.2.1.
+- An IMS UE that supports MES shall utilize the same trust and security mechanisms for the other media as utilized for an IMS emergency voice call.
+- When roaming, a UE shall originate an IMS MES in the serving network in the same manner as for IMS emergency voice calls.
+
+#### 10.4.2.3 Originating Network Requirements
+
+When an IMS MES is enabled by the originating network, the following apply:
+
+- Other media shall only be supported in packet-based networks that support IMS emergency voice calls.
+- The originating network shall deliver all media to the same IP PSAP throughout the duration of the IMS MES.
+- The network shall indicate to the UE, for each requested media, whether it was successfully or unsuccessfully established.
+- Further notification of added and removed media shall be provided to the UE while the IMS MES is active.
+- If none of the media requested by the UE is successfully established, the IMS MES will fail and an IMS MES failure indication will be provided to the UE.
+
+The following requirements for IMS emergency voice calls also apply when IMS MES is supported by the network:
+
+- Subject to regional regulatory requirements, the network shall be able to authenticate the UE using the same procedures as for IMS emergency voice calls.
+- The originating network shall provide the capability to enable an IMS UE supporting IMS MES to obtain local emergency numbers or other emergency address(es) (e.g. destination address) utilizing the same mechanism as used for IMS emergency voice calls.
+- An IMS MES shall be provided in the local serving network.
+- For an IMS MES, any kind of emergency addressing (e.g. SIP URIs, Tel URIs) and special indications for emergency sessions shall be treated in the same manner as IMS emergency voice calls.
+
+- The originating network should detect all IMS MESs regardless of the UE emergency call indication. According to operator policy, the originating network may either inform the UE to enable re-origination as an IMS MES or support origination of the initial call.
+- The originating network shall be responsible for routing the IMS MES towards the appropriate PSAP (e.g., based on emergency service type, location, or policy).
+- The network shall be able to provide integrity protection, and/or privacy for other media similar to that provided for IMS emergency voice calls.
+- An IMS MES shall utilize the same priority mechanisms as IMS emergency voice calls.
+- Detailed log records of the IMS MES shall be generated by the originating network in a similar manner to IMS emergency voice calls and subject to regulatory requirements.
+- All media content within the IMS MES shall be carried with an indication of the source, in a similar manner as for IMS emergency voice calls.
+
+## 10.5 Void
+
+## 10.6 Location Availability for Emergency Calls
+
+National regulations may require wireless networks to provide the emergency caller's location. This requirement typically overrides the caller's right to privacy with respect to their location being revealed, but remains in effect only as long as the authorities need to determine the caller's location. The interpretation of the duration of this privacy override may also be different, subject to national regulation. For example, some countries require location to be available from the wireless network only while the call is up, while others may allow PSAP's to unilaterally decide how long the location must be made available.
+
+Therefore, the requirement for providing location availability is to allow the network to support providing a mobile caller's location to the authorities for as long as required by the national regulation in force for that network.
+
+NOTE: See TS 22.071 [44] for location service requirements on emergency calls.
+
+## 10.7 Transfer of data during emergency calls
+
+Emergency calls may be supplemented with emergency related data [1]. Typically this data enables the accurate geographic location of a manually or automatically activated emergency calling device e.g. an in vehicle system (IVS), to be provided to the Public Safety Answering Point (PSAP).
+
+The following requirements apply to UEs designed to be able to perform eCalls and to networks supporting eCall:
+
+- The data may be sent prior to, in parallel with, or at the start of the voice component of an eCall.
+- Should the PSAP request additional data then this may be possible during the established eCall.
+- The realisation of the transfer of data during an eCall shall minimise changes to the originating and transit networks.
+- Both the voice and data components of the eCall shall be routed to the same PSAP or designated emergency call centre.
+- The transmission of the data shall be acknowledged and, if necessary, data shall be retransmitted.
+- The UE shall indicate at call setup if the emergency call will carry supplementary data, i.e. is an eCall.
+
+UEs designed to be able to perform eCalls and configured to only perform eCalls (eCall only mode) shall comply with the following additional requirements:
+
+- The UE shall not perform mobility management procedures, including registration on a PLMN, except when attempting to initiate and during an eCall, or to initiate a test or reconfiguration of the terminal upon request from the user.
+
+- For UEs that have the ability to be called back by the PSAP, the UE shall be capable to continue mobility management procedures for a limited duration following the termination of the eCall.
+- The UE shall contain an USIM application.
+- In the case where the user subscribes to other services provided by the PLMN, it shall be possible for the network operator to reconfigure the UE so that it can access the subscribed services.
+- It shall be possible for the user of the UE to change network operator/service provider (i.e. to use a different USIM) or for the subscriber to modify the existing subscription used with the UE.
+- It shall be possible for the UE upon request from the user to initiate a call to an operator designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services.
+
+Additional national and regional requirements are as specified in Annex A.
+
+## 10.8 Supplementary service interaction during emergency calls
+
+Supplementary services that interrupt or divert the media path between a PSAP and the end device shall be handled as specified in TS 22.173 [40] (e.g. Communication Hold) for Multimedia Telephony. No such Supplementary Services are applicable to CS Emergency Calls (TS12) according to TS 22.004 [5].
+
+## 10.9 Emergency Calls in a MUSIM UE
+
+A MUSIM UE shall be able to select a USIM to originate an emergency call in the following priority:
+
+- USIM in normal service
+- USIM in limited service state
+
+The MUSIM UE shall avoid interruptions of emergency call procedures of one USIM by other services of other USIM.
+
+Subject to regulatory requirements, call-back requirements defined in clause 10.1.3 apply to a MUSIM UE.
+
+## 10.10 Emergency Services over Non-public networks
+
+Subject to local/regional regulations, the 5G system shall support IMS Multimedia Emergency services (see clause 10.4) over non-public network (NPN) [59] for NPNs using IMS.
+
+## 10.11 Short Message Service over IMS to emergency centre
+
+EPS and 5GS shall route a Short Message over IMS using the emergency numbers to a local emergency response centre (i.e. PSAP), according to the local regulations.
+
+The Short Message shall be routed to the emergency response centre serving the location where the subscriber is located and replies routed back to the subscriber in accordance with national regulations as specified in 10.1.
+
+The 3GPP system shall support a Short Message to be routed to different emergency response centres, depending on the type of emergency as specified in 10.1.
+
+The Short Message Service to emergency response centre shall be supported without a SIM/USIM/ISIM being present.
+
+- Note 1: It will be left to the national authorities to decide whether the network accepts Short Message Service to emergency response centre without the SIM/USIM/ISIM.
+
+The Short Message Service to emergency response centre shall be able to use the same identification methods as for emergency calls, as specified in 10.1.1.
+
+Subject to local/regional regulations Short Message Service to emergency response centre shall support location service as specified in chapter 10.6.
+
+## 10.12 Emergency Sessions over Relay UEs
+
+Where the 5G system supports remote UE access to emergency sessions via relay UEs, the following requirements apply:
+
+- Subject to local regulatory requirements, the UE shall first attempt to make an emergency session via any available network. If the UE fails to find a network that allows emergency sessions, the UE shall attempt an emergency session via a relay UE.
+- Subject to local regulatory requirements, the 5G system shall route emergency sessions to an appropriate PSAP for the location of the remote UE, which can be in the same country of the remote UE or not.
+
+# --- 11 Numbering principles
+
+The following network addressing schemes listed below shall be supported at the relevant domains:
+
+- E.164,
+- E.168,
+- E.212,
+- X.121
+- Internet (including e.g. IP address, SIP URI).
+
+## 11.1 Number portability
+
+### 11.1.1 Requirements for CS CN domain
+
+Some numbering schemes shall be fully independent of the supporting serving network and the home environment, allowing users to transfer this number to another home environment. For further information see 3GPP TS 22.066 [7].
+
+An MSISDN shall be allocated to each new user at the start of a subscription. This number may be allocated from one of several numbering domains. For example:
+
+- home / serving environment numbering scheme;
+- national numbering scheme;
+- regional numbering scheme;
+- global numbering scheme.
+
+A user shall be able to move subscription from one home environment to another without changing the MSISDN provided that the new home environment offers service in the same geographic domain. It is envisaged that home environment s will be able to allocate MSISDNs from each of these domains as required.
+
+### 11.1.2 Requirements for PS CN domain
+
+None identified.
+
+### 11.1.3 Requirements for IM CN subsystem
+
+It shall be possible to offer number portability for E.164 numbers within IM CN subsystem. For further information see 3GPP TS 22.066 [7].
+
+## 11.2 Evolution path
+
+Since 3GPP specifications aim to be aligned with IMT-2000, a primary goal in numbering is the provision of global user numbering in line with steps taken by the ITU - SG2.
+
+The numbering scheme and network implementation chosen shall allow for international/global evolution.
+
+## 11.3 Void
+
+## 11.4 Void
+
+## 11.5 Void
+
+## 11.6 Private numbering
+
+A user may wish to use private numbers for the purposes of calling frequent numbers. Therefore there is a requirement for the use, by the user, of Private Numbering Plans (PNPs). These schemes may belong to the user himself, to a home environment or a third-party.
+
+## 11.7 Numbering schemes
+
+### 11.7.1 Multiple numbering scheme
+
+The standards shall support the possibility of allowing the bearer service associated with an MT call to be implicitly defined by the destination MSISDN, for example to use a different MSISDN to establish voice, fax or data. It will be possible for multiple MSISDNs to be associated with a single subscription.
+
+### 11.7.2 Single numbering scheme
+
+The standards shall support the possibility of allowing MT calls of different bearer types (e.g. voice, fax, data) to be routed to a single MSISDN. It is recognised that the implementation of this may depend on the availability of bearer information associated with an incoming call from the adjoining transit network. In particular the standards will support this possibility in the case of an adjoining ISDN transit network.
+
+### 11.7.3 Additional numbers
+
+The 3GPP system shall support the possibility to assign an additional MSISDN, in addition to the original MSISDN, to a user with a connection to the PS CN domain. If this additional MSISDN is available, it shall be used for correlation of CS and IMS in voice call and service continuity as well as IMS Centralized Service. In this case the original MSISDN may be used for charging and OA&M purposes and forwarded to the PS gateway to other packet data networks.
+
+## 11.8 Optimal routing
+
+The implementation of the numbering scheme used shall allow for optimal routing; i.e. routing shall not take place simply on the number dialled.
+
+See 3GPP TS 22.079 [8] for some scenarios for the CS CN domain. Optimal routing for IP services is supported by the All-IP Network [42].
+
+# --- 11a Identification Requirements
+
+## 11a.1 Subscriber Identification
+
+In 3GPP the identity of a subscriber is encoded in a identity module application which is contained on a UICC or on a GSM SIM card. The GSM SIM card is a removable component of the User Equipment; UICC can be removable or also embedded. Three types of identity modules are used in the 3GPP system:
+
+- Universal Subscriber Identity Module (USIM)
+- IMS Subscriber Identity Module (ISIM)
+- Subscriber Identity Module (SIM) according to GSM
+
+General requirements:
+
+- In the 3GPP system each subscriber shall be uniquely identifiable.
+- The serving networks shall be able to authenticate any subscriber that roams onto their network
+- If a UE, that is registered on the serving network, contains a GSM SIM card or a UICC containing a identity module application, the serving network shall be able to identify the associated home PLMN.
+
+Note 1: UE support of GSM SIM is optional.
+
+Note 2: See the chapter (USIM, UICC and Terminal) of the present specification for a reference, which GSM phase SIMs need to be supported by the network.
+
+## 11a.2 Terminal Identification
+
+It is a requirement that the terminal can be uniquely identified by the home environment and serving network. This shall require a terminal identity scheme which uniquely identifies each terminal, see 3GPP TS 22.016[12].
+
+## 11a.3 Home Environment / Serving Network Identification
+
+Home / serving environments need to route communication to the current location of the user. This shall require a identity scheme which uniquely identifies the serving environment and shall be used for routing purposes.
+
+## 11a.4 Serving Environment / Mobile Virtual Network Identification
+
+A mobile virtual network operator (MVNO) is a service provider that does not have its own radio access network, but resells wireless services, typically under their own brand name, using the network of a host PLMN operator.
+
+It should be possible to uniquely identify subscribers belonging to a particular MVNO.
+
+# --- 12 Human Factors and user procedures
+
+The User Interface (MMI) from the end-user's point of view should be as flexible as possible while still meeting the general service requirements. In addition, it should be capable of being updated so as to meet new services which are still to be envisaged.
+
+In general, the following principles should be encompassed:
+
+- activation of services should be as simple as possible with minimum input expected from the user;
+- feedback, to the user from the various services, should be meaningful;
+- any error recovery procedures provided should be simple to understand and execute.
+- input from the user and information to the user should be provided in alternative selectable modes in order to match user capabilities, preferences and situation.
+
+However, a detailed specification for the User Interface shall not be defined. In particular given the global nature of the third generation systems, for different regions of the world, different criteria will determine the implementation of the User Interface. Also it is unlikely that there will be a single common handset which will meet all the service requirements and therefore a common User Interface would be impractical.
+
+Given the flexibility of the services, there should be a wide range of User Interface possibilities. These possibilities include simple terminals with a single on/off button through to complex terminals providing support to hearing/visually impaired users.
+
+Control of CS CN Domain supplementary services (3GPP TS 22.004 [5]), may use MMI procedures specified in 3GPP TS 22.030 [6] and existing MMI related UE features (Annex A) may also be used. In particular the following features are highly desirable for uniform UE implementation where appropriate:
+
+- Mapping of numeric keys to European alphabetic keys to ensure compatible mnemonic dialing as defined in 3GPP TS 22.030 [6],
+- "+" key function to enable one key international access as defined in Annex A
+- Structure of the MMI as described in 3GPP TS 22.030 [6]
+- Presentation of IMEI (International Mobile Equipment Identity) as defined in 3GPP TS 22.030 [6].
+
+# --- 13 UICC, USIM and Terminal
+
+This clause defines the functional characteristics and requirements of the User Service Identity Module (USIM) and ISIM (IM Services Identity Module). The USIM/ISIM are applications residing on a UICC.
+
+## 13.1 The USIM/ISIM and User Profiles
+
+### 13.1.1 The USIM
+
+Every USIM shall have a unique identity and shall be associated with one and only one home environment.
+
+It shall be possible for a home environment to uniquely identify a user by the USIM.
+
+The USIM shall be used to provide security features.
+
+For access to services, provided by PS or CS CN domains, a valid USIM shall be required. Optionally, SIM according to GSM phase 2, GSM phase 2+, 3GPP release 99, 3GPP release 4 specifications may be supported.
+
+The USIM shall be able to support SIM Application Toolkit as specified in 3GPP TS 22.038 [3].
+
+The USIM shall reside on a UICC. USIM specific information shall be protected against unauthorised access or alteration.
+
+It shall be possible to update USIM specific information via the radio interface, in a secure manner.
+
+Access to the IMS services shall be possible using the USIM application in the event of no ISIM being present on the UICC. If an ISIM is present on the UICC it shall be used to access the IMS.
+
+It shall be possible to store provisioning parameters on the USIM according to DM specifications [37].
+
+It should be possible to store provisioning parameters on the USIM according to CP specifications [38].
+
+It shall be possible for the network operator to configure the USIM to indicate (through personalisation and OTA) whether provisioning parameters according to DM specifications or provisioning parameters according to CP specifications shall be used.
+
+**NOTE:** To avoid misoperation of the UE in a mixed provisioning environment e.g. during a transition phase when both CP and DM clients are present in the UE, the CP parameters on the USIM can be read first. If DM information is present (provisioned OTA in the CP parameters.), then use DM, otherwise use CP.
+
+Annex A describes a number of features that may optionally be supported by the UE and thus USIM.
+
+### 13.1.2 User Profiles
+
+It shall be possible for a user to be associated with one or a number of user profiles, which the user can select and activate on a per call basis. The user profile contains information which may be used to personalise services for the user.
+
+It shall be possible for one or more user profiles associated with the same user to be active simultaneously so that the user may make or receive calls associated with different profiles simultaneously. Activation of profiles shall be done in a secure manner, for example with the use of a PIN.
+
+For terminating calls the correct profile shall be indicated by the user address used (e.g. MSISDN, SIP URI), each profile will have at least one unique user address associated with it. For originating calls the user shall be able to choose from the available profiles, the appropriate one for the call. A profile identity will need to be associated with the call for accounting and billing purposes. User profile identities need not be standardised but a standardised means is required for indicating that a particular profile is being used.
+
+Simultaneous use of the same user profile on multiple terminals for the same type of service shall not be allowed.
+
+User profiles associated with different home environments shall not share the same user address.
+
+### 13.1.3 UICC usage in GERAN only Terminals
+
+In Release 5 and later, terminals supporting only GERAN shall support USIM.
+
+NOTE: It is strongly recommended that manufacturers implement SIM support on GERAN only terminals until the population of SIMs in the market is reduced to a low level.
+
+### 13.1.4 Multiple USIMs per UICC
+
+The standard shall support more than one USIM per UICC even when those USIMs are associated with different home environments. Only one of the USIMs or the SIM shall be active at a given time. While the UE is in idle mode, it shall be possible for the user to select/reselect one USIM application amongst those available on the UICC. At switch on, the Last Active USIM shall be automatically selected. The Last Active USIM shall be stored on the UICC. By default if there is no Last Active USIM defined in the UICC, the user shall be able to select the active USIM amongst those available on the UICC.
+
+The standard must not prevent the coexistence of USIM applications, each associated with different home environments on the same UICC, so long as the security problems which arise from such a coexistence are solved.
+
+### 13.1.5 The ISIM
+
+Access to the IMS services shall be possible using an ISIM application.
+
+The ISIM shall be sufficient for providing the necessary security features for the IMS and IMS only.
+
+The ISIM shall reside on a UICC. ISIM specific information shall be protected against unauthorised access or alteration.
+
+It shall be possible to update ISIM specific information via the radio interface, in a secure manner.
+
+NOTE: When accessing IMS over GERAN/UTRAN/EUTRAN or I-WLAN using ISIM, a USIM needs also be present to access the rest of the 3GPP system. Alternatively USIM could be used to access IMS.
+
+## 13.2 The UICC
+
+Characteristics including physical formats of a UICC are defined in TS 31.101[36].
+
+Access to services via 3GPP system with a single UICC shall be possible.
+
+NOTE 1: The UICC refers to either a physically distinct module, or to an embedded eUICC (e.g as defined in [62], [63]).
+
+### 13.2.1 The UICC and Applications other than the USIM or ISIM
+
+It shall be possible for the UICC to host other applications in addition to the USIM or ISIM, see figure 3. Service providers, subscribers or users may need to establish additional data or processes on the UICC. Each application on an UICC shall reside in its own domain (physical or logical). It shall be possible to manage each application on the card separately. The security and operation of an application in any domain shall not be compromised by an application running in a different domain. Applications may need to use their own security mechanisms which are separate to those specified by 3GPP e.g. electronic commerce applications.
+
+Examples of UICC applications are: USIM, ISIM, off-line user applications like UPT, electronic banking, credit service, etc.
+
+Applications should be able to share some information such as a common address book.
+
+It shall be possible to address applications, which reside on the UICC, via the radio interface.
+
+
+
+The diagram illustrates a Multifunction UICC (IC-card) containing three distinct applications: a USIM application, an 'Other appl.' (Other application), and another USIM application. Below the card, two Service Providers, labeled SP 1 and SP 2, are shown. SP 1 has an arrow pointing to the first USIM application, and SP 2 has an arrow pointing to the third USIM application, indicating that each service provider can access its respective USIM application on the same card.
+
+Diagram of a Multifunction UICC (IC-card) showing three applications: USIM, Other appl., and USIM. Two Service Providers, SP 1 and SP 2, are shown below the card with arrows pointing to the first and third applications respectively.
+
+**Figure 3: Example of a Multifunction UICC**
+
+### 13.2.1a UICC applications and IMS
+
+UICC applications may make use of IMS functionalities controlled by ME.
+
+**NOTE:** This is to allow a UICC application to interact with an Application Server (AS) through IMS. Examples of UICC applications include identity management, banking applications, etc.
+
+### 13.2.2 Fast Access and Retrieval of Data from UICC
+
+An optional "high speed" interface may be provided between the UICC and the ME.
+
+If provided, this interface shall allow fast access and retrieval of data to support functionalities requiring large amounts of data to be transferred to and from the UICC. Examples include:
+
+- on-card web servers
+- rapid access to data stored on the UICC, e.g. phone book, PLMN lists or user data
+
+A UICC/ME interface supporting this "high speed" interface shall be backward compatible with the TS 102 221 interface specified in 3GPP TS 31.101 [36].
+
+## 13.3 Terminals and Multiple UICCs
+
+A single terminal may support the use of multiple UICC (e.g. with applications like USIM and/or banking, credit card,...). Only one UICC shall be active at a time to access a PLMN. In case the active UICC contains more than one USIM, the requirements of 13.1.4 shall apply.
+
+If the UICC with the active USIM is removed from the mobile terminal during a call (except for emergency calls), the call shall be terminated immediately. If the UICC with an active ISIM is removed during an IMS session the IMS session shall be terminated.
+
+## 13.4 Multiple USIMs
+
+With the growing demand in the consumer market, some commercially deployed UEs support more than one USIM (typically two). With support of MUSIM UEs in the 3GPP system, the system performance and user experiences are expected to be improved.
+
+The 3GPP system shall support ME with multiple USIMs (on the same UICC or on different UICCs) that are registered at the same time.
+
+The 3GPP system shall treat each registration from the USIMs of a MUSIM UE independently. Each registered USIM in a MUSIM UE shall be associated with a dedicated IMEI/PEI.
+
+# 14 Types of features of UEs
+
+3GPP specifications should support a wide variety of user equipment, i.e. setting any limitations on terminals should be avoided as much as possible. For example user equipment like hand-portable phones, personal digital assistants and laptop computers can clearly be seen as likely terminals.
+
+In order not to limit the possible types of user equipment they are not standardised. The UE types could be categorised by their service capabilities rather than by their physical characteristics. Typical examples are speech only UE, narrowband data UE, wideband data UE, data and speech UE, etc.
+
+In order to enhance functionality split and modularity inside the user equipment the interfaces of UE should be identified. Interfaces like UICC-interface, PCMCIA-interface and other PC-interfaces, including software interfaces, should be covered by references to the applicable interface standards.
+
+UEs have to be capable of supporting a wide variety of teleservices, multimedia services and applications provided in PLMN environment. Limitations may exist on UEs capability to support all possible teleservices, multimedia services and information types (speech, narrowband data, wideband data, video, etc.) and therefore functionality to indicate capabilities of a UE shall be specified.
+
+The basic mandatory UE requirements are:
+
+- Support for USIM. Optional support of GSM phase 2, 2+, 3GPP Release 99 and Release 4 SIM cards [34]. Phase 1, 5V SIM cards shall not be supported. Support for the SIM/ISIM is optional for the UE, however, if it is supported, the mandatory requirements for SIM/ISIM shall be supported in the UE;
+
+Note 1: There is no Release 5 specification for the SIM, and therefore references to "SIM" apply to earlier releases.
+
+Note 2: It is strongly recommended that manufacturers implement SIM support on terminals supporting GERAN until the population of SIMs in the market is reduced to a low level.
+
+- Home environment and serving network registration and deregistration;
+- Location update;
+- Originating or receiving a connection oriented or a connectionless service;
+- An unalterable equipment identification; IMEI, see 3GPP TS 22.016 [12];
+- Basic identification of the terminal capabilities related to services such as; the support for software downloading, application execution environment/interface, MExE terminal class, supported bearer services.
+- Terminals capable for emergency calls shall support emergency call without a SIM/USIM/ISIM.
+- Support for the execution of algorithms required for encryption, for CS and PS services. Support for non encrypted mode is required;
+- Support for the method of handling automatic calling repeat attempt restrictions as specified in 3GPP TS 22.001 [4];
+- At least one capability type shall be standardised for mobile terminals supporting the GERAN,UTRAN and E-UTRAN radio interfaces.
+- Under emergency situations, it may be desirable for the operator to prevent UE users from making access attempts (including emergency call attempts) or responding to pages in specified areas of a network, see 3GPP TS 22.011 [11];
+- Ciphering Indicator for terminals with a suitable display;
+- The ciphering indicator feature allows the UE to detect that the 3GPP radio interface ciphering (user plane) is not switched on and to indicate this to the user. The ciphering indicator feature may be disabled by the home network operator setting data in the SIM/USIM. The default terminal behaviour shall be to take into account the operator setting data in the SIM/USIM. However, terminals with a user interface that can allow it, shall offer the possibility for the user to configure the terminal to ignore the operator setting data in the SIM/USIM. If this
+
+feature is not disabled by the SIM/USIM or if the terminal has been configured to ignore the operator setting data in the SIM/USIM, then whenever a user plane connection is in place, which is, or becomes un-enciphered, an indication shall be given to the user. In addition, if this feature is not disabled by the SIM/USIM or if the terminal has been configured to ignore the operator setting data in the SIM/USIM, then additional information may also be provided about the status of the ciphering. Ciphering itself is unaffected by this feature, and the user can choose how to proceed;
+
+- Support for PLMN selection.
+- Support for handling of interactions between toolkits concerning the access to UE MMI input/output capabilities;
+- Whenever an application (e.g. a SAT/MExE/WAP application) requires the access to the UE MMI input/output capabilities (e.g. display, keyboard,... ), the UE shall grant this access subject to the capabilities of the UE. This shall not cause the termination of any other applications (e.g. WAP browser or MExE/SAT application) which were previously using these UE resources. The UE shall give the user the ability to accept or reject the new application. In the case that the application request is rejected, the access to the UE MMI input/output capabilities is returned to the applications which were previously using these UE resources. If the user decides to continue with the new application, then when this new application is terminated, the access to the UE MMI input/output capabilities shall be returned to the UE to be re-allocated to applications (e.g. the preceding application which was interrupted). Subject to the capabilities of the UE, the user shall have the ability to switch the MMI input/output capabilities between applications.
+
+NOTE: Rejecting a request to access the UE MMI input/output capabilities by an application does not necessarily mean that it is terminated, but only that the access to the UE MMI input/output capabilities are not granted to this application. Handling of rejection (termination, put on hold,...) is the responsibility of the application.
+
+Annex A describes a number of features which may optionally be supported by the UE.
+
+# 15 Relationship between subscription and service delivery
+
+## 15.1 Subscription
+
+A subscription describes the commercial relationship between the subscriber and the service provider.
+
+
+
+The diagram shows a 'Subscriber' at the top connected to four subscriptions: 'Subscription 1', 'Subscription 2', 'Subscription 3', and 'Subscription n'. 'Subscription 1' is connected to a box labeled 'CS CN Domain Services' which contains 'Service A', 'Service B', 'Service C', 'Service D', and 'Service E'. 'Subscription 2' is connected to two boxes: 'PS CN Domain Services' containing 'Service Z', and 'IM CN Subsystem Services' containing 'Service A\*', 'Service B\*', 'Service C\*', and 'Service D\*'. 'Subscription 3' is also connected to the 'PS CN Domain Services' box. 'Subscription n' is connected to the 'IM CN Subsystem Services' box.
+
+Diagram illustrating the relationship between a Subscriber, multiple Subscriptions, and various CN Domain Services.
+
+Figure 4: Subscriber, subscription and services relationship
+
+A subscription to a network operator may provide the user with access to one or more domains. A Subscription shall identify the set of services, within particular domains, to which the user has access (see figure 3); each subscription may
+
+specify a different set of services. These services may be provided by the CS CN Domain and/or a PS CN Domain and/or an IM CN subsystem. Subscriptions relate to services such as Basic Services (e.g. Teleservices, Bearer services), PS services and IM-Services (IP-based multimedia services), which are typically provided by network operators, and to value added services which typically are provided by network operators and/or other entities that provide services to a subscriber
+
+The subscription identifies:
+
+- the services and related services information that are made available to the subscriber by the service provider;
+
+In addition, a subscription to a network operator may identify:
+
+- the domains to which the user has been granted access by the network operator. In particular, the PS service profile and information on the allowed QoS parameter ranges shall be contained in the subscription.
+
+- the identity of the subscriber within these domains.
+
+NOTE: The identity of a subscriber in the CS CN domain and PS CN domain (e.g. her IMSI) may potentially be different to her identity in the IM CN subsystem
+
+- the radio access systems over which the subscriber may access their services e.g. UTRAN, GERAN, EUTRAN, I-WLAN.
+
+## 15.2 Other concepts associated with services
+
+### Provision of services:
+
+An action to make a service available to a subscriber. The provision may be:
+
+- general: where the service is made available to all subscribers (subject to compatibility restrictions enforced) without prior arrangements being made with the service provider;
+- pre-arranged: where the service is made available to an individual subscriber only after the necessary arrangements have been made with the service provider.
+
+### Withdrawal:
+
+An action taken by the service provider to remove an available service from a subscriber's access. The withdrawal may be:
+
+- general: where the service is removed from all subscribers provided with the service;
+- specific: where the service is removed on an individual basis from subscribers provided with the service.
+
+NOTE: Access to the IM subsystem requires IP connectivity provided, for example, through provision of the PS CN domain.
+
+## 15.3 Requirements concerning service delivery
+
+In general, it is a requirement to allow the use of independent services simultaneously (i.e. Basic, PS, IP multimedia and operator specific).
+
+- 1) The network usage shall be based on the services identified within the subscription, the terminal capabilities and, where applicable, roaming agreements between operators.
+- 2) The Home environment shall be able to decide on the service delivery in a roaming scenario. I.e. it shall control how services are delivered in line with the subscription.
+- 3) If an offered or required service (e.g. voice) could be provided with different technologies within the serving network, the decision on service delivery shall be based on preferences identified in the user profile and serving network capabilities and conditions (e.g. load).
+
+- 4) If the user profile does not allow an alternative service delivery method and the requested delivery method is not available in the serving network the service shall not be provided to the subscriber. This applies also to data bearer services with defined QoS parameters (or parameter ranges).
+
+Examples:
+
+- A terminating voice call for a subscriber with a dual/multi mode terminal (e.g. UTRAN/GERAN) could be delivered in a hybrid network as IM service or CS voice call (TS11). The delivery decision is based on the preferences of service delivery within the user profile and the network conditions. If there is no preference information of the Home environment available the decision is made only on the network conditions from the serving network.
+- A terminating data service (e.g. PS with QoS for real time audio) where the network cannot provide the QoS at call setup. Both the originating and terminating application shall be informed about the possible QoS configuration for that call. The further handling (setup continuation, termination) depends on the decisions of the applications.
+
+### 15.3.1 Mobile Originated Voice calls
+
+When a ME capable of offering voice service both on CS and IMS is CS attached and IMS registered MO CS Voice calls (TS11) and MO IMS voice services shall be originated on the domain specified by the Home operator policy or users preferences. The Home Operator policy shall have precedence to user preferences.
+
+### 15.3.2 Mobile Terminated Voice calls
+
+When a ME capable of offering voice service both on CS and IMS, MT CS Voice calls (TS11) and MT IMS voice services shall be delivered over the domain specified by the Home operator policy or users preferences. The Home Operator policy shall have precedence to user preferences. If the call delivery attempt fails in one domain, if specified by operator policy, it should be possible to attempt the delivery in the other domain or the call/communication forwarding supplementary services [41, 40] may be invoked if provisioned.
+
+NOTE 1: The delivery decision will take into account aspects such as IMS registration and CS attachment status.
+
+NOTE 2: When the terminating network knows that the UE is either IMS registered or CS attached in non-3GPP access (e.g. CDMA), the delivery decision will take this into account in order to select the correct domain.
+
+# --- 16 Charging principles
+
+The cost of the call may cover the cost of sending, transporting, delivery and storage. The cost of call related signalling may also be included. Provision shall be made for charging based on time, destination, location, volume, bandwidth, access technology and quality. Charges may also be levied as a result of the use of value-added services.
+
+It shall be possible for information relating to chargeable events to be made available to the home environment at short notice. The requirements shall include:
+
+- Immediately after a chargeable event is completed;
+- At regular intervals of time, volume or charge during a chargeable event.
+- Delivery of the location of the terminal to the home environment, e.g. cell identification;
+
+Standardised mechanisms of transferring charging information are required to make these requirements possible.
+
+It should be possible for multiple leg calls (e.g. forwarded, conference or roamed) to be charged to each party as if each leg was separately initiated. However, in certain types of call, the originating party may wish/be obliged to pay for other legs (e.g. SMS MO may also pay for the MT leg.).
+
+It shall be possible to charge according to the location (e.g. cell, or zone) and access technology that are being used to access network services.
+
+Provision shall be made for the chargeable party to be changed during the life of the call. There shall be a flexible billing mechanism which may include the use of stored value cards, credit cards or similar devices.
+
+The chargeable party (normally the calling party) shall be provided with an indication of the charges to be levied (e.g. via the called number automatically or the Advice of Charge supplementary service) for the duration of the call (even though the user may change service environment) The user shall be able to make decisions about the acceptable level of accumulated charge dynamically or through their service profile.
+
+If a user is to be charged for accepting a call then their consent should be obtained. This may be done dynamically or through their service profile.
+
+Charging and accounting solutions shall support the shared network architecture so that end users can be appropriately charged for their usage of the shared network, and network sharing partners can be allocated their share of the costs of the shared network resources.
+
+# 17 Roaming
+
+## 17.1 Assumptions
+
+In order to roam, the following applies:
+
+- Mobile terminal can connect to the radio access network.
+- Authentication (charging/billing network) must occur in order to get access to services (except for emergency calls).
+- The services offered to a roaming subscriber may be restricted by the capabilities of the visited network, and the roaming agreement between the visited and the home environment.
+
+## 17.2 Principle
+
+Long term evolution of the IM CN subsystem shall not be restricted by the short/mid-term inter-domain roaming requirements.
+
+## 17.3 Requirements
+
+
+
+The diagram shows a 'Home Environment' box at the top containing three circles: 'CS profile data', 'PS profile data', and 'IM CN profile data'. Below a horizontal line, three ovals represent 'Visited Networks': 'CS visited', 'PS visited', and 'IM CN subsystem visited'. Lines connect each profile data circle in the Home Environment to its corresponding visited network oval.
+
+Diagram illustrating Roaming requirements. The Home Environment contains CS profile data, PS profile data, and IM CN profile data. These are connected to three Visited Networks: CS visited, PS visited, and IM CN subsystem visited.
+
+**Figure 5: Roaming requirements**
+
+- The personalised services & capabilities available in a visited network are dependent upon the subscription options in the home environment. This does not preclude the visited network offering additional services, or access to content providers.
+- Roaming from this release's home environment to CS (this release or earlier) visited network is required
+- Roaming from this release's home environment to IM CN subsystem visited network is required
+- Roaming from this release's home environment to PS (this release or earlier) visited network is required
+- Roaming from previous releases' home environment (or earlier) to this release CS visited network is required
+- Roaming from previous releases' home environment (or earlier) to this release PS visited network is required
+
+NOTE: When an operator allows a subscriber to roam to different domains, the home environment needs to provide subscription data to the visited network . The mapping between service data of the different domains is not standardised; it is determined by the home environment and may be influenced by roaming agreements.
+
+# --- 18 Handover Requirements
+
+Any handover required to maintain an active service while a user is mobile within the coverage area of a given network, shall be seamless from the user's perspective. However handovers that occur between different radio environments may result in a change of the quality of service experienced by the user.
+
+It shall be possible for users to be handed over between different networks subject to appropriate roaming/commercial agreements.
+
+For further information see 3GPP TS 22.129 [9].
+
+# --- 19 Network Selection
+
+Network selection procedures are defined in 3GPP TS 22.011 [11].
+
+Other procedures may be offered by the UE.
+
+# --- 20 Security
+
+Security matters are considered in 3GPP TS 21.133 [15] and 3GPP TS 33.120 [16].
+
+# 21 Voice Call Continuity
+
+## 21.1 General
+
+The 3GPP system shall be able to provide continuity between CS voice services (Teleservice 11[14]) and the full duplex speech component of IMS multimedia telephony service [40] with no negative impact upon the user's experience of the voice service. This functionality is known as voice call continuity. Voice call continuity shall be executed when continuation of a voice service is required based on operator policy across a change in the connection of the UE to the 3GPP system as the user moves from using the CS domain to using IMS and vice versa.
+
+The user experience shall be unaffected by the transition from a CS voice service to a full duplex speech component of IMS multimedia telephony and vice versa, and the user shall experience no disruption in the voice service provided. The voice service is continued with the same ME.
+
+It shall be possible to support Voice call continuity between IMS and the CS domain belonging to different operators; i.e., when the user's IMS services are under the control of the home IMS and the user is roaming in the coverage of the visited CS network.
+
+It shall be possible for an operator to enable or disable Voice call continuity for a given subscriber e.g. based on roaming conditions, terminal capabilities.
+
+## 21.2 Support of Supplementary Services
+
+The voice call continuity user's experience shall be such that, to the greatest degree possible, a consistency of service is provided regardless of the underlying communication infrastructure and technology. With regard to supplementary services, the general principle is that CS-based supplementary services only apply whilst a VCC subscriber is in the CS domain and equivalent services over IMS only apply whilst a VCC subscriber is in the IMS domain, although there are exceptions listed below. It is not required to synchronise the supplementary service settings of the CS domain with the related service settings of the IMS (e.g. different forwarding numbers may apply over CS and over IMS).
+
+The following supplementary services apply. The impact on the supplementary services in case the VCC is executed for the calling party, the called party, or both is described below.
+
+### 21.2.1 Line Identification Services
+
+A user who has subscribed to the CLIP Supplementary Service and receives a call shall also receive the line identity or appropriate IMS information of the calling party.
+
+The identity presentation is not changed for the duration of the call regardless of whether the call undergoes VCC.
+
+If the CLIR Supplementary Service or IMS identity restriction is applicable to the call, then at call setup time the called user shall receive an indication that the identity is not available because of restriction.
+
+The indication is not changed for the duration of the call regardless of whether the call undergoes VCC.
+
+If COLP or a corresponding IMS service is applicable to a call the calling subscriber shall receive the connected line identity or appropriate IMS information at call setup time.
+
+The identity presentation is not changed for the duration of the call regardless of whether the call undergoes VCC.
+
+If the COLR Supplementary Service or IMS identity restriction is applicable to the call, then the calling user shall receive an indication at call setup time that the identity of the connected party is not available because of restriction.
+
+The indication is not changed for the duration of the call regardless of whether the call undergoes VCC.
+
+### 21.2.2 All Call Forwardings
+
+It shall be possible to perform VCC on a call which was forwarded due to call forwarding supplementary services in the CS or redirecting services in the IMS.
+
+### 21.2.3 Call Waiting
+
+The functionality of call waiting supplementary service in the CS domain shall not be affected by the user's ability to undergo VCC.
+
+NOTE: Whether the user will continue to receive call waiting notifications in the case their call is continued in the IMS will depend on whether a call waiting service is available in the IMS.
+
+### 21.2.4 Call Hold
+
+It shall be possible to re-establish a call which has been put on hold before undergoing VCC, after the VCC has been performed.
+
+### 21.2.5 Multiparty
+
+It shall be possible for any party in a multiparty call to undergo VCC and to stay in the call. It shall be possible to terminate the entire multiparty call when the served mobile subscriber releases even if she is connected via the IMS after undergoing VCC.
+
+### 21.2.6 All Call Barrings
+
+If a call were to undergo VCC and that would result in the call being barred in the target domain/system, it shall be up to the home operator policy whether the call continues in the target domain/system, the call terminates, or VCC is not executed for the call.
+
+### 21.2.7 Void
+
+### 21.2.8 Void
+
+### 21.2.9 All other Supplementary Services
+
+Other supplementary services are not discussed in this section as they do not apply to calls in progress (i.e. they apply to call set up only) or their support and/or the need for standardised implementation has not been identified as critical for VCC in this Release.
+
+## 21.3 Quality of Service
+
+Voice call continuity shall not adversely impact the quality of the voice service experienced by the user.
+
+## 21.4 Security
+
+Voice call continuity shall not adversely impact the security of the 3GPP system.
+
+Security mechanisms of the 3GPP system shall be reused for voice call continuity.
+
+## 21.5 Emergency calls
+
+Voice call continuity for emergency calls shall be applicable to dual radio and single radio UEs.
+
+Voice call continuity of emergency calls shall only be performed when all the following conditions are met:
+
+- the source network is IMS;
+- the target network supports emergency calls;
+- the user is moving out of coverage;
+
+- the source and target network belong to the same operator;
+- the target network supports voice call continuity.
+
+## 21.6 Charging
+
+It shall be possible to indicate in the charging information that a VCC event has occurred (e.g., so that appropriate ratings can be applied for the CS and IMS parts of the continued voice call).
+
+## 21.7 VCC Activation
+
+It shall be possible to activate VCC based on operator policies, taking into account any of the following:
+
+- Radio conditions e.g. radio quality thresholds and related hysteresis
+- Coverage availability e.g.: Always prefer I-WLAN, if certain SSID are available
+
+# --- 22 IMS Centralized Services
+
+## 22.1 General
+
+The ICS user shall receive both registered and unregistered services in a consistent manner when the user accesses IMS either via the CS or the PS domain (both of which can be supported by 3GPP access networks or non-3GPP access networks). Support of UEs enhanced with ICS capability as well as UEs without ICS capability shall be possible.
+
+NOTE: The impacts to support non-3GPP CS domains to support of ICS are outside the scope of 3GPP.
+
+## 22.2 Service Consistency
+
+Subscribers shall have a consistent user experience regardless of the domain used, subject to the constraints of the UE and access network.
+
+## 22.3 Service Continuity
+
+ICS shall support service continuity between CS and PS domains (both of which can be supported by 3GPP access networks or non-3GPP access networks), subject to the constraints of the UE and access networks.
+
+Note : The impacts to support non 3GPP CS domains are outside the scope of 3GPP.
+
+The service continuity shall include:
+
+- Basic services
+- Non mid-call services
+- Mid-call services
+
+The support of service continuity for fax and data (CS) media components is not required.
+
+## 22.4 IMS Services
+
+The set of IMS services supported by ICS shall include at least the following, subject to the constraints of the UE and access networks:
+
+- IMS Multimedia Telephony services, including:
+ - speech,
+ - video,
+ - fax,
+ - data (CS),
+ - Supplementary services defined within [40]; and
+ - Multimedia priority service.
+- IMS emergency calls, including eCall.
+
+NOTE: Other IMS hosted services supported by an operator or 3rd party may be supported.
+
+## 22.5 Roaming Support
+
+An ICS user shall be able to receive full ICS support from the HPLMN while roaming in the VPLMN, subject to the constraints of the VPLMN (e.g. roaming agreements, operator policies).
+
+The Home operator shall be able to control if the UE enhanced with ICS capability shall act without ICS capability while roaming.
+
+# --- 23 CS IP interconnection requirements
+
+## 23.1 Introduction
+
+CS IP interconnect represents the interconnection of MSC Server functionality between 2 CS networks over an underlying IP infrastructure.
+
+## 23.2 IP interconnect
+
+The IP connection used for CS IP interconnect shall be generic such that it can support all combinations of core network interconnection. E.g. the IP interconnection shall be shared between the IMS interconnection and the CS IP interconnection.
+
+It shall be possible to handle the inter-connection of all services over this generic IP interface. The handling of security and charging shall also be generic for all IP interconnect scenarios.
+
+## 23.3 MSC server interconnect
+
+The following requirements apply at the interconnection point when two PLMNs are interconnected by means of IP transport technology for 2G and 3G CS services.
+
+The system shall support the capability for CS service interoperability and interworking.
+
+It shall be possible to apply operator defined policy at the interconnection point.
+
+The system shall support the capability to control the session resources when two different network domains are connected that may have, for example, different IP addressing schemes.
+
+The system shall support IP inter-connection between core networks either by direct connection or by using an intermediate carrier (e.g. GSMA IPX [43]).
+
+The system shall support both bilateral interconnection between two carriers and multilateral interconnection (e.g. GSMA IPX [43]) by means of intermediate carrier.
+
+The system shall support either
+
+- transparent relay of the IP signalling and traffic;
+- service aware interconnection
+
+The system shall support codec negotiation across one or multiple interconnects to minimise transcoding (and preferably eliminate it) to provide the highest quality service to the user.
+
+# 24 Service Alignment & Migration
+
+## 24.1 Introduction
+
+Services can be offered to the users via different service domains, e.g. certain teleservices and supplementary services via CS or Multimedia Telephony and supplementary services via IMS. Especially for the supplementary services given below a strong relationship exists from the user's point of view. Therefore means shall be provided to enable a consistent user experience when changing from one service domain to the other.
+
+The requirements in this clause are applicable during the migration to an ICS. The ability to synchronise the service settings will facilitate the migration from a CS to an IMS based network and will allow network operators maximum flexibility in their migration strategies.
+
+## 24.2 Alignment of supplementary services settings
+
+Based on user preferences and if provisioned by the home operator the network shall automatically synchronise the parameter settings of the supplementary services listed in the following table:
+
+**Table 24.2-1: Alignment of supplementary services settings**
+
+| CS Voice (TS11)
Supplementary Services | Equivalent Multimedia
Telephony Services in
IMS domain | Service Behaviour Required |
+|-------------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CLIP/CLIR | OIP/OIR | Consistency of presentation |
+| CoLP/CoLR | TIP/TIR | Consistency of presentation |
+| CNAP | OIP/OIR | Consistency of presentation |
+| Call Forwarding | CDIV | Call forwarding/CDIV shall work consistently no matter which domain the user is in. The settings (e.g. forwarding numbers) shall remain the same across domains for all the parts of the service for which there is an equivalent. |
+| Call Waiting | Communication Waiting | The busy state of the user shall be available to both domains so that this can be applied no matter from which domain an incoming call/communication originates. The activation status of Call Waiting and Communication Waiting shall be synchronised. |
+| Call Hold | Communication HOLD | Any calls held in one domain shall remain held on moving to a different domain. It shall be possible to re-establish a call that was put on hold in another domain. |
+| Multiparty | CONF | Any conference (multiparty) calls set up in one domain shall remain in force if any user moves to another domain. |
+| Closed User Group | Closed User Group | Consistency required across domains |
+| CCBS | CCBS | Consistency required across domains |
+| Call Deflection | Defined in CDIV | Consistency required across domains |
+| Explicit Call Transfer | ECommT | Consistency required across domains. The UE state (i.e. if busy or not) shall be available in both domains to ensure that this can be applied consistently. |
+| Call Barring | Communication Barring | Call/ Communication Barring shall work consistently no matter which domain the user is in. The settings (i.e. barred numbers) shall remain the same across domains. |
+| AoC | AoC | Consistent support across domains. If the user moves from one domain to the other during the communication, the AoC shall indicate the correct charge for the total duration of the communication. |
+
+The operator shall be able to provision the user with the possibility to define which of the above settings shall be synchronised automatically and which settings can exist independently of each other. E.g. a user might decide that the activation status of CLIP/OIP, CLIR/OIR, Call Waiting/Communication Waiting etc. is synchronised but that the call forwarding status and forwarded-to-number is different from the communication diversion settings and the diverted-to-party address.
+
+If the synchronisation of supplementary services, which use the UE's busy state for invocation, is activated the busy state of the UE shall be available in both domains.
+
+NOTE: The "user not reachable" or "user not logged in" conditions in the different domains are independent of each other. This means, e.g. not being registered in the IMS does not affect the invocation of CFNRc in the CS domain.
+
+Synchronisation of settings means that the most recent changes which have been applied in one domain are propagated to the other domain.
+
+There are certain circumstances under which the synchronisation will fail e.g. when a user inserts a SIP URI as diverted-to-party address in the IMS domain which has no Tel URI associated with it. In such a case there is no valid setting for the CS domain for this particular parameter and therefore the CS domain service setting shall remain unchanged. The user may receive a notification about the failure of the synchronisation procedure and its cause.
+
+# --- 25 System optimisation for communication with specific characteristics
+
+## 25.1 Void
+
+## 25.2 Numbering Resource Efficiency
+
+The following optional requirement is intended to provide better numbering resource efficiency for UEs that only require packet switched services.
+
+- A network operator shall be able to provide PS only subscriptions with or without assigning an MSISDN.
+- Remote triggering shall be supported with or without assigning an MSISDN.
+- Remote UE configuration shall be supported without the use of an MSISDN.
+
+Note 1: Current remote UE configuration solutions (i.e. Device Management and Over-the-Air configuration) are mainly based on SMS, which assumes the use of MSISDNs.
+
+Note 2: The requirements in this sub-clause apply to server-to-UE communication scenarios only.
+
+## 25.3 Network provided destination for uplink data
+
+The Network Provided Destination for Uplink Data feature is intended for use when all data from a UE is to be directed to a network provided destination address.
+
+- For uplink data communication, the network shall be able to direct all uplink PS data traffic to a network provided destination address.
+
+NOTE: This feature may be used, for example, when all data from an electricity meter is sent to a server maintained by the network operator.
+
+## 25.4 PS only subscriptions
+
+The system shall support subscriptions that only allow packet-based services and SMS.
+
+# --- 26 Single Sign-On (SSO) Service
+
+## 26.1 Requirements
+
+### 26.1.1 Requirements for the UE
+
+An SSO-capable UE shall support 3GPP SSO Authentication, without user intervention, based on Operator-controlled credentials.
+
+An SSO-capable UE shall be able to initiate the SSO Service regardless of the access network technologies supported by the UE.
+
+An SSO-capable UE that supports 3GPP access and non-3GPP access shall support transparency of the SSO Service from a user perspective during transitions between 3GPP access and non-3GPP access, whether or not the transition occurs during a data application session.
+
+An SSO-capable UE may support a request for SSO Local User Authentication from a Data Application Provider or an Identity Provider to confirm the presence of the registered user of the data application.
+
+### 26.1.2 Requirements for a 3GPP SSO Service
+
+The 3GPP SSO Service shall provide secure, seamless and transparent access to data applications for users of the SSO Service independent of the access network technology.
+
+The 3GPP SSO Service shall be able to interwork with Identity Management (IdM) specifications (e.g., OpenID [51]).
+
+The 3GPP SSO Service shall support 3GPP SSO Authentication based on Operator-controlled credentials and policies.
+
+The 3GPP SSO Service may support negotiation and use of an agreed authentication method between the UE and the 3GPP SSO Identity Provider. The negotiation of an authentication method may be repeated each time the user accesses a DAP's service.
+
+The 3GPP SSO Service may support mechanisms to ensure the presence of the registered user of the data application to satisfy policies of the Data Application Provider.
+
+The 3GPP SSO Service shall be transparent from a user perspective when transitions occur between 3GPP access and non-3GPP access, whether or not the transition occurs during a data application session.
+
+The 3GPP SSO Service shall be transparent from a user perspective when the user accesses a data application using an identity created through a 3rd Party SSO Identity Provider. The user shall be able to configure which 3rd party SSO identities are used with the 3GPP SSO Service.
+
+# --- 26a User Identity
+
+## 26a.1 Introduction
+
+Identifying distinguished user identities of the user (provided by some external party or by the operator) in the operator network enables an operator to provide an enhanced user experience and optimized performance as well as to offer services to devices that are not part of a 3GPP network. The user to be identified could be an individual human user, using a UE with a certain subscription, or an application running on or connecting via a UE, or a device (“thing”) behind a gateway UE.
+
+Network settings can be adapted and services offered to users according to their needs, independent of the subscription that is used to establish the connection. By acting as an identity provider, the operator can take additional information from the network into account to provide a higher level of security for the authentication of a user.
+
+NOTE: The basic concept and relations of user identity management is described in TR 22.904 [61].
+
+## 26a.2 Requirements
+
+### 26a.2.1 User Identifiers and user authentication
+
+The 3GPP system shall be able to provide User Identities with related User Identifiers for a user.
+
+The User Identifier shall be independent of existing identifiers relating to subscription or device (e.g. IMSI, MSISDN, IMPI, IMPU, SUPI, GPSI, IMEI) and of other User Identifiers.
+
+The User Identifier may be provided by some entity within the operator's network or by a 3rd party.
+
+The 3GPP system shall support to interwork with a 3rd party network entity for authentication of the User Identity.
+
+The 3GPP system shall support to perform authentication of a User Identity regardless of the user's access, the user's UE and its HPLMN as well as the provider of the User Identifier.
+
+The 3GPP network shall be able to provide a User Identifier for a non-3GPP device that is connected to the network via a UE that acts as a gateway.
+
+The 3GPP network shall support to perform authentication of a User Identity used by devices that are connected via a UE that acts as a gateway.
+
+The 3GPP system shall be able to take User Identity specific service settings and parameters into account when delivering a service.
+
+A subscriber shall be able to link and unlink one or more user Identities with his 3GPP subscription.
+
+The 3GPP system shall support user authentication with User Identifiers from devices that connect via the internet; the 3GPP system shall support secure provisioning of credentials to those devices to enable them to access the network and its services according to the 3GPP subscription that has been linked with the User Identity.
+
+The 3GPP system shall support secure provisioning of credentials to a non-3GPP device connected via a gateway UE, whose User Identifier has been linked with the 3GPP subscription of the gateway UE, to enable the non-3GPP device to access the network and its services according to the linked 3GPP subscription when connected via non-3GPP access.
+
+The 3GPP system shall be able to assess the level of confidence in the User Identity by taking into account information regarding the used mechanism for obtaining that User Identity (e.g. algorithms, key-length, time since last authentication), information from the network (e.g. UE or device in use, access technology, location).
+
+The operator and the subscriber shall be able to restrict the number of simultaneously active User Identifiers per UE.
+
+### 26a.2.2 Access to services
+
+The 3GPP System shall support to authenticate a User Identity to a service with a User Identifier.
+
+NOTE: The requirement applies to 3GPP services and non-3GPP services that are accessed via the 3GPP System
+
+The 3GPP system shall be able to provide information to services concerning the level of confidence of the User Identity and authentication process.
+
+A service shall be able to request the 3GPP network to only authenticate users to the service for which the association of the user with a User Identifier has been established according to specified authentication policies of the service.
+
+When a user requests to access a service the 3GPP System shall support authentication of the User Identity with a User Identifier towards the service if the level of confidence for the correct association of a User Identity with a User Identifier complies to specified policies of the service.
+
+The 3GPP network shall be able to take the User Profile into account when assigning a UE to a network slice, moving a UE from one network slice to another, and removing a UE from a network slice.
+
+The 3GPP system shall support to allow a UE access to a slice based on successful User Identity authentication.
+
+The 3GPP system shall support to deny a UE access to a slice based on unsuccessful User Identity authentication.
+
+### 26a.2.3 User Identity Profile and its User Identities
+
+The 3GPP system shall be able to store and update a User Profile for a user.
+
+The User Profile shall include a User Identifier.
+
+The User Profile may include one or more pieces of the following information:
+
+- additional User Identifiers of the user's User Identities and potentially linked 3GPP subscriptions,
+- used UEs (identified by their subscription and device identifiers),
+- capabilities the used UEs support for authentication,
+- information regarding authentication policies required by different services and slices to authenticate a user for access to these services or slices.
+- User Identity specific service settings and parameters.
+Those shall include network parameters (e.g. QoS parameters), IMS service (e.g. MMTEL supplementary services) and operator deployed service chain settings.
+- User Identity specific network resources (e.g., network slice).
+
+The user shall be able to activate, deactivate and suspend, i.e. temporarily deactivate, the use of the User Identifiers per device or UE and the associated settings in its user profile.
+
+Note 1: Suspending (temporarily deactivating) a User Identifier on a UE could also be automatically performed by the device on behalf of the user after a period of inactivity of the user at that device. The time period of inactivity of the user at that device after which a device should suspend a User Identifier may depend on home operator policy.
+
+Note 2: Re-activation of a suspended User Identifier on a UE where it was suspended could involve simplified authentication (e.g. using fingerprint) at the device.
+
+Subject to operator policy the 3GPP system shall be able to update User Profile related to a User Identifier, according to the information shared by a trusted 3rd party.
+
+### 26a.2.4 Operator requirements
+
+The operator shall be able to enable or disable the use of a User Identifier in his network.
+
+The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services
+
+The operator shall be able to set the boundaries within which the user specific settings are taken into account in his network. The operator shall be able to restrict the feature depending of the provider of the User Identifier, the roaming status of the UE, the service and its specific parameters.
+
+The operator shall be able to set restrictions for devices accessing the network and its services via non-3GPP access with their User Identity linked to a 3GPP subscription. The 3GPP system shall support restrictions based on the User Identity provider, the roaming status of the linked 3GPP subscription, and the network service that is accessed.
+
+The 3GPP system shall be able to support automatically suspending an active User Identity after a certain period of time of user inactivity, e.g. up to one hour, as configured by the operator.
+
+The 3GPP system shall be able to support a fast re-activation for a suspended User Identity, based on MNOs' configuration.
+
+The 3GPP system shall enable a user to configure, within the boundaries set by the network operator, which services shall be available on a device where a user logs in. These services include voice, video, and messaging.
+
+#### 26a.2.5 Privacy requirements
+
+The 3GPP system shall protect the privacy of the user by transferring to a service only User Identity information that is necessary to provide the service and for which the user has consented to when registering for the service.
+
+# --- 27 User plane congestion management
+
+## 27.1 Introduction
+
+RAN user plane congestion, in the context of this clause, is considered to be downlink congestion that affects the user plane, which may last for a few seconds, a few minutes, or a few hours due to arrival of new active users, increase of communication intensity of existing users, the radio environment changing, the mobile user changing location, and other reasons, thus causing the capacity of RAN resources to transfer user data to be exceeded. A short-duration burst of user plane traffic should not be identified as RAN congestion.
+
+## 27.2 General
+
+- a) The network shall be able to detect RAN user plane congestion onset and abatement. Mechanisms to cope with RAN user plane congestions should be resilient to rapid changes in the level of congestion.
+- b) The network shall be able to identify whether or not an active UE is in a RAN user plane congested cell.
+- c) The network operator shall be able to configure or provision and enforce policy rules to best deal with RAN user plane congestion.
+- d) The system should react in a timely manner to manage a RAN user plane congestion situation, i.e. that the measures taken become effective to promptly help resolve the RAN user plane congestion.
+- e) The signalling overhead caused by RAN user plane congestion management solutions in the system shall be minimized.
+- f) The network shall be able to take into consideration the RAN user plane congestion status and the subscriber's profile when coping with traffic congestion.
+
+## 27.3 Prioritizing traffic
+
+- a) According to operator policy, during RAN user plane congestion the operator shall be able to select the communications which require preferential treatment and allocate sufficient resources for such communications in order to provide these services with appropriate service quality.
+- b) According to operator policy, the network shall be able to select specific users (e.g. heavy users, roaming users, etc.) and adjust the QoS of existing connections/flows and apply relevant policies to new connections/flows depending on the RAN user plane congestion status and the subscriber's profile.
+
+Note 1: Preferably, connections/flows need to be adjusted such that the user experience is not negatively affected.
+
+## 27.4 Reducing traffic
+
+- a) Based on RAN congestion status and according to operator policy, the network shall be able to reduce the user plane traffic load (e.g. by compressing images or by adaptation for streaming applications) taking into account UE related information (e.g. UE capabilities, subscription).
+- b) The system shall be able to adjust the communication media parameters of real-time communications so that they consume less bandwidth.
+
+## 27.5 Void
+
+# --- 28 RAN Sharing Enhancements
+
+## 28.1 General
+
+RAN Sharing Enhancements allow multiple Participating Operators to share the resources of a single RAN according to agreed allocation schemes. The Shared RAN is provided by a Hosting RAN Operator which can be one of the Participating Operators.
+
+The Shared RAN can be GERAN, UTRAN, E-UTRAN or NG-RAN as described below.
+
+All the following requirements shall be subject to Hosting RAN Operator configuration.
+
+## 28.2 Specific E-UTRAN and NG-RAN Sharing requirements
+
+### 28.2.1 Allocation of Shared E-UTRAN and NG-RAN resources
+
+When E-UTRAN and NG-RAN resources are shared they can be allocated unequally to the Participating Operators, depending on the planned or current needs of these operators and based on service agreements with the Hosting E-UTRAN/NG-RAN Operator.
+
+The following requirements apply:
+
+The Hosting E-UTRAN/NG-RAN Operator shall be able to specify the allocation of E-UTRAN/NG-RAN resources to each of the Participating Operators by the following:
+
+- a) static allocation, i.e. guaranteeing a minimum allocation and limiting to a maximum allocation,
+- b) static allocation for a specified period of time and/or specific cells/sectors,
+- c) first UE come first UE served allocation.
+- d) the type and number of 5G slices
+
+Resources include both user plane and signalling plane. The Hosting E-UTRAN/NG-RAN Operator needs to be able to manage the sharing of the signalling traffic independently from that of the user traffic because signalling traffic and user traffic are not always directly related. For example for MTC devices, the signalling traffic volume can be high and the user traffic volume low whereas for downloading video, the signalling traffic is low and the user traffic is high.
+
+The following requirements apply:
+
+The management and allocation of resources of signalling traffic over the Shared E-UTRAN/NG-RAN shall be independent from the management and allocation of resources of the user traffic over the Shared E-UTRAN.
+
+A Shared E-UTRAN/NG-RAN shall be capable of differentiating traffic associated with individual Participating Operators.
+
+A Shared E-UTRAN/NG-RAN shall be able to conduct admission control based on the allocated E-UTRAN/NG-RAN resources for each Participating Operator.
+
+A Hosting E-UTRAN/NG-RAN Operator shall be able to control resource usage taking into account the allocated E-UTRAN/NG-RAN resources for each Participating Operator. A means of monitoring the usage of resources shall be provided.
+
+All shared E-UTRAN/NG-RAN capabilities offered by the Hosting E-UTRAN/NG-RAN Operator shall be individually available for use by each Participating Operator where this is possible.
+
+The 3GPP System shall support a Shared RAN (E-UTRAN or NG-RAN) to cover a specific coverage area (e.g. from a complete network to a single cell, both outdoor and indoor).
+
+The 3GPP System shall support service continuity for UEs that are moving between different Shared RANs or between a Shared RAN and a non-shared RAN.
+
+## 28.2.2 OA&M Access to the Shared E-UTRAN/NG-RAN
+
+Each Participating Operator can have their own OA&M capabilities, which are used for monitoring and for selected operations in a shared E-UTRAN/NG-RAN. Information exchange involved in those operations need to be controlled by the Hosting E-UTRAN/NG-RAN Operator as to prevent disclosing them to other Participating Operators, be it for business, operational, or technical reasons.
+
+The following requirements apply:
+
+Selected OA&M capabilities for the Shared E-UTRAN/NG-RAN, under the control of the Hosting E-UTRAN Operator, shall be accessible by the Participating Operator's OA&M functions
+
+This would allow, for example, the Participating Operator to do the following:
+
+- test of communication path between the Participating Operator's network elements and the Shared E-UTRAN/NG-RAN,
+- obtain fault reports,
+- retrieve RAN resource usage information.
+
+## 28.2.3 Generation and retrieval of usage and accounting information
+
+To facilitate interoperator accounting between Hosting E-UTRAN/NG-RAN Operator and Participating Operator the Hosting E-UTRAN/NG-RAN Operator needs to record E-UTRAN/NG-RAN resource usage by UEs of the Participating Operator.
+
+The following requirements apply:
+
+A Hosting E-UTRAN/NG-RAN Operator shall be able to collect events supporting the accounting of network resource usage separately for each Participating Operator. Collected events may be delivered to the subscriber's Participating Operator. This includes:
+
+- start of service in the Shared E-UTRAN/NG-RAN for a UE of the Participating Operator,
+- end of service in the Shared E-UTRAN/NG-RAN for a UE of the Participating Operator.
+
+## 28.2.4 MDT Collection
+
+MDT data from a Participating Operator's customer UEs allow the Hosting E-UTRAN/NG-RAN Operator to be provided with performance measurements on his Shared E-UTRAN/NG-RAN. The Participating Operator is responsible for obtaining and retaining any required user consent related to privacy.
+
+The following requirements apply:
+
+When authorized by the Participating Operators, the Hosting E-UTRAN/NG-RAN Operator shall be able to collect MDT data of the Participating Operator's UEs connected through its E-UTRAN/NG-RAN.
+
+- NOTE: This functionality should also allow for the case where the Hosting E-UTRAN/NG-RAN Operator does not have an adjunct core network.
+
+## 28.2.5 PWS support of Shared E-UTRAN/NG-RAN
+
+A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of E-UTRAN/NG-RAN Sharing.
+
+The following requirements apply:
+
+The Shared E-UTRAN/NG-RAN shall be able to broadcast PWS messages originated from the core networks of all Participating Operators.
+
+NOTE: Rel-11 design requires a shared PWS core. However, some regulatory obligations require a solution in which no common PWS core network entity is involved.
+
+## 28.2.6 Support for load balancing
+
+Hosting E-UTRAN/NG-RAN Operators have the need to optimize E-UTRAN/NG-RAN resource usage within the shared E-UTRAN/NG-RAN for a particular coverage area. At the same time, the agreed shares of E-UTRAN/NG-RAN resources based on a single cell and sector for each Participating Operator need to be respected. Likewise, Participating Operators have the need to optimize their E-UTRAN/NG-RAN resource usage among shared and unshared E-UTRAN/NG-RAN for a particular coverage area.
+
+The capability to perform load balancing on an individual Participating Operator's traffic basis within a shared E-UTRAN/NG-RAN shall be supported.
+
+The capability to perform load balancing on the combined traffic of all the Participating Operators within a shared E-UTRAN/NG-RAN shall be supported.
+
+The capability to perform load balancing between an individual Participating Operator's traffic within a shared E-UTRAN/NG-RAN and traffic in that Participating Operator's unshared E-UTRAN/NG-RAN where the shared and unshared E-UTRAN/NG-RAN coverage overlaps shall be supported.
+
+NOTE: Load balancing capabilities are expected to take into account the allocation of resources to each Participating Operator and the load level for each Participating Operator to the extent possible, so that the principal objective to maximize throughput is not impacted.
+
+If load balancing in a Shared E-UTRAN/NG-RAN is supported and if a Participating Operator's EPC indicates overload to the Shared E-UTRAN/NG-RAN in order to mitigate the overload situation then overload mitigation measures shall have minimal impact on the communication between the Shared E-UTRAN/NG-RAN and other Participating Operators EPCs.
+
+## 28.2.7 Dynamic capacity negotiation
+
+In situations where a need for additional, unplanned, E-UTRAN/NG-RAN capacity by a Participating Operator arises (e.g. in the case of big mass-events) the Shared E-UTRAN/NG-RAN can provide means to allocate available spare capacity to the Participating Operator. Based on service level agreement between the Hosting and Participating operator such allocation can be automated without human intervention.
+
+The following requirements apply:
+
+The Participating Operator shall be able to query and request spare capacity of the Shared E-UTRAN/NG-RAN, based on policies and without human intervention.
+
+The Shared E-UTRAN/NG-RAN shall be able to allocate spare capacity to Participating Operator, based on policies and without human intervention.
+
+# 28.3 Specific GERAN & UTRAN Sharing Requirements
+
+## 28.3.1 Allocation of Shared GERAN or UTRAN Resources
+
+When GERAN or UTRAN resources are shared they can be allocated unequally to the Participating Operators, depending on the planned or current needs of these operators and based on service agreements with the Hosting RAN Operator.
+
+The following requirements apply:
+
+The Hosting RAN Operator shall be able to specify the allocation of GERAN or UTRAN resources to each of the Participating Operators by the following:
+
+- a) static allocation, i.e. guaranteeing a minimum allocation and limiting to a maximum allocation,
+- b) static allocation for a specified period of time and/or specific cells/sectors,
+
+- c) first UE come first UE served allocation.
+
+The management and allocation of resources of signalling traffic over the Shared GERAN or UTRAN shall be independent from the management and allocation of resources of the user traffic over the Shared GERAN or UTRAN.
+
+A Shared GERAN or UTRAN shall be capable of differentiating traffic associated with individual Participating Operators and shall be able to limit QoS available for traffic of the UEs of a Participating Operator (e.g. "best effort" if not enough resources are available).
+
+A Shared GERAN or UTRAN shall be able to conduct admission control based on the allocated GERAN or UTRAN resources for each Participating Operator with a margin of tolerance.
+
+A Hosting RAN Operator shall be able to control resource usage taking into account the allocated GERAN or UTRAN resources for each Participating Operator. A means of monitoring the usage of resources shall be provided.
+
+All Shared GERAN or UTRAN capabilities offered by the Hosting RAN Operator shall be individually available for use by each Participating Operator where this is possible.
+
+A Hosting RAN shall be able to provide an indication to each Participating Operator of how much capacity they are allocated at any one time. Signalling and User traffic shall be separately identified.
+
+The ability to allow a single RAN (GERAN or UTRAN) to be fully shared by a number of Participating Operators shall be provided.
+
+## 28.3.2 OA&M Access to the Shared GERAN or UTRAN
+
+Each Participating Operator can have their own OA&M capabilities, which are used for monitoring and for selected operations in a Shared GERAN or UTRAN. Information exchange involved in those operations need to be controlled by the Hosting RAN Operator so as to prevent disclosing them to other Participating Operators, be it for business, operational, or technical reasons.
+
+The following requirements apply:
+
+Selected OA&M capabilities for the Shared GERAN or UTRAN, under the control of the Hosting RAN Operator, shall be accessible by the Participating Operator's OA&M functions
+
+This would allow, for example, the Participating Operator to do the following:
+
+- test of communication path between the Participating Operator's network elements and the Shared GERAN or UTRAN,
+- obtain fault reports,
+- retrieve GERAN or UTRAN resource usage information.
+
+## 28.3.3 Generation and retrieval of usage and accounting information
+
+To facilitate inter-operator accounting between the Hosting RAN Operator and the Participating Operator, the Hosting RAN Operator needs to record GERAN or UTRAN resource usage by UEs of the Participating Operator.
+
+The following requirements apply:
+
+A Hosting RAN Operator shall be able to collect events supporting the accounting of network resource usage separately for each Participating Operator. Collected events may be delivered to the subscriber's Participating Operator. This includes:
+
+- start of service in the Shared GERAN or UTRAN for a UE of the Participating Operator,
+- end of service in the Shared GERAN or UTRAN for a UE of the Participating Operator.
+
+### 28.3.4 MDT Collection
+
+MDT data from a Participating Operator's customer UEs allow the Hosting RAN Operator to be provided with performance measurements on his Shared GERAN or UTRAN. The Participating Operator is responsible for obtaining and retaining any required user consent related to privacy.
+
+The following requirements apply:
+
+When authorized by the Participating Operators, the Hosting RAN Operator shall be able to collect MDT data of the Participating Operator's UEs connected through its GERAN or UTRAN.
+
+The Participating Operators shall be able to retrieve this data for their own subscribers from the Hosting RAN Operator.
+
+NOTE: This functionality should also allow for the case where the Hosting RAN Operator does not have an adjunct core network.
+
+### 28.3.5 PWS support of Shared GERAN or UTRAN
+
+A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of GERAN or UTRAN Sharing.
+
+The following requirements apply:
+
+The Shared GERAN or UTRAN shall be able to broadcast PWS.
+
+NOTE: The Hosting RAN Operator is responsible for the delivery of PWS messages to the UEs.
+
+### 28.3.6 Support for load balancing
+
+Hosting RAN Operators need to optimise GERAN or UTRAN resource usage within the Shared GERAN or UTRAN for a particular coverage area while respecting the agreed resource shares for each Participating Operator. Similarly, Participating Operators need to optimise their GERAN or UTRAN resource usage between Shared and unshared GERAN or UTRAN for a particular coverage area.
+
+The Hosting RAN Operator shall have the capability to balance the Signalling and User Traffic load individually for each Participating Operator within a Shared GERAN or UTRAN.
+
+The capability to perform load balancing on the combined traffic of all the Participating Operators within a Shared GERAN or UTRAN shall be provided. The agreed shares of GERAN or UTRAN resources shall be maintained. Signalling and User traffic shall be managed independently.
+
+The capability to perform load balancing between an individual Participating Operator's traffic within a Shared GERAN or UTRAN and traffic in that Participating Operator's unshared GERAN or UTRAN where the Shared and unshared GERAN or UTRAN coverage overlaps shall be supported.
+
+The Hosting RAN Operator shall be able to balance the load across all Participating Operators.
+
+### 28.3.7 Dynamic capacity negotiation
+
+The Participating Operator shall be able to request on-demand spare capacity of the Shared GERAN or UTRAN based on policies and without human intervention.
+
+The Hosting RAN Operator shall be able to allocate spare on-demand capacity on the Shared GERAN or UTRAN to a Participating Operator, based on policies and without human intervention.
+
+The Participating Operator shall be able to request the cancellation of granted on-demand capacity requests.
+
+The Hosting RAN Operator shall be able to cancel a granted request based on a Participating Operator's request or based on agreed policy.
+
+The Hosting RAN Operator shall be able to change the amount shared by each Participating Operator based on traffic demand. A minimum capacity (that can be set) of the Hosting RAN shall be reserved for each Participating Operator that cannot be allocated to other Participating Operators.
+
+## 29 Service exposure with 3rd party service providers
+
+### 29.1 General
+
+The intention of service exposure is that, under the assumption of a service agreement between MNO and a 3rd party, the 3GPP Network allows a 3rd party service provider to benefit from network provided services and capabilities that are exposed by the PLMN. For example the 3GPP Core Network can exchange information with the 3rd party to optimize usage and management of 3GPP resources. A standardized exposure of network services/capabilities reduces the complexity of different 3rd parties to access different 3GPP network services and capabilities.
+
+General requirements for service exposure with 3rd party service providers:
+
+- The operator shall be able to provide to a 3rd party service provider secure and chargeable access to the exposed services/capabilities i.e. to authenticate, authorize and charge the 3rd party entities.
+
+NOTE 1: This requirement can be implemented by the existing standardised API frameworks e.g. the OMA API framework.
+
+- It shall be ensured that the 3GPP services/capabilities are not disclosed to unauthorised parties and that user privacy (avoid e.g. trackable and traceable identity information of the concerned UE) is maintained subject to user agreement, operator policy, service agreement between operator and 3rd party and regulation constraints.
+- The network service/capability exposure should be generic enough to support different application needs. Exposed 3GPP services/capabilities may use functionalities from different network entities and different 3GPP interfaces
+
+### 29.2 Exposed Services and capabilities
+
+The 3GPP Core Network shall be able provide a standardized interface to enable exposure of the following services and capabilities to 3rd party service providers:
+
+Support of 3rd party requested MTC Device triggering
+
+- The 3GPP Core Network shall support a 3rd party service provider request to trigger a UE that is served by the 3rd party service provider, the request shall include:
+ - a trigger payload, to provide information to the application on the UE to e.g. trigger application related actions,
+ - a validity period.
+
+NOTE 1: The 3GPP Network will attempt to deliver the trigger message to the UE until the validity period expires.
+
+- The 3GPP Core Network shall support the 3rd party service provider to recall or replace a trigger message that it has previously submitted.
+
+NOTE 2: The goal of device triggering is that the UE takes action based on the content of the trigger payload. This response can involve initiation of communication with an MTC Server of the 3rd party service provider. The UE can initiate communication immediately or later within the validity period.
+
+Support of 3rd party interaction for 3GPP resource management for background data transfer:
+
+- The 3GPP Core Network shall support a 3rd party service provider request for background data transfer for a set of UEs that are served by the 3rd party service provider, indicating:
+ - the desired time window for the data transfer,
+ - the volume of the data expected to be transferred in a geographic area TS 23.032 [56].
+- Additionally, the 3rd party application server shall be able to indicate to the 3GPP System when the background data transfer (a) exceeds the agreed maximum data volume or (b) continues beyond the agreed time window or
+
+(c) happens outside the agreed areas – e.g. due to movement of individual UEs, whether this background data transfer:
+
+- shall be stopped by the 3GPP System or
+- shall continue, possibly under a different charging regime.
+- The 3GPP Core Network shall be able to inform the 3rd party service provider in one coordinated response, based on locally available information (e.g. congestion level) over the geographic area, about:
+ - one or more recommended time windows for the data transfer and
+ - for each time window the maximum aggregated bitrate for the set of UEs in the geographical area indicated by the 3rd party service provider.
+- Additionally, the 3GPP Core Network shall be able to inform the 3rd party service provider about the charging policy that will be applied to the 3rd party service provider if the data are transferred within the recommended time window and if transmission rates stay below the limits of the respective maximum aggregated bitrate.
+- The goal of providing the time window is to favour transfer of more traffic during non-busy hours and reason for providing the maximum aggregate bitrate is to spread out traffic during that time. The goal of multiple time windows is to allow the 3rd party provider to choose one appropriate time window based on its preference like the expected charging regime and bitrate.
+
+Support of 3rd party interaction on information for predictable communication patterns of a UE:
+
+- The 3GPP Core Network shall enable a 3rd party service provider to provide information about predictable communication patterns of individual UEs or groups of UEs that are served by this 3rd party service provider. Such communication patterns may include:
+ - Time and traffic volume related patterns (e.g. repeating communication initiation intervals, desired 'keep alive' time of data sessions, average/maximum volume per data transmission, etc.).
+ - Location and Mobility related patterns (e.g. indication of stationary UEs, predictable trajectories of UEs, etc.).
+- This information may be used by the 3GPP system to optimize resource usage.
+
+Support of 3rd party requested session QoS and priority
+
+- The 3GPP Core Network shall enable a 3rd party service provider to request setting up data sessions with specified QoS (e.g. low latency or jitter) and priority handling to a UE that is served by the 3rd party service provider.
+
+Support of 3rd party requested broadcast
+
+- The 3GPP Core Network shall enable a 3rd party service provider to request sending a broadcast message in a specified geographic area (as specified in TS 22.368 [52]) expecting to reach a group of devices that are served by the 3rd party service provider.
+
+Informing the 3rd party about potential network issues
+
+- The 3GPP Core Network shall be able to indicate to a 3rd party service provider when data transmissions have a risk of incapability to provide expected throughput and/or QoS in a specific area (e.g. due to forecasted high traffic load in that area). Additionally, an estimate may be given when the high traffic load is expected to be mitigated.
+
+Informing the 3rd party about UE status
+
+- The 3GPP Core Network shall be able to provide the following information about a UE that is served by the 3rd party service provider:
+ - Indication of the of the roaming status (i.e. Roaming and No Roaming) and the serving network, when the UE starts/stops roaming,
+ - Loss of connectivity of the UE,
+
+- Change or loss of the association between the ME and the USIM,
+- Communication failure events of the UE visible to the network (e.g. for troubleshooting).
+- Reporting when the UE moves in/out of a geographic area that is indicated by the 3rd party,
+- Reporting when the UE changes Routing Area / Tracking Area / Location Area / Cell.
+- Reporting when the UE changes the status of 3GPP PS Data Off.
+
+NOTE: The area indicated by a 3rd party service provider can be mapped to the area used in the 3GPP network, i.e. a list of LAs/RAs/TAs/cells. The 3rd party service provider can define a geographical area as shapes (e.g. polygons, circles) or civic addresses (streets, districts...) as referenced by OMA Presence API [53] e.g. defined by shape areas of IETF RFC-5491 [54] or by civic addresses defined in IETF RFC-5139 [55].
+
+- The 3rd party service provider shall be able to request a one time reporting or reporting at defined times (e.g. regular intervals, certain pre-defined time points) on the number of UEs present in a certain area and the location of each UE as for a Location Based Service.
+- Subject to user consent, operator policy and regulatory constraints, the user privacy shall be maintained when passing location information to a 3rd party service provider.
+
+Informing the 3rd party about a UE's connection properties
+
+- The 3GPP Core Network shall be able to inform a 3rd party about a UE's connection properties.
+
+NOTE: Connection properties of a UE describe the average data rate range or non-absolute value (e.g. high, medium or low) that the UE is likely to be able to obtain at the current location. The connection properties can, for example, be generated from the UE's RAT type the UE is currently attached to, the load conditions at its current location and/or other parameters.
+
+Support for non-IP small data transfer with a 3rd party
+
+- The 3GPP Core Network shall support a 3rd party for submitting a small amount of non-IP data for delivery to a UE.
+- The 3GPP Core Network shall support a 3rd party application server for receiving a small amount of non-IP data delivered from a UE.
+- The 3GPP Core Network shall support a 3rd party to configuring non-IP data delivery for a particular UE (e.g. destination address, maximum number of messages, duration for which configuration applies).
+
+NOTE: The use of the Non-IP Data Delivery feature via Service Capability Exposure Function assumes that the UE has indicated support for 'non-IP data transfer' and in case the Service Capability Exposure Function is used there will be no user plane EPS bearer established.
+
+---
+
+## 30 Flexible Mobile Service Steering
+
+### 30.1 Introduction
+
+In order to realize efficient and flexible mobile service steering in (S)Gi-LAN, the network operator uses information (e.g. user profile, network operator's policies, RAT type, application characteristics) to define traffic steering policies. These policies are used to steer the subscriber's traffic to appropriate enablers (e.g. NAT, antimalware, parental control, DDoS protection) in the (S)Gi-LAN.
+
+The term (S)Gi-LAN used in the present document represents a system which is out of 3GPP scope. Corresponding term for the 5G network is N6-LAN.
+
+For traffic steering to service functions in 5G network, enhancement beyond the service requirements below are defined in [59].
+
+## 30.2 General Requirements
+
+The following requirements apply:
+
+- The 3GPP Core Network shall be able to define and modify traffic steering policies that are used to steer traffic in (S)Gi-LAN containing operator or 3rd party service functions e.g. to improve e.g. the user's QoE, apply the bandwidth limitation and provide valued added services.
+- Traffic steering policy shall be able to distinguish between upstream and downstream traffic.
+- The 3GPP Core Network shall be able to define different traffic steering policies for a user's traffic on a per session basis (e.g. for applying parental control, anti-malware, DDoS protection, video optimization).
+- The 3GPP Core Network defines traffic steering policies based on one or more pieces of information such as:
+ - network operator's policies
+ - user subscription (e.g. user's priority, the status of optional subscriber services from the subscription data, based on service provider used, subscribed QoS)
+ - user's current RAT
+ - the network (RAN and CN) load status
+ - application characteristics such as: application type (video, web browsing, IM, etc), application protocol ( HTTP, P2P, etc), target address name (URL) and application provider (My tube, etc)
+ - time
+ - UE location
+ - information (e.g. APN) of the destination network (i.e. a PDN or an internal IP network) of traffic flow
+- In case of roaming, the HPLMN shall be able to apply traffic steering policies for home routed traffic.
+
+NOTE: Traffic steering policies for local breakout is not specified.
+
+---
+
+## 31 Control of traffic from UE-based applications toward associated server
+
+### 31.1 Description
+
+This feature is a set of service features that allows operators to control traffic from UEs to an application on a third-party server or the third-party server itself. When an application on a third-party server or the third-party server itself becomes congested or fails the traffic towards that server need to be controlled to avoid/mitigate potential issues caused by resulting unproductive use of 3GPP network resource. This will also make it possible to allow 3GPP network to help third-party servers to handle overload and recover from failures. (see [11])
+
+### 31.2 Requirements
+
+#### 31.2.1 Control requirements
+
+The 3GPP network shall be able to control (i.e. block and/or prioritize) traffic from UEs to an application on a third-party server or the third-party server itself without affecting traffic to other applications on the third-party server or to other third-party servers.
+
+For this purpose, the 3GPP network shall be able to identify the third-party server or the application on the third-party server, and the traffic towards it.
+
+When congestion or failure of the application on the third-party server or the third-party server abates the 3GPP network shall be able to apply this feature in a phased manner to gradually restore traffic according to operator policy.
+
+The 3GPP network shall be able to control traffic through this feature based on:
+
+- (1) the traffic load on the 3GPP network,
+- (2) the MNO policy,
+- (3) the MNO's service subscription profiles such as access class information, and
+- (4) third-party service subscription profiles
+
+without impacting the traffic to other applications on the third-party server or other third-party servers.
+
+#### 31.2.2 Requirements on awareness of third-party server issue
+
+The 3GPP network shall be able to receive a status indication from the third-party server when an application on it is experiencing congestion or failure, and when normal operation resumes. Such a status indication may be sent periodically, and/or when the status of the application changes.
+
+The 3GPP network shall be able to detect and monitor a third-party server's operational status e.g. congestion levels, failure and unavailability of the third-party server.
+
+---
+
+## 32 3GPP enhancement for TV application support
+
+### 32.1 Feature description
+
+3GPP enhancement for TV service support is a feature whereby 3GPP networks can provide unicast and broadcast transport, referred to as “TV transport services”, to support distribution of TV programs. TV transport services can support the three types of TV services – Free-to-air (FTA), Free-to-view (FTV), and Subscribed services. Each type of TV service has different requirements in order to meet regulatory obligations and public service and commercial broadcaster's requirements regarding content distribution, hence many requirements captured below are optional to implement depending on the type of TV transport services an MNO chooses to offer.
+
+## 32.2 Requirements
+
+### 32.2.1 General requirements
+
+The 3GPP network shall be able to support on-demand network capacity assignment for TV services.
+
+The 3GPP system shall allow the MNO to implement a network supporting downlink only broadcasting based on a set of EPS functionalities and entities which are required to offer linear TV services.
+
+The 3GPP network shall be able to support on-demand network broadcast service area coverage management for TV transport services.
+
+The 3GPP network shall support content delivery up to UHD resolution.
+
+The 3GPP network shall allow the MNO to authenticate a subscriber before providing TV transport services via unicast.
+
+The 3GPP network shall allow the MNO to authenticate a subscriber before providing TV transport services via eMBMS broadcast.
+
+The 3GPP network shall enable an MNO to allow a UE to receive TV transport services via eMBMS broadcast without authentication.
+
+The 3GPP network shall be able to provide FTA TV services receivable by UEs subscribed to the MNO and roaming UEs of other MNOs. A UE supporting enhanced TV transport services and in limited service state shall be able to receive eMBMS broadcast TV transport services.
+
+The 3GPP network shall provide the ability for an MNO to meet regulatory requirements for privacy and non-identification of a receiving user by entities outside of the MNO.
+
+NOTE: The MNO is responsible for maintaining the privacy of personal usage data collected as a result of providing access to the TV services.
+
+The 3GPP network shall provide mechanisms to restrict the reception of some or all Subscribed TV services to groups of subscribers (e.g. based on the recipients of the services are subscribers of the MNO, roaming subscribers of other MNOs, or not subscribed to any MNO).
+
+The quality of experience of the TV service shall be independent from the size of the concurrent audience. While receiving TV services in normal service state, subscribers of the MNO and roaming subscribers shall be able to access other subscribed services such as voice, data or SMS.
+
+The 3GPP network shall support combinations of SD, FHD and UHD resolution TV transport services.
+
+The 3GPP network shall allow the MNO to provide a TV service in a resource efficient manner over a large area up to the size of a country.
+
+The 3GPP network shall enable the quality of experience of the TV service to be ensured throughout the coverage area defined for the TV service.
+
+### 32.2.2 Requirement for transmission performance enhancement
+
+The 3GPP system shall be able to support 20Mbps over one logical broadcast channel.
+
+The mechanisms in the 3GPP network shall be designed to support at least 10 high quality video channels of 12Mbps each simultaneously via broadcast.
+
+The 3GPP network shall support flexible change between broadcast and unicast per traffic demand over the same carrier.
+
+The 3GPP network shall be able to convert network unicast capacity to network broadcast capacity and vice versa so that each can range from 0% to 100% of the capacity.
+
+The 3GPP network shall be able to support using one carrier for both unicast and broadcast distribution of TV services.
+
+If allowed by the operator and a spare carrier is available, the 3GPP network shall be able to make use of spare carriers or free up carriers if not required anymore.
+
+### 32.2.3 Requirement for network flexibility
+
+The 3GPP network shall be able to support network broadcast capacity assignment according to operator policies to consider the following criteria:
+
+- OTT provider request (including TV service information (e.g., codec information, media type information, etc))
+- available network unicast/broadcast capacity of 3GPP network
+
+Within the radio resources dedicated to TV services in a geographic area the 3GPP network shall allow the MNO to specify the allocation of radio resource by the following:
+
+- static allocation, i.e., pre-defined maximum percentage to be used for unicast and broadcast
+- dynamic allocation, i.e., the pre-defined maximum percentage for both unicast and broadcast to be changed at a time-resolution of [one] minute over a period of [24] hours
+
+The 3GPP network shall be able to support network broadcast geographic area coverage management considering following criteria:
+
+- OTT provider request (including the potential coverage information of TV service information)
+- available network unicast/broadcast capacity of 3GPP network
+- number of users under broadcast network coverage
+- The location information of UE
+
+The 3GPP network shall be able to deliver media content via unicast and broadcast in an efficient manner. The 3GPP system shall be capable of ensuring the timing sequence of different media content received by different UEs at the same location, even via different transport path, aligning with the timing sequence of TV service of the OTT provider in order to maintain synchronism.
+
+A UE shall be able to receive eMBMS from one cell site while receiving other services from the same cell site or another possibly cell site.
+
+The 3GPP network shall allow an MNO to service all UEs in an area with eMBMS independent of which MNO network(s) they have subscription to.
+
+### 32.2.4 Requirement for TV application support
+
+The eMBMS service layer should support audio and video formats typically supported by TV Content Providers for SD and HD TV transport services and UHD TV transport services.
+
+The eMBMS service layer should support codecs typically supported by TV Content Providers for HD TV services and UHD TV services. The eMBMS service layer should support accessibility functions typically supported by TV Content Providers (e.g. subtitling, closed captioning, audio descriptions, anonymous reception, reporting to support ratings, reporting enforcement, etc.).
+
+The eMBMS service layer should support regulatory mandates typically supported by TV Content Providers (blackouts, emergency alerts, etc.).
+
+The eMBMS service layer should support interactivity functions typically supported by TV Content Providers (interactive services, second screen, personalization, etc.).
+
+The eMBMS service layer should support ad insertion use cases typically supported by TV Content Providers (targeted ad insertion, ad replacement, etc.).
+
+The eMBMS service layer should support encryption, security and conditional access functions typically supported by TV Content Providers.
+
+The eMBMS service layer should support efficient concurrent delivery of multiple application components (TV service application signalling, statistical multiplexing, etc.).
+
+The eMBMS service layer should support random access and channel change times comparable to existing HD TV services.
+
+The eMBMS service layer should support TV service content delivery over broadcast only, unicast only and combinations of the two.
+
+The eMBMS service layer should support delivery of real-time and non-real-time content.
+
+The eMBMS service layer should enable extensibility and forward-compatibility to new requirements, formats, codecs and other functions to the extent possible.
+
+An eMBMS transport layer should be able to transport TV streams formatted not compliant to 3GPP standards.
+
+A UE should be able to access an eMBMS transport session with the support of only transport metadata.
+
+An eMBMS system should be able to be initiated by a UE with sufficient metadata provided by a mechanism other than User Service Description for non 3GPP transport services.
+
+### 32.2.5 Requirement for RAN sharing
+
+A participating eMBMS-enabled RAN shall be capable of distributing the content including both free-to-air content and subscribed content in conjunction with other participating eMBMS-enabled RANs.
+
+The hosting eMBMS-enabled RAN network provider shall be able to manage the shared eMBMS network to each of the participating MNOs.
+
+Each RAN provider shall report events supporting the accounting of network resource usage separately for each Participating MNO. This includes:
+
+- Start of service in the shared eMBMS network for a UE of the Participating MNO
+- End of service in the shared eMBMS network for a UE of the Participating MNO
+
+### 32.2.6 Requirement for wide area support
+
+The eMBMS network shall be able to support designated coverage area, for example national, regional and local coverage areas.
+
+### 32.2.7 Requirement for capability exposure
+
+The 3GPP system shall be able to support an MNO offering on-demand broadcast availability to TV services.
+
+Subject to MNO and 3rd OTT party agreement, to enable the MNO to evaluate the impact on distribution of data transfer in the network, the 3rd OTT party shall be able to indicate to the MNO the desired media format information: the volume of the data traffic expected to be broadcast in this geographic area, indication whether the streaming content can be accessed when the mobile users moves out/in of broadcast coverage area, indication whether the streaming content can be cached in the MNO network, association information among users i.e. user information, expected media content information, device information and group information of TV service and the timing relationship information of different media content.
+
+The 3GPP network shall enable an MNO to inform a 3rd party of the result (e.g., selected media format information, mode of content delivery (broadcast only, broadcast/unicast fall-back support, consumption-based switching between unicast/broadcast), QoE of content delivery, cached content indication) of delivering a TV service to a user.
+
+### 32.2.8 Fixed reception for TV services
+
+The 3GPP network shall allow a UE to receive a broadcast TV content using existing TV antenna equipment.
+
+NOTE 1: “existing TV antenna equipment” means rooftop or indoor antennas directly connected to a TV or set-top box typically used to receive DTT signals
+
+The 3GPP network shall allow a UE to receive unicast TV content using existing TV antenna equipment, at least for the downlink
+
+NOTE 2: This might imply the uplink to take another path e.g. via a different antenna if existing TV antenna equipment is not suitable for transmission.
+
+---
+
+## 33 Usage over unlicensed access
+
+### 33.1 Description
+
+It is important to document usage over unlicensed access such that an operator has the facility to determine which type of access the traffic was transported over.
+
+For example, LTE-WiFi Aggregation (LWA) and License Assisted Access (LAA) are two features whereby a UE is connected to two access technologies at the same time, i.e., a primary access and a secondary access, where the secondary access technology operates in unlicensed spectrum.
+
+### 33.2 Requirements
+
+The 3GPP network shall be able to identify traffic which was transported over unlicensed access.
+
+---
+
+## 34 Void
+
+### 34.1 Void
+
+### 34.2 Void
+
+---
+
+## 35 Restricted local operator services
+
+### 35.1 Description
+
+Access to restricted local operator services by unauthenticated UEs is based on FCC regulations in the U.S. related to manual roaming as noted in the Code of Federal Regulations (CFR) Title 47 Chapter 1 Subchapter B Part 20 Section 20.3 and the Code of Federal Regulations (CFR) Title 47 Chapter 1 Subchapter B Part 20 Section 20.12 (Resale and Roaming) Subparagraph c [60].
+
+The restricted local operator services offered by an operator are out of scope of 3GPP. Allowing access to restricted local operator services is completely under the local operator's control. The local operator can restrict unauthenticated UEs to be able to access restricted local operator services exclusively.
+
+Authenticated UEs in limited service state may also be able to use restricted local operator services.
+
+NOTE: Services provided through RLOS may also be available to authenticated UEs not in limited service state by other methods.
+
+### 35.2 Requirements
+
+Based on operator policy and national regulations, the 3GPP system shall support a mechanism to indicate to UEs that restricted local operator services are available.
+
+A UE shall be able to explicitly request access to a network offering restricted local operator services in order to access restricted local operator services.
+
+A UE explicitly requesting access to a network offering restricted local operator services in order to receive restricted local operator services shall not be put into limited service state.
+
+Based on operator policy and national regulations, the 3GPP system shall support mechanisms to allow access to restricted local operator services by unauthenticated UEs.
+
+The network shall be able to isolate restricted local operator services and usage from the rest of the network (i.e., similar to security for unauthenticated CS or IMS emergency calls).
+
+When a UE recognizes an origination attempt to a restricted local operator service and has not received an indication from the serving system that restricted local operator services are available, the UE shall block the origination attempt.
+
+The UE shall include the restricted local operator service call type indicator when an origination attempt is made for a restricted local operator service.
+
+---
+
+## Annex A (normative): Description of optional user equipment features
+
+### A.1 Display of called number
+
+This feature enables the caller to check before call setup whether the selected number is correct.
+
+### A.2 Indication of call progress signals
+
+Indications shall be given such as tones, recorded messages or visual display based on signalling information returned from the PLMN. On data calls, this information may be signalled to the DTE.
+
+Call progress indicators are described in 3GPP TS 22.001 [4].
+
+### A.3 Country/PLMN indication
+
+The country/PLMN indicator shows in which PLMN the UE is currently registered. This indicator is necessary so that the user knows when "roaming" is taking place and that the choice of PLMN is correct. Both the country and PLMN will be indicated. When more than one visited PLMN is available in a given area such information will be indicated.
+
+The PLMN name is either:
+
+- Stored in the ME and associated with the MCC+MNC combination received on the broadcast channel;
+- NITZ (see 22.042 [17]) (in which case it overrides the name stored in the ME);
+- stored in the USIM in text and/or graphic format and associated with the MCC+MNC combination, and optionally the LAI, received on the broadcast channel (in which case it overrides the name stored in the UE and – if present – the NITZ name).
+
+It shall be possible to store on the USIM at least 10 PLMN Identifications (MCC+MNC combination and optionally the LAI) for which the same PLMN name shall be displayed.
+
+The PLMN name stored in the USIM has the highest priority, followed by the PLMN name provided by NITZ. The PLMN name stored in the ME has the lowest priority.
+
+If the PLMN name stored in the USIM is not available in text format and the UE is unable to display the graphic format, the PLMN name provided by NITZ has the highest priority, the PLMN name stored in the ME has the next priority.
+
+For a PLMN name provided by NITZ, operators using non-Latin characters of the local language (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) may include the network name in Latin characters in addition to characters of the local language.
+
+For a PLMN name provided by NITZ, the roaming UE should skip displaying non-Latin character(s) if the language of those character(s) does not match the language of the MMI for the UE. If this would lead to no remaining Latin character in the PLMN name, the UE should skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has the next priority instead.
+
+## A.4 Service Provider Name indication
+
+The service provider name is stored in the USIM in text and/or optionally graphic format. It shall be possible to associate at least 10 PLMN Identifications (MCC+MNC combination) with the same SP Name.
+
+When registered on the HPLMN, or one of the PLMN Identifications used for Service Provider Name display:
+
+- (i) The SP Name shall be displayed;
+- (ii) Display of the PLMN Name is an operator's option by setting the appropriate fields in the USIM (i.e. the Service Provider name shall be displayed either in parallel to the PLMN Name or instead of the PLMN Name).
+
+When registered on neither the HPLMN, nor one of the PLMN Identifications used for Service Provider Name display:
+
+- (i) The PLMN name shall be displayed;
+- (ii) Display of the SP Name is an operator's option by setting the appropriate fields in the USIM.
+
+If the UE is unable to display the full name of the Service Provider the name is cut from the tail end. The storage of Service Provider name and options, and choice of options, shall be under control of the network operator.
+
+### A.4a Core Network Operator Name indication
+
+It shall be possible for the UE to display the name of the core network operator the user has selected.
+
+## A.5 Keypad
+
+A physical means of entering numbers, generally, though not necessarily, in accordance with the layout shown in figure A.1.
+
+See also 3GPP TS 22.030 [6] (Man-Machine Interface).
+
+Additional keys may provide the means to control the UE (e.g. to initiate and terminate calls).
+
+
+
+Figure A.1: A standard numeric keypad layout. The keypad is a rectangular box containing a grid of keys. The first three rows contain the numbers 1 through 9, arranged in three columns: Row 1: 1, 2, 3; Row 2: 4, 5, 6; Row 3: 7, 8, 9. The fourth row contains the asterisk (\*), the number 0, and the hash symbol (#).
+
+Figure A.1
+
+## A.6 Short message indication and acknowledgement
+
+This feature allows the delivery of short messages to a UE from a service centre. Such messages are submitted to the service centre by a telecommunications network user who can also request information of the status of the message by further interrogation of the service centre. The service centre then transmits the message to an active UE user.
+
+The UE must therefore provide an indication to the user that a message has been received from the service centre and must also send an acknowledgement signal to the PLMN to show that this indication has been activated. The PLMN then returns this acknowledgement to the service centre.
+
+The short message service teleservice is described in specification 3GPP TS 22.003 [14].
+
+## A.7 Short message overflow indication
+
+An indication shall be given to the user of the short message service when an incoming message cannot be received due to insufficient available memory.
+
+## A.8 International access function
+
+Provision is made for a direct, standard method of gaining international access. For this purpose the UE may have a key whose primary or secondary function is marked "+". This is signalled over the radio interface and would have the effect of generating the international access code in the network. It may be used directly when setting up a call, or entered into the memory for abbreviated dialling.
+
+This feature is of benefit since the international access code varies between CEPT countries, which might cause confusion to a user, and prevent the effective use of abbreviated dialling when roaming internationally. Users may still place international calls conventionally, using the appropriate international access code.
+
+## A.9 Service Indicator (SI)
+
+An indication is given to the user that there is adequate signal strength (as far as can be judged from the received signal) to allow a call to be made. Additionally the network should be capable of providing, and the UE may display, an indication of the serving cells' capabilities e.g. GPRS, HSDPA, HSUPA.
+
+If indicated by the registered network, the UE in idle mode may display an indication of one of the radio access technologies provided to the UE in the network on which the UE is registered with the following priority order: E-UTRAN, UTRAN, GERAN.
+
+Displaying the serving cell's capabilities and the access technology are mutually exclusive.
+
+## A.10 Dual Tone Multi Frequency (DTMF)
+
+The UE shall be capable of initiating DTMF in accordance with specifications 3GPP TS 22.003 [14]. Optionally, the UE may provide a suppress function which allows the user to switch off the DTMF function.
+
+## A.11 On/Off switch
+
+The UE may be provided with a means of switching its power supply on and off. Switch-off shall be "soft", so that on activation, the UE completes the following housekeeping functions: termination of a current call, detach (where applicable) and storing required data in the SIM/USIM before actually switching off. As far as possible, this procedure should also apply on power failure (e.g. remote switch-off or low battery).
+
+## A.12 Sub-Address
+
+This feature allows the mobile to append and/or receive a sub-address to a Directory Number, for use in call set-up, and in those supplementary services that use a Directory Number.
+
+## A.13 Short Message Service Cell Broadcast
+
+The Short Message Service Cell Broadcast enables the mobile equipment to receive short messages from a message handling system.
+
+The short message service cell broadcast teleservice is described in specification 3GPP TS 22.003 [14]
+
+## A.14 Short Message Service Cell Broadcast DRX
+
+This feature enables a mobile equipment to save on battery utilization, by allowing the mobile equipment to not listen during the broadcast of messages the subscriber is not interested in.
+
+## A.15 Support of the extended Short message cell broadcast channel
+
+This feature allows a mobile equipment by supporting of the extended Short message cell broadcast channel to enhance the capacity of the service. The support of the extended channel has low priority, i.e. the UE can interrupt the reading of this channel if idle mode procedures have to be executed.
+
+## A.16 Network Identity and Timezone
+
+The feature provides the means for serving PLMNs to transfer current identity, universal time and the local timezone to mobile equipment, and for the mobile equipment to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the ME or have changed their name since the ME was sold. Additionally time and timezone information can be utilized by MEs as desired.
+
+The network name time and timezone information will normally be transferred from the network to the ME:
+
+- 1) Upon registering on the network.
+- 2) When the UE geographically relocates to a different Local Time Zone.
+- 3) When the network changes its Local Time Zone, e.g. between summer and winter time.
+- 4) When the network changes its identity.
+- 5) At any time during a signalling connection with mobile equipment.
+
+Further details of this feature are described in 3GPP TS 22.042 [17].
+
+## A.17 Network's indication of alerting in the UE
+
+This feature provides the means for serving PLMNs to transfer to a UE an indication that may be used by the UE to alert the user in a specific manner in the following cases:
+
+- mobile terminating call
+- network-initiated USSD
+- network-initiated Mobile Originated (MO) connection, if the ME supports the "network-initiated MO connection" feature.
+
+Eight different indications are defined, whether the mobile terminating traffic is a call or USSD or related to the network-initiated MO connection procedure. These indications are sent by the network and received by the UE:
+
+- Three of these indications are used as levels, reflecting some kind of urgency: level 0 indicates that the UE shall not alert the user for USSD and remain silent in the case of call, level 2 shall be considered by the UE as more important than level 1 for the purpose of alerting the user.
+
+- The five other indications are used as categories, identifying different types of terminating traffic. The UE shall inform the user in a specific manner for each of these five categories. Nevertheless, the possible forms of the alert (different ringing tones, displayed text, graphical symbols...) is still up to the mobile manufacturer (some forms of alerts can be simultaneously used, e.g. ringing tones and text on the display).
+
+The management of the feature by the UE requires for the handling of categories that:
+
+- the SIM/USIM stores for each category an informative text (maximum 25 characters per category) describing the type of terminating traffic associated with the category. This information could be used by the UE when alerting the user (display on the screen). It is necessary for the network operator to be able to change the meaning of each category.
+- The user has the ability to set up his/her own association between the type of terminating traffic (identified by each category) and the different types of alert provided by the UE. To help the user in this choice, the UE uses the informative text associated with each category (as stored in the SIM/USIM). The UE should keep this association when switched off.
+
+Default settings should also be defined in the ME for the following cases:
+
+- when the UE receives a call, USSD or a request for a network-initiated MO connection with no alerting indication,
+- when the UE receives a call, USSD or a request for a network-initiated MO connection with a category of alerting not defined in the SIM/USIM.
+
+These default settings should be separated per type of mobile terminated traffic received (call, USSD or request for a network-initiated MO connection).
+
+A UE supporting the feature shall act according to the following points in case of mobile terminating traffic:
+
+- when a mobile terminating traffic is received without any indication (level or category), the ME shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
+- if a level is indicated, the UE shall use an alert enabling the user to differentiate between the three levels.
+- if a category is indicated, then:
+ - if the SIM/USIM used in the UE does not store any information on that feature, the UE shall ignore the category received with any mobile terminating traffic and act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
+ - if the category is not defined in the SIM/USIM, the UE shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic).
+ - if the category is defined in the SIM/USIM, the UE shall use the alert associated with this category. In addition, it would be very useful for the user to be notified of the informative text associated with this category (e.g. on the display).
+
+Some interactions between this feature and other services related to alerting are described below:
+
+- the call waiting service has priority on this feature, i.e. the call waiting tone will be played and not the alert derived by this feature. If possible, two different indications should be given to the user (e.g. the call waiting tone and a text on the display indicating call waiting, and in addition a text relative to the type of the new call received).
+- the presentation of the calling line identity takes priority on this feature, if it is not possible to display this information and another information related to this feature.
+- In case of interaction between this feature and UE specific features to alert the user (e.g. whole silent mode), the user should still be able to differentiate between the different levels or different types of terminating traffic, even if the alert itself may be changed.
+
+## A.18 Network-initiated Mobile Originated (MO) connection
+
+The "Network-initiated Mobile Originated connection" feature allows the network to ask the mobile equipment to establish a mobile originated connection. The serving PLMN provides the mobile equipment with the necessary information which is used by the mobile equipment to establish the connection.
+
+Currently only the network-initiated mobile originated call feature is specified. It is mandatory for a UE supporting CCBS and is used in the case of a CCBS recall.
+
+## A.19 Abbreviated dialling
+
+The directory number or part of it is stored in the mobile equipment together with the abbreviated address. After retrieval the directory number may appear on the display.
+
+Abbreviated dialling numbers stored in the UE or USIM may contain wild characters.
+
+If wild characters are used to indicate missing digits, each wild character shall be replaced for network access or supplementary service operation, by a single digit entered at the keypad. The completed directory number is transmitted on the radio path.
+
+## A.20 Barring of Dialled Numbers
+
+This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers belonging to a pre-programmed list of numbers in the SIM/USIM.
+
+Barred Dialling Numbers stored in the /USIM may contain wild characters.
+
+Under control of PIN2, "Barred Dialling Mode" may be enabled or disabled. The selected mode is stored in the SIM/USIM.
+
+Under PIN2 control, it shall be possible to add, modify or delete a particular "Barred Dialling Number" (BDN) and to allocate or modify its associated comparison method(s). This BDN may have the function of an abbreviated dialling number / supplementary service control (ADN/SSC), overflow and/or sub-address.
+
+When BDN is inactive, no special controls are specified, and the barred dialling numbers may be read (though not modified or deleted, except under PIN2 control) as if they were normal abbreviated dialling numbers. Access to keyboard and normal abbreviated dialling numbers (including sub-address) is also permitted.
+
+When Barring of Dialled Numbers is active:
+
+- Considering a number dialled by the user, if it exists a BDN for which there is a successful comparison (see below) between that BDN and the dialled number, then the ME shall prevent the call attempt to that number. If there is no BDN to fulfil those conditions, the call attempt is allowed by the ME.
+
+With each BDN is associated one (or a combination of) comparison method(s) used between that BDN and the number dialled by the user. At least three different comparison methods are possible:
+
+- The comparison is made from the first digit of that BDN, from the first digit of the dialled number and for a number of digits corresponding to the length of the BDN.
+- The comparison is made from the first digit of that BDN, from any digit of the dialled number and for a number of digits corresponding to the length of the BDN.
+- The comparison is made backwards from the last digit of that BDN, from the last digit of the dialled number and for a number of digits corresponding to the length of the BDN.
+- If a BDN stored in the SIM/USIM contains one or more wild characters in any position, each wild character shall be replaced by any single digit when the comparison between that BDN and the dialled number is performed.
+- If a BDN contains a sub-address, and the same number without any sub-address or with that sub-address is dialled, the ME shall prevent the call attempt to that number.
+- Numbers specified as "barred" may only be modified under PIN2 control.
+
+- If the ME does not support barring of dialled numbers, the UE with a BDN enabled USIM shall not allow the making of calls and the UE with BDN enabled SIM shall not allow the making or receiving of calls. However, this feature does not affect the ability to make emergency calls.
+
+If "Fixed Number Dialling" and "Barring of Dialled Numbers" are simultaneously active, the dialled number shall be checked against the two features before the ME allows the call attempt. In that case, a dialled number will only be allowed by the ME if it is in the FDN list and if the comparison between that number and any number from the BDN list is not successful.
+
+The UE may support other selective barrings, e.g. applying to individual services (e.g. telephony, data transmission) or individual call types (e.g. long distance, international calls).
+
+## A.21 DTMF control digits separator
+
+Provision has been made to enter DTMF digits with a telephone number, and upon the called party answering the UE shall send the DTMF digits automatically to the network after a delay of 3 seconds ( $\pm 20\%$ ). The digits shall be sent according to the procedures and timing specified in 3GPP TS 24.008 [13].
+
+The first occurrence of the "DTMF Control Digits Separator" shall be used by the ME to distinguish between the addressing digits (i.e. the phone number) and the DTMF digits. Upon subsequent occurrences of the separator, the UE shall pause again for 3 seconds ( $\pm 20\%$ ) before sending any further DTMF digits.
+
+To enable the separator to be stored in the address field of an Abbreviated Dialling Number record in the SIM/USIM, the separator shall be coded as defined in 3GPP TS 31.102 [19]. The telephone number shall always precede the DTMF digits when stored in the SIM/USIM.
+
+The way in which the separator is entered and display in the UE, is left to the individual manufacturer's MMI.
+
+MEs which do not support this feature and encounter this separator in an ADN record of the SIM/USIM will treat the character as "corrupt data" and act accordingly.
+
+## A.22 Selection of directory number in messages
+
+The Short Message Service (SMS), Cell Broadcast Service (CBS), Multimedia Message Service (MMS), Network-initiated USSD or Network Response to Mobile Originated USSD message strings may be used to convey a Directory Number, which the user may wish to call.
+
+## A.23 Last Numbers Dialled (LND)
+
+The Last "N" Numbers dialled may be stored in the SIM/USIM and/or the ME. "N" may take the value up to 10 in the SIM/USIM. It may be any value in the ME. The method of presentation of these to the user for setting up a call is the responsibility of the UE but if these numbers are stored in both the SIM/USIM and the UE, those from the SIM/USIM shall take precedence.
+
+## A.24 Service Dialling Numbers
+
+The Service Dialling Numbers feature allows for the storage of numbers related to services offered by the network operator/service provider in the SIM/USIM (e.g. customer care). The user can use these telephone numbers to make outgoing calls, but the access for updating of the numbers shall be under the control of the operator.
+
+NOTE: No MMI is envisaged to be specified for these numbers and it is left to mobile manufacturer implementations.
+
+A specific example of Service Dialling Numbers is the storage of mailbox dialling numbers on the SIM/USIM for access to mailboxes associated with Voicemail, Fax, Electronic Mail and Other messages.
+
+## A.25 Fixed number dialling
+
+This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers other than those pre-programmed in the SIM/USIM.
+
+Under control of PIN 2, "Fixed Dialling Mode" may be enabled or disabled. The mode selected is stored in the SIM/USIM.
+
+Fixed Dialling Numbers (FDNs) are stored in the SIM/USIM in the Fixed Dialling Number field. FDN entries are composed of a destination address/Supplementary Service Control. Destination addresses may have the format relevant to the bearer services/teleservices defined in [21] and [14]. FDN entries may take the function of an Abbreviated Dialling Number/Supplementary Service Control (ADN/SSC), Overflow and/or sub-address. Fixed Dialling Numbers stored in the SIM/USIM may contain wild card characters.
+
+The Fixed Dialling feature is optional, however when Fixed Dialling Mode is enabled, an ME supporting the feature shall;
+
+- Prevent the establishment of bearer services/teleservices to destination addresses which are not in FDN entries on a per bearer service/teleservice basis. The list of bearer services/teleservices excluded from the FDN check shall be stored in the SIM/USIM. Those bearer services/teleservices are characterised by their service code as described in [23]. For instance, if the SMS teleservices is indicated in this list, SMS can be sent to any destination. By default, the ME shall prevent the establishment of any bearer service/teleservice to destination addresses which are not in FDN entries.
+- Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2.
+- Allow the establishment of bearer services/teleservice to destination addresses stored in FDN entries. For SMS, the Service Center address and the end-destination address shall be checked.
+- Support the reading and substitution of wildcards in any position of an FDN entry, via the ME MMI.
+- Allow the user to replace each wildcard of an FDN entry by a single digit, on a per call basis without using PIN2. The digit replacing the wildcard may be used for network access or supplementary service operation.
+- Only allow Supplementary Service (SS) Control (in Dedicated or Idle mode) if the SS control string is stored as an FDN entry.
+- Allow the extension of an FDN entry by adding digits to the Fixed Dialling number on a per call basis.
+- Allow the emergency numbers (see Section 8.4) to be called, even if it is not an FDN entry.
+- Allow normal access to ADN fields (i.e. allow ADN entries to be modified, added or deleted) and the keyboard.
+- Allow use of ADNs subject to the FDN filter.
+
+When FDN is disabled, an ME supporting FDN shall;
+
+- Allow FDN entries to be read as though they were normal ADN entries.
+- Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2.
+- Allow normal access to ADN fields and the keyboard.
+
+If the ME does not support FDN, the UE shall not allow the making of calls when Fixed Dialling is enabled in the USIM, and the UE shall not allow the making or receiving of calls when Fixed Dialling is enabled in the SIM. However, emergency calls (112 and other user defined emergency numbers) shall still be possible.
+
+NOTE: Wildcards are stored on the SIM/USIM. The wildcard coding is given in 3GPP TS 31.102 [19].
+
+## A.26 Message Waiting Indication
+
+A short message may be used to provide an indication to the user about the status and number of types of messages waiting on systems connected to the PLMN. The ME shall present this indication as an icon on the screen, or other
+
+MMI indication, and store the indication status on the SIM/USIM to allow the status to be retained through power off/on, SIM/USIM movement between UEs etc.
+
+The ME shall be able to accept and acknowledge these message waiting status short messages irrespective of the memory available in the SIM/USIM.
+
+## A.27 Transfer of eCall Minimum Set of Data (MSD)
+
+### A.27.1 General Requirements
+
+With the exception of the following specific requirements, considered necessary for the satisfactory operation of the eCall service, all existing emergency call requirements shall apply.
+
+An eCall shall consist of an emergency call supplemented by a minimum set of emergency related data (MSD). The MSD e.g. vehicle identity, location information and other parameters, is defined by CEN [46].
+
+- An eCall may be initiated automatically, for example due to a vehicle collision, or manually by the vehicle occupants;
+- An IVS, or other UE designed to support eCall functionality, shall include in the emergency call set-up an indication that the present call is either a Manually Initiated eCall (MIEC) or an Automatically Initiated eCall (AIEC).
+- The Minimum Set of Data (MSD) sent by the In vehicle System (IVS) to the network shall not exceed 140 bytes;
+- Should the MSD component not be included in an eCall, or is corrupted or lost for any reason, then this shall not affect the associated emergency call speech functionality.
+- To reduce the time taken to establish an eCall an IVS whilst in eCall only mode, may receive network availability information whilst not registered on a PLMN.
+- PLMNs should make use of eCall indicators, received in the emergency call set-up, to differentiate eCalls from other emergency calls.
+- The MIEC and AIEC should be used by the serving network to filter and route eCalls to dedicated, eCall equipped, PSAPs.
+- The PSAP shall be given an indication that the incoming call is an eCall.
+- When an emergency call, other than an eCall, is routed to a PSAP that supports the eCall service, the eCall equipment shall not cause audible interference to the emergency voice call.
+
+Throughout the duration of the emergency call and following receipt of the MSD by the PSAP
+
+- It shall be possible for the PSAP to send a confirmation to the IVS that the MSD has been acted upon.
+- It shall be possible for the PSAP to request the IVS to re-send its most recent MSD.
+- It shall be possible for the PSAP to instruct the IVS to terminate the eCall.
+
+### A.27.2 Requirements for the transfer of eCall MSD in a TS12 call
+
+The MSD should typically be made available to the PSAP within 4 seconds measured from the time when end to end connection with the PSAP is established;
+
+A call progress indication shall be provided to the user whilst the MSD transmission is in progress.
+
+Where the eCall indicators are not supported by the serving network, the time needed for the PSAP eCall modem to differentiate between eCalls and other TS12 calls, before routing the call to an operator, shall not exceed 2 seconds from when the IVS receives notification that the PSAP has answered the call.
+
+When an eCall is routed to a PSAP, that does not support the eCall service, the In Vehicle System (IVS) shall not emit any audible tones for longer than 2 seconds from the time that the call is first answered.
+
+### A.27.3 Requirements for the transfer of eCall data in an IMS emergency call
+
+The MSD should typically be available to the PSAP when the end to end connection with the PSAP has been established.
+
+NOTE: There are cases where a UE delivers multiple instances of an MSD to one or more PSAPs, for example as per 3GPP TS 22.101 clause 10.1.2., when an IMS emergency call based eCall attempt has not been successful but the MSD was successfully received by a PSAP. It is out of the scope of 3GPP as to how to manage any duplicate information received by the PSAP(s) or emergency services as a result of this.
+
+Additional data (i.e. data not contained in the initial MSD) may be transferred at any time during the eCall (e.g. MSD acknowledgement, resending of the MSD if requested by a PSAP).
+
+The call setup time of an eCall shall be the same as for an IMS emergency call.
+
+The IVS shall not emit any audible tones in order to transfer the MSD or other eCall related data.
+
+### A.27.4 Interworking requirements
+
+A PSAP, which is connected to the IMS, and supports either IMS emergency call based eCall or TS12 based eCall, shall be able to interwork with a TS12 based IVS using IMS Centralized Service, i.e. it shall be able to terminate the emergency call from the IVS, receive the MSD and request additional data from the IVS, using the eCall Modem end-to-end.
+
+An IVS that supports IMS emergency call based eCalls shall also support TS12 based eCalls.
+
+An IVS that supports IMS emergency call based eCalls and is attached via LTE access with no CS access available shall support the transfer of MSD via IMS emergency call to a TS12 based PSAP using the eCall Modem end-to-end.
+
+NOTE 1: It is assumed that the above scenario is very unlikely to occur on the market. Therefore the operation of eCall Modem over a PS bearer should be considered as an option of last resort [58]. As such this is not constrained by the requirements in A.27.2 and A.27.3.
+
+In case of interworking between TS12 and IMS emergency call based eCall equipment the requirements given in subclause A.27.2 shall apply, requirements given in subclause A.27.3 do not apply.
+
+### A.27.5 Domain selection
+
+A PLMN shall indicate to an IVS whether IMS emergency call based eCalls are supported.
+
+An IVS that supports both IMS emergency call based eCalls and TS12 based eCalls shall support domain selection for an eCall in the same way as for any other emergency call except for determining PLMN support for an IMS emergency based eCall using the PLMN indication for this.
+
+## A.28 Requirements for "In Case of Emergency" (ICE) information
+
+The In Case of Emergency (ICE) information are used to enable first responders, such as paramedics, fire-fighters, and police officers, to contact a victim's emergency contact(s) in order to identify the victim and obtain important medical information or other information required during an emergency.
+
+A UE shall have the capability to store one or more "ICE information" on the UICC. The "ICE information" shall list the type of information which is to be configured by the mobile operator as described in the table below.
+
+**Table A.28.1: "ICE information" description**
+
+| | ICE information type format | ICE information type value | ICE information value 1 | ICE information value 2 | ICE information value n |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------|
+| Description | Two formats shall be defined in this release:
1- Phone number format. For the phone number format it shall be possible to store a name and a phone number.
2- Free format.
It shall be possible for the mobile operator to provision zero, one or several instances of a given format on the UICC.
| It shall be possible to store this information in text or graphic format. | It shall be possible to have at least one ICE information value field. If more than one information value fields are required it shall be indicated by the ICE information type format.
It shall be possible for the subscriber to add, modify, view, or delete any ICE information value.
For the free format ICE information type format, it shall be possible to store information in text or graphic format.
For pre-defined ICE information type formats the ME should adapt the input mode to the type of the ICE information value (e.g. numerical mode for phone number input).
| Present only if explicitly indicated by the ICE information type format. | Present only if explicitly indicated by the ICE information type format. |
+
+The following table provides an example of ICE information stored on the UICC:
+
+**Table A.28.2: "ICE information" example**
+
+| ICE information type | ICE information type value | ICE information value 1 | ICE information value 2 |
+|----------------------|--------------------------------|-----------------------------|-------------------------|
+| Phone Number | "Contact in case of emergency" | My Wife | +3364566 |
+| Phone Number | "Contact in case of emergency" | Family Smith | +3364565 |
+| Phone Number | "Contact in case of emergency" | My Family doctor: Dr. Jones | +33643234 |
+| Free Format | "Medical Information" | My blood type is A+, I am | N/A |
+
+| | | | |
+|-------------|-----------------------|-------------------------------------------------------------------|-----|
+| | | allergic to etc. | |
+| Free Format | "Home Postal Address" | 15 rue de la Paix, Paris, France | N/A |
+| Free Format | "Language" | French | N/A |
+| Free Format | "Travel Information" | London, from 3 rd July. to 29 th July, 2008 | N/A |
+
+Provision is made for direct and unambiguous read access from the UE to ICE information stored on the UICC.
+
+The subscriber may choose not to enter any ICE information.
+
+The default configuration for this information shall be that they are accessible even when the security features on either the UE or UICC have been enabled (e.g. the keypad is locked). It shall be possible for the subscriber to change this default setting to prevent accessibility to the ICE information (i.e. a user configurable setting in the UICC indicates whether the ICE information on the UICC shall be displayed or not, if the ICE access procedure described in TS 22.030 [6] is invoked).
+
+The unlocking of ICE information shall not allow access to other secure information on the UICC or UE. The ICE information value should not be accessible to ME or UICC applications.
+
+The ICE access procedure is described in TS 22.030 [6].
+
+---
+
+## Annex B (informative): Additional number use case
+
+Company X is customer of operator Z and has a subscription for voice and data with 10 SIM cards. The company also decides to subscribe to the private numbering plan feature of operator Z. A certain corporate phone number is assigned to company X, e.g. +43 676 88888 xx (with xx being the extensions of the users), and they can freely choose the extensions for up to 100 SIM cards.
+
+Initially company X take the existing 10 SIM cards (with the existing MSISDNs) and integrate them into the private numbering plan by assigning the extensions 11 to 20 to these cards via a web portal. This is not a permanent assignment, the extensions can be changed easily any time, old SIMs can be deleted from the private numbering plan and new ones can be integrated whenever necessary. Special privileges or restrictions can be chosen on a per SIM basis via the portal and special tariffs apply.
+
+The CEO of company X calls a customer. The customer's phone displays the corporate number + extension of the CEO as CLI. After a while the customer decides to call back the CEO and uses the corporate number + extension as MSISDN. Later they also exchange some short messages, again the corporate number + extension of the CEO is used as sender's MSISDN.
+
+For all these calls and short messages operator Z is able to collect charging records containing the corporate number + extension.
+
+The CEO also uses her smart phone to establish PS connections to browse the internet and to access the intranet via the operator's gateway. The corporate number + extension is used for authentication and authorisation in the company's intranet and its web applications. Charging for PS connections by operator Z is also based on this number.
+
+In general the users in company X are not aware of their "real" underlying MSISDNs in the system, they only see the corporate number + their extension and there is no need for them to know the underlying MSISDN.
+
+## Annex C (informative): Change history
+
+| Change history | | | | | |
+|-------------------|-------------------------------|--------------------|------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments |
+| SMG#22 | 302/97 | 001 | 4.6 (Role Model) | 3.1.0 | SMG3 queried the separation of network operator into core and access, which, on examination, SMG1 find unhelpful |
+| SMG#22 | 319/97
(SMG1 WPC 125/97) | 002 | | 3.1.0 | Editorial Changes: FLMPTS was replaced by IMT 2000, 2 new references given, additional clarifications. |
+| SMG#22 | 320/97 | 003 | 8.5, 9.3, 9.5, 17 | 3.1.0 | Changes on Emergency Calls, User identification, Multiple profiles and additional handover requirements. |
+| After SMG#23 | SMG1 433u/97
965/97 | 004 | | Draft 3.2.0 | Based on Approved Changes at SMG#22
Distributed at SMG1 in Dresden Nov 3-7, 97 to be Approved at SMG#24 |
+| SMG#24 | 966/97 | 005 | Sections 8, 9, 11 | 3.2.1 | Restructuring of sections 8,9 and 11 to gather all requirements relating to multiple subscriptions into one section and to improve the clarity. |
+| SMG#24 | 967/97 | 006 | Section 8.1 | 3.2.1 | To improve the accuracy of text on numbering principles and minor editorial change to section 8.1 |
+| SMG#27 | 98-0551 | 007 | Section 4.6 and misc. | 3.3.0 | Removal of commercial role model from the specification in order to improve clarity |
+| SMG#27 | 98-0552
(Not Approved) | 008 | New Section 18
(Not Applied) | 3.3.0 | To include requirements for network selection in service principles: NOT APPROVED > NOT APPLIED |
+| Pre-SMG#28 | (SMG1 Tdoc 98-0893)
99-040 | 008 r4
Rejected | New Section 18
Applied | [Draft 3.4.0] | Added Network Selection section - Agreed by correspondence - Jan 13, 1999 - Prepared with CRs applied with revision marks |
+| SMG#27 | 98-0553 | 009 | Section 4.3 | 3.3.0 | To remove unnecessary reference to IN and B-ISDN |
+| SMG#27 | 98-0682 | 010 | Section 11 | 3.3.0 | To improve the clarity of service requirements for multiple user profiles |
+| Pre-SMG#28 | (SMG1 Tdoc 98-0869)
99-040 | 011 | Sections 1, 2, 3, 4, 9, 10, 12, 17 | Draft 3.4.0 | Clean up for UMTS phase 1
Agreed at SMG1 Rome |
+| Pre-SMG#28 | (SMG1 Tdoc 98-852)
99-040 | 012 | Sections 3,8,9,11,14,15 | Draft 3.4.0 | Changes in IC card and terminal service requirements
Agreed at SMG1 Rome |
+| Pre-SMG#28 | (SMG1 Tdoc 98-0894)
99-040 | 013r1 | Section 3.2 & 4.3 | Draft 3.4.0 | Clarification of general requirements for efficient use of radio resources
Agreed by correspondence - Jan 13, 1999 - Prepared with CRs applied with revision marks |
+| Note | | | | Draft 3.4.0 | SMG1 agreed only |
+
+| Change history | | | | | |
+|----------------|-----------|--------------|--------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments |
+| pre-SMG#28 | 99-040 | 015 Rejected | 17 | Draft 3.4.0 | According to the outcome of the SMG 1 ad-hoc meeting on handover issues it is proposed that inter-operator handover is not required for UMTS phase 1.(rejected by smg#28) |
+| SMG#28 | 99-305 | 008r5 | Revised Section 18 | 3.4.0 | Network Selection presented at SMG#28 in 2201_008r4 was further revised and Approved at SMG#28. |
+| Note | | | | 3.4.0 | Removal of Section 12 on UPT with CR 011 causes a skip section from Section 11 to 13. |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------|----|
+| TSG SA # | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-03 | SP-99104 | S1-99202 | 22.101 | A016 | | R99 | B | Control of supplementary services (GSM 02.04), may use MMI procedures specified in GSM 02.30 and existing GSM MMI related MS features (GSM 02.07) may also be used. | 3.4.0 | | |
+| Post-SA#3 | | | 22.101 | | | R99 | | Updated Logo, ... | 3.5.0 | 3.5.1 | |
+| SP-04 | SP-99229 | S1-99387 | 22.101 | 021 | | R99 | B | MultiNumbering: It will be possible for multiple MSISDNs to be associated with a single subscription. | 3.5.0 | 3.6.0 | |
+| SP-04 | SP-99226 | S1-99395 | 22.101 | 020 | 7 | R99 | B | Emergency: To route the call to the appropriate emergency service if more than one emergency number is supported in a country. | 3.5.0 | 3.6.0 | |
+| SP-05 | SP-99439 | S1-99737 | 22.101 | 025 | | R99 | B | Support of SAT by USIM | 3.6.0 | 3.7.0 | |
+| SP-05 | SP-99439 | S1-99816 | 22.101 | 024 | | R99 | B | Clarification on the usage on 2G SIM and 3G USIM | 3.6.0 | 3.7.0 | |
+| SP-05 | SP-99435 | S1-99851 | 22.101 | 022 | | R99 | C | Clarification of Emergency Call requirements | 3.6.0 | 3.7.0 | |
+| SP-06 | SP-99524 | S1-991031 | 22.101 | 029 | | R99 | B | Emergency Call | 3.7.0 | 3.8.0 | |
+| SP-06 | SP-99527 | S1-991038 | 22.101 | 028 | | R99 | C | FDN | 3.7.0 | 3.8.0 | |
+| SP-06 | SP-99519 | S1-991026 | 22.101 | 026 | | R99 | D | Mainly editorial update for GSM/3GPP use. | 3.7.0 | 3.8.0 | |
+| SP-07 | SP-000060 | S1-000112 | 22.101 | 030 | | R99 | A | Support of encryption in GPRS mobile stations | 3.8.0 | 3.9.0 | |
+| SP-07 | SP-000070 | S1-000137 | 22.101 | 031 | | R99 | F | Fixed Dialing Number (FDN) | 3.8.0 | 3.9.0 | |
+| SP-08 | SP-000210 | S1-000271 | 22.101 | 033 | | R99 | D | Network selection procedures removed from section 16, reference to 22.011 added | 3.9.0 | 3.10.0 | |
+| SP-08 | SP-000200 | S1-000350 | 22.101 | 035 | | R99 | B | Emergency Calls and numbers used | 3.9.0 | 3.10.0 | |
+| SP-08 | SP-000201 | S1-000362 | 22.101 | 038 | | R99 | F | CS multimedia support | 3.9.0 | 3.10.0 | |
+| SP-08 | SP-000202 | S1-000326 | 22.101 | 039 | | R99 | F | Clarification for USIM Application selection | 3.9.0 | 3.10.0 | |
+| SP-08 | SP-000210 | S1-000270 | 22.101 | 034 | | R00 | D | Network selection procedures removed from section 16, reference to 22.011 added | 3.9.0 | 4.0.0 | |
+| SP-08 | SP-000200 | S1-000351 | 22.101 | 036 | | R00 | B | Emergency Calls and numbers used | 3.9.0 | 4.0.0 | |
+| SP-08 | SP-000213 | S1-000352 | 22.101 | 037 | | R00 | B | Emergency Call enhancements | 3.9.0 | 4.0.0 | |
+| SP-09 | SP-000383 | S1-000603 | 22.101 | 040 | | R4 | B | Multimedia messaging | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000383 | S1-000605 | 22.101 | 041 | | R4 | C | Service Management requirements | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000430 | S1-000700 | 22.101 | 042 | 1 | R4 | F | General corrections and clarifications to 22.101 for Release 2000 | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000383 | S1-000598 | 22.101 | 046 | | R4 | D | Editorial changes to 22.101 for Release 2000 | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000430 | S1-000698 | 22.101 | 047 | 1 | R4 | C | Numbering Principles | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000383 | S1-000620 | 22.101 | 048 | | R4 | C | Service evolution | 4.0.0 | 4.1.0 | |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|-----|---|-------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|----------------------|
+| SP-09 | SP-000391 | S1-000573 | 22.101 | 049 | | R4 | D | Emergency Call | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000405 | S1-000649 | 22.101 | 050 | | R4 | B | Text Conversation | 4.0.0 | 4.1.0 | |
+| SP-09 | SP-000383 | S1-000625 | 22.101 | 043 | | R5 | F | Classification of services | 4.0.0 | 5.0.0 | |
+| SP-09 | SP-000383 | S1-000622 | 22.101 | 044 | | R5 | B | IP multimedia services | 4.0.0 | 5.0.0 | |
+| SP-09 | SP-000383 | S1-000621 | 22.101 | 045 | | R5 | B | IP multimedia session for Emergency Call | 4.0.0 | 5.0.0 | |
+| SP-09 | SP-000430 | S1-000699 | 22.101 | 051 | | R5 | C | IM Number portability | 4.0.0 | 5.0.0 | |
+| SP-09 | SP-000430 | S1-000701 | 22.101 | 052 | | R5 | F | Introduction of IM CN | 4.0.0 | 5.0.0 | |
+| SP-09 | SP-000383 | S1-000704 | 22.101 | 053 | | R5 | F | Subscription | 4.0.0 | 5.0.0 | |
+| SP-09 | SP-000383 | S1-000705 | 22.101 | 054 | | R5 | F | Roaming | 4.0.0 | 5.0.0 | |
+| SP-10 | SP-000533 | S1-000799 | 22.101 | 059 | | Rel-5 | A | Deleting Encrypted USIM-ME interface | 5.0.0 | 5.1.0 | TEI4 |
+| SP-11 | SP-010053 | S1-010072 | 22.101 | 063 | | Rel-5 | A | Handling of interactions between applications requiring the access to UE resources | 5.1.0 | 5.2.0 | Service Clean up R99 |
+| SP-11 | SP-010054 | S1-010208 | 22.101 | 065 | | Rel-5 | A | PLMN name indication | 5.1.0 | 5.2.0 | TEI4 |
+| SP-11 | SP-010055 | S1-010179 | 22.101 | 067 | | Rel-5 | A | CR to 22.101 on Introduction of CPHS features | 5.1.0 | 5.2.0 | UICC1-CPHS |
+| SP-11 | SP-010056 | S1-010210 | 22.101 | 069 | | Rel-5 | A | Display of service provider name in the UE | 5.1.0 | 5.2.0 | TEI4 |
+| SP-11 | SP-010057 | S1-010250 | 22.101 | 070 | | Rel-5 | C | CR to 22.101 on Clarifications on IMS emergency call support | 5.1.0 | 5.2.0 | EMC1-PS |
+| SP-12 | SP-010262 | S1-010505 | 22.101 | 072 | | Rel-5 | A | Replacement of references to 23.121 for R4 onwards | 5.2.0 | 5.3.0 | TEI4 |
+| SP-12 | SP-010258 | S1-010574 | 22.101 | 073 | | Rel-5 | C | Subscription and Provisioning | 5.2.0 | 5.3.0 | TEI5 |
+| SP-12 | SP-010255 | S1-010577 | 22.101 | 075 | | Rel-5 | A | Addition of a Streaming paragraph | 5.2.0 | 5.3.0 | PSTREAM |
+| SP-12 | SP-010263 | S1-010351 | 22.101 | 077 | | Rel-5 | A | CS Multimedia fallback to speech | 5.2.0 | 5.3.0 | TEI4 |
+| SP-12 | SP-010253 | S1-010595 | 22.101 | 080 | | Rel-5 | A | Clarification of PLMN Name Indication and Service Provider Name Indication feature. | 5.2.0 | 5.3.0 | SPANME |
+| SP-13 | SP-010441 | S1-010832 | 22.101 | 084 | | Rel-5 | A | Addition of a statement on parameter storage on the SIM/USIM. | 5.3.0 | 5.4.0 | TEI4 |
+| SP-13 | SP-010436 | S1-010889 | 22.101 | 086 | 1 | Rel-5 | F | Definition of Home Environment | 5.3.0 | 5.4.0 | VHE1 |
+| SP-15 | SP-020052 | S1-020609 | 22.101 | 087 | | Rel-5 | B | CR 22.101 Rel.5 B Service change and fallback for UDI/RDI multimedia calls | 5.4.0 | 5.5.0 | SCUDIF |
+| SP-15 | SP-020049 | S1-020510 | 22.101 | 088 | | Rel-5 | C | CR to 22.101 on IMS access | 5.4.0 | 5.5.0 | 43000 |
+| SP-15 | SP-020051 | S1-020613 | 22.101 | 089 | | Rel-5 | C | CR to 22.101 on USIM support in Rel-5 GSM only terminals | 5.4.0 | 5.5.0 | UICC1 |
+| SP-15 | SP-020050 | S1-020658 | 22.101 | 090 | | Rel-5 | C | CR to 22.101 on Access to IMS services using ISIM
NOTE: special dispensation was given by SA #15 to allow some leeway on the section numbering. | 5.4.0 | 5.5.0 | TEI/ISIM |
+| SP-15 | SP-020045 | S1-020457 | 22.101 | 092 | - | Rel-5 | A | Editorial CR to correct terms and references | 5.4.0 | 5.5.0 | CORRECT |
+| SP-15 | SP-020126 | | 22.101 | 093 | | Rel-5 | F | Correction of references to obsolete SIP RFC 2543 IETF specification | 5.4.0 | 5.5.0 | IMS-CCR |
+| SP-16 | SP-020381 | | 22.101 | 095 | 1 | Rel-5 | F | CR to 22.101 v5.5.0 on REL5 clean up | 5.5.0 | 5.6.0 | IMS |
+| SP-16 | SP-020255 | S1-020848 | 22.101 | 096 | | Rel-6 | D | CR to 22.101 v5.5.0 on Editorial for REL6 | 5.5.0 | 6.0.0 | IMS |
+| SP-17 | SP-020557 | S1-021849 | 22.101 | 103 | | Rel-6 | F | Clarification of SIM support in Rel-6 | 6.0.0 | 6.1.0 | TEI4 |
+| SP-17 | SP-020557 | S1-021755 | 22.101 | 104 | | Rel-6 | B | CR to 22.101 Removal of implementation details for directory number in SMS and other services | 6.0.0 | 6.1.0 | TEI6 |
+| SP-17 | SP-020557 | S1-021775 | 22.101 | 105 | | Rel-6 | F | CR to 22.101 Rel-6 Clean up of IMS Rel 6 to re-instate requirements | 6.0.0 | 6.1.0 | IMS |
+| SP-18 | SP-020658 | S1-022064 | 22.101 | 107 | | Rel-6 | B | CR to 22.101 on IMS number portability rev of 1909 | 6.1.0 | 6.2.0 | IMS |
+| SP-18 | SP-020658 | S1-022119 | 22.101 | 108 | | Rel-6 | B | CR to 22.101 Rel 6 on | 6.1.0 | 6.2.0 | EMC1 |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|-------|---|--------------------------------------------------------------------------------------------------|-------|-------|------------|
+| | | | | | | | | Emergency calls | | | |
+| SP-18 | SP-020666 | S1-022263 | 22.101 | 109 | | Rel-6 | B | CR to 22.101 on WLAN interworking | 6.1.0 | 6.2.0 | WLAN |
+| SP-18 | SP-020651 | S1-022340 | 22.101 | 113 | | Rel-6 | A | CR to 22.101 on Support of SIM and USIM in REL-6 | 6.1.0 | 6.2.0 | TEI5 |
+| SP-19 | SP-030022 | S1-030215 | 22.101 | 114 | - | Rel-6 | B | Simultaneous connection to 3GPP systems and I-WLANs | 6.2.0 | 6.3.0 | WLAN-CR |
+| SP-19 | SP-030035 | S1-030269 | 22.101 | 115 | - | Rel-6 | B | Requirements for Network Sharing in Rel-6 | 6.2.0 | 6.3.0 | NTShar-CR |
+| SP-19 | SP-030148 | S1-030257 | 22.101 | 117 | - | Rel-6 | A | CR to 22.101 Rel 6 on SIM support | 6.2.0 | 6.3.0 | TEI5 |
+| SP-20 | SP-030351 | | 22.101 | 125 | 1 | Rel-6 | A | Alignment of Subscriber Identification requirements to current implementation | 6.3.0 | 6.4.0 | TEI5 |
+| SP-21 | SP-030457 | S1-030911 | 22.101 | 128 | - | Rel-6 | A | Clarification on USIM-based access to IMS | 6.4.0 | 6.5.0 | IMS |
+| SP-21 | SP-030492 | S1-031049 | 22.101 | 132 | | Rel-6 | C | Cleanup and modifications on identification of emergency numbers in 22.101 Rel-6 | 6.4.0 | 6.5.0 | EMC1 |
+| SP-21 | SP-030534 | S1-031061 | 22.101 | 134 | 1 | Rel-6 | A | Support of Release 4 SIM in Release 6 | 6.4.0 | 6.5.0 | TEI5 |
+| SP-22 | SP-030700 | S1-031339 | 22.101 | 135 | - | Rel-6 | B | Automatic Device Detection | 6.5.0 | 6.6.0 | TEI |
+| SP-22 | SP-030700 | S1-031342 | 22.101 | 136 | - | Rel-6 | C | Correction of Core Network emergency call requirements | 6.5.0 | 6.6.0 | EMC1 |
+| SP-22 | SP-030687 | S1-031344 | 22.101 | 137 | - | Rel-6 | C | Clarification of emergency call requirements | 6.5.0 | 6.6.0 | EMC1 |
+| SP-22 | SP-030790 | - | 22.101 | 141 | - | Rel-6 | A | Removal of unnecessary numbers from the ME default emergency number list (Rel-6) | 6.5.0 | 6.6.0 | EMC1 |
+| SP-23 | SP-040084 | S1-040198 | 22.101 | 145 | - | Rel-6 | A | Alignment to TS 31.102 on FDN/BDN unsupported terminal procedure. | 6.6.0 | 6.7.0 | TEI |
+| SP-23 | SP-040091 | S1-040215 | 22.101 | 146 | - | Rel-6 | B | Improvements to Circuit Switched Video and Voice Service procedures | 6.6.0 | 6.7.0 | CS-VVS |
+| SP-23 | SP-040101 | S1-040258 | 22.101 | 150 | - | Rel-6 | D | Extraction of redundant WLAN information – now in WLAN TS22.234 | 6.6.0 | 6.7.0 | WLAN |
+| SP-23 | SP-040101 | S1-040262 | 22.101 | 151 | - | Rel-6 | D | Extraction of redundant WLAN related simultaneous connection information [ now in WLAN TS22.234] | 6.6.0 | 6.7.0 | WLAN |
+| SP-24 | SP-040288 | S1-040427 | 22.101 | 152 | - | Rel-6 | F | Correction of UICC related text. | 6.7.0 | 6.8.0 | TEI |
+| SP-24 | SP-040292 | S1-040537 | 22.101 | 154 | - | Rel-6 | F | Editorial Correction of R5 reference | 6.7.0 | 6.8.0 | IMS2 |
+| SP-24 | SP-040301 | S1-040513 | 22.101 | 153 | - | Rel-7 | B | Termination of location privacy override for emergency calls | 6.7.0 | 7.0.0 | LCS2; EMC1 |
+| SP-27 | SP-050058 | S1-050161 | 22.101 | 158 | - | Rel-7 | A | Clean-up in Core Network Operator Name Indication section (22.101) | 7.0.0 | 7.1.0 | NTShar |
+| SP-27 | SP-050059 | S1-050252 | 22.101 | 160 | - | Rel-7 | A | Removal of Reference to TS 22.121 | 7.0.0 | 7.1.0 | TEI7 |
+| SP-28 | SP-050216 | S1-050519 | 22.101 | 163 | - | Rel-7 | A | Clarification on optionality of Service Provider Name indication | 7.1.0 | 7.2.0 | TEI-6 |
+| SP-28 | SP-050225 | S1-050581 | 22.101 | 164 | - | Rel-7 | B | Voice call continuity requirements | 7.1.0 | 7.2.0 | VCC |
+| SP-29 | SP-050522 | S1-050793 | 22.101 | 0165 | - | Rel-7 | F | Correction of emergency number example | 7.2.0 | 7.3.0 | TEI7 |
+| SP-29 | SP-050522 | S1-050873 | 22.101 | 0166 | - | Rel-7 | F | Requirements on the type of emergency | 7.2.0 | 7.3.0 | TEI7 |
+| SP-29 | SP-050522 | S1-050796 | 22.101 | 0167 | - | Rel-7 | C | Modification to chapter 4.2 on service capabilities | 7.2.0 | 7.3.0 | TEI7 |
+| SP-29 | SP-050518 | S1-050896 | 22.101 | 0168 | - | Rel-7 | F | Refinement of general description of VCC | 7.2.0 | 7.3.0 | VCC |
+| SP-29 | SP-050518 | S1-050897 | 22.101 | 0169 | - | Rel-7 | C | Charging requirements for voice call continuity | 7.2.0 | 7.3.0 | VCC |
+| SP-29 | SP-050518 | S1-050936 | 22.101 | 0171 | 1 | Rel-7 | C | Clarification of VCC Triggers | 7.2.0 | 7.3.0 | VCC |
+| SP-29 | SP-050522 | S1-050906 | 22.101 | 0172 | - | Rel-7 | F | Clarification on the identification of emergency numbers | 7.2.0 | 7.3.0 | EMC1 |
+| SP-29 | SP-050522 | S1-050883 | 22.101 | 0173 | - | Rel-7 | B | Provisioning parameters stored on USIM | 7.2.0 | 7.3.0 | TEI7 |
+| SP-29 | SP-050518 | S1-050934 | 22.101 | 0174 | - | Rel-7 | C | Supplementary Service | 7.2.0 | 7.3.0 | VCC |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|-------|---|----------------------------------------------------------------------------------------------------------------------|-------|-------|--------|
+| | | | | | | | | Requirements for VCC | | | |
+| SP-30 | SP-050750 | S1-051145 | 22.101 | 0176 | - | Rel-7 | F | Correcting reference to OMA DM and Client provisioning specifications | 7.3.0 | 7.4.0 | TEI7 |
+| SP-30 | SP-050746 | S1-051209 | 22.101 | 0177 | - | Rel-7 | F | Clarification of supplementary services requirements for VCC | 7.3.0 | 7.4.0 | VCC |
+| SP-30 | SP-050746 | S1-051220 | 22.101 | 0178 | - | Rel-7 | F | Clarification of VCC Triggers | 7.3.0 | 7.4.0 | VCC |
+| SP-30 | SP-050737 | S1-051236 | 22.101 | 0179 | - | Rel-7 | A | Introduction of Cell capability indicator | 7.3.0 | 7.4.0 | TEI6 |
+| SP-30 | SP-050805 | - | 22.101 | 0180 | 1 | Rel-7 | B | Emergency sip uri to be stored in MT | 7.3.0 | 7.4.0 | EMC1 |
+| SP-31 | SP-060207 | - | 22.101 | 0182 | 1 | Rel-8 | F | Inclusion of AIPN within the 3GPP service principles specification | 7.4.0 | 8.0.0 | AIPN |
+| SP-32 | SP-060448 | - | 22.101 | 0186 | 1 | Rel-8 | F | Corrections to align the Rel-8 and (latest) Rel-7 versions of TS 22.101 | 8.0.0 | 8.1.0 | TEI8 |
+| SP-32 | SP-060316 | S1-060561 | 22.101 | 0187 | - | Rel-8 | B | VCC Additional flexibility | 8.0.0 | 8.1.0 | VCC |
+| SP-32 | SP-060315 | S1-060621 | 22.101 | 0191 | - | Rel-8 | A | Clarification of IMS voice service | 8.0.0 | 8.1.0 | VCC |
+| SP-32 | SP-060435 | - | 22.101 | 0192 | 1 | Rel-8 | B | QoS Parameters Provisioning | 8.0.0 | 8.1.0 | TEI8 |
+| SP-32 | SP-060449 | - | 22.101 | 0193 | 2 | Rel-8 | B | High Speed Interface between the Terminal and the UICC | 8.0.0 | 8.1.0 | TEI8 |
+| SP-32 | SP-060320 | S1-060626 | 22.101 | 0194 | - | Rel-8 | F | Clarification on handling of emergency number | 8.0.0 | 8.1.0 | TEI-8 |
+| SP-33 | SP-060470 | S1-060939 | 22.101 | 0197 | - | Rel-8 | A | Clarification on Domain Selection for MO and MT Operations | 8.1.0 | 8.2.0 | TEI8 |
+| SP-33 | SP-060468 | S1-060950 | 22.101 | 0199 | - | Rel-8 | A | Emergency calls and ISIM | 8.1.0 | 8.2.0 | EMC1 |
+| SP-33 | SP-060472 | S1-060964 | 22.101 | 0200 | - | Rel-8 | B | Requirements for the determination of cell capability usage - when requested by CN | 8.1.0 | 8.2.0 | TEI8 |
+| SP-34 | SP-060777 | S1-061321 | 22.101 | 0195 | 3 | Rel-8 | C | Requirements for the addition of a data component to TS12 emergency calls and eCall MSD (data) transfer requirements | 8.2.0 | 8.3.0 | TEMCD |
+| SP-34 | SP-060773 | S1-061406 | 22.101 | 0201 | - | Rel-8 | B | Serving Environment / Mobile Virtual Network Identification | 8.2.0 | 8.3.0 | TEI8 |
+| SP-34 | SP-060765 | S1-061347 | 22.101 | 0204 | - | Rel-8 | A | Removal of IMS emergency call identifier | 8.2.0 | 8.3.0 | EMC1 |
+| SP-35 | SP-070130 | S1-070190 | 22.101 | 0205 | 1 | Rel-8 | D | Addition of Evolved 3GPP System description and corrections to references | 8.3.0 | 8.4.0 | SAE-R |
+| SP-35 | SP-070134 | S1-070299 | 22.101 | 0207 | 1 | Rel-8 | B | Registration in Densely-populated area | 8.3.0 | 8.4.0 | RED |
+| SP-36 | SP-070355 | S1-070673 | 22.101 | 0211 | 1 | Rel-8 | C | Graphic format of PLMN name | 8.4.0 | 8.5.0 | TEI8 |
+| SP-36 | SP-070354 | S1-070802 | 22.101 | 0214 | 1 | Rel-8 | A | Alignment of SPD1 definition between TS22.101 and TS31.102 | 8.4.0 | 8.5.0 | TEI5 |
+| SP-36 | SP-070472 | S1-070790 | 22.101 | 0215 | 2 | Rel-8 | F | Correction of the backward compatibility requirement for the HSP interface | 8.4.0 | 8.5.0 | TEI-8 |
+| SP-37 | SP-070661 | S1-071314 | 22.101 | 218 | 2 | Rel-8 | B | ICS Requirements – General | 8.5.0 | 8.6.0 | ICS-RA |
+| SP-37 | SP-070661 | S1-071315 | 22.101 | 221 | 2 | Rel-8 | B | ICS Requirements - Service Consistency | 8.5.0 | 8.6.0 | ICS-RA |
+| SP-37 | SP-070661 | S1-071316 | 22.101 | 222 | 2 | Rel-8 | B | ICS Requirements - Service Continuity | 8.5.0 | 8.6.0 | ICS-RA |
+| SP-37 | SP-070661 | S1-071317 | 22.101 | 225 | 2 | Rel-8 | B | ICS Requirements - IMS Services | 8.5.0 | 8.6.0 | ICS-RA |
+| SP-37 | SP-070662 | S1-070995 | 22.101 | 216 | 1 | Rel-8 | C | Clarification on graphic format of PLMN name | 8.5.0 | 8.6.0 | TEI8 |
+| SP-37 | SP-070676 | - | 22.101 | 217 | 4 | Rel-8 | B | Requirements for eCall | 8.5.0 | 8.6.0 | EData |
+| SP-38 | SP-070850 | S1-071712 | 22.101 | 0232 | 1 | Rel-8 | B | ICS - Clarification of Service Continuity | 8.6.0 | 8.7.0 | ICSRA |
+| SP-38 | SP-070850 | S1-071713 | 22.101 | 0233 | 1 | Rel-8 | B | ICS - Service Continuity Requirements | 8.6.0 | 8.7.0 | ICSRA |
+| SP-38 | SP-070850 | S1-071714 | 22.101 | 0234 | 1 | Rel-8 | B | ICS - Roaming Support | 8.6.0 | 8.7.0 | ICSRA |
+| SP-38 | SP-070850 | S1-071715 | 22.101 | 0235 | 1 | Rel-8 | B | Clarify UE requirements for ICS | 8.6.0 | 8.7.0 | ICS-RA |
+| SP-38 | SP-070861 | S1-071932 | 22.101 | 0229 | 2 | Rel-8 | B | Requirements for Emergency Call-Back | 8.6.0 | 8.7.0 | TEI8 |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|--------------------------------------------------------------------------------|-------|--------|--------------------|
+| SP-38 | SP-070862 | S1-071927 | 22.101 | 0241 | 2 | Rel-8 | B | CS IP Interconnection requirement | 8.6.0 | 8.7.0 | IPINTERC |
+| SP-39 | SP-080036 | S1-080309 | 22.101 | 0237 | 6 | Rel-8 | B | Requirements for "In Case of Emergency" (ICE) information | 8.7.0 | 8.8.0 | ICE |
+| SP-39 | SP-080042 | S1-080296 | 22.101 | 0250 | 1 | Rel-8 | F | Update the related contents about "Evolved Packet System" | 8.7.0 | 8.8.0 | AIPN-SAE |
+| SP-39 | SP-080041 | S1-080297 | 22.101 | 0251 | 1 | Rel-8 | F | CS multimedia calls | 8.7.0 | 8.8.0 | TEI8 |
+| SP-39 | SP-080041 | S1-080298 | 22.101 | 0252 | 1 | Rel-8 | D | correction of wrong referencing | 8.7.0 | 8.8.0 | TEI8 |
+| SP-39 | SP-080032 | S1-080314 | 22.101 | 0253 | 2 | Rel-8 | B | Requirements for transfer for data during emergency calls | 8.7.0 | 8.8.0 | EData |
+| SP-39 | SP-080032 | S1-080266 | 22.101 | 0254 | 1 | Rel-8 | B | Requirements for the transfer of eCall Minimum Set of Data | 8.7.0 | 8.8.0 | EData |
+| SP-39 | SP-080043 | S1-080337 | 22.101 | 0255 | 2 | Rel-8 | B | RAT indicator | 8.7.0 | 8.8.0 | TEI8 |
+| SP-39 | SP-080039 | S1-080287 | 22.101 | 0256 | 1 | Rel-8 | B | ICS requirement for roaming | 8.7.0 | 8.8.0 | ICSRA |
+| SP-39 | SP-080040 | S1-080237 | 22.101 | 0262 | 1 | Rel-8 | B | Additional requirements for CS IP interconnection | 8.7.0 | 8.8.0 | IPINTERC |
+| SP-39 | SP-080043 | S1-080299 | 22.101 | 0263 | 1 | Rel-8 | B | Addition of Unique Device Identifier to Calling Line Identification | 8.7.0 | 8.8.0 | TEI8 |
+| SP-39 | SP-080040 | S1-080327 | 22.101 | 0265 | 1 | Rel-8 | B | Clarification of requirements for CS IP interconnection | 8.7.0 | 8.8.0 | IPINTERC |
+| SP-40 | SP-080308 | S1-080746 | 22.101 | 0267 | 3 | Rel-8 | F | Emergency Call Interaction | 8.8.0 | 8.9.0 | EMC1 |
+| SP-40 | SP-080299 | S1-080581 | 22.101 | 0269 | 1 | Rel-8 | C | eCall call back requirements clarification | 8.8.0 | 8.9.0 | EDATA |
+| SP-40 | SP-080298 | S1-080735 | 22.101 | 0270 | 3 | Rel-8 | F | Common IMS Proposals - Requirements for Emergency Calls | 8.8.0 | 8.9.0 | CIMS_3G PP2 |
+| SP-40 | SP-080306 | S1-080715 | 22.101 | 0271 | 1 | Rel-8 | F | Correction of reference for PLMN architecture | 8.8.0 | 8.9.0 | AIPN-SAE |
+| SP-40 | SP-080299 | S1-080714 | 22.101 | 0272 | 1 | Rel-8 | F | Corrections to general requirements for emergency calls | 8.8.0 | 8.9.0 | EData |
+| SP-40 | SP-080308 | S1-080560 | 22.101 | 0274 | - | Rel-8 | F | Clarification of IMS Emergency Calls | 8.8.0 | 8.9.0 | EMC1 |
+| SP-40 | SP-080299 | S1-080743 | 22.101 | 0275 | 1 | Rel-8 | C | Reconfigurable eCall only terminal access to test and reconfiguration services | 8.8.0 | 8.9.0 | EDATA |
+| SP-40 | SP-080302 | S1-080705 | 22.101 | 0276 | - | Rel-8 | F | Correction of ICE requirements | 8.8.0 | 8.9.0 | ICE |
+| SP-40 | SP-080311 | S1-080774 | 22.101 | 0268 | 3 | Rel-9 | B | Requirements for Service Alignment and Migration | 8.8.0 | 9.0.0 | ETWS-S1 |
+| SP-41 | SP-080498 | S1-082192 | 22.101 | 0282 | 1 | Rel-9 | F | Clarification on IMS services supported by ICS | 9.0.0 | 9.1.0 | ICSRA |
+| SP-41 | SP-080643 | - | 22.101 | 0280 | 2 | Rel-9 | F | RED optimization of location update | 9.0.0 | 9.1.0 | RED |
+| SP-42 | SP-080884 | | 22.101 | 0290 | 6 | Rel-9 | A | ICS Service Continuity | 9.1.0 | 9.2.0 | CIMS8 |
+| SP-42 | SP-080779 | S1-084415 | 22.101 | 281 | 2 | Rel-9 | B | User Data Convergence Requirements | 9.1.0 | 9.2.0 | UDC |
+| SP-42 | SP-080781 | S1-084177 | 22.101 | 0283 | 2 | Rel-9 | F | VCC for emergency calls | 9.1.0 | 9.2.0 | IMS_EME R_GPRS_EPS |
+| SP-42 | SP-080784 | S1-084424 | 22.101 | 0290 | 3 | Rel-9 | C | ICS Service Continuity | 9.1.0 | 9.2.0 | TEI9 |
+| SP-42 | SP-080783 | S1-084404 | 22.101 | 0299 | 3 | Rel-9 | B | UICC applications access to IMS | 9.1.0 | 9.2.0 | TEI9 |
+| SP-42 | SP-080781 | S1-084096 | 22.101 | 300 | - | Rel-9 | F | Make IMS emergency calls available in all access systems | 9.1.0 | 9.2.0 | TEI9 |
+| SP-43 | SP-090079 | S1-090174 | 22.101 | 0307 | 1 | Rel-9 | A | Clarification and enhancement of ciphering indicator feature | 9.2.0 | 9.3.0 | TEI9 |
+| SP-44 | SP-090377 | S1-091407 | 22.101 | 0312 | 4 | Rel-9 | F | Domain selection for emergency call | 9.3.0 | 9.4.0 | IMS_EME R_GPRS_EPS |
+| SP-44 | SP-090369 | S1-091393 | 22.101 | 0313 | - | Rel-9 | A | eCall - PSAP acknowledgement to the IVS | 9.3.0 | 9.4.0 | Edata |
+| SP-45 | SP-090475 | S1-093290 | 22.101 | 0315 | 1 | Rel-9 | A | Minimise delay to emergency voice calls | 9.4.0 | 9.5.0 | EDATA |
+| SP-45 | SP-090480 | S1-093282 | 22.101 | 321 | 1 | Rel-9 | F | Domain selection for emergency call | 9.4.0 | 9.5.0 | IMS_EME R_GPRS_EPS |
+| SP-45 | SP-090483 | S1-093286 | 22.101 | 0316 | 1 | Rel-10 | F | Add reference to MSD specification | 9.4.0 | 10.0.0 | EDATA |
+| SP-45 | SP-090484 | S1-093341 | 22.101 | 0320 | 4 | Rel-10 | B | Selected IP Traffic Offload | 9.4.0 | 10.0.0 | LIPA_SIP |
+
+| | | | | | | | | | | | |
+|-------|-----------|------------|--------|------|---|--------|---|-----------------------------------------------------------------------------------------------------------|--------|--------|--------------------|
+| | | | | | | | | | | | TO |
+| SP-45 | SP-090483 | S1-093261 | 22.101 | 322 | 1 | Rel-10 | F | Clarification of emergency call back requirements | 9.4.0 | 10.0.0 | TEI10 |
+| SP-46 | SP-090887 | S1-094259 | 22.101 | 0336 | 1 | Rel-10 | A | Providing eCall indication to the PSAP | 10.0.0 | 10.1.0 | EDATA |
+| SP-46 | SP-090836 | S1-094262 | 22.101 | 0338 | - | Rel-10 | A | Remove requirement for operator determined eCall call-back duration. | 10.0.0 | 10.1.0 | EDATA |
+| SP-46 | SP-090842 | S1-094272 | 22.101 | 0330 | 1 | Rel-10 | A | User data repository shall be possible to be shared among different PLMNs that have trusted relationships | 10.0.0 | 10.1.0 | UDC |
+| SP-46 | SP-090844 | S1-094499 | 22.101 | 0327 | 2 | Rel-10 | A | Use of GTT-IP for IMS emergency calls (mirror) | 10.0.0 | 10.1.0 | TEI9 |
+| SP-46 | SP-090846 | S1-094496 | 22.101 | 0328 | 1 | Rel-10 | B | ICS Enhancements | 10.0.0 | 10.1.0 | TEI10 |
+| SP-46 | SP-090849 | S1-094300 | 22.101 | 0325 | 3 | Rel-10 | B | Roaming and Mobility aspects for Selected IP Traffic Offload | 10.0.0 | 10.1.0 | LIPA_SIP TO |
+| SP-47 | SP-100187 | S1-100321 | 22.101 | 0339 | 2 | Rel-10 | B | SIPTO requirements common for macro network and H(e)NB subsystems | 10.1.0 | 10.2.0 | LIPA_SIP TO |
+| SP-47 | SP-100188 | S1-100445 | 22.101 | 0332 | 6 | Rel-10 | C | Clarification to Emergency call selection prioritization | 10.1.0 | 10.2.0 | TEI10 |
+| SP-47 | SP-100188 | S1-100442 | 22.101 | 0340 | 1 | Rel-10 | C | Clarification on ICS wrt data (CS) and fax | 10.1.0 | 10.2.0 | TEI10 |
+| SP-47 | SP-100191 | S1-100431 | 22.101 | 0343 | 2 | Rel-10 | B | IMS emergency call enhancements | 10.1.0 | 10.2.0 | IESE |
+| SP-48 | SP-100431 | S1-101060r | 22.101 | 0347 | 6 | Rel-10 | B | Addition of Requirement for UDC Data Model | 10.2.0 | 10.3.0 | TEI10 |
+| SP-48 | SP-100401 | S1-101067 | 22.101 | 0350 | - | Rel-10 | F | Correction of reference | 10.2.0 | 10.3.0 | IESE |
+| SP-49 | SP-100585 | S1-102403 | 22.101 | 0353 | 2 | Rel-11 | B | SIPTO mobility/continuity | 10.3.0 | 11.0.0 | SIPTO_S C |
+| SP-51 | SP-110168 | S1-110088 | 22.101 | 0360 | - | Rel-11 | F | Clarification on Service Continuity for SIPTO | 11.0.0 | 11.1.0 | SIPTO_S C |
+| SP-52 | SP-110373 | S1-111410 | 22.101 | 0367 | 3 | Rel-11 | B | IMS emergency call requirements for additional media types | 11.1.0 | 11.2.0 | NOVES |
+| SP-52 | SP-110376 | S1-111209 | 22.101 | 0369 | - | Rel-11 | D | Removing text discrepancy between Rel-10 and Rel-11 for UDC Data Model | 11.1.0 | 11.2.0 | TEI11 |
+| SP-52 | SP-110418 | - | 22.101 | 0372 | 2 | Rel-11 | A | IMS emergency calls | 11.1.0 | 11.2.0 | IMS_EME R_GPRS_EPS |
+| | | | | | | | | Correction of typo on cover page | 11.2.0 | 11.2.1 | |
+| SP-53 | SP-110582 | S1-112392 | 22.101 | 0373 | 1 | Rel-11 | F | SIPTO in the Mobile Operator Network and Local Residential/Enterprise Network | 11.2.0 | 11.3.0 | TEI11 |
+| SP-53 | SP-110576 | S1-112101 | 22.101 | 0379 | - | Rel-11 | B | IMS emergency call support with other media handover considerations | 11.2.0 | 11.3.0 | NOVES |
+| SP-53 | SP-110576 | S1-112344 | 22.101 | 0380 | 1 | Rel-11 | B | Notification of IMS emergency call support with other media | 11.2.0 | 11.3.0 | NOVES |
+| SP-53 | SP-110576 | S1-112350 | 22.101 | 0385 | 3 | Rel-11 | B | Domain Selection for IMS emergency calls with additional media types | 11.2.1 | 11.3.0 | NOVES |
+| SP-53 | SP-110579 | S1-112385 | 22.101 | 0374 | 1 | Rel-11 | F | SIPTO Service Continuity | 11.2.0 | 11.3.0 | SIPTO_S C |
+| SP-53 | SP-110579 | S1-112393 | 22.101 | 0378 | 2 | Rel-11 | C | Clarification on collection of traffic and signalling for SIPTO | 11.2.0 | 11.3.0 | SIPTO_S C |
+| SP-53 | SP-110582 | S1-112025 | 22.101 | 0376 | - | Rel-11 | F | Correction of clause numbers and editorial corrections | 11.2.1 | 11.3.0 | TEI11 |
+| SP-53 | SP-110651 | S1-112328 | 22.101 | 0383 | 3 | Rel-11 | F | Moving "Network provided destination for uplink data" requirement from 22.368 into 22.101 | 11.2.1 | 11.3.0 | SIMTC |
+| SP-53 | SP-110651 | S1-112329 | 22.101 | 0384 | 4 | Rel-11 | F | Moving PS-Only requirements from 22.368 into 22.101 | 11.2.1 | 11.3.0 | SIMTC |
+| SP-54 | SP-110811 | S1-113245 | 22.101 | 0387 | 1 | Rel-11 | F | IMS Multimedia Emergency Session support for UEs in Limited Service Mode | 11.3.0 | 11.4.0 | NOVES |
+| SP-54 | SP-110811 | S1-113249 | 22.101 | 0388 | 2 | Rel-11 | F | Correction and removal of inconsistencies to IMS Emergency call when using other media | 11.3.0 | 11.4.0 | NOVES |
+
+| | | | | | | | | | | | |
+|-------|-----------|------------|--------|------|---|--------|---|----------------------------------------------------------------------------------------------------------|--------|--------|----------|
+| SP-54 | SP-110811 | S1-113248 | 22.101 | 0390 | 2 | Rel-11 | F | Indication of supported media during an IMS multimedia emergency session | 11.3.0 | 11.4.0 | NOVES |
+| SP-54 | SP-110811 | S1-113250 | 22.101 | 0391 | 1 | Rel-11 | F | Handover of other media to networks that do not support IMS emergency voice calls | 11.3.0 | 11.4.0 | NOVES |
+| SP-54 | SP-110873 | S1-113093r | 22.101 | 0392 | 2 | Rel-11 | F | Media allowed on callback from PSAP | 11.3.0 | 11.4.0 | NOVES |
+| SP-54 | SP-110811 | S1-113094 | 22.101 | 0393 | - | Rel-11 | F | Routing IMS multimedia sessions towards the PSAP | 11.3.0 | 11.4.0 | NOVES |
+| SP-54 | SP-110813 | S1-113098 | 22.101 | 0394 | - | Rel-11 | B | PS additional number | 11.3.0 | 11.4.0 | TEI11 |
+| SP-55 | SP-120103 | S1-120256 | 22.101 | 0401 | 1 | Rel-11 | F | PS only subscriptions with SMS support | 11.4.0 | 11.5.0 | SIMTC |
+| SP-55 | SP-120105 | S1-120346 | 22.101 | 0400 | 4 | Rel-12 | B | Introduction of Small Data Applications requirements | 11.4.0 | 12.0.0 | TEI12 |
+| SP-56 | SP-120286 | S1-121314 | 22.101 | 0409 | 1 | Rel-12 | A | Emergency calls from non CSG members in CSG cells | 12.0.0 | 12.1.0 | EHNB |
+| SP-56 | SP-120288 | S1-121396 | 22.101 | 0412 | 1 | Rel-12 | A | Clarification of PS additional numbers requirement | 12.0.0 | 12.1.0 | TEI11 |
+| SP-56 | SP-120288 | S1-121392 | 22.101 | 0415 | - | Rel-12 | A | Modification of how ME treats emergency call type(s) | 12.0.0 | 12.1.0 | TEI11 |
+| SP-57 | SP-120519 | S1-122463 | 22.101 | 0423 | 1 | Rel-12 | A | Correction of UE mandatory features | 12.1.0 | 12.2.0 | TEI8 |
+| SP-57 | SP-120528 | S1-122221 | 22.101 | 0416 | 3 | Rel-12 | B | Definitions for integration of Single Sign-On (SSO) frameworks with 3GPP networks | 12.1.0 | 12.2.0 | SSO_int |
+| SP-57 | SP-120528 | S1-122433 | 22.101 | 0417 | 2 | Rel-12 | B | Requirements for integration of Single Sign-On (SSO) frameworks with 3GPP networks | 12.1.0 | 12.2.0 | SSO_int |
+| SP-58 | SP-120868 | S1-124504 | 22.101 | 0433 | 5 | Rel-12 | D | MSISDN-less SMS Handling | 12.2.0 | 12.3.0 | MTCe-SRM |
+| SP-58 | SP-120919 | S1-124416 | 22.101 | 0434 | 4 | Rel-12 | B | Addition of UPCON Requirements | 12.2.0 | 12.3.0 | UPCON |
+| SP-59 | SP-130106 | S1-131033 | 22.101 | 0444 | - | Rel-12 | D | Clarification of RAN user plane congestion definition | 12.3.0 | 12.4.0 | UPCON |
+| SP-59 | SP-130112 | S1-131226 | 22.101 | 0445 | 3 | Rel-12 | B | Add Requirement on emergency IM CN subsystem | 12.3.0 | 12.4.0 | ESID |
+| SP-61 | SP-130413 | S1-134180 | 22.101 | 0463 | 1 | Rel-13 | B | E-UTRAN Sharing Enhancements | 12.4.0 | 13.0.0 | RSE |
+| SP-62 | SP-130601 | S1-135293 | 22.101 | 0464 | 2 | Rel-13 | D | Editorial fixes to RAN Sharing Enhancements | 13.0.0 | 13.1.0 | RSE |
+| SP-62 | SP-130601 | S1-135309 | 22.101 | 0465 | 3 | Rel-13 | B | Support for Load Balancing in Shared E-UTRAN | 13.0.0 | 13.1.0 | RSE |
+| SP-62 | SP-130601 | S1-135310 | 22.101 | 0466 | 3 | Rel-13 | B | Additional RAN Sharing Requirements | 13.0.0 | 13.1.0 | RSE |
+| SP-62 | SP-130601 | S1-135294 | 22.101 | 0468 | 2 | Rel-13 | C | Clarification of Hosting E-UTRAN Operator role | 13.0.0 | 13.1.0 | RSE |
+| SP-62 | SP-130601 | S1-135313 | 22.101 | 0469 | 3 | Rel-13 | C | Adding explanatory text to requirements on E-UTRAN Sharing | 13.0.0 | 13.1.0 | RSE |
+| SP-62 | SP-130601 | S1-135312 | 22.101 | 0470 | 3 | Rel-13 | B | Enabling Dynamic capacity negotiation | 13.0.0 | 13.1.0 | RSE |
+| SP-63 | SP-140066 | S1-140230 | 22.101 | 0471 | 1 | Rel-13 | C | RSE load balancing under EPC congestion situations | 13.1.0 | 13.2.0 | RSE |
+| SP-65 | SP-140501 | S1-143604 | 22.101 | 0473 | 5 | Rel-13 | B | Exposure of network service and capabilities to 3rd party | 13.2.0 | 13.3.0 | SEES |
+| SP-65 | SP-140508 | S1-143607 | 22.101 | 0476 | 4 | Rel-13 | B | Co-ordinated SIPTO Change of P-GW | 13.2.0 | 13.3.0 | CSIPTO |
+| SP-65 | SP-140510 | S1-143279 | 22.101 | 0479 | 1 | Rel-13 | C | Definition of (S)Gi-LAN | 13.2.0 | 13.3.0 | FMSS |
+| SP-65 | SP-140510 | S1-143556 | 22.101 | 0478 | 3 | Rel-13 | B | Requirements for Flexible Mobile Steering Service | 13.2.0 | 13.3.0 | FMSS |
+| SP-66 | SP-140755 | S1-144611 | 22.101 | 481 | 2 | Rel-13 | B | GERAN & UTRAN Sharing, change to the title of Section 28 and update to clause 28.1 | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140755 | S1-144617 | 22.101 | 482 | 2 | Rel-13 | B | GERAN & UTRAN Sharing, new clauses 28.3 and 28.3.1 (Allocation of Shared GERAN & UTRAN requirements). | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140755 | S1-144618 | 22.101 | 483 | 2 | Rel-13 | B | GERAN & UTRAN Sharing, new clause 28.3.2 (OA&M access to the shared RAN). | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140755 | S1-144533 | 22.101 | 484 | 1 | Rel-13 | B | GERAN & UTRAN Sharing, new clause 28.3.3 (Generation and retrieval of usage and accounting information). | 13.3.0 | 13.4.0 | GUSH |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|-----------------------------------------------------------------------------------------|--------|--------|-----------|
+| SP-66 | SP-140755 | S1-144534 | 22.101 | 485 | 1 | Rel-13 | B | GERAN & UTRAN Sharing, new clause 28.3.4 (MDT Collection) | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140755 | S1-144640 | 22.101 | 486 | 3 | Rel-13 | B | GERAN & UTRAN Sharing, new clause 28.3.5 (PWS Support) | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140755 | S1-144619 | 22.101 | 487 | 2 | Rel-13 | B | GERAN & UTRAN Sharing, new clause 28.3.6 (Support for load balancing). | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140755 | S1-144636 | 22.101 | 488 | 3 | Rel-13 | B | GERAN & UTRAN Sharing, new clause 28.3.7 (Dynamic capacity negotiation). | 13.3.0 | 13.4.0 | GUSH |
+| SP-66 | SP-140781 | S1-144528 | 22.101 | 493 | - | Rel-13 | A | eCall mode of operation | 13.3.0 | 13.4.0 | EDATA |
+| SP-66 | SP-140751 | S1-144556 | 22.101 | 494 | - | Rel-13 | F | Align the MTC monitoring requirements with Service Exposure requirements | 13.3.0 | 13.4.0 | TEI13 |
+| SP-67 | SP-150039 | S1-150214 | 22.101 | 495 | 2 | Rel-13 | F | Update of Definitions | 13.4.0 | 13.5.0 | GUSH |
+| SP-68 | SP-150272 | S1-151547 | 22.101 | 499 | 3 | Rel-14 | C | Requirement to support domain selection between VoLTE and CDMA CS | 13.5.0 | 14.0.0 | eDSVCC |
+| SP-68 | SP-150276 | S1-151536 | 22.101 | 496 | 3 | Rel-14 | B | Update of eCall definition to include IMS emergency call based eCall | 13.5.0 | 14.0.0 | EIEI |
+| SP-68 | SP-150276 | S1-151537 | 22.101 | 497 | 2 | Rel-14 | B | Support of IMS emergency calls in ICS | 13.5.0 | 14.0.0 | EIEI |
+| SP-68 | SP-150276 | S1-151538 | 22.101 | 498 | 2 | Rel-14 | B | Update of transfer of MSD to include IMS emergency call based eCall | 13.5.0 | 14.0.0 | EIEI |
+| SP-69 | SP-150539 | S1-152457 | 22.101 | 501 | 1 | Rel-14 | B | Enhancements for control of traffic from UE-based applications toward associated server | 14.0.0 | 14.1.0 | CATS |
+| SP-71 | SP-160100 | S1-160473 | 22.101 | 0508 | 2 | Rel-14 | B | Requirements for enhancements on User Location Reporting Support | 14.1.0 | 14.2.0 | eULRS |
+| SP-71 | SP-160112 | S1-160300 | 22.101 | 0509 | 2 | Rel-14 | B | Paging policy selection criteria requirements in LTE | 14.1.0 | 14.2.0 | PPEPO_LTE |
+| SP-71 | SP-160110 | S1-160474 | 22.101 | 0510 | 4 | Rel-14 | B | Requirements for enhanced TV service | 14.1.0 | 14.2.0 | EnTV |
+| SP-71 | SP-160096 | S1-160173 | 22.101 | 0511 | | Rel-14 | F | Clarification of relationship between GTT and Real Time Text | 14.1.0 | 14.2.0 | TEI14 |
+| SP-71 | SP-160116 | S1-160541 | 22.101 | 0512 | 2 | Rel-14 | B | Accounting for usage when using unlicensed access networks | 14.1.0 | 14.2.0 | USOS |
+| SP-71 | SP-160114 | S1-160302 | 22.101 | 0513 | | Rel-14 | B | Requirements for supporting third-party owned (S)Gi-LAN service | 14.1.0 | 14.2.0 | eFMSS |
+| SP-72 | SP-160353 | S1-161594 | 22.101 | 518 | 1 | Rel-14 | A | Addition of Cellular IoT non-IP transport to exposed services and capabilities | 14.2.0 | 14.3.0 | SEES |
+| SP-73 | SP-160541 | S1-162532 | 22.101 | 0519 | 1 | Rel-14 | F | Clarification of mobility management procedures for UEs in eCall mode | 14.3.0 | 14.4.0 | EIEI |
+| SP-74 | SP-160888 | S1-163032 | 22.101 | 0520 | | Rel-14 | F | Update of eCall MSD reference | 14.4.0 | 14.5.0 | TEI14 |
+| SP-74 | SP-160888 | S1-163392 | 22.101 | 0521 | 3 | Rel-14 | F | Support of Emergency sessions over WLAN | 14.4.0 | 14.5.0 | TEI14 |
+| SP-74 | SP-160889 | S1-163452 | 22.101 | 0522 | 3 | Rel-14 | F | Clarification of the consequences of eCall second attempts on another domain | 14.4.0 | 14.5.0 | EIEI |
+| SP-75 | SP-170149 | S1-171437 | 22.101 | 0524 | 2 | Rel-14 | A | Alignment of UPCON Service Requirements | 14.5.0 | 14.6.0 | UPCON |
+| SP-75 | SP-170154 | S1-171445 | 22.101 | 0525 | 2 | Rel-14 | F | Support of Emergency sessions over WLAN | 14.5.0 | 14.6.0 | TEI14 |
+| SP-75 | SP-170155 | S1-171275 | 22.101 | 0526 | 1 | Rel-15 | C | Addition of 5G RAN sharing | 14.5.0 | 15.0.0 | SMARTE R |
+| SP-75 | SP-170162 | S1-171415 | 22.101 | 0528 | 1 | Rel-15 | B | Enhancement of the service exposure for background data transfer | 14.5.0 | 15.0.0 | eBT |
+| SP-75 | SP-170247 | S1-171440 | 22.101 | 0530 | | Rel-15 | F | Addition of informing PS Data Off state to Third-party | 14.5.0 | 15.0.0 | TEI15 |
+| SP-76 | SP-170437 | S1-172231 | 22.101 | 0535 | 1 | Rel-15 | A | Adding Device Triggering to the Exposed Services and Capabilities | 15.0.0 | 15.1.0 | SEES |
+| SP-76 | SP-170443 | S1-172281 | 22.101 | 0532 | 2 | Rel-15 | F | Correction of 5G-RAN sharing => not implementable, written on another spec (22.011) | 15.0.0 | 15.1.0 | SMARTE R |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|--------------------------------------------------------------------------------------------------------|--------|--------|--------|
+| SP-76 | SP-170447 | S1-172235 | 22.101 | 0536 | 1 | Rel-15 | B | Requirements for access to restricted local operator services | 15.0.0 | 15.1.0 | PARLOS |
+| SP-77 | SP-170694 | S1-173451 | 22.101 | 0537 | 1 | Rel-15 | D | Remove restricted local operator services definition | 15.1.0 | 15.2.0 | PARLOS |
+| SP-77 | SP-170692 | S1-173260 | 22.101 | 0539 | 1 | Rel-15 | F | Correction of the term "5G-RAN" to "NG-RAN" in RAN sharing | 15.1.0 | 15.2.0 | TEI15 |
+| SP-78 | SP-170983 | S1-174023 | 22.101 | 0541 | | Rel-15 | A | Support of Emergency sessions over WLAN | 15.2.0 | 15.3.0 | SEW2 |
+| SP-78 | SP-170988 | S1-174558 | 22.101 | 0542 | 2 | Rel-15 | F | Clarification of PARLOS indicator and use without a UICC | 15.2.0 | 15.3.0 | PARLOS |
+| SP-79 | SP-180132 | S1-180601 | 22.101 | 0544 | 2 | Rel-15 | F | Requiring the UE to set the restricted local operator service call type indicator when requesting RLOS | 15.3.0 | 15.4.0 | PARLOS |
+| SP-80 | SP-180305 | S1-181178 | 22.101 | 0545 | | Rel-15 | F | Alignment of requirements for access to restricted local operator services | 15.4.0 | 15.5.0 | PARLOS |
+| SP-80 | SP-180305 | S1-181396 | 22.101 | 0546 | 1 | Rel-16 | F | Alignment of requirements for access to restricted local operator services | 15.4.0 | 16.0.0 | PARLOS |
+| SP-81 | SP-180754 | S1-182687 | 22.101 | 0552 | | Rel-16 | A | Local emergency numbers and emergency call types for use in the IM CN subsystem handling | 16.0.0 | 16.1.0 | TEI15 |
+| SP-81 | SP-180767 | S1-182704 | 22.101 | 0549 | 2 | Rel-16 | B | UIA Service Requirements | 16.0.0 | 16.1.0 | UIA |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2019-06 | SA#84 | SP-190567 | 0558 | 3 | A | Solving user comprehension of network name in foreign language | 16.2.0 |
+| 2019-09 | SA#85 | SP-190810 | 0559 | 4 | B | Service requirements for enabling Multi-USIM devices support | 17.0.0 |
+| 2019-09 | SA#85 | SP-190810 | 0560 | 4 | B | Support of Emergency Services for Multi-USIM Devices | 17.0.0 |
+| 2019-12 | SP-86 | SP-191026 | 0562 | | F | Clarify that emergency call-back is a regulatory requirement | 17.1.0 |
+| 2019-12 | SP-86 | SP-191026 | 0564 | 1 | F | Description for supporting MUSIM UE | 17.1.0 |
+| 2019-12 | SP-86 | SP-191035 | 0563 | 3 | B | IMS emergency requirement for NPN | 17.1.0 |
+| 2020-07 | SA#88e | SP-200569 | 0566 | 1 | F | Correction of UICC definition and references | 17.2.0 |
+| 2020-12 | SA#90e | SP-201041 | 570 | 1 | B | Service requirements for enhancing SFC service support | 18.0.0 |
+| 2021-03 | SA#91e | SP-210200 | 572 | | A | Correction of reference to "Master Operator" and use of "Hosting E-UTRAN Operator" | 18.1.0 |
+| 2021-04 | - | - | - | - | - | Numbering of references corrected | 18.1.1 |
+| 2021-09 | SA#93e | SP-211096 | 0575 | 1 | A | Handling of emergency numbers in non-public networks | 18.2.0 |
+| 2021-09 | SA#93e | SP-211096 | 0576 | | D | Correction of 'air interface' terminology | 18.2.0 |
+| 2021-12 | SP-94 | SP-211494 | 0578 | 1 | B | Addition of PIN requirement for credentials provisioning | 18.3.0 |
+| 2022-06 | SA#96 | SP-220434 | 582 | | D | Clean-up of the references for quality improvement | 18.4.0 |
+| 2022-06 | SA#96 | SP-220429 | 583 | 1 | B | SMS over IMS to emergency response centre | 18.4.0 |
+| 2022-06 | SA#96 | SP-220434 | 584 | 1 | F | Emergency service support over ProSe Relays | 18.4.0 |
+| 2023-06 | SA#100 | SP-230525 | 0588 | 1 | A | Aligning the RAN sharing related definitions for quality improvement | 18.5.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22104/04867b54e8cdb31a034edbb472a41162_img.jpg b/marked/Rel-18/22_series/22104/04867b54e8cdb31a034edbb472a41162_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6e9a2d7549dcad118c24129cfc6d1ee9e58c14e
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/04867b54e8cdb31a034edbb472a41162_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da09613fa8a3c0b08e799245193a79af4dec7b0a554afcdc5ed3930febaa6369
+size 44539
diff --git a/marked/Rel-18/22_series/22104/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-18/22_series/22104/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de568d40bd542e1d96f2f5d45aa650dc3aa47397
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3447dfefe84f981a7a008e17ec5ac369e86542e236e015c417d63c3f45ec33a9
+size 61902
diff --git a/marked/Rel-18/22_series/22104/108264c3e265fe4696520ddbc3a3601e_img.jpg b/marked/Rel-18/22_series/22104/108264c3e265fe4696520ddbc3a3601e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..edfb41125f5be1180e73198ef31367f5401d0ae3
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/108264c3e265fe4696520ddbc3a3601e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e0c9d88a01e143ba3ec89ab949967931fc3c2e1e9757a1b641ffa3c6c7697f3
+size 19175
diff --git a/marked/Rel-18/22_series/22104/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-18/22_series/22104/18003425d0e8638dde4acc9c5c468c5c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dd80e6710aa63880ee1453946dc66223abcac760
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/18003425d0e8638dde4acc9c5c468c5c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0eb3476ecfba77899c31103e895fb0b891b2aa7f04b26d3b0b788aa13e6fcea9
+size 59373
diff --git a/marked/Rel-18/22_series/22104/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-18/22_series/22104/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2e5b9b9001e222018099292b7217c971f0e1311
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5abdf78744b76c954ba87ea4c4c0148915884112c3717676487b60bfb01d147a
+size 65897
diff --git a/marked/Rel-18/22_series/22104/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-18/22_series/22104/195611c20b2dc7ed0fa3033392e22908_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c29fd1164396360f51b1eb4c4b8fd719023e525
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/195611c20b2dc7ed0fa3033392e22908_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89f47f5c8b1262838dbb642dd65d290cd2df940af7e314b37c907ee8e0c5a7f1
+size 51114
diff --git a/marked/Rel-18/22_series/22104/26d0c0482ad7f4f026a58ecc0b468980_img.jpg b/marked/Rel-18/22_series/22104/26d0c0482ad7f4f026a58ecc0b468980_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f163c9ccaa89f95e78c20003ea9a8920d27dae54
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/26d0c0482ad7f4f026a58ecc0b468980_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ce6b27537ae7d059e2860ad5f07878b58c7267b6e54fe1c383714d47c6e3682
+size 52141
diff --git a/marked/Rel-18/22_series/22104/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/22_series/22104/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1f43c6fed88382f36f410ca2de646c735e9e962
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e90e743a040197233b261793db77a0e73fb8b3bbed5213b2a065aafa89888e1
+size 32299
diff --git a/marked/Rel-18/22_series/22104/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/Rel-18/22_series/22104/34b047489058d6400b412cd0ae2334ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b4afe8095821c0899aee88f5c95ac8e3841d06c
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/34b047489058d6400b412cd0ae2334ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7fcdebaa2bb3d2adc6885c3bd77d7a95c6ea6d2ecdf60167f5345c73e6b0056
+size 56673
diff --git a/marked/Rel-18/22_series/22104/36ea45381c7b7fcbc99ce438860f8f37_img.jpg b/marked/Rel-18/22_series/22104/36ea45381c7b7fcbc99ce438860f8f37_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13456f02d289215f9536781dec56b81a77583a3e
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/36ea45381c7b7fcbc99ce438860f8f37_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:948093406a38871e04b687b84802aebeef980a28937d657f6b3c87f8cd9beeef
+size 23225
diff --git a/marked/Rel-18/22_series/22104/4224f170b677d60f6f86ce95d8dc725a_img.jpg b/marked/Rel-18/22_series/22104/4224f170b677d60f6f86ce95d8dc725a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ed045fa74948cb91b311ffde0e395511a82b20e
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/4224f170b677d60f6f86ce95d8dc725a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:178cdd2478ad1ad0f5e2d93111582647aa33581b74ccfa863915a4b9ffab3ea6
+size 110258
diff --git a/marked/Rel-18/22_series/22104/55736d2180d01f631782ce0784caafa3_img.jpg b/marked/Rel-18/22_series/22104/55736d2180d01f631782ce0784caafa3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3484e15f7b5344232cf6509f85d840fcbb52503
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/55736d2180d01f631782ce0784caafa3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b3b1b27b19b4ddcb3d084549bb801c7466be38a0d0177a0e0adf46ef05848de
+size 46445
diff --git a/marked/Rel-18/22_series/22104/5e17a7bb8192b905e70074ef897b7966_img.jpg b/marked/Rel-18/22_series/22104/5e17a7bb8192b905e70074ef897b7966_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..078f06ca80c8ae72cb11e284c9f77af90aa1180b
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/5e17a7bb8192b905e70074ef897b7966_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fb715d1cdfdaf95522cd31d14473b0c748ca760600e836ec07646881dd9437b
+size 6652
diff --git a/marked/Rel-18/22_series/22104/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22104/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..564a63f2ebf1e0d052441d58d7b498da96f601fe
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35c35f88447d99d29cae534f70cd3c3a30d767815ce0aadc35825f19a70c0323
+size 9880
diff --git a/marked/Rel-18/22_series/22104/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22104/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99da8ef07aca9ca4c0f6b77f40ea3624e59a196a
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3526699d19804ac52f8141d4176bb755befd48d10a29357c28096ecd486beef0
+size 5665
diff --git a/marked/Rel-18/22_series/22104/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/Rel-18/22_series/22104/742a5484e7dd016256ab99921bbd635d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b61c3ded5e264101a0c4d4a4e841304d3958af9d
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/742a5484e7dd016256ab99921bbd635d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59257b360ac98ae16b40006d34dee5863d748ceffa59d4c3b1039a87017ef704
+size 86692
diff --git a/marked/Rel-18/22_series/22104/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-18/22_series/22104/7ed5d5770331f31ade15439a21c31425_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36df95c67e0e0768d1a8caca46f07a4de182de0a
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/7ed5d5770331f31ade15439a21c31425_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2335df72e174059e53e849515962d6ef80a064505d9592b9c574a7695f72f7dd
+size 71098
diff --git a/marked/Rel-18/22_series/22104/95c11a9c59e4ad4af81a0e635ceafe45_img.jpg b/marked/Rel-18/22_series/22104/95c11a9c59e4ad4af81a0e635ceafe45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a401eafed05fb502bb858538033dd2dc7b2fa7b
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/95c11a9c59e4ad4af81a0e635ceafe45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:47af052761dde24d4f47ac5cd5eb508d1ed12af59222e5701f0489a8c7ae2ba9
+size 19870
diff --git a/marked/Rel-18/22_series/22104/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg b/marked/Rel-18/22_series/22104/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c6757ae302d203b6c4949de776173255d98fcaa
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:faa8adfdcfb474a41e4aafdfd746e72f774b693ff4d7f0a862a3dfef3fa8cc77
+size 52166
diff --git a/marked/Rel-18/22_series/22104/c0f6ba43542fddfee899e1af9cbd720d_img.jpg b/marked/Rel-18/22_series/22104/c0f6ba43542fddfee899e1af9cbd720d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a85f99a07c4eca0506555ad098068f95754b5df
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/c0f6ba43542fddfee899e1af9cbd720d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e35d499504aa8ba775e8e1ca0dcb4d3c79f0a975877c13664d04d0674dc977cd
+size 21782
diff --git a/marked/Rel-18/22_series/22104/cd1644aa63c56ebb82e7063295fc1cf7_img.jpg b/marked/Rel-18/22_series/22104/cd1644aa63c56ebb82e7063295fc1cf7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d39beb45712db5c89d7c77a6c6242d5bb6c7f915
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/cd1644aa63c56ebb82e7063295fc1cf7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d50f59606a8f6dc30ffce0655be20108310bd154fafb221589b0096a9029b4a2
+size 10730
diff --git a/marked/Rel-18/22_series/22104/e05434e963901d7e9c0bf5a6758200ed_img.jpg b/marked/Rel-18/22_series/22104/e05434e963901d7e9c0bf5a6758200ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33914f181876f90305de08ba1056bcd408dced32
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/e05434e963901d7e9c0bf5a6758200ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e0e1b0478b5e5e465a9fde238959f3b62d0c4fef62b499f958411c2dc6cb9f9
+size 54333
diff --git a/marked/Rel-18/22_series/22104/e38f0349f1b6094626cbfeab7105f029_img.jpg b/marked/Rel-18/22_series/22104/e38f0349f1b6094626cbfeab7105f029_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fed79fc0924bcd077c2c7fd60b5e44705e9115b6
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/e38f0349f1b6094626cbfeab7105f029_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abef531e4dccf5f8cb1fa578a904f8688190cd831ac54bdad656b54a17f154f9
+size 87795
diff --git a/marked/Rel-18/22_series/22104/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/marked/Rel-18/22_series/22104/e60c2d24a97a2855d98671d27ea43d0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f0005ede4cbcc68d262068aab009a1c7617abbf
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/e60c2d24a97a2855d98671d27ea43d0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a12f9522ce6235483bc8ce1fd00a14660d9c8d1fd4f6fc8c9aeaa6612de799e0
+size 38197
diff --git a/marked/Rel-18/22_series/22104/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg b/marked/Rel-18/22_series/22104/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec4ebd7f1eb546127eed68a7d8e150ddf9410d34
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72137f129cc569857d6fd484be18dbb97bde78de46c7902bd0c18774dad95b49
+size 54382
diff --git a/marked/Rel-18/22_series/22104/ebbf932a7c39555fbb003c4502fb90ed_img.jpg b/marked/Rel-18/22_series/22104/ebbf932a7c39555fbb003c4502fb90ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fdec90de7be8d069731e3c8be3131f3c086d1266
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/ebbf932a7c39555fbb003c4502fb90ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8637849a15f2cc2fbf93ce74745c116c8cbad6bb357279d23cafbd25041fa92d
+size 32168
diff --git a/marked/Rel-18/22_series/22104/eec47775133f5c3b02d42ab8f85599ce_img.jpg b/marked/Rel-18/22_series/22104/eec47775133f5c3b02d42ab8f85599ce_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a3b6e8035073b57c38b288d09fe0457f6ea808b
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/eec47775133f5c3b02d42ab8f85599ce_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99b3ad075fc3ecac1b39541d71fcf054bc33a1ce1426d4d5a5ec20681226cd7a
+size 7870
diff --git a/marked/Rel-18/22_series/22104/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/Rel-18/22_series/22104/efb282bed9f06eef1987a14fb27bc599_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19f85bcd9a76f37ac81d0d1e9d957c1c2274897f
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/efb282bed9f06eef1987a14fb27bc599_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df7c2cee7d1308a73d6404957235cad2654153d0b1411aff3971ecbf5b9ba2be
+size 83406
diff --git a/marked/Rel-18/22_series/22104/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg b/marked/Rel-18/22_series/22104/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..213dd55fbc122b1055e7b979c43d568e15af86a5
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05e8be442a03baa8ac146fe4b37370af963eaf48548f33e7f610200589d3bb19
+size 20525
diff --git a/marked/Rel-18/22_series/22104/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Rel-18/22_series/22104/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8e3ffd9e01fb86e5d9fc785cebdbc0199a14cd7
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4800bf07b75ac22e492ae4229f50af828139d428f6e322489c5912c1fd776767
+size 110555
diff --git a/marked/Rel-18/22_series/22104/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/22_series/22104/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac653695cb8fb2ee1f1ca1ff6ec7936c2a46f189
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddb7adef86fa54d9e518b1970dbed07072faced29dd4bf981896e120743cf762
+size 48457
diff --git a/marked/Rel-18/22_series/22104/raw.md b/marked/Rel-18/22_series/22104/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bf0e775df588039fdf46970ef22efc587805fba
--- /dev/null
+++ b/marked/Rel-18/22_series/22104/raw.md
@@ -0,0 +1,2646 @@
+
+
+# 3GPP TS 22.104 V18.3.0 (2021-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for cyber-physical control applications in vertical domains; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like signal icon above the 'G', and the word 'ADVANCED' in smaller capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+**Verticals**
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|----------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| Introduction ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions, symbols and abbreviations..... | 9 |
+| 3.1 Definitions..... | 9 |
+| 3.2 Symbols..... | 10 |
+| 3.3 Abbreviations ..... | 10 |
+| 4 Overview..... | 10 |
+| 4.1 Introduction ..... | 10 |
+| 4.2 Activity patterns in automation..... | 11 |
+| 4.3 Communication attributes ..... | 11 |
+| 4.4 Control systems and related communication patterns..... | 12 |
+| 4.5 Implications for 5G systems..... | 12 |
+| 5 Performance requirements ..... | 12 |
+| 5.1 Overview ..... | 12 |
+| 5.2 Periodic deterministic communication..... | 14 |
+| 5.3 Aperiodic deterministic communication..... | 21 |
+| 5.4 Non-deterministic communication..... | 23 |
+| 5.5 Mixed traffic..... | 24 |
+| 5.6 Clock synchronisation requirements ..... | 25 |
+| 5.6.0 Description ..... | 25 |
+| 5.6.1 Clock synchronisation service level requirements ..... | 25 |
+| 5.6.2 Clock synchronisation service performance requirements..... | 26 |
+| 5.6A Time-sensitive communication requirements ..... | 27 |
+| 5.6B 5G Timing Resiliency ..... | 27 |
+| 5.6C Support for infrastructure protection of electrical transmission..... | 27 |
+| 5.6C.1 Description ..... | 27 |
+| 5.6C.2 Requirements..... | 27 |
+| 5.7 Positioning performance requirements..... | 27 |
+| 5.7.1 General requirements..... | 27 |
+| 5.7.2 Energy efficiency requirements for high accuracy positioning ..... | 28 |
+| 5.8 Network operation requirements..... | 28 |
+| 6 Ethernet applications..... | 29 |
+| 6.1 Description ..... | 29 |
+| 6.2 Requirements..... | 29 |
+| 7 Direct device connection for cyber-physical control applications..... | 29 |
+| 7.1 Description ..... | 29 |
+| 7.2 Requirements..... | 29 |
+| 7.2.1 General ..... | 29 |
+| 7.2.2 Network performance ..... | 30 |
+| 7.2.3 Clock synchronization..... | 30 |
+| 7.2.3.1 Description..... | 30 |
+| 7.2.3.2 Clock synchronization requirements..... | 30 |
+| 7.2.4 Service Continuity ..... | 31 |
+| 7.2.5 Direct device connection via UE to UE relay..... | 31 |
+| 8 Indirect network connection for cyber-physical control applications..... | 31 |
+| 8.1 Description ..... | 31 |
+| 8.2 Requirements..... | 31 |
+| 8.2.1 General ..... | 31 |
+| 8.2.2 Communication via indirect network connection..... | 31 |
+
+| | | |
+|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------|
+| 8.2.3 | Clock synchronization ..... | 32 |
+| 8.2.3.1 | Description ..... | 32 |
+| 8.2.3.2 | Clock synchronization requirements ..... | 32 |
+| 8.2.4 | Service Continuity ..... | 32 |
+| 9 | Recovery of infrastructure for electrical distribution..... | 33 |
+| 9.1 | Description ..... | 33 |
+| 9.2 | Requirements..... | 33 |
+| Annex A (informative): Summary of service performance requirements ..... | | 34 |
+| A.1 | About the vertical domains addressed in this Annex..... | 34 |
+| A.2 | Factories of the Future ..... | 34 |
+| A.2.1 | Overview ..... | 34 |
+| A.2.2 | Factory automation..... | 35 |
+| A.2.2.1 | Motion control ..... | 35 |
+| A.2.2.2 | Control-to-control communication ..... | 37 |
+| A.2.2.3 | Mobile robots..... | 37 |
+| A.2.2.4 | Wired to wireless link replacement ..... | 41 |
+| A.2.2.5 | Cooperative carrying ..... | 42 |
+| A.2.3 | Process automation..... | 44 |
+| A.2.3.1 | Closed-loop control ..... | 44 |
+| A.2.3.2 | Process and asset monitoring..... | 44 |
+| A.2.3.3 | Plant asset management..... | 45 |
+| A.2.4 | Human machine interfaces ..... | 46 |
+| A.2.4.1 | Mobile control panels ..... | 46 |
+| A.2.4.1A | Mobile operation panels ..... | 48 |
+| A.2.4.2 | Augmented reality ..... | 50 |
+| A.2.5 | Monitoring and maintenance..... | 50 |
+| A.2.5.1 | Remote access and maintenance..... | 50 |
+| A.3 | (void)..... | 52 |
+| A.4 | Electric-power distribution and Smart Grid..... | 52 |
+| A.4.1 | Overview ..... | 52 |
+| A.4.2 | Primary frequency control..... | 52 |
+| A.4.3 | Distributed voltage control..... | 53 |
+| A.4.4 | Distributed energy automation..... | 53 |
+| A.4.4.1 | Distributed automated switching for isolation and service restoration ..... | 53 |
+| A.4.4.2 | Distributed automation without GOOSE..... | 55 |
+| A.4.4.3 | Intelligent distributed feeder automation..... | 56 |
+| A.4.4.4 | High-speed current differential protection ..... | 58 |
+| A.4.5 | Smart grid millisecond-level precise load control..... | 59 |
+| A.4.6 | Distributed energy storage ..... | 61 |
+| A.4.7 | Advanced metering ..... | 63 |
+| A.4.8 | Smart distribution transformer terminal ..... | 65 |
+| A.4.9 | Distributed energy resources and micro-grids ..... | 66 |
+| A.4.10 | Ensuring uninterrupted communication service availability during emergencies ..... | 68 |
+| A.5 | Central power generation ..... | 68 |
+| A.5.1 | Overview ..... | 68 |
+| A.5.2 | Wind power plant network..... | 68 |
+| A.6 | Connected hospitals or medical facilities..... | 69 |
+| A.6.1 | Overview ..... | 69 |
+| A.6.2 | Robotic Aided Surgery ..... | 69 |
+| A.6.3 | Robotic Aided Diagnosis ..... | 72 |
+| A.7 | Positioning ..... | 73 |
+| A.7.1 | Overview of positioning in industrial use cases..... | 73 |
+| A.7.2 | Low Power High Accuracy Positioning..... | 74 |
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------|------------|
+| Annex B (informative): Communication service errors ..... | 77 |
+| B.1 Introduction..... | 77 |
+| B.2 Corruption ..... | 77 |
+| B.3 Unintended repetition..... | 77 |
+| B.4 Incorrect sequence..... | 77 |
+| B.5 Loss ..... | 78 |
+| B.6 Unacceptable deviation from target end-to-end latency ..... | 78 |
+| B.7 Masquerade ..... | 78 |
+| B.8 Insertion ..... | 78 |
+| B.9 Addressing ..... | 78 |
+| Annex C (informative): Characterising communication services..... | 79 |
+| C.1 Modelling of communication in automation..... | 79 |
+| C.1.1 Area of consideration ..... | 79 |
+| C.1.2 Logical link ..... | 80 |
+| C.1.2.1 Nature and function ..... | 80 |
+| C.1.2.2 Message transformation..... | 81 |
+| C.1.2.3 Communication device..... | 81 |
+| C.1.2.4 Communication system ..... | 81 |
+| C.2 Communication service description..... | 82 |
+| C.2.1 Overview ..... | 82 |
+| C.2.2 Characteristic parameters ..... | 82 |
+| C.2.3 Influence quantities ..... | 84 |
+| C.3 Up time and up state vs. down state and down time ..... | 85 |
+| C.4 Timeliness as an attribute for timing accuracy ..... | 86 |
+| C.4.1 Overview ..... | 86 |
+| C.4.2 Network latency requirement formulated by use of timeliness..... | 87 |
+| C.4.3 Timeliness ..... | 87 |
+| C.4.4 Deviation ..... | 87 |
+| C.4.5 Earliness ..... | 88 |
+| C.4.6 Lateness..... | 89 |
+| C.4.7 Conclusion..... | 89 |
+| C.5 Communication service terminology w.r.t. 5G network and vertical applications..... | 89 |
+| Annex D (informative): 5G in industrial automation: different and multiple time domains for synchronization..... | 92 |
+| D.1 Description..... | 92 |
+| D.2 Merging of working clock domains..... | 93 |
+| D.3 Time synchronization with 5G networks ..... | 94 |
+| Annex E (informative): Audio and Video Production ..... | 95 |
+| E.1 Description ..... | 95 |
+| E.2 Multiple source wireless studio..... | 95 |
+| E.3 Timing use in AV production applications ..... | 96 |
+| Annex F (informative): Relation of reliability and communication service availability ..... | 98 |
+| Annex G (informative): Change history..... | 100 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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.
+
+The present document implements Option 2 for decimal and thousands separator characters: "The decimal sign shall be a full-stop (period). The thousands separator shall be a comma." (TR 21.801 v16.2.0 Clause 6.6.7).
+
+# --- Introduction
+
+The present document addresses a challenging class of vertical applications, namely cyber-physical control applications, which require very high levels of communication service availability, and some of them also require very low end-to-end latencies.
+
+Real-time Ethernet is one of the established wireline communication technologies for cyber-physical control applications, and this specification identifies requirements that 5G systems must meet to support real-time Ethernet.
+
+The present document provides new Stage 1 requirements based on the input from relevant stakeholders of the respective vertical domains.
+
+# --- 1 Scope
+
+The present document provides Stage 1 normative service requirements for 5G systems, in particular service requirements for cyber-physical control applications in vertical domains and requirements for auxiliary applications. In the context of the present document, cyber-physical systems are to be understood as systems that include engineered, interacting networks of physical and computational components; control applications are to be understood as applications that control physical processes. Examples for auxiliary applications are distributed sensing and asset monitoring.
+
+Communication services supporting cyber-physical control applications need to be ultra-reliable and, in some cases, the end-to-end latency must be very low. Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation, Smart Grid .
+
+The aspects addressed in the present document include:
+
+- end-to-end service performance requirements and network performance requirements related to these end-to-end service performance requirements;
+- support for Ethernet services specific to industrial/high performance use cases. Related Ethernet functionalities include, for example, those in IEEE 802.1Qbv;
+- direct device connection and indirect network connection for cyber-physical applications.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.261: "Service requirements for the 5G system".
+- [3] IEC 61784-3: "Industrial communication networks – profiles – part 3: functional fieldbuses – general rules and profile definitions".
+- [4] BZKI, "Aspects of dependability assessment in ZDKI", June 2017.
+- [5] BZKI, "Requirement Profiles in ZDKI", 2017.
+- [6] IEC 61158: "Industrial communication networks – fieldbus specification", 2014.
+- [7] IEC 61907, "Communication network dependability engineering".
+- [8] Richard C. Dorf and Robert H. Bishop, "Modern Control Systems", Pearson, Harlow, 13th Edition, 2017.
+- [9] Ernie Hayden, Michael Assante, and Tim Conway, "An Abbreviated History of Automation & Industrial Controls Systems and Cybersecurity", SANS Institute, {accessed: 2017-05-23}, 2014.
+- [10] IEC 61512 "Batch control - Part 1: Models and terminology".
+
+- [11] RESERVE project, Deliverable D1.3, ICT Requirements, , September 2017.
+- [12] RESERVE project, Deliverable D1.2, Energy System Requirements , September 2017.
+- [13] G. Garner, "Designing Last Mile Communications Infrastructures for Intelligent Utility Networks (Smart Grids)", IBM Australia Limited, 2010.
+- [14] B. Al-Omar, B., A. R. Al-Ali, R. Ahmed, and T. Landolsi, "Role of Information and Communication Technologies in the Smart Grid", Journal of Emerging Trends in Computing and Information Sciences, Vol. 3, pp. 707-716, 2015.
+- [15] H. Kagermann, W. Wahlster, and J. Helbig, "Recommendations for implementing the strategic initiative INDUSTRIE 4.0", Final report of the Industrie 4.0 working group, acatech – National Academy of Science and Engineering, Munich, April 2013.
+- [16] IEC 62443-3-2: "Security for industrial automation and control systems - Part 3-2: Security risk assessment and system design", in progress.
+- [17] IEC 62657-2: "Industrial communication networks - Wireless communication networks - Part 2: Coexistence management", 2017.
+- [18] IEC 62657-1: "Industrial communication networks – Wireless communication networks – Part 1: Wireless communication requirements and spectrum considerations".
+- [19] IEEE Std 802.1Q: "IEEE Standard for Local and Metropolitan Area Networks---Bridges and Bridged Networks".
+
+NOTE: IEEE Std 802.1Qbv-2015 "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridges Networks - Amendment 25: Enhancements for Scheduled Traffic" has been included into IEEE Std 802.1Q-2018.
+- [20] IEEE, Use Cases IEC/IEEE 60802, 2018.
+- [21] (void)
+- [22] IEEE Std 802.1AS: "IEEE Standard for Local and Metropolitan Area Networks--Timing and Synchronization for Time-Sensitive Applications".
+- [23] 3GPP TS 22.289: "Mobile Communication System for Railways".
+- [24] IEEE P802.1CS: "IEEE Standard for Local and Metropolitan Area Networks--Link-local Registration Protocol".
+- [25] IEEE P802.1Qdd: "IEEE Draft Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks -- Amendment: Resource Allocation Protocol (RAP) ".
+- [26] IEC/IEEE 60802: "Time-Sensitive Networking Profile for Industrial Automation".
+- [27] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)".
+- [28] IEC TR 61850-90-1:2010, Communication Networks and Systems for Power Utility automation – Part 90-1: Use of IEC61850 for the communication between substations.
+- [29] 5G DNA White Paper: "5GDN@Smart Grid White Paper: Requirements, Technologies, and Practices"
+- [30] IEC 61850-9-3-2016 – IEC/IEEE International Standard - Communication Networks and Systems for Power Utility automation – Part 9-3: Precision time protocol profile for power utility automation.
+- [31] IEEE Std C37.238-2017 , IEEE Standard Profile for Use of IEEE Std 1588™ Precision Time Protocol in Power System Applications.
+
+- [32] IEC 61850-90-5:2012, Use of IEC 61850 to transmit Synchrophasors information according to IEEE C37.118.
+- [33] IEEE Std C37.118.2-2011, IEEE Standard for Synchrophasor Data Transfer for Power Systems.
+- [34] IEEE Std 1588-2019: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**characteristic parameter:** numerical value that can be used for characterising the dynamic behaviour of communication functionality from an application point of view.
+
+**clock synchronicity:** the maximum allowed time offset within a synchronisation domain between the sync master and any sync device.
+
+NOTE 1: Clock synchronicity (or synchronicity) is used as KPI of clock synchronisation services.
+
+NOTE 2: Clock synchronicity is also referred to as clock (or time) synchronization precision.
+
+**clock synchronisation service:** the service to align otherwise independent user-specific UE clocks.
+
+**communication service availability:** as defined in TS 22.261 [2].
+
+**communication service reliability:** ability of the communication service to perform as required for a given time interval, under given conditions.
+
+NOTE 3: Given conditions would include aspects that affect reliability, such as: mode of operation, stress levels, and environmental conditions.
+
+NOTE 4: Reliability may be quantified using appropriate measures such as mean time between failures, or the probability of no failure within a specified period of time.
+
+NOTE 5: This definition is based on IEC 61907 [7].
+
+**direct device connection:** as defined in TS 22.261 [2].
+
+**end-to-end latency:** as defined in TS 22.261 [2].
+
+**error:** discrepancy between a computed, observed or measured value or condition and the true, specified or theoretically correct value or condition.
+
+NOTE 6: This definition was taken from IEC 61784-3 [3].
+
+**factory automation:** automation application in industrial automation branches typically with discrete characteristics of the application to be automated with specific requirements for determinism, low latency, reliability, redundancy, cyber security, and functional safety.
+
+NOTE 7: Low latency typically means below 10 ms delivery time.
+
+NOTE 8: This definition is taken from IEC 62657-1 [18].
+
+**global clock:** a user-specific synchronization clock set to a reference timescale such as the International Atomic Time.
+
+**indirect network connection:** as defined in TS 22.261 [2].
+
+**influence quantity:** quantity not essential for the performance of an item but affecting its performance.
+
+**process automation:** automation application in industrial automation branches typically with continuous characteristics of the application to be automated with specific requirements for determinism, reliability, redundancy, cyber security, and functional safety.
+
+NOTE 9: This definition is taken from IEC 62657-1 [18].
+
+**service area:** as defined in TS 22.261 [2].
+
+**survival time:** as defined in TS 22.261 [2].
+
+**sync device:** device that synchronizes itself to the master clock of the synchronization domain.
+
+**sync master:** device serving as the master clock of the synchronization domain.
+
+**transfer interval:** time difference between two consecutive transfers of application data from an application via the service interface to 3GPP system.
+
+NOTE 10: This definition is based on subclause 3.1.85 in IEC 62657-2 [17].
+
+**user experienced data rate:** as defined in TS 22.261 [2].
+
+**vertical domain:** an industry or group of enterprises in which similar products or services are developed, produced, and provided.
+
+**working clock:** a user-specific synchronization clock for a localized set of UEs collaborating on a specific task or work function.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| | |
+|----------|---------------|
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|--------|------------------------------------------|
+| AV | Audio-Visual |
+| AVPROD | AV Production |
+| CSIF | Communication Service Interface |
+| EPON | Ethernet Passive Optical Network |
+| FIFO | First In, First Out |
+| GOOSE | Generic Object-Oriented Substation Event |
+| HCL | Higher Communication Layer |
+| HMI | Human Machine Interface |
+| IMU | Inertial Measurement Unit |
+| LCL | Lower Communication Layer |
+| PMU | Phasor Measurement Unit |
+
+# 4 Overview
+
+## 4.1 Introduction
+
+For the purpose of this document, a vertical domain is a particular industry or group of enterprises in which similar products or services are developed, produced, and provided. Automation refers to the control of processes, devices, or systems in vertical domains by automatic means. The main control functions of automated control systems include taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators.
+
+In the context of this document, cyber-physical systems are referred to as systems that include engineered, interacting networks of physical and computational components. Cyber-physical control applications are to be understood as applications that control physical processes. Cyber-physical control applications in automation follow certain activity patterns, which are open-loop control, closed-loop control, sequence control, and batch control (see Clause 4.2).
+
+Communication services supporting cyber-physical control applications need to be ultra-reliable, dependable with a high communication service availability, and often require low or (in some cases) very low end-to-end latency.
+
+Communication in automation in vertical domains follows certain communication patterns. The most well-known is periodic deterministic communication, others are aperiodic deterministic communication and non-deterministic communication (see Clause 4.3).
+
+Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation and energy automation. This document addresses service requirements for cyber-physical control applications and supporting communication services from the vertical domains of factories of the future (smart manufacturing), electric power distribution, and central power generation. Service requirements for cyber-physical control applications and supporting communication services for rail-bound mass transit are addressed in TS 22.289 [23].
+
+## 4.2 Activity patterns in automation
+
+**Open-loop control:** The salient aspect of open-loop control is the lack of feedback from the output to the control; when providing commands to an actuator, it is assumed that the output of the influenced process is predetermined and within an acceptable range. This kind of control loop works if the influences of the environment on process and actuator are negligible. Also, this kind of control is applied in case unwanted output can be tolerated [8].
+
+**Closed-loop control:** Closed-loop control enables the manipulation of processes even if the environment influences the process or the performance of the actuator changes over time. This type of control is realised by sensing the process output and by feeding these measurements back into a controller [8].
+
+**Sequence control:** Sequence control may either step through a fixed sequence or employ logic that performs different actions based on various system states and system input [8]. Sequence control can be seen as an extension of both open-loop and closed-loop control, but instead of achieving only one output instance, an entire sequence of output instances can be produced [9].
+
+**Batch control:** Batch processes lead to the production of finite quantities of material (batches) by subjecting input materials to a defined order of processing actions by use of one or more pieces of equipment [10].
+
+## 4.3 Communication attributes
+
+Communication in automation can be characterised by two main attributes: periodicity and determinism.
+
+Periodicity means that a transmission interval is repeated. For example, a transmission occurs every 15 ms. Reasons for a periodical transmission can be the periodic update of a position or the repeated monitoring of a characteristic parameter. Most periodic intervals in communication for automation are rather short. The transmission is started once and continuous unless a stop command is provided.
+
+An aperiodic transmission is, for example, a transmission which is triggered instantaneously by an event, i.e., events are the trigger of the transmission. Events are defined by the control system or by the user. Example events are:
+
+- Process events: events that come from the process when thresholds are exceeded or fallen below, e.g., temperature, pressure, level, etc.
+- Diagnostic events: events that indicate malfunctions of an automation device or module, e.g., power supply defective; short circuit; too high temperature; etc.
+- Maintenance events: events based on information that indicates necessary maintenance work to prevent the failure of an automation device.
+
+Most events, and especially alarms, are confirmed. In this context, alarms are messages that inform a controller or operator that an event has occurred, e.g., an equipment malfunction, process deviation, or other abnormal condition requiring a response. The receipt of the alarm is acknowledged usually within a short time period by the application that
+
+received the alarm. If no acknowledgment is received from the target application after a preset time, the so-called monitoring time, the alarm is sent again after a preset time or some failure response action is started.
+
+Determinism refers to whether the delay between transmission of a message and receipt of the message at the destination address is stable (within bounds). Usually, communication is called deterministic if it is bounded by a given threshold for the latency/transmission time. In case of a periodic transmission, the variation of the interval is bounded.
+
+## 4.4 Control systems and related communication patterns
+
+There are preferences in the mapping between the type of control and the communication pattern. Open-loop control is characterised by one or many messages sent to an actuator. These can be sent in a periodic or an aperiodic pattern. However, the communication means used need to be deterministic since typically an activity response from the receiver and/or the receiving application is expected.
+
+Closed-loop control produces both periodic and aperiodic communication patterns. Closed-loop control is often used for the control of continuous processes with tight time-control limits, e.g., the control of a printing press. In this case, one typically relies on periodic communication patterns. Note that in both the aperiodic and periodic case, the communication needs to be deterministic.
+
+Logging of device states, measurements, etc. for maintenance purposes and such typically entails aperiodic communication patterns. In case the transmitted logging information can be time-stamped by the respective function, determinism is often not mandatory.
+
+In practice, vertical communication networks serve a large number of applications exhibiting a wide range of communication requirements. In order to facilitate efficient modelling of the communication network during engineering and for reducing the complexity of network optimisation, traffic classes or communication patterns have been identified [6]. There are three typical traffic classes or communication patterns in industrial environments [6], i.e.,
+
+- deterministic periodic communication: periodic communication with stringent requirements on timeliness of the transmission.
+- deterministic aperiodic communication: communication without a preset sending time. Typical activity patterns for which this kind of communication is suitable are event-driven actions.
+- non-deterministic communication: subsumes all other types of traffic, including periodic non-real time and aperiodic non-real time traffic. Periodicity is irrelevant in case the communication is not time-critical.
+
+Some communication services exhibit traffic patterns that cannot be assigned to one of the above communication patterns exclusively (mixed traffic).
+
+## 4.5 Implications for 5G systems
+
+In order to be suitable for automation in vertical domains, 5G systems need to be dependable and flexible to meet specific KPIs to serve specific applications and use cases. They need to come with the system properties of reliability, availability, maintainability, safety, and integrity. What particular requirements each property needs to meet depends on the particularities of the domain and the use case. Annex F discusses the difference between reliability and communication service availability. The requirements in this document provide various sets of performance criteria that need to be met to satisfactorily support different use cases of cyber-physical control applications used by various vertical markets.
+
+# --- 5 Performance requirements
+
+## 5.1 Overview
+
+There are two fundamental perspectives concerning dependable communication in 5G systems: the end-to-end perspective of the communication services and the network perspective (see Figure 5.1-1).
+
+
+
+The diagram shows two 'distributed automation application' boxes at the top, each containing a 'CSIF' (Communication Service Interface) block. These boxes are connected to a central '5G System' cloud. The '5G System' cloud is connected to a 'Communication Service' block at the bottom. The entire diagram is titled '5G Service Performance Requirements'.
+
+Diagram illustrating the network perspective of a 5G system. Two 'distributed automation application' boxes, each containing a 'CSIF' (Communication Service Interface) block, are connected to a central '5G System' cloud. The '5G System' cloud is connected to a 'Communication Service' block at the bottom. The entire diagram is titled '5G Service Performance Requirements'.
+
+CSIF – Communication Service Interface between distributed automation application/function and 5G system
+
+**Figure 5.1-1: Network perspective of 5G system**
+
+The Communication Service in Figure 5.1-1 may be implemented as a logical communication link between a UE on one side and a network server on the other side, or between a UE on one side and a UE on the other side.
+
+In some cases, a local approach (e.g. network edge) is preferred for the communication service on the network side in order to reduce the latency, to increase communication service availability, or to keep sensitive data in a non-public network on the factory site.
+
+The tables in Clauses 5.2 through 5.5 below provide sets of requirements where periodicity and determinism are critical to meeting cyber-physical control application needs in various vertical scenarios. While many use cases have similar KPI values, the important distinction is that in order to meet the needs of different verticals and different uses, the 5G system will need to be sufficiently flexible to allow deployment configurations that can meet the different sets of KPIs specific to each use.
+
+Communication service availability is considered an important service performance requirement for cyber-physical applications, especially for applications with deterministic traffic. The communication service availability depends on the latency and reliability (in the context of network layer packet transmissions, as defined in TS 22.261 [2]) of the logical communication link, as well as the survival time of the cyber-physical application (see Annex C.3 for further details on these relations).
+
+The communication service reliability requirements also depend on the operation characteristics of the corresponding cyber-physical applications. Typically, the communication services critical for the automation application also come with stringent communication service reliability requirements. Note that the communication service reliability requirement has no direct relationship with the communication service availability requirement.
+
+The "# of UEs" in the tables in clauses 5.2 to 5.5 is intended to give an indication of the UE density that would need to be served within a given service area.
+
+Clock synchronisation is needed in many "vertical" use cases. The requirements and tables in Clause 5.6 provide specific criteria for managing time sensitive communications in an industrial environment.
+
+High accuracy positioning is becoming essential for Factories of the Future. The reason for this is that tracking of mobile devices as well as mobile assets is becoming increasingly important in improving processes and increasing flexibility in industrial environments, Clause 5.7 provides positioning requirements for horizontal and vertical accuracy, availability, heading, latency and UE speed in an industrial use case scenario.
+
+An example of the relationship between reliability (in the context of network layer packet transmissions, as defined in TS 22.261 [2]), survival time and communication service availability of a logical communication link is illustrated in the following Table 5.1-1. This is done for a special case where packet errors are uncorrelated, which in many cases is an unrealistic assumption.
+
+**Table 5.1-1: Example of relationship between reliability (as defined in TS 22.261) and communication service availability when the survival time is equal to the transfer interval.**
+
+| Communication service availability | Reliability
( as defined in TS 22.261)
$1 - p$ |
+|------------------------------------|------------------------------------------------------|
+| 99.999 9 % | 99.9 % |
+| 99.999 999 % | 99.99 % |
+| 99.999 999 99 % | 99.999 % |
+| 99.999 999 999 9 % | 99.999 9 % |
+| 99.999 999 999 999 % | 99.999 99 % |
+
+## 5.2 Periodic deterministic communication
+
+Periodic deterministic communication is periodic with stringent requirements on timeliness and availability of the communication service. A transmission occurs every transfer interval. A description of periodic deterministic communication can be found in Clauses 4.3 and 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.2-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.2-1 can be found in Annex C.
+
+The 5G system shall be able to provide periodic deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.2-1.
+
+Process and asset monitoring using industrial wireless sensors is a special case of periodic deterministic communication with more relaxed requirements on timeliness and availability. These use cases put a slightly different set of requirements on the 5G system due to the specific constraints of industrial wireless sensors. These requirements for individual logical communication links are listed in Table 5.2-2 and additional information on the underlying use cases can be found in Annex A.
+
+Smart-Grid use case information can be found in Annex A.
+
+Table 5.2-1: Periodic deterministic communication service performance requirements
+
+| Characteristic parameter | | | | Influence quantity | | | | | | |
+|-----------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------|--------------------------------|----------------------------------------------|--------------------------|----------------------------|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------|
+| Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (note 2) (note 12a) | Service bit rate: user experienced data rate (note 12a) | Message size [byte] (note 12a) | Transfer interval: target value (note 12a) | Survival time (note 12a) | UE speed (note 13) | # of UEs | Service area (note 3) | Remarks |
+| 99.999 % to 99.999 99 % | ~ 10 years | < transfer interval value | – | 50 | 500 µs | 500 µs | ≤ 75 km/h | ≤ 20 | 50 m x 10 m x 10 m | Motion control (A.2.2.1) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < transfer interval value | – | 40 | 1 ms | 1 ms | ≤ 75 km/h | ≤ 50 | 50 m x 10 m x 10 m | Motion control (A.2.2.1) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < transfer interval value | – | 20 | 2 ms | 2 ms | ≤ 75 km/h | ≤ 100 | 50 m x 10 m x 10 m | Motion control (A.2.2.1) |
+| 99.999 9 % | – | < 5 ms | 1 kbit/s (steady state)
1.5 Mbit/s (fault case) | < 1,500 | < 60 s (steady state)
≥ 1 ms (fault case) | transfer interval | stationary | 20 | 30 km x 20 km | Electrical Distribution – Distributed automated switching for isolation and service restoration (A.4.4); (note 5) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < transfer interval value | | 1 k | ≤ 10 ms | 10 ms | - | 5 to 10 | 100 m x 30 m x 10 m | Control-to-control in motion control (A.2.2.2); (note 9) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < transfer interval value (note 5) | 50 Mbit/s | | ≤ 1 ms | 3 x transfer interval | stationary | 2 to 5 | 100 m x 30 m x 10 m | Wired-2-wireless 100 Mbit/s link replacement (A.2.2.4) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < transfer interval value (note 5) | 250 Mbit/s | | ≤ 1 ms | 3 x transfer interval | stationary | 2 to 5 | 100 m x 30 m x 10 m | Wired-2-wireless 1 Gbit/s link replacement (A.2.2.4) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < transfer interval value | | 1 k | ≤ 50 ms | 50 ms | - | 5 to 10 | 1,000 m x 30 m x 10 m | Control-to-control in motion control (A.2.2.2); (note 9) |
+| > 99.999 9 % | ~ 10 years | < transfer interval value | – | 40 to 250 | 1 ms to 50 ms (note 6) (note 7) | transfer interval value | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 | Mobile robots (A.2.2.3) |
+| 99.999 9 % to 99.999 999 % | ~ 1 month | < transfer interval value | – | 40 to 250 | 4 ms to 8 ms (note 7) | transfer interval value | < 8 km/h (linear movement) | TBD | 50 m x 10 m x 4 m | Mobile control panels – remote control of e.g. assembly robots, milling machines (A.2.4.1); (note 9) |
+
+| Characteristic parameter | | | | Influence quantity | | | | | | |
+|-----------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------|--------------------------------|--------------------------------------------|--------------------------|-----------------------------|--------------------|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
+| Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (note 2) (note 12a) | Service bit rate: user experienced data rate (note 12a) | Message size [byte] (note 12a) | Transfer interval: target value (note 12a) | Survival time (note 12a) | UE speed (note 13) | # of UEs | Service area (note 3) | Remarks |
+| 99.999 999 % | 1 day | < 8 ms (note 14) | 250 kbit/s | 40 to 250 | 8 ms | 16 ms | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m | Mobile Operation Panel: Emergency stop (connectivity availability) (A.2.4.1A) |
+| 99.999 99 % | 1 day | < 10 ms (note 14) | < 1 Mbit/s | < 1024 | 10 ms | ~10 ms | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m | Mobile Operation Panel: Safety data stream (A.2.4.1A) |
+| 99.999 999 % | 1 day | 10 ms to 100 ms (note 14) | 10 kbit/s | 10 to 100 | 10 ms to 100 ms | transfer interval | stationary | 2 or more | 100 m 2 to 2,000 m 2 | Mobile Operation Panel: Control to visualization (A.2.4.1A) |
+| 99.999 999 % | 1 day | < 1 ms (note 14) | 12 Mbit/s to 16 Mbit/s | 10 to 100 | 1 ms | ~ 1 ms | stationary | 2 or more | 100 m 2 | Mobile Operation Panel: Motion control (A.2.4.1A) |
+| 99.999 999 % | 1 day | < 2 ms (note 14) | 16 kbit/s (UL)
2 Mbit/s (DL) | 50 | 2 ms | ~ 2 ms | stationary | 2 or more | 100 m 2 | Mobile Operation Panel: Haptic feedback data stream (A.2.4.1A) |
+| 99.999 9 % to 99.999 999 % | ~ 1 year | < transfer interval | – | 40 to 250 | < 12 ms (note 7) | 12 ms | < 8 km/h (linear movement) | TBD | typically 40 m x 60 m; maximum 200 m x 300 m | Mobile control panels - remote control of e.g. mobile cranes, mobile pumps, fixed portal cranes (A.2.4.1); (note 9) |
+| 99.999 9 % to 99.999 999 % | ≥ 1 year | < transfer interval value | – | 20 | ≥ 10 ms (note 8) | 0 | typically stationary | typically 10 to 20 | typically ≤ 100 m x 100 m x 50 m | Process automation – closed loop control (A.2.3.1) |
+| 99.999 % | TBD | ~ 50 ms | – | ~ 100 | ~ 50 ms | TBD | stationary | ≤ 100,000 | several km 2 up to 100,000 km 2 | Primary frequency control (A.4.2); (note 9) |
+| 99.999 % | TBD | ~ 100 ms | – | ~ 100 | ~ 200 ms | TBD | stationary | ≤ 100,000 | several km 2 up to 100,000 km 2 | Distributed Voltage Control (A.4.3) (note 9) |
+
+| Characteristic parameter | | | | Influence quantity | | | | | | |
+|-----------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------|------------------------------------------|--------------------------------------------|--------------------------------------------------------|-----------------------------|-----------------------------|--------------------------------------------------|-----------------------------------------------------------------------------|
+| Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (note 2) (note 12a) | Service bit rate: user experienced data rate (note 12a) | Message size [byte] (note 12a) | Transfer interval: target value (note 12a) | Survival time (note 12a) | UE speed (note 13) | # of UEs | Service area (note 3) | Remarks |
+| > 99.999 9 % | ~ 1 year | < transfer interval value | – | 15 k to 250 k | 10 ms to 100 ms (note 7) | transfer interval value | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 | Mobile robots – video-operated remote control (A.2.2.3) |
+| > 99.999 9 % | ~ 1 year | < transfer interval value | – | 40 to 250 | 40 ms to 500 ms (note 7) | transfer interval value | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 | Mobile robots (A.2.2.3) |
+| 99.99 % | ≥ 1 week | < transfer interval value | – | 20 to 255 | 100 ms to 60 s (note 7) | ≥ 3 x transfer interval value | typically stationary | ≤ 10,000 to 100,000 | ≤ 10 km x 10 km x 50 m | Plant asset management (A.2.3.3) |
+| >99.999 999 % | > 10 years | < 2 ms | 2 Mbit/s to 16 Mbit/s | 250 to 2,000 | 1 ms | transfer interval value | stationary | 1 | < 100 m 2 | Robotic Aided Surgery (A.6.2) |
+| >99.999 9 % | > 1 year | < 20 ms | 2 Mbit/s to 16 Mbit/s | 250 to 2,000 | 1 ms | transfer interval value | stationary | 2 per 1,000 km 2 | < 400 km (note 12) | Robotic Aided Surgery (A.6.2) |
+| >99.999 % | >> 1 month (< 1 year) | < 20 ms | 2 Mbit/s to 16 Mbit/s | 80 | 1 ms | transfer interval value | stationary | 20 per 100 km 2 | < 50 km (note 12) | Robotic Aided Diagnosis (A.6.3) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < 0.5 x transfer interval | 2.5 Mbit/s | 250 to 500 with localisation information | > 5 ms
> 2.5 ms
> 1.7 ms (note 10) | 0 transfer interval
2 x transfer interval (note 10) | ≤ 6 km/h (linear movement) | 2 to 8 | 10 m x 10 m x 5 m;
50 m x 5 m x 5 m (note 11) | Cooperative carrying – fragile work pieces; (ProSe communication) (A.2.2.5) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < 0.5 x transfer interval | 2.5 Mbit/s | 250 to 500 with localisation information | > 5 ms
> 2.5 ms
> 1.7 ms (note 10) | 0 transfer interval
2 x transfer interval (note 10) | ≤ 12 km/h (linear movement) | 2 to 8 | 10 m x 10 m x 5 m;
50 m x 5 m x 5 m (note 11) | Cooperative carrying – elastic work pieces; (ProSe communication) (A.2.2.5) |
+
+| Characteristic parameter | | | | Influence quantity | | | | | | |
+|-----------------------------------------------------------|---------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------|--------------------------------------------|--------------------------|--------------------|-----------------------------------------------------------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------|
+| Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (note 2) (note 12a) | Service bit rate: user experienced data rate (note 12a) | Message size [byte] (note 12a) | Transfer interval: target value (note 12a) | Survival time (note 12a) | UE speed (note 13) | # of UEs | Service area (note 3) | Remarks |
+| > 99.9 % | | DL: < 10 ms
UL: < 10 ms | UL: > 16 Mbit/s (urban),
640 Mbit/s (rural)
DL: > 100 kbit/s
(note 15) | UL: 800 kbyte | UL: 10 ms | | | > 10/km 2 (urban),
> 100/km 2 (rural)
(note 16) | | Distributed energy storage – monitoring (A.4.6) |
+| > 99.9 % | | DL: < 10 ms
UL: < 1 s | UL: > 128 kbit/s (urban),
10.4 Mbit/s (rural);
DL: > 100 kbit/s
(note 15) | UL: 1.3 Mbyte
DL: > 100 kbyte | UL: 1000 ms | | | > 10/km 2 (urban),
> 100/km 2 (rural)
(note 16) | | Distributed energy storage – data collection (A.4.6) |
+| > 99.99 % | | General information data collection:
< 3 s
(note 17) | UL: < 2 Mbit/s
DL: < 1 Mbit/s | | | | | < 10,000/km 2
(note 18) | | Advanced metering (A.4.7) |
+| 99.999 % | | < 10 ms | 2 Mbit/s to 10 Mbit/s | | normal: 1 s;
fault: 2 ms
(note 24) | | | 54/km 2 (note 19),
78/km 2 (note 20) | | Intelligent distributed feeder automation (A.4.4.3) |
+| > 99.99 % | | 10 ms,
100 ms, 3 s
(note 22) | > 2 Mbit/s (note 21) | | | | | 500 in the service area
(note 23) | Communication distance is from 100 m to 500 m, outdoor, indoor / deep indoor | Smart distribution –transformer terminal (A.4.8) |
+| 99.999 % | | 5 ms, 10 ms,
15 ms (note 25) | 1.2 Mbit/s to 2.5 Mbit/s | < 245 byte | ≤ 1 ms
≤ 2 ms
(note 26) | | | ≤ 100/km 2 | several km 2 | High speed current differential protection (note 12a) (A.4.4.4) |
+| 99.999 9 % | | 3 ms | 5.4 Mbit/s | 140 byte | ≤ 1 ms | | stationary | | | Distributed Energy Resources (DER) and microgrids (A.4.9) |
+
+| Characteristic parameter | | | | Influence quantity | | | | | | |
+|-----------------------------------------------------------|---------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------|--------------------------------|--------------------------------------------|--------------------------|--------------------|----------|-----------------------|---------------------------------------------------------------------------------------|
+| Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (note 2) (note 12a) | Service bit rate: user experienced data rate (note 12a) | Message size [byte] (note 12a) | Transfer interval: target value (note 12a) | Survival time (note 12a) | UE speed (note 13) | # of UEs | Service area (note 3) | Remarks |
+| 99.999 9 % | | 100 ms (note 12a and note 5) | < 1 kbit/s per DER | | | | stationary | | | Ensuring uninterrupted communication service availability during emergencies (A.4.10) |
+
+- NOTE 1: One or more retransmissions of network layer packets may take place in order to satisfy the communication service availability requirement.
+- NOTE 2: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+- NOTE 3: Length x width (x height).
+- NOTE 4: (void)
+- NOTE 5: Communication includes two wireless links (UE to UE).
+- NOTE 6: This covers different transfer intervals for different similar use cases with target values of 1 ms, 1 ms to 10 ms, and 10 ms to 50 ms.
+- NOTE 7: The transfer interval deviates around its target value by $< \pm 25\%$ .
+- NOTE 8: The transfer interval deviates around its target value by $< \pm 5\%$ .
+- NOTE 9: Communication may include two wireless links (UE to UE).
+- NOTE 10: The first value is the application requirement, the other values are the requirement with multiple transmission of the same information (two or three times, respectively).
+- NOTE 11: Service Area for direct communication between UEs. The group of UEs with direct communication might move throughout the whole factory site (up to several km2).
+- NOTE 12: Maximum straight-line distance between UEs.
+- NOTE 12a: It applies to both UL and DL unless stated otherwise.
+- NOTE 13: It applies to both linear movement and rotation unless stated otherwise.
+- NOTE 14: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
+- NOTE 15: Service bit rate for one energy storage station.
+- NOTE 16: Activity storage nodes/km2. This value is used for deducing the data volume in an area that features multiple energy storage stations. The data volume can be calculated with the following formula $(\text{current service bit rate per storage station}) \times (\text{activity storage nodes/km}^2) + (\text{video service bit rate per storage station}) \times (\text{activity storage nodes/km}^2)$ .
+- NOTE 17: One-way delay from 5G IoT device to backend system. The distance between the two is below 40 km (city range).
+- NOTE 18: Typical connection density in today's city environment. With the evolution from centralised meters to socket meters in the home, the connection density is expected to increase 5 to 10 times.
+- NOTE 19: When the distributed terminals are deployed along an overhead line, there are about 54 terminals per square kilometre.
+- NOTE 20: When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals per square kilometre.
+- NOTE 21: Service bit rate of the smart metering application between the smart distribution transformer terminal and the energy end equipment. Once there are multiple smart grid applications, the required service bit rate will be higher.
+- NOTE 22: The end-to-end latency depends on the applications supported by the smart distribution transformer terminal. The lower the end-to-end latency, the more applications can be supported.
+- NOTE 23: The service area is circular with a radius between 100 m and 500 m (0.031 km2 to 0.79 km2).
+- NOTE 24: During the normal working phase of the feeder system, the heartbeat packet is transmitted periodically with a 1 s transfer interval. When a fault occurs, the heartbeat is sent with a 2 ms transfer interval.
+- NOTE 25: The maximum allowed delay between two protection relays would be between 5 ms and 10 ms, depending on the voltage (see IEC 61850-90-1 for more details [aa]). For some legacy systems, the end-to-end latency is usually set to 15 ms.
+- NOTE 26: For a sampling rate of 600 Hz, the transfer interval is 1.7 ms. For 1200 Hz, the transfer interval is 0.83 ms.
+
+Table 5.2-2: Communication service performance requirements for industrial wireless sensors
+
+| Characteristic parameter | | | | | | Influence quantity | | | | | Remarks |
+|--------------------------------------------------|--------------------------------------------------------------|-----------------------------|-------------------------------------|----------------------------------------------------------------|----------------------------------|------------------------------|------------------------|------------|-----------------------------------|--------------------|-------------------------------------------------------|
+| Communication service availability: target value | Communication service reliability: mean time between failure | End-to-end latency (note 6) | Transfer interval (note 1) (note 7) | Service bit rate: user experienced data rate (note 2) (note 7) | Battery lifetime [year] (note 3) | Message Size [byte] (note 7) | Survival time (note 7) | UE speed | UE density [UE / m 2 ] | Range [m] (note 4) | |
+| 99.99 % | ≥ 1 week | < 100 ms | 100 ms to 60 s | ≤ 1 Mbit/s | ≥ 5 | 20 (note 5) | 3 x transfer interval | stationary | Up to 1 | < 500 | Process monitoring, e.g. temperature sensor (A.2.3.2) |
+| 99.99 % | ≥ 1 week | < 100 ms | ≤ 1 s | ≤ 200 kbit/s | ≥ 5 | 25 k | 3 x transfer interval | stationary | Up to 0.05 | < 500 | Asset monitoring, e.g. vibration sensor (A.2.3.2) |
+| 99.99 % | ≥ 1 week | < 100 ms | ≤ 1 s | ≤ 2 Mbit/s | ≥ 5 | 250 k | 3 x transfer interval | stationary | Up to 0.05 | < 500 | Asset monitoring, e.g. thermal camera (A.2.3.2) |
+
+NOTE 1: The transfer interval deviates around its target value by $< \pm 25 \%$ .
+
+NOTE 2: The traffic is predominantly mobile originated.
+
+NOTE 3: Industrial sensors can use a wide variety of batteries depending on the use case, but in general they are highly constrained in terms of battery size.
+
+NOTE 4: Distance between the gNB and the UE.
+
+NOTE 5: The application-level messages in this use case are typically transferred over Ethernet. For small messages, the minimum Ethernet frame size of 64 bytes applies and dictates the minimum size of the PDU sent over the air interface.
+
+NOTE 6: It applies to both UL and DL unless stated otherwise.
+
+NOTE 7: It applies to UL.
+
+## 5.3 Aperiodic deterministic communication
+
+Aperiodic deterministic communication is without a pre-set sending time, but still with stringent requirements on timeliness and availability of the communication service. A description of aperiodic deterministic communication can be found in Clauses 4.3 and 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.3-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.3-1 can be found in Annex C.
+
+The 5G system shall be able to provide aperiodic deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.3-1.
+
+Table 5.3-1: Aperiodic deterministic communication service performance requirements
+
+| Characteristic parameter (KPI) | | | | Influence quantity | | | | | Remarks |
+|------------------------------------|---------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------------|------------------------------|---------------|-----------------------------|---------------------------------------------|-------------------------|------------------------------------------------------------------------------------------|
+| Communication service availability | Communication service reliability: mean time between failures | Max Allowed End-to-end latency (note 1) (note 5) | Service bit rate: user-experienced data rate (note 5) | Message size [byte] (note 5) | Survival time | UE speed (note 6) | # of UEs | Service Area (note 3) | |
+| > 99.999 9 % | ~ 1 week | 10 ms | UL: > 10 Mbit/s | – | – | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 | Mobile robots – video streaming (A.2.2.3) |
+| 99.999 9 % to 99.999 999 % | ~ 1 month | < 30 ms | > 5 Mbit/s | – | – | < 8 km/h (linear movement) | TBD | TBD | Mobile control panels - parallel data transmission (A.2.4.1) |
+| 99.999 999 % | 1 day | <8 ms (note 8) | 250 kbit/s | 40 to 250 | 16 ms | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m | Mobile Operation Panel: Emergency stop (emergency stop events) (A.2.4.1A) |
+| 99.999 9 % | – | < 50 ms | 0.59 kbit/s
28 kbit/s | < 100 | – | stationary | 10 km -2 to 100 km -2 | TBD | Smart grid millisecond level precise load control (A.4.5) |
+| > 99.9 % | ~ 1 month | < 10 ms | – | – | – | < 8 km/h (linear movement) | ≥ 3 | 20 m x 20 m x 4 m | Augmented reality; bi-directional transmission to image processing server (A.2.4.2) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < 1 ms (note 4) | 25 Mbit/s | – | – | stationary | 2 to 5 | 100 m x 30 m x 10 m | Wired-2-wireless 100 Mbit/s link replacement (A.2.2.4) |
+| 99.999 9 % to 99.999 999 % | ~ 10 years | < 1 ms (note 4) | 500 Mbit/s | – | – | stationary | 2 to 5 | 100 m x 30 m x 10 m | Wired-2-wireless 1 Gbit/s link replacement (A.2.2.4) |
+| > 99.9 % | – | DL: < 10 ms
UL:<1 s (rural) | DL: > 100 kbit/s
UL: > 5 Gbit/s (note 9) | – | – | stationary | > 100 | | Distributed energy storage; energy storage station video (A.4.6) |
+| > 99.99 % | – | < 100 ms (note 10); | DL:<1 Mbit/s | – | – | – | – | – | Advanced metering (A.4.7) |
+| > 99.999 % | – | 20 ms | – | < 100 byte | – | – | – | several km 2 | Distributed automated switching for isolation and service restoration (A.4.4.1) (note 7) |
+| > 99.999 9 % | | < 3 ms | – | 160 byte | – | – | – | – | Distributed Energy Resources (DERs) and micro-grids (A.4.9) (note 7) |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+
+NOTE 2: (void)
+
+NOTE 3: Length x width x height.
+
+NOTE 4: Scheduled aperiodic traffic with transfer interval (max end-to-end allowed latency < transfer interval).
+
+NOTE 5: It applies to both UL and DL unless stated otherwise.
+
+NOTE 6: It applies to both linear movement and rotation unless stated otherwise.
+
+NOTE 7: Communication includes two wireless links (UE to UE).
+
+NOTE 8: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
+
+NOTE 9: The service bit rate in one energy storage station can be calculated as follows: $12.5 \text{ Mbytes/s} \times 50 \text{ containers} \times 8 = 5 \text{ Gbit/s}$ .
+
+NOTE 10: The maximum allowed end-to-end latency is for accuracy fee control. It is the delay for one-way communication between the backend system and the 5G IoT device. The distance between the two is 40 km or lower (city range).
+
+## 5.4 Non-deterministic communication
+
+Non-deterministic communication subsumes all other traffic types than periodic/aperiodic deterministic communication. This includes periodic/aperiodic non-real-time traffic. A description of non-deterministic communication can be found in Clauses 4.3 and 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.4-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.4-1 can be found in Annex C.
+
+The 5G system shall be able to provide non-deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.4-1.
+
+**Table 5.4-1: Non-deterministic communication service performance requirements**
+
+| Characteristic parameter (KPI) | | Influence quantity | | | Remarks |
+|---------------------------------------------------------------|----------------------------------------------|-------------------------------------------------|--------------|--------------------------------------------------------|-------------------------------------------------|
+| Communication service reliability: mean time between failures | Service bit rate: user-experienced data rate | UE speed (note 2) | # of UEs | Service area (note 1) | |
+| ~ 1 month | DL: $\geq 1 \text{ Mbit/s}$ | $\sim 0 \text{ km/h}$
$\leq 75 \text{ km/h}$ | $\leq 100$ | $50 \text{ m} \times 10 \text{ m} \times 10 \text{ m}$ | Motion control - software updates (A.2.2.1) |
+| | UL: $> 10 \text{ Mbit/s}$ | $\leq 50 \text{ km/h}$
(linear movement) | $\leq 2,000$ | $\leq 1 \text{ km}^2$ | Mobile robots; real-time video stream (A.2.2.3) |
+
+NOTE 1: Length x width x height
+
+NOTE 2: It applies to both linear movement and rotation unless stated otherwise.
+
+## 5.5 Mixed traffic
+
+Mixed traffic cannot be assigned to one of the other communication patterns exclusively. Additional information on the underlying use cases of the sets of requirements in Table 5.5-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.5-1 can be found in Annex C.
+
+The 5G system shall be able to provide mixed traffic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.5-1.
+
+**Table 5.5-1: Mixed traffic communication service performance requirements**
+
+| Characteristic parameter (KPI) | | | | Influence quantity | | | | | Remarks |
+|------------------------------------|---------------------------------------------------------------|--------------------------------------------------|--------------------------------------------------------|---------------------|---------------|-----------------------------|-----------|-------------------------|--------------------------------------------------------------|
+| Communication service availability | Communication service reliability: mean time between failures | Max Allowed End-to-end latency (note 1) (note 3) | Service bit rate: aggregate user-experienced data rate | Message Size [byte] | Survival time | UE speed | # of UEs | Service Area | |
+| 99.999 999 9 % | ~ 10 years | 16 ms | | | | stationary | < 1,000 | several km 2 | Wind power plant – control traffic (A.5.2) |
+| 99.999 9 % to 99.999 99 % | 1 day | (note 4) | 12 Mbit/s | 250 to 1,500 | | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m | Mobile Operation Panel: Manufacturing data stream (A.2.4.1A) |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+NOTE 2: (void)
+NOTE 3: It applies to both UL and DL unless stated otherwise.
+NOTE 4: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
+
+## 5.6 Clock synchronisation requirements
+
+### 5.6.0 Description
+
+Clock synchronicity, or time synchronization precision, is defined between a sync master and a sync device. The requirement on the synchronicity budget for the 5G system is the time error contribution between ingress and egress of the 5G system on the path of clock synchronization messages.
+
+Clock synchronisation requirements specific for direct device connection and indirect network connection are captured in section 7.2.3 and 8.2.3.
+
+### 5.6.1 Clock synchronisation service level requirements
+
+The 5G system shall support a mechanism to process and transmit IEEE 1588v2 / Precision Time Protocol messages to support 3rd-party applications which use this protocol.
+
+The 5G system shall support a mechanism to synchronise the user-specific time clock of UEs with a global clock.
+
+The 5G system shall support a mechanism to synchronize the user-specific time clock of UEs with a working clock.
+
+The 5G system shall support two types of synchronization clocks, the global time domain and the working clock domains.
+
+The 5G system shall support networks with up to 128 working clock domains (with different synchronization domain identifiers / domain numbers), including for UEs connected through the 5G network.
+
+NOTE 1: The domain number (synchronization domain identifier) is defined with one octet in IEEE 802.1AS [22].
+
+The 5G system shall be able to support up to four simultaneous synchronization domains on a UE.
+
+NOTE 1A: The four synchronization domains are used, for example, as two synchronization domains for global time and two working clock domains. One pair of global time and working clock is used as redundant synchronization domains for zero failover time.
+
+The synchronicity budget for the 5G system within the global time domain shall not exceed 900 ns.
+
+NOTE 2: The global time domain requires in general a precision of 1 $\mu\text{s}$ between the sync master and any device of the clock domain. Some use cases require only a precision of $\leq 100 \mu\text{s}$ for the global time domain if a working clock domain with precision of $\leq 1 \mu\text{s}$ is available.
+
+NOTE 3: (void)
+
+The synchronicity budget for the 5G system within a working clock domain shall not exceed 900 ns.
+
+NOTE 4: The working clock domains require a precision of $\leq 1 \mu\text{s}$ between the sync master and any device of the clock domain.
+
+NOTE 5: Different working clock domains are independent and can have different precision.
+
+NOTE 6: The synchronicity budget for the 5G system is also applicable when the flow of clock synchronization messages traverses the air interface twice.
+
+The 5G system shall provide a media-dependent interface for one or multiple IEEE 802.1AS sync domains [22].
+
+The 5G system shall provide an interface to the 5G sync domain which can be used by applications to derive their working clock domain or global time domain (Reference Clock Model).
+
+The 5G system shall provide an interface at the UE to determine and to configure the precision and time scale of the working clock domain.
+
+The 5G system shall be able to support arbitrary placement of sync master functionality and sync device functionality in integrated 5G / non-3GPP TSN networks.
+
+The 5G system shall be able to support clock synchronization through the 5G network if the sync master and the sync devices are served by different UEs. (Flow of clock synchronization messages is in either direction, UL and DL.)
+
+The 5G system shall provide a suitable means to support the management of the merging and separation of working clock domains, that is interoperable with the corresponding mechanisms of TSN and IEEE 802.1AS.
+
+The 5G system shall provide a suitable means to support precise time distribution, clock synchronization and synchrophasor communication functionalities specific to smart grid applications, e.g.:
+
+- IEC 61850-9-3 [30] profile and IEEE Std C37.238-2017 [31].
+- at least one of the two profiles for synchrophasor communications: IEC 61850-90-5:2012 [32], or IEEE Std C37.118.2-2011 [33].
+
+NOTE 7: The requirement above assumes the ability to support all main clock synchronization functionalities defined in the respective references, unless explicitly indicated. Support of IEC 61850-90-5 can entail supporting multiple profiles (e.g. A-profile, T-profile, KDC-profile and IEEE 802.1Q QoS profiles can be applicable for support of synchrophasor communications).
+
+### 5.6.2 Clock synchronisation service performance requirements
+
+**Table 5.6.2-1: Clock synchronization service performance requirements for 5G System**
+
+| User-specific clock synchronicity accuracy level | Number of devices in one communication group for clock synchronisation | 5GS synchronicity budget requirement (note 1) | Service area | Scenario |
+|--------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | up to 300 UEs | ≤ 900 ns | ≤ 100 m x 100 m | - - Motion control (A.2.2.1)
- - Control-to-control communication for industrial controller (A.2.2.2)
|
+| 2 | up to 300 UEs | ≤ 900 ns | ≤ 1,000 m x 100 m | - - Control-to-control communication for industrial controller (A.2.2.2)
|
+| 3 | up to 10 UEs | < 10 µs | ≤ 2,500 m 2 | - - High data rate video streaming
|
+| 3a | up to 100 UEs | < 1 µs | ≤ 10 km 2 | - - AVPROD synchronisation and packet timing
|
+| 4 | up to 100 UEs | < 1 µs | < 20 km 2 | - - Smart Grid: synchronicity between PMUs
|
+| 4a | up to 100 UEs | < 250 ns to 1 µs | < 20 km 2 | Smart Grid: IEC 61850-9-2 Sampled Values |
+| 4b | up to 100 UEs | <10-20 µs | < 20 km 2 | Smart Grid: IEC 61850-9-2 Sampled Values – Power system protection in digital substation |
+| 4c | 54/km 2 (note 2)
78/km 2 (note 3) | < 10 µs | several km 2 | Smart Grid: Intelligent Distributed Feeder Automation (A.4.4.3) |
+| 4d | up to 100 UEs | <1 ms | < 20 km 2 | Smart Grid: IEC 61850-9-2 Sampled Values – Event reporting and Disturbance recording |
+| 5 | up to 10 UEs | < 50 µs | 400 km | - - Telesurgery (A.6.2) and telediagnosis (A.6.3)
|
+
+NOTE 1: The clock synchronicity requirement refers to the clock synchronicity budget for the 5G system, as described in Clause 5.6.1.
+
+NOTE 2: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre. The resulting power load density is 20 MW/km2.
+
+NOTE 3: When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals in one square kilometre. The resulting power load density is 20 MW/km2.
+
+## 5.6A Time-sensitive communication requirements
+
+The 5G system shall support the fully distributed model for configuration of time-sensitive networking.
+
+The 5G system shall support the fully distributed model for configuration of time-sensitive networking that is aligned with Multiple Stream Registration Protocol (MSRP, IEEE 802.1Q [19] clause 35.1), IEEE P802.1CS Link-local Registration Protocol (LRP) [24], and IEEE P802.1Qdd Resource Allocation Protocol (RAP) [25].
+
+The 5G system shall support the user-network / network-network interface for the dynamic configuration of the fully distributed model for time-sensitive networking.
+
+## 5.6B 5G Timing Resiliency
+
+To enable support of many critical services within the 5G network, additional requirements and KPIs that enhance the 5G system with timing resiliency are specified in TS 22.261 [2] clauses 6.36 and 7.8. Those enhancements enable use of the 5G system for time critical services in collaboration with or as a backup to other timing solution such as loss or degradation of GNSS reference timing.
+
+## 5.6C Support for infrastructure protection of electrical transmission
+
+### 5.6C.1 Description
+
+Transmission infrastructure is a key component of the energy system. Communication enables protection of this infrastructure. The algorithms involved depend on certain constraints must be met, particularly concerning the end-to-end latency.
+
+### 5.6C.2 Requirements
+
+The 5G system shall support an end-to-end latency of less than 5 ms or 10 ms, as requested by the UE initiating the communication.
+
+NOTE 1: Whether the end-to-end latency is 5 ms or 10 ms depends on the applied voltage level.
+
+NOTE 2: The end-to-end latency is between two UEs, including two wireless links.
+
+The 5G system shall support communication channel symmetry in terms of end-to-end latency (latency from UE1 to UE2, and end-to-end latency from UE2 to UE1), with an asymmetry of < 2ms.
+
+## 5.7 Positioning performance requirements
+
+### 5.7.1 General requirements
+
+High accuracy positioning is becoming essential for Factories of the Future. The reason for this is that tracking of mobile devices as well as mobile assets is becoming increasingly important in improving processes and increasing flexibility in industrial environments.
+
+The 5G system shall provide positioning information for a UE that is out of coverage of the network, with accuracy of < [1 m] relative to other UEs that are in proximity and in coverage of the network.
+
+Table 5.7.1-1 below lists typical scenarios and the corresponding high positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
+
+NOTE: The column on "Corresponding Positioning Service Level in TS 22.261" maps the scenarios listed in Table 5.7.1-1 to the service levels defined in TS 22.261 [2].
+
+**Table 5.7.1-1: Positioning performance requirements**
+
+| Scenario | Horizontal accuracy | Vertical accuracy | Availability | Heading | Latency for position estimation of UE | UE speed | Corresponding Positioning Service Level in TS 22.261 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------|--------------|------------|---------------------------------------|-----------|------------------------------------------------------|
+| Mobile control panels with safety functions (non-danger zones) | < 5 m | < 3 m | 90 % | n/a | < 5 s | n/a | Service Level 2 |
+| Process automation – plant asset management | < 1 m | < 3 m | 90 % | n/a | < 2 s | < 30 km/h | Service Level 3 |
+| Flexible, modular assembly area in smart factories (for tracking of tools at the work-place location) | < 1 m (relative positioning) | n/a | 99 % | n/a | 1 s | < 30 km/h | Service Level 3 |
+| Augmented reality in smart factories | < 1 m | < 3 m | 99 % | < 0.17 rad | < 15 ms | < 10 km/h | Service Level 4 |
+| Mobile control panels with safety functions in smart factories (within factory danger zones) | < 1 m | < 3 m | 99.9 % | < 0.54 rad | < 1 s | n/a | Service Level 4 |
+| Flexible, modular assembly area in smart factories (for autonomous vehicles, only for monitoring purposes) | < 50 cm | < 3 m | 99 % | n/a | 1 s | < 30 km/h | Service Level 5 |
+| Inbound logistics for manufacturing (for driving trajectories (if supported by further sensors like camera, GNSS, IMU) of indoor autonomous driving systems)) | < 30 cm (if supported by further sensors like camera, GNSS, IMU) | < 3 m | 99.9 % | n/a | 10 ms | < 30 km/h | Service Level 6 |
+| Inbound logistics for manufacturing (for storage of goods) | < 20 cm | < 20 cm | 99 % | n/a | < 1 s | < 30 km/h | Service Level 7 |
+
+### 5.7.2 Energy efficiency requirements for high accuracy positioning
+
+The 5G system shall support low power high accuracy positioning mechanisms that allow a battery-constrained UE to sustain a long lifetime without changing battery. Some corresponding use cases and example scenarios are captured in Annex A.7.2.
+
+## 5.8 Network operation requirements
+
+For use by Industry 4.0, the 5G system needs to meet various operational options that are not typical in a traditional mobile operator setting. Additional system requirements that enable a 5G system to support those options are included in this clause.
+
+5G system shall provide support for reliable communications when a UE serves as a TSN talker or listener so there is no single point of service failure.
+
+# --- 6 Ethernet applications
+
+## 6.1 Description
+
+This section lists the requirements applicable to the 5G system for supporting cyber-physical applications using Ethernet.
+
+For requirements pertaining to common, fundamental Ethernet transport requirements, and any requirements necessary to support the 5G LAN-type service, see Clause 6.24 in TS 22.261 [2].
+
+## 6.2 Requirements
+
+For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronisation defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet.
+
+For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronisation defined by IEEE 802.1AS across 5G-based Ethernet links and other ethernet transports such as wired and optical (EPON.)
+
+For infrastructure dedicated to high performance Ethernet applications, the accuracy of clock synchronisation should be better than 1 $\mu$ s.
+
+For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support enhancements for time-sensitive networking as defined by IEEE 802.1Q, e.g. time-aware scheduling with absolute cyclic time boundaries defined by IEEE 802.1Qbv [19], for 5G-based Ethernet links with PDU sessions type Ethernet.
+
+For infrastructure dedicated to high performance Ethernet applications, absolute cyclic time boundaries shall be configurable for flows in DL direction and UL direction.
+
+For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support coexistence of hard-RT traffic following a time-aware schedule and lower priority traffic. The lower priority traffic cannot have a performance degrading impact on the hard-RT traffic.
+
+The Ethernet transport service shall support routing based on information extracted from the Ethernet header information created based on IEEE 802.1Qbv.
+
+# --- 7 Direct device connection for cyber-physical control applications
+
+## 7.1 Description
+
+This section lists the requirements applicable to the 5G system for supporting cyber-physical control applications using wireless direct device connection.
+
+## 7.2 Requirements
+
+### 7.2.1 General
+
+The 5G system shall allow UEs to use direct device connection when the UEs are not served by a RAN.
+
+The 5G system shall be able to support direct device connection between UEs in close proximity using spectrum different than the spectrum being used for the 5GC-based communication.
+
+The 5G system shall be able to support direct device connection for 5G LAN-type private communication.
+
+The 5G system shall be able to support multicast communication between the UEs within the group of UEs using direct device connection .
+
+### 7.2.2 Network performance
+
+The 5G system shall be able to support direct device connection between a group of UEs for periodic deterministic communication (both unicast and multicast) with respective service performance requirements in Table 5.2-1 related to cooperative carrying.
+
+The 5G system shall be able to support mobility of the group of UEs using direct device connections with respective service performance requirements in Table 5.2-1 related to cooperative carrying.
+
+The 5G system shall be able to support direct device connection with respective service performance requirements in Table 5.2-1 related to cooperative carrying between UEs up to 50 m distance.
+
+### 7.2.3 Clock synchronization
+
+#### 7.2.3.1 Description
+
+This clause lists the service level requirements and performance requirements applicable to the 5G system for supporting clock synchronization for direct device connection, building on the description already provided in Clause 5.6.0.
+
+#### 7.2.3.2 Clock synchronization requirements
+
+The 5G system shall be able to support clock synchronization (working clock domain) between the UEs within the group of UEs using direct device connection ProSe communication.
+
+The 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile) or 5G sync domain-based clock synchronization among the group of UEs using direct device connection.
+
+The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs in the group of UEs using direct device connection.
+
+The 5G system shall be able to support up to four simultaneous synchronization domains on a UE using direct device connection.
+
+The 5G system using direct device connection shall support one or multiple time domains (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile or 5G sync domain configuration).
+
+The 5G system shall provide a suitable means to support the merging and separation of working clock domains at the UEs within the group of UEs connected by direct device connection, that is interoperable with the corresponding mechanisms of IEEE 802.1AS [22], IEEE Std 1588 [28], or 5G sync domain.
+
+For direct device connection, the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to Table 7.2.3.2-1. In this case, the sync master and sync device are located at or connected to two UEs which are connected via direct device connection.
+
+**Table 7.2.3.2-1: Direct device connection clock synchronization service performance requirements for 5G System**
+
+| Number of devices in one communication group for clock synchronization | 5GS synchronicity budget requirement (note 1) | Service area (note 2) | Scenario |
+|------------------------------------------------------------------------|-----------------------------------------------|----------------------------------------|-------------------------------------------------------|
+| 2 to 16 | ≤ 900 ns | 10 m x 10 m x 5 m;
50 m x 5 m x 5 m | Cooperative carrying – fragile work pieces; (A.2.2.5) |
+| 2 to 16 | ≤ 900 ns | 10 m x 10 m x 5 m;
50 m x 5 m x 5 m | Cooperative carrying – elastic work pieces; (A.2.2.5) |
+
+NOTE 1: 5G synchronicity budget is the time error between ingress and egress of the 5G system on the path of clock synchronization messages (as described in Clause 5.6.0). For direct device connection, the ingress is one UE and the egress the other directly connected UE.
+
+NOTE 2: Service Area for direct device connections between UEs (length x width x height). The group of UEs with direct device connections might move throughout the whole factory site (up to several km2).
+
+### 7.2.4 Service Continuity
+
+The 5G system shall be able to minimize service disruption for a group of UEs using direct device connection with respective service performance requirements in Table 5.2-1 related to cooperative carrying, when the group moves between a non-public network and a PLMN (subject to operator policies and agreement between the operators and service providers).
+
+### 7.2.5 Direct device connection via UE to UE relay
+
+The 5G system shall be able to support direct device connection via an UE to UE relay with respective service performance requirements in Table 5.2-1 related to cooperative carrying between UEs out of transmission range of each other.
+
+# --- 8 Indirect network connection for cyber-physical control applications
+
+## 8.1 Description
+
+This section lists the requirements applicable to the 5G system for supporting cyber-physical control applications using wireless indirect network connection.
+
+## 8.2 Requirements
+
+### 8.2.1 General
+
+The 5G system shall be able to support multicast communication between the UEs within the group of UEs using indirect network connection.
+
+### 8.2.2 Communication via indirect network connection
+
+The 5G system shall be able to provide service to an out-of-coverage UE via indirect network connection using one relay UE while meeting the performance requirements specified for the process automation use cases in Table 5.2-1 (related to Annex A.2.3.1 and A.2.3.2).
+
+### 8.2.3 Clock synchronization
+
+#### 8.2.3.1 Description
+
+This clause lists the service level requirements and performance requirements applicable to the 5G system for supporting clock synchronization for indirect network connection, building on the description already provided in Clause 5.6.0.
+
+#### 8.2.3.2 Clock synchronization requirements
+
+The 5G system shall be able to support clock synchronization (working clock domain) for UEs using indirect network connection.
+
+The 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile) or 5G sync domain-based clock synchronization for UEs using indirect network connection.
+
+The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs using indirect network connection.
+
+The 5G system shall be able to support up to four simultaneous synchronization domains on a UE using indirect network connection.
+
+The 5G system shall provide a suitable means to support the merging and separation of working clock domains at the UEs connected by indirect network connection, that is interoperable with the corresponding mechanisms of IEEE 802.1AS [22] or another applicable IEEE Std 1588 [28] profile or 5G sync domain.
+
+For indirect network connection between UEs using one UE-to-network relay, the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to Table 8.2.3.2-1.
+
+**Table 8.2.3.2-1: Indirect network connection clock synchronization service performance requirements for 5G System**
+
+| Number of devices in one communication group for clock synchronization | UE density [UE / m 2 ] | 5GS synchronicity budget requirement (note 1) | Service area (note 2) | Scenario |
+|------------------------------------------------------------------------|-----------------------------------|-----------------------------------------------|------------------------|----------------------------------------------------|
+| 10 to 20 UEs | - | < 1 ms | ≤ 100 m x 100 m x 50 m | Process automation – closed loop control (A.2.3.1) |
+| ≤ 10,000 to 100,000 | - | ≤ 1 ms | ≤ 10 km x 10 km x 50 m | Process and asset monitoring (A.2.3.2) |
+
+NOTE 1: 5G synchronicity budget is the time error between ingress and egress of the 5G system on the path of clock synchronization messages (as described in Clause 5.6.0). For indirect network connection, 3 cases are considered:
+1) If the path of clock synchronization messages is between device and network side, ingress and egress of the 5G system are the remote UE and the corresponding UPF on the network side.
+2) If ingress and egress of the 5G system are at the device side, the 5G synchronicity budget is the time error between the involved remote UE and the 5G sync master.
+3) If the sync master is inside the 5G system, the 5G synchronicity budget ingress is the sync master in the 5G system and egress is the remote UE.
+
+NOTE 2: Service Area for indirect network connections between UEs (length x width x height).
+
+### 8.2.4 Service Continuity
+
+The 5G system shall be able to minimize service disruption for a UE using indirect network connection with respective service performance requirements in Table 5.2-1 related to process automation, when the UE moves between a non-public network and a PLMN (subject to operator policies and agreement between the operators and service providers).
+
+# --- 9 Recovery of infrastructure for electrical distribution
+
+## 9.1 Description
+
+The robustness of the infrastructure for electrical power distribution may depend upon the possibility to operate telecommunication networks even during an energy system incident, in which electricity cannot be delivered to some network operator facilities. Through coordination between the network operator and the energy system operator, increases in the ability to recover the energy system operation can be achieved.
+
+## 9.2 Requirements
+
+Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the ability of the MNO's infrastructure to continue operation despite a lack of electrical supply service, specifying which physical regions would be affected in terms of physical topology and the remaining time in which operation is possible.
+
+NOTE1: This information can facilitate energy distribution system recovery operations.
+
+Subject to regulatory requirements, the 5G system shall support a mechanism by which a third party can, in the event of an energy distribution system service interruption, communicate the energy distribution system recovery status in terms of location and time table to the MNO.
+
+NOTE2: This information can facilitate MNO operations to facilitate energy system recovery.
+
+# --- Annex A (informative): Summary of service performance requirements
+
+## A.1 About the vertical domains addressed in this Annex
+
+A vertical domain is an industry or group of enterprises in which similar products or services are developed, produced, and provided.
+
+The vertical domains addressed in this Annex are
+
+- Factories of the Future (A.2);
+- electric-power distribution (A.4); and
+- central power generation (A.5); and
+- Connected hospitals or medical facilities (A.6).
+
+## --- A.2 Factories of the Future
+
+### A.2.1 Overview
+
+The manufacturing industry is currently subject to a fundamental change, which is often referred to as the "Fourth Industrial Revolution" or simply "Industry 4.0" [15]. The main goals of Industry 4.0 are—among others—the improvement of flexibility, versatility, resource efficiency, cost efficiency, worker support, and quality of industrial production and logistics. These improvements are important for addressing the needs of increasingly volatile and globalised markets. A major enabler for all this is cyber-physical production systems based on a ubiquitous and powerful connectivity, communication, and computing infrastructure. The infrastructure interconnects people, machines, products, and all kinds of other devices in a flexible, secure and consistent manner. Several different application areas can be distinguished:
+
+- 1) **Factory automation:** Factory automation deals with the automated control, monitoring and optimisation of processes and workflows within a factory. This includes aspects like closed-loop control applications (e.g., based on programmable logic or motion controllers) and robotics, as well as aspects of computer-integrated manufacturing. Factory automation generally represents a key enabler for industrial mass production with high quality and cost-efficiency. Corresponding applications are often characterised by highest requirements on the underlying communication infrastructure, especially in terms of communication service availability, determinism, and latency. In the Factories of the Future, static sequential production systems will be more and more replaced by novel modular production systems offering a high flexibility and versatility. This involves many increasingly mobile production assets, for which powerful wireless communication and localisation services are required.
+- 2) **Process automation:** Process automation refers to the control of production and handling of substances like chemicals, food & beverage, pulp, etc. Process automation improves the efficiency of production processes, energy consumption, and safety of the facilities. Sensors measuring process values, such as pressures or temperatures, are working in closed loops via centralised and decentralised controllers. In turn, the controllers interact with actuators, e.g., valves, pumps, heaters. Also, monitoring of attributes such as the filling levels of tanks, quality of material, or environmental data are important, as well as safety warnings or plant shut downs. Workers in the plant are supported by mobile devices. A process automation facility may range from a few 100 m2 to several km2, and the facility may be geographically distributed. Depending on the size, a production plant may have several 10,000 measurement points and actuators. Autarkic device power supply for years is needed in order to stay flexible and to keep the total costs of ownership low.
+
+- 3) **HMIs and production IT:** Human-machine interfaces (HMIs) include all sorts of devices for the interaction between people and production facilities, such as panels attached to a machine or production line, but also standard IT devices, such as laptops, tablet PCs, smartphones, etc. In addition, augmented- and virtual-reality applications are expected to play an increasingly important role in future.
+- 4) **Logistics and warehousing:** Organisation and control of the flow and storage of materials and goods in the context of industrial production. In this respect, intra-logistics is dealing with logistics within a certain property (e.g., within a factory), for example by ensuring the uninterrupted supply of raw materials on the shop floor level using automated guided vehicles (AGVs), fork-lifts, etc. This is to be seen in contrast to logistics between different sites. Warehousing particularly refers to the storage of materials and goods, which is also getting more and more automated, for example based on conveyors, cranes and automated storage and retrieval systems.
+- 5) **Monitoring and maintenance:** Monitoring of certain processes and/or assets in the context of industrial production without an immediate impact on the processes themselves (in contrast to a typical closed-loop control system in factory automation, for example). This particularly includes applications such as condition monitoring and predictive maintenance based on sensor data, but also big data analytics for optimising future parameter sets of a certain process, for instance. For these use cases, the data acquisition process is typically not latency-critical.
+
+For each of these application areas, a multitude of potential use cases exists, some of which are outlined in the following subclauses. These use cases can be mapped to the given application areas (see Table A.2.1-1).
+
+**Table A.2.1-1: Mapping of the considered use cases (columns) to application areas (rows)**
+
+| | Motion control | Control-to-control | Mobile control panels with safety | Mobile robots | Remote access and maintenance | Augmented reality | Closed-loop process control | Process monitoring | Plant asset management |
+|----------------------------|----------------|--------------------|-----------------------------------|---------------|-------------------------------|-------------------|-----------------------------|--------------------|------------------------|
+| Factory automation | X | X | | X | | | | | |
+| Process automation | | | | X | | | X | X | X |
+| HMIs and Production IT | | | X | | | X | | | |
+| Logistics and warehousing | | X | | X | | | | | X |
+| Monitoring and maintenance | | | | | X | | | | |
+
+### A.2.2 Factory automation
+
+#### A.2.2.1 Motion control
+
+A motion control system is responsible for controlling moving and/or rotating parts of machines in a well-defined manner, for example in printing machines, machine tools or packaging machines.
+
+A schematic representation of a motion control system is depicted in Figure A.2.2.1-1. A motion controller periodically sends desired set points to one or several actuators (e.g., a linear actuator or a drive) which thereupon perform a corresponding action on one or several processes (in this case usually a movement or rotation of a certain component). At the same time, sensors determine the current state of the process(es), e.g. the current position and/or rotation of one or multiple components, and send the actual values back to the motion controller. This is done in a strictly cyclic and deterministic manner, such that during one application cycle the motion controller sends updated set points to all actuators, and all sensors send their actual values back to the motion controller. Nowadays, typically Industrial Ethernet technologies are used for motion control systems.
+
+
+
+```
+
+graph LR
+ MC[Motion Controller] -- "Set Points" --> A[Actuator]
+ A -- "Act" --> P[Process]
+ P -- "Sense" --> S[Sensor]
+ S -- "Actual Values" --> MC
+
+```
+
+Schematic representation of a motion control system showing a closed-loop interaction between a Motion Controller, Actuator, Process, and Sensor. The Motion Controller sends 'Set Points' to the Actuator, which 'Acts' on the Process. The Process is 'Sensed' by the Sensor, which returns 'Actual Values' to the Motion Controller.
+
+Figure A.2.2.1-1: Schematic representation of a motion control system
+
+Table A.2.2.1-1: Service performance requirements for motion control
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------|---------------------|--------------------------------|--------------------------------|---------------|-----------|----------|---------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: lower bound | Transfer interval: upper bound | Survival time | UE speed | # of UEs | Service area (note) |
+| 1 | 99.999 to 99.999 99 | ~ 10 years | < transfer interval value | – | 50 | 500 µs – 500 ns | 500 µs + 500 ns | 500 µs | ≤ 72 km/h | ≤ 20 | 50 m x 10 m x 10 m |
+| 2 | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | – | 40 | 1 ms – 500 ns | 1 ms + 500 ns | 1 ms | ≤ 72 km/h | ≤ 50 | 50 m x 10 m x 10 m |
+| 3 | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | – | 20 | 2 ms – 500 ns | 2 ms + 500 ns | 2 ms | ≤ 72 km/h | ≤ 100 | 50 m x 10 m x 10 m |
+
+NOTE: Length x width x height.
+
+Use cases one to three
+
+Characteristic parameters and influence quantities for a communication service supporting the cyclic interaction described above.
+
+#### A.2.2.2 Control-to-control communication
+
+Control-to-control communication, i.e., the communication between different industrial controllers is already used today for different use cases, such as:
+
+- large machines (e.g., newspaper printing machines), where several controls are used to cluster machine functions, which need to communicate with each other; these controls typically need to be synchronised and exchange real-time data;
+- individual machines that are used for fulfilling a common task (e.g., machines in an assembly line) often need to communicate, for example for controlling and coordinating the handover of work pieces from one machine to another.
+
+Typically, a control-to-control network has no fixed configuration of certain controls that need to be present. The control nodes present in the network often vary with the status of machines and the manufacturing plant. Therefore, hot-plugging support for different control nodes is important and often used.
+
+**Table A.2.2.2-1: Service performance requirements for control-to control communication in motion control**
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------|-------------------|---------------|------------|----------|-----------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Message size [byte] | Transfer interval | Survival time | UE speed | # of UEs | Service area (note 1) |
+| 1 (note 2) | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | 1 k | ≤ 10 ms | 10 ms | stationary | 5 to 10 | 100 m x 30 m x 10 m |
+| 2 (note 2) | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | 1 k | ≤ 50 ms | 50 ms | stationary | 5 to 10 | 1,000 m x 30 m x 10 m |
+
+NOTE 1: Length x width x height.
+NOTE 2: Communication may include two wireless links (UE to UE)
+
+##### Use case one
+
+Control-to-control communication between different motion (control) subsystems, as addressed in Subclause A.2.2.1. An exemplary application for this is large printing machines, where it is not possible or desired to control all actuators and sensors by one motion controller only.
+
+##### Use case two
+
+Control-to-control communication between different motion (control) subsystems. Exemplary application for this are extra-large machines or individual machines used for fulfilling a common task (e.g., machines in an assembly line).
+
+#### A.2.2.3 Mobile robots
+
+Mobile robots and mobile platforms, such as automated guided vehicles, have numerous applications in industrial and intra-logistics environments and will play an increasingly important role in the Factory of the Future. A mobile robot essentially is a programmable machine able to execute multiple operations, following programmed paths to fulfil a large variety of tasks. This means, a mobile robot can perform activities like assistance in work steps, collaboration with other robots, e.g. for car assembly, and transport of goods, materials and other objects. Mobile robot systems are characterised by a maximum flexibility in mobility relative to the environment, with a certain level of autonomy and perception ability, i.e., they can sense and react with their environment.
+
+Autonomous guided vehicles (AGVs) are a sub-group of mobile robots. AGVs are driverless and used for moving materials efficiently within a facility. A detailed overview of the state of the art of autonomous-guided-vehicle systems is provided elsewhere in the literature [16]. All mobile robots incorporate all functionalities needed for an AGV.
+
+Today, the AGV's control intelligence is hosted inside the AGV. In the future, centralised fleet control will be hosted in the edge cloud, which will require reliable wireless communication between the control entity and all AGVs. Also, the current paradigm of pre-describing a route for the AGV will be replaced with target-based navigation. This paradigm change will make AGV routes more flexible.
+
+Mobile robots are monitored and controlled from a guidance control system. Radio-controlled guidance control is necessary to get up-to-date process information, to avoid collisions between mobile robots, to assign driving jobs to the mobile robots, and to manage the traffic of mobile robots. The mobile robots are track-guided by the infrastructure with markers or wires in the floor or guided by own surround sensors, like cameras and laser scanners.
+
+Mobile robot systems can be divided in operation in indoor, outdoor and both indoor and outdoor areas. These environmental conditions have an impact on the requirements of the communication system, e.g., the handover process, to guarantee the required cycle times.
+
+Where this document does not explicitly refer to AGVs, the term *mobile robots* applies to AGVs as well as to mobile robots.
+
+Table A.2.2.3-1: Service performance requirements for mobile robots
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|----------------------------------|---------------------------------------------|---------------------|--------------------------------------------|----------------------------------------|--------------------------------------------|--------------------------------|-----------|----------|---------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: lower bound | Transfer interval: target value (note) | Transfer interval: upper bound | Survival time | UE speed | # of UEs | Service area |
+| 1 | > 99.999 9 | ~ 10 years | < target transfer interval value | – | 40 to 250 | – < 25 % of target transfer interval value | 1 ms to 50 ms | + < 25 % of target transfer interval value | target transfer interval value | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 |
+| 2 | > 99.999 9 | ~ 1 year | < target transfer interval value | – | 15 k to 250 k | – < 25 % of target transfer interval value | 10 ms to 100 ms | + < 25 % of target transfer interval value | target transfer interval value | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 |
+| 3 | > 99.999 9 | ~ 1 year | < target transfer interval value | – | 40 to 250 | – < 25 % of target transfer interval value | 40 ms to 500 ms | + < 25 % of target transfer interval value | target transfer interval value | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 |
+| 4 | > 99.999 9 | ~ 1 week | 10 ms | > 10 Mbit/s | – | – | – | – | – | ≤ 50 km/h | ≤ 2,000 | ≤ 1 km 2 |
+
+NOTE: The transfer interval is not so strictly periodic in these use cases. The transfer interval deviates around its target value within bounds. The mean of the transfer interval is close to the target value.
+
+##### Use case one
+
+Periodic communication for the support of precise cooperative robotic motion control (transfer interval: 1 ms), machine control (transfer interval: 1 ms to 10 ms), co-operative driving (10 ms to 50 ms).
+
+##### Use case two
+
+Periodic communication for video-operated remote control.
+
+##### Use case three
+
+Periodic communication for standard mobile robot operation and traffic management.
+
+##### Use case four
+
+Real-time streaming data transmission (video data) from a mobile robot to the guidance control system.
+
+##### Additional information
+
+AGVs have the following needs.
+
+- The direct-device control is time-critical since the communication involves safety-relevant functions such as emergency stop and the avoidance of obstacles.
+- For the implementation of swarm intelligence, position and availability information are needed. A possible route change due to a blocked route affects the routes of all other AGVs that will follow. The communication is less time-critical than for safety-relevant functions.
+- Camera-based navigation requires high data rates. Examples for camera-based navigation are the positioning of boxes/containers, detection of persons and obstacles, as well as creation and administration of a map for flexible navigation. Note that sensor-based navigation requires lower data rates than camera-based navigation.
+
+Mobile robots have additional needs.
+
+- The mobile robot provides an additional service during transport (for instance quality inspection, scanning of surroundings, asset identification, carrying of work pieces). In order to reduce the uplink data rate, pre-compression of data is possible directly on the device. The communication is not or at least less time-critical than the motion control of the mobile robot.
+- The mobile robot needs to interact with the periphery (for instance intelligent storage racks, stationary robots, and moving machines). This communication is time-critical. Interaction with the periphery can be relevant at the start point, end point, and also at several intermediate stations (for instance the collection of parts from intelligent storage racks). The exact position and orientation can be determined by a centering station and the AGV sensors. Additional scanning by the robot with a video camera may be necessary.
+
+#### A.2.2.4 Wired to wireless link replacement
+
+In a traditional factory, the production environment is fixed. Machines that are cooperating are connected via cable, typically using an industrial ethernet technology like PROFINET. In order to increase flexibility in the production setup, the wired links are replaced with wireless links.
+
+
+
+The diagram illustrates a 'Production Cell' containing four machines: Machine 2, Machine 3, Machine 4, and Machine 5. At the top, a 'Supervisory PLC (S-PLC)' is shown with a '5G UE' icon. Below it, each machine is represented in a colored box: Machine 2 (green), Machine 3 (orange), Machine 4 (grey), and Machine 5 (pink). Each machine has its own '5G UE' icon. Machine 2 and Machine 5 are connected directly to the S-PLC's 5G UE. Machine 3 and Machine 4 are connected to a central switch/router, which is then connected to the S-PLC's 5G UE. Each machine is also connected to three smaller icons representing other devices or sensors.
+
+Diagram of a Production Cell showing four cooperating machines (Machine 2, Machine 3, Machine 4, Machine 5) connected wirelessly to a Supervisory PLC (S-PLC). Each machine is equipped with a 5G UE. The S-PLC is connected to all four machines via their 5G UEs.
+
+Figure A.2.2.4-1: Example of four cooperating machines with wireless connections (based on [26])
+
+We assume two or more machines (typically 4 or 5) to be cooperating with each other during production. In order to replace the cables, each machine is equipped with one UE, connected to the controller (shown in Figure A.2.2.4-1). The cooperating machine's communication can be divided into two types. Periodic traffic and a-periodic traffic. Both types are scheduled, therefore the a-periodic traffic is also adhering to the transfer interval. The traffic requirements are from the point of view of the UE and give the maximum aggregate traffic of all links. Meaning, the traffic per link may change according to the number of cooperating machines but the total traffic at the UE cannot exceed the given values.
+
+Table A.2.2.4-1: Service performance requirements for wired to wireless link replacement
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | | |
+|--------------------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|--------------------|-------------------|-----------------------|------------|----------|-----------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Data rate [Mbit/s] | Transfer interval | Survival time | UE speed | # of UEs | Service area (note 1) |
+| 1
(periodic traffic) | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | 50 | ≤ 1 ms | 3 x transfer interval | stationary | 2 to 5 | 100 m x 30 m x 10 m |
+| 1
(aperiodic traffic) | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | 25 | ≤ 1 ms (note 2) | | stationary | 2 to 5 | 100 m x 30 m x 10 m |
+| 2
(periodic traffic) | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | 250 | ≤ 1 ms | 3 x transfer interval | stationary | 2 to 5 | 100 m x 30 m x 10 m |
+| 2
(aperiodic traffic) | 99.999 9 to 99.999 999 | ~ 10 years | < transfer interval value | 500 | ≤ 1 ms (note 2) | | stationary | 2 to 5 | 100 m x 30 m x 10 m |
+
+NOTE 1: Length x width x height.
+
+NOTE 2: Transfer interval also applies for scheduled aperiodic traffic
+
+##### *Use case one*
+
+In the case of the 100 Mbit/s link replacement, 50 % periodic traffic and 25 % a-periodic traffic are assumed.
+
+##### *Use case two*
+
+In the case of the 1 Gbit/s link replacement, 25 % periodic traffic and 50 % a-periodic traffic are assumed.
+
+#### A.2.2.5 Cooperative carrying
+
+In a smart factory, large or heavy work pieces will be carried from one place to another by multiple mobile robots or AGVs. These mobile robots / AGVs need to work together in order to carry the large or heavy work piece safely. This cooperation is achieved with a cyber-physical control application that controls the drives and movements of the mobile robots / AGVs in a coordinated way, so that large or heavy work pieces are carried smoothly and safely from one place to another (see Figure 5.11.1-1).
+
+
+
+Diagram showing four mobile robots (AGVs) cooperatively carrying a large rectangular work piece. The robots are positioned at the corners of the work piece, with two on each side. A large blue arrow points to the left, indicating the direction of movement.
+
+**Figure A.2.2.5-1: Mobile robots / AGVs carrying a large work piece cooperatively**
+
+The communication between the collaborating mobile robots / AGVs requires high communication service availability and ultra-low latency. The exchange of control commands and control feedback is done with periodic deterministic communication and using time-sensitive networking.
+
+There are two distinct use case variants of cooperative carrying: (1) carrying of rigid or fragile work pieces that require very precise coordination between the collaborating mobile robots, and (2) carrying of more flexible or elastic work pieces that allow some tolerance in the coordinated movements of the collaborative mobile robots. The higher tolerance in the coordinated movements allows for either faster movement of the work piece or longer transfer intervals (trade-off between UE speed and transfer interval).
+
+**Table A.2.2.5-1: Service performance requirements for cooperative carrying**
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------|----------------------------------------|------------------------------------------|----------------------------------------------|-----------|----------|----------------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value (note 1) | Survival time (note 1) | UE speed | # of UEs | Service area (note 2) |
+| 1 | 99.999 9 to 99.999 999 | ~ 10 years | < 0.5 x transfer interval | 2.5 Mbit/s | 250; 500 with localisation information | > 5 ms
> 2.5 ms
> 1.7 ms | 0 transfer interval
2 x transfer interval | ≤ 6 km/h | 2 to 8 | 10 m x 10 m x 5 m;
50 m x 5 m x 5 m |
+| 2 | 99.999 9 to 99.999 999 | ~ 10 years | < 0.5 x transfer interval | 2.5 Mbit/s | 250; 500 with localisation information | > 5 ms
> 2.5 ms
> 1.7 ms | 0 transfer interval
2 x transfer interval | ≤ 12 km/h | 2 to 8 | 10 m x 10 m x 5 m;
50 m x 5 m x 5 m |
+
+NOTE 1: The first value is the application requirement, the other values are the requirement with multiple transmission of the same information (two or three times respectively).
+NOTE 2: Service Area for direct communication between UEs (length x width x height). The group of UEs with direct communication might move throughout the whole factory site (up to several km2)
+
+##### Use case one
+
+Periodic deterministic communication for cooperative carrying of fragile work pieces (UE to UE / ProSe communication).
+
+##### *Use case two*
+
+Periodic deterministic communication for cooperative carrying of elastic work pieces (UE to UE / ProSe communication).
+
+### A.2.3 Process automation
+
+#### A.2.3.1 Closed-loop control
+
+In the closed-loop control use case for process automation, several sensors are installed in a plant and each sensor performs continuous measurements. The measurement data are transported to a controller, which takes decision to set actuators. The latency and determinism in this use case are crucial. This use case has very stringent requirements in terms of latency and service availability. The required service area is usually bigger than for motion control use cases. Interaction with the public network (e.g., service continuity, roaming) is not required.
+
+**Table A.2.3.1-1: Service performance requirements for closed-loop control in process automation**
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|----------------------------------|---------------------|----------------------------------------|---------------------------------|----------------------------------------|---------------|----------------------|--------------------|----------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Message size [byte] | Transfer interval: lower bound | Transfer interval: target value | Transfer interval: upper bound | Survival time | UE speed | # of UEs | Service area (note) |
+| 1 | 99.999 9 to 99.999 999 | ≥ 1 year | < target transfer interval value | 20 | -5 % of target transfer interval value | ≥ 10 ms | +5 % of target transfer interval value | 0 | typically stationary | typically 10 to 20 | typically ≤ 100 m x 100 m x 50 m |
+
+NOTE: Length x width x height.
+
+##### *Use case one*
+
+Several sensors are installed in a plant and each sensor performs continuous measurements. The measurement data are transported to a controller, which takes decision to set actuators.
+
+#### A.2.3.2 Process and asset monitoring
+
+For process and asset monitoring in the area of process automation, a large number of industrial wireless sensors are installed in the plant to give insight into process and environmental conditions, asset health and inventory of material. The data are transported to displays for observation and/or to databases for registration and data analysis. Examples of sensors are temperature, pressure or flow rate sensors for process monitoring, vibration sensors for health monitoring of e.g. motors, or thermal cameras to detect leakages. Industrial wireless sensors are typically constrained in terms of size, complexity and/or power consumption. The operation for this use case can be in a wide service area, and interaction with the public network (e.g., service continuity, roaming) may be required.
+
+Table A.2.3.2-1: Service performance requirements for process and asset monitoring
+
+| Use case | Characteristic parameter | | | | | | Influence quantity | | | | | |
+|----------|------------------------------------------------------|--------------------------------------------------------------|--------------------|----------------------------|-------------------|----------------------------------|------------------------------|-----------------------|------------|-----------------------------------|--------------------|------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failure | End-to-end latency | Transfer interval (note 1) | Bit rate [bits/s] | Battery lifetime [year] (note 2) | Message Size [byte] (note 3) | Survival time | UE speed | UE density [UE / m 2 ] | Range [m] (note 4) | Service area (note 5) |
+| 1 | 99.99 | ≥ 1 week | < 100 ms | 100 ms to 60 s | ≤ 1 M | ≥ 5 | 20 (note 3) | 3 x transfer interval | Stationary | Up to 1 | < 500 | ≤ 10 km x 10 km x 50 m |
+| 2 | 99.99 | ≥ 1 week | < 100 ms | ≤ 1 s | ≤ 200 k | ≥ 5 | 25 k | 3 x transfer interval | Stationary | Up to 0.05 | < 500 | ≤ 10 km x 10 km x 50 m |
+| 3 | 99.99 | ≥ 1 week | < 100 ms | ≤ 1 s | ≤ 2 M | ≥ 5 | 250 k | 3 x transfer interval | Stationary | Up to 0.05 | < 500 | ≤ 10 km x 10 km x 50 m |
+
+NOTE 1: The transfer interval deviates around its target value by < ± 25 %.
+
+NOTE 2: Industrial sensors can use a wide variety of batteries depending on the use case, but in general they are highly constrained in terms of battery size.
+
+NOTE 3: The application-level messages in this use case are typically transferred over Ethernet, in which case the minimum Ethernet frame size of 64 bytes applies and dictates the minimum size of the PDU sent over the air interface.
+
+NOTE 4: Distance between the gNB and the UE.
+
+NOTE 5: Length x width x height.
+
+##### *Use case one*
+
+Sensors generating periodic measurements of a continuous value (e.g. temperature, pressure, flow rate sensors). The traffic is predominantly mobile originated.
+
+##### *Use case two*
+
+Sensors generating waveform measurements (e.g. vibration sensors). Even though the waveform measurement is continuous, it is expected that this type of sensors will buffer and transmit the data periodically (e.g. every second) to save battery by enabling discontinuous transmission. The traffic is predominantly mobile originated.
+
+##### *Use case three*
+
+Cameras (regular or thermal) for asset monitoring (e.g. for leakage detection). Even though the video recording is continuous, it is expected that this type of sensors will buffer and transmit the data periodically (e.g. every second) to save battery by enabling discontinuous transmission. The traffic is predominantly mobile originated.
+
+#### A.2.3.3 Plant asset management
+
+To keep a plant running, it is essential that the assets, such as pumps, valves, heaters, instruments, etc., are maintained. Timely recognition of any degradation and continuous self-diagnosis of components are used to support and plan maintenance. Remote software updates enhance and adapt the components to changing conditions and advances in technology. The operation for this use case can be in a wide service area, and interaction with the public network (e.g., service continuity, roaming) may be required. In this use case, the assets themselves are assumed to be connected to the 5G system. The use case where sensors are used to monitor assets is covered in clause A.2.3.2.
+
+Table A.2.3.3-1: Service performance requirements for plant asset management
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------|-------------------|--------------------------------------------------------------------------|----------------------|----------------|-------------------------------------------------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Message size [byte] | Transfer interval | Survival time | UE speed | # of UEs | Service area (note) |
+| 1 | 99.99 | TBD | < transfer interval value | 20 to 255 | several seconds | matter of convenience; typically $\geq 3 \times$ transfer interval value | typically stationary | $\leq 100,000$ | typically $\leq 10 \text{ km} \times 10 \text{ km} \times 50 \text{ m}$ |
+| NOTE: | Length x width x height. | | | | | | | | |
+
+##### *Use case one*
+
+To keep a plant running, it is essential that the assets, such as pumps, valves, heaters, and instruments are maintained. Timely recognition of any degradation and continuous self-diagnosis of components are used to support and plan maintenance. Remote software updates enhance and adapt the components to changing conditions and advances in technology.
+
+### A.2.4 Human machine interfaces
+
+#### A.2.4.1 Mobile control panels
+
+Control panels are crucial devices for the interaction between people and production machinery as well as for the interaction with moving devices. These panels are mainly used for configuring, monitoring, debugging, controlling and maintaining machines, robots, cranes or complete production lines. In addition to that, (safety) control panels are typically equipped with an emergency stop button and an enabling device, which an operator can use in case of a safety event in order to avoid damage to humans or machinery. When the emergency stop button is pushed, the controlled equipment immediately comes to a safe stationary position. Likewise, if a machine, robot, etc. is operated in the so-called special 'enabling device mode', the operator manually keeps the enabling device switch in a special stationary position. If the operator pushes this switch too much or releases it, the controlled equipment immediately comes to a safe stationary position as well. This way, it can be ensured that the hand(s) of the operator are on the panel (and not under a moulding press, for example), and that the operator does—for instance—not suffer from any electric shock or the like. A common use case for this 'enabling device mode' is the installation, testing or maintenance of a machine, during which other safety mechanisms (such as a safety fence) are deactivated.
+
+Due to the criticality of these safety functions, safety control panels currently have mostly a wire-bound connection to the equipment they control. In consequence, there tend to be many such panels for the many machines and production units that typically can be found in a factory. With an ultra-reliable low-latency wireless link, it would be possible to connect such mobile control panels with safety functions wirelessly. This would lead to a higher usability and would allow for the flexible and easy re-use of panels for controlling different machines.
+
+The cycle times of the control application depends on the process/machinery/equipment whose safety has to be ensured. For a fast-moving robot, for example, end-to-end latencies are lower than for slowly moving linear actuators.
+
+Table A.2.4.1-1: Service performance requirements for mobile control panels
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|----------------------------------|---------------------------------------------|---------------------|--------------------------------------------|---------------------------------|------------------------------------------|--------------------------------|------------|----------|----------------------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: lower bound | Transfer interval: target value | Transfer interval: upper bound | Survival time | UE speed | # of UEs | Service area (note 1) |
+| 1 (note 3) | 99.999 9 to 99.999 999 | ~ 1 month | < target transfer interval value | – | 40 to 250 | – < 25 % of target transfer interval value | 4 ms to 8 ms | + 25 % of target transfer interval value | target transfer interval value | < 7.2 km/h | TBD | 50 m x 10 m x 4 m |
+| 2 (note 3) | 99.999 9 to 99.999 999 | ~ 1 month | < target transfer interval value | > 5 Mbit/s | – | – < 25 % of target transfer interval value | < 30 ms | + 25 % of target transfer interval value | TBD | < 7.2 km/h | TBD | TBD |
+| 3 (note 3) | 99.999 9 to 99.999 999 | ~ 1 year | < target transfer interval | – | 40 to 250 | – < 25 % of target transfer interval value | < 12 ms | + 25 % of target transfer interval value | 12 ms | < 7.2 km/h | TBD | typically 40 m x 60 m; maximum 200 m x 300 m |
+
+NOTE 1: Length x width (x height).
+NOTE 2: The transfer interval is not so strictly periodic in these use cases. The transfer interval deviates around its target value within bounds. The mean of the transfer interval is close to the target value.
+NOTE 3: Communication may include two wireless links (UE to UE)
+
+##### *Use case one*
+
+Periodic, bi-directional communication for remote control. Examples for controlled units: assembly robots; milling machines.
+
+##### *Use case two*
+
+Aperiodic data transmission in parallel to remote control (use case one).
+
+##### *Use case three*
+
+Periodic, bi-directional communication for remote control. Examples for controlled units: mobile cranes, mobile pumps, fixed portal cranes.
+
+#### A.2.4.1A Mobile operation panels
+
+Operation and monitoring of machines, mobile robots, or production units via a mobile operation panel provides higher flexibility and comfort for human operators. A single mobile operation panel can be used to manage more than one production system due to its mobility in the factory. The mobile operation panel provides relevant information for configuration, control of industrial machines as well as monitoring of relevant data generated during the construction of a product. The monitoring data is generally considered to be less time-critical subsequently requiring non-real-time communication. On the other hand, the mobile operation panel supports safety-critical functions such as emergency stops or enabling or changing the position of robots and other machines. These functions are generally considered to have strict ultra-low latencies and reliable transmission requirements that must follow strict safety standards making them time-critical (real-time communication).
+
+**Table A.2.4.1A-1: Service performance requirements for mobile operation panels**
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------|--------------------|---------------------|---------------------------------|-------------------|-----------------------------|-----------|--------------------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Direction (note 2) | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area (note 1) |
+| 1 | 99.999 999 | 1 day | < 8 ms | 250 kbit/s | Uplink
Downlink | 40 to 250 | 8 ms | 16 ms | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m |
+| 2 | 99.999 99 | 1 day | < 10 ms | < 1 Mbit/s | Uplink | < 1,024 | 10 ms | ~10 ms | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m |
+| 3 | 99.999 999 | 1 day | 10 ms to 100 ms | 10 kbit/s | Uplink
Downlink | 10-100 | 10-100 ms | transfer interval | stationary | 2 or more | 100 m 2 to 2,000 m 2 |
+| 4 | 99.999 999 | 1 day | < 1 ms | 12 Mbit/s to 16 Mbit/s | Downlink | 10-100 | 1 ms | ~1 ms | stationary | 2 or more | 100 m 2 |
+| 5 | 99.999 999 | 1 day | < 2 ms | 16 kbit/s (UL)
2 Mbit/s (DL) | Uplink
Downlink | 50 | 2 ms | ~2 ms | stationary | 2 or more | 100 m 2 |
+| 6 | 99.999 9 to 99.999 99 | 1 day | up to [x] | 12 Mbit/s | Uplink
Downlink | 250 to 1,500 | | | quasi-static; up to 10 km/h | 2 or more | 30 m x 30 m |
+
+NOTE 1: Length x width.
+
+NOTE 2: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
+
+##### Use case one
+
+Emergency Stop with periodic-deterministic communication for connectivity availability and aperiodic-deterministic communication for emergency stop events.
+
+##### *Use case two*
+
+Safety data stream with periodic deterministic communication.
+
+##### *Use case three*
+
+Visualization of Control with periodic deterministic communication.
+
+##### *Use case four*
+
+Motion Control with periodic deterministic communication.
+
+##### *Use case five*
+
+Haptic feedback data stream with periodic deterministic communication.
+
+##### *Use case six*
+
+Manufacturing data stream with mixed traffic.
+
+#### A.2.4.2 Augmented reality
+
+It is envisioned that in future smart factories and production facilities, people will continue to play an important and substantial role. However, due to the envisaged high flexibility and versatility of the Factories of the Future, shop floor workers should be optimally supported in getting quickly prepared for new tasks and activities and in ensuring smooth operations in an efficient and ergonomic manner. To this end, augmented reality may play a crucial role, for example for the following applications:
+
+- monitoring of processes and production flows;
+- step-by-step instructions for specific tasks, for example in manual assembly workplaces;
+- ad hoc support from a remote expert, for example for maintenance or service tasks.
+
+In this respect, especially head-mounted augmented-reality devices with see-through display are very attractive since they allow for a maximum degree of ergonomics, flexibility and mobility and leave the hands of workers free for other tasks. However, if such augmented-reality devices are worn for a longer period (e.g., one work shift), these devices have to be lightweight and highly energy-efficient while at the same time they should not become very warm. A very promising approach is to offload complex (e.g., video) processing tasks to the network (e.g., an edge cloud) and to reduce the augmented-reality head-mounted device's functionality. This has the additional benefit that the augmented-reality application may have easy access to different context information (e.g., information about the environment, production machinery, the current link state, etc.) if executed in the network.
+
+**Table A.2.4.2-1: Service performance requirements for augmented reality in human-machine interfaces**
+
+| Use case # | Characteristic parameter | | | Influence quantity | |
+|--------------------------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|--------------------|---------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | UE speed | Service area (note) |
+| 1 | > 99.9 | ~ 1 month | < 10 ms | < 8 km/h | 20 m x 20 m x 4 m |
+| NOTE: Length x width x height. | | | | | |
+
+##### Use case one
+
+Bi-directional message transmission between an augmented-reality device and an image processing server.
+
+### A.2.5 Monitoring and maintenance
+
+#### A.2.5.1 Remote access and maintenance
+
+In factories of the future, there are needs to perform remote access and maintenance to devices and entities, for instance, by remote control centres. The devices and entities might be installed at geographically distributed locations. These devices typically have firmware/software which needs to be updated occasionally. Maintenance information also needs to be collected and distributed from/to these devices periodically. The devices can be both stationary and mobile. Device maintenance may happen in parallel to the actual production process and other communication services performed at the device side without any negative impact on these production communication services.
+
+Table A.2.5.1-1: Service performance requirements for remote access and maintenance
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------|---------------------|--------------------------------|--------------------------------|---------------|-----------|----------|---------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: lower bound | Transfer interval: upper bound | Survival time | UE speed | # of UEs | Service area (note) |
+| 1 | – | ~ 1 month | – | ≥ 1 Mbit/s | – | – | – | – | ≤ 72 km/h | ≤ 100 | 50 m x 10 m x 10 m |
+| NOTE: | Length x width x height. | | | | | | | | | | |
+
+##### *Use case one*
+
+Transmission of non-deterministic messages in parallel to other interactions. Example applications: software/firmware updates and exchange of maintenance information.
+
+##### --- A.3 (void) ---
+
+## A.4 Electric-power distribution and Smart Grid
+
+### A.4.1 Overview
+
+The energy sector is currently subject to a fundamental change, which is caused by the evolution towards renewable energy, i.e. an increasing number of power plants based on solar and wind power. These changes lead to bi-directional electricity flows and increased dynamics of the power system. New sensors and actuators are being deployed in the power system to efficiently monitor and control the volatile conditions of the grid, requiring real-time information exchange [11][12].
+
+The emerging electric-power distribution grid is also referred to as Smart Grid. The smartness enhances insight into both the grid as a power network and the grid as a system of systems. Enhanced insight improves controllability and predictability, both of which drive improved operation and economic performance and both of which are prerequisites for the sustainable and scalable integration of renewables into the grid and the potential transition to new grid architectures. Smart Grid benefits spread across a broad spectrum but generally include improvements in: power reliability and quality; grid resiliency; power usage optimisation; operational insights; renewable integration; insight into energy usage; and safety and security.
+
+Overviews of (future) electric-power distribution can be found elsewhere in the literature [13][14].
+
+### A.4.2 Primary frequency control
+
+Primary frequency control is among the most challenging and demanding control applications in the utility sector. A primary frequency control system is responsible for controlling the energy supply injected and withheld to ensure that the frequency is not deviating more than 0.02 % from the nominal value (e.g., 50 Hz in Europe). Frequency control is based on having sensors for measuring the features in all parts of the network at all points where energy generation or storage units are connected to the grid. At these points, electronic power converters, also known as inverters, are equipped with communication units to send measurement values to other points in the grid such as a frequency control unit, or receive control commands to inject more, or less, energy into the local network.
+
+With the widespread deployment of local generation units, i.e. solar power units, or wind turbines, hundreds of thousands of such units, and their inverters, may have to be connected in a larger power distribution network.
+
+Primary frequency control is carried out in one of three ways:
+
+- 1) Centralised control, all data analysis and corrective actions are determined by a central frequency control unit.
+- 2) Decentralised control, the automatic routine frequency control is performed by the individual local inverter based on local frequency values. Statistics and other information is communicated to the central frequency control unit.
+- 3) Distributed control, the automatic routine frequency control is performed by the individual local inverter based on local and neighbouring frequency values. Statistics and other information are communicated to the central frequency control unit.
+
+**Table A.4.2-1: Service performance requirements for primary frequency control**
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------|---------------------------------|---------------|-----------|-------------------------------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Message size [byte] | Transfer interval: target value | Survival time | # of UEs | Service area |
+| 1 | 99.999 | TBD | ~ 50 ms | ~ 100 | ~ 50 ms | TBD | ≤ 100,000 | several km 2 up to 100,000 km 2 |
+
+#### *Use case one*
+
+Periodic communication service supporting message exchange for primary frequency control.
+
+### A.4.3 Distributed voltage control
+
+In the evolution towards 100 % renewable electric power production, the objective of voltage control is to balance the voltage in future low voltage distribution grids connecting local loads and prosumers, as well as energy storage facilities. The aim is to stabilise the voltage as locally as possible, so that decisions and control commands can be issued as quickly as possible. Distributed voltage control is a challenging and demanding control application. Consumer devices rely on having stable voltage levels to operate successfully. When future energy networks rely on thousands of local energy generation units relying mostly on solar and wind power, then it is crucial to stabilise the voltage levels in all segments of the distribution grid. Inverters, or electronic power converters, measure the voltage and power and change the amount of power injected into the grid, and they connect and disconnect end points from the distribution network.
+
+Distributed control means that the automated voltage control shall be performed by the local voltage control units based on local *and neighbouring* voltage and impedance values. Statistics and other information shall be communicated to the central distribution management system, though.
+
+**Table A.4.3-1: Service performance requirements for distributed voltage control**
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------|---------------------------------|---------------|-----------|-------------------------------------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Message size [byte] | Transfer interval: target value | Survival time | # of UEs | Service area |
+| 1 | 99.999 | TBD | ~ 100 ms | ~ 100 | ~ 200 ms | TBD | ≤ 100,000 | several km 2 up to 100,000 km 2 |
+
+#### *Use case one*
+
+Periodic communication service supporting message exchange for distributed voltage control.
+
+### A.4.4 Distributed energy automation
+
+#### A.4.4.1 Distributed automated switching for isolation and service restoration
+
+A power distribution grid fault is a stressful situation. There are self-healing solutions for automated switching, fault isolation, and service restoration. Furthermore, these solutions are ideally suited to handle outages that affect critical
+
+power consumers, such as industrial plants or data centres. Supply interruptions must be fixed within less than a second for critical power consumers. Automated solutions are able to restore power supply within a few hundred milliseconds.
+
+
+
+The diagram illustrates a distribution ring network. At the center is a hub labeled 'IEC 61850-GOOSE'. Surrounding this hub are several nodes, each represented by an icon: a house, a factory, a substation, and another house. These nodes are connected to the central hub via lines. A fault, indicated by a lightning bolt icon, occurs on one of the lines. The system then performs 'Service restoration', shown by a red circle with a white 'X' and the text 'Service restoration'. Another node is labeled 'NOP' (No Operation). The entire network is enclosed in a large circle, and the background is a light grey gradient.
+
+Diagram of a distribution ring showing a fault and service restoration. A central 'IEC 61850-GOOSE' hub is connected to multiple nodes (houses, factory, substation) via a ring of lines. A fault (flash of lightning) occurs on one line, and the system performs 'Service restoration' to restore power. The diagram also shows 'NOP' (No Operation) at one node.
+
+**Figure A.4.4.1-1: Depiction of a distribution ring and a failure (flash of lightning)**
+
+The FLISR (Fault Location, Isolation & Service Restoration) solution consists of switch controller devices which are especially designed for feeder automation applications that support the self-healing of power distribution grids with overhead lines. They serve as control units for reclosers and disconnectors in overhead line distribution grids.
+
+The system is designed for using fully distributed, independent automated devices. The logic resides in each individual feeder automation controller located at the poles in the feeder level. Each feeder section has a controller device. Using peer-to-peer communication among the controller devices, the system operates autonomously without the need of a regional controller or control centre. However, all self-healing steps carried out will be reported immediately to the control centre to keep the grid status up to date. The controllers conduct self-healing of the distribution line in typically 500 ms by isolating the faults.
+
+Peer-to-peer communication via IEC 61850 GOOSE (Generic Object Oriented Substation Event) messages provides data as fast as possible (Layer 2 multicast message). They are sent periodically (in steady state, with changing interval time in fault case) by each controller to several or all other controllers of the same feeder and are not acknowledged.
+
+The service bit rate per controller is low in steady state, but GOOSE bursts with high service bit rate do occur, especially during fault situations. GOOSE messages are sent by several or all controller units of the feeder nearly at the same point in time during the fault location, isolation and service restoration procedure with a low end-to-end latency.
+
+The associated (a)periodic communication KPIs are provided in Table A4.4.1-1.
+
+Table A.4.4-1.1: Service performance requirements for distributed automated switching for isolation and service restoration
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | |
+|---------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|----------------------------------------------------|---------------------|----------------------------------------------|------------------------------------|------------|-----------------------|-------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area (note 1) |
+| 1
(note 2) | 99.999 9 | – | < 5 ms | 1 kbit/s (steady state)
1.5 Mbit/s (fault case) | < 1,500 | < 60 s (steady state)
≥ 1 ms (fault case) | transfer interval (one frame loss) | stationary | 20 | 30 km x 20 km |
+| 2 | > 99.999 % | - | 20 ms (note 2) | - | < 100 | - | - | stationary | ≤ 100/km 2 | several km 2 |
+
+NOTE 1: Length x width
+
+NOTE 2: UE to UE communication (two wireless links)
+
+##### *Use case one*
+
+GOOSE (a)periodic deterministic communication service supporting bursty message exchange for fault location, isolation, and service restoration.
+
+##### *Use case two*
+
+Typically event-driven, aperiodic deterministic communication service supporting fault detection and isolation.
+
+#### A.4.4.2 Distributed automation without GOOSE
+
+If the control of electrical power distribution components is performed from a central system entity, the controlled entities can be operated in a way that a controlled service restoration is possible without the use of GOOSE. Though this is not as effective as the communication has less strict requirements, this form of distribution automation is nevertheless effective, and it is also compliant with IEC standards and widely deployed in energy systems. The associated KPI is provided in Table A.4.4.2-1.
+
+Table A.4.4.2-1: KPI for distributed automation without use of GOOSE
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------|---------------------|---------------------------------|---------------|----------|-----------------------------------------------------------------------------------------------------------|-------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| 1 | 99.999 | – | 100 ms to 2 s | 9.6 to 100 | – | – | – | – | Concentrated rural: 70.8;
Dispersed rural and semi-urban: 7.6;
rural support: 0.048;
urban: 11.0 | several km 2 |
+
+##### Use case one
+
+Distributed automation without use of GOOSE using a centralized architecture.
+
+#### A.4.4.3 Intelligent distributed feeder automation
+
+Intelligent distributed feeder automation system which supported by 5G connections is designed to realize intelligent judgment, analysis, fault location, fault isolation and non-fault area power supply restoration operations. As illustrated in the Figure A.4.4.3-1, the distributed feeder automation system is mainly composed of a distribution master station, a distribution terminal, switch stations, and the communication system (UEs in the substations, 5G network, plus the data network). The distribution master station is mainly used for information gathering and human-computer interaction, and the distributed terminals are used for the collection of feeder status information and judgment, fault location, isolation, as well as power supply restoration based on this information. Distributed terminal actions are reported to the distribution master station. The 5G communication system enables communication among the distribution terminals. The distribution master station is usually connected to the 5G system via a data network, which is out of 3GPP scope.
+
+
+
+The diagram illustrates an intelligent distributed feeder automation architecture. At the top, a 'Distributed Master Station' is connected to a central '5G' cloud. Below the cloud, there are two 'substation' units. Each substation contains a 'Switch station' and a 'Distributed Terminal'. Each 'Distributed Terminal' is connected to a '5G UE'. The '5G UEs' are interconnected via '5G communication link' (represented by dashed lines) for peer-to-peer data exchange. The '5G' cloud acts as a central hub for the '5G UEs'.
+
+Legend:
+
+- 5G communication link (dashed line)
+- 5G UE (icon)
+
+Diagram of intelligent distributed feeder automation showing a Distributed Master Station connected to a 5G cloud, which is in turn connected to multiple substations. Each substation contains a switch station and a Distributed Terminal connected to a 5G UE. The 5G UEs are interconnected via 5G communication links (dashed lines) for peer-to-peer data exchange.
+
+Figure A.4.4.3-1: Example of intelligent distributed feeder automation
+
+The distribution master station manages multiple distributed terminals. Each distributed terminal is served by a 5G UE to exchange the collected data with other distributed terminals. From an application perspective, the communication between distributed terminals is peer-to-peer. The 5G communication service availability needs to be very high. Therefore, at least two communication links are usually deployed for hot standby or for transmitting data synchronously between two distributed terminals. The associated KPI is provided in Table A.4.4.3-1.
+
+Table A.4.4.3-1: KPI for intelligent distributed feeder automation
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|--------------------------------------|---------------------------------------------|---------------------|--------------------------------------|---------------|----------|------------------------------------------------------------|-------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| 1 | 99.999 | – | Normal: 1 s;
Fault: 2 ms (note 2) | 2 M to 10 M (note 1) | – | Normal: 1 s;
Fault: 2 ms (note 2) | – | – | 54/km 2 (note 3)
78/km 2 (note 4) | several km 2 |
+
+NOTE 1: The KPI values are sourced from [29].
+NOTE 2: It is the one-way delay from a distributed terminal to 5G network.
+NOTE 3: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre.
+NOTE 4: When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals in one square kilometre.
+
+Use cases #1: Intelligent distributed feeder automation
+
+#### A.4.4.4 High-speed current differential protection
+
+High-speed current differential protection, which is required for sub-millisecond fault detection, is another typical use case of power distribution automation. The approach utilises differential current measurements to significantly reduce fault detection time. The protection relays exchange the current samples via the 5G system. Each relay then compares the sent and received samples to determine if a fault has occurred in a protected area. This is done in order to identify and isolate a fault in the grid. The sampling rate varies and is dependent on the algorithms designed by the manufacturers. A protection relay collects the current samples (with the typical message size of up to 245 bytes) at a frequency of 600 Hz, 1200 Hz, 1600 Hz, or 3000 Hz. The exchange of measurement samples is done in a strictly cyclic and deterministic manner. With the sampling rate of 600 Hz, the transfer interval is 1.7 ms and the required bandwidth 1.2 Mbit/s; for 1200 Hz, the transfer interval is 0.83 ms and the required bandwidth 2.4 Mbit/s. The maximum allowed end-to-end delay between two protection relays is between 5 ms and 10 ms, depending on the voltage (see IEC 61850-90-1 for more details [28]). For some legacy systems, the latency usually is set to 15 ms. The associated KPIs are provided in Table A.4.4.4-1.
+
+Table A.4.4.4-1: KPIs for high speed current differential protection
+
+| Use case # | Communication service availability | End-to-end latency: maximum (note) | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | UE density [#/km 2 ] | Service area |
+|------------|------------------------------------|------------------------------------|---------------------------------------------|---------------------|---------------------------------|------------------------------------|------------|---------------------------------|-------------------------|
+| 1 | > 99.999 % | 15 ms | 2.5 Mbit/s | < 245 | ≤ 1 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| 2 | > 99.999 % | 15 ms | 1.2 Mbit/s | < 245 | ≤ 2 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| 3 | > 99.999 % | 10 ms | 2.5 Mbit/s | < 245 | ≤ 1 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| 4 | > 99.999 % | 10 ms | 1.2 Mbit/s | < 245 | ≤ 2 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| 5 | > 99.999 % | 5 ms | 2.5 Mbit/s | < 245 | ≤ 1 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| 6 | > 99.999 % | 5 ms | 1.2 Mbit/s | < 245 | ≤ 2 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+
+NOTE : UE-to-UE communication.
+
+*Use case #1:* High-speed current differential protection with a sampling rate of 1200 Hz for legacy systems.
+
+*Use case #2:* High-speed current differential protection with a sampling rate of 600 Hz for legacy systems.
+
+*Use case #3:* High-speed current differential protection with a sampling rate of 1200 Hz under voltage condition 1 (see IEC 61850-90-1[28] for more details).
+
+*Use case #4:* High-speed current differential protection with a sampling rate of 600 Hz under voltage condition 1 (see IEC 61850-90-1[28] for more details).
+
+*Use case #5:* High-speed current differential protection with a sampling rate of 1200 Hz under voltage condition 2 (see IEC 61850-90-1[28] for more details).
+
+*Use case #6: High-speed current differential protection with a sampling rat*
+
+### A.4.5 Smart grid millisecond-level precise load control
+
+Precise Load Control is the basic application for smart grid. When serious HVDC (high-voltage direct current) transmission fault happens, Millisecond-Level Precise Load Control is used to quickly remove interruptible less-important load, such as electric vehicle charging piles and non-continuous production power supplies in factories.
+
+Table A.4.5-1: Service performance requirements for smart grid millisecond-level precise load control
+
+| Use case # | Characteristic parameter | | | | Influence quantity | | | | | |
+|-----------------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------|---------------------|---------------------------------|---------------|------------|------------------------------------------------|--------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| 1 | 99.999 9 | – | < 50 ms | 0.59 kbit/s
28 kbit/s | < 100 | n/a
(note) | – | stationary | 10 km -2 to
100 km -2 | TBD |
+| NOTE: event-triggered | | | | | | | | | | |
+
+##### *Use case one*
+
+A non-periodic deterministic communication service between control primary station and load control terminals for removing interruptible less-important load quickly.
+
+### A.4.6 Distributed energy storage
+
+Distributed power generation includes various power sources such as solar, wind, fuel cells, and gas. Distributed power generation typically comes with a low power density and entails thus typically a decentralised deployment. Decentralisation causes technical problems and challenges Smart Grid operators. When distributed power generation is connected to the electrical grid, the energy flow becomes more complicated as the user often is both an electricity consumer and producer (a so-called “prosumer”). Therefore, the current in the electricity grid can change direction at different locations of the grid and at different times of the day.
+
+The information exchange in a distributed energy grid does not only include power-generation-related data, but also control commands for the distributed energy storage equipment. An example for such a command is “change the load characteristics to realise a flexible electricity grid” etc.
+
+
+
+The diagram illustrates a distributed-energy storage grid architecture. At the top left, solar panels are connected to a 'Solar monitoring' unit and a 'Solar inverter'. Below them, a 'Wind sensor' and a 'Current meter' are shown. A 'Temp. sensor' is connected to a 'Distributed Energy Device (DED)'. This DED is connected to a 'Local SCADA' system. Another 'DED' is connected to an 'Electric Vehicle Energy monitoring' station, which includes a car and a charging station. A third 'DED' is connected to an 'Energy Storage station monitoring' facility. All three 'DEDs' are connected via a central 'WAN' (Wide Area Network) cloud. The 'WAN' is connected to a 'Distributed Energy Storage Management Platform (DESMP)', which is represented by a cloud icon containing a computer monitor and a map.
+
+Diagram of a distributed-energy storage grid showing various components connected to a central management platform.
+
+**Figure A.4.6-1 Example of a distributed-energy storage grid**
+
+Figure A.4.6-1 shows an example of distributed-energy storage grid. The distributed-energy storage grid needs to exchange information among the distributed-energy storage management platform (DESMP) and distributed-energy devices (DEDs).
+
+The DED is a plug-and-play device and periodically collects its energy information, such as battery energy, charge and discharge status, energy alarm information, etc. The DED then transfers this information via 5G UE to the DESMP. The DESMP regularly manages the DEDs, e.g., the DESMP monitors the DEDs working status, controls the DEDs working modes, or configures the DEDs energy parameters etc. The associated KPIs are provided in Table A.4.6-1.
+
+
+
+Table A.4.6-1: Communication service performance requirements – data for distributed energy storage
+
+| Use case# | Characteristic parameter | | | | Influence quantity | | | | | |
+|-----------|--------------------------------------------------|---------------------------------------------------------------|----------------------------------|--------------------------------------------------------------------------------|----------------------------------|---------------------------------|---------------|------------|-------------------------------------------------------------------------|-------------------------|
+| | Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bit rate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| 1 | > 99.9 % | | DL: < 10 ms
UL: < 10 ms | UL: > 16 Mbit/s (urban);
640 Mbit/s (rural)
DL: > 100 kbit/s (note 1) | UL: 800 kbyte | UL: 10 ms | – | stationary | > 10/km 2 (urban);
> 100/km 2 (rural) (note 2) | several km 2 |
+| 2 | > 99.9 % | | DL: < 10 ms
UL: < 1 s | UL: > 128 kbit/s (urban);
10.4 Mbit/s (rural);
DL: > 100 kbit/s (note 1) | UL: 1.3 Mbyte
DL: > 100 kbyte | UL: 1000 ms | – | stationary | > 10/km 2 (urban);
> 100/km 2 (rural) (note 2) | several km 2 |
+| 3 | > 99.9 % | | DL: < 10 ms
UL: < 1 s (rural) | DL: > 100 kbit/s
UL: > 5 Gbit/s (note 3) | | | | stationary | > 100/km 2 | several km 2 |
+
+NOTE 1: Service bit rate for one energy storage station.
+
+NOTE 2: Activity storage nodes/km2. This value is used for deducing the data volume in an area that features multiple energy storage stations. The data volume can be calculated with the following formula (current service bit rate per storage station) x (activity storage nodes/km2) + (video service bit rate per storage station) x (activity storage nodes/km2).
+
+NOTE 3: The downlink user experienced data rate is calculated as follows: 12.5 Mbytes/s x 50(containers) x 8 = 5 Gbit/s
+
+Use case#1: Distributed energy storage – periodic communication for monitoring
+
+Use case#2: Distributed energy storage – periodic communication for data collection
+
+Use case#3: Distributed energy storage – aperiodic video communication
+
+### A.4.7 Advanced metering
+
+Instead of recording and sending metering data from a wired electricity meter unit, electricity metering collecting can be executed by a UE-integrated smart meter unit. Smart meter units can send real-time metering data to a server in the utility through mobile networks. In this way, the power enterprise—based on the analysis of the user’s power consumption behavior—gives the user power consumption suggestions, which fosters the user’s power consumption and energy saving habits.
+
+The electric smart meters monitor relevant user energy status and deliver the status data to a measurement data management system (MDMS). The MDMS sends control commands according to its policy and the status of the data collected from the smart meters. The MDMS commands include tripping, closing permission, alarm, alarm release, power protection, and power protection release. Accurate-fee control is one of the basic services of advanced metering. When the electric power user doesn’t pay her electric fee on time, the MDMS can cut off the power supply. And when there is a need for temporary power supply for this user, the MDMS can recover the power supply. This operation requires real-time interaction between the electric smart meter and the MDMS. Due to massive number of electricity meters, it is estimated that in the near future, the amount of this kind of interaction will increase 5 to 10 times. The associated KPIs are provided in Table A.4.7-1.
+
+**Table A.4.7-1: Communication KPI for advanced metering**
+
+| Use case# | Characteristic parameter | | | | Influence quantity | | | | | |
+|-----------|--------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------------------------------------|---------------------|---------------------------------|---------------|------------|----------------------------------|--------------|
+| | Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bit rate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| 1 | > 99.99 | | Accuracy fee control: < 100 (note 1);
General information data collection: < 3000 | UL: < 2 M
DL: < 1 M | – | – | – | stationary | < 10 000/km 2 (note2) | – |
+
+NOTE 1: One-way delay from 5G IoT device to backend system. The distance between the two is below 40 km (city range).
+NOTE 2: It is the typical connection density in today city environment. With the evolution from centralised meters to socket meters in the home, the connection density is expected to increase 5 to 10 times.
+
+Use case#1: Advanced metering
+
+### A.4.8 Smart distribution transformer terminal
+
+A smart distribution transformer terminal is usually deployed in a distribution transformer area. The terminal can support multiple energy applications simultaneously. Multiple kinds of energy data are collected by the terminal and then delivered to a energy application platform. Figure A.4.8.1-1 illustrates a workflow example for a smart distribution transformer terminal.
+
+
+
+The diagram illustrates the workflow of a smart distribution transformer terminal. At the top, a box contains three components: 'Connection Management Platform', 'Distribution Master Station', and 'Electric Energy Data Acquire System Master Station', followed by an ellipsis. To the right of this box is a blue arrow pointing left from a box labeled 'Energy application platform'. Below this top box is a large box divided into two channels. 'Channel 1: Broad bandwidth' on the left lists: 'Electrical analog data, Meter reading data, Topology relationship, Decision-making information, Edge computing conclusion, Equipment OA&M data, Parameter tune, Remote upgrading, Scheduled communication...'. 'Channel 2: Low latency, high stability' on the right lists: 'Fault / Alarming events, Switch state variation, Device abnormal changes, Remote control operation ...'. Between these two channels are two vertical double-headed arrows labeled 'Channel 1' and 'Channel 2'. Below the channels is a box labeled 'Smart Distribution Transformer Terminal'. Below this terminal box are six boxes representing energy end equipment: 'Smart meter', 'Power consumption concentrator', 'Cable head temperature sensor', 'Charging pile', 'Smoke detector', and 'Smart RCD'. Each of these boxes has a double-headed arrow connecting it to the terminal box. To the right of these equipment boxes is a blue arrow pointing left from a box labeled 'Energy end equipment'.
+
+Diagram of a smart distribution transformer terminal workflow showing data flow from energy end equipment through the terminal to an energy application platform via two channels.
+
+Figure A.4.8-1: Example of a smart distribution transformer terminal workflow
+
+In general, the connections between the smart distribution transformer terminal and the energy application platform are provided by the 5G system. The connections between energy end equipment and smart distribution transformer terminal may be provided by 5G system. In this case, about 300 to 500 energy end devices are connected to one smart distribution transformer terminal. The average service bit rate between the smart distribution transformer terminal and an energy end device is more than 2 Mbit/s in uplink for each application. The related communication distance is between 100 m and 500 m. The associated KPI is provided in Table A.4.8-1.
+
+Table A.4.8-1: Key Performance for Smart Distribution Transformer Terminal
+
+| Use case# | Characteristic parameter | | | | Influence quantity | | | | | |
+|-----------|--------------------------------------------------|---------------------------------------------------------------|-----------------------------|----------------------------------------------|---------------------|---------------------------------|---------------|----------|----------------------------------|-----------------------------------------------------------------------------------|
+| | Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bit rate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| 1 | >99.99% | – | 10 ms, 100 ms, 3 s (note 2) | > 2 Mbit/s (note 1) | – | – | – | – | 500 in the service area (note 3) | Communication distance is from 100 m to 500 m, (outdoor, indoor, and deep indoor) |
+
+NOTE 1: It is the smart metering application data rate between the Smart Distribution Transformer Terminal and energy end equipment. Once there are multiple smart grid applications, it is required more data rate.
+
+NOTE 2: It depends on different applications supported by the Smart Distribution Transformer Terminal. The less the latency is, the more applications can be supported.
+
+NOTE 3: The distribution area can be calculated as $3.14 \times \text{range}^2$ and in general is between 0.031 km2 and 0.79 km2.
+
+Use case#1: smart distribution transformer terminal
+
+### A.4.9 Distributed energy resources and micro-grids
+
+Distributed energy resources (DER) become increasingly important. The potentially large number of DERs will have an impact on security, stability, and operation efficiency of the energy grid.
+
+The integration of DERs into the energy grid poses many challenges for the involved communication system. To incorporate more renewable and alternative energy sources, the communication infrastructure must have the ability to easily handle an increasing amount of data traffic or service requests and must provide a real-time monitoring and control operation for these distributed energy resources. A reliable communication between the DERs is crucial.
+
+When it comes to communications architecture, IEC 61850 is a widely used standard for automation and equipment of power utilities and DER, specifically for defining protocols for IEDs (Intelligent electronic devices) at electrical substations. The IEC 61850 standard specifies the timing constraints for messages typically used in substations. GOOSE (Generic Object Oriented Substation Events) and SV (Sampled Values) messages are assumed as time critical messages. They have the tightest deadlines (maximum allowed transfer time) among all IEC 61850 messages, corresponding to 3 ms. While GOOSE is typically used for transferring information related to monitoring and control functions (circuit breaker status etc.), SV is used for transferring measurement samples of current and voltage signals. The SV protocol works on a periodic information transmission model, sending messages at a fixed rate. For protection purposes, the default rate is 4000 or 4800 messages per second for 50 and 60 Hz power systems, respectively. On the other hand, the GOOSE protocol operates in a sporadic information transmission model, where a continuous flow of data is maintained to increase communication reliability. The typical
+
+sizes of GOOSE and SV messages are 160 and 140 bytes, respectively. GOOSE messages are transmitted in two different modes: (1) safe operation: 1 message per second (service bit rate = 1.28 kbit/s); (2) emergency operation: 32 messages per second (service bit rate = 41.0 kbit/s). SV messages are transmitted at much higher rate, namely 4800 messages per second (service bit rate = 5.4 Mbit/s). The associated KPIs are provided in Table A.4.9-1.
+
+**Table A.4.9-1: Key Performance for Distributed energy resources (DER): using SV (Sampled Values) message**
+
+| Use case# | Characteristic parameter | | | | Influence quantity | | | |
+|------------------------------------------|--------------------------------------------------|---------------------------------------------------------------|-----------------------------|----------------------------------------------|---------------------|---------------------------------|-------------------|------------|
+| | Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bit rate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed |
+| 1 | 99,9999 % | – | < 3 ms | 4.5 Mbit/s | 140 | ≤ 1 ms | transfer interval | stationary |
+| 2 | 99,9999 % | – | < 3 ms | 5.4 Mbit/s | 140 | ≤ 1 ms | transfer interval | stationary |
+| 3 | > 99,9999 % | – | < 3 ms | – | 160 | – | – | stationary |
+| NOTE: UE to UE communication is assumed. | | | | | | | | |
+
+*Use case#1:* Distributed energy resources and micro-grids: using SV(sample value) message with 50Hz
+
+*Use case#2:* Distributed energy resources and micro-grids: using SV(sample value) message with 60Hz
+
+*Use case#3:* Distributed energy resources and micro-grids: using GOOSE message
+
+### A.4.10 Ensuring uninterrupted communication service availability during emergencies
+
+During emergencies, public mobile land networks (PLMNs) may restrict network access, which may lead to a prohibitively low communication service availability for machine-type communication (MTC) for Smart Grid applications. An example is communication for microgrids. Microgrids are separate parts of a power grid that can be controlled and operated individually in a so-called island mode, or together with other parts of the power grid. The idea is to prioritise Smart Grid-related communication in order to ensure reliable and available communication for selected devices during emergency conditions. Existing features of a mobile network can be used to differentiate MTC of devices in a microgrid from other kind of MTC traffic or human-to-human communication. These features can help these microgrid devices to have communication service during emergencies. The communication among the microgrid devices enables co-ordination of DERs, which help the DERs can autarkically implement recovery of an islanded microgrid.
+
+The associated KPI is provided in Table A.4.10-1.
+
+**Table A.4.10-1: Key Performance for uninterrupted MTC service availability**
+
+| Characteristic parameter (KPI) | | | | Influence quantity | | | | |
+|--------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------|-------------------------------------------------------|---------------------|---------------|------------|----------|--------------|
+| Communication service availability: target value | Communication service reliability: mean time between failures | Max Allowed End-to-end latency (note 1; (note 2)) | Service bit rate: user-experienced data rate (note 2) | Message size [byte] | Survival time | UE speed | # of UEs | Service Area |
+| 99.999 9 % | – | 100 ms | < 1 kbit/s per DER | – | – | Stationary | – | – |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+NOTE 2: It applies to both UL and DL unless stated otherwise.
+
+## A.5 Central power generation
+
+### A.5.1 Overview
+
+This domain comprises all aspects of centralised power generation, i.e. the centralised conversion of chemical energy and other forms of energy into electrical energy. Typical electric-power outputs are 100 MW and more. Examples for pertinent systems are large gas turbines, steam turbines, combined-cycle power plants, and wind farms. The planning and installation of respective equipment and plants as well as the operation, monitoring and maintenance of these plants is encompassed by this vertical domain.
+
+### A.5.2 Wind power plant network
+
+**Table A.5.2-1: Service performance requirements for wind power plant network**
+
+| Use case # | Characteristic parameter | | | | Influence quantity | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|--------------------|--------------------|-------------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Packet error ratio | UE speed | Service area |
+| 1 | 99.999 999 9 | ~ 10 years | 16 ms | < 10 -9 | stationary | several km 2 |
+
+*Use case one*
+
+Communication in support of closed-loop cyber-physical control in a wind farm. The wind farm can be deployed offshore.
+
+NOTE: This type of communication service can be provided via a wired connection.
+
+## A.6 Connected hospitals or medical facilities
+
+### A.6.1 Overview
+
+The traditional value chain for the medical device industry, which historically has been driven by innovation and research and development, is currently witnessing a shift in the landscape. As governments and health insurers worldwide implement measures to control costs, public hospitals are operating on tighter budgets, while private facilities are receiving lower reimbursements. In the developed world, decisions that used to be the sole preserve of doctors are now also made by regulators, hospital administrators, and other non-clinicians. This broader set of influencers comes with different objectives, e.g. the prioritization of cost effectiveness or even just costs.
+
+This shift in focus from volume-based healthcare to value-based healthcare has led medical devices companies to move to business models based on providing clinical value with cost efficiency.
+
+Technological progress and better infrastructures, in particular high-quality wireless networks, have fed this business model transformation, allowing coordinated therapies, services, and health analytics and enabling efficient outcome measurement solutions.
+
+On this matter, 5G enables shifting care location from hospitals to homes and others lower cost facilities which mechanically translates into more savings. Additionally, another example showing that 5G can enable cost savings required by the medical industry can be found inside hospitals where wireless transmission of low latency data streams improves operating room planning, enable streamlining equipment usage and simplifies operating theater implementation.
+
+### A.6.2 Robotic Aided Surgery
+
+Robotic aided surgery is particularly suitable to invasive surgical procedures that require delicate tissue manipulation and access to areas with difficult exposure. It is achieved through complex systems that translate the surgeon's hand movements into smaller, precise movements of tiny instruments that can generally bend and rotate far more than a human hand is capable of doing inside the patient's body. In addition, those systems are usually able to filter out hand tremor and therefore allow more consistent outcomes for existing procedures, and more importantly the development of new procedures currently made impractical by the accuracy limits of unaided manipulation.
+
+A typical robotic setup for telesurgery can be depicted as follows.
+
+
+
+```
+graph LR; SC[Surgeon Console] -- 5G --> MA[Medical Application]; MA -- 5G --> R[Robot]; R --> T[Trocars]; R --> E[Endoscope];
+```
+
+Diagram of a typical robotic surgery system setup showing the flow from Surgeon Console to Medical Application to Robot to Trocars and Endoscope, with 5G communication links.
+
+Figure A.6.2-1: Typical Robotic Surgery System Setup
+
+The robot and the surgeon's console can be co-located in the same operating room in which case they communicate through a NPN, or, in another deployment option, when specialists and patients are far from each other (hundreds of kilometres) they can exchange data through communication services delivered by PLMNs. The depicted medical application can be instantiated at either side or in the Cloud. Its role consists in:
+
+- Generating appropriate haptic feedback based on instrument location, velocity, effort measurements data and images issued by surgical instruments and 3D pre-operative patient body model. This allows to provide tactile guidance by constraining where the instruments (scalpel, etc.) can go.
+- Filtering motion control commands for better closed loop stability
+
+Typical surgery robotic systems can have around 40 actuators and the same number of sensors which allows to compute the data rate requires in each direction in order to execute a given movement.
+
+Human sensitivity of touch is very high, tactile sensing has about 400 Hz bandwidth, where bandwidth refers to the frequency of which the stimuli can be sensed. This is why, in general, haptic feedback systems operate at frequencies around 1,000 Hz. This rate naturally applies to the update of all information used in the generation of the haptic feedback, e.g. instruments velocity, position ... Therefore, the robot control process involves:
+
+- The surgeon console periodically sending a set of points to actuators
+- Actuators executing a given process
+- Sensors sampling velocity, forces, positions, ... at the very same time and returning that information to the surgeon console at the rate of 1 kHz
+
+As opposed to machine to machine communication, robotic aided surgery implies there is a human being in the middle of the control loop, which means that the console generates new commands based on the system state collected in the previous 1 kHz cycle and also on surgeon's hand movement.
+
+Each equipment involved in a robotic telesurgery setup (endoscopes, image processing system, displays, motion controller and haptic feedback systems) is synchronized thanks to a common clock either external or provided by the 5G system. The synchronization is often achieved through dedicated protocols such as e.g. PTP version 2 and allows to e.g. guarantee the consistency of the haptic feedback and displayed images at the master console, or enable the recording and offline replay of the whole procedure.
+
+**Table A.6.2-1: Service performance requirements for motion control and haptic feedback**
+
+| Use case # | Characteristic parameter | | | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|--------------------------------------------------------------|-----------------------------|-----------------------|------------------------------|---------------------|-------------------|-------------------|------------|-------------------------------|--------------|
+| | Communication service availability: target value [%] | Communication service reliability: Mean Time Between Failure | End-to-end latency: maximum | Bit rate | Direction | Message Size [byte] | Transfer Interval | Survival time | UE speed | # of active UEs (note1) | Service Area |
+| 1 | > 99.999 999 | > 10 years | < 2 ms | 2 Mbit/s to 16 Mbit/s | network to UE; UE to network | 250 to 2,000 | 1 ms | transfer interval | stationary | 1 | room |
+| 2 | > 99.999 9 | > 1 year | < 20 ms | 2 Mbit/s to 16 Mbit/s | network to UE; UE to network | 250 to 2,000 | 1 ms | transfer interval | stationary | < 2 per 1,000 km 2 | national |
+
+Note 1: The upper limit of UEs' density is provided for large service areas to address non-uniform distributions of UEs, while an absolute number of UEs is provided for small service areas.
+
+#### *Use case one*
+
+Periodic communication for the support of precise cooperative robotic motion control and haptic feedback in case of robotic aided surgery where the surgeon console and the robot are collocated in the same operating room
+
+#### *Use case two*
+
+Periodic communication for the support of cooperative robotic motion control and haptic feedback in case of telesurgery. In this case, the surgeon console and the robot are not collocated and communicate with each other through a connection established over a PLMN possibly spanning an entire country. Relaxed requirements imply that much less complex surgical procedures are achievable in use case 2 than in use case 1. It shall be noted that this use case also involves more experienced and trained surgeons, who can cope with longer latencies in the communication system.
+
+### A.6.3 Robotic Aided Diagnosis
+
+Robotic aided diagnosis involves a remote expert in a large central hospital who controls a diagnosis robotic system deployed in a local medical facility. Such robotic systems can be e.g.:
+
+- Haptic feedback tool used for palpating and deployed in e.g. a Mobile Specialist Practise facility
+- Ultrasound probe deployed in an ambulance or a medical facility
+
+A typical robotic setup for tele diagnosis can be depicted as follows:
+
+
+
+```
+graph LR; EC[Expert Console] <-->|5G| MA[Medical Application]; MA <-->|5G| R[Robot]; R --- S[Scopes]; R --- Sen[Sensors];
+```
+
+The diagram illustrates a typical robotic surgery system setup. It consists of four main components connected in a linear sequence from left to right: an 'Expert Console', a 'Medical Application', a 'Robot', and a pair of 'Scopes' and 'Sensors'. The 'Expert Console' and 'Medical Application' are connected via a bidirectional communication link labeled '5G'. The 'Medical Application' and 'Robot' are also connected via a bidirectional communication link labeled '5G'. The 'Robot' is connected to the 'Scopes' and 'Sensors' via a single line, indicating that the robot is equipped with these instruments.
+
+Diagram of a typical robotic surgery system setup showing the flow from Expert Console to Medical Application to Robot, which is connected to Scopes and Sensors.
+
+**Figure A.6.3-1: Typical Robotic Surgery System Setup**
+
+Specialists and patients are far from each other (typically dozens of kilometres) and can exchange data through communication services delivered by PLMNs. The depicted medical application can be instantiated at either side or in the Cloud. Its role consists in:
+
+- Generating appropriate haptic feedback based on instrument location, velocity, effort measurements data and images issued by instruments.
+- Filtering motion control commands for better closed loop stability
+
+**Table A.6.3-1: Service performance requirements for motion control and haptic feedback**
+
+| Use case # | Characteristic parameter | | | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|--------------------------------------------------------------|-----------------------------|-----------------------|------------------------------|---------------------|---------------------------------|-------------------|------------|------------------------------|--------------|
+| | Communication service availability: target value [%] | Communication service reliability: Mean Time Between Failure | End-to-end latency: maximum | Bit rate | Direction | Message Size [byte] | Transfer Interval | Survival time | UE speed | # of active UEs | Service Area |
+| 1 | > 99.999 | >> 1 month (< 1 year) | < 20 ms | 2 Mbit/s to 16 Mbit/s | network to UE; UE to network | ~80 | < 20 ms per 100 km 2 | transfer interval | stationary | < 20 per 100 km 2 | regional |
+
+#### *Use case one*
+
+Periodic communication for the support of precise cooperative robotic motion control and haptic feedback in case of robotic aided diagnosis where the expert and the patient are not collocated and communicate with each other through a connection established over a PLMN.
+
+## A.7 Positioning
+
+### A.7.1 Overview of positioning in industrial use cases
+
+Positioning is particularly important for cyber-physical control applications in vertical domains like factories. The reason for this is that mobile devices and mobile assets are becoming increasingly common in the flexible production and subsequently the need for real-time locations data is increasing.
+
+In this context, positioning is especially important for warehousing and logistics processes, autonomous driving systems and fleet management and flexible adaptation in production. In the best case all relevant goods and products are continuously tracked from the moment they are received to the moment they are made available. The tracking process provides the relevant context information that is needed for real-time control and optimization of the material flow and subsequent production processes. In this scenario, autonomous driving systems fetch parts from the warehouse independently and transport them to flexible assembly cells on the shop floor. As part of the flexible fleet management system, these autonomous driving systems are continuously localized and move quickly and in constant interaction with their environment. In the process, production machinery and assembly cells and their given status are monitored seamlessly while relevant objects like tools and workpieces being localized. This makes it possible to adapt quickly to changes in circumstances. The result is flexible, autonomously controlled production that is capable of adapting to new situations at any time. Wireless positioning for human machine interfaces like AR/VR should also be possible.
+
+The requirements for positioning vary widely between different use cases.
+
+### A.7.2 Low Power High Accuracy Positioning
+
+Low power high accuracy positioning is an integral part of a considerable number of industrial applications. The total energy needed for a specific operation time for such a low power high accuracy positioning optimized IoT-device is a combination of energy for positioning (varies depending on the used positioning method), energy for communication/synchronization and a difficult to predict factor to take additional losses through e.g. security, power management, microcontroller, and self-discharge of batteries into account.
+
+Examples of target applications for low power high accuracy positioning are asset tracking in process automation, tracking of vehicles, and tool tracking.
+
+Table A.7.2-1 gives an indication of the required operation time of the 5G enabled IoT device and duty cycle of the updated position information for different use cases.
+
+**Table A.7.2-1: Low power high accuracy positioning use cases**
+
+| Use Case # | Horizontal accuracy | Corresponding service level (22.261) | Positioning interval/ duty cycle | battery life time/ minimum operation time |
+|------------|---------------------|--------------------------------------|----------------------------------|-----------------------------------------------------------------------|
+| 1 | 10 m | Service Level 1 | on request | 24 months |
+| 2 | 2 m to 3 m | Service Level 2 | < 4 seconds | > 6 months |
+| 3 | < 1 m | Service Level 3 | no indication | 1 work shift - 8 hours (up to 3 days, 1 month for inventory purposes) |
+| 4 | < 1 m | Service Level 3 | 1 second | 6 - 8 years |
+| 5 | < 1 m | Service Level 3 | 5 seconds - 15 minutes | 18 months |
+| 6 | < 1 m | Service Level 3 | 15 s to 30 s | 6 - 12 months |
+| 7 | 30 cm | Service Level 5 | 250 ms | 18 months |
+| 8 | 30 cm | Service Level 5 | 1 second | 6 - 8 years (no strong limitation in battery size) |
+| 9 | 10 m | Service Level 1 | 20 minutes | 12 years (@20mJ/position fix) |
+
+#### *Use case one*
+
+Process automation: Dolly tracking (outdoor).
+
+#### *Use case two*
+
+Process automation: Asset tracking.
+
+#### *Use case three*
+
+Flexible modular assembly area: Tool tracking in flexible, modular assembly areas in smart factories.
+
+#### *Use case four*
+
+Process automation: Sequence container (Intralogistics).
+
+#### *Use case five*
+
+Process automation: Palette tracking (e.g. in turbine construction).
+
+#### *Use case six*
+
+Flexible modular assembly area: Tracking of workpiece (in- and outdoor) in assembly area and warehouse.
+
+#### *Use case seven*
+
+Flexible modular assembly area: Tool assignment (assign tool to vehicles in a production line, left/right) in flexible, modular assembly area in smart factories.
+
+#### *Use case eight*
+
+Flexible modular assembly area: Positioning of autonomous vehicles for monitoring purposes (vehicles in line, distance 1.5 meter).
+
+#### *Use case nine*
+
+(Intra-)logistics: Asset tracking
+
+
+
+# --- Annex B (informative): Communication service errors
+
+## B.1 Introduction
+
+IEC 61784-3-3 describes fundamental communication errors that can be identified for applications with functional safety requirements [3]. The description of these communication errors is adjusted to field buses. These errors may however also occur in other communication systems. As explained in Annex C, some of these errors are also used for the assessment of communication services that do not support safety-critical applications.
+
+## --- B.2 Corruption
+
+Messages may be corrupted due to errors within an application, due to errors on the transmission medium, or due to message interference.
+
+- NOTE 1: Message error during transfer is a normal event for any standard communication system; such events are detected with high probability at receivers by use of, for instance, hash functions.
+- NOTE 2: Most communication systems include protocols for recovery from transmission errors, so these messages will not be classed as 'loss' until recovery or repetition procedures have failed or are not used.
+- NOTE 3: If the recovery or repetition procedures take longer than a specified deadline, a message is classed as "unacceptable delay". See also the discussion in Clause C.3.
+- NOTE 4: In the very low probability event that multiple errors result in a new message with correct message structure (for example addressing, length, hash function such as CRC, etc.), the message will be accepted and processed further. Evaluations based on a message sequence number or a time stamp can result in fault classifications such as unintended repetition, incorrect sequence, unacceptable delay, insertion [3].
+
+## --- B.3 Unintended repetition
+
+Due to an error, fault, or interference, not updated messages are accidentally repeated.
+
+- NOTE 1: Repetition by the sender is a common procedure when an expected acknowledgment/response is not received from a target station, or when a receiver detects a missing message and asks for it to be resent.
+
+In some cases, the lack of response can be detected, and the message repeated with minimal delay and no loss of sequence, in other cases the repetition occurs later and arrives out of sequence with other messages.
+
+- NOTE 2: Some field buses use redundancy to send the same message multiple times or via multiple alternate routes to increase the probability of good reception [3].
+
+## --- B.4 Incorrect sequence
+
+Due to an error, fault, or interference, the predefined sequence (for example natural numbers, time references) associated with messages from a source is incorrect.
+
+- NOTE 1: Field bus systems can contain elements that store messages (for example FIFOs in switches, bridges, routers) or use protocols that can alter the sequence (for example, by allowing messages with high priority to overtake those with lower priority).
+- NOTE 2: When multiple sequences are active, such as transmission of messages from different source entities or reports relating to different object types, these sequences are monitored separately, and errors can be reported for each sequence [3].
+
+## --- B.5 Loss
+
+Due to an error, fault or interference, a message or acknowledgment is not received [3].
+
+## --- B.6 Unacceptable deviation from target end-to-end latency
+
+Messages may be delayed or advanced beyond their permitted arrival time window. Causes for this behaviour include errors in the transmission medium, congested transmission lines, interference, and applications sending messages in such a manner that communication services are delayed or denied.
+
+Message errors can be recovered in the following ways using scheduled or cyclic scans, for instance, in field buses:
+
+- a) immediate repetition;
+- b) repetition using spare time at the end of the cycle;
+- c) treating the message as lost and waiting for the next cycle to receive the next value.
+
+In case of (a), all subsequent messages in that cycle are slightly delayed, while in case (b) only the resent message is delayed.
+
+Cases (a) and (b) are often not classed as an unacceptable deviation from the target end-to-end latency.
+
+Case (c) would be classed as an unacceptable delay for cyclic, distributed automation functions, unless the cycle repetition interval is short enough to ensure that delays between cycles are not significant and that the next cyclic value can be accepted as a replacement for the missed previous value before the survival time expires (see Clause C.3) [3].
+
+## --- B.7 Masquerade
+
+Due to a fault or interference, a message is inserted that relates to an apparently valid source entity, so a non-safety related message may be received by a safety-related participant, which then treats it as safety related.
+
+NOTE: Communication systems used for safety-related applications can use additional checks to detect masquerade, such as authorised source identities and pass-phrases or cryptography [3].
+
+## --- B.8 Insertion
+
+Due to a fault or interference, a message is received that relates to an unexpected or unknown source entity.
+
+NOTE: These messages are additional to the expected message stream, and because they do not have expected sources, they cannot be classified as correct, unintended repetition, or incorrect sequence [3].
+
+## --- B.9 Addressing
+
+Due to a fault or interference, a safety-related message is delivered to the incorrect safety related participant, which then treats reception as correct [3].
+
+# Annex C (informative): Characterising communication services
+
+## C.1 Modelling of communication in automation
+
+### C.1.1 Area of consideration
+
+For our discussion of communication in automation we apply a definition of the area of consideration for industrial radio communication that is found elsewhere in the literature [4]. This definition is illustrated in Figure C.1.1-1.
+
+
+
+Abstract diagram of the area of consideration for industrial radio communication. The diagram shows a 'Distributed automation application' cloud at the top containing several 'Distributed automation function' blocks. Below this cloud is a 'Communication medium' cloud. Between the application functions and the communication medium are 'Communication function' blocks, which are highlighted in blue. Vertical double-headed arrows connect each 'Distributed automation function' block to its corresponding 'Communication function' block, and each 'Communication function' block to the 'Communication medium'. A red line labeled 'Reference interface' points to the boundary between a 'Distributed automation function' and its 'Communication function'. Another red line labeled 'Communication requirements and conditions' points to the boundary between the 'Communication function' and the 'Communication medium'.
+
+NOTE: Blue objects: communication system; other objects: automation application system.
+
+**Figure C.1.1-1: Abstract diagram of the area of consideration for industrial radio communication**
+
+Here, a distributed automation application system is depicted. This system includes a distributed automation application, which is the aggregation of several automation functions. These can be functions in sensors, measurement devices, drives, switches, I/O devices, encoders etc. All of these functions contribute toward the control of physical objects. Field bus systems, industrial Ethernet systems, or wireless communication systems can be used for connecting the distributed functions. The essential function of these communication systems is the distribution of messages among the distributed automation functions. For cyber-physical control applications, the dependability of the entire communication system and/or of its devices or its links is essential. Communication functions are realised by the respective hardware and software implementation.
+
+In order for the automation application system to operate, messages need to be exchanged between spatially distributed application functions. For that process, messages are exchanged at an interface between the automation application system and the communication system. This interface is termed the reference interface. Required and guaranteed values for characteristic parameters, which describe the behavioural properties of the radio communication system, as well as some influence quantities refer to that interface.
+
+The conditions that influence the behaviour of wireless communication are framed by the communication requirements of the application (e.g., end-to-end latency), the characteristics of the communication system (e.g., output power of a transmitter), and the transmission conditions of the media (e.g., signal fluctuations caused by multipath propagation).
+
+General requirements from the application point of view for the time and failure behaviour of a communication system are mostly related to an end-to-end link. It is assumed in the present document that the behaviour of the link is representative of the communication system as a whole and of the entire scope of the application.
+
+### C.1.2 Logical link
+
+#### C.1.2.1 Nature and function
+
+Starting with the general approach mentioned in Subclause C.1.1, the logical link can be regarded as a possible asset within the area of consideration (see Figure C.1.1-1). The conditions under which its functions are to be performed are vital for the dependability of the automation application system.
+
+
+
+Figure C.1.2.1-1: The concept of a logical link. This diagram illustrates the concept of a logical link in a distributed automation system. At the top, a cloud represents the 'Distributed automation Application'. Below it, four 'Distributed Automation Component' blocks are shown. Each block has a 'Wireless Communication Component' at its base. A red line labeled 'Logical link' connects two 'Logical endpoints' (marked with red dots) within the communication components of two different automation components. These endpoints are part of the 'Reference interface'. The components are connected to a 'Wireless Communication Medium' (represented by a blue cloud at the bottom) via vertical arrows.
+
+**Figure C.1.2.1-1: The concept of a logical link**
+
+This is the link between a logical end point in a source device and the logical end point in a target device. Logical end points are elements of the reference interface, which may group several logical end points together.
+
+The intended function of the logical link is the transmission of a sequence of messages from a logical source end point to the correct logical target end point. This is achieved by transforming each message into a form that fosters error-free transmission. The transmission process includes certain processes, for instance repetitions, in order to fulfil the intended function. After transmission, the transported package(s) is converted back into a message. The message is to be available and correct at the target within a defined time. The sequence of messages at the target is to be the same as the sequence at the source.
+
+The functional units, which are necessary to fulfil this function are shown, in Figure C.1.2.1-1.
+
+
+
+HCL: Higher Communication Layer
+LCL: Lower Communication Layer
+
+Figure C.1.2.1-2: The asset 'logical link'. This diagram shows the functional units of a logical link between a 'Source' and a 'Target'. On the Source side, a 'Reference interface' box contains an 'application function' and a 'Logical endpoint'. This is connected to a 'Communication function' box containing 'HCL' (Higher Communication Layer) and 'LCL' (Lower Communication Layer) blocks. On the Target side, the structure is mirrored. Between the Source's Communication function and the Target's Communication function is a 'Physical link' (Transmission medium). The 'Logical link' is indicated by a bracket spanning from the Source's Logical endpoint to the Target's Logical endpoint, encompassing the HCL, LCL, and Transmission medium components.
+
+**Figure C.1.2.1-2: The asset "logical link"**
+
+The required function can be impaired by various influences, which can lead to communication errors. Such errors are described elsewhere in the literature [4][5]. A summary of these errors is provided in Annex A. The occurrence of one of these errors influences the values of the relevant dependability parameters of the logical link.
+
+#### C.1.2.2 Message transformation
+
+The present document addresses both OSI-layer-3 (IP) and OSI-layer-2 communication. The model in Figure C.1.2-1 can be used for describing both cases. The implementation of communication functions is split between a higher communication layer (HCL) and a lower communication layer (LCL). The partition of the layer for the two traffic options discussed in the present document is provided in Table C.1.2.2-1. This difference is of importance when discussing the implications of the service performance requirements in Clause 5 and Annex A for the network performance (see Clause C.5).
+
+**Table C.1.2.2-1: Partition into higher communication layer and lower communication layer**
+
+| OSI level at which the traffic occurs | Levels comprised by the higher communication layer | Levels comprised by the lower communication layer |
+|---------------------------------------|----------------------------------------------------|---------------------------------------------------|
+| 3 | 4 to 6 | 1 to 3 |
+| 2 | 3 to 6 (note) | 1 to 2 |
+
+NOTE: In some vertical application, level 3 to 6 are not implemented.
+
+The messages to be transmitted for the intended function of a logical link are defined by strings of characters with a certain semantic. Such a character string is handed over as user data at the reference interface for transmission. If the number of characters in a message is too great for it to be transmitted as a unit, the message is divided for transmission into several packets (fragmentation).
+
+#### C.1.2.3 Communication device
+
+The communication devices—together with the physical link—determine the function and thus the dependability of the logical link. The function of the communication devices is the correct sending and correct receipt of sequences of messages. The asset "communication device" is depicted in Figure C.1.2.3-1.
+
+
+
+The diagram illustrates the architecture of a communication device. On the left, a 'Communication device - Source' is shown as a red-bordered box containing two internal components: 'HCL' (Higher Communication Layer) and 'LCL' (Lower Communication Layer). A 'Logical Endpoint' and 'Reference interface' are located at the left boundary of this box. On the right, a 'Communication device - Target' is shown similarly, with 'HCL' and 'LCL' components, and its own 'Logical Endpoint' and 'Reference interface' at the right boundary. Between the two devices is a 'Physical link' (indicated by a bracket above) which contains a 'Transmission distance' block. A 'Logical link' (indicated by a bracket below) spans between the two reference interfaces, passing through the 'LCL' and 'HCL' components of both devices.
+
+Diagram of the communication device asset showing two communication devices (Source and Target) connected by a physical link. Each device contains HCL and LCL layers. The logical link is shown between the reference interfaces of the two devices.
+
+HCL: Higher Communication Layer
+LCL: Lower Communication Layer
+
+**Figure C.1.2.3-1: Asset "communication device"**
+
+#### C.1.2.4 Communication system
+
+The communication system as an asset represents a quantity of logical links whose message transmissions are implemented by wireless devices via one or more media. The communication system function to be provided consists in transmitting messages for all the logical links in the distributed application. This function is to be performed for a defined period, the operating time of the automation application.
+
+In an automation application system, it is paramount that requirements pertaining to logical links are fulfilled. These requirements and the conditions can be very different from one case and implementation to the other. The functions (services and protocols) for individual logical links can therefore also be different. Despite these differences, some of the logical links share communication devices and media.
+
+## C.2 Communication service description
+
+### C.2.1 Overview
+
+Tables C.2.2-1, C.2.3-1 summarise candidate interface parameters for the description of the communication service performance. The lists are grouped according to whether the parameter stands for automation characteristic parameters (Table C.2.2-1) or influence quantities (Table C.2.3-1). The meaning of the columns and rows is explained after each table.
+
+NOTE 1: Not all parameters in Table C.2.2-1 and Table C.2.3-1 would be used in a service call.
+
+NOTE 2: Ingress and egress in this clause are in reference to the communication service interface between the source application and the communication service interface (ingress) and the communication service and the target application (egress).
+
+### C.2.2 Characteristic parameters
+
+**Table C.2.2-1: Candidate characteristic parameters for the dependable communication service interface**
+
+| Parameter name | Typical metric (unit) | Traffic class (note) | | |
+|------------------------------------|---------------------------------------------------------------------------|--------------------------------------|---------------------------------------|---------------------------------|
+| | | Deterministic periodic communication | Deterministic aperiodic communication | Non-deterministic communication |
+| Communication service availability | Minimum availability (dimensionless) | X | X | X |
+| End-to-end latency | Target value and timeliness (ms) | X | X | X |
+| Communication service reliability | Mean time between failures (days) | X | X | X |
+| Service bit rate | Target value (bit/s); user experienced data rate (bit/s); time window (s) | – | X | X |
+| Update time | Target value and timeliness | X | – | – |
+
+NOTE: – application requirements (KPIs). X: applies; –: does not apply.
+
+#### Parameter description
+
+#### *Communication service availability*
+
+This parameter indicates if the communication system works as contracted ("available"/"unavailable" state). The communication system is in the "available" state as long as the availability criteria for transmitted packets are met. The service is unavailable if the packets received at the target are impaired and/or untimely (e.g. update time > stipulated maximum). If the survival time (see Table C.2.3-1) is larger than zero, consecutive impairments and/or delays are ignored until the respective time has expired.
+
+#### *End-to-end latency*
+
+This parameter indicates the time allotted to the communication system for transmitting a message and the permitted timeliness.
+
+#### *Communication service reliability*
+
+Mean time between failures is one of the typical indicators for communication service reliability. This parameter states the mean value of how long the communication service is available before it becomes unavailable. For instance, a mean time between failures of one month indicates that a communication service runs error-free for one month on average before an error/errors make the communication service unavailable. Usually, an exponential distribution is assumed. This means, there will be several failures where the time between two subsequent errors is below the mean value (1 month in the example).
+
+Communication service availability and communication service reliability (mean time between failures) give an indication on the time between failures and the length of the failures.
+
+#### *Service bit rate*
+
+##### *a) deterministic communication*
+
+The target value indicates committed data rate in bit/s sought from the communication service. This is the minimum data rate the communication system guarantees to provide at any time, i.e. in this case target value = user experienced data rate.
+
+##### *b) non-deterministic communication*
+
+The target value indicates the target data rate in bit/s. This is the information rate the communication system aims at providing on average during a given (moving) time window (unit: s). The user experienced data rate the lower data rate threshold for any of the time windows.
+
+#### *Update time*
+
+Applicable only to periodic communication, the update time indicates the time interval between any two consecutive messages delivered from the egress (of the communication system) to the application.
+
+#### **Traffic classes**
+
+In practice, vertical communication networks serve applications exhibiting a wide range of communication requirements. In order to facilitate efficient modelling of the communication network during engineering, and for reducing the complexity of network optimisation, disjoint QoS sets have been identified. These sets are referred to as traffic classes [6]. Typically, only three traffic classes are needed in industrial environments [6], i.e.
+
+- deterministic periodic communication;
+- deterministic aperiodic communication; and
+- non-deterministic communication.
+
+Deterministic periodic communication stands for periodic communication with stringent requirements on timeliness of the transmission.
+
+Deterministic aperiodic communication stands for communication without a pre-set sending time. Typical activity patterns for which this kind of communication is suitable are event-driven actions.
+
+Non-deterministic communication subsumes all other types of traffic. Periodic non-real time and aperiodic non-real time traffic are subsumed by the non-deterministic traffic class, since periodicity is irrelevant in case the communication is not time-critical.
+
+#### **Usage of the parameters in Table C.2.2-1**
+
+Control service request and response; monitoring service response and indication.
+
+### C.2.3 Influence quantities
+
+**Table C.2.3-1: Candidate application influencing parameters for the dependable communication service interface**
+
+| Parameter name | Typical metric (unit) | Traffic class (note) | | | Usage of this parameter |
+|-----------------------|----------------------------------------------------------------------------------------------|--------------------------------------|---------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------|
+| | | Deterministic periodic communication | Deterministic aperiodic communication | Non-deterministic communication | |
+| Burst | Maximum user data length (byte) and line rate of the communication service interface (bit/s) | – | X | X | Service request and response; monitoring service response and indication |
+| Message size | Maximum or current value (byte) | X | (X) | (X) | Service request and response; non-deterministic data transmission; deterministic aperiodic data transmission |
+| Service time interval | Start (time) and end (time) | X | X | X | Service request and response |
+| Survival time | Maximum (s) | X | X | – | Service request and response |
+| Transfer interval | Target value and timeliness (s) | X | – | – | Service request and response |
+
+NOTE: X: applies; (X): usually does not apply; –: does not apply.
+
+#### Parameter description
+
+#### *Burst*
+
+The transmission of, for instance, program code and configuration data may be handed to the 3GPP system as data burst. In this case, the ingress data rate exceeds the capacity of the network, which implies that some of the data has to be stored within the ingress node of the communication system before it can be transmitted to the egress interface(s). However, the application consuming the communication service requires that the data of such a burst needs to be transmitted completely. This is in contrast to periodic data transmission, where new messages overwrite old ones.
+
+Typical metrics for bursts: maximum user data length and line rate of the communication service interface.
+
+#### *Message size*
+
+The user data length indicates the (maximum) size of the user data packet delivered from the application to the ingress of the communication system and from the egress of the communication system to the application. For periodic communication this parameter can be used for calculating the requested user-experienced data rate. If this parameter is not provided, the default is the maximum value supported by the PDU type (e.g. Ethernet PDU: maximum frame length is 1,522 octets, IP PDU: maximum packet length is 65,535 octets).
+
+#### *Service time interval*
+
+Describes the start and end time of a communication service. Note that there are other ways to describe the service time interval numerically, for instance as the tuple [start time, service duration].
+
+#### *Survival time*
+
+The maximum survival time indicates the time period the communication service may not meet the application's requirement before the communication service is deemed to be in an unavailable state.
+
+NOTE 1: The survival time indicates to the communication service the time available to recover from failure. This parameter is thus tightly related to maintainability [7].
+
+#### *Transfer interval*
+
+Applicable only to periodic communication, the transfer interval indicates the time elapsed between any two consecutive messages delivered by the automation application to the ingress of the communication system.
+
+## C.3 Up time and up state vs. down state and down time
+
+The assessment of periodic deterministic communication services is based on the assessment of successful message transmission over a logical communication link. Message transmission is either:
+
+- *successful, if it is correctly and timely received, or*
+- *unsuccessful, if it is incorrectly received, lost or untimely.*
+
+Up time and down time can be derived from received messages. As far as timely received messages are correct, the logical communication link status is *up*. If a message loss or an incorrectly or untimely received message is detected the logical communication link status is *down*. To denote up and down states the terms “up time interval” and “down time interval”, or alternatively “*available*” and “*unavailable*” may be used. An example of the relation between logical communication link status, communication service status and application status is presented in Figure C.3-1.
+
+
+
+The diagram illustrates the relationship between three status levels over time for a Source Device and a Target Device. The vertical axis represents time, starting from the 'Start of transmission'.
+
+- Source Device:** Sends periodic messages (orange arrows). Some are correctly received, while others are lost (dashed arrows). A 'Deadline for expected message' is indicated by a red double-headed arrow.
+- Target Device:**
+ - Logical comm. link status:** Shows 'DOWN' and 'UP' states. It transitions from 'UP' to 'DOWN' when a message is lost and back to 'UP' when messages are correctly received again.
+ - Communication service status:** Shows 'DOWN' and 'UP' states. It has a 'Survival Time' period after the link goes down before it transitions to 'DOWN'. It transitions to 'UP' when the link is 'UP' again.
+ - Application status:** Shows 'DOWN' and 'UP' states. It has a 'Survival Time' period after the service goes down before it transitions to 'DOWN'. It transitions to 'UP' when the service is 'UP' again.
+- Intervals:**
+ - Operational interval:** The duration where the application status is 'UP', which is approximately equal to the 'Up time interval'.
+ - Down time interval:** The duration where the application status is 'DOWN'.
+ - Application recovery time:** The time required for the application to recover from a 'DOWN' state to an 'UP' state.
+
+Figure C.3-1: Relation between logical communication link, communication service and application statuses (example with lost messages).
+
+**Figure C.3-1: Relation between logical communication link, communication service and application statuses (example with lost messages)**
+
+The flow of events in Figure C.3-1 is as follows:
+
+- The logical communication link is up and running (blue line is UP). A source device starts sending periodic messages to a target device (orange arrows), on which an automation function (application) is running. The
+
+communication service is, from the point of view of the target application, in an up state (violet line is UP) and so is the application (green line is UP).
+
+- b) The logical communication link status changes to down state if it no longer can support end-to-end transmission of the source device's messages to the target device in agreement with the negotiated communication requirements. Once the application on the target device senses the absence (or unsuccessful reception) of expected messages ("Deadline for expected message" in Figure C.3-1), it will wait a pre-set period before it considers the communication service to be unavailable ; this is the so-called survival time. The survival time can be expressed as
+ - a period or,
+ - especially with cyclic traffic, as maximum number of consecutive incorrectly received or lost messages.
+- c) If the survival time has been exceeded, both the communication service and the application transition into a down state (violet and green lines change to DOWN in Figure C.3-1). The application will usually take corresponding actions for handling such situations of unavailable communication services. For instance, it will commence an emergency shutdown. Note that this does not imply that the target application is "shut off"; rather it transitions into a pre-defined state, e.g. a safe state. In the safe state, the target application might still listen to incoming packets or may try to send messages to the source application.
+- d) Once the logical communication link status is in the up state again (blue line in Figure C.3-1 changes to UP), the communication service state as perceived by the target application will change to the up state. The communication service is thus again perceived as available (violet line changes to UP in Figure C.3-1). The state of the application, however, depends on the counter measures taken by the application. The application might stay in down state if it is in a safe state due to an emergency shutdown. Or, the application may do a recovery and change to up state again. The time needed for the application to return to the up state after the communication service is restored is shown as "Application recovery time" in Figure C.3-1.
+
+The availability of the communication service is calculated using the accumulated down time. For instance, in case the communication service is expected to run for a time $T$ , the unavailability $U$ of the communication service can be calculated as
+
+$$U = \frac{\sum_i \Delta t_i}{T}$$
+
+Where $\Delta t_i$ is the length of the $i$ -th downtime interval of the communication service within the time period $T$ . The communication service availability $A$ can then be calculated as
+
+$$A = 1 - U.$$
+
+## C.4 Timeliness as an attribute for timing accuracy
+
+### C.4.1 Overview
+
+There are several time parameters in dependability assessment. A required value is specified for every time parameter. This value can be a maximum, mean, modal, minimum etc. Typically, there is a deviation from the desired value to the actual value. Jitter is often used to characterise this variation. Since jitter generally is used for characterising the behaviour of a measured parameter, for instance the scatter of measured end-to-end latencies ("the world as it is"), it can be quite confusing to use it for formulating service performance requirements ("the world as we want it to be"). What is needed is a concept and related parameters that allow for formulating and talking about the end-to-end latency requirements in Clause 5 and Annex A.
+
+The most important attribute is timeliness. Timeliness can be formulated a permitted interval for the actual value of the time parameter. Accuracy, earliness and lateness describe the allowed deviation from a target value. Accuracy is the magnitude of deviation. It can be negative (early) or positive (tardy).
+
+### C.4.2 Network latency requirement formulated by use of timeliness
+
+In 5G networks, the end-to-end latency KPI is a critical KPI in order to ensure that the network can deliver the packet within a time limit specified by an application: not too early and not too late.
+
+In cyber-physical automation, the arrival time of a specific packet should be strictly inside a prescribed time window. In other words, a strict time boundary applies: [minimum end-to-end latency, maximum end-to-end latency]. Otherwise, the transmission is erroneous. Although most use cases that require timely delivery only specify the maximum end-to-end latency, the minimum latency is also sometimes prescribed. In the latter case, a communication error occurs if the packet is delivered earlier than the minimum end-to-end latency. An example for a related application is putting labels at a specific location on moving objects, and the arrival of a message is interpreted as a trigger for this action. In other words, the application does not keep its own time, but interprets the message arrival as clock signal. Maximum and minimum end-to-end latency alone do not disclose which value is preferred, i.e. target value. The next three subclauses introduce concepts help with relating maximum end-to-end latency, minimum end-to-end latency, and target value to each other.
+
+### C.4.3 Timeliness
+
+Timeliness is described by a time interval (see Figure C.4.3-1). The interval is restricted by a lower bound ( $t_{LB}$ ) and an upper bound ( $t_{UB}$ ). This interval contains all values $t_A$ that are within an accepted "distance" to the target value $t_R$ .
+
+
+
+The figure shows a 2D coordinate system with a vertical axis labeled 'TL' and a horizontal axis labeled 't'. A diagonal orange line starts from a negative value on the vertical axis and extends upwards and to the right. Two vertical red lines intersect the horizontal axis at points labeled $t_{LB}$ and $t_{UB}$ . A tick mark on the horizontal axis between these two lines is labeled $t_R$ . The orange line passes through the point $(t_R, 0)$ on the horizontal axis.
+
+Figure C.4.3-1: Timeliness function. A graph showing the Timeliness (TL) function over time (t). The vertical axis is labeled TL and the horizontal axis is labeled t. A diagonal orange line represents the function. Two vertical red lines mark the lower bound t\_LB and the upper bound t\_UB. The target value t\_R is marked on the horizontal axis between t\_LB and t\_UB.
+
+**Figure C.4.3-1: Timeliness function**
+
+A message reception is considered in time, if it is received within the timeliness interval. If it is received outside the timeliness interval, the message reception is considered invalid. This is related to the communication error "unacceptable deviation from target end-to-end latency" (see Subclause B.6). In other words, maximum end-to-end latency = $t_{UB}$ and minimum end-to-end latency = $t_{LB}$ .
+
+Timeliness is related to deviation (see Subclause C.4.4), the lower bound $t_{LB}$ is related to earliness (see Subclause C.4.5), and the upper bound $t_{UB}$ is related to lateness (see Subclause C.4.6).
+
+### C.4.4 Deviation
+
+The term deviation describes the discrepancy between an actual value ( $t_A$ ) and a target value ( $t_R$ ).
+
+$$\text{Deviation}(t_A) = t_A - t_R.$$
+
+Figure C.4.4-1 shows two examples. The target value is 10 time units ( $t_R = 10$ ) in both cases. In the first case (blue) the actual value measures 12 time units ( $t_A = 12$ ). The difference of both amounts to +2 time units, which means that the
+
+deviation is 2 time units [ $\text{Accuracy}(t_A) = 2$ ]. The second case (purple) shows the actual value as 9 time units ( $t_A = 9$ ). The difference of both amounts to -1 time unit, which means that the deviation is -1 time units [ $\text{Accuracy}(t_A) = -1$ ].
+
+
+
+The diagram shows a horizontal timeline with a target time $t_R = 10$ marked by a vertical tick. Above the timeline, a blue horizontal line represents an actual arrival at $t_A = 12$ , with a blue arrow pointing right from the target to the actual value, labeled '2'. Below the timeline, a purple horizontal line represents an actual arrival at $t_A = 9$ , with a purple arrow pointing left from the actual value to the target, labeled '-1'. A green horizontal line is also shown at $t = 10$ , representing the target time.
+
+Figure C.4.4-1: Examples for accuracy values. A timeline diagram showing target time (t\_R = 10) and actual arrival times (t\_A = 12 and t\_A = 9). A blue arrow indicates a deviation of 2 units for t\_A = 12, and a purple arrow indicates a deviation of -1 unit for t\_A = 9.
+
+Figure C.4.4-1: Examples for accuracy values
+
+Figure C.4.4-2 shows the deviation with respect to the target time ( $t$ ). The following applies:
+
+$\text{Deviation}(t) < 0$ for $t < t_R$ ; that is, the arrival is early.
+
+$\text{Deviation}(t) = 0$ for $t = t_R$ ; that is, the arrival is as desired, i.e. on time.
+
+$\text{Deviation}(t) > 0$ for $t > t_R$ ; that is, the arrival is late (see also C.4.6)
+
+
+
+The graph shows a coordinate system with a vertical axis labeled 'AC' and a horizontal axis labeled 't'. A straight line with a positive slope starts from a negative value on the AC axis and crosses the t-axis at a point labeled $t_R$ . For $t < t_R$ , the line is below the t-axis (negative AC), and for $t > t_R$ , the line is above the t-axis (positive AC).
+
+Figure C.4.4-2: Accuracy function. A graph showing the accuracy function AC versus time t. The function is a straight line with a positive slope, crossing the t-axis at t\_R.
+
+Figure C.4.4-2: Accuracy function
+
+### C.4.5 Earliness
+
+Earliness describes how early the actual value is: earliness is greater than 0 if the actual value is less than the target value (see Figure C.4.5-1). The following applies:
+
+$\text{Earliness}(t_A) = t_R - t_A = -\text{Deviation}(t_A)$ for $t_A < t_R$ ;
+
+$\text{Earliness}(t_A) = 0$ for $t_A \geq t_R$ .
+
+In an example, the target value is 10 time units ( $t_R = 10$ ), and the actual value is 7 time units ( $t_A = 7$ ). The difference of both is 3 time units with respect to being early. That means that the earliness is 3 time units [ $\text{Earliness}(t_A) = 3$ ].
+
+
+
+Figure C.4.5-1: Earliness function graph. The vertical axis is labeled E and the horizontal axis is labeled t. A purple line starts at a point on the E axis and decreases linearly to a point on the t axis labeled t\_R. From t\_R onwards, the line is horizontal along the t axis.
+
+Figure C.4.5-1: Earliness function
+
+### C.4.6 Lateness
+
+Lateness describes how much greater the actual value is than the target value: lateness is greater than 0 if the actual value is greater than the desired value (see Figure C.4.6-1). The following applies:
+
+$$L(t_A) = 0 \text{ for } t_A \leq t_R;$$
+
+$$L(t_A) = t_A - t_R = \text{Deviation}(t_A) \text{ for } t_A > t_R.$$
+
+In an example, the target value is 10 time units ( $t_R = 10$ ), and the actual value measures 14 time units ( $t_A = 14$ ). The difference of both is 4 time units with respect to being late. That means that the lateness is 4 time units [ $L(t_A) = 4$ ].
+
+
+
+Figure C.4.6-1: Lateness function graph. The vertical axis is labeled L and the horizontal axis is labeled t. A blue line is horizontal along the t axis until it reaches a point labeled t\_R. At t\_R, the line becomes a 45-degree upward-sloping line.
+
+Figure C.4.6-1: Lateness function
+
+### C.4.7 Conclusion
+
+Using the concepts of earliness and lateness (see Subclauses C.4.5 and C.4.6, respectively), the maximum and minimum end-to-end latency can be rewritten as follows.
+
+$$\text{Maximum end-to-end latency} = \text{target end-to-end latency} + \text{maximum lateness};$$
+
+$$\text{Minimum end-to-end latency} = \text{target end-to-end latency} - \text{maximum earliness}.$$
+
+## --- C.5 Communication service terminology w.r.t. 5G network and vertical applications
+
+This section clarifies the wording and terminology with respect to communication interfaces that are relevant for vertical applications. Because the 3GPP network does not cover the complete ISO-OSI communication stack, it is important to distinguish between
+
+- the vertical applications' point of view, and
+- the 3GPP network's point of view.
+
+In this section, the relation between those two is clarified.
+
+Figure C.5-1 shows a simplified version of the communication stack. The PHY layer, the MAC layer and some parts of the IP layer are part of the 3GPP network. The layers that are part of the 3GPP network are referred to as lower communication layers (LCL). The communication stack also includes an application. The OSI layers related to providing data to the application are referred to as the higher communication layers (HCL). The interface between LCL and HCL is referred to as communication service interface (CSIF).
+
+For the assessment of the overall system performance, it is important to differentiate between the 3GPP network's performance (i.e., including only the LCL and measured at the CSIF) and the overall system performance including the application layer (i.e., including both, the LCL and the HCL). In Figure C.5-1, the orange arrow depicts the vertical application's point of view. The blue arrows indicate two options to measure the 3GPP network's performance, i.e., including and excluding the IP layer.
+
+
+
+Figure C.5-1: Network performance measurements at different communication system interfaces (CSIF). The diagram shows two communication stacks. The left stack has layers: Distributed automation function, Application layer, Transport Layer, IP layer, MAC Sub-layer, and Physical layer. The right stack is identical. Between the stacks, an orange arrow labeled 'communication system performance' points from the Application layer down to the Physical layer. Blue arrows point to the CSIF between the Transport Layer and IP layer (labeled 'Example: CSIF for smart manufacturing') and to the CSIF between the IP layer and MAC Sub-layer (labeled 'Example: CSIF for real-time process control'). All layers point down to a common 'Channel' at the bottom.
+
+**Figure C.5-1: Network performance measurements at different communication system interfaces (CSIF)**
+
+Figure C.5-2 illustrates how messages are transmitted from a source application device (e.g., a programmable logic controller) to a target application device (e.g. an industrial robot). The source application function (AF) is executed in the source operating system (OS) and hands over a message to the application layer interface of the source communication device. In the higher communication layers (HCL), which are not part of the 3GPP system, the data is processed. From the HCL the data is transferred to the lower communication layers (LCL), which are part of the 3GPP system. After transmission through the physical communication channel and the LCL of the target communication device, the data is passed to the HCL and lastly to the target application device. Characteristic parameters with respect to time are defined in Figure C.5-2.
+
+From 3GPP system point of view:
+
+- Transfer interval of 5G system: Time between the arrival of two pieces of data at the source CSIF.
+- End-to-end latency: Time measured from the point when a piece of data received at the CSIF in the source communication device until the same piece of data is passed to the CSIF in the target communication device.
+
+From vertical application point of view:
+
+- Transfer interval of vertical application: Time between the transmission of two successive pieces of data from the source application.
+- Transmission time: Time measured from the point when a piece of data is handed from the application layer interface of the source application device, until the same piece of data is received at the application layer interface of the target application device.
+- Update time: Time between the reception of two consecutive pieces of data at the application layer interface to the target application device.
+
+If not stated otherwise, the terms "end-to-end latency" and "transfer interval" refer to the 3GPP system / 5G network parameters in this document.
+
+
+
+The diagram illustrates the data flow and timing for a downlink communication service via a 5G network. It is divided into five vertical zones: Distributed automation function (Source), Higher layers (Source), Communication service via 5G network, Higher layers (Target), and Distributed automation function (Target).
+On the Source side, the 'Application device - Source' contains 'AF' and 'OS' blocks. Data flows from 'AF' to 'OS', then into the 'Communication device - Source' which contains 'HCL', 'CSIF', and 'LCL' blocks. The 'Transfer Interval of vertical application' is marked between the 'OS' block and the 'HCL' block. The 'Transfer interval of 5G system' is marked at the 'CSIF' block.
+The data then enters the 'Communication channel' within the 'Communication service via 5G network' zone.
+On the Target side, data flows from the 'Communication channel' into the 'Communication device - Target' (containing 'LCL', 'CSIF', and 'HCL' blocks), then into the 'Application device - Target' (containing 'OS' and 'AF' blocks).
+Timing parameters are indicated: 'End-to-end latency' is the time from the 'CSIF' block on the source side to the 'CSIF' block on the target side. 'Transmission time' is the time from the 'CSIF' block on the source side to the 'OS' block on the target side. 'Update time' is the time from the 'CSIF' block on the source side to the 'AF' block on the target side.
+
+Diagram illustrating the relation between application device and communication device in a downlink example. It shows the flow of data from a source application device through various layers (AF, OS, HCL, CSIF, LCL) into a 5G network communication channel, and then back out through the layers to a target application device. Timing parameters like Transfer Interval of vertical application, Transfer interval of 5G system, End-to-end latency, Transmission time, and Update time are indicated.
+
+Figure C.5-2: Relation between application device and communication device (downlink example).
+
+# Annex D (informative): 5G in industrial automation: different and multiple time domains for synchronization
+
+## D.1 Description
+
+The required synchronization precision is usually given as the maximum absolute value of the time difference between sync master and any device in the synchronisation domain (time domain or clock domain). A common example is a synchronisation precision of $\leq 1 \mu\text{s}$ . This is equivalent to $\pm$ the precision value, so $\pm 1 \mu\text{s}$ between sync master and any device in the synchronisation domain, resulting in two times this value as maximum absolute time difference between any two devices in the synchronisation domain ( $2 \mu\text{s}$ in the example).
+
+An industrial automation network generally consists of two distinct time domains.
+
+First is the *global time domain*. This is the time used for overall synchronization in the system (e.g. the factory). It is used to align operations and events chronologically. Industrial automation uses the term *universal time domain* [20] for the global time domain described in this document. Global time is known as a synonym for universal time in industrial automation. Global time is called wall clock in certain areas and standards.
+
+The synchronization precision is typically $\leq 1 \mu\text{s}$ [20]. In some areas, a precision of $\leq 100 \mu\text{s}$ might be sufficient for the global time domain if a working clock with precision of $\leq 1 \mu\text{s}$ is available. The assigned timescale is usually the International Atomic Time (TAI, *temps atomique international*), based on the precision time protocol (PTP) epoch (starting from 1 January 1970 00:00:00 TAI) [22]. While there is usually only one global time, multiple global time domains are possible.
+
+Clock synchronization in the global time domain usually applies to all UEs within the industrial facility in industrial automation. That is, a global time domain covers usually the industrial facility.
+
+Second is the *working clock domain*. Working clock domains are constrained in size. They often consist of a single machine or a set of neighbouring machines that physically collaborate. The restricted size allows very precise time synchronization ( $\leq 1 \mu\text{s}$ ) with efficient network components. Synchronisation to a working clock is used to align e.g. production lines, production cells, or machines/functional units. In these cases, the application synchronizes locally within the working clock domains (Figure D.1-1), allowing precise synchronization with more efficient components. A global time domain usually contains multiple working clock domains. The starting point (epoch) is the start of the working clock domain.
+
+
+
+The diagram shows a large circle labeled "Universal Time Domain" at the top. Inside this circle, there are two smaller circles. The left smaller circle is green and labeled "Working Clock Domain 1" at its bottom; it contains two black robot icons. The right smaller circle is red and labeled "Working Clock Domain 2" at its bottom; it contains one blue robot icon. This visualizes that multiple working clock domains can exist within a single universal time domain.
+
+Diagram illustrating the relationship between a Universal Time Domain and multiple Working Clock Domains. A large outer circle represents the Universal Time Domain. Inside it are two smaller circles: a green one on the left labeled 'Working Clock Domain 1' containing two robot icons, and a red one on the right labeled 'Working Clock Domain 2' containing one robot icon.
+
+Figure D.1-1: Global time domain and working clock domains
+
+The assigned timescale of a working clock domain is arbitrary (timescale ARB [22]). Therefore, different working clock domains may have different timescales and different synchronisation accuracy and precision. Robots, motion control applications, numeric control, and any kind of clocked / isochronous application rely on the timescale of the working clock domain to make sure that actions are precisely interwoven as needed.
+
+Clock synchronization in the working clock domain is constraint in size. A specific working clock domain will contain only a subset of the UEs within the industrial facility. Often, the UEs of the working clock domain are connected to the same gNB. However, it is also possible that a working clock domain contains multiple neighbouring gNBs. This depends on the actual use case and its vertical application.
+
+Devices may be part of multiple time domains leading to overlapping working clock domains.
+
+The required precision (usually $\leq 1 \mu\text{s}$ ) is between the sync master and any sync devices of the clock domain, both, global time domain and working clock domain.
+
+Clock domains might be called sync domains in certain areas and standards.
+
+## D.2 Merging of working clock domains
+
+One key issue of the integration of TSN and 5G wireless networks that has to be handled is mobility. The integration of 5G wireless communication into the industrial communication infrastructure allows for mobility in the manufacturing process. This mobility enhances flexibility in the manufacturing process, e.g. through adding certain manufacturing capabilities on-demand by having a machine move to the respective production line. This means that machines that are synchronized to different working clock domains may need to interact with each other.
+
+The following scenario illustrates this. After the mobile machine has arrived at the intended location and is stationary again, the two interacting working clock domains have to be synchronized with each other. Otherwise interaction might not be possible without interfering with ongoing operations. An example is an autonomous mobile handling robot adding parts to an assembly line. Without synchronization between both, correct placement of the parts would be impossible.
+
+However, it is not feasible to schedule these interactions beforehand. Therefore, the interaction between different working clock domains requires a concept for handling the communication. TSN provides already mechanisms for this. The 5G systems and the UEs need to provide an interface in order to exchange information of the clock domain.
+
+
+
+Figure D.2-1: Working clock domain interactions 'Merge' and 'Separate'. The diagram shows two scenarios within a 'Universal Time Domain' (represented by a large oval). In the 'Merge' scenario (left), 'Working Clock Domain 1' (a green oval) contains two stationary robots and a mobile robot. In the 'Separate' scenario (right), 'Working Clock Domain 1' (green oval) contains two stationary robots, while 'Working Clock Domain 2' (a red oval) contains the mobile robot. The mobile robot is shown interacting with the stationary robots in both cases.
+
+**Figure D.2-1: Working clock domain interactions "Merge" and "Separate"**
+
+When members of different working clock domains interact, there are two possible options (Figure D.2-1). Which option is used depends on the application and its requirements.
+
+- Merge: The working clock domains merge into one. This option can be used in applications where synchronization is critical, e.g. high precision robots interacting with each other.
+
+- Separate: The members of the different working clock domains interact while keeping their own separate time synchronizations. This option can be used in applications where synchronization is non-critical, e.g. an AGV collecting finished products from a production line.
+
+## --- D.3 Time synchronization with 5G networks
+
+For the time synchronization with 5G networks, we consider two possible options.
+
+The 5G system uses the IEEE 802.1AS sync domains [22]: In this case, the 5G system provides a media dependent interface to the IEEE 802.1AS sync domain, which the application can use to synchronize to the sync domain. In the IEEE 802.1AS standard [22], a similar concept is detailed in the MDSyncSend and MDSyncReceive structures.
+
+The 5G system provides the working clock domains and global time domain: In this case, the 5G system has to provide an interface which the application can use to derive their working clock domain or global time domain. A device can belong to multiple working clock domains. An application can use each of these as the reference clock for synchronization (reference clock model).
+
+NOTE: The required precision (usually $\leq 1 \mu\text{s}$ ) is between the sync master and any sync device of the clock domain.
+
+# Annex E (informative): Audio and Video Production
+
+## E.1 Description
+
+AV production includes television and radio studios, outside and remotely controlled broadcasts, live newsgathering, sports events, music festivals, among others. All of these applications require a high degree of reliability, since they are related to the capturing and transmission of data at the beginning of a production chain. This differs drastically when compared to other multimedia services because the communication errors will be propagated to the entire audience that is consuming that content both live and recorded for later distribution. Furthermore, the transmitted data is often post-processed with nonlinear filters which could actually amplify defects that would be otherwise not noticed by humans. Therefore, these applications call for uncompressed or only slightly compressed data, and very low probability of errors. These devices will also be used alongside existing technologies which have a high level of performance and so any new technologies will need to match or improve upon the existing workflows to drive adoption of the technology.
+
+The performance aspects that are covered by/in TS 22.263 [27] (Service requirements for Video, Imaging and Audio for professional applications) also target the latency that these services experience.
+
+In recent years, production facilities have moved from bespoke unidirectional highly specialised networks to IP based systems and software-based workflows. This migration is expected to continue, and wireless IP connectivity is key to a number of these workflows.
+
+Typical set ups require multiple devices such as cameras, microphones and control surfaces that require extremely close synchronisation to maintain consistency of pictures and audio. Such clock synchronization requirements are captured in clause 5.6. Often devices need to communicate directly to each other for instance a camera to a monitor or a microphone to a PA system.
+
+Video and audio applications also require extremely high quality of service metrics as the loss of a single packet can cause picture or sound breakup in the downstream processing or distribution. Often this is a legal, regulatory or contractual agreement to maintain a high quality, stable and clear video or audio signal.
+
+## E.2 Multiple source wireless studio
+
+This use case will deploy a multiple camera studio of approximately 1,000 m2 (~5 cameras) where wired and wireless functionalities currently provided by traditional infrastructure technologies are likely to be deployed using a standalone non-public network. A combination of IP enabled wired and wireless cameras working at both HD and UHD resolutions will be deployed in a studio. Associated equipment such as video monitors, prompting systems, camera control will be provided over the 5G network. Camera timing and synchronisation will be provided over the 5G system. As well as video, audio will be sourced from both wired and wireless microphones incl. control/monitoring and combined with the video to produce high quality synchronised AV content. 5G will also be deployed to control lighting and camera robotics. Talkback intercom systems will be deployed using low latency multicast links.
+
+Today's digital AV network transport is typically handled separately for wireless and wired transfers (see figure E.1.2-1). Wireless AV transmissions are implemented with application specific solutions that allow deterministic data transport of a single isolated audio or video link. Wired AV transmissions are Ethernet / IP based. Quality of service in AV IP networks is mainly achieved with IP DiffServ / DSCP based prioritization of packets in network switches. This method is sufficient for most AV use cases since jitter resulting from packet collisions is small, for example in the order of 10 µs per concurring data stream in Gbit Ethernet.
+
+
+
+Figure E.2-1: Typical AVPROD setup diagram. A central 'Network switch' is connected to a 'Mixing / production console' via an 'Ethernet / IP' link with 'QoS = IP DiffServ / DSCP'. The network switch is also connected to a 'Loudspeaker' and a 'Display'. Two 'wireless receiver' units are connected to the network switch. One 'wireless receiver' is connected to a 'microphone' and an 'In-ear-monitor' via 'Application specific deterministic' links. The other 'wireless receiver' is connected to a 'Camera' via an 'Application specific deterministic' link. A 'wireless transmitter' is also connected to the network switch and has a dashed connection to the 'In-ear-monitor'.
+
+**Figure E.2-1: Typical AVPROD setup**
+
+The microphones and cameras can be co-located in a broadcast centre in which case they would communicate through a LAN or NPN. For remote production operations the mixing and production console may be separated by some distance (existing examples are cross continental. In this instance they may communicate via a PLMN or combination of PLMN and WAN networks.
+
+Some approaches may also deploy main (leader) equipment at the broadcast centre with secondary (follower) equipment at the location site to reduce latency.
+
+Other aspects of this workflow may also include robotic control where both the physical position (height, direction and tilt) and the technical control (focus, zoom, iris, colour) of a device of a camera, microphone or light may be controlled remotely. In this instance round trip latency of < 20ms is required in order for an operator to see a move reflected at his control position as it is made.
+
+It is important to note that these are a combination of automated robotics (pre-programmed moves) and manually controlled robotics (following an unpredictable event such a sport).
+
+## E.3 Timing use in AV production applications
+
+Timing of multiple devices such as microphones and camera is also critical. Timing signals are used in 2 separate ways.
+
+- To maintain synchronisation between devices so that electronic shutters on cameras operate at the same time and frequency and that when cutting between any two cameras pointed at the same source no discernible jumps can be seen. This requires accuracy within the frame boundary of a given video signal. A single frame of video at 120 Hz would require a clock accurate to within 8 ms.
+- To timestamp an IP packet carrying a video or audio sample. Existing standards and workflows for AVPROD rely on IEEE 1588 PTP timing with a SMPTE media profile applied. This requires a clock accurate to within 1 $\mu$ s
+
+
+
+The diagram illustrates the timing synchronization for AVPROD. At the top, a **GPS** unit and a **Common Reference Clock** are connected to a **PTP** (Precision Time Protocol) cloud. The PTP cloud is connected to a **2110 Enabled Device**. Inside this device, an **Internal Device Clock** is shown. To its left, the **Video Media Clock** (values: 0 5 0 7 7 4 8 6) and **Audio Media Clock** (values: 1 9 4 3 1 1 6 2) are connected to the internal clock. Below each media clock, a **Zero Offset** is applied to generate the **Video RTP Clock** (values: 0 5 0 7 7 4 8 6) and **Audio RTP Clock** (values: 1 9 4 3 1 1 6 2). These RTP clocks are used to generate **RTP Timestamps** for **Video Datagram** (value: 05077486) and **Audio Datagram** (value: 19431162). The RTP timestamps are shown being exchanged between the video and audio datagrams.
+
+Diagram of typical IP based timing setup for AVPROD showing GPS, PTP, and 2110 Enabled Device components.
+
+Figure E.3-1 Typical IP based timing set up for AVPROD
+
+# Annex F (informative): Relation of reliability and communication service availability
+
+Availability and reliability are used both in 3GPP and vertical industries, but with different meanings. Communication service availability addresses the availability of a communication service. This definition follows the vertical standard IEC 61907 [7]. On the other hand, reliability is a 3GPP term and addresses the availability of a communication network. The relation of both terms is depicted in figure F-1 for a mobile network.
+
+
+
+Figure F-1: Illustration of the concepts reliability and communication service availability. The diagram shows a central 'Mobile Network' cloud connected to 'End node A' and 'End node B'. 'End node A' is connected to 'Application A & communication protocol' via 'Communication Service Interface A'. 'End node B' is connected to 'Application B & communication protocol' via 'Communication Service Interface B'. A green double-headed arrow labeled 'Communication Service Availability' spans from the interface of Application A to the interface of Application B. A blue double-headed arrow labeled 'Reliability' spans between End node A and End node B.
+
+**Figure F-1: Illustration of the concepts reliability and communication service availability.**
+
+As depicted, reliability covers the communication-related aspects between two nodes (here: end nodes), while communication service availability addresses the communication-related aspects between two communication service interfaces. This might seem to be a small difference, but this difference can lead to situations, where reliability and communication service availability have different values.
+
+## Example: traffic gets "stuck"
+
+The related scenario is depicted in figure F-2.
+
+
+
+Figure F-2: Example in which reliability and communication service availability have different values. The diagram is identical to Figure F-1, but with an additional element at the bottom. A label 'Communication:' is followed by an orange arrow pointing right, labeled 'Packages from
+
+**Figure F-2: Example in which reliability and communication service availability have different values. Packages are reliably transmitted from the communication service interface A to end node B, but they are not exposed at the communication service interface B.**
+
+This scenario addresses unicast communication from application A to B. The packets are handed over at the communication service interface A from the application to the communication network, and the packets are then transmitted to the end node B. In this example, the packets received by end node B are not exposed at the communication service interface B. So, even if all packets that are handed over to end node A are successfully delivered to end node B within the time constraint required by the targeted service (reliability = 100 %), the
+
+communication service availability is 0% since no packets arrive at the "end", namely the communication service interface B.
+
+## **Example: packets dropped at the communication service interface**
+
+The related scenario is depicted in figure F-3.
+
+
+
+The diagram illustrates a communication scenario between Application A and Application B, mediated by End node A, a Mobile Network, and End node B.
+
+Key components and labels:
+
+
+- Application A & communication protocol** (green box on the left)
+- Communication Service Interface A** (small vertical label between App A and End node A)
+- End node A** (blue box)
+- Mobile Network** (cloud shape in the center)
+- End node B** (blue box)
+- Communication Service Interface B** (small vertical label between End node B and App B)
+- Application B & communication protocol** (green box on the right)
+- Communication Service Availability** (green double-headed arrow spanning from App A to App B)
+- Reliability** (blue double-headed arrow spanning from End node A to End node B)
+- Communication:** (orange arrow pointing right)
+- !** (red exclamation mark)
+- Packages from "A" to "B"** (red arrow pointing right)
+
+ The diagram shows that while Reliability is maintained between the two end nodes, Communication Service Availability is affected by packet drops at the communication service interfaces, specifically at Interface B in this context.
+
+Figure F-3: Diagram illustrating a scenario where reliability and communication service availability have different values. The diagram shows a flow from Application A to End node A, through a Mobile Network to End node B, and finally to Application B. A green double-headed arrow labeled 'Communication Service Availability' spans from Application A to Application B. A blue double-headed arrow labeled 'Reliability' spans from End node A to End node B. Below this, a red arrow labeled 'Packages from "A" to "B"' shows packets being transmitted from Application A, but only half of them reach End node B, as indicated by a red exclamation mark and a dashed line.
+
+**Figure F-3: Example in which reliability and communication service availability have different values. Only half of the packets handed over to the end node A are actually transmitted to end node B and then handed over to application B at the communication service interface B.**
+
+This scenario describes unicast communication of evenly interspersed packets from application A to B. The packets are handed over at the communication service interface A from the application to the communication network, and the packets are then transmitted to the end node B. However, only every second packet is actually successfully handed over to end node A and then transmitted to end node B. Thus, only half of the packets arrive at application B. Note though that the reliability of the mobile network is 100%, since all packets transmitted by end node A are delivered to end node B within the time constraint required by the targeted service. However, depending on the agreed QoS, the communication service availability can be of the same value as the reliability or much lower. For instance, if the agreed survival time is equal to or larger than the end-to-end latency, reliability and communication service availability are equal. However, if the survival time is smaller, the reliability is two times the communication service availability.
+
+Note that the shortest time interval over which the communication service availability should be calculated is the sum of maximum allowed end-to-end latency and survival time.
+
+# Annex G (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------|-------------|--|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | |
+| 2018-05 | SA1#82 | S1-181551 | – | – | – | Skeleton for TS 22.104 ("Service requirements for cyber-physical control applications in vertical domains") | 0.0.0 | |
+| 2018-05 | SA1#82 | S1-181552 | – | – | – | Includes agreements at SA1#82, Dubrovnik, Croatia | 0.1.0 | |
+| 2018-08 | SA1#83 | S1-182344 | – | – | – | Includes agreements at SA1#83, West Palm Beach, Florida | 0.2.0 | |
+| 2018-11 | SA1#84 | S1-183276 | – | – | – | Includes agreements at SA1#83, Spokane, WA, USA, rapporteur's clean-up | 0.3.0 | |
+| 2018-12 | SA#82 | SP-181006 | | | | Presentation to SA for one-step approval | 1.0.0 | |
+| 2018-12 | SA#82 | SP-181006 | | | | Raised to v.16.0.0 following SA approval | 16.0.0 | |
+| 2019-03 | SA#83 | SP-190081 | 0003 | 2 | F | Clarifying UE-to-UE versus UE-to-network | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190081 | 0002 | 1 | F | Moving rail-bound mass transit requirements – shift from cyberCAV | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190081 | 0001 | 1 | F | Clean-up and corrections of TS 22.104 cyberCAV | 16.1.0 | |
+| 2019-06 | SA#84 | SP-190299 | 0008 | | F | Corrections to TS 22.104 v16.1.0 | 16.2.0 | |
+| 2019-06 | SA#84 | SP-190299 | 0006 | 2 | F | Add missing abbreviations to TS 22.104 | 16.2.0 | |
+| 2019-06 | SA#84 | SP-190299 | 0005 | 2 | C | Adding edge computing aspect | 16.2.0 | |
+| 2019-06 | SA#84 | SP-190311 | 0009 | 1 | C | Adding vertical positioning requirements to TS 22.104 v16.1.0 | 17.0.0 | |
+| 2019-09 | SA#85 | SP-190807 | 0012 | 1 | B | Addition of a new synchronisation performance requirement | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190807 | 0011 | 2 | B | Addition of robotic aided surgery and diagnosis performance requirements | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190800 | 0023 | 1 | A | Correction of a figure number in Annex D.2 | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190812 | 0010 | | B | Add one more case for control-to-control communication | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190812 | 0013 | 1 | B | Network operation requirements | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190812 | 0015 | 3 | B | eCAV – Further 5G service requirements for Positioning | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190812 | 0018 | 2 | B | eCAV – Service performance requirements for Industrial Wireless Sensors | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190812 | 0016 | 2 | B | eCAV – further 5G service requirements for wired to wireless link replacement for smart manufacturing / Industry 4.0 | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190812 | 0020 | 3 | B | eCAV – further 5G service requirements for network performance | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190857 | 0021 | 3 | B | ECAV - further 5G service requirements for ProSe communication for CAV | 17.1.0 | |
+| 2019-09 | SA#85 | SP-190856 | 0019 | 3 | B | ECAV - further 5G service requirements for industrial Ethernet integration (clock synchronization, time-sensitive communication) | 17.1.0 | |
+| 2019-12 | SA#86 | SP-191016 | 0027 | 5 | B | Addition of informative annex for AV Prod | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191020 | 0026 | 1 | F | Correction of CMED KPIs tables | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0034 | 4 | A | Clarification of clock synchronicity requirements | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0028 | | F | Addition of transmission directions and movement characteristics | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0030 | 1 | A | Clarification on communication service reliability | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0035 | 1 | F | Derivation of communication service availability and reliability from network performance metrics | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0037 | 1 | D | Editorial and minor corrections to TR 22.104 | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0032 | 2 | C | Network performance requirements for mobile operation panel | 17.2.0 | |
+| 2019-12 | SA#86 | SP-191028 | 0038 | 2 | F | TS 22104 - Annex A for cooperative carrying | 17.2.0 | |
+| 2020-07 | SA#88e | SP-200568 | 0050 | | F | Correction of service performance requirements in tables of annex A.6 | 17.3.0 | |
+| 2020-07 | SA#88e | SP-200567 | 0049 | | D | 22.104 Miscellaneous editorial corrections | 17.3.0 | |
+| 2020-07 | SA#88e | SP-200562 | 0041 | 2 | A | Clarifications to communication service performance requirements | 17.3.0 | |
+| 2020-07 | SA#88e | SP-200567 | 0048 | 2 | A | Miscellaneous values for further study | 17.3.0 | |
+| 2020-07 | SA#88e | SP-200562 | 0045 | 2 | A | Correcting description of communication service status in Clause C.3 | 17.3.0 | |
+| 2020-07 | SA#88e | SP-200562 | 0047 | 1 | A | Clock synchronicity budget for the 5G system | 17.3.0 | |
+| 2020-09 | SA#89e | SP-200790 | 0055 | | F | Quality improvement – burst definition | 17.4.0 | |
+| 2020-09 | SA#89e | SP-200790 | 0058 | 1 | D | CR 22.104 R17 - Editorial Improvements – Decimal Separator | 17.4.0 | |
+| 2021-03 | SA#91e | SP-210200 | 0063 | | D | Non-inclusive language replacement 22.104 | 17.5.0 | |
+| 2021-03 | SA#91e | SP-210217 | 0064 | 1 | B | Adding energy efficiency use cases for positioning to the ANNEX A | 17.5.0 | |
+| 2021-06 | SA#92e | SP-210564 | 0075 | 1 | A | Quality improvement - update of definition of communication service availability | 18.1.0 | |
+| 2021-06 | SA#92e | SP-210565 | 0066 | 1 | D | Quality improvement - addition of new annex (relationship between reliability and communication service availability) | 18.1.0 | |
+| 2021-06 | SA#92e | SP-210565 | 0068 | 1 | D | 22.104 - V18.0.0 - quality improvement - update of mobile-robots use case description | 18.1.0 | |
+| 2021-06 | SA#92e | SP-210565 | 0069 | 1 | F | Correction of mobile-robot use cases (UE number) | 18.1.0 | |
+| 2021-06 | SA#92e | SP-210565 | 0070 | 1 | D | Quality improvement - service duration | 18.1.0 | |
+
+| | | | | | | | |
+|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------|--------|
+| 2021-06 | SA#92e | SP-210517 | 0065 | 1 | B | 5G timing resiliency | 18.1.0 |
+| 2021-06 | SA#92e | SP-210524 | 0073 | | D | Alignment of positioning power consumption aspects between 22.261 and 22.104 | 18.1.0 |
+| 2021-06 | SA#92e | SP-210524 | 0072 | 1 | B | Adding LPHAP requirements for Industrial IoT | 18.1.0 |
+| 2021-09 | SA#93e | SP-211038 | 0077 | 2 | A | Quality improvement: update of reference to IEEE 802.1AS | 18.2.0 |
+| 2021-09 | SA#93e | SP-211070 | 0078 | 1 | B | Introduction of Smart Energy Infrastructure Requirements | 18.2.0 |
+| 2021-09 | SA#93e | SP-211070 | 0080 | 1 | B | Annex for smart grid | 18.2.0 |
+| 2021-09 | SA#93e | SP-211070 | 0082 | 1 | B | Introduction of SEI KPIs | 18.2.0 |
+| 2021-09 | SA#93e | SP-211070 | 0083 | 1 | D | Adjusting scope clause in TS 22.104 to the specification's content | 18.2.0 |
+| 2021-09 | SA#93e | SP-211039 | 0084 | 1 | F | Clarification of requirements for clock synchronization with direct device connection and indirect network connection communication | 18.2.0 |
+| 2021-09 | SA#93e | SP-211070 | 0087 | 1 | B | Inclusion of Smart Energy Infrastructure Requirements | 18.2.0 |
+| 2021-12 | SP-94 | SP-211497 | 0089 | 1 | C | Correction of references for clause 2 | 18.3.0 |
+| 2021-12 | SP-94 | SP-211497 | 0090 | | D | Remove editor note for Figure A.4.4.3-1 | 18.3.0 |
+| 2021-12 | SP-94 | SP-211497 | 0091 | 1 | F | Update to Smart Grid normative requirements | 18.3.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22115/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22115/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4760bc26d537b712606f5f9ac65760193216d8b1
--- /dev/null
+++ b/marked/Rel-18/22_series/22115/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e21f214f4450a8199384443f8624c7109b5d0a9aad28e577443c14d6706f701
+size 9383
diff --git a/marked/Rel-18/22_series/22115/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22115/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..572183f874d0155260764a9cc6624702f8740afa
--- /dev/null
+++ b/marked/Rel-18/22_series/22115/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cfcc9b148db535e4da9a6fa63aff27326ac44d3d2110d5e3542edde3f951554
+size 7006
diff --git a/marked/Rel-18/22_series/22115/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/22_series/22115/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4ce5778e672914e2e00977f1d6da6f9bb6fc1bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22115/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6c134a392c59eeb3dbe2d3e58152f2f7badd62abbbf1889da892ebdf88a40a9
+size 48920
diff --git a/marked/Rel-18/22_series/22115/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/22_series/22115/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee8dbdcb44a15212610ac80211105cf0011470e9
--- /dev/null
+++ b/marked/Rel-18/22_series/22115/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c9244318c60e57243b79f532302bcdf57505fba3c7437efab00be3fd8be2a31
+size 124128
diff --git a/marked/Rel-18/22_series/22115/raw.md b/marked/Rel-18/22_series/22115/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..383cfc229282a2288f24cf3718fb2513585d86fc
--- /dev/null
+++ b/marked/Rel-18/22_series/22115/raw.md
@@ -0,0 +1,1024 @@
+
+
+# 3GPP TS 22.115 V18.0.0 (2020-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service aspects; Charging and billing (Release 18)**
+
+
+
+---
+
+The 5G logo consists of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+
+
+The 3GPP logo features the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" and "P" are connected at the top. Below the "G" and "P" is a red signal wave icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, charging
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|--------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Main Requirements and High-Level Principles..... | 7 |
+| 4.1 Cross Phase Compatibility ..... | 9 |
+| 4.2 Charging Entity Relationships ..... | 9 |
+| 4.3 Charging guidelines for IP-Multimedia services ..... | 11 |
+| 4.3.1 User Charging Requirements ..... | 11 |
+| 4.3.1.1 Session End Point Configurations ..... | 11 |
+| 4.3.1.2 Charging Principles For User Session Components ..... | 12 |
+| 4.3.1.3 Other Charging Requirements ..... | 13 |
+| 4.3.2 Roaming Charging Requirements ..... | 14 |
+| 4.3.3 Interconnect Charging Requirements..... | 15 |
+| 4.3.4 Conveyance & Usage charging requirements ..... | 16 |
+| 4.3.5 Charging 3 rd parties ..... | 16 |
+| 4.3.6 Advice of Charge (AoC) ..... | 16 |
+| 4.3.7 Service Aware Charging Requirements ..... | 17 |
+| 4.4 Additional Charging requirements for prepay services..... | 17 |
+| 4.5 QoS and gating based on spending limit..... | 18 |
+| 4.6 ProSe Charging Requirements ..... | 18 |
+| 4.7 Unlicensed access requirements..... | 19 |
+| 4.8 Charging Requirements for Indirect 3GPP Communication..... | 19 |
+| 5 Collection of charging information..... | 20 |
+| 5.1 Charging information Requirements..... | 20 |
+| 5.1.1 Information provided by the user ..... | 20 |
+| 5.1.2 Information provided by the serving network ..... | 20 |
+| 5.1.3 Charged Party ..... | 21 |
+| 5.1.4 Information provided by the third party accessed by the user..... | 22 |
+| 5.2 Special Cases..... | 22 |
+| 5.2.1 Long calls and sessions ..... | 22 |
+| 5.2.2 Multimedia calls ..... | 23 |
+| 5.2.3 Service Change..... | 23 |
+| 5.2.4 E-Commerce..... | 23 |
+| 5.2.5 Volume Based Charging..... | 23 |
+| 5.2.6 VAS..... | 23 |
+| 5.2.7 Usage of IP Multimedia service ..... | 23 |
+| 5.2.8 I- WLAN ..... | 23 |
+| 5.2.9 Charging for two (and multi)-phases services for IMS networks ..... | 23 |
+| 5.2.10 CSG charging requirements for UTRAN and E-UTRAN..... | 24 |
+| 5.2.11 Inter-UE Transfer charging ..... | 24 |
+| 5.2.12 Selected IP Traffic Offload charging..... | 24 |
+| 5.2.12A Charging requirements for IoT small data..... | 24 |
+| 5.2.13 TV Service Support Requirements..... | 24 |
+| 5.2.14 Charging for Flexible Mobile Service Steering..... | 25 |
+| 5.2.15 Restricted local operator services..... | 25 |
+| 5.2.16 Charging for streaming services..... | 25 |
+| 5.2.17 User Identity ..... | 25 |
+| 6 Transfer of Charging Information..... | 25 |
+| 6.1 Integrity, Secrecy and Validation of Content and Receipt of Charging Information ..... | 25 |
+
+- 7 Accounting and Settlement..... 26
+ - 7.1 Delegation of charging authority..... 26
+ - 7.2 Fraud Control ..... 26
+ - 7.2.1 Fraud Control by the Home Environment ..... 26
+ - 7.2.2 Fraud Control by the Serving Network ..... 26
+ - 7.3 Cost Control ..... 26
+ - 7.3.1 Cross Phase Compatibility ..... 27
+ - 7.4 Inter-network Settlement..... 27
+- 8 Automatic Roaming Agreements..... 27
+ - 8.1 Routing the Registration Request..... 28
+ - 8.2 Settlement of charges ..... 28
+- Annex A (informative): Change history..... 29**
+
+# Foreword
+
+This Technical Specification (TS) has been produced by the 3rd 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
+
+The present document describes the Service Aspects of charging and billing of the 3GPP System.
+
+The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The present document will elaborate on the charging requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
+
+# --- 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 TS 22.101: "Service aspects; Service Principles".
+- [2] 3GPP TS 22.066: "Support of Mobile Number Portability (MNP)".
+- [3] 3GPP TS 22.234: "Requirements for 3GPP system to wireless local area network (WLAN) interworking".
+- [4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"
+- [5] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services"
+- [6] ETS 300 178: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information at call set-up time (AOC-S) supplementary service; Service description"
+- [7] ETS 300 179: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information during the call (AOC-D) supplementary service; Service description"
+- [8] ETS 300 180: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information at the end of the call (AOC-E) supplementary service; Service description"
+- [9] TS 183 047: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN IMS Supplementary Services; Advice Of Charge (AOC)"
+- [10] TS 183 058: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification"
+- [11] void
+- [12] 3GPP TS 22.220, "Service requirements for Home NodeBs and Home eNodeBs"
+- [13] 3GPP TS 22.278, "Service requirements for the Evolved Packet System (EPS)"
+- [14] 3GPP TS 22.261: "Service requirements for the 5G system".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the definitions in [4] are supplemented by the following definitions:
+
+**Gateway UE:** a UE, which acts as a gateway providing access to and from the 3GPP network for one or more non-3GPP devices that are connected to the gateway UE.
+
+**Prepay service:** A prepay service allows a subscriber to pay in advance for the use of specific services, the prepay account may be updated each time the subscriber uses the services related to that account.
+
+**Real time:** Time, typically in number of seconds, to perform the on-line mechanism used for fraud control and cost control.
+
+**Session:** logical connection between parties involved in a packet switched based communication This term is used for IP connections rather than the term "call" that is normally used for a connection over conventional (circuit switched) systems.
+
+Note: Information about charging is typically collected in Charging Data Records (CDR).
+
+**Local Charging Zone (LCZ):** A logical grouping of a number of cells, where a special tariff applies for a select group of users. A network may have a number of LCZs. A LCZ does not necessarily need to be aligned with an LA or RA, i.e. the border of LCZ may not be the border of an LA or RA.
+
+**User:** As defined in TR 21.905 [29]: An entity, not part of the 3GPP System, which uses 3GPP System services. Example: a person using a 3GPP System mobile station as a portable telephone. Additional examples for a user in the context of this TS: a non-3GPP device connected to the 3GPP system via a gateway, or an application running on a UE.
+
+**User Identity:** information representing a user in a specific context. A user can have several user identities, e.g. a User Identity in the context of his profession, or a private User Identity for some aspects of private life.
+
+**User Identifier:** a piece of information used to identify one specific User Identity in one or more systems.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document the definition of abbreviations in [4] apply.
+
+# 4 Main Requirements and High-Level Principles
+
+The main new requirements for 3GPP system charging and accounting are:
+
+- to provide charging information for all charges incurred and requiring settlement between the different commercial roles;
+- to allow fraud control by the Home Environment and the Serving network;
+- to allow cost control by the charged party;
+- to provide at the beginning of a chargeable event an indication to the charged party (if involved in the chargeable event) of the charges to be levied for this event;
+- to allow itemised billing for all services charged to each subscription, including voice and data calls, and services offered by home environments;
+- to enable the Home environment to provide a Prepay Service and to enable the serving network to support that Prepay Service for the Home environment's subscribers;
+- to allow interconnect (inter-operator) charging including mobile/fixed operator to mobile/fixed operator (circuit switched & IP), and mobile/fixed operator to IP network provider; and mobile/fixed operator to I-WLAN
+
+operator;
+
+- to allow Network operator to 3rd party supplier (e.g. Value-Added Service Provider) charging;
+- to provide details required for Customer Care purposes;
+- to support the shared network architecture so that end users can be appropriately charged for their usage of the shared network, and network sharing partners can be allocated their share of the costs of the shared network resources.
+
+The high-level principles that will guide the charging requirements are summarised as follows:
+
+- It shall be possible to charge separately for each type of medium used (e.g. voice, video, data) in a session and for each service used (e.g. voice call, streaming video, file download);
+- It shall be possible to charge for different levels of QoS applied for and/or allocated during a session for each type of medium or service used;
+- It shall be possible to charge each "leg" of a session separately. This includes the incoming and outgoing legs and any forwarded/redirected legs. (Note: The legs mentioned here are logical legs, i.e. not necessarily identical to actual signal and traffic flow. Even though tromboning may be avoided by optimal routing, the operator should still be able to charge for the 'virtual legs' of the call);
+- It shall be possible to charge unsuccessful calls and sessions (e.g. for billing purposes, to provide the user a full documentation of his call attempts);
+- The user can be charged according to the service used irrespective of the technology used to deliver it. (That is, the charge is not derived from whether 2G or 3G is used);
+- The user can be charged according to the technology used to deliver a service. (That is, different charges can be applied on 2G and 3G);
+- It shall be possible to charge a user according to the network resources used. For example, if a large bandwidth is required to use high quality video, the user could be charged accordingly. This is related to charging by QoS;
+- It shall be possible to charge users flexibly for the use of extra resources (in at least the same network) for all legs of the call. For example, if a video component is added to a voice call the use of extra radio resource at both ends of the call could be paid for by each user in the call or totally by the initiating user;
+- It shall be possible to suppress charging for certain types of connection e.g. when a customer receives tones or network announcements or during sessions such as automated pre-pay top-up;
+- It shall be possible to apply different charging based on tariff information provided by a 3rd party. This tariff information may change during the use of the service (e.g. based on menu selection in a voice response menu). In this case the requirement applies both for customer-charging and interconnect-charging;
+- It shall be possible for the home network to charge its customers while roaming in the same ways as when they are at home. For example, if duration-based charging is used for charging for streaming music in the home network, then it shall be possible to apply the same principle when the user is roaming;
+- It shall be possible for operators to have the option to apply charging mechanisms that are used in GSM/GPRS. For example, for duration of a voice call, for the amount of data transmitted (e.g. for streaming, file download, browsing) and for an event (one-off charge);
+- It shall be possible for a network operator to charge its users for activities while roaming so that the home network will get the capability to raise service charges depending on the roamed to network, e.g. because of inter operator charges for the use of service capabilities within the visited network which will in general depend on the serving network. The ability to supply all the necessary information for all the charging options will depend on the capability of the visited network. For service capabilities which are provided by the home network, however, it is required that the charging information is collected to allow to identify the serving network of the served subscriber;
+- It shall be possible for charging to be applied based on location, presence, push services etc.;
+- The network may provide information to the UE so that the UE is able to notify and indicate to the user the LCZs it is in. This allows the user to decide whether to accept/originate the service depending on the LCZs they
+
+are in;
+
+- It shall be possible to charge using pre-pay, post-pay, advice of charge, 3rd party charging techniques;
+- It shall be possible for the home network to apply different tariffs to national calls and short messages established/sent by their subscribers while roaming in their Home PLMN depending on whether or not the called subscriber's Home PLMN equals the calling subscriber's Home PLMN, rather than on the called subscriber's MSISDN;
+
+Note: This distinction is necessary only in the case, where the called subscriber's MSISDN may have been ported by Mobile Number Portability.
+
+- For circuit switched interconnection only a capability is required to collect information regarding user rate and user protocol at the interconnection point so that e.g. the identification of CS video telephony at the interconnection point for inter-network accounting purposes becomes possible.
+
+These new requirements and principles will allow users more freedom to obtain service when roaming, whilst providing effective cost and credit control for the Home Environment and User.
+
+## 4.1 Cross Phase Compatibility
+
+Where possible (e.g. services already defined within earlier releases), the charging information collected shall be consistent with the information already provided
+
+It is envisaged that 3GPP system will evolve beyond this Release with the addition of a number of new requirements for charging and billing, for example with the addition of a number of new requirements for charging and billing; these are noted in the appropriate sections below. The technical standards for each release should be developed in such a way that it is possible and practical to introduce these requirements, ideally in a backward compatible manner.
+
+Note: When a change is introduced which affects the 3GPP technical standards, it is said to be 'backward compatible' if existing equipment can continue to operate and perform correctly with equipment that conforms to the new implementation.
+
+## 4.2 Charging Entity Relationships
+
+In the process of introduction of the all-IP technology there will be a mixture of different types of entities using different types of technology.
+
+The diagram below shows the different entities involved in charging and their relationships.
+
+
+
+Diagram illustrating the types of entities and the relevant type of charging in a telecommunications network. The diagram is divided into four horizontal layers: 'Circuit-switched' Telecommunications Networks non-IP (top), IP based Telecommunications Networks (second layer), Gateways (third layer), and Content (bottom). A central 'Mobile Network Operator' (yellow oval) is connected to various entities across these layers. Charging types are indicated by arrows: 'Interconnect Charging' and 'Roaming Charging' with 'Fixed Operator' and 'Mobile Operators' in the non-IP layer; 'Usage Charging' and 'Conveyance Charging' with 'Fixed Operator' and 'Backbone e.g. GRX' in the IP layer; 'Usage Charging' and 'Roaming Charging' with 'I-WLAN Operator' and 'Mobile Operators' in the IP layer; 'Capacity Charging' with 'Internet'; 'Access Charging' with 'Portals' in the Gateways layer; and 'Supplier Charging' with 'Applications' and 'Information' in the Content layer. The 'Mobile Network Operator' also provides 'Wholesale Charging' to a '3rd Party Service Provider', which in turn provides 'Retail Charging' to 'User' entities.
+
+The types of entities and the relevant type of charging as shown on the diagram are as follows:
+
+- **Users:** retail charged by Mobile Network Operator or 3rd Party Service Provider.
+- **3rd Party Service Providers:** wholesale charged by Mobile Network Operator.
+- **Other telecommunications operators:** interconnect charging between Mobile Network Operator and non-IP "circuit-switched" Network Operators for call traffic carried; usage charging between Mobile Network Operator and IP-based Network Operators for session traffic carried.
+- **Other mobile operators:** roaming charging between these entities, this may require different mechanisms for IP-based types from the traditional "circuit-switched" types. Also, where mobile operators need to pass traffic to one another, there will be interconnect charging for non-IP "circuit switched" types; usage charging for IP-based types.
+- **I-WLAN operators:** where I-WLAN operators need to pass traffic to mobile operators or mobile operators to I-WLAN operators, there may be roaming and usage charging.
+- **IP backbone carriers:** conveyance charging Mobile Network Operators for traffic carried.
+- **3rd Party content & application suppliers:** supplier charging between Mobile Network Operators and Value Added Service Providers for information exchanged.
+- **3rd Party Portals:** access charging between Mobile Network Operators and this entity.
+- **Internet:** charge for capacity of connection between Mobile Network Operator and Internet. An Operator pays a provider for a connection based on capacity, e.g. annual charge for a 2Mbit/s "pipe".
+
+## 4.3 Charging guidelines for IP-Multimedia services
+
+### 4.3.1 User Charging Requirements
+
+This section describes the options required for the charging of end users. The network operator could charge users directly (retail charging) or charge a 3rd party service provider (wholesale charging). These requirements can therefore apply to retail and wholesale charging. Note that the word "session" is used to describe the connection between a user and either another user or a service. This term is used for IP connections rather than the term "call" that is normally used for a connection over conventional (circuit switched) systems.
+
+The various ways that users can establish sessions and the main components are described. Also, the required charging options are specified.
+
+#### 4.3.1.1 Session End Point Configurations
+
+A variety of different connection configurations are possible for IP multi-media independently of the components of the session being used. It should be possible to charge for the following types of sessions with the options identified. These charging options should be applicable to each medium separately. Note that not all the charging options need to be used and that some of the options can be used only if the particular party is using the resources of IMS:
+
+The table below lists some example session scenarios and describes some of the possible charging options for each scenario. The table does not list all possible session scenarios nor does it list all possible charging options for the scenarios. Rather, the intent of the table is to emphasize the numerous charging options that shall be supported by an IP Multimedia System due to the complexity of sessions possible. The charging options shall adequately account for all session resources used in order to enable the operators to apply flexible billing policies and to satisfy regional and/or national regulatory policies.
+
+In general, any session shall allow for the following charging options:
+
+- To apply the "Calling Party Pays" charging principle;
+- A 3rd party to be charged for all or part of the session;
+- Split charging between any of the parties, including 3rd parties;
+- Session setup and session resources to have different charging rules. Different rules would be applied for example, in a scenario where **A** calls an advertising number, say **B**. **B** could be a web-based toy advertisement number, for example. In this scenario, **A** could pay for the initiation fee (session setup), and **B** could pay for the session resource.
+- Any party can add another media to the current session in progress and any of the parties (not necessarily the one(s) being charged for the current session) can be charged for the additional media. For example, **A** calls **B** and **A** is paying for the audio; **B** adds a wireless video image to the call and pays for that portion. The individual resource set-up and usage should be separately identified. This supports the "Calling Party Pays" model;
+- During an active session, media types can change (e.g. audio changed to data) and shall be charged for appropriately. It is thus necessary to be able to detect a change of media during a session so that different rating may be applied.
+
+It should also be noted that during a multi-party session, normally if the charged party drops off the session, all components being charged to that party should drop. But it is foreseeable to support a service option that allows the charged party to continue to be charged even if they drop off the session. The charging rules should support this option.
+
+| No | CONNECTION | DESCRIPTION | CHARGING OPTIONS REQUIRED |
+|----|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | A sets up a session to B | A simple connection between 2 subscribers or a subscriber and a service (eg voicemail) | A pays for the session set-up to B
A pays for the session resource to B
B pays for the session resource to A |
+| 2 | A sets up a session to B | A simple connection where B is a "toll free" (800) type service | B pays for the session set-up
B pays for the session resource
A pays for part of the session resource (i.e. allowing split charging between A & B ) |
+| 3 | A requests session with B , B redirects to C | This is redirection. The connection path is not set up to B from A , instead A is told to set up a connection direct to C | A pays for the session set-up to B
A pays for the session resource to C
C pays for the session resource to A
A pays for the session resource as though it were to B and B pays for the session resource to C as though it came from B |
+| 4 | A requests session with B , B forwards to C | This is normal forwarding as in GSM. The connection path is A to B 's home network and B 's home network to C | A pays for the session set-up to B
A pays for the session resource as though it were to B and B pays for the session resource to C . |
+| 5 | A sets up sessions with multiple parties (Multi-party) | Connections to multiple parties are initiated by A | A pays for the set-up of each session
A pays for each of the sessions resource to each of the called parties
Each of the called parties pays for the session resource to A |
+| 6 | A has a multi-party session where the individual parties set up the session to A | The multiple parties in the session initiate the session to A | Each party pays for the session set-up to A
A pays for the session resource to the multiple parties
The individual parties in the session each pay for the session resource to A |
+| 7 | A is in a session with B , then puts B on hold to set up a session with C , then returns to B after dropping C | A still has a connection to B while also in a session with C . The session with B continues after the session with C is terminated | A pays for each of session set-ups to B and C
A pays for the session resource to B & C
B & C pay for the session resource to A |
+| 8 | A is in a session with B then answers a session request from C while keeping B on hold | A still has a connection to B while also in a session with C . The session with B continues after the session with C is terminated | A pays for the session set-up to B
C pays for the session set-up to A
A pays for the session resource to B and C
B & C pay for the session resource to A |
+| 9 | A sets up a session with B who is roaming in another network | The connection is made from A to B 's home network and then forwarded to B in the visited network. (Normal GSM mechanism)
Alternatively, A is redirected directly to B in the visited network | A pays for the session set-up to B
A pays for the session resource as though it were to B in his home network and B pays for the session resource from his home network to the visited network
A pays for the session resource to B in the visited network
B pays for the session resource to A |
+
+#### 4.3.1.2 Charging Principles For User Session Components
+
+A number of different components can comprise a session. These components may be added or dropped from an ongoing session by any participating party. These components should be individually identifiable for charging purposes.
+
+Generally, the party that adds a component should be responsible for the payment for the use of the component. However, it should also be possible to charge all users that need an increase in resource to handle the component. An example is 2 users in an audio session where one of the users upgrades the session to videophone session. Both users could be charged extra for the use of the video component as this requires extra resource at both ends.
+
+Possible components are:
+
+- Voice
+
+- Audio (real time)
+- Audio (streaming)
+- Video (real-time)
+- Video (streaming)
+- Data (download/upload)
+- Data interactive e.g. web browsing
+- Messaging (SMS text type)
+- E-mail
+- Data stream (unspecified content) This is where the network operator acts as a "bit-pipe"
+
+It shall be possible to charge for each of these components separately in a session with the options shown in the table below.
+
+It shall be possible for operators to be able to charge for individual components of sessions even if there is no identifiable service. For example, a proprietary codec may be used to set up an "end-to-end" speech session where the network operator acts as a "bit-pipe". In this case, it should be possible for the operator to charge for this differentially. This type of component is called "datastream" in the table below.
+
+It might not be possible to apply some of the charging mechanism and type options described below depending on the capability of the networks used.
+
+| COMPONENT | CHARGING MECHANISM OPTIONS | CHARGING TYPE OPTIONS |
+|-----------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Voice | Charging principles as described in section 4.3.1.1 | Charging by duration of session
Charging by QoS requested and/or delivered
One-off set-up charge |
+| Real time Audio and Video | Charging principles as described in section 4.3.1.1 | Charging by duration of session
Charging by QoS requested and/or delivered
One-off set-up charge |
+| Streaming Audio and Video | Charged to the initiator of the request
Charged to the sender of the audio or video | Charging by duration of session
Charging by volume of data, optionally QoS-differentiated
One-off set-up charge |
+| Data (upload or download) | Charged to the initiator of the request
Charged to the sender of the data | Charging by duration of session
Charging by volume of data, optionally QoS-differentiated
One-off set-up charge |
+| Interactive Data | Charged to the initiator of the session | Charging by duration of session
Charging by volume of data, optionally QoS-differentiated
One-off set-up charge |
+| Messaging (SMS text type) | Charged to the initiator of the message
Charged to the recipient of the message | Charging by event (e.g. like SMS)
Charging by volume of data |
+| Unspecified content (data stream) | Charged to the initiator of the session
Charged to all parties involved | Charging by duration of session
Charging by volume of data (sent & received), optionally QoS-differentiated
One-off set-up charge |
+
+#### 4.3.1.3 Other Charging Requirements
+
+The user will also be charged for additional activities while in a session, for example downloaded applications or
+
+information. The table below shows some of these requirements and the priority. [This section will need to be further developed.]
+
+| CHARGING REQUIREMENT | DESCRIPTION |
+|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Downloaded items | User is charged for a specific item downloaded eg a music file, video clip, application |
+| Location based services | User is charged for receiving information on his location (charging based on accuracy as an option). This could be a stand-alone location query or linked to another service |
+| Content accessed or downloaded | User is charged according to the value of the information. E.g. weather information, share price or other financial information |
+| M-Commerce | Electronic transactions to 3 rd party suppliers of goods & services |
+| Use of portal or other site | User is charged for any access to a portal or any other site. This could be a one-off charge or based on duration or data volume of the portal or site use |
+| APN and associated content | User is charged for access to a specific APN and for the content associated. Requirements are for further study. |
+| Actual duration of rendered service | User is charged (e.g. for premium rate services or hotline) based on the actual duration of the rendered service |
+
+### 4.3.2 Roaming Charging Requirements
+
+It shall be possible for a network operator to charge its users for activities while roaming. It shall be possible for a network operator to charge its users while roaming using the same principles used while on the home network. The ability to supply all the necessary information for all the charging options will depend on the capability of the visited network.
+
+In addition, the network operators have to charge each other for the use of their networks by roaming users. The methods of charging between operators may be different from the methods used to charge the user. For example, a user may be charged by duration for voice sessions made while roaming but the home network may pay the visited network by volume of data used. Based on preconfiguration or indication from the home network, the serving network may be aware that charging information per individual subscription is not needed. In that case the serving network may omit detailed collection of chargeable events per individual subscription and instead base roaming charging of the home network on optimised collection of chargeable events.
+
+Mechanisms used in today's networks may also be applied e.g. Inter-Operator Tariff (IOT).
+
+The table below shows the types of charging principle that networks will require for roaming settlement and a priority for its provision.
+
+| ITEM | CHARGING METHOD DESCRIPTION |
+|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Charging for session use | Sessions made by users while roaming charged according to the principles described in section 4.3.1.1, above. This includes duration and volume charging |
+| Downloaded items | Items downloaded by the user while roaming from providers associated with the visited network are charged back to the home network for onward charge to the user |
+| Location based services | Location information provided by the visited network is charged back to the home network for possible onward charge to the user. |
+| Content accessed or downloaded | Information that is accessed by the user while roaming from providers associated with the visited network is charged according to its value by the visited network back to the home network for onward charge to the user. |
+| M-Commerce | Charging requirements between visited and home networks for M-Commerce transactions made by a roaming user are for further study. |
+| Use of portal or other site | The visited network may charge the home network for any access by the roaming user to a local portal or any other local site. This could be a one-off charge and/or based on duration or data volume of the portal or site use |
+| APN & associated content | Charge by visited network to home network for access to a specific APN and for the content associated. Requirements are for further study. |
+
+### 4.3.3 Interconnect Charging Requirements
+
+This clause applies (but is not limited) to the following interconnection scenarios:
+
+- Interworking between two IMS-based networks
+- Interworking between IMS-based networks and PSTN/ISDN
+- Interworking between IMS-based networks and TISPAN NGN supporting PES
+- IMS transit scenario
+
+The following charging requirements principles and guidelines shall apply for IMS when interconnected to other systems:
+
+- Existing, legacy charging principles will need to be retained while there is a requirement to interwork with non-IP based "circuit switched" type of networks
+- All the charging and accounting information shall be collected as closest as possible to the interconnection point (subject to network element performance capabilities).
+- A session or a service instance shall be uniquely identified within a network domain to allow a correct accounting and charging.
+- The identities of the originating network and of the destination network shall be unique and transported at signalling layer. This applies also to transit scenarios.
+- The interconnecting provider(s) will be able to apply Inter Operator Tariff schemes both for offline and online charging.
+- Charging information will be available for recording at both ends of interconnected parties. The charging information shall be sufficient to enable inter operator accounting correlation and inter operator dispute resolution. When per individual subscription charging information from the other operator is not needed, interconnect charging may be based on optimised collection of chargeable events.
+- The real-time transfer of tariff information in interconnection scenarios shall be supported when the serving network supports it, in order to support value added services that are billed by the caller's operator (e.g. Premium rate services 0900 or hotlines).
+
+Note: Such services often appear as 3rd party services where the tariff information resides in the called network and the caller's operator does not have this information.
+
+- This tariff information must be submitted by the external provider in real-time, so that the caller's operator is capable of
+ - providing AoC (Advice of Charge) information to the caller.
+ - capturing the imported tariff information into charging records.
+
+The service-hosting network shall provide appropriate charging information to the caller's operator in a secure way, independently from the real-time transfer of charging information for AoC purposes.
+
+Note: Where required to support offline charging for third party services where the tariff information resides in the called network and the caller's operator needs to bill the end user for that service.
+
+### 4.3.4 Conveyance & Usage charging requirements
+
+It shall be possible for network operators (including mobile, fixed and IP backbone suppliers) to charge each other for the use of resources required to support user sessions. The items to be charged and the principles to be applied are described below.
+
+The methods of charging between operators could be different from the methods used to charge the user. For example, a user may be charged by duration for voice sessions but the mobile network may pay the fixed network or 3rd party carrier by volume of data used. When per individual subscription charging information from the other operator is not needed, conveyance and usage charging may be based on optimised collection of chargeable events.
+
+**Table 4.3.4-1: Conveyance & Usage charging requirements**
+
+| ITEM | CHARGING METHOD DESCRIPTION |
+|--------------------|---------------------------------------------------------------------------------------|
+| Session use | Charging according to the resources used by duration of session and/or by data volume |
+| Quality of Service | Charging by QoS delivered to and from the other network |
+
+### 4.3.5 Charging 3rd parties
+
+It shall be possible for network operators and 3rd parties to charge each other for the use of their resources. Third parties include content and application providers and portals.
+
+When per individual subscription charging information is not needed, 3rd party charging may be based on on optimised collection of chargeable events.
+
+The items that will be charged and the principles are described below:
+
+**Table 4.3.5-1: Charging 3rd parties**
+
+| ITEM | CHARGING METHOD DESCRIPTION |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Content accessed | The 3 rd party charges the end user (via the network operator) for content accessed/downloaded |
+| Access to site | The 3 rd party is charged by the network operator for each "hit" by its users |
+| Location information | The 3 rd party is charged by the network operator for information on the location of the user. Amount charged could depend on accuracy of location information. |
+| Presence information | The 3 rd party is charged by the network operator for presence information about the user. |
+| Pushed information | The 3 rd party is charged by the network operator for each message pushed to the user, e.g. advertisements |
+
+### 4.3.6 Advice of Charge (AoC)
+
+The Advice of Charge (AoC) supplementary service allows the served user to be informed of MMTel session related
+
+charging information.
+
+AoC information may occur as:
+
+- Advice of Charge for Information purposes (AoCI): This supplementary service provides the information to produce an estimate of the cost of the service used. This means that the displayed value and the cost of the service used (e.g. corresponding bill item) may differ.
+- Advice of Charge for Charging purposes (AoCC): This supplementary service provides the means by which the UE may indicate the charge that will be made for the use of MMTel service (i.e. the cost of the service used.)
+
+AoC-information may be sent to the served user at the following phases of communication:
+
+- Charging information at communication set-up time (AOC-S): When the AOC-S supplementary service is activated, the IMS shall provide the user with information about the charging rates at communication establishment. In addition, the IMS may inform the served user at the communication set-up time if a change in charging rates is to take place after the communication set-up.
+- Charging information during the communication (AOC-D): After the AOC-D supplementary service is activated, the IMS shall provide the user with charging information for a communication during the active phase of this communication. The supplied charging information shall be provided as a rate of communication service (e.g. costs per minute) or as a cumulative charge incurred so far for the communication (i.e. charges recorded from the start of the communication and until the moment the charging information is sent to the served user), or as charging units. When the call is released, the network shall send the recorded charges for the communication to the served user.
+- Charging information at the end of the communication (AOC-E): When the AOC-E supplementary service is activated, the network shall provide the served user with charging information indicating the recorded charges for a communication when this communication is released.
+
+Compatibility with existing, legacy AoC principles from both fixed and mobile networks shall be taken into account. This comprises (but is not limited to) the following requirements for AoC as specified in TS 22.086 [5], ETS 300 178 [6], ETS 300 179 [7], ETS 300 180 [8], TS 183 047 [9] and TS 183 058 [10].
+
+AoC shall be also supported for interconnection scenarios.
+
+### 4.3.7 Service Aware Charging Requirements
+
+Service Aware Charging provides the means to perform charging based on identified IMS communication service and the service in use.
+
+To facilitate service aware charging, the system shall support the possibility to identify the IMS communication service and the service in use in the charging and accounting data collection.
+
+To ensure that service aware charging can be provided when roaming, the home network shall have the possibility to provide the unequivocally identified IMS communication service to the visited network.
+
+## 4.4 Additional Charging requirements for prepay services
+
+A prepay service allows a subscriber to pay in advance for the use of specific services, the prepay account will be decreased each time the subscriber uses the services related to that account.
+
+In a multi-service environment like 3GPP system, a subscriber can have different prepay accounts for different kinds of services (e.g. internet access, m-commerce, infotainment, location-based services etc.).
+
+In order to guarantee the use of the prepay services, the following general requirements shall be fulfilled:
+
+- The prepay service shall check a subscriber's prepay account for coverage of the requested service charges prior to execution of that service.
+- All charging information related to a specific prepay account shall be prevented to the user when the prepay credit of that account is exhausted or expired.
+- All the ongoing charging information related to a specific prepay account shall be immediately (within a few
+
+seconds) interrupted as soon as the prepay credit of that account exhausts or expires.
+
+- The prepay service shall decrease the prepay account each time the subscriber uses the services related to that account.
+
+It should be possible to support more than one prepay account for a user if needed.
+
+To guarantee a meaningful multi-prepay account concept, at least 2 different prepay accounts should be supported.
+
+## 4.5 QoS and gating based on spending limit
+
+- When the subscriber spending limit has reached a pre-set limit, the system shall be able to trigger a QoS downgrade and/or restrict access to one, several or all IP services based on operator pre-defined thresholds.
+
+Note: A spending limit is the usage limit (e.g. monetary, volume, duration) that a subscriber is allowed to consume.
+
+- When the subscriber spending limit (e.g. monetary, volume, duration) has been increased, the system shall be able to modify resources (e.g. QoS, Bandwidth, access) to services accordingly.
+- The home network shall be able to enforce the subscriber spending limits for a roaming subscriber without having dedicated support of the feature in the visited network.
+- Additional signalling load should be minimized.
+
+## 4.6 ProSe Charging Requirements
+
+This section describes the requirements for collecting charging data for ProSe [13]. The requirements also apply in the roaming case.
+
+Online and offline charging shall be supported.
+
+The EPS shall be able to collect charging data for the ability to discover ProSe-enabled UEs served by the E-UTRAN of a different PLMN.
+
+The EPS shall be able to collect charging data for ProSe Discovery features including:
+
+- the ability of a ProSe-enabled UE to be discoverable, including based on the range class;
+- the ability to discover other ProSe-enabled UEs, including based on the range class;
+- the event of discovering a ProSe-enabled UE, including based on the range class;
+- the technology (e.g., E-UTRA or WLAN) that was used for ProSe Discovery.
+
+When a ProSe-enabled UE uses ProSe Communication, or EPC Path established following ProSe Discovery, the 3GPP System shall be able to collect charging data for this communication including its:
+
+- Activation/deactivation;
+- Initiation/termination;
+- Duration and amount of data transmitted / received;
+- QoS, if via E-UTRAN (e.g. levels of availability, allocated resource);
+- Inter-operator communication;
+- Inter-operator signalling;
+- Identification of UEs or groups involved.
+
+Note: This requirement applies to any ProSe E-UTRA Communication between two ProSe-enabled UEs, ProSe Group Communication, ProSe Broadcast Communication and ProSe-assisted WLAN direct communication.
+
+The EPS shall be able to collect charging data for use of ProSe Discovery, ProSe Communication and EPC Path established following ProSe Discovery by an application. This requirement applies to any ProSe E-UTRA Communication between two ProSe-enabled UEs, ProSe Group Communication, ProSe Broadcast Communication and ProSe-assisted WLAN direct communication.
+
+## 4.7 Unlicensed access requirements
+
+This section describes the requirements for collecting data for usage over unlicensed access. The requirements also apply in the roaming case.
+
+Data collected on usage over unlicensed access shall contain sufficient information for operating purpose (e.g., accounting, charging and charging and network planning).
+
+## 4.8 Charging Requirements for Indirect 3GPP Communication
+
+This section describes the requirements to enable operator collection of charging data for an Evolved ProSe Remote UE and Relay UE using an Indirect 3GPP Communication. The requirements also apply in the roaming case.
+
+Online and offline charging shall be supported whenever an Evolved ProSe Remote UE using a direct 3GPP communication or an Indirect 3GPP Communication.
+
+The 3GPP core network shall be able to provide charging information for an Evolved ProSe Remote UE using a direct 3GPP communication or an Indirect 3GPP Communication independently of charging data of the other UEs, with following information:
+
+- Initiation/termination;
+- Duration and amount of data transmitted / received;
+- QoS (e.g. levels of availability, allocated resource);
+- Inter-operator communication;
+- Inter-operator signalling;
+- Identification of UEs involved;
+- Identification of RAT involved;
+- Timestamp when the connection mode changes.
+
+The 3GPP core network shall be able to provide charging information for an Evolved ProSe Relay UE using a direct 3GPP communication or an Indirect 3GPP Communication independently of charging data of the other UEs, with following information:
+
+- Identification of remote UEs involved;
+- Initiation/termination;
+- Duration and amount of data transmitted / received;
+- QoS (e.g. levels of availability, allocated resource);
+- Inter-operator communication;
+- Inter-operator signalling;
+- Identification of RAT involved;
+- Timestamp when the connection mode changes.
+
+The 3GPP core network shall be able to collect charging data for an Evolved ProSe Remote UE which accesses the 3GPP core network through an Indirect 3GPP Communication.
+
+The 3GPP core network shall be able to identify the relayed traffic of an Evolved ProSe UE-to-network Relay, e.g. to be
+
+able to apply different rating.
+
+# --- 5 Collection of charging information
+
+The standard shall support the collection and transfer of charging information in order to facilitate:
+
+- interworking with Release 98 and earlier releases
+- fraud management procedures;
+- unsuccessful calls and sessions documentation (e.g. for billing purposes);
+
+Note: collection of charging information due to error in the signalling flows (e.g. incomplete or erroneous call setup) are not required;
+
+- detailed itemised billing
+- allow for prepay charging
+
+Generally, the charging information collected shall support the high level principles in section 4 (above) and the requirements identified for inter-operator charging as elaborated by the GSM Association. The information listed below is the minimum requirement.
+
+## 5.1 Charging information Requirements
+
+Charging information shall be collected in the Serving Network to record chargeable User or Mobile Station activity and inter-carrier connections. Some of the information is provided by the user, other information is only available in the network element of the serving network.
+
+Depending on the type of charging information some of the data may not be available or might not be required.
+
+### 5.1.1 Information provided by the user
+
+The user's user equipment that is incurring the charge shall provide the following information to the serving network:
+
+- User identity used for authentication;
+- Home environment identity;
+- Terminal Identity and Terminal Class;
+- Destination endpoint identifier for service requested (e.g. B number);
+- Resource requested (e.g. bandwidth, connectionless);
+- QoS parameters (e.g. maximum delay);
+- IP Multimedia capability requested (e.g. media components).
+
+### 5.1.2 Information provided by the serving network
+
+The network serving the user shall provide the following information to the home environment:
+
+- All of the information listed in section above (Information provided by the user);
+- Serving network identity;
+- Recording network element identity;
+- Universal Time (UT) at which the service request was initiated;
+- Universal Time (UT) at which resources were provided for the service;
+
+- Universal Time (UT) at which the service execution was successfully completed;
+- Universal Time (UT) at which the service execution was unsuccessfully completed;
+- Local time of the serving cell when the service request was initiated for the originating or terminating UE. This could either be explicitly reported, or implicitly reported by providing three pieces of information: the UTC, the time zone offset from UTC, and an indication of daylight savings time;
+- Cause for unsuccessful completion of the service execution. At least the following causes shall be included:
+ - the terminating party does not respond;
+ - communication rejected by the terminating party;
+ - network determined terminating party busy;
+ - network congestion;
+ - terminating party non reachable (out of coverage, switched-off);
+ - destination non reachable (non active address, non-existing address).
+- Resource allocated to the user;
+- Quantity of data transferred both to and from the user;
+- QoS provided to the user;
+- Location of the user in the standard format used for 3GPP location-based services (e.g. geographical co-ordinates, Cell ID);
+- Network determined PLMN ID and Cell ID;
+- whether GSM Optimal Routing was applied;
+- If IN or CAMEL services were applied, the service parameters and the actually used destination number and calling party number identification;
+- Time duration covered by this charging information to an accuracy of at least 1 second;
+- Unique identity of the chargeable event which allows the billing system to correlate all charging information belonging to the same chargeable event;
+- Unique charging information identity (unique per network element in a period of about 100 days);
+- IP Multimedia capability provided to the user;
+- VAS information;
+- Identifier of third party accessed by the user;
+- Presence Information;
+- Service Identification (e.g. voice call, video call, data download etc);
+- Supplementary Services used;
+- Prepay account identifier and related information.
+
+### 5.1.3 Charged Party
+
+For subscription related chargeable events the charging information shall indicate the charged party, i.e. normally the calling party. As alternative it should be possible to apply reverse charging or to charge the event to a party not involved in the event itself (e.g. a company as VPN subscriber). It should be possible for multiple leg calls (e.g. forwarded, conference or roamed) to be charged to each party as if each leg was separately initiated. However, in certain types of call, the originating party may wish/be obliged to pay for other legs (e.g. SMS MO may also pay for the MT leg.).
+
+It shall be possible to change the chargeable party at the session set-up or during the session.
+
+The 3GPP Packet Core network shall allow the 3rd party service provider to request which of the subscriber or the 3rd party service provider (e.g. the sponsor) has to be charged for an ongoing traffic flow in order to allow:
+
+- The subscriber to be charged for the traffic flow,
+- The 3rd party service provider to be charged for the traffic flow.
+
+NOTE: The change of the charged party (sponsor pays or user pays for this traffic flow) only applies from the time of the request.
+
+In case of inter-network chargeable events, the charging information usually does not contain the charged party, but it can be derived from network configuration information contained in the charging event data.
+
+For each party to be charged for a chargeable event or parts of it charging information shall be collected.
+
+### 5.1.4 Information provided by the third party accessed by the user
+
+Supply of Value-Added Services, especially in IP based environment, is often made with the aid of third parties typically represented by portals and content/application providers.
+
+To execute an effective charging of these services, the following charging information should be provided by the third party:
+
+- Third party identity;
+- Type of service (information, entertainment, gaming, public utility);
+- Change in the type of service provided to the user;
+- Type of content (picture, videoclip, mp3 file, java file);
+- Universal Time (UT) at which the service request was initiated;
+- If a service change happens, Universal Time (UT) at which the service provision was initiated;
+- Universal Time (UT) at which the service execution was successfully completed;
+- Universal Time (UT) at which the service execution was unsuccessfully completed;
+- Cause for unsuccessful completion of the service execution. At least the following causes shall be included:
+ - the terminating party does not respond;
+ - communication rejected by the terminating party;
+ - network determined terminating party busy;
+ - network congestion;
+ - terminating party non reachable (out of coverage, switched-off);
+ - destination non reachable (non active address, non-existing address).
+- Cause for Abnormal reject of the service;
+- Universal Time (UT) for abnormal reject of the service
+
+## 5.2 Special Cases
+
+### 5.2.1 Long calls and sessions
+
+The advent of packet data services, which can extend for very long periods of time (days, weeks etc), although at low cost because charges are based on data throughput, may mean that charging information are only output at the end of
+
+very long periods. For this reason, the serving network shall support the transmission of charging information also during the life of the packet data session, either when some charge value is reached or some duration or some data volume or all three, to allow for both charging settlement and cost control.
+
+### 5.2.2 Multimedia calls
+
+During one call the user may invoke different services like speech, data transmission, video and audio, which may lead to a separate collection of charging information for each service in different network components. In this case, the billing system shall be able to correlate this charging information and to indicate to the user that they belonged to one call.
+
+### 5.2.3 Service Change
+
+Sufficient information about a service change using SCUDIF changing a voice call to a CS multimedia call, or vice versa, shall be collected to enable operators to apply maximum flexibility in charging. This information is collected on top of the data that is already available for the underlying call now subject for the service change.
+
+On a service change using SCUDIF the following information shall be collected on both sides of the call:
+
+- 1) Initiator of the service change (A side or B side)
+- 2) Type of the service change (To speech or to multimedia)
+- 3) For a service change to multimedia: nature of the service change (User or network-initiated service change)
+
+### 5.2.4 E-Commerce
+
+The 3GPP system may be used to trade soft goods (e.g. information, video, audio), or hard goods (e.g. books) of high or low value per item between the user and a merchant. It shall be possible for such merchants to charge users directly for services they provide. Electronic payment mechanisms are or shall be made available through other standards (micropayment, credit card payment, etc), and therefore are outside the scope of this specification 3GPP shall not prohibit the use of these mechanisms, and, where possible, shall provide the basic communications transport to allow them to be used effectively.
+
+However, if the serving network acts as merchant of soft goods, it may charge the user directly, collecting the related charging information as described above or using micropayment mechanisms.
+
+### 5.2.5 Volume Based Charging
+
+It shall be possible to charge for the total volume of data/packets sent and received by the user.
+
+### 5.2.6 VAS
+
+It shall be possible to charge the user for Value Added Services offered by the network in terms of access, surfing, queries etc. irrespectively of the volume of data sent or received by the user.
+
+### 5.2.7 Usage of IP Multimedia service
+
+It shall be possible to charge the usage of IP multimedia service independently of the volume of data sent or received by the user. Information on the IP Multimedia capability provided to the user (e.g. voice, mixture of voice and video component, numbers of parties) should be available in the charging information.
+
+### 5.2.8 I- WLAN
+
+I-WLAN charging issues are captured in 3GPP TS 22.234 [3].
+
+### 5.2.9 Charging for two (and multi)-phases services for IMS networks
+
+It shall be possible to charge a service change in case of VAS that foresee different service phases at different tariffs.
+
+This applies both at the interconnection between IMS network operators and at the interconnection between IMS network operators and service providers.
+
+This information is collected on top of the data that is already available for the underlying communication now subject for the service change.
+
+### 5.2.10 CSG charging requirements for UTRAN and E-UTRAN
+
+Detailed requirements for CSG access may be found in 3GPP TS 22.220 [12].
+
+Charging related requirements:
+
+- It shall be possible to charge subscribers for consuming network services via a CSG cell based on the following information:
+ - CSG identity of the CSG cell
+ - subscriber membership of the CSG
+ - type of service consumed by the subscriber
+ - addition to and deletion from a CSG
+- An operator shall be able to provide applicable tariffing information when a subscriber is added to a CSG.
+- The network operator shall be able to charge both on-line and off-line for subscribers consuming network services via a CSG cell.
+
+### 5.2.11 Inter-UE Transfer charging
+
+It shall be possible to charge for Inter-UE Transfer (i.e. transfer/replication/sharing) of media components across multiple IMS UEs.
+
+### 5.2.12 Selected IP Traffic Offload charging
+
+The network shall be able to apply volume-base charging to a subscriber regardless of whether the subscriber's traffic has been offloaded from the mobile operator's network as described in 3GPP TS 22.101 [1].
+
+For subscribers' traffic offloaded from the mobile operator network, the network shall be able to apply either online or offline charging.
+
+### 5.2.12A Charging requirements for IoT small data
+
+Requirements for IoT resource efficiency for small data transmission can be found in 3GPP TS 22.278 [13].
+
+The 3GPP system shall be able to record charging data for both IP data and non-IP data to/from a UE.
+
+The 3GPP system shall be able to record charging data for user plane transfer of small data messages.
+
+The 3GPP system shall be able to record charging data for offline charging for control plane transfer of small data messages. At least the following data shall be recorded:
+
+- Non-IP data delivery submission requests in mobile originated and mobile terminated direction;
+- Data volume per submission request
+- Destination and source information
+
+### 5.2.13 TV Service Support Requirements
+
+The 3GPP network shall be able to generate accounting data for TV transport service.
+
+### 5.2.14 Charging for Flexible Mobile Service Steering
+
+The 3GPP core network shall be able to generate charging information to support accounting between operator and the third party service provider when operators use traffic steering policies to steer traffic to appropriate enablers which are deployed by the third party service provider in (S)Gi-LAN as described in 3GPP TS 22.101 [1].
+
+For service functions which are provided by the operator and the chain of service functions as requested by the third-party service providers, the enhancement of charging aspects is indicated in 3GPP TS 22.261 [14].
+
+### 5.2.15 Restricted local operator services
+
+The description of restricted local operator services is contained in 3GPP TS 22.101 [1].
+
+The 3GPP network shall be able to collect charging information regarding the use of restricted local operator services, when available.
+
+### 5.2.16 Charging for streaming services
+
+Charging information shall identify whether the streaming service as defined in [13] was provided in real time or using delay tolerant delivery.
+
+The 3GPP system shall be able to generate and collect the charging data (e.g. the duration of streaming service, the amount of data transferred) for local streaming service.
+
+In case of caching of content on a UE, charging information shall be generated when the cached content is consumed by the user.
+
+### 5.2.17 User Identity
+
+The description of User Identification is contained in 3GPP TS 22.101 [1].
+
+The 3GPP system shall be able to include the User Identifier including information concerning the provider of the User Identifier in the charging data for on- and offline charging.
+
+The 3GPP system shall be able to record charging data for user authentication.
+
+The 3GPP system shall be able to create charging data containing the User Identifier and the subscription to which it is linked for access and use of network services by a non-3GPP device that was authorized with its User Identifier linked to a subscription.
+
+# --- 6 Transfer of Charging Information
+
+The efficient transfer of charging information between serving networks and from serving networks to home environments requires a standardised interface between these entities. It shall be possible to define different time intervals for the transfer of charging information between serving network and home environment (e.g. when a chargeable event occurs, when a chargeable event is initiated by the user, when a chargeable event terminates, at regular intervals during a chargeable event).
+
+The format of the charging information exchanged (see 5.1) shall be standardised. It shall be possible for the relevant parties to agree minimum and maximum age of charging information transferred between themselves.
+
+## 6.1 Integrity, Secrecy and Validation of Content and Receipt of Charging Information
+
+The transmission mechanism for charging information collected in 5.1 above shall ensure its integrity and secrecy.
+
+A mechanism to validate the source and integrity of the information shall be provided so that:
+
+- the home environment shall be able to validate the source and integrity of the charging information supplied by
+
+the serving network;
+
+- the serving network shall be able to validate the source and integrity of the charging information supplied by the user;
+- the serving network shall have proof that services were provided to a specified user.
+
+# --- 7 Accounting and Settlement
+
+The serving network shall collect and process the charging data generated in its network elements. The record of each individual transaction shall be reported to the home environment at short time intervals in order to allow further processing by the billing system in the Home Environment, provide itemised bills, and to deal with any disputes regarding charges both for users and for other visited networks and home environment.
+
+The standard shall support the transfer of charging data at different intervals as required by the Home Environment (e.g. short time intervals, real time, other regular intervals).
+
+## 7.1 Delegation of charging authority
+
+The registration process allows the home environment to authenticate users before they incur any charges. Once authenticated, the home environment then delegates authority to the serving network operator with which he has a direct commercial relationship to incur charges for services supplied to that user. The direct commercial relationship may be with either the serving network operator if known directly by the home environment or a network operator known to the home environment. This procedure uses each network as trusted third parties in a chain of delegation between entities, thus allowing commercial transactions between entities who have no direct commercial dealings. There shall be an authentication procedure between all entities in the 3GPP system which have a commercial relationship.
+
+In the case of a multimedia telephony, when the HPLMN requests that optimal media routeing is not applied, the VPLMN shall disable optimal media routeing for all the subscribers of the requesting network.
+
+## 7.2 Fraud Control
+
+A mechanism to control fraud shall be provided by the serving networks and the home environment.
+
+### 7.2.1 Fraud Control by the Home Environment
+
+Charging information shall be collected by the home environment in real time from all serving networks which its users are allowed to use. The billing system in the home environment shall process the information in real time and provide the means to set charge thresholds per time interval upon which some actions may be started, such as informing the customer care centre or even barring the user in the HLR.
+
+It shall be possible for the Home Environment to define different time intervals for the collection and the processing of charging information (e.g. real time, short time, other regular intervals).
+
+### 7.2.2 Fraud Control by the Serving Network
+
+Charging information shall be collected from the network elements and processed in real time. This will allow the serving network to always be aware of the exposure to visitors. A limit for the accumulated charges for all visitors from one home environment or a limit per visitor may be agreed between the home environment and the serving network.
+
+It shall be possible for the Serving Network to define different time intervals for the collection and the processing of charging information (e.g. real time, short time, other regular intervals).
+
+## 7.3 Cost Control
+
+A mechanism shall be standardised providing an indication to the user (if involved in the chargeable event) of the charges to be levied for a chargeable event. This mechanism shall be able to handle all possible charging scenarios, and
+
+all service and tariff variants that the home environment and the serving network may offer to the user.
+
+The user shall be able to set in his home environment a limit for the accumulated charges per time interval. Upon exceeding this limit or prior to incurring a charge which would exceed the limit, certain actions may be desired by the user:
+
+- notification to the user, requesting to extend the limit; or
+- Home Environment barring allowing no further originating calls; or
+- Home Environment barring cancelling the roaming permission.
+
+### 7.3.1 Cross Phase Compatibility
+
+For Release 99 the cost control mechanism may be based on Advice of Charge. However the Release 99 standards should not prevent the future implementation of the full Cost Control requirements.
+
+The Release 99 standards should allow these new features to be introduced in a backward compatible manner; specifically terminals conforming to Release 99 standards should continue to support the Release 99 service requirements when operating with future implementations of Advice of Charge in the Home Environment.
+
+## 7.4 Inter-network Settlement
+
+Mechanisms shall also be provided to allow inter-network settlement of charges on a bulk basis. The same mechanisms shall be used between home environments and serving networks. This will allow each of these parties to meter the total input and output of charges and thus determine the payments required on a periodic basis between each of the parties with which they directly interact. The mechanisms used shall allow each of the parties to meter charge flows independently, with the aim of matching the values recorded at both sides of the same interface. The imbalance in charge flow shall be accumulated in short time, such that each entity can be informed when a threshold has been exceeded and determine whether to continue.
+
+# --- 8 Automatic Roaming Agreements
+
+Support for the requirements in this section is not required in Release 99. However the Release 99 standards should not prevent the future implementation of this requirement in a backward compatible manner (e.g. a roaming broker enabled Home Environment should inter-operate with a R99 Serving Network).
+
+It is a requirement that users shall be able to obtain service and use chargeable services with networks with whom neither they nor their home environment have any direct commercial agreement. This shall be enabled by interworking via trusted third parties. Each Home Environment shall interwork with one or more serving network operators, with whom they would negotiate a commercial roaming agreement and test the interworking. Any user wishing to use the services of a particular serving network would register with that serving network, that would either directly or indirectly interwork with the home environment. Fraud and cost control mechanisms shall be used to ensure that charges incurred for 3GPP services do not exceed the credit limits set. This can be applied for the user and the other roles involved in commercial dealings. In practice, any serving network shall be capable of operating as a roaming broker.
+
+
+
+```
+sequenceDiagram
+ participant User
+ participant SNO as Servina Network Operator
+ participant RB as Roaming Broker
+ participant HE as Home Environment
+
+ Note left of SNO: Registration Request
+ SNO->>HE: Registration Request
+ HE-->>SNO: Authorisation
+ SNO-->>HE: Online Sianallina Information
+ SNO-->>HE: Call Detail Records
+```
+
+The diagram illustrates the registration and roaming process. It features four entities: User, Servina Network Operator, Roaming Broker, and Home Environment. The process begins with a 'Registration Request' sent from the Servina Network Operator to the Home Environment. The Home Environment responds with 'Authorisation' back to the Servina Network Operator. The Servina Network Operator then sends 'Online Sianallina Information' and 'Call Detail Records' to the Home Environment. The User is connected to the Servina Network Operator, which is connected to the Roaming Broker, which is connected to the Home Environment.
+
+Figure 1: Registration and Roaming Process. A sequence diagram showing interactions between User, Servina Network Operator, Roaming Broker, and Home Environment.
+
+Figure 1: Registration and Roaming Process
+
+## 8.1 Routing the Registration Request
+
+The same mechanisms used for routing calls and resolving addresses shall be used to route the subscription identity back to its Home Environment. The standard shall support a routing identification mechanism to allow a serving network, which does not maintain its own list of all known HE, to determine the appropriate route to reach a given HE. A number of alternative routes may be possible, and ideally the system should be capable of determining the lowest cost to the end user.
+
+Typically, smaller networks will only have a limited number of external connections to other networks or clearing houses, but may not know which one to use for an unknown (new) HE. In this case, the serving network may make a number of inquiries for each route to determine the lowest cost route to handle the call.
+
+## 8.2 Settlement of charges
+
+Settlement of charges incurred by a user shall be on a wholesale basis between the different parties involved in the registration link. By authorising a user to register, or a roaming broker to pass that on, each party is in turn authorising charges up to a maximum credit limit with the adjacent party. Any charges levied can then be paid to the adjacent party on a wholesale basis at the end of a mutually agreed accounting period. Funds are thus passed between each party for the services supplied by the network operator in a serial fashion.
+
+# Annex A (informative): Change history
+
+| Document information | | |
+|----------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Date | Status | Comment |
+| 27 August 1996 | Version 0.0.1 | SMG 1 WPC output draft for editing purposes only |
+| 3 February 1997 | Version 0.0.3 | Presented to SMG1 WPC meeting, London
Incorporated changes agreed at Dec 96 Meeting including charging model and charge enquiry |
+| 20 April 1997 | Version 0.0.4 | Presented to SMG1 WPC meeting in Sophia Antipolis
Incorporated text submitted at Feb 97 meeting |
+| 4 June 1997 | Version 1.0.0 | Proposed Version 1 incorporating changes discussed at SMG1 WPC meeting in Antwerps, June 97 |
+| 23 June 1997 | Version 1.0.2 | Incorporated remaining changes discussed at SMG1 WPC meeting in Antwerps, June 97 |
+| 27 Nov 1997 | Version 1.1.0 | Preparation for SMG1 UMTS Helsinki meeting, incorporating text from reports 22.24 and 22.71 |
+| 4 Dec 1997 | Version 1.2.0 | Incorporated comments from 22.24, 22.71 developed at SMG1 UMTS Meeting in Helsinki |
+| 26 April 1999 | Version 3.1.0 | |
+| 8 Dec 1997 | Version 1.2.2 | Format and editorial changes by ETSI Sec for SMG#24 |
+| 5 November 1998 | Version 1.3.0 | Incorporate changes discussed at SMG1 Rome, including reflecting changes to 22.01 role model. |
+| 12 January 1999 | Version 1.3.1 | Accept Changes and send to editing SMG1 Rome Tdoc 98-0859 Agreed by correspondence. Reviewed by Rapporteur Jan 13, 1999 |
+| 27 January 1999 | Version 2.0.0 | To be presented at SMG#28 for Approval |
+| February 1999 | Version 3.0.0 | Approved at SMG#28 |
+| March 1999 | Version 3.0.1 | Reformatted for TSG SA |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|---------------------------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SMG#28 | | | 22.115 | | | | | Version 3.0.0 Approved | | 3.0.0 | |
+| SP-03 | SP-99106 | S1-99234 | 22.115 | A001 | 1 | R99 | F | Clarification of the Charging Service | 3.0.0 | 3.1.0 | |
+| SP-05 | SP-99454 | S1-99817 | 22.115 | 002 | | R99 | D | clarify the mandatory features supported by the standard | 3.1.0 | 3.2.0 | |
+| SP-05 | SP-99454 | S1-99762 | 22.115 | 003 | | R99 | B | Addition of Charging for Volume of Data and some edits | 3.1.0 | 3.2.0 | |
+| SP-07 | SP-000066 | S1-000171 | 22.115 | 004 | | R99 | D | Clarifications to 22.115 | 3.2.0 | 3.3.0 | |
+| SP-11 | SP-010065 | S1-010258 | 22.115 | | | Rel-4 | | Creation of Release 4 | 3.3.0 | 4.0.0 | |
+| SP-11 | SP-010058 | S1-010192 | 22.115 | 005 | | Rel-5 | B | Introduction of charging for IPMultimedia and Event Based Charging | 3.3.0 | 5.0.0 | IMS-OAM |
+| SP-12 | SP-010260 | S1-010572 | 22.115 | 006 | | Rel-5 | B | Introduction of online charging for prepaid services | 5.0.0 | 5.1.0 | PRPY |
+| SP-15 | SP-020053 | S1-020643 | 22.115 | 007 | | Rel-5 | B | CR 22.115 Charging and billing
Some latitude was given by SA #15 to MCC to ensure that section numbering of original sections did not change. | 5.1.0 | 5.2.0 | OAM-CH |
+| SP-19 | SP-030023 | S1-030184 | 22.115 | 008 | - | Rel-6 | B | CR to TS 22.115 - Clarification of the charging entity WLAN | 5.2.0 | 6.0.0 | WLAN-CR |
+| SP-19 | SP-030035 | S1-030270 | 22.115 | 009 | - | Rel-6 | B | Requirements for Network Sharing in Rel-6 | 5.2.0 | 6.0.0 | NTShar-CR |
+| SP-20 | SP-030263 | N4-030449 | 22.115 | 013 | 1 | Rel-6 | A | Charging Requirements in an MNP environment | 6.0.0 | 6.1.0 | TEI |
+| SP-21 | SP-030467 | S1-030764 | 22.115 | 014 | - | Rel-6 | D | Alignment of 22.115 with 21.801 | 6.1.0 | 6.2.0 | TEI-6 |
+| SP-21 | SP-030467 | S1-030976 | 22.115 | 015 | - | Rel-6 | B | CS interconnection requirement for the identification of user data rate and user protocol at the interconnection point for charging purposes | 6.1.0 | 6.2.0 | TEI-6 |
+| SP-22 | SP-030701 | S1-031296 | 22.115 | 016 | - | Rel-6 | F | CR on 22.115: CS interconnection correction of an improper statement on the requirement for the identification of user data rate and user protocol at the interconnection point e.g. for inter-network | 6.2.0 | 6.3.0 | TEI-6 |
+| SP-23 | SP-040101 | S1-040259 | 22.115 | 020 | - | Rel-6 | D | Extraction of redundant WLAN charging information – now in WLAN TS22.234 | 6.3.0 | 6.4.0 | WLAN |
+| SP-29 | SP-050621 | | 22.115 | 0021 | 2 | Rel-6 | F | Clarification of Charging Implications of SCUDIF | 6.4.0 | 6.5.0 | CS video and voice improvements |
+| SP-30 | SP-050808 | - | 22.115 | 0022 | 2 | Rel-6 | F | Clarification of Charging Implications of SCUDIF | 6.5.0 | 6.6.0 | CS_VSS |
+| SP-31 | SP-060203 | - | 22.115 | 0023 | 3 | Rel-6 | F | Making charging principles also applicable to prepay services | 6.6.0 | 6.7.0 | TEI6 |
+| SP-33 | - | - | 22.115 | - | - | Rel-7 | - | Produced as a result of the implementation of Rel-8 CR 0024 and 0025 to Rel-6 | 6.7.0 | 7.0.0 | - |
+| SP-33 | SP-060483 | S1-060963 | 22.115 | 0024 | - | Rel-8 | B | Local Charging Zone Concept | 7.0.0 | 8.0.0 | LCZR |
+| SP-33 | SP-060483 | S1-060962 | 22.115 | 0025 | - | Rel-8 | B | Local Charging Zone Requirements | 7.0.0 | 8.0.0 | LCZR |
+| SP-37 | SP-070567 | S1071093 | 22.115 | 30 | 1 | Rel-8 | A | Correction for incomplete text on Universal Time (UT) at which resources were provided for the service | 8.0.0 | 8.1.0 | TEI8 |
+| SP-38 | SP-070845 | S1-071784 | 22.115 | 0036 | 1 | Rel-8 | C | Inclusion of fixed operator in interconnection charging requirements | 8.1.0 | 8.2.0 | CIMS8-TIS |
+| SP-38 | SP-070845 | S1-071785 | 22.115 | 0034 | 2 | Rel-8 | B | TISPAN charging requirements | 8.1.0 | 8.2.0 | CIMS8-TIS |
+| SP-38 | SP-070857 | S1-071933 | 22.115 | 0035 | 2 | Rel-8 | B | Charging Requirements for | 8.1.0 | 8.2.0 | TEI8 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|---------------------------------------------------------------------------------------------------------------------------|--------|--------|---------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| | | | | | | | | Unsuccessful sessions and calls | | | |
+| SP-38 | SP-070863 | S1-071929 | 22.115 | 0037 | 3 | Rel-8 | B | Charging for two-phases services | 8.1.0 | 8.2.0 | CHRG2P H |
+| SP-39 | SP-080031 | S1-080252 | 22.115 | 0038 | 2 | Rel-8 | F | Advice of Charge (AoC) requirements | 8.2.0 | 8.3.0 | CIMS8-TIS |
+| SP-39 | SP-080034 | S1-080332 | 22.115 | 0039 | 3 | Rel-8 | B | HNB/HeNB - Closed Subscriber Group (CSG) charging for UTRA and E-UTRA | 8.2.0 | 8.3.0 | HomeNB |
+| SP-39 | SP-080192 | - | 22.115 | 0040 | 2 | Rel-8 | F | Correction of charging requirement for multi-phase services | 8.2.0 | 8.3.0 | CHRGMP H |
+| SP-43 | SP-090195 | S1-090332 | 22.115 | 0044 | - | Rel-9 | B | HNB/HeNB Charging Requirements | 8.3.0 | 9.0.0 | EHNB |
+| SP-45 | SP-090652 | S1-093360 | 22.115 | 0047 | 1 | Rel-10 | B | Charging requirements for replication and sharing of multi-media session across multiple IMS UEs | 9.0.0 | 10.0.0 | eIMS_SC C-IDT |
+| SP-46 | SP-090849 | S1-094309 | 22.115 | 0048 | 1 | Rel-10 | B | Charging aspects for Selected IP Traffic Offload | 10.0.0 | 10.1.0 | LIPA_SIP TO |
+| SP-49 | SP-100583 | S1-102391 | 22.115 | 0053 | 2 | Rel-11 | B | Charging considerations for MMTel when Optimal Media Routing is used | 10.1.0 | 11.0.0 | OSCAR |
+| SP-49 | SP-100584 | S1-102394 | 22.115 | 0054 | 1 | Rel-11 | B | QoS and gating based on spending limit | 10.1.0 | 11.0.0 | QoS_SSL |
+| SP-50 | SP-100800 | S1-103229 | 22.115 | 0055 | 1 | Rel-11 | B | Clarification of Subscriber Spending Limit | 11.0.0 | 11.1.0 | QoS_SSL |
+| SP-50 | SP-100804 | S1-103232 | 22.115 | 0056 | 3 | Rel-11 | B | Clarification of location requirement | 11.0.0 | 11.1.0 | NWK-PL2IMS |
+| - | | | | | | | | LTE logo changed to LTE Advanced logo | 11.1.0 | 11.1.1 | - |
+| SP-51 | SP-110171 | S1-110325 | 22.115 | 0057 | 2 | Rel-11 | B | Addition of additional network provided time information for IMS charging | 11.1.0 | 11.2.0 | NWK-PL2IMS |
+| SP-52 | SP-110379 | S1-111067 | 22.115 | 0058 | - | Rel-11 | B | Charging clarifications for INIPUI | 11.2.0 | 11.3.0 | INPUI |
+| SP-53 | SP-110582 | S1-112398 | 22.115 | 0059 | 2 | Rel-11 | C | SIPTO Terminology and Charging requirements Update | 11.3.0 | 11.4.0 | TEI11 |
+| SP-54 | SP-110813 | S1-113448 | 22.115 | 0061 | 3 | Rel-11 | B | Clarification of service based charging | 11.4.0 | 11.5.0 | TEI11 |
+| SP-57 | SP-120522 | S1-122038 | 22.115 | 0066 | - | Rel-11 | B | Removal of INIPUI Charging Requirements from Rel-11 | 11.5.0 | 11.6.0 | INPUI |
+| SP-59 | SP-130116 | S1-131311 | 22.115 | 0067 | 4 | Rel-12 | B | Add charging requirements | 11.6.0 | 12.0.0 | ProSe |
+| SP-60 | SP-130315 | S1-133260 | 22.115 | 0070 | 1 | Rel-12 | F | Charging for the use of EPC Path in ProSe | 12.0.0 | 12.1.0 | ProSe |
+| SP-60 | SP-130315 | S1-133307 | 22.115 | 0068 | 3 | Rel-12 | F | Broadening of ProSe Communication Definition to include ProSe Group and ProSe Broadcast Communications for Public Safety. | 12.0.0 | 12.1.0 | ProSe |
+| SP-61 | SP-130412 | S1-134012 | 22.115 | 0071 | - | Rel-12 | D | Removing duplicate ProSe definitions | 12.1.0 | 12.2.0 | ProSe |
+| SP-62 | SP-130594 | S1-135307 | 22.115 | 0072 | 2 | Rel-13 | B | Bulk charging records for roaming, interconnect, conveyance and usage charging, and charging to third parties | 12.2.0 | 13.0.0 | SRMMTC |
+| SP-65 | SP-140501 | S1-143605 | 22.115 | 0073 | 5 | Rel-13 | B | Exposure of charging to 3rd party | 13.0.0 | 13.1.0 | SEES |
+| SP-66 | SP-140752 | S1-144608 | 22.115 | 0074 | 3 | Rel-13 | F | Clarifications of charging to 3rd party | 13.1.0 | 13.2.0 | SEES |
+| SP-67 | SP-150038 | S1-150301 | 22.115 | 0077 | - | Rel-13 | A | Alignment of ProSe communication charging data requirements | 13.2.0 | 13.3.0 | ProSe |
+| SP-71 | SP-160110 | S1-160339 | 22.115 | 0079 | 1 | Rel-14 | B | Accounting requirement for TV transport service support | 13.3.0 | 14.0.0 | EnTV |
+| SP-71 | SP-160116 | S1-160542 | 22.115 | 0080 | 1 | Rel-14 | B | Accounting for usage when using unlicensed access networks | 13.3.0 | 14.0.0 | USOS |
+| SP-71 | SP-160114 | S1-160543 | 22.115 | 0081 | 1 | Rel-14 | B | Requirements for supporting accounting in the third party owned (S)Gi-LAN service | 13.3.0 | 14.0.0 | eFMSS |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|---------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-72 | SP-160354 | S1-161318 | 22.115 | 0082 | 1 | Rel-14 | C | update on accounting requirement for unlicensed access | 14.0.0 | 14.1.0 | USOS |
+| SP-72 | SP-160362 | S1-161579 | 22.115 | 0083 | 2 | Rel-14 | B | Charging requirements for Indirect 3GPP Communication | 14.0.0 | 14.1.0 | REAR |
+| SP-74 | SP-160901 | S1-163242 | 22.115 | 0084 | 2 | Rel-15 | B | Inclusion of distinction between WLAN direct discovery and ProSe direct discovery for charging purposes | 14.1.0 | 15.0.0 | ProSe_WLAN_DD |
+| SP-76 | SP-170447 | S1-172384 | 22.115 | 0086 | 2 | Rel-15 | B | Charging for Restricted Local Operator Services | 15.0.0 | 15.1.0 | PARLOS |
+| SP-77 | SP-170694 | S1-173452 | 22.115 | 0087 | 1 | Rel-15 | F | Remove restricted local operator services definition | 15.1.0 | 15.2.0 | PARLOS |
+| SP-79 | SP-180133 | S1-180533 | 22.115 | 0090 | 1 | Rel-15 | F | Charging for indirect network connection | 15.2.0 | 15.3.0 | TEI15 |
+| SP-80 | SP-180323 | S1-181751 | 22.115 | 0091 | 3 | Rel-16 | B | Charging for streaming services
MCC Note: as specified in the comment of CR 0092 in SP-180305 S1-181180, that CR applies to Rel-15 only, so it is not included in here | 15.3.0 | 16.0.0 | eLSTR |
+| SP-81 | SP-180766 | S1-182650 | 22.115 | 0095 | 1 | Rel-16 | F | Charging Requirement for Operator controlled Caching service delivery | 16.0.0 | 16.1.0 | eLSTR |
+| SP-81 | SP-180767 | S1-182084 | 22.115 | 0094 | | Rel-16 | B | UIA Charging Requirements | 16.0.0 | 16.1.0 | UIA |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2019-12 | SA#86 | SP-191009 | 0101 | 1 | A | Charging requirements for small data transmission | 16.2.0 |
+| 2019-12 | SA#86 | SP-191014 | 0096 | 1 | B | Introduction of NCIS Charging Requirements | 17.0.0 |
+| 2019-12 | SA#86 | SP-191023 | 0097 | 1 | C | Update of charging requirements for indirect communication to reflect REFEC | 17.0.0 |
+| 2020-12 | SA#90e | SP-201041 | 105 | 1 | B | Charging Service requirements for enhancing SFC support | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22119/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22119/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..573979e7429e90cae0a0743ad6a5814b0b5e3fbb
--- /dev/null
+++ b/marked/Rel-18/22_series/22119/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd0e2c05e90c0dd606eeb06eacb28f09c4e32c57ee5d8435d058636873231af7
+size 9303
diff --git a/marked/Rel-18/22_series/22119/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22119/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90a272776d0d3bbd72cde1b3439d0d5d72a7230e
--- /dev/null
+++ b/marked/Rel-18/22_series/22119/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7938d9183b682f6c999fe189de7321999ea6703c9c14784d29b86a0ec0be5f39
+size 7295
diff --git a/marked/Rel-18/22_series/22119/raw.md b/marked/Rel-18/22_series/22119/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac93badb6a7808e1a3b5117325237361cb7224f4
--- /dev/null
+++ b/marked/Rel-18/22_series/22119/raw.md
@@ -0,0 +1,257 @@
+
+
+# 3GPP TS 22.119 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Maritime Communication Services over 3GPP system; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+3GPP logo
+
+## Keywords ---
+
+Maritime, Requirements
+
+## **3GPP**
+
+## Postal address ---
+
+## 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet ---
+
+
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-------------------------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Symbols..... | 5 |
+| 3.3 Abbreviations ..... | 5 |
+| 4 Overview..... | 6 |
+| 5 Requirements of basic capabilities..... | 6 |
+| 5.1 Network connection and service continuity ..... | 6 |
+| 5.1.1 Description ..... | 6 |
+| 5.1.2 Void ..... | 7 |
+| 5.2 Identification ..... | 7 |
+| 5.2.1 Description ..... | 7 |
+| 5.2.2 Requirements..... | 7 |
+| 6 Requirements of multi-access and seamless mobility..... | 7 |
+| 6.1 Seamless mobility ..... | 7 |
+| 6.1.1 Description ..... | 7 |
+| 6.1.2 Requirements..... | 7 |
+| 7 Requirements of warning notification and emergency request..... | 8 |
+| 7.1 Notification for maritime safety ..... | 8 |
+| 7.1.1 Description ..... | 8 |
+| 7.1.2 Requirements..... | 8 |
+| 7.2 Emergency request for maritime safety ..... | 8 |
+| 7.2.1 Description ..... | 8 |
+| 7.2.2 Requirements..... | 8 |
+| Annex A (informative): Status of legacy communication methods used for the navigation ..... | 9 |
+| Annex B (informative): Status of legacy communication methods used by equipment inside a vessel..... | 10 |
+| Annex C (informative): Change history..... | 11 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document describes service requirements to enable maritime communication services to be supported over a 3GPP system. Requirements for MC services applicable to general maritime usage are specified in 3GPP Technical Specifications dedicated to MC services [2], [3], [4], [5].
+
+Requirements in the present document are specific to maritime usage.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
+- [3] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
+- [4] 3GPP TS 22.281: "Mission Critical (MC) video".
+- [5] 3GPP TS 22.282: "Mission Critical (MC) data".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+(none)
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+(none)
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|-----|--------------------------------------------|
+| ICT | Information and Communication Technologies |
+| IMO | International Maritime Organization |
+| MC | Mission Critical |
+
+| | |
+|-------|--------------------------------------------------------|
+| MCS | Mission Critical Services |
+| NM | nautical mile |
+| SOLAS | International Convention for the Safety of Life at Sea |
+
+# --- 4 Overview
+
+The maritime domain, one of the 5G vertical domains in 3GPP is moving forward with the digitalisation and mobilisation of commercial as well as safety fields. Legacy 3GPP-based technologies and solutions can be beneficial to the digitalisation and mobilisation of the maritime domain though some of the legacy 3GPP enabling technologies and solutions may not be able to fully support the performances required by the maritime domain. The maritime radio environment was not originally considered by 3GPP when the technical specifications and solutions were standardised for LTE and 5G.
+
+However, most of the legacy mobile services and IoT services based on capabilities of EPS and 5GS specified in 3GPP specifications are applicable to maritime usage for the support of mobile broadband services, and for the support of IoT services or machine-type communication services in a vessel at sea.
+
+In addition, there are service scenarios and requirements specified in 3GPP specifications based on requirements of other related vertical domains (e.g. public safety domain, automotive domain, factory automation domain, and satellite industrial domain). Some requirements derived from service scenarios pertaining to these related vertical domains are applicable to the maritime domain. Thus, it is beneficial to use 3GPP enabling technologies developed to satisfy those requirements for the maritime domain in terms of economy of scale.
+
+For example, satellite access is one of the 3GPP radio access networks supported over the 5G system, so it is possible to provide seamless maritime mobile services by integrating multiple access technologies including satellite access depending on the service scenarios. In addition, 5G LAN-type access that can replace Ethernet-based access is applicable to indoor maritime mobile services inside a vessel.
+
+MC Services specified in 3GPP specifications are applicable to commercial and maritime safety fields. Some similarities exist between the public safety domain and the maritime domain in terms of service scenarios that are essentially the same. For example, in some situations, mobile communication services are supported on or amongst UEs while disconnected from their networks, i.e. off-network mode, or under isolated conditions.
+
+However, the maritime domain also has specific situations that do not pertain in other vertical domains or in the legacy ICT industrial domain. New 3GPP enabling technologies dedicated to the maritime domain can be used to address such specific situations based on requirements derived from maritime use cases. Other vertical domains may benefit from such new 3GPP enabling technologies that consider maritime domain scenarios and may need more robust technologies or solutions than those that currently exist for those vertical domains.
+
+The present document provides the stage 1 requirements specific to maritime usage over a 3GPP system for commercial as well as safety purposes. The stage 1 requirements derived from specific maritime usage but also related to MC services are specified in 3GPP technical specifications dedicated to MC services.
+
+# --- 5 Requirements of basic capabilities
+
+## 5.1 Network connection and service continuity
+
+### 5.1.1 Description
+
+General 3GPP procedures of network connection and service continuity are applicable to maritime usage within 3GPP communication range. For example, a UE mapped to a vessel needs to perform network reselection when a vessel arrives at a port where 3GPP networks are available different from the 3GPP network that a vessel was previously connected to but disconnected from when the vessel started a voyage and moved out of coverage of that network. Additional capabilities for the establishment of a 3GPP network connection and for service continuity could improve user experiences on maritime communication services over a 3GPP system despite some constraints from the maritime communication environment including the communication environment inside a vessel that is usually made of steel.
+
+### 5.1.2 Void
+
+## 5.2 Identification
+
+### 5.2.1 Description
+
+A UE identity specified in 3GPP specifications is applicable to maritime usage. There are vessel identities for the identification of a vessel as a unique identity in maritime communication services. Mapping a UE identity with a vessel identity is needed to support identification procedures based on vessel identities in maritime domain when a vessel itself plays the role of a UE in a 3GPP system.
+
+### 5.2.2 Requirements
+
+The 3GPP system shall provide a mechanism to associate a UE identity with a vessel identity.
+
+# --- 6 Requirements of multi-access and seamless mobility
+
+## 6.1 Seamless mobility
+
+### 6.1.1 Description
+
+Network deployment scenarios are to be taken into account for maritime communication and these may differ from terrestrial communication in order to provide seamless mobile services within a vessel at sea or on inland waterways. The usage of moving networks, isolated networks or satellite access networks may be more commonly applicable for maritime safety services compared with general commercial services over 3GPP networks because fixed mobile network deployments are used for most terrestrial mobile services.
+
+The communication range may depend on a number of factors such as the power level transmitted, the height of the antenna, the type of vessel, the particular service scenario and propagation conditions. Thus, it may not be easy to provide a single value for the communication range between two vessels, and for a vessel that is applicable for all maritime service scenarios.
+
+### 6.1.2 Requirements
+
+The minimum communication range between vessels shall be equal to the maximum line-of-sight range between antennas mounted on two vessels at sea or on inland waterways.
+
+NOTE: The communication range between vessels is measured in nautical miles (NM)s and 1 NM equals 1852 metres.
+
+EXAMPLE: In the case of non-SOLAS vessels with antenna heights 4 metres above sea level, the minimum communication range is 10 NMs when applying the formula defined in IMO Resolution A.801(19).
+
+# 7 Requirements of warning notification and emergency request
+
+## 7.1 Notification for maritime safety
+
+### 7.1.1 Description
+
+Notifications for maritime safety are transmitted by authorities to maritime mobile users at sea. Notifications can be used to inform vessels of the location of a vessel in danger. A vessel that receives notifications relating to maritime safety needs to be able to relay such notifications to neighbouring vessels that are not in coverage of the 3GPP system.
+
+### 7.1.2 Requirements
+
+The 3GPP system shall provide a mechanism of including the position, heading and speed of other UEs in a maritime notification transmitted only to a dedicated UE requesting maritime safety information.
+
+## 7.2 Emergency request for maritime safety
+
+### 7.2.1 Description
+
+Maritime accidents such as "man overboard" need to be handled quickly and effectively by the 3GPP system. 3GPP specifications provides several mechanisms for reporting emergencies to and requesting assistance from the appropriate authorities. In addition to legacy emergency request mechanisms, additional capabilities could make a 3GPP system more powerful for maritime safety.
+
+### 7.2.2 Requirements
+
+The 3GPP system shall provide a mechanism of distributing a maritime emergency request received from a UE to all UEs on that vessel.
+
+A UE dedicated to a vessel shall support the capability of sending maritime emergency requests including the vessel-dedicated UE's actual position (e.g. current position, heading and speed of the vessel and scheduled navigational routes).
+
+# --- Annex A (informative): Status of legacy communication methods used for the navigation
+
+Void
+
+# --- Annex B (informative): Status of legacy communication methods used by equipment inside a vessel
+
+Void
+
+# Annex C (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-08 | SA1#83 | S1-182608 | | | | TS Skeleton | 0.0.0 |
+| 2018-08 | SA1#83 | S1-182609 | | | | Scope | 0.1.0 |
+| 2018-08 | SA1#83 | S1-182610 | | | | Overview | 0.1.0 |
+| 2018-08 | SA1#83 | S1-182611 | | | | Requirements of basic capabilities | 0.1.0 |
+| 2018-08 | SA1#83 | S1-182726 | | | | Requirements of maritime notification and emergency request | 0.1.0 |
+| 2018-09 | SA#81 | SP-180762 | | | | Raised by MCC to v.1.0.0 for presentation to SA for information | 1.0.0 |
+| 2018-11 | SA1#84 | S1-183615 | | | | Requirement on the communication range between vessels | 1.1.0 |
+| 2018-12 | SA#82 | SP-181004 | | | | Raised by MCC to v.2.0.0 for presentation to SA for approval | 2.0.0 |
+| 2018-12 | SA#82 | SP-181004 | | | | Raised by MCC to v.16.0.0 following SA#82 approval | 16.0.0 |
+| 2019-09 | SA#85 | SP-190802 | 0002 | 2 | F | Clarification and editorial updates | 16.1.0 |
+| 2020-09 | SA#89e | SP-200785 | 0003 | 1 | F | R16 CR to TS22.119 for Requirement alignment for Relay | 16.2.0 |
+| 2020-09 | SA#89e | SP-200786 | 0004 | 1 | F | Clarification and disambiguation of text, provision of missing abbreviations and references | 16.2.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22125/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22125/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad7779f5d036a833792084ada3834377d762f0aa
--- /dev/null
+++ b/marked/Rel-18/22_series/22125/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f2715f81d94482a6670063c686e25ba80872a4200f20c63de58ef91a3c5168f
+size 7575
diff --git a/marked/Rel-18/22_series/22125/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22125/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97bf64b2de080dcf7aa6d7c91437fe95801b4291
--- /dev/null
+++ b/marked/Rel-18/22_series/22125/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7deec4fcec78c72a48896b3e883c737d10ae6abc30e129d138420a11a3daa8c
+size 5542
diff --git a/marked/Rel-18/22_series/22125/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-18/22_series/22125/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43e92cdbc733fde2aebcdbcee6acbaaedc4075c0
--- /dev/null
+++ b/marked/Rel-18/22_series/22125/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9426ea6b21b5cad9bd729ee7d29ec1d8bf064e7659256afe890cb29f21969862
+size 47548
diff --git a/marked/Rel-18/22_series/22125/raw.md b/marked/Rel-18/22_series/22125/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c3c606d1f11a4292be74c9b20f003d053b09077f
--- /dev/null
+++ b/marked/Rel-18/22_series/22125/raw.md
@@ -0,0 +1,519 @@
+
+
+# 3GPP TS 22.125 V18.0.0 (2023-09) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Uncrewed Aerial System (UAS) support in 3GPP; Stage 1; Release 18** ---
+
+
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the bottom by a red, curved line. The "P" and "P" are connected at the top by a black, curved line. A small "TM" symbol is located to the right of the "P".
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+## Keywords ---
+
+Uncrewed, Aerial, Requirements
+
+## **3GPP**
+
+### Postal address ---
+
+### 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47
+16
+
+## Internet ---
+
+
+
+## ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|--------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Symbols..... | 6 |
+| 3.3 Abbreviations ..... | 6 |
+| 4 Overview on UAS..... | 6 |
+| 4.1 General ..... | 6 |
+| 4.2 C2 Communication ..... | 6 |
+| 5 Requirements for Remote Identification of UAS ..... | 7 |
+| 5.1 General ..... | 7 |
+| 5.2 UAS traffic management..... | 9 |
+| 5.2.1 General ..... | 9 |
+| 5.2.2 Decentralized UAS traffic management..... | 9 |
+| 5.3 Void..... | 9 |
+| 5.4 Security..... | 9 |
+| 6 Requirements for UAV usages ..... | 10 |
+| 6.1 General ..... | 10 |
+| 6.2 Network exposure for UAV services ..... | 10 |
+| 6.3 Service restriction for UEs onboard of UAV ..... | 10 |
+| 6.4 Requirements for UxNB..... | 10 |
+| 6.5 C2 communication ..... | 11 |
+| 7 Performance requirements ..... | 11 |
+| 7.1 KPIs for services provided to the UAV applications ..... | 11 |
+| 7.2 KPIs for UAV command and control..... | 12 |
+| 7.3 Positioning performance requirements..... | 13 |
+| 7.4 Other requirements ..... | 14 |
+| Annex A (informative): UAS Reference Model..... | 15 |
+| A.1 UAS Reference Model in 3GPP ecosystem ..... | 15 |
+| Annex B (informative): Change history ..... | 16 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+Interest in using cellular connectivity to support Uncrewed Aerial Systems (UAS) is strong, and the 3GPP ecosystem offers excellent benefits for UAS operation. Ubiquitous coverage, high reliability and QoS, robust security, and seamless mobility are critical factors to supporting UAS command and control functions. In parallel, regulators are investigating safety and performance standards and Registration and licensing programs to develop a well-functioning private and civil UAS ecosystem which can safely coexist with commercial air traffic, public and private infrastructure, and the general population.
+
+The 3GPP system can provide control plane and user plane communication services for UAS. Examples of services which can be offered to the UAS ecosystem includes data services for command and control (C2), telematics, UAS-generated data, remote identification, and authorisation, enforcement, and regulation of UAS operation.
+
+# --- 1 Scope
+
+The present document identifies the requirements for operation of Uncrewed Aerial Vehicles (UAVs) via the 3GPP system.
+
+This includes requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription.
+
+# --- 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] FAA UTM Concept of Operations v1.0, Foundational Principles, Roles and Responsibilities, Use Cases and Operational Threads
+- [3] FAA Remote Identification, [https://www.faa.gov/uas/research\\_development/remote\\_id/](https://www.faa.gov/uas/research_development/remote_id/)
+- [4] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
+- [5] IMT 2020(5G): "Application for UAV in 5G White Paper", September 2018
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Above ground level (AGL):** In the context of a UAV it is the UAV altitude referenced to ground level in the vicinity.
+
+**Command and Control (C2) Communication:** the user plane link to convey messages with information of command and control for UAV operation between a UAV controller and a UAV.
+
+**Uncrewed Aerial System (UAS):** Composed of Uncrewed Aerial Vehicle (UAV) and related functionality, including command and control (C2) links between the UAV and the controller, the UAV and the network, and for remote identification. A UAS is comprised of a UAV and a UAV controller.
+
+NOTE: A UAV can be controlled by different UAV controllers, but at any given time, a UAV is under the control of only one UAV controller. The mechanisms to ensure which UAV controller is active and controlling the UAV is out of scope of 3GPP.
+
+**Uncrewed Aerial System Traffic Management (UTM):** a set of functions and services for managing a range of autonomous vehicle operations.
+
+**UAV controller:** The UAV controller of a UAS enables a drone pilot to control an UAV.
+
+**UxNB:** radio access node on-board UAV. It is a radio access node providing connectivity to UEs, which is carried in the air by an Uncrewed Aerial Vehicle (UAV).
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|-----------|-----------------------------------------------|
+| BVLOS | Beyond Visual Line of Sight |
+| C2 | Command and Control |
+| Remote ID | Remote Identification [3] |
+| UAS | Uncrewed Aerial System |
+| UAV | Uncrewed Aerial Vehicle |
+| UTM | Uncrewed Aerial System Traffic Management [2] |
+
+# --- 4 Overview on UAS
+
+## 4.1 General
+
+An Uncrewed Aerial System (UAS) is the combination of an Uncrewed Aerial Vehicle (UAV), sometimes called a drone, and a UAV controller. A UAV is an aircraft without a human pilot onboard – instead, in some cases, the UAV can be controlled from an operator via a UAV controller and will have a range of autonomous flight capabilities. The communication system between the UAV and UAV controller is, within the scope of this specification and in some scenarios, provided by the 3GPP system. The UAS model considers also the scenario where the UAV controller communicates with the UAV via mechanisms outside the scope of 3GPP.
+
+UAVs range in size and weight from small, light aircraft often used for recreational purposes to large, heavy aircraft which are often more suited to commercial applications. Regulatory requirements vary across this range and vary on a regional basis.
+
+The communication requirements for UAS cover both the Command and Control (C2), and uplink and downlink data to/from the UAS components towards both the serving 3GPP network and network servers. The applicable C2 communication modes is depicted in clause 4.2.
+
+Uncrewed Aerial System Traffic Management (UTM) is used to provide a number of services to support UAS and their operations including but not limited to UAS identification and tracking, authorisation, enforcement, regulation of UAS operations, and also to store the data required for UAS(s) to operate. It also allows authorised users (e.g., air traffic control, public safety agencies) to query the identity and metadata of a UAV and its UAV controller.
+
+## 4.2 C2 Communication
+
+When using 3GPP network as the transport network for supporting UAS services, the following C2 communication are considered to provision UAS services by guaranteeing QoS for the C2 communication:
+
+**Direct C2 communication:** the UAV controller and UAV establish a direct C2 link to communicate with each other and both are registered to the 5G network using the radio resource configured and scheduled provided by the 5G network for direct C2 communication.
+
+**Network-Assisted C2 communication:** the UAV controller and UAV register and establish respective unicast C2 communication links to the 5G network and communicate with each other via 5G network. Also, both the UAV
+
+controller and UAV may be registered to the 5G network via different NG-RAN nodes. The 5G network needs to support mechanism to handle the reliable routing of C2 communication.
+
+**UTM-Navigated C2 communication:** the UAV has been provided a pre-scheduled flight plan, e.g. array of 4D polygons, for autonomous flying, however UTM still maintains a C2 communication link with the UAV in order to regularly monitor the flight status of the UAV, verify the flight status with up-to-date dynamic restrictions, provide route updates, and navigate the UAV whenever necessary.
+
+In general, Direct C2 communication and Network-Assisted C2 communication are used by a human-operator using a UAV controller. UTM-Navigated C2 communication is used by the UTM to provide cleared flying routes and routes updates. In order to ensure the service availability and reliability of the C2 communication for UAS operation, especially when the UAV is flying beyond line of sight (BLOS) of the operator, redundant C2 communication links can be established for any C2 communication links from UAV controller or UTM to a UAV.
+
+For reliability and service availability consideration, it is possible to activate more than one C2 communication with one as a backup link for C2 communication or switch among the applicable links for C2 communication.
+
+- For example, Direct C2 communication can be used at first and then switch to the Network-Assisted C2 communication when the UAV is flying BLOS.
+- For example, UTM-navigated C2 communication can be utilized whenever needed, e.g. for air traffic control, the UAV is approaching a No Drone Zone, and detected potential security threats, etc.
+
+There are four control modes considered in the C2 communication for the UAV operation that are with different requirements, e.g. on message intervals, sizes, and end to end latencies, etc., including steer to waypoints, direct stick steering, automatic flight by UTM and approaching autonomous navigation infrastructure.
+
+- Steer to waypoints: the control message contains flight declaration, e.g. waypoints, sent from the UAV controller or UTM to the UAV. The control mode is used in both of direct C2 communication and network-assisted C2 communication.
+- Direct stick steering: the control message contains direction instructions sending from the UAV controller to the UAV while optionally video traffic is provided as feedback from the UAV to the UAV controller. The control mode is used in both of direct C2 communication and network-assisted C2 communication.
+- Automatic flight by UTM: the control message contains a pre-scheduled flight plan, e.g. array of 4D polygons, sent from the UTM to the UAV, which thereafter flies autonomously with periodic position reporting. The control mode is used in UTM-Navigated C2 communication.
+- Approaching autonomous navigation infrastructure: the control message contains direction instructions, e.g. waypoints, altitudes and speeds from the UTM to the UAV. When the UAV is landing/departing, the UTM coordinates more closely with autonomous navigation infrastructure, e.g. vertiport or package distribution center. The control mode is used in UTM-Navigated C2 communication.
+
+# --- 5 Requirements for Remote Identification of UAS
+
+## 5.1 General
+
+[R-5.1-001] The 3GPP system should enable UTM to associate the UAV and UAV controller, and the UTM to identify them as a UAS.
+
+[R-5.1-002] The 3GPP system shall be able to provide UTM with the identity/identities of a UAS.
+
+[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status.
+
+[R-5.1-004] The 3GPP system shall enable a UAS to send UTM the UAV controller data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV controller, position, owner identity, owner
+
+address, owner contact details, owner certification, UAV operator identity, UAV operator license, UAV operator certification, UAV pilot identity, UAV pilot license, UAV pilot certification and flight plan.
+
+[R-5.1-005] The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS.
+
+NOTE 0: Subject to the regional regulation, the different authentication and authorization levels can be: the initial network access authentication and authorization, UAS identity authentication, UAV flight plan authorization, additional UTM service authentications, such as flight monitoring, collision avoidance services, so on.
+
+[R-5.1-006] The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future.
+
+[R-5.1-007] Based on regulations and security protection, the 3GPP system shall enable a UAS to send UTM the identifiers which can be: IMEI, MSISDN, or IMSI, or IP address.
+
+[R-5.1-008] The 3GPP system shall enable a UE in a UAS to send the following identifiers to a UTM: IMEI, MSISDN, or IMSI, or IP address
+
+[R-5.1-009] The 3GPP system should enable an MNO to augment the data sent to a UTM with the following: network-based positioning information of UAV and UAV controller.
+
+NOTE 1: This augmentation may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information, such as OTDOA, cell coordinates, synchronization source, etc.
+
+NOTE 2: This requirement will not be applied to the case which the UAS and UTM has direct control communication connection without going through MNO, such as OTDOA, cell coordinates, synchronization source, etc.
+
+[R-5.1-010] The 3GPP system shall enable UTM to inform an MNO of the outcome of an authorisation to operate.
+
+[R-5.1-011] The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present.
+
+[R-5.1-012] The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller.
+
+[R-5.1-013] The 3GPP network should be able to provide supplement location information of UAV and its controller to a UTM.
+
+NOTE 3: This supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information.
+
+[R-5.1-014] The 3GPP network shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.
+
+[R-5.1-014a] The 3GPP system shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.
+
+[R-5.1-015] The 3GPP system shall provide the capability for network to obtain the UAS information regarding its support of 3GPP communication capabilities designed for UAS operation.
+
+[R-5.1-016] The 3GPP system shall support the UAS identification and subscription data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE.
+
+NOTE 4: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS.
+
+[R-5.1-017] The 3GPP system shall support the UTM in detection of UAV operating without authorization.
+
+NOTE 5: the scenarios covered by the requirement above are FFS.
+
+## 5.2 UAS traffic management
+
+### 5.2.1 General
+
+NOTE: The following requirements are valid for both centralized and decentralized UTM.
+
+[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with flight clearance, to a UAV.
+
+[R-5.2.1-002] The 3GPP system shall be able to deliver route modification information received from a UTM to a UAV with a latency of less than 500ms.
+
+[R-5.2.1-003] The 3GPP system shall be able to deliver the notifications received from a UTM to a UAV controller with a latency of less than 500ms.
+
+[R-5.2.1-004] Based on MNO policies and/or regulatory requirements, the 3GPP system shall enable the UTM to take over the communication used to control the UAV.
+
+### 5.2.2 Decentralized UAS traffic management
+
+[R-5.2.2-001] The 3GPP system shall enable a UAV to broadcast the following data for identifying UAV(s) in a short-range area for collision avoidance: e.g. UAV identities if needed based on different regulation requirements, UAV type, current location and time, flight route information, current speed, operating status.
+
+[R-5.2.2-002] The 3GPP system shall be able to support a UAV to transmit a message via network connection for identifying itself as an UAV to the other UAV(s).
+
+[R-5.2.2-003] The 3GPP system shall enable UAV to preserve the privacy of the owner of the UAV, UAV pilot, and the UAV operator in its broadcast of identity information.
+
+[R-5.2.2-004] The 3GPP system shall enable a UAV to receive local broadcast communication transport service from other UAV in short range.
+
+[R-5.2.2-005] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service in the coverage or out of coverage of a 3GPP network.
+
+[R-5.2.2-006] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when the sending and receiving UAVs are served by the same or different PLMNs.
+
+[R-5.2.2-007] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at relative speeds of up to 320kmph.
+
+[R-5.2.2-008] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service with variable message payloads of 50-1500 bytes, not including security-related message component(s).
+
+[R-5.2.2-009] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range of up to 600m.
+
+[R-5.2.2-010] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages at a frequency of at least 10 messages per second.
+
+[R-5.2.2-011] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages with an end-to-end latency of at most 100ms.
+
+## 5.3 Void
+
+## 5.4 Security
+
+[R-5.4-001] The 3GPP system shall protect the transport of data between the UAS and UTM.
+
+[R-5.4-002] The 3GPP system shall protect against spoofing attacks of the UAS identities.
+
+[R-5.4-003] The 3GPP system shall allow non-repudiation of data sent between the UAS and UTM at the application layer.
+
+[R-5.4-004] The 3GPP system shall support the capability to provide different levels of integrity and privacy protection for the different connections between UAS and UTM as well as the data being transferred via those connections.
+
+[R-5.4-005] The 3GPP system shall support confidentiality protection of identities related to the UAS and personally identifiable information.
+
+[R-5.4-006] The 3GPP system shall support regulatory requirements (e.g. Lawful Intercept) for UAS traffic.
+
+# --- 6 Requirements for UAV usages
+
+## 6.1 General
+
+Beyond UAV related requirements, the 3GPP can be used to support for a wide range of applications and scenarios by using low altitude UAVs in various commercial and government sectors. New service level requirements and KPIs for supporting various UAV applications by the 3GPP system have been identified and specified e.g. Service requirements and KPIs related to command and control (C2), payload (e.g. camera) and the operation of radio access nodes on-board UAVs.
+
+## 6.2 Network exposure for UAV services
+
+[R-6.2-001] The 3GPP system shall provide means to allow a 3rd party to request and obtain real-time monitoring the status information (e.g., location of UAV, communication link status) of a UAV.
+
+[R-6.2-002] Based on operator 's policy, the 3GPP system shall provide means to provide a 3rd party with the information regarding the service status for UAVs in a certain geographical area and/or at a certain time.
+
+NOTE: Service status is about the information of whether the communication service to the UAV can be provided with a certain QoS by the network.
+
+## 6.3 Service restriction for UEs onboard of UAV
+
+[R-6.3-001] The 3GPP network shall be able to support network-based 3D space positioning (e.g., with altitude 30~300m) of a UE onboard UAV.
+
+[R-6.3-002] The 3GPP system shall be able to notify the authorized third party of potential stopping of connectivity service before the UE onboard of UAV enters an area (e.g., due to altitude) where the connectivity service is not authorized for the UE.
+
+## 6.4 Requirements for UxNB
+
+[R-6.4-001] The 5G system shall be able to support UxNBs to provide enhanced and more flexible radio coverage.
+
+[R-6.4-002] The 3GPP system shall be able to provide suitable means to control the operation of the UxNBs (e.g. to start operation, stop operation, replace UxNB etc.).
+
+[R-6.4-003] The 3GPP system shall be able to provide means to minimize power consumption of the UxNBs (e.g. optimizing operation parameter, optimized traffic delivery).
+
+[R-6.4-004] The 3GPP system shall be able to minimize interference e.g. caused by UxNBs changing their positions.
+
+## 6.5 C2 communication
+
+[R-6.5-001] The 3GPP system shall support C2 communication with required QoS for pre-defined C2 communication models (e.g. using direct ProSe Communication between UAV and the UAV controller, UTM-navigated C2 communication based on flight plan between UTM and the UAV).
+
+[R-6.5-002] The 3GPP system shall support C2 communication with required QoS when switching between the C2 communication models.
+
+[R-6.5-003] The 3GPP system shall support a mechanism for the UTM to request monitoring of the C2 communication with required QoS for pre-defined C2 communication models (e.g. using direct ProSe Communication between UAV and the UAV controller, UTM-navigated C2 communication between UTM and the UAV).
+
+# --- 7 Performance requirements
+
+## 7.1 KPIs for services provided to the UAV applications
+
+The 5G system shall be able to provide uncrewed aerial vehicle with the service performance requirements reported in Table 7.1-1.
+
+UAV originated QoS in the table refers to the QoS of Uplink data (e.g. from UAV to the network side). UAV terminated QoS is the QoS of downlink data (e.g. from the network side to UAV).
+
+The data transmitted by the 5G system includes data collected by hardware devices installed on UAV such as cameras, e.g. pictures, videos and files. It is also possible to transmit some software calculation or statistical data, e.g. UAV management data. The service control data transmitted by the 5G system may be based on application triggers, such as switch, rotation, promotion and demotion control of equipment on UAV. Various UAV applications may require different uplink and downlink QoS at the same time. The 5G system may simultaneously provide services to other users on the ground (e.g., the KPIs for rural and urban scenarios as defined in 7.1 of TS 22.261 [4]) in the same area without service degradation.
+
+Table 7.1-1 KPIs for services provided to the UAV applications
+
+| Use case | Services | Data rate | End to end Latency | Altitude AGL | service area (note 4) |
+|----------|----------------------------------------|----------------------------------------------------------------|--------------------|------------------------|------------------------------------------------|
+| 1 | 8K video live broadcast | 100Mbps UAV originated | 200 ms | <100 m | Urban, scenic area |
+| | | 600Kbps UAV terminated | 20 ms | <100 m | |
+| 2 | Laser mapping/ HD patrol Note 7 | 120Mbps UAV originated Note 1 | 200 ms | 30-300 m | Urban, rural area, scenic area |
+| | | 300Kbps UAV terminated | 20 ms | 30-300 m | |
+| 3 | 4*4K AI surveillance | 120Mbps UAV originated | 20 ms | <200 m | Urban, rural area |
+| | | 50Mbps UAV terminated | 20 ms | <200 m | |
+| 4 | Remote UAV controller through HD video | >=25Mbps UAV originated (Note 3) | 100 ms | <300 m | Urban, rural area |
+| | | 300Kbps UAV terminated | 20 ms | <300 m | |
+| 5 | Real-Time Video | 0.06 Mbps w/o video UAV originated | 100 ms | - | Urban, rural, countryside |
+| 6 | Video streaming | 4 Mbps for 720p video
9 Mbps for 1080p video UAV originated | 100 ms | - | Urban, rural, countryside |
+| 7 | Periodic still photos | 1Mbps UAV originated | 1s 1S | <0.20m <120m | Urban, rural, countryside
Urban, rural area |
+
+NOTE 1: The flight average speed is 60km/h. The KPI is referring to [5].
+
+NOTE 2: The latency is the time of the 5G system provide higher accuracy location information of a UAV to a third party.
+
+NOTE 3: Referring to clause 5.2.2, the absolute flying speed of UAV in this service can be up to 160km/h.
+
+NOTE 4: The density of active UAV is 10/200km2. The maximum altitude is 300m. The flight average speed is 60km/h.
+
+## 7.2 KPIs for UAV command and control
+
+UAVs may use a variety of flight command and control modes. Command and control (C2) communications refers to the two-way communication, which may include video, required to control the operation of the UAV itself. C2 messages may be communicated with the UAV controller, the UTM or both and may or may not be periodic. UAV controller and UTM communications may happen at essentially the same time with different required QoS. Any mission specific communication (e.g. HD video for area surveillance), if required, is additional. Different modes of control and their typical KPIs are listed in this clause below. The 5G system shall support UAV operation at altitudes of at least 120m / 400ft above ground level, e.g. the services should be provided and characterized up to 3000ft AGL.
+
+**Table 7.2-1 KPIs for command and control of UAV operation**
+
+| Control Mode | Function | Typical Message Interval | Max UAV ground speed | Typical message Size (note 1) | End to end Latency | Reliability (note 2) | Positive ACK (note 8) |
+|--------------------------------------------------|------------------------------------|--------------------------|----------------------|-------------------------------|--------------------|----------------------|-----------------------|
+| Steer to waypoints (note 3) | UAV terminated C2 message | >=1 s | 300 km/h | 100 byte | 1 s | 99.9% | Required |
+| | UAV originated C2 message (note 4) | 1 s | | 84-140 byte | 1 s | 99.9% | Not Required |
+| Direct stick steering (note 5) | UAV terminated C2 message | 40 ms (note 6) | 60km/h | 24 byte | 40 ms | 99.9% | Required |
+| | UAV originated C2 message (note 7) | 40 ms | | 84-140 byte | 40 ms | 99.9% | Not Required |
+| Automatic flight on UTM (note 10) | UAV terminated C2 message | 1 s | 300 km/h | <10 kbyte | 5 s (note 9) | 99.9% | Required |
+| | UAV originated C2 message | 1 s (note 9) | | 1500 byte | 5 s (note 9) | 99.9% | Required |
+| Approaching Autonomous Navigation Infrastructure | UAV terminated C2 message | 500 ms | 50 km/h | 4 kbyte | 10 ms | 99% | Required |
+| | UAV originated C2 message | 500 ms | | 4 kbyte | 140 ms | 99.99% | Required |
+
+NOTE 1: Message size is at the application layer and excludes any headers and security related load. The numbers shown are typical as message size depends on the commands sent and is implementation specific.
+
+NOTE 2: Message reliability is defined as the probability of successful transmission within the required latency at the application layer while under network coverage.
+
+NOTE 3: Video is neither required nor expected to be used for steering in this mode.
+
+NOTE 4: It may be possible to transmit this message on an event driven basis (e.g. approaching a geo fence). A status message may, but is not required to, be sent as a response to a control message.
+
+NOTE 5: A video feedback is required for this mode. The KPIs for video are defined in table 7.2-2.
+
+NOTE 6: UAVs on-board controllers typically update at either 50Hz (20ms) or 25Hz (40ms).
+
+NOTE 7: A status message may, but is not required to, be sent as a response to a control message A 1Hz slow mode also exists.
+
+NOTE 8: Positive ACK is sent to the originator of the message (i.e. UAV controller and / or the UTM). The 5G system makes no assumption whether an appropriate ACK is sent by the application layer.
+
+NOTE 9: At the application layer, the C2 communication between a UAV and UTM can be allowed to experience much longer traffic interruptions, e.g. timeouts of 30 s on the uplink and 300 s on the downlink.
+
+NOTE 10: This only represents periodic message exchange during a nominal mission in steady state. It does not represent unusual or aperiodic events such as conveying dynamic restrictions or a flight plan to the UAV on the downlink.
+
+**Table 7.2-2 KPIs for video used to aid UAV control.**
+
+| Scenario (note 2) | Data rate | End to end Latency | Reliability (note 1) | Direction | Positive ACK required |
+|-----------------------------|-------------------------|--------------------|----------------------|-------------|-----------------------|
+| VLOS (visual line of sight) | 2 Mbps at 480 p, 30 fps | 1 s | 99.9% | Sent by UAV | Not Required |
+| Non-VLOS | 4 Mbps at 720 p, 30 fps | 140 ms | 99.99% | Sent by UAV | Not Required |
+
+NOTE 1: Message reliability is defined as the probability of successful transmission within the required latency.
+
+NOTE 2: Maximum UAV speed is same as control mode of direct stick steering in 7.2-1
+
+## 7.3 Positioning performance requirements
+
+Table 7.3-1 below lists typical scenarios and the corresponding positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
+
+NOTE: The column on "Corresponding Positioning Service Level in TS 22.261" maps the scenarios listed in Table 7.3-1 to the service levels defined in TS 22.261 [4].
+
+**Table 7.3-1: Positioning performance requirements**
+
+| Scenario | Accuracy
(95 % confidence level) | | Availability | Heading | Latency for
position
estimation
of UE | UE
Speed | Corresponding
Positioning
Service Level
in TS 22.261 |
+|-------------------------------------------|-------------------------------------|----------------------|--------------|---------|------------------------------------------------|-------------|---------------------------------------------------------------|
+| | Horizontal
accuracy | Vertical
accuracy | | | | | |
+| 8K video live broadcast | [0.5 m] | [1 m] | 99% | | 1s | [<120 km/h] | 5 |
+| Laser mapping/
HD patrol | [0.5 m] | [1 m] | 99% | | 1s | [<120 km/h] | 5 |
+| 4*4K AI surveillance | [0.1 m] | | | | | [<60 km/h] | |
+| Remote UAV controller
through HD video | [0.5 m] | [1 m] | 99% | | 1s | [<120 km/h] | 5 |
+| Periodic still photos | [0.1 m] | [1 m] | | | | [<60 km/h] | |
+
+NOTE: The positioning accuracy in this table is not related to navigation or safety.
+
+## 7.4 Other requirements
+
+[R-7.4-001] The 5G system shall support a mechanism to switch between C2 communication modes for UAS operation, e.g. from indirect C2 communication to direct C2 communication, and ensure the disconnect time is below the latency requirements.
+
+[R-7.4-002] The 3GPP system shall enable concurrent communications between the UAV-controller and UAV and between the UTM and the UAV that may require different KPIs.
+
+[R-7.4-003] The 3GPP system shall be capable of switching between the KPIs, as requested by the UAV-controller or the UTM, within [500ms].
+
+# Annex A (informative): UAS Reference Model
+
+## A.1 UAS Reference Model in 3GPP ecosystem
+
+
+
+Diagram of the UAS Reference Model in the 3GPP ecosystem. It shows three UAVs connected to a central 3GPP Mobile Network cloud. Each UAV is associated with a 'UAV Application' and a 'UAV Controller'. The top UAV is connected to a controller via a C2 interface (transport not in 3GPP scope). The middle UAV is connected to a controller via C2 over 3GPP connectivity. The bottom UAV is connected to a controller via the 3GPP Mobile Network. All three UAVs exchange 'Application Data Traffic' with a 'UTM' (Unmanned Traffic Management) system. The 3GPP Mobile Network cloud is shown as a central hub for the middle and bottom UAVs.
+
+**Figure B.1-1: UAS model in 3GPP ecosystem.**
+
+In the UAS reference model:
+
+- a UAS is composed of one UAV and one UAV controller in this illustration
+- UAVs are connected over cellular connectivity
+- a UAV can be controlled by a UAV controller connected via the 3GPP mobile network
+- a UAV can be controlled by a UAV controller not connected via the 3GPP mobile network, using a C2 interface not in 3GPP scope
+- a UAV controller connected via the 3GPP mobile network can control one or more UAV(s)
+- the UAS exchanges application data traffic with a UTM
+
+**NOTE:** Several types of UAV controllers exist, e.g. hand-held UAV controllers, PCs/WSs and automated or manual functions that are part of the UTM. The mechanisms to ensure which UAV controller is active and controlling the UAV is out of scope of 3GPP.
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|------|-----|---------------------------------------------------------------------------------------------|-------------|--|
+| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New version | |
+| 24/08/2018 | SA1#83 | S1-182766 | - | - | - | Skeleton created | 0.1.0 | |
+| 16/11/2018 | SA1#84 | S1-183278 | - | - | - | TS22.125 v0.2.0 created to include agreements at this meeting | 0.2.0 | |
+| 2018-12 | SA#82 | SP-181009 | - | - | - | Presentation for one-step approval to SA | 1.0.0 | |
+| 2018-12 | SA#82 | SP-181009 | - | - | - | Raised to v.16.0.0 following SA#82's one step approval | 16.0.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0001 | 2 | C | Removal of requirement on enforcement | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0005 | 1 | F | Detect and report the problematic UAV controller to UTM | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0009 | 1 | F | Clarification for identity of UAV controller data | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0008 | 1 | B | Addition for Abbreviations | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0003 | 3 | F | Clarification of Centralized UTM | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0004 | 3 | F | Clarification of Decentralized UTM for Collision Avoidance | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0002 | 2 | F | Clarification of UTM Definition | 16.1.0 | |
+| 2019-03 | SA#83 | SP-190083 | 0006 | 3 | B | Definition and Clarification for UTM | 16.1.0 | |
+| 2019-06 | SA#84 | SP-190300 | 0010 | 3 | F | Rewording the enforcement requirement in section 5.2 | 16.2.0 | |
+| 2019-09 | SA#85 | SP-190801 | 0021 | 2 | F | Clarifications on UAS terminology and model | 16.3.0 | |
+| 2019-09 | SA#85 | SP-190809 | 0017 | 2 | B | Definition and introduction of C2 Communication | 17.0.0 | |
+| 2019-09 | SA#85 | SP-190809 | 0018 | 2 | B | CR to 22.125 Network exposure requirements for UAV | 17.0.0 | |
+| 2019-09 | SA#85 | SP-190809 | 0013 | 2 | B | Adding UxNB related requirements | 17.0.0 | |
+| 2019-09 | SA#85 | SP-190809 | 0020 | 2 | B | Service restriction requirements for UAV | 17.0.0 | |
+| 2019-09 | SA#85 | SP-190801 | 0024 | 2 | F | Corrections to Requirements | 17.0.0 | |
+| 2019-12 | SA#86 | SP-191024 | 0026 | 2 | B | KPIs for UAV services | 17.1.0 | |
+| 2019-12 | SA#86 | SP-191024 | 0027 | 3 | F | Clarification of Control Modes in C2 communication | 17.1.0 | |
+| 2020-09 | SA#89e | SP-200881 | 0028 | 5 | F | Clarification of the definition of a UAS | 17.2.0 | |
+| 2021-03 | SA#91e | SP-210197 | 0034 | 1 | F | Clarification of problematic UAV | 17.3.0 | |
+| 2021-09 | SA#93e | SP-211034 | 0036 | 1 | D | UAS terminology alignment | 17.4.0 | |
+| 2021-12 | SP-94 | SP-211491 | 0038 | 1 | D | CR Editorial to T22.125 clause 6.4 and clause 7.1 | 17.5.0 | |
+| 2021-12 | SP-94 | SP-211491 | 0039 | 1 | D | CR inclusive language correction to T22.125 clause 1 | 17.5.0 | |
+| 2021-12 | SP-94 | SP-211491 | 0040 | 1 | C | CR to T22.125 for correction and readability improvement clause 4.2 and clause | 17.5.0 | |
+| 2021-12 | SP-94 | SP-211491 | 0041 | 2 | C | Addition of a note to [R-5.1-017] related to the applicability of the requirement | 17.5.0 | |
+| 2022-03 | SP#95e | SP-220078 | 0043 | 1 | D | Editorial corrections to TS 22.125 on UAV | 17.6.0 | |
+| 2023-09 | SA#101 | | | | B | Identical to v.17.6.0, issued because of CR #0047r7 in SP-231034, creating v.19 out of v.17 | 18.0.0 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22129/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-18/22_series/22129/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..abfcce0afbcd506c1c81babafcdd06e18b67db1c
--- /dev/null
+++ b/marked/Rel-18/22_series/22129/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62b685c2f5249133fe517d57b76cf20ae74263211631f29bd6a67f1c1e60b2eb
+size 63189
diff --git a/marked/Rel-18/22_series/22129/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22129/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..47ca62374aa8514799319f9445265d1542d1f444
--- /dev/null
+++ b/marked/Rel-18/22_series/22129/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67e76a3c6e1ee41965e2f065b569b80d8cfd135847c45f7503529d4636b1fce3
+size 8288
diff --git a/marked/Rel-18/22_series/22129/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22129/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d107e5ab554572172d9c1fe82c7e805eac754206
--- /dev/null
+++ b/marked/Rel-18/22_series/22129/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2737ce6737c2d983c8a528d43f16428340a5bd69c59a81f687d1da5b0d2ac8f
+size 7268
diff --git a/marked/Rel-18/22_series/22129/raw.md b/marked/Rel-18/22_series/22129/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..db79d0a714fc3af4847a37b12d75b4333d5cbd15
--- /dev/null
+++ b/marked/Rel-18/22_series/22129/raw.md
@@ -0,0 +1,707 @@
+
+
+# 3GPP TS 22.129 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service aspects; Handover requirements between UTRAN and GERAN or other radio systems (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like graphic above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal-like icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, GSM, handover
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 1.1 Situations in which Service Requirements apply ..... | 6 |
+| 2 References..... | 7 |
+| 3 Definitions and Abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 General Principles governing service continuity ..... | 8 |
+| 4.1 Service Continuity Scenarios ..... | 8 |
+| 4.2 Service Continuity requirements..... | 8 |
+| 4.2.1 Service continuity for CS ..... | 8 |
+| 4.2.2 Service continuity for GPRS ..... | 9 |
+| 4.2.3 Service continuity for IM Services..... | 9 |
+| 4.3 General Operational Considerations ..... | 9 |
+| 4.3.1 Coverage environment..... | 9 |
+| 4.3.2 Inter PLMN Handover Issues ..... | 9 |
+| 4.3.3 Charging and Network Management..... | 10 |
+| 4.3.4 Cost and efficiency ..... | 10 |
+| 4.3.5 Security ..... | 10 |
+| 4.4 Performance Requirements ..... | 10 |
+| 4.4.1 Temporary degradation of service caused by handover ..... | 10 |
+| 5 Requirements for Handover ..... | 10 |
+| 5.1 Handover due to UE Movement..... | 10 |
+| 5.2 Handover due to negotiated service requirement..... | 11 |
+| 5.3 Handover between Radio Access Modes ..... | 11 |
+| 5.4 Cell capacity..... | 11 |
+| 5.5 Handover of a Multicall ..... | 11 |
+| 5.6 Access Rights ..... | 11 |
+| 5.7 Handover for shared networks ..... | 11 |
+| 6 Requirements for Handover from UTRAN to GERAN..... | 12 |
+| 6.1 Operational Requirements..... | 12 |
+| 6.1.2 GERAN bands ..... | 12 |
+| 6.2 Performance Requirements ..... | 12 |
+| 6.2.1 Detection Time of Potential GERAN Handover Candidates ..... | 12 |
+| 6.2.2 Number of GERAN handover candidates to detect..... | 12 |
+| 6.2.3 Probability of Connection Loss ..... | 12 |
+| 6.3 Specific Requirements for Individual Services from UTRAN to GERAN ..... | 13 |
+| 6.3.1 Speech..... | 13 |
+| 6.3.2 Short Message Service ..... | 13 |
+| 6.3.3 Cell Broadcast ..... | 13 |
+| 6.3.4 USSD..... | 13 |
+| 6.3.5 Facsimile..... | 13 |
+| 6.3.6 Data Bearer Services ..... | 13 |
+| 6.3.6.1 Circuit Switched Data..... | 13 |
+| 6.3.6.2 Packet Switched Data ..... | 13 |
+| 6.3.7 Supplementary Services ..... | 13 |
+| 6.4 Requirements on multiple bearer services handover from UTRAN to GERAN ..... | 13 |
+| 7 Requirements for Handover from GERAN to UTRAN..... | 14 |
+| 7.1 Operational Requirements..... | 14 |
+| 7.1.2 GERAN bands ..... | 14 |
+| 7.2 Performance Requirements ..... | 14 |
+| 7.3 Specific Requirements for Individual Service Handover from GERAN to UTRAN ..... | 14 |
+| 7.3.1 Speech..... | 14 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------------------------------|-----------|
+| 7.3.2 | Short Message Service ..... | 14 |
+| 7.3.3 | Cell Broadcast ..... | 14 |
+| 7.3.4 | USSD ..... | 14 |
+| 7.3.5 | Facsimile..... | 15 |
+| 7.3.6 | Data Bearer Services ..... | 15 |
+| 7.3.6.1 | Circuit Switched Data ..... | 15 |
+| 7.3.6.2 | Packet Switched Data ..... | 15 |
+| 7.3.7 | Supplementary services ..... | 15 |
+| 7.4 | Requirements on multiple bearer services handover from GERAN to UTRAN ..... | 15 |
+| 8 | Cross Phase Compatibility for this release ..... | 15 |
+| 8.1 | Compatibility with Existing Specifications..... | 15 |
+| 8.2 | Compatibility with Future 3GPP specifications ..... | 15 |
+| 8.2.1 | Requirements for Service Capabilities ..... | 16 |
+| 8.2.2 | Inter PLMN Handover Issues ..... | 16 |
+| 8.2.3 | Handover between Environments..... | 16 |
+| 8.3 | Support of Multicall with Simultaneous Voice Calls..... | 16 |
+| Annex A (informative): | Illustration of elements in inter-PLMN handover ..... | 17 |
+| Annex B (informative): | Open Points on Inter-Operator Handover..... | 18 |
+| B.2 | Selection of Target Cells for Handover ..... | 18 |
+| B.3 | Network Information Exchange..... | 18 |
+| B.4 | Service Requirements ..... | 18 |
+| B.5 | Billing, Accounting and Charging Requirements ..... | 18 |
+| Annex C (informative): | Change history ..... | 19 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 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 this TS, 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 specification;
+
+# 1 Scope
+
+The scope of this document includes service requirements for handover maintaining continuity of service to a wireless terminal as it moves between the radio coverage area, or "cells", associated with different base station sites. This functionality is called "handover". Handover can also occur due to change of radio resource providing a service without necessarily any change of the base stations involved. In particular, when the radio resources providing a service change from one of the UTRA radio access modes to the other (UTRA-FDD and UTRA-TDD), this is regarded as handover. Particular emphasis has been placed on the description of requirements for service continuity within UTRAN and between UTRAN and GERAN.
+
+It is a key requirement to allow for dual or multi-mode terminals to handover traffic from UTRAN to GERAN and vice versa. This document describes the service requirements for intra- and inter- system handover.
+
+The following subject areas are within the scope of these service requirements:
+
+- User perceived performance that may be influenced by handover;
+- Operational requirements relating to handover;
+- Security requirements.
+
+The requirements set forth in this document are service requirements, in that they fulfil the following:
+
+- The requirements are independent of the implementation of the UTRAN;
+- The extent to which the requirements are met are in principle verifiable using observables that are not internal to the UTRAN.
+
+## 1.1 Situations in which Service Requirements apply
+
+The service requirements in this document are as far as possible independent of the implementation. They therefore apply to situations where handover would occur regardless of how the radio access network is implemented. Situations envisaged are:
+
+- Handover within UTRAN due to change of radio resource caused by UE movement between areas covered by different transmitters;
+- Handover within UTRAN due to change of UTRA radio access mode;
+- Handover due to change of radio system.
+
+It is possible that handover (i.e. change of radio resource) will occur in other situations, for example the technical implementation of the UTRAN may necessitate it or O&M procedures initiated by the operator may force it. Requirements for these situations are not within the scope of this document, with the exception of two remarks:
+
+- Where the technical implementation of the UTRAN necessitates handover as a matter of normal operation (i.e. not related to the above situations), then services shall in no way be degraded or adversely affected;
+- The service requirements for handover occurring in situations such as O&M activity are outside the scope of this document.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications "
+
+[2] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)"
+
+# 3 Definitions and Abbreviations
+
+## 3.1 Definitions
+
+In addition to the following, abbreviations used in the present document are listed in TR 21.905 [1].
+
+For the purposes of the present document, the following definitions apply:
+
+**Connection mode (for a bearer service):** characterises the type of association between two endpoints as required by the bearer service for the transfer of information. A bearer service is either connection-oriented or connectionless. In a connection oriented mode, a logical association called *connection* needs to be established between the source and the destination entities before information can be exchanged between them. Connection oriented bearer services lifetime is the period of time between the establishment and the release of the connection.
+
+**Connectionless (for a bearer service):** In a connectionless bearer, no connection is established beforehand between the source and the destination entities; the source and destination network addresses need to be specified in each message. Transferred information cannot be guaranteed of ordered delivery. Connectionless bearer services lifetime is reduced to the transport of one message.
+
+**GERAN coverage:** an area where mobile cellular services are provided by a GERAN in accordance with GERAN specifications.
+
+**UTRAN coverage:** an area where mobile cellular services are provided by a UTRAN in accordance with UTRAN specifications.
+
+**Multi mode terminal:** UE that can obtain service from at least one UTRA radio access mode, and one or more different systems such as GERAN bands or possibly other radio systems such IMT-2000 family members.
+
+**Handover:** The process in which the radio access network changes the radio transmitters or radio access mode or radio system used to provide the bearer services, while maintaining a defined bearer service QoS.
+
+**Intra PLMN handover:** Handover within the same network, i.e. having the same MCC-MNC regardless of radio access system. Note: this includes the case of UTRAN $\leftrightarrow$ GERAN handover where MCC-MNC are the same in both cases.
+
+**Inter PLMN handover:** Handover between different PLMNs, i.e. having different MCC-MNC.
+
+**Inter system handover:** Handover between networks using different radio systems , e.g. UTRAN – GERAN.
+
+**UTRA Radio access mode:** the selected UTRA radio access mode i.e. UTRA-FDD; UTRA-TDD.
+
+**Radio system:** the selected 2nd or 3rd generation radio access technology.
+
+**Service Continuity:** The means for maintaining active services during changes in the coverage areas or their characteristics without, as far as possible, the user noticing. Note that Service Continuity can be achieved by handover, cell re-selection or other mechanisms.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|----|----------------|
+| UE | User equipment |
+|----|----------------|
+
+# --- 4 General Principles governing service continuity
+
+## 4.0 General Principles for service continuity
+
+The general principles for service continuity described in this specification refer to service continuity within the UTRAN, within the GERAN and between the UTRAN and GERAN. As a principle, the requirements on service continuity characteristics should be according to the target network on which the service is maintained.
+
+Service requirements for seamless mobility between multiple heterogeneous access systems beyond only UTRAN and GERAN are contained within TS 22.278 [2].
+
+## 4.1 Service Continuity Scenarios
+
+Service continuity shall support the following scenarios:
+
+1. Continuity of active CS services when moving within UTRAN, within GERAN and between UTRAN and GERAN coverage areas.
+2. Continuity of active GPRS sessions when moving within UTRAN, within GERAN and between UTRAN and GERAN coverage areas.
+3. Continuity of active IM Services when moving within UTRAN, within GERAN and between UTRAN and GERAN coverage areas (that support those IM services).
+
+Service continuity is not applicable for any call or session using resources specific to the source domain that cannot be maintained using resources in the target domain.
+
+## 4.2 Service Continuity requirements
+
+For all scenarios, the specifications shall cover both service continuity within the same PLMN (intra-PLMN) and between PLMNs (inter-PLMN), including the case where the PLMNs involved are operated by different network operators.
+
+It shall be possible for a user to roam between the different parts of a shared network without requiring any user intervention. The user experience while roaming in a shared network shall be comparable to the user experience while roaming in a non-shared network.
+
+### 4.2.1 Service continuity for CS
+
+The scenario numbers in this table refer to the scenarios in section 4.1.
+
+| | | To CS services | |
+|------------------|-------|------------------|------------------|
+| | | UTRAN | GERAN |
+| From CS services | UTRAN | Yes - Scenario 1 | Yes - Scenario 1 |
+| | GERAN | Yes – Scenario 1 | Yes – Scenario 1 |
+
+### 4.2.2 Service continuity for GPRS
+
+Service continuity of GPRS sessions (conversation, streaming, interactive and background) is required within the GERAN, within the UTRAN, and between the UTRAN and GERAN (scenario 2 in section 4.1 above).
+
+Note: Service continuity for conversational, streaming and interactive GPRS sessions is not applicable to and from GERAN Release 4 or earlier, due to the lack of support for the conversational, streaming and interactive GPRS within GERAN Release 4 or earlier. In these cases, although the QoS required may not be available in the target, the bearer shall be maintained as long as possible. If the QoS supported by GERAN is not acceptable, the user/application may terminate the session.
+
+### 4.2.3 Service continuity for IM Services
+
+Service continuity of IM services is required within the GERAN, within the UTRAN, and between the UTRAN and GERAN (scenario 3 in section 4.1 above).
+
+Note: Service continuity of IM Services is not applicable to and from GERAN Release 4 or earlier as the IM Services service classes are not supported by GERAN Release 4 or earlier. In these cases, although the QoS required may not be available in the target, the bearer shall be maintained as long as possible. If the QoS supported by GERAN is not acceptable, the user/application may terminate the session.
+
+## 4.3 General Operational Considerations
+
+### 4.3.1 Coverage environment
+
+Mechanisms defined to support service continuity between different radio systems or radio access modes should effectively cope with a number of coverage scenarios:
+
+- Limited coverage in a 'sea' of coverage provided by another radio system or radio access mode, or vice versa;
+- Selective operation at a geographical boundary, with extensive UTRAN coverage on one side and extensive coverage from another radio system on the other side;
+- Geographically co-located areas of UTRAN coverage and another radio system.
+
+However the specifications should impose no restrictions or assumptions on how an operator might deploy or operate the network in both GERAN and UTRAN.
+
+### 4.3.2 Inter PLMN Handover Issues
+
+Handovers to support service continuity between PLMNs should remain an optional feature to implement. It is envisaged that handover would take place due to changing radio conditions caused e.g. by movement of the terminal causing it to leave the coverage area of a PLMN.
+
+The following networks may be involved with an inter-PLMN handover procedure. These concepts are illustrated in Annex A:
+
+- The user's *home network*, i.e. the operator where the user's subscription may be found;
+- The user's *visited network* where the subscriber user is currently registered, i.e. the network where the subscriber user has performed the last successful update location procedure. As long as the subscriber user is roaming
+
+within the home network, home and visited network are identical;
+
+- The user's *serving network* covering the cell that serves the subscriber. After successful completion of the update location update procedure, the serving network is identical with the visited network. After an inter-PLMN handover, the visited network is different from the serving network until a location update procedure has been successfully completed (excepted the case that the subscriber returns into the visited network);
+- The *target network* covering candidate target cell(s) for inter-PLMN handover. The target network has overlapping radio coverage with the serving network but not necessarily with the visited network.
+
+The minimum requirements for inter-PLMN HO are:
+
+- Continuity of an *active call* across the handover procedure, where this would be possible for intra-PLMN handover;
+- The decision whether the handover request is accepted must be taken by the target network.
+
+### 4.3.3 Charging and Network Management
+
+Means shall be standardised which allow charging records to record the time of handover in the case of inter-PLMN operator handover. Charging records must be able to reflect the level of UTRA radio access, operation mode and network type after handover.
+
+A capability to provide network management information relating to frequency of occurrence and type of handover should be defined.
+
+### 4.3.4 Cost and efficiency
+
+The UTRAN specifications shall facilitate the cost-effective implementation both on the network and on the terminal side, of multi mode operation between GERAN and UTRAN. Impacts on networks based on earlier releases shall be minimised. Such handover shall not require user intervention.
+
+### 4.3.5 Security
+
+Security requirements should embody the principle that handover shall not compromise the security of the network providing the new radio resources; the (possibly different) network providing the original radio resources; and the UE. The security mechanisms should also cater for appropriate authentication processes and meet the requirements of national administrations in terms of lawful interception.
+
+## 4.4 Performance Requirements
+
+### 4.4.1 Temporary degradation of service caused by handover
+
+During intra UTRAN handover or handover from UTRAN to GERAN, degradation of service shall be no greater than during intra GERAN handover.
+
+The duration of the discontinuity experienced by PS and CS real time services should be shorter than that in the handover of CS speech calls over GERAN.
+
+# --- 5 Requirements for Handover
+
+## 5.1 Handover due to UE Movement
+
+It should be possible to provide a technical implementation of handover such that there is no measurable impact on the quality of any service when handover due to UE movement occurs. This does not imply that all handovers will achieve this ideal. However, the specifications shall define at least one UTRA radio access mode in which this is possible given the following:
+
+- UE speed stays within limits for given service;
+- UE stays constantly within UTRA coverage of a single UTRAN.
+
+When there is handover to a new cell with different radio conditions and if a PS sessions is unable to maintain the required quality of service, the QoS of the sessions may be modified to lower quality to continue communication.
+
+## 5.2 Handover due to negotiated service requirement
+
+In order to allow the connection with the negotiated bearer- or teleservice to be established, means shall be defined, which makes it possible for the core network, to recommend to access network to handover the UE to another RAT better suited to support the desired bearer- or teleservice.
+
+## 5.3 Handover between Radio Access Modes
+
+The specifications shall permit a technical implementation of handover between radio access modes, although there may be a temporary degradation of QoS on bearer services at the time of handover.
+
+## 5.4 Cell capacity
+
+Consideration must be given services such as multimedia, which may involve use of multiple bearers. Due for example to cell loading, it may happen that a target cell cannot support the combination of bearer services provided by the current serving cell. Although all bearer services may not be handed over, the handover to another cell should not be precluded.
+
+## 5.5 Handover of a Multicall
+
+The handover event can trigger changes to individual calls in any multicall scenario.
+
+It shall be possible to handover all the calls in a multicall configuration. If the target system is UTRAN and the target cell is not able to accommodate all the calls in a multicall configuration, then the calls that are handed over are selected according to operator preferences. If the target system is GERAN, then the call that is handed over shall be selected in following order:
+
+- i The call of teleservice emergency call ;
+- ii The call of teleservice telephony;
+- iii The call of any other type according to operator preferences.
+
+Calls that cannot be handed over will be released.
+
+A change in the availability of suitable radio resources may also occur for other reasons in addition to handover.
+
+## 5.6 Access Rights
+
+It shall be possible to prevent handover to cells to which the UE does not have access rights. In this case, a handover to allowed cells shall be attempted. For this release this requirement only applies for UTRAN to UTRAN and UTRAN to GERAN handover in both A/Gb and Iu mode.
+
+## 5.7 Handover for shared networks
+
+Handover shall be supported within a shared network and between a shared network and a non-shared network.
+
+The requirements that apply to inter PLMN handover between non-shared networks shall equally apply to inter PLMN handover between shared networks as well as between a shared and a non-shared network.
+
+The network shall be able to make the decision on the most appropriate candidate for handover based on any
+
+combination of the following information:
+
+- type of subscription (e.g. prepay / postpay)
+- home network of the subscriber
+- access rights
+- connected core network
+
+NOTE: Access rights describe which of the candidates for handover a subscriber is allowed to access. The access rights are granted by the home PLMN on a subscriber by subscriber basis.
+
+# --- 6 Requirements for Handover from UTRAN to GERAN
+
+## 6.1 Operational Requirements
+
+### 6.1.2 GERAN bands
+
+The standard shall support handover to any combination of GERAN bands supported by the specifications.
+
+## 6.2 Performance Requirements
+
+The following service principles apply to performance requirements:
+
+- When the UE performs handover to GERAN then the service requirements of GERAN that relate to handover between different cells in different location areas is taken as the benchmark. It is not the intention to set more stringent service requirements for UTRAN to GERAN handover than are already commonly accepted for handover within GERAN.
+
+### 6.2.1 Detection Time of Potential GERAN Handover Candidates
+
+Means shall be defined which allow the UE to achieve as good detection time performance as the GERAN benchmark: i.e. to behave in such a way as to detect potential handover candidates as quickly as a mobile performing an intra GERAN handover is required to do so.
+
+### 6.2.2 Number of GERAN handover candidates to detect
+
+Means shall be available which allow UE to detect an equal number of GERAN handover candidates relative to the GERAN benchmark, i.e. to behave in such a way as to detect as many potential handover candidates as a mobile performing an intra GERAN handover is required to do so.
+
+### 6.2.3 Probability of Connection Loss
+
+The service requirement is that it should be possible to hand over to GERAN from UTRAN with a probability of connection loss that fulfils the corresponding service requirement for intra GERAN handover.
+
+## 6.3 Specific Requirements for Individual Services from UTRAN to GERAN
+
+### 6.3.1 Speech
+
+Handover of a CS Speech teleservice (TS11) from UTRAN to GERAN is required. This requirement also applies to emergency calls (TS12):
+
+- Any call based on the default UTRAN speech codec (AMR) shall be mapped to the FR GSM speech codec. In the case the terminal and the GERAN network support AMR and /or EFR and/or HR, it shall be the operators choice to define the appropriate mapping.
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for speech handover.
+
+### 6.3.2 Short Message Service
+
+There are no requirements related to handover for short message service.
+
+### 6.3.3 Cell Broadcast
+
+There are no requirements related to handover for cell broadcast.
+
+### 6.3.4 USSD
+
+The technical specifications shall provide means to ensure that any handover that occurs during a USSD interaction need no more affect the service than intra-GERAN handover.
+
+### 6.3.5 Facsimile
+
+It is not required that a facsimile transmission that is active between UE and network at the time of handover from UTRAN to GERAN completes successfully.
+
+### 6.3.6 Data Bearer Services
+
+#### 6.3.6.1 Circuit Switched Data
+
+Specifications shall be defined to permit the possibility of handover of a UTRAN data bearer service to GERAN
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for data bearer service handover.
+
+#### 6.3.6.2 Packet Switched Data
+
+It is required to handover a user PS context between GERAN and UTRAN. Independently of the used air interface, the user shall stay connected to an external network (internet, intranet).
+
+### 6.3.7 Supplementary Services
+
+Control and use of Supplementary Services should not be effected by a handover to GERAN.
+
+## 6.4 Requirements on multiple bearer services handover from UTRAN to GERAN
+
+Consideration must be given to services that may involve multiple bearer services. The mapping between UTRAN bearer services and GERAN bearer services will depend upon many factors such as data rate, delay constraints, error rate etc. In the event certain UTRAN bearer services cannot be handed over to GERAN, the handover of some of the bearers to maintain the service should not be precluded.
+
+In the case where user equipped with a dual mode terminal is in UTRAN coverage and has multiple PDP contexts activated (for instance to support multimedia) then it is preferable to handover one PDP context, rather than dropping all of them.
+
+As a first priority only the PDP contexts which have an associated QoS that can be supported by the GERAN should be candidates for handover.
+
+If there are still multiple PDP contexts as "handover candidates" then it shall be an operator choice which PDP context will be maintained. When roaming this decision shall be taken by the serving network. The operator may choose to either;
+
+- a) Drop all of the PDP contexts.
+- b) Choose one based upon criteria such as duration, amount of traffic transferred, etc.
+
+In case of UTRAN to GERAN handover of a **Multicall** only one call can be handed over.
+
+# --- 7 Requirements for Handover from GERAN to UTRAN
+
+## 7.1 Operational Requirements
+
+### 7.1.2 GERAN bands
+
+The standard shall support handover from any combination of GERAN bands supported by the GERAN specifications.
+
+## 7.2 Performance Requirements
+
+During handover from GERAN to UTRAN, temporary degradations shall be no greater than for intra-GERAN handovers.
+
+## 7.3 Specific Requirements for Individual Service Handover from GERAN to UTRAN
+
+### 7.3.1 Speech
+
+AMR, EFR, FR and HR calls shall be mapped to the default UTRAN speech codec.
+
+### 7.3.2 Short Message Service
+
+There are no requirements related to handover for short message service.
+
+### 7.3.3 Cell Broadcast
+
+There are no requirements related to handover for cell broadcast.
+
+### 7.3.4 USSD
+
+The technical specifications shall provide means to ensure that any handover that occurs during a USSD interaction need no more affect the service than intra-GERAN handover.
+
+### 7.3.5 Facsimile
+
+It is not required that a facsimile transmission that is active between UE and network at the time of handover from GERAN to UTRAN completes successfully.
+
+### 7.3.6 Data Bearer Services
+
+#### 7.3.6.1 Circuit Switched Data
+
+Specifications shall be defined to permit the possibility of handover of a data bearer from GERAN to UTRAN.
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for circuit switched data handover.
+
+#### 7.3.6.2 Packet Switched Data
+
+It is required to handover a user context between GERAN and UTRAN. Independently of the used radio interface, the user shall stay connected to an external network (internet, intranet). Any change in the QoS shall be seen at the service access points as a network initiated renegotiation of QoS. If the supported QoS is not acceptable, the UE/user may terminate the connection/context.
+
+Means shall be defined which make it possible to limit any temporary degradation on handover so it meets the performance specified by GERAN service requirements for packet switched data handover.
+
+### 7.3.7 Supplementary services
+
+Control and use of Supplementary Services should not be effected by a handover to UTRAN.
+
+## 7.4 Requirements on multiple bearer services handover from GERAN to UTRAN
+
+Consideration must be given to services that may involve the use of multiple bearer services. For example Class A GPRS terminals will be capable of simultaneously supporting more than one data bearer services. Means shall be defined to allow handover of several data bearer services from GERAN to UTRAN
+
+# --- 8 Cross Phase Compatibility for this release
+
+This section details the cross phase compatibility requirements relating to the service requirements in this document.
+
+Note: When a change is introduced which affects the 3GPP technical specifications, it is said to be 'backward compatible' if existing equipment can continue to operate and perform correctly with equipment that conforms to the new implementation.
+
+## 8.1 Compatibility with Existing Specifications
+
+Where the service and operational requirements in this document relate to a GERAN, compatibility is required with systems conforming to the R99 or later GERAN specifications.
+
+## 8.2 Compatibility with Future 3GPP specifications
+
+The specifications that define the technical implementation of this release should be developed in such a way that it is practical to add the requirements in this section in a backward compatible manner.
+
+### 8.2.1 Requirements for Service Capabilities
+
+3GPP standardises service capabilities, not services. As part of the service capabilities it is envisaged that applications may wish to respond to events related to handover that either has occurred, is about to occur or could potentially occur. The service capabilities described in this section should be available at least to UE hosted applications.
+
+The following list of uses is provided as an example and is not intended to be exhaustive:
+
+- An application may wish to accept or reject offered QoS;
+- An application may wish to cope to the effect that handover has on a service, for example facsimile retransmission;
+- An application may wish to preferentially choose radio resources.
+
+It is therefore required that the service capability set available to an application be able to provide an indication that handover has occurred or could occur with information about the type of handover and radio resources involved. The service capabilities should support QoS negotiation.
+
+### 8.2.2 Inter PLMN Handover Issues
+
+The minimum requirements for inter-PLMN HO are:
+
+- The ability to check with the home network whether the user is permitted to handover from the visited network to a target network.
+- Invocation of the handover procedure only occurs if the target network provides the radio channel type required for the respective call;
+- The avoidance of "network hopping", i.e. successive handover procedures between neighbouring networks for the same call;
+- The possibility of user notification of inter-PLMN HO (e.g. possible tariff change) when it occurs.
+
+### 8.2.3 Handover between Environments
+
+UMTS is expected to provide coverage in a number of environments including fixed and mobile as described in the table below. The technical specifications should not preclude the possibility of implementing these requirements in a backward compatible manner.
+
+| From \ To | Terrestrial Cellular | Fixed/Cordless | Satellite |
+|----------------------|----------------------|----------------|-----------|
+| Terrestrial Cellular | Yes (R99) | Yes | Yes |
+| Fixed/Cordless | Yes | Yes | Yes |
+| Satellite | Yes | Yes | No |
+
+## 8.3 Support of Multicall with Simultaneous Voice Calls
+
+In the case where Multicall is used to support multiple voice calls a handover must be attempted for each bearer that is in use. In the case where not all bearers can be supported by the destination network the related voice calls shall be automatically put on hold. After the handover is completed, the subscriber shall be able to retrieve any held voice call by invoking the Call Hold service.
+
+This requirement is dependent on the user subscribing to Call Hold.
+
+This is only required if there is more than one simultaneous speech call and this is therefore not required for this release.
+
+# Annex A (informative): Illustration of elements in inter-PLMN handover
+
+Figure 1 illustrates the above definitions taking an example of European GSM networks. The subscriber's home network is France. The visited network where the subscriber is registered in a VLR is Germany. The signalling connection between HLR and VLR is indicated by dotted lines. The calls for the subscriber are controlled by the MSC collocated to the VLR where the subscriber is registered. This MSC is called "*anchor MSC*".
+
+Handover to a different MSC may occur if the cell serving the subscriber after handover is not controlled by the anchor MSC. This MSC is called the "*serving MSC*". Even after the call has been handed over to a different MSC, the call control function remains in the anchor MSC. The signalling connection and circuit switched connection established between anchor MSC and serving MSC are indicated by a solid line.
+
+When the French subscriber registered in a German network roams near the border to the Netherlands, inter-PLMN handover may occur. In this case a Dutch network is the *target network*. After handover, the anchor MSC located in a German network continues to control the call. The German network remains the *visited network* where the subscriber is registered. The subscriber's location information stored in the HLR remains unchanged. The signalling and circuit switched connections between the anchor MSC and the previously serving MSC in the German network will be released when the User Equipment (UE) is served by a cell within a Dutch network. The Dutch network becomes the *serving network*. From the Dutch network the subscriber may be handed over to a Belgian network.
+
+
+
+The diagram shows a map of Western Europe with several network elements overlaid. France is shown in green, Germany in light green, the Netherlands in light blue, Belgium in light pink, and Luxembourg in light yellow. A mobile phone icon is at the top left, with dashed lines pointing to cell towers in Germany (1), the Netherlands (2), and Belgium (3). In France, there is a yellow cylinder labeled 'HLR' and two yellow boxes labeled 'Gateway MSC'. In Germany, there are two yellow boxes labeled 'MSC' and a yellow box labeled 'VLR'. One MSC is connected to the HLR via a dotted line. Another MSC is connected to the Gateway MSC via a solid line. In the Netherlands, there is a pink box labeled 'MSC' connected to the Gateway MSC via a solid line. In Belgium, there is a pink box labeled 'MSC' connected to the Gateway MSC via a solid line. The diagram illustrates the network architecture for inter-PLMN handover, showing the flow of signalling and data between the home network and visited networks.
+
+Diagram illustrating inter-PLMN handover elements across France, Germany, Netherlands, Belgium, and Luxembourg. It shows the Home Location Register (HLR) in France, Visiting Location Registers (VLRs) and Mobile Switching Centers (MSCs) in Germany, and MSCs in the Netherlands and Belgium. Dotted lines represent signalling connections between the HLR and VLRs. Solid lines represent circuit-switched connections between the anchor MSC and serving MSC. A mobile phone icon represents the User Equipment (UE).
+
+Fig. 1: Example for Inter-PLMN handover
+
+Figure 1: Example for inter-PLMN handover
+
+# --- Annex B (informative): Open Points on Inter-Operator Handover
+
+The requirements outlined below are likely to need further elaboration, although these may be outside the scope of service requirements.
+
+## --- B.2 Selection of Target Cells for Handover
+
+A mechanism is envisaged to support the selection of the target cell for handover. The target cell may be part of the serving network or part of another network.
+
+## --- B.3 Network Information Exchange
+
+A mechanism is envisaged to support the exchange of network information between different operators. Two categories of network information are identified:
+
+- static information, for example, neighbour cell lists, interconnecting traffic and signalling links, etc.;
+- dynamic information, for example real-time signalling information related to target cell selection, etc.
+
+## --- B.4 Service Requirements
+
+FFS.
+
+[There is a need to identify which services can be maintained during handover and the interactions of services across network boundaries]
+
+## --- B.5 Billing, Accounting and Charging Requirements
+
+FFS.
+
+# Annex C (informative): Change history
+
+| Document history | | |
+|------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | |
+| 0.0.1 | 29 Oct 98 | First Draft for tdoc |
+| 0.0.2 | 5 Jan 98 | Evolved from tdoc 3 then 7 of SMG 1 handover ad hoc |
+| 0.0.3 | 6 Jan 98 | evolved from tdoc 20 of SMG1 handover ad hoc |
+| 0.0.4 | 7 Jan 98 | evolved from tdoc 35 of SMG1 handover adhoc |
+| 0.0.5 | 8 Jan 98 | Evolved from tdoc 45 of SMG1 handover adhoc |
+| 1.0.0 | 27 January | To be presented as version 1.0.0 to SMG#28 for Approval |
+| 1.1.0 | 5 Mar 99 | - - new requirement for inter-operator handover, as demanded by SMG
- - removes text on security requirements by referencing 33.21
- - editorial revisions
|
+| 1.2.0 | 22 Mar 99 | - 1 Initial draft for email handover ad hoc 22-27 Mar.
- -
|
+| 1.3.0 | 24 Mar 99 | Clarify inter-operator handover requiremetn |
+| 1.4.0 | 26 Mar 99 | Proposed as draft version 2.0.0 |
+| 2.0.0 | 12 Apr 99 | Draft version 2.0.0 |
+| 2.0.1 | 12 Apr 99 | Editorially equivalent 2.0.0, with editorial comments removed |
+| 2.0.2 | 16 April 99 | Editorial review |
+| 3.0.0 | | |
+| 3.1.0 | October 1999 | Inclusion of CRs at SA#5 |
+| 3.2.0 | December 1999 | Inclusion of CRs at SA#6 |
+| 3.3.0 | June 2000 | Inclusion of CRs at SA#8 |
+| 4.0.0 | October 2000 | Inclusion of CRs at SA#9 |
+| 4.1.0 | January 2001 | Inclusion of CRs at SA#10 |
+| 4.2.0 | March 2001 | Inclusion of CRs at SA#11 |
+
+| Change history | | | | | | | | | | | |
+|----------------|----------|----------|--------|-----|-----|-----|-----|--------------------------------------------------------|-------|-------|----|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-05 | SP-99436 | S1-99500 | 22.129 | 002 | | R99 | F | SMS handover requirement clarification | 3.0.0 | 3.1.0 | |
+| SP-05 | SP-99436 | S1-99516 | 22.129 | 003 | | R99 | D | Removal of out-of-date appendix | 3.0.0 | 3.1.0 | |
+| SP-05 | SP-99436 | S1-99533 | 22.129 | 004 | | R99 | D | Editorial improvements of definitions and alignment of | 3.0.0 | 3.1.0 | |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|--------------------------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| | | | | | | | | terminology | | | |
+| SP-05 | SP-99436 | S1-99540 | 22.129 | 005 | | R99 | C | To elucidate 1-1 handover principle for R99 | 3.0.0 | 3.1.0 | |
+| SP-05 | SP-99436 | S1-99541 | 22.129 | 006 | | R99 | D | Clarification of the scope of mandatory requirements | 3.0.0 | 3.1.0 | |
+| SP-05 | SP-99483 | S1-99565 | 22.129 | 007 | 1 | R99 | C | Removes all non-R99 requirements, by changing them into Cross phase compatibility requirements which apply to R99. | 3.0.0 | 3.1.0 | |
+| SP-06 | SP-99553 | S1-99877 | 22.129 | 008 | | R99 | D | Editorial CR to 22.129 | 3.1.0 | 3.2.0 | |
+| SP-06 | SP-99523 | S1-991019 | 22.129 | 009 | | R99 | D | 3G/2G handover in the PS Domain | 3.1.0 | 3.2.0 | |
+| SP-06 | SP-99523 | S1-991066 | 22.129 | 010 | | R99 | B | Handover of a Multicall | 3.1.0 | 3.2.0 | |
+| SP-06 | SP-99521 | S1-99868 | 22.129 | 011 | | R99 | C | Performance requirements for real time services and requirements for handover between UMTS and GPRS | 3.1.0 | 3.2.0 | |
+| SP-08 | SP-000205 | S1-000349 | 22.129 | 012 | | R99 | F | Alignment of handover requirements for Multicall | 3.2.0 | 3.3.0 | |
+| SP-09 | SP-000426 | S1-000574 | 22.129 | 013 | | R99 | F | Removal of requirements for SoLSA support | 3.3.0 | 3.4.0 | |
+| SP-09 | SP-000389 | S1-000613 | 22.129 | 014 | | R4 | B | Bearer Modification without pre-notification | 3.3.0 | 4.0.0 | |
+| SP-10 | SP-000534 | S1-000863 | 22.129 | 015 | | R99 | F | Handover requirements | 3.4.0 | 3.5.0 | |
+| SP-10 | SP-000534 | S1-000864 | 22.129 | 016 | | Rel-4 | A | Handover requirements | 4.0.0 | 4.1.0 | TEI4 |
+| SP-11 | SP-010061 | S1-010251 | 22.129 | 017 | | Rel-4 | D | Editorial CR to correct references to releases | 4.1.0 | 4.2.0 | CORRECT |
+| SP-12 | SP-010264 | S1-010553 | 22.129 | 018 | | Rel-4 | F | Bearer modification without pre-modification | 4.2.0 | 4.3.0 | BMWPN |
+| SP-12 | SP-010245 | S1-010353 | 22.129 | 019 | | Rel-4 | F | Inter PLMN handover | 4.2.0 | 4.3.0 | Handover |
+| SP-13 | SP-010434 | S1-010859 | 22.129 | 020 | 1 | Rel-5 | B | Release 5 IMS Service Continuity Requirements | 4.3.0 | 5.0.0 | IMS |
+| SP-14 | SP-010670 | 1289 | 22.129 | 025 | | Rel-5 | A | Multicall handover requirements | 5.0.0 | 5.1.0 | |
+| SP-16 | SP-020250 | S1-021093 | 22.129 | 026 | | Rel-5 | F | CR to TS 22.129 on access rights in connected mode | 5.1.0 | 5.2.0 | TEI |
+| SP-19 | SP-030035 | S1-030271 | 22.129 | 027 | - | Rel-6 | B | Netshare CR to TS 22.129 on Requirements for Network Sharing in Rel-6 | 5.2.0 | 6.0.0 | NTShar-CR |
+| SP-22 | SP-030704 | S1-031300 | 22.129 | 028 | 4 | Rel-6 | B | Service based handover/assignment | 6.0.0 | 6.1.0 | TEI |
+| SP-31 | - | - | 22.129 | - | - | Rel-7 | | Rel-7 created as a result of applying CR 0029 from SA #31 to Rel-6 in order to create Rel-8 | 6.1.0 | 7.0.0 | - |
+| SP-31 | SP-060208 | - | 22.129 | 0029 | 1 | Rel-8 | F | Introduction of reference to the AIPN Stage 1 in TS 22.129 | 6.1.0 | 8.0.0 | AIPN |
+| SP-38 | SP-070855 | S1-071839 | 22.129 | 0030 | 1 | Rel-8 | B | Introduction of reference to EPS Stage 1 in TS 22.129 | 8.0.0 | 8.1.0 | AIPN-SAE |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.1.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | - | - | - | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22135/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22135/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8f35ed4ad64a5771a78716a809b4481c0cc696a
--- /dev/null
+++ b/marked/Rel-18/22_series/22135/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d96a5e1d24270e40e89830d626000b3dc4d21ddb69cbde16575c14fe9d9631d7
+size 8182
diff --git a/marked/Rel-18/22_series/22135/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22135/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc6bc4f813adced92c024b660eb55ff5795770bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22135/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15fd4ae7c319660070fc3dfc8ffa883ed6d9d537e4ba645f4999849854f69b74
+size 7354
diff --git a/marked/Rel-18/22_series/22135/64fd8bd804acee34ea91bdde28997fe3_img.jpg b/marked/Rel-18/22_series/22135/64fd8bd804acee34ea91bdde28997fe3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07e1a323045ebb4f9a3235c0c4581cd897022594
--- /dev/null
+++ b/marked/Rel-18/22_series/22135/64fd8bd804acee34ea91bdde28997fe3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d0b179d0a16ecaf745c867de77d4604553c1ebe8d55d15b9960ebb036371d43
+size 26151
diff --git a/marked/Rel-18/22_series/22135/raw.md b/marked/Rel-18/22_series/22135/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4259d091bde1197995034102f052c54246f3386a
--- /dev/null
+++ b/marked/Rel-18/22_series/22135/raw.md
@@ -0,0 +1,632 @@
+
+
+# 3GPP TS 22.135 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multicall; Service description; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring the text "5G" in a large, bold, black font with "ADVANCED" in smaller letters to the right. Above the "5G" is a green graphic consisting of three curved lines representing signal waves.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "G" has a red signal wave icon at its base. A small "TM" trademark symbol is located to the upper right of the "P".
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+LTE, UMTS, multicall, supplementary service;
+stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|------------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 4 Description..... | 7 |
+| 4.1 Description of multicall..... | 7 |
+| 4.2 Applicability to telecommunication services..... | 7 |
+| 5 Functional requirements..... | 7 |
+| 5.1 Provision..... | 7 |
+| 5.2 Withdrawal..... | 7 |
+| 5.3 Registration ..... | 8 |
+| 5.4 Erasure..... | 8 |
+| 5.5 Activation..... | 8 |
+| 5.6 Deactivation ..... | 8 |
+| 5.7 Invocation..... | 8 |
+| 5.8 Interrogation ..... | 8 |
+| 5.9 Call related procedures..... | 8 |
+| 5.9.1 Terminating CS call..... | 8 |
+| 5.9.2 Originating CS call ..... | 9 |
+| 5.10 Charging requirements ..... | 9 |
+| 6 Exceptional procedures or unsuccessful outcome ..... | 9 |
+| 6.1 Exceptional operation or unsuccessful outcome ..... | 9 |
+| 6.2 Registration ..... | 9 |
+| 6.3 Erasure..... | 9 |
+| 6.4 Activation..... | 10 |
+| 6.5 Deactivation ..... | 10 |
+| 6.6 Invocation..... | 10 |
+| 6.7 Interrogation ..... | 10 |
+| 6.8 Roaming in non-supporting networks ..... | 10 |
+| 7 Interaction with other services ..... | 10 |
+| 7.1 Line Identification ..... | 10 |
+| 7.1.1 Calling Line Identification Presentation (CLIP) ..... | 10 |
+| 7.1.2 Calling Line Identification Restriction (CLIR) ..... | 10 |
+| 7.1.3 Connected Line Identification Presentation (COLP)..... | 10 |
+| 7.1.4 Connected Line Identification Restriction (COLR) ..... | 10 |
+| 7.2 Call Forwarding..... | 11 |
+| 7.2.1 Call Forwarding Unconditional (CFU) ..... | 11 |
+| 7.2.2 Call Forwarding on Busy (CFB) ..... | 11 |
+| 7.2.3 Call Forwarding on No Reply (CFNRy) ..... | 11 |
+| 7.2.4 Call Forwarding on Not Reachable (CFNRc) ..... | 11 |
+| 7.3 Call Completion ..... | 11 |
+| 7.3.1 Call Hold (CH) ..... | 11 |
+| 7.3.2 Call Waiting (CW) ..... | 11 |
+| 7.4 Multi Party (MPTY)..... | 12 |
+| 7.5 Closed User Group (CUG)..... | 12 |
+| 7.6 Advice of Charge (AoC)..... | 12 |
+| 7.7 Call Barring..... | 12 |
+| 7.7.1 Barring of all outgoing calls ..... | 12 |
+| 7.7.2 Barring of outgoing international calls ..... | 12 |
+| 7.7.3 Barring of outgoing international calls except those directed to the HPLMN country ..... | 12 |
+| 7.7.4 Barring of all incoming calls ..... | 12 |
+| 7.7.5 Barring of incoming calls when roaming ..... | 12 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------------------------|-----------|
+| 7.8 | Explicit Call Transfer (ECT)..... | 12 |
+| 7.9 | Completion of Call to Busy Subscriber (CCBS)..... | 13 |
+| 7.10 | Multiple Subscriber Profile (MSP) ..... | 13 |
+| 7.11 | Calling Name Presentation (CNAP) ..... | 13 |
+| 7.12 | User-to-User Signalling (UUS)..... | 13 |
+| 7.13 | enhanced Multi-Level Precedence and Pre-emption service (eMLPP) ..... | 13 |
+| 7.14 | Call Deflection (CD)..... | 13 |
+| 8 | Interaction with other network features and services..... | 13 |
+| 8.1 | CAMEL..... | 13 |
+| 8.2 | IST ..... | 13 |
+| 8.3 | ODB ..... | 13 |
+| 8.4 | Emergency Calls ..... | 13 |
+| Annex A (normative): | Busy definition ..... | 15 |
+| Annex B (informative): | Cross Phase Compatibility ..... | 16 |
+| B.1 | Compatibility With Existing Standards ..... | 16 |
+| B.2 | Compatibility With Future Releases ..... | 16 |
+| B.2.1 | Multicall configuration..... | 16 |
+| B.2.2 | Several simultaneous speech calls / bearers..... | 17 |
+| B.2.3 | CCBS..... | 17 |
+| Annex C (informative): | Change history..... | 18 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document presents describes Multicall supplementary service.
+
+The general aspects, including definitions and recommended provision, of the description of the 3GPP Supplementary Services are given in 3GPP TS 22.004.
+
+# 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 TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
+- [2] 3GPP TS 22.004: "General on Supplementary Services".
+- [3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".
+- [4] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
+- [5] 3GPP TS 22.100: "UMTS Phase 1 Release 99".
+- [6] 3GPP TS 22.129: "Handover Requirement between UTRAN and GERAN or other Radio Systems".
+- [7] 3GPP TS 22.097: "Multiple Subscriber Profile (MSP) ".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+**CS Call:** Circuit switched call. A call routed through CS domain. CS call can be for example a speech call, fax call or data call. One call shall only use one bearer at the time
+
+**Multiparty:** Supplementary Service for speech conference service
+
+**Ncs\_MO:** maximum number of simultaneous mobile originating CS calls. The value of The Value of Ncs\_MO is 7. If Ncs\_MO has been reached, no more MO calls can be set-up
+
+**Ncs\_MT:** Maximum number of simultaneous mobile terminating CS calls. The value of Ncs\_MT is 7. If Ncs\_MT has been reached, additional MT call attempts shall fail without any indication to the called subscriber
+
+**Nbr:** Maximum number of simultaneous CS bearers. The value of Nbr is the smallest value within the Nbr\_User, Nbr\_UE, and Nbr\_SN
+
+**Nbr\_User:** Maximum number of simultaneous CS bearers allowed, as defined by the user within the limits given by Nbr\_SB
+
+$N_{br\_SB}$ : Maximum number of simultaneous CS bearers allowed, defined by the service provider in the Multicall subscription
+
+$N_{br\_UE}$ : Maximum number of simultaneous CS bearers supported by the UE
+
+$N_{br\_SN}$ : Maximum number of simultaneous CS bearers supported by the serving network
+
+# --- 4 Description
+
+## 4.1 Description of multicall
+
+The Multicall supplementary service enables a mobile subscriber to have several simultaneous CS calls, each call using its own dedicated bearer.
+
+Only one CS bearer can used for speech at any one times.
+
+A speech call is one of TS11 (Telephony), TS12 (Emergency Calls), and TS61 (Alternate speech/fax). If the bearer capability information is not available, e.g. the call is originated/transited by a PSTN, the basic service cannot be deduced and the network shall, for multicall purposes, handle the call as telephony.
+
+A held call shall be regarded as using the bearer used while the call was active.
+
+NOTE: The 3GPP protocol architecture allows several parallel CS calls, the limitation being that there is only one traffic channel in GERAN, which the different CS calls share. This is facilitated by e.g. the Call Waiting, Call Hold, Call Transfer and Multiparty Supplementary Services. Call configurations related to supplementary services are not considered as Multicall. See clause 7 for interaction.
+
+It shall be possible for each CS call to use a dedicated bearer of independent traffic and performance characteristics. It shall be possible to release each active CS call independently of any other CS call.
+
+## 4.2 Applicability to telecommunication services
+
+The applicability of this Supplementary Service is defined in 3GPP TS 22.004.
+
+# --- 5 Functional requirements
+
+## 5.1 Provision
+
+Multicall is provided by prior arrangement with the service provider.
+
+Multicall shall be provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not to any subset of these BS.
+
+When the Multicall supplementary service is provisioned the maximum number of simultaneous CS bearers available to the subscriber ( $N_{br\_SB}$ ) shall be defined as part of the subscription. The value for $N_{br\_SB}$ shall in the range from 2 up to 7.
+
+## 5.2 Withdrawal
+
+It shall be possible to withdraw the Multicall supplementary service subscription on request of the subscriber or for administrative reasons.
+
+## 5.3 Registration
+
+The user shall be able to modify the maximum number of CS bearers available ( $N_{br\_User}$ ) within the limitations set by the service provider. ( $N_{br\_SB}$ ).
+
+If the subscriber attempts to register a value for $N_{br\_User}$ that is higher than the value of $N_{br\_SB}$ , the request shall be rejected and the subscriber shall be informed on the unsuccessful outcome on the request.
+
+## 5.4 Erasure
+
+Data related to the Multicall supplementary service shall be erased by the service provider as a result of withdrawal.
+
+## 5.5 Activation
+
+The Multicall supplementary service shall be activated by the service provider as a result of provision.
+
+## 5.6 Deactivation
+
+The Multicall supplementary service shall be deactivated by the service provider as a result of withdrawal.
+
+## 5.7 Invocation
+
+The Multicall supplementary service shall be invoked by the system when at least one call is in progress and another call with a dedicated bearer is to be set up. The Multicall service applies to mobile originating and mobile terminating calls.
+
+## 5.8 Interrogation
+
+The user shall be able to interrogate the network for the values of $N_{br\_User}$ , $N_{br\_SB}$ and $N_{br\_SN}$ .
+
+## 5.9 Call related procedures
+
+### 5.9.1 Terminating CS call
+
+The indication of a terminating CS call to the mobile terminal will be done by the Multicall supplementary service until either the maximum number of bearer ( $N_{br}$ ) or the maximum number of CS mobile terminating calls ( $N_{cs\_MT}$ ) has been reached.
+
+If the maximum number of terminating calls ( $N_{cs\_MT}$ ) has been reached, and additional terminating call shall be reject without any indication to the subscriber.
+
+If the maximum number of bearers ( $N_{br}$ ) has been reached an additional terminating call will be only indicated to the user if the user has the Call Waiting supplementary service active, see chapter 7.4.2 for interactions with Call Waiting.
+
+If $N_{br}$ and $N_{cs\_MT}$ havenot been reached, a terminating call is indicated to the user and she may react in the following way:
+
+- a) Accept the terminating call:
+ - The user/user applications shall have the possibility to allocate a new bearer for the terminating call.
+ - If the user has the Call Hold SS active, the user shall have the possibility to reuse/share an already established bearer (e.g. release existing calls or put an speech on hold and accept the terminating call).
+- b) Rejecting the terminating call:
+ - If the user rejects the terminating call the call shall be released in a normal way.
+
+c) Ignore the incoming call:
+
+- If the user ignores the indication of the terminating call (i.e. neither accepts nor rejects it ), the normal call handling shall apply, e.g. after the Alerting Timer expires the call will be released.
+
+If there is a terminating speech call attempt and an ongoing speech call (active or held), the terminating call shall not be indicated to user by the Multicall service. The Call waiting call SS shall be invoked if applicable, see chapter 7.4.2 for interactions with Call Waiting SS.
+
+The user can have possibility to reuse/share a bearer only when she is provisioned for Call Hold SS. See subclause 7.4.1 for interaction with Call Hold SS.
+
+### 5.9.2 Originating CS call
+
+If neither $N_{br}$ nor $N_{cs\_MO}$ have not been reached and the user wants to establish a new originating CS call she may act in the following way:
+
+- a) allocate a new bearer for the originating call;
+- b) reuse/share an already established bearer (e.g. to put an speech on hold and set-up a new call).
+
+The user can have possibility to reuse/share a bearer only when she is provisioned for Call Hold SS. See subclause 7.4.1 for interaction with Call Hold SS. The mobile terminal shall not originate a speech call requesting a new bearer when there is already an active speech call.
+
+## 5.10 Charging requirements
+
+Each of the calls using a dedicated bearer shall be charged individually.
+
+Allocation of a dedicated bearer shall be visible in the charging data.
+
+# 6 Exceptional procedures or unsuccessful outcome
+
+## 6.1 Exceptional operation or unsuccessful outcome
+
+The number of simultaneous CS bearers supported by the system may vary in different regions. For instance, after handover the number of simultaneous bearers available to the served subscriber may be lower than the number of already established bearers. Such events shall trigger changes to individual calls in any multicall scenario.
+
+The handover requirements for multicall are specified in 3GPP TS 22.129 [6].
+
+## 6.2 Registration
+
+If the system cannot accept a registration request, the served mobile subscriber shall receive a notification that Multicall registration was not successful. Possible causes are:
+
+- service not subscribed to;
+- $N_{br\_User} > N_{br\_SB}$ ;
+- insufficient information.
+
+## 6.3 Erasure
+
+No exceptional operation identified.
+
+## 6.4 Activation
+
+No exceptional operation identified.
+
+## 6.5 Deactivation
+
+No exceptional operation identified.
+
+## 6.6 Invocation
+
+If the served subscriber attempts to set up a new call with a dedicated bearer while the maximum number of bearers available to the subscriber ( $N_{br}$ ) has been reached, the call attempt shall be rejected by normal procedures, indicating that no more bearers are available.
+
+## 6.7 Interrogation
+
+When a mobile subscriber who is not provided with the Multicall supplementary service interrogates the service data of the Multicall supplementary service, she shall be notified that she is not subscribed to the service.
+
+## 6.8 Roaming in non-supporting networks
+
+Roaming into networks not supporting the Multicall supplementary service shall be possible. The served subscriber will not have any access to the Multicall supplementary service and the system should behave accordingly.
+
+When the served subscriber performs any procedure related to Multicall service as described in the clauses above while roaming in a non-supporting network, she shall be notified that the service is not available.
+
+# --- 7 Interaction with other services
+
+## 7.1 Line Identification
+
+### 7.1.1 Calling Line Identification Presentation (CLIP)
+
+No impact, i.e. CLIP shall be provided with all calls.
+
+### 7.1.2 Calling Line Identification Restriction (CLIR)
+
+No impact, i.e. CLIR shall be provided with all calls.
+
+### 7.1.3 Connected Line Identification Presentation (COLP)
+
+No impact, i.e. COLP shall be provided with all calls.
+
+### 7.1.4 Connected Line Identification Restriction (COLR)
+
+No impact, i.e. COLR shall be provided with all calls.
+
+## 7.2 Call Forwarding
+
+### 7.2.1 Call Forwarding Unconditional (CFU)
+
+No impact.
+
+### 7.2.2 Call Forwarding on Busy (CFB)
+
+No impact.
+
+NOTE: CFB shall be invoked when the network detects a NDUB condition. The maximum number of bearers available to the subscriber ( $N_{br}$ ) affects the NDUB condition. For the NDUB definition specific for Multicall, see annex A.
+
+This means that for the case of $N_{br} = 1$ , the system behaviour shall be the same as for a subscriber who is not provided with the Multicall service.
+
+### 7.2.3 Call Forwarding on No Reply (CFNRy)
+
+No impact.
+
+### 7.2.4 Call Forwarding on Not Reachable (CFNRc)
+
+No impact.
+
+## 7.3 Call Completion
+
+### 7.3.1 Call Hold (CH)
+
+No impact, i.e. it shall be possible to put an established speech call on hold.
+
+Irrespective of whether the maximum number of CS bearers ( $N_{br}$ ) is reached or not, and a terminating call is indicated to the user, she shall be able to accept the terminating call by applying the Call Hold service to an active speech call. By that she makes the bearer of the held call available to the new call.
+
+NOTE 1: This means that for the case of $N_{br} = 1$ , the system behaviour shall be the same as for a subscriber who is not provided with the Multicall service.
+
+NOTE 2: There is no change to the maximum number of held calls allowed for the Multicall supplementary service. The maximum number of held calls is still 1 per a subscriber.
+
+### 7.3.2 Call Waiting (CW)
+
+When the subscriber has at least one ongoing call and a new terminating call is speech; then Call Waiting shall be invoked if:
+
+- 1) there is an active speech call and Call Waiting is active and operative for speech or;
+- 2) there is a held speech call, with no active call on the same bearer, and Call Waiting is active and operative for speech or;
+- 3) there is a held speech call, with an active non-speech call on the same bearer, and Call Waiting is active and operative for that non-speech basic service or;
+- 4) there are no speech calls (including a call on hold), the maximum number of bearers ( $N_{br}$ ) has been reached and Call Waiting is active and operative for at least one of the basic services currently in use.
+
+When the subscriber has at least one ongoing call and a new terminating call is not speech; then Call Waiting shall be invoked if the maximum number of bearers ( $N_{br}$ ) has been reached and Call Waiting is active and operative for at least one of the basic services currently in use.
+
+NOTE: There is no change to the maximum number of waiting calls allowed for the Multicall service. The maximum number of waiting calls is still 1 per a subscriber.
+
+## 7.4 Multi Party (MPTY)
+
+No Impact.
+
+The number of MPTY member may be limited by $N_{cs\_MO}$ , $N_{cs\_MT}$ and $N_{cs}$ .
+
+## 7.5 Closed User Group (CUG)
+
+No impact.
+
+## 7.6 Advice of Charge (AoC)
+
+The subscriber shall receive the AoC indication individually for each CS call.
+
+For the AoCC service, the ACM (Accumulated Call Meter as defined in TS 22.024) shall reckon the sum of the charge generated by all simultaneous CS calls.
+
+## 7.7 Call Barring
+
+No impact.
+
+### 7.7.1 Barring of all outgoing calls
+
+No impact.
+
+### 7.7.2 Barring of outgoing international calls
+
+No impact.
+
+### 7.7.3 Barring of outgoing international calls except those directed to the HPLMN country
+
+No impact.
+
+### 7.7.4 Barring of all incoming calls
+
+No impact.
+
+### 7.7.5 Barring of incoming calls when roaming
+
+No impact.
+
+## 7.8 Explicit Call Transfer (ECT)
+
+No impact.
+
+## 7.9 Completion of Call to Busy Subscriber (CCBS)
+
+The definition of the IDLE state of subscriber A and destination B is not modified, i.e. a subscriber is considered to be IDLE when all the bearers (calls) for her have been released.
+
+A subscriber to whom CCBS can be invoked shall be regarded as NDUB under the specific NDUB condition for Multicall (See Annex A).
+
+## 7.10 Multiple Subscriber Profile (MSP)
+
+No impact. The Multicall supplementary service shall be provisioned on a per subscriber basis. Nbr\_SN, Nbr\_SB, and Nbr\_user shall apply over all profiles.
+
+## 7.11 Calling Name Presentation (CNAP)
+
+No impact.
+
+## 7.12 User-to-User Signalling (UUS)
+
+No Impact
+
+## 7.13 enhanced Multi-Level Precedence and Pre-emption service (eMLPP)
+
+No impact.
+
+## 7.14 Call Deflection (CD)
+
+No impact.
+
+# --- 8 Interaction with other network features and services
+
+## 8.1 CAMEL
+
+No impact.
+
+## 8.2 IST
+
+No impact.
+
+## 8.3 ODB
+
+No impact.
+
+## 8.4 Emergency Calls
+
+The network shall handle emergency call at first priority. When a user originates an emergency call, the network shall behave as follows:
+
+- The network, which supports Multicall, shall accept the emergency call within the serving network capability regardless of Multicall subscription limitation to the user.
+
+- The MS shall ensure that an emergency call setup request is acceptable to a serving network which does not support multicall, if necessary by releasing one or more existing call.
+
+# --- Annex A (normative): Busy definition
+
+NDUB (Network Determined User Busy) occurs when:
+
+1. The maximum number of mobile terminating calls ( $N_{cs\_MT}$ ) has been reached (NOTE 1).
+2. The maximum number of bearers ( $N_{br}$ ) has been reached and the maximum number of waiting calls has been reached (NOTE 2, NOTE3).
+
+NOTE 1: This can occur even if bearers are still available, e.g. when the MS is engaged in MPTY SS. If the maximum number of mobile terminating calls ( $N_{cs\_MT}$ ) has been reached, the Call Waiting SS cannot be invoked.
+
+NOTE 2: If Call Waiting is provisioned and activated, and when the maximum number of bearers has been reached the Call Waiting SS can be invoked. This case is not regarded as NDUB. See subclause 7.3.2 for interaction with Call Waiting SS.
+
+NOTE 3: According to the speech bearer number limitation, the incoming speech call shall be regarded as encountering NDUB when the MS is engaged in a speech call (including a held call) and Call Waiting SS is not provisioned and activated for the user, irrespective of the further availability of bearers for the user. For the condition under which Call Waiting SS shall be invoked in this case, see subclause 7.3.2.
+
+For User Determined User Busy (UDUB) condition see TS 22.001 Annex C.
+
+# Annex B (informative): Cross Phase Compatibility
+
+This section details the cross phase compatibility requirements relating to the service requirements in this document.
+
+NOTE: When a change is introduced which affects the 3GPP specifications, it is said to be 'backward compatible' if existing equipment can continue to operate and perform correctly with equipment that conforms to the new implementation.
+
+## B.1 Compatibility With Existing Standards
+
+Where the service and operational requirements in this document relate to core network functionality, compatibility is required.
+
+Multicall mechanisms are not applicable for GERAN.
+
+## B.2 Compatibility With Future Releases
+
+It is envisaged that 3GPP standards will evolve in future releases, for example with the addition of new service requirements. The standards which define the technical implementation should be developed in such a way that it is practical to add the requirements in this section in a backward compatible manner.
+
+Following chapters include requirements that are foreseen for future release.
+
+### B.2.1 Multicall configuration
+
+When having one active CS call and one held call on the same bearer. It shall be possible to create a new CS bearer and to move one of the calls to the new bearer, resulting both calls being active within the limits set by the operator/user and within the capability of the terminal. See figure 2: Split of bearer.
+
+When having two calls (multicall) on the separate bearers. It shall be possible to join both calls to one of the two bearers, put the one of the calls to hold and to release unused CS bearer. It shall be possible to select which call to put on hold. See figure 2: Combination of bearers. *(Note: there is no clear end-user service requirement for this feature at time being).*
+
+NOTE: Due to that only speech calls can be put on hold, so one of the two active Cs calls has to be a speech call.
+
+
+
+```
+
+graph LR
+ subgraph CallHoldSS [Call Hold SS]
+ CALL1((Active CALL1)) --- BEARER((BEARER))
+ CALL2((Hold CALL2)) --- BEARER
+ end
+ subgraph Multicall [Multicall]
+ CALL1_2((CALL1)) --- BEARER1((BEARER1))
+ CALL2_2((CALL2)) --- BEARER2((BEARER2))
+ end
+ CallHoldSS -- Split --> Multicall
+ Multicall -- Combine --> CallHoldSS
+
+```
+
+Figure 2: Illustration for split of bearer and combination of bearers. The diagram shows two states: 'Call Hold SS' and 'Multicall'. In 'Call Hold SS', an 'Active CALL1' and a 'Hold CALL2' are connected to a single 'BEARER'. In 'Multicall', 'CALL1' and 'CALL2' are connected to 'BEARER1' and 'BEARER2' respectively. Arrows labeled 'Split' and 'Combine' show the transition between these states.
+
+Figure 2: Illustration for split of bearer and combination of bearers
+
+### B.2.2 Several simultaneous speech calls / bearers
+
+A Key requirements for multicall is to allow several simultaneous CS calls with dedicated bearers. The most important usage scenario is to allow several CS data bearers to be bind at application level resulting to higher than 64kbits/s data rates. Another important feature is to allow simultaneous speech and data calls.
+
+It's been proposed that the multical feature could be introduced in a phased manner; meaning that in the first phase, i.e. 3GPP release 99 does only support one active speech call at a time. However, Call control should not prohibit a complete set of multiple speech bearer services in future releases and UTRAN shall be designed in a flexible way to support multiple speech bearers. The specific NDUB definition for speech call shall be removed when multiple speech call is supported. At this release , Supplementary Services Call Waiting, Multiparty and Call Hold are used to offer simultaneous speech calls to user.
+
+Ncs may be extended in further releases.
+
+If multiple simultaneous speech calls are supported in the future then the Call Hold service may be used to reconfigure the number of bearers supporting speech calls if required during handover. e.g. in the case of handover to GERAN where only one speech call can be active at a time. This requirement is dependent on the user subscribing to Call Hold.
+
+### B.2.3 CCBS
+
+At this release CCBS no enhancements for CCBS is required.
+
+In the future releases the definition of IDLE state of subscriber A and destination B should be modified in away that the IDLE state is reach even if there are active CS calls but the maximum limit of CS calls is not reached.
+
+# Annex C (informative): Change history
+
+| Date | Version | Comment |
+|---------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 19 Mar. 1999 | 0.0.1 | First draft by the editor (Tommi Kokkola / Nokia) |
+| 30 Mar. 1999 | 0.1.0 | Output from S1 Multicall ad hoc |
+| 6 Apr. 1999 | 0.1.0 | Minor modifications by the editor. Proposed version 1.0.0 |
+| 19 Apr. 1999 | 1.0.0 | For information to 3GPP TSG SA#3 |
+| 10. Jun. 1999 | 1.1.0 | Draft from editor for the email meeting. |
+| 18. Jun. 1999 | 1.1.1 | Draft during the email meeting. |
+| 24. Jun. 1999 | 1.2.0 | Result of email discussions. For some issues status still unstable. |
+| 1. Jul. 1999 | 1.2.1 | Comments from TSGN & TSGS Multimedia and Multicall joint meeting included. (Revisions included from version 1.1.0) |
+| 8. Jul. 1999 | 1.3.0 | Results from S1 Plenary. Drafting continues at S1_Multicall mailing lists.
Contributions expected on:
-Busy, Idle, Active states
-Busy definition
-Supplementary service interactions incl. related CR to appropriate SS when needed. (Specifically 02.83 need to be studied.)
- all topics marked with FFS... |
+| 28. Sep. 1999 | 1.4.0 | Output from S1 Multicall ad hoc, Germany. |
+| 1.Oct. 1999 | 1.6.0 | Proposed version 2.0.0 |
+| 10. Oct 1999 | 2.0.0 | Version 2.0.0 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|-----|-----|-----|-----|------------------------------------------------------------------------------------|-------|-------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-05 | SP99-433 | | 22.135 | | | | | Version 3.0.0 approved | | 3.0.0 | |
+| SP-06 | SP-99523 | S1-991020 | 22.135 | 001 | | R99 | D | Transfer of Handover chapter to 22.129 | 3.0.0 | 3.1.0 | |
+| SP-06 | SP-99523 | S1-991065 | 22.135 | 002 | | R99 | D | Clarification on handling of multiple bearers | 3.0.0 | 3.1.0 | |
+| SP-06 | SP-99554 | S1-99963 | 22.135 | 003 | | R99 | C | Registration, Interrogation and Restriction of Packet Domain | 3.0.0 | 3.1.0 | |
+| SP-07 | SP-000068 | S1-000168 | 22.135 | 004 | | R99 | F | Clarification of requirement for Multicall | 3.1.0 | 3.2.0 | |
+| SP-08 | SP-000205 | S1-000349 | 22.129 | 012 | | R99 | F | Alignment of handover requirements for Multicall | 3.2.0 | 3.3.0 | |
+| SP-09 | SP-000375 | S1-000585 | 22.135 | 006 | | R99 | F | Interaction with MSP | 3.3.0 | 3.4.0 | |
+| SP-09 | SP-000406 | S1-000656 | 22.135 | 007 | | R99 | F | Removal of the Requirement on Network to Tear Down Calls to Accept EC in Multicall | 3.3.0 | 3.4.0 | |
+| SP-09 | SP-000406 | S1-000657 | 22.135 | 008 | | R99 | F | Addition of Ncs_MT limitation to number of MPTY members | 3.3.0 | 3.4.0 | |
+
+| | | | | | | | | | | | |
+|---------|-----------|-----------|--------|-----|---|-------|---|-----------------------------------------------------------|--------|--------|---------|
+| SP-11 | SP-010065 | S1-010258 | 22.135 | | | Rel-4 | | Transferred to 3GPP Release 4 | 3.4.0 | 4.0.0 | |
+| SP-15 | SP-020045 | S1-020457 | 22.135 | 009 | - | Rel-4 | F | Editorial CR to correct terms and references | 4.0.0 | 4.1.0 | CORRECT |
+| SP-16 | SP-020267 | S1-021043 | 22.135 | | | Rel-5 | | Updated from Rel-4 to Rel5 | 4.1.0 | 5.0.0 | |
+| SP-26 | SP-040744 | S1-040997 | 22.135 | | | Rel-6 | | Updated from Rel-5 to Rel-6 | 5.0.0 | 6.0.0 | |
+| SP-36 | | | 22.135 | | | Rel-7 | | Updated from Rel-6 to Rel-7 | 6.0.0 | 7.0.0 | |
+| SP-42 | | | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | - | - | - | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22140/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22140/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d071b557c8648bb111295a969536da818767566
--- /dev/null
+++ b/marked/Rel-18/22_series/22140/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4651ada5d7b3a7210a04d8d6333a8f5c9d47e59248eb82cadf46b1e2ef862726
+size 8253
diff --git a/marked/Rel-18/22_series/22140/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22140/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d107e5ab554572172d9c1fe82c7e805eac754206
--- /dev/null
+++ b/marked/Rel-18/22_series/22140/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2737ce6737c2d983c8a528d43f16428340a5bd69c59a81f687d1da5b0d2ac8f
+size 7268
diff --git a/marked/Rel-18/22_series/22140/raw.md b/marked/Rel-18/22_series/22140/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..973a65034cf805b81858f2fb84aa06550e3bff32
--- /dev/null
+++ b/marked/Rel-18/22_series/22140/raw.md
@@ -0,0 +1,696 @@
+
+
+# 3GPP TS 22.140 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Messaging Service (MMS); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font. The 'G' has a red signal wave icon at its base, and a 'TM' symbol is at the top right.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+LTE, UMTS, MMS, multimedia, stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|---------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 High level Requirements..... | 6 |
+| 5 General Requirements..... | 7 |
+| 5.1 Multimedia message management ..... | 8 |
+| 5.2 Multimedia message delivery and submission..... | 10 |
+| 5.2.1 MM delivery to and submission from a VASP ..... | 12 |
+| 5.3 Notification and Acknowledgement..... | 12 |
+| 5.4 Addressing..... | 13 |
+| 5.5 Management and Control of a Network Based Repository..... | 13 |
+| 5.6 Error Messages..... | 13 |
+| 5.6.1 Prepaid Errors ..... | 13 |
+| 5.7 MMS client interaction with UICC..... | 13 |
+| 6 User Profile ..... | 14 |
+| 7 Security ..... | 14 |
+| 8 Charging..... | 14 |
+| 9 External Interface..... | 15 |
+| 10 Interworking..... | 15 |
+| 11 Roaming..... | 15 |
+| 12 Support of Operator Specific Services..... | 15 |
+| 12.1 Service Interaction..... | 16 |
+| 12.1.1 VASP Services ..... | 16 |
+| Annex A (informative): Change history..... | 17 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+SMS has been very successful in the GSM second generation system, as all mobiles have supported the application level and it is possible to send to any GSM handset without the need to check for individual support. This easy to use service for non realtime text transmission between GSM users shall be succeeded to in third generation mobile systems by a non real-time Multimedia Message Service, MMS. The MMS will allow users to send and receive messages exploiting the whole array of media types available today e.g. text, images, audio, video while also making it possible to support new content types as they become popular.
+
+3GPP shall not standardise new services themselves, but instead uses the standardised set of service capabilities features on which the new services will be built.
+
+Multimedia technology is rapidly developing new capabilities, such as multimedia messages, games, presentations and services that are now considered to be a part of everyday life. Multimedia consists of one or more media elements (such as text, voice, image and video), and it is the combination of these media elements in an ordered synchronised manner that creates a multimedia presentation.
+
+A non-realtime multimedia message as observed by the user is a combination of one or more different media elements in a multimedia presentation, that can be transferred between users without the requirement for the need to be transferred in realtime. The non-real-time multimedia messaging service shall be capable of supporting current and future multimedia messaging services, and exploit the advances being made in the world multimedia community, with additional mobile requirements.
+
+# --- 1 Scope
+
+This Technical Specification defines the stage one description of the non real-time Multimedia Messaging Service, MMS. Stage one is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber's and service providers' points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the Multimedia Messaging Service, which are sufficient to provide a complete service.
+
+This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:
+
+- multiple media elements per single message
+- individual handling of message elements
+- different delivery methods for each message element
+- negotiate different terminal and network MM capabilities
+- notification and acknowledgement of MM related events (e.g. delivery, deletion, ...)
+- handling of undeliverable MM
+- personalised MMS configuration
+- flexible charging
+
+The above list is not exhaustive.
+
+Thus the MMS enables a unified application which integrates the composition, storage, access, and delivery of different kinds of media, e.g. text, voice, image or video in combination with additional mobile requirements.
+
+# --- 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 TS 22.101: "Service Principles".
+- [2] Void
+- [3] 3GPP TS 21.133: "3G Security; Security Threats and Requirements".
+- [4] ITU-T E.164 (1997): "The International Public Telecommunications Numbering Plan".
+- [5] IETF; STD 0011 (RFC 2822): "Internet Message Format", URL:
+.
+
+- [6] 3GPP TS 21.905: "Vocabulary".
+- [7] 3GPP TS 31.102 "Characteristics of the USIM Application".
+- [8] 3GPP TS 51.011 (Rel-4): "Specification of the Subscriber Identity Module – Mobile Equipment (SIM-ME) interface".
+- [9] 3GPP TS 22.242 "Digital Rights Management (DRM); Stage 1".
+- [10] 3GPP TS 22.240 "Stage 1 Service Requirement for the 3GPP Generic User Profile (GUP)" .
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+**Recipient :** the recipient is the entity to which a MM has been sent.
+
+**Sender:** the sender is the entity that sent a MM.
+
+**User:** the user is the MM sender or the MM recipient.
+
+**message element:** a message element is a part of a MM consisting of only one media type.
+
+**multimedia message:** a multimedia message is a message composed of one or more message elements.
+
+**multimedia message service:** A multimedia message service allows transfer of multimedia messages between users without the requirement for the multimedia messages to be transferred in real-time.
+
+**media types:** a media type refers to one form of presenting information to a user, e.g. voice or fax.
+
+**media formats:** within one media type different media formats are applicable for the media presentation, e.g. a picture can be GIF or JPEG format.
+
+**network:** for the purposes of supporting multimedia messaging, the term network shall be considered to include the mobile operator's network and any functionality which may exist outside the mobile operator's network (i.e. fixed, internet and multimedia technologies etc.), and the support provided by that functionality for multimedia messaging.
+
+**Operator Specific Service:** network-based and operator administered function being able to perform additional, operator defined, MMS services based on MMS capabilities for address translation and charging.
+
+**Value Added Service Provider:** provides services other than basic telecommunications service for which additional charges may be incurred.
+
+**Short code:** A string of alphanumeric characters which addresses a specific service of a Value Added Service Provider.
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+| | |
+|------|-------------------------------|
+| MM | Multimedia Message |
+| MMS | Multimedia Message Service |
+| SMS | Short Message Service |
+| VASP | Value Added Services Provider |
+
+# --- 4 High level Requirements
+
+The following list gives the high level requirements of the MMS. These are requirements which are independent of the user's perception of the service:
+
+### - Forward compatible multimedia messaging
+
+Multimedia messaging mechanisms shall provide the capability to support current and evolving multimedia messaging by re-using existing standards as far as possible and proposing extensions (as necessary) to existing standards (i.e. the multimedia messaging service shall support the evolution of multimedia messaging technologies).
+
+### - Consistent messaging
+
+Regardless of the message type / format, MMS shall be capable of supporting integration of all types of messaging (e.g. fax, SMS, Multimedia , voicemail, e-mail etc.) in a consistent manner.
+
+### - Universal messaging access
+
+Within the capabilities of networks and terminals, the user shall be able to experience consistent access to the MMS regardless of the access point.
+
+For example the user should be capable of accessing her multimedia messages through a number of different access points, which should include 3GPP systems, fixed networks, the Internet, etc.
+
+### - Interoperability
+
+The MMS shall support a minimum set of functionality and message formats to ensure interoperability (e.g. deletion of MM, identified standardised message notification, message media types and message content formats).
+
+The MMS shall provide a minimum set of supported formats to ensure full interoperability between different terminals and networks from the very beginning of service provisioning (e.g. JPEG for pictures, MP3 for audio, MPEG for motion pictures, etc.).
+
+The MMS shall support version management by indicating a version number in the MM for interoperability purpose.
+
+# --- 5 General Requirements
+
+Network operators have many differing requirements, and MMS shall be supported in the network in a manner which allows network operators to consider different configurations depending on their network and commercial requirements. Thus, an identified set of functionalities and formats shall be standardised to ensure interoperability across networks and terminals to support MMS.
+
+However, some network operators may wish to design and configure networks in different ways, and the subsequent requirements are identified to allow flexibility in how the MMS functionality is supported. For example in some networks the network operators may wish to implement the MMS functionality within the core network, whereas other may wish to place the MMS functionality on the periphery of the core network (e.g. a centralised network model instead of a distributed architecture). Further, some network operators may wish to support a limited set of MMS functionality, while others may require extensive and elaborate MMS support according to their business models (e.g. basic MMS instead of advanced MMS). Interoperability shall always be maintained within this flexible architecture.
+
+The following sub-clauses use the term "*The MMS shall be able to support a request for ...*" and similar phrases to allow network operators to consider these different network models and business requirements, to permit flexible architectures and ensure MMS interoperability.
+
+The following sub-clauses use the term "*This requirement shall be supported at the application layer in the terminal (and/or the network), and will not be further elaborated.*" and similar phrases to identify those service requirements that shall be supported by MMS but do not require standardisation.
+
+The criterion for identifying these types of requirements is as follows:
+
+If the requirement corresponds to an interaction and/or command between the terminal and the network applications from the same Service Provider (e.g. between the recipient's terminal resident messaging application and the recipient's network resident application. The same applies for the sender), then this requirement shall be supported by MMS but does not require standardisation.
+
+The following general requirements shall be supported.
+
+## 5.1 Multimedia message management
+
+### - Terminal-sensitive MM management
+
+The MMS shall be able to support the capability for the terminal and network to take account of the capability of the user's terminal (e.g. deliver a MM / notification in a manner compatible with the terminals capability).
+
+### - Terminal status-sensitive MM Management
+
+The MMS shall be able to support the capability of the network to take account of the availability, changes of the state of availability of the terminal (e.g. store messages if the recipient is not available).
+
+#### - MMS Control by the operator
+
+The MMS shall be able to support a request from the operator to enable/disable MM delivery and submission.
+
+#### - MMS Control by the user
+
+The MMS shall be able to support a request from the user to enable/disable MM delivery and submission.
+
+This requirement shall be supported at the application layer in the terminal, and will not be further elaborated.
+
+#### - Storage of MMS parameters
+
+The USIM shall be able to store the following types of MMS related data:
+
+- i) a number of sets of issuer configuration information to allow access to MMS services.
+
+At least one of these sets of configuration information should be stored on the USIM by the issuer of the USIM.
+
+The first issuer configuration information set is denoted as the default configuration set.
+
+This configuration information shall only be configurable by the issuer of the USIM.
+
+- ii) a number of sets of user configuration information to allow access to MMS services.
+
+If more than one set of configuration information is present, it shall be possible for the user to select which set is used. If the user has not selected any of the configuration information sets, then the default set in the active USIM is used.
+
+- iii) MMS notifications
+
+- iv) MMS user preferences
+
+A terminal using a USIM [7] or a SIM [8] with these MMS parameters, shall by default use them and the related preferred bearer, to access to the MMS services.
+
+NOTE 1: Terminal support of SIM and USIM in general is specified in 3GPP TS 22.101[1].
+
+#### - Personalise multimedia messaging
+
+The MMS shall be able to support a request by the user to manage the Service Preferences of his User Service Profile related to this MMS [6](e.g. customise his MM environment within the capabilities of the terminal, network and MM application. This could be unconditional or conditional e.g. depending on roaming conditions or operator restrictions).
+
+#### - MM creation
+
+The MMS shall be able to support the request to create a MM by the user or an application.
+
+This requirement shall be supported at the application layer in the terminal, and will not be further elaborated.
+
+#### - **MM Time Stamping**
+
+The MMS shall be able to support the request to include a reliable time value in an MM, a notification and an acknowledgement as appropriate.
+
+#### - **Multiple Media**
+
+Multimedia messages may be composed of either a single medium (e.g. voice) or multi-media (e.g. Voice and video). The MMS shall be able to support a request for media synchronisation / sequencing.
+
+#### - **Media Type Conversion**
+
+The MMS shall be able to support a request to convert between media types (e.g. Fax to image). The MMS shall be able to support an indication from a VASP that VASP originated content of an MM should not be converted or changed by the MMS service provider before it is delivered to the recipient.
+
+This requirement shall be supported at the application layer in the network, and will not be further elaborated.
+
+#### - **Media Format Conversion**
+
+The MMS shall be able to support a request by the user or the application to convert between MM media formats (e.g. JPEG to GIF).
+
+This requirement shall be supported at the application layer in the terminal and/or in the network, and will not be further elaborated.
+
+#### - **Message forwarding**
+
+The MMS shall be able to support a request to forward multimedia messages or multimedia message elements without having to first download the MM to the terminal. The MMS shall provide a mechanism to prevent an MM forwarding loop (e.g. MMs are setup to be automatically forwarded from User A to B, then from B to C and from C back to A. Users A, B, and C are unaware that they have setup this undesirable situation).
+
+#### - **Storage of Multi-Media Messages**
+
+The MMS shall be able to support a request for multimedia messages or message elements to be stored until delivered to the recipient's terminal, until they expire, or until they are deleted by the user (unless configured differently). The MMS shall be able to support a request to store and manage all MMs in a network based repository rather than on the mobile terminal.
+
+When the USIM supports MMs storage, it shall be possible for the MMS client to store and retrieve MMs or elements of MMs in the USIM.
+
+NOTE 2: There is no requirement for the MMS to be responsible for the processing/presentation of the MM message, after it has been delivered to the terminal.
+
+#### - **Prioritisation of Messages**
+
+The MMS shall be able to support a request for MM prioritisation . The prioritisation is passed to the recipient(s) of the message as an indication of the importance the sender places on the message. MM prioritisation is not acted upon by the network.
+
+#### - **Message qualification**
+
+The MMS shall be able to support a request for MM qualification (e.g. subject) for the purpose of advanced user experience and awareness.
+
+#### - **Screening of Messages**
+
+The MMS shall be able to support a request for MM screening subject to the capabilities of the network (e.g. automatically delete "junk mail", anonymous messages without delivery to the recipient's terminal).
+
+This requirement shall be supported at the application layer in the terminal and/or in the network, and will not be further elaborated.
+
+#### - **Validity Period**
+
+The MMS shall be able to support a request by the originator of a message to define validity periods (earliest and latest desired time) for message delivery (e.g. if a message can not be delivered within a certain time it will be automatically deleted). The MMS service provider shall be able to set the MAXIMUM allowable validity period for any message.
+
+#### - **Multimedia Message Processing by a VASP**
+
+The MMS shall be able to support a request for messages to be processed by a VASP. An example of such processing may be where an MM is sent to a VASP before delivery to the recipient so that the VASP can add multimedia element(s) to the original message.
+
+#### - **Replacing MM**
+
+The MMS shall be able to support a request by a VASP to replace a previously sent MM from the VASP with a second newer MM.
+
+#### - **Cancellation of MM**
+
+The MMS shall be able to support a request by a VASP to delete a MM that had previously been sent from the VASP but not yet delivered to the terminal.
+
+#### - **Hyperlinks in MM**
+
+It shall be possible to embed a hyperlink in a MM.
+
+The following guidelines on editing, presenting and following of hyperlinks should be followed:
+
+- There should be no restriction to the position in the MM where a hyperlink can be added.
+- It should be possible to clearly recognise the presence of a hyperlink.
+
+NOTE 3: It is preferable to display the title of a hyperlink rather than the complete address. (URI)
+
+- Presence of a hyperlink in an MM should not impact the presentation of the MM (i.e. due to immediate following or storage of the link)
+- The recipient of an MM should be able to follow a hyperlink.
+
+The hyperlink should not be followed automatically by default (explicit user interaction should be required)
+
+#### - **Digital Rights Management**
+
+The MMS shall be able to support controlling the distribution of controlled content as defined in 3GPP TS 22.242 [9]. MMS Content Providers shall be able to invoke DRM to prevent unauthorized copying and forwarding of controlled content through the MMS.
+
+## 5.2 Multimedia message delivery and submission
+
+### - **Submission mechanism**
+
+The MMS shall support multimedia messages or messages elements to be submitted from the sender's UE.
+
+#### - **Push Mechanism**
+
+The MMS shall be able to support a request for multimedia messages or messages elements to be automatically delivered to the recipient's UE.
+
+#### - **Pull Mechanism**
+
+The MMS shall be able to support a request for multimedia messages or messages elements to be delivered to the recipient's UE on request by the recipient.
+
+NOTE 1: Push and pull delivery mechanisms could be identical; the criteria which decide on the type of mechanism (push / pull) are either described in the User Services Profile or out of the scope of this specification.
+
+#### - **Concurrency**
+
+The MMS shall be able to support MM delivery to and from the user's terminal not be restricted during other active services (subject to the capabilities of the terminal and the network).
+
+#### - **Streaming**
+
+The MMS shall be able to support streaming for MM delivery from the MMS system to the terminal.
+
+Support for streaming for MM upload from the terminal to the MMS system will be considered for future releases.
+
+#### - **Preferred Bearer**
+
+It shall be possible to define a list of precedence for bearers in the configuration information sets for delivery and submission of MM (e.g. GPRS, CSD). By default, the terminal shall be able to support automatic bearer selection (i.e. without user intervention) based on the order of precedence defined in the configuration information sets on the USIM[7] or SIM [8]. The user shall be able to enable or disable automatic bearer selection. When disabled, manual bearer selection shall be available from the list of bearers.
+
+#### - **Conditional delivery mechanism**
+
+It shall be possible for the user to define in the User Profile a set of conditions that determine which delivery mechanism should be used for the delivery of a MM.
+
+Such conditions should include:
+
+- Roaming status of the recipient (e.g. inside or outside the home network)
+- Identity of the MM originator
+- Time of day (of the recipient's home network)
+- Upper limit to the MM size
+
+The notification message indicating an MMS awaiting delivery shall relay the information of the user's preferred delivery mechanism, if such information is made available by the user profile in the network, to the UE. If a mismatch is identified between the delivery mechanism configured in the UE and the delivery mechanism indicated in the notification message, it shall be possible for the user to select either the delivery mechanism configured in the UE or the delivery mechanism indicated in the notification message.
+
+Furthermore, the terminal may also display a warning prior to the download of a message depending on some terminal parameters such as:
+
+- Available storage capacity
+- Remaining battery life
+- Available bearers
+
+For example, the user may elect to have all MMs downloaded automatically when in the home network, be able to manually select whether to download a MM or not when roaming.
+
+It shall be possible for the network operator to program a default set of rules for the delivery mechanism in the User profile. Such rules can be overridden by the user.
+
+NOTE 2: The way the user profile is accessed and modified is not subject of standardisation.
+
+#### - **MM intended for applications other than the default MMS client on the UE**
+
+The MMS shall support MMs that are not intended for presentation but used to originate and deliver information to applications residing on the UE other than the default MMS client.
+
+NOTE 3: The intended application can present the MM contents.
+
+When an application sends a MM not intended for presentation, it shall be possible to uniquely identify that originating application and the target application on the recipient UE as well as the instance of the application if more than one instance can be active. The originating application may reside on a UE or within the network.
+
+The message payload shall not be modified by the MMS.
+
+If the MM is originated by the subscriber's home environment, it shall be possible to protect the MM from accidental deletion by the user.
+
+### 5.2.1 MM delivery to and submission from a VASP
+
+#### - VASP submission mechanism
+
+The MMS shall support multimedia messages or messages elements to be submitted from a VASP.
+
+#### - VASP delivery mechanism
+
+The MMS shall be able to support multimedia messages or messages elements to be delivered to a VASP.
+
+#### - VASP mass distribution
+
+The MMS shall be able to support a request from a VASP for mass distribution of MMs to recipients.
+
+#### - Additional VASP data
+
+The MMS shall be able to convey additional data associated with an MM from a VASP to the MMS service provider and vice versa.
+
+Note: A possible use case for this could be the option to send additional charging information from the VASP to the MMS service provider. However the data itself is not specified for this release.
+
+## 5.3 Notification and Acknowledgement
+
+The MMS shall be able to support a request to send generic notification and acknowledgement capability to inform the user in an appropriate manner of MMS events. Examples may include:
+
+- notify the recipient about received messages (including a description of the message, e.g. content, size, type).
+- notify the recipient about actions taken by the MMS, (e.g. due to profile settings like automatic MM forwarding, deletion, etc.).
+- acknowledge the sender about successful or failed MM or storage of a MM.
+- acknowledge the sender about successful or failed MM submission.
+- acknowledge the sender, including a VASP, about successful or failed MM delivery to the recipient terminal (subject to the recipient permitting such an acknowledgement).
+- acknowledge the sender, including a VASP, about the MM being read/handled at the recipient terminal (subject to the recipient permitting such an acknowledgement).
+- acknowledge the sender, including a VASP, about successful or failed MM deletion.
+- acknowledge the sender, including a VASP, upon request, about the status of a submitted MM (i.e. delivered / not delivered).
+- acknowledge a VASP, upon request, about the status of a mass distributed MM. A mass MM status report might be an aggregated report on the status of individual messages for all recipients on the distribution list of a specific mass distributed MM.
+- acknowledge a VASP, upon request, about the status of previously submitted MMs, after a VASP had sent the MMs being queried.
+
+## 5.4 Addressing
+
+The MMS shall support different addressing formats to identify the sender and recipient. It shall be possible to submit one message to multiple recipients.
+
+The MMS shall support the capability for both MSISDN [4] and e-mail addressing schemes [5] to be used, and the user may use either form of addressing to send a message.
+
+The MMS shall be able to support the request to hide the sender's address from the recipient.
+
+The MMS shall support a distribution list for mass distribution of MMs from a VASP. The MMS shall support the ability for a VASP to have the distribution list modified by the MMS service provider for this release.
+
+The MMS may support short code addresses to address Value Added Services. If supported, and routing of messages to a MMS VASP service based on a short code address is enabled, the MMS shall be able to translate the short code address to a routable address to be used in the transport layer, e.g. a URI.
+
+## 5.5 Management and Control of a Network Based Repository
+
+Network based repository is optional. If supported, MMS shall be able to support following functionalities:-
+
+- The MMS shall allow an MMS service provider to configure MMS in such a way that one, several or all incoming MMs of a particular user be stored persistently in a network based repository
+- The MMS shall allow an MMS service provider to configure MMS in such a way that one, several or all submitted MMs of a particular user be stored persistently in a network based repository
+- The MMS shall be able to support a request from a sender to persistently store a sent MM in a network based repository at the time of sending
+- The MMS shall be able to support a request from a user to persistently store a MM for which he received a notification in a network based repository
+- The MMS shall be able to support a request from a user to upload one or more MMs into a network based repository for persistent storage
+- The MMS shall be able to support a request from a user to retrieve one or more MMs that are stored in a network based repository
+- The MMS shall be able to support a request from a user to delete one or more MMs that are stored in a network based repository
+- The MMS shall be able to support a request from a user to forward one or more MMs that are stored in a network based repository to another destination without being delivered first to that user.
+- The MMS shall be able to support a request from a user to view the list of MMs and MM related attributes, such as sender, recipient, subject and date/time, in a network based repository
+
+## 5.6 Error Messages
+
+It shall be possible for the operator to configure the content of the error message delivered to the MMS client.
+
+### 5.6.1 Prepaid Errors
+
+The MMS shall notify a prepaid user when message submission was unsuccessful due to lack of credit in the prepaid account, explicitly stating this situation.
+
+## 5.7 MMS client interaction with UICC
+
+It shall be possible for an MMS client in the ME to interact with a UICC to manage (e.g. send, receive and present) MMS messages stored on the UICC, in accordance with the requirements in this specification. It shall be possible to
+
+indicate to the UE that an MM needs to receive special treatment. When a MM has been marked with this indication, means shall be provided to protect the MM from accidental deletion e.g. by asking for additional confirmation to the user. The use of this indication shall be under the control of the HPLMN.
+
+# --- 6 User Profile
+
+The MMS shall be able to support the ability to create, update, store, transfer, interrogate, manage and retrieve a user's multimedia messaging profiles.
+
+The multimedia messaging profiles shall allow a user to configure and personalise his multimedia messaging environment with the multimedia messaging profiles (e.g. which media types and notifications that shall be delivered to the recipient , such as voice only or text only).
+
+The user profile shall allow the user to create and manipulate a list of users, identified by their addresses, from which the user does not want to receive messages. This list is called "user-level blacklist". It shall be possible for the user to add, remove and edit addresses in the user-level blacklist.
+
+Note: User-level blacklist differs from ODB blacklist. Users can decide from whom they do not want to receive messages by adding the corresponding address to the user profile.
+
+If the MMS supports a network based repository of MMs, it shall be possible for the users to configure where incoming MMs will be stored.
+
+The multimedia messaging profiles shall form part of the user's virtual home environment.
+
+MMS information in the user profile when stored in the UA or the network shall be accessed in a standardised manner. The MMS should accomplish this using mechanisms described in the 3GPP Generic User Profile 3GPP TS 22.240 [10] whenever possible.
+
+# --- 7 Security
+
+The user shall be able to use and access MM in a secure manner. It shall be possible for the contents of MMs to be read only by the intended recipient(s). A recipient shall be informed of the reliability of the identity of the sender in case the sender has authorised his identity to be transmitted.
+
+The integrity of MMs during transit shall be assured to extent of the network capabilities.
+
+The MMS shall be intrinsically resistant to attempts of malicious or fraudulent use.
+
+An MMS service provider shall be able to authenticate a VASP connected to it and shall be able to be authenticated by a VASP connected to it. The MMS service provider shall be able to authorise the VASP to use various MM services. The MMS shall support encryption of the transport layer between an MMS service provider and a VASP.
+
+Note: Key management is outside the scope of this release of this standard.
+
+The "Security Threats and Requirements" specified in 21.133 [3] shall not be compromised.
+
+# --- 8 Charging
+
+The MMS shall be able to support various charging models, including:
+
+- Sender pays;
+- both Sender and Recipient pay their respective charges for message delivery;
+- Recipient pays for receipt of messages from a VASP when there is a commercial agreement between the Recipient and the VASP;
+- Sender pays for reply message on a per message basis.
+
+- The third party who has a commercial agreement with the VASP (and possibly additional agreement with the operator and/or recipient) is charged for the delivery of the message to the recipient.
+
+The MMS shall be able to support various charging mechanisms. The following charging characteristics may be considered:
+
+- message types, length, storage time in the network, etc,
+- delivering time, upload / download method,
+- MM-sender / -recipient,
+- number of messages sent,
+- number of messages received,
+- roaming conditions,
+- location conditions,
+- Indication of charging,
+
+The MMS indicates to the recipient prior to the recipient downloading a multi media message whether the sender has paid or the recipient is expected to pay for the message.
+
+- Prepaid subscriptions.
+- Bearer of the message
+
+The MMS shall support a standardized interface to transfer CDRs and other charging related information between the MMS system and the billing system for prepaid and postpaid billing solutions.
+
+# --- 9 External Interface
+
+External interfaces for controlling and delivering MM between the terminal and an external device e.g. portable computer should be supported.
+
+# --- 10 Interworking
+
+The standard shall permit interworking with other or existing messaging technologies, messaging services, intelligent network services and supplementary services, either located within or outside a mobile network.
+
+In the case of a VASP, such interworking shall include capability negotiation between the VASP and the MMS service provider. Such capability negotiation shall include service version information as a minimum for this release.
+
+# --- 11 Roaming
+
+Roaming between network operators shall be supported.
+
+# --- 12 Support of Operator Specific Services
+
+The MMS may support operator specific services. Thereby network operators shall be able to provide additional MMS services dealing with enhanced addressing and charging.
+
+If supported, the interaction between the MMS and Operator Specific Service shall happen immediately after multimedia message submission time or immediately before multimedia message delivery time, or both.
+
+Multimedia Messages sent or delivered from/to users shall be subject to operator specific services handling if:
+
+- the user is provisioned with operator specific services in the MMS user profile. The user may be provisioned independently for operator specific services applicable for submission and delivery of multimedia messages. Provisioning of Operator Specific Services for MMS is under control of the HPLMN operator.
+- the MMS determines based on a pre-analysis of the recipient's address(es) found in a submitted multimedia message that an Operator Specific Service needs to be invoked. The definition of the addresses invoking MMS Operator Specific Services is under control of the HPLMN operator(s) of the originating and terminating subscribers.
+
+If the Operator Specific Services needs to be invoked, the MMS shall temporarily suspend the normal process of that multimedia message and shall provide the Operator Specific Services with at least the following information:
+
+- messaging event (submission, delivery)
+- multimedia message data:
+ - sender identification
+ - recipient addresses
+
+As a response to the above request from the MMS, the Operator Specific Services may request the MMS to perform one of the following actions:
+
+- leave the multimedia message unmodified and proceed with its processing;
+- reject the message.
+- modify one or more of the following multimedia message data:
+ - sender identification
+ - recipient addresses
+
+Operator Specific Services shall be allowed to influence charging of the message by providing additional information to the MMS. The MMS shall transparently forward this information to the billing systems together with the MMS charging relevant data.
+
+## 12.1 Service Interaction
+
+This subclause specifies interactions between Operator Specific Services and other services in the MMS.
+
+### 12.1.1 VASP Services
+
+Operator Specific Services take precedence over VASP services. If short code addressing to Value Added Services is supported by the MMS, the result from an Operator Specific Service shall be subject to short code address translation.
+
+Multimedia Messages submitted from a VASP may be subject to operator specific services.
+
+# Annex A (informative): Change history
+
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+|---------|-----------|-----------|--------|-----|-----|-------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|------------------|
+| SP_06 | PP-99529 | | 22.140 | - | | R99 | - | Approved at SA#08 as version 3.0.0 | 2.0.0 | 3.0.0 | |
+| SP_08 | SP-000214 | S1-000347 | 22.140 | 001 | | R00 | B | Introduction of streaming for MMS | 3.0.0 | 4.0.0 | |
+| - | - | - | 22.140 | - | | R00 | - | Corrected implementation of CR001 by MCC, re-introducing the R00 text deleted by implementation of CR002 to R99 version (see SP-000208). Some editorial clean-up. | 4.0.0 | 4.0.1 | |
+| SP-11 | SP-010062 | S1-010265 | 22.140 | 004 | | Rel-4 | C | Alignment of Stage 1 MMS to Stage 2 MMS | 4.0.1 | 4.1.0 | MMS |
+| SP-11 | SP-010062 | S1-010016 | 22.140 | 005 | | Rel-4 | C | Support for Streaming in MMS | 4.0.1 | 4.1.0 | MMS |
+| SP-11 | SP-010062 | S1-010014 | 22.140 | 006 | | Rel-4 | F | MM Forwarding | 4.0.1 | 4.1.0 | MMS |
+| SP-11 | SP-010062 | S1-010015 | 22.140 | 007 | | Rel-4 | B | New features in MMS R'4 | 4.0.1 | 4.1.0 | MMS |
+| SP-14 | SP-010676 | S1-011345 | 22.140 | 008 | | Rel-5 | B | Stage 1 Requirements for VASP connectivity | 4.1.0 | 5.0.0 | MESS5-MMS |
+| SP-14 | SP-010748 | | 22.140 | 009 | - | Rel-5 | B | Minimum set of functionality for the support of a Network Based repository | 4.1.0 | 5.0.0 | MMS enhancements |
+| SP-15 | SP-020193 | | 22.140 | 010 | 1 | Rel-5 | B | Support of charging models in MMS | 5.0.0 | 5.1.0 | MMS |
+| SP-15 | SP-020055 | S1-020209 | 22.140 | 011 | | Rel-5 | B | CR to 22.140 on addressing | 5.0.0 | 5.1.0 | MMS |
+| SP-15 | SP-020045 | S1-020457 | 22.140 | 012 | - | Rel-5 | A | Editorial CR to correct terms and references | 5.0.0 | 5.1.0 | CORRECT |
+| SP-15 | SP-020055 | S1-020622 | 22.140 | 013 | | Rel-5 | B | CR 22.140 Rel. 5 MMS Configuration | 5.0.0 | 5.1.0 | MMS enhancements |
+| SP-15 | SP-020045 | S1-020468 | 22.140 | 014 | | Rel-5 | D | Editorial CR 22.140 Rel.5 D - Update of references and general requirements | 5.0.0 | 5.1.0 | CORRECT |
+| SP-15 | SP-020195 | | 22.140 | 015 | | Rel-5 | B | Automatic bearer selection for MMS delivery and submission | 5.0.0 | 5.1.0 | MMS Enhancement |
+| SP-16 | SP-020251 | S1-021073 | 22.140 | 016 | | Rel-5 | F | CR to 22.140 - Introduction of short codes for VASP addressing | 5.1.0 | 5.2.0 | MMS Enhancement |
+| SP-17 | SP-020553 | S1-021786 | 22.140 | 017 | | Rel-5 | F | Removal of SMS and USSD as possible bearers from 22.140 v5.2.0 | 5.2.0 | 5.3.0 | MMS |
+| SP-18 | SP-020814 | S1-022387 | 22.140 | 019 | 1 | Rel-5 | A | Storage of configuration information on the (U)SIM - for Rel 5 | 5.3.0 | 5.4.0 | MESS5-MMS |
+| SP-18 | SP-020660 | S1-022312 | 22.140 | 020 | | Rel-6 | B | Requirements for the MMS charging models and charging mechanisms | 5.4.0 | 6.0.0 | MMS |
+| SP-18 | SP-020660 | S1-022313 | 22.140 | 021 | | Rel-6 | B | Additional feature for the MMS charging model | 5.4.0 | 6.0.0 | MMS |
+| SP-18 | SP-020660 | S1-022314 | 22.140 | 022 | | Rel-6 | B | Requirement for preventing the loop of MM | 5.4.0 | 6.0.0 | MMS |
+| SP-19 | SP-030024 | S1-030267 | 22.140 | 024 | - | Rel-6 | C | Update to 22.140 to clarify prioritisation | 6.0.0 | 6.1.0 | MMS6-SR |
+| SP-20 | SP-030256 | S1-030493 | 22.140 | 026 | - | Rel-6 | B | Add DRM Requirement to 22.140 | 6.1.0 | 6.2.0 | MMS |
+| SP-20 | SP-030256 | S1-030494 | 22.140 | 027 | | Rel-6 | B | Add a Standardized Charging Record Interface Requirement to 22.140 | 6.1.0 | 6.2.0 | MMS |
+| SP-20 | SP-030256 | S1-030551 | 22.140 | 028 | | Rel-6 | B | Add a Standardized User Profile to 22.140 | 6.1.0 | 6.2.0 | MMS |
+| SP-20 | SP-030256 | S1-030536 | 22.140 | 029 | | Rel-6 | B | Addition of blacklisting capability in the the multimedia messaging profiles | 6.1.0 | 6.2.0 | R6: MMS |
+| SP-20 | SP-030257 | S1-030638 | 22.140 | 034 | - | Rel-6 | F | Error Messages in MMS | 6.1.0 | 6.2.0 | MMS-R6 |
+
+| | | | | | | | | | | | |
+|---------|-----------|-----------|--------|-----|---|-------|---|-------------------------------------------------------|--------|--------|---------|
+| SP-21 | SP-030460 | S1-030883 | 22.140 | 035 | - | Rel-6 | B | Management of Hyperlinks with MMS | 6.2.0 | 6.3.0 | MMS |
+| SP-21 | SP-030552 | S1-031056 | 22.140 | 036 | 2 | Rel-6 | B | MM storage in the USIM | 6.2.0 | 6.3.0 | MMS-R6 |
+| SP-21 | SP-030542 | S1-031055 | 22.140 | 037 | 1 | Rel-6 | B | Conditional delivery behaviour | 6.2.0 | 6.3.0 | MMS6 |
+| SP-22 | SP-030689 | S1-031240 | 22.140 | 039 | - | Rel-6 | B | MMS targeting UE elements | 6.3.0 | 6.4.0 | MMS |
+| SP-22 | SP-030783 | SP-030783 | 22.140 | 040 | 2 | Rel-6 | B | UICC interaction with MMS clients | 6.3.0 | 6.4.0 | MMS-R6 |
+| SP-23 | SP-040203 | | 22.140 | 041 | 1 | Rel-6 | B | MMS targeting UE elements | 6.4.0 | 6.5.0 | MMS |
+| SP-23 | SP-040093 | S1-040234 | 22.140 | 042 | - | Rel-6 | C | Prepaid – lack of credit error in MMS | 6.4.0 | 6.5.0 | MESS6 |
+| SP-24 | SP-040450 | S1-040540 | 22.140 | 044 | 1 | Rel-6 | B | Support of MMS operator specific services | 6.5.0 | 6.6.0 | MMS-6 |
+| SP-24 | SP-040290 | S1-040541 | 22.140 | 045 | - | Rel-6 | F | Clarification on MMS client interaction with UICC | 6.5.0 | 6.6.0 | MMS-R6 |
+| SP-24 | SP-040290 | S1-040542 | 22.140 | 046 | | Rel-6 | F | Update to scope and removal of VHE based requirement. | 6.5.0 | 6.6.0 | MMS6-SR |
+| SP-27 | SP-050059 | S1-050218 | 22.140 | 047 | - | Rel-6 | F | Removal of Reference to TS 22.121 | 6.6.0 | 6.7.0 | TEI6 |
+| SP-36 | | | 22.140 | | | Rel-7 | | Updated from Rel-6 to Rel-7 | 6.7.0 | 7.0.0 | |
+| SP-42 | - | - | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | - | - | - | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|-----------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-07 | SA#88e | - | - | - | - | Updated to Rel-16 by MCC | 16.0.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22142/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22142/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/22_series/22142/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/22_series/22142/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22142/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22b1a112fd33e8f703481f37849af5ac208240e8
--- /dev/null
+++ b/marked/Rel-18/22_series/22142/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c68a2e2c5effdd5d4c045bb58da0e6808eba6808bba7552f708436b752b3efe
+size 5400
diff --git a/marked/Rel-18/22_series/22142/raw.md b/marked/Rel-18/22_series/22142/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8a55dc01df80c64aea414c1427e5f13265786263
--- /dev/null
+++ b/marked/Rel-18/22_series/22142/raw.md
@@ -0,0 +1,445 @@
+
+
+# 3GPP TS 22.142 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Value Added Services (VAS) for Short Message Service (SMS) requirements (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+SMS, Services
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-----------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Requirements ..... | 6 |
+| 4.1 High Level Requirements..... | 6 |
+| 4.2 Overall Service Requirements..... | 6 |
+| 4.2.1 Management of Service Information..... | 6 |
+| 4.2.1.1 Capabilities provided to the user ..... | 6 |
+| 4.2.1.2 Capabilities provided to the network ..... | 7 |
+| 4.2.1.3 Capabilities provided to authorized third party ..... | 7 |
+| 4.2.2 Short Message processing ..... | 7 |
+| 4.2.3 Short Message Forwarding..... | 7 |
+| 4.2.4 Short Message Forwarding multiple subscriptions ..... | 7 |
+| 4.2.5 Short Message filtering..... | 8 |
+| 4.2.6 Short Message receipt..... | 8 |
+| 4.2.7 Short Message Network Storage ..... | 8 |
+| 4.2.8 Short Message to multiple destinations..... | 8 |
+| 4.2.9 Short Message Virtual Private Network (VPN) ..... | 9 |
+| 4.2.10 Short Message Auto Reply ..... | 9 |
+| 4.2.11 Short Message Personal Signature ..... | 9 |
+| 4.2.12 Short Message Deferred Delivery ..... | 9 |
+| 4.2.13 Management and control of network based repository ..... | 9 |
+| 4.2.14 Addressing..... | 10 |
+| 5 Requirements for service priority and Interaction ..... | 10 |
+| 6 Quality of Service ..... | 10 |
+| 7 Charging aspects for VAS-SMS ..... | 10 |
+| 8 Security ..... | 11 |
+| 9 Interworking..... | 11 |
+| 10 Roaming..... | 11 |
+| Annex A: Change history ..... | 12 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies the service requirements associated with series of value-added features for short message service (SMS). Specifically, the objective of this document is to specify potential new value-added services for SMS in 3GPP that need to be standardized.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
+- [3] ITU-T E.164 (1997): "The International Public Telecommunications Numbering Plan".
+- [4] IETF STD 0011 (RFC 2822): "Internet Message Format", URL: .
+- [5] 3GPP TS 23.204: " Support of Short Message Service (SMS) over Generic 3GPP Internet Protocol (IP) Access. Stage 2".
+- [6] 3GPP TR 22.942: "Study on Value Added Services (VAS) for Short Message Service (SMS)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in [1] and the following apply:
+
+**Short Message Forwarding:** The service permits the network to send all incoming short messages addressed to the called mobile subscriber's directory number to another directory number.
+
+**Short Message Filtering:** The service permits the network to filter certain short messages on behalf of a called/calling party based on the called/calling party's preferences.
+
+**Short Message Receipt:** The service permits the network to send one or more receipts to inform a calling party the status of sent message.
+
+**Short Message Network Storage:** The service permits the network to help the subscriber store messages that the subscriber has sent or received.
+
+**SMS VPN service:** Enables the exchange of SMS messages between VPN (Virtual Private Network) members by using a short number, usually similar to the receiver fixed extension number, instead of using the full mobile number of the recipient.
+
+**SMS Auto Reply:** The SMS Auto Reply service enables the subscriber to activate an automatic SMS reply in response to incoming SMS messages, both from in network subscribers as well as from foreign networks subscribers (incoming MT messages from foreign networks).
+
+**SMS Personal Signature:** The service allows the end user to personalize its outgoing messages either with a personal remark or a business title. The service enables a user to pre-define a text that will automatically be added to all outgoing SMS messages.
+
+**SMS Deferred Delivery:** The SMS deferred delivery service provides a subscriber the capability to control the actual delivery time of messages created by him. User using this capability can send a message and configure it to be delivered at a later time.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply in addition to [1]:
+
+| | |
+|---------|----------------------------------------|
+| SMS-SC | Short Message Service - Service Centre |
+| SM | Short Message |
+| VAS-SMS | Value-added Services for SMS |
+
+# --- 4 Requirements
+
+## 4.1 High Level Requirements
+
+The VAS-SMS shall be implemented without influencing the existing SMS service.
+
+The VAS-SMS shall be implemented without depending on the terminal's capability.
+
+Users shall be able to register, activate, deactivate, withdraw and reconfigure VAS-SMS via the UE, or web portals.
+
+The VAS-SMS shall be designed and implemented in a way to provide users who joined the services one coherent and identical user experience, regardless of the SM flow and SM scenario (e.g. messages to and from applications, MO-MT in an in network and MT from Foreign Network).
+
+Provisioning of VAS-SMS by one operator should not depend on the support of other operators i.e. originating or terminating VAS-SMS services should be independently.
+
+## 4.2 Overall Service Requirements
+
+### 4.2.1 Management of Service Information
+
+#### 4.2.1.1 Capabilities provided to the user
+
+The VAS-SMS shall be able to support a request from an application to query/change the choice of services for a subscriber.
+
+The VAS-SMS shall be able to support a request from an application to query/change the subscriber's preferences for a certain service, for example:
+
+- i) To add or delete or modify a subscriber's filtering conditions by which VAS-SMS can refuse some of the subscriber's incoming messages.
+- ii) To modify a subscriber's signature that will be appended to an SM sent from the subscriber.
+- iii) To modify a subscriber's forwarding address that substitutes for the subscriber's original receiving address.
+
+#### 4.2.1.2 Capabilities provided to the network
+
+The VAS-SMS shall be able to support a request to query/change the subscriber's information, for example:
+
+- i) To get the detail information about the subscriber's service.
+- ii) To add or delete a subscriber's service information.
+
+The VAS-SMS shall be able to support a request to query the handling results of the subscription service.
+
+#### 4.2.1.3 Capabilities provided to authorized third party
+
+The VAS-SMS shall be able to support a request from an application to modify the contents that will be appended to an SM, for example:
+
+- i) to load or unload a particular content provided by the third party
+- ii) to associate a content with a particular subscriber or a type of subscribers
+- iii) to define the trigger for inclusion or change of such content
+
+Note: The management of VAS4SMS service is out of scope of 3GPP standardisation.
+
+### 4.2.2 Short Message processing
+
+The VAS-SMS should be able to deal with the content of an SM, for example:
+
+- i) To insert content (as agreed with the subscriber, or as agreed with a third party and authorized by the subscriber) into the original SM and form a new SM (e.g. append the signature to the SM, append the content as provided by the third party, ...).
+- ii) To compile an SM by containing operator's information (e.g. construct a delivery report).
+- iii) To use certain words in an SM as the filtering criteria.
+
+The VAS-SMS should be able to convert the format of an SM into other formats (e.g. email, WAP message, etc).
+
+### 4.2.3 Short Message Forwarding
+
+It shall be supported that users can set certain conditions (e.g., different time periods) for message forwarding. There are no significant delays to any part of the service.
+
+With the advent of SM forwarding there is also the issue of how to handle the situation when a user by mistake sets forwarding to wrong number (a number that is in use). Ideally a recipient should be capable of stopping the delivery of such SM to its own address. As a minimum the recipient's operator should be capable of identifying forwarded SM and stop delivery. Infinite forwarding loops needs to be prevented and the maximum number of times the SM is forwarded should be limited.
+
+SM Forwarding service should support forwarding to numbers of both the operator as well as other operators.
+
+It shall be possible to Notify a recipient upon activation of the service and only upon his approval activate the service for the user.
+
+There may be no relation between SM Forwarding service and Voice Call Forwarding service.
+
+### 4.2.4 Short Message Forwarding multiple subscriptions
+
+It may be supported that an operator can set a group of subscriptions for which SM are forwarded to the active/last activated subscription of that group, under the condition that the delivery address of the SM is associated to a subscription of that group and that address is not registered on the network.
+
+### 4.2.5 Short Message filtering
+
+It shall be supported that users can set certain conditions for message filtering.
+
+### 4.2.6 Short Message receipt
+
+It shall be supported that the callee can configure the content of an additional receipt SM for different callers, so the standard Status Report may be accompanied by a newly generated SM with the content provided by the operator.
+
+### 4.2.7 Short Message Network Storage
+
+It should be possible for the operator to support Short Message Network Storage to allow users to store the messages in the network.
+
+It should be possible for users to store the messages in the network based on their personal settings (e.g. store all sent & received messages, store the messages from/to particular users, store the messages sent & received in a specified period of time etc).
+
+It should be possible for users to store and manage the messages for their preference (e.g. users can set different folders to store different sort of messages, therefore it is convenient to inquire the stored messages based on message sort or key words).
+
+It should be possible for the operator to ensure all relevant information of the messages stored in the network are consistent with that displayed to users, e.g. content of the messages, sender/recipient, sending/receiving time, etc.
+
+It shall be supported that user can pre-set certain conditions for storage. The storage condition includes all sent messages, all received messages, messages sent to or received from one or more special phone numbers and so on.
+
+It should be possible for the operator to prevent storage of configuration SM, notifications (e.g. voice mail, SM delivery notifications).
+
+It shall be supported that users can transfer the messages stored in the message depository to any other mobile phone.
+
+It shall be supported that users can inquire the messages stored in the message depository according to certain query conditions (e.g., short message receiver, short message sender, key words etc.).
+
+It shall be supported that users can manage the stored messages via a website, and it shall be possible for the user to set access right for other users ( e.g. read only , read and download etc), in this way, other users are able to inquire his stored messages through a link to the website after valid authentication.
+
+In case of multiple delivery attempts SM will be copied only once regardless of the number of delivery attempts.
+
+It shall be possible to combine concatenated SM to single Message in the Network store or alternatively indicate in the message that it is part of concatenated SM.
+
+The Short Message Network Storage service shall prevent duplicate storage message as a result of failure in transmission of the original SM.
+
+Messages should be stored in the Network Storage regardless of the user availability and as soon as the original SM is being processed in the SMSC.
+
+### 4.2.8 Short Message to multiple destinations
+
+It shall be able to support inclusion of multiple recipients in a message when a user sends a single message to multiple individuals.
+
+It should be possible for all recipients of the message to be aware of other recipients.
+
+It should be possible for a recipient to choose to whom the reply message is sent, i.e. to the original sender and to other recipients of the original message.
+
+It shall be supported that a user can include multiple destination addresses in a message. The recipient except those addresses displaying information is blocked shall receive information on all recipients of the message.
+
+It shall be supported that each recipient of the message can send a message back to all recipients of the original message.
+
+### 4.2.9 Short Message Virtual Private Network (VPN)
+
+Sending messages to local numbers based on the dialling plan should be supported. There shall be no significant delays to any part of the service.
+
+### 4.2.10 Short Message Auto Reply
+
+It shall be possible that users can activate the SM Auto Reply Service to be active for different time periods. In addition it shall be possible to configure the system to reply only once to each sender in a predefined period of time.
+
+It shall be possible for users to configure and manage their Automatic Reply messages, e.g. edit and delete the content of the message.
+
+It shall be possible for users to set different Automatic Reply messages to different senders.
+
+Auto reply to auto reply loops need to be prevented.
+
+### 4.2.11 Short Message Personal Signature
+
+The SM Personal Signature Service shall support certain conditions configured by users or control system wide (e.g., append personal signature depending on the original short message length, append personal signature to certain destinations). There shall be no significant delays to any part of the service.
+
+### 4.2.12 Short Message Deferred Delivery
+
+The SM Deferred delivery shall support the following delivery time options:
+
+- Relative timing – The text will include information as for the of how many more days, hours, minutes shall pass before the message shall be delivered.
+- Absolute timing - The text will include information indicating of the specific Date and Time for the message to be delivered
+
+The SM Deferred Delivery Service shall support all type of languages
+
+The SM Deferred Delivery Service shall support concatenated messages
+
+There shall be no significant delays to any part of the service.
+
+### 4.2.13 Management and control of network based repository
+
+VAS-SMS should be able to provide following capabilities to support network based repository:
+
+- The VAS-SMS should allow configuring in such a way that certain sent or received messages of a particular user can be stored persistently in a network based repository.
+- The VAS-SMS should be able to support a request from SMS-SC to persistently store a sent message in a network based repository at the time of sending.
+- The VAS-SMS should be able to support a request from an application to upload certain messages into a network based repository for persistent storage.
+- The VAS-SMS should be able to support a request from an application to retrieve/delete certain messages stored in a network based repository
+- The VAS-SMS should be able to support a request from an application to view the list of messages and related attributes (e.g. sender, recipient, date/time, etc) in a network based repository
+
+### 4.2.14 Addressing
+
+The VAS-SMS should support different addressing formats to identify the sender and recipient; it should support both MSISDN[3] and e-mail addressing schemes[4].
+
+A short number should be supported. This number should be unique within VPN where it is used.
+
+The VAS-SMS should support an alpha-numeric addressing format (similar to specified in [2]).
+
+The VAS-SMS should be able to submit one message to multiple recipients.
+
+The VAS-SMS should be able to support the request to hide the sender's or other recipients' addresses.
+
+# --- 5 Requirements for service priority and Interaction
+
+The different rules of VAS-SMS priority and interaction are provided by operator. For example, the priority order maybe as following:
+
+- SM Filtering
+- SM Network Storage
+- SM Forwarding
+- etc.
+
+The VAS-SMS should be classified by priority and triggered according to priority order.
+
+The VAS-SMS should provide the capability to configure certain priority.
+
+Caller SMS receipt has higher priority than Callee SMS Receipt service.
+
+# --- 6 Quality of Service
+
+The quality of basic SMS service should not be affected by introducing the VAS-SMS.
+
+The following key performance for quality of VAS-SMS shall be kept consistent with basic SMS. For example:
+
+- SMS delivery successful rate
+- authentication successful rate
+- end to end data loss rate
+- end to end data delay
+- charging successful rate
+- reliability of network and service
+
+# --- 7 Charging aspects for VAS-SMS
+
+The VAS-SMS shall provide accounting rules for accurate accounting. It shall be able to support following charging aspects.
+
+- Charging Model
+
+The VAS-SMS charging includes basic communication fee and special service fee.
+
+Basic communication fee is paid for usage of network resource. CDR is generated by SMSC. Special service fee is paid for usage of the VAS-SMS. CDR is generated by the VAS-SMS system. Charging models of special service fee shall include but not limit to the following items:
+
+- i) charging per VAS-SMS
+- ii) monthly basis
+
+Per each service category, different charging models and rates should be configurable for the special service fee.
+
+- Charging principle
+
+The following principles shall be supported according to different service categories:
+
+- i) VAS-SMS triggered by sending party – basic communication fee and special service fee are paid by the sending party.
+- ii) VAS-SMS services triggered by recipient – basic communication fee is paid by the sending party, whilst special service fee is paid by the recipient.
+- iii) Charging only happens after the status report has been received by the SMSC.
+
+- Charging Scheme
+
+The VAS-SMS shall support a standardized interface to transfer CDRs and other charging related information between the VAS-SMS and the billing system for prepaid and post-paid billing solutions.
+
+# --- 8 Security
+
+Security of the VAS-SMS services shall be consistent with basic SMS service. The user shall be able to use and access the VAS-SMS services in a secure manner.
+
+VAS-SMS should support Lawful Interception as required by Regional Regulations.
+
+# --- 9 Interworking
+
+Interworking with existing messaging technologies and messaging services should be supported.
+
+The VAS-SMS should be able to send the content of an SM to a reachable address, for example:
+
+- i) To send an email to email servers after converting the SM into an email.
+- ii) To send a WAP message to a WAP Push Gateway after converting the SM into a WAP message.
+- iii) To send an SM to a subscriber by sending an SM to SMSC.
+- iv) To send an SM via IMS. Refer to [5].
+- v) To send a delivery report .
+
+# --- 10 Roaming
+
+General roaming requirements should be compliant with roaming function of SMS.
+
+The user should be able to experience the consistent VAS-SMS services whether in home network or roaming.
+
+# Annex A: Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|-----------------------------------------------------------|--------|--------|---------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-44 | SP-090376 | S1-091375 | 22.142 | 0001 | 1 | Rel-9 | C | Limiting the maximum number of times the SM is forwarded | 9.0.0 | 9.1.0 | VAS4SMS |
+| SP-44 | SP-090376 | S1-091376 | 22.142 | 0002 | 1 | Rel-9 | C | To prevent auto reply to auto reply loop | 9.0.0 | 9.1.0 | VAS4SMS |
+| SP-44 | SP-090376 | S1-091362 | 22.142 | 0003 | 1 | Rel-9 | B | Independent provisioning of VAS-SMS | 9.0.0 | 9.1.0 | VAS4SMS |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | | | | | | | | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2019-07 | - | - | - | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22146/0019f09403376d6444ee323591fa2e98_img.jpg b/marked/Rel-18/22_series/22146/0019f09403376d6444ee323591fa2e98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..824e41e7890d7758a645bc53de96f7df7cf0b488
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/0019f09403376d6444ee323591fa2e98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e59b13973df53f1123b41f9866eed5193fff2260c6c13d0733c967e9c12c8ff5
+size 33994
diff --git a/marked/Rel-18/22_series/22146/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg b/marked/Rel-18/22_series/22146/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99b6a4e1dd44b3027d08a9b328f7cde73882bcc6
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1734f672cc3e44b47d8e63c8d3b0e1baec360799e4ee1c39610895156cb33e59
+size 83005
diff --git a/marked/Rel-18/22_series/22146/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/22_series/22146/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bd4a697719c7e1d4183a8693c6083beeb47bad7
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b58880635cf6d7ef3deec8ed8c3736afce44d21bb26469f199836eeeb8750adf
+size 35924
diff --git a/marked/Rel-18/22_series/22146/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22146/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/22_series/22146/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22146/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2df6ad86e7021bc7b157060e6b949b94736b13ff
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53faf037465dde7b382f95640f809053f12882698bd17ee17c7b0f3ac7e8cf9
+size 5413
diff --git a/marked/Rel-18/22_series/22146/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-18/22_series/22146/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bae8a4f1f6b6be11bf83a23269d2662de9637dc0
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85d03079dd4444afa57db11a832330f397980e4f2480719b139775646cd9e577
+size 101188
diff --git a/marked/Rel-18/22_series/22146/raw.md b/marked/Rel-18/22_series/22146/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..17838bf4df4b02c1b3b52adc4cfc5299ac08772d
--- /dev/null
+++ b/marked/Rel-18/22_series/22146/raw.md
@@ -0,0 +1,554 @@
+
+
+# 3GPP TS 22.146 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Broadcast/Multicast Service (MBMS); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, service, multicast, broadcast
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 General description of a multimedia broadcast/multicast service (MBMS)..... | 7 |
+| 4.1 MBMS broadcast mode..... | 7 |
+| 4.2 MBMS multicast mode ..... | 8 |
+| 4.2.1 Multicast subscription and reception..... | 9 |
+| 4.3 Discovery and announcement of MBMS services ..... | 10 |
+| 5 High level requirements ..... | 10 |
+| 5.1 Broadcast mode..... | 10 |
+| 5.1.1 Home environment requirements ..... | 10 |
+| 5.1.2 User requirements for MBMS ..... | 11 |
+| 5.2 Multicast mode..... | 12 |
+| 5.2.1 Home environment requirements ..... | 12 |
+| 5.2.2 User requirements for MBMS ..... | 13 |
+| 5.3 Availability..... | 14 |
+| 6 Security ..... | 14 |
+| 7 Charging..... | 14 |
+| 7.1 Broadcast mode..... | 14 |
+| 7.2 Multicast mode..... | 14 |
+| Annex A (informative): MBMS Bit Rates..... | 16 |
+| Annex B (informative): Change history ..... | 17 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+Broadcast and Multicast are methods for transmitting data-grams from a single source to several destinations (point-to-multipoint). To date, release-4 and release-99 define two services in this respect:
+
+A cell broadcast service (CBS) allowing for low bit-rate data to be transmitted to all subscribers in a set of given cells over a shared broadcast channel. This service offers a message-based service [5,6]
+
+An IP-Multicast service allowing for mobile subscribers to receive multicast traffic. This service does not allow for multiple subscribers to share radio or core network resources and as such does not offer any advantages as far as resource utilization within the PLMN and over the radio access network. [3,4]
+
+It is envisaged that for some applications, multiple users can receive the same data at the same time. The benefit of multicast and broadcast in the network is that the data is sent once on each link. For example, an SGSN will send data once to an RNC regardless of the number of Node Bs and UEs that wish to receive it. The benefit of multicast and broadcast on the air interface is that many users can receive the same data on a common channel, thus not clogging up the air interface with multiple transmissions of the same data.
+
+With increasing use of high bandwidth applications in third generation mobile systems, especially with a large number of users receiving the same high data rate services, efficient information distribution is essential. Thus, broadcast and multicast are techniques to decrease the amount of data within the network and use resources more efficiently
+
+# --- 1 Scope
+
+This Technical specification defines the stage one description of the Broadcast and Multicast Services for the 3GPP System. Stage one is the set of requirements which shall be supported for the provision of Broadcast and Multicast services, seen primarily from the subscriber's and service providers' points of view.
+
+Note: Non-3GPP access systems may provide MBMS transport service, but this is not in the scope of this specification.
+
+This TS includes information applicable to network operators, content providers, and terminal and network manufacturers.
+
+This TS contains the core requirements for Multicast and Broadcast Services, which are sufficient to provide a complete service.
+
+# --- 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] RFC 1112: "Host extensions for IP multicasting", RFC 1920: " Internet official protocol standards", RFC 1458: "Requirements for multicast protocols", RFC 1301: "Multicast transport protocol"
+- [3] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1".
+- [4] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [5] 3GPP TS 25.324: "Broadcast/Multicast Control BMC"
+- [6] 3GPP TS 23.041: "Technical Realization of Cell Broadcast Service (CBS)"
+- [7] 3GPP TS 22.246: "MBMS User Services".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the definitions in 3GPP TR 21.905 [1] as well as the following definitions apply.
+
+**Broadcast service area:** The area in which a specific broadcast service is available. It is defined individually per broadcast service. The broadcast service area may represent the coverage area of the entire PLMN, or part(s) of the PLMN's coverage area. The broadcast service area is the sum of all local broadcast areas offering the same service.
+
+**Local Broadcast Area:** The area of a broadcast service, where the service content is the same. One broadcast service may have different content in different local broadcast areas.
+
+**Broadcast mode:** The part of MBMS that supports broadcast services.
+
+**Broadcast service:** A unidirectional point-to-multipoint service in which data is efficiently transmitted from a single source to multiple UEs in the associated broadcast service area. Broadcast services may be received by all users who have enabled the specific broadcast service locally on their UE and who are in the broadcast area defined for the service.
+
+**Broadcast session:** A continuous and time-bounded reception of a broadcast service by the UE. A single broadcast service can only have one broadcast session at any time. A broadcast service may consist of multiple successive broadcast sessions.
+
+**Mobile Station (MS):** Defined in 3GPP TS 24.002. (The abbreviation "UE" in this specification refers both to MS and User Equipment.)
+
+**Multicast transmission activation:** The process by which the network activates the transmission of Multicast data.
+
+**Multicast service area:** The area in which a specific multicast service is available. It is defined individually per multicast service. The multicast service area may represent the coverage area of an entire PLMN, or part(s) of the PLMN's coverage area. The multicast service area is the sum of all local multicast areas offering the same service.
+
+**Local multicast area:** The area of a multicast service, where the service content is the same. One multicast service may have different content in different local multicast areas.
+
+**Multicast mode:** The part of MBMS that supports multicast services.
+
+**Multicast joining:** The process by which a user joins a multicast group.
+
+**Multicast session:** A continuous and time-bounded reception of a multicast service by the UE. A single multicast service can only have one multicast session at any time. A multicast service may consist of multiple successive multicast sessions.
+
+**Multimedia Broadcast/Multicast Service (MBMS):** A unidirectional point-to-multipoint service in which data is transmitted from a single source entity to a group of users in a specific area. The MBMS has two modes: Broadcast mode and Multicast mode.
+
+**Multicast group:** A group of users that have an activated MBMS in multicast mode and therefore are ready to or are receiving data transmitted by this service. The multicast group is a subset of the **Multicast subscription group**. Multicast subscription group members may join the corresponding multicast group.
+
+**Multicast service:** A unidirectional point-to-multipoint service in which data is efficiently transmitted from a single source to a multicast group in the associated multicast service area. Multicast services can only be received by such users that are subscribed to the specific multicast service and have joined the multicast group associated with the specific service.
+
+**Multicast subscription:** The process by which a user subscribes or is subscribed to a multicast subscription group and thereby is authorised to join certain multicast services. Multicast subscription is performed either upon user selection or due to home environment initiation.
+
+**Multicast Subscription Group:** A group of users who are subscribed to a certain MBMS in multicast mode and therefore authorised to join and receive multicast services associated with this group.
+
+**User Equipment:** defined in TS 21.905. An occurrence of a User Equipment is an MS for GSM as defined in TS 24.002.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|------|----------------------------------------|
+| MBMS | Multimedia Broadcast/Multicast Service |
+| MS | Mobile Station |
+| UE | User Equipment |
+
+# 4 General description of a multimedia broadcast/multicast service (MBMS)
+
+Point to multipoint services exist today which allow data from a single source entity to be transmitted to multiple endpoints. These services are expected to be used extensively over wireless networks, hence there is a need for a capability in the PLMN to efficiently support them. The Multimedia Broadcast/Multicast Service (MBMS) will provide this capability for such broadcast/multicast services provided by the home environment and other VASPs.
+
+The MBMS is a unidirectional point to multipoint bearer service in which data is transmitted from a single source entity to multiple recipients. It is anticipated that other services will use these bearer capabilities.
+
+MBMS also enables an IMS application located on an application server to send multimedia to a set of IMS users in the service area by means of MBMS bearer service.
+
+3GPP has defined two modes of operation:
+
+- the broadcast mode
+- the multicast mode.
+
+## 4.1 MBMS broadcast mode
+
+The broadcast mode is a unidirectional point-to-multipoint transmission of multimedia data (e.g. text, audio, picture, video) from a single source entity to all users in a broadcast service area. The broadcast mode is intended to efficiently use radio/network resources e.g. data is transmitted over a common radio channel. Data is transmitted in the broadcast service area as defined by the network (Home environment).
+
+MBMS data transmission should adapt to different RAN capabilities or different radio resource availability, e.g. by reducing the bitrate of the MBMS data. The selection and description of an appropriate mechanism is subject to MBMS stage 2.
+
+Figure 1 gives an example of how a network can be configured to broadcast a variety of high bit rate services to users within the associated broadcast service area.
+
+A broadcast service received by the UE, involves one or more successive broadcast sessions. A broadcast service might, for example, consist of a single on-going session (e.g. a media stream) or may involve several intermittent sessions over an extended period of time (e.g. messages).
+
+
+
+Figure 1: Example of Multicast Broadcast Mode Network. The diagram illustrates the network architecture for MBMS. On the left, a 'Broadcast Service Area' contains several mobile devices (UEs). A large red arrow labeled 'Broadcast Data' points from the 'UMTS Packet Switching Core' to these devices. The core is connected to a 'Multimedia Broadcast Control Unit (MBMS)'. The core also connects to a list of services: 'QoS handling', 'VASP authentication', 'Broadcast Area Configuration', and 'Radio resource management'. The core is further connected to a 'Multimedia Services' cloud, which is connected to 'Operator Specific Services' and 'Internet Hosted Services'. At the bottom, a 'FM/Video Stream' is shown being received by a mobile device.
+
+Figure 1: Example of Multicast Broadcast Mode Network
+
+The broadcast mode should not be confused with the existing Cell Broadcast service (CBS) which is currently used for low bit rate services (messaging) whilst the broadcast mode enables the broadcast of multimedia services (Audio, Video etc).
+
+An example of a service using the broadcast mode could be advertising or a welcome message to the network. As not all users attached to the network may wish to receive these messages then the user shall be able to enable/disable the reception of these broadcast service on his UE.
+
+The broadcast mode differs from the multicast mode in that there is no specific requirement to activate or subscribe to the MBMS in broadcast mode.
+
+The broadcast mode should allow terminals to minimise their power consumption.
+
+It is expected that charging data for the end user will not be generated for this mode at MBMS Transport Service layer. Charging data related to security procedures for the end user at MBMS User Service layer may be generated, cf. clause 7. The reception of the traffic in the broadcast mode is not guaranteed. The receiver may be able to recognize data loss.
+
+## 4.2 MBMS multicast mode
+
+The multicast mode allows the unidirectional point-to-multipoint transmission of multimedia data (e.g. text, audio, picture, video) from a single source point to a multicast group in a multicast service area. The multicast mode is intended to efficiently use radio/network resources e.g. data is transmitted over a common radio channel. Data is transmitted in the multicast service area as defined by the network (Home environment). In the multicast mode there is the possibility for the network to selectively transmit to cells within the multicast service area which contain members of a multicast group.
+
+MBMS data transmission should adapt to different RAN capabilities or different radio resource availability, e.g. by reducing the bitrate of the MBMS data. The selection and description of an appropriate mechanism is subject to MBMS stage 2.
+
+A multicast service received by the UE, involves one or more successive multicast sessions. A multicast service might, for example, consist of a single on-going session (e.g. a multimedia stream) or may involve several intermittent multicast sessions over an extended period of time (e.g. messages).
+
+An example of a service using the multicast mode could be a football results service for which a subscription is required.
+
+Unlike the broadcast mode, the multicast mode generally requires a subscription to the multicast subscription group and then the user joining the corresponding multicast group. The subscription and group joining may be made by the PLMN operator, the user or a third party on their behalf (e.g. company). Unlike the broadcast mode, it is expected that charging data for the end user will be generated for this mode at MBMS Transport Service layer. Charging data related to security procedures for the end user at MBMS User Service layer may be generated, cf. clause 7.
+
+
+
+Figure 2: Example of Multicast Mode Network. This diagram illustrates the architecture of a multicast mode network. On the left, multiple User Equipment (UE) icons are shown with a 'Multicast Subscription Group' label. Arrows point from these UEs into a central cloud labeled 'Multicast Capable UTRAN GERAN'. Within this cloud, three horizontal arrows represent 'Service synchronization', 'User interest indication', and 'Multicast Data Stream'. These streams connect to a central box labeled '3GPP Packet Core / IP Multimedia'. This box lists several functions: 'QoS handling', 'Service Provisioning', 'Subscription Handling', 'Billing/Accounting', 'Activation', and 'Multicast area Control'. From the Packet Core, lines connect to three external service clouds: 'Multimedia Services' (yellow), 'Operator Specific Services' (orange), and 'IP Network' (purple). The IP Network cloud is further connected to a list of services: 'Multimedia Streaming', 'Live web casting', and 'TV news/sports/Advertising'. A green cloud labeled 'IP Multimedia subsystem' is also connected to the Packet Core.
+
+Figure 2: Example of Multicast Mode Network
+
+Reception of multicast services cannot be guaranteed over the access network. For many applications and services guaranteed data reception may be carried out by higher layer services or applications which make use of MBMS.
+
+Multicast mode should allow terminals to minimise their power consumption.
+
+The multicast mode defined in this specification should not be confused with IP Multicast (RFCs 1112, 1301, 1458, 1920 [2]). There are similarities between these two services and such similarities may be exploited in 3GPP networks given that 3GPP multicast mode has been defined with consideration to maximizing efficiency on the radio interface and of network resources.
+
+Multicast mode shall be inter-operable with IETF IP Multicast. This could allow the best use of IP service platforms to help maximize the availability of applications and content so that current and future services can be delivered in a more resource efficient manner. Figure 2 above shows a general high level overview of multicast mode network.
+
+### 4.2.1 Multicast subscription and reception
+
+The following is the expected sequence for the user to be able to access the MBMS multicast mode:
+
+- 1 The user subscribes or is subscribed to a multicast subscription group which is uniquely identified and thereby becomes a member of that group. The subscription may be continuous (e.g. as defined by the subscriber's contract), time-limited, or generated by the subscriber on a one-time basis. The subscription to multicast services shall not be further standardized.
+- 2 The user discovers, or becomes aware (e.g. via service announcements), that there are multicast services currently active, or multicast services that will become active at some time later, at the user's current location.
+- 3a) The user selects a multicast service and hence the user joins the corresponding multicast group. The user should be able to join a multicast service as soon as possible after announcement of the service.
+- 3b) As an alternative, the Home Environment can join the user to the selected multicast group on behalf of the user, that has previously subscribed to this multicast group.
+
+Signalling exchange between the UE and the network might not be necessary in some cases, e.g. in the case of network congestion.
+
+- 4 If the transmission is not already in progress the network starts transmitting the corresponding multicast content. Alternatively, the transmission may start at a later time.
+- 5 The network may optionally select to set up unicast (point to point) connections to some users e.g. if there are insufficient users to justify multicasting
+
+- 6 The UE starts receiving the multicast data associated with the multicast group(s) it has joined
+- 7 The user may choose to stop receiving a selected multicast service and thereby leaves the multicast group. The user may also select to continue (or not) to receive service announcements for this multicast subscription group.
+- 8 The user may unsubscribe or be unsubscribed from the multicast subscription group and stop receiving both the multicast data and future service announcements for this multicast subscription group.
+
+The home environment shall be able to remove a user from a multicast group (deactivation) and if required remove the subscriber from the multicast subscription group (un-subscription). This is required to allow the operator to bar service.
+
+## 4.3 Discovery and announcement of MBMS services
+
+The user shall be able to find out or be informed about MBMS services available in the network. The network shall support service announcements both for the broadcast and multicast mode of MBMS in order to enable the user to be informed about the MBMS services available currently, or some time later.. Users should also be able to discover and monitor MBMS service availability e.g. using a URL.
+
+# --- 5 High level requirements
+
+## 5.1 Broadcast mode
+
+### 5.1.1 Home environment requirements
+
+- Broadcast services
+
+The PLMN operator shall be able to provision one or more broadcast services within his PLMN.
+
+The operators sharing a network shall be able to provide one or more broadcast services for their own subscribers and inbound roamers from roaming partners only. This shall be applicable for sharing of radio network and for sharing of radio network and the core network entities connected to the radio network.
+
+A broadcast area is configured individually for each broadcast service. Broadcast areas associated with different broadcast services are independent of each other and may overlap.
+
+A broadcast service shall be able to distribute different content data to different locations, i.e. local broadcast areas, within the broadcast service area as shown in figure 3. This allows the user to receive broadcast data depending on his location (e.g. a “nationwide traffic service” with localized traffic reports). Only one location specific version of content data is distributed to each of the individual local broadcast areas, i.e. in any location a user will never receive different content data from a single broadcast service.
+
+It shall be possible to define a broadcast service for only the subscribers and inbound roamers of one of the operators sharing network. The broadcast services transmitted in a broadcast service area of operator A shall only be available to the subscribers and inbound roamers of operator A. The broadcast areas of different sharing operators may cover the same geographical area. This shall be applicable for sharing of radio network and for sharing of radio network and the core network entities connected to the radio network.
+
+
+
+Diagram of Broadcast Service with different content data for different locations. A yellow box at the top is labeled 'Broadcast Service Data Source'. Below it, a dashed box labeled 'Broadcast Service Area' contains three rounded rectangles: 'Content data 1 in Local broadcast area A', 'Content data 2 in Local broadcast area B', and 'Content data 3 in Local broadcast area C'. Above each of these three boxes are three vertical lines labeled '1', '2', and '3'. A label 'QoS or Media component' is positioned to the left of these lines. The entire structure is connected from the top source to the local content boxes.
+
+**Figure 3 Broadcast Service with different content data for different locations**
+
+#### - Quality of service
+
+The PLMN operator shall be able to configure the quality of service for each individual broadcast service. It should be possible to adapt the MBMS data transmission to different RAN capabilities or different radio resource availability.
+
+The home environment shall be able to set priority to select which simultaneous broadcast services are supported when there is a limit on the resources available.-
+
+#### - Network and radio efficiency
+
+The PLMN operator shall be able to use network and radio resources in an efficient manner.
+
+NOTE: Allocation of resources based on actual need in the broadcast service area is not applicable for the broadcast mode.
+
+The operator shall be able to schedule a certain broadcast service at pre-determined times.
+
+#### - Types of data services
+
+MBMS in The broadcast mode shall be transparent for the transferred data packets independent of the type of service being transmitted, will support a number of services, and permit support of and therefore transfer all data types e.g. Audio, Data, Video or combinations thereof. A minimum number of data types may need to be identified to enable interoperability.
+
+#### - Sources of data services
+
+In addition to supporting their own broadcast services the PLMN shall as well support broadcast services from third parties (i.e. HE-VASPs or VASPs or IMS server)
+
+#### - Broadcast service announcements
+
+The PLMN operator shall be able to provide service announcements for a broadcast service within and outside of the broadcast area defined for the service.
+
+### 5.1.2 User requirements for MBMS
+
+#### - User mobility
+
+The user shall be able to continue receiving broadcast services throughout the broadcast service area. For example, in case of handover and presuming that a certain broadcast service is offered in the target cell, it should be possible for the user to continue receiving the service in the target cell.
+
+#### - User selectivity
+
+The user shall be able to discover what broadcast services are available at the user's current location and outside of the current location.
+
+The user shall be able to enable/disable the reception of specific broadcast services and can receive simultaneously more than one MBMS service.
+
+The user may be able to define service preference for reception. A priority procedure may be implemented to allow the user to select between simultaneous broadcast services e.g. while receiving commercial broadcast service a new broadcast service may interrupt this.
+
+While receiving one or more broadcast services, it shall be possible for the user to be informed about incoming voice calls or the availability of other MBMS services.
+
+Dependent on terminal capabilities, it shall be possible for the user to participate in other services, while simultaneously participating in MBMS services. For example the user can originate or receive a call or send and receive messages whilst receiving advertisements.
+
+## 5.2 Multicast mode
+
+### 5.2.1 Home environment requirements
+
+- Multicast services
+
+The PLMN operator shall be able to provision one or more multicast services. A multicast area is configured individually for each multicast service. Multicast areas associated with different multicast services are independent of each other and may overlap.
+
+Multicast service areas may cover part(s) of one or more PLMNs.
+
+A multicast service shall be able to distribute different content data to different locations, i.e. local multicast areas, within the multicast service area as shown in figure 4. This allows the user to receive multicast data depending on his location (e.g. a “nationwide traffic service” with localized traffic reports) Only one version of location specific content data is distributed to each of the individual local multicast areas, i.e. in any location a user will never receive different content data from a single multicast service.
+
+
+
+Diagram of Multicast Service with different content data for different locations. A yellow box at the top is labeled 'Multicast Service Data Source'. Below it, a horizontal line represents 'QoS or Media component', with three vertical lines labeled '1', '2', and '3' extending down to three separate boxes. These boxes are labeled 'Content data 1 in Local multicast area A', 'Content data 2 in Local multicast area B', and 'Content data 3 in Local multicast area C'. A dashed line encloses these three boxes and is labeled 'Multicast Service Area' at the bottom.
+
+**Figure 4 Multicast Service with different content data for different locations**
+
+- Multicast subscription groups and multicast groups
+
+The PLMN operator shall be able to provision one or more multicast subscription groups. The home environment shall be able to make a user a member of a multicast subscription group (subscription).
+
+On receipt of a request to join a multicast group, the PLMN shall check that the user is a member of the applicable multicast subscription group. The home environment shall be able to join users to the multicast group e.g. at the request of the subscriber.
+
+- Quality of service
+
+The PLMN operator shall be able to configure the quality of service for individual multicast services. It should be possible to adapt the MBMS data transmission to different RAN capabilities or different radio resource availability.
+
+As part of the same service, it should be possible for the operator to provide the UEs with multiple successive sessions with different quality-of-service for each session.
+
+The home environment shall be able to set priority to select which simultaneous multicast services are supported when there is a limit on the resources available.
+
+- Network and radio efficiency
+
+The PLMN operator shall be able to use network and radio resources in an efficient manner.
+
+Within the multicast service area, the network may distribute the data across the whole multicast service area or parts of the area. The decision to distribute to only parts of the multicast service area may be based on: a) multicast group members are present in a given part of the multicast area b) resources are not available in parts of the multicast service area.
+
+The operator shall be able to schedule a certain multicast service at pre-determined times.
+
+- Types of services
+
+The multicast mode shall be independent of the type of service being transmitted, will support a number of services, and permit support of all data types e.g. Audio, Data, Video or combinations thereof. A minimum number of data types may need to be identified to enable interoperability
+
+- Sources of services
+
+In addition to supporting their own multicast services the PLMN shall as well support multicast services by third parties (i.e. HE-VASPs or VASPs or IMS server).
+
+- Multicast service announcements
+
+The PLMN operator shall be able to provide service announcements for a multicast service within and outside of the multicast area defined for the service.
+
+### 5.2.2 User requirements for MBMS
+
+- User mobility
+
+The user shall be able to continue receiving multicast services throughout the multicast service area in which the service is provided. For example, in case of handover and presuming that a certain multicast service is offered in the target cell, it should be possible for the user to continue the session in the target cell. It is possible that data loss will occur due to user mobility.
+
+- User selectivity
+
+The user shall be able to discover what multicast services are available at the user's current location and outside of the current location. The user shall be able to select between different multicast services provided to the user and can receive simultaneously more than one MBMS service.
+
+The user may be able to define service preference for reception. A priority procedure may be implemented to allow the user to select between simultaneous broadcast/multicast services e.g. while receiving commercial broadcast service a new multicast service may interrupt this.
+
+While receiving PS or CS services, it shall be possible for the user to receive notification of MBMS multicast sessions.
+
+Note: This may depend on the capability of the UE in some access system.
+
+While receiving one or more multicast services it shall be possible for the user to be informed about incoming voice calls or the availability of other MBMS services.
+
+Dependent on terminal capabilities, it shall be possible for the user to participate in other services, while simultaneously participating in MBMS services. For example the user can originate or receive a call or send and receive messages whilst receiving MBMS video content.
+
+- Multicast subscription groups and multicast groups
+
+The subscriber shall be able to subscribe to or unsubscribe from a multicast subscription group. (The subscription mechanism is outside the scope of this TS.)
+
+The user shall be able to join a multicast group only if he is a member of the applicable multicast subscription group. The user shall be able to leave a multicast group if he is a member of that group.
+
+## 5.3 Availability
+
+If provided by the network MBMS in broadcast mode shall be available to all users in the broadcast service areas that are registered/attached to a PLMN.
+
+If provided by the network, MBMS in multicast mode shall be available to all users that are registered/attached to a PLMN.
+
+MBMS services (multicast or broadcast mode) shall be available via GERAN, UTRAN, E-UTRAN.
+
+It is possible to prevent access to the content of the MBMS multicast / broadcast data by UEs that do not register to the PLMNs that deliver the MBMS service (including case when these PLMNs and the RPLMN of the UE are part of the same network sharing infrastructure). Access prevention could be done by application layer means (e.g. application layer ciphering).
+
+Within the broadcast or multicast service area, it shall be possible to inform users of up-coming MBMS sessions which they may receive. This may be useful e.g. to initiate UE processes for the reception of MBMS data.
+
+In case of roaming a user should also be able to subscribe and join Multicast Services that are provided in the home network and visited network, as allowed by the user's home environment.
+
+# --- 6 Security
+
+It shall be possible to ensure that only those users who are entitled to receive a specific MBMS service may do so. It should be possible to choose whether a given MBMS service is to be delivered with or without ensured group security.
+
+If a terminal supports MBMS, then it shall support UICC based key management and all the function and interfaces required for it. In addition, ME key management shall be supported. If the UICC is capable of MBMS key management, ME key management shall not be activated.
+
+# --- 7 Charging
+
+## 7.1 Broadcast mode
+
+It shall be possible to collect charging information for the transmission of broadcast services to enable billing of broadcast services providers e.g. billing 3rd parties for advertising.
+
+Examples of the type of the charging information that could be collected include:
+
+- usage duration
+- volume of contents
+
+The above list of possible charging mechanisms is neither complete nor exhaustive.
+
+It shall be possible to collect subscriber charging information for the end user (including roaming situations) based on security procedures (e.g. key management) for the receipt of broadcast data on a per broadcast service basis.
+
+## 7.2 Multicast mode
+
+It shall be possible to collect charging information for the transmission of multicast services to enable billing of multicast services providers e.g. billing 3rd parties for advertising.
+
+It shall be possible to collect subscriber charging information (including roaming) for the use of the multicast mode (e.g. to enable billing to multicast services providers), as well as for the receipt of multicast data (e.g. users), on a per multicast service basis. On-line charging for multicast services should be possible as well.
+
+Examples of the type of the charging information that could be collected include:
+
+- multicast session duration
+- time when joining and leaving a multicast subscription group, duration of membership to a multicast subscription group
+- time when joining and leaving a multicast group, duration of membership to a multicast group
+- multicast session volume of contents
+
+The above list of possible charging mechanisms is neither complete nor exhaustive.
+
+Billing issues are out of scope of this TS.
+
+# --- Annex A (informative): MBMS Bit Rates
+
+Application bit rates for user services provided over MBMS are detailed within the stage 1 specification for 3GPP TS 22.246 "MBMS User Services" [7].
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|-----------------------------------------------------------------------------------|-------|-------|---------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| | SA1#13 | | 22.146 | | | | | Creation of TS | | 0.1.0 | MBMS |
+| | SA1#13 | | 22.146 | | | | | Output version from SA1 #13 | 0.1.0 | 1.0.0 | MBMS |
+| | SA1 #13 | | 22.146 | | | | | Raised to version 2.0.0 for approval at SA #13 | 1.0.0 | 2.0.0 | MBMS |
+| SP-13 | SP-010443 | S1-010858 | 22.146 | | | | | Approved at SA #13 | 2.0.0 | 5.0.0 | MBMS |
+| SP-14 | SP-010678 | 1077 | 22.146 | 002 | 2 | Rel-5 | F | Proposed CR on changes to definitions in 22.146 | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1305 | 22.146 | 003 | 3 | Rel-5 | B | Proposed CR on clarification of reliable transmission | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1075 | 22.146 | 005 | 1 | Rel-5 | F | Proposed CR on clarifications of the availability of MBMS | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1303 | 22.146 | 006 | 2 | Rel-5 | F | Proposed CR on Clarification on MBMS applicability in Gb mode | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1306 | 22.146 | 009 | 2 | Rel-5 | F | Proposed CR on data loss during handover | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1076 | 22.146 | 011 | 1 | Rel-5 | C | Proposed CR on optional privacy assurance for Multicast services | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1304 | 22.146 | 018 | 2 | Rel-5 | F | Proposed CR to 22.146: High level Diagrams of MBMS | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1065 | 22.146 | 019 | | Rel-5 | F | CR Clarifying Service Requirements on Multicast and Broadcast Areas | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1326 | 22.146 | 020 | 2 | Rel-5 | F | Proposed CR to 22.146 MBMS | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1225 | 22.146 | 021 | | Rel-5 | B | Multiple Areas for Multicast and Broadcast Services | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1309 | 22.146 | 022 | 1 | Rel-5 | F | MBMS service discovery | 5.0.0 | 5.1.0 | MBMS |
+| SP-14 | SP-010678 | 1020 | 22.146 | 023 | | Rel-5 | F | CR to 22.146 (MBMS) UE and MS definition | 5.0.0 | 5.1.0 | MBMS |
+| SP-15 | SP-020057 | S1-020125 | 22.146 | 024 | | Rel-5 | F | CR 22.146 Rel. 5 F Area Specific QoS for Broadcast and Multicast Services | 5.1.0 | 5.2.0 | MBMS |
+| SP-15 | SP-020057 | S1-020128 | 22.146 | 025 | | Rel-5 | F | CR 22.146 Rel. 5 F Clause 4.2 Multicast mode | 5.1.0 | 5.2.0 | MBMS |
+| SP-15 | SP-020057 | S1-020133 | 22.146 | 026 | | Rel-5 | F | CR 22.146 Rel. 5 F Addition of MBMS multicast mode and broadcast mode definitions | 5.1.0 | 5.2.0 | MBMS |
+| SP-15 | SP-020057 | S1-020563 | 22.146 | 027 | | Rel-5 | B | Proposed CR on MBMS Broadcast and Multicast Sessions | 5.1.0 | 5.2.0 | MBMS |
+| SP-15 | SP-020057 | S1-020565 | 22.146 | 028 | | Rel-5 | B | Power consumption minimisation for MBMS | 5.1.0 | 5.2.0 | MBMS |
+| SP-15 | SP-020057 | S1-020646 | 22.146 | 029 | | Rel-5 | F | CR to 22.146 (MBMS stage 1) 'Editorial Change' | 5.1.0 | 5.2.0 | MBMS |
+| SP-15 | SP-020045 | S1-020457 | 22.146 | 030 | - | Rel-5 | F | Editorial CR to correct terms and references | 5.1.0 | 5.2.0 | CORRECT |
+| SP-16 | SP-020257 | S1-020892 | 22.146 | 031 | | Rel-6 | C | Proposed CR on Multicast Joining Outside the Multicast Area | 5.2.0 | 6.0.0 | MBMS |
+| SP-16 | SP-020257 | S1-021180 | 22.146 | 032 | | Rel-6 | F | CR to 22.146: Clarification of requirement related to paging messages | 5.2.0 | 6.0.0 | MBMS |
+| SP-17 | SP-020561 | S1-021473 | 22.146 | 033 | | Rel-6 | B | Support of simultaneous services in MBMS | 6.0.0 | 6.1.0 | MBMS |
+| SP-17 | SP-020561 | S1-021472 | 22.146 | 034 | | Rel-6 | F | Proposal for Amalgamation of 1279, 1334, 1291 | 6.0.0 | 6.1.0 | MBMS |
+| SP-17 | SP-020561 | S1-021471 | 22.146 | 035 | | Rel-6 | B | Proposed CR to 22.146: addition of QoS information | 6.0.0 | 6.1.0 | MBMS |
+| SP-17 | SP-020561 | S1-021469 | 22.146 | 036 | | Rel-6 | F | MBMS Editorial CR | 6.0.0 | 6.1.0 | MBMS |
+
+| | | | | | | | | | | | |
+|---------|-----------|-----------|--------|------|---|--------|---|---------------------------------------------------------------------------------------------------------------------------------------|--------|--------|----------|
+| SP-17 | SP-020561 | S1-021483 | 22.146 | 037 | | Rel-6 | F | Proposed CR 22.146 on MBMS Availability | 6.0.0 | 6.1.0 | MBMS |
+| SP-17 | SP-020561 | S1-021481 | 22.146 | 038 | | Rel-6 | C | Proposed CR to 22.146: Multicast service discovery | 6.0.0 | 6.1.0 | MBMS |
+| SP-17 | SP-020561 | S1-021475 | 22.146 | 039 | | Rel-6 | B | CR to 22.146 on MBMS Charging | 6.0.0 | 6.1.0 | MBMS |
+| SP-19 | SP-030026 | S1-030154 | 22.146 | 040 | - | Rel-6 | C | CR to 22.146 - MBMS Cell broadcast in shared network | 6.1.0 | 6.2.0 | MBMS |
+| SP-22 | SP-030705 | S1-031010 | 22.146 | 041 | - | Rel-6 | F | Alignment of MBMS use cases and bit rates | 6.2.0 | 6.3.0 | MBMS |
+| SP-23 | SP-040094 | S1-040225 | 22.146 | 042 | - | Rel-6 | F | Clarification on user requirements for notification of multicast sessions | 6.3.0 | 6.4.0 | MBMS |
+| SP-24 | SP-040291 | S1-040518 | 22.146 | 043 | - | Rel-6 | F | Addition of a concept regarding UE joining time | 6.4.0 | 6.5.0 | MBMS |
+| SP-25 | SP-040504 | S1-040706 | 22.146 | 044 | - | Rel-6 | F | Rel-6 removal of notification requirement while receiving PS or CS services | 6.5.0 | 6.6.0 | MBMS |
+| SP-25 | SP-040696 | - | 22.146 | 045 | 1 | Rel-6 | F | Key management priority for MBMS services | 6.5.0 | 6.6.0 | MBMS |
+| SP-30 | SP-050742 | S1-051233 | 22.146 | 0046 | - | Rel-7 | B | Enabling IMS to use the MBMS bearer service | 6.6.0 | 7.0.0 | MBMSE |
+| SP-31 | SP-060019 | S1-060305 | 22.146 | 0048 | - | Rel-7 | A | Alignment of 22.146 with MBMS stage 3 | 7.0.0 | 7.1.0 | MBMS |
+| SP-32 | SP-060309 | S1-060610 | 22.146 | 0049 | - | Rel-8 | B | Extends MBMS bearers to all 3GPP systems | 7.1.0 | 8.0.0 | MBMSE |
+| SP-33 | SP-060465 | S1-060934 | 22.146 | 0051 | - | Rel-8 | A | Relaxing the current requirement that suggests a mandatory support for MBMS | 8.0.0 | 8.1.0 | MBMSE |
+| SP-35 | SP-070116 | S1-070288 | 22.146 | 0052 | - | Rel-8 | B | Requirement of MBMS Service Subscription for Roaming Users | 8.1.0 | 8.2.0 | MBMSE |
+| SP-36 | SP-070360 | S1-070788 | 22.146 | 0055 | 3 | Rel-8 | F | Explicitly define the function | 8.2.0 | 8.3.0 | MBMS |
+| SP-36 | SP-070361 | S1-070644 | 22.146 | 0056 | - | Rel-8 | F | Broadcast service priority | 8.2.0 | 8.3.0 | MBMS |
+| SP-40 | SP-080306 | S1-080722 | 22.146 | 0058 | 1 | Rel-9 | F | Addition of the support of eMBMS in Rel-9 | 8.3.0 | 9.0.0 | AIPN-SAE |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| SP-54 | SP-110810 | S1-113183 | 22.146 | 0061 | 1 | Rel-10 | F | MBMS reception | 10.0.0 | 10.1.0 | TEI10 |
+| SP-59 | - | - | - | - | - | - | - | Updated to Rel-11 version by MCC. Since an unofficial v.11.0.0 had circulated, the first Rel-11 official version is numbered v.11.1.0 | 10.1.0 | 11.1.0 | |
+| 2014-10 | - | - | - | - | - | - | - | Update to Rel-12 version (MCC) | 11.1.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2019-07 | - | - | - | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22153/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22153/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..68d446a4c1bf888f009193ce5b6d1934fb336292
--- /dev/null
+++ b/marked/Rel-18/22_series/22153/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9d58db16a53f9137b4f82b8e62e5b0bd44d43c39f95fb1d62f48713af8cba03
+size 9316
diff --git a/marked/Rel-18/22_series/22153/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22153/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d107e5ab554572172d9c1fe82c7e805eac754206
--- /dev/null
+++ b/marked/Rel-18/22_series/22153/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2737ce6737c2d983c8a528d43f16428340a5bd69c59a81f687d1da5b0d2ac8f
+size 7268
diff --git a/marked/Rel-18/22_series/22153/raw.md b/marked/Rel-18/22_series/22153/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..dff32d107ac781808b25d4d9f2085d22e7b3097e
--- /dev/null
+++ b/marked/Rel-18/22_series/22153/raw.md
@@ -0,0 +1,1040 @@
+
+
+# 3GPP TS 22.153 V18.2.0 (2023-06) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia priority service (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller capital letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, GSM, LTE, multimedia
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|----------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 General description ..... | 7 |
+| 5 High level requirements ..... | 8 |
+| 5.1 General ..... | 8 |
+| 5.2 Priority session treatment in originating network ..... | 9 |
+| 5.3 Priority session progression ..... | 9 |
+| 5.4 Priority session treatment in terminating network ..... | 9 |
+| 5.4a Priority Data Bearer Service ..... | 9 |
+| 5.5 Priority levels ..... | 10 |
+| 5.6 Invocation on demand ..... | 10 |
+| 5.7 Multimedia priority service code/identifier..... | 10 |
+| 5.8 Roaming ..... | 10 |
+| 5.8.1 Roaming within the home country ..... | 11 |
+| 5.8.2 Roaming outside the home country ..... | 11 |
+| 5.9 Handover ..... | 11 |
+| 5.10 Interworking with CS domain ..... | 11 |
+| 5.10.1 Mobile origination in the CS domain -> MPS mobile termination ..... | 11 |
+| 5.10.2 MPS mobile origination -> mobile termination to the CS domain ..... | 11 |
+| 5.10.3 CS Fallback from LTE ..... | 11 |
+| 5.10a Fallback in 5GS..... | 12 |
+| 5.11 Network Management Functions ..... | 12 |
+| 5.12 Policy Control ..... | 12 |
+| 5.13 Priority before service invocation ..... | 12 |
+| 5.13.1 Overview of priority before service invocation..... | 12 |
+| 5.13.2 Requirement for priority before service invocation ..... | 13 |
+| 5.14 Recovery/Restoration ..... | 13 |
+| 5.15 Quality of Service (QoS)..... | 13 |
+| 5.16 Inter-network aspects ..... | 13 |
+| 5.17 Interactions with supplementary services ..... | 13 |
+| 6 MMI aspects..... | 14 |
+| 7 Security and privacy..... | 14 |
+| 7.1 General ..... | 14 |
+| 7.2 Access Control ..... | 14 |
+| 7.3 Integrity ..... | 14 |
+| 7.4 Confidentiality/Privacy ..... | 14 |
+| 7.5 Use of Encryption..... | 15 |
+| 7.6 Attestation of Authorized MPS Priority..... | 15 |
+| 8 Charging aspects ..... | 15 |
+| 9 Service specific aspects..... | 15 |
+| 9.1 MPS for MMTEL voice ..... | 15 |
+| 9.1.1 General ..... | 15 |
+| 9.1.2 Invocation and revocation ..... | 16 |
+| 9.1.2.1 Invocation ..... | 16 |
+| 9.1.2.2 Revocation ..... | 17 |
+| 9.1.3 Authentication and authorization ..... | 17 |
+
+| | | |
+|-------------------------------|----------------------------------------------|-----------|
+| 9.1.4 | Signalling..... | 17 |
+| 9.1.5 | Media..... | 18 |
+| 9.2 | MPS for MMTEL video..... | 18 |
+| 9.2.1 | General ..... | 18 |
+| 9.2.2 | Invocation and revocation ..... | 18 |
+| 9.2.2.1 | Invocation ..... | 18 |
+| 9.2.2.2 | Revocation ..... | 19 |
+| 9.2.3 | Authentication and authorization ..... | 20 |
+| 9.2.4 | Signalling..... | 20 |
+| 9.2.5 | Media..... | 20 |
+| 9.3 | MPS for DTS..... | 21 |
+| 9.3.1 | General ..... | 21 |
+| 9.3.2 | Invocation and revocation ..... | 22 |
+| 9.3.2.1 | Invocation ..... | 22 |
+| 9.3.2.2 | Revocation ..... | 23 |
+| 9.3.3 | Authentication and authorization ..... | 23 |
+| 9.3.4 | Signalling..... | 24 |
+| 9.3.5 | Media..... | 24 |
+| 9.3.6 | QoS ..... | 24 |
+| 9.3.7 | Security ..... | 24 |
+| 10 | Non-3GPP access..... | 25 |
+| 10.1 | MPS when access to the EPC/5GC is WLAN ..... | 25 |
+| 10.1.1 | MPS for MMTEL voice and video..... | 25 |
+| 10.1.1.1 | General..... | 25 |
+| 10.1.1.2 | Authentication and authorization..... | 25 |
+| 10.1.1.3 | WLAN Interworking..... | 25 |
+| 10.1.2 | MPS for DTS..... | 25 |
+| 10.1.2.1 | General..... | 25 |
+| 10.1.2.2 | Authentication and authorization ..... | 26 |
+| 10.1.2.3 | WLAN interworking..... | 26 |
+| 10.1.3 | Void ..... | 26 |
+| Annex A (informative): | Change history..... | 27 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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].
+
+| | |
+|--------------|--------------------------------|
+| DTS | Data Transport Service |
+| MMTEL | Multimedia Telephony |
+| MPS | Multimedia Priority Service |
+| OTT | Over-The-Top |
+| PIN | Personal Identification Number |
+| VPN | Virtual Private Network |
+| NSWO | Non-Seamless WLAN Offload |
+
+# --- 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, and Data communication session 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, 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 Voice, Video and Data sessions 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, and Data).
+
+**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 Users 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, and data 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 and video 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: In this case of an UE with an MPS subscription, subscription related information stored in the UE is used, e.g., 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).
+
+- An authorized Service User using a UE that does not have an MPS subscription, and
+
+NOTE 2: In this case, the Service User is not identified by the subscription related information stored in the UE (e.g., the Service User borrows a UE that does not have an MPS subscription). In this case, radio interface priority may not be provided for the initial request for invocation of MPS. It is provided only after MPS is established for the MPS Voice, Video or Data session.
+
+- An authorized IoT device with an MPS subscription.
+
+NOTE 3: In this case of an IoT device with an MPS subscription, subscription related information stored in the IoT device is used to allow invocation/revocation of MPS through machine interactions that may not directly involve a human MPS Service User.
+
+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, and data) 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, and data) 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 subscription related information stored in the UE is 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 and Data) 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 or data) 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 and Data.
+
+The 3GPP network shall allow enforcement of QoS rule(s) for MPS Voice, Video and Data.
+
+The system shall support means to retain MPS invoked on Voice, Video and Data sessions 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, or data 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 Voice, Video or Data session 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.
+
+# --- 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, and data.
+
+## 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: In this case of an UE with an MPS subscription, subscription related information stored in the UE is used, e.g., 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).
+
+- 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 is not identified by the subscription information stored in the UE (e.g., the Service User borrows a UE that does not have an MPS subscription). In this case, radio interface priority is not provided for the initial request for invocation of MPS. It is provided only after MPS is established for the MMTEL voice call.
+
+- 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 on 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: In the case of an UE with an MPS subscription, subscription related information stored in the UE is used, e.g., 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).
+
+- 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 is not identified by the subscription information stored in the UE (e.g., the Service User borrows a UE that does not have an MPS subscription). In this case, radio interface priority is not provided for the initial request for invocation of MPS. It is provided only after MPS is established for the MPS for MMTEL video session.
+
+- 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 on 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 predetermined 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: In this case of an UE with an MPS subscription, subscription related information stored in the UE is used, e.g., 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).
+
+- 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 is not identified by the subscription related information stored in the UE (e.g., the Service User borrows a UE that does not have an MPS subscription). In this case, radio interface priority is not provided for the initial request for invocation of MPS. It is provided only after MPS is established for the DTS session.
+
+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 authorize 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.
+
+# 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
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|-------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-37 | SP-070576 | - | 22.146 | - | - | Rel-8 | - | Raised to v.2.0.0 by MCC for approval as v.8.0.0 | 1.3.0 | 2.0.0 | PRIOR |
+| SP-37 | - | - | 22.146 | - | - | Rel-8 | - | Raised to v.8.0.0 by MCC following SA#37 approval | 2.0.0 | 8.0.0 | PRIOR |
+| SP-40 | SP-080305 | S1-080438 | 22.153 | 0004 | - | Rel-8 | D | CR to TS 22.153 on applicability of MPS | 8.0.0 | 8.1.0 | PRIOR |
+| SP-40 | SP-080310 | S1-080727 | 22.153 | 0003 | 1 | Rel-9 | B | CR to TS 22.153 on an optional service invocation method for MPS | 8.0.0 | 9.0.0 | ePRIOR |
+| SP-41 | SP-080494 | - | 22.153 | 0006 | 1 | Rel-9 | A | Trusted domain support | 9.0.0 | 9.1.0 | PRIOR |
+| SP-42 | SP-080778 | S1-084394 | 22.153 | 0007 | 3 | Rel-9 | F | Correction to priority levels and networks | 9.1.0 | 9.2.0 | EPRIOR |
+| SP-42 | SP-080778 | S1-084365 | 22.153 | 0008 | 1 | Rel-9 | C | Indication of MPS | 9.1.0 | 9.2.0 | EPRIOR |
+| SP-47 | SP-100188 | S1-100101 | 22.153 | 0011 | - | Rel-10 | F | Clarification of MPS Service Aspects - Video and Data Bearer service | 9.2.0 | 10.0.0 | TEI10 |
+| SP-47 | SP-100188 | S1-100458 | 22.153 | 0012 | 3 | Rel-10 | B | Priority for data bearer services | 9.2.0 | 10.0.0 | TEI10 |
+| SP-49 | SP-100580 | S1-102180 | 22.153 | 0013 | - | Rel-10 | B | Priority for data bearer services | 10.0.0 | 10.1.0 | TEI10 |
+| SP-51 | SP-110172 | S1-110182 | 22.153 | 0014 | 2 | Rel-11 | F | Clarifying PS to CS handover requirements for multimedia priority calls | 10.1.0 | 11.0.0 | TEI11 |
+| SP-52 | SP-110376 | S1-111413 | 22.153 | 0016 | 1 | Rel-11 | B | Priority treatment for Network Management functions | 11.0.0 | 11.1.0 | TEI11 |
+| SP-52 | SP-110376 | S1-111414 | 22.153 | 0017 | 1 | Rel-11 | C | Clarification of Priority Information | 11.0.0 | 11.1.0 | TEI11 |
+| 2014-10 | - | - | - | - | - | - | - | Update to Rel-12 version (MCC) | 11.1.0 | 12.0.0 | |
+| 2015-06 | - | - | - | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | |
+| SP-68 | SP-150270 | S1-151607 | 22.153 | 0019 | 3 | Rel-14 | C | Additions to MPS description | 12.0.0 | 14.0.0 | MPS_Mod s |
+| SP-68 | SP-150270 | S1-151540 | 22.153 | 0020 | 2 | Rel-14 | C | MPS Policy Control | 12.0.0 | 14.0.0 | MPS_Mod s |
+| SP-68 | SP-150270 | S1-151542 | 22.153 | 0021 | 2 | Rel-14 | C | Priority in Advance of Service Invocation | 12.0.0 | 14.0.0 | MPS_Mod s |
+| SP-69 | SP-150537 | S1-152174 | 22.153 | 0022 | - | Rel-14 | F | MPS exemption from load rebalancing | 14.0.0 | 14.1.0 | MPS_Mod s |
+| SP-69 | SP-150537 | S1-152681 | 22.153 | 0024 | 3 | Rel-14 | F | MPS priority during initial Attach | 14.0.0 | 14.1.0 | MPS_Mod s |
+| SP-70 | SP-150751 | S1-154442 | 22.153 | 0025 | 1 | Rel-14 | F | Addition of end-to-end-cases in general description | 14.1.0 | 14.2.0 | MPS_Mod s |
+| SP-70 | SP-150751 | S1-154443 | 22.153 | 0026 | 1 | Rel-14 | F | Clarification of high level MPS requirements. | 14.1.0 | 14.2.0 | MPS_Mod s |
+| SP-70 | SP-150751 | S1-154444 | 22.153 | 0027 | 1 | Rel-14 | F | Fix inconsistent requirements on invocation of MPS priority. | 14.1.0 | 14.2.0 | MPS_Mod s |
+| SP-70 | SP-150751 | S1-154445 | 22.153 | 0028 | 1 | Rel-14 | B | MPS security requirements | 14.1.0 | 14.2.0 | MPS_Mod s |
+| SP-71 | SP-160097 | S1-160332 | 22.153 | 0029 | 1 | Rel-14 | F | Text alignment for terminating UE option | 14.2.0 | 14.3.0 | MPS_Mod s |
+| SP-71 | SP-160097 | S1-160333 | 22.153 | 0030 | 1 | Rel-14 | F | Update to Priority Data Bearer Service | 14.2.0 | 14.3.0 | MPS_Mod s |
+| SP-71 | SP-160097 | S1-160334 | 22.153 | 0031 | 1 | Rel-14 | B | MPS Anonymity Requirement | 14.2.0 | 14.3.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161096 | 22.153 | 0032 | | Rel-14 | D | Editorial Corrections | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161097 | 22.153 | 0033 | | Rel-14 | F | Update to Handover Materials | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161099 | 22.153 | 0035 | | Rel-14 | F | Update on Number of Priority Levels | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161102 | 22.153 | 0038 | | Rel-14 | F | Clarification of CS Domain Interworking | 14.3.0 | 14.4.0 | MPS_Mod s |
+
+| | | | | | | | | | | | |
+|---------|-----------|-----------|--------|------|---|--------|---|-----------------------------------------------------------------|--------|--------|-----------|
+| SP-72 | SP-160356 | S1-161442 | 22.153 | 0036 | 1 | Rel-14 | F | Alignment of requirement for priority before service invocation | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161443 | 22.153 | 0037 | 1 | Rel-14 | F | MPS priority for CS fallback | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161445 | 22.153 | 0040 | 1 | Rel-14 | F | Correction of MPS Roaming Requirement | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161558 | 22.153 | 0039 | 3 | Rel-14 | B | QoS for MPS | 14.3.0 | 14.4.0 | MPS_Mod s |
+| SP-72 | SP-160356 | S1-161559 | 22.153 | 0034 | 2 | Rel-14 | B | Service code for MPS | 14.3.0 | 14.4.0 | MPS_Mod s |
+| 2018-06 | - | - | - | - | - | Rel-15 | - | Raised to Rel-15 by MCC | 14.4.0 | 15.0.0 | - |
+| 2019-09 | - | - | - | - | - | Rel-16 | - | Created by MCC due to Rel-17 CR#0041 and 42 | 15.0.0 | 16.0.0 | - |
+
+| Change history | | | | | | | | | | | |
+|----------------|---------|-----------|------|------|-----|-------------------------------------------------------------------------------------------------------|--|--|--|--|-------------|
+| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | | | | | New version |
+| 2019-09 | SA#85 | SP-190867 | 0041 | 3 | B | Common MPS Voice, Video and Data updates based on TR 22.854, MPS Phase 2 Feasibility Study | | | | | 17.0.0 |
+| 2019-09 | SA#85 | SP-190806 | 0042 | 2 | B | MPS service specific updates based on TR 22.854, MPS Phase 2 Feasibility Study | | | | | 17.0.0 |
+| 2019-12 | SA#86 | SP-191018 | 0044 | 1 | D | Editorial clean-up to close out MPS Phase 2 additions | | | | | 17.1.0 |
+| 2019-12 | SA#86 | SP-191018 | 0045 | 3 | B | Attestation of Authorized MPS Priority Markings | | | | | 17.1.0 |
+| 2019-12 | SA#86 | SP-191018 | 0046 | 1 | B | Addition of requirements to upgrade an established MMTEL voice call to MPS | | | | | 17.1.0 |
+| 2019-12 | SA#86 | SP-191018 | 0043 | 3 | F | Clarifications on MPS2 requirements and terminology | | | | | 17.1.0 |
+| 2020-12 | SA#90e | SP-201027 | 47 | 0 | D | Editorial Cleanup of MPS Phase 2 Additions | | | | | 17.2.0 |
+| 2020-12 | SA#90e | SP-201027 | 48 | 1 | F | Alignment of descriptive text with associated requirement for MPS invocation from a non-subscribed UE | | | | | 17.2.0 |
+| 2021-09 | SA#93e | SP-211072 | 0049 | 1 | B | MPS when access to EPC/5GC is WLAN (MPS_WLAN) | | | | | 18.0.0 |
+| 2021-09 | SA#93e | SP-211039 | 0050 | 1 | B | Fallback in 5GS | | | | | 18.0.0 |
+| 2021-12 | SP-94 | SP-211492 | 0052 | 1 | D | Editorial correction of reference (Rel-18 Mirror) | | | | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211492 | 0054 | 1 | F | MPS for DTS description alignment (Rel-18 Mirror) | | | | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211501 | 0055 | 1 | B | MPS and Supplementary Services Interactions | | | | | 18.1.0 |
+| 2023-06 | SA#100 | SP-230531 | 0059 | | F | Correction to MPS requirements | | | | | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22173/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22173/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8f35ed4ad64a5771a78716a809b4481c0cc696a
--- /dev/null
+++ b/marked/Rel-18/22_series/22173/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d96a5e1d24270e40e89830d626000b3dc4d21ddb69cbde16575c14fe9d9631d7
+size 8182
diff --git a/marked/Rel-18/22_series/22173/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22173/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d107e5ab554572172d9c1fe82c7e805eac754206
--- /dev/null
+++ b/marked/Rel-18/22_series/22173/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2737ce6737c2d983c8a528d43f16428340a5bd69c59a81f687d1da5b0d2ac8f
+size 7268
diff --git a/marked/Rel-18/22_series/22173/raw.md b/marked/Rel-18/22_series/22173/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..89d34222221ec227fbc3b311d60a79b3ece725b8
--- /dev/null
+++ b/marked/Rel-18/22_series/22173/raw.md
@@ -0,0 +1,3064 @@
+
+
+# 3GPP TS 22.173 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font, with a red signal wave icon below the 'G' and a 'TM' symbol to the right.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, LTE, telephony, multimedia, IP,
+supplementary service
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-----------------------------------------------------------------------------------|----|
+| Foreword ..... | 9 |
+| 1 Scope..... | 10 |
+| 2 References..... | 10 |
+| 3 Definitions, symbols and abbreviations..... | 11 |
+| 3.1 Definitions..... | 11 |
+| 3.2 Symbols..... | 11 |
+| 3.3 Abbreviations ..... | 11 |
+| 4 Service description..... | 12 |
+| 4.1 General Service characteristics ..... | 12 |
+| 4.2 Default media handling capabilities of IMS Multimedia Telephony service ..... | 12 |
+| 4.3 Association of Services to Time/Date..... | 13 |
+| 4.4 Additional timing information ..... | 13 |
+| 4.5 Allow / block list..... | 13 |
+| 4.6 Multi-device and Multi-Identity..... | 13 |
+| 4.6.1 General ..... | 13 |
+| 4.6.2 User Configuration ..... | 14 |
+| 4.7 Caller Identity Verification Results Delivery to the User..... | 14 |
+| 5 Service Requirements ..... | 14 |
+| 6 Quality of Service ..... | 14 |
+| 7 Interworking requirements..... | 14 |
+| 7.1 Interworking with CS domain..... | 14 |
+| 7.2 Interworking with external networks ..... | 15 |
+| 7.3 Media Aspects on Interworking ..... | 15 |
+| 8 Supplementary Services..... | 15 |
+| 8.1 General ..... | 15 |
+| 8.2 Supplementary Services applicable to IMS Multimedia Telephony..... | 15 |
+| 8.2.1 Originating Identification Presentation (OIP) ..... | 15 |
+| 8.2.1.1 Definition ..... | 15 |
+| 8.2.1.2 Service interactions with other IMS supplementary services..... | 16 |
+| 8.2.1.2.1 Identification services ..... | 16 |
+| 8.2.1.2.2 Diversion services..... | 16 |
+| 8.2.1.2.3 Communication Waiting (CW)..... | 17 |
+| 8.2.1.3 Interoperability with PSTN/ISDN and mobileCS Networks..... | 17 |
+| 8.2.2 Originating Identification Restriction (OIR)..... | 17 |
+| 8.2.2.1 Definition ..... | 17 |
+| 8.2.2.2 Service interactions with other IMS supplementary services..... | 17 |
+| 8.2.2.2.1 Identification services ..... | 17 |
+| 8.2.2.2.2 Diversion services..... | 17 |
+| 8.2.2.2.3 Explicit Communication Transfer (ECT)..... | 18 |
+| 8.2.2.3 Interoperability with PSTN/ISDN and mobile CS Networks..... | 18 |
+| 8.2.3 Terminating Identification Presentation (TIP) ..... | 18 |
+| 8.2.3.1 Definition ..... | 18 |
+| 8.2.3.2 Service interactions with other IMS supplementary services..... | 18 |
+| 8.2.3.2.1 Identification services ..... | 18 |
+| 8.2.3.2.2 Diversion services..... | 18 |
+| 8.2.3.3 Interoperability with PSTN/ISDN and mobile CS Networks..... | 19 |
+| 8.2.4 Terminating Identification Restriction (TIR)..... | 19 |
+| 8.2.4.1 Definition ..... | 19 |
+| 8.2.4.2 Service interactions with other IMS Multimedia Telephony services..... | 19 |
+| 8.2.4.2.1 Identification services ..... | 19 |
+| 8.2.4.3 Interoperability with PSTN/ISDN and mobile CS Networks..... | 19 |
+| 8.2.5 Malicious Communication IDentification (MCID)..... | 19 |
+
+| | | |
+|------------|------------------------------------------------------------------|----|
+| 8.2.5.1 | Definition ..... | 19 |
+| 8.2.5.2 | Service interactions with other IMS supplementary services ..... | 20 |
+| 8.2.5.2.1 | Diversion Services..... | 20 |
+| 8.2.5.2.2 | Explicit Communication Transfer (ECT)..... | 20 |
+| 8.2.5.2.3 | CONference (CONF) ..... | 20 |
+| 8.2.5.2.4 | Three-Party (3PTY)..... | 20 |
+| 8.2.5.3 | Interoperability with PSTN/ISDN Networks ..... | 20 |
+| 8.2.6 | Anonymous Communication Rejection (ACR)..... | 20 |
+| 8.2.6.1 | Definition ..... | 20 |
+| 8.2.6.2 | Service interactions with other IMS supplementary services ..... | 21 |
+| 8.2.6.2.1 | Identification Services..... | 21 |
+| 8.2.6.2.2 | Diversion Services..... | 21 |
+| 8.2.6.2.3 | Communication Waiting (CW) ..... | 22 |
+| 8.2.6.2.4 | Completion of Communications to Busy Subscriber (CCBS) ..... | 22 |
+| 8.2.6.3 | Interoperability with PSTN/ISDN ..... | 22 |
+| 8.2.7 | Communication DIVersion (CDIV) ..... | 22 |
+| 8.2.7.1 | Definition ..... | 22 |
+| 8.2.7.2 | (void)..... | 25 |
+| 8.2.7.3 | Service interactions with other IMS supplementary services ..... | 25 |
+| 8.2.7.3.1 | Identification services ..... | 25 |
+| 8.2.7.3.2 | Malicious Communication IDentification (MCID)..... | 25 |
+| 8.2.7.3.3 | Anonymous Communication Rejection (ACR) ..... | 25 |
+| 8.2.7.3.4 | Diversion services ..... | 25 |
+| 8.2.7.3.5 | Communication Waiting (CW) ..... | 28 |
+| 8.2.7.3.6 | Communication Barring (CB)..... | 28 |
+| 8.2.7.3.7 | Completion of Communications to Busy Subscriber (CCBS) ..... | 29 |
+| 8.2.7.3.8 | Advice Of Charge (AOC) ..... | 29 |
+| 8.2.7.4 | Interoperability with PSTN/ISDN and CS mobile networks ..... | 29 |
+| 8.2.8 | Communication Waiting (CW) ..... | 29 |
+| 8.2.8.1 | Definition ..... | 29 |
+| 8.2.8.2 | Service interactions with other IMS supplementary services ..... | 29 |
+| 8.2.8.2.1 | Anonymous Communication Rejection (ACR) ..... | 29 |
+| 8.2.8.2.1a | Enhanced Calling Name (eCNAM) ..... | 30 |
+| 8.2.8.2.2 | Diversion services ..... | 30 |
+| 8.2.8.2.3 | Completion of Communications to Busy Subscriber (CCBS) ..... | 30 |
+| 8.2.8.3 | Interoperability with PSTN/ISDN ..... | 30 |
+| 8.2.9 | Communication HOLD (HOLD) ..... | 30 |
+| 8.2.9.1 | Definition ..... | 30 |
+| 8.2.9.2 | Service interactions with other IMS supplementary services ..... | 30 |
+| 8.2.9.2.1 | CONference (CONF) ..... | 30 |
+| 8.2.9.2.2 | Three-Party (3PTY)..... | 30 |
+| 8.2.9.3 | Interoperability with PSTN/ISDN and CS mobile networks ..... | 30 |
+| 8.2.10 | Communication Barring (CB) ..... | 31 |
+| 8.2.10.1 | Definition ..... | 31 |
+| 8.2.10.2 | Service interactions with other IMS supplementary services ..... | 32 |
+| 8.2.10.2.1 | Diversion services ..... | 32 |
+| 8.2.10.3 | Interoperability with PSTN/ISDN and CS mobile networks ..... | 33 |
+| 8.2.11 | Completion of Communications to Busy Subscriber (CCBS) ..... | 33 |
+| 8.2.11.1 | Definition ..... | 33 |
+| 8.2.11.2 | Service interactions with other IMS supplementary services ..... | 34 |
+| 8.2.11.2.1 | Identification services ..... | 34 |
+| 8.2.11.2.2 | Anonymous Communication Rejection (ACR) ..... | 34 |
+| 8.2.11.2.3 | Communication DIVersion (CDIV)..... | 34 |
+| 8.2.11.2.4 | Communication Waiting (CW) ..... | 34 |
+| 8.2.11.2.5 | Communication HOLD (HOLD) ..... | 34 |
+| 8.2.11.2.6 | Communication Barring (CB)..... | 34 |
+| 8.2.11.2.7 | Completion of Communications to Busy Subscriber (CCBS) ..... | 34 |
+| 8.2.11.2.8 | Advice Of Charge services (AOC)..... | 35 |
+| 8.2.11.2.9 | Enhanced Calling Name (eCNAM) ..... | 35 |
+| 8.2.11.3 | Interoperability with PSTN/ISDN ..... | 35 |
+| 8.2.12 | Message Waiting Indication (MWI)..... | 35 |
+| 8.2.12.1 | Definition ..... | 35 |
+
+| | | |
+|--------------|-------------------------------------------------------------------|----|
+| 8.2.12.2 | Service interactions with other services..... | 35 |
+| 8.2.12.2.1 | Diversion services ..... | 35 |
+| 8.2.12.3 | Interoperability with PSTN/ISDN and CS mobile networks ..... | 36 |
+| 8.2.13 | CONference (CONF)..... | 36 |
+| 8.2.13.1 | Definition ..... | 36 |
+| 8.2.13.2 | Service interactions with other IMS supplementary services ..... | 36 |
+| 8.2.13.2.1 | Diversion services ..... | 36 |
+| 8.2.13.2.2 | CONference (CONF) ..... | 36 |
+| 8.2.13.2.3 | Advice Of Charge services (AOC)..... | 36 |
+| 8.2.13.2.4 | Originating Identification Restriction (OIR)..... | 36 |
+| 8.2.13.2.5 | Terminating Identification Restriction (TIR)..... | 36 |
+| 8.2.13.2.6 | Three-Party (3PTY)..... | 37 |
+| 8.2.13.3 | Interoperability with PSTN/ISDN and CS Mobile networks ..... | 37 |
+| 8.2.14 | Advice Of Charge (AOC)..... | 37 |
+| 8.2.14.1 | Definition ..... | 37 |
+| 8.2.14.2 | Service interactions with other IMS supplementary services ..... | 37 |
+| 8.2.14.2.1 | Diversion services ..... | 37 |
+| 8.2.14.2.2 | Completion of Communications to Busy Subscriber (CCBS) ..... | 37 |
+| 8.2.14.2.3 | CONference (CONF) ..... | 37 |
+| 8.2.14.3 | Interoperability with PSTN/ISDN ..... | 38 |
+| 8.2.15 | Explicit Communication Transfer (ECT)..... | 38 |
+| 8.2.15.1 | Definition ..... | 38 |
+| 8.2.15.2 | Service interactions with other IMS supplementary services ..... | 38 |
+| 8.2.15.2.1 | Identification services ..... | 38 |
+| 8.2.15.2.1.2 | Originating Identification Presentation (OIP) ..... | 39 |
+| 8.2.15.2.2 | Communication Barring (CB)..... | 39 |
+| 8.2.15.2.3 | CONference (CONF) ..... | 39 |
+| 8.2.15.2.4 | Advice Of Charge (AOC) ..... | 39 |
+| 8.2.15.2.5 | Explicit Communication Transfer (ECT)..... | 40 |
+| 8.2.15.3 | Interoperability with PSTN/ISDN and CS mobile networks ..... | 40 |
+| 8.2.16 | Reverse charging ..... | 40 |
+| 8.2.16.1 | Definition ..... | 40 |
+| 8.2.16.2 | Service interactions with other IMS supplementary services ..... | 40 |
+| 8.2.16.3 | Interoperability with PSTN/ISDN ..... | 40 |
+| 8.2.17 | Closed User Group (CUG) ..... | 40 |
+| 8.2.17.1 | Definition ..... | 40 |
+| 8.2.17.2 | Service interactions with other IMS supplementary services ..... | 41 |
+| 8.2.17.2.1 | Diversion services ..... | 41 |
+| 8.2.17.2.1.1 | Communication Forwarding Unconditional (CFU) ..... | 41 |
+| 8.2.17.2.1.2 | Communication Forwarding Busy (CFB)..... | 41 |
+| 8.2.17.2.1.3 | Call Forwarding No Reply (CFNR)..... | 41 |
+| 8.2.17.2.1.4 | Communication Forwarding on Not Logged-in (CFNL)..... | 41 |
+| 8.2.17.2.1.5 | Communication Forwarding on Subscriber Not Reachable (CFNRc)..... | 41 |
+| 8.2.17.2.1.6 | Communication Deflection (CD)..... | 41 |
+| 8.2.17.2.2 | Explicit Communication Transfer (ECT)..... | 42 |
+| 8.2.17.2.3 | Three-Party (3PTY)..... | 42 |
+| 8.2.17.2.4 | CONference (CONF) ..... | 42 |
+| 8.2.17.3 | Interoperability with PSTN/ISDN ..... | 42 |
+| 8.2.18 | Three-Party (3PTY)..... | 42 |
+| 8.2.18.1 | Definition ..... | 42 |
+| 8.2.18.2 | Service interactions with other IMS supplementary services ..... | 42 |
+| 8.2.18.2.1 | Terminating Identification Presentation (OIR) ..... | 42 |
+| 8.2.18.2.2 | Terminating Identification Restriction (TIR)..... | 42 |
+| 8.2.18.2.3 | Three-Party (3PTY)..... | 43 |
+| 8.2.18.2.4 | CONference (CONF) ..... | 43 |
+| 8.2.18.3 | Interoperability with PSTN/ISDN ..... | 43 |
+| 8.2.19 | Flexible Alerting (FA) ..... | 43 |
+| 8.2.19.1 | Definition ..... | 43 |
+| 8.2.19.2 | Service interactions with other IMS supplementary services ..... | 43 |
+| 8.2.19.2.1 | Identification services ..... | 43 |
+| 8.2.19.2.2 | Diversion services ..... | 44 |
+| 8.2.20 | Personal Network Management (PNM) ..... | 44 |
+
+| | | |
+|--------------|------------------------------------------------------------------------------------------------------------|----|
+| 8.2.20.1 | Definition ..... | 44 |
+| 8.2.20.2 | Service interactions with other IMS supplementary services ..... | 44 |
+| 8.2.21 | Customized Alerting Tone (CAT)..... | 44 |
+| 8.2.21.1 | Definition ..... | 44 |
+| 8.2.21.2 | Service interactions with other IMS supplementary services ..... | 44 |
+| 8.2.21.2.1 | Identification services ..... | 44 |
+| 8.2.21.2.2 | Diversion services ..... | 45 |
+| 8.2.21.2.3 | Communication Waiting (CW)..... | 45 |
+| 8.2.21.2.4 | Explicit Communication Transfer (ECT)..... | 45 |
+| 8.2.22 | Customized Ringing Signal (CRS)..... | 45 |
+| 8.2.22.1 | Definition ..... | 45 |
+| 8.2.22.2 | Service interactions with other IMS supplementary services ..... | 45 |
+| 8.2.22.2.1 | Identification services ..... | 45 |
+| 8.2.22.2.2 | Diversion services ..... | 45 |
+| 8.2.22.2.3 | Communication Waiting (CW)..... | 46 |
+| 8.2.22.2.4 | Explicit Communication Transfer (ECT)..... | 46 |
+| 8.2.23 | Completion of Communications on No Reply (CCNR)..... | 46 |
+| 8.2.23.1 | Definition ..... | 46 |
+| 8.2.23.2 | Service interactions with other IMS supplementary services ..... | 46 |
+| 8.2.23.2.1 | Identification services ..... | 46 |
+| 8.2.23.2.1.1 | Originating Identification Presentation (OIP) ..... | 46 |
+| 8.2.23.2.1.2 | Originating Identification Restriction (OIR) ..... | 46 |
+| 8.2.23.2.1.3 | Terminating Identification Presentation (TIP) ..... | 47 |
+| 8.2.23.2.1.4 | Terminating Identification Restriction (TIR) ..... | 47 |
+| 8.2.23.2.2 | Advice Of Charge services (AOC)..... | 47 |
+| 8.2.23.2.3 | Communication Waiting (CW)..... | 47 |
+| 8.2.23.2.4 | Communication HOLD (HOLD) ..... | 47 |
+| 8.2.23.2.5 | Explicit Communication Transfer (ECT)..... | 47 |
+| 8.2.23.2.6 | Closed User Group (CUG)..... | 47 |
+| 8.2.23.2.7 | Completion of communications services ..... | 47 |
+| 8.2.23.2.7.1 | Completion of Communications to Busy Subscriber (CCBS) ..... | 47 |
+| 8.2.23.2.7.2 | Completion of Communications on No Reply (CCNR)..... | 48 |
+| 8.2.23.2.8 | CONFerence (CONF) ..... | 48 |
+| 8.2.23.2.9 | Communication DIVersion (CDIV)..... | 48 |
+| 8.2.23.2.9.1 | General ..... | 48 |
+| 8.2.23.2.9.2 | Communication Forwarding Unconditional (CFU) ..... | 48 |
+| 8.2.23.2.9.3 | Communication Forwarding Busy (CFB) ..... | 48 |
+| 8.2.23.2.9.4 | Communication Forwarding No Reply (CFNR) ..... | 49 |
+| 8.2.23.2.9.5 | Communication Forwarding on Not Logged in (CFNL) ..... | 49 |
+| 8.2.23.2.9.6 | Communication Deflection (CD) ..... | 49 |
+| 8.2.23.2.10 | Malicious Communication IDentification (MCID)..... | 49 |
+| 8.2.23.2.11 | Anonymous Communication Rejection and Communication Barring (ACR/CB) ..... | 49 |
+| 8.2.23.2.12 | Message Waiting Indication (MWI) ..... | 49 |
+| 8.2.23.2.13 | Flexible Alerting (FA)..... | 49 |
+| 8.2.23.2.14 | Customized Alerting Tones (CAT)..... | 50 |
+| 8.2.23.3 | Interoperability with PSTN/ISDN ..... | 50 |
+| 8.2.24 | Enhanced Calling Name (eCNAM)..... | 50 |
+| 8.2.24.1 | Definition and Scope ..... | 50 |
+| 8.2.24.2 | Service Requirements and Functionality ..... | 50 |
+| 8.2.24.3 | Service interactions with other IMS supplementary services ..... | 51 |
+| 8.2.24.3.1 | Identification Services..... | 51 |
+| 8.2.24.3.2 | Diversion Services..... | 52 |
+| 8.2.24.3.3 | Communication Waiting (CW)..... | 52 |
+| 8.2.24.3.4 | Completion of Communication to Busy Subscriber (CCBS)..... | 52 |
+| 8.2.24.3.5 | Explicit Communication Transfer (ECT)..... | 52 |
+| 8.2.24.4 | Interoperability with PSTN/ISDN and mobile CS services..... | 53 |
+| 8.2A | Supplementary Services applicable to IMS Multimedia Telephony without equivalent in non-IMS networks ..... | 53 |
+| 8.2A.1 | Completion of Communications on Not Logged-in (CCNL)..... | 53 |
+| 8.2A.1.1 | Definition ..... | 53 |
+| 8.2A.1.2 | Service interactions with other IMS supplementary services ..... | 53 |
+| 8.2A.1.2.1 | Identification services ..... | 53 |
+
+| | | |
+|--------------------------------|---------------------------------------------------------------------------------------------------|-----------|
+| 8.2A.1.2.1.1 | Originating Identification Presentation (OIP) ..... | 53 |
+| 8.2A.1.2.1.2 | Originating Identification Restriction (OIR) ..... | 53 |
+| 8.2A.1.2.1.3 | Terminating Identification Presentation (TIP) ..... | 54 |
+| 8.2A.1.2.1.4 | Terminating Identification Restriction (TIR) ..... | 54 |
+| 8.2A.1.2.2 | Advice Of Charge services (AOC)..... | 54 |
+| 8.2A.1.2.3 | Communication Waiting (CW) ..... | 54 |
+| 8.2A.1.2.4 | Communication HOLD (HOLD) ..... | 54 |
+| 8.2A.1.2.5 | Explicit Communication Transfer (ECT)..... | 54 |
+| 8.2A.1.2.6 | Closed User Group (CUG)..... | 54 |
+| 8.2A.1.2.7 | Completion of communications services (CC) ..... | 54 |
+| 8.2A.1.2.8 | CONFerence (CONF) ..... | 55 |
+| 8.2A.1.2.9 | Communication DIVersion (CDIV)..... | 55 |
+| 8.2A.1.2.9.1 | General ..... | 55 |
+| 8.2A.1.2.9.2 | Communication Forwarding Unconditional (CFU) ..... | 55 |
+| 8.2A.1.2.9.3 | Communication Forwarding Busy (CFB) ..... | 55 |
+| 8.2A.1.2.9.4 | Communication Forwarding No Reply (CFNR) ..... | 55 |
+| 8.2A.1.2.9.5 | Communication Forwarding on Not Logged in (CFNL) ..... | 56 |
+| 8.2A.1.2.9.6 | Communication Deflection (CD) ..... | 56 |
+| 8.2A.1.2.10 | Malicious Communication IDentification (MCID)..... | 56 |
+| 8.2A.1.2.11 | Anonymous Communication Rejection and Communication Barring (ACR/CB) ..... | 56 |
+| 8.2A.1.2.12 | Message Waiting Indication (MWI) ..... | 56 |
+| 8.2A.1.2.13 | Flexible Alerting (FA)..... | 56 |
+| 8.2A.1.2.14 | Customized Alerting Tones (CAT)..... | 56 |
+| 8.2A.1.3 | Interoperability with PSTN/ISDN ..... | 56 |
+| 8.3 | Concepts associated with IMS supplementary services..... | 57 |
+| 8.3.1 | Administration of supplementary services ..... | 57 |
+| 8.3.2 | Unstructured SS data operations ..... | 57 |
+| 8.3.3 | Network Announcement and Tones Insertion ..... | 57 |
+| 8.4 | Use of authorization option in relation to IMS supplementary services ..... | 57 |
+| 8.4.1 | Definition..... | 57 |
+| 8.4.2 | Description ..... | 57 |
+| 8.4.3 | Management - normal procedures and successful outcome ..... | 57 |
+| 8.4.3.1 | Provision of authorization..... | 57 |
+| 8.4.3.2 | Withdrawal of authorization ..... | 58 |
+| 8.4.3.3 | Authentication requirements..... | 58 |
+| 9 | IMS Multimedia Telephony with Enhanced Voice ..... | 59 |
+| Annex A (informative): | General terminal guidelines ..... | 60 |
+| A.1 | Service state indication ..... | 60 |
+| A.2 | Supervisory tones..... | 60 |
+| Annex B (informative): | Service interactions table..... | 61 |
+| Annex C (normative): | IMS Multimedia Telephony supplementary services applicable to the fixed access..... | 64 |
+| Annex D (normative): | IMS Multimedia Telephony supplementary services applicable to the mobile 3GPP access..... | 66 |
+| Annex Da (normative): | Network determined user busy. .... | 67 |
+| Annex Db (informative): | services classification applicable to Inter IMS Network-to-Network Interface (II-NNI)..... | 68 |
+| Db.1 | High Priority Category ..... | 68 |
+| Db.2 | Medium Priority Category ..... | 68 |
+| Db.3 | Low Priority Category..... | 69 |
+| Annex Dc (normative): | Enterprise IP-PBX Supplementary Services to support 3GPP Voice Interworking..... | 70 |
+| Dc.1 | General ..... | 70 |
+
+| | | |
+|-------------------------------|------------------------------------------------------------|-----------|
+| Dc.2 | Individual Line Services..... | 70 |
+| Dc.2.1 | Introduction ..... | 70 |
+| Dc.2.2 | Call Transfer (Unattended, Attended & Early Attended)..... | 70 |
+| Dc.2.3 | Multi-party Ad-hoc Conference with Rosters ..... | 70 |
+| Dc.2.4 | Call Forwarding..... | 71 |
+| Dc.2.5 | Single Number Reach (SNR) ..... | 71 |
+| Dc.2.6 | Do Not Disturb (DND)..... | 71 |
+| Dc.2.7 | Immediate Divert (to messaging system)..... | 72 |
+| Dc.2.8 | Shared-line Features (remote-in-use, call-Barge)..... | 72 |
+| Dc.2.9 | Callback..... | 72 |
+| Dc.2.10 | Connected Name and Number Display ..... | 72 |
+| Dc.2.11 | Call Whisper..... | 72 |
+| Dc.3 | Group Line Services..... | 73 |
+| Dc.3.1 | Introduction ..... | 73 |
+| Dc.3.2 | Enterprise Music On Hold..... | 73 |
+| Dc.3.3 | Call Park ..... | 73 |
+| Dc.3.4 | Call Pickup/Group Pickup ..... | 73 |
+| Annex E (informative): | Bibliography references..... | 73 |
+| Annex F (informative): | Change history..... | 75 |
+
+---
+
+## Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document define the IMS Multimedia Telephony service and the minimum set of capabilities required to secure multi-vendor and multi-operator inter-operability for Multimedia Telephony and related Supplementary Services.
+
+---
+
+## 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] (void)
+- [3] (void)
+- [4] 3GPP TS 22.228: "IP multimedia (IM) CN subsystem, stage 1"
+- [5] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN and the means to describe them".
+- [6] 3GPP TS 22.041: "Operator Determined Barring (ODB)"
+- [7] 3GPP TS 24.173: " IMS Multimedia Telephony Communication Service and Supplementary Services; Stage 3"
+- [8] 3GPP TS 22.101: "Service principles".
+- [9] 3GPP TS 22.182: "Customized Alerting Tones (CAT) Requirements; Stage 1".
+- [10] 3GPP TS 22.183: "Customized Ringing Signal (CRS) Requirements; Stage 1".
+- [11] ITU-T Recommendation F.703: "Multimedia Conversational Services".
+- [12] 3GPP TS 22.090 : "Unstructured Supplementary Service Data (USSD); Stage 1".
+- [13] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".
+- [14] 3GPP TS 22.030 : " Man-Machine Interface (MMI) of the User Equipment (UE)".
+- [15] ATIS 1000067.2015, "IP NGN Enhanced Calling Name (eCNAM)"
+- [16] IETF RFC 8224: "Authenticated Identity Management in the Session Initiation Protocol (SIP)".
+- [17] ATIS 1000074.2019, "Signature-based Handling of Asserted information using toKENs (SHAKEN)".
+
+## 3 Definitions, symbols and abbreviations
+
+### 3.1 Definitions
+
+**Caller Identity Analytics function:** A verification function that analyzes a large set of traffic data to identify fraud and caller identity spoofing trends and make risk recommendations about the originating telephone number based on trend analysis.
+
+**Block list:** List of identities or identity ranges that, for one reason or another, are being denied a particular service.
+
+**Spoofed call:** A call where caller identity creation, modification or removal in call signalling results in an unauthorized or illegal use of this identity in the call., This typically occurs where the caller intends to defraud the called user or otherwise illegally obscure the real caller identity.
+
+**Allow list:** List of identities or identity ranges that are provided particular services. Allow list is also named VIP list.
+
+### 3.2 Symbols
+
+(void).
+
+### 3.3 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].
+
+| | |
+|-------|----------------------------------------------------------------------|
+| 3PTY | Three Party |
+| ACR | Anonymous Communication Rejection |
+| AOC-C | Advice Of Charge - Charging |
+| AOC-D | Advice Of Charge - During the communication |
+| AOC-E | Advice Of Charge - at the End of the communication |
+| AOC-I | Advice Of Charge - Information |
+| AOC-S | Advice Of Charge - charging information at communication Set-up time |
+| CAT | Customized Alerting Tone |
+| CB | Communication session Barring |
+| CCBS | Completion of Communication sessions to Busy Subscriber |
+| CD | Communication Deflection |
+| CDIV | Communication DIVersion |
+| CFB | Communication Forwarding Busy |
+| CFNL | Communication Forwarding on Not Logged-in |
+| CFNR | Communication Forwarding No Reply |
+| CFNRc | Communication Forwarding on Subscriber Not Reachable |
+| CFU | Communication Forwarding Unconditional |
+| COLP | CONnected Line identification Presentation |
+| COLR | CONnected Line identification Restriction |
+| CONF | CONFerence |
+| CRS | Customized Ringing Signal |
+| CS | Circuit Switched |
+| CUG | Closed User Group |
+| CW | Communication Waiting |
+| eCNAM | Enhanced Calling Name |
+| ECT | Explicit Communication Transfer |
+| FA | Flexible Alerting |
+| HOLD | Communication HOLD |
+| ICB | Incoming Communications Barring |
+| MCID | Malicious Communication IDentification |
+| MWI | Message Waiting Indication |
+| OCB | Outgoing Communications Barring |
+
+| | |
+|--------|---------------------------------------------------------------|
+| OIP | Originating Identification Presentation |
+| OIR | Originating Identification Restriction |
+| PSAP | Public Safety Answer Point |
+| PUI | Public User Identity |
+| SHAKEN | Signature-based Handling of Asserted information using toKENs |
+| STIR | Secure Telephone Identity Revisited |
+| TIP | Terminating Identification Presentation |
+| TIR | Terminating Identification Restriction |
+
+---
+
+## 4 Service description
+
+### 4.1 General Service characteristics
+
+The IMS Multimedia Telephony Service should allow multimedia conversational communications between two or more users. It provides real time bidirectional conversational transfer of speech, video or optionally other types of data.
+
+The IMS Multimedia Telephony communication is point to point between terminals communicating, or a terminal and a network entity. This communication is usually symmetrical, but in special cases the media components present in each direction may be different, or they may be the same but with different bit rates and Quality of Service.
+
+An IMS Multimedia Telephony communication can start with only one type of media and additional types of media may or may not be added by the users as the communication progress. Therefore a particular IMS Multimedia Telephony communication may consist of only one type of media, e.g. speech.
+
+IMS Multimedia Telephony service is different from other IMS based services, such as Push to Talk over Cellular (PoC).
+
+Its characteristics includes the following:
+
+- IMS Multimedia Telephony is a service where speech, and speech combined with other media components, is the typical usage but the service is not limited to always include speech, it also caters for other media or combinations of media (e.g. text and video).
+- The IMS multimedia telephony service includes supplementary services. The behaviour of these services is almost identical to supplementary services for CS voice (TS 11) and PSTN/ISDN.
+
+NOTE: most supplementary services are active in the set-up phase. Mid-session supplementary services such as session transfer and session hold exist.
+
+- The anticipated usage model is that of traditional telephony: one user connecting to any other user, regardless of operator and access technology.
+- When a supplementary service is invoked it applies to all media components of an IMS Multimedia Telephony communication. A supplementary service can be activated by the user for one or more types of media components. If one or more of these media components are present in the IMS Multimedia Telephony communication then the supplementary service is invoked.
+
+### 4.2 Default media handling capabilities of IMS Multimedia Telephony service
+
+IMS Multimedia Telephony can support many different types of media.
+
+IMS Multimedia Telephony service includes the following standardized media capabilities:
+
+- Full duplex speech;
+- Real time video (simplex, full duplex), synchronized with speech if present;
+- Real-Time Text communication;
+- File transfer;
+
+- Video clip sharing, picture sharing, audio clip sharing. Transferred files may be displayed/replayed on receiving terminal for specified file formats
+- Fax;
+- Data (CS).
+
+The support of each of these media capabilities is optional for a UE.
+
+At least one common standardized format (e.g. JPEG, AMR) shall be supported per media type.
+
+NOTE: IMS Multimedia Telephony service fulfils the service requirement for the Total Conversation in ITU-T F 703 [11].
+
+The IMS Multimedia Telephony service shall support the following handling of media
+
+- Adding, removing and modifying individual media to/from an IMS Multimedia Telephony communication
+
+## 4.3 Association of Services to Time/Date
+
+As a service option, the activation, deactivation and invocation of services may be associated with a time and/or date setting. To support roaming, the time zone may also be included.
+
+## 4.4 Additional timing information
+
+As a service option, additional timing information on current active services may be made available by the network. The content of this information is service dependant.
+
+As a service option, the user may be allowed dynamically extend this timing for the active communication.
+
+## 4.5 Allow / block list
+
+As service provider option, activation/deactivation/invocation services may be associated with a allow/block list. A list may be specific to a service or may be used by several services.
+
+## 4.6 Multi-device and Multi-Identity
+
+### 4.6.1 General
+
+The support of multiple devices is inherent in IMS. In addition, a service provider may allow a user to use any public user identities for its outgoing and incoming calls. The added identities can but do not have to belong to the served user. Identities may be part of different subscriptions and different operators.
+
+NOTE: The identity does not have to be pre-allocated to an individual USIM or ISIM.
+
+The owner (e.g. individual subscriber, operator/company) of the added identity needs to give its permission for others to use the identity.
+
+The owner (e.g. individual subscriber, operator/company) of the identity shall be able to revoke the permission for others to use the identity.
+
+A user shall be able to indicate which of the allowed identities the user wishes to use for each outgoing communication.
+
+The network shall be able to indicate to the user which identity the incoming communication is intended to reach.
+
+The network shall allow users to add and to delete identities asymmetrically, e.g. if an identity belonging to user B is allowed to be used by user A, this does not automatically mean that an identity belonging to user A is allowed to be used by user B.
+
+Synchronization of communication logs between the multiple devices that are registered under the user identity shall be possible, e.g. the list of in- and outgoing calls, as well as when a missed call notification has been read on one device the other devices shall be updated so they are aligned.
+
+#### 4.6.2. User Configuration
+
+The 3GPP System shall support a mechanism for an authorised user to set user preferences to indicate which identities are active or inactive on a specific UE
+
+When an identity is activated or deactivated all UEs that can use that identity to either originate or terminate a session shall receive a notification of the change of status.
+
+### 4.7 Caller Identity Verification Results Delivery to the User
+
+The OIP service (including delivery of the calling name) and the eCNAM service deliver identity information based on information generated by the originating network (e.g., telephone number). Caller Identity Verification functions, such as Caller Identity Analytics functions at the terminating network, can modify the originating network's caller identity information in accordance with the terminating operator policy. The modified name is intended to provide information to the end user about the potential risks associated with the caller identity.
+
+Full or partial name string modifications that result from or are performed by the Caller Identity Analytics function shall be delivered to the UE, according to local operator policy.
+
+Example displays:
+
+- J. Smith
+- "SCAM?" J. Smith
+- "POSSIBLE SCAM".
+
+This is primarily intended for situations where the existing device is unable to, otherwise, present new information to the user, such as spoofing indications.
+
+The 3GPP system shall support a mechanism for a user to simply retrieve (e.g., to view or save) the full or partial name string delivered to the UE, including modifications that result from or are performed by the Caller Identity Analytics function.
+
+NOTE: This applies to both answered calls and missed/unanswered calls (which are received but not answered due to call waiting or other reasons, including some calls rejected by the user intentionally).
+
+---
+
+## 5 Service Requirements
+
+General service requirements as specified for IMS services in [4] apply.
+
+---
+
+## 6 Quality of Service
+
+General QoS requirements as specified for IMS services in [4] apply.
+
+---
+
+## 7 Interworking requirements
+
+### 7.1 Interworking with CS domain
+
+Standardisation of interworking between the IMS domain and the CS domain for multimedia telephony communications is provided as specified in [4].
+
+## 7.2 Interworking with external networks
+
+General interworking requirements with external networks as specified for IMS services in [4] apply.
+
+## 7.3 Media Aspects on Interworking
+
+End to end codec negotiation shall be supported. When the codec negotiation fails, transcoding should be provided as an operator option.
+
+When transcoding applies, the quality degradation and additional latency due to decoding/encoding operation shall be minimized.
+
+When the media plane is locally broken-out and/or locally broken-in within a visited network, the home network may instruct the visited network to perform transcoding.
+
+To optimize the end-user experience, during the codec negotiation and subject to operator policy, a wideband codec should be preferred over a narrowband codec, subject to the capabilities of both ends.
+
+---
+
+## 8 Supplementary Services
+
+### 8.1 General
+
+This clause provides the description of the supplementary services applicable to IMS Multimedia Telephony service.
+
+The behaviour of IMS supplementary services, as perceived by the user, shall be consistent with the behaviour perceived when using the equivalent supplementary services on PSTN/ ISDN and CS mobile networks.
+
+For each supplementary service, the following is provided:
+
+- a short service definition;
+- a description of the normal operation with successful outcome.
+
+And when applicable also:
+
+- a description of exceptional operation or unsuccessful outcome;
+- descriptions on interaction with other supplementary services applicable to IMS Multimedia Telephony service;
+- consideration for interworking with the CS mobile and fixed services.
+
+In general, if a service is not mentioned within the interaction clause then there is no impact.
+
+The support of some of these services may be mandatory or optional depending on specific country/regional regulation.
+
+For CEPT members see annex C.
+
+Some services are not applicable to UE accessing IMS via 3GPP accesses. See annex D.
+
+### 8.2 Supplementary Services applicable to IMS Multimedia Telephony
+
+#### 8.2.1 Originating Identification Presentation (OIP)
+
+##### 8.2.1.1 Definition
+
+The OIP service provides the terminating party with the Identity of the originating party.
+
+The requirements for Presentation of session originating party identity shall be handled as described in [4].
+
+### 8.2.1.2 Service interactions with other IMS supplementary services
+
+#### 8.2.1.2.1 Identification services
+
+##### 8.2.1.2.1.1 Originating Identification Restriction (OIR)
+
+The requirements for the interactions between presenting and withholding the originating party's identity shall be as described in [4].
+
+##### 8.2.1.2.1.2 Enhanced Calling Name
+
+For users that subscribe to both OIP and eCNAM, originating party identity and eCNAM identity data shall be delivered to the terminating party.
+
+The terminating service provider shall extract the originating party's telephone number from the originating party identity (e.g., from the tel-URI) to use in its query to retrieve eCNAM identity data from a trusted data source.
+
+If the originating party's telephone number cannot be obtained, eCNAM shall not be retrieved. Instead, the terminating service provider shall indicate the unavailability of the eCNAM identity data to the terminating party.
+
+The interface between terminating service provider and the trusted data source shall be private and secure.
+
+The conditions for exchange of data are governed by regional regulation and through service provider agreement.
+
+#### 8.2.1.2.2 Diversion services
+
+##### 8.2.1.2.2.1 Communication Forwarding Unconditional (CFU)
+
+When a communication has been forwarded and the forwarded-to party has been provided with the OIP service, the forwarded-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+##### 8.2.1.2.2.2 Communication Forwarding Busy (CFB)
+
+When a communication has been forwarded and the forwarded-to party has been provided with the OIP service, the forwarded-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+##### 8.2.1.2.2.3 Communication Forwarding No Reply (CFNR)
+
+When a communication has been forwarded and the forwarded-to party has been provided with the OIP service, the forwarded-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+##### 8.2.1.2.2.4 Communication Forwarding on Not Logged-in (CFNL)
+
+When a communication has been forwarded and the forwarded-to party has been provided with the OIP service, the forwarded-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+##### 8.2.1.2.2.5 Communication Deflection (CD)
+
+When a communication has been deflected and the deflected-to party has been provided with the OIP service, the deflected-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+#### 8.2.1.2.2.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)
+
+When a communication has been forwarded and the forwarded-to party has been provided with the OIP service, the forwarded-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+8.2.1.2.2.7 (void)
+
+#### 8.2.1.2.3 Communication Waiting (CW)
+
+If a party has the OIP service active and is notified that an incoming communication is waiting, then this party shall receive the identity information of the originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+### 8.2.1.3 Interoperability with PSTN/ISDN and mobileCS Networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the OIP service with mobile CS and PSTN/ISDN Supplementary Service CLIP and vice-versa. The scope of this interworking may result in a limited service capability (only E.164 numbers can be used in the PSTN/ISDN).
+
+## 8.2.2 Originating Identification Restriction (OIR)
+
+### 8.2.2.1 Definition
+
+The Originating Identification Restriction (OIR) service enables the originating party to withhold the presentation of its asserted identity information to the terminating party.
+
+The requirements for withholding the originators identity shall be as described in [4]. Those requirements also allow certain terminating party to override the restriction (override capability).
+
+### 8.2.2.2 Service interactions with other IMS supplementary services
+
+#### 8.2.2.2.1 Identification services
+
+##### 8.2.2.2.1.1 Originating Identification Presentation (OIP)
+
+The requirements for the interactions between presenting and withholding the originating parties' identity shall be as described in [4].
+
+##### 8.2.2.2.1.2 Enhanced Calling Name
+
+The requirements for interactions between presenting and withholding the originating party's eCNAM identity data shall adhere to the rules described in [4] for the presentation of session originator identity.
+
+If the originating party subscribed to or invokes OIR, eCNAM identity information shall not be delivered, including data elements that the originating party had consented to release.
+
+#### 8.2.2.2.2 Diversion services
+
+##### 8.2.2.2.2.1 Communication Forwarding Unconditional (CFU)
+
+When the OIR service has been invoked, the originating party's identity information shall not be presented to the forwarded-to party unless the forwarded-to party has an override capability.
+
+##### 8.2.2.2.2.2 Communication Forwarding Busy (CFB)
+
+Same as for CFU.
+
+#### 8.2.2.2.2.3 Communication Forwarding No Reply (CFNR)
+
+Same as for CFU.
+
+#### 8.2.2.2.2.4 Communication Forwarding on Not Logged-in (CFNL)
+
+Same as for CFU.
+
+#### 8.2.2.2.2.5 Communication Deflection (CD)
+
+Same as for CFU.
+
+#### 8.2.2.2.2.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)
+
+Same as for CFU.
+
+#### 8.2.2.2.2.7 (void)
+
+### 8.2.2.2.3 Explicit Communication Transfer (ECT)
+
+An originating party's restriction requirements from the original communication shall be used in order to restrict the presentation of that party's identity to any party in a transferred communication.
+
+### 8.2.2.3 Interoperability with PSTN/ISDN and mobile CS Networks
+
+The IMS Multimedia Telephony service shall support the interoperability of OIR service with the mobile CS and the PSTN/ISDN Supplementary Service CLIR and vice-versa. The scope of this interworking may result in a limited service capability. The Originating Identity Restriction information shall be conveyed from IMS to a mobile CS or a PSTN/ISDN and vice-versa. The network to which the called/terminating party is connected to is responsible to handle this service.
+
+In case of limited interoperability, the restriction, OIR/CLIR shall have precedence.
+
+## 8.2.3 Terminating Identification Presentation (TIP)
+
+### 8.2.3.1 Definition
+
+The TIP service provides the originating party with the asserted identity of the terminating party. The requirements for the presentation of the terminating identity shall be as described in [4].
+
+NOTE: See also service definition in [E-17].
+
+### 8.2.3.2 Service interactions with other IMS supplementary services
+
+#### 8.2.3.2.1 Identification services
+
+##### 8.2.3.2.1.1 Terminating identification presentation restriction
+
+The requirements for the interactions between presenting and withholding the terminating party's identity shall be as described in [4].
+
+#### 8.2.3.2.2 Diversion services
+
+If forwarding party B chooses to restrict the presentation of the forwarded-to party C's identity, the originating party A shall not receive the terminating party C's identity irrespective of whether the terminating party C has TIR activated or not.
+
+### 8.2.3.3 Interoperability with PSTN/ISDN and mobile CS Networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the TIP services with mobile CS and PSTN/ISDN Supplementary Service COLP and vice-versa. The scope of this interworking may result in a limited service capability
+
+## 8.2.4 Terminating Identification Restriction (TIR)
+
+### 8.2.4.1 Definition
+
+The Terminating Identification Restriction (TIR) enables the terminating party to withhold presentation of its asserted identity information to the originating party.
+
+The requirements for withholding the terminating party's identity are described in [4]. Those requirements also allow certain originating parties to override the restriction (override capability).
+
+This service description is based on the service description described in [E-20].
+
+### 8.2.4.2 Service interactions with other IMS Multimedia Telephony services
+
+#### 8.2.4.2.1 Identification services
+
+##### 8.2.4.2.1.1 Terminating Identification Presentation (TIP)
+
+The requirements for the interactions between presenting and withholding the terminating party's identity shall be as described in [4].
+
+### 8.2.4.3 Interoperability with PSTN/ISDN and mobile CS Networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the TIR services with mobile CS and PSTN/ISDN Supplementary Services and vice-versa. The scope of this interworking may result in a limited service capability.
+
+In the case the target network does not support TIR service, the TIP information shall not be forwarded.
+
+## 8.2.5 Malicious Communication Identification (MCID)
+
+### 8.2.5.1 Definition
+
+The MCID service enables an incoming communication to be identified as malicious and registered.
+
+This service may be available to a user only after subscription. Once the user has indicated to the network that the communication is malicious, the IMS shall register at least the following information:
+
+- Terminating Identity Information;
+- Originator Identity Information;
+- Local Time and Date of the invocation in the network serving the terminating entity;
+
+The information shall not be available to the terminating entity nor the originating entity. The information shall be under the control of the network operator.
+
+The user may identify the communication as malicious during the alerting phase, during an ongoing communication, or for a limited period after the communication has ceased.
+
+## 8.2.5.2 Service interactions with other IMS supplementary services
+
+### 8.2.5.2.1 Diversion Services
+
+The MCID service can be invoked for a diverted communication. In addition to the normal operation of the MCID service, the identity of the first diverting party shall be registered and, as a network option, the last diverting party can be registered.
+
+#### 8.2.5.2.1.1 Communication Forwarding No Reply (CFNR)
+
+If the terminating party has activated CFNR, once forwarding has taken place, the forwarding party cannot invoke the MCID service.
+
+#### 8.2.5.2.1.2 Communication Deflection (CD)
+
+If the terminating party has activated communication deflection, once deflection has taken place, the deflecting party cannot invoke the MCID service.
+
+### 8.2.5.2.2 Explicit Communication Transfer (ECT)
+
+The transferring party cannot invoke the malicious communication identification service on a communication after transfer of that communication has been successfully invoked.
+
+If after a transfer has been completed, the transferred-to party successfully invokes the malicious communication identification service, then the network shall register the identities of all parties involved.
+
+### 8.2.5.2.3 CONFerence (CONF)
+
+The conference controller cannot invoke the malicious call identification IMS supplementary service for participants within the conference.
+
+**NOTE:** To activate the malicious call identification IMS supplementary service, the conference controller should first create a private communication with the user to be identified using the malicious call identification IMS supplementary service.
+
+If a participant invokes the malicious call identification IMS supplementary service, only information about the connection to the conference controller shall be registered. No information about the other participants shall be registered.
+
+### 8.2.5.2.4 Three-Party (3PTY)
+
+See clause 8.2.5.2.3, noting that 3PTY is a special case of CONF.
+
+## 8.2.5.3 Interoperability with PSTN/ISDN Networks
+
+The MCID service shall interoperate for all communications from a PSTN/ISDN to an IMS Network supporting IMS Multimedia Telephony service and vice-versa. The registered information shall be stored in the invoking party's network and may also be stored in the malicious party's network.
+
+## 8.2.6 Anonymous Communication Rejection (ACR)
+
+### 8.2.6.1 Definition
+
+The Anonymous Communications Rejection (ACR) service allows the terminating party to reject incoming communications from originating parties that have restricted their identity presentation.
+
+Anonymous communications rejection provides the capability for network, on behalf of the user, to reject incoming sessions from users who have restricted the presentation of their originating identity, i.e. the asserted originating identity is marked "presentation restricted".
+
+This service description is based on the service description described in [E-14].
+
+### *Optional feature*
+
+In case of ACR service,
+
+- a allow list should contain certified public identities or identity ranges of users, from which incoming anonymous communications are allowed whatever ACR activation state,
+- a block list should contain certified public identities or identity ranges of users, from which incoming anonymous communications are not allowed whatever ACR activation state.
+
+## 8.2.6.2 Service interactions with other IMS supplementary services
+
+### 8.2.6.2.1 Identification Services
+
+#### 8.2.6.2.1.1 Originating Identification Presentation (OIP)
+
+No impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.
+
+#### 8.2.6.2.1.2 Originating Identification Restriction (OIR)
+
+If the terminating party has activated the ACR service, then the OIR service causes the execution of the ACR service in accordance with the procedures in clause 8.2.6.1.
+
+If the terminating party has the override capability according to the OIR service, then the ACR service shall not apply.
+
+### 8.2.6.2.2 Diversion Services
+
+NOTE: The precedence that ACR takes over the communication diversion services does not exclude the use of forwarding functionality in the ACR functionality itself. As an example: forwarding of anonymous communications (e.g. to a voice mailbox), as part of the ACR functionality is possible.
+
+If the diverted-to user has activated the ACR service, then the ACR service shall take precedence over the communication diversion supplementary service i.e. the communication shall be rejected according to the ACR service.
+
+#### 8.2.6.2.2.1 Communication Forwarding Unconditional (CFU)
+
+If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding unconditional service i.e. the communication shall be rejected according to the ACR service.
+
+#### 8.2.6.2.2.2 Communication Forwarding Busy (CFB)
+
+If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding busy service i.e. the communication shall be rejected according to the ACR service.
+
+#### 8.2.6.2.2.3 Communication Forwarding No Reply (CFNR)
+
+If the forwarding party has activated the ACR service:
+
+- no impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.
+
+NOTE: If the originating party has restricted its identity due to the OIR service the communication will not be presented.
+
+#### 8.2.6.2.2.4 Communication Forwarding on Not Logged-in (CFNL)
+
+If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding on not logged in service i.e. the communication shall be rejected according to the ACR service.
+
+#### 8.2.6.2.2.5 Communication Forwarding on Subscriber Not Reachable (CFNRc)
+
+If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding on subscriber not reachable service i.e. the communication shall be rejected according to the ACR service.
+
+#### 8.2.6.2.3 Communication Waiting (CW)
+
+If the terminating party has activated the ACR service, then the ACR service shall take precedence over the Communication Waiting service. The ACR service can be activated while a communication is waiting without changing the state of the waiting communication session.
+
+#### 8.2.6.2.4 Completion of Communications to Busy Subscriber (CCBS)
+
+NOTE: A CCBS recall (from the network to the originating party) resulting from the completion of communications to busy subscribers shall not be rejected due to the application of the ACR service.
+
+Assuming the originating party connects to the terminating party and the terminating party activates the ACR service (or has activated the ACR service), two cases are possible:
+
+a) The ACR service was activated by the terminating party before the originating party originates a communication:
+
+- No impact, i.e. no IMS supplementary service shall affect the operation of the other IMS supplementary service.
+
+NOTE: If the originating party has restricted its identity due to the OIR service and if the terminating party is busy, the originating party will receive no busy indication, and the completion of communications to busy subscriber service will not apply. Instead the communication session attempt shall be rejected according to the normal procedures of the ACR service.
+
+b) The ACR service is activated by the terminating party after the originating party has activated the completion of communications to busy subscriber service on the terminating party:
+
+- If the terminating party activates the ACR service after the originating party has activated the completion of communications to busy subscriber service on the terminating party, then the communication resulting from the completion of communications to busy subscriber service shall be rejected if the originating party has restricted its identity due to the OIR service.
+
+#### 8.2.6.3 Interoperability with PSTN/ISDN
+
+The IMS Multimedia Telephony service shall support the interoperability of the ACR services with PSTN/ISDN Supplementary Services and vice-versa. The scope of this interworking may result in a limited service capability.
+
+### 8.2.7 Communication DIVersion (CDIV)
+
+#### 8.2.7.1 Definition
+
+The following Communication DIVersion services are defined:
+
+- Communication Forwarding Unconditional (CFU).
+- Communication Forwarding Busy (CFB).
+- Communication Forwarding No Reply (CFNR).
+- Communication Forwarding on Not Logged in (CFNL).
+- Communication Deflection (CD).
+- Communication Forwarding on Subscriber Not Reachable (CFNRc).
+
+For all communications diversion services, a service provider option of notification of diversion may be provided to the originating party. This service provider option may also include support for the invoking user to suppress the notification.
+
+As a service option, CDIV services may be associated with a time and/or date setting. To support roaming, the time zone may also be included.
+
+As a service option, CDIV services may be associated with the results of spoofed call detection applied to the session originator identity.
+
+The use of any of the network determined diversion services on a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.
+
+#### Communication Forwarding Unconditional (CFU)
+
+The CFU service enables a user to have the network redirect all communications to another user. The CFU service may operate on all communication, or just those associated with specified services. The user's ability to originate communications is unaffected by the CFU service. After the CFU service has been activated, communications are forwarded independent of the status of the user.
+
+As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFU service has been activated. This indication may be provided when the user originates a communication if the CFU service has been activated for the user's identity and for the service requested for the communication.
+
+The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
+
+This service description is based on the service description described in [E-1].
+
+#### Communication Forwarding Busy (CFB)
+
+The CFB service enables a user to have the network redirect communications, which would otherwise be regarded as busy, to another user. The CFB service may operate on all communications, or just those associated with specified services. The user's ability to originate communications is unaffected by the CFB service.
+
+As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFB service has been activated. This indication may be provided when the user originates a communication if the CFB service has been activated for the user and for the service requested for the communication.
+
+The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
+
+This service description is based on the service description described in [E-2].
+
+#### Communication Forwarding No Reply (CFNR)
+
+The CFNR service enables a user to have the network redirect communications, when the communication request is not responded to within a defined period of time, to another user. The CFNR service may operate on all communications, or just those associated with specified services. The user's ability to originate communications is unaffected by the CFNR service.
+
+The CFNR service can only be invoked by the network after the communication has been offered to the user and an indication that the user has been informed of the communication request.
+
+As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNR service has been activated. This indication may be provided when the user originates a communication if the CFNR service has been activated for the user and for the service requested for the communication.
+
+The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
+
+This service description is based on the service description described in [E-3].
+
+As a service option, CFNR activation confirmation may include information from the network providing the public identity where the communication will be forwarded to, and the expiry time before the communication is forwarded.
+
+As a service option, the user may be allowed to dynamically extend this timing.
+
+#### Communication Forwarding on Not Logged-in (CFNL)
+
+The Communication Forwarding on Not Logged-in (CFNL) service enables a user to redirect incoming communications, when the user is not currently registered (logged-in), to another user. The CFNL service may operate on all communications, or just those associated with specified services.
+
+As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNL service has been activated. This indication may be provided when the user next registers (logs in). An indication may also be provided as part of de-registration (log out).
+
+The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
+
+#### Communication Deflection (CD)
+
+The CD service enables the user to respond to an incoming communication by requesting redirection of that communication to another user. The CD service can only be invoked before the communication is established by the user, i.e. in response to the offered communication, or during the period that the user is being informed of the communication. The user's ability to originate communications is unaffected by the CD service.
+
+The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
+
+This service description is based on the service description described in [E-4].
+
+#### Communication Forwarding on Subscriber Not Reachable (CFNRc)
+
+The CFNRc service enables a user to have the network redirect all incoming communications, or just those associated with a specific service, when called mobile subscriber's address is not reachable (e.g. there is no IP connectivity to the user's terminal, or, in the case of a mobile device, it is not in radio coverage), to another address. The CFNRc service may operate on all communications, or just those associated with specified services. The user's ability to originate communications is unaffected by the CFNRc service.
+
+**NOTE:** It may be affected by the reason that have triggered the loss of connectivity, e.g. in the mobile case if the mobile subscriber is de-registered, if there is radio congestion or if the mobile subscriber for example is being out of radio coverage,
+
+As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNRc service has been activated. This indication may be provided when the user originates a communication if the CFNRc service has been activated for the user and for the service requested for the communication.
+
+The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.
+
+#### *Optional feature*
+
+Lists can be used also in association to Communication Diversions (CDIV).
+
+- a block list should contain public identities or identity ranges of users, from which incoming communications are not forwarded when CDIV is activated.
+
+- a allow list should contain public identities or identity ranges of users, from which incoming communications are forwarded when CDIV is activated.
+
+#### 8.2.7.2 (void)
+
+### 8.2.7.3 Service interactions with other IMS supplementary services
+
+#### 8.2.7.3.1 Identification services
+
+##### 8.2.7.3.1.1 Originating Identification Presentation (OIP)
+
+When a communication has been diverted and the diverted-to party has been provided with the originating identification presentation service, the diverted-to party shall receive the identity of the originating party, if this originating party has not subscribed to or invoked the originating identification restriction service.
+
+##### 8.2.7.3.1.2 Originating Identification Restriction (OIR)
+
+When the originating identification restriction service has been invoked, the originating party's identity shall not be presented to the diverted-to party unless the diverted-to party has an override capability.
+
+##### 8.2.7.3.1.3 Terminating Identification Presentation (TIP)
+
+When a communication has been diverted and the originating party has been provided with the terminating identification presentation service, the originating party shall receive the identity of the diverted-to party, unless the diverting user has selected the option to suppress the notification of diversion.
+
+##### 8.2.7.3.1.4 Terminating Identification Restriction (TIR)
+
+If the diverting party or the diverted-to party has invoked the Terminating Identification Restriction service, then the diverted-to party's identity shall not be provided to the originating party unless the originating party has override capability.
+
+##### 8.2.7.3.1.5 Enhanced Calling Name (eCNAM)
+
+When a communication has been diverted and the diverted-to party subscribes to the eCNAM service, the diverted-to party shall receive the eCNAM identity data of the original originating party, if this originating party has not subscribed to or invoked OIR.
+
+#### 8.2.7.3.2 Malicious Communication Identification (MCID)
+
+This service does not apply to UE accessing from mobile 3GPP access networks.
+
+See clause 8.2.5.2.1.
+
+#### 8.2.7.3.3 Anonymous Communication Rejection (ACR)
+
+This service does not apply to UE accessing from mobile 3GPP access networks.
+
+See clause 8.2.6.2.2.
+
+#### 8.2.7.3.4 Diversion services
+
+##### 8.2.7.3.4.1 Communication Forwarding Unconditional (CFU)
+
+**Communication Forwarding Unconditional (CFU):** Not applicable.
+
+**Communication Forwarding Busy (CFB):** Invocation of the communication forwarding unconditional service shall take precedence over the CFB service.
+
+**Communication Forwarding No Reply (CFNR):** Invocation of the communication forwarding unconditional service shall take precedence over the CFNR service.
+
+**Communication Forwarding on Not Logged-in (CFNL):** Invocation of the communication forwarding unconditional service shall take precedence over the CFNL service.
+
+**Communication Deflection (CD):** Invocation of the communication forwarding unconditional service shall take precedence over the CD service.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** Invocation of the communication forwarding unconditional service shall take precedence over the CFNRc service.
+
+#### 8.2.7.3.4.2 Communication Forwarding Busy (CFB)
+
+**Communication Forwarding Unconditional (CFU):** Invocation of the CFU service shall take precedence over the communication forwarding busy service.
+
+**Communication Forwarding Busy (CFB):** Not applicable.
+
+**Communication Forwarding No Reply (CFNR):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding on Not Logged-in (CFNL):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Deflection (CD):** If the terminating party is not network determined user busy, then the CD service or the communication forwarding busy service can be invoked, depending on the response from the terminating party.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** If the terminating party is network determined busy, then CFB shall take precedence over CFNRc. Otherwise, if the terminating party is not network determined user busy, then there is no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.7.3.4.3 Communication Forwarding No Reply (CFNR)
+
+**Communication Forwarding Unconditional (CFU):** Invocation of the CFU service shall take precedence over the communication forwarding no reply service.
+
+**Communication Forwarding Busy (CFB):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding No Reply (CFNR):** Not applicable.
+
+**Communication Forwarding on Not Logged-in (CFNL):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Deflection (CD):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+NOTE: If the network indicates the arrival of an incoming communication to the terminating party, then the CD service, or the communication forwarding no reply service can be invoked, depending on the response, or lack of response, from the terminating party.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.7.3.4.4 Communication Forwarding on Not Logged-in (CFNL)
+
+**Communication Forwarding Unconditional (CFU):** Invocation of the communication forwarding unconditional service shall take precedence over the CFNL service.
+
+**Communication Forwarding Busy (CFB):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding No Reply (CFNR):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding on Not Logged-in (CFNL):** Not applicable.
+
+**Communication Deflection (CD):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.7.3.4.5 Communication Deflection (CD)
+
+**Communication Forwarding Unconditional (CFU):** Invocation of the CFU service shall take precedence over the communication deflection service.
+
+**Communication Forwarding Busy (CFB):** If the terminating party is not network determined user busy, then the communication deflection service or the CFB service can be invoked, depending on the response from the terminating party.
+
+**Communication Forwarding No Reply (CFNR):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+NOTE: If the network indicates the arrival of an incoming communication to the terminating party, then the communication deflection service, or the CFNR service can be invoked, depending on the response, or lack of response, from the terminating party.
+
+**Communication Forwarding on Not Logged-in (CFNL):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Deflection (CD):** Not applicable.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.7.3.4.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)
+
+**Communication Forwarding Unconditional (CFU):** Invocation of the communication forwarding unconditional service shall take precedence over the CFNRc service.
+
+**Communication Forwarding Busy (CFB):** If the terminating party is network determined busy, then CFB shall take precedence over CFNRc. Otherwise, if the terminating party is not network determined user busy, then there is no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding No Reply (CFNR):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding on Not Logged-in (CFNL):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Deflection (CD):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** Not applicable.
+
+#### Explicit Communication Transfer (ECT)
+
+No interaction, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### Other services:
+
+Communication Forwarding on Mobile Subscriber Not Reachable (CFNRc) shall interact with the following IMS supplementary services in exactly the same way as described for Communication Forwarding No Reply (CFNR):
+
+Originating Identification Presentation (OIP)
+
+Originating Identification Restriction (OIR)
+
+Terminating Identification Presentation (TIP)
+Terminating Identification Restriction (TIR)
+Communication Diversion (CDIV); Communication Forward Unconditional
+Communication Diversion (CDIV); Communication Deflection
+Communication Diversion (CDIV); Communication Forward On not Logged-in
+Communication Hold (HOLD)
+Communication Barring (CB)
+Message Waiting Indication (MWI)
+Conference (CONF)
+
+8.2.7.3.4.7 (void)
+
+#### 8.2.7.3.5 Communication Waiting (CW)
+
+**Communication Forwarding Unconditional (CFU):** CW has no impact on CFU. The communication will be forwarded without regard to the terminating party's state. A forwarded-to party may have communication waiting service and this will be activated if busy.
+
+A forwarded communication can result in the communication waiting service.
+
+**Communication Forwarding Busy (CFB):** No impact, i.e. neither service shall affect the operation of other service. A forwarded communication can result in the communication waiting service.
+
+NOTE: If the terminating party is Network Determined User Busy, the communication waiting service is not be invoked, and the CFB service is invoked if it was activated.
+
+**Communication Forwarding No Reply (CFNR):** If the terminating party has activated the CFNR service, then a waiting communication shall still be offered. If the CFNR timer expires before an answer is received then the CFNR service shall be invoked and the communication shall be forwarded and communication waiting ceased.
+
+A forwarded communication can result in the communication waiting service.
+
+**Communication Forwarding on Not Logged-in (CFNL):** No impact.
+
+NOTE: If a party with an active communication waiting logs out, the all active and offered communication would be released.
+
+**Communication Deflection (CD):** When receiving the communication waiting indication, terminating party can invoke the CD service. A deflected communication can result in the communication waiting service.
+
+**Communication Forwarding on Subscriber Not Reachable (CFNRc):** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.7.3.6 Communication Barring (CB)
+
+##### 8.2.7.3.6.1 Outgoing communication barring-fixed
+
+If the outgoing communication barring-fixed service has already been activated, a request to activate any CDIV service shall be rejected if the forwarding party's communication to the diverted-to party would be barred by the outgoing communication barring-fixed service.
+
+If the CDIV service was activated before the activation of the outgoing communication barring-fixed service, the outgoing communication barring-fixed service can still be activated. When the two services have already been activated, a request to invoke the CDIV service shall be rejected if the forwarding party's communication to the diverted-to party would be barred by the outgoing communication barring-fixed service at the time of the invocation attempt of the CDIV service.
+
+##### 8.2.7.3.6.2 Outgoing communication barring-user controlled
+
+If the outgoing communication barring-user controlled service has already been activated, a request to activate any CDIV service shall be rejected if the forwarding party's communication to the diverted-to party would be barred by the outgoing communication barring-user controlled service.
+
+If the CDIV service was activated before the activation of the outgoing communication barring-user controlled service, the outgoing communication barring-user controlled service can still be activated. When the two services have already been activated, a request to invoke the CDIV service shall be rejected if the forwarding party's communication to the diverted-to party would be barred by the outgoing communication barring-user controlled service at the time of the invocation attempt of the CDIV service.
+
+#### 8.2.7.3.7 Completion of Communications to Busy Subscriber (CCBS)
+
+CCBS recalls shall never be diverted. They shall be provided to the original originating party.
+
+#### 8.2.7.3.8 Advice Of Charge (AOC)
+
+##### 8.2.7.3.8.1 Charging information at the End of the communication (AOC-E)
+
+**Originating party:** No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+**Forwarding party:** When a communication is forwarded and the forwarding party is charged for the forwarded part of the communication, then as a network option, the charging information can be transferred to the forwarding user when the communication is terminated provided that the served user has subscribed to the advice of charge: charging information at the end of the communication service with the value of the subscription option set to "for all communications automatically".
+
+#### 8.2.7.4 Interoperability with PSTN/ISDN and CS mobile networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the CDIV service with mobile CS and PSTN/ISDN Supplementary Services and vice-versa. The scope of this interworking may result in a limited service capability. The CLI information of the originating party as well as further CLI information (first redirected address, last redirected address) may be provided to the final called party, if the network allows this.
+
+### 8.2.8 Communication Waiting (CW)
+
+#### 8.2.8.1 Definition
+
+The Communication Waiting (CW) service enables a terminating party to be informed at the time that a new communication is requested, and that no resources are available for that incoming communication.
+
+The user has then the choice of accepting, rejecting or ignoring the incoming communication.
+
+The maximum number of communications that may be waiting is a service provider option.
+
+If the current number of communications waiting is equal to the maximum, then any new attempted incoming communication request shall be rejected with a busy cause.
+
+This service description is based on the service description described in [E-6] and [E-5].
+
+As a service option, the communication waiting indication may also include the expiry time. As a service option, the user may be allowed to dynamically extend this timing.
+
+In the presence of another call at the destination user where the incoming call is identified as a callback to an emergency call, then either the communication request shall be presented, or the CW service shall be used.
+
+#### 8.2.8.2 Service interactions with other IMS supplementary services
+
+##### 8.2.8.2.1 Anonymous Communication Rejection (ACR)
+
+If the terminating party has activated the ACR service, then the ACR service shall take precedence over the Communication Waiting service. The ACR service can be activated while a communication is waiting without changing the state of the waiting communication session.
+
+#### 8.2.8.2.1a Enhanced Calling Name (eCNAM)
+
+If the terminating party has the eCNAM service active and is notified that an incoming communication is waiting, then this terminating party shall receive the eCNAM identity data of the incoming waiting party, if this originating party has not subscribed to or invoked the OIR service.
+
+#### 8.2.8.2.2 Diversion services
+
+The interactions between Communication Waiting and Communication Diversion services are described in clause 8.2.7.3.5 of the present document.
+
+#### 8.2.8.2.3 Completion of Communications to Busy Subscriber (CCBS)
+
+If a subscriber to the completion of communications to busy subscriber service places a communication to a terminating party who has subscribed to the CW service, and the terminating party is provided the communication waiting indication, then invocation of completion of communications to busy subscriber service cannot occur.
+
+#### 8.2.8.3 Interoperability with PSTN/ISDN
+
+No requirements.
+
+### 8.2.9 Communication HOLD (HOLD)
+
+#### 8.2.9.1 Definition
+
+The communication HOLD service enables a user to suspend media within a session, and resume that media at a later time.
+
+Each party in a communication can hold and retrieve the communication independently from the other party. This also applies when a communication involves more than two parties (e.g. CONF).
+
+This service description is based on the service description described in [4], dealing about the user ability to suspend and resume a session.
+
+The use of HOLD on an emergency call, or a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.
+
+#### 8.2.9.2 Service interactions with other IMS supplementary services
+
+##### 8.2.9.2.1 CONFerence (CONF)
+
+A, B and C are in a conference that was created by B invoking the CONF service. B can interrupt their own participation in the conference by using the HOLD service. When B does this, A and C shall not receive the HOLD notification and are not prevented from carrying on their conversation
+
+##### 8.2.9.2.2 Three-Party (3PTY)
+
+See clause 8.2.9.2.1, noting that 3PTY is a special case of CONF.
+
+#### 8.2.9.3 Interoperability with PSTN/ISDN and CS mobile networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the HOLD service with mobile CS and PSTN/ISDN Supplementary Services and vice-versa. The scope of this interworking may result in a limited service capability.
+
+## 8.2.10 Communication Barring (CB)
+
+### 8.2.10.1 Definition
+
+The group of Communication Restriction Services includes two services:
+
+- Outgoing Communications Barring (OCB).
+
+This service allows a user to bar certain categories of outgoing communications. The network shall provide the capability for a user to select a set of categories (e.g. identities or range of identities) for barring. The type of barring is chosen by the user at provision time, and shall be valid for all outgoing communications. The network shall provide the capability for the user to bar outgoing communications based on user defined identities or identity ranges. Barring of an outgoing communication for a specific identity, a number of specific identities, or a range of identities shall be dependent on an entry in a OCB identity list held in the network. This list shall either be a "block list" or "allow list". A "block list" shall contain the identities or identity ranges to be barred by the network for outgoing communications. A "allow list" shall contain the identities or identity ranges that shall be allowed by the network for outgoing communications, i.e. all identities not in the "allow list" shall be barred.
+
+The ability of the served user to receive communications and to originate emergency communications shall be unaffected by OCB.
+
+This service description is based on the service description described in [E-15] and [E-16].
+
+- Incoming Communications Barring (ICB).
+
+This service allows a user to bar certain categories of incoming communications. The service also allows the user to have the barring of incoming communications activated always or only during certain conditions. The network shall provide the capability for a user to select from a set of categories (e.g. identities or range of identities) for barring. Barring of an incoming communication shall be dependent on an entry in an ICB identity list held in the network. This list shall be a "block list" which contains the identities or identity ranges to be barred by the network for incoming communications. The type of barring is chosen by the user at provision time and may be valid for all incoming communications, or be limited to a specific service group or certain conditions (e.g. when the user is roaming).
+
+The ability of the served user to set-up outgoing communications shall be unaffected by ICB.
+
+The ICB service includes a roaming condition. The roaming condition is set to true when the served user is roaming.
+
+The use of ICB on a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.
+
+- ICB enhancement of dynamic blocking of incoming communications
+
+As a service option, the dynamic blocking of incoming communications service facilitates either or both of the following:
+
+- A terminating users register of unwanted callers within the network for barring future incoming communications from the unwanted callers either permanently or for a temporary period or for a maximum lifetime which is set by the network operator. As an option, an additional "dynamic block list" may be provided, which is different compared to the standard ICB list. If this additional "dynamic block list" is provided, the user shall have the option to activate and deactivate that list independent of the already existing standard ICB list.
+- A terminating user activates barring of spoofed calls either permanently or for a temporary period or for a maximum lifetime which is set by the network operator based on associated spoofed call detection applied to the session originator identity.
+
+The following information shall be stored by the network for dynamic blocking of incoming calls:
+
+**Actual Identity of caller:** This is the network asserted identity of the caller.
+
+**Start and end date for barring:** This specifies the duration of block. If not provided, it implies the caller should be barred permanently or for a maximum lifetime which is set by the network operator.
+
+Additionally, the following information may be provided by the user or spoofed call detection and associated with the actual identity:
+
+- **Reason:** This specifies the reason for blocking or an alias, e.g. "Telemarketer". This field may assist the subscriber to manage their block list
+- **Published Identity of caller:** This may be the actual identity of caller or 'private' or 'anonymous' if the caller has opted for privacy.
+
+NOTE: The unwanted caller may have requested privacy e.g. by subscribing to OIR service which prevents the calling identity being shown to the called user. In these cases the called user may just see "Anonymous" or "Unknown". However the called party can still invoke caller ID blocking since the network knows the true identity of the caller. To facilitate the management of the list of blocked callers, the user may use the reason field to identify the blocked caller.
+
+The network shall never reveal an identity withheld using privacy, OIR, or other mechanisms (i.e. list management must use the published identity).
+
+As an option and subject to the network operator policy, the network shall notify (e.g. announcement) the blocked originating user (unwanted user), that the called user has set an incoming communication barring for his identity.
+
+Subject to the network operator policy, the subscriber may request notification of communication barrings within the network in addition to subscribing to the dynamic blocking of incoming communications service.
+
+NOTE 1: The contents of information received as part of notification for the dynamic blocking of incoming communications, could be the same as the ones, that are registered as part of communication barring.
+
+NOTE 2: Off-line management of the barring list (e.g. via a web page) may be provided as a service option.
+
+NOTE 3: Where required by regulation, this enhanced service may be used to block calls from a previously malicious caller.
+
+## 8.2.10.2 Service interactions with other IMS supplementary services
+
+### 8.2.10.2.1 Diversion services
+
+#### 8.2.10.2.1.1 Communication Forwarding Unconditional (CFU)
+
+If the OCB service has already been activated, a request to activate the communication forwarding unconditional service shall be rejected if the user's communication to the forwarded-to user would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.
+
+If the communication forwarding unconditional service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding unconditional service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding unconditional service..
+
+#### 8.2.10.2.1.2 Communication Forwarding Busy (CFB)
+
+If the OCB service has already been activated, a request to activate the communication forwarding busy service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.
+
+If the communication forwarding busy service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding busy service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding busy service.
+
+#### 8.2.10.2.1.3 Communication Forwarding No Reply (CFNR)
+
+If the OCB service has already been activated, a request to activate the communication forwarding no reply service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.
+
+If the communication forwarding no reply service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding no reply service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding no reply service.
+
+#### 8.2.10.2.1.4 Communication Forwarding on Not Logged-in (CFNL)
+
+If the OCB service has already been activated, a request to activate the communication forwarding no registration service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.
+
+If the communication forwarding on Not Logged-in service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding on Not Logged-in service shall be rejected if the forwarding party's communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding on Not Logged-in service.
+
+#### 8.2.10.2.1.5 Communication Deflection (CD)
+
+If the OCB service has been activated, a request to invoke the communication deflection service shall be rejected if the deflecting party's communication to the deflected-to party would be barred by the OCB service at the time of the invocation attempt of the communication deflection service.
+
+### 8.2.10.3 Interoperability with PSTN/ISDN and CS mobile networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the CB service with mobile CS and PSTN/ISDN Supplementary Service CB and with ODB [6], and vice-versa. The scope of this interworking may result in a limited service capability.
+
+## 8.2.11 Completion of Communications to Busy Subscriber (CCBS)
+
+### 8.2.11.1 Definition
+
+The CCBS service enables originating party, encountering a busy terminating party, to have the communication completed without having to make a new communication attempt when the terminating party becomes free.
+
+When originating party requests the CCBS service, the network will monitor for terminating party becoming free.
+
+When terminating party becomes free then the network will wait a short time in order to allow the resources to be re-used for originating a communication. If the resources are not re-used by terminating party within this time, then the network will automatically inform originating party that terminating party has become free. Originating party can generate the CCBS communication to terminating party.
+
+When originating party accepts the CCBS recall, then the network will automatically generate a CCBS communication to terminating party.
+
+NOTE: A service provided to terminating party which prevents the registration of CCBS requests is outside the scope of the present document.
+
+During CCBS recall, information shall be provided which indicates a CCBS recall. The information provided in the original communication attempt shall be included in the CCBS recall.
+
+This service description is based on the service description described in [E-9].
+
+As a service option, the time to expiry of the CCBS and the terminating party identity may be provided by the network, either at successful activation, or as a result of an interrogation.
+
+## 8.2.11.2 Service interactions with other IMS supplementary services
+
+### 8.2.11.2.1 Identification services
+
+### 8.2.11.2.2 Anonymous Communication Rejection (ACR)
+
+A CCBS recall (from the network to the originating party) resulting from the completion of communications to busy subscribers shall not be rejected due to the application of the ACR service.
+
+Assume the originating party connects to the terminating party and the terminating party activates the ACR service or has activated the ACR service:
+
+- The ACR service is activated by the terminating party after the originating party has activated the completion of communications to busy subscriber service on the terminating party:
+ - If the terminating party activates the ACR service after the originating party has activated the completion of communications to busy subscriber service on the terminating party, then the communication resulting from the completion of communications to busy subscriber service shall be rejected if the originating party has restricted its identity due to the OIR service.
+
+### 8.2.11.2.3 Communication DIVersion (CDIV)
+
+CCBS recalls shall never be diverted. They shall be provided to the original originating party.
+
+CCBS can not be activated on a diverted communication.
+
+### 8.2.11.2.4 Communication Waiting (CW)
+
+NOTE: For a waiting communication, terminating party is not considered as busy.
+
+If the Communication Waiting indication cannot be provided at the terminating party, originating party will receive busy indication and can invoke the CCBS service to terminating party.
+
+CCBS requests in the terminating party's CCBS queue shall only be processed if there are no communications waiting.
+
+### 8.2.11.2.5 Communication HOLD (HOLD)
+
+No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+NOTE 1: When receiving a CCBS communication indication, originating party may invoke the communication hold service in order to make interface resources available for the establishment of the CCBS communication.
+
+NOTE 2: When originating party is busy or CCBS busy and is notified that terminating party is free, invocation of the communication hold service will not result in the CCBS communication being established.
+
+### 8.2.11.2.6 Communication Barring (CB)
+
+The originating party calls the terminating party who is busy, and then the originating party invokes CCBS. If the originating party then invokes OCB before the terminating party becomes free, the CCBS communication may be rejected due to the OCB invocation.
+
+### 8.2.11.2.7 Completion of Communications to Busy Subscriber (CCBS)
+
+A user can be both an "originating party" and a "terminating party" simultaneously, i.e. that user can have activated the CCBS service and have CCBS requests outstanding whilst at the same time that user can be the destination of CCBS requests from other users.
+
+If a user receives a CCBS recall while that terminating party's CCBS queue is being processed, then the CCBS recall shall take priority over the handling of the terminating party's CCBS queue. The handling of CCBS requests activated by this user shall have priority over the handling of CCBS requests activated by other users on this user.
+
+If one of the user's CCBS requests matures as a result, then the user shall be provided a CCBS recall or notification. The terminating party idle guard timer, if running, shall be cancelled.
+
+#### 8.2.11.2.8 Advice Of Charge services (AOC)
+
+Charging information can be provided for the original communication, and for the resulting CCBS communication.
+
+#### 8.2.11.2.9 Enhanced Calling Name (eCNAM)
+
+The originating party's eCNAM identity data shall be delivered to the CCBS customer's UE when the terminating party becomes free and a CCBS communication is generated to the terminating party.
+
+If the terminating party has subscribed to or invoked OIR, the originating party's eCNAM identity data shall not be delivered to the originating party.
+
+### 8.2.11.3 Interoperability with PSTN/ISDN
+
+The IMS Multimedia Telephony service shall support the interoperability of the CCBS service with PSTN/ISDN Supplementary Service CCBS and vice-versa. The scope of this interworking may result in a limited service capability.
+
+## 8.2.12 Message Waiting Indication (MWI)
+
+### 8.2.12.1 Definition
+
+The MWI service enables the network, upon the request of a controlling user to indicate to the receiving user, that there is at least one message waiting. The indication is sent to the receiving user when a message is deposited. Optionally, the network may send an indication to the user that there are no more unread message in the mail box. This indication may be send when the last unread message is read.
+
+NOTE: As an example, a voice message is stored by the network for a particular user. The network then provides the MWI to the user to indicate there is a message for retrieval. Having received this indication, the receiving user can subsequently access the mail box, to listen to the message.
+
+The means by which the receiving user accesses and manages the mail box voice message service are outside the scope of the present document.
+
+This service description is based on the service description described in [E-13].
+
+### 8.2.12.2 Service interactions with other services
+
+#### 8.2.12.2.1 Diversion services
+
+##### 8.2.12.2.1.1 Communication Forwarding Unconditional (CFU)
+
+The MWI shall never be diverted.
+
+##### 8.2.12.2.1.2 Communication Forwarding Busy (CFB)
+
+Same as CFU.
+
+##### 8.2.12.2.1.3 Communication Forwarding No Reply (CFNR)
+
+Same as CFU.
+
+##### 8.2.12.2.1.4 Communication Forwarding on Not Logged-in (CFNL)
+
+The MWI shall never be diverted. The indication shall be provided to the owning identity on re-registering.
+
+### 8.2.12.3 Interoperability with PSTN/ISDN and CS mobile networks
+
+There is no interoperability with mobile CS and PSTN/ISDN because MWI is a local service.
+
+## 8.2.13 CONFerence (CONF)
+
+### 8.2.13.1 Definition
+
+The CONF service enables a user to participate in and control a simultaneous communication involving a number of users.
+
+When the CONF service is invoked, conference resources are allocated to the served user.
+
+Once a conference is active, users can join and leave a conference, and remote users can be added to or removed from the conference.
+
+This service description is based on the service description described in [E-7] and [E-8].
+
+Conference participants can request to be informed of these actions. This information can include details beyond that described in [E-7] and [E-8], about other participants including their identity.
+
+The use of CONF on an emergency call, or a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.
+
+### 8.2.13.2 Service interactions with other IMS supplementary services
+
+#### 8.2.13.2.1 Diversion services
+
+No impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.
+
+#### 8.2.13.2.2 CONFerence (CONF)
+
+A user can be involved as the conference controller separately in more than one conference. However, the user cannot add any conference to another conference.
+
+The CONFerence service shall provide a similar user experience as the circuit switched Multiparty supplementary service but with multimedia capabilities.
+
+#### 8.2.13.2.3 Advice Of Charge services (AOC)
+
+No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service. Communication diversion.
+
+NOTE: Every communication within the CONF service may be charged according to the normal communication procedures. Special arrangements (e.g. conference initiator may be charged for other parties' communications in the conference) are out of scope of the present specification.
+
+#### 8.2.13.2.4 Originating Identification Restriction (OIR)
+
+The OIR service shall take precedence as required in [4].
+
+NOTE: A conference participant joining with an active OIR therefore has no details that can be included in any conference notifications.
+
+#### 8.2.13.2.5 Terminating Identification Restriction (TIR)
+
+The TIR service shall take precedence as required in [4].
+
+NOTE: A conference participant added with an active TIR therefore has no details that can be included in any conference notifications.
+
+#### 8.2.13.2.6 Three-Party (3PTY)
+
+See clause 8.2.13.2.2, noting that 3PTY is a special case of CONF.
+
+#### 8.2.13.3 Interoperability with PSTN/ISDN and CS Mobile networks
+
+The IMS Multimedia Telephony service shall support the interoperability of the CONF service with mobile CS and PSTN/ISDN Supplementary Services and vice-versa. The scope of this interworking may result in a limited service capability.
+
+### 8.2.14 Advice Of Charge (AOC)
+
+#### 8.2.14.1 Definition
+
+AOC is a group of services as follows:
+
+- Advice Of Charge: charging information at communication Set-up time (AOC-S);
+
+The advice of charge at communication set-up service provides the user with information about the charging rates at the time of communication establishment or during the communication in the case of charging rates changes. The charge information provided relates to the charges incurred on the network to which the served user is attached.
+
+This service description is based on the service description described in [E-10] for AoC-S on a permanent mode.
+
+- Advice Of Charge: charging information During the communication (AOC-D);
+
+The advice of charge during the communication service enables the user to receive information on the recorded charges for a communication during the active phase of the communication. The provided charging information may be exchanged between different operator domain if those operators have interconnect agreements to do so.
+
+This service description is based on the service description described in [E-11] for AoC-S on a permanent mode.
+
+- Advice Of Charge: charging information at the End of the communication (AOC-E)
+
+The advice of charge at end of communication service provides the user with charging information for a communication when the communication is terminated. Dependent on the option chosen at the time of subscription, the information can be sent for all communications, or on a per communication basis. The charge information provided relates to the charges incurred on the network to which the served user is attached.
+
+This service description is based on the service description described in [E-12] for AoC-S on a permanent mode.
+
+#### 8.2.14.2 Service interactions with other IMS supplementary services
+
+##### 8.2.14.2.1 Diversion services
+
+Originating party: No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+Forwarding party: When a communication is forwarded and the forwarding party is charged for the forwarded part of the communication, then as a network option, the charging information can be transferred to the forwarding user when the communication is terminated.
+
+##### 8.2.14.2.2 Completion of Communications to Busy Subscriber (CCBS)
+
+Charging information shall be provided for the original communication, and for the resulting CCBS communication.
+
+##### 8.2.14.2.3 CONFerence (CONF)
+
+No impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.
+
+### 8.2.14.3 Interoperability with PSTN/ISDN
+
+The IMS shall support the interoperability of the AOC service with PSTN/ISDN Supplementary Services and vice-versa. The scope of this interworking may result in a limited service capability.
+
+## 8.2.15 Explicit Communication Transfer (ECT)
+
+### 8.2.15.1 Definition
+
+The Explicit Communication Transfer (ECT) service enables a party involved in a communication to transfer that communication to a third party.
+
+There are two situations in which transfer shall be possible:
+
+- The transferring party has no ongoing communication with the transfer Target (ECT Blind/Assured) then either:
+ - a) the transferring party wants to perform the transfer without any further action on the transfer operation (ECT Blind),
+ - b) the transferring party wants to have the possibility to act on the transfer operation progress (ECT Assured).
+- The transferring party has a communication with the transfer Target (ECT Consultative).
+
+#### **ECT Blind/Assured:**
+
+The ECT Blind/Assured enables the transferring party A who has an active communication with a party B, which can be an incoming or outgoing communication, to transfer that communication into a new communication between party B and a third party C without having prior communication with the third party C, and release itself from the communication.
+
+Because of the blind call towards party C, it is not possible to know in advance the result of the transfer. Therefore, party A should be informed of the establishment state of the transfer before being released from the communication.
+
+For Assured transfer, the transferring party A can limit the duration of the transfer attempt, release the transfer before it is completed or retrieve its communication with the transferee in case of transfer failure.
+
+#### **ECT Consultative:**
+
+The ECT Consultative enables a transferring party A to transform two of that party's communications (e.g. an active communication and a communication on hold, to parties B and C), each of which can be an incoming communication or an outgoing communication, into a new communication between party B and party C.
+
+Prior to transfer, the media session shall have been established on the communication between transferring party A and party B (transferee). On the communication between transferring party A and party C (transfer target), the media session shall have been established prior to transfer.
+
+The service should be applicable independent of whether party B and party C are IMS users or not.
+
+This service description is based on the service description described in [E-18].
+
+The use of ECT on an emergency call, or a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.
+
+### 8.2.15.2 Service interactions with other IMS supplementary services
+
+#### 8.2.15.2.1 Identification services
+
+##### 8.2.15.2.1.1 Terminating Identification Restriction (TIR)
+
+A terminating party's restriction requirements from the original communication shall be used in order to restrict the presentation of that party's identity to the other user in a transferred communication.
+
+NOTE: If the media flow(s) is established on the communication to party C after transfer, the presentation of the identity of party C shall be restricted according to party C's Terminating identification restriction service (i.e. as for the normal operation of the Terminating identification restriction service).
+
+#### 8.2.15.2.1.2 Originating Identification Presentation (OIP)
+
+For ECT Blind, the transferee identity shall be presented to the transfer target subject to the transferee's originating identification restriction service.
+
+The transferring party identity may also be presented to the transfer target based on operator policy and terminal capability and subject to the transferring party's originating identification restriction service.
+
+#### 8.2.15.2.1.3 Enhanced Calling Name (eCNAM)
+
+The transferee eCNAM identity data shall be delivered to the transfer target subject to the transferee's originating identification restriction service, and assuming the transfer target has eCNAM service.
+
+The transferring party eCNAM identity data may also be delivered to the transfer target based on operator policy and terminal capability and subject to the transferring party's originating identification restriction service.
+
+#### 8.2.15.2.2 Communication Barring (CB)
+
+In case the transferring party A has outgoing communication barring active towards party C, transferring party A's request for communication transfer of party B to party C shall also be barred, if it occurs in relation to the establishment of the communication to C.
+
+For ECT Blind, if the transfer target has incoming communication barring active, the transferee identity shall be checked to apply the service restriction. The transferring party identity may also be checked with Communication Barring based on operator policy.
+
+#### 8.2.15.2.3 CONFerence (CONF)
+
+The conference controller cannot transfer the conference to another party.
+
+NOTE: Conferees can invoke the ECT service in order to transfer their connection to the conference to another party after that connection has been established.
+
+#### 8.2.15.2.4 Advice Of Charge (AOC)
+
+##### 8.2.15.2.4.0 General
+
+This service does not apply to UE accessing from mobile 3GPP access networks.
+
+##### 8.2.15.2.4.1 Advice Of Charge at communication Set-up (AOC-S)
+
+When party A transfers a communication, AOC-S shall be considered as completed.
+
+For party B and party C, no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+##### 8.2.15.2.4.2 Advice Of Charge During the communication (AOC-D)
+
+When party A transfers a communication and has activated AOC-D, the charge up to that time shall be sent as a subtotal charge for that communication. The AOC-D service shall then be considered as completed.
+
+NOTE: If party A had activated the AOC-D, then party A will receive information separately for both of the communications.
+
+For party B and party C, no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.15.2.4.3 Advice Of Charge at the End of a communication (AOC-E)
+
+If a party A is charged for the transferred part of the communication and has activated the AOC-E, then either:
+
+- a) the charging information shall be sent to party A when the transferred communication is terminated; or
+- b) when the communications are transferred, party A shall be informed that charging information is not available. The AOC-E shall then be considered as completed.
+
+For party B and party C, no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
+
+#### 8.2.15.2.5 Explicit Communication Transfer (ECT)
+
+The ECT service can be invoked simultaneously by any of the parties on an active communication, but this is not regarded as a normal situation. The network shall not explicitly prevent this occurring.
+
+Therefore, both parties (party A and party B) in a normal communication, who have each subscribed to the ECT service, can simultaneously transfer the communication. That is, if party A and party B are involved in a communication on which the connection has been established, party A can transfer the communication to party C and party B can transfer the communication to another party.
+
+**NOTE:** Mechanisms which prevent the ECT service from resulting in a connection which contains no parties able to terminate the communication may result in rejection of simultaneous requests to invoke the ECT service by the parties involved in the communication.
+
+#### 8.2.15.3 Interoperability with PSTN/ISDN and CS mobile networks
+
+No restrictions.
+
+### 8.2.16 Reverse charging
+
+#### 8.2.16.1 Definition
+
+The reverse charging at communication set up time service allows the terminating party to be charged for the entire communication. Only usage based charges can be applied to the terminating party. The service shall be requested by the originating party at communication set up time. The terminating party must receive an explicit indication of a reverse charge communication request.
+
+This service description is based on the service description described in [E-19].
+
+#### 8.2.16.2 Service interactions with other IMS supplementary services
+
+None.
+
+#### 8.2.16.3 Interoperability with PSTN/ISDN
+
+The IMS Multimedia Telephony service shall support the interoperability of Reverse Charging with the PSTN/ISDN and vice-versa.
+
+### 8.2.17 Closed User Group (CUG)
+
+#### 8.2.17.1 Definition
+
+The CUG service enables users to form groups of members, whose communication profile is restricted for incoming and outgoing communications. Members of a specific CUG can communicate among themselves but not, in general, with users outside the group.
+
+Specific CUG members can have additional capabilities that allow them to initiate outgoing communications to users outside the group, and/or to accept incoming communications from users outside the group. Specific CUG members can
+
+have additional restrictions that prevent outgoing communications to other members of the CUG, or prevent incoming communications from other members of the CUG.
+
+A closed user group consists of a number of members from one or more public, and/or private networks. Identification of each member shall be according to the requirements in [8]. A specific user may be a member of one or more CUGs. Subscription to a closed user group shall be defined for all communication services, or in relation to one, or to a list of communication services.
+
+This service description is based on the ISDN service description described in [E-22].
+
+## 8.2.17.2 Service interactions with other IMS supplementary services
+
+### 8.2.17.2.1 Diversion services
+
+#### 8.2.17.2.1.1 Communication Forwarding Unconditional (CFU)
+
+CUG restrictions shall be checked and met for the communication between the originating party and the forwarding party. The information of a CUG applied by the IMS Multimedia Telephony service on the original communication shall be used for the communication forwarding and by this means CUG restrictions shall be checked and met for the communication between the originating party and the forwarded-to party.
+
+In the case of multiple forwarding, CUG restrictions between the originating party and the forwarding party have to be checked and met at each intermediate forwarding point. In addition, CUG restrictions between the originating party and forwarded-to party shall be met end-to-end.
+
+The outgoing communication barring information of the forwarding party shall not be used to determine whether the communication can be forwarded.
+
+The CUG information sent to the "forwarded-to" destination shall be the same CUG information of the originating party that was sent from the originating network.
+
+#### 8.2.17.2.1.2 Communication Forwarding Busy (CFB)
+
+See interactions with CFU 8.2.17.2.1.1
+
+#### 8.2.17.2.1.3 Call Forwarding No Reply (CFNR)
+
+See interactions with CFU 8.2.17.2.1.1
+
+NOTE: CUG restrictions were checked and met for the communication between the originating party and the forwarding party when the communication was offered to the forwarding party.
+
+#### 8.2.17.2.1.4 Communication Forwarding on Not Logged-in (CFNL)
+
+See interactions with CFU 8.2.17.2.1.1
+
+#### 8.2.17.2.1.5 Communication Forwarding on Subscriber Not Reachable (CFNRc).
+
+See interactions with CFU 8.2.17.2.1.1
+
+#### 8.2.17.2.1.6 Communication Deflection (CD)
+
+The information of a CUG applied on the original communication shall be used for the deflected part of the communication and by this means CUG restrictions shall be checked and met for the communication between the originating party and the deflected-to party.
+
+In the case of multiple deflections, CUG restrictions between the originating party and the deflecting party have to be checked and met at each intermediate deflecting point. In addition, CUG restrictions between the originating party and deflected-to party shall be met end-to-end.
+
+When a communication is deflected, a new check of the CUG restrictions between the originating party and the deflected-to party is made at the "deflected-to" destination. The CUG information sent to the "deflected-to" destination is the same CUG information of the originating party that was sent from the originating network.
+
+The outgoing communication barring information of the deflecting party shall not be used to determine whether the communication can be deflected.
+
+NOTE: CUG restrictions were checked and met for the communication between the originating party and the deflecting party when the communication was offered to the deflecting party.
+
+#### 8.2.17.2.2 Explicit Communication Transfer (ECT)
+
+The two communications shall use the same CUG for the transfer to be successful.
+
+NOTE: CUG restrictions between users will have been checked when the first communication is established. Similarly, CUG restrictions between users will have been checked when establishing the second communication.
+
+#### 8.2.17.2.3 Three-Party (3PTY)
+
+For the successful invocation of the three party service any CUG restrictions applied to one communication shall match with any CUG restrictions applied to the other communication.
+
+#### 8.2.17.2.4 CONFerence (CONF)
+
+When the communication involving the first conferee is added to the conference, then the conference shall assume the CUG of that communication.
+
+In order to add a subsequent communication to the conference, then the CUG of that communication shall be checked against the CUG of the conference.
+
+#### 8.2.17.3 Interoperability with PSTN/ISDN
+
+The IMS Multimedia Telephony service shall support the interoperability of the CUG service with the PSTN/ISDN and vice versa. No restrictions.
+
+### 8.2.18 Three-Party (3PTY)
+
+#### 8.2.18.1 Definition
+
+The 3PTY service enables a user to establish, participate in and control a simultaneous communication involving a number of users.
+
+The 3PTY service can be invoked by the served user who is involved in at least two calls (one active communication and at least one held communication), each of which may be an incoming or outgoing communication.
+
+The connections shall be established on each of the two communications prior to the invocation of the 3PTY service.
+
+3PTY communication setup is equivalent to a three party conference created on request of the served user from existing communication sessions, this is equivalent to three party conference creation in CONF, For this reason 3PTY can be seen as a special case of CONF and most of service interactions for CONF apply also to 3PTY.
+
+This service description is based on the service description described in [E-21].
+
+#### 8.2.18.2 Service interactions with other IMS supplementary services
+
+##### 8.2.18.2.1 Terminating Identification Presentation (OIR)
+
+See clause 8.2.13.2.4, noting that 3PTY is a special case of CONF.
+
+##### 8.2.18.2.2 Terminating Identification Restriction (TIR)
+
+See clause 8.2.13.2.5, noting that 3PTY is a special case of CONF.
+
+### 8.2.18.2.3 Three-Party (3PTY)
+
+A, B and C are in a three-way conversation that was created by B invoking the 3PTY service. A can create a second three-way conversation involving the original three-way conversation and D by invoking the 3PTY service.
+
+### 8.2.18.2.4 CONFerence (CONF)
+
+A, B and C are involved in a conference that was created by B invoking the CONF service. A can create a three-way conversation involving the original conference call and D by invoking the 3PTY service.
+
+NOTE: It is FFS whether there is a conflict with the requirement expressed by 8.2.13.2.2, considering that 3PTY is just a special case of CONF.
+
+### 8.2.18.3 Interoperability with PSTN/ISDN
+
+The IMS Multimedia Telephony service shall support the interoperability of the 3PTY service with PSTN/ISDN supplementary service 3PTY and vice-versa. The scope of this interworking may result in a limited service capability.
+
+## 8.2.19 Flexible Alerting (FA)
+
+### 8.2.19.1 Definition
+
+Flexible Alerting (FA) causes a call to a Pilot Identity to branch the call into several legs to alert several FA group members simultaneously or sequentially. In the simultaneous case, the first leg to be answered is connected to the calling party and the other call legs are abandoned. In the sequential case the order in which legs are alerted depends on application-specific criteria (including static preferences, last used device, last registered device).
+
+FA group members are alerted by dialling the public addressable identity (e.g. Public User Identity) associated with the FA group (i.e., a E.164 number or a SIP URI), which is referred to as the Pilot Identity. The Pilot Identity maps to a set of public addressable identities (e.g. PUI or GRUU) where each identity references a member of the FA group. The FA group consists of a list of identities, and can be configured by the user or the operator.
+
+In FA, there are two configuration options for busy indication: Single User Busy, and Multiple User Busy. The configuration of the option for a particular FA group shall be performed by the operator.
+
+- For Single User Busy, the FA Group returns a busy indication if any group member indicates busy before the call is answered.
+- For Multiple User Busy, the FA Group returns a busy indication if all accessible members indicate busy.
+
+### 8.2.19.2 Service interactions with other IMS supplementary services
+
+#### 8.2.19.2.1 Identification services
+
+##### 8.2.19.2.1.1 Terminating Identification Presentation (TIP)
+
+If an originating call from a user has TIP activated, the termination identification is the FA Pilot Identity.
+
+##### 8.2.19.2.1.2 Terminating Identification Restriction (TIR)
+
+If the FA Pilot Identity has TIR activated, the termination identification is not presented.
+
+##### 8.2.19.2.1.3 Originating Identification Presentation (OIP)
+
+If the FA Pilot Identity has OIP activated, incoming calls to the FA Pilot Identity apply OIP to the members of the FA group.
+
+##### 8.2.19.2.1.4 Originating Identification Restriction (OIR)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+## 8.2.19.2.2 Diversion services
+
+### 8.2.19.2.2.1 Communication Forwarding Unconditional (CFU)
+
+CFU takes precedence over FA. CFU of the FA Pilot Identity shall apply to calls to the Pilot Identity when CFU is active.
+
+CFU for the FA pilot identity takes precedence over CFU of the individual FA members. That is, if both the FA pilot identity and an FA member have CFU active, CFU treatment is determined by the FA pilot identity.
+
+### 8.2.19.2.2.2 Communication Forwarding Busy (CFB)
+
+CFB of the FA Pilot Identity shall apply to calls to the Pilot Identity when CFB is active and the FA group is considered to be busy.
+
+CFB for the FA pilot identity takes precedence over CFB of the individual FA members. That is, if both the FA pilot identity and an FA member have CFB active, CFB treatment is determined by the FA pilot identity.
+
+## 8.2.20 Personal Network Management (PNM)
+
+### 8.2.20.1 Definition
+
+Personal Network Management (PNM) as specified in TS22.259 allows a user to manage her UEs in regard to terminating services according to preferences set by the user, capabilities and availabilities of devices.
+
+NOTE: Fixed network terminals could become subject of PNM
+
+### 8.2.20.2 Service interactions with other IMS supplementary services
+
+Invocation of supplementary services for terminating services applicable to the active UE take precedence over invocation of supplementary service applicable to the called UE. There is no impact on specified interaction among supplementary services once invoked.
+
+There is no impact on the registration, erasure, activation, deactivation and interrogation of supplementary services.
+
+## 8.2.21 Customized Alerting Tone (CAT)
+
+### 8.2.21.1 Definition
+
+The Customized Alerting Tone Service (CAT service) is an operator specific service by which an operator enables the subscriber to customize the alerting tone which is played to the calling party. The requirements for CAT within IMS shall be as described in [9].
+
+### 8.2.21.2 Service interactions with other IMS supplementary services
+
+#### 8.2.21.2.1 Identification services
+
+##### 8.2.21.2.1.1 Originating Identification Restriction (OIR)
+
+The interaction between CAT and the OIR supplementary services shall be as described in [9].
+
+##### 8.2.21.2.1.2 Terminating Identification Restriction (TIR)
+
+The interaction between CAT and the TIR supplementary services shall be as described in [9].
+
+#### 8.2.21.2.2 Diversion services
+
+##### 8.2.21.2.2.1 Communication Forwarding Unconditional (CFU)
+
+The interaction between CAT and the CFU supplementary services shall be as described in [9].
+
+##### 8.2.21.2.2.2 Communication Forwarding Busy (CFB)
+
+The interaction between CAT and the CFU supplementary services shall be as described in [9].
+
+##### 8.2.21.2.2.3 Communication Forwarding on Not Reachable (CFNRc)
+
+The interaction between CAT and the CFNRc supplementary services shall be as described in [9].
+
+##### 8.2.21.2.2.4 Communication Forwarding No Reply (CFNR)
+
+The interaction between CAT and the CFNR supplementary services shall be as described in [9].
+
+#### 8.2.21.2.3 Communication Waiting (CW)
+
+The interaction between CAT and the CW supplementary services shall be as described in [9].
+
+#### 8.2.21.2.4 Explicit Communication Transfer (ECT)
+
+The interaction between CAT and the ECT supplementary services shall be as described in [9].
+
+### 8.2.22 Customized Ringing Signal (CRS)
+
+#### 8.2.22.1 Definition
+
+The Customized Ringing Signal (CRS service) is an operator specific service by which an operator enables the subscriber to customize the ringing signal which is played to the called party. The requirements for CRS within IMS shall be as described in [10].
+
+#### 8.2.22.2 Service interactions with other IMS supplementary services
+
+##### 8.2.22.2.1 Identification services
+
+###### 8.2.22.2.1.1 Originating Identification Restriction (OIR)
+
+The interaction between CRS and the OIR supplementary services shall be as described in [10].
+
+###### 8.2.22.2.1.2 Originating Identification Presentation (OIP)
+
+The interaction between CRS and the OIP supplementary services shall be as described in [10].
+
+##### 8.2.22.2.2 Diversion services
+
+###### 8.2.22.2.2.1 Communication Forwarding Unconditional (CFU)
+
+The interaction between CRS and the CFU supplementary services shall be as described in [10].
+
+###### 8.2.22.2.2.2 Communication Forwarding Busy (CFB)
+
+The interaction between CRS and the CFU supplementary services shall be as described in [10].
+
+#### 8.2.22.2.2.3 Communication Forwarding on Not Reachable (CFNRc)
+
+The interaction between CRS and the CFNRc supplementary services shall be as described in [10]
+
+#### 8.2.22.2.2.4 Communication Forwarding No Reply (CFNR)
+
+The interaction between CRS and the CFNR supplementary services shall be as described in [10]
+
+#### 8.2.22.2.3 Communication Waiting (CW)
+
+The interaction between CRS and the CW supplementary services shall be as described in [10].
+
+#### 8.2.22.2.4 Explicit Communication Transfer (ECT)
+
+The interaction between CRS and the ECT supplementary services shall be as described in [10].
+
+### 8.2.23 Completion of Communications on No Reply (CCNR)
+
+#### 8.2.23.1 Definition
+
+The CCNR service enables the originating party, encountering a terminating party who does not answer the communication (No Reply), to have the communication completed without having to make a new communication attempt when the terminating party becomes not busy after having initiated an activity.
+
+When the originating party requests the CCNR service, the network will monitor for the terminating party becoming not busy after having initiated an activity.
+
+When the terminating party becomes not busy after having initiated an activity, then the network will wait a short time in order to allow the resources to be re-used for originating a communication. If the resources are not re-used by the terminating party within this time, then the network will automatically recall the originating party.
+
+When the originating party accepts the CCNR recall, then the network will automatically generate a CCNR call to the terminating party.
+
+NOTE: A service provided to the terminating party which prevents the registration of CCNR requests is outside the scope of the present document.
+
+During CCNR recall, information shall be provided which indicates a CCNR recall. The information provided in the original communication attempt shall be included in the CCNR recall.
+
+This service description is based on the service description described in [E-23].
+
+#### 8.2.23.2 Service interactions with other IMS supplementary services
+
+##### 8.2.23.2.1 Identification services
+
+###### 8.2.23.2.1.1 Originating Identification Presentation (OIP)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+NOTE: If the originating party accepts a CCNR recall, the resulting CCNR call is a basic communication and the terminating party can receive originating identification presentation.
+
+###### 8.2.23.2.1.2 Originating Identification Restriction (OIR)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+NOTE: If the originating party has invoked originating identification restriction and the terminating party accepts a CCNR recall, then the resulting CCNR call is a basic communication and the terminating party will not receive the originating identification of the originating party.
+
+#### 8.2.23.2.1.3 Terminating Identification Presentation (TIP)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.1.4 Terminating Identification Restriction (TIR)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.2 Advice Of Charge services (AOC)
+
+Charging information can be given for the original communication, and for the resulting CCNR communication.
+
+#### 8.2.23.2.3 Communication Waiting (CW)
+
+CCNR requests in the CCNR queue of the terminating party shall only be processed if there are no communications waiting. In other situations there is no impact between the CW and the CCNR service.
+
+#### 8.2.23.2.4 Communication HOLD (HOLD)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+NOTE 1: When receiving a CCNR recall indication, the originating party may invoke the communication hold service in order to make interface resources available for the establishment of the CCNR communication.
+
+NOTE 2: When the originating party is busy or CCNR busy and is notified that the terminating party is not busy, invocation of the communication hold service will not result in the CCNR communication being established.
+
+#### 8.2.23.2.5 Explicit Communication Transfer (ECT)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.6 Closed User Group (CUG)
+
+Closed user group information from the original communication shall also be included in the CCNR communication.
+
+NOTE: Closed user group information is not included in the check for a compatible terminal. If a terminal performs an internal closed user group check and uses the closed user group information provided on a communication to determine whether, or not, to inform the user of the incoming communication, then such a terminal may react positively to the check for a compatible terminal due to the absence of closed user group information, but due to the internal closed user group check such a terminal may then not inform the user of the arrival of the resulting CCNR call.
+
+#### 8.2.23.2.7 Completion of communications services
+
+##### 8.2.23.2.7.1 Completion of Communications to Busy Subscriber (CCBS)
+
+A user can be both an originating party and a terminating party simultaneously, i.e. that user can have activated the CCNR service or the completion of communications to busy subscriber (CCBS) service and have CCNR requests or CCBS requests outstanding whilst at the same time that user can be the destination of CCNR requests or CCBS requests from other users.
+
+CCBS requests and CCNR requests against the same terminating party shall be queued in the same queue.
+
+If a user receives a CCNR recall or CCBS recall (i.e. as originating party) while that user's queue as terminating party is being processed, then the CCNR recall or CCBS recall shall take priority over the handling of that user's queue. The handling of CCNR requests and CCBS requests activated by this user (i.e. as originating party) shall have priority over the handling of CCNR requests and CCBS requests activated by other users on this user (i.e. as terminating party).
+
+If one of the user's CCNR requests can be processed, then this user (see first paragraph) shall be given a CCNR recall or notification as described in [E-23] clause 5. The served user's terminating party idle guard timer, if running, shall be cancelled. The processing of CCBS requests shall be according to the requirements of the CCBS supplementary service.
+
+If a network supports the option to retain CCNR requests (see [E-23] clause 5.3.3.1 b)), then CCBS requests shall be retained when a CCBS call encounters a busy destination.
+
+If the network checks for identical requests in the user's queue, the check shall include both CCNR requests and CCBS requests.
+
+If an originating party has a CCBS recall pending on arrival of a CCNR recall, this should be treated in the same way as in the case where the originating party is CCNR busy (see [E-23] clause 5.2.3 and clause 5.3.3.2 b)).
+
+#### 8.2.23.2.7.2 Completion of Communications on No Reply (CCNR)
+
+A user can be both a originating party and a terminating party simultaneously, i.e. that user can have activated the CCNR service and have CCNR requests outstanding whilst at the same time that user can be the destination of CCNR requests from other users.
+
+If a user receives a CCNR recall while that user's CCNR queue as terminating party is being processed, then the CCNR recall shall take priority over the handling of the CCNR queue. The handling of CCNR requests activated by this user shall have priority over the handling of CCNR requests activated by other users on this user.
+
+If one of the user's CCNR requests can be processed as a result, then this user (see first paragraph) shall be given a CCNR recall or notification as described in [E-23] clause 5. The served user's terminating party idle guard timer, if running, shall be cancelled.
+
+#### 8.2.23.2.8 CONFerence (CONF)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+#### 8.2.23.2.9 Communication DIVersion (CDIV)
+
+##### 8.2.23.2.9.1 General
+
+CCNR recalls shall not be diverted. They shall be given to the originating party at the originating party's original location.
+
+##### 8.2.23.2.9.2 Communication Forwarding Unconditional (CFU)
+
+For CFU activated by user B before user A requests CCNR:
+
+- If user B has activated CFU, and the forwarded communication results in a communication completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C. If user A activates CCNR and subsequently activates CFU, the CCNR recall shall be given to user A at his original location.
+As a network option, in case of a diversion at user B, user A shall not be informed that CCNR is possible.
+
+For CFU activated by user B after user A requests CCNR on user B:
+
+- If user B activates CFU after user A has activated CCNR on user B, then the CCNR request shall be cancelled and a notification "CCNR cancelled" shall be sent to the user A.
+As a network option, the CCNR request shall be suspended until user B deactivates CFU. If the service duration timer expires before user B deactivates CFU, the CCNR request shall be cancelled.
+
+##### 8.2.23.2.9.3 Communication Forwarding Busy (CFB)
+
+For CFB activated by user B before user A requests CCNR:
+
+- If user B has activated the communication forwarding busy service and is busy, and the forwarded communication results in a call-completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C.
+
+For CFB activated by user B after user A requests CCNR on user B:
+
+- If user B activates the communication forwarding busy service after user A has activated the CCNR service on user B, the communication forwarding busy service shall not be invoked for the CCNR communication.
+
+#### 8.2.23.2.9.4 Communication Forwarding No Reply (CFNR)
+
+For CFNR activated by user B before user A requests CCNR:
+
+- If user B has activated the communication forwarding on no reply service and does not answer the communication, and the forwarded communication results in a communication-completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C.
+As a network option, user A shall be informed that CCNR at user B is possible.
+
+For CFNR activated by user B after user A requests CCNR on user B:
+
+- If user B activates the communication forwarding on no reply service after user A has activated the communication forwarding on no reply service on user B, a CCNR communication from user A which encounters a no reply condition at user B shall be treated as follows:
+ - the procedures of CCNR shall be applied; or
+ - the communication shall be forwarded as a normal communication.
+
+#### 8.2.23.2.9.5 Communication Forwarding on Not Logged in (CFNL)
+
+For CFNL activated by user B before user A requests CCNR:
+
+- If user B has activated the communication forwarding not registered service and is not logged in, and the forwarded communication results in a communication completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C.
+As a network option, user A shall be informed that CCNR at user B is possible.
+
+For CFNL activated by user B after user A requests CCNR on user B:
+
+- If user B activates the communication forwarding not registered service after user A has activated CCNR on user B, then the CC request shall be cancelled and a notification "CCNR cancelled" shall be sent to the user A.
+As a network option, the CCNR request shall be suspended until user B deactivates CFNL. If the service duration timer expires before user B deactivates CFNL, the CCNR request shall be cancelled.
+
+#### 8.2.23.2.9.6 Communication Deflection (CD)
+
+For the originating user A:
+
+- If a communication to the called user B is deflected to user C by the CD service and results in a communication completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C. A CCNR recall shall not be deflected.
+
+For the called user B:
+
+- A CCNR call shall not be deflected.
+
+#### 8.2.23.2.10 Malicious Communication IDentification (MCID)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.11 Anonymous Communication Rejection and Communication Barring (ACR/CB)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.12 Message Waiting Indication (MWI)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.13 Flexible Alerting (FA)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2.23.2.14 Customized Alerting Tones (CAT)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+### 8.2.23.3 Interoperability with PSTN/ISDN
+
+The IMS Multimedia Telephony service shall support the interoperability of the CCNR service with PSTN/ISDN Supplementary Service CCNR and vice-versa. The scope of this interworking may result in a limited service capability.
+
+## 8.2.24 Enhanced Calling Name (eCNAM)
+
+### 8.2.24.1 Definition and Scope
+
+The eCNAM service [15] provides the terminating party with the eCNAM identity data of the originating party. The eCNAM identity data consists of a name and metadata. This service is available to a user only after subscription.
+
+NOTE: The size of the eCNAM identity data can be up to 1000 characters.
+
+The eCNAM service informs and protects terminating users from fraud attempts (e.g., fraudulent robocalls) through its retrieval, assembly and delivery of the call metadata together with the results of the Caller Identity Analytics function (defined in Section 3.1).
+
+The Caller Identity Analytics function is expected to encompass the results of verification, such as the Secure Telephone Identity Revisited (STIR) [16] / Signature-based Handling of Asserted information using toKENs (SHAKEN) [17].
+
+The eCNAM service combines its metadata and the results of the Caller Identity Analytics function so that the end user receives an all-inclusive display of the pertinent call information. As a result, the end user receives the eCNAM metadata, authentication and verification mechanisms, and the outcome of the Caller Identity Analytics in the same eCNAM message.
+
+### 8.2.24.2 Service Requirements and Functionality
+
+The terminating service provider shall extract the originating party's telephone number from the originating party identity (e.g., from the tel-URI) to use in its query to retrieve eCNAM identity data from an authoritative data source. eCNAM identity data includes any information that allows the recipient to identify or contact the calling party, including the telephone number, name, logo.
+
+The terminating service provider shall ensure that the received calling number is verified.
+
+If the terminating service provider determines that the originating party's telephone number is verified and OIR is not invoked, the terminating service provider shall retrieve the originating party's eCNAM identity data.
+
+If the originating party's telephone number cannot be obtained, eCNAM identity data may not be available and the terminating service provider shall indicate the unavailability of the eCNAM identity data to the terminating party.
+
+If the originating party's telephone number cannot be verified, eCNAM identity data may not be displayed to the user. However, subject to service provider policy, the results of the Caller Identity Analytics function – if available - shall be included in the eCNAM message delivered to the UE.
+
+The interface between the terminating service provider (eCNAM service) and the Caller Identity Analytics function shall be private and secure.
+
+NOTE 1: The Caller Identity Analytics function is expected to have information (e.g., statistical and reputation) about the caller and/or the call that could be useful to the user. Therefore, even in the absence of a verification service, the delivery of this analytics information can protect the user against fraud and help service providers meet their regulatory obligations.
+
+The terminating service provider shall obtain the eCNAM identity data from a trusted source. This trusted source may be the originating service provider or a third party with a business arrangement with the originating service provider.
+
+The interface between the terminating service provider and the trusted data source shall be private and secure.
+
+The conditions for exchange of data are governed by regional regulatory administration and through service provider agreement.
+
+The terminating service provider's delivery of originating party's eCNAM identity data to the terminating party shall be subject to Originating Identification Restrictions (OIR).
+
+If a terminating service provider requests a data element that the originating party did not consent to releasing, the data element shall not be returned.
+
+NOTE 2: A trusted source contains subscriber identity information that is obtained directly from the subscriber's communications service record, and is updated in near-real time with any changes in the subscriber's service record. A subscriber's communications service record is created when the user starts service with the service provider. The record contains information such as the name, address, billing information.
+
+The service provider shall obtain its subscribers' consent for elements listed on the subscriber's communications service record at the start of communications service, and allow the subscriber to modify his/her consent at any point during the service.
+
+NOTE 3: The metadata is intended to provide additional identity information about the originating party to the terminating party. The originating party's privacy is a primary factor determining presentation of his/her metadata to the terminating party; no identity information is presented without his/her consent. Examples of the metadata include: the postal code, the preferred language, the business name and the business segment. The metadata delivered can vary from one service provider to another. The metadata offered by each service provider is subject to expansion and modifications over time, as more data or updated data becomes available about the originating party.
+
+For the eCNAM service, the originating and terminating service providers shall agree on the retrievable metadata with the originating party's consent based on regional regulations.
+
+The eCNAM service shall support a service provider policy to establish the priority of delivering the identity data received from eCNAM query results and originating party identity data over any other data received from the originating party.
+
+NOTE 4: OIP and eCNAM have the same level of priority.
+
+3GPP systems shall support the delivery of the eCNAM identity data in multiple languages (e.g., Chinese). Semantic translation is outside the scope of this standard.
+
+3GPP systems shall relay the eCNAM identity data from the trusted sources to the terminating party without modification.
+
+NOTE 5: The purpose of the preceding two requirements is to deliver eCNAM in more languages, such as Chinese. However, this does not require the storage of the eCNAM data in multiple languages in the databases.
+
+### 8.2.24.3 Service interactions with other IMS supplementary services
+
+#### 8.2.24.3.1 Identification Services
+
+##### 8.2.24.3.1.1 Originating Identification Presentation (OIP)
+
+For users that subscribe to both OIP and eCNAM, both originating party identity and eCNAM identity data shall be delivered to the terminating party.
+
+##### 8.2.24.3.1.2 Originating Identification Restriction (OIR)
+
+The requirements for presenting and withholding the originating party's eCNAM identity data shall adhere to the rules described in [4] for the presentation of session originator identity.
+
+If the originating party subscribed to or invokes OIR, eCNAM identity data shall not be delivered to the terminating party, including data elements that the originating party had consented to release.
+
+Non-identifying information generated by the Caller Identity Analytics function to alert the user against possible fraud (e.g., "Known Scam") can be delivered to the user on calls from anonymous (private) callers. It is therefore possible for the user to receive a display such as:
+
+Private Number... "Known Scam"
+
+#### 8.2.24.3.2 Diversion Services
+
+##### 8.2.24.3.2.1 Communication Forwarding Unconditional (CFU)
+
+When a communication has been forwarded and the forwarded-to party has been provided with the eCNAM service, the forwarded-to party shall receive the eCNAM identity data of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+##### 8.2.24.3.2.2 Communication Forwarding Busy (CFB)
+
+Same as CFU.
+
+##### 8.2.24.3.2.3 Communication Forwarding No Reply (CFNR)
+
+Same as CFU.
+
+##### 8.2.24.3.2.4 Communication Forwarding on Not Logged-in (CFNL)
+
+Same as CFU.
+
+##### 8.2.24.3.2.5 Communication Deflection (CD)
+
+When a communication has been deflected and the deflected-to party has been provided with the eCNAM service, the deflected-to party shall receive the eCNAM identity data of the original originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+##### 8.2.24.3.2.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)
+
+Same as CFU.
+
+#### 8.2.24.3.3 Communication Waiting (CW)
+
+If a terminating party has the eCNAM service active and is notified that an incoming communication is waiting, then this terminating party shall receive the eCNAM identity data of the originating party, if this originating party has not subscribed to or invoked the OIR service.
+
+#### 8.2.24.3.4 Completion of Communication to Busy Subscriber (CCBS)
+
+The originating party's eCNAM identity shall be transmitted to the CCBS customer's UE when the terminating party becomes free and a CCBS communication is generated to the terminating party.
+
+If the terminating party subscribed to or has invoked OIR, the terminating party eCNAM identity data shall not be delivered to the originating party.
+
+#### 8.2.24.3.5 Explicit Communication Transfer (ECT)
+
+The transferee's eCNAM identity data shall be delivered to the transfer target subject to the transferee's OIR, and assuming the transfer target has eCNAM active.
+
+The transferring party eCNAM identity data may also be delivered to the transfer target based on operator policy and terminal capability and subject to the transferring party's OIR.
+
+#### 8.2.24.4 Interoperability with PSTN/ISDN and mobile CS services
+
+The IMS Multimedia Telephony service shall support the interoperability of the eCNAM service with mobile CS and PSTN/ISDN Supplementary Service CLIP. The eCNAM service shall utilize only the calling number originating from the PSTN to obtain the originating party's eCNAM identity data.
+
+eCNAM is not offered in the PSTN.
+
+### 8.2A Supplementary Services applicable to IMS Multimedia Telephony without equivalent in non-IMS networks
+
+#### 8.2A.1 Completion of Communications on Not Logged-in (CCNL)
+
+##### 8.2A.1.1 Definition
+
+The CCNL service enables the originating party, encountering a terminating party who is not registered, to have the communication completed without having to make a new communication attempt when the terminating party registers again.
+
+When the originating party requests the CCNL service, the network will monitor for the terminating party registering again.
+
+As a service provider option only originating parties who are listed in the terminating party's whitelist are allowed to request the CCNL service.
+
+NOTE: The administration of the terminating party's whitelist is out of scope of this document.
+
+When the terminating party registers again, then the network will wait a short time in order to allow the terminating party to originate a communication. If no communication is originated by the terminating party within this time, then the network will automatically recall the originating party. As a service provider option the terminating user's acceptance of the CCNL request shall be required before the originating party will be recalled. When the originating party accepts the CCNL recall, then the network will automatically generate a CCNL call to the terminating party.
+
+When the terminating party is busy or not logged-in upon arrival of the CCNL call, the original CCNL request shall retain its position in the queue, and the remaining period in which the CCNL request remains valid shall not be changed by this event.
+
+During CCNL recall, information shall be provided which indicates a CCNL recall. The information provided in the original communication attempt shall be included in the CCNL recall.
+
+##### 8.2A.1.2 Service interactions with other IMS supplementary services
+
+###### 8.2A.1.2.1 Identification services
+
+###### 8.2A.1.2.1.1 Originating Identification Presentation (OIP)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+NOTE: If the originating party accepts a CCNL recall, the resulting CCNL call is a basic communication and the terminating party can receive originating identification presentation.
+
+###### 8.2A.1.2.1.2 Originating Identification Restriction (OIR)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+NOTE: If the originating party has invoked originating identification restriction and the terminating party accepts a CCNL recall, then the resulting CCNL call is a basic communication and the terminating party will not receive the originating identification of the originating party.
+
+#### 8.2A.1.2.1.3 Terminating Identification Presentation (TIP)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.1.4 Terminating Identification Restriction (TIR)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.2 Advice Of Charge services (AOC)
+
+Charging information can be given for the original communication, and for the resulting CCNL communication.
+
+#### 8.2A.1.2.3 Communication Waiting (CW)
+
+CCNL requests in the CCNL queue of the terminating party shall only be processed if there are no communications waiting. In other situations there is no impact between the CW and the CCNL service.
+
+#### 8.2A.1.2.4 Communication HOLD (HOLD)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+NOTE 1: When receiving a CCNL recall indication, the originating party may invoke the communication hold service in order to make interface resources available for the establishment of the CCNL communication.
+
+NOTE 2: When the originating party is busy or CCNL busy and is notified that the terminating party is available, invocation of the communication hold service will not result in the CCNL communication being established.
+
+#### 8.2A.1.2.5 Explicit Communication Transfer (ECT)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.6 Closed User Group (CUG)
+
+Closed user group information from the original communication shall also be included in the CCNL communication.
+
+NOTE: Closed user group information is not included in the check for a compatible terminal. If a terminal performs an internal closed user group check and uses the closed user group information provided on a communication to determine whether, or not, to inform the user of the incoming communication, then such a terminal may react positively to the check for a compatible terminal due to the absence of closed user group information, but due to the internal closed user group check such a terminal may then not inform the user of the arrival of the resulting CCNL call.
+
+#### 8.2A.1.2.7 Completion of communications services (CC)
+
+The following Completion of Communications services are defined: Completion of Communications to Busy Subscriber (CCBS), Completion of Communications on No Reply (CCNR) and Completion of Communications on Not Logged-in (CCNL)
+
+A user can be both an originating party and a terminating party simultaneously, i.e. that user can have activated CC services and have CC requests outstanding whilst at the same time that user can be the destination of CC requests from other users.
+
+CC requests against the same terminating party shall be queued in the same queue.
+
+If a user receives a CCNL recall (i.e. as originating party) while that user's queue as terminating party is being processed, then the CCNL recall shall take priority over the handling of that user's queue. The handling of CCNL requests activated by this user (i.e. as originating party) shall have priority over the handling of CC requests activated by other users on this user (i.e. as terminating party).
+
+If one of the user's CCNL requests can be processed, then this user shall be given a CCNL recall or a notification. The served user's terminating party idle guard timer, if running, shall be cancelled. The processing of CCBS or CCNR requests shall be according to the requirements of the CCBS or CCNR supplementary services.
+
+If the network checks for identical requests in the user's queue, the check shall include CCNL, CCNR and CCBS requests.
+
+If an originating party has a CCBS or CCNR recall pending on arrival of a CCNL recall, this should be treated in the same way as in the case where the originating party is CCNL busy. In this case, the CCNL request shall be suspended until user A becomes neither busy nor CCNL busy.
+
+#### 8.2A.1.2.8 CONFerence (CONF)
+
+No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
+
+#### 8.2A.1.2.9 Communication DIVersion (CDIV)
+
+##### 8.2A.1.2.9.1 General
+
+CCNL recalls shall not be diverted.
+
+##### 8.2A.1.2.9.2 Communication Forwarding Unconditional (CFU)
+
+For CFU activated by user B before user A requests CCNL:
+
+- If user B has activated CFU, and the forwarded communication results in a communication completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C. If user A activates CCNL and subsequently activates CFU, the CCNL recall shall be given to user A.
+As a network option, in case of a diversion at user B, user A shall not be informed that CCNL is possible.
+
+For CFU activated by user B after user A requests CCNL on user B:
+
+- If user B activates CFU after user A has activated CCNL on user B, then the CCNL request shall be cancelled and a notification "CCNL cancelled" shall be sent to the user A.
+As a network option, the CCNL request shall be suspended until user B deactivates CFU. If the service duration timer e2Apires before user B deactivates CFU, the CCNL request shall be cancelled.
+
+##### 8.2A.1.2.9.3 Communication Forwarding Busy (CFB)
+
+For CFB activated by user B before user A requests CCNL:
+
+- If user B has activated the communication forwarding busy service and is busy, and the forwarded communication results in a call-completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C.
+As a network option, in case of a diversion at user B, user A shall not be informed that CCNL is possible.
+
+For CFB activated by user B after user A requests CCNL on user B:
+
+- If user B activates the communication forwarding busy service after user A has activated the CCNL service on user B, the communication forwarding busy service shall not be invoked for the CCNL communication.
+
+##### 8.2A.1.2.9.4 Communication Forwarding No Reply (CFNR)
+
+For CFNR activated by user B before user A requests CCNL:
+
+- If user B has activated the communication forwarding on no reply service and does not answer the communication, and the forwarded communication results in a communication-completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C.
+As a network option, in case of a diversion at user B, user A shall not be informed that CCNL is possible.
+
+For CFNR activated by user B after user A requests CCNL on user B:
+
+- If user B activates the communication forwarding on no reply service after user A has activated CCNL on user B, then the CCNL request shall be cancelled and a notification "CCNL cancelled" shall be sent to the user A. As a network option, the CCNL request shall be suspended until user B deactivates CFNR. If the service duration timer e2Apire before user B deactivates CFNR, the CCNL request shall be cancelled.
+
+#### 8.2A.1.2.9.5 Communication Forwarding on Not Logged in (CFNL)
+
+For CFNL activated by user B before user A requests CCNL:
+
+- If user B has activated the communication forwarding not registered service and is not logged in, and the forwarded communication results in a communication completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C. As a network option, user A shall be informed that CCNL at user B is possible.
+
+For CFNL activated by user B after user A requests CCNL on user B:
+
+- If user B activates the communication forwarding not registered service after user A has activated the communication forwarding on not logged-in service on user B, a CCNL communication from user A which encounters a not logged in condition at user B shall be treated as follows:
+ - the procedures of CCNL shall be applied; or
+ - the communication shall be forwarded as a normal communication.
+
+#### 8.2A.1.2.9.6 Communication Deflection (CD)
+
+For the originating user A:
+
+- If a communication to the called user B is deflected to user C by the CD service and results in a communication completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C. A CCNL recall shall not be deflected.
+
+For the called user B:
+
+- A CCNL call shall not be deflected.
+
+#### 8.2A.1.2.10 Malicious Communication Identification (MCID)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.11 Anonymous Communication Rejection and Communication Barring (ACR/CB)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.12 Message Waiting Indication (MWI)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.13 Flexible Alerting (FA)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+#### 8.2A.1.2.14 Customized Alerting Tones (CAT)
+
+No impact, i.e. neither service shall affect the operation of the other service.
+
+### 8.2A.1.3 Interoperability with PSTN/ISDN
+
+Not applicable.
+
+## 8.3 Concepts associated with IMS supplementary services
+
+### 8.3.1 Administration of supplementary services
+
+Provision, Withdrawal, Registration, Erasure, Activation, Deactivation and Invocation shall be as defined in ITU-T Recommendation I.210 [5].
+
+Users shall be able to register, activate, deactivate, withdraw, interrogate and reconfigure IMS supplementary services via the UE, or web portals.
+
+### 8.3.2 Unstructured SS data operations
+
+The Multimedia Telephony Service shall provide a consistent service experience to the user for mobile initiated USSD operations in MMI mode and reserved for HPLMN use, according to TS 22.090 [12].
+
+### 8.3.3 Network Announcement and Tones Insertion
+
+The Multimedia Telephony Service shall be able to play network announcements or tones to the subscriber at any time during a session.
+
+If there is an appropriate bilateral agreement, the home network shall be able to instruct the visited network to play a network announcement or tone to the subscriber at any time during a session.
+
+When the UE locally renders the supervisory tones, the UE should follow the procedure indicated in Annex A.2 applicable for the home operator network of the UE in particular within a mobile network. The UE shall not locally render tones to indicate diversion or queueing of calls.
+
+## 8.4 Use of authorization option in relation to IMS supplementary services
+
+### 8.4.1 Definition
+
+Some IMS supplementary services (e.g. communication session barring) can be offered to a user with the subscription option of authorization to control the service. When this option is selected, every action (related to that IMS supplementary service), such as registration, erasure, activation or deactivation is performed by the user with concurrent authentication.
+
+For IMS supplementary services requiring authorization by user authentication, the service experience for the user shall be consistent with the procedures defined in TS 22.030 [14] for password based supplementary service management.
+
+### 8.4.2 Description
+
+When the subscription option authorized control of a IMS supplementary service is provided, authentication handling is supported by the network.
+
+### 8.4.3 Management - normal procedures and successful outcome
+
+#### 8.4.3.1 Provision of authorization
+
+Each IMS supplementary service which requires authorization to control this service may be offered with the subscription option authorized control of the IMS supplementary service. The values of this option may be:
+
+- user authentication;
+- by the service provider.
+
+#### 8.4.3.2 Withdrawal of authorization
+
+Authorization may be withdrawn for administrative reasons or due to subscription modification.
+
+#### 8.4.3.3 Authentication requirements
+
+The network shall provide, and allow the user to maintain, the authentication credentials.
+
+---
+
+## 9 IMS Multimedia Telephony with Enhanced Voice
+
+The IMS Multimedia Telephony with Enhanced Voice should fulfill the following requirements:.
+
+- IMS Multimedia Telephony with Enhanced Voice should allow for significantly improved quality of user experience compared to IMS Multimedia Telephony with pre-Rel-12 voice services.
+- It should be possible to achieve significantly better service quality than is possible with both Rel-11 3GPP narrowband and wideband voice services.
+- IMS Multimedia Telephony with Enhanced Voice should be deployable in an efficient manner.
+- IMS Multimedia Telephony with Enhanced Voice should efficiently use the transmission resource access and transport networks. It should also allow possibility to implement the new services on low-cost devices and network equipment with limited computational resource. With regard to transmission efficiency, it should exceed that of the pre-Rel-12 3GPP wideband voice service.
+- Transcoding should be avoided as much as possible. If transcoding cannot be avoided, voice conversational quality degradation should be as limited as possible.
+- The best possible quality should be delivered to all participants in conference calls.
+
+---
+
+## Annex A (informative): General terminal guidelines
+
+### A.1 Service state indication
+
+It is considered useful to indicate to the user the current state, notably the activated state of those services which can lead to communications not being offered. For example, an active CFU results in no communication being presented.
+
+Generally speaking any "not usual" state of a service should be indicated on the terminal: CFU activated, CW deactivated, OIR in permanent mode activated, etc.
+
+In the case of services which can be remotely controlled from another terminal or a server, the terminal should receive this information from the network.
+
+### A.2 Supervisory tones
+
+TS 22.001 [13] Annex F provides details of supervisory tones generated by the ME.
+
+---
+
+## Annex B (informative): Service interactions table
+
+Table B.1 summarizes the service interactions between pairs of IMS supplementary services, as identified in section 8 of this document.
+
+Each case of the table represents the scenario where services on the horizontal row heading are invoked when services on the vertical column heading are already active.
+
+The case is filled with one of three possible options: character "Y" indicates interaction has been identified between the corresponding service pair and described in the present document, character "N" indicates no interaction has been identified and no information is provided in the present document, '-' is for scenarios which are not applicable.
+
+Table B.1: Identified service interactions between pairs of IMS supplementary services
+
+| | OIP | OIR | eCNAM | TIP | TIR | MI D | AC | CFU | CFB | CFNR | CFNL | CD | CFNRc | CW | HOLD | CB | CCBS | MWI | CONF | AOC | ECT | RC | CUG | 3PTY |
+|--------------------------------------------------------------|-----|-----|-------|-----|-----|------|----|-----|----------|------|------|----|-------|----------|------|----|------|-----|------|-----|-----|----|-----|------|
+| Originating Identification Presentation (OIP) | - | Y | Y | N | N | N | Y | Y | Y | Y | Y | Y | Y | Y | N | N | N | N | N | N | N | N | N | N |
+| Originating Identification Restriction (OIR) | Y | - | Y | N | N | N | Y | Y | Y | Y | Y | Y | Y | N | N | N | N | N | N | N | N | N | N | N |
+| Enhanced CNAM (eCNAM) | Y | Y | - | N | N | N | N | Y | Y | Y | Y | Y | Y | Y | N | N | Y | N | N | N | Y | N | N | N |
+| Terminating Identification Presentation (TIP) | N | N | N | - | Y | N | N | Y | Y | Y | Y | Y | Y | N | N | N | N | N | N | N | N | N | N | N |
+| Terminating Identification Restriction (TIR) | N | N | N | Y | - | N | N | Y | N | N | N | N | N | N | N | N | N | N | N | N | Y | N | N | N |
+| Malicious Communication Identification (MCID) | N | N | N | N | N | - | N | Y | N | Y | N | Y | Y | N | N | N | N | N | N | N | N | N | N | N |
+| Anonymous Communication Rejection (ACR) | N | N | N | N | N | N | - | Y | Y | Y | Y | N | Y | Y | N | N | Y | N | N | N | N | N | N | N |
+| Communication Forwarding Unconditional (CFU) | Y | Y | Y | Y | N | N | Y | - | Y | Y | Y | Y | Y | N | N | Y | Y | Y | N | Y | N | N | Y | N |
+| Communication Forwarding Busy (CFB) | Y | Y | Y | Y | N | N | Y | Y | - | N | N | Y | Y | see note | N | Y | Y | Y | N | Y | N | N | Y | N |
+| Communication Forwarding No Reply (CFNR) | Y | Y | Y | Y | N | Y | Y | Y | N | - | N | N | N | Y | N | Y | Y | Y | N | Y | N | N | Y | N |
+| Communication Forwarding on Not Logged-In (CFNL) | Y | Y | Y | Y | N | N | Y | Y | N | N | - | N | N | N | N | Y | Y | Y | N | Y | N | N | Y | N |
+| Communication Deflection (CD) | Y | Y | Y | Y | N | Y | Y | Y | Y | N | N | - | N | Y | N | Y | Y | Y | N | Y | N | N | Y | N |
+| Communication Forwarding on Subscriber Not Reachable (CFNRc) | Y | Y | Y | Y | N | Y | Y | Y | Y | N | N | N | - | Y | N | Y | Y | Y | N | N | N | N | Y | N |
+| Communication Waiting (CW) | Y | N | Y | N | N | N | Y | N | see note | Y | N | Y | Y | - | N | N | Y | N | N | N | N | N | N | N |
+| Communication Hold (HOLD) | N | N | N | N | N | N | N | N | N | N | N | N | N | N | - | N | N | N | N | N | N | N | N | Y |
+| Communication Barring (CB) | N | N | N | N | N | N | N | Y | Y | Y | Y | Y | Y | N | N | - | Y | N | N | N | Y | N | N | N |
+| Completion of Communications to Busy Subscriber (CCBS) | N | N | Y | N | N | N | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | N | N | Y | N | N | N | N |
+| Message Waiting Indication (MWI) | N | N | N | N | N | N | N | Y | Y | Y | Y | N | Y | N | N | N | N | - | N | N | N | N | N | N |
+| Conference (CONF) | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | Y | Y | Y | N | Y | N |
+
+| | OI P | OI R | eCNAM | TI P | TI R | MI D | AC | CFU | CFB | CFNR | CFNL | CD | CFNRc | CW | HOLD | CB | CCBS | MMI | CONF | AOC | ECT | RC | CUG | 3PTY |
+|---------------------------------------|------|------|-------|------|------|------|----|-----|-----|------|------|----|-------|----|------|----|------|-----|------|-----|-----|----|-----|------|
+| Advice of Charge (AOC) | N | N | N | N | N | N | N | Y | Y | Y | Y | Y | N | N | N | N | Y | N | Y | - | N | N | N | N |
+| Explicit Communication Transfer (ECT) | N | Y | Y | N | N | Y | N | N | N | N | N | N | N | N | N | Y | N | N | Y | Y | Y | N | Y | N |
+| Reverse Charging (RC) | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | - | N | N |
+| Closed User Group (CUG) | N | N | N | N | N | N | N | Y | Y | Y | Y | Y | Y | N | N | N | N | N | Y | N | Y | N | - | N |
+| Three-Party (3PTY) | N | N | N | N | N | N | N | N | N | N | N | N | N | N | Y | N | N | N | N | N | N | N | Y | Y |
+
+NOTE: It is not permitted to have both CW and CFB active at the same time for a particular user.
+
+---
+
+## Annex C (normative): IMS Multimedia Telephony supplementary services applicable to the fixed access
+
+The following services have been split into 3 categories applicable to CEPT members:
+
+- Mandatory services: selected services that must form the basis of any set of services considered applicable to IMS Multimedia Telephony service. These are considered to meet the requirements of regulation concerning the processing of personal data and the protection of privacy in the electronic communications sector.
+- Recommended services: selected services that offer service providers with a transition from CS mobile and fixed services to IMS Multimedia Telephony service.
+- Optional services: other services.
+
+### Mandatory services
+
+Originating Identification Presentation (OIP)
+Originating Identification Restriction (OIR)
+Terminating Identification Presentation (TIP)
+Terminating Identification Restriction (TIR)
+Malicious Communication Identification (MCID)
+Anonymous Communication Rejection (ACR)
+
+### Recommended services
+
+Communication Diversion (CDIV)
+Communication Waiting (CW)
+Communication HOLD (HOLD)
+Communication Barring (CB)
+Completion of Communications to Busy Subscriber (CCBS)
+Completion of Communications on No Reply (CCNR)
+Message Waiting Indication (MWI)
+
+### Optional services
+
+CONFerence (CONF)
+Advice Of Charge (AOC)
+Explicit Communication Transfer (ECT)
+Reverse charging
+Closed User Group (CUG)
+Three-Party (3PTY)
+Flexible Alerting (FA)
+Customized Alerting Tone (CAT)
+Customized Ringing Signal (CRS)
+
+Completion of Communications on Not Logged in (CCNL)
+
+---
+
+## Annex D (normative): IMS Multimedia Telephony supplementary services applicable to the mobile 3GPP access
+
+Only these services apply to UEs using a mobile 3GPP access:
+
+Originating Identification Presentation (OIP)
+
+Originating Identification Restriction (OIR)
+
+Terminating Identification Presentation (TIP)
+
+Terminating Identification Restriction (TIR)
+
+Communication Diversion (CDIV)
+
+Communication Hold (HOLD)
+
+Communication Barring (CB)
+
+Message Waiting Indication (MWI)
+
+Conference (CONF)
+
+Explicit Communication Transfer (ECT)
+
+Completion of Communications on Not Logged in (CCNL)
+
+Communication Waiting (CW)
+
+NOTE: Communication Waiting service may be provided entirely by means of an equivalent feature in the UE. In this case this service does not need to be supported by the network.
+
+Completion of Communications to Busy Subscriber (CCBS)
+
+Completion of Communications on No Reply (CCNR)
+
+Personal Network Management (PNM)
+
+Customized Alerting Tone (CAT)
+
+Customized Ringing Signal (CRS)
+
+Additionally, EN 301 082 (OCB-fixed) does not apply to 2G and 3G Mobile terminals, for which the functionality is specified by means of Operator Determined Barring [6] and not through supplementary services.
+
+---
+
+## Annex Da (normative): Network determined user busy.
+
+The capability of network determined user busy is a network option.
+
+The network may determine busy conditions at the time an incoming IMS Multimedia Telephony session is about to be offered.
+
+The conditions for network determined user busy are identified, on a per subscription basis, based on the availability of limited resources assigned to the terminating user, or due to other information such as presence.
+
+The conditions for network determined "user busy" include:
+
+- the maximum number of total communications permitted has been reached;
+- the maximum number of simultaneous media streams supported at the given subscriber's interface(s) has been reached;
+- the maximum bandwidth supported at the given subscriber's interface(s) has been reached.
+- subscriber making himself "busy" in a subscriber profile, involved in the incoming multimedia telephony session.
+
+The network determined user busy condition may be used to trigger certain services (e.g. Call Forwarding on Busy, Call Waiting on Busy), or reject the session, or both. If the session rejection is propagated back to the originator, a "user busy" indication must be provided as the cause of the rejection.
+
+In addition, a further condition, "approaching network determined user busy" that is related to the Network determined user busy condition, may be provided. This condition may be used to trigger certain services (e.g. Call Waiting). However, this condition is not a busy condition and shall not cause a "user busy" indication being sent towards the session originator.
+
+The conditions for approaching network determined user busy are identified, on a per subscription basis, based on the availability of limited resources assigned to the terminating user.
+
+The conditions for approaching network determined user busy include:
+
+- a pre-determined number, or less, of communications are available (i.e. the maximum number of communications minus the current number); or
+- a pre-determined number, or less, of simultaneous media streams available (i.e. the maximum number of simultaneous media streams minus the current number); or
+- a certain limit in the bandwidth used at the given subscriber's interface(s) has been reached.
+
+---
+
+## Annex Db (informative): services classification applicable to Inter IMS Network-to-Network Interface (II-NNI).
+
+The goal of this informative annex is to improve the service interconnection at II-NNI. The classification of services may simplify the cooperation between interconnecting networks but remains optional.
+
+### Db.1 High Priority Category
+
+List of services with high priority to be supported at II-NNI (it is recommended to be able to deliver these services at II-NNI). These services have technical impact the II-NNI:
+
+- Basic Voice,
+- Originating Identification Presentation (OIP),
+- Originating Identification Restriction (OIR),
+- Incoming Communication Barring (ICB) – including Anonymous Communication Rejection (ACR),
+- Advice Of Charge (AOC),
+- Communication DIVersion (CDIV) – Call DIV signaling information saying that this call has been already diverted.
+- Malicious Communication Identification (MCID),
+- Communication HOLD (HOLD),
+- Communication Waiting (CW).
+
+### Db.2 Medium Priority Category
+
+List of services with medium priority to be supported at II-NNI (it is recommended that interconnecting parties agree on using these services before planning to open them at II-NNI). These services have technical impact the II-NNI:
+
+- Terminating Identification Presentation (TIP),
+- Terminating Identification Restriction (TIR),
+- Message Waiting Indication (MWI),
+- Completion of Communications to Busy Subscriber (CCBS),
+- Completion of Communications on Non Reply (CCNR),
+- Explicit Communication Transfer (ECT),
+- Closed User Group (CUG),
+- Personal Network Management (PNM),
+- Three-ParTY (3PTY),
+- CONFerence (CONF),
+- User to User service.
+
+## Db.3 Low Priority Category
+
+List of services with low priority that have no identified impact on II-NNI (the delivery of these services is inside of originating network):
+
+- Flexible Alerting (FA),
+- Outgoing Communication Barring (OCB),
+- Customized Alerting Tone (CAT),
+- Customized Ringing Signal (CRS)
+- Call Completion Not Logged In (CCNL).
+
+---
+
+# Annex Dc (normative): Enterprise IP-PBX Supplementary Services to support 3GPP Voice Interworking
+
+## Dc.1 General
+
+The services in this annex are the services that could be supported in an enterprise IP-PBX environment. These are provided in order to support implementation of interworking between an Enterprise IP-PBX and IMS. 3GPP UEs that are designed to work in an Enterprise environment could support these types of supplementary services.
+
+## Dc.2 Individual Line Services
+
+### Dc.2.1 Introduction
+
+IP-PBX features are generally classified as either Individual Line or Group Line Services. Individual Line services are applicable to individual Enterprise users (aka "lines" or "extensions"). Group Services, in contrast, are applicable to groups of users.
+
+### Dc.2.2 Call Transfer (Unattended, Attended & Early Attended)
+
+This is based on Explicit Communications Transfer (ECT) as described in Section 8.2.15.
+
+In a Unattended Call Transfer, an ongoing call is transferred to a 3rd party by one of the parties (called the transferring party) without checking the status of the 3rd party. This is supported as a service provider option of ECT in Section 8.2.15.
+
+In an attended call transfer (sometimes called Supervised Call Transfer) the ongoing call is placed on hold by the transferring party, another call is established between the transferring party and the party to whom the call is proposed to be transferred, and then the call is (or may be, depending on the result of that discussion) transferred to that party. This is effectively a combination of the Communication HOLD service defined in section 8.2.9 and ECT defined in Section 8.2.15.
+
+In an Early Attended Call Transfer the ongoing call is placed on hold and the transferring party waits to hear the 3rd party's phone ring. Once the transferring party hears ring tone, he transfers the call. This is supported as a service provider option of ECT in Section 8.2.15.
+
+### Dc.2.3 Multi-party Ad-hoc Conference with Rosters
+
+Multi-party and Conference Calls provide communications between multiple users. Such calls may or may not be arranged in advance. Multi-party calls not arranged in advance are termed "ad hoc".
+
+Conference calls generally involve multiple parties, so the terms *multi-party call* and *conference call* are in some senses synonymous. Conventionally, the term *conference call* refers to a call that is arranged in advance by a moderator or host who has special privileges (e.g., can mute and un-mute other participants), with logistics communicated e.g., through email or a calendar system. To participate in a conference call one typically calls a number associated with a conferencing server.
+
+An Ad Hoc Multi-party call is usually not pre-arranged and participants are generally all "equal" (they can mute and un-mute themselves). There may or may not be a conferencing server involved.
+
+The list of participants in a multi-party / conference call is known as the roster. The IP-PBX may have the ability to supply the roster to the device of any participant.
+
+## Dc.2.4 Call Forwarding
+
+Call Forwarding, or Communications Diversion (CDIV), is defined in Section 8.2.7. Call Forwarding Activation is an action on the part of the user to change the call forwarding behaviour of his device; e.g., by activating or deactivating forwarding to a pre-designated number, or changing the forwarded to number.
+
+Call forwarding (aka Communications Diversion or CDIV) is provided to incoming calls based on the called party's status and service configuration. It may be invoked for the reasons summarized below. Call forwarding for other reasons is not precluded, as a network option.
+
+1. Call Forward on Busy - Call Forwarding is invoked because the called party's line is not able to accept the incoming call (e.g., it is in use, or off hook).
+
+This is known as Communication Forwarding Busy (CFB) in Section 8.2.7.1.
+
+2. Call Forward on No Answer - Call Forwarding is invoked after the called party is alerted a configured number of times without response.
+
+This is known as Communication Forward on No Reply (CFNR) in Section 8.2.7.1.
+
+3. Call Forward Unconditional - Call Forwarding is enabled by the user (e.g., prior to leaving the office) so that all subsequent calls will be immediately forwarded to the specified destination. This configuration typically remains in effect until manually cancelled. The forwarded line may indicate that it is in this state by issuing a special dial tone (e.g., "stutter dial tone") when the receiver is taken off hook. Call Forward Unconditional may be invoked using special key sequences (Vertical Service Codes), e.g., \*72 in North America or \*21\* in Europe, followed by the forward-to number; or via a special button or soft key on the device.
+
+This is known as Communication Forwarding Unconditional (CFU) in Section 8.2.7.1.
+
+4. Call Forward on Do Not Disturb - similar to call forward unconditional, but invoked by pressing the Do Not Disturb button or soft key. Most devices will visually display that they are in the Do Not Disturb state. Pressing the Do Not Disturb button or soft key while in the Do Not Disturb state, causes the line to exit this state.
+
+This is known as Communication Deflection (CD) in Section 8.2.7.1.
+
+## Dc.2.5 Single Number Reach (SNR)
+
+The Single Number Reach (SNR) capability allows calls to a IP-PBX extension to be picked up on or transferred to, alternate devices such as a home phone or mobile phone.
+
+In the case of a call incoming to the number associated with the IP-PBX extension, the IP-PBX will normally ring that line first. If it is unanswered, the IP-PBX will ring one or more alternate numbers.
+
+An in-progress call may be "pushed to" a pre-configured alternate device by pressing a special button or key sequence on the device with which the IP-PBX extension number is associated. Similarly it can be "pulled back" to that device.
+
+## Dc.2.6 Do Not Disturb (DND)
+
+The Do Not Disturb (DND) function prevents calls from being terminated to an extension for which DND is activated.
+
+Calls to an extension for which DND is activated may be directed to a pre-assigned extension (e.g., a secretary), receive a busy signal, or receive an indication that the called party is busy. In some IP-PBXs the call may be allowed through to the extension but displayed differently (e.g., with a visual indication, but without ringing). It may be possible to circumvent the called party's DND status by policy (e.g., the called party's boss can "get through") or by entering a circumvention code.
+
+## Dc.2.7 Immediate Divert (to messaging system)
+
+The Immediate Divert function allows a call to be connected to a messaging system (typically a voice mail system). The call may be active, on hold or in the process of being established. The messaging system may be associated with the party invoking the Immediate Divert function or (if they differ) with the original called party. When the call is in the process of being established this is known as Communication Diversion (CDIV) as defined in Section 8.2.7. When the call is active or on hold, this is known as Explicit Communication Transfer (ECT) as defined in Section 8.2.15.
+
+Immediate Divert is invoked by a special key, softkey or key sequence depending on the capability of the device. The IP-PBX typically informs the diverted party that the call has been diverted, and to whose messaging system the diverted party is now speaking.
+
+## Dc.2.8 Shared-line Features (remote-in-use, call-Barge)
+
+A shared line is a telephone number associated with multiple devices at the same time. A set of devices sharing the same number is called a Shared Line Group. This is a variant of the Closed User Group defined in Section 8.2.17. The Call Barge function allows a user to join an in-progress call in which it and one of the currently participating devices are members of the same Shared Line Group.
+
+Call Barge is only possible from device 'A' if at least one device in the same Shared Line Group as 'A' has a call in progress. This status may be indicated to the user of device 'A' by the IP-PBX.
+
+## Dc.2.9 Callback
+
+The Callback function notifies a user when the party to whom a call was previously attempted, becomes available. It is effectively the combination of Communication Completion on Busy (CCBS) and Communication Completion on No Reply (CCNR) defined in Sections 8.2.11 and 8.2.23.
+
+If IP-PBX user 'A' attempts to call IP-PBX user 'B' but the call fails, e.g., because user B's line was busy or the call was unanswered, user 'A' may invoke the Callback function. Doing so causes the IP-PBX to monitor B's status, and notify user A when user B becomes available. For example if B's line was previously off hook, he will be deemed available when he next goes on hook.
+
+## Dc.2.10 Connected Name and Number Display
+
+This feature allows the device to display the name and/or telephone number of both current parties on a 2-party call.
+
+This feature uses the Connected Line ID Presentation (COLP/COLR) and Connected Name Presentation (CONP/CONR) services to allow or restrict presentation of this information on a call by call basis.
+
+This feature requires that the IMS or the IP-PBX maintains the name associated with Enterprise specific identities (short numbers).
+
+## Dc.2.11 Call Whisper
+
+Call Whisper identifies to the called party, information about the caller (e.g., the caller ID, and the telephone number the caller dialed) while the caller continues to hear ringing. This information allows the called party to know how to greet the caller, and/or whether to accept the call. This is an optional service described in section 7.5.1 of TS 22.228 [4].
+
+This capability is often used when multiple non-geographic numbers (e.g., toll free numbers) are used to route calls to the same directory number. For example a call center may take calls for many companies, and the receptionists need to greet the caller differently based on the company to which the call is related. It can also be used in a FMC scenario where e.g., a call to either the fixed or the mobile device will cause both to ring. The implementation will typically translate the called number into a pre-defined phrase (e.g., "this call is for Acme Rockets" or "this call is for your mobile"). The format of the "whisper" may vary (e.g., audio vs. visual presentation) depending on the capabilities of the device.
+
+## Dc.3 Group Line Services
+
+### Dc.3.1 Introduction
+
+A IP-PBX often provides a set of advanced services to groups of users within the Enterprise. The groups generally correspond to job functions (e.g., help desk attendants) or organizations (e.g., marketing, sales). Group Services may for example allow enhanced collaboration among group members, or allow the distribution of work across them.
+
+### Dc.3.2 Enterprise Music On Hold
+
+Music on Hold (MOH) is played to the party whose line has been placed on hold.
+
+The Music on Hold (MOH) feature allows users to place on-net and off-net users on hold with music that is streamed from a streaming source. In an Enterprise MOH is often used to provide information rather than music. The caller may interact with the MOH capability using simple key sequences, e.g., "enter \*0 to hear about our sales, or \*1 to disable this announcement". The announcement may be customized based e.g., on the number dialled. The media is typically streamed from a Music on Hold Server, which may or may not be considered part of the IP-PBX.
+
+This is an add-on to the Communication HOLD service defined in Section 8.2.9. The network should be capable of suppressing MOH when the held party is part of a multi-party call.
+
+### Dc.3.3 Call Park
+
+The Call Park feature allows a party involved in a call to place that call on hold on one device and resume it from another.
+
+Traditionally Call Park has been activated using a special button (the "call park" button) or key sequence. The call is at that point transferred to an idle extension, and is said to be "parked on" that extension. The IP-PBX may provide some means of "paging" the desired party, e.g., through a public address system or via some form of messaging. The call can be resumed from any IP-PBX line, by providing the extension number on which it is "parked".
+
+This is a variation of the Communication HOLD service defined in Section 8.2.9, where the call can be picked up from a different terminal than placed on hold.
+
+### Dc.3.4 Call Pickup/Group Pickup
+
+Call Pickup allows a user to answer on one line or device, an incoming call directed to another line or device. Lines or devices may be assigned to groups, in which case call pickup is restricted to lines or devices in the same group. That is known as Group Pickup.
+
+Imagine a large room with many phones and few people. One of the phones, on the far side of the room, starts to ring. Rather than walking across the room, a user can press a special button or key sequence on his own phone to transfer that call to his phone. That is Call Pickup.
+
+In a distributed environment it may not be possible for the user to hear the other phone ringing, so an alternative alerting mechanism may be used. For example a text message could alert a user on his mobile that his office or home phone was ringing.
+
+---
+
+## Annex E (informative): Bibliography references
+
+In chapter 8 several informative references are given to provide a more complete understanding of the stage 1 definition of the IMS supplementary services developed in this TS.
+
+These references shall be intended as general guidelines given to integrate the service descriptions of this document and are exclusively intended to be applicable in relation to stage 1 aspects. Stage 3 of Multimedia Telephony service is defined exclusively in [7].
+
+- [E-1] ETSI ETS 300 200: "Integrated Services Digital Network (ISDN); Call Forwarding Unconditional (CFU) supplementary service; Service description".
+- [E-2] ETSI EN 300 199 (V1.2.1): "Integrated Services Digital Network (ISDN); Call Forwarding Busy (CFB) supplementary service; Service description".
+- [E-3] ETSI EN 300 201 (V1.2.1): "Integrated Services Digital Network (ISDN); Call Forwarding No Reply (CFNR) supplementary service; Service description".
+- [E-4] ETSI ETS 300 202: "Integrated Services Digital Network (ISDN); Call Deflection (CD) supplementary service; Service description".
+- [E-5] ETSI ETS 300 056: "Integrated Services Digital Network (ISDN); Call Waiting (CW) supplementary service; Service description".
+- [E-6] ETSI ETS 300 139: "Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Service description".
+- [E-7] ETSI ETS 300 183: "Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Service description".
+- [E-8] ETSI ETS 300 164: "Integrated Services Digital Network (ISDN); Meet-Me Conference (MMC) supplementary service; Service description".
+- [E-9] ETSI EN 300 357 (V1.2.1): "Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Service description".
+- [E-10] ETSI ETS 300 178: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information at call set-up time (AOC-S) supplementary service; Service description".
+- [E-11] ETSI ETS 300 179: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information during the call (AOC-D) supplementary service; Service description".
+- [E-12] ETSI ETS 300 180: "Integrated Services Digital Network (ISDN); Advice of Charge: charging information at the end of the call (AOC-E) supplementary service; Service description".
+- [E-13] ETSI EN 300 650 (V1.2.1): "Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI) supplementary service; Service description".
+- [E-14] ETSI EN 301 798 (V1.1.1): "Services and Protocols for Advanced Networks (SPAN); Anonymous Call Rejection (ACR) Supplementary Service; Service description".
+- [E-15] ETSI EN 301 082 (V2.1.1): "Integrated Services Digital Network (ISDN); Outgoing Call Barring-Fixed (OCB-F) supplementary service; Service description".
+- [E-16] ETSI EN 301 084 (V2.1.1): "Integrated Services Digital Network (ISDN); Outgoing Call Barring-User Controlled (OCB-UC) supplementary service; Service description".
+- [E-17] ETSI ETS 300 094 V2.1.1 (2000-06): "Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP); supplementary service; Service description".
+- [E-18] ETSI EN 300 367 V1.2.1 (1998-10): "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Service description".
+- [E-19] ITU-T Recommendation I.256.3 (08/92): "Integrated Services Digital Network (ISDN); general structure and service capabilities; Reverse Charging".
+- [E-20] ETSI ETS 300 095 ed.1 (1992-01): "Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Service description".
+- [E-21] ETSI ETS 300 186 ed.1 (1993-07): "Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Service description".
+- [E-22] ETSI ETS 300 136 (March 1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Service description".
+
+[E-23] ETSI EN 301 134 (October 1998): "Integrated Services Digital Network (ISDN); Completion of Calls on No Reply (CCNR) supplementary service; Service description".
+
+## Annex F (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|------------------------------------------------------------------------------------------------|-------|-------|-------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| 2006-02 | | | 22.173 | | | | | First skeleton | | 0.0.1 | |
+| 2006-02 | | SA1#31 | 22.173 | | | | | Updated with text from TR 22.973 v1.1.0 | 0.0.1 | 0.1.0 | |
+| SP-31 | | | 22.173 | | | | | Agreed to be sent to SA #31 for information | 0.1.0 | 1.0.0 | |
+| 2006-04 | SA1#32 | S1-060549 | 22.173 | | | | | Update at SA1#32, Including S1-060386, S1-060509, S1-060547, S1-060543. | 1.0.0 | 1.1.0 | |
+| 2006-04 | SA1#32 | S1-060628 | 22.173 | | | | | Raised to 2.0.0 for presentation to SA #32 | 1.1.0 | 2.0.0 | |
+| 2006-06 | SP-32 | SP-060310 | 22.173 | - | - | | | Approved at SA #32 | 2.0.0 | 7.0.0 | |
+| 2006-10 | SP-33 | SP-060471 | 22.173 | 0001 | - | | | CR to 22.173 to remove the editor's note in the Conf supplementary service | 7.0.0 | 7.1.0 | MITe |
+| 2006-10 | SP-33 | SP-060471 | 22.173 | 0002 | - | | | Requirements of setting the priority of IMS supplementary services | 7.0.0 | 7.1.0 | MITe |
+| SP-34 | SP-060761 | S1-061400 | 22.173 | 0003 | - | Rel-7 | F | A133-01; removal of requirement to align supplementary service requirements | 7.1.0 | 7.2.0 | MITE |
+| SP-34 | SP-060761 | S1-061436 | 22.173 | 0005 | - | Rel-7 | F | Clarification on media components | 7.1.0 | 7.2.0 | MTSI-REQ |
+| SP-35 | SP-070117 | S1-070250 | 22.173 | 0006 | 1 | Rel-7 | F | Clarification on supplementary services | 7.2.0 | 7.3.0 | MTSI-REQ |
+| SP-37 | SP-070660 | S1-071293 | 22.173 | 0008 | 4 | Rel-8 | B | TISPAN MMTEL R8 for Common IMS | 7.3.0 | 8.0.0 | TISMML-R8 |
+| SP-38 | SP-070846 | S1-071788 | 22.173 | 0011 | 1 | Rel-8 | B | Network determined user busy | 8.0.0 | 8.1.0 | CIMS8-TIS |
+| SP-38 | SP-070847 | S1-071862 | 22.173 | 0010 | 1 | Rel-8 | D | Editorial modifications | 8.0.0 | 8.1.0 | TISMML-R8 |
+| SP-38 | SP-070847 | S1-071865 | 22.173 | 0013 | 3 | Rel-8 | B | Media Handling Interworking | 8.0.0 | 8.1.0 | TMMTEL |
+| SP-39 | SP-080044 | S1-080260 | 22.173 | 0016 | 2 | Rel-8 | B | Flexible Alerting service | 8.1.0 | 8.2.0 | CIMS_3G PP2 |
+| SP-39 | SP-080041 | S1-080179 | 22.173 | 0017 | 1 | Rel-8 | F | Addition of a missing requirement from Rel-7 | 8.1.0 | 8.2.0 | TEI8 |
+| SP-40 | SP-080297 | S1-080586 | 22.173 | 0019 | 1 | Rel-8 | A | Adding and removing media during a multimedia service session | 8.2.0 | 8.3.0 | TEI7 |
+| SP-40 | SP-080307 | S1-080757 | 22.173 | 0020 | 3 | Rel-8 | F | Clarifications on media interworking for IMS Multimedia telephony | 8.2.0 | 8.3.0 | MMTEL-R8 |
+| SP-41 | SP-080496 | S1-082407 | 22.173 | 0021 | 2 | Rel-8 | D | Editorial modifications | 8.3.0 | 8.4.0 | TEI8 |
+| SP-42 | SP-080770 | S1-083188 | 22.173 | 0032 | 1 | Rel-8 | F | retrieval the settings of IMS supplementary services | 8.4.0 | 8.5.0 | TEI8 |
+| SP-42 | SP-080770 | S1-084422 | 22.173 | 0033 | 3 | Rel-8 | F | Changing the attributes of individual media during an IMS Multimedia Telephony communication | 8.4.0 | 8.5.0 | MMTel |
+| SP-42 | SP-080770 | S1-083439 | 22.173 | 0036 | 3 | Rel-8 | F | Correction of interaction of SS and emergency callback | 8.4.0 | 8.5.0 | TEI8 |
+| SP-42 | SP-080768 | S1-084149 | 22.173 | 0049 | - | Rel-8 | C | Addition of IMS CAT to IMS Multimedia Telephony service | 8.4.0 | 8.5.0 | CIMS_3G PP2 |
+| SP-42 | SP-080770 | S1-084423 | 22.173 | 0052 | 2 | Rel-8 | F | Applicability of PNM to MMTel | 8.4.0 | 8.5.0 | MMTel |
+| SP-42 | SP-080777 | S1-083213 | 22.173 | 0038 | 2 | Rel-9 | B | Association of Services to Time/Date | 8.5.0 | 9.0.0 | eMMTel |
+| SP-42 | SP-080777 | S1-083216 | 22.173 | 0040 | 3 | Rel-9 | B | Add additional timing information | 8.5.0 | 9.0.0 | eMMTel |
+| SP-42 | SP-080777 | S1-084383 | 22.173 | 0046 | 3 | Rel-9 | B | Allow / Block list (MCC Note: the title of this CR has been modified here to fit the inclusive | 8.5.0 | 9.0.0 | eMMTel |
+
+| | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------|-----------|-----------|--------|------|---|--------|---|------------------------------------------------------------------------------------------|--------|--------|------------|
+| | | | | | | | | language initiative) | | | |
+| SP-42 | SP-080777 | S1-084382 | 22.173 | 0048 | 2 | Rel-9 | C | Enhancements for ICB | 8.5.0 | 9.0.0 | eMMTel |
+| SP-42 | SP-080776 | S1-084328 | 22.173 | 0050 | 1 | Rel-9 | C | Addition of IMS CRS to IMS Multimedia Telephony service | 8.5.0 | 9.0.0 | TEI9 |
+| SP-43 | SP-090083 | S1-090184 | 22.173 | 0052 | 1 | Rel-9 | F | Corrections to dynamic blocking of incoming communications | 9.0.0 | 9.1.0 | eMMTel |
+| SP-44 | SP-090372 | S1-091295 | 22.173 | 0054 | 2 | Rel-9 | A | Alignment CR: Completion of Communications on No Reply | 9.1.0 | 9.2.0 | TEI9 |
+| SP-45 | SP-090478 | S1-093295 | 22.173 | 0055 | 3 | Rel-9 | D | Introduce reference to Total Conversation in IMS Multimedia Telephony | 9.2.0 | 9.3.0 | eMMTel |
+| SP-45 | SP-090478 | S1-093355 | 22.173 | 0057 | 1 | Rel-9 | F | Correction of applicabilities | 9.2.0 | 9.3.0 | TEI9 |
+| SP-45 | SP-090486 | S1-093372 | 22.173 | 0056 | 1 | Rel-10 | B | Completion of Communications on Not Logged-in (CCNL) | 9.2.0 | 10.0.0 | CCNL |
+| SP-46 | SP-090837 | S1-094498 | 22.173 | 0063 | 3 | Rel-10 | A | Correction of CDIV interactions | 10.0.0 | 10.1.0 | TEI8 |
+| SP-46 | SP-090846 | S1-094479 | 22.173 | 0060 | 1 | Rel-10 | D | Correction of numbering | 10.0.0 | 10.1.0 | TEI10 |
+| SP-46 | SP-090846 | S1-094495 | 22.173 | 0064 | 1 | Rel-10 | B | ICS Enhancements | 10.0.0 | 10.1.0 | TEI10 |
+| SP-46 | SP-090846 | S1-094281 | 22.173 | 0059 | 2 | Rel-10 | B | Time extension | 10.0.0 | 10.1.0 | TEI10 |
+| NOTE: version 10.1.0 wrongly shows "10.0.0" on cover page and Change History was not updated (but all CRs implemented). | | | | | | | | | | | |
+| SP-47 | SP-100190 | S1-100072 | 22.173 | 0066 | - | Rel-10 | B | Enhanced voice services | 10.1.0 | 10.2.0 | EVS_Cod ec |
+| SP-48 | SP-100437 | S1-101107 | 22.173 | 0068 | 2 | Rel-11 | B | USSD Simulation Service | 10.2.0 | 11.0.0 | USSI |
+| SP-49 | SP-100583 | S1-102011 | 22.173 | 0069 | - | Rel-11 | B | IMS Roaming Enhancements | 11.0.0 | 11.1.0 | OSCAR |
+| SP-51 | SP-110163 | S1-110430 | 22.173 | 0071 | 1 | Rel-11 | A | Supplementary services classification on II-NNI | 11.1.0 | 11.2.0 | TEI10 |
+| SP-53 | SP-110632 | S1-112375 | 22.173 | 0074 | 3 | Rel-11 | B | Supplementary Services for Support of Enterprise IP-PBX | 11.2.0 | 11.3.0 | VINE |
+| SP-54 | SP-110807 | S1-113394 | 22.173 | 0078 | 1 | Rel-11 | A | ACR correction | 11.3.0 | 11.4.0 | IMSTSS |
+| SP-54 | SP-110816 | S1-113325 | 22.228 | 0155 | 1 | Rel-12 | B | INIPUI Address Resolution | 11.4.0 | 12.0.0 | TEI12 |
+| SP-56 | SP-120291 | S1-121350 | 22.173 | 0039 | 2 | Rel-12 | B | ECT Blind and OIP interaction | 12.0.0 | 12.1.0 | ECTB |
+| SP-56 | SP-120291 | S1-121028 | 22.173 | 0040 | 1 | Rel-12 | B | ECT Blind and Incoming Communication Barring interaction clarification in MMTel 22.173. | 12.0.0 | 12.1.0 | ECTB |
+| SP-57 | SP-120526 | S1-122434 | 22.173 | 0085 | 1 | Rel-12 | F | ECT Blind clarification in MMTel 22.173 | 12.1.0 | 12.2.0 | ECTB |
+| SP-58 | SP-120873 | S1-124493 | 22.173 | 0086 | 4 | Rel-12 | C | Sequential Flexible Alerting | 12.2.0 | 12.3.0 | SEQ_FA |
+| SP-60 | SP-130196 | S1-133136 | 22.173 | 0090 | 2 | Rel-12 | F | Clarification of supplementary services suppression on callbacks | 12.3.0 | 12.4.0 | TEI12 |
+| SP-63 | SP-140064 | S1-140224 | 22.173 | 0092 | 1 | Rel-12 | F | ECT - Assured Transfer description in MMTel | 12.4.0 | 12.5.0 | TEI12 |
+| SP-64 | SP-140222 | S1-141029 | 22.173 | 0098 | - | Rel-12 | A | Removal of CDIVN service | 12.5.0 | 12.6.0 | TISMML-R8 |
+| SP-65 | SP-140497 | S1-143499 | 22.173 | 0099 | 1 | Rel-12 | F | ME-generated supervisory tones for voice over IMS | 12.6.0 | 12.7.0 | TEI12 |
+| SP-66 | SP-140750 | S1-144321 | 22.173 | 101 | - | Rel-12 | B | Support for network initiated USSD | 12.7.0 | 12.8.0 | TEI12 |
+| SP-67 | SP-150042 | S1-150218 | 22.173 | 103 | 3 | Rel-14 | B | Password based service activation for IMS Multimedia Telephony service | 12.8.0 | 14.0.0 | PWDIMS |
+| SP-71 | SP-160092 | S1-160305 | 22.173 | 0106 | 1 | Rel-14 | A | MMTEL correction of a wrong reference to a clause | 14.0.0 | 14.1.0 | TEI13 |
+| SP-71 | SP-160096 | S1-160172 | 22.173 | 0107 | - | Rel-14 | F | Clarification of relationship between GTT and Real Time Text | 14.0.0 | 14.1.0 | TEI14 |
+| SP-71 | SP-160095 | S1-160503 | 22.173 | 0108 | 2 | Rel-14 | B | Local supervisory tones | 14.0.0 | 14.1.0 | TEI14 |
+| SP-71 | SP-160093 | S1-160308 | 22.173 | 0113 | 1 | Rel-14 | A | Correct the reference to pre-EVS releases | 14.0.0 | 14.1.0 | TEI12 |
+| SP-72 | SP-160355 | S1-161616 | 22.173 | 114 | 2 | Rel-14 | F | Clarification on local supervisory tones rendering | 14.1.0 | 14.2.0 | TEI14 |
+| SP-73 | SP-160547 | S1-162273 | 22.173 | 0115 | 1 | Rel-15 | C | Addition of spoofed callerid as a criteria for call diversion and call blocking features | 14.2.0 | 14.3.0 | SPECTRE |
+| SP-74 | SP-160836 | - | 22.173 | 0117 | 5 | Rel-15 | B | Enhanced Calling Name Service | 15.0.0 | 15.1.0 | eCNAM |
+| SP-80 | SP-180316 | S1-181739 | 22.173 | 0118 | 3 | Rel-16 | B | Multi-device requirements | 15.1.0 | 16.0.0 | MuD |
+| SP-81 | SP-180768 | S1-182657 | 22.173 | 0119 | 2 | Rel-16 | F | Update to MUD identities | 16.0.0 | 16.1.0 | MuD |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|---------|-----|--------------------------------------------------------------------|----------------|
+| Date | Meeting | TDoc | CR | R
ev | Cat | Subject/Comment | New
version |
+| 2019-03 | SA#83 | SP-190086 | 0123 | 2 | C | Analytics results delivered in a modified calling name display | 16.2.0 |
+| 2019-06 | SA#84 | SP-190296 | 0124 | 2 | F | UE injected tone in case of call is being forwarded/call is queued | 16.3.0 |
+| 2019-09 | SA#85 | SP-190819 | 0125 | 3 | C | Enhanced Calling Name (eCNAM) Analytics Interworking | 17.0.0 |
+| 2019-09 | SA#85 | SP-190824 | 0128 | 4 | B | MuD user preferences | 17.0.0 |
+| 2019-12 | SA#86 | SP-191037 | 0129 | | D | Editorial clean-up | 17.1.0 |
+| 2019-12 | SA#86 | SP-191037 | 0130 | 2 | C | Clarification on eCNAM-related information retrieval | 17.1.0 |
+| 2020-12 | SA#90e | SP-201026 | 131 | 1 | F | Clarification on MuDE activation / deactivation | 17.2.0 |
+| 2021-03 | SA#91e | SP-210200 | 132 | | D | Non-inclusive language replacement | 17.3.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22174/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22174/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/22_series/22174/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/22_series/22174/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22174/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2df6ad86e7021bc7b157060e6b949b94736b13ff
--- /dev/null
+++ b/marked/Rel-18/22_series/22174/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53faf037465dde7b382f95640f809053f12882698bd17ee17c7b0f3ac7e8cf9
+size 5413
diff --git a/marked/Rel-18/22_series/22174/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg b/marked/Rel-18/22_series/22174/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b5f8fe6357a2d7fae912261c581ce3771385171
--- /dev/null
+++ b/marked/Rel-18/22_series/22174/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80ce64fb6df20163ca1abd721cfef74464083f4cf0aff83a3340827901819e17
+size 40226
diff --git a/marked/Rel-18/22_series/22174/raw.md b/marked/Rel-18/22_series/22174/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cfdbb1778f0aa836b97c71d9d4944f33b1db1ca
--- /dev/null
+++ b/marked/Rel-18/22_series/22174/raw.md
@@ -0,0 +1,484 @@
+
+
+# 3GPP TS 22.174 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Push Service; Service aspects; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+LTE, UMTS, push, stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|---------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Overview of the Push Service..... | 6 |
+| 5 Requirements ..... | 7 |
+| 5.1 General ..... | 8 |
+| 5.2 Provisioning ..... | 8 |
+| 5.3 Subscription..... | 8 |
+| 5.4 Addressing and Routing..... | 9 |
+| 5.5 Delivery..... | 9 |
+| 5.6 Service Management..... | 10 |
+| 6 Security ..... | 10 |
+| 7 Privacy ..... | 10 |
+| 8 Access rules..... | 11 |
+| 9 Charging..... | 11 |
+| 10 Push Subscription Profile Information..... | 12 |
+| 11 Roaming ..... | 12 |
+| 12 Barring of the Push Service ..... | 12 |
+| Annex A (informative): Change history..... | 13 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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 Push Service introduces a means to transmit push data from a push initiator to a push recipient (e.g. a UE) without a previous user action. The push concept, as provided by the SMS teleservice, has been very successful in the GSM second generation, both for text messaging (for user viewing) and for other unstandardized data to the SIM (as a building block used for OTA and other purposes). This TS introduces the Push Service as a generalization of existing network capabilities plus the development of new capabilities. The Push Service should therefore be understood as a building block (network capability), which can be used for new services, both public and private, in 3GPP.
+
+In the normal client/server model, a client requests a service or information from a server, which then responds in transmitting information to the client. This is known as the "pull" technology, the user pulls information from the content provider. The World Wide Web is a typical example of pull technology, where a user enters a URL (the request) that is sent to a server and the server answers by sending a Web page (the response) to the user.
+
+In contrast to this there is also the "push" technology where there is no explicit request from the user before the content provider (push initiator) initiates an information transfer to a user. Another way of saying this is that whereas "pull" transaction of information are always initiated from the user, "push" transactions are content provider initiated. The welcome message received after registration with a visited network whilst roaming is an example of information transfer that has been initiated without a request from the user. Typically, a user signs up with the push initiator and defines their interest, volume of information acceptable and other factors in the push subscription profile. As information becomes available that satisfies the user's push subscription profile, the push initiator delivers it to the user using the Push Service.
+
+The Push service may be used to implement high level services such as IP multimedia services, MMS, etc., and new services including public safety, government, corporate IT, transfer of push data to machines and devices, in addition to infotainment type services.
+
+Another common use for push services is the delivery of notification from e.g. MMS to the user while the user has the option of "pulling" the actual push data from the push initiator.
+
+The PLMN Push function provides the push data to the user agent in the UE. The user agent interprets and presents the push data to a person, device or machine using the UE.
+
+**NOTE:** The requirements of services such as streaming, conversational services and broadcast are independent from push. Therefore they are not considered appropriate for inclusion here. Push will be available for use in appropriate applications of all high level services.
+
+# --- 1 Scope
+
+This Technical Specification defines the Stage 1 description of the Push Service and is the set of requirements that shall be supported for the provision of push, seen primarily from the subscriber's, service providers' and delivery network points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers. It is of use to manufacturers and organisations which have devices or machines benefiting by availability of push service.
+
+This TS contains the core requirements for the Push Service, for operator and external Push Initiators, which are sufficient to provide a complete service capability and service capability feature.
+
+This TS defines the requirements for the Push Service to enable delivery of push data, including such functionality as:
+
+- Transfer of push data from a Push Initiator to a Push Recipient
+- Latency and Priority classes,
+- Definition of handling of undeliverable push data.
+
+# --- 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 TS 21.133: "3G security; Security threats and requirements".
+- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [3] 3GPP TS 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
+
+# --- 3 Definitions and abbreviations
+
+Definitions and abbreviations used in the present document are listed in TR 21.905 [2]. For the purposes of this document the following definitions and abbreviations apply:
+
+## 3.1 Definitions
+
+**Push Data:** data sent by the push initiator to the push recipient, of a format known to the receiver (push recipient), and not otherwise defined by the push service.
+
+**PLMN:** the 3GPP network that receives the push data from the push initiator and ensures the delivery of push data to the push recipient. The delivery of the push data may involve other networks.
+
+**Push function:** the function in the PLMN that receives the Push Data from the Push initiator. The push function is responsible for delivering the push data to the Push recipient.
+
+**Push initiator:** the entity that originates push data and submits it to the push function for delivery to a Push recipient. A Push initiator may be e.g. an application providing value added services.
+
+**Push recipient:** the entity that receives the push data from the Push function and processes or uses it. This may include the UE with which the PLMN communicates with, the user agent with the application level address, and the device, machine or person which uses the push data. A Push recipient is controlled by an individual user .
+
+**Push service:** a service capability offered by the PLMN. The Push Service is initiated by a Push Initiator in order to transfer push data (e.g. data, multimedia content) from the Push Initiator to the Push Recipient without a previous user action. The Push Service could be used as a basic capability or as component of a value added service.
+
+**Push User agent:** is any software or device associated with a Push recipient that interprets Push Data to the user. This may include textual browsers, voice browsers, search engines, machine or device interface software, etc.
+
+**Push Subscription Profile:** a set of parameters indicating the Push recipient's settings and preferences for the Push Service.
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+URL – Uniform Resource Locator.
+
+# 4 Overview of the Push Service
+
+The overview of push is followed by a summary of the relationships among the entities involved (operators, users, push recipients and push initiators).
+
+NOTE: these are functional descriptions: multiple functions may, depending on business arrangements, be performed by a single entity.
+
+
+
+The diagram shows three main components: a 'Push Recipient' (represented by a box containing 'User, Device, Or Machine'), a 'PLMN' (represented by a cloud containing a 'Push function' box), and a 'Push Initiator' (represented by a server icon). Dashed arrows indicate the flow of data: from the Push Initiator to the Push function, and from the Push function to the Push Recipient. A bracket at the bottom groups the PLMN and Push function as the 'Push Service'.
+
+Diagram illustrating the Push Service Overview. A Push Recipient (User, Device, Or Machine) is connected via a dashed arrow to a PLMN cloud containing a Push function. The Push function is connected via a dashed arrow to a Push Initiator. The entire process is labeled as the Push Service.
+
+**Figure 1: Push Service Overview**
+
+The Push Service is a service whereby the Push Initiator sends push data through a Push Server to a Push Recipient, without interaction from the Push Recipient.
+
+The typical mode of operation is as follows:
+
+- A Push Recipient (e.g. user, receiving device like a meter) explicitly or implicitly subscribes to a set of value added services offered by various Push Initiators and allow these Push Initiators to send it push data that meet the Push Recipient's configured criteria. (This configured criteria is part of the Push user profile.)
+- A Push Initiator identifies information matching the criteria set by the Push Initiator and package it up into the push data
+- The Push Initiator delivers the push data to the Push function, identifying the Recipient's address, and optionally priority, delivery time parameters, etc.
+- The Push function takes the responsibility of delivering the push data, optionally following the priority and delivery time parameters, to the Push Recipient and for providing feedback to the Push Initiator regarding delivery of the push data if requested by the Push Initiator.
+
+Key characteristics of the Push Service include:
+
+- The Push Initiator may, but is not required to deal with the specifics of the wireless transport, selection of appropriate bearers, out-of-coverage or roaming issues, and other wireless network anomalies. These are all managed by the Push Service and hence can be optimised at the network level rather than being handled by all applications. Using an available bearer the push service offers as many capabilities that are available to delivery of the push data following the requested push services requested by the push initiator.
+- The push initiator shall be provided with a means to query the push server for a specific recipient's push user profile subject to privacy considerations.
+- The push server shall not change the push data (contents). Any transformations that the Push Server provides shall be compliant with user privacy requirements as defined in the push subscriber profile.
+- The push service shall be able to handle user groups (i.e. have the ability to target a certain group of push recipients).
+- The push service is capable of supporting asynchronous communication between a Push Initiator and the push recipient on a wireless device.
+- The privacy of the user is important and the introduction of the push services should in no way result in unwanted information "spam" being sent to mobile users.
+
+The Push data could contain:
+
+- Application specific data exchanged between a server and its client e.g. ERP, CRM, Field Service management, m-commerce transaction data or a meter reading
+- Provisioning or configuration control data
+
+The entities shown in Figure 1 are Push Initiator, Push Server (PLMN) and the Push Recipient. The Push Initiator may be outside the Operators network and hence will require well-defined relationships amongst them.
+
+For example, a Push Initiator can be within the Operator domain (e.g. an operator portal) or an external VASP. A Push Recipient (e.g. a User) will need to be part of the Operators network and will require allowing the network to pass through push data and also subscribing to the Push Initiator to generate the data it wants pushed. To support flexible billing models, it becomes necessary for the Operator to have a defined commercial relationship with the Push Initiator.
+
+# --- 5 Requirements
+
+The following list gives the high level requirements for the Push service.
+
+## 5.1 General
+
+The Push Service shall allow a Push Initiator (which may be external to the PLMN) to initiate delivery of push data to the Push recipient. It shall be possible to deliver push data to the push recipient without any user intervention, subject to settings in the push subscription profile. The Push Initiator may interrogate the push subscription profile, if available, in order to establish the user preference related to the Push Service.
+
+- The push mechanism shall be efficient in the use of network resources and terminal resources.
+- It shall be possible to support Push Service independently over CS (including CS data and SMS), PS domains or IMS.
+- NOTE: Operators should be able to choose which of these options they use to deliver Push services, and it should be possible to use these options independently from each other. E.g. delivery over the PS domain would allow operators who are not planning to introduce IMS and SMS to offer Push Services.
+- It shall be possible to deploy Push Services independently of other services defined by 3GPP.
+- The quality of service delivery shall be able to include time-sensitive as well as reliable delivery choices
+- It shall be possible to use all available access networks (e.g. GERAN, UTRAN,).
+- It shall be possible for the Push Initiator to specify a bearer for the Push Service, as a default the push service shall identify the bearer. The Push Initiator may, however, require certain grade of service for delivery, e.g. speed of delivery or delivery acknowledgement.
+
+## 5.2 Provisioning
+
+The operator shall be able to provision a user or organisation-user (e.g. a subscriber or a VASP) with the Push Service. The provision may include usage of the Push Service as a Push initiator, as a Push recipient or both.
+
+The provision may be:
+
+- general: where the service is made available to all user or organisation-users (subject to compatibility restrictions enforced) without prior arrangements being made with the operator;
+- pre-arranged: where the service is made available to an individual user or organisation-user only after the necessary arrangements have been made with the operator.
+
+If the user is provisioned with the Push Service as a Push initiator he may use the Push Service in order to transfer push data to the Push Recipient, subject to settings in the push subscription profile of the Push Recipient.
+
+If the user is provisioned with the Push Service as a Push recipient he may use the Push Service in order to receive push data from a Push initiator.
+
+The push subscription profile parameters (user's settings and preferences) are managed by the user or the operator on behalf of the user.
+
+The operator shall be able to withdraw the provision of the Push service. Withdrawal may be general or pre-arranged.
+
+NOTE: Provisioning with – or subscription to – value added services, that make use the Push service are out of scope of this specification.
+
+NOTE : the concept of organisation user may apply to GUP and if so will not be duplicated here.
+
+## 5.3 Subscription
+
+The usage of the Push Service to deliver push data from a Push Initiator to a Push Recipient requires as a precondition either an explicit or implicit subscription to the Push Service
+
+Explicit Push Subscription:
+
+A subscriber subscribes to the Push Service together with the Push service provider, i.e. the home PLMN operator. Home PLMN Push service providers may then use the Push service to deliver content to the subscriber.
+
+Implicit Push Subscription:
+
+A Value added service provider shall be able to subscribe to the Push Service on behalf of a subscriber to a value added service provided by this VASP. From a Push service point of view the subscriber becomes a push recipient. From now on the Value added service provider shall be able to use the Push Service capabilities to deliver content to this particular subscriber, i.e. the push recipient.
+
+The Push service subscription is valid for the subscriber to receive push data from the VASP that has subscribed to the Push service as long as the subscription is valid.
+
+## 5.4 Addressing and Routing
+
+It shall be possible to uniquely identify push recipients.
+
+It shall be possible for push recipients to uniquely identify push initiators.
+
+The addressing model shall include addresses of the device (e.g. IP address, SIP-URI, MSISDN) and application level addressing (i.e. user agents). The addressing model shall be compatible with Internet specifications when applicable.
+
+It shall be possible to deliver push data to a push recipient with a dynamically allocated IP address.
+
+The Push service shall be able to deliver a push data to a push recipient that does not have an IP address currently assigned.
+
+Both telecom and internet numbering and addressing schemes shall be supported.
+
+It shall be possible to address push recipients without allocating E.164 numbers.
+
+## 5.5 Delivery
+
+The PLMN may set restrictions including maximum size of Push data.
+
+The Push Service may offer classes of priority and service delivery. When offered this shall include support for the following:
+
+- Delivery time constraints (timing window, i.e. allow the push initiator to specify "deliver after" and "deliver before" parameters)
+- Requested delivery priority (different priorities dependent on for example push initiator, or allowing the push initiator to specify the desired priority)
+- If neither delivery time nor priority is set then a single attempt shall be made to deliver the push data without unnecessary delay.
+- The push service shall be able to send a delivery report to the push initiator, which includes information about a specific submission's final outcome (delivered, expired, etc.). The report is sent only if the push initiator requested it in the initial push submission or has requested it for all push submissions.
+- It shall be possible to deliver push data both in an acknowledged and an un-acknowledged manner between the push service and the push recipient
+- It shall be possible for the push initiator to request that only one delivery attempt is made.
+
+In case the push recipient declines a specific instance of push data, it shall be provided with means to indicate whether the push service is allowed to re-send it or not.
+
+In the case that classes of priority and service delivery are not offered an attempt to deliver push data to the push recipient shall be made without unnecessary delay.
+
+## 5.6 Service Management
+
+The basic principle of service management is "the user is in control".
+
+The user is provisioned with the Push Service by a Network Operator. If a user is provisioned with the push service, the provisioning data shall include a push subscription profile for push service settings and push service preferences. .
+
+The push subscription profile of a Push Recipient shall at least contain:
+
+- General settings, independent of individual Push initiators
+this may include:
+ - Permissible minimal QoS per data format for receiving push data
+ - Permissible maximum size of push data permitted to be pushed
+ - Permissible charging thresholds to receive push data
+- A mechanism for screening push initiators
+
+NOTE: Parameters may be bearer sensitive.
+
+# --- 6 Security
+
+The "Security Threats and Requirements" specified in 21.133 [1] shall not be compromised.
+
+It shall be possible for the Push Service Operator to be assured of the identity of the Push Initiator.
+
+It shall be possible for the Push Recipient to be assured of the identity of the Push Initiator.
+
+Mechanisms shall be provided to ensure that the push data is sent to and accessed only by the intended addressed entity.
+
+It shall be possible for the Push Service or the user to deny unauthorized push data.
+
+An authorization may be based on the following:
+
+- identity of the Push Initiator
+- the destination user, device or user agent
+- push related attributes such as priority and content type
+
+It shall be possible for the user to control acceptance of push data sent to the user based on the trust level of the Push Initiator.
+
+The Push Service shall provide data integrity and data confidentiality of the push data.
+
+Push Initiators must have authorization (e.g. service level agreement) with the Push Service Operator (e.g. PLMN Operators) in order to use the Push Service.
+
+# --- 7 Privacy
+
+The Push Service shall ensure compliance with the Push Recipient's privacy requirements as described below. Specific local, national, and regional privacy regulations shall be complied with. An operator shall, at any time, be able to override a Push Recipient's privacy preferences if required to do so by legal authorities.
+
+The privacy of the user is important and the introduction of the push services should in no way result in unwanted information "spam" being sent to mobile users.
+
+# 8 Access rules
+
+The Push Recipient shall be able to define access rules, in order to control how her privacy requirements shall be handled by the Push function.
+
+It shall be possible for the Push Recipient to define the following access rules:
+
+- The Push Recipient shall be able to allow push data from individual push initiators or groups of Push Initiators to transmit push data to the Push recipient
+- It shall be possible for the Push Recipient to uniquely identify a Push initiator and the addressed User Agent prior to accepting or declining a request to receive push data from that Push Initiator.
+- The Push Recipient shall be able to automatically decline push data from individual push initiators or groups of Push Initiators to transmit push data to the Push recipient
+- At any time it shall be possible for the Push Recipient to stop receipt of push data from a Push Initiator. This may include any push data from this Push Initiator or only push data addressed to a particular User Agent of the Push Recipient.
+- The Push Recipient shall be able to allow individual push initiators or groups of Push Initiators to transmit push data without user interaction at the Push Recipient's side.
+
+It shall be possible for the Push Recipient to define these access rules based on:
+
+- The identity of the Push Initiator
+- The addressed User Agent
+
+In addition it shall be possible for the Push Recipient to specify the validity of these access rules
+
+- Only for the next request of the Push Initiator or
+- For a pre-defined period e.g. next hour
+- Unlimited, i.e. till modification or removal of the access rule.
+
+NOTE: A set of default access rules may be defined by the operator.
+
+# 9 Charging
+
+This paragraph specifies charging requirements for the Push service.
+
+The Push service shall support various charging mechanisms (e.g. reverse, prepaid and reply charging etc.).
+
+The following charging scenarios shall be supported:
+
+1. Charging for the push service can be subscription based.
+Different charging options shall be permissible whether the user is provisioned with the Push Service as a Push initiator or as a Push recipient.
+2. Charging for the push service can be based on the push data, the resources used and time needed to carry out the push service.
+3. Charging for the push service can be based on the size of the push data pushed to a receiver.
+4. It shall be possible to charge the Push recipient only, the Push Initiator only, or both.
+5. It shall also be possible to mix and match the various different charging scenarios outlined above.
+6. It shall be possible to charge for the initial push service activation.
+
+7. It shall be possible to charge a Push initiator for an attempt to send push data to a push recipient, even if the push recipient rejects the push data
+
+It shall be possible to include the following data in the CDRs as charging information if available:
+
+- message types, length, storage time in the network, etc
+- delivery time, upload / download method,
+- Push service sender / -recipient
+- the amount of the push data sent
+- the amount of the push data received.
+- roaming conditions (e.g. in a visited network)
+- location conditions
+
+# --- 10 Push Subscription Profile Information
+
+For each Push recipient the Push Service shall keep a Push subscription profile. This Push subscription profile shall contain the Push recipient's access rules.
+
+Optionally (as an operator's option) the Push subscription profile may contain additional Push personalization settings of the Push recipient, e.g.
+
+- Permissible minimal QoS per data format for receiving push data
+- Permissible maximum size of data packages permitted to be pushed
+- Permissible charging thresholds to receive push data
+- ...
+
+At any time, the Push Service shall permit a Push recipient to modify her Push subscription profile information.
+
+A Push initiator shall be able to interrogate any Push Recipient's Push subscription profile information. However only information relevant to this Push Initiator shall be revealed by the Push Service
+
+NOTE: The Push subscription profile may be realized as part of the 3GPP Generic User Profile (TS 22.240) [3]
+
+# --- 11 Roaming
+
+Push services shall be available when roaming.
+
+The push recipients shall be able to select and receive pushed local services, subject to the user profile settings.
+
+# --- 12 Barring of the Push Service
+
+It shall be possible to provide the Push Service to a user regardless of barring status of other services, providing that a bearer to deliver the Push Content is available.
+
+It shall be possible for user to bar the Push Service regardless of barring status of other services.
+
+# Annex A (informative): Change history
+
+| | | |
+|----------|---------------|---------------------------------------------------------------------------------------|
+| V. 0.1.0 | February 2001 | First Draft (Presented at TSG-SA-WG1 6 th – 9 th February 2001) |
+| V. 0.2.0 | July 2001 | Second Draft (from SA1 ad-hoc, 9 July 2001) |
+| V. 0.3.0 | November 2001 | Third Draft (presented at SA1 5 th – 9 th November 2001) |
+| V. 0.3.1 | January 2002 | Highlighting removed as basis for Phoenix SWG (13-18 January 2002) |
+| V. 0.5.0 | January 2002 | Output of Phoenix Push SWG (15-16 January 2002). |
+| v. 0.6.0 | February 2002 | Output from Saalfelden (11 th – 15 th February 2002) |
+| v. 0.7.0 | April 2002 | Output from Sophia Antipolis (9 th April 2002) |
+| v. 0.7.1 | April 2002 | Clean copy of output from Sophia Antipolis |
+| v. 0.8.0 | May 2002 | Output of Victoria (15 th May 2002) |
+| v. 0.8.1 | May 2002 | Clean copy of output from Victoria |
+| v. 1.0.0 | May 2002 | Submission to SA for information |
+| v. 1.1.0 | July 2002 | Output of Rome (8 – 12 July 2002) |
+| v. 1.1.1 | July 2002 | Clean copy of output from Rome |
+| v. 1.2.0 | August 2002 | Output of Durango (12 – 16 August 2002) |
+| v. 1.2.1 | August 2002 | Clean copy of output from Durango |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|---------------------------------------------------------------|--------|--------|------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| | | | 22.174 | | | Rel 6 | | Updated for presentation to SA #17 | | 2.0.0 | |
+| SP-17 | SP-20571 | | 22.174 | | | Rel 6 | | Presented to SA #17 for approval | 2.0.0 | 6.0.0 | |
+| SP-18 | SP-020661 | S1-021947 | 22.174 | 001 | | Rel-6 | F | Removal of Note | 6.0.0 | 6.1.0 | PUSH |
+| SP-18 | SP-020661 | S1-021949 | 22.174 | 002 | | Rel-6 | C | Removal of Media from Charging Parameters | 6.0.0 | 6.1.0 | PUSH |
+| SP-18 | SP-020661 | S1-021950 | 22.174 | 003 | | Rel-6 | D | Removal of void reference | 6.0.0 | 6.1.0 | PUSH |
+| SP-18 | SP-020661 | S1-022188 | 22.174 | 004 | | Rel-6 | C | Push Delivery Class | 6.0.0 | 6.1.0 | PUSH |
+| SP-18 | SP-020661 | S1-022334 | 22.174 | 005 | | Rel-6 | D | Revision of Requirements for One-Off Charging | 6.0.0 | 6.1.0 | PUSH |
+| SP-19 | SP-030027 | S1-030059 | 22.174 | 006 | - | Rel-6 | C | Removal of MMS content | 6.1.0 | 6.2.0 | PUSH |
+| SP-19 | SP-030027 | S1-030250 | 22.174 | 007 | - | Rel-6 | C | Barring of Push Service | 6.1.0 | 6.2.0 | PUSH |
+| SP-19 | SP-030027 | S1-030063 | 22.174 | 008 | - | Rel-6 | C | Removal of 'Null' Interworking Chapter | 6.1.0 | 6.2.0 | PUSH |
+| SP-19 | SP-030027 | S1-030117 | 22.174 | 009 | - | Rel-6 | D | CR to the PUSH Stage 1 TS on the Feature Interactions section | 6.1.0 | 6.2.0 | PUSH |
+| SP-36 | | | 22.174 | | | Rel-7 | | Updated from Rel-6 to Rel-7 | 6.2.0 | 7.0.0 | |
+| SP-42 | - | - | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | - | - | - | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2019-07 | - | - | - | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22179/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-18/22_series/22179/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..28c73e491201f9f30e5eeb7c93204bd276a7f813
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:202b78e83e3f72c9988f38b4fa2260b486c9ec21b1103c77272900681e720845
+size 48676
diff --git a/marked/Rel-18/22_series/22179/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-18/22_series/22179/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bdba86d35132d49a996aae4bcae0ae315e48c95b
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00f38d7a10091fb8151a09ef27275787ac56083a9f8fd4ac2a2d6e3afb2a42f5
+size 61294
diff --git a/marked/Rel-18/22_series/22179/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-18/22_series/22179/16152cf1d84aea10848758f51a91ff6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..245a045a9a08a2fd6d78e96858b83c069c73bce4
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/16152cf1d84aea10848758f51a91ff6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45e37e7c25d35cec8f93fa7005f2ad934104302bdcef1916a1171957dbcc75f7
+size 120594
diff --git a/marked/Rel-18/22_series/22179/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/Rel-18/22_series/22179/3493d7ba4c86f944e159de1bf45ff03d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b986361df145cf75a2c7309df77b0a05f36f86b0
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/3493d7ba4c86f944e159de1bf45ff03d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0f36ffdf110faa879668615b527566c54ecebc076b5e6fcc0b208aae00fe306
+size 49335
diff --git a/marked/Rel-18/22_series/22179/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22179/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0924ce5944c7e15f8f140d3590bc5fe8060ddee1
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d0c7ce6306e5c99815c3d82ae0bff5903ac63cd6bce23f4730144f1f49baf3d
+size 9556
diff --git a/marked/Rel-18/22_series/22179/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22179/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b485d04226ab64613f08f706875fb77d45dddd2
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:352e5b2954944afee8a4cbf514960f0a5af2f58d525d67eb5b1fc9d5e8d01af7
+size 8063
diff --git a/marked/Rel-18/22_series/22179/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-18/22_series/22179/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3433d170824dfe5f660a5712d9fc25234f52edd
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b65ff2a901dd53c26bb7f23ce3c1cdc5226a2149386a3e98174662d90e754aed
+size 144362
diff --git a/marked/Rel-18/22_series/22179/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-18/22_series/22179/bd671b21db63e6fdb2196e9b18502aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6be087ea2ed94687490bb280c9e6d51b05aa2f72
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/bd671b21db63e6fdb2196e9b18502aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a4aa7de99b5efc73b78c8f46820cd2ea692a5490aef41c84e52f4518d68fdb6
+size 163171
diff --git a/marked/Rel-18/22_series/22179/e42cc691d9c7c4d23e66b04472bb494e_img.jpg b/marked/Rel-18/22_series/22179/e42cc691d9c7c4d23e66b04472bb494e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03f793f5e0574690e68ad23be8f0e99a3ac5f5f1
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/e42cc691d9c7c4d23e66b04472bb494e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57cf55bc414506aebd035af3bf9800b9adf0d3458b11dedfbe97e66f0485e4cb
+size 42559
diff --git a/marked/Rel-18/22_series/22179/raw.md b/marked/Rel-18/22_series/22179/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4fd5e6a17b86948d7e7515f489d183f712cbf845
--- /dev/null
+++ b/marked/Rel-18/22_series/22179/raw.md
@@ -0,0 +1,3676 @@
+
+
+# 3GPP TS 22.179 V18.0.0 (2023-06) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Push To Talk (MCPTT); Stage 1 (Release 18)** ---
+
+
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red signal icon consisting of three curved lines. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - France
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|----------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 8 |
+| Introduction ..... | 8 |
+| 1 Scope..... | 9 |
+| 2 References..... | 9 |
+| 3 Definitions and abbreviations ..... | 10 |
+| 3.1 Definitions..... | 10 |
+| 3.2 Abbreviations ..... | 12 |
+| 4 Mission Critical Push To Talk overview ..... | 12 |
+| 4.1 General ..... | 12 |
+| 4.2 Typical use of the MCPTT Service..... | 13 |
+| 4.3 Overview of MCPTT Group affiliation, call and transmission..... | 13 |
+| 4.4 General handling of requests..... | 17 |
+| 4.5 Overview of MCPTT UE and MCPTT User in the MCPTT Service ..... | 17 |
+| 4.5.1 MCPTT User association to MCPTT UE in on-network mode ..... | 18 |
+| 4.5.2 MCPTT User and MCPTT UE relationship..... | 18 |
+| 4.5.3 MCPTT Users accessing the service through non-3GPP access interface..... | 18 |
+| 4.5.4 Shareable MCPTT UEs and gateway UEs..... | 18 |
+| 4.5.5 MCPTT User association to MCPTT UE in off-network mode..... | 19 |
+| 4.6 Overview of MCPTT priorities ..... | 20 |
+| 4.6.1 MCPTT priority model..... | 20 |
+| 4.6.2 Generic processing of priority information ..... | 21 |
+| 4.6.3 Handling of MCPTT priority information for Floor control ..... | 22 |
+| 4.6.4 Handling of MCPTT priority information for interactions at the transport layer ..... | 22 |
+| 4.6.5 Handling of MCPTT priority information for interactions with non-3GPP PTT systems..... | 22 |
+| 4.6.6 MCPTT priority for Private Call ..... | 22 |
+| 4.7 Overview of MCPTT identifiers ..... | 22 |
+| 5 MCPTT Service requirements common for on the network and off the network ..... | 23 |
+| 5.1 General group call requirements ..... | 23 |
+| 5.1.1 General aspects..... | 23 |
+| 5.1.2 Group/status information..... | 23 |
+| 5.1.3 Group configuration ..... | 23 |
+| 5.1.4 Identification..... | 23 |
+| 5.1.5 Membership/affiliation ..... | 24 |
+| 5.1.6 Group Call administration ..... | 24 |
+| 5.1.7 Prioritization ..... | 24 |
+| 5.1.8 Charging requirements for MCPTT ..... | 24 |
+| 5.2 Broadcast Group..... | 24 |
+| 5.2.1 General Broadcast Group Call..... | 24 |
+| 5.2.2 Group-Broadcast Group (e.g., announcement group) ..... | 25 |
+| 5.2.3 User-Broadcast Group (e.g., System Call) ..... | 25 |
+| 5.3 Late call entry..... | 25 |
+| 5.4 Dynamic group management (i.e., dynamic regrouping)..... | 25 |
+| 5.5 Receiving from multiple MCPTT calls..... | 25 |
+| 5.5.1 Overview ..... | 25 |
+| 5.5.2 Requirements..... | 26 |
+| 5.6 Private Call..... | 26 |
+| 5.6.1 Private Call overview ..... | 26 |
+| 5.6.2 Private Call (with Floor control) general requirements..... | 26 |
+| 5.6.3 Private Call (with Floor control) commencement requirements ..... | 27 |
+| 5.6.4 Private Call (with Floor control) termination ..... | 28 |
+| 5.6.5 Private Call (with Floor control) administration ..... | 28 |
+| 5.7 MCPTT priority requirements..... | 29 |
+| 5.7.1 Overview ..... | 29 |
+
+| | | |
+|-----------|-------------------------------------------------------------------------------------------|----|
+| 5.7.2 | Call types based on priorities ..... | 29 |
+| 5.7.2.1 | MCPTT Emergency Group Call ..... | 29 |
+| 5.7.2.1.1 | MCPTT Emergency Group Call requirements..... | 29 |
+| 5.7.2.1.2 | MCPTT Emergency Group Call cancellation requirements..... | 30 |
+| 5.7.2.2 | Imminent Peril group call ..... | 30 |
+| 5.7.2.2.1 | Imminent Peril group call requirements..... | 30 |
+| 5.7.2.2.2 | Imminent Peril group call cancellation requirements ..... | 30 |
+| 5.7.2.3 | MCPTT Emergency Private Call (with Floor control) ..... | 31 |
+| 5.7.2.3.1 | MCPTT Emergency Private Call (with Floor control) requirements..... | 31 |
+| 5.7.2.3.2 | MCPTT Emergency Private Call (with Floor control) cancellation requirements ..... | 31 |
+| 5.7.2.4 | MCPTT Emergency Alert..... | 31 |
+| 5.7.2.4.1 | MCPTT Emergency Alert requirements ..... | 31 |
+| 5.7.2.4.2 | MCPTT Emergency Alert cancellation requirements..... | 31 |
+| 5.8 | User ID ..... | 32 |
+| 5.9 | MCPTT UE management..... | 32 |
+| 5.10 | MCPTT User Profile ..... | 32 |
+| 5.11 | Support for multiple devices ..... | 32 |
+| 5.12 | Location..... | 32 |
+| 5.13 | Security..... | 33 |
+| 5.14 | Audio / voice quality ..... | 33 |
+| 5.15 | Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor control) ..... | 33 |
+| 5.16 | Relay requirements..... | 33 |
+| 5.17 | Gateway requirements..... | 33 |
+| 5.18 | Control and management by Mission Critical Organizations ..... | 34 |
+| 5.18.1 | Overview ..... | 34 |
+| 5.18.2 | General requirements..... | 34 |
+| 5.18.3 | Operational visibility for Mission Critical Organizations ..... | 34 |
+| 5.19 | General Administrative – groups and users ..... | 34 |
+| 6 | MCPTT Service requirements specific to on-network use ..... | 34 |
+| 6.1 | General administrative – groups and users ..... | 34 |
+| 6.2 | MCPTT calls ..... | 35 |
+| 6.2.1 | Commencement modes for MCPTT Group calls ..... | 35 |
+| 6.2.2 | Queuing ..... | 36 |
+| 6.2.3 | Floor control ..... | 36 |
+| 6.2.3.1 | General aspects ..... | 36 |
+| 6.2.3.2 | Requesting permission to transmit..... | 36 |
+| 6.2.3.3 | Override ..... | 37 |
+| 6.2.3.3.1 | General aspects..... | 37 |
+| 6.2.3.3.2 | Override – one transmitting Participant ..... | 37 |
+| 6.2.3.3.3 | Override – simultaneously Transmitting MCPTT Group Members ..... | 38 |
+| 6.2.3.4 | Terminating permission to transmit..... | 38 |
+| 6.2.3.5 | Transmit time limit ..... | 38 |
+| 6.2.3.6 | Audio cut-in on designated MCPTT Groups ..... | 38 |
+| 6.2.3.6.1 | Overview ..... | 38 |
+| 6.2.3.6.2 | Requirements ..... | 39 |
+| 6.2.3.6.3 | Requesting permission to transmit..... | 39 |
+| 6.2.3.6.4 | Terminating permission to transmit ..... | 39 |
+| 6.2.3.6.5 | Transmit time limit..... | 39 |
+| 6.2.3.7 | MCPTT Groups configured for multi-talker control ..... | 40 |
+| 6.2.3.7.1 | Overview ..... | 40 |
+| 6.2.3.7.2 | General aspects..... | 40 |
+| 6.2.3.7.3 | Requesting permission to transmit..... | 40 |
+| 6.2.3.7.4 | Override..... | 41 |
+| 6.2.4 | Call termination ..... | 41 |
+| 6.3 | General requirements ..... | 42 |
+| 6.4 | General group call ..... | 42 |
+| 6.4.1 | General aspects ..... | 42 |
+| 6.4.2 | Group status/information ..... | 42 |
+| 6.4.3 | Identification..... | 42 |
+| 6.4.4 | Membership/affiliation ..... | 42 |
+| 6.4.5 | Membership/affiliation list ..... | 42 |
+
+| | | |
+|-----------|------------------------------------------------------------------------------------------------------|----|
+| 6.4.6 | Authorized user remotely changes another MCPTT User's affiliated and/or Selected MCPTT Group(s)..... | 43 |
+| 6.4.6.1 | Mandatory change..... | 43 |
+| 6.4.6.2 | Negotiated change..... | 43 |
+| 6.4.7 | Prioritization ..... | 43 |
+| 6.4.8 | Relay requirements..... | 43 |
+| 6.4.9 | Administrative ..... | 43 |
+| 6.5 | Broadcast group..... | 44 |
+| 6.5.1 | General Broadcast Group Call ..... | 44 |
+| 6.5.2 | Group-Broadcast Group (e.g., announcement group) ..... | 44 |
+| 6.5.3 | User-Broadcast Group (e.g., System Call) ..... | 44 |
+| 6.6 | Dynamic group management (i.e., dynamic regrouping)..... | 44 |
+| 6.6.1 | General dynamic regrouping ..... | 44 |
+| 6.6.2 | Group Regrouping ..... | 44 |
+| 6.6.2.1 | Service description..... | 44 |
+| 6.6.2.2 | Requirements ..... | 44 |
+| 6.6.3 | Temporary Group-Broadcast Group..... | 45 |
+| 6.6.4 | User regrouping ..... | 45 |
+| 6.6.4.1 | Service description..... | 45 |
+| 6.6.4.2 | Requirements ..... | 45 |
+| 6.7 | Private Call..... | 45 |
+| 6.7.0 | Overview ..... | 45 |
+| 6.7.1 | General requirements..... | 45 |
+| 6.7.2 | Administrative ..... | 46 |
+| 6.7.3 | Prioritization ..... | 46 |
+| 6.7.4 | Private Call (without Floor control) commencement requirements ..... | 46 |
+| 6.7.4a | Private Call (with Floor control) commencement requirements ..... | 47 |
+| 6.7.5 | Private Call (without Floor control) termination ..... | 48 |
+| 6.7.6 | Call back request requirements..... | 48 |
+| 6.8 | MCPTT priority requirements..... | 48 |
+| 6.8.1 | General ..... | 48 |
+| 6.8.2 | 3GPP system access controls..... | 49 |
+| 6.8.3 | 3GPP system admission controls..... | 49 |
+| 6.8.4 | 3GPP system scheduling controls ..... | 49 |
+| 6.8.5 | UE access controls..... | 49 |
+| 6.8.6 | Application layer priorities..... | 49 |
+| 6.8.6.1 | Overview..... | 49 |
+| 6.8.6.2 | Requirements ..... | 49 |
+| 6.8.7 | Call types based on priorities ..... | 49 |
+| 6.8.7.1 | MCPTT Emergency Group Call requirements ..... | 49 |
+| 6.8.7.2 | MCPTT Emergency Private Call (with Floor control) requirements ..... | 50 |
+| 6.8.7.3 | Imminent Peril group call requirements ..... | 50 |
+| 6.8.7.4 | MCPTT Emergency Alert..... | 50 |
+| 6.8.7.4.1 | Requirements..... | 50 |
+| 6.8.7.4.2 | MCPTT Emergency Alert cancellation requirements ..... | 50 |
+| 6.9 | IDs and aliases..... | 50 |
+| 6.10 | User Profile management..... | 50 |
+| 6.11 | Support for multiple devices ..... | 51 |
+| 6.12 | Location..... | 51 |
+| 6.13 | Security..... | 51 |
+| 6.13.1 | Overview ..... | 51 |
+| 6.13.2 | Cryptographic protocols ..... | 51 |
+| 6.13.3 | Authentication ..... | 51 |
+| 6.13.4 | Access control ..... | 51 |
+| 6.13.5 | Regulatory issues..... | 52 |
+| 6.14 | Interactions for MCPTT Group Calls and MCPTT Private Calls..... | 52 |
+| 6.15 | Audio MCPTT call performance..... | 52 |
+| 6.15.1 | General overview..... | 52 |
+| 6.15.2 | General requirements..... | 52 |
+| 6.15.3 | MCPTT access time and mouth-to-ear latency ..... | 52 |
+| 6.15.3.1 | General overview ..... | 52 |
+| 6.15.3.2 | Requirements ..... | 53 |
+
+| | | |
+|------------|-----------------------------------------------------------------|----|
+| 6.15.4 | Late call entry performance..... | 54 |
+| 6.15.4.1 | General overview ..... | 54 |
+| 6.15.4.2 | Requirements ..... | 55 |
+| 6.15.5 | Audio / voice quality ..... | 56 |
+| 6.15.6 | Radio Resource Efficiency Performance..... | 56 |
+| 6.16 | Additional services for MCPTT calls..... | 56 |
+| 6.16.1 | Discreet listening capabilities..... | 56 |
+| 6.16.2 | Ambient listening ..... | 56 |
+| 6.16.2.1 | Overview of ambient listening..... | 56 |
+| 6.16.2.2 | Ambient listening requirements..... | 56 |
+| 6.16.2.2.1 | General Ambient Listening requirements ..... | 56 |
+| 6.16.2.2.2 | Remotely initiated Ambient Listening requirements ..... | 57 |
+| 6.16.2.2.3 | Locally initiated Ambient Listening requirements..... | 57 |
+| 6.16.3 | Remotely initiated MCPTT call ..... | 57 |
+| 6.16.3.1 | Overview ..... | 57 |
+| 6.16.3.2 | Requirements..... | 57 |
+| 6.16.4 | Recording and audit requirements..... | 58 |
+| 6.17 | Interaction with telephony services..... | 58 |
+| 6.18 | Interworking ..... | 58 |
+| 6.18.1 | Non-3GPP access ..... | 58 |
+| 6.18.2 | Interworking between MCPTT systems..... | 58 |
+| 6.18.3 | Interworking with non-3GPP PTT systems..... | 58 |
+| 6.18.3.1 | Overview..... | 58 |
+| 6.18.3.2 | Project 25 ..... | 59 |
+| 6.18.3.3 | TETRA..... | 60 |
+| 6.18.3.4 | Legacy land mobile radio ..... | 61 |
+| 6.18.3.5 | Void ..... | 61 |
+| 6.18.4 | GSM-R ..... | 61 |
+| 6.18.4.1 | Overview..... | 61 |
+| 6.18.4.2 | Requirements ..... | 61 |
+| 6.19 | MCPTT coverage extension using ProSe UE-to-Network Relays ..... | 62 |
+| 7 | MCPTT Service requirements specific to off-network use ..... | 62 |
+| 7.1 | Off-network Push To Talk overview ..... | 62 |
+| 7.2 | General off-network MCPTT requirements..... | 64 |
+| 7.3 | Floor control..... | 64 |
+| 7.3.1 | General aspects ..... | 64 |
+| 7.3.2 | Requesting permission to transmit ..... | 64 |
+| 7.3.3 | Override ..... | 64 |
+| 7.3.4 | Terminating permission to transmit..... | 65 |
+| 7.3.5 | Transmit time limit ..... | 65 |
+| 7.4 | Call Termination ..... | 65 |
+| 7.5 | Broadcast Group..... | 65 |
+| 7.6 | Dynamic group management (i.e., dynamic regrouping)..... | 66 |
+| 7.7 | MCPTT priority requirements..... | 66 |
+| 7.8 | Call types based on priorities ..... | 66 |
+| 7.8.1 | MCPTT Emergency Group Call requirements ..... | 66 |
+| 7.8.2 | MCPTT Emergency Group Call cancellation requirements..... | 66 |
+| 7.8.3 | Imminent Peril Call ..... | 66 |
+| 7.8.3.1 | Imminent Peril group call requirements..... | 66 |
+| 7.8.3.2 | Imminent Peril group call cancellation requirements ..... | 66 |
+| 7.9 | Location..... | 66 |
+| 7.10 | Security..... | 66 |
+| 7.11 | Audio MCPTT Call performance..... | 67 |
+| 7.11.1 | MCPTT Access time and Mouth-to-ear latency..... | 67 |
+| 7.11.1.1 | General overview ..... | 67 |
+| 7.11.1.2 | Requirements ..... | 67 |
+| 7.11.2 | Late call entry performance..... | 67 |
+| 7.11.2.1 | General overview ..... | 67 |
+| 7.11.2.2 | Requirements ..... | 67 |
+| 7.11.3 | Audio / Voice quality ..... | 68 |
+| 7.12 | Off-network MCPTT operations..... | 68 |
+
+| | | |
+|-------------------------------------------------------------------|----------------------------------------------------|-----------|
+| 7.13 | Off-network UE functionality ..... | 68 |
+| 7.14 | Switching to off-network MCPTT ..... | 68 |
+| 7.15 | Off-network recording and audit requirements ..... | 68 |
+| 7.16 | Off-network UE-to-UE Relay ..... | 68 |
+| 7.16.1 | Private Calls..... | 68 |
+| 7.16.2 | Group Calls..... | 68 |
+| Annex A (informative): Variables ..... | | 69 |
+| Annex A1 (Informative): MCPTT Requirements for MCCoRe..... | | 69 |
+| Annex B (informative): Bibliography..... | | 84 |
+| Annex C (informative): MCPTT scalability guide..... | | 85 |
+| Annex D (informative): Change history..... | | 86 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 present document covers requirements for Mission Critical Push To Talk (MCPTT) service (represented by the term, MCPTT Service). The MCPTT Service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways). The specifications contained within the present document can also form the basis for a non-mission critical Push To Talk service (called a PTT service).
+
+Note that further development of mission critical services beyond MCPTT (such as Mission Critical Video and Mission Critical Data) created an opportunity to re-use base functionality documented in the Stage 1 requirements for MCPTT. For example, the ability to communicate mission critical information to groups of users is a common need regardless of service type. Wherever originating MCPTT requirements were found to be in common with other mission critical services, those requirements were moved to a new Technical Specification (3GPP TS 22.280). Each requirement that was moved has been voided in this version of 3GPP TS 22.179, and an informative annex has been created at the end of this specification documenting the location of the originating 3GPP TS 22.179 requirement in 3GPP TS 22.280.
+
+# 1 Scope
+
+The present document provides the service requirements for operation of the MCPTT Service. MCPTT makes use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service. The MCPTT Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.
+
+# 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] TSB-102-B: "Project 25 TIA-102 Document Suite Overview".
+- [3] TIA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards".
+- [4] TIA-102.BABA: "Vocoder Description".
+- [5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+- [6] 3GPP TS 22.468: "Group Communication System Enablers for LTE (GCSE\_LTE)".
+- [7] ITU-T Recommendation P.862: "Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs".
+- [8] ITU-T Recommendation P.862.1: "Mapping function for transforming P.862 raw result scores to MOS-LQO".
+- [9] ITU-T Recommendation P.863: "Perceptual objective listening quality assessment".
+- [10] TIA-102.BABG: "Enhanced Vocoder Methods of Measurement for Performance", March 2010.
+- [11] 3GPP TS 26.190: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions".
+- [12] 3GPP TS 26.194: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Voice Activity Detector (VAD)".
+- [13] 3GPP TS 22.011: "Service accessibility".
+- [14] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Stations (MS) in idle mode".
+- [15] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
+- [16] ISBN 2-7461-1832-4: "UIC Project EIRENE System Requirements Specification".
+
+[17] ETSI EN 301 515 V3.0.0 (2018-03): "Global System for Mobile communication (GSM); Requirements for GSM operation on railways".
+
+# --- 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]. Definitions provided in 3GPP TS 22.280 [15] also apply to this specification.
+
+**Affiliated MCPTT Group Member:** An MCPTT Group Member who has indicated an interest in the group and is prepared to receive and/or transmit Group Communications from/to the particular MCPTT Group.
+
+**Automatic Commencement Private Call:** A Private Call in which the initiation of the Private Call does not require any action on the part of the receiving MCPTT User.
+
+**Broadcast Group Call:** A group call where the initiating MCPTT User expects no response from the other MCPTT Users, so that when his transmission is complete, so is the call.
+
+**Call Commencement Mode:** This is a setting that determines the conditions under which a call is started.
+
+**Dispatcher:** An MCPTT User who participates in MCPTT communications for command and control purposes.
+
+**Floor control:** An arbitration system in an MCPTT Service that determines who has the authority to transmit (talk) at a point in time during an MCPTT call.
+
+**Group-Broadcast Group:** A collection of groups defined by the MCPTT Administrator (e.g., representing a particular organizational structure) and intended to be the recipients of Broadcast Group Calls.
+
+**Group Regroup:** The temporary combining of a multiplicity of groups into a single group.
+
+**Hang Time:** A configurable maximum length of the inactivity (silence) period between consecutive MCPTT transmissions within the same call.
+
+**Imminent Peril Call:** An urgent MCPTT Group call that highlights the potential of death or serious injury, but is less critical than an MCPTT Emergency Group Call. For example a call prioritized in the event of immediate threat to any human life such as resulting from an MCPTT User's observation of or engagement in a situation involving imminent peril to the general public (e.g., a forest fire about to encircle campers, tanker truck ready to explode near a school, casualties at the scene of a car bombing).
+
+**In-progress Emergency:** An emergency condition for a group that has been accepted by the MCPTT Service, but has not yet been cancelled by an authorized user.
+
+**In-progress Imminent Peril:** An imminent peril condition for a group that has been accepted by the MCPTT Service and has not yet been cancelled by an authorized MCPTT User.
+
+**Late call entry:** An Affiliated MCPTT Group Member joins in an in progress MCPTT Group Call.
+
+**Location:** The current physical location (i.e., co-ordinates plus estimated accuracy and timestamp) of the MCPTT UE that can be cross-referenced to a map.
+
+**Losing audio:** Audio of an overridden talker that is routed to selected authorized MCPTT Users.
+
+**Manual Commencement Private Call:** A Private Call in which the initiation of the Private Call requires the receiving MCPTT User to perform some action to accept or reject the Private Call setup.
+
+**MCPTT Administrator:** An individual authorized to control parameters of the MCPTT Service for an organization including, for example, user and group definition, user/group aliases, user priorities, group membership/priorities/hierarchies, security and privacy controls.
+
+**MCPTT Emergency Alert:** A notification from the MCPTT UE to the MCPTT Service that the MCPTT User has an emergency condition.
+
+**MCPTT Emergency Group Call:** An urgent MCPTT Group call that highlights the potential of death or serious injury to the initiator.
+
+**MCPTT Emergency Private Call:** An urgent MCPTT Private Call that highlights the potential of death or serious injury to the initiator.
+
+**MCPTT Emergency State:** A heightened condition of alarm for an MCPTT User indicating a need for immediate assistance due to a personal life-threatening situation.
+
+**MCPTT Group:** A defined set of MCPTT Users identified independently of transport or network type.
+
+**MCPTT Group Member:** An MCPTT User who has been authorized to participate in Group Communications of a particular MCPTT Group.
+
+**MCPTT Request:** The action taken by an MCPTT User to request the permission to transmit voice on a call.
+
+**MCPTT Service:** A Push To Talk communication service supporting applications for Mission Critical Organizations and mission critical applications for other businesses and organizations (e.g., utilities, railways) with fast setup times, high availability, reliability and priority handling.
+
+**MCPTT system:** The collection of applications, services, and enabling capabilities required to provide Mission Critical Push To Talk for a Mission Critical Organization.
+
+**MCPTT UE:** A UE that enables an MCPTT User to participate in MCPTT Service.
+
+**MCPTT User:** A user of an MCPTT Service, who has a device with the capability to participate in MCPTT Services.
+
+**MCPTT User Profile:** The set of information that allows an MCPTT User to employ the MCPTT Service in a given role and/or from a given MCPTT device.
+
+**Mission Critical Push To Talk:** A group communication service with fast setup times, ability to handle large groups, strong security and priority handling.
+
+**Off-Network MCPTT Service:** The collection of functions and capabilities required to provide MCPTT using ProSe Discovery and the ProSe Communication path for MCPTT Users using Public Safety ProSe-enabled UEs as a direct communication between UEs.
+
+**Partner MCPTT System:** Allied MCPTT system that provides MCPTT Services to an MCPTT User based on the MCPTT User Profile that is defined in the Primary MCPTT System of that MCPTT User.
+
+**Pre-emption:** The act of terminating on-going calls in order to free up resources for a higher priority call request.
+
+**Primary MCPTT System:** MCPTT system where the MCPTT User Profile of an MCPTT User is defined.
+
+**Private Call:** A call between a pair of MCPTT Users using the MCPTT Service with or without MCPTT Floor control.
+
+**Project 25 RFSS:** A Project 25 Radio Frequency (RF) Subsystem as defined in TSB-102-B [2].
+
+**Receiving MCPTT Group Member:** An Affiliated MCPTT Group Member who is currently receiving Group Communication from an MCPTT Group.
+
+**Selected MCPTT Group:** The MCPTT Group that a particular Affiliated MCPTT Group Member uses for transmission.
+
+**System Call:** A special case of a Broadcast Group Call that is transmitted to all users in a dynamically defined geographic area.
+
+**Transmitting MCPTT Group Member:** An Affiliated MCPTT Group Member who is currently transmitting a Group Communication to a Selected MCPTT Group.
+
+**User-Broadcast Group:** A collection of users defined by the MCPTT Administrator (e.g., representing a particular organizational structure) and intended to be the recipients of Broadcast Group Calls.
+
+**User ID:** The main unique identifier for an MCPTT User.
+
+**User Regroup:** The temporary combining of a multiplicity of users into a new group.
+
+## 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].
+
+| | |
+|----------|-------------------------------------------------------------------------------|
+| FIFO | First In First Out |
+| GCSE_LTE | Group Communication System Enablers for LTE |
+| KPI | Key Performance Indicator |
+| MCPTT | Mission Critical Push To Talk |
+| MOS-LQO | Mean Opinion Score – Listening Quality Objective |
+| P25 | Project 25 |
+| PESQ | Perceptual Evaluation of Speech Quality |
+| POLQA | Perceptual Objective Listening Quality Assessment |
+| ProSe | Proximity Services |
+| PTT | Push To Talk |
+| RFSS | Radio Frequency (RF) Subsystem as defined in the TTA-102 specifications (P25) |
+| TETRA | Terrestrial Trunked Radio |
+| TIA | Telecommunications Industry Association |
+| UIC | Union Internationale des Chemins de Fer |
+
+# --- 4 Mission Critical Push To Talk overview
+
+## 4.1 General
+
+A Push To Talk service provides an arbitrated method by which two or more users may engage in communication. Users may request permission to transmit (e.g., traditionally by means of a press of a button). The Mission Critical Push To Talk (MCPTT) service supports an enhanced PTT service, suitable for mission critical scenarios, based upon 3GPP system services. The requirements for Mission Critical Push To Talk (MCPTT) service defined within can also form the basis for a non-mission critical Push To Talk (PTT) service.
+
+The MCPTT Service is intended to support communication between several users (a group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. However, the MCPTT Service also supports Private Calls between pairs of users. The MCPTT Service builds on the existing 3GPP transport communication mechanisms provided by the 3GPP architectures to establish, maintain, and terminate the actual communication path(s) among the users.
+
+The MCPTT Service also builds upon service enablers: Group Communications System Enablers and Proximity Services. To the extent feasible, it is expected that the end user's experience to be similar regardless if the MCPTT Service is used under coverage of a 3GPP network or based on ProSe without network coverage. To clarify this intent, the requirements are grouped according to applicability to on-network use, off-network use, or both.
+
+Though the MCPTT Service primarily focuses on the use of the 3GPP system there might be users who access the MCPTT Service through non-3GPP access technology, dispatchers and administrators are examples of this. Dispatchers and administrators are special users who have particular admin and call management privileges which normal users might not have. In MCPTT dispatchers can use an MCPTT UE (i.e., 3GPP) or a non-3GPP access connection to the MCPTT Service based on a "dispatcher and Administrator" interface. Through this interface a user is able to access and manage the services related to on the network and those common to on the network and off the network.
+
+The MCPTT Service allows users to request the permission to talk (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control). When multiple requests occur, the determination of which user's request is accepted and which users' requests are rejected or queued is based upon a number of characteristics (including the respective priorities of the users in contention). MCPTT Service provides a means for a user with higher priority (e.g., MCPTT Emergency condition) to override (interrupt) the current talker. MCPTT Service also supports a mechanism to limit the time a user talks (hold the floor) thus permitting users of the same or lower priority a chance to gain the floor.
+
+The MCPTT Service provides the means for a user to monitor activity on a number of separate calls and enables the user to switch focus to a chosen call. An MCPTT Service user may join an already established MCPTT Group call (Late call entry). In addition the MCPTT Service provides the User ID of the current speaker(s) and user's Location determination features.
+
+The users of an MCPTT Service may have more stringent expectations of performance than the users of a commercial PTT service.
+
+MCPTT is primarily targeting to provide a professional Push To Talk service to e.g., public safety, transport companies, utilities or industrial and nuclear plants. In addition to this a commercial PTT service for non-professional use (e.g., groups of people on holiday) may be delivered through an MCPTT system. Based on their operational model, the performance and MCPTT features in use vary per user organization, where functionality which is more mission critical specific (e.g., Ambient Listening and Imminent Peril Call) might not be available to commercial customers.
+
+MCPTT Users expect to communicate with other MCPTT Users as outlined above, however MCPTT Users also need to be able to communicate with non MCPTT Users using their MCPTT UEs for normal telephony services.
+
+## 4.2 Typical use of the MCPTT Service
+
+**NOTE:** Even though this subclause is written from an organization specific perspective the text is illustrative for typical use of MCPTT Services by all MCPTT Users.
+
+Public safety workers often operate in groups and perform different tasks during the day/week. Many tasks and operations are controlled, assisted and/or coordinated by a dispatcher.
+
+For their communications public safety workers are organized in groups. People that are working together communicate in the same MCPTT Group, the group communication helping them to coordinate quickly.
+
+People with different tasks often communicate in separate MCPTT Groups.
+
+Many of the public safety tasks are routine tasks, that are handled by standard procedures and communication structures, using dedicated MCPTT Groups. Communication structures and MCPTT Groups are also prepared for the handling of large incidents and control of large events. Similarly there are MCPTT Groups and procedures for coordination with public safety workers from other organizations and/or other countries.
+
+The standard procedures and communication structures help the public safety workers to do their work successfully. This results in a long list of (>100) MCPTT Groups available to a public safety worker, from which the correct one is selected depending on the task. To help the public safety worker to quickly find and select the correct MCPTT Group for the task, the MCPTT Groups in the radio are often structured in folders and/or accessible via key-shortcuts. In addition to pre-established MCPTT Groups that users select, there are also provisions in MCPTT systems to merge MCPTT Groups and to select on behalf of a user which group they should be using and for a dispatcher to push them onto it. The large number of MCPTT Groups provisioned on devices is helpful for the device to be able to operate on the network and off the network. However the ability to provision over the air is also seen as a very useful feature, as currently Land Mobile Radio devices often have to be locally re-programmed, rather than updated over the air.
+
+## 4.3 Overview of MCPTT Group affiliation, call and transmission
+
+An MCPTT Service provides Group Call and Private Call capabilities, which have various process flows, states and permissions associated with them. The figure 4.3.1, figure 4.3.2, and figure 4.3.3 indicate the high level flows, states and permissions associated with Group Calls and Private Calls. The diagrams apply to the on-network case and off-network case, as from a user perspective the service and concepts should appear similar on the network and off the network. From a technical perspective there might be differences between the on-network states and off-network states (e.g., off the network Affiliation might not require notifying an application server of a user's affiliation and there might also be other differences in the detail depending on the extent to which the off-network capabilities can match the on-network capabilities).
+
+If an MCPTT User wants to communicate with an MCPTT Group they have to be allowed to access the MCPTT Group (i.e., be an MCPTT Group Member), they then have to affiliate and then can have an MCPTT Group as their Selected MCPTT Group. If an MCPTT User is only affiliated to a group this is so that they can receive from the group, however if an MCPTT User has a Selected MCPTT Group this is their group for transmitting on. The differences in states enable an MCPTT User to receive from multiple MCPTT Groups, but specify which MCPTT Group they would like to transmit on.
+
+Both receive and transmit allowed for an MCPTT User with respect to a particular MCPTT Group.
+
+
+
+The diagram illustrates the state transitions for an MCPTT User, organized into two main vertical sections: **Group call** (top) and **Private call** (bottom), separated by a dashed line.
+
+- Group call section:**
+ - The outermost state is **MCPTT User**, which contains a **Standby** state (initial state).
+ - From **MCPTT User Standby**, an **Indicate interest [MCPTT Group Member]** transition leads to the **Affiliated MCPTT Group Member** state.
+ - From **Affiliated MCPTT Group Member**, a **Remove interest** transition returns to **MCPTT User Standby**.
+ - The **Affiliated MCPTT Group Member** state contains a sub-state machine for the **MCPTT Group Selected**:
+ - Initial state of the sub-machine is **Standby**.
+ - Transitions from **Standby** to **Transmitting MCPTT Group Member**: **Request & Granted floor**.
+ - Transitions from **Transmitting MCPTT Group Member** to **Standby**: **Time out, Override, Pre-empted or stop transmit**.
+ - Transitions from **Transmitting MCPTT Group Member** to **Receiving MCPTT Group Member**: **Override [MCPTT Request accepted]**.
+ - Transitions from **Receiving MCPTT Group Member** to **Standby**: **Stop Receiving Audio**.
+ - Transitions from **Standby** to **Receiving MCPTT Group Member**: **Audio Received**.
+ - External transitions to the **MCPTT Group Selected Standby** state include: **Select Group** (from **Affiliated MCPTT Group Member**), **De-select Group** (from **Receiving MCPTT Group Member**), and **Stop Receiving Audio** (from **Receiving MCPTT Group Member**).
+- Private call section:**
+ - States: **Transmitting or Receiving in a Private Call** and **Standby** (initial state).
+ - Transition from **Standby** to **Transmitting or Receiving in a Private Call**: **Private call initiated [authorised Private call]**.
+ - Transition from **Transmitting or Receiving in a Private Call** to **Standby**: **Private call terminated**.
+- Potential Interactions:** Dotted double-headed arrows connect the **MCPTT User Standby** state with both the **Private call Standby** state and the **Transmitting or Receiving in a Private Call** state, indicating potential interactions between Group and Private calls.
+
+**Key:**
+
+- Start state
+- Separates Orthogonal states, ie transitions in Group call happen in parallel to Private call.
+- State
+- [event] Indicates conditionality, if condition inside brackets is TRUE, then transition will occur.
+- ↶ Potential Interactions, Parallel States or Potential Transitions
+- Transitions between states
+
+MCPTT User state diagram showing Group call and Private call states.
+
+NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
+
+**Figure 4.3.1: MCPTT User state diagram- transmit and receive for a particular MCPTT Group**
+
+Transmit only allowed for an MCPTT User with respect to a particular MCPTT Group.
+
+
+
+**MCPTT User**
+
+**Group call**
+
+MCPTT User Affiliated to 'm' Groups and has a maximum of 1 Group Selected [as authorised]
+
+**Affiliated MCPTT Group Member**
+
+Indicate interest [MCPTT Group Member]
+
+**Standby**
+
+Remove interest
+
+**MCPTT Group Selected**
+
+**Standby**
+
+Select Group
+
+De-select Group
+
+Time out, Override, Pre-empted or stop transmit
+
+Request & Granted floor
+
+**Transmitting MCPTT Group Member**
+
+**Private call**
+
+**Transmitting or Receiving in a Private Call**
+
+Private call initiated [authorised Private call]
+
+Private call terminated
+
+**Standby**
+
+**Key**
+
+- Start state
+- Separates Orthogonal states , ie transitions in Group call happen in parallel to Private call.
+- ⋯ Potential Interactions, Parallel States or Potential Transitions
+- State [event] Indicates conditionality, if condition inside brackets is TRUE, then transition will occur.
+- Transitions between states
+
+MCPTT User state diagram showing Group call and Private call states. The diagram is divided into two main sections by a dashed line. The top section, 'Group call', contains a state 'Affiliated MCPTT Group Member' which includes a sub-state 'MCPTT Group Selected'. Transitions include 'Indicate interest', 'Select Group', 'De-select Group', 'Time out, Override, Pre-empted or stop transmit', and 'Request & Granted floor'. The bottom section, 'Private call', contains states 'Transmitting or Receiving in a Private Call' and 'Standby', with transitions 'Private call initiated' and 'Private call terminated'. A 'Key' at the bottom explains the symbols used: solid line for state transitions, dashed line for orthogonal state separation, dotted line for potential interactions, solid circle for start state, and rounded rectangle for a state with conditional events.
+
+NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
+
+**Figure 4.3.2: MCPTT User state diagram- transmit only for a particular MCPTT Group**
+
+Receive only allowed for an MCPTT User with respect to a particular MCPTT Group.
+
+
+
+The diagram illustrates the state transitions for an MCPTT User, organized into two main vertical compartments: 'Group call' and 'Private call', separated by a dashed line.
+
+- Group call compartment:**
+ - Contains a sub-state 'Affiliated MCPTT Group Member' (indicated by a note: 'MCPTT User Affiliated to 'm' Groups and has a maximum of 1 Group Selected [as authorised]').
+ - Inside this sub-state, there are two states: 'Standby' (start state) and 'Receiving MCPTT Group Member'.
+ - Transitions: 'Standby' to 'Receiving MCPTT Group Member' is triggered by 'Audio Received'; 'Receiving MCPTT Group Member' to 'Standby' is triggered by 'Stop Receiving Audio'.
+ - Outside the sub-state but within the 'Group call' compartment, there is another 'Standby' state.
+ - Transitions to this 'Standby' state: from 'Affiliated MCPTT Group Member' (trigger: 'Indicate interest [MCPTT Group Member]') and from 'Receiving MCPTT Group Member' (trigger: 'Remove interest').
+- Private call compartment:**
+ - Contains two states: 'Transmitting or Receiving in a Private Call' and 'Standby' (start state).
+ - Transitions: 'Transmitting or Receiving in a Private Call' to 'Standby' (trigger: 'Private call terminated'); 'Standby' to 'Transmitting or Receiving in a Private Call' (trigger: 'Private call initiated [authorised Private call]').
+- Potential Interactions:** Dotted double-headed arrows connect 'Standby' in the Group call compartment with 'Standby' in the Private call compartment, and also connect 'Affiliated MCPTT Group Member' with 'Standby' in the Private call compartment.
+
+**Key:**
+
+- Start state
+- Separates Orthogonal states, i.e. transitions in Group call happen in parallel to Private call.
+- <---> Potential Interactions, Parallel States or Potential Transitions
+- State [event] Indicates conditionality, if condition inside brackets is TRUE, then transition will occur.
+- Transitions between states
+
+MCPTT User state diagram- receive only for a particular MCPTT Group
+
+NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
+
+**Figure 4.3.3: MCPTT User state diagram- receive only for a particular MCPTT Group**
+
+It is possible for an MCPTT User to be affiliated with one or more MCPTT Groups. Normally, while in operation, an MCPTT User informs the MCPTT Service about which MCPTT Groups he would like to be affiliated to. These affiliations remain in effect until the MCPTT User removes them, or changes them, or signs out of the service. Some MCPTT Users have permanent affiliations to certain MCPTT Groups and those affiliations are set up implicitly (i.e., automatically) when operating on the network. For those users, the MCPTT Group affiliation starts when the MCPTT Service successfully signs in the user and ends when the MCPTT User's explicit or implicit (e.g., due to inactivity or the turning off of all its devices) request to sign out of the MCPTT Service is acknowledged.
+
+Every time a PTT request is granted a user can start an MCPTT transmission or "talk burst". An MCPTT Group Call consists of one or more MCPTT transmissions. Whether two consecutive transmissions from same or different users are part of the same call, or the second transmission starts a new call, depends on the configurable maximum length of the inactivity period between the consecutive MCPTT transmissions. This inactivity period can be seen as a Hang Time that starts at the end of the preceding transmission. While this timer is running, the resources associated with the call stay assigned to the call (except in case of pre-emption), which could reduce the latency of future floor requests for this group versus groups who are not involved in a call. When a new transmission starts during the inactivity period, the timer is stopped, reset and restarted again at the end of that transmission.
+
+The MCPTT Service recognizes a number of "special" group calls including: Broadcast Group Call, Emergency Group Call and Imminent Peril group call.
+
+A Broadcast Group Call can be seen as a special group call with only one MCPTT transmission.
+
+While the In-progress Emergency state or In-progress Imminent Peril state is active, the inactivity period is conceptually set to infinity; i.e., the resources assigned to calls during these states are never released (except in case of pre-emption). An MCPTT Emergency Group Call or an Imminent Peril group call can be seen as having an unspecified number of transmissions: essentially, all the transmissions to a group during In-progress Emergency state or In-progress Imminent Peril are part of the same MCPTT Group Call.
+
+Conditions on starting ("commencement") and continuing an MCPTT call can be established. Usually at least the call initiator (but also other users) are kept informed via notifications of the starting, stopping, queuing, etc., of a call.
+
+In general, commencement conditions are related to the presence on the call (i.e., participation) of certain members of the group, and/or of a minimum number of members, as well as on the availability of resources (e.g., GBR bearers) of proper ARP. If the commencement conditions are not met, the call does not start (it can be queued or rejected). Normally, commencement conditions are not checked for individual transmission within a call.
+
+Continuation conditions are similar (though not required to be identical) to commencement conditions and get re-evaluated when pre-emption, degradation of priority, motion out of communication range, de-selection of the group or de-affiliation (explicit or implicit) occur. If the continuation conditions are not met, the call stops.
+
+## 4.4 General handling of requests
+
+Request handling is by no means specific only to MCPTT Service, but it plays a central role in its functionality.
+
+Requests appear in the MCPTT Service in many forms and under many circumstances: e.g., requests for the floor during a call, requests for starting a call, requests for resources. Conceptually, requests are accompanied by priority information that is used in the arbitration, in case of contention; see also subclause 4.6 for a brief explanation and examples on how priority processing is modelled.
+
+Upon arrival, a request is immediately granted, denied, or queued.
+
+If queued, a request can be dropped due to queue overflow (i.e., too many items queued) or can be cancelled by an authorized user, who is usually the initiator of the request. Either way, the net result is that the request is denied.
+
+When a request denial is communicated, the request may be re-requested either manually by user action or automatically. In the automatic case, while the request remains denied, it may be automatically repeated a configurable number of times where a minimum time interval between re-transmissions may also be applied.
+
+There are many "queuing disciplines" possible that govern the placement of items in a queue and their subsequent removal from the queue: e.g., FIFO, priority order. Assuming that the queuing discipline chosen places the highest priority requests towards the top of the queue, the granted request is either, depending on the design and configuration, the front-most entry in the queue or the first entry counting from the top that can be satisfied by the available resources. For example, if the topmost entry in the queue is awaiting for ten GBR bearers of given characteristics to become available and the second entry in the queue is waiting for seven GBR bearers to become available, and at some point in time eight GBR bearers become available, then it is possible that the second request is granted ahead of the first one, which continues to wait. Alternatively, neither the first request nor the second request is granted and the wait continues until at least ten GBR bearers become available, at which time the first request is granted while the second request continues to wait.
+
+## 4.5 Overview of MCPTT UE and MCPTT User in the MCPTT Service
+
+The MCPTT Service supports MCPTT User Profiles. The MCPTT User Profile contains important information related to the MCPTT User receiving the MCPTT Service, including the MCPTT User identity, which is globally unique and independent of the mobile subscriber identity (IMSI) assigned by a 3GPP network operator. Part of the content of the MCPTT User Profile (e.g., containing some display preferences, some UE audio settings, some address books) can be set/modified/updated by the MCPTT User, but significant portions might be set/modified/updated only by authorized persons. The MCPTT User Profile is stored permanently in database(s) associated with the infrastructure providing the MCPTT Service. Relevant parts of the profile might be downloaded to and cached temporarily or permanently on certain MCPTT UEs. When stored on an MCPTT UE, the MCPTT User Profile associated with an MCPTT User might be confidentiality and integrity protected, with the information available only to a trusted application client associated to the MCPTT User, upon authentication. The MCPTT User Profile information can be synchronized automatically or on demand between the cache on the MCPTT UE and the main copy held in the database(s) of the MCPTT Service infrastructure. The MCPTT User Profile is part of the MCPTT application service domain and forms the basis of MCPTT application layer security and identifies an MCPTT User to the MCPTT Service.
+
+Each MCPTT User has at least one MCPTT User Profile, and possibly several. Typically, one of the MCPTT User Profiles is designated as the default MCPTT User Profile, to be used unless an MCPTT User Profile is explicitly selected. In general, a user profile is associated with a specific device, with a specific mode of operation (i.e., on the
+
+network or off the network) and/or with a specific situation (e.g., user being off-duty, in a certain city, or playing a certain role). When an MCPTT User Profile is synchronized between the infrastructure and an MCPTT device, information could be downloaded to the device and updated, as necessary. Subsequently and subject to permissions, the MCPTT User might choose a different associated MCPTT User Profile to be downloaded and stored on the device. Only one MCPTT User Profile is active at a time. Authorized users are allowed to create, delete and alter MCPTT User Profiles for an MCPTT User and/or pre-stored MCPTT User Profiles.
+
+The MCPTT Service supports MCPTT UEs which connect to the MCPTT Service. The capabilities of an MCPTT UE are specified in the present document. The MCPTT Application that is resident on the MCPTT UE establishes this connection, employing application layer security in its connection to the MCPTT Service. An MCPTT UE is capable of operating in on-network and off-network modes.
+
+### 4.5.1 MCPTT User association to MCPTT UE in on-network mode
+
+Consistent with the 3GPP paradigm, when an MCPTT UE is powered on, it accesses the 3GPP system, and connects to the 3GPP network. During this phase, the credentials from a USIM application (or possibly, an ISIM application, if IMS is used) on a UICC associated with the MCPTT UE is used for authentication with an HSS. This is followed by the MCPTT Application, resident on the MCPTT UE, establishing a connection, employing application layer security in its connection to the MCPTT Service.
+
+Possibilities for the MCPTT UE, when connecting to the MCPTT Service:
+
+- An MCPTT UE, with credentials of an MCPTT User at the time of connection to the MCPTT Service, is able to authenticate using a specific MCPTT User identity (e.g., via an Identity Management service). After successful user authentication the MCPTT User Profiles are made available to the MCPTT UE for use in both on-network and off-network operation modes.
+- An MCPTT UE, without credentials of a specific MCPTT User at the time of connection to the MCPTT Service, proceeds using a default identity associated with the MCPTT UE itself. In this case, the MCPTT Service is capable of assigning a temporary MCPTT User Identity to this MCPTT UE. Some level of authentication might be attempted, and, depending on the results, an appropriate MCPTT User Profile associated with this temporary MCPTT User Identity and with the circumstances of the access is made available to the MCPTT UE for use in both on-network and off-network operation modes.
+- The MCPTT Administrator is able to retrieve hardware and software parameters to define specific parameters and attributes (e.g., groups, MCPTT Emergency behaviour, priority and QoS attributes) associated with a temporary MCPTT User Identity for operation of the MCPTT UE for use in both on-network and off-network operation modes.
+
+### 4.5.2 MCPTT User and MCPTT UE relationship
+
+A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application.
+
+The MCPTT Service allows the same MCPTT User to sign in (and stay simultaneously signed in) from different MCPTT UEs. For example, an incident manager or commander might use a portable phone, a command tablet, or a separate messaging unit.
+
+### 4.5.3 MCPTT Users accessing the service through non-3GPP access interface
+
+This document primarily focuses on MCPTT Users accessing and managing the MCPTT Service through MCPTT UEs, however there might be some dispatchers and administrators who might access the service through a non-3GPP access interface.
+
+### 4.5.4 Shareable MCPTT UEs and gateway UEs
+
+The conceptual model for shareable MCPTT UEs is that of a pool of UEs, each UE being interchangeable with any other, and users randomly choosing one or more UEs from the pool, each user for his temporary exclusive use. A shareable MCPTT UE can be used by user who can gain access to the MCPTT client application stored on it and can
+
+become an authenticated MCPTT User. A shareable MCPTT UE can serve only one MCPTT User at a time. An MCPTT User who signs into a shareable MCPTT UE that is already in-use causes the sign-off of the previous MCPTT User.
+
+An MCPTT User can simultaneously have several active MCPTT UEs, which, from an MCPTT Service point of view, are addressable individually and/or collectively within the context of their association to the MCPTT User.
+
+The conceptual model for a gateway UE is that of a UE capable of providing service to an MCPTT User employing a non-3GPP device. A gateway UE is usable simultaneously by multiple MCPTT Users. Unlike a shareable MCPTT UE, if a new person enters his valid credentials towards signing in the MCPTT Service, his successful signing in and becoming an MCPTT User does not affect the initial MCPTT Users already served by the gateway UE.
+
+A gateway UE is typically installed in a vehicle (e.g., a police car, fire truck) and has wired and/or wireless connections to various devices in use by the MCPTT Users.
+
+A gateway UE differs functionally from a ProSe relay node. In the ProSe paradigm, the relay node and the devices served by it are all (ProSe enabled) 3GPP UEs, and are "visible" to the 3GPP system as UEs. In the gateway UE paradigm, only the gateway UE is an 3GPP device and only it is "visible" at the 3GPP network layer.
+
+Figure 4.5.4.1 shows schematically some of the relationships between MCPTT Users and MCPTT UEs.
+
+
+
+Figure 4.5.4-1: Relationships between MCPTT Users and MCPTT UEs. The diagram shows an MCPTT Application on the left connected to four users: UserA, UserB, UserC, and UserD. UserA is labeled 'User with multiple UEs' and is connected to three UEs: UE0, UE1, and UE2. UserB is connected to UE2. UserC is connected to UE3, which is labeled 'Gateway UE'. UserD is connected to UE4. All UEs (UE0, UE1, UE2, UE3, UE4) are connected to a single LTE EPS on the right. A vertical dashed line separates the 'Application Function' (left) from the 'LTE Transport' (right).
+
+**Figure 4.5.4-1: Relationships between MCPTT Users and MCPTT UEs**
+
+### 4.5.5 MCPTT User association to MCPTT UE in off-network mode
+
+A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application.
+
+After successful local user authentication an MCPTT User Profile, which was previously made available to the MCPTT UE, is used for off-network operation mode. This previously configured MCPTT User Profile information allows the MCPTT User to be identified using the same MCPTT User Identity as in the on-network mode.
+
+An MCPTT UE, without credentials of a specific MCPTT User, operates in off-network mode, if so configured by an MCPTT Administrator. The MCPTT Administrator defines specific parameters and attributes (e.g., groups, MCPTT Emergency behaviour, priority and QoS attributes) associated with a temporary MCPTT User Identity for operation of the MCPTT UE in off-network operation mode.
+
+## 4.6 Overview of MCPTT priorities
+
+### 4.6.1 MCPTT priority model
+
+Many non-public safety 3GPP users today subscribe to one particular priority and QoS level of service (e.g., "gold", "silver" or "bronze"), which always provides fixed differentiation. This model, effective and relatively straightforward for non-public safety users, falls short when it comes to the needs of the public safety applications.
+
+MCPTT Priority and QoS is situational. The MCPTT Service is intended to provide a real-time priority and QoS experience for MCPTT calls, as public safety users have significant dynamic operational conditions that determine their priority. For example, the type of incident a responder is serving or the responder's overall shift role needs to strongly influence a user's ability to obtain resources from the 3GPP system.
+
+Another feature of a mission critical service is transparency of interactions between the users and the system. A first responder that needs to change the QoS of his communications is not to be distracted from his mission due to complicated UE behaviours or service interactions. Instead, the service acts in an anticipatory and adaptive manner to provide the proper quality of experience to the user, automatically, or with simple and minimal interaction.
+
+The mission critical service is also expected to provide the ability to interface with public safety systems (e.g., Computer Aided Dispatch) in order to determine the user's state (e.g., incident severity), environment and conditions and to affect the most appropriate priority and QoS experience for the user.
+
+The MCPTT Priority handling for on-network use for MCPTT Calls is conceptually modelled as shown in figure 4.6.1.1. The conceptual model identifies three areas of prioritization: prioritization between and within calls, inter-system prioritization, and prioritization at the transport layer (3GPP system and UE). At the Application Layer a generic, network side, functional entity, "MCPTT Priority and QoS Control", processes with each request static, preconfigured information about users and groups participating in MCPTT, as well as dynamic (or situational) information about them. Based on the results of this processing, the "MCPTT Priority and QoS Control" provides information to and directs interactions with other functional entities, systems, or layers to ensure, to the extent possible, that from a quality of experience point of view, calls and transmissions are handled properly in accordance to established policy rules.
+
+Error! Objects cannot be created from editing field codes.
+
+**Figure 4.6.1-1: A conceptual on-network MCPTT priority model**
+
+The User Static Attributes include information categorizing the user, possibly by several criteria (e.g., first responder, second responder, supervisor, dispatcher, administrator), as well as jurisdictional boundaries and possibly a preconfigured system-wide individual priority level.
+
+The Group Static Attributes include information about the nature/type of the group and the owning organization(s), the jurisdictional boundaries for transmitters and receivers within the group, the normal hours of operation for the group, pre-emption dispositions relative to other groups, and the default minimum priority of the group, i.e., the minimum priority characteristics that are provided to all the Participants in a group call associated with this group, regardless of their individual priority characteristics.
+
+The User Dynamic Attributes include the user/Participant's operational status (e.g., on/off duty), his location, the type of incident (e.g., MCPTT Emergency or Imminent Peril) he might be involved in and whether or not he initiated it, whether or not he is individually involved in a formally managed incident and if yes, the boundaries of the incident area, the incident severity and his assigned role in the resolution of the incident.
+
+The Group Dynamic Attributes include the type of incident (e.g., MCPTT Emergency or Imminent Peril), if any, the group is currently handling and in case of involvement in a formally managed incident the boundaries of the incident area and the incident severity.
+
+### 4.6.2 Generic processing of priority information
+
+This functionality applies to MCPTT Call initiations and transmissions for the management of potentially contended resources (e.g., GBR bearers) and also for Floor control during an MCPTT Group Call.
+
+Each request for exclusive access to resource(s) or for preferential treatment over a contending request arrives accompanied by priority information. This information stays associated with the companion request, whether the
+
+request is granted or is queued. The priority information is used for comparison between requests and facilitates the adding and removing of requests from queues and/or authorized interruption of service associated with a previously granted request, if still active. For each request, whether initially queued or not, the requesting party is informed (directly or indirectly) when his request is granted or denied. Other users/Participants are also notified of the disposition of a request and the notification includes the identity of the requestor, as needed. In addition, each requestor can be notified of the position of his request in the queue and he is allowed to cancel his requests while queued.
+
+### 4.6.3 Handling of MCPTT priority information for Floor control
+
+Floor control is applied in the context of a single MCPTT Call and is triggered by a Participant request for the permission to transmit. Priority information accompanies each grant request.
+
+### 4.6.4 Handling of MCPTT priority information for interactions at the transport layer
+
+At the Transport Layer, the MCPTT Service uses 3GPP controls to adapt the overall behaviour of the MCPTT System to the needs for resources and/or preferential treatment over other contenders, based on the priority information accompanying the request.
+
+The following four controls are available, to be used as necessary, based on the phase of the MCPTT call:
+
+- 3GPP system Access Controls;
+- UE Access Controls;
+- 3GPP system Admission Controls; and
+- 3GPP system Scheduling Controls.
+
+3GPP system Access Controls and UE Access Controls are used to allow preferential treatment of public safety UEs in situations of access congestion. The controls use priority and QoS mechanisms (e.g., using mechanisms like Access Class Barring, Service Specific Access Control, Access Control for Circuit Switched Fallback, Extended Access Barring).
+
+Admission Controls are used for the establishment and maintenance of the priority levels and of the pre-emption vulnerability and capability of bearers associated with transmissions and calls. At the start of an MCPTT call, the MCPTT Service requires bearers with proper ARP and pre-emption characteristics are in place prior to the call proceeding.
+
+Scheduling Controls (e.g., QCI and bandwidth for the bearers) are used for assuring the appropriate QoS necessary for meeting the Participants' expectation in the perceived quality of the delivered information, primarily in terms of when the service starts and the real-time characteristics of the delivered traffic (e.g., perceived delay, choppiness, clarity).
+
+### 4.6.5 Handling of MCPTT priority information for interactions with non-3GPP PTT systems
+
+An MCPTT call can be mixed, with some Participants served by one network/system and other Participants served by a different network(s)/system(s). In general the systems can be quite different. For example, some Participants use MCPTT/LTE, while others could use a P25-based system.
+
+### 4.6.6 MCPTT priority for Private Call
+
+The MCPTT Service uses User Static Attributes of the Participants, potentially adjusted based on User Dynamic Attributes, if applicable. By default, the priority of an MCPTT Private Call is the same as the priority of the originator of the call. Similar to group calls there are MCPTT Emergency Private Calls (with Floor control), which also have a similarly high priority. These are used where there is immediate danger to the user and are typically used to communicate with a dispatcher.
+
+## 4.7 Overview of MCPTT identifiers
+
+The main identifiable entities in use by the MCPTT Service are Mission Critical Organizations, MCPTT Groups, MCPTT Users, and MCPTT Administrators. The UEs are identified at the transport or network layer, but in some situations they might also be identified by the MCPTT Service. Each identifiable entity is distinct from all others and has an identifier (ID) associated to it, unique within a proximate identity domain. Those domains correspond to identifiable entities and can be nested within other domains in a multi-level hierarchical fashion. For example an MCPTT User might have an identifier unique within the domain corresponding to a Mission Critical Organization. The top-down concatenation of identifiers can generate unique identifiers within larger contexts, eventually leading to the identifiers being globally unique.
+
+Each identifier can be associated with one or more aliases, which can be used for displaying and selection purposes. Some aliases are shortened equivalents of the identifier used for efficient signalling and are not intended for human interactions. At a minimum, each entity has one alias (default) which is the alphanumeric representation of its identifier. Most entities have a main alias, which is the entity's name. Some aliases can be pictures, icons or other graphic representations. It is up to the implementation to decide if aliases have to be unique and if so, within which domain. Finally, some aliases are public, can be created/deleted only by authorized persons and are available to the MCPTT Service, while other aliases are private, can be created/deleted by their owners and might be residing only on certain UEs or be part of some private address books.
+
+It is possible in principle for User IDs, Group IDs, as well as for aliases, to be defined system wide with certain values, but have different values for each application: e.g., the system wide User ID might be different from the MCPTT User ID and different from the video User ID for the same user. However, this type of separation might not be beneficial, and in practice only one identifier is likely to be used.
+
+For simplicity, the term "User ID" is employed to identify an MCPTT User, without distinction of whether it is an identifier or an alias.
+
+# --- 5 MCPTT Service requirements common for on the network and off the network
+
+## 5.1 General group call requirements
+
+### 5.1.1 General aspects
+
+[R-5.1.1-001] Void
+
+[R-5.1.1-002] Void
+
+[R-5.1.1-003] Void
+
+[R-5.1.1-004] Void
+
+[R-5.1.1-005] Void
+
+### 5.1.2 Group/status information
+
+[R-5.1.2-001] Void
+
+[R-5.1.2-002] Void
+
+### 5.1.3 Group configuration
+
+[R-5.1.3-001] Void
+
+[R-5.1.3-002] Void
+
+### 5.1.4 Identification
+
+[R-5.1.4-001] Void
+
+### 5.1.5 Membership/affiliation
+
+[R-5.1.5-001] Void
+
+[R-5.1.5-002] Void
+
+[R-5.1.5-003] Void
+
+[R-5.1.5-004] Void
+
+[R-5.1.5-005] Void
+
+[R-5.1.5-006] Void
+
+[R-5.1.5-007] Void
+
+[R-5.1.5-008] Void
+
+### 5.1.6 Group Call administration
+
+[R-5.1.6-001] Void
+
+### 5.1.7 Prioritization
+
+[R-5.1.7-001] Void
+
+[R-5.1.7-002] Void
+
+### 5.1.8 Charging requirements for MCPTT
+
+[R-5.1.8-001] Void
+
+[R-5.1.8-002] Void
+
+[R-5.1.8-003] Void
+
+[R-5.1.8-004] Void
+
+[R-5.1.8-005] Void
+
+[R-5.1.8-006] Void
+
+[R-5.1.8-007] Void
+
+[R-5.1.8-008] Void
+
+[R-5.1.8-009] Void
+
+[R-5.1.8-010] Void
+
+[R-5.1.8-011] Void
+
+## 5.2 Broadcast Group
+
+### 5.2.1 General Broadcast Group Call
+
+[R-5.2.1-001] Void
+
+[R-5.2.1-002] Void
+
+### 5.2.2 Group-Broadcast Group (e.g., announcement group)
+
+[R-5.2.2-001] Void
+
+[R-5.2.2-002] Void
+
+[R-5.2.2-003] Void
+
+[R-5.2.2-004] Void
+
+### 5.2.3 User-Broadcast Group (e.g., System Call)
+
+[R-5.2.3-001] Void
+
+[R-5.2.3-002] Void
+
+## 5.3 Late call entry
+
+[R-5.3-001] Void
+
+[R-5.3-002] Void .
+
+[R-5.3-003] Void
+
+[R-5.3-004] Void .
+
+[R-5.3-005] Void
+
+## 5.4 Dynamic group management (i.e., dynamic regrouping)
+
+NOTE: No common on-network and off-network dynamic group management requirements have been identified.
+
+## 5.5 Receiving from multiple MCPTT calls
+
+### 5.5.1 Overview
+
+MCPTT Users receive call traffic of their affiliated MCPTT Groups. This multiple receiving, called monitoring by some organizations, provides MCPTT Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCPTT User is deployed to provide additional support for that event. The MCPTT User might be assigned to support the activities of more than one MCPTT Group on the same shift. This means that the MCPTT User receives multiple MCPTT Groups.
+
+An MCPTT User with limited speaker resources (e.g., a handheld UE) might find that playing out concurrent received audio from multiple active MCPTT Groups becomes confusing and could also cause undesired voice distortion for the receiving user. During periods of time when the MCPTT User is receiving audio from multiple MCPTT Groups, which MCPTT Group's audio is presented to the MCPTT User is determined by the MCPTT User's choice, the priority associated with the talker of the Selected MCPTT Group(s), other considerations or combinations of these. The MCPTT UE is aware of all the active groups to which the MCPTT User has affiliated or selected and the identity of the other active receiving groups is available for display on the MCPTT UE. When the receive activity from the Selected MCPTT Group stops, the MCPTT UE might present the audio from the next group per the MCPTT User's choice or by other means.
+
+If none of the multiple groups to which the MCPTT User has affiliated or selected is active, the MCPTT UE would continue to monitor for activity by any of the multiple affiliated or Selected MCPTT Groups. Monitoring for activity of multiple MCPTT Groups is also known as scanning and the list of the multiple groups is also known as a scan list.
+
+### 5.5.2 Requirements
+
+[R-5.5.2-001] Void
+
+[R-5.5.2-002] Void
+
+[R-5.5.2-003] Void
+
+[R-5.5.2-004] Void
+
+[R-5.5.2-005] Void
+
+[R-5.5.2-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N5) of MCPTT Group transmissions that an MCPTT UE simultaneously receives in one MCPTT Group call in case of override.
+
+[R-5.5.2-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N10) of MCPTT Private Calls (with Floor control) in which an MCPTT UE simultaneously participates.
+
+[R-5.5.2-008] Void
+
+[R-5.5.2-009] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N7) of MCPTT Group transmissions that an MCPTT User simultaneously receives in one MCPTT Group call in case of override.
+
+[R-5.5.2-010] Void
+
+[R-5.5.2-011] Void
+
+[R-5.5.2-012] Void
+
+[R-5.5.2-013] Void
+
+## 5.6 Private Call
+
+### 5.6.1 Private Call overview
+
+Private Calls allow two MCPTT Users to communicate directly with each other without the use of MCPTT Groups. They leverage many of the functions and features of MCPTT Group Calls, such as MCPTT User identity and alias information, location information, encryption, privacy, priority, and administrative control. Private Calls can use Floor control or not (i.e., be full voice duplex calls between users), though Private Calls without Floor control are only supported on the network.
+
+Two commencement modes of Private Calls are supported: Manual Commencement Private Call and Automatic Commencement Private Call. The two commencement modes can be used in conjunction with Private Calls with/without Floor control.
+
+Manual Commencement Private Calls mimic a telephone conversation where the called party receives a notification that they are being requested to join a Private Call, and the called party may accept, reject, or ignore the call request. Once the call setup is accepted, the Private Call is established and both Participants may communicate with each other.
+
+Automatic Commencement Private Calls mimic the immediate setup and voice propagation of Group Call operation between two users where the calling party initiates an Automatic Commencement Private Call to another user and sends audio without any additional call setup delay beyond Group Calls. If available and able to accept the Private Call from the calling party, the called party immediately joins the Private Call and processes the calling party's audio.
+
+### 5.6.2 Private Call (with Floor control) general requirements
+
+NOTE: The requirements in this subclause should mirror requirements in 6.7.1 for Private Call (without Floor control).
+
+[R-5.6.2-001] The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (with Floor control) to the relevant MCPTT User that is a Participant of the MCPTT Private Call (with Floor control).
+
+[R-5.6.2-002] The MCPTT Service shall support Private Calls with Floor control.
+
+[R-5.6.2-003] The MCPTT Service shall provide a mechanism for an authorized MCPTT User that is a called party in an MCPTT Private Call (with Floor control), to restrict providing the reason why an MCPTT Private Call (with Floor control) setup has failed to the calling MCPTT User.
+
+[R-5.6.2-004] The MCPTT Service shall provide a mechanism for the Private Call (with Floor control) to be set up with the MCPTT UE designated by the called MCPTT User to be used for Private Calls (with Floor control) when the called MCPTT User has signed on to the MCPTT Service with multiple MCPTT UEs.
+
+[R-5.6.2-005] Void
+
+### 5.6.3 Private Call (with Floor control) commencement requirements
+
+NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.4 for Private Call (without Floor control).
+
+[R-5.6.3-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (with Floor control), which determine the conditions under which Private Calls (with Floor control) are set up.
+
+[R-5.6.3-002] Void.
+
+[R-5.6.3-003] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel an MCPTT Private Call (with Floor control) prior to the call setup.
+
+[R-5.6.3-004] The MCPTT Service shall provide a means by which an authorized MCPTT User initiates an MCPTT Private Call (with Floor control).
+
+[R-5.6.3-005] The MCPTT Service shall provide a means by which an MCPTT UE initiates an MCPTT Private Call (with Floor control) to any MCPTT User for which the MCPTT UE's current MCPTT User is authorized.
+
+NOTE 2: For off-network use, only an MCPTT UE within communication range (possibly via a ProSe UE-to-UE Relay) receives the transmission.
+
+[R-5.6.3-006] The MCPTT Service shall provide a means by which an MCPTT User initiates a Manual Commencement Private Call (with Floor control) to any MCPTT User for which the MCPTT User is authorized.
+
+[R-5.6.3-007] The MCPTT Service shall require that the called MCPTT User accepts a Manual Commencement Private Call (with Floor control) setup request before the call proceeds.
+
+[R-5.6.3-008] The MCPTT Service shall provide a means for an MCPTT User to accept a Manual Commencement Private Call (with Floor control) request from another MCPTT User.
+
+[R-5.6.3-009] The MCPTT Service shall provide a means by which an MCPTT User initiates an Automatic Commencement Private Call (with Floor control) to any MCPTT User for which the MCPTT User is authorized.
+
+[R-5.6.3-010] The MCPTT UE shall support automatic commencement mode and manual commencement mode for Private Calls (with Floor control).
+
+[R-5.6.3-011] The MCPTT Service shall provide a manual commencement mode countermmand by which an authorized MCPTT User may request that the invited MCPTT UE answer automatically.
+
+[R-5.6.3-012] The MCPTT Service shall provide a means by which the calling authorized MCPTT User is notified the called MCPTT User received the Private Call (with Floor control) request.
+
+[R-5.6.3-013] The MCPTT Service shall require that the called MCPTT UE acknowledge receipt of an Automatic Commencement Private Call (with Floor control) setup request before the audio transmission proceeds.
+
+[R-5.6.3-014] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (with Floor control) to another MCPTT user.
+
+[R-5.6.3-015] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (with Floor control) to another MCPTT user in the following situations:
+
+- Always
+- If the MCPTT User is not reachable
+- If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
+- Based on manual input of the MCPTT User
+
+### 5.6.4 Private Call (with Floor control) termination
+
+NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.5 for Private Call (without Floor control).
+
+[R-5.6.4-001] The MCPTT Service shall provide a mechanism for an MCPTT User to reject an MCPTT Private Call (with Floor control).
+
+[R-5.6.4-002] The MCPTT Service shall provide a means by which an authorized MCPTT User ignores a Manual Commencement Private Call (with Floor control) request from another MCPTT User.
+
+NOTE 2: Ignoring a Manual Commencement Private Call (with Floor control) results in no indication of the reason for call failure being sent to the calling MCPTT User.
+
+[R-5.6.4-003] The MCPTT Service shall provide a means by which an MCPTT User ends a Private Call (with Floor control) in which the MCPTT User is a Participant.
+
+### 5.6.5 Private Call (with Floor control) administration
+
+NOTE: The requirements in this subclause should mirror requirements in 6.7.2 for Private Call (without Floor control), except [R-5.6.5-005] which is specific to Private Call with Floor control.
+
+[R-5.6.5-001] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within their authority, are authorized to place a Manual Commencement Private Call (with Floor control).
+
+[R-5.6.5-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within their authority, are authorized to place an Automatic Commencement Private Call (with Floor control).
+
+[R-5.6.5-003] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure for a particular authorized MCPTT User, a set of MCPTT Users under the same authority to which an MCPTT Private Call (with Floor control) can be made.
+
+[R-5.6.5-004] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure the maximum duration for MCPTT Private Calls (with Floor control) for MCPTT Users within their authority.
+
+[R-5.6.5-005] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure a timeout value in which an MCPTT Private Call (with Floor control) without a transmitting or receiving MCPTT User ends, for MCPTT Users within their authority.
+
+[R-5.6.5-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure whether an MCPTT User, within their authority, that is a called party in an MCPTT Private Call (with Floor control), may restrict providing the reason why an MCPTT Private Call (with Floor control) setup has failed to the calling MCPTT User.
+
+## 5.7 MCPTT priority requirements
+
+### 5.7.1 Overview
+
+MCPTT Emergency Group Call and MCPTT Imminent Peril group call are MCPTT Group Calls that provide the MCPTT User elevated priority towards obtaining resources of the MCPTT system. The MCPTT Emergency Private Call similarly provides elevated priority to resources of the MCPTT system. The MCPTT Emergency Alert provides a notification of an MCPTT Emergency situation from an MCPTT UE, regardless if the user is signed in with the MCPTT Service or not.
+
+The MCPTT Emergency Alert is initiated from an MCPTT UE to inform the MCPTT Service of the user's immediate need of assistance due to the user's personal, life-threatening situation. If the user is not properly authenticated, he is treated as a temporary MCPTT User with limited permissions. The user initiates this notification by actuating a user interface on the MCPTT UE. The notification to the MCPTT Service includes the MCPTT User's ID, potentially an MCPTT Group ID, the user's Mission Critical Organization name and the most current location available for the user's MCPTT UE.
+
+The user profile/group configuration determines which MCPTT Group ID is used, if any. If the user profile indicates that a dedicated (i.e., not used for everyday traffic) MCPTT Emergency Group is to be used, then the MCPTT Emergency call traffic moves to a different group. MCPTT Users that support MCPTT Emergency situations are required to monitor the dedicated MCPTT Emergency Group(s) for call activity. If the user profile indicates that the selected (i.e., currently active) MCPTT Group is to be used, then its Group ID is used, unless no group is selected.
+
+After the MCPTT User has initiated an MCPTT Emergency Alert, MCPTT Emergency Private Call or MCPTT Emergency Group Call, the MCPTT User is considered to be in the MCPTT Emergency State. The user remains in the MCPTT Emergency State until the MCPTT User cancels the MCPTT Emergency State.
+
+An MCPTT Group Call started by an MCPTT User while in the MCPTT Emergency State or previously started but followed by an MCPTT Emergency Alert becomes an MCPTT Emergency Group Call. The MCPTT Group ID used for the MCPTT Emergency Group Call is the same MCPTT Group ID included in the MCPTT Emergency Alert. An MCPTT User or dispatcher might initiate an MCPTT Emergency Group Call without an MCPTT Emergency Alert. The start of an MCPTT Emergency Group Call starts an In-progress Emergency condition for the MCPTT Group. Any subsequent MCPTT Group Call made by any MCPTT Group Member of an MCPTT Group which has an In-progress Emergency is treated as an MCPTT Emergency Group Call. MCPTT Emergency Group priority is removed when the In-progress Emergency for the group is cancelled.
+
+An MCPTT Private Call started by an MCPTT User while in the MCPTT Emergency State becomes an MCPTT Emergency Private Call.
+
+MCPTT Imminent Peril group call is differentiated from MCPTT Emergency Group Call based on for whom the assistance is required. The MCPTT Emergency Group Call is initiated by an MCPTT User for assistance for the MCPTT Emergency condition involving that user. The MCPTT Imminent Peril group call is initiated by an MCPTT User for assistance to other MCPTT Users or persons of the general public observed to be in trouble and may soon need assistance.
+
+There is no MCPTT Imminent Peril Alert and no MCPTT Imminent Peril State for MCPTT Users. The granting of an MCPTT Imminent Peril group call starts an In-progress Imminent Peril condition for the MCPTT Group. Any subsequent MCPTT Group Call made by any MCPTT Group Member of an MCPTT Group which has an In-progress Imminent Peril condition is treated as an MCPTT Imminent Peril group call. MCPTT Imminent Peril Group priority is removed when the In-progress Imminent Peril for the group is cancelled.
+
+### 5.7.2 Call types based on priorities
+
+#### 5.7.2.1 MCPTT Emergency Group Call
+
+##### 5.7.2.1.1 MCPTT Emergency Group Call requirements
+
+[R-5.7.2.1.1-001] Void
+
+[R-5.7.2.1.1-002] Void
+
+[R-5.7.2.1.1-003] Void
+
+[R-5.7.2.1.1-004] Void
+
+[R-5.7.2.1.1-005] Void
+
+[R-5.7.2.1.1-006] Void
+
+[R-5.7.2.1.1-007] Void
+
+[R-5.7.2.1.1-008] Void
+
+[R-5.7.2.1.1-009] Void
+
+[R-5.7.2.1.1-010] Void
+
+[R-5.7.2.1.1-011] Void
+
+[R-5.7.2.1.1-012] Void
+
+[R-5.7.2.1.1-013] Void
+
+[R-5.7.2.1.1-014] Void
+
+##### 5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements
+
+[R-5.7.2.1.2-001] Void
+
+[R-5.7.2.1.2-002] Void
+
+[R-5.7.2.1.2-003] Void
+
+[R-5.7.2.1.2-004] Void
+
+[R-5.7.2.1.2-005] Void
+
+#### 5.7.2.2 Imminent Peril group call
+
+##### 5.7.2.2.1 Imminent Peril group call requirements
+
+[R-5.7.2.2.1-001] Void
+
+[R-5.7.2.2.1-002] Void
+
+[R-5.7.2.2.1-003] Void
+
+[R-5.7.2.2.1-004] Void.
+
+[R-5.7.2.2.1-005] Void
+
+[R-5.7.2.2.1-006] Void.
+
+[R-5.7.2.2.1-007] Void
+
+[R-5.7.2.2.1-008] Void
+
+[R-5.7.2.2.1-009] Void
+
+##### 5.7.2.2.2 Imminent Peril group call cancellation requirements
+
+[R-5.7.2.2.2-001] Void
+
+[R-5.7.2.2.2-002] Void
+
+[R-5.7.2.2.2-003] Void
+
+[R-5.7.2.2.2-004] Void
+
+#### 5.7.2.3 MCPTT Emergency Private Call (with Floor control)
+
+##### 5.7.2.3.1 MCPTT Emergency Private Call (with Floor control) requirements
+
+[R-5.7.2.3.1-001] The MCPTT Service shall support MCPTT Emergency Private Calls (with Floor control) from authorized MCPTT Users.
+
+NOTE: This functionality out of network relies on the MCPTT User being called being within ProSe Communication range. For this reason this functionality is more likely to be used on the network.
+
+[R-5.7.2.3.1-002] When an MCPTT User initiates an MCPTT Emergency Private Call (with Floor control) this may trigger an MCPTT Emergency Alert for that MCPTT User.
+
+[R-5.7.2.3.1-003] When an MCPTT User initiates an MCPTT Emergency Private Call (with Floor control) this shall put that MCPTT User into an MCPTT Emergency State.
+
+##### 5.7.2.3.2 MCPTT Emergency Private Call (with Floor control) cancellation requirements
+
+[R-5.7.2.3.2-001] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) by an authorized MCPTT User.
+
+[R-5.7.2.3.2-002] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) when criteria established by the MCPTT Administrator are met (e.g., timeout).
+
+[R-5.7.2.3.2-003] The MCPTT Service shall support an MCPTT User cancelling their own MCPTT Emergency State.
+
+#### 5.7.2.4 MCPTT Emergency Alert
+
+##### 5.7.2.4.1 MCPTT Emergency Alert requirements
+
+[R-5.7.2.4.1-001] Void
+
+[R-5.7.2.4.1-002] Void
+
+[R-5.7.2.4.1-003] Void
+
+[R-5.7.2.4.1-004] Void .
+
+[R-5.7.2.4.1-005] Void.
+
+[R-5.7.2.4.1-006] Void
+
+[R-5.7.2.4.1-007] Void
+
+[R-5.7.2.4.1-008] Void
+
+[R-5.7.2.4.1-009] Void
+
+[R-5.7.2.4.1-010] Void
+
+[R-5.7.2.4.1-011] Void
+
+[R-5.7.2.4.1-012] Void
+
+##### 5.7.2.4.2 MCPTT Emergency Alert cancellation requirements
+
+[R-5.7.2.4.2-001] Void
+
+[R-5.7.2.4.2-002] Void
+
+[R-5.7.2.4.2-003] Void
+
+## 5.8 User ID
+
+[R-5.8-001] Void
+
+[R-5.8-002] Void
+
+[R-5.8-003] Void
+
+## 5.9 MCPTT UE management
+
+[R-5.9-001] Void
+
+[R-5.9-002] Void
+
+## 5.10 MCPTT User Profile
+
+[R-5.10-001] Void
+
+[R-5.10-002] Void
+
+## 5.11 Support for multiple devices
+
+[R-5.11-001] Void
+
+[R-5.11-002] Void
+
+## 5.12 Location
+
+[R-5.12-001] Void
+
+[R-5.12-002] Void
+
+[R-5.12-003] Void
+
+[R-5.12-004] Void
+
+[R-5.12-005] Void
+
+[R-5.12-006] Void
+
+[R-5.12-007] Void
+
+[R-5.12-008] Void .
+
+[R-5.12-009] Void
+
+[R-5.12-010] Void
+
+[R-5.12-011] The MCPTT Service shall provide a means for an MCPTT UE to send a Location information update whenever the MCPTT User initiates an MCPTT Imminent Peril Call.
+
+[R-5.12-012] Void
+
+[R-5.12-013] Void
+
+[R-5.12-014] Void
+
+[R-5.12-015] Void
+
+## 5.13 Security
+
+[R-5.13-001] Void
+
+[R-5.13-002] Void
+
+[R-5.13-003] Void
+
+[R-5.13-004] Void
+
+[R-5.13-005] Void
+
+[R-5.13-006] Void
+
+[R-5.13-007] Void
+
+[R-5.13-008] Void
+
+[R-5.13-009] Void
+
+[R-5.13-010] Void
+
+[R-5.13-011] Void
+
+[R-5.13-012] Void
+
+[R-5.13-013] Void
+
+## 5.14 Audio / voice quality
+
+[R-5.14-001] Void
+
+[R-5.14-002] MOS-LQO shall achieve the noise reduction performance of TIA-102.BABG [10] Table 3-1.
+
+[R-5.14-003] MOS-LQO shall achieve a noise reduction performance for the 3GPP Adaptive Multi-Rate Wide Band codec (AMR-WB TS 26.190 [11] and TS 26.194 [12]) that is equal to or greater than that specified for the P25 full rate and half rate voice codecs in TIA-102. BABG [10].
+
+## 5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor control)
+
+[R-5.15-001] The MCPTT Service shall allow an MCPTT UE to be transmitting in one MCPTT Group Call while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control).
+
+[R-5.15-002] The MCPTT Service shall allow an MCPTT UE to be receiving or transmitting in one MCPTT Private Call (with Floor control) while simultaneously receiving transmissions from one or more MCPTT Group Calls.
+
+[R-5.15-003] The MCPTT Service shall allow an MCPTT UE to be receiving one or more MCPTT Group Calls while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control).
+
+## 5.16 Relay requirements
+
+[R-5.16-001] Void
+
+[R-5.16-002] Void
+
+[R-5.16-003] Void
+
+## 5.17 Gateway requirements
+
+[R-5.17-001] Void
+
+## 5.18 Control and management by Mission Critical Organizations
+
+### 5.18.1 Overview
+
+Subclause 5.18 contains general requirements for management of the MCPTT Service by Mission Critical Organizations sharing the same MCPTT system, and more specific requirements pertaining to management controls and operational visibility, and to management of security services.
+
+### 5.18.2 General requirements
+
+[R-5.18.2-001] Void
+
+[R-5.18.2-002] Void
+
+[R-5.18.2-003] Void
+
+[R-5.18.2-004] Void
+
+[R-5.18.2-005] Void
+
+### 5.18.3 Operational visibility for Mission Critical Organizations
+
+[R-5.18.3-001] Void
+
+## 5.19 General Administrative – groups and users
+
+[R-5.19-001] Void
+
+[R-5.19-002] Void
+
+[R-5.19-003] Void
+
+[R-5.19-004] Void
+
+[R-5.19-005] Void
+
+[R-5.19-006] Void
+
+[R-5.19-007] Void
+
+[R-5.19-008] Void
+
+# --- 6 MCPTT Service requirements specific to on-network use
+
+## 6.1 General administrative – groups and users
+
+[R-6.1-001] Void
+
+[R-6.1-002] Void
+
+[R-6.1-003] Void
+
+[R-6.1-004] Void.
+
+[R-6.1-005] Void.
+
+[R-6.1-006] Void
+
+[R-6.1-007] Void
+
+## 6.2 MCPTT calls
+
+### 6.2.1 Commencement modes for MCPTT Group calls
+
+[R-6.2.1-001] The MCPTT Service shall be capable of allowing an MCPTT Group call setup request to proceed without prior acknowledgement by any MCPTT User of that MCPTT Group.
+
+[R-6.2.1-001a] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if a minimum number of MCPTT Group Members are currently affiliated.
+
+[R-6.2.1-001b] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if specific MCPTT Group Member(s) are currently affiliated.
+
+[R-6.2.1-002] An MCPTT User currently affiliated to an MCPTT Group shall acknowledge receipt of an MCPTT Group call setup request, if requested to do so by the MCPTT Service.
+
+[R-6.2.1-003] The MCPTT User's acknowledgement may require direct interaction of the MCPTT UE with the human user, or may be automatically executed by the MCPTT UE, in accordance with policy established by an MCPTT Administrator.
+
+[R-6.2.1-004] The MCPTT Service shall be capable of requiring that a minimum number of Affiliated MCPTT Group Members acknowledges receipt of the MCPTT Group call setup request before the audio transmission proceeds.
+
+[R-6.2.1-005] The MCPTT Service shall be capable of requiring that specific MCPTT Users acknowledge receipt of the MCPTT Group call setup request before the audio transmission proceeds, regardless of the affiliation state of those users.
+
+NOTE 1: In this case the MCPTT Service affiliates the specific MCPTT Users who are not currently affiliated to the target MCPTT Group and then returns them to their previous affiliation state when the transmission ends.
+
+[R-6.2.1-006] The MCPTT Service shall be capable of requiring that all MCPTT Users that are both affiliated to the MCPTT Group and in a given geographical area acknowledge receipt of an MCPTT Group call setup request before the audio transmission proceeds.
+
+[R-6.2.1-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to determine the subset of Affiliated MCPTT Group Members that shall acknowledge receipt of the MCPTT Group call setup request before the audio transmission proceeds.
+
+NOTE 2: In the following requirements, the term, "MCPTT Group Call setup request requires acknowledgement" is used when one or more of the acknowledgement conditions defined above (i.e., [R-6.2.1-004], [R-6.2.1-005], [R-6.2.1-006], and/or [R-6.2.1-007]) applies.
+
+[R-6.2.1-008] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), the MCPTT Service may proceed with the call and then may notify the initiating MCPTT User that the acknowledgements did not include all required members.
+
+[R-6.2.1-009] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members do not acknowledge the call setup within a configured time, the MCPTT Service may abandon the call and then may notify the initiating MCPTT User that the acknowledgements did not include all required members.
+
+[R-6.2.1-010] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the initiating MCPTT User shall at any time have the option of allowing the call to proceed regardless of the state of the acknowledgements (i.e., to "convert" the call to an unacknowledged call).
+
+[R-6.2.1-010a] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members did not acknowledge the call setup within a configured time, the MCPTT Service shall be able to provide the list of MCPTT Group Members who did not acknowledge the call to the initiating MCPTT User.
+
+[R-6.2.1-011] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the acknowledged call setup timeout shall be established by an MCPTT Administrator.
+
+[R-6.2.1-012] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the behaviour in response to the expiration of the acknowledged call setup timeout shall be established by an MCPTT Administrator.
+
+[R-6.2.1-013] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the MCPTT Service shall support an indefinite (i.e., infinite) call setup timeout.
+
+[R-6.2.1-014] If the MCPTT Service has knowledge that some affiliated members of a group can not be Participants in an unacknowledged MCPTT Group Call, the MCPTT Service shall provide an indication to the requester that the call is proceeding without all affiliated members, and shall provide the list of the missing members based on policy established by the MCPTT Administrator.
+
+[R-6.2.1-015] If MCPTT User(s) are excluded from an MCPTT call as there is insufficient capacity to support their participation the MCPTT Service shall ensure that the MCPTT User(s) receive a notification that they have been excluded from the call for reasons of lack of capacity.
+
+### 6.2.2 Queuing
+
+[R-6.2.2-001] Void
+
+[R-6.2.2-002] Void
+
+[R-6.2.2-003] Void
+
+[R-6.2.2-004] Void
+
+[R-6.2.2-005] Void
+
+[R-6.2.2-006] Void
+
+### 6.2.3 Floor control
+
+#### 6.2.3.1 General aspects
+
+[R-6.2.3.1-001] The Floor control functionality in an MCPTT Service shall determine at a point in time which Participant(s) are allowed to transmit to other Participant(s).
+
+[R-6.2.3.1-002] Receiving Participant(s) shall receive audio from one transmitting Participant. The only exception is if an MCPTT Group is configured to allow simultaneous Transmitting MCPTT Group Members in override.
+
+[R-6.2.3.1-003] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the number (maximum of N9) of simultaneous audios received by an MCPTT User in a single MCPTT Group.
+
+#### 6.2.3.2 Requesting permission to transmit
+
+[R-6.2.3.2-001] An authorized Participant shall be able to request to transmit to an MCPTT Group or an individual Participant.
+
+[R-6.2.3.2-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group.
+
+[R-6.2.3.2-003] The Floor control functionality shall determine the transmitting Participant(s) when there are simultaneous requests for permission to transmit within the same call.
+
+[R-6.2.3.2-004] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group, the Affiliated MCPTT Group Member that made and was granted the request shall be given an indication of being allowed to transmit.
+
+[R-6.2.3.2-005] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group, an Affiliated MCPTT Group Member that made and was not granted the request shall be given an indication that permission to transmit was rejected or queued.
+
+[R-6.2.3.2-006] The depth of the Floor control queue shall be configurable.
+
+[R-6.2.3.2-007] Following an MCPTT Private Call (with Floor control) request for permission to transmit, the MCPTT User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCPTT User.
+
+[R-6.2.3.2-008] Following an MCPTT Private Call (with Floor control) request for permission to transmit, an MCPTT User that is not allowed to transmit shall be given an indication that the permission to transmit was rejected or queued.
+
+[R-6.2.3.2-009] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant is starting to transmit.
+
+[R-6.2.3.2-010] The MCPTT Service shall provide a mechanism for an MCPTT Participant to remove its MCPTT Request from the Floor control queue.
+
+[R-6.2.3.2-011] The MCPTT Service shall provide a mechanism for removal (i.e., request accepted, request denied, or expiration of a timer) of an MCPTT Request from the Floor control queue.
+
+[R-6.2.3.2-012] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the parameter(s) of the Floor control queue for an MCPTT Group (i.e., timer).
+
+#### 6.2.3.3 Override
+
+##### 6.2.3.3.1 General aspects
+
+[R-6.2.3.3.1-001] The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types shall be granted a request to override an active MCPTT transmission.
+
+[R-6.2.3.3.1-002] The MCPTT Service shall enable an MCPTT Administrator to configure which MCPTT Group transmission a Participant(s) receives, overriding and/or overridden for cases where an authorized Participant overrides an MCPTT transmission.
+
+[R-6.2.3.3.1-003] The MCPTT Service shall enable the MCPTT Administrator to configure the MCPTT Group to allow only the overriding Participant to transmit or to allow both the overriding and overridden Participant to transmit.
+
+[R-6.2.3.3.1-004] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure MCPTT Private Calls (with Floor control) to allow only the overriding Participant to transmit or to allow both the overriding and overridden Participant to transmit.
+
+[R-6.2.3.3.1-005] The priority hierarchy used for granting a request to override an active MCPTT transmission shall contain at least four (4) levels.
+
+[R-6.2.3.3.1-006] The transmitting Participant shall be determined by the relative Floor control priorities of the Participants and Call type based on priority (e.g MCPTT Emergency).
+
+[R-6.2.3.3.1-007] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or Call type based on priority (e.g MCPTT Emergency) are ranked higher than the priority level of the transmitting Participant or Call type based on priority.
+
+[R-6.2.3.3.1-008] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
+
+##### 6.2.3.3.2 Override – one transmitting Participant
+
+[R-6.2.3.3.2-001] If the MCPTT Group has been configured to only allow the overriding transmitting Participant, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant.
+
+##### 6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members
+
+[R-6.2.3.3.3-001] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants, authorized receiving Participants shall be enabled to listen to both the overriding and overridden Participant transmissions, dependent on configuration.
+
+[R-6.2.3.3.3-002] The MCPTT Service shall allow successive overrides of an MCPTT Group Call when the request to override is made by an MCPTT User having a higher Floor control priority than the currently transmitting Participants.
+
+[R-6.2.3.3.3-003] In the case of successive overrides, the MCPTT Service shall enable only two transmissions, one overriding transmission, from the highest priority MCPTT User, and one overridden transmission, chosen from among the two overridden Participants based upon configured rule(s). (i.e., this could be based simply on priority of user, it could be based on a policy that an overridden MCPTT Emergency transmission shall remain as the overridden transmission or a rule could be established that the MCPTT system shall not allow two dispatchers to be both the overriding and overridden transmitters.).
+
+#### 6.2.3.4 Terminating permission to transmit
+
+[R-6.2.3.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time.
+
+[R-6.2.3.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer wants to transmit.
+
+NOTE: In this case audio stops being transmitted to the receiver Participant(s) until an authorized Participant sends a subsequent request for permission to transmit.
+
+[R-6.2.3.4-003] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
+
+#### 6.2.3.5 Transmit time limit
+
+[R-6.2.3.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit.
+
+[R-6.2.3.5-002] The Floor control functionality shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
+
+[R-6.2.3.5-003] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
+
+[R-6.2.3.5-004] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
+
+[R-6.2.3.5-005] The Floor control functionality shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached.
+
+#### 6.2.3.6 Audio cut-in on designated MCPTT Groups
+
+##### 6.2.3.6.1 Overview
+
+The audio cut-in feature applies to specially designated MCPTT Groups and results in Floor control for that group allowing any participant within the MCPTT Group to interrupt any other participant. In particular the audio cut-in feature means that the last Participant to request the floor is assigned the floor immediately and there is only ever one talker on the call at a particular point in time. Audio cut-in is often used for teams escorting VIPs where timeliness is essential to allow teams to react as quickly as possible.
+
+Other than the difference in floor control logic, the MCPTT Groups configured to support audio cut-in behave in the same way as other MCPTT Groups with group management, affiliation, selection of a group, requesting the floor, the notifications received related to Floor control etc working in the same way.
+
+##### 6.2.3.6.2 Requirements
+
+[R-6.2.3.6.2-001] The MCPTT Group shall be configurable to allow audio cut-in.
+
+NOTE 1: MCPTT Groups configured for audio cut-in behave in the same way as MCPTT Groups not configured for audio cut-in in all other respects other than the Floor control logic described in this sub-clause.
+
+[R-6.2.3.6.2-002] When an MCPTT Group has been configured to support audio cut-in, the Floor control functionality shall give the floor to the MCPTT Group Member that has selected that MCPTT Group and made the most recent request to transmit in that MCPTT Group.
+
+NOTE 2: Requests to transmit that are received simultaneously will be addressed by manufacturer implementation.
+
+[R-6.2.3.6.2-003] When an MCPTT Group has been configured to support audio cut-in the Floor control functionality shall restrict the number of talkers in the group to one.
+
+[R-6.2.3.6.2-004] When an MCPTT Group has been designated to support audio cut-in the MCPTT Group shall not support any form of floor control queuing and associated functionality.
+
+[R-6.2.3.6.2-005] When the current talker is interrupted by a request to transmit on an MCPTT Group supporting audio cut-in, the talk request of the interrupted talker shall end.
+
+NOTE 3: The interrupted talker must make a new request to transmit in order to transmit again.
+
+[R-6.2.3.6.2-006] Void
+
+[R-6.2.3.6.2-007] Void
+
+##### 6.2.3.6.3 Requesting permission to transmit
+
+[R-6.2.3.6.3-001] An authorized Participant shall be able to request to transmit to an MCPTT Group configured to support audio cut-in.
+
+[R-6.2.3.6.3-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group configured to support audio cut-in.
+
+[R-6.2.3.6.3-003] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured to support audio cut-in, the Affiliated MCPTT Group Member that made and was granted the request shall be given an indication of being allowed to transmit.
+
+[R-6.2.3.6.3-004] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant is starting to transmit on a group configured for audio cut-in.
+
+##### 6.2.3.6.4 Terminating permission to transmit
+
+[R-6.2.3.6.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time on a group configured for audio cut-in.
+
+[R-6.2.3.6.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer wants to transmit on a group configured for audio cut-in.
+
+NOTE: In this case audio stops being transmitted to the receiver Participant(s) until an authorized Participant sends a subsequent request for permission to transmit.
+
+[R-6.2.3.6.4-003] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting on a group configured for audio cut-in.
+
+##### 6.2.3.6.5 Transmit time limit
+
+[R-6.2.3.6.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit on a group configured for audio cut-in.
+
+[R-6.2.3.6.5-002] The Floor control functionality for a group configured for audio cut-in shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
+
+[R-6.2.3.6.5-003] The Floor control functionality for a group configured for audio cut-in shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
+
+[R-6.2.3.6.5-004] The Floor control functionality for a group configured for audio cut-in shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
+
+[R-6.2.3.6.5-005] The Floor control functionality for a group configured for audio cut-in shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached.
+
+#### 6.2.3.7 MCPTT Groups configured for multi-talker control
+
+##### 6.2.3.7.1 Overview
+
+The multi-talker control applies to designated MCPTT Groups and results in allowing several Participants talking simultaneously within the MCPTT Group. For example, Multi-talker control is used by railway communication e.g. during shunting operation.
+
+Except for Floor control as specified in clauses 6.2.3.1, 6.2.3.2, 6.2.3.3 and 6.2.3.6 all other requirements specified in 6.2.3 floor control are applicable to MCPTT Groups configured to support multi-talker control
+
+When an MCPTT Group is configured for multi-talker control, the requirements listed below apply.
+
+##### 6.2.3.7.2 General aspects
+
+[R-6.2.3.7.2-001] An MCPTT Group shall be configurable to allow multi-talker control.
+
+[R-6.2.3.7.2-002] The MCPTT Service shall provide a mechanism for multiple MCPTT Users to talk simultaneously in an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.2-003] The MCPTT Service shall determine which Participant(s) are allowed to transmit to all other Participant(s) in an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.2-004] The MCPTT Service shall support all Participant(s) to receive audio from all other Participant(s) that are transmitting in an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.2-005] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.2-006] The MCPTT Service shall allow an authorized MCPTT User to change the maximum number of simultaneous talkers at any time during a group call in an MCPTT Group configured for multi-talker control.
+
+##### 6.2.3.7.3 Requesting permission to transmit
+
+[R-6.2.3.7.3-001] The MCPTT Service shall enable authorized Participants to request to transmit to an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.3-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.3-003] The MCPTT Service shall determine the transmitting Participant(s) when there are simultaneous requests for permission to transmit within the same call for an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.3-004] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured for multi-talker control the MCPTT Service shall provide an Affiliated MCPTT Group Member that made and was granted the request an indication of being allowed to transmit.
+
+##### 6.2.3.7.4 Override
+
+###### 6.2.3.7.4.1 General aspects
+
+[R-6.2.3.7.4.1-001] If the number of MCPTT Users requesting the permission to talk exceeds the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control, the MCPTT Service shall apply the override mechanism.
+
+[R-6.2.3.7.4.1-002] The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types shall be granted a request to override an active MCPTT transmission on an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.4.1-003] The priority hierarchy used for granting a request to override an active MCPTT transmission on a group configured for multi-talker control shall contain at least four (4) levels.
+
+[R-6.2.3.7.4.1-004] The transmitting Participant on an MCPTT Group a group configured for multi-talker control shall be determined by the relative priorities of the Participants and Call type based on priority (e.g MCPTT Emergency).
+
+[R-6.2.3.7.4.1-005] Transmission requests of Participants with insufficient relative priority shall be rejected.
+
+[R-6.2.3.7.4.1-006] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or Call type based on priority (e.g MCPTT Emergency) are ranked higher than the priority level of the transmitting Participant or Call type based on priority for an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.4.1-007] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden for an MCPTT Group configured for multi-talker control.
+
+[R-6.2.3.7.4.1-008] The MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant on an MCPTT Group configured for multi-talker control.
+
+### 6.2.4 Call termination
+
+[R-6.2.4-001] If a Participant of an MCPTT Group call is pre-empted, the MCPTT Service shall terminate the call or continue the call with an indication to the transmitting Participant that one or more receiving Participants was pre-empted.
+
+[R-6.2.4-002] If MCPTT User(s) are pre-empted from an ongoing MCPTT call as there is insufficient capacity to support their ongoing participation, the MCPTT Service shall ensure that the MCPTT User(s) receive a notification that they have been removed from the call for reasons of lack of capacity.
+
+[R-6.2.4-003] The MCPTT Service shall terminate a call after the Hang Time expires.
+
+[R-6.2.4-004] Void.
+
+[R-6.2.4-005] The MCPTT Service shall provide an indication to the Participants that the call is within a configurable amount of time before the call time limit is reached.
+
+[R-6.2.4-006] The MCPTT Service shall release the call when the call time limit has been reached.
+
+[R-6.2.4-007] The MCPTT Service shall provide an indication to the Participants that the call time limit has been reached.
+
+[R-6.2.4-008] The MCPTT Service shall release an MCPTT Group call if any of the termination conditions are met (e.g., last Participant leaving, second last Participant leaving, initiator leaving) or the minimum number of Affiliated MCPTT Group Members are not present.
+
+## 6.3 General requirements
+
+[R-6.3-001] Void
+
+[R-6.3-002] Void
+
+[R-6.3-003] Void
+
+[R-6.3-004] Void
+
+## 6.4 General group call
+
+### 6.4.1 General aspects
+
+[R-6.4.1-001] Void
+
+### 6.4.2 Group status/information
+
+[R-6.4.2-001] Void
+
+[R-6.4.2-002] Void
+
+[R-6.4.2-003] Void
+
+[R-6.4.2-004] Void
+
+[R-6.4.2-005] Void
+
+[R-6.4.2-006] Void
+
+[R-6.4.2-007] Void
+
+### 6.4.3 Identification
+
+[R-6.4.3-001] Void
+
+[R-6.4.3-002] Void
+
+### 6.4.4 Membership/affiliation
+
+[R-6.4.4-001] Void
+
+[R-6.4.4-002] Void
+
+### 6.4.5 Membership/affiliation list
+
+[R-6.4.5-001] Void
+
+[R-6.4.5-002] Void
+
+[R-6.4.5-003] Void
+
+[R-6.4.5-004] Void
+
+[R-6.4.5-005] Void
+
+[R-6.4.5-006] Void
+
+[R-6.4.5-007] Void
+
+[R-6.4.5-008] Void
+
+### 6.4.6 Authorized user remotely changes another MCPTT User's affiliated and/or Selected MCPTT Group(s)
+
+#### 6.4.6.1 Mandatory change
+
+[R-6.4.6.1-001] Void
+
+[R-6.4.6.1-002] Void
+
+[R-6.4.6.1-003] Void
+
+[R-6.4.6.1-004] Void
+
+#### 6.4.6.2 Negotiated change
+
+[R-6.4.6.2-001] Void
+
+[R-6.4.6.2-002] Void
+
+[R-6.4.6.2-003] Void
+
+[R-6.4.6.2-004] Void
+
+[R-6.4.6.2-005] Void
+
+[R-6.4.6.2-006] Void
+
+### 6.4.7 Prioritization
+
+[R-6.4.7-001] Void
+
+[R-6.4.7-002] Void
+
+[R-6.4.7-003] Void
+
+[R-6.4.7-004] Void
+
+### 6.4.8 Relay requirements
+
+[R-6.4.8-001] Void
+
+### 6.4.9 Administrative
+
+[R-6.4.9-001] Void
+
+[R-6.4.9-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to set a predefined time period (Hang Time) without any traffic in MCPTT calls (with Floor control), after which the MCPTT calls shall terminate.
+
+[R-6.4.9-003] Void
+
+[R-6.4.9-004] Void
+
+[R-6.4.9-005] Void
+
+[R-6.4.9-006] Void
+
+[R-6.4.9-007] Void
+
+## 6.5 Broadcast group
+
+### 6.5.1 General Broadcast Group Call
+
+[R-6.5.1-001] Void
+
+[R-6.5.1-002] Void
+
+### 6.5.2 Group-Broadcast Group (e.g., announcement group)
+
+[R-6.5.2-001] Void
+
+### 6.5.3 User-Broadcast Group (e.g., System Call)
+
+[R-6.5.3-001] Void
+
+## 6.6 Dynamic group management (i.e., dynamic regrouping)
+
+### 6.6.1 General dynamic regrouping
+
+[R-6.6.1-001] Void
+
+[R-6.6.1-002] Void
+
+[R-6.6.1-003] Void
+
+[R-6.6.1-004] Void
+
+[R-6.6.1-005] Void
+
+[R-6.6.1-006] Void
+
+### 6.6.2 Group Regrouping
+
+#### 6.6.2.1 Service description
+
+Group Regrouping enables dispatchers or any authorized user to temporarily combine MCPTT Groups. A dispatcher uses Group Regrouping for different reasons.
+
+Due to an incident in an area it can be necessary to temporarily enable MCPTT Users from different MCPTT Groups to communicate to each other to coordinate. After the incident the dispatcher cancels the Group Regrouping and the MCPTT Users continue with their original configured MCPTT Groups.
+
+During quiet periods control room managers can decide to combine MCPTT Groups and handle their operations and communications with one dispatcher. In the busier period the Group Regrouping is cancelled and the MCPTT Groups are handled by separate dispatchers.
+
+#### 6.6.2.2 Requirements
+
+[R-6.6.2.2-001] Void
+
+[R-6.6.2.2-002] Void
+
+[R-6.6.2.2-003] Void
+
+[R-6.6.2.2-004] Void
+
+[R-6.6.2.2-005] Void
+
+[R-6.6.2.2-006] Void
+
+[R-6.6.2.2-007] Void
+
+### 6.6.3 Temporary Group-Broadcast Group
+
+[R-6.6.3-001] Void
+
+[R-6.6.3-002] Void
+
+### 6.6.4 User regrouping
+
+#### 6.6.4.1 Service description
+
+In the operational MCPTT environment most tasks are covered by standard procedures and communication structures and MCPTT Users can easily access the MCPTT Groups to handle their tasks.
+
+Exceptionally it could happen that there is an urgent need for a dedicated set of individual MCPTT Users to communicate in an MCPTT Group, but that this is not foreseen in the communication structure. This could be due to extreme conditions or due to a cooperation that is outside normal procedures.
+
+User Regrouping enables dispatchers or authorized users to instantaneously provide a dedicated MCPTT Group to these MCPTT Users to enable the required communication. Depending on configuration the MCPTT Users could be automatically affiliated to this MCPTT Group. After the operation this MCPTT Group is removed by the dispatcher or authorized user.
+
+#### 6.6.4.2 Requirements
+
+[R-6.6.4.2-001] Void
+
+[R-6.6.4.2-002] Void
+
+[R-6.6.4.2-003] Void
+
+[R-6.6.4.2-004] Void
+
+[R-6.6.4.2-005] Void
+
+## 6.7 Private Call
+
+### 6.7.0 Overview
+
+Private Calls can use Floor control or not. Private Calls (without Floor control) are only supported on network, whereas Private Calls (with Floor control) are supported both on and off network. Private Calls (without Floor control) are intended to have the same functionality as specified for Private Calls (with Floor control) in subclauses 5.6.2, 5.6.3, 5.6.4, 5.6.5. Comparable requirements are included in subclauses 6.7.1, 6.7.2, 6.7.4 and 6.7.5, with the exception of R-5.6.5-005, which is specific to Private Calls (with Floor control).
+
+### 6.7.1 General requirements
+
+[R-6.7.1-001] The on-network MCPTT Service shall support two types of Private Calls, one which uses Floor control and one which does not.
+
+NOTE: An MCPTT Private Call (without Floor control) is effectively a full voice duplex call between two users.
+
+[R-6.7.1-002] Void
+
+[R-6.7.1-003] Void
+
+[R-6.7.1-004] Void
+
+[R-6.7.1-005] Void
+
+[R-6.7.1-006] Void
+
+[R-6.7.1-007] Void
+
+[R-6.7.1-008] Void
+
+[R-6.7.1-009] Void
+
+[R-6.7.1-010] The MCPTT Service shall provide a mechanism by which specified Participants or Participant types (e.g., dispatch) have the ability to override an active PTT transmission of the other Participant in the Private Call.
+
+[R-6.7.1-011] Void
+
+[R-6.7.1-012] The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (without Floor control) to the relevant MCPTT User that is a Participant of the MCPTT Private Call (without Floor control).
+
+[R-6.7.1-013] The MCPTT Service shall provide a mechanism for an authorized MCPTT User that is a called party in an MCPTT Private Call (without Floor control), to restrict providing the reason why an MCPTT Private Call (without Floor control) setup has failed to the calling MCPTT User.
+
+[R-6.7.1-014] Void
+
+### 6.7.2 Administrative
+
+[R-6.7.2-001] Void
+
+[R-6.7.2-002] Void
+
+[R-6.7.2-003] Void
+
+[R-6.7.2-004] Void
+
+[R-6.7.2-005] Void
+
+[R-6.7.2-006] Void
+
+[R-6.7.2-007] Void
+
+[R-6.7.2-008] Void
+
+### 6.7.3 Prioritization
+
+[R-6.7.3-001] Void
+
+[R-6.7.3-002] Void
+
+[R-6.7.3-003] Void
+
+[R-6.7.3-004] Void
+
+[R-6.7.3-005] Void
+
+[R-6.7.3-006] Void
+
+[R-6.7.3-007] Void
+
+### 6.7.4 Private Call (without Floor control) commencement requirements
+
+[R-6.7.4-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (without Floor control), which determine the conditions under which Private Calls (without Floor control) are set up.
+
+[R-6.7.4-002] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel an MCPTT Private Call (without Floor control) prior to the call setup.
+
+[R-6.7.4-003] The MCPTT Service shall provide a means by which an authorized MCPTT User initiates an MCPTT Private Call (without Floor control).
+
+[R-6.7.4-004] Void
+
+[R-6.7.4-005] The MCPTT Service shall provide a means by which an MCPTT User initiates a Manual Commencement Private Call (without Floor control) to any MCPTT User for which the MCPTT User is authorized.
+
+[R-6.7.4-006] The MCPTT Service shall require that the called MCPTT User accepts a Manual Commencement Private Call (without Floor control) setup request before the call proceeds.
+
+[R-6.7.4-007] The MCPTT Service shall provide a means for an MCPTT User to accept a Manual Commencement Private Call (without Floor control) request from another MCPTT User.
+
+[R-6.7.4-008] Void
+
+[R-6.7.4-009] The MCPTT UE shall support automatic commencement mode and manual commencement mode for Private Calls (without Floor control).
+
+[R-6.7.4-010] The MCPTT Service shall provide a manual commencement mode countermand by which an authorized MCPTT User may request that the invited MCPTT UE answers automatically.
+
+[R-6.7.4-011] Void
+
+[R-6.7.4-012] The MCPTT Service shall require that the called MCPTT UE acknowledge receipt of an Automatic Commencement Private Call (without Floor control) setup request before the audio transmission proceeds.
+
+[R-6.7.4-013] The MCPTT Service shall provide a first-to-answer commencement mode by allowing the originating user to indicate multiple potential target recipients for a Private Call (without Floor control) and shall ensure that the call is established only to the first answering user.
+
+NOTE: Attention needs to be given to prevent undesired outcomes caused, for example, by automatic answer or divert to voicemail.
+
+[R-6.7.4-014] When a receiving user answers a first-to-answer Private Call (without Floor control) the MCPTT Service shall remove all other receiving users from that call.
+
+[R-6.7.4-015] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (without Floor control) to another MCPTT user.
+
+[R-6.7.4-016] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (without Floor control) to another MCPTT user in the following situations:
+
+- Always
+- If the MCPTT User is not reachable
+- If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
+- Based on manual input of the MCPTT User
+
+#### 6.7.4a Private Call (with Floor control) commencement requirements
+
+[R-6.7.4a-001] The MCPTT Service shall provide a first-to-answer commencement mode by allowing the originating user to indicate multiple potential target recipients for a Private Call (with Floor control) and shall ensure that the call is established only to the first answering user.
+
+NOTE: Attention needs to be given to prevent undesired outcomes caused, for example, by automatic answer or divert to voicemail.
+
+[R-6.7.4a-002] When a receiving user answers a first-to-answer Private Call (with Floor control) the MCPTT Service shall remove all other receiving users from that call.
+
+### 6.7.5 Private Call (without Floor control) termination
+
+[R-6.7.5-001] Void
+
+[R-6.7.5-002] The MCPTT Service shall provide a means by which an authorized MCPTT User ignores a Manual Commencement Private Call (without Floor control) request from another MCPTT User.
+
+NOTE: Ignoring a Manual Commencement Private Call (without Floor control) results in no indication of the reason for call failure being sent to the calling MCPTT User.
+
+[R-6.7.5-003] Void
+
+### 6.7.6 Call back request requirements
+
+[R-6.7.6-001] The MCPTT Service shall provide a mechanism (i.e., MCPTT Private Call call back request) for the calling party of an MCPTT Private Call to request that the called party (at earliest convenience) place a call to the calling party.
+
+[R-6.7.6-002] The MCPTT Service shall provide a mechanism for the calling party of an MCPTT Private Call to assign an urgency indication (i.e., low, normal, urgent) to any call back request.
+
+[R-6.7.6-003] The MCPTT Service shall provide an MCPTT UE receiving an MCPTT Private Call call back request with an indication of the assigned call back urgency assigned by the calling party.
+
+[R-6.7.6-004] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel a call back request.
+
+[R-6.7.6-005] The MCPTT Service shall provide an MCPTT UE receiving an MCPTT Private Call call back request with an indication of which MCPTT User called and when.
+
+## 6.8 MCPTT priority requirements
+
+### 6.8.1 General
+
+[R-6.8.1-001] Void
+
+[R-6.8.1-002] The MCPTT Service shall provide an access control mechanism to support multiple Access Priorities to prioritize MCPTT MO call initiation attempts, depending on their access priorities.
+
+[R-6.8.1-003] Void
+
+[R-6.8.1-004] Void
+
+[R-6.8.1-005] Void
+
+[R-6.8.1-006] Void
+
+[R-6.8.1-007] Void
+
+[R-6.8.1-008] Void
+
+[R-6.8.1-009] Void
+
+[R-6.8.1-010] Void
+
+[R-6.8.1-011] Void
+
+[R-6.8.1-012] Void
+
+[R-6.8.1-013] Void
+
+[R-6.8.1-014] Void
+
+[R-6.8.1-015] Void
+
+[R-6.8.1-016] Void
+
+[R-6.8.1-017] Void
+
+### 6.8.2 3GPP system access controls
+
+[R-6.8.2-001] Void
+
+### 6.8.3 3GPP system admission controls
+
+[R-6.8.3-001] Void
+
+### 6.8.4 3GPP system scheduling controls
+
+[R-6.8.4-001] Void
+
+### 6.8.5 UE access controls
+
+[R-6.8.5-001] Void
+
+### 6.8.6 Application layer priorities
+
+#### 6.8.6.1 Overview
+
+Dispatchers from different critical communication organizations access the same networks and network resources. Depending on the event, the priority is given to an organization and/or a group rather than to another. For instance, in case of a fire priority is given to the fire brigades dealing with it, while in case of a criminal arrest priority is given to the police officers in charge of the arrest.
+
+#### 6.8.6.2 Requirements
+
+[R-6.8.6.2-001] Void
+
+[R-6.8.6.2-002] Void
+
+[R-6.8.6.2-003] Void
+
+[R-6.8.6.2-004] The MCPTT system may stop already established MCPTT calls with the capability to be pre-empted and a lower application layer priority to allow a new MCPTT call with pre-emption capability enabled for pre-emption to be established.
+
+[R-6.8.6.2-005] Void
+
+[R-6.8.6.2-006] Void
+
+### 6.8.7 Call types based on priorities
+
+#### 6.8.7.1 MCPTT Emergency Group Call requirements
+
+[R-6.8.7.1-001] Void
+
+[R-6.8.7.1-002] Void
+
+[R-6.8.7.1-003] Void
+
+[R-6.8.7.1-004] Void
+
+#### 6.8.7.2 MCPTT Emergency Private Call (with Floor control) requirements
+
+[R-6.8.7.2-001] The MCPTT Service shall ensure that MCPTT Emergency Private Calls (with Floor control) have the highest priority over all other MCPTT Private Calls.
+
+[R-6.8.7.2-002] The MCPTT Service shall be capable of requesting increased priority for the Participants of an MCPTT Emergency Private Call.
+
+[R-6.8.7.2-003] The MCPTT Service shall be capable of changing a Private Call (with Floor control) in progress to an MCPTT Emergency Private Call (with Floor control).
+
+[R-6.8.7.2-004] MCPTT Emergency Private Calls (with Floor control), including their content and signalling, shall have pre-emptive priority over all other types of MCPTT calls, except System Calls, MCPTT Emergency Group Calls and other MCPTT Emergency Private Calls (with Floor control).
+
+#### 6.8.7.3 Imminent Peril group call requirements
+
+[R-6.8.7.3-001] Void
+
+[R-6.8.7.3-002] Void
+
+[R-6.8.7.3-003] Void
+
+#### 6.8.7.4 MCPTT Emergency Alert
+
+##### 6.8.7.4.1 Requirements
+
+[R-6.8.7.4.1-001] Void
+
+[R-6.8.7.4.1-002] Void
+
+[R-6.8.7.4.1-003] Void
+
+[R-6.8.7.4.1-004] Void
+
+[R-6.8.7.4.1-005] Void
+
+[R-6.8.7.4.1-006] Void
+
+##### 6.8.7.4.2 MCPTT Emergency Alert cancellation requirements
+
+[R-6.8.7.4.2-001] Void
+
+[R-6.8.7.4.2-002] Void
+
+## 6.9 IDs and aliases
+
+[R-6.9-001] Void
+
+[R-6.9-002] Void
+
+[R-6.9-003] Void
+
+[R-6.9-004] Void
+
+## 6.10 User Profile management
+
+[R-6.10-001] Void
+
+[R-6.10-002] Void
+
+[R-6.10-003] Void
+
+[R-6.10-004] Void
+
+## 6.11 Support for multiple devices
+
+[R-6.11-001] Void
+
+[R-6.11-002] Void
+
+[R-6.11-003] Void
+
+## 6.12 Location
+
+[R-6.12-001] Void
+
+[R-6.12-002] Void
+
+[R-6.12-003] Void
+
+[R-6.12-004] Void
+
+[R-6.12-005] Void
+
+[R-6.12-006] Void
+
+[R-6.12-007] Void
+
+## 6.13 Security
+
+### 6.13.1 Overview
+
+Security covers areas designed to protect the confidentiality, integrity, and availability of information that is processed, stored, and transmitted. The security requirements listed here cover the areas of cryptographic protocols, authentication, access control, and regulatory issues.
+
+### 6.13.2 Cryptographic protocols
+
+[R-6.13.2-001] Void
+
+[R-6.13.2-002] Void
+
+[R-6.13.2-003] Void
+
+### 6.13.3 Authentication
+
+[R-6.13.3-001] Void
+
+### 6.13.4 Access control
+
+[R-6.13.4-001] Void
+
+[R-6.13.4-002] Void
+
+[R-6.13.4-003] Void
+
+[R-6.13.4-004] Void
+
+[R-6.13.4-005] Void
+
+[R-6.13.4-006] Void
+
+[R-6.13.4-007] Void
+
+[R-6.13.4-008] Void
+
+[R-6.13.4-009] Void
+
+[R-6.13.4-010] Void
+
+### 6.13.5 Regulatory issues
+
+[R-6.13.5-001] Void
+
+## 6.14 Interactions for MCPTT Group Calls and MCPTT Private Calls
+
+[R-6.14-001] Void
+
+[R-6.14-002] Void
+
+[R-6.14-003] The MCPTT Service shall only allow an MCPTT User to participate in one MCPTT Private Call (without Floor control) at a time.
+
+## 6.15 Audio MCPTT call performance
+
+### 6.15.1 General overview
+
+Meeting the KPIs defined in the following subclauses is based on a number of factors, including the selection of appropriate protocols, minimizing messaging, the backhaul technology used, and appropriate configuration of the deployed network. The corresponding requirements are intended to convey the resulting KPIs when all of those factors are taken into account. For example, where there is significant backhaul delay, that delay is expected to be added to the KPIs.
+
+### 6.15.2 General requirements
+
+[R-6.15.2-001] The architecture and protocols providing the MCPTT Service shall be designed in a way to eventually allow a deployed network to meet the KPIs specified hereafter (subclause 6.15.3.2 and subclause 6.15.4.2).
+
+### 6.15.3 MCPTT access time and mouth-to-ear latency
+
+#### 6.15.3.1 General overview
+
+For MCPTT Users, one of the most important performance criteria is the MCPTT Access time (KPI 1). The MCPTT Access time is defined as the time between when an MCPTT User request to speak (normally by pressing the MCPTT control on the MCPTT UE) and when this user gets a signal to start speaking. This time does not include confirmations from receiving users.
+
+The MCPTT Access time (KPI 1) does not include the time for an MCPTT User to affiliate to the group. This is a common scenario within public safety, meaning that affiliations to MCPTT Groups are long lived during several working hours. KPI 1 is applicable in both an MCPTT Group call setup request and subsequent MCPTT Requests that are part of the same call. KPI 1 for subsequent MCPTT Requests might take a slightly shorter time than the first MCPTT setup request of the same call due to its potential need of resource allocation in terms of bearer establishment. However from an end user perspective there is no need to differentiate required performance for an MCPTT Group call setup request and subsequent MCPTT Requests.
+
+The End-to-end MCPTT Access time (KPI 2) is defined as the time between when an MCPTT User requests to speak (normally by pressing the MCPTT control on the MCPTT UE) and when this user gets a signal to start speaking, including MCPTT call establishment (if applicable) and possibly acknowledgement from first receiving user before voice can be transmitted. Group calls can be set up with or without acknowledgements from receiving users.
+
+For MCPTT Private Calls (with Floor control), end-to-end MCPTT Access time (also KPI 2) is measured from the initiating client's Private call request to reception of either a Private Call response for automatic commencement or the MCPTT ringing indication for manual commencement. End-to-end access time for both automatic and manual commencement private calls (KPI 2) is shown in Figure 6.15.3.1.1.
+
+NOTE: The End-to-end MCPTT Access time (KPI 2) is not applicable for an MCPTT Group transmission call setup when no acknowledgement is requested from any Affiliated MCPTT Group Member.
+
+The Mouth-to-ear latency (KPI 3) is the time between an utterance by the transmitting user, and the playback of the utterance at the receiving user's speaker. Figure 6.15.3.1.1 illustrates the MCPTT Access time and Mouth-to-ear latency.
+
+
+
+Figure 6.15.3.1.1: Illustration of MCPTT access time and mouth-to-ear latency. The diagram shows two horizontal timelines for 'Transmitting user' and 'Receiving user'. On the transmitting user's timeline, a 'PTT Request' is sent, followed by a 'PTT Request grant' received, and then a 'PTT Release' is sent. A green bar labeled 'Talker Audio Capture' starts at the 'PTT Request grant' and ends at the 'PTT Release'. On the receiving user's timeline, a green bar labeled 'Audio Playback' starts at a point indicated by a dashed vertical line from the start of the 'Talker Audio Capture' bar. An arrow labeled 'Mouth-to-ear latency (KPI 3)' points from the start of the 'Talker Audio Capture' bar to the start of the 'Audio Playback' bar. A bracket labeled 'PTT Access time (KPI 1) or End-to-end PTT Access time (KPI 2)' spans from the 'PTT Request' to the 'PTT Request grant' on the transmitting user's timeline.
+
+Figure 6.15.3.1.1: Illustration of MCPTT access time and mouth-to-ear latency
+
+#### 6.15.3.2 Requirements
+
+[R-6.15.3.2-001] KPI 1, KPI 2, and KPI 3 should be measured where there is negligible backhaul delay.
+
+[R-6.15.3.2-002] The MCPTT Service shall provide the MCPTT Access time and Mouth-to-ear latency specified in this subclause to all MCPTT Users related to an MCPTT call regardless of call type (e.g., group, Private Call), group size and/or user density.
+
+NOTE: This ensures that all MCPTT Users experience the same performance regardless of whether the audio is transferred over unicast or multicast delivery.
+
+[R-6.15.3.2-003] The MCPTT Service shall be capable of providing the performance specified herein for all Affiliated MCPTT Group Members in the Group Call when there is not a transcoder in the bearer path.
+
+[R-6.15.3.2-004] The MCPTT Service shall be capable of providing the performance specified herein for all Participants in a Private Call when there is not a transcoder in the bearer path.
+
+[R-6.15.3.2-005] The KPIs defined in this subclause shall apply in an 3GPP network under traffic load not exceeding 70% of each network nodes capacity.
+
+[R-6.15.3.2-006] On networks with QoS services, the KPIs defined in this subclause shall apply when the total sector loading of the serving sector by MCPTT Users with equal or greater priority than the subject MCPTT User is less than 70%.
+
+[R-6.15.3.2-007] The KPIs defined in this subclause shall apply to group calls when the transmitting MCPTT User is connected to the MCPTT Service and has selected an MCPTT Group.
+
+[R-6.15.3.2-008] The KPIs defined in this subclause shall apply to group calls when the receiving MCPTT User is connected to the MCPTT Service and affiliated with the MCPTT Group.
+
+[R-6.15.3.2-009] The KPIs defined in this subclause shall apply to Automatic Commencement Private Calls when both the transmitting and receiving MCPTT Users are connected to the MCPTT Service.
+
+[R-6.15.3.2-010] Void
+
+[R-6.15.3.2-011] When there are transcoding functions in the bearer path of the MCPTT Service, the performance provided by the MCPTT Service shall be no more than 40 ms greater than the performance specified herein when there are no transcoding functions in the bearer path.
+
+[R-6.15.3.2-012] For group calls where no acknowledgement is requested from affiliated MCPTT group members, the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 95% of all MCPTT Request.
+
+[R-6.15.3.2-012a] For group and private calls where the call is already established, the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 95% of all MCPTT PTT Requests.
+
+[R-6.15.3.2-013] For MCPTT Emergency Group Calls and Imminent Peril Calls the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 99% of all MCPTT Requests.
+
+[R-6.15.3.2-014] For group calls where automatic acknowledgement is requested from the UEs of the affiliated MCPTT group members, the MCPTT Service shall provide an End-to-end MCPTT Access time (KPI 2) less than 1000 ms for users under coverage of the same network.
+
+[R-6.15.3.2-015] The MCPTT Service shall provide a Mouth-to-ear latency (KPI 3) that is less than 300 ms for 95% of all voice bursts.
+
+[R-6.15.3.2-016] There shall be no (0 ms) initial lost audio at receiving user.
+
+[R-6.15.3.2-017] There shall be no (0 ms) trailing lost audio at the end of the voice burst at receiving user. [R-6.15.3.2-018] The KPIs defined in this subclause shall apply to Manual Commencement Private Calls when both the transmitting and receiving MCPTT Users are connected to the MCPTT Service.
+
+[R-6.15.3.2-019] The MCPTT Service shall provide private call End-to-end MCPTT Access time (KPI 2) equal to or less than 1000 ms for users under coverage of the same network when the MCPTT private call is setup in the Manual Commencement mode.
+
+[R-6.15.3.2-020] The MCPTT Service shall provide private call End-to-end MCPTT Access time (KPI 2) equal to or less than 1000 ms for users under coverage of the same network when the MCPTT private call is setup in the Automatic Commencement mode.
+
+### 6.15.4 Late call entry performance
+
+#### 6.15.4.1 General overview
+
+An MCPTT User is able to join or leave already ongoing MCPTT Group calls. Late call entry is the activity when an Affiliated MCPTT Group Member joins an MCPTT Group call in which other Affiliated MCPTT Group Members are already active. The Late call entry time (KPI 4) is the time to enter an ongoing MCPTT Group call measured from the time that a user decides to monitor such an MCPTT Group Call, to the time when the MCPTT UE's speaker starts to play the audio. The performance requirements for Late call entry time only applies to when there is ongoing voice transmitted at the time the MCPTT User joins the call.
+
+In a Late call entry there might be an initial lost audio of the voice burst sent to the new Receiving MCPTT Group Member. Figure 6.15.4.1.1 illustrates the Late call entry time.
+
+
+
+The diagram illustrates the sequence of events for a Push-to-Talk (PTT) call, focusing on the 'Late call entry time' (KPI 4) for the receiving user.
+
+1. **Transmitting user**: Initiates a 'PTT request', receives a 'PTT request grant', and begins 'Talker Audio Capture'.
+
+2. **Receiving user**: Experiences 'Initial lost audio' at the start of the call.
+
+3. **Network and UE processing delay**: The time interval between the start of audio capture and the grant of the call entry.
+
+4. **Late Call Entry granted by MCPTT application server**: The point in time when the receiving user's application server approves the late entry.
+
+5. **Late Call Entry time (KPI 4)**: The time interval from the start of audio capture to the 'Late Call Entry by receiving user'.
+
+6. **Audio Playback**: The period when the receiving user hears the audio.
+
+7. **PTT release**: The transmitting user ends the call.
+
+Figure 6.15.4.1.1: Illustration of Late call entry time. The diagram shows the interaction between a Transmitting user and a Receiving user. The Transmitting user sends a PTT request, which is granted with a PTT request grant. The user then starts Talker Audio Capture. The Receiving user receives the audio, but there is an Initial lost audio period. The network and UE processing delay occurs, followed by a Late Call Entry granted by the MCPTT application server. The Late Call Entry time (KPI 4) is indicated. The Receiving user then starts Audio Playback. The Transmitting user eventually sends a PTT release.
+
+Figure 6.15.4.1.1: Illustration of Late call entry time
+
+#### 6.15.4.2 Requirements
+
+[R-6.15.4.2-001] The KPIs in this subclause shall apply for terrestrial use only, and when users are under coverage of the same network.
+
+NOTE: Terrestrial use refers to using terrestrial 3GPP access, e.g. not using satellite 3GPP access. It includes support of air-to-ground scenarios, such as communication with MCPTT users in helicopters, fixed wing aircraft or other crewed aerial vehicles.
+
+[R-6.15.4.2-002] The KPIs defined in this subclause shall apply in an 3GPP network under traffic load not exceeding 70% of each network nodes capacity.
+
+[R-6.15.4.2-002a] The KPIs defined in this subclause shall apply to MCPTT users who have affiliated or have been affiliated by the network and are now performing late call entry due to activity on the affiliated group.
+
+NOTE: Cases of UE mobility, or loss of coverage and re-establishment, are not covered.
+
+[R-6.15.4.2-003] The maximum Late call entry time (KPI 4a) for calls without application layer encryption within one MCPTT system shall be less than 150 ms for 95% of all Late call entry requests.
+
+[R-6.15.4.2-004] The maximum Late call entry time (KPI 4b) for application layer encrypted calls within one MCPTT system should meet the requirements for KPI 4 for unencrypted calls.
+
+[R-6.15.4.2-005] The maximum Late call entry time (KPI 4b) for application layer encrypted calls within one MCPTT system shall be less than 350 ms for 95% of all Late Call Entries into encrypted calls.
+
+[R-6.15.4.2-006] The Late call entry Time for encrypted calls interworking with other non-3GPP PTT systems should meet the requirements for KPI 4b for application layer encrypted calls within one MCPTT system.
+
+NOTE: Additional delay deriving from the non-3GPP PTT system is not included in this KPI.
+
+[R-6.15.4.2-007] The additional Late call entry Time for an MCPTT UE late entering an application layer encrypted call interworking with other non-3GPP PTT systems shall not exceed the difference in the encrypted and unencrypted Late call entry Times for the interworking system.
+
+### 6.15.5 Audio / voice quality
+
+[R-6.15.5-001] The MCPTT UE shall support at least one mandatory 3GPP voice codec.
+
+NOTE 1: The UE implementation could include other non-3GPP voice codecs, e.g., TETRA voice codecs, P25 voice codecs [4].
+
+NOTE 2: Refer to [R-6.4.9-006], which enables an MCPTT Administrator to set the preferred voice codec for an MCPTT Group.
+
+[R-6.15.5-002] When an MCPTT call is within one MCPTT system the average MOS-LQO shall be greater than or equal to 3.0 measured according to the ITU standard Perceptual Evaluation of Speech Quality (PESQ) as defined in P.862 [7] and P.862.1 [8].
+
+[R-6.15.5-003] When an MCPTT call involves interworking with other non-3GPP PTT systems the average MOS-LQO shall be greater than or equal to 2.7 measured according to the ITU standard PESQ as defined in P.862 [7] and P.862.1 [8].
+
+[R-6.15.5-004] When an MCPTT call is within one MCPTT system the average MOS-LQO shall be greater than or equal to 3.0 measured according to the ITU standard Perceptual Objective Listening Quality Assessment (POLQA) as defined in P.863 [9].
+
+[R-6.15.5-005] When an MCPTT call involves interworking with other non-3GPP PTT systems the average MOS LQO shall be greater than or equal to 2.7 measured according to the ITU standard POLQA as defined in P.863 [9].
+
+## 6.15.6 Radio Resource Efficiency Performance
+
+[R-6.15.6-001] Void
+
+[R-6.15.6-002] Void
+
+## 6.16 Additional services for MCPTT calls
+
+### 6.16.1 Discreet listening capabilities
+
+[R-6.16.1-001] Void
+
+### 6.16.2 Ambient listening
+
+#### 6.16.2.1 Overview of ambient listening
+
+Ambient Listening is a feature that allows an authorized MCPTT User, typically a dispatcher, to cause an MCPTT UE to initiate a call which results in no indication on the MCPTT UE that it is transmitting. Ambient Listening can be initiated by an authorized MCPTT User who wants to be listened to by another remote authorized MCPTT User or can be initiated by a remote authorized MCPTT User who wants to listen to another MCPTT User. The purpose of this feature allows a dispatcher to listen to activities at the Location of the remote MCPTT UE to find out what is happening around that MCPTT UE without providing an indication to the MCPTT User or people around the user (whom the MCPTT User does not want to make aware of this action) that this is happening. This type of call is different from other types of call, as for Ambient Listening audio is only transmitted to one party in the call (i.e., a dispatcher or an authorized MCPTT User that is acting in a similar role to a dispatcher).
+
+This is used for stolen MCPTT UEs, monitoring officers, officer safety and particular operations, where it is important that the MCPTT UE does not indicate what is happening.
+
+#### 6.16.2.2 Ambient listening requirements
+
+##### 6.16.2.2.1 General Ambient Listening requirements
+
+[R-6.16.2.2.1-001] Void
+
+[R-6.16.2.2.1-002] Void
+
+[R-6.16.2.2.1-003] Void
+
+[R-6.16.2.2.1-004] The MCPTT Service shall terminate Ambient Listening if the MCPTT User being listened to starts to transmit in an MCPTT Private Call or an MCPTT Group Call.
+
+NOTE: An authorized MCPTT User could initiate Discreet Listening at this point if needed.
+
+#### 6.16.2.2.2 Remotely initiated Ambient Listening requirements
+
+[R-6.16.2.2.2-001] Void
+
+[R-6.16.2.2.2-002] Void
+
+#### 6.16.2.2.3 Locally initiated Ambient Listening requirements
+
+[R-6.16.2.2.3-001] Void
+
+[R-6.16.2.2.3-002] Void
+
+### 6.16.3 Remotely initiated MCPTT call
+
+#### 6.16.3.1 Overview
+
+A Remotely initiated MCPTT Call is a feature that allows an authorized user, typically a dispatcher, to cause a remote MCPTT UE to initiate a call by itself, without its user explicitly initiating the call by depressing the PTT switch. The purpose of this feature allows the dispatcher to listen to activities at the Location of the remote MCPTT UE to find out what is happening around that MCPTT UE. This feature is also known as "Remote Unit Monitoring" in P25 systems.
+
+There are two typical use cases for this feature.
+
+The first one is the case where a user could have been incapacitated. This could be both accidentally, say a traffic accident, or deliberately, for example a violent attack. In both cases it would be necessary to remotely open the microphone of the MCPTT UE in order to allow another user or a group of users to listen to what is happening to prepare assistance. The communication that is set up is either a Private Call or a Group Call, and the call could optionally be visible to the remote MCPTT UE's user.
+
+The second one is the case of a stolen MCPTT UE. Here it is just necessary to activate the radio so that a dispatcher can listen to any background noise or speech in order to make an analysis of the situation. In this situation, the initiation of the call from the remote MCPTT UE, typically a Private Call in that case, is not visible by that MCPTT UE's user.
+
+Other use cases, such as undercover operations, discreet surveillance of users or investigations, could exist depending on the missions of the critical communications users and on legislations.
+
+The behaviour of the remotely initiated Call is not different from a normal call initiated by the local user. The same rules for resource allocation and interactions with other services apply, but the initiator of the feature can have the capability to request a pre-emptive or high priority for that Call to ensure it is set up even in case of resource congestion or to limit disturbance by other services.
+
+#### 6.16.3.2 Requirements
+
+[R-6.16.3.2-001] Void
+
+[R-6.16.3.2-002] Void
+
+[R-6.16.3.2-003] Void
+
+[R-6.16.3.2-004] Void
+
+## 6.16.4 Recording and audit requirements
+
+[R-6.16.4-001] Void
+
+[R-6.16.4-002] Void
+
+[R-6.16.4-003] Void
+
+[R-6.16.4-004] Void
+
+[R-6.16.4-005] Void
+
+[R-6.16.4-006] Void
+
+[R-6.16.4-007] Void
+
+[R-6.16.4-008] Void
+
+[R-6.16.4-009] Void
+
+[R-6.16.4-010] Void
+
+## 6.17 Interaction with telephony services
+
+[R-6.17-001] Void
+
+[R-6.17-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure the interaction between telephony calls and MCPTT calls for an MCPTT User.
+
+[R-6.17-003] Void
+
+## 6.18 Interworking
+
+### 6.18.1 Non-3GPP access
+
+[R-6.18.1-001] Void
+
+### 6.18.2 Interworking between MCPTT systems
+
+[R-6.18.2-001] Void
+
+[R-6.18.2-002] Void
+
+[R-6.18.2-003] Void
+
+[R-6.18.2-004] Void
+
+[R-6.18.2-005] Void
+
+[R-6.18.2-006] Void
+
+[R-6.18.2-007] Void
+
+### 6.18.3 Interworking with non-3GPP PTT systems
+
+#### 6.18.3.1 Overview
+
+Mission critical users currently employ a wide range of narrowband mission critical Push To Talk services. Project 25 (governed by the TIA-102 standards) and TETRA (governed by ETSI standards) are digital public safety grade PTT systems. In addition, "legacy" or "conventional FM" systems are common throughout the world. These systems provide
+
+PTT and related services that are analogous to those provided by MCPTT, including group calls, Private Calls, broadcast calls, dynamic group management and other services.
+
+The MCPTT Service is intended to interwork with these non-3GPP PTT systems.
+
+### 6.18.3.2 Project 25
+
+[R-6.18.3.2-001] The MCPTT Service shall enable interworking with non-3GPP PTT Systems that are compliant with the TTA-102 (P25) standards.
+
+[R-6.18.3.2-002] Interworking between the MCPTT Service and P25 shall be capable of interworking with a multiplicity of independently administered Project 25 Radio Frequency Subsystems (RFSS).
+
+[R-6.18.3.2-003] Interworking between the MCPTT Service and P25 shall support interoperable MCPTT Group Calls between MCPTT Users and P25 subscriber units and consoles.
+
+[R-6.18.3.2-004] Interworking between the MCPTT Service and P25 shall support interoperable MCPTT Emergency Group Calls and P25 emergency calls.
+
+[R-6.18.3.2-005] Interworking between the MCPTT Service and P25 shall support end-to-end encrypted MCPTT Group Calls between MCPTT Users and P25 subscriber units and consoles.
+
+[R-6.18.3.2-006] Interworking between the MCPTT Service and P25 shall provide a means for an authorized user to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
+
+[R-6.18.3.2-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize an MCPTT User to be able to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
+
+[R-6.18.3.2-008] Interworking between the MCPTT Service and P25 shall provide a means for an authorized P25 subscriber units and consoles to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
+
+[R-6.18.3.2-009] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize a P25 subscriber unit or P25 console to be able to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
+
+[R-6.18.3.2-010] Interworking between the MCPTT Service and P25 shall support Group Regrouping that includes both MCPTT Groups and P25 groups.
+
+[R-6.18.3.2-011] Interworking between the MCPTT Service and P25 shall support User Regrouping that includes both MCPTT Users and P25 subscriber units.
+
+[R-6.18.3.2-012] Interworking between the MCPTT Service and P25 shall support interworking of Group-Broadcast Group Calls and P25 announcement group calls.
+
+[R-6.18.3.2-013] Interworking between the MCPTT Service and P25 shall support interoperable User IDs and P25 subscriber IDs.
+
+[R-6.18.3.2-014] Interworking between the MCPTT Service and P25 shall support interoperable PTT Private Calls (with Floor control) between an MCPTT User and a P25 subscriber unit or console.
+
+[R-6.18.3.2-015] Interworking between the MCPTT Service and P25 shall provide a mechanism to reconcile the Private Call (with Floor control) commencement mode between an MCPTT User and a P25 subscriber unit or console.
+
+[R-6.18.3.2-016] Interworking between the MCPTT Service and P25 shall support end-to-end encrypted PTT Private Calls (with Floor control) between an MCPTT User and a P25 subscriber unit or console.
+
+[R-6.18.3.2-017] Interworking between the MCPTT Service and P25 shall support a means of reconciling codecs between interoperable calls.
+
+[R-6.18.3.2-018] Interworking between the MCPTT Service and P25 shall support conveyance of Losing audio from P25 subscriber units and consoles to authorized MCPTT Users.
+
+[R-6.18.3.2-019] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize MCPTT Users to be able to receive Losing audio from P25 subscribers units and consoles.
+
+[R-6.18.3.2-020] For Private Calls (with Floor control) interworking between the MCPTT Service and non-3GPP PTT systems that do not support Private Call override (e.g., Project 25 Phase 1 systems), the Participant attempting to override shall be notified that the override can not be accomplished.
+
+[R-6.18.3.2-021] For Private Call (with Floor control) interworking, between the MCPTT Service and non-3GPP PTT systems that do support Private Call override (e.g., Project 25 Phase 2 systems), the MCPTT Service shall provide a mechanism for Participants to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant is ranked higher than the priority level of the transmitting Participant.
+
+### 6.18.3.3 TETRA
+
+[R-6.18.3.3-001] The MCPTT Service shall enable interworking with non-3GPP PTT Systems that are compliant with the ETSI TETRA standards.
+
+[R-6.18.3.3-002] Interworking between the MCPTT Service and TETRA shall be capable of interworking with a multiplicity of independently administered TETRA systems (Switching and management Infrastructures).
+
+[R-6.18.3.3-003] Interworking between the MCPTT Service and TETRA shall support interoperable MCPTT Group Calls between MCPTT Users and TETRA mobile stations and consoles.
+
+[R-6.18.3.3-004] Interworking between the MCPTT Service and TETRA shall support interoperable MCPTT Emergency Group Calls and TETRA emergency calls.
+
+[R-6.18.3.3-005] Interworking between the MCPTT Service and TETRA shall support end-to-end encrypted MCPTT Group Calls between MCPTT Users supporting the TETRA voice codec and end-to-end encryption and TETRA mobile stations and consoles.
+
+[R-6.18.3.3-006] Interworking between the MCPTT Service and TETRA shall provide a means for an authorized user to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles.
+
+[R-6.18.3.3-007] Interworking between the MCPTT Service and TETRA shall provide a means for an authorized TETRA mobile station or console to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles.
+
+[R-6.18.3.3-008] Interworking between the MCPTT Service and TETRA shall support Group Regrouping that includes both MCPTT Groups and TETRA groups.
+
+[R-6.18.3.3-009] Interworking between the MCPTT Service and TETRA shall support User Regrouping that includes both MCPTT Users and TETRA mobile stations.
+
+[R-6.18.3.3-010] Interworking between the MCPTT Service and TETRA shall support interoperable User IDs and TETRA IDs.
+
+[R-6.18.3.3-011] Interworking between the MCPTT Service and TETRA shall support interoperable PTT Private Calls between an MCPTT User and a TETRA mobile station or console.
+
+[R-6.18.3.3-012] Interworking between the MCPTT Service and TETRA shall support end-to-end encrypted PTT Private Calls between an MCPTT User supporting TETRA codec and encryption and a TETRA mobile station or console.
+
+[R-6.18.3.3-013] Interworking between the MCPTT Service and TETRA shall support a means of reconciling codecs between interoperable calls when not end-to-end encrypted.
+
+[R-6.18.3.3-014] For Private Call (with Floor control) interworking, between the MCPTT Service and non-3GPP PTT systems that do support Private Call override, the MCPTT Service shall provide a mechanism for Participants to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant is ranked higher than the priority level of the transmitting Participant.
+
+### 6.18.3.4 Legacy land mobile radio
+
+[R-6.18.3.4-001] The MCPTT Service shall enable interworking with legacy Land Mobile Radio systems that are compliant with the TIA-603-D [3] Standard.
+
+[R-6.18.3.4-002] Interworking between the MCPTT Service and TIA-603 systems shall be capable of interworking with a multiplicity of independently administered systems based on the TIA-603-D [3] Standard.
+
+[R-6.18.3.4-003] Interworking between the MCPTT Service and TIA-603 systems shall support interoperable PTT Group calls between MCPTT Users and TIA-603 subscriber units and consoles.
+
+[R-6.18.3.4-004] Interworking between the MCPTT Service and TIA-603 systems shall provide a mechanism for an authorized MCPTT User to initiate an override within a PTT Group call that has both MCPTT Users and TIA 603 subscriber units and consoles.
+
+[R-6.18.3.4-005] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize an MCPTT User to be able to initiate an override of a PTT Group call between MCPTT Users and TIA-603 subscriber units and consoles.
+
+[R-6.18.3.4-006] Interworking between the MCPTT Service and TIA-603 systems shall provide a mechanism for an authorized TIA-603 subscriber unit or console to initiate an override within a PTT Group call that has both MCPTT Users and TIA 603 subscriber units and consoles.
+
+[R-6.18.3.4-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize a TIA-603 subscriber unit or TIA-603 console to be able to initiate an override of a PTT Group call between MCPTT Users and TIA-603 subscriber units and consoles.
+
+[R-6.18.3.4-008] Interworking between the MCPTT Service and TIA-603 systems shall support interoperable PTT Private Calls (with Floor control) between MCPTT Users and TIA-603 subscriber units or consoles.
+
+[R-6.18.3.4-009] Interworking between the MCPTT Service and TIA-603 systems shall support a means of reconciling codecs between interoperable calls.
+
+[R-6.18.3.4-010] Interworking between the MCPTT Service and TIA-603 systems shall support conveyance of Losing audio from TIA 603 subscribers units and consoles to suitably privileged MCPTT Users.
+
+[R-6.18.3.4-011] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize MCPTT Users to be able to receive Losing audio from TIA-603 subscribers units and consoles.
+
+### 6.18.3.5 Void
+
+## 6.18.4 GSM-R
+
+### 6.18.4.1 Overview
+
+GSM-R, governed by 3GPP standards, is widely and globally used for rail communication. GSM-R offers capabilities analogous to those provided by MCPTT, including group calls, point-to point calls, broadcast calls, dynamic group management and the bearer service for train safety applications.
+
+### 6.18.4.2 Requirements
+
+[R-6.18.4.2-001] Void
+
+[R-6.18.4.2-002] Void
+
+[R-6.18.4.2-002a] Void
+
+[R-6.18.4.2-002b] Void
+
+[R-6.18.4.2-003] The MCPTT Service shall enable interworking between MCPTT Group Call and Advanced Speech Call Items used in GSM-R.
+
+NOTE: The impact on GSM-R needs to be minimised.
+
+[R-6.18.4.2-004] Interworking between the MCPTT Service and GSM-R shall support interoperable PTT Private Calls between an MCPTT User and a GSM-R mobile station or controller terminal.
+
+[R-6.18.4.2-005] Interworking between the MCPTT Service and GSM-R voice services shall support a means of reconciling codecs.
+
+## 6.19 MCPTT coverage extension using ProSe UE-to-Network Relays
+
+[R-6.19-001] Void
+
+[R-6.19-002] Void
+
+[R-6.19-003] Void
+
+[R-6.19-004] Void
+
+[R-6.19-005] Void
+
+[R-6.19-006] Void
+
+---
+
+## 7 MCPTT Service requirements specific to off-network use
+
+### 7.1 Off-network Push To Talk overview
+
+The MCPTT Service while operating in off-network mode comprises a set or collection of functions necessary to provide Mission Critical Push To Talk (MCPTT) using a ProSe direct (UE-to-UE) Communication path (ProSe direct communication path) for transport. The ProSe direct communication path does not traverse the network infrastructure.
+
+Users operating off the network are either out of network coverage (not served by a 3GPP network) (e.g., in a remote mountain area fighting a forest fire 20 miles from the nearest network) or have selected a ProSe direct communication path for MCPTT while in network coverage. MCPTT Users operating off the network need to be in ProSe direct communication range in order to communicate.
+
+NOTE 1: While the network is likely to be a primary, reliable transport of MCPTT communications, there are many situations where MCPTT communications are needed in areas where the network is not available, or coverage is not reliable.
+
+MCPTT Users outside of the coverage of the fixed network might be first responders in a rural area assisting in a response to a plane crash, fire fighters in a remote mountain area fighting a forest fire or police officers inside a residence responding to a domestic issue. Off-network MCPTT communications are expected to be immediately accessible to users in the absence of the network.
+
+MCPTT Users in network coverage might be working in a confined area, such as fire fighters fighting a structure fire where direct UE-to-UE communication is more desirable and reliable. Users can communicate directly with one another without having to overcome the resistance of a building and distance to the nearest base station to communicate with other members of their team inside the building that are nearby.
+
+To operate off the network, an MCPTT UE is capable of automatically switching to a ProSe direct communication path for use of MCPTT when detecting an off-network (out of coverage) condition. In addition a mechanism is provided for an authorized user to select (manually switch to) a ProSe direct communication path for use of off-network MCPTT communications (e.g., while in network coverage).
+
+When operating off the network, the MCPTT Service is provided by the MCPTT application on the UE as compared to operations on the network, where the MCPTT Application on the UE interacts with an MCPTT server and the network to provide the MCPTT Service.
+
+NOTE 2: For MCPTT UEs that have selected a ProSe Direct Communication path for use of MCPTT while in network coverage, signalling with the network and MCPTT Service might be available (e.g., radio resource allocation, MCPTT User Profile management updates and cryptographic key management updates), while the MCPTT User transmissions would be direct between the MCPTT UEs (e.g., not traversing the network).
+
+The Off-Network MCPTT Service builds upon ProSe enablers to establish, maintain and terminate the signalling and communication path(s) among the off-network users. To the extent feasible, it is expected that the end user's experience is similar regardless if the MCPTT Service is used with a 3GPP network or based on the use of a ProSe direct communication path.
+
+The Off-Network MCPTT Service is intended to support communication between a group of users (a group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. However, the MCPTT Service also supports Private Calls between pairs of users.
+
+When operating off the network the MCPTT Service allows users to request the permission to talk (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control).
+
+The Off-Network MCPTT Service provides a means for a user with higher priority (e.g., MCPTT Emergency condition) to override (interrupt) the current talker. The Off-Network MCPTT Service also supports a mechanism to limit the time a user talks (hold the floor) thus permitting users of the same or lower priority a chance to gain the floor.
+
+The Off-Network MCPTT Service provides the means for a user to monitor activity on a number of separate calls and enables the user to switch focus to a chosen call. An Off-Network MCPTT Service user might join an already established MCPTT Group call (Late call entry). In addition the Off-Network MCPTT Service supports User IDs, aliases and user Location determination features.
+
+For operation off the network (e.g., when out of network coverage), an MCPTT UE is (pre-)provisioned by an MCPTT Administrator and/or authorized user with the following in order to use MCPTT:
+
+- a) An MCPTT User Profile associated with each of the intended MCPTT Users of the MCPTT UE that might be used for off-network operation;
+ - 1) An alphanumeric identifier (with a minimum length of N3) (i.e., alias) for each MCPTT User;
+ - 2) A number of off-network MCPTT Groups for use by the MCPTT User;
+ - 3) An alphanumeric identifier (i. e., alias) for the authorized off-network MCPTT Groups;
+ - 4) A Mission Critical Organization name if available, associated with each of the intended MCPTT Users or Administrator;
+ - 5) A number of off-network MCPTT Users for Private Call for which the MCPTT User is authorized;
+- b) Authentication and end to end security keys.
+
+NOTE 3: MCPTT UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
+
+An MCPTT UE operating off the network is capable of transmitting the talker Location information, User ID, alias(es), off-network MCPTT Group ID, group alias and, if available, Mission Critical Organization name of the user who is talking (i.e., whose UE is transmitting) to all other users in a call including MCPTT UEs operating off the network that are late entering a call in progress.
+
+The Off-Network MCPTT Service uses the capabilities defined in ProSe TS 22.278 [5], including the ProSe Relay capabilities defined in ProSe TS 22.278 [5] and GCSE\_LTE TS 22.468 [6].
+
+NOTE 4: As indicated in TS 22.278 [5] use of a ProSe Direct Communication path outside of network coverage is only applicable for Public Safety ProSe enabled UEs. For non-Public Safety ProSe enabled UEs the selection of the most appropriate communication path (ProSe Communication path (direct or routed via local basestation) or 3GPP network path) is under network control and based on operator preferences.
+
+MCPTT Service requirements specific to off-network use are defined in clause 7. Common MCPTT service requirements defined in clause 5 apply whether the MCPTT Service is in use on the network or off the network.
+
+## 7.2 General off-network MCPTT requirements
+
+[R-7.2-001] Void
+
+[R-7.2-002] Void
+
+[R-7.2-003] Void
+
+[R-7.2-004] Void
+
+[R-7.2-005] Void
+
+## 7.3 Floor control
+
+### 7.3.1 General aspects
+
+[R-7.3.1-001] The off-network Floor control functionality in an MCPTT Service shall determine at a point in time which off-network Participant(s) are allowed to transmit to other off-network Participants.
+
+[R-7.3.1-002] The off-network Floor control functionality in an MCPTT Service shall determine at a point in time which received transmission(s) from off-network Participant(s) shall be presented to the receiving off-network Participant(s).
+
+### 7.3.2 Requesting permission to transmit
+
+[R-7.3.2-001] A Participant in an off-network MCPTT Group call, with the authority to transmit, shall be able to request to transmit to the off-network MCPTT Group.
+
+[R-7.3.2-002] The off-network Floor control functionality shall have a mechanism for resolving simultaneous requests for permission to transmit within the same call.
+
+[R-7.3.2-003] Following an MCPTT Request for permission to transmit, the Affiliated MCPTT Group Member that is allowed to transmit shall be given an indication that the member is allowed to transmit on the member's Selected MCPTT Group.
+
+[R-7.3.2-004] Following an MCPTT Request for permission to transmit, an Affiliated MCPTT Group Member that is not allowed to transmit on the Selected MCPTT Group shall be given an indication that permission to transmit was rejected or queued.
+
+[R-7.3.2-005] Following an MCPTT Private Call (with Floor control) request for permission to transmit, the MCPTT User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCPTT User.
+
+[R-7.3.2-006] Following an MCPTT Private Call (with Floor control) request for permission to transmit, an MCPTT User that is not allowed to transmit shall be given an indication that the permission to transmit was rejected.
+
+### 7.3.3 Override
+
+[R-7.3.3-001] An MCPTT UE shall be pre-provisioned by an MCPTT Administrator and/or authorized user with the necessary information in order that Floor control override may operate during off-network MCPTT.
+
+[R-7.3.3-002] The MCPTT Service shall provide a mechanism for MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types, when operating off the network, be granted a request to override an active off-network MCPTT transmission.
+
+[R-7.3.3-003] The priority hierarchy used for granting a request to override an active MCPTT transmission shall contain at least four (4) levels.
+
+[R-7.3.3-004] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or call type are ranked higher than the priority level of the transmitting Participant or call type.
+
+[R-7.3.3-005] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
+
+[R-7.3.3-006] The MCPTT Service shall provide a mechanism to enable an MCPTT Administrator to configure which MCPTT Group transmission a Participant(s) receives, overriding and/or overridden for cases where an authorized Participant overrides an off-network MCPTT transmission. This mechanism, at the receiving Participant, shall also determine which transmission should be presented to the MCPTT User when an unauthorized transmission override has occurred due to a failure of transmit Floor control (e.g., due to the best effort nature of ProSe direct communication).
+
+[R-7.3.3-007] If the MCPTT Group has been configured to only allow the overriding transmitting Participant to transmit, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant.
+
+[R-7.3.3-008] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants to transmit, the MCPTT Service shall provide a mechanism for authorized receiving Participants to be able to listen to both the overriding transmission and any overridden Participant transmissions, dependent on configuration.
+
+### 7.3.4 Terminating permission to transmit
+
+[R-7.3.4-001] A transmitting Participant shall be able to indicate to the Off-Network MCPTT Service that the Participant no longer wants to transmit.
+
+[R-7.3.4-002] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
+
+### 7.3.5 Transmit time limit
+
+[R-7.3.5-001] An MCPTT UE shall be pre-provisioned by an MCPTT Administrator and/or authorized user with the necessary information in order that a transmit time limit function may operate during off-network MCPTT.
+
+[R-7.3.5-002] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit.
+
+[R-7.3.5-003] The Floor control functionality shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
+
+[R-7.3.5-004] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
+
+[R-7.3.5-005] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
+
+[R-7.3.5-006] The Floor control functionality shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached.
+
+## 7.4 Call Termination
+
+[R-7.4-001] The MCPTT Service when operating off the network shall terminate a call after a period of inactivity.
+
+[R-7.4-002] The MCPTT Service when operating off the network shall provide a mechanism for an MCPTT Administrator to preconfigure the inactivity timer.
+
+[R-7.4-003] Void
+
+[R-7.4-004] Void
+
+[R-7.4-005] Void
+
+[R-7.4-006] Void
+
+## 7.5 Broadcast Group
+
+[R-7.5-001] Void
+
+[R-7.5-002] Void
+
+## 7.6 Dynamic group management (i.e., dynamic regrouping)
+
+NOTE: No specific off-network MCPTT requirements for dynamic group management have been identified.
+
+## 7.7 MCPTT priority requirements
+
+[R-7.7-001] Void
+
+[R-7.7-002] The Off-Network MCPTT Service shall pass these attributes to the ProSe transport layer for the purposes of prioritizing the associated user data.
+
+[R-7.7-003] Void
+
+## 7.8 Call types based on priorities
+
+### 7.8.1 MCPTT Emergency Group Call requirements
+
+[R-7.8.1-001] Void
+
+[R-7.8.1-002] Void
+
+[R-7.8.1-003] Void
+
+### 7.8.2 MCPTT Emergency Group Call cancellation requirements
+
+[R-7.8.2-001] Void
+
+### 7.8.3 Imminent Peril Call
+
+#### 7.8.3.1 Imminent Peril group call requirements
+
+[R-7.8.3.1-001] Void
+
+[R-7.8.3.1-002] Void
+
+[R-7.8.3.1-003] Void
+
+[R-7.8.3.1-004] Void
+
+[R-7.8.3.1-005] Void
+
+#### 7.8.3.2 Imminent Peril group call cancellation requirements
+
+[R-7.8.3.2-001] Void
+
+[R-7.8.3.2-002] Void
+
+## 7.9 Location
+
+[R-7.9-001] Void
+
+## 7.10 Security
+
+[R-7.10-001] Void
+
+[R-7.10-002] Void
+
+## 7.11 Audio MCPTT Call performance
+
+### 7.11.1 MCPTT Access time and Mouth-to-ear latency
+
+#### 7.11.1.1 General overview
+
+For MCPTT Users, one of the most important performance criteria is the MCPTT Access time (KPI 1). The MCPTT Access time is defined as the time between when an MCPTT User requests to speak (normally by pressing the MCPTT control on the UE) and when this user gets a signal to start speaking. This time does not include confirmations from receiving users.
+
+The Mouth-to-ear latency (KPI 3) is the time between an utterance by the transmitting user, and the playback of the utterance at the receiving user's speaker. Figure 7.11.1.1.1 illustrates the MCPTT Access time and Mouth-to-ear latency.
+
+
+
+Figure 7.11.1.1-1: Illustration of MCPTT Access time and Mouth-to-ear latency. The diagram shows two horizontal timelines for 'Transmitting user' and 'Receiving user'. On the transmitting user's timeline, a 'PTT Request' is sent, followed by a 'PTT Access time (KPI 1)' interval, then a 'PTT Request grant' is received, and finally a 'PTT Release' is sent. A green bar labeled 'Talker Audio Capture' starts at the 'PTT Request grant' and ends at the 'PTT Release'. On the receiving user's timeline, a green bar labeled 'Audio Playback' starts at the 'PTT Request grant' and ends at the 'PTT Release'. A vertical dashed line connects the start of 'Talker Audio Capture' to the start of 'Audio Playback'. A bracket labeled 'Mouth-to-ear latency (KPI 3)' indicates the time difference between the start of 'Talker Audio Capture' and the start of 'Audio Playback'.
+
+**Figure 7.11.1.1-1: Illustration of MCPTT Access time and Mouth-to-ear latency**
+
+#### 7.11.1.2 Requirements
+
+NOTE: The MCPTT Access time and Mouth-to-ear latency for off-network use is FFS.
+
+### 7.11.2 Late call entry performance
+
+#### 7.11.2.1 General overview
+
+An MCPTT User is able to join or leave an already ongoing MCPTT Group Call. Late call entry is the activity when an Affiliated MCPTT Group Member joins an MCPTT Group Call in which other Affiliated MCPTT Group Members are already active. The Late call entry time (KPI 4) is the time to enter an ongoing MCPTT Group Call measured from the time that the user decides to monitor such an MCPTT Group Call, to the time when the UE's speaker starts to play the audio. The performance requirements for Late call entry time only applies to when there is ongoing voice transmitted at the time the MCPTT User joins the call.
+
+In a Late call entry there might be an initial lost audio of the voice burst sent to the new Receiving MCPTT Group Member.
+
+#### 7.11.2.2 Requirements
+
+NOTE: The Late call entry time (KPI 4) for off-network use is FFS.
+
+### 7.11.3 Audio / Voice quality
+
+[R-7.11.3-001] Void.
+
+## 7.12 Off-network MCPTT operations
+
+[R-7.12-001] Void
+
+[R-7.12-002] Void
+
+[R-7.12-003] Void
+
+## 7.13 Off-network UE functionality
+
+[R-7.13-001] Void
+
+[R-7.13-002] Void
+
+[R-7.13-003] Void
+
+[R-7.13-004] Off-network MCPTT UEs shall support a minimum number of (N8) simultaneous off-network MCPTT calls.
+
+## 7.14 Switching to off-network MCPTT
+
+[R-7.14-001] Void
+
+[R-7.14-002] Void
+
+[R-7.14-003] Void
+
+## 7.15 Off-network recording and audit requirements
+
+[R-7.15-001] Void
+
+[R-7.15-002] Void
+
+## 7.16 Off-network UE-to-UE Relay
+
+### 7.16.1 Private Calls
+
+[R-7.16.1-001] Void
+
+[R-7.16.1-002] Void
+
+[R-7.16.1-003] Void
+
+### 7.16.2 Group Calls
+
+[R-7.16.2-001] Void
+
+[R-7.16.2-002] Void
+
+## Annex A (informative): Variables
+
+**Table A.1: List of variables**
+
+| Variable | Meaning | Value | Reference |
+|--------------------|----------------------------------------------------------------------------------------------------|-----------|--------------------------|
+| B1 | Number of levels of group hierarchy | | 5.2.2 |
+| B2 | Number of levels of user hierarchy | | 5.2.3 |
+| KPI 1 | MCPTT Access time | < 300 ms | 6.15.3.2 |
+| KPI 2 | End-to-end MCPTT Access time | < 1000 ms | 6.15.3.2 |
+| KPI 3 | Mouth-to-ear latency | < 300 ms | 6.15.3.2 |
+| KPI 4 a | Maximum Late call entry time (without application layer encryption) | < 150 ms | 6.15.4.2 |
+| KPI 4 b | Maximum Late call entry time (with application layer encryption) | < 350 ms | 6.15.4.2 |
+| | | | |
+| N1 | Number of receiving members present for an MCPTT Group. | | 6.4.2 |
+| N2 | Total number of MCPTT Groups that an MCPTT User can be affiliated to simultaneously | | 5.1.5 |
+| N3 | Minimum length of alphanumeric identifiers (i.e., Alias ID) | | 5.8, 6.4.3, 7.1, and 7.2 |
+| N4 | Number of simultaneous MCPTT Group calls received by a UE | | 5.5.2 |
+| N5 | Total number of MCPTT Group transmissions that a UE can receive | | 5.5.2 |
+| N6 | Number of simultaneous MCPTT Group calls received by a user | | 5.5.2 |
+| N7 | Total number of MCPTT Group transmissions that a user can receive | | 5.5.2 |
+| N8 | Minimum number of simultaneous off-network MCPTT calls supported by an off-network MCPTT UE. | | 7.13 |
+| N9 | Maximum number of simultaneous audios received by an MCPTT User in a single MCPTT Group | | 6.2.3.1 |
+| N10 | Total number of MCPTT Private Calls (with Floor control) in which a UE simultaneously participates | | 5.5.2 |
+| N11 | Total number of MCPTT Group Members of an MCPTT Group | | 6.1 |
+
+## Annex A1 (Informative): MCPTT Requirements for MCCoRe
+
+This table provides an exhaustive list of those requirements in 3GPP TS 22.179 that have been mapped to MCCoRe.
+
+| 5 MCPTT Service Requirements common for on the network and off the network | |
+|-----------------------------------------------------------------------------------|---------------------------|
+| 5.1 General Group call requirements | |
+| 5.1.1 General Aspects | |
+| R-5.1.1-001 → R-5.1.1-001 | R-5.1.1-002 → R-5.1.1-002 |
+| R-5.1.1-003 → R-5.1.1-003 | R-5.1.1-004 → R-5.1.1-004 |
+| R-5.1.1-005 → R-5.1.1-005 | |
+| 5.1.2 Group/status information | |
+| R-5.1.2-001 → R-5.1.2-001 | R-5.1.2-002 → R-5.1.2-002 |
+| 5.1.3 Group configuration | |
+
+| | |
+|----------------------------------------------------------------|---------------------------|
+| R-5.1.3-001 → R-5.1.3-001 | R-5.1.3-002 → R-5.1.3-002 |
+| 5.1.4 Identification | |
+| R-5.1.4-001 → R-5.1.4-001 | |
+| 5.1.5 Membership/affiliation | |
+| R-5.1.5-001 → R-5.1.5-001 | R-5.1.5-002 → R-5.1.5-002 |
+| R-5.1.5-003 → R-5.1.5-003 | R-5.1.5-004 → R-5.1.5-004 |
+| R-5.1.5-005 → R-5.1.5-005 | R-5.1.5-006 → R-5.1.5-006 |
+| R-5.1.5-007 → R-5.1.5-007 | R-5.1.5-008 → R-5.1.5-008 |
+| 5.1.6 Group Call administration | |
+| R-5.1.6-001 → R-5.1.6-001 | |
+| 5.1.7 Prioritization | |
+| R-5.1.7-001 → R-5.1.7-001 | R-5.1.7-002 → R-5.1.7-002 |
+| 5.1.8 Charging requirements for MCPTT | |
+| R-5.1.8-001 → R-5.1.8-001 | R-5.1.8-002 → R-5.1.8-002 |
+| R-5.1.8-003 → R-5.1.8-003 | R-5.1.8-004 → R-5.1.8-004 |
+| R-5.1.8-005 → R-5.1.8-005 | R-5.1.8-006 → R-5.1.8-006 |
+| R-5.1.8-007 → R-5.1.8-007 | R-5.1.8-008 → R-5.1.8-008 |
+| R-5.1.8-009 → R-5.1.8-009 | R-5.1.8-010 → R-5.1.8-010 |
+| R-5.1.8-011 → R-5.1.8-011 | |
+| 5.2 Broadcast Group | |
+| 5.2.1 General Broadcast Group Communication | |
+| R-5.2.1-001 → R-5.2.1-001 | R-5.2.1-002 → R-5.2.1-002 |
+| 5.2.2 Group-Broadcast Group (e.g., announcement group) | |
+| R-5.2.2-001 → R-5.2.2-001 | R-5.2.2-002 → R-5.2.2-002 |
+| R-5.2.2-003 → R-5.2.2-003 | R-5.2.2-004 → R-5.2.2-004 |
+| 5.2.3 User-Broadcast Group (e.g., System Communication) | |
+| R-5.2.3-001 → R-5.2.3-001 | R-5.2.3-002 → R-5.2.3-002 |
+| 5.3 Late call entry | |
+| R-5.3-001 → R-5.3-001 | R-5.3-002 → R-5.3-002 |
+| R-5.3-003 → R-5.3-003 | R-5.3-004 → R-5.3-004 |
+| R-5.3-005 → R-5.3-005 | |
+| 5.4 Dynamic group management (i.e., dynamic regrouping) | |
+| NA | |
+| 5.5 Receiving from multiple MCPTT calls | |
+| 5.5.1 Overview | |
+| NA | |
+| 5.5.2 Requirements | |
+| R-5.5.2-004 → R-5.4.2-001 | R-5.5.2-005 → R-5.4.2-002 |
+| R-5.5.2-008 → R-5.4.2-003 | R-5.5.2-010 → R-5.4.2-004 |
+| R-5.5.2-011 → R-5.4.2-005 | R-5.5.2-012 → R-5.4.2-006 |
+| R-5.5.2-013 → R-5.4.2-007 | |
+
+| | |
+|--------------------------------------------------------------------------|-----------------------------------|
+| 5.6 Private Call | |
+| NA | |
+| 5.6.1 Private Call Overview | |
+| NA | |
+| 5.6.2 Private Call (with Floor control) general requirements | |
+| NA | |
+| 5.6.3 Private Call (with Floor control) commencement requirements | |
+| NA | |
+| 5.6.4 Private Call (with Floor control) termination | |
+| NA | |
+| 5.6.5 Private Call (with Floor control) administration | |
+| NA | |
+| 5.7 MCPTT priority requirements | |
+| NA | |
+| 5.7.1 Overview | |
+| NA | |
+| 5.7.2 Call types based on priorities | |
+| NA | |
+| 5.7.2.1 MCPTT Emergency Group Call | |
+| NA | |
+| 5.7.2.1.1 MCPTT Emergency Group Call requirements | |
+| R-5.7.2.1.1-002 → R-5.6.2.2.1-002 | R-5.7.2.1.1-003 → R-5.6.2.2.1-003 |
+| R-5.7.2.1.1-004 → R-5.6.2.2.1-004 | R-5.7.2.1.1-005 → R-5.6.2.2.1-005 |
+| R-5.7.2.1.1-006 → R-5.6.2.2.1-006 | R-5.7.2.1.1-007 → R-5.6.2.2.1-007 |
+| R-5.7.2.1.1-008 → R-5.6.2.2.1-008 | R-5.7.2.1.1-009 → R-5.6.2.2.1-009 |
+| R-5.7.2.1.1-010 → R-5.6.2.2.1-010 | R-5.7.2.1.1-011 → R-5.6.2.2.1-011 |
+| R-5.7.2.1.1-012 → R-5.6.2.2.1-012 | R-5.7.2.1.1-013 → R-5.6.2.2.1-013 |
+| R-5.7.2.1.1-014 → R-5.6.2.2.1-014 | R-5.7.2.1.1-001 → R-5.6.2.2.1-001 |
+| 5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements | |
+| R-5.7.2.1.2-001 → R-5.6.2.2.2-001 | R-5.7.2.1.2-002 → R-5.6.2.2.2-002 |
+| R-5.7.2.1.2-003 → R-5.6.2.2.2-003 | R-5.7.2.1.2-004 → R-5.6.2.2.2-004 |
+| R-5.7.2.1.2-005 → R-5.6.2.2.2-005 | |
+| 5.7.2.2 Imminent Peril group call | |
+| NA | |
+| 5.7.2.2.1 Imminent Peril group call requirements | |
+| R-5.7.2.2.1-001 → R-5.6.2.3.1-001 | R-5.7.2.2.1-002 → R-5.6.2.3.1-002 |
+| R-5.7.2.2.1-003 → R-5.6.2.3.1-003 | R-5.7.2.2.1-004 → R-5.6.2.3.1-004 |
+| R-5.7.2.2.1-005 → R-5.6.2.3.1-005 | R-5.7.2.2.1-006 → R-5.6.2.3.1-006 |
+| R-5.7.2.2.1-007 → R-5.6.2.3.1-007 | R-5.7.2.2.1-008 → R-5.6.2.3.1-008 |
+| R-5.7.2.2.1-009 → R-5.6.2.3.1-009 | |
+| 5.7.2.2.2 Imminent Peril group call cancellation requirements | |
+
+| | |
+|----------------------------------------------------------------------------------------------|-----------------------------------|
+| R-5.7.2.2.2-001 → R-5.6.2.3.2-001 | R-5.7.2.2.2-002 → R-5.6.2.3.2-002 |
+| R-5.7.2.2.2-003 → R-5.6.2.3.2-003 | R-5.7.2.2.2-004 → R-5.6.2.3.2-004 |
+| 5.7.2.3 MCPTT Emergency Private Call (with Floor Control) | |
+| NA | |
+| 5.7.2.3.1 MCPTT Emergency Private Call (with Floor Control) requirements | |
+| NA | |
+| 5.7.2.3.2 MCPTT Emergency Private Call (with Floor Control) cancellation requirements | |
+| NA | |
+| 5.7.2.4 MCPTT Emergency Alert | |
+| NA | |
+| 5.7.2.4.1 MCPTT Emergency Alert requirements | |
+| R-5.7.2.4.1-001 → R-5.6.2.4.1-001 | R-5.7.2.4.1-002 → R-5.6.2.4.1-002 |
+| R-5.7.2.4.1-003 → R-5.6.2.4.1-003 | R-5.7.2.4.1-004 → R-5.6.2.4.1-004 |
+| R-5.7.2.4.1-005 → R-5.6.2.4.1-005 | R-5.7.2.4.1-006 → R-5.6.2.4.1-006 |
+| R-5.7.2.4.1-007 → R-5.6.2.4.1-007 | R-5.7.2.4.1-008 → R-5.6.2.4.1-008 |
+| R-5.7.2.4.1-009 → R-5.6.2.4.1-009 | R-5.7.2.4.1-010 → R-5.6.2.4.1-010 |
+| R-5.7.2.4.1-011 → R-5.6.2.4.1-011 | R-5.7.2.4.1-012 → R-5.6.2.4.1-012 |
+| 5.7.2.4.2 MCPTT Emergency Alert cancellation requirements | |
+| R-5.7.2.4.2-001 → R-5.6.2.4.2-001 | R-5.7.2.4.2-002 → R-5.6.2.4.2-002 |
+| R-5.7.2.4.2-003 → R-5.6.2.4.2-003 | |
+| 5.8 User ID | |
+| R-5.8-001 → R-5.7-001 | R-5.8-002 → R-5.7-002 |
+| R-5.8-003 → R-5.7-003 | |
+| 5.9 MCPTT UE Management | |
+| R-5.9-001 → R-5.8-001 | R-5.9-002 → R-5.8-002 |
+| 5.10 MCPTT User Profile | |
+| R-5.10-001 → R-5.9-001 | R-5.10-002 → R-5.9-002 |
+| 5.11 Support for multiple devices | |
+| R-5.11-001 → R-5.10-001 | R-5.11-002 → R-5.10-002 |
+| 5.12 Location | |
+| R-5.12-001 → R-5.11-001, R-5.11-002 | R-5.12-002 → R-5.11-003 |
+| R-5.12-003 → R-5.11-004 | R-5.12-004 → R-5.11-005 |
+| R-5.12-005 → R-5.11-006 | R-5.12-006 → R-5.11-007 |
+| R-5.12-007 → R-5.11-008 | R-5.12-008 → R-5.11-009 |
+| R-5.12-009 → R-5.11-010 | R-5.12-010 → R-5.11-011 |
+| R-5.12-012 → R-5.11-012 | R-5.12-013 → R-5.11-013 |
+| R-5.12-014 → R-5.11-014 | R-5.12-015 → R-5.11-015 |
+| 5.13 Security | |
+| R-5.13-001 → R-5.12-001 | R-5.13-002 → R-5.12-002 |
+| R-5.13-003 → R-5.12-003 | R-5.13-004 → R-5.12-004 |
+| R-5.13-005 → R-5.12-005 | R-5.13-006 → R-5.12-006 |
+
+| | |
+|-------------------------------------------------------------------------------------------------|-----------------------------|
+| R-5.13-007 → R-5.12-007 | R-5.13-008 → R-5.12-008 |
+| R-5.13-009 → R-5.12-009 | R-5.13-010 → R-5.12-010 |
+| R-5.13-011 → R-5.12-011 | R-5.13-012 → R-5.12-012 |
+| R-5.13-013 → R-5.12-013 | |
+| 5.14 Audio/voice quality | |
+| R-5.14-001 → R-5.13-001 | |
+| 5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor Control) | |
+| NA | |
+| 5.16 Relay requirements | |
+| R-5.16-001 → R-5.14-001 | R-5.16-002 → R-5.14-002 |
+| R-5.16-003 → R-5.14-003 | |
+| 5.17 Gateway Requirements | |
+| R-5.17-001 → R-5.15-001 | |
+| 5.18 Control and management by Mission Critical Organizations | |
+| NA | |
+| 5.18.1 Overview | |
+| NA | |
+| 5.18.2 General Requirements | |
+| R-5.18.2-001 → R-5.16.2-001 | R-5.18.2-002 → R-5.16.2-002 |
+| R-5.18.2-003 → R-5.16.2-003 | R-5.18.2-004 → R-5.16.2-004 |
+| R-5.18.2-005 → R-5.16.2-005 | |
+| 5.18.3 Operational visibility for Mission Critical Organizations | |
+| R-5.18.3-001 → R-5.16.3-001 | |
+| 5.19 General Administrative – groups and users | |
+| R-5.19-001 → R-5.17-001 | R-5.19-002 → R-5.17-002 |
+| R-5.19-003 → R-5.17-003 | R-5.19-004 → R-5.17-004 |
+| R-5.19-005 → R-5.17-005 | R-5.19-006 → R-5.17-006 |
+| R-5.19-007 → R-5.17-007 | R-5.19-008 → R-5.17-008 |
+| 6 MCPTT Service requirements specific to on-network use | |
+| NA | |
+| 6.1 General administrative – groups and users | |
+| R-6.1-001 → R-6.1-001 | R-6.1-002 → R-6.1-002 |
+| R-6.1-003 → R-6.1-003 | R-6.1-006 → R-6.1-004 |
+| R-6.1-007 → R-6.1-005 | |
+| 6.2 MCPTT calls | |
+| NA | |
+| 6.2.1 Commencement modes for MCPTT Group calls | |
+| NA | |
+| | |
+| | |
+| 6.2.2 Queuing | |
+
+| | |
+|-----------------------------------------------------------------------------|---------------------------|
+| R-6.2.2-001 → R-6.2.2-001 | R-6.2.2-002 → R-6.2.2-002 |
+| R-6.2.2-003 → R-6.2.2-003 | R-6.2.2-004 → R-6.2.2-004 |
+| R-6.2.2-005 → R-6.2.2-005 | R-6.2.2-006 → R-6.2.2-006 |
+| 6.2.3 Floor control | |
+| NA | |
+| 6.2.3.1 General aspects | |
+| NA | |
+| 6.2.3.2 Requesting permission to transmit | |
+| NA | |
+| 6.2.3.3 Override | |
+| NA | |
+| 6.2.3.3.1 General aspects | |
+| NA | |
+| | |
+| | |
+| | |
+| 6.2.3.3.2 Override – one transmitting Participant | |
+| NA | |
+| 6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members | |
+| NA | |
+| 6.2.3.4 Terminating permission to transmit | |
+| NA | |
+| | |
+| 6.2.3.5 Transmit time limit | |
+| NA | |
+| 6.2.3.6 Audio cut-in designated MCPTT Groups | |
+| NA | |
+| 6.2.3.6.1 Overview | |
+| NA | |
+| 6.2.3.6.2 Requirements | |
+| NA | |
+| 6.2.3.6.3 Requesting permission to transmit | |
+| NA | |
+| 6.2.3.6.4 Terminating permission to transmit | |
+| NA | |
+| 6.2.3.6.5 Transmit time limit | |
+| NA | |
+| 6.2.3.7 MCPTT Groups designated for multi-talker control | |
+| NA | |
+| 6.2.3.7.1 Overview | |
+| NA | |
+
+| | |
+|--------------------------------------------------------------------------------------------------------------|-------------------------------|
+| 6.2.3.7.2 General Aspects | |
+| NA | |
+| 6.2.3.7.3 Requesting permission to transmit | |
+| NA | |
+| 6.2.3.7.3 Requesting permission to transmit | |
+| NA | |
+| 6.2.3.7.4 Override | |
+| NA | |
+| 6.2.3.7.4.1 General Aspects | |
+| NA | |
+| 6.2.4 Call termination | |
+| NA | |
+| | |
+| | |
+| 6.3 General requirements | |
+| R-6.3-001 → R-6.3-001 | R-6.3-002 → R-6.3-002 |
+| R-6.3-003 → R-6.3-003 | R-6.3-004 → R-6.3-004 |
+| 6.4 General group call | |
+| NA | |
+| 6.4.1 General aspects | |
+| R-6.4.1-001 → R-6.4.1-001 | |
+| 6.4.2 Group status/information | |
+| R-6.4.2-001 → R-6.4.2-001 | R-6.4.2-002 → R-6.4.2-002 |
+| R-6.4.2-003 → R-6.4.2-003 | R-6.4.2-004 → R-6.4.2-004 |
+| R-6.4.2-005 → R-6.4.2-005 | R-6.4.2-006 → R-6.4.2-006 |
+| R-6.4.2-007 → R-6.4.2-007 | |
+| 6.4.3 Identification | |
+| R-6.4.3-001 → R-6.4.3-001 | R-6.4.3-002 → R-6.4.3-002 |
+| 6.4.4 Membership/affiliation | |
+| R-6.4.4-001 → R-6.4.4-001 | R-6.4.4-002 → R-6.4.4-002 |
+| 6.4.5 Membership/affiliation list | |
+| R-6.4.5-001 → R-6.4.5-001 | R-6.4.5-002 → R-6.4.5-002 |
+| R-6.4.5-003 → R-6.4.5-003 | R-6.4.5-004 → R-6.4.5-004 |
+| R-6.4.5-005 → R-6.4.5-005 | R-6.4.5-006 → R-6.4.5-006 |
+| R-6.4.5-007 → R-6.4.5-007 | R-6.4.5-008 → R-6.4.5-008 |
+| 6.4.6 Authorized user remotely changes another MCPTT User's affiliated and/or Selected MCPTT Group(s) | |
+| NA | |
+| 6.4.6.1 Mandatory change | |
+| R-6.4.6.1-001 → R-6.4.6.1-001 | R-6.4.6.1-002 → R-6.4.6.1-002 |
+| R-6.4.6.1-003 → R-6.4.6.1-003 | R-6.4.6.1-004 → R-6.4.6.1-004 |
+| 6.4.6.2 Negotiated change | |
+
+| | |
+|---------------------------------------------------------------|-------------------------------|
+| R-6.4.6.2-001 → R-6.4.6.2-001 | R-6.4.6.2-002 → R-6.4.6.2-002 |
+| R-6.4.6.2-003 → R-6.4.6.2-003 | R-6.4.6.2-004 → R-6.4.6.2-004 |
+| R-6.4.6.2-005 → R-6.4.6.2-005 | R-6.4.6.2-006 → R-6.4.6.2-006 |
+| 6.4.7 Prioritization | |
+| R-6.4.7-001 → R-6.4.7-001 | R-6.4.7-002 → R-6.4.7-002 |
+| R-6.4.7-003 → R-6.4.7-003 | R-6.4.7-004 → R-6.4.7-004 |
+| 6.4.8 Relay requirements | |
+| R-6.4.8-001 → R-6.4.8-001 | |
+| 6.4.9 Administrative | |
+| R-6.4.9-001 → R-6.4.9-001 | R-6.4.9-003 → R-6.4.9-002 |
+| R-6.4.9-004 → R-6.4.9-003 | R-6.4.9-007 → R-6.4.9-004 |
+| R-6.4.9-006 → R-6.4.9-005 | R-6.4.9-007 → R-6.4.9-006 |
+| 6.5 Broadcast Group | |
+| NA | |
+| 6.5.1 General Broadcast Group Call | |
+| R-6.5.1-001 → R-6.5.1-001 | R-6.5.1-002 → R-6.5.1-002 |
+| 6.5.2 Group-Broadcast Group (e.g., announcement group) | |
+| R-6.5.2-001 → R-6.5.2-001 | |
+| 6.5.3 User-Broadcast Group (e.g., System Call) | |
+| R-6.5.3-001 → R-6.5.3-001 | |
+| 6.6 Dynamic group management (i.e., dynamic reporting) | |
+| NA | |
+| 6.6.1 General dynamic regrouping | |
+| R-6.6.1-001 → R-6.6.1-001 | R-6.6.1-002 → R-6.6.1-002 |
+| R-6.6.1-003 → R-6.6.1-003 | R-6.6.1-004 → R-6.6.1-004 |
+| R-6.6.1-005 → R-6.6.1-005 | R-6.6.1-006 → R-6.6.1-006 |
+| 6.6.2 Group Regrouping | |
+| NA | |
+| 6.6.2.1 Service Description | |
+| NA | |
+| 6.6.2.2 Requirements | |
+| R-6.6.2.2-001 → R-6.6.2.2-001 | R-6.6.2.2-002 → R-6.6.2.2-002 |
+| R-6.6.2.2-003 → R-6.6.2.2-003 | R-6.6.2.2-004 → R-6.6.2.2-004 |
+| R-6.6.2.2-005 → R-6.6.2.2-005 | R-6.6.2.2-006 → R-6.6.2.2-006 |
+| R-6.6.2.2-007 → R-6.6.2.2-007 | |
+| 6.6.3 Temporary Group-Broadcast Group | |
+| R-6.6.3-001 → R-6.6.3-001 | R-6.6.3-002 → R-6.6.3-002 |
+| 6.6.4 User regrouping | |
+| NA | |
+| 6.6.4.1 Service description | |
+| NA | |
+
+| | |
+|-----------------------------------------------------------------------------|-------------------------------|
+| 6.6.4.2 Requirements | |
+| R-6.6.4.2-001 → R-6.6.4.2-001 | R-6.6.4.2-002 → R-6.6.4.2-002 |
+| R-6.6.4.2-003 → R-6.6.4.2-003 | R-6.6.4.2-004 → R-6.6.4.2-004 |
+| R-6.6.4.2-005 → R-6.6.4.2-005 | |
+| 6.7 Private Call | |
+| NA | |
+| 6.7.0 Overview | |
+| NA | |
+| 6.7.1 General Requirements | |
+| R-6.7.1-002 → R-6.7.2-001 | R-6.7.1-003 → R-6.7.2-002 |
+| R-6.7.1-004 → R-6.7.2-003 | R-6.7.1-011 → R-6.7.2-004 |
+| R-6.7.1-014 → R-6.7.2-005 | |
+| 6.7.2 Administrative | |
+| R-6.7.2-001 → R-6.7.3-001 | R-6.7.2-002 → R-6.7.3-002 |
+| R-6.7.2-003 → R-6.7.3-003 | R-6.7.2-004 → R-6.7.3-004 |
+| R-6.7.2-005 → R-6.7.3-005 | R-6.7.2-006 → R-6.7.3-006 |
+| R-6.7.2-007 → R-6.7.3-007 | R-6.7.2-008 → R-6.7.3-008 |
+| 6.7.3 Prioritization | |
+| R-6.7.3-001 → R-6.7.4-001 | R-6.7.3-002 → R-6.7.4-002 |
+| R-6.7.3-003 → R-6.7.4-003 | R-6.7.3-004 → R-6.7.4-004 |
+| R-6.7.3-005 → R-6.7.4-005 | R-6.7.3-006 → R-6.7.4-006 |
+| R-6.7.3-007 → R-6.7.4-007 | |
+| 6.7.4 Private Call (without Floor control) commencement requirements | |
+| R-6.7.4-004 → R-6.7.5-001 | R-6.7.4-008 → R-6.7.5-002 |
+| R-6.7.4-011 → R-6.7.5-003 | |
+| 6.7.4a Private Call (with Floor control) commencement requirements | |
+| NA | |
+| 6.7.5 Private Call (without Floor control) termination | |
+| R-6.7.5-001 → R-6.7.6-001 | R-6.7.5-003 → R-6.7.6-002 |
+| 6.7.6 Call back request requirements | |
+| NA | |
+| 6.8 MCPTT Priority Requirements | |
+| NA | |
+| 6.8.1 General | |
+| R-6.8.1-001 → R-6.8.1-001 | R-6.8.1-003 → R-6.8.1-002 |
+| R-6.8.1-004 → R-6.8.1-003 | R-6.8.1-005 → R-6.8.1-004 |
+| R-6.8.1-006 → R-6.8.1-005 | R-6.8.1-007 → R-6.8.1-006 |
+| R-6.8.1-008 → R-6.8.1-007 | R-6.8.1-009 → R-6.8.1-008 |
+| R-6.8.1-010 → R-6.8.1-009 | R-6.8.1-011 → R-6.8.1-010 |
+| R-6.8.1-012 → R-6.8.1-011 | R-6.8.1-013 → R-6.8.1-012 |
+| R-6.8.1-014 → R-6.8.1-013 | R-6.8.1-015 → R-6.8.1-014 |
+
+| | |
+|-------------------------------------------------------------------------------|-----------------------------------|
+| R-6.8.1-016 → R-6.8.1-015 | R-6.8.1-017 → R-6.8.1-016 |
+| 6.8.2 3GPP system access controls | |
+| R-6.8.2-001 → R-6.8.2-001 | |
+| 6.8.3 3GPP system admission controls | |
+| R-6.8.3-001 → R-6.8.3-001 | |
+| 6.8.4 3GPP system scheduling controls | |
+| R-6.8.4-001 → R-6.8.4-001 | |
+| 6.8.5 UE access controls | |
+| R-6.8.5-001 → R-6.8.5-001 | |
+| 6.8.6 Application layer priorities | |
+| NA | |
+| 6.8.6.1 Overview | |
+| NA | |
+| 6.8.6.2 Requirements | |
+| R-6.8.6.2-001 → R-6.8.7.2-001 | R-6.8.6.2-002 → R-6.8.7.2-002 |
+| R-6.8.6.2-003 → R-6.8.7.2-003 | R-6.8.6.2-005 → R-6.8.7.2-004 |
+| R-6.8.6.2-006 → R-6.8.7.2-005 | |
+| 6.8.7 Call types based on priorities | |
+| NA | |
+| 6.8.7.1 MCPTT Emergency Group Call requirements | |
+| R-6.8.7.1-001 → R-6.8.8.1-001 | R-6.8.7.1-002 → R-6.8.8.1-002 |
+| R-6.8.7.1-003 → R-6.8.8.1-003 | R-6.8.7.1-004 → R-6.8.8.1-004 |
+| 6.8.7.2 MCPTT Emergency Private Call (with Floor control) requirements | |
+| NA | |
+| 6.8.7.3 Imminent Peril group call requirements | |
+| R-6.8.7.3-001 → R-6.8.8.3-001 | R-6.8.7.3-002 → R-6.8.8.3-002 |
+| R-6.8.7.3-003 → R-6.8.8.3-003 | |
+| 6.8.7.4 MCPTT Emergency Alert | |
+| NA | |
+| 6.8.7.4.1 Requirements | |
+| R-6.8.7.4.1-001 → R-6.8.8.4.1-001 | R-6.8.7.4.1-002 → R-6.8.8.4.1-002 |
+| R-6.8.7.4.1-003 → R-6.8.8.4.1-003 | R-6.8.7.4.1-004 → R-6.8.8.4.1-004 |
+| R-6.8.7.4.1-005 → R-6.8.8.4.1-005 | R-6.8.7.4.1-006 → R-6.8.8.4.1-006 |
+| 6.8.7.4.2 MCPTT Emergency Alert cancellation requirements | |
+| R-6.8.7.4.2-001 → R-6.8.8.4.2-001 | R-6.8.7.4.2-002 → R-6.8.8.4.2-002 |
+| 6.9 IDs and aliases | |
+| R-6.9-001 → R-6.9-001 | R-6.9-002 → R-6.9-002 |
+| R-6.9-003 → R-6.9-003 | R-6.9-004 → R-6.9-004 |
+| 6.10 User Profile Management | |
+| R-6.10-001 → R-6.10-001 | R-6.10-002 → R-6.10-002 |
+| R-6.10-003 → R-6.10-003 | R-6.10-004 → R-6.10-004 |
+
+| | |
+|------------------------------------------------------------------------|-------------------------------------|
+| 6.11 Support for multiple devices | |
+| R-6.11-001 → R-6.11-001 | R-6.11-002 → R-6.11-002 |
+| R-6.11-003 → R-6.11-003 | |
+| 6.12 Location | |
+| R-6.12-001 → R-6.12-001 | R-6.12-002 → R-6.12-002 |
+| R-6.12-003 → R-6.12-003 | R-6.12-004 → R-6.12-004 |
+| R-6.12-005 → R-6.12-005 | R-6.12-006 → R-6.12-006 |
+| R-6.12-007 → R-6.12-007 | |
+| 6.13 Security | |
+| NA | |
+| 6.13.1 Overview | |
+| NA | |
+| 6.13.2 Cryptographic protocols | |
+| R-6.13.2-001 → R-6.13.2-001 | R-6.13.2-002 → R-6.13.2-002 |
+| R-6.13.2-003 → R-6.13.2-003 | |
+| 6.13.3 Authentication | |
+| R-6.13.3-001 → R-6.13.3-001 | |
+| 6.13.4 Access control | |
+| R-6.13.4-001 → R-6.13.4-001 | R-6.13.4-002 → R-6.13.4-002 |
+| R-6.13.4-003 → R-6.13.4-003 | R-6.13.4-004 → R-6.13.4-004 |
+| R-6.13.4-005 → R-6.13.4-005 | R-6.13.4-006 → R-6.13.4-006 |
+| R-6.13.4-007 → R-6.13.4-007 | R-6.13.4-008 → R-6.13.4-008 |
+| R-6.13.4-009 → R-6.13.4-009 | R-6.13.4-010 → R-6.13.4-010 |
+| 6.13.5 Regulatory Issues | |
+| R-6.13.5-001 → R-6.13.5-001 | |
+| 6.14 Interactions for MCPTT Group Calls and MCPTT Private Calls | |
+| R-6.14-001 → R-6.14-001 | R-6.14-002 → R-6.14-002 |
+| 6.15 Audio MCPTT call performance | |
+| NA | |
+| 6.16 Additional services for MCPTT calls | |
+| NA | |
+| 6.16.1 Discreet listening capabilities | |
+| R-6.16.1-001 → R-6.15.1-001 | |
+| 6.16.2 Ambient listening | |
+| NA | |
+| 6.16.2.1 Overview of ambient listening | |
+| NA | |
+| 6.16.2.2 Ambient listening requirements | |
+| NA | |
+| 6.16.2.2.1 General Ambient Listening Requirements | |
+| R-6.16.2.2.1-001 → R-6.15.2.2.1-001 | R-6.16.2.2.1-002 → R-6.15.2.2.1-002 |
+
+| | |
+|---------------------------------------------------------------------|-------------------------------------|
+| R-6.16.2.2.1-003 → R-6.15.2.2.1-003 | |
+| 6.16.2.2.2 Remotely initiated ambient listening requirements | |
+| R-6.16.2.2.2-001 → R-6.15.2.2.2-001 | R-6.16.2.2.2-002 → R-6.15.2.2.2-002 |
+| 6.16.2.2.3 Locally initiated ambient listening requirements | |
+| R-6.16.2.2.3-001 → R-6.15.2.2.3-001 | R-6.16.2.2.3-002 → R-6.15.2.2.3-002 |
+| 6.16.3 Remotely initiated MCPTT call | |
+| NA | |
+| 6.16.3.1 Overview | |
+| NA | |
+| 6.16.3.2 Requirements | |
+| R-6.16.3.2-003 → R-6.15.3.2-003 | R-6.16.3.2-004 → R-6.15.3.2-004 |
+| R-6.16.3.2-002 → R-6.15.3.2-002 | R-6.16.3.2-001 → R-6.15.3.2-001 |
+| 6.16.4 Recording and audit requirements | |
+| R-6.16.4-001 → R-6.15.4-001 | R-6.16.4-002 → R-6.15.4-002 |
+| R-6.16.4-005 → R-6.15.4-005 | R-6.16.4-006 → R-6.15.4-006 |
+| R-6.16.4-007 → R-6.15.4-007 | R-6.16.4-008 → R-6.15.4-008 |
+| R-6.16.4-009 → R-6.15.4-009 | R-6.16.4-010 → R-6.15.4-010 |
+| R-6.16.4-003 → R-6.15.4-003 | R-6.16.4-004 → R-6.15.4-004 |
+| 6.17 Interaction with telephony services | |
+| R-6.17-001 → R-6.16-001 | R-6.17-003 → R-6.16-002 |
+| 6.18 Interworking | |
+| NA | |
+| 6.18.1 Non-3GPP access | |
+| R-6.18.1-001 → R-6.17.1-001 | |
+| 6.18.2 Interworking between MCCore systems | |
+| R-6.18.2-001 R-6.17.2-001→ | R-6.18.2-002 R-6.17.2-002→ |
+| R-6.18.2-003 R-6.17.2-003→ | R-6.18.2-004 R-6.17.2-004→ |
+| R-6.18.2-005 R-6.17.2-005→ | R-6.18.2-006 R-6.17.2-006→ |
+| R-6.18.2-007 R-6.17.2-007→ | |
+| 6.18.3 Interworking with non-3GPP PTT systems | |
+| NA | |
+| 6.18.3.1 Overview | |
+| NA | |
+| 6.18.3.2 Project 25 | |
+| NA | |
+| 6.18.3.3 TETRA | |
+| NA | |
+| 6.18.3.4 Legacy land mobile radio | |
+| NA | |
+| 6.18.4 GSM-R | |
+| NA | |
+
+| | |
+|-----------------------------------------------------------------------|---------------------------|
+| 6.18.4.1 Overview | |
+| NA | |
+| 6.18.4.2 Requirements | |
+| NA | |
+| 6.19 MCPTT coverage extension using ProSe UE-to-Network Relays | |
+| R-6.19-001 → R-6.18-001 | R-6.19-002 → R-6.18-002 |
+| R-6.19-003 → R-6.18-003 | R-6.19-004 → R-6.18-004 |
+| R-6.19-005 → R-6.18-005 | R-6.19-006 → R-6.18-006 |
+| 7 MCPTT Service Requirements specific to off-network use | |
+| NA | |
+| 7.1 Off-network Push To Talk overview | |
+| NA | |
+| 7.2 General off-network MCPTT requirements | |
+| R-7.2-001 → R-7.2-001 | R-7.2-002 → R-7.2-002 |
+| R-7.2-003 → R-7.2-003 | R-7.2-004 → R-7.2-004 |
+| R-7.2-005 → R-7.2-005 | |
+| 7.3 Floor control | |
+| NA | |
+| 7.3.1 General Aspects | |
+| NA | |
+| 7.3.2 Requesting permission to transmit | |
+| NA | |
+| 7.3.3 Override | |
+| NA | |
+| 7.3.4 Terminating permission to transmit | |
+| NA | |
+| 7.3.5 Transmit time limit | |
+| NA | |
+| 7.4 Call Termination | |
+| R-7.4-003 → R-7.4-001 | R-7.4-004 → R-7.4-002 |
+| R-7.4-005 → R-7.4-003 | R-7.4-006 → R-7.4-004 |
+| 7.5 Broadcast Group | |
+| R-7.5-001 → R-7.5-001 | R-7.5-002 → R-7.5-002 |
+| 7.6 Dynamic group management (i.e., dynamic regrouping) | |
+| NA | |
+| 7.7 MCPTT priority requirements | |
+| R-7.7-001 → R-7.6-001 | R-7.7-003 → R-7.6-002 |
+| 7.8 Call types based on priorities | |
+| NA | |
+| 7.8.1 MCPTT Emergency Group Call requirements | |
+| R-7.8.1-001 → R-7.7.1-001 | R-7.8.1-002 → R-7.7.1-002 |
+
+| | |
+|--------------------------------------------------------------------|-------------------------------|
+| R-7.8.1-003 → R-7.7.1-003 | |
+| 7.8.2 MCPTT Emergency Group Call cancellation requirements | |
+| R-7.8.2-001 → R-7.7.2-001 | |
+| 7.8.3 Imminent Peril Call | |
+| NA | |
+| 7.8.3.1 Imminent Peril group call requirements | |
+| R-7.8.3.1-001 → R-7.7.3.1-001 | R-7.8.3.1-002 → R-7.7.3.1-002 |
+| R-7.8.3.1-003 → R-7.7.3.1-003 | R-7.8.3.1-004 → R-7.7.3.1-004 |
+| R-7.8.3.1-005 → R-7.7.3.1-005 | |
+| 7.8.3.2 Imminent Peril group call cancellation requirements | |
+| R-7.8.3.2-001 → R-7.7.3.2-001 | R-7.8.3.2-002 → R-7.7.3.2-002 |
+| 7.9 Location | |
+| R-7.9-001 → R-7.8-001 | |
+| 7.10 Security | |
+| R-7.10-001 → R-7.9-001 | R-7.10-002 → R-7.9-002 |
+| 7.11 Audio MCPTT Call performance | |
+| NA | |
+| 7.11.1 MCPTT Access time and Mouth-to-ear latency | |
+| NA | |
+| 7.11.1.1 General overview | |
+| NA | |
+| 7.11.1.2 Requirements | |
+| NA | |
+| 7.11.2 Late call entry performance | |
+| NA | |
+| 7.11.2.1 General overview | |
+| NA | |
+| 7.11.2.2 Requirements | |
+| NA | |
+| 7.11.3 Audio/voice quality | |
+| NA | |
+| 7.12 Off-network MCPTT operations | |
+| R-7.12-001 → R-7.10-001 | R-7.12-002 → R-7.10-002 |
+| R-7.12-003 → R-7.10-003 | |
+| 7.13 Off-network UE functionality | |
+| R-7.13-001 → R-7.11-001 | R-7.13-002 → R-7.11-002 |
+| R-7.13-003 → R-7.11-003 | |
+| 7.14 Switching to off-network MCPTT | |
+| R-7.14-001 → R-7.13-001 | R-7.14-002 → R-7.13-002 |
+| R-7.14-003 → R-7.13-003 | |
+| 7.15 Off-network recording and audit requirements | |
+
+| | |
+|----------------------------------------|-----------------------------|
+| R-7.15-001 → R-7.14-001 | R-7.15-002 → R-7.14-002 |
+| 7.16 Off-network UE-to-UE relay | |
+| NA | |
+| 7.16.1 Private Communications | |
+| R-7.16.1-001 → R-7.15.1-001 | R-7.16.1-002 → R-7.15.1-002 |
+| R-7.16.1-003 → R-7.15.1-003 | |
+| 7.16.2 Group Communications | |
+| R-7.16.2-001 → R-7.15.2-001 | R-7.16.2-002 → R-7.15.2-002 |
+
+---
+
+## Annex B (informative): Bibliography
+
+- 3GPP TS 22.115: "Service aspects; Charging and billing".
+
+---
+
+## Annex C (informative): MCPTT scalability guide
+
+The MCPTT Service might support an authorized MCPTT UE to be an MCPTT member of at least 5,000 MCPTT Groups.
+
+The MCPTT Service might support a minimum of 500,000 MCPTT Groups.
+
+The MCPTT Service might support MCPTT Group membership from two MCPTT Users to all the MCPTT Users signed on the MCPTT system.
+
+The MCPTT Service might support an MCPTT Group Call where all the Participants are located in one cell of the MCPTT system.
+
+The MCPTT Service might support an MCPTT Group Call with one or more Participants located in every cell of the MCPTT system.
+
+The MCPTT Service might support a range of 36 to 150 simultaneous MCPTT Group Calls in every cell of the MCPTT system per regional regulatory requirement.
+
+The MCPTT Service might support a minimum of 2000 MCPTT Users within an MCPTT Group or a combination of different MCPTT Groups, in every cell of the MCPTT system.
+
+NOTE: The concurrent number of Participants in a cell is subject to radio capacity limitation in a cell per operator policy.
+
+## Annex D (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|----|-----|--------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-66 | SP-140844 | | | | | | | Raised by MCC to version 13.0.0 following SA's approval | 2.1.0 | 13.0.0 | |
+| SP-66 | - | - | | | | | | Correction of Figure 4.6.1-1 (previously corrupted) and of some typos, including: consistent use of capital and spaces instead of hyphens in "Push To Talk", removal of the requirement numbering for the three paragraph of sections 6.6.2.1 and 6.6.4.1 since they are not requirements | 13.0.0 | 13.0.1 | |
+| SP-67 | SP-150040 | S1-150011 | 22.179 | 1 | - | Rel-13 | F | Replacement of Home and Visited by Primary and Partner | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150225 | 22.179 | 2 | 1 | Rel-13 | F | Completion of application of S1-144278 | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150226 | 22.179 | 3 | 1 | Rel-13 | F | Clarification of number and types of Private Calls | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150228 | 22.179 | 5 | 1 | Rel-13 | F | Completion of application of S1-144570 | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150016 | 22.179 | 6 | - | Rel-13 | F | Improper use of 'emergency' | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150230 | 22.179 | 7 | 2 | Rel-13 | D | Correct use of MCPTT terminology | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150229 | 22.179 | 8 | 1 | Rel-13 | F | Clarifying KPI requirement | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150019 | 22.179 | 9 | - | Rel-13 | D | Wording correction | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150021 | 22.179 | 11 | - | Rel-13 | F | Change the title of TS 22.179 to align with MCPTT WID and agreed contribution S1-144232 | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150022 | 22.179 | 12 | - | Rel-13 | D | Changing Ues to UEs | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150023 | 22.179 | 13 | - | Rel-13 | D | Editorial clean ups | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150342 | 22.179 | 14 | 2 | Rel-13 | F | Correction of type of Private Calls supported in for both on and off the network use. | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150025 | 22.179 | 15 | - | Rel-13 | F | Clarification of dedicated MCPTT Group type used for Imminent Peril Group call communication by MCPTT User | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150026 | 22.179 | 16 | - | Rel-13 | F | Replacement of personality management with user profile management | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150027 | 22.179 | 17 | - | Rel-13 | F | Modify text in first sentence of third paragraph for clause 7.1 Off-Network Push-to-Talk overview. | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150028 | 22.179 | 18 | - | Rel-13 | F | Replacement of clause 5.14 title Audio/ video quality with Audio/ voice quality. | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150232 | 22.179 | 19 | 1 | Rel-13 | F | Convert 2nd sentence of 5th requirement in clause 6.2.4 Call Termination into a new requirement | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150309 | 22.179 | 20 | 2 | Rel-13 | F | Move two requirements from clause 6.1 General Administrative -groups and users into common clause 5.19 General Administrative -groups and users. | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150234 | 22.179 | 21 | 1 | Rel-13 | B | Charging for MCPTT usage | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150092 | 22.179 | 22 | - | Rel-13 | F | Reinstatement of MCPTT User Profile | 13.0.1 | 13.1.0 | MCPTT-SA1 |
+| SP-67 | SP-150040 | S1-150093 | 22.179 | 23 | - | Rel-13 | F | Fix improper multiple requirements | 13.0.1 | 13.1.0 | MCPTT-SA1 |
+| SP-67 | SP-150040 | S1-150094 | 22.179 | 24 | - | Rel-13 | F | Remove implementation-specific requirement for default value | 13.0.1 | 13.1.0 | MCPTT-SA1 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|-----------------------------------------------------------------------------------------------------------------------------------|--------|--------|-------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-67 | SP-150040 | S1-150236 | 22.179 | 26 | 1 | Rel-13 | F | CR- to clarify requirements in 6.4.9 and 6.2.4. | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150265 | 22.179 | 28 | 1 | Rel-13 | F | CR to clarify what call type refers to in 6.2.3.3.1 | 13.0.1 | 13.1.0 | MCPTT |
+| SP-67 | SP-150040 | S1-150107 | 22.179 | 30 | - | Rel-13 | D | Separation of supplementary service, callback, requirements | 13.0.1 | 13.1.0 | MCPTT |
+| SP-68 | SP-150354 | - | 22.179 | 31 | 1 | Rel-13 | F | Clarification on the update and use of codecs in MCPTT | 13.1.0 | 13.2.0 | MCPTT |
+| SP-68 | SP-150355 | - | 22.179 | 32 | 1 | Rel-13 | F | Clarification on Broadcast Groups Off-Network Requirement R-7.5-002 | 13.1.0 | 13.2.0 | MCPTT |
+| SP-70 | SP-150750 | S1-154482 | 22.179 | 0033 | 1 | Rel-13 | F | Edits, formatting, and style corrections | 13.2.0 | 13.3.0 | MCPTT |
+| SP-70 | SP-150750 | S1-154483 | 22.179 | 0034 | 1 | Rel-13 | F | MCPTT Emergency Group Call correction | 13.2.0 | 13.3.0 | MCPTT |
+| SP-70 | SP-150750 | S1-154546 | 22.179 | 0035 | 1 | Rel-13 | F | KPI 4 when MBMS is used | 13.2.0 | 13.3.0 | MCPTT |
+| SP-71 | SP-160103 | S1-160313 | 22.179 | 0036 | 1 | Rel-14 | C | Mission Critical Push to Talk over LTE Realignment (MCPTT-R) | 13.3.0 | 14.0.0 | MCImp-MCPTR |
+| SP-72 | SP-160359 | S1-161580 | 22.179 | 38 | 3 | Rel-14 | B | Inclusion of "first-to-answer" commencement mode for private calls | 14.0.0 | 14.1.0 | MCPTT |
+| SP-72 | SP-160391 | - | 22.179 | 40 | | Rel-14 | B | Introduction of Audio cut-in requirements in MCPTT | 14.0.0 | 14.1.0 | MCImp-MCPTR |
+| SP-72 | SP-160359 | S1-161626 | 22.179 | 37 | 2 | Rel-14 | C | Mission Critical Push to Talk over LTE for Realignment (MCPTT-R) | 14.0.0 | 14.1.0 | MCPTT |
+| SP-73 | SP-160542 | S1-162402 | 22.179 | 0043 | 1 | Rel-14 | F | Remove definitions for participant and participant type in MCPTT TS 22.179 that are being added to MCCoRe TS 22.280. | 14.1.0 | 14.2.0 | MCImp-MCPTR |
+| SP-73 | SP-160542 | S1-162404 | 22.179 | 0044 | 1 | Rel-14 | D | In MCPTT TS 22.179 Provide editorial changes to sub-clause 6.6.2.2. | 14.1.0 | 14.2.0 | MCImp-MCPTR |
+| SP-73 | SP-160542 | S1-162405 | 22.179 | 0045 | 1 | Rel-14 | F | Remove definition for Mission Critical Organization in MCPTT TS 22.179 that was added to MCCoRe TS 22.280 as a common definition. | 14.1.0 | 14.2.0 | MCImp-MCPTR |
+| SP-73 | SP-160542 | S1-162400 | 22.179 | 0046 | 1 | Rel-14 | F | Clarifications and corrections to audio cut-in | 14.1.0 | 14.2.0 | MCImp-MCPTR |
+| SP-74 | SP-160890 | S1-163011 | 22.179 | 0047 | | Rel-14 | D | Editorial change to MCPTT TS 22.179 sub-clause 6.2.3.6.2 | 14.2.0 | 14.3.0 | MCImp-MCPTR |
+| SP-74 | SP-160890 | S1-163012 | 22.179 | 0048 | | Rel-14 | D | Editorial changes to Annex A1 sub-clause 6.2.3.6 | 14.2.0 | 14.3.0 | MCImp-MCPTR |
+| SP-76 | SP-170445 | S1-172430 | 22.179 | 0052 | 6 | Rel-15 | B | multi-talker group call | 14.3.0 | 15.0.0 | MONASTERY |
+| SP-77 | SP-170696 | S1-173507 | 22.179 | 0054 | 2 | Rel-15 | F | Clarify MCPTT group in 6.2.3.7 | 15.0.0 | 15.1.0 | MONASTERY |
+| SP-77 | SP-170696 | S1-173506 | 22.179 | 0055 | 3 | Rel-15 | F | Correction on behavior of groups configured for multi talker control wrt groups using public safety floor control | 15.0.0 | 15.1.0 | MONASTERY |
+| SP-78 | SP-170985 | S1-174039 | 22.179 | 0057 | | Rel-15 | F | Removing 'over LTE' from the title of the specification | 15.1.0 | 15.2.0 | MCOVer |
+| SP-78 | SP-170985 | S1-174541 | 22.179 | 0058 | 1 | Rel-15 | F | Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards | 15.1.0 | 15.2.0 | MCOVer |
+| SP-78 | SP-170997 | S1-174424 | 22.179 | 0061 | 3 | Rel-16 | B | Addition of requirement on interworking with SCP in GSM-R | 15.2.0 | 16.0.0 | MONASTERY2 |
+| SP-79 | SP-180134 | S1-180433 | 22.179 | 0062 | 1 | Rel-16 | B | Adding more functionality to interworking between FRMCS and GSM-R | 16.0.0 | 16.1.0 | MONASTERY2 |
+| SP-80 | SP-180310 | S1-181707 | 22.179 | 0064 | 4 | Rel-16 | F | Interworking between MCX Service system and GSM-R | 16.1.0 | 16.2.0 | MONASTERY2 |
+| SP-80 | SP-180310 | S1-181708 | 22.179 | 0063 | 2 | Rel-16 | B | Adding functionality to 22.179 to support assured voice communication | 16.1.0 | 16.2.0 | MONASTERY2 |
+| SP-81 | SP-180757 | S1-182565 | 22.179 | 0066 | 1 | Rel-16 | B | Enhancement for interworking of group communication between | 16.2.0 | 16.3.0 | MONASTERY2 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|----------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| | | | | | | | | FRMCS and GSM-R | | | |
+| SP-81 | SP-180761 | S1-182613 | 22.179 | 0065 | 1 | Rel-16 | B | Application of MCPTT to maritime usage | 16.2.0 | 16.3.0 | MARCOM |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-12 | SP-82 | SP-181000 | 0067 | 1 | C | Addition of new Group Call Commencement Modes | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0068 | 1 | B | Move interworking of functional alias from MCPTT to MCCoRe TS, MCPTT part | 16.4.0 |
+| 2019-03 | SA#83 | SP-190084 | 0069 | | B | Add forwarding for private calls | 16.5.0 |
+| 2019-12 | SA#86 | SP-191036 | 0073 | 1 | C | Group and Private call setup KPIs | 17.0.0 |
+| 2022-03 | SP#95e | SP-220081 | 0075 | 1 | F | Clarification on use of MCPTT Late call entry KPIs | 17.1.0 |
+| 2023-06 | SA#100 | - | | | | CR 0076r2 in SP-230529 creates Rel-19 from Rel-17. Version 18.0.0 is a technical-content duplicate of v.17.1.0. created for administrative reasons. | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22182/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22182/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c91c79e0eb9c9a8b7d92a5f0d74b766337c712d
--- /dev/null
+++ b/marked/Rel-18/22_series/22182/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2b51f30903077f1187e9d0b3bf1366ebdece54e52172d15f5f8c7aa5ee7eb6a
+size 8213
diff --git a/marked/Rel-18/22_series/22182/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22182/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a230726fd9e7018245cf60c10b90f593675afa72
--- /dev/null
+++ b/marked/Rel-18/22_series/22182/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c2c5c623bea570b269badb02aa1ce28642469dd5808261b7629f16da6120a81
+size 6861
diff --git a/marked/Rel-18/22_series/22182/raw.md b/marked/Rel-18/22_series/22182/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5469b6a1eda1751819e2a75b52a2578c837dcade
--- /dev/null
+++ b/marked/Rel-18/22_series/22182/raw.md
@@ -0,0 +1,465 @@
+
+
+# 3GPP TS 22.182 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Customized Alerting Tones (CAT) Requirements; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+GSM, UMTS, LTE, Alerting, tone
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|----------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 CAT Service Requirements ..... | 6 |
+| 4.1 Basic functionality of the CAT service..... | 6 |
+| 4.1.1 CAT functionality in IMS domain ..... | 7 |
+| 4.1.2 CAT functionality in the CS domain..... | 7 |
+| 4.2 Normal procedures with successful outcome..... | 8 |
+| 4.2.1 Provisioning and Withdrawal ..... | 8 |
+| 4.2.2 Activation and Deactivation and Update..... | 8 |
+| 4.2.2.1 Activation..... | 8 |
+| 4.2.2.2 Deactivation ..... | 8 |
+| 4.2.3 Basic scenarios ..... | 8 |
+| 4.2.3.0 CAT to be supported in the CS domain..... | 8 |
+| 4.2.3.1 Only called party has activated the CAT service..... | 8 |
+| 4.2.3.2 Only calling party has activated the CAT service ..... | 9 |
+| 4.2.3.3 Both parties have activated the CAT service..... | 9 |
+| 4.2.4 Interaction with Supplementary Services..... | 10 |
+| 4.2.4.1 Originating Identification Restriction (OIR) ..... | 10 |
+| 4.2.4.2 Terminating Identification Restriction (TIR) ..... | 10 |
+| 4.2.4.3 Communication Diversion (CDIV) ..... | 10 |
+| 4.2.4.4 Communication Waiting (CW)..... | 11 |
+| 4.2.4.5 Explicit Communication Transfer (ECT) ..... | 11 |
+| 4.3 CAT service configuration ..... | 12 |
+| 4.4 The content of CAT..... | 12 |
+| 4.5 Inter-working CAT..... | 12 |
+| 4.5.1 CAT Interworking between different PLMNs..... | 12 |
+| 4.5.2 Interworking between CS and IMS based CAT services ..... | 12 |
+| 5 CAT Service Interoperability..... | 13 |
+| Annex A (informative): Change history..... | 14 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies the requirements and technical considerations for Customized Alerting Tone (CAT) service in both CS and PS domains, especially additional features for roaming and interoperability support.
+
+This document considers voice and multi-media CAT, so the CAT user may experience favourable songs, multi-media clips or other customized alerting tones.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
+- [3] 3GPP TS 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
+
+# --- 3 Definitions, symbols 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].
+
+**Alerting Tone:** An indication that is played to the calling party during establishment of a call or during an established call session indicating one of the following:
+
+- that the called subscriber is being alerted.
+- the progress of communication request (Call Forward, Call Wait etc.)
+- any alerting event during a call session
+
+**Customized Alerting Tone:** An Alerting Tone that is customized by the called subscriber or the calling subscriber, and it can contain additional media types.
+
+**Customized Alerting Tone Service:** A Customized Alerting Tone Service (CAT service) is an operator specific service by which an operator enables the subscriber to customize his alerting tone.
+
+**CAT Inter-action:** is the interaction of the CAT service with other services, e.g. CAT Inter-action with Call Forwarding.
+
+**CAT Inter-working :** Multiple Domains Inter-working is the interworking of a CAT service over different domains or subsystems (CS or IMS) as well as between PLMNs.
+
+**CAT content provider:** A service provider that provides a set of Alerting Tones for use as CAT for subscribers of the CAT service. A 3GPP operator may be a CAT content provider.
+
+## 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].
+
+| | |
+|-----|--------------------------|
+| CAT | Customized Alerting Tone |
+|-----|--------------------------|
+
+# --- 4 CAT Service Requirements
+
+## 4.1 Basic functionality of the CAT service
+
+The Customized Alerting Tone Service (CAT service) is an operator specific service by which an operator enables the subscriber to customize the alerting tone which is played to the calling party. The calling party does not need to be a CAT subscriber to experience the CAT set by called subscriber. CAT service should not negatively affect the conversation between calling and called parties, e.g. no voice/video clipping, no longer communication setup time.
+
+- The service shall support the CAT content types of audio, video, image, graphic, text, location and electronic business card.
+- CAT can contain one or several content types, and at most one element of each type.
+- The calling party should be able to simultaneously experience multiple CAT contents, e.g. audio and video.
+- The service user shall be able to subscribe the CAT service, activate the CAT service, update the settings, e.g. to change his active CAT.
+- The calling party shall be able to experience the CAT set by the called CAT service subscriber.
+- The CAT shall override the default alerting tone towards the calling party.
+- The operator should have the capability to store multiple CATs per CAT service subscriber.
+- The CAT subscriber should be able to configure the CAT service. The CAT service should be able to select the appropriate CAT according to the rules. The CAT subscriber profile is based on the following parameters:
+ 1. CAT content descriptor - Pointing to the right content or combination of contents (e.g. personal prompt plus chosen music track).
+ 2. CAT timing descriptor - Time of day, day of week, specific date and intervals based on each of those parameters.
+ 3. User (called/calling party) descriptor - user ID (or group ID of users), user presence, user location, CAT user charging mode
+
+Note 1: As location information may be restricted in some instances, the default user location may be a generic "unknown".
+
+Note 2: Presence information for a CS user is limited to attached or detached
+
+- The CAT service shall be able to select the appropriate CAT according to the CAT user profile.
+- The operator shall be able to verify that the party is authorised to store and update CAT content.
+- The operator shall be able to set limitations on file type, file size, etc. for storing the CAT content.
+- It should be possible to inform the user about status and changes in his CAT service, e.g. close expiry date for the CAT service or a particular CAT content.
+
+Note: In the CS domain, this information may be provided by existing means such as SMS and web access.
+
+- The operator shall be able to charge for the CAT service on event, volume or media type basis.
+- The called party shall be able to pre-configure the CAT service. The preconfigured service is played upon receipt of an incoming communication notification. This may be based upon the calling party identity.
+- The calling party should be able to reject the CAT service based on rules e.g. time, the identity of the called party.
+- It shall be possible for a CAT subscriber to subscribe to a CAT that is provided by a third party content provider.
+
+### 4.1.1 CAT functionality in IMS domain
+
+The functions identified here are specific to communications made between users within the IMS.
+
+- The calling party shall be able to experience the CAT set by the calling CAT service subscriber, both when the calling party is within HPLMN and when roaming.
+- The calling party's operator shall be able to configure which CAT should have priority, the one set by the called or calling CAT service subscriber. The calling party's operator shall be able to take into account the calling CAT service subscriber's preferences. By default, if no preference is set, the CAT set by the calling party has priority.
+- When the called party answers the communication the CAT shall stop or continue to play during the conversation, depending on operator or user preferences.
+- When the called party is notified about an incoming communication, the called party shall be able to send an indication to the CAT service which CAT to play to the calling party. This CAT-B indication shall have priority over a pre-configured CAT-B.
+- When the CAT is playing, the calling party shall be able to stop it, subject to service provider policy, and then he shall experience the default alerting tone for the duration of the communication establishment.
+
+Note 1: The default alerting tone may be a CAT selected by the operator in the event of e.g. CAT STOP.
+
+- The calling user shall have the possibility to copy the CAT of the called user as his own while the CAT is being played. The pre-requisites are that the called user has enabled CAT sharing, if applicable, for that instance of CAT and that both users are subscribers to the same HPLMN.
+
+Note 2: A CAT might also be copied offline via e.g. web interface but that functionality does not require standardisation.
+
+Note 3: The expression "to copy the CAT" does not necessarily mean that the CAT is actually copied. It may also mean that a purchase request is being sent to the CAT service provider.
+
+### 4.1.2 CAT functionality in the CS domain
+
+The functions identified here are specific to communications made between users within the CS domain.
+
+- The calling party shall be able to experience the CAT set by the calling CAT service subscriber when in the HPLMN. When roaming this function may not be available.
+- The calling party's operator shall be able to configure which CAT should have priority, the one set by the called or calling CAT service subscriber. By default, if no preference is set, the CAT set by the calling party has priority.
+- When the called party answers the communication the CAT shall stop.
+- When the CAT is playing, the calling party shall be able to stop it, subject to service provider policy, and then he shall experience the default alerting tone for the duration of the communication establishment. The pre-requisites are that both called and calling user are subscribers to the same HPLMN and the calling user is within the HPLMN.
+
+Note 1: The default alerting tone may be a CAT selected by the operator in the event of e.g. CAT STOP.
+
+- The calling user shall have the possibility to copy the CAT of the called user as his own while the CAT is being played. The pre-requisites are that the called user has enabled CAT sharing, if applicable, for that instance of CAT and that both users are subscribers to the same HPLMN and the calling user is within the HPLMN.
+
+Note 2: A CAT might also be copied offline via e.g. web interface but that functionality does not require standardisation.
+
+Note 3: The expression "to copy the CAT" does not necessarily mean that the CAT is actually copied. It may also mean that a purchase request is being sent to the CAT service provider.
+
+- The calling party UE shall be able to start automatically downloading and streaming CAT content through PS domain during the call setup. Downloaded CAT content shall not be used for other purposes except CAT service.
+
+## 4.2 Normal procedures with successful outcome
+
+### 4.2.1 Provisioning and Withdrawal
+
+The CAT Service can be provisioned and withdrawn by the operator per subscriber. Procedures for provisioning and withdrawal are out of scope of standardisation.
+
+### 4.2.2 Activation and Deactivation and Update
+
+#### 4.2.2.1 Activation
+
+When a subscriber activates his CAT Service he shall be able to specify which CAT a calling user should experience, or use the operator's default setting.
+
+After a subscriber has activated his CAT Service a calling user should experience the CAT that was chosen by the subscriber.
+
+#### 4.2.2.2 Deactivation
+
+After a subscriber has deactivated his CAT Service a calling user should experience the default alerting tone.
+
+### 4.2.3 Basic scenarios
+
+#### 4.2.3.0 CAT to be supported in the CS domain
+
+Alerting the called subscriber constitute the basic CAT service requirements, while other CATs may be considered optional
+
+The following table summarize these cases:
+
+**Table 0: Normal Operation Scenarios**
+
+| Scenarios | CAT Support |
+|---------------------------------------------------------------------------------|-------------|
+| The called subscriber is being alerted | Mandatory |
+| The progress of communication request (Call Forward, Call Wait, User busy etc.) | Mandatory |
+| Others | Optional |
+
+#### 4.2.3.1 Only called party has activated the CAT service
+
+In the following scenarios, contained in table 1, it is assumed that the called party (B) has activated his CAT Service. Calling party (A) is calling B. The calling party has not subscribed and/or activated the CAT service.
+
+The Customized Alerting Tone of B is CAT-B.
+
+**Table 1: Normal Operation Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|---------------------------------------|-------------------------------------------------------------------------------------------------------|
+| 1 | B, ringing | A experiences CAT-B |
+| 2 | B, busy | A experiences busy indication. |
+| 3 | B, no answer | First A experiences CAT-B and then the 'no answer' indication after B's 'no answer' timer has expired |
+| 4 | B, not reachable | A experiences 'not reachable' indication |
+
+#### 4.2.3.2 Only calling party has activated the CAT service
+
+In the following scenarios, contained in table 2, it is assumed that only the calling party (A) has activated his CAT Service. Calling party (A) is calling B. The called party has not subscribed and/or activated the CAT service.
+
+The Customized Alerting Tone of A is CAT-A,
+
+**Table 2: Normal Operation Scenarios**
+
+| | Called party
B
(condition) | Required behaviour |
+|---|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B, ringing | Depending on A settings, subscriber A will experience either CAT-A or the default alerting tone. |
+| 2 | B, busy | Depending on A settings, subscriber A will experience either CAT-A or the default busy tone. |
+| 3 | B, no answer | Depending on A settings, subscriber A will experience either CAT-A or the default alerting tone and then the 'no answer' indication after B's 'no answer' timer has expired |
+| 4 | B, not reachable | A experiences 'not reachable' indication |
+
+#### 4.2.3.3 Both parties have activated the CAT service
+
+In the following scenarios, contained in table 3, it is assumed that both the calling party (A) and called party (B) have activated the CAT Service. Calling party (A) is calling B.
+
+The Customized Alerting Tone of B is CAT-B, the Customized Alerting Tone for A is CAT-A.
+
+**Table 3: Normal Operation Scenarios**
+
+| | Called party
B
(condition) | Required behaviour |
+|---|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B, ringing | Depending on A settings, A experiences CAT-A, CAT-B or the default alerting tone. |
+| 2 | B, busy | Depending on A settings, subscriber A will experience either CAT-A or the default busy tone. |
+| 3 | B, no answer | Depending on A settings, subscriber A will experience either CAT-A, CAT-B or the default alerting tone and then the 'no answer' indication after B's 'no answer' timer has expired |
+| 4 | B, not reachable | A experiences 'not reachable' indication |
+
+### 4.2.4 Interaction with Supplementary Services
+
+The following section describes the interaction between CAT and the IMS Multimedia Telephony supplementary services defined in [22.173] and the equivalent CS supplementary services.
+
+#### 4.2.4.1 Originating Identification Restriction (OIR)
+
+The OIR service takes precedence over the CAT service subscribed by the calling party or by the called party. If the called party has a CAT associated to the calling party's identity, the service will not be invoked. If the called party has a CAT not associated to the calling party's identity then the service is invoked.
+
+NOTE: OIR service itself is independent from CAT service. The service logic providing CAT will handle the privacy request of the originator's identity for invoking OIR service and decide whether to invoke CAT service.
+
+#### 4.2.4.2 Terminating Identification Restriction (TIR)
+
+The TIR service takes precedence over the CAT service subscribed by the calling party or by the called party. If the calling party has a CAT associated to the called party's identity, the service will not be invoked. If the calling party has a CAT not associated to the calling party's identity then the service is invoked. The CAT service can take precedence over the TIR service when the calling party has an override category, such as the police, for which the TIR service is not applied.
+
+#### 4.2.4.3 Communication Diversion (CDIV)
+
+Additionally, for call-forwarding scenarios, it is assumed that Forwarded-to-party (C) has activated his CAT Service. The Customized Alerting Tone of C is called CAT-C. The Customized Alerting Tone of D is called CAT-D. The calling party has not subscribed and/or activated the CAT service. If applicable, the CAT experienced by the calling user should be the one customized for the user by the connected-to-party
+
+In the following table, all the CATs that A experiences in the column "Required behaviour" may be replaced by CAT-B, if the operator wants to deploy so.
+
+**Table 4: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Forwarded-to-party
(condition) | Required behaviour |
+|---|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| 1 | B has activated Call Forwarding Unconditional (CFU) to C and A's call is forwarded to C | C, ringing | A experiences CAT-C |
+| 2 | B has activated Call Forwarding on Busy (CFB) to C, B is busy and A's call is forwarded to C | C, ringing | A experiences CAT-C |
+| 3 | B has activated Call Forwarding on No Reply (CFNRy) to C and A's call is forwarded to C | C, ringing | A experiences CAT-B until B's CFNRy timer has expired. Then experiences CAT-C. |
+| 4 | B has activated Call Forwarding on Not Reachable (CFNRc) to C and A's call is forwarded to C | C, ringing | A experiences CAT-C |
+| 5 | B has activated a Call Forwarding to C and C has activated a Call Forwarding to D so A's call is forwarded to D | Tandem Forwarding: C has activated a Call Forwarding to D and A's call is forwarded to D | A experiences CAT-D |
+
+Table 5 describes when the calling party has subscribed and activated the CAT service.
+
+**Table 5: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Forwarded-to-party
(condition) | Required behaviour |
+|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
+| 1 | A has activated CAT-A and B has activated Call Forwarding Unconditional (CFU), Call Forwarding on Busy (CFB) or Call Forwarding on Not Reachable (CFNRc) to C.
A's call is forwarded to C | C, ringing | Depending on operator settings, subscriber A will experience the CAT set for user B, C or the default ringing tone. |
+| 2 | B has activated Call Forwarding on No Reply (CFNRy) to C and A's call is forwarded to C | C, ringing | A experiences CAT-A for user B until B's CFNRy timer has expired. Then experiences CAT-A for user C. |
+
+- It should be possible to configure the CAT service so that different CATs are used according to user profile (e.g. Date, Time, Call status)
+
+#### 4.2.4.4 Communication Waiting (CW)
+
+If the called party has activated the communication waiting and he is busy, depending on the operator's settings, the calling party will experience either the CAT service or the default communication waiting indication.
+
+**Table 6: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Forwarded-to-party
(condition) | Required behaviour |
+|---|--------------------------------------------------------------------------------------------------|-------------------------------------------|------------------------------------------------------------------------------------------------------|
+| 1 | A has activated CAT and B has activated call waiting. B is engaged in an active or held call. | | Depending on A settings, subscriber A will experience either CAT-A or the default call waiting tone. |
+| 2 | B has activated CAT and B has activated call waiting and B is engaged in an active or held call. | | Depending on A settings, subscriber A will experience either CAT-B or the default call waiting tone. |
+
+#### 4.2.4.5 Explicit Communication Transfer (ECT)
+
+The called party (A) has activated the ECT service and the communication is transferred to C. The calling party will only experience the CAT from the C in case of blind transfer and if C has activated the CAT service. In case of consultative transfer the calling party will not experience the CAT service.
+
+## 4.3 CAT service configuration
+
+- A service subscriber, that has activated his CAT service, shall be able to select and update his CAT settings - e.g. select a different CAT than the current one. It should be possible to charge the subscriber for selection / update of the CAT settings.
+- The calling user should be able to 'copy' the last CAT that was experienced in the ongoing call, as his own CAT.
+
+Note: Operators should be aware that copyrights may be infringed and therefore the operator may need to take appropriate action.
+
+## 4.4 The content of CAT
+
+The content of CAT can be music, voice, text, or video.
+
+In IMS the CAT may be composed of music, voice, text, video, which can be provided by the CAT content provider, operator or by the user himself.
+
+If the calling party is in the CS domain the CAT may be composed of music, voice, video, which can be provided by the CAT content provider, operator or by the user himself.
+
+The content of the CAT service may be dynamically created, possibly taking into account information available in the network, e.g. calling and/or called user's location and/or presence information.
+
+## 4.5 Inter-working CAT
+
+### 4.5.1 CAT Interworking between different PLMNs
+
+It is important for a good user experience that CAT works as predicted independently if the called or the calling user is roaming. A standardized CAT solution should therefore fulfil the following end user requirements:
+
+- When calling a user of another PLMN, the calling party shall be able to experience the CAT set by the called party.
+- When calling a user of another PLMN, the calling party shall be able to experience the CAT set by the calling party.
+- When roaming to another PLMN, the calling party shall be able to experience the CAT set by the called party.
+- The calling party shall be able to experience the CAT set by the called party who is roaming to another PLMN.
+
+### 4.5.2 Interworking between CS and IMS based CAT services
+
+The CS and IMS based CAT services should fulfil the following end user requirements:
+
+- When calling a user in the other domain (CS or IMS), the calling party shall be able to experience the CAT set by the called party.
+- When calling a user in the other domain (CS or IMS), the calling party shall be able to experience the CAT set by the calling party.
+- When calling a CAT service subscriber of another domain (CS or IMS), the calling party should be able to copy the CAT of the called user as his own CAT. The pre-requisites are that the called user has enabled CAT sharing, if applicable, for that instance of CAT and that both users are subscribers to the same HPLMN.
+- When calling a CAT service subscriber of another domain (CS or IMS), the calling party should be able to stop an ongoing CAT.
+
+The scope of this interoperability may result in a limited service capability.
+
+# 5 CAT Service Interoperability
+
+## 5.1 Interaction with Charging
+
+The operator shall be able to charge for the CAT service according to the different charging mode (see the table below):
+
+| Index | Charging mode | Example |
+|-------|------------------------|-------------------------------------------------------------------------------------------|
+| 1 | Service monthly fee | Fixed (for example monthly) expense for the CAT service. |
+| 2 | Fee of purchasing CAT | A subscriber is charged by the system when he purchases CAT, including copying CAT. |
+| 3 | Fee of configuring CAT | A subscriber may be charged by the system when he set his CAT or updates his CAT setting. |
+| 4 | Fee per CAT usage | Advertising CAT.
High/low quality CAT |
+
+## 5.2 Interaction with User Profile
+
+- It shall be possible to store a User Profile relevant to CAT.
+- It shall be possible to access/manage CAT User Profile by a user/subscriber and/or CAT service provider.
+- It shall be possible to manage access rights for
+ - User Profile components
+ - Media content
+
+## 5.3 CAT Fall back
+
+It shall be possible that if the CAT can't be played for some reason (for example, the CAT system fails, or the CAT content expiry is up, or other reasons), the calling party will experience the traditional prompt tone instead of the CAT,
+
+When the multi-media CAT fails to be played in some condition (such as the caller roams from 3G network to 2G network), the voice CAT may be played instead if possible.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|-------------------------------------------------------------|--------|--------|-----------|
+| Change history | | | | | | | | | | | |
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-38 | SP-070842 | S1-071674 | 22.182 | 0010 | 1 | Rel-8 | C | Removal of unworkable requirements | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071675 | 22.182 | 0006 | 1 | Rel-8 | C | Called party CAT selection | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071676 | 22.182 | 0008 | 1 | Rel-8 | C | CAT Rules | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071677 | 22.182 | 0009 | 1 | Rel-8 | C | Copy CAT | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071678 | 22.182 | 0011 | 1 | Rel-8 | C | CAT Calling | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071679 | 22.182 | 0012 | 1 | Rel-8 | C | CAT to CAT | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071804 | 22.182 | 0003 | 1 | Rel-8 | C | Clarification on CS CAT Provisioning | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070842 | S1-071805 | 22.182 | 0013 | 1 | Rel-8 | F | Update the CAT Interaction definition | 8.0.0 | 8.1.0 | CAT |
+| SP-38 | SP-070843 | S1-071846 | 22.182 | 0004 | 2 | Rel-8 | B | TISPAN text for CTMIF filtering services | 8.0.0 | 8.1.0 | TISCMI-R8 |
+| SP-39 | SP-080029 | S1-080271 | 22.182 | 0014 | 1 | Rel-8 | C | Clarification of CS and IMS based CAT | 8.1.0 | 8.2.0 | CAT |
+| SP-39 | SP-080029 | S1-080161 | 22.182 | 0015 | 1 | Rel-8 | B | Addition of a list of CAT to be supported in the CS domain | 8.1.0 | 8.2.0 | CAT |
+| SP-41 | SP-080497 | S1-082188 | 22.182 | 0016 | 1 | Rel-9 | B | Multimedia CAT content download | 8.2.0 | 9.0.0 | TEI9 |
+| SP-42 | SP-080767 | S1-083437 | 22.182 | 0019 | 1 | Rel-9 | A | Removal of DRM note from CAT | 9.0.0 | 9.1.0 | CAT |
+| SP-44 | SP-090368 | S1-091404 | 22.182 | 0022 | - | Rel-9 | A | Clarification on the interaction with CAT and OIR | 9.1.0 | 9.2.0 | CAT |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.2.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| SP-65 | SP-140512 | S1-143561 | 22.182 | 0023 | 3 | Rel-13 | C | Enhanced call information presentation to the calling party | 11.0.0 | 13.0.0 | ECIP |
+| SP-75 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22183/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22183/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f4053654fc08a3ea4d0367878d35d8776cd80e0
--- /dev/null
+++ b/marked/Rel-18/22_series/22183/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5de43dd928ab631172bacbc021b1b07cae8c06cb426245159cc83b783ae1aff1
+size 8171
diff --git a/marked/Rel-18/22_series/22183/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22183/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a00eddda2af83179c1d96c055e62547c3635da6e
--- /dev/null
+++ b/marked/Rel-18/22_series/22183/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:920984dd8f2b7ebf510544188e27d45f13658afb26283ccf0f8fc030e6ad6a19
+size 6388
diff --git a/marked/Rel-18/22_series/22183/raw.md b/marked/Rel-18/22_series/22183/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..55d11f098cdc977ac9b3f7351a3c757107bd443c
--- /dev/null
+++ b/marked/Rel-18/22_series/22183/raw.md
@@ -0,0 +1,440 @@
+
+
+# 3GPP TS 22.183 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Customized Ringing Signal (CRS) Requirements; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+Ringing signal, UMTS, LTE
+
+### **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|---------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 CRS Service Requirements..... | 6 |
+| 4.1 Basic functionality of CRS service ..... | 6 |
+| 4.1.1 Functionality - IMS domain ..... | 7 |
+| 4.1.2 Functionality - CS domain..... | 7 |
+| 4.2 Normal procedures with successful outcome..... | 8 |
+| 4.2.1 Provisioning and Withdrawal ..... | 8 |
+| 4.2.2 Activation and Deactivation and Update..... | 8 |
+| 4.2.2.1 Activation..... | 8 |
+| 4.2.2.2 Deactivation ..... | 8 |
+| 4.2.2.3 Update ..... | 8 |
+| 4.2.3 Basic scenarios ..... | 8 |
+| 4.2.3.1 Only calling party has activated the CRS service..... | 8 |
+| 4.2.3.2 Only called party has activated the CRS service ..... | 8 |
+| 4.2.3.3 Both parties have activated the CRS service ..... | 9 |
+| 4.2.4 Interaction with Supplementary Services..... | 9 |
+| 4.2.4.2 Originating Identification Restriction (OIR) ..... | 9 |
+| 4.2.4.3 Communication Diversion (CDIV) ..... | 9 |
+| 4.2.4.4 Communication Waiting (CW)..... | 10 |
+| 4.2.4.5 Explicit Communication Transfer (ECT) ..... | 11 |
+| 4.3 CRS service configuration ..... | 12 |
+| 4.4 The content of CRS ..... | 12 |
+| 4.5 Inter-working CRS ..... | 12 |
+| 4.5.1 Inter-working between PLMNs ..... | 12 |
+| 4.5.2 Inter-working between CS and IMS ..... | 13 |
+| Annex A (informative): Change history..... | 14 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The document specifies the requirements and technical considerations for Customized Ringing Signal (CRS) service in the PS and CS domains, especially additional features for roaming and interoperability support.
+
+This document considers voice and multi-media CRS, so the CRS user may experience favourable songs, multi-media clips or other customized CRS.
+
+This document specifies the CRS filtering service requirements that allow the user to filter the CRS.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
+- [3] 3GPP TS 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
+- [4] ETSI TISPAN TR 181 015: "Requirements for Customized Originating and Terminating Multimedia Information Presentation (COMIP/CTMIP) and Customized Originating and Terminating Multimedia Information Filtering (COMIF/CTMIF) Requirements Analysis".
+
+# --- 3 Definitions, symbols 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].
+
+**Ringing Signal:** A Ringing Signal is played to the called party as an incoming communication indication during establishment of a communication. It is provided by the UE of the called party.
+
+**Customized Ringing Signal:** A Ringing Signal that is customized by the calling party or the called party, and it can contain additional media types. It is provided by the network.
+
+**CRS inter-action:** CRS inter-action is the interaction of the CRS service with other services, e.g. inter-action with Call Forwarding.
+
+**CRS inter-working :** CRS inter-working is the interworking of a CRS service over different domains or subsystems (CS or IMS) as well as between PLMNs.
+
+**CRS content provider:** A service provider that provides a set of Ring Signals for use as CRS for subscribers of the CRS service. A 3GPP operator may be a CRS content provider.
+
+## 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].
+
+| | |
+|-----|---------------------------|
+| CRS | Customized Ringing Signal |
+|-----|---------------------------|
+
+# --- 4 CRS Service Requirements
+
+## 4.1 Basic functionality of CRS service
+
+The Customized Ringing Signal service (CRS service) is an operator specific service by which an operator enables the subscriber to customize the ringing signal which is played to the called party. The CRS content will be provided to the called party only if it's allowed by the called party. The called party does not need to be a CRS subscriber to experience the CRS set by calling subscriber.
+
+- The service shall support the CRS content types of audio, video, image, graphic, text, location, and electronic business card.
+- CRS can contain one or several content types, and at most one element of each type.
+- The called party should be able to simultaneously experience multiple CRS contents, e.g. audio and video.
+- The service user shall be able to subscribe to the services, activate the services, update the settings, e.g. to change his active CRS.
+- The CRS service shall override the default ringing signal towards the called party provided that media components are compatible.
+- The called party shall be able to experience the CRS set by the called service subscriber.
+- The called party shall be able to experience the CRS set by the calling service subscriber.
+- The operator should have the capability to store multiple CRSs per service subscriber.
+- It should be possible to inform the user about status and changes in his service, e.g. service expiry date or a particular CRS content.
+
+Note: In the CS domain, this information may be provided by existing means such as SMS and web access.
+
+- The operator shall be able to charge for the CRS service and the related contents on event, volume or media type basis.
+- It shall be possible for a subscriber to subscribe to CRS that is provided by a third party content provider.
+- CRS service should not negatively affect the conversation between calling and called parties, e.g. no voice /video clipping.
+- If the CRS can't be played for some reason (for example, the CRS system fails, or the CRS content expiry is up, or the called user roams from 3G network to 2G network, or other reasons), the called party shall experience the default ringing signal instead of the CRS.
+- When the multi-media CRS fails to be played in some condition (such as the caller roams from 3G network to 2G network or network congestion occurs), the voice CRS may be played instead if possible.
+- The operator shall be able to verify that the party is authorised to store and update CRS content.
+- The operator shall allow the calling party to select from the pre-stored CRS content according to the called party on a per call basis.
+
+- As service option, if a specific text (object of the communication) is provided by the calling party, this information should replace any potential text information pre-stored in the network.
+
+### 4.1.1 Functionality - IMS domain
+
+The CRS services in IMS domain are defined by:
+
+- For the CRS service, the called party's operator shall be able to configure which CRS should have priority, the one set by the called or calling CRS service subscriber. The called party's operator shall be able to take into account the called CRS service subscriber's preferences. By default, if no preference is set, the CRS set by the called party has priority.
+- When the called party answers the communication the CRS shall stop or continue to play during the conversation, depending on operator or user preferences. By default, if no preference is set, when the called party answers the communication the CRS shall stop.
+- When the calling party is setting up a communication, the calling party shall be able to send an indication to the CRS service which CRS to play to the called party.
+- The called party shall have the capability to copy the CRS of the calling party as his own CRS while the CRS is being played. The pre-requisites are that the calling party has enabled CRS sharing, if applicable, for that instance of CRS and that both parties are subscribers to the same HPLMN.
+
+Note 1: A CRS might also be copied offline via e.g. web interface but that functionality does not require standardisation.
+
+Note 2: The expression "to copy the CRS" does not necessarily mean that the CRS is actually copied. It may also mean that a purchase request is being sent to the CRS service provider.
+
+- The CRS service shall be able to send CRS to the called party on per call basis.
+- The CRS service shall send an indication to the multimedia information presentation service which multimedia information to play to the called party (e.g. when the called party is notified about an incoming communication, the CRS subscriber can send an indication to the CRS service which CRS to play to the called party).
+- The CRS subscriber may be able to replace one CRS with another one while it is playing.
+- The CRS subscriber may be able to receive CRS service after communication establishment.
+
+### 4.1.2 Functionality - CS domain
+
+The CRS services in CS domain are defined by:
+
+- For the CRS service, the called party's operator shall be able to configure which CRS should have priority, the one set by the called or calling CRS service subscriber. By default, if no preference is set, the CRS set by the called party has priority.
+- When the called party answers the communication the CRS shall stop.
+- The called party shall have the capability to copy the CRS of the calling party as his own CRS. The pre-requisites are that the calling user has enabled CRS sharing, if applicable, for that instance of CRS and that both parties are subscribers to the same HPLMN and the called party is within the HPLMN.
+
+Note 1: A CRS might also be copied offline via e.g. web interface but that functionality does not require standardisation.
+
+Note 2: The expression "to copy the CRS" does not necessarily mean that the CRS is actually copied. It may also mean that a purchase request is being sent to the CRS service provider.
+
+- During the call setup over the CS domain, the called party UE shall be able to start automatically downloading and streaming CRS content through PS domain. Downloaded CRS content shall not be used for other purposes except CRS service.
+
+## 4.2 Normal procedures with successful outcome
+
+### 4.2.1 Provisioning and Withdrawal
+
+The CRS Service can be provisioned and withdrawn by the operator on a per subscriber basis.
+
+If the CRS service is not provisioned, the called party shall not experience content of CRS, he should experience the default ringing signal.
+
+Note: Procedures for provisioning and withdrawal are out of scope of standardisation.
+
+### 4.2.2 Activation and Deactivation and Update
+
+#### 4.2.2.1 Activation
+
+When a subscriber activates his CRS Service he shall be able to specify which CRS a called user should experience, or use the operator's default setting.
+
+After a subscriber has activated his CRS Service a called user should experience the CRS that was chosen by the subscriber.
+
+#### 4.2.2.2 Deactivation
+
+After a subscriber has deactivated his CRS Service a called user shall experience the default ringing signal.
+
+#### 4.2.2.3 Update
+
+When a subscriber updates his CRS Service, updated CRS should overwrite the existing one.
+
+### 4.2.3 Basic scenarios
+
+#### 4.2.3.1 Only calling party has activated the CRS service
+
+In the following scenarios, contained in table 1, it is assumed that only the calling party (A) has activated his CRS Service. Calling party (A) is calling B. The called party has subscribed and not activated the CRS service.
+
+Note: To activate his CRS means the user has chosen that his CRS should be experienced.
+
+The CRS of A is CRS-A.
+
+**Table 1: Normal Operation Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|-------------------------------|----------------------------------------------------------------------------------------|
+| 1 | B, ringing | Depending on B settings, B will experience either CRS-A or the default ringing signal. |
+
+#### 4.2.3.2 Only called party has activated the CRS service
+
+In the following scenario, contained in table 2, it is assumed that only the called party (B) has activated his CRS Service. Calling party (A) is calling B. The calling party has not subscribed and/or activated the CRS service.
+
+The CRS of B is CRS-B.
+
+**Table 2: Normal Operation Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|---------------------------------------|----------------------------------------------------|
+| 1 | B, ringing | B experiences CRS-B or the default ringing signal. |
+
+#### 4.2.3.3 Both parties have activated the CRS service
+
+In the following scenarios, contained in table 3, it is assumed that both the calling party (A) and called party (B) have activated the CRS Service. Calling party (A) is calling B.
+
+The CRS of B is CRS-B, the CRS for A is CRS-A.
+
+**Table 3: Normal Operation Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B, ringing | Depending on B settings, B experiences CRS-A, CRS-B or the default ringing signal.
If B has not set preference, B experiences CRS-B. |
+
+### 4.2.4 Interaction with Supplementary Services
+
+#### 4.2.4.1 Originating Identification Presentation (OIP)
+
+No impact. The OIP service is performed independently of the CRS, the CRS will use the information provided by OIP.
+
+The CRS service shall be able to distinguish information provided via service platform and information provided by the network (e.g. public identity sends by the OIP service).
+
+#### 4.2.4.2 Originating Identification Restriction (OIR)
+
+The OIR service takes precedence over the CRS service subscribed by the calling party or by the called party.
+
+#### 4.2.4.3 Communication Diversion (CDIV)
+
+Table 4 describes when the forwarded-to party (C) has not subscribed or activated the CRS service.
+
+**Table 4: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Forwarded-to-
party
(condition) | Required behaviour |
+|---|----------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------------------------------------------|
+| 1 | B has activated Call Forwarding Unconditional (CFU) to C and A's call is forwarded to C | C, ringing | C experiences CRS-A or CRS-B or the default ringing signal. |
+| 2 | B has activated Call Forwarding on Busy (CFB) to C, B is busy and A's call is forwarded to C | C, ringing | C experiences CRS-A or CRS-B or the default ringing signal. |
+| 3 | B has activated Call Forwarding on No Reply (CFNRy) to C and A's call is forwarded to C | C, ringing | C experiences CRS-A or CRS-B or the default ringing signal. |
+| 4 | B has activated Call Forwarding on Not Reachable (CFNRc) to C and A's call is forwarded to C | C, ringing | C experiences CRS-A or CRS-B or the default ringing signal. |
+
+Table 5 describes when the forwarded-to-party (C) has subscribed and activated the CRS service.
+
+The CRS of C is CRS-C.
+
+**Table 5: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Forwarded-to-party
(condition) | Required behaviour |
+|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Call Forwarding Unconditional (CFU), Call Forwarding on Busy (CFB) or Call Forwarding on Not Reachable (CFNRc) to C. A's call is forwarded to C | C, ringing | Depending on operator settings, subscriber C will experience the CRS-C or CRS-A or CRS-B or the default ringing signal. |
+| 2 | B has activated Call Forwarding on No Reply (CFNRy) to C and A's call is forwarded to C | C, ringing | B experiences the standard ringing signal until B's CFNRy timer has expired. Then C experiences CRS-C or CRS-A or CRS-B or the default ringing signal. |
+
+Note: in addition to playing the applicable CRS, related operator settings allow (see [4], 7.1.1):
+
+- Case 1: when CRS-B is played to C, CDIV may also be set to present B's number to the forwarded-to user.
+- Case 2: when CRS-B is played to C, CDIV may also be set to NOT present B's number to the forwarded-to user.
+- Case 3: CRS-A may be provided to C when B's operator has chosen not to send CRS-B.
+
+#### 4.2.4.4 Communication Waiting (CW)
+
+If the called party B has activated the communication waiting service and he is busy, depending on the operator's settings, the called party will experience either the CRS service or the default communication waiting indication.
+
+If B experiences the CRS service, B shall receive appropriate media in order to limit perturbation on the ongoing communication with C (e.g. CRS audio information may be replaced by the default communication waiting tone).
+
+Table 6 describes the situation that only the calling party A has subscribed and activated the CRS service.
+
+**Table 6: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Communication Waiting, | Depending on operator settings or user preference, B experiences the communication waiting indication or CRS-A whose audio information is replaced by the communication waiting indication. |
+
+Table 7 describes the situation that only the called party B has subscribed and activated the CRS service.
+
+**Table 7: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated Communication Waiting, | Depending on operator settings or user preference, B experiences the communication waiting indication or CRS-B whose audio information is replaced by the communication waiting indication. |
+
+Table 8 describes the situation that both the calling party A and called party B have subscribed and activated the CRS service.
+
+**Table 8: Supplementary Service Interaction Scenarios**
+
+| | Called party B
(condition) | Required behaviour |
+|---|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1 | B has activated
Communication Waiting, | Depending on operator settings or user preference, B experiences the communication waiting indication or CRS-A/CRS-B whose audio information is replaced by the communication waiting indication. |
+
+#### 4.2.4.5 Explicit Communication Transfer (ECT)
+
+In case of immediate transfer the called party C shall either experience the CRS from CRS-A or CRS-C depending on operator settings and if A or C has activated the CRS service.
+
+In case of consultative transfer, when A is on hold and B has invoked the ECT service between A and C, C shall either experience the CRS from CRS-B or CRS-C depending on operator settings and if B or C has activated the CRS service. When the communication is established between A and C, C shall either experience the CRS from CRS-A or CRS-C depending on operator settings and if A or C has activated the CRS service.
+
+## 4.3 CRS service configuration
+
+The CRS subscriber should be able to configure the service with a service profile based on the following parameters:
+
+1. CRS content descriptor – Pointing to the right content or combination of contents (e.g. personal prompt plus chosen music/video track)
+2. CRS timing descriptor – Time of day, day of week, specific date and intervals based on each of those parameters.
+3. User (called/calling party) descriptor – user ID (or group ID of users), user presence, user location, CRS user charging mode
+
+Note 1: As location information may be restricted in some instances, the default user location may be set to “unknown”
+
+Note 2: Presence information for a CS user is limited to attached or detached.
+
+The CRS service shall be able to select the appropriate CRS according to the CRS user profile.
+
+A CRS subscriber who has activated his service, shall be able to select and update his settings - e.g. select a different CRS than the current one. It should be possible to charge the subscriber for selection / update of the CRS settings.
+
+A storage mechanism for a user Profile relevant to CRS and/or CRS filtering should be supported.
+
+A user/subscriber and/or CRS service provider should be able to access/manage CRS and/or a CRS filtering User Profile.
+
+A means of managing Access rights for User Profile components and media content should be supported.
+
+The network should provide the capability for the called/forwarded party to reject CRS provided by the calling party according to some rules:
+
+- reject all CRS, unconditionally.
+- reject CRS for unknown parties and accept all known parties,
+- reject CRS for parties identified as with malicious information in a black list and accept all others,
+- prompt the user to accept/reject CRS only for unknown parties and accept CRS all others (default)
+- For IMS CRS, it should be possible to prompt the user to accept or reject CRS for each incoming call (e.g. to present CRS or not).
+
+## 4.4 The content of CRS
+
+The content of CRS can be CRS such as music, voice, text, or video.
+
+The CRS may be composed of music, voice, text, video, which can be provided by the CRS content provider, operator or by the user himself.
+
+The content of the CRS service may be dynamically created, possibly taking into account information available in the network, e.g. calling and/or called user's location and/or presence information.
+
+The dynamic content of CRS service may be stored in the network in order to be experienced again by the called party. This may be requested by the called party, calling party, or service provider. The content may be downloaded to the UE or streamed down to the UE when the CRS is playing.
+
+## 4.5 Inter-working CRS
+
+### 4.5.1 Inter-working between PLMNs
+
+. The CRS service should therefore fulfil the following end user requirements:
+
+- When receiving a communication from another PLMN, the called party shall be able to experience the CRS set by the calling party.
+- When receiving a communication from another PLMN, the called party shall be able to experience the CRS set by the called party.
+- When roaming to another PLMN, the called party shall be able to experience the CRS set by the called party.
+- When roaming to another PLMN, the called party shall be able to experience the CRS set by the calling party.
+- The called party shall be able to experience the CRS set by the calling party who is roaming to another PLMN.
+
+### 4.5.2 Inter-working between CS and IMS
+
+The CS and IMS based CRS services should fulfil the following end user requirements:
+
+- When receiving a communication from another domain (CS or IMS), the called party shall be able to experience the CRS set by the calling party.
+- When receiving a communication from another domain (CS or IMS), the called party shall be able to experience the CRS set by the called party.
+- When receiving a communication from another domain (CS or IMS), the called party should be able to copy the CRS of the calling user as his own CRS. The pre-requisites are that the calling user has enabled CRS sharing, if applicable, for that instance of CRS and that both users are subscribers to the same HPLMN.
+
+The scope of this interoperability may result in a limited service capability.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|------------------------------------------------------------|--------|--------|------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-42 | SP-080789 | S1-084326 | 22.183 | - | - | Rel-9 | - | Approved at SA#42 | 2.0.0 | 9.0.0 | CRS |
+| SP-46 | SP-090838 | S1-094332 | 22.183 | 0001 | 1 | Rel-9 | F | CRS media components compatibility | 9.0.0 | 9.1.0 | CRS |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| SP-65 | SP-140512 | S1-143562 | 22.183 | 0002 | 3 | Rel-13 | C | Enhanced call information presentation to the called party | 11.0.0 | 13.0.0 | ECIP |
+| SP-75 | - | - | - | - | - | Rel-14 | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22185/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-18/22_series/22185/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c9bb6a4a335a08ade8f20f44e2072f0c0862444
--- /dev/null
+++ b/marked/Rel-18/22_series/22185/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9de2030a9bb2fa2cdf5dd64fec8d04d698dc75b7998d87eec89b40aadd9fdf6c
+size 32713
diff --git a/marked/Rel-18/22_series/22185/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22185/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e6719be2c06aef4dc6f0379d36ddcecffe93e9c
--- /dev/null
+++ b/marked/Rel-18/22_series/22185/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1b981fd030a7306865065990fcd78b53b6336ad5bf45c279abec50d910e5cd9
+size 9392
diff --git a/marked/Rel-18/22_series/22185/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22185/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac1e939ff23453d7b73dc095f0938e8df273a3f0
--- /dev/null
+++ b/marked/Rel-18/22_series/22185/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa5331bdcf37991269ad2817637b6995e650a5a96e5f24daf942a10b2bdc82b2
+size 7266
diff --git a/marked/Rel-18/22_series/22185/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Rel-18/22_series/22185/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c04c0be8a87e5749fbc05ddb8a59862337842e6
--- /dev/null
+++ b/marked/Rel-18/22_series/22185/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4a93a5fbd8f73d94bf8d8dcb55ddefe8cc8378e67a1c1a5960d65c1e6766359
+size 25722
diff --git a/marked/Rel-18/22_series/22185/raw.md b/marked/Rel-18/22_series/22185/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..05f53c22ca65afb263fa5eeff84bf702a8800aff
--- /dev/null
+++ b/marked/Rel-18/22_series/22185/raw.md
@@ -0,0 +1,376 @@
+
+
+# 3GPP TS 22.185 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for V2X services; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+Vehicle
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- ***Copyright Notification***
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|----------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 5 |
+| 4 Overview on V2X (informative)..... | 6 |
+| 4.1 Types of V2X application support in 3GPP..... | 6 |
+| 4.1.1 General ..... | 6 |
+| 4.1.2 Vehicle-to-Vehicle (V2V) application ..... | 6 |
+| 4.1.3 Vehicle-to-Infrastructure (V2I) application..... | 7 |
+| 4.1.4 Vehicle-to-Network (V2N) application..... | 7 |
+| 4.1.5 Vehicle-to-Pedestrian (V2P) application..... | 7 |
+| 4.2 Relative priority of V2X communication..... | 8 |
+| 5 Requirements ..... | 8 |
+| 5.1 Overall Requirements..... | 8 |
+| 5.2 Specific Service Requirements..... | 9 |
+| 5.2.1 Latency/ Reliability Requirements ..... | 9 |
+| 5.2.2 Message Size Requirements ..... | 9 |
+| 5.2.3 Frequency Requirements ..... | 9 |
+| 5.2.4 Range Requirements..... | 9 |
+| 5.2.5 Speed Requirements ..... | 9 |
+| 5.3 Security Requirements ..... | 10 |
+| Annex A (informative): Background Information on Service Requirement..... | 11 |
+| Annex B (informative): Change history..... | 14 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document provides 3GPP support for V2X service requirements to be supported by LTE transport. These requirements are identified by taking into account the V2X service requirements defined in other SDOs, e.g. ETSI ITS, US SAE. The specification includes requirements of safety and non-safety aspects.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.-
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TR 22.885: "Study on LTE Support for V2X Services".
+- [3] ETSI TR 102 638 V1.1.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Road Side Unit:** A stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications.
+
+NOTE: RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that supports V2X application logic using the functionality provided by either a 3GPP network or an UE (referred to as UE-type RSU).
+
+**Pseudonymity:** The condition when the processing of personally identifiable information is such the data can no longer be attributed to a specific subscriber without the use of additional information, as long as such additional information is kept separately and subject to technical and organisational measures to ensure non-attribution to an identified or identifiable subscriber.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|-----|---------------------------|
+| RSU | Road Side Unit |
+| V2I | Vehicle-to-Infrastructure |
+| V2N | Vehicle-to-Network |
+| V2P | Vehicle-to-Pedestrian |
+| V2V | Vehicle-to-Vehicle |
+| V2X | Vehicle-to-Everything |
+
+# 4 Overview on V2X (informative)
+
+## 4.1 Types of V2X application support in 3GPP
+
+### 4.1.1 General
+
+The V2X applications in the present specification, referred to as Vehicle-to-Everything (V2X), contain the following four different types:
+
+- Vehicle-to-Vehicle (V2V)
+- Vehicle-to-Infrastructure (V2I)
+- Vehicle-to-Network (V2N)
+- Vehicle-to-Pedestrian (V2P)
+
+
+
+The diagram shows a central red car labeled 'Vehicle'. Four arrows originate from this car, each representing a different type of V2X communication: 'V2V' points to a yellow car labeled 'Vehicle'; 'V2P' points to a pedestrian icon labeled 'Pedestrian'; 'V2I' points to a radio tower labeled 'RSU'; and 'V2N' points to a server icon labeled 'Application Server'.
+
+Diagram illustrating the types of V2X applications: V2V, V2P, V2I, and V2N.
+
+**Figure 4.1.1-1: Types of V2X applications (V2V, V2P, V2N and V2I)**
+
+These four types of V2X applications can use “co-operative awareness” to provide more intelligent services for end-users. This means that entities, such as vehicles, roadside infrastructure, application server and pedestrians, can collect knowledge of their local environment (e.g., information received from other vehicles or sensor equipment in proximity) to process and share that knowledge in order to provide more intelligent services, such as cooperative collision warning or autonomous driving.
+
+These intelligent transportation services and the associated message sets have been defined in automotive SDOs outside 3GPP. Three basic classes of applications for providing ITS services: road safety, traffic efficiency, and other applications can be found in e.g., [3].
+
+3GPP only handles the transport of these messages to support different types of V2X applications. The message transport expectations are described in requirements defined in this specification.
+
+### 4.1.2 Vehicle-to-Vehicle (V2V) application
+
+V2V applications expect UEs that are in proximity of each other to exchange V2V application information. 3GPP transport of messages containing V2V application information requires the UE to have a valid subscription and authorization from a network operator. Transport for a valid subscriber is provided whether the UE is served or not served by E-UTRAN.
+
+The UE supporting V2V applications transmits messages containing V2V application information (e.g. location, dynamics, and attributes). The message payloads may be flexible in order to accommodate varying amount of information.
+
+3GPP transport of message containing V2V application information is predominantly broadcast-based as illustrated in Figure 4.1-2. Such 3GPP transport includes the transport between UEs directly and/or, due to the limited direct communication range, the transport between UEs via infrastructure supporting V2X communication, e.g., RSU, application server, etc.
+
+
+
+Diagram illustrating broadcast-based V2V communications. A central Tx UE (Transmitter User Equipment) is shown within a dashed circle labeled 'Message broadcasting'. Three Rx UE (Receiver User Equipment) units are positioned around the Tx UE, two within the dashed circle and one outside. A red dashed arrow labeled 'Communication range' points from the Tx UE to one of the Rx UEs outside the dashed circle, indicating the range of the broadcast.
+
+Figure 4.1.2-1: Broadcast-based V2V communications
+
+### 4.1.3 Vehicle-to-Infrastructure (V2I) application
+
+The UE supporting V2I applications transmits messages containing V2I application information to an RSU or locally relevant application server. The RSU and/or the locally relevant application server transmit messages containing V2I application information to one or more UEs supporting V2I applications.
+
+A locally relevant application server serves a particular geographic area. There can be multiple application servers serving overlapping areas, providing the same or different applications.
+
+### 4.1.4 Vehicle-to-Network (V2N) application
+
+The UE supporting V2N applications communicates with an application server supporting V2N applications. Both parties communicate with each other via EPS.
+
+### 4.1.5 Vehicle-to-Pedestrian (V2P) application
+
+V2P applications expect UEs that are in proximity of each other to exchange V2P application information. 3GPP transport of messages containing V2P application information requires the UE to have a valid subscription and authorization from a network operator. Transport for a valid subscriber is provided whether the UE is served or not served by E-UTRAN.
+
+The UE supporting V2P applications transmits messages containing V2P application information. It is expected that V2P application information can be transmitted either by a UE supporting V2X application in a vehicle (e.g., warning to pedestrian), or by a UE supporting V2X application associated with a vulnerable road user (e.g., warning to vehicle).
+
+3GPP transport of messages containing V2P application information includes the transport between UEs directly and/or, due to the limited direct communication range, the transport between UEs via infrastructure supporting V2X communication, e.g., RSU, application server, etc.
+
+NOTE: The main difference between 3GPP transport of messages with V2P and V2V application information is due to the properties of the UE. A UE supporting V2P applications used by pedestrian might, for example, have lower battery capacity, the radio sensitivity might be limited, e.g. due to antenna design, and therefore it may not be able to send messages with the same periodicity as UEs supporting V2V application, and/or receive messages.
+
+## 4.2 Relative priority of V2X communication
+
+Subject to regional/national regulatory requirements and operator policies, certain mission critical services (e.g. Public Safety, MPS) can be relatively prioritized over transport of V2X application information. Transport of safety-related V2X application information can be prioritized over transport of non-safety-related V2X application information.
+
+However, in general, it is expected that operator can control relative priorities of different services.
+
+# --- 5 Requirements
+
+## 5.1 Overall Requirements
+
+[R-5.1-001] The message transmission shall be under control of the 3GPP network when the transmitting UE is served by the E-UTRAN.
+
+[R-5.1-002] A UE supporting V2X application shall be able to be pre-configured by the 3GPP network with parameters to be used for the transmission and reception of messages when not served by E-UTRAN supporting V2X communication.
+
+[R-5.1-003] A UE supporting V2X application shall be able to transmit and receive messages when served or not served by E-UTRAN supporting V2X communication.
+
+[R-5.1-004] An RSU shall be able to transmit/receive messages to/from a UE supporting V2X application.
+
+[R-5.1-005] The 3GPP system shall be able to support message transfer between UEs when served or not served by the same PLMN supporting V2X communications.
+
+[R-5.1-006] The 3GPP system shall be able to provide means to prioritize message transmission among UEs supporting V2X application
+
+[R-5.1-007] The 3GPP system shall be able to provide means to prioritize transmission of messages according to their type (e.g. safety vs. non-safety).
+
+[R-5.1-008] The 3GPP system shall be able to vary the transmission rate and range of the V2X communication based on service conditions (e.g., UE speed, UE density).
+
+[R-5.1-009] The 3GPP system shall be able to distribute information in a resource efficient way to large numbers of UEs supporting V2X application.
+
+[R-5.1-010] A UE supporting V2X application shall be able to identify whether E-UTRAN supports V2X communication.
+
+[R-5.1-011] The 3GPP system shall be able to provide means for an application server and the RSU to control the area and the size of the area where the messages are being distributed.
+
+[R-5.1-011a] The 3GPP system shall be able to provide means for distribution of messages from a UE supporting V2X application to locally relevant application servers.
+
+[R-5.1-012] The E-UTRA(N) shall be able to support a high density of UEs supporting V2X application.
+
+[R-5.1-013] Both the HPLMN and VPLMN operators shall be able to charge for network resource usage when messages are transferred by a UE supporting V2X application.
+
+[R-5.1-014] For UE supporting V2X application with limited resources (e.g., battery), the impact on its resources (e.g., battery consumption) due to message transfer should be minimized.
+
+[R-5.1-015] The 3GPP network should make available any supported positional accuracy improvement techniques (e.g., DGPS and/or OTDOA) in a resource efficient way to a subscribed UE supporting V2X application.
+
+## 5.2 Specific Service Requirements
+
+### 5.2.1 Latency/ Reliability Requirements
+
+[R-5.2.1-001] The E-UTRA(N) shall be capable of transferring messages between two UEs supporting V2V/P application, directly or via an RSU, with a maximum latency of 100ms.
+
+[R-5.2.1-002] For particular usage (i.e., pre-crash sensing) only, the E-UTRA(N) should be capable of transferring messages between two UEs supporting V2V application with a maximum latency of 20ms.
+
+[R-5.2.1-003] The E-UTRA(N) shall be capable of transferring messages between a UE supporting V2I application and an RSU with a maximum latency of 100ms.
+
+[R-5.2.1-004] The E-UTRAN shall be capable of transferring messages via 3GPP network entities between a UE and an application server both supporting V2N application with an end-to-end delay no longer than 1000 ms.
+
+[R-5.2.1-005] The E-UTRA(N) shall be able to support high reliability without requiring application-layer message retransmissions.
+
+### 5.2.2 Message Size Requirements
+
+[R-5.2. 2-001] The E-UTRA(N) shall be capable of transferring periodic broadcast messages between two UEs supporting V2X application with variable message payloads of 50-300 bytes, not including security-related message component.
+
+[R-5.2. 2-002] The E-UTRA(N) shall be capable of transferring event-triggered messages between two UEs supporting V2X application with variable message payloads which can be up to 1200 bytes, not including security-related message component.
+
+NOTE: 3GPP only handles the transport of messages for V2X services/applications based on message characteristics (e.g., latency, message size) and is agnostic to message types.
+
+### 5.2.3 Frequency Requirements
+
+[R-5.2.3-001] The E-UTRA(N) shall be able to support a maximum frequency of 10 messages per second per transmitting UE .
+
+NOTE: It is assumed that V2X application provides messages to 3GPP layer for transport either periodically and/or triggered by certain events.
+
+### 5.2.4 Range Requirements
+
+[R-5.2.4-001] The E-UTRAN shall be capable of supporting a communication range sufficient to give the driver(s) ample response time (e.g. 4 seconds).
+
+### 5.2.5 Speed Requirements
+
+[R-5.2.5-001] The 3GPP system shall be capable of transferring messages between UEs supporting V2V application, while the maximum relative velocity of the UEs is 500 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication.
+
+[R-5.2.5-002] The 3GPP system shall be capable of transferring messages between UEs supporting V2V and V2P application, respectively, while the UE's maximum absolute velocity is 250 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication.
+
+[R-5.2.5-003] The 3GPP system shall be capable of transferring messages between a UE and an RSU both supporting V2I application, while the UE's maximum absolute velocity is 250 km/h, regardless of whether the UE or the RSU is served or not served by E-UTRAN supporting V2X communication.
+
+## 5.3 Security Requirements
+
+[R.5.3-001] The 3GPP network shall provide a means for the MNO to authorize a UE supporting V2X application to perform V2X communication when served by E-UTRAN supporting V2X communication.
+
+[R.5.3-002] The 3GPP network shall provide a means (e.g., pre-authorization) for the MNO to authorize a UE supporting V2X application to perform V2X communication when not served by E-UTRAN supporting V2X communication.
+
+[R.5.3-003] The 3GPP network shall provide a means for the MNO to authorize UEs supporting V2X application separately to perform V2N communication.
+
+[R.5.3-004] The 3GPP system shall support integrity protection of the transmission for a V2X application.
+
+[R.5.3-005] Subject to regional regulatory requirements and/or operator policy for a V2X application, the 3GPP system shall support pseudonymity and privacy of a UE using the V2X application, by ensuring that a UE identity cannot be tracked or identified by any other UE beyond a certain short time-period required by the V2X application.
+
+[R.5.3-006] Subject to regional regulatory requirements and/or operator policy for a V2V/V2I application, the 3GPP system shall support pseudonymity and privacy of a UE in the use of a V2V/V2I application, such that no single party (operator or third party) can track a UE identity in that region.
+
+# Annex A (informative): Background Information on Service Requirement
+
+The basic categories of V2X services for V2X described in the TR 22.885 can be grouped into the following main categories based on ITS definition of basic set of services [3] :
+
+- 1) Road Safety Requirements e.g Queue warning use case related requirements
+- 2) Mutual Vehicle Awareness – Information only e.g forward collision warning requirements
+- 3) Vehicle Related Application Requirements e.g Automated parking system requirement
+
+Clause 5.2 refers to specific service requirements which are categorized as:
+
+**Latency/Reliability Requirements:** Maximum tolerable elapsed time from the instant a data packet is generated at the source application to the instant it is received by the destination application. Low Latency values are provided to support services in the case of mutual awareness of vehicle or to send warning messages as defined in the some use cases in TR22.885
+
+**Reliability:** Maximum tolerable packet loss rate at the application layer, a packet is considered lost if it is not received by the destination application within the maximum tolerable end-to-end latency for that application.
+
+**Message Size Requirements:** Messages sizes are important when multicast or broadcast messages are being sent to vehicles within range to either warn them for collision prevention or when an event occurs to inform other vehicle about an accident.
+
+**Frequency Requirements:** Minimum required bit rate for the application to function correctly. The sending rates i.e frequency of messages is relatively important especially for critical vehicular safety application.
+
+**Range Requirements:** Maximum distance between source and destination(s) of a radio transmission within which the application should achieve the specified reliability
+
+**Speed Requirements:** Maximum relative and absolute speed under which the specified reliability should be achieved.
+
+With this brief description of the service categories, the table suggested below is used to reference the specific requirements in clause 5.2 to some of the use cases in the TR which makes for easy understanding and for better clarification of the suggested application of the services:
+
+| TS requirement | Requirement | Potential V2X service | Use case Requirement in TR 22.885 |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------|
+| Latency Requirement | | | |
+| [R-5.2.1-001] | The E-UTRA(N) shall be capable of transferring messages between two UEs supporting V2V/P application, directly or via an RSU, with a maximum latency of 100ms. | Typical use case is for Mutual Vehicle Awareness and Road safety | [CPR-014] |
+| [R-5.2.1-002] | For particular usage (i.e., pre-crash sensing) only, the E-UTRA(N) should be capable of transferring messages between two UEs supporting V2V application with a maximum latency of 20ms. | Requirement applies in Road safety use cases | [CPR-015] |
+| [R-5.2.1-003] | The E-UTRA(N) shall be capable of transferring messages between a UE supporting V2I application and an RSU with a maximum latency of 100ms. | Requirement applies in Road safety use cases | [CPR-016] |
+
+| | | | |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------|
+| [R-5.2.1-004] | The E-UTRAN shall be capable of transferring messages via 3GPP network entities between a UE and an application server both supporting V2N application with an end-to-end delay no longer than 1000 ms. | Applies to Mutual Vehicle Awareness use case | [CPR-017] |
+| [R-5.2.1-005] | The E-UTRA(N) shall be able to support high reliability without requiring application-layer message retransmissions. | Mutual Vehicle Awareness and Road safety cases | [CPR-027] |
+| Message Size | | | |
+| [R-5.2. 2-001] | The E-UTRA(N) shall be capable of transferring periodic broadcast messages between two UEs supporting V2X application with variable message payloads of 50-300 bytes, not including security-related message component. | Supports all three use case categories | [CPR-019] |
+| [R-5.2. 2-002] | The E-UTRA(N) shall be capable of transferring event-triggered messages between two UEs supporting V2X application with variable message payloads which can be up to 1200 bytes, not including security-related message component. | Mostly Road safety applications | [CPR-020] |
+| Frequency | | | |
+| [R-5.2.3-001] | The E-UTRA(N) shall be able to support a maximum frequency of 10 messages per second per UE or per RSU. | Road safety and Mutual Vehicle Awareness | [CPR-011] |
+| Range Requirement | | | |
+| [R-5.2.4-001] | The E-UTRAN shall be capable of supporting a communication range sufficient to give the driver(s) ample response time (e.g. 4 seconds). | | [CPR-005] |
+| Speed Requirement | | | |
+| [R-5.2.5-001] | The 3GPP system shall be capable of transferring messages between UEs supporting V2V application, while the maximum relative velocity of the UEs is 500 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication. | Road Safety, Mutual Vehicle Awareness | [CPR-030] |
+| [R-5.2.5-002] | The 3GPP system shall be capable of transferring messages between UEs supporting V2V and V2P application, respectively, while the UE's maximum absolute velocity is 250 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication. | Road Safety, Mutual Vehicle Awareness | [CPR-031] |
+
+| | | | |
+|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------|
+| [R-5.2.5-003] | The 3GPP system shall be capable of transferring messages between a UE and an RSU both supporting V2I application, while the UE's maximum absolute velocity is 250 km/h, regardless of whether the UE or the RSU is served or not served by E-UTRAN supporting V2X communication. | Road Safety, Mutual Vehicle Awareness | [CPR-031] |
+|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------|
+
+---
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|---------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-71 | SP-160099 | | | | | | | Raised to v.14.0.0 following one-step-approval by SA | 1.1.0 | 14.0.0 | V2XLTE |
+| SP-72 | SP-160357 | S1-161219 | 22.185 | 0004 | | Rel-14 | F | V2X: correction of missing figure 4.1.2-1 | 14.0.0 | 14.1.0 | V2XLTE |
+| SP-72 | SP-160357 | S1-161426 | 22.185 | 3 | 1 | Rel-14 | F | Clarification of transmission frequency requirement | 14.0.0 | 14.1.0 | V2XLTE |
+| SP-72 | SP-160357 | S1-161517 | 22.185 | 5 | | Rel-14 | F | Inclusion of Informative Annex to TS 22 185 | 14.0.0 | 14.1.0 | V2XLTE |
+| SP-72 | SP-160357 | S1-161518 | 22.185 | 1 | 2 | Rel-14 | F | V2X priority to other services | 14.0.0 | 14.1.0 | V2XLTE |
+| SP-73 | SP-160540 | S1-162507 | 22.185 | 0002 | 7 | Rel-14 | F | Correction on V2X privacy | 14.1.0 | 14.2.0 | V2XLTE |
+| SP-73 | SP-160540 | S1-162504 | 22.185 | 0009 | 2 | Rel-14 | F | Distribution of V2X messages to locally relevant V2X application servers | 14.1.0 | 14.2.0 | V2XLTE |
+| SP-73 | SP-160540 | S1-162503 | 22.185 | 0010 | 2 | Rel-14 | F | Correction of speed parameter values | 14.1.0 | 14.2.0 | V2XLTE |
+| - | - | - | - | - | - | - | - | Version 14.2.0 was mentioning "14.1.0" in the front page. This is corrected in 14.2.1 | 14.2.0 | 14.2.1 | - |
+| SP-75 | SP-170152 | S1-170363 | 22.185 | 0011 | 2 | Rel-14 | D | Clarification on Definition for V2X | 14.2.1 | 14.3.0 | V2XLTE |
+| SP-75 | SP-170152 | S1-171027 | 22.185 | 0012 | | Rel-14 | F | Corrections to requirement numbers in sub-clause 5.22 and Annex A | 14.2.1 | 14.3.0 | V2XLTE |
+| SP-80 | SP-180309 | S1-181352 | 22.185 | 0013 | 1 | Rel-14 | F | Update the note in the RSU definition | 14.3.0 | 14.4.0 | V2XLTE |
+| 2018-06 | - | - | - | - | - | Rel-15 | - | Raised to Rel-15 by MCC | 14.4.0 | 15.0.0 | - |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22186/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-18/22_series/22186/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ac0b0e29f601c6f6984e42294b30ecb1c8b3eae
--- /dev/null
+++ b/marked/Rel-18/22_series/22186/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ce9db6bd08e2d02a3299d2dc7f66b5dace5521ec880b349b25d278c6e6e47c3
+size 25896
diff --git a/marked/Rel-18/22_series/22186/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22186/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5110e8ca321933113f23959f9ac355f31e6e27d6
--- /dev/null
+++ b/marked/Rel-18/22_series/22186/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c72ac5cdbd9e143130e9ad609b16f52ae227a0246918950c2eb63ddedb58ca27
+size 9392
diff --git a/marked/Rel-18/22_series/22186/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22186/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac1e939ff23453d7b73dc095f0938e8df273a3f0
--- /dev/null
+++ b/marked/Rel-18/22_series/22186/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa5331bdcf37991269ad2817637b6995e650a5a96e5f24daf942a10b2bdc82b2
+size 7266
diff --git a/marked/Rel-18/22_series/22186/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/Rel-18/22_series/22186/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16d3da04f3d255da49d10b9555c93bd08efbe83d
--- /dev/null
+++ b/marked/Rel-18/22_series/22186/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af9c709a3e94f9b822924fd0ca3074534933a2bead35f73bf81974dc98468a67
+size 60197
diff --git a/marked/Rel-18/22_series/22186/raw.md b/marked/Rel-18/22_series/22186/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5be2b07f208900b17014a9ef70228ac8b99316e8
--- /dev/null
+++ b/marked/Rel-18/22_series/22186/raw.md
@@ -0,0 +1,519 @@
+
+
+# 3GPP TS 22.186 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Enhancement of 3GPP support for V2X scenarios; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+Vehicle-to-Everything, V2X, eV2X, Vehicular
+communication
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-----------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Overview..... | 6 |
+| 4.1 Categories of requirements to support eV2X scenarios ..... | 6 |
+| 5 Requirements ..... | 7 |
+| 5.1 General Requirements ..... | 7 |
+| 5.2 Requirements to support Vehicles Platooning ..... | 8 |
+| 5.3 Requirements to support Advanced Driving..... | 10 |
+| 5.4 Requirements to support Extended Sensors ..... | 11 |
+| 5.5 Requirements to support Remote Driving..... | 11 |
+| Annex A (informative): Background information on service Requirements ..... | 13 |
+| Annex B (informative): Relation between TS 22.185 and this TS ..... | 15 |
+| Annex C (informative): Relationship between V2X applications and V2X requirements..... | 16 |
+| Annex E (informative): Change history..... | 18 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies service requirements to enhance 3GPP support for V2X scenarios in the 3GPP systems (i.e. EPS, 5G).
+
+It includes transport layer support for both safety and non-safety V2X scenarios:
+
+- Safety-related V2X scenarios: e.g. automated driving, vehicle platooning
+- Non-safety-related V2X scenarios: e.g., mobile high data rate entertainment, mobile hotspot/office/home, dynamic digital map update
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.261: "Service requirements for the 5G system".
+- [3] 3GPP TS 22.185: "Service requirements for V2X services".
+- [4] SAE International, "AUTOMATED DRIVING LEVELS OF DRIVING AUTOMATION ARE DEFINED IN NEW SAE INTERNATIONAL STANDARD J3016", December 2016; US Homeland Security Digital Library, "Self-Driving Cars: Levels of Automation", March 2017 .
+- [5] ISO TS 17419:2014: "Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context".
+- [6] IEEE Std 1609.0-2013: "IEEE Guide for Wireless Access in Vehicular Environments (WAVE) architecture".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**End-to-end latency:** Time it takes to transfer a given piece of information from a source to a destination, measured at the application level, from the moment it is transmitted by the source to the moment it is received at the destination.
+
+**Reliability (%):** The success probability of transmitting X bytes within a certain delay, which is the time it takes to deliver a small data packet from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface.
+
+**Road Side Unit:** A stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications.
+
+NOTE: RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that supports V2X application logic using the functionality provided by either a 3GPP network or an UE (referred to as UE-type RSU).
+
+For the purposes of the present document, the following terms and definitions given in ISO TS 17419 [5] apply:
+
+ITS Application Identifier: globally unique, registered number identifying an ITS application object
+
+For the purposes of the present document, the following term and definition given in IEEE Std 1609.0 [6] apply:
+
+Provider Service Identifier: An identifier of an application-service provided by a higher layer entity.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|---------|-------------------------------|
+| ITS | Intelligent Transport Systems |
+| ITS-AID | ITS Application Identifier |
+| LoA | Level of Automation |
+| PSID | Provider Service Identifier |
+| RSU | Road Side Unit |
+
+# --- 4 Overview
+
+## 4.1 Categories of requirements to support eV2X scenarios
+
+Different V2X scenarios require the transport of V2X messages with different performance requirements for the 3GPP system. This Technical Specification specifies service requirements to enhance 3GPP support for V2X scenarios in the following six areas:
+
+- General Aspects: interworking, communication-related requirements valid for all V2X scenarios
+- Vehicles Platooning
+- Advanced Driving
+- Extended Sensors
+- Remote Driving
+- Vehicle quality of service Support
+
+Vehicles Platooning enables the vehicles to dynamically form a group travelling together. All the vehicles in the platoon receive periodic data from the leading vehicle, in order to carry on platoon operations. This information allows the distance between vehicles to become extremely small, i.e., the gap distance translated to time can be very low (sub second). Platooning applications may allow the vehicles following to be autonomously driven.
+
+Advanced Driving enables semi-automated or fully-automated driving. Longer inter-vehicle distance is assumed. Each vehicle and/or RSU shares data obtained from its local sensors with vehicles in proximity, thus allowing vehicles to coordinate their trajectories or maneuvers. In addition, each vehicle shares its driving intention with vehicles in proximity. The benefits of this use case group are safer traveling, collision avoidance, and improved traffic efficiency.
+
+Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video data among vehicles, RSUs, devices of pedestrians and V2X application servers. The vehicles can enhance the perception of their environment beyond what their own sensors can detect and have a more holistic view of the local situation.
+
+Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves or a remote vehicle located in dangerous environments. For a case where variation is limited
+
+and routes are predictable, such as public transportation, driving based on cloud computing can be used. In addition, access to cloud-based back-end service platform can be considered for this use case group.
+
+Vehicle quality of service support enables a V2X application to be timely notified of expected or estimated change of quality of service before actual change occurs and to enable the 3GPP System to modify the quality of service in line with V2X application's quality of service needs. Based on the quality of service information, the V2X application can adapt behaviour to 3GPP System's conditions. The benefits of this use case group are offerings of smoother user experience of service.
+
+## 4.2 Level of Automation
+
+A relevant aspect of advanced V2X applications is the Level of Automation (LoA), which reflects the functional aspects of the technology and affects the system performance requirements. In accordance with the levels from SAE [4], the LoA are: 0 – No Automation, 1 – Driver Assistance, 2 – Partial Automation, 3 – Conditional Automation, 4 – High Automation, 5 – Full Automation.
+
+A distinction is drawn between lower levels and higher levels based on whether the human operator or the automated system is primarily responsible for monitoring the driving environment.
+
+The 3GPP system provides the performances expected for all levels of automation
+
+# --- 5 Requirements
+
+## 5.1 General Requirements
+
+[R.5.1-001] The 3GPP system shall be able to control the communication range for a message based on the characteristic of the messages transmitted by a UE supporting V2X application.
+
+[R.5.1-002] The 3GPP system shall be able to optimize the communication between UEs supporting V2X application belonging to the same group and in proximity.
+
+[R.5.1-003] The 3GPP system shall be able to support the message transfer for group management operations as requested by the application layer.
+
+NOTE 1: The determination of group membership may be done at the upper layers and/or lower layers (application and/or Layer 2).
+
+[R.5.1-004] The 3GPP system shall be able to support message transfer among a group of UEs supporting V2X application.
+
+[R.5.1-005] The 3GPP system shall be able to support message transfer between two UEs belonging to the same group of UEs supporting V2X application.
+
+[R.5.1-006] The 3GPP system shall be able to support confidentiality and integrity of message transfer among a group of UEs supporting V2X application.
+
+[R.5.1-007] The 3GPP system shall support relative lateral position accuracy of 0.1 m between UEs supporting V2X application.
+
+[R.5.1-008] The 3GPP system shall support high connection density for congested traffic.
+
+NOTE 2: Example estimate is for worst case US Freeway scenario that does not include arterial roads (i.e. onramps): 5 lanes in each direction or 10 lanes total per highway, for up to 3 highways intersecting = 3,100 to 4,300 cars per square kilometer
+
+[R.5.1-009] The 3GPP system shall support efficient coordination of radio resources used for transport of messages to maximize the utilization of the available spectrum and to ensure the required reliability.
+
+[R.5.1-010] The 3GPP system shall be able to control the UL and DL reliability of transport of V2X communications, depending on the requirement of V2X application
+
+[R.5.1-011] Impact to E-UTRA(N) by UE supporting only NR based V2X communication shall be minimized.
+
+[R.5.1-012] Impact to NR by UE supporting only E-UTRA based V2X communication shall be minimized.
+
+[R.5.1-013] The 3GPP system shall be able to support message transfer between UEs or between a UE and a UE-type RSU, regardless of whether or not they are subscribers of the same PLMN supporting V2X communications. In case they are subscribers to different PLMNs, there shall be no service degradation of the message transfer.
+
+[R.5.1-014] The 3GPP system shall enable discovery and communication between UEs supporting the same V2X application.
+
+[R.5.1-015] The 3GPP system shall be able to support the operators to select which 3GPP RAT to use for a V2X application.
+
+NOTE 3: Different V2X applications can be identified by use of different ITS-AID or PSID.
+
+[R.5.1-016] The 3GPP system shall enable a UE supporting a V2X application to obtain network access via another UE supporting V2X application.
+
+[R.5.1-017] The 3GPP system shall enable a UE supporting a V2X application to discover another UE supporting V2X application that can offer access to the network.
+
+[R.5.1-018] The 3GPP system shall support switching between direct 3GPP connection and indirect 3GPP connection via a UE supporting a V2X application, for a UE supporting a V2X application.
+
+[R.5.1-019] The 3GPP system should be able to support confidentiality and integrity of message transfer between a UE supporting a V2X application and network, when the UE is using an indirect 3GPP connection.
+
+[R.5.1-020] The 3GPP system shall allow UEs supporting V2X application to use NR for direct communication when the UEs are not served by a RAN using NR.
+
+[R.5.1-021] The 3GPP system shall allow UEs supporting V2X application to use E-UTRA for direct communication when the UEs are not served by a RAN using E-UTRA.
+
+[R.5.1-022] An RSU shall be able to communicate with up to 200 UEs supporting a V2X application.
+
+NOTE 4: This requirement specifies the number of UEs that RSU should be capable of handling. The requirement is not applied to the number of UE in a platoon.
+
+NOTE 5: This requirement is not applied to UE-type RSU.
+
+[R.5.1-023] The 3GPP system shall be able to support confidentiality and integrity of message transfer between a UE supporting V2X application and a V2X application server.
+
+[R.5.1-024] The 3GPP system shall provide a mechanism to provide addressing information (e.g. IP address or FQDN) of V2X application server(s) to the UEs supporting V2X applications.
+
+[R.5.1-025] The 3GPP system shall allow the UE to use multiple 3GPP RATs (i.e. NR & E-UTRA) simultaneously for direct communication.
+
+## 5.2 Requirements to support Vehicles Platooning
+
+[R.5.2-001] The 3GPP system shall be able to support up to 5 UEs for a group of UEs supporting V2X application.
+
+[R.5.2-002] For Vehicle Platooning, the 3GPP system shall be able to support reliable V2V communications between a specific UE supporting V2X applications and up to 19 other UEs supporting V2X applications.
+
+NOTE 1: For group of heavy goods vehicle platooning, the number of UEs in a platoon can be smaller, due to communication range, the length of truck, inter-truck distance, etc.
+
+[R.5.2-003] The 3GPP system shall support relative longitudinal position accuracy of less than 0.5 m for UEs supporting V2X application for platooning in proximity.
+
+Table 5.2-1 Performance requirements for Vehicles Platooning
+
+| Communication scenario description | | Req # | Payload (Bytes) | Tx rate (Message / Sec) | Max end-to-end latency (ms) | Reliability (%) (NOTE 5) | Data rate (Mbps) | Min required communication range (meters) (NOTE 6) |
+|-----------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------|------------------|-------------------------|-----------------------------|--------------------------|------------------|----------------------------------------------------|
+| Scenario | Degree | | | | | | | |
+| Cooperative driving for vehicle platooning Information exchange between a group of UEs supporting V2X application. | Lowest degree of automation | [R.5.2-004] | 300-400 (NOTE 2) | 30 | 25 | 90 | | |
+| | Low degree of automation | [R.5.2-005] | 6500 (NOTE 3) | 50 | 20 | | | 350 |
+| | Highest degree of automation | [R.5.2-006] | 50-1200 (NOTE 4) | 30 | 10 | 99.99 | | 80 |
+| | High degree of automation | [R.5.2-007] | | | 20 | | 65 (NOTE 3) | 180 |
+| Reporting needed for platooning between UEs supporting V2X application and between a UE supporting V2X application and RSU. | N/A | [R.5.2-008] | 50-1200 | 2 | 500 | | | |
+| Information sharing for platooning between UE supporting V2X application and RSU. | Lower degree of automation | [R.5.2-009] | 6000 (NOTE 3) | 50 | 20 | | | 350 |
+| | Higher degree of automation | [R.5.2-0010] | | | 20 | | 50 (NOTE 3) | 180 |
+
+NOTE 2: This value is applicable for both triggered and periodic transmission of data packets.
+
+NOTE 3: The data that is considered in this V2X scenario includes both cooperative manoeuvres and cooperative perception data that could be exchanged using two separate messages within the same period of time (e.g., required latency 20ms).
+
+NOTE 4: This value does not include security related messages component.
+
+NOTE 5: Sufficient reliability should be provided even for cells having no value in this table
+
+NOTE 6: This is obtained considering UE speed of 130km/h. All vehicles in a platoon are driving in the same direction.
+
+## 5.3 Requirements to support Advanced Driving
+
+Table 5.3-1 Performance requirements for advanced driving
+
+| Communication scenario description | | Req # | Payload (Bytes) | Tx rate (Message /Sec) | Max end-to-end latency (ms) | Reliability (%) (NOTE3) | Data rate (Mbps) | Min required Communication range (meters) (NOTE 4) |
+|-----------------------------------------------------------------------------------------|-----------------------------|-------------|-----------------|------------------------|-----------------------------|-------------------------|-----------------------------|----------------------------------------------------|
+| Scenario | Degree | | | | | | | |
+| Cooperative collision avoidance between UEs supporting V2X applications. | | [R.5.3-001] | 2000 (NOTE 5) | 100 (NOTE 5) | 10 | 99.99 | 10 (NOTE 1) | |
+| Information sharing for automated driving between UEs supporting V2X application. | Lower degree of automation | [R.5.3-002] | 6500 (NOTE 1) | 10 | 100 | | | 700 |
+| | Higher degree of automation | [R.5.3-003] | | | 100 | | 53 (NOTE 1) | 360 |
+| Information sharing for automated driving between UE supporting V2X application and RSU | Lower degree of automation | [R.5.3-004] | 6000 (NOTE 1) | 10 | 100 | | | 700 |
+| | Higher degree of automation | [R.5.3-005] | | | 100 | | 50 (NOTE 1) | 360 |
+| Emergency trajectory alignment between UEs supporting V2X application. | | [R.5.3-006] | 2000 (NOTE 5) | | 3 | 99.999 | 30 | 500 |
+| Intersection safety information between an RSU and UEs supporting V2X application. | | [R.5.3-007] | UL: 450 | UL: 50 | | | UL: 0.25
DL: 50 (NOTE 2) | |
+| Cooperative lane change between UEs supporting V2X applications. | Lower degree of automation | [R.5.3-008] | 300-400 | | 25 | 90 | | |
+| | Higher degree of automation | [R.5.3-009] | 12000 | | 10 | 99.99 | | |
+| Video sharing between a UE supporting V2X application and a V2X application server. | | [R.5.3-010] | | | | | UL: 10 | |
+
+NOTE 1: This includes both cooperative manoeuvres and cooperative perception data that could be exchanged using two separate messages within the same period of time (e.g., required latency 100ms).
+
+NOTE 2: This value is referring to a maximum number of 200 UEs. The value of 50 Mbps DL is applicable to broadcast or is the maximum aggregated bitrate of the all UEs for unicast.
+
+NOTE 3: Sufficient reliability should be provided even for cells having no values in this table
+
+NOTE 4: This is obtained considering UE speed of 130km/h. Vehicles may move in different directions.
+
+NOTE 5: These values are based on calculations for cooperative maneuvers only.
+
+## 5.4 Requirements to support Extended Sensors
+
+Table 5.4-1 Performance requirements for extended sensors
+
+| Communication scenario description | | Req # | Payload (Bytes) | Tx rate (Message /Sec) | Max end-to-end latency (ms) | Reliability (%) | Data rate (Mbps) | Min required communication range (meters) |
+|-------------------------------------------------------------------|-----------------------------|----------------------|-----------------|------------------------|-----------------------------|-----------------|------------------|-------------------------------------------|
+| Scenario | Degree | | | | | | | |
+| Sensor information sharing between UEs supporting V2X application | Lower degree of automation | [R.5.4-001] | 1600 | 10 | 100 | 99 | | 1000 |
+| | Higher degree of automation | [R.5.4-002] | | | 10 | 95 | 25 (NOTE 1) | |
+| | | [R.5.4-003] | | | 3 | 99.999 | 50 | 200 |
+| | | [R.5.4-004] | | | 10 | 99.99 | 25 | 500 |
+| | | [R.5.4-005] | | | 50 | 99 | 10 | 1000 |
+| | | [R.5.4-006] (NOTE 2) | | | 10 | 99.99 | 1000 | 50 |
+| Video sharing between UEs supporting V2X application | Lower degree of automation | [R.5.4-007] | | | 50 | 90 | 10 | 100 |
+| | Higher degree of automation | [R.5.4-008] | | | 10 | 99.99 | 700 | 200 |
+| | | [R.5.4-009] | | | 10 | 99.99 | 90 | 400 |
+
+NOTE 1: This is peak data rate.
+NOTE 2: This is for imminent collision scenario.
+
+## 5.5 Requirements to support Remote Driving
+
+[R.5.5-001] The 3GPP system shall support message exchange between a UE supporting V2X application and V2X application server for an absolute speed of up to 250 km/h.
+
+Table 5.5-1 Performance requirements for remote driving
+
+| Communication scenario description | Req # | Max end-to-end latency (ms) | Reliability (%) | Data rate (Mbps) |
+|-------------------------------------------------------------------------------------------|-------------|-----------------------------|-----------------|------------------|
+| Information exchange between a UE supporting V2X application and a V2X Application Server | [R.5.5-002] | 5 | 99.999 | UL: 25
DL: 1 |
+
+## 5.6 Requirements to support vehicle quality of service
+
+[R.5.6-001] The 3GPP system shall be able to provide a standardized interface to V2X applications to enable the V2X application to adjust its service offerings based on the quality of service of the ongoing connection or on the estimated quality of service.
+
+[R.5.6-002] The 3GPP system shall be able to authenticate and authorize V2X application for requesting information on the quality of service of the ongoing connection or on the estimated quality of service.
+
+[R.5.6-003] The 3GPP system shall be able to provide quality of service information to the V2X application in a resource efficient way.
+
+[R.5.6-004] The 3GPP system shall be able to support an efficient and secure mechanism to gather information (e.g. location information, reliability information, timing information, latency information, velocity information), in order to generate information about quality of service in a resource efficient way.
+
+[R.5.6-005] The 3GPP system shall be able to support continuity of reporting estimated quality of service for a UE even when the PLMN serving the UE changes.
+
+[R.5.6-006] The 3GPP system shall be able to provide V2X applications with estimated quality of service information for a certain geographic area and time.
+
+[R.5.6-007] The 3GPP system shall be able to provide a V2X application with quality of service parameters that can be provisioned for connection for a certain geographic area in a certain time.
+
+[R.5.6-008] The 3GPP system shall be able to notify V2X applications with updated estimation of unfulfillment (or re-fulfillment) of quality of service for a certain geographic area, at least a certain amount of time before when the actual change occurs.
+
+[R.5.6-009] On request by the V2X application, the 3GPP system shall be able to provide information on whether connectivity with specific quality of service is expected to be fulfilled in a certain geographical area and at a certain time.
+
+[R.5.6-010] The 3GPP network shall notify a V2X application that the current quality of service of a UE's ongoing communication might be unfulfilled (or re-fulfilled) in the future.
+
+[R.5.6-011] The 3GPP system shall be able to support negotiating quality of service alternatives with the V2X application.
+
+[R.5.6-012] The 3GPP system shall be able to provide V2X applications with updated quality of service from the quality of service alternatives previously negotiated by the V2X application, when the quality of service of the UE's ongoing connection changes.
+
+[R.5.6-013] The 3GPP system shall be able to support a V2X application to request connectivity with specific quality of service parameter for a certain geographic area and time.
+
+[R.5.6-014] The 3GPP system shall be able to provide a V2X application with response on whether the request of connectivity service with specific quality of service parameter for a certain geographic area and a certain time is accepted or not.
+
+# Annex A (informative): Background information on service Requirements
+
+For each requirement in this specification, Table A-1 indicates reference to the consolidated potential requirements in TR 22.886:
+
+**Table A-1 Reference information for requirements**
+
+| Requirement # in this specification | CPR # in TR 22.886 |
+|-------------------------------------|--------------------|
+| [R.5.1-001] | [CPR.G-001] |
+| [R.5.1-002] | [CPR.G-002] |
+| [R.5.1-003] | [CPR.G-003] |
+| [R.5.1-004] | [CPR.G-004] |
+| [R.5.1-005] | [CPR.G-005] |
+| [R.5.1-006] | [CPR.G-006] |
+| [R.5.1-007] | [CPR.G-007] |
+| [R.5.1-008] | [CPR.G-009] |
+| [R.5.1-009] | [CPR.G-010] |
+| [R.5.1-010] | [CPR.G-011] |
+| [R.5.1-011] | [CPR.G-012] |
+| [R.5.1-012] | [CPR.G-013] |
+| [R.5.1-013] | [CPR.G-014] |
+| [R.5.1-014] | [CPR.G-016] |
+| [R.5.1-015] | [CPR.G-017] |
+| [R.5.1-016] | [CPR.G-018] |
+| [R.5.1-017] | [CPR.G-019] |
+| [R.5.1-018] | [CPR.G-020] |
+| [R.5.1-019] | [CPR.G-021] |
+| [R.5.1-020] | [CPR.G-022] |
+| [R.5.1-021] | [CPR.G-022] |
+| [R.5.1-022] | [CPR.G-023] |
+| [R.5.1-023] | [CPR.G-025] |
+| [R.5.2-001] | [CPR.P-001] |
+| [R.5.2-002] | [CPR.P-002] |
+| [R.5.2-003] | [CPR.P-003] |
+| [R.5.2-004] | [CPR.P-005] |
+| [R.5.2-004] | [CPR.P-007] |
+| [R.5.2-005] | [CPR.P-009] |
+| [R.5.2-006] | [CPR.P-008] |
+| [R.5.2-006] | [CPR.P-004] |
+| [R.5.2-007] | [CPR.P-010] |
+| [R.5.2-008] | [CPR.P-006] |
+| [R.5.2-009] | [CPR.P-011] |
+| [R.5.2-010] | [CPR.P-012] |
+| [R.5.3-001] | [CPR.A-001] |
+| [R.5.3-002] | [CPR.A-002] |
+| [R.5.3-003] | [CPR.A-003] |
+| [R.5.3-004] | [CPR.A-004] |
+| [R.5.3-005] | [CPR.A-005] |
+| [R.5.3-006] | [CPR.A-006] |
+| [R.5.3-007] | [CPR.A-007] |
+| [R.5.3-008] | [CPR.A-008] |
+| [R.5.3-009] | [CPR.A-009] |
+| [R.5.3-010] | [CPR.A-010] |
+| [R.5.4-001] | [CPR.E-002] |
+| [R.5.4-002] | [CPR.E-001] |
+| [R.5.4-003] | [CPR.E-003] |
+
+| | |
+|-------------|----------------------------------------------------------|
+| [R.5.4-004] | [CPR.E-004] |
+| [R.5.4-005] | [CPR.E-005] |
+| [R.5.4-006] | [CPR.E-006] |
+| [R.5.4-007] | [CPR.E-007] |
+| [R.5.4-008] | [CPR.E-008] |
+| [R.5.4-009] | [CPR.E-008] |
+| [R.5.5-001] | [CPR.R-001] |
+| [R.5.5-002] | [CPR.R-001]
[CPR.R-002]
[CPR.R-003]
[CPR.R-004] |
+| [R.5.6-001] | [CPR.Q-015] |
+| [R.5.6-002] | [CPR.Q-009] |
+| [R.5.6-003] | [CPR.Q-002] |
+| [R.5.6-004] | [CPR.Q-002] |
+| [R.5.6-005] | [CPR.Q-004] |
+| [R.5.6-006] | [CPR.Q-001] |
+| [R.5.6-007] | [CPR.Q-006] |
+| [R.5.6-008] | [CPR.Q-017] |
+| [R.5.6-009] | [CPR.Q-011] |
+| [R.5.6-010] | [CPR.Q-018] |
+| [R.5.6-011] | [CPR.Q-007] |
+| [R.5.6-012] | [CPR.Q-019] |
+| [R.5.6-013] | [CPR.Q-012] |
+| [R.5.6-014] | [CPR.Q-013] |
+
+# --- Annex B (informative): Relation between TS 22.185 and this TS
+
+3GPP Technical Specification on Service Requirements for V2X Services [3] was developed with focus on basic safety aspect and non-safety aspect using LTE-based technology. This Technical Specification on Enhancement of 3GPP Support for V2X Services was developed with focus on enhancements of V2X Use Case scenarios, including more rigorous functional requirements for advanced features that cannot be achieved by [3].
+
+# Annex C (informative): Relationship between V2X applications and V2X requirements
+
+In this specification, performance requirements for various scenarios are defined. KPIs of the various scenarios are not mutually exclusive. When several V2X applications are simultaneously running in the vehicle, total performance requirement to serve that vehicle is not the sum of individual performance requirement of each V2X application:
+
+- Different use cases or applications may use and share same V2X message. For example, according to ETSI TS 102.637, information included in a DENM message can be used by multiple applications such as emergency electronic brake lights, wrong way driving warning and so on. Thus, there is no need for each application to generate separately V2X messages.
+- According to ETSI EN 302.665, V2X application layer is separated from V2X Facilities layer. V2X applications do not have V2X message handling capabilities, and this is left to V2X Facilities layer. Because V2X Facilities layer serves all V2X applications, the V2X Facilities layer can optimize V2X message handling, by considering overall requirements of different V2X applications.
+
+Figure C-1 shows one of example configuration where multiples V2X applications and one common V2X message handling entity exist. Because only one driving wheel, one accelerator and one brake exist in a vehicle, the applications in a vehicle may either be combined or operate in a harmonized fashion. Then, V2X messages are also used in a harmonized fashion.
+
+
+
+Figure C-1: Relationship between V2X messages and Applications (illustrative purpose only). The diagram illustrates a vehicle's internal architecture and its interaction with external V2X modules. At the top, a 'Decision Unit (e.g. Autonomous driving system or human driver)' contains 'Applications (use cases)' (Platooning, Cooperative adaptive cruise control, Cooperative collision avoidance and so on) and 'Decision Logic'. Below this is a 'Data Management' block with 'Dynamic Map' and 'Planning/Control Data'. A 'Sensor System' feeds into the 'Dynamic Map'. The 'Decision Unit' interacts with 'Data Management' and a 'Control Unit (e.g. Actuators..)'. The 'Control Unit' manages 'Driving wheels' and 'Accelerator/braking'. A 'V2X Function' block is connected to 'Data Management' and a 'V2X module of other Vehicles/Infras/Servers' via 'V2X MSGs (e.g. CAM, DENM, CAMv2, BSM, etc)'. A dashed line separates the internal vehicle components from the external V2X module.
+
+Figure C-1. Relationship between V2X messages and Applications (illustrative purpose only)
+
+# Annex D (informative): Role model for service exposure for Estimation
+
+In relation to the service requirements in section 5.6, following figure shows the role model for the involved entities. Data gathering entity gathers relevant data that can be used as an input to estimation entity. The data can be statistical data, historical data and etc. Based on the data provided by data gathering entity, estimation entity makes an estimation that is requested by third parties. The result of estimation is provided from 3GPP system to third party. While interface from 3GPP system toward third party and interface among entities within 3GPP system is standardized, how actual estimation mechanism is performed within estimation entity or how much the estimation is accurate is out of 3GPP scope.
+
+
+
+```
+graph LR; subgraph 3GPP_System [3GPP System]; DG[Data Gathering] <--> E[Estimation]; end; TP[Third party (e.g. V2X application)]; TP -- Service Request --> 3GPP_System; 3GPP_System -- "Service Response (e.g. estimated information)" --> TP;
+```
+
+Diagram illustrating the role model for service exposure for Estimation. A 3GPP System (containing Data Gathering and Estimation entities) interacts with a Third party (e.g. V2X application). The Third party sends a Service Request to the 3GPP System, and the 3GPP System responds with a Service Response (e.g. estimated information).
+
+**NOTE:** How estimation is done is outside of 3GPP Scope
+
+# Annex E (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|----|-----|-----|----------------------------------------------------------------|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2017-01 | | | | | | Skeleton | | 0.1.0 |
+| 2017-02 | | | | | | Update based on agreement in SA1 #77 | | 0.2.0 |
+| 2017-03 | SA#75 | SP-170158 | | | | MCC Clean-up | | 1.0.0 |
+| 2017-03 | SA#75 | SP-170250 | | | | Update based on input from SA#75, including assigned TS number | | 1.0.1 |
+| 2017-03 | | | | | | Raised to v.15.0.0 following SA's approval | | 15.0.0 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|--------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-76 | SP-170444 | S1-172363 | 22.186 | 0006 | 4 | Rel-15 | B | Adding requirement on addressing information of V2X application server(s) | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172304 | 22.186 | 0003 | 1 | Rel-15 | F | Clean-up of KPI of eV2X TS | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172311 | 22.186 | 0008 | 3 | Rel-15 | F | Consolidate communication range in 5.3 Advanced Driving | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172310 | 22.186 | 0009 | 2 | Rel-15 | F | Correction of NOTE 2 UL/DL values in 5.3 Advanced Driving | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172301 | 22.186 | 0007 | 1 | Rel-15 | D | Editorial modifications for TS 22.186 | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172306 | 22.186 | 0012 | 1 | Rel-15 | D | Global editorial clean-up | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172309 | 22.186 | 0001 | 2 | Rel-15 | F | Removal of editor's NOTE in section 5.1 | 15.0.0 | 15.1.0 | eV2X |
+| SP-76 | SP-170444 | S1-172313 | 22.186 | 0010 | 2 | Rel-15 | C | Remove the brackets and Editor's note in Video sharing of 5.4 Extended Sensors | 15.0.0 | 15.1.0 | eV2X |
+| SP-77 | SP-170693 | S1-173479 | 22.186 | 0013 | 2 | Rel-15 | F | Correction to information exchange via RSU | 15.1.0 | 15.2.0 | eV2X |
+| SP-77 | SP-170693 | S1-173480 | 22.186 | 0015 | 2 | Rel-15 | F | correction to data rate and transmission rate | 15.1.0 | 15.2.0 | eV2X |
+| SP-80 | SP-180309 | S1-181562 | 22.186 | 0016 | 2 | Rel-15 | F | Update the note in the RSU definition | 15.2.0 | 15.3.0 | eV2X |
+| SP-81 | SP-180755 | S1-182626 | 22.186 | 0018 | 1 | Rel-16 | A | SAE International's Levels of Automation reference link | 15.3.0 | 16.0.0 | eV2X |
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2018-12 | SP-82 | SP-181012 | 0019 | 4 | B | normative requirements for V2XIMP | | 16.1.0 |
+| 2018-12 | SP-82 | SP-181012 | 0020 | 2 | B | Annex Role model for V2XIMP | | 16.1.0 |
+| 2019-06 | SA#84 | SP-190568 | 0023 | 6 | F | CR to TS 22.186 on eV2X Requirements | | 16.2.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22220/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-18/22_series/22220/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97a0a5a51c6c78099c11f9d3f96fd5dec6b8c8a2
--- /dev/null
+++ b/marked/Rel-18/22_series/22220/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35dcbaa7a9dcc9896900e9fdaded3f54ba9667e29aeff543ac2a74e60903433e
+size 86244
diff --git a/marked/Rel-18/22_series/22220/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22220/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/22_series/22220/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/22_series/22220/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22220/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2df6ad86e7021bc7b157060e6b949b94736b13ff
--- /dev/null
+++ b/marked/Rel-18/22_series/22220/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53faf037465dde7b382f95640f809053f12882698bd17ee17c7b0f3ac7e8cf9
+size 5413
diff --git a/marked/Rel-18/22_series/22220/raw.md b/marked/Rel-18/22_series/22220/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..96fb65fd8ee433f82b3a3aa029eb49fb857164f8
--- /dev/null
+++ b/marked/Rel-18/22_series/22220/raw.md
@@ -0,0 +1,722 @@
+
+
+# 3GPP TS 22.220 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for Home Node B (HNB) and Home eNode B (HeNB) (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+UMTS, LTE, stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 General..... | 7 |
+| 4.1 Description ..... | 7 |
+| 5 Common requirements for Home NodeB / Home eNodeB ..... | 7 |
+| 5.1 HNB and HeNB Installation, identification and location requirements ..... | 7 |
+| 5.2 OA&M Requirements ..... | 8 |
+| 5.3 Access Control requirements ..... | 8 |
+| 5.3.1 General ..... | 8 |
+| 5.3.2 Closed Subscriber Group..... | 9 |
+| 5.4 Display requirements..... | 10 |
+| 5.4.1 CSG Type ..... | 10 |
+| 5.4.2 HNB Name ..... | 10 |
+| 5.5 Mobility Aspects for Home NodeB and Home eNodeB..... | 11 |
+| 5.5.1 PLMN selection..... | 11 |
+| 5.5.2 Idle-mode operation..... | 11 |
+| 5.5.3 Connected mode operation ..... | 11 |
+| 5.5.4 Manual CSG selection..... | 11 |
+| 5.6 Services support ..... | 12 |
+| 5.6.1 General ..... | 12 |
+| 5.6.2 Emergency services ..... | 12 |
+| 5.6.3 IMS Interworking ..... | 12 |
+| 5.7 Local IP Access (LIPA) ..... | 13 |
+| 5.7.1 Description ..... | 13 |
+| 5.7.2 General requirements..... | 13 |
+| 5.8 Managed Remote Access to home based network..... | 14 |
+| 5.9 Selected IP Traffic Offload (SIPTO) at Local Networks ..... | 14 |
+| 5.10 UICC and H(e)NB..... | 15 |
+| 5.11 Void..... | 15 |
+| 5.11.1 Void ..... | 15 |
+| 5.11.2 Void ..... | 15 |
+| 6 Requirements for Home NodeB..... | 15 |
+| 6.1 Access Control ..... | 15 |
+| 6.2 Void..... | 16 |
+| 7 Requirements for Home eNodeB..... | 16 |
+| 7.1 Services support ..... | 16 |
+| 7.1.1 Void ..... | 16 |
+| 8 Quality of Service ..... | 16 |
+| 8.1 General ..... | 16 |
+| 8.2 Admission Control ..... | 16 |
+| 9 Security and privacy..... | 16 |
+| 9.1 General ..... | 16 |
+| 9.2 Security Requirements ..... | 16 |
+| 9.3 Privacy..... | 16 |
+
+10 Charging Aspects ..... 17
+
+Annex A (informative): Use cases..... 18
+
+Annex B (informative): Clarification of H(e)NB Access Modes ..... 21
+
+Annex C (informative): Overview of identifiers and names. .... 22
+
+Annex D (informative): Change history..... 24
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+In Rel-8, 3GPP has specified the basic functionalities for the support of Home Node B (HNB) and Home eNodeB (HeNB). The requirements for these basic functionalities were captured in TS 22.011.
+
+From Rel-9 onward, it has been agreed to consolidate all the requirements from Rel-8 and further requirements for HNB and HeNB in a new TS, which is this specification.
+
+# --- 1 Scope
+
+This specification defines the service requirements for the basic functionalities for the support of Home NodeB (HNB) and Home eNodeB (HeNB) – jointly referred to as H(e)NB – and the further functionalities that will enable the mobile operators to provide more advanced services as well as improving the user experience.
+
+# --- 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] Void
+- [3] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1".
+- [4] 3GPP TS 22.101: "Service Aspects; Service Principles".
+- [5] TR-069 Amendment 2: "CPE WAN Management Protocol v1.1, Broadband Forum", viewable at
+- [6] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
+- [7] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
+- [8] 3GPP TS 22.115: "Service aspects; Charging and billing".
+- [9] 3GPP TS 22.268: "Public Warning System (PWS) requirements".
+- [10] 3GPP TS 22.011: "Service accessibility".
+- [11] 3GPP TS 31.115: "Secured packet structure for (Universal) Subscriber Identity Mobile (U)SIM Toolkit applications".
+- [12] 3GPP TS 31.116: "Remote APDU Structure for (U)SIM Toolkit applications".
+
+# --- 3 Definitions, symbols 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].
+
+**Closed access mode:** H(e)NB provides services only to its associated CSG members.
+
+**Home based network:** An IP based network in the same premises as, and is connected to, the H(e)NB.
+
+**Hybrid access mode:** H(e)NB provides services to its associated CSG members and to non-CSG members.
+
+**Open access mode:** H(e)NB operates as a normal NodeB or eNodeB.
+
+**HNB:** A HNB is a Customer-premises equipment that connects a 3GPP UE over UTRAN wireless air interface to a mobile operator's network using a broadband IP backhaul.
+
+**HeNB:** A HeNB is a Customer-premises equipment that connects a 3GPP UE over EUTRAN wireless air interface to a mobile operator's network using a broadband IP backhaul.
+
+**H(e)NB Gateway:** H(e)NB Gateway is a mobile operator's equipment (usually physically located on mobile operator premises) through which the H(e)NB gets access to mobile operator's core network.
+
+**H(e)NB Hosting Party:** A H(e)NB Hosting Party has a contractual relationship with the operator, related to the provision of access to the operator's network via one or more H(e)NBs.
+
+NOTE: A H(e)NB Hosting Party is likely to have the billing relationship with the operator. A H(e)NB Hosting Party will typically be the "lead" user in a household but could be e.g. the corporate IT manager in an enterprise context.
+
+**H(e)NB Subsystem:** A H(e)NB Subsystem consists of the H(e)NB and the H(e)NB Gateway.
+
+## 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].
+
+| | |
+|--------|-------------------------|
+| CSG | Closed Subscriber Group |
+| HNB | Home NodeB |
+| HeNB | Home eNodeB |
+| H(e)NB | HNB and HeNB |
+
+# --- 4 General
+
+## 4.1 Description
+
+Access to 3G and evolved 3G (EPS) services may be provided via UTRAN or E-UTRAN cellular base stations belonging to e.g. domestic, business, commercial enterprises. This type of access may be provided by the PLMN by means of HNB and HeNB (jointly referred to as H(e)NB). The H(e)NB provides services either only to a Closed Subscriber Group (CSG) or to other mobile subscribers too. The H(e)NB is connected to the mobile operator core network using IP via any suitable access technology.
+
+# --- 5 Common requirements for Home NodeB / Home eNodeB
+
+## 5.1 HNB and HeNB Installation, identification and location requirements
+
+- H(e)NB shall have a unique equipment identity.
+- All the H(e)NBs serving the same CSG share the same unique (within the PLMN) identity called CSG Identity.
+
+NOTE: CSGs of different PLMNs are considered different, even if the PLMNs are indicated to the UE as "equivalent PLMNs" [10].
+
+- It shall be possible to support at least 125 million CSG Identities within a PLMN of an operator.
+- The radio transmitter of a H(e)NB shall not be activated until configured and authorised by the operator.
+- When installing, provisioning, configuring or re-configuring an H(e)NB the operator shall be able to:
+ - verify the H(e)NB's identity.
+ - obtain the geographical location of the H(e)NB.
+
+NOTE: The scenario where a H(e)NB is connected to one operator's network and later changed to another operator's network is not required.
+
+- The operator shall be able to determine that the H(e)NB is installed and operated in accordance with all relevant regulatory requirements.
+- The operator shall be able to configure the settings of the H(e)NB. In the case where the H(e)NB has detrimental impact on the spectrum usage, the H(e)NB can be set to out-of-service by the operator.
+- Installation and activation of a new H(e)NB shall require no reconfiguration of the operator's network.
+- The impact of H(e)NB on the core network should be minimised.
+
+## 5.2 OA&M Requirements
+
+- H(e)NB shall support the automatic discovery of an operator's management platform.
+- It shall be possible to make use of the operator's management platform to carry out OA&M functions for H(e)NB. The management connection between H(e)NB and the operator's management platform shall be end-to-end secure.
+- H(e)NB shall support OA&M procedures which allow the operator to remotely configure the H(e)NB, deploy software upgrades, detect and report changes in RF conditions and perform general OA&M tasks. The OA&M procedures shall be as closely aligned as possible with those that are commonly used in broadband access networks such as defined in TR-069 Amendment 2 [5].
+- If the connection between H(e)NB and the rest of the operator network is out of service, then it shall be possible within an operator's defined time period for the H(e)NB to deactivate the air-interface.
+- When the H(e)NB Hosting Party authentication is required by the MNO, the H(e)NB shall not activate the air-interface unless the authentication of the H(e)NB Hosting Party has been performed successfully.
+
+## 5.3 Access Control requirements
+
+### 5.3.1 General
+
+- Subject to operator and H(e)NB Hosting Party agreement, the operator shall be able to configure the H(e)NB with open, hybrid or closed access mode.
+- When the H(e)NB is configured for open access mode, it shall be possible for the H(e)NB to provide services to subscribers of any PLMN, subject to roaming agreement.
+- When the H(e)NB is configured for hybrid access mode, it shall be possible for the H(e)NB to provide services to:
+ - its associated CSG members, and
+ - subscribers of any PLMN not belonging to its associated CSG, subject to roaming agreement.
+
+- When the H(e)NB is configured for closed access mode, only users that belong to its associated CSG shall be able to obtain services.
+- CSG members may include subscriber of any PLMN subject to roaming agreement, defined as HPLMN CSG Roaming.
+- The VPLMN may support VPLMN Autonomous CSG Roaming by providing CSG membership to the roaming subscriber without exchanging any CSG specific information with the HPLMN. The VPLMN shall disable VPLMN Autonomous CSG Roaming on a per HPLMN basis if requested by the home operator.
+
+NOTE: VPLMN Autonomous CSG Roaming and HPLMN CSG Roaming can be active in the same VPLMN
+
+- The CSG membership granted to the subscriber during his stay in the VPLMN may be retained by the VPLMN (e.g. in case the subscriber moves to another PLMN and subsequently returns to the VPLMN).
+
+### 5.3.2 Closed Subscriber Group
+
+- The CSG manager shall be able, under the operator supervision, to add, remove and view CSG membership
+
+NOTE: the interaction of the user with the application that manages the Allowed CSG Lists is out of scope of 3GPP (e.g. Web interface).
+
+- For each subscriber, the network maintains a single CSG list containing the CSG identities that the subscriber is allowed to use.
+- The UE shall contain a list of allowed CSG identities (Allowed CSG List). It shall be possible to store the Allowed CSG List in the USIM. When available, the list on the USIM shall be used. It shall be possible for both, the operator and the UE, to modify the Allowed CSG List.
+- The UE shall allow the user to introduce new CSGs to the Allowed CSG List by means of manual CSG selection only.
+- The UE shall maintain an operator-controlled list of allowed CSG identities (Operator CSG list). It shall be possible to store the Operator CSG list in the USIM. When available, the list on the USIM shall be used. It shall be possible for the operator to modify the Operator CSG List.
+- The two lists are maintained independently from each other. A change in the Operator CSG list shall not trigger the UE to modify the Allowed CSG list to reflect such change automatically.
+- Except during manual CSG selection, all CSG cells belonging to a CSG identity not included in the Allowed CSG List or Operator CSG list shall be considered not suitable by the UE (“not suitable” as specified in TS 25.304 [6] and TS 36.304 [7]).
+- Each CSG identity shall be associated to a subscriber group which identifies the subscribers allowed to access the CSG.
+- When the subscriber group is updated, the affected UE shall be informed accordingly.
+- For temporary members, it shall be possible to limit the period of time during which the subscriber is considered a member of a CSG (granted access rights). It shall be possible to configure a time period for each temporary member.
+- The time period shall be configurable by the CSG manager and/or the operator operating the CSG and shall span from 1 decihour to several days. Unlimited membership to the CSG is allowed.
+- When a CSG is no longer considered available to provide services, except for emergency calls (i.e. due to time period expiry or removal of the CSG membership), it shall be possible to continue the established communication in another cell not belonging to this CSG.
+- In hybrid access mode when services cannot be provided to a CSG member due to a shortage of H(e)NB resources it shall be possible to continue the established communication of non-CSG members in another cell.
+- In hybrid access mode, to minimise the impact on CSG members from established communication of non-CSG members, it shall be possible for the network to allow the data rate of established PS communication of non-CSG members to be reduced.
+
+## 5.4 Display requirements
+
+### 5.4.1 CSG Type
+
+The CSG Type is an indicator provided by the UE that is configured by the operator.
+
+- It shall be possible for the operator to associate a CSG identity in the UE's Allowed CSG List or the Operator CSG List with a CSG Type. Therefore, it is possible that a CSG identity stored in different UEs may either be associated with the same CSG Type or with different CSG Types.
+
+NOTE: The CSG Type allows, for example, information on the applied billing regime to be given to the user.
+
+- When a UE camps on a cell with a CSG identity that is part of the UE's Allowed CSG List and or the Operator CSG List has an associated CSG Type, a UE that has a display capability shall provide the user with the associated CSG Type. A UE that does not have a display capability may provide the CSG Type by other means, e.g. voice notification.
+- If the CSG Type for a CSG identity has not been configured in the UE, the UE may provide the HNB Name instead. In this case, the user is notified that the UE is providing the HNB Name rather than CSG Type.
+- It shall be possible to store the CSG Type in the USIM. As an option, the CSG Type may be stored in the ME. If the CSG Type is present in the USIM, a CSG Type stored in the ME shall be ignored. If the CSG Type is present in the Operator CSG list, a CSG Type present in the Allowed CSG list shall be ignored.
+- The CSG Type shall be stored in text and/or graphical format. When the CSG Type has a text component, the CSG Type text length shall not exceed 12 characters in any language.
+
+### 5.4.2 HNB Name
+
+HNB Name is a common name referring to HNB/HeNB as defined in TR 21.905 [1].
+
+- It shall be possible for a CSG cell and for a hybrid cell to broadcast a HNB Name in free text format. The UE may display the HNB Name when camping on the cell where it is broadcasted. The HNB Name, if broadcasted or stored in the UE, shall be available to the user during manual CSG selection. The HNB Name shall be configurable by the operator or the H(e)NB Hosting Party at the discretion of the operator.
+- The HNB Name length shall not exceed 48x8 bits.
+
+NOTE 1: In order to allow the maximum flexibility in the way the HNB Name is configured in any language, UTF-8 coding should be used; this allows a maximum length of 48 characters coded on one byte, 24 characters on two bytes, 16 characters on 3 bytes down to a minimum of 12 characters if all characters are encoded on 4 bytes.
+
+- If available and depending on operator preferences a HNB Name may be stored together with the associated CSG Identity in the UE's Operator CSG List.
+- If available and depending on operator preferences a HNB Name may be stored together with the associated CSG Identity in the UE's Allowed CSG List.
+- A HNB Name present in the Operator CSG list shall take precedence over a HNB Name present in the Allowed CSG list, which in turn shall take precedence over the broadcasted HNB Name.
+
+NOTE 2: The UE's Operator CSG List and Allowed CSG List are stored on the USIM or, optionally, in the ME as specified in section 5.3.2.
+
+NOTE 3: The HNB Name is necessary in order to aid the user in choosing the correct CSG identity when performing a manual CSG identity selection.
+
+## 5.5 Mobility Aspects for Home NodeB and Home eNodeB
+
+### 5.5.1 PLMN selection
+
+The standard automatic and manual network selection procedures are used to register a UE on a PLMN via a H(e)NB.
+
+### 5.5.2 Idle-mode operation
+
+In addition to normal cell reselection procedures, the following requirements apply:
+
+- It shall be possible to support idle mode mobility between a H(e)NB cell and other cells and between H(e)NB cells.
+- A UE in idle mode shall prefer to select a cell whose CSG Identity is in the UE's Allowed CSG List or in the Operator CSG list, when the cell reselection criteria has been met.
+
+NOTE: All CSG identities on the Allowed CSG list and the Operator CSG list have the same priority.
+
+- The cell reselection procedure should not result in excessive power consumption in the UE.
+
+### 5.5.3 Connected mode operation
+
+- It shall be possible to support service continuity, including handover, between a H(e)NB cell and other cells and between H(e)NB cells. This includes H(e)NB cells in residential and enterprise environment.
+- For operational and deployment purposes, handovers between a H(e)NB cell and other cells and between H(e)NB cells should not significantly increase mobility related signalling.
+- Data session(s) may be terminated by the network after the UE leaves the H(e)NB coverage area on a per UE basis (e.g. based on subscriber tariff change).
+
+### 5.5.4 Manual CSG selection
+
+The user shall be able to request the UE to perform a scan for available CSGs. When such request is received the UE shall perform a scan of available CSGs, their CSG Identities and their HNB Names. In the UE display, the available CSGs shall be represented by their associated HNB Names and PLMN Name(s). If the HNB Name is not available, the CSG Identity shall be displayed instead.
+
+An indication shall be given to the user as to which of the available CSGs is contained in the Allowed CSG List or Operator CSG list. The available CSGs shall be displayed in the following order:
+
+- The CSGs, whose CSG Identities are contained in the Allowed CSG list.
+- The CSGs, whose CSG Identities are contained in the Operator CSG List.
+- Any other CSG, whose CSG Identity is not included in the Allowed CSG List or the Operator CSG list.
+
+The HPLMN shall configure, on a PLMN basis, the UE to display the available CSGs so that either:
+
+- all CSGs are displayed, or
+- only CSGs in the Operator CSG List are displayed.
+
+NOTE: It is assumed that OMA DM/OTA will be used by the HPLMN to configure the ME/USIM
+
+By default, the UE shall display all available CSGs for any PLMN, unless the UE has been configured by the HPLMN, for a specific PLMN, to display only CSGs in the Operator CSG List that are available.
+
+When the user selects an entry in the list, the UE shall reselect any of the available cells with the CSG chosen by the user.
+
+The UE shall attempt to register to the PLMN.
+
+If the registration attempt is accepted, the UE shall add the CSG identity to the Allowed CSG list unless the cell is a hybrid cell or the identity is already present in the list.
+
+If the registration attempt is accepted and the UE is allowed to add the CSG identity to the Allowed CSG list then the UE may add the broadcasted HNB Name to the Allowed CSG list.
+
+If the registration attempt is rejected and the CSG entry is in the Allowed CSG list, that CSG and the associated HNB Name shall be removed from the Allowed CSG list.
+
+In addition, when the user manually selects a CSG in a PLMN, which is different from the last registered PLMN, the following behaviour applies:
+
+- The UE shall enter into Manual PLMN Selection state.
+- The UE shall attempt to register to the PLMN. This PLMN shall not be stored as the Last Registered PLMN.
+- When the UE is no longer in the service area of the CSG the UE shall return to the previous PLMN Selection state.
+
+## 5.6 Services support
+
+### 5.6.1 General
+
+- Subject to availability of network resources there shall be no difference in the user experience when using the PLMN provided services via H(e)NB or via NodeB/eNodeB (NB/eNB).
+- Depending on operator preferences and in compliance with regulatory requirements ETWS and PWS [9] shall be supported.
+- Any additional registration and paging load as a result of H(e)NB deployment shall be minimized.
+- Deployment of H(e)NBs and NB/eNBs on the same spectrum should not degrade the performance of UEs receiving service from NB/eNBs.
+- Deployment of H(e)NBs and NB/eNBs on the same spectrum should not degrade the NB/eNB's coverage and capacity.
+
+### 5.6.2 Emergency services
+
+- Subject to local regulatory requirements, H(e)NB shall support emergency calls, as specified in TS 22.101 [4].
+- It shall be possible for the operator to provide location information of the UE attempting an emergency call over a H(e)NB. The location information shall be sufficiently accurate to comply with the regulatory requirements that apply to the area where the H(e)NB is deployed.
+
+### 5.6.3 IMS Interworking
+
+- The operator can provide CS-to-IMS interworking as specified in the IMS Centralized Services clause of TS 22.101 [4].
+
+## 5.7 Local IP Access (LIPA)
+
+### 5.7.1 Description
+
+Local IP Access provides access for IP capable UEs connected via a H(e)NB (i.e. using H(e)NB radio access) to other IP capable entities in the same residential/enterprise IP network. Data traffic for Local IP Access is expected to not traverse the mobile operator's network except mobile operator network components in the residential/enterprise premises. Signaling traffic will continue to traverse the mobile operator network. The residential/enterprise IP network itself and the entities within that network are not within the scope of 3GPP standardisation.
+
+NOTE: It is not precluded that a small amount of data traffic for Local IP Access (e.g. user packets that trigger paging) be forwarded via the mobile operator's network, provided there is a trust relationship between the H(e)NB hosting party and the mobile operator.
+
+
+
+The diagram illustrates the LIPA architecture within a residential/enterprise premises (represented by a house). Inside, a UE (User Equipment) is connected to an H(e)NB. The H(e)NB is connected to the Mobile operator's core network (represented by a cloud) via a logical connection for mobile operator IP traffic (blue double arrow). The H(e)NB is also connected to the Residential/enterprise IP Network (represented by a green cloud containing a printer, computer, and monitor) via a logical connection for Local IP access (yellow double arrow). The UE is shown sending IP traffic to the mobile operator's CN and receiving Local IP traffic from the Residential/enterprise IP Network.
+
+Legend:
+
+- logical connection for mobile operator IP traffic (blue double arrow)
+- scope of Local IP access (yellow double arrow)
+
+Diagram illustrating Local IP Access (LIPA) architecture. A house represents the residential/enterprise premises. Inside, a UE (User Equipment) is connected to an H(e)NB. The H(e)NB is connected to the Mobile operator's core network (represented by a cloud) via a logical connection for mobile operator IP traffic (blue double arrow). The H(e)NB is also connected to the Residential/enterprise IP Network (represented by a green cloud containing a printer, computer, and monitor) via a logical connection for Local IP access (yellow double arrow). The UE is shown sending IP traffic to the mobile operator's CN and receiving Local IP traffic from the Residential/enterprise IP Network.
+
+### 5.7.2 General requirements
+
+A H(e)NB subsystem shall be able to support Local IP Access in order to provide access for IP capable UEs connected via a H(e)NB subsystem (i.e. using H(e)NB radio access) to other IP capable entities in the same residential/enterprise IP network.
+
+- Simultaneous access from a UE to the mobile operator's core network (e.g. internet, PLMN services) and Local IP Access to a residential/enterprise IP network shall be supported.
+- Subject to regulatory requirements, Local IP Access traffic shall be routable only between the UE, H(e)NB and other entities within the residential/enterprise IP network.
+- A UE shall have a valid subscription with the mobile operator in order to use Local IP Access.
+
+- A UE shall be able to use Local IP Access in a visited network subject to roaming agreement between mobile operators.
+- The HPLMN shall be able to enable/disable LIPA usage when the UE roams to particular VPLMNs.
+- Local IP Access shall not affect services running in parallel for the same UE.
+- Pre-Rel 10 UEs should be able to use Local IP Access.
+- The user may be notified when a H(e)NB provides access to a residential/enterprise IP network
+- A UE using Local IP Access shall be contactable by another IP endpoint in the same residential/enterprise IP network via Local IP Access.
+- The operator shall be able to configure the network to support connection request from a UE so that a LIPA connection is used when the UE is located within the residential/enterprise IP network, and a regular connection via the Core Network is used otherwise.
+- It shall be possible for a UE to maintain its IP connectivity to the residential/enterprise IP network when moving between H(e)NBs within the same residential/enterprise IP network. Any interruption to this IP connectivity shall be limited to levels comparable to that of the IP connectivity for PLMN services.
+
+NOTE: Loss of access to the residential/enterprise IP network is acceptable as a UE moves out of H(e)NB coverage.
+
+- The mobile operator shall be able to configure the H(e)NB to enable/disable Local IP Access.
+- The mobile operator shall be able to enable/disable Local IP Access per user subscription per CSG.
+- The H(e)NB Hosting Party, within the limits set by the mobile operator, shall be able enable/disable Local IP Access per H(e)NB.
+- The H(e)NB subsystem shall allow the mobile operator to make traffic and signalling performance measurements related to Local IP Access for each user and for the H(e)NB.
+- The H(e)NB subsystem shall allow the mobile operator to collect fault management information related to Local IP Access for each H(e)NB.
+
+NOTE: It is possible for the H(e)NB Hosting Party to use additional access control mechanisms (e.g. using a password) to restrict access of UEs to the residential/corporate IP network. However, such additional access control is out of scope of 3GPP standardisation.
+
+- Local IP Access shall not compromise the security of the mobile operator's network.
+
+## 5.8 Managed Remote Access to home based network
+
+- The H(e)NB may support remote access for a CSG member to the home based network from a UE via a PLMN in order to provide access to IP capable devices connected to the home based network.
+- It shall be possible to restrict the access to the home based network on per-subscriber basis (e.g. some subscribers may have managed access to their home network and others may not).
+
+## 5.9 Selected IP Traffic Offload (SIPTO) at Local Networks
+
+It shall be possible that a H(e)NB SubSystem supports Selected IP Traffic Offload to provide access for a UE connected via a H(e)NB (i.e. using H(e)NB radio access) to a defined IP network (e.g. the Internet). The following requirements apply to the H(e)NB SubSystem to support Selected IP Traffic Offload at the local residential/enterprise IP network:
+
+- Selected IP Traffic Offload shall be possible to be done without traversing the mobile operator network, subject to regulatory requirements.
+- The mobile operator and the H(e)NB Hosting Party, within the limits set by the mobile operator, shall be able to enable/disable Selected IP Traffic Offload per H(e)NB.
+
+- Based on mobile operator SIPTO policies and configured user consent per APN, the network shall be able to offload traffic.
+
+Note: There is a possibility that the user's service experience will be different if the user's traffic is offloaded via SIPTO at local residential/enterprise IP networks.
+
+- The SIPTO policies may be defined per APN or per IP flow:
+ - SIPTO policies per APN indicate whether all traffic associated with a specific APN is subject to offload;
+ - SIPTO policies per IP flow are routing policies indicating which APN to use for a specific IP flow. The Operator may provide routing policies to the UE that assist the UE in routing the IP flows towards an appropriate APN. This is applicable for UE regardless of whether or not it has established IP connectivity to the local enterprise/residential network.
+- The mobile operator shall be able to configure the SIPTO policies either statically or dynamically.
+- Simultaneous connectivity from the UE to the mobile operator's core network and to a defined IP network (e.g. the Internet) via a fixed residential/enterprise IP network using SIPTO shall be supported.
+- Simultaneous access from the UE to PLMN services and to fixed services via a fixed residential/enterprise IP network using SIPTO shall be supported.
+
+Requirements that are common with Selected IP Traffic Offload in the mobile operator network can be found in section 4.3.5 in [4].
+
+## 5.10 UICC and H(e)NB
+
+Optionally, the H(e)NB may support identification and authentication of the H(e)NB Hosting Party by means of a UICC-based application.
+
+This application may also contain information for the initial provisioning (e.g. the O&M system contact).
+
+If the H(e)NB supports the H(e)NB Hosting Party application,
+
+- The H(e)NB shall support the use of the operator's UICC application management platform to configure the Hosting Party application.
+- The UICC application shall be able to acquire the geographical location of the H(e)NB.
+
+Note: UICC application management is specified in 3GPP TS 31.115 [11] and 3GPP TS 31.116 [12].
+
+## 5.11 Void
+
+### 5.11.1 Void
+
+### 5.11.2 Void
+
+# --- 6 Requirements for Home NodeB
+
+## 6.1 Access Control
+
+- It shall be possible to control access (i.e. accept and reject connection requests) of pre-Release 8 UEs.
+
+NOTE: Such mechanisms may be different for those used to access control a Release 8 UE.
+
+- The operation of a HNB shall not adversely impact the performances of a pre-Release 8 UEs operating in the area where the HNB is active and vice versa.
+
+- The total bandwidth from the HNB towards the network for 4 simultaneous TS11 or TS12, including signalling and overhead, shall not exceed 200 kbps
+
+## 6.2 Void ---
+
+# 7 Requirements for Home eNodeB
+
+## 7.1 Services support
+
+### 7.1.1 Void ---
+
+# 8 Quality of Service
+
+## 8.1 General
+
+- Subject to agreement between the mobile operator and the broadband access provider, it shall be possible to request resources from the broadband IP backhaul for the QoS treatment for sessions traversing the H(e)NB subsystem.
+
+## 8.2 Admission Control
+
+- The network shall be able to perform admission control based on the available H(e)NB backhaul resource.
+ - The network shall be able to set different criteria for admission. The network control in a hybrid cell for CSG and non-CSG members.
+-
+
+# 9 Security and privacy
+
+## 9.1 General
+
+- The use of H(e)NB shall not compromise the security of any PLMN or broadband access network.
+
+## 9.2 Security Requirements
+
+- The H(e)NB shall provide a high level of security, equivalent or better than Rel-8 3GPP systems.
+- Security policy shall be under the control of the H(e)NB network operator.
+- The H(e)NB shall not impact the security of the UE.
+
+## 9.3 Privacy
+
+- The H(e)NB shall not compromise user privacy for UEs that are using the H(e)NB, including communication confidentiality, location privacy and identity protection.
+
+# --- 10 Charging Aspects
+
+NOTE: Refer to charging requirements in TS 22.115 [8]
+
+# --- Annex A (informative): Use cases
+
+These use cases do not imply any requirement beyond that which is contained in the normative part of this TS.
+
+## **Use case-1: H(e)NB Mobility**
+
+User A connects to the H(e)NB via mobile device. User A should be able to move around within the H(e)NB coverage in the home or enterprise. User should also be able to invoke additional services based on user policy and operator policy.
+
+## **Use case-2: H(e)NB Guest Users**
+
+User A and User B are subscribers of Operator 1 and Operator 2 respectively. User A visits User B in his home and User B allows User A to use H(e)NB in User B's home. User A should be able to access all the services he is subscribed to from Operator 1 based on the policies set by User B and operator 2. Operator 1 and Operator 2 have roaming agreement.
+
+## **Use case-3: HNB/HeNB – NB/eNB Handovers**
+
+User A subscribes to cellular services of Operator 1 and is authorised to access a HNB/HeNB from same or other operator. User A starts service in the H(e)NB coverage and continues moving into a cellular network. Similarly User A starts service in cellular network and continues moving into H(e)NB coverage. User A does not see any impact on services due to mobility in both cases.
+
+## **Use case-4: Access to Home based services**
+
+User A connects to the H(e)NB via mobile device. User A should be able to access home based services (e.g. local digital media servers and digital media players) from the mobile device. Other users may access the home based services subject to H(e)NB Hosting Party policies.
+
+## **Use case-5: Media Transfer**
+
+User A connects to the H(e)NB via mobile device. User A starts viewing video streaming service on the mobile device. User A then wants to continue viewing the video on a different screen for better viewing. User A should be able to transfer the session to a high-definition TV or PC connected via broadband connection. User A should also be able to transfer the session from the TV or PC to a mobile device and continue the session in the H(e)NB coverage and also in the cellular network.
+
+## **Use case-6: IMS capable HNB used for coverage purposes**
+
+In this scenario, the reason for an operator to introduce IMS capable HNB is to offload voice traffic from his existing CS core network to IMS. However, as in this scenario the usage of 'legacy' services (e.g. CS Fax) is still assumed - only the utilization of network resources is to be changed - it is requested that IMS capable HNB provides all the services/ capabilities that are provided through regular Node B from the beginning.
+
+## **Use case-7: IMS capable HNB for a new business model**
+
+This scenario starts with a view that HNB is located in the user's residence and the UE is the preferred equipment to interact with home services/ applications. New business can be expected there. In this scenario, some of the CS services/ capabilities that are provided through regular Node B might not be
+
+needed or might be provided in a later step if the operator could instead offer attractive new services under IMS capable HNB only.
+
+## **Use case-8: IMS capable HNB for Green field operator**
+
+This scenario expects new players to get into the mobile market. In this scenario, they would aim to deploy cost efficient and future proof infrastructure, i.e. no CS domain but IMS/PS domain only, regardless of whether or not UEs have IMS client on them.
+
+### **Use case-9: Hybrid access mode**
+
+In order to improve the coverage in a shopping mall, H(e)NBs are deployed. The shopping mall owner may have been provided a special deal by the network operator where the employees of the shopping mall will get preferential charging rates and priority access when accessing services via these H(e)NBs. In exchange, the shopping mall owner allows the public to use the H(e)NBs to access the normal network operator services. The H(e)NB Hosting Party should not need to manage the public access and the public should not need to do anything special in order to get services on the H(e)NB.
+
+## **Use case-10: Open access mode**
+
+Typically to enhance coverage or capacity of an operator's public network, for example in railway stations, airports, stadiums, etc, taking benefit of the H(e)NBs additional functionality (e.g. uncoordinated deployment).
+
+## **Use case-11: HNB interacts with Home network**
+
+User A connects with his UE (possibly a pre-Rel 9 UE) to the HNB with IMS Interworking and Local IP Access to the home network capabilities. The home network accommodates home network devices (Intercom, Door lock, Network radio, Photo server, etc.) and the HNB. User A should be able to communicate with a visitor at Intercom via the mobile device.
+
+## **Use case-12: HNB interacts with IP-PABX**
+
+User A connects with his UE (possibly a pre-Rel 9 UE) to a HNB with IMS Interworking and Local IP Access to the home network capabilities at an office. The HNB might be deployed and interconnect with an enterprise extension telephone system (e.g. SIP based PABX). User A should be able to make/receive an extension call to/from fixed line UE under SIP based PABX. In addition, User A with the mobile device and User B with computers should be able to access a common groupware server at the office and share the same information such as schedule, emails, etc.
+
+## **Use case-13: Electronic customer guide in shopping centre, using Local IP access**
+
+A department store or shopping centre provides electronic shopping guide. When user A enters into a shopping centre where a shopping centre H(e)NB is installed, an invitation indication shows up on his mobile device which he accepts. This allows him access to the centre's H(e)NB. Subsequently, he accesses the centre's customer service server, which is only accessible through the H(e)NB where he uploads his shopping list. The customer service server responds a list of sale items of similar nature. He accepts or declines the various choices and the final shopping list is downloaded to his UE. While user A is waiting, User A watches free TV show or advertisement provided through the H(e)NB for the shop customer. While in the shopping centre the user has simultaneous access to operator's and local shopping centre services.
+
+## **Use case-14: Local IP Access**
+
+The user has the subscription through home operator H. The user is served by the home operator H. The UE obtains IP connectivity in both a local gateway to obtain local connectivity for IMS services (e.g. as in local IP access or for enterprise scenarios with call to other terminals in the PABX area) and to a home gateway (as in normal connectivity for IMS services). For IMS sessions to be routed to e.g. remote terminals, the traffic is sent through the connectivity with the home gateway, whereas for IMS session that can be routed locally (e.g. based on local phone number), the traffic is sent through the connectivity with the local gateway through the local IP access. Whether the UE routes a specific IMS session through the local access or the home gateway can be controlled on a per session basis. Also, the UE may obtain local connectivity by default (e.g. based on static configuration by the operator) or dynamically based on indication by the IMS server.
+
+## **Use case-15:**
+
+Subscriber A from Network A owns HNB/HeNB A because of no macro network coverage .
+Guest user B from Network B visits subscriber A's house. Subscriber A wants to allow guest user B access to HNB/HeNB A while the guest user B is visiting.
+
+## **Use case-16:**
+
+Corporation A has sites in country A, B and C.
+Corporation A has employees from country A and B.
+Employees in country A are from Operator AA and AB.
+Employees in country B are from Operator B.
+Corporation A has HNB/HeNB in country A from Operator AA and country B from Operator B.
+Employees from country A and B are allowed access to HNB/HeNBs in country A and B.
+
+## **Use case-17: Content-sharing services in the residential IP network**
+
+During a trip to the zoo Alice has taken several pictures and has recorded a video clip on her UE. After returning home her UE connects to the H(e)NB in the home and accesses the residential IP network. The local devices (video, printer, ..) are automatically discovered by the UE. Alice views the videos on her video player, prints photos on her printer, uploads her media onto media server, and downloads media for her next outing.
+
+# Annex B (informative): Clarification of H(e)NB Access Modes
+
+Table B.1 illustrates the different H(e)NB Access Modes and what access is allowed for UEs of any release depending on whether the UE is allowed access to the CSG.
+
+In Table B.1 “Access” means “Access to services”.
+
+“Preferential access” means the user will get preferential access to the cell.
+
+**Table B.1: H(e)NB access for UEs of any release**
+
+| | H(e)NB Access Mode | | |
+|------------------------------|--------------------|-----------|---------------------|
+| | Open | Closed | Hybrid |
+| UE allowed access to CSG | Access | Access | Preferential Access |
+| UE not allowed access to CSG | Access | No Access | Access |
+
+NOTE: Pre Release 8 UEs can only access HNBs
+
+# Annex C (informative): Overview of identifiers and names.
+
+**Table C.1: Overview of identifiers and names**
+
+| item | used for | associated with | permanently stored in | distribution method | displayed to user | comment |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| H(e)NB equipment identity | | H(e)NB (physical entity) | - H(e)NB
- administration database of the operator
| O&M procedures | NO | not known to UE, therefore not useable by UE to identify a H(e)NB |
+| CSG identity | - automatic and manual CSG selection
- access control to CSG cells
| - a CSG, i.e. a group of users (UEs).
- One or More H(e)NBs (CSG cells)
| - H(e)NB
- administration database of the operator
- Allowed CSG List in the UE if user (UE) is member of CSG (USIM entry takes precedence over ME)
| - provided by O&M to H(e)NBs
- provided by home PLMN to UEs (the Home PLMN and Visited PLMN should synchronize this information )
- Provided to the UE by OMA DM when stored in the ME,
- Provided to the UE by OTA when stored in the USIM
- Provided to UE via manual CSG
| YES, if HNB Name is not available | A CSG identity is unique within a PLMN. In the UE a CSG ID, together with a network identifier, identifies a CSG globally uniquely. |
+
+| | | | | | | |
+|---------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | selection | | |
+| HNB name (optional) | for supporting (ease of use) manual CSG selection, displaying a “friendly” name to the user | CSG identity (relationship: m CSG ID : n HNB names) | - • H(e)NB
- • administration database of the operator
- • UE
| - • Provided by O&M to H(e)NBs
- • Optionally stored by user in UE
- • broadcasted by H(e)NB
| YES during manual selection, OPTIONAL during normal operation.
(USIM entry takes precedence over broadcast and ME) | If a HNB name is stored in the UE it needs to be associated with a CSG identity. Initial configuration in the UE may be done by the operator (e.g. at point of sale). Later, a HNB name is implicitly associated to the current CSG identity by the UE when the user stores the HNB name |
+| CSG Type | for additional information (on e.g. billing mode) to the user when camping on a CSG cell (i.e. after CSG has been selected) | CSG identity (relationship: n CSG ID : 1 CSG Type) | - • administration database of the operator
- • UE
| - • provided by initial UE configuration, OTA and device management to UEs
| YES, if CSG is in Allowed CSG List. (USIM entry takes precedence over ME) | UE needs to associate a CSG Type with a CSG identity
Association done by operator (the Home PLMN and Visited PLMN should synchronize this information ) |
+
+# Annex D (informative): Change history
+
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+|---------|-----------|------------|--------|------|-----|--------|-----|----------------------------------------------------------------------------------|--------|--------|-------------|
+| SP-43 | SP-090087 | - | 22.220 | - | - | - | - | Approved by SA plenary. | 2.0.0 | 9.0.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091273 | 22.220 | 0002 | 1 | Rel-9 | F | Clarification on the displaying of the H(e)NB name during manual CSG selection | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091164 | 22.220 | 0004 | 4 | Rel-9 | B | Optional USIM support in H(e)NB | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091387 | 22.220 | 0011 | 3 | Rel-9 | F | Clarification on Local IP Access Requirements | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091083 | 22.220 | 0015 | - | Rel-9 | F | Remove VPLMN CSG support for Rel9 | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091382 | 22.220 | 0016 | 2 | Rel-9 | F | Clarification on the requirement of session diversion. | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091279 | 22.220 | 0019 | 2 | Rel-9 | F | Allowed CSG list management for hybrid cells | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091158 | 22.220 | 0023 | 3 | Rel-9 | D | Clarification of H(e)NB Owner / Hosting Party | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091159 | 22.220 | 0024 | 2 | Rel-9 | D | H(e)NB Operator Change | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091383 | 22.220 | 0025 | 2 | Rel-9 | F | Clarification of the terminology about H(e)NB access modes | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090373 | S1-091274 | 22.220 | 0026 | 1 | Rel-9 | F | Minor corrections for clarification | 9.0.0 | 9.1.0 | EHLNB |
+| SP-44 | SP-090374 | S1-091260 | 22.220 | 0005 | 1 | Rel-9 | F | Rel 8 Rel 9 CSG lists alignment (approved at SA#44 but not implemented in 9.1.0) | 9.1.0 | 9.1.1 | EHLNB |
+| SP-45 | SP-090477 | S1-093332 | 22.220 | 0032 | 2 | Rel-9 | F | CSG Lists clarification | 9.1.1 | 9.2.0 | EHLNB |
+| SP-45 | SP-090477 | S1-093329 | 22.220 | 0035 | 1 | Rel-9 | F | IP access approach of backhaul network for H(e)NB | 9.1.1 | 9.2.0 | EHLNB |
+| SP-45 | SP-090477 | S1-093331 | 22.220 | 0037 | 1 | Rel-9 | D | Editorial corrections of TS 22.220 | 9.1.1 | 9.2.0 | EHLNB |
+| SP-45 | SP-090477 | S1-093480 | 22.220 | 0039 | 2 | Rel-9 | C | Loss of IP Backhaul Connection | 9.1.1 | 9.2.0 | EHLNB |
+| SP-45 | SP-090477 | S1-093330 | 22.220 | 0041 | 1 | Rel-9 | F | Clarification of definition for H(e)NB Hosting Party | 9.1.1 | 9.2.0 | EHLNB |
+| SP-45 | SP-090483 | S1-093477 | 22.220 | 0038 | 4 | Rel-10 | F | CR to 22.220 on Clarification of QoS Requirements | 9.1.1 | 10.0.0 | TEI 10 |
+| SP-46 | SP-090839 | S1-094318 | 22.220 | 0057 | 1 | Rel-10 | A | Simplified CSG list handling | 10.0.0 | 10.1.0 | EHLNB |
+| SP-46 | SP-090845 | S1-094323 | 22.220 | 0067 | 2 | Rel-10 | B | H(e)NB mobility related load optimization | 10.0.0 | 10.1.0 | EHNBF |
+| SP-46 | SP-090845 | S1-094380 | 22.220 | 0063 | 3 | Rel-10 | B | Requirements on HNBs in enterprise environments | 10.0.0 | 10.1.0 | EHNBF |
+| SP-46 | SP-090849 | S1-094328 | 22.220 | 0046 | 3 | Rel-10 | B | Local IP Access requirements update | 10.0.0 | 10.1.0 | LIPA_SIP TO |
+| SP-46 | SP-090849 | S1-094321 | 22.220 | 0047 | 2 | Rel-10 | B | Selected IP Traffic Offload Requirements for H(e)NB SubSystem | 10.0.0 | 10.1.0 | LIPA_SIP TO |
+| SP-46 | SP-090849 | S1-094429 | 22.220 | 0062 | 1 | Rel-10 | B | Use case for digital content sharing with LIPA | 10.0.0 | 10.1.0 | EHNBF |
+| SP-47 | SP-100186 | S1-100331 | 22.220 | 0072 | 1 | Rel-10 | B | Termination of data session | 10.1.0 | 10.2.0 | EHNBF |
+| SP-47 | SP-100186 | S1-100328 | 22.220 | 0080 | 1 | Rel-10 | F | IMS HNB interworking alignment with SA2 decision | 10.1.0 | 10.2.0 | EHNBF |
+| SP-47 | SP-100186 | S1-100453 | 22.220 | 0092 | 3 | Rel-10 | B | Add VPLMN CSG support for Rel-10 | 10.1.0 | 10.2.0 | EHLNB |
+| SP-47 | SP-100230 | S1-100324r | 22.220 | 0094 | 1 | Rel-10 | A | Clarification of the interaction of the Operator and Allowed CSG lists | 10.1.0 | 10.2.0 | EHLNB |
+| SP-47 | SP-100187 | S1-100316 | 22.220 | 0070 | 1 | Rel-10 | B | Mobility for Local IP Access (LIPA) | 10.1.0 | 10.2.0 | LIPA_SIP TO |
+| SP-47 | SP-100187 | S1-100012 | 22.220 | 0071 | - | Rel-10 | F | Removal of SIPTO common requirements | 10.1.0 | 10.2.0 | LIPA_SIP TO |
+| SP-47 | SP-100187 | S1-100326 | 22.220 | 0082 | 3 | Rel-10 | B | Clarification of requirements for LIPA | 10.1.0 | 10.2.0 | LIPA_SIP TO |
+| SP-47 | SP-100188 | S1-100025 | 22.220 | 0073 | - | Rel-10 | A | H(e)NB Hosting Party USIM management | 10.1.0 | 10.2.0 | TEI-10 |
+| SP-48 | SP-100402 | S1-101248 | 22.220 | 0100 | 3 | Rel-10 | F | Enable/disable Selected IP Traffic Offload per H(e)NB | 10.2.0 | 10.3.0 | LIPA_SIP TO |
+| SP-48 | SP-100399 | S1-101250 | 22.220 | 0101 | 4 | Rel-10 | F | Clarification of the CSG list in | 10.2.0 | 10.3.0 | EHNBF |
+
+| | | | | | | | | | | | |
+|---------|-----------|------------|--------|------|---|--------|---|----------------------------------------------------------------------------------------------------|--------|--------|-------------|
+| | | | | | | | | networks, Operator CSG list (OCL) and Allowed CSG list (ACL) | | | |
+| SP-49 | SP-100573 | S1-102388 | 22.220 | 0110 | 4 | Rel-10 | F | Removal of requirement to inhibit Allowed CSG List and VPLMN Autonomous CSG Roaming clarifications | 10.3.0 | 10.4.0 | EHNBF |
+| SP-49 | SP-100576 | S1-102399 | 22.220 | 0106 | 3 | Rel-10 | F | Correction on HNB Name | 10.3.0 | 10.4.0 | EHNBF |
+| SP-49 | SP-100576 | S1-102404 | 22.220 | 0107 | 4 | Rel-10 | F | Clarification of LIPA requirements | 10.3.0 | 10.4.0 | EHNBF |
+| SP-49 | SP-100578 | S1-102197 | 22.220 | 0105 | 3 | Rel-10 | F | SIPTO for H(e)NB Subsystems Policy and User Interaction | 10.3.0 | 10.4.0 | LIPA_SIP TO |
+| SP-49 | SP-100578 | S1-102400 | 22.220 | 0104 | 3 | Rel-10 | F | Enablement/disablement policies for LIPA | 10.3.0 | 10.4.0 | LIPA_SIP TO |
+| SP-50 | SP-100796 | S1-103277 | 22.220 | 0117 | 1 | Rel-10 | F | Requirement on conditional LIPA | 10.4.0 | 10.5.0 | LIPA_SIP TO |
+| SP-50 | SP-100796 | S1-103348 | 22.220 | 0118 | 3 | Rel-10 | F | Clarification on "enable/disable LIPA" | 10.4.0 | 10.5.0 | LIPA_SIP TO |
+| SP-51 | SP-110161 | S1-110183 | 22.220 | 0123 | 2 | Rel-11 | A | Hosting Party Identity Module | 11.0.0 | 11.1.0 | TEI9 |
+| SP-51 | SP-110172 | S1-110178 | 22.220 | 0119 | 3 | Rel-11 | B | New Requirements for Enterprise Interworking scenario | 11.0.0 | 11.1.0 | TEI 11 |
+| SP-52 | SP-110368 | S1-111403 | 22.220 | 0133 | 1 | Rel-11 | A | Correction to the admission control for the H(e)NB | 11.1.0 | 11.2.0 | TEI11 |
+| SP-52 | SP-110369 | S1-111432 | 22.220 | 0129 | 1 | Rel-11 | A | Removal of PBX integration requirements | 11.1.0 | 11.2.0 | EHNBF |
+| SP-52 | SP-110376 | S1-111126 | 22.220 | 0134 | - | Rel-11 | F | Clarification for SIPTO policy | 11.1.0 | 11.2.0 | TEI11 |
+| SP-53 | SP-110582 | S1-112387 | 22.220 | 0142 | 1 | Rel-11 | F | Clarification for SIPTO user consent | 11.2.0 | 11.3.0 | TEI11 |
+| SP-53 | SP-110582 | S1-112394 | 22.220 | 0136 | 1 | Rel-11 | F | SIPTO for the Local Residential/Enterprise Networks | 11.2.0 | 11.3.0 | TEI11 |
+| SP-53 | SP-110582 | S1-112395 | 22.220 | 0140 | 2 | Rel-11 | F | H(e)NB behaviour in case of absence of the UICC | 11.2.0 | 11.3.0 | TEI11 |
+| SP-53 | SP-110582 | S1-112396 | 22.220 | 0137 | 3 | Rel-11 | B | Allow the H(e)NB UICC application to acquire location Information | 11.2.0 | 11.3.0 | TEI11 |
+| SP-54 | SP-110871 | S1-113415r | 22.220 | 0147 | 2 | Rel-11 | A | H(e)NB emergency call support | 11.3.0 | 11.4.0 | EHNB |
+| SP-54 | SP-110808 | S1-113458 | 22.220 | 0149 | 1 | Rel-11 | A | MBMS not supported for HeNB | 11.3.0 | 11.4.0 | EHNB |
+| SP-57 | SP-120520 | S1-122477 | 22.220 | 0156 | 3 | Rel-11 | A | Optional UICC authentication | 11.5.0 | 11.6.0 | TEI9 |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.6.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2019-07 | - | - | - | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|-----------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-07 | SA#88e | - | - | - | - | Updated to Rel-16 by MCC | 16.0.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22226/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22226/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b3fed1595d9a089c213e2be90e44e0530226755
--- /dev/null
+++ b/marked/Rel-18/22_series/22226/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad15b18d2a6b1aa45183427c109e5fd0ac510654cece5ee620862536260c7c1e
+size 8248
diff --git a/marked/Rel-18/22_series/22226/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22226/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12d227f2b5edcf5190e2e0ef0375a85017a2376e
--- /dev/null
+++ b/marked/Rel-18/22_series/22226/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:008400560f83d3976ca3e24768311133773a26ceb54579861acfadf208845f13
+size 6788
diff --git a/marked/Rel-18/22_series/22226/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/Rel-18/22_series/22226/aa81b9b80bd1e3d723922b3a033564a2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..096a877e1952697264569154c6d02f752087cb0c
--- /dev/null
+++ b/marked/Rel-18/22_series/22226/aa81b9b80bd1e3d723922b3a033564a2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59c300a951028e96f3800453209a61648ad3b6ae6cea822e95b6b503af2f763d
+size 72692
diff --git a/marked/Rel-18/22_series/22226/raw.md b/marked/Rel-18/22_series/22226/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d478af6a37ad040029b4ce6d39290027ec5c0ca2
--- /dev/null
+++ b/marked/Rel-18/22_series/22226/raw.md
@@ -0,0 +1,661 @@
+
+
+# 3GPP TS 22.226 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Global Text Telephony (GTT); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon at its base, and a 'TM' trademark symbol is located to the upper right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## Keywords
+
+---
+
+LTE, UMTS, telephony, text, stage 1
+
+## **3GPP**
+
+## Postal address
+
+## --- 3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|----------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 High level Requirements..... | 7 |
+| 5 General Requirements..... | 8 |
+| 5.1 Text conversation host environments..... | 8 |
+| 5.2 Text conversation management..... | 8 |
+| 5.3 Registration of text conversation capabilities ..... | 8 |
+| 5.4 Session control ..... | 8 |
+| 5.5 Invoking text conversation..... | 8 |
+| 5.6 Text conversation handling during calls ..... | 9 |
+| 5.7 Alerting..... | 9 |
+| 5.8 Addressing..... | 9 |
+| 5.9 Roaming ..... | 10 |
+| 6 Security and reliability ..... | 10 |
+| 7 Charging..... | 10 |
+| 8 External Interfaces ..... | 10 |
+| 8.1 External interfaces in the terminal ..... | 10 |
+| 8.2 External interfaces to other networks..... | 10 |
+| 9 Interworking..... | 11 |
+| 10 Additional services..... | 11 |
+| 10.1 Emergency services..... | 11 |
+| 10.2 Relay services..... | 12 |
+| 11 Network implementation considerations ..... | 12 |
+| Annex A (informative): Background..... | 13 |
+| A.1 Total Conversation ..... | 13 |
+| A.2 Interworking ..... | 13 |
+| A.3 Additional services..... | 14 |
+| Annex B (informative): Initial requirements..... | 15 |
+| B.1 Transmission Performance..... | 15 |
+| B.2 Man Machine Interface (MMI) ..... | 16 |
+| B.3 Compatibility..... | 16 |
+| B.4 Complexity of Implementation and Roll Out..... | 17 |
+| B.5 Referenced consumer requirements ..... | 18 |
+| Annex C (informative): Change history..... | 19 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+Real time, character by character text conversation is a component that increases usability in a conversational session.
+
+Global Text Telephony is a feature that adds the capability to use a text conversation component in a session. It is called Global Text or GTT here.
+
+Interworking with corresponding features in other networks is an important part of Global Text. Specifically, the different kinds of PSTN text telephone systems supported by the international text telephone modem standard ITU-T V.18 are included in the modes for interworking.
+
+One important reason to offer the Global Text feature is to enable emergency service access to people who are depending on a written dialogue.
+
+A more elaborated background is found in Annex A, and requirements in Annex B.
+
+Figure 1 gives an overview of the user environment for Global Text.
+
+
+
+Figure 1: Global Text service environment. The diagram illustrates the network architecture for the Global Text service. A central 'GTTFE' (Global Text Telephone Feature) is shown as a large grey oval containing two 'Cellular Network' clouds. Inside the cellular networks are 'Mobile, text capable terminals' (represented by a mobile phone and a laptop). The cellular networks are connected to a 'Fixed Network' cloud. The 'Fixed Network' is connected to a 'Fixed textphone user' (represented by a desktop computer and a textphone) and a 'Fixed multimedia user' (represented by a desktop computer). The 'Fixed Network' is also connected to an 'IP network' cloud. The 'IP network' is connected to an 'IP textphone or multimedia user' (represented by a desktop computer and a server). Arrows indicate the flow of text and multimedia data between the users and the networks.
+
+Figure 1. Global Text service environment
+
+# 1 Scope
+
+This Technical Specification defines the stage one description of the Global Text Telephone Feature, GTT.. Stage one is the set of requirements which shall be supported for the provision of the real-time text conversation feature, seen primarily from the subscriber's and service providers' points of view.
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the Global Text Telephony feature, which are sufficient to provide a complete feature to incorporate in conversational services.
+
+This TS defines the requirements for GTT to be understood as a framework to enable real-time transmission of text, for the purpose of a text based or text supported conversation between users. Text may be transported alone or in combination with other media in the session, especially video and voice.
+
+Thus the GTT enables text conversation to be included in any mobile conversational service.
+
+Interworking with existing text telephony in PSTN as well as emerging forms of standardised text conversation in all networks is within the scope of this document. Interoperation with Multimedia Messaging Services is also within scope of this feature.
+
+Note: The Global Text Telephony feature may be enhanced due to e.g. operator's or regulator's requirements, however such additional functionality shall not compromise conformance to the core requirements documented in this TS.
+
+# 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 TS 22.101: "Service Principles".
+- [2] ETSI ETR 333; Text Telephony; User requirements and Recommendations
+- [3] ITU-T H.248 Annex F Facsimile, Text conversation and call discrimination packages (2000)
+- [4] ITU-T Recommendation T.140 (1998) – Text conversation protocol for multimedia application. With amendment 1 (2000).
+- [5] ITU-T Recommendation F.700 (2000) – Framework recommendation for audiovisual/multimedia services.
+- [6] ITU-T Recommendation V.18 (2000) – Operational and interworking requirements for DCE:s operating in the text telephone mode.
+- [7] 3GPP TS 22.140: "Multimedia Messaging Service; Stage 1"
+- [8] 3GPP TS 23.140: "Multimedia Messaging Service; Functional description; Stage 2"
+- [9] IETF RFC 2793. (2000) RTP Payload for text conversation.
+- [10] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+**Total Conversation:** A service offering standardised simultaneous text, video and voice conversation or a subset thereof.
+
+**Host environment :** The session environment where the text component is added. E.g. Circuit switched voice, IP Multimedia etc.
+
+**Text Conversation:** A real time conversation in text with transmission character by character as entered.
+
+Further definitions are listed in 3GPP TR 21.905 [10].
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+| | |
+|-------|-----------------------------------------------------------------------------------------------------------------|
+| EDT | European Deaf Telephone |
+| GTT | Global Text Telephony; The feature that adds real time text conversation to any 3GPP conversational environment |
+| GTTFE | Global Text Telephony Feature Environment – The network components and functions forming GTT |
+| TTY | Here used as the term for the text telephone type dominating in USA. |
+| DTMF | Here used as a term for the text telephone type used in Holland, using DTMF tones. |
+| VCO | Voice Carry Over: Alternating (or parallel) sending of Speech and receiving Text |
+| HCO | Hear Carry Over: Alternating (or parallel) receiving Speech and transmission of Text |
+| FCC | Federal Communications Commission (of United States of America) |
+| PER | Printable character Error Rate |
+| MMI | Man Machine Interface |
+| SIM | Subscriber Identification Module |
+
+| | |
+|------|---------------------------------------------|
+| ITU | International Telecom Standardisation Union |
+| GSM | Global System for Mobile communication |
+| 3GPP | Third Generation Partnership Project |
+| CS | Circuit Switched |
+| IP | Internet Protocols |
+
+Further abbreviations are listed in TR 21.905 [10].
+
+# --- 4 High level Requirements
+
+The following list gives the high level requirements of the GTT. These are requirements which are independent of the user's perception of the feature:-
+
+- Service definition
+
+Global Text shall provide a real time conversational text feature. A general definition is found in Recommendation ITU-T F.700[5].
+
+- Global Text Telephony host environments
+
+A standardised method for Global Text Telephony shall at least be specified for each host environment in the mobile networks that can carry voice.
+
+- Standards compliant and forward compatible text conversation
+
+Global Text Telephone mechanisms shall provide the capability to support current and evolving text telephony and text conversation features by re-using existing standards as far as possible and proposing extensions (as necessary) to existing standards (i.e. the global text telephony feature shall support the evolution of Total Conversation technologies in all networks).
+
+- Consistent text conversation
+
+Regardless of the selected host environment, the far end terminal, the interworking facilities involved, GTT shall be capable of providing a consistent way of handling the conversation.
+
+- Global Text Telephone access
+
+Within the capabilities of networks and terminals, the user shall be provided consistent access to the GTT regardless of the access point.
+
+For example: the user shall be capable of accessing the text conversation features through a number of different access points, including networks based on 3GPP specifications, access through dedicated multimedia terminals, and access through combinations of mobile phones combined with text user interface devices.
+
+- Interoperability
+
+Global Text Telephony shall support interoperability with existing and emerging text telephone systems and text conversation features.
+
+Global Text Telephony shall support a minimum set of environments where text conversation is supported to ensure full interoperability between different terminals and networks.
+
+- Emergency calls
+
+The implementation of Global Text Telephony shall enable a user to make emergency calls to, and receive calls from, an emergency call centre via a text telephony device used in conjunction with GTT enabled user equipment.
+
+# 5 General Requirements
+
+Network operators have many differing requirements, and GTT shall be supported in the network in a manner which allows network operators to consider different configurations depending on their network and commercial requirements. Thus, an identified set of functionalities and protocols shall be standardised to ensure interoperability across networks and terminals to support GTT.
+
+The following general requirements shall be supported.
+
+## 5.1 Text conversation host environments
+
+The protocol environments for text conversation shall be the same as the ones used for other multimedia conversation calls and voice calls. The selected environment for a session is called the host environment.
+
+Supported host environments are:
+
+- Packet switched multimedia
+- Circuit switched multimedia.
+- The text conversation carried by a data transmission procedure, possible to combine with a voice session.
+- Circuit switched voice telephony, with the text conversation carried in-band in the voice channel.
+
+## 5.2 Text conversation management
+
+It shall be possible to allow GTT use without GTT specific subscription.
+
+Note: There is no requirement for GTT feature specific subscription, but for "normal GTT calls" a subscription for telephony is required. For "emergency GTT call" no subscription of any kind is required.
+
+Session start up delay and loss of initial characters should be minimised as far as practically possible.
+
+The text transport method should remain transparent to the network, unless specific functionality is required to provide a satisfactory quality of service.
+
+## 5.3 Registration of text conversation capabilities
+
+The availability of text conversation capabilities in the user terminal may need to be communicated to the network at call establishment in order to access the GTT service. However, a user is expected to be able to access the GTT service without explicit GTT registration with the operator.
+
+## 5.4 Session control
+
+The session control (call control) functions shall use the same procedures as the selected host environment.
+
+Additional operations needed to invoke the text component may be automated by the text conversation user interface.
+
+It shall be possible to establish text-only calls as well as calls with other media components.
+
+## 5.5 Invoking text conversation
+
+Calls with terminals where text conversation is used shall be monitored for requests to start the text feature.
+
+When either party in a call begins usage of the text feature, an effort shall be made to establish text conversation. It shall be possible to start text conversation during a call already established in voice or video mode by adding the text component.
+
+The mode selected for text conversation ( IP Multimedia, CS Multimedia, Voice path etc. ) shall be determined according to a prioritised procedure.
+
+Modes allowing simultaneous voice and text shall by default have higher priority, while the user shall be given opportunities to prioritise text-only modes. The default order shall be: IP Multimedia, CS Multimedia, data path text plus voice, voice path text.
+
+The user shall be given call progress information and text invocation progress information in text or other non-audible media.
+
+## 5.6 Text conversation handling during calls
+
+Text transmission shall be done character by character as entered, or in small groups transmitted so, that no character is delayed before transmission more than 0.5 seconds. (as stated in ITU-T T.140 [4])
+
+The text transmission shall allow a rate of at least 10 characters per second so that human typing speed as well as speech to text methods of generating conversation text can be supported.
+
+The end-to-end delay of characters shall be less than two seconds, measured between two mobile users, or between one mobile user and any interworking fixed network user, assuming that the fixed network does not contribute with more than one second to this figure.
+
+The character corruption rate should be less than 1% in conditions where users experience the voice transmission quality to be low but useful.
+
+The transmission of the text conversation shall be made according to the character set and operations defined in ITU-T T.140. [4]. This requirement enables smooth interworking with minimal loss of functionality between different text conversation environments. The allowed limitations in character set support specified in ITU-T T.140 shall be obeyed, so that two terminals always have a minimum common character set available for conversation.
+
+Figure 2 gives an example of a possible layout of a real time text conversation according to ITU-T T.140.
+
+| ANNE | EVE |
+|------------------------------------------------------------|-------------------------------------------------------------------------|
+| Hi, this is Anne. | Oh, hello Anne, I am glad you are calling!
It was long since we met! |
+| Yes, have you heard that I will come to Paris in November? | No, that was new to me. What brings you here? |
+
+**Figure 2: A possible way to display a conversation with one window each**
+
+Display of the conversation shall be done according to the principles specified in T.140, unless the display is provided through interworking with a legacy mode text telephone, when the limitations of that device may govern.
+
+NOTE: It shall be noted that support for any written language is possible with T.140, and that many languages require other writing directions than left-to-right.
+
+## 5.7 Alerting
+
+Since many GTT users are deaf or hard-of-hearing, the terminals used for GTT shall provide an interface that can be used to activate alternative alerting modes e.g. flash or vibration.
+
+## 5.8 Addressing
+
+GTT shall support the addressing formats of the host environments. to identify the different kinds of endpoints of the call used in the different host environments (see section 9, interworking.)
+
+## 5.9 Roaming
+
+Access to the GTT service while roaming is desirable.
+
+Note: Operators may consider using a Virtual Home Environment toolkit to provide GTT services to roaming subscribers. It can be expected that the subscriber will need to specifically subscribe to this service and no access to the GTT service will be possible if the visited network does not support the appropriate VHE toolkit. It should also be noted that emergency calls bypass most VHE toolkits, therefore emergency calls will require GTT support in the local network.
+
+# --- 6 Security and reliability
+
+The user shall be able to use and access GTT in a secure manner. Within the limitations enforced by the host environments, the following apply.
+
+- It shall be possible for the contents of GTT sessions to be read only by the intended recipient(s).
+- The “Security Threats and Requirements” specified in 22.133 [3] shall not be compromised.
+
+# --- 7 Charging
+
+It is foreseen that users will not be expected to pay a premium for access to the GTT service. Hence the requirement to capture detailed information relating to the use of GTT is seen as optional.
+
+Various charging mechanisms may be supported in addition to what is defined for the host environment, the following charging characteristics may be considered:-- Text was used in the call.- The duration for which text was used in a call.
+
+# --- 8 External Interfaces
+
+## 8.1 External interfaces in the terminal
+
+It shall be possible to control and operate GTT from external digital devices, e.g, portable computers. For this purpose interfaces shall be standardised between the terminal and such external digital devices.
+
+It shall be possible to control and operate GTT from external analogue text telephones. For this purpose, interfaces shall be standardised between the mobile terminal and such external analogue text telephones.
+
+External interfaces specified for controlling and operating GTT between the terminal and an external device should make it possible to use the external device for both Multimedia Messaging and GTT.
+
+## 8.2 External interfaces to other networks
+
+No new network interfaces shall be specified for GTT, only the necessary elements to accomplish text interworking. These are specified in ITU-T H.248 Annex F, in the Text Conversation and Text Telephone packages [3].
+
+The networks for specified interworking include:
+
+- PSTN for interworking with PSTN text telephones.
+- IP networks for interworking with IP conversational multimedia terminals and IP text telephones.
+- CS networks for interworking with CS Multimedia terminals.
+- Mobile networks out of scope of the GTT specifications interface through common interworking facilities.
+
+# 9 Interworking
+
+It shall be possible to use GTT to communicate with similar features in other networks as specified in ITU-T H.248 Annex F, in the Text Conversation and Text Telephone packages [3].
+
+This includes:
+
+- PSTN text telephones, using voice telephony as a carrier according to ITU-T V.18 [6].
+- IP text telephones, using IP multimedia protocols and text according to ITU-T T.140 [4].
+- IP conversational multimedia terminals using IP multimedia protocols with text according to ITU-T T.140 [4].
+- CS multimedia with text according to ITU-T T.140 [4].
+
+There is no requirement that the host environment combinations for interworking shall be extended for GTT support beyond the host environment interworking established for other media.
+
+For interworking with text conversation in mobile networks outside the scope of the GTT specifications, interworking shall be specified as for other external networks.
+
+For mobile services within scope of the GTT specification, interworking shall be possible between different forms of GTT, within the limits of interworking between the different host environments.
+
+GTT shall permit use of the supplementary services defined for the host environment.
+
+Users of both GTT and Multimedia Messaging [7],[8], should be provided the following interoperation opportunities:
+
+- If a call with a text component fails, it should be possible to offer the user to send a message to a MultiMedia Messaging facility such that the message may later be delivered in non-real time to the destination.
+- External User Equipment interface specifications should enable both GTT and MMS text handling functions to be placed in the same device.
+
+Note: In order to fulfil the requirement to give a consistent view of the feature from different access points, it may be of interest to give fixed network text telephone users possibilities to send and receive MMS text messages. This is however outside the scope of this specification.
+
+# 10 Additional services
+
+## 10.1 Emergency services
+
+It shall be possible to support emergency service calls with text and voice.
+
+If an emergency service centre supports call back to the calling user, then the call-back function shall be available for GTT text calls without modification to the existing emergency service centre text telephony equipment.
+
+GTT emergency calls shall be possible without the SIM/USIM module in the same host environments as such calls are enabled for voice.
+
+All information that follows a voice call to the emergency centre, shall also be provided to the centre if GTT text is used in the call.
+
+The emergency service requirements shall be possible to fulfil for emergency service centres equipped with PSTN text telephones, operated through a relay operator service or an interworking functions.
+
+Support of GTT service for emergency calls shall not jeopardise normal emergency calls.
+
+## 10.2 Relay services
+
+Relay services offer translation between text and voice. It is most commonly implemented as manned services.
+
+Access to relay services shall be possible for GTT users. Establishment of the relay service itself is outside the scope of GTT.
+
+GTT shall enable addition of a relay service to the call. The relay service terminates the text path, and translates between text and voice.
+
+Addressing the destination and requesting support from the relay service should be possible to do in one operation from the GTT user.
+
+Other aspects of implementing relay services are outside the scope of this specification.
+
+# --- 11 Network implementation considerations
+
+The GTT feature may be implemented in a number of ways. The GTT specifications shall allow cost effective implementations both for networks with a small part of the subscribers using GTT as well as networks with relatively many subscribers using GTT.
+
+# Annex A (informative): Background
+
+Text telephone systems were implemented mainly for distant conversation with deaf, hard-of-hearing, speech-impaired and deaf-blind users. The text telephone systems offer a real time, character by character, conversation in text, optionally combinable with voice. With proper implementation in mobile systems, the feature is expected to be of interest for any user.
+
+The general user needs are described in ETSI ETR 333 Human Factors, Text Telephony; User requirements and Recommendations [2].
+
+In PSTN, seven different, openly specified systems for text telephony exist, and are used in different regions. Some proprietary modes are also used.
+
+The open specifications are called Baudot, DTMF, EDT, V.21, Bell103, Minitel and V.18. They all use different modem technologies and character coding for the transmission of text. They are briefly described in the annexes of ITU-T V.18 [6].
+
+ITU-T V.18 [6] is an automoding mechanism that enables communication with all the legacy modes on the modem level. It also detects when both parties have V.18, and invokes an internationally useful character set, defined in ITU-T T.140, and optionally transmission of text and voice simultaneously. Native modulation for V.18 is V.21, while V.61 is used when simultaneous voice and text is wanted. Other modulations can be negotiated.
+
+V.18 and T.140 are intended for use in new PSTN text telephones. They are also intended for use in gateways, bridging from the fragmented situation in the PSTN, into new services, designed according to the Total Conversation concept.
+
+## A.1 Total Conversation
+
+Total Conversation adds text conversation to multimedia protocols in a standardised way, so that simultaneous communication in video, text and voice is accomplished. For the text part, the Unicode based text presentation protocol ITU-T T.140 is used. It is transmitted with a specific standardised transport channel for each environment. Subsets can be used for example for text telephony enabled in the multimedia architectures.
+
+Total Conversation is currently defined in the following environments:
+
+1. Packet networks, where the procedures described in ITU-T H.323 Annex G can be used for text conversation sessions, using TCP or RTP/T140 for the transport of T.140. A simple packet text telephone is defined, called Text SET.
+2. Packet networks, where the IETF Session Initiation Protocol SIP can be used for setting up and conducting text conversation sessions using RTP/T140 for the transport of T.140 text media. RTP/T140 is MIME registered and specified in IETF RFC 2793 [9].
+3. The H.324 multimedia environment in PSTN, ISDN and Mobile networks, where an AL1 channel connected by H.245 procedures is used for T.140.
+4. The H.320 multimedia environment, where a H.224 channel with client ID=2 is specified for transport of T.140.
+5. The T.120 data conferencing environment, that can be used alone or in conjunction with any of the environments above, where T.134 specifies the application entity and T.125 the data channel for T.140.
+6. Text Telephony in the PSTN using the ITU-T V.18 modem and T.140 for the presentation without any further transport protocol.
+
+## A.2 Interworking
+
+Interworking between these forms of Text Conversation can be achieved through the use of gateways or interworking functions. One gateway mechanism (*in the process of standardisation*) is ITU-T H.248, where Annex F, Facsimile, Text conversation and call discrimination packages [3] describes additions for handling text telephony and text conversation.
+
+## A.3 Additional services
+
+Apart from the basic user – to – user conversation, the following are examples of important additional services that can be offered text telephone users and Total Conversation users.
+
+### Emergency services
+
+The ability to call to emergency services, announce an emergency situation and discuss the actions can be offered text telephone users and Total Conversation users. Calls from the emergency service with support for text conversation is also needed.
+
+### Relay services
+
+In order to have conversations with users of plain voice telephones, text relay services are established. Currently, manned relay services dominate, offering real time translation between written and spoken language. Automatic and semi-automatic versions are emerging. A through connection of the voice channel is usually offered as an option to satisfy users who can benefit from multiple modes.
+
+With Total Conversation services, both traditional text relay services and other relay services are established. Examples are sign language relay services with text support during service establishment and speech-support relay services with visual enhancement.;
+
+# Annex B (informative): Initial requirements
+
+This section is informative and specifies the initial requirements that formed the base of definition of GTT. The 3GPP GTT specifications together define what requirements will be met.
+
+Most requirements in this chapter are derived from the requirements expressed to be urgent by the FCC and the CTIA TTY forum in USA. The relation with these requirements are documented for each requirement.
+
+Many of these requirements are written with the view that a PSTN text telephone is attached to the mobile station for implementation of the basic GTT functionality.
+
+## B.1 Transmission Performance
+
+**A1:** The printable character error rate (PER) shall be less than 1% for stationary calls under nominal radio conditions, i.e. where also speech calls show an acceptable quality (TTY/FCC 1).
+
+**A2:** The printable character error rate (PER) shall be less than 1% for calls with pedestrian speed or typical vehicle speed under nominal radio conditions (TTY/FCC 13, TTY Forum, extended).
+
+**A3:** An output volume control should be provided in order to allow adaptation to existing Text Telephone equipment for optimal receiving quality (TTY/FCC 4).
+
+**A4:** The input range shall be automatically adapted to the proper receiving level (new).
+
+**A5:** The Text Telephone shall allow to transmit Speech and Text (VCO/HCO) in an automated way, without user interaction, either by alternating between speech and text mode or by transmitting speech and text in parallel (objective) (TTY/FCC 9, extended).
+
+**A6:** The delay of the speech path shall not exceed that of a normal speech call in that situation by more than 40ms in one way, if the text telephone functionality is activated. Otherwise no additional delay shall occur to the speech signal. The delay of the speech path should not vary during a speech phrase.
+
+**A7:** The delay of the text path shall not exceed that of the speech path by more than 1000 ms (one way) at typing speed of 7 characters per second. The delay of the text path may be variable.
+
+**A8:** The time of switching between Text and Speech mode shall not exceed 1000 ms at normal typing speed.
+
+**A9:** The printable character throughput shall not be smaller than 10 characters per second under nominal radio operating conditions (TTY/FCC 10, extended).
+
+**A10:** Under impaired radio conditions the character throughput may be reduced in order to achieve the desired printable character error rate (TTY/FCC 10, modified).
+
+**A11:** The signals used for transmission should pass existing fixed and wireless “analogue” speech channels with a printable character error rate below 1% under nominal radio conditions, if two devices are connected “back to back”.
+
+**A12:** The data transmission bit rate should be as high as possible under the given radio conditions with the objective of 300 Bit/s with a bit error rate below $10^{-3}$ and a residual bit error rate below $10^{-5}$ (after removing detected bit errors).
+
+**A13:** It shall be possible to transmit both, single characters, as well as long text or data strings (from file) efficiently.
+
+**A14:** The transmission mechanism should provide data flow control to adapt the source data rate (when in file transfer mode) to the varying radio transmission conditions, in order not to lose data on the path.
+
+**A15:** The character coding shall allow transmission of characters from any language in a consistent way.
+
+## B.2 Man Machine Interface (MMI)
+
+These Requirements and Objectives are to some extent depending on implementation and not on the transmission standard. This list shall by no means restrict the innovation capabilities of vendors, but give guidelines and define a minimum set, against which the transmission standard needs to be checked.
+
+**B1:** The Text Telephone user must be able to monitor all aspects of call progress (same or more information as provided to voice users) by tones and visualisation (TTY/FCC 2). The transmission standard shall provide the necessary monitor information to the MMI.
+
+**B2:** There must be an indication, by tones and visualisation, when the call is connected or disconnected (TTY/FCC 3).
+
+**B3:** Call information such as caller identification, where provided in mobile voice services, should also be provided for Text Telephony calls (TTY/FCC 11 adapted).
+
+**B4:** The Text Telephone system must be able to send “Text Tones” to a normal telephone user, to indicate that he is using a text telephone, even if the other user has only a normal phone (TTY/FCC 6 adjusted).
+
+**B5:** The Text Telephone user must have a means of tactile (vibrating) ring signal indication. (TTY/FCC 5), besides an acoustical and optical ring signal indication (new).
+
+**B6:** Emergency calls (e.g. to 112 or 911 numbers) shall not require any further user interaction than for any normal voice call. (except to connect the possible additional equipment) (new).
+
+**B7:** Call back from Emergency Call Centres should not require any further user interaction than for any normal voice call (except to connect the possible additional equipment) (new).
+
+**B8:** Call setup to and from other Text Telephone users of the same type according to the new standard should not require any further user interaction than for any normal voice call (new).
+
+**B9:** Call setup to and from other Text Telephone users of an other kind ( e.g. those defined in ITU V.18) may require some user activity, like
+
+- sending a short additional precode (e.g. 2..3 digits) or
+- typing a short digit sequence to invoke the service (e.g. like #55\*) or
+- (on user's preference) the permanent subscription to such a service
+- a capability signalling by the mobile
+- activating a text telephone application
+- others
+
+**B10:** The new standard should allow the usage of ordinary unmodified mobile phones as already available to the user or on the mass market, in order to get the advantage of high volumes price level.
+
+**B10:** The new standard shall allow to hide the intermediate (with existing phones) necessary user interaction, as described in the items before, in modern equipment (automatic service).
+
+**B11:** The use of the Text Telephone for emergency calls with unregistered phones or without SIM/USIM shall be possible as for normal voice calls.
+
+**B12:** The interface to the possible adapters shall be exactly specified with
+
+- mandatory interfaces (as to allow interaction to existing Text Telephones and the basic access to the mobile phone) and
+- optional interfaces (as to connect microphone and loudspeaker, the control port of the mobile phones, ...)
+
+## B.3 Compatibility
+
+**C1:** The standard shall be compatible to equipment on the landline side as specified in ITU recommendation V.18 (TTY/FCC 12, extended), including all annexes of V.18 and V.18 with V.61 for voice and text simultaneously
+
+**C2:** The landline party's Text Telephone equipment shall not need modifications or additions in order to be compatible and to achieve the desired error rate (TTY/FCC 7).
+
+**C3:** It shall be possible to deploy the Text Telephone standard world wide in all systems based on 3GPP specifications (new).
+
+**C4:** The wireless Text Telephone (i.e. on the Mobile user side) may require modifications or additions or the development of new equipment (TTY/FCC 8). The smaller the modifications or additions the better.
+
+**C5:** Roaming between networks of different operators of the same kind of wireless technology shall be possible, provided the operators has installed the service.
+
+**C6:** Is should be possible to connect equipment implementing the standard to any existing mobile phone of any existing wireless standard.
+
+**C7:** Communication between Text Telephones in different kinds of wireless technologies shall be possible.
+
+**C8:** Communication with text between mobile text telephones and multimedia devices with text shall be possible.
+
+## **B.4 Complexity of Implementation and Roll Out**
+
+**D1:** The standard shall allow a fast first step implementation and roll out
+
+**D2:** The standard shall allow integration into the mobile phone or the Text Telephone terminal or integration of everything together into a single device.
+
+## B.5 Referenced consumer requirements
+
+In the previous sections of this annex, the “TTY /FCC” requirements refer to the points below. They are formulated in November 1999 as the consumer requirements by the TTY Forum administered by CTIA in USA. The comments are inserted here for clarification.
+
+1. The character error rate should approximate that of AMPS, which has been demonstrated at <1% for stationary calls. More research on AMPS performance with TTY would be useful to assist in specifying a range of conditions.
+
+2. The TTY caller must be able to visually monitor all aspects of call progress provided to voice users. Specifically, the ability to pass through sounds on the line to the TTY (so that the user can monitor ring, busy, answered-in-voice, etc.) should be provided.
+
+3. There must be a visual indication when the call has been disconnected.
+
+4. A volume control should be provided.
+
+Comment: This item is intended to allow the TTY user to adjust volume for better reception of TTY tones into a mobile terminal attached TTY. It has no meaning for other solutions.
+
+5. The TTY user must have a means of tactile (vibrating) ring signal indication.
+
+6. The caller must be able to transmit TTY tones independent of the condition of the receiving modem.
+
+Comment: This is to permit Text Telephone signalling, to let a hearing person know that the incoming call is from a text telephone.)
+
+7. The landline party's TTY must not require retrofitting in order to achieve the desired error rate.
+
+8. The wireless party's TTY may require retrofitting, or a new model TTY to be developed, or the use of a portable data terminal such as a personal digital assistant.
+
+9. VCO and HCO should be supported where possible.
+
+Comment: VCO= Voice carry over. HCO= Hearing Carry Over. These are terms for alternating voice and text in the same call.
+
+10. Reduction of throughput (partial rate) on Baudot is highly undesirable and should not be relied upon to achieve compliance (see #7). It may be useful as a user-selectable option to improve accuracy on a given call.
+
+11. Call information such as ANI and ALI, where provided in wireless voice, should also be provided for TTY calls. Comment: ANI= Automatic Number Identification, ALI= Automatic Location Identification.
+
+12. On the landline side, the solution need not support little-used or obsolete TTY models, but in general should support the embedded base of TTY's sold over the past ten years. The landline equipment supported must not be limited to that used in Public Service Answering Points (911 centers).
+
+13. Drive conditions must be supported, again using AMPS as a benchmark.
+
+# Annex C (informative): Change history
+
+| Document history | | |
+|------------------|------------|--------------------------------------------------------------------------------|
+| V. 0.0.1 | April 2000 | First Draft (Presented at TSG-S1 10 th – 15 th April 00) |
+| V.0.3.0 | July 2000 | Includes changes required by S1#9. |
+| V.0.3.1 | Aug. 2000 | Align with 3GPP doc structure |
+| V.0.3.2 | Aug. 2000 | Comments from Ericsson and Siemens accepted |
+| V.1.0.0 | Sept. 2000 | Updated to version 1.0.0 for presentation to SA #9 |
+| V.1.1.0 | May 2001 | Updated with output of GTT ad-hoc. To be sent for approval at SA#12 |
+| V.2.0.0 | May 2001 | Raised to version 2.0.0 for approval at SA #12 |
+| V5.0.0 | June 2001 | Approved at SA #12 |
+| V5.1.0 | Oct. 2001 | Creation of 5.1.0 by inclusion of CRs at SA #13 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|-----------------------------------------------------------|--------|--------|---------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| Dec 1999 | | | 02.01 | | | | | Transferred to 3GPP SA1 | 8.1.0 | 3.0.0 | |
+| SP-13 | SP-010433 | S1-010861 | 22.226 | 001 | | Rel-5 | F | CR to 22.226 version 5.0.0 GTT Stage 1 as requested by SA | 5.0.0 | 5.1.0 | GTT |
+| SP-15 | SP-020045 | S1-020457 | 22.226 | 002 | - | Rel-5 | F | Editorial CR to correct terms and references | 5.1.0 | 5.2.0 | CORRECT |
+| SP-26 | SP-040744 | S1-040997 | 22.001 | | | Rel-6 | | Updated from Rel-5 to Rel-6 | 5.0.0 | 6.0.0 | |
+| SP-36 | | | 22.001 | | | Rel-7 | | Updated from Rel-6 to Rel-7 | 6.0.0 | 7.0.0 | |
+| SP-42 | - | - | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22233/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22233/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a6d79486224de460a78526722732ee0ce26a031
--- /dev/null
+++ b/marked/Rel-18/22_series/22233/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d94b7792ba7d79eb4c005adcf7b9803b65f5d6e8b08ab9d0356c859ab5aa6760
+size 8254
diff --git a/marked/Rel-18/22_series/22233/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22233/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36e7a3f828f0d9967346c18ed8d0d20d55782e48
--- /dev/null
+++ b/marked/Rel-18/22_series/22233/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7cbf06110fcfc48b544916c42a24fe9ac22143fe9bf33e65e487c08bbe24ee6
+size 8060
diff --git a/marked/Rel-18/22_series/22233/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-18/22_series/22233/997233d405f0d4b89ddeb7683e047f66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8fee918b51222c302e27acec2c428602425b6bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22233/997233d405f0d4b89ddeb7683e047f66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd73157d1a72f8e3e937ca1f69f432733b6c460dbe8a6aefb37243680aa893ce
+size 80238
diff --git a/marked/Rel-18/22_series/22233/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-18/22_series/22233/d793cf7c174b89eb024d132f00679787_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32bcbfd1a6cffc7124693c2cce9845a4eee5fc5f
--- /dev/null
+++ b/marked/Rel-18/22_series/22233/d793cf7c174b89eb024d132f00679787_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0332c1224304eaac3605653069efb19789ec6117bd2a1366b01dad1386ecf34d
+size 50787
diff --git a/marked/Rel-18/22_series/22233/raw.md b/marked/Rel-18/22_series/22233/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba02b0ca5b2a1fdec814a0711dae29d28b0c3ec3
--- /dev/null
+++ b/marked/Rel-18/22_series/22233/raw.md
@@ -0,0 +1,437 @@
+
+
+# 3GPP TS 22.233 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Transparent end-to-end packet-switched streaming service; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'P', and a 'TM' symbol to the right.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, packet mode, stage 1
+
+### **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles – Sophia Antipolis
+Valbonne – FRANCE
+Tel. : +33 4 92 94 42 00 Fax : +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|---------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Entities involved in Streaming service..... | 6 |
+| 5 Service Requirements ..... | 7 |
+| 5.1 General ..... | 7 |
+| 5.2 Media Types..... | 8 |
+| 5.3 Multimedia Composition and Interaction ..... | 9 |
+| 5.4 Transport ..... | 9 |
+| 5.5 Service Personalization ..... | 10 |
+| 5.6 Service Management..... | 10 |
+| 6 Security ..... | 11 |
+| 7 Charging..... | 11 |
+| 8 Digital Rights Management ..... | 11 |
+| 9 Interworking..... | 11 |
+| 10 Service Interaction ..... | 11 |
+| Annex A (informative): PSS Examples ..... | 13 |
+| Annex B (informative): Change history..... | 15 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+3G mobile systems, through the increase in available bandwidth, offer new possibilities and services. One of these new services will be the ability to stream sound and movies to mobile devices.
+
+Streaming is a mechanism whereby media content can be rendered at the same time that it is being transmitted to the client over the data network.
+
+Streaming services are required whenever instant access to multimedia information needs to be integrated into an interactive media application. This has to be seen in contrast to other multimedia services like for instance MMS where multimedia content is delivered to the user asynchronously by means of a “message”.
+
+Interactive applications that use streaming services include on-demand and live information delivery applications. Examples of the first category are music, music videos and news-on-demand applications. Live delivery of radio and television programs are examples of the second category, this could e.g. make it possible to listen to domestic radio while abroad.
+
+A web server works with requests for information, it delivers that particular information as fast as possible, completes the transaction, disconnects and goes on to other requests. A client connects to a web server only when it needs information. This strategy works well as long as pictures and text are to be received. If a client wants to watch video or listen to audio, the entire file must be received before it can be played. The problem is that these kinds of files can be very large thus potentially causing storage problems in the client and resulting in long start-up latency. A streaming service improves this by allowing the media to be consumed as it is received, thereby reducing the latency and removing the need to store the media.
+
+In addition to providing the streaming mechanism the PSS also encompasses the composition of media objects thereby allowing compelling multimedia services to be provisioned. For instance, a mobile cinema ticketing application would allow the user to view the film trailers.
+
+# --- 1 Scope
+
+This Technical Specification defines the stage one description of the Packet-switched Streaming Service (PSS). Stage one is the set of requirements that shall be supported for the provision of a streaming service, seen primarily from the user's and service providers' points of view but also includes the service capabilities of the PSS itself
+
+This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This TS contains the core requirements for the Packet-switched Streaming Service (PSS), which are sufficient to enable a range of services.
+
+# --- 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] Void
+- [2] Void
+- [3] 3GPP TS 22.105: "Services and Service Capabilities".
+- [4] 3GPP TS 26.233: "Transparent End to End Packet Switched Streaming Service (PSS): General Description".
+- [5] 3GPP TS 26.234: "Transparent End to End Packet Switched Streaming Service (PSS): Protocol and Codecs".
+- [6] 3GPP TS 21.905: "Vocabulary for 3GPP specifications".
+- [7] Void
+- [8] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) part 2: media types".
+- [9] 3GPP TS 22.242: "Digital Rights Management (DRM)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+**Client:** in the context of Streaming Service the client is a device (or service) that receives media objects and/or multimedia composition instructions from a server.
+
+**Media Type:** a type of media e.g. text, audio, video, graphics (see section 5.2)
+
+**Media Object:** an instance of a media type (e.g. a picture) or a combination of instances of media types (e.g. a video clip that includes audio)
+
+**Media Attribute:** an attribute of a media object depending on the media type e.g. the colour of a piece of text
+
+**Multimedia Composition:** the position in time and space of media objects relative to one another
+
+**Multimedia Services:** Services that handle several types of media such as audio and video in a synchronised way from the user's point of view. A multimedia service may involve multiple parties, multiple connections, and the addition or deletion of resources and users within a single communication session.
+
+**Server:** in the context of the Streaming Service the server is a device (or service) that delivers media objects and/or multimedia composition instructions in response to client requests.
+
+**Streaming:** a mechanism whereby media content can be rendered at the same time that it is being transmitted to the client over the data network.
+
+**Streaming Service:** an alternative way of referring to the PSS.
+
+**Terminal Profile:** Set of information about the physical capabilities of the terminal.
+
+**User Profile:** Is the set of information necessary to provide a user with a consistent, personalised service environment, irrespective of the user's location or the terminal used (within the limitations of the terminal and the serving network).
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [6] 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 [6].
+
+| | |
+|-------|-----------------------------------|
+| CODEC | Coder / DECoder |
+| MMS | Multimedia Messaging Service |
+| PS | Packet Switched |
+| PSS | Packet Switched Streaming Service |
+| QoS | Quality of Service |
+| UE | User Equipment |
+
+# --- 4 Entities involved in Streaming service
+
+The figures 01 and 02 shows the basic entities involved in the Streaming service and how they connect.
+
+Clients initiate the service and connect to the selected content server. Content servers can generate live content e.g. video from a concert. User profile and terminal capability data can be stored on a network server and will be contacted at the initial set up. User Profile will provide the Streaming service with the user's preferences. Terminal capabilities will be used by the Streaming service to decide whether or not the client is capable of receiving the streamed content.
+
+Portals are servers allowing convenient access to streamed media content. For instance, a portal might offer content browse and search facilities. In the simplest case, it is simply a Web/WAP-page with a list of links to streaming content. The content itself is usually stored on content servers, which can be located elsewhere in the network.
+
+
+
+Figure 01: Network elements involved in a 2G/3G packet switched streaming service for GPRS core. The diagram shows two 'Streaming Client' boxes on the left, each connected to a radio access network (GERAN and UTRAN). Both GERAN and UTRAN are connected to a '3GPP CoreNetwork' cloud. Inside the core network, data flows from GERAN/UTRAN through an 'SGSN' to a 'GGSN'. The 'GGSN' is connected to an 'IPNetwork' cloud. The 'IPNetwork' cloud is connected to several external entities: 'Content Servers', 'Live Encoders', 'Portals', and 'User and terminal profiles' (all shown as dashed boxes). A 'Content Cache' (also a dashed box) is connected to the 'IPNetwork' cloud.
+
+Figure 01: Network elements involved in a 2G/3G packet switched streaming service for GPRS core
+
+
+
+Figure 02: Network elements involved in a 2G/3G and LTE packet switched streaming service for EPC. On the left, a 'UE PSS Client' is connected to an 'E-UTRAN' (represented by an oval). The 'E-UTRAN' is connected to an 'MME'. The 'MME' is connected to an 'HSS' and a 'P-GW'. Above the 'MME', 'UTRAN' and 'GERAN' (represented by clouds) are also connected to the 'MME'. The 'P-GW' is connected to a 'PCRF' and an 'Operator's IP network' (represented by an oval). The 'Operator's IP network' is connected to 'Content caches', 'Content servers', 'Portals', and 'User and terminal profiles' (all shown as dashed boxes).
+
+Figure 02: Network elements involved in a 2G/3G and LTE packet switched streaming service for EPC
+
+# 5 Service Requirements
+
+## 5.1 General
+
+Stage 2 implementations are shown in TS 26.233 [4] and stage 3 in TS 26.234 [5].
+
+The PSS uses a Client / Server model. The client controls the server by sending requests to the server, which responds to these commands.
+
+- The PSS shall support downlink streaming.
+- The PSS shall maintain backwards compatibility (i.e. a Rel-4 client should be able to interoperate with a Rel-5 server and vice versa).
+- The PSS should consider interoperability with streaming elements (protocols, formats etc) already in use in other industries (e.g. the internet).
+- The PSS shall support access to live content in addition to pre-authored content. E.g. ability to listen to domestic radio station whilst abroad.
+- It shall be possible for an operator to configure a PSS television service so that the typical channel switching time, from the end user's perspective, does not exceed 2 seconds. A PSS television service may include live content offering or video on-demand content offering.
+- PSS should allow support for time shifted live media consumption and bookmarks.
+- The PSS should be able to support mechanisms that allow for efficient usage of transport resources (e.g. by compression of data in PSS).
+Such mechanisms should have no or minimal impacts on the core network and access networks.
+
+Note: Such mechanisms may not be available for all streamed content.
+
+- The PSS shall:
+ - use open standards where these are available for Streaming service requirements
+ - use standard procedures and interfaces to avoid interoperability problems among client, server and encoder
+ - The live PSS shall define an interaction procedure to provide interoperability between server and encoder.
+ - The live PSS shall define an interaction procedure to provide interoperability between server and server.
+ - use extensions to existing standards if needed
+
+## 5.2 Media Types
+
+- The PSS should support multiple media types (see ref [5]) to enable rich, compelling multimedia services, for example:
+ - Audio (including speech)
+ - Video
+ - Still image
+ - Graphics (2D and 3D) including animation and Timed Graphics
+ - Text
+ - Plain text
+ - Formatted text e.g. size, colour, font
+ - Timed Text
+ - Synthetic audio (e.g. MIDI)
+ - Metadata e.g. indication that text has been supplied for the hard of hearing
+- The number of implementations of each media type shall be kept to a minimum, considering the implementation impact to the terminals, interoperability, contents mobility and backward compatibility.
+- The PSS shall share media codecs with other 3G multimedia services to allow easy interworking when needed.
+
+- The PSS should be able to call upon a font that is available across all terminals, either by use of an agreed default font in all terminals or by downloading the font prior to display. This requirement applies to formatted text only and is dependent upon the terminal capability.
+
+## 5.3 Multimedia Composition and Interaction
+
+- The PSS shall enable the creation of multimedia services incorporating multiple media objects.
+- The PSS shall provide the capability to position and synchronise media objects on the client.
+- The PSS shall support flowing/scrolling of text or graphics in any direction.
+- The PSS shall provide the capability to specify the media attributes – text (e.g. colour, size, font, format) or graphics (e.g. size, colour) – in relation to the timebase of other media objects. E.g. in a karaoke application where the audio track and song lyrics are downloaded together, it should be possible to not only display the song lyrics in time to the music but to display the lyrics in different colours to indicate to the user when to sing them
+- The PSS shall provide the capability to update media objects dynamically. E.g. substitution of news report with a more up to date version on the content server.
+- The PSS should provide the capability to update the attributes of media objects dynamically. E.g. colour coded pre-paid indicator to indicate credit level.
+- The PSS should provide the capability to update the multimedia composition dynamically. E.g. the user interacts with the application and changes a scene.
+- The PSS shall provide the capability that allows the user to navigate through or interact with the multimedia service. E.g. Once a user has downloaded a “tour of London” application the user has the ability to navigate through London and see video clips or hear audio descriptions of points of interest in London.
+- The PSS shall provide the capability that allows clients of different capabilities to maximise the user experience. E.g. if a client did not support graphic animations it could render a single image.
+- The PSS shall support the transfer to the terminal of information on the accessed content in addition to the filename (e.g. song title, artist).
+
+## 5.4 Transport
+
+- The PSS transport shall be provided by the PS Domain.
+- Quality of Service (e.g. time delay) requirements shall be in accordance with requirements in 22.105 (ref. 3)
+- The PSS should be able to work over different QoS bearers.
+- The PSS shall provide a mechanism whereby the client is sent a list of media encoding bit rates and the client determines which one to use based on the network service bearers offered and the user preferences.
+- The PSS client shall be capable of requesting an appropriate level of QoS for the session. The QoS supplied may be limited by the local operator's access policy and/or network functionality.
+- The PSS should provide mechanisms for streaming servers and clients to adapt to the network conditions in order to achieve significant improvement in the quality of streaming, e.g. using information on end-to-end transport quality from the network.
+- The PSS should provide a reliable delivery mechanism that enables the user to receive the content without any errors due to the transport mechanism, i.e. a delivery mechanism without bit errors or packet loss. Such mechanism should support the following features :
+ - The rendering of video content without any transport degradation : the content is downloaded without any errors, it assures that the subscribers see the content that has been designed by the content creators.
+
+Note: User expectation of live video is related to the fact that it is delivered without interruptions or long delays. As such, reliable delivery mechanism is not considered for rendering of live video content (under poor conditions it might even be difficult to achieve). - The rendering of the content should start before the transfer is complete.
+
+- A broken session should be restarted efficiently without going back to the beginning : the PSS client is able to detect what content is missing and to ask the server to send this content.
+
+Note: In addition to the regular PSS transport mechanism it is possible to use download transport mechanisms in the following way: Audiovisual data encapsulated in a file is transmitted from the server to the client. The user is able to play the content during the file download, giving a similar look and feel to the regular PSS transport mechanism.
+
+## 5.5 Service Personalization
+
+- The PSS should support the ability for the client to have specific preferences described in the user profile. For example, if the user wants to watch a news show the preferred language (speech or subtitles) is specified in the user profile
+- The PSS shall support a basic set of terminal capabilities.
+- For the purpose of optimised presentation of the media streaming, PSS shall include capability exchange and negotiation mechanisms on server/client capabilities and user preferences at the session set up.
+- The client should be able to send user preferences to the server during a streaming session. E.g. the user may toggle between mono and stereo sound.
+
+## 5.6 Service Management
+
+User's control of the service:
+
+- The client shall initiate the streaming session.
+- The user shall have the possibility to stop the streaming session after it has been invoked.
+- The user shall have the possibility to pause the streaming session after it has been invoked. E.g. if a user has activated the streaming session and then gets a phone call, he/she shall be able to decide whether or not he/she wants the streaming session to continue. After a pause the user can choose to resume the streaming session.
+- The PSS should be able to simultaneously handle the streaming session and conversational (circuit or packet?) services (e.g. voice and video telephony)
+- The user shall have the possibility of jumping to another point within the media clip (i.e., random access)
+- The user should be able to search through media content whilst viewing the content.
+- If the content is available under different formats corresponding to the terminal capabilities and user preferences, the client should have the opportunity to choose the format for which the content will be streamed. Assuming the user has already set the user profile and the client is aware of this.
+
+Service Provider's management of the service:
+
+- The end user should be notified if the PSS is unavailable.
+- The Streaming session should be gracefully disconnected if the client is not capable of handling the streamed content.
+- The service provider should have the means by which a streaming session can be gracefully terminated (e.g. in a prepay scenario when the user's account has run out of credit)
+- The PSS should be able to support real-time quality of service metrics data from the UE.
+
+# --- 6 Security
+
+The user shall be able to use the PSS in a secure manner. Mechanisms shall be provided to ensure that the media objects are only sent to and accessed by the intended end-user(s).
+
+- PSS shall support end-to-end security (e.g. between the server and the Streaming client).
+
+# --- 7 Charging
+
+PSS should support various charging mechanisms, for example, time base charging, volume based charging, event based charging, content based charging.
+
+It shall be possible to include the following streaming specific data, as a minimum, in the CDRs as charging information:
+
+- streaming type (e.g. real-time or non real-time),
+- volume of streaming content delivered
+- volume of data delivered
+- time of start of delivery
+- duration
+- Qos, including transmission rate, packet loss ratio, transfer delay(latency ,jitter),
+- Streaming service sender / -recipient
+- number of Streaming events sent
+- number of Streaming events received.
+- Media type
+- Content id (the particular content stream being accessed)
+
+# --- 8 Digital Rights Management
+
+PSS shall support the 3GPP DRM mechanism (see ref [9])
+
+# --- 9 Interworking
+
+The standard shall permit interworking with other streaming technologies.
+
+# --- 10 Service Interaction
+
+- The PSS shall define a common file format (common to all download mechanisms) for easy service interaction with other multimedia delivery services defined in 3GPP (e.g. MMS).
+- It shall be possible for the PSS to interact with the MMS and other 3GPP multimedia delivery services. The interfaces and protocols used between the PSS and other 3GPP multimedia delivery services shall be standardized.
+
+Note : Service interaction with MMS is especially important because there are application scenarios where media delivery via a streaming service could be replaced by media delivery via MMS and vice versa.
+
+- The PSS shall define a server file format to provide easy interoperability between Content Creators and Service Providers.
+
+# --- Annex A (informative): PSS Examples
+
+Some domains may benefit from the convenient, ubiquitous and more reachable mobile device. A second challenge for operators and service providers is to utilise the 'mobile' effect for providing value-added services. We believe successful wireless data services will exploit the unique mobile characteristics. A non-exhaustive list of these mobile service characteristics can be presented as follows:
+
+- Content everywhere: Locally interactive content and remote interaction (back-channels) in relation to interactive streamed media, including rewind/pause functions will define the key features for providing attractive and friendly contents for distance learning applications and other information services (news, financial, etc). Scanning headlines of daily newspapers is already about to become a popular 'waiting time' activity. In the learning context, one may imagine that a student will be able to select on his portal page the school section from which he will be able to view a list of classes that will take place and to preview current live lectures, required readings, etc.
+- Lifestyle facilitators: When discovering a tourism site one may want access to leisure and travel information (e.g., flight deals, package holidays, quality hotels, fun activities, etc). During weekend outings and holidays, a common use case will be the following: one uses the location finder to find the nearest shop where he can find the desired object at the desired price, a navigation guide helps him to determine how he will get to the shop or store.
+- Entertainment services: Gaming is already being touted as the biggest generator of minutes of use for interactive cellular services in Asia and Europe. Features such as streamed 2D graphics, 3D objects, complex animations and multi-user technologies will attract more subscribers by allowing richer experiences with more fancy navigation schemes. As an example of future scenario, when online-games will become very popular, 3D-graphics of the new multimedia mobile phones allow a bunch of fancy games. Players can join multi-user games, some use a virtual location as well as the real location in a funny interactive way
+
+This set of multimedia applications should be foreseen for the Release 5 and the future releases.
+
+## Service Examples
+
+All these service examples could use or be enhanced by PSS.
+
+### Infotainment
+
+Video on demand, including TV
+
+Audio on demand, including news, music, etc
+
+Multimedia Travel Guide
+
+Karaoke – song words change colour to indicate when to sing
+
+Multimedia information services:
+
+- Sports
+- News
+- Stock quotes
+- Traffic
+
+Weather cams – gives information on other part of country or the world
+
+### Edutainment
+
+Distance learning – video stream of teacher or learning material together with teacher's voice or audio track.
+
+How to ? service – manufacturers show how to program the VCR at home
+
+### **Corporate**
+
+Field engineering information – junior engineer gets access to on line manuals to show how to repair the central heating system
+
+Surveillance of business premises or private property (real-time and non real-time)
+
+### **M-commerce**
+
+Multimedia Cinema ticketing application
+
+On line shopping – product presentations could be streamed to the user and then the user could buy on line.
+
+# Annex B (informative): Change history
+
+| | | |
+|---------|---------------|----------------------------------------------------|
+| V.0.1.0 | May 2001 | First Draft (Presented at TSG-SA-WG1 #12 ) |
+| v.0.2.0 | July 2001 | Second Draft (Presented at TSG-SA-WG1 #13) |
+| v.0.3.0 | November 2001 | Third Draft (Presented at TSG-SA-WG1 #14) |
+| 1.0.0 | November 2001 | Raised to version 1.0.0 for presentation to SA #14 |
+| 2.0.0 | February 2002 | Updated, ready for approval in SA #15 |
+| 5.0.0 | March 2002 | Approved, SA#15 |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|-------------------------------------------------------------------------------------------|--------|--------|---------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-17 | SP-020563 | S1-021791 | 22.233 | 001 | | Rel-6 | B | Requirement for efficient use of transport resources for PS Streaming | 5.0.0 | 6.0.0 | PSS-E |
+| SP-17 | SP-020563 | S1-021627 | 22.233 | 002 | | Rel-6 | B | CR, PSS server file format | 5.0.0 | 6.0.0 | PSS-E |
+| SP-18 | SP-020662 | S1-022037 | 22.233 | 003 | | Rel-6 | B | CR on streaming metrics | 6.0.0 | 6.1.0 | PSS |
+| SP-18 | SP-020662 | S1-022335 | 22.233 | 004 | | Rel-6 | B | DRM requirement for streaming | 6.0.0 | 6.1.0 | PSS-E |
+| SP-18 | SP-020662 | S1-022337 | 22.233 | 005 | | Rel-6 | B | Interaction MSS/PSS | 6.0.0 | 6.1.0 | PSS |
+| SP-18 | SP-020662 | S1-022353 | 22.233 | 006 | | Rel-6 | B | Asset Information in File Format | 6.0.0 | 6.1.0 | PSS |
+| SP-18 | SP-020662 | S1-022354 | 22.233 | 007 | | Rel-6 | B | Clarification of Transport Requirements | 6.0.0 | 6.1.0 | PSS |
+| SP-18 | SP-020662 | S1-022355 | 22.233 | 008 | | Rel-6 | B | CR on 22.233 'PSS Charging' | 6.0.0 | 6.1.0 | PSS |
+| SP-18 | SP-020662 | S1-022327 | 22.233 | 009 | | Rel-6 | B | CR FOR R6 22.233 on Declaration of Content Cache | 6.0.0 | 6.1.0 | PSS-E |
+| SP-19 | SP-030029 | S1-030245 | 22.233 | 010 | - | Rel-6 | B | PSS charging information | 6.1.0 | 6.2.0 | PSSrel6 |
+| SP-21 | SP-030466 | S1-030962 | 22.233 | 011 | - | Rel-6 | C | Removal of content cache information in PSS architecture | 6.2.0 | 6.3.0 | PSS |
+| SP-21 | SP-030466 | S1-030963 | 22.233 | 012 | - | Rel-6 | C | Reliable delivery mechanism | 6.2.0 | 6.3.0 | PSS |
+| SP-32 | - | - | 22.233 | - | - | - | - | Raised to version 7.0.0 as a result of implementing CR 30, a Rel-8 CR to a Rel-6 version. | 6.3.0 | 7.0.0 | - |
+| SP-32 | SP-060370 | S1-060627 | 22.233 | 0030 | 1 | Rel-8 | B | Requirement of avoiding live PSS interoperability problems among encoders and servers | 7.0.0 | 8.0.0 | TEI8 |
+| SP-43 | SP-090218 | S1-090323 | 22.233 | 0032 | 1 | Rel-8 | F | Addition of Rel-8 mobile TV requirement to PSS | 8.0.0 | 8.1.0 | TEI8 |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.1.0 | 9.0.0 | |
+| SP-51 | SP-110161 | S1-110176 | 22.233 | 0033 | - | Rel-9 | F | Removal of the outdated reference to TS 21.133 | 9.0.0 | 9.1.0 | TEI9 |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | - | - | - | - | - | - | - | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
+
diff --git a/marked/Rel-18/22_series/22240/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22240/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90653fa3de9b12a364ac55577f28536dc68189d6
--- /dev/null
+++ b/marked/Rel-18/22_series/22240/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11040e50bb4c60abba096f4986d1a0f2d19ff60fc3a9fb2a53200d30f32357fa
+size 8204
diff --git a/marked/Rel-18/22_series/22240/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22240/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..790c872f78780d0d1dedd74c6f596283d641a513
--- /dev/null
+++ b/marked/Rel-18/22_series/22240/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a328f4a21491b8085c12e1194ccb3a90035270eb678a888757ff37469da2ce67
+size 6313
diff --git a/marked/Rel-18/22_series/22240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-18/22_series/22240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..893b574d0efe7a23993cad0d45279dbc16a0f478
--- /dev/null
+++ b/marked/Rel-18/22_series/22240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26bfd14f07b9023a787d616251c985a4bd6e083229ab6d6cb12f9f6f8dd06bce
+size 66991
diff --git a/marked/Rel-18/22_series/22240/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/22_series/22240/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8242becab099856417beacb8399063e2fe9b479b
--- /dev/null
+++ b/marked/Rel-18/22_series/22240/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bdc44a8d45d44d6dfbe2691a2e354d60f6dab5af2c6253759caa432febef20dd
+size 53345
diff --git a/marked/Rel-18/22_series/22240/raw.md b/marked/Rel-18/22_series/22240/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3b1863a034ea6d87b6b4ab3d307545d7b39a2fb
--- /dev/null
+++ b/marked/Rel-18/22_series/22240/raw.md
@@ -0,0 +1,827 @@
+
+
+# 3GPP TS 22.240 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for 3GPP Generic User Profile (GUP); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G ADVANCED logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## --- **Keywords**
+
+LTE, UMTS, user
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-----------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1. Scope..... | 5 |
+| 2. References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 General description ..... | 6 |
+| 4.1 Introduction ..... | 6 |
+| 4.1.1 Intended Usage of the Generic User Profile ..... | 7 |
+| 4.1.2 Benefits of the 3GPP Generic User Profile for individual stakeholders ..... | 7 |
+| 4.2 Conceptual view of the GUP..... | 8 |
+| 4.3 GUP Data Stores and GUP data Users..... | 9 |
+| 4.4 Synchronisation model..... | 10 |
+| 4.5 Contents of GUP ..... | 11 |
+| 4.6 The role of Data Description in GUP..... | 12 |
+| 5 Stakeholder requirements..... | 12 |
+| 5.1 Subscriber Requirements..... | 13 |
+| 5.1.1 User Requirements ..... | 13 |
+| 5.2 Value Added Service Provider Requirements..... | 13 |
+| 5.3 Home Network Operator Requirements..... | 13 |
+| 5.4 Roamed-to Network Operator Requirements..... | 14 |
+| 5.5 Regulatory Requirements..... | 14 |
+| 6 General Requirements..... | 14 |
+| 6.1 Network Requirements..... | 14 |
+| 6.2 UE Requirements ..... | 14 |
+| 6.3 General Service Requirements ..... | 15 |
+| 6.4 Management Requirements..... | 15 |
+| 6.5 Synchronization Requirements ..... | 15 |
+| 6.6 Data Description Requirements ..... | 16 |
+| 7 Security ..... | 16 |
+| 8 Privacy and Authorisation..... | 17 |
+| 8.1 General Requirements ..... | 17 |
+| 8.2 Authorisation Rules..... | 17 |
+| 9 Charging..... | 18 |
+| Annex A (informative): Example 3GPP Generic User Profile use cases ..... | 19 |
+| Annex B (informative): Additional Information..... | 21 |
+| Annex C (informative): Bibliography ..... | 24 |
+| Annex D (informative): Change history..... | 25 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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, e.g. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document introduces the requirements and features of a 3GPP Generic User Profile (GUP). The GUP will help overcome some of the challenges associated with the introduction of sophisticated user terminals with widely varying capabilities, hybrid combinations of mobile network domains, the advent of downloadable applications, and the desire of users to customise potentially complex services to individual preferences and needs.
+
+The present document for a Generic User Profile will capture requirements that will allow:
+
+1. A way to express user preferences in a consistent manner.
+2. Effective management, control ownership and protection of GUP data.
+3. Extensibility to cater for future needs and the simple addition of new features.
+
+# --- 1. Scope
+
+The present document defines the stage one description to the 3GPP Generic User Profile (GUP). It specifies requirements to the 3GPP Generic User Profile, seen primarily from the user, home environment, serving network and value added service provider's points of view.
+
+The present document includes information applicable to the home environment, device- and network manufacturers and value added service providers which are sufficient to provide complete support of services in 3GPP networks.
+
+While the 3GPP Generic User Profile may contain components that are out of scope of 3GPP (e.g. for services offered by third parties) the requirements in the present document pertain only to those components that lie within the 3GPP system.
+
+# --- 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 TS 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 32.140: "Subscription Management Requirements".
+- [3] Open Mobile Alliance (OMA): OMA-RD-Parlay\_Service\_Access-V1\_0-20100427-A.
+- [4] W3C Recommendation "Extensible Markup Language (XML) 1.0 (Fifth Edition)"
+
+- [5] W3C Recommendation "XML Schemas, Part 1: Structures Second Edition"
+
+- [6] W3C Recommendation "XML Schemas, Part 2: Datatypes Second Edition"
+
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**3GPP Generic User Profile (GUP):** The 3GPP Generic User Profile is the collection of user related data which affects the way in which an individual user experiences services and which may be accessed in a standardised manner as described in this specification. The Generic User Profile is defined using the W3C XML recommendation [4].
+
+**GUP Component (logical):** A GUP component is logically an individual part of the Generic User Profile.
+
+**GUP Component instance (physical):** a GUP component instance is a physical representation of a GUP component. To one GUP component (logical) correspond one or more component instances, i.e. physical copies. Component instances may be located in the Home Network, in the Value Added Service Provider Environment and/or the User Equipment.
+
+**GUP Data Element:** the indivisible unit of Generic User Profile information.
+
+**GUP Data Model:** The data model describing the data structure, the way the data elements are defined and the relationship to each other.
+
+**Data Description Method:** A method describing how to define the data contained in the Generic User Profile. The description is defined using the W3C XML Schemas recommendations [5], [6].
+
+**Master component instance (aka master instance):** Among the component instances (physical) associated with a GUP component (logical), one of them is tagged with the role of "master instance". The master component instance is responsible for the correct value of the corresponding GUP component.
+
+**Public User Identity:** Identity which is used to communicate with other users.
+
+**User:** for definition see 3GPP TR 21.905 [1]. In addition the present document assumes, that the user has a unique identity in the 3GPP system (IMSI or IMS Private ID) and is associated with one 3GPP subscriber. (Note, that a user may have many addresses though! E.g. the user can have several Public User IDs). The user is not necessarily identical to the 3GPP subscriber.
+
+Further 3GPP system related definitions are given in 3GPP TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|--------------------------------------------|
+| GERAN | GSM/EDGE Radio Access Network |
+| GUP | 3GPP Generic User Profile |
+| IMS | IP Multimedia Core Network Subsystem |
+| IMSI | International Mobile Subscriber Identity |
+| MVNO | Mobile Virtual Network Operator |
+| OSA | Open Service Access |
+| PID | Private User Identity |
+| UE | User Equipment |
+| UTRAN | Universal Terrestrial Radio Access Network |
+| VASP | Value Added Service Provider |
+| VHE | Virtual Home Environment |
+| WLAN | Wireless Local Area Network |
+
+Further 3GPP system related abbreviations are given in 3GPP TR 21.905 [1].
+
+# --- 4 General description
+
+## 4.1 Introduction
+
+The fact of having several domains within the 3GPP mobile system (e.g. Circuit-Switched, Packet-Switched, IP Multimedia Subsystem) and access technologies (e.g. GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to Users, Services and User Equipment will be increased greatly. This causes difficulties for Users, Subscribers, network Operators and Value added service providers to create, access and manage the user-related data located in different entities.
+
+The objective of specifying the 3GPP Generic User Profile is to provide a means to enable harmonised usage of the user-related information originating from different entities. The specification of the GUP shall also allow extensibility to cater for future developments.
+
+The 3GPP Generic User Profile is the collection of User-related data which affects the way in which an individual user experiences services where a community of entities share this data. The 3GPP Generic User Profile can be stored in the home network environment and/or Value Added Service Provider equipment.
+
+The 3GPP Generic User Profile will be accessed by different stakeholders and managed either by one (centralised) or by different stakeholders (de-centralised) such as the user, subscriber, value added service provider and network
+
+operator by a standardised access mechanism. The 3GPP Generic User Profile allows intra-network usage (i.e. data exchange between applications within a mobile operator's network) and inter-network usage (between mobile operator's network and value added service providers) as illustrated in Figure 1.
+
+Note: MVNOs and visited networks are treated as value added service providers in terms of GUP data exchanges with mobile operator's network.
+
+The 3GPP Generic User Profile may be also be used by different applications in a standardised way.
+
+The 3GPP Generic User Profile will help to create and manage the user data in each entity and on the other hand to make it easier to find all user related data as a whole in the home network environment.
+
+Technically the 3GPP Generic User Profile provides an architecture, data description and interface with mechanisms to handle the data.
+
+### 4.1.1 Intended Usage of the Generic User Profile
+
+The intended usage of the 3GPP generic user profile is a critical factor driving its detailed specification, e.g., architecture and data model. In general, user profile data can be shared between different stakeholders to facilitate the following:
+
+- **User preference management:** Enable applications to read and utilize a limited set of user preference information
+- **User service customization:** Enable applications to read and utilize personalized service information, i.e., individual settings for a particular service
+- **Terminal capability management:** Enable applications to access terminal-related capabilities
+- **User Information sharing:** Enable applications to read and utilize application level information, e.g. address book information
+- **Profile key access:** Enable applications to use a unique identity as a key to access profile information, .e.g. any public user identity or an alias.
+
+It is intended that the 3GPP GUP, in particular, will address all of the above. As can be inferred, a user's identity can serve as the unique common key into the profile.
+
+### 4.1.2 Benefits of the 3GPP Generic User Profile for individual stakeholders
+
+The following chapter shows in an exemplary way how stakeholders may benefit from GUP. The examples given are neither exhaustive nor are they meant to be part of, or be implemented by GUP. On the contrary, these functions / use-cases need to be seen distinct from GUP, but capabilities offered through GUP (e.g. a common data description, data access- and synchronisation mechanisms ...) may be utilised to build these functions.
+
+- Subscription Management and Customer Care:
+Subscription Management [2] benefits from a standardised way to access subscription data of a user. Already today customer care is a noticeable part of an operator's expenses, it will grow to be even more expensive as more services and more terminal types become available for 3GPP system. Unlike the Supplementary services in GSM new services in 3GPP are not standardised. Therefore content and format of subscription data as well as the places (repositories) where subscription data are stored may be different for different new services. GUP specifies the description of- and access of data in a standardised way. This will allow:
+ - **Service providers** as well as Value Added Service providers to use standardised GUP mechanisms for Subscription Management and Customer Care by the operator.
+ - Reduce costs for Subscription Management and Customer Care for the **operator** and/or **service provider** and/or value added service provider since management tools may rely on this standardised mechanism.
+- Subscription Check by third party provided services:
+Third party provided services may run on application servers outside the 3GPP system. However subscription information may be kept by the home operator.
+
+To find out, whether a service is allowed to be invoked by a particular user the service needs to check its subscription. Access to this information can be controlled by means of GUP mechanisms.
+
+- Benefit for third party **value added service providers** and for
+- **Operators**, who want to keep subscription within their domain
+- Services Interaction:
+If personalisation of services possibly effect other services it may be advantageous, that such personalisation is visible to these other services. If a service is designed to permit access to these data through GUP mechanisms:
+ - the **user** or **operator** may choose to allow certain services to access certain user data of other services of the user.
+- Provision of Terminal Capability information:
+Services (from the home- or visited network operator or provided by third parties) may need to know what capabilities the terminal, that is currently used by the user, supports. Multiple provisioning protocols are a problem for terminal vendors since the UE has to support all of them. The GUP data will be described in the same way and can therefore be used in different protocols without having to change. GUP mechanisms could provide the basis for retrieval of a user's terminal capabilities.
+ - Benefit for the **value added service provider**, who can rely on a GUP mechanism to obtain this information.
+
+## 4.2 Conceptual view of the GUP
+
+For each user (characterised by an IMSI or IMS PID) one User Profile exists, which may consist of several 'components'. These components may be distributed in the home network and value added service provider's environment. Within the home network, the components may be distributed in various network nodes. Figure 1 below provides a conceptual overview of GUP and is as such for informative purposes only. Only one master of the component exists, but one or more copies of the master component may exist. The home operator shall be able to copy master components, which are located outside the home network to the home network. Within the home network, functionality exists that is able to locate GUP components, thereby making applications unaware of the actual location of the components. The administration and management of the data associated with this functionality is under the control of the home network. Although GUP does not attempt to provide an actual classification of the data it may contain, one may consider categorisations such as general user information, terminal related information, service specific information, etc. as indicated in clause 4.4.
+
+
+
+The diagram illustrates the conceptual view of GUP (Generic User Profile) data distribution between a Home Network and a Value Added Service Provider. The Home Network contains a cloud labeled 'GUP Data' which is divided into three sections: 'General User Information' (containing Component A and Component B), 'Other Data (eg terminal related information)' (containing Component D and Component E), and 'Service Specific Information' (containing Component Y and Component X). The Value Added Service Provider contains a cloud labeled 'GUP Data' which contains Component A and Component Y. A double-headed green arrow connects the Home Network cloud and the Value Added Service Provider cloud, indicating data exchange. A legend at the bottom left shows a yellow box with a wavy pattern for 'Component Instance' and a solid yellow box for 'Master Component Instance'.
+
+Conceptual view of GUP diagram showing Home Network and Value Added Service Provider data components.
+
+Figure 1: Conceptual view of GUP
+
+## 4.3 GUP Data Stores and GUP data Users
+
+This clause describes in general terms where the generic user profile data resides and which entities use that information. A general feature of the user profile is that the different entities are data consumers for a certain subset of the generic user profile and are data suppliers for another part. The 3GPP GUP data are distributed by nature and consequently stored in home network and Value Added Service Provider Equipment.
+
+
+
+```
+
+graph TD
+ subgraph GUP_Data_Users
+ TA[Terminal Application]
+ HNA[Home Network Application]
+ 3PA[3rd Party Application]
+ OAMA[OAM and subscription Management Application]
+ end
+ GUP((Generic User Profile))
+ subgraph GUP_Data_Stores
+ HN[Home Network]
+ VASP[Value Added Service Provider]
+ end
+ TA --- GUP
+ HNA --- GUP
+ 3PA --- GUP
+ OAMA --- GUP
+ GUP --- HN
+ GUP --- VASP
+ HN --- VASP
+
+```
+
+Figure 2: Illustration of the scope of 3GPP Generic User Profile. The diagram shows 'GUP Data Users' at the top, which include 'Terminal Application', 'Home Network Application', '3rd Party Application', and 'OAM and subscription Management Application'. These are connected to a central 'Generic User Profile' cloud. Below the cloud are 'GUP Data Stores', which include 'Home Network' and 'Value Added Service Provider'. The cloud is connected to both stores.
+
+**Figure 2: Illustration of the scope of 3GPP Generic User Profile**
+
+The Generic User Profile provides a generic mechanism to access and manipulate user related data for suppliers and consumers. Using this mechanism the data can be retrieved and managed in a uniform way. However the data contents itself are not described within the Generic User Profile, but only the data model and a schema shall be defined.
+
+The suppliers and consumers of the data can be divided into the following groups of applications:
+
+- Applications in the home network
+- 3rd Party Applications
+- OAM and subscription management applications
+
+Applications in the home network may include those related to call or session handling as well as messaging or web services. Typically fairly high requirements are set on the response time.
+
+3rd Party Applications are similar to applications in the home network but they are non-trusted which means that strict security, access and privacy procedures shall be carried out.
+
+OAM activities related to user profile are provisioning and administration of user data by the network operator. These activities are characterised by needs for high throughput and allow longer response time. In order to allow simple and centralized administration it should be transparent to the administrator where the different parts of the user data are stored. As a result, this role needs a single system image on user profile, or, on functional terms, a common data access function. As one alternative the user self-service management may be implemented as part of this function.
+
+## 4.4 Synchronisation model
+
+GUP components instances may be distributed in the home network and value added service provider's environment. The distribution model is shown in Figure 1.
+
+A data consumer can request a copy of a GUP component, i.e. the master instance of the component. This copy may be a **working copy** or a **synchronised copy**.
+
+**Master instance:** the data supplier holds the master instance of a GUP component.
+
+Note: During the lifetime of a component, the role of *master instance* may be played by different component instances (e.g. in the case of failure). But at any point in time, there is always one and only one "master instance". This implementation aspect is beyond the scope of GUP.
+
+A **synchronised copy** of a GUP component is a component instance that is kept synchronized with the master instance.
+
+Synchronization here means that changes made to the master instance will be propagated to the synchronized copy (e.g. update, deletion, etc.) The synchronized copy is held within the data consumer's local store..
+
+A **working copy** of a GUP component is a component instance that corresponds to a copy (or snapshot) of the master instance at a given point in time. The working copy is held within the data consumer's local store. Future changes to the master instance (e.g. update, deletion, etc.) are NOT propagated to the working copy. The working copy remains unaffected by changes of the master instance of the GUP component.
+
+If a GUP component is no longer applicable for a given user, the master instance for this GUP component is deleted and all data stores holding synchronized copies are notified about this deletion.
+
+If the access rights of the component are changed, a proper notification is sent to the owner of the synchronized copy.
+
+## 4.5 Contents of GUP
+
+The present document does not mandate any data to be part of the 3GPP Generic User Profile. However the following kind of data are considered to be useful for inclusion in GUP.
+
+### 1. Authorised and subscribed services information:
+
+These kind of data are generally owned by the home operator and allow management and interrogation of subscription information and would typically consist of:
+
+- authorised services that the subscriber may subscribe to
+- services the subscriber actually has subscribed to
+
+### 2. General user information
+
+Data, owned by the user, which are not specific to individual services, but may be useful for any service. These would be data like
+
+- settings (e.g. name, postal address), preferences (e.g. language)
+- Registered Service Profiles of the user, indicating the currently active Service Profile of the user.
+
+### 3. PLMN specific user information
+
+Data, owned by the home operator, which are not specific to individual services, but may be useful for any service. These typically would be data like
+
+- addresses (e.g. MSISDNs, URLs) of the user.
+- WAP parameters (e.g. standard WAP gateway)
+- GPRS parameters (in UE and HSS)
+- Preferred access technologies (The preferred access technology, second preferred access technology etc. e.g. UTRAN, GERAN, WLAN etc.)
+
+### 4. Privacy control data of the user
+
+Data, owned by the user, which are specific to individual services and which control privacy settings of that service. These could e.g. be
+
+- Privacy settings for standardised services like the Presence service or Push service.
+- Privacy settings of non-standardised services.
+
+### 5. Service specific information of the user:
+
+Data, owned by the user or value added service provider, which are specific to individual services (standardised or non-standardised). These could e.g. be
+
+- Service customisation data of the user.
+- Service authentication- and authorisation data (for “single sign on”) like keys, certificates, passwords...
+
+### 6. Terminal related data
+
+These are data, which relate in particular to the user's terminals (ME and UICC). These could e.g. consist of
+
+- Terminal capabilities of the terminal currently in use (e.g. User Interface capabilities, communication capabilities, available services, service capabilities,...).
+- Data for initial configuration and/or reset of the ME.
+- Backup data for recovery of the ME configuration including service specific data.
+
+### 7. Charging and billing related data
+
+This data consists of information necessary for the user related charging and billing. This data could e.g. consist of:
+
+- The billing policy
+
+Note: The following data categories are not considered to be useful for the 3GPP Generic User Profile:
+
+- Run Time Data.
+Data that are created during the initiation of the session, call or application execution and if they are only available during the lifetime of such session, call or application execution then they are considered as Run Time data.
+- Historic/Statistic Data.
+User/system behaviour information (e.g. statistics on the usage preferred web pages; duration, number of calls, error rate).
+
+## 4.6 The role of Data Description in GUP
+
+GUP provides a means of supporting access to data for ranges of services and functions (e.g. MMS, Presence). The support of users' services and personalization data may result in manipulating data in a structured manner, and a standardised way of describing and accessing these data structures, utilizing a Data Description Method based on XML Schema.
+
+As there may be technologies which have impact on the GUP but could not be included in the Data Description Method, the Data Description Method should take this coexistence with other technologies into consideration.
+
+# --- 5 Stakeholder requirements
+
+These requirements are given from the perspective of the key stakeholders.
+
+The stakeholders within the context of GUP are:
+
+- the Subscriber
+
+Note: The subscriber may hold subscriptions for one user (e.g. in the case the subscriber is identical with the user) or several users (e.g. in the case of a company - the subscriber – holding subscriptions for it's employees – the users)
+
+- the User
+
+Note: The user may or may not be identical with the Subscriber.
+
+- the Value Added Service Provider
+- the Home Network Operator
+- the Roamed-to Network Operator
+- the Regulator
+
+## 5.1 Subscriber Requirements
+
+For a subscriber's services, that support and are supported by GUP:
+
+- The subscriber shall be able to customise her subscribed services and interrogate customisation settings, subject to limitations by the Home operator and/or value added service provider. The user interface for customisation/interrogation is service specific and out of scope of this specification.
+
+### 5.1.1 User Requirements
+
+For a user's services, that support and are supported by GUP:
+
+- The user shall be able to customise the services , that have been subscribed to her by the subscriber and interrogate customisation settings, subject to limitations by the Home operator and/or value added service provider and/or subscriber. The user interface for customisation/interrogation is service specific and out of scope of this specification.
+
+## 5.2 Value Added Service Provider Requirements
+
+VASP services, i.e. services provided by Value Added Service Providers (VASP), shall – via mechanisms of the GUP – be able to:
+
+- Identify the network, the service and the user in any GUP related operation
+- Check a user's subscription information for the service.
+- Provide access to a user's service specific GUP data stored by the application (according to the access rights set by the user).
+- Access other GUP data of the user subject to limitations of access rights
+
+VASP services – standardised and non-standardised – may be part of the 3GPP system (as operator supplied services in the home-network or in a different 3GPP network) or may reside outside the 3GPP system.
+
+It shall be possible for VASP services outside the 3GPP domain to access GUP only via a secure interface to the 3GPP system.
+
+## 5.3 Home Network Operator Requirements
+
+The home network operator shall, via GUP mechanisms, be able to:
+
+- support On-line Service Registration
+
+Subscriber service registration can be set up by on-line subscription not just by customer care. This will also reduce Customer Relationship Management (CRM) workload.
+
+- access Terminal Capabilities
+
+Terminal capabilities (e.g. software and hardware information, application features, etc) shall be accessible to the network. This information may be used to enable any services within network.
+
+- access Value Added Service Provider Capability Information
+
+Value Added Service Provider capability information (e.g. Compression algorithms, Billing capabilities) should be accessible to the network. This information may be used to provide end-to-end service according to UE, Network and the Value Added Service Provider's capabilities.
+
+## 5.4 Roamed-to Network Operator Requirements
+
+None yet identified.
+
+## 5.5 Regulatory Requirements
+
+None identified in addition to the considerations in clause 8. Privacy and Authorisation.
+
+# --- 6 General Requirements
+
+This clause includes different general technical requirements which are not from the perspective of a particular stakeholder.
+
+## 6.1 Network Requirements
+
+These requirements are collected from the point of view of technical Network infrastructure and Elements:
+
+- The GUP data shall be accessed by standardised GUP interfaces and protocols which use the generic GUP data model to carry the user profile.
+- The GUP Interface shall be independent of the structure and semantics of the data.
+- The GUP access mechanism shall support accessing of the whole profile data or a selected part of it.
+- The GUP access mechanism shall include read, create, modify and delete access. GUP shall provide these access mechanisms to read, create, modify, and delete data of GUP components.
+
+Note: This does not include installation and modification of the structure of GUP components at a specified data store, nor does it imply management of GUP data stores of GUP component instances.
+
+- The GUP data shall be transferred in a standardised way.
+- The GUP interface shall include a standardised way for access control.
+- The GUP interface shall enforce the subscriber privacy.
+- The GUP interface shall enforce the user privacy.
+- The GUP shall not cause significant additional load or delays to the network functions and elements.
+
+## 6.2 UE Requirements
+
+This clause includes different UE specific requirements for the 3GPP GUP.
+
+- GUP shall provide mechanisms to represent UE data as GUP components in the network (e.g. terminal capabilities, user preferences, etc).
+- Network based applications should have "read" access to GUP components representing UE data, irrespective of the connection status of the UE.
+- It shall be possible to back up GUP data to the home network or VASP network and to restore it to a UE, however, the mechanism used is outside the scope of GUP.
+
+## 6.3 General Service Requirements
+
+This clause includes different Service aspects and requirements for the 3GPP Generic User Profile. The following general requirements from the point of view of different Service Applications apply:
+
+- It shall be possible for an application to retrieve the whole user profile or selected parts of it in one transaction.
+- There shall be effective means to retrieve individual GUP data elements with acceptable delay for real-time services.
+
+One typical use case for the latter requirement is a call control application that would take advantage of subscriber's preferences or charging related information.
+
+Third party applications may take advantage of the features specified e.g. for Open Service Access (see OMA Parlay Service Access Requirements [3]) to access GUP data.
+
+The description of GUP data shall be easily extensible for new, proprietary uses without any problems caused for the existing or standard applications.
+
+## 6.4 Management Requirements
+
+This clause includes different technical Management aspects for the 3GPP Generic User Profile based on the needs of e.g. Self-Service Management, Subscription Management, Service Management, Network Element Management, Network Management and Customer Relationship Management.
+
+In 3G networks it is expected that user profile data is not only distributed over different network elements but belongs to different administrative domains. These administrative domains may be closed against external access. However, in order to enable a seamless service experience for the user a controlled transparency to exchange user profile data is needed.
+
+There exist two main cases to be addressed:
+
+### **Domain borders in the home network:**
+
+Already in the network of the subscriber's home network operator there may exist different domains. Potential examples are application of 3rd party value added service providers which are loosely coupled with the network provider, e.g. their applications run under the brand of the network operator but their data are stored and maintained apart from the network operator's entities.
+
+### **Domain borders between different network operators:**
+
+This is the well-known roaming scenario where a user is served by another network than his home one. Roaming is already addressed by mobile networks but in the case of 3G networks there is an important additional requirement: The assumed frequent changes of applications induces a need to handle frequent changes of data sources/consumers.
+
+The user profile data access architecture shall enable the transparent and flexible usage of the user profile data. It shall provide transparent access to distributed data fulfilling the needs of the different roles described above. Furthermore, the architecture shall address the fact that parts of the user profile data are potentially located in different administrative domains. Possible means are negotiation capabilities and proxy functionality at the domain borders.
+
+### **Management of GUP data components:**
+
+Making a particular data store available for GUP is not in the scope of GUP and needs to be administered by other means.
+
+The administration (installation and modification) of the structure of GUP components at a specified data store is not in the scope of GUP and needs to be administered by other means.
+
+## 6.5 Synchronization Requirements
+
+To avoid unnecessary duplicated data storage an application should be able to access parts of the user's GUP data.
+
+The following requirements are applicable to the synchronization model:
+
+1. GUP shall offer a mechanism to define *synchronized copies*, i.e. instances that are kept synchronized with the master instance.
+2. GUP shall offer a mechanism to define *working copies*, i.e. instances that do not require any synchronization.
+3. GUP shall make sure that synchronized copies do not conflict with the access right of the corresponding GUP components. For example, if the access rights to some parts of the GUP component change such that the data consumer no longer has access rights, then those parts of the GUP component would no longer be synchronised.
+
+## 6.6 Data Description Requirements
+
+The Generic User Profile is a generic, extensible profile data collection with mechanisms to e.g. create, retrieve, delete and modify the data. GUP shall define a standardised way of data description. This allows for a standardised access and handling of these data, not excluding the possibility of proprietary extensions.
+
+Only part of the data contents are standardised within 3GPP specifications, whereas application specific data is outside the scope of the 3GPP standardisation. This specification does not mandate any 3GPP service specific data to be part of the 3GPP Generic User Profile. However the common data types shall be specified to facilitate the separate work on the service specific definitions (e.g. for the user profile in HSS).
+
+The common data shall contain data types for at least:
+
+- Private IDs (IMSI and IMS Private User Identity)
+- Public IDs (MSISDN and SIP URL)
+- Other address types, that are supported by 3GPP (e.g. e-mail)
+- Service identifications
+- Generic privacy control data
+- Date and time
+- Service Subscription state (e.g. "active", "not subscribed", "dormant" ...)
+
+# --- 7 Security
+
+Secure mechanisms shall be available for the transfer of User Profile data to, from or between authorised entities. Access to User Profile data shall only be permitted in an authorised and secure manner. The secure mechanisms to be applied shall be appropriate to the level of confidentiality of the data, the endpoints of the transfer and the routes that are available for the transfer of the data. The owner of the data, normally the body storing the master copy of the data, shall be responsible for applying the appropriate level of security to the transfer of the data.
+
+The secure mechanisms available shall include the following:
+
+1. Authentication of consumer
+Before any user data transfer takes place, it shall be possible for the supplier of the data to verify the identity of the consumer.
+2. Authentication of supplier
+It shall be possible for the consumer of data to identify the supplier.
+3. It is permissible for either the supplier or consumer of data to employ the services of a third party, known to, and trusted by, both in order to provide authentication of identity.
+4. The validity of an authentication of identity shall, if required, be subject to a maximum time limit.
+5. It shall be possible for the supplier of data to render the data to be unreadable by any party not authorised to receive it.
+6. It shall be possible for the consumer of data to detect whether the data have been tampered with during transmission. .
+
+7. The security mechanisms shall provide verification that the data has been sent by the supplier and received by the consumer (non-repudiation).
+8. It shall be possible for the supplier and/or the consumer to create an audit log of all GUP data transfer transactions of a specified type, provided that this requirement is made known before any transfer takes place
+9. User profile data in general is proprietary data. This data may not be shared with unauthorized entities. *Access control* to the data is required. This access control must also apply to data which is located at legacy systems, currently without own access control functionality.
+10. Correct setting of data values in the user profile may be critical for the integrity of certain network services. Therefore, *consistency checks* are needed to minimise the risk.
+11. Transaction security for the change of data should be available in order to ensure the consistent change of data at different locations.
+
+# --- 8 Privacy and Authorisation
+
+This clause describes the requirements for the authorization of access to the user profile data. The Privacy can be provided by the means of authorization mechanism.
+
+## 8.1 General Requirements
+
+It shall be possible for the user to define privacy requirements for components of the 3GPP Generic User Profile to determine access rights.
+
+It is agreed in the subscription agreement between the home network operator and the subscriber how the access and privacy control is carried out e.g. who is able to control different parts of the user profile including the privacy settings. The GUP shall provide means to implement access and privacy control according to the different agreements.
+
+The GUP authorization shall be independent of who has set the privacy rules for each part of the GUP data. A generic mechanism shall be provided to ensure that only such data for which there is a valid authority can be created, read, modified or deleted.
+
+The privacy requirements shall fulfill local privacy regulations. Lawful interception and other regulator requirements may imply that GUP data is delivered to authorities despite the privacy settings.
+
+## 8.2 Authorisation Rules
+
+Authorisation of the requested action (create, read, modify or delete) on the user profile data depends on the following information:
+
+- identification of the requesting application
+- identification of the requesting subscriber (if delivered in the request)
+- identification of the targeted user
+- identification of the targeted user profile data
+
+The disclosure of the user profile data must be considered based on the identification of the application requesting access to the data. The possible identities of the applications will not be standardized but are implementation specific.
+
+Regarding trusted applications involving other subscribers or comparable entities it shall be possible also to check the access rights of the subscriber being served by the application. This requires that the identification of the served subscriber is passed via the GUP mechanism in addition to the application identification. The access is first defined per applications and secondly per served subscriber. The access may be granted also to the public, some group or a list of subscribers.
+
+The identity of targeted user will be based on the 3GPP network identities (Private and Public User Identities). Public User Identities would be normally applied, but especially within the operator domain the Private Identity could be used as well.
+
+The targeted user profile data will be controlled as per the whole user profile and/or per different GUP components and/or per different GUP data elements.
+
+Depending on the service the privacy of the requested GUP data can additionally be managed in the service level e.g. in Presence or IMS group management. The privacy rules for these services are specified in the corresponding 3GPP specifications.
+
+The GUP shall also support the possibility that the privacy of specific GUP data is queried from other privacy control system. Existing privacy solutions should be considered and adopted if applicable (e.g. LCS).
+
+# --- 9 Charging
+
+It shall be possible to support charging for the management, access and synchronization of the 3GPP Generic User Profile. (e.g. for capability negotiation or remote diagnostic information gathering).
+
+Note: There might be legislative restrictions on charging. This is FFS.
+
+# --- Annex A (informative): Example 3GPP Generic User Profile use cases
+
+## 1. Setting up a Subscription for a new customer
+
+- Precondition
+ - A person has just purchased a new device, and requires new subscription data to be initiated in the shop.
+- Actions
+ - Subscription data is input by the shop personnel by means of a Subscription Management application.
+ - Subscription Management application stores the data in Generic User Profile in the Home Network.
+- Post-condition
+ - The user can leave the shop. Her subscription is ready to use.
+
+## 2. Application Access to User Profile Data using OSA (Pull Scenario)
+
+- Precondition
+ - The application is registered with the OSA framework
+ - The application is authorised to access the user profile management Service Control Function and use methods which permit read/write data in user profiles
+- Actions
+ - The application uses OSA to read/write data in the user profile of the user
+ - The network provides the requested data or modifies the data as requested
+- Post-condition
+ - Consistency of the user profile data
+
+## 3. Notification of user subscription to an HE-VASP application using OSA (Push Scenario)
+
+- Precondition
+ - The OSA application from the HE-VASP is registered with the OSA framework
+ - The OSA application is authorized to receive subscription/unsubscription notifications
+ - The OSA application has subscribed to the notification permitting to it to know when new users have subscribed to the service implemented by the OSA application
+- Actions
+ - A new user subscribes to the service implemented by the OSA application
+ - The Home Environment notifies the OSA application about a new subscription and provides it with relevant information (e.g. identity of the user)
+ - Possibly the OSA application provides the home environment with a link (e.g. URL) to a location where the user can customize the service
+- Post-conditions
+
+- The OSA application can now have access to home environment -owned user profile information for this user, provided that it is granted the related access rights
+- The user can customize service data for the service implemented by the OSA application
+
+## 4. Customization of service specific data for a VHE service provided by a HE-VASP
+
+- Preconditions
+ - The user has a VHE subscription
+ - The user is subscribed to the service provided by the HE-VASP
+ - There is a link from the user Personal Service Environment (PSE) to the HE-VASP for service customization
+ - The user has access to her PSE and has successfully been logged to it
+- Actions
+ - The user accesses her PSE and decides to customize the service provided by the HE-VASP
+ - She transparently access a service customization interface provided by the HE-VASP (possibly via a hyperlink)
+ - She defines/modifies service customization data, which are managed and stored by the HE-VASP
+- Post-condition
+ - Next time she uses the service, new customization data will be used
+
+# --- Annex B (informative): Additional Information
+
+Note: The following use cases are currently not in the scope of 3GPP Generic User Profile Stage 1 but they are still considered to be useful information (e.g. for future work) and therefore included in this Annex.
+
+## 1. Setting up a Subscription for a new customer
+
+- Precondition
+ - A person has just purchased a new device, and requires a new subscription to be initiated in the shop.
+- Actions
+ - The user preferences for services are established.
+ - Information about the terminal capabilities are received from the UE.
+ - User Profile content is created for the Subscriber, and downloaded over the air, via local link or similar
+- Post-condition
+ - The user can leave the shop. Her phone/device is ready to use. Basic settings needed to start and run initial applications ready.
+
+## 2. Initial Service Configuration (Bootstrap)
+
+- Precondition
+ - No settings made, user with a subscription
+- Actions
+ - Settings, partly based on user profile downloaded over the air, via local link or similar
+ - The download initiated by the value added service provider, network operator, 3rd party or user
+- User Data
+ - Setting received could include basic connectivity configuration parameters and the user's security policy
+- Post-condition
+ - The user's phone/device ready to use. Basic settings needed to start and run initial applications ready
+
+## 3. Backup/Restore of User Profile Components stored in the UE
+
+- Precondition
+- Backup
+ - The phone is configured, all the user preferences are set.
+ - The settings include user profile parameters such as generic parameters, service personalisation parameters, user's security policy and other user preferences
+- Restore
+ - The phone's initial configuration enables download of configuration and user data at least via local link.
+ - A backup of phone configuration and user preferences is available in the network.
+
+- Actions
+ - The user wishes to backup or restore the current version, or parts of the current user profile to the network, or to another UE.
+ - The backup/restore is performed via local link or remotely towards the network
+ - The backup/restore can be initiated by the user, the value added service provider, 3rd parties or the network operator
+- User Profile Storage
+ - Secure area of the (U)SIM or ME or retained in the network by the value added service provider. User private data is only stored in the network with the user permission.
+
+## 4. Content Negotiation
+
+- Precondition
+ - The user has set her preferences in the UE
+ - Terminal type capability information is stored in "internet"
+- Actions
+ - The user initiates request for content. The request contains:
+ - User preference fetched from the UP
+ - Reference to the capability information is stored in "internet"
+ - Deviating capability information
+ - Returned content selected or tailored according to User preferences and capability information
+
+## 5. Terminal Management – Manual Helpdesk
+
+- Precondition
+ - A user is complaining because her pocket web browser does not work. He calls the helpdesk
+- Actions
+ - The UE capabilities are established by the helpdesk person
+ - A helpdesk person at an operator, value added service provider or enterprise verifies that the correct operating parameters are set on the device of a complaining user
+- Post-condition
+ - The user's is happy. The pocket web browser is running correctly
+
+## 6. Terminal Management – Automated Self Fixing
+
+- Precondition
+ - A software agent on the user's device identifies an error.
+- Actions
+ - It contacts the helpdesk software entity to fix the problem.
+ - The UE capabilities are established by the automated self-fixing solution.
+
+- The self-fixing solution correctly diagnoses the error and provisions a bug fix.
+- Post-condition
+ - The user's device software executes correctly (and is happy)
+
+## 7. Automatic Access Selection based on preferred list
+
+- Precondition
+ - The UE shall be able to support automatic access technologies selection (i.e. without user intervention).
+ - The user has set her preferences in the UE and enabled automatic access technologies selection.
+ - A list of preferred access technologies capabilities information is stored in "internet"
+ - The access technologies are authorized.
+- Actions
+ - The user equipment initiates request for selected access technology. The request contains:
+ - User preferences fetched from the UP
+ - Reference to the access technology capabilities information is stored in "internet"
+ - The preferred access technology is selected.
+- Post-condition
+ - The preferred access technology is selected based on the order of precedence defined in a list of access technologies on the UE. The switch to a less preferred access technology, in case the most preferred is not available, takes place without user intervention.
+
+## 8. Multiple Access Technology Negotiation
+
+- Precondition
+ - The user has set her preferences in the UE and enabled access selection.
+ - Terminal type capability information is stored in "internet"
+ - The access technologies are authorized
+ - The user has access and connection with one ongoing application
+- Actions
+ - The (Multi-mode) terminal initiates request for another access technologies.
+ - The terminal chooses the most appropriate access form based on the UP and/or the sessions in progress demand of service quality.
+ - Returned access form selected according to User preferences and capability information.
+- Post-condition
+ - Change of access technology without interrupting any session(s) to/from that host (context transfer).
+ - The old access connection end.
+ - The user and the terminal are connected via the new access (i.e. WLAN) with the same user identity, without having to re-authenticate.
+
+# --- Annex C (informative): Bibliography
+
+The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information.
+
+3GPP TS 21.133: "3G Security; Security Threats and Requirements".
+
+3GPP TS 22.097: "Multiple Subscriber Profile (MSP) Phase 1; Service description - Stage 1".
+
+3GPP TR 22.121: "The Virtual Home Environment".
+
+# Annex D (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|---------|--------|-----|----------------------------------------------------------------------------------|--------|--------|-------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Re
v | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-19 | SP-030036 | | 22.240 | | | Rel-6 | | Approved at SA #19 | 2.0.0 | 6.0.0 | |
+| SP-21 | SP-030469 | S1-030965 | 22.240 | 001 | | Rel-6 | F | Clarifications for section 7 of 22.240 | 6.0.0 | 6.1.0 | GUP |
+| SP-22 | SP-030707 | S1-031256 | 22.240 | 002 | - | Rel-6 | F | Clarifications on general service requirements and data description requirements | 6.1.0 | 6.2.0 | GUP |
+| SP-22 | SP-030707 | S1-031257 | 22.240 | 003 | - | Rel-6 | F | Clarifications GUP data access and administration | 6.1.0 | 6.2.0 | GUP |
+| SP-22 | SP-030707 | S1-031258 | 22.240 | 004 | - | Rel-6 | F | Clarifications on GUP synchronisation | 6.1.0 | 6.2.0 | GUP |
+| SP-23 | SP-040095 | S1-040202 | 22.240 | 005 | - | Rel-6 | F | GUP UE Requirements | 6.2.0 | 6.3.0 | GUP |
+| SP-25 | SP-040507 | S1-040683 | 22.240 | 006 | - | Rel-6 | F | GUP, UE requirements corrections | 6.3.0 | 6.4.0 | GUP |
+| SP-26 | SP-040730 | S1-040989 | 22.240 | 007 | - | Rel-6 | F | Removal of erroneous use cases | 6.4.0 | 6.5.0 | GUP |
+| SP-42 | | | | | | Rel-7 | | Upgraded to Rel-7 without technical change. | 6.5.0 | 7.0.0 | |
+| SP-42 | | | | | | Rel-7 | | Upgraded to Rel-8 without technical change. | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| SP-49 | SP-100575 | S1-102054 | 22.240 | 0008 | - | Rel-9 | D | Removal of references to 3GPP OSA | 9.0.0 | 9.1.0 | TEI9 |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| SP-62 | SP-130592 | S1-135289 | 22.240 | 0009 | 1 | Rel-11 | F | Correction of external references | 11.0.0 | 11.1.0 | TEI11 |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.1.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2020-01 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22242/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22242/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f2622c319f3a68672ea3e7be9b7bb3c18d957a5
--- /dev/null
+++ b/marked/Rel-18/22_series/22242/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cbd61f3d1d02ef713057b49988a705c8d9116705a39965b986371748bb230d4f
+size 8161
diff --git a/marked/Rel-18/22_series/22242/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22242/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc6bc4f813adced92c024b660eb55ff5795770bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22242/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15fd4ae7c319660070fc3dfc8ffa883ed6d9d537e4ba645f4999849854f69b74
+size 7354
diff --git a/marked/Rel-18/22_series/22242/raw.md b/marked/Rel-18/22_series/22242/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c97d0f66c1bdad837a9583afec31dead337350e5
--- /dev/null
+++ b/marked/Rel-18/22_series/22242/raw.md
@@ -0,0 +1,147 @@
+
+
+# 3GPP TS 22.242 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Digital Rights Management (DRM); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring the text "5G" in a large, bold, black font with "ADVANCED" in smaller letters to the right. Above the "5G" is a green graphic consisting of three curved lines representing signal waves.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" is larger and has a red signal wave graphic at its base. A small "TM" trademark symbol is located to the upper right of the "P".
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+LTE, UMTS, service, DRM
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|---------------------------------------------------|----------|
+| Foreword ..... | 4 |
+| 1 Void..... | 5 |
+| 2 References..... | 5 |
+| 3 Void..... | 5 |
+| 4 Digital Rights Management Model..... | 5 |
+| 5 to 10 Void..... | 5 |
+| Annex A (informative): Void..... | 5 |
+| Annex B (informative): Change history..... | 6 |
+
+## --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 Void
+
+## 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] OMA-RD-DRM " OMA DRM Requirements" (Open Mobile Alliance) [Available at [http://www.openmobilealliance.org/release\\_program/index.html](http://www.openmobilealliance.org/release_program/index.html)]
+
+# --- 3 Void
+
+# 4 Digital Rights Management Model
+
+The text in this specification has been removed. DRM specifications are elaborated in the Open Mobile Alliance (OMA) according to an agreement between 3GPP and OMA.
+
+For DRM Service and System Aspects OMA-RD-DRM is referenced [1].
+
+## --- 5 to 10 Void
+
+## --- Annex A (informative):
+
+### Void
+
+## Annex B (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|-----------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-15 | SP-020061 | S1-020659 | | | | Rel-6 | | Presentation to SA for information | 1.0.0 | 1.0.0 | DRM |
+| SP-16 | SP-020261 | S1-021185 | | | | Rel-6 | | Presentation to SA for approval | 2.0.0 | 6.0.0 | DRM |
+| SP-17 | SP-020564 | S1-021609 | 22.242 | 001 | | Rel-6 | F | Clean-up of TS 22.242 | 6.0.0 | 6.1.0 | DRM |
+| SP-19 | SP-030177 | | 22.242 | 002 | 1 | Rel-6 | B | DRM collaboration with OMA | 6.1.0 | 6.2.0 | DRM |
+| SP-26 | SP-040906 | S1-040963 | 22.242 | 003 | 1 | Rel-6 | F | Removing text in DRM stage 1 specification and reference OMA RD | 6.2.0 | 6.3.0 | DRM |
+| SP-36 | | | 22.242 | | | Rel-7 | | Updated from Rel-6 to Rel-7 | 6.3.0 | 7.0.0 | |
+| SP-42 | - | - | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22243/01141eb99b707de5aead56f84afe3b1f_img.jpg b/marked/Rel-18/22_series/22243/01141eb99b707de5aead56f84afe3b1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04594c202e7791b5048a7adea34d6a4f97415935
--- /dev/null
+++ b/marked/Rel-18/22_series/22243/01141eb99b707de5aead56f84afe3b1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3683c76973abf1a6f3f2f16037a575406bcf21cc36dd15098c7b1a3faa16b126
+size 85106
diff --git a/marked/Rel-18/22_series/22243/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22243/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8cec23f6e213b241f2742386263d844cd350c779
--- /dev/null
+++ b/marked/Rel-18/22_series/22243/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d7cf3e5bf93395cbe4d2cf205a204755b538a8569505f6ecc00ed5f61e324a2
+size 9730
diff --git a/marked/Rel-18/22_series/22243/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22243/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61df19bb76b11f90e8ed277486d32f5685071224
--- /dev/null
+++ b/marked/Rel-18/22_series/22243/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc6f895d6f505603d2e6e5b0bfa55bdacb63a0afdf9b00d7c43e5f92107f0faf
+size 5293
diff --git a/marked/Rel-18/22_series/22243/raw.md b/marked/Rel-18/22_series/22243/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a6493dbe989b9fee72deebf4a1f5b051c87e34cd
--- /dev/null
+++ b/marked/Rel-18/22_series/22243/raw.md
@@ -0,0 +1,442 @@
+
+
+# 3GPP TS 22.243 V18.0.1 (2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Speech recognition framework for automated voice services; Stage 1 (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## --- **Keywords**
+
+---
+
+LTE, UMTS, speech, stage 1
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|----------------------------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 7 |
+| 2.1 Normative References ..... | 7 |
+| 2.2 Informative References ..... | 7 |
+| 3. Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Requirements ..... | 9 |
+| 4.1 Initiation ..... | 9 |
+| 4.2 Information during the speech recognition session..... | 10 |
+| 4.3 Control..... | 10 |
+| 4.4 User Perspective (User Interface) ..... | 10 |
+| 5 UE and network capabilities ..... | 10 |
+| 6 Administration ..... | 11 |
+| 6.1 Authorization..... | 11 |
+| 6.2 Deauthorization ..... | 11 |
+| 6.3 Registration ..... | 11 |
+| 6.4 Deregistration ..... | 11 |
+| 6.5 Activation..... | 11 |
+| 6.6 Deactivation ..... | 12 |
+| 7 Service Provisioning ..... | 12 |
+| 8 Security ..... | 12 |
+| 9 Privacy ..... | 12 |
+| 10 Charging..... | 12 |
+| 11 Roaming..... | 13 |
+| 12 Interaction with other services ..... | 13 |
+| Annex A (informative): Speech recognition Framework-based automated voice service examples ..... | 14 |
+| Annex B (informative): Change History ..... | 15 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+Forecasts show that speech-driven services will play an important role on the 3G market. People want the ability to access information while on the move and the small portable mobile devices that will be used to access this information need improved user interfaces using speech input. At present, however, the complexity of medium and large vocabulary speech recognition systems is beyond the memory and computational resources of such devices. Also associated delay to download speech data files (e.g. grammars, acoustic models, language models, vocabularies etc. ...) may be prohibitive. Eventually, it may not always be acceptable for the speech service providers to allow download of these speech data files if they contained confidential information (password (security issue), customer names and address (privacy issue)) or intellectual properties; for example a well crafted speech grammar is often considered by speech service providers as a trade secret.
+
+Server-side processing of the combined speech and DTMF input and speech output can overcome these constraints by taking full advantage of memory and processing power as well as specialized speech engines and data files. However, the distortions introduced by the encoding used to send the audio between the client and the server as well as additional network errors can degrade the performance of the speech engines; therefore also limiting the achievable speech functionalities. A server-side speech service is generally equivalent to a phone call to an automatic service. As for any other telephony service, DTMF is a feature that should always be considered as needed.
+
+This document describes a generic speech recognition framework to distribute the audio sub-system and the speech services by sending encoded speech and meta-information between the client and the server. Instead of using a voice channel as in today's server-based speech services, an error-protected data channel will be used to transport encoded speech from the client audio sub-system (terminal client) to remote speech engines (on server) for processing (e.g. speech recognition, speaker recognition,). The speech recognition framework will also enable downlink data streaming of voice and recorded audio prompt generated by server to the terminal client audio subsystem. The speech recognition framework may use conventional codecs like AMR or Distributed Speech Recognition (DSR) optimized codecs.
+
+The speech recognition framework will provide users with a high performance distributed speech interface to server-based automatic speech services with communication, information access or transactional purposes.
+
+The types of supported user interfaces include those that are voice only, for example, automatic speech access to information, such as a voice portal described in this section. These typically support combined speech or DTMF input.
+
+In the future, a new range of multi-modal applications is also envisaged incorporating different modes of input (e.g. speech, keyboard, pen) and speech and visual output.
+
+# 1 Scope
+
+The present document defines the stage one description of the Speech Recognition Framework for Automated Voice Services. Stage One is the set of requirements for data seen primarily from the user's and service providers' points of view.
+
+This Technical Specification includes information applicable to network operators, service providers, terminal and network manufacturers.
+
+This Technical Specification contains the core requirements for the Speech Recognition Framework for automated voice services.
+
+The scope of this Stage 1 is to identify the requirements for 3G networks to support the deployments of a speech recognition framework - based automated voice services and therefore to introduce a 3GPP speech recognition framework as part of speech-enabled services. The Speech Recognition Framework for automated voice services is an optional feature in a 3GPP system.
+
+Figure 1 positions the Speech recognition Framework (SRF) with respect to other speech-enabled services as discussed in [6]. As illustrated, SRF is designed to support server-side speech recognition over packet switched network (e.g. IMS). As such SRF also enable configurations of multimodal and multi-device services that include distribute the speech engines.
+
+Note that it is possible to design speech-enabled services that alternate or combine the use of client-side only engines and SRF.
+
+
+
+```
+graph TD; SES[Speech-enabled Services] --> MS[Multimodal Services]; SES --> SOS[Speech-only Services]; MS <--> MDS[Multi-device Services]; MS --> CSSE[Client-side only Speech engines]; MS --> SSE[Server-side Speech engines]; SOS --> CSSE; SOS --> SSE; MDS --> CSSE; MDS --> SSE; SSE --> SRF[Speech Recognition Framework (Packet Switched)]; SSE --> CSR[Circuit Switched Speech Recognition]; SRF --> DSR[DSR optimized Codec]; SRF --> O[Other]; SRF --> CC[Conventional Codec]; CSR --> CC;
+```
+
+Figure 1: Positions the scope of the speech recognition framework as part of general speech enabled services. The diagram shows a hierarchy of services and engines. At the top is 'Speech-enabled Services', which branches into 'Multimodal Services' and 'Speech-only Services'. 'Multimodal Services' and 'Speech-only Services' both point to 'Client-side only Speech engines' and 'Server-side Speech engines'. 'Multi-device Services' is shown to the left of 'Multimodal Services' with a double-headed arrow, and it also points to 'Client-side only Speech engines' and 'Server-side Speech engines'. 'Server-side Speech engines' branches into 'Speech Recognition Framework (Packet Switched)' and 'Circuit Switched Speech Recognition'. 'Speech Recognition Framework (Packet Switched)' branches into 'DSR optimized Codec', 'Other', and 'Conventional Codec'. 'Circuit Switched Speech Recognition' also points to 'Conventional Codec'.
+
+**Figure 1 - Positions the scope of the speech recognition framework as part of general speech enabled services.**
+
+# 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*.
+
+## 2.1 Normative References
+
+- [1] 3GPP TS 21.133: "3G security; Security threats and requirements".
+- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [3] 3GPP TR 22.941: "IP based multimedia framework; Stage 0".
+- [4] 3GPP TS 22.105: "Services and service capabilities".
+- [5] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem; Stage 1".
+- [6] 3GPP TR 22.977: "Feasibility study for speech-enabled services".
+
+## 2.2 Informative References
+
+- [7] ETSI ES 201 108 v1.1.2: "Distributed Speech Recognition: Front-end Feature Extraction Algorithm; Compression Algorithm", April 2000.
+- [8] Void
+- [9] Void
+- [10] ETSI ES 202 050 v0.0.0 "Speech Processing, Transmission and Quality aspects (STQ); Distributed speech recognition; Advanced front-end feature extraction algorithm; Compression algorithms; DSR advanced front end", standard selected; document in preparation.
+
+# 3. Definitions and abbreviations
+
+Definitions and abbreviations used in the present document are listed in TR 21.905 [2]. For the purposes of this document the following definitions and abbreviations apply:
+
+## 3.1 Definitions
+
+**Automated Voice Services:** Voice applications that provide a voice interface driven by a voice dialog manager to drive the conversation with the user in order to complete a transaction and possibly execute requested actions. It relies on speech recognition engines to map user voice input into textual or semantic inputs to the dialog manager and mechanisms to generate voice or recorded audio prompts (text-to-speech synthesis, audio playback,). It is possible that it relies on additional speech processing (e.g. speaker verification). Typically telephony-based automated voice services also provide call processing and DTMF recognition capabilities. Examples of traditional automated voice services are traditional IVR (Interactive Voice Response Systems) and VoiceXML Browsers.
+
+**Barge-in event:** Event that takes place when the user starts to speak while audio output is generated.
+
+**Conventional Codec:** The module in UE that encodes the speech input waveform , similar to the encoder in a vocoder e.g. EFR, AMR.
+
+**Downlink exchanges:** Exchanges from servers and networks to the terminal.
+
+**Dialog manager:** A technology to drive a dialog between user and automated voice services. For example a VoiceXML voice browser is essentially a dialog manager programmed by VoiceXML that drives speech recognition and text-to-speech engines.
+
+**DSR Optimised Codec:** The module in UE which takes speech input, extracts acoustic features and encodes them with a scheme optimised for speech recognition. This module is similar to the conventional codec, such as AMR. On the server-side, the uplink encoded stream can be directly consumed by speech engines without having to be converted to a waveform.
+
+**Meta information:** Data that may be required to facilitate and enhance the server-side processing of the input speech and facilitate the dialog management in an automated voice service. These may include keypad events over-riding spoken input, notification that the UE is in hands-free mode, client-side collected information (speech/no-speech, barge-in), etc....
+
+**Speech Recognition Framework:** A generic framework to distribute the audio sub-system and the speech services by sending encoded speech between the client and the server. For the uplink, it can rely on conventional (ASR) or on DSR optimised codecs where acoustic features are extracted and encoded on the terminal.
+
+**Speech Recognition Framework-based Automated Voice Service:** An automated voice service utilising the speech recognition framework to distribute the speech engines from the audio sub-system. In such a case the user voice input is captured and encoded, with a conventional or a DSR optimised for speech recognition as negotiated at session initiation. The encoded speech is streamed uplink to server-side speech engines that process it. The application dialog manager generates prompts that are streamed downlink to the terminal.
+
+**SRF Call:** An uninterrupted interaction of a user with an application that relies on SRF-based automated voice services.
+
+**SRF Session:** Exchange of audio and meta-information, explicitly negotiated and initiated by the SRF session control protocols, between terminal (audio-sub-systems) and SRF-based automated voice services. Sessions last until explicitly terminated by the control protocols.
+
+**SRF User Agent:** a process within a terminal that enables the user to select a particular SRF-based automated voice service or to enter the address of a SRF-based automated voice service. The user agent converts the user input or selection into a SIP IMS session initiation with the corresponding SRF-based automated voice service. The user agent can also terminate the session with the service when the user device to disconnect.
+
+**Text-to-Speech Synthesis:** A technology to convert text in a given language into human speech in that particular language.
+
+**Uplink exchanges:** Exchanges from the mobile terminal to the server / network.
+
+## 3.2 Abbreviations
+
+For the purposes of this document the following abbreviations apply:
+
+AMR – Adaptive Multi Rate
+
+DSR – Distributed Speech Recognition
+
+DTMF – Dual Tone Multi-Frequency
+
+IETF – Internet Engineering Task Force
+
+IMS – IP Multimedia Subsystem
+
+IVR – Interactive Voice Response system
+
+PCM – Pulse Coded Modulation
+
+PIM - Personal Information Manager
+
+SIP – Session Initiation Protocol
+
+SRF – Speech Recognition Framework
+
+URI – Uniform Resource Identifier
+
+# --- 4 Requirements
+
+A 3GPP speech recognition framework enables the use of conventional codecs (e.g. AMR) or DSR optimized codecs to distribute in the network the speech engines that process speech input or generate speech output. It includes:
+
+- Default uplink and downlink codec specifications.
+- A stack of speech recognition protocols to support:
+ - Establishment of uplink and downlink sessions, along with codec negotiation
+ - Transport of speech recognition payload (uplink) with conversational QoS
+ - Support of transport (also at conversational QoS) of meta-information required for the deployment of speech recognition applications between the terminal and speech engines (meta-information may include terminal events and settings, audio sub-system events, parameters and settings, etc.).
+
+IMS provides a protocol stack (e.g. SIP/SDP, RTP and QoS), that may advantageously be used to implement such capabilities.
+
+It shall be possible to recommend a codec to be supported by default to deploy services that rely on the 3GPP speech recognition framework. To that effect, the specifications will consider either conventional speech codecs (e.g. AMR) or DSR optimized codecs.
+
+ETSI has published DSR optimized codecs specifications (ETSI ES 201 108 & ETSI ES 202 050 [7, 10]) and a payload format for transport of DSR data over RTP (IETF AVT DSR).
+
+The following list gives the high level requirements for the SRF-based automated voice services: .
+
+- Users of the SRF-based automated voice service shall be able to initiate voice communication, access information or conduct transactions by voice commands using speech recognition. Examples of SRF-based automated voice services are provided in Appendix A.
+
+The speech recognition framework for automated voice services will be offered by the network operators and will bring value to the network operator by the ability to charge for the SRF-based automated voice services.
+
+This service may be offered over a packet switched network; however in general this requires specification of a complete protocol stack. When this service is offered over the IMS, the protocols used for the meta information and front-end parameters (from terminal to server) and associated control and application specific information can and shall be based on those in IMS.
+
+## 4.1 Initiation
+
+It shall be possible for a user to initiate a connection to the SRF-based automatic voice services by entering the identity of the service. Most commonly, when used as a voice service, this will be performed by entering a phone number. However, particular terminals may offer a user agent that accepts other addressing schemes to be entered by the user: IP address, URI, e-mail address possibly associated to a protocol identifier. This is particularly important for multi-modal usages.
+
+In all cases, the terminal will convert the address entered by the user to initiate a session via the SIP IMS session initiation protocol and establish the different SRF protocols. During this initiation of the SRF session, it shall be possible to negotiate the uplink and downlink codecs. The terminal shall support a codec suitable for speech recognition as a default uplink codec.
+
+## 4.2 Information during the speech recognition session
+
+Codec negotiation during a SRF session should be optionally supported.
+
+This may be motivated by the expected or observed acoustic environment, the service package purchased by the user, the user profile (e.g. hands-free as default) or service need. The user speaks to the service and receives output back from the automated voice service provider as audio (recorded 'natural' speech) or Text-to-Speech Synthesis. The output from the server can be provided in the downlink as a streaming service or by using conversational speech codec.
+
+Additional control and application specific information shall be exchanged during the session between the client and the service. Accordingly some terminals shall be able to support sending additional data to the service (e.g. keypad information and other terminal and audio events) and receiving data feedback that shall be displayed on the terminal screen.
+
+Dynamic payload switches within a session may be considered to transport meta-information.
+
+## 4.3 Control
+
+It shall be possible to use SRF sessions in order to provide access to SRF-based automated voice services. For example applications might use a SRF session to access and navigate within and between the various SRF-based automated voice services by spoken commands or pressed keypads.
+
+It shall be possible for network operators to control access to SRF-based automated voice services based on subscription profile of the callers.
+
+## 4.4 User Perspective (User Interface)
+
+The user's interface to this service shall be via the UE. User can interact by spoken and keypad inputs. The UE can have a visual display capability. When supported by the terminal, the server-based application can display visual information (e.g., stock quote figures, flight gates and times) in addition to audio playback (via recorded speech or text-to-speech synthesis) of the information. These are examples of multimodal interfaces. SRF enables distributed multimodal interfaces as described in [6].
+
+# --- 5 UE and network capabilities
+
+In addition to the capabilities required for IMS Basic Voice session (such as the default voice codec that will be used for the downlink audio prompt stream), the following SRF-based automated voice service-specific capabilities shall be required in the UE and network:
+
+- A default uplink codec (conventional codec or DSR optimized codec).
+- A downlink conventional codec and downlink streaming capabilities (simultaneous with uplink).
+- The capability to transmit keypad information from the client to the server (e.g., either DTMF or the keypad string).
+- The capability to reconstruct encoded speech. The reconstruction requirement does not apply to the UE.
+
+It shall be possible to enable application specific information exchanges between the client and the server (e.g. client events (e.g. barge-in events), display information, etc...), in the form of speech meta-information. It shall be possible to enable these exchanges with conversational QoS.
+
+SRF shall be supported by an uplink channel available in GERAN and UTRAN networks for the transport of the codec payload and with QoS (Quality of Service) for conversational class, streaming and interactive QoS services as specified in TS 22.105 [4].
+
+It shall be possible for the network to distinguish a SRF session from a basic voice session (e.g. for charging purposes).
+
+# --- 6 Administration
+
+SRF-based automated voice services may be provided by the network operator (home or visited) or by third parties. See appendix A for examples of such services.
+
+The administration of the SRF-based automated voice services will be under the control of the network operator. But when decided to do so by the network operator, it should be possible to the third party providers to administer the SRF-based automated voice services themselves through the gateway that they would connect to IMS. In such case, the third party provider performs all the administrative steps and no registration would be required with the network operator.
+
+## 6.1 Authorization
+
+Authorization for use of SRF-based automated voice services will be under the control of the network operator. It shall require authorization of the connection to IMS.
+
+The network operators can provide automated voice services or they can only provide the network that connects users to SRF-based automated voice services provided by third party application service providers. The network operator shall be able to permit or prevent access to a third party service. This requirement shall be treated as equivalent to allowing or prevent access to some phones numbers (IMS voice sessions) or internet services (domains for example in WAP data access).
+
+The network operator shall be able to administer the authorization of a SRF-based automated voice service on a user basis as well as on a service basis (e.g. to authorize access to all users or prevent access to all users).
+
+It shall be possible for the operator to provide for the user:
+
+- Authorization to access a particular "address" (e.g. 3rd party SRF-based automated voice service)
+- Authorization to use a service that the operator authorize access to when the 3rd party operator wishes to rely on the operator to control this access
+
+It shall be possible for the third party provider to authorize usage of its services based on the identity of the user.
+
+## 6.2 Deauthorization
+
+Deauthorization for use of the SRF-based automated voice services shall be under the control of the network operator as for the authorization described in section 6.1.
+
+## 6.3 Registration
+
+Authorized SRF-based automated voice service register their address with the IMS upon authorization of the service authorized SRF-based automated voice service can then be reached by the user (by entering address and initiated a SRF session).
+
+## 6.4 Deregistration
+
+Disconnection from the IMS shall prevent the use of the SRF-based automated voice service. Deregistration may be decided by the third party provider.
+
+## 6.5 Activation
+
+Once authorized and registered a SRF-based automated voice service is deemed activated as for other IMS services.
+
+## 6.6 Deactivation
+
+Deactivation shall be done by deregistering the services (operator or service provider initiative) or by refusing to initiate a SRF session (service provider initiative).
+
+# --- 7 Service Provisioning
+
+The SRF-based automated voice services shall be able to be provisioned by either the network operator (roaming or home) or by a 3rd party service provider.
+
+It shall be possible for network operators and 3rd party service providers to offer SRF-based automatic voice services by providing identity of service, such as a phone number, an IP address or a URI that the user can enter or select on the terminal.
+
+# --- 8 Security
+
+The "Security Threats and Requirements" specified in 21.133 [1] shall not be compromised.
+
+It shall be possible to deny unauthorized access to 3GPP SRF-based automated voice services. An authorization may be based on the following,
+
+- identity of the accessing user agent, server or device
+- the destination user, device or user agent
+
+Third parties shall have authorization from the User and PLMN Operators in order to access 3GPP SRF-based automated voice services.
+
+It shall be possible to reconstitute PCM samples from DSR packets so that the user's spoken command can be transcribed at a later time, if required.
+
+# --- 9 Privacy
+
+For SRF-based automated voice services, privacy requirements shall be at least as good as for IMS voice or data sessions [5]:
+
+- It shall be possible to encrypt speech and speech meta-data exchanges;
+- It shall be possible to prevent exchange of the user's true identity, location and other terminal or user related information when required.
+
+SRF-based automated voice services, may imply that the service provider collects information about the user or usage. This information should be treated according to the policies in place for data and voice (e.g. human to operator or human to automated service) services. The SRF-based automated voice services shall not add additional privacy risks.
+
+# --- 10 Charging
+
+The user can be charged for sessions with SRF-based automated voice services in a variety of ways. The following shall be possible:
+
+- a) By duration of session (including "one-off" charge/flat rate)
+- b) By data volume transferred (number of packets) or other similar criteria.
+- c) By subscription fees for the service (unlimited usage or unlimited usage up to a point and then per-use fees)
+
+- d) Free (e.g. with the service being subsidised by advertising revenue from advertisement spots). The advertisement spots may be inserted either at session start-up or close, or designed in such that system delay time is masked (e.g., while the user is waiting for the flight schedules to be returned, or a purchase transaction to be completed). The network operator will receive revenue from users directly as well as from the content and service providers who want their sites to be accessible via the automated voice service, and from advertisers. Advertising spots can be inserted at appropriate points during the session (e.g., at the beginning of the session, while the user is waiting for a system response, or at the end of a session).
+
+SRF-based automated voice services shall be available to pre-paid and post-paid subscribers.
+
+# --- 11 Roaming
+
+The user shall be able to utilize SRF-based automated voice services when roaming in any IMS compatible mobile network.
+
+The capabilities of the SRF-based automated voice service shall be available in the roamed-to network in the same manner as in the home network, within the limitation of the capabilities of the serving network.
+
+# --- 12 Interaction with other services
+
+No interaction with other services identified. When connected to the IMS, other IMS services are available to the user through the terminal.
+
+Other services (non IMS voice etc..) may be available with or without disconnecting from the IMS.
+
+# --- Annex A (informative): Speech recognition Framework-based automated voice service examples
+
+Examples of Automated Voice Services include:
+
+- Communication assistance (Name dialling, Service Portal, Directory assistance)
+- Information retrieval (e.g., obtaining stock-quotes, checking local weather reports, flight schedules, movie/concert show times and locations)
+- M-Commerce and other transactions (e.g., buying movie/concert tickets, stock trades, banking transactions)
+- Personal Information Manager (PIM) functions (e.g., making/checking appointments, managing contacts list, address book, etc.)
+- Messaging (IM, unified messaging, etc...)
+- Information capture (e.g. dictation of short memos)
+- A usage scenario for multimodal applications with a GUI user agent on the terminal synchronized with an SRF automated voice service.
+
+# Annex B (informative): Change History
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|-----|-----|-------|-----|--------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| | | | 22.243 | | | | | Initial draft based on content of TR 22.941 | | 0.0.1 | |
+| | | | 22.243 | | | | | Output of ad-hoc drafting session | | 0.0.2 | |
+| | | | 22.243 | | | | | Presented to TSG SA#14 for information | 0.0.2 | 1.0.0 | |
+| | | | 22.243 | | | | | Reviewed in SWG DSR 14 Jan 2002 | 1.0.0 | 1.1.0 | |
+| | | | 22.243 | | | | | Reviewed again in SWG DSR 14 Jan 2002 | 1.1.0 | 1.2.0 | |
+| | | | 22.243 | | | | | Contribution to 1.2.0 to address open issues | 1.2.0 | 1.3.0 | |
+| | | | 22.243 | | | | | Update to 1.3.0 to address comments at DSR SWG (Sophia Antipolis) | 1.3.0 | 1.4.0 | |
+| | | | 22.243 | | | | | Update to 1.4.0 to reflect the new SRF terminology. | 1.4.0 | 1.5.0 | |
+| | | | 22.243 | | | | | Update to 1.5.0 to reflect changes agreed to in SWG mtg in Rome. | 1.5.0 | 1.6.0 | |
+| | | | 22.243 | | | | | Update to 1.6.0 to reflect and update according to the agreements in SES SWG in Rome | 1.6.0 | 1.6.1 | |
+| | | | 22.243 | | | | | Updated to reflect changes agreed to in SES SWG in Durango | 1.6.1 | 1.7.0 | |
+| | | | 22.243 | | | | | Updated for presentation to SA #17 | 1.7.0 | 2.0.0 | |
+| SP-17 | SP-020572 | | 22.243 | | | Rel-6 | | Presented to SA for approval | 2.0.0 | 6.0.0 | |
+| SP-18 | SP-020664 | S1-021928 | 22.243 | 001 | | Rel-6 | F | CR to TS 22.243 Removal of references | 6.0.0 | 6.1.0 | SRSES |
+| SP-19 | SP-030031 | S1-030151 | 22.243 | 003 | - | Rel-6 | F | Correction of contradictory information (former: 'Removal of references') | 6.1.0 | 6.2.0 | SRSES |
+| SP-20 | SP-030260 | S1-030431 | 22.243 | 004 | - | Rel-6 | F | UE and network capabilities | 6.2.0 | 6.3.0 | SRSES |
+| SP-20 | SP-030260 | S1-030432 | 22.243 | 005 | - | Rel-6 | C | Addition of Streaming and interactive QoS | 6.2.0 | 6.3.0 | SRSES |
+| SP-21 | SP-030468 | S1-030974 | 22.243 | 007 | - | Rel-6 | B | Reconstructed speech as an output mechanism | 6.3.0 | 6.4.0 | SRSES |
+| SP-36 | | | 22.243 | | | Rel-7 | | Updated from Rel-6 to Rel-7 | 6.4.0 | 7.0.0 | |
+| SP-42 | - | - | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2019-07 | - | - | - | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22246/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22246/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d071b557c8648bb111295a969536da818767566
--- /dev/null
+++ b/marked/Rel-18/22_series/22246/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4651ada5d7b3a7210a04d8d6333a8f5c9d47e59248eb82cadf46b1e2ef862726
+size 8253
diff --git a/marked/Rel-18/22_series/22246/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22246/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc6bc4f813adced92c024b660eb55ff5795770bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22246/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15fd4ae7c319660070fc3dfc8ffa883ed6d9d537e4ba645f4999849854f69b74
+size 7354
diff --git a/marked/Rel-18/22_series/22246/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-18/22_series/22246/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46174341d7df8d699fd5dced93079f91ff4a3f24
--- /dev/null
+++ b/marked/Rel-18/22_series/22246/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f159d4b557cce08568345f7aecbfb99547694f73b82a70e11f9082fa083eaf5
+size 76888
diff --git a/marked/Rel-18/22_series/22246/raw.md b/marked/Rel-18/22_series/22246/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..20980ec4ae946e91286a090a0154c0799ec8c536
--- /dev/null
+++ b/marked/Rel-18/22_series/22246/raw.md
@@ -0,0 +1,572 @@
+
+
+# 3GPP TS 22.246 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font, with a red signal wave icon below the 'G' and a 'TM' symbol to the right.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, broadcast, multimedia, stage 1
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+### --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|---------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Classification of MBMS User Services ..... | 6 |
+| 5 High level requirements ..... | 7 |
+| 5.0 General ..... | 7 |
+| 5.1 Common requirements to broadcast and multicast ..... | 9 |
+| 5.2 Interoperability ..... | 10 |
+| 5.2a Pre-Delivery verification..... | 10 |
+| 5.3 Delivery verification ..... | 11 |
+| 6 MBMS User Service requirements ..... | 11 |
+| 6.1 Charging..... | 11 |
+| 6.2 Security..... | 11 |
+| 6.3 Privacy..... | 11 |
+| 6.4 Quality of service ..... | 11 |
+| 6.5 Subscription..... | 12 |
+| 6.6 Availability..... | 12 |
+| Annex A (informative): Use Cases..... | 13 |
+| Annex B (informative): Example service scenarios ..... | 15 |
+| B.1 Text notification service..... | 15 |
+| B.2 Local Area Information distribution (Case A)..... | 15 |
+| B.3 Local Area Information distribution (Case B)..... | 15 |
+| B.4 Multicast distribution ..... | 15 |
+| B.5 Audio Distribution..... | 16 |
+| B.6 General Content Distribution ..... | 16 |
+| B.7 Software Download..... | 16 |
+| Annex C (informative): Change history..... | 17 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+TS 22.146 [2] specifies the multimedia broadcast and multicast service (MBMS) application independent transport service and includes some guidance on application services and bit rates. The present specification defines MBMS User Services that use the capabilities of MBMS. Service related information is defined in this specification to specify requirements in terms of data rates, quality of service requirements, typical volumes of data etc.
+
+MBMS User Services may be delivered to a user at different bit rates and quality of service depending on radio networks and conditions. This technical specification describes service scenarios for MBMS User Services.
+
+In addition scenarios related to security and charging are described providing information for detailed MBMS User Services security and charging mechanisms to be specified. The service scenarios described in this specification are not exhaustive, it is possible that MBMS may be used for services that are not included in this specification. The present specification describes the minimal requirements for interoperability for MBMS based services. This specification establishes a basis which can also be used for future services.
+
+# --- 1 Scope
+
+The present document describes MBMS User Services that use the capabilities of MBMS. Application scenarios including charging, QoS aspects and related service requirements derived from them are described. These scenarios and service requirements can be used as guidance for the design of codecs and bearers.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP specifications".
+- [2] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service".
+- [3] 3GPP TS 26.140: "Multimedia Messaging Service (MMS): Media formats and Codecs".
+- [4] 3GPP TS 26.134: "Transparent end-to-end Packet-switched Streaming Service (PSS) Protocols and codecs".
+- [5] 3GPP TS 22.240 "Service requirement for the 3GPP Generic User Profile (GUP)".
+- [6] 3GPP TS 22.242: "Digital Rights Management".
+- [7] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) Access Reference Configuration".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the definitions in 3GPP TR 21.905 [1] as well as the following definitions apply.
+
+**Broadcast service area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Local Broadcast Area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Broadcast mode:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Broadcast service:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Broadcast session:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**MBMS transport service:** A MBMS transport service is either a broadcast service or a multicast service as defined in TS 22.146 [2].
+
+**MBMS User Services:** Services that are intended to be delivered to multiple users simultaneously. MBMS User Services use the capabilities of the MBMS application independent transport.
+
+**Media types:** a media type refers to one form of presenting information to a user, e.g. voice or fax.
+
+**Mobile Station (MS):** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast transmission activation:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast service area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Local multicast area:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast mode:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast joining:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast session:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multimedia Broadcast/Multicast Service (MBMS):** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast group:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast service:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast subscription:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**Multicast Subscription Group:** see TS 22.146: "Multimedia Broadcast/Multicast Service" [2].
+
+**User Equipment:** defined in TS 21.905. An occurrence of a User Equipment is an MS for GSM as defined in TS 24.002 [7].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|------|----------------------------------------|
+| MBMS | Multimedia Broadcast/Multicast Service |
+| MS | Mobile Station |
+| PSS | Packet-switched Streaming Service |
+| UE | User Equipment |
+
+# 4 Classification of MBMS User Services
+
+There exist many services and applications that can be provided over the application independent MBMS transport [2]. It is not necessary to standardise specific end user services because the deployment of particular applications and services over the capabilities provided by the 3GPP system is operator specific and outside the scope of standardisation. However, it is possible to classify MBMS User Services according to the method used to distribute these services.
+
+There are four types of MBMS User Service considered within this specification.
+
+### - Streaming services
+
+A continuous data flow providing a stream of continuous media (i.e. audio and video) is a basic MBMS User Service. Like digital video broadcasting, supplementary information of text and/or still images (static media) is also important. For example, if text includes URLs of some content on the Internet, a user can easily access the content without entering the URL for herself. Still images may also be used for banner images that advertise some product or service. These static media need to be synchronized and displayed with audio/video streams.
+
+Note: Streaming in the context of MBMS User Services may not be the same as that described e.g. within PSS [4].
+
+### - File download services
+
+This service delivers binary data (file data) over an MBMS bearer. An MBMS client (i.e. UE) activates an appropriate application, and utilises the delivered data. The most important functionality for this service is reliability. In other words, it is necessary that the user receive all the data sent in order to experience the service.
+
+- Carousel services
+
+Carousel is a service that combines aspects of both the Streaming and File download services described above. Similar to the streaming service this service includes time synchronisation. However, the target media of this service is only static media (e.g. text and/or still images). Time synchronization with other media is also required. For example, text objects are delivered and updated from time to time. Still images may also be collated to display low frame-rate video. In common with the download service this service also includes reliability (typically 100% reliability is not always necessary). The benefit of this service is that it is possible over a low bit-rate bearer.
+
+An example of an application utilising the Carousel service is a 'ticker-tape' type service in which the data is provided to the user repetitively and updated at certain times to reflect changing circumstances.
+
+- Television (TV) service
+
+The Television service is an MBMS service consisting of synchronised streaming audio and visual components.
+
+# --- 5 High level requirements
+
+## 5.0 General
+
+MBMS user services are services an operator may provide to subscribers. MBMS user services use the capabilities of MBMS. The operator may provide such services on his own or in collaboration with third party service providers. In addition, an MBMS user service may be provided to the operator's own subscribers and/or to inbound roaming subscribers from other operators.
+
+### MBMS User Services
+
+MBMS user services are based on broadcast- or multicast services, which are defined in TS 22.146 [2].
+
+MBMS user services shall be bearer agnostic to enable access via generic IP access systems.
+
+An MBMS user service may use one or more broadcast- or multicast services at a time within the MBMS service area bound to this user service.
+
+- Note 1: A single broadcast- or multicast service can only have one broadcast- or multicast session at any time within the MBMS service area bound to this user service. A broadcast- or multicast service may consist of multiple successive broadcast- or multicast sessions. (see TS 22.146 [2])
+- Note 2: As part of the same multicast service, it should be possible for the operator to provide the UEs with multiple successive sessions with different quality-of-service for each session. (see TS 22.146 [2])
+
+
+
+The diagram illustrates the mapping of MBMS transport services to MBMS user services over time. The horizontal axis represents time, indicated by an arrow at the bottom labeled "time".
+
+- MBMS transport service 1 (multicast)** carries a **text session**. It is mapped to **MBMS user service X** (green box).
+- MBMS transport service 2 (multicast)** carries an **audio session**. It is mapped to **MBMS user service Y** (yellow box).
+- MBMS transport service 3 (multicast)** carries a **text session** and a **video session**. It is mapped to **MBMS user service Y** (yellow box).
+- MBMS transport service 4 (broadcast)** carries an **audio session**. It is mapped to **MBMS user service Z** (cyan box).
+
+Brackets on the right side of the diagram group the transport services and their sessions to the corresponding user services: Service X uses services 1 and 2; Service Y uses services 2 and 3; Service Z uses service 4.
+
+Diagram illustrating the mapping of MBMS transport services to MBMS user services over time. The diagram shows four transport services: MBMS transport service 1 (multicast) with a text session, MBMS transport service 2 (multicast) with an audio session, MBMS transport service 3 (multicast) with text and video sessions, and MBMS transport service 4 (broadcast) with an audio session. These are mapped to three user services: X (green), Y (yellow), and Z (cyan). A horizontal arrow at the bottom indicates the progression of time.
+
+It shall be possible for an MBMS user service to make use of different application independent MBMS transport services at different times or in parallel. The MBMS transport services used may vary for instance in QoS parameters or target broadcast or multicast area.
+
+It shall be possible for one application independent MBMS transport service to be used by more than one MBMS user service at a time.
+
+If an MBMS user service makes use of several application independent MBMS transport services then these may only consist of either broadcast or multicast services, but not of a combination of both.
+
+Note: The combination of broadcast- or multicast services in future releases is FFS
+
+When necessary, within a single MBMS user service, it shall be possible to synchronize the media sessions.
+
+NOTE: For different application independent MBMS transport services to support a single MBMS user service it may be necessary to logically link the transport services to each other, as illustrated in the figure for the audio- and video session of MBMS user service X.
+
+The UTRAN, GERAN and E-UTRAN accesses shall provide protection against normal transmission errors (eg interference not related to cell changes and handovers).
+
+Non 3GPP access system used to transport MBMS user services should provide protection against normal transmission errors (e.g. interference not related to cell changes and handovers).
+
+The BM-SC is responsible for providing protection e.g. FEC, long interleaving and/or point to point repairing the transmission, against errors (eg those caused by cell changes and longer breaks in transmission).
+
+### Service examples
+
+MBMS user services may be classified according to the table within Annex A of this specification into several service examples, which are characterized by
+
+- Their predominant broadcast- or multicast service, that constitutes this MBMS user service together with its reliability (QoS) and data transfer rate requirements
+- Media types that are transmitted via this broadcast- or multicast service
+- Type of the service, which implies handling of the distributed media by the UE (e.g. download for subsequent presentation, streaming for instant presentation or carousel downloading)
+- Charging characteristics
+- A potential requirement for point-to-point delivery verification for delivered content.
+
+To express the requirements for standardised service types are one objective of the present specification.
+
+### Service classes
+
+MBMS user services may be provided for many purposes to the user and may convey information of various kinds. E.g. some services may be used for traffic information, others for entertainment or for news services. Service classes denote a classification of MBMS user services according to their usage. However, service class values are not in the scope of 3GPP standardisation but may be subject of inter-operator service arrangements.
+
+## 5.1 Common requirements to broadcast and multicast
+
+The following list describes requirements on an application level:
+
+### Service classes
+
+In case of roaming a user shall be able to enjoy services as follows:
+
+- A user shall be able to activate services that are provided locally in the visited network, as allowed by the user's home environment (e.g. local tourist information).
+- A user subscribed to a service class in the HPLMN shall be able to enjoy equivalent services in the same service class as provided by a visited PLMN without explicit subscription in the VPLMN (e.g. weather forecast).
+
+A user subscribed to a service class in the HPLMN shall be able to have access to home contents provided via a visited PLMN without explicit subscription in the VPLMN (e.g. enjoy subscribed service while roaming)
+
+#### Service Interworking
+
+The user shall be able to manipulate content delivered over MBMS and forward it using other services (e.g. MMS, Speech Call- and IMS signalling, Hyperlinks, ....). Care should be taken in order to fulfil requirements concerning DRM and respective barring and charging capabilities.
+
+When interacting with user profiles, MBMS User Services shall use the mechanisms described in [5] TS 22.240 (Generic User Profile).
+
+#### Content storage in the UE
+
+It shall be possible for the UE to store content delivered to it over MBMS and provide it to the user at a later time. Care should be taken in order to fulfil requirements concerning DRM and respective charging capabilities.
+
+#### Data formats and types
+
+Media types shall be supported independent of specific data types and formats behind..
+
+As a minimum MBMS User Services shall support the following media types:
+
+- Text
+It shall be possible to embed hyperlinks and to decorate text within content provided by MBMS User Services.
+- Still Images
+
+- Video
+- Speech
+- Mono/Stereo Audio
+
+Data format and data types as being used by other multimedia services shall be supported for interoperability reasons.
+
+Note : It is not intended to constrain MBMS to existing codec technologies. The intention is to maintain consistency with other multimedia services whilst also allowing for adoption of new codec technologies as appropriate.
+
+#### **Digital Rights Management**
+
+The MBMS User Service shall be able to control content distribution as defined in 3GPP TS 22.242 [6]. MBMS content providers shall be able to invoke DRM to prevent unauthorized copying and forwarding of content.
+
+#### **Notification of required capabilities**
+
+The capabilities (e.g. memory size) required to receive a particular transmission shall be notified in advance by the network or service centre.
+
+#### **MBMS Television Service**
+
+It shall be possible for a user to select between different content within the MBMS Television Service.
+
+The MBMS service shall add no more than 1 second when switching between different TV streams to any delay introduced with regards to the coding of the TV stream.
+
+It shall be possible for an operator to configure the MBMS Television service so that the typical switching time, from the end user's perspective, does not exceed 2 seconds.
+
+Handover within the same radio access technology shall be transparent to the user.
+
+Handover between different radio access technologies should be performed without any user perceived interruption.
+
+Note: The quality of the MBMS Television service may change depending on the capabilities of the target network.
+
+## **5.2 Interoperability**
+
+MBMS User Services shall ensure service interoperability with respect to media formats and codecs, at the same time being able to re-use existing multimedia capabilities in the UE as far as possible.
+
+Therefore MBMS User Services shall support a minimum set of media formats and codecs. This minimum set should be aligned with the set of media formats and codecs required for MMS [3] and PSS [4].
+
+## **5.2a Pre-Delivery verification**
+
+It is required that the operator can verify the number of active MBMS users when service commences.
+
+The UE shall provide a secure means to inform the network of the start of services by pre-delivery verification transmitted over a point-to-point connection to the home/visited network. This pre-delivery verification may be relayed to the service provider. The pre-delivery verification shall also support the carriage of bearer specific non-real time information, i.e. previously stored in the UE, to the BM-SC. Such bearer specific information may, for example, include historic C/I measurements for the serving cell.
+
+It should be noted that pre-delivery verification by point-to-point mechanisms partially reduces the resource-efficiency of the underlying broadcast services. Sacrificing resource-efficiency due to requirements of UE reporting may be necessary but should be kept as minimal as possible to minimize congestion.
+
+## 5.3 Delivery verification
+
+For some MBMS user services it is required that the operator can verify that the content conveyed by the service has been received by the UE.
+
+The UE shall provide a secure means to provide such delivery verification transmitted over a point-to-point connection to the home/visited network. This delivery verification may be relayed to the service provider.
+
+The delivery verification shall also support the carriage of bearer specific non-real time information, i.e. previously stored in the UE, to the BM-SC. Such bearer specific information may, for example, include historic C/I measurements for the serving cell.
+
+It should be noted that delivery verification by point-to-point mechanisms partially reduces the resource-efficiency of the underlying broadcast services. Sacrificing resource-efficiency due to requirements of UE reporting may be necessary but should be kept as minimal as possible to minimize congestion.
+
+# --- 6 MBMS User Service requirements
+
+## 6.1 Charging
+
+The MBMS User Service shall support standardized mechanisms to transfer charging related information.
+
+It shall be possible to charge for MBMS content the user receives while roaming in a VPLMN.
+
+As indicated in Annex A some services will require an indication that MBMS content has been received. Therefore it shall be possible for the UE to provide such an indication.
+
+The MBMS User Service shall support the following charging mechanisms :
+
+- Charging on a subscription basis
+- Charging for keys that allow the user access to the data
+
+## 6.2 Security
+
+The following security aspects shall be taken into account:
+
+Any user modifiable MBMS service data (e.g. storage of deliveries in the UE, data type and format specific behaviours etc) shall only be modified by the authenticated user (see also 4.1.1 above).
+
+## 6.3 Privacy
+
+Third parties and VASP should not be aware about user IDs for MBMS subscriptions unless explicitly allowed by the operator.
+
+## 6.4 Quality of service
+
+It should be possible for the operator to collect statistical data such as lost frames, assigned resources, bit-rates achieved etc.
+
+It shall be possible for the operator to adapt the distribution of a MBMS user service consisting of different MBMS transport services to provide multiple QoS levels according to the QoS resources provided by the access network(s), while maintaining the resource efficiency of the underlying MBMS transport services.
+
+Note: It is necessary that an MBMS user service, consisting of different MBMS transport services providing multiple QoS levels, can be received by all MBMS-capable terminals.
+
+It shall be possible to base the adaptation of the distribution of a MBMS user service to the QoS resources provided by the access network(s) on:
+
+- the QoS resources within the same access network (e.g. UTRAN).
+- the QoS resources provided by different access networks (e.g. UTRAN and GERAN).
+
+It shall be possible to adapt the distribution of an ongoing MBMS user service to persistently changed QoS resource conditions in the access network(s).
+
+Adaptation of the distribution of a MBMS user service to the QoS resources in different access networks or parts of the same access network shall not affect the QoS of the MBMS user service in other access networks or other parts of the same access network.
+
+## 6.5 Subscription
+
+During the lifetime of subscription to a Multicast Service it shall be possible for the user to declare the service preferences. It shall be possible for the network to store the user settings e.g. using GUP.
+
+## 6.6 Availability
+
+The user should be able to receive MBMS user services via generic IP access systems.
+
+Note: The transport of MBMS user services over non 3GPP accesses is out of scope of 3GPP, however if the non 3GPP access system has multicast or broadcast capabilities these should be utilised if possible.
+
+# Annex A (informative): Use Cases
+
+| Service Example | Media | Distribution Scope | MBMS User Service Classification | Application Bit rate Note 1 | Delivery Verification Required Note 3 | User Charging Note 4 |
+|--------------------------------------------------------------|------------------------------------------------------|----------------------|----------------------------------|-----------------------------|---------------------------------------|-------------------------------|
+| Reliable text distribution (eg Local news) | Text | Multicast | Download | Up to 10 kbps | Yes | Event |
+| Unverified text distribution | Text | Multicast, Broadcast | Carousel, download | Up to 10 kbps | No | - |
+| Text distribution with still images and/or low quality video | Text, Still images, Video (e.g. 3fps) | Multicast, Broadcast | Carousel, download | Up to 32 kbps | Service dependent | User service dependent Note 2 |
+| Audio streaming | Stereo Audio | Multicast | Streaming | Up to 48kbps | Service dependent | - |
+| Audio streaming | Stereo Audio | Broadcast | Streaming | Up to 48kbps | No | - |
+| Audio download | Stereo Audio | Broadcast | Download | Up to 48kbps | Service dependent | - |
+| Audio download | Stereo Audio | Multicast | Download | Up to 48kbps | Yes | Event |
+| Audio distribution with low quality video | Stereo Audio, Video (e.g. 3fps) | Broadcast | Streaming | Up to 128kbps Note 5 | No | - |
+| Audio distribution with low quality video | Stereo Audio, Video (e.g. 3fps) | Multicast | Streaming | Up to 128kbps Note 5 | Service dependent | - |
+| Audio distribution with low quality video | Stereo Audio, Video (e.g. 3fps) | Broadcast | Download | Up to 128kbps Note 5 | Service dependent | - |
+| Audio distribution with low quality video | Stereo Audio, Video (e.g. 3fps) | Multicast | Download | Up to 128kbps Note 5 | Yes | Event |
+| Video streaming | Video & supplementary data (e.g. text, still images) | Broadcast | Streaming | Up to 384 kbps Note 5 | No | - |
+| Video streaming | Video & supplementary data (e.g. text, still images) | Multicast | Streaming | Up to 384 kbps Note 5 | Service dependent | - |
+| Video distribution | Video & supplementary data (e.g. text, still images) | Broadcast | Download | Up to 384 kbps Note 5 | Service dependent | - |
+| Video distribution | Video & supplementary data (e.g. text, still images) | Multicast | Download | Up to 384 kbps Note 5 | Yes | Event |
+| General Content Distribution | Video, Audio, File Data (binary data) | Broadcast | Carousel, download | Up to 384 kbps Note 5 | Service dependent | - |
+| General Content Distribution | Video, Audio, File Data (binary data) | Multicast | Carousel, download | Up to 384 kbps Note 5 | Yes | Event |
+| Secure data download | File; eg UE type specific and/or application | Multicast | Carousel, download | Up to 10kbps | - | - |
+
+| | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--|--|--|--|--|
+| | specific
software | | | | | |
+| Notes :
1. Bit rate of the user data at the application layer.
2. If User Charging is Event based then Delivery Verification is required
3. Delivery Verification relates only to verification itself. Quality assessments may be required in addition.
4. DRM may be applicable to User Charging.
5. For GERAN lower bandwidth availability may constrain some applications. In such cases it may be possible to provide the same content via different delivery methods.
6. The ' - ' mark indicates that no applicable information has been identified. | | | | | | |
+
+# --- Annex B (informative): Example service scenarios
+
+This annex provides a non-exhaustive list of potential service scenarios for MBMS User Services.
+
+## B.1 Text notification service
+
+**Media:** Text
+
+**Precondition:** The user is a member of a MBMS Multicast group supplying text alerts.
+
+**Actions:** At an appropriate time an alert is sent to the user's mobile handset using the MBMS Multicast service.
+
+**Post condition:** The user receives the alert using her mobile handset and takes appropriate action.
+
+## B.2 Local Area Information distribution (Case A)
+
+**Media:** Text & Text with low quality video
+
+**Precondition:** The user is a registered with an MBMS Broadcast service providing information to the local area such as local news and weather reports.
+
+**Actions:** Information in the form of text & text with low quality video is distributed to the user's mobile handset by the MBMS Broadcast service. The text may be scrolled on the mobile handset. The information distributed by the MBMS Broadcast Service may be repeated periodically and updated at appropriate intervals.
+
+**Post condition:** The user is aware of events that have taken place within the local area and can view appropriate images.
+
+## B.3 Local Area Information distribution (Case B)
+
+**Media:** Video & Audio
+
+**Precondition:** The user is a registered with an MBMS Broadcast service providing streaming audio and/or visual content related to a local area, such as audio and visual guides to local attractions, traffic reports etc...
+
+**Actions:** Audio and/or visual information is distributed to the user's mobile handset by the MBMS Broadcast service. The user is able experience the content on her mobile device. The user is able to receive the MBMS broadcast service continuously throughout the local area. At some points the user is able to interact with the content of the MBMS Broadcast service in order to access specific information regarding items being presented within the content. The user is able to activate/deactivate reception of the MBMS service at any time.
+
+**Post condition:** The user experiences and interacts with the content provided and is therefore able to obtain information regarding the local area and act accordingly.
+
+## B.4 Multicast distribution
+
+**Media:** Text & Text with still images
+
+**Precondition:** The user is a member if a MBMS multicast group providing personally tailored content such as targeted advertising etc...
+
+**Actions:** Information is provided by the MBMS Multicast service in the form of text & text with still images, to the user's mobile handset based on her subscription to the Multicast group and current location.
+
+**Post condition:** The user receives tailored content and is able to utilize this as appropriate.
+
+## B.5 Audio Distribution
+
+**Media:** Stereo Audio
+
+**Precondition:** The user is registered with an MBMS Broadcast service providing stereo quality streaming audio content.
+
+**Actions:** Audio content is distributed to the user's mobile handset by the MBMS Broadcast service. Whilst listening to the audio content the user is able to interact with the service using the capabilities of the mobile handset (e.g. messaging).
+
+**Post condition:** The user is able to enjoy the stereo quality audio content and interacts with the service as appropriate.
+
+## B.6 General Content Distribution
+
+**Media:** Video, Audio & File Data
+
+**Precondition:** The user is registered with a MBMS Broadcast service providing a variety of content.
+
+**Actions:** Content is periodically distributed to a particular area by the MBMS Broadcast service. When the user activates reception of the MBMS Broadcast service she is able to receive the content being distributed at that time.
+
+**Post condition:** The user is able to receive and enjoy the content being distributed.
+
+## B.7 Software Download
+
+**Media :** File
+
+**Preconditions :** Need to update/download software in UE, the User is subscribed to MBMS User Service, OTA download is supported in UE
+
+**Actions:** The operator compiles a list of affected users and sends them a text message (using MBMS) explaining the problem and that the user should select the MBMS application on their handset. The user sees a message inviting her to activate the Enable Upgrade, selects 'yes' and the software patch transferred by the MBMS User Service, including verification parameters.
+
+**Postcondition :** The software once installed allows the user to view the MMs that she couldn't see before.
+
+# Annex C (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|---------------------------------------------------------------------------------|--------|--------|-------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| Jun 2003 | | | 22.246 | | | | | Initial draft presented | 0.0.0 | 0.1.0 | MBMS |
+| Aug 2003 | | | 22.246 | | | | | Output from MBMS adhoc Staines | 0.1.0 | 0.2.0 | MBMS |
+| Sep 2003 | | | 22.246 | | | | | Approved in SA1 for presentation to SA #21 | 0.2.0 | 1.0.0 | MBMS |
+| Oct 2003 | | | 22.246 | | | Rel-6 | | Raised to version 2.0.0 for approval at SA #22 | 1.0.0 | 2.0.0 | MBMS |
+| SP-22 | SP-030708 | S1-031003 | 22.246 | | | Rel-6 | | Approved at SA #22 | 2.0.0 | 6.0.0 | MBMS |
+| SP-23 | SP-040204 | | 22.246 | 0001 | 1 | Rel-6 | B | CR on advertising of capabilities required to receive a particular transmission | 6.0.0 | 6.1.0 | MBMS |
+| SP-23 | SP-040204 | S1-040226 | 22.246 | 0002 | - | Rel-6 | F | Addition of "MBMS transport service" definition | 6.0.0 | 6.1.0 | MBMS |
+| SP-23 | SP-040204 | S1-040227 | 22.246 | 0003 | - | Rel-6 | F | Clarification on delivery verification for MBMS user services | 6.0.0 | 6.1.0 | MBMS |
+| SP-23 | SP-040204 | | 22.246 | 0004 | 1 | Rel-6 | C | Using a single MBMS transport service for multiple MBMS user services | 6.0.0 | 6.1.0 | MBMS |
+| SP-25 | SP-040505 | S1-040634 | 22.246 | 0005 | - | Rel-6 | D | Minor corrections to TS 22.246 (MBMS User Services) | 6.1.0 | 6.2.0 | MBMS |
+| SP-29 | SP-050530 | S1-050887 | 22.246 | 0006 | - | Rel-7 | C | Support of enhanced MBMS user services providing multiple QoS levels (2) | 6.2.0 | 7.0.0 | MBMSE |
+| SP-29 | SP-050530 | S1-050939 | 22.246 | 0007 | - | Rel-7 | C | Support of enhanced MBMS user services providing multiple QoS levels | 6.2.0 | 7.0.0 | MBMSE |
+| SP-32 | SP-060308 | S1-060513 | 22.246 | 0009 | - | Rel-7 | F | Proposed CR to clarify the requirements for roaming | 7.0.0 | 7.1.0 | MBMSE |
+| SP-32 | SP-060307 | S1-060609 | 22.246 | 0010 | - | Rel-8 | B | Requirements on MBMS user service over generic IP accesses | 7.1.0 | 8.0.0 | MBMSE |
+| SP-33 | SP-060466 | S1-060935 | 22.246 | 0011 | - | Rel-8 | A | Proposed CR to clarify the requirements for roaming (see CR 0009) | 8.0.0 | 8.1.0 | MBMSE |
+| SP-34 | SP-060770 | S1-061433 | 22.246 | 0012 | - | Rel-8 | B | Requirements for LTE MBMS Television Service | 8.1.0 | 8.2.0 | LTE |
+| SP-35 | SP-070131 | S1-070282 | 22.246 | 0015 | 1 | Rel-8 | C | Requirements for LTE MBMS Television Service | 8.2.0 | 8.3.0 | SAE-R (LTE) |
+| SP-35 | SP-070115 | S1-070181 | 22.246 | 0017 | - | Rel-8 | A | Parallel, but regional, MBMS Sessions within one MBMS service. | 8.2.0 | 8.3.0 | MBMSE |
+| SP-36 | SP-070364 | S1-070784 | 22.246 | 0021 | - | Rel-8 | A | CR on Service Class Handling | 8.3.0 | 8.4.0 | MBMS |
+| SP-39 | SP-080043 | S1-080302 | 22.246 | 0022 | 3 | Rel-8 | B | Requirement for delivery verification in MBMS | 8.4.0 | 8.5.0 | TEI8 |
+| SP-39 | SP-080043 | S1-080303 | 22.246 | 0023 | 3 | Rel-8 | B | Requirement for pre-delivery verification in MBMS | 8.4.0 | 8.5.0 | TEI8 |
+| SP-46 | SP-090844 | S1-094275 | 22.246 | 0029 | 1 | Rel-9 | F | Updating to also include E-UTRAN for MBMS | 8.5.0 | 9.0.0 | TEI9 |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+
+| Change history | | | | | | | | | | | |
+|----------------|---------|---------|------|----|-----|-----|-----|-----------------------------------------------------------|--------|--------|----|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22250/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22250/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8f35ed4ad64a5771a78716a809b4481c0cc696a
--- /dev/null
+++ b/marked/Rel-18/22_series/22250/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d96a5e1d24270e40e89830d626000b3dc4d21ddb69cbde16575c14fe9d9631d7
+size 8182
diff --git a/marked/Rel-18/22_series/22250/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22250/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d107e5ab554572172d9c1fe82c7e805eac754206
--- /dev/null
+++ b/marked/Rel-18/22_series/22250/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2737ce6737c2d983c8a528d43f16428340a5bd69c59a81f687d1da5b0d2ac8f
+size 7268
diff --git a/marked/Rel-18/22_series/22250/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Rel-18/22_series/22250/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77e9da60dd84469be12d88c55c47a9b95f0efa79
--- /dev/null
+++ b/marked/Rel-18/22_series/22250/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fc559a3012faef16980e455be0e7e0885dd9ef05788efbfee8d5e745081247e
+size 42964
diff --git a/marked/Rel-18/22_series/22250/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-18/22_series/22250/997233d405f0d4b89ddeb7683e047f66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b3e75b98f2704012c43491b8c6a10aa07dbc49e
--- /dev/null
+++ b/marked/Rel-18/22_series/22250/997233d405f0d4b89ddeb7683e047f66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1efb3371faa6fe7b60ba4431d7ff25bee1c5bbe52359192fa5d4836a0fc363b7
+size 48612
diff --git a/marked/Rel-18/22_series/22250/raw.md b/marked/Rel-18/22_series/22250/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..847b2642fc2dd9bd8806b4caf5f17622d30c45f7
--- /dev/null
+++ b/marked/Rel-18/22_series/22250/raw.md
@@ -0,0 +1,363 @@
+
+
+# 3GPP TS 22.250 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) group management; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font, with a red signal wave icon below the 'G' and a 'TM' symbol to the right.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+---
+
+LTE, UMTS, management, IMS
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|--------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3.2 Abbreviations ..... | 5 |
+| 4 IMS group management..... | 6 |
+| 4.1 Informative description of group management ..... | 6 |
+| 5 High level requirements ..... | 7 |
+| 5.1 Group management roles ..... | 7 |
+| 5.2 General requirements ..... | 7 |
+| 5.3 Group member requirements..... | 8 |
+| 5.4 Management requirements ..... | 9 |
+| 5.5 Notification and acknowledgement requirements..... | 9 |
+| 6 Security ..... | 10 |
+| 7 Charging..... | 10 |
+| Annex A (informative): Change history..... | 11 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+This Technical Specification defines the requirements for the support of IP Multimedia Subsystem (IMS) group management capability. IMS group management capability provides a possibility to manage network based groups. IMS group management allows defining different roles and rights to the members of a group, defining group level information and properties, etc.
+
+The IMS group management is a generic capability that can be utilised together with several different services. Some examples of the services that can use IMS group management are
+
+- Presence service
+Presentity has a control of who is able to see his presence information. The control is carried out via access control lists, which can be managed with IMS group management. Number of presentities can be subscribed via a list of presentities. The list can be managed with IMS group management.
+- Chat
+Administrator of the chat is able to control users that are allowed to participate in the chat. The control is carried out via access control lists, which can be managed with IMS group management.
+- Messaging
+In messaging the server may be able to distribute the messages to several recipients based on the delivery list. The content of the delivery list can be managed with IMS group management.
+
+The above examples show only very limited set of possibilities where IMS group management can be utilised. The use of IMS group management is not restricted to these
+
+# 1 Scope
+
+The present document defines the stage one description of the IMS group management. Stage one is the set of requirements which shall be supported for the provision of IMS group management, seen primarily from the subscribers' and service providers' points of view.
+
+The TS includes information applicable to network operator, service provider, terminal and network manufacturer.
+
+Additional functionalities not documented in the TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the IMS group management defined in this specification.
+
+# 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 TR21.905: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications
+- [2] 3GPP TS 22.141: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Presence Service; Stage 1
+- [3] 3GPP TS 22.340: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IMS Messaging; Stage 1
+
+**Group administrator:** Group administrator has the full set of rights for viewing and managing the group identifier, group specific information, service specific group information, member identifiers and group member properties.
+
+**Group content:** Group content includes the group identifier, the group specific information, the service specific group information, and the list of group member identifiers with the associated group member properties.
+
+**Group member:** Group member is an entity in the group. Further 3G related definitions are given in 3GPP TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+| | |
+|-----|-------------------------|
+| IP | Internet Protocol |
+| IMS | IP Multimedia Subsystem |
+
+# 4 IMS group management
+
+## 4.1 Informative description of group management
+
+This clause has an informative description of the IMS group management and its role in a few service examples. Furthermore, example characteristics of the group will be described to give an overview of a group and its management.
+
+Group as a concept means a group of persons in this context. Groups can be used by group related services such as conference calls, presence service (c.f. 3GPP TS 22.141 [2]) and messaging (c.f. 3GPP TS 22.340 [3]). This description does not cover requirements for group services themselves but only management of the groups that can be utilized by the group related services. The driver for specifying generic group management is twofold: the same group created by user (or service provider) can be used in many services and same group management functions can be utilised independently of the service being used.
+
+In conference call, the control machinery in network would use a group to setup a conference call and distribution of group media. In messaging area, group management could be utilized in chat sessions (Figure 1) and distribution lists (Figure 2). A chat session could be created by joining a group. The message distribution would be handled by the messaging server. The user would send messages to a group and the server would distribute the messages. In the context of presence service, the user could create groups of watchers with the group management features and different presence information would be provided to each of the groups. These are only few examples of possible use of IMS group management and they intend to clarify the scope of group management.
+
+
+
+The diagram shows a central 'Chat server' cylinder. Inside the cylinder is a box labeled 'Access list:' containing the names 'Bob', 'Jack', and 'Marc'. On the left, three stick figures labeled 'Bob', 'Jack', and 'Marc' have arrows pointing towards the server. A yellow callout box with an arrow pointing to these arrows contains the text: 'Joining to chat is not IMS group management'. On the right, a stick figure is shown with a speech bubble containing the text: 'I want to let Bob, Jack and Marc to join this chat, that I controlling.' An arrow points from this figure to the server. A yellow callout box with an arrow pointing to this arrow contains the text: 'Use IMS group management to add Bob, Jack and Marc to chat access list'.
+
+Diagram illustrating the context of IMS group management in a chat service. A central 'Chat server' contains an 'Access list' with 'Bob', 'Jack', and 'Marc'. Three stick figures (Bob, Jack, Marc) are shown on the left, with arrows pointing from them to the server. A yellow callout box points to these arrows with the text 'Joining to chat is not IMS group management'. On the right, a stick figure is shown with a speech bubble saying 'I want to let Bob, Jack and Marc to join this chat, that I controlling.' An arrow points from this figure to the server. A yellow callout box points to this arrow with the text 'Use IMS group management to add Bob, Jack and Marc to chat access list'.
+
+Figure 1. Example: groups in context of chat service
+
+
+
+The diagram shows a user on the right sending a message to a central 'Messaging server'. A yellow callout box from the user states: 'I want to send a message to Paul, Lena and Lisa. To optimise the radio interface traffic I will utilise messaging server to do the distribution'. Above the server, another yellow callout box says: 'Use IMS group management to create message delivery list'. The server has a 'Delivery list' containing 'Paul', 'Lena', and 'Lisa'. Arrows labeled 'Message' point from the server to each of these three recipients (represented by stick figures) on the left.
+
+Diagram illustrating the use of IMS group management to create a message delivery list. A user sends a message to a messaging server, which then distributes it to multiple recipients (Paul, Lena, Lisa) based on a delivery list.
+
+**Figure 2. Example: group used as a message delivery list**
+
+How the group is used within a service is outside the scope of this document and outside the scope of group management. For example, taking part in a chat session, making a conference call and give access to certain attributes of the presence information are all group service specific issues and therefore outside the scope of group management. However, all of them could use groups managed by generic IMS group management.
+
+The IMS group management is a common set of actions that can be taken by the group administrator of a group or the group members. Typically, the group consists of members who may have varying rights for configuring or seeing the group properties.
+
+# 5 High level requirements
+
+## 5.1 Group management roles
+
+The IMS group management shall provide the ability for users to create groups that can be utilized in context of different services.
+
+The following roles are identified for IMS Group Management:
+
+- group administrator;
+Group administrator shall always have the full set of rights for viewing and managing the group and member properties. Each group shall have at least one group administrator at all times. The group administrator is not a group member by default. The entity creating a group becomes a group administrator.
+- group member; and
+Group member rights shall be assigned by the one who has rights to do that. Group member can be another group.
+- others.
+These are services and entities that are external to the group (i.e. not group administrators or members). They may or may not be able to use or access group content depending on the group specific information.
+
+## 5.2 General requirements
+
+The groups controlled by the IMS group management shall be associated with
+
+- a group identifier;
+Each group shall have a globally unique, addressable group identifier, which may be suggested by the group administrator when creating the group. The IMS service provider allocates group identifier. The group identifier is used to refer to a specific group (for example when sending a message, when updating the list of group members...).
+
+- b) group specific information; and
+
+Group specific information is divided into two parts
+
+ - 1) group information; and
+
+The group information contains informative text. This could be used for example to describe the type and usage of the group.
+ - 2) group properties.
+
+Group properties are:
+
+ - i) group visibility; and
+
+Group visibility defines who are able to see the group identifier when performing a search. The following classes exist:
+
+ - only the group administrators; and
+ - the group administrators and the group members.
+ - ii) group duration.
+
+Once created, a group will exist until either:
+
+ - its expiration time; or
+ - administratively removed.
+- c) service specific group information.
+
+The service specific group information may give additional information on how the group should be used in the context of a specific service. For example, it may indicate that the group shall be used as an access list in the context of the presence service. Detailed description of the service specific group information is not within the scope of this TS. Possible values can be defined by the terminal manufacturer, operator, service provider, or by other specifications. The service specific group information is transparent to the group management.
+
+## 5.3 Group member requirements
+
+Requirements for the members are
+
+- a) Member identification; and
+
+It shall be possible to identify the members of the group based on the
+
+ - 1) member identifier;
+
+Each single entity shall have a globally unique, addressable identifier(s).
+ - 2) group identifier; or
+
+Member can be a another group(s) which is referred with a group identifier(s).
+ - 3) commonly known group of entities.
+
+Member can be any entity that has defined characteristics in the identifier field.
+- b) group member properties.
+
+It shall be possible to associate properties for each group member. Such properties are
+
+ - 1) member rights;
+
+Each member shall be associated with rights. They define which actions the member is allowed to perform.
+ - 2) anonymity; and
+
+It shall be possible to hide the member identifier.
+ - 3) service specific member information.
+
+The service specific member information may give additional information on member in the context of a specific service. For example, it may indicate the screen name of the member in context of chat service. Detailed description of the service specific member information is not within the scope of this TS. Possible values can be defined by the terminal manufacturer, operator, service provider, or by other specifications. The service specific member information is transparent to the group management.
+
+## 5.4 Management requirements
+
+The IMS group management shall provide following capabilities to manage groups. The rights associated to the members control the capabilities they are able to perform. These capabilities are:
+
+- a) create a group;
+The entity creating a group becomes a group administrator. The administrator shall not become group member by default when creating a group. Further, when creating a group it shall be possible to
+ - 1) define the members of the group;
+ - 2) define group specific information;
+ - 3) define service specific group information; and
+ - 4) define member properties.
+- b) delete a group;
+It shall be possible to delete a group.
+- c) add members to a group;
+It shall be possible to add members to a group.
+- d) get member list of a group;
+It shall be possible to get the list of all members of a group. In case of nested group only the group identifier of the nested group will be provided.
+- e) remove members from a group;
+It shall be possible to remove members from a group.
+- f) get group member identification and group member properties;
+It shall be possible to get member identification and group member properties.
+- g) modify group member properties;
+It shall be possible to modify group member properties within their rights.
+- h) get group specific information and service specific group information;
+It shall be possible to get group specific information and service specific group information.
+- i) modify the group specific information and service specific group information;
+It shall be possible to modify all group specific information and service specific group information.
+- j) simultaneous access from multiple terminals; and
+It shall be possible to manage groups simultaneously from multiple terminals (e.g. via mobile phone and PC).
+- k) Search.
+It shall be possible for a user to retrieve the group identifiers of all the groups for which he has the group administrator role within his operator's network.
+
+It shall be possible for a user to retrieve the group identifiers of all the groups for which he has the group member role within his operator's network. If a group is not visible for its group members, then the group identifier will not be revealed to the user.
+
+In both cases the search criteria shall be a text string. It shall be possible to use wild cards as part of the text string.
+
+It shall be possible for authorised users and applications to use the group content. Some parts of the group content may not be revealed (e.g. group properties...).
+
+## 5.5 Notification and acknowledgement requirements
+
+The rights associated with the group members and administrator(s) may grant them access to some notification features described below.
+
+It shall be possible for the group members, administrator(s) and authorised users and applications to subscribe to different events concerning the group. When an event occurs the entities interested in that event shall be notified. The notification categories are:
+
+- a) change in group specific information;
+- b) change in service specific group information;
+- c) change in group members; and
+This includes also the changes in the number of anonymous members.
+- d) change in group member properties.
+
+# --- 6 Security
+
+The use and access to group content and notification(s) of changes shall be supported in a secure manner. It shall be possible to authenticate and authorise users and applications requesting access to the group content (IMS security and authentication mechanisms may be used). It shall only be possible for the group content and notification(s) of changes to be supplied to the authenticated and authorized users and applications.
+
+The group management shall support measures to detect and prevent attempts to abuse the group content and notification(s) of changes. The integrity of the group content and notification(s) of changes during transfer shall be assured to extent of the network capabilities.
+
+NOTE: In case of non-IMS users using and accessing group content and notification(s) of changes, alternative security mechanisms may be used. Such mechanisms are to be defined by IMS service provider and they are not subject to standardisation. Those mechanisms should ensure the authentication and authorisation of users and applications that access the group content. The mechanisms shall provide integrity and confidentiality during the transport of the group content and notification(s) of changes.
+
+It shall be possible to protect the request of group content and the notification of changes in the group content from attacks (e.g., eavesdropping, tampering, and replay attacks).
+
+# --- 7 Charging
+
+Charging for IMS group management shall be based on existing IMS charging mechanisms as appropriate.
+
+IMS group management shall be able to support various charging models, including:
+
+- a) pay per transaction;
+- b) volume based charging;
+Charging may be based on the volume of transferred group content.
+- c) indirect charging; and
+Group management may be indirectly charged when it is incorporated as part of a service.
+- d) offline charging and online charging.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|----|-----|-------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| | | | ab.cde | | | | | Produced during IMS SWG meeting 8th-12th April, Sophia Antipolis, France | | 0.0.0 | IMSGM |
+| | | S1-020751 | 22.250 | | | | | Initial content provided to number of clauses and subclauses. | 0.0.0 | 0.1.0 | IMSGM |
+| | | | 22.250 | | | | | Definitions added. Group management roles and Group member roles subclauses added. Major revisions in General requirements, Management requirements and Notification and acknowledgement requirements subclauses. | 0.1.0 | 0.2.0 | IMSGM |
+| | | | 22.250 | | | | | Major revisions in General requirements and Notification and acknowledgement requirements subclauses. | 0.2.0 | 0.3.0 | IMSGM |
+| | | | 22.250 | | | | | Group roles reduced to two, Introduction, Security and Charging requirements added. | 0.3.0 | 0.4.0 | IMSGM |
+| | SP-020566 | | 22.250 | | | | | Presented for information | 0.4.0 | 1.0.0 | IMSGM |
+| | | S1-022042 | 22.250 | | | | | Number of editor's notes removed, visibility and search clarified | 1.0.0 | 1.1.0 | IMSGM |
+| 12 /12/02 | SP-18 | SP-020669 | 22.250 | | | | | Raised to version 2.0.0 for presentation for approval at SA #18 | 1.1.0 | 2.0.0 | IMSGM |
+| 12 /12/02 | SP-18 | SP-020669 | 22.250 | | | | | Approved at SA #18 | 2.0.0 | 6.0.0 | IMSGM |
+| 12 /06/07 | SP-36 | | 22.250 | | | | | Updated from Rel-6 to Rel-7 | 6.0.0 | 7.0.0 | |
+| SP-42 | - | - | | | | Rel-8 | | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22259/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-18/22_series/22259/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b5386482393a09a43c590db538217a274812bec
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9982d5c37389a6ca5ab46363001b96ed06c6cacef5efef5acf48c9678c4b2e7f
+size 69973
diff --git a/marked/Rel-18/22_series/22259/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-18/22_series/22259/3da1a07cb87051bf616c9876db958cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..263151217967036a3cdb5630f5c30dcf7ccd1d3a
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/3da1a07cb87051bf616c9876db958cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c5aff2e34890bf8607b5885df33dbf1f5fad2aa0cb26adfa921f0f7ad5aa6f2
+size 25159
diff --git a/marked/Rel-18/22_series/22259/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-18/22_series/22259/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdcbda1654cb478129fd1334f6a8d65590f335ef
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e63b6eaa43dc5794d05f497519dbf7722b3e0c0cee038634d3a57c3e592a1aa5
+size 69603
diff --git a/marked/Rel-18/22_series/22259/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-18/22_series/22259/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9513195f58c7dfc6bc809efa3560f8ab7e23c9b1
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb75800d92e5ee01ea96f39e8a19dcfc9a90dc4753c6888115cc899f277d7ea9
+size 49848
diff --git a/marked/Rel-18/22_series/22259/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22259/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/22_series/22259/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22259/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2df6ad86e7021bc7b157060e6b949b94736b13ff
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53faf037465dde7b382f95640f809053f12882698bd17ee17c7b0f3ac7e8cf9
+size 5413
diff --git a/marked/Rel-18/22_series/22259/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-18/22_series/22259/77464a47f104d0d647b2414591137b64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50e17c7d42fafec06e41a1fdf4b731b0818ff85c
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/77464a47f104d0d647b2414591137b64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d418d61cdf2b937046e60f25770bfc6bf86f569c25c04e44ced7e63d80103bc
+size 45877
diff --git a/marked/Rel-18/22_series/22259/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/22_series/22259/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4474f136f7c1693a302c41313067c4755fe879a
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a392fe23c584deeb0a912cfa429b38e6de59861eccd3b4ed955ae61cd2fa5a1
+size 65254
diff --git a/marked/Rel-18/22_series/22259/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-18/22_series/22259/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b6f5eee06537a1aac6a818fd9c79be9f03a63f7
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5799cdd6a4cc989237b61cb4f5f7e2d6711e01bdbf604a7e834d226072a6b73d
+size 90657
diff --git a/marked/Rel-18/22_series/22259/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-18/22_series/22259/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..06c44c08b4b02ac6a58479cc9168d4e8fb244475
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb0dc4902a33c27aaf648a2b0213af423ebcc7ee94ee388dda4d9abb20812ae6
+size 80490
diff --git a/marked/Rel-18/22_series/22259/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-18/22_series/22259/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..993babedeb67e01f821cfb85f4bc0be409353bcf
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b45dba501c86ff156a4842e3177d909d639c61a18f0b638760134040afe20c4
+size 56447
diff --git a/marked/Rel-18/22_series/22259/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/22_series/22259/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1892088777f622a252396a0c181acd13cf79f240
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e44c979d53a95d1d6f5a2aab5a1fe33090e71ca336bdc1ab77089df4173bb4c6
+size 20292
diff --git a/marked/Rel-18/22_series/22259/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-18/22_series/22259/a3472689858b068ef469213682965325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9c50a7d14b1f4c7fd5de4c2515d3880bb5df9ae
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/a3472689858b068ef469213682965325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70cafc7be43d32bbd1ff7f03a86862c104897ee4f1d40fe60f473804fbfc41ab
+size 73682
diff --git a/marked/Rel-18/22_series/22259/a51105b2031bad93b818b82f071c6add_img.jpg b/marked/Rel-18/22_series/22259/a51105b2031bad93b818b82f071c6add_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70777fd0fe78b28331660bd543fb3a17fe964c28
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/a51105b2031bad93b818b82f071c6add_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcbdad55b8c9207577fae1a9ba94c002e5bb70f56096d5af428e7b0162be6602
+size 31756
diff --git a/marked/Rel-18/22_series/22259/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-18/22_series/22259/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0bd2d3bc3def93012d49e85bae44fedd703557e5
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b4a627d344090eb96b3eafbb597e08cf76fc4ce7771a5958a644af8652093da
+size 65366
diff --git a/marked/Rel-18/22_series/22259/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-18/22_series/22259/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e69351ddec8b6739476483012ad5ea874fdf172
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdf74ce527c62f3f2fa0c3a1b6c34e02475ab2bc0f906e985b00cd8f02aaaa48
+size 61033
diff --git a/marked/Rel-18/22_series/22259/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-18/22_series/22259/e636d7ccca0ad14c6b95201404324823_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1835c87b1cffc4bc084f73844180cae679a4f78c
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/e636d7ccca0ad14c6b95201404324823_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e37eb36b59790a22c0421bca031740a39385ca99142fab1903df05235d63547d
+size 27367
diff --git a/marked/Rel-18/22_series/22259/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-18/22_series/22259/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3e8a0c9113115130ee8f2f47330769bf7f629da5
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11d93e1cede3ca4a72972092824563770de16448a7bbdb436127de76448ac447
+size 88369
diff --git a/marked/Rel-18/22_series/22259/raw.md b/marked/Rel-18/22_series/22259/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f8ce8b6a51d1322842e4f87ac78bcb143305638
--- /dev/null
+++ b/marked/Rel-18/22_series/22259/raw.md
@@ -0,0 +1,711 @@
+
+
+# 3GPP TS 22.259 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for Personal Network Management (PNM); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, GSM, service, stage 1, network,
+management
+
+## **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|--------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Personal UE networks..... | 7 |
+| 4.1 General description ..... | 7 |
+| 4.2 PN UE Redirecting application..... | 8 |
+| 4.2.1 Requirements for PN UE redirecting application..... | 8 |
+| 4.2.2 Usability requirements for PN UE redirection application ..... | 10 |
+| 4.2.3 Security for PN UE redirection application..... | 10 |
+| 4.2.4 Charging for PN UE redirection application ..... | 10 |
+| 4.2.5 Interaction with supplementary services ..... | 10 |
+| 4.3 PN access control ..... | 11 |
+| 4.3.1 Requirements for PN access control..... | 11 |
+| 4.3.2 Usability requirements for PN access control ..... | 11 |
+| 4.3.3 Security for PN access control ..... | 11 |
+| 4.3.4 Charging for PN access control..... | 11 |
+| 5 PNE networks ..... | 12 |
+| 5.1 General description ..... | 12 |
+| 5.2 Personal area network management..... | 12 |
+| 5.2.1 Personal area network requirements..... | 13 |
+| 5.2.2 Usability requirements of personal area network management..... | 14 |
+| 5.2.3 Security ..... | 14 |
+| 5.2.3.1 General..... | 14 |
+| 5.2.3.2 PNE management requirements..... | 15 |
+| 5.2.4 Charging ..... | 15 |
+| 5.3 PNE redirecting application ..... | 15 |
+| 5.3.1 Requirements for PNE redirecting application..... | 15 |
+| 5.3.2 Usability requirements..... | 16 |
+| 5.3.3 Security ..... | 16 |
+| 5.3.4 Charging ..... | 16 |
+| 5.4 PN access control for PNE networks ..... | 16 |
+| 5.4.1 Requirements for PN access control for PNE networks..... | 16 |
+| 5.4.2 Usability requirements for PN access control in PNE networks ..... | 16 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------------|-----------|
+| Annex A (informative): | Use cases..... | 17 |
+| A.1 | Use case: Connection between PNEs of a PN ..... | 17 |
+| A.2 | Use case of UE-PN connection..... | 18 |
+| A.2a | PN Access control: Parental control ..... | 19 |
+| A.3 | Use case of PN-User access a PLMN from their PNEs..... | 19 |
+| A.4 | Use case for connection between guest UE and PN ..... | 20 |
+| A.5 | Use case on UE redirection of terminating services ..... | 21 |
+| A.6 | Use case on PNE redirection of terminating services ..... | 22 |
+| A.7 | Use case: Selective update based on capability lists..... | 23 |
+| A.8 | Use case: Combination of two PANs..... | 23 |
+| A.9 | Use case: Separation of PAN ..... | 25 |
+| Annex B (Informative): | Change history..... | 26 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+Traditionally a single integrated device with integrated radio access means formed the User Equipment (UE) for access to mobile communication services. Now, however, many subscribers possess more than one device for running mobile communication services, which may be connected to form a Personal Network (PN). The devices differ in their capabilities and these capabilities qualify the devices more or less for specific end-to-end applications or particular media like audio, video and pictures. A part of the devices offers own network access means for accessing the PLMN via UTRA, WLAN, or other access technologies. The other devices are Terminal Equipments without radio access capabilities.
+
+Personal Network Management (PNM) allows the users to manage their devices and PN's. This TS specifies requirements for allowing the users to manage their devices. The considered management functions of Personal Network Management comprise the setup and configuration of Personal Networks, the personalization for the termination of services within the Personal Network as well as the enabling of secure connections between the Personal Network Elements. This includes the management of Personal Area Networks with their local device connections and their available radio access means.
+
+Two different scenarios are distinguished for Personal Network Management:
+
+- 1 Personal UE Networks: This addresses the management of multiple UEs belonging to a single PN-User. It contains the UE Redirecting application that provides for redirect terminating services to selected UEs and PN Access Control that provide for privacy and enable restricted access to a PN.
+- 2 PNE Networks: This extends the scope of considered managed objects from UEs to physically separated UE components and to attached MEs. It does not only extend the PN UE Redirecting application and PN Access Control by PAN-specific aspects but addresses the PAN Management with interactions of TEs and MEs.
+
+These two scenarios are handled separately within the TS as the requirements of Personal UE Networks and PNE Networks are focussed on different types of services. Personal UE Networks aim at an easy-to-use UE management whereas PNE Networks enable complex scenarios of local networks with alternative network access means.
+
+# --- 1 Scope
+
+The present document describes the service requirements for the Personal Network Management (PNM). Aspects of data synchronisation and management of user data are out of scope.
+
+# --- 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 TS 22.004: "General on supplementary services".
+- [2] 3GPP TS 22.101: "Service aspects; Service principles".
+- [3] 3GPP TS 22.105: "Service aspects; Services and service capabilities".
+- [4] 3GPP TR 22.944: "Report on service requirements for UE functionality split".
+- [6] Void
+- [7] 3GPP TS 23.101: "General Universal Mobile Telecommunications System (UMTS) architecture".
+- [8] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services".
+- [9] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem"..
+- [10] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS)".
+- [11] 3GPP TS 23.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services".
+- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [12] 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 [12].
+
+**Personal Network:** A Personal Network (PN), in the context of Personal Network Management, consists of more than one Personal Network Element under the control of one PN-User providing access to the serving PLMNs. There shall be at least one Personal Network Element with a USIM subscription in a PN. Authentication of the user for each PLMN access is based on the USIM(s) of the PN. The Personal Network Elements are managed in a way that the user perceives a continuous secure connection regardless of their relative locations. The Personal Network Elements
+
+belonging to the PN-User's PN maybe registered to different PLMNs at a time. The PN-User controls the PN using facilities provided by the Personal Network Management (PNM).
+
+**Personal Network Element:** A Personal Network Element (PNE) is the basic component making up a PN-User's Personal Network. A Personal Network Element is handled as a single entity in PNM but physically it may be either a single device or a group of devices. The Personal Network Element may be a TE, MT, ME or even a complete UE.
+
+**Personal Area Network:** A Personal Area Network (PAN) is a local network of the PN-User. In the context of Personal Network Management, the PAN consists of at least one UE and may additionally comprise a number of MEs/MTs, with own radio access means that allow them to directly access the PLMN of the UE. The UE and locally connected additional MEs/MTs are the PNEs of the PAN. Alternatively the UE components, i.e TEs and MT, may be handled as separate PNEs. The UE contains the single active USIM of the PAN.
+
+**PNE Identifier:** The PNE Identifier uniquely identifies each PNE of a PN within the PN. The PNE Identifier of MTs and MEs is the IMEI. Other PNEs have PNM-specific identifiers that are allocated for enabling PNM functions.
+
+**PN-User:** For the purpose of Personal Network Management the PN-User is the person who owns the Personal Network Elements with respective subscriptions at one service provider.
+
+**Registration:** In the context of Personal Network Management registration is the procedure by which a particular entity is either added to the Personal Network or to the Personal Area Network. Entities are physically separated devices or groups of devices. The entity stays registered till deregistration of the entity is performed. The status of registration to a Personal Network or Personal Area Network is not affected by the status of registration/attachment to the PLMN.
+
+**Configuration:** In the context of Personal Network Management Configuration contains the procedure by which a PN-User can configure the PN settings for the PN UE and the PN Access Control applications.
+
+**Interrogation:** In the context of Personal Network Management Interrogation is the procedure by which a PN-User can interrogate the PN settings which are configured by the PN-User before.
+
+For further definitions see [12].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations given in TR 21.905 [12] 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 [12].
+
+| | |
+|-----|-----------------------------|
+| PNM | Personal Network Management |
+| PN | Personal Network |
+| PAN | Personal Area Network |
+| PNE | Personal Network Element |
+
+# --- 4 Personal UE networks
+
+## 4.1 General description
+
+Personal UE Network features enable the management of multiple UEs belonging to a single PN-User. In particular, customer needs who own more than one terminal and subscription are addressed, e.g. ordinary handset for telephony, car phone, PDA for emails when on the move, data card with laptop for work when in semi-stationary mode. Although those devices are mainly held for a particular usage, many are able to support more than one sort of services, e.g. telephony is supported by all but the data card. Personal UE Networks are not aware of the presence of other PNEs belonging to a user.
+
+Functionality enabled by Personal UE Networks comprises PN UE redirection and PN Access Control.
+
+Registration, configuration and interrogation procedures for PNM are supported via IMS capable PN UEs, via a web client or by administrative procedures.
+
+## 4.2 PN UE Redirecting application
+
+Customers may not carry always their full set of "gadgets", but still want to be reachable. Currently management of all the terminals for the PN-User by setting forwarding options, switch on and off terminals, providing partners with multiple addresses is not very customer friendly.
+
+
+
+```
+
+graph TD
+ PNM((PNM)) <--> AS1((Access System))
+ PNM <--> AS2((Access System))
+ PNM <--> AS3((Access System))
+ AS1 <--> UE1[UE]
+ AS2 <--> UE2[UE]
+ AS3 <--> UE3[UE]
+
+```
+
+Diagram illustrating the PN UE Redirecting application. A central cloud labeled 'PNM' is connected to three 'Access System' clouds. Each 'Access System' cloud is connected to a 'UE' (User Equipment) icon. The 'PNM' cloud is at the top, and the 'Access System' clouds are arranged horizontally below it. The 'UE' icons are at the bottom, each connected to an 'Access System' cloud. All connections are shown with red double-headed arrows.
+
+**Fig 1: UEs managed by PN e.g. UE Redirecting application**
+
+### 4.2.1 Requirements for PN UE redirecting application
+
+- PNM shall be provided to a subscription upon customers request via administrative procedures.
+- PNM shall be withdrawn upon customer request or for administrative reasons via administrative procedures.
+- The PN-Users shall be able to register and deregister UEs to their PN.
+- Successful registration shall add the UE as new Personal Network Element to the Personal Network. The information on the UE and the public user identities belonging to the UE shall be written to the service profile in the network. A deregistration procedure shall be performed to remove a registered UE from the Personal Network.
+- Each UE shall only be registered in one PN and the network shall reject the registration request of a UE that is already registered in another PN.
+- The PN-Users shall be able to "activate" a certain UE of their PN as the default UE for terminating services addressed to any of the UEs belonging to the PN. Activation shall be possible
+ - On a global level for all services supported by the UE capabilities and subscription
+ - On a per service basis for selected services supported by the UE capabilities and subscription
+ - On a per service component basis for the different media of a supported service (in line with [9])
+- The PN-Users shall be able to configure priorities of a UEs list with priority for terminating a specific service.
+
+- Note: the priority may be based on parameters such as time, device capability and PN-User choice.
+- The PN-User shall be able to interrogate the PNM network database for the current PN-User settings of their own PN.
+- The registration and configuration procedures shall include a validation and update of identities and capabilities associated with the UE. For this reason, registration and activation of a UE shall only be done for UEs that are currently attached/registered to the network. The UE shall either send an registration/activation request to the network or the network shall "invite" the UE based on a request received from another UE belonging to the PN. Registration and activation may be also provided via administrative procedures.
+- The UE or the network shall deny activation as default UE for terminating a particular service or service component, in case the UE does not provide the capability or the subscription to terminate the service.
+- Deactivation and deregistration should not always require the involvement of the UE affected by the setting. However the network shall only process deactivation and deregistration requests from UEs belonging to the same PN.
+- A UE performing activations shall have the capability to perform the deactivations for these settings.
+- For terminating services without an activated UE, the services shall not be redirected but shall be terminated by the addressed target UE. Information shall be offered to the PN-User when the only active device for terminating a service is deactivated.
+- In case more than one device is activated for a terminating service, e.g. IMS devices with the same Public User Identity, the service should be directed to all devices that are currently reachable for the network (PS attached or IMS registered). It shall be possible to make the PN-User aware on charging implications caused by activation of more than one UE for directing of the same service.
+- If activations are configured for one or more media types of a service then the overall service directing setting shall be overwritten for directing these service components.
+- Directing media of a service to different devices should be up to the choice and responsibility of the PN-User. For instance, in case of synchronized media the redirection to different devices may result in a loss of synchronization.
+- A new activation overrides the previous activation status when successful.
+- Deregistration of active UEs shall comprise the global deactivation of the UEs.
+- It shall be possible to allow two sets of activation settings. One set is always present and contains the default configuration. On a temporary basis, a second set of activation settings is configured. The temporary activations shall provide a means for saving and restoring current activation settings. While temporary activations are switched on, these settings shall override the non-temporary configuration.
+- The network shall assume that the non-temporary settings are still valid after fallback from temporary to non-temporary activation settings. For this reason, it shall be possible for the UE to access and change temporary as well as non-temporary settings.
+- If capabilities or subscriptions of an active UE change and activated services are no longer supported by the UE, e.g. TEs providing these capabilities are removed, then the UE shall deactivate the affected services and offer appropriate information to the user and the PN service.
+- It shall be possible for a UE to offer capability lists to the PNM service, where the capability list contains the capabilities that the UE is capable of terminating or is interested in receiving updates regarding them.
+- It shall be possible for UEs of the PN to update PN configuration after an attachment/registration of the UE to the network.
+- PNM settings may comprise current UE capabilities and redirection settings of a PN. The PNM service shall update the PNM settings to the UEs, selectively based on their respective capability lists, when other UE capabilities of the PN change.
+- Means shall be provided to enable redirection to a particular UE for dealing with situations where UEs share the same Public User Identity.
+
+- Terminating services shall only be redirected if the redirection does not cause systematic misbehaviour of user devices or the network (e.g. SMS is one service where redirection shall not be applied if any over-the-air management of the target UE would be prevented.)
+- The PNM service shall interwork with CS-Domain call forwarding [8] and IMS session redirecting [9] in a way that no collisions of contradicting redirections occur in the network and the redirection of data remains transparent for the user. The considered interworking scenarios shall include the redirection of IP Multimedia sessions caused by any of the listed events or conditions [9].
+- The UE Redirecting application shall be applicable to terminating services in the CS-domain, PS-domain, and IMS subsystem.
+- Originating services shall not be affected by the default settings.
+- The services that are made available for redirection shall be consistent with existing service identifiers, e.g. IMS communication service identifier [10], or service grouping, e.g. basic service groups [1].
+- Redirection of terminating services and service media shall be done for only public user identities and addresses belonging to a UE of the PN.
+- The PN-User shall be able to exclude specific public user identities and addresses of the PN from data redirection.
+
+Note: In the above requirements, registration means the registration of UE and of its public identities to the PN. The registration procedures of the UE to the PLMN remain unaffected.
+
+### 4.2.2 Usability requirements for PN UE redirection application
+
+The following PNM procedures shall be at least available via one of the UEs belonging to the actual PN of the PN-User and shall be realized in a user friendly and secure manner:
+
+- Registration of a UE
+- Deregistration of a UE
+- Activation of a UE for a specific service or service component
+- Global activation of a UE for all services, as far as supported
+- Setting up of capability lists as requested by a user
+- Interrogation of PNM database
+
+### 4.2.3 Security for PN UE redirection application
+
+- Registration of UEs to a PN shall require the consent of the subscriber by appropriate means, e.g. an "invite" function, preventing intended/unintended access by unauthorized UEs.
+
+### 4.2.4 Charging for PN UE redirection application
+
+- All charges for terminating services shall be levied to the "active" UEs, even when originally addressed to another UE belonging to the PN.
+- It shall be possible to raise registration/deregistration and activation/deactivation fees.
+
+### 4.2.5 Interaction with supplementary services
+
+- For terminating services invocation of Supplementary Services applicable to the active UE shall take precedence over invocation of Supplementary Service applicable to the called UE.
+- There is no impact on the registration, erasure, activation, deactivation of Supplementary Services.
+
+## 4.3 PN access control
+
+- Private networks may consist of UEs which are only privately accessed, that is each UE may be accessed only by other UEs of the PN. The PN-User may additionally modify the access levels of each UE of the PN to be public or private.
+- In order to allow external UEs or Guest UEs to access these UEs, the PNM provides access control procedures. The PNM shall provide registration and authentication mechanisms for guest device access.
+
+Note 1: Authentication refers to verifying the registration status of a certain guest UE by the PNM.
+
+Note 2: It is assumed that guest UE access to a UE in a PN is routed via the PLMN Network. In particular control of access to a UE via local interfaces is outside the scope of this specification.
+
+### 4.3.1 Requirements for PN access control
+
+- The PN-User may register up to UEs to be private to the PN, whereby public access to these devices may be restricted.
+- The PN-User is able to register up to UE public identities not owned by him as registered callers that are allowed to initiate sessions with the private UEs of the PN, and these UEs containing these registered public identities are referred to as Guest UEs.
+- The PN-User may nominate a UE as the default UE for access control. This UE shall have the access rights to register/deregister private UEs and guest UEs.
+- The registration of Guest UE may be performed by the default UE for access control and enabled dynamically (querying during session initiation procedures using public identity of caller) or statically (using PN specific database) by PNM procedures.
+- In case the user has another UE in the PN as the default UE for redirection, then the querying shall be directed to the default UE for redirection.
+
+### 4.3.2 Usability requirements for PN access control
+
+- Registration of a Guest UE
+- Deregistration of a Guest UE
+- PN access level settings for a particular UE of the PN to be public / private
+- PN Access control settings are stored at PNM database, for a particular Guest UE e.g unlimited access of PN by close friends, limited access by acquaintances.
+
+Note: In the above requirements, public identity may be substituted in place of UE. Example, either a public identity or a UE may be registered into a PN.
+
+### 4.3.3 Security for PN access control
+
+- PN access control settings refer to the PN-User providing different access control settings of his PN for different Guest UEs / Public Identity.
+
+### 4.3.4 Charging for PN access control
+
+Note: Currently no additional charging issues have been identified, but this topic may be studied further.
+
+# 5 PNE networks
+
+## 5.1 General description
+
+PNE Networks enable functions for the management and direct accessibility of the physically separated components of a UE, i.e. TEs and MEs..
+
+PNE Network functions comprise the management and communication of these PNEs within a PN as well as the extension of the PN UE Redirecting application and the PN access control function to include the redirection to UE and PAN components.
+
+
+
+Diagram illustrating devices addressed by PAN Management. A central PNM (Personal Network Management) cloud is connected to three Access System clouds. These Access Systems are connected to various User Equipment (UE) and Personal Area Network (PAN) components. The components include Mobile Equipment (ME) and Terminal Equipment (TE) units. The diagram shows two PANs (cyan ovals) and one UE (yellow oval) connected to the Access Systems. The PNM cloud is connected to the three Access System clouds via red double-headed arrows. Each Access System cloud is connected to a PAN or UE via red double-headed arrows. Within each PAN, the ME and TEs are connected to the Access System via red double-headed arrows. The ME is also connected to the TEs via dashed double-headed arrows. A legend in the top right corner identifies the colors for UE (yellow), PN (purple), and PAN (cyan).
+
+Fig 2: Devices addressed by PAN Management
+
+## 5.2 Personal area network management
+
+Service requirements cover the management of UE(s), as well as UE components and TE(s), ME(s) or MT(s) and belonging to the same PAN(s) (see Figure 2).
+
+A UE including a USIM, can comprise physically separated TEs and can also have connections with other MTs or MEs (e.g., a PDA, music player, laptop, camera, headset, etc.). The devices are connected through short-range wired or wireless connections (when they are in close proximity) and form a small network, called a PAN (Personal Area Network). The owner of the PNE that holds the USIM controls the PAN.
+
+PNEs of a PAN without / not requiring a USIM, may have the need to access services provided by the PLMN or to communicate with another entity through the PLMN. In this case PNEs must be authenticated and authorized by using the USIM associated with the PLMN (i.e., a single USIM authority shall be shared by all the PNEs of the PAN that access services provided by the PLMN).
+
+For managing a PAN means are required to identify a particular PNE within a PAN. The PNE identifiers enable connections between selected PNEs and directing of terminating services to a particular PNE.
+
+Thus PNM identifiers are divided into subscriber identities and PNE identities. 3GPP private subscriber identifiers are the unique IMSI and the unique IMS Private User Identities stored in USIM and ISIM. The subscriber identities are used, for example, for registration, authorization, administration, and accounting purposes in the network. The PNE Identifiers are used to identify devices within a PN and may be used, for example, for blacklist and Device Management purposes. When the PNE is a ME, the IMEI should be reused as PNE identifier unless for security reasons or other reasons this is not feasible. In contrast to MEs the PNE identifiers of TEs are PNM-specific and have little network security relevance as TE have no own radio access means.
+
+Annex A.3 shows two use cases where users access a PLMN from their PANs.
+
+The PN shall support the combination and separation of PANs.
+
+### 5.2.1 Personal area network requirements
+
+- The PN-User shall be able to control which PNEs (i.e. TEs, MTs and MEs) are part of a PAN via MMI procedures.
+- A user may set-up more than one PAN within a PN.
+- The PN-User shall be able to register and deregister PNEs that can be used in a PAN.
+- The PN-User shall be able to activate and deactivate the PNEs registered to a PAN.
+- A PAN uses exactly one active USIM for authentication. Hence a PAN contains exactly one 3GPP UE.
+- In case of only one ME within the PAN the PAN reduces to a 3GPP UE and shall behave as such.
+- The PNE Identifier of MEs shall be the IMEI. For TEs it shall be possible to allocate PNM-specific PNE identifiers.
+
+Note: Cases occur in practice where IMEIs are duplicated for misuse. Resulting potential security threats should be considered when adding functionality that requires a secure PNE identifier.
+
+- PNM-specific PNE Identifiers should only be required for PNM-internal purposes but should be harmonized with other optional device identifiers (i.e. Personal ME Identifier in CSI [11]).
+- PNM-specific PNE Identifiers shall not be used for routing purposes in the network except PN-internal forwarding to a particular PNE within a PAN.
+- PNE Identifiers shall be unique within a PN. Procedures are needed to avoid that PNEs of one PN have the same PNE Identifier.
+- It shall not be necessary to store PNE Identifiers in TEs. Instead PNE identities should be managed by a PAN device responsible for processing PAN Management functions.
+- It shall be possible to simultaneously access a PLMN via multiple access systems. For example, the user might use PNE1 for data services (internet access) together with PNE2 on a PLMN for a speech call.
+- The PN shall support the combination of two or more PANs into one PAN when they are in close proximity. In this case a UE shall be designated for the new PAN. Other UEs who participate in the combination shall be deactivated and hence act as MEs in the new PAN.
+- The PN shall support the separation of PAN under specific conditions. In case that there is no active UE among the separated devices, a ME with a USIM shall be designated and activated as UE for the new PAN.
+- The PN shall be able to update registration information of PNEs that participate in the combination or separation of PANs.
+
+
+
+Diagram illustrating connections between MEs and TEs to a PLMN. Two TEs (TE I and TE II) are connected to an ME. This ME is connected to a PLMN. Another ME is also connected to the PLMN. The first ME contains a USIM. Arrows indicate two paths to the PLMN: 1. authentication by using a USIM of a UE (from the first ME's USIM to the PLMN), and 2. direct access to a PLMN (from the second ME to the PLMN).
+
+**Figure 34: Connections between MEs and TEs**
+
+### 5.2.2 Usability requirements of personal area network management
+
+The following PAN Management procedures shall be supported by PAN in a user friendly and secure manner:
+
+- Authentication and authorization of PNEs in a PAN
+- Registration of PNEs in a PAN
+- Deregistration of PNEs in a PAN
+- Activation of PNEs in a PAN
+- Deactivation of PNEs in a PAN
+- Management of PNE identities within a PAN
+- Registration update of PNEs in a PAN
+- Combination management of PAN
+- Separation management of PAN
+- Capability announcement of PNEs in a PAN
+
+### 5.2.3 Security
+
+In order to maintain security between a PAN and a PLMN, MTs or MEs providing direct connectivity must be authenticated and authorized when they get attached to the network and start using/accessing 3GPP services. For authentication and authorization, existing security mechanisms, which are based on USIMs , shall be used.
+
+For improved security, the MT or ME may use suitable trusted computing technologies.
+
+#### 5.2.3.1 General
+
+- A secured interface between the UE holding the (U)SIM and other PNE's in the PAN is required. This "local interface" must be able to protect against eavesdropping, and undetected modification attacks on security-related signalling data (e.g. authentication challenges and responses). Cryptographic or physical means may be used for this purpose.
+- Both endpoints of the local interface shall be mutually authenticated and authorized.
+- The ME/MT without (U)SIM shall be capable of communicating with the U(SIM) only if the UE containing (U)SIM is switched on and a (U)SIM is powered on. Furthermore the ME/MT without (U)SIM shall not be allowed to change the status of the UE with active (U)SIM, or the remote (U)SIM, e.g. to reset it, or to switch its power on or off.
+
+- The ME/MT without the (U)SIM shall be capable of detecting the presence and availability of the active (U)SIM on the UE containing it. It also has the ability to terminate an authenticated network sessions when, the (U)SIM is no longer accessible within a short monitoring time period.
+- The user shall have the capability to shut off sharing of (U)SIM feature. The owner of the UE holding the active (U)SIM should authorize its use.
+- Integrity and privacy of signalling between ME/MTs and the PLMN shall be supported. No leakage of (U)SIM information to the user, or any third party over the wireless interface (e.g. Bluetooth/WLAN).
+- Whenever someone (a specific device) tries to remotely access a (U)SIM for the first time some sort of alert shall be sent, e.g. a message will be displayed informing the user of the access. The user can then decide whether the access is authorized and can allow or disallow it.
+- The UE holding the (U)SIM should be responsible for mediating access to the (U)SIM Application/Data such as controlling the logical channels.
+- UICC presence detection shall be supported via the local interface.
+- When the (U)SIM is re-used over local interfaces, additional access control on the Applications/Data information shall be implemented by the UE holding the active (U)SIM compared to the case when it is accessed by the UE holding the (U)SIM directly. For example, some AT commands might have to be restricted.
+
+#### 5.2.3.2 PNE management requirements
+
+- Default Settings
+
+The default settings of any PNE coming from the manufacturer should always be set to "Do Not Auto Connect" or "Do Not Make Discoverable".
+
+The user must be aware that they are allowing their PNE to "be seen" by other devices.
+
+- Connection Confirmation
+
+A PNE shall only accept a connection from another PNE after receiving a confirmation from the user indicating willingness to accept such a connection (i.e. there should be no "auto-accept" feature on the PNE).
+
+The requesting PNE should represent itself via its Unique Identifier.
+
+### 5.2.4 Charging
+
+If any charges are made for the provision of PNM these should be levied to the active subscription of the PAN.
+
+## 5.3 PNE redirecting application
+
+The Personal Network may comprise more than one UE or PAN. Each entity belonging to a Personal Network is generally termed as a PNE. The PNE may be a single device or a group of devices. The Personal Network from a user's perspective is his own network. Any of his PNEs may connect to each other, whereby the user may restrict public access via means provided by PNM. Personal Network Elements may not have public user IDs (E.g. MSISDN or URI), and therefore "other" users are not able to directly address data to these TEs.
+
+The PNE Redirecting application is based on the PN UE Redirecting Service. In contrast to the PN UE Redirecting Service the PNE Redirecting application shall not only allow to activate/deactivate UEs but is able to direct data to particular TEs of the UEs or to connected MEs. Thus a PNE is not limited to UEs and it is possible to handle particular components within a UE or PAN as PNE.
+
+Annex shows a use case describing aspects of PNE-PNE connection.
+
+### 5.3.1 Requirements for PNE redirecting application
+
+- All PN UE Redirecting requirements shall apply to the PNE Redirecting Service with PNE substituting UE.
+
+- Registration data in the network shall include information that determines the PAN or UE a registered PNE belongs to. Furthermore registration data shall comprise the public user identities of the UEs and PANs in the Personal Network.
+- It shall not be possible to register PNEs that are neither part of a UE or registered component of a PAN.
+
+### 5.3.2 Usability requirements
+
+- All usability requirements of the PN UE Redirecting application shall apply to the PNE Redirecting Service.
+
+### 5.3.3 Security
+
+- Registration of PNEs to a PN shall require the consent of the subscriber by appropriate means, e.g. an "invite" function,
+- Advanced PNM shall ensure the integrity and confidentiality of between PNEs in a Personal Network.
+- The PNE shall be authenticated towards the PLMN based on a locally connected USIM. Only authorised and suitably authenticated PNEs should be able to use a locally connected USIM for network authentication purposes.
+
+### 5.3.4 Charging
+
+- All charges for terminating services shall be levied to the active subscription of the PAN where the activated PNE belongs to, even when a terminating service was originally addressed to another PNE belonging to the PN.
+- It shall be possible to raise registration/deregistration and activation/deactivation fees.
+
+## 5.4 PN access control for PNE networks
+
+- Guest UEs may be provided access to PNEs of a PN.
+
+### 5.4.1 Requirements for PN access control for PNE networks
+
+- All Service requirements for PN Access Control for Personal UE networks shall also apply to the PNE networks.
+
+### 5.4.2 Usability requirements for PN access control in PNE networks
+
+- PN access level settings for a particular PNE of the PN to be public / private
+
+# Annex A (informative): Use cases
+
+## A.1 Use case: Connection between PNEs of a PN
+
+PNM allows the communication between a PNE and PNEs of other UEs/PANs belonging to the same PN. For this purpose it shall be possible to establish a secure link between the PNEs of a PN. This is enabled by establishing secure links among locally connected devices of a PAN. In the example in figure 4 the PNEs have established a secure link. Through this secure link, a user is able to gain access from the ME in UE1 to the TE in UE2 at home and monitor the heating or burglar alarm system while away from home, therefore enabling the ME to be the active PNE for termination of the alarm service remotely. Figure 5 explains the secure PNE-PNE communications.
+
+The TE in UE2 has an own PNE Identifier that allows the ME in UE1 to identify and to directly communicate with the TE.
+
+
+
+The diagram shows a PLMN cloud at the top connected to two 'Access System' clouds. Below these are two user equipment (UE) areas: UE 1 (yellow oval) and UE 2 (blue oval), both part of a larger PN (purple oval). UE 1 contains a person icon, a mobile device (ME) with a red star (USIM Subscription), and three 'TE' boxes. UE 2 contains a mobile device (ME) with a red star, two 'TE' boxes, and a house icon. A blue double-headed arrow (Secure Connection) connects the ME in UE 1 to the ME in UE 2. Red double-headed arrows connect the PLMN to each Access System, and each Access System to the ME in its respective UE. A legend on the right shows a red star for 'USIM Subscription' and a blue double-headed arrow for 'Secure Connection'.
+
+Diagram illustrating the use case for connection between devices of a PN. A PLMN cloud is connected to two Access System clouds. UE 1 (yellow oval) contains a person, a mobile device (ME) with a USIM subscription (red star), and three TE boxes. UE 2 (blue oval) contains a mobile device (ME) with a USIM subscription (red star), two TE boxes, and a house. A secure connection (blue double-headed arrow) is established between the ME in UE 1 and the ME in UE 2. Red double-headed arrows connect the PLMN to the Access Systems, and the Access Systems to the MEs in UE 1 and UE 2. A legend indicates that a red star represents a USIM Subscription and a blue double-headed arrow represents a Secure Connection.
+
+Figure 4: Use case for connection between the devices of a PN
+
+
+
+Figure 5: Connection between the PNEs. This diagram illustrates the network architecture for connecting Personal Networks (PNs). At the top, a 'PLMN' cloud is connected to two 'Access System' clouds. Below these, two Personal Networks are shown: 'PPAN' (Personal Packet Network) on the left and 'PAN' (Personal Area Network) on the right. The PPAN contains three 'TEPNE' (Terminal Equipment PNE) units, each marked with a red star representing its identity. The PAN contains two 'TEPNE' units, also marked with red stars, and a house icon representing the network owner. A blue double-headed arrow indicates a 'Secure Connection' between the two Access Systems. Red double-headed arrows show the connection between the PLMN and the Access Systems, and between the Access Systems and the PNEs in the PNs. A legend on the right shows a red star for 'PNE Identity' and a blue double-headed arrow for 'Secure Connection'.
+
+Figure 5: Connection between the PNEs
+
+## A.2 Use case of UE-PN connection
+
+Personal UE Networks security requirements state that registration of a PNE to a PN requires the consent of the owner of the USIM associated with the PLMN. The description here concerns access of a Personal Network by a PNE external to that Personal Network. In the case of user A wishing to allow PNE B to register into his PN as a Guest UE, the user controls access to his PN, in other words PNM protects the privacy of A's PN. For example in figure 6, PNE B (ME) may only be allowed to access TE A1 and this is controlled by the user, and enabled by procedures. PNE B may access A's PN by appropriate means, e.g. an "invite function".
+
+
+
+Figure 6: Use case for UE-PN connection. This diagram shows a use case where an external PNE connects to a user's PN. A 'PLMN' cloud at the top is connected to two 'Access System' clouds. Below, 'PN: User A' is shown as a purple oval containing two 'TE PNE' units, 'TE PNE A1' and 'TE PNE A2', each with a red star. An external 'UE PNE B' (marked with a red star) is shown outside the PN. A blue double-headed arrow indicates a 'Secure Connection' between the two Access Systems. Red double-headed arrows show connections from the PLMN to the Access Systems, and from the Access Systems to the PNEs. A legend on the right shows a red star for 'Subscription' and a blue double-headed arrow for 'Secure Connection'.
+
+Figure 6: Use case for UE-PN connection
+
+## A.2a PN Access control: Parental control
+
+Alice has subscribed to PNM private network service. She has two UEs with her in the PN – UE 1a and UE 1b. She decides to give UE 1b to her son Bob. Bob is still a young kid and Alice worries about him getting calls from strangers. So she registers her UE (UE 1a) as default UE for access control. She then creates an access list that contains a list of registered callers (Guest UEs). Any calls from the registered callers (e.g. UE 3) or Guests are allowed to go through to the private UE (Bob's UE) directly. In case of unregistered callers (e.g. UE 2), the PN AS rejects the call directly or the PN Server queries Alice (UE 1a) whether the call can be continued. Alice can respond by allowing or disallowing (cancelling) the call. In addition, she may register the unregistered caller dynamically (on the fly) during session initiation procedures itself.
+
+
+
+The diagram shows the following components and interactions:
+
+- Legend:**
+ - Red arrow: Call setup
+ - Green arrow: Access Control
+ - Red star: USIM Subscription
+- PN AS:** Contains an "Access list". It mediates access control between the IMS Network and the PN.
+- IMS Network:** The central network component, involved in call setup and access control mediation.
+- PN (Private Network):** Contains:
+ - Default UE for access control (UE 1a):** Holds a USIM (red star) and is used for access control decisions.
+ - Private UE (UE 1b):** The target UE for calls.
+- External Callers:**
+ - Unregistered caller / Guest UE (UE 2):** Initiates call setup (red arrow) to the IMS Network. Access control (green arrow) is denied or requires confirmation.
+ - Registered caller (UE 3):** Initiates call setup (red arrow) to the IMS Network. Access control (green arrow) is granted.
+- Interactions:**
+ - UE 2 (Unregistered) → IMS Network: Call setup (red arrow).
+ - IMS Network → PN AS: Access Control (green arrow).
+ - PN AS → UE 1a: Confirmation with default UE (if caller is unregistered) (red arrow).
+ - UE 1a → PN AS: Response (green arrow).
+ - PN AS → IMS Network: Mediation by PN AS (green arrow).
+ - IMS Network → UE 1b: Call setup (red arrow).
+ - UE 3 (Registered) → IMS Network: Call setup (red arrow).
+ - IMS Network → PN AS: Access Control (green arrow).
+ - PN AS → IMS Network: Mediation by PN AS (green arrow).
+ - IMS Network → UE 1b: Call setup (red arrow).
+
+Figure 16: Use case for PN Access Control. The diagram illustrates the network architecture and call flow for parental control. It includes a PN AS (Private Network Application Server) with an access list, an IMS Network, and a PN (Private Network) containing UE 1a (Default UE for access control) and UE 1b (Private UE). External callers include an unregistered caller (UE 2) and a registered caller (UE 3). Call setup is shown with red arrows, and access control with green arrows. A legend defines the arrow types: red for Call setup, green for Access Control, and a red star for USIM Subscription.
+
+Figure 16: Use case for PN Access Control
+
+## A.3 Use case of PN-User access a PLMN from their PNEs
+
+Figure 7 shows a use case where a user terminates a video service with a PNEs, which is part of a PAN of the PN-User. In this use case the user has multiple PNEs. It is assumed that the required PNE can communicate with the PNE containing the USIM through PAN internal communication means when they are in close proximity. After authentication of the PNEs by the PLMN through the PNE holding the (U)SIM, the user can access the video service. The PNM has the capability to manage the UE components as a user's PAN. It shall have a binding table between the PNE holding the (U)SIM and the other PAN PNEs which includes their identities and addresses.
+
+Figure 8 shows a use case where a user utilizes a video service through PNEs that have their own network access means and thus a direct access means to a PNM. PNEs attached to a UE don't have their own USIM and may or may not have their own access means. The PNE holding the (U)SIM can authenticate these other PNEs to the PLMN when these PNEs are in close proximity to the UE. After authentication of the PNEs, the user can access the video service directly via the attached PNEs, with no help from the PNE holding the (U)SIM. Again, the PNM of a PLMN has the capability to manage more than one PNE under a PAN. As long as the PNEs are connected to the PNE holding the U(SIM) it shall
+
+be possible to keep the data communication channels through established access network means of the MEs themselves. If an PNE disassociates from the PNE holding the U(SIM), the data communication channels of the PAN PNE should be terminated immediately.
+
+Figure 9 shows a use case where a user receives a video service through PNEs which are directly connected to another access system (i.e. External IP network with a commercial relationship with the PNM service provider). When many packets (e.g. for a higher resolution or frame rate) are sent to a user for Video Service, the user may want to receive them directly through a more suitable PNE and access system. If the specific PNE has its own network connection, not via UE, the user can request the PNM to get a new data path via its own network connection e.g. Internet. In this case, the specific PNE must be authenticated and authorized by using the PNE holding the (U)SIM (i.e., a single USIM authority is shared by all the PNEs of the PAN) and the session is controlled by UE. The user can receive the video service through the PNE after the PNM establishes a new data path via the external IP network for Video Service. If the user wants to disconnect the new data path, which is already connected to a PNE, he/she can also request the release of new data path through PNM. The new data path of the PNE will be terminated immediately.
+
+
+
+Figure 7: Single network connection through PNE holding the (U)SIM of PAN. The diagram shows a Video Service connected to a PNM, which is connected to a PLMN (e.g. CS, PS). The PLMN is connected to a PAN (Personal Area Network) containing a ME (Mobile Equipment) and three TEs (Terminals). The ME is connected to the PLMN and has a USIM Subscription. User Data (solid blue line) flows from the Video Service through the PNM, PLMN, and ME to the TEs. Control Data (dashed red line) flows from the PNM through the ME to the TEs.
+
+Figure 7: Single network connection through PNE holding the (U)SIM of PAN
+
+
+
+Figure 8: Multiple network connections through 3GPP access systems. The diagram shows a Video Service connected to a PNM, which is connected to a PLMN (e.g. CS, PS). The PLMN is connected to a PAN containing a UE (User Equipment), a ME, and another ME. The UE is connected to the PLMN and has a USIM Subscription. User Data (solid blue line) flows from the Video Service through the PNM, PLMN, and UE to the MEs. Control Data (dashed red line) flows from the PNM through the UE to the MEs.
+
+Figure 8: Multiple network connections through 3GPP access systems
+
+
+
+Figure 9: Multiple network connections through other access system. The diagram shows a Video Service connected to a PNM, which is connected to a PLMN (e.g. CS, PS). The PLMN is connected to an Access System, which is connected to a PAN containing a UE and three MEs. The UE is connected to the PLMN and has a USIM Subscription. New User Data (solid green line) flows from the Video Service through the PNM, PLMN, and Access System to the MEs. User Data (solid blue line) flows from the Video Service through the PNM, PLMN, and UE to the MEs. Control Data (dashed red line) flows from the PNM through the UE to the MEs.
+
+Figure 9: Multiple network connections through other access system
+
+Note: If the access system is a non-3GPP network, there must be a commercial relationship between the HPLMN and the non-3GPP access system.
+
+## A.4 Use case for connection between guest UE and PN
+
+The Guest UE is registered into the PN after authentication mechanisms. This use case describes an example where the Guest UE belongs to a different service provider. Once registered into the PN, the Guest UE is allowed to access the
+
+PN, based on access control procedures set by the PN user for the particular Guest UE. For example, in fig 10 given below, the Guest UE is allowed to access the video service that the PN of the PNE holding the (U)SIM offers. That is the Guest UE is chosen for the termination of the specific service of video that the PN offers, The PNM facilitates this by secure authentication, registration and routing of the Guest UE.
+
+
+
+The diagram shows a network architecture. At the top, two clouds represent 'PNM - Service Provider' and 'Service Provider B'. Below 'PNM - Service Provider' are two clouds labeled 'Access System'. Below 'Service Provider B' is one cloud labeled 'Access System'. A large blue curved arrow connects 'PNM - Service Provider' to the 'Access System' under 'Service Provider B'. On the left, a purple oval labeled 'Personal Network (PN)' contains a 'UEUSIM holding PNE' (represented by a person icon), a 'Video server' (represented by a server icon), two 'Device' boxes, a 'RAN' (represented by a radio tower icon), and 'UE A' (represented by a mobile phone icon). Red double-headed arrows connect the 'PNM - Service Provider' cloud to the 'Access System' cloud, which is connected to the 'Video server'. Another red double-headed arrow connects the 'Video server' to the 'RAN', which is connected to 'UE A'. A red double-headed arrow also connects the 'PNM - Service Provider' cloud to the 'Personal Network (PN)' oval. On the right, a 'Guest UE' (represented by a mobile phone icon) is connected to the 'Access System' under 'Service Provider B' via a red double-headed arrow labeled 'Authentication'. Below the 'Guest UE' is a 'Video service client' (represented by a mobile phone icon). A red double-headed arrow connects the 'Guest UE' to the 'Video service client'. A red double-headed arrow also connects the 'Video service client' to the 'USIM Subscription' (represented by a star icon).
+
+Figure 10: Guest UE registered in PN. The diagram illustrates a network architecture where a Guest UE is connected to a Personal Network (PN) via a UEUSIM holding PNE. The PNE is connected to a PNM - Service Provider, which is further connected to Service Provider B. The PNM is also connected to an Access System, which is connected to another Access System. The Guest UE is connected to the second Access System via an Authentication process. The PNM is also connected to a Video server, which is connected to a Device. The Device is connected to a RAN, which is connected to UE A. The PNM is also connected to a Personal Network (PN) via a UEUSIM holding PNE. The Guest UE is connected to the second Access System via an Authentication process. The PNM is also connected to a Video server, which is connected to a Device. The Device is connected to a RAN, which is connected to UE A. The PNM is also connected to a Personal Network (PN) via a UEUSIM holding PNE.
+
+Figure 10: Guest UE registered in PN
+
+## A.5 Use case on UE redirection of terminating services
+
+A user owns two phones, a PDA, and a notebook. All devices have radio access means to the 3GPP System. Phones and PDA support UTRAN. The notebook allows access via WLAN. The user has subscribed the PNM PN UE redirection and registered all devices in the Personal Network.
+
+In a possible scenario the user is on an airport and must wait for a delayed plane. The user carries the notebook and one of the phones with her/him. The other two devices are left at home. Usually the user does not use the notebook for accessing 3GPP services. However, an Interworked WLAN access network may exist at the airport. Via the WLAN hotspot the user is able to establish a connection to the PLMN. To shorten the waiting time the user wants to utilize the WLAN hotspot for enjoying subscribed 3GPP multimedia services via the notebook. The services are configured for the termination at PDA and phones. The user needs a convenient solution to enable a temporary termination of the services with the notebook in order to benefit from the available advanced multimedia processing capabilities of the notebook and the high speed data access. Depending on the services the user would have to reconfigure either the services or the devices. In case of device reconfiguration a forwarding function would have to be set up at the phones and the PDA for directing services to the notebook. This is not only inconvenient but currently not feasible for the user as a part of the devices is left at home. Furthermore different redirecting settings would be required for CS and IMS. In praxis the complicated manual handling would hamper the flexible use of the available devices. Instead the user wants to switch on the notebook and press a button to activate the notebook for the service termination either temporarily or permanently. Depending on the user preferences the user interface may also offer to activate a specific subscribed service, like a multimedia news service. Beside of the minimized manual interaction the handling would be more natural. When the user wants to do something with a particular device the user does not expect the necessity to configure other entities. After finishing the usage of the multimedia services the user presses the deactivation button to stop a temporary activation. In non-temporary cases the activations are changed by activating one or more other devices at a later point in time. For instance, back at home the user may prefer to use the PDA for receiving the multimedia news. After switch-on the user simply presses the activation software button on the PDA to either receive the news exclusively or simultaneously on the PDA.
+
+
+
+Diagram illustrating the activation of UE 2 for directing service termination to UE 2. The diagram shows a 'Services' cloud connected to a 'PLMN' cloud, which contains a 'PNM' node. The 'PLMN' cloud is connected to two 'Access System' clouds. The 'Access System' clouds are connected to a 'Personal Network' cloud containing 'UE 1' and 'UE 2'. A dotted blue arrow represents the 'Original data flow to UE1', originating from 'Services' and passing through 'PLMN', 'PNM', and the left 'Access System' to 'UE 1'. A solid blue arrow represents the 'Redirection from UE1 to UE2', originating from 'UE 1' and passing through the right 'Access System' to 'UE 2'. Red arrows indicate connections between the 'Access System' clouds and the 'Personal Network' cloud, and between the 'PNM' node and the 'Access System' clouds.
+
+Figure 11: Activation of UE 2 for directing service termination to UE 2
+
+## A.6 Use case on PNE redirection of terminating services
+
+An advanced user does not only possess a number of different devices with 3GPP access for various purposes like a multimedia phone with advanced camera and music capabilities, a car phone with car specific features, or a smart phone with messaging and internet. The advanced user is interested in local connectivity between these devices and with other owned devices like a PDA and notebook. For instance, a user may be on a business tour with the car. The car has an in-built car phone. The user wants to utilize the 3GPP access of the car phone in order to terminate network services with the notebook. For this purpose the user sets up a local network between notebook and car phone. In this scenario the car phone provides the MT capabilities and the notebook acts as TE of the UE. With the PN UE redirection the user would only be able to redirect terminating services to the car UE. The TE device would not be known and visible to the PLMN routing. The user would have to configure the local network to achieve the proper forwarding and processing within the local network. Instead of complicated manual settings the user wants a simple natural method as provided by the PN UE Redirecting application. The user starts the notebook. Automatically the car phone is detected and a local connection with the car phone is established. Afterwards the user presses a software button for terminating all or selected services on the notebook. This should work independently of the radio access means available for the access to the 3GPP system. For example the notebook may have own radio access means. After activation of the notebook for service termination the radio access means do not matter. Independent of the radio access technology and possibly simultaneous connections to the 3GPP system the chosen services are always directed to the notebook.
+
+
+
+Figure 12: Activating a particular device of a UE or PAN for service termination. The diagram shows a network architecture where data flows from Services through PLMN and PNM to Access Systems, and then to User Equipment (UE). UE 1 is connected to three TE (Terminal Equipment) devices. UE 2 is connected to TE 1 and TE 2. A legend indicates that a dotted blue arrow represents the 'Original data flow to UE1' and a solid blue arrow represents the 'Redirection to TE1 of UE2'. The entire UE area is labeled 'Personal Network'.
+
+Figure 12: Activating a particular device of a UE or PAN for service termination
+
+## A.7 Use case: Selective update based on capability lists
+
+Alice has a home PAN or UE where her video device (sink) has been registered as a PNE at the PNM. Alice is traveling to her office, and has registered her UE to the PN. For all video services she has chosen her video device as the terminating device, where it can be recorded for future viewing. She has also requested the PN service to update her on PN settings based on the service she is interested in (video devices, audio devices, printing devices, other services). For some reason, her video device (TE) becomes unavailable (Eg: power goes down or switched off by somebody else or network down.etc). The home PAN or UE deactivates this video device (TE) and makes the PN service aware of this deactivation. The PN service then lets Alice know of this event based on the capability list she has chosen.
+
+As an effect, Alice after receiving this update may change her video terminating settings to her own UE.
+
+## A.8 Use case: Combination of two PANs
+
+Figure 13 and Figure 14 describe the PNM functionality on combination of two PANs. When PAN1 and PAN2 are physically close to each other, the user may hope to combine them into one PAN and designate UE1 as the new PAN's UE. The PNM needs to deactivate UE2 and update relative registration information (binding tables and addresses) of UE1 and PNEs in PAN2. The PNEs in PAN2 (ME2 and TE2) may keep or change the original network positions, i.e. the connection to UE2 or UE1 (described as case 1 and case 2). After the combination UE2 and ME2 need to be authorized through UE1 to get access for any new service, and then they can access those services directly.
+
+
+
+This diagram illustrates the network architecture for the combination of two PANs (case 1). At the top, a 'Video Service' and a 'PNM' (green box) are connected to a 'PLMN' (pink cloud, e.g., CS, PS and AIPN). The PLMN is connected to two User Equipment (UE) devices, UE1 and UE2, via dashed red arrows representing control data. UE1 is part of PAN1, which includes ME1 and TE1. UE2 is part of PAN2, which includes ME2 and TE2. A solid blue arrow represents user data flowing from the PLMN to UE1. A dashed red arrow represents control data flowing from the PNM to UE1. A solid blue arrow represents user data flowing from the PLMN to UE2. A dashed red arrow represents control data flowing from the PNM to UE2. A legend on the right indicates: a red star for USIM Subscription, a solid blue arrow for User Data, and a dashed red arrow for Control Data.
+
+Diagram of two PANs (case 1) showing data flows between a Video Service, PNM, PLMN, and two User Equipment (UE) devices.
+
+Figure 13: Combination of two PANs (case 1)
+
+
+
+This diagram illustrates the network architecture for the combination of two PANs (case 2). It is similar to Figure 13 but with a key difference in the control data flow. The 'Video Service', 'PNM', and 'PLMN' components are identical. The control data flow (dashed red arrows) from the PNM goes to UE1, but from UE1, it branches out to both ME1 and ME2. The user data flow (solid blue arrows) from the PLMN goes to UE1 and then to UE2. The legend on the right is the same as in Figure 13.
+
+Diagram of two PANs (case 2) showing data flows between a Video Service, PNM, PLMN, and two User Equipment (UE) devices.
+
+Figure 14: Combination of two PANs (case 2)
+
+## A.9 Use case: Separation of PAN
+
+Figure 15 describes the PNM functionality on separation of PAN. It's very likely to happen that some devices in a PAN move far away and almost out of control, or even they are not so far away but the user wants to separate them into two PANs. In this use case the user want to separate ME2, TE2 and ME3 from the PAN and to form a new PAN (PAN2). The PNM shall designate a UE for PAN2, i.e. activate a ME (ME3) who contains a USIM. The PN shall update registration information of ME3 (UE2), ME2, TE2 and UE1 due to the changes of network positions. And the PNEs in PAN2 including UE2 need to get authorized through the USIM on UE2 for new services provided by PLMN.
+
+
+
+The diagram illustrates the network architecture for the separation of a PAN. At the top, a cloud represents the PLMN (e.g. CS, PS and AIPN), which is connected to a 'Video Service' and a 'PNM' (Personal Network Manager). Below the PLMN, there are two separate PANs, PAN1 and PAN2, each enclosed in a dashed yellow oval. PAN1 contains a UE1 (User Equipment) with a USIM (indicated by a red star), ME1 (Mobile Equipment), and TE1 (Terminal Equipment). PAN2 contains a UE2 (ME3) with a USIM (indicated by a red star), ME2 (Mobile Equipment), and TE2 (Terminal Equipment). Blue arrows represent 'User Data' flowing from the PLMN to the UEs. Red dashed arrows represent 'Control Data' flowing from the PNM to the UEs. A legend on the right side of the diagram identifies the symbols: a red star for 'USIM Subscription', a blue arrow for 'User Data', and a red dashed arrow for 'Control Data'.
+
+Diagram illustrating the separation of a PAN into two separate PANs (PAN1 and PAN2) connected to a PLMN.
+
+Figure 15: Separation of PAN
+
+# Annex B (Informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|------------------------------------------------------------------------------------------------|-------|-------|-------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| 05/07/2005 | | | | | | | | Initial draft produced by PNM Rapporteur and provided to the SA1 email exploder for comment. | - | 0.0.0 | |
+| 13/07/2005 | | | | | | | | Revised initial draft produced by Rapporteur after SWG at SA1#29. | 0.0.0 | 0.0.1 | |
+| 01.08.05 | | | | | | | | Revised by the rapporteur, taking account conclusions at SA#29 | 0.0.1 | 0.0.2 | |
+| 25.10.05 | | | | | | | | Revised by the rapporteur, providing definition for TE, and additional use cases | 0.0.2 | 0.0.3 | |
+| 26.10.05 | | | | | | | | Output document at SA1#30 | 0.0.3 | 0.1.0 | |
+| 05.12.05 | | | | | | | | To SA#30 for information | 0.1.0 | 1.0.0 | |
+| 16.02.06 | | | | | | | | Clarification of identifiers, alignment with IMS and call forwarding extensions. | 1.0.0 | 1.1.0 | |
+| 17.02.06 | | | | | | | | Addition of private network services involving guest access, priority termination of services. | 1.1.0 | 1.2.0 | |
+| 17.02.06 | | | | | | | | Raised to version 2.0.0 for approval at SA #31 | 1.2.0 | 2.0.0 | |
+| SP-31 | SP-060213 | | | | | | | Approved at SA #31 | 2.0.0 | 7.0.0 | |
+| SP-32 | SP-060313 | S1-060643 | 22.259 | 0001 | - | Rel-7 | F | Requirement for selective update of PNM settings | 7.0.0 | 7.1.0 | PNPAN |
+| SP-32 | SP-060313 | S1-060644 | 22.259 | 0002 | - | Rel-7 | F | Use Cases for UE Redirecting Service and PNE Redirecting Service | 7.0.0 | 7.1.0 | PNPAN |
+| SP-32 | SP-060452 | - | 22.259 | 0003 | 2 | Rel-7 | F | Requirements for TEs/MEs capabilities using services through access systems | 7.0.0 | 7.1.0 | PNPAN |
+| SP-32 | SP-060440 | - | 22.259 | 0004 | 1 | Rel-7 | D | CR – Editorial changes of TS 22.259 - PNM | 7.0.0 | 7.1.0 | PNPAN |
+| SP-32 | SP-060441 | - | 22.259 | 0005 | 1 | Rel-7 | F | CR to 22.259 – Security-related changes | 7.0.0 | 7.1.0 | PNPAN |
+| SP-32 | SP-060313 | S1-060655 | 22.259 | 0006 | - | Rel-8 | B | Combination and Separation Management for PANs | 7.1.0 | 8.0.0 | PNM |
+| SP-33 | SP-060467 | S1-060960 | 22.259 | 0008 | - | Rel-8 | A | CR on Corrections and clarifications to TS 22.259 - PNM | 8.0.0 | 8.1.0 | PNPAN |
+| SP-34 | SP-060763 | S1-061391 | 22.259 | 0010 | - | Rel-8 | A | Clarification on simultaneously access | 8.1.0 | 8.2.0 | PNPAN |
+| SP-35 | SP-070132 | S1-070253 | 22.259 | 0011 | 1 | Rel-8 | C | Private network services - Use case and requirements | 8.2.0 | 8.3.0 | TEI8 |
+| SP-35 | SP-070132 | S1-070254 | 22.259 | 0012 | - | Rel-8 | D | Removal of paragraph numbers from entire document | 8.2.0 | 8.3.0 | TEI8 |
+| SP-38 | SP-070852 | S1-071658 | 22.259 | 0014 | 1 | Rel-8 | F | Clarification of functionality and | 8.3.0 | 8.4.0 | PNM |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|----------------------------------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| | | | | | | | | possible simplification. | | | |
+| SP-38 | SP-070926 | - | 22.259 | 0013 | 3 | Rel-8 | F | Terminology alignment with CT1 | 8.3.0 | 8.4.0 | PNM |
+| SP-40 | - | - | 22.259 | | | Rel-9 | | Creation of Rel-9 to keep text on PNE (removed in v.8.5.0 by CR 0015r1 to align to Stage 3). Content identical to v.8.4.0. | 8.4.0 | 9.0.0 | PNME |
+| SP-45 | SP-090479 | S1-093253 | 22.259 | 0015 | 2 | Rel-9 | F | EPNM Clarification | 9.0.0 | 9.1.0 | PAN_EPN M |
+| SP-46 | SP-090840 | S1-094286 | 22.259 | 0016 | 1 | Rel-9 | F | ME support in Rel-9 | 9.1.0 | 9.2.0 | PAN_EPN M |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.2.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2019-07 | - | - | - | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22261/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Rel-18/22_series/22261/23cb65390082ab306c15bd3d8196135e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f0737260a64565691bc4ebf51749a14651059ad
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/23cb65390082ab306c15bd3d8196135e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f19befbaac36ec1ce191db57998c8dc5a24e724431c5635f66053b8c778a5b53
+size 95964
diff --git a/marked/Rel-18/22_series/22261/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-18/22_series/22261/2cf3896394a2342a2b46c504ab9a8830_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1a7b4382183179b16bcc62c5887e2604c67fb27
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/2cf3896394a2342a2b46c504ab9a8830_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c6ee0ae331bff0e716346cc7633a7c75bdd0fe240d9492a48256b13557c5e6f
+size 38739
diff --git a/marked/Rel-18/22_series/22261/3c04a06e1bebf2ba5a6af7a74285bfc3_img.jpg b/marked/Rel-18/22_series/22261/3c04a06e1bebf2ba5a6af7a74285bfc3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04737a4654d3880018d42e299a4b814c14279442
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/3c04a06e1bebf2ba5a6af7a74285bfc3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb7f18e252202dddb1a934fc10630bd05e4abc562df6f9f3b3f8ad92c1a5531c
+size 42900
diff --git a/marked/Rel-18/22_series/22261/48adb97a6a4a14b039450192f25cc1e0_img.jpg b/marked/Rel-18/22_series/22261/48adb97a6a4a14b039450192f25cc1e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..311d64210427b2e720cc07d51904c41489410c7a
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/48adb97a6a4a14b039450192f25cc1e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bef5e11e9ffde462c49d3a9a7f8cf4a881af40c1d96b7f8be090d1d71cf644f8
+size 109973
diff --git a/marked/Rel-18/22_series/22261/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22261/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ef277d9764e2f57751fd91593de9af4e82551bd
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3a815039bbc82b99499013d797d7b118c5057ca80a91e2c31e53c2ad1e992ef
+size 9476
diff --git a/marked/Rel-18/22_series/22261/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22261/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f3f0faec336d9f36ac51c7b670e537f696cd23a
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22e37f51f4e6dcdc6a430d6a6c27df851dc3c22e8ec7422768e2b9744780a5b4
+size 5727
diff --git a/marked/Rel-18/22_series/22261/737abf1e655afd3324b6b3987945d913_img.jpg b/marked/Rel-18/22_series/22261/737abf1e655afd3324b6b3987945d913_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ecd12ab8fa0140cd492c3cf6a7123ad646ddf441
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/737abf1e655afd3324b6b3987945d913_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51e92b588d9be50653b042ffe2bca8290f49e2cfe09fc3be83fbcb9f2b257ea3
+size 66160
diff --git a/marked/Rel-18/22_series/22261/7c6fd006fc4d304794392d41fab4ee10_img.jpg b/marked/Rel-18/22_series/22261/7c6fd006fc4d304794392d41fab4ee10_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1293c23e67eebe195469d031c3025fbb0e61f9ca
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/7c6fd006fc4d304794392d41fab4ee10_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d0dd220b8af79e216874d8ca1ecc62e7d394dfccb197878b9f43e6fd65a98dd
+size 98901
diff --git a/marked/Rel-18/22_series/22261/a37adbbe12ec735a20ead2466363d07a_img.jpg b/marked/Rel-18/22_series/22261/a37adbbe12ec735a20ead2466363d07a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..080bf670010b6966871faa626ffd90548bfcd7e5
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/a37adbbe12ec735a20ead2466363d07a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da421794d5eb98c49c8f6ea02be8eea28ad17521613f4f8104d5929e9a75bc15
+size 130420
diff --git a/marked/Rel-18/22_series/22261/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg b/marked/Rel-18/22_series/22261/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c138130325fbf321e8284009f76de9e9fb7ca632
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/c93c4b33a2b42c8dd6d82a354f2f89f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f33ede715cf9fc96bbf8b0d7bb5209e8bdda65f731c7a1fd567e55587e7b778f
+size 57066
diff --git a/marked/Rel-18/22_series/22261/raw.md b/marked/Rel-18/22_series/22261/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8efbe30a1948d5b8ee3884a077f368e4f4b9241f
--- /dev/null
+++ b/marked/Rel-18/22_series/22261/raw.md
@@ -0,0 +1,4208 @@
+
+
+# 3GPP TS 22.261 V18.12.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like signal icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+Fifth, Generation, 5G
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+©2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|---------------------------------------------------------|----|
+| Foreword ..... | 8 |
+| Introduction ..... | 8 |
+| 1 Scope..... | 9 |
+| 2 References..... | 9 |
+| 3 Definitions, symbols and abbreviations..... | 11 |
+| 3.1 Definitions..... | 11 |
+| 3.2 Abbreviations ..... | 14 |
+| 4 Overview..... | 15 |
+| 5 High-level requirements..... | 16 |
+| 5.1 Migration to 5G..... | 16 |
+| 5.1.1 Description ..... | 16 |
+| 5.1.2 Requirements..... | 16 |
+| 5.1.2.1 Interworking between 5G systems..... | 16 |
+| 5.1.2.2 Legacy service support ..... | 16 |
+| 5.1.2.3 Interoperability with legacy 3GPP systems ..... | 17 |
+| 6 Basic capabilities..... | 17 |
+| 6.1 Network slicing ..... | 17 |
+| 6.1.1 Description ..... | 17 |
+| 6.1.2 Requirements..... | 17 |
+| 6.1.2.1 General..... | 17 |
+| 6.1.2.2 Management..... | 18 |
+| 6.1.2.3 Network slice constraints..... | 19 |
+| 6.1.2.4 Cross-network slice coordination ..... | 19 |
+| 6.2 Diverse mobility management ..... | 19 |
+| 6.2.1 Description ..... | 19 |
+| 6.2.2 General requirements..... | 20 |
+| 6.2.3 Service continuity requirements ..... | 20 |
+| 6.2.4 Roaming related requirements..... | 20 |
+| 6.3 Multiple access technologies..... | 21 |
+| 6.3.1 Description ..... | 21 |
+| 6.3.2 Requirements..... | 21 |
+| 6.3.2.1 General..... | 21 |
+| 6.3.2.2 E-UTRA access..... | 21 |
+| 6.3.2.3 Satellite access ..... | 21 |
+| 6.3.2.4 Fixed broadband access ..... | 22 |
+| 6.4 Resource efficiency ..... | 22 |
+| 6.4.1 Description ..... | 22 |
+| 6.4.2 Requirements..... | 23 |
+| 6.4.2.1 General..... | 23 |
+| 6.4.2.2 Efficient bulk operations for IoT ..... | 23 |
+| 6.4.2.3 Efficient management for IoT..... | 24 |
+| 6.4.2.4 Efficient control plane ..... | 24 |
+| 6.5 Efficient user plane..... | 24 |
+| 6.5.1 Description ..... | 24 |
+| 6.5.2 Requirements..... | 24 |
+| 6.6 Efficient content delivery ..... | 25 |
+| 6.6.1 Description ..... | 25 |
+| 6.6.2 Requirements..... | 26 |
+| 6.7 Priority, QoS, and policy control ..... | 26 |
+| 6.7.1 Description ..... | 26 |
+| 6.7.2 Requirements..... | 27 |
+| 6.8 Dynamic policy control..... | 27 |
+| 6.9 Connectivity models..... | 28 |
+
+| | | |
+|----------|-----------------------------------------------------------------------|----|
+| 6.9.1 | Description ..... | 28 |
+| 6.9.2 | Requirements..... | 28 |
+| 6.9.2.1 | General..... | 28 |
+| 6.9.2.2 | Services and Service Continuity ..... | 28 |
+| 6.9.2.3 | Permission and Authorization..... | 29 |
+| 6.9.2.4 | Relay UE Selection..... | 29 |
+| 6.9.2.5 | Satellite and Relay UEs ..... | 29 |
+| 6.10 | Network capability exposure..... | 30 |
+| 6.10.1 | Description ..... | 30 |
+| 6.10.2 | Requirements..... | 30 |
+| 6.11 | Context-aware network ..... | 32 |
+| 6.11.1 | Description ..... | 32 |
+| 6.11.2 | Requirements..... | 32 |
+| 6.12 | Self backhaul..... | 33 |
+| 6.12.1 | Description ..... | 33 |
+| 6.12.2 | Requirements..... | 33 |
+| 6.13 | Flexible broadcast/multicast service ..... | 33 |
+| 6.13.1 | Description ..... | 33 |
+| 6.13.2 | Requirements..... | 33 |
+| 6.14 | Subscription aspects ..... | 34 |
+| 6.14.1 | Description ..... | 34 |
+| 6.14.2 | Requirements..... | 35 |
+| 6.15 | Energy efficiency ..... | 35 |
+| 6.15.1 | Description ..... | 35 |
+| 6.15.2 | Requirements..... | 36 |
+| 6.16 | Markets requiring minimal service levels ..... | 36 |
+| 6.16.1 | Description ..... | 36 |
+| 6.16.2 | Requirements..... | 36 |
+| 6.17 | Extreme long range coverage in low density areas..... | 36 |
+| 6.17.1 | Description ..... | 36 |
+| 6.17.2 | Requirements..... | 37 |
+| 6.18 | Multi-network connectivity and service delivery across operators..... | 37 |
+| 6.18.1 | Description ..... | 37 |
+| 6.18.2 | Requirements..... | 37 |
+| 6.19 | 3GPP access network selection..... | 37 |
+| 6.19.1 | Description ..... | 37 |
+| 6.19.2 | Requirements..... | 38 |
+| 6.20 | eV2X aspects..... | 38 |
+| 6.20.1 | Description ..... | 38 |
+| 6.20.2 | Requirements..... | 38 |
+| 6.21 | NG-RAN Sharing..... | 39 |
+| 6.21.1 | Description ..... | 39 |
+| 6.21.2 | Requirements..... | 39 |
+| 6.22 | Unified access control ..... | 39 |
+| 6.22.1 | Description ..... | 39 |
+| 6.22.2 | Requirements..... | 39 |
+| 6.22.2.1 | General..... | 39 |
+| 6.22.2.2 | Access identities ..... | 40 |
+| 6.22.2.3 | Access categories..... | 40 |
+| 6.23 | QoS monitoring ..... | 41 |
+| 6.23.1 | Description ..... | 41 |
+| 6.23.2 | Requirements..... | 42 |
+| 6.24 | Ethernet transport services ..... | 43 |
+| 6.24.1 | Description ..... | 43 |
+| 6.24.2 | Requirements..... | 43 |
+| 6.25 | Non-public networks ..... | 44 |
+| 6.25.1 | Description ..... | 44 |
+| 6.25.2 | Requirements..... | 44 |
+| 6.26 | 5G LAN-type service ..... | 45 |
+| 6.26.1 | Description ..... | 45 |
+| 6.26.2 | Requirements..... | 46 |
+| 6.26.2.1 | General..... | 46 |
+
+| | | |
+|----------|---------------------------------------------------------------|----|
+| 6.26.2.2 | 5G LAN-virtual network (5G LAN-VN)..... | 46 |
+| 6.26.2.3 | Creation and management ..... | 46 |
+| 6.26.2.4 | Privacy ..... | 47 |
+| 6.26.2.5 | Traffic types..... | 47 |
+| 6.26.2.6 | Discovery ..... | 47 |
+| 6.26.2.7 | (void)..... | 47 |
+| 6.26.2.8 | Indirect communication mode ..... | 47 |
+| 6.26.2.9 | Service exposure ..... | 48 |
+| 6.27 | Positioning services..... | 48 |
+| 6.27.1 | Description ..... | 48 |
+| 6.27.2 | Requirements..... | 48 |
+| 6.28 | Cyber-physical control applications in vertical domains ..... | 49 |
+| 6.28.1 | Description ..... | 49 |
+| 6.28.2 | Requirements..... | 50 |
+| 6.28.2.1 | General..... | 50 |
+| 6.28.2.2 | Smart Grid..... | 50 |
+| 6.29 | Messaging aspects..... | 50 |
+| 6.29.1 | Description ..... | 50 |
+| 6.29.2 | Requirements..... | 50 |
+| 6.30 | Steering of roaming ..... | 51 |
+| 6.30.1 | Description ..... | 51 |
+| 6.30.2 | Requirements..... | 51 |
+| 6.31 | Minimization of Service Interruption..... | 51 |
+| 6.31.1 | Description ..... | 51 |
+| 6.31.2 | Requirements..... | 51 |
+| 6.31.2.1 | General..... | 51 |
+| 6.31.2.2 | Disaster Condition ..... | 51 |
+| 6.31.2.3 | Disaster Roaming..... | 52 |
+| 6.32 | UAV aspects..... | 52 |
+| 6.32.1 | Description ..... | 52 |
+| 6.32.2 | Requirements..... | 52 |
+| 6.33 | Video, imaging and audio for professional applications..... | 52 |
+| 6.33.1 | Description ..... | 52 |
+| 6.33.2 | Requirements..... | 53 |
+| 6.34 | Critical medical applications..... | 53 |
+| 6.34.1 | Description ..... | 53 |
+| 6.34.2 | Requirements..... | 53 |
+| 6.35 | Service Function Chaining ..... | 53 |
+| 6.35.1 | Introduction ..... | 53 |
+| 6.35.2 | General Requirements ..... | 54 |
+| 6.35.3 | Service Function Management ..... | 54 |
+| 6.36 | 5G Timing Resiliency ..... | 54 |
+| 6.36.1 | Overview ..... | 54 |
+| 6.36.2 | General ..... | 55 |
+| 6.36.3 | Monitoring and Reporting ..... | 55 |
+| 6.36.4 | Service Exposure ..... | 55 |
+| 6.37 | Ranging based services ..... | 55 |
+| 6.37.1 | Description ..... | 55 |
+| 6.37.2 | Requirements..... | 56 |
+| 6.38 | Personal IoT Networks and Customer Premises Networks ..... | 57 |
+| 6.38.1 | Description ..... | 57 |
+| 6.38.2 | Requirements..... | 57 |
+| 6.38.2.1 | General..... | 57 |
+| 6.38.2.2 | Gateways..... | 58 |
+| 6.38.2.3 | Operation without 5G core network connectivity ..... | 58 |
+| 6.38.2.4 | Discovery ..... | 59 |
+| 6.38.2.5 | Relay Selection ..... | 59 |
+| 6.38.2.6 | Security ..... | 59 |
+| 6.38.2.7 | QoS ..... | 60 |
+| 6.38.2.8 | Charging..... | 60 |
+| 6.38.2.9 | Creation and Management..... | 60 |
+| 6.39 | 5G IMS Multimedia Telephony Service ..... | 61 |
+
+| | | |
+|-----------|---------------------------------------------------------------------------|----|
+| 6.39.1 | Description ..... | 61 |
+| 6.39.2 | General ..... | 61 |
+| 6.39.3 | Service Exposure ..... | 61 |
+| 6.40 | AI/ML model transfer in 5GS ..... | 62 |
+| 6.40.1 | Description ..... | 62 |
+| 6.40.2 | Requirements ..... | 63 |
+| 6.41 | Providing Access to Local Services ..... | 63 |
+| 6.41.1 | Description ..... | 63 |
+| 6.41.2 | Requirements ..... | 64 |
+| 6.41.2.1 | General ..... | 64 |
+| 6.41.2.2 | Configuration of Localized Services in Hosting Network ..... | 64 |
+| 6.41.2.3 | User Manual Selection of Localized Services via Hosting Network ..... | 65 |
+| 6.41.2.4 | UE Configuration, Provisioning, Authentication and Authorization ..... | 65 |
+| 6.41.2.5 | UE Discovery, Selection and Access ..... | 65 |
+| 6.41.2.6 | Hosting Network Localized Services and Home Operator Services ..... | 66 |
+| 6.41.2.7 | Returning to Home Network ..... | 66 |
+| 6.41.2.8 | Charging ..... | 66 |
+| 6.41.2.9 | Regulatory Services ..... | 66 |
+| 6.41.2.10 | Multicast/Broadcast ..... | 66 |
+| 6.42 | Mobile base station relays ..... | 67 |
+| 6.42.1 | Description ..... | 67 |
+| 6.42.2 | Requirements ..... | 67 |
+| 6.43 | Tactile and multi-modal communication service ..... | 69 |
+| 6.43.1 | Description ..... | 69 |
+| 6.43.2 | Requirements ..... | 69 |
+| 6.44 | Support of Roaming services providers ..... | 70 |
+| 6.44.1 | Overview ..... | 70 |
+| 6.44.2 | Requirements ..... | 70 |
+| 7 | Performance requirements ..... | 71 |
+| 7.1 | High data rates and traffic densities ..... | 71 |
+| 7.2 | Low latency and high reliability ..... | 72 |
+| 7.2.1 | Overview ..... | 72 |
+| 7.2.2 | Scenarios and KPIs ..... | 72 |
+| 7.2.3 | Other requirements ..... | 73 |
+| 7.2.3.1 | (void) ..... | 73 |
+| 7.2.3.2 | Wireless road-side infrastructure backhaul ..... | 73 |
+| 7.3 | High-accuracy positioning ..... | 76 |
+| 7.3.1 | Description ..... | 76 |
+| 7.3.2 | Requirements ..... | 76 |
+| 7.3.2.1 | General ..... | 76 |
+| 7.3.2.2 | Requirements for horizontal and vertical positioning service levels ..... | 76 |
+| 7.3.2.3 | Other performance requirements ..... | 78 |
+| 7.4 | KPIs for a 5G system with satellite access ..... | 78 |
+| 7.4.1 | Description ..... | 78 |
+| 7.4.2 | Requirements ..... | 78 |
+| 7.5 | High-availability IoT traffic ..... | 79 |
+| 7.5.1 | Description ..... | 79 |
+| 7.5.2 | Requirements ..... | 80 |
+| 7.6 | High data rate and low latency ..... | 81 |
+| 7.6.1 | AR/VR ..... | 81 |
+| 7.7 | KPIs for UE to network relaying in 5G system ..... | 82 |
+| 7.8 | KPIs for 5G Timing Resiliency ..... | 83 |
+| 7.9 | KPIs for ranging based services ..... | 84 |
+| 7.10 | KPIs for AI/ML model transfer in 5GS ..... | 87 |
+| 7.11 | KPIs for tactile and multi-modal communication service ..... | 88 |
+| 8 | Security ..... | 91 |
+| 8.1 | Description ..... | 91 |
+| 8.2 | General ..... | 91 |
+| 8.3 | Authentication ..... | 92 |
+| 8.4 | Authorization ..... | 92 |
+
+| | | |
+|----------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------|
+| 8.5 | Identity management..... | 92 |
+| 8.6 | Regulatory ..... | 93 |
+| 8.7 | Fraud protection ..... | 93 |
+| 8.8 | Resource efficiency..... | 93 |
+| 8.9 | Data security and privacy..... | 94 |
+| 8.10 | 5G Timing Resiliency ..... | 94 |
+| 9 | Charging aspects ..... | 94 |
+| 9.1 | General ..... | 94 |
+| 9.2 | 5G LAN..... | 95 |
+| 9.3 | 5G Timing Resiliency ..... | 95 |
+| Annex A (informative): Void..... | | 96 |
+| Annex B (informative): Void ..... | | 96 |
+| Annex C (informative): Relation of communication service availability and reliability..... | | 97 |
+| Annex D (informative): Critical-communication use cases..... | | 98 |
+| D.1 | Factory automation – motion control..... | 98 |
+| D.1.0 | General ..... | 98 |
+| D.1.1 | Service area and connection density..... | 99 |
+| D.1.2 | Security ..... | 99 |
+| D.2 | Factory automation – other use cases..... | 100 |
+| D.2.0 | General ..... | 100 |
+| D.2.1 | Service area and connection density..... | 101 |
+| D.2.2 | Security ..... | 101 |
+| D.3 | Process automation..... | 101 |
+| D.3.0 | General ..... | 101 |
+| D.3.1 | Remote control ..... | 102 |
+| D.3.2 | Process and asset monitoring..... | 102 |
+| D.3.3 | Service area ..... | 102 |
+| D.4 | Electric-power distribution and smart grid..... | 102 |
+| D.4.0 | General ..... | 102 |
+| D.4.1 | Medium voltage..... | 102 |
+| D.4.1.0 | Overview..... | 102 |
+| D.4.1.1 | Service area and connection density ..... | 104 |
+| D.4.1.2 | Security ..... | 104 |
+| D.4.2 | High voltage ..... | 104 |
+| D.4.2.0 | Overview..... | 104 |
+| D.4.2.1 | Service area and connection density..... | 104 |
+| D.4.2.2 | Security ..... | 105 |
+| D.5 | Intelligent transport systems – infrastructure backhaul..... | 105 |
+| D.5.0 | General ..... | 105 |
+| D.5.1 | Service area and connection density..... | 105 |
+| Annex E (informative): (void) ..... | | 106 |
+| Annex F (informative): QoS Monitoring ..... | | 106 |
+| F.1 | QoS monitoring for assurance..... | 106 |
+| F.2 | Network Diagnostics ..... | 107 |
+| Annex G (informative): Asset Tracking use cases..... | | 107 |
+| G.1 | Asset Tracking..... | 107 |
+| G.2 | Battery life expectancy and message size to support example use cases for asset tracking ..... | 107 |
+| Annex H (informative): Interworking between Network Operators and Application Providers for localized services..... | | 108 |
+| Annex I (informative): Change history ..... | | 110 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 need to support different kinds of UEs (e.g. for the Internet of Things (IoT)), services, and technologies is driving the technology revolution to a high-performance and highly efficient 3GPP system. The drivers include IoT, Virtual Reality (VR), industrial control, ubiquitous on-demand coverage, as well as the opportunity to meet customized market needs. These drivers require enhancements to the devices, services, and technologies well established by 3GPP. The key objective with the 5G system is to be able to support new deployment scenarios to address diverse market segments.
+
+This document compiles requirements that define a 5G system.
+
+The 5G system is characterised, for example, by:
+
+- Support for multiple access technologies
+- Scalable and customizable network
+- Advanced Key Performance Indicators (KPIs) (e.g. availability, latency, reliability, user experienced data rates, area traffic capacity)
+- Flexibility and programmability (e.g. network slicing, diverse mobility management, Network Function Virtualization)
+- Resource efficiency (both user plane and control plane)
+- Seamless mobility in densely populated and heterogeneous environment
+- Support for real time and non-real time multimedia services and applications with advanced Quality of Experience (QoE)
+
+# --- 1 Scope
+
+The present document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278 [5].
+
+# --- 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] NGMN 5G White Paper v1.0, February 2015.
+- [3] 3GPP TS 22.011: "Service accessibility".
+- [4] Void
+- [5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+- [6] 3GPP TS 22.101: "Service aspects; Service principles".
+- [7] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service (MBMS)".
+- [8] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services".
+- [9] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios".
+- [10] NGMN, "Recommendations for NGMN KPIs and Requirements for 5G", June 2016
+- [11] 3GPP TS 22.115: "Service aspects; Charging and billing".
+- [12] Void
+- [13] Soriano, R., Alberto, M., Collazo, J., Gonzales, I., Kupzo, F., Moreno, L., & Lorenzo, J. OpenNode. Open Architecture for Secondary Nodes of the Electricity Smartgrid. In Proceedings CIRED 2011 21st International Conference on Electricity Distribution, CD1. June 2011.
+- [14] North American Electric Reliability Council. Frequently Asked Questions (FAQs) Cyber Security Standards CIP-002-1 through CIP-009-1. Available: [http://www.nerc.com/docs/standards/sar/Revised\\_CIP-002-009\\_FAQs\\_06Mar06.pdf](http://www.nerc.com/docs/standards/sar/Revised_CIP-002-009_FAQs_06Mar06.pdf). 2006.
+- [15] McTaggart, Craig, et al. "Improvements in power system integrity protection schemes". Developments in Power System Protection (DPSP 2010). Managing the Change, 10th IET International Conference on. IET, 2010.
+- [16] IEEE Power Engineering Society – Power System Relaying Committee – System Protection Subcommittee Working Group C-6. Wide Area Protection and Emergency Control.
+- [17] Begovic, Miroslav, et al. "Wide-area protection and emergency control". Proceedings of the IEEE 93.5, pp. 876-891, 2005.
+
+- [18] ITU-T Recommendation G.1000 "Communications quality of service: A framework and definitions".
+- [19] IEC 61907, "Communication network dependability engineering".
+- [20] NIST, "Framework for Cyber-Physical Systems", 2016.
+- [21] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
+- [22] 3GPP TS 22.262: "Message Service within the 5G System".
+- [23] 3GPP TS 22.289: "Mobile Communication System for Railways".
+- [24] 3GPP TS 22.071: "Location Services".
+- [25] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
+- [26] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP".
+- [27] Void
+- [28] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)".
+- [29] Void
+- [30] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT)".
+- [31] IEEE 1588-2019, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems.
+- [32] IEC 61850-9-3-2016 - IEC/IEEE International Standard - Communication networks and systems for power utility automation – Part 9-3: Precision time protocol profile for power utility automation.
+- [33] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN"
+- [34] ATIS-0900005: "Technical Report on GPS Vulnerability",
+[https://access.atis.org/apps/group\\_public/download.php/36304/ATIS-0900005.pdf](https://access.atis.org/apps/group_public/download.php/36304/ATIS-0900005.pdf)
+- [35] European Commission, Regulatory Technical Standard 25. Level of accuracy of business clocks
+[https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25\\_en.pdf](https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25_en.pdf) (annex
+[https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex\\_en.pdf](https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex_en.pdf))
+- [36] 5G-ACIA, "Exposure of 5G capabilities for Connected Industries and Automation Applications",
+5G-ACIA white paper, February 2021, [https://5g-acia.org/wp-content/uploads/2021/04/5G-ACIA\\_ExposureOf5GCapabilitiesForConnectedIndustriesAndAutomationApplications.pdf](https://5g-acia.org/wp-content/uploads/2021/04/5G-ACIA_ExposureOf5GCapabilitiesForConnectedIndustriesAndAutomationApplications.pdf)
+- [37] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services".
+- [38] ITU-T, "Technology Watch Report: The Tactile Internet", August 2014.
+- [39] D. Soldani, Y. Guo, B. Barani, P. Mogensen, I. Chih-Lin, S. Das, "5G for ultra-reliable low-latency communications". IEEE Network. 2018 Apr 2; 32(2):6-7.
+- [40] O. Holland et al., "The IEEE 1918.1 "Tactile Internet" Standards Working Group and its Standards," Proceedings of the IEEE, vol. 107, no. 2, Feb. 2019.
+- [41] Altınsoy, M. E., Blauert, J., & Treier, C., "Inter-Modal Effects of Non-Simultaneous Stimulus Presentation," A. Alippi (Ed.), Proceedings of the 7th International Congress on Acoustics, Rome, Italy, 2001.
+- [42] Hirsh I.J., and Sherrick C.E, 1961. J. Exp. Psychol 62, 423-432
+
+- [43] Altinsoy, M.E. (2012). "The Quality of Auditory-Tactile Virtual Environments," Journal of the Audio Engineering Society, Vol. 60, No. 1/2, pp. 38-46, Jan.-Feb. 2012.
+- [44] M. Di Luca and A. Mahnan, "Perceptual Limits of Visual-Haptic Simultaneity in Virtual Reality Interactions," 2019 IEEE World Haptics Conference (WHC), 2019, pp. 67-72, doi: 10.1109/WHC.2019.8816173.
+- [45] K. Antonakoglou et al., "Toward Haptic Communications Over the 5G Tactile Internet", IEEE Communications Surveys & Tutorials, 20 (4), 2018.
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**5G enhanced positioning area:** a subset of the 5G positioning service area that is assumed to be provided with additional infrastructure or deploy a particular set of positioning technologies to enhance positioning services.
+
+NOTE 1: The enhanced positioning service area represents for example a factory plant, a dense urban area, an area along a road or railway track, a tunnel and covers both indoor and outdoor environments.
+
+**5G LAN-type service:** a service over the 5G system offering private communication using IP and/or non-, i.e. UEs that are members of the same 5G LAN-VN IP type communications.
+
+**5G LAN-virtual network:** a virtual network capable of supporting 5G LAN-type service.
+
+**5G satellite access network:** 5G access network using at least one satellite.
+
+**5G positioning service area:** a service area where positioning services would solely rely on infrastructures and positioning technologies that can be assumed to be present anywhere where 5G is present (e.g. a country-wide operator-supplied 5G network, GNSS, position/motion sensors).
+
+NOTE 2: This includes both indoor and any outdoor environments.
+
+**active communication:** a UE is in active communication when it has one or more connections established. A UE may have any combination of PS connections (e.g. PDP contexts, active PDN connections).
+
+**activity factor:** percentage value of the amount of simultaneous active UEs to the total number of UEs where active means the UEs are exchanging data with the network.
+
+**aggregated QoS:** QoS requirement(s) that apply to the traffic of a group of UEs.
+
+**area traffic capacity:** total traffic throughput served per geographic area.
+
+**authorised administrator:** a user or other entity authorised to partially configure and manage a network node in a CPN (e.g. a PRAS, or eRG) or a PIN element in a PIN.
+
+**communication service availability:** percentage value of the amount of time the end-to-end communication service is delivered according to a specified QoS, divided by the amount of time the system is expected to deliver the end-to-end service.
+
+NOTE 3: The end point in "end-to-end" is the communication service interface.
+
+NOTE 4: The communication service is considered unavailable if it does not meet the pertinent QoS requirements. For example, the communication service is unavailable if a message is not correctly received within a specified time, which is the sum of maximum allowed end-to-end latency and survival time.
+
+**Customer Premises Network:** a network located within a premise (e.g. a residence, office or shop), which is owned, installed and/or (at least partially) configured by the customer of a public network operator.
+
+**direct device connection:** the connection between two UEs without any network entity in the middle.
+
+**direct network connection:** one mode of network connection, where there is no relay UE between a UE and the 5G network.
+
+**Disaster Condition:** This is the condition that a government decides when to initiate and terminate, e.g. a natural disaster. When this condition applies, users may have the opportunity to mitigate service interruptions and failures.
+
+**Disaster Inbound Roamer:** A user that (a) cannot get service from the PLMN it would normally be served by, due to failure of service during a Disaster Condition, and (b) is able to register with other PLMNs.
+
+**Disaster Roaming:** This is the special roaming policy that applies during a Disaster Condition.
+
+**end-to-end latency:** the time that it takes to transfer a given piece of information from a source to a destination, measured at the communication interface, from the moment it is transmitted by the source to the moment it is successfully received at the destination.
+
+**evolved Residential Gateway:** a gateway between the public operator network (fixed/mobile/cable) and a customer premises network.
+
+**holdover:** A clock A, previously synchronized/syntonized to another clock B (normally a primary reference or a Master Clock) but whose frequency is determined in part using data acquired while it was synchronized/syntonized to B, is said to be in holdover or in the holdover mode as long as it is within its accuracy requirements.
+
+NOTE 4bis: holdover is defined in [31]
+
+**Holdover time:** the time period that is available to repair the first priority timing source when it is lost (e.g., when the primary GNSS reference is lost). During this period the synchronization accuracy requirement should be guaranteed, e.g., by means of defining multiple synchronization references.
+
+**Hosted Service:** a service containing the operator's own application(s) and/or trusted third-party application(s) in the Service Hosting Environment, which can be accessed by the user.
+
+**hybrid access:** access consisting of multiple different access types combined, such as fixed wireless access and wireline access.
+
+**indirect network connection:** one mode of network connection, where there is a relay UE between a UE and the 5G network.
+
+**IoT device:** a type of UE which is dedicated for a set of specific use cases or services and which is allowed to make use of certain features restricted to this type of UEs.
+
+NOTE 5: An IoT device may be optimized for the specific needs of services and application being executed (e.g. smart home/city, smart utilities, e-Health and smart wearables). Some IoT devices are not intended for human type communications.
+
+**network slice:** a set of network functions and corresponding resources necessary to provide the required telecommunication services and network capabilities.
+
+**NG-RAN:** a radio access network connecting to the 5G core network which uses NR, E-UTRA, or both.
+
+**non-public network:** a network that is intended for non-public use.
+
+**NR:** the new 5G radio access technology.
+
+**Personal IoT Network:** A configured and managed group of at least one UE PIN Element and one or more PIN Element that communicate with each other.
+
+**PIN Element:** UE or non-3GPP device that can communicate within a PIN.
+
+**PIN direct connection:** the connection between two PIN Elements without any 3GPP RAN or core network entity in the middle.
+
+NOTE 5A: A PIN direct connection could internally be relayed by other PIN Elements.
+
+NOTE 5B: When a PIN direct connection is between two PIN Elements that are UEs this direct connection is typically known as a direct device connection.
+
+**PIN Element with Gateway Capability:** a UE PIN Element that has the ability to provide connectivity to and from the 5G network for other PIN Elements.
+
+NOTE 5C: A PIN Element can have both PIN management capability and Gateway Capability.
+
+**PIN Element with Management Capability:** A PIN Element with capability to manage the PIN.
+
+**positioning service availability:** percentage value of the amount of time the positioning service is delivering the required position-related data within the performance requirements, divided by the amount of time the system is expected to deliver the positioning service according to the specification in the targeted service area.
+
+**positioning service latency:** time elapsed between the event that triggers the determination of the position-related data and the availability of the position-related data at the system interface.
+
+**Premises Radio Access Station:** a base station installed at a customer premises network.
+
+**priority service:** a service that requires priority treatment based on regional/national or operator policies.
+
+**private communication:** a communication between two or more UEs belonging to a restricted set of UEs.
+
+**private network:** an isolated network deployment that does not interact with a public network.
+
+**private slice:** a dedicated network slice deployment for the sole use by a specific third-party.
+
+**Ranging:** refers to the determination of the distance between two UEs and/or the direction of one UE from the other one via direct device connection.
+
+**relative positioning:** relative positioning is to estimate position relatively to other network elements or relatively to other UEs.
+
+**reliability:** in the context of network layer packet transmissions, percentage value of the packets successfully delivered to a given system entity within the time constraint required by the targeted service out of all the packets transmitted.
+
+**satellite:** a space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO) typically at an altitude between 300 km to 2 000 km, Medium-Earth Orbit (MEO) typically at an altitude between 8 000 to 20 000 km, or Geostationary satellite Earth Orbit (GEO) at 35 786 km altitude.
+
+**satellite access:** direct connectivity between the UE and the satellite.
+
+**satellite NG-RAN:** a NG-RAN which uses NR in providing satellite access to UEs.
+
+**service area:** geographic region where a 3GPP communication service is accessible.
+
+NOTE 6: The service area can be indoors.
+
+NOTE 7: For some deployments, e.g. in process industry, the vertical dimension of the service area can be considerable.
+
+**service continuity:** the uninterrupted user experience of a service that is using an active communication when a UE undergoes an access change without, as far as possible, the user noticing the change.
+
+NOTE 8: In particular service continuity encompasses the possibility that after a change the user experience is maintained by a different telecommunication service (e.g. tele- or bearer service) than before the change.
+
+NOTE 9: Examples of access changes include the following. For EPS: CS/PS domain change. For EPS and 5G: radio access change, switching between a direct network connection and an indirect network connection.
+
+**Service Hosting Environment:** the environment, located inside of 5G network and fully controlled by the operator, where Hosted Services are offered from.
+
+**synchronization threshold:** A synchronization threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one of which is presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous.
+
+NOTE 10: This definition is based on [41].
+
+**survival time:** the time that an application consuming a communication service may continue without an anticipated message.
+
+**Time to First Fix (TTFF):** time elapsed between the event triggering for the first time the determination of the position-related data and the availability of the position-related data at the positioning system interface.
+
+**User Equipment:** An equipment that allows a user access to network services via 3GPP and/or non-3GPP accesses.
+
+**user experienced data rate:** the minimum data rate required to achieve a sufficient quality experience, with the exception of scenario for broadcast like services where the given value is the maximum that is needed.
+
+**wireless backhaul:** a link which provides an interconnection between 5G network nodes and/or transport network using 5G radio access technology.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|-----------|-----------------------------------------------------------|
+| 5G LAN-VN | 5G LAN-Virtual Network |
+| A/S | Actuator/Sensor |
+| CPN | Customer Premises Network |
+| eFMSS | Enhancement to Flexible Mobile Service Steering |
+| eRG | Evolved Residential Gateway |
+| eV2X | Enhanced V2X |
+| FL | Federated Learning |
+| FMSS | Flexible Mobile Service Steering |
+| GEO | Geostationary satellite Earth Orbit |
+| ICP | Internet Content Provider |
+| ID | Identification |
+| IMU | Inertial Measurement Unit |
+| IOPS | Isolated E-UTRAN Operation for Public Safety |
+| LEO | Low-Earth Orbit |
+| MBS | Metropolitan Beacon System |
+| MCS | Mission Critical Services |
+| MCX | Mission Critical X, with X = PTT or X = Video or X = Data |
+| MEO | Medium-Earth Orbit |
+| MIoT | Massive Internet of Things |
+| MMTEL | Multimedia Telephony |
+| MPS | Multimedia Priority Service |
+| MSGin5G | Message Service Within the 5G System |
+| NPN | Non-Public Network |
+| PIN | Personal IoT Network |
+| PRAS | Premises Radio Access Station |
+| RSTP | Rapid Spanning Tree Protocol |
+| SEES | Service Exposure and Enablement S |
+| SST | Slice/Service Type |
+| TBS | Terrestrial Beacon System |
+| TTFF | Time To First Fix |
+| UAV | Uncrewed Aerial Vehicle |
+| UTC | Coordinated Universal Time |
+| XR | Extended Reality |
+
+# 4 Overview
+
+Unlike previous 3GPP systems that attempted to provide a 'one size fits all' system, the 5G system is expected to be able to provide optimized support for a variety of different services, different traffic loads, and different end user communities. Various industry white papers, most notably, the NGMN 5G White Paper [2], describe a multi-faceted 5G system capable of simultaneously supporting multiple combinations of reliability, latency, throughput, positioning, and availability. This technology revolution is achievable with the introduction of new technologies, both in access and the core, such as flexible, scalable assignment of network resources. In addition to increased flexibility and optimization, a 5G system needs to support stringent KPIs for latency, reliability, throughput, etc. Enhancements in the radio interface contribute to meeting these KPIs as do enhancements in the core network, such as network slicing, in-network caching and hosting services closer to the end points.
+
+A 5G system also supports new business models such as those for IoT and enterprise managed networks. Drivers for the 5G KPIs include services such as Uncrewed Aerial Vehicle (UAV) control, Augmented Reality (AR), and factory automation. Network flexibility enhancements support self-contained enterprise networks, installed and maintained by network operators while being managed by the enterprise. Enhanced connection modes and evolved security facilitate support of massive IoT, expected to include tens of millions of UEs sending and receiving data over the 5G network.
+
+Flexible network operations are the mainstay of the 5G system. The capabilities to provide this flexibility include network slicing, network capability exposure, scalability, and diverse mobility. Other network operations requirements address the necessary control and data plane resource efficiencies, as well as network configurations that optimize service delivery by minimizing routing between end users and application servers. Enhanced charging and security mechanisms handle new types of UEs connecting to the network in different ways. The enhanced flexibility of the 5G system also allows to cater to the needs of various verticals. For example, the 5G system introduces the concept of non-public networks providing exclusive access for a specific set of users and specific purpose(s). Non-public networks can, depending on deployment and (national) regulations, support different subsets of 5G functionality. In this specification 5G network requirements apply to both NPNs and PLMNs, unless specified otherwise. Additionally, there are specific requirements dedicated only to NPNs or PLMNs, which are indicated accordingly. More information can be found in Section 6.25.
+
+Mobile Broadband (MBB) enhancements aim to meet a number of new KPIs. These pertain to high data rates, high user density, high user mobility, highly variable data rates, deployment, and coverage. High data rates are driven by the increasing use of data for services such as streaming (e.g. video, music, and user generated content), interactive services (e.g. AR), and IoT. These services come with stringent requirements for user experienced data rates as well as associated requirements for latency to meet service requirements. Additionally, increased coverage in densely populated areas such as sports arenas, urban areas, and transportation hubs has become essential for pedestrians and users in urban vehicles. New KPIs on traffic and connection density enable both the transport of high volumes of data traffic per area (traffic density) and transport of data for a high number of connections (e.g. UE density or connection density). Many UEs are expected to support a variety of services which exchange either a very large (e.g. streaming video) or very small (e.g. data burst) amount of data. The 5G system will handle this variability in a resource efficient manner. All of these cases introduce new deployment requirements for indoor and outdoor, local area connectivity, high user density, wide area connectivity, and UEs travelling at high speeds.
+
+Another aspect of 5G KPIs includes requirements for various combinations of latency and reliability, as well as higher accuracy for positioning. These KPIs are driven by support for both commercial and public safety services. On the commercial side, industrial control, industrial automation, UAV control, and AR are examples of those services. Services such as UAV control will require more precise positioning information that includes altitude, speed, and direction, in addition to horizontal coordinates.
+
+Support for Massive Internet of Things (MIoT) brings many new requirements in addition to those for the enhanced KPIs. The expansion of connected things introduces a need for significant improvements in resource efficiency in all system components (e.g. UEs, IoT devices, radio, access network, core network).
+
+The 5G system also aims to enhance its capability to meet KPIs that emerging V2X applications require. For these advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed, are made more stringent.
+
+# --- 5 High-level requirements
+
+## 5.1 Migration to 5G
+
+### 5.1.1 Description
+
+The 5G system supports most of the existing EPS services, in addition to many new services. The existing EPS services can be accessed using the new 5G access technologies even where the EPS specifications might indicate E-UTRA(N) only. Only new or changed service requirements for new or changed services are specified in this TS. The few EPS capabilities that are not supported by the 5G system are identified in clause 5.1.2.2 below.
+
+### 5.1.2 Requirements
+
+#### 5.1.2.1 Interworking between 5G systems
+
+The 5G system shall support a UE with a 5G subscription roaming into a 5G Visited Mobile Network which has a roaming agreement with the UE's 5G Home Mobile Network.
+
+The 5G system shall enable a Visited Mobile Network to provide support for establishing home network provided data connectivity as well as visited network provided data connectivity.
+
+The 5G system shall enable a Visited Mobile Network to provide support for services provided in the home network as well as provide services in the visited network. Whether a service is provided in the visited network or in the home network is determined on a service by service basis.
+
+The 5G system shall provide a mechanism for a network operator to limit access to its services for a roaming UE, (e.g. based on roaming agreement).
+
+The 5G system shall provide a mechanism for a network operator to direct a UE onto a partnership network for routing all or some of the UE user plane and associated control plane traffic over the partnership network, subject to an agreement between the operators.
+
+#### 5.1.2.2 Legacy service support
+
+In principle, the 5G system shall support all EPS capabilities (e.g. from TSs 22.011, 22.101, 22.278, 22.185, 22.071, 22.115, 22.153, 22.173, 22.468). However,
+
+- voice service continuity from NG-RAN to GERAN shall not be supported,
+- voice service continuity from NG-RAN to UTRAN CS should be supported (see Note),
+- voice service continuity from GERAN to NG-RAN shall not be supported,
+- voice service continuity from UTRAN to NG-RAN shall not be supported,
+- CS fallback from NG-RAN to GERAN shall not be supported,
+- CS fallback from NG-RAN to UTRAN shall not be supported,
+- seamless handover between NG-RAN and GERAN shall not be supported,
+- seamless handover between NG-RAN and UTRAN shall not be supported,
+- access to a 5G core network via GERAN or UTRAN shall not be supported,
+- video service continuity between 5GS and UMTS shall not be supported,
+- IP address preservation for PS service when UE moves between 5GS and GSM/UMTS shall not be supported, and
+- Service continuity between 5GS and CDMA2000 shall not be supported.
+
+NOTE: Architectural or protocol changes needed to support voice service continuity from NG-RAN to UTRAN CS are expected to have minimum impact on architecture, specifications, or the development of the 5G New Core and New Radio.
+
+#### 5.1.2.3 Interoperability with legacy 3GPP systems
+
+The 5G system shall support mobility procedures between a 5G core network and an EPC with minimum impact to the user experience (e.g. QoS, QoE).
+
+# --- 6 Basic capabilities
+
+## 6.1 Network slicing
+
+### 6.1.1 Description
+
+Network slicing allows the operator to provide customised networks. For example, there can be different requirements on functionality (e.g. priority, charging, policy control, security, and mobility), differences in performance requirements (e.g. latency, mobility, availability, reliability and data rates), or they can serve only specific users (e.g. MPS users, Public Safety users, corporate customers, roamers, or hosting an MVNO).
+
+A network slice can provide the functionality of a complete network, including radio access network functions, core network functions (e.g. potentially from different vendors) and IMS functions. One network can support one or several network slices.
+
+### 6.1.2 Requirements
+
+#### 6.1.2.1 General
+
+The serving 5G network shall support providing connectivity to home and roaming users in the same network slice.
+
+In shared 5G network configuration, each operator shall be able to apply all the requirements from this clause to their allocated network resources.
+
+The 5G system shall be able to support IMS as part of a network slice.
+
+The 5G system shall be able to support IMS independent of network slices.
+
+For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall be able to support the UE to access the most suitable network slice in minimum time (e.g. based on the location of the UE, ongoing applications, UE capability, frequency configured for the network slice).
+
+5G system shall minimize signalling exchange and service interruption time for a network slice, e.g. when restrictions related to radio resources change (e.g., frequencies, RATs).
+
+The 5G system shall be able to minimize power consumption of a UE (e.g. reduce unnecessary cell measurements), in an area where no authorized network slice is available.
+
+When a UE moves out of the service area of a network slice for an active application, the 5G system shall be able to minimize impact on the active applications (e.g., providing early notification).
+
+NOTE 1: Various methods can be used to detect whether the UE moves toward the border area and to notify the UE.
+
+The 5G system shall support a mechanism for a UE to select and access network slice(s) based on UE capability, ongoing application, radio resources assigned to the slice, and policy (e.g., application preference).
+
+The 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs
+
+For UEs that have the ability to obtain service from more than one VPLMN simultaneously, the following requirements apply:
+
+- When a roaming UE with a single PLMN subscription requires simultaneous access to multiple network slices and the network slices are not available in a single VPLMN, the 5G system shall enable the UE to:
+- be registered to more than one VPLMN simultaneously; and
+- use network slices from more than one VPLMN simultaneously
+- The HPLMN shall be able to authorise a roaming UE with a single PLMN subscription to be registered to more than one VPLMN simultaneously in order to access network slices of those VPLMNs.
+- The HPLMN shall be able to provide a UE with permission and prioritisation information of the VPLMNs the UE is authorised to register to in order to use specific network slices.
+
+NOTE 2: The above requirements assume certain UE capabilities, e.g. the ability to be connected to more than one PLMN simultaneously.
+
+#### 6.1.2.2 Management
+
+The 5G system shall allow the operator to create, modify, and delete a network slice.
+
+The 5G system shall allow the operator to define and update the set of services and capabilities supported in a network slice.
+
+The 5G system shall allow the operator to configure the information which associates a UE to a network slice.
+
+The 5G system shall allow the operator to configure the information which associates a service to a network slice.
+
+The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice.
+
+The 5G system shall support a mechanism for the VPLMN, as authorized by the HPLMN, to assign a UE to a network slice with the needed services or to a default network slice.
+
+The 5G system shall enable a UE to be simultaneously assigned to and access services from more than one network slice of one operator.
+
+Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network.
+
+Creation, modification, and deletion of a network slice shall have no or minimal impact on traffic and services in other network slices in the same network.
+
+The 5G system shall support scaling of a network slice, i.e. adaptation of its capacity.
+
+The 5G system shall enable the network operator to define a minimum available capacity for a network slice. Scaling of other network slices on the same network shall have no impact on the availability of the minimum capacity for that network slice.
+
+The 5G system shall enable the network operator to define a maximum capacity (e.g., number of UEs, number of data sessions) for a network slice.
+
+The 5G system shall enable the network operator to define a priority order between different network slices in case multiple network slices compete for resources on the same network.
+
+The 5G system shall support means by which the operator can differentiate policy control, functionality and performance provided in different network slices.
+
+#### 6.1.2.3 Network slice constraints
+
+The 5G system shall support a mechanism to prevent a UE from trying to access a radio resource dedicated to a specific private slice for any purpose other than that authorized by the associated third-party.
+
+NOTE 1: UEs that are not authorized to access a specific private slice will not be able to access it for emergency calls if the private slice does not support emergency services.
+
+The 5G system shall support a mechanism to configure a specific geographic area in which a network slice is accessible, i.e. a UE shall be within the geographical area in order to access the network slice.
+
+The 5G system shall support a mechanism to limit a UE to only receiving service from an authorized slice.
+
+For a UE authorized to access to multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall minimize service interruption time when the UE changes the access from one network slice to another network slice. (e.g. based on changes of active applications).
+
+For traffic pertaining to a network slice offered via a relay node, 5G system shall use only radio resources (e.g. frequency band) allowed for the network slice.
+
+NOTE 2: Allowed radio resources (e.g., frequency band) may be different for direct network connections (between UE and NG-RAN) than for backhaul connections (between the relay node and the NG-RAN).
+
+The 5G system shall support a mechanism to prevent a UE from registering with a network slice when the maximum number of UEs for that slice are registered.
+
+The 5G system shall support a mechanism to prevent a UE from establishing a new data session within a network slice when the maximum number of data sessions for that slice are established.
+
+NOTE 3: Based on national/regional regulations and operator policy, exemptions can be provided for UEs configured for priority services (e.g., MPS) and for priority service sessions.
+
+#### 6.1.2.4 Cross-network slice coordination
+
+The 5G system shall support a mechanism to provide time stamps with a common time base at the monitoring API, for services that cross multiple network slices and 5G networks.
+
+The 5G system shall provide suitable APIs to coordinate network slices in multiple 5G networks so that the selected communication services of a non-public network can be extended through a PLMN (e.g. the service is supported by a slice in the non-public network and a slice in the PLMN).
+
+The 5G system shall provide a mechanism to enable an MNO to operate a hosted non-public network and private slice(s) of its PLMN associated with the hosted non-public network in a combined manner.
+
+## 6.2 Diverse mobility management
+
+### 6.2.1 Description
+
+A key feature of 5G is support for UEs with different mobility management needs. 5G will support UEs with a range of mobility management needs, including UEs that are
+
+- stationary during their entire usable life (e.g. sensors embedded in infrastructure),
+- stationary during active periods, but nomadic between activations (e.g. fixed access),
+- mobile within a constrained and well-defined space (e.g. in a factory), and
+- fully mobile.
+
+Moreover, some applications require the network to ensure seamless mobility of a UE so that mobility is hidden from the application layer to avoid interruptions in service delivery while other applications have application specific means to ensure service continuity. But these other applications can still require the network to minimize interruption time to ensure that their application-specific means to ensure service continuity work effectively.
+
+With the ever-increasing multimedia broadband data volumes, it is also important to enable the offloading of IP traffic from the 5G network onto traditional IP routing networks via an IP anchor node close to the network edge. As the UE moves, changing the IP anchor node can be needed in order to reduce the traffic load in the system, reduce end-to-end latency and provide a better user experience.
+
+The flexible nature of a 5G system will support different mobility management methods that minimize signalling overhead and optimize access for these different types of UEs.
+
+### 6.2.2 General requirements
+
+The 5G network shall allow operators to optimize network behaviour (e.g. mobility management support) based on the mobility patterns (e.g. stationary, nomadic, spatially restricted mobility, full mobility) of a UE or group of UEs.
+
+The 5G system shall enable operators to specify and modify the types of mobility support provided for a UE or group of UEs.
+
+The 5G system shall optimize mobility management support for a UE or group of UEs that use only mobile originated communications.
+
+The 5G system shall support inter- and/or intra- access technology mobility procedures within 5GS with minimum impact to the user experience (e.g. QoS, QoE).
+
+### 6.2.3 Service continuity requirements
+
+The 5G system shall enable packet loss to be minimized during inter- and/or intra- access technology changes for some or all connections associated with a UE.
+
+The 5G system shall minimize interruption time during inter- and/or intra- access technology mobility for some or all connections associated with a UE.
+
+NOTE: The interruption time includes all delays which have impact on service continuity.
+
+For applications that require the same IP address during the lifetime of the session, the 5G system shall enable maintaining the IP address assigned to a UE when moving across different cells and access technologies for connections associated with a UE.
+
+The 5G system shall enable minimizing impact to the user experience (e.g. minimization of interruption time) when changing the IP address and IP anchoring point for some or all connections associated with a UE.
+
+The 5G system shall support service continuity for a remote UE, when the remote UE changes from a direct network connection to an indirect network connection and vice-versa.
+
+The 5G system shall support service continuity for a remote UE, when the remote UE changes from one relay UE to another and both relay UEs use 3GPP access to the 5G core network.
+
+For a 5G system with satellite access, the following requirements apply:
+
+- The 5G system shall support service continuity between 5G terrestrial access network and 5G satellite access networks owned by the same operator or owned by different operators having an agreement.
+
+### 6.2.4 Roaming related requirements
+
+For a 5G system with satellite access, the following requirements apply:
+
+- A 5G system with satellite access shall enable roaming of UE supporting both satellite access and terrestrial access between 5G satellite networks and 5G terrestrial networks.
+- UEs supporting satellite access shall support optimized network selection and reselection to PLMNs with satellite access, based on home operator policy.
+
+## 6.3 Multiple access technologies
+
+### 6.3.1 Description
+
+The 5G system will support 3GPP access technologies, including one or more NR and E-UTRA as well as non-3GPP access technologies. Interoperability among the various access technologies will be imperative. For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP or non-3GPP access technology for a service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE. New technology such as satellite and wide area base stations will increase coverage and availability. This clause provides requirements for interworking with the various combinations of access technologies.
+
+### 6.3.2 Requirements
+
+#### 6.3.2.1 General
+
+Based on operator policy, the 5G system shall enable the UE to select, manage, and efficiently provision services over the 3GPP or non-3GPP access.
+
+Based on operator policy, the 5G system shall support steering a UE to select certain 3GPP access network(s).
+
+Based on operator policy, the 5G system shall be able to dynamically offload part of the traffic (e.g. from 3GPP RAT to non-3GPP access technology), taking into account traffic load and traffic type.
+
+Based on operator policy, the 5G system shall be able to provide simultaneous data transmission via different access technologies (e.g. NR, E-UTRA, non-3GPP), to access one or more 3GPP services.
+
+When a UE is using two or more access technologies simultaneously, the 5G system shall be able to optimally distribute user traffic over the access technologies in use, taking into account e.g. service, traffic characteristics, radio characteristics, and UE's moving speed.
+
+The 5G system shall be able to support data transmissions optimized for different access technologies (e.g. 3GPP, non-3GPP) for UEs that are simultaneously connected to the network via different accesses.
+
+Based on operator policy, the 5G system shall be able to add or drop the various access connections for a UE during a session.
+
+The 5G system shall be able to support mobility between the supported access networks (e.g. NG-RAN, WLAN, fixed broadband access network, 5G satellite access network).
+
+The 5G system shall support UEs with multiple radio and single radio capabilities.
+
+The 5G system shall support dynamic and static network address allocation of a common network address to the UE over all supported access types.
+
+The 5G system shall support a set of identities for a single user in order to provide a consistent set of policies and a single set of services across 3GPP and non-3GPP access types.
+
+The 5G system shall support the capability to operate in licensed and/or unlicensed bands.
+
+#### 6.3.2.2 E-UTRA access
+
+The 5G system shall be able to support seamless handover between NR and E-UTRA.
+
+The 5G system shall support UEs with dual radio capability (i.e. a UE that can transmit on NR and E-UTRA simultaneously) as well as UEs with single radio capability (i.e. a UE that cannot transmit on NR and E-UTRA simultaneously).
+
+#### 6.3.2.3 Satellite access
+
+The 5G system shall be able to provide services using satellite access.
+
+A 5G system with satellite access shall support different configurations where the radio access network is either a satellite NG-RAN or a non-3GPP satellite access network, or both.
+
+A UE supporting satellite access shall be able to provide or assist in providing its location to the 5G network.
+
+A 5G system with satellite access shall be able to determine a UE's location in order to provide service (e.g. route traffic, support emergency calls) in accordance with the governing national or regional regulatory requirements applicable to that UE.
+
+The 5G system with satellite access shall be able to support low power MIoT type of communications.
+
+#### 6.3.2.4 Fixed broadband access
+
+The 5G system shall be able to efficiently support connectivity using fixed broadband access.
+
+NOTE: The specification of fixed broadband access network is outside the scope of 3GPP.
+
+The 5G system shall support use of a relay UE that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+
+The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+
+## 6.4 Resource efficiency
+
+### 6.4.1 Description
+
+5G introduces the opportunity to design a system to be optimized for supporting diverse UEs and services. While support for IoT is provided by EPS, there is room for improvement in efficient resource utilization that can be designed into a 5G system whereas they are not easily retrofitted into an existing system. Some of the underlying principles of the potential service and network operation requirements associated with efficient configuration, deployment, and use of UEs in the 5G network include bulk provisioning, resource efficient access, optimization for UE originated data transfer, and efficiencies based on the reduced needs related to mobility management for stationary UEs and UEs with restricted range of movement.
+
+As sensors and monitoring UEs are deployed more extensively, the need to support UEs that send data packages ranging in size from a small status update in a few bits to streaming video increases. A similar need exists for smart phones with widely varying amounts of data. Specifically, to support short data bursts, the network should be able to operate in a mode where there is no need for a lengthy and high overhead signalling procedure before and after small amounts of data are sent. The system will, as a result, avoid both a negative impact to battery life for the UE and wasting signalling resources.
+
+For small form factor UEs it will be challenging to have more than 1 antenna due to the inability to get good isolation between multiple antennas. Thus, these UEs need to meet the expected performance in a 5G network with only one antenna.
+
+Cloud applications like cloud robotics perform computation in the network rather than in a UE, which requires the system to have high data rate in the uplink and very low round trip latency. Supposed that high density cloud robotics will be deployed in the future, the 5G system need to optimize the resource efficiency for such scenario.
+
+Additional resource efficiencies will contribute to meeting the various KPIs defined for 5G. Control plane resource efficiencies can be achieved by optimizing and minimizing signalling overhead, particularly for small data transmissions. Mechanisms for minimizing user plane resources utilization include in-network caching and application in a Service Hosting Environment closer to the end user. These optimization efforts contribute to achieving lower latency and higher reliability.
+
+Diverse mobility management related resource efficiencies are covered in clause 6.2.
+
+Security related resource efficiencies are covered in clause 8.8.
+
+### 6.4.2 Requirements
+
+#### 6.4.2.1 General
+
+The 5G system shall minimize control and user plane resource usage for data transfer from send only UEs.
+
+The 5G system shall minimize control and user plane resource usage for stationary UEs (e.g. lower signalling to user data resource usage ratio).
+
+The 5G system shall minimize control and user plane resource usage for transfer of infrequent small data units.
+
+The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of small data units.
+
+The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of continuous uplink data that requires both high data rate (e.g. 10 Mbit/s) and very low end-to-end latency (e.g. 1-10 ms).
+
+The 5G network shall optimize the resource use of the control plane and/or user plane to support high density connections (e.g. 1 million connections per square kilometre) taking into account, for example, the following criteria:
+
+- type of mobility support;
+- communication pattern (e.g. send-only, frequent or infrequent);
+- characteristics of payload (e.g. small or large size data payload);
+- characteristics of application (e.g. provisioning operation, normal data transfer);
+- UE location;
+- timing pattern of data transfer (e.g. real time or non-delay sensitive).
+
+The 5G system shall efficiently support service discovery mechanisms where UEs can discover, subject to access rights:
+
+- status of other UEs (e.g. sound on/off);
+- capabilities of other UEs (e.g. the UE is a relay UE) and/or;
+- services provided by other UEs (e.g. the UE is a colour printer).
+
+The 5G system shall be able to minimise the amount of wireless backhaul traffic (e.g. consolidating data transmissions to 1 larger rather than many smaller), when applicable (e.g. providing service in an area subject to power outages).
+
+The 5G system shall support small form factor UEs with single antenna.
+
+NOTE: Small form factor UEs are typically expected to have the diagonal less than 1/5 of the lowest supported frequency wave length.
+
+For a 5G system with satellite access, the following requirements apply:
+
+- The 5G system with satellite access shall support the use of satellite links between the radio access network and core network, by enhancing the 3GPP system to handle the latencies introduced by satellite backhaul.
+- A 5G system with satellite access shall be able to support meshed connectivity between satellites interconnected with intersatellite links.
+
+#### 6.4.2.2 Efficient bulk operations for IoT
+
+The 5G network shall optimize the resource use of the control plane and/or user plane to support bulk operation for high connection density (e.g. 1 million connections per square kilometre) of multiple UEs.
+
+The 5G system shall support a timely, efficient, and/or reliable mechanism to transmit the same information to multiple UEs.
+
+#### 6.4.2.3 Efficient management for IoT
+
+The 5G network shall optimize the resource use of the control plane and/or user plane to manage (e.g. provide service parameters, activate, deactivate) a UE.
+
+The 5G network shall be able to provide policies for background data transfer to a UE so that the 5G system can optimally use the control plane and/or user plane resources.
+
+#### 6.4.2.4 Efficient control plane
+
+The 5G system shall minimize the signalling that is required prior to user data transmission.
+
+NOTE: The amount of signalling overhead may vary based on the amount of data to be transmitted, even for the same UE.
+
+## 6.5 Efficient user plane
+
+### 6.5.1 Description
+
+5G is designed to meet diverse services with different and enhanced performances (e.g. high throughput, low latency and massive connections) and data traffic model (e.g. IP data traffic, non-IP data traffic, short data bursts and high throughput data transmissions).
+
+User plane should be more efficient for 5G to support differentiated requirements. On one hand, a Service Hosting Environment located inside of operator's network can offer Hosted Services closer to the end user to meet localization requirement like low latency, low bandwidth pressure. These Hosted Services contain applications provided by operators and/or trusted 3rd parties. On the other hand, user plane paths can be selected or changed to improve the user experience or reduce the bandwidth pressure, when a UE or application changes location during an active communication.
+
+The 5G network can also support multiple wireless backhaul connections (e.g. satellites and/or terrestrial), and efficiently route and/or bundle traffic among them.
+
+### 6.5.2 Requirements
+
+Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path between UEs attached to the same network, modifying the path as needed when the UE moves during an active communication.
+
+The 5G network shall enable a Service Hosting Environment provided by operator.
+
+Based on operator policy, the 5G network shall be able to support routing of data traffic between a UE attached to the network and an application in a Service Hosting Environment for specific services, modifying the path as needed when the UE moves during an active communication.
+
+Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path, modifying the path as needed when the UE moves or application changes location, between a UE in an active communication and:
+
+- an application in a Service Hosting Environment; or
+ - an application server located outside the operator's network; or
+ - an application server located in a customer premises network or personal IoT network.
+
+The 5G network shall maintain user experience (e.g. QoS, QoE) when a UE in an active communication moves from a location served by a Service Hosting Environment to:
+
+- another location served by a different Service Hosting Environment; or
+- another location served by an application server located outside the operator's network; or
+
+- another location served by an application server located in a customer premises network or personal IoT network, and vice versa.
+
+The 5G network shall maintain user experience (e.g. QoS, QoE) when an application for a UE moves as follows:
+
+- within a Service Hosting Environment; or
+- from a Service Hosting Environment to another Service Hosting Environment; or
+- from a Service Hosting Environment to an application server located place outside the operator's network; or
+- from a Service Hosting Environment to an application server located in a customer premises network or personal IoT network, and vice versa.
+
+The 5G network shall be able to interact with applications in a Service Hosting Environment for efficient network resource utilization and offloading data traffic to the Service Hosting Environment close to the UE's point of attachment to the access network.
+
+The 5G network shall support configurations of the Service Hosting Environment in the network (e.g. access network, core network), that provide application access close to the UE's point of attachment to the access network.
+
+The 5G system shall support mechanisms to enable a UE to access the closest Service Hosting Environment for a specific hosted application or service.
+
+The 5G network shall enable instantiation of applications for a UE in a Service Hosting Environment close to the UE's point of attachment to the access network.
+
+The 5G system shall be able to suspend or stop application instances in a Service Hosting Environment.
+
+NOTE: Not all applications will always be available in all Service Hosting Environments. Therefore, it may be needed to instantiate an application at a Service Hosting Environment nearby for serving a particular UE.
+
+Based on operator policy, the 5G system shall provide a mechanism such that one type of traffic (from a specific application or service) to/from a UE can be offloaded close to the UE's point of attachment to the access network, while not impacting other traffic type to/from that same UE.
+
+For a 5G system with satellite access, the following requirements apply:
+
+- A 5G system with satellite access shall be able to select the communication link providing the UE with the connectivity that most closely fulfils the agreed QoS
+- A 5G system with satellite access shall be capable of supporting simultaneous use of 5G satellite access network and 5G terrestrial access networks.
+- A 5G system with satellite access shall be able to support both UEs supporting only satellite access and UEs supporting simultaneous connectivity to 5G satellite access network and 5G terrestrial access network.
+
+The 5G System shall enable the discovery of a suitable Hosted Service.
+
+## 6.6 Efficient content delivery
+
+### 6.6.1 Description
+
+Video-based services (e.g. live streaming, VR) and personal data storage applications have been instrumental for the massive growth in mobile broadband traffic. Subject to service agreement between the operator and the content provider, the information of content and content itself can be aware by operator. In-network content caching provided by the operator, a third-party or both, can improve user experience, reduce backhaul resource usage and utilize radio resource efficiently.
+
+The operation of in-network caching includes flexible management of the location of the content cache within the network and efficient delivery of content to and from the appropriate content caching application. Examples of services are the delivery of popular video content from a content caching application via broadcast, and secure storage of a user's personal data or files using a distributed caching application. Such a service could also provide a student with a wireless
+
+backpack, where students can resume their work through the same or a different UE at any time, with very fast response times from the network.
+
+### 6.6.2 Requirements
+
+The 5G system shall enable efficient delivery of content from a content caching application under the control of the operator (e.g. a cache located close to the UE).
+
+The 5G system shall support a content caching application in a UE under the control of the operator.
+
+The 5G system shall support configurations of content caching applications in the network (e.g. access network, core network), that provide content close to the UE.
+
+Based on operator policy, the 5G system shall support an efficient mechanism for selection of a content caching application (e.g. minimize utilization of radio, backhaul resources and/or application resource) for delivery of the cached content to the UE.
+
+The 5G system shall support a mechanism for the operator to manage content distribution across content caching applications.
+
+The 5G system shall support delivery of cached content from a content caching application via the broadcast/multicast service.
+
+For a 5G system with satellite access, the following requirement applies.
+
+- A 5G system with satellite access shall be able to optimise the delivery of content from a content caching application by taking advantage of satellites in supporting ubiquitous service, as well as broadcasting/multicasting on very large to global coverages.
+
+## 6.7 Priority, QoS, and policy control
+
+### 6.7.1 Description
+
+The 5G network will support many commercial services (e.g. medical) and regional or national regulatory services (e.g. MPS, Emergency, Public Safety) with requirements for priority treatment. Some of these services share common QoS characteristics such as latency and packet loss rate but can have different priority requirements. For example, UAV control and air traffic control can have stringent latency and reliability requirements but not necessarily the same priority requirements. In addition, voice-based services for MPS and Emergency share common QoS characteristics as applicable for normal public voice communications yet can have different priority requirements. The 5G network will need to support mechanisms that enable the decoupling of the priority of a particular communication from the associated QoS characteristics such as latency and reliability to allow flexibility to support different priority services (that need to be configurable to meet operator needs, consistent with operator policies and corresponding national and regional regulatory policies).
+
+The network needs to support flexible means to make priority decisions based on the state of the network (e.g. during disaster events and network congestion) recognizing that the priority needs can change during a crisis. The priority of any service can be different for a user of that service based on operational needs and regional or national regulations. Therefore, the 5G system should allow a flexible means to prioritise and enforce prioritisation among the services (e.g. MPS, Emergency, medical, Public Safety) and among the users of these services. The traffic prioritisation can be enforced by adjusting resource utilization or pre-empting lower priority traffic.
+
+The network must offer means to provide the required QoS (e.g. reliability, latency, and bandwidth) for a service and the ability to prioritize resources when necessary to meet the service requirements. Existing QoS and policy frameworks handle latency and improve reliability by traffic engineering. In order to support 5G service requirements, it is necessary for the 5G network to offer QoS and policy control for reliable communication with latency required for a service and enable the resource adaptations as necessary.
+
+The network needs to allow multiple services to coexist, including multiple priority services (e.g. Emergency, MPS and MCS) and must provide means to prevent a single service from consuming or monopolizing all available network resources, or impacting the QoS (e.g. availability) of other services competing for resources on the same network under specific network conditions. For example, it is necessary to prevent certain services (e.g. citizen-to-authority
+
+Emergency) sessions from monopolizing all available resources during events such as disaster, emergency, and DDoS attacks from impacting the availability of other priority services such as MPS and MCS.
+
+Also, as 5G network is expected to operate in a heterogeneous environment with multiple access technologies, multiple types of UE, etc., it should support a harmonised QoS and policy framework that applies to multiple accesses.
+
+Further, for QoS control in EPS only covers RAN and core network, but for 5G network E2E QoS (e.g. RAN, backhaul, core network, network to network interconnect) is needed to achieve the 5G user experience (e.g. ultra-low latency, ultra-high bandwidth).
+
+### 6.7.2 Requirements
+
+The 5G system shall allow flexible mechanisms to establish and enforce priority policies among the different services (e.g. MPS, Emergency, medical, Public Safety) and users.
+
+NOTE 1: Priority between different services is subject to regional or national regulatory and operator policies.
+
+The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service.
+
+The 5G system shall enable the network operator to define and statically configure a maximum resource assignment for a specific service that can be adjusted based on the network state (e.g. during congestion, disaster, emergency and DDoS events) subject to regional or national regulatory and operator policies.
+
+The 5G system shall allow decoupling of the priority of a particular communication from the associated QoS characteristics such as end-to-end latency and reliability.
+
+The 5G system shall be able to support a harmonised QoS and policy framework applicable to multiple accesses.
+
+The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
+
+NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
+
+The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
+
+A 5G system with multiple access technologies shall be able to select the combination of access technologies to serve an UE on the basis of the targeted priority, pre-emption, QoS parameters and access technology availability.
+
+The 5G system shall support a mechanism to determine suitable QoS parameters for traffic over a satellite backhaul, based e.g. on the latency and bandwidth of the specific backhaul .
+
+NOTE 3: The case where a backhaul connection has dynamically changed latency and/or bandwidth needs to be considered.
+
+## 6.8 Dynamic policy control
+
+The 5G system shall support the creation and enforcement of prioritisation policy for users and traffic, during connection setup and when connected.
+
+NOTE: Prioritisation, pre-emption, and precedence of critical traffic associated with certain priority services (e.g. MPS and Emergency) are subject to regional/national regulatory and operator policies.
+
+The 5G system shall support optimised signalling for prioritised users and traffic where such signalling is prioritized over other signalling traffic.
+
+Based on operator policy, the 5G system shall allow flexible means for authorized entities to create and enforce priority among the different service flows.
+
+Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration.
+
+Based on operator policy, the 5G system shall maintain a session when prioritization of that session changes in real time, provided that the new priority is above the threshold for maintaining the session.
+
+## 6.9 Connectivity models
+
+### 6.9.1 Description
+
+The UE (remote UE) can connect to the network directly (direct network connection), connect using another UE as a relay UE (indirect network connection), or connect using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, Public Safety and others). In these cases, the use of relay UEs can be used to improve the energy efficiency and coverage of the system.
+
+Remote UEs can be anything from simple wearables, such as sensors embedded in clothing, to a more sophisticated wearable UE monitoring biometrics. They can also be non-wearable UEs that communicate in a Personal Area Network such as a set of home appliances (e.g. smart thermostat and entry key), or the electronic UEs in an office setting (e.g. smart printers), or a smart flower pot that can be remotely activated to water the plant.
+
+When a remote UE is attempting to establish an indirect network connection, there might be several relay UEs that are available in proximity and supporting selection procedures of an appropriate relay UE among the available relay UEs is needed.
+
+Indirect network connection covers the use of relay UEs for connecting a remote UE to the 3GPP network. There can be one or more relay UE(s) (more than one hop) between the network and the remote UE.
+
+### 6.9.2 Requirements
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.278 [5], clauses 7B and 7C.
+
+#### 6.9.2.1 General
+
+The 5G system shall support the relaying of traffic between a remote UE and a gNB using one or more relay UEs.
+
+The 5G system shall support different traffic flows of a remote UE to be relayed via different indirect network connection paths.
+
+The connection between a remote UE and a relay UE shall be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed band.
+
+The connection between a remote UE and a relay UE shall be able to use fixed broadband technology.
+
+The 5G system shall support indirect network connection mode in a VPLMN when a remote UE and a relay UE subscribe to different PLMNs and both PLMNs have a roaming agreement with the VPLMN.
+
+The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode.
+
+The network operator shall be able to define the maximum number of hops supported in their networks when using relay UEs.
+
+#### 6.9.2.2 Services and Service Continuity
+
+A 5G system shall be able to support all types of traffic e.g. voice, data, IoT small data, multimedia, MCX for indirect network connection mode.
+
+The 5G system shall be able to support QoS for a user traffic session between the remote UE and the network using 3GPP access technology.
+
+The 5G system shall be able to provide indication to a remote UE (alternatively, an authorized user) on the quality of currently available indirect network connection paths.
+
+The 5G system shall be able to maintain service continuity of indirect network connection for a remote UE when the communication path to the network changes (i.e. change of one or more of the relay UEs, change of the gNB).
+
+#### 6.9.2.3 Permission and Authorization
+
+The 5G system shall enable the network operator to authorize a UE to use indirect network connection. The authorization shall be able to be restricted to using only relay UEs belonging to the same network operator. The authorization shall be able to be restricted to only relay UEs belonging to the same application layer group.
+
+The 5G system shall enable the network operator to authorize a UE to relay traffic as relay UE. The authorization shall be able to allow relaying only for remote UEs belonging to the same network operator. The authorization shall be able to allow relaying only for remote UEs belonging to the same application layer group.
+
+The 5G system shall support a mechanism for an end user to provide/revoke permission to an authorized UE to act as a relay UE.
+
+The 5G system shall support a mechanism for an authorized third-party to provide/revoke permission to an authorized UE to act as a relay UE.
+
+The 5G system shall provide a suitable API by which an authorized third-party shall be able to authorize (multiple) UEs under control of the third-party to act as a relay UE or remote UE.
+
+The 5G system shall provide a suitable API by which an authorized third-party shall be able to enable/disable (multiple) UEs under control of the third-party to act as a relay UE or remote UE.
+
+#### 6.9.2.4 Relay UE Selection
+
+The 3GPP system shall support selection and reselection of relay UEs based on a combination of different criteria e.g.
+
+- the characteristics of the traffic that is intended to be relayed (e.g. expected message frequency and required QoS),
+- the subscriptions of relay UEs and remote UE,
+- the capabilities/capacity/coverage when using the relay UE,
+- the QoS that is achievable by selecting the relay UE1
+- the power consumption required by relay UE and remote UE2
+- the pre-paired relay UE3
+- the 3GPP or non-3GPP access the relay UE uses to connect to the network,
+- the 3GPP network the relay UE connects to (either directly or indirectly),
+- the overall optimization of the power consumption/performance of the 3GPP system, or
+- battery capabilities and battery lifetime of the relay UE and the remote UE.
+
+NOTE: Reselection may be triggered by any dynamic change in the selection criteria, e.g. by the battery of a relay UE getting depleted, a new relay capable UE getting in range, a remote UEs requesting additional resources or higher QoS, etc.
+
+#### 6.9.2.5 Satellite and Relay UEs
+
+For a 5G system with satellite access, the following requirements apply:
+
+- A 5G system with satellite access shall be able to support relay UE's with satellite access.
+
+NOTE: The connection between a relay UE and a remote UE is the same regardless of whether the relay UE is using satellite access or not.
+
+- A 5G system with satellite access shall support mobility management of relay UEs and the remote UEs connected to the relay UE between a 5G satellite access network and a 5G terrestrial network, and between 5G satellite access networks.
+- A 5G system with satellite access shall support joint roaming between different 5G networks of a relay UE and the remote UEs connected to that relay UE.
+
+## 6.10 Network capability exposure
+
+### 6.10.1 Description
+
+3GPP SEES and (e)FMSS features allow the operator to expose network capabilities e.g. QoS policy to third-party ISPs/ICPs. With the advent of 5G, new network capabilities need to be exposed to the third-party (e.g. to allow the third-party to customize a dedicated physical or virtual network or a dedicated network slice for diverse use cases; to allow the third-party to manage a trusted third-party application in a Service Hosting Environment to improve user experience, and efficiently utilize backhaul and application resources).
+
+### 6.10.2 Requirements
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.101 [6], clause 29.
+
+Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a UE to a network slice used for the third-party.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a service to a network slice used for the third-party.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to assign a UE to a network slice used for the third-party, to move a UE from one network slice used for the third-party to another network slice used for the third-party, and to remove a UE from a network slice used for the third-party based on subscription, UE capabilities, and services provided by the network slice.
+
+The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide the 3GPP network via encrypted connection with the expected communication behaviour of UE(s).
+
+NOTE 1: The expected communication behaviour is, for instance, the application servers a UE is allowed to communicate with, the time a UE is allowed to communicate, or the allowed geographic area of a UE.
+
+The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide via encrypted connection the 3GPP network with the actions expected from the 3GPP network when detecting behaviour that falls outside the expected communication behaviour.
+
+NOTE 2: Such actions can be, for instance, to terminate the UE's communication, to block the transferred data between the UE and the not allowed application.
+
+The 5G network shall be able to provide secure means for providing communication scheduling information (i.e. the time period the UE(s) will use a communication service) to an NPN via encrypted connection. This communication scheduling information is used by the 5G network to perform network energy saving and network resource optimization.
+
+The 5G network shall provide a mechanism to expose broadcasting capabilities to trusted third-party broadcasters' management systems.
+
+Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to manage this trusted third-party owned application(s) in the operator's Service Hosting Environment.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a third-party to monitor this trusted third-party owned application(s) in the operator's Service Hosting Environment.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to scale a network slice used for the third-party, i.e. to adapt its capacity.
+
+Based on operator policy, a 5G network shall provide suitable APIs to allow one type of traffic (from trusted third-party owned applications in the operator's Service Hosting Environment) to/from a UE to be offloaded to a Service Hosting Environment close to the UE's location.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
+
+Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party.
+
+Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party.
+
+Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party.
+
+The 5G system shall support the means for disengagement (tear down) of communication services by an authorized third-party.
+
+Based on operator policy, the 5G network shall expose a suitable API to provide the security logging information of UEs, for example, the active 3GPP security mechanisms (e.g. data privacy, authentication, integrity protection) to an authorized third-party.
+
+Based on operator policy, the 5G system shall provide suitable means to allow a trusted and authorized third-party to consult security related logging information for the network slices dedicated to that third-party.
+
+Based on operator policy, the 5G network shall be able to acknowledge within 100 ms a communication service request from an authorized third-party via a suitable API.
+
+The 5G network shall provide suitable APIs to allow a trusted third-party to monitor the status (e.g. locations, lifecycle, registration status) of its own UEs.
+
+NOTE 3: The number of UEs could be in the range from single digit to tens of thousands.
+
+The 5G network shall provide suitable APIs to allow a trusted third-party to get the network status information of a private slice dedicated for the third-party, e.g. the network communication status between the slice and a specific UE.
+
+The 5G system shall support APIs to allow the non-public network to be managed by the MNO's Operations System.
+
+The 5G system shall provide suitable APIs to allow third-party infrastructure (i.e. physical/virtual network entities at RAN/core level) to be used in a private slice.
+
+A 5G system shall provide suitable APIs to enable a third-party to manage its own non-public network and its private slice(s) in the PLMN in a combined manner.
+
+The 5G system shall support suitable APIs to allow an MNO to offer automatic configuration services (for instance, interference management) to non-public networks deployed by third parties and connected to the MNO's Operations System through standardized interfaces.
+
+The 5G system shall be able to:
+
+- provide a third-party with secure access to APIs (e.g. triggered by an application that is visible to the 5G system), by authenticating and authorizing both the third-party and the UE using the third-party's service.
+- provide a UE with secure access to APIs (e.g. triggered by an application that is not visible to the 5G system), by authenticating and authorizing the UE.
+- allow the UE to provide/revoke consent for information (e.g., location, presence) to be shared with the third-party.
+- preserve the confidentiality of the UE's external identity (e.g. MSISDN) against the third-party.
+- provide a third-party with information to identify networks and APIs on those networks.
+
+Based on operator policy, the 5G system shall provide means by which an MNO informs a third party of changes in UE subscription information. The 5G system shall also provide a means for an authorised third party to request this information at any time from the MNO.
+
+NOTE 4: Examples of UE subscription information include IP address, 5G LAN-VN membership, and configuration parameters for data network access.
+
+NOTE 5: These changes can have strong impacts in the stability of the third-party service.
+
+The 5G system shall provide a means by which an MNO can inform authorised 3rd parties of changes in the
+
+- RAT type that is serving a UE;
+- cell ID;
+- RAN quality of signal information;
+- assigned frequency band.
+
+This information listed above shall be provided with a suitable frequency via OAM and/or 5G core network.
+
+NOTE 6: The information aids the third party user to take proactive actions so that it can achieve high service availability in delivery of its services.
+
+## 6.11 Context-aware network
+
+### 6.11.1 Description
+
+A variety of sensors such as accelerometer, gyroscope, magnetometer, barometer, proximity sensor, and GPS can be integrated in a UE. Also, different applications running on the UE can have different communication needs (e.g. different traffic time). In addition, a UE can support different access technologies such as NR, E-UTRA, WLAN access technology, and fixed broadband access technology. The information gathered by sensors, the utilized access technologies, the application context, and the application traffic characteristics can provide useful information to the applications installed in the UE and can also help the 5G system utilize resources in an efficient and optimized way.
+
+### 6.11.2 Requirements
+
+The 5G system shall support network resource utilization efficiently and network optimization based on system information, including:- network conditions, such as network load and congestion information;
+
+- information on served UEs such as access information (e.g. 3GPP access, non-3GPP access), cell type (e.g. macro cell, small cell), user experienced data rate;
+- application's characteristics (e.g. expected traffic over time);
+- information on prioritized communication such as user subscription profile and priority level, priority services (e.g. MPS, Emergency, and Public Safety), application used for priority communications (e.g. voice, video, and data) and traffic associated with priority communications (signalling and media);
+- subject to user consent, enhanced traffic characteristic of UE (e.g. Mobility information (e.g. no mobility, nomadic, spatially restricted mobility, full mobility), location, sensor-level information (e.g. direction, speed, power status, display status, other sensor information installed in the UE), application-level information (e.g. foreground applications, running background application, and user settings).
+
+The 5G system shall support mechanisms to collect system information for network optimization within an operator configured time scale.
+
+## 6.12 Self backhaul
+
+### 6.12.1 Description
+
+The increased density of access nodes needed to meet future performance objectives poses considerable challenges in deployment and management (e.g. backhaul availability, backhaul capacity and scalability). The use of wireless backhaul for such access nodes helps to address some of the challenges.
+
+Wireless self-backhauling in the radio access network can enable simpler deployment and incremental rollout by reducing reliance on the availability of wired backhaul at each access node location. Network planning and installation efforts can be reduced by leveraging plug and play type features -- self-configuration, self-organizing, and self-optimization.
+
+### 6.12.2 Requirements
+
+The 5G network shall enable operators to support wireless self-backhaul using NR and E-UTRA.
+
+The 5G network shall support flexible and efficient wireless self-backhaul for both indoor and outdoor scenarios.
+
+The 5G network shall support flexible partitioning of radio resources between access and backhaul functions.
+
+The 5G network shall support autonomous configuration of access and wireless self-backhaul functions.
+
+The 5G network shall support multi-hop wireless self-backhauling.
+
+NOTE 1: This is to enable flexible extension of range and coverage area.
+
+The 5G network shall support autonomous adaptation on wireless self-backhaul network topologies to minimize service disruptions.
+
+The 5G network shall support topologically redundant connectivity on the wireless self-backhaul.
+
+NOTE 2: This is to enhance reliability and capacity and reduce end-to-end latency.
+
+## 6.13 Flexible broadcast/multicast service
+
+### 6.13.1 Description
+
+The proliferation of video services, ad-hoc multicast/broadcast streams, software delivery over wireless, group communications and broadcast/multicast IoT applications have created a need for a flexible and dynamic allocation of radio resources between unicast and multicast services within the network as well as support for a stand-alone deployment of multicast/broadcast network. Moreover, enabling such a service over a network for a wide range of inter-site distances between the radio base stations will enable a more efficient and effective delivery system for real-time and streaming multicast/broadcast content over wide geographic areas as well as in specific geographic areas spanning a limited number of base stations. A flexible multicast/broadcast service will allow the 5G system to efficiently deliver such services.
+
+### 6.13.2 Requirements
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.146 [7], TS 22.246 [8] and TS 22.101 [6], clause 32.
+
+The 5G system shall support operation of downlink only broadcast/multicast over a specific geographic area (e.g. a cell sector, a cell or a group of cells).
+
+The 5G system shall support operation of a downlink only broadcast/multicast system over a wide geographic area in a spectrally efficient manner for stationary and mobile UEs.
+
+The 5G system shall enable the operator to reserve 0% to 100% of radio resources of one or more radio carriers for the delivery of broadcast/multicast content.
+
+The 5G network shall allow the UE to receive content via a broadcast/multicast radio carrier while a concurrent data session is ongoing over another radio carrier.
+
+The 5G system shall be able to support broadcast/multicast of UHD streaming video (e.g. 4K/8K UHD).
+
+NOTE 1: Taking into account the bandwidth needs for different streaming video resolution.
+
+The 5G network shall allow the operator to configure and broadcast multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service in a stand-alone 3GPP based broadcast/multicast system.
+
+The 5G network shall support parallel transfer of multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service to the same UE taking into account e.g. UE capability, radio characteristics, application information.
+
+The 5G system shall support parallel transfer of multiple multicast/broadcast user services to a UE.
+
+The 5G system shall support a stand-alone multicast/broadcast network comprising of multiple cells with inter-site distances of up to 200 km.
+
+The 5G system shall support multicast/broadcast via a 5G satellite access network, or via a combination of a 5G satellite access network and other 5G access networks.
+
+The 5G system shall be able to setup or modify a broadcast/multicast service area within [1s].
+
+NOTE 2: For MCPTT related KPIs see 3GPP TS 22.179 [30], clause 6.15.
+
+The 5G system shall be able to apply QoS, priority and pre-emption to a broadcast/multicast service area.
+
+The 5G system shall support downlink parallel transfer of the same content, via broadcast/multicast and/or unicast, such that all receiver group members in a given area receive the media at the same time according to user perception.
+
+NOTE 3: In this context user perception refers to a difference in delay of typically less than 20 ms.
+
+The 5G system shall support a mechanism to inform a media source of relevant changes in conditions in the system (e.g. capacity, failures).
+
+The 5G system shall provide means for a media source to provide QoS requirement requests to the broadcast/multicast service.
+
+The 5G system shall provide means for the broadcast/multicast service to inform the media source of the available QoS, including modification of available QoS characteristics and availability of the broadcast/multicast service.
+
+The 5G system shall be able to support broadcast/multicast of voice, data and video group communication, allowing at least 800 concurrently operating groups per geographic area.
+
+NOTE 4: In this context "concurrently operating groups" means that the associated media streams are delivered concurrently.
+
+The 5G system shall support delivery of the same UE-originated data in a resource-efficient manner in terms of service bit rate to UEs distributed over a large geographical area.
+
+The 5G system shall allow a UE to request a communication service to simultaneously send data to different groups of UEs at the same time.
+
+The 5G system shall allow different QoS policy for each group the UE communicates with.
+
+## 6.14 Subscription aspects
+
+### 6.14.1 Description
+
+With the Internet of Things, it is expected that the diversity of IoT devices (e.g. sensors, UAVs, smart flower pots) and the usage models will largely vary. Moreover, when the IoT device is manufactured, the deployment location and specific usage might not be known. Sometimes the IoT devices will be added to existing subscriptions, other times they can be part of a new subscription for the user. Sometimes the IoT devices can be leased. During their life cycle these
+
+IoT devices go through different stages, involving the change in ownership when the IoT device is deployed and possibly afterwards, the activation of the IoT device by the preferred operator, a possible change of operators, etc. These stages need to be managed securely and efficiently. A method of dynamic subscription generation and management is needed in addition to statically provisioned subscription. Once the subscription is established, subscription management becomes necessary, for example, to modify the subscription when the ownership of the IoT device changes, to update or refresh credentials due to suspected leakage or theft of security keys or as a preventive measure.
+
+The Internet of Things will also support various connectivity models: The IoT devices can connect with the network directly or connect with the network using another IoT device as a relay UE, or they can be capable of using both types of connections. The direct device connection between the IoT device and the relay UE can be using 3GPP or non-3GPP RAT. The relay UE can access the network also using 3GPP or non-3GPP access networks (e.g. WLAN, fixed broadband access network). In order to identify and manage the IoT devices, a subscription with the 5G network is needed, even if the access is done via non-3GPP access.
+
+### 6.14.2 Requirements
+
+An IoT device which is able to access a 5G PLMN in direct network connection mode using a 3GPP RAT shall have a 3GPP subscription.
+
+The 5G system shall allow the operator to identify a UE as an IoT device based on UE characteristics (e.g. identified by an equipment identifier or a range of equipment identifiers) or subscription or the combination of both.
+
+The 5G system shall be able to provide mechanisms to change the association between a subscription and address/number of an IoT device (e.g. changing the owner and subscription information associated with the IoT device) within the same operator and in between different operators in an automated or manual way.
+
+The 5G system shall be able to support identification of subscriptions independently of identification of IoT devices. Both identities shall be secure.
+
+An IoT device which is able to connect to a UE in direct device connection mode shall have a 3GPP subscription, if the IoT device needs to be identifiable by the core network (e.g. for IoT device management purposes or to use indirect network connection mode).
+
+Based on operator policy, the 5G system shall support a mechanism to provision on-demand connectivity (e.g. IP connectivity for remote provisioning). This on-demand mechanism should enable means for a user to request on-the-spot network connectivity while providing operators with identification and security tools for the provided connectivity.
+
+The 5G system shall support a secure mechanism for a home operator to remotely provision the 3GPP credentials of a uniquely identifiable and verifiably secure IoT device.
+
+The 5G system shall support a secure mechanism for the network operator of an NPN to remotely provision the non-3GPP identities and credentials of a uniquely identifiable and verifiably secure IoT device.
+
+Based on MNO and NPN policy, the 5G system shall support a mechanism to enable MNO to update the subscription of an authorized UE in order to allow the UE to connect to a desired NPN. This on-demand mechanism should enable means for a user to request on-the-spot network connectivity which is authorized by its MNO.
+
+Based on operator policy, the 5G system shall provide means for authorised 3rd parties to request changes to UE subscription parameters for access to data networks, e.g., static IP address and configuration parameters for data network access.
+
+## 6.15 Energy efficiency
+
+### 6.15.1 Description
+
+Energy efficiency is a critical issue in 5G. The potential to deploy systems in areas without a reliable energy source requires new methods of managing energy consumption not only in the UEs but throughout all components of the 5G system.
+
+Small form factor UEs also typically have a small battery and this not only puts constraints on general power optimization but also on how the energy is consumed. With smaller batteries it is more important to understand and follow the limitations for both the maximum peak and continuous current drain.
+
+### 6.15.2 Requirements
+
+The 5G access network shall support an energy saving mode with the following characteristics:
+
+- the energy saving mode can be activated/deactivated either manually or automatically;
+- service can be restricted to a group of users (e.g. public safety user, emergency callers).
+
+NOTE: When in energy saving mode the UE's and Access transmit power may be reduced or turned off (deep sleep mode), end-to-end latency and jitter may be increased with no impact on set of users or applications still allowed.
+
+The 5G system shall support mechanisms to improve battery life for a UE over what is possible in EPS.
+
+The 5G system shall optimize the battery consumption of a relay UE via which a UE is in indirect network connection mode.
+
+The 5G system shall support UEs using small rechargeable and single coin cell batteries (e.g. considering impact on maximum pulse and continuous current).
+
+## 6.16 Markets requiring minimal service levels
+
+### 6.16.1 Description
+
+A key aspect of 5G system flexibility is the ability to support both the very high-end markets as well as very low end markets. Some systems will be deployed in areas where there are constraints on energy resources (e.g. sporadic access to power) and lower end user expectations for availability, reliability, and data rates. In such cases, the system needs additional flexibility to adapt power consumption needs based on fluctuations in power availability. The system should be efficient in order to provide essential services in harsh environments (e.g. far remote rural areas, very large territories) while taking into account the local constraints (adapting resources consumptions to long distances, dealing with variable conditions and possibly disconnections). Content delivery should be optimized in order to reduce constraints on transport networks, on low-end UEs (e.g. small screen, limited energy consumption), variable network conditions, and client profiles.
+
+### 6.16.2 Requirements
+
+In constrained circumstances (e.g. reduced power supply), the 5G system shall be able to support a minimal user experience (e.g. user experienced data rate of [100] kbit/s, E2E latency of 50 ms, lower availability of the network of 95%).
+
+The 5G system shall support centralized automation and management of the network in order to reduce local management tasks.
+
+The 5G system shall support a mechanism to reduce data transfer rate at the cell edge for very large coverage area (e.g. 100 kbit/s for more than 100 km cell coverage, 1 Mbit/s for 100 km cell coverage).
+
+The 5G system shall be able to give priority to services (e.g. e-Health) when resources are limited.
+
+## 6.17 Extreme long range coverage in low density areas
+
+### 6.17.1 Description
+
+A fully connected society is expected in the near future. The network access everywhere over long distances (e.g. at remote rural areas or at sea) including both humans and machines need to be supported.
+
+### 6.17.2 Requirements
+
+The 5G system shall support the extreme long-range coverage (up to 100 km) in low density areas (up to 2 user/km2).
+
+The 5G system shall support a minimum user throughput of 1 Mbit/s on DL and 100 kbit/s on UL at the edge of coverage.
+
+The 5G system shall support a minimum cell throughput capacity of 10 Mbit/s/cell on DL (based on an assumption of 1 GB/month/sub).
+
+The 5G system shall support a maximum of [400] ms E2E latency for voice services at the edge of coverage.
+
+## 6.18 Multi-network connectivity and service delivery across operators
+
+### 6.18.1 Description
+
+Given the multitude of use cases for new verticals and services, each operator, based on its business model, can deploy a network serving only a subset of the vertical industries and services. However, this should not prevent an end-user from accessing all new services and capabilities that will be accessible via 5G systems. To provide a better user experience for their subscribers with UEs capable of simultaneous network access, network operators could contemplate a variety of sharing business models and partnership with other network and service providers to enable its subscribers to access all services via multiple networks simultaneously, and with minimum interruption when moving.
+
+### 6.18.2 Requirements
+
+The 5G system shall enable users to obtain services from more than one network simultaneously on an on-demand basis.
+
+For a user with a single operator subscription, the use of multiple serving networks operated by different operators shall be under the control of the home operator.
+
+When a service is offered by multiple operators, the 5G system shall be able to maintain service continuity with minimum service interruption when the serving network is changed to a different serving network operated by a different operator.
+
+NOTE 1: A business agreement is required between the network operators.
+
+In the event of the same service being offered by multiple operators, unless directed by the home operator's network, the UE shall be prioritized to receive subscribed services from the home operator's network.
+
+NOTE 2: If the service is unavailable (e.g. due to lack of network coverage) from the home operator's network, the UE may be able to receive the service from another operator's network.
+
+NOTE 3: QoS provided by the partner operator's network for the same service will be based on the agreement between the two operators and could be different than that provided by the home operator's network.
+
+## 6.19 3GPP access network selection
+
+### 6.19.1 Description
+
+The 5G system will support the concept of "network slices" where different NG-RANs potentially are connected to network slices of different SSTs. A 5G UE can provide assistance information (e.g. SST) to enable the network to select one or more network slices. A 5G system is foreseen to support one or more SSTs, but possibly not all existing SSTs.
+
+A 5G network operator controls and is responsible for what SSTs that should be available to a specific UE and subscription combination, based on associated subscription type, network operator policies, network capabilities and UE capabilities. The network operator can populate the Operator Controlled PLMN Selector list with associated access
+
+technology identifiers, stored in the 5G UE, with the PLMN/RAT combinations enabling access to the SSTs that are available to the 5G UE with associated subscription.
+
+The UE uses the list of PLMN/RAT combinations for PLMN selection, if available, typically during roaming situations. In non-roaming situations, the UE and subscription combination typically matches the HPLMN/EHPLMN capabilities and policies, from a SST perspective. That is, a 5G UE accessing its HPLMN/EHPLMN should be able to access SSTs according to UE capabilities and the related subscription.
+
+Optionally, a 5G system supports, subject to operator policies, a User Controlled PLMN Selector list that enables the 5G UE user to specify preferred PLMNs with associated access technology identifier in priority order. The user can obtain information about suitable PLMN/RAT combination that would support services preferred by the user.
+
+### 6.19.2 Requirements
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.011 [3], clause 3.2.
+
+The 5G system shall support selection among any available PLMN/RAT combinations, identified through their respective PLMN identifier and Radio Access Technology identifier, in a prioritised order. The priority order may, subject to operator policies, be provisioned in an Operator Controlled PLMN Selector lists with associated RAT identifiers, stored in the 5G UE.
+
+The 5G system shall support, subject to operator policies, a User Controlled PLMN Selector list stored in the 5G UE, allowing the UE user to specify preferred PLMNs with associated RAT identifier in priority order.
+
+## 6.20 eV2X aspects
+
+### 6.20.1 Description
+
+The 3GPP system is expected to support various enhanced V2X scenarios.
+
+Vehicles Platooning enables the vehicles to dynamically form a group travelling together. All the vehicles in the platoon receive periodic data from the leading vehicle, in order to carry on platoon operations. This information allows the distance between vehicles to become extremely small, i.e. the gap distance translated to time can be very low (sub second). Platooning applications can allow the vehicles following to be autonomously driven.
+
+Advanced Driving enables semi-automated or fully-automated driving. Longer inter-vehicle distance is assumed. Each vehicle and/or RSU shares data obtained from its local sensors with vehicles in proximity, thus allowing vehicles to coordinate their trajectories or manoeuvres. In addition, each vehicle shares its driving intention with vehicles in proximity. The benefits of this use case group are safer traveling, collision avoidance, and improved traffic efficiency.
+
+Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video data among vehicles, Road Side Units, UEs of pedestrians and V2X application servers. The vehicles can enhance the perception of their environment beyond what their own sensors can detect and have a more holistic view of the local situation.
+
+Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves or a remote vehicle located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. In addition, access to cloud-based back-end service platform can be considered for this use case group.
+
+### 6.20.2 Requirements
+
+The 3GPP system supports the transport of messages with different performance requirements to support V2X scenarios. The associated requirements are described in eV2X 3GPP TS 22.186 [9].
+
+## 6.21 NG-RAN Sharing
+
+### 6.21.1 Description
+
+The increased density of access nodes needed to meet future performance objectives poses considerable challenges in deployment and acquiring spectrum and antenna locations. RAN sharing is seen as a technical solution to these issues.
+
+### 6.21.2 Requirements
+
+Requirements related to NG-RAN sharing are described in 3GPP TS 22.101 [6], clause 28.2.
+
+A 5G satellite access network shall support NG-RAN sharing.
+
+## 6.22 Unified access control
+
+### 6.22.1 Description
+
+Depending on operator's policies, deployment scenarios, subscriber profiles, and available services, different criterion will be used in determining which access attempt should be allowed or blocked when congestion occurs in the 5G System. These different criteria for access control are associated with Access Identities and Access Categories. The 5G system will provide a single unified access control where operators control accesses based on these two.
+
+In unified access control, each access attempt is categorized into one or more of the Access Identities and one of the Access Categories. Based on the access control information applicable for the corresponding Access Identity and Access Category of the access attempt, the UE performs a test whether the actual access attempt can be made or not.
+
+The unified access control supports extensibility to allow inclusion of additional standardized Access Identities and Access Categories and supports flexibility to allow operators to define operator-defined Access Categories using their own criterion (e.g. network slicing, application, and application server).
+
+NOTE: Clauses 4.1 through 4.4a of TS 22.011 are obsolete and replaced by clause 6.22.2 of this specification. However, when a UE is configured for EAB according to TS 22.011, the UE is also configured for delay tolerant service for 5G system.
+
+### 6.22.2 Requirements
+
+#### 6.22.2.1 General
+
+Based on operator policy, the 5G system shall be able to prevent UEs from accessing the network using relevant barring parameters that vary depending on Access Identity and Access Category. Access Identities are configured at the UE as listed in Table 6.22.2.2-1. Access Categories are defined by the combination of conditions related to UE and the type of access attempt as listed in Table 6.22.2.3-1. One or more Access Identities and only one Access Category are selected and tested for an access attempt.
+
+The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in one or more areas of the RAN.
+
+The UE shall be able to determine whether or not a particular new access attempt is allowed based on barring parameters that the UE receives from the broadcast barring control information and the configuration in the UE.
+
+In the case of multiple core networks sharing the same RAN, the RAN shall be able to apply access control for the different core networks individually.
+
+The unified access control framework shall be applicable both to UEs accessing the 5G CN using E-UTRA and to UEs accessing the 5G CN using NR.
+
+The unified access control framework shall be applicable to UEs in RRC Idle, RRC Inactive, and RRC Connected at the time of initiating a new access attempt (e.g. new session request).
+
+NOTE 1: "new session request" in RRC Connected refers to events, e.g. new MMTEL voice or video session, sending of SMS (SMS over IP, or SMS over NAS), sending of IMS registration related signalling, new PDU session establishment, existing PDU session modification, and service request to re-establish the user plane for an existing PDU session.
+
+The 5G system shall support means by which the operator can define operator-defined Access Categories to be mutually exclusive.
+
+NOTE 2: Examples of criterion of operator-defined Access Categories are network slicing, application, and application server.
+
+The unified access control framework shall be applicable to inbound roamers to a PLMN.
+
+The serving PLMN should be able to provide the definition of operator-defined Access Categories to the UE.
+
+#### 6.22.2.2 Access identities
+
+**Table 6.22.2.2-1: Access Identities**
+
+| Access Identity number | UE configuration |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|
+| 0 | UE is not configured with any parameters from this table |
+| 1 (NOTE 1) | UE is configured for Multimedia Priority Service (MPS). |
+| 2 (NOTE 2) | UE is configured for Mission Critical Service (MCS). |
+| 3 | UE for which Disaster Condition applies (note 4) |
+| 4-10 | Reserved for future use |
+| 11 (NOTE 3) | Access Class 11 is configured in the UE. |
+| 12 (NOTE 3) | Access Class 12 is configured in the UE. |
+| 13 (NOTE 3) | Access Class 13 is configured in the UE. |
+| 14 (NOTE 3) | Access Class 14 is configured in the UE. |
+| 15 (NOTE 3) | Access Class 15 is configured in the UE. |
+| NOTE 1: Access Identity 1 is used by UEs configured for MPS, in the PLMNs where the configuration is valid. The PLMNs where the configuration is valid are HPLMN, PLMNs equivalent to HPLMN, and visited PLMNs of the home country.
Access Identity 1 is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country. | |
+| NOTE 2: Access Identity 2 is used by UEs configured for MCS, in the PLMNs where the configuration is valid. The PLMNs where the configuration is valid are HPLMN or PLMNs equivalent to HPLMN and visited PLMNs of the home country. Access Identity 2 is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country. | |
+| NOTE 3: Access Identities 11 and 15 are valid in Home PLMN only if the EHPLMN list is not present or in any EHPLMN. Access Identities 12, 13 and 14 are valid in Home PLMN and visited PLMNs of home country only. For this purpose, the home country is defined as the country of the MCC part of the IMSI. | |
+| NOTE 4: The configuration is valid for PLMNs that indicate to potential Disaster Inbound Roamers that the UEs can access the PLMN. See clause 6.31. | |
+
+Any number of these Access Identities may be barred at any one time.
+
+#### 6.22.2.3 Access categories
+
+**Table 6.22.2.3-1: Access Categories**
+
+| Access Category number | Conditions related to UE | Type of access attempt |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| 0 | All | MO signalling resulting from paging |
+| 1 (NOTE 1) | UE is configured for delay tolerant service and subject to access control for Access Category 1, which is judged based on relation of UE's HPLMN and the selected PLMN. | All except for Emergency, or MO exception data |
+| 2 | All | Emergency |
+| 3 | All except for the conditions in Access Category 1. | MO signalling on NAS level resulting from other than paging |
+| 4 | All except for the conditions in Access Category 1. | MMTEL voice (NOTE 3) |
+| 5 | All except for the conditions in Access Category 1. | MMTEL video |
+| 6 | All except for the conditions in Access Category 1. | SMS |
+| 7 | All except for the conditions in Access Category 1. | MO data that do not belong to any other Access Categories (NOTE 4) |
+| 8 | All except for the conditions in Access Category 1 | MO signalling on RRC level resulting from other than paging |
+| 9 | All except for the conditions in Access Category 1 | MO IMS registration related signalling (NOTE 5) |
+| 10 (NOTE 6) | All | MO exception data |
+| 11-31 | | Reserved standardized Access Categories |
+| 32-63 (NOTE 2) | All | Based on operator classification |
+
+NOTE 1: The barring parameter for Access Category 1 is accompanied with information that define whether Access Category applies to UEs within one of the following categories:
+a) UEs that are configured for delay tolerant service;
+b) UEs that are configured for delay tolerant service and are neither in their HPLMN nor in a PLMN that is equivalent to it;
+c) UEs that are configured for delay tolerant service and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN.
+When a UE is configured for EAB, the UE is also configured for delay tolerant service. In case a UE is configured both for EAB and for EAB override, when upper layer indicates to override Access Category 1, then Access Category 1 is not applicable.
+
+NOTE 2: When there are an Access Category based on operator classification and a standardized Access Category to both of which an access attempt can be categorized, and the standardized Access Category is neither 0 nor 2, the UE applies the Access Category based on operator classification. When there are an Access Category based on operator classification and a standardized Access Category to both of which an access attempt can be categorized, and the standardized Access Category is 0 or 2, the UE applies the standardized Access Category.
+
+NOTE 3: Includes Real-Time Text (RTT).
+
+NOTE 4: Includes IMS Messaging.
+
+NOTE 5: Includes IMS registration related signalling, e.g. IMS initial registration, re-registration, and subscription refresh.
+
+NOTE 6: Applies to access of a NB-IoT-capable UE to a NB-IOT cell connected to 5GC when the UE is authorized to send exception data.
+
+Access Category 0 in Table 6.22.2.3-1 shall not be barred, irrespective of Access Identities.
+
+NOTE: The network can control the amount of access attempts relating to Access Category 0 by controlling whether to send paging or not.
+
+## 6.23 QoS monitoring
+
+### 6.23.1 Description
+
+The QoS requirements specified for particular services such as URLLC services, vertical automation communication services, and V2X, mandate QoS guarantees from the network. However, the network cannot always guarantee the required QoS of the service. An example reason for this shortcoming is that the latency and/or packet error rate increase due to interference in a radio cell. In such cases, it is critical that the application and/or application server is notified in a
+
+timely manner. Hence, the 5G system should be able to support QoS monitoring/assurance for URLLC services, V2X and vertical automation.
+
+For more information on QoS assurance see Annex F.
+
+Vertical automation systems are locally distributed and are typically served by wired and wireless communication networks of different types and with different characteristics. If the operation of the system or one of its sub-processes does not work properly, there is a need for quickly finding and eliminating the related error or fault in order to avoid significant operation and thus financial losses. To that end, automation devices and applications implement diagnosis and error-analysis algorithms, as well as predictive maintenance features.
+
+Due to their inherent challenges, wireless communication systems are usually under suspicion in case an error occurs in a distributed automation application. Therefore, diagnosis and fault analysis features for 5G systems are required. The 5G system needs to provide sufficient monitoring information as input for such diagnosis features.
+
+QoS monitoring can be used for the following activities:
+
+- assessing and assuring the dependability of network operation;
+- assessing and assuring the dependability of the communication services;
+- excluding particular communication errors;
+- identifying communication errors;
+- analysing the location of an error including the geographic location of the involved network component (UE; front-haul component; core node);
+- activation of application-related countermeasures.
+
+This section provides requirements for both functionality and service exposure. In addition, the service exposure requirements on QoS monitoring in 22.101 [6], clause 29.2 apply.
+
+### 6.23.2 Requirements
+
+The 5G system shall provide a mechanism for supporting real-time E2E QoS monitoring within a system.
+
+NOTE 1: The end points in E2E are the termination points of the communication service within the boundary of the 5G system.
+
+The 5G system shall support combined QoS monitoring for a group of UEs.
+
+NOTE 1A: Combined monitoring stands for the monitoring of several UEs for which the monitoring results are reported together. An example for combined QoS monitoring is that the 5G networks monitors the service bit rates of all connections associated with the group of UEs.
+
+The 5G network shall provide an interface to an application for QoS monitoring (e.g. to initiate QoS monitoring, request QoS parameters, events, logging information).
+
+The 5G system shall be able to provide real time QoS parameters and events information to an authorized application/network entity.
+
+NOTE 2: The QoS parameters to be monitored and reported can include latency (e.g. UL/DL or round trip), jitter, and packet loss rate.
+
+The 5G system shall be able to log the history of the communication events.
+
+NOTE 3: The communication history may include timestamps of communication events and position-related information. Examples of such information are the positions of UEs and of radio base stations associated with communication events. Communication events include instances when the required QoS is not met.
+
+The 5G system shall support different levels of granularity for QoS monitoring (e.g. per flow or set of flows).
+
+The 5G system shall be able to provide event notification upon detecting an error that the negotiated QoS level cannot be met/guaranteed.
+
+The 5G system shall be able to provide information that identifies the type and the location of a communication error (e.g. cell ID).
+
+The 5G system shall be able to provide notification of communication events to authorized entities per pre-defined patterns.
+
+NOTE 4: An example for a communication event is that the service bit rate drops below a pre-defined threshold for QoS parameters. When such an event occurs, the authorized entity is notified, and the event is logged.
+
+The 5G system shall support event-based QoS monitoring.
+
+NOTE 5: An example for a triggering event is a position change of the pertinent UE. A position change can, for instance, be inferred from a 5G position service that tracks the UE.
+
+The 5G system shall be able to respond to a request from an authorized entity to provide real-time QoS monitoring information within a specified time after receiving the request (e.g., within 5 s).
+
+NOTE 6: The response time can be specified by the user.
+
+The 5G system shall support an update/refresh rate for real time QoS monitoring with a specified value (e.g., at least one update per second).
+
+The 5G system shall be able to provide statistical information of service parameters and error types while a communication service is in operation.
+
+NOTE 7: The time span for collection and evaluation of statistical values can be specified by the user.
+
+The 5G system shall provide information on the current availability of a specific communication service in a particular area (e.g. cell ID) upon request of an authorized entity.
+
+The 5G system shall provide a means by which an MNO informs a third party of network events (failure of network infrastructure affecting UEs in a particular area, etc.).
+
+Based on MNO policy, the 5G system shall provide a mechanism to automatically report service degradations, communications loss, and sustained connection loss in a specific geographic area (e.g., a cell sector, a cell or a group of cells) to a third party.
+
+NOTE 8: These reports use a standard format. The specific values, thresholds, and conditions upon which alarms occur can include the measured values for end-to-end latency, service bit rate, communication service availability, end-to-end latency jitter, etc. for a UE, the UE's location, and the time(s) during which the degradation occurred.
+
+The 5G system shall provide a mechanism for an authorised third party to report to an MNO service degradations, communication loss, and sustained connection loss.
+
+NOTE 9: These reports use a standard format. The specific values, thresholds, and conditions upon which alarms occur can include the measured values for end-to-end latency, service bit rate, communication service availability, end-to-end latency jitter, etc. for a UE, the UE's location, and the time(s) during which the degradation occurred.
+
+NOTE 10: What the MNO does with such reports is out of scope of 3GPP.
+
+## 6.24 Ethernet transport services
+
+### 6.24.1 Description
+
+This clause includes common, fundamental Ethernet transport requirements, and any requirements necessary to support a 5G LAN-type service. The requirements applicable to the 5G system for supporting cyber-physical applications using Ethernet are described in 3GPP TS 22.104 [21].
+
+### 6.24.2 Requirements
+
+The 3GPP system shall be able to support an Ethernet transport service.
+
+The 5G network shall support the routing of non-IP packet (e.g. Ethernet frame) efficiently for private communication between UEs within a 5G LAN-type service.
+
+The 5G network shall be able to provide the required QoS (e.g. reliability, latency, and bandwidth) for non-IP packet (e.g. Ethernet frame) for private communication between UEs within a 5G LAN-type service.
+
+The Ethernet transport service shall support routing based on information extracted from Virtual LAN (VLAN) ID by the 3GPP system.
+
+The Ethernet transport service shall support the transport of Ethernet frames between UEs that Ethernet devices are connected to.
+
+The Ethernet transport service shall support the transport of Ethernet frames between a UE that an Ethernet device is connected to and an Ethernet network in DN (Data Network).
+
+NOTE: If more than one Ethernet devices need to be connected to a UE, they can be connected using an Ethernet switch between the devices and the UE.
+
+The Ethernet transport service shall support the transport of Ethernet broadcast frames.
+
+The Ethernet transport service shall support traffic filtering and prioritization based on source and destination MAC addresses.
+
+The Ethernet transport service shall support traffic filtering and prioritization based on Ethertype (including multiple Ethertypes in double tagging).
+
+The Ethernet transport service shall support traffic filtering and prioritization based on 802.1Q VLAN tags (including double tagging).
+
+The Ethernet transport service shall support routing based on information extracted by the 3GPP system from the Bridge Protocol Data Units created in the Ethernet network based on a Spanning Tree Protocol (e.g. RSTP).
+
+## 6.25 Non-public networks
+
+### 6.25.1 Description
+
+Non-public networks are intended for the sole use of a private entity such as an enterprise, and can be deployed in a variety of configurations, utilising both virtual and physical elements. Specifically, they can be deployed as completely standalone networks, they can be hosted by a PLMN, or they can be offered as a slice of a PLMN.
+
+In any of these deployment options, it is expected that unauthorized UEs, those that are not associated with the enterprise, will not attempt to access the non-public network, which could result in resources being used to reject that UE and thereby not be available for the UEs of the enterprise. It is also expected that UEs of the enterprise will not attempt to access a network they are not authorized to access. For example, some enterprise UEs can be restricted to only access the non-public network of the enterprise, even if PLMN coverage is available in the same geographic area. Other enterprise UEs can access both a non-public network and a PLMN where specifically allowed.
+
+In addition to the requirements in this section, all requirements and KPIs in other sections of TS 22.261, that are not exclusively for PLMNs (i.e. explicitly using the term PLMN) also apply to (i.e. are in scope of) non-public networks, except the requirements in sections 5.1, 6.2.4 and 6.3.2.2. However, hereby it is important to realize that requirements and features are optional to be supported by a non-public network, since non-public network deployments can include different subsets of 5G system requirements and services described in the sections of TS 22.261. The deployment choices are dependent on verticals needs and regulation.
+
+### 6.25.2 Requirements
+
+The 5G system shall support non-public networks.
+
+The 5G system shall support non-public networks that provide coverage within a specific geographic area.
+
+The 5G system shall support both physical and virtual non-public networks.
+
+The 5G system shall support standalone operation of a non-public network, i.e. a non-public network may be able to operate without dependency on a PLMN.
+
+Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall support for non-public network subscribers:
+
+- access to subscribed PLMN services via the non-public network;
+- seamless service continuity for subscribed PLMN services between a non-public network and a PLMN;
+- access to selected non-public network services via a PLMN;
+- seamless service continuity for non-public network services between a non-public network and a PLMN.
+
+Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall enable a UE, with multiple subscriptions, to simultaneously access multiple non-public networks and corresponding services, via those NPNs or via a different network (PLMN or NPN).
+
+Subject to regional or national regulatory requirements for emergency services, 5G system shall be able to support IMS emergency services for non-public networks.
+
+A non-public network subscriber to access a PLMN service shall have a service subscription using 3GPP identifiers and credentials provided or accepted by a PLMN.
+
+The 5G system shall support a mechanism for a UE to identify and select a non-public network.
+
+NOTE: Different network selection mechanisms may be used for physical vs virtual non-public networks.
+
+The 5G system shall support identifiers for a large number of non-public networks to minimize collision likelihood between assigned identifiers.
+
+The 5G system shall support a mechanism to prevent a UE with a subscription to a non-public network from automatically selecting and attaching to a PLMN or non-public network it is not authorized to select.
+
+The 5G system shall support a mechanism to prevent a UE with a subscription to a PLMN from automatically selecting and attaching to a non-public network it is not authorized to select.
+
+The 5G system shall support a mechanism for a PLMN to control whether a user of a UE can manually select a non-public network hosted by this PLMN that the UE is not authorized to select automatically.
+
+The 5G system may broadcast a human readable network name that a UE may display for manual selection of a non-public network.
+
+The 5G system shall support a change of host of a non-public network from one PLMN to another PLMN without changing the network selection information stored in the UEs of the non-public network.
+
+The 5G system shall enable an NPN to support multiple third-party service providers.
+
+In the event of a loss of communication between RAN and core network, the 5G system shall be able to provide capability to securely re-connect an NPN network function within a short period of time ( $< 1\text{s}$ ).
+
+## 6.26 5G LAN-type service
+
+### 6.26.1 Description
+
+5G expands the scope and reach of 3GPP-defined technologies. There are multiple market segments in the realm of residential, office, enterprise and factory, where 5G will need to provide services with similar functionalities to Local Area Networks (LANs) and VPN's but improved with 5G capabilities (e.g. high performance, long distance access, mobility and security).
+
+### 6.26.2 Requirements
+
+#### 6.26.2.1 General
+
+The 5G system shall support 5G LAN-type service in a shared RAN configuration.
+
+The 5G system shall support 5G LAN-type service over a wide area mobile network.
+
+The 5G network shall support service continuity for 5G LAN-type service, i.e. the private communication between UEs shall not be interrupted when one or more UEs of the private communication move within the same network that provides the 5G LAN-type service.
+
+The 5G system shall support use of unlicensed as well as licensed spectrum for 5G LAN-type services.
+
+The 5G system shall enable the network operator to provide the same 5G LAN-type service to any 5G UE, regardless of whether it is connected via public base stations, indoor small base stations connected via fixed access, or via relay UEs connected to either of these two types of base stations.
+
+#### 6.26.2.2 5G LAN-virtual network (5G LAN-VN)
+
+A UE shall be able to select a 5G LAN-VN, that the UE is a member of, for private communication.
+
+A 5G system shall support 5G LAN-VNs with member UEs numbering between a few to tens of thousands.
+
+The 5G system shall be able to support large numbers of small 5G LAN-VNs.
+
+NOTE: Targeting residential deployments translate into millions of 5GLAN-VN per operator per country. These residential 5G LAN-VNs typically contain between 10-50 devices.
+
+The 5G LAN-VN shall support member UEs that are subscribed to different PLMNs, e.g. a 5G LAN-VN may span multiple countries and have member UEs that have a subscription to a PLMN in their home country.
+
+The 5G system shall support on-demand establishment of UE to UE, multicast, and broadcast private communication between members UEs of the same 5G LAN-VN. Multiple types of data communication shall be supported, at least IP and Ethernet.
+
+The 5G network shall ensure that only member UEs of the same 5G LAN-VN are able to establish or maintain private communications among each other using 5G LAN-type service.
+
+The 5G system shall allow member UEs of a 5G LAN-VN to join an authorized multicast session over that 5G LAN-VN.
+
+The 5G system shall be able to restrict private communications within a 5G LAN-VN based on UE's location (i.e. when the UE moves out of the area it can no longer communicate on the 5G LAN-VN).
+
+The 5G network shall enable member UEs of a 5G LAN-VN to use multicast/broadcast over a 5G LAN-type service to communicate with required latency (e.g. 180 ms).
+
+The 5G system shall support a mechanism to provide consistent QoE to all the member UEs of the same 5G LAN-VN.
+
+The 5G system shall support routing based on a private addressing scheme within the 5G LAN-VN.
+
+The 5G system shall support a communication path between a non-3GPP device in the CPN and a UE in the 5G-LAN VN via the eRG of the CPN, for an eRG that is part of the 5G LAN-VN.
+
+#### 6.26.2.3 Creation and management
+
+The 5G network shall enable the network operator to scale up/down a 5G LAN-VN, e.g. the coverage, capacity for efficient consumption of network resources.
+
+The 5G network shall enable the network operator to create, manage, and remove 5G LAN-VN including their related functionality (subscription data, routing and addressing functionality).
+
+The 5G network shall enable the network operator to add one or more authorized UEs to an existing 5G LAN-VN.
+
+NOTE 1: A UE needs to be authorized by the MNO to use 5G LAN-type service before it can be added to any 5G LAN-VN.
+
+NOTE 2: some use cases will require user permission for a UE to be added to a 5G LAN-VN.
+
+The 5G system shall enable the network operator to add an authorized UE to multiple independent 5G LAN-VNs.
+
+The 5G network shall enable the network operator to remove one or more UEs from an existing 5G LAN-VN.
+
+NOTE 3: Removing a UE from a 5G LAN-VN does not have impact on other 5G LAN-VNs that the UE is a member of.
+
+The 5G system shall enable the network operator to configure a 5G LAN-VN that is available only within a geographical area.
+
+Based on MNO policy, the 5G network shall provide suitable means to allow an authorised third party to
+
+- monitor changes in QoS policy that pertains to LAN-VN performance;
+- configure and receive information regarding the achieved performance for a specific UE;
+- configure and receive information regarding the achieved performance for a specific network;
+- receive notification of changes in specific configuration aspects of the UE in the VN (e.g., changes in group membership information.)
+
+#### 6.26.2.4 Privacy
+
+The 5G system shall be able to prevent the sharing of a UE's identifying information (e.g. SUPI, MSISDN) on private communication among UEs using 5G LAN-type service.
+
+#### 6.26.2.5 Traffic types
+
+A 5G system shall support all media types (e.g. voice, data, multimedia) for 5G LAN-type service.
+
+The 5G system shall support traffic scenarios typically found in a home setting (from sensors to video streaming, relatively low amount of UEs per group, many devices are used only occasionally) for 5G LAN-type service.
+
+The 5G system shall support traffic scenarios typically found in an office setting (from sensors to very high data rates e.g. for conferencing, medium amount of UEs per group) for 5G LAN-type service.
+
+The 5G system shall support traffic scenarios typically found in an industrial setting (from sensors to remote control, large amount of UEs per group) for 5G LAN-type service.
+
+#### 6.26.2.6 Discovery
+
+The 5G system shall enable a member UE to discover other member UEs within the same 5G LAN-VN.
+
+The 5G LAN-type service shall be able to support existing non-3GPP service discovery mechanisms (e.g. mechanisms to discover printers).
+
+#### 6.26.2.7 (void)
+
+#### 6.26.2.8 Indirect communication mode
+
+The 5G system shall support 5G LAN-type service for authorized UEs using indirect network connection or direct network connection.
+
+The 5G network shall be able to provide a remote UE using 5G LAN-type service with same level of service as if the remote UE would be using a direct network connection (i.e. provide required QoS for the Ethernet packets transferred between remote UE and relay UE if they are using 3GPP access).
+
+The 5G network shall be able to support service continuity for the private communication between a remote UE with other member UEs of the same 5G LAN-VN, when the remote UE changes from one relay UE to another or when the UE changes between direct and indirect network connection.
+
+#### 6.26.2.9 Service exposure
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to create/remove a 5G LAN-VN.
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to manage a 5G LAN-VN dedicated for the usage by the trusted third-party, including the address allocation.
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to authorize/deauthorize UEs to access a specific 5G LAN-VN managed by the trusted third-party.
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to add/remove an authorized UE to/from a specific 5G LAN-VN managed by the trusted third-party.
+
+## 6.27 Positioning services
+
+### 6.27.1 Description
+
+5G positioning services aims to support verticals and applications with positioning accuracies better than 10 meters, thus more accurate than the ones of TS 22.071 [24] for LCS. High accuracy positioning is characterized by ambitious system requirements for positioning accuracy in many verticals and applications, including regulatory needs.
+
+In Location-Based-Services and eHealth, higher accuracy is instrumental to new services and applications, both outdoor and indoor.
+
+For example, on the factory floor, it is important to locate assets and moving objects such as forklifts, or parts to be assembled. Similar needs exist in transportation and logistics, for example rail, road and use of UAVs. In some road user cases, UE's supporting V2X application(s) are also applicable to such needs. In cases such as guided vehicles (e.g. industry, UAVs) and positioning of objects involved in safety-related functions, availability needs to be very high.
+
+Mission Critical Organizations require mission critical services to have accurate positioning such that first responders can be located at all times during normal and critical operations, indoors as well as outdoors. The level of positioning accuracy (and other KPIs) required is much more stringent than that required by local and regional regulatory requirements for commercial 5G users.
+
+### 6.27.2 Requirements
+
+The 5G system shall provide 5G positioning services in compliance with regulatory requirements.
+
+NOTE 1: example of regulatory requirements encompasses requirements on emergency calls (e.g. e911), reliability and safety requirement (RAMS) applicable to some use cases and verticals, implementation of Priority, Precedence, Preemption (PPP) mechanisms to ensure sufficient reliability metrics are reached.
+
+The 5G system shall provide different 5G positioning services, supported by different single and hybrid positioning methods to supply absolute and relative positioning.
+
+NOTE 2: hybrid positioning methods include both the combination of 3GPP positioning technologies and the combination of 3GPP positioning technologies with non-3GPP positioning technologies such as, GNSS (e.g. Beidou, Galileo, GPS, Glonass), Network-based Assisted GNSS and High-Accuracy GNSS, Terrestrial Beacon Systems, dead-reckoning sensors (e.g. IMU, barometer), WLAN/Bluetooth-based positioning.
+
+The 5G system shall enable an MCX UE to use the 5G positioning services to determine its position with the associated uncertainty/confidence of the position, on request, triggered by an event or periodically.
+
+The 5G System shall be able to provide the 5G positioning services in case of roaming.
+
+The 5G system shall support mechanisms to determine the UE's position-related data for period when the UE is outside the coverage of 3GPP RAT-dependent positioning technologies but within the 5G positioning service area (e.g. within the coverage of satellite access).
+
+The 5G system shall be able to make the position-related data available to an application or to an application server existing within the 5G network, external to the 5G network, or in the User Equipment.
+
+NOTE 3: the position service latency can be tailored to the use cases.
+
+The 5G system shall be able to manage and log position-related data in compliance with applicable traceability, authentication and security regulatory requirements.
+
+The 5G network shall be able to request the UE to provide its position-related data on request—together with the accuracy of its position—triggered by an event or periodically and to request the UE to stop providing its position-related data periodically.
+
+NOTE 4: This requirement does not preclude whether the position is computed in the UE or elsewhere in the 5G System (e.g. core network).
+
+The 5G system shall support mechanisms to configure dynamically the update rate of the position-related data to fulfil different performances (e.g. power consumption, position service latency) or different location modes.
+
+NOTE 5: for example, the 5G System needs to be able to request the UE to provide its location periodically with an update rate ranging from one location every [1 s to 10 s] in location normal mode to one location every [30 s to 300 s, or more] in location power saving mode. The 5G System needs to allow UEs to sleep for extended periods (e.g. one week), without requiring the UE to update its position data.
+
+The 5G system shall allow the UE to trigger a different update rate of the position-related data based on whether the UE is moving or not.
+
+The 5G system shall be able to determine the position-related data of the 5G positioning services with any update rate ranging from one set of position-related data every 0,1 s to one set of position-related data every month.
+
+NOTE 6: the position service latency can be tailored to the use cases.
+
+The 5G System shall be able to negotiate the positioning methods according to the operator's policy or the application's requirements or the user's preferences and shall support mechanisms to allow the network or the UE to trigger this negotiation.
+
+The 5G system shall supply a method for the operator to configure and manage different positioning services for different users.
+
+The 5G system shall be able to determine the reliability, and the uncertainty or confidence level, of the position-related data.
+
+The 5G system shall be able to access to the positioning methods used for calculating the position-related data and to the associated uncertainty/confidence indicators.
+
+## 6.28 Cyber-physical control applications in vertical domains
+
+### 6.28.1 Description
+
+The 5G system is expected to meet the service requirements for cyber-physical control applications in vertical domains.
+
+A vertical domain is a particular industry or group of enterprises in which similar products or services are developed, produced, and provided. Automation refers to the control of processes, devices, or systems in vertical domains by automatic means. The main control functions of automated control systems include taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators.
+
+Cyber-physical systems are to be understood as systems that include engineered, interacting networks of physical and computational components. Cyber-physical control applications are to be understood as applications that control physical processes. Cyber-physical control applications in automation follow certain activity patterns, which are open-loop control, closed-loop control, sequence control, and batch control.
+
+Communication services supporting cyber-physical control applications need to be ultra-reliable, dependable with a high communication service availability, and often require low or (in some cases) very low end-to-end latency.
+
+Communication in automation in vertical domains follows certain communication patterns. The most well-known is periodic deterministic communication, others are a-periodic deterministic communication and Smart Grid.
+
+Smart Grid is a term that refers to enhanced cyber-physical control of electrical grids and to related application. Smart Grid operation can cover power generation, transmission, distribution, and consumption, which can require high communication service availability and communication service reliability, and in some cases a low end-to-end latency with more accurate clock synchronization. 5G system functionalities can be used for Smart Grid control, monitoring, availability assurance, service security, isolation and etc. Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation and energy automation.
+
+For more information about cyber-physical control applications in specific vertical domains, see clauses D.1 to D.4.
+
+### 6.28.2 Requirements
+
+#### 6.28.2.1 General
+
+The 5G system supports the communication services for cyber-physical control applications in the vertical domains of factories of the future (smart manufacturing), electric power distribution, smart grid, central power generation, and rail-bound mass transit. The associated requirements are described in 3GPP TS 22.104 [21].
+
+#### 6.28.2.2 Smart Grid
+
+For the 5G system to support the Smart Grid, the 5G systems needs to fulfil at minimum the following requirements.
+
+- 3GPP TS 22.104 clauses 5.2, 5.3, and 5.6 for requirements related to periodic communication, aperiodic communication, and clock synchronization;
+- 3GPP TS22.104, clause 5.6.1, 5.6C, 9 and A.4 for Smart Grid specific service requirements;
+- 3GPP TS 22.261, clauses 6.10, 6.13, 6.14, and 6.26 for requirements related to the support of secured communication between the 5G system and a trusted third-party;
+- 3GPP TS 22.261, clauses 6.23 for the requirements related to information exchange between the 5G system and a trusted third-party;
+- 3GPP TS 22.261, clause 8.9 for the requirements on security.
+
+## 6.29 Messaging aspects
+
+### 6.29.1 Description
+
+The 5G system is expected to support advanced capabilities and performance of messaging service especially for massive IoT communication which are introduced by the MSGin5G Service [22]. The MSGin5G Service provides one to one, group and broadcast message services for thing-to-thing and person-to-thing communication with low end-to-end latency and high reliability of message delivery, in a resource efficient manner to optimize the resource usage of the both control plane and user plane in the network, and power saving in the user devices.
+
+### 6.29.2 Requirements
+
+The 5G system supports the MSGin5G Service. The associated service level requirements of the MSGin5G Service are described in 3GPP TS 22.262 [22].
+
+## 6.30 Steering of roaming
+
+### 6.30.1 Description
+
+Steering of roaming allows the HPLMN (or subscribed NPN) to steer a UE to a VPLMN or NPN on which the HPLMN (or subscribed NPN) wants the UE to register, when the UE registers on another VPLMN or NPN. This capability can be needed for reasons e.g. reselection to a higher priority PLMN, or NPNs, based on business arrangements.
+
+### 6.30.2 Requirements
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.011 [3], clause 3.2.2.8.
+
+The 5G system shall support a mechanism for the HPLMN to control the timing when a UE registered on a VPLMN, in automatic mode (see clause 3.1 of TS 23.122 [25]) and currently in CONNECTED mode, enters IDLE mode and initiates higher priority PLMN selection based on the type of ongoing communication.
+
+NOTE 1: Changes needed to support the above requirement are expected to have minimum impact on the 5G system. UE is expected to initiate the above-mentioned PLMN selection e.g. by locally releasing the established N1 NAS signalling connection.
+
+NOTE 1a: The requirement above applies also to the case of a UE registered to a non-subscribed (standalone) NPN, in order to select a higher priority PLMN or NPN.
+
+The UE shall be able to delay conforming to steering of roaming control information from the HPLMN while it is engaged in priority service (e.g. emergency call, MPS session), or a service defined by HPLMN policy not to be interrupted (e.g. MMTEL voice/video call).
+
+NOTE 2: The HPLMN policy can take into account the user's preference for the service(s) not to be interrupted. User preferences can be communicated utilizing non-standard operator-specific mechanisms, e.g. web-based.
+
+The mechanism mentioned above in this clause shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 5G system.
+
+The 5G system shall support mechanisms to enable a credentials holder (e.g. HPLMN or subscribed standalone NPN) to send steering of roaming information to a UE for selecting standalone NPNs (e.g. prioritized list of preferred NPNs).
+
+## 6.31 Minimization of Service Interruption
+
+### 6.31.1 Description
+
+A mobile network can fail to provide service in the event of a disaster (for example a fire.) The requirements listed in this clause provide the 5GS with the capability to mitigate interruption of service. UEs can obtain service in the event of a disaster, if there are PLMN operators prepared to offer service. The minimization of service interruption is constrained to a particular time and place. To reduce the impact to the 5G System of supporting Disaster Roaming, the potential congestion resulting from an influx or outflux of Disaster Inbound Roamers is taken into account.
+
+### 6.31.2 Requirements
+
+#### 6.31.2.1 General
+
+Subject to regulatory requirements or operator's policy, 3GPP system shall be able to enable a UE of a given PLMN to obtain connectivity service (e.g. voice call, mobile data service) from another PLMN for the area where a Disaster Condition applies.
+
+#### 6.31.2.2 Disaster Condition
+
+The 3GPP system shall enable UEs to obtain information that a Disaster Condition applies to a particular PLMN or PLMNs.
+
+NOTE: If a UE has no coverage of its HPLMN, then obtains information that a Disaster Condition applies to the UE's HPLMN, the UE can register with a PLMN offering Disaster Roaming service.
+
+The 3GPP system shall support means for a PLMN operator to be aware of the area where Disaster Condition applies.
+
+The 3GPP system shall be able to support provision of service to Disaster Inbound Roamer only within the specific region where Disaster Condition applies.
+
+The 3GPP system shall be able to provide efficient means for a network to inform Disaster Inbound roamers that a Disaster Condition is no longer applicable.
+
+Subject to regulatory requirements or operator's policy, the 3GPP system shall support a PLMN operator to be made aware of the failure or recovery of other PLMN(s) in the same country when the Disaster Condition is applies, or when the Disaster Condition is not applicable.
+
+#### 6.31.2.3 Disaster Roaming
+
+The 3GPP system shall be able to provide means to enable a UE to access PLMNs in a forbidden PLMN list if a Disaster condition applies and no other PLMN is available except for PLMNs in the forbidden PLMN list.
+
+The 3GPP system shall provide means to enable that a Disaster Condition applies to UEs of a specific PLMN.
+
+The 3GPP system shall be able to provide a resource efficient means for a PLMN to indicate to potential Disaster Inbound Roamers whether they can access the PLMN or not.
+
+Disaster Inbound Roamers shall perform network reselection when a Disaster Condition has ended.
+
+The 3GPP system shall minimize congestion caused by Disaster Roaming.
+
+The 5G system shall support a mechanism for the HPLMN to control whether a UE, with HPLMN subscription, should apply Disaster Roaming when a Disaster Condition arises (in the HPLMN or a VPLMN).
+
+3GPP system shall be able to collect charging information for a Disaster Inbound Roamer with information about the applied disaster condition.
+
+## 6.32 UAV aspects
+
+### 6.32.1 Description
+
+The 3GPP system is expected to support various enhanced UAV scenarios, especially for a wide range of applications and scenarios by using low altitude UAVs in various commercial and government sectors.
+
+### 6.32.2 Requirements
+
+The 3GPP system supports service requirements and KPIs related to command and control (C2), payload (e.g. camera) and the operation of radio access nodes on-board of UAVs. The associated requirements are described in 3GPP TS 22.125 [26].
+
+## 6.33 Video, imaging and audio for professional applications
+
+### 6.33.1 Description
+
+Audio-Visual (AV) production includes television and radio studios, live news-gathering, sports events, music festivals, among others. Typically, numerous wireless devices such as microphones, in-ear monitoring systems or cameras are used in these scenarios. In the future, the wireless communication service for such devices are expected to be provided by a 5G system. AV production applications require a high degree of confidence, since they are related to the capturing and transmission of data at the beginning of a production chain. This differs drastically when compared to other multimedia services because the communication errors will be propagated to the entire audience that is consuming that content both live and on recorded media. Furthermore, the transmitted data is often post-processed with filters which could actually amplify defects that would be otherwise not noticed by humans. Therefore, these applications call for
+
+uncompressed or slightly compressed data, and very low probability of errors. These devices will also be used alongside existing technologies which have a high level of performance and so any new technologies will need to match or improve upon the existing workflows to drive adoption of the technology.
+
+The 3GPP system already plays an important role in the distribution of AV media content and services. Release 14 contains substantial enhancements to deliver TV services of various kinds, from linear TV programmes for mass audiences to custom-tailored on-demand services for mobile consumption. However, it is expected that also in the domain of AV content and service production, 3GPP systems will become an important tool for a market sector with steadily growing global revenues. There are several areas in which 3GPP networks can help to produce AV content and services in an efficient and flexible manner.
+
+### 6.33.2 Requirements
+
+The 5G system supports the communication services for video, imaging and audio for professional applications. The associated requirements are described in 3GPP TS 22.263 [28].
+
+## 6.34 Critical medical applications
+
+### 6.34.1 Description
+
+The 5G system is expected to meet the service requirements for critical medical applications where critical medical applications denote medical devices and applications involved in the delivery of care for patient's survival. Additionally, as the medical industry undergoes a shift to value-based healthcare, where companies and healthcare providers have to move to business models based on providing clinical value with cost efficiency, the 5G system can help to adopt new and more efficient care delivery models in order to reduce administrative and supply costs.
+
+On this matter, 5G technology can especially have an important impact by:
+
+- enabling superior monitoring capability means thus improving the effectiveness of preventive care,
+- enabling shifting care location from hospitals to homes and other lower cost facilities,
+- improving operating room planning, enabling streamlining equipment usage and simplifying operating theater implementation,
+- Enhancing cooperation in critical situations between ambulance and hospital staff.
+
+### 6.34.2 Requirements
+
+The 5G system shall support the communication services for critical medical applications. The associated requirements are described:
+
+- in 3GPP TS 22.104 [21] for the requirements related to controlling both local or remote robotic diagnosis or surgery systems,
+- in 3GPP TS 22.263 [28] for the requirements related to high quality medical imaging and augmented reality systems located in hybrid operating rooms, in remote healthcare facilities or ambulances,
+- in 3GPP TS 22.261 clause 7.5 for the requirements on the support of tele-diagnosis or tele-monitoring systems,
+- in 3GPP TS 22.261 clauses 6.10, 8.2 and 8.9 for the requirements on the security of medical data that fulfil regulatory requirements.
+
+## 6.35 Service Function Chaining
+
+### 6.35.1 Introduction
+
+In order to support enhancement of service function chaining for 5G networks beyond the requirements for FMSS in TS 22.101, the network operator defines service function chaining policies for service function chaining to steer the traffic associated to the application and its users on per UE basis to appropriate ordered service functions.
+
+A service function chain for 5G networks contains service functions such as firewall functions, NAT, antimalware, parental control, DDoS protection, TCP proxies, load balancers, KPI monitoring, and video optimization, etc.
+
+NOTE: these are non-exhaustive examples of service functions. Other service functions can be provided by an operator.
+
+### 6.35.2 General Requirements
+
+The following requirements apply for supporting enhancement of service function chaining for 5G networks:
+
+- The network operator shall be able to define and modify service function chaining policies for steering traffic on per application per UE basis through required service function chaining with ordered service functions to improve the user's QoE.
+- Service functions chaining policies shall be able to distinguish between upstream and downstream traffic.
+- The coexistence of traffic with and without service function chaining shall be supported.
+- Service function chaining shall provide suitable means for authorized third parties to request a chain of service functions provided by the network operator based on operator's service function chaining policies.
+- In case of roaming, the HPLMN shall be able to apply traffic steering policies and service function chaining policies for home routed traffic.
+- In case of roaming with local breakout, the HPLMN shall be able to provide the traffic steering policies and service function chaining policies to the VPLMN providing local breakout with support of service function chaining.
+- Service function chaining shall support deployments where the Hosted Services are provided by the operator and deployments where the Hosted Services are provided by a third party.
+
+### 6.35.3 Service Function Management
+
+- The service function management shall allow the operator to create, modify, and delete a service function based on operator's service function chaining policies.
+- The service function management shall allow the operator to create, configure, and control a chain of service functions per application and its users on per UE basis based on operator's policy or request from third parties.
+ - The service function management shall be able to manage service function chaining for deployments where the Hosted Services are provided by the operator and for deployments where the Hosted Services are provided by a third party.
+
+## 6.36 5G Timing Resiliency
+
+### 6.36.1 Overview
+
+5G systems rely on reference precision timing signals for network synchronization in order to operate. These synchronization references are generated by Primary reference Time Clocks that typically get the timing reference from GNSS receivers and in order to meet the relevant synchronization requirements also during failure conditions, the synchronization network designs typically include means to address potential degradation of the GNSS signal performance. Some deployment of 5G involve applications that themselves can be sensitive to any degradation of the timing signal. In such cases it is beneficial for the 5G system to be enhanced to act as a backup for loss of their GNSS references. In some implementations, timing resiliency enhancements to the 5G system can work in collaboration with different types of time sources (e.g., atomic clock, time service delivered over the fibre) to provide a robust time synchronization.
+
+5G as a consumer of time synchronization benefits from timing resiliency which enables the support of many critical services within the 5G network even during the event of a loss or degradation of the primary GNSS reference timing. Additionally, for time critical services (e.g. financial sector or smart grid), the 5G system can operate in collaboration with or as backup to other timing solutions. A base of clock synchronization requirements when 5G is providing a time
+
+signal, if it is deployed in conjunction with an IEEE TSN network or if it is providing support for IEEE 1588 related protocols, is included in [21] clause 5.6.
+
+The enhancements in this clause build on this to add timing resiliency to the 5G system enabling its use as a replacement or backup for other timing sources.
+
+### 6.36.2 General
+
+The 5G system shall support enhanced timing resiliency in collaboration with different types of time sources (e.g., GNSS, TBS/MBS [33] [34], Sync over Fiber [34]) to provide a robust time synchronization.
+
+The 5G system shall be able to maintain accurate time synchronization as appropriate for the supported applications in the event of degradation or loss of the primary timing reference (e.g., GNSS).
+
+### 6.36.3 Monitoring and Reporting
+
+The 5G system shall be able to support mechanisms to monitor for timing source failure (e.g., GNSS).
+
+The 5G system shall be able to detect when reference timing signals (e.g., from GNSS or other timing source) are no longer viable for network time synchronization.
+
+The 5G system shall support a mechanism to determine if there is degradation of the 5G time synchronization.
+
+The 5G system shall be able to support mechanisms to indicate to devices (e.g., UEs, applications) that there is an alternate time source available for use (e.g., 5G system internal holdover capability, atomic clock, Sync over Fiber, TBS, GNSS), taking into account the holdover capability of the devices.
+
+The 5G system shall be able to detect when a timing source fails or is restored for network time synchronization.
+
+The 5G system shall support mechanisms to monitor different time sources and adopt the most appropriate.
+
+The 5G system shall support a mechanism to report timing errors such as divergence from UTC and time sync degradation to UEs and 3rd party applications.
+
+### 6.36.4 Service Exposure
+
+The 5G system shall support a mechanism for a 3rd party application to request resilient timing with specific KPIs (e.g., accuracy, interval, coverage area).
+
+## 6.37 Ranging based services
+
+### 6.37.1 Description
+
+Ranging-based services are the applications utilizing the distance between two UEs and/or the direction of one UE from the other one. In 3D case, direction includes horizontal direction and elevation direction. Ranging-based services can apply to a variety of verticals, such as consumer, smart home, smart city, smart transportation, smart retail, and industry 4.0. Some ranging-based services can only require the distance measurement, some can only require direction measurement, others can require both distance and direction measurement.
+
+Ranging can be supported with or without 5G coverage and figure 6.37.1-1 is an illustration of ranging between UEs that are in coverage, out of coverage, or with partial coverage. Both licensed and unlicensed spectrum can be used for ranging. If licensed spectrum is used, it shall be fully under operator control.
+
+
+
+Figure 6.37.1-1: Illustration of ranging between UEs with or without 5G coverage. The diagram shows three scenarios: 'In coverage', 'Partial coverage', and 'Out of coverage'. In each scenario, two User Equipment (UE) blocks, labeled UE1 and UE2, are shown with a double-headed arrow between them labeled 'distance/direction'. In the 'In coverage' and 'Partial coverage' scenarios, the UEs are within a shaded oval representing 5G coverage, and a 5G base station icon is present. In the 'Out of coverage' scenario, the UEs are outside any coverage oval, and no base station is shown.
+
+**Figure 6.37.1-1: Illustration of ranging between UEs with or without 5G coverage**
+
+### 6.37.2 Requirements
+
+The 5G system shall be able to support for a UE to discover other UEs supporting ranging.
+
+The 5G system shall be able to authorize ranging for a UE or a group of UE when using licensed spectrum.
+
+The 5G system shall be able to protect privacy of a UE and its user, ensuring that no identifiable information can be tracked by undesired entities during ranging.
+
+The 5G system shall be able to enable or disable ranging.
+
+The 5G system shall support mutual ranging, i.e. two UEs shall be able to initiate ranging to each other.
+
+The 5G system shall be able to ensure that the use of Ranging, if in licensed spectrum, is only permitted in network coverage under the full control of the operator who provides the coverage.
+
+NOTE 1: The above requirement does not apply for public safety networks with dedicated spectrum, where ranging might be allowed out of coverage or in partial coverage as well.
+
+The 5G system shall support energy efficient UE ranging operation.
+
+The 5G system shall be able to start ranging and stop ranging according to the application layer's demand.
+
+The 5G system shall be able to provide mechanisms for a MNO, or authorized 3rd party, to provision and manage ranging operation and configurations.
+
+The 5G system shall be able to support mechanisms for a UE to assist another UE to perform ranging of a third UE (if the requesting UE is LOS with the assisting UE and the assisting UE is LOS with the third UE).
+
+NOTE 2: It cannot be assumed that all ranging UEs support the same application for exchange of information.
+
+The 5G system shall be able to support ranging enabled UEs to determine the ranging capabilities (e.g. capabilities to perform distance and/or angle measurement) of other ranging enabled UEs.
+
+The 5G system shall be able to allow a ranging enabled UE to determine if another ranging enabled UE is stationary or mobile, before and/or during ranging.
+
+NOTE 3: This may require assistance from other ranging enabled UEs.
+
+The 5G system shall allow ranging between 2 UEs triggered by and exposed to a third UE.
+
+The 5G system shall allow ranging service between 2 UEs triggered by and exposed to the application server.
+
+The 5G system shall be able to support one UE initiating ranging to the other UE.
+
+The 5G system shall be able to support ranging between UEs which subscribe to different operators.
+
+The 5G system shall be able to allow roaming UEs to perform ranging.
+
+The 5G system shall be able to ensure the integrity and confidentiality of ranging information used by ranging-enabled UEs.
+
+The 5G system shall be able to ensure that user privacy is not violated during ranging, e.g., subject to regional or national regulatory requirements.
+
+The 5G system shall be able to ensure security protection (e.g., interworking security) when the ranging concerns UEs subscribed with different operators.
+
+The level of security provided by the existing 5G system shall not be adversely affected when ranging is enabled.
+
+The 5G system shall support means to securely identify other ranging capable UEs, with which a certain UE can perform ranging.
+
+## 6.38 Personal IoT Networks and Customer Premises Networks
+
+### 6.38.1 Description
+
+Personal IoT Networks (PINs) and Customer Premises Networks (CPNs) provide local connectivity between UEs and/or non-3GPP devices. The CPN via an eRG, or PIN Elements via a PIN Element with Gateway Capability can provide access to 5G network services for the UEs and/or non-3GPP devices on the CPN or PIN. CPNs and PINs have in common that in general they are owned, installed and/or (at least partially) configured by a customer of a public network operator.
+
+A Customer Premises Network (CPN) is a network located within a premises (e.g. a residence, office or shop). Via an evolved Residential Gateway (eRG), the CPN provides connectivity to the 5G network. The eRG can be connected to the 5G core network via wireline, wireless, or hybrid access. A Premises Radio Access Station (PRAS) is a base station installed in a CPN. Through the PRAS, UEs can get access to the CPN and/or 5G network services. The PRAS can be configured to use licensed, unlicensed, or both frequency bands. Connectivity between the eRG and the UE, non-3GPP Device, or PRAS can use any suitable non-3GPP technology (e.g. Ethernet, optical, WLAN).
+
+A Personal IoT Network (PIN) consists of PIN Elements that communicate using PIN Direct Connection or direct network connection and is managed locally (using a PIN Element with Management Capability). Examples of PINs include networks of wearables and smart home / smart office equipment. Via a PIN Element with Gateway Capability, PIN Elements have access to the 5G network services and can communicate with PIN Elements that are not within range to use PIN Direct Connection. A PIN includes at least one PIN Element with Gateway Capability and at least one PIN Element with Management Capability.
+
+A PIN Element with Management Capability is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN.
+
+The requirements as described in 3GPP TS 22.101 [6] clause 26a can also apply to Personal IoT Networks and Customer Premises Networks.
+
+### 6.38.2 Requirements
+
+#### 6.38.2.1 General
+
+The 5G system shall support mechanisms to identify a PIN, a PIN Element, an eRG and a PRAS.
+
+Subject to local regulations, the 5G system shall support regulatory requirements for emergency calls, PWS and eCall for UEs connected via a CPN.
+
+NOTE: The above requirement applies to UEs connected via 3GPP access.
+
+The 5G system shall support applications on an Application Server connected to a CPN or PIN.
+
+The 5G system shall be able to support PINs with PIN Elements subscribed to more than one network operator (e.g., a PIN Element that is a MUSIM UE and subscribes to different operators respectively, one PIN Element subscribed to network operator A and another PIN Element subscribed to network operator B).
+
+Subject to regulatory requirements and operator policy, the 5G system shall support an efficient data path within the CPN for intra-CPN communications.
+
+NOTE 1: For services an operator deploys in the 5G network (i.e. not in the CPN), local data routed via eRG does not apply.
+
+Subject to regulatory requirements and operator policy, the 5G system shall support a data path not traversing the 5G network for intra-PIN communications via direct connections.
+
+The 5G system shall enable the network operator to provide any 5G services to any UE via a PRAS connected via an eRG.
+
+NOTE 2: Whether the PRAS can be used by UEs from other PLMNs in the same country as the PLMN associated with the PRAS is subject to regulatory policy on national roaming.
+
+The 5G system shall minimize service disruption for a UE that is moving between CPN access and operator provided mobile access.
+
+NOTE 3: CPN access can imply access via a PRAS or can imply access directly via an eRG. Operator provided mobile access implies access via an operator owned base station.
+
+The 5G system shall minimize service disruption when a CPN communication path changes between two PRASes.
+
+The 5G system shall be able to minimize service disruption when a PIN Element changes the communication path from one PIN Element (e.g. PIN Element with Gateway Capability) to another PIN Element or operator provided mobile access. The communication path between PIN Elements may include licensed and unlicensed spectrum as well as 3GPP and non-3GPP access.
+
+The 5G system shall be able to support PRAS sharing between multiple PLMNs.
+
+The 5G system shall support mechanisms to aggregate, switch or split the service between non-3GPP RAT and PIN direct connections using licensed spectrum.
+
+#### 6.38.2.2 Gateways
+
+The 5G system shall be able to support access to the 5G network and its services via at least one gateway (i.e. PIN Element with Gateway Capability or eRG) for authorised UEs and authorised non-3GPP devices in a PIN or a CPN.
+
+The 5G system shall be able to support IP traffic offload to data network for a CPN.
+
+NOTE 1: The priority of offload can be from default configuration, network or user.
+
+Under operator control, an eRG, shall be able to efficiently deliver 5G multicast/broadcast services to authorized UEs and non-3GPP devices in the CPN.
+
+NOTE 2: The multicast service(s) that each of the authorized UEs and/or non-3GPP devices is allowed to receive may be different.
+
+#### 6.38.2.3 Operation without 5G core network connectivity
+
+The 5G system shall allow PIN Elements to communicate when there is no connectivity between a PIN Element with Gateway Capability and a 5G network. For a Public Safety PIN licensed spectrum may be used for PIN direct communications otherwise unlicensed spectrum shall be used.
+
+When a CPN has lost connectivity with the 5G network, the 5G system shall provide an operator-controlled mechanism to enable:
+
+- in the default configuration, or under certain conditions configured by the operator, the PRAS radio interface shall be deactivated; and
+
+- under certain other conditions configured by the operator, the CPN shall continue existing intra-CPN communication, as long as no interaction with the 5G network is needed (e.g. refreshing security keys).
+
+NOTE 1: The requirement above relates to intra-CPN operations and is subject to operator policy and control, under certain situations.
+
+NOTE 2: Setting up new intra-CPN or intra-PIN communication sessions without connection to the 5G network is only possible with non-3GPP provided credentials.
+
+#### 6.38.2.4 Discovery
+
+The 5G system shall enable a UE or non-3GPP device in a CPN or PIN to discover other UEs or non-3GPP devices within the same CPN or PIN subject to access rights.
+
+The 5G system shall efficiently support service discovery mechanisms where a UE or non-3GPP device in a CPN or PIN can discover, subject to access rights:
+
+- availability and reachability of other entities (e.g. other UEs or non-3GPP devices) on the CPN or PIN;
+- capabilities of other entities on the CPN (e.g. PRAS, eRG) or PIN (e.g. relay UE, connection types) and/or;
+- services provided by other entities on the CPN or PIN (e.g. the entity is a printer). The 5G system shall support a mechanism for an Authorised Administrator to indicate whether a PIN element is discoverable by other PIN elements of the same PIN.
+
+The 5G system shall support a mechanism for an Authorised Administrator to indicate whether a PIN element is discoverable by UEs that are not members of the PIN.
+
+#### 6.38.2.5 Relay Selection
+
+In addition to the relay selection requirements in 6.9.2.4, relay selection within a PIN is enabled for both UEs and non-3GPP device and supports the additional selection criteria:
+
+- The 5G system shall support a mechanism for a PIN Element to select a relay for PIN direct connection that enables access to the target PIN Element.
+
+## 6.38.2.6 Security
+
+The 5G system shall provide user privacy; location privacy, identity protection and communication confidentiality for non-3GPP devices and UEs that are using the PIN Element with Gateway Capability, eRG or PRAS.
+
+NOTE 1: Privacy protection should not block differentiated routing and QoS for different destinations and services for the UE(s).
+
+The 5G system shall support a mechanism to minimize the security risk of communications using an eRG.
+
+The 5G system shall enable the network operator associated with an eRG to control the security policy of an eRG.
+
+The 5G system shall support a mechanism to minimize the security risk of communications via a PRAS.
+
+The PRAS (and its associated backhaul connectivity) shall provide a level of security equivalent to regular 5G base stations.
+
+The 5G system shall enable the network operator associated with the Premises Radio Access Station (PRAS) to control the security policy of the PRAS.
+
+The 5G system shall support authentication of a UE with 3GPP credentials for communication with entities (UEs, non-3GPP devices) in a CPN.
+
+NOTE 2: To support this functionality the CPN needs to be connected with the 5G core network.
+
+The 5G system shall provide support for a network operator to authenticate a PRAS.
+
+The 5G system shall provide support for a network operator to authorize a PRAS for its use in a CPN.
+
+The 5G system shall support a PIN Element using non operator managed credentials (e.g. provided by a third party) for performing communications within the PIN when those communications use PIN direct connections.
+
+The 5G system shall support a mechanism to mitigate repeated and unauthorized attempts to access PIN Elements (e.g. mitigate a malicious flood of messages).
+
+### 6.38.2.7 QoS
+
+The 5G system shall support real time E2E QoS monitoring and control for any intra-CPN data traffic to or from a UE (i.e. via eRG or via PRAS and eRG).
+
+The 5G system shall support real time E2E QoS monitoring and control for any data traffic between a UE within a CPN and the 5G network (i.e. via eRG or via PRAS and eRG).
+
+### 6.38.2.8 Charging
+
+The 5G system shall support charging data collection for data traffic to/from individual UEs in a CPN or PIN (i.e., UEs behind the PIN Element with Gateway Capability or eRG and/or PRAS).
+
+The 5G system shall be able to generate charging data that can differentiate between backhaul for the PRAS and other data traffic over the same access.
+
+### 6.38.2.9 Creation and Management
+
+The 5G system shall support a mechanism for the network operator to provision an eRG with:
+
+- policies on which transport (e.g. wireless, cable, etc.) is best suited for different negotiated QoS levels,
+- authentication credentials,
+- identification,
+- initial OA&M information, and
+- associated subscription
+
+The 5G system shall enable the network operator to configure a PRAS with:
+
+- radio settings pertaining to licensed spectrum,
+- authentication credentials,
+- identification,
+- initial OA&M information, and
+- associated subscription.
+
+Subject to operator policy, the 5G system shall enable the Authorised Administrator to provision a PRAS with UE access considerations (allowing all UEs, or allowing specific UEs only)
+
+The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of an eRG.
+
+The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of a PRAS.
+
+The 5G system shall support mechanisms for a network operator or authorized 3rd party (e.g., a PIN User) to create, remove and manage a PIN, including:
+
+- Authorizing/deauthorizing PIN Elements;
+- Authorizing/deauthorizing PIN Elements with Management Capability;
+- Authorizing/deauthorizing PIN Elements with Gateway Capability;
+- Establishing duration of the PIN;
+
+- Configure PIN Elements to enable service discovery of other PIN Elements;
+- Authorize/deauthorise if a PIN Element can use a PIN Element with Gateway Capability to communicate with the 5GS;
+- Authorize/deauthorise for a PIN Element(s):
+ - which other PIN Element it can communicate with,
+ - which applications/service or service in that PIN it can access,
+ - which PIN Element it can use as a relay.
+- Authorize/deauthorise a UE to perform service discovery of PIN Elements over the 5G network;
+- Configure a PIN Element for external connectivity e.g. via 5G system;
+
+NOTE1: The authorization can include the consideration of the location and time validity of the PIN and its PIN elements.
+
+The 5G system shall support a mechanism to enable a UE that is not a PIN Element of the PIN or a non-3GPP device that is not a PIN element of the PIN to request to join the PIN.
+
+The 5G system shall support mechanisms for a network operator to configure the following policies in a PIN:
+
+- Configure the connectivity type (e.g. licensed, unlicensed PIN direct connection) a PIN Element can use.
+
+5G system shall be able to support mechanism to provide life span information of the PIN to the authorized 3rd party or the PIN elements when the PIN is created for limited time span.
+
+The 5G system shall provide means to control which UEs can connect to a PRAS.
+
+The 5G system shall support mechanisms to provision a PIN Element to use either licensed (under control of a MNO) or unlicensed spectrum (may be under the control of the MNO, or not) (e.g., when it has no connectivity to the 5G system).
+
+## 6.39 5G IMS Multimedia Telephony Service
+
+### 6.39.1 Description
+
+The 5G system is expected to support advanced capabilities and performance of enhanced IMS multimedia telephony service to meet new demands from consumers, business customers and vertical markets. Nowadays 3GPP has introduced new network capabilities and new types of devices (e.g. AR/VR/XR devices, robot, etc.), which can bring promising improvements to IMS multimedia telephony service. While more and more individual consumers enjoy multimedia telephony services across the globe, multimedia telephony services become popular also among business customers. There are several primary business functions that organizations use multimedia telephony services for, including internal communication, talking with prospects (sales call), contacting current customers and clients, customer support, and contact centre (or call centre) activities. While business customers consider the multimedia telephony services offer attractive features to their business, they also experience some practical issues that expect support from the 5G system.
+
+### 6.39.2 General
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.173 [37].
+
+The IMS multimedia telephony service shall support AR media processing.
+
+### 6.39.3 Service Exposure
+
+Requirements in this clause are subject to regulatory requirements and operator policy.
+
+The 5G system shall provide means to allow a trusted third-party to update the multimedia telephony service subscription and allocate a third-party specific identity to an authorized user.
+
+NOTE: The third party is authorized to change user identities for those subscriptions authorized by the operator.
+
+The following requirements apply to the originating side:
+
+- The 5G network shall provide a means for third parties (e.g. enterprises) to be authorized to verify the use of calling identity information by its authorized users.
+- The 5G network shall provide a means for authorized third parties to verify that an authenticated user is authorized to include or reference the pre-established calling identity information included in the call setup or retrieved by the called party.
+- The 5G network shall provide a means to verify the authenticity of the pre-established stored identity information that is referenced by the call setup and retrieved by the called party.
+
+The following requirements apply to the terminating side.
+
+- The 5G network shall provide a means for third parties (e.g. enterprises) to be able to verify the caller's authorization to use the identity information either in addition to or instead of verification performed by the terminating PLMN.
+- The 5G network shall provide a means to verify the authenticity of any stored identity information referenced by the call setup to be presented to the called party.
+
+## 6.40 AI/ML model transfer in 5GS
+
+### 6.40.1 Description
+
+Artificial Intelligence (AI)/Machine Learning (ML) is being used in a range of application domains across industry sectors. In mobile communications systems, mobile devices (e.g. smartphones, automotive, robots) are increasingly replacing conventional algorithms (e.g. speech recognition, image recognition, video processing) with AI/ML models to enable applications. The 5G system can at least support three types of AI/ML operations:
+
+- AI/ML operation splitting between AI/ML endpoints
+
+The AI/ML operation/model is split into multiple parts according to the current task and environment. The intention is to offload the computation-intensive, energy-intensive parts to network endpoints, whereas leave the privacy-sensitive and delay-sensitive parts at the end device. The device executes the operation/model up to a specific part/layer and then sends the intermediate data to the network endpoint. The network endpoint executes the remaining parts/layers and feeds the inference results back to the device.
+
+- AI/ML model/data distribution and sharing over 5G system
+
+Multi-functional mobile terminals might need to switch the AI/ML model in response to task and environment variations. The condition of adaptive model selection is that the models to be selected are available for the mobile device. However, given the fact that the AI/ML models are becoming increasingly diverse, and with the limited storage resource in a UE, it can be determined to not pre-load all candidate AI/ML models on-board. Online model distribution (i.e. new model downloading) is needed, in which an AI/ML model can be distributed from a NW endpoint to the devices when they need it to adapt to the changed AI/ML tasks and environments. For this purpose, the model performance at the UE needs to be monitored constantly.
+
+- Distributed/Federated Learning over 5G system
+
+The cloud server trains a global model by aggregating local models partially-trained by each end devices. Within each training iteration, a UE performs the training based on the model downloaded from the AI server using the local training data. Then the UE reports the interim training results to the cloud server via 5G UL channels. The server aggregates the interim training results from the UEs and updates the global model. The updated global model is then distributed back to the UEs and the UEs can perform the training for the next iteration.
+
+## 6.40.2 Requirements
+
+Based on operator policy, the 5G system shall be able to provide means to allow an authorized third-party to monitor the resource utilisation of the network service that is associated with the third-party.
+
+NOTE 1: Resource utilization in the preceding requirement refers to measurements relevant to the UE's performance such as the data throughput provided to the UE.
+
+Based on operator policy, the 5G system shall be able to provide an indication about a planned change of bitrate, latency, or reliability for a QoS flow to an authorized 3rd party so that the 3rd party AI/ML application is able to adjust the application layer behaviour if time allows. The indication shall provide the anticipated time and location of the change, as well as the target QoS parameters.
+
+Based on operator policy, 5G system shall be able to provide means to predict and expose predicted network condition changes (i.e. bitrate, latency, reliability) per UE, to an authorized third party.
+
+Subject to user consent, operator policy and regulatory constraints, the 5G system shall be able to support a mechanism to expose monitoring and status information of an AI-ML session to a 3rd party AI/ML application.
+
+NOTE 2: Such mechanism is needed for AI/ML application to determine an in-time transfer of AI/ML model.
+
+5G system shall be able to provide event alerting to an authorized 3rd party, together with a predicted time of the event (e.g., alerting about traffic congestion or UE moving into/out of a different geographical area).
+
+NOTE 3: A 3rd party AI/ML application may use the prediction information to minimize disturbance in the transfer of learning data and AI/ML model data.
+
+The 5G system shall be able to expose aggregated QoS parameter values for a group of UEs to an authorized service provider.
+
+The 5G system shall be able to support an authorised 3rd party to change aggregated QoS parameter values associated with a group of UEs, e.g. UEs of a FL group.
+
+Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to expose information (e.g. candidate UEs) to an authorized 3rd party to assist the 3rd party to determine member(s) of a group of UEs (e.g. UEs of a FL group).
+
+## 6.41 Providing Access to Local Services
+
+### 6.41.1 Description
+
+Providing access to local services refers to the capability to provide access to a hosting network and a set of services offered by the hosting network provider, and 3rd party service providers including other network operators and 3rd party application providers. The services can be localized (i.e. provided at specific/limited area) and can be bounded in time. The user can become aware of the available access to local services, and the process to gain and terminate access to the hosting network and local services. This process should be efficient, and convenient from a user experience standpoint.
+
+Providing access to local services creates new opportunities for users and service providers. For example, access can be provided in areas where there is no coverage provided by other networks (for example, on a fairground established far from other infrastructure), or the access and local services can be established as needed (on a short-term basis), without the need for long term business relationships, permanently installed equipment, etc.
+
+The type of local services and access for localized services via a hosting network can be promoted and arranged through different channels. Principally the service providers (e.g., brick and mortar businesses, entertainment venues, construction contractors, first responder agencies, etc.) will provide information and proper incentive or instructions to potential users so that they will seek to access the local services via hosting networks.
+
+## 6.41.2 Requirements
+
+### 6.41.2.1 General
+
+In the requirements below, it is assumed that:
+
+- Both the home network and the hosting network can be a PLMN or NPN.
+- Only subscribers of a public network can roam into a PLMN. Examples of interworking scenarios between network operators and application providers for localized services are indicated in Annex H.
+
+### 6.41.2.2 Configuration of Localized Services in Hosting Network
+
+NOTE: The term “Service provider of localized services” includes also 3rd party service provider.
+
+The 5G system shall support suitable mechanisms to allow automatically establishing localized service agreements for a specific occasion (time and location) and building temporary relationship among hosting network operator and other service providers including network operators or 3rd party application providers.
+
+The 5G system shall support means for the service provider to request the hosting network via standard mechanisms to provide access to 3rd party services at a specific period of time and location. This period of time shall be flexible, so that a change in service provision can be decided at any time (e.g., to cancel or prolong local services in the locality of service delivery) based on localized services agreements.
+
+Based on localized services agreements, the 5G system shall provide suitable means to allow the service provider to request and provision various localized service requirements, including QoS, expected/maximum number of users, event information for discovery, network slicing, required IP connectivity etc, and routing policies for the application of the localized services via the hosting network.
+
+The 5G system shall support means for a hosting network to create policies and configure resources for the requested time and location for the 3rd party services based on the received request.
+
+The 5G system shall support means for a hosting network to notify the service provider of the accepted service parameters and routing policies.
+
+Subject to regulatory requirements and localized service agreements, the 5G system shall allow a home network operator to automatically negotiate policies with the hosting network for allowing the home network's subscribers to connect at a specific occasion, e.g., time and location, for their home network services.
+
+Subject to the automatic localized services agreements between the hosting network operator and home network operator, for UE with only home network subscription and with authorization to access hosting networks the 5G system shall support:
+
+- access to the hosting network and use home network services or selected localized services via the hosting network,
+- seamless service continuity for home network services or selected localized services when moving between two hosting networks or a host network and the home network.
+
+The 5G system shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of their spatial extent (in terms of a particular topology, for example a single cell), as specified by a service provider of localized services.
+
+The 5G system shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of the resources or capacity available, to correspond to requirements that apply only to the locality of service delivery, as specified by a service provider of localized services.
+
+The 5G system shall support means for a hosting network to provide a 3rd party service provider with information for automatic discovery of the hosting network by the UEs to allow access to specific 3rd party services.
+
+The 5G system shall support secure mechanisms to allow a home network to coordinate with a hosting network for a subscriber to temporarily access the hosting network (e.g., based on temporary credentials) at a given time (start time and duration) and location.
+
+### 6.41.2.3 User Manual Selection of Localized Services via Hosting Network
+
+The hosting network shall allow a UE to manually select temporary localized services which are provided via local breakout at the hosting network.
+
+NOTE: Localized services which are provided via local breakout at the hosting network can be based on interworking scenarios for hosting network owned/collaborative services as indicated in Annex H.
+
+### 6.41.2.4 UE Configuration, Provisioning, Authentication and Authorization
+
+Subject to localized services agreements, the 5G system shall enable a home network operator to authorize a UE for using its home network services via a hosting network for a certain period of time and/or location.
+
+The 5G system shall allow a trusted 3rd party service provider to provide UEs with localized service policy (e.g., QoS, network slice in the hosting or home network, service restriction such as time and location) via the hosting network or the UE's home network.
+
+The 5G system shall enable a UE to use credentials provided by the hosting network with or without coordination with the home network of the UE, to make use of localized services via the hosting network with a certain time (including starting time and the duration) and location validity.
+
+The 5G system shall be able to allow the home network to steer its UE(s) to a hosting network with the consideration of the location, times, coverage of the hosting network and services offered by the home network and hosting network.
+
+The 5G system shall provide support to enable secure means to authenticate and authorize a user of a UE accessing a hosting network, including cases in which a UE has no subscription to the hosting network and still needs to get authorized to use localized services via the hosting network.
+
+NOTE: It can be assumed that a network provider deploying a hosting network has access to respective identification information about the user, e.g., through a separate registration process outside the scope of 3GPP.
+
+The 5G system shall be able to authenticate and authorize the UE of a user authenticated to a hosting network to access the hosting network and its localized services on request of a service provider.
+
+### 6.41.2.5 UE Discovery, Selection and Access
+
+Subject to operator's policy and agreement between a 3rd party service provider and operator, the 5G system shall enable a UE to receive and use configuration provided by a 3rd party service provider to discover and access a hosting network and localized services, including the considerations of prior service agreement with a 3rd party service provider and no prior subscription to hosting network. If the UE is able to obtain services from two networks simultaneously, it may additionally select the hosting network. If the UE cannot maintain the connection to the home network while selecting the hosting network, the selection shall only be done on request by the user, i.e., using manual selection.
+
+The 5G system shall support secure means for a UE to select and access localized services which may be provided by a 3rd party service provider via a hosting network, independent of prior subscription to the hosting network or 3rd party service provider.
+
+The 5G system shall enable the home network to allow a UE to automatically select a hosting network for accessing localized services when specified conditions (e.g., predefined time, location) are fulfilled.
+
+The 5G system shall be able to prevent a UE to re-access the hosting network after the localized services were terminated if the authorization for the localized services is no longer valid (e.g., can be based on certain conditions such as time or location of the user).
+
+The 5G system may support means for a UE which may or may not have prior subscription to the hosting network to display human readable information on how to gain access to the hosting network and available 3rd party services.
+
+The 5G system shall support a mechanism to allow a user to manually select a specific local hosting network.
+
+NOTE: Additional information can be presented to the user to facilitate the manual network selection.
+
+The 5G system shall be able to limit access of specific UEs to a configurable area of a hosting network's coverage area.
+
+The 5G system shall be able to maintain privacy of a user against the hosting network while the UE does not make use of the hosting network, for example, to prevent tracking of UEs by hosting networks.
+
+The 5G system shall enable the home network to instruct a UE to select a hosting network with certain conditions (e.g., predefined time, location) based on the request from a service provider.
+
+The 5G system shall enable the home network to allow a UE to select a hosting network or change to another hosting network, without any additional user intervention as long as the delivered services, both localized services and home routed services, are unchanged.
+
+#### 6.41.2.6 Hosting Network Localized Services and Home Operator Services
+
+The 5G system shall enable the home network operator to indicate to the UE what services are preferred to be used from the home network when the UE connects to a hosting network and the requested services are available from both the hosting and the home network.
+
+Based on localized service agreements, the hosting network shall be able to provide required connectivity and QoS for a UE simultaneously connected to the hosting network for localized services and its home network for home network services.
+
+A UE shall be able to connect to its home network via the hosting network, if supported by the hosting network and the home network based on localized service agreements.
+
+#### 6.41.2.7 Returning to Home Network
+
+The 5G system shall provide mechanisms to mitigate user plane and control plane overload caused by a high number of UEs returning from a temporary local access of a hosting network to their home network in a very short period of time.
+
+The 5G system shall provide mechanisms to minimize the impact on the UEs communication e.g., to prevent user plane and control plane outages when returning to a home network together with other high number of UEs in a very short period of time, after terminating their temporary local access to a hosting network.
+
+#### 6.41.2.8 Charging
+
+The 5G system shall be able to collect charging information for the use of localized services at the hosting network and provide the charging records to UEs' home operators based on localized service agreements and charging policies provided by the service providers of localized services.
+
+#### 6.41.2.9 Regulatory Services
+
+A hosting network using the 5G system shall be able to support regulatory services (e.g., PWS, LI, and emergency calls), based on regional/national regulatory requirements.
+
+#### 6.41.2.10 Multicast/Broadcast
+
+The operator of a hosting network shall support a mechanism allowing different service providers of localized services to disseminate their services and content over broadcast/multicast transport. This mechanism should also provide means to include diverse content in the same transmission, e.g., to include advertisements with other content, or to include multiple content in the same media delivered to the user.
+
+A hosting network shall provide multicast and broadcast services in an energy efficient manner to UEs receiving this service.
+
+A hosting network shall support resource efficient content delivery through multicast/broadcast.
+
+A hosting network shall support a mechanism to provide low latency signalling for efficient content delivery to many UEs.
+
+Subject to home operator policy, a hosting network shall be able to prioritize specific multicast and broadcast services for local access over home routed access, even if the same service is available in both networks.
+
+## 6.42 Mobile base station relays
+
+### 6.42.1 Description
+
+The requirements below refer to a “*mobile base station relay*”, which is a mobile base station acting as a relay between a UE and the 5G network, i.e. providing a NR access link to UEs and connected wirelessly (using NR) through a donor NG-RAN to the 5G Core. Such mobile base station relay is assumed to be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle).
+
+NOTE: The radio link used between a mobile base station relay and served UEs, as well as between mobile base station relay and donor RAN, is assumed to be NR-Uu; in that regard, it should be clear that a mobile base station relay is different than a UE relay (which uses instead a PC5-based link to provide indirect connection to remote UEs).
+
+Few main underlying assumptions are:
+
+- requirements cover single-hop relay scenarios as baseline (multi-hop is not precluded);
+- legacy UEs are supported;
+- other stage-1 requirements (e.g. on wireless self-backhaul), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. relays on board of moving vehicles), thus cannot cover the requirements below, which are intended to be specific to mobile base station relays;
+- the identified requirements do not intend to imply or exclude specific network/relay architectures and topology solutions (e.g. could be IAB based, or others);
+- the MNO managing mobile base station relays, and the RAN/5GC they connect to, can be a PLMN or an NPN operator.
+
+### 6.42.2 Requirements
+
+The 5G system shall support efficient operation of mobile base station relays.
+
+The 5G system shall be able to support means, for a mobile network operator, to configure, provision and control the operation of a mobile base station relay, e.g. activation/deactivation, permitted location(s) or time of operation.
+
+The 5G system shall be able to support provisioning and configuration mechanisms to control UEs’ selection and access to a mobile base station relay, e.g. based on UE’s authorization, geographic or temporary restrictions, relay’s load.
+
+The 5G system shall be able to support RAN sharing between multiple PLMNs for UEs connected to the 5G network via mobile base station relays.
+
+NOTE 1: the above requirement assumes both relay and (donor) RAN resources, including UE access link and relay backhaul link, are shared among operators.
+
+The 5G system shall be able to configure and provision specific required QoS for traffic relayed via a mobile base station relay.
+
+NOTE 2: QoS is end-to-end, i.e. from UE to 5GC.
+
+Subject to regulatory requirements and based on operator policy, the 5G system shall support means to configure and expose monitoring information of a mobile base station relay to an MNO’s authorized third-party.
+
+The 5G system shall be able to provide means to optimize network behaviour to efficiently deliver data based on the mobility information (e.g., itinerary), known or predicted, of mobile base station relays.
+
+The 5G system shall be able to support communication from/to users of one MNO (MNO-A) via mobile base station relays, where the traffic between the relay and the MNO-A network is transported using 5G connectivity (RAN and 5GC) provided by a different MNO (MNO-B).
+
+NOTE 3: The 5G connectivity provided to the MNO-A relays by the different MNO (MNO-B) assumes a generic wireless backhaul transport, independent from the mobile base station relay functionalities.
+
+The 5G system shall be able to support UEs connectivity to RAN using simultaneously, a link without mobile base station relay and a link via a mobile base station relay, or simultaneous links via different mobile base station relays.
+
+NOTE 4: The above requirements cover scenarios where the two links (to the RAN) could be connected to the same or different RAN node(s), and assuming both relay(s) and RAN belong to the same PLMN.
+
+The 5G system shall be able to provide means to support efficient UE cell selection and cell reselection (between mobile base station relays or between relays and RAN) in the presence of mobile base station relays.
+
+The 5G system shall be able to ensure end-to-end service continuity, in the presence of mobile base station relays.
+
+NOTE 5: The above requirement intends to cover different scenarios of UE mobility (e.g. UE moving between two mobile base station relays, or between macro RAN and relay) and relay mobility (e.g. base station relay moving between different donor RAN nodes).
+
+The 5G system shall be able to support mechanisms to optimize mobility and energy efficiency for UEs located in a vehicle equipped with a base station relay.
+
+NOTE 6: The above requirements cover scenarios where mobile base station relays provide 5G access for both UEs in the vehicle and around the vehicle.
+
+The 5G system shall be able to support incremental deployment of connectivity by means of one or a series of mobile base station relays for use only in specific locations where UEs would receive no other 3GPP access (terrestrial or non-terrestrial) coverage, e.g., for public safety scenarios.
+
+The 5G system shall be able to support mobile base station relays using 3GPP satellite NG-RAN (NR satellite access).
+
+The 5G system shall be able to support mobile base station relays accessing to 5GC via NR satellite access and NR terrestrial access simultaneously.
+
+The 5G system shall be able to support service continuity for mobile base station relays using at least one 3GPP satellite NG-RAN.
+
+NOTE 7: This requirement applies to scenarios where there is a transition between two 3GPP NG-RAN, operated by the same MNO, involving at least one 3GPP satellite NG-RAN.
+
+The 5G system shall be able to identify and differentiate UEs' traffic carried via a mobile base station relay and collect charging information, including specific relay information (e.g. geographic location served by the relay).
+
+The 5G system shall support means for a mobile base station relay to have a certain subscription with a HPLMN, used to get access and connectivity to the HPLMN network (via a donor RAN).
+
+The 5G system shall support the ability of a base station relay to roam from its HPLMN into a VPLMN.
+
+The 5G system shall support mechanisms, for the HPLMN controlling a mobile base station relay, to enable/disable mobile relay operation if the relay is roaming in a VPLMN.
+
+The 5G system shall support mechanisms to disable mobile relay operation by a VPLMN where a mobile base station relay is roaming to.
+
+The 5G system shall be able to fulfil necessary regulatory requirements (e.g. for support of emergency services) when UEs access the 3GPP network via a mobile base station relay.
+
+The 5G system shall be able to support priority services (e.g. MPS) when UEs access the 3GPP network via a mobile base station relay.
+
+The 5G system shall be able to support location services for the UEs accessing 5GS via a mobile base station relay.
+
+The 5G system shall ensure that existing end-to-end 5G security between the UE and 3GPP network is unaffected when the UE accesses the 3GPP network via a mobile base station relay.
+
+The 5G system shall be able to minimize radio interference possibly caused by mobile base station relays.
+
+The 5G system shall minimize the impact of the presence of mobile base station relays on radio network management (e.g. through automatic neighbour cell list configuration).
+
+## 6.43 Tactile and multi-modal communication service
+
+### 6.43.1 Description
+
+The tactile and multi-modal communication service can be applied in multiple fields, e.g. industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road traffic, serious gaming, education, culture and smart grid [38]. These services support applications enabling input from more than one sources and/or output to more than one destinations to convey information more effectively. As figure 6.43.1-1 illustrates, the input and output can be different modalities including:
+
+- Video/Audio media;
+- Information received by sensors about the environment, e.g. brightness, temperature, humidity, etc.;
+- Haptic data: can be feelings when touching a surface (e.g., pressure, texture, vibration, temperature), or kinaesthetic senses (e.g. gravity, pull forces, sense of position awareness).
+
+
+
+Figure 6.43.1-1: Multi-modal interactive system diagram. The diagram shows a user (An ambiguous perception/instructor) providing 'Information from the user' and 'Information from ambient' to a central 'Multi-modality input' block. This block contains various sensors and data streams: Biometric from voice, Words from voice, Emotion from voice, Biometric from face, Emotion from face, Lips movements, Emotion from wearables, Gesture, Relative Location, Ambient information, and Haptic information from wearable. These inputs are processed by three services: Service 1 (Biometric recognition), Service 2 (Intention perception with Multi-modality NLP, Multi-modality emotion, and Multi-modality haptic), and Service 3 (Service presence with Audio/video service and IoT control). The services then provide 'Multi-modality output' back to the user, which includes Haptic feedback, Brightness, Sensible temperature, Video, and Audio.
+
+Figure 6.43.1-1. Multi-modal interactive system
+
+For immersive multi-modal VR applications, synchronization between different media components is critical in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization), particularly when the synchronization threshold between two or more modalities is less than the latency KPI for the application. Example synchronization thresholds [41] [42] [43] [44] are summarised in table 6.43.1-1.
+
+Table 6.43.1-1: Typical synchronization thresholds for immersive multi-modality VR applications
+
+| Media components | synchronization threshold (note 1) | |
+|---------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------|
+| audio-tactile | audio delay:
50 ms | tactile delay:
25 ms |
+| visual-tactile | visual delay:
15 ms | tactile delay:
50 ms |
+| NOTE 1: for each media component, “delay” refers to the case where that media component is delayed compared to the other. | | |
+
+### 6.43.2 Requirements
+
+The 5G system shall enable an authorized 3rd party to provide policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
+
+The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
+
+NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs' flows (e.g., haptic, audio and video) of a multi-modal communication session.
+
+## 6.44 Support of Roaming services providers
+
+### 6.44.1 Overview
+
+In the roaming ecosystem, a roaming services provider provides the technical and commercial means to facilitate the deployment and operation of roaming services between a client operator and a set of selected connected operators.
+
+The roaming services provider handles the technical implementation of the roaming relations in a scalable and operationally efficient way.
+
+With a roaming services provider present in the roaming ecosystem, operators can choose not to establish a bilateral direct agreement with specific operators. A trusted relation exists between the involved operator and the roaming services provider.
+
+Roaming services providers, according to their role and responsibilities, assume financial and technical liability to apply all necessary controls and access to all communications.
+
+Among other functionalities, a roaming services provider needs to:
+
+- Process identifiers and potentially other information transmitted in signalling messages between PLMNs in a secure manner.
+- Be able to modify, add or delete information that is relevant to their role, respecting what is contractually agreed in service level agreements (SLAs) and enforced technically.
+- Isolate the individual operator signalling flows from each other
+- Report on the detection of and mitigation of security breaches.
+
+### 6.44.2 Requirements
+
+The 5G system shall allow roaming services to be provided by a roaming services provider in charge of managing roaming agreements, by mediating between two or more PLMNs, while maintaining the privacy and 5G security of any information transmitted between the home and the serving PLMN.
+
+NOTE 1: A PLMN can support both bi-lateral direct relationships with other PLMNs and make use of roaming service provider services toward different roaming partners.
+
+The 5G system shall allow a roaming services provider to be a trusted entity for either a home PLMN, a visited PLMN or both.
+
+NOTE 2: The expected maximum number of roaming service providers is two, one for the home PLMN and another for the visited PLMN.
+
+The 5G system shall allow a roaming services provider to accept or reject registration attempts, on behalf of the involved PLMNs, based on the roaming agreements.
+
+NOTE 3: Rejecting user registrations using an appropriate release cause permits the UE to be able to reselect another roaming partner or technology.
+
+The 5G system shall allow a roaming services provider to identify the origin and destination PLMN, and to verify the authenticity, of every transmitted message.
+
+The 5G system shall allow the Roaming services provider to be able to originate and modify messages as per contractually agreed SLAs.
+
+The 5G system shall allow the involved PLMNs to be able to identify the origin of any message generated by the roaming services providers as well as to identify any modification made to the exchanged messages by the roaming services providers.
+
+---
+
+## 7 Performance requirements
+
+### 7.1 High data rates and traffic densities
+
+Several scenarios require the support of very high data rates or traffic densities of the 5G system. The scenarios address different service areas: urban and rural areas, office and home, and special deployments (e.g. massive gatherings, broadcast, residential, and high-speed vehicles). The scenarios and their performance requirements can be found in table 7.1-1.
+
+- Urban macro – The general wide-area scenario in urban area
+- Rural macro – The general wide-area scenario in rural area
+- Indoor hotspot – The scenario for offices and homes, and residential deployments.
+- Broadband access in a crowd – The scenario for very dense crowds, for example, at stadiums or concerts. In addition to a very high connection density the users want to share what they see and hear, putting a higher requirement on the uplink than the downlink.
+- Dense urban – The scenario for pedestrian users, and users in urban vehicles, for example, in offices, city centres, shopping centres, and residential areas. The users in vehicles can be connected either directly or via an onboard base station to the network.
+- Broadcast-like services – The scenario for stationary users, pedestrian users, and users in vehicles, for example, in offices, city centres, shopping centres, residential areas, rural areas and in high speed trains. The passengers in vehicles can be connected either directly or via an onboard base station to the network.
+- High-speed train – The scenario for users in trains. The users can be connected either directly or via an onboard base station to the network.
+- High-speed vehicle – The scenario for users in road vehicles. The users can be connected either directly or via an onboard base station to the network.
+- Airplanes connectivity – The scenario for users in airplanes. The users can be connected either directly or via an onboard base station to the network.
+
+**Table 7.1-1 Performance requirements for high data rate and traffic density scenarios.**
+
+| | Scenario | Experienced data rate (DL) | Experienced data rate (UL) | Area traffic capacity (DL) | Area traffic capacity (UL) | Overall user density | Activity factor | UE speed | Coverage |
+|---|-----------------------------|-------------------------------------|------------------------------------------|-------------------------------------|-------------------------------------|------------------------------------------------|-----------------|----------------------------------------------------------------------|------------------------------------------|
+| 1 | Urban macro | 50 Mbit/s | 25 Mbit/s | 100 Gbit/s/km 2 (note 4) | 50 Gbit/s/km 2 (note 4) | 10 000/km 2 | 20 % | Pedestrians and users in vehicles (up to 120 km/h) | Full network (note 1) |
+| 2 | Rural macro | 50 Mbit/s | 25 Mbit/s | 1 Gbit/s/km 2 (note 4) | 500 Mbit/s/km 2 (note 4) | 100/km 2 | 20 % | Pedestrians and users in vehicles (up to 120 km/h) | Full network (note 1) |
+| 3 | Indoor hotspot | 1 Gbit/s | 500 Mbit/s | 15 Tbit/s/km 2 | 2 Tbit/s/km 2 | 250 000/km 2 | note 2 | Pedestrians | Office and residential (note 2) (note 3) |
+| 4 | Broadband access in a crowd | 25 Mbit/s | 50 Mbit/s | [3,75] Tbit/s/km 2 | [7,5] Tbit/s/km 2 | [500 000]/km 2 | 30 % | Pedestrians | Confined area |
+| 5 | Dense urban | 300 Mbit/s | 50 Mbit/s | 750 Gbit/s/km 2 (note 4) | 125 Gbit/s/km 2 (note 4) | 25 000/km 2 | 10 % | Pedestrians and users in vehicles (up to 60 km/h) | Downtown (note 1) |
+| 6 | Broadcast-like services | Maximum 200 Mbit/s (per TV channel) | N/A or modest (e.g. 500 kbit/s per user) | N/A | N/A | [15] TV channels of [20 Mbit/s] on one carrier | N/A | Stationary users, pedestrians and users in vehicles (up to 500 km/h) | Full network (note 1) |
+| 7 | High-speed train | 50 Mbit/s | 25 Mbit/s | 15 Gbit/s/train | 7,5 Gbit/s/train | 1 000/train | 30 % | Users in trains (up to 500 km/h) | Along railways (note 1) |
+| 8 | High-speed vehicle | 50 Mbit/s | 25 Mbit/s | [100] Gbit/s/km 2 | [50] Gbit/s/km 2 | 4 000/km 2 | 50 % | Users in vehicles (up to 250 km/h) | Along roads (note 1) |
+| 9 | Airplanes connectivity | 15 Mbit/s | 7,5 Mbit/s | 1,2 Gbit/s/plane | 600 Mbit/s/plane | 400/plane | 20 % | Users in airplanes (up to 1 000 km/h) | (note 1) |
+
+NOTE 1: For users in vehicles, the UE can be connected to the network directly, or via an on-board moving base station.
+NOTE 2: A certain traffic mix is assumed; only some users use services that require the highest data rates [2].
+NOTE 3: For interactive audio and video services, for example, virtual meetings, the required two-way end-to-end latency (UL and DL) is 2-4 ms while the corresponding experienced data rate needs to be up to 8K 3D video [300 Mbit/s] in uplink and downlink.
+NOTE 4: These values are derived based on overall user density. Detailed information can be found in [10].
+NOTE 5: All the values in this table are targeted values and not strict requirements.
+
+## 7.2 Low latency and high reliability
+
+### 7.2.1 Overview
+
+Several scenarios require the support of very low latency and very high communications service availability. Note that this implies a very high reliability. The overall service latency depends on the delay on the radio interface, transmission within the 5G system, transmission to a server which can be outside the 5G system, and data processing. Some of these factors depend directly on the 5G system itself, whereas for others the impact can be reduced by suitable interconnections between the 5G system and services or servers outside of the 5G system, for example, to allow local hosting of the services.
+
+### 7.2.2 Scenarios and KPIs
+
+Different deployments of URLLC capabilities will depend on the 3GPP system being able to meet specific sets of KPIs with different values and ranges applicable for each attribute. A common, yet flexible, 5G approach to URLLC will
+
+enable the 5G system to meet the specific sets of KPIs needed in a given implementation. To provide clear and precise requirements for specific types of services, the corresponding KPI requirements are included in other specifications as follows:
+
+- Cyber-physical control applications in vertical domains can be found in 22.104 [21].
+- V2X can be found in 22.186 [9].
+- Rail communications can be found in 22.289 [23].
+
+Some scenarios requiring very low latency and very high communication service availability are described below:
+
+- Motion control – Conventional motion control is characterised by high requirements on the communications system regarding latency, reliability, and availability. Systems supporting motion control are usually deployed in geographically limited areas but can also be deployed in wider areas (e.g. city- or country-wide networks), access to them can be limited to authorized users, and they can be isolated from networks or network resources used by other cellular customers.
+- Discrete automation – Discrete automation is characterised by high requirements on the communications system regarding reliability and availability. Systems supporting discrete automation are usually deployed in geographically limited areas, access to them can be limited to authorized users, and they can be isolated from networks or network resources used by other cellular customers.
+- Process automation – Automation for (reactive) flows, e.g. refineries and water distribution networks. Process automation is characterized by high requirements on the communications system regarding communication service availability. Systems supporting process automation are usually deployed in geographically limited areas, access to them is usually limited to authorized users, and it will usually be served by non-public networks.
+- Automation for electricity distribution and smart grid (mainly medium and high voltage). Electricity distribution and smart grid are characterized by high requirements on the communications service availability and security, as well as low latency in some cases. In contrast to the above use cases, electricity distribution and smart grid are deeply immersed into the public space. Since electricity distribution is an essential infrastructure, it is well served by network slices to provide service isolation and security, or by non-public networks.
+- Wireless road-side infrastructure backhaul in intelligent transport systems – Automation solutions for the infrastructure supporting street-based traffic. This use case addresses the connection of the road-side infrastructure, e.g. roadside units, with other infrastructure, e.g. a traffic guidance system. As is the case for automation electricity, the nodes are deeply immersed into the public space.
+- Remote control – Remote control is characterised by a UE being operated remotely by a human or a computer. For example, Remote Driving enables a remote driver or a V2X application to operate a remote vehicle with no driver or a remote vehicle located in a dangerous environment.
+- Rail communications (e.g. railway, rail-bound mass transit) have been using 3GPP based mobile communication (e.g. GSM-R) already for some time, while there is still a driver on-board of the train. The next step of the evolution will be providing fully automated train operation that requires highly reliable communication with moderate latencies but at very high speeds of up to 500 km/h.
+
+For specific requirements, refer to the specifications noted above [21], [9], [23].
+
+## 7.2.3 Other requirements
+
+### 7.2.3.1 (void)
+
+### 7.2.3.2 Wireless road-side infrastructure backhaul
+
+Intelligent Transport Systems embrace a wide variety of communications-related applications that are intended to increase travel safety, minimize environmental impact, improve traffic management, and maximize the benefits of transportation to both commercial users and the general public.
+
+Road-side infrastructure such as traffic light controllers, roadside units, traffic monitoring in urban areas and along highways and streets is wirelessly connected to traffic control centres for management and control purposes. The backhaul communication between the road-side infrastructure and the traffic control centre requires low-latency, high
+
+communication service availability, and high-capacity connections for reliable distribution of data. Road-side infrastructure is deployed alongside streets in urban areas and alongside major roads and highways every 1-2 km.
+
+For more information about infrastructure backhaul, see clause D.5.
+
+To support wireless road-side infrastructure backhaul the 5G system shall support the performance requirements in table 7.2.3.2-1.
+
+**Table 7.2.3.2-1 Performance requirements for wireless ITS infrastructure backhaul scenario**
+
+| Scenario | Max. allowed end-to-end latency (note 1) | Survival time | Communication service availability (note 2) | Reliability (note 2) | User experienced data rate | Payload size (note 3) | Traffic density (note 4) | Connection density (note 5) | Service area dimension (note 6) |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------|---------------------------------------------|----------------------|----------------------------|-----------------------|--------------------------|-----------------------------|---------------------------------|
+| wireless road-side infrastructure backhaul | 30 ms | 100 ms | 99,9999% | 99,999% | 10 Mbit/s | Small to big | 10 Gbit/s/km² | 1 000/km² | 2 km along a road |
+| NOTE 1: This is the maximum end-to-end latency allowed for the 5G system to deliver the service in the case the end-to-end latency is completely allocated to the 5G system from the UE to the Interface to Data Network.
NOTE 2: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
NOTE 3: Small: payload typically ≤ 256 bytes
NOTE 4: Based on the assumption that all connected applications within the service volume require the user experienced data rate.
NOTE 5: Under the assumption of 100% 5G penetration.
NOTE 6: Estimates of maximum dimensions; the last figure is the vertical dimension.
NOTE 7: All the values in this table are example values and not strict requirements. Deployment configurations should be taken into account when considering service offerings that meet the targets. | | | | | | | | | |
+
+## 7.3 High-accuracy positioning
+
+### 7.3.1 Description
+
+Adaptability and flexibility are among the key features of the 5G system to serve a wide diversity of verticals and services, in different environments (e.g. rural, urban, indoor). This applies to high-accuracy positioning and translates into the ability to satisfy different levels of services and requirements, for instance on performance (e.g. accuracy, positioning service availability, positioning service latency) and on functionality (e.g. security).
+
+### 7.3.2 Requirements
+
+#### 7.3.2.1 General
+
+The 5G System shall provide different 5G positioning services with configurable performances working points (e.g. accuracy, positioning service availability, positioning service latency, energy consumption, update rate, TTFF) according to the needs of users, operators and third parties.
+
+The 5G system shall support the combination of 3GPP and non-3GPP positioning technologies to achieve performances of the 5G positioning services better than those achieved using only 3GPP positioning technologies.
+
+NOTE 1: For instance, the combination of 3GPP positioning technologies with non-3GPP positioning technologies such as GNSS (e.g. Beidou, Galileo, GLONASS, and GPS), Terrestrial Beacon Systems (TBS), sensors (e.g. barometer, IMU), WLAN/Bluetooth-based positioning, can support the improvement of accuracy, positioning service availability, reliability and/or confidence level, the reduction of positioning service latency, the increase of the update rate of the position-related data, increase the coverage (service area).
+
+NOTE 2: The combination can vary over time to optimise the performances, and can be the combination of multiple positioning technologies at the same epoch and/or the combination of multiple positioning technologies at different epochs.
+
+The corresponding positioning information shall be acquired in a timely fashion, be reliable, and be available (e.g. it is possible to determine the position).
+
+UEs shall be able to share positioning information between each other e.g. to a controller if the location information cannot be processed or used locally.
+
+#### 7.3.2.2 Requirements for horizontal and vertical positioning service levels
+
+The 5G system shall be able to provide positioning services with the performances requirements reported in Table 7.3.2.2-1.
+
+NOTE: The requirements do not preclude any type of UE, including specific UE such as for example V2X, MTC.
+
+**Table 7.3.2.2-1 Performance requirements for Horizontal and Vertical positioning service levels**
+
+| Positioning service level | Absolute(A) or Relative(R) positioning | Accuracy (95 % confidence level) | | Positioning service availability | Positioning service latency | Coverage, environment of use and UE velocity | | | | |
+|---------------------------|----------------------------------------|----------------------------------|----------------------------|----------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------|--|--|
+| | | Horizontal Accuracy | Vertical Accuracy (note 1) | | | 5G positioning service area | 5G enhanced positioning service area (note 2) | | | |
+| | | | | | | | Outdoor and tunnels | Indoor | | |
+| 1 | A | 10 m | 3 m | 95 % | 1 s | Indoor - up to 30 km/h
Outdoor (rural and urban) up to 250 km/h | NA | Indoor - up to 30 km/h | | |
+| 2 | A | 3 m | 3 m | 99 % | 1 s | Outdoor (rural and urban) up to 500 km/h for trains and up to 250 km/h for other vehicles | Outdoor (dense urban) up to 60 km/h
Along roads up to 250 km/h and along railways up to 500 km/h | Indoor - up to 30 km/h | | |
+| 3 | A | 1 m | 2 m | 99 % | 1 s | Outdoor (rural and urban) up to 500 km/h for trains and up to 250 km/h for other vehicles | Outdoor (dense urban) up to 60 km/h
Along roads up to 250 km/h and along railways up to 500 km/h | Indoor - up to 30 km/h | | |
+| 4 | A | 1 m | 2 m | 99,9 % | 15 ms | NA | NA | Indoor - up to 30 km/h | | |
+| 5 | A | 0,3 m | 2 m | 99 % | 1 s | Outdoor (rural) up to 250 km/h | Outdoor (dense urban) up to 60 km/h
Along roads and along railways up to 250 km/h | Indoor - up to 30 km/h | | |
+| 6 | A | 0,3 m | 2 m | 99,9 % | 10 ms | NA | Outdoor (dense urban) up to 60 km/h | Indoor - up to 30 km/h | | |
+| 7 | R | 0,2 m | 0,2 m | 99 % | 1 s | Indoor and outdoor (rural, urban, dense urban) up to 30 km/h
Relative positioning is between two UEs within 10 m of each other or between one UE and 5G positioning nodes within 10 m of each other (note 3) | | | | |
+
+NOTE 1: The objective for the vertical positioning requirement is to determine the floor for indoor use cases and to distinguish between superposed tracks for road and rail use cases (e.g. bridges).
+
+NOTE 2: Indoor includes location inside buildings such as offices, hospital, industrial buildings.
+
+NOTE 3: 5G positioning nodes are infrastructure equipment deployed in the service area to enhance positioning capabilities (e.g. beacons deployed on the perimeter of a rendezvous area or on the side of a warehouse).
+
+### 7.3.2.3 Other performance requirements
+
+The 5G system shall be able to provide the 5G positioning services with a TTFF less than 30 s and, for some 5G positioning services, shall support mechanisms to provide a TTFF less than 10 s.
+
+NOTE 1: In some services, a TTFF of less than 10s can only be achievable at the expense of a relaxation of some other performances (e.g. horizontal accuracy can be 1 m or 3 m after 10 s TTFF, and reach a steady state accuracy of 0,3 m after 30 s).
+
+The 5G system shall support a mechanism to determine the UE's velocity with a positioning service availability of 99%, an accuracy better than 0,5 m/s for the speed and an accuracy better than 5 degree for the 3-Dimension direction of travel.
+
+The 5G system shall support a mechanism to determine the UE's heading with an accuracy better than 30 degrees (0,54 rad) and a positioning service availability of 99,9 % for static users and with an accuracy better than 10 degrees (0,17 rad) and a positioning service availability of 99 % for users up to 10 km/h.
+
+For power consumption aspects for various usage scenarios see TS 22.104 [21]
+
+Low power high accuracy positioning use cases and example scenarios for Industrial IoT devices can be found in 3GPP TS 22.104 [21].
+
+## 7.4 KPIs for a 5G system with satellite access
+
+### 7.4.1 Description
+
+Satellite access networks are based on infrastructures integrated on a minimum of satellites that can be placed in either GEO, MEO or LEO.
+
+The propagation delay via satellite associated with these orbit ranges can be summarized in Table 7.4.1-1:
+
+**Table 7.4.1-1: Propagation delay via satellite**
+
+| | UE to serving satellite propagation delay [ms] [NOTE 1] | | UE to ground max propagation delay [ms] [NOTE 2] |
+|-----|---------------------------------------------------------|-----|--------------------------------------------------|
+| | Min | Max | |
+| LEO | 3 | 15 | 30 |
+| MEO | 27 | 43 | 90 |
+| GEO | 120 | 140 | 280 |
+
+NOTE1: The serving satellite provides the satellite radio link to the UE
+NOTE2: delay between UE and ground station via satellite link; Inter satellite links are not considered
+
+### 7.4.2 Requirements
+
+A 5G system providing service with satellite access shall be able to support GEO based satellite access with up to 285 ms end-to-end latency.
+
+NOTE 1: 5 ms network latency is assumed and added to satellite one-way delay.
+
+A 5G system providing service with satellite access shall be able to support MEO based satellite access with up to 95 ms end-to-end latency.
+
+NOTE 2: 5 ms network latency is assumed and added to satellite one-way delay.
+
+A 5G system providing service with satellite access shall be able to support LEO based satellite access with up to 35 ms end-to-end latency.
+
+NOTE 3: 5 ms network latency is assumed and added to satellite one-way delay.
+
+A 5G system shall support negotiation on quality of service taking into account latency penalty to optimise the QoE for UE.
+
+The 5G system with satellite access shall support high uplink data rates for 5G satellite UEs.
+
+The 5G system with satellite access shall support high downlink data rates for 5G satellite UEs.
+
+The 5G system with satellite access shall support communication service availabilities of at least 99,99%.
+
+**Table 7.4.2-1: Performance requirements for satellite access**
+
+| Scenario | Experienced data rate (DL) | Experienced data rate (UL) | Area traffic capacity (DL) (note 1) | Area traffic capacity (UL) (note 1) | Overall user density | Activity factor | UE speed | UE type |
+|---------------------------------|----------------------------|----------------------------|-------------------------------------|-------------------------------------|-----------------------|-----------------|---------------------------------------|---------------------------------------|
+| Pedestrian (note 2) | [1] Mbit/s | [100] kbit/s | 1,5 Mbit/s/km 2 | 150 kbit/s/km 2 | [100]/km 2 | [1,5] % | Pedestrian | Handheld |
+| Public safety | [3,5] Mbit/ss | [3,5] Mbit/s | TBD | TBD | TBD | N/A | 100 km/h | Handheld |
+| Vehicular connectivity (note 3) | 50 Mbit/s | 25 Mbit/s | TBD | TBD | TBD | 50 % | Up to 250 km/h | Vehicle mounted |
+| Airplanes connectivity (note 4) | 360 Mbit/s/ plane | 180 Mbit/s/ plane | TBD | TBD | TBD | N/A | Up to 1000 km/h | Airplane mounted |
+| Stationary | 50 Mbit/s | 25 Mbit/s | TBD | TBD | TBD | N/A | Stationary | Building mounted |
+| Video surveillance (note 4a) | [0,5] Mbit/s | [3] Mbit/s | TBD | TBD | TBD | N/A | Up to 120km/h or stationary (note 4b) | Vehicle mounted or fixed installation |
+| Narrowband IoT connectivity | [2] kbit/s | [10] kbit/s | 8 kbit/s/km 2 | 40 kbit/s/km 2 | [400]/km 2 | [1] % | [Up to 100 km/h] | IoT |
+
+Note 1: Area capacity is averaged over a satellite beam.
+
+Note 2: Data rates based on Extreme long-range coverage target values in clause 6.17.2. User density based on rural area in Table 7.1-1.
+
+Note 3: Based on Table 7.1-1
+
+Note 4: Based on an assumption of 120 users per plane 15/7.5 Mbit/s data rate and 20 % activity factor per user
+
+Note 4a: Refer to video surveillance data transmitted (in UL) from a UE on the ground (e.g. picture or video from a camera) using satellite NG-RAN to connect to 5GC, and video surveillance-related configuration or control data sent (in DL) to the UE/device. 0.5 Mbit/s for DL experienced data rate is based on MAVLINK protocol that is widely used for UAV control. 3 Mbit/s for UL experienced data rate is based on the assumed sum from 2.5 Mbit/s for video streaming and 0.5 Mbit/s for data transmission.
+
+Note 4b: Up to 120km/h applies to vehicle mounted while stationary applies to fixed installation.
+
+Note 5: All the values in this table are targeted values and not strict requirements.
+
+Note 6: Performance requirements for all the values in this table should be analyzed independently for each scenario.
+
+## 7.5 High-availability IoT traffic
+
+### 7.5.1 Description
+
+Several scenarios require the support of highly reliable machine type communication such as those, typically (but not restricted to) related to medical monitoring. They involve different deployment areas, different device speeds and densities and require a high-availability communication service to transfer a low data rate uplink data stream from one or several devices to an application.
+
+Their related performance requirements can be found in table 7.5.2-1.
+
+## 7.5.2 Requirements
+
+Table 7.5.2-1: Performance requirements for highly reliable machine type communication
+
+| Profile | Characteristic parameter | | | | | Influence quantity | | | | | |
+|-----------------------------|-------------------------------------------------------|---------------------------------------------------------------|-----------------------------|------------|-----------|---------------------|-------------------|-------------------|-----------------|--------------------------------------------|--------------------------------------------------------------|
+| | Communication service availability: target value in % | Communication service reliability (Mean Time Between Failure) | End-to-end latency: maximum | Bit rate | Direction | Message Size [byte] | Transfer Interval | Survival Time | UE speed (km/h) | # of UEs connection | Service Area |
+| Medical monitoring (note 2) | > 99,9999 | <1 year (>> 1 month) | < 100 ms | < 1 Mbit/s | Uplink | ~ 1000 | 50 ms | Transfer Interval | < 500 | 10/km 2 to 1000/km 2 | Country wide including rural areas and deep indoor. (note 1) |
+
+NOTE 1: "deep indoor" term is meant to be places like e.g. elevators, building's basement, underground parking lot, ...
+
+NOTE 2: These performance requirements aim energy-efficient transmissions performed using a device powered with a 3.3V battery of capacity < 1000 mAh that can last at least 1 month without recharging and whereby the peak current for transmit operations stays below 50 mA.
+
+## 7.6 High data rate and low latency
+
+### 7.6.1 AR/VR
+
+Audio-visual interaction is characterised by a human being interacting with the environment or people, or controlling a UE, and relying on audio-visual feedback. In the use cases like VR and interactive conversation the latency requirements include the latencies at the application layer (e.g. codecs), which could be specified outside of 3GPP.
+
+To support VR environments with low motion-to-photon capabilities, the 5G system shall support:
+
+- motion-to-photon latency in the range of 7 ms to 15ms while maintaining the required resolution of up to 8k giving user data rate of up to [1Gbit/s] and
+- motion-to-sound delay of [ $< 20$ ms].
+
+NOTE: The motion-to-photon latency is defined as the latency between the physical movement of a user's head and the updated picture in the VR headset. The motion-to-sound latency is the latency between the physical movement of a user's head and updated sound waves from a head mounted speaker reaching their ears.
+
+To support interactive task completion during voice conversation, the 5G system shall support low-delay speech coding for interactive conversational services (100 ms, one-way mouth-to-ear).
+
+Due to the separate handling of the audio and video component, the 5G system will have to cater for the VR audio-video synchronisation in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization). To support VR environments the 5G system shall support audio-video synchronisation thresholds:
+
+- in the range of [125 ms to 5 ms] for audio delayed and
+- in the range of [45 ms to 5 ms] for audio advanced.
+
+When it comes to implementation of applications containing AR/VR components, the requirements on the 5G network could depend on architectural choices implementing these services. Note 3 in table 7.1-1 above gives an example on such dependences for a VR application in a 5G system. Table 7.6.1-1 below illustrates additional use cases and provides more corresponding requirements on the 5G system.
+
+- Cloud/Edge/Split Rendering – Cloud/Edge/Split Rendering is characterised by the transition and exchange of the rendering data between the rendering server and device.
+- Gaming or Training Data Exchanging – This use case is characterised by the exchange of the gaming or training service data between two 5G connected AR/VR devices.
+- Consume VR content via tethered VR headset – This use case involves a tethered VR headset receiving VR content via a connected UE; this approach alleviates some of the computation complexity required at the VR headset, by allowing some or all decoding functionality to run locally at the connected UE. The requirements in the table below refer to the direct wireless link between the tethered VR headset and the corresponding connected UE.
+
+**Table 7.6.1-1 KPI Table for additional high data rate and low latency service**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | |
+|------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|--------------------|--------------------------|--------------------------------------------------------------------------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | # of UEs | UE Speed | Service Area (note 2) |
+| Cloud/Edge/Split Rendering (note 1) | 5 ms (i.e. UL+DL between UE and the interface to data network) (note 4) | 0,1 to [1] Gbit/s supporting visual content (e.g. VR based or high definition video) with 4K, 8K resolution and up to 120 frames per second content. | 99,99 % in uplink and 99,9 % in downlink (note 4) | - | Stationary or Pedestrian | Countrywide |
+| Gaming or Interactive Data Exchanging (note 3) | 10ms (note 4) | 0,1 to [1] Gbit/s supporting visual content (e.g. VR based or high definition video) with 4K, 8K resolution and up to 120 frames per second content. | 99,99 % (note 4) | ≤ [10] | Stationary or Pedestrian | 20 m x 10 m; in one vehicle (up to 120 km/h) and in one train (up to 500 km/h) |
+| Consumption of VR content via tethered VR headset (note 6) | [5 to 10] ms (note 5) | 0,1 to [10] Gbit/s (note 5) | [99,99 %] | - | Stationary or Pedestrian | – |
+
+NOTE 1: Unless otherwise specified, all communication via wireless link is between UEs and network node (UE to network node and/or network node to UE) rather than direct wireless links (UE to UE).
+NOTE 2: Length x width (x height).
+NOTE 3: Communication includes direct wireless links (UE to UE).
+NOTE 4: Latency and reliability KPIs can vary based on specific use case/architecture, e.g. for cloud/edge/split rendering, and can be represented by a range of values.
+NOTE 5: The decoding capability in the VR headset and the encoding/decoding complexity/time of the stream will set the required bit rate and latency over the direct wireless link between the tethered VR headset and its connected UE, bit rate from 100 Mbit/s to [10] Gbit/s and latency from 5 ms to 10 ms.
+NOTE 6: The performance requirement is valid for the direct wireless link between the tethered VR headset and its connected UE.
+
+## 7.7 KPIs for UE to network relaying in 5G system
+
+In several scenarios, it can be beneficial to relay communication between one UE and the network via one or more other UEs. The functional requirements related to relaying can be found in clause 6.9.2. Performance requirements for relaying in different scenarios can be found in table 7.7-1.
+
+**Table 7.7-1: Key Performance for UE to network relaying**
+
+| Scenario | Max. data rate (DL) | Max. data rate (UL) | End-to-end latency (note 7) | Area traffic capacity (DL) | Area traffic capacity (UL) | Area user density | Area | Range of a single hop (note 8) | Estimated number of hops |
+|--------------------------|---------------------|---------------------|-----------------------------|------------------------------------|------------------------------------|-------------------------------------|--------------------------|-------------------------------------|--------------------------|
+| InHome Scenario (note 1) | 1 Gbit/s | 500 Mbit/s | 10 ms | 5 Gbit/s /home | 2 Gbit/s /home | 50 devices /house | 10 m x 10m – 3 floors | 10 m indoor | 2 to 3 |
+| Factory Sensors (note 2) | 100 kbit/s | 5 Mbit/s | 50 ms to 1 s | 1 Gbit/s /factory | 50 Gbit/s /factory | 10000 devices /factory | 100 m x 100 m | 30 m indoor / metallic | 2 to 3 |
+| Smart Metering (note 3) | 100 bytes / 15 mins | 100 bytes / 15 mins | 10 s | 200 x 100 bytes / 15 mins /hectare | 200 x 100 bytes / 15 mins /hectare | 200 devices /hectare | 100 m x 100 m | > 100 m indoor / deep indoor | 2 to 5 |
+| Containers (note 4) | 100 bytes / 15 mins | 100 bytes / 15 mins | 10 s | 15000 x 100 bytes / 15 mins /ship | 15000 x 100 bytes / 15 mins /ship | 15000 containers /ship | 400 m x 60 m x 40 m | > 100 m indoor / outdoor / metallic | 3 to 9 |
+| Freight Wagons | 100 bytes / 15 mins | 100 bytes / 15 mins | 10 s | 200 x 100 bytes / 15 mins /train | 200 x 100 bytes / 15 mins /train | 120 wagons /train | 1 km | > 100 m outdoor / tunnel | 10 to 15 |
+| Public Safety (note 5) | 12 Mbit/s | 12 Mbit/s | 30 ms | 20 Mbit/s /building | 40 Mbit/s /building | 30 devices /building | 100 m x 100 m – 3 floors | > 50 m indoor (floor or stairwell) | 2 to 4 |
+| Wearables (note 6) | 10 Mbit/s | 10 Mbit/s | 10 ms | 20 Mbit/s per 100 m 2 | 20 Mbit/s per 100 m 2 | 10 wearables per 100 m 2 | 10 m x 10 m | 10 m indoor / outdoor | 1 to 2 |
+
+NOTE 1: Area traffic capacity is determined by high bandwidth consuming devices (e.g. ultra HD TVs, VR headsets), the number of devices has been calculated assuming a family of 4 members.
+
+NOTE 2: Highest data rate assumes audio sensors with sampling rate of 192 kHz and 24 bits sample size.
+
+NOTE 3: Three meters (gas, water, electricity) per house, medium density of 50 to 70 houses per hectare.
+
+NOTE 4: A large containership with a mix of 20 foot and 40 foot containers is assumed.
+
+NOTE 5: A mix of MCPTT, MCVideo, and MCData is assumed. Average 3 devices per firefighter / police officer, of which one video device. Area traffic based on 1080 p, 60 fps is 12 Mbit/s video, with an activity factor of 30% in uplink (30% of devices transmit simultaneously at high bitrate) and 15% in downlink.
+
+NOTE 6: Communication for wearables is relayed via a UE. This relay UE can use a further relay UE.
+
+NOTE 7: End-to-end latency implies that all hops are included.
+
+NOTE 8: 'Metallic' implies an environment with a lot of metal obstructions (e.g. machinery, containers). 'Deep indoor' implies that there can be concrete walls / floors between the devices.
+
+NOTE 9: All the values in this table are example values and not strict requirements.
+
+## 7.8 KPIs for 5G Timing Resiliency
+
+The 5G system shall be able to support a holdover time capability with timing resiliency performance requirements defined in table 7.8-1.
+
+**Table 7.8-1: Timing resiliency performance requirements for 5G System**
+
+| Use case | Holdover time (note 3) | Sync target | Sync accuracy | Service area | Mobility | Remarks |
+|-------------------------|------------------------|--------------|----------------------------|----------------------|----------|---------------------------------------------------------------------------|
+| Power grid (5G network) | Up to 24 hour | UTC (note 1) | <250 ns to 1000 ns (note2) | < 20 km 2 | low | When 5G System provides direct PTP Grandmaster capability to sub-stations |
+
+| | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------|----------------------------|----------------------|-----|---------------------------------------------------------------------------------------------------------------|
+| Power grid (time synchronization device) | >5 s | UTC (note 1) | <250 ns to 1000 ns (note2) | < 20 km 2 | low | When 5G sync modem is integrated into PTP grandmaster solution (with 24h holdover capability at sub-stations) |
+| NOTE 1: A different synchronization target is acceptable as long as the offset is preconfigured when an alternatively sourced time differs from GNSS. In this case, a 5G end device will provide PPS output which can be used for measuring the difference. | | | | | | |
+| NOTE 2: Different accuracy measurements are based on different configurations needed to support the underlying requirements from IEC 61850-9-3 [32]. The range is between 250 ns and 1000 ns. The actual requirement depends on the specific deployment. | | | | | | |
+| NOTE 3: This requirement will vary based on deployment options. | | | | | | |
+
+**Table 7.8-2: Timing resiliency accuracy KPIs for members or participants of a trading venue [35]**
+
+| Type of trading activity | Maximum divergence from UTC | Granularity of the timestamp (note 1) |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------------|
+| Activity using high frequency algorithmic trading technique | 100 µs | ≤1 µs |
+| Activity on voice trading systems | 1 s | ≤1 s |
+| Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading | 1 s | ≤1 s |
+| Activity of concluding negotiated transactions | 1 s | ≤1 s |
+| Any other trading activity | 1 ms | ≤1 ms |
+| NOTE 1: Only relevant for the case where the time synchronization assists in configuring the required granularity for the timestamp (for direct use), otherwise it will be configured separately as part of the financial transaction timestamp process. | | |
+
+## 7.9 KPIs for ranging based services
+
+In several scenarios, it can be beneficial to determine the distance between two UEs and/or the direction of one UE from the other one via direct communication connection. The functional requirements related to ranging based services can be found in clause 6.37. Performance requirements for ranging based services in different scenarios can be found in table 7.9-1.
+
+Key performance indicators and key attributes for ranging are defined as follows:
+
+- **Ranging accuracy:** describes the absolute value of the deviation of the measured distance and/or direction between two UEs to the true distance and/or direction value.
+- **Confidence level:** describes the percentage of all the possible measured distance and/or direction that can be expected to include the true distance and/or direction considering the ranging accuracy.
+- **Effective ranging distance:** the largest distance between the UE who initiates the ranging and target UEs in the ranging operation.
+- **Line-of-sight (LOS) Environment:** the environment between the UE who initiates the ranging and target UEs, such as LOS and non-LOS (NLOS).
+- **Coverage:** type of radio coverage conditions of the UEs who are involved in ranging, such as in coverage (IC), partial coverage (PC) and out of coverage (OOC). See also figure 6.37.1-1.
+
+NOTE: If using licensed spectrum, ranging is only permitted in network coverage under the full control of the operator who provides the coverage, except for public safety networks with dedicated spectrum where ranging might be allowed out of coverage or in partial coverage as well.
+
+- **Relative UE velocity:** the target UE can be either static or mobile relative to the UE who initiates the ranging. In the latter, the attribute shall also provide some elements about its motion, e.g. maximum speed, trajectory.
+- **Availability:** percentage value of the amount of time when a ranging system is able to provide the required ranging-related data within the performance targets or requirements divided by the amount of time the system is expected to provide the ranging service in a targeted service area.
+- **Latency:** time elapsed between the event that triggers the determination of the ranging-related data and the availability of the ranging-related data at the ranging system interface.
+- **Ranging interval:** time difference between two consecutive ranging operations.
+
+**Table 7.9-1: Performance requirements for ranging based services**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+|----------------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|----------------------------|-----------|----------|-----------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | | | | | | | |
+| Smart TV Remoter | 10cm up to 3 meter separation | ±2° horizontal direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-60°) to (+60°);
±2° Elevation direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-45°) to (+45°) | 99 % | 50ms | 10m | IC/PC/OOC | LOS | Static/Moving (<1m/s) | 50ms | - | - |
+| Picture and video sharing based on Ranging results | 10cm | 2° | 99 % | 50ms | 10m | IC/PC/OOC | LOS | Static/Moving (<1m/s) | 50ms | - | - |
+| Distance based smart device control | 10cm | - | 99 % | 100ms | 20m | IC/PC/OOC | LOS | Static/Moving (<1m/s) | 50ms | 20 | - |
+
+| | | | | | | | | | | | |
+|---------------------------------------------------|-------|----------|------|-------|------|-----------|-----|------------------------------|-------|----|----------------------------------------------------|
+| Smart Vehicle Key | 10 cm | - | 99 % | 50ms | 30m | IC/PC/OOC | LOS | Static/
Moving
(<2m/s) | 25ms | - | 50UEs/
(10 4 m 2 ) |
+| Touchless Self-
checkout Machine
Control | 10cm | - | 99 % | 150ms | 1m | IC/PC/OOC | LOS | Static/
Moving
(<1m/s) | 100ms | - | = |
+| Hands Free Access | 10cm | - | 99 % | 500ms | 10 m | IC/PC/OOC | LOS | Static/
Moving
(1 m/s) | 50ms | - | 20
UEs/3.14*100
m 2 |
+| Smart Transportation
Metro/Bus Validation | 10cm | - | 99 % | - | 2m | IC/PC/OOC | LOS | Static/
Moving
(3km/h) | 50ms | 20 | 100 in the area
of 8 m 2 |
+| Ranging of UE's in
front of vending
machine | 20cm | 10° | - | 1s | 5m | IC/PC/OOC | LOS | Static/
Moving
(<1m/s) | 50ms | - | 10 |
+| Finding Items in a
supermarket | 50 cm | 5 degree | 95 % | - | 100m | IC/PC/OOC | LOS | Static/
Moving
(<1m/s) | 250ms | - | 100 UEs/
(3.14*10 4 m 2 ) |
+
+| | | | | | | | | | | | |
+|---------------------------------------------------------|-------|----------|------|---|----------|-----------|-----|------------------------------------|----|-----|-----------------------------------------------|
+| distance based intelligent perception for public safety | 50cm | - | 99 % | - | 20m | IC/PC/OOC | LOS | Static/
Moving
(<20km/h ) | - | 100 | - |
+| Long Distance Search | 20m | 5° | 99 % | - | 100m-1km | IC/PC/OOC | LOS | Static/
Moving
(up to 10m/s) | 5s | - | - |
+| Long range approximate location | [10m] | ±[12.5°] | 99 % | - | 500m | IC/PC/OOC | LOS | Static/
Moving
(<10m/s) | - | 1 | [50]UEs/
(10 4 m 2 ) |
+
+## 7.10 KPIs for AI/ML model transfer in 5GS
+
+The 5G system shall support split AI/ML inference between UE and Network Server/Application function with performance requirements as given in Table 7.10-1.
+
+**Table 7.10-1 KPI Table of split AI/ML inference between UE and Network Server/Application function**
+
+| Uplink KPI | | | | | Downlink KPI | | | | | Remarks |
+|-----------------------------------|-----------------------|--------------|------------------------------------|-------------|-----------------------------------|-----------------------|-----------------|-------------|--|-------------------------------|
+| Max allowed UL end-to-end latency | Experienced data rate | Payload size | Communication service availability | Reliability | Max allowed DL end-to-end latency | Experienced data rate | Payload size | Reliability | | |
+| 15 ms | 144 Mbit/s | 0.27 MByte | 99.999 % | 99.9 % | | | | 99.999 % | | Split AI/ML image recognition |
+| 100 ms | 1.5 Mbit/s | | | | 100 ms | 150 Mbit/s | 1.5 MByte/frame | | | Enhanced media recognition |
+| | 4.7 Mbit/s | | | | 12 ms | 320 Mbit/s | 40 kByte | | | Split control for robotics |
+
+NOTE 1: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
+
+The 5G system shall support AI/ML model downloading with performance requirements as given in Table 7.10-2.
+
+**Table 7.10-2 KPI Table of AI/ML model downloading**
+
+| Max allowed DL end-to-end latency | Experienced data rate (DL) | Model size | Communication service availability | Reliability | User density | # of downloaded AI/ML models | Remarks |
+|-----------------------------------|----------------------------|------------|------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------------------------|--------------------------------------------|----------------------------------------------------|
+| 1s | 1.1Gbit/s | 138MByte | 99.999 % | 99.9% for data transmission of model weight factors; 99.999% for data transmission of model topology | | | AI/ML model distribution for image recognition |
+| 1s | 640Mbit/s | 80MByte | 99.999 % | | | | AI/ML model distribution for speech recognition |
+| 1s | 512Mbit/s(see note 1) | 64MByte | | | | Parallel download of up to 50 AI/ML models | Real time media editing with on-board AI inference |
+| 1s | | 536MByte | | | up to 5000~10000/km 2 in an urban area | | AI model management as a Service |
+| 1s | 22Mbit/s | 2.4MByte | 99.999 % | | | | AI/ML based Automotive Networked Systems |
+| 1s | | 500MByte | | | | | Shared AI/ML model monitoring |
+| 3s | 450Mbit/s | 170MByte | | | | | Media quality enhancement |
+
+NOTE 1: 512Mbit/s concerns AI/ML models having a payload size below 64 MB. TBD for larger payload sizes.
+NOTE 2: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
+
+The 5G system shall support Federated Learning between UE and Network Server/Application function with performance requirements as given in Table 7.10-3.
+
+**Table 7.10-3: KPI Table of Federated Learning between UE and Network Server/Application function**
+
+| Max allowed DL or UL end-to-end latency | DL experienced data rate | UL experienced data rate | DL packet size | UL packet size | Communication service availability | Remarks |
+|-----------------------------------------|--------------------------|--------------------------|----------------|----------------|------------------------------------|---------------------------------------------------------------------|
+| 1s | 1.0Gbit/s | 1.0Gbit/s | 132MByte | 132MByte | | Uncompressed Federated Learning for image recognition |
+| 1s | 80.88Mbit/s | 80.88Mbit/s | 10Mbyte | 10Mbyte | TBD | Compressed Federated Learning for image/video processing |
+| 1s | TBD | TBD | 10MByte | 10MByte | | Data Transfer Disturbance in Multi-agent multi-device ML Operations |
+
+## 7.11 KPIs for tactile and multi-modal communication service
+
+The 5G system shall support tactile and multi-modal communication services with the following KPIs.
+
+**Table 7.11-1: Multi-modal communication service performance requirements**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | Remarks |
+|-------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------|------------------------------------------------------------------------------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | UE Speed | Service Area | |
+| Immersive multi-modal VR (UL: device → application sever) | 5 ms (note 2) | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.9% (without haptic compression encoding)
99.999% (with haptic compression encoding) [40] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
More DoFs can be supported by the haptic device | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Haptic feedback |
+| | 5 ms | < 1Mbit/s | 99.99% [40] | 1500 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Sensing information e.g. position and view information generated by the VR glasses |
+| Immersive multi-modal VR (DL: application sever → device) | 10 ms (note1) | 1-100 Mbit/s | 99.9% [40] | 1500 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Video |
+| | 10 ms | 5-512 kbit/s | 99.9% [40] | 50 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Audio |
+| | 5 ms (note 2) | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.9% (without haptic compression encoding)
99.999% (with haptic compression encoding) [40] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Haptic feedback |
+| Remote control robot | 1-20ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.999% [40] | 2-8 (1 DoF) | high-dynamic (≤ 50 km/h) | ≤ 1 km 2 | Haptic feedback |
+| | 20-100ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.999% [40] | 2-8 (1 DoF) | Stationary or Pedestrian | ≤ 1 km 2 | Haptic feedback |
+| | 5 ms | 1-100 Mbit/s | 99.999% [40] | 1500 | Stationary or Pedestrian | ≤ 1 km 2 | Video |
+| | 5 ms | 5-512 kbit/s | 99.9% [40] | 50-100 | Stationary or Pedestrian | ≤ 1 km 2 | Audio |
+| | 5 ms | < 1Mbit/s | 99.999% [40] | - | Stationary or Pedestrian | ≤ 1 km 2 | Sensor information |
+| Skillset sharing low-dynamic robotics (including teleoperation ) Controller to controllee | 5-10ms | 0.8 - 200 kbit/s (with compression) | 99.999% [40][45] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | Stationary or Pedestrian | 100 km 2 | Haptic (position, velocity) |
+
+| | | | | | | | |
+|---------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------|---------------------------------|-----------------------------|
+| Skillset sharing low-dynamic robotics (including teleoperation )
Controlee to controller | 5-10ms | 0.8 - 200 kbit/s (with compression) | 99,999% [40][45] | 1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800 | Stationary or Pedestrian | 100 km 2 | Haptic feedback |
+| | 10ms | 1-100 Mbit/s | 99,999% [40] [45] | 1500 | Stationary or Pedestrian | 100 km 2 | Video |
+| | 10ms | 5-512 kbit/s | 99,9% [40] [45] | 50 | Stationary or Pedestrian | 100 km 2 | Audio |
+| Skillset sharing Highly dynamic/ mobile robotics
Controller to controlee | 1-5ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99,999% (with compression)
99,9% (w/o compression) [40] [45] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | high-dynamic | 4 km 2 | Haptic (position, velocity) |
+| Skillset sharing Highly dynamic/ mobile robotics
Controlee to controller | 1-5ms | 0.8 - 200 kbit/s | 99,999% (with compression)
99,9% (w/o compression) [40] [45] | 1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800 | high-dynamic | 4 km 2 | Haptic feedback |
+| | 1-10ms | 1-10 Mbit/s | 99,999% [40] [45] | 2000-4000 | high-dynamic | 4 km 2 | Video |
+| | 1-10ms | 100-500 kbit/s | 99,9% [40] [45] | 100 | high-dynamic | 4 km 2 | Audio |
+| Immersive multi-modal navigation applications
Remote Site → Local Site (DL) | 50 ms [39] | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.999 % [40] | 1 DoF: 2 to 8
10 DoF: 20 to 80
100 DoF: 200 to 800 | Stationary or Pedestrian | ≤ 100 km 2 ( note 5) | Haptic feedback |
+| | <400 ms [39] | 1-100 Mbit/s | 99.999 % [40] | 1500 | Stationary/ or Pedestrian, | ≤ 100 km 2 (note 5) | Video |
+| | <150 ms [39] | 5-512 kbit/s | 99.9 % [40] | 50 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | Audio |
+| | <300 ms | 600 Mbit/s | 99.9 % [40] | 1500 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | VR |
+| Immersive multi-modal navigation applications
Local Site → Remote Site (UL) | <300 ms | 12 kbit/s [26] | 99.999 % [40] | 1500 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | Biometric / Affective |
+| | <400 ms [39] | 1-100 Mbit/s | 99.999 % [40] | 1500 | Workers:
Stationary/ or Pedestrian,
UAV: [30-300mph] | ≤ 100 km 2 (note 5) | Video |
+| | <150 ms [39] | 5-512 kbit/s | 99.9 % [40] | 50 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | Audio |
+| | <300 ms | 600 Mbit/s | 99.9 % [40] | 1500 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | VR |
+
+NOTE 1: Motion-to-photon delay (the time difference between the user's motion and corresponding change of the video image on display) is less than 20 ms, and the communication latency for transferring the packets of one audio-visual media is less than 10 ms, e.g. the packets corresponding to one video/audio frame are transferred to the devices within 10 ms.
+
+NOTE 2: According to IEEE 1918.1 [40] as for haptic feedback, the latency is less than 25 ms for accurately completing haptic operations. As rendering and hardware introduce some delay, the communication delay for haptic modality can be reasonably less than 5 ms, i.e. the packets related to one haptic feedback are transferred to the devices within 10 ms.
+
+NOTE 3: Haptic feedback is typically haptic signal, such as force level, torque level, vibration and texture.
+
+NOTE 4: The latency requirements are expected to be satisfied even when multimodal communication for skillset sharing is via indirect network connection (i.e., relayed by one UE to network relay).
+
+NOTE 5: In practice, the service area depends on the actual deployment. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
+
+---
+
+## 8 Security
+
+### 8.1 Description
+
+IoT introduces new UEs with different life cycles, including IoT devices with no user interface (e.g. embedded sensors), long life spans during which an IoT device can change ownership several times (e.g. consumer goods), and which cannot be pre-provisioned (e.g. consumer goods). These drive a need for secure mechanisms to dynamically establish or refresh credentials and subscriptions. New access technologies, including licensed and unlicensed, 3GPP and non-3GPP, drive a need for access-independent security that is seamlessly available while the IoT device is active. High-end smartphones, UAVs, and factory automation drive a need for protection against theft and fraud. A high level of 5G security is essential for critical communication, e.g. in industrial automation, industrial IoT, and the Smart Grid. Expansion into enterprise, vehicular, medical, and public safety markets drive a need for increased end user privacy protection. 5G security addresses all of these new needs while continuing to provide security consistent with prior 3GPP systems.
+
+### 8.2 General
+
+The 5G system shall support a secure mechanism to store cached data.
+
+The 5G system shall support a secure mechanism to access a content caching application.
+
+The 5G system shall support a secure mechanism to access a service or an application in an operator's Service Hosting Environment.
+
+The 5G system shall enable support of an access-independent security framework.
+
+The 5G system shall support a mechanism for the operator to authorize subscribers of other PLMNs to receive temporary service (e.g. mission critical services).
+
+The 5G system shall be able to provide temporary service for authorized users without access to their home network (e.g. IOPS, mission critical services).
+
+The 5G system shall allow the operator to authorize a third-party to create, modify and delete network slices, subject to an agreement between the third-party and the network operator.
+
+Based on operator policy, a 5G network shall provide suitable means to allow a trusted and authorized third-party to create and modify network slices used for the third-party with appropriate security policies (e.g. user data privacy handling, slices isolation, enhanced logging).
+
+The 5G system shall support a secure mechanism to protect relayed data from being intercepted by a relay UE.
+
+Subject to HPLMN policy as well as its service and operational needs, any USIM able to access EPS instead of a 5G USIM may be used to authenticate a user in a 5G system to access supported services according to the user subscription.
+
+The 5G system shall provide integrity protection and confidentiality for communications between authorized UEs using a 5G LAN-type service.
+
+The 5G LAN-VN shall be able to verify the identity of a UE requesting to join a specific private communication.
+
+The 5G system shall provide suitable means to allow the use of a trusted third-party provided encryption between any UE served by a private slice and a core network entity in that private slice.
+
+The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a private slice and a core network entity in that private slice.
+
+The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a non-public network and a core network entity in that non-public network.
+
+## 8.3 Authentication
+
+The 5G system shall support an efficient means to authenticate a user to an IoT device (e.g. biometrics).
+
+The 5G system shall be able to support authentication over a non-3GPP access technology using 3GPP credentials.
+
+The 5G system shall support operator-controlled alternative authentication methods (i.e. alternative to AKA) with different types of credentials for network access for IoT devices in isolated deployment scenarios (e.g. for industrial automation).
+
+The 5G system shall support a suitable framework (e.g. EAP) allowing alternative (e.g. to AKA) authentication methods with non-3GPP identities and credentials to be used for UE network access authentication in non-public networks.
+
+NOTE: Non-public networks can use 3GPP authentication methods, identities, and credentials for a UE to access network. Non-public networks are also allowed to utilize non-AKA based authentication methods such as provided by the EAP framework, for which the credentials can be stored in the ME.
+
+Subject to an agreement between an MNO and a 3rd party, the 5G system shall support a mechanism for the PLMN to authenticate and authorize UEs for access to both a hosted non-public network and private slice(s) of the PLMN associated with the hosted non-public network.
+
+The 5G network shall support a 3GPP supported mechanism to authenticate legacy non-3GPP devices for 5G LAN-VN access.
+
+The 5G system shall support a mechanism for the non-public network to authenticate and authorize UEs for access to network slices of that non-public network.
+
+The 5G system shall enable an NPN to be able to request a third-party service provider to perform NPN access network authentication of a UE based on non-3GPP identities and credentials supplied by the third-party service provider.
+
+The 5G system shall enable an NPN to be able to request a PLMN to perform NPN access network authentication of a UE based on 3GPP identities and credentials supplied by the PLMN.
+
+## 8.4 Authorization
+
+The 5G system shall allow the operator to authorize an IoT device to use one or more 5G system features that are restricted to IoT devices.
+
+The 5G system shall allow the operator to authorize /de-authorize UEs for using 5G LAN-type service.
+
+NOTE: When a UE is de-authorized from using 5G LAN-type service, it is removed from all 5G LAN-VNs.
+
+Based on operator policy, before establishing a direct device connection using a non-3GPP access technology, IoT devices may use 3GPP credentials to determine if they are authorized to engage in direct device connection.
+
+Based on operator policy, the 5G system shall provide a means to verify whether a UE is authorized to use prioritized network access for a specific service.
+
+## 8.5 Identity management
+
+The 5G system shall provide a mechanism for an operator to allow access from a UE using a temporary identifier that hides its subscriber identity.
+
+The 5G system shall provide a mechanism for an operator to allow access from a UE connected in an indirect network connection using a temporary identifier that hides its subscriber identity.
+
+The HPLMN shall be able to associate a temporary identifier to a UE's subscriber identity.
+
+The 5G system shall be able to protect subscriber identity and other user identifying information from passive attacks.
+
+Subject to regional or national regulatory requirements, the 5G system shall be able to protect subscriber identity and other user identifying information from active attacks.
+
+The 5G system shall be able to allow the equipment identifier to be collected by legitimate entity regardless of UE's user interface, when required.
+
+The 5G system shall be able to support identification of subscriptions independently of identification of equipment.
+
+The 5G system shall support a secure mechanism to collect system information while ensuring end-user and application privacy (e.g. application level information is not to be related to an individual user identity or subscriber identity and UE information is not to be related to an individual subscriber identity).
+
+Subject to regional or national regulatory requirements, the 5G system shall be able to provide the 5G positioning services while ensuring the protection of the privacy of the UE's user or owner, including the respect of his consent to the positioning services.
+
+NOTE 1: this includes the ability for the 5G system to provide the positioning services on demand without having to track continuously the position of the involved UE.
+
+NOTE 2: the respect of the user's consent to some positioning services could abide by different rules in case of emergency (for example, rules that would also receive consent from the user, but well before the emergency occurs).
+
+For a private network using 5G technology, the 5G system shall support network access using identities, credentials, and authentication methods provided and managed by a third-party and supported by 3GPP.
+
+## 8.6 Regulatory
+
+The 5G system shall support regional or national regulatory requirements for all supported access networks.
+
+The 5G system shall support Lawful Interception, subject to regional or national regulatory requirements.
+
+A 5G satellite access network connected to 5G core networks in multiple countries shall be able to meet the corresponding regulatory requirements from these countries (e.g. Lawful Interception).
+
+A 5G system shall support regulatory requirements for 5G LAN-type services.
+
+## 8.7 Fraud protection
+
+Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to disable from normal operation of a UE reported as stolen.
+
+Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to re-enable a recovered stolen UE to normal operation.
+
+The 5G system shall be able to protect user location information from passive attacks.
+
+Subject to regional or national regulatory requirements, the 5G system shall be able to protect user location information from active attacks.
+
+Subject to regional or national regulatory requirements, the 5G system shall support mechanisms to protect the production of the user location information and user positioning-related data against tampering and spoofing.
+
+Subject to regional or national regulatory requirements, the 5G system shall support mechanisms to detect tampering and spoofing attempts on the production of the user location information and the user position-related data.
+
+## 8.8 Resource efficiency
+
+The 5G system shall minimize security signalling overhead without compromising the security level of the 3GPP system.
+
+The 5G system shall support an efficient secure mechanism to transmit the same data (e.g. service provisioning multiple sensors) to multiple UEs.
+
+## 8.9 Data security and privacy
+
+The 5G system shall support data integrity protection and confidentiality methods that serve URLLC, high data rates and energy constrained devices.
+
+The 5G system shall support a mechanism to verify the integrity of a message as well as the authenticity of the sender of the message.
+
+The 5G system shall support encryption for URLLC services within the requested end-to-end latency.
+
+Subject to regulatory requirements, the 5G system shall enable an MNO to provide end-to-end integrity protection, confidentiality, and protection against replay attacks between a UE and third-party application server, such that the 3GPP network is not able to intercept or modify the data transferred between a UE and third-party application server.
+
+Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support data integrity verification service to assure the integrity of the data exchanged between the 5G network and a third-party service provider.
+
+NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE.
+
+Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support confidentiality to prevent exposure of data exchanged between the 5G network and a third party service provider.
+
+NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE.
+
+## 8.10 5G Timing Resiliency
+
+The 5G system shall support a mechanism to verify authorization of a 3rd party application to use 5G timing resiliency.
+
+The 5G system shall support a mechanism to monitor and verify authenticity of the timing source, where supported by the time source.
+
+---
+
+## 9 Charging aspects
+
+### 9.1 General
+
+The following set of requirements complement the requirements listed in 3GPP TS 22.115 [11]. The requirements apply for both home and roaming cases.
+
+The 5G core network shall support collection of all charging information on either a network or a slice basis.
+
+The 5G core network shall support collection of charging information for alternative authentication mechanisms.
+
+The 5G core network shall support collection of charging information associated with each serving MNO when multi-network connectivity is used under the control of the home operator.
+
+The 5G core network shall support charging for services/applications in an operator's Service Hosting Environment.
+
+The 5G core network shall support charging for content delivered from a content caching application.
+
+The 5G core network shall support collection of charging information based on the access type (e.g. 3GPP, non-3GPP, satellite access).
+
+The 5G core network shall support collection of charging information based on the slice that the UE accesses.
+
+The 5G system shall be able to generate charging information regarding the used radio resources e.g. used frequency bands.
+
+The 5G core network shall support collection of charging information based on the capacity and performance metrics.
+
+In a 5G system with satellite access, charging call records associated with satellite access(es) shall include the location of the associated UE(s) with satellite access
+
+NOTE: The precision of the location of the UE can be based on the capabilities of the UE or of the network.
+
+The 5G system shall be able to support an indirect network connection even when the UE is in E-UTRAN or NG-RAN coverage.
+
+The 5G system shall be able to support mechanisms to differentiate charging information for traffic carried over satellite backhaul.
+
+For service function chaining (see clause 10) the collection of charging information associated to the use of service functions and the chain of service functions requested by third parties shall be supported.
+
+The 5G system shall be able to support collection of charging information for a group of UEs, e.g. UEs of a AI/ML FL group.
+
+## 9.2 5G LAN
+
+A 5G core network shall support collection of charging information for a 5G LAN-type service based on resource usage (e.g. licensed or unlicensed spectrum, QoS, applications).
+
+The 5G core network shall support collection of charging information for a 5G LAN-type service when a UE joins or leaves a specific private communication.
+
+The 5G core network shall support collection of charging information for a 5G LAN-type service for both home and roaming UEs based on the UE's HPLMN.
+
+## 9.3 5G Timing Resiliency
+
+The 5G system shall be able to collect charging information based on the timing source (e.g., the source in use, start and stop of source usage).
+
+The 5G system shall be able to collect charging information per UE for use of a timing source (e.g., start/stop time and source used by a UE, timing source used by UE, holdover capability).
+
+The 5G system shall be able to collect charging information on 5G system timing resiliency (e.g., resiliency KPIs, holdover capability, number of UEs using a certain timing source).
+
+The 5G system shall be able to collect charging information per application using 5G timing resiliency, including 3rd party application, (e.g., timing resiliency KPIs, holdover capability, number of UEs using a certain timing source).
+
+---
+
+Annex A (informative):
+Void
+
+Annex B (informative):
+Void
+
+---
+
+## Annex C (informative): Relation of communication service availability and reliability
+
+NOTE: The content of this annex was moved to annex F of TS 22.104 [21].
+
+---
+
+## Annex D (informative): Critical-communication use cases
+
+### D.1 Factory automation – motion control
+
+#### D.1.0 General
+
+Factory automation requires communications for closed-loop control applications. Examples for such applications are motion control of robots, machine tools, as well as packaging and printing machines. All other factory automation applications are addressed in Annex D.2.
+
+The corresponding industrial communication solutions are referred to as fieldbuses. The pertinent standard suite is IEC 61158. Note that clock synchronization is an integral part of fieldbuses that support motion control use cases.
+
+In motion control applications, a controller interacts with a large number of sensors and actuators (e.g. up to 100) that are integrated in a manufacturing unit. The resulting sensor/actuator density is often very high (up to 1 m-3). Many such manufacturing units have to be supported within close proximity within a factory (e.g. up to 100 in automobile assembly line production).
+
+In a closed-loop control application, the controller periodically submits instructions to a set of sensor/actuator devices, which return a response within a so-called cycle time. The messages, which are referred to as telegrams, are typically small ( $\leq 56$ bytes). The cycle time can be as low as 2 ms, setting stringent end-to-end latency constraints on telegram forwarding ( $\leq 1$ ms). Additional constraints on isochronous telegram delivery add tight constraints on the lateness ( $1 \mu\text{s}$ ), and the communication service has also to be highly available (99,9999%).
+
+Multi-robot cooperation is a case in closed-loop control, where a group of robots collaborate to conduct an action, for example, symmetrical welding of a car body to minimize deformation. This requires isochronous operation between all robots. For multi-robot cooperation, the lateness ( $1 \mu\text{s}$ ) is to be interpreted as the lateness among the command messages of a control event to the group robots.
+
+To meet the stringent requirements of closed-loop factory automation, the following considerations have to be taken:
+
+- Limitation to short-range communications.
+- Use of direct device connection between the controller and actuators.
+- Allocation of licensed spectrum. Licensed spectrum can further be used as a complement to unlicensed spectrum, e.g. to enhance reliability.
+- Reservation of dedicated radio interface resources for each link.
+- Combination of multiple diversity techniques to approach the high reliability target within stringent end-to-end latency constraints (example: frequency, antenna and various forms of spatial diversity, e.g. via relaying)
+- Utilizing OTA time synchronization to satisfy latency-variation constraints for isochronous operation.
+
+A typical industrial closed-loop motion control application is based on individual control events. Each closed-loop control event consists of a downlink transaction followed by a synchronous uplink transaction, both of which are executed within a cycle time. Control events within a manufacturing unit might need to occur isochronously. Factory automation considers application layer transaction cycles between controller devices and sensor/actuator devices. Each transaction cycle consists of (1) a command sent by the controller to the sensor/actuator (downlink), (2) application-layer processing on the sensor/actuator device, and (3) a subsequent response by the sensor/actuator to the controller (uplink). Cycle time includes the entire transaction from the transmission of a command by the controller to the reception of a response by the controller. It includes all lower layer processes and latencies on the radio interface as well the application-layer processing time on the sensor/actuator.
+
+
+
+Diagram of communication paths in a factory network. At the top, a 'Factory Network' cloud is connected to 'Supervisory control', 'Network Security', and 'Network management'. Below, 'Unit 1' and 'Unit n' are shown. Each unit contains a 'Controller' connected to a 'BS' (Base Station). The 'BS' is connected to multiple 'S/A' (Sensor/Actuator) units via 'Wireless links' and 'Repeater' nodes. Red arrows represent 'Isochronous Requests' from the Controller to the S/A. Blue arrows represent 'Isochronous Replies' from the S/A to the Controller. In Unit n, the Controller is also connected to a 'High-speed field bus' which is connected to another 'BS'.
+
+**Figure D.1.0-1: Communication path for isochronous control cycles within factory units. Step 1 (red): controller requests sensor data (or an actuator to conduct actuation) from the sensor/actuator (S/A). Step 2 (blue): sensor sends measurement information (or acknowledges actuation) to controller.**
+
+Figure D.1.0-1 depicts how communication can occur in factory automation. In this use case, communication is confined to local controller-to-sensor/actuator interaction within each manufacturing unit. Repeaters can provide spatial diversity to enhance reliability.
+
+## D.1.1 Service area and connection density
+
+The maximum service volume in motion control is currently set by hoisting solutions, i.e. cranes, and by the manipulation of large machine components, e.g. propeller blades of wind-energy generators. Cranes can be rather wide and quite high above the shop floor, even within a factory hall. In addition, they typically travel along an entire factory hall.
+
+An approximate dimension of the service area is 100 x 100 x 30 m.
+
+Note that production cells are commonly much smaller (< 10 x 10 x 3 m). There are typically about 10 motion-control connections in a production cell, which results in a connection density of up to $10^5 \text{ km}^{-2}$ .
+
+## D.1.2 Security
+
+Network access and authorization in an industrial factory deployment is typically provided and managed by the factory owner with its ID management, authentication, confidentiality and integrity.
+
+Note that motion control telegrams usually are not encrypted due to stringent cycle time requirements.
+
+A comprehensive security framework for factories has been described in IEC 62443.
+
+## D.2 Factory automation – other use cases
+
+### D.2.0 General
+
+Factory automation encompasses all types of production that result in discrete products: cars, chocolate bars, etc. Automation that addresses the control of flows and chemical reactions is referred to as process automation (see clause D.3). Discrete automation requires communications for supervisory and open-loop control applications, as well as process monitoring and tracking of operations inside an industrial plant. In these applications, a large number of sensors, which are distributed over the plant, forward measurement data to process controllers on a periodic or event-driven base. Traditionally, wireline field bus technologies have been used to interconnect sensors and control equipment. Due to the sizable extension of a plant (up to 10 km2), the large number of sensors, rotary joints, and the high deployment complexity of wired infrastructure, wireless solutions have made inroads into industrial process automation.
+
+The related use cases require support of a large number of sensor devices per plant, as well as high communication service availability (99,99%). Furthermore, power consumption is relevant since some sensor devices are battery-powered with a targeted battery lifetime of several years (while providing measurement updates every few seconds). Range also becomes a critical factor due to the low transmit power levels of the sensors, the large size of the plant, and the high-reliability requirements on transport. End-to-end latency requirements typically range between 10 ms and 1 s. User-experienced data rates can be rather low since each transaction typically comprises less than 256 bytes. However, there has been a shift from field busses featuring somewhat modest data rates (~ 2 Mbit/s) to those with higher data rates (~ 10 Mbit/s) due to the increasing number of distributed applications and "data-hungry" applications. An example for the latter is the visual control of production processes. For this application, the user experienced data rate is typically around 10 Mbit/s and the transmitted packets are much larger than what was stated earlier.
+
+Existing wireless technologies for factory automation rely on unlicensed bands. Communication is therefore vulnerable to interference caused by other technologies (e.g. WLAN). With the stringent requirements on transport reliability, such interference is detrimental to proper operation.
+
+The use of licensed spectrum could overcome the vulnerability to same-band interference and therefore enable higher reliability. Utilization of licensed spectrum can be confined to those events where high interference bursts in unlicensed bands jeopardizes communication service availability and end-to-end latency constraints. This allows sharing the licensed spectrum between process automation and conventional mobile services.
+
+Multi-hop topologies can provide range extension and mesh topologies can increase reliability through path redundancy. Clock synchronization will be highly beneficial since it enables more power-efficient sensor operation and mesh forwarding.
+
+The corresponding industrial communication solutions are referred to as fieldbuses. The related standard suite is IEC 61158.
+
+A typical discrete automation application supports downstream and upstream data flows between process controllers and sensors/actuators. The communication consists of individual transactions. The process controller resides in the plant network. This network interconnects via base stations to the wireless (mesh-) network which hosts the sensor/actuator devices. Typically, each transaction uses less than 256 bytes. An example of a controller-initiated transaction service flow is:
+
+1. The process controller requests sensor data (or an actuator to conduct actuation). The request is forwarded via the plant network and the wireless network to the sensors/actuators.
+2. The sensors/actuators process the request and send a replay in upstream direction to the controller. This reply can contain an acknowledgement or a measurement reading.
+
+An example of a sensor/actuator device-initiated transaction service flow:
+
+1. The sensor sends a measurement reading to the process controller. The request is forwarded via the wireless (mesh) network and the plant network.
+2. The process controller can send an acknowledgement in opposite direction.
+
+For both controller- and sensor/actuator-initiated service flows, upstream and downstream transactions can occur asynchronously.
+
+Figure D.2.0-1 depicts how communication can occur in discrete automation. In this use case, communication runs between process controller and sensor/actuator device via the plant network and the wireless (mesh) network. The wireless (mesh) network can also support access for handheld devices for supervisory control or process monitoring purposes.
+
+
+
+Diagram of communication paths in an industrial plant network. At the top, an 'Industrial Plant' box contains 'Supervisory control', 'Network Security', and 'Network management' connected to a 'Plant Network' cloud. Two 'Process Controller' boxes are connected to this cloud. Below the cloud is a 'Gateway' connected to two 'BS' (Base Station) boxes. These BS boxes are part of a mesh network with 'Router', 'RT' (Router), and 'Wireless links'. At the bottom are three 'S/A' (Sensor/Actuator) devices and a 'Sensor/Actuator' device. Two 'Handheld' devices are also connected to the mesh network. Communication paths are shown: 1. Autonomous Measurement report (red arrow from S/A to Process Controller). 2. ACK Reply (blue arrow from Process Controller to S/A). 3. Measurement request (red arrow from Process Controller to Sensor/Actuator). 4. Measurement response (blue arrow from Sensor/Actuator to Process Controller).
+
+**Figure D.2.0-1: Communication path for service flows between process controllers and sensor/actuator devices. Left-hand side: Step 1 (red) – the sensor/actuator (S/A) sends measurement report autonomously, Step 2 (blue) controller acknowledges. Right-hand side: Step 1 (red) - controller requests sensor data (or an actuator to conduct actuation), Step 2 (blue): S/A sends measurement information (or acknowledges actuation) to controller.**
+
+## D.2.1 Service area and connection density
+
+Factory halls can be rather large and even quite high. We set the upper limit at 1000 x 1000 x 30 m. Note that the connection density might vary quite a bit throughout factory halls. The density is, for instance, much higher along an assembly line than in an overflow buffer. Also, the density usually increases towards the factory floor. Typically, there is at least one connection per 10 m2, which results in a connection density of up to 105 km-2.
+
+## D.2.2 Security
+
+Network access and authorization in an industrial factory deployment is typically provided and managed by the factory owner with its ID management, authentication, confidentiality and integrity.
+
+A comprehensive security framework for factories has been described in IEC 62443.
+
+# D.3 Process automation
+
+## D.3.0 General
+
+Process automation has much in common with factory automation (see clause D.2). Instead of discrete products (cars, chocolate bars, etc.), process automation addresses the production of bulk products such as petrol and reactive gases. In
+
+contrast to factory automation, motion control is of limited or no importance. Typical end-to-end latencies are 50 ms. User-experienced data rates, communication service availability, and connection density vary noticeably between applications. Below, we describe one emerging use case (remote control via mobile computational units, clause D.3.1) and a contemporary use case (monitoring, clause D.3.2).
+
+Note that automation fieldbuses (see clause D.2.0) are also used in process automation.
+
+### D.3.1 Remote control
+
+Some of the interactions within a plant are conducted by automated control applications similar to those described in clause D.2. Here too, sensor output is requested in a cyclic fashion, and actuator commands are sent via the communication network between a controller and the actuator. Furthermore, there is an emerging need for the control of the plant by personnel on location. Typically, monitoring and managing of distributed control systems takes place in a dedicated control room.
+
+Staff deployment to the plant itself occurs, for instance, during construction and commissioning of a plant and in the start-up phase of the processes. In this scenario, the locally deployed staff taps into the same real-time data as provided to the control room. These remote applications require high data rates ( $\sim 100$ Mbit/s) since the staff on location needs to view inaccessible locations with high definition (e.g. emergency valves) and since their colleagues in the control room benefit from high-definition footage from body cameras (HD or even 4K).
+
+For both kinds of applications, a very high communication service availability is needed (99,999%). Typically, only a few control loops are fully automated and only handful of control personnel is deployed on location, so that the connection density is rather modest ( $\sim 1000$ km-2).
+
+### D.3.2 Process and asset monitoring
+
+The monitoring of states, e.g. the level of the liquid of process reactors, is a paramount task in process automation. Due to the ever-changing states, measurement data is either pulled or pushed from the sensors in a cyclic manner. Some sensors are more conveniently accessed via wireless links, and monitoring of these sensors via handheld terminals, e.g. during maintenance, is also on the rise. This kind of application entails rather modest user experienced data rates ( $\sim 1$ Mbit/s), and since this kind of data is "only" an indicator for, e.g., what process should be stopped in order to avoid an overflow, and not for automated control loops, the requirement on communication service availability is comparably low (99,9%). Note that emergency valves and such are typically operated locally and do not rely on communication networks. However, many sensors are deployed in chemical plants etc., so that connection density can readily reach 10 000 km-2.
+
+### D.3.3 Service area
+
+While, for instance, chemical plants and refineries can span over several square kilometres, the dedicated control rooms are typically only responsible for a subset of that area. Such subsets are often referred to as plants, and their typical size is 300 m x 300 m x 50 m.
+
+## D.4 Electric-power distribution and smart grid
+
+### D.4.0 General
+
+In TS 22.104 [21] clause A.4, typical electric power distribution and smart grid use cases have been introduced. Here just give some examples.
+
+### D.4.1 Medium voltage
+
+#### D.4.1.0 Overview
+
+An energy-automation domain that now has standards based support by mobile-network technology is the backhaul electricity grid, i.e. the part of the distribution grid between primary substations (high voltage $\rightarrow$ medium voltage) and secondary substations (medium voltage $\rightarrow$ low voltage), and other smart grid services. In figure D.4.1.0-1 we depict a
+
+medium-voltage ring together with energy-automation use cases that either are already deployed or are anticipated within the near future.
+
+
+
+Functional, topological sketch of a medium-voltage ring. The diagram shows a ring of power lines connecting Substation B (with CBs) to a central 'Wireless Backhaul Network' (orange cloud). The network is connected to a 'DMS' (Distribution Management System) and a 'Backhaul to Control Centre'. The ring contains several 'RMU' (Ring Main Unit) devices, each with a CB/Recloser (red square) and a Load Switch (red circle). A lightning bolt indicates a fault. Various energy-automation use cases are shown: PQ (Power Quality), FISR (Fault Isolation and System Restoration), Fault Indicator, Normally Open (green dot), Demand-Response, HEM (Home Energy Manager), AMI (Advanced Metering Infrastructure), and Renewable. A legend at the bottom left identifies the red square as 'CB / Recloser' and the red circle as 'Load Switch'.
+
+**Figure D.4.1.0-1: Functional, topological sketch of a medium-voltage ring.** AMI: advanced metering infrastructure; CB: circuit breaker; DMS: distribution management system; FISR: fault isolation and system restoration; HEM: home energy manager; PQ: power quality; RMU: ring main unit.
+
+The primary substation and the secondary substations are supervised and controlled by a distribution-management system (DMS). If energy-automation devices in the medium-voltage power line ring need to communicate with each other and /or the DMS, a wireless backhaul network needs to be present (orange "cloud" in figure D.4.1.0-1).
+
+A majority of applications in electricity distribution adhere to the communication standard IEC 60870-5-104. However, its modern "cousin" IEC 61850 experiences rapidly increasing popularity. The communication requirements for IEC 61850 applications can be found in EC 61850-90-4. Communication in wide-area networks is described in IEC 61850-90-12.
+
+Usually, power line ring structures have to be open in order to avoid a power-imbalance in the ring (green dot in figure D.4.1.0-1). Examples for energy-automation that already is implemented in medium-voltage grids (albeit in low numbers) are power-quality measurements and the measurement of secondary-substation parameters (temperature, power load, etc.) [13]. Other use cases are demand response and the control of distributed, renewable energy resources (e.g. photovoltaics).
+
+A use case that could also be realised in the future is fault isolation and system restoration (FISR).
+
+«Element.Notes»FISR automates the management of faults in the distribution grid. It supports the localization of the fault, the isolation of the fault, and the restoration of the power delivery. For this kind of automation, the pertinent sensors and actuators broadcast telegrams about their states (e.g., "emergency closer idle") and about actions (e.g., "activating closer") into the backhaul network. This information is used by the ring main units (RMUs) as input for their decision algorithms. We illustrate this use of automation telegrams for an automated FISR event in figure D.4.1.0-1. Let us assume the distribution lines are cut at the location indicated by the bolt of lightning in the figure. In that case, the RMUs between the bolt and the green load switch (open) will be without power. The RMUs next to the "bolt" automatically open their load switches after having sensed the loss of electric connectivity between them. They both broadcast these actions into the backhaul network. Typically, these telegrams are repeated many times while the time between adjacent telegrams increases exponentially. This communication patterns leads to sudden, distributed surges in
+
+the consumed communication bandwidth. After the RMUs next to the "bolt" have opened their switch, the RMU that so far has kept the power line ring open (green dot in figure D.4.1.0-1) closes the load switch. This event too is broadcasted into the backhaul network. The typical maximum end-to-end latency for this kind of broadcast is 25 ms with a peak experienced data rate of 10 Mbit/s. Note that the distribution system typically subscribes to telegrams from all RMUs in order to keep abreast with the happenings in the distribution grid.
+
+Automatic fault handling in the distribution grid shortens outage time and offloads the operators in the distribution control centre for more complicated situations. Therefore, automated FISR can help to improve performance indexes like System Average Interruption Duration Index and System Average Interruption Frequency Index.
+
+Automation telegrams are typically distributed via domain multicast. As explained above, the related communication pattern can be "bursty", i.e. only few automation telegrams are sent when the distribution network operates nominally ( $\sim 1$ kbit/s), but, for instance, a disruption in the power line triggers a short-lived avalanche of telegrams from related applications in the ring ( $\geq 1$ Mbit/s).
+
+#### D.4.1.1 Service area and connection density
+
+Service coverage is only required along the medium-voltage line. In Europe, the line often forms a loop (see figure D.4.1.0-1), while deployments in other countries, e.g. the USA, tend to extend linearly over distances up to $\sim 100$ km. The vertical dimension of the poles in a medium voltages line is typically less than 40 m. Especially in urban areas, the number of ring main units can be rather large ( $> 10$ km $^{-2}$ ), and the number of connections to each ring main unit is expected to increase swiftly once economical, suitable wireless connectivity becomes available. We predict connection densities of up to 1.000 km $^{-2}$ .
+
+#### D.4.1.2 Security
+
+Due to its central role in virtually every country on earth, electricity distribution is heavily regulated. Security assessments for, e.g. deployments in North America, need to adhere to the NERC CIP suite [14]. Technical implementations are described in standard suites such as IEC 62351.
+
+### D.4.2 High voltage
+
+#### D.4.2.0 Overview
+
+In order to avoid region- or even nation-wide power outages, wide-area power system protection is on the rise. "When a major power system disturbance occurs, protection and control actions are required to stop the power system degradation, restore the system to a normal state, and minimize the impact of the disturbance. The present control actions are not designed for a fast-developing disturbance and can be too slow. Local protection systems are not able to consider the overall system, which can be affected by the disturbance. Wide area disturbance protection is a concept of using system-wide information and sending selected local information to a remote location to counteract propagation of the major disturbances in the power system." [15]. Protection actions include, "among others, changes in demand (e.g. load shedding), changes in generation or system configuration to maintain system stability or integrity and specific actions to maintain or restore acceptable voltage levels." [16]. One specific application is phasor measurement for the stabilisation of the alternating-current phase in a transport network. For this, the voltage phase is measured locally and sent to a remote-control centre. There, this information is processed, and automated actions are triggered. One action can be the submission of telegrams to power plants, instructing them to either accelerate or decelerate their power generators in order to keep the voltage phase in the transport network stable. A comprehensive overview of this topic can be found elsewhere in the literature [17].
+
+This kind of automation requires very low end-to-end latencies (5 ms) [16] and—due to its critical importance for the operation of society—a very high communication service availability (99,9999%).
+
+#### D.4.2.1 Service area and connection density
+
+As is the case for medium-voltage distribution networks (see Annex D.4.1), connectivity in high-voltage automation has to be provided mainly along the power line. The distances to be covered can be substantial (hundreds of kilometres in rural settings), while shorter links are prevalent in metropolitan areas. The number of connections in wide-area power system protection is rather low; but—due to the sliver-shaped service area—the connection density can be rather high (1000 km $^{-2}$ ).
+
+## D.4.2.2 Security
+
+Due to its central role in virtually every country on earth, electricity distribution is heavily regulated. Security assessments for, e.g. deployments in North America, need to adhere to the NERC CIP suite [14]. Technical implementations are described in standard suites such as IEC 62351.
+
+# D.5 Intelligent transport systems – infrastructure backhaul
+
+## D.5.0 General
+
+Intelligent Transport Systems (ITS) embrace a wide variety of communications-related applications that are intended to increase travel safety, minimize environmental impact, improve traffic management, and maximize the benefits of transportation to both commercial users and the general public. Over recent years, the emphasis in intelligent vehicle research has turned to co-operative systems, in which the traffic participants (vehicles, bicycles, pedestrians, etc.) communicate with each other and/or with the infrastructure.
+
+Cooperative ITS is the term used to describe technology that allows vehicles to become connected to each other, and to the infrastructure and other parts of the transport network. In addition to what drivers can immediately see around them, and what vehicle sensors can detect, all parts of the transport system will increasingly be able to share information to improve decision making. Thus, this technology can improve road safety through avoiding collisions, but also assist in reducing congestion and improving traffic flows, and reduce environmental impacts. Once the basic technology is in place as a platform, an array of applications can be developed.
+
+Cooperative ITS can greatly increase the quality and reliability of information available about vehicles, their location and the road environment. In the future, cars will know the location of road works and the switching phases of traffic lights ahead, and they will be able to react accordingly. This will make for safer and more convenient travel and faster arrival at the destination. On-board driver assistance, coupled with two-way communication between vehicles and between vehicles and road infrastructure, can help drivers to better control their vehicle and hence have positive effects in terms of safety and traffic efficiency. An important role in this plays the so-called road side units (RSUs). Vehicles can also function as sensors reporting weather and road conditions including incidents. In this way, cars can be used as information sources for high-quality information services.
+
+RSUs are connected to the traffic control centre for management and control purposes. They broadcast, e.g., traffic light information (RSU → vehicle) and traffic information from the traffic-control centre (TCC) via the RSU to the vehicles (TCC → RSU → vehicle). RSUs also collect vehicle probe data for the traffic control centre (vehicle → RSU → TCC). For reliable distribution of data, low-latency and high-capacity connections between RSUs (e.g. traffic lights, traffic signs, etc.) and the TCC are required. This type of application comes with rather tight end-to-end latency requirements for the communication service between RSU and TCC (10 ms), since relayed data needs to be processed in the TCC and, if needed, the results are forwarded to neighbouring RSUs. Also, the availability of the communication service has to be very high (99,999%) in order to compete with existing wired technology and in order to justify the costly deployment and maintenance of RSUs. Furthermore, due to considerably large aggregation areas (see clause D.5.1), considerable amounts of data need to be backhauled to the TCC (up to 10 Mbit/s per RSU).
+
+## D.5.1 Service area and connection density
+
+It is relatively hard to provide estimates for the service area dimension. One reason is that it depends on the placement of the base station relative to the RSUs. Also, the RSUs can, in principle, act as relay nodes for each other. The service area dimension stated in table 7.2.3.2-1 indicates the size of the typical data collection area of an RSU (2 km along a road), from which the minimum spacing of RSUs can be inferred. The connection density can be quite high in case data is relayed between RSUs, i.e. along the road (1000 km-2).
+
+## Annex E (informative): (void)
+
+## Annex F (informative): QoS Monitoring
+
+### F.1 QoS monitoring for assurance
+
+This Clause discusses how QoS monitoring information can be used for assurance purposes. For background information on assurance see [19] and appendix A.3 in [20].
+
+Assurance consists of four major steps (see Figure F.1-1 and [18]):
+
+- *Customer's QoS requirements*
+
+These state the level of quality required by the customer of a service. This information is divulged to the provider.
+
+- *Service provider's offerings of QoS (or planned/targeted QoS)*
+
+This is a statement of the level of quality expected to be offered to the customer by the service provider.
+
+- *QoS achieved/delivered*
+
+This is the level of quality achieved and delivered to the customer. Monitoring information is divulged to the customer.
+
+- *Customer rating of QoS*
+
+The customer can compare the QoS achieved by the provider with the QoS requirements (see above) and its own experience of the QoS. This is a crucial step for establishing assurance about the fulfillment of the customer's requirements.
+
+
+
+```
+graph LR
+ subgraph Customer
+ C1[customer's QoS requirements]
+ C2[Comparison of QoS achieved by provider (monitoring) with requirements and QoS experienced by customer]
+ end
+ subgraph Provider
+ P1[QoS assured by provider]
+ P2[QoS achieved by provider]
+ end
+ C1 -- divulged to --> P1
+ P1 --> P2
+ P2 -- monitoring information --> C2
+```
+
+Diagram illustrating QoS assurance by use of QoS monitoring information. The diagram is split by a vertical dashed line representing the 'interface between application and communication system'. On the left (Customer side), there are two boxes: 'customer's QoS requirements' at the top and 'Comparison of QoS achieved by provider (monitoring) with requirements and QoS experienced by customer' at the bottom. On the right (Provider side), there are two boxes: 'QoS assured by provider' at the top and 'QoS achieved by provider' at the bottom. Arrows show the flow: 'divulged to' from customer's requirements to assured QoS, 'monitoring information' from achieved QoS to comparison box, and a downward arrow from assured QoS to achieved QoS. Vertical labels 'CUSTOMER' and 'PROVIDER' are on the far left and right respectively.
+
+**Figure F.1-1: QoS assurance by use of QoS monitoring information**
+
+NOTE: This Figure is based on the trust model in reference [18].
+
+The start time and the duration of the QoS monitoring is specified in the parameter *observation time interval*, which is exchanged between the customer, for instance an application consuming a communication service, and the provider (for instance a private 5G network providing a communication service). The observation time interval is the time interval during which a series of measurements is conducted. In the context of QoS monitoring, these are the measurements necessary for assessing the QoS of communication services, for instance the measurement of end-to-end latencies.
+
+Examples of parameters to be monitored by the provider are given in annex C in reference [36].
+
+## F.2 Network Diagnostics
+
+Network diagnostics helps with scanning, diagnosing and identifying problems within a network. Diagnostics includes gathering data and continuously providing sufficient performance parameters that characterize the quality of the network connection. This includes data of the physical connection as well as of logical links and sub-networks. Exposure of relevant (and possibly aggregated) performance parameters ensures a quick reaction in case of failure as well as identifying network connectivity, performance and other related problems. Network diagnostic should be able to:
+
+- be proactive (to early detect failures) and not only reactive (to deal with faults that have already occurred).
+- accurately differentiate malfunctions/failures and evaluate their impact on the service/network.
+- provide clear explanations about what happened.
+- suggest corrective actions, and possibly perform them automatically.
+
+Furthermore, specific connectivity information is also of interest as well as usage information (e.g. traffic load) of the node (e.g. RAN).
+
+Network diagnostic information needs to be generated automatically and, in case of a hosted or virtual network deployment, be made available to the tenant of the network via a suitable API.
+
+---
+
+## Annex G (informative): Asset Tracking use cases
+
+### G.1 Asset Tracking
+
+Every organisation owns assets (e.g. machines, medical devices, containers, pallets, trolleys). These assets are often not stationary: they are transported all over the world by different kinds of vehicles; and the assets are also moved inside various kinds of buildings.
+
+The ownership of assets can change many times during the life-cycle of the asset as different stakeholders take possession of the assets and pass them on to other stakeholders along the supply chain and value chain.
+
+So, many stakeholders want to track their assets anytime and anywhere (indoor & outdoor) in a global and multi-modal context (e.g. sea, air, road, rail).
+
+The asset tracking topic implies more than just knowing the location of an asset. Asset tracking includes real time and/or time-stamped monitoring of several asset-related properties depending on the asset and its content (e.g. condition of the asset and changes, environmental factors – temperature, mechanical shock).
+
+The 5G system provides the capability to better support asset tracking in all its aspects in particular in term of coverage (need to support full coverage: e.g. indoor / urban / rural / harsh environments / metallic obstructions on land, sea) with the support of terrestrial and non- terrestrial network as well as use of relays when necessary and in term of energy efficiency (15 to 20 years' lifetime of an asset tracking device without changing the battery or the UE).
+
+### G.2 Battery life expectancy and message size to support example use cases for asset tracking
+
+For asset tracking it is important to be able to have the asset on the field during a period corresponding to the life of the asset without changing the UE or the battery of the UE.
+
+The battery life expectancy, message size and device density values required to support the potential opportunities in various asset tracking use cases are summarised in table G.2-1
+
+**Table G.2-1: Battery life expectancy and message size to support example use cases for asset tracking**
+
+| | Scenario | Battery Life Expectancy (note 1) | Typical Message size | Maximum Message size | Typical Frequency (number of messages per day) | Typical Battery Capacity | Device density |
+|---|---------------------|----------------------------------|----------------------|----------------------|------------------------------------------------|--------------------------|------------------------------|
+| 1 | Containers (note 2) | 12 years | 200 bytes | 2500 bytes | 24 | 21,6 Wh | 1,4 devices / m 3 |
+| 2 | Wagons | 20 years | 200 bytes | 2500 bytes | 24 | 36 Wh | 0,3 devices / m 2 |
+| 3 | Pallets | 7 years | 300 bytes | 300 bytes | 24 | 12 Wh | 4 devices/ m 2 |
+
+NOTE 1: Battery life expectancy is to be assumed in all coverage conditions and is based on typical message size value and typical frequency
+NOTE 2: A large container ship with a mix of 20 ft and 40 ft containers is assumed.
+NOTE 3: All the values in this table are targeted values and not strict requirements.
+
+## Annex H (informative): Interworking between Network Operators and Application Providers for localized services
+
+This clause illustrates examples of scenarios applicable for interworking between hosting network operators (PLMN or NPN) and data applications based on service agreements for localized services among network operators and application/service providers:
+
+- Hosting network operator owns the 5G network which provides access and IP connectivity to serving UEs.
+- Network operator owned application layer entities, e.g., including Service Hosting Environment, or IMS network.
+- Application platforms in third party domain can be owned by third party application/service providers, or home/other network operators.
+- The Application platforms could be application servers (e.g., Video on Demand Server, Cloud gaming server, etc.), 3rd party software development platforms, and third party/operator Service Hosting Environments.
+
+The following figures show the collaborative relationship in three domains including network operators providing access and IP connectivity, network operators providing services via IMS/application platforms, and application/service providers providing services via application platforms or applications. The dashed line between visited hosting network operator and Home network operator is based on service level localized service agreement and the horizontal line represents the demarcation between the network operator domains and the 3rd party domain. In an operator network, the application layer entities can include IMS network, Application platforms, and API Gateway for third party applications developed using APIs (e.g., REST, GSMA OneAPI).
+
+Figure H-1 provides the home operator owned/collaborative interworking scenarios where traffic is routed to home network operator and applications are delivered by the home operator via interworking agreements between network operators.
+
+
+
+This diagram illustrates the 'Home Operator owned/collaborative interworking scenario Home Routed'. It is divided into three horizontal domains: 'Internet/3rd Party Domain' at the top, 'Home Operator Domain' in the middle, and 'Visited Operator Domain' at the bottom right.
+
+In the 'Internet/3rd Party Domain', there are 'Application#n' and 'Application#1' on the left, 'Other operators IMS' and 'Other operators Application Platforms' in the center, and 'Application Platform#1' and 'Application Platform#n' on the right.
+
+In the 'Home Operator Domain', 'Application#n' and 'Application#1' connect via a solid line to an 'API Gateway'. The 'API Gateway' connects via a solid line to the 'Home Operator' (represented by a solid blue circle). The 'Home Operator' connects via solid lines to 'Home Operator Owned Application Platforms' and 'Home Operator IMS' (both represented by dashed ovals).
+
+Dashed lines connect the 'Internet/3rd Party Domain' components to the 'Home Operator'. Specifically, 'Other operators IMS' and 'Other operators Application Platforms' connect to the 'Home Operator', as do 'Application Platform#1' and 'Application Platform#n'.
+
+A dashed line connects the 'Home Operator' to the 'Visited Operator Domain', where it connects to a 'Hosting Network Operator' (solid blue circle). A dashed line also connects the 'Hosting Network Operator' to a 'UE' (User Equipment) box.
+
+Solid lines represent traffic routed over domains within the home operator network, while dashed lines represent traffic routed over domains outside of the home operator network.
+
+Diagram of Home Operator owned/collaborative interworking scenario Home Routed. It shows traffic flow from various application platforms through a Home Operator to a Visited Operator Domain, where a UE is located. Solid lines represent internal Home Operator network traffic, while dashed lines represent traffic routed across different domains.
+
+**Figure H-1: Home Operator owned/collaborative interworking scenario Home Routed**
+
+Note: The other network operators and service/application operators in 3rd party domain provides collaborative services in application platforms to Home operator. The arrow solid line represents the traffics routed over domains within home operator network while the arrow dash lines represent the traffics routed over domains outside of home operator network.
+
+Figure H-2 provides hosting network operator owned and collaborative interworking scenarios between visited hosting network operator and operators in 3rd party domains where traffic is routed to application from the hosting network to 1) hosting network owned application platforms, 2) collaborative home network owned application platforms, and 3) third parties via interworking agreements between visited hosting network operator and home/other network operators, and between hosting network operator and other application/service providers.
+
+
+
+This diagram illustrates the 'Hosting Network Operator owned/collaborative interworking scenario Local Breakout'. It is divided into three horizontal domains: 'Internet/3rd Party Domain' at the top, 'Home Operator Domain' at the bottom left, and 'Visited Operator Domain' in the center.
+
+In the 'Internet/3rd Party Domain', there are 'Other Operators IMS' and 'Other Operators Owned Application Platforms' on the left, and 'Application Platform#n' and 'Application Platform#1' on the right.
+
+In the 'Home Operator Domain', there are 'Home Operator Owned Application Platforms' and 'Home Operator IMS' (both represented by dashed ovals) on the left, and a 'Home Operator' (solid blue circle) in the center.
+
+In the 'Visited Operator Domain', there is a 'Hosting Network Operator' (solid blue circle) in the center, which connects via solid lines to 'Hosting Network Operator Owned Application Platforms' and 'Hosting Network Operator IMS' (both represented by dashed ovals) on the right. Below the 'Hosting Network Operator' is a 'UE' (User Equipment) box.
+
+Dashed lines connect the 'Internet/3rd Party Domain' components to the 'Hosting Network Operator'. Specifically, 'Other Operators IMS' and 'Other Operators Owned Application Platforms' connect to the 'Hosting Network Operator', as do 'Application Platform#n' and 'Application Platform#1'.
+
+A dashed line connects the 'Home Operator' to the 'Hosting Network Operator'.
+
+A dashed line connects the 'UE' to an 'API Gateway' (solid blue oval), which then connects via a solid line to the 'Hosting Network Operator'.
+
+Solid lines represent traffic routed over domains within the hosting network operator network, while dashed lines represent traffic routed over domains outside of the hosting network operator network.
+
+Diagram of Hosting Network Operator owned/collaborative interworking scenario Local Breakout. It shows traffic flow from a UE through a Hosting Network Operator to various application platforms. Solid lines represent internal Hosting Network Operator network traffic, while dashed lines represent traffic routed across different domains.
+
+**Figure H-2:Hosting Network Operator owned/collaborative interworking scenario Local Breakout**
+
+Note: The other network operators and application/service operators in 3rd party domain provides collaborative services in application platform to hosting network operator and/or home network operator. The arrow solid lines represent the traffics routed over domains within hosting network while the arrow dash lines represent the traffics routed over domains outside of hosting operator network.
+
+Other interworking scenarios are not excluded.
+
+## Annex I (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|---------|-----------|----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------|--|--|-------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | | | |
+| 2016-12 | SA#75 | SP-170156 | - | - | - | Skeleton | | 0.1.0 | | | |
+| 2017-03 | SA#75 | SP-170156 | - | - | - | Agreements in SA1#75: S1-162342, S1-162305, S1-162480, S1-162345, S1-162481, S1-162471, S1-162313, S1-162347, S1-162486, S1-162349, S1-162546, S1-162322, S1-162323, S1-162450, S1-162547, S1-162548, S1-162549, S1-162492, S1-162550, S1-162520, S1-162485, S1-162517, S1-162551, S1-162505. And rapporteur's clean-up. | | | | | 0.1.1 |
+| | | | | | | Agreements in SA1#76: S1-163412, S1-163445, S1-163446, S1-163256, S1-163070, S1-163415, S1-163258, S1-163293, S1-163260, S1-163416, S1-163296, S1-163264, S1-163265, S1-163266, S1-163267, S1-163268, S1-163297, S1-163298, S1-163417, S1-163418, S1-163299, S1-163274, S1-163275, S1-163277, S1-163278, S1-163280, S1-163448, S1-163421, S1-163029, S1-163112, S1-163285, S1-163286, S1-163287, S1-163422, S1-163289, S1-163382, S1-163132, and rapporteur's clean-up. | | | | | 0.2.0 |
+| 2017-03 | SA#75 | SP-170156 | - | - | - | MCC Clean-up for presentation to SA for information | | 1.0.0 | | | |
+| 2017-03 | SA#75 | SP-170156 | - | - | - | Agreements in SA1#76bis: S1-170198, S1-170199, S1-170335, S1-170201, S1-170008, S1-170207, S1-170106, S1-170338, S1-170092, S1-170339, S1-170212, S1-170340, S1-170341, S1-170014, S1-170217, S1-170218, S1-170219, S1-170131, S1-170342, S1-170314, S1-170224, S1-170206, S1-170090, S1-170225, S1-170226, S1-170343, S1-170228, S1-170229, S1-170230, S1-170232, S1-170122, S1-170042, S1-170234, S1-170345, S1-170364, S1-170236, S1-170347, S1-170220, S1-170239, S1-170243, S1-170209, S1-170365, S1-170245, S1-170048, and rapporteur's clean-up. | | | | | 1.1.0 |
+| 2017-02 | SA1#77 | | | | | Agreements in SA1#77: S1-171400, S1-171401, S1-171430, S1-171141, S1-171252, S1-171253, S1-171256, S1-171257, S1-171258, S1-171143, S1-171259, S1-171431, S1-171149, S1-171261, S1-171144, S1-171263, S1-171297, S1-171290, S1-171266, S1-171154, S1-171267, S1-171268, S1-171269, S1-171073, S1-171291, S1-171150, S1-171272, S1-171151, S1-171152, S1-171273, S1-171188, S1-171153, S1-171155, S1-171283, S1-171274, S1-171277, S1-171278, S1-171393, S1-171399, S1-171156, S1-171060, S1-171069, S1-171180, S1-171284, S1-171285, S1-171140, S1-171286, S1-171288, S1-171398, S1-171292, S1-171435, and rapporteur's clean-up. | | | | | 1.2.0 |
+| 2017-03 | SA#75 | SP-170156 | - | - | - | Presentation for approval | | 2.0.0 | | | |
+| 2017-03 | SA#75 | - | | | | Raised to v.15.0.0 following SA's approval | | 15.0.0 | | | |
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|----------------------------------------------------------------------------------|--------|--------|----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-76 | SP-170443 | S1-172288 | 22.261 | 0017 | 3 | Rel-15 | B | Addition of requirement on charging for the tenant of the slice | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172286 | 22.261 | 0016 | 3 | Rel-15 | B | Addition of requirement on maintaining user experience when UE performs handover | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172270 | 22.261 | 0022 | 2 | Rel-15 | F | Alignment of network slicing requirements | 15.0.0 | 15.1.0 | SMARTE R |
+
+| | | | | | | | | | | | |
+|-------|-----------|---------------|--------|------|---|--------|---|------------------------------------------------------------------------------------------------------------------------|--------|--------|--------------|
+| SP-76 | SP-170443 | S1-172283 | 22.261 | 0011 | 3 | Rel-15 | F | Clarification on removal of network function | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172279 | 22.261 | 0021 | 3 | Rel-15 | F | Clarifications on network slicing | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172257 | 22.261 | 0020 | 1 | Rel-15 | F | Clean-up of requirements on network slice scaling | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172262 | 22.261 | 0025 | 1 | Rel-15 | F | Correction on '8 securtiy' | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172012 | 22.261 | 0001 | | Rel-15 | F | CR to 22.261 Correction of the references for eV2X TS | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172285 | 22.261 | 0015 | 4 | Rel-15 | F | Efficient User Plane | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172280 | 22.261 | 0012 | 3 | Rel-15 | C | Exposure of QoE capability | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172256 | 22.261 | 0023 | 1 | Rel-15 | C | Maintaining a session whose priority changes in real time | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172261 | 22.261 | 0027 | 1 | Rel-15 | B | parallel transfer of multiple multicast/broadcast user services to a UE | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172277 | 22.261 | 0002 | 3 | Rel-15 | F | Replacement of 5G-RAN with NG-RAN | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172278 | 22.261 | 0006 | 2 | Rel-15 | F | Update service continuity definition | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172404 | 22.261 | 0007 | 4 | Rel-15 | C | Updates to network slice assignment in TS 22.261 | 15.0.0 | 15.1.0 | SMARTE R |
+| SP-76 | SP-170443 | S1-172287 | | | | | | Request in CR 0031r1 to raise this spec to v.16.0.0 without CR0031r1 but with all other CRs | 15.1.0 | 16.0.0 | - |
+| SP-77 | SP-170699 | S1-173544 | 22.261 | 0032 | 2 | Rel-16 | F | Requirement for audio video sync timing for audio-visual interaction. | 16.0.0 | 16.1.0 | TEI15 |
+| SP-77 | SP-170692 | S1-173459 | 22.261 | 0046 | | Rel-16 | A | Correction on security requirement for relayed data protection | 16.0.0 | 16.1.0 | MONAST ERY |
+| SP-77 | SP-170692 | S1-173461 | 22.261 | 0048 | | Rel-16 | A | Correction on regulatory requirement for all access technologies | 16.0.0 | 16.1.0 | MONAST ERY |
+| SP-77 | SP-170692 | S1-173463 | 22.261 | 0049 | | Rel-16 | A | Update TS number of eV2X specification | 16.0.0 | 16.1.0 | MONAST ERY |
+| SP-77 | SP-170692 | S1-173549 | 22.261 | 0051 | | Rel-16 | A | Clarification on access control requirement | 16.0.0 | 16.1.0 | SMARTE R |
+| SP-78 | SP-170989 | S1-174564 | 22.261 | 0068 | 1 | Rel-16 | F | Provide a more realistic KPI value for Virtual Reality | 16.1.0 | 16.2.0 | TEI16 |
+| SP-78 | SP-170987 | S1-174620 | 22.261 | 0069 | | Rel-16 | A | Clarification of unified access control requirements | 16.1.0 | 16.2.0 | SMARTE R |
+| SP-79 | SP-180129 | S1-180598 | 22.261 | 0079 | 2 | Rel-16 | A | Clarification of 5GC requirements | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-79 | SP-180130 | S1-180496 | 22.261 | 0077 | 1 | Rel-16 | A | Alignment of normative and descriptive clauses for Unified Access Control regarding operator defined Access Identities | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-79 | SP-180130 | S1-180527 | 22.261 | 0088 | | Rel-16 | A | Clarification of access Identity in unified access control | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-79 | SP-180130 | S1-180529 | 22.261 | 0089 | | Rel-16 | A | Clarification of Messaging in Unified Access Control (UAC) | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-79 | SP-180131 | S1-180194 | 22.261 | 0085 | | Rel-16 | A | Clarification of latency requirements | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-79 | SP-180213 | fromS1-180611 | 22.261 | 0086 | 3 | Rel-16 | A | Support Legacy USIM in 5G | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-79 | SP-180224 | fromS1-180503 | 22.261 | 0075 | 4 | Rel-16 | B | Support of Voice Service Continuity from 5G system to UTRAN CS | 16.2.0 | 16.3.0 | 5GVSC |
+| SP-79 | SP-180140 | S1-180624 | 22.261 | 0090 | | Rel-16 | F | Release 15 alignment on the KPIs for URLLC | 16.2.0 | 16.3.0 | SMARTER Ph2 |
+| SP-79 | SP-180142 | S1-180596 | 22.261 | 0081 | 2 | Rel-16 | B | 5G Requirements to Prevent a Single Service (e.g. Emergency) from Monopolizing Network Resources | 16.2.0 | 16.3.0 | SMARTE R |
+| SP-80 | SP-180312 | S1-181389 | 22.261 | 0095 | 1 | Rel-16 | F | Positioning Part align with Rel-15 structure | 16.3.0 | 16.4.0 | SMARTE R_Ph2 |
+| SP-80 | SP-180312 | S1-181740 | 22.261 | 0103 | 3 | Rel-16 | F | Clarifications on communication service availability and reliability | 16.3.0 | 16.4.0 | SMARTE R_Ph2 |
+| SP-80 | SP-180314 | S1-181714 | 22.261 | 0097 | 3 | Rel-16 | B | QoS Monitoring | 16.3.0 | 16.4.0 | QoS_MON |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|--------------------------------------------------------------------------------------------------------------|--------|--------|----------|
+| SP-80 | SP-180318 | S1-181659 | 22.261 | 0253 | | Rel-16 | B | Inter-RAT Mobility requirement for realtime service | 16.3.0 | 16.4.0 | MOBRT |
+| SP-80 | SP-180320 | S1-181547 | 22.261 | 0101 | 3 | Rel-16 | B | Inclusion of ethernet transport services in TS 22.261 | 16.3.0 | 16.4.0 | 5GLAN |
+| SP-80 | SP-180325 | S1-181671 | 22.261 | 0098 | 3 | Rel-16 | B | Policy delivery to UE for background data transfer | 16.3.0 | 16.4.0 | PDBDT |
+| SP-80 | SP-180464 | S1-181719 | 22.261 | 0254 | 1 | Rel-16 | B | IMS and Network Slicing | 16.3.0 | 16.4.0 | enIMS |
+| SP-81 | SP-180752 | S1-182662 | 22.261 | 0268 | 2 | Rel-16 | A | Clarification to Delay Tolerant | 16.4.0 | 16.5.0 | SMARTER |
+| SP-81 | SP-180752 | S1-182674 | 22.261 | 0289 | 2 | Rel-16 | A | Clarify the method of configuring the UE to use Access Identity 1 and Access Identity 2 | 16.4.0 | 16.5.0 | SMARTER |
+| SP-81 | SP-180752 | S1-182758 | 22.261 | 0297 | 1 | Rel-16 | A | Support for use of licensed and unlicensed bands | 16.4.0 | 16.5.0 | SMARTER |
+| SP-81 | SP-180754 | S1-182438 | 22.261 | 0283 | 1 | Rel-16 | A | Addition of new Access category for 'MO signalling on RRC level resulting from other than paging'- Mirror CR | 16.4.0 | 16.5.0 | TEI15 |
+| SP-81 | SP-180788 | - | 22.261 | 0280 | 3 | Rel-16 | C | Updates to QoS Monitoring Description | 16.4.0 | 16.5.0 | QoS_MON |
+| SP-81 | SP-180789 | - | 22.261 | 0292 | 4 | Rel-16 | C | Addition of Informative Annex for QoS Monitoring | 16.4.0 | 16.5.0 | QoS_MON |
+| SP-81 | SP-180763 | S1-182677 | 22.261 | 0278 | 3 | Rel-16 | B | Network service exposure requirements | 16.4.0 | 16.5.0 | cyberCAV |
+| SP-81 | SP-180763 | S1-182685 | 22.261 | 0295 | 1 | Rel-16 | B | Ethernet support in TS 22.261 | 16.4.0 | 16.5.0 | cyberCAV |
+| SP-81 | SP-180763 | S1-182756 | 22.261 | 0286 | 3 | Rel-16 | B | Non-public network requirements | 16.4.0 | 16.5.0 | cyberCAV |
+| SP-81 | SP-180764 | S1-182009 | 22.261 | 0255 | | Rel-16 | B | Performance requirements for 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182016 | 22.261 | 0261 | | Rel-16 | B | NG-RAN sharing for 5G satellite access network | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182385 | 22.261 | 0264 | 1 | Rel-16 | B | Satellite links between radio access network and core network | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182590 | 22.261 | 0263 | 2 | Rel-16 | B | Regulatory and charging aspects related to 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182602 | 22.261 | 0256 | 1 | Rel-16 | B | Multiple access requirements related to 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182605 | 22.261 | 0259 | 2 | Rel-16 | B | Efficient user plane aspects of 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182606 | 22.261 | 0260 | 2 | Rel-16 | B | Mobility management related requirements for 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182607 | 22.261 | 0262 | 1 | Rel-16 | B | QoS control aspects of 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182619 | 22.261 | 0265 | 1 | Rel-16 | B | Broadcast and multicast via satellite access networks | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182720 | 22.261 | 0258 | 2 | Rel-16 | B | Efficient delivery of content using 5G satellite access network | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180764 | S1-182725 | 22.261 | 0257 | 3 | Rel-16 | B | Connectivity aspects of 5G satellite access | 16.4.0 | 16.5.0 | 5GSAT |
+| SP-81 | SP-180765 | S1-182585 | 22.261 | 0269 | 2 | Rel-16 | B | KPIs for horizontal and vertical positioning service levels in clause 7.3.2 | 16.4.0 | 16.5.0 | 5G_HYPOS |
+| SP-81 | SP-180765 | S1-182586 | 22.261 | 0270 | 2 | Rel-16 | B | Other KPIs for 5G positioning services | 16.4.0 | 16.5.0 | 5G_HYPOS |
+| SP-81 | SP-180765 | S1-182587 | 22.261 | 0271 | 2 | Rel-16 | B | Security requirements for 5G positioning services | 16.4.0 | 16.5.0 | 5G_HYPOS |
+| SP-81 | SP-180765 | S1-182588 | 22.261 | 0272 | 2 | Rel-16 | C | Update description (clause 7.3.1) of 5G positioning services | 16.4.0 | 16.5.0 | 5G_HYPOS |
+| SP-81 | SP-180769 | S1-182769 | 22.261 | 0273 | 3 | Rel-16 | F | Clarification for Inter-RAT Mobility requirement for realtime service | 16.4.0 | 16.5.0 | MOBRT |
+| SP-81 | SP-180770 | S1-182395 | 22.261 | 0276 | 1 | Rel-16 | B | 5GLAN Requirements | 16.4.0 | 16.5.0 | 5GLAN |
+| SP-81 | SP-180770 | S1-182702 | 22.261 | 0275 | 2 | Rel-16 | B | 5GLAN charging requirements | 16.4.0 | 16.5.0 | 5GLAN |
+| SP-81 | SP-180770 | S1-182755 | 22.261 | 0274 | 3 | Rel-16 | B | 5GLAN security requirements | 16.4.0 | 16.5.0 | 5GLAN |
+| SP-81 | SP-180774 | S1-182771 | 22.261 | 0281 | 2 | Rel-16 | B | Enhanced network slice requirements based on business role models | 16.4.0 | 16.5.0 | BRMNS |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-12 | SP-82 | SP-181007 | 0331 | 2 | B | Functional requirements for 5G positioning services (clause 6) | 16.6.0 |
+| 2018-12 | SP-82 | SP-181007 | 0309 | 2 | F | Terminology correction for positioning-related tables in 7.3.2 | 16.6.0 |
+| 2018-12 | SP-82 | SP-181007 | 0308 | 3 | D | Clarification on positioning-related descriptions in 7.3.1 | 16.6.0 |
+| 2018-12 | SP-82 | SP-181007 | 0330 | 2 | C | Clarification of requirement on energy per fix in clause 7.3.2.3 | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0340 | | C | Update of 5GLAN – Indirect Communication Mode | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0319 | 2 | F | Clarification on Ethernet transport services | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0334 | 2 | C | Addition to definition on private communication | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0335 | 2 | C | Update of 5GLAN - General | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0336 | 2 | C | Update of 5G LAN - virtual network (5G LAN-VN). | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0341 | 1 | C | Update of 5GLAN – Service exposure | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0337 | 3 | C | Update of 5GLAN - Creation and management | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0342 | 2 | C | Update of 5GLAN – Security | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0339 | 4 | C | Update of 5GLAN – Discovery | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0338 | 5 | C | Update of 5GLAN – Privacy | 16.6.0 |
+| 2018-12 | SP-82 | SP-181008 | 0316 | 4 | B | 5GLAN requirements about enabling disabling UE from 5G-LAN based on location | 16.6.0 |
+| 2018-12 | SP-82 | SP-181128 | 0298 | 2 | F | Corrections on requirements for SAT | 16.6.0 |
+| 2018-12 | SP-82 | SP-181011 | 0310 | 2 | B | Enhanced network slice requirements based on business role models | 16.6.0 |
+| 2018-12 | SP-82 | SP-181011 | 0299 | 3 | F | Correction to BRMNS requirements | 16.6.0 |
+| 2018-12 | SP-82 | SP-181005 | 0329 | | B | Introduction of cyberCAV | 16.6.0 |
+| 2018-12 | SP-82 | SP-181005 | 0311 | 2 | B | Support for security requirements based on FS_CAV | 16.6.0 |
+| 2018-12 | SP-82 | SP-181005 | 0315 | 2 | F | Replacing private network with non-public network | 16.6.0 |
+| 2018-12 | SP-82 | SP-181005 | 0333 | 2 | B | cyberCAV - network interaction requirement for uninterrupted real-time video | 16.6.0 |
+| 2018-12 | SP-82 | SP-181129 | 0303 | 1 | B | MSGin5G requirements on the 5G system | 16.6.0 |
+| 2018-12 | SP-82 | SP-181003 | 0343 | 2 | C | Update to Annex F for Network Diagnostics | 16.6.0 |
+| 2018-12 | SP-82 | SP-180997 | 0348 | 1 | F | Minor correction to URLLC clause | 16.6.0 |
+| 2018-12 | SP-82 | SP-181002 | 0313 | | F | Editorial correction in header | 16.6.0 |
+| 2018-12 | SP-82 | SP-181002 | 0312 | 2 | F | Clause 7.2 alignment with other Rel-16 WIDs | 16.6.0 |
+| 2018-12 | SP-82 | SP-181002 | 0349 | 2 | D | Move of KPIs for wireless RSU-TCC backhaul to 7.2.3 | 16.6.0 |
+| 2019-03 | SA#83 | SP-190080 | 0354 | | F | Correction to the definition of communication service availability | 16.7.0 |
+| 2019-03 | SA#83 | SP-190080 | 0355 | 2 | F | Clarifications of bulk authentication | 16.7.0 |
+| 2019-03 | SA#83 | SP-190082 | 0351 | 1 | F | Clarification for 5GLAN requirements | 16.7.0 |
+| 2019-03 | SA#83 | SP-190080 | 0352 | 1 | F | Update the Annex D in TS 22.261 to align the references | 16.7.0 |
+| 2019-03 | SA#83 | SP-190080 | 0353 | 1 | D | Editorial clean-up of TS 22.261 | 16.7.0 |
+| 2019-06 | SA#84 | SP-190302 | 0363 | 3 | F | National or regional regulatory requirements for satellite access | 16.8.0 |
+| 2019-06 | SA#84 | SP-190298 | 0361 | | D | Editorial clean-up of TS 22.261 | 16.8.0 |
+| 2019-06 | SA#84 | SP-190298 | 0359 | 2 | D | Changing 'authorized user' to 'authorized entity' in requirements where an end user is not involved | 16.8.0 |
+| 2019-06 | SA#84 | SP-190298 | 0360 | 2 | F | Abbreviations of TS 22.261 | 16.8.0 |
+| 2019-06 | SA#84 | SP-190298 | 0362 | 2 | F | Addition of selection Relay requirements to 22.261 | 16.8.0 |
+| 2019-09 | SA#85 | SP-190803 | 0397 | 1 | F | Modification of positioning service and high accuracy positioning | 16.9.0 |
+| 2019-09 | SA#85 | SP-190812 | 0392 | 3 | C | Definition of absolute and relative positioning | 16.9.0 |
+| 2019-09 | SA#85 | SP-190798 | 0380 | | D | Editorial corrections of TS 22.261 | 16.9.0 |
+| 2019-09 | SA#85 | SP-190798 | 0367 | 1 | F | Clarification of dynamic policy control requirements | 16.9.0 |
+| 2019-09 | SA#85 | SP-190798 | 0368 | 2 | F | Clarification of geographic constraint on a network slice | 16.9.0 |
+| 2019-09 | SA#85 | SP-190798 | 0383 | 2 | F | Clarify requirements for bulk IoT operation and authentication | 16.9.0 |
+| 2019-09 | SA#85 | SP-190798 | 0399 | 3 | F | Clarifications for KPIs on Low latency and high reliability scenarios | 16.9.0 |
+| 2019-09 | SA#85 | SP-190807 | 0371 | 1 | B | Addition of security requirements for critical medical applications | 17.0.0 |
+| 2019-09 | SA#85 | SP-190807 | 0372 | 1 | B | Addition of medical telemetry requirements | 17.0.0 |
+| 2019-09 | SA#85 | SP-190821 | 0381 | 2 | B | Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode | 17.0.0 |
+| 2019-09 | SA#85 | SP-190817 | 0390 | 4 | B | 22.261 - Asset Tracking Description and Requirements | 17.0.0 |
+| 2019-09 | SA#85 | SP-190815 | 0365 | 2 | B | Introduction of Minimization of Service Interruption (MINT) | 17.0.0 |
+| 2019-09 | SA#85 | SP-190817 | 0391 | 4 | B | KPIs for Asset Tracking in 5G system | 17.0.0 |
+| 2019-09 | SA#85 | SP-190809 | 0382 | 2 | B | General description for UAV aspects | 17.0.0 |
+| 2019-09 | SA#85 | SP-190812 | 0394 | 2 | B | eCAV – further 5G service requirements for network operation and management | 17.0.0 |
+| 2019-09 | SA#85 | SP-190805 | 0377 | 1 | B | Service hosting environment aspects of interactive service | 17.0.0 |
+| 2019-09 | SA#85 | SP-190805 | 0375 | 3 | B | Performance requirements of interactive service | 17.0.0 |
+| 2019-09 | SA#85 | SP-190808 | 0386 | 1 | B | Connectivity models description section updated. | 17.0.0 |
+| 2019-09 | SA#85 | SP-190808 | 0387 | 1 | B | Connectivity models new functional requirements | 17.0.0 |
+| 2019-09 | SA#85 | SP-190808 | 0388 | 1 | B | KPIs for UE to network relaying in 5G system | 17.0.0 |
+| 2019-10 | - | - | - | - | - | Adding missing carriage return between the last sentence of clause 6.31.2.1 and clause 6.31.2.2, also at the end of 6.31.2.2 before 6.31.2.3 | 17.0.1 |
+| 2019-12 | SA#86 | SP-191010 | 0418 | 1 | A | UAC for NB-IOT | 17.1.0 |
+| 2019-12 | SA#86 | SP-191010 | 0432 | 1 | A | Clarifications and updates on the description of positioning use | 17.1.0 |
+
+| | | | | | | | |
+|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------|--------|
+| | | | | | | cases in Annex B and Annex E | |
+| 2019-12 | SA#86 | SP-191012 | 0411 | 1 | A | Unified Access Control for IMS registration related signalling | 17.1.0 |
+| 2019-12 | SA#86 | SP-191014 | 0403 | 4 | B | CR for group communication in 5G system | 17.1.0 |
+| 2019-12 | SA#86 | SP-191014 | 0405 | 2 | B | Tethered VR requirement for 5G | 17.1.0 |
+| 2019-12 | SA#86 | SP-191014 | 0413 | 2 | F | Update of NCIS KPI requirements | 17.1.0 |
+| 2019-12 | SA#86 | SP-191016 | 0420 | 3 | B | Addition of AVProd introduction in 22.261 | 17.1.0 |
+| 2019-12 | SA#86 | SP-191020 | 0426 | | C | Updating integrity protection requirement based on consolidated CMED requirements | 17.1.0 |
+| 2019-12 | SA#86 | SP-191020 | 0416 | 2 | B | Addition of general section 6.x for CMED | 17.1.0 |
+| 2019-12 | SA#86 | SP-191023 | 0422 | 1 | B | Establishment of an indirect network connection | 17.1.0 |
+| 2019-12 | SA#86 | SP-191023 | 0421 | 3 | C | Clarification of requirements | 17.1.0 |
+| 2019-12 | SA#86 | SP-191028 | 0430 | 3 | B | Operator provided end-to-end security for factory networks | 17.1.0 |
+| 2019-12 | SA#86 | SP-191032 | 0378 | 4 | B | On Access control for MINT | 17.1.0 |
+| 2019-12 | SA#86 | SP-191034 | 0384 | 7 | B | Broadcast / multicast requirements supporting Mission Critical Services in 5G | 17.1.0 |
+| 2019-12 | SA#86 | SP-191035 | 0425 | 2 | B | Supporting IMS emergency for NPN | 17.1.0 |
+| 2019-12 | SA#86 | SP-191036 | 0412 | 1 | F | Clarify requirements for bulk IoT authentication | 17.1.0 |
+| 2019-12 | SA#86 | SP-191036 | 0423 | 2 | D | Editorial changes and corrections | 17.1.0 |
+| 2019-12 | SA#86 | SP-191036 | 0419 | 2 | C | VR requirement for 5G | 17.1.0 |
+| 2020-03 | SA#87 | SP-200122 | 0436 | 1 | A | Manual CAG selection clarification | 17.2.0 |
+| 2020-07 | SA#88e | SP-200563 | 0454 | | A | correction to access control for NB-IoT | 17.3.0 |
+| 2020-07 | SA#88e | SP-200565 | 0442 | 1 | D | Addition of generic 5G requirements for VIAPA | 17.3.0 |
+| 2020-07 | SA#88e | SP-200569 | 0428 | 4 | B | Performance requirements for satellite access | 17.3.0 |
+| 2020-09 | SA#89e | SP-200784 | 0456 | 1 | A | Addition of Human Readable Network Name | 17.4.0 |
+| 2020-09 | SA#89e | SP-200889 | 0462 | 2 | D | Quality improvement of TS 22.261 (R17) – editorial modifications | 17.4.0 |
+| 2020-09 | SA#89e | SP-200818 | 0472 | 1 | B | Addition of requirements on Subscriber-aware Northbound API access | 18.0.0 |
+| 2020-12 | SA#90e | SP-201029 | 482 | 1 | A | Quality improvement of TS 22.261 | 18.1.0 |
+| 2020-12 | SA#90e | SP-201029 | 480 | 1 | A | Correction of Access Identities Table in clause 6.22.2.2 | 18.1.0 |
+| 2020-12 | SA#90e | SP-201025 | 489 | 1 | A | Clarification of a steering of roaming requirement | 18.1.0 |
+| 2020-12 | SA#90e | SP-201140 | 0478 | 3 | B | Service requirements for enhancing service function chaining support by 5G network | 18.1.0 |
+| 2021-01 | - | | | | | CR 478r3 was meant to add one clause and its subclauses under section 6 and not to add a new section 10. This is corrected here. | 18.1.1 |
+| 2021-03 | SA#91e | SP-210199 | 504 | 1 | C | Clarification to KPIs for a 5G system with satellite access | 18.2.0 |
+| 2021-03 | SA#91e | SP-210215 | 496 | 1 | B | update of CR of Addition of requirements on Data integrity in 5G | 18.2.0 |
+| 2021-03 | SA#91e | SP-210198 | 500 | 1 | A | Modification of requirements for network slice constraints | 18.2.0 |
+| 2021-06 | SA#92e | SP-210498 | 0528 | 1 | A | Clarification for Congestion Avoidance for MINT | 18.3.0 |
+| 2021-06 | SA#92e | SP-210502 | 0524 | 1 | A | Editorial correction for network capability exposure and abbreviation | 18.3.0 |
+| 2021-06 | SA#92e | SP-210564 | 531 | | A | Quality improvement - clarification of QoS-monitoring requirement | 18.3.0 |
+| 2021-06 | SA#92e | SP-210564 | 530 | 1 | A | Quality improvement - updating the definition of communication service availability | 18.3.0 |
+| 2021-06 | SA#92e | SP-210565 | 508 | 1 | D | Quality improvement - update of Annex C | 18.3.0 |
+| 2021-06 | SA#92e | SP-210565 | 512 | 1 | D | Quality improvement - update of annex D | 18.3.0 |
+| 2021-06 | SA#92e | SP-210565 | 513 | 1 | D | Quality improvement - update of clause F.1 | 18.3.0 |
+| 2021-06 | SA#92e | SP-210565 | 514 | 1 | D | Quality improvement - voiding annex A and B | 18.3.0 |
+| 2021-06 | SA#92e | SP-210516 | 0505 | 1 | B | New service requirements for EASNS | 18.3.0 |
+| 2021-06 | SA#92e | SP-210517 | 0507 | 1 | B | 5G timing resiliency | 18.3.0 |
+| 2021-06 | SA#92e | SP-210518 | 0506 | 1 | B | Adding High-level and Performance Requirements for Ranging | 18.3.0 |
+| 2021-06 | SA#92e | SP-210524 | 0515 | | C | Clarification of LPHAP requirements | 18.3.0 |
+| 2021-06 | SA#92e | SP-210524 | 0526 | | D | Alignment of positioning power consumption aspects between 22.261 and 22.104 | 18.3.0 |
+| 2021-06 | SA#92e | SP-210529 | 0525 | 1 | B | Requirements for satellite backhaul | 18.3.0 |
+| 2021-09 | SA#93e | SP-211039 | 0518 | 3 | F | Clarification of NPN in 22.261 | 18.4.0 |
+| 2021-09 | SA#93e | SP-211069 | 0519 | 2 | B | Update to KPIs to 5G system with satellite access for support control and/or video surveillance | 18.4.0 |
+| 2021-09 | SA#93e | SP-211063 | 0533 | 1 | B | 5G LAN related requirements from FS Resident (Pirates) | 18.4.0 |
+| 2021-09 | SA#93e | SP-211063 | 0534 | | C | Application Server related requirements from FS Resident (pirates) | 18.4.0 |
+| 2021-09 | SA#93e | SP-211063 | 0535 | 1 | B | Pirates definitions and abbreviations | 18.4.0 |
+| 2021-09 | SA#93e | SP-211063 | 0536 | 1 | B | Pirates general introduction | 18.4.0 |
+| 2021-09 | SA#93e | SP-211063 | 0539 | 1 | B | Pirates requirements | 18.4.0 |
+| 2021-09 | SA#93e | SP-211038 | 0541 | 1 | A | EXPOSE: editorial improvement of a QoS monitoring requirement | 18.4.0 |
+| 2021-09 | SA#93e | SP-211071 | 0542 | 1 | B | EXPOSE: addition to QoS monitoring requirements | 18.4.0 |
+| 2021-09 | SA#93e | SP-211071 | 0543 | 1 | F | EXPOSE: correction of a QoS monitoring requirement | 18.4.0 |
+| 2021-09 | SA#93e | SP-211071 | 0544 | 1 | B | EXPOSE: addition of position accuracy | 18.4.0 |
+| 2021-09 | SA#93e | SP-211039 | 0546 | 1 | D | Miscellaneous corrections from CR implementation | 18.4.0 |
+| 2021-09 | SA#93e | SP-211070 | 0547 | 1 | B | Introduction of Smart Energy Infrastructure Requirements | 18.4.0 |
+| 2021-09 | SA#93e | SP-211060 | 0549 | 1 | B | Evolution of IMS Multimedia Telephony Service | 18.4.0 |
+| 2021-09 | SA#93e | SP-211070 | 0550 | 1 | B | Introduce of Smart Grid service | 18.4.0 |
+| 2021-09 | SA#93e | SP-211062 | 0551 | 1 | B | Adding requirements for AMMT | 18.4.0 |
+| 2021-09 | SA#93e | SP-211062 | 0552 | 1 | B | CR22.261v18.3.0 Adding performance requirements for AMMT | 18.4.0 |
+| 2021-09 | SA#93e | SP-211030 | 0557 | 1 | A | Correction to Reliability definition | 18.4.0 |
+
+| | | | | | | | |
+|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------|---------|
+| 2021-09 | SA#93e | SP-211032 | 0559 | 1 | A | Removal of user intervention on services exempted from release due to SOR | 18.4.0 |
+| 2021-09 | SA#93e | SP-211064 | 0560 | 1 | B | Introducing PALS Normative Requirements | 18.4.0 |
+| 2021-09 | SA#93e | SP-211039 | 0564 | 1 | B | Support multiple non-public networks access and corresponding simultaneous services for a UE | 18.4.0 |
+| 2021-09 | SA#93e | SP-211070 | 0565 | | B | Addition of requirements for Confidentiality in 5GS (SEI) | 18.4.0 |
+| 2021-09 | SA#93e | SP-211096 | 0567 | 1 | D | Editorial corrections for references, abbreviations and clauses 6.36, 8.10 and 9.3 | 18.4.0 |
+| 2021-09 | SA#93e | SP-211066 | 0568 | 1 | B | Introduction of VMR requirements | 18.4.0 |
+| 2021-09 | SA#93e | SP-211096 | 0571 | 1 | A | Correction of 'air interface' terminology | 18.4.0 |
+| 2021-09 | SA#93e | SP-211096 | 0576 | 1 | A | UAS terminology alignment | 18.4.0 |
+| 2021-09 | SA#93e | SP-211070 | 0577 | 2 | B | Inclusion of Smart Energy Infrastructure Requirements | 18.4.0 |
+| 2021-12 | SP-94 | SP-211495 | 0582 | | A | Editorial corrections to clause 6.23.2 (QoS monitoring) | 18.5.0 |
+| 2021-12 | SP-94 | SP-211488 | 0583 | 1 | F | Correction of network condition change per UE | 18.5.0 |
+| 2021-12 | SP-94 | SP-211500 | 0587 | 1 | A | Clarification of NPN in 22.261 | 18.5.0 |
+| 2021-12 | SP-94 | SP-211493 | 0588 | | F | Adding Informative Annex for PALS | 18.5.0 |
+| 2021-12 | SP-94 | SP-211497 | 0590 | 1 | D | Alignment with new added smart grid | 18.5.0 |
+| 2021-12 | SP-94 | SP-211501 | 0593 | 1 | A | Clarification to NPN requirements on USIM and multiple subscriptions | 18.5.0 |
+| 2021-12 | SP-94 | SP-211488 | 0597 | 1 | B | Adding requirement of FL for AMMT | 18.5.0 |
+| 2021-12 | SP-94 | SP-211488 | 0598 | 1 | F | Adding definition of terminology for AMMT | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0599 | 1 | B | Update the general section of PIRates | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0600 | 1 | B | Update the gateways section of PIRates | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0602 | 1 | C | Update the discovery section of PIRates | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0604 | 1 | C | Update the creation and management section of PIRates | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0605 | 1 | F | Correction on the definition of PIN and PIN Element | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0607 | | F | Correction for 5G-RG | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0610 | 1 | B | Pirates general introduction missing background text | 18.5.0 |
+| 2021-12 | SP-94 | SP-211498 | 0611 | 2 | B | TACMM CR Introduction of text for Tactile and multi-modal communication service | 18.5.0 |
+| 2021-12 | SP-94 | SP-211493 | 0614 | 1 | F | Clarification of Service Providers for PALS | 18.5.0 |
+| 2021-12 | SP-94 | SP-211502 | 0619 | | F | CR adding NPN clarification plus editorials | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0622 | 2 | B | Adding leftover PIN requirement to normative spec | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0623 | 2 | F | Replacing undefined term PIN User | 18.5.0 |
+| 2021-12 | SP-94 | SP-211494 | 0624 | 2 | F | Clarifying Lawful Intercept requirements | 18.5.0 |
+| 2021-12 | SP-94 | SP-211500 | 0626 | | A | NPN support for positioning service requirement | 18.5.0 |
+| 2021-12 | SP-94 | SP-211493 | 0627 | 1 | B | Addition of PALS requirement for manual selection | 18.5.0 |
+| 2021-12 | SP-94 | SP-211499 | 0628 | 1 | A | Clarification of NPN in 22.261 | 18.5.0 |
+| 2021-12 | SP-94 | SP-211488 | 0629 | | B | Update to charging requirements for AMMT | 18.5.0 |
+| 2022-03 | SP#95e | SP-220080 | 0633 | 1 | F | Clarification of KPI in TS22.261 clause 7.10 for AMMT use case | 18.6.0 |
+| 2022-03 | SP#95e | SP-220080 | 0634 | 1 | F | Clarification of 5GC assistance for FL member selection | 18.6.0 |
+| 2022-03 | SP#95e | SP-220080 | 0630 | 1 | F | Clarification of terminology for localized services | 18.6.0 |
+| 2022-03 | SP#95e | SP-220080 | 0631 | 1 | F | Correction to CPN Requirements | 18.6.0 |
+| 2022-03 | SP#95e | SP-220081 | 0636 | | A | Clarification of SoR requirements | 18.6.0 |
+| 2022-03 | SP#95e | SP-220082 | 0632 | 1 | F | Update the use of may and can for quality improvement | 18.6.0 |
+| 2022-06 | - | - | - | - | - | Carriage return that was missing just before 6.41.1 has been introduced | 18.6.1 |
+| 2022-09 | SA#97 | SP-220932 | 649 | 1 | A | Add requirements on maximum capacity of network slicing | 18.7.0 |
+| 2022-09 | SA#97 | SP-220933 | 653 | 1 | D | Clean-up of the references for quality improvement | 18.7.0 |
+| 2022-12 | SA#98 | SP-221259 | 0664 | 1 | D | Editorial Corrections to TS 22.261 on PALS | 18.8.0 |
+| 2023-03 | SA#99 | SP-230217 | 0675 | 1 | F | Clarification on AI-ML KPIs | 18.9.0 |
+| 2023-03 | SA#99 | SP-230216 | 0673 | 1 | F | Corrections to PALS | 18.9.0 |
+| 2023-03 | SA#99 | SP-230215 | 0669 | 1 | D | Miscellaneous corrections to Ranging | 18.9.0 |
+| 2023-06 | SA#100 | SP-230527 | 0686 | 2 | F | Clarification on AI-ML KPIs | 18.10.0 |
+| 2023-09 | SA#101 | SP-231173 | 727 | 2 | B | Roaming service providers enablement in 5G | 18.11.0 |
+| 2023-12 | SA#102 | SP-231393 | 0733 | 2 | F | Clarification of usage of default slice in roaming | 18.12.0 |
+| 2023-12 | SA#102 | SP-231394 | 0753 | 1 | A | Correction of requirement in subclause 6.3 (Multiple access technologies) | 18.12.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22262/5d76c2e9976aaf97001ee189908830fb_img.jpg b/marked/Rel-18/22_series/22262/5d76c2e9976aaf97001ee189908830fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..beae33826f9fe45e29294a185bde400162254184
--- /dev/null
+++ b/marked/Rel-18/22_series/22262/5d76c2e9976aaf97001ee189908830fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9616860b3ef4b2f08bc0c00ab568a39f237eef1b6c8069ef1c2b09df27132672
+size 62986
diff --git a/marked/Rel-18/22_series/22262/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22262/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3dc1d881ebe542907c1a98824c968496397d3cc7
--- /dev/null
+++ b/marked/Rel-18/22_series/22262/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c87e16b820c12ee6d768ee401504b51cb957c46932ecdeb309e8d2023ab9f61c
+size 9581
diff --git a/marked/Rel-18/22_series/22262/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22262/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1208d9ede4d48cfe439824a01f403864c2008a7
--- /dev/null
+++ b/marked/Rel-18/22_series/22262/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be29198e697df1024555dea683d176fe4cdabe41c9cae3a2173506ca3ae6e032
+size 7160
diff --git a/marked/Rel-18/22_series/22262/raw.md b/marked/Rel-18/22_series/22262/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..97f5f2ac7323c8c2bc98eab12a656e67907b48b1
--- /dev/null
+++ b/marked/Rel-18/22_series/22262/raw.md
@@ -0,0 +1,357 @@
+
+
+# 3GPP TS 22.262 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Message Service within the 5G System; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+5G, message service
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+### --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|---------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.3 Abbreviations ..... | 5 |
+| 4 Overview..... | 6 |
+| 4.1 General ..... | 6 |
+| 4.2 Message communication models ..... | 6 |
+| 5 Service requirements..... | 7 |
+| 5.1 General ..... | 7 |
+| 5.1.1 Description ..... | 7 |
+| 5.1.2 Requirements..... | 7 |
+| 5.2 Point-to-point message..... | 8 |
+| 5.2.1 Description ..... | 8 |
+| 5.2.2 Requirements..... | 8 |
+| 5.3 Application-to-point message ..... | 8 |
+| 5.3.1 Description ..... | 8 |
+| 5.3.2 Requirements..... | 8 |
+| 5.4 Group message ..... | 9 |
+| 5.4.1 Description ..... | 9 |
+| 5.4.2 Requirements..... | 9 |
+| 5.5 Broadcast message ..... | 9 |
+| 5.5.1 Description ..... | 9 |
+| 5.5.2 Requirements..... | 9 |
+| 6 Charging..... | 9 |
+| 6.1 Description ..... | 9 |
+| 6.2 Requirements..... | 9 |
+| 7 Security ..... | 10 |
+| 7.1 Description ..... | 10 |
+| 7.2 Requirements..... | 10 |
+| 8 Roaming..... | 10 |
+| 8.1 Description ..... | 10 |
+| 8.2 Requirements..... | 10 |
+| 9 Interconnection..... | 10 |
+| 9.1 Description ..... | 10 |
+| 9.2 Requirements..... | 10 |
+| 10 Interworking..... | 11 |
+| 10.1 Description ..... | 11 |
+| 10.2 Requirements..... | 11 |
+| Annex A (informative): Change history..... | 11 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 present document covers requirements for a message service used for person-to-thing and thing-to-thing communication within the 5G system (represented by the term MSGin5G Service).
+
+# --- 1 Scope
+
+The present document provides the service requirements for operation of the MSGin5G Service. The MSGin5G Service provides point-to-point, application-to-point, group and broadcast message delivery for person-to-thing communication and thing-to-thing communication.
+
+# --- 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".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**application-to-point message:** message that is originated at a UE and terminated at an application server in the network or originated at an application server in the network and terminated at a UE.
+
+**MSGin5G Service:** a MNO message service within the 5G System that enables point-to-point, application-to-point, group and broadcast message delivery for thing-to-thing communication and person-to-thing communication.
+
+**MSGin5G Server:** an entity in the 5G system for routing messages between UEs and messages between application servers and UEs.
+
+**MSGin5G Gateway:** an entity in the 5G system for interworking between the MSGin5G Service and non-3GPP message service.
+
+**point-to-point message:** message that is originated at a UE and terminated at a UE.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|------------------------------------------|
+| AOMT | Application Originated Mobile Terminated |
+| IoT | Internet of Things |
+| MIoT | Massive Internet of Things |
+| MOAT | Mobile Originated Application Terminated |
+| MOMT | Mobile Originated Mobile Terminated |
+| NIDD | Non IP Data Delivery |
+
+# 4 Overview
+
+## 4.1 General
+
+Massive Internet of Things (MIoT) is one of key market segments of 5G. The typical IoT device communication is sending and receiving small data which can be delivered just in a message. Today SMS is used as message enabler for some IoT applications. However, SMS has limitation in term of service capabilities (e.g. 140 bytes payload) and performance (e.g. long latency), in addition, the overhead of control plane resource is high. There have been enhancements and optimizations on the 3GPP network capabilities to facilitate IoT applications including device triggering, small data transfer, and Non IP Data Delivery (NIDD) etc.
+
+Nevertheless, the characteristics of MIoT devices including high density connection, flexible mobility, saving power, limited computing capability, bulk of devices, and traffic pattern of short burst of small data will bring various new demands on message communication, e.g. light weight message communication for provision and monitoring, ultra low latency and high reliability message communication for remote control, and extremely high resource efficiency for large scale connections.
+
+The MSGin5G Service is basically designed and optimized for massive IoT device communication including thing-to-thing communication and person-to-thing communication.
+
+## 4.2 Message communication models
+
+
+
+Figure 4.2 a: The MSGin5G Service overview. The diagram shows a 5G System (dashed box) containing an MSGin5G Server connected to a 5G Core/Access Network. Two external servers, APP1 Server and APP2 Server, are connected to the MSGin5G Server. Below the 5G Core, four User Equipment (UE) units are shown: UE A, UE B, UE C, and UE D. UE A and UE B are connected to the 5G Core and contain an MSGin5G Service. UE C is connected to the 5G Core and contains an SMS service. UE D is connected to the 5G Core via an MSGin5G Gateway and contains a Non-3GPP Message service. Applications (APP1, APP2) are shown within the UEs, connected to their respective message services.
+
+**Figure 4.2 a: The MSGin5G Service overview**
+
+The MSGin5G Service is a message enabler for applications. An application client (APP1 Client) in UE A utilizes MSGin5G Service to send a message to UE B. This message will be routed to UE B via the 5G system, or this message will be first routed to the application server (APP1 Server) and then forwarded to UE B. If the terminated UE (UE C) supports SMS but does not support the MSGin5G Service, the message will be translated to SMS by MSGin5G Server. A UE (UE D) that does not support 3GPP message service can connect to the MSGin5G Service via MSGin5G Gateway that facilitates the translation between the MSGin5G Service and non-3GPP message service. The connection between the UE D and the gateway can be via 3GPP access or non 3GPP access (e.g. WLAN).
+
+The message communication models include:
+
+- point-to-point message: message that is originated at a UE and terminated at a UEs.
+
+- application-to-point message: message that is originated at a UE and terminated at an application server in the network or originated at an application server in the network and terminated at a UE.
+- group message: messages are originated at a UE and terminated at a group of UEs (the members of a group can be located in different geographical areas).
+- broadcast message: messages are originated at an application server in the network or an UE and terminated at all the UEs in a specific service area within a cell or multiple cells.
+
+# --- 5 Service requirements
+
+## 5.1 General
+
+### 5.1.1 Description
+
+The MSGin5G Service enables various message communication models with advanced service capabilities and performance. In addition to point-to-point, application-to-point, group and broadcast message communication are supported in the MSGin5G Service. To meet the requirements of remote control, the MSGin5G Service needs to provide very low end-to-end latency and high reliability of message delivery.
+
+Considering the massive connections of IoT devices and high throughput of message communication between devices or between devices and application servers, the MSGin5G Service needs to be in a resource efficient manner to optimize the resource usage of the both control plane and user plane. The IoT devices usually have limitation in computation and storage, and are powered by batteries or small solar photovoltaic equipment, so the message communications need to be light weight and well scheduled in order to save power and data traffic consumption in the device.
+
+### 5.1.2 Requirements
+
+[R-5.1.2-001] The MSGin5G Service shall support UE sending and receiving a text or data message with end-to-end latency less than [500] ms.
+
+NOTE 1: Initial connection activation latencies may be longer depending on receiving UE power saving states, paging, etc.
+
+[R-5.1.2-002] The MSGin5G Service shall support variable size of payload of a text or data message with maximum [2048] bytes, and support segmented transmission if the content is large than the maximum payload length of a message.
+
+[R-5.1.2-003] The MSGin5G Service shall support delivery of a message to a specific application in the terminated UE. This message contains the contents that can be handled by the specific application.
+
+[R-5.1.2-004] The MSGin5G Service shall support acknowledgement of delivery status (success, failure) of a message and indication of reason if the delivery is failed.
+
+[R-5.1.2-005] The MSGin5G Service shall support storage of a message if a UE is unavailable (disconnected or power off) for future delivery once the UE becomes available.
+
+[R-5.1.2-006] The MSGin5G Service shall support a server in the network triggering the UE to perform an action (e.g. wake up and establish a PDN connection).
+
+[R-5.1.2-007] The MSGin5G Service shall support a UE sending and receiving messages via a MSGin5G Gateway
+
+NOTE 2: The connection between the UE and the MSGin5G Gateway can be 3GPP or non-3GPP access (e.g. WLAN.)
+
+[R-5.1.2-008] The MSGin5G Service shall support the mobility of a UE (i.e. the UE can still send/receive messages when it changes the location of network access).
+
+[R-5.1.2-009] The MSGin5G Service shall support per-message information for store and forward, e.g. whether the message can be buffered or how long the message is valid.
+
+## 5.2 Point-to-point message
+
+### 5.2.1 Description
+
+The typical IoT communication happens between a person and a thing or two things, where the messages are Mobile Originated and Mobile Terminated (MOMT). A person can use his mobile handset to communicate with multiple smart devices, e.g. wearable devices like intelligent watch and smart home devices like air conditioner. These smart devices may have USIM or not. The MSGin5G Service needs to support addressing the UE by IMSI/MSISDN or IMEI.
+
+There are different applications in a UE that will use point-to-point messages. The MSGin5G Service needs to identify which application a message is to be delivered to and hence route the message to the corresponding application server in the network and application client in the UE.
+
+### 5.2.2 Requirements
+
+[R-5.2.2-001] The MSGin5G Service shall support Mobile Originated Mobile Terminated (MOMT) messaging, i.e. messages are originated and terminated at UEs.
+
+[R-5.2.2-002] The MSGin5G Service shall support addressing the UE by IMSI/MSISDN or IMEI.
+
+[R-5.2.2-003] The MSGin5G Service shall support a mechanism to identify the applicable application and route a MOMT message to the corresponding application server in the network and application client in the UE.
+
+## 5.3 Application-to-point message
+
+### 5.3.1 Description
+
+The application-to-point message enables sending/receiving message between an application server and an IoT device. The message can be Mobile Originated Application Terminated (MOAT) and Application Originated Mobile Terminated (AOMT). The MOAT messages can be used by devices for reporting the small data. For example, in environmental monitoring, a monitoring device sends a message to the application server to report the collected data by the sensor every hour. The AOMT messages can be used by an application server to manage or control the devices. For example, in shared bike communication, the application server sends a message to a bike to unlock the bike.
+
+One type of devices need to report data to the application server in a scheduled way (e.g. every hour). Another type of devices need to be reachable by the application server in a non-scheduled way, e.g. the server updates the configuration of the device. An IoT device that is powered by batteries or small solar photovoltaic equipment, needs to access the MSGin5G Service in the whole lifecycle (e.g. 10 years), which requires the MSGin5G Service be very light weight in power consumption. The AOMT messages are time sensitive. The MSGin5G Service needs to support low latency delivery of AOMT messages.
+
+### 5.3.2 Requirements
+
+[R-5.3.2-001] The MSGin5G Service shall support Mobile Originated Application Terminated (MOAT) messaging, i.e. messages are originated at a UE and terminated at an application server in the network.
+
+[R-5.3.2-002] The MSGin5G Service shall support Application Originated Mobile Terminated (AOMT) messaging, i.e. messages are originated at an application server in the network and terminated at a UE.
+
+[R-5.3.2-003] The MSGin5G Service shall support Application Originated Mobile Terminated messaging service with max latency of 10 seconds while maintaining battery life of at least 3 months for small data traffic once every hour and typical sized IOT battery [200-500mAh].
+
+## 5.4 Group message
+
+### 5.4.1 Description
+
+In 5G IoT communication, there is a need that a group of devices can communicate with each other, which means the message sent by a device will be received by all the other devices in the group. The members of a group can be devices for persons and smart things that are located in different geographical areas. Group management mechanism is required to support the members joining or leaving a group.
+
+### 5.4.2 Requirements
+
+[R-5.4.2-001] The MSGin5G Service shall support group message communication, i.e. a UE sends a message to a group of UEs. All the members in a group can send messages. The UEs in a group can be located in different geographical areas.
+
+[R-5.4.2-002] The MSGin5G Service shall support group management for message communication:
+
+- establishing/deleting a group
+- adding UEs to the group or removing UEs from the group
+- configuration of a maximum number of members in a group
+
+## 5.5 Broadcast message
+
+### 5.5.1 Description
+
+The MSGin5G Service for MIoT needs to support broadcast message delivery in order to handle the massive communications efficiently without long latency. The receivers of broadcast messages can be all UEs within a cell or multiple cells. The broadcast areas can be configured according to the policy of application.
+
+To avoid malicious attack, only authorized UEs or application server can send broadcast messages.
+
+### 5.5.2 Requirements
+
+[R-5.5.2-001] The MSGin5G Service shall support broadcasting a text or data message with end-to-end latency less than [500] ms.
+
+[R-5.5.2-002] The MSGin5G Service shall support an authorized application server or UE to send a broadcast message to all the UEs within a specific area which is configured according to application policy.
+
+# --- 6 Charging
+
+## 6.1 Description
+
+The business model of MIoT market may be different from that of consumer market. The MNO may need flexible policy for charging of the MSGin5G Service, e.g., flat rate (per month or per year), charge per message, and charge by amount of data. For different message communication models, the charging policy may be distinguished. The MSGin5G Service needs to provide charging information to support different charging policy.
+
+## 6.2 Requirements
+
+[R-6.2-001] The MSGin5G Service shall be able to collect charging information of a UE according to the operator's charging policy including charge per message, charge by amount of data, and flat rate (e.g., per month or per year).
+
+[R-6.2-002] The MSGin5G Service shall be able to collect charging information of an application provider in application-to-point message communication.
+
+# --- 7 Security
+
+## 7.1 Description
+
+The messages of thing-to-thing or person-to-thing can be critical, e.g., a message for remote control may trigger actions of a device. To protect an IoT device from malicious attack, only authorized UEs can send messages to this device. In addition, the content of messages need to be integrity and confidentiality protected.
+
+The IoT devices may be battery-powered, so the security mechanism for MSGin5G needs to be light weight.
+
+## 7.2 Requirements
+
+[R-7.2-001] The MSGin5G Service shall support a mechanism for the operator to configure the allow-list of UEs that are authorized to send messages to a specific UE. The MSGin5G Service shall be able to block messages from non-authorized UEs.
+
+[R-7.2-002] The MSGin5G Service shall support integrity and confidentiality protection for the payload of a message.
+
+# --- 8 Roaming
+
+## 8.1 Description
+
+The IoT device can be a device equipped in a vehicle moving from one nation to another nation. When roaming, the device needs to be able to access to the MSGin5G Service.
+
+## 8.2 Requirements
+
+[R-8.2-001] The MSGin5G Service shall support a roaming UE sending and receiving messages.
+
+# --- 9 Interconnection
+
+## 9.1 Description
+
+The MSGin5G Service is a service that can involve two different operators on originating and terminating side, and hence interconnection is needed.
+
+## 9.2 Requirements
+
+[R-9.2-001] The MSGin5G Service shall support an UE within an operator sending a message to another UE within another operator.
+
+[R-9.2-002] The MSGin5G Service shall support an application server sending/receiving a message to/from a UE within another operator.
+
+# 10 Interworking
+
+## 10.1 Description
+
+The legacy IoT devices have been widely deployed. These devices may support legacy message service like SMS. When the terminated UE does not support the MSGin5G Service, interworking between MSGin5G Service and another message service (e.g., SMS) is required subject to the operator's policy.
+
+## 10.2 Requirements
+
+[R-10.2-001] The MSGin5G Service shall be able to interwork with SMS for point-to-point message and application-to-point message.
+
+[R-10.2-002] The MSGin5G Service shall be able to translate one message into multiple SMS messages when the length of a message of MSGin5G Service is large than the maximum length of a SMS message.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|------|-----|----------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New version |
+| 2018-11 | SA1#84 | S1-183137 | | | | Including agreed docs: S1-183038, S1-183472, S1-183457, S1-183454, S1-183096, S1-183456, S1-183152 | 0.1.0 |
+| 2018-12 | SA#82 | SP-181010 | - | - | - | Presentation for one-step approval to SA | 1.0.0 |
+| 2018-12 | SA#82 | SP-181010 | - | - | - | Raised to v.16.0.0 following SA#82's one-step approval | 16.0.0 |
+| 2021-09 | SA#93e | SP-211033 | 0001 | 2 | F | MSGin5G store-and-forward modifications | 17.0.0 |
+| 2022-03 | SP#95e | SP-220081 | 0002 | 1 | D | Non-inclusive language replacement | 17.1.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22268/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22268/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3cf838d69a0b53b22eb93189d368bf6c86a3a4ee
--- /dev/null
+++ b/marked/Rel-18/22_series/22268/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:349e6c58987c0ba860981f7bb4c5a949c2eaa5f9e13d3ba1bc98d3d41f26174b
+size 8202
diff --git a/marked/Rel-18/22_series/22268/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22268/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a10f769b9ea3bca9468b9a1211bfbbf1b1614af3
--- /dev/null
+++ b/marked/Rel-18/22_series/22268/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5a9959338e8483259bbd54b75a5dcce8396e878f4425435e64934d0730340f3
+size 7232
diff --git a/marked/Rel-18/22_series/22268/raw.md b/marked/Rel-18/22_series/22268/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a88953ab12c5afed427d5880c75778fcdd539eb
--- /dev/null
+++ b/marked/Rel-18/22_series/22268/raw.md
@@ -0,0 +1,672 @@
+
+
+# 3GPP TS 22.268 V18.3.0 (2023-06) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Public Warning System (PWS) requirements (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G ADVANCED logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font, with a red signal wave icon below the 'G' and a 'TM' symbol to the right.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+Alert, Public Warning, UMTS, LTE
+
+## **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+©2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## 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..... | 13 |
+| 7 EU-ALERT Specific Requirements..... | 14 |
+| 7.1 Introduction to EU-ALERT ..... | 14 |
+| 7.2 Additional PWS Requirements Specific to EU-ALERT..... | 14 |
+| 8 Korean Public Alert System specific Requirements ..... | 15 |
+| 8.1 Introduction to Korean Public Alert System ..... | 15 |
+| 8.2 Additional PWS Requirements Specific to Korean Public Alert System (KPAS) ..... | 15 |
+| 9 Enhancements of Public Warning System (ePWS) ..... | 16 |
+| 9.1 Service description ..... | 16 |
+| 9.2 General Requirements ..... | 16 |
+| 9.2.1 ePWS Requirements..... | 16 |
+| 9.2.2 Battery Life of ePWS-UE..... | 17 |
+| 9.2.3 Enabling and disabling of Warning Notifications ..... | 17 |
+| 9.3 Requirements for 3GPP system supporting ePWS-UEs ..... | 17 |
+| 9.4 Requirements for ePWS-UE incapable of displaying text based Warning Notification..... | 17 |
+| 9.4.1 Requirements for ePWS-UE with no user interface..... | 17 |
+| 9.4.2 Requirements for ePWS-UE with a user interface incapable of displaying text based Warning Notification..... | 18 |
+| 9.5 Requirements for the improvement of understanding the Warning Notification..... | 18 |
+| 10 Relay of Warning Notification..... | 18 |
+| 10.1 Service description ..... | 18 |
+| 10.2 Requirements for the relay functionality..... | 18 |
+
+
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 |
+| 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.
+
+## 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: A bandwidth reduced low complexity UE or a UE supporting eDRX may not support 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: 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.
+
+# 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. These specifications covers 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**
+
+## 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.
+
+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 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 and 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 and 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.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|------------|--------|------|-----|--------|-----|--------------------------------------------------------------------------------------------------------------------|--------|--------|---------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-42 | SP-080788 | S1-084395 | 22.268 | - | - | Rel-9 | - | One-step-approved by SA#42 | 1.0.1 | 9.0.0 | PWS |
+| SP-43 | SP-090085 | S1-090201 | 22.268 | 0001 | 1 | Rel-9 | D | Fix for a note that is floating out of context | 9.0.0 | 9.1.0 | PWS-S1 |
+| SP-43 | SP-090085 | S1-090202 | 22.268 | 0002 | 1 | Rel-9 | F | Proposal to solve conflicting requirements | 9.0.0 | 9.1.0 | PWS-S1 |
+| SP-43 | SP-090085 | S1-090203 | 22.268 | 0004 | 1 | Rel-9 | F | Regulatory Requirements Pertaining to Roaming | 9.0.0 | 9.1.0 | PWS-S1 |
+| SP-43 | SP-090085 | S1-090204 | 22.268 | 0005 | - | Rel-9 | F | Removal of "subject to regulatory requirements" from PWS-UE requirements | 9.0.0 | 9.1.0 | PWS-S1 |
+| SP-43 | | | | | | | | ETSI clean-up: apply correct style and layout | 9.0.0 | 9.1.0 | - |
+| SP-44 | SP-090375 | S1-091398 | 22.268 | 0006 | 1 | Rel-9 | F | Update Reference [4] | 9.1.0 | 9.2.0 | PWS |
+| SP-44 | SP-090375 | S1-091397 | 22.268 | 0007 | 1 | Rel-9 | F | CR 22.268 Clarify Requirements for Handling of Concurrent PWS Warning Notifications | 9.1.0 | 9.2.0 | PWS |
+| SP-44 | - | - | - | - | - | - | - | Re-introduction of the figure in 6.1 which disappeared for some obscure reason | 9.2.0 | 9.2.1 | - |
+| - | | | | | | | | LTE logo changed into LTE Advanced logo | 11.0.0 | 11.0.1 | - |
+| SP-51 | SP-110172 | S1-110022 | 22.268 | 0010 | - | Rel-11 | F | RAT support for EU-Alert | 11.0.0 | 11.1.0 | TEI11 |
+| SP-53 | SP-110574 | S1-112405 | 22.268 | 0017 | 4 | Rel-11 | A | Korean Public Alert System specific requirements | 11.1.0 | 11.2.0 | TEI10 |
+| SP-54 | SP-110872 | S1-113239r | 22.268 | 0019 | 2 | Rel-11 | A | Updates on Korean Public Alert System specific requirements | 11.2.0 | 11.3.0 | TEI10 |
+| SP-54 | SP-110813 | S1-113441 | 22.268 | 0020 | 2 | Rel-11 | C | CMAS messages in Multiple Languages | 11.2.0 | 11.3.0 | TEI11 |
+| SP-55 | SP-120172 | S1-120341r | 22.268 | 0027 | 6 | Rel-11 | A | PWS Security requirement correction | 11.3.0 | 11.4.0 | PWS |
+| SP-55 | SP-120185 | S1-120338r | 22.268 | 0024 | 7 | Rel-11 | B | Disabling receipt of PWS messages | 11.3.0 | 11.4.0 | TEI11 |
+| SP-57 | SP-120529 | S1-122082 | 22.268 | 0037 | - | Rel-12 | B | Introduction of PWS Security requirements | 11.4.0 | 12.0.0 | PWS_Sec |
+| SP-58 | SP-120870 | S1-124468 | 22.268 | 0040 | 2 | Rel-12 | F | Clarification of conditions of PWS Security requirements | 12.0.0 | 12.1.0 | PWS_Sec |
+| SP-60 | SP-130196 | S1-133290 | 22.268 | 0045 | 2 | Rel-12 | F | CR on Rel-11 alignment regarding disabling and enabling of PWS Notifications | 12.1.0 | 12.2.0 | TEI12 |
+| SP-60 | SP-130196 | S1-133292 | 22.268 | 0046 | 1 | Rel-12 | C | CR regarding PWS integrity protection when roaming internationally | 12.1.0 | 12.2.0 | TEI12 |
+| SP-70 | SP-150748 | S1-154480 | 22.268 | 0047 | 1 | Rel-13 | F | A bandwidth reduced low complexity UE or a UE supporting eDRX may not support PWS | 12.2.0 | 13.0.0 | TEI13 |
+| SP-75 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| SP-76 | SP-170441 | S1-172424 | 22.268 | 0048 | 2 | Rel-14 | F | Alignment of 3GPP PWS specifications to recent FCC WEA/CMAS regulation changes | 14.0.0 | 14.1.0 | TEI14 |
+| - | - | - | - | - | - | - | - | Creation of v.15.0.0 identical to v.14.1.0 because of the CRs approved at SP#79 raising the spec from v.14 to v.16 | 14.1.0 | 15.0.0 | - |
+| SP-79 | SP-180135 | S1-180584 | 22.268 | 0052 | 2 | Rel-16 | B | Requirements for 3GPP system supporting ePWS-UEs | 15.0.0 | 16.0.0 | ePWS |
+| SP-79 | SP-180135 | S1-180585 | 22.268 | 0049 | 4 | Rel-16 | B | Definition of ePWS-UE and abbreviation of ePWS | 15.0.0 | 16.0.0 | ePWS |
+| SP-79 | SP-180135 | S1-180586 | 22.268 | 0051 | 3 | Rel-16 | B | Background of ePWS-UE requirements | 15.0.0 | 16.0.0 | ePWS |
+| SP-79 | SP-180135 | S1-180587 | 22.268 | 0053 | 3 | Rel-16 | B | Requirements for ePWS-UE with different or no user interface or with different roles | 15.0.0 | 16.0.0 | ePWS |
+| SP-79 | SP-180135 | S1-180588 | 22.268 | 0054 | 2 | Rel-16 | B | Requirements for the improvement of understanding the PWS message | 15.0.0 | 16.0.0 | ePWS |
+| SP-79 | SP-180135 | S1-180589 | 22.268 | 0055 | 3 | Rel-16 | B | Addition of NOTE in legacy requirements for the improvement of understanding | 15.0.0 | 16.0.0 | ePWS |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|---------------------------------------------------------------------------|--------|--------|-------|
+| | | | | | | | | the PWS message | | | |
+| SP-80 | SP-180308 | S1-181564 | 22.268 | 0059 | 1 | Rel-16 | A | Alignment of 3GPP PWS specifications to recent FCC WEA regulation changes | 16.0.0 | 16.1.0 | TEI15 |
+| SP-81 | SP-180754 | S1-182440 | 22.268 | 0061 | 2 | Rel-16 | A | Additional requirements in KPAS | 16.1.0 | 16.2.0 | TEI15 |
+| SP-81 | SP-180756 | S1-182235 | 22.268 | 0062 | | Rel-16 | B | EU-alert applicability for 5G | 16.1.0 | 16.2.0 | TEI16 |
+
+| Change history | | | | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | | | | New version |
+| 2019-06 | SA#84 | SP-190301 | 0063 | 2 | F | CR 22.268-0063 Roaming requirements and security requirements for ePWS-UEs | | | | | 16.3.0 |
+| 2020-09 | SA#89e | SP-200785 | 64 | 1 | F | R16 CR to TS22.268 for Requirement alignment for Relay | | | | | 16.4.0 |
+| 2022-03 | | | | | | Identical to v.16.4.0
Creation of v.7.0.0 as to be able to implement CR 0068r2 (SP-220355) that goes from v.16.4.0 to v.18.0.0 | | | | | 17.0.0 |
+| 2022-03 | SP#95e | SP-220355 | 0068 | 2 | B | Device based geo-fencing for EU-alert | | | | | 18.0.0 |
+| 2022-06 | SA#96 | SP-220432 | 0074 | | F | Re-introducing relay requirements for public warning services | | | | | 18.1.0 |
+| 2022-06 | SA#96 | SP-220434 | 0072 | 1 | B | Alignment of KPAS requirements | | | | | 18.1.0 |
+| 2022-12 | SA#98 | SP-221262 | 0077 | 2 | C | Corrections of message length and coding for KPAS services | | | | | 18.2.0 |
+| 2023-06 | SA#100 | SP-230534 | 0078 | 1 | F | Corrections of scope and reference including editorial fixes | | | | | 18.3.0 |
+| 2023-06 | SA#100 | SP-230534 | 0079 | 1 | B | UE based geo-fencing requirements for KPAS | | | | | 18.3.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22279/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22279/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46c60da0685bffc0d6a7667caa1cd24f135fd5fc
--- /dev/null
+++ b/marked/Rel-18/22_series/22279/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79f79bf1bec63bedecbe06895efca602e9e285aa8ed78b9601b21803cd75e6c7
+size 8185
diff --git a/marked/Rel-18/22_series/22279/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22279/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a230726fd9e7018245cf60c10b90f593675afa72
--- /dev/null
+++ b/marked/Rel-18/22_series/22279/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c2c5c623bea570b269badb02aa1ce28642469dd5808261b7629f16da6120a81
+size 6861
diff --git a/marked/Rel-18/22_series/22279/raw.md b/marked/Rel-18/22_series/22279/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4931949fa72d0e75b305a3f54a2056c57ea08497
--- /dev/null
+++ b/marked/Rel-18/22_series/22279/raw.md
@@ -0,0 +1,495 @@
+
+
+# 3GPP TS 22.279 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon at its base, and a 'TM' symbol is located to the top right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+
+
+## --- **Keywords**
+
+LTE, UMTS, circuit mode, packet mode, IMS,
+stage 1
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions, symbols and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Introduction to Combinational Service ..... | 8 |
+| 5 General requirements ..... | 8 |
+| 6 User experience of combinational services..... | 9 |
+| 7 Service Capability Detection ..... | 9 |
+| 7.1 General ..... | 9 |
+| 7.2 User privacy ..... | 9 |
+| 8 IMS service behaviour during a Combinational Service ..... | 10 |
+| 9 Interaction with supplementary services..... | 10 |
+| 9.1 Line Identification ..... | 10 |
+| 9.1.1 Calling Line Identity Presentation (CLIP) ..... | 10 |
+| 9.1.2 Calling Line Identity Restriction (CLIR) ..... | 10 |
+| 9.1.3 Connected Line Identification Presentation (COLP)..... | 11 |
+| 9.1.4 Connected Line Identification Restriction (COLR) ..... | 11 |
+| 9.2 Name Identification..... | 11 |
+| 9.2.1 Calling Name Presentation (CNAP)..... | 11 |
+| 9.3 Call Forwarding..... | 11 |
+| 9.3.1 Call Forwarding Unconditional (CFU) ..... | 11 |
+| 9.3.2 Call Forwarding on Busy (CFB) ..... | 11 |
+| 9.3.3 Call Forwarding on No Reply (CFNRY) ..... | 11 |
+| 9.3.4 Call Forwarding on Not Reachable (CFNRC) ..... | 11 |
+| 9.3.5 Call Deflection (CD) ..... | 11 |
+| 9.4 Call Offering ..... | 12 |
+| 9.4.1 Explicit Call Transfer (ECT)..... | 12 |
+| 9.5 Call Completion ..... | 12 |
+| 9.5.1 Call Waiting (CW) ..... | 12 |
+| 9.5.2 Call Hold (CH) ..... | 12 |
+| 9.5.3 Call Completion to Busy Subscriber (CCBS) ..... | 12 |
+| 9.5.4 Multi Call (MC)..... | 12 |
+| 9.6 Multi Party..... | 12 |
+| 9.6.1 Multi Party call (MPTY) ..... | 12 |
+| 9.7 Community of Interest ..... | 12 |
+| 9.7.1 Closed User Group (CUG) ..... | 12 |
+| 9.8 Charging..... | 13 |
+| 9.8.1 Advice of Charge - Information (AOCI)..... | 13 |
+| 9.8.2 Advice of charge – Charge (AOCC) ..... | 13 |
+| 9.9 Additional Info Transfer..... | 13 |
+| 9.9.1 User-to-User Signalling service 1 (UUS1)..... | 13 |
+| 9.9.2 User-to-User Signalling service 2 (UUS2)..... | 13 |
+| 9.9.3 User-to-User Signalling service 3 (UUS3)..... | 13 |
+| 9.10 Call Barring..... | 13 |
+| 9.10.1 Barring of All Outgoing Calls (BAOC) ..... | 13 |
+| 9.10.2 Barring of Outgoing International Calls (BOIC)..... | 13 |
+| 9.10.3 Barring of Outgoing International Calls except to HPLMN country (BOIC-exHC) ..... | 13 |
+| 9.10.4 Barring of All Incoming Calls (BAIC)..... | 13 |
+| 9.10.5 Barring of All Incoming Calls when roaming outside HPLMN country (BICROAM)..... | 13 |
+
+| | | |
+|-------------------------------|-------------------------------------------------------------------|-----------|
+| 9.11 | Call Priority ..... | 14 |
+| 9.11.1 | Enhanced Multi Level Precedence Pre-emption (EMLPP) ..... | 14 |
+| 10 | Impacts on other services ..... | 14 |
+| 10.1 | Support of Teleservices during a combinational service ..... | 14 |
+| 10.2 | Support of Location Services during a combinational service ..... | 14 |
+| 11 | Charging aspects for Combinational Service ..... | 14 |
+| 12 | Provisioning ..... | 14 |
+| Annex A (informative): | Change history ..... | 15 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies service requirements for Combining CS and IMS services using a CS speech or CS multimedia call in association with an IMS session. The IMS session may consist of one or more IMS services.
+
+Requirements for the following capabilities are included:
+
+- Radio capability exchange.
+- Terminal capability exchange.
+- E.164 number exchange.
+- Adding IMS session to an ongoing CS call.
+- Adding a CS call to an ongoing IMS session.
+- Supplementary services as they relate to CSICS.
+
+It is intended that the capabilities defined herein for CSICS shall support interoperability between different operator networks, and roaming.
+
+# --- 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.979: "Feasibility study on Combined CS Calls and IMS Sessions".
+- [3] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem".
+- [4] 3GPP TS 22.004: "General on Supplementary Services".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Combinational Service:** A combinational service is created by adding one or more IMS session(s) to a CS call (or vice versa). The CS call and IMS session are established between the same participants.
+
+**Combinational call:** this is the name given to the service in which a circuit switched speech teleservice is enriched by adding an IMS session where both services (IMS session and CS call) are originated in one single UE and are terminated in another single UE.
+
+**Combinational Session:** this is the name given to the service in which an ongoing IMS session between two users is enriched by adding a circuit switched based call. The individual service instances that form the combinational session are originated in a single UE and terminated in another single UE.
+
+**CSICS capable UE:** UE that supports Combinational Service.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply. Additional applicable abbreviations can be found in TR 21.905 [1].
+
+| | |
+|-------|--------------------------------------------|
+| CSICS | Circuit Switched IMS Combinational Service |
+|-------|--------------------------------------------|
+
+# --- 4 Introduction to Combinational Service
+
+Combinational services are applicable to both UTRAN and GERAN and enables the unidirectional or bi-directional exchange of PS data within the context of an IMS session
+
+A specific subscription for combinational services is not necessary. However, both users A and B shall as a minimum be provisioned with CS telephony (TS11) as well as for accessing the IMS.
+
+The existing address context is reused when the combined service is established, which makes the combined service simple to invoke for the user.
+
+# --- 5 General requirements
+
+In addition to the existing IMS requirements [3], the following general requirements apply for CSICS:
+
+It shall be possible to establish a combinational service between two users within the same PLMN or within different PLMNs.
+
+It shall be possible to establish a combinational service between two users camped on identical or different RATs.
+
+It shall be possible to establish a combinational service when roaming, assuming the visited operator supports GPRS roaming.
+
+The user (A or B party) shall only need to know one address in order to establish the combinational service.
+
+It shall be possible to add an IMS session to a CS speech call, thereby creating a combinational call.
+
+It shall be possible to add a CS speech call to an IMS session, thereby creating a combinational session.
+
+It shall be possible to add an IMS session to a CS Multimedia call, thereby creating a combinational call.
+
+It shall be possible to add a CS Multimedia call to an IMS session, thereby creating a combinational session.
+
+The following two service modes will exist in regards to IMS registration depending on different UE implementations:
+
+- 1) IMS pre established state: the CSICS capable UE performs the IMS registration at switch on.
+- 2) IMS on demand state: the CSICS capable UE performs the IMS registration:
+ - to start the communication, or
+ - to add a IMS session to an existing CS call.
+
+Interoperability between UEs that implement such different approaches shall be enabled.
+
+During a CS call it shall be possible to request establishment of the IMS session whether the invited UE is IMS registered or not. The invited user shall be able to accept or reject the IMS registration request.
+
+A combinational service shall enable both unidirectional and bi-directional exchange of PS data within the context of the IMS session.
+
+# --- 6 User experience of combinational services
+
+When one of the participating users terminates the CS call of a combinational service, the IMS session may continue.
+
+When one of the participating users terminates the IMS session of a combinational service, the CS call may continue.
+
+When the user A sends media to a user B, the user B can accept or reject the media (confirmation from the receiving party is needed) and vice versa.
+
+If media, or parts thereof, accepted by a user cannot be rendered by the UE simultaneously with the CS call, conflicts shall be resolved such that the user is presented with:
+
+- CS speech with preference over IMS speech/audio;
+- IMS video and images with preference over CS video.
+
+It shall be possible to initiate a combinational service with user perceived simultaneous setup of IMS session and CS call. The CS call and IMS session can be established sequentially and on the failure of any of the setups the user may be prompted to decide whether to continue. The terminating user shall be able to accept or reject CS call or IMS session independently.
+
+# --- 7 Service Capability Detection
+
+## 7.1 General
+
+The Service Capability Detection may indicate to the user that the UEs have interoperable CSICS capability and that the access network(s) have the necessary network functionality to carry the combinational service.
+
+The detection of the capabilities of the recipient terminal and the operators' networks shall ensure that information is updated in case of change of terminal.
+
+An operator should have the mechanism to inhibit the capability check, or at least indicate to UE that it should not be performed.
+
+Note: An operator may want to inhibit the capability check for CSICS in order to optimise the usage of radio resources.
+
+It shall be possible for the (CSICS capable) UEs to have the information, prior to initiating a combinational service, regarding the type of capabilities, which are jointly supported by both UEs, without user intervention.
+
+Due to the handover of the participating users to an access network which does not support combinational services, service capability detection may be needed during a CS call to notify the user of the service availability.
+
+## 7.2 User privacy
+
+Participants in a CS call or IMS session may choose not to reveal their identity, even though this may prevent the establishment of a combinational session.
+
+During the service capability detection and exchange of information process, the user's privacy settings shall be respected. The applicable privacy settings are as described in clauses 8 and 9. Additionally, the user shall be able to restrict the information exchanged by the service capability detection application and the user's consent should be requested prior to the exchange of information.
+
+NOTE: The terminal is not normally aware of existing Calling Line Identity Restriction / Connected Line Restriction settings in the network, hence the need for the user to be able to configure the service capability detection application not to reveal such information.
+
+# --- 8 IMS service behaviour during a Combinational Service
+
+There is no standardised supplementary service defined for IMS session, however mechanisms exist (service capabilities) to emulate the behaviour of some of the most common supplementary services that exist in the circuit switched domain. The intention in this clause is NOT to define "supplementary services" for IMS, just to explain the service behaviour during a combinational session for some specific cases as indicated below:
+
+- **IMS session hold:** In an ongoing combinational service, the user may decide to suspend the IMS session. When this service is invoked the user should be able to decide whether the CS call of the combinational service should also be put on hold.
+- **IMS session waiting:** In an ongoing combinational service, the user should be able to receive an alert of an incoming IMS session towards his UE. Subject to the capability of the UE, the user should be provided with the option to switch between the ongoing session and the new incoming one, or accept the new one in parallel with the existing one. The CS call of the combinational service should continue during the alerting of the subscriber and the user may decide to put the CS call on hold when switching to the new IMS session.
+- **IMS session redirect:** It should be possible to add CS call to a redirected IMS session, subject to the capability of the recipient UE.
+- **Identity presentation:** Existing Session Originator Identity Presentation rules apply to IMS session.
+- **Identity restriction:** Existing Session Originator Identity Presentation Suppression rules apply to IMS session, even if this results in the called party being unable to establish a combinational session.
+
+# --- 9 Interaction with supplementary services
+
+The current section lists the supplementary services as specified in 3GPP TS 22.004 [4].
+
+## 9.1 Line Identification
+
+### 9.1.1 Calling Line Identity Presentation (CLIP)
+
+When CLIP is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+If the called party does not subscribe to CLIP or the CLI is not available, then the called party's UE may treat an incoming IMS session as an independent IMS session and the called party may establish an independent IMS session with the calling party.
+
+### 9.1.2 Calling Line Identity Restriction (CLIR)
+
+Existing CLIR rules apply, even if this results in the called party being unable to establish a combinational call.
+
+If a calling party uses CLIR when establishing a CS call, either by subscription or per call basis, and the called party does not have CLIR override, then the called party's UE may treat an incoming IMS session as an independent IMS session and the called party may establish an independent IMS session with the calling party.
+
+If the CLI of the calling party is restricted as a result of CLIR, then the calling party's UE or the network shall ensure that the Public User Identity of the calling party is also restricted when establishing an outgoing IMS session associated with this CS call and when responding to an incoming IMS session associated with this CS call.
+
+### 9.1.3 Connected Line Identification Presentation (COLP)
+
+When COLP is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+If the calling party does not subscribe to COLP or the COL is not available, then the calling party's UE may use the called party number of the CS call, as provided by the UE to the network, to correlate an incoming IMS session with the CS call and to establish an IMS session associated with the CS call.
+
+### 9.1.4 Connected Line Identification Restriction (COLR)
+
+Existing COLR rules apply, even if this results in the calling party being unable to establish a combinational call.
+
+If the called party subscribes to COLR and the calling party does not have COLR override, then the calling party's UE may use the called party number of the CS call, as provided by the UE to the network, to correlate an incoming IMS session with the CS call and to establish an IMS session associated with the CS call.
+
+If the COL of the called party is restricted as a result of COLR, then the called party's UE or the network shall ensure that the Public User Identity of the called party is also restricted when establishing an outgoing IMS session associated with this CS call and when responding to an incoming IMS session associated with this CS call.
+
+## 9.2 Name Identification
+
+### 9.2.1 Calling Name Presentation (CNAP)
+
+When CNAP is used in conjunction with a combinational service, it shall function as specified for CS calls.
+
+## 9.3 Call Forwarding
+
+### 9.3.1 Call Forwarding Unconditional (CFU)
+
+Call forwarding unconditional shall not prevent the calling party or the called party from adding an IMS session to the CS call. Refer to the clause on Line Identification for the usage of the CLI and COL for establishing an IMS session associated with the CS call and for correlating an incoming IMS session with the CS call.
+
+### 9.3.2 Call Forwarding on Busy (CFB)
+
+Refer to CFU.
+
+### 9.3.3 Call Forwarding on No Reply (CFNRY)
+
+Refer to CFU.
+
+### 9.3.4 Call Forwarding on Not Reachable (CFNRC)
+
+Refer to CFU.
+
+### 9.3.5 Call Deflection (CD)
+
+Refer to CFU.
+
+## 9.4 Call Offering
+
+### 9.4.1 Explicit Call Transfer (ECT)
+
+At the moment that the subscriber invokes ECT, she may have an IMS session ongoing with either or both of the CS call parties. The user may keep or terminate these IMS sessions when ECT is invoked. The two CS call parties that are in speech connection after the invocation of ECT, have not exchanged Radio Network and Terminal capabilities with one another. Neither are these two call parties aware of one another's Line Identification. These parties are therefore not capable of initiating IMS sessions, associated with the CS call.
+
+## 9.5 Call Completion
+
+### 9.5.1 Call Waiting (CW)
+
+When a second CS call arrives during an ongoing combinational call, the IMS session of the ongoing combinational call shall not be affected. When the user decides to place the ongoing CS call on hold and accept the second CS call, then the rules as specified for Call Hold apply for the ongoing CS call that is placed on hold. When the incoming, waiting CS call is accepted, the calling party's UE and called party's UE may exchange terminal capability and radio network capability. An IMS session may be established associated with the second CS call, when that CS call is accepted. The IMS session(s) for the second CS call may run concurrently with the IMS session(s) for the CS call that is on hold.
+
+### 9.5.2 Call Hold (CH)
+
+When a user places a CS call on hold, the user may decide to suspend an IMS session associated with that CS call, or to terminate the IMS session. When a held CS call is resumed, an associated IMS session that was suspended when that CS call was placed on hold, may be resumed. The user may decide whether new IMS sessions may be created for a CS call when that CS call is currently in the held state.
+
+For the second CS call that may be established or accepted when a first CS call is placed on hold, the calling party's UE and called party's UE may exchange terminal capability and radio network capability. An IMS session may be established associated with the second CS call, when that second call is active.
+
+### 9.5.3 Call Completion to Busy Subscriber (CCBS)
+
+Not part of the scope of the present specification.
+
+### 9.5.4 Multi Call (MC)
+
+Not part of the scope of the present specification.
+
+## 9.6 Multi Party
+
+### 9.6.1 Multi Party call (MPTY)
+
+Not part of the scope of the present specification.
+
+## 9.7 Community of Interest
+
+### 9.7.1 Closed User Group (CUG)
+
+No impact. When the establishment of an outgoing CS call or the acceptance of a CS incoming call is barred due to CUG, that shall not affect the calling or called party's ability to establish IMS sessions with the other party. However, these IMS sessions will not be considered "combinational".
+
+## 9.8 Charging
+
+### 9.8.1 Advice of Charge - Information (AOCI)
+
+When AOCI is used in conjunction with a combinational service, it shall function as specified for CS calls and packet data service.
+
+### 9.8.2 Advice of charge – Charge (AOCC)
+
+Refer to AOCI.
+
+## 9.9 Additional Info Transfer
+
+### 9.9.1 User-to-User Signalling service 1 (UUS1)
+
+When UUS1 is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+### 9.9.2 User-to-User Signalling service 2 (UUS2)
+
+When UUS2 is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+### 9.9.3 User-to-User Signalling service 3 (UUS3)
+
+When UUS3 is used in conjunction with a combinational service, it shall function as specified for CS voice and data calls.
+
+## 9.10 Call Barring
+
+### 9.10.1 Barring of All Outgoing Calls (BAOC)
+
+When the establishment of an outgoing CS call is barred due to BAOC, that shall not affect the calling party's ability to establish IMS sessions with the other party. However, these IMS sessions will not be considered "combinational".
+
+### 9.10.2 Barring of Outgoing International Calls (BOIC)
+
+Refer to BAOC.
+
+### 9.10.3 Barring of Outgoing International Calls except to HPLMN country (BOIC-exHC)
+
+Refer to BAOC.
+
+### 9.10.4 Barring of All Incoming Calls (BAIC)
+
+When the acceptance of an incoming CS call is barred due to BAIC, that shall not affect the called party's ability to establish IMS sessions with the other party. However, these IMS sessions will not be considered "combinational".
+
+### 9.10.5 Barring of All Incoming Calls when roaming outside HPLMN country (BICROAM)
+
+Refer to BAIC.
+
+## 9.11 Call Priority
+
+### 9.11.1 Enhanced Multi Level Precedence Pre-emption (EMLPP)
+
+When a CS call cannot be established due to a lower precedence this shall not affect the user's ability to establish IMS sessions to another party. However, these IMS sessions will not be considered "combinational".
+
+It shall be possible to pre-empt a CS call which is part of a combinational service.
+
+It shall be possible to add a precedence call to an IMS session.
+
+# --- 10 Impacts on other services
+
+## 10.1 Support of Teleservices during a combinational service
+
+It should be possible to send and receive an SMS while engaged in a combinational service.
+
+## 10.2 Support of Location Services during a combinational service
+
+It shall be possible to locate a user engaged in a combinational service.
+
+# --- 11 Charging aspects for Combinational Service
+
+For combinational services, it must be possible to charge as follows:
+
+It shall be possible to provide charging information on the CS call and IMS session for correlation purposes in order to allow off-line charging.
+
+The charging information shall continue to be produced for any remaining multimedia components or the CS call when a multimedia component or the CS call drops during the communication between the two parties.
+
+Note: The below requirement will presumably not be feasible within Rel-7 timeframe, but may be considered in Rel-8.
+
+The home operator should be able to correlate charged media components and CS call in order to introduce dedicated charging schemes, e.g. discounts. This applies to on-line charging as well as off-line charging.
+
+# --- 12 Provisioning
+
+The combinational service should not place additional provisioning requirement on the operator.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|-------|-----|---------------------------------------------------------------------------------------------|--------|--------|-------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| 2005-01 | | | | | | | | First Draft | | 0.0.0 | |
+| 2005-04 | | | | | | | | Output from SA1 #28 Beijing | 0.0.0 | 1.0.0 | |
+| 2005-07 | | | | | | | | Output from SA1 #29 SWG in Povoa de Varzim | 1.0.0 | 1.1.0 | |
+| 2005-07 | | | | | | | | Output from SA #29 plenary | 1.1.0 | 2.0.0 | |
+| SP-29 | SP-050517 | | | | | | | Approved at SA #29 | 2.0.0 | 7.0.0 | |
+| SP-30 | SP-050745 | S1-051125 | 22.279 | 0001 | - | Rel-7 | F | UE behaviour for simultaneous rendering of CS call and IMS media (Action A29-07 from SA#29) | 7.0.0 | 7.1.0 | CSICS |
+| SP-30 | SP-050745 | S1-051148 | 22.279 | 0002 | - | Rel-7 | F | CR to TS22.279 for correction of the term | 7.0.0 | 7.1.0 | CSICS |
+| SP-30 | SP-050745 | S1-051152 | 22.279 | 0003 | - | Rel-7 | F | Clarification of supplementary services requirements for CSICS | 7.0.0 | 7.1.0 | CSICS |
+| SP-42 | - | - | - | - | - | Rel-8 | - | Updated from Rel-7 to Rel-8 | 7.0.0 | 8.0.0 | |
+| SP-46 | - | - | - | - | - | - | - | Updated to Rel-9 by MCC | 8.0.0 | 9.0.0 | |
+| 2011-03 | - | - | - | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22280/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22280/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c45c67d628d7a01696101b856174f0b9950f14ec
--- /dev/null
+++ b/marked/Rel-18/22_series/22280/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a45180ff5f2e10af13024473b3560c25e85c55027da03464781c681af1c7601e
+size 9440
diff --git a/marked/Rel-18/22_series/22280/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22280/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36f87d7316ee0fd1fd217b029ed01df82d7a5c5b
--- /dev/null
+++ b/marked/Rel-18/22_series/22280/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64680123734feea80fb462f1d25621772a1ee7c3b21db0efbbc36f8a67730606
+size 7248
diff --git a/marked/Rel-18/22_series/22280/raw.md b/marked/Rel-18/22_series/22280/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..eba9e1dbb98f49596f093eca72e103c988a792ae
--- /dev/null
+++ b/marked/Rel-18/22_series/22280/raw.md
@@ -0,0 +1,4315 @@
+
+
+# 3GPP TS 22.280 V18.5.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Services Common Requirements (MCCoRe); Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+Mission, Critical
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 8 |
+| 1 Scope..... | 9 |
+| 2 References..... | 9 |
+| 3 Definitions and abbreviations ..... | 9 |
+| 3.1 Definitions..... | 9 |
+| 3.2 Abbreviations ..... | 11 |
+| 4 Overview..... | 11 |
+| 4.1 Rationale for MCCoRe..... | 11 |
+| 4.2 MCCoRe creation process..... | 11 |
+| 5 MCX Service requirements common for on the network and off the network..... | 12 |
+| 5.1 General Group Communications requirements..... | 12 |
+| 5.1.1 General aspects..... | 12 |
+| 5.1.2 Group/status information ..... | 13 |
+| 5.1.3 Group configuration ..... | 13 |
+| 5.1.4 Identification..... | 13 |
+| 5.1.5 Membership/affiliation ..... | 13 |
+| 5.1.6 Group Communication administration ..... | 13 |
+| 5.1.7 Prioritization ..... | 13 |
+| 5.1.8 Charging requirements for MCX Service..... | 14 |
+| 5.1.9 MCX Service Emergency Alert triggered by Location ..... | 14 |
+| 5.2 Broadcast Group..... | 14 |
+| 5.2.1 General Broadcast Group Communication..... | 14 |
+| 5.2.2 Group-Broadcast Group (e.g., announcement group) ..... | 14 |
+| 5.2.3 User-Broadcast Group (e.g., System Communication) ..... | 15 |
+| 5.3 Late communication entry..... | 15 |
+| 5.4 Receiving from multiple MCX Service communications..... | 15 |
+| 5.4.1 Overview ..... | 15 |
+| 5.4.2 Requirements..... | 16 |
+| 5.5 Private Communication..... | 16 |
+| 5.5.1 Private Communication general requirements ..... | 16 |
+| 5.5.2 Charging requirements for MCX Service..... | 16 |
+| 5.6 MCX Service priority requirements..... | 17 |
+| 5.6.1 Overview ..... | 17 |
+| 5.6.2 Communication types based on priorities ..... | 18 |
+| 5.6.2.1 MCX Service Emergency and Imminent Peril general requirements..... | 18 |
+| 5.6.2.1.1 Overview ..... | 18 |
+| 5.6.2.1.2 Requirements..... | 18 |
+| 5.6.2.2 MCX Service Emergency Group Communication ..... | 18 |
+| 5.6.2.2.1 MCX Service Emergency Group Communication requirements..... | 18 |
+| 5.6.2.2.2 MCX Service Emergency Group Communication cancellation requirements ..... | 19 |
+| 5.6.2.3 MCX Service Imminent Peril Group Communication ..... | 20 |
+| 5.6.2.3.1 MCX Service Imminent Peril Group Communication requirements..... | 20 |
+| 5.6.2.3.2 MCX Service Imminent Peril Group Communication cancellation requirements ..... | 20 |
+| 5.6.2.4 MCX Service Emergency Alert..... | 20 |
+| 5.6.2.4.1 MCX Service Emergency Alert requirements ..... | 20 |
+| 5.6.2.4.2 MCX Service Emergency Alert cancellation requirements ..... | 21 |
+| 5.7 MCX Service User ID ..... | 21 |
+| 5.8 MCX UE management..... | 22 |
+| 5.9 MCX Service User Profile ..... | 22 |
+| 5.9a Functional alias ..... | 22 |
+| 5.10 Support for multiple devices ..... | 24 |
+| 5.11 Location..... | 25 |
+| 5.12 Security..... | 26 |
+| 5.13 Media quality..... | 26 |
+
+| | | |
+|-----------|----------------------------------------------------------------------------------------------------------|----|
+| 5.14 | Relay requirements..... | 26 |
+| 5.15 | Gateway requirements..... | 27 |
+| 5.16 | Control and management by Mission Critical Organizations ..... | 27 |
+| 5.16.1 | Overview ..... | 27 |
+| 5.16.2 | General requirements..... | 27 |
+| 5.16.3 | Operational visibility for Mission Critical Organizations ..... | 28 |
+| 5.16.4 | Sharing of administrative configuration between Mission Critical Organizations ..... | 28 |
+| 5.17 | General administrative – groups and users ..... | 28 |
+| 5.18 | Open interfaces for MCX services..... | 29 |
+| 5.18.1 | Overview ..... | 29 |
+| 5.18.2 | Requirements..... | 29 |
+| 5.19 | Media forwarding..... | 29 |
+| 5.19.1 | Service description ..... | 29 |
+| 5.19.2 | Requirements..... | 29 |
+| 5.20 | Receipt notification ..... | 30 |
+| 5.20.1 | Service description ..... | 30 |
+| 5.20.2 | Requirements..... | 30 |
+| 5.21 | Additional services for MCX Service communications..... | 30 |
+| 5.21.1 | Remotely initiated MCX Service communication ..... | 30 |
+| 5.21.1.1 | Overview..... | 30 |
+| 5.21.1.2 | Requirements ..... | 30 |
+| 5.21.2 | Remotely terminated MCX Service communication..... | 30 |
+| 5.21.2.1 | Requirements ..... | 30 |
+| 6 | MCX Service requirements specific to on-network use ..... | 31 |
+| 6.1 | General administrative – groups and users ..... | 31 |
+| 6.2 | MCX Service communications ..... | 31 |
+| 6.2.1 | Notification and acknowledgement for MCX Service Group Communications..... | 31 |
+| 6.2.2 | Queuing ..... | 31 |
+| 6.3 | General requirements ..... | 32 |
+| 6.4 | General MCX Service Group Communications..... | 32 |
+| 6.4.1 | General aspects..... | 32 |
+| 6.4.2 | Group status/information..... | 32 |
+| 6.4.3 | Identification..... | 32 |
+| 6.4.4 | Membership/affiliation ..... | 33 |
+| 6.4.5 | Membership/affiliation list ..... | 33 |
+| 6.4.6 | Authorized user remotely changes another MCX User's affiliated and/or Selected MCX Service Group(s)..... | 33 |
+| 6.4.6.1 | Mandatory change..... | 33 |
+| 6.4.6.2 | Negotiated change..... | 34 |
+| 6.4.7 | Prioritization ..... | 34 |
+| 6.4.8 | Relay requirements..... | 34 |
+| 6.4.9 | Administrative ..... | 34 |
+| 6.5 | Broadcast Group..... | 35 |
+| 6.5.1 | General Broadcast Group Communication..... | 35 |
+| 6.5.2 | Group-Broadcast Group (e.g., announcement group) ..... | 35 |
+| 6.5.3 | User-Broadcast Group (e.g., System Communication) ..... | 35 |
+| 6.6 | Dynamic group management (i.e., dynamic regrouping)..... | 35 |
+| 6.6.1 | General dynamic regrouping ..... | 35 |
+| 6.6.2 | Group regrouping ..... | 36 |
+| 6.6.2.1 | Service description..... | 36 |
+| 6.6.2.2 | Requirements ..... | 36 |
+| 6.6.3 | Temporary Broadcast Groups..... | 37 |
+| 6.6.4 | User regrouping ..... | 37 |
+| 6.6.4.1 | Service description..... | 37 |
+| 6.6.4.1.1 | User regrouping controlled by dispatcher or authorized user ..... | 37 |
+| 6.6.4.1.2 | Automatic user regrouping..... | 37 |
+| 6.6.4.2 | Requirements ..... | 37 |
+| 6.6.5 | Dynamic Group Participation..... | 38 |
+| 6.6.5.1 | Service description..... | 38 |
+| 6.6.5.2 | Requirements ..... | 38 |
+| 6.7 | Private Communication..... | 39 |
+
+| | | |
+|------------|------------------------------------------------------------------------------------------------|----|
+| 6.7.1 | Overview ..... | 39 |
+| 6.7.2 | General requirements..... | 39 |
+| 6.7.3 | Administrative ..... | 39 |
+| 6.7.4 | Prioritization ..... | 40 |
+| 6.7.5 | Private Communication (without Floor control) commencement requirements ..... | 40 |
+| 6.7.6 | Private Communication (without Floor control) termination ..... | 40 |
+| 6.8 | MCX Service priority requirements..... | 41 |
+| 6.8.1 | General ..... | 41 |
+| 6.8.2 | 3GPP system access controls..... | 42 |
+| 6.8.3 | 3GPP system admission controls..... | 42 |
+| 6.8.4 | 3GPP system scheduling controls ..... | 42 |
+| 6.8.5 | UE access controls..... | 42 |
+| 6.8.6 | Mobility and load management..... | 42 |
+| 6.8.6.1 | Mission Critical mobility management according to priority..... | 42 |
+| 6.8.6.2 | Load management..... | 42 |
+| 6.8.7 | Application layer priorities..... | 43 |
+| 6.8.7.1 | Overview..... | 43 |
+| 6.8.7.2 | Requirements ..... | 43 |
+| 6.8.8 | Communication types based on priorities ..... | 43 |
+| 6.8.8.1 | MCX Service Emergency Group Communication requirements ..... | 43 |
+| 6.8.8.2 | MCX Service Emergency Private Communication requirements ..... | 44 |
+| 6.8.8.3 | Imminent Peril Group Communication requirements ..... | 44 |
+| 6.8.8.4 | MCX Service Emergency Alert..... | 44 |
+| 6.8.8.4.1 | Requirements..... | 44 |
+| 6.8.8.4.2 | MCX Service Emergency Alert cancellation requirements ..... | 45 |
+| 6.8.8.5 | Ad hoc Group Communication requirements ..... | 45 |
+| 6.9 | IDs and aliases..... | 45 |
+| 6.10 | MCX Service User Profile management..... | 45 |
+| 6.11 | Support for multiple devices ..... | 45 |
+| 6.12 | Location..... | 46 |
+| 6.13 | Security..... | 46 |
+| 6.13.1 | Overview ..... | 46 |
+| 6.13.2 | Cryptographic protocols ..... | 46 |
+| 6.13.3 | Authentication ..... | 46 |
+| 6.13.4 | Access control ..... | 46 |
+| 6.13.5 | Regulatory issues..... | 47 |
+| 6.13.6 | Storage control..... | 47 |
+| 6.14 | Interactions for MCX Service Group Communications and MCX Service Private Communications ..... | 47 |
+| 6.15 | Additional services for MCX Service communications..... | 47 |
+| 6.15.1 | Discreet listening capabilities..... | 47 |
+| 6.15.2 | Ambient listening ..... | 48 |
+| 6.15.2.1 | Overview of ambient listening..... | 48 |
+| 6.15.2.2 | Ambient listening requirements..... | 48 |
+| 6.15.2.2.1 | General ambient listening requirements..... | 48 |
+| 6.15.2.2.2 | Remotely initiated ambient listening requirements..... | 48 |
+| 6.15.2.2.3 | Locally initiated ambient listening requirements ..... | 48 |
+| 6.15.3 | Remotely initiated MCX Service Communication..... | 49 |
+| 6.15.3.1 | Overview..... | 49 |
+| 6.15.3.2 | Requirements ..... | 49 |
+| 6.15.4 | Recording and audit requirements..... | 49 |
+| 6.15.5 | MCX Service Ad hoc Group Communication ..... | 50 |
+| 6.15.5.1 | Overview..... | 50 |
+| 6.15.5.2 | General aspects ..... | 50 |
+| 6.15.5.3 | Administrative ..... | 52 |
+| 6.15.5.4 | Notification and acknowledgement for MCX Service Ad hoc Group Communications ..... | 52 |
+| 6.15.6 | MCX Service Ad hoc Group Emergency Alert..... | 52 |
+| 6.15.6.1 | Overview..... | 52 |
+| 6.15.6.2 | General aspects ..... | 53 |
+| 6.15.6.3 | Administrative ..... | 53 |
+| 6.16 | Interaction with telephony services..... | 53 |
+| 6.17 | Interworking ..... | 54 |
+| 6.17.1 | Non-3GPP access ..... | 54 |
+
+| | | |
+|----------|--------------------------------------------------------------------------|----|
+| 6.17.2 | Interworking between MCX Service systems ..... | 54 |
+| 6.17.3 | Interworking with non-MCX Service systems ..... | 54 |
+| 6.17.3.1 | GSM-R..... | 54 |
+| 6.17.3.2 | External systems ..... | 55 |
+| 6.18 | MCX Service coverage extension using ProSe UE-to-Network Relays..... | 55 |
+| 6.19 | Additional MCX Service requirements..... | 55 |
+| 6.19.1 | Communication rejection and queuing..... | 55 |
+| 6.19.1.1 | Requirements ..... | 55 |
+| 7 | MCX Service requirements specific to off-network use..... | 56 |
+| 7.1 | Off-network communications overview..... | 56 |
+| 7.2 | General off-network MCX Service requirements ..... | 58 |
+| 7.3 | Admission control ..... | 58 |
+| 7.3.1 | General aspects ..... | 58 |
+| 7.3.2 | Communication initiation ..... | 58 |
+| 7.4 | Communication termination..... | 59 |
+| 7.5 | Broadcast Group..... | 59 |
+| 7.6 | MCX Service priority requirements..... | 59 |
+| 7.7 | Communication types based on priorities ..... | 60 |
+| 7.7.1 | MCX Service Emergency Group Communication requirements..... | 60 |
+| 7.7.2 | MCX Service Emergency Group Communication cancellation requirements..... | 60 |
+| 7.7.3 | Imminent Peril Communication ..... | 60 |
+| 7.7.3.1 | Imminent Peril Group Communication requirements ..... | 60 |
+| 7.7.3.2 | Imminent Peril Group Communication cancellation requirements ..... | 60 |
+| 7.8 | Location..... | 60 |
+| 7.9 | Security..... | 61 |
+| 7.10 | Off-network MCX Service operations ..... | 61 |
+| 7.11 | Off-network UE functionality ..... | 61 |
+| 7.12 | Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay ..... | 61 |
+| 7.12.1 | UE-to-Network Relay for all data types ..... | 61 |
+| 7.12.2 | UE-to-UE Relay streaming..... | 62 |
+| 7.12.3 | Off-Network streaming ..... | 62 |
+| 7.13 | Switching to off-network MCX Service ..... | 62 |
+| 7.14 | Off-network recording and audit requirements ..... | 62 |
+| 7.15 | Off-network UE-to-UE Relay ..... | 63 |
+| 7.15.1 | Private Communications ..... | 63 |
+| 7.15.2 | Group Communications..... | 63 |
+| 7.16 | Off-network Ad hoc Group Communication ..... | 63 |
+| 8 | Inter-MCX Service interworking..... | 63 |
+| 8.1 | Inter-MCX Service interworking overview ..... | 63 |
+| 8.2 | Concurrent operation of different MCX Services ..... | 64 |
+| 8.2.1 | Overview ..... | 64 |
+| 8.2.2 | Requirements..... | 64 |
+| 8.3 | Use of unsharable resources within a UE..... | 64 |
+| 8.4 | Single group with multiple MCX Services ..... | 65 |
+| 8.4.1 | Overview ..... | 65 |
+| 8.4.2 | Requirements..... | 65 |
+| 8.4.3 | Compatibility of UE ..... | 65 |
+| 8.4.3.1 | Advertising service capabilities required..... | 65 |
+| 8.4.3.2 | Conversion between capabilities ..... | 65 |
+| 8.4.4 | Individual permissions for service access ..... | 66 |
+| 8.4.5 | Common alias and user identities or mappable ..... | 66 |
+| 8.4.6 | Single location message ..... | 66 |
+| 8.5 | Priority between services ..... | 66 |
+| 8.5.1 | Overview ..... | 66 |
+| 8.5.2 | Requirements..... | 66 |
+| 9 | Air ground air Communication..... | 67 |
+| 9.1 | Service Description ..... | 67 |
+| 9.2 | Requirements..... | 67 |
+| 10 | MCX Service in IOPS mode..... | 67 |
+
+| | |
+|------------------------------------------------------------------------------------------------------------------|------------|
+| Annex A (normative): MCCoRe Requirements for MCPTT ..... | 68 |
+| Annex B (normative): MCCoRe Requirements for MCVideo..... | 79 |
+| Annex C (normative): MCCoRe Requirements for MCData ..... | 89 |
+| Annex D (informative): Characteristics and traffic assumptions for air ground air
communications..... | 100 |
+| D.1 Environment..... | 100 |
+| D.2 Altitudes ..... | 101 |
+| D.3 Maximum speed and mobility..... | 101 |
+| D.4 Traffic assumptions..... | 101 |
+| Annex E (informative): Variables..... | 101 |
+| Annex F (informative): Change history ..... | 102 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document provides the service requirements that are common across two or more mission critical services, that is MCPTT, MCData and MCVideo. The mission critical services make use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service as specified in 3GPP TS 22.179 [1], MCVideo Service as specified in 3GPP TS 22.281 [2], and MCData Service as specified in 3GPP TS 22.282 [3]. The mission critical services can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.
+
+# --- 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 TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
+- [2] 3GPP TS 22.281: "Mission Critical Video services".
+- [3] 3GPP TS 22.282: "Mission Critical Data services".
+- [4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+- [6] 3GPP TS 22.468: "Group Communication System Enablers for LTE (GCSE\_LTE) ".
+- [7] 3GPP TS 22.011: "Service accessibility".
+- [8] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Stations (MS) in idle mode".
+- [9] ISBN 2-7461-1832-4: "UIC Project EIRENE System Requirements Specification".
+- [10] ETSI EN 301 515 V3.0.0 (2018-03): "Global System for Mobile communication (GSM); Requirements for GSM operation on railways".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [4].
+
+**Affiliated MCX Service Group Member:** An MCX Service Group Member who has indicated an interest in participating in communications of the group, has been accepted by the MCX Service, and is prepared to receive and/or transmit Group Communications from/to the particular MCX Group.
+
+**Air ground air Communication:** A communication (point-to-point or group) between at least one MCX User located on the ground and one or more MCX Users in helicopter(s) or aircraft while not on the ground, but in flight (in the air).
+
+**Broadcast Group Communication:** A group communication where the initiating MCX User expects no response from the other MCX Users, so that when the user's transmission is complete, so is the communication.
+
+**Group Communication:** A one-to-many or many-to-many communication using an MCX Service.
+
+**In-progress Emergency:** An emergency condition that has been accepted by the MCX Service, but has not yet been cancelled.
+
+**Late Entry:** An Affiliated MCX Service Group Member joins in an in progress MCX Service Group Communication.
+
+**Location:** The current position and if available information about the instantaneous velocity and direction of the MCX UE, and other attributes e.g., a label indicating a geographic area in which the MCX UE is located.
+
+NOTE 1: Location and Location information terms can be used interchangeably.
+
+**MCX Service Ad hoc Group Communication:** The combining of a multiplicity of MCX Users into a group for the duration of a communication and when the communication is terminated the group no longer exists.
+
+**MCX Service Ad hoc Group Emergency Alert:** The combining of a multiplicity of MCX Users into a group for sending an emergency alert.
+
+**MCX Service Administrator:** An individual authorized to control MCX parameters for an organization including, for example, user and group definitions, user/group aliases, user priorities, group membership/priorities/hierarchies, security and privacy controls.
+
+**MCX Service Emergency Alert:** A notification from the MCX UE to the MCX Service that the MCX User has an emergency condition.
+
+**MCX Service Emergency State:** A heightened condition of alarm for an MCX User indicating a need for immediate assistance due to a personal life-threatening situation.
+
+**MCX Service Emergency Group Communication:** An urgent MCX Service group communication initiated by a MCX user when there is the potential of immediate death or serious injury.
+
+**MCX Service Group:** A defined set of MCX Users with associated communication dispositions (e.g. media restrictions, default priority and commencement directions).
+
+**MCX Service Group Communication:** A group communication for a particular MCX Service.
+
+**MCX Service Group Member:** An MCX User authorized, upon successful affiliation, to participate in Group Communications of a particular MCX Group.
+
+**MCX Service Imminent Peril Group Communication:** An urgent MCX Service Group Communication initiated by an MCX user when there is a potential of death or serious injury, but is less critical than an MCX Service Emergency Group Communication.
+
+**MCX Service User Profile:** The set of information associated to an MCX User that allows that user to employ the MCX Service in a given role and/or from a given MCX UE.
+
+**MCX UE:** A UE that can be used to participate in MCX Services.
+
+**MCX User:** A user of MCX Service, who can use an MCX UE to participate in MCX Services.
+
+**Mission Critical:** Quality or characteristic of a communication activity, application, service or device, that requires low setup and transfer latency, high availability and reliability, ability to handle large numbers of users and devices, strong security and priority and pre-emption handling.
+
+**Mission Critical Applications:** Generic communication applications with mission critical characteristics, traditionally encompassing push-to-talk voice (MCPTT), real-time video (MCVideo) and real-time data (MCData).
+
+NOTE 2: The short name, **MCX**, is used instead, with X standing for PTT, Video or Data
+
+**Mission Critical Organization:** An end-user organization that includes MCX Users and/or MCX UEs, and can include MCX Service Administrators, and can be organized hierarchically with administrative control delegated within the organization or to an outside entity.
+
+**Mission Critical Service:** Communication service providing enabling capabilities for Mission Critical Applications that are provided to end users from Mission Critical Organizations or other businesses and organizations (e.g., utilities, railways).
+
+NOTE 3: The short name, MCX Service, can be used instead.
+
+**Participant:** An MCX User who is currently receiving and/or transmitting in a Group Communication or a Private Communication.
+
+**Participant type:** Functional category of the Participant (e.g., first responder, second responder, dispatch, dispatch supervisor), typically defined by the MCX Service Administrators.
+
+**Private Communication:** A one-to-one communication between a pair of users using an MCX Service.
+
+**Selected MCX Service Group:** An MCX Service Group that a particular Affiliated MCX Service Group Member uses for transmission.
+
+**Transmitting MCX Service Group Member:** An Affiliated MCX Service Group Member who is currently transmitting in a Group Communication to a Selected MCX Service Group.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [4] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [4].
+
+| | |
+|-------------|---------------------------------------------------------|
+| MCCoRe | Mission Critical Services Common Requirements |
+| MCData | Mission Critical Data |
+| MCPTT | Mission Critical Push To Talk |
+| MCVideo | Mission Critical Video |
+| MCX | Mission Critical X, with X = PTT or X= Video or X= Data |
+| MCX Service | Mission Critical Service |
+
+# --- 4 Overview
+
+## 4.1 Rationale for MCCoRe
+
+Further development of mission critical services beyond Mission Critical Push To Talk (MCPTT), such as Mission Critical Video (MCVideo) and Mission Critical Data (MCData), created an opportunity to re-use base functionality documented in the Stage 1 requirements for MCPTT. For example, the ability to communicate mission critical information to groups of users is a common need regardless of service type. Wherever originating MCPTT requirements were found to be in common with other mission critical services, those requirements were moved to this Technical Specification (3GPP TS 22.280). Each requirement that was moved has been voided in 3GPP TS 22.179, and an informative annex has been created at the end of that specification documenting the location of the originating 3GPP TS 22.179 requirement in the present document.
+
+## 4.2 MCCoRe creation process
+
+The creation of 3GPP TS 22.280 followed a thorough analysis by mission critical application stakeholders of all the requirements in 3GPP TS 22.179, TR 22.879, and TR 22.880. Each set of requirements was evaluated, requirement-by-requirement, to determine if any one requirement was applicable to another service (MCPTT, MCVideo, or MCData). If anyone requirement was shared between two or more services, it was designated as a Mission Critical Services Common Requirements (MCCoRe) requirement and placed into this technical specification. At the end of this specification, there are sets of normative annexes that enumerate each requirement in the present document that is
+
+applicable to the given scope for the annex. For instance, one annex covers MCPTT, and there is a comprehensive table that lists every requirement that follows in clauses 5-9 that are applicable to MCPTT.
+
+In the present document the term, MCX Service, is used to mean any mission critical service and when applied in requirements it means any mission critical service that is identified in the normative annexes as applying to the requirement in question. When the term, MCX Service, is used multiple times in a single requirement it means the same MCX Service except in the case of the inter service interworking in clause 8. Therefore, other than requirements in the inter services interworking clause, all requirements in the present document are single service requirements.
+
+In principle, a mission critical group could use multiple services. At any time during a mission critical group communication, a group of mission critical users can, subject to permissions and availability of services and capable UEs, start or stop using any one or more instantiation(s) of any of the MCX services. In the text of the specification for each individual service, the group is considered to use the services of that individual type, and consequently is called MCPTT Group, MCVideo Group, MCData Group, or generically, MCX Service Group. Referring to a group as an individual service group is for writing simple requirements purposes, and does not mean that the group cannot actively use other services. See sub-clause 8.4 for more information.
+
+The grouping and consolidation of common requirements shared by multiple mission critical applications is not to be construed as a statement or requirement of architectural design, impacting entities and interfaces. It is for downstream working groups to determine whether they can:
+
+- a) create generic MCX Service functionality that can be re-used by all Mission Critical Applications virtually unmodified;
+- b) extend and/or customize common MCX Services, if they determine that a Mission Critical Application has special needs, or
+- c) define separate support for Mission Critical Applications if they determine that they are so specialized that they cannot take advantage of a common MCX Service.
+
+# --- 5 MCX Service requirements common for on the network and off the network
+
+## 5.1 General Group Communications requirements
+
+### 5.1.1 General aspects
+
+[R-5.1.1-001] The MCX Service shall allow an MCX User utilizing one or more MCX UE(s), concurrently, to sign-in and receive service on each of the MCX UE(s).
+
+[R-5.1.1-002] The MCX Service shall provide a mechanism by which an MCX UE makes a MCX Service group transmission to any MCX Service Group(s) for which the current MCX User is authorized.
+
+NOTE: For off-network use, only group members with MCX UEs within communication range receive the transmission.
+
+[R-5.1.1-003] The MCX Service shall be able to notify the Affiliated MCX Service Group Members when the group communication is set up (e.g., this can be provided as an audible tone on the MCX UE).
+
+[R-5.1.1-004] The MCX Service shall provide a mechanism to disable notifications (e.g., audible tone) on an MCX UE when receiving normal MCX Service Group Communications (not MCX Service Emergency or Imminent Peril Communications).
+
+[R-5.1.1-005] At any moment in time in an MCX Service Group communication, only one Participant type shall be used per Participant.
+
+[R-5.1.1-006] The MCX Service shall provide a mechanism for a dispatcher or authorized user to configure which content source shall be able to transmit the content to an MCX Service Group (e.g. video cameras near an incident).
+
+### 5.1.2 Group/status information
+
+[R-5.1.2-001] The MCX Service shall provide a mechanism by which an MCX Service UE determines in which of the MCX Service Groups for which it is authorized there is an on-going MCX Service Group Communication.
+
+[R-5.1.2-002] The MCX Service shall provide a mechanism by which an authorized MCX User determines in which MCX Service Groups there is an on-going MCX Service Group Communication.
+
+### 5.1.3 Group configuration
+
+[R-5.1.3-001] The MCX Service shall allow the MCX Service Administrator to restrict who can be a member of specific MCX Service Groups, so that those MCX Service Groups shall be inaccessible to other users, including dispatchers or supervisors.
+
+[R-5.1.3-002] The MCX Service shall enable a properly provisioned and authorized MCX UE operating on the network to receive its application layer level parameters (e.g., MCX Service Group ID, group keys) necessary for initiating and participating in Selected MCX Service Group and Private Communications at a future time, while off the network.
+
+NOTE: This is a "run-time" requirement applicable to an already configured MCX UE, when MCX Service Groups and/or MCX Users, in addition to what was already configured, need to participate in future off-network communications.
+
+### 5.1.4 Identification
+
+[R-5.1.4-001] The MCX Service shall support identifiers using character sets for international languages specified via configuration.
+
+### 5.1.5 Membership/affiliation
+
+[R-5.1.5-001] The MCX Service shall provide a mechanism by which an MCX User determines the currently defined MCX Service Groups for which the MCX User is authorized.
+
+[R-5.1.5-002] The MCX Service shall provide a mechanism by which an MCX UE determines the currently defined MCX Service Groups for which it is authorized.
+
+[R-5.1.5-003] The MCX Service shall support an MCX User's ability to affiliate to one or more MCX Service Groups.
+
+[R-5.1.5-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to limit the total number (Nc2) of MCX Service Groups that an MCX User can be affiliated to simultaneously.
+
+[R-5.1.5-005] An MCX User may simultaneously be an MCX Service Group Member of one or more MCX Service Groups.
+
+[R-5.1.5-006] The MCX Service shall provide a mechanism for an MCX Service Group Member to select zero or one Selected MCX Service Group.
+
+[R-5.1.5-007] The MCX Service shall require that MCX Users affiliate with MCX Service Groups prior to participation in the communications of those groups.
+
+[R-5.1.5-008] An MCX User shall be able to affiliate with a multiplicity of MCX Service Groups, subject to restrictions configured by the MCX Service Administrator.
+
+### 5.1.6 Group Communication administration
+
+[R-5.1.6-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum duration for MCX Service Group Communications for MCX Users within their authority.
+
+### 5.1.7 Prioritization
+
+[R-5.1.7-001] The MCX Service shall provide a mechanism to organize MCX Service Groups into a hierarchy(ies).
+
+[R-5.1.7-002] The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).
+
+### 5.1.8 Charging requirements for MCX Service
+
+[R-5.1.8-001] The MCX Service shall support charging for MCX Service Group Communications.
+
+[R-5.1.8-002] Void
+
+[R-5.1.8-003] The MCX Service shall support time-of-day sensitive charging based on actual resource utilization, provided QoS and provided priority.
+
+[R-5.1.8-004] The MCX Service shall generate charging data that identifies the device(s) involved in a communication.
+
+[R-5.1.8-005] The MCX Service shall support confidentiality of the charging between the service provider and the network operator.
+
+[R-5.1.8-006] The MCX Service shall support confidentiality of the identity of the Mission Critical Organization.
+
+[R-5.1.8-007] The MCX Service shall support reconciliation of the charging records between the service provider and the network operator.
+
+[R-5.1.8-008] The MCX Service shall support offline charging.
+
+[R-5.1.8-009] The MCX Service shall support online charging.
+
+[R-5.1.8-010] The MCX Service shall be able to generate charging data for on-network mode.
+
+[R-5.1.8-011] The MCX Service shall be able to generate charging data for off-network mode.
+
+### 5.1.9 MCX Service Emergency Alert triggered by Location
+
+[R-5.1.9-001] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be triggered when an MCX UE moves into a predefined area.
+
+[R-5.1.9-002] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be cancelled when the MCX UE moves out of a predefined area or to remain active until cancelled by the MCX User.
+
+## 5.2 Broadcast Group
+
+### 5.2.1 General Broadcast Group Communication
+
+[R-5.2.1-001] The MCX Service shall support Broadcast Group Communications within that MCX Service from authorized MCX Service Group Members as determined by the MCX Service Administrator.
+
+[R-5.2.1-002] The MCX Service shall only allow the initiating MCX Service Group Member to transmit on a Broadcast Group Communication, unless overridden (e.g., by a supervisor).
+
+### 5.2.2 Group-Broadcast Group (e.g., announcement group)
+
+[R-5.2.2-001] The MCX Service shall provide for the creation of Group-Broadcast Groups within that MCX Service with up to Bc1 levels of group hierarchy.
+
+[R-5.2.2-002] The MCX Service shall be configurable to create a Group-Broadcast Group from one or more Group-Broadcast Groups within that MCX Service with any other non-Broadcast Group from the same MCX Service.
+
+[R-5.2.2-003] The MCX Service shall enable an MCX Service Administrator to create a Group-Broadcast Group.
+
+[R-5.2.2-004] A Broadcast Group Communication transmitted on a Group-Broadcast Group shall have priority over Group Communications on its subordinate groups from the same MCX Service.
+
+### 5.2.3 User-Broadcast Group (e.g., System Communication)
+
+[R-5.2.3-001] The MCX Service shall provide for the creation of User-Broadcast Groups within that MCX Service with up to Bc2 levels of user hierarchy.
+
+[R-5.2.3-002] A Broadcast Group Communication transmitted on a User-Broadcast Group shall have priority over Group Communications from the same MCX Service involving users within the user hierarchy.
+
+## 5.3 Late communication entry
+
+[R-5.3-001] The MCX Service shall provide a mechanism by which an Affiliated MCX Service Group Member can join an on-going MCX Service Group Communication.
+
+[R-5.3-002] The MCX Service shall provide the identities of the transmitting MCX Service Group Member, and of the MCX Service Group and, if available, the aliases of the transmitting MCX Service Group Member and the identity of the Mission Critical Organization to the MCX UEs that enter the communication late.
+
+[R-5.3-003] The MCX Service shall provide the transmitting MCX Service Group Member's Location information to MCX UEs that are late entering a communication in progress, subject to permissions.
+
+[R-5.3-004] If an MCX Service Group Communication proceeds without all Affiliated MCX Service Group Members (e.g., due to one or more members being temporarily out of coverage during the communication setup or in one or more higher priority communications), the MCX Service shall attempt to add those affiliated members as the communication proceeds and they become available.
+
+[R-5.3-005] If during an on-going MCX Service Group Communication, additional MCX Service Group Members affiliate with the MCX Service Group, the MCX Service shall add those members to the Group Communication.
+
+[R-5.3-006] When the late entry user(s) become(s) member of the Group communication, all participants may be notified about the late entry member joining the Group communication.
+
+## 5.4 Receiving from multiple MCX Service communications
+
+### 5.4.1 Overview
+
+MCX Users receive communications traffic of their affiliated MCX Service Groups. This multiple receiving, called monitoring by some organizations, provides MCX Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCX User is deployed to provide additional support for that event. The MCX User might be assigned to support the activities of more than one MCX Service Group on the same shift. This means that the MCX User receives multiple MCX Service Groups.
+
+An MCX User with limited resources (e.g., a handheld UE) might find that using concurrent received MCX Service communications from multiple active MCX Service Groups becomes confusing. During periods of time when the MCX User is receiving communications from multiple MCX Service Groups, which MCX Service Group's communication is presented to the MCX User is determined by the MCX User's choice, the priority associated with the sender of the Selected MCX Service Group, other considerations or combinations of these. The MCX UE is aware of all the active groups to which the MCX User has affiliated and which is the selected group (if any). The identities of the other active receiving groups can be made available for display on the MCX UE. When the receive activity from the Selected MCX Service Group stops, the MCX UE might present the communications from another group per the MCX User's choice or by other means.
+
+If none of the multiple groups to which the MCX User has affiliated or selected is active, the MCX UE would continue to monitor for activity by any of the multiple affiliated or Selected MCX Service Groups. Monitoring for activity of multiple MCX Service Groups is also known as scanning and the list of the multiple groups is also known as a scan list.
+
+### 5.4.2 Requirements
+
+[R-5.4.2-001] The MCX Service shall allow an MCX UE to be receiving or transmitting in one MCX Service Group while simultaneously receiving additional MCX Service Groups.
+
+[R-5.4.2-002] The MCX Service shall provide a mechanism to configure the number (Ne4) of MCX Service Group Communications to be simultaneously received by an MCX UE, authorized by an MCX Service Administrator and/or authorized user.
+
+[R-5.4.2-003] The MCX Service shall provide a mechanism to configure the number (Ne5) of MCX Service Group Communications to be simultaneously received by an MCX User, authorized by an MCX Service Administrator and/or authorized user.s
+
+[R-5.4.2-004] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to prioritize the order in which communications on multiple MCX Service Groups within an MCX Service User Profile are presented by the MCX user's MCX UE.
+
+[R-5.4.2-004A] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to prioritize the order in which multiple MCX Service Private Communications are presented by the MCX user's MCX UE.
+
+[R-5.4.2-004B] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to prioritize the order in which communications on MCX Service Groups within an MCX Service User Profile and MCX Service Private Communications are presented by the MCX user's MCX UE.
+
+[R-5.4.2-005] The MCX Service shall provide multiple MCX Service User IDs to an MCX UE when multiple MCX Service Groups that have a sender are received by the MCX UE.
+
+[R-5.4.2-006] The MCX Service shall allow an authorized MCX UE to receive on-network MCX Service Group and off-network MCX Service Group Communications simultaneously.
+
+[R-5.4.2-007] The MCX Service shall ensure that if there is an MCX Service Emergency Group Communication on one of the MCX Service Groups that an MCX User is affiliated to, but that user is already in a lower priority MCX Service Group Communication or Private Communication, that the MCX User automatically hears/displays the MCX Service Emergency Group Communication.
+
+[R-5.4.2-007a] Depending on meaningful elements of a functional alias the MCX Service shall be able to restrict or allow MCX Users to be involved in more than one MCX Service Emergency Group Communication at a time.
+
+[R-5.4.2-008] The MCX Service shall support reception and recording of multiple concurrent Private Communications by an authorized user (e.g., dispatch operator).
+
+[R-5.4.2-009] The MCX Service shall provide a mechanism by which an MCX UE can receive and record multiple concurrent Private Communications from MCX users for which the current MCX User is authorized.
+
+## 5.5 Private Communication
+
+### 5.5.1 Private Communication general requirements
+
+[R-5.5.1-001] The MCX Service shall provide a mechanism for a dispatcher or authorized user to configure which content source shall be able to send the content to an MCX User (e.g. video cameras near an incident).
+
+### 5.5.2 Charging requirements for MCX Service
+
+[R-5.5.2-001] The MCX Service shall support charging for Private Communications.
+
+## 5.6 MCX Service priority requirements
+
+### 5.6.1 Overview
+
+MCX Service Emergency Group Communications and MCX Service Imminent Peril Group Communications are MCX Service Group Communications that provide the MCX User elevated priority towards obtaining resources of the MCX Service system. The MCX Service Emergency Private Communication similarly provides elevated priority to resources of the MCX Service system. The MCX Service Emergency Alert provides a notification of an MCX Service Emergency situation from an MCX UE, regardless if the MCX User is signed in with the MCX Service or not.
+
+The MCX Service Emergency Alert is initiated from an MCX UE to inform the MCX Service of the MCX User's immediate need of assistance due to the MCX User's personal, life-threatening situation. If the MCX User is not properly authenticated, he/she is treated as a temporary MCX User with limited permissions. The MCX User initiates this notification by actuating an MCX User interface on the MCX UE. The notification to the MCX Service includes the MCX User's ID, potentially an MCX Service Group ID, the user's Mission Critical Organization name and the most current location available for the user's MCX UE.
+
+The MCX Service User Profile/group configuration determines which MCX Service Group ID is used, if any. If the MCX Service User Profile indicates that a dedicated (i.e., not used for everyday traffic) MCX Service Emergency Group is to be used, then the MCX Service Emergency communication traffic moves to a different group. MCX Users that support MCX Service Emergency situations monitor the dedicated MCX Service Emergency Group(s) for communications activity. If the MCX Service User Profile indicates that the Selected MCX Service Group is to be used, then its MCX Service Group ID is used, unless no group is selected for transmissions.
+
+After the MCX User has initiated an MCX Service Emergency Alert, MCX Service Emergency Private Communication or MCX Service Emergency Group Communication, the MCX User is considered to be in the MCX Service Emergency State. The user remains in the MCX Service Emergency State until the MCX User cancels the MCX Service Emergency State.
+
+An MCX Service Group Communication started by an MCX User while in the MCX Service Emergency State or previously started but followed by an MCX Service Emergency Alert becomes an MCX Service Emergency Group Communication. The MCX Service Group ID used for the MCX Service Emergency Group Communication is the same MCX Service Group ID included in the MCX Service Emergency Alert. An MCX User or dispatcher might initiate an MCX Service Emergency Group Communication without an MCX Service Emergency Alert. The start of an MCX Service Emergency Group Communication starts an In-progress Emergency condition for the MCX Service Group. Any subsequent MCX Service Group Communications made by any MCX Service Group Member of an MCX Service Group, which has an In-progress Emergency, is treated as an MCX Service Emergency Group Communication. MCX Service Emergency Group Priority is removed when the In-progress Emergency for the group is cancelled.
+
+An MCX Service Private Communication started by an MCX User while in the MCX Service Emergency State becomes an MCX Service Emergency Private Communication.
+
+MCX Service Imminent Peril Group Communications are differentiated from MCX Service Emergency Group Communications based on for whom the assistance is required. The MCX Service Emergency Group Communication is initiated by an MCX User for assistance for the MCX Service Emergency condition involving that user. An MCX Service Imminent Peril Group Communication is initiated by an MCX User for assistance to other MCX Users or persons of the general public observed to be in trouble and may soon need assistance.
+
+There is no MCX Service Imminent Peril Alert and no MCX Service Imminent Peril State for MCX Users. The granting of an MCX Service Imminent Peril Group Communication starts an In-progress Imminent Peril condition for the MCX Service Group. Any subsequent MCX Service Group Communication made by any MCX Service Group Member of an MCX Service Group that has an In-progress Imminent Peril condition is treated as an MCX Service Imminent Peril Group Communication. MCX Service Imminent Peril Group Priority is removed when the In-progress Imminent Peril for the group is cancelled.
+
+### 5.6.2 Communication types based on priorities
+
+#### 5.6.2.1 MCX Service Emergency and Imminent Peril general requirements
+
+##### 5.6.2.1.1 Overview
+
+Emergency Group Communication and Imminent Peril Group Communication are MCX Service Group Communications that provide the MCX User elevated priority towards obtaining resources of the MCX Service system. The MCX Service Emergency Alert provides a notification of an MCX Service Emergency situation from an MCX UE, regardless if the user is signed in with the MCX Service or not. The MCX Service Emergency Alert is initiated from an MCX UE to inform the MCX Service of the user's immediate need of assistance due to the user's personal, life-threatening situation.
+
+When multiple MCX Services are active in an MCX UE, the interaction of these features between the services needs to be considered. When an MCX User initiates an Emergency Group Communication, he/she may only want a subset of the active MCX Services to have emergency priority. Likewise, for Imminent Peril the North American user requirement is that only the active MCX Service receives Imminent Peril priority when the Imminent Peril condition is initiated. For example, if the MCX User is transmitting a video when he/she initiates Imminent Peril, then only the MCVideo service will be granted elevated priority.
+
+##### 5.6.2.1.2 Requirements
+
+[R-5.6.2.1.2-001] When an MCX User initiates an MCX Service Emergency Group Communication, a subset of MCX Service applications (e.g. MCPTT, MCVideo) relevant to the MCX User and configured for the MCX Service Group, shall be used for MCX Service Emergency Group Communications.
+
+[R-5.6.2.1.2-002] The MCX Service shall support an MCX Service Emergency Alert, which on initiation by an MCX User shall put that MCX User into the MCX Service Emergency State and cause that MCX UE to send an MCX Service Emergency Alert containing the following information: Location, MCX Service User ID, the user's Mission Critical Organization name, the list of notification IDs (e.g. groups, other users), and the list of application service MCX Service Group IDs to be used for MCX Service Emergency Group Communication (i.e., user's selected group or dedicated MCX Service Emergency Group).
+
+[R-5.6.2.1.2-003] The MCX Service in the UE shall request Imminent Peril priority for the currently active MCX Service Application (e.g. MCPTT, MCVideo) when the MCX User requests an MCX Service Imminent Peril Group Communication.
+
+[R-5.6.2.1.2-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Applications (e.g. MCPTT, MCVideo) are used for MCX Service Emergency Group Communications by an MCX User when that user is in an MCX Service Emergency State.
+
+[R-5.6.2.1.2-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Applications (e.g. MCPTT, MCVideo) can be used for Imminent Peril Group Communication.
+
+#### 5.6.2.2 MCX Service Emergency Group Communication
+
+##### 5.6.2.2.1 MCX Service Emergency Group Communication requirements
+
+[R-5.6.2.2.1-001] The MCX Service shall support MCX Service Emergency Group Communications from an authorized MCX Group Member on the currently Selected MCX Group or on an MCX Group designated for MCX Service Emergency Group Communications.
+
+[R-5.6.2.2.1-002] When an MCX User initiates an MCX Service Emergency Group Communication this may trigger an MCX Service Emergency Alert for that MCX User.
+
+[R-5.6.2.2.1-003] When an MCX User initiates an MCX Service Emergency Group Communication this shall put that MCX User into an MCX Service Emergency State.
+
+[R-5.6.2.2.1-004] The MCX Service shall ensure that MCX Service Emergency Group Communications have the highest priority over all other MCX Service Group transmissions from the same MCX Service, except MCX Service
+
+System Communications, MCX Service Emergency Private Communications, and other MCX Service Emergency Group Communications.
+
+[R-5.6.2.2.1-005] The MCX Service shall be capable of changing a group communication in progress to an MCX Service Emergency Group Communication.
+
+[R-5.6.2.2.1-006] MCX Service Emergency Group Communications, including their content and signalling, shall have pre-emptive priority over all other types of MCX Service communications from the same MCX Service, except MCX Service System Communications, MCX Emergency Private Communications, and other MCX Service Emergency Group Communications.
+
+[R-5.6.2.2.1-007] The MCX Service shall provide the MCX Service User ID of the initiator of an MCX Service Emergency Group Communication and an indication that it is an MCX Service Emergency Group Communication to Affiliated MCX Service Group Members.
+
+[R-5.6.2.2.1-008] The MCX Service shall add the MCX Service Emergency priority to the group when an In-progress Emergency on that group is initiated.
+
+[R-5.6.2.2.1-009] The MCX Service shall remove the MCX Service Emergency Priority associated with the group when an In-progress Emergency on that group is cancelled.
+
+**Editor's Note: The interaction of MCX Service Emergency Communication and Imminent Peril Communication is FFS.**
+
+[R-5.6.2.2.1-010] The Affiliated MCX Service Group Members shall be notified when their group communication transitions to an In-progress Emergency.
+
+[R-5.6.2.2.1-011] The MCX Service shall maintain knowledge of the Affiliated MCX Service Group Member(s) that initiated the MCX Service Emergency Group Communication(s) until the In-progress Emergency is cancelled.
+
+[R-5.6.2.2.1-012] The MCX Service shall maintain an In-progress Emergency condition for a group from the time the initial MCX Service Emergency Group Communication was requested until the In-progress Emergency condition is cancelled.
+
+[R-5.6.2.2.1-013] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated MCX Service Emergency Group) is used for the MCX Service Emergency Group Communication by an MCX User.
+
+[R-5.6.2.2.1-014] While In-progress Emergency status is maintained for an MCX Service Group Communication, the MCX Service shall provide the MCX Service User ID of the initiator of the In-progress Emergency status and an indication that it is an MCX Service Emergency Group Communication to existing and Late communication entry Affiliated MCX Service Group Members.
+
+##### 5.6.2.2.2 MCX Service Emergency Group Communication cancellation requirements
+
+[R-5.6.2.2.2-001] The MCX Service shall support cancellation of an In-progress Emergency by an authorized MCX User for an MCX Service Group.
+
+[R-5.6.2.2.2-002] The MCX Service shall support cancellation of an In-progress Emergency for an MCX Service Group when criteria established by the MCX Service Administrator are met (e.g., timeout).
+
+[R-5.6.2.2.2-003] The MCX Service shall support cancellation of an In-progress Emergency for an MCX Service Group and MCX Service Emergency State for an MCX User by the MCX Service Emergency Group Communication initiator.
+
+[R-5.6.2.2.2-004] The MCX Service shall notify Affiliated MCX Service Group Members of the cancellation of the In-progress Emergency and the identity of the cancelling MCX User.
+
+[R-5.6.2.2.2-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to cancel in-progress Emergencies.
+
+#### 5.6.2.3 MCX Service Imminent Peril Group Communication
+
+##### 5.6.2.3.1 MCX Service Imminent Peril Group Communication requirements
+
+[R-5.6.2.3.1-001] The MCX Service shall support Imminent Peril group communications from authorized Affiliated MCX Service Group Members.
+
+[R-5.6.2.3.1-002] The MCX Service (e.g. MCPTT, MCVideo) shall ensure that MCX Service Imminent Peril group communications have priority over all other MCX Service Group transmissions from the same MCX Service, except MCX Service System Communications, MCX Service Emergency Group Communications, MCX Service Emergency Private Communications, and other MCX Service Imminent Peril group communications.
+
+[R-5.6.2.3.1-003] The MCX Service shall be capable of changing an MCX Service Group communication in progress to an Imminent Peril group communication.
+
+[R-5.6.2.3.1-004] MCX Service Imminent Peril group communications, including their content and signalling, shall have pre-emptive priority over all other types of MCX Service communications from the same MCX Service, except MCX Service Emergency Group Communications, MCX Service Emergency Private Communications, MCX Service System Communications, and other MCX Service Imminent Peril group communications.
+
+[R-5.6.2.3.1-005] The Affiliated MCX Service Group Members shall be notified when an MCX Service Group communications transitions to In-progress Imminent Peril status.
+
+[R-5.6.2.3.1-006] While Imminent Peril status is maintained for an MCX Service Group communications, the MCX Service shall provide the MCX Service User ID of the initiator of the Imminent Peril status and an indication that it is an Imminent Peril group communication to existing and Late communication entry Affiliated MCX Service Group Members.
+
+[R-5.6.2.3.1-007] The MCX Service shall add the Imminent Peril priority to the group when an In-progress Imminent Peril on that group is initiated.
+
+[R-5.6.2.3.1-008] The MCX Service shall remove the Imminent Peril priority associated with the MCX Service Group when the In-progress Imminent Peril status of that MCX Service Group is cancelled.
+
+**Editor's note: The interaction of MCX Service Emergency Communication and Imminent Peril Communication is FFS.**
+
+[R-5.6.2.3.1-009] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated imminent peril group) shall be used for the Imminent Peril communications for an MCX User.
+
+##### 5.6.2.3.2 MCX Service Imminent Peril Group Communication cancellation requirements
+
+[R-5.6.2.3.2-001] The MCX Service shall support cancellation of an In-progress Imminent Peril by an authorized MCX User.
+
+[R-5.6.2.3.2-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize MCX Service Users to cancel an In-progress Imminent Peril.
+
+[R-5.6.2.3.2-003] The MCX Service shall support cancellation of an In-progress Imminent Peril by the Imminent Peril group communication initiator.
+
+[R-5.6.2.3.2-004] The MCX Service shall support cancellation of an In-progress Imminent Peril when criteria created by the MCX Service Administrator are met.
+
+#### 5.6.2.4 MCX Service Emergency Alert
+
+##### 5.6.2.4.1 MCX Service Emergency Alert requirements
+
+[R-5.6.2.4.1-001] The MCX Service shall support an MCX Service Emergency Alert capability, which on initiation by an MCX User shall put that MCX User into the MCX Service Emergency State and cause that MCX UE to send an MCX Service Emergency Alert.
+
+[R-5.6.2.4.1-002] The MCX Service shall provide a means for an authorized user to be able to activate the MCX Service Emergency Alert capability.
+
+[R-5.6.2.4.1-003] The MCX Service Emergency Alert shall contain the following information: Location, MCX Service User ID and MCX Service Group ID (i.e., user's selected group or dedicated MCX Service Emergency Group, as per group configuration) and the user's Mission Critical Organization name.
+
+[R-5.6.2.4.1-004] The MCX Service Emergency Alert shall be distributed to affiliated members of the group that was used in the MCX Service Emergency Alert.
+
+[R-5.6.2.4.1-004a] For an MCX Service Emergency Private Communication the MCX Service Emergency Alert shall be distributed to the MCX User that the communication was initiated to.
+
+[R-5.6.2.4.1-005] The MCX Service shall provide a mechanism for an authorized MCX User to configure an MCX Service Emergency Alert to send a notification to MCX Users within a configurable geographic area of the MCX User entering the MCX Service Emergency State, independent of the MCX Service Group Membership.
+
+[R-5.6.2.4.1-006] The MCX UE shall maintain knowledge of the MCX Service Emergency State, until cancelled.
+
+[R-5.6.2.4.1-007] Until the MCX Service Emergency State is cancelled on the MCX UE, all MCX Service Group communications or Private Communications transmissions by the MCX User shall be an MCX Service Emergency Group Communication or Emergency Private Communication.
+
+[R-5.6.2.4.1-008] The MCX UE shall be configurable as to which group (i.e., user's selected group or dedicated MCX Service Emergency Group) or MCX User is used for the MCX Service Emergency communications.
+
+[R-5.6.2.4.1-009] The MCX UE shall immediately affiliate to the group configured for MCX Service Emergency Group Communication, if not already affiliated to the group, after activating an MCX Service Emergency Alert.
+
+[R-5.6.2.4.1-010] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure how an MCX User is notified of an incoming MCX Service Emergency Alert (e.g., visual, audio).
+
+[R-5.6.2.4.1-011] The MCX Service shall provide a mechanism for an MCX User to configure, subject to MCX Service Policy, how they are notified of an incoming MCX Service Emergency Alert (e.g., visual, audio).
+
+[R-5.6.2.4.1-012] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated MCX Service Emergency Group) or MCX User (e.g., dispatcher) is used for the MCX Service Emergency Alert by an MCX User.
+
+[R-5.6.2.4.1-013] The MCX Administrator shall be able to configure whether the initiation of a MCX Service Emergency Alert shall also automatically trigger a MCX Service Emergency Group Communication.
+
+##### 5.6.2.4.2 MCX Service Emergency Alert cancellation requirements
+
+[R-5.6.2.4.2-001] The MCX UE shall only provide a means for cancelling the MCX Service Emergency State locally by an authorized user of that MCX UE.
+
+[R-5.6.2.4.2-002] The MCX Service shall support MCX Service Emergency Alert cancellation by authorized MCX Users.
+
+[R-5.6.2.4.2-003] The MCX Service shall distribute MCX Service Emergency Alert cancellation to all affiliated members of the group identified in the cancellation.
+
+## 5.7 MCX Service User ID
+
+[R-5.7-001] The MCX Service shall provide a mechanism for the creation and deletion of aliases for an MCX User and its associated MCX Service User Profiles by authorized parties.
+
+[R-5.7-002] The MCX Service shall provide a mechanism for each MCX Service User ID to be associated with an alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) assigned by an MCX Service Administrator.
+
+[R-5.7-003] All UEs shall provide a configurable capability to display the MCX Service User ID, aliases associated with the MCX Service User ID, with the Selected MCX Service Group, and with the Mission Critical Organization name.
+
+## 5.8 MCX UE management
+
+[R-5.8-001] An MCX UE shall support one or more MCX Service User Profiles.
+
+[R-5.8-002] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized MCX User to perform MCX UE Provisioning.
+
+## 5.9 MCX Service User Profile
+
+[R-5.9-001] The MCX Service shall ensure that each MCX User has at least one associated MCX Service User Profile that records the MCX User's: information, including permissions and privileges with respect to the MCX Service.
+
+NOTE: Examples of profile information include: their MCX Service User ID, which MCX Service Groups they are a member of, their Participant type, which authority they belong to, whether they can make/receive Private Communications.
+
+[R-5.9-002] The MCX Service shall provide a means for an MCX Service Administrator to manage the MCX Service User Profile for MCX Users within their authority.
+
+## 5.9a Functional alias
+
+### 5.9a.1 Overview
+
+A functional alias is a user selectable alias that is tied to the assignment or task of the user. A MCX User can activate one or multiple functional aliases at the same time. The activation of the functional alias(es) will take place after the user has signed in to the MCX Service using the MCX User ID.
+
+The same functional alias can be assigned for use to multiple users depending on MCX Service Administrator settings. A functional alias can be taken over by an authorized MCX User, depending on MCX Service Administrator settings. These two capabilities are mutually exclusive and can not be configured for the same functional alias.
+
+A functional alias can be used to identify for example the driver(s) of a particular train, identified by train number and the role of the user on that train.
+
+Each functional alias that is active on the MCX Service system is unique for addressing purposes. For example, if there are two drivers of TRAIN29 (e.g. DRIVER1\_TRAIN29, DRIVER2\_TRAIN29), then each active functional alias should be uniquely addressable.
+
+A functional alias can be structured into meaningful elements (e.g. user.agency@organization.country, role.mission@department.company, function.equipment.ID@city, label1.label2.label3@firstname.lastname). Based on one or more of these elements in the functional alias, specific sets of MCX users can be selected fore.g. regrouping purposes.
+
+### 5.9a.2 Requirements
+
+[R-5.9a-001] The MCX Service shall provide a mechanism for the MCX User to activate one or more functional alias(es) for use by the MCX Users within that MCX Service system (i.e. the primary MCX Service system of the functional alias).
+
+[R-5.9a-001a] The MCX Service system shall be able to use the functional alias as a unique identifier for MCX Users as Participant of an MCX Service Group, e.g. to display a functional alias as speaker identification or for the use in group member lists.
+
+[R-5.9a-001b] The MCX Service system shall provide a mechanism for an MCX User to assign a functional alias for use on an MCX Service Group.
+
+[R-5.9a-001c] The MCX Service system shall provide a mechanism for an MCX User to assign an activated functional alias for an outgoing MCX Private communication.
+
+[R-5.9a-002] The MCX User shall be reachable by its functional alias(es) from within the MCX Service system where the functional alias was activated.
+
+[R-5.9a-002a] An MCX User shall be reachable by its functional alias from the primary MCX system while migrated to partner MCX Service systems.
+
+[R-5.9a-003] The MCX Service shall provide a mechanism for the MCX User to deactivate a functional alias.
+
+[R-5.9a-004] The MCX Service shall upon request provide the MCX User a list of functional aliases from which the user can select for activation/deactivation.
+
+NOTE: The list may contain functional aliases based on a certain context, like location of the MCX User, operational schedule, etc.
+
+[R-5.9a-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to create, delete, manage functional aliases, and for each functional alias indicate either if it can be simultaneously active for multiple MCX Users up to a per-alias configurable number, or if it is allowed to be taken over by an authorized MCX User, or none of these two options.
+
+[R-5.9a-006] If an MCX User attempts to activate a functional alias that is already active for another MCX User, and is not allowed to be simultaneously active for multiple MCX Users or the number of simultaneous MCX Users is reached to the upper limit, the MCX Service shall inform the MCX User that the functional alias is already in use.
+
+[R-5.9a-007] If an MCX User attempts to activate a functional alias that is already active for at least one other MCX User, and that functional alias is allowed to be simultaneously active for multiple MCX Users and the upper limit of number of simultaneous MCX Users is not reached, the MCX Service shall activate the functional alias for the MCX user and inform all other MCX User(s) with the same functional alias.
+
+[R-5.9a-008] If an authorized MCX User attempts to activate a functional alias that is already used by another MCX User, and that functional alias is allowed to be taken over, and is not indicated for simultaneous activation to multiple MCX Users, the MCX Service shall offer the MCX User to take over the functional alias from the MCX User using the alias.
+
+[R-5.9a-008a] If an authorized MCX User attempts to activate a functional alias that is already active for at least one other MCX User, and the upper limit of number of simultaneous MCX Users is reached, the MCX Service shall reject the MCX User's request.
+
+[R-5.9a-009] If an authorized MCX User takes over the functional alias that is already active for another MCX User, the MCX Service shall activate the functional alias to the MCX User and inform the previous MCX User that the alias has been deactivated.
+
+[R-5.9a-010] The MCX Service shall allow the MCX User to perform an activation/deactivation of an unlisted functional alias that is defined in the MCX Service system.
+
+[R-5.9a-011] An authorized MCX User shall be able to interrogate the MCX Service system of the alias(es) active for a certain MCX User.
+
+[R-5.9a-012] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize a MCX User to activate, deactivate, interrogate and take over a functional alias.
+
+[R-5.9a-013] VOID
+
+[R-5.9a-014] The MCX Service shall allow the functional alias to be structured as a combination of organizationally meaningful elements (e.g. user.agency@organization.country, role.mission@department.company, function.equipment.ID@city, label1.label2.label3@firstname.lastname).
+
+[R-5.9a-015] The MCX Service system shall allow an MCX Service Administrator to make use of information (e.g. operational schedules, locations, velocity or direction) from external sources to create or delete a functional alias.
+
+[R-5.9a-016] The MCX Service system shall allow the MCX Service Administrator to assign a communication priority for a functional alias.
+
+[R-5.9a-017] The MCX Service system shall allow the MCX Service Administrator to assign a time limit to a functional alias after which the functional alias will be deactivated.
+
+[R-5.9a-018] The MCX Service shall support automatic activation and de-activation of a functional alias based on the operational criteria (e.g. MCX User ID, login/logoff from the MCX Service system, specific external information supplied by external systems).
+
+[R-5.9a-019] The MCX Service shall provide a mechanism for an MCX Service Administrator to define a functional alias with related geographic areas that can be associated to MCX Users for the purpose of routing Location dependent communications, as part of handling MCX Service Private Communication requests, when the determination of the receiving party is based on the initiating MCX User's current Location.
+
+[R-5.9a-020] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias or a specific element or combination of specific elements in the functional alias, a set of functional aliases under the same authority to which a Private Communication (without Floor control) can be made by an MCX User registered to this particular functional alias.
+
+[R-5.9a-021] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias or a specific element or combination of specific elements in the functional alias, a set of functional aliases under the same authority from which Private Communication (without Floor control) is allowed to an MCX User registered to this particular functional alias.
+
+[R-5.9a-022] For private calls to functional aliases the authorizations in clause 5.9a.2 shall replace the authorizations defined in clause 6.7.3.
+
+[R-5.9a-023] The MCX Service system shall support private calls and private emergency calls to a functional alias simultaneously activated by multiple MCX Users.
+
+[R-5.9a-024] The MCX Service system shall enable an MCX Service Administrator to select the mechanism to be used for handling of private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users.
+
+[R-5.9a-025] The MCX Service system shall be able to provide a mechanism to inform the MCX User about the functional alias activation/deactivation status (e.g. activation/deactivation accepted, activation/deactivation pending, activation/deactivation rejected).
+
+[R-5.9a-026] The MCX Service shall provide the functional alias(es) of the transmitting MCX Service Group Member that enter the communication late in accordance with sub-clause 5.3.
+
+[R-5.9a-027] The MCX Service shall provide a Location information report for every authorized MCX User associated with one functional alias in accordance with sub-clause 6.12.
+
+[R-5.9a-028] The MCX Service shall provide the functional alias(es) associated with the MCX Service User ID, of the transmitting Participant to the receiving MCX Users (UEs) unless the transmitting Participant's identity is restricted in accordance with sub-clause 6.4.3.
+
+[R-5.9a-029] The MCX Service shall provide, upon request, the list of currently affiliated members of an MCX group which encompasses the MCX Service User ID and the associated functional alias(es) of each member in accordance with sub-clause 6.4.5.
+
+[R-5.9a-030] The MCX Service shall provide a mechanism for the enforcement of uniqueness of a functional alias within a Mission Critical organisation in accordance with sub-clause 6.9.
+
+[R-5.9a-031] The MCX Service shall provide a mechanism for an authorized MCX User to obtain a list of functional aliases currently activated in the system either periodically or as a onetime request.
+
+NOTE: The mechanism may allow for filtering criteria e.g. geographic area.
+
+## 5.10 Support for multiple devices
+
+[R-5.10-001] The MCX Service shall allow an MCX User to log in to multiple MCX UEs concurrently.
+
+[R-5.10-001a] The MCX Service shall be able to allow the MCX Service Administrator to limit the number of simultaneous logins of MCX Users to multiple MCX UEs on a per-MCX service basis.
+
+[R-5.10-001b] The MCX Service shall be able to allow the MCX Service Administrator to limit the number of simultaneous logins of an MCX User to multiple MCX UEs on a per MCX User basis.
+
+[R-5.10-002] The MCX Service shall ensure that the MCX User logs into each MCX UE separately.
+
+## 5.11 Location
+
+[R-5.11-001] The MCX Service shall support obtaining and conveying Location information describing the position of the MCX UE.
+
+[R-5.11-002] The MCX Service should support obtaining and conveying high accuracy Location information describing the position of the MCX UE.
+
+[R-5.11-002a] The MCX Service shall be able to provide a mechanism for obtaining high accuracy Location information by integrating position information from multiple external sources (e.g. magnetometers, orientation sensors, GNSS)
+
+[R-5.11-003] The MCX Service shall provide for the flexibility to convey future formats of Location information.
+
+[R-5.11-004] The MCX Service shall provide a means for MCX Service Administrators to manage the privacy of Location information for MCX Users within their authority.
+
+[R-5.11-005] An authorized MCX User shall be able to control the supplying of Location information by the MCX UE for MCX Service communications.
+
+[R-5.11-006] The conveyed Location information shall be the most recently obtained information about the position of the MCX UE at the time of the Location information conveyance.
+
+[R-5.11-007] The MCX Service shall be capable of configuring and re-configuring one or more Location information update triggers (i.e., identified conditions that, when satisfied, cause the MCX UE to report its current Location information).
+
+[R-5.11-008] The MCX Service shall be able to modify Location information update triggers of an MCX User while the MCX User is on the network.
+
+[R-5.11-009] The MCX Service shall provide a means for an MCX UE to send a Location information update whenever a trigger condition is satisfied (e.g., initial registration, distance travelled, elapsed time, cell change, tracking area change, PLMN change, MCX Service communication initiation).
+
+[R-5.11-010] The MCX Service shall provide a means for an MCX UE to send a Location information update whenever the MCX User initiates an MCX Service Emergency Alert.
+
+[R-5.11-011] The MCX Service shall provide a means for an MCX UE to send a Location information update whenever the MCX User initiates an MCX Service Emergency Group Communication.
+
+[R-5.11-012] The MCX Service shall provide a means for an MCX UE to send a Location information update if the MCX User is in an MCX Service Emergency State and a configured amount of time has passed since the previous location information update.
+
+[R-5.11-013] The MCX Service shall provide a means for an MCX UE to send a Location information update whenever a trigger condition is satisfied while the MCX User is in MCX Service Emergency State (e.g., initial registration, distance travelled, elapsed time, cell change, tracking area change, PLMN change, MCX Service communication initiation).
+
+NOTE 1: The Location information update triggers for an MCX User in an MCX Service Emergency State might be different than the Location information update triggers used when the MCX User is not in an MCX Service Emergency State.
+
+[R-5.11-014] The MCX Service shall provide a means for an MCX Service Administrator to define geographical areas to be used for Location information update triggers for MCX Users within their authority.
+
+[R-5.11-015] The MCX Service shall provide a means for an MCX UE in a predefined area to send a Location information update whenever a trigger condition configured in an MCX User's active MCX Service User Profile is satisfied (e.g., initial registration, distance travelled, elapsed time, cell change, tracking area change, PLMN change, MCX Service communication initiation).
+
+NOTE 2: The Location information update triggers for an MCX User in a predefined area might be different than the Location information update triggers used when the MCX User is not in a predefined area.
+
+## 5.12 Security
+
+[R-5.12-001] The MCX Service shall provide a means to support the confidentiality and integrity of all user traffic and signalling at the application layer.
+
+[R-5.12-002] The MCX Service shall support MCX User with globally unique identities, independent of the mobile subscriber identity (IMSI) assigned by a 3GPP network operator to UEs.
+
+[R-5.12-003] The MCX Service identities shall be part of the MCX Service application service domain.
+
+[R-5.12-004] The MCX Service identities shall form the basis of the MCX Service application layer security for the MCX Service.
+
+[R-5.12-005] The MCX Service shall provide the MCX User with a mechanism to perform a single authentication for access to all authorized features.
+
+[R-5.12-006] The MCX Service shall provide a means for an authorized MCX UE to access selected MCX Service features prior to MCX User authentication.
+
+[R-5.12-007] The MCX Service shall require authentication of the MCX User before service access to all authorized MCX Service features is granted.
+
+NOTE: The MCX Service features available are based on the authenticated user identity(s).
+
+[R-5.12-008] Subject to regulatory constraints, the MCX Service shall provide a means to support confidentiality, message integrity, and source authentication for some information exchanges (e.g., MCX Service User Profile management, kill commands) that have the potential to disrupt the operation of the target MCX UE.
+
+[R-5.12-009] The MCX Service shall provide a means to support end-to-end security for all media traffic transmitted between MCX UEs.
+
+[R-5.12-010] End-to-end security shall be supported both within and without network coverage and regardless of whether the traffic is transmitted directly or via the network infrastructure.
+
+[R-5.12-011] Subject to regulatory constraints, the MCX Service shall provide a cryptographic key management service(s).
+
+[R-5.12-012] The cryptographic key management service(s) shall support both pre-provisioning and over-the-air provisioning of cryptographic keys.
+
+[R-5.12-013] The cryptographic key management service(s) shall ensure that cryptographic keys are confidentiality protected, integrity protected and authenticated when delivered over-the-air.
+
+[R-5.12-014] The MCX Service shall provide end-to-end confidentiality and integrity protection to the MCX User Profile when transferred to and/or from and while stored on an MCX Server, an MCX UE or both.
+
+## 5.13 Media quality
+
+[R-5.13-001] The MCX Service shall have the flexibility to be used with different codecs (audio / video).
+
+## 5.14 Relay requirements
+
+[R-5.14-001] The MCX Service shall be able to use ProSe Relay capabilities defined in TS 22.278 [5] and TS 22.468 [6].
+
+[R-5.14-002] An MCX UE which is unable to gain service from a 3GPP network should attempt to make use of one or more suitable ProSe UE-to-Network Relay(s) in its proximity (see sub-clause 6.18).
+
+[R-5.14-003] In off-network situations ProSe UE-to-UE Relay functionality shall be supported (see sub-clause 7.15) between MCX UEs.
+
+[R-5.14-004] The MCX Service shall provide a means for an MCX UE in a robot to have a ProSe UE-to-Network Relay capability.
+
+## 5.15 Gateway requirements
+
+[R-5.15-001] The MCX Service system shall be accessible via gateway MCX UEs by MCX Users.
+
+[R-5.15-001a] The MCX Service system shall provide a mechanism to uniquely identify a gateway MCX UE.
+
+[R-5.15-002] Gateway MCX UEs shall ensure that the content of communications between the MCX Service System and an MCX User attached to the gateway MCX UEs is unaltered.
+
+[R-5.15-003] Gateway MCX UEs shall handle the communication traffic attributes, e.g. priority and QoS, of an MCX User attached to a gateway MCX UE independently of other MCX Users concurrently attached to the same gateway MCX UE.
+
+[R-5.15-004] Multiple Gateway MCX UEs shall be able to operate within the same area (e.g., site of an incident or accident, overlapping coverage, adjacent cells, etc.).
+
+[R-5.15-005] MCX Users shall be able to select gateway MCX UEs, in case multiple, accessible gateway MCX UEs are available.
+
+[R-5.15-006] An MCX User shall be able to access multiple gateway MCX UEs simultaneously from a single device while restricting a MCX Service to one gateway (e.g., MCPTT on gateway UE 1, MCData and MCVideo on gateway UE 2).
+
+## 5.16 Control and management by Mission Critical Organizations
+
+### 5.16.1 Overview
+
+Clause 5.16 contains general requirements for management of the MCX Service by Mission Critical Organizations sharing the same MCX Service system, and more specific requirements pertaining to management controls and operational visibility, and to management of security services.
+
+### 5.16.2 General requirements
+
+[R-5.16.2-001] The MCX Service shall be able to support multiple Mission Critical Organizations, each with their own MCX Users and MCX Service Groups, on the same MCX Service system.
+
+[R-5.16.2-002] The MCX Service shall provide a mechanism by which Mission Critical Organizations designate and manage (i.e., add, delete, change authorizations, etc.) MCX Service Administrators with authority to manage users, groups, other MCX Service Administrators, security controls, and other mission affecting parameters (e.g., authorizations and priorities) of the MCX Service.
+
+[R-5.16.2-003] The MCX Service shall protect the operational privacy of Mission Critical Organizations by providing effective separation between the administrative and security management (e.g., key) parameters of those organizations except as authorized by the Mission Critical Organizations involved.
+
+[R-5.16.2-004] The MCX Service shall protect the administrative and security management parameters of Mission Critical Organizations from viewing and manipulation by individuals (including those within and outside of the mission critical organization) not explicitly authorized by the Mission Critical Organization.
+
+[R-5.16.2-005] The MCX Service shall provide a mechanism by which Mission Critical Organizations may share subsets of their administrative and security parameters with other Mission Critical Organizations.
+
+NOTE: The purposes of these requirements protect the operational security of organizations while still allowing for interworking of MCX UE and Users under the control of the Mission Critical Organizations.
+
+### 5.16.3 Operational visibility for Mission Critical Organizations
+
+[R-5.16.3-001] The MCX Service shall provide a means by which an MCX Service Administrator associated with a Mission Critical Organization has visibility into the operational status of the service (e.g., during a natural disaster).
+
+### 5.16.4 Sharing of administrative configuration between Mission Critical Organizations
+
+Mission Critical Organizations can deploy their own 3GPP standardized mobile, local, countrywide or national broadband mission critical communications systems. In order to grant visiting MCX Service Users access to a Partner MCX Service System and its services, a mechanism is required, which allows the exchange of administrative configuration between connected MCX Service Systems.
+
+**NOTE:** Administrative configuration is used for adding MCX Service Users into a Partner MCX Service System's user and group databases, modifying security controls and other mission affecting parameters, and for enabling or disabling certain services for specific users. Relevant information can be exchanged, for example, prior to the visiting MCX Service Users arriving at a Partner MCX Service System or dynamically during events.
+
+[R-5.16.4-001] An MCX Service shall provide a mechanism to allow an authorised MCX User to request MCX User configuration changes in one or more Partner MCX Service Systems (e.g., priorities, authorizations).
+
+[R-5.16.4-002] An MCX Service shall provide a mechanism to allow an authorised MCX User to evaluate and respond to requests for configuration changes from Partner MCX Service Systems.
+
+[R-5.16.4-003] An MCX Service shall provide a mechanism to allow an authorised MCX User to configure automatic responses to categories of requests for configuration changes from Partner MCX Service Systems (e.g., particular users, or groups).
+
+[R-5.16.4-004] An MCX Service shall provide a mechanism to allow an authorised MCX User to request configuration information (e.g., users, groups, security level) from Partner MCX Service Systems.
+
+[R-5.16.4-005] An MCX Service shall provide a mechanism to allow an authorised MCX User to send configuration information to Partner MCX Service Systems.
+
+[R-5.16.4-006] An MCX Service shall provide a mechanism to allow an authorised MCX User to exchange operationally relevant information for specific MCX Users, e.g., MCX User capability information, with Partner MCX Service Systems.
+
+**NOTE:** Capability information could include, but not limited to, information such as chemical, biohazard, medical or equipment handling capabilities for a specific MCX User.
+
+[R-5.16.4-007] An MCX Service System shall provide a mechanism to allow secure exchange of administrative and security related information with interconnected MCX Service systems without compromising the integrity and security of either system.
+
+[R-5.16.4-008] An MCX Service System shall provide a mechanism to allow exchange of administrative and security related information with interconnected MCX Service systems without exposing the internal network topology of either system.
+
+## 5.17 General administrative – groups and users
+
+[R-5.17-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to create and define the membership of MCX Service Groups.
+
+[R-5.17-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize a user to request an MCX Service Group Communication to one or more MCX Service Groups.
+
+[R-5.17-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to determine MCX Users who have the role of a particular Participant type on an MCX Service Group.
+
+[R-5.17-004] The MCX Service shall provide mechanisms for an MCX Service Administrator to assign and amend the identifying information of an MCX Service Group (e.g., name, alias).
+
+[R-5.17-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to assign and amend the identifying information of MCX Service User Profiles (e.g., name, identifier, alias).
+
+[R-5.17-006] The MCX Service shall provide a mechanism to notify MCX Users when they become a member of an MCX Service Group or their membership of an MCX Service Group is removed. This notification shall include any provisions required by the MCX User to use the MCX Service Group if the MCX User has been added to the MCX Service Group or remove provisions if the MCX User has been removed from the MCX Service Group.
+
+[R-5.17-007] The MCX Service shall provide mechanisms for an MCX Service Administrator to create, amend, delete, and suspend MCX Service User Profiles.
+
+[R-5.17-008] The MCX Service shall enable an MCX Service Administrator to configure which MCX Service Group Members are authorized to select to transmit to an MCX Service Group.
+
+## 5.18 Open interfaces for MCX services
+
+### 5.18.1 Overview
+
+It is expected that data applications such as database access or event managers are or will be, enhanced thanks to the use of multimedia communications. As a consequence, there is a need for external applications to securely access and use MCX Services.
+
+### 5.18.2 Requirements
+
+[R-5.18.2-001] The MCX Service shall be securely accessible via an open interface by an external application.
+
+NOTE: Access includes one or more of the following: ability to obtain information on demand or via notification, ability to set parameters, ability to control aspects of the service, and the ability to transmit/receive media to/from the service (e.g. video).
+
+[R-5.18.2-002] The MCX Service shall restrict external access based on MCX Service permissions and authorizations.
+
+[R-5.18.2-003] The open interface for MCX Services shall support control and indication of communication priority.
+
+[R-5.18.2-004] The MCX Service shall be able to authenticate the MCX User connecting to the MCX Service through the open interface.
+
+## 5.19 Media forwarding
+
+### 5.19.1 Service description
+
+When receiving any kind of media, a user may need to forward it to another user or to another group, subject to relevant authorization. That is to say to communicate between groups the user has to be a member of both groups. Video, messages, files, and streaming may be forwarded.
+
+### 5.19.2 Requirements
+
+[R-5.19.2-001] An MCX Service shall provide a mechanism for an authorized MCX User to forward media received within an MCX Group to another MCX User or another MCX Group.
+
+[R-5.19.2-002] An MCX Service shall provide a mechanism for an authorized MCX User to forward media received from an MCX User to another MCX User or to an MCX Group.
+
+[R-5.19.2-003] The MCX Service shall provide a mechanism for a MCX UE (whose current user is authorized) to forward a received real time communication in an MCX Group communication to a Group Broadcast Group.
+
+## 5.20 Receipt notification
+
+### 5.20.1 Service description
+
+For an MCX Service such as MCVideo or MCData, a user may want to know when the MCX communication has been delivered and when it has been viewed.
+
+### 5.20.2 Requirements
+
+[R-5.20.2-001] The MCX Service shall provide a mechanism for the sender of a real time communication to receive a notification that the communication is being received and/or displayed.
+
+## 5.21 Additional services for MCX Service communications
+
+### 5.21.1 Remotely initiated MCX Service communication
+
+#### 5.21.1.1 Overview
+
+A Remotely initiated MCX Communication is a feature that allows an authorized user, typically a dispatcher, to cause a remote MCX UE to initiate a communication by itself, without its user explicitly initiating the communication by depressing the MCX switch. The purpose of this feature allows the dispatcher to listen to activities at the Location of the remote MCX UE to find out what is happening around that MCX UE. This feature is also known as "Remote Unit Monitoring" in P25 systems.
+
+#### 5.21.1.2 Requirements
+
+[R-5.21.1.2-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely initiate an MCX Service Private Communication or MCX Service Group Communication from another user's MCX UE.
+
+[R-5.21.1.2-002] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to request remote activation of an MCX Service Group Communication from another user's (e.g. officer in the field with wearable camera) MCX UE.
+
+[R-5.21.1.2-003] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. officer in the field with wearable camera) to accept or deny access to an MCX Service Group Communication from their MCX UE.
+
+[R-5.21.1.2-004] The MCX Service shall provide a mechanism for an MCX User to request an authorized MCX User (e.g., a dispatcher) to send an MCX Communication (e.g., video or data) to the MCX UE (downlink pull).
+
+NOTE: A video could be stored on the MCX UE or taken on line by the camera.
+
+### 5.21.2 Remotely terminated MCX Service communication
+
+#### 5.21.2.1 Requirements
+
+[R-5.21.2.1-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely terminate an MCX Service Private Communication or MCX Service Group Communication from another user's MCX UE.
+
+# 6 MCX Service requirements specific to on-network use
+
+## 6.1 General administrative – groups and users
+
+[R-6.1-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to limit the total number (Nc6) of MCX Service Group Members of an MCX Service Group.
+
+[R-6.1-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to remove MCX Service Groups from the MCX Service system.
+
+[R-6.1-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to disable and re-enable MCX Service Groups.
+
+[R-6.1-004] The MCX Service shall provide a mechanism to log MCX Service Administrators' activities (e.g., cryptographic key updates, MCX Service User Profile changes, password changes, invalid access attempts).
+
+[R-6.1-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to define geographic areas that can be associated to dispatchers for the purpose of routing Location dependent communications and alerts, as part of handling MCX Service Private Communication requests and MCX Service Group Communications, when the receiving/alerted party is based on the MCX User's current Location.
+
+## 6.2 MCX Service communications
+
+### 6.2.1 Notification and acknowledgement for MCX Service Group Communications
+
+[R-6.2.1-001] The MCX Service shall be capable of allowing an MCX Service Group Communication to proceed without prior acknowledgement by any MCX User of that MCX Service Group.
+
+[R-6.2.1-002] The MCX Service shall provide a notification and acknowledgement function for an MCX User currently affiliated to an MCX Service Group to acknowledge receipt of an MCX Service Group Communication, if configured to do so.
+
+[R-6.2.1-003] The MCX User's acknowledgement may require direct interaction of the MCX UE with the human user, or may be automatically executed by the MCX UE, in accordance with policy established by an MCX Service Administrator.
+
+[R-6.2.1-004] If the MCX Service has knowledge that some affiliated members of a group cannot be Participants in an MCX Service Group Communication, the MCX Service shall provide an indication to the requester that the communication is proceeding without all affiliated members, and shall provide the list of the missing members based on policy established by the MCX Service Administrator.
+
+[R-6.2.1-005] If MCX User(s) are excluded from an MCX Service communication as there is insufficient capacity to support their participation the MCX Service shall notify the MCX User(s) that they have been excluded from the communication for reasons of lack of capacity.
+
+### 6.2.2 Queuing
+
+[R-6.2.2-001] The MCX Service shall prioritize the transmit request queue based on the type of communication (e.g., group, private), urgency of the communication (e.g., general group, MCX Service Emergency, Imminent Peril), attributes (e.g., priority level) of the MCX Service Group (if a group communication), and attributes (e.g., priority level) of the requesting MCX User.
+
+[R-6.2.2-002] When prioritizing the transmit queue, the MCX Service may assign higher priority to communications of the MCX Service Groups and MCX Users operating within the boundaries of their jurisdictions, if known.
+
+[R-6.2.2-003] When prioritizing the transmit queue, the MCX Service may assign higher priority to communications of the MCX Service Groups and MCX Users during hours of operation or while on duty, if known.
+
+[R-6.2.2-004] The MCX Service shall allow MCX Users with queued requests for permission to transmit to cancel their requests.
+
+[R-6.2.2-005] If an MCX Service Group Communication request to transmit has been queued, the MCX Service shall provide, upon request, that MCX User's current position in the queue.
+
+[R-6.2.2-006] If a request for an MCX Service Group Communication is queued, the MCX Service shall provide an indication to the requester when the communication continues.
+
+## 6.3 General requirements
+
+[R-6.3-001] A PLMN shall support multiple MCX Service systems.
+
+[R-6.3-002] An MCX Service system shall be capable of providing MCX Services to MCX Users in multiple PLMNs.
+
+[R-6.3-003] The MCX Service shall provide a means by which changes performed by an MCX Service Administrator take effect immediately.
+
+[R-6.3-004] The MCX Service shall provide a means by which changes performed by an MCX Service Administrator take effect at a specified date/time.
+
+## 6.4 General MCX Service Group Communications
+
+### 6.4.1 General aspects
+
+[R-6.4.1-001] Interruption to an MCX Service Group Communication shall be minimized when participants move from one area to another.
+
+### 6.4.2 Group status/information
+
+[R-6.4.2-001] The MCX Service shall provide a mechanism by which an authorized MCX User determines which MCX Service Groups have at least one other MCX User affiliated.
+
+[R-6.4.2-002] The MCX Service shall provide a mechanism by which an authorized MCX UE determines what MCX Service Groups have at least one active receiving member.
+
+[R-6.4.2-003] The MCX Service shall provide a mechanism by which an authorized MCX UE determines that a number (Nc1) of receiving members are present for an MCX Service Group.
+
+[R-6.4.2-004] The MCX Service shall provide a mechanism by which an authorized MCX UE determines that a particular receiving member(s) is present for an MCX Service Group.
+
+[R-6.4.2-005] The MCX Service shall provide a notification, for example audio and/or visual, to a user that there are no members on an MCX Service Group being used/monitored by the user and that the user is the only user affiliated to that MCX Service Group.
+
+[R-6.4.2-006] The MCX Service shall provide a mechanism by which an authorized MCX User can determine which MCX Service Group(s) another MCX User has affiliated to.
+
+[R-6.4.2-007] The MCX Service shall provide a mechanism by which an authorized MCX User can determine which MCX Service Group(s) another MCX User has selected.
+
+### 6.4.3 Identification
+
+[R-6.4.3-001] The MCX Service shall provide the MCX Service User ID, associated MCX Service User ID alias(es), MCX Service Group ID, group aliases and, if available, the identity of the Mission Critical Organization name of the transmitting Participant to the receiving MCX UEs unless the transmitting Participant's identity is restricted.
+
+[R-6.4.3-002] The MCX Service shall present users with human readable identifiers (with a minimum length of Nc3) for MCX Users (i.e., MCX Service User ID alias(es)) and for the MCX Service Groups (i.e., group alias(es)).
+
+### 6.4.4 Membership/affiliation
+
+[R-6.4.4-001] The MCX Service shall support automatic affiliation of the MCX UE to a Group-Broadcast Group or User-Broadcast Group within that MCX Service.
+
+[R-6.4.4-002] The MCX Service shall support an MCX User's ability to revoke their affiliation with an MCX Service Group.
+
+[R-6.4.4-002a] The MCX Service shall enable an MCX User to revoke their affiliation with a specific MCX Service Group on specific MCX UEs.
+
+[R-6.4.4-003] The MCX Service shall be able to prevent the MCX User having registered a specific Functional Alias from revoking their affiliation with a specific MCX Service Group.
+
+[R-6.4.4-004] The MCX Service shall be able to prevent the MCX User to revoke their affiliation with a specific MCX Service Group if the MCX User is the only MCX User in the MCX Service Group registered a specific Functional Alias.
+
+### 6.4.5 Membership/affiliation list
+
+[R-6.4.5-001] The MCX Service shall provide, upon request, the list of currently affiliated members on an MCX Service Group to an authorized user regardless of the user's affiliation.
+
+[R-6.4.5-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to request the list of currently affiliated members on an MCX Service Group regardless of the MCX User's affiliation or group membership.
+
+[R-6.4.5-003] The MCX Service shall provide, upon request, the list of currently affiliated members of an MCX Service Group to an authorized MCX UE.
+
+[R-6.4.5-003a] The MCX Service shall provide a mechanism to enable an authorized MCX User to automatically receive any changes made to the list of currently affiliated members for an MCX Service Group.
+
+[R-6.4.5-004] When a list of affiliated members is provided, the list shall reference each member by MCX Service User ID and/or associated aliases.
+
+[R-6.4.5-005] The MCX Service shall provide, upon request, the current list of members of an MCX Service Group to an authorized user.
+
+[R-6.4.5-006] The MCX Service shall provide, upon request, the current list of members of an MCX Service Group to an authorized MCX UE regardless of the MCX UE's membership.
+
+[R-6.4.5-007] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to request the complete list of members of an MCX Service Group, regardless of the MCX User's membership.
+
+[R-6.4.5-008] When a list of members is provided, the list shall reference each member by MCX Service User ID and/or associated aliases.
+
+### 6.4.6 Authorized user remotely changes another MCX User's affiliated and/or Selected MCX Service Group(s)
+
+#### 6.4.6.1 Mandatory change
+
+[R-6.4.6.1-001] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to change an on-network MCX User's Selected MCX Service Group(s) and then the MCX Service shall send a notification to the on-network MCX User.
+
+[R-6.4.6.1-002] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to make changes to the group(s) that an on-network MCX User is affiliated to and then the MCX Service shall send a notification to the on-network MCX User.
+
+[R-6.4.6.1-003] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to change multiple other on-network MCX Users' Affiliated MCX Service Group(s) to a specific MCX Service Group, and the MCX Service shall notify this to the on-network MCX Users.
+
+[R-6.4.6.1-004] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to change multiple other on-network MCX Users' Selected MCX Service Group(s) to a specific MCX Service Group, and the MCX Service shall notify this to the on-network MCX Users.
+
+#### 6.4.6.2 Negotiated change
+
+[R-6.4.6.2-001] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that another on-network MCX User should affiliate to a specific MCX Service Group.
+
+[R-6.4.6.2-002] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that multiple other on-network MCX Users should affiliate to a specific MCX Service Group.
+
+[R-6.4.6.2-003] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that another on-network MCX User should select a specific MCX Service Group.
+
+[R-6.4.6.2-004] The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that multiple on-network MCX Users should select a specific MCX Service Group.
+
+[R-6.4.6.2-005] The MCX Service shall provide a mechanism to the on-network MCX User to accept or reject a proposed change in selected or affiliated MCX Service Group(s).
+
+[R-6.4.6.2-006] The MCX Service shall provide a notification to the authorized MCX User (e.g., dispatcher) if the change that they proposed to another on-network MCX User(s) affiliated/Selected MCX Service Group was accepted/rejected by the MCX User(s).
+
+### 6.4.7 Prioritization
+
+[R-6.4.7-001] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different MCX Service Group Communications with respect to transport.
+
+[R-6.4.7-002] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different MCX Service Group Communications with respect to presentation.
+
+[R-6.4.7-003] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of MCX Service Groups Communications and other traffic with respect to transport.
+
+[R-6.4.7-004] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of MCX Service Groups Communications and other traffic with respect to presentation.
+
+### 6.4.8 Relay requirements
+
+[R-6.4.8-001] The MCX UE-to-Network Relay service shall provide on-network MCX Service to MCX UEs not currently connected to the serving network.
+
+### 6.4.9 Administrative
+
+[R-6.4.9-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the conditions under which MCX Service communications shall be terminated (e.g., last Participant leaving, second last Participant leaving, initiator leaving).
+
+NOTE: A Participant can leave an ongoing MCX Service Group communication e.g. because the Participant is de-affiliating from the MCX Service Group.
+
+[R-6.4.9-002] The MCX Service shall provide a mechanism for MCX Service Administrators to configure the maximum allowed time duration for MCX Service Group communications to remain active.
+
+[R-6.4.9-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to determine how many MCX Users shall remain participating for MCX Service Group Communications to remain active.
+
+[R-6.4.9-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure MCX Service Groups to be receive-only for specified MCX Service Group Members.
+
+[R-6.4.9-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to set the preferred codecs for an MCX Service Group.
+
+[R-6.4.9-006] The MCX Service shall provide a mechanism for an MCX Service Administrator to confine use of an MCX Service Group to MCX Service Group Members in a particular geographic area.
+
+## 6.5 Broadcast Group
+
+### 6.5.1 General Broadcast Group Communication
+
+[R-6.5.1-001] The MCX Service shall deliver an on-Network Broadcast Group Communication within that MCX Service to the members of a Broadcast Group who are on-Network, and who may be all of the MCX Service system users, or a subset thereof.
+
+[R-6.5.1-002] The MCX Service shall support Broadcast Group Communications within that MCX Service to a dynamically defined geographic area.
+
+### 6.5.2 Group-Broadcast Group (e.g., announcement group)
+
+[R-6.5.2-001] The MCX Service shall optionally support termination of all, or a subset of, subordinate group communications within that MCX Service upon initiation of a Broadcast Group Communication transmitted on a Group-Broadcast Group.
+
+### 6.5.3 User-Broadcast Group (e.g., System Communication)
+
+[R-6.5.3-001] The MCX Service shall optionally support termination of all group communications within that MCX Service that are not MCX Service Emergency Group Communications involving those users within the user hierarchy upon initiation of a Broadcast Group Communication transmitted on a User-Broadcast Group.
+
+## 6.6 Dynamic group management (i.e., dynamic regrouping)
+
+### 6.6.1 General dynamic regrouping
+
+[R-6.6.1-001] Group Regroup and User Regroup operations shall be manageable by authorized MCX Users.
+
+[R-6.6.1-002] The temporary group formed by Group Regroup or User Regroup operations shall persist until torn down by an authorized MCX User.
+
+[R-6.6.1-003] The priority of the temporary group formed by a Group Regroup or User Regroup operations shall be established by the creator of the group within bounds established by MCX Service Administrators.
+
+[R-6.6.1-004] The MCX Service shall enable an MCX Service Administrator to grant and to revoke the authorization of an MCX User to be able to perform dynamic regrouping operations.
+
+[R-6.6.1-005] The MCX Service shall enable an MCX Service Administrator to configure whether a temporary group is encrypted.
+
+[R-6.6.1-006] The temporary group formed by Group Regroup or User Regroup operations shall be treated like any other MCX Service Group, except the ability for a temporary group formed by a Group Regroup operation to be included in another Group Regroup operation.
+
+### 6.6.2 Group regrouping
+
+#### 6.6.2.1 Service description
+
+Group regrouping enables dispatchers or any authorized user to temporarily combine MCX Service Groups. A dispatcher uses group regrouping for different reasons.
+
+Due to an incident in an area it can be necessary to temporarily enable MCX Users from different MCX Service Groups to communicate to each other to coordinate. After the incident the dispatcher cancels the group regrouping and the MCX Users continue with their original configured MCX Service Groups.
+
+During quiet periods control room managers can decide to combine MCX Service Groups and handle their operations and communications with one dispatcher. In the busier period the group regrouping is cancelled and the MCX Service Groups are handled by separate dispatchers.
+
+MCX Service Groups that are being combined in a Group Regroup operation may belong to the same or different MCX servers and may have different security and priority levels, different floor control methods, as well as different operational characteristics (e.g. different call start criteria, different call or session hang timers, different transmit time limits, different override settings, different floor control parameters such as queue depth, queuing policy and time-to-live in the queue). However, the newly created temporary MCX Service Group can have only a single security level, priority level, floor control method, and set of operational characteristics. The MCX Service will apply the proper setting of those parameters for the new MCX Service Group.
+
+#### 6.6.2.2 Requirements
+
+[R-6.6.2.2-001] The MCX Service shall provide a means of dynamically combining a multiplicity of groups into a new, temporary group (i.e., to perform a "Group Regroup operation").
+
+[R-6.6.2.2-002] The MCX Service shall notify MCX Users when and how any of their affiliated groups are affected by a Group Regroup operation including notification of modified security, priority, floor control, and other operational characteristics.
+
+[R-6.6.2.2-003] The MCX Service shall provide notification and information to an authorized MCX User if that user is attempting to Group Regroup MCX Service Groups of different security levels, priority levels, and/or floor control methods.
+
+[R-6.6.2.2-004] The MCX Service shall enable an authorized MCX User to set the security level of the Group created from a Group Regroup operation. Where an MCX User does not specify the security level the MCX Service shall default the security level to be set to the lowest security level of the constituent Groups.
+
+[R-6.6.2.2-005] The MCX Service shall notify Affiliated MCX Service Group Members of a constituent MCX Service Group when the security level of the MCX Service Group that they are using lowers as a result of a Group Regroup operation.
+
+[R-6.6.2.2-006] The MCX Service shall enable an authorized MCX User to set the priority level of the group formed from a Group Regroup operation. Where an MCX User does not specify the priority level the MCX Service shall default the priority level to be set to the highest priority level of the constituent Groups.
+
+[R-6.6.2.2-007] Broadcast Groups shall be able to be included in a Group Regroup operation.
+
+[R-6.6.2.2-008] The MCX Service shall enable an authorized MCX User or MCX Service Administrator to configure default settings and rules for the operational characteristics of temporary MCX Service Groups resulting from Group Regroup operations (e.g. call start criteria, hang time).
+
+[R-6.6.2.2-009] The MCX Service shall enable an authorized MCX User to specify the operational characteristics of temporary MCX Service Groups resulting from Group Regroup operations either explicitly, or via pre-defined implicit rules, or via pre-configured default values, or, in case all the constituent Groups have in common the same operational characteristics, to use the common settings.
+
+[R-6.6.2.2-010] The MCX Service shall enable an authorized MCX User to set the floor control method of the Group created from a Group Regroup operation when the Group Regroup includes one or more groups configured for audio cut-in operation. Where an MCX User does not specify the floor control method the MCX Service shall default to using normal floor control for the Group Regroup (i.e. do not use audio cut-in).
+
+[R-6.6.2.2-011] The MCX Service shall prevent an authorized MCX User from including a temporary group in a Group Regroup operation.
+
+[R-6.6.2.2-012] The MCX Service shall prevent an authorized MCX User from including a MCX Group that is already part of an existing Group Regroup in a different Group Regroup operation.
+
+[R-6.6.2.2-013] The MCX Service shall be configurable either to prevent or to allow all authorized MCX Users from including a MCX Group that is in emergency state in a Group Regroup operation.
+
+### 6.6.3 Temporary Broadcast Groups
+
+[R-6.6.3-001] The MCX Service shall enable an authorized MCX User to create a temporary Group-Broadcast Group from a multiplicity of MCX Service Groups within that MCX Service.
+
+[R-6.6.3-001a] The MCX Service shall enable an authorized MCX User to create a temporary User-Broadcast Group from a multiplicity of MCX Users within that MCX Service.
+
+[R-6.6.3-001b] The MCX Service shall enable an authorized MCX User to create a temporary Broadcast Group from a combination of a multiplicity of MCX Service Groups and a multiplicity of MCX Users within that MCX Service.
+
+[R-6.6.3-002] The MCX Service shall only allow the creator of the temporary Broadcast Group to transmit on it.
+
+### 6.6.4 User regrouping
+
+#### 6.6.4.1 Service description
+
+##### 6.6.4.1.1 User regrouping controlled by dispatcher or authorized user
+
+There is a need for a mechanism for combining MCX Users into a new MCX Service Group under control by a dispatcher or authorized user to support ad-hoc communication needs.
+
+In the operational MCX Service environment, most tasks are covered by standard procedures and communication structures, and MCX Users can easily access the MCX Service Groups to handle their tasks.
+
+Exceptionally it could happen that there is an urgent need for a dedicated set of individual MCX Users to communicate in an MCX Service Group, but that this is not foreseen in the communication structure. This could be due to extreme conditions or due to a cooperation that is outside normal procedures.
+
+User Regrouping enables dispatchers or authorized users to instantaneously provide a dedicated MCX Service Group to these MCX Users to enable the required communication. Depending on configuration the MCX Users could be automatically affiliated to this MCX Service Group. After the operation this MCX Service Group is removed by the dispatcher or authorized user.
+
+##### 6.6.4.1.2 Automatic user regrouping
+
+There is also a need to for an automatic mechanism that determines a set of individual MCX Users to become members of a MCX Service Group and to automatically become affiliated to that MCX Service Group.
+
+These individual MCX Users are selected automatically by the MCX Service based on certain parameters (e.g. location, geographic area, participant type, direction of movement, speed). If MCX Service Group members do not meet the parameters anymore they will automatically be de-affiliated from the MCX Service Group and removed from the MCX Service Group member list. The remaining MCX Service Group members and the MCX Service Group member(s) removed will be informed accordingly. Conversely, MCX Users that are starting to meet the parameters (e.g due to location changes) will automatically be added and affiliated to the MCX Service Group. The MCX Service Group members and the added MCX Service Group member(s) will be informed accordingly.
+
+#### 6.6.4.2 Requirements
+
+[R-6.6.4.2-001] The MCX Service shall provide a means for combining a multiplicity of MCX Users into a new, temporary group (i.e., to perform a "User Regroup operation").
+
+[R-6.6.4.2-002] The MCX Service shall provide a means for combining a multiplicity of MCX Users into a new, temporary group based on a parameter or a combination of parameters (e.g., particular geographic area, Participant type, initiation of urgent type communication such as MCX Emergency Alert or MCX Emergency Group Communication).
+
+[R-6.6.4.2-002a] The MCX Service shall provide a means for automatically combining a multiplicity of MCX Users into a temporary MCX Service Group based on certain criteria. For example, the criteria may include one or more parameters from the list below:
+
+- A specific element or combination of specific elements in the functional alias of a MCX User
+- Location (including speed and heading) of a MCX User
+- Location or particular geographic area specified by an MCX Service Administrator
+- MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
+
+[R-6.6.4.2-002b] The MCX Service shall be able to automatically update the memberslist of a temporary MCX Service Group based on certain criteria i.e. to remove MCX Users no more meeting the criteria and add MCX Users starting to meet the criteria. For example, the criteria may include one or more parameters from the list below:
+
+- A specific element or combination of specific elements in the functional alias of a MCX User
+- Location (including speed and heading) of a MCX User
+- Location or particular geographic area specified by an MCX Service Administrator
+- MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
+
+[R-6.6.4.2-003] The MCX Service shall provide a mechanism to preconfigure the parameters for a particular User Regroup operation, such that an authorized MCX User activates this preconfigured User Regroup and communicates with this temporary group with minimal delay.
+
+NOTE: An example of the use of this functionality is for an MCX User to communicate with particular other MCX Users within a predefined radius of the MCX User's Location. This functionality is likely to be for urgent type communications such as MCX Service Emergency Group Communications.
+
+[R-6.6.4.2-004] The MCX Service shall notify MCX Users when they are affected by a User Regroup operation.
+
+[R-6.6.4.2-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure whether an MCX Service system shall automatically affiliate the MCX Users included in the temporary group created by the User Regroup operation.
+
+### 6.6.5 Dynamic Group Participation
+
+#### 6.6.5.1 Service description
+
+Dynamic group participation enables control of group affiliation, de-affiliation, and selection on MCX Service Groups based on various combinations of criteria. For highly mobile MCX UEs, such as those used in railway communication, the group affiliation and selection needs to change, for example, when a train crosses a controlling area border.
+
+#### 6.6.5.2 Requirements
+
+[R-6.6.5.2-001] The MCX Service shall enable an MCX User to automatically affiliate to one or more MCX Service Groups based on one, or a combination of, criteria.
+
+[R-6.6.5.2-002] The MCX Service shall be able to automatically affiliate an MCX User to one or more MCX Service Groups based one, or a combination of, criteria.
+
+[R-6.6.5.2-003] The MCX Service shall enable an MCX User to automatically choose the Selected MCX Service Group based on one, or a combination of, criteria.
+
+[R-6.6.5.2-004] The MCX Service shall be able to automatically choose the Selected MCX Service Group of an MCX User based on one, or a combination of, criteria.
+
+[R-6.6.5.2-005] The MCX Service shall enable an MCX User to automatically de-affiliate from one or more currently affiliated groups based on a change to one, or a combination of, criteria.
+
+[R-6.6.5.2-006] The MCX Service shall be able to automatically de-affiliate an MCX User from one or more currently affiliated groups based on a change to one, or a combination of, criteria.
+
+[R-6.6.5.2-007] The MCX Service shall be able to prevent an MCX User de-affiliating from specific currently affiliated groups based on one, or a combination of, criteria.
+
+NOTE: Examples of criteria for the above requirements could include one or more parameters from the list below:
+
+- A specific element or combination of specific elements in the functional alias of a MCX User
+- Location (including speed and heading) of a MCX User
+- Location or particular geographic area specified by an MCX Service Administrator
+- MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
+
+[R-6.6.5.2-008] The MCX Service shall enable an MCX User to select on specific MCX UEs whether automatic affiliation and/or de-affiliation is allowed.
+
+## 6.7 Private Communication
+
+### 6.7.1 Overview
+
+Private Communications can use some form of Floor control or not.
+
+### 6.7.2 General requirements
+
+[R-6.7.2-001] The MCX Service should provide a mechanism for authorized MCX Users to query whether a particular MCX User is present on the network.
+
+[R-6.7.2-002] The MCX Service should provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to place a Private Communication (without Floor control).
+
+[R-6.7.2-003] The MCX Service should provide a mechanism for authorized MCX Users to query whether a particular MCX User is capable of participating in a Private Communication.
+
+[R-6.7.2-004] The MCX Service shall provide a mechanism by which an MCX User can make a Private Communication to the local dispatcher based on the MCX User's current Location.
+
+[R-6.7.2-005] The MCX Service shall provide a mechanism for the Private Communication to be set up with the MCX UE designated by the receiving MCX User to be used for Private Communications when the receiving MCX User has signed on to the MCX Service with multiple MCX UEs.
+
+### 6.7.3 Administrative
+
+[R-6.7.3-001] The MCX Service should provide a mechanism for an MCX Service Administrator to configure whether the presence on the network of a particular MCX User is available.
+
+[R-6.7.3-002] The MCX Service should provide a mechanism for an MCX Service Administrator to configure which MCX Users may determine whether a particular MCX User is present on the network.
+
+[R-6.7.3-003] The MCX Service should provide a mechanism for an MCX Service Administrator to configure whether the ability to participate in Private Communications of a particular MCX User is available.
+
+[R-6.7.3-004] The MCX Service should provide a mechanism for an MCX Service Administrator to configure which MCX Users may determine whether a particular MCX User is capable of participating in a Private Communication.
+
+[R-6.7.3-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to place a Manual Commencement Private Communication (without Floor control).
+
+[R-6.7.3-006] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to place an Automatic Commencement Private Communication (without Floor control).
+
+[R-6.7.3-007] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular authorized MCX User, a set of MCX Users under the same authority to which a Private Communication (without Floor control) can be made by this particular MCX User.
+
+[R-6.7.3-007a] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular authorized MCX User, a set of MCX Users under the same authority from which Private Communication (without Floor control) is allowed to this particular MCX User.
+
+[R-6.7.3-008] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum duration for Private Communication for MCX Users within their authority.
+
+NOTE: The maximum duration can be set to infinite.
+
+### 6.7.4 Prioritization
+
+[R-6.7.4-001] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and Group Communications with respect to transport.
+
+[R-6.7.4-002] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and Group Communications with respect to presentation.
+
+[R-6.7.4-003] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different Private Communications with respect to transport.
+
+[R-6.7.4-004] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different Private Communications with respect to presentation.
+
+[R-6.7.4-005] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and other traffic with respect to transport.
+
+[R-6.7.4-006] The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and other traffic with respect to presentation.
+
+[R-6.7.4-007] The MCX Service shall provide a mechanism to prioritize Private Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).
+
+### 6.7.5 Private Communication (without Floor control) commencement requirements
+
+[R-6.7.5-001] The MCX Service shall provide a means by which an MCX UE initiates a Private Communication (without Floor control) to any MCX User for which the MCX UE's current MCX User is authorized.
+
+[R-6.7.5-002] The MCX Service shall provide a means by which an MCX User initiates an Automatic Commencement Private Communication (without Floor control) to any MCX User for which the MCX User is authorized.
+
+[R-6.7.5-003] The MCX Service shall provide a means by which the transmitting authorized MCX User is notified the receiving MCX User received the Private Communication (without Floor control) request.
+
+### 6.7.6 Private Communication (without Floor control) termination
+
+[R-6.7.6-001] The MCX Service shall provide a mechanism for an MCX User to reject a Private Communication (without Floor control).
+
+[R-6.7.6-002] The MCX Service shall provide a means by which an MCX User ends a Private Communication (without Floor control) in which the MCX User is a Participant.
+
+## 6.8 MCX Service priority requirements
+
+### 6.8.1 General
+
+[R-6.8.1-001] The MCX Service shall support multiple MCX Service Application priorities, which are mapped to priority levels, based on network operator policy.
+
+[R-6.8.1-002] MCX Service shall support multiple pre-emptive priorities.
+
+[R-6.8.1-003] The MCX Service shall provide a mechanism for MCX Service Administrators to create, a pre-emption hierarchy for MCX Service Group transmissions and their associated users (i.e., to facilitate local management of the service and its resources).
+
+[R-6.8.1-004] The MCX Service shall support MCX Service Groups with the permission to pre-empt other MCX Service communications.
+
+[R-6.8.1-005] In case of resource shortage a communication made to a group with pre-emption permissions shall be given resources to complete this communication by pre-empting lower priority communications.
+
+NOTE: An MCX Service communication that needs the use of pre-emption still needs to satisfy the communication setup requirements.
+
+[R-6.8.1-006] MCX Service shall support queuing and retention by priority.
+
+[R-6.8.1-007] The MCX Service shall provide a mechanism for an MCX Service Administrator to establish the priority hierarchy and characteristics of MCX Service Group transmissions.
+
+[R-6.8.1-008] The MCX Service shall enable an MCX Service Administrator to prioritize MCX Service Groups in relation to other MCX Service Groups (with respect to transport and presentation).
+
+[R-6.8.1-009] The MCX Service shall enable an MCX Service Administrator to set the priority for a subset of a Mission Critical Organization's MCX Service Groups relative to other subsets of a Mission Critical Organization's MCX Service Groups subordinate to the MCX Service Administrator's authority.
+
+[R-6.8.1-010] When determining priority for an MCX Service communication, the MCX Service shall use the MCX User/Participant's attributes (e.g., first/second responder, supervisor, dispatcher, on/off duty) and the MCX Service Group's attributes (e.g., type of group, owning organization of the group, MCX Service Emergency, Imminent Peril).
+
+[R-6.8.1-011] When determining priority for an MCX Service transmission, the MCX Service shall use the MCX User/Participant's attributes (e.g., first/second responder, supervisor, dispatcher, on/off duty) and the MCX Service Group's attributes (e.g., type of group, owning agency of the group, MCX Service Emergency, Imminent Peril).
+
+[R-6.8.1-012] The MCX Service shall provide a means for the attributes used for determining the priority for MCX Users and Groups to influence the Priority and QoS for all MCX UEs associated with the MCX User.
+
+[R-6.8.1-013] Based on the attributes used for determining the priority for MCX Users and Groups, the MCX Service shall provide consistent and deterministic priority for all MCX Users within their Primary MCX Service System.
+
+[R-6.8.1-014] Based on the attributes used for determining the priority for MCX Users and Groups, subject to roaming capabilities and operator agreement, the MCX Service shall provide consistent and deterministic priority for all MCX Users that roam into Partner MCX Service Systems.
+
+[R-6.8.1-015] The MCX Service shall provide a means for an MCX User to monitor the attributes used for determining priority of his/her communications and transmissions.
+
+[R-6.8.1-016] The MCX Service shall provide a means for an authorized MCX User to monitor and affect a change of the attributes used for determining the priority of another MCX User's communications and transmissions.
+
+### 6.8.2 3GPP system access controls
+
+[R-6.8.2-001] The 3GPP system shall, subject to operator policy, provide a means for the MCX Service to influence the modification of the access parameters used by the network to admit MCX UEs within a defined area.
+
+NOTE: It is believed that the existing UE network access mechanisms could be utilized to meet the above requirement.
+
+### 6.8.3 3GPP system admission controls
+
+[R-6.8.3-001] The 3GPP system shall, subject to operator policy, provide a means for the MCX Service to influence the selection and/or modification of admission and retention controls for the bearers assigned or about to be assigned to an MCX UE based on the MCX User's and MCX Service Group attributes used for the priority determination.
+
+NOTE: It is believed that the existing 3GPP mechanisms for network priority and QoS could be utilized to meet the above requirement.
+
+### 6.8.4 3GPP system scheduling controls
+
+[R-6.8.4-001] The 3GPP system shall, subject to operator policy, provide a means for the MCX Service to influence the selection and/or modification of the bearer scheduling controls for the bearers assigned or about to be assigned to an MCX UE based on the MCX User's and MCX Service Group attributes used for the priority determination.
+
+NOTE: It is believed that the existing 3GPP mechanisms for network priority and QoS could be utilized to meet the above requirement.
+
+### 6.8.5 UE access controls
+
+[R-6.8.5-001] The MCX Service shall allow the MCX UE to temporarily modify selected 3GPP system access parameters, according to configuration established by an MCX Service Administrator in agreement with the operator's policy.
+
+NOTE: It is believed that the existing network access mechanisms, e.g., ACDC (see 3GPP TS 22.011 [7] and 3GPP TS 23.122 [8]), could be utilized to meet the above requirement.
+
+### 6.8.6 Mobility and load management
+
+#### 6.8.6.1 Mission Critical mobility management according to priority
+
+[R-6.8.6.1-001] A Mission Critical System shall minimize the interruption to an on-going MCX Service communication when the UE transitions its connection to that communication from one network to another, taking into account that priority management is done in the visited Mission Critical System.
+
+[R-6.8.6.1-002] Mobility shall be subject to authorization from home and visited networks consistent with operational priority management mechanisms. The authorization may be pre-negotiated or in an *ad hoc* manner.
+
+#### 6.8.6.2 Load management
+
+[R-6.8.6.2-001] MCX Users shall be able to use dedicated 3GPP networks as well as public 3GPP networks. When possible, private 3GPP networks are preferably used. But public 3GPP networks may be used e.g., when no private 3GPP network coverage is available or for lower priority data flows while under an overloaded private 3GPP network coverage.
+
+[R-6.8.6.2-002] MCX Services shall be able to propose, according to operational priorities and available resources, adjustments in quality of service and delay of communications.
+
+[R-6.8.6.2-003] MCX Services shall be able to propose to request to pre-empt other on-going communications (for communications that can be pre-empted).
+
+[R-6.8.6.2-004] MCX Services shall be able to notify users of actions taken by the dispatcher that result in a change in priority for a data flow.
+
+[R-6.8.6.2-005] MCX Services shall be able to notify users when the network is not able to provide the requested quality of service.
+
+### 6.8.7 Application layer priorities
+
+#### 6.8.7.1 Overview
+
+Dispatchers from different critical communication organizations access the same networks and network resources. Depending on the event, the priority is given to an organization and/or a group rather than to another. For instance, in case of a fire priority is given to the fire brigades dealing with it, while in case of a criminal arrest priority is given to the police officers in charge of the arrest.
+
+#### 6.8.7.2 Requirements
+
+[R-6.8.7.2-001] The MCX Service system shall be able to give application priorities to each communication according to the event in addition to the priority given according to groups.
+
+[R-6.8.7.2-002] The 3GPP system shall inform the MCX Service system if a new MCX Service communication cannot be set up.
+
+[R-6.8.7.2-003] The MCX Service system shall assign to each communication:
+
+- an application layer pre-emption capability;
+- a capability to be pre-empted; and
+- an application layer priority value.
+
+[R-6.8.7.2-004] If there are no MCX Service communications with the capability to be pre-empted, the MCX Service communications with the lowest application layer priorities may be terminated, even if the MCX Service communications are set as not pre-emptable.
+
+[R-6.8.7.2-005] There shall be at least 8 and preferably 30 configurable levels of priority.
+
+[R-6.8.7.2-006] The MCX Service shall enable the MCX User to request the priority level for each individual communication.
+
+[R-6.8.7.2-007] The MCX Service system shall provide a mechanism that enables the MCX User to request any priority level up to the authorised priority level.
+
+[R-6.8.7.2-008] The MCX Service system shall verify the priority level at communication setup against the maximum authorised priority level.
+
+[R-6.8.7.2-009] The MCX Service system shall assign the defined priority level to a communication if the MCX User has not requested a priority level at setup.
+
+[R-6.8.7.2-010] The MCX Service system shall assign the maximum authorised priority level to a communication if the MCX User has requested at setup a priority level higher than the maximum authorised priority level.
+
+### 6.8.8 Communication types based on priorities
+
+#### 6.8.8.1 MCX Service Emergency Group Communication requirements
+
+[R-6.8.8.1-001] The MCX Service shall be capable of requesting increased priority for all Participants of an MCX Service Emergency Group Communication.
+
+[R-6.8.8.1-002] The MCX Service may inform affiliated group members that an MCX Service Emergency Group Communication was requested but resources were not available for the communication to be granted.
+
+[R-6.8.8.1-003] The MCX Service shall provide a mechanism for an MCX Service Emergency Group Communication to transmit to a temporary MCX Service Group created by a preconfigured User Regroup operation.
+
+NOTE: This type of MCX Service Emergency Group Communication could be used by MCX Users who need to communicate urgently to specific other MCX Users within a predefined radius of their current Location.
+
+[R-6.8.8.1-004] The MCX Service shall ensure that if there is an MCX Emergency Group Communication on one of the MCX Groups that an MCX User is affiliated to, but that user is already in a Private Communication, that the MCX User is notified of the MCX Emergency Group Communication. In the case of MCPTT the Emergency Group Communication is immediately connected to the receiving user except when the existing Private Communication is with Floor control.
+
+#### 6.8.8.2 MCX Service Emergency Private Communication requirements
+
+[R-6.8.8.2-001] The MCX Service shall ensure that MCX Emergency Private Communication have the highest priority over all other Private Communications.
+
+[R-6.8.8.2-002] The MCX Service shall be capable of requesting increased priority for the Participants of an MCX Emergency Private Communication.
+
+[R-6.8.8.2-003] The MCX Service shall be capable of changing a Private Communication in progress to an MCX Emergency Private Communication.
+
+[R-6.8.8.2-004] MCX Emergency Private Communications, including their content and signalling, shall have pre-emptive priority over all other types of MCX Service communications, except System Communications, MCX Emergency Group Communications and other MCX Emergency Private Communications.
+
+#### 6.8.8.3 Imminent Peril Group Communication requirements
+
+[R-6.8.8.3-001] The MCX Service shall be capable of requesting increased priority for all Participants of an Imminent Peril group communication.
+
+[R-6.8.8.3-002] The MCX Service shall maintain knowledge of the Affiliated MCX Service Group Member(s) that initiated the Imminent Peril group communication.
+
+[R-6.8.8.3-003] The MCX Service shall maintain an In-progress Imminent Peril condition for a group from the time the initial Imminent Peril group communication was requested until the In-progress Imminent Peril condition is cancelled.
+
+**Editor's Note: Whether imminent peril and MCX Service Emergency Group Communications can be generalized is FFS.**
+
+#### 6.8.8.4 MCX Service Emergency Alert
+
+##### 6.8.8.4.1 Requirements
+
+[R-6.8.8.4.1-001] The MCX Service may allow MCX UEs that are unauthorized, not registered, or authenticated to activate the MCX Service Emergency Alert capability.
+
+[R-6.8.8.4.1-002] The MCX User shall be notified that the MCX Service Emergency Alert was received by the MCX Service.
+
+[R-6.8.8.4.1-003] The MCX Service shall be configurable on how the user is notified (e.g., visual, audio).
+
+[R-6.8.8.4.1-004] The MCX Service shall maintain knowledge of the MCX Service Emergency State of the MCX UE, until cancelled.
+
+[R-6.8.8.4.1-005] The MCX Service shall inform an MCX UE of active MCX Service Emergency Alerts after successful registration/authentication with the MCX Service.
+
+[R-6.8.8.4.1-006] The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to transmit to a temporary MCX Service Group created by a preconfigured User Regroup operation.
+
+NOTE: This type of MCX Service Emergency Alert could be used by MCX Users who need to communicate urgently to specific other MCX Users within a predefined radius of their current Location.
+
+##### 6.8.8.4.2 MCX Service Emergency Alert cancellation requirements
+
+[R-6.8.8.4.2-001] The MCX Service shall allow authorized users to cancel any MCX UE's MCX Service Emergency Alert from the system.
+
+[R-6.8.8.4.2-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize a user to cancel, from the system, an MCX Service Emergency Alert initiated by another MCX User.
+
+#### 6.8.8.5 Ad hoc Group Communication requirements
+
+[R-8.8.8.5-001] The In-progress Emergency condition for a MCX Service Ad hoc Group Communication shall be cancelled when the communication is terminated.
+
+## 6.9 IDs and aliases
+
+[R-6.9-001] The MCX Service shall provide a mechanism for permanent and temporary assignment of IDs and aliases.
+
+[R-6.9-002] The MCX Service shall provide a mechanism for the enforcement of uniqueness of IDs and aliases.
+
+[R-6.9-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure IDs and aliases.
+
+[R-6.9-004] The MCX Service shall provide the MCX Service User ID and /or associated aliases, the identity of the Selected MCX Service Group, and, if available, the identity of the Mission Critical Organization name of the transmitting MCX User to all MCX UEs that are receiving for display by each MCX UE.
+
+## 6.10 MCX Service User Profile management
+
+[R-6.10-001] The MCX Service shall be able to dynamically modify one or more pieces of information within the MCX Service User Profile (e.g., the list of MCX Service Groups for which the user has access credentials) while in use by the MCX User.
+
+[R-6.10-002] The MCX Service shall provide a means by which an MCX Service Administrator designates that new or updated MCX Service User Profiles are to be installed at the MCX UE for immediate use by the MCX User.
+
+[R-6.10-003] The MCX Service shall provide a means by which an MCX Service Administrator designates a particular time and date when new or updated MCX Service User Profiles are to be installed at the MCX UE for use by the MCX User.
+
+[R-6.10-004] The MCX Service User Profile shall be construed to be sensitive user information and shall be provided end-to-end confidentiality and integrity protection when transferred between the MCX Service and MCX UE.
+
+## 6.11 Support for multiple devices
+
+[R-6.11-001] The MCX Service shall provide a notification to the MCX User if the MCX User is already logged on to another MCX UE.
+
+[R-6.11-002] The MCX Service shall provide the mechanisms to allow an MCX User to log off remotely from other MCX UEs.
+
+[R-6.11-003] The MCX Service shall provide the mechanism to allow an authorized MCX User to remotely log off another MCX User from an MCX UE.
+
+## 6.12 Location
+
+[R-6.12-001] The MCX Service shall provide Location information of the transmitting MCX UE to receiving MCX UEs subject to privacy restrictions.
+
+[R-6.12-002] The MCX Service shall support conveyance of Location information provided by 3GPP location services.
+
+[R-6.12-003] The MCX Service shall provide a means for an authorized MCX User to restrict the dissemination of his Location information.
+
+[R-6.12-004] The MCX Service shall provide end-to-end confidentiality of Location information.
+
+[R-6.12-005] The MCX Service shall provide authentication of messages carrying Location information.
+
+[R-6.12-006] The MCX Service shall provide a means for an authorized MCX User to activate a one-time Location information report of an MCX User and periodic Location information update reports of an MCX User or a specific Functional Alias.
+
+[R-6.12-007] The MCX Service shall provide a means for an authorized MCX User to deactivate periodic Location information update report of an MCX User.
+
+## 6.13 Security
+
+### 6.13.1 Overview
+
+Security covers areas designed to protect the confidentiality, integrity, and availability of information that is processed, stored, and transmitted. The security requirements listed here cover the areas of cryptographic protocols, authentication, access control, regulatory issues and storage control.
+
+### 6.13.2 Cryptographic protocols
+
+[R-6.13.2-001] The MCX Service shall employ open cryptographic standards, subject to applicable local policy (e.g., Federal Information Processing Standards (FIPS) 140-2).
+
+[R-6.13.2-002] The MCX Service shall allow for update to new cryptographic operations and methods without making obsolete existing operations and methods, or requiring upgrade of all user equipment simultaneously.
+
+[R-6.13.2-003] The MCX Service shall allow for the coexistence of a multiplicity of cryptographic suites.
+
+NOTE 1: A "cryptographic suite" is a consistent collection of cryptographic operations (e.g., encryption and message authentication) spanning the totality of required cryptographic operations for MCX Service. That is, if MCX Service requires a stream cipher, a message authentication code, and a secure hash, then counter-mode AES-256, CMAC with AES-256 as an underlying cipher, and SHA-512 would constitute a cryptographic suite for MCX Service.
+
+NOTE 2: The definition and identification of cryptographic suites and algorithms need not all be within the scope of 3GPP.
+
+### 6.13.3 Authentication
+
+[R-6.13.3-001] The MCX Service shall provide a means by which an MCX UE can require authentication of the MCX Service.
+
+### 6.13.4 Access control
+
+[R-6.13.4-001] The MCX Service shall support suspending or disabling of access from an MCX UE or an MCX User to the MCX Service.
+
+[R-6.13.4-002] An MCX User who has a profile that has been deleted or suspended shall be prevented from using that MCX Service User Profile to access the MCX Service.
+
+[R-6.13.4-003] The MCX Service shall provide a mechanism to temporarily disable an MCX UE remotely by the MCX Service Administrator or an authorized MCX User.
+
+[R-6.13.4-004] The MCX Service shall only allow a user to affiliate to or select an enabled MCX Service Group (i.e., not disabled).
+
+[R-6.13.4-005] A temporarily disabled MCX UE, which has limited access capability per Mission Critical Organization policy, shall be able to be re-enabled by the MCX Service Administrator or an authorized MCX User.
+
+[R-6.13.4-006] The MCX Service shall provide a mechanism to re-enable a temporarily disabled MCX UE by the MCX Service Administrator or an authorized MCX User.
+
+[R-6.13.4-007] The MCX Service shall provide a mechanism to permanently disable an MCX UE by the MCX Service Administrator or an authorized MCX User.
+
+[R-6.13.4-008] The permanently disabled MCX UE shall remove all MCX Service User Profiles stored in the MCX UE.
+
+[R-6.13.4-009] The permanently disabled MCX UE shall have no access to MCX Services.
+
+[R-6.13.4-010] The security solution for the MCX Service shall minimize the impact of a compromised MCX UE on other MCX UEs.
+
+### 6.13.5 Regulatory issues
+
+[R-6.13.5-001] The MCX Service shall support lawful interception.
+
+### 6.13.6 Storage control
+
+[R-6.13.6-001] The MCX Service shall provide all relevant security for media storage (e.g., video or data) on the MCX UE (e.g., data encryption, access only to authorized MCX Group Members).
+
+## 6.14 Interactions for MCX Service Group Communications and MCX Service Private Communications
+
+[R-6.14-001] The MCX Service shall allow an MCX UE to be receiving and transmitting in one MCX Private Communication (without Floor control) while simultaneously receiving transmissions from other MCX Group communications within the same MCX service.
+
+[R-6.14-002] The MCX Service shall allow an MCX UE to be receiving and transmitting in one MCX Private Communication (without Floor control) while simultaneously receiving transmissions from other MCX Private Communications (with Floor control) within the same MCX service.
+
+## 6.15 Additional services for MCX Service communications
+
+### 6.15.1 Discreet listening capabilities
+
+[R-6.15.1-001a] The MCX Service shall provide discreet listening capabilities without noticeable impact on or knowledge of the target MCX User, or the members of the target MCX Service Group including Ad hoc groups, and all other unauthorized MCX Users.
+
+[R-6.15.1-001] The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Private Communication transmissions to and from a specific target MCX User that is within the authority of the authorized MCX User.
+
+[R-6.15.1-002] The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Group Communication transmissions to and from a specific target MCX User that is within the authority of the authorized MCX User.
+
+[R-6.15.1-002a] The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Ad hoc Group Communication transmissions to and from a specific target MCX User that is within the authority of the authorized MCX User.
+
+[R-6.15.1-003] Subject to regulatory constraints and operator security policies, the MCX Service shall allow to be configured not to provide transmissions from MCX Users who are communicating with the discreet listening target MCX User, and who are not themselves targets of discreet listening.
+
+[R-6.15.1-004] The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Group transmissions from a specific MCX Service Group that is within the authority of the authorized MCX User.
+
+NOTE: Permission to activate discreet listening can include multiple levels of authorization, but this is outside the scope of 3GPP.
+
+### 6.15.2 Ambient listening
+
+#### 6.15.2.1 Overview of ambient listening
+
+Ambient listening is a feature that allows an authorized MCX User, typically a dispatcher, to cause an MCX UE to initiate a communication which results in no indication on the MCX UE that it is transmitting. Ambient listening can be initiated by an authorized MCX User who wants to be "listened" to by another remote authorized MCX User or can be initiated by a remote authorized MCX User who wants to "listen" to another MCX User. The purpose of this feature allows a dispatcher to "listen" to activities at the Location of the remote MCX UE to find out what is happening around that MCX UE without providing an indication to the MCX User or people around the user (whom the MCX User does not want to make aware of this action) that this is happening. This type of communication is different from other types of communications, as for ambient listening information is only transmitted to one party in the communication (i.e., a dispatcher or an authorized MCX User that is acting in a similar role to a dispatcher).
+
+This is used for stolen MCX UEs, monitoring officers, officer safety and particular operations, where it is important that the MCX UE does not indicate what is happening.
+
+#### 6.15.2.2 Ambient listening requirements
+
+##### 6.15.2.2.1 General ambient listening requirements
+
+[R-6.15.2.2.1-001] The MCX UE that is being listened to shall be the only transmitting party in the Private Communication.
+
+[R-6.15.2.2.1-002] For an MCX UE that is being listened to there shall be no indication on the MCX UE that it is transmitting.
+
+[R-6.15.2.2.1-003] If someone attempts to turn off an MCX UE that is being listened to it shall appear to be turned off even while Ambient Listening continues to be active.
+
+##### 6.15.2.2.2 Remotely initiated ambient listening requirements
+
+[R-6.15.2.2.2-001] The MCX Service shall provide a mechanism to allow an MCX Service Administrator and/or an authorized user to set up Ambient Listening on a remote MCX UE within their authority.
+
+[R-6.15.2.2.2-002] The MCX Service shall ensure that Ambient Listening triggered remotely is terminated only by the remote authorized MCX User (e.g., a dispatcher).
+
+##### 6.15.2.2.3 Locally initiated ambient listening requirements
+
+[R-6.15.2.2.3-001] The MCX Service shall provide a mechanism to allow an authorized MCX User to use the MCX UE that the MCX User is currently using to initiate Ambient Listening to another authorized MCX User (e.g., a dispatcher).
+
+[R-6.15.2.2.3-002] The MCX Service shall ensure that Ambient Listening triggered locally can be terminated by the MCX User being listened to or by the remote MCX Service Administrator and/or authorized user, who was the listening Participant.
+
+### 6.15.3 Remotely initiated MCX Service Communication
+
+#### 6.15.3.1 Overview
+
+A Remotely initiated MCX Service Communication is a feature that allows an authorized user, typically a dispatcher, to cause a remote MCX UE to initiate a communication by itself, without its user explicitly initiating the communication manually. The purpose of this feature allows the dispatcher to "listen" to activities at the Location of the remote MCX UE to find out what is happening around that MCX UE. This feature is also known as "Remote Unit Monitoring" in P25 systems.
+
+There are two typical use cases for this feature.
+
+The first one is the case where a user could have been incapacitated. This could be both accidentally, say a traffic accident, or deliberately, for example a violent attack. In both cases it would be necessary to remotely initiate a communication from the MCX UE in order to allow another user or a group of users to "listen" to what is happening to prepare assistance. The communication that is set up is either a Private Communication or a Group Communication, and the communication could optionally be visible to the remote MCX UE's user.
+
+The second one is the case of a stolen MCX UE. Here it is just necessary to activate the MCX UE so that a dispatcher can "listen" to any background communication in order to make an analysis of the situation. In this situation, the initiation of the communication from the remote MCX UE, typically a Private Communication in that case, is not visible by that MCX UE's user.
+
+Other use cases, such as undercover operations, discreet surveillance of users or investigations, could exist depending on the missions of the critical communications users and on legislations.
+
+The behaviour of the remotely initiated Communication is not different from a normal communication initiated by the local MCX User. The same rules for resource allocation and interactions with other services apply, but the initiator of the feature can have the capability to request a pre-emptive or high priority for that Communication to ensure it is set up even in case of resource congestion or to limit disturbance by other services.
+
+#### 6.15.3.2 Requirements
+
+[R-6.15.3.2-001] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized MCX User to cause an MCX UE that is within their authority to initiate an MCX Private Communication to the MCX Service Administrator and/or authorized MCX User and then begin transmitting to the MCX Service Administrator or authorized MCX User.
+
+[R-6.15.3.2-002] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to provide a notification to the user of the MCX UE when a remote MCX Private Communication is initiated.
+
+[R-6.15.3.2-003] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to cause an MCX UE that is within their authority to initiate an MCX Service Group Communication and then to begin transmitting to the Affiliated MCX Service Group Members.
+
+[R-6.15.3.2-004] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to provide a notification to the user of the MCX UE when a remote MCX Service Group Communication is initiated.
+
+### 6.15.4 Recording and audit requirements
+
+[R-6.15.4-001] The MCX Service shall provide a mechanism for a Mission Critical Organization to log the metadata of the MCX Service Group Communications and MCX Service Private Communications under the organization's authority.
+
+[R-6.15.4-002] Metadata shall be logged for both the transmitting Participant and the receiving Participant(s).
+
+[R-6.15.4-003] The MCX Service shall provide a mechanism for a Mission Critical Organization to record the transmissions of the Group Communications and Private Communications under the organization's authority.
+
+[R-6.15.4-004] The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following metadata per communication: depending on service this may include; start time, date, MCX User ID,
+
+functional alias(es), MCX Group ID, Location information of the transmitting Participant, end time or duration, end reason, type of communication (e.g., MCX Service Emergency, regroup, private) and success/failure indication.
+
+[R-6.15.4-005] If an MCX Service Group Communication or MCX Service Private Communication uses end-to-end confidentiality, the MCX Service shall provide a mechanism for a Mission Critical Organization to maintain the end-to-end confidentiality when the MCX Service Group Communication or MCX Service Private Communication is logged.
+
+[R-6.15.4-006] The MCX Service shall provide a mechanism for a Mission Critical Organization to log the metadata of non-communication related user activities under the agency's authority.
+
+[R-6.15.4-007] The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following non-communication activity types: MCX Service Emergency Alert, MCX Service Emergency Alert cancellation, In-progress Emergency cancellation, registration state change, overridden event, user remote logout, changing another user's affiliations, affiliation change, change of Selected MCX Service Group, (de)activation of functional alias(es) and User and Group Regroup operations.
+
+[R-6.15.4-008] The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following metadata per non-communication activity: time, date, MCX Service User identity, activity type and pertinent information about the activity (e.g. MCX User/Group ID(s) included in the temporary group created by the User/Group Regroup operation). The following metadata should be logged if applicable to the activity type: MCX Service Group ID, Location information of the MCX User, affiliation list, target MCX Service User ID and success/failure indication.
+
+[R-6.15.4-009] The MCX Service shall provide a mechanism for a Mission Critical Organization to log metadata for all failed authorization attempts (e.g., invalid login password) by an MCX User.
+
+[R-6.15.4-010] The MCX Service shall provide a mechanism to collect metadata for network access events (e.g., pre-emption of the 3GPP system bearer services, loss of signal, failed registration attempts).
+
+[R-6.15.4-011] The MCX Service shall provide recording and audit functions for all types of MCX Service group communication (e.g., normal group, regroup group, Ad hoc group).
+
+### 6.15.5 MCX Service Ad hoc Group Communication
+
+#### 6.15.5.1 Overview
+
+Due to an incident in an area, or a special operation, it can be necessary to coordinate MCX Users using Group Communication where these users do not normally work together and do not share any groups in common. MCX Service Ad hoc Group Communication enables authorized users to combine a random set of MCX Users into a group communication. The main characteristics of this ad hoc group communication are:
+
+- a) The ad hoc group does not exist until it is spontaneously created during the communication.
+- b) The ad hoc group ceases to exist when the communication terminates.
+
+A single communication consists of one or more media transmissions until explicitly terminated by various means. MCX Users that are being combined in an ad hoc group communication may be served by the same or different MCX systems and may normally use MCX Service Groups with different security and priority levels, different floor control methods, and other different operational characteristics. The MCX Service Ad hoc Group Communication will use a common security level, priority level, floor control method, and set of operational characteristics for the participants during a communication. As with any group communication, the priority level can change dynamically.
+
+The ad hoc group is used for a single communication and it does not persist when the communication is terminated. Authorized users can recreate the ad hoc group for subsequent communications, or request creation of a permanent MCX Service Group from the participants in the ad hoc group communication.
+
+NOTE: When the MCX Service Ad hoc Communication is terminated the list of participants may be retained for ease of initiating another ad hoc communication with the same participants.
+
+#### 6.15.5.2 General aspects
+
+[R-6.15.5.2-001] The MCX Service shall provide a mechanism for an authorized MCX User to combine an ad hoc multiplicity of MCX Users into a MCX Service Ad hoc Group Communication.
+
+NOTE: Selection of the list of MCX Users can be manual, or automatic based on certain criteria (e.g., location). This is left for implementation.
+
+[R-6.15.5.2-001a] The MCX Service shall provide the reason for denial to an MCX user who was not authorised to initiate an MCX Service Ad hoc Group Communication.
+
+[R-6.15.5.2-001b] The participant of an MCX Ad hoc Group Communication who has activated several Functional Alias(es) shall receive only one communication based on the unique MCX Service ID.
+
+[R-6.15.5.2-001c] The MCX Service shall provide a mechanism for the participant of an Ad hoc Group Communication to determine the Functional Alias, through which this participant is addressed by the communication.
+
+[R-6.15.5.2-002] An MCX Service Ad hoc Group Communication is a type of MCX Service Group communication and shall support MCX Service Group Communication mechanisms for call processing (e.g., transmit request queuing, hang time, broadcast mode).
+
+[R-6.15.5.2-003] MCX Service Ad hoc Group Communications shall be terminated by an authorised user or using the same mechanisms as MCX Service Group communications (e.g., initiator release, server release, hang time expiration).
+
+[R-6.15.5.2-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure additional conditions under which MCX Service Ad hoc Group Communication shall be terminated (e.g., last Participant leaving, second last Participant leaving, initiator leaving).
+
+[R-6.15.5.2-005] When an MCX Service Ad hoc Group Communication is terminated the group shall not persist.
+
+[R-6.15.5.2-006] The MCX Service shall provide a mechanism for the initiator of a MCX Service Ad hoc Group Communication to indicate which MCX Users have to mandatorily acknowledge the setup request before the media transmission proceeds.
+
+[R-6.15.5.2-007] The MCX Service shall provide a mechanism for an authorized initiator of a MCX Service Ad hoc Group Communication to define the communication parameters for the Ad hoc Group Communication (e.g. priority, hang time, broadcast/non-broadcast)
+
+[R-6.15.5.2-008] MCX Service Ad hoc Group Communications shall be able to support the same urgency as MCX Service Group communication (e.g., general group, emergency, imminent peril).
+
+[R-6.15.5.2-009] MCX Service Ad hoc Group Communications shall support the applicable security requirements as identified in sub-clause 5.12.
+
+[R-6.15.5.2-010] The MCX Service shall provide a mechanism for the initiator of an MCX Service Ad hoc Group Communication to request that the list of participants is suppressed.
+
+[R-6.15.5.2-011] The MCX Service shall provide a mechanism for authorized MCX Users to create a permanent MCX Service Group from the members of the MCX Service Ad hoc Group communication.
+
+[R-6.15.5.2-012] The MCX Service shall provide a mechanism for the initiator and/or an authorised user to add or remove participants during an in progress MCX Service Ad hoc Group communication.
+
+[R-6.15.5.2-013] The MCX Service shall provide a mechanism for a participant to join an in progress MCX Service Ad hoc Group communication.
+
+[R-6.15.5.2-014] The MCX Service shall provide a mechanism for the initiator of an MCX Service Ad hoc Group Communication to request that the list of participants be determined and updated by the MCX Service system using pre-defined criteria.
+
+[R-6.15.5.2-014a] When the list of participants is determined or updated by the MCX Service system, the MCX Service shall provide a mechanism that monitors and ensures that the participants list is applied for an MCX Service Ad hoc Group communication, performing retries when needed.
+
+[R-6.15.5.2-015] The MCX Service shall provide a mechanism for a participant of an MCX Service Ad hoc Group Communication to provide his location information to an authorised participant of the same group.
+
+#### 6.15.5.3 Administrative
+
+[R-6.15.5.3-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to initiate a MCX Service Ad hoc Group Communication.
+
+[R-6.15.5.3-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum number of MCX Users who can participate in a MCX Service Ad hoc Group Communication.
+
+[R-6.15.5.3-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users are authorized to participate in a MCX Service Ad hoc Group Communication. [TS 22.280 R-6.7.2-003]
+
+[R-6.15.5.3-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to define the default parameters for MCX Service Ad hoc Group communication (e.g., priority, hang time, broadcast mode).
+
+[R-6.15.5.3-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure whether MCX Service Ad hoc Group Communication is allowed on the MCX system regardless of individual MCX User authorizations.
+
+#### 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications
+
+[R-6.15.5.4-001] The MCX Service shall provide mechanisms for notification and acknowledgement of MCX Service Ad hoc Group Communications as defined in section 6.2.1.
+
+NOTE: For MCX Service Ad hoc Group Communications a participant is considered an affiliated member of the group during communication setup.
+
+### 6.15.6 MCX Service Ad hoc Group Emergency Alert
+
+#### 6.15.6.1 Overview
+
+Due to an incident in an area, or a special operation, it can be necessary to coordinate MCX Users using Ad hoc Group Emergency Alert where these users do not normally work together and do not share any groups in common. MCX Service Ad hoc Group Emergency Alert enables authorized users to combine a random set of MCX Users based on criteria into a group and to send an emergency alert to this set of MCX Users.
+
+The main characteristics of the Ad hoc Group Emergency Alert are:
+
+- The ad hoc group does not exist until it is spontaneously created at the initiation of the Ad hoc Group Emergency Alert.
+- After initiation of the Ad hoc Group Emergency Alert the MCX User may be put into the MCX Service Emergency State.
+- After initiation of the Ad hoc Group Emergency Alert the resulting ad hoc group may be used for group communications.
+- The ad hoc group ceases to exist when the group communications in the ad hoc group have terminated, and the Ad hoc Group Emergency Alert has been cancelled.
+
+An authorised user is able to:
+
+- Initiate an MCX Service Ad hoc Group Emergency Alert with participants satisfying specific criteria,
+- Cancel an MCX Service Ad hoc Group Emergency Alert,
+
+During an ongoing MCX Service Ad hoc Group Emergency Alert, the set of MCX Users may change dynamically based on these criteria (e.g., criteria may not longer be met, or criteria may be met for additional MCX users, and as a result users are removed from or added to the ongoing Ad hoc Group Emergency Alert).
+
+#### 6.15.6.2 General aspects
+
+[R-6.15.6.2-001] The MCX Service shall support an MCX Service Ad hoc Group Emergency Alert capability, which on initiation by an MCX User causes that MCX UE to send an MCX Service Ad hoc Group Emergency Alert and may put that MCX User into the MCX Service Emergency State.
+
+[R-6.15.6.2-002] The MCX Service shall provide a means for an authorized user to be able to activate the MCX Service Ad hoc Group Emergency Alert capability.
+
+[R-6.15.6.2-002a] The MCX Service shall provide the reason for denial to an MCX user who was not authorised to activate the MCX Service Ad hoc Group Emergency Alert.
+
+[R-6.15.6.2-003] The MCX Service Emergency Alert shall contain the following information: Location information, MCX Service User ID, Functional Alias, Criteria for determining list of participants, available MCX Services, additional information related to the alert, and the user's Mission Critical Organization name.
+
+[R-6.15.6.2-004] The MCX Service shall provide a mechanism for the initiator of an MCX Service Ad hoc Group Emergency Alert to request that the list of participants is to be determined and updated by the MCX Service system using pre-defined criteria.
+
+[R-6.15.6.2-005] The MCX Service Ad hoc Group Emergency Alert shall be distributed to the list of participants determined by the MCX Service system.
+
+[R-6.15.6.2-005a] When the list of participants is determined and updated by the MCX Service system, the MCX Service shall provide notifications to the relevant participants and authorized users.
+
+[R-6.15.6.2-005b] When the list of participants is determined or updated by the MCX Service system, the MCX Service shall provide a mechanism that monitors and ensures that the participants list is applied for MCX Service Ad hoc Group Emergency Alert, performing retries when needed.
+
+[R-6.15.6.2-006] The MCX Service shall support MCX Service Ad hoc Group Emergency Alert cancellation by authorized MCX Users.
+
+[R-6.15.6.2-007] The MCX Service shall provide a mechanism for an authorised user which is participant of an active MCX Service Ad hoc Group Emergency Alert to set up group communications using the ad hoc group.
+
+[R-6.15.6.2-008] When an MCX Service Ad hoc Group Emergency Alert is cancelled and ongoing calls in the ad hoc group are terminated the ad hoc group shall not persist.
+
+#### 6.15.6.3 Administrative
+
+[R-6.15.6.3-001] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to initiate a MCX Service Ad hoc Group Emergency Alert.
+
+[R-6.15.6.3-002] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum number of MCX Users who can participate in a MCX Service Ad hoc Group Emergency Alert.
+
+[R-6.15.6.3-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users are authorized to participate in a MCX Service Ad hoc Group Emergency Alert.
+
+[R-6.15.6.3-004] The MCX Service shall provide a mechanism for an MCX Service Administrator to define the default parameters for the ad hoc group resulting from the MCX Service Ad hoc Group Emergency Alert (e.g., priority, hang time, broadcast mode).
+
+[R-6.15.6.3-005] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure whether MCX Service Ad hoc Group Emergency Alert is allowed on the MCX system regardless of individual MCX User authorizations.
+
+## 6.16 Interaction with telephony services
+
+[R-6.16-001] The MCX Service shall provide a mechanism to allow an MCX Service Administrator to configure whether an MCX User using an MCX UE is able to make and/or receive telephony calls, including public emergency calls.
+
+[R-6.16-002] The MCX Service shall provide a mechanism for an MCX User authorized to use telephony services to block incoming telephony calls.
+
+## 6.17 Interworking
+
+### 6.17.1 Non-3GPP access
+
+[R-6.17.1-001] Subject to security and operational constraints and limitations of the underlying access technology, the MCX Service shall provide a mechanism to allow IP-based non-3GPP access to the MCX Service system.
+
+NOTE: An example of non-3GPP access is a dispatcher connecting to the system via a console.
+
+### 6.17.2 Interworking between MCX Service systems
+
+[R-6.17.2-001] An MCX Service shall provide mechanisms to allow an MCX User to operate in a Partner MCX Service System, subject to authorization from both the Partner and the Primary MCX Service Systems of the MCX User.
+
+[R-6.17.2-002] The authentication of an MCX User with an MCX Service in a Partner MCX Service System shall be based on security parameters obtained from the Primary MCX Service System of the MCX User.
+
+NOTE 1: This is an application layer authentication and not 3GPP network authentication.
+
+[R-6.17.2-003] Any functionality needed from the visited PLMN network is subject to roaming capabilities and operator agreement.
+
+[R-6.17.2-004] An MCX Service shall provide mechanisms to allow an MCX User on the Primary MCX Service System to affiliate and communicate in an MCX Service Group from a Partner MCX Service System, subject to authorization from the Primary MCX Service System and the Partner MCX Service System where the MCX Service Group is defined.
+
+[R-6.17.2-005] An MCX Service shall provide mechanisms to allow a roaming MCX User to affiliate and communicate in an MCX Service Group from the Partner MCX Service System, subject to authorization from the Partner MCX Service System where the MCX Service Group is defined.
+
+[R-6.17.2-006] An MCX Service shall provide mechanisms to allow an MCX User that receives service from a Partner MCX Service System to affiliate and communicate in an MCX Service Group from another Partner MCX Service System, subject to authorization from the Partner MCX Service System where the MCX Service Group is defined.
+
+[R-6.17.2-007] End to end security of an MCX Service Group communication (including in Partner MCX Service Systems) shall be based on parameters obtained from the MCX Service system where the MCX Service Group is defined.
+
+[R-6.17.2-008] The MCX Service shall enable to establish an MCX Service Ad hoc Group Emergency Alert and MCX Ad hoc Group Communication with Participants of multiple MC Systems, which are interconnected.
+
+### 6.17.3 Interworking with non-MCX Service systems
+
+#### 6.17.3.1 GSM-R
+
+[R-6.17.3.1-001] The MCX Service system shall enable bilateral interworking for MCX User positioning information and location information provided for a GSM-R mobile station [9], [10].
+
+[R-6.17.3.1-002] The MCX Service system shall enable interworking with a GSM-R system that is compliant with the UIC GSM-R (EIRENE) standards [9] and EN 301 515 [10].
+
+NOTE: The impact on GSM-R needs to be minimised.
+
+[R-6.17.3.1-003] The MCX Service system shall enable interworking between functional alias and alternative addressing scheme used in GSM-R.
+
+[R-6.17.3.1-004] A GSM-R user shall be reachable using the corresponding functional alias activated by the MCX Service system.
+
+[R-6.17.3.1-005] The MCX Service shall allow an MCX User to be reachable by a functional alias on the MCX Service system or on the GSM-R system.
+
+#### 6.17.3.2 External systems
+
+[R-6.17.3.2-001] The MCX Service system shall support a mechanism for the MCX Service Administrator to also allow the usage of functional alias and/or MCX User Identity as addressing scheme for use by non-MCX services (e.g. Machine Type Communication).
+
+[R-6.17.3.2-002] The MCX Service system shall enable interworking with PLMN and PSTN telephony services.
+
+## 6.18 MCX Service coverage extension using ProSe UE-to-Network Relays
+
+[R-6.18-001] A ProSe-enabled UE authorized to act as a ProSe UE-to-Network Relay shall, if authorized, support the bi-directional relay of signalling (control plane) and data (user plane) between an MCX UE and the on-network MCX Service.
+
+[R-6.18-002] A ProSe UE-to-Network Relay authorized to act as an MCX Service relay shall advertise, at the ProSe interface, those MCX Services (Groups) which it is currently relaying.
+
+[R-6.18-003] An MCX UE which is unable to gain service from a 3GPP network shall search for ProSe UE-to-Network Relay(s) offering MCX Services for the affiliated MCX Service Groups of the MCX User.
+
+[R-6.18-004] A ProSe UE-to-Network Relay authorized to support MCX Service coverage extension relay between an MCX UE and the on-network MCX Service shall provide a mechanism for an off-network MCX UE to affiliate to one or more MCX Service Groups using the on-network MCX Service.
+
+[R-6.18-005] The ProSe UE-to-Network Relay that has enabled an MCX UE to affiliate to an MCX Service Group using the on-network MCX Service shall subsequently support the bi-directional relay of signalling (control plane) and data (user plane) between the MCX UE and the on-network MCX Service for that MCX Service Group.
+
+[R-6.18-006] A ProSe UE-to-Network Relay authorized to support the bi-directional relay of signalling (control plane) and data (user plane) between an MCX UE and the on-network MCX Service shall provide a mechanism for an off-network MCX UE to initiate and/or receive Private Communications using the on-network MCX Service.
+
+## 6.19 Additional MCX Service requirements
+
+### 6.19.1 Communication rejection and queuing
+
+Requests to transmit appear in MCX Services in many forms and under many circumstances. Normally, requests to transmit are accompanied by priority information that is used to arbitrate the decision to assign resources for the transmission amongst competing requests to transmit. Upon arrival, a request to transmit is immediately granted, rejected, or queued. If queued, a request to transmit is normally granted when conditions which caused the queue are removed, or it can be dropped automatically for a number of reasons, or it can be cancelled by an authorized user who is usually the initiator of the request to transmit. When a request to transmit is rejected, it can be re-requested either manually by user action or automatically.
+
+#### 6.19.1.1 Requirements
+
+[R-6.19.1.1-001] The MCX Service shall provide a mechanism to queue any MCX request to transmit.
+
+[R-6.19.1.1-002] The MCX Service shall provide a mechanism to reject MCX request to transmit with a cause indication.
+
+[R-6.19.1.1-003] The MCX Service shall notify the requesting MCX Participant and may notify one or more authorized users when a communication is queued, when a communication is rejected, when communications has started after being de-queued.
+
+[R-6.19.1.1-004] The MCX Service shall provide a mechanism for an MCX User to remove its MCX request to transmit from the MCX request queue.
+
+[R-6.19.1.1-005] The MCX Service shall provide a mechanism for an authorised user to remove another user's MCX request to transmit from the MCX request queue.
+
+[R-6.19.1.1-005a] The MCX Service shall provide a mechanism for an authorised user to clear the entire MCX request queue.
+
+[R-6.19.1.1-006] An MCX Service User shall be notified when his request to transmit is removed from the MCX request queue.
+
+[R-6.19.1.1-007] The MCX Service shall provide a mechanism for an MCX Administrator to configure service parameter(s) (e.g., timer) for automatic removal of an MCX request to transmit from any MCX request queue.
+
+# --- 7 MCX Service requirements specific to off-network use
+
+## 7.1 Off-network communications overview
+
+The MCX Service while operating in off-network mode comprises a set or collection of functions necessary to provide Mission Critical Services (e.g., MCPTT, MCVideo, MCData, etc.) using a ProSe direct (UE-to-UE) Communication path (ProSe direct communication path) for transport. The ProSe direct communication path does not traverse the network infrastructure.
+
+Users operating off the network are either out of network coverage (not served by a 3GPP network) (e.g., in a remote mountain area fighting a forest fire 20 miles from the nearest network) or have selected a ProSe direct communication path for MCX Service while in network coverage. MCX Users operating off the network need to be in ProSe direct communication range in order to communicate.
+
+NOTE 1: While the network is likely to be a primary, reliable transport of MCX Service communications, there are many situations where MCX Service communications are needed in areas where the network is not available, or coverage is not reliable.
+
+MCX Users outside of the coverage of the fixed network might be first responders in a rural area assisting in a response to a plane crash, fire fighters in a remote mountain area fighting a forest fire or police officers inside a residence responding to a domestic issue. Off-network MCX Service communications are expected to be immediately accessible to users in the absence of the network.
+
+MCX Users in network coverage might be working in a confined area, such as fire fighters fighting a structure fire where direct UE-to-UE communication is more desirable and reliable. Users can communicate directly with one another without having to overcome the resistance of a building and distance to the nearest base station to communicate with other members of their team inside the building that are nearby.
+
+To operate off the network, an MCX UE is capable of automatically switching to a ProSe direct communication path for use of MCX Services when detecting an off-network (out of coverage) condition. In addition, a mechanism is provided for an authorized user to select (manually switch to) a ProSe direct communication path for use of off-network MCX Service communications (e.g., while in network coverage).
+
+When operating off the network, the MCX Service is provided by the MCX Service Application on the UE as compared to operations on the network, where the MCX Service Application on the UE interacts with an MCX Service server and the network to provide the MCX Service.
+
+NOTE 2: For MCX UEs that have selected a ProSe Direct Communication path for use of MCX Services while in network coverage, signalling with the network and MCX Service might be available (e.g., radio resource allocation, MCX Service User Profile management updates and cryptographic key management updates), while the MCX User transmissions would be direct between the MCX UEs (e.g., not traversing the network).
+
+The Off-Network MCX Service builds upon ProSe enablers to establish, maintain and terminate the signalling and communication path(s) among the off-network users. To the extent feasible, it is expected that the end user's experience is similar regardless if the MCX Service is used with a 3GPP network or based on the use of a ProSe direct communication path.
+
+The Off-Network MCX Service is intended to support communication between a group of users (a group communication), where each user has the ability to gain access to transmit in an arbitrated manner. However, the MCX Service also supports Private Communications between pairs of users.
+
+When operating off the network the MCX Service allows users to request the permission to transmit (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control).
+
+The Off-Network MCX Service provides a means for a user with higher priority (e.g., MCX Service Emergency condition) to override (interrupt) the current sender. The Off-Network MCX Service also supports a mechanism to limit the time a user transmits (has access to the resources) thus permitting users of the same or lower priority a chance to gain access to the resources.
+
+The Off-Network MCX Service provides the means for a user to monitor activity on a number of separate communications and enables the user to switch focus to a chosen communication. An Off-Network MCX User might join an already established MCX Service Group Communication (Late communication entry). In addition the Off-Network MCX Service supports MCX Service User IDs, aliases and user Location determination features.
+
+For operation off the network (e.g., when out of network coverage), an MCX UE is (pre-)provisioned by an MCX Service Administrator and/or authorized user with the following in order to use MCX Services:
+
+- a) An MCX Service User Profile associated with each of the intended MCX Users of the MCX UE that might be used for off-network operation;
+ - 1) An alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) for each MCX User;
+ - 2) A number of off-network MCX Service Groups for use by the MCX User;
+ - 3) An alphanumeric identifier (i.e., alias) for the authorized off-network MCX Service Groups;
+ - 4) A Mission Critical Organization name if available, associated with each of the intended MCX Users or Administrator;
+ - 5) A number of off-network MCX Users for Private Communications for which the MCX User is authorized;
+- b) Authentication and end-to-end security keys.
+
+NOTE 3: MCX UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
+
+An MCX UE operating off the network is capable of transmitting the sender's Location information, MCX Service User ID, alias(es), off-network MCX Service Group ID, group alias and, if available, Mission Critical Organization name of the user who is transmitting (i.e., whose UE is transmitting) to all other users in a communication including MCX UEs operating off the network that are late entering a communication in progress.
+
+The Off-Network MCX Service uses the capabilities defined in ProSe TS 22.278 [5], including the ProSe Relay capabilities defined in ProSe TS 22.278 [5] and GCSE\_LTE TS 22.468 [6].
+
+NOTE 4: As indicated in TS 22.278 [5] use of a ProSe Direct Communication path outside of network coverage is only applicable for Public Safety ProSe enabled UEs. For non-Public Safety ProSe enabled UEs the selection of the most appropriate communication path (ProSe Communication path (direct or routed via local basestation) or 3GPP network path) is under network control and based on operator preferences.
+
+MCX Service requirements specific to off-network use are defined in clause 7. Common MCX Service requirements defined in clause 5 apply whether the MCX Service is in use on the network or off the network.
+
+## 7.2 General off-network MCX Service requirements
+
+[R-7.2-001] In order to operate off the network using the direct communication path, an MCX UE shall be a Public Safety ProSe-enabled UE.
+
+[R-7.2-002] The Off-Network MCX Service shall make use of the ProSe capabilities related to ProSe Communication using the direct communication path between Public Safety ProSe-enabled UEs as defined in TS 22.278 [5].
+
+[R-7.2-003] The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to pre-provision MCX UEs that may not be served by the network with the following in order to operate using off-network MCX Service:
+
+- a) An MCX Service User Profile associated with each of the intended MCX Users of the MCX UE that might be used for off-network operation:
+ - 1) alphanumeric identifier (i.e., Alias ID) for the authorized off-network MCX Service Groups;
+ - 2) a number of off-network MCX Service Groups for use by an MCX User;
+ - 3) a MCX Service User ID associated with each of the intended MCX Users;
+ - 4) an alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) for each MCX Service User ID.
+- b) authentication and end to end security keys.
+
+NOTE: MCX UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
+
+[R-7.2-004] An MCX UE operating off the network shall be capable of transmitting the MCX Service User ID, alias(es), off-network MCX Service Group and, if available, Mission Critical Organization name of the user who is talking (i.e., whose UE is transmitting) to all other users in the communication including MCX UEs operating off the network that enter the communication late.
+
+[R-7.2-005] An MCX UE operating off the network shall be capable of transmitting the sender's Location information (i.e., whose UE is transmitting) to all other users in the communication including MCX UEs operating off the network that enter the communication late.
+
+## 7.3 Admission control
+
+### 7.3.1 General aspects
+
+[R-7.3.1-001] The admission control functionality shall authorize a participant to start a communication.
+
+[R-7.3.1-002] The admission control function shall be common to all services. That is to say resources are shared by all MCX Services depending on priorities. When a new communication is started an MCX service shall take into account priorities of all MCX Services communications as well as the resources they take/need.
+
+[R-7.3.1-003] The off-network Floor control functionality in an MCX Service shall determine at a point in time which received transmission(s) from off-network Participant(s) shall be presented to the receiving off-network Participant(s).
+
+### 7.3.2 Communication initiation
+
+[R-7.3.2-001] An authorized participant shall be able to request to start a communication.
+
+[R-7.3.2-002] The admission control functionality shall determine if an MCX User is allowed to start a communication and transmit according to resource management.
+
+[R-7.3.2-003] Following an off network MCX Service request for permission to transmit on the Selected MCX Group, the Affiliated MCX Group Member that made and was granted the request shall be given an indication of being granted permission to transmit.
+
+[R-7.3.2-004] When an MCX User is not allowed to start a communication, the MCX Service shall notify the MCX User that his communication has been queued or rejected.
+
+[R-7.3.2-005] When an MCX User is not allowed to start a communication the request may be queued or rejected.
+
+## 7.4 Communication termination
+
+[R-7.4-001] The MCX Service when operating off the network shall provide a mechanism for an MCX Service Administrator to preconfigure separately the limit for the total length of time of an MCX Service Group Communication and an MCX Service Private Communication.
+
+[R-7.4-002] The MCX Service when operating off the network shall provide an indication to the Participants that the communication is within a configurable amount of time before the communication time limit is reached.
+
+[R-7.4-003] The MCX Service when operating off the network shall provide an indication to the Participants that the communication time limit has been reached.
+
+[R-7.4-004] The MCX Service when operating off the network shall release the communication when the communication time limit has been reached.
+
+## 7.5 Broadcast Group
+
+[R-7.5-001] The MCX Service when operating off the network shall support Broadcast Group Communications within that MCX Service.
+
+[R-7.5-002] The MCX Service shall deliver an off-Network Broadcast Group Communication to the members of a Broadcast Group within that MCX Service who are within communication range, and who may be all of the MCX Service system users, or a subset thereof.
+
+## 7.6 MCX Service priority requirements
+
+[R-7.6-001] The Off-Network MCX Service shall assign to each MCX Service Group or Private Communication:
+
+- an application layer pre-emption capability;
+- a capability to be pre-empted; and
+- an application layer priority value.
+
+[R-7.6-002] The Off-Network MCX Service shall support at least 8 configurable levels of priority.
+
+[R-7.6-003] The Off-Network MCX Service shall support multiple MCX Service Application priorities which are mapped to ProSe priority levels, based on network operator policy.
+
+[R-7.6-004] The Off-Network MCX Service shall enable an MCX Service Administrator to prioritize MCX Groups in relation to other MCX Groups (with respect to transport and presentation).
+
+[R-7.6-005] When determining priority for an MCX communication, the Off-Network MCX Service shall use the MCX User/Participant's attributes (e.g., first/second responder, supervisor, dispatcher, on/off duty) and the MCX Group's attributes (e.g., type of group, owning organization of the group, MCX Emergency, Imminent Peril).
+
+[R-7.6-006] The Off-Network MCX Service shall support multiple pre-emptive priorities.
+
+[R-7.6-007] The Off-Network MCX Service shall provide a mechanism for MCX Administrators to create, a pre-emption hierarchy for MCX Group communications and their associated users (i.e., to facilitate local management of the service and its resources).
+
+[R-7.6-008] The Off-Network MCX Service shall support MCX Groups with the permission to pre-empt other MCX communications.
+
+[R-7.6-009] In case of resource shortage an MCX communication made to a group with pre-emption permissions shall be given resources to complete this communication by pre-empting lower priority MCX communications.
+
+## 7.7 Communication types based on priorities
+
+### 7.7.1 MCX Service Emergency Group Communication requirements
+
+[R-7.7.1-001] The Off-Network MCX Service shall provide a mechanism for an authorized Participant of an off-network MCX Service Group Communication to change the status of the off-network MCX Service Group Communication in progress to an off-network MCX Service Emergency Group Communication.
+
+[R-7.7.1-002] An off-network MCX UE that has initiated the MCX Service Emergency Group Communication shall maintain knowledge of the in progress off-network MCX Service Emergency Group Communication until it is cancelled.
+
+[R-7.7.1-003] An off-network MCX UE initiating an off-network MCX Service Emergency Group Communication shall be capable of transmitting its MCX Service User ID and an indication that it is an off-network MCX Service Emergency Group Communication to all other users in the communication.
+
+### 7.7.2 MCX Service Emergency Group Communication cancellation requirements
+
+[R-7.7.2-001] An indication of the cancellation of an off-network MCX Service Emergency Communication and the identity of the cancelling user shall be transmitted to Affiliated MCX Service Group Members of the off-network MCX Service Emergency Group Communication.
+
+### 7.7.3 Imminent Peril Communication
+
+#### 7.7.3.1 Imminent Peril Group Communication requirements
+
+[R-7.7.3.1-001] The Off-Network MCX Service shall provide a mechanism for an Affiliated MCX Service Group Member to initiate (or join) an off-network MCX Service Group Communication and set (or change) the status of the communication to Imminent Peril.
+
+[R-7.7.3.1-002] If an MCX Service Group has previously been configured to be used for Imminent Peril communications by the MCX User, that MCX Service Group shall be used for the communication.
+
+[R-7.7.3.1-003] The MCX Service when operating in off-network mode shall provide a mechanism, for an authorized Participant of an in progress off-network MCX Service Group Communication, to change the status of the communication to an off-network MCX Service Imminent Peril group communication.
+
+[R-7.7.3.1-004] The off-network MCX UE that has initiated an MCX Service Imminent Peril group communication shall be responsible for maintaining the knowledge of the Imminent Peril status until it is cancelled.
+
+[R-7.7.3.1-005] The Off-Network MCX Service shall provide a mechanism to inform and keep updated other Participants of the MCX Service Group Communication regarding the Imminent Peril status of the communication and regarding the MCX Service User ID of the MCX User setting the status to Imminent Peril.
+
+#### 7.7.3.2 Imminent Peril Group Communication cancellation requirements
+
+[R-7.7.3.2-001] An indication of the cancellation of the Imminent Peril status of an off-network MCX Service Imminent Peril group communication and the MCX Service User ID of the cancelling user shall be transmitted to Affiliated MCX Service Group Members of an off-network MCX Service Imminent Peril group communication.
+
+[R-7.7.3.2-002] If the Imminent Peril status of an MCX Service Imminent Peril group communication is cancelled by an MCX User other than the user initiating the Imminent Peril status, then the Off-Network MCX Service shall provide a mechanism to clear the knowledge of the Imminent Peril status maintained at the UE of the initiating MCX User.
+
+## 7.8 Location
+
+[R-7.8-001] An MCX UE shall be capable of transmitting its Location, if known, to other MCX UEs when operating off the network, subject to privacy restrictions.
+
+[R-7.8-002] An MCX UE shall be capable of providing a mechanism for obtaining the distance between the MCX UE and other MCX UEs within communication range.
+
+[R-7.8-003] The Off-Network MCX Service shall provide a means for an authorized MCX User to activate a one-time Location information report of a particular target MCX User within communication range.
+
+## 7.9 Security
+
+[R-7.9-001] MCX UEs operating off the network shall be capable of protecting the confidentiality of Location and identity information conveyed to or from other MCX UEs.
+
+[R-7.9-002] MCX UEs operating off the network shall be capable of authenticating the sender of messages carrying Location and identity information.
+
+## 7.10 Off-network MCX Service operations
+
+[R-7.10-001] Off-Network MCX Services shall be able to operate in the complete absence of any fixed infrastructure.
+
+[R-7.10-002] Off-Network MCX Services shall only be available for authorized users.
+
+[R-7.10-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize users for Off-Network MCX Services.
+
+## 7.11 Off-network UE functionality
+
+[R-7.11-001] An MCX UE shall be capable of utilizing off-network MCX Service and on-network MCX Service at the same time.
+
+NOTE: Sub-clause 7A.2 in TS 22.278 specifies requirements for concurrent communications on and off the network within the same group, concurrent communications on and off the network with different groups, and concurrent communications on and off the network involving both groups and Private Communications. This concurrent communication is not defined as a ProSe relay.
+
+[R-7.11-002] When switching from on-network to off-network operation (either manually or automatically), an MCX UE should attempt to notify the MCX Service that it is leaving the network.
+
+[R-7.11-003] Prior to automatically going off the network an MCX UE should attempt to make use of suitable ProSe UE-to-Network Relay in its proximity.
+
+## 7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay
+
+### 7.12.1 UE-to-Network Relay for all data types
+
+[R-7.12.1-001] MCX Users shall be able to transmit and receive real time data (e.g., voice, streaming video/data) between an on-network MCX UE and an off-network MCX UE via a ProSe UE-to-Network relay using the MCX UE-to-Network Relay service.
+
+[R-7.12.1-002] The MCX Service shall provide a mechanism for an authorized MCX User to forward real-time data (e.g. voice, streaming video/data) from an MCX User to another MCX User across a ProSe UE-to-Network relay using the MCX UE-to-Network Relay service.
+
+[R-7.12.1-003] The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to forward real time data (e.g. voice, streaming video/data) from one MCX User to another MCX User.
+
+[R-7.12.1-004] The MCX Service shall provide a mechanism to select/re-select a UE-to-Network Relay node that has enough capability for the real time data (e.g. video) forwarding.
+
+## 7.12.2 UE-to-UE Relay streaming
+
+[R-7.12.2-001] MCX Users shall be able to transmit and receive streaming video or data between an off-network MCX UE and another off-network MCX UE via a ProSe UE-to-UE relay using the MCX UE-to-UE Relay service.
+
+[R-7.12.2-002] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from on-network operation to off-network operation via a ProSe UE-to-UE relay.
+
+[R-7.12.2-003] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from off-network operation via a ProSe UE-to-UE relay to on-network operation.
+
+## 7.12.3 Off-Network streaming
+
+[R-7.12.3-001] MCX Users shall be able to transmit and receive streaming video or data between an off-network MCX UE and another off-network MCX UE via ProSe communications.
+
+[R-7.12.3-002] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from a ProSe UE-to-UE relay to ProSe direct communications with another MCX UE.
+
+[R-7.12.3-003] The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from ProSe direct communications with another MCX UE to a ProSe UE-to-UE relay.
+
+## 7.13 Switching to off-network MCX Service
+
+[R-7.13-001] An MCX UE shall be capable of automatically switching to a ProSe direct communications path for use of MCX Service when detecting an off-network (out of coverage) condition.
+
+[R-7.13-002] A means shall be provided for an authorized MCX User to be able to manually switch between on-network operation and a ProSe direct communication path for use of Off-Network MCX Service while in network coverage.
+
+[R-7.13-003] Subject to operator policy and/or network authorization, a means shall be provided for an authorized MCX User using a Public Safety ProSe-enabled UE to be able to manually switch between the on-network operation and a ProSe direct communication path for use of Off-Network MCX Service while in network coverage or out of network coverage.
+
+[R-7.13-004] An MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection to that communication from on-network operation to off-network ProSe direct communication with another MCX UE.
+
+[R-7.13-005] An MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection to that communication from off-network ProSe direct communication with another MCX UE to on-network operation.
+
+## 7.14 Off-network recording and audit requirements
+
+[R-7.14-001] The Off-Network MCX Service shall provide a mechanism to collect metadata for MCX Service Group Communications and MCX Service Private Communications (e.g., initiating MCX Service User ID, MCX Service Group ID) and non-communication activities (e.g., changing group settings) from MCX UEs operating in off-network mode. Metadata shall be logged for both the transmitting Participant and the receiving Participant(s).
+
+[R-7.14-001a] The Off-Network MCX Service shall provide a mechanism for a Mission Critical Organization to record the media content of the transmitting Participant of Group Communications and Private Communications under the organization's authority from MCX UEs operating in off-network mode.
+
+NOTE: The handling of storage limitation of the UE is out of scope of 3GPP.
+
+[R-7.14-002] Upon return to on-network operation, the MCX Service shall provide a mechanism to retrieve communication and non-communication activity metadata from an MCX UE that has collected such metadata while operating in off-network mode.
+
+[R-7.14-002a] Upon return to on-network operation, the MCX Service shall provide a mechanism to retrieve the media content of the transmitting Participant of Group Communications and Private Communications from an MCX UE that has recorded such media content while operating in off-network mode.
+
+## 7.15 Off-network UE-to-UE Relay
+
+### 7.15.1 Private Communications
+
+[R-7.15.1-001] The Off-Network MCX Service shall provide a means by which the MCX User of a (source) UE can make a Private Communication to the MCX User of a (target) UE via a ProSe UE-to-UE Relay.
+
+[R-7.15.1-002] The Off-Network MCX Service shall provide a mechanism for a source MCX User to query whether a particular target MCX User is within ProSe direct communication range.
+
+[R-7.15.1-003] An MCX UE shall be able to:
+
+- discover whether the UE of the target MCX User is itself within direct communication range of the source UE; and if not;
+- instead discover whether the UE of the target MCX User is within communication range of a ProSe UE-to-UE Relay that is within direct communication range of the source UE.
+
+### 7.15.2 Group Communications
+
+[R-7.15.2-001] An MCX Service Administrator or authorized user shall be able to configure a ProSe-enabled UE, authorized to act as a ProSe UE-to-UE Relay, to relay any received MCX Service transmissions for one (or more) specified MCX Service Groups.
+
+[R-7.15.2-002] An MCX UE receiving both the original MCX Service Group transmission and a relayed transmission shall be able to associate the two transmissions, correctly order a mixture of packets (received directly and indirectly) and identify duplicate packets.
+
+## 7.16 Off-network Ad hoc Group Communication
+
+[R-7.16-001] The off-network MCX Service shall provide a mechanism to combine an ad hoc multiplicity of MCX Users within communication range into a group communication.
+
+---
+
+## 8 Inter-MCX Service interworking
+
+### 8.1 Inter-MCX Service interworking overview
+
+Clause 8 describes interworking of one MCX Service with another.
+
+The MCData Service as defined in TS 22.282 [3] includes description of multiple independent applications and data transfer capabilities, which may themselves be subject to interworking limitations as identified in clause 8. Therefore, requirements in clause 8 should be used as guidance for MCData interworking between individual applications within that one MCX Service.
+
+## 8.2 Concurrent operation of different MCX Services
+
+### 8.2.1 Overview
+
+In some cases, a User or UE will use multiple independent MCX Services. The intention in this case is that each service will operate totally independently of the other services and should not cause service, capability or capacity interaction problems. It is understood that different UE may have different abilities to cope with the demands of simultaneous services. The requirements in sub-clause 8.2.2 identify how to handle simultaneous services which are intended to be completely independent of each other but limits in total capacity to handle multiple services and multiple instances within a service is left for suppliers to characterise for their products.
+
+Where independent functionality between services is constrained due to transport capacity limitations, those requirements are indicated in the sub-clause on Priority between Services.
+
+When the constraint is due to the service itself (e.g. Audio embedded within a video and MCPTT speech both delivering audible signals) any potential conflict may be avoided by action in the network part of the service but these actions are not specified. In sub-clause 8.2.2 actions taken by a single UE in case of conflict not resolved in the network are specified.
+
+### 8.2.2 Requirements
+
+[R-8.2.2-001] Except where expressly stated each MCX Service shall operate independently of each other MCX Service.
+
+[R-8.2.2-002] Any floor control facility remains completely independent for each of simultaneous MCX Services except where expressly stated.
+
+[R-8.2.2-003] A user shall be able to transmit on one MCX Service and receive on another without service interaction limitations.
+
+[R-8.2.2-004] A user shall be able to transmit on different MCX Services at essentially the same time without service interaction limitations.
+
+[R-8.2.2-005] A user shall be able to receive on different MCX Services at essentially the same time without service interaction limitations except where services are competing for the same unsharable resource which may include the display, audio transducers, etc.
+
+[R-8.2.2-006] When operating multiple MCX Services on the same network, radio resources shall be able to be utilized in an efficient manner for all MCX Services up to certain thresholds defined for each MCX Service and/or the combination of MCX Services. The radio resource allocation for each MCX Service and the combination of MCX Services shall be flexible based on demand, or allocated in a predefined manner.
+
+[R-8.2.2-007] The network shall be able to assign radio resources so that resources assigned to each MCX Service, or the combination of all MCX Services stays below a threshold, subject to the agreement between the 3GPP network operator and the Mission Critical Organization(s) (e.g., 3GPP network can be operated by Mission Critical Organization(s), or 3GPP network is operated by commercial operator), for resources to be used for MCX Services without impacting other non-MCX Services.
+
+## 8.3 Use of unsharable resources within a UE
+
+[R-8.3-001] An MCX UE should be able to present audio from multiple sources (e.g. MCVideo, MCPTT) in a manner that is easily distinguished.
+
+[R-8.3-002] An MCX UE may enable the user (e.g. incident commander) to control the relative volumes and spatial rendering of concurrent audio sources (e.g. MCVideo, MCPTT) at the UE.
+
+[R-8.3-003] The MCX Service shall provide a mechanism for a MCX User to prioritize the use of contended resources (e.g. display, loudspeaker) in the UE (e.g. most recently selected MCX Service, MCPTT voice always has priority).
+
+[R-8.3-004] Communication marked as Emergency or Imminent Peril shall take priority use of contended resources in the UE over communication not marked as Emergency or Imminent Peril.
+
+[R-8.3-005] When a MCX Service is denied access to contended resource in the UE, an indication shall be given to the User to alert them of the situation.
+
+[R-8.3-006] When a MCX Service is denied access to contended resource in the UE, a facility shall be provided for the User to select their preferred MCX Service for access to contended resources for the duration of the limitation.
+
+## 8.4 Single group with multiple MCX Services
+
+### 8.4.1 Overview
+
+It is useful to be able to configure any single group to be able to handle multiple MCX Services. In sub-clause 8.4 requirements are on the service to provide a solution that looks as though the services are working in a coupled and coordinated manner. The exact means of achieving this is not implied here. So, where a User may affiliate to a single group for two services, this could be a single affiliation indicating two services but handled together or it could be that the UE sends two affiliations, one for each service, in response to the single command to affiliate. There may also be other possibilities. In essence, the solution should look and feel like a combined service.
+
+### 8.4.2 Requirements
+
+[R-8.4.2-001] Mission critical groups shall be able to use multiple MCX Services independently or in combination.
+
+[R-8.4.2-002] The MCX Service shall provide a mechanism by which an authorized MCX User can affiliate to a mission critical group using that MCX Service through a single logical group affiliation for any subset of MCX Services used by the group, or independently by MCX Service.
+
+[R-8.4.2-003] To support operation coordinated between mission critical services, an MCX Service used by a mission critical group shall be able to interact with another MCX Service used by the same group.
+
+[R-8.4.2-004] To support combined services where the operation is intended to be coordinated, each MCX Service shall be able to apply similar geographic restrictions in use for one MCX Service to also operate in the coordinated MCX Service(s).
+
+[R-8.4.2-005] The MCX Service shall provide a mechanism by which an authorized MCX User who is affiliated to multiple MCX Services in a single group can de-affiliate specific MCX UEs from each MCX Service independently.
+
+### 8.4.3 Compatibility of UE
+
+#### 8.4.3.1 Advertising service capabilities required
+
+[R-8.4.3.1-001] The MCX Service shall provide a mechanism by which an MCX User of a UE can only affiliate to a Common MCX Service Group(s) for MCX Services that the MCX User's UE is capable of supporting.
+
+[R-8.4.3.1-002] The MCX Service shall provide a mechanism to advertise the service capabilities required to participate in a group e.g. choice of codec so that an MCX User can check the UE's compatibility before attempting to affiliate.
+
+[R-8.4.3.1-003] The MCX Service shall provide a mechanism for a UE to advertise its capability and limitation information when its MCX User affiliates to a group.
+
+NOTE: For example when an MCX User affiliates to an MCVideo group, the MCX User's UE may indicate the codecs and coding rates supported so that the MCVideo service will ensure that the UE receives video that it can render.
+
+[R-8.4.3.1-004] If the MCX User affiliates to a group, but its UE does not provide capability and limitation information, then the MCX Service shall assume that any MCX Service relevant content can be handled by that UE.
+
+#### 8.4.3.2 Conversion between capabilities
+
+[R-8.4.3.2-001] Where an MCX Service does not advertise the service capabilities required to participate in a group it is assumed that service capability itself is sufficient to take part in the group. For example if a specific codec is being used
+
+and a joining UE may not support that codec then the service will provide transcoding for UEs that support the service but do not support the codec.
+
+#### 8.4.4 Individual permissions for service access
+
+[R-8.4.4-001] When a UE makes a combined request to affiliate to a Common MCX Service Group the MCX Service may respond by permitting access to the group for some but not all MCX Services if appropriate.
+
+#### 8.4.5 Common alias and user identities or mappable
+
+[R-8.4.5-001] To support combined services where the operation is intended to be coordinated, it shall be possible for one MCX Service to access and communicate using user identifying information in use for a coordinated MCX Service.
+
+#### 8.4.6 Single location message
+
+[R-8.4.6-001] The MCX Service shall provide configuration and capability so that when a UE is affiliated to a Common MCX Service Group and some or all of the MCX Services periodically require location messages to be sent then each location message sent may be configured to apply to all MCX Services or to only one specific MCX Service.
+
+[R-8.4.6-002] The MCX Service shall provide configuration and capability so that when a UE is affiliated to multiple groups and some or all of the groups periodically require location messages to be sent then each location message sent may be configured to apply to all affiliated groups or may be applied to only one specific group.
+
+[R-8.4.6-003] The MCX Service shall provide configuration and capability so that when a UE is affiliated to multiple Common MCX Service Groups and some or all of the Common MCX Service Groups periodically require location messages to be sent then each location message sent may be configured to apply to all Common MCX Service Groups or may be applied to only one specific Common MCX Service Group.
+
+### 8.5 Priority between services
+
+#### 8.5.1 Overview
+
+The 3GPP priority system using ARP and QCI is expected to be used for relative priority treatment among communications at the transport level. Further application of priority will be invoked in and by the MCX Service system according to service related requirements e. g User and situation
+
+#### 8.5.2 Requirements
+
+[R-8.5.2-001] For on network communications, priority management shall manage all data flows from the different mission critical services together when applying priority decisions.
+
+NOTE 1: No mission critical service is considered as always having priority over another.
+
+[R-8.5.2-002] For off network communications, priority management shall manage all data flows from the different mission critical services together when applying priority decisions.
+
+NOTE 2: No mission critical service is considered as always having priority over another.
+
+[R-8.5.2-003] The MCX Service systems shall provide a mechanism to dynamically prioritize one MCX Service over another.
+
+[R-8.5.2-004] The MCX Services, in coordination with each other, shall be able to give appropriate priorities to the different communications according to User, content type, device type, participant type and operational situation.
+
+[R-8.5.2-005] MCX Services shall notify users of actions taken by the dispatcher that result in a change in priority for a data flow.
+
+---
+
+## 9 Air ground air Communication
+
+### 9.1 Service Description
+
+Mission critical users use aircrafts and helicopters for operational purpose. Being able to communicate in real time with helicopters and aircraft is a basic need.
+
+Some traffic assumptions are provided in Annex D.
+
+### 9.2 Requirements
+
+[R-9.2-001] The MCX Service shall support Air ground air Communication up to 15.000 ft with a speed up to [450]km/h.
+
+---
+
+## 10 MCX Service in IOPS mode
+
+[R-10-001] An MCX Service shall be able to provide services when operating in a 3GPP network in IOPS mode.
+
+NOTE: Services may be reduced for example due to lack of back haul.
+
+## Annex A (normative): MCCoRe Requirements for MCPTT
+
+Table A.1 provides an exhaustive list of those requirements in 3GPP TS 22.280 that are applicable to MCPTT.
+
+**Table A.1**
+
+| | | | | | |
+|---------------------------------------------------------------------------------|-------------|-------------|-------------|-------------|-------------|
+| 5 MCX Service Requirements common for on the network and off the network | | | | | |
+| NA | | | | | |
+| 5.1 General Group Communications Requirements | | | | | |
+| NA | | | | | |
+| 5.1.1 General aspects | | | | | |
+| R-5.1.1-001 | R-5.1.1-002 | R-5.1.1-003 | R-5.1.1-004 | R-5.1.1-005 | |
+| 5.1.2 Group/status information | | | | | |
+| R-5.1.2-001 | R-5.1.2-002 | | | | |
+| 5.1.3 Group configuration | | | | | |
+| R-5.1.3-001 | R-5.1.3-002 | | | | |
+| 5.1.4 Identification | | | | | |
+| R-5.1.4-001 | | | | | |
+| 5.1.5 Membership/affiliation | | | | | |
+| R-5.1.5-001 | R-5.1.5-002 | R-5.1.5-003 | R-5.1.5-004 | R-5.1.5-005 | R-5.1.5-006 |
+| R-5.1.5-007 | R-5.1.5-008 | | | | |
+| 5.1.6 Group Communication administration | | | | | |
+| R-5.1.6-001 | | | | | |
+| 5.1.7 Prioritization | | | | | |
+| R-5.1.7-001 | R-5.1.7-002 | | | | |
+| 5.1.8 Charging requirements for MCX Service | | | | | |
+| R-5.1.8-001 | R-5.1.8-003 | R-5.1.8-004 | R-5.1.8-005 | R-5.1.8-006 | R-5.1.8-007 |
+| R-5.1.8-008 | R-5.1.8-009 | R-5.1.8-010 | R-5.1.8-011 | | |
+| 5.1.9 MCX Service Emergency Alert triggered by location | | | | | |
+| NA | | | | | |
+| 5.2 Broadcast Group | | | | | |
+| NA | | | | | |
+| 5.2.1 General Broadcast Group Communication | | | | | |
+| R-5.2.1-001 | R-5.2.1-002 | | | | |
+| 5.2.2 Group-Broadcast Group (e.g., announcement group) | | | | | |
+| R-5.2.2-001 | R-5.2.2-002 | R-5.2.2-003 | R-5.2.2-004 | | |
+| 5.2.3 User-Broadcast Group (e.g., System Communication) | | | | | |
+| R-5.2.3-001 | R-5.2.3-002 | | | | |
+| 5.3 Late communication entry | | | | | |
+| R-5.3-001 | R-5.3-002 | R-5.3-003 | R-5.3-004 | R-5.3-005 | |
+| 5.4 Receiving from multiple MCX Service communications | | | | | |
+| 5.4.1 Overview | | | | | |
+| NA | | | | | |
+| 5.4.2 Requirements | | | | | |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|------------------|------------------|
+| R-5.4.2-001 | R-5.4.2-002 | R-5.4.2-003 | R-5.4.2-004 | R-5.4.2-004A | R-5.4.2-004B |
+| R-5.4.2-005 | R-5.4.2-006 | R-5.4.2-007 | R-5.4.2-007a | R-5.4.2-008 | R-5.4.2-009 |
+| 5.5 Private Communication | | | | | |
+| NA | | | | | |
+| 5.5.1 Private Communication general requirements | | | | | |
+| NA | | | | | |
+| 5.5.2 Charging requirement for MCX Service | | | | | |
+| R-5.5.2-001 | | | | | |
+| 5.6 MCX Service priority requirements | | | | | |
+| NA | | | | | |
+| 5.6.1 Overview | | | | | |
+| NA | | | | | |
+| 5.6.2 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 5.6.2.1 MCX Service Emergency and Imminent Peril general requirements | | | | | |
+| NA | | | | | |
+| 5.6.2.1.1 Overview | | | | | |
+| NA | | | | | |
+| 5.6.2.1.2 Requirements | | | | | |
+| R-5.6.2.1.2-001 | R-5.6.2.1.2-002 | R-5.6.2.1.2-003 | R-5.6.2.1.2-004 | R-5.6.2.1.2-005 | |
+| 5.6.2.2 MCX Service Emergency Group Communication | | | | | |
+| NA | | | | | |
+| 5.6.2.2.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-5.6.2.2.1-001 | R-5.6.2.2.1-002 | R-5.6.2.2.1-003 | R-5.6.2.2.1-004 | R-5.6.2.2.1-005 | R-5.6.2.2.1-006 |
+| R-5.6.2.2.1-007 | R-5.6.2.2.1-008 | R-5.6.2.2.1-009 | R-5.6.2.2.1-010 | R-5.6.2.2.1-011 | R-5.6.2.2.1-012 |
+| R-5.6.2.2.1-013 | R-5.6.2.2.1-014 | | | | |
+| 5.6.2.2.2 MCX Service Emergency Group Communication cancellation requirements | | | | | |
+| R-5.6.2.2.2-001 | R-5.6.2.2.2-002 | R-5.6.2.2.2-003 | R-5.6.2.2.2-004 | R-5.6.2.2.2-005 | |
+| 5.6.2.3 MCX Service Imminent Peril Group | | | | | |
+| NA | | | | | |
+| 5.6.2.3.1 MCX Service Imminent Peril Group Communication requirements | | | | | |
+| R-5.6.2.3.1-001 | R-5.6.2.3.1-002 | R-5.6.2.3.1-003 | R-5.6.2.3.1-004 | R-5.6.2.3.1-005 | R-5.6.2.3.1-006 |
+| R-5.6.2.3.1-007 | R-5.6.2.3.1-008 | R-5.6.2.3.1-009 | | | |
+| 5.6.2.3.2 MCX Service Imminent Peril Group Communications cancellation requirements | | | | | |
+| R-5.6.2.3.2-001 | R-5.6.2.3.2-002 | R-5.6.2.3.2-003 | R-5.6.2.3.2-004 | | |
+| 5.6.2.4 MCX Service Emergency Alert | | | | | |
+| NA | | | | | |
+| 5.6.2.4.1 MCX Service Emergency Alert requirements | | | | | |
+| R-5.6.2.4.1-001 | R-5.6.2.4.1-002 | R-5.6.2.4.1-003 | R-5.6.2.4.1-004 | R-5.6.2.4.1-004a | R-5.6.2.4.1-004b |
+| R-5.6.2.4.1-005 | R-5.6.2.4.1-006 | R-5.6.2.4.1-007 | R-5.6.2.4.1-008 | R-5.6.2.4.1-009 | R-5.6.2.4.1-010 |
+| R-5.6.2.4.1-011 | R-5.6.2.4.1-012 | R-5.6.2.4.1-013 | | | |
+| 5.6.2.4.2 MCX Service Emergency Alert cancellation requirements | | | | | |
+| R-5.6.2.4.2-001 | R-5.6.2.4.2-002 | R-5.6.2.4.2-003 | R-5.6.2.4.2-004 | | |
+| 5.7 MCX Service User ID | | | | | |
+| R-5.7-001 | R-5.7-002 | R-5.7-003 | | | |
+
+| | | | | | |
+|-------------------------------------------------------------------------|--------------|--------------|--------------|--------------|-------------|
+| 5.8 MCX UE Management | | | | | |
+| R-5.8-001 | R-5.8-002 | | | | |
+| 5.9 MCX Service User Profile | | | | | |
+| R-5.9-001 | R-5.9-002 | | | | |
+| 5.9A Functional alias | | | | | |
+| R-5.9a-001 | R-5.9a-001a | R-5.9a-001b | R-5.9a-001c | R-5.9a-002 | R-5.9a-002a |
+| R-5.9a-003 | R-5.9a-004 | R-5.9a-005 | R-5.9a-006 | | |
+| R-5.9a-007 | R-5.9a-008 | R-5.9a-009 | R-5.9a-010 | R-5.9a-011 | R-5.9a-012 |
+| R-5.9a-013 | R-5.9a-014 | R-5.9a-015 | R-5.9a-016 | R-5.9a-017 | R-5.9a-018 |
+| R-5.9a-019 | R-5.9a-020 | R-5.9a-021 | R-5.9a-022 | R-5.9a-023 | [R-5.9a-024 |
+| R-5.9a-025 | R-5.9a-026 | R-5.9a-027 | R-5.9a-028 | R-5.9a-029 | R-5.9a-030 |
+| R-5.9a-031 | | | | | |
+| 5.10 Support for multiple devices | | | | | |
+| R-5.10-001 | R-5.10-001a | R-5.10-002 | | | |
+| 5.11 Location | | | | | |
+| R-5.11-001 | R-5.11-002 | R-5.11-002a | R-5.11-003 | R-5.11-004 | R-5.11-005 |
+| R-5.11-006 | R-5.11-007 | R-5.11-008 | R-5.11-009 | R-5.11-010 | R-5.11-011 |
+| R-5.11-013 | R-5.11-014 | R-5.11-015 | R-5.11-015 | | |
+| 5.12 Security | | | | | |
+| R-5.12-001 | R-5.12-002 | R-5.12-003 | R-5.12-004 | R-5.12-005 | R-5.12-006 |
+| R-5.12-007 | R-5.12-008 | R-5.12-009 | R-5.12-010 | R-5.12-011 | R-5.12-012 |
+| R-5.12-013 | R5.12-014 | | | | |
+| 5.13 Media quality | | | | | |
+| R-5.13-001 | | | | | |
+| 5.14 Relay requirements | | | | | |
+| R-5.14-001 | R-5.14-002 | R-5.14-003 | R-5.14-004 | | |
+| 5.15 Gateway requirements | | | | | |
+| R-5.15-001 | R-5.15-002 | R-5.15-003 | | | |
+| 5.16 Control and management by Mission Critical Organizations | | | | | |
+| NA | | | | | |
+| 5.16.1 Overview | | | | | |
+| NA | | | | | |
+| 5.16.2 General requirements | | | | | |
+| R-5.16.2-001 | R-5.16.2-002 | R-5.16.2-003 | R-5.16.2-004 | R-5.16.2-005 | |
+| 5.16.3 Operational visibility for Mission Critical Organizations | | | | | |
+| R-5.16.3-001 | | | | | |
+| 5.17 General administrative – groups and users | | | | | |
+| R-5.17-001 | R-5.17-002 | R-5.17-003 | R-5.17-004 | R-5.17-005 | R-5.17-006 |
+| R-5.17-007 | R-5.17-008 | | | | |
+| 5.18 Open interfaces for MCX services | | | | | |
+| NA | | | | | |
+| 5.18.1 Overview | | | | | |
+| NA | | | | | |
+| 5.18.2 Requirements | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------|-------------|
+| 5.19 Media forwarding | | | | | |
+| NA | | | | | |
+| 5.19.1 Service description | | | | | |
+| NA | | | | | |
+| 5.19.2 Requirements | | | | | |
+| NA | | | | | |
+| 5.20 Receipt notification | | | | | |
+| NA | | | | | |
+| 5.20.1 Service description | | | | | |
+| NA | | | | | |
+| 5.20.2 Requirements | | | | | |
+| NA | | | | | |
+| 5.21 Additional services for MCX Service communications | | | | | |
+| NA | | | | | |
+| 5.21.1 Remotely initiated MCX Service communication | | | | | |
+| NA | | | | | |
+| 5.21.1.1 Overview | | | | | |
+| NA | | | | | |
+| 5.21.1.2 Requirements | | | | | |
+| NA | | | | | |
+| 5.21.2 Remotely terminated MCX Service communication | | | | | |
+| NA | | | | | |
+| 5.21.2.1 Requirements | | | | | |
+| R-5.21.2.1-001 | | | | | |
+| 6 MCX Service requirements specific to on-network use | | | | | |
+| NA | | | | | |
+| 6.1 General administrative – groups and users | | | | | |
+| R-6.1-001 | R-6.1-002 | R-6.1-003 | R-6.1-004 | R-6.1-005 | |
+| 6.2 MCX Service communications | | | | | |
+| NA | | | | | |
+| 6.2.1 Notification and acknowledgement for MCX Service Group Communications | | | | | |
+| NA | | | | | |
+| 6.2.2 Queuing | | | | | |
+| R-6.2.2-001 | R-6.2.2-002 | R-6.2.2-003 | R-6.2.2-004 | R-6.2.2-005 | R-6.2.2-006 |
+| 6.3 General requirements | | | | | |
+| R-6.3-001 | R-6.3-002 | R-6.3-003 | R-6.3-004 | | |
+| 6.4 General group communication | | | | | |
+| NA | | | | | |
+| 6.4.1 General aspects | | | | | |
+| R-6.4.1-001 | | | | | |
+| 6.4.2 Group status/information | | | | | |
+| R-6.4.2-005 | R-6.4.2-001 | R-6.4.2-002 | R-6.4.2-003 | R-6.4.2-004 | R-6.4.2-006 |
+| R-6.4.2-007 | | | | | |
+| 6.4.3 Identification | | | | | |
+| R-6.4.3-001 | R-6.4.3-002 | | | | |
+| 6.4.4 Membership/affiliation | | | | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------------------|---------------|----------------|----------------|---------------|---------------|
+| R-6.4.4-001 | R-6.4.4-002 | R-6.4.4-002a | R-6.4.4-003 | R-6.4.4-004 | |
+| 6.4.5 Membership/affiliation list | | | | | |
+| R-6.4.5-001 | R-6.4.5-002 | R-6.4.5-003 | R-6.4.5-003a | R-6.4.5-004 | R-6.4.5-005 |
+| R-6.4.5-006 | R-6.4.5-007 | R-6.4.5-008 | | | |
+| 6.4.6 Authorized user remotely changes another MCX User's affiliated and/or Selected MCX Service Group(s) | | | | | |
+| NA | | | | | |
+| 6.4.6.1 Mandatory change | | | | | |
+| R-6.4.6.1-001 | R-6.4.6.1-002 | R-6.4.6.1-003 | R-6.4.6.1-004 | | |
+| 6.4.6.2 Negotiated change | | | | | |
+| R-6.4.6.2-001 | R-6.4.6.2-002 | R-6.4.6.2-003 | R-6.4.6.2-004 | R-6.4.6.2-005 | R-6.4.6.2-006 |
+| 6.4.7 Prioritization | | | | | |
+| R-6.4.7-001 | R-6.4.7-002 | R-6.4.7-003 | R-6.4.7-004 | | |
+| 6.4.8 Relay requirements | | | | | |
+| R-6.4.8-001 | | | | | |
+| 6.4.9 Administrative | | | | | |
+| R-6.4.9-001 | R-6.4.9-002 | R-6.4.9-003 | R-6.4.9-004 | R-6.4.9-005 | R-6.4.9-006 |
+| 6.5 Broadcast Group | | | | | |
+| NA | | | | | |
+| 6.5.1 General Broadcast Group Communication | | | | | |
+| R-6.5.1-001 | R-6.5.1-002 | | | | |
+| 6.5.2 Group-Broadcast Group (e.g., announcement group) | | | | | |
+| R-6.5.2-001 | | | | | |
+| 6.5.3 User-Broadcast Group (e.g., system communication) | | | | | |
+| R-6.5.3-001 | | | | | |
+| 6.6 Dynamic group management (i.e., dynamic reporting) | | | | | |
+| NA | | | | | |
+| 6.6.1 General dynamic regrouping | | | | | |
+| R-6.6.1-001 | R-6.6.1-002 | R-6.6.1-003 | R-6.6.1-004 | R-6.6.1-005 | R-6.6.1-006 |
+| 6.6.2 Group regrouping | | | | | |
+| NA | | | | | |
+| 6.6.2.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.2.2 Requirements | | | | | |
+| R-6.6.2.2-001 | R-6.6.2.2-002 | R-6.6.2.2-003 | R-6.6.2.2-004 | R-6.6.2.2-005 | R-6.6.2.2-006 |
+| R-6.6.2.2-007 | R-6.6.2.2-008 | R-6.6.2.2-009 | R-6.6.2.2-010 | R-6.6.2.2-011 | R-6.6.2.2-012 |
+| R-6.6.2.2-013 | | | | | |
+| 6.6.3 Temporary Broadcast Groups | | | | | |
+| R-6.6.3-001 | R-6.6.3-001a | R-6.6.3-001b | R-6.6.3-002 | | |
+| 6.6.4 User regrouping | | | | | |
+| NA | | | | | |
+| 6.6.4.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.4.2 Requirements | | | | | |
+| R-6.6.4.2-001 | R-6.6.4.2-002 | R-6.6.4.2-002a | R-6.6.4.2-002b | R-6.6.4.2-003 | R-6.6.4.2-004 |
+| R-6.6.4.2-005 | | | | | |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------|---------------|---------------|---------------|---------------|---------------|
+| 6.6.5 Dynamic Group Participation | | | | | |
+| NA | | | | | |
+| 6.6.5.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.5.2 Requirements | | | | | |
+| R-6.6.5.2-001 | R-6.6.5.2-002 | R-6.6.5.2-003 | R-6.6.5.2-004 | R-6.6.5.2-005 | R-6.6.5.2-006 |
+| R-6.6.5.2-007 | R-6.6.5.2-008 | | | | |
+| 6.7 Private Communication | | | | | |
+| NA | | | | | |
+| 6.7.1 Overview | | | | | |
+| NA | | | | | |
+| 6.7.2 General requirements | | | | | |
+| R-6.7.2-001 | R-6.7.2-002 | R-6.7.2-003 | R-6.7.2-004 | R-6.7.2-005 | |
+| 6.7.3 Administrative | | | | | |
+| R-6.7.3-001 | R-6.7.3-002 | R-6.7.3-003 | R-6.7.3-004 | R-6.7.3-005 | R-6.7.3-006 |
+| R-6.7.3-007 | R-6.7.3-007a | R-6.7.3-008 | | | |
+| 6.7.4 Prioritization | | | | | |
+| R-6.7.4-001 | R-6.7.4-002 | R-6.7.4-003 | R-6.7.4-004 | R-6.7.4-005 | R-6.7.4-006 |
+| R-6.7.4-007 | | | | | |
+| 6.7.5 Private Communication (without Floor control) commencement requirements | | | | | |
+| R-6.7.5-001 | R-6.7.5-002 | R-6.7.5-003 | | | |
+| 6.7.6 Private Communication (without Floor control) termination | | | | | |
+| R-6.7.6-001 | R-6.7.6-002 | | | | |
+| 6.8 MCX Service priority requirements | | | | | |
+| NA | | | | | |
+| 6.8.1 General | | | | | |
+| R-6.8.1-001 | R-6.8.1-002 | R-6.8.1-003 | R-6.8.1-004 | R-6.8.1-005 | R-6.8.1-006 |
+| R-6.8.1-007 | R-6.8.1-008 | R-6.8.1-009 | R-6.8.1-010 | R-6.8.1-011 | R-6.8.1-012 |
+| R-6.8.1-013 | R-6.8.1-014 | R-6.8.1-015 | R-6.8.1-016 | | |
+| 6.8.2 3GPP system access controls | | | | | |
+| R-6.8.2-001 | | | | | |
+| 6.8.3 3GPP system admission controls | | | | | |
+| R-6.8.3-001 | | | | | |
+| 6.8.4 3GPP system scheduling controls | | | | | |
+| R-6.8.4-001 | | | | | |
+| 6.8.5 UE access controls | | | | | |
+| R-6.8.5-001 | | | | | |
+| 6.8.6 Mobility and load management | | | | | |
+| NA | | | | | |
+| 6.8.6.1 Mission Critical mobility management according to priority | | | | | |
+| R-6.8.6.1-001 | R-6.8.6.1-002 | | | | |
+| 6.8.6.2 Load management | | | | | |
+| R-6.8.6.2-001 | R-6.8.6.2-002 | R-6.8.6.2-003 | R-6.8.6.2-004 | R-6.8.6.2-005 | |
+| 6.8.7 Application layer priorities | | | | | |
+| NA | | | | | |
+| 6.8.7.1 Overview | | | | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|
+| NA | | | | | |
+| 6.8.7.2 Requirements | | | | | |
+| R-6.8.7.2-001 | R-6.8.7.2-002 | R-6.8.7.2-003 | R-6.8.7.2-004 | R-6.8.7.2-005 | R-6.8.7.2-006 |
+| R-6.8.7.2-007 | R-6.8.7.2-008 | R-6.8.7.2-009 | R-6.8.7.2-010 | | |
+| 6.8.8 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 6.8.8.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-6.8.8.1-001 | R-6.8.8.1-002 | R-6.8.8.1-003 | R-6.8.8.1-004 | | |
+| 6.8.8.2 MCX Service Emergency Private Communication requirements | | | | | |
+| NA | | | | | |
+| 6.8.8.3 Imminent Peril Group Communication requirements | | | | | |
+| R-6.8.8.3-001 | R-6.8.8.3-002 | R-6.8.8.3-003 | | | |
+| 6.8.8.4 MCX Service Emergency Alert | | | | | |
+| NA | | | | | |
+| 6.8.8.4.1 Requirements | | | | | |
+| R-6.8.8.4.1-001 | R-6.8.8.4.1-002 | R-6.8.8.4.1-003 | R-6.8.8.4.1-004 | R-6.8.8.4.1-005 | R-6.8.8.4.1-006 |
+| 6.8.8.4.2 MCX Service Emergency Alert cancellation requirements | | | | | |
+| R-6.8.8.4.2-001 | R-6.8.8.4.2-002 | | | | |
+| 6.8.8.X Ad hoc Group Communication requirements | | | | | |
+| R-6.8.8.X-001 | | | | | |
+| 6.9 IDs and aliases | | | | | |
+| R-6.9-001 | R-6.9-002 | R-6.9-003 | R-6.9-004 | | |
+| 6.10 User Profile management | | | | | |
+| R-6.10-001 | R-6.10-002 | R-6.10-003 | R-6.10-004 | | |
+| 6.11 Support for multiple devices | | | | | |
+| R-6.11-001 | R-6.11-002 | R-6.11-003 | | | |
+| 6.12 Location | | | | | |
+| R-6.12-001 | R-6.12-002 | R-6.12-003 | R-6.12-004 | R-6.12-005 | R-6.12-006 |
+| R-6.12-007 | | | | | |
+| 6.13 Security | | | | | |
+| NA | | | | | |
+| 6.13.1 Overview | | | | | |
+| NA | | | | | |
+| 6.13.2 Cryptographic protocols | | | | | |
+| R-6.13.2-001 | R-6.13.2-002 | R-6.13.2-003 | | | |
+| 6.13.3 Authentication | | | | | |
+| R-6.13.3-001 | | | | | |
+| 6.13.4 Access control | | | | | |
+| R-6.13.4-001 | R-6.13.4-002 | R-6.13.4-003 | R-6.13.4-004 | R-6.13.4-005 | R-6.13.4-006 |
+| R-6.13.4-007 | R-6.13.4-008 | R-6.13.4-009 | R-6.13.4-010 | | |
+| 6.13.5 Regulatory issues | | | | | |
+| R-6.13.5-001 | | | | | |
+| 6.13.6 Storage control | | | | | |
+| NA | | | | | |
+| 6.14 Interactions for MCX Service Group Communications and MCX Service Private Communications | | | | | |
+| R-6.14-001 | R-6.14-002 | | | | |
+
+| | | | | | |
+|----------------------------------------------------------------------------------------------|------------------|------------------|-----------------|----------------|------------------|
+| 6.15 Additional services for MCX Service communications | | | | | |
+| NA | | | | | |
+| 6.15.1 Discreet listening capabilities | | | | | |
+| R-6.15.1-001a | R-6.15.1-001 | R-6.15.1-002 | R-6.15.1-002a | R-6.15.1-003 | R-6.15.1-004 |
+| 6.15.2 Ambient listening | | | | | |
+| NA | | | | | |
+| 6.15.2.1 Overview of ambient listening | | | | | |
+| NA | | | | | |
+| 6.15.2.2 Ambient listening requirements | | | | | |
+| NA | | | | | |
+| 6.15.2.2.1 General ambient listening requirements | | | | | |
+| R-6.15.2.2.1-001 | R-6.15.2.2.1-002 | R-6.15.2.2.1-003 | | | |
+| 6.15.2.2.2 Remotely initiated ambient listening requirements | | | | | |
+| R-6.15.2.2.2-001 | R-6.15.2.2.2-002 | | | | |
+| 6.15.2.2.3 Locally initiated ambient listening requirements | | | | | |
+| R-6.15.2.2.3-001 | R-6.15.2.2.3-002 | | | | |
+| 6.15.3 Remotely initiated MCX Service Communication | | | | | |
+| NA | | | | | |
+| 6.15.3.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.3.2 Requirements | | | | | |
+| R-6.15.3.2-001 | R-6.15.3.2-002 | R-6.15.3.2-003 | R-6.15.3.2-004 | | |
+| 6.15.4 Recording and audit requirements | | | | | |
+| R-6.15.4-001 | R-6.15.4-002 | R-6.15.4-003 | R-6.15.4-004 | R-6.15.4-005 | R-6.15.4-006 |
+| R-6.15.4-007 | R-6.15.4-008 | R-6.15.4-009 | R-6.15.4-010 | R-6.15.4-011 | |
+| 6.15.5 MCX Service Ad hoc Group Communication | | | | | |
+| NA | | | | | |
+| 6.15.5.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.5.2 General Aspects | | | | | |
+| R-6.15.5.2-001 | R-6.15.5.2-001a | R-6.15.5.2-001b | R-6.15.5.2-001c | R-6.15.5.2-002 | R-6.15.5.2-003 |
+| R-6.15.5.2-004 | R-6.15.5.2-005 | R-6.15.5.2-006 | R-6.15.5.2-007 | R-6.15.5.2-008 | R-6.15.5.2-009 |
+| R-6.15.5.2-010 | R-6.15.5.2-011 | R-6.15.5.2-012 | R-6.15.5.2-013 | R-6.15.5.2-014 | R-6.15.5.2-014a5 |
+| R-6.15.5.2-015 | | | | | |
+| 6.15.5.3 Administrative | | | | | |
+| R-6.15.5.3-001 | R-6.15.5.3-002 | R-6.15.5.3-003 | R-6.15.5.3-004 | R-6.15.5.3-005 | |
+| 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications | | | | | |
+| R-6.15.5.4-001 | | | | | |
+| 6.15.6 MCX Service Ad hoc Group Emergency Alert | | | | | |
+| NA | | | | | |
+| 6.15.6.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.6.2 General aspects | | | | | |
+| R-6.15.6.2-001 | R-6.15.6.2-002 | R-6.15.6.2-002a | R-6.15.6.2-003 | R-6.15.6.2-004 | R-6.15.6.2-005a |
+
+| | | | | | |
+|-----------------------------------------------------------------------------|-----------------|----------------|----------------|----------------|----------------|
+| R-6.15.6.2-005a | R-6.15.6.2-005b | R-6.15.6.2-006 | R-6.15.6.2-007 | R-6.15.6.2-008 | |
+| 6.15.6.3 Administrative | | | | | |
+| R-6.15.6.3-001 | R-6.15.6.3-002 | R-6.15.6.3-003 | R-6.15.6.3-004 | R-6.15.6.3-005 | |
+| 6.16 Interaction with telephony services | | | | | |
+| R-6.16-001 | R-6.16-002 | | | | |
+| 6.17 Interworking | | | | | |
+| NA | | | | | |
+| 6.17.1 Non-3GPP access | | | | | |
+| R-6.17.1-001 | | | | | |
+| 6.17.2 Interworking between MCX Service systems | | | | | |
+| R-6.17.2-001 | R-6.17.2-002 | R-6.17.2-003 | R-6.17.2-004 | R-6.17.2-005 | R-6.17.2-006 |
+| R-6.17.2-007 | R-6.17.2-008 | | | | |
+| 6.17.3 Interworking with non-MCX Service systems | | | | | |
+| NA | | | | | |
+| 6.17.3.1 GSM-R | | | | | |
+| R-6.17.3.1-001 | R-6.17.3.1-002 | R-6.17.3.1-003 | R-6.17.3.1-004 | R-6.17.3.1-005 | |
+| 6.17.3.2 External systems | | | | | |
+| R-6.17.3.2-001 | R-6.17.3.2-002 | | | | |
+| 6.18 MCX Service coverage extension using ProSe UE-to-Network Relays | | | | | |
+| R-6.18-001 | R-6.18-002 | R-6.18-003 | R-6.18-004 | R-6.18-005 | R-6.18-006 |
+| 6.19 Additional MCX Service requirements | | | | | |
+| NA | | | | | |
+| 6.19.1 Communication rejection and queuing | | | | | |
+| NA | | | | | |
+| 6.19.1.1 Requirements | | | | | |
+| R-6.19.1.1-001 | R-6.19.1.1-002 | R-6.19.1.1-003 | R-6.19.1.1-004 | R-6.19.1.1-005 | R-6.19.1.1-006 |
+| R-6.19.1.1-007 | | | | | |
+| 7 MCX Service requirements specific to off-network use | | | | | |
+| NA | | | | | |
+| 7.1 Off-network communications overview | | | | | |
+| NA | | | | | |
+| 7.2 General off-network MCX Service requirements | | | | | |
+| R-7.2-001 | R-7.2-002 | R-7.2-003 | R-7.2-004 | R-7.2-005 | |
+| 7.3 Admission control | | | | | |
+| NA | | | | | |
+| 7.3.1 General aspects | | | | | |
+| R-7.3.1-001 | R-7.3.1-002 | R-7.3.1-003 | | | |
+| 7.3.2 Communication initiation | | | | | |
+| R-7.3.2-001 | R-7.3.2-002 | R-7.3.2-003 | R-7.3.2-004 | R-7.3.2-005 | |
+| 7.4 Communication termination | | | | | |
+| R-7.4-001 | R-7.4-002 | R-7.4-003 | R-7.4-004 | | |
+| 7.5 Broadcast Group | | | | | |
+| R-7.5-001 | R-7.5-002 | | | | |
+| 7.6 MCX Service priority requirements | | | | | |
+| R-7.6-001 | R-7.6-002 | R-7.6-003 | R-7.6-004 | R-7.6-005 | R-7.6-006 |
+
+| | | | | | |
+|----------------------------------------------------------------------------------|---------------|---------------|---------------|---------------|--|
+| R-7.6-007 | R-7.6-008 | R-7.6-009 | | | |
+| 7.7 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 7.7.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-7.7.1-001 | R-7.7.1-002 | R-7.7.1-003 | | | |
+| 7.7.2 MCX Service Emergency Group Communication cancellation requirements | | | | | |
+| R-7.7.2-001 | | | | | |
+| 7.7.3 Imminent Peril Communication | | | | | |
+| NA | | | | | |
+| 7.7.3.1 Imminent Peril Group Communication requirements | | | | | |
+| R-7.7.3.1-001 | R-7.7.3.1-002 | R-7.7.3.1-003 | R-7.7.3.1-004 | R-7.7.3.1-005 | |
+| 7.7.3.2 Imminent Peril Group Communication cancellation requirements | | | | | |
+| R-7.7.3.2-001 | R-7.7.3.2-002 | | | | |
+| 7.8 Location | | | | | |
+| R-7.8-001 | R-7.8-002 | R-7.8-003 | | | |
+| 7.9 Security | | | | | |
+| R-7.9-001 | R-7.9-002 | | | | |
+| 7.10 Off-network MCX Service operations | | | | | |
+| R-7.10-001 | R-7.10-002 | R-7.10-003 | | | |
+| 7.11 Off-network UE functionality | | | | | |
+| R-7.11-001 | R-7.11-002 | R-7.11-003 | | | |
+| 7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay | | | | | |
+| NA | | | | | |
+| 7.12.1 UE-to-Network Relay for all data types | | | | | |
+| R-7.12.1-001 | R-7.12.1-002 | R-7.12.1-003 | R-7.12.1-004 | | |
+| 7.12.2 UE-to-UE Relay streaming | | | | | |
+| R-7.12.2-001 | R-7.12.2-002 | R-7.12.2-003 | | | |
+| 7.12.3 Off-Network streaming | | | | | |
+| R-7.12.3-001 | R-7.12.3-002 | R-7.12.3-003 | | | |
+| 7.13 Switching to off-network MCX Service | | | | | |
+| R-7.13-001 | R-7.13-002 | R-7.13-003 | R-7.13-004 | R-7.13-005 | |
+| 7.14 Off-network recording and audit requirements | | | | | |
+| R-7.14-001 | R-7.14-001a | R-7.14-002 | R-7.14-002a | | |
+| 7.15 Off-network UE-to-UE relay | | | | | |
+| NA | | | | | |
+| 7.15.1 Private Communications | | | | | |
+| R-7.15.1-001 | R-7.15.1-002 | R-7.15.1-003 | | | |
+| 7.15.2 Group Communications | | | | | |
+| R-7.15.2-001 | R-7.15.2-002 | | | | |
+| 7.16 Off-network Ad hoc Group Communication | | | | | |
+| R-7.16-001 | | | | | |
+| 8 Inter-MCX Service interworking | | | | | |
+| NA | | | | | |
+| 8.1 Inter-MCX Service interworking overview | | | | | |
+| NA | | | | | |
+| 8.2 Concurrent operation of different MCX Services | | | | | |
+
+| | | | | | |
+|-----------------------------------------------------------|---------------|---------------|---------------|-------------|-------------|
+| NA | | | | | |
+| 8.2.1 Overview | | | | | |
+| NA | | | | | |
+| 8.2.2 Requirements | | | | | |
+| R-8.2.2-001 | R-8.2.2-002 | R-8.2.2-003 | R-8.2.2-004 | R-8.2.2-005 | R-8.2.2-006 |
+| R-8.2.2-007 | | | | | |
+| 8.3 Use of unsharable resources within a UE | | | | | |
+| R-8.3-001 | R-8.3-002 | R-8.3-003 | R-8.3-004 | R-8.3-005 | R-8.3-006 |
+| 8.4 Single group with multiple MCX Services | | | | | |
+| NA | | | | | |
+| 8.4.1 Overview | | | | | |
+| NA | | | | | |
+| 8.4.2 Requirements | | | | | |
+| R-8.4.2-001 | R-8.4.2-002 | R-8.4.2-003 | R-8.4.2-004 | R-8.4.2-005 | |
+| 8.4.3 Compatibility of UE | | | | | |
+| NA | | | | | |
+| 8.4.3.1 Advertising service capabilities required | | | | | |
+| R-8.4.3.1-001 | R-8.4.3.1-002 | R-8.4.3.1-003 | R-8.4.3.1-004 | | |
+| 8.4.3.2 Conversion between capabilities | | | | | |
+| R-8.4.3.2-001 | | | | | |
+| 8.4.4 Individual permissions for service access | | | | | |
+| R-8.4.4-001 | | | | | |
+| 8.4.5 Common alias and user identities or mappable | | | | | |
+| R-8.4.5-001 | | | | | |
+| 8.4.6 Single location message | | | | | |
+| R-8.4.6-001 | R-8.4.6-002 | R-8.4.6-003 | | | |
+| 8.5 Priority between services | | | | | |
+| NA | | | | | |
+| 8.5.1 Overview | | | | | |
+| NA | | | | | |
+| 8.5.2 Requirements | | | | | |
+| R-8.5.2-001 | R-8.5.2-002 | R-8.5.2-003 | R-8.5.2-004 | R-8.5.2-005 | |
+| 9 Air Ground Air Communications | | | | | |
+| NA | | | | | |
+| 9.1 Service description | | | | | |
+| NA | | | | | |
+| 9.2 Requirements | | | | | |
+| R-9.2-001 | | | | | |
+| 10 MCX Service in IOPS mode | | | | | |
+| R-10-001 | | | | | |
+
+## Annex B (normative): MCCoRe Requirements for MCVideo
+
+Table B.1 provides an exhaustive list of those requirements in 3GPP TS 22.280 that are applicable to MCVideo.
+
+**Table B.1**
+
+| | | | | | |
+|---------------------------------------------------------------------------------|-------------|-------------|-------------|--------------|--------------|
+| 5 MCX Service Requirements common for on the network and off the network | | | | | |
+| NA | | | | | |
+| 5.1 General Group Communications requirements | | | | | |
+| NA | | | | | |
+| 5.1.1 General aspects | | | | | |
+| R-5.1.1-001 | R-5.1.1-002 | R-5.1.1-003 | R-5.1.1-004 | R-5.1.1-005 | R-5.1.1-006 |
+| 5.1.2 Group/status information | | | | | |
+| R-5.1.2-001 | R-5.1.2-002 | | | | |
+| 5.1.3 Group configuration | | | | | |
+| R-5.1.3-001 | R-5.1.3-002 | | | | |
+| 5.1.4 Identification | | | | | |
+| R-5.1.4-001 | | | | | |
+| 5.1.5 Membership/affiliation | | | | | |
+| R-5.1.5-001 | R-5.1.5-002 | R-5.1.5-003 | R-5.1.5-004 | R-5.1.5-005 | R-5.1.5-006 |
+| R-5.1.5-007 | R-5.1.5-008 | | | | |
+| 5.1.6 Group Communication administration | | | | | |
+| R-5.1.6-001 | | | | | |
+| 5.1.7 Prioritization | | | | | |
+| R-5.1.7-001 | R-5.1.7-002 | | | | |
+| 5.1.8 Charging requirements for MCX Service | | | | | |
+| R-5.1.8-001 | R-5.1.8-003 | R-5.1.8-004 | R-5.1.8-005 | R-5.1.8-006 | R-5.1.8-007 |
+| R-5.1.8-008 | R-5.1.8-009 | R-5.1.8-010 | R-5.1.8-011 | | |
+| 5.1.9 MCX Service Emergency Alert triggered by location | | | | | |
+| R-5.1.9-001 | R-5.1.9-002 | | | | |
+| 5.2 Broadcast Group | | | | | |
+| NA | | | | | |
+| 5.2.1 General Broadcast Group Communication | | | | | |
+| R-5.2.1-001 | R-5.2.1-002 | | | | |
+| 5.2.2 Group-Broadcast Group (e.g., announcement group) | | | | | |
+| R-5.2.2-001 | R-5.2.2-002 | R-5.2.2-003 | R-5.2.2-004 | | |
+| 5.2.3 User-Broadcast Group (e.g., System Communication) | | | | | |
+| R-5.2.3-001 | R-5.2.3-002 | | | | |
+| 5.3 Late communication entry | | | | | |
+| R-5.3-001 | R-5.3-002 | R-5.3-003 | R-5.3-004 | R-5.3-005 | |
+| 5.4 Receiving from multiple MCX Service communications | | | | | |
+| 5.4.1 Overview | | | | | |
+| NA | | | | | |
+| 5.4.2 Requirements | | | | | |
+| R-5.4.2-001 | R-5.4.2-002 | R-5.4.2-003 | R-5.4.2-004 | R-5.4.2-004A | R-5.4.2-004B |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|------------------|-----------------|
+| R-5.4.2-005 | R-5.4.2-006 | R-5.4.2-007 | R-5.4.2-007a | R-5.4.2-008 | R-5.4.2-009 |
+| 5.5 Private Communication | | | | | |
+| NA | | | | | |
+| 5.5.1 Private Communication general requirements | | | | | |
+| R-5.5.1-001 | | | | | |
+| 5.5.2 Charging requirement for MCX Service | | | | | |
+| R-5.5.2-001 | | | | | |
+| 5.6 MCX Service priority requirements | | | | | |
+| NA | | | | | |
+| 5.6.1 Overview | | | | | |
+| NA | | | | | |
+| 5.6.2 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 5.6.2.1 MCX Service Emergency and Imminent Peril general requirements | | | | | |
+| NA | | | | | |
+| 5.6.2.1.1 Overview | | | | | |
+| NA | | | | | |
+| 5.6.2.1.2 Requirements | | | | | |
+| R-5.6.2.1.2-001 | R-5.6.2.1.2-002 | R-5.6.2.1.2-003 | R-5.6.2.1.2-004 | R-5.6.2.1.2-005 | |
+| 5.6.2.2 MCX Service Emergency Group Communication | | | | | |
+| NA | | | | | |
+| 5.6.2.2.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-5.6.2.2.1-001 | R-5.6.2.2.1-002 | R-5.6.2.2.1-003 | R-5.6.2.2.1-004 | R-5.6.2.2.1-005 | R-5.6.2.2.1-006 |
+| R-5.6.2.2.1-007 | R-5.6.2.2.1-008 | R-5.6.2.2.1-009 | R-5.6.2.2.1-010 | R-5.6.2.2.1-011 | R-5.6.2.2.1-012 |
+| R-5.6.2.2.1-013 | R-5.6.2.2.1-014 | | | | |
+| 5.6.2.2.2 MCX Service Emergency Group Communication cancellation requirements | | | | | |
+| R-5.6.2.2.2-001 | R-5.6.2.2.2-002 | R-5.6.2.2.2-003 | R-5.6.2.2.2-004 | R-5.6.2.2.2-005 | |
+| 5.6.2.3 MCX Service Imminent Peril Group | | | | | |
+| NA | | | | | |
+| 5.6.2.3.1 MCX Service Imminent Peril Group Communication requirements | | | | | |
+| R-5.6.2.3.1-001 | R-5.6.2.3.1-002 | R-5.6.2.3.1-003 | R-5.6.2.3.1-004 | R-5.6.2.3.1-005 | R-5.6.2.3.1-006 |
+| R-5.6.2.3.1-007 | R-5.6.2.3.1-008 | R-5.6.2.3.1-009 | | | |
+| 5.6.2.3.2 MCX Service Imminent Peril Group Communications cancellation requirements | | | | | |
+| R-5.6.2.3.2-001 | R-5.6.2.3.2-002 | R-5.6.2.3.2-003 | R-5.6.2.3.2-004 | | |
+| 5.6.2.4 MCX Service Emergency Alert | | | | | |
+| NA | | | | | |
+| 5.6.2.4.1 MCX Service Emergency Alert requirements | | | | | |
+| R-5.6.2.4.1-001 | R-5.6.2.4.1-002 | R-5.6.2.4.1-003 | R-5.6.2.4.1-004 | R-5.6.2.4.1-004a | |
+| R-5.6.2.4.1-005 | R-5.6.2.4.1-006 | R-5.6.2.4.1-007 | R-5.6.2.4.1-008 | R-5.6.2.4.1-009 | R-5.6.2.4.1-010 |
+| R-5.6.2.4.1-011 | R-5.6.2.4.1-012 | R-5.6.2.4.1-013 | | | |
+| 5.6.2.4.2 MCX Service Emergency Alert cancellation requirements | | | | | |
+| R-5.6.2.4.2-001 | R-5.6.2.4.2-002 | R-5.6.2.4.2-003 | | | |
+| 5.7 MCX Service User ID | | | | | |
+| R-5.7-001 | R-5.7-002 | R-5.7-003 | | | |
+| 5.8 MCX UE Management | | | | | |
+
+| | | | | | |
+|-------------------------------------------------------------------------|--------------|--------------|--------------|--------------|-------------|
+| R-5.8-001 | R-5.8-002 | | | | |
+| 5.9 MCX Service User Profile | | | | | |
+| R-5.9-001 | R-5.9-002 | | | | |
+| 5.9A Functional alias | | | | | |
+| R-5.9a-001 | R-5.9a-001a | R-5.9a-001b | R-5.9a-001c | R-5.9a-002 | R-5.9a-002a |
+| R-5.9a-003 | R-5.9a-004 | R-5.9a-005 | R-5.9a-006 | | |
+| R-5.9a-007 | R-5.9a-008 | R-5.9a-009 | R-5.9a-010 | R-5.9a-011 | R-5.9a-012 |
+| R-5.9a-013 | R-5.9a-014 | R-5.9a-015 | R-5.9a-016 | R-5.9a-017 | R-5.9a-018 |
+| R-5.9a-019 | R-5.9a-020 | R-5.9a-021 | R-5.9a-022 | R-5.9a-023 | R-5.9a-024 |
+| R-5.9a-025 | R-5.9a-026 | R-5.9a-027 | R-5.9a-028 | R-5.9a-029 | R-5.9a-030 |
+| R-5.9a-031 | | | | | |
+| 5.10 Support for multiple devices | | | | | |
+| R-5.10-001 | R-5.10-001a | R-5.10-002 | | | |
+| 5.11 Location | | | | | |
+| R-5.11-001 | R-5.11-002 | R-5.11-002a | R-5.11-003 | R-5.11-004 | R-5.11-005 |
+| R-5.11-006 | R-5.11-007 | R-5.11-008 | R-5.11-009 | R-5.11-010 | R-5.11-011 |
+| R-5.11-012 | R-5.11-013 | R-5.11-014 | R-5.11-015 | | |
+| 5.12 Security | | | | | |
+| R-5.12-001 | R-5.12-002 | R-5.12-003 | R-5.12-004 | R-5.12-005 | R-5.12-006 |
+| R-5.12-007 | R-5.12-008 | R-5.12-009 | R-5.12-010 | R-5.12-011 | R-5.12-012 |
+| R-5.12-013 | R-5.12-014 | | | | |
+| 5.13 Media quality | | | | | |
+| R-5.13-001 | | | | | |
+| 5.14 Relay requirements | | | | | |
+| R-5.14-001 | R-5.14-002 | R-5.14-003 | R-5.14-004 | | |
+| 5.15 Gateway requirements | | | | | |
+| R-5.15-001 | R-5.15-002 | R-5.15-003 | | | |
+| 5.16 Control and management by Mission Critical Organizations | | | | | |
+| NA | | | | | |
+| 5.16.1 Overview | | | | | |
+| NA | | | | | |
+| 5.16.2 General requirements | | | | | |
+| R-5.16.2-001 | R-5.16.2-002 | R-5.16.2-003 | R-5.16.2-004 | R-5.16.2-005 | |
+| 5.16.3 Operational visibility for Mission Critical Organizations | | | | | |
+| R-5.16.3-001 | | | | | |
+| 5.17 General administrative – groups and users | | | | | |
+| R-5.17-001 | R-5.17-002 | R-5.17-003 | R-5.17-004 | R-5.17-005 | R-5.17-006 |
+| R-5.17-007 | R-5.17-008 | | | | |
+| 5.18 Open interfaces for MCX services | | | | | |
+| NA | | | | | |
+| 5.18.1 Overview | | | | | |
+| NA | | | | | |
+| 5.18.2 Requirements | | | | | |
+| R-5.18.2-001 | R-5.18.2-002 | R-5.18.2-003 | R-5.18.2-004 | | |
+| 5.19 Media forwarding | | | | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------|----------------|----------------|----------------|-------------|-------------|
+| NA | | | | | |
+| 5.19.1 Service description | | | | | |
+| NA | | | | | |
+| 5.19.2 Requirements | | | | | |
+| R-5.19.2-001 | R-5.19.2-002 | R-5.19.2-003 | | | |
+| 5.20 Receipt notification | | | | | |
+| NA | | | | | |
+| 5.20.1 Service description | | | | | |
+| NA | | | | | |
+| 5.20.2 Requirements | | | | | |
+| R-5.20.2-001 | | | | | |
+| 5.21 Additional services for MCX Service communications | | | | | |
+| NA | | | | | |
+| 5.21.1 Remotely initiated MCX Service communication | | | | | |
+| NA | | | | | |
+| 5.21.1.1 Overview | | | | | |
+| NA | | | | | |
+| 5.21.1.2 Requirements | | | | | |
+| R-5.21.1.2-001 | R-5.21.1.2-002 | R-5.21.1.2-003 | R-5.21.1.2-004 | | |
+| 5.21.2 Remotely terminated MCX Service communication | | | | | |
+| NA | | | | | |
+| 5.21.2.1 Requirements | | | | | |
+| R-5.21.2.1-001 | | | | | |
+| 6 MCX Service requirements specific to on-network use | | | | | |
+| NA | | | | | |
+| 6.1 General administrative – groups and users | | | | | |
+| R-6.1-001 | R-6.1-002 | R-6.1-003 | R-6.1-004 | R-6.1-005 | |
+| 6.2 MCX Service communications | | | | | |
+| NA | | | | | |
+| 6.2.1 Notification and acknowledgement for MCX Service Group Communications | | | | | |
+| R-6.2.1-001 | R-6.2.1-002 | R-6.2.1-003 | R-6.2.1-004 | R-6.2.1-005 | |
+| 6.2.2 Queuing | | | | | |
+| R-6.2.2-001 | R-6.2.2-002 | R-6.2.2-003 | R-6.2.2-004 | R-6.2.2-005 | R-6.2.2-006 |
+| 6.3 General requirements | | | | | |
+| R-6.3-001 | R-6.3-002 | R-6.3-003 | R-6.3-004 | | |
+| 6.4 General group communication | | | | | |
+| NA | | | | | |
+| 6.4.1 General aspects | | | | | |
+| R-6.4.1-001 | | | | | |
+| 6.4.2 Group status/information | | | | | |
+| R-6.4.2-005 | R-6.4.2-001 | R-6.4.2-002 | R-6.4.2-003 | R-6.4.2-004 | R-6.4.2-006 |
+| R-6.4.2-007 | | | | | |
+| 6.4.3 Identification | | | | | |
+| R-6.4.3-001 | R-6.4.3-002 | | | | |
+| 6.4.4 Membership/affiliation | | | | | |
+| R-6.4.4-001 | R-6.4.4-002 | R-6.4.4-002a | R-6.4.4-003 | R-6.4.4-004 | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------------------|---------------|----------------|----------------|---------------|---------------|
+| 6.4.5 Membership/affiliation list | | | | | |
+| R-6.4.5-001 | R-6.4.5-002 | R-6.4.5-003 | R-6.4.5-003a | R-6.4.5-004 | R-6.4.5-005 |
+| R-6.4.5-006 | R-6.4.5-007 | R-6.4.5-008 | | | |
+| 6.4.6 Authorized user remotely changes another MCX User's affiliated and/or Selected MCX Service Group(s) | | | | | |
+| NA | | | | | |
+| 6.4.6.1 Mandatory change | | | | | |
+| R-6.4.6.1-001 | R-6.4.6.1-002 | R-6.4.6.1-003 | R-6.4.6.1-004 | | |
+| 6.4.6.2 Negotiated change | | | | | |
+| R-6.4.6.2-001 | R-6.4.6.2-002 | R-6.4.6.2-003 | R-6.4.6.2-004 | R-6.4.6.2-005 | R-6.4.6.2-006 |
+| 6.4.7 Prioritization | | | | | |
+| R-6.4.7-001 | R-6.4.7-002 | R-6.4.7-003 | R-6.4.7-004 | | |
+| 6.4.8 Relay requirements | | | | | |
+| R-6.4.8-001 | | | | | |
+| 6.4.9 Administrative | | | | | |
+| R-6.4.9-001 | R-6.4.9-002 | R-6.4.9-003 | R-6.4.9-004 | R-6.4.9-005 | R-6.4.9-006 |
+| 6.5 Broadcast Group | | | | | |
+| NA | | | | | |
+| 6.5.1 General Broadcast Group Communication | | | | | |
+| R-6.5.1-001 | R-6.5.1-002 | | | | |
+| 6.5.2 Group-Broadcast Group (e.g., announcement group) | | | | | |
+| R-6.5.2-001 | | | | | |
+| 6.5.3 User-Broadcast Group (e.g., system communication) | | | | | |
+| R-6.5.3-001 | | | | | |
+| 6.6 Dynamic group management (i.e., dynamic reporting) | | | | | |
+| NA | | | | | |
+| 6.6.1 General dynamic regrouping | | | | | |
+| R-6.6.1-001 | R-6.6.1-002 | R-6.6.1-003 | R-6.6.1-004 | R-6.6.1-005 | R-6.6.1-006 |
+| 6.6.2 Group regrouping | | | | | |
+| NA | | | | | |
+| 6.6.2.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.2.2 Requirements | | | | | |
+| R-6.6.2.2-001 | R-6.6.2.2-002 | R-6.6.2.2-003 | R-6.6.2.2-004 | R-6.6.2.2-005 | R-6.6.2.2-006 |
+| R-6.6.2.2-007 | R-6.6.2.2-008 | R-6.6.2.2-009 | R-6.6.2.2-011 | R-6.6.2.2-012 | R-6.6.2.2-013 |
+| 6.6.3 Temporary Broadcast Groups | | | | | |
+| R-6.6.3-001 | R-6.6.3-001a | R-6.6.3-001b | R-6.6.3-002 | | |
+| 6.6.4 User regrouping | | | | | |
+| NA | | | | | |
+| 6.6.4.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.4.2 Requirements | | | | | |
+| R-6.6.4.2-001 | R-6.6.4.2-002 | R-6.6.4.2-002a | R-6.6.4.2-002b | R-6.6.4.2-003 | R-6.6.4.2-004 |
+| R-6.6.4.2-005 | | | | | |
+| 6.6.5 Dynamic Group Participation | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------|---------------|---------------|---------------|---------------|---------------|
+| 6.6.5.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.5.2 Requirements | | | | | |
+| R-6.6.5.2-001 | R-6.6.5.2-002 | R-6.6.5.2-003 | R-6.6.5.2-004 | R-6.6.5.2-005 | R-6.6.5.2-006 |
+| R-6.6.5.2-007 | R-6.6.5.2-008 | | | | |
+| 6.7 Private Communication | | | | | |
+| NA | | | | | |
+| 6.7.1 Overview | | | | | |
+| NA | | | | | |
+| 6.7.2 General requirements | | | | | |
+| R-6.7.2-001 | R-6.7.2-002 | R-6.7.2-003 | R-6.7.2-004 | R-6.7.2-005 | |
+| 6.7.3 Administrative | | | | | |
+| R-6.7.3-001 | R-6.7.3-002 | R-6.7.3-003 | R-6.7.3-004 | R-6.7.3-005 | R-6.7.3-006 |
+| R-6.7.3-007 | R-6.7.3-007a | R-6.7.3-008 | | | |
+| 6.7.4 Prioritization | | | | | |
+| R-6.7.4-001 | R-6.7.4-002 | R-6.7.4-003 | R-6.7.4-004 | R-6.7.4-005 | R-6.7.4-006 |
+| R-6.7.4-007 | | | | | |
+| 6.7.5 Private Communication (without Floor control) commencement requirements | | | | | |
+| R-6.7.5-001 | R-6.7.5-002 | R-6.7.5-003 | | | |
+| 6.7.6 Private Communication (without Floor control) termination | | | | | |
+| R-6.7.6-001 | R-6.7.6-002 | | | | |
+| 6.8 MCX Service priority requirements | | | | | |
+| NA | | | | | |
+| 6.8.1 General | | | | | |
+| R-6.8.1-001 | R-6.8.1-002 | R-6.8.1-003 | R-6.8.1-004 | R-6.8.1-005 | R-6.8.1-006 |
+| R-6.8.1-007 | R-6.8.1-008 | R-6.8.1-009 | R-6.8.1-010 | R-6.8.1-011 | R-6.8.1-012 |
+| R-6.8.1-013 | R-6.8.1-014 | R-6.8.1-015 | R-6.8.1-016 | | |
+| 6.8.2 3GPP system access controls | | | | | |
+| R-6.8.2-001 | | | | | |
+| 6.8.3 3GPP system admission controls | | | | | |
+| R-6.8.3-001 | | | | | |
+| 6.8.4 3GPP system scheduling controls | | | | | |
+| R-6.8.4-001 | | | | | |
+| 6.8.5 UE access controls | | | | | |
+| R-6.8.5-001 | | | | | |
+| 6.8.6 Mobility and load management | | | | | |
+| NA | | | | | |
+| 6.8.6.1 Mission Critical mobility management according to priority | | | | | |
+| R-6.8.6.1-001 | R-6.8.6.1-002 | | | | |
+| 6.8.6.2 Load management | | | | | |
+| R-6.8.6.2-001 | R-6.8.6.2-002 | R-6.8.6.2-003 | R-6.8.6.2-004 | R-6.8.6.2-005 | |
+| 6.8.7 Application layer priorities | | | | | |
+| NA | | | | | |
+| 6.8.7.1 Overview | | | | | |
+| NA | | | | | |
+| 6.8.7.2 Requirements | | | | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|
+| R-6.8.7.2-001 | R-6.8.7.2-002 | R-6.8.7.2-003 | R-6.8.7.2-004 | R-6.8.7.2-005 | R-6.8.7.2-006 |
+| R-6.8.7.2-007 | R-6.8.7.2-008 | R-6.8.7.2-009 | R-6.8.7.2-010 | | |
+| 6.8.8 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 6.8.8.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-6.8.8.1-001 | R-6.8.8.1-002 | R-6.8.8.1-003 | R-6.8.8.1-004 | | |
+| 6.8.8.2 MCX Service Emergency Private Communication requirements | | | | | |
+| R-6.8.8.2-001 | R-6.8.8.2-002 | R-6.8.8.2-003 | R-6.8.8.2-004 | | |
+| 6.8.8.3 Imminent Peril Group Communication requirements | | | | | |
+| R-6.8.8.3-001 | R-6.8.8.3-002 | R-6.8.8.3-003 | | | |
+| 6.8.8.4 MCX Service Emergency Alert | | | | | |
+| NA | | | | | |
+| 6.8.8.4.1 Requirements | | | | | |
+| R-6.8.8.4.1-001 | R-6.8.8.4.1-002 | R-6.8.8.4.1-003 | R-6.8.8.4.1-004 | R-6.8.8.4.1-005 | R-6.8.8.4.1-006 |
+| 6.8.8.4.2 MCX Service Emergency Alert cancellation requirements | | | | | |
+| R-6.8.8.4.2-001 | R-6.8.8.4.2-002 | | | | |
+| 6.8.8.9 Ad hoc Group Communication requirements | | | | | |
+| R-6.8.8.9-001 | | | | | |
+| 6.9 IDs and aliases | | | | | |
+| R-6.9-001 | R-6.9-002 | R-6.9-003 | R-6.9-004 | | |
+| 6.10 User Profile management | | | | | |
+| R-6.10-001 | R-6.10-002 | R-6.10-003 | R-6.10-004 | | |
+| 6.11 Support for multiple devices | | | | | |
+| R-6.11-001 | R-6.11-002 | R-6.11-003 | | | |
+| 6.12 Location | | | | | |
+| R-6.12-001 | R-6.12-002 | R-6.12-003 | R-6.12-004 | R-6.12-005 | R-6.12-006 |
+| R-6.12-007 | | | | | |
+| 6.13 Security | | | | | |
+| NA | | | | | |
+| 6.13.1 Overview | | | | | |
+| NA | | | | | |
+| 6.13.2 Cryptographic protocols | | | | | |
+| R-6.13.2-001 | R-6.13.2-002 | R-6.13.2-003 | | | |
+| 6.13.3 Authentication | | | | | |
+| R-6.13.3-001 | | | | | |
+| 6.13.4 Access control | | | | | |
+| R-6.13.4-001 | R-6.13.4-002 | R-6.13.4-003 | R-6.13.4-004 | R-6.13.4-005 | R-6.13.4-006 |
+| R-6.13.4-007 | R-6.13.4-008 | R-6.13.4-009 | R-6.13.4-010 | | |
+| 6.13.5 Regulatory issues | | | | | |
+| R-6.13.5-001 | | | | | |
+| 6.13.6 Storage control | | | | | |
+| R-6.13.6-001 | | | | | |
+| 6.14 Interactions for MCX Service Group Communications and MCX Service Private Communications | | | | | |
+| R-6.14-001 | R-6.14-002 | | | | |
+| 6.15 Additional services for MCX Service communications | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|----------------------------------------------------------------------------------------------|------------------|------------------|-----------------|----------------|------------------|
+| 6.15.1 Discreet listening capabilities | | | | | |
+| R-6.15.1-001a | R-6.15.1-001 | R-6.15.1-002 | R-6.15.1-002a | R-6.15.1-003 | R-6.15.1-004 |
+| 6.15.2 Ambient listening | | | | | |
+| NA | | | | | |
+| 6.15.2.1 Overview of ambient listening | | | | | |
+| NA | | | | | |
+| 6.15.2.2 Ambient listening requirements | | | | | |
+| NA | | | | | |
+| 6.15.2.2.1 General ambient listening requirements | | | | | |
+| R-6.15.2.2.1-001 | R-6.15.2.2.1-002 | R-6.15.2.2.1-003 | | | |
+| 6.15.2.2.2 Remotely initiated ambient listening requirements | | | | | |
+| R-6.15.2.2.2-001 | R-6.15.2.2.2-002 | | | | |
+| 6.15.2.2.3 Locally initiated ambient listening requirements | | | | | |
+| R-6.15.2.2.3-001 | R-6.15.2.2.3-002 | | | | |
+| 6.15.3 Remotely initiated MCX Service Communication | | | | | |
+| NA | | | | | |
+| 6.15.3.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.3.2 Requirements | | | | | |
+| R-6.15.3.2-001 | R-6.15.3.2-002 | R-6.15.3.2-003 | R-6.15.3.2-004 | | |
+| 6.15.4 Recording and audit requirements | | | | | |
+| R-6.15.4-001 | R-6.15.4-002 | R-6.15.4-003 | R-6.15.4-004 | R-6.15.4-005 | R-6.15.4-006 |
+| R-6.15.4-007 | R-6.15.4-008 | R-6.15.4-009 | R-6.15.4-010 | R-6.15.4-011 | |
+| 6.15.5 MCX Service Ad hoc Group Communication | | | | | |
+| NA | | | | | |
+| 6.15.5.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.5.2 General Aspects | | | | | |
+| R-6.15.5.2-001 | R-6.15.5.2-001a | R-6.15.5.2-001b | R-6.15.5.2-001c | R-6.15.5.2-002 | R-6.15.5.2-003 |
+| R-6.15.5.2-004 | R-6.15.5.2-005 | R-6.15.5.2-006 | R-6.15.5.2-007 | R-6.15.5.2-008 | R-6.15.5.2-009 |
+| R-6.15.5.2-010 | R-6.15.5.2-011 | R-6.15.5.2-012 | R-6.15.5.2-013 | R-6.15.5.2-014 | R-6.15.5.2-014a5 |
+| R-6.15.5.2-015 | | | | | |
+| 6.15.5.3 Administrative | | | | | |
+| R-6.15.5.3-001 | R-6.15.5.3-002 | R-6.15.5.3-003 | R-6.15.5.3-004 | R-6.15.5.3-005 | |
+| 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications | | | | | |
+| R-6.15.5.4-001 | | | | | |
+| 6.15.6 MCX Service Ad hoc Group Emergency Alert | | | | | |
+| NA | | | | | |
+| 6.15.6.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.6.2 General Aspects | | | | | |
+| R-6.15.6.2-001 | R-6.15.6.2-002 | R-6.15.6.2-002a | R-6.15.6.2-003 | R-6.15.6.2-004 | R-6.15.6.2-005 |
+| R-6.15.6.2-005a | R-6.15.6.2-005b | R-6.15.6.2-006 | -6.15.6.2-007 | R-6.15.6.2-008 | |
+| 6.15.6.3 Administrative | | | | | |
+
+| | | | | | |
+|-----------------------------------------------------------------------------|----------------|----------------|----------------|----------------|----------------|
+| R-6.15.6.3-001 | R-6.15.6.3-002 | R-6.15.6.3-003 | R-6.15.6.3-004 | R-6.15.6.3-005 | |
+| 6.16 Interaction with telephony services | | | | | |
+| R-6.16-001 | R-6.16-002 | | | | |
+| 6.17 Interworking | | | | | |
+| NA | | | | | |
+| 6.17.1 Non-3GPP access | | | | | |
+| R-6.17.1-001 | | | | | |
+| 6.17.2 Interworking between MCX Service systems | | | | | |
+| R-6.17.2-001 | R-6.17.2-002 | R-6.17.2-003 | R-6.17.2-004 | R-6.17.2-005 | R-6.17.2-006 |
+| R-6.17.2-007 | R-6.17.2-008 | | | | |
+| 6.17.3 Interworking with non-MCX Service systems | | | | | |
+| NA | | | | | |
+| 6.17.3.1 GSM-R | | | | | |
+| R-6.17.3.1-001 | R-6.17.3.1-002 | R-6.17.3.1-003 | R-6.17.3.1-004 | R-6.17.3.1-005 | |
+| 6.17.3.2 External systems | | | | | |
+| R-6.17.3.2-001 | R-6.17.3.2-002 | | | | |
+| 6.18 MCX Service coverage extension using ProSe UE-to-Network Relays | | | | | |
+| R-6.18-001 | R-6.18-002 | R-6.18-003 | R-6.18-004 | R-6.18-005 | R-6.18-006 |
+| 6.19 Additional MCX Service requirements | | | | | |
+| NA | | | | | |
+| 6.19.1 Communication rejection and queuing | | | | | |
+| NA | | | | | |
+| 6.19.1.1 Requirements | | | | | |
+| R-6.19.1.1-001 | R-6.19.1.1-002 | R-6.19.1.1-003 | R-6.19.1.1-004 | R-6.19.1.1-005 | R-6.19.1.1-006 |
+| R-6.19.1.1-007 | | | | | |
+| 7 MCX Service requirements specific to off-network use | | | | | |
+| NA | | | | | |
+| 7.1 Off-network communications overview | | | | | |
+| NA | | | | | |
+| 7.2 General off-network MCX Service requirements | | | | | |
+| R-7.2-001 | R-7.2-002 | R-7.2-003 | R-7.2-004 | R-7.2-005 | |
+| 7.3 Admission control | | | | | |
+| NA | | | | | |
+| 7.3.1 General aspects | | | | | |
+| R-7.3.1-001 | R-7.3.1-002 | R-7.3.1-003 | | | |
+| 7.3.2 Communication initiation | | | | | |
+| R-7.3.2-001 | R-7.3.2-002 | R-7.3.2-003 | R-7.3.2-004 | R-7.3.2-005 | |
+| 7.4 Communication termination | | | | | |
+| R-7.4-001 | R-7.4-002 | R-7.4-003 | R-7.4-004 | | |
+| 7.5 Broadcast Group | | | | | |
+| R-7.5-001 | R-7.5-002 | | | | |
+| 7.6 MCX Service priority requirements | | | | | |
+| R-7.6-001 | R-7.6-002 | R-7.6-003 | R-7.6-004 | R-7.6-005 | R-7.6-006 |
+| R-7.6-007 | R-7.6-008 | R-7.6-009 | | | |
+| 7.7 Communication types based on priorities | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|----------------------------------------------------------------------------------|---------------|---------------|---------------|---------------|--|
+| 7.7.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-7.7.1-001 | R-7.7.1-002 | R-7.7.1-003 | | | |
+| 7.7.2 MCX Service Emergency Group Communication cancellation requirements | | | | | |
+| R-7.7.2-001 | | | | | |
+| 7.7.3 Imminent Peril Communication | | | | | |
+| NA | | | | | |
+| 7.7.3.1 Imminent Peril Group Communication requirements | | | | | |
+| R-7.7.3.1-001 | R-7.7.3.1-002 | R-7.7.3.1-003 | R-7.7.3.1-004 | R-7.7.3.1-005 | |
+| 7.7.3.2 Imminent Peril Group Communication cancellation requirements | | | | | |
+| R-7.7.3.2-001 | R-7.7.3.2-002 | | | | |
+| 7.8 Location | | | | | |
+| R-7.8-001 | R-7.8-002 | R-7.8-003 | | | |
+| 7.9 Security | | | | | |
+| R-7.9-001 | R-7.9-002 | | | | |
+| 7.10 Off-network MCX Service operations | | | | | |
+| R-7.10-001 | R-7.10-002 | R-7.10-003 | | | |
+| 7.11 Off-network UE functionality | | | | | |
+| R-7.11-001 | R-7.11-002 | R-7.11-003 | | | |
+| 7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay | | | | | |
+| NA | | | | | |
+| 7.12.1 UE-to-Network Relay for all data types | | | | | |
+| R-7.12.1-001 | R-7.12.1-002 | R-7.12.1-003 | R-7.12.1-004 | | |
+| 7.12.2 UE-to-UE Relay streaming | | | | | |
+| R-7.12.2-001 | R-7.12.2-002 | R-7.12.2-003 | | | |
+| 7.12.3 Off-Network streaming | | | | | |
+| R-7.12.3-001 | R-7.12.3-002 | R-7.12.3-003 | | | |
+| 7.13 Switching to off-network MCX Service | | | | | |
+| R-7.13-001 | R-7.13-002 | R-7.13-003 | R-7.13-004 | R-7.13-005 | |
+| 7.14 Off-network recording and audit requirements | | | | | |
+| R-7.14-001 | R-7.14-001a | R-7.14-002 | R-7.14-002a | | |
+| 7.15 Off-network UE-to-UE relay | | | | | |
+| NA | | | | | |
+| 7.15.1 Private Communications | | | | | |
+| R-7.15.1-001 | R-7.15.1-002 | R-7.15.1-003 | | | |
+| 7.15.2 Group Communications | | | | | |
+| R-7.15.2-001 | R-7.15.2-002 | | | | |
+| 7.16 Off-network Ad hoc Group Communication | | | | | |
+| R-7.16-001 | | | | | |
+| 8 Inter-MCX Service interworking | | | | | |
+| NA | | | | | |
+| 8.1 Inter-MCX Service interworking overview | | | | | |
+| NA | | | | | |
+| 8.2 Concurrent Operation of Different MCX Services | | | | | |
+| NA | | | | | |
+| 8.2.1 Overview | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|-----------------------------------------------------------|---------------|---------------|---------------|-------------|-------------|
+| 8.2.2 Requirements | | | | | |
+| R-8.2.2-001 | R-8.2.2-002 | R-8.2.2-003 | R-8.2.2-004 | R-8.2.2-005 | R-8.2.2-006 |
+| R-8.2.2-007 | | | | | |
+| 8.3 Use of unsharable resources within a UE | | | | | |
+| R-8.3-001 | R-8.3-002 | R-8.3-003 | R-8.3-004 | R-8.3-005 | R-8.3-006 |
+| 8.4 Single Group with multiple MCX Services | | | | | |
+| NA | | | | | |
+| 8.4.1 Overview | | | | | |
+| NA | | | | | |
+| 8.4.2 Requirements | | | | | |
+| R-8.4.2-001 | R-8.4.2-002 | R-8.4.2-003 | R-8.4.2-004 | R-8.4.2-005 | |
+| 8.4.3 Compatibility of UE | | | | | |
+| NA | | | | | |
+| 8.4.3.1 Advertising service capabilities required | | | | | |
+| R-8.4.3.1-001 | R-8.4.3.1-002 | R-8.4.3.1-003 | R-8.4.3.1-004 | | |
+| 8.4.3.2 Conversion between capabilities | | | | | |
+| R-8.4.3.2-001 | | | | | |
+| 8.4.4 Individual permissions for service access | | | | | |
+| R-8.4.4-001 | | | | | |
+| 8.4.5 Common alias and user identities or mappable | | | | | |
+| R-8.4.5-001 | | | | | |
+| 8.4.6 Single location message | | | | | |
+| R-8.4.6-001 | R-8.4.6-002 | R-8.4.6-003 | | | |
+| 8.5 Priority between services | | | | | |
+| NA | | | | | |
+| 8.5.1 Overview | | | | | |
+| NA | | | | | |
+| 8.5.2 Requirements | | | | | |
+| R-8.5.2-001 | R-8.5.2-002 | R-8.5.2-003 | R-8.5.2-004 | R-8.5.2-005 | |
+| 9 Air Ground Air Communications | | | | | |
+| NA | | | | | |
+| 9.1 Service description | | | | | |
+| NA | | | | | |
+| 9.2 Requirements | | | | | |
+| R-9.2-001 | | | | | |
+| 10 MCX Service in IOPS mode | | | | | |
+| R-10-001 | | | | | |
+
+## Annex C (normative): MCCoRe Requirements for MCData
+
+Table C.1 provides an exhaustive list of those requirements in 3GPP TS 22.280 that are applicable to MCData.
+
+Table C.1
+
+| | | | | | |
+|---------------------------------------------------------------------------------|--------------|--------------|--------------|-------------|-------------|
+| 5 MCX Service requirements common for on the network and off the network | | | | | |
+| NA | | | | | |
+| 5.1 General Group Communications requirements | | | | | |
+| NA | | | | | |
+| 5.1.1 General aspects | | | | | |
+| R-5.1.1-001 | R-5.1.1-002 | R-5.1.1-003 | R-5.1.1-006 | | |
+| 5.1.2 Group/status information | | | | | |
+| NA | | | | | |
+| 5.1.3 Group configuration | | | | | |
+| R-5.1.3-001 | R-5.1.3-002 | | | | |
+| 5.1.4 Identification | | | | | |
+| R-5.1.4-001 | | | | | |
+| 5.1.5 Membership/affiliation | | | | | |
+| R-5.1.5-001 | R-5.1.5-002 | R-5.1.5-003 | R-5.1.5-005 | R-5.1.5-007 | R-5.1.5-008 |
+| 5.1.6 Group Communication administration | | | | | |
+| NA | | | | | |
+| 5.1.7 Prioritization | | | | | |
+| R-5.1.7-001 | R-5.1.7-002 | | | | |
+| 5.1.8 Charging requirements for MCX Service | | | | | |
+| R-5.1.8-001 | R-5.1.8-003 | R-5.1.8-004 | R-5.1.8-005 | R-5.1.8-006 | R-5.1.8-007 |
+| R-5.1.8-008 | R-5.1.8-009 | R-5.1.8-010 | R-5.1.8-011 | | |
+| 5.1.9 MCX Service Emergency Alert triggered by location | | | | | |
+| R-5.1.9-001 | R-5.1.9-002 | | | | |
+| 5.2 Broadcast Group | | | | | |
+| NA | | | | | |
+| 5.2.1 General Broadcast Group Communication | | | | | |
+| R-5.2.1-002 | | | | | |
+| 5.2.2 Group-Broadcast Group (e.g., announcement group) | | | | | |
+| R-5.2.2-001 | R-5.2.2-002 | R-5.2.2-003 | R-5.2.2-004 | | |
+| 5.2.3 User-Broadcast Group (e.g., System Communication) | | | | | |
+| R-5.2.3-001 | R-5.2.3-002 | | | | |
+| 5.3 Late communication entry | | | | | |
+| NA | | | | | |
+| 5.4 Receiving from multiple MCX Service communications | | | | | |
+| 5.4.1 Overview | | | | | |
+| NA | | | | | |
+| 5.4.2 Requirements | | | | | |
+| R-5.4.2-001 | R-5.4.2-004 | R-5.4.2-004A | R-5.4.2-004B | R-5.4.2-005 | R-5.4.2-006 |
+| R-5.4.2-007 | R-5.4.2-007a | R-5.4.2-008 | R-5.4.2-009 | | |
+| 5.5 Private Communication | | | | | |
+| NA | | | | | |
+| 5.5.1 Private Communication general requirements | | | | | |
+| R-5.5.1-001 | | | | | |
+| 5.5.2 Charging requirement for MCX Service | | | | | |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|------------------|-----------------|
+| R-5.5.2-001 | | | | | |
+| 5.6 MCX Service priority requirements | | | | | |
+| NA | | | | | |
+| 5.6.1 Overview | | | | | |
+| NA | | | | | |
+| 5.6.2 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 5.6.2.1 MCX Service Emergency and Imminent Peril general requirements | | | | | |
+| NA | | | | | |
+| 5.6.2.1.1 Overview | | | | | |
+| NA | | | | | |
+| 5.6.2.1.2 Requirements | | | | | |
+| R-5.6.2.1.2-001 | R-5.6.2.1.2-002 | R-5.6.2.1.2-003 | R-5.6.2.1.2-004 | R-5.6.2.1.2-005 | |
+| 5.6.2.2 MCX Service Emergency Group Communication | | | | | |
+| NA | | | | | |
+| 5.6.2.2.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-5.6.2.2.1-001 | R-5.6.2.2.1-002 | R-5.6.2.2.1-003 | R-5.6.2.2.1-004 | R-5.6.2.2.1-005 | R-5.6.2.2.1-006 |
+| R-5.6.2.2.1-007 | R-5.6.2.2.1-008 | R-5.6.2.2.1-009 | R-5.6.2.2.1-010 | R-5.6.2.2.1-011 | R-5.6.2.2.1-012 |
+| R-5.6.2.2.1-013 | R-5.6.2.2.1-014 | | | | |
+| 5.6.2.2.2 MCX Service Emergency Group Communication cancellation requirements | | | | | |
+| R-5.6.2.2.2-001 | R-5.6.2.2.2-002 | R-5.6.2.2.2-003 | R-5.6.2.2.2-004 | R-5.6.2.2.2-005 | |
+| 5.6.2.3 MCX Service Imminent Peril Group | | | | | |
+| NA | | | | | |
+| 5.6.2.3.1 MCX Service Imminent Peril Group Communication requirements | | | | | |
+| R-5.6.2.3.1-001 | R-5.6.2.3.1-002 | R-5.6.2.3.1-003 | R-5.6.2.3.1-004 | R-5.6.2.3.1-005 | R-5.6.2.3.1-006 |
+| R-5.6.2.3.1-007 | R-5.6.2.3.1-008 | R-5.6.2.3.1-009 | | | |
+| 5.6.2.3.2 MCX Service Imminent Peril Group Communications cancellation requirements | | | | | |
+| R-5.6.2.3.2-001 | R-5.6.2.3.2-002 | R-5.6.2.3.2-003 | R-5.6.2.3.2-004 | | |
+| 5.6.2.4 MCX Service Emergency Alert | | | | | |
+| NA | | | | | |
+| 5.6.2.4.1 MCX Service Emergency Alert requirements | | | | | |
+| R-5.6.2.4.1-001 | R-5.6.2.4.1-002 | R-5.6.2.4.1-003 | R-5.6.2.4.1-004 | R-5.6.2.4.1-004a | |
+| R-5.6.2.4.1-005 | R-5.6.2.4.1-006 | R-5.6.2.4.1-007 | R-5.6.2.4.1-008 | R-5.6.2.4.1-009 | R-5.6.2.4.1-010 |
+| R-5.6.2.4.1-011 | R-5.6.2.4.1-012 | R-5.6.2.4.1-013 | | | |
+| 5.6.2.4.2 MCX Service Emergency Alert cancellation requirements | | | | | |
+| R-5.6.2.4.2-001 | R-5.6.2.4.2-002 | R-5.6.2.4.2-003 | | | |
+| 5.7 MCX Service User ID | | | | | |
+| R-5.7-001 | R-5.7-002 | R-5.7-003 | | | |
+| 5.8 MCX UE Management | | | | | |
+| R-5.8-001 | R-5.8-002 | | | | |
+| 5.9 MCX Service User Profile | | | | | |
+| R-5.9-001 | R-5.9-002 | | | | |
+| 5.9A Functional alias | | | | | |
+| R-5.9a-001 | R-5.9a-001a | R-5.9a-001b | R-5.9a-001c | R-5.9a-002 | R-5.9a-002a |
+| R-5.9a-003 | R-5.9a-004 | R-5.9a-005 | R-5.9a-006 | | |
+
+| | | | | | |
+|-------------------------------------------------------------------------|--------------|--------------|--------------|--------------|------------|
+| R-5.9a-007 | R-5.9a-008 | R-5.9a-009 | R-5.9a-010 | R-5.9a-011 | R-5.9a-012 |
+| R-5.9a-013 | R-5.9a-014 | R-5.9a-015 | R-5.9a-016 | R-5.9a-017 | R-5.9a-018 |
+| R-5.9a-019 | R-5.9a-020 | R-5.9a-021 | R-5.9a-022 | R-5.9a-023 | R-5.9a-024 |
+| R-5.9a-025 | R-5.9a-026 | R-5.9a-027 | R-5.9a-028 | R-5.9a-029 | R-5.9a-030 |
+| R-5.9a-031 | | | | | |
+| 5.10 Support for multiple devices | | | | | |
+| R-5.10-001 | R-5.10-001a | R-5.10-002 | | | |
+| 5.11 Location | | | | | |
+| R-5.11-001 | R-5.11-002 | R-5.11-002a | R-5.11-003 | R-5.11-004 | R-5.11-005 |
+| R-5.11-006 | R-5.11-007 | R-5.11-008 | R-5.11-009 | R-5.11-010 | R-5.11-011 |
+| R-5.11-012 | R-5.11-013 | R-5.11-014 | R-5.11-015 | | |
+| 5.12 Security | | | | | |
+| R-5.12-001 | R-5.12-002 | R-5.12-003 | R-5.12-004 | R-5.12-005 | R-5.12-006 |
+| R-5.12-007 | R-5.12-008 | R-5.12-009 | R-5.12-010 | R-5.12-011 | R-5.12-012 |
+| R-5.12-013 | R-5.12-014 | | | | |
+| 5.13 Media quality | | | | | |
+| NA | | | | | |
+| 5.14 Relay requirements | | | | | |
+| R-5.14-001 | R-5.14-002 | R-5.14-003 | R-5.14-004 | | |
+| 5.15 Gateway requirements | | | | | |
+| R-5.15-001 | R-5.15-002 | R-5.15-003 | | | |
+| 5.16 Control and management by Mission Critical Organizations | | | | | |
+| NA | | | | | |
+| 5.16.1 Overview | | | | | |
+| NA | | | | | |
+| 5.16.2 General requirements | | | | | |
+| R-5.16.2-001 | R-5.16.2-002 | R-5.16.2-003 | R-5.16.2-004 | R-5.16.2-005 | |
+| 5.16.3 Operational visibility for Mission Critical Organizations | | | | | |
+| R-5.16.3-001 | | | | | |
+| 5.17 General administrative – groups and users | | | | | |
+| R-5.17-001 | R-5.17-002 | R-5.17-003 | R-5.17-004 | R-5.17-005 | R-5.17-006 |
+| R-5.17-007 | R-5.17-008 | | | | |
+| 5.18 Open interfaces for MCX services | | | | | |
+| NA | | | | | |
+| 5.18.1 Overview | | | | | |
+| NA | | | | | |
+| 5.18.2 Requirements | | | | | |
+| R-5.18.2-001 | R-5.18.2-002 | R-5.18.2-003 | R-5.18.2-004 | | |
+| 5.19 Media forwarding | | | | | |
+| NA | | | | | |
+| 5.19.1 Service description | | | | | |
+| NA | | | | | |
+| 5.19.2 Requirements | | | | | |
+| R-5.19.2-001 | R-5.19.2-002 | R-5.19.2-003 | | | |
+| 5.20 Receipt notification | | | | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------|-------------|-------------|
+| NA | | | | | |
+| 5.20.1 Service description | | | | | |
+| NA | | | | | |
+| 5.20.2 Requirements | | | | | |
+| R-5.20.2-001 | | | | | |
+| 5.21 Additional services for MCX Service communications | | | | | |
+| NA | | | | | |
+| 5.21.1 Remotely initiated MCX Service communication | | | | | |
+| NA | | | | | |
+| 5.21.1.1 Overview | | | | | |
+| NA | | | | | |
+| 5.21.1.2 Requirements | | | | | |
+| R-5.21.1.2-001 | R-5.21.1.2-002 | R-5.21.1.2-003 | R-5.21.1.2-004 | | |
+| 5.21.2 Remotely terminated MCX Service communication | | | | | |
+| NA | | | | | |
+| 5.21.2.1 Requirements | | | | | |
+| R-5.21.2.1-001 | | | | | |
+| 6 MCX Service requirements specific to on-network use | | | | | |
+| NA | | | | | |
+| 6.1 General administrative – groups and users | | | | | |
+| R-6.1-001 | R-6.1-002 | R-6.1-003 | R-6.1-004 | R-6.1-005 | |
+| 6.2 MCX Service communications | | | | | |
+| NA | | | | | |
+| 6.2.1 Notification and acknowledgement for MCX Service Group Communications | | | | | |
+| R-6.2.1-001 | R-6.2.1-002 | R-6.2.1-003 | R-6.2.1-004 | R-6.2.1-005 | |
+| 6.2.2 Queuing | | | | | |
+| NA | | | | | |
+| 6.3 General requirements | | | | | |
+| R-6.3-001 | R-6.3-002 | R-6.3-003 | R-6.3-004 | | |
+| 6.4 General group communication | | | | | |
+| NA | | | | | |
+| 6.4.1 General aspects | | | | | |
+| R-6.4.1-001 | | | | | |
+| 6.4.2 Group status/information | | | | | |
+| R-6.4.2-005 | R-6.4.2-001 | R-6.4.2-002 | R-6.4.2-003 | R-6.4.2-004 | R-6.4.2-006 |
+| R-6.4.2-007 | | | | | |
+| 6.4.3 Identification | | | | | |
+| R-6.4.3-001 | R-6.4.3-002 | | | | |
+| 6.4.4 Membership/affiliation | | | | | |
+| R-6.4.4-001 | R-6.4.4-002 | R-6.4.4-002a | R-6.4.4-003 | R-6.4.4-004 | |
+| 6.4.5 Membership/affiliation list | | | | | |
+| R-6.4.5-001 | R-6.4.5-002 | R-6.4.5-003 | R-6.4.5-003a | R-6.4.5-004 | R-6.4.5-005 |
+| R-6.4.5-006 | R-6.4.5-007 | R-6.4.5-008 | | | |
+| 6.4.6 Authorized user remotely changes another MCX User's affiliated and/or Selected MCX Service Group(s) | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|----------------------------------------------------------------|---------------|----------------|----------------|---------------|---------------|
+| 6.4.6.1 Mandatory change | | | | | |
+| R-6.4.6.1-001 | R-6.4.6.1-002 | R-6.4.6.1-003 | R-6.4.6.1-004 | | |
+| 6.4.6.2 Negotiated change | | | | | |
+| R-6.4.6.2-001 | R-6.4.6.2-002 | R-6.4.6.2-003 | R-6.4.6.2-004 | R-6.4.6.2-005 | R-6.4.6.2-006 |
+| 6.4.7 Prioritization | | | | | |
+| R-6.4.7-001 | R-6.4.7-002 | R-6.4.7-003 | R-6.4.7-004 | | |
+| 6.4.8 Relay requirements | | | | | |
+| R-6.4.8-001 | | | | | |
+| 6.4.9 Administrative | | | | | |
+| R-6.4.9-001 | R-6.4.9-004 | R-6.4.9-006 | | | |
+| 6.5 Broadcast Group | | | | | |
+| NA | | | | | |
+| 6.5.1 General Broadcast Group Communication | | | | | |
+| NA | | | | | |
+| 6.5.2 Group-Broadcast Group (e.g., announcement group) | | | | | |
+| NA | | | | | |
+| 6.5.3 User-Broadcast Group (e.g., system communication) | | | | | |
+| NA | | | | | |
+| 6.6 Dynamic group management (i.e., dynamic reporting) | | | | | |
+| NA | | | | | |
+| 6.6.1 General dynamic regrouping | | | | | |
+| R-6.6.1-001 | R-6.6.1-002 | R-6.6.1-003 | R-6.6.1-004 | R-6.6.1-005 | R-6.6.1-006 |
+| 6.6.2 Group regrouping | | | | | |
+| NA | | | | | |
+| 6.6.2.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.2.2 Requirements | | | | | |
+| R-6.6.2.2-001 | R-6.6.2.2-002 | R-6.6.2.2-003 | R-6.6.2.2-004 | R-6.6.2.2-005 | R-6.6.2.2-006 |
+| R-6.6.2.2-007 | R-6.6.2.2-008 | R-6.6.2.2-009 | R-6.6.2.2-011 | R-6.6.2.2-012 | R-6.6.2.2-013 |
+| 6.6.3 Temporary Broadcast Groups | | | | | |
+| R-6.6.3-001 | R-6.6.3-001a | R-6.6.3-001b | R-6.6.3-002 | | |
+| 6.6.4 User regrouping | | | | | |
+| NA | | | | | |
+| 6.6.4.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.4.2 Requirements | | | | | |
+| R-6.6.4.2-001 | R-6.6.4.2-002 | R-6.6.4.2-002a | R-6.6.4.2-002b | R-6.6.4.2-003 | R-6.6.4.2-004 |
+| R-6.6.4.2-005 | | | | | |
+| 6.6.5 Dynamic Group Participation | | | | | |
+| NA | | | | | |
+| 6.6.5.1 Service description | | | | | |
+| NA | | | | | |
+| 6.6.5.2 Requirements | | | | | |
+| R-6.6.5.2-001 | R-6.6.5.2-002 | R-6.6.5.2-003 | R-6.6.5.2-004 | R-6.6.5.2-005 | R-6.6.5.2-006 |
+| R-6.6.5.2-007 | R-6.6.5.2-008 | | | | |
+| 6.7 Private Communication | | | | | |
+
+| | | | | | |
+|--------------------------------------------------------------------------------------|---------------|---------------|---------------|---------------|---------------|
+| NA | | | | | |
+| 6.7.1 Overview | | | | | |
+| NA | | | | | |
+| 6.7.2 General requirements | | | | | |
+| R-6.7.2-001 | R-6.7.2-002 | R-6.7.2-003 | R-6.7.2-004 | R-6.7.2-005 | |
+| 6.7.3 Administrative | | | | | |
+| R-6.7.3-001 | R-6.7.3-002 | R-6.7.3-003 | R-6.7.3-004 | R-6.7.3-005 | R-6.7.3-006 |
+| R-6.7.3-007 | R-6.7.3-007a | R-6.7.3-008 | | | |
+| 6.7.4 Prioritization | | | | | |
+| R-6.7.4-001 | R-6.7.4-002 | R-6.7.4-003 | R-6.7.4-004 | R-6.7.4-005 | R-6.7.4-006 |
+| R-6.7.4-007 | | | | | |
+| 6.7.5 Private Communication (without Floor control) commencement requirements | | | | | |
+| R-6.7.5-001 | R-6.7.5-002 | R-6.7.5-003 | | | |
+| 6.7.6 Private Communication (without Floor control) termination | | | | | |
+| R-6.7.6-001 | R-6.7.6-002 | | | | |
+| 6.8 MCX Service priority Requirements | | | | | |
+| NA | | | | | |
+| 6.8.1 General | | | | | |
+| R-6.8.1-001 | R-6.8.1-002 | R-6.8.1-003 | R-6.8.1-004 | R-6.8.1-005 | R-6.8.1-006 |
+| R-6.8.1-007 | R-6.8.1-008 | R-6.8.1-009 | R-6.8.1-010 | R-6.8.1-011 | R-6.8.1-012 |
+| R-6.8.1-013 | R-6.8.1-014 | R-6.8.1-015 | R-6.8.1-016 | | |
+| 6.8.2 3GPP system access controls | | | | | |
+| R-6.8.2-001 | | | | | |
+| 6.8.3 3GPP system admission controls | | | | | |
+| R-6.8.3-001 | | | | | |
+| 6.8.4 3GPP system scheduling controls | | | | | |
+| R-6.8.4-001 | | | | | |
+| 6.8.5 UE access controls | | | | | |
+| R-6.8.5-001 | | | | | |
+| 6.8.6 Mobility and load Management | | | | | |
+| NA | | | | | |
+| 6.8.6.1 Mission Critical mobility management according to priority | | | | | |
+| R-6.8.6.1-001 | R-6.8.6.1-002 | | | | |
+| 6.8.6.2 Load management | | | | | |
+| R-6.8.6.2-001 | R-6.8.6.2-002 | R-6.8.6.2-003 | R-6.8.6.2-004 | R-6.8.6.2-005 | |
+| 6.8.7 Application layer priorities | | | | | |
+| NA | | | | | |
+| 6.8.7.1 Overview | | | | | |
+| NA | | | | | |
+| 6.8.7.2 Requirements | | | | | |
+| R-6.8.7.2-001 | R-6.8.7.2-002 | R-6.8.7.2-003 | R-6.8.7.2-004 | R-6.8.7.2-005 | R-6.8.7.2-006 |
+| R-6.8.7.2-007 | R-6.8.7.2-008 | R-6.8.7.2-009 | R-6.8.7.2-010 | | |
+| 6.8.8 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 6.8.8.1 MCX Service Emergency Group Communication requirements | | | | | |
+| R-6.8.8.1-001 | R-6.8.8.1-002 | R-6.8.8.1-003 | R-6.8.8.1-004 | | |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|
+| 6.8.8.2 MCX Service Emergency Private Communication requirements | | | | | |
+| R-6.8.8.2-001 | R-6.8.8.2-002 | R-6.8.8.2-003 | R-6.8.8.2-004 | | |
+| 6.8.8.3 Imminent Peril Group Communication requirements | | | | | |
+| R-6.8.8.3-001 | R-6.8.8.3-002 | R-6.8.8.3-003 | | | |
+| 6.8.8.4 MCX Service Emergency Alert | | | | | |
+| NA | | | | | |
+| 6.8.8.4.1 Requirements | | | | | |
+| R-6.8.8.4.1-001 | R-6.8.8.4.1-002 | R-6.8.8.4.1-003 | R-6.8.8.4.1-004 | R-6.8.8.4.1-005 | R-6.8.8.4.1-006 |
+| 6.8.8.4.2 MCX Service Emergency Alert cancellation requirements | | | | | |
+| R-6.8.8.4.2-001 | R-6.8.8.4.2-002 | | | | |
+| 6.8.8.9 Ad hoc Group Communication requirements | | | | | |
+| R-6.8.8.9-001 | | | | | |
+| 6.9 IDs and aliases | | | | | |
+| R-6.9-001 | R-6.9-002 | R-6.9-003 | R-6.9-004 | | |
+| 6.10 User Profile management | | | | | |
+| R-6.10-001 | R-6.10-002 | R-6.10-003 | R-6.10-004 | | |
+| 6.11 Support for multiple devices | | | | | |
+| R-6.11-001 | R-6.11-002 | R-6.11-003 | | | |
+| 6.12 Location | | | | | |
+| R-6.12-001 | R-6.12-002 | R-6.12-003 | R-6.12-004 | R-6.12-005 | R-6.12-006 |
+| R-6.12-007 | | | | | |
+| 6.13 Security | | | | | |
+| NA | | | | | |
+| 6.13.1 Overview | | | | | |
+| NA | | | | | |
+| 6.13.2 Cryptographic protocols | | | | | |
+| R-6.13.2-001 | R-6.13.2-002 | R-6.13.2-003 | | | |
+| 6.13.3 Authentication | | | | | |
+| R-6.13.3-001 | | | | | |
+| 6.13.4 Access control | | | | | |
+| R-6.13.4-001 | R-6.13.4-002 | R-6.13.4-003 | R-6.13.4-004 | R-6.13.4-005 | R-6.13.4-006 |
+| R-6.13.4-007 | R-6.13.4-008 | R-6.13.4-009 | R-6.13.4-010 | | |
+| 6.13.5 Regulatory issues | | | | | |
+| R-6.13.5-001 | | | | | |
+| 6.13.6 Storage control | | | | | |
+| R-6.13.6-001 | | | | | |
+| 6.14 Interactions for MCX Service Group Communications and MCX Service Private Communications | | | | | |
+| R-6.14-001 | R-6.14.002 | | | | |
+| 6.15 Additional services for MCX Service communications | | | | | |
+| NA | | | | | |
+| 6.15.1 Discreet listening capabilities | | | | | |
+| R-6.15.1-001a | R-6.15.1-001 | R-6.15.1-002 | R-6.15.1-002a | R-6.15.1-003 | R-6.15.1-004 |
+| 6.15.2 Ambient listening | | | | | |
+| NA | | | | | |
+| 6.15.2.1 Overview of ambient listening | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|----------------------------------------------------------------------------------------------|------------------|------------------|-----------------|----------------|------------------|
+| 6.15.2.2 Ambient listening requirements | | | | | |
+| NA | | | | | |
+| 6.15.2.2.1 General ambient listening requirements | | | | | |
+| R-6.15.2.2.1-001 | R-6.15.2.2.1-002 | R-6.15.2.2.1-003 | | | |
+| 6.15.2.2.2 Remotely initiated ambient listening requirements | | | | | |
+| R-6.15.2.2.2-001 | R-6.15.2.2.2-002 | | | | |
+| 6.15.2.2.3 Locally initiated ambient listening requirements | | | | | |
+| R-6.15.2.2.3-001 | R-6.15.2.2.3-002 | | | | |
+| 6.15.3 Remotely initiated MCX Service communication | | | | | |
+| NA | | | | | |
+| 6.15.3.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.3.2 Requirements | | | | | |
+| R-6.15.3.2-002 | R-6.15.3.2-001 | | | | |
+| 6.15.4 Recording and audit requirements | | | | | |
+| 6.15.5 MCX Service Ad hoc Group Communication | | | | | |
+| NA | | | | | |
+| 6.15.5.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.5.2 General Aspects | | | | | |
+| R-6.15.5.2-001 | R-6.15.5.2-001a | R-6.15.5.2-001b | R-6.15.5.2-001c | R-6.15.5.2-002 | R-6.15.5.2-003 |
+| R-6.15.5.2-004 | R-6.15.5.2-005 | R-6.15.5.2-006 | R-6.15.5.2-007 | R-6.15.5.2-008 | R-6.15.5.2-009 |
+| R-6.15.5.2-010 | R-6.15.5.2-011 | R-6.15.5.2-012 | R-6.15.5.2-013 | R-6.15.5.2-014 | R-6.15.5.2-014a5 |
+| R-6.15.5.2-015 | | | | | |
+| 6.15.5.3 Administrative | | | | | |
+| R-6.15.5.3-001 | R-6.15.5.3-002 | R-6.15.5.3-003 | R-6.15.5.3-004 | R-6.15.5.3-005 | |
+| 6.15.5.4 Notification and acknowledgement for MCX Service Ad hoc Group Communications | | | | | |
+| R-6.15.5.4-001 | | | | | |
+| R-6.15.4-001 | R-6.15.4-002 | R-6.15.4-003 | R-6.15.4-004 | R-6.15.4-005 | R-6.15.4-006 |
+| R-6.15.4-007 | R-6.15.4-008 | R-6.15.4-009 | R-6.15.4-010 | R-6.15.4-011 | |
+| 6.15.6 MCX Service Ad hoc Group Emergency Alert | | | | | |
+| NA | | | | | |
+| 6.15.6.1 Overview | | | | | |
+| NA | | | | | |
+| 6.15.6.2 General Aspects | | | | | |
+| R-6.15.6.2-001 | R-6.15.6.2-002 | R-6.15.6.2-002a | R-6.15.6.2-003 | R-6.15.6.2-004 | R-6.15.6.2-005 |
+| R-6.15.6.2-005a | R-6.15.6.2-005b | R-6.15.6.2-006 | R-6.15.6.2-007 | R-6.15.6.2-008 | |
+| 6.15.6.3 Administrative | | | | | |
+| R-6.15.6.3-001 | R-6.15.6.3-002 | R-6.15.6.3-003 | R-6.15.6.3-004 | R-6.15.6.3-005 | |
+| 6.16 Interaction with telephony services | | | | | |
+| R-6.16-001 | R-6.16-002 | | | | |
+| 6.17 Interworking | | | | | |
+| NA | | | | | |
+| 6.17.1 Non-3GPP access | | | | | |
+
+| | | | | | |
+|----------------------------------------------------------------------------------|----------------|----------------|----------------|----------------|----------------|
+| R-6.17.1-001 | | | | | |
+| 6.17.2 Interworking between MCX Service systems | | | | | |
+| R-6.17.2-001 | R-6.17.2-002 | R-6.17.2-003 | R-6.17.2-004 | R-6.17.2-005 | R-6.17.2-006 |
+| R-6.17.2-007 | R-6.17.2-008 | | | | |
+| 6.17.3 Interworking with non-MCX Service systems | | | | | |
+| NA | | | | | |
+| 6.17.3.1 GSM-R | | | | | |
+| R-6.17.3.1-001 | | | | | |
+| 6.17.3.2 External systems | | | | | |
+| R-6.17.3.2-001 | R-6.17.3.2-002 | | | | |
+| 6.18 MCX Service coverage extension using ProSe UE-to-Network Relays | | | | | |
+| R-6.18-001 | R-6.18-002 | R-6.18-003 | R-6.18-004 | R-6.18-005 | R-6.18-006 |
+| 6.19 Additional MCX Service requirements | | | | | |
+| NA | | | | | |
+| 6.19.1 Communication rejection and queuing | | | | | |
+| NA | | | | | |
+| 6.19.1.1 Requirements | | | | | |
+| R-6.19.1.1-001 | R-6.19.1.1-002 | R-6.19.1.1-003 | R-6.19.1.1-004 | R-6.19.1.1-005 | R-6.19.1.1-006 |
+| R-6.19.1.1-007 | | | | | |
+| 7 MCX Service requirements specific to off-network use | | | | | |
+| NA | | | | | |
+| 7.1 Off-network communications overview | | | | | |
+| NA | | | | | |
+| 7.2 General off-network MCX Service requirements | | | | | |
+| R-7.2-001 | R-7.2-002 | R-7.2-003 | R-7.2-004 | R-7.2-005 | |
+| 7.3 Admission control | | | | | |
+| NA | | | | | |
+| 7.3.1 General aspects | | | | | |
+| R-7.3.1-001 | R-7.3.1-002 | R-7.3.1-003 | | | |
+| 7.3.2 Communication initiation | | | | | |
+| R-7.3.2-001 | R-7.3.2-002 | R-7.3.2-003 | R-7.3.2-004 | R-7.3.2-005 | |
+| 7.4 Communication termination | | | | | |
+| R-7.4-001 | R-7.4-002 | R-7.4-003 | R-7.4-004 | | |
+| 7.5 Broadcast Group | | | | | |
+| NA | | | | | |
+| 7.6 MCX Service priority requirements | | | | | |
+| R-7.6-001 | R-7.6-002 | R-7.6-003 | R-7.6-004 | R-7.6-005 | R-7.6-006 |
+| R-7.6-007 | R-7.6-008 | R-7.6-009 | | | |
+| 7.7 Communication types based on priorities | | | | | |
+| NA | | | | | |
+| 7.7.1 MCX Service Emergency Group Communication requirements | | | | | |
+| NA | | | | | |
+| 7.7.2 MCX Service Emergency Group Communication cancellation requirements | | | | | |
+| NA | | | | | |
+| 7.7.3 Imminent Peril Communication | | | | | |
+| NA | | | | | |
+
+| | | | | | |
+|-----------------------------------------------------------------------------|--------------|--------------|--------------|-------------|-------------|
+| 7.7.3.1 Imminent Peril Group Communication requirements | | | | | |
+| NA | | | | | |
+| 7.7.3.2 Imminent Peril Group Communication cancellation requirements | | | | | |
+| NA | | | | | |
+| 7.8 Location | | | | | |
+| R-7.8-001 | R-7.8-002 | R-7.8-003 | | | |
+| 7.9 Security | | | | | |
+| R-7.9-001 | R-7.9-002 | | | | |
+| 7.10 Off-network MCX Service operations | | | | | |
+| R-7.10-001 | R-7.10-002 | R-7.10-003 | | | |
+| 7.11 Off-network UE functionality | | | | | |
+| R-7.11-001 | R-7.11-002 | R-7.11-003 | | | |
+| 7.12 Streaming for ProSe UE-to-UE Relay and UE-to-Network Relay | | | | | |
+| NA | | | | | |
+| 7.12.1 UE-to-Network Relay for all data types | | | | | |
+| R-7.12.1-001 | R-7.12.1-002 | R-7.12.1-003 | R-7.12.1-004 | | |
+| 7.12.2 UE-to-UE Relay streaming | | | | | |
+| R-7.12.2-001 | R-7.12.2-002 | R-7.12.2-003 | | | |
+| 7.12.3 Off-Network streaming | | | | | |
+| R-7.12.3-001 | R-7.12.3-002 | R-7.12.3-003 | | | |
+| 7.13 Switching to off-network MCX Service | | | | | |
+| R-7.13-001 | R-7.13-002 | R-7.13-003 | R-7.13-004 | R-7.13-005 | |
+| 7.14 Off-network recording and audit requirements | | | | | |
+| R-7.14-001 | R-7.14-001a | R-7.14-002 | R-7.14-002a | | |
+| 7.15 Off-network UE-to-UE relay | | | | | |
+| NA | | | | | |
+| 7.15.1 Private Communications | | | | | |
+| R-7.15.1-001 | R-7.15.1-002 | R-7.15.1-003 | | | |
+| 7.16 Off-network Ad hoc Group Communication | | | | | |
+| R-7.16-001 | | | | | |
+| 7.15.2 Group Communications | | | | | |
+| R-7.15.2-001 | R-7.15.2-002 | | | | |
+| 8 Inter-MCX Service interworking | | | | | |
+| NA | | | | | |
+| 8.1 Inter-MCX Service interworking overview | | | | | |
+| NA | | | | | |
+| 8.2 Concurrent operation of different MCX Services | | | | | |
+| NA | | | | | |
+| 8.2.1 Overview | | | | | |
+| NA | | | | | |
+| 8.2.2 Requirements | | | | | |
+| R-8.2.2-001 | R-8.2.2-002 | R-8.2.2-003 | R-8.2.2-004 | R-8.2.2-005 | R-8.2.2-006 |
+| R-8.2.2-007 | | | | | |
+| 8.3 Use of unsharable resources within a UE | | | | | |
+| R-8.3-001 | R-8.3-002 | R-8.3-003 | R-8.3-004 | R-8.3-005 | R-8.3-006 |
+| 8.4 Single Group with multiple MCX Services | | | | | |
+
+| | | | | | |
+|-----------------------------------------------------------|---------------|---------------|---------------|-------------|--|
+| NA | | | | | |
+| 8.4.1 Overview | | | | | |
+| NA | | | | | |
+| 8.4.2 Requirements | | | | | |
+| R-8.4.2-001 | R-8.4.2-002 | R-8.4.2-003 | R-8.4.2-004 | R-8.4.2-005 | |
+| 8.4.3 Compatibility of UE | | | | | |
+| NA | | | | | |
+| 8.4.3.1 Advertising service capabilities required | | | | | |
+| R-8.4.3.1-001 | R-8.4.3.1-002 | R-8.4.3.1-003 | R-8.4.3.1-004 | | |
+| 8.4.3.2 Conversion between capabilities | | | | | |
+| R-8.4.3.2-001 | | | | | |
+| 8.4.4 Individual permissions for service access | | | | | |
+| R-8.4.4-001 | | | | | |
+| 8.4.5 Common alias and user identities or mappable | | | | | |
+| R-8.4.5-001 | | | | | |
+| 8.4.6 Single location message | | | | | |
+| R-8.4.6-001 | R-8.4.6-002 | R-8.4.6-003 | | | |
+| 8.5 Priority between services | | | | | |
+| NA | | | | | |
+| 8.5.1 Overview | | | | | |
+| NA | | | | | |
+| 8.5.2 Requirements | | | | | |
+| R-8.5.2-001 | R-8.5.2-002 | R-8.5.2-003 | R-8.5.2-004 | R-8.5.2-005 | |
+| 9 Air Ground Air Communications | | | | | |
+| NA | | | | | |
+| 9.1 Service description | | | | | |
+| NA | | | | | |
+| 9.2 Requirements | | | | | |
+| R-9.2-001 | | | | | |
+| 10 MCX Service in IOPS mode | | | | | |
+| R-10-001 | | | | | |
+
+---
+
+## Annex D (informative): Characteristics and traffic assumptions for air ground air communications
+
+The mission critical air ground air communications will be used as described below.
+
+---
+
+### D.1 Environment
+
+Helicopters are used for rescue and providing reconnaissance information to support events/incidents in rural (including mountains) environments and urban environments. Helicopters are also used for rescue and providing reconnaissance support for events/incidents in the ocean within a limited range of land or ship.
+
+Planes are often used in rural (including forests and mountains) environment, but they can also be used in and near urban areas.
+
+## D.2 Altitudes
+
+Helicopters have an altitude of 1.500 ft in general but in mountains it goes up to 15.000 ft.
+
+Planes have an altitude between 2.000 ft and 15.000 ft.
+
+The system will have to operate from 500 ft above ground level/above the sea with service continuity between ground communications and air ground air communications.
+
+## D.3 Maximum speed and mobility
+
+Helicopters are moving at a speed of 250 km/h, planes are moving at 450 km/h. The ascent and descent speed are up to 1.000 ft per minute.
+
+## D.4 Traffic assumptions
+
+For a region of 90.000 km2, a minimum of 18 communications per regions are supported with at least 6 simultaneous communications for helicopters and at least 6 simultaneous communications for planes.
+
+## Annex E (informative): Variables
+
+**Table E.1: List of variables**
+
+| Variable | Meaning | Reference |
+|----------|---------------------------------------------------------------------------------|--------------------------|
+| Bc1 | Number of levels of group hierarchy within an MCX Service | 5.2.2 |
+| Bc2 | Number of levels of user hierarchy within an MCX Service | 5.2.3 |
+| | | |
+| Nc1 | Number of receiving members present for an MCX Group. | 6.4.2 |
+| Nc2 | Total number of MCX Groups that an MCX User can be affiliated to simultaneously | 5.1.5 |
+| Nc3 | Minimum length of alphanumeric identifiers (i.e., Alias ID) | 5.7, 6.4.3, 7.1, and 7.2 |
+| Nc4 | Number of simultaneous MCX Group communications received by an MCX UE | 5.4.2 |
+| Nc5 | Number of simultaneous MCX Group communications received by a user | 5.4.2 |
+| Nc6 | Total number of MCX Group Members of an MCX Group | 6.1 |
+
+## Annex F (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-73 | SP-160543 | S1-162406 | 22.280 | 0001 | 1 | Rel-14 | F | Corrections to referenced sub-clauses in Annex B and Annex C | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162407 | 22.280 | 0003 | 1 | Rel-14 | D | Add an Informative Annex table in MCCoRe TS 22.280 with a List of Variables used | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162403 | 22.280 | 0004 | 1 | Rel-14 | F | Add definitions for participant and participant type to MCCoRe TS 22.280 sub-clause 3.1. | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162019 | 22.280 | 0005 | | Rel-14 | D | Editorial changes to MCCoRe TS 22.280 Informative Annex D sub-clause D.1 | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162020 | 22.280 | 0006 | | Rel-14 | F | In MCCoRe TS 22.280 provide changes to References 1, 2, and 3 in clause 2. | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162408 | 22.280 | 0007 | 1 | Rel-14 | D | Provide editorial changes to several sub-clauses in MCCoRe TS 22.280 for consistency and to improve understanding and readability.
MCC Note: 25 th change (removing Annexes a, B and C) not implemented since contradicting other CRs (i.e. CR#0001r1, 0008r2, 0010r1, 0012r1 and 0021r1) | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162497 | 22.280 | 0008 | 2 | Rel-14 | C | In MCCoRe TS 22.280 provide editorial changes to the service description in sub-clause 6.19.1 Call rejection and queuing. | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162036 | 22.280 | 0009 | | Rel-14 | B | In MCCoRe TS 22.280 Add a requirement in sub-clause 8.4.2 Requirements for a single group with multiple MCX Services. | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162266 | 22.280 | 0010 | 1 | Rel-14 | B | In MCCoRe TS 22.280 Add sub-clause 7.4 requirements to normative Annex C MCCoRe Requirements for MCData. | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162410 | 22.280 | 0012 | 1 | Rel-14 | F | Insertion of new clause 5.5.2 with requirement [R-5.1.8-002] from clause 5.1.8 | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162411 | 22.280 | 0013 | 1 | Rel-14 | F | Corrections to Clause 4.2 | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162124 | 22.280 | 0014 | | Rel-14 | F | Correction of inconsistency between header 6.7 and overview text 6.7.1 | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162125 | 22.280 | 0015 | | Rel-14 | F | Correction to clause 5.1.1 requirement [R-5.1.1-005] | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162412 | 22.280 | 0016 | 1 | Rel-14 | F | Clarification of text in clause 5.4.1 | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162127 | 22.280 | 0017 | | Rel-14 | F | Clarification of text in clause 5.6.1 | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162413 | 22.280 | 0018 | 1 | Rel-14 | F | Moving of informative text within requirements to NOTEs | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162414 | 22.280 | 0019 | 1 | Rel-14 | F | Correction [R-7.12.3-003] | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162415 | 22.280 | 0020 | 1 | Rel-14 | F | Correction of the entity that affiliates | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162416 | 22.280 | 0021 | 1 | Rel-14 | F | Single requirement label [R-5.6.2.4.1-004] with two requirements | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162132 | 22.280 | 0022 | | Rel-14 | F | Corrections to definitions | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-73 | SP-160543 | S1-162401 | 22.280 | 0023 | 1 | Rel-14 | F | Corrections to Group Regroup triggered by the need to support of Audio Cut-in capability | 14.0.0 | 14.1.0 | MCImp-MCCoRe |
+| SP-74 | SP-160891 | S1-163008 | 22.280 | 0024 | | Rel-14 | F | Corrections to referenced sub- | 14.1.0 | 14.2.0 | MCImp- |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|--------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------------|
+| | | | | | | | | clauses in Annex C | | | MCCoRe |
+| SP-74 | SP-160891 | S1-163009 | 22.280 | 0025 | | Rel-14 | D | Editorial changes to 3 sub-clauses | 14.1.0 | 14.2.0 | MCImp-MCCoRe |
+| SP-74 | SP-160891 | S1-163010 | 22.280 | 0026 | | Rel-14 | D | Provide editorial changes to the service description in sub-clause 6.19.1 Communication rejection and queuing for readability. | 14.1.0 | 14.2.0 | MCImp-MCCoRe |
+| SP-75 | SP-170150 | S1-170191 | 22.280 | 0027 | 1 | Rel-14 | F | Corrections to requirement references in the applicability annexes | 14.2.0 | 14.3.0 | MCImp-MCCoRe |
+| SP-75 | SP-170150 | S1-171025 | 22.280 | 0030 | | Rel-14 | F | Correct inconsistent use of the term 'one-to-many' | 14.2.0 | 14.3.0 | MCImp-MCCoRe |
+| SP-76 | SP-170445 | S1-172428 | 22.280 | 0031 | 7 | Rel-15 | B | FRMCS Role management and presence | 14.3.0 | 15.0.0 | MONAST ERY |
+| SP-77 | SP-170696 | S1-173361 | 22.280 | 0042 | 1 | Rel-15 | F | Correction to requirement on usage of ulisted functional alias | 15.0.0 | 15.1.0 | MONAST ERY |
+| SP-77 | SP-170696 | S1-173362 | 22.280 | 0043 | 1 | Rel-15 | C | update requirement for functional alias | 15.0.0 | 15.1.0 | MONAST ERY |
+| SP-77 | SP-170696 | S1-173510 | 22.280 | 0045 | 2 | Rel-15 | C | update requirement for functional alias | 15.0.0 | 15.1.0 | MONAST ERY |
+| SP-78 | SP-170985 | S1-174042 | 22.280 | 0046 | | Rel-15 | F | Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards | 15.1.0 | 15.2.0 | MCOVer |
+| SP-78 | SP-170997 | S1-174419 | 22.280 | 0047 | 2 | Rel-16 | B | Priority controlled by MCX User for receiving from Multiple MCX service Communication | 15.1.0 | 16.0.0 | MONAST ERY2 |
+| SP-78 | SP-170997 | S1-174425 | 22.280 | 0049 | 3 | Rel-16 | B | Changes relating to the User regrouping section of 22.280 | 15.1.0 | 16.0.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180037 | 22.280 | 0053 | | Rel-16 | B | Enhanced control of User Regroup and Private Communication | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180436 | 22.280 | 0057 | 1 | Rel-16 | F | Clarification of definition of Mission Critical Service in 22.280 | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180439 | 22.280 | 0060 | 1 | Rel-16 | B | Changes related to membership/affiliation section of 22.280 | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180564 | 22.280 | 0054 | 3 | Rel-16 | B | Adding more functionality to interworking between FRMCS and GSM-R | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180565 | 22.280 | 0055 | 5 | Rel-16 | C | Functional Alias enhancements(chapter 5.9a) | 16.0.0 | 16.1.0 | FS_FRMC S2 |
+| SP-79 | SP-180134 | S1-180568 | 22.280 | 0056 | 2 | Rel-16 | B | Introduction of railway emergency alert functionality to 22.280 | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180583 | 22.280 | 0061 | 2 | Rel-16 | B | Changes related to administrative sections of 22.280 | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-79 | SP-180134 | S1-180612 | 22.280 | 0059 | 3 | Rel-16 | B | Query of location based on functional alias | 16.0.0 | 16.1.0 | MONAST ERY2 |
+| SP-80 | SP-180306 | S1-181704 | 22.280 | 0083 | 2 | Rel-16 | A | Generalisation of EPS into 3GPP system | 16.1.0 | 16.2.0 | MCOVer |
+| SP-80 | SP-180307 | S1-181385 | 22.280 | 0063 | 1 | Rel-16 | A | User profile presentation priority | 16.1.0 | 16.2.0 | MCImp-MCCoRe |
+| SP-80 | SP-180310 | S1-181582 | 22.280 | 0071 | 2 | Rel-16 | C | chapter_5_10 MCX User log in to multiple devices | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181588 | 22.280 | 0074 | 2 | Rel-16 | F | Interworking between MCX Service system and GSM-R | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181589 | 22.280 | 0070 | 2 | Rel-16 | B | Addition of location based communication depending on functional alias | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181590 | 22.280 | 0069 | 2 | Rel-16 | B | Adding authorization for private communication based on functional alias | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181617 | 22.280 | 0082 | 2 | Rel-16 | B | Add a requirement on 5.11 Location | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181700 | 22.280 | 0073 | 4 | Rel-16 | B | Extension of functional alias chapter 5.9a | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181705 | 22.280 | 0064 | 4 | Rel-16 | B | Addition of location functionality for autonomous train control and operation | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-80 | SP-180310 | S1-181706 | 22.280 | 0065 | 4 | Rel-16 | F | Off-network UE functionality for virtual coupling | 16.1.0 | 16.2.0 | MONAST ERY2 |
+| SP-81 | SP-180757 | S1-182255 | 22.280 | 0089 | | Rel-16 | F | Public emergency calls | 16.2.0 | 16.3.0 | MONAST ERY2 |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|-------------------------------------------------------------------|--------|--------|----------------|
+| SP-81 | SP-180757 | S1-182561 | 22.280 | 0084 | 1 | Rel-16 | B | Dynamic Group Participation | 16.2.0 | 16.3.0 | MONAST
ERY2 |
+| SP-81 | SP-180757 | S1-182580 | 22.280 | 0090 | 1 | Rel-16 | F | Clarification of requirement R-6.4.9-001 | 16.2.0 | 16.3.0 | MONAST
ERY2 |
+| SP-81 | SP-180757 | S1-182581 | 22.280 | 0088 | 2 | Rel-16 | B | Selection of Application Layer Priorities by the MCX Service user | 16.2.0 | 16.3.0 | MONAST
ERY2 |
+| SP-81 | SP-180761 | S1-182614 | 22.280 | 0085 | 1 | Rel-16 | B | Application of MCX Services to maritime usage | 16.2.0 | 16.3.0 | MARCOM |
+
+| Change history | | | | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | | | | New version |
+| 2018-12 | SP-82 | SP-180999 | 0091 | 1 | B | Requirement to allow for users to automatically be informed when affiliation information changes in a group | | | | | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0094 | 1 | B | Move interworking of functional alias from MCPTT to MCCoRe TS, MCCoRe part | | | | | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0097 | 1 | B | Interworking among MCX Service systems | | | | | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0101 | 1 | F | Dynamic Group Participation | | | | | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0099 | 2 | B | Unique addressing of MCX Users when using functional alias | | | | | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0098 | 2 | B | Additional requirements for the use of a gateway UE | | | | | 16.4.0 |
+| 2018-12 | SP-82 | SP-181000 | 0096 | 1 | C | Changes to recording and audit metadata | | | | | 16.4.0 |
+| 2019-03 | SP-83 | SP-190079 | 0107 | 3 | F | Clarification for discreet listening | | | | | 16.5.0 |
+| 2019-03 | SP-83 | SP-190084 | 0102 | 1 | C | Group regrouping additional requirements | | | | | 16.5.0 |
+| 2019-06 | SA#84 | SP-190313 | 0110 | 1 | C | Add new capabilities for late communication entry | | | | | 17.0.0 |
+| 2019-06 | SA#84 | SP-190313 | 0111 | 2 | C | Deactivation of an unlisted functional alias and deactivation status | | | | | 17.0.0 |
+| 2019-06 | SA#84 | SP-190313 | 0108 | 2 | C | Enhance metadata to be logged for Railway post-incident analysis | | | | | 17.0.0 |
+| 2019-09 | SA#85 | SP-190799 | 0133 | 1 | A | Additional broadcast regroup requirements | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190799 | 0120 | 1 | B | Additional broadcast regroup requirements -> ignored (identical to the CR#0133r1 just above) | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190799 | 0129 | 2 | A | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190813 | 0122 | 1 | C | Support the FRMCS use case for Arbitration when a user is registered to multiple UEs | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190813 | 0127 | 1 | F | Extend Functional Alias binding to MCX Service Private Communication | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190813 | 0131 | 1 | B | Support the location services related use cases while operating in off-network mode | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190813 | 0121 | 2 | C | Activate Location Information report of a specific FA in a certain area | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190813 | 0126 | 1 | F | Clarify routing location dependent communications as part of handling MCX Service Private Communication requests | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190813 | 0132 | 2 | B | Support the recording of communication related use cases while operating in off-network mode | | | | | 17.1.0 |
+| 2019-09 | SA#85 | SP-190804 | 0134 | 1 | F | New additional broadcast regroup requirements | | | | | 17.1.0 |
+| 2019-12 | SA#86 | SP-191030 | 0138 | 2 | C | Clarification on interworking between FRMCS System and Public Networks | | | | | 17.2.0 |
+| 2019-12 | SA#86 | SP-191030 | 0137 | 1 | D | Editorial correction to broadcast regroup requirements | | | | | 17.2.0 |
+| 2020-07 | SA#88e | SP-200560 | 0140 | 3 | A | Clarification on the maximum number limit of simultaneous log ins of an MCX user | | | | | 17.3.0 |
+| 2020-07 | SA#88e | SP-200560 | 0141 | | F | Addition of a per-MCX user log-in limit | | | | | 17.3.0 |
+| 2020-12 | SA#90e | SP-201029 | 143 | 1 | B | Enhancement to MCX User request queue operation | | | | | 17.4.0 |
+| 2021-03 | SA#91e | SP-210199 | 144 | 1 | B | Gateway MCX UE identification | | | | | 17.5.0 |
+| 2021-06 | SA#92e | SP-210499 | 0145 | 1 | C | Enhancement of MCX UE de-affiliation requirements | | | | | 17.6.0 |
+| 2021-09 | SA#93e | SP-211036 | 0147 | | F | Correction - Adding missing requirements into tables in the normative Annexes | | | | | 17.7.0 |
+| 2021-09 | SA#93e | SP-211061 | 0146 | 1 | B | Sharing administrative configuration between Mission Critical Organizations (SACI MCS) | | | | | 18.0.0 |
+| 2021-09 | SA#93e | SP-211074 | 0148 | 2 | B | Ad hoc group call requirements (AHGC) | | | | | 18.0.0 |
+| 2022-03 | SP#95e | SP-220082 | 0149 | | C | Enhanced MCX Service Ad hoc Group Communication to support Railway needs | | | | | 18.1.0 |
+| 2022-06 | SA#96 | SP-220434 | 152 | 1 | F | Call restriction based on subparts/elements of functional alias | | | | | 18.2.0 |
+| 2022-06 | SA#96 | SP-220434 | 153 | 1 | F | Additional parameters for Location Information and clarification of Location terms | | | | | 18.2.0 |
+| 2022-06 | SA#96 | SP-220434 | 154 | 1 | F | Enhanced MCX Service Ad hoc Group Communication to support Railway needs | | | | | 18.2.0 |
+| 2023-03 | SA#99 | SP-230218 | 0158 | 1 | B | Introduction of MCX Service Ad hoc Group Emergency Alert | | | | | 18.3.0 |
+| 2023-06 | SA#100 | SP-230526 | 0161 | 3 | C | Notification of updated list of participants of Ad hoc Group Emergency Alert | | | | | 18.4.0 |
+| 2023-12 | SA#102 | SP-231395 | 0167 | 2 | C | Enhancement of MCX Service Ad hoc Group Emergency Alert and Ad hoc Group Communications for railways | | | | | 18.5.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22281/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22281/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a5d0457cf580558a227300f96055b52797f78ab
--- /dev/null
+++ b/marked/Rel-18/22_series/22281/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b153ef2ca0948e29b02d3b0024df70a0ebc28c81edec80829811e513d9285e5
+size 9586
diff --git a/marked/Rel-18/22_series/22281/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22281/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4508bd26743b17c17d0474a0edda67aa7322a7c8
--- /dev/null
+++ b/marked/Rel-18/22_series/22281/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd588310f251c34d004323e9407f1dd5be739ceb9ac4beb8829e82b8f3a34c6e
+size 7248
diff --git a/marked/Rel-18/22_series/22281/raw.md b/marked/Rel-18/22_series/22281/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..83eaa7c2adbf01f31768321afc6dd87786585808
--- /dev/null
+++ b/marked/Rel-18/22_series/22281/raw.md
@@ -0,0 +1,1175 @@
+
+
+# 3GPP TS 22.281 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Video services (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## Keywords ---
+
+Mission, Critical, Video
+
+## **3GPP**
+
+## Postal address ---
+
+## 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet ---
+
+
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Overview..... | 8 |
+| 4.1 Description of the MCVideo service..... | 8 |
+| 4.2 Comparison with the MCPTT service..... | 9 |
+| 4.3 Video surveillance..... | 9 |
+| 4.4 Group Management/ Communication and Affiliation ..... | 9 |
+| 4.5 Security..... | 10 |
+| 4.6 Confidentiality:..... | 10 |
+| 4.7 User identities and inter-working between MCServices..... | 10 |
+| 4.8 Non video aspects of the MCVideo service..... | 10 |
+| 4.8.1 Relationship with other MCServices..... | 10 |
+| 4.8.2 Camera control ..... | 11 |
+| 4.8.3 Location ..... | 11 |
+| 4.8.4 Emergency Alert..... | 11 |
+| 4.9 Video codecs ..... | 11 |
+| 5 MCVideo specific requirements ..... | 11 |
+| 5.1 MCVideo services common for on network and off network..... | 11 |
+| 5.1.1 Video characteristics ..... | 11 |
+| 5.1.1.1 Operational recommendations and requirements for video codecs for the MCVideo service ..... | 11 |
+| 5.1.1.2 End-user criteria and requirements for the selection of a video codec for MCVideo service..... | 13 |
+| 5.1.1.3 Video modes ..... | 13 |
+| 5.1.1.3.1 Description ..... | 13 |
+| 5.1.1.3.2 Requirements..... | 13 |
+| 5.1.2 Video parameters remote control ..... | 13 |
+| 5.1.2.1 Remote modification of real time video quality ..... | 13 |
+| 5.1.2.1.1 Service description ..... | 13 |
+| 5.1.2.1.2 Requirements..... | 14 |
+| 5.1.2.2 Video capabilities information management ..... | 14 |
+| 5.1.2.2.1 Service description ..... | 14 |
+| 5.1.2.2.2 Requirements..... | 14 |
+| 5.1.3 Video remote control including camera discovery..... | 15 |
+| 5.1.3.1 Remote camera control ..... | 15 |
+| 5.1.3.1.1 Service description ..... | 15 |
+| 5.1.3.1.2 Requirements..... | 15 |
+| 5.1.3.2 Camera discovery ..... | 15 |
+| 5.1.3.2.1 Service description ..... | 15 |
+| 5.1.3.2.2 Requirements..... | 15 |
+| 5.1.3.3 Communications remote control..... | 16 |
+| 5.1.3.3.1 Service description ..... | 16 |
+| 5.1.3.3.2 Requirements..... | 16 |
+| 5.1.4 Video processing capabilities ..... | 16 |
+| 5.1.4.1 Service description..... | 16 |
+| 5.1.4.2 Requirements ..... | 16 |
+| 5.1.5 Robots video remote control ..... | 16 |
+| 5.1.5.1 Service description..... | 16 |
+| 5.1.5.2 Requirements ..... | 17 |
+| 5.1.6 MCVideo Profile management and administration..... | 17 |
+| 5.1.6.1 Service description..... | 17 |
+| 5.1.6.2 Requirements ..... | 17 |
+
+| | | |
+|-----------|-------------------------------------------------------------------|----|
+| 5.1.7 | Capabilities additional to MCCoRe..... | 18 |
+| 5.1.7.1 | Leaving and rejoining an in progress video communication..... | 18 |
+| 5.1.7.1.1 | Service description ..... | 18 |
+| 5.1.7.1.2 | Requirements..... | 18 |
+| 5.1.8 | MCVideo capability information sharing..... | 18 |
+| 5.1.8.1 | Service description..... | 18 |
+| 5.1.8.2 | Requirements ..... | 18 |
+| 5.1.9 | Video push and pull services..... | 18 |
+| 5.1.9.1 | Video pull service ..... | 18 |
+| 5.1.9.1.1 | Service description ..... | 18 |
+| 5.1.9.1.2 | Requirements..... | 19 |
+| 5.1.9.2 | Video push service..... | 19 |
+| 5.1.9.2.1 | Service description ..... | 19 |
+| 5.1.9.2.2 | Requirements..... | 19 |
+| 5.1.10 | Video streams availability and characteristics..... | 19 |
+| 5.1.10.1 | Service description..... | 19 |
+| 5.1.10.2 | Requirements ..... | 20 |
+| 5.1.11 | Video conferencing ..... | 20 |
+| 5.1.11.1 | Service description..... | 20 |
+| 5.1.11.2 | Requirements ..... | 20 |
+| 5.1.12 | Additional security requirements for MCVideo..... | 21 |
+| 5.1.12.1 | General..... | 21 |
+| 5.1.12.2 | Requirements ..... | 21 |
+| 5.2 | MCVideo services requirements specific to on-network use..... | 21 |
+| 5.2.1 | Video availability notification..... | 21 |
+| 5.2.1.1 | Service description..... | 21 |
+| 5.2.1.2 | Requirements ..... | 21 |
+| 5.2.2 | Replay of stored video..... | 22 |
+| 5.2.2.1 | Service description..... | 22 |
+| 5.2.2.2 | Requirements ..... | 22 |
+| 5.2.3 | Video storage control ..... | 22 |
+| 5.2.3.1 | Service description..... | 22 |
+| 5.2.3.2 | Requirements ..... | 22 |
+| 5.2.4 | Capabilities additional to MCCoRe..... | 22 |
+| 5.2.4.1 | Service description..... | 22 |
+| 5.2.4.2 | Requirements ..... | 22 |
+| 5.2.5 | Video control by a dispatcher ..... | 22 |
+| 5.2.5.1 | Service description..... | 22 |
+| 5.2.5.2 | Requirements ..... | 23 |
+| 5.2.6 | Transmission control ..... | 23 |
+| 5.2.6.1 | Overview..... | 23 |
+| 5.2.6.2 | Transmission control requirements..... | 23 |
+| 5.2.6.2.1 | General ..... | 23 |
+| 5.2.6.2.2 | Receiving video streams..... | 24 |
+| 5.2.6.2.3 | Entering an ongoing video stream..... | 25 |
+| 5.2.6.2.4 | Video streams reconfiguration and termination ..... | 25 |
+| 5.2.7 | Override ..... | 25 |
+| 5.2.7.1 | Overview..... | 25 |
+| 5.2.7.2 | General aspects ..... | 25 |
+| 5.2.8 | Communication termination..... | 26 |
+| 5.3 | MCVideo services requirements specific to off-network use ..... | 27 |
+| 5.3.1 | Private Communication Off-Network ..... | 27 |
+| 5.3.1.1 | Overview..... | 27 |
+| 5.3.1.2 | Private Communication Off-Network general requirements ..... | 27 |
+| 5.3.1.3 | Private Communication Off-Network commencement requirements ..... | 27 |
+| 5.3.1.4 | Private Communication Off-Network termination ..... | 28 |
+| 5.3.1.5 | Private Communication Off-Network administration ..... | 28 |
+| 5.3.2 | MCVideo Transmission Control Off-Network ..... | 28 |
+| 5.3.2.1 | Overview..... | 28 |
+| 5.3.2.2 | General Aspects ..... | 28 |
+| 5.3.2.3 | Requesting Permission to Transmit ..... | 28 |
+| 5.3.2.4 | Override ..... | 29 |
+
+5.3.2.5 Terminating Permission to Transmit ..... 29
+5.3.2.6 Transmit Time Limit..... 29
+5.4 Performance and quality requirements for on-network and off-network..... 30
+5.4.1 MCVideo device and camera moving at high speed..... 30
+5.4.1.1 Service description..... 30
+5.4.1.2 Requirements ..... 30
+5.4.2 Latencies..... 30
+6 Interworking..... 30
+6.1 Interworking with non 3GPP video systems ..... 30
+**Annex A (informative): Change history..... 31**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document provides the service requirements for operation of the MCVideo service. MCVideo makes use of capabilities included in Group Communication System Enablers, Proximity Services, Isolated E-UTRAN operation for Public Safety and Mission Critical Services Common Requirements with additional requirements specific to the MCVideo Service. The MCVideo Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g. utility companies, railways and maritime usage). The requirements in this specifications do not apply to GSM or UMTS.
+
+# --- 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] Void.
+- [3] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
+- [4] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT); Stage 1".
+- [5] 3GPP TS 22.282: "Mission Critical Data services".
+- [6] ITU-T Recommendation H.264: Advanced video coding for generic audiovisual services, v2, 2016".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**MCVideo Quality:** a measure of the distortion or artefacts in a video signal which impacts the ability of a Mission Critical Organisation to utilise the video for its intended purpose. For example if the purpose of the video is to capture license plates on vehicles in a range of outdoor conditions, video quality is measured in the ability of the video outputs to provide the specific information across a range of environmental conditions.
+
+**Real Time:** Of or relating to systems that update information at the same rate as they receive data, enabling them to direct or control a process such as video recording and display. Sometimes referred to as live or real life timing of events.
+
+**Real-Time Video:** Video viewed at the same time it is being shot.
+
+**Robot:** A machine that can perform a task automatically or via remote control such as an unmanned vehicle that can be aerial (e.g., Unmanned aerial vehicle (UAV), aerial drone), aquatic (e.g., unmanned surface vehicle (USV)), submarine, (e.g., unmanned underwater vehicles (UUV), underwater drone) or terrestrial (unmanned ground vehicle (UGV)).
+
+NOTE: Unmanned vehicles typically have a set of sensors to observe the environment, and either autonomously make decisions about their behavior or pass the information to a human operator at a different location who controls the vehicle through teleoperation.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|---------|-----------------------------------------------|
+| IOPS | Isolated E-UTRAN Operation for Public Safety |
+| MCCoRe | Mission Critical Services Common Requirements |
+| MCData | Mission Critical Data |
+| MCPTT | Mission Critical Push to Talk |
+| MCVideo | Mission Critical Video |
+| PTZ | Pan-Tilt-Zoom |
+| TVNP | TV Network Protocol |
+
+# --- 4 Overview
+
+## 4.1 Description of the MCVideo service
+
+MCVideo defines a service for Mission Critical video communication using 3GPP transport networks. Mission Critical refers to meeting the needs of agencies providing Public Safety services such as, but not limited to, Police, Fire and Ambulance services. Those needs include high reachability, availability and reliability of the service, low latency, real-time operating capabilities, highly secured operations, inter-operability with other services and systems, private and group communications, handling of emergencies and ability to provide prioritization, pre-emption, queuing and QoS. Although the service is designed for transport over commercial and dedicated 3GPP networks it is not expected to be limited to use over 3GPP networks. However, performance over other transport networks has not been considered when producing this document.
+
+MCVideo service includes:
+
+- Video capture and encoding of the video information;
+- Secure streaming and storing of the video information;
+- Video decoding and rendering of the video information;
+- Processing of the video information, including the ability to annotate video frames and recognize video features;
+- Mission critical and public safety level functionality (e.g. group sessions, affiliations, end-to-end confidentiality, emergency type communications) and performance (e.g. low latency);
+- Transmission and control of the parameters relevant to those functions;
+- Secure operation such that video information can be reasonably un-impeachable when used in evidentiary procedures;
+- Definition and configuration of MCVideo groups and applications;
+- Configuration of the MCVideo users' profiles and of the MCVideo UEs; and
+- Interoperability with other services and systems.
+
+While the streaming of video is part of the MCVideo Service, the non-real-time or offline transfer of a video clip stored as a file containing video data is covered by the MCData Service as defined in 3GPP TS 22.282 [5].
+
+An MCVideo video stream can be associated with a stand alone MCVideo group of users, or can be one of the streams of a multi-media MCX Service group.
+
+An MCVideo UE is a device that provides video acquisition (e.g. has a camera), video rendering (has a display) or both and normally also has some encoding / decoding, communication and storage capabilities.
+
+## 4.2 Comparison with the MCPTT service
+
+MCVideo makes use of many of the same capabilities that were originally defined for MCPTT in 3GPP TS 22.179 [4] and now are mostly specified at stage 1 in the MCCoRe specification [3]. Such capabilities include, but are not limited to, Group Communication, Group Management, Affiliation, Security and Confidentiality. The MCVideo service also allows the same user to have multiple user profiles defined and to simultaneously use multiple UEs.
+
+However, the MCVideo Service also differs from MCPTT in some respects. In MCPTT there is a specific way of floor control to assert good order and appropriate use of priority to control and manage situations where multiple users in a group might attempt to speak at the same time. Simultaneous speech can degrade intelligibility of communications. The role of floor control is to manage who can transmit at a point in time and who will have to wait to speak to the group. In MCVideo the control approach is more varied. There is admission control to manage the appropriate access to network resources according to the user's priority and the UE's capabilities. In some cases, this may include control to restrict simultaneous video being sent from different users in the group (likely to be useful for network capacity/UE limitations). From a user perspective there is not the same need to restrict multiple simultaneous transmission and presentation of video within the same group, as if different streams are available at the UE then the user could choose which, to look at them simultaneously. It is assumed that users that are permitted to transmit video are generally allowed to send video to a group, unless there is a network capacity/UE restriction rule that places limitations on the number of videos to that group. In this case users would be trained in appropriate use of that choice.
+
+The point at which video is transmitted to a group may vary, e.g. a user may press to send video and wait until allowed by the network to stream to the affiliated group according to the admission control policy. However, the user may be able to "force" the immediate transmission of the video information, for example, by pressing and holding the button to send video. In this case the UE will take immediate action to capture the video for onward transmission as soon as permitted. Also the UE will communicate the immediate nature of the video to the network, which may choose to authorise the access and then locally store it for onward transmission or stream it immediately to the relevant group. In this case the video may be slightly delayed due to the start up delay. It is also possible for the user to mark their video communication as Emergency or Imminent Peril and this will immediately elevate the priority of video communications for this group above non emergency video.
+
+A further way that MCVideo differs from MCPTT is that group members may be configured not to automatically receive video. Video may be streamed up to the network and users invited to join when/if convenient/appropriate for them or only if they have access to a multicast enabled device. An example might be where a Police Officer driving to an incident is not able to view a video of the events unfolding, but his partner in the car can usefully receive and view the video. In this case MCVideo working together with MCPTT will provide a powerful solution to know which videos to receive for those best placed to receive them. This user reception function might be used to late join a video stream or with the store and forward capability for video.
+
+## 4.3 Video surveillance
+
+Surveillance cameras could also use the MCVideo service in which case, in addition to the existing video storage and monitoring activity already used for the surveillance camera, authority may be given to users in the MCVideo system to connect to, control receive and forward video either to an individual or to a group. Surveillance includes the ability to locally and remotely activate video streaming automatically or on demand, to control the positioning, optical and video parameters of the camera and to recognize video features. The camera may be exclusively in the MCVideo system, or it may be accessed by connection from the MCVideo Service via an existing external interface for surveillance camera networks. In this latter case, the external interface is expected to provide requests for control and onward streaming of video, which will be managed together with the normal control network for those cameras. This external interface is outside of the control of 3GPP and existing standards may be used for part or all of the functionality of this interface e.g. TVNP.
+
+## 4.4 Group Management/ Communication and Affiliation
+
+MCVideo group communication aspects are very similar to MCPTT. Each user may be a member of several, even many, groups. Membership is determined by administration control and provides a user identity based level of authority to join a group. Each user chooses to affiliate to the groups that they want to receive video communication from. Once a
+
+user has successfully affiliated to a group they will begin to receive video communications directed to that group according to the video distribution approach used. A user who wishes to send video to a group shall select the relevant group and then they may send video to it.
+
+Groups may interwork with other MCX Service groups, so a single group could be configured for MCPTT and MCVideo and any other combination of MCX Services. The present document does not describe how that is managed, it could be a single group with a single affiliate message and separate attributes for each service or it may be different groups managed together by administrator control and linked in the UE to allow single user action to trigger the same action e.g. affiliate, for each relevant service. It shall be possible for services actions to be taken independently because some UE may not be capable of all of the linked services and some users may not be given access to some services or some groups for some services.
+
+## 4.5 Security
+
+All MCVideo communications, video and supporting signalling and messaging which start and end entirely within MCVideo systems are protected by the security mechanisms used for other MCX Services and defined in MCCoRe. MCVideo communications to and from external end points may be security protected and routed through the normal MCVideo system and then forwarded into the required network for onward delivery to the external end point. Alternatively, such communication could just use the protection and routing provided by the transport network. Given the potential use of stored video information in evidentiary procedures, ensuring the integrity, confidentiality and accuracy of the video information and its associated meta-data is of paramount importance for MCVideo Data.
+
+## 4.6 Confidentiality:
+
+MCVideo has the same confidentiality requirements as for other MCX Services and are defined in MCCoRe [3].
+
+## 4.7 User identities and inter-working between MCServices
+
+All users have a unique identity and at least one alias for other MCServices. A single user can have the same or different aliases for any and every MCX Service and group that they are members of, but user identities and aliases for each user resolve to a unique identity even among multiple independent MCX Services in the same domain (e.g. State or Country). In this way, a user who identifies another user using one service will be able to make contact using a different service.
+
+For example, multiple groups and multiple Mission Critical organisations working in the same building might use a map application, which shows them where all the other users are. It should be possible for one user to be able to identify a nearby user from the map and request a video (via the MCVideo Service) of the situation from a certain vantage in order to take appropriate action. The other user may be in a combined group for the mapping application (MCData) but not currently known affiliated in any other group along with the requesting user. User identities requirements are specified in MCCoRe [3].
+
+It is assumed in the present document that, even when there is no configured inter-service interworking action, the User ID for any user detected in any MCService can be used to establish video communication to that user, subject to the user being authorised for the MCVideo Service and the UE being MCVideo capable.
+
+## 4.8 Non video aspects of the MCVideo service
+
+### 4.8.1 Relationship with other MCServices
+
+As with MCPTT which has non-speech aspects to the service, in a similar way there are non-video aspects for the MCVideo service. Many of these services are in common with MCPTT such as Emergency Alert signalling, Location messaging etc. but some are also distinct such as video camera control (PTZ – Pan, Tilt, Zoom).
+
+It may also be possible for some MCCoRe aspects to work in the same way between MCVideo and MCData, for example store and forward video.
+
+### 4.8.2 Camera control
+
+Camera control is specified in MCVideo but it is not intended to define a new PTZ protocol. Where protocols exist, these should be assumed for MCVideo e.g. TVNP for PTZ although TVNP is unlikely to be the only relevant standard so there should be provision to use alternative standards according to need.
+
+### 4.8.3 Location
+
+As with other MCServices, from time to time MCVideo Service providing UE location is required. Ideally the same location messaging for a MCService UE supporting multiple services could be used to update all relevant services at the same time. Location messaging requirements are defined at stage 1 in MCCoRe specification [3].
+
+### 4.8.4 Emergency Alert
+
+As with other MCServices, the MCVideo Service will use an Emergency Alert to indicate an emergency state and to gain transport network priority. When multiple services are operating together it should be configurable whether the Emergency state of one service affects or not the Emergency state of another service. This situation may be complex to handle between groups using different services. Operational requirements are defined in the Interworking clause of MCCoRe specification [3].
+
+## 4.9 Video codecs
+
+In general, an MCVideo UE can support several video codecs (or video codec operating modes) of which some could be optional, some could be locally/regionally mandated via regulation, and one is globally mandated via 3GPP implicit (by reference) or explicit (by detailed specification) standardization as the mandatory universal interoperability video codec. If MCVideo UEs participate in a video session, they may need to negotiate or rely on defaults or other rules to establish a common video codec for the video session. Transcoding is not desirable on grounds of complexity and efficiency and in order to enable end-to-end ciphering.
+
+The MCVideo service supports both combined (for efficiency and synchronization) and separate (for cases when the video component cannot or will not be received) handling of video and audio streams.
+
+# --- 5 MCVideo specific requirements
+
+## 5.1 MCVideo services common for on network and off network
+
+### 5.1.1 Video characteristics
+
+#### 5.1.1.1 Operational recommendations and requirements for video codecs for the MCVideo service
+
+[R-5.1.1.1-001] The video codecs for the MCVideo service should be able to compress/record variable (from very low to very high) resolution video information acquired in real-time:
+
+- in conditions of varied mobility (from static to highly mobile); and
+- in conditions of optical and thermal illuminations varying from dimly lit to glare and high brightness.
+
+[R-5.1.1.1-002] The MCVideo service shall use video coding and decoding that enables license plate reading, facial and fingerprint recognition and overview of scenes.
+
+[R-5.1.1.1-002a] The MCVideo service shall support MCVideo UEs that are capable of only receiving videos (e.g. do not have a camera).
+
+[R-5.1.1.1-002b] The MCVideo service shall support MCVideo UEs that are capable of only transmitting videos (e.g. traffic camera).
+
+[R-5.1.1.1-002c] The MCVideo service shall support MCVideo UEs that are capable of transmitting and receiving videos.
+
+[R-5.1.1.1-002d] The MCVideo service shall support transportation of all 3GPP mandated video frame rates and resolutions.
+
+[R-5.1.1.1-003] The video codecs for the MCVideo service should be able to work effectively in an environment that allows for the transfer of stored or just acquired video information or both, including the capability of rapidly trading image resolution and chromaticity for transfer latency and bandwidth.
+
+[R-5.1.1.1-004] MCVideo UEs should support rendering of video clips in industry-standard widely-used formats.
+
+[R-5.1.1.1-005] The video codecs for the MCVideo service should be able to decompress video information, in a manner that enables detail-oriented intelligibility of the information.
+
+[R-5.1.1.1-006] The video encoders for the MCVideo service should provide both automatic adaptive and manual setting of its working parameters across wide ranges of values and be able to immediately and predictably reflect the changes in values.
+
+[R-5.1.1.1-007] The video codecs for the MCVideo service should provide video compression ratios and quality at least comparable to what it is customarily and reasonably expected from H.264 [6] compliant video codec implementations.
+
+[R-5.1.1.1-008] Subject to capability, capacity and configuration, it should be possible for MCVideo UEs to support the generation, storage, transmission and rendering of uncompressed video information or of video information losslessly compressed.
+
+[R-5.1.1.1-009] The MCVideo service shall provide a mechanism for an authorised MCVideo User or MCVideo Administrator to configure and to temporarily reconfigure the preferred video codec, default video resolution and default video frame rate for an MCVideo Group.
+
+[R-5.1.1.1-010] The MCVideo service shall provide a mechanism for an authorised MCVideo User or MCVideo Administrator to configure, in preference order, the allowed sets of video codec(s), corresponding video resolution(s) and video frame rate(s) for an MCVideo Group.
+
+[R-5.1.1.1-011] The MCVideo service shall provide a mechanism for automatic negotiation between MCVideo UEs for the establishment of a common video codec, corresponding video resolution(s) and video frame rate(s) for the duration of an MCVideo communication.
+
+[R-5.1.1.1-012] The MCVideo service shall support video resolution at least from 320 x 240 at 10 frames per second up to and beyond 1280 x 720 at 30 frames per second.
+
+[R-5.1.1.1-012a] An MCVideo UE that is able to transmit video may support a video resolution from 320 x 240 at 10 frames per second up to and beyond 1280 x 720 at 30 frames per second.
+
+[R-5.1.1.1-012b] An MCVideo UE that is able to receive videos shall support as a minimum, the reception, decoding and rendering of all 3GPP mandated video frame rates and resolutions.
+
+[R-5.1.1.1-013] The MCVideo service should enable high definition rendering of the video information with quality at least corresponding to video format 1080p (1920 × 1080 pixels HDTV resolution).
+
+[R-5.1.1.1-014] The MCVideo service should support the video capturing and storing of video information for objects moving at speeds of up to 150 km/h, with the ability to extract images of quality necessary for license plate reading.
+
+[R-5.1.1.1-015] The MCVideo service shall support mutual adaptation between the video codecs and the video information carrying bearer in terms of video resolution, frame rate and QoS characteristics (e.g. bandwidth, error rate).
+
+[R-5.1.1.1-016] The MCVideo service shall support UE entering the video communication late to identify the video resolution and frame rate being used and be able to start video capture, storage, encoding, transmission, reception, decoding and rendering with minimal delay upon entering the video communication.
+
+[R-5.1.1.1-017] The MCVideo service should support combined handling of video and audio information.
+
+[R-5.1.1.1-018] The MCVideo service shall support separate handling of video and audio information, including the ability to cipher, transport, store and deliver video and audio separately.
+
+[R-5.1.1.1-019] The MCVideo service shall enable uploaded images to be integrity protected on a per-frame basis and inter-frame basis.
+
+#### 5.1.1.2 End-user criteria and requirements for the selection of a video codec for MCVideo service
+
+[R-5.1.1.2-001] A single video codec for global interoperability shall be specified as mandatory. Other video codecs may be specified as optional where benefits over the global interoperability video codec are identified.
+
+NOTE: This requirement refers to 3GPP action. Local, national and regional authorities can make additional video codecs mandatory within their jurisdiction.
+
+[R-5.1.1.2-002] The global interoperability video codec shall be widely available and have a good in-field track record of availability, reliability, quality and responsiveness acquired over a substantive period of time of actual use as prescribed.
+
+[R-5.1.1.2-003] The global interoperability video codec shall have been extensively tested in all the potentially deployable operation modes.
+
+[R-5.1.1.2-004] The complexity, processing power and energy consumption of the global interoperability video codec should be in the “small” range for the specific task at hand, when other video codecs are used for comparison.
+
+[R-5.1.1.2-005] Based on the capabilities of the active UE(s) in possession of a user, each media component of a transmission received by the user shall be playable on at least one of the active UEs.
+
+#### 5.1.1.3 Video modes
+
+##### 5.1.1.3.1 Description
+
+Although MCVideo requires low latency video streams not all video streams need to comply with the same low latency. There are some situations where the latency is less important but it is very important to capture what is visible in front of the camera at the precise time. These different requirements do not necessarily relate to the level of situational Emergency and so there is a difference in a MCVideo service between Emergency and urgency.
+
+To avoid dimensioning a service to only cope with the most urgent requirements all the time and to avoid having the user community invoke Emergency just to mark a video as low latency, video modes are introduced.
+
+##### 5.1.1.3.2 Requirements
+
+[R-5.1.1.3.2-001] Based on authorized user or Administrator designation or based on profile information, the MCVideo transmissions shall be identifiable in one of three video modes i) urgent real time, ii) non-urgent real time, iii) non real time.
+
+[R-5.1.1.3.2-002] The MCVideo service shall provide a mechanism for an authorized MCVideo User or Administrator to set the video mode for an MCVideo Group.
+
+[R-5.1.1.3.2-003] The MCVideo service shall provide a mechanism for an authorized MCVideo User or Administrator to configure the allowed video modes for an MCVideo Group.
+
+### 5.1.2 Video parameters remote control
+
+#### 5.1.2.1 Remote modification of real time video quality
+
+##### 5.1.2.1.1 Service description
+
+Circumstances can affect the quality of the video connection and it should therefore be possible to adapt the video connection parameters to those circumstances in an effective manner.
+
+Mission critical control room operators and dispatchers will use video to analyse and control incidents in the field. The dispatcher might need to adapt the video quality to the purpose and for efficient use of 3GPP network resources. In the same way, an incident might be remotely managed by an officer in the field, using videos received from users involved in the incident and other sources. If only an overview of the scene is needed, a low video quality might be all that is
+
+needed. If there is a need to read a license plate or to recognize something in the scene, a very high definition video may be required. Those adaptations will have to be done in real time.
+
+##### 5.1.2.1.2 Requirements
+
+[R-5.1.2.1.2-001] The MCVideo service shall provide a mechanism for authorized MCVideo Users to remotely modify video settings in real time, through parameter modification (e.g. resolution modification) and through codec renegotiation.
+
+[R-5.1.2.1.2-002] The MCVideo service shall minimize the interruption and video information loss due to video parameter changes and codec renegotiation during video capture, transmission and rendering.
+
+[R-5.1.2.1.2-003] The MCVideo service shall provide a mechanism for authorized MCVideo Users to locally modify video quality, through parameter modification.
+
+NOTE: While a dispatcher remotely controls an MCVideo UE in the field, the local modification of parameters is forbidden.
+
+[R-5.1.2.1.2-004] The MCVideo service shall provide a mechanism for an MCVideo Administrator to authorize an MCVideo User to modify the video settings of the transmitted video stream of another MCVideo User.
+
+[R-5.1.2.1.2-005] The MCVideo service shall provide a mechanism to negotiate a change of codec being used during the video transmission.
+
+[R-5.1.2.1.2-006] The MCVideo service shall provide a mechanism for an MCVideo Administrator to authorize an MCVideo User to renegotiate a codec during a video transmission.
+
+[R-5.1.2.1.2-007] The MCVideo service shall support signaling such that video capabilities or parameters for a camera can be remotely controlled on an MCVideo UE (e.g. to capture video, video clips, images of sufficient quality to perform the purpose intended).
+
+#### 5.1.2.2 Video capabilities information management
+
+##### 5.1.2.2.1 Service description
+
+In order to enable remote control of video cameras in the field, there is a need to exchange those video capability parameters and to allow control of a subset of those parameters.
+
+##### 5.1.2.2.2 Requirements
+
+[R-5.1.2.2.2-001] The MCVideo service shall require authentication of the MCVideo User before granting service access to remotely control the video capabilities of a remote MCVideo UE.
+
+[R-5.1.2.2.2-002] The MCVideo service shall provide a mechanism by which an authorized MCVideo User can obtain and display the video capabilities of another MCVideo UE.
+
+[R-5.1.2.2.2-003] The MCVideo service shall provide a mechanism by which an authorized MCVideo User can limit what information to receive about a remote MCVideo UE.
+
+[R-5.1.2.2.2-004] The MCVideo service shall provide a mechanism for a MCVideo Administrator to authorize an MCVideo User to receive and display the capabilities of a remote MCVideo UE.
+
+[R-5.1.2.2.2-005] The MCVideo service shall support signaling such that a set of camera capabilities or parameters of an MCVideo UE can be displayed on a remote MCVideo UE.
+
+### 5.1.3 Video remote control including camera discovery
+
+#### 5.1.3.1 Remote camera control
+
+##### 5.1.3.1.1 Service description
+
+In addition to video parameters control, there is a need to remotely control the camera views (Pan, Tilt, Zoom). The technical solution need to leverage already existing standards.
+
+In addition, a user will need to be able to capture and store video from a remote camera.
+
+##### 5.1.3.1.2 Requirements
+
+[R-5.1.3.1.2-001] The MCVideo service shall provide a mechanism for an MCVideo user to remotely control a camera on another MCVideo UE subject to relevant authorization.
+
+[R-5.1.3.1.2-002] The MCVideo service shall support signalling such that a set of video capabilities or parameters for a camera can be selected on an MCVideo UE (e.g. capture video, video clips and images of sufficient quality to perform the intended purpose).
+
+[R-5.1.3.1.2-003] The MCVideo service shall provide a mechanism through which an authorized MCVideo User can control camera functions not specifically related to the video stream e.g. Pan, Tilt and Zoom (PTZ), including being able to place a capable camera in and out of an automatic detection, activation and tracking mode.
+
+NOTE: Existing protocols (e.g. TVNP) could be used.
+
+[R-5.1.3.1.2-004] The MCVideo service shall provide a mechanism for an MCVideo Administrator to authorize an MCVideo User to remotely activate another MCVideo User's camera.
+
+#### 5.1.3.2 Camera discovery
+
+##### 5.1.3.2.1 Service description
+
+When arriving at an incident and/or affiliating to a group related to the incident, an authorized user wants to discover the cameras he/she can connect to and control.
+
+The presence, exact location, addressing information, video coverage area and capabilities of cameras might not always be known to MCVideo Users. However, an authorized MCVideo User might want to discover and establish communication in order to avail himself of the video information provided by such cameras. The MCVideo service might need to control access of various users (or types of users) to different sets of cameras. For example, a remotely located medical expert might be granted access to cameras within ambulances at an incident scene, but not to security surveillance cameras. Within its allowed set of cameras, a user might want to find a subset that meets certain criteria. This can be achieved by establishing categories and associating them to various cameras. An interested user could then specify the categories of interest and the MCVideo Service would identify to the user cameras of the specified categories. Examples of categories include certain technical capabilities of the camera (e.g. self-activated camera, wide field of view etc.) and areas of use (traffic, security surveillance).
+
+##### 5.1.3.2.2 Requirements
+
+[R-5.1.3.2.2-001] An MCVideo UE shall be capable to discover, negotiate service, controlling parameters and capabilities, and to start receiving, storing and displaying video transmitted from another MCVideo UE.
+
+[R-5.1.3.2.2-002] An MCVideo UE shall be discoverable subject to permissions and authorization, capable of negotiating service, controlling parameters and capabilities, and remotely controlling another MCVideo UE.
+
+[R-5.1.3.2.2-003] The MCVideo service shall allow an MCVideo User to discover, determine the status, working parameters and capabilities and to negotiate service of MCVideo UEs within sets authorized to the MCVideo User.
+
+[R-5.1.3.2.2-004] The MCVideo service shall allow an MCVideo user to discover an MCVideo UE based on specified categories to which the MCVideo UE belongs.
+
+#### 5.1.3.3 Communications remote control
+
+##### 5.1.3.3.1 Service description
+
+Authorized users will need to be able to remotely control video communications.
+
+##### 5.1.3.3.2 Requirements
+
+[R-5.1.3.3.2-001] The MCVideo service shall provide a mechanism for an authorised MCVideo User to remotely start and stop local recording of video.
+
+[R-5.1.3.3.2-002] The MCVideo service shall provide a mechanism for an authorised MCVideo User to remotely set triggers for automatic commencement of video transmission to authorised MCVideo Users; such triggers to include motion detection, time of day, face recognition, licence plate recognition, location and speed.
+
+[R-5.1.3.3.2-003] The MCVideo service shall provide a mechanism for an authorised MCVideo User to remotely start and stop playback of recorded video (including in low resolution fast-forward mode).
+
+[R-5.1.3.3.2-004] The MCVideo service shall provide a mechanism for an authorised MCVideo User to remotely initiate transmission of a selected part of a recorded video to authorised MCVideo Users.
+
+### 5.1.4 Video processing capabilities
+
+#### 5.1.4.1 Service description
+
+There is a need to have processing capabilities in order to enhance the user experience.
+
+#### 5.1.4.2 Requirements
+
+[R-5.1.4.2-001] The MCVideo system shall have video processing capabilities including combining different video streams, to show them on a single display unit, provide digital zoom within a video stream, adapt the size and resolution of a video stream to the size and resolution of the screen or window, record video and make stills of different video streams.
+
+[R-5.1.4.2-002] The MCVideo service shall provide a mechanism for recording video content for video processing purpose.
+
+[R-5.1.4.2-003] The MCVideo service shall provide a mechanism for capturing video content using coordinated multiple video cameras.
+
+[R-5.1.4.2-004] The MCVideo service shall provide a mechanism for determining in a reasonably indisputable way whether or not presented video content was captured with multiple cameras and at the same time.
+
+[R-5.1.4.2-005] The MCVideo service shall provide a mechanism for simultaneous activation and control of multiple video cameras.
+
+[R-5.1.4.2-006] The MCVideo service should support rendering video content in stereo 3D.
+
+### 5.1.5 Robots video remote control
+
+#### 5.1.5.1 Service description
+
+Robots will be used more and more to provide unique services to Mission Critical organizations. Critical communications users need, as a consequence, a common communication framework to manage videos from robots which can take advantage of different transport technologies such as a 3GPP system. The MCVideo service, working in conjunction with existing robot control capabilities, will provide mechanisms to do that.
+
+The following sub-clause aims at defining requirements to ensure robot video control communication can be provided through a 3GPP system.
+
+It is expected that there will be different manufacturers for robots. As a consequence a well-known transport framework is needed in order to ensure easy integration of new robots.
+
+#### 5.1.5.2 Requirements
+
+[R-5.1.5.2-001] A robot may be equipped with an MCVideo UE and provide functions of an MCVideo UE, such as remote control of video parameters.
+
+[R-5.1.5.2-002] The MCVideo service shall provide a mechanism to control the video settings of a robot.
+
+[R-5.1.5.2-003] The MCVideo service shall support aerial unmanned vehicles at an altitude of up to 150 meter above the floor.
+
+[R-5.1.5.2-004] The MCVideo service, in coordination with the MCData Service, shall be able to give different priorities to the communication for controlling the MCVideo UEs, the communication for controlling/driving the robot, the communication for controlling the video transmission from the robot and the video transmitted by the robot, depending also on who it is transmitted to (e.g. pilot, a dispatcher or a group).
+
+[R-5.1.5.2-005] The MCVideo service shall provide a minimum of four levels of latencies for controlling video:
+
+- When the MCVideo UE is in an aerial unmanned vehicle, during take-off and landing, the video control latency shall remain under 100 ms.
+- When the MCVideo UE is in an aerial unmanned vehicle, while flying, the video control latency shall remain under 300 ms.
+- When the MCVideo UE is in an aquatic or submarine unmanned vehicle, the video control latency shall remain under 500 ms.
+- When the MCVideo UE is in a terrestrial unmanned vehicle moving at less than 120km/h, the video control latency shall remain under 400 ms.
+
+NOTE: At this stage of the work, the latency is an end-to-end latency. The split between network latency and robot latency is left for stage 2.
+
+[R-5.1.5.2-006] The MCVideo service shall provide a latency of the video transmission less than 500 ms when the video is used by the pilot.
+
+[R-5.1.5.2-007] Void.
+
+### 5.1.6 MCVideo Profile management and administration
+
+#### 5.1.6.1 Service description
+
+This clause describes the specific user profile management for MCVideo.
+
+#### 5.1.6.2 Requirements
+
+[R-5.1.6.2-001] The MCVideo service shall ensure that each MCVideo User has at least one associated MCVideo User Profile that contains the MCVideo's authorizations for video control, for example permissions to turn on/off cameras and displays, to enable video and audio transmission to authorized targets, to use normal controls for recording and/or playing the video, to raise and lower the resolution and the width of the visual field of the recording and of the transmission, to change the position of the visual field of the camera and to activate / deactivate motion sensors that can trigger the automatic activation of cameras.
+
+### 5.1.7 Capabilities additional to MCCoRe
+
+#### 5.1.7.1 Leaving and rejoining an in progress video communication
+
+##### 5.1.7.1.1 Service description
+
+Considering that video distribution will take significant amount of resources, and considering an operational user may in many cases not be available to watch a video, the system needs to provide an efficient means to manage entering and leaving video communications.
+
+##### 5.1.7.1.2 Requirements
+
+[5.1.7.1.2-001] The MCVideo service shall provide a means for a receiving MCVideo User to cancel receipt of a video stream on an MCVideo UE.
+
+[5.1.7.1.2-002] The MCVideo service shall provide a means for an MCVideo User to redirect on demand or in pre-determined fashion the receipt of a video stream between a receiving MCVideo UE and a video mail box.
+
+[5.1.7.1.2-003] The MCVideo service shall provide a means for an MCVideo User to rejoin a previously cancelled video stream.
+
+NOTE: This ceases to apply if the video stream has terminated for any reason.
+
+[5.1.7.1.2-004] When an MCVideo User cancels receipt of a video stream and has no other MCVideo UE receiving that video stream, an indication shall be sent to the sending MCVideo User as notification that the receiving user in question has left the video stream.
+
+[5.1.7.1.2-005] When an MCVideo User rejoins an ongoing video stream on a first MCVideo UE, an indication shall be sent to the sending MCVideo User as notification that the receiving user in question has rejoined the video stream.
+
+[5.1.7.1.2-006] If all receiving members of a video stream have left the video stream, the sending user shall be given an indication that all users have left and given the choice to end the video stream or continue sending the video for storage available for subsequent download by other users.
+
+### 5.1.8 MCVideo capability information sharing
+
+#### 5.1.8.1 Service description
+
+Before trying to remotely access the video capabilities of a UE, it might be useful to know about its capability in order to be sure the operational purpose can be achieved.
+
+#### 5.1.8.2 Requirements
+
+[R-5.1.8.2-001] Subject to permissions and authorization, the MCVideo service shall provide a means to share information about video capabilities (e.g. codecs) of MCVideo UEs under the control of members of a selected group.
+
+[R-5.1.8.2-002] Subject to permissions and authorizations, the MCVideo service shall provide a means to share current status of MCVideo UE activity (e.g. receiving video, transmitting video, or recording video) between the members of a selected group.
+
+### 5.1.9 Video push and pull services
+
+#### 5.1.9.1 Video pull service
+
+##### 5.1.9.1.1 Service description
+
+Users need the capability to pull a video from a source which might be a UE in the field, or a video storage server . In this service, a user requests another user to transmit a video stored or directly taken from the camera.
+
+##### 5.1.9.1.2 Requirements
+
+[R-5.1.9.1.2-001] The MCVideo service shall provide a mechanism for an authorized MCVideo User (e.g. dispatcher) to request an MCVideo UE to transmit a video to the requester, or to another authorized party or to both (uplink pull).
+
+#### 5.1.9.2 Video push service
+
+##### 5.1.9.2.1 Service description
+
+Users need the capability to push a video to another user.
+
+##### 5.1.9.2.2 Requirements
+
+[R-5.1.9.2.2-001] The MCVideo service shall provide a mechanism for an authorized MCVideo User to push video to another MCVideo User.
+
+[R-5.1.9.2.2-002] The MCVideo service shall provide a mechanism for an MCVideo administrator to authorize an MCVideo user to push a video to another MCVideo user.
+
+[R-5.1.9.2.2-003] The MCVideo service shall provide a mechanism for an authorized MCVideo User to enable and to disable the automatic sending of notification to a second MCVideo User that a video is being pushed to a third MCVideo User.
+
+NOTE: The second and the third MCVideo Users can be the same MCVideo User.
+
+[R-5.1.9.2.2-004] The MCVideo service shall provide a mechanism for an MCVideo User to enable and to disable being notified about video being pushed to specific MCVideo Users.
+
+[R-5.1.9.2.2-005] The MCVideo service shall provide a mechanism for an MCVideo User to enable and to disable the reception of video of specific categories.
+
+[R-5.1.9.2.2-006] The MCVideo service shall provide a mechanism for an authorized MCVideo User to manage, activate and de-activate a blacklist for MCVideo push whereby if that authorized user has activated MCVideo push blacklisting and an incoming MCVideo push is received from an MCVideo user whose ID is configured in this list then the MCVideo push request from the sending MCVideo user is denied.
+
+[R-5.1.9.2.2-007] The MCVideo service shall provide a mechanism for an authorized MCVideo User to manage, activate and de-activate a whitelist for MCVideo push whereby if that authorized MCVideo user has activated MCVideo push whitelisting and an incoming MCVideo push is received from an MCVideo user whose ID is not configured in this list then the MCVideo push request from the sending MCVideo user is denied.
+
+NOTE: It is not recommended to have both MCVideo push blacklisting and MCVideo push whitelisting activated at the same time.
+
+[R-5.1.9.2.2-008] The MCVideo service shall provide a mechanism for an MCVideo User to suspend and to resume receiving an incoming video stream from an MCVideo push.
+
+[R-5.1.9.2.2-009] The MCVideo video push service shall allow the MCVideo user to configure the MCVideo UE either to automatically accept an incoming MCVideo push request or to prompt the user as to whether to manually accept or reject the incoming MCVideo push request from the sending MCVideo user.
+
+[R-5.1.9.2.2-010] The MCVideo service shall provide a mechanism for an MCVideo administrator to authorize an MCVideo user to use the MCVideo push blacklist and whitelist feature.
+
+### 5.1.10 Video streams availability and characteristics
+
+#### 5.1.10.1 Service description
+
+Users need to be informed of the existence and the technical and operational details of group video streams in progress. The user can then decide to join the stream or not, based on the information provided.
+
+#### 5.1.10.2 Requirements
+
+[R-5.1.10.2-001] The MCVideo service shall provide a mechanism for an authorized MCVideo User to forward details of a received video stream to other MCVideo users so that, if authorized, they may also join the MCVideo stream.
+
+[R-5.1.10.2-002] The MCVideo service shall provide a mechanism for an administrator and for an authorized user, or both, to locally and remotely assign specific category tags and access permissions to a specific MCVideo UE (e.g. a certain video camera) within their domain that can be used by authorized MCVideo Users to discover, select and address that MCVideo UE.
+
+[R-5.1.10.2-003] The MCVideo service shall provide a mechanism for an administrator and for an authorized user, or both, to locally and remotely assign specific category tags and access permissions to a specific video clip within their domain that can be used by authorized MCVideo users to view that video clip.
+
+[R-5.1.10.2-004] The MCVideo service shall provide a mechanism for the advertising and distribution of category tags associated with a specific MCVideo UE or a video clip.
+
+[R-5.1.10.2-005] The MCVideo service shall provide a mechanism for an MCVideo User to use and control each of his MCVideo UEs independently of the others.
+
+[R-5.1.10.2-006] The MCVideo service shall provide a mechanism for an MCVideo User to enable and to disable the alerting and displaying of notifications addressed to MCVideo UEs under his control.
+
+[R-5.1.10.2-007] The MCVideo service shall support a mechanism by which an external observer is prevented from determining whether or not an MCVideo UE is performing video capture, transmission, or both.
+
+[R-5.1.10.2-008] The MCVideo service shall be able to provide an integrity protected timestamped detailed log of all performed and attempted activities for each user of the MCVideo Service.
+
+[R-5.1.10.2-009] The MCVideo service shall be able to add and integrity protect meta-data to a video stream (e.g. time stamps, location coordinates, parameter settings, authorship information) at the time of the video capture and recording, such that the authenticity and accuracy of the recording cannot be disputed.
+
+[R-5.1.10.2-010] The MCVideo service shall provide a mechanism by which limits on information transfer parameters (e.g. bandwidth) can be set and adjusted dynamically in order to prevent or alleviate depletion of communication resources (e.g. congestion).
+
+### 5.1.11 Video conferencing
+
+#### 5.1.11.1 Service description
+
+For small groups working on the same operation, there is a need to have a video conferencing service. This service allows a group with limited size to exchange synchronized voice and video.
+
+#### 5.1.11.2 Requirements
+
+[5.1.11.2-001] The MCVideo service shall provide a video conferencing feature.
+
+[5.1.11.2-002] The MCVideo service shall provide a mechanism to limit the maximum number of Participants in a video conference.
+
+[5.1.11.2-003] The MCVideo service shall provide a means for an authorized User or Administrator to configure the maximum number of participants in a video conference.
+
+[5.1.11.2-004] Each participant in an MCVideo video conference shall be able to simultaneously transmit video and associated synchronized voice to all other video conference participants.
+
+[5.1.11.2-005] Each participant in a video conference, subject to UE display capabilities, shall be able to receive videos from all other participants.
+
+NOTE: If relevant, the MCVideo service builds a mosaic with all the video streams and provide the mosaic to all interested participants. All the associated audio streams will be provided in this case.
+
+[5.1.11.2-006] Each participant in a video conference shall be able to choose and display a subset of video streams provided by other participants, while continuing to receive audio streams from all participants.
+
+[5.1.11.2-007] Each participant in a video conference shall be able to disable video and use the video conferencing service as a voice-only conference service.
+
+### 5.1.12 Additional security requirements for MCVideo
+
+#### 5.1.12.1 General
+
+Videos for public safety are critical and there is a need for them to be trustable. For evidentiary purposes Public Safety videos need to be certified as authentic and not tampered. The integrity of video data is of particular importance.
+
+#### 5.1.12.2 Requirements
+
+[R-5.1.12.2-001] The MCVideo service shall provide means for the generation, handling and storing of video material with evidentiary potential in a manner that guarantees its authenticity.
+
+[R-5.1.12.2-002] The MCVideo service shall provide means for tamper detection for video material with evidentiary potential.
+
+[R-5.1.12.2-003] The MCVideo service should provide means for tamper protection for video material with evidentiary potential.
+
+[R-5.1.12.2-004] The MCVideo service shall provide a mechanism by which security related information generated based on securely communicated data from the MCVideo server can be embedded in created videos and subsequently integrity protected, at the time of the video creation by the MCVideo capable UE.
+
+[R-5.1.12.2-005] The MCVideo service shall provide the ability for MCVideo server and MCVideo capable UEs to exchange MCData among themselves via secure links during the creation of videos.
+
+[R-5.1.12.2-006] MCVideo capable UEs shall be able to use location, time, subscription identity, device identity and information provided from outside the UE to generate and use security data for videos created by the UE.
+
+## 5.2 MCVideo services requirements specific to on-network use
+
+### 5.2.1 Video availability notification
+
+#### 5.2.1.1 Service description
+
+This function aims at informing the user when there is a video file which he could be interested in. The notification might also enclose a description of the video as well as an indication of its operational importance.
+
+In this service the video has been stored and is not part of an ongoing video transmission.
+
+#### 5.2.1.2 Requirements
+
+[R-5.2.1.2-001] An authorized MCVideo User shall be able to notify an MCVideo Group of the availability of a video.
+
+[R-5.2.1.2-002] An authorized MCVideo User shall be able to individually notify an MCVideo User outside an MCVideo Group that a video is available independently from any affiliation mechanism.
+
+[R-5.2.1.2-003] The MCVideo service shall provide a mechanism for an authorized MCVideo User to retrieve and view a video that has been identified in a notification.
+
+[R-5.2.1.2-004] The MCVideo availability notification may use another service (e.g. MCData).
+
+[R-5.2.1.2-005] The MCVideo service shall only send video notifications to MCVideo Users authorized to view the video.
+
+### 5.2.2 Replay of stored video
+
+#### 5.2.2.1 Service description
+
+This function aims at offering video tape functions for a user viewing a video as well as an opportunity to choose and view video files stored on the server.
+
+#### 5.2.2.2 Requirements
+
+[R-5.2.2.2-001] The MCVideo service shall provide an authorization mechanism for MCVideo Users and MCVideo Groups to view a remotely stored video.
+
+[R-5.2.2.2-002] The MCVideo service shall provide a mechanism for an authorized MCVideo User to view a video with simple video player functions (e.g. pause rewind, forward).
+
+[R-5.2.2.2-003] The MCVideo service shall provide a list of available and authorized videos for the MCVideo User.
+
+[R-5.2.2.2-004] The MCVideo service shall provide a means to associate MCVideo User authorizations to each file for viewing, modifying and/or deleting the file.
+
+NOTE: This mechanism might use groups of users.
+
+### 5.2.3 Video storage control
+
+#### 5.2.3.1 Service description
+
+Since mission critical video is sensitive data with varying local regulatory issues, an MCVideo system cannot allow videos to be viewed or copied by unauthorized people. As a consequence, there is a need to have a mechanism to automatically delete videos from a terminal as well as a mechanism to remotely delete videos from a terminal.
+
+#### 5.2.3.2 Requirements
+
+[R-5.2.3.2-001] The MCVideo service shall provide a means for an administrator to remotely select and delete selected videos and associated data of an MCVideo User from the MCVideo UE.
+
+[R-5.2.3.2-002] The MCVideo service shall provide a means by which all MCVideo data (including video related metadata) are periodically deleted from the MCVideo UE unless an action is taken by an authorized MCVideo User.
+
+[R-5.2.3.2-003] The deletion period shall be configurable.
+
+### 5.2.4 Capabilities additional to MCCoRe
+
+#### 5.2.4.1 Service description
+
+This function aims at restricting use of video services to a specific authorized MCVideo User.
+
+#### 5.2.4.2 Requirements
+
+[R-5.2.4.2-001] The MCVideo Service shall provide a mechanism for an MCVideo Administrator to restrict an MCVideo User's video communication to MCVideo use only.
+
+### 5.2.5 Video control by a dispatcher
+
+#### 5.2.5.1 Service description
+
+Dispatchers need advanced capabilities for managing MCVideo services for MCVideo Users and fixed cameras under their control.
+
+#### 5.2.5.2 Requirements
+
+[R-5.2.5.2-001] The MCVideo service shall provide a mechanism for a dispatcher of an MCVideo Group to request a monitoring camera to transmit a video to the dispatcher.
+
+[R-5.2.5.2-002] The MCVideo service shall provide a mechanism for a dispatcher of an MCVideo Group to terminate the video transmission from the monitoring camera to the dispatcher.
+
+[R-5.2.5.2-003] The MCVideo service shall provide a mechanism for a dispatcher of an MCVideo Group to request a monitoring camera to transmit a video to an authorized user.
+
+[R-5.2.5.2-004] The MCVideo service shall provide a mechanism for a dispatcher of an MCVideo Group to terminate the video transmission from the monitoring camera to the authorized user.
+
+[R-5.2.5.2-005] The MCVideo service shall provide a mechanism for a dispatcher to distribute a video to MCVideo Group Members.
+
+[R-5.2.5.2-006] The MCVideo service shall provide a mechanism for a dispatcher to terminate the video distribution to MCVideo Group Members.
+
+[R-5.2.5.2-007] The MCVideo service shall provide a mechanism for a dispatcher or an authorized user to build a mosaic from different video sources and transmit this mosaic in an MCVideo group communication.
+
+[R-5.2.5.2-008] The MCVideo Service shall provide a means to obtain the video display capabilities available for an MCVideo User.
+
+[R-5.2.5.2-009] The MCVideo service shall provide a mechanism to ensure that a target MCVideo User is able to watch a mosaic video before transmission to the user begins.
+
+### 5.2.6 Transmission control
+
+#### 5.2.6.1 Overview
+
+MCVideo provides a method of working where each video being sent is delivered as an invitation to the affiliated group members for them to elect to commence receiving or not as suits their situation. It is far better not to send video to a user who is unable to view it. Conflicting or simultaneous video communications would result in simultaneous (or near simultaneous) invitations to join and the users can choose which video communication, if any, to join. Forced reception of video can be configured by an authorised user. In this case, suitably authorised receiving users could be permitted to opt out of viewing, perhaps because they have a specific task to watch some other stream.
+
+As a consequence a video group communication can allow the user to accept the video stream before receiving a video and can allow the user to choose from available video streams amongst a list of ongoing video streams available to the user.
+
+#### 5.2.6.2 Transmission control requirements
+
+##### 5.2.6.2.1 General
+
+[R-5.2.6.2.1-001] The MCVideo service shall determine which Participant(s) are allowed to transmit a video stream.
+
+[R-5.2.6.2.1-002] An authorized Participant shall be able to request to transmit to an MCVideo Group or an individual.
+
+[R-5.2.6.2.1-003] When a request to transmit a video stream to an MCVideo Group is granted the MCVideo service shall send an invitation to all affiliated members of the selected group to allow them to accept to receive the video.
+
+[R-5.2.6.2.1-004] An MCVideo Group shall have the flexibility to be configured to allow simultaneous transmitting MCVideo Group Members.
+
+[R-5.2.6.2.1-005] MCVideo service shall provide a mechanism for the MCVideo Administrator to configure the maximum number of simultaneous transmissions in a single MCVideo Group.
+
+NOTE: No limit is a valid setting.
+
+[R-5.2.6.2.1-006] The MCVideo service shall determine who is allowed to transmit when there are requests to transmit more than the maximum number of simultaneous communications within the same group.
+
+[R-5.2.6.2.1-007] The MCVideo service may withhold permission to transmit for service based pre-emptive capacity reasons.
+
+[R-5.2.6.2.1-008] Following an MCVideo service request for permission to transmit on the Selected MCVideo Group, the Affiliated MCVideo Group Member that made and was granted the request shall be given an indication of being granted permission to transmit.
+
+[R-5.2.6.2.1-009] Following an MCVideo Private Communication request for permission to transmit, an MCVideo User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCVideo User(s).
+
+[R-5.2.6.2.1-010] When a user is not allowed to start a Group communication the request may be queued or rejected.
+
+[R-5.2.6.2.1-011] Following an MCVideo Group service request for permission to transmit on the Selected MCVideo Group, an Affiliated MCVideo Group Member that made but was not granted the request shall be given an indication that permission to transmit was queued or rejected.
+
+[R-5.2.6.2.1-012] Following an MCVideo Private Communication request for permission to transmit, an MCVideo User that is not allowed to transmit shall be given an indication that the permission to transmit was queued or rejected.
+
+##### 5.2.6.2.2 Receiving video streams
+
+[R-5.2.6.2.2-001] When a video group communication is started using a particular MCVideo Group all affiliated group members for that same MCVideo group shall be sent an invitation notifying them of the new video stream.
+
+[R-5.2.6.2.2-002] The MCVideo service shall provide a mechanism to include conditions for acceptance or rejection of the invitation (e.g. forced, unforced).
+
+[R-5.2.6.2.2-003] In the case of unforced invitation to receive an MCVideo user shall receive the video stream of a MCVideo communication only after having accepted the invitation.
+
+[R-5.2.6.2.2-004] MCVideo service shall provide a mechanism for the MCVideo Administrator to configure the maximum number of simultaneous streams received by an MCVideo User.
+
+NOTE 1: No limit is a valid setting.
+
+[R-5.2.6.2.2-005] As a configuration option, the MCVideo system shall provide a means for an authorized MCVideo user to automatically receive video communications.
+
+NOTE 2: When configured for the User to receive a video stream automatically, the transmission starts without acceptance of the receiving MCVideo User.
+
+[R-5.2.6.2.2-006] As a configuration option, the MCVideo service shall provide a means for an MCVideo user to automatically receive emergency video streams.
+
+[R-5.2.6.2.2-007] As a configuration option, the MCVideo service shall provide a means for an authorized MCVideo user to automatically receive imminent peril video streams.
+
+[R-5.2.6.2.2-008] An authorised user shall be able to configure an MCVideo group to support individual user/UE opt in to receive communications or mandatory/automatic reception.
+
+[R-5.2.6.2.2-009] An MCVideo user shall be able to opt in to receive communications for any recently invited group communications for which the MCVideo user is affiliated.
+
+NOTE 3: A list of recent invitations to opt in is stored and presented to the user on demand. Recent might be time limited, size of list limited or any other limit. Ceased communications is removed from the opt in invitation list.
+
+[R-5.2.6.2.2-010] When a video private communication is started the receiving participant shall be given the option of accepting or rejecting the communication.
+
+##### 5.2.6.2.3 Entering an ongoing video stream
+
+[R-5.2.6.2.3-001] The MCVideo service shall provide to the MCVideo User the list of ongoing/currently transmitting video group communications, for which he is affiliated, periodically and on demand.
+
+[R-5.2.6.2.3-002] The MCVideo user shall be able to choose one or more video group communications subject to MCVideo settings and UE capabilities (e.g. MCVideo UE display capabilities).
+
+[R-5.2.6.2.3-003] The MCVideo service shall provide a means to separately control the sound of the different video communications received.
+
+##### 5.2.6.2.4 Video streams reconfiguration and termination
+
+[R-5.2.6.2.4-001] The MCVideo service shall make efficient use of resources (e.g. use of eMBMS).
+
+[R-5.2.6.2.4-002] The MCVideo service shall provide a notification to a transmitting MCVideo Group Member if there are no other MCVideo Group Members who have affiliated to the MCVideo Group.
+
+[R-5.2.6.2.4-003] The MCVideo service shall provide a notification to a transmitting MCVideo Group Member if there are no MCVideo Group Members receiving their communication.
+
+NOTE: When an opt in communication is commenced, a reasonable time is allowed for other users to opt to receive the communication before such a notification is sent.
+
+[R-5.2.6.2.4-004] The MCVideo service may interrupt the transmission of an MCVideo communication when there is no MCVideo User receiving it.
+
+[R-5.2.6.2.4-005] The MCVideo service may restart the transmission of an MCVideo communication as soon as any affiliated/authorized user wants to receive the MCVideo communication.
+
+### 5.2.7 Override
+
+#### 5.2.7.1 Overview
+
+For MCVideo override is possible and useful but is different from MCPTT.
+
+MCVideo might be operated in a combined way with MCPTT. Therefore, it is likely that the sending user will have the opportunity to state what their intention is for the video that they send. In this case it might not be necessary for other regular members of the group to receive the video but the dispatcher might always receive it. In this situation, when the group invitation is sent, individual users could request to join the video if it is useful to them and convenient. Override can then be achieved by the user realising, from the MCPTT call, that another video is more important and so switching over to receive the new one.
+
+As an alternative to the invitation approach a forced approach is still possible but a group force of a video is an unpredictable option as some users might well be unable to view the video. Forced override is still possible in MCVideo. The video is announced as an invitation but includes a forced override indication. The system makes the forced override but, depending on configuration, the user might be able to review a list of allowed continuing video streams and go back to the one they are using.
+
+MCVideo might operate in a group way with many members of the group sending video to a dispatcher (private call) and the dispatcher periodically selecting and sending video back to the group.
+
+#### 5.2.7.2 General aspects
+
+[R-5.2.7.2-001] The MCVideo Service shall enable an MCVideo Service Administrator to create a hierarchy for determining which Participants, Participant types, and urgent transmission types, if any, shall be granted a request to override an active MCVideo Service transmission.
+
+[R-5.2.7.2-002] The MCVideo Service shall enable an MCVideo Service Administrator to configure which MCVideo Service Group transmission(s) a Participant(s) receives for cases where an MCVideo Service transmission can be overridden and/or to configure to allow the Participant to select from available video streams.
+
+[R-5.2.7.2-003] The MCVideo service shall enable the MCVideo Service Administrator to configure the MCVideo Service Group to limit the number of Participant(s) allowed to transmit at the same time into the same group.
+
+[R-5.2.7.2-004] The MCVideo service shall provide a mechanism for an MCVideo Service Administrator to configure MCVideo Service Private Communications to pre-empt or not to pre-empt active received group communications.
+
+[R-5.2.7.2-005] Any hierarchy used for granting a request to override an active MCVideo Service transmission shall contain at least four (4) levels.
+
+[R-5.2.7.2-006] The transmitting Participant(s) shall be determined by the relative priorities of the Participants, number of allowed transmissions and Communication type based on configuration.
+
+[R-5.2.7.2-007] The MCVideo service shall provide a mechanism for Participants, to override an active MCVideo Service transmission of a transmitting Participant based on configuration.
+
+[R-5.2.7.2-008] If an MCVideo service transmission is overridden, the MCVideo Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
+
+[R-5.2.7.2-009] If the MCVideo Service Group limit for the number of Participant(s) allowed to communicate at the same time into the same group would otherwise be exceeded, the MCVideo service shall revoke transmit permissions for non-emergency communications using the relative priorities of the Participants, emergency state and video mode based on configuration.
+
+### 5.2.8 Communication termination
+
+[R-5.2.8-001] The MCVideo service shall enable an authorized MCVideo User to terminate the permission to transmit of a transmitting Participant at any time.
+
+[R-5.2.8-002] A transmitting Participant shall be able to indicate to the MCVideo service that the Participant no longer wants to transmit.
+
+[R-5.2.8-003] If a receiving Participant of an MCVideo Service Group Communication is pre-empted, the MCVideo Service may terminate the communication or continue the communication with an indication to the transmitting Participant that one or more receiving Participants was pre-empted.
+
+NOTE 1: If the transmitting participant is pre-empted the communication stops.
+
+[R-5.2.8-004] If MCVideo User(s) are pre-empted from an on-going MCVideo service communication as there is insufficient capacity to support their on-going participation, the MCVideo service may ensure that the MCVideo User(s) receive a notification that they have been removed from the communication for reasons of lack of capacity.
+
+[R-5.2.8-005] The MCVideo service shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
+
+NOTE 2: Infinite is a valid setting for the transmit time limit.
+
+[R-5.2.8-006] The MCVideo service shall enable an MCVideo Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit.
+
+[R-5.2.8-007] The MCVideo service may provide a notification of intent to terminate a communication e.g. to give the user time to request a time limit extension.
+
+[R-5.2.8-008] The MCVideo service may terminate a communication without previously sending a notification.
+
+[R-5.2.8-009] The MCVideo service may include an indication of termination reason (e.g. time limit, administrator action) with any notification of intent to terminate or actual termination.
+
+[R-5.2.8-010] An MCVideo UE shall provide, to the User, a notification of termination or intent to terminate including any reason given.
+
+[R-5.2.8-011] The MCVideo service may include a request for more information with any notification of intent to terminate communication.
+
+NOTE 3: For example, to allow the user to request additional time, if required.
+
+[R-5.2.8-012] An MCVideo UE shall respond to a request for more information.
+
+[R-5.2.8-012a] The response to a request for more information may include request for more time, indicate no foreseen end to the communication.
+
+[R-5.2.8-013] The MCVideo service shall terminate an MCVideo Service Group Communication if any termination condition is met (e.g. last Participant leaving, second last Participant leaving, initiator leaving, time limit) or the minimum number of Affiliated MCVideo Service Group Members are not present.
+
+## 5.3 MCVideo services requirements specific to off-network use
+
+### 5.3.1 Private Communication Off-Network
+
+#### 5.3.1.1 Overview
+
+Private Communications allow two MCVideo Users to communicate directly with each other without the use of MCVideo Groups. They leverage many of the functions and features of MCVideo Group Communication, such as MCVideo User identity and alias information, location information, encryption, privacy, priority, and administrative control. This capability establishes the ability to transmit unidirectional video between two MCVideo Users, but could be used to create a bi-directional video conferencing capability.
+
+Two commencement modes of Private Communication are supported: Manual Commencement Private Communication and Automatic Commencement Private Communication.
+
+Manual Commencement Private Communication mimics a telephone conversation where the receiving party receives a notification that they are being requested to join a Private Communication, and the receiving party might accept, reject, or ignore the Communication request. Once the Communication setup is accepted, the Private Communication is established.
+
+Automatic Commencement Private Communication mimics the immediate setup and propagation of Group Communication operation between two users where the transmitting party initiates an Automatic Commencement Private Communication to another user and sends video without any additional Communication setup delay beyond Group Communication. If available and able to accept the Private Communication from the transmitting party, the receiving party immediately joins the Private Communication and processes the Communication transmitting party's video.
+
+#### 5.3.1.2 Private Communication Off-Network general requirements
+
+[R-5.3.1.2-001] The MCVideo service shall support Private Communications Off-Network.
+
+[R-5.3.1.2-002] The MCVideo Service shall provide a mechanism for the Private Communication to be set up with the MCVideo UE designated by the receiving MCVideo User to be used for Private Communications when the receiving MCVideo User has signed on to the MCVideo service with multiple MCVideo UEs.
+
+#### 5.3.1.3 Private Communication Off-Network commencement requirements
+
+[R-5.3.1.3-001] The MCVideo service shall provide a mechanism for an MCVideo User to cancel an MCVideo Private Communication prior to the Communication setup.
+
+[R-5.3.1.3-002] The MCVideo service shall provide a means by which an authorized MCVideo User initiates an MCVideo Private Communication.
+
+[R-5.3.1.3-003] The MCVideo service shall provide a means by which an MCVideo UE initiates an MCVideo Private Communication to any MCVideo User for which the MCVideo UE's current MCVideo User is authorized.
+
+NOTE: For off-network use, only an MCVideo UE within communication range (possibly via a ProSe UE-to-UE Relay) receives the transmission.
+
+[R-5.3.1.3-004] The MCVideo service shall provide a means by which an MCVideo User initiates an Automatic Commencement Private Communication to any MCVideo User for which the MCVideo User is authorized.
+
+#### 5.3.1.4 Private Communication Off-Network termination
+
+[R-5.3.1.4-001] The MCVideo service shall provide a mechanism for an MCVideo User to reject an MCVideo Private Communication.
+
+[R-5.3.1.4-002] The MCVideo service shall provide a means by which an MCVideo User ends a Private Communication in which the MCVideo User is a Participant.
+
+#### 5.3.1.5 Private Communication Off-Network administration
+
+[R-5.3.1.5-001] The MCVideo service shall provide a mechanism for an MCVideo Administrator to configure which MCVideo Users, within their authority, are authorized to place a Manual Commencement Private Communication.
+
+[R-5.3.1.5-002] The MCVideo service shall provide a mechanism for an MCVideo Administrator to configure which MCVideo Users, within their authority, are authorized to place an Automatic Commencement Private Communication.
+
+[R-5.3.1.5-003] The MCVideo service shall provide a mechanism for an MCVideo Administrator to configure for a particular authorized MCVideo User, a set of MCVideo Users under the same authority to which an MCVideo Private Communication can be made.
+
+[R-5.3.1.5-004] The MCVideo service shall provide a mechanism for an MCVideo Administrator to configure the maximum duration for MCVideo Private Communications for MCVideo Users within their authority.
+
+### 5.3.2 MCVideo Transmission Control Off-Network
+
+#### 5.3.2.1 Overview
+
+MCVideo Transmission Control Off-Network provides a necessary capability for an authorized user of the MCVideo service to request to transmit, receive an indication of being allowed to transmit or not being allowed to transmit and terminate a request to transmit when the MCVideo user no longer wants to transmit. A transmit time limit is provided which allows an MCVideo Administrator to configure the limits for any transmission related to a single request to transmit. MCVideo Transmission Control Off-Network also provides an override capability based on a priority hierarchy to override an active MCVideo transmission of a transmitting Participant based on configuration.
+
+#### 5.3.2.2 General Aspects
+
+[R-5.3.2.2-001] The MCVideo service when operating off-network shall determine at a point in time which off-network Participant(s) are allowed to transmit to other off-network Participants.
+
+[R-5.3.2.2-002] An MCVideo Group shall have the flexibility to be configured to allow simultaneous transmitting MCVideo Group Members.
+
+[R-5.3.2.2-003] The MCVideo service shall provide a mechanism for the MCVideo Service Administrator to configure the maximum number of simultaneous communications received by an off-network MCVideo User in a single MCVideo Group.
+
+#### 5.3.2.3 Requesting Permission to Transmit
+
+[R-5.3.2.3-001] An authorized Participant shall be able to request to transmit to an MCVideo Group or an individual MCVideo User.
+
+[R-5.3.2.3-002] The MCVideo service shall determine which Participant(s) are permitted to transmit when there are simultaneous requests for permission to transmit within the same group.
+
+[R-5.3.2.3-003] Following an MCVideo request for permission to transmit on the Selected MCVideo Group, any Affiliated MCVideo User that made and was granted the request shall be given an indication of being allowed to transmit.
+
+[R-5.3.2.3-004] Following an MCVideo request for permission to transmit on the Selected MCVideo Group, any Affiliated MCVideo User that made and was not granted the request shall be given an indication that permission to transmit was not given at that time.
+
+[R-5.3.2.3-005] The MCVideo service when operating off-network shall provide a mechanism for an MCVideo Participant to cancel its MCVideo request to transmit at any stage, including before the request has been granted.
+
+[R-5.3.2.3-006] The MCVideo service shall provide a mechanism for the MCVideo Administrator to configure parameter(s) relating to the automatic termination of an off-network MCVideo service request to transmit.
+
+#### 5.3.2.4 Override
+
+[R-5.3.2.4-001] An MCVideo UE shall be pre-provisioned by an MCVideo Administrator and/or authorized user with the necessary information in order that override may operate during off-network MCVideo communication.
+
+[R-5.3.2.4-002] The MCVideo service shall provide a mechanism for MCVideo Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types, when operating off the network, be granted a request to override an active off-network MCVideo transmission.
+
+[R-5.3.2.4-003] The priority hierarchy used for granting a request to override an active MCVideo transmission shall contain at least four (4) levels.
+
+[R-5.3.2.4-004] The MCVideo service shall provide a mechanism for Participants, to override an active MCVideo transmission of a transmitting Participant based on configuration.
+
+[R-5.3.2.4-005] If an MCVideo transmission is overridden, the MCVideo Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
+
+[R-5.3.2.4-006] The MCVideo service shall provide a mechanism to enable an MCVideo Administrator to configure which MCVideo Group transmission(s) a Participant(s) receives, for cases where an MCVideo transmission can be overridden.
+
+[R-5.3.2.4-007] If the MCVideo Group has been configured to only allow the overriding transmitting Participant to transmit, the MCVideo service shall revoke the transmit permission of the overridden transmitting Participant.
+
+#### 5.3.2.5 Terminating Permission to Transmit
+
+[R-5.3.2.5-001] A transmitting Participant shall be able to indicate to the off-network MCVideo service that the Participant no longer wants to transmit.
+
+[R-5.3.2.5-002] The off-network MCVideo service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
+
+#### 5.3.2.6 Transmit Time Limit
+
+[R-5.3.2.6-001] The Off-Network MCVideo Service shall provide a mechanism for an MCVideo UE to be pre-provisioned by an MCVideo Administrator and/or authorized user with the necessary information in order that a transmit time limit function may operate during off-network MCVideo communication.
+
+[R-5.3.2.6-002] The Off-Network MCVideo Service shall enable an MCVideo Administrator to configure the limits (e.g. elapsed time, quantity of data) for any transmission related to a single request to transmit.
+
+[R-5.3.2.6-003] The Off-Network MCVideo Service shall have configurable limits (e.g. elapsed time, quantity of data), including indefinite, for any transmission related to a single request to transmit (e.g. elapsed time, quantity of data).
+
+[R-5.3.2.6-004] The Off-Network MCVideo Service shall provide an indication to the transmitting Participant a configurable amount before the transmit limit is reached.
+
+[R-5.3.2.6-005] The Off-Network MCVideo Service shall provide an indication to the transmitting Participant that the Participant's transmit limit has been reached.
+
+[R-5.3.2.6-006] The Off-Network MCVideo Service shall remove the permission to transmit from the transmitting Participant when the Participant's transmit limit has been reached.
+
+## 5.4 Performance and quality requirements for on-network and off-network
+
+### 5.4.1 MCVideo device and camera moving at high speed
+
+#### 5.4.1.1 Service description
+
+Motion affects the length of time a desired target is shown in the video frame, and can cause the target to blur. The level of motion in a particular piece of video content can have a huge impact on the performance of a video coder. A moving camera might also produce video that is much more difficult to encode efficiently.
+
+For public safety applications, if the video is considered “mission critical,” the loss or interruption of a video stream or any significant delay in the delivery of the video stream might be unacceptable for processing by the video decoder. Therefore, if a source of video content is in motion and handovers between radio coverage areas are necessary, then it is important that the handovers are handled in a manner to minimize loss, interruption and delay of the video stream.
+
+#### 5.4.1.2 Requirements
+
+[R-5.4.1.2-001] The MCVideo Service shall support one-to-one video communications between authorized MCVideo UEs when the transmitting and/or receiving MCVideo UEs are moving at different speeds, from 0 km/h to 160km/h.
+
+[R-5.4.1.2-002] The MCVideo Service shall support group video communications between authorized MCVideo UEs when the transmitting and/or receiving MCVideo UEs are moving at different speeds, from 0 km/h to 160km/h.
+
+NOTE: It is assumed that communications in high speed trains might be possible with special design.
+
+### 5.4.2 Latencies
+
+[R-5.4.2-001] The MCVideo Service shall ensure that transmission of urgent real time video transmissions shall be started within 2 seconds after the request.
+
+[R-5.4.2-002] The MCVideo Service shall ensure that the end-to-end delay from transmitting MCVideo UE to receiving MCVideo UE or console for urgent real time video transmissions shall be no more than 1 s.
+
+[R-5.4.2-003] A sending MCVideo UE may be configured to begin storing video immediately from the time the user requests an MCVideo transmission. In this case the end to end delay shall not exceed 1 s plus the commencement delay (up to 2 s).
+
+[R-5.4.2-004] The MCVideo Service shall ensure that the end-to-end delay from transmitted MCVideo UE to receiving MCVideo UE or console for non-urgent real time priority video transmissions shall be no more than 10 s.
+
+[R-5.4.2-005] Synchronisation between video and audio when played at the MCVideo receiving UE or console shall be within 50 ms.
+
+# --- 6 Interworking
+
+## 6.1 Interworking with non 3GPP video systems
+
+[R-6.1-001] The MCVideo service shall, be able to interwork with non 3GPP systems subject to capabilities and compatibilities limitations using standardized interface(s).
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|---------------|
+| TSG SA # | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Ca t | Subject/Comment | Old | New | WI |
+| SP-73 | SP-160544 | S1-162430 | 22.281 | 0001 | 2 | Rel-14 | F | Video requirements clarifications | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162494 | 22.281 | 0002 | 2 | Rel-14 | F | Add Service description in sub-clause 5.4.1.1 for MCVideo Device and Camera moving at high speed. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162017 | 22.281 | 0003 | | Rel-14 | D | Editorial changes to several sub-clauses in MCVideo TS 22.281 for consistency and to improve understanding and readability. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162419 | 22.281 | 0004 | 1 | Rel-14 | F | Add References to clause 2 and Abbreviations to sub-clause 3.2 in MCVideo TS 22.281. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162021 | 22.281 | 0005 | | Rel-14 | F | Add 'remotely' to the requirements in sub-clause 5.1.3.3.2 in MCVideo TS 22.281 to provide clarification. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162498 | 22.281 | 0006 | 2 | Rel-14 | F | In MCVideo TS 22.281 add a definition for robot in sub-clause 3.1 and provide changes to sub-clause 5.1.5 Robots video remote control to improve understanding and readability. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162034 | 22.281 | 0007 | | Rel-14 | F | In MCVideo TS 22.281 modify sub-clause 5.3.2.2 requirement 3 and remove variable N9. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162495 | 22.281 | 0009 | 2 | Rel-14 | F | In MCVideo TS 22.281 Modify title of sub-clause 5.4 to indicate that the performance and quality requirements are for on-network and off-network. | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-73 | SP-160544 | S1-162499 | 22.281 | 0010 | 2 | Rel-14 | F | Corrections to 22.281 | 14.0.0 | 14.1.0 | MCImp-MCVideo |
+| SP-74 | SP-160892 | S1-163013 | 22.281 | 0011 | | Rel-14 | D | Editorial change to MCVideo TS 22.281 sub-clause 3.1 | 14.1.0 | 14.2.0 | MCImp-MCVideo |
+| SP-75 | SP-170150 | S1-171056 | 22.281 | 0013 | | Rel-14 | F | Correct inconsistent use of the term "one-to-many" | 14.2.0 | 14.3.0 | MCImp-MCVideo |
+| SP-75 | SP-170150 | S1-171232 | 22.281 | 0014 | | Rel-14 | F | Clarification of MCVideo push requirement R-5.1.9.2.2-006 | 14.2.0 | 14.3.0 | MCImp-MCVideo |
+| SP-76 | SP-170438 | S1-172396 | 22.281 | 0015 | 1 | Rel-15 | F | Clarification of MCVideo push blacklist and whitelist feature | 14.3.0 | 15.0.0 | MCImp-MCVideo |
+| SP-78 | SP-170985 | S1-174040 | 22.281 | 0016 | | Rel-15 | F | Removing 'over LTE' from the title of the specification | 15.0.0 | 15.1.0 | MCOVer |
+| SP-78 | SP-170985 | S1-174044 | 22.281 | 0017 | | Rel-15 | F | Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards | 15.0.0 | 15.1.0 | MCOVer |
+| SP-78 | SP-170984 | S1-174546 | 22.281 | 0018 | 1 | Rel-15 | D | MCVideo push text correction | 15.0.0 | 15.1.0 | TEI15 |
+| SP-81 | SP-180761 | S1-182074 | 22.281 | 0019 | | Rel-16 | B | Application of MCVideo to maritime usage | 15.1.0 | 16.0.0 | MARCOM |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|-----------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2022-03 | SA#95e | - | - | - | - | Upgraded to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22282/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22282/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a5d0457cf580558a227300f96055b52797f78ab
--- /dev/null
+++ b/marked/Rel-18/22_series/22282/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b153ef2ca0948e29b02d3b0024df70a0ebc28c81edec80829811e513d9285e5
+size 9586
diff --git a/marked/Rel-18/22_series/22282/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22282/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f65ed32ad7f103cab2cb1956f274d562d553219
--- /dev/null
+++ b/marked/Rel-18/22_series/22282/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17789522e58a5944f923a286f89af4745a40944cbb002586093e820a96ff38ac
+size 7232
diff --git a/marked/Rel-18/22_series/22282/raw.md b/marked/Rel-18/22_series/22282/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b8794b0c136f842344e8aa180d8b4b6fc59392e
--- /dev/null
+++ b/marked/Rel-18/22_series/22282/raw.md
@@ -0,0 +1,722 @@
+
+
+# 3GPP TS 22.282 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Data services Release 18** ---
+
+
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+Mission, Critical, Data
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Overview..... | 7 |
+| 5 MCData generic capability requirements common for on-network and off-network ..... | 7 |
+| 5.1 Introduction ..... | 7 |
+| 5.2 SDS feature ..... | 7 |
+| 5.2.1 General ..... | 7 |
+| 5.2.2 Requirements..... | 8 |
+| 5.2.3 Remote Start Requirements Using SDS..... | 8 |
+| 5.3 File distribution capability ..... | 9 |
+| 5.3.1 General ..... | 9 |
+| 5.3.2 Requirements..... | 9 |
+| 5.4 Data streaming capability..... | 9 |
+| 5.4.1 General ..... | 9 |
+| 5.4.2 Requirements..... | 9 |
+| 5.5 IP connectivity..... | 10 |
+| 5.5.1 Service description ..... | 10 |
+| 5.5.2 Requirements..... | 10 |
+| 6 MCData specific requirements..... | 11 |
+| 6.1 MCData Services common for on network and off network ..... | 11 |
+| 6.1.1 Conversation management including delivery notification..... | 11 |
+| 6.1.1.1 Service description..... | 11 |
+| 6.1.1.2 Service requirements..... | 11 |
+| 6.1.2 Robots..... | 12 |
+| 6.1.2.1 Robots remote control..... | 12 |
+| 6.1.2.1.1 Service description ..... | 12 |
+| 6.1.2.1.2 Requirements..... | 12 |
+| 6.1.2.2 Robots communication ..... | 13 |
+| 6.1.2.2.1 Robot identification ..... | 13 |
+| 6.1.2.2.1.1 Service description ..... | 13 |
+| 6.1.2.2.2 Requirements..... | 13 |
+| 6.1.3 MCData enhanced status ..... | 13 |
+| 6.1.3.1 Service description..... | 13 |
+| 6.1.3.2 Requirements ..... | 13 |
+| 6.2 MCData Services requirements specific to on-network use ..... | 13 |
+| 6.2.1 Database enquiries and secured internet access ..... | 13 |
+| 6.2.1.1 Service description..... | 13 |
+| 6.2.1.2 Requirements ..... | 14 |
+| 6.2.2 Transmission control requirements ..... | 14 |
+| 6.2.2.1 General..... | 14 |
+| 6.2.2.2 Receiving data..... | 14 |
+| 6.2.2.3 Accessing data ..... | 15 |
+| 6.2.2.4 Data reconfiguration and termination ..... | 15 |
+| 6.2.4 MCData enhanced status on-network..... | 15 |
+| 6.2.4.1 Service description..... | 15 |
+| 6.2.4.2 Requirements ..... | 15 |
+| 6.2.3 Communication termination..... | 15 |
+| 6.3 MCData Services requirements specific to off-network use..... | 16 |
+| 6.3.1 Private Communication Off-Network ..... | 16 |
+
+| | | |
+|-------------------------------|-----------------------------------------------|-----------|
+| 6.3.1.1 | Overview..... | 16 |
+| 6.3.1.2 | Requirements ..... | 16 |
+| 6.3.2 | MCData Transmission Control Off-Network..... | 17 |
+| 6.3.2.1 | Overview..... | 17 |
+| 6.3.2.2 | General Aspects ..... | 17 |
+| 6.3.2.3 | Requesting Permission to Transmit ..... | 17 |
+| 6.3.2.4 | Override ..... | 17 |
+| 6.3.2.5 | Terminating Permission to Transmit ..... | 18 |
+| 6.3.2.6 | Transmit Time Limit..... | 18 |
+| 7 | Interworking..... | 18 |
+| 7.1 | Interworking with non 3GPP data systems ..... | 18 |
+| Annex A (informative): | Change history..... | 20 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document provides the service requirements for operation of the MCData service. MCData makes use of capabilities included in Group Communication System Enablers, Proximity Services, Isolated E-UTRAN operation for Public Safety and Mission Critical Services Common Requirements with additional requirements specific to the MCData Service. The MCData Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specifications do not apply to GSM or UMTS.
+
+# --- 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 41.001: "GSM Specification set".
+- [3] 3GPP TS 22.280: "Mission Critical Services Common Requirements".
+- [4] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
+- [5] ETSI TS 100 392-2 v.3.7.1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air Interface (AI)
+- [6] 3GPP TS 22.281: "Mission Critical Video services".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Conversation:** A series of messages that are linked to the same topic within a group or one-to-one data communication.
+
+**Conversation ID:** An identifier that uniquely identifies a conversation within a group or one-to-one data communication.
+
+**MCData Conversation Hang Time:** The time from the transmission of an MCData message after which a subsequent MCData message is no longer considered to be linked to the previous one.
+
+**MCData System:** The collection of applications, services, and enabling capabilities required to provide Mission Critical Data for a Mission Critical Organization.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|----------------------------------------------|
+| IOPS | Isolated E-UTRAN Operation for Public Safety |
+| SDS | Short Data Service |
+
+# --- 4 Overview
+
+MCData defines a service for Mission Critical Data services. As well as voice services, current mission critical users have been increasing their use of data services, including low throughput services on legacy networks and data services on commercial networks. This need will continue to grow with the creation of the new multimedia services. The MCData service needs to provide a means to manage all data connections of mission critical users in the field and provide relevant resources to the ones who need it. For example mission critical users already use event manager software along with the voice system. The migration to 3GPP networks will allow mission critical users to operate current and new data services whilst relying on the fundamental capabilities of mission critical communication such as defined for MCPTT in [4] and included into MCCoRe [3].
+
+The MCData Service provides a set of communication services that will be directly used by the user or functions that will be called by external applications in control rooms.
+
+The MCData Service will reuse functions including end-to-end encryption, key management, authentication of the sender, etc. defined in [3] in order to provide group communications for data services. As for all mission critical services, users affiliate to groups in order to receive communications directed to the group.
+
+In addition, the MCData Service will provide a set of generic capabilities such as: messaging, file distribution, data streaming, IP proxy, etc. Also, the MCData Service will provide specific services such as conversation management, data base enquiries, internet access, robots control.
+
+The MCData Service is expected to have open interfaces in the network. It needs also to provide an opportunity for a variety of multimedia applications using the MCData Service.
+
+# --- 5 MCData generic capability requirements common for on-network and off-network
+
+## 5.1 Introduction
+
+MCData makes frequent use of a set of capabilities and enablers that allows for many end user services to be built on a common foundation. Several generic capabilities are defined for use in the MCData Service. These capabilities can be used on their own to transfer files, messages and other content to individuals and affiliated members of groups or combined with other services, through an application, to provide complete end users services as determined by the authorities implementing the service. The MCData generic capabilities are common for on-network and off-network.
+
+It is not intended to invent new protocols for the MCData Service. Where existing protocols are efficient and sufficient, the service should make use of these protocols.
+
+## 5.2 SDS feature
+
+### 5.2.1 General
+
+The SDS feature of the MCData Service could be considered as a basic protocol carrying a limited size, but variable content, payload message. This message could be text or could be marked for extensible purposes including short binary
+
+messages for application communication. Messaging could be one-to-one messaging or could be group messaging using groups as specified in MCCoRe.
+
+### 5.2.2 Requirements
+
+[R-5.2.2-001] The MCData Service shall provide an SDS feature for conveyance of limited size, variable content, messages.
+
+[R-5.2.2-002] The MCData SDS shall provide a group service to affiliated members with policy assertion capabilities (e.g. certain types of message or content may only be relevant to certain members of a group due, for example, to location).
+
+[R-5.2.2-003] The MCData SDS shall provide a one to one service with policy assertion capabilities (e.g. policy to limit certain types of message or content to certain users due, for example, to location or user privilege).
+
+[R-5.2.2-004] The MCData SDS shall provide the option to include a content payload of at least [1000] characters of 8 bit text or [500] characters of 16 bit text or [250] characters of 32 bit text and the necessary character encoding information (for example to identify alphabet used).
+
+[R-5.2.2-005] The MCData SDS shall provide the option to include a content payload of at least [1000] characters of hyperlink or interleaved text and hyperlink(s) to allow subsequent access to linked content (which may be a large file).
+
+[R-5.2.2-006] The MCData SDS shall provide the option to include a content payload of at least [1000] bytes of binary data to be used by a local running application and the necessary addressing detail to identify the intended application.
+
+[R-5.2.2-007] The MCData SDS shall provide a message thread indication so that multiple message flows can be managed independently.
+
+[R-5.2.2-008] When replying to a message on the MCData SDS or sending any message which should be coupled with previously sent or received messages or message flows; the message thread indication shall use the same indication as was used for those previous messages.
+
+[R-5.2.2-009] The MCData SDS shall provide a selectable read receipt indication. When requested, the receiving entity shall provide receipt indication for delivered and read messages as appropriate.
+
+NOTE 1: The read indication will implicitly indicate delivered as well.
+
+[R-5.2.2-010] The MCData SDS shall provide a configurable read receipt indication. When configured, the receiving entity shall provide receipt indication addressed to the application for delivered and read messages as appropriate.
+
+NOTE 2: The read indication will implicitly indicate delivered as well.
+
+[R-5.2.2-011] The MCData SDS shall permit delivery history interrogation for suitably authorized users.
+
+[R-5.2.2-012] The MCData SDS shall provide the option to add a field indicating location of the sending user/UE.
+
+[R-5.2.2-013] The MCData SDS shall allow empty messages including only a field indicating location of the sending user/UE.
+
+### 5.2.3 Remote Start Requirements Using SDS
+
+[R-5.2.3-001] SDS content received in a UE, addressed to a known local application that is not yet running shall cause the UE to start the local application and pass the content to the application. This could be used to start an application and pass to it the initial data.
+
+[R-5.2.3-002] The MCData SDS shall provide the capability to remotely start a local application (e.g. situational awareness). This may be through specific use of binary payload on the SDS.
+
+## 5.3 File distribution capability
+
+### 5.3.1 General
+
+File distribution is a fundamental capability of the MCData Service. File distribution can be used to provide a standalone file transfer capability or can be invoked by a controlling application to support the purpose of the application.
+
+### 5.3.2 Requirements
+
+[R-5.3.2-001] The MCData Service shall provide a file distribution capability.
+
+[R-5.3.2-002] The MCData file distribution capability shall provide a service to allow a user to send a file to any combination of individual users and/or affiliated groups.
+
+[R-5.3.2-003] The MCData file distribution capability shall provide an option for each recipient to choose to receive the file or not (e.g. by storing the file and sending a link (URL) to all relevant members).
+
+NOTE 1: By using this capability a user can choose when to receive the file.
+
+[R-5.3.2-004] The MCData file distribution capability shall allow a user to reject to receive the file where appropriate.
+
+[R-5.3.2-005] The MCData file distribution capability shall provide a sending user selectable indication for mandatory download so that the UE, for all relevant receiving members, will automatically download the file.
+
+NOTE 2: The mandatory indication provides a system level capability and could be invoked automatically by need of the application or might be provided for selection by the user.
+
+[R-5.3.2-006] The MCData file distribution capability shall provide download complete indications for each recipient successfully downloading the file.
+
+[R-5.3.2-007] The MCData file distribution capability shall allow the sender to select to send the file immediately to all chosen users.
+
+[R-5.3.2-008] The MCData file distribution capability shall make use of available system delivery efficiencies for distribution of common information to users within a specific geographic area and able to receive at the same time.
+
+[R-5.3.2-009] The MCData file distribution capability shall allow a user to cancel distribution of files they have sent, but have not been delivered.
+
+[R-5.3.2-010] The MCData file distribution capability shall allow an authorised user to cancel distribution of files being sent or waiting to be sent.
+
+## 5.4 Data streaming capability
+
+### 5.4.1 General
+
+Data streaming is a fundamental capability of the MCData Service. Data streaming can be used to provide a standalone data streaming capability or can be invoked by a controlling application to support the purpose of the application.
+
+### 5.4.2 Requirements
+
+[R-5.4.2-001] The MCData Service shall provide a data streaming capability.
+
+[R-5.4.2-002] The MCData data streaming capability shall provide an option that allows each recipient to choose to receive the data stream or not (e.g. by sending a link (URL) to all relevant members).
+
+[R-5.4.2-003] The MCData data streaming capability shall allow a user to reject to receive the datastream.
+
+[R-5.4.2-004] The MCData data streaming capability shall provide a sending user selectable indication for automatic reception by the UE.
+
+[R-5.4.2-005] The MCData data streaming capability shall provide start and stop records to the sender for each recipient successfully receiving the data stream.
+
+[R-5.4.2-006] The MCData data streaming capability shall make use of available system delivery efficiencies for streaming of common information to users within the same relevant area and able to receive at the same time.
+
+[R-5.4.2-007] The MCData data streaming capability shall allow a user to cancel streaming of data they have initiated including data remaining buffered in the system waiting to be streamed.
+
+[R-5.4.2-008] The MCData data streaming capability shall allow an authorised user to terminate streaming of data being sent and cancel streaming of data remaining buffered in the system waiting to be streamed.
+
+[R-5.4.2-009] The MCData data streaming capability shall provide setup time of:
+
+- Less than 1 second for immediate setup of a data communication.
+- Less than 3 second for normal setup of a data communication.
+
+NOTE 1: Setup time of a communication is essential because of their safety related character.
+
+NOTE 2: Communication setup encompasses the value of the elapsed time between the communication establishment request and the indication of successful communication establishment.
+
+## 5.5 IP connectivity
+
+### 5.5.1 Service description
+
+IP connectivity can be used for MCData applications that are based on the IP client-server paradigm. The UE can contain a client using a service in the network (e.g. a police officer accessing a server on the police Intranet from his mobile phone). The UE can also contain a server that is accessed by other UEs (e.g. a mobile information display that is controlled by a police officer from his mobile phone). As an UE for MCData application can be an unmanned device, or device without user interface, authorization of IP data transport can be provided remotely by an authorized user for the UE.
+
+### 5.5.2 Requirements
+
+[R-5.5.2-001] The MCData Service shall enable an MCData user to initiate transport of IP data towards a server in the network or another MCData user.
+
+[R-5.5.2-002] The MCData Service shall enable incoming transport of IP data towards an MCData user, initiated by another MCData user.
+
+[R-5.5.2-003] The MCData Service shall enable an authorized person for an MCData user to authorize initiation of transport of IP data from that MCData user to specific destinations. This authorization may be preconfigured or may be provided by the authorized person when IP data transport to a new destination is initiated. Authorization may be revoked on demand by the authorized person.
+
+[R-5.5.2-004] The MCData Service shall enable a MCData user or authorized person for this MCData user to authorize initiation of incoming transport of IP data from specific other MCData users. This authorization may be preconfigured, or may be provided by the authorized person when IP data transport from a new destination is initiated. Authorization may be revoked on demand by the authorized person.
+
+[R-5.5.2-005] The MCData Service shall support incoming and outgoing IP data transport for a MCData user with a higher per packet priority .
+
+[R-5.5.2-006] The MCData Service shall enable an authorized person to remotely authorize the use of higher per packet priority for a particular MCData user.
+
+# 6 MCData specific requirements
+
+## 6.1 MCData Services common for on network and off network
+
+### 6.1.1 Conversation management including delivery notification
+
+#### 6.1.1.1 Service description
+
+A group of people can be involved in different activities in an operational situation. As a consequence, there is a need to manage different activities and to easily retrieve data exchanged around one activity. Therefore conversation management is applied to all messaging and file transfer. Conversation management can be seen as an aggregation of related MCData transmissions for a given activity.
+
+The system will not be able to manage an infinite number of conversations. Rather than simply limiting the number of conversations and asking users to send a notification when the conversation ends, it is proposed here to limit the time of a conversation.
+
+#### 6.1.1.2 Service requirements
+
+[R-6.1.1.2-001] The MCData Service shall provide a conversation management feature for each MCData User.
+
+[R-6.1.1.2-002] The MCData conversation management service shall be available for group communication as well as for one-to-one communications.
+
+[R-6.1.1.2-003] The MCData Service conversation management feature shall use the SDS and file distribution generic capabilities.
+
+NOTE: For instance, if SDS and file distribution capability are combined for a conversation, the two thread indications are assumed to appear in the conversation as unique.
+
+[R-6.1.1.2-004] A conversation shall be identified through a unique conversation ID.
+
+[R-6.1.1.2-005] The MCData Service conversation management feature shall provide an MCData Conversation Hang Time after which the last message/file shall no longer be correlated to the previous.
+
+[R-6.1.1.2-006] The MCData Conversation Hang Time shall be available to the user.
+
+[R-6.1.1.2-007] The MCData Conversation Hang Time shall be configurable for each MCData User and each MCData Group.
+
+[R-6.1.1.2-008] The MCData Service conversation management feature shall allow multiple parallel conversations for the same group or the same pair of users.
+
+[R-6.1.1.2-009] The MCData Service shall provide a mechanism for an MCData User to request to receive a "message delivered" and/or "message read" disposition notifications for all outgoing messages and all file transfers for a specific private conversation of the MCData User.
+
+[R-6.1.1.2-009a] The MCData Service shall provide a mechanism for an MCData User to request to receive "message delivered" and/or "message read" disposition notifications for all outgoing messages and all file transfers for a specific conversation in a group that the MCData User is affiliated to."
+
+[R-6.1.1.2-009b] The MCData Service shall provide a mechanism for the MCData User to request the disposition notifications either per message, or during a time window or for the whole conversation.
+
+[R-6.1.1.2-009c] The MCData Service shall provide a mechanism for an authorized MCData User to request to receive or to stop to receive "message delivered" and/or "message read" disposition notifications for all messages and all file transfers for a specific conversation in a group that the authorized MCData User is affiliated to.
+
+[R-6.1.1.2-009d] The MCData Service shall provide a mechanism for an authorized MCData User to request to receive or to stop to receive "message delivered" and/or "message read" disposition notifications for all messages and all file transfers for all conversations in a group that the authorized MCData User is affiliated to.
+
+[R-6.1.1.2-010] The MCData Service shall make use of SDS and file distribution capability to provide relevant access to delivery history and delivery efficiencies.
+
+[R-6.1.1.2-011] If configured by the MCX Administrator the MCData Service shall be able to provide a MCX User the data that had previously been distributed in an ongoing MCData group conversation before this MCX User had affiliated or joined.
+
+### 6.1.2 Robots
+
+#### 6.1.2.1 Robots remote control
+
+##### 6.1.2.1.1 Service description
+
+Robots as defined in 3GPP TS 22.281 [6] will be used more and more to provide unique services to mission critical organizations. Critical communications users need, as a consequence, a common communication framework for robots which can take advantage of different transport technologies such as a 3GPP system. The MCData Service, working in conjunction with existing robot control capabilities, will provide mechanisms to do that.
+
+The following sub-clause aims at defining requirements to ensure robot control communication can be provided through a 3GPP system.
+
+We expect different manufacturers for robots. As a consequence a well-known transport framework is needed in order to ensure easy integration of new robots.
+
+##### 6.1.2.1.2 Requirements
+
+[R-6.1.2.1.2-001] The MCData Service shall enable the control of robots.
+
+[R-6.1.2.1.2-002] The MCData Service shall provide a common transmission framework to use and control robots.
+
+[R-6.1.2.1.2-003] The MCData Service shall provide a default control latency depending on the robots type under
+
+- 50 ms for an aerial unmanned vehicle;
+- 200 ms for an aquatic or submarine unmanned vehicle; and
+- 400 ms for a terrestrial unmanned vehicle.
+
+NOTE: At this stage of the work, the latency is an end to end latency. The split between network latency and robot latency is left for stage 2. The latency is measured between the action of the pilot and the movement of the robot (not only MCData Service).
+
+[R-6.1.2.1.2-004] The MCData Service shall be able to simultaneously manage multiple robots and robot types.
+
+[R-6.1.2.1.2-005] Void.
+
+[R-6.1.2.1.2-006] The MCData Service shall support management of an aerial unmanned vehicle at an altitude of up to 150 m above the floor.
+
+[R-6.1.2.1.2-007] The MCData Service shall have a default priority scheme for each kind of robot (aerial, aquatic, submarine or terrestrial unmanned vehicles).
+
+[R-6.1.2.1.2-008] The MCData Service shall be able to provide relevant priorities to different MCData communications according to the default priority scheme without additional configuration.
+
+[R-6.1.2.1.2-009] The MCData Service default priority scheme shall ensure that data exchanged for controlling a robot has relevant high priority amongst user data and cannot be pre-empted.
+
+[R-6.1.2.1.2-010] The MCData Service default priority scheme shall ensure that essential robots telemetry data (such as position when out of sight) has also a high priority and cannot be pre-empted.
+
+[R-6.1.2.1.2-011] The essential telemetry data shall be identified and minimized in order not to forbid critical operational data to be transmitted.
+
+#### 6.1.2.2 Robots communication
+
+[R-6.1.2.2-001] The MCData Service shall support MCData communication between robots.
+
+[R-6.1.2.2-002] The MCData Service shall support MCData communication between robots to be initiated and/or terminated by a controller.
+
+#### 6.1.2.2 Robot identification
+
+##### 6.1.2.2.1 Service description
+
+Robots as defined in [6] (e.g., aerial, aquatic, submarine and terrestrial unmanned vehicles) will need to be identified across the organization in order to share who is doing what.
+
+There will also be a need to exchange information specific to different robots.
+
+##### 6.1.2.2.2 Requirements
+
+[R-6.1.2.2.2-001] The MCData Service shall provide a means to identify robots used by a Mission Critical Organization.
+
+[R-6.1.2.2.2-002] The MCData Service shall provide a mechanism for an authorized user to get identifying information for one or more robots associated with all MCData UEs that are under the coverage of the MCData System. Location information may be also sent with identifying data.
+
+[R-6.1.2.2.2-003] The MCData Service shall provide to an MCData authorized User a means to get the location of each robot associated with any MCData UE under the coverage of the MCData System.
+
+[R-6.1.2.2.2-004] The MCData Service shall be able to provide characteristics (free formatted information transported by 3GPP) of an MCData UE associated with a given robot to the authorized user.
+
+### 6.1.3 MCData enhanced status
+
+#### 6.1.3.1 Service description
+
+Mission Critical Service users need to share status information specific to their activities. For instance status can be: available, in operation on site, going to the operation site, or just arrived. When working in a group, there is a need to constantly share this information.
+
+#### 6.1.3.2 Requirements
+
+[R-6.1.3.2-001] The MCData Service shall provide a means to share in real-time operational status information between members of a selected group.
+
+[R-6.1.3.2-002] The possible operational status values shall be configurable.
+
+[R-6.1.3.2-003] The minimum number of possible different operational status values shall be 32.
+
+## 6.2 MCData Services requirements specific to on-network use
+
+### 6.2.1 Database enquiries and secured internet access
+
+#### 6.2.1.1 Service description
+
+Mission critical users are already using data applications today for which a priority management will need to be implemented.
+
+#### 6.2.1.2 Requirements
+
+[R-6.2.1.2-001] The MCData Service shall provide controlled access to external services (e.g. data bases, web sites, event manager software).
+
+[R-6.2.1.2-002] The MCData Service shall be able to select priorities to data flows for external services (e.g. data bases access, web sites, event manager software).
+
+### 6.2.2 Transmission control requirements
+
+#### 6.2.2.1 General
+
+[R-6.2.2.1-001] The MCData Service shall determine which Participant(s) are allowed to transmit data.
+
+[R-6.2.2.1-002a] The MCData Service shall provide a mechanism so that small data items can be automatically sent to the chosen receiving users (private communication) or to affiliated members of the Selected MCData group.
+
+[R-6.2.2.1-002b] The MCData Service shall provide a mechanism so that when an MCData request to transmit is granted, the data can be automatically sent on to the chosen receiving users (private communication) or to affiliated members of the Selected MCData group (i.e. without prior acceptance from the receiving user).
+
+[R-6.2.2.1-002c] The MCData Service shall provide a mechanism so that when an MCData request to transmit is granted the data can be temporarily stored in the system and an invitation to receive is sent to the chosen receiving users (private communication) or to affiliated members of the Selected MCData group.
+
+NOTE 1: This is for support of sending large data files, allowing the receiving user to choose when to receive.
+
+[R-6.2.2.1-002d] The MCData Service may provide a configurable default time to live value for data waiting to be delivered to a receiving user.
+
+[R-6.2.2.1-002e] The MCData Service may terminate all remaining invitations to receive after expiry of the time to live.
+
+[R-6.2.2.1-003] The MCData Service shall provide a mechanism for the MCData Administrator to configure the maximum data size for automatic data transmission.
+
+[R-6.2.2.1-004] When an MCData UE has begun to transmit data or when the data transmission has completed the MCData Service shall begin to send the data to all affiliated members of the selected group.
+
+NOTE 2: Where the MCData Service chooses to use eMBMS to broadcast the data to several users, the UE will need to be notified to select the relevant channel before the data is sent.
+
+NOTE 3: The MCData Service might choose to temporarily store the transmitted data and deliver it independently to receiving users as appropriate.
+
+[R-6.2.2.1-005] The MCData Service may withhold permission to transmit for service based pre-emptive capacity reasons.
+
+[R-6.2.2.1-006] Following an MCData Service request for permission to transmit on the Selected MCData Group, an Affiliated MCData Group Member that made but was not granted the request shall be given an indication that permission to transmit was not given at that time.
+
+[R-6.2.2.1-007] When a user is not allowed to start a communication the request may be queued or rejected.
+
+#### 6.2.2.2 Receiving data
+
+[R-6.2.2.2-001] An MCData user shall be able to choose to download data for any recently invited group communications.
+
+NOTE: A list of available data is stored and presented to the user on demand. The term, recent, might be time limited, size of list limited or any other limit.
+
+#### 6.2.2.3 Accessing data
+
+[R-6.2.2.3-001] The MCData Service shall provide, periodically and on demand, to the MCData User the list of available recently invited data group communications for which he is affiliated.
+
+[R-6.2.2.3-002] The MCData user shall be able to affiliate to one or more MCData Groups subject to MCData settings and UE capabilities.
+
+#### 6.2.2.4 Data reconfiguration and termination
+
+[R-6.2.2.4-001] The MCData Service shall make efficient use of resources.
+
+[R-6.2.2.4-002] The MCData Service shall provide a notification to a transmitting MCData Group Member if there are no other MCData Group Members who have affiliated to the MCData Group.
+
+[R-6.2.2.4-003] Following a notification that there are no other MCData Group Members affiliated to the MCData Group and if the transmitting MCData Group Member does not terminate their request to transmit, the MCData Service may either (terminate the permission to transmit) or (allow the transmission to continue and store the transmitted data for a time to live time and deliver invitations to receive to subsequent affiliating members).
+
+### 6.2.4 MCData enhanced status on-network
+
+#### 6.2.4.1 Service description
+
+When operating on network it should be possible to implement a centralised enhanced status system to track the enhanced status of many users. This would use communication from the users to a centralised system. Other users could interrogate or subscribe to changes from this centralised system.
+
+#### 6.2.4.2 Requirements
+
+[R-6.2.4.2-001] The MCData Service shall provide a means to share, in real-time, operational status information to a single MCData User or centralised enhanced status system.
+
+[R-6.2.4.2-002] The MCData Service shall allow an authorised user to subscribe for status update reports of users within their domain.
+
+[R-6.2.4.2-003] The MCData Service shall allow an authorised user to publish status updates on behalf of another MCData User within their domain.
+
+### 6.2.3 Communication termination
+
+[R-6.2.3-001] The MCData Service shall enable an authorized MCData User to terminate the transmission of a transmitting participant at any time.
+
+[R-6.2.3-002] A transmitting participant shall be able to indicate to the MCData Service that the participant no longer wants to transmit.
+
+[R-6.2.3-003] If a transmitting participant of an MCData Service Group Communication is pre-empted, the MCData Service shall terminate the communication.
+
+[R-6.2.3-004] If MCData User(s) are pre-empted from an on-going MCData Service communication as there is insufficient capacity to support their on-going participation, the MCData Service shall provide the MCData User(s) with a notification that they have been removed from the communication for reasons of lack of capacity.
+
+[R-6.2.3-005] The MCData Service shall have a configurable limit for the maximum amount of data or time that a Participant transmits from a single request to transmit.
+
+NOTE 1: Infinite is a valid setting for the transmit data limit.
+
+[R-6.2.3-006] The MCData Service shall enable an MCData Administrator to configure the limits for a transmission that a Participant transmits from a single request to transmit.
+
+[R-6.2.3-007] The MCData Service may provide a notification of intent to terminate a communication e.g. to give the user time to request an extension.
+
+[R-6.2.3-008] The MCData Service may terminate a communication without previously sending a notification.
+
+[R-6.2.3-009] The MCData Service may include an indication of termination reason (e.g. data volume limit, administrator action, time limit expiry) with any notification of intent to terminate or actual termination.
+
+[R-6.2.3-010] An MCData UE shall provide, to the MCData User, a notification of intent to terminate including any reason given.
+
+[R-6.2.3-010a] An MCData UE may provide, to the MCData User, a notification of termination including any reason given.
+
+[R-6.2.3-011] The MCData Service may include a request for more information with any notification of intent to terminate communication.
+
+NOTE 2: For example to allow the UE to indicate the remaining data volume to send if known.
+
+[R-6.2.3-012] An MCData UE shall respond to a request for more information.
+
+[R-6.2.3-012a] The response to the request for more information may include an indication of the amount of data still to be transmitted.
+
+[R-6.2.3-013] The MCData Service shall terminate an MCData Service Group Communication if any termination condition occurs.
+
+## 6.3 MCData Services requirements specific to off-network use
+
+### 6.3.1 Private Communication Off-Network
+
+#### 6.3.1.1 Overview
+
+Private Communications off-network allows two MCData Users to communicate directly with each other without the use of the network. Private Communications off-network is generally applicable to all of the MCData subservices (SDS, file distribution capability, data streaming capability, IP connectivity).
+
+#### 6.3.1.2 Requirements
+
+[R-6.3.1.2-001] The MCData service shall support Private Communications Off-Network.
+
+[R-6.3.1.2-002] The MCData service shall provide a mechanism for an MCData User to cancel an MCData Private Communication prior to the Communication setup.
+
+[R-6.3.1.2-003] The MCData service shall provide a means by which an authorized MCData User initiates an MCData Private Communication.
+
+[R-6.3.1.2-004] The MCData service shall provide a means by which an MCData UE initiates an MCData Private Communication to any MCData User for which the MCData UE's current MCData User is authorized.
+
+NOTE: For off-network use, only an MCData UE within communication range (possibly via a ProSe UE-to-UE Relay) receives the transmission.
+
+[R-6.3.1.2-005] The MCData service shall provide a mechanism for an MCData User to reject an MCData Private Communication.
+
+[R-6.3.1.2-006] The MCData service shall provide a means by which an MCData User ends a Private Communication in which the MCData User is a Participant.
+
+[R-6.3.1.2-007] The MCData service shall provide a mechanism for an MCData Administrator to configure for a particular authorized MCData User, a set of MCData Users under the same authority to which an MCData Private Communication can be made.
+
+[R-6.3.1.2-008] The MCData service shall provide a mechanism for an MCData Administrator to configure the maximum duration for MCData Private Communications for MCData Users within their authority.
+
+### 6.3.2 MCData Transmission Control Off-Network
+
+#### 6.3.2.1 Overview
+
+MCData Transmission Control Off-Network provides a necessary capability for an authorized user of the MCData service to request to transmit, receive an indication of being allowed to transmit or not being allowed to transmit and terminate a request to transmit when the MCData user no longer wants to transmit. A transmit time limit is provided which allows an MCData Administrator to configure the limits for any transmission related to a single request to transmit. MCData Transmission Control Off-Network also provides an override capability based on a priority hierarchy to override an active MCData transmission of a transmitting Participant based on configuration. The MCData Transmission Control Off-Network capability does not apply to all of the MCData subservices (SDS, file distribution capability, data streaming capability, IP connectivity).
+
+#### 6.3.2.2 General Aspects
+
+[R-6.3.2.2-001] The MCData service when operating off-network shall determine at a point in time which off-network Participant(s) are allowed to transmit to other off-network Participants.
+
+[R-6.3.2.2-002] An MCData Group shall have the flexibility to be configured to allow simultaneous transmitting MCData Group Members.
+
+[R-6.3.2.2-003] The MCData service shall provide a mechanism for the MCData Service Administrator to configure the maximum number of simultaneous communications received by an off-network MCData User in a single MCData Group.
+
+#### 6.3.2.3 Requesting Permission to Transmit
+
+[R-6.3.2.3-001] An authorized Participant shall be able to request to transmit to an MCData Group or an individual MCData User.
+
+[R-6.3.2.3-002] The MCData service shall determine which Participant(s) are permitted to transmit when there are simultaneous requests for permission to transmit within the same group.
+
+[R-6.3.2.3-003] Following an MCData request for permission to transmit on the Selected MCData Group, any Affiliated MCData User that made and was granted the request shall be given an indication of being allowed to transmit.
+
+[R-6.3.2.3-004] Following an MCData request for permission to transmit on the Selected MCData Group, any Affiliated MCData User that made and was not granted the request shall be given an indication that permission to transmit was not given at that time.
+
+[R-6.3.2.3-005] Following an MCData Private Communication request for permission to transmit, an MCData User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCData User(s).
+
+[R-6.3.2.3-006] Following an MCData Private Communication request for permission to transmit, an MCData User that is not allowed to transmit shall be given an indication that the permission to transmit was queued or rejected.
+
+[R-6.3.2.3-007] The MCData service when operating off-network shall provide a mechanism for an MCData Participant to cancel its MCData request to transmit at any stage, including before the request has been granted.
+
+[R-6.3.2.3-008] The MCData service shall provide a mechanism for the MCData Administrator to configure parameter(s) relating to the automatic termination of an off-network MCData service request to transmit.
+
+#### 6.3.2.4 Override
+
+[R-6.3.2.4-001] An MCData UE shall be pre-provisioned by an MCData Administrator and/or authorized user with the necessary information in order that override may operate during off-network MCData communication.
+
+[R-6.3.2.4-002] The MCData service shall provide a mechanism for MCData Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types, when operating off the network, be granted a request to override an active off-network MCData transmission.
+
+[R-6.3.2.4-003] The priority hierarchy used for granting a request to override an active MCData transmission shall contain at least four (4) levels.
+
+[R-6.3.2.4-004] The MCData service shall provide a mechanism for Participants, to override an active MCData transmission of a transmitting Participant based on configuration.
+
+[R-6.3.2.4-005] If an MCData transmission is overridden, the MCData Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
+
+[R-6.3.2.4-006] The MCData service shall provide a mechanism to enable an MCData Administrator to configure which MCData Group transmission(s) a Participant(s) receives, for cases where an MCData transmission can be overridden.
+
+[R-6.3.2.4-007] If the MCData Group has been configured to only allow the overriding transmitting Participant to transmit, the MCData service shall revoke the transmit permission of the overridden transmitting Participant.
+
+#### 6.3.2.5 Terminating Permission to Transmit
+
+[R-6.3.2.5-001] A transmitting Participant shall be able to indicate to the off-network MCData service that the Participant no longer wants to transmit.
+
+[R-6.3.2.5-002] The off-network MCData service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
+
+#### 6.3.2.6 Transmit Time Limit
+
+[R-6.3.2.6-001] The Off-Network MCData Service shall provide a mechanism for an MCData UE to be pre-provisioned by an MCData Administrator and/or authorized user with the necessary information in order that a transmit time limit function may operate during off-network MCData communication.
+
+[R-6.3.2.6-002] The Off-Network MCData Service shall enable an MCData Administrator to configure the limits (e.g. elapsed time, quantity of data) for any transmission related to a single request to transmit.
+
+[R-6.3.2.6-003] The Off-Network MCData Service shall have configurable limits (e.g. elapsed time, quantity of data), including indefinite, for any transmission related to a single request to transmit (e.g. elapsed time, quantity of data).
+
+[R-6.3.2.6-004] The Off-Network MCData Service shall provide an indication to the transmitting Participant a configurable amount before the transmit limit is reached.
+
+[R-6.3.2.6-005] The Off-Network MCData Service shall provide an indication to the transmitting Participant that the Participant's transmit limit has been reached.
+
+[R-6.3.2.6-006] The Off-Network MCData Service shall remove the permission to transmit from the transmitting Participant when the Participant's transmit limit has been reached.
+
+# --- 7 Interworking
+
+## 7.1 Interworking with non 3GPP data systems
+
+[R-7.1-001] Interworking between the MCData SDS and TETRA Short Data Service [5] shall be supported.
+
+**Editor's Note:** interworking with other non-3GPP systems is FFS.
+
+## 7.2 Interworking with GSM-R
+
+[R-7.2-001] Interworking between the MCData SDS and GSM-R SMS shall be supported.
+
+---
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------------|
+| TSG SA # | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Ca t | Subject/Comment | Old | New | WI |
+| SP-73 | SP-160545 | S1-162015 | 22.282 | 0001 | | Rel-14 | F | Remove requirement in MCData TS 22.282 that has been added to MCCoRe TS 22.280. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162424 | 22.282 | 0002 | 1 | Rel-14 | D | Editorial changes to several clauses and sub-clauses in MCData TS 22.282 for consistency and to improve understanding and readability. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162500 | 22.282 | 0003 | 2 | Rel-14 | B | In MCData TS 22.282 Add requirements to empty sub-clause 6.3 MCData Services requirements specific to off-network use. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162426 | 22.282 | 0004 | 1 | Rel-14 | F | In MCData TS 22.282 Provide changes to sub-clause 6.1.2 Robots, to improve understanding and readability. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162026 | 22.282 | 0005 | | Rel-14 | F | In MCData TS 22.282 Modify the title of clause 5 MCData generic capability requirements and add a sentence to the introduction sub-clause 5.1 | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162496 | 22.282 | 0006 | 2 | Rel-14 | F | Remove data streaming from MCData TS 22.282 sub-clause 6.1.1.1 Service description 1st paragraph, 3rd sentence. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162030 | 22.282 | 0007 | | Rel-14 | F | In MCData TS 22.282 change group to users in sub-clause 5.2.2 requirement 3. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162428 | 22.282 | 0008 | 1 | Rel-14 | F | Change may to shall in MCData TS 22.282 sub-clause 6.2.3 requirement 10. | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-73 | SP-160545 | S1-162429 | 22.282 | 0009 | 1 | Rel-14 | F | Corrections to 22.282 | 14.0.0 | 14.1.0 | MCImp-MCData |
+| SP-74 | SP-160893 | S1-163014 | 22.282 | 0010 | | Rel-14 | F | Change the numbering for requirement 3 in sub-clause 6.1.2.1.2. | 14.1.0 | 14.2.0 | MCImp-MCData |
+| SP-75 | SP-170150 | S1-170167 | 22.282 | 0011 | | Rel-14 | D | Replace Configuration with Conversation in R-6.1.1.2-006 | 14.2.0 | 14.3.0 | MCImp-MCData |
+| SP-75 | SP-170150 | S1-171026 | 22.282 | 0012 | | Rel-14 | F | Correct inconsistent use of the term 'one-to-many' | 14.2.0 | 14.3.0 | MCImp-MCData |
+| SP-78 | SP-170985 | S1-174041 | 22.282 | 0016 | | Rel-15 | F | Removing 'over LTE' from the title of the specification | 14.3.0 | 15.0.0 | MCOVer |
+| SP-78 | SP-170985 | S1-174045 | 22.282 | 0017 | | Rel-15 | F | Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards | 14.3.0 | 15.0.0 | MCOVer |
+| SP-78 | SP-170989 | S1-174566 | 22.282 | 0015 | 2 | Rel-16 | C | Addition of capability to support centralised enhanced status monitoring | 15.0.0 | 16.0.0 | TEI16 |
+| SP-79 | SP-180133 | S1-180297 | 22.282 | 0020 | 1 | Rel-16 | A | Clarification of requirements for delivery and read notifications | 16.0.0 | 16.1.0 | TEI15 |
+| SP-79 | SP-180134 | S1-180432 | 22.282 | 0021 | 1 | Rel-16 | B | Introduction of railway emergency alert functionality to 22.282 | 16.0.0 | 16.1.0 | MONASTERY2 |
+| SP-79 | SP-180134 | S1-180448 | 22.282 | 0018 | 2 | Rel-16 | B | TS_22.282 CR_LOCOTROL infomation transmission between engines | 16.0.0 | 16.1.0 | MONASTERY2 |
+| SP-80 | SP-180310 | S1-181585 | 22.282 | 0024 | 2 | Rel-16 | B | CR_22.282_ setup time requirement for monitoring and control of critical infrastrucuture communication | 16.1.0 | 16.2.0 | MONASTERY2 |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|-----------------------------------------|--------|--------|------------|
+| SP-81 | SP-180757 | S1-182578 | 22.282 | 0026 | 2 | Rel-16 | B | IP connectivity for MCData users. | 16.2.0 | 16.3.0 | MONASTERY2 |
+| SP-81 | SP-180761 | S1-182615 | 22.282 | 0025 | 1 | Rel-16 | B | Application of MCData to maritime usage | 16.2.0 | 16.3.0 | MARCOM |
+
+| Change history | | | | | | | |
+|-----------------------|----------------|-------------|-----------|------------|------------|-----------------------------------------------------------|--------------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-12 | SP-82 | SP-181000 | 0027 | | B | Add interworking between MCData SDS and GSM-R SMS | 16.4.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22289/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22289/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b13247b8520a7d12eb1a026cb443a3f8a7ff0c96
--- /dev/null
+++ b/marked/Rel-18/22_series/22289/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38992a8b71f5a824c4c459c6feee31245fcc86572b237f1bc794c36e37bd2532
+size 9473
diff --git a/marked/Rel-18/22_series/22289/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22289/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5cbf1e19fc495479526b246999967ad418e0c2c0
--- /dev/null
+++ b/marked/Rel-18/22_series/22289/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95abc991924fb924e2e3fcbecfaf1a144e2be4d8ec053138dd59eef7249fcb3f
+size 7160
diff --git a/marked/Rel-18/22_series/22289/a71911ad87414271aeb190e0eebcb989_img.jpg b/marked/Rel-18/22_series/22289/a71911ad87414271aeb190e0eebcb989_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63683d8fe502512f6141b9df7f6f46fd7adbfb4f
--- /dev/null
+++ b/marked/Rel-18/22_series/22289/a71911ad87414271aeb190e0eebcb989_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b962d1d2ceed25694f9c368db2143065c93d36b45fa3c18d0afeef41442e139
+size 58781
diff --git a/marked/Rel-18/22_series/22289/c0843c6d138705289960d9f53a6e72a1_img.jpg b/marked/Rel-18/22_series/22289/c0843c6d138705289960d9f53a6e72a1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae80e13323fdd4e907825d29248e69e825d28520
--- /dev/null
+++ b/marked/Rel-18/22_series/22289/c0843c6d138705289960d9f53a6e72a1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8515f808396879beab55abe76d72068640dad07e983326f735841e89f057401
+size 80971
diff --git a/marked/Rel-18/22_series/22289/c3c305cefbac2e7b13be34ab87054d1e_img.jpg b/marked/Rel-18/22_series/22289/c3c305cefbac2e7b13be34ab87054d1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3dac900e900cc593103029f28ddcb0e59064cfa7
--- /dev/null
+++ b/marked/Rel-18/22_series/22289/c3c305cefbac2e7b13be34ab87054d1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5866e5309edea324a451519ba195744f57c72a2813abb0efdec1ee79a74d7a3b
+size 73230
diff --git a/marked/Rel-18/22_series/22289/raw.md b/marked/Rel-18/22_series/22289/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5b2cfd0fe5f6b314744f0904db73756b652c119
--- /dev/null
+++ b/marked/Rel-18/22_series/22289/raw.md
@@ -0,0 +1,546 @@
+
+
+# 3GPP TS 22.289 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mobile Communication System for Railways; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+## Keywords ---
+
+Railways; Requirements
+
+### **3GPP**
+
+### Postal address ---
+
+### 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+### Internet ---
+
+
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|--------------------------------------------------------------------------------|---------------------------------------------------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations..... | 6 |
+| 4 Railway communication functionality..... | 6 |
+| 4.1 Bulk Transfer of CCTV archives from Train to Ground ..... | 6 |
+| 4.1.1 Description..... | 6 |
+| 4.1.2 Requirements ..... | 9 |
+| 4.2 Bulk transfer of multimedia from ground to train..... | 9 |
+| 4.2.1 Description..... | 9 |
+| 4.2.2 Requirements ..... | 10 |
+| 4.3 Massive Inter-carriage data transfer..... | 10 |
+| 4.3.1 Description..... | 10 |
+| 4.3.2 Requirements ..... | 10 |
+| 4.4 Coexistence of automated train control with other train applications ..... | 10 |
+| 4.4.1 Description..... | 10 |
+| 4.4.2 Requirements ..... | 11 |
+| 5 Performance requirements for main line..... | 11 |
+| 5.1 Environmental conditions ..... | 11 |
+| 5.2 Low latency and high reliability ..... | 11 |
+| 5.2.1 Overview..... | 11 |
+| 5.2.2 Scenarios and KPIs for main line..... | 12 |
+| 6 Performance requirements for rail-bound mass transit..... | 14 |
+| 6.1 Environmental conditions ..... | 14 |
+| 6.2 Low latency and high reliability ..... | 14 |
+| 6.2.1 Overview..... | 14 |
+| 6.2.2 Scenarios and KPIs for rail-bound mass transit..... | 14 |
+| 6.2.2.1 ..... | Overview 14 |
+| 6.2.2.2..... | Scenarios and KPIs for rail-bound mass transit 15 |
+| Annex A (informative): Change history..... | 17 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document provides rail communication Stage 1 normative service requirements for 5G system. Rail communication includes main line and rail-bound mass transit. Communication for main line is based on the set of Mission Critical specification [1], [2], [3], [4]. Several service requirements for rail-bound mass transit are based on the methodology of cyber-physical control applications [7]. Requirements which are not in the scope of those specifications are provided in this Technical Specification.
+
+# --- 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 TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
+- [2] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
+- [3] 3GPP TS 22.281: "Mission Critical Video services ".
+- [4] 3GPP TS 22.282: "Mission Critical Data services ".
+- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [6] 3GPP TS 22.261: "Service requirements for the 5G system"
+- [7] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains"
+- [8] UIC EIRENE: "Functional Requirements Specification Version 8.0.0"
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Area traffic capacity:** total traffic throughput served per kilometer along a rail line.
+
+**CCTV:** Closed-circuit television, also known as video surveillance, is the use of video cameras for monitoring and recording people, animals and objects in different places, such as in vehicles and stations.
+
+**CCTV offload:** Transfer of video surveillance data archives from train to ground through the wireless connection between mobile communication unit in the train and ground communication units located at the depot and at the stations and/or stops.
+
+**Communication service availability:** percentage value of the amount of time the end-to-end communication service is delivered according to an agreed QoS, divided by the amount of time the system is expected to deliver the end-to-end service according to the specification in a specific area.
+
+**Communication service reliability:** ability of the communication service to perform as required for a given time interval, under given conditions.
+
+**End-to-end latency:** the time that takes to transfer a given piece of information unidirectional from a source to a destination, measured at the communication interface, from the moment it is transmitted by the source to the moment it is successfully received at the destination.
+
+**Inter-carriage link:** Wireless connection between the carriages of the train.
+
+**Reliability:** in the context of network layer packet transmissions, percentage value of the amount of sent network layer packets successfully delivered to a given system entity within the time constraint required by the targeted service, divided by the total number of sent network layer packets.
+
+**Survival time:** the time that an application consuming a communication service may continue without an anticipated message.
+
+**Transfer interval:** time difference between two consecutive transfers of application data from an application via the service interface to 3GPP system.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|----------------------------|
+| CCTV | Closed-circuit television |
+| MTTC | Mass-transit train control |
+
+# --- 4 Railway communication functionality
+
+## 4.1 Bulk Transfer of CCTV archives from Train to Ground
+
+### 4.1.1 Description
+
+The video surveillance system in trains consists of multiple cameras which are recording and encoding the video feeds 24/7 either into the video recorders or into internal memory of the cameras themselves. The amount of video recordings is excessive, which exceeds rather fast the physical storage capacity that is available in video recorders and/or in cameras. The regulations in different countries are ruling retention time for recordings until up to 31 days or even more. However, the recordings need to be stored in the physical storages located in the vehicles for only seven days.
+
+Next, an example estimation is provided to illustrate the offload performance with different uplink speeds, when the train is commuting from Helsinki to Kemijärvi. The parameters for the calculation are provided in Table 1, whereas the offload results for uplink speeds of 400 Mbps, 750 Mbps and 1000 Mbps are provided respectively in Figure 1.1.1-2, Figure 1.1.1-3 and in Figure 1.1.1-4.
+
+| Station | Arrives | Departs | Stop time | Time between stations |
+|-----------|---------|---------|-----------|-----------------------|
+| HELSINKI | | 18:52 | | |
+| PASILA | 18:57 | 19:00 | 0:03 | 0:08 |
+| TIKKURILA | 19:41 | 19:44 | 0:03 | 0:44 |
+| RIIHIMÄKI | 20:19 | 20:22 | 0:03 | 0:38 |
+
+| | | | | |
+|-------------|-------|-------|------|------|
+| HÄMEENLINNA | 20:46 | 20:48 | 0:02 | 0:26 |
+| TAMPERE | 21:38 | 22:11 | 0:33 | 1:23 |
+| PARKANO | 23:03 | 23:06 | 0:03 | 0:55 |
+| SEINÄJOKI | 0:08 | 0:10 | 0:02 | 1:04 |
+| KOKKOLA | 1:37 | 1:39 | 0:02 | 1:29 |
+| YLIVIESKA | 3:10 | 3:12 | 0:02 | 1:33 |
+| OULU | 4:42 | 5:00 | 0:18 | 1:48 |
+| KEMI | 6:08 | 6:12 | 0:04 | 1:12 |
+| ROVANIEMI | 7:47 | 7:55 | 0:08 | 1:43 |
+| MISI | 8:31 | 8:32 | 0:01 | 0:37 |
+| KEMIJÄRVI | 9:00 | 9:05 | 0:05 | 0:33 |
+
+Table 4.1.1-1. The parameters for the offload calculation for the train route between Helsinki and Kemijärvi.
+
+
+
+| Location | Data In (Mbits) | Data Output capacity (Mbits) | Left (Mbits) |
+|-------------|-----------------|------------------------------|--------------|
+| HELSINKI | 0 | 0 | 0 |
+| PASIL | ~50,000 | ~100,000 | ~50,000 |
+| TIKKURILA | ~200,000 | ~100,000 | ~100,000 |
+| RIIHIMÄKI | ~250,000 | ~150,000 | ~100,000 |
+| HÄMEENLINNA | ~280,000 | ~200,000 | ~100,000 |
+| TAMPERE | ~550,000 | ~900,000 | ~100,000 |
+| PARKANO | ~200,000 | ~100,000 | ~150,000 |
+| SEINÄJOKI | ~400,000 | ~100,000 | ~350,000 |
+| KOKKOLA | ~700,000 | ~100,000 | ~650,000 |
+| YLIVIESKA | ~1,000,000 | ~100,000 | ~950,000 |
+| OULU | ~1,400,000 | ~500,000 | ~900,000 |
+| KEMI | ~1,200,000 | ~150,000 | ~1,050,000 |
+| ROVANIEMI | ~1,450,000 | ~200,000 | ~1,250,000 |
+| MISI | ~1,400,000 | ~50,000 | ~1,350,000 |
+| KEMIJÄRVI | ~1,500,000 | ~150,000 | ~1,350,000 |
+
+Bar chart showing offload results in Mbits for various locations along the train route. The Y-axis represents Mbits from 0,00 to 1600000,00. The X-axis lists locations: HELSINKI, PASILA, TIKKURILA, RIIHIMÄKI, HÄMEENLINNA, TAMPERE, PARKANO, SEINÄJOKI, KOKKOLA, YLIVIESKA, OULU, KEMI, ROVANIEMI, MISI, KEMIJÄRVI. The legend indicates three data series: Data In (blue), Data Output capacity (brown), and Left (red).
+
+Figure 4.1.1-2. The offload results with uplink speed of 450 Mbps.
+
+
+
+| Location | Data In (Mbits) | Data Output capacity (Mbits) | Left (Mbits) |
+|-------------|-----------------|------------------------------|--------------|
+| HELSINKI | 10000 | 150000 | 10000 |
+| PASILA | 10000 | 150000 | 10000 |
+| TIKKURILA | 180000 | 150000 | 10000 |
+| RIIHIMÄKI | 180000 | 150000 | 10000 |
+| HÄMEENLINNA | 150000 | 100000 | 10000 |
+| TAMPERE | 400000 | 1450000 | 10000 |
+| PARKANO | 220000 | 150000 | 10000 |
+| SEINÄJOKI | 350000 | 250000 | 10000 |
+| KOKKOLA | 600000 | 100000 | 500000 |
+| YLIVIESKA | 850000 | 100000 | 750000 |
+| OULU | 1200000 | 800000 | 400000 |
+| KEMI | 680000 | 200000 | 500000 |
+| ROVANIEMI | 900000 | 400000 | 550000 |
+| MISI | 700000 | 100000 | 650000 |
+| KEMIJÄRVI | 780000 | 250000 | 550000 |
+
+Bar chart showing offload results for 750 Mbps uplink speed across various locations. The Y-axis is 'Mbits' from 0,00 to 1600000,00. The X-axis lists locations: HELSINKI, PASILA, TIKKURILA, RIIHIMÄKI, HÄMEENLINNA, TAMPERE, PARKANO, SEINÄJOKI, KOKKOLA, YLIVIESKA, OULU, KEMI, ROVANIEMI, MISI, KEMIJÄRVI. Legend: Data In (blue), Data Output capacity (red), Left (red).
+
+Figure 4.1.1-3. The offload results with uplink speed of 750 Mbps.
+
+
+
+| Location | Data In (Mbits) | Data Output capacity (Mbits) | Left (Mbits) |
+|-------------|-----------------|------------------------------|--------------|
+| HELSINKI | 10000 | 200000 | 10000 |
+| PASILA | 10000 | 200000 | 10000 |
+| TIKKURILA | 180000 | 200000 | 10000 |
+| RIIHIMÄKI | 180000 | 200000 | 10000 |
+| HÄMEENLINNA | 150000 | 100000 | 10000 |
+| TAMPERE | 350000 | 1950000 | 10000 |
+| PARKANO | 220000 | 200000 | 10000 |
+| SEINÄJOKI | 300000 | 200000 | 150000 |
+| KOKKOLA | 500000 | 150000 | 400000 |
+| YLIVIESKA | 750000 | 150000 | 650000 |
+| OULU | 1050000 | 1050000 | 10000 |
+| KEMI | 300000 | 250000 | 10000 |
+| ROVANIEMI | 450000 | 450000 | 10000 |
+| MISI | 150000 | 100000 | 10000 |
+| KEMIJÄRVI | 250000 | 300000 | 10000 |
+
+Bar chart showing offload results for 1000 Mbps uplink speed across various locations. The Y-axis is 'Mbits' from 0,00 to 2500000,00. The X-axis lists locations: HELSINKI, PASILA, TIKKURILA, RIIHIMÄKI, HÄMEENLINNA, TAMPERE, PARKANO, SEINÄJOKI, KOKKOLA, YLIVIESKA, OULU, KEMI, ROVANIEMI, MISI, KEMIJÄRVI. Legend: Data In (blue), Data Output capacity (red), Left (red).
+
+Figure 4.1.1-4. The offload results with uplink speed of 1000 Mbps.
+
+Based on the example estimations presented in the figures 4.1.1-1 – 4.1.1-4, the required throughput speed for the offload should be at least 1 Gbps.
+
+Hence, in order to meet the requirement regarding the retention time and to minimize the required physical storage in the train, FRMCS needs to provide the means to transfer the CCTV archives from train to ground, i.e. enable means for CCTV offload.
+
+In a CCTV offload system, FRMCS provides means for transferring video surveillance data between a mobile communication unit in the train and ground communication units located at the depot and at the stations and/or stops alongside the predetermined route of the train. Whenever the train approaches the stations and/or stops or arrives into the depot, FRMCS facilitates the communication between the ground and mobile communication unit. The mobile communication unit in the train forwards the video surveillance data from the video recorder and/or directly from video
+
+surveillance cameras. The generic offload procedure between the ground and mobile communication units could be e.g as described in the following;
+
+- The ground communication unit is monitoring whether a transmission signal from the mobile communication unit is available and that the signal quality is sufficient for synchronization.
+- Upon successful synchronization, the ground communication unit requests offload from the mobile communication unit and the connection between the ground communication and mobile communication unit is established as soon as the sufficient signal quality is acknowledged by the FRMCS and mobile communication unit.
+- The transfer of CCTV archives from train to ground is started.
+- The ground communication system forwards the offloaded data further to the ground storage.
+- The transfer of CCTV archives continues as long as sufficient connection between the train and ground system is available and/or aborted by the FRMCS.
+
+Rail-bound mass transit requires the same functionality, however, the CCTV offload is even more challenging due to the shorter stop times of commuter trains.
+
+### 4.1.2 Requirements
+
+[R4.1.2-1] FRMCS shall facilitate the CCTV offload from train to ground when, during the train stops the stations and/or stops, stations, and whenever the train arrives into the stops and at the depot.
+
+[R4.1.2-2] The FRMCS shall be able to support that CCTV archives can be transferred into the ground system in a time and resource efficient way in dedicated places such as stations, train stops or train depots.
+
+[R4.1.2-3] The CCTV offload shall be initiated by the ground communication unit, once the sufficient signal quality is available between the ground and mobile communication units.
+
+[R4.1.2-4] The transfer of CCTV archives shall not affect mission critical communication.
+
+## 4.2 Bulk transfer of multimedia from ground to train
+
+### 4.2.1 Description
+
+The offering of multimedia services to the passengers is becoming default service during long travels in airplanes and more and more, also in trains. In order to minimize the excessive consumption of network capacity between train and ground, a bulk transfer of multimedia databases from ground to train during stops at the stations and depots is optimal solution. The bulk transfer of multimedia is done when the train stops at the stations, stops and depot, ideally with minimum of one gigabit transfer speed. Hence, the multimedia content can be more versatile and updated in regular basis. The actual content is also consumed in-train network operated by the FRMCS and hence it does not give burden to the link budget between train and ground. The multimedia may contain movies, TV shows, cached webpages etc.
+
+The bulk transfer of multimedia is facilitated by the FRMCS, which provides means for transferring the multimedia databases data between ground communication units, located at the depot, stations and/or stops alongside the predetermined route of the train. Whenever the train approaches the stations and/or stops or arrives into the depot, FRMCS facilitates the communication between the ground and mobile communication unit, if bulk transfer of multimedia transfer is requested. The ground communication unit uploads the multimedia databases from ground into the mobile communication unit in the train, where the data is stored in the train multimedia data storage. The generic procedure for the bulk transfer of multimedia between the ground and mobile communication units could be e.g as described in the following;
+
+- The ground communication unit is monitoring whether a transmission signal from the mobile communication unit is available and that the signal quality is sufficient for synchronization.
+- Upon successful synchronization, the mobile communication unit requests multimedia upload from the mobile communication unit and the connection between the ground communication and mobile communication unit is established as soon as the sufficient signal quality is acknowledged by the FRMCS and mobile communication unit.
+
+- The transfer of multimedia databases from ground to train is started.
+- The mobile communication system forwards the transferred multimedia databases further into the in-train storage.
+- The transfer of multimedia archives continues as long as sufficient connection between the train and ground system is available and/or aborted by the FRMCS.
+
+### 4.2.2 Requirements
+
+[R4.2.2-1] FRMCS shall facilitate the transfer of multimedia archives from ground to train.
+
+[R4.2.2-2] The FRMCS shall be able to support that multimedia databases can be transferred from ground to train in a time and resource efficient way, when the train stops at the stations, train stops and at the depot.
+
+[R4.2.2-3] FRMCS shall facilitate communication capabilities provided by the train.
+
+[R4.2.2-4] The transfer of multimedia databases shall not impact mission critical communication.
+
+## 4.3 Massive Inter-carriage data transfer
+
+### 4.3.1 Description
+
+The inter-carriage links between train vehicles enable sufficient capacity to enable massive data transfer throughout the train required e.g. for transfer of CCTV archives, multimedia databases and live streaming as well as for control, operational, and passenger services. Mobile communication unit in train provides connection between carriages of the train used, e.g. for the transfer of CCTV archives to a central node in the train from which the connection to the ground system will take place.
+
+### 4.3.2 Requirements
+
+[R4.3.2-1] The FRMCS shall facilitate the onboard communication between carriages of a train, e.g. to collect CCTV content at one place on the train for transfer to the ground system.
+
+[R4.3.2-2] The Inter-carriage links shall support at least the same throughput speed as the mobile communication unit of FRMCS providing the link between train and ground system.
+
+[R4.3.2-3] The onboard communication between carriages of a train shall not impact mission critical communication.
+
+## 4.4 Coexistence of automated train control with other train applications
+
+### 4.4.1 Description
+
+Train automation can be divided into control and operations. Both types consist of distributed applications that rely on dependable communication. Typically, control applications such as for automated train control are of higher priority than operational applications, and the latter are typically of higher priority than passenger services. One of the main challenges is to guarantee the premium priority of control-related communication over other types of communication, especially since the data bandwidth consumed for control is typically dwarfed by data traffic stemming from the other two application areas. Another challenge is to guarantee the super priority of operational data communication over passenger-related communication. Driverless trains are not the only source of automation in mass transit, and thus not the only source of dependable machine-type communication. For instance, mass transit train control (MTTC) including communication-based train control (CBTC) is also used for trains exhibiting lower grades of automation, if assisted by rail-to-rail-side wireless communication, which is at the core of driverless trains.
+
+Communication services for MTTC have to coexist with other high-priority and low-priority communication services. This coexistence is done assigning priorities to the communications, see below an example of how these priorities can be allocated:
+
+- The MTTC communication service might have the highest priority (train control).
+- The CCTV communication service might have high-priority, but lower than MTTC.
+- (High data rate) data communication services such as passenger internet access might be of low priority.
+- Emergency calls need to be established on demand with a priority suitable to guarantee call success independent of already running communication services.
+
+NOTE: This kind of emergency calls is using the train and rail infrastructure and not the public emergency services. An example for a train emergency system are microphone/speaker boxes that are integrated into the walls of the passenger area.
+
+The setup of high data rate communication services with low priority does not have an impact on the communication services for train control. Furthermore, the start-up of a communication service for train control will acquire sufficient resources in the 5G network, even if high data rate communication services with low priority are already running.
+
+### 4.4.2 Requirements
+
+[R4.4.2-1] High priority communication services, especially their end-to-end latency and availability, shall not be affected by communication services of lower priority running in parallel.
+
+[R4.4.2-2] The start-up of high-priority communication services shall not be affected by already running services with different priorities.
+
+# 5 Performance requirements for main line
+
+## 5.1 Environmental conditions
+
+Rail communication is subject to much diverse limitations in urban and sparsely populated areas. Depending on the landscape, the construction of tunnels, e.g. underground or mountain crossing, or the construction of new tracks, the embedding of railway lines within aisles, through uninhabited areas is required. Tunnels are specific and require separate consideration in signal propagation through the changing fill factor. Here, the use of leaky feeder cables is essential.
+
+Crucial constraints for the provision of performance factors are summarized in a non-exhaustive list below:
+
+- Free space;
+- Railway corridors in general and especially in hilly terrain;
+- Railway corridors through forest areas;
+- Underground / tunnel environment;
+- Moving trains or objects in a railway station and shunting yards;
+
+## 5.2 Low latency and high reliability
+
+### 5.2.1 Overview
+
+In future, for example trains will simultaneously exchange control information and status information with the responsible traffic management system on the ground. This procedure is a key factor for automated operation without a driver. Nonetheless, also traditional voice communication is needed to allow train staff to communicate with the ground staff.
+
+Trains are operated at speeds up to 500 km/h. Under these conditions voice, video and data communication are to be provided. Especially train control communication is of extreme importance to ensure passengers safety.
+
+In normal rail operation and in the context of Grade of Automation (GoA3 and GoA4) video/radar/lidar sensors on trains and on ground will be used to:
+
+- detect hazards on tracks, and
+- ensure a safe passenger (dis-)embarkation (e.g., ensure that passengers are not stuck in doors, or between platform and train, when trains depart, and trigger emergency braking or postpone train departure if any hazardous situation is detected).
+
+The relative braking distance of a rail vehicle is an important indicator of the safety, which is significantly influenced by the transmission reliability between train and controller at low speeds up to 40 km/h. This mainly applies to the entry and exit of trains in the station area or displacement manoeuvres within marshalling yards. The reliability and latency of the transmission of the control command signalling of speeds up to 40 km/h has a direct impact on the braking distance.
+
+### 5.2.2 Scenarios and KPIs for main line
+
+To support this various voice, video and data categories, the following rail communication scenarios under the aspect of train speed shall be considered:
+
+- **Voice Communication** for operational purposes impacting train safety
+- **Critical Video Communication** for observation purposes with indirect impact on train operation, e.g. passenger surveillance;
+- **Very Critical Video Communication** with direct impact on train safety- related critical train control and operation, e.g. used in driverless (e.g. Grade of Automation - GoA3/GoA4) operation for automated detection of objects (no human in the loop) or video-based remote control (human in the loop);
+- **Standard Data Communication** used for the exchange of train diagnostic information or communication relevant information;
+- **Critical Data Communication** for present rail traffic management systems;
+- **Very Critical Data Communication** for enhanced intelligent rail traffic management systems e.g. full automated train control systems (driverless – remote control); requires high reliable transmission and preservation of the response pattern;
+- **Messaging** for the reliable exchange of short information e.g. train departure procedure;
+
+| Scenario | End-to-end latency | Reliability (Note 1) | Speed limit | User experience d data rate | Payload size (Note 2) | Area traffic density | Service area dimension (note 3) |
+|----------------------------------------------------------------------|--------------------|----------------------|-------------|-----------------------------|-----------------------|----------------------|-----------------------------------------|
+| Voice Communication for operational purposes | ≤100 ms | 99,9% | ≤500 km/h | 100 kbps up to 300 kbps | Small | Up to 1 Mbps/line km | 200 km along rail tracks |
+| Critical Video Communication for observation purposes | ≤100 ms | 99,9% | ≤500 km/h | 10 Mbps | Medium | Up to 1 Gbps/km | 200 km along rail tracks |
+| Very Critical Video Communication with direct impact on train safety | ≤100 ms | 99,9% | ≤500 km/h | 10 Mbps up to 20 Mbps | Medium | Up to 1 Gbps/km | 200 km along rail tracks |
+| | ≤10 ms | 99,9% | ≤40 km/h | 10 Mbps up to 30 Mbps | Medium | Up to 1 Gbps/km | 2 km along rail tracks urban or station |
+| Standard Data Communication | ≤500 ms | 99,9% | ≤500 km/h | 1 Mbps up to 10 Mbps | Small to large | Up to 100 Mbps/km | 100 km along rail tracks |
+| Critical Data Communication | ≤500 ms | 99,9999% | ≤500 km/h | 10 kbps up to 500 kbps | Small to medium | Up to 10 Mbps/km | 100 km along rail tracks |
+| Very Critical Data Communication | ≤100 ms | 99,9999% | ≤500 km/h | 100 kbps up to 1 Mbps | Small to Medium | Up to 10 Mbps/km | 200 km along rail tracks |
+| | ≤10 ms | 99,9999% | ≤40 km/h | 100 kbps up to 1 Mbps | Small to Medium | Up to 100 Mbps/km | 2 km along rail tracks |
+| Messaging | - | 99,9% | ≤500 km/h | 100 kbps | Small | Up to 1 Mbps/km | 2 km along rail tracks |
+
+NOTE 1: Reliability as defined in sub-clause 3.1.
+NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.
+NOTE 3: Estimates of maximum dimensions.
+
+**Table 5.2.2-1 Performance requirements for rail scenarios – main line**
+
+NOTE: All values in Table 5.2.2-1 are target values and assumes the use of a dedicated network for rail communication.
+
+End-to-end latency and reliability of the communication scenarios listed in Table 5.2.2-1 shall be applied separately from the individually used priority of the communication.
+
+To support off network communication, data categories, the following rail communication scenarios under the aspect of train speed shall be considered:
+
+- **Very Critical Data Communication** for enhanced intelligent rail traffic management systems e.g. virtual coupling; requires high reliable transmission and preservation of the response pattern;
+
+| Scenario | End-to-end latency | Reliability (Note 1) | Speed limit | User experience d data rate | Payload size (Note 2) | Area traffic density | Service area dimension (Note 3) | Max required communication range (meters) (Note 4) |
+|----------------------------------|--------------------|----------------------|-------------|-----------------------------|-----------------------|----------------------|---------------------------------|----------------------------------------------------|
+| Very Critical Data Communication | ≤100 ms | 99,9999% | ≤500 km/h | 100 kbps up to 1 Mbps | Small to Medium | Up to 10 Mbps/km | 3 km along rail tracks | [1000 ~ 3000] |
+| | ≤300 ms | 99,9% | ≤40 km/h | 100 kbps up to 1 Mbps | Small to Medium | Up to 100 Mbps/km | 3 km along rail tracks | [1000 ~ 3000] |
+
+NOTE 1: Reliability as defined in sub-clause 3.1.
+NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.
+NOTE 3: Estimates of maximum dimensions.
+NOTE 4: Relevant for Off-Network MCData Service only, supporting train platooning. All trains in a platoon are driving in the same direction.
+
+**Table 5.2.2-2 Performance requirements for rail scenarios – off network communication**
+
+### 5.2.3 Communication establishment
+
+The duration of time for establishing a communication between entities, e.g. after network change or loss of communication, the braking distance between vehicles and its impact to the risk integral is crucial. Based on this, the following communication setup times of a communication shall be provided:
+
+| Type | FRMCS | Interworking with GSM-R | Interworking with LMR |
+|-----------------------------------------------|--------|------------------------------------------------------|---------------------------------------|
+| Immediate communication session establishment | ≤1 sec | ≤1 sec + call setup time as defined in table 3-1 [8] | ≤1 sec + LMR call setup time (Note 1) |
+| Normal communication session establishment | ≤3 sec | ≤3 sec + call setup time as defined in table 3-1 [8] | ≤3 sec + LMR call setup time (Note 1) |
+
+Note 1: In the interworking, the setup times are considered with 3GPP side only. Extra times may be applied depend on interworking communication technology.
+
+**Table 5.2.3-1 Communication setup times**
+
+# 6 Performance requirements for rail-bound mass transit
+
+## 6.1 Environmental conditions
+
+Rail-bound mass transit communication is required mostly in tunnels and urban areas. Tunnels are specific and require separate consideration in signal propagation, e.g for waveguide like non-line-of-sight communication, changing cross-section or blocking/shadowing by other trains. Here, the use of leaky feeder cables can be essential depending on the deployment scenario. Within urban areas the interference through other users and the multi-path propagation in conjunction with a high velocity have to be considered. In both environments a high train density has to be considered, especially in stations and shunting yards or depots.
+
+## 6.2 Low latency and high reliability
+
+### 6.2.1 Overview
+
+Low latency and high reliability, high communication service availability, and dependability of communication are important service and performance requirements for mass transit train control (MTTC) such as communication based train control (CBTC). They are necessary to provide high grades of automation such as necessary for e.g. driverless trains. Furthermore, trains will simultaneously exchange control information and status information with the responsible traffic management system on the ground.
+
+Trains are operated at speeds up to 160 km/h. The communication for rail-bound mass transit has to be provided under these conditions.
+
+Especially train control communication is of extreme importance to ensure passengers safety. The relative braking distance of a rail vehicle is an important indicator of the safety requirements.
+
+### 6.2.2 Scenarios and KPIs for rail-bound mass transit
+
+#### 6.2.2.1 Overview
+
+There are three main drivers behind the growing importance of communication services in rail-bound mass transit: (1) train automation (2) operational data, and (3) passenger information.
+
+Caused by increased safety awareness, onboard video surveillance/CCTV and emergency calls play an increasing role in order to setup communication with passengers during emergencies, e.g., when trains have to stop inside tunnels. CCTV is required for high grades of automation by regulation.
+
+Communication for rail-bound mass transit can be associated with different communication patterns as described in TS 22.104 [7] Clauses 4.3 and 4.4 and as used in communication for cyber-physical control applications in vertical domains.
+
+*Periodic deterministic communication* is periodic with stringent requirements on timeliness and availability of the communication service. A transmission occurs every transfer interval.
+
+*Aperiodic deterministic communication* is without a pre-set sending time, but still with stringent requirements on timeliness and availability of the communication service.
+
+*Non-deterministic communication* subsumes all other traffic types than periodic/aperiodic deterministic communication. This includes periodic/aperiodic non-real-time traffic.
+
+*Mixed traffic* cannot be assigned to one of the other communication patterns exclusively.
+
+#### 6.2.2.2 Scenarios and KPIs for rail-bound mass transit
+
+Coexistence of automated train control with other train applications: A train is operated in an automated manner, and the communication of the train controller with the rail side co-exists with traffic generated by other applications.
+
+The following communication scenarios of rail-bound mass transit shall be considered in order to support the coexistence of automated train control with other train applications:
+
+*Use case 1:* Periodic communication for train control.
+
+*Use case 2:* Communication serving CCTV cameras streaming within the train and to the rail-side.
+
+*Use case 3:* Emergency call from the train to a remote control centre via the mass-transit communication system.
+
+The following communication scenario shall be considered in order to support train coupling in rail-bound mass transit:
+
+*Use case 4:* Wireless communication link between two coaches; the link carries traffic from many applications.
+
+The following communication scenario shall be considered in order to support rail-bound mass transit:
+
+*Use case 5:* CCTV offload in train stations.
+
+A *characteristic parameter* can be used to characterise the dynamic behaviour and performance of the functionality of the communication service of the 5G network (key performance indicator).
+
+A communication service is considered unavailable in case an expected message is not received within a specified time, which, at minimum, is the sum of maximum end-to-end latency and survival time. The end point in "end-to-end latency" is assumed to be the communication service interface between the application and the 5G system (cf. TS 22.104 [7] Annex C).
+
+Mean time between failures (MTBF) is one of the typical indicators for communication service reliability. This parameter states the mean value of how long the communication service is available before it becomes unavailable. For instance, a mean time between failures of one month indicates that a communication service runs error-free for one month on average before an error makes the communication service unavailable. Usually, an exponential distribution is assumed. This means, there will be several failures where the time between two subsequent errors is below the mean value (1 month in the example).
+
+Availability and reliability together indicate frequency and duration of acceptable unavailabilities of a communication service.
+
+An *influence quantity* is not essential for the characterisation of the dynamic behaviour of an item but it affects the performance of the characteristic parameter of an item.
+
+Further information on characteristic parameters and influence quantities used in Table 6.2.2.3-1 can be found in TS 22.104 [7] Annex C.
+
+The 5G system shall support the communication service performance requirements (KPIs) reported in Table 6.2.2.3-1.
+
+Table 6.2.2.3-1: Characteristic parameters (KPIs) of communication service performance requirements for rail-bound mass transit
+
+| Use case | Characteristic parameters | | | | Influence parameters | | | | | | |
+|-----------------------------------------------------------------|-----------------------------------------------------------|---------------------------------------------------------------|--------------------------------------|----------------------------------------------|-------------------------|--------------|---------------------------------|---------------|------------|----------|-----------------------|
+| | Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (note 2) | Service bit rate: user experienced data rate | Communication pattern | Message size | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area (note 3) |
+| 1: Control of automated train (note 4) | 99,999 % | below 1 year but >>1 month | <100 ms | ≥200 kbit/s | periodic deterministic | ≤200 byte | 100 ms | ~500 ms | ≤160 km/h | <25 | 50 km x 200 m |
+| 2: CCTV communication service for surveillance cameras (note 4) | >99,99 % | ~1 week | <500 ms | ≥2 Mbit/s | aperiodic deterministic | | | ~500 ms | ≤160 km/h | <25 | 50 km x 200 m |
+| 3: Emergency voice call (note 4) | >99,99 % | ~1 day | <200 ms | ≥200 kbit/s | aperiodic deterministic | | | ~2 s | ≤160 km/h | <25 | 50 km x 200 m |
+| 4: Train coupling | >99,9999 % | ~1 year | <100 ms | 1 Gbit/s | mixed traffic | | | ~500 ms | – (note 5) | 2 | 3 m x 1 m |
+| 5: CCTV offload in train stations | | | | ≥1 Gbit/s | non-deterministic | | | | ~0 km/h | ≥1 | train station |
+
+NOTE 1: One or more retransmissions of network layer packets may take place in order to satisfy the communication service availability requirement.
+
+NOTE 2: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+
+NOTE 3: Length x width.
+
+NOTE 4: 2 UEs per train car, column "# of UEs" is per train, there are multiple trains in the given service area.
+
+NOTE 5: UE speed is irrelevant since this communication takes place between two train segments.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2018-12 | SA#82 | SP-181001 | - | - | - | Presentation for one-step approval to SA | | 1.0.0 |
+| 2018-12 | SA#82 | SP-181001 | - | - | - | Raised to v.16.0.0 following SA#82's one-step approval | | 16.0.0 |
+| 2019-03 | SA#83 | SP-190084 | 0002 | 1 | D | Editorial corrections to TS 22.289 | | 16.1.0 |
+| 2019-03 | SA#83 | SP-190081 | 0001 | 2 | F | Moving rail-bound mass transit requirements – shift into FRMCS | | 16.1.0 |
+| 2019-12 | SA#86 | SP-191030 | 0006 | 2 | B | Call setup time for interworking with LMR | | 17.0.0 |
+| 2019-12 | SA#86 | SP-191030 | 0007 | 2 | B | Off network communication for interworking with LMR | | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22340/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-18/22_series/22340/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34717f88fbde793fa2bdbc1fd96aab0bb2a01467
--- /dev/null
+++ b/marked/Rel-18/22_series/22340/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bda4ed856f5b8efcc7d8fb119ddc3dfaa6d779424ac67e9435214a187fb09f46
+size 40903
diff --git a/marked/Rel-18/22_series/22340/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22340/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d071b557c8648bb111295a969536da818767566
--- /dev/null
+++ b/marked/Rel-18/22_series/22340/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4651ada5d7b3a7210a04d8d6333a8f5c9d47e59248eb82cadf46b1e2ef862726
+size 8253
diff --git a/marked/Rel-18/22_series/22340/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22340/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d107e5ab554572172d9c1fe82c7e805eac754206
--- /dev/null
+++ b/marked/Rel-18/22_series/22340/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2737ce6737c2d983c8a528d43f16428340a5bd69c59a81f687d1da5b0d2ac8f
+size 7268
diff --git a/marked/Rel-18/22_series/22340/raw.md b/marked/Rel-18/22_series/22340/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..37443b322df9d8e9e18f4a3d04ccb92aa6da94f7
--- /dev/null
+++ b/marked/Rel-18/22_series/22340/raw.md
@@ -0,0 +1,558 @@
+
+
+# 3GPP TS 22.340 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) messaging; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font. The 'G' has a red signal wave icon at its base, and a 'TM' trademark symbol is located to the upper right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+UMTS, IMS, stage 1
+
+## **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-----------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions, symbols and abbreviations..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Informative description of messaging services in the IMS..... | 7 |
+| 5 Informative description of messaging types ..... | 8 |
+| 6 Immediate messaging requirements..... | 8 |
+| 6.1 General requirements ..... | 8 |
+| 6.2 Message content requirements ..... | 9 |
+| 6.3 Management requirements ..... | 9 |
+| 6.4 Message delivery requirements..... | 9 |
+| 6.5 Storage requirements..... | 10 |
+| 6.6 User privacy requirements ..... | 10 |
+| 6.7 Message Filtering..... | 10 |
+| 7 Session based messaging requirements..... | 11 |
+| 7.1 General requirements ..... | 11 |
+| 7.2 Message content requirements ..... | 12 |
+| 7.3 Management requirements ..... | 13 |
+| 7.4 Message delivery requirements..... | 13 |
+| 7.5 Storage requirements..... | 13 |
+| 7.6 User privacy requirements ..... | 14 |
+| 7.7 Message Filtering..... | 14 |
+| 8 Addressing requirements..... | 15 |
+| 9 Security ..... | 15 |
+| 10 Charging..... | 15 |
+| 11 Interworking..... | 16 |
+| 11.1 General ..... | 16 |
+| 11.2 Requirements for SMS-Immediate Messaging service-level interworking ..... | 16 |
+| 11.3 Requirements for SMS-Session based Messaging service-level interworking..... | 17 |
+| Annex A (informative): Change history..... | 19 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+In today's world there are many different types of messaging services available both in the wired and wireless worlds. Some messaging services are supported in both environments; others are only to be found in one. The expectations of the services differ in that some are designed to be used in what is perceived as 'real' time, whereas others are designed as a 'mailbox' service where the message is stored ready for collection or delivery at a later stage.
+
+The 3GPP Technical Report TR22.940 identifies the issues and needs surrounding messaging solutions related to the 3GPP IP Multimedia Subsystem (IMS) taking into consideration use cases that illustrate the needs of both service providers and users. This Technical Specification takes the Technical Report into account when defining the requirements for the support of IMS Messaging.
+
+IMS Messaging services incorporates one or more of the following messaging types Immediate messaging and Session based messaging. With Immediate messaging the sender expects immediate message delivery in what is perceived as real time. With Session based messaging a communications association is established between two or more users before communication can take place. In the simplest form Session based messaging maybe a direct communication between two users. This specification defines the requirements for both the Immediate message type and the Session based message type.
+
+The specification provides the ability to develop interoperable messaging services that use Immediate and/or Session based message types.
+
+# 1 Scope
+
+The present document specifies the stage one description of the IMS Messaging services. Stage one is an overall service description and defines service requirements, primarily from the subscriber's and service providers' points of view, and does not deal with the details of the human interface itself.
+
+The present TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
+
+The present TS contains the requirements for IMS Messaging services, which are sufficient to provide a complete service. The messaging types identified in this document are: immediate messaging and session based messaging.
+
+It is highly desirable that technical solutions for IMS Messaging services should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this 3GPP TS may implement requirements which are considered outside the scope of this 3GPP TS. Such additional functionality shall not compromise conformance to the core requirements of the service.
+
+# 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] Void
+- [2] 3GPP TS 22.250: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Stage 1, IMS Group Management
+- [3] RFC 2486: "The Network Access Identifier"
+- [4] 3GPP TS 21.133; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Threats and Requirements
+- [5] 3GPP TS 26.140; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Messaging Service (MMS); Media formats and codecs
+- [6] 3GPP TS 26.234: "End-to-end transparent streaming Service (PSS); Protocols and Codecs".
+- [7] 3GPP TS 22.228; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the Internet Protocol (IP) multimedia core network subsystem; Stage 1
+- [8] 3GPP TS 26.244: "Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)";
+- [9] 3GPP TS 26.245: "Transparent end-to-end packet switched streaming service (PSS); Timed text format".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+**Immediate messaging:** A type of IMS Messaging service by which the sender expects immediate message delivery in (near) real time fashion
+
+**IMS Messaging services:** A group of services, supported by capabilities of the 3GPP IP Multimedia Subsystem 3GPP TS 22.228 [7], that allows an IMS user to send and receive messages to other users. IMS messaging services comprise of one or more types: Immediate messaging and Session based messaging.
+
+**Session based messaging:** A type of IMS Messaging service by which the sender expects immediate message delivery in (near) real time fashion . In addition the sender(s) and the receiver(s) have to join to a messaging session e.g. chat room, before message exchange can take place
+
+## 3.2 Abbreviations
+
+| | |
+|-----|-------------------------|
+| IP | Internet Protocol |
+| IMS | IP Multimedia Subsystem |
+| OMA | Open Mobile Alliance |
+
+# 4 Informative description of messaging services in the IMS
+
+As 3GPP has developed the concept of IMS it is thought useful to consider how a SIP based IP network can be utilised to provide messaging capabilities. One of the chief characteristics of SIP is its ability to rapidly and efficiently create real-time sessions between groups of users. It therefore appears that SIP based messaging would be a potential candidate to provide the equivalent of “Chat Room” and “Instant Messaging” (IM) type services found on the Internet today. Typical characteristics instant messaging are instant delivery of the messages to the targeted recipient(s) and interaction with presence information where users are able to see who is on-line as well as their status.
+
+A chat room is a "place" where multiple persons can join, follow and contribute to the ongoing discussion and leave the "room" at any time. Chat rooms are more permanent in nature when compared to IM exchanges and may be created by users or service providers. Additionally, chat rooms can be further divided to the private and public chat rooms. Normally, users who are participating in chat room will receive all the messages that are sent by the other participants. Similarly, the users are also able to send private messages to the chat room or even privately to some participant.
+
+Unfortunately, the most popular internet based instant messaging services are usually based upon closed and proprietary protocols which has made it impossible for different service providers to allow interoperable messaging between their respective users. Additionally, internet based services do not take into consideration the wireless environment and the needs of operators to provide services that are commercially viable by for example, providing support for charging. This technical specification will further elaborate the essential messaging characteristic of these services and state how they may be enhanced, e.g. operators may be able to create and then advertise chat rooms containing specific content where users who join the room may be charged an 'entrance' fee,
+
+
+
+The diagram illustrates a central 'Chat Server' represented by a cylinder. Four participants, represented by stick figures with envelopes, interact with the server:
+
+- Harry** (top left) sends a 'Join to chat' request and a 'Message' to the server. The server responds with a 'Message'.
+- Peter** (top right) sends a 'Message' to the server. The server responds with a 'Message'.
+- Ken** (bottom right) sends a 'Send a private message to Ken' to the server. The server responds with a 'Message'.
+- Amanda** (bottom) sends a 'Join to chat' request and an 'Invite Amanda to join to chat' to the server.
+
+Diagram illustrating an Example IMS Messaging service: Chat room. A central Chat Server is shown. Harry, Peter, Ken, and Amanda are participants. Harry sends a 'Join to chat' request and a 'Message' to the server. Peter sends a 'Message' to the server. Ken sends a 'Send a private message to Ken' to the server. Amanda sends a 'Join to chat' request and an 'Invite Amanda to join to chat' to the server. The server sends 'Message' responses to Harry, Peter, and Ken.
+
+Figure 1. Example IMS Messaging service: Chat room
+
+# 5 Informative description of messaging types
+
+Messaging can be divided to two different main classes based on the expectation of the sender. The sender either expects the message to be delivered immediately or he does not care so much whether the message is delivered immediately or later.
+
+The immediate case can be further divided to two different sub-classes based on the actions required from the user before he can engage in a communication. The user can both send and receive messages without any prior actions or he may be required to join to a messaging session before the message exchange can take place.
+
+The messaging types considered in this specification are
+
+### - **Immediate messaging:**
+
+Typically, sender is aware of the availability of the recipient(s) (possibly through the use of the Presence service) before sending this type of message as, if the recipient is not available, the message may be discarded or deferred. An immediate message may be deferred by the recipient's network based on the message filtering settings defined by the recipient or by the recipient's IMS service provider.
+
+### - **Session based messaging:**
+
+The sender and recipient expect near real time message delivery. Typically, recipients of the session based messaging that are not joined to a group or are not available will not receive the messages. Typically, a sender may send a message to all participants in the messaging session without addressing them individually.
+
+# 6 Immediate messaging requirements
+
+## 6.1 General requirements
+
+Network operators have different network configuration and commercial requirements. IMS Messaging shall be supported in a manner that meets the operator's IMS requirements. Thus, an identified set of functionalities and formats shall be standardized to ensure interoperability across networks and terminals to support IMS Messaging.
+
+The following general requirements shall be supported by Immediate messaging.
+
+- a) It shall be possible for the UE and the network to differentiate between immediate messages from other messaging types.
+- b) Within the capabilities of networks and terminals, the user shall have a consistent experience regardless of the access network e.g. 3GPP systems, fixed networks, the Internet.
+- c) Immediate messaging shall support a minimum set of functionality for message delivery, management and filtering to ensure interoperability between different terminals and networks.
+- d) Immediate messaging shall be able to support the ability of the recipient's network to take into account the recipient's terminal capabilities. In addition, the originating network/terminal may also be able to take into account recipient's terminal capabilities. Specifically the recipient's terminal capabilities that may be taken into account at a minimum include:
+ - 1) Display capabilities (including screen size, number of colours, number of lines of text, etc);
+ - 2) Media content types supported (Audio, Video etc);
+ - 3) Media content formats supported (JPEG, GIF, etc);
+ - 4) Media Storage capacity;
+ - 5) Encryption/Security mechanisms supported
+
+The capabilities of the user's terminal may be reflected in the message filtering and corresponding actions as identified in clause 6.7.
+
+- e) Immediate messaging should be able to take into account the availability and changes of the state of availability of the terminal. Immediate messaging shall be able to make use of the Presence Service, if provided by the network.
+- f) It shall be possible to store in the ISIM a number of sets of configuration information to allow access to Immediate messaging services. One of these sets of configuration information is preset by the issuer of the ISIM. Such preset configuration information set shall only be configurable by issuer of the ISIM. The preset configuration information is selected unless otherwise specified by the user. It shall be possible to retain the configuration information when the UICC is used in different terminals.
+- g) It shall be possible to send and receive immediate messages without prior establishing a messaging session.
+- h) It shall be possible for the network operator providing the Immediate messaging service to choose, wherever possible, the most suitable transport mechanism for carrying messages (e.g. signalling network, dedicated PDP context, other access technologies and so on...) both for UE originated and UE terminated messages.
+- i) It shall be possible for the network operator providing the Immediate messaging service to choose, wherever possible, the parameters used (i.e. QoS) both for UE originated and UE terminated messages.
+
+## 6.2 Message content requirements
+
+Following requirements are specific to content delivered with immediate messaging.
+
+- a) Content size shall not be limited by technology.
+- b) It shall be possible to carry different media including text, images, video and audio within a single message. Media types shall be MIME encoded.
+- c) Immediate messaging shall provide a minimum set of supported formats to ensure full interoperability between different terminals and networks (e.g. JPEG for pictures, AMR for speech, H.263 for video). The minimum set of supported formats shall be common to all IMS Messaging types. The minimum set of supported formats should be aligned with formats used in other 3GPP-defined services 3GPP TS 26.140 [5], 3GPP TS 26.234 [6].
+- d) Content formats shall be defined so that interworking with 3GPP and Internet messaging solutions is facilitated.
+- e) It shall be possible to compose message of either a single medium (e.g. voice) or multi-media (e.g. voice and video). The IMS Messaging service shall be able to support a request for media sequencing.
+
+## 6.3 Management requirements
+
+The following management requirements shall be supported.
+
+- a) The IMS service provider shall be able to enable/disable message delivery and submission.
+- b) Immediate messaging shall be able to support a request from the user to enable/disable message delivery.
+- c) Immediate messaging shall be able to support the user to manage his user service profile related to Immediate messaging (e.g. customize his messaging environment within the capabilities of the terminal, network and messaging application). This could be unconditional or conditional e.g. depending on roaming conditions or operator restrictions.
+- d) Immediate messaging shall allow an IMS service provider to configure Immediate messaging environment e.g. in such a way that submitted and/or incoming Immediate messages of a particular user are stored in a network based repository.
+
+## 6.4 Message delivery requirements
+
+Following requirements define the message delivery.
+
+- a) Message delivery shall be immediate i.e. messages are transported by the IMS system to the recipient's terminal (without notifications) subject to message filtering settings defined by the recipient or by the recipient's IMS service provider.
+
+- b) Messages shall not be stored by the network. If supported by the recipient's network as an application option messages may be stored in the recipients network.
+- c) It shall be possible for the sender to receive delivery acknowledgements (success/failure) for sent messages.
+
+## 6.5 Storage requirements
+
+The following storage requirements shall be supported.
+
+- a) It shall be possible for a sender to request to persistently store a sent Immediate message in a network based repository at the time of sending if the IMS service provider provides such application level service.
+- b) Immediate messaging shall be able to support a request from a user to retrieve messages that are stored in a network based repository.
+- c) Immediate messaging shall be able to support a request from a user to delete messages that are stored in a network based repository.
+- d) Immediate messaging shall be able to support a request from a user to forward one or more messages that are stored in a network based repository to another destination.
+- e) Immediate messaging shall be able to support a request from a user to view the list of messages and message related attributes, such as sender, recipient, subject and date/time, in a network based repository.
+- f) Immediate messaging shall be able to support a request from a user to upload one or more Immediate messages into a network based repository for persistent storage.
+
+## 6.6 User privacy requirements
+
+Following requirements define user privacy.
+
+- a) It shall be possible for the recipient to see the public ID of the sender of the message unless the sender has requested to hide it.
+- b) It shall be possible for the sender of the message to request to hide its public ID from the recipient (anonymous sender).
+
+The sender's public ID shall not be delivered to the recipient. The capability of public ID hiding is an IMS service provider and legislation issue and it may or may not be available. If the service is not available the message shall not be delivered to the recipient.
+
+## 6.7 Message Filtering
+
+It shall be possible for a subscriber to set up, modify, and delete filters in the network of the subscriber's IMS service provider, in order to control the treatment of a message by the network when an immediate message is received when the subscriber is either unavailable or when the subscriber does not currently want to receive messages. The filters shall also support the ability of the subscriber to specify the maximum size and type of message content etc that they are or are not willing to accept. The filters shall also support the ability of the subscriber to block (and unblock) messages from specific senders or anonymous senders.
+
+Following specific requirements define the message filtering capabilities of the recipient.
+
+- a) It shall be possible to define specific message treatment based on following criteria
+ - 1) sender address (including anonymous senders);
+ - 2) message size;
+ - 3) message class (e.g. advertisement, private....);
+ - 4) message priority;
+ - 5) message content type (e.g. video, audio....);
+
+- 6) message content format (e.g. mpeg, jpeg....);
+ - 7) message type (e.g. immediate message);
+ - 8) message subject;
+ - 9) availability of the recipient; and
+ - 10) additional criteria maybe possible but are outside the scope of this document..
+- b) It shall be possible to specify the following message treatments in a filter:
+- 1) Block the delivery of the message content.
+ - 2) Store the message content and notify recipient.
+ - 3) Store the message content for a specific time or until the recipient requests delivery.
+ - 4) Store and push the message content to recipient when available.
+ - 5) Redirect the message to another address.
+ - 6) Additional treatments maybe possible but are outside the scope of this document.
+
+The IMS service provider shall also be able to set and control the filter settings either on behalf of the subscriber or based on policy.
+
+# --- 7 Session based messaging requirements
+
+## 7.1 General requirements
+
+Network operators have different network configuration and commercial requirements. IMS Messaging shall be supported in a manner that meets the operator's IMS requirements. Thus, an identified set of functionalities and formats shall be standardized to ensure interoperability across networks and terminals to support IMS Messaging.
+
+The following general requirements shall be supported.
+
+- a) There shall be a mechanism to differentiate session based messages from other messaging types.
+- b) Within the capabilities of networks and terminals, the user shall have a consistent experience regardless of the access network e.g. 3GPP systems, fixed networks, the Internet.
+- c) Session based messaging shall support a minimum set of functionality to ensure interoperability between different terminals and networks.
+- d) Session based messaging shall be able to take into account the capabilities of the terminals participating in the messaging session. Specifically the terminal capabilities that may be taken into account at a minimum include:
+ - 1) Display capabilities (including screen size, number of colours, number of lines of text, etc);
+ - 2) Media content types supported (Audio, Video etc);
+ - 3) Media content formats supported (JPEG, GIF, etc);
+ - 4) Media Storage capacity;
+ - 5) Encryption/Security mechanisms supported
+
+The capabilities of the user's terminal may be reflected in the message filtering and corresponding actions as identified in clause 7.7.
+
+- e) It shall be possible to store in the ISIM a number of sets of configuration information to allow access to IMS Messaging services. One of these sets of configuration information is preset by the issuer of the ISIM. Such preset configuration information set shall only be configurable by issuer of the ISIM. The preset configuration
+
+information is selected unless otherwise specified by the user. It shall be possible to retain the configuration information when the UICC is used in different terminals.
+
+- f) It shall be possible for the subscribers to join to a session e.g. chat room.
+- g) It shall be possible for the subscribers to leave a session e.g. chat room.
+- h) It shall be possible to send a message to all the participants of a messaging session without specifying the individual participant's addresses or using a message delivery list.
+- i) It shall be possible to invite new participants to the existing messaging session.
+ - 1) The invitations shall be semi permanent i.e. it is not required that invitee will act immediately.
+ - 2) It shall be possible to cancel the invitation by the inviter.
+ - 3) It shall be possible for the inviter to define the validity period of the invitation.
+ - 4) It shall be possible for the invitee to see the originator of the invitation unless the inviter has required hiding his public ID.
+ - 5) It shall be possible for the inviter to define the messaging session to which the invitation is made.
+ - 6) It shall be possible for the invitee to identify the messaging session to which he was invited.
+- j) It shall be possible for the recipient of the message to identify from which messaging session the message came from (for both public and private messages).
+- k) It shall be possible for the recipient to identify the sender (unless the sender has required hiding its public ID) of the message in addition to the messaging session from which the message came from.
+- l) It shall be possible for the sender to send a private message for a selected recipient.
+- m) It shall be possible for the recipient to determine if the message was sent as a private message within a messaging session.
+- n) It shall be possible for the subscriber to request the message session properties e.g. list of active members.
+- o) It shall be possible for the subscriber to automatically receive updates containing the changes in message session properties e.g. change in the list of active members.
+- p) It shall be possible to utilize IMS Group Management 3GPP TS 22.250 [2] as appropriate.
+- q) It shall be possible for a subscriber in an IMS Messaging session to request and to receive an indication of when user is entering a message ("Is typing"). This request may apply to a specific user or users in the same session. Subject to privacy requirements, the corresponding indications will identify the persons who are entering a message.
+- r) It shall be possible for the network operator providing the IMS Messaging service to choose, wherever possible, the most suitable transport mechanism for carrying messages (e.g. signalling network, dedicated PDP context, other access technologies and so on...)
+- s) It shall be possible for the network operator providing the IMS Messaging service to choose, wherever possible, the parameters used (i.e. QoS)
+- t) The operator shall be able to enforce the use of the preferred transport mechanism and parameters both for UE originated and UE terminated messages.
+
+## 7.2 Message content requirements
+
+Following requirements are specific to content delivered with session based messaging.
+
+- a) Content size shall not be limited by technology.
+- b) It shall be possible to carry different media including text, images, video and audio. Media types shall be MIME encoded.
+
+- c) Session based messaging shall provide a minimum set of supported formats to ensure full interoperability between different terminals and networks (e.g. JPEG for pictures, AMR for speech, H.263 for video). The minimum set of supported formats shall be common to all IMS Messaging types. The minimum set of supported formats should be aligned with formats used in other 3GPP-defined services 3GPP TS 26.140 [5], 3GPP TS 26.234 [6].
+- d) Content formats shall be defined so that they enable interworking with 3GPP and Internet messaging solutions.
+- e) It shall be possible to compose message of either a single medium (e.g. voice) or multi-media (e.g. voice and video). The IMS Messaging service shall be able to support a request for media sequencing.
+
+## 7.3 Management requirements
+
+The following management requirements shall be supported.
+
+- a) IMS Messaging shall be able to support a request from the IMS service provider to enable/disable message delivery and submission.
+- b) IMS Messaging shall be able to support a request from the user to enable/disable message delivery and submission.
+- c) IMS Messaging shall be able to support the user to manage his user service profile related to IMS Messaging (e.g. customize his messaging environment within the capabilities of the terminal, network and messaging application). This could be unconditional or conditional e.g. depending on roaming conditions or operator restrictions.
+- d) It shall be possible for IMS service provider to configure messaging session environment e.g. in such a way that all incoming IMS Messages are stored in a network based repository.
+- e) It shall be possible for an authorized user or an IMS service provider enable session based messaging (e.g. create chat room) and thus become an administrator of messaging session.
+- f) It shall be possible for the administrator of a messaging session to control who is allowed to participate in the messaging session.
+- g) It shall be possible for the IMS service provider or administrator of a messaging session to disable messaging session (e.g. close a chat room).
+- h) It shall be possible for the administrator of the messaging session (to set properties related to the messaging session (e.g. the chat room name, topic, maximum number of active users).
+
+## 7.4 Message delivery requirements
+
+Following requirements define the message delivery.
+
+- a) Message delivery shall be immediate i.e. messages are transported by the IMS system to the recipient's terminal (without notifications) subject to message filtering settings defined by the recipient or by the recipient's IMS service provider.
+- b) It shall be possible for the sender to receive delivery acknowledgements (success/failure) for sent messages.
+
+## 7.5 Storage requirements
+
+Session Based Messaging shall support global storage of sessions (accessible to all participants) and personal storage (accessible to the user who requested the storage). For personal storage, all storage operations listed below are applicable. In the case of global storage, users will be able to list and retrieve messages, not delete messages or turn storage on or off.
+
+The following storage requirements shall be supported.
+
+- a) It shall be possible for a participant to request to persistently store a sent Session Based Message or all messages associated with a session in a network based repository if the IMS service provider provides such application level service.
+- b) IMS Messaging shall be able to support a request from a user to retrieve one or more messages stored in a network based repository.
+- c) IMS Messaging shall be able to support a request from a user to delete one or more messages or sessions that are stored in a network based repository.
+- d) IMS Messaging shall be able to support a request from a user to view the list of messages and message related attributes, such as sender, recipient, subject and date/time, in a network based repository.
+
+## 7.6 User privacy requirements
+
+Following requirements define user privacy.
+
+- a) It shall be possible for the recipient to see the public ID of the sender of the message unless the sender has requested to hide it.
+- b) It shall be possible for the sender of the message to request to hide its public ID from the recipient (anonymous sender).
+The sender's public ID shall not be delivered to the recipient. The capability of public ID hiding is an IMS service provider and legislation issue and it may or may not be available. If the service is not available the message shall not be delivered to the recipient.
+- c) It shall be possible for the sender to use nickname when sending messages.
+In case of nickname the recipient shall only be able to see the nickname but not the real address from which the message came from. It shall be possible to use nicknames for public and private messages. It shall be possible for the recipient to reply to the message sent with a nickname.
+- d) It shall be possible for a member of an IMS Messaging session to disable the reporting of the indication that they are entering a message ("Is Typing") on a per session basis. Further granularity levels for this requirement is for further study.
+
+## 7.7 Message Filtering
+
+It shall be possible for a subscriber to set up, modify, and delete filters in the network of the subscriber's IMS service provider, in order to control the treatment of a message by the network when a message is received. The filters shall also support the ability of the subscriber to specify the maximum size and type of message content etc that they are or are not willing to accept. The filters shall also support the ability of the subscriber to block (and unblock) messages from specific senders or anonymous senders.
+
+Following specific requirements define the message filtering capabilities of the recipient.
+
+- a) It shall be possible to define specific message treatment based on following criteria
+ - 1) sender address (including anonymous senders);
+ - 2) message size;
+ - 3) message class (e.g. advertisement, private....);
+ - 4) message priority;
+ - 5) message content type (e.g. video, audio....);
+ - 6) message content format (e.g. mpeg, jpeg....);
+ - 7) message type (e.g. immediate message);
+ - 8) message subject; and
+
+- 9) additional criteria maybe possible but are outside the scope of this document.
+- b) It shall be possible to specify the following message treatments in a filter:
+ - 1) Block the delivery of the message content.
+ - 2) Store the message content and notify recipient,
+ - 3) Store the message content for a specific time or until the recipient requests delivery.
+ - 4) Store and push the message content to recipient when available.
+ - 5) Redirect the message to another address.
+ - 6) Additional treatments maybe possible but are outside the scope of this document.
+
+The IMS service provider shall also be able to set and control the filter settings either on behalf of the subscriber or based on policy.
+
+# --- 8 Addressing requirements
+
+It shall be possible to use a single address to identify the recipient. The single address shall be either a SIP URL, a network address identifier (NAI as defined in RFC2486 [3]) or a MSISDN.
+
+IMS Messaging shall be based on existing IMS address resolution and routing mechanisms.
+
+# --- 9 Security
+
+The user shall be able to use IMS Messaging and access messages in a secure manner. It shall be possible for the contents of messages to be read only by the intended recipient(s). A recipient shall be informed of the reliability of the identity of the sender in case the sender has authorised his identity to be transmitted.
+
+The integrity of messages during transit shall be assured to extent of the network capabilities.
+
+IMS Messaging shall be intrinsically resistant to attempts of malicious or fraudulent use.
+
+The "Security Threats and Requirements" specified in 3GPP TS 21.133 [4] shall not be compromised.
+
+# --- 10 Charging
+
+Charging for IMS Messaging shall be based on existing IMS charging mechanisms as appropriate.
+
+IMS Messaging shall be able to support various charging models, including:
+
+- a) sender only pays;
+- b) both sender and recipient pay their respective charges for message delivery; and
+- c) recipient pays.
+
+IMS Messaging shall be able to support different charging approaches:
+
+- a) volume based charging;
+- b) QoS based charging;
+- c) service based charging;
+- d) number of messages sent and/or received; and
+- e) offline charging or/and online charging.
+
+IMS Messaging shall be able to support various charging mechanisms. The following charging characteristics may be considered:
+
+- a) message content type and length;
+Message content type should be declared using a standardised declaration [the note may need to be moved to a different section e.g. message filtering].
+- b) roaming conditions;
+- c) prepaid subscriptions;
+- d) time when the message is sent;
+- e) time when the message is delivered;
+[FFS, "delivered" could indicate message stored, message read, message received by the terminal and so on...]
+- f) message origin and destination;
+- g) access network employed; and
+- h) the charging information shall describe the amount of data sent and received to and from the external data network [Note: this is introduced to take into account the network(s) transited by message].
+
+# --- 11 Interworking
+
+## 11.1 General
+
+It should be possible for the IMS Messaging subscriber to send/receive messages to/ from subscribers of 3GPP defined messaging services (SMS, EMS, MMS). Optionally, it should be possible to send/receive messages to/from users of fixed Internet messaging service (e.g. SMTP and SIMPLE based services).
+
+## 11.2 Requirements for SMS-Immediate Messaging service-level interworking
+
+These requirements shall be considered for SMS-Immediate Messaging service-level interworking:
+
+- it shall be possible for a user to send an Immediate Message or an SMS message to another user without having to know which messaging client the receiving user has;
+- The user experience shall be consistent with the SMS and Immediate Messaging service level expectations to as large an extent as possible. If the recipient is not available and deferred messaging is offered then the message shall be kept until delivery is possible or the message expires;
+- When interworking from an SMS message to an Immediate Message, the network should deliver all content types in an SMS message to equivalent IMS content types where they exist;
+- When interworking from an Immediate Message to an SMS message, the network should deliver all content types in an Immediate Message to equivalent SMS content types where they exist;
+- When interworking from an Immediate Message to an SMS message and a form of anonymity has been requested by the sending party and the operator of the interworking function cannot identify the sending party, subject to operator policy, interworking shall be suppressed for that message. Subject to operator policy and / or the ability to identify the sending party, the sending party may be informed that the message could not be delivered.
+- When interworking from an Immediate Message to an SMS message, it shall be possible for the sender of the Immediate message to request to hide its public ID from the recipient (e.g. be an anonymous sender). In this case the sender's public ID may not be delivered to the recipient subject to operator policy.
+
+- Based on operator policy, it shall be possible for e.g., an SMS system or data download message such as an over the air configuration message, to be prevented from being interworked at a service level to an Immediate Message, but to instead be transported as an SMS message via IMS, CS or PS;
+- If a user is registered to receive SMS service, then the SMS message should be delivered as an SMS message via IMS, CS or PS transport instead of via service-level interworking, subject to operator and user preferences;
+- If a user is registered to receive Immediate Messaging service, then the Immediate Message should be delivered that way instead of via service-level interworking, subject to operator and user preferences;
+- If an SMS user requests an SMS status report, then an SMS status report should be generated when the message is delivered using Immediate Messaging;
+- If an IMS user requests a notification that the message was delivered to the recipient, an SMS status report should be generated when the message is delivered to the SMS user's client;
+- It shall be possible to generate the appropriate charging-related information and provide the appropriate online charging mechanism (if it is applied for the SMS and/or Immediate Messaging services) for the interworking services.
+
+## 11.3 Requirements for SMS-Session based Messaging service-level interworking
+
+These requirements shall be considered for SMS-Session based messaging service-level interworking:
+
+- Pre Release 10 UE shall be supported by SMS-Session based messaging service-level interworking.
+- it shall be possible for a session based messaging user to send a messaging session invitation to an SMS user;
+- When interworking from a Session based message to an SMS message, the network should deliver all content types in the Session based message to equivalent SMS content types where they exist;
+- When interworking from an SMS message to a Session based message, the network should deliver all content types in an SMS message to equivalent Session based message content types where they exist;
+- If an SMS user requests an SMS status report, then an SMS status report should be generated when the message is delivered using Session based message and a success or failure delivery notification has been received from the Session based message user;
+- If a Session based message user requests a notification that the message was delivered to the recipient, an SMS status report should be generated when the message is delivered to the SMS user's client; an SMS status report should be communicated to a Session based message user as a delivery notification;
+- A session invitation sent towards an SMS user is handled in one of 3 ways (dependent on service provider policies):
+ - 1) The session invitation is accepted by the network on behalf of the SMS user.
+ - 2) The session invitation is denied by the network on behalf of the SMS user.
+ - 3) The SMS user is asked for consent for accepting the session invitation:
+ - The session invitation will be delivered as an SMS message to the SMS user; the appropriate instructions should be included to guide the SMS user how to react (join/reject) the session invitation.
+ - The SMS user will send back a response in an SMS message according to the embedded instruction if included.
+- The user experience shall be consistent with the SMS and Session based messaging service level expectations to as large an extent as possible;
+- For session based messaging the session based connectivity should be maintained for the SMS user so that the SMS user could:
+
+- participate in the session (i.e. exchange messages)
+- exit the session (no more message exchange) according to the instruction embedded in the SMS message.
+- When interworking a session invitation from a Session based messaging service to an SMS message and a form of anonymity has been requested by the sending party and the operator of the interworking function cannot identify the sending party, subject to operator policy, interworking shall be suppressed for that session invitation. Subject to operator policy and / or the ability to identify the sending party, the sending party may be informed that the session invitation could not be delivered.
+- When interworking a session invitation from a Session based messaging service to an SMS message, it shall be possible for the sender of the session invitation to request to hide its public ID from the recipient (e.g. be an anonymous sender). In this case the sender's public ID shall not be delivered to the recipient subject to operator policy.
+- It shall be possible to generate the appropriate charging-related information and provide the appropriate online charging mechanism (if it is applied for the SMS and/or Session based messaging services) for the interworking services. Such charging related information shall take into account the one-to-many relationship of messages sent to a session.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| | | | 22.abc | | | | | Produced during IMS Messaging interim SWG meeting 23 rd -24 th September, Reading, UK | | 0.0.0 | IMSM |
+| | | S1-021873 | 22.abc | | | | | Revisions on the requirements mainly due to new document structure | 0.0.0 | 0.1.0 | IMSM |
+| | | S1-022052 | 22.340 | | | | | TS number updated, introduction, scope and definitions added, remaining issues (except the one concerning storage requirements in session based messaging and one in interworking) marked with editor's notes resolved | 0.1.0 | 0.2.0 | IMSM |
+| 12 /12/02 | SP-18 | SP-020671 | 22.340 | | | | | Raised to version 2.0.0 for presentation for approval at SA #18 | 0.2.0 | 2.0.0 | IMSM |
+| 12 /12/02 | SP-18 | SP-020671 | 22.340 | | | | | Approved at SA #18 | 2.0.0 | 6.0.0 | IMSM |
+| SP-19 | SP-030032 | S1-030260 | 22.340 | 0001 | - | Rel-6 | D | CR to 22.340 on required message formats for IMS messaging | 6.0.0 | 6.1.0 | IMSM-TS |
+| SP-27 | SP-050062 | S1-050255 | 22.340 | 0002 | - | Rel-6 | F | Removal of Deferred Messaging Requirements | 6.1.0 | 6.2.0 | IMSM-TS |
+| SP-30 | SP-050654 | | 22.340 | - | - | Rel7 | - | Raised to Rel-7 to allow reference by TISPAN | 6.2.0 | 7.0.0 | FBI |
+| SP-35 | SP-070124 | S1-070262 | 22.340 | 0004 | 1 | Rel-8 | B | CR0004 on 22.340 for SMS - IM service level interworking reqs | 7.0.0 | 8.0.0 | MESSIW |
+| SP-39 | SP-080038 | S1-080282 | 22.340 | 0005 | 2 | Rel-8 | C | Addition of Privacy requirements when Service Level interworking is performed | 8.0.0 | 8.1.0 | SLIMS |
+| SP-39 | SP-080038 | S1-080279 | 22.340 | 0006 | 2 | Rel-8 | F | Clarification on storage requirements | 8.0.0 | 8.1.0 | SLIMS |
+| SP-45 | SP-090485 | S1-093269 | 22.340 | 0007 | 2 | Rel-10 | B | Enhancements for CPM-SMS Interworking | 8.1.0 | 10.0.0 | CPM_SMS |
+| 2012-09 | - | - | - | - | - | - | - | Updated to Rel-11 by MCC | 10.0.0 | 11.0.0 | |
+| 2014-10 | | | | | | | | Updated to Rel-12 by MCC | 11.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | - | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22346/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22346/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab7fcff6441d8a44e2461d7e7b06a5d97a35eb1f
--- /dev/null
+++ b/marked/Rel-18/22_series/22346/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1e413ad522e4fc144e00d9046712773ea7b365e815ed00ab132f35bc70e4ef8
+size 9565
diff --git a/marked/Rel-18/22_series/22346/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22346/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc6bc4f813adced92c024b660eb55ff5795770bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22346/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15fd4ae7c319660070fc3dfc8ffa883ed6d9d537e4ba645f4999849854f69b74
+size 7354
diff --git a/marked/Rel-18/22_series/22346/raw.md b/marked/Rel-18/22_series/22346/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..315cb73b19a0cff9886269436bf1c40aad4425c9
--- /dev/null
+++ b/marked/Rel-18/22_series/22346/raw.md
@@ -0,0 +1,353 @@
+
+
+# 3GPP TS 22.346 V18.0.1 (2024-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1 (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+Isolated, E-UTRAN, Public, Safety
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+### --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|---------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Overview..... | 7 |
+| 4.1 Service description ..... | 7 |
+| 5 Service requirements..... | 8 |
+| 5.1 General requirements ..... | 8 |
+| 5.2 Subscriber and service management requirements ..... | 8 |
+| 5.2.1 Introduction (informative) ..... | 8 |
+| 5.2.2 Requirements..... | 8 |
+| 5.2.3 Interoperability with MCPTT..... | 9 |
+| 5.3 Requirements for initiation of Isolated E-UTRAN operation..... | 9 |
+| 5.3.1 Introduction (informative) ..... | 9 |
+| 5.3.2 Requirements..... | 9 |
+| 5.4 Requirements for ongoing Isolated E-UTRAN operation..... | 10 |
+| 5.4.1 Introduction (informative) ..... | 10 |
+| 5.4.2 Requirements..... | 10 |
+| 5.5 Requirements for termination of an Isolated E-UTRAN ..... | 11 |
+| 5.5.1 Introduction (informative) ..... | 11 |
+| 5.5.2 Requirements..... | 11 |
+| 5.6 Requirements for security aspects of Isolated E-UTRAN operation ..... | 11 |
+| 5.6.1 Introduction (informative) ..... | 11 |
+| 5.6.2 Requirements..... | 11 |
+| Annex A (informative): Change history ..... | 13 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies the service requirements for Isolated E-UTRAN Operation in support of mission critical network operation for Public Safety. In particular, requirements are specified for:
+
+- Initiation of Isolated E-UTRAN operation.
+- Ongoing Isolated E-UTRAN operation.
+- Termination of Isolated E-UTRAN operation.
+- Security aspects of Isolated E-UTRAN operation.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.101: "Services aspects; Service principles".
+
+# --- 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].
+
+**Isolated E-UTRAN:** either an E-UTRAN without normal connectivity with the EPC or deployed NeNBs with E-UTRAN functionality.
+
+**Isolated E-UTRAN operation:** Comprises two situations: 1) In the event of an interruption to normal backhaul connectivity Isolated E-UTRAN operation aims to adapt to the failure and maintain an acceptable level of network operation in the Isolated E-UTRAN. The restoration of service is the eventual goal. 2) Operation following the deployment of one or more Nomadic eNBs either without backhaul or with limited backhaul.
+
+**Limited backhaul capability:** Isolated E-UTRAN operation supports operation where the Isolated E-UTRAN has no backhaul capability to the EPC. Furthermore Isolated E-UTRAN operation may have limited backhaul capability to the EPC. For the case of limited backhaul capability to the EPC only the signalling of public safety UEs can reliably be communicated to the EPC; in addition users may have the possibility to transmit a limited amount of user data with no guarantee of service.
+
+**Nomadic eNB (NeNB):** An NeNB is a nomadic cell and may consist: base station, antennas, microwave backhaul and support for local services. The NeNB is intended for Public Safety use providing coverage or additional capacity where: 1) coverage was never present (e.g. forest fire or underground rescue) or 2) where, for example, due to natural disaster coverage is no longer present.
+
+## 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].
+
+| | |
+|------|-------------|
+| NeNB | Nomadic eNB |
+|------|-------------|
+
+# 4 Overview
+
+## 4.1 Service description
+
+Ensuring the continued ability of Public Safety users to communicate within mission critical situations is of the utmost importance. The Isolated E-UTRAN mode of operation provides the ability to maintain a level of communications for Public Safety users, via an eNB (or set of connected eNBs), following the loss of backhaul communications. The Isolated E-UTRAN mode of operation also provides the ability to create a serving radio access network without backhaul communications, from a deployment of one or more standalone Nomadic eNBs (NeNBs). In addition the Isolated EUTRAN feature also addresses the scenario where a fixed or nomadic set of eNBs is without normal backhaul communications but has been provided with an alternative (non-ideal) limited bandwidth backhaul.
+
+An Isolated E-UTRAN may comprise a deployment of one or more NeNBs. In this case operator control would initiate Isolated E-UTRAN operation for a group of NeNBs in a given incident area. An Isolated E-UTRAN derived from NeNBs exhibits similar behaviour to an Isolated E-UTRAN derived from eNBs including: support for Public Safety Ues in the coverage area, communication between NeNBs and support for limited backhaul connectivity.
+
+The Isolated E-UTRAN may comprise a single or multiple eNBs, a single or multiple NeNBs, or a mixed group of eNBs and NeNBs. An Isolated E-UTRAN comprising multiple (N)eNBs, with connections between the (N)eNBs, can provide communication between Ues across a wider area of coverage than can be provided by a single isolated (N)eNB. The Ues in the coverage of the Isolated E-UTRAN are able to continue communicating and provide a restricted set of services supporting voice, data and group communications, to their Public Safety users.
+
+An Isolated E-UTRAN is characterized by having no, or a limited, backhaul connection. In particular, the Isolated E-UTRAN feature enables services to be provided to Public Safety Ues in the following backhaul scenarios (see also Table 4.1-1):
+
+- No backhaul;
+- Limited bandwidth signalling only backhaul;
+- Limited bandwidth signalling and user data backhaul.
+
+**Table 4.1-1: Isolated E-UTRAN scenarios**
+
+| IOPS Scenario | Signalling backhaul status | User Data backhaul status | Comment |
+|---------------------------------|-----------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| No backhaul | Absent | Absent | Fully Isolated E-UTRAN operation using local routing of UE-UE data traffic and possible support for access to the public internet via a local gateway |
+| Signalling only backhaul | Limited | Absent | User data traffic offload at the E-UTRAN using local routing of UE-UE data traffic and possible support for access to the public internet via a local gateway |
+| Limited backhaul | Limited | Limited | Selective user data traffic offload at the E-UTRAN using local routing of UE-UE data traffic and possible support for access to the public internet via a local gateway |
+| Normal backhaul | Normal | Normal | Normal EPC connected operation |
+
+# --- 5 Service requirements
+
+## 5.1 General requirements
+
+Isolated E-UTRAN operation shall not impact either GSM or UMTS.
+
+The use of Isolated E-UTRAN operation shall be authorized by the operator. The network controls the use of E-UTRAN resources used for Isolated E-UTRAN operation.
+
+When a Public Safety UE communicates within the Isolated E-UTRAN, the PLMN operator shall be able to collect accounting data for this communication.
+
+## 5.2 Subscriber and service management requirements
+
+### 5.2.1 Introduction (informative)
+
+In order to provide efficient Isolated E-UTRAN operation it is necessary that eNBs (and NeNBs) capable of forming and joining an Isolated E-UTRAN are able to support certain functions locally thereby providing services of importance to the Public Safety community.
+
+### 5.2.2 Requirements
+
+Public Safety Ues served only by an Isolated E-UTRAN will not possess user plane connectivity to an external IP network due to the absence of backhaul connectivity to the Mobile Operator Network. The Isolated E-UTRAN may support Selected IP Traffic Offload at the Local Network, compatible with the service principles defined in [2], in order to provide connectivity to external IP networks (e.g. internet) when a backhaul connection (limited or otherwise) is present.
+
+The Isolated E-UTRAN shall be able to make use of a limited backhaul connection to exchange control plane signalling with the EPC.
+
+The Isolated E-UTRAN may use the limited backhaul connection to exchange user plane data with the EPC.
+
+NOTE: There is no quality of service expectations for user plane data.
+
+The Isolated E-UTRAN shall support mobility for Public Safety Ues between the eNBs comprising the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall be able to establish 'local routing' and ProSe Group Communication for the Public Safety Ues in coverage of the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall be able to provide voice and data communications services to all Public Safety Ues and groups under the coverage of the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall allow Public Safety Ues under its coverage to initiate and maintain voice and data communications with other Public Safety Ues and groups under the coverage of the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall be capable of informing served Public Safety Ues about which other Public Safety Ues the Isolated E-UTRAN is serving. The Isolated E-UTRAN shall support restrictions upon the provision of this information according to security policy.
+
+NOTE: For example, information on users within a served user's organization could be sent to that served user, and information on users could be provided to other users within the same group. Lists of served users and/or served groups could be obtained from the network or could be compiled from information collected from the Ues served by the isolated system.
+
+### 5.2.3 Interoperability with MCPTT
+
+The following requirements define a minimal set of MCPTT capabilities that are needed to provide MCPTT support under Isolated E-UTRAN operation. These requirements apply only to users under coverage of the same Isolated E-UTRAN.
+
+These requirements apply to (N)eNBs which support MCPTT communications when not operating in an Isolated E-UTRAN.
+
+A mechanism to pre-provision group membership, including MCPTT Emergency Group membership, shall be supported.
+
+NOTE: Groups may be pre-provisioned on an organization basis or may cross organizational boundaries.
+
+A Public Safety user shall be able to initiate an MCPTT Emergency Group call that reaches the following, when preconfigured as affiliated Group Members:
+
+- a dispatcher (the dispatcher may be connected directly to the (N)eNB or via a UE)
+- members of the group under the coverage of the Isolated E-UTRAN and/or;
+- all Ues under the coverage of the Isolated E-UTRAN.
+
+During Isolated E-UTRAN operation each group shall be able to initiate at least one MCPTT voice group communication that all the group's authorized members are allowed to join, up to the limit of available radio resources.
+
+MCPTT voice group communication shall be able to pre-empt video communications or other data services.
+
+## 5.3 Requirements for initiation of Isolated E-UTRAN operation
+
+### 5.3.1 Introduction (informative)
+
+The initiation of Isolated E-UTRAN operation occurs in the event an eNB determines that there is an interruption to normal backhaul connectivity. At this point the eNB can determine if it still has connectivity to other eNBs. It is necessary for services to be set up and a limited backhaul, that might be present, needs to be taken into consideration. The Isolated E-UTRAN needs to inform the UE that it is now working in an Isolated E-UTRAN and an indication to this effect is passed on to the Public Safety user.
+
+### 5.3.2 Requirements
+
+An eNB supporting Isolated E-UTRAN operation shall be able to detect a loss of backhaul connection and shall be able to initiate Isolated E-UTRAN operation.
+
+An (N)eNB shall be informed by O&M procedures if its backhaul connection is of limited bandwidth (e.g. a temporary nomadic backhaul deployment or a replacement backhaul in a disaster situation).
+
+Under operator control an NeNB shall be able to initiate Isolated E-UTRAN operation.
+
+When an eNB enters Isolated E-UTRAN operation it shall be able to, if permitted by operator policy, minimize disruption to existing established services between those Public Safety Ues served by the eNB. The eNB shall terminate services that cannot be supported locally by the Isolated E-UTRAN or by the limited backhaul service if that is available.
+
+When an (N)eNB enters Isolated E-UTRAN operation services shall be supported for all Public Safety Ues under the coverage of the Isolated E-UTRAN.
+
+An Isolated E-UTRAN may comprise one or more (N)eNBs.
+
+An (N)eNB supporting Isolated E-UTRAN operation which has initiated Isolated E-UTRAN operation shall attempt to communicate with known peer (N)eNBs for the purpose of commencing Isolated E-UTRAN joint operation.
+
+(N)eNBs engaged in Isolated E-UTRAN joint operation shall be able to exchange user traffic and signalling with other (N)eNBs belonging to the same Isolated E-UTRAN.
+
+An Isolated E-UTRAN shall provide an indication to Public Safety UEs within the coverage area regarding whether limited bandwidth backhaul services are available or whether support is available for local services only. An Isolated E-UTRAN shall be capable of continuing to provide this indication until the Isolated E-UTRAN operation is terminated.
+
+A Public Safety UE served by an Isolated E-UTRAN shall provide an indication to the user that the user is communicating within an Isolated E-UTRAN and whether a limited backhaul service is available or whether support is available for local services only.
+
+## 5.4 Requirements for ongoing Isolated E-UTRAN operation
+
+### 5.4.1 Introduction (informative)
+
+It is necessary to manage the potentially dynamic ongoing operation of an Isolated E-UTRAN where:
+
+- Public Safety UEs join and leave the Isolated E-UTRAN.
+- eNBs join and leave the Isolated E-UTRAN.
+- NeNBs join and leave the Isolated E-UTRAN.
+- Isolated E-UTRANs may be combined to form larger Isolated E-UTRANs or may be split up in smaller Isolated E-UTRANs.
+
+The EPS should monitor the status of a disconnected or limited bandwidth backhaul with the intention of re-establishing a normal connection between the Isolated E-UTRAN and the EPC.
+
+### 5.4.2 Requirements
+
+The EPS shall monitor the status of a disconnected backhaul with the intention of re-establishing a connection to the EPC.
+
+The EPS shall monitor the status of a limited bandwidth backhaul connection with the intention of re-establishing normal operation with the EPC.
+
+The Isolated E-UTRAN shall admit Public Safety UEs to the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall manage Public Safety UE mobility between (N)eNBs within the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall possess the ability to add (N)eNBs to the Isolated E-UTRAN.
+
+**NOTE:** An (N)eNB added to the Isolated E-UTRAN may be an (N)eNB which possess a limited backhaul connection. Furthermore the (N)eNB with a limited backhaul connection admitted to the Isolated E-UTRAN may be the only (N)eNB in the Isolated E-UTRAN that possesses a limited backhaul connection.
+
+The Isolated E-UTRAN shall support the ability to combine with another Isolated E-UTRAN to form a larger combined Isolated E-UTRAN.
+
+No disruption shall be caused to local services within the remaining Isolated E-UTRAN due to an (N)eNB leaving the Isolated E-UTRAN
+
+**NOTE:** The (N)eNB leaving the Isolated E-UTRAN may be the only (N)eNB in the Isolated E-UTRAN which possess a limited backhaul connection.
+
+No disruption shall be caused to local services within the remaining Isolated E-UTRANs due to an Isolated E-UTRAN being subdivided.
+
+## 5.5 Requirements for termination of an Isolated E-UTRAN
+
+### 5.5.1 Introduction (informative)
+
+In the event that the EPS detects a restored backhaul it attempts to re-establish a connection between the EPC and (N)eNB. On successful re-establishment of a connection to the EPC the (N)eNB reverts to the normal EPC connected mode of operation. While reverting to the EPC connected mode of operation the (N)eNB will transition all Public Safety UEs with active contexts to operation under the control of the EPC.
+
+When the connection to the EPC is restored, Public Safety UEs, which were served by the (N)eNB as part of the Isolated E-UTRAN can indicate to the Public Safety user that EPC connected services are once again available.
+
+### 5.5.2 Requirements
+
+If the Isolated E-UTRAN is operating without any backhaul connection the EPS shall on detection of a restored backhaul attempt to re-establish a connection between the EPC and (N)eNB.
+
+If the Isolated E-UTRAN is operating with a limited bandwidth backhaul connection the EPS shall on detection of a restored full bandwidth backhaul attempt to re-establish normal operation between the EPC and (N)eNB.
+
+While re-establishing a connection to the EPC, or normal operation with the EPC, the EPS shall be able to manage, for all UEs with active contexts, the transition, where appropriate, of local services provided by the Isolated E-UTRAN to equivalent services provided via the EPC.
+
+Having re-established control plane and user plane connections to the EPC, which are not restricted by a limited backhaul capability, the (N)eNB shall cease to provide the local services and routing which characterized Isolated E-UTRAN operation.
+
+When an (N)eNB ceases Isolated E-UTRAN operation the (N)eNB shall cease to provide any indications, to Public Safety UEs within its coverage area, regarding the availability of only limited bandwidth backhaul services and/or whether support is available only for local services. Public Safety UEs served by the (N)eNB shall be able to indicate to the user the cessation of the restricted Isolated E-UTRAN mode of operation and/or the availability of normal EPC connected services.
+
+## 5.6 Requirements for security aspects of Isolated E-UTRAN operation
+
+### 5.6.1 Introduction (informative)
+
+The Isolated E-UTRAN is expected to provide for the authentication of participating entities and for the confidentiality and integrity of communications. Provision of these security features is required for:
+
+- UE to (N)eNB communication;
+- (N)eNB to (N)eNB communication;
+- UE to UE communication, i.e. for the case of ProSe operation within the Isolated E-UTRAN.
+
+### 5.6.2 Requirements
+
+The Isolated E-UTRAN shall support the following requirements for security, authorization and privacy in each of the three IOPS backhaul scenarios (see scenarios 1-3 in Table 4.1-1).
+
+The Isolated E-UTRAN shall ensure the confidentiality and integrity of both user data and network signalling to a level comparable with that provided by the existing 3GPP system. This requirement applies to any communication between two Public Safety UEs communicating via the Isolated E-UTRAN and between an (N)eNB providing locally connected services and a Public Safety UE connected to the Isolated E-UTRAN.
+
+A mechanism shall be provided to ensure the confidentiality and integrity of user data and signalling over the radio communication paths and over any inter-(N)eNB communication paths of an Isolated E-UTRAN.
+
+Existing 3GPP security mechanisms (including, but not necessarily limited to, ProSe security mechanisms) shall be reused whenever possible and appropriate.
+
+The Isolated E-UTRAN shall provide mechanism(s) to ensure mutual authentication between an Isolated E-UTRAN and (N)eNBs, or other Isolated E-UTRANs, joining the Isolated E-UTRAN.
+
+The Isolated E-UTRAN shall provide mechanism(s) to ensure mutual authentication between an Isolated E-UTRAN and UEs connecting to the Isolated E-UTRAN.
+
+The security mechanism(s) supported by an Isolated E-UTRAN shall be consistent with the dynamic nature of an Isolated E-UTRAN. The security of credentials shall not be compromised by solutions for Isolated E-UTRAN operation.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|----|-----|--------------------------------------------------------------|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 05-2014 | | | | | First draft | | 0.1.0 |
+| 08-2014 | | | | | Presentation to SA#65 | 0.1.0 | 0.2.0 |
+| 09-2014 | SA#65 | SP-140506 | | | MCC clean-up for presentation to SA#65 for one-step approval | 0.2.0 | 1.0.0 |
+| 09-2014 | SA#65 | | | | Raised to v.13.0.0 following SA's one-step-approval | 1.0.0 | 13.0.0 |
+| 03-2017 | SA#75 | | | | Updated to rel-14 by MCC | 13.0.0 | 14.0.0 |
+| 2018-06 | - | - | - | | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|-----------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-07 | SA#88e | - | - | - | - | Updated to Rel-16 by MCC | 16.0.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22368/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-18/22_series/22368/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcc1ab2209d30ce7443da6069d9b0b59a88dad36
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92912add404d77e97967cddc36e272da003993a4c6ac48cc7a6235590b239a5a
+size 34624
diff --git a/marked/Rel-18/22_series/22368/3b621c21b0af3a504a28d2547e87138f_img.jpg b/marked/Rel-18/22_series/22368/3b621c21b0af3a504a28d2547e87138f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f7fd9ac9247b46c669ade6f618cefa7a7fc610b
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/3b621c21b0af3a504a28d2547e87138f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df4f82b8e380ce9370265b3a792d3d14df8d36278be9b027e251d7df83d29be5
+size 32237
diff --git a/marked/Rel-18/22_series/22368/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22368/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0ad65f7da5addb52f8a5a19e46f57ed7850a9a6
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e986831a449e6065210a6a747f5344a5fb63180c1943f96d5779f0c5bd558fe7
+size 8266
diff --git a/marked/Rel-18/22_series/22368/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22368/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc24848b1d8fe159caa0808284b8c65d167cf112
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ab181f0222b786d19f8d537a1f906e5c1a121b58a668102e2ad40c58ee66097
+size 7308
diff --git a/marked/Rel-18/22_series/22368/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-18/22_series/22368/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..859b42b5942364efe6f09ac5f5ec57108f44af71
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06096da67a126663d6361680b923848da203a20c6c76c6849aa24d184afd498e
+size 57887
diff --git a/marked/Rel-18/22_series/22368/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/Rel-18/22_series/22368/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04d22e7fffd0aee31a94f1c2710e5a52e0f0440a
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d2e82b32ef6034434b4911c2ae323e2a8942aa964d6a62e6d4688ec97184ea6
+size 29707
diff --git a/marked/Rel-18/22_series/22368/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-18/22_series/22368/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cccad63ffd33ad65618aa188a3d3e1cad4bb9afa
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e7c9c6255fd8002d08978cae8591742742226ed305dda8b2ed2911d6c3fe586
+size 40841
diff --git a/marked/Rel-18/22_series/22368/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-18/22_series/22368/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86caa3625284a8acd54f5ada05e1efe4b6980583
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0cc3c8cf75b00b9d4156d6d05932b8f21c9678a63010d8b68ec7627f5e2bdc97
+size 28169
diff --git a/marked/Rel-18/22_series/22368/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-18/22_series/22368/a234352dfaccdc24745c88eef7724cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b900bb5d816357be469444ffc77b84b56e0578ad
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/a234352dfaccdc24745c88eef7724cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de7a6d0bb959b10ff44da5ad80e65e071c37191e46ee2c80cf700ff8a73b17f1
+size 33705
diff --git a/marked/Rel-18/22_series/22368/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-18/22_series/22368/e636d7ccca0ad14c6b95201404324823_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..86eed33427fd82ef0f556176cd035878c4d66bb5
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/e636d7ccca0ad14c6b95201404324823_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:641ebc850836d546efde3a6aef0b19b5cbce05123446db83e5fcba87e5c0cbec
+size 36180
diff --git a/marked/Rel-18/22_series/22368/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/22_series/22368/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbaaea553b2fe41c213975c4ff901050471e5e7e
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df1b78bb6c508c8de35c9b935891fc4d0e918b77a87569f86c4eb603c5aa4e32
+size 25750
diff --git a/marked/Rel-18/22_series/22368/raw.md b/marked/Rel-18/22_series/22368/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0ec632590547382a5179c49999e055079fe7b84
--- /dev/null
+++ b/marked/Rel-18/22_series/22368/raw.md
@@ -0,0 +1,717 @@
+
+
+# 3GPP TS 22.368 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for Machine-Type Communications (MTC); Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font. The 'P' has a red signal wave icon at its base, and a 'TM' trademark symbol is located to the upper right of the 'P'.
+
+3GPP logo
+
+## --- **Keywords**
+
+Service, requirement, machine
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Overview of system optimizations for machine-type communications..... | 7 |
+| 5 MTC communication aspects..... | 8 |
+| 5.1 MTC communication scenarios ..... | 8 |
+| 5.1.1 Introduction ..... | 8 |
+| 5.1.2 MTC devices communicating with one or more MTC servers ..... | 8 |
+| 5.1.3 MTC devices communicating with each other..... | 9 |
+| 5.2 (void)..... | 9 |
+| 6 Categories of features for Machine-Type Communications ..... | 10 |
+| 7 Service requirements..... | 11 |
+| 7.1 Common service requirements..... | 11 |
+| 7.1.1 General ..... | 11 |
+| 7.1.2 MTC Device triggering ..... | 12 |
+| 7.1.3 Addressing..... | 12 |
+| 7.1.4 Identifiers..... | 13 |
+| 7.1.5 Charging requirements ..... | 14 |
+| 7.1.6 Security requirements ..... | 14 |
+| 7.1.7 Remote MTC device management ..... | 14 |
+| 7.2 Specific service requirements – MTC Features ..... | 14 |
+| 7.2.1 Low Mobility..... | 14 |
+| 7.2.2 Time Controlled..... | 14 |
+| 7.2.3 Void ..... | 15 |
+| 7.2.4 Void ..... | 15 |
+| 7.2.5 Small Data Transmissions ..... | 15 |
+| 7.2.6 Void ..... | 16 |
+| 7.2.7 Infrequent Mobile Terminated..... | 16 |
+| 7.2.8 MTC Monitoring ..... | 16 |
+| 7.2.9 Void ..... | 17 |
+| 7.2.10 Secure Connection..... | 17 |
+| 7.2.11 Void ..... | 17 |
+| 7.2.12 Void ..... | 17 |
+| 7.2.13 Void ..... | 17 |
+| 7.2.14 Group Based MTC Features ..... | 17 |
+| 7.2.14.1 General..... | 17 |
+| 7.2.14.2 Group Based Policing ..... | 17 |
+| 7.2.14.3 Group Based Addressing ..... | 17 |
+| Annex A (informative): Use cases..... | 19 |
+| Annex B (informative): Examples of MTC applications..... | 23 |
+| Annex C (informative): Change history..... | 24 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies the service requirements for Network Improvements for Machine Type Communications. In particular it will:
+
+- identify and specify general requirements for machine type communications;
+- identify service aspects where network improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications;
+- specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.011: " Service accessibility".
+- [3] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
+- [4] ETSI TS 102 690: "Machine-to-Machine communications (M2M); functional architecture".
+- [5] ETSI TS 102 921: " Machine-to-Machine communications (M2M); mla, dla, and mld interfaces".
+
+# 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].
+
+**MTC Device:** A MTC Device is a UE equipped for Machine Type Communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s).
+
+Note 1: A MTC Device might also communicate locally (wirelessly, possibly through a Personal Area Network, or hardwired) with other entities which provide the MTC Device "raw data" for processing and communication to the MTC Server(s) and/or other MTC Device(s). Local communication between MTC Device(s) and other entities is out of scope of the present document.
+
+**MTC Feature:** MTC Features are network functions to optimize the network for use by M2M applications.
+
+**MTC Group:** A MTC Group is a group of MTC Devices that share one or more MTC Features and that belong to the same MTC Subscriber.
+
+**MTC Server:** A MTC Server is a server, which communicates to the PLMN itself, and to MTC Devices through the PLMN. The MTC Server can also have an interface which can be accessed by the MTC User. The MTC Server can:
+
+- Provide services for other servers (e.g. The MTC Server is a Services Capability Server 3GPP TS 23.682 [3] for an Application Server [3]), and/or
+- Provide services for applications and can host the application (e.g. The MTC Server is an Application Server [3]).
+
+**MTC User:** A MTC User uses the service provided by the MTC Server.
+
+**MTC Subscriber:** A MTC Subscriber is a legal entity having a contractual relationship with the network operator to provide service to one or more MTC Devices.
+
+Note 2: Typically a M2M service provider is the party holding subscriptions in order to provide connectivity between MTC Devices and the MTC Server. In practise certain roles can collapse, e.g. the network operator acts as the same time as service provider.
+
+## 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].
+
+| | |
+|-------|------------------------------------------------------|
+| NIMTC | Network Improvements for Machine Type Communications |
+| MNO | Mobile Network Operator |
+| MTC | Machine-Type Communications |
+
+# --- 4 Overview of system optimizations for machine-type communications
+
+Machine-type communication is a form of data communication which involves one or more entities that do not necessarily need human interaction.
+
+A service optimized for machine type communications differs from a service optimized for Human to Human communications. Machine-type communications is different to current mobile network communication services as it involves:
+
+- a) different market scenarios,
+- b) data communications,
+- c) lower costs and effort,
+- d) a potentially very large number of communicating terminals with,
+- e) to a large extent, little traffic per terminal.
+
+For the purpose of the present document, the term MTC is used for the purpose to describe use-cases and illustrate the diverse characteristics of machine-type communication services.
+
+The informative annex A gives an overview of MTC use-cases which also illustrate different overload scenarios which will require overload control functions to prevent overload and to differentiate between services offered to different subscribers with different service requirements. In particular, certain MTC services and MTC applications, as exemplified in annex B, are more tolerant and can accept a lower level of performance requirements for its communication services. However, some MTC services will have similar service requirements as current mobile network communication services.
+
+# 5 MTC communication aspects
+
+## 5.1 MTC communication scenarios
+
+### 5.1.1 Introduction
+
+For MTC communication the following communication scenarios can be identified:
+
+- a) MTC Devices communicating with one or more MTC Server;
+- b) MTC Devices communicating with each other.
+
+### 5.1.2 MTC devices communicating with one or more MTC servers
+
+The network operator provides network connectivity to MTC Server(s). This applies to MTC Server(s) controlled by the network operator (refer to figure 5-1) or to MTC Server(s) not controlled by the network operator (refer to figure 5-2.)
+
+
+
+The diagram shows a yellow cloud labeled 'Operator domain'. Inside the cloud is a box labeled 'MTC Server'. To the right of the cloud, outside it, is a box labeled 'MTC User'. A line connects the 'MTC Server' inside the cloud to the 'MTC User' outside. On the left, four boxes labeled 'MTC Device' are shown, with dashed lines between them indicating more devices. Lines connect each 'MTC Device' to the 'Operator domain' cloud.
+
+Figure 5-1: Communication scenario with MTC devices communicating with MTC server. MTC server is located in the operator domain.
+
+**Figure 5-1: Communication scenario with MTC devices communicating with MTC server. MTC server is located in the operator domain.**
+
+
+
+The diagram shows a yellow cloud labeled 'Operator domain'. On the left, four boxes labeled 'MTC Device' are shown, with dashed lines between them indicating more devices. Lines connect each 'MTC Device' to the 'Operator domain' cloud. Outside the cloud to the right, there is a box labeled 'MTC Server', which is connected to a box labeled 'MTC User'. A line connects the 'Operator domain' cloud to the 'MTC Server'.
+
+Figure 5-2: Communication scenario with MTC devices communicating with MTC server. MTC server is located outside the operator domain.
+
+**Figure 5-2: Communication scenario with MTC devices communicating with MTC server. MTC server is located outside the operator domain.**
+
+The MTC Device and the MTC Server it is communicating with may implement a service enablement framework (e.g. as specified in [4] and [5]) to provide generic functionality for applications. The MTC Device may implement multiple instances of service enablement frameworks, each communicating with a different MTC Server.
+
+Note 1: the standardization of service enablement frameworks is out of scope of 3GPP.
+
+Note 2: as an example, a device can have two (or more) service enablement frameworks, both compliant to the same specific standard or belonging to the same proprietary implementation. Each one has to be peered to a different MTC server.
+
+### 5.1.3 MTC devices communicating with each other
+
+The communication scenario where the MTC Devices communicate directly without intermediate MTC Server (refer to figure 5-3) is not considered in this release of the specification.
+
+
+
+The diagram illustrates a communication scenario between two operator domains, 'Operator domain A' and 'Operator domain B', represented by yellow cloud shapes. On the left, four rectangular boxes labeled 'MTC Device' are connected to 'Operator domain A'. On the right, four similar 'MTC Device' boxes are connected to 'Operator domain B'. A solid line connects the two operator domains. Dashed lines extend from the 'MTC Device' boxes in each domain towards the center, indicating direct communication paths between devices in different domains without an intermediate MTC server.
+
+Diagram showing MTC Devices in Operator domain A and Operator domain B connected directly to each other.
+
+Figure 5-3: MTC Devices communicating directly with each other without intermediate MTC server
+
+## 5.2 (void)
+
+# --- 6 Categories of features for Machine-Type Communications
+
+Machine-Type Communication (MTC) applications do not all have the same characteristics. This implies that not every system optimization is suitable for every MTC application. Therefore, MTC Features are defined to provide structure for the different system optimization possibilities that can be invoked. MTC Features provided to a particular subscriber are identified in the subscription. MTC Features can be individually activated.
+
+The following MTC Features have been defined:
+
+- Low Mobility;
+- Time Controlled;
+- Small Data Transmissions;
+- Infrequent Mobile Terminated;
+- MTC Monitoring;
+- Secure Connection;
+- Group Based MTC Features:
+ - Group Based Policing;
+ - Group Based Addressing.
+
+# 7 Service requirements
+
+## 7.1 Common service requirements
+
+### 7.1.1 General
+
+The following are MTC common service requirements:
+
+- The network shall enable the network operator to identify per subscription which individual MTC Features are subscribed to by a particular MTC Subscriber.
+- The network shall provide a mechanism for the MTC Subscriber to activate or deactivate MTC Features.
+- The network shall enable the network operator to identify which individual MTC Features are activated for a particular MTC Subscriber.
+
+Note 1: The activation/deactivation functionality can be provided via a web interface that is outside the scope of 3GPP specifications.
+
+- The network shall provide a mechanism for the network operator to control the addition or removal of individual MTC Features to a subscription (e.g. based on matching or mismatching of MTC Features).
+- The network shall provide a mechanism for the network operator to restrict activation of MTC Features (e.g. based on matching or mismatching of MTC Features).
+- The network may provide a mechanism for the network operator to allow MTC Devices to override restrictions imposed by a particular MTC Feature.
+- The network operator shall be able to restrict the use of a USIM to specific MEs/MTC Devices.
+- The network shall provide a mechanism to reduce peaks in the data and signalling traffic resulting from very large numbers of MTC Devices (almost) simultaneously attempting data and/or signalling interactions.
+- The network shall provide a mechanism to restrict downlink data and signalling when the network is overloaded.
+- The network shall provide a mechanism to restrict access towards a specific APN when the network is overloaded.
+- A MTC Device may support the Extended Access Barring (EAB) mechanism defined in TS 22.011 [2].
+- A MTC Device supporting the EAB mechanism shall be able to be configured for EAB by the HPLMN.
+- The HPLMN shall be able to configure EAB on a MTC Device that supports it.
+- Once configured, and upon reception of broadcasted EAB information, the MTC Device shall adhere to the defined EAB mechanisms.
+
+Note 2: The decision of whether a MTC Device is configured for EAB is out of 3GPP scope. In general, MTC Devices considered more tolerant to access restrictions are well suited to be configured for EAB.
+
+- The system shall provide mechanisms to efficiently maintain connectivity for a large number of MTC Devices.
+- The network shall provide mechanisms to handle MTC Devices and applications on MTC Devices registering on the IP multimedia core network subsystem and accessing its capabilities including interaction with IMS application servers/enablers.
+- Configuration parameters which are provided in the USIM shall take precedence over parameters provided in the MTC Device if both exist.
+- The network shall allow a resource efficient registration of MTC Devices and applications on MTC Devices on the IP multimedia core network subsystem (e.g. no need of a permanently assigned ID per MTC Device)
+
+- The system shall provide mechanisms to lower power consumption of MTC Devices.
+- The system shall provide a resource efficient way to support MTC Devices that send or receive data infrequently, i.e. with long periods between data transmissions.
+- MTC Devices may or may not be kept attached to the network when not communicating, depending on operator policies and MTC Application requirements.
+- MTC Devices may keep their data connection or not keep their data connection when not communicating, depending on operator policies and MTC Application requirements.
+
+### 7.1.2 MTC Device triggering
+
+The requirements related to MTC Device triggering include the following:
+
+- The network shall be able to trigger MTC Devices to initiate communication with the MTC Server based on a trigger indication from the MTC Server.
+- The system shall provide a mechanism such that only trigger indications received from authorized MTC Servers will lead to triggering of MTC Devices.
+- Upon receiving a trigger indication from a source that is not an authorized MTC Server, the network shall be able to provide the details of the source (e.g. address) to the MTC User.
+- The system shall provide a mechanism to the MTC User to provide a set of authorized MTC Server(s).
+- Upon receiving a trigger indication, if the network is not able to trigger the MTC Device, the 3GPP system may send an indication to the MTC Server that triggering the MTC Device has been suppressed.
+
+Note: Suppression of triggering could be due to system conditions such as network congestion.
+
+- A MTC Device shall be able to receive trigger indications from the network and shall establish communication with the MTC Server when receiving the trigger indication. Possible options may include:
+ - Receiving trigger indication when the MTC Device is not attached to the network.
+ - Receiving trigger indication when the MTC Device is attached to the network, but has no data connection established.
+ - Receiving trigger indication when the MTC Device is attached to the network and has a data connection established.
+
+### 7.1.3 Addressing
+
+The system shall provide mechanisms, according to operator policy, where an MTC Server can send a mobile terminated message to the MTC Device. Scenarios include:
+
+- The MTC Server is located in the public IPv6 address space. The MTC Device is assigned a public IPv6 address by the MNO.
+
+
+
+Figure 7-1: MTC server and the MTC Device in the public IPv6 address space. The diagram shows two large ovals representing IPv6 Address Spaces. The left oval contains an 'MTC Device' (purple oval) and an 'MNO' (blue oval). The right oval contains an 'MTC Server' (purple oval). Arrows indicate connections: from the MTC Device to the MNO, and from the MTC Server to the MNO. The two ovals are connected at a single point on their right sides.
+
+**Figure 7-1: MTC server and the MTC Device in the public IPv6 address space**
+
+- The MTC Server is located in a public IPv4 address space; the MTC Device is assigned a private IPv4 address by the MNO.
+
+Alternatively, the MTC Server is located in a private IPv4 address space and is assigned a private IPv4 address by the MNO; the MTC Device is assigned a private IPv4 address by the MNO corresponding to the same IPv4 address space as the MTC Server.
+
+
+
+Figure 7-2: MTC Server in a public or private IPv4 address space, MTC Device in a private IPv4 address space. The diagram shows two large ovals. The left oval is labeled 'Private IPv4 Address Space' and contains an 'MTC Device' (purple oval) and an 'MNO' (blue oval). The right oval is labeled 'IPv4 Address Space' and contains an 'MTC Server' (purple oval). Arrows indicate connections: from the MTC Device to the MNO, and from the MTC Server to the MNO. The two ovals are connected at a single point on their right sides.
+
+**Figure 7-2: MTC Server in a public or private IPv4 address space,
+MTC Device in a private IPv4 address space**
+
+### 7.1.4 Identifiers
+
+The requirements for MTC related to identifiers include the following:
+
+- The system shall be able to uniquely identify the ME;
+- The system shall be able to uniquely identify the MTC Subscriber.
+
+Note 1: The two requirements above also apply to human-to-human communications. However, for Machine-Type Communications identifiers will have to be able to cater for a number of identifiers at least two orders of magnitude higher than for human-to-human communications.
+
+- In order to use MTC triggering, the system shall support association between an MTC Device identity and one or more Service Enablement Framework individually.
+
+Note 2: The Service Enablement Framework server in the network needs to associate its peer Service Enablement Framework client on the MTC Device with the external identifier of the MTC Device. Preconfiguration of the association is sufficient when the Service Enablement Framework knows the MTC Device identities in advance to the starting of the service, but this does not match all the relevant scenarios of service deployment.
+
+- The system shall provide mechanisms for the network operator to efficiently manage numbers and identifiers related to MTC Subscribers.
+
+### 7.1.5 Charging requirements
+
+The core network shall be able to:
+
+- count MTC Feature activation / de-activation.
+- collect charging data with a granularity (e.g. in time or location) that can identify the use of network resources when used outside the limits of subscription or MTC Feature, e.g. time window, location, or can identify when the MTC Device is overriding other restrictions (e.g. low priority).
+- count particular Monitoring events.
+
+Note: The above charging requirements apply to off line charging only.
+
+### 7.1.6 Security requirements
+
+The security requirements for MTC include the following:
+
+- MTC optimizations shall not degrade security compared to non-MTC communications
+
+### 7.1.7 Remote MTC device management
+
+The operator shall be able to manage MTC Devices using existing mechanisms (e.g. OMA DM)
+
+## 7.2. Specific service requirements – MTC Features
+
+### 7.2.1 Low Mobility
+
+The MTC Feature Low Mobility is intended for use with MTC Devices that do not move, move infrequently, or move only within a certain region.
+
+For the Low Mobility MTC Feature:
+
+- The network operator shall be able to change the frequency of mobility management procedures or simplify mobility management per MTC Device.
+- The network operator shall be able to define the frequency of location updates performed by the MTC Device.
+
+### 7.2.2 Time Controlled
+
+The MTC Feature Time Controlled is intended for use with MTC Applications that can tolerate to send or receive data only during defined time intervals and avoid unnecessary signalling outside these defined time intervals. The network operator may allow such MTC Applications to send/receive data and signalling outside of these defined time intervals but charge differently for such traffic.
+
+For the Time Controlled MTC Feature:
+
+- The network operator shall be able to reject access requests per MTC Device (e.g. attach to the network or set up a data connection) outside a defined access grant time interval.
+
+Note 1: The Time Controlled MTC Feature does not affect the MTC Server to send trigger indications to the MTC Device.
+
+- The network operator shall be able to allow access (e.g. attach to the network or set up a data connection) outside a defined access grant time interval and charge this differently.
+- The network shall reject access requests per MTC Device (e.g. attach to the network or set up a data connection) during a defined forbidden time interval (e.g. to allow maintenance of a MTC Server).
+- The local network shall be able to alter the access grant time interval based on local criteria (e.g. daily traffic load, time zones). The forbidden time interval shall not be altered.
+
+Note 2: It is assumed that an access grant time interval will not overlap a forbidden time interval.
+
+Note 3: "Local network" can refer to a VPLMN in roaming case, or to the local part of a large RPLMN (e.g. that spans across multiple time zones).
+
+- The network shall be able to restrict the duration of access by terminating access (e.g. detach or disconnect a data connection) after a defined access duration.
+
+Note 4: The defined access duration (e.g. 10 minutes) is pre-agreed between the network operator and the MTC Subscriber, and is typically long enough to ensure the completion of normal communication between MTC Device and MTC Server.
+
+- The MTC Device may disconnect immediately when it finishes its communications with the MTC Server before wait until the end of the access duration.
+- The network shall communicate the (altered) access grant time interval and the access duration to the MTC Device.
+- The network may communicate the (altered) access grant time interval and the access duration to the MTC Server/MTC User.
+
+Note 5: It is desirable that access of MTC Devices with the same access grant time interval is distributed across this interval in a manner to reduce peaks in the signalling and data traffic.
+
+### 7.2.3 Void
+
+### 7.2.4 Void
+
+### 7.2.5 Small Data Transmissions
+
+The MTC Feature Small Data Transmissions is intended for use with MTC Devices that send or receive small amounts of data.
+
+For the Small Data Transmissions MTC Feature:
+
+- The system shall support transmissions of small amounts of data with minimal network impact (e.g. signalling overhead, network resources, delay for reallocation).
+- Before transmission of small amount of data, the MTC Device may be attached or detached to/from the network.
+
+Note 1: "Transmission" implies either sending or receiving small amount of data.
+
+- The 3GPP system shall be able to count the number of small data transmissions per subscription e.g. for charging or statistical purposes.
+
+Note 2: observed size of many of the instances of data exchanges is on the order of 1K (1024) octets
+
+Note 3: Charging and accounting of small data transmissions between operators can be done on a bulk basis.
+
+### 7.2.6 Void
+
+### 7.2.7 Infrequent Mobile Terminated
+
+The MTC Feature Infrequent Mobile Terminated is intended for use with MTC Devices that mainly utilize mobile originated communications.
+
+For the Infrequent Mobile Terminated MTC Feature:
+
+- The network operator shall be able to reduce the frequency of mobility management procedures per MTC Device.
+- The network shall be able to maintain information on when the MTC Device is not reachable for mobile terminated communications. The network shall not trigger the MTC Device when it is known to be unreachable, and instead may inform the MTC Server that the MTC Device is not reachable.
+
+Note: With the Infrequent Mobile Terminated MTC Feature, the network operator should be able to minimize mobility management due to MTC Device movement .
+
+### 7.2.8 MTC Monitoring
+
+The MTC Feature MTC Monitoring is intended for monitoring MTC Device related events.
+
+For the MTC Monitoring MTC Feature:
+
+- The system shall provide mechanisms to detect the following events:
+ - behaviour which is not aligned with activated MTC Feature(s)
+ - change of the association between the ME and the USIM
+ - loss of connectivity. The maximum time between the actual loss of connectivity occurred and the loss of connectivity detected shall be configurable per subscription.
+ - communication failure events of the UE visible to the network (e.g. for troubleshooting)
+ - change of the location (geographical position and/or point of attachment in the network) of the MTC Device.
+
+Note 1: Loss of connectivity means it is no longer possible to establish signalling between the MTC Device and the network.
+
+Note 2: The maximum detection time is on the order of 1 minute to 1 hour.
+
+- The MTC Subscriber shall be able to define which of the above events will be detected.
+- Upon the above event detection, the network shall be able to:
+ - provide a warning notification to the MTC Server;
+ - limit the services provided to the MTC Device (e.g. reduce allocated resource).
+- The MTC User shall be able to define what occurs when an event is detected.
+- The MTC Device shall be able to transfer other event notification to the MTC Server where the event detection is out of 3GPP scope, for example, the loss of signal reception, notification when the MTC Device power level is lower than a threshold.
+
+Note 3: Loss of signal reception refers to a situation when a MTC Device can no longer receive the network which could be due to interference (e.g. from a jammer or other source) or other reasons.
+
+### 7.2.9 Void
+
+### 7.2.10 Secure Connection
+
+The MTC Feature Secure Connection is intended for use with MTC Devices that require a secure connection between the MTC Device and MTC Server/MTC Application Server.
+
+For the Secure Connection MTC Feature:
+
+- The network operator shall be able to efficiently provide network security for connection between MTC Device and a MTC Server or between MTC Device and a MTC Application Server in case there is a direct connection with the MTC Application Server. This applies even when some of the devices are roaming i.e. connected via a VPLMN.
+
+### 7.2.11 Void
+
+### 7.2.12 Void
+
+### 7.2.13 Void
+
+### 7.2.14 Group Based MTC Features
+
+#### 7.2.14.1 General
+
+A Group Based MTC Feature is a MTC Feature that applies to an MTC Group.
+
+- The system shall be optimized to handle MTC Groups. The system shall provide a mechanism to associate an MTC Device to a single MTC Group.
+- Each Group Based MTC Feature is applicable to all the members of the MTC Group.
+- An MTC Group shall be identified uniquely across 3GPP networks.
+
+Note 1: With Group Based MTC Features, each MTC Device is visible from the 3GPP Network perspective.
+
+Note 2: MTC Features that are not Group Based MTC Features can also be applied to MTC Group members.
+
+Note 3: An MTC Device can belong to more than one MTC group, but policy conflicts need to be avoided through administrative means.
+
+#### 7.2.14.2 Group Based Policing
+
+The MTC Feature Group Based Policing is intended for use with a MTC Group for which the network operator wants to enforce a combined QoS policy.
+
+For the Group Based Policing MTC Feature:
+
+- A maximum bit rate for the data that is sent/received by a MTC Group shall be enforced.
+
+Note: Policy control could be static to reduce complexity. In this case, static means that the policy for a specific MTC Group is fixed for the group and does not change due to dynamic conditions.
+
+#### 7.2.14.3 Group Based Addressing
+
+MTC Feature Group Based Addressing is intended for use with a MTC Group for which the network operator wants to optimize the message volume when many MTC Devices need to receive the same message.
+
+For the Group Based Addressing MTC Feature:
+
+- The network shall provide a mechanism to send a broadcast message within a particular geographic area, e.g. to wake up the MTC Devices that are members of that MTC Group; only MTC Devices of the target group configured to receive the broadcast message will recognize it.
+
+Note 1: The geographic area for the broadcast may be a cell sector, a cell or a group of cells.
+
+Note 2: Verification of receipt of a broadcast message is not necessary.
+
+# --- Annex A (informative): Use cases
+
+## Addressing from a centralized entity Use Case
+
+Metering devices are typically monitored and controlled by a centralized entity outside or inside the network operator system. Due to the need for centralized control, the centralized entity will inform or poll the metering device when it needs measurement information rather than the metering device autonomously sending measurements. Depending on the nature of the metering application, low latency responses are sometimes required (metering for high pressure pipelines for example). To accomplish this, the centralized entity will need to inform the metering device when it needs a measurement. Typically due to the limitation of IPv4 address space, the metering terminal is behind a NAT (Network Address Translator) where it is not assigned a routable IPv4 address.
+
+## Theft /Vandalism Vulnerable MTC Application Use Case
+
+In contrast to the traditional H2H devices, which are carefully held and protected by a person, MTC Devices are often located in remote areas and ideally are untouched after installation for many years. The remote locations make these devices more susceptible to tampering by unauthorized persons. The tampering of the MTC Device is often accompanied by damage to the metering device. The network has security mechanisms for protection for this type of activity which may not be effective for MTC Devices. The network can not prevent it but can detect it as early as possible in order to deactivate the ME's service and the related USIM. In addition, often theft/vandalism vulnerable MTC Devices are stationary after initial installation and activation. The stationarity of the MTC Device can be utilized to improve the detection of theft. If a known stationary devices moves, it can be concluded that the MTC Device has been stolen and thus the account deactivated.
+
+## Time Controlled MTC Application Use Case
+
+For some MTC applications the actual time at which communication takes place is less important, but low communication costs are extremely important. A network operator can offer low communication fees for this type of applications by allowing communication to take place during low traffic time periods only. Possibly the network operator may want to dynamically adjust these time periods based on the actual network traffic load at a specific time.
+
+## Radio Network Congestion Use Case
+
+Radio network congestion because of mass concurrent data transmission takes place in some MTC applications. One of the typical applications is the bridge monitoring with a mass of sensors. When a train passes through the bridge, all the sensors transmit the monitoring data almost simultaneously. The same thing happens in hydrology monitoring during the time of heavy rain and in building monitoring when intruders break in. The network should be optimized to enable a mass of MTC Devices in a particular area to transmit data almost simultaneously.
+
+## Core Network Congestion Use Case
+
+With many MTC applications, a large number of MTC Devices is affiliated with a single MTC User. These MTC Devices together are part of a MTC Group. The MTC User associated with the MTC Group owns a MTC Server which is connected to the PS network of a mobile network operator via an Access Point Name (APN) using the Gi interface. The MTC Devices in the MTC Group communicate with this MTC Server.
+
+Typically, the MTC Devices in the MTC Group are scattered over the network in such a way that the data simultaneously sent by the MTC Devices in any particular cell is limited and will not cause a radio network overload. Despite this, when a high number of MTC Devices are sending/receiving data simultaneously, data congestion may occur in the mobile core network or on the link between mobile core network and MTC Server where the data traffic related to MTC Group is aggregated. Preferably, a network operator and the MTC User have means to enforce a maximum rate for the data sent/received by the MTC Group.
+
+
+
+The diagram shows a 'Large group of MTC devices' represented by a vertical stack of eight small rectangles inside a blue oval. Lines connect these devices to two separate 'SGSN' boxes. Both 'SGSN' boxes have lines connecting them to a single 'GGSN' box. The 'GGSN' box is connected to an orange cloud. Inside the cloud, there is a 'MTC Server' represented by a computer icon. Red starburst icons, representing congestion, are placed on the link between the 'GGSN' and the cloud, and on the link between the cloud and the 'MTC Server'.
+
+Diagram illustrating congestion in a mobile core network and on the link between the mobile core network and an MTC Server. A large group of MTC devices is connected to two SGSNs. These SGSNs are connected to a GGSN, which is in turn connected to an MTC Server via a cloud. Red starburst icons indicate congestion points at the GGSN and on the link to the MTC Server.
+
+**Figure A-1: Congestion in mobile core network and on the link between mobile core network and MTC Server**
+
+## Signalling Network Congestion Use Case
+
+Congestion in the signalling network is caused by a high number of MTC Devices trying almost simultaneously: (1) to attach to the network or (2) to activate/modify/deactivate a connection. In a 3GPP system supporting MTC applications such an overload of the network can be caused by e.g. many mobile payment terminals that become active on a national holiday or by high numbers of metering devices becoming active almost simultaneously after a period of power outage. Also some MTC applications generate recurring data transmissions at precisely synchronous time intervals (e.g. precisely every hour or half hour). Preferably, the 3GPP system provides means to the network operator and MTC User to spread the resulting peaks in the signalling traffic.
+
+
+
+The diagram shows a 'Large number of vending machines' represented by a vertical stack of eight small rectangles inside a blue oval. Lines connect these machines to two 'SGSN' boxes. Each 'SGSN' box is connected to both an 'HSS' box and an 'MME' box. All four boxes ('SGSN', 'HSS', 'MME', and the second 'SGSN') have lines connecting them to a single 'GW' box. The 'GW' box is connected to an orange cloud. Inside the cloud, there is a 'Radius' box and a 'MTC Server' (represented by a computer icon). Red starburst icons, representing congestion, are placed on the links between the 'SGSN' and 'HSS', 'SGSN' and 'MME', 'HSS' and 'MME', and between the 'MME' and the 'GW'.
+
+Diagram illustrating signalling network congestion. A large number of vending machines are connected to two SGSNs, which are connected to an HSS and an MME. The MME is connected to a GW, which is connected to a Radius server and an MTC Server via a cloud. Red starburst icons indicate congestion points at the SGSNs, HSS, MME, and GW.
+
+**Figure A-2: Signalling network congestion**
+
+## Access Control with billing plan Use Case
+
+In some configurations, it may be necessary to restrict the access of a UICC that is dedicated to be used only with machine-type modules associated with a specific billing plan. It should be possible to associate a list of UICC to a list of terminal identity such as IMEISV so that if the UICC is used in an other terminal type, the access will be refused. See the following configuration:
+
+
+
+Figure A-3: Access Control with billing plan. The diagram shows two scenarios of network access control based on billing plans. In the top scenario, a 'Machine type module' (represented by a box with colored squares) with a 'USIM' and 'Ubiquitous plan' sends a 'Notification of IMEISV (machine type module)' to an 'SGSN'. The 'SGSN' is connected to a 'GGSN'. The access is 'Accepted'. In the bottom scenario, 'others' (represented by a laptop) with a 'USIM' and 'Ubiquitous plan' sends a 'Notification of IMEISV (handset or cart type)' to an 'SGSN'. The 'SGSN' is connected to a 'GGSN'. The access is 'Denied', indicated by a red 'X' over the connection line.
+
+**Figure A-3: Access Control with billing plan**
+
+## Extra Low Power Consumption Use Case
+
+For high mobility case, tracking MTC devices such as animal tracking MTC devices in natural world with high mobility require extra low power consumption because it is almost impossible to replace the battery or recharge the battery for animal tracking MTC device. Compared to the tracking devices installed in the cars and trucks because cars and trucks could generate electricity by themselves, extra low power consumption for these MTC devices is required.
+
+For cargo tracking, the cargo with a tracking MTC device could move very fast such as on a train or lorry and could stand still such as in the dock before loading or unloading. It is not desired to either change its battery or replace battery during the transport period, so extra low power consumption MTC devices are also required.
+
+For prisoner tracking MTC devices are already used by police, prisoners will not cooperate with police and would wish the MTC devices have flat batteries; therefore, extra low power consumption feature is required for these MTC devices. For the tracking MTC devices of elder people who have memory problem, children or pets, even the batteries of these MTC devices could be replaced or charged, however, considering the worst scenario – if they are missing, it requires the MTC devices with extra low power consumption and long working time in order to find them.
+
+For low mobility case, the gas meter MTC devices must be battery powered. Extra low power consumption for gas MTC devices is much more critical than electricity meters.
+
+## Extra Low Power Consumption with Time Controlled MTC Devices Use Case
+
+Time Controlled MTC Devices which send or receive data only at certain pre-defined periods may be operated in one or more modes that minimize power consumption.
+
+An MTC Device may be operated in a mode where it is expected to receive non-periodic messages (e.g. emergency messages or notifications of altered access period as with the MTC Feature Time Controlled outside the time controlled periods. The MTC Device should minimize power consumption while in a mode to support this.
+
+If the application requires the MTC Device to send or receive data within pre-defined periods and receive non-periodic messages outside these periods, operation at the lowest possible power consumption level to extend battery life should be achieved.
+
+## End-to-end security for roaming MTC devices
+
+An MTC Application communicates with a large number of MTC Devices that are located globally and may or may not be mobile. Examples of such devices are mobile navigation systems and payment terminals. Connectivity for the MTC Devices is provided by a single network operator that uses its roaming agreements to connect MTC Devices that are not within range of its own network.
+
+From the perspective of the operator of the MTC application its MTC Server and the domain of its network operator are part of a trusted domain. However, the domain of the roaming operator are not seen as part of the trusted domain, as is depicted in the figure below.
+
+
+
+The diagram shows a central 'MTC Server' inside a dashed box labeled 'trusted domain'. To the left and right of this box are four 'Operator domain' clouds, each represented by a yellow cloud shape. Below each cloud is an 'MTC Device' represented by an orange rectangle. Arrows point from each 'MTC Device' to its corresponding 'Operator domain' cloud. From the 'Operator domain' clouds, arrows point towards the 'MTC Server' inside the 'trusted domain' box. The 'Operator domain' clouds are interconnected by horizontal lines, showing a chain of connectivity.
+
+Diagram illustrating end-to-end security for roaming MTC devices. A central 'MTC Server' is enclosed in a dashed box labeled 'trusted domain'. Four 'Operator domain' clouds are shown, each connected to an 'MTC Device'. The 'MTC Server' is connected to the 'Operator domain' clouds, and the 'Operator domain' clouds are connected to the 'MTC Devices'.
+
+**Figure A-4: End-to-end security for roaming MTC devices**
+
+The operator of the MTC application therefore requires end-to-end security for messages exchanged between MTC application and MTC Devices. The network operator does not have control over the security features in the domain of the roaming operators. Furthermore, for efficiency reasons the roaming operators may decide on a local breakout to for instance the Internet for MTC traffic in which case the information partly travels over the Internet. The network operator needs to satisfy the MTC application owner's end-to-end security requirement without relying on network security alone.
+
+# Annex B (informative): Examples of MTC applications
+
+Some examples of machine-type communication applications are listed in the following table. This list is not exhaustive and is intended to be indicative of the scope of machine-type communication applications.
+
+| Service Area | MTC applications |
+|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Security | Surveillance systems
Backup for landline
Control of physical access (e.g. to buildings)
Car/driver security |
+| Tracking & Tracing | Fleet Management
Order Management
Pay as you drive
Asset Tracking
Navigation
Traffic information
Road tolling
Road traffic optimization/steering |
+| Payment | Point of sales
Vending machines
Gaming machines |
+| Health | Monitoring vital signs
Supporting the aged or handicapped
Web Access Telemedicine points
Remote diagnostics |
+| Remote Maintenance/Control | Sensors
Lighting
Pumps
Valves
Elevator control
Vending machine control
Vehicle diagnostics |
+| Metering | Power
Gas
Water
Heating
Grid control
Industrial metering |
+| Consumer Devices | Digital photo frame
Digital camera
eBook |
+
+# Annex C (informative): Change history
+
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+|---------|-----------|------------|--------|------|-----|--------|-----|---------------------------------------------------------------|--------|--------|-------|
+| SP-47 | SP-100192 | - | 22.220 | - | - | - | - | Raised from v1.2.2 to v.2.0.0 for approval | 1.2.2 | 2.0.0 | NIMTC |
+| SP-47 | - | - | 22.220 | - | - | - | - | Raised from v.2.0.0 to v.10.0.0 after approval of SA#47 | 2.0.0 | 10.0.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101157 | 22.368 | 0001 | 2 | Rel-10 | F | Deletion of section 5.2 | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101158 | 22.368 | 0003 | 2 | Rel-10 | F | Clarification of PAM | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101138 | 22.368 | 0005 | 1 | Rel-10 | F | CR to TS22.368 Clarification of Location Specific Trigger | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101139 | 22.368 | 0006 | 1 | Rel-10 | F | CR to TS22.368 Clarification of Infrequent Transmission | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101159 | 22.368 | 0009 | 3 | Rel-10 | F | Clarification of Requirements for Time Controlled MTC Feature | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100435 | S1-101143r | 22.368 | 0010 | 2 | Rel-10 | F | Clarification and completion of PAM requirements | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101142 | 22.368 | 0011 | 1 | Rel-10 | F | Clarification of local network in Time Controlled | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101077 | 22.368 | 0013 | - | Rel-10 | F | Correction of missing changes to clause 7.2.2 | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101078 | 22.368 | 0014 | - | Rel-10 | F | Correction of terminology | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101080 | 22.368 | 0015 | - | Rel-10 | F | Clarification of "may" in clause 7.2.2 | 10.0.0 | 10.1.0 | NIMTC |
+| SP-48 | SP-100400 | S1-101083 | 22.368 | 0017 | - | Rel-10 | F | Correction of MTC User shall in 7.2.8 | 10.0.0 | 10.1.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102258 | 22.368 | 0023 | 1 | Rel-10 | F | Simplification of Mobile Originated Only feature | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102259 | 22.368 | 0024 | 1 | Rel-10 | F | Simplification of Infrequent Mobile Terminated feature | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102260 | 22.368 | 0025 | 1 | Rel-10 | F | Clarification of MTC Monitoring feature | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102264 | 22.368 | 0029 | 1 | Rel-10 | F | Clarification of Group Based MTC Features | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102280 | 22.368 | 0038 | 2 | Rel-10 | F | Clarification of subscription | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102281 | 22.368 | 0018 | 2 | Rel-10 | F | Clarification on MTC Server relationship to network operator | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102282 | 22.368 | 0027 | 2 | Rel-10 | F | Clarification of Location Specific Trigger | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102287 | 22.368 | 0034 | 1 | Rel-10 | F | MTC Group Features definition clarification | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102288 | 22.368 | 0035 | 1 | Rel-10 | F | MTC Infrequent Transmission clarification | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102289 | 22.368 | 0036 | 1 | Rel-10 | F | MTC Secure Connection | 10.1.0 | 10.2.0 | NIMTC |
+| SP-49 | SP-100579 | S1-102290 | 22.368 | 0037 | 2 | Rel-10 | F | MTC Time Controlled clarification | 10.1.0 | 10.2.0 | NIMTC |
+| SP-50 | SP-100798 | S1-103312 | 22.368 | 0049 | 2 | Rel-10 | F | NIMTC Terminology | 10.2.0 | 10.3.0 | NIMTC |
+| SP-50 | SP-100798 | S1-103311 | 22.368 | 0051 | 2 | Rel-10 | B | Clarification of data delay in case of Overload | 10.2.0 | 10.3.0 | NIMTC |
+| SP-50 | SP-100801 | S1-103209 | 22.368 | 0045 | 1 | Rel-11 | C | Clarification on the requirements of Low Mobility MTC Feature | 10.2.0 | 11.0.0 | SIMTC |
+| - | | | | | | | | LTE logo changed into LTE Advanced logo | 11.0.0 | 11.0.1 | - |
+| SP-51 | SP-110162 | S1-110427 | 22.368 | 0069 | 2 | Rel-11 | A | MTC charging requirements in Rel-11 | 11.0.1 | 11.1.0 | NIMTC |
+| SP-51 | SP-110162 | S1-110411 | 22.368 | 0071 | - | Rel-11 | A | Clarification of EAB | 11.0.1 | 11.1.0 | NIMTC |
+| SP-51 | SP-110167 | S1-110429 | 22.368 | 0058 | 3 | Rel-11 | B | Additional security for MTC Triggering requirements | 11.0.1 | 11.1.0 | SIMTC |
+| SP-51 | SP-110167 | S1-110414 | 22.368 | 0059 | 2 | Rel-11 | B | Suppress MTC device triggering | 11.0.1 | 11.1.0 | SIMTC |
+| SP-51 | SP-110167 | S1-110420 | 22.368 | 0080 | 2 | Rel-11 | B | MTC - IMS Service Layer Capabilities | 11.0.1 | 11.1.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111026 | 22.368 | 0075 | - | Rel-11 | F | Correction of charging requirements | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111036 | 22.368 | 0072 | - | Rel-11 | B | MTC - IMS Service Layer Capabilities | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111304 | 22.368 | 0091 | - | Rel-11 | F | Clarification of MTC Device management requirement | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111328 | 22.368 | 0088 | 1 | Rel-11 | F | Clarification of MTC identifier to | 11.1.0 | 11.2.0 | SIMTC |
+
+| | | | | | | | | | | | |
+|-------|-----------|-----------|--------|------|---|--------|---|---------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|------------|
+| | | | | | | | | aligning it with MTC Group feature | | | |
+| SP-52 | SP-110374 | S1-111329 | 22.368 | 0083 | 2 | Rel-11 | B | New Requirements for MTC Monitoring Feature | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111373 | 22.368 | 0092 | 2 | Rel-11 | A | Correction of SIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111374 | 22.368 | 0078 | 2 | Rel-11 | C | MTC Device Trigger and Time Controlled MTC Feature | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111375 | 22.368 | 0081 | 3 | Rel-11 | F | Clarification on MTC User | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111377 | 22.368 | 0089 | 2 | Rel-11 | F | Clarification of requirements for MTC | 11.1.0 | 11.2.0 | SIMTC |
+| SP-52 | SP-110374 | S1-111379 | 22.368 | 0079 | 3 | Rel-11 | C | Introduction of new scenarios for IP addressing | 11.1.0 | 11.2.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112334 | 22.368 | 0095 | 3 | Rel-11 | F | Clarification to small data transmissions requirement | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112335 | 22.368 | 0103 | 2 | Rel-11 | C | Clarification of MTC Small Data | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112336 | 22.368 | 0101 | 1 | Rel-11 | B | Location Monitoring Requirement for MTC Monitoring Feature | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112337 | 22.368 | 0096 | 2 | Rel-11 | F | Correction of offline MTC Device Triggering | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112338 | 22.368 | 0108 | 1 | Rel-11 | D | Editorial CR on offline MTC Devices | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112339 | 22.368 | 0098 | 2 | Rel-11 | C | MTC Group-Based Addressing | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110578 | S1-112412 | 22.368 | 0099 | 3 | Rel-11 | F | MTC Small Data Transmissions | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110651 | S1-112169 | 22.368 | 0106 | 2 | Rel-11 | F | CR to 22.368 - Moving "Network provided destination for uplink data" requirement from 22.368 into 22.101 | 11.2.0 | 11.3.0 | SIMTC |
+| SP-53 | SP-110651 | S1-112171 | 22.368 | 0107 | 2 | Rel-11 | F | CR to 22.368 - Moving PS-Only requirements from 22.368 into 22.101 | 11.2.0 | 11.3.0 | SIMTC |
+| SP-55 | SP-120103 | S1-120334 | 22.368 | 0120 | 3 | Rel-11 | F | Security to MTC server and MTC application | 11.3.0 | 11.4.0 | SIMTC |
+| SP-56 | SP-120289 | S1-121376 | 22.368 | 0126 | 1 | Rel-11 | F | Clarify restricting use of a USIM to specific MEs/MTC Devices | 11.4.0 | 11.5.0 | SIMTC |
+| SP-56 | SP-120289 | S1-121447 | 22.368 | 0128 | 4 | Rel-11 | F | MTC Server Definition | 11.4.0 | 11.5.0 | SIMTC |
+| SP-56 | SP-120288 | S1-121457 | 22.368 | 0130 | 5 | Rel-11 | F | MTC Device Power Level Monitoring | 11.4.0 | 11.5.0 | TEI11 |
+| SP-56 | SP-120289 | S1-121458 | 22.368 | 0131 | 4 | Rel-11 | F | Connection Error Codes for Troubleshooting Requirement | 11.4.0 | 11.5.0 | SIMTC |
+| SP-57 | SP-120524 | S1-122513 | 22.368 | 0133 | 2 | Rel-12 | F | Clarification of MTC Charging Requirements wrt on line/off line | 11.5.0 | 12.0.0 | MTCe-SRM |
+| SP-57 | SP-120533 | S1-122516 | 22.368 | 0127 | 7 | Rel-12 | C | External identifier availability | 11.5.0 | 12.0.0 | MTCe-SIMSE |
+| SP-57 | SP-120533 | S1-122435 | 22.368 | 0132 | 1 | Rel-12 | B | MTC Device and MTC Server relation with Service Enablement Frameworks | 11.5.0 | 12.0.0 | MTCe-SIMSE |
+| SP-58 | SP-120868 | S1-124465 | 22.368 | 0144 | - | Rel-12 | C | Removal of requirement to be able to count for device initiated signalling | 12.0.0 | 12.1.0 | MTCe-SRM |
+| SP-58 | SP-120868 | S1-124489 | 22.368 | 0139 | 2 | Rel-12 | C | Clean-up of Location specific trigger Requirement | 12.0.0 | 12.1.0 | MTCe-SRM |
+| SP-58 | SP-120868 | S1-124512 | 22.368 | 0145 | 2 | Rel-12 | C | Moving MTC Feature Infrequent Transmission into a generic requirement | 12.0.0 | 12.1.0 | MTCe-SRM |
+| SP-58 | SP-120868 | S1-124488 | 22.368 | 0136 | 2 | Rel-12 | C | Clean-up of Time Tolerant Requirement | 12.0.0 | 12.1.0 | MTCe-SRM |
+| SP-59 | SP-130104 | S1-131289 | 22.368 | 0146 | 2 | Rel-12 | C | Clarification and merge of Mobile Originated Only and Infrequent Mobile Terminated | 12.1.0 | 12.2.0 | MTCe-SRM |
+| SP-59 | SP-130104 | S1-131290 | 22.368 | 0147 | 2 | Rel-12 | C | Moving MTC Priority Alarm into a generic requirement | 12.1.0 | 12.2.0 | MTCe-SRM |
+| SP-59 | SP-130109 | S1-131302 | 22.368 | 0148 | 2 | Rel-12 | D | Clarification of requirements for the support of multiple service enablement frameworks | 12.1.0 | 12.2.0 | MTCe-SIMSE |
+| SP-62 | SP-130593 | S1-135102 | 22.368 | 0151 | - | Rel-12 | F | Removal of group based charging requirements | 12.2.0 | 12.3.0 | MTCe-SRM |
+| SP-64 | - | - | - | - | - | - | - | Rel.13 version created to keep text applicable to Rel-13 only, | 12.3.0 | 13.0.0 | - |
+
+| | | | | | | | | | | | |
+|-----------|-----------|-----------|--------|-----|---|--------|---|--------------------------------------------------------------------------------------|--------|--------|-------|
+| | | | | | | | | removed in the Rel-12 version 12.4.0 by CR0153r1 | | | |
+| SP-66 | SP-140751 | S1-144352 | 22.368 | 155 | - | Rel-13 | F | Align the MTC monitoring requirements with Service Exposure requirements | 13.0.0 | 13.1.0 | TEI13 |
+| SP-75 | | | | | - | Rel-14 | | Updated to Rel-14 by MCC | 13.1.0 | 14.0.0 | |
+| Aug. 2017 | - | - | | | - | Rel-14 | | Previous version was incorrectly saved as "22638-e10.doc" instead of "22368-e00.doc" | 14.0.0 | 14.0.1 | - |
+| July 2019 | - | - | - | - | - | Rel-15 | | Updated to Rel-15 by MCC | 14.0.1 | 15.0.0 | |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|-----------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-07 | SA#88e | - | - | - | - | Updated to Rel-16 by MCC | 16.0.0 |
+| 2022-03 | SA#95e | - | - | - | - | Updated to Rel-17 by MCC | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22468/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-18/22_series/22468/3da1a07cb87051bf616c9876db958cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4cf99ee4f48afabd23794cbff4a85df6e4020fb
--- /dev/null
+++ b/marked/Rel-18/22_series/22468/3da1a07cb87051bf616c9876db958cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2abf5f7f4788d42961176c53f4952fef9d4a796a107537f76ddc6262a7a8d1d3
+size 64694
diff --git a/marked/Rel-18/22_series/22468/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22468/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c6eb67c3a52cceb12528673609a645eceb40bcd
--- /dev/null
+++ b/marked/Rel-18/22_series/22468/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64a7f181b7d4896062f1e42663d74140470e80d1bb703b39056ab4e936f0ccdd
+size 9473
diff --git a/marked/Rel-18/22_series/22468/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22468/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..708fcd72236124fab01c24ad5ea56a9007e7129f
--- /dev/null
+++ b/marked/Rel-18/22_series/22468/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9649a3d26acb7cf967f685d6ace0bcd002eb8e30dce690149c94399258fed05b
+size 7160
diff --git a/marked/Rel-18/22_series/22468/raw.md b/marked/Rel-18/22_series/22468/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b6f1c7bbd9a74a5bbbd06dae04435894bbc1776d
--- /dev/null
+++ b/marked/Rel-18/22_series/22468/raw.md
@@ -0,0 +1,727 @@
+
+
+# 3GPP TS 22.468 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Group Communication System Enablers (GCSE) (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+Group, Communication, Service
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Overview (informative)..... | 7 |
+| 4.1 Service description of a Group Communication service..... | 7 |
+| 4.2 Relation to Group Communication System Enablers ..... | 8 |
+| 5 Functional requirements..... | 8 |
+| 5.1 Overall requirements..... | 8 |
+| 5.1.1 High level requirements ..... | 8 |
+| 5.1.2 Performance..... | 8 |
+| 5.1.3 Service continuity ..... | 9 |
+| 5.1.4 Resource efficiency ..... | 9 |
+| 5.1.5 Scalability ..... | 9 |
+| 5.1.6 Security requirements for Group Communication ..... | 9 |
+| 5.2 Group handling..... | 10 |
+| 5.2.1 Creation, modification, and deletion of GCSE Groups ..... | 10 |
+| 5.2.1.1 General..... | 10 |
+| 5.2.1.2 GCSE Group Management by Users ..... | 10 |
+| 5.2.1.3 GCSE Group Management by 3rd parties ..... | 10 |
+| 5.2.2 Geographical scope of GCSE Groups ..... | 10 |
+| 5.3 Group Communication ..... | 11 |
+| 5.3.1 Group Communication setup requirements ..... | 11 |
+| 5.3.2 Services to the Group Member..... | 11 |
+| 5.3.3 Group Member requests of the system..... | 11 |
+| 5.3.4 Priority and pre-emption of GCSE communication ..... | 11 |
+| 5.3.5 Services provided during an on-going Group Communication..... | 12 |
+| 5.3.6 User perception of Group Communication ..... | 12 |
+| 6 Interaction with other services and functions ..... | 12 |
+| 6.1 Emergency calling..... | 12 |
+| 6.2 Interaction with ProSe..... | 12 |
+| Annex A (informative): Use cases..... | 14 |
+| A.1 Speech Group Call use case ..... | 14 |
+| A.1.1 Description ..... | 14 |
+| A.1.2 Pre-conditions..... | 14 |
+| A.1.3 Service flows ..... | 14 |
+| A.1.3.1 Service Flow 1 – Joining a group..... | 14 |
+| A.1.3.2 Service Flow 2 – Joining and leaving a group based on group operating area ..... | 14 |
+| A.1.3.3 Service Flow 3 – Call start ..... | 14 |
+| A.1.3.4 Service Flow 4 – Call interruption ..... | 15 |
+| A.1.3.5 Service Flow 5 – Talking party changeover..... | 15 |
+| A.1.3.6 Service Flow 6 – Late Entry and mobility..... | 15 |
+| A.1.3.7 Service Flow 7 – Call release ..... | 16 |
+| A.1.3.8 Service Flow 8 – Blocking of resources..... | 16 |
+| A.1.4 Post-conditions ..... | 16 |
+| A.2 "See what I see" use case ..... | 16 |
+| A.2.1 Description ..... | 16 |
+| A.2.2 Actors ..... | 16 |
+
+| | | |
+|-------------------------------|-------------------------------------------------------------|-----------|
+| A.2.3 | Pre-conditions..... | 17 |
+| A.2.4 | Service flows..... | 17 |
+| A.2.5 | Post-condition..... | 17 |
+| A.3 | Harmonized multi-agency use case..... | 18 |
+| A.3.1 | Description ..... | 18 |
+| A.3.2 | Actors ..... | 18 |
+| A.3.3 | Pre-conditions..... | 18 |
+| A.3.4 | Service flows ..... | 18 |
+| A.3.5 | Post-condition..... | 19 |
+| Annex B (informative): | Group communication concept(s)..... | 20 |
+| Annex C (informative): | Description of usage of GCSE for public safety ..... | 22 |
+| Annex D (informative): | Change history..... | 23 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+To position 3GPP radio as technology for critical communications such as public safety, Group Communication is needed.
+
+Group Communication function complements its sibling communication feature of proximity-based services (ProSe).
+
+# --- 1 Scope
+
+The present document collects the requirements as relevant to improve the 3GPP system to support Group Communication for Public Safety and Critical Communication and other services.
+
+For Public Safety and Critical Communication Services, US requirements as specified in NPSTC (Mission Critical Voice Requirements) [2], [3], [4], the TETRA + Critical Communications Association (TCCA) [8] and ITU [6], [7] inputs are taken as starting point.
+
+Other regional requirements may also be reflected in the work. The requirements are worded in a way to easily accommodate future requirements from other regions or stakeholders.
+
+Other services have corresponding regulatory and service justification.
+
+# --- 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] Recommended Minimum Technical Requirements to Ensure Nationwide Interoperability for the Nationwide Public Safety Broadband Network, Final Report, NPSTC BBWG, May 22, 2012.
+- [3] Mission Critical Voice Communications Requirements for Public Safety, NPSTC BBWG, August 30, 2011.
+- [4] Public Safety Broadband High-Level Statement of Requirements for FirstNet Consideration, NPSTC Report Rev B, June 13, 2012.
+- [5] 3GPP TS 22.101: "Service aspects; Service principles".
+- [6] ITU-T Recommendation G.114 One-Way Transmission Time, May 2003.
+- [7] ITU-T Recommendation Y.1541 Network Performance Objectives for IP-Based Services, December 2011
+- [8] ETSI ETR 086: "Trans European Trunked Radio (TETRA) System; Technical Requirements Specification Part 1: Voice plus Data (V+D) systems", January 1994.
+- [9] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+
+# --- 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].
+
+**Group Member:** A user assigned to a GCSE Group.
+
+**GCSE Group:** A set of Group Members.
+
+**Receiver Group Member:** A Group Member of a GCSE Group that has interest expressed in receiving ongoing or future Group Communications of that GCSE Group.
+
+**Transmitter Group Member:** A Group Member of a GCSE Group that is authorized to transmit an ongoing or future Group Communications for that GCSE Group.
+
+**Group Communication:** Communication from Transmitter Group Members to Receiver Group Members.
+
+**Group Communication System Enabler (GCSE):** A 3GPP feature enabling an application layer functionality to provide Group Communication.
+
+**Multipoint Service:** A service used to distribute the same content to many UEs in a resource efficient way.
+
+## 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].
+
+| | |
+|-------|---------------------------------------------|
+| CN | Core Network |
+| GCSE | Group Communication System Enabler |
+| LMR | Land Mobile Radio |
+| ProSe | Proximity Services |
+| PTT | Push to Talk |
+| RAN | Radio Access Network |
+| TETRA | TERrestrial Trunked Radio |
+| TCCA | TETRA + Critical Communications Association |
+
+# --- 4 Overview (informative)
+
+## 4.1 Service description of a Group Communication service
+
+A Group Communication Service is intended to provide a fast and efficient mechanism to distribute the same content to multiple users in a controlled manner as an enabler for a variety of services.
+
+As an example, the concept of group communications is used extensively in the operation of classical Land Mobile Radio (LMR) systems used for, but not limited to, Public Safety organizations. At the moment, the primary use of a Group Communication Service in LMR is to provide "Push to Talk" (PTT) functionality, so a Group Communication Service based on the 3GPP system should enable PTT voice communications with comparable performance.
+
+Another example is network controlled interactive services. 5G UEs will include new forms of devices, e.g. VR/AR devices, robots, game consoles, etc. These will be used in diverse environments including public spaces, in educational institutions and in the work place. These supported scenarios entail efficient support of 5G UEs executing group communication applications, specifically gaming and interactive data exchange applications with delay sensitivity and demanding throughput.
+
+The service should allow flexible modes of operation as the users and the environment they are operating in evolves. For example, the capabilities of the 3GPP system allow for broadband communication, so Group Communication Service is expected to support, voice, video or, more general, data communication. Also the 3GPP system can allow users to communicate to several groups at the same time in parallel e.g. voice to one group, different streams of video or data to several other groups.
+
+The users of Group Communication Service are organised into groups; a user can be member of more than one group.
+
+## 4.2 Relation to Group Communication System Enablers
+
+The requirements listed in the present document shall serve as requirements to develop enablers; i.e. modular functions and open interfaces (e.g. a resource efficient distribution mechanism) that can be used to design Group Communication Services. This is to flexibly accommodate the different operational requirements on Group Communication Services that are expected to be different for various types of user groups (e.g. police or fire brigade), or from country to country.
+
+# --- 5 Functional requirements
+
+## 5.1 Overall requirements
+
+### 5.1.1 High level requirements
+
+The ability to make use of the Group Communication System Enabler provided by the 3GPP system shall be enabled on a Group Member basis.
+
+The system shall provide a mechanism to indicate network support of Group Communication System Enabler to the UE.
+
+The UE shall have the ability to indicate the network support of Group Communication System Enabler to the user.
+
+Group Communication System Enabler shall support various media such as conversational type communication (e.g. voice, video) or streaming (e.g. video) or data (e.g. messaging) or a combination of them.
+
+The system shall be able to uniquely identify a GCSE group. The system shall be able to uniquely identify a Group Member within a GCSE group
+
+The system shall provide a mechanism to send a Group Communication to all Receiver Group Members.
+
+Only Receiver Group Members of the GCSE Group shall be able to receive from that GCSE Group via Group Communication.
+
+The system shall be able to authorise a Group Member to become a Transmitter Group Member.
+
+A Transmitter Group Member shall be able to transmit to a GCSE Group that it is a member of, with or without being a Receiver Group Member of that GCSE Group.
+
+The interface between the GCSE client on the UE and the network shall be an open interface.
+
+Note 1: As GCSE Groups can be composed of users from different agencies in different territories using GCSE clients provided by different manufacturers it is essential that multi-vendor interworking is facilitated.
+
+The network shall provide a third party interface for Group Communication. This implies that the interface supports e.g. charging and authentication/authorisation.
+
+The system shall provide a mechanism for a Group Member that is not connected via a 3GPP network, to communicate in a Group Communication for a GCSE Group that it is a member of.
+
+Note 2: This requirement accommodates the need to support a console-type dispatching device, which is most often a wired device used in Group Communications by Public Safety.
+
+### 5.1.2 Performance
+
+The system shall be optimized to minimize the time intervals related to the use of Group Communication.
+
+The recommended time intervals specified below are for consideration in the development of detailed RAN/CN requirements, and the evaluation of architecture solutions.
+
+The system should provide a mechanism to support a Group Communication end-to-end setup time less than or equal to 300ms. It is assumed that this value is for an uncontended network, where there is no presence checking and no acknowledgements requested from Receiver Group Member(s). The end-to-end setup time is defined as the time
+
+between when a Group Member initiates a Group Communication request on a UE and the point when this Group Member can start sending start sending a voice or data communication.
+
+The time from when a UE requests to join an ongoing Group Communication to the time that it receives the Group Communication should be less than or equal to 300ms.
+
+Note: The 300 ms indicated in the preceding requirements is based on requirements from ETSI ETR 086 [8] for legacy TETRA mission critical voice systems. It is understood that these requirements are particularly important for half duplex voice communication and other data that is delay sensitive. These requirements may not be met in some cases where the data is delay insensitive e.g., a large document and/or where the type of Group Communication requires acknowledgement(s) from Receiver Group Members before it is allowed to proceed.
+
+The end to end delay for media transport for Group Communications should be less than or equal to 150 ms [6, 7].
+
+### 5.1.3 Service continuity
+
+When UEs are moving among cells during Group Communication, service continuity shall be supported.
+
+### 5.1.4 Resource efficiency
+
+The system shall provide a mechanism to efficiently distribute data for Group Communication.
+
+### 5.1.5 Scalability
+
+The number of Receiver Group Members in any area may be unlimited
+
+The system shall support multiple distinct Group Communications in parallel to any one UE that is capable of supporting that number of distinct Group Communications in parallel. The mechanisms defined shall allow future extension of the number of distinct Group Communications supported in parallel.
+
+Note: This includes both multiple Group Communications within the same GCSE Group, and multiple Group Communications associated with multiple GCSE Groups. The actual number of such Group Communications achievable and desirable will depend on the type of media.
+
+### 5.1.6 Security requirements for Group Communication
+
+The system shall support at least the same security level for Group Communication (e.g. for Authentication, Integrity, Confidentiality and Privacy) as a 3GPP LTE packet data bearer.
+
+### 5.1.7 Charging requirements for Group Communication
+
+The system shall support the collection of resource and service usage information for Group Communication.
+
+### 5.1.8 Roaming and network interworking requirements
+
+The system shall support the transmitting and/or receiving of Group Communication by Group Members that are roaming.
+
+Subject to operator agreement, the system shall be able to support Group Communications where Group Members are attached to different PLMNs.
+
+An interface shall be provided to enable Group Communication interworking between a network offering GCSE-based Group Communication Services with either or both of:
+
+- another 3GPP network offering GCSE-based Group Communication Services,
+- a non-3GPP network offering group communication services.
+
+### 5.1.9 High availability of Group Communication
+
+The system shall be capable of achieving high levels of availability for Group Communications utilising GCSE, e.g. by seeking to avoid single points of failure in the GCSE architecture and/or by including recovery procedures from network failures.
+
+## 5.2 Group handling
+
+### 5.2.1 Creation, modification, and deletion of GCSE Groups
+
+#### 5.2.1.1 General
+
+There are two mutually exclusive ways that the 3GPP System supports GCSE Group management creation, modification and deletion functions, by authorized users and by third parties.
+
+General requirements that apply to both are listed below.
+
+The system shall provide a mechanism for the dynamic creation, modification, and deletion of GCSE Groups.
+
+Information additional to the set of Group Members shall be associated with a GCSE Group, to be used by the system to identify the GCSE Group and to specify attributes that determine how it is changed and used. This may be used to, e.g. define which Group Members are authorized for administrative functions, and whether the GCSE Group can be relayed via ProSe.
+
+The system shall provide notification of the creation or deletion of a GCSE Group to its Group Members.
+
+The system shall provide a mechanism to remotely configure a UE with any GCSE related information.
+
+#### 5.2.1.2 GCSE Group Management by Users
+
+If authorised, a user shall be able to request and receive a list of all the GCSE Groups for which it is a Group Member.
+
+A mechanism shall be provided such that, if authorized, a user may modify information associated with a GCSE Group, add or remove Group Members of a GCSE Group, or create/delete a GCSE Group.
+
+If authorized, a user shall be able to request and receive a list of Group Members of a particular GCSE Group.
+
+If authorized, a user shall be able to request a notification for when specific or any Group Member(s) is added to or removed from a particular GCSE Group.
+
+#### 5.2.1.3 GCSE Group Management by 3rd parties
+
+The 3GPP system shall allow a 3rd party (e.g., a gaming server) to provide information to be used for group communication (e.g. group ID and group member list).
+
+### 5.2.2 Geographical scope of GCSE Groups
+
+GCSE Groups shall by definition be of system wide scope. Optionally, GCSE Groups may be geographically restricted.
+
+The system shall provide a mechanism to restrict all Group Communications for a given GCSE Group to a defined geographic area. In this case Group Members shall be able to receive and/or transmit only within this geographic area.
+
+The system shall provide a mechanism to redefine the geographic area for a GCSE Group that has a defined geographic area.
+
+The system shall provide a mechanism to override geographic area restrictions for a GCSE Group for a particular Group Communication transmission.
+
+The system shall provide a mechanism to restrict a particular Group Communication transmission to a defined geographic area within the geographical scope of that group. In this case only Receiver Group Members within the geographic area shall receive the Group Communication.
+
+## 5.3 Group Communication
+
+### 5.3.1 Group Communication setup requirements
+
+A Transmitter Group Member shall be able to transmit a Group Communication for a GCSE Group without knowledge of the identities of other GCSE Group Members.
+
+A Group Member shall be able to request to join or leave an established Group Communication.
+
+The system shall provide a mechanism to setup, release, and modify a multipoint service with applicable parameters e.g. QoS, priority.
+
+The system shall validate the parameters received in the request to setup or modify a Group Communication based on the policy specified by the group's subscription information, e.g. checks for QoS, priority.
+
+The system shall provide the means to notify the requesting entity of any updates in the status of an on-going Group Communication.
+
+The system shall provide notification to the requesting entity of the outcome of a request to setup, release, or modify a multipoint service.
+
+### 5.3.2 Services to the Group Member
+
+The system shall provide a mechanism to permit a Group Member to request notification when a Group Communication is initiated using that GCSE group.
+
+The system shall provide notification of a Group Communication to Group Members that have requested notification for the GCSE Group.
+
+### 5.3.3 Group Member requests of the system
+
+A Group Member shall be able to express interest to receive Group Communications when the GCSE Group is used for Group Communications.
+
+The system shall provide a mechanism for a Receiver Group Member receiving a Group Communication to be able to accept, reject, or ignore the Group Communication.
+
+The system shall provide a mechanism for a Receiver Group Member receiving a Group Communication to be required to accept the Group Communication.
+
+### 5.3.4 Priority and pre-emption of GCSE communication
+
+The following requirements apply to the allocation and retention of system resources:
+
+The system shall provide a mechanism to support at least n priority levels for Group Communication.
+
+The system shall provide a mechanism to support reassignment of Group Communication priority level.
+
+The network operator shall be able to configure each Group Communication priority level with the ability to pre-empt lower priority Group Communications and non-Group Communications traffic.
+
+The system shall provide a mechanism to allow pre-emption of lower priority for Group Communications and non-Group Communications traffic.
+
+Group Members within a GCSE Group shall be able to have different priorities from each other.
+
+### 5.3.5 Services provided during an on-going Group Communication
+
+An entity shall be able to request a notification when a specific Group Member ceases to be a Receiver Group Member.
+
+A Receiver Group Member ceases to be a Receiver Group Member of a certain group by:
+
+- user decision
+- third party decision
+- after a service dependent amount of time
+- after a system configurable amount of time of unavailability.
+
+A notification shall be provided to the requesting entity when a specific Group Member ceases to be a Receiver Group Member.
+
+Note: During the lifetime of a Group Communication the Receiver Group Members of the Group Communication may change. In the case where there are no Receiver Group Members, Transmitter Group Members would need to know that there are no other Receiver Group Members, and when another Receiver Group Member returns to the Group Communication.
+
+A Transmitter Group Member ceases to be a Transmitter Group Member of a certain group by:
+
+- user decision
+- third party decision
+- after a service dependent amount of time
+- after a system configurable amount of time of unavailability.
+
+### 5.3.6 User perception of Group Communication
+
+All Receiver Group Members in a given area shall receive the Group Communication at the same time according to user perception.
+
+All changes to the GCSE Group (e.g., adding or removing group members) shall take effect as soon as possible.
+
+All changes to the set of Receiver Group Members shall take effect in the Group Communication as soon as possible.
+
+# --- 6 Interaction with other services and functions
+
+## 6.1 Emergency calling
+
+The ability for a UE to make an emergency call (3GPP TS 22.101 [5]) shall be unaffected by being in a Group Communication.
+
+## 6.2 Interaction with ProSe
+
+If the 3GPP system supports ProSe, the 3GPP system shall be able to make use of ProSe Group Communication and the public safety ProSe UE-to-Network Relay for Group Communication, subject to operator policies and UE capabilities or settings.
+
+A public safety ProSe-enabled UE not served by a public safety enabled 3GPP system shall be able to support Group Communication based on ProSe Communication paths. A public safety ProSe-enabled UE shall be able to dynamically express its interest in receiving, via a public safety ProSe UE-to-Network Relay, the Group Communications of one or more GCSE Groups for which it is authorized.
+
+A public safety ProSe UE-to-Network Relay shall be able to relay Group Communication to/from ProSe Communication paths, if the following conditions apply:
+
+- the GCSE Group is allowed to be relayed; and
+- the public safety ProSe UE-to-Network Relay is allowed to relay Group Communication.
+
+A public safety ProSe UE-to-Network Relay shall be able to restrict the relayed Group Communication on a per group basis.
+
+The system shall support groups whose membership shall be the same irrespective of whether a Group Communication is made using ProSe Group Communication or GCSE Group Communication.
+
+GCSE Group Members shall be able to access Group Communication services using ProSe Communication paths [9] and/or by network path (3GPP TS 22.278 [9]).
+
+# --- Annex A (informative): Use cases
+
+## A.1 Speech Group Call use case
+
+### A.1.1 Description
+
+This use case describes communications in a speech group call.
+
+### A.1.2 Pre-conditions
+
+A "traffic" group is enabled on the system, where "system" refers to the combination of group call application and underlying 3GPP network.
+
+The list of UEs permitted to join the group is defined on the system.
+
+The operating area of the group is defined on the system (e.g. by lists of radio sites which are allowed to support the group).
+
+UEs are configured with lists of groups that they may join.
+
+Mick is a dispatcher in control of "traffic" group.
+
+Traffic group officers are members of "traffic" group and include Ned, Oscar, Peter and Roger.
+
+Simon is another officer who is not authorised to use "traffic" group.
+
+### A.1.3 Service flows
+
+#### A.1.3.1 Service Flow 1 – Joining a group
+
+Traffic group officers including Ned, Roger and Peter (but not Oscar), who are within the defined operating area of the traffic group, select the group on their UE devices in order to join the group and communicate in the group. The group is also selected on Mick's dispatcher terminal.
+
+The UE indicates to the user if joining the group was successful.
+
+Oscar is located outside the defined area of the traffic group. His UE indicates that he is out of area for this group.
+
+Simon is within the defined area of the "traffic" group, but he is not authorised to use the group.
+
+#### A.1.3.2 Service Flow 2 – Joining and leaving a group based on group operating area
+
+Oscar has not changed the group setting on his UE. He moves into the group's operating area. His UE automatically joins the group, and he receives an indication on the UE that he is now within the operating area of the group.
+
+Ned moves to an area outside the operating area of the group. The system automatically removes his UE from the group. The UE indicates to Ned that he is now outside the operating area of the group.
+
+#### A.1.3.3 Service Flow 3 – Call start
+
+Ned moves back to an area within the defined operating area of the group. His UE automatically joins the group, and he receives an indication that he is now within the operating area of the group.
+
+The group is not carrying traffic.
+
+Oscar initiates a call to the group on his UE. The system sets the call up. Oscar receives an indication that the call is set up, and he may talk, within 300 ms of initiating the call setup. Other group members, irrespective of their location relative to Oscar and irrespective of the number of users who have joined the group, receive an indication that a call is starting within 300 ms of Oscar initiating the call setup.
+
+The system efficiently allocates resources on all cells, and cells that provide service to many group members use the same resources for all members to receive the call.
+
+Oscar speaks, and all group members including the dispatcher Mick hear the audio that he has spoken within minimal delay (within a few hundred milliseconds). The audio is a one way transmission, i.e. receiving parties hear Oscar's spoken audio, but no-one hears audio from any of the receiving parties.
+
+All receiving parties including the dispatcher, Mick, can see Oscar's identity as the talking party on their UEs up to the time Oscar disconnects his call to the group.
+
+Differences in audio delay are not noticeable to officers standing near each other who are receiving service from the same cell as each other; i.e. they do not hear an "echo" effect from different UEs.
+
+Any UEs which are permitted to be members of the group, but which have not joined the group do not take part in the call.
+
+#### A.1.3.4 Service Flow 4 – Call interruption
+
+While Oscar is still speaking, Ned attempts to speak (i.e. he makes a PTT request).
+
+- If the system is configured such that the transmitting party cannot be interrupted, then Ned's PTT request is rejected. He receives an indication on his UE of the rejection. Oscar continues to speak and to be heard by all receiving parties in the group.
+- If the system is configured (such that interruption is possible, or is possible based on relative priorities of Oscar and Ned, and Ned has a higher priority rating), then the system sends a message to Oscar's UE withdrawing transmit permission. The UE indicates this to Oscar, and Oscar's UE no longer transmits. The system grants transmit permission to Ned's UE, which indicates that his request is successful. Ned now speaks, and his speech is heard by the group from this point onwards. All receiving parties now see Ned's identity as the talking party on their UEs.
+
+If priorities are used, at least four priorities are needed for normal user, supervisory user, dispatcher and supervisory dispatcher.
+
+#### A.1.3.5 Service Flow 5 – Talking party changeover
+
+When the current talking party (Oscar in 4.1, Ned in 4.2) has finished speaking, an indication is sent to the UEs of all group members.
+
+Peter then initiates speech transmission to the group. The group call goes on with Peter as the talking party.
+
+#### A.1.3.6 Service Flow 6 – Late Entry and mobility
+
+Roger has not previously selected the "traffic" group, and therefore has not been listening to audio. Whilst Peter is transmitting, Roger selects the "traffic" group on his UE. The UE signals to the system that it wants to join the group, and system grants the request. The UE joins the call, and Roger hears the audio being spoken by Peter, and Roger's UE displays Peter's identity as the talking party.
+
+The system allocates resources efficiently to include Roger. If Roger is receiving service from a radio site which is also serving several other users, Roger's UE uses the same resources that are being used for the other users.
+
+Ned is receiving the call on one cell, but moves to another cell whilst Peter is transmitting. The system hands over Ned's call to the new cell. If the new cell is serving several other users, Ned's UE uses the same resources that are being used for the other users. Ned experiences minimal interruption to his received audio due to the cell change.
+
+Whilst transmitting, Peter moves to another cell. The system hands over Peter's call to the new cell and allows him to continue transmission with minimal interruption.
+
+#### A.1.3.7 Service Flow 7 – Call release
+
+Peter finishes transmitting and ends the call on his UE. The UE signals to the system that the transmission is ceased, and the system in turn signals this to all receiving parties in the call. Peter's audio is no longer heard, and his identity is no longer displayed as the talking party.
+
+After a short period of time, the system releases resources which had been assigned to the call.
+
+The Group Call is cleared by the system after a short time after the last speaker and no one has spoken in the meantime (and the system may be configured with a timer to determine this time).
+
+#### A.1.3.8 Service Flow 8 – Blocking of resources
+
+Oscar initiates a new call. Traffic group members are spread across several cells.
+
+Calling Party cell busy:
+
+- Oscar's cell does not have enough resources to support the new call.
+- Oscar receives an indication that the call cannot be established, and will be queued.
+- The system places the call in a queue until enough resources are available at least on Oscar's cell.
+- Once enough resources are available, the call is started, and Oscar receives an indication that he can start to transmit.
+
+Receiving Party cell busy:
+
+- Oscar's cell has enough resources to support the call, but on one or more cells where group members are receiving service, the system does not have enough resources to support the new call. Two alternatives may follow:
+ - Queued configuration: If the system is configured to queue calls, the call is queued until the system has enough resources to support all the users of the group. Oscar receives an indication that the call has been queued. Once enough resources become available, Oscar receives an indication that he can start to transmit.
+ - Immediate call start configuration: If the system is configured to start providing that the talking party's cell has sufficient resources, the call will be started and audio received by receiving parties in the call on cells where the system has enough resources to receive the call. If cells that did not have enough resources at the start of the call subsequently have the enough resources available e.g. due to a reduction in load, users on those cells are connected into the call as soon as is possible.
+
+### A.1.4 Post-conditions
+
+Whilst idle, the group is not consuming system resources.
+
+## --- A.2 "See what I see" use case
+
+### A.2.1 Description
+
+This use case illustrates a situation where a policeman shares multimedia content (video and/or picture) with all the members of a pre-defined group (including the dispatcher and group members in the field). According to the operational rules of the users, the sharing of multimedia content within a group might be authorized by a dispatcher or not. This use case describes the case where the sharing is authorized by the dispatcher.
+
+### A.2.2 Actors
+
+A group of police officers is affected to a mission of protecting a touristic and shopping area from pickpockets and delinquency acts.
+
+Officer Graham is the dispatcher in the control room.
+
+Officer Smith and Johnson are two members of the team on the field.
+
+Officer Smith is assigned to the surveillance of the main square of the touristic and shopping area. Officer Johnson is another member of the group assigned to the surveillance of a set of streets adjacent to the main square of the area.
+
+### A.2.3 Pre-conditions
+
+A group "Area Protection Team" is created to provide multimedia communications between the officers in the field and the incident management officer in the control room.
+
+All officers (including Officers Graham, Smith and Johnson) have their equipment configured to the "Area Protection Team" group.
+
+Officer Smith is equipped with a wearable camera connected to his UE. Officer Smith's terminal is also capable of multimedia communications (video, voice group calls, text and data). All members of the group in the field have the same equipment set-up.
+
+Default communication mode is Push to Talk (PTT) voice [refer to A.1 "Speech Group Call Use Case and requirement proposal"].
+
+### A.2.4 Service flows
+
+1- Officer Smith is supervising the main square of the touristic and shopping area. He is in voice group call communications with all members of the team on the "Area Protection Team" group.
+
+2- Suddenly, a pick-pocket steals a camera from a tourist in the vicinity of the Officer Smith. Officer Smith informs the team (including the dispatcher) using PTT voice communication that an incident is occurring in the main square.
+
+3- Officer Smith identifies the suspect in the crowd. He activates the transmission of his wearable live video camera. A live video communication is created between Officer Smith's UE and the control room. Officer Graham can also see the suspect on the live video. Optionally, Officer Smith receives an indication that Officer Graham is actually receiving the live video flow.
+
+3bis- Optionally, Officer Graham remotely triggers a modification of the quality of the live video to a higher quality.
+
+4 – Officer Graham dispatches the video to the other members of the team so that all of them can identify how the suspect looks like (note, suspect identification can be augmented by means of voice description using the PTT communications on the "Area Protection Team" and/or by highlighting and tracking the image of the suspect on the live video). A video group communication is then created from the network to all team members. All team members can now see what Officer Smith is seeing and can also identify the suspect in the crowd.
+
+5 – From the live video that Officer Johnson receives on his terminals, he realises that the suspect is running into his direction. He gets ready to arrest the suspect.
+
+6 – Officer Johnson arrests the suspect.
+
+### A.2.5 Post-condition
+
+After the suspect has been arrested, Officer Graham suspends the sharing of the video with all group members.
+
+Officer Smith stops transmitting live video images.
+
+Communications between all members of the team reverts to nominal PTT voice communication.
+
+## A.3 Harmonized multi-agency use case
+
+### A.3.1 Description
+
+This use case illustrates a situation where a GCSE group of personnel from one local agency (e.g. fire fighters) will need to be joined with other GCSE groups of personnel from other agencies representing the same locality (e.g. police, ambulance), or with other GCSE groups from national, international or adjacent localities (e.g. police from an adjacent force, national authorities, or authorities from an adjacent country). In all cases the various groups which form the composite group must be able to join/leave the composite group and be identified as members of it. The individual personnel must also be able to fully participate in multimedia sessions within the composite group (i.e. take the floor, receive broadcast communications, etc.).
+
+### A.3.2 Actors
+
+A group of local fire fighters, called to an explosion and gas leak from a chemical facility close to a national border.
+
+The local fire service dispatcher.
+
+A group of local ambulance personnel, called to attend to casualties at the site.
+
+A group of local police officers, called to evacuate residents downwind of the leak in the same country.
+
+A group of police officers in the adjacent country, called to prepare for possible evacuation of residents downwind of the leak in their territory.
+
+### A.3.3 Pre-conditions
+
+The local fire fighters are members of GCSE Group A.
+
+The local ambulance personnel are members of GCSE Group B.
+
+The local police officers are members of GCSE Group C.
+
+The group of police officers in the adjacent country are members of GCSE Group Z.
+
+The GCSE applications on the UEs in all four groups are compatible, and are able to interwork with one another and with any of the four individual GCSE servers which may eventually control them.
+
+### A.3.4 Service flows
+
+1- The local fire fighters are called to the scene and use GCSE Group A. They notice casualties. The local ambulance personnel attend to the casualties and use GCSE Group B.
+
+2- A second chemical storage tank is seen to be in imminent danger of rupture so the Fire Service Dispatcher adds GCSE Group B to Group A to form a composite group, in order to keep Ambulance personnel apprised of the situation. Members of both groups are able to use the composite group to communicate amongst each other using all the common capabilities of the GCSE clients resident on their UEs.
+
+3- The local police officers are called to the surrounding area in order to evacuate nearby residents and prevent others from entering. They use GCSE Group C. The Fire Service Dispatcher adds GCSE Group C to the composite group in order to keep them apprised. Members of all three groups are able to use the composite group to communicate amongst each other using all the common capabilities of the GCSE clients resident on their UEs.
+
+4- The prevailing wind carries the gas cloud from the initial leak towards the national border so the Police Authority in the adjacent country mobilises their local force to prepare residents for evacuation. They use GCSE Group Z.
+
+5- The Fire Service Dispatcher adds GCSE Group Z to the composite group to keep the police force in the adjacent country apprised. Members of all four groups are able to use the composite group to communicate amongst each other using all the common capabilities of the GCSE clients resident on their UEs.
+
+6- The second chemical storage tank is successfully damped down by the local fire service, made safe, and further danger is averted. The initial gas cloud dissipates to a safe level.
+
+7- The local fire fighters inform the Fire Service Dispatcher that all is safe. The Fire Service Dispatcher is able to inform all members of the composite group that the incident is over.
+
+### A.3.5 Post-condition
+
+Having informed the composite group members that all is safe the Fire Service Dispatcher dissolves the composite group.
+
+Communications between members of the four individual GCSE groups continue within the separate groups A, B, C, and Z.
+
+# Annex B (informative): Group communication concept(s)
+
+From the 3GPP network perspective the concept of a group communication appears to be a foreign concept. The concept of group communication has been the underpinnings of public safety communications currently and in the past, not point to point communications. A group communication is the ability for a set of devices to be considered as a whole. In these public safety systems the method for identifying a group communication has evolved from a particular radio frequency to an abstraction (i.e., a logical group identifier). The logical Venn diagram shown in figure 1 shows the concept of a group communication considering three characteristics: a member of a group (A), the device is reachable (R), and the device wants to participate (P).
+
+
+
+Let x represent a device.
+ Let A represent a set of devices.
+ Let R represent the set of devices that are reachable.
+ Let P represent the set of devices that want to participate.
+
+Venn diagram illustrating group communication characteristics. A large rectangle labeled 'All devices' contains three overlapping circles labeled A, R, and P. Circle A is at the top, R is at the bottom left, and P is at the bottom right. The regions are labeled as follows: x1 is outside all circles; x5 is inside A only; x3 is inside R only; x2 is inside P only; x7 is the intersection of A and R only; x6 is the intersection of A and P only; x4 is the intersection of R and P only; x8 is the intersection of all three circles A, R, and P.
+
+**Figure B.1: Group characteristics**
+
+The truth table shown in Table B.1 provides the expected actions that the 3GPP network must provide to the device based on these three characteristics.
+
+**Table B.1: Expected actions**
+
+| representative device | member of group | reachable | wants to participate | actions |
+|-----------------------|-----------------|-----------|----------------------|---------------------------------------------------------------|
+| x8 | T | T | T | receives notice, receives call, participates in communication |
+| x7 | T | T | F | receives notice, receives call, does not participate |
+
+| | | | | |
+|----|---|---|---|----------------------------------------------------------------------|
+| x6 | T | F | T | does not receive notice, does not receive call, does not participate |
+| x5 | T | F | F | does not receive notice, does not receive call, does not participate |
+| x4 | F | T | T | does not receive notice, does not receive call, does not participate |
+| x3 | F | T | F | does not receive notice, does not receive call, does not participate |
+| x2 | F | F | T | does not receive notice, does not receive call, does not participate |
+| x1 | F | F | F | does not receive notice, does not receive call, does not participate |
+
+Using these characteristics the 3GPP network needs to know the devices that make up the group communication so that it can make the appropriate inquiries and make the correct decisions to determine reachability, membership, and participation. The condition (or indication) to participate may be at the device level or may be a decision made by the user of the device. The 3GPP network is the only entity that knows whether a device is reachable. The application layer can indirectly obtain the reachability information from the 3GPP network (e.g., by using it to deliver an application "ping" message). As one can see from Table 1 the actual devices that will compose the group communication may not be all of the devices that are listed as members of a group.
+
+# --- Annex C (informative): Description of usage of GCSE for public safety
+
+Based on real life scenarios, at least 36 simultaneous voice group communications involving a total of at least 2000 participating users in an area , with up to 500 users being able to participate in the same group could be expected.
+
+# Annex D (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|-----------|--------|------|-----|--------|-----|---------------------------------------------------|--------|--------|----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | WI |
+| SP-60 | SP-130292 | - | 22.468 | - | - | | - | One-step-approved by SA#60 | 1.0.1 | 12.0.0 | GCSE_LTE |
+| SP-66 | SP-140753 | S1-144547 | 22.468 | 13 | | Rel-13 | C | Removing floor control requirements from GCSE_LTE | 12.0.0 | 13.0.0 | GCSE_LTE |
+| SP-75 | - | - | - | - | | Rel-14 | - | - | 13.0.0 | 14.0.0 | - |
+| SP-80 | SP-180306 | S1-181381 | 22.468 | 0014 | 1 | Rel-15 | F | Removal of LTE specific terminology from 22.468 | 14.0.0 | 15.0.0 | MCOVer |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2019-12 | SA#86 | - | - | - | - | Comment: V.16.0.0 identical to v.15.0.0. Created because of Rel-17 CR 0016r3 (in SP-191014) on a Rel-15 spec. | 16.0.0 |
+| 2019-12 | SA#86 | SP-191014 | 0016 | 3 | B | Introduction of NCIS Service Requirements | 17.0.0 |
+| 2020-07 | - | - | - | - | - | Wrong file in 3GU ("22468-h00.zip" actually contained v.16.0.0 instead of 17.0.0) | 17.0.1 |
+| 2024-03 | SA#103 | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22519/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-18/22_series/22519/54fabc351eda5228d2fa28cd9ba07971_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7d2e98bbf16095c353856fef6a7fe74eeaf71bc
--- /dev/null
+++ b/marked/Rel-18/22_series/22519/54fabc351eda5228d2fa28cd9ba07971_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:362b39efacda20e6a158c0e2b3e0d46aaccfdb4f35d0ad3ca4b24d625b6dd535
+size 31777
diff --git a/marked/Rel-18/22_series/22519/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22519/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c5063fd81b0ff8674f089e8f942b14bfb7ccbce
--- /dev/null
+++ b/marked/Rel-18/22_series/22519/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e040f76666a123ef6779c35a3c8eb00134d1bc50ded13ec948caeb364e3e9dd
+size 9609
diff --git a/marked/Rel-18/22_series/22519/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22519/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0501237a6643e88d1b653ffc76110f4a81ed475
--- /dev/null
+++ b/marked/Rel-18/22_series/22519/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8afa50db6ea795bf861adc919b103effc1599e2d57cd0576b61853bb7a31e2ac
+size 7066
diff --git a/marked/Rel-18/22_series/22519/a92b1fdf37a74b707e9f03087c8f1377_img.jpg b/marked/Rel-18/22_series/22519/a92b1fdf37a74b707e9f03087c8f1377_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..387753e7414ff37572e229f89bc6fe6bdd87d548
--- /dev/null
+++ b/marked/Rel-18/22_series/22519/a92b1fdf37a74b707e9f03087c8f1377_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb12f4551602cef018a8567b1a059644b65f1b1e76267b4df49df4deb5600b33
+size 20731
diff --git a/marked/Rel-18/22_series/22519/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/22_series/22519/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..278984b924117866848acfabfbca82d7fa4c0b71
--- /dev/null
+++ b/marked/Rel-18/22_series/22519/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10b792635c3ee2aa12c439ba4206e6d3bd000630a54e1f2a53d9e56d57cfa738
+size 20382
diff --git a/marked/Rel-18/22_series/22519/raw.md b/marked/Rel-18/22_series/22519/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a0372748c863891485bc2b08d610cc5966e3b5c8
--- /dev/null
+++ b/marked/Rel-18/22_series/22519/raw.md
@@ -0,0 +1,687 @@
+
+
+# 3GPP TS 22.519 V18.0.1 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Business Communication Requirements (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+Business, Communication, Trunking
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Capabilities for the support of IP multimedia services ..... | 8 |
+| 4.1 General ..... | 8 |
+| 4.1.1 Types of traffic ..... | 8 |
+| 4.1.2 Business communication capabilities..... | 9 |
+| 4.1.3 Business models ..... | 9 |
+| 4.1.4 Number, naming and addressing ..... | 11 |
+| 4.1.5 Identification of session originator and terminator..... | 11 |
+| 4.1.6 Charging and accounting requirements..... | 11 |
+| 4.1.7 Regulatory requirements ..... | 12 |
+| 4.1.7.1 Lawful intercept..... | 12 |
+| 4.1.7.2 Emergency service..... | 12 |
+| 4.1.7.3 Identifying malicious communications..... | 12 |
+| 4.1.7.4 Anonymous communications rejection ..... | 12 |
+| 4.1.8 Mobility ..... | 13 |
+| 4.1.8.1 Roaming..... | 13 |
+| 4.1.9 Routing requirements ..... | 13 |
+| 4.1.9.1 Routing to a NGCN user..... | 13 |
+| 4.1.9.2 number range based routing..... | 13 |
+| 4.1.10 Communication admission control..... | 13 |
+| 4.1.11 Geographical location..... | 14 |
+| 4.2 NGN/NGCN interconnection requirements ..... | 14 |
+| 4.2.1 NGCN site identifier..... | 14 |
+| 4.2.2 Corporate network user identifier..... | 14 |
+| 4.2.3 Authentication and security requirements..... | 14 |
+| 4.3 Specific requirements for hosted enterprise services ..... | 14 |
+| 4.3.1 Security requirements for hosted enterprise services ..... | 14 |
+| 4.3.2 Capabilities provided to a HES user..... | 15 |
+| 4.3.3 Capabilities provided to the enterprise..... | 15 |
+| 4.3.3.1 Break-in ..... | 15 |
+| 4.3.3.2 Break-out ..... | 15 |
+| 4.4 Specific requirements for business trunking application ..... | 15 |
+| 4.4.1 Routeing capabilities ..... | 15 |
+| 4.4.1.1 Overview..... | 15 |
+| 4.4.1.2 Break-in ..... | 15 |
+| 4.4.1.3 Break-out ..... | 15 |
+| 4.4.1.4 Bulk rerouting..... | 16 |
+| 4.4.2 Communication barring..... | 16 |
+| 5 PSTN/ISDN emulation service ..... | 16 |
+| 6 Codecs services..... | 16 |
+| 7 Network attachment requirements ..... | 16 |
+| 7.1 General ..... | 16 |
+| 7.2 Specific requirements for virtual leased line..... | 16 |
+| 7.2.1 Security requirements for virtual leased line..... | 16 |
+| 8 CPE configuration..... | 17 |
+
+9 Control of processing overload..... 17
+10 IP addressing..... 17
+11 NGN interconnection..... 17
+12 Transport stratum..... 17
+12.1 NGN/NGCN interconnection requirements..... 17
+12.1.1 Redundancy support..... 17
+12.2 Specific requirements for virtual leased line..... 17
+**Annex A (informative): Change history..... 19**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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 present document is structured in a similar manner to ETSI TS 181 005 [2] and the main clause numbering from this point in the document onwards therefore follows that document, with the scope of those clauses also following that of ETSI TS 181 005 [2].
+
+As well as the interconnection of NGCN equipment to the NGN, the NGN can be used to host various business communication capabilities on behalf of an enterprise. These are:
+
+- a) virtual leased line, where NGCN sites are interconnected through the NGN;
+- b) business trunking application, where the NGN hosts transit capabilities between NGCNs, break-in capabilities from NGN to NGCN and break-out capabilities from NGCN to NGN; and
+- c) hosted enterprise services, where an NGN hosts originating and/or terminating business communication capabilities for business communication users that are directly attached to an NGN.
+
+These hosted capabilities may be hosted using the different capabilities described in different clauses in ETSI TS 181 005 [2] and therefore where appropriate the various clauses of the present document are broken up to further describe interconnection requirements, and these various hosted capabilities, as follows:
+
+- x.1 General;
+- x.2 NGN/NGCN interconnection requirements;
+- x.3 Specific requirements for hosted enterprise services;
+- x.4 Specific requirements for business trunking application; and
+- x.5 Specific requirements for virtual leased line.
+
+This structure has been followed in 3GPP TS 22.519, even though 3GPP TS 22.228 [6] (the equivalent specification) is structured in a different manner.
+
+# 1 Scope
+
+The present document specifies network requirements:
+
+- to support connection and interoperation of business communication capabilities (either hosted in NGCN or NGN) to the NGN; and
+- to support connection and interoperation of business communication capabilities to other business communication capabilities (either hosted in NGCN or NGN); and
+- to support connection and interoperation of business communication capabilities to other business communication capabilities located in or connected to the ISDN and PSTN; and
+- to support PABX functionality (hosted enterprise services) in an NGN.
+
+NOTE 1: Network requirements to support connection of NGCN directly connected to an NGN are specified.
+
+NOTE 2: Attachment of legacy PBX functionality to the NGN is not specified in the present document. It is assumed that existing legacy service requirements apply in this case.
+
+The present document also specifies network requirements for communication between NGCN capabilities (including user equipment) to other NGCN capabilities of the same enterprise through the NGN (e.g. geographically separated).
+
+The present document does not specify NGCN services, nor does it specify network based application services provided to a user of an NGCN.
+
+# 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] Recommendation ITU-T E.164: "The international public telecommunication numbering plan".
+- [2] ETSI TS 181 005 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements".
+- [3] 3GPP TS 33.203: "3G security; Access security for IP-based services".
+- [4] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
+- [5] ISO/IEC 11571: "Information technology - Telecommunications and information exchange between systems - Private Integrated Services Networks - Addressing".
+- [6] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1".
+- [7] ETSI TR 102 478 (V1.1.1): "Corporate telecommunication Networks (CN); Enterprise communication involving Next Generation carrier Networks (NGN)".
+- [8] 3GPP TS 22.115: "Service aspects; Charging and billing".
+- [9] 3GPP TS 33.106: "3G security; Lawful interception requirements".
+
+[10] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [10] 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 [10].
+
+**business communication:** any communication that is either:
+
+- originated in an NGCN; or
+- terminated in an NGCN; or
+- originated in the NGN on behalf of an enterprise; or
+- terminated in the NGN on behalf of an enterprise;
+
+and which is subject to special arrangements between the NGN operator and the enterprise
+
+**business communication capabilities:** any capability whether hosted in an NGCN or an NGN that enables and/or enriches Business Communication
+
+NOTE: Business Trunking, Hosted Enterprise Services and Virtual Leased Line are examples of business communication capabilities hosted in NGN.
+
+**Business Trunking (BT):** connection of an NGCN to an NGN
+
+**business trunking application:** NGN application that either provides transit capabilities between NGCNs, or, break-in capabilities from NGN to NGCN and/or break-out capabilities from NGCN to NGN
+
+NOTE: A business trunking application may also provide additional services beyond basic breakin, breakout and transit capabilities to the NGCN.
+
+**corporate network user identifier:** identifies a corporate network user on communications entering, leaving or transiting the NGN, either representing an originating corporate network user or as a globally routable target identity
+
+**Corporate telecommunication Network (CN):** sets of enterprise premises equipment, owned by or managed on behalf of an enterprise that are located at geographically dispersed locations and are interconnected to provide telecommunication services to a defined group of users belonging to that enterprise
+
+**enterprise:** unit of economic organization or activity, especially a business organization
+
+**Hosted Enterprise Services (HES):** NGN application whereby the NGN hosts all originating and/or terminating business communication capabilities for enterprise users that are directly attached to NGN and have an IMS service subscription for this application in the NGN
+
+**Next Generation CN (NGCN):** self-contained corporate network designed to take advantage of emerging IP-based communications solutions and that can have its own applications and service provisioning
+
+NOTE 1: For the purpose of the present document it is a corporate network that provides an IP-based interface to an NGN.
+
+NOTE 2: TR 102 478 [7] uses NGCN to collectively refer to IP-PBXs.
+
+**NGCN site:** separate part of an NGCN
+
+**NOTE:** An NGCN site might represent a part of an NGCN bound to a specific geographic location. When an NGCN site serves more than one geographic location then all locations served by that NGCN site would have access to an NGN concerned via the NGCN site's connectivity arrangement with that NGN. Communication between different NGCN sites belonging to the same NGCN can but need not pass through their respective NGN(s). For example, such communications might be routed by the NGN(s) only during periods of high traffic or equipment outage within the NGCN. An NGCN site can have access to its NGN either directly or via some other NGN that provides a transit capability. An NGCN can have NGCN Sites in different countries.
+
+**NGCN identifier:** identifier by which an NGCN is known to an NGN with which it has a connectivity arrangement
+
+**public network traffic:** traffic sent to or received from an NGN for processing according to the normal NGN rules
+
+**private network traffic:** traffic sent to or received from an NGN for processing according to an agreed set of rules specific to an enterprise or a community of closely related enterprises
+
+**Private Numbering Plan (PNP):** numbering plan explicitly relating to a particular private numbering domain, defined by the PISN Administrator of that domain
+
+**NOTE 1:** See ISO/IEC 11571 [5].
+
+**NOTE 2:** Terminology used in this definition and in relation to this term used in the text is as defined in ISO/IEC 11571 [5]. For the purposes of the present document a PISN and a NGCN can be regarded as equivalent.
+
+**PNP number:** number belonging to a PNP
+
+**NOTE:** See ISO/IEC 11571 [5].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|------|--------------------------------------|
+| BT | Business Trunking |
+| CAC | Communication Admission Control |
+| CN | Corporate telecommunication Network |
+| HES | Hosted Enterprise Services |
+| IMS | IP Multimedia core network Subsystem |
+| IP | Internet Protocol |
+| NGCN | Next Generation Corporate Network |
+| NGN | Next Generation Network |
+| PBX | Private Branch Exchange |
+| PNP | Private Numbering Plan |
+| PSAP | Public Safety Answering Point |
+| SLA | Service-Level Agreement |
+| TIP | Termination Identity Interface |
+| UE | User Equipment |
+| UNI | User to Network Interface |
+
+# --- 4 Capabilities for the support of IP multimedia services
+
+## 4.1 General
+
+### 4.1.1 Types of traffic
+
+The traffic generated or received on behalf of an NGCN can be either:
+
+- 1) traffic sent to the NGN for processing according to normal rules of the NGN. This type of traffic is known as public network traffic;
+
+- 2) traffic sent to the NGN for processing according to an agreed set of rules specific to an enterprise. This type of traffic is known as private network traffic. Private network traffic is normally within a single enterprise, but private network traffic can also exist between two different enterprises if not precluded for regulatory reasons.
+
+NOTE: An enterprise network may separately distinguish private network calls that originate in the NGN from private network calls that originate in the enterprise; this does not form part of the present document.
+
+The NGN shall distinguish public network traffic from private network traffic. The NGN shall distinguish private network traffic belonging to one enterprise from that belonging to another enterprise.
+
+Private network traffic may require different handling in the NGN compared to public network traffic, see for example clause 4.1.7 on regulatory requirements.
+
+Except between closely-related enterprises where regulations permit, the NGN shall treat traffic between enterprises as public network traffic. In such cases, as part of the capabilities provided to the enterprise, the NGN can provide break-out and/or break-in capabilities on behalf of each enterprise.
+
+For private network traffic the NGN shall be transparent to any extensions of the chosen signalling protocol, except where there is a specific need for NGN intervention required to deliver the service requested by the enterprise customer.
+
+### 4.1.2 Business communication capabilities
+
+The NGN can provide the following capabilities to an enterprise:
+
+- a) virtual leased line, where NGCN sites are interconnected through the NGN. No additional capabilities are provided by the NGN;
+- b) business trunking application, where the NGN hosts transit capabilities between NGCNs, break-in capabilities from NGN to NGCN and break-out capabilities from NGCN to NGN. A business trunking application may also host additional capabilities beyond basic break-in, break-out and transit capabilities to the NGCN. Typically there is no corporate network terminal equipment connected directly to an NGN. The capabilities provided are defined in clause 4.4;
+- c) hosted enterprise services, where an NGN hosts originating and/or terminating business communication capabilities for business communication users that are directly attached to an NGN and have an IMS service subscription for this application in this NGN. This is known commonly as IP-Centrex. The capabilities provided are defined in clause 4.3.
+
+NOTE: NGCNs will not necessarily use IMS in their support of session-based capabilities.
+
+### 4.1.3 Business models
+
+Additionally to the business domain relationships as specified in 3GPP TS 22.228 [6] the NGN shall support the following business domain relationships:
+
+- a) NGCN to IMS relationship: NGCN is attached to an Access network that is connected to the NGN IMS with which the NGCN has a service agreement as shown in figure 4.1, the relationship is with the home IMS.
+
+
+
+Diagram illustrating the NGCN to IMS relationship. A green oval labeled 'NGCN' is connected by a line to another green oval labeled 'Access network'. The 'Access network' is connected by a line to a third green oval labeled 'Home IMS'. The 'Home IMS' is located within a larger grey oval labeled 'NGN'. A curved arrow labeled 'Relationship a' points from the 'NGCN' oval to the 'Home IMS' oval, indicating the service agreement relationship.
+
+Figure 4.1
+
+- b) NGCN to Access network relationship: NGCN is connected to an Access Network as shown in figure 4.2. The relationships given in 3GPP TS 22.228 [6] would normally be sufficient to enable connectivity with the NGN, providing there is a relationship between the NGCN and the IMS. Relationship b may be required in some cases.
+
+
+
+```
+
+graph LR
+ NGCN((NGCN)) -- "Relationship b" --> AN((Access network))
+ AN --- HI((Home IMS))
+ subgraph NGN
+ HI
+ E(( ))
+ end
+
+```
+
+Figure 4.2: Diagram showing the relationship between an NGCN, an Access network, and an NGN. The NGCN is connected to the Access network, which is connected to the Home IMS. The Home IMS is part of the NGN. A curved arrow labeled 'Relationship b' points from the NGCN to the Access network.
+
+Figure 4.2
+
+NOTE: The Access Networks to which the various NGCN sites are connected may belong to different operators.
+
+The following business model relationship is shown as it plays a role in some scenarios. The present document assumes the business relationships described in item a) and b) and those as assumed from 3GPP TS 22.228 [6] in order to create communications in support of this relationship:
+
+- c) NGCN to NGCN relationship: The relationship between two NGCNs is shown in figure 4.3.
+
+
+
+```
+
+graph LR
+ NGCN1((NGCN 1)) --- AN1((Access network))
+ AN1 --- IMS1((IMS))
+ subgraph NGN1
+ IMS1
+ end
+ NGCN2((NGCN 2)) --- AN2((Access network))
+ AN2 --- IMS2((IMS))
+ subgraph NGN2
+ IMS2
+ end
+ NGCN1 -- "Relationship c" --> NGCN2
+
+```
+
+Figure 4.3: Diagram showing the relationship between two NGCNs (NGCN 1 and NGCN 2) via their respective IMS and Access networks. NGCN 1 is connected to an Access network, which is connected to an IMS. The IMS is part of an NGN. NGCN 2 is connected to an Access network, which is connected to an IMS. The IMS is part of an NGN. A curved arrow labeled 'Relationship c' points from NGCN 1 to NGCN 2.
+
+Figure 4.3
+
+NOTE: Both NGCN 1 and NGCN 2 have their own relationship with an NGN. NGCN 1 and NGCN 2 may also represent parts of the same NGCN. Additionally NGCN 1 and NGCN 2 may have relationships with different NGNs, which may belong to the same or different operators.
+
+Where the figures and text identify "IMS" forming the business relationship; this can apply also to the usage of other subsystems in the NGN architecture.
+
+Additionally to the interconnect models as specified in 3GPP TS 22.228 [6], the NGN shall support:
+
+- an interconnect model where bi-lateral Service Level Agreements are established between an NGCN and an NGN.
+
+Business trunking applications are normally provided by the home IMS and relationship a) is used to establish these capabilities, which in turn uses relationships given in 3GPP TS 22.228 [6] for the access network related relationship. Hosted enterprise services are normally provided by the home IMS, the existing business relationships as specified in 3GPP TS 22.228 [6] being sufficient to establish such capabilities.
+
+Virtual leased line services can be supported directly using relationship b, or it can be supported using relationship a) with the IMS which in turn uses relationships given in 3GPP TS 22.228 [6] for the access network related relationship.
+
+Roaming of NGCN users is supported by either:
+
+- a combination of business model relationship a) with relationships in 3GPP TS 22.228 [6] relationship with the visited IMS. No relationship is required between the home NGCN and the visited NGN or access network.
+
+Roaming of NGN users to NGCN is supported by:
+
+- a combination of business model relationship a) with relationships in 3GPP TS 22.228 [6] relationship with the home IMS. No relationship is required between the home IMS and the visited NGCN.
+
+The service offering to an NGCN may be restricted by the capabilities of the access network, the business agreement between the access network operator and the NGN operator and the business agreement between the NGCN and NGN operators.
+
+### 4.1.4 Number, naming and addressing
+
+3GPP TS 22.228 [6] provides requirements for the support of numbering to end users of the NGN which apply equally for public network traffic generated by, or received by a business communication capability.
+
+For private network traffic generated by, or received by, a business communication capability, the requirements of 3GPP TS 22.228 [6] apply along with the following additional requirements:
+
+- 1) the NGN shall support tel-URIs that encode a PNP number, the PNP used by the enterprise shall be uniquely identified in this tel URI.
+
+NOTE: Ensuring the uniqueness of the PNP identifier can be achieved by using a domain name associated with the enterprise, that the PNP belongs to.
+
+For public and private network traffic generated by, or received by, a business communication capability, the requirements of 3GPP TS 22.228 [6] apply along with the following additional requirements:
+
+- 1) the NGN shall support usage of SIP URIs with a domain belonging to an enterprise, and any usage of SIP URIs with a domain hosted by the enterprise; and
+- 2) the NGN shall support usage of SIP URIs where more than one domain belong to the same enterprise, and any usage of SIP URIs where more than one domain is hosted by the same enterprise;
+- 3) the NGN shall support usage of SIP URIs where a domain belonging to an enterprise, is partly hosted in NGCN and partly hosted in NGN.
+
+URIs prefixed with "IM" and "Pres" are supported as specified in 3GPP TS 22.228 [6].
+
+### 4.1.5 Identification of session originator and terminator
+
+As defined in 3GPP TS 33.203 [3] a trust domain is used for the management of identities within enterprise network interconnection.
+
+For identification, the requirements described in 3GPP TS 22.228 [6] are supported to NGN users and users of business communications capabilities as follows:
+
+- 1) when the business communication capability is outside the trust domain, the NGN asserts an identity that the NGN associates (by means of subscription data) with the enterprise, in addition to delivering the identity of the enterprise user as provided by the NGCN and which is not asserted by the NGN;
+- 2) when the business communication capability is inside the trust domain, the NGN presents the identity of the enterprise user as the asserted identity. The NGN shall accept the asserted identity received from the NGCN; and
+- 3) in order to support interworking with the PSTN/ISDN, and for other purposes, an alias identity of the enterprise user can be needed. An alias set for an enterprise user consists of:
+ - a) a SIP URI not in the form of a public telecommunication number; and
+ - b) one of either:
+ - a public telecommunications number that reaches the same enterprise user; or
+ - a private network number that reaches the same enterprise user.
+
+For enterprise users, it is the responsibility of the enterprise to provide the alias set. The NGN shall be able to receive alias sets from the NGCN.
+
+NGNs shall be able to deliver alias sets (of any user) to the NGCN.
+
+The above requirements apply to the identities of both session originator and session terminator.
+
+### 4.1.6 Charging and accounting requirements
+
+An enterprise can account for traffic in its business communication capabilities whether hosted in an NGCN or NGN.
+
+For public network traffic, the requirements of 3GPP TS 22.115 [8] apply.
+
+For public network traffic, the enterprise and the NGN operator shall be able to identify each other across any interconnection interface, including intra-NGN interfaces to hosted business communication capabilities. For private network traffic, any involved enterprise shall be able to identify each other across any interconnection interface between its business communication capabilities.
+
+Any business communication capability hosted in an NGN shall be able to account for private network traffic to the enterprise in the same manner as exists for an NGN operator to account for their own traffic.
+
+Additionally, for private network traffic, the enterprise and the NGN operator shall be able to identify each other across any interconnection interface.
+
+### 4.1.7 Regulatory requirements
+
+#### 4.1.7.1 Lawful intercept
+
+Lawful Intercept should be handled according to TS 33.106 [9].
+
+#### 4.1.7.2 Emergency service
+
+Both public network traffic and private network traffic may carry emergency calls.
+
+An emergency call identified as public network traffic shall be handled in accordance with the emergency call requirements of the NGN, i.e. in accordance with the requirements of 3GPP TS 22.228 [6].
+
+In case of a public network traffic emergency call, an NGN shall forward geographical location information received from an NGCN and possibly use it for routing to an appropriate PSAP. This can be subject to both privacy and regulatory requirements.
+
+Routeing of calls identified as emergency calls in private network traffic is outside the scope of NGN documents. The NGN shall not handle such calls as specified in 3GPP TS 22.228 [6]. This also applies to a hosted NGCN capability.
+
+NOTE 1: Many enterprises will require the call to be routed to a private PSAP.
+
+NOTE 2: Private numbering plans or dialling plans used within an enterprise can reuse national emergency numbers (e.g. 112 in Europe) for other purposes and can use a different number to denote an emergency call.
+
+NOTE 3: Where an enterprise operates a private PSAP, it can require that calls be routed to the private PSAP (or to one of several private PSAPs) or to a public PSAP depending on circumstances. For example, for a caller physically located within a particular enterprise site, routing to the private PSAP for that site can be required, whereas for callers physically located elsewhere routing to the public PSAP could be required.
+
+#### 4.1.7.3 Identifying malicious communications
+
+A call identified as public network traffic shall be handled in accordance with the malicious call identification requirements of the NGN, i.e. in accordance with the requirements of 3GPP TS 22.228 [6].
+
+Identification of malicious calls in private network traffic is outside the scope of NGN documents. The NGN shall not handle such calls as specified in TS 181 005 [2]. This also applies to a hosted NGCN capability.
+
+NOTE: Separate regulatory requirements can apply for private network traffic, or there is the possibility of no regulatory requirements at all.
+
+#### 4.1.7.4 Anonymous communications rejection
+
+A call identified as public network traffic shall be handled in accordance with the anonymous call rejection requirements of the NGN, i.e. in accordance with the requirements of 3GPP TS 22.228 [6].
+
+Requirements for handling of anonymous calls in private network traffic are outside the scope of NGN documents. The NGN shall not handle such calls as specified in 3GPP TS 22.228 [6]. This also applies to a hosted NGCN capability.
+
+NOTE: Separate regulatory requirements can apply for private network traffic, or there is the possibility of no regulatory requirements at all.
+
+### 4.1.8 Mobility
+
+#### 4.1.8.1 Roaming
+
+The business models as expressed in 3GPP TS 22.228 [6] and clause 4.1.3 of the present document allow several roaming scenarios. Important roaming scenarios in the context of business communication are highlighted in this clause. These scenarios apply whether the NGCN functionality is external to the NGN, or hosted in the NGN.
+
+For all scenarios both terminal mobility and personal mobility should be supported as defined in 3GPP TS 22.228 [6].
+
+An NGCN user should be able to register and receive service from their NGCN while roaming to:
+
+- a) another NGCN site of the same NGCN and interconnected by the NGN; or
+- b) the NGN to which the NGCN is directly connected; or
+- c) the NGN to which the NGCN is indirectly connected via another NGN.
+
+Over and above the roaming capabilities provided in 3GPP TS 22.228 [6], an NGN user should be able to register and receive service from their NGN while roaming to:
+
+- a) an NGCN connected to the NGN; or
+- b) an NGCN indirectly connected to the NGN;
+
+subject to agreement with the NGCN.
+
+### 4.1.9 Routing requirements
+
+#### 4.1.9.1 Routing to a NGCN user
+
+The NGN shall support routing to NGCN users that do not have an IMS service subscription in the NGN, but can be reached through an NGCN site that has a business trunking arrangement with an NGN.
+
+NOTE: In this case an NGCN site has an IMS subscription, the corporate network users in a NGCN do not need their own IMS service subscription, since they are owned and managed by the NGCN. What this requirement achieves is that these corporate network users can be reached from the public part of the NGN by addressing them directly using a public address.
+
+#### 4.1.9.2 number range based routing
+
+The NGN shall support routing based on Recommendation ITU-T E.164 [1] number ranges.
+
+NOTE: To be able to route to corporate network users in an NGCN, it should be possible to route only on a specific number range that is assigned to such an NGCN.
+
+### 4.1.10 Communication admission control
+
+The NGN shall support Communication Admission Control on a per NGCN site basis. The NGN operator defines the set of rules or policies under which this should occur, and the NGCN operator should be able to configure the capability within those rules and policies. It shall be possible to set the following thresholds on a per direction basis (i.e. incoming and outgoing communications):
+
+- maximum number of simultaneous session-oriented communications;
+- maximum number of simultaneous streams per communication;
+- maximum number of immediate messages.
+
+Communications coming in excess to the allowed threshold may be accepted or rejected.
+
+NOTE: The enterprise may select values for communication admission control that correspond to the Service Level Agreement (SLA) between the enterprise and the operator. If this occurs, then communications coming in excess of the allowed threshold which are accepted may be subject to specific charging rules.
+
+### 4.1.11 Geographical location
+
+An NGN shall be able to provide to an NGCN the geographical location information of an NGCN user. This can be subject to privacy requirements.
+
+NOTE 1: An NGCN can use the geographical location information for example to provide location based services to the NGCN user.
+
+NOTE 2: The source of geographical location information may be an NGN or an NGCN UE.
+
+## 4.2 NGN/NGCN interconnection requirements
+
+### 4.2.1 NGCN site identifier
+
+NGN shall support identification of an NGCN site, for authentication and authorization purposes.
+
+NOTE 1: The NGCN site identification is needed to be able to let the NGN determine which NGCN site a communication is originating from.
+
+NOTE 2: An NGCN may have more than one NGCN site and hence more than one NGCN site identifier associated.
+
+### 4.2.2 Corporate network user identifier
+
+In addition to the Naming, Numbering and Addressing requirements expressed in 3GPP TS 22.228 [6] and in clause 4.1.4 of the present document the NGN shall provide the capability to uniquely identify NGCN users. NGCN user identities are assigned by an NGCN operator.
+
+NOTE 1: This does not exclude scenarios where one organization acting as an NGN operator also in another role administers the NGCN of an enterprise on behalf of that enterprise.
+
+NOTE 2: The above requirement ensures that for communications from an NGCN user to an NGN user the NGN user's OIP service can present the correct identity of the calling NGCN user.
+
+NOTE 3: The above requirement ensures that for communications from an NGN user to an NGCN user the NGN user's TIP service can present the correct identity of the called NGCN user.
+
+NOTE 4: The above requirement ensures that NGN users can call NGCN users that have identities within the set of identities that are available to that NGCN under the business trunking arrangement for that NGCN.
+
+### 4.2.3 Authentication and security requirements
+
+Authentication and Security with regard to connection of an NGCN to the NGN shall comply with security requirements specified in 3GPP TS 33.203 [3] and 3GPP TS 33.210 [4].
+
+## 4.3 Specific requirements for hosted enterprise services
+
+### 4.3.1 Security requirements for hosted enterprise services
+
+When HES are being provided, a UE which is directly attached to or roams into an IMS network (via UNI) shall comply to the IMS access security requirements as specified in 3GPP TS 33.203 [3].
+
+### 4.3.2 Capabilities provided to a HES user
+
+The capabilities provided by such hosting towards HES users are not specified further by the present document, except that such hosting can form an integral part of any business communication support.
+
+### 4.3.3 Capabilities provided to the enterprise
+
+#### 4.3.3.1 Break-in
+
+HES can provide break-in. Break-in is where public network traffic is accepted from the public network and delivered to the HES user.
+
+#### 4.3.3.2 Break-out
+
+HES can provide break-out. Break-out is where private network traffic is routed in the NGCN, or other business communication capability, to a point where it can enter an NGN on terms advantageous to the NGCN operator. An HES providing break-out therefore converts private network traffic to become public network traffic. The purpose of this capability is to allow a call from within the NGCN, or other business communication capability, to reach a user outside the enterprise (e.g. in the NGN). The NGN operator defines the set of rules or policies under which this should occur, and the NGCN operator should be able to configure the capability within those rules and policies. As an example, these rules and policies may be selected for tariff reasons, and the point where the capability is applied may be dependent on both geographic location and the NGN operator involved.
+
+When break-out is provided, the HES shall convert any identities provided as private network numbers to valid public telecommunication numbers.
+
+## 4.4 Specific requirements for business trunking application
+
+### 4.4.1 Routeing capabilities
+
+#### 4.4.1.1 Overview
+
+The business trunking application can provide a number of special routeing capabilities. Examples of these are as follows:
+
+- Break-in.
+- Break-out.
+- Bulk rerouting.
+
+#### 4.4.1.2 Break-in
+
+A business trunking application can provide break-in. Break-in is where public network traffic is routed in the NGN to a point where it can enter an NGCN, or other business communication capability, on terms advantageous to the NGCN operator. A business trunking application providing break-in therefore converts public network traffic to become private network traffic. The purpose of this capability is to allow a call from outside the NGCN to reach a user within the enterprise. The NGN operator defines the set of rules or policies under which this should occur, and the NGCN operator should be able to configure the capability within those rules and policies. As an example, these rules and policies may be selected for tariff reasons (for example such that the NGCN operator can reduce the tariff to the calling user), and the point where the capability is applied may be dependent on both geographic location and the NGN operator involved.
+
+#### 4.4.1.3 Break-out
+
+A business trunking application can provide break-out. Break-out is where private network traffic is routed in the NGCN, or other business communication capability, to a point where it can enter an NGN on terms advantageous to the NGCN operator. A business trunking application providing break-out therefore converts private network traffic to become public network traffic. The purpose of this capability is to allow a call from within the NGCN, or other business
+
+communication capability, to reach a user outside the enterprise (e.g. in the NGN). The NGN operator defines the set of rules or policies under which this should occur, and the NGCN operator should be able to configure the capability within those rules and policies. As an example, these rules and policies may be selected for tariff reasons, and the point where the capability is applied may be dependent on both geographic location and the NGN operator involved.
+
+When break-out is provided, the business trunking application shall convert any identities provided as private network numbers to valid public telecommunication numbers.
+
+#### 4.4.1.4 Bulk rerouting
+
+A business trunking application can provide bulk rerouting. Bulk rerouting is where private network traffic (possibly after break-in) destined for a terminating NGCN site is routed to an alternative NGCN site or answer point. This allows the NGCN site to be removed from service, e.g. overnight when it is not attended, or under fault conditions. The NGN operator defines the set of rules or policies under which this should occur, and the NGCN operator should be able to configure the capability within those rules and policies. These can include:
+
+- a) not reachable (e.g. all calls to a particular NGCN site are diverted to a configured destination in case IP connectivity is lost between the network and this NGCN site);
+- b) congestion; and
+- c) time and date (e.g. all calls to a particular NGCN site are rerouted to a configured destination during closed hours).
+
+### 4.4.2 Communication barring
+
+Communication barring enables network rejection of incoming communications that fulfil certain globally provisioned or configured conditions for a particular NGCN site. The NGN operator defines the set of rules or policies under which this should occur, and the NGCN operator should be able to configure the capability within those rules and policies. The decision to reject a communication shall be independent of the actual communication target (i.e. which line behind the NGCN site is being targeted by the session).
+
+# --- 5 PSTN/ISDN emulation service
+
+Not in the scope of the present document.
+
+# --- 6 Codecs services
+
+Requirements on codec support in the network from TS 181 005 [2] clause 6 apply.
+
+# --- 7 Network attachment requirements
+
+## 7.1 General
+
+Network attachment requirements from 3GPP TS 22.228 [6] apply.
+
+## 7.2 Specific requirements for virtual leased line
+
+### 7.2.1 Security requirements for virtual leased line
+
+When Virtual Leased Line is being provided, the NGN shall comply to the Communications and Data Security Requirements for Network Domain Security as specified in 3GPP TS 33.210 [4].
+
+# --- 8 CPE configuration
+
+CPE in the context of the present document is NGCN site equipment that connects to an NGN. Requirements on CPE configuration support in the network from 3GPP TS 22.228 [8] clause 5 apply. No specific requirements for CPE configuration support have been identified for business communication in this release.
+
+# --- 9 Control of processing overload
+
+In addition to the control of processing overload requirements in TS 181 005 [2] clause 10, an NGN shall have mechanisms available to control overload at the interconnect between that NGN and an NGCN. Where NGCN sites from multiple enterprises are served by the same processing resource an NGN shall ensure that overload affects traffic from and to NGCN sites of multiple enterprises, and other traffic, fairly.
+
+An NGN shall be able to provide to an NGCN site processing overload control information, the NGCN site shall use this to regulate the load presented to the NGN. How an NGCN site regulates the load presented to an NGN is outside the scope of the present document.
+
+An NGCN site shall be able to provide to an NGN processing overload control information, an NGN shall use this to regulate the load presented to an NGCN site.
+
+NOTE: HES users will be treated in the same manner as ordinary NGN users.
+
+# --- 10 IP addressing
+
+Requirements on IP addressing support in the network from 3GPP TS 22.228 [6] apply. For business communication capabilities hosted in an NGN, the IP addressing support of that NGN applies.
+
+# --- 11 NGN interconnection
+
+Requirements on NGN interconnection support in the network from 3GPP TS 22.228 [6] apply. No specific requirements for NGN interconnection support have been identified for business communication in this release.
+
+# --- 12 Transport stratum
+
+## 12.1 NGN/NGCN interconnection requirements
+
+### 12.1.1 Redundancy support
+
+An NGN may support the connection of multiple NGCN sites belonging to the same enterprise, where an NGCN site B may serve as a redundant site for another NGCN site A. Redundancy is needed to ensure reachability of the NGCN users located in site A via the redundant site B.
+
+When an NGN detects that an NGCN site cannot accept (totally or partially) communications or detects a failure at the interconnect with the NGCN site, then an NGN shall support failover mechanisms to the NGCN site serving as redundant NGCN site.
+
+## 12.2 Specific requirements for virtual leased line
+
+NGN may provide the following capabilities:
+
+- A virtual leased line, where NGCN sites are interconnected transparently on IP level through the NGN. (IP level VPN) No additional capabilities are provided by the NGN.
+
+- A virtual leased line, where an NGCN UE (not directly connected to an NGCN site, but connected at the transport stratum to the NGN) and an NGCN site are interconnected transparently on IP level through the NGN. (IP level VPN) No additional capabilities are provided by the NGN.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | | | | |
+|----------------|-----------|---------|------|----|-----|--------|-----|-----------------------------------------------------------|--------|--------|-----------|
+| TSG SA# | SA Doc. | SA1 Doc | Spec | CR | Rev | Rel | Cat | Subject/Comment | Old | New | Work Item |
+| SP-65 | SP-140500 | - | | | | Rel-12 | | Raised to v.12.0.0 following SA's approval | 2.0.0 | 12.0.0 | |
+| 2015-12 | - | - | - | - | - | Rel-13 | - | Updated to Rel-13 by MCC | 12.0.0 | 13.0.0 | |
+| 2017-03 | - | - | - | - | - | - | - | Updated to Rel-14 by MCC | 13.0.0 | 14.0.0 | |
+| 2018-06 | - | - | - | - | - | - | - | Updated to Rel-15 by MCC | 14.0.0 | 15.0.0 | |
+| SA#88e | - | - | - | - | - | - | - | Updated to Rel-16 by MCC | 15.0.0 | 16.0.0 | |
+| 2022-03 | - | - | - | - | - | - | - | Updated to Rel-17 by MCC | 16.0.0 | 17.0.0 | |
+| 2024-03 | - | - | - | - | - | - | - | Updated to Rel-18 by MCC (and issue with v.18.0.0 upload) | 17.0.0 | 18.0.1 | |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22835/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-18/22_series/22835/088921fa3f5a44c8551815122517eefd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ce8275b79969e899e95d758f23c6a39fb48aca2
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/088921fa3f5a44c8551815122517eefd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9bddf1499ab357f0331ab111aa6ed3106245db729935fe2159070694ee0c08f1
+size 40582
diff --git a/marked/Rel-18/22_series/22835/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-18/22_series/22835/171115f072e42b379238ed0dd438e9d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c71888e62fd08623b0fe84fe1603f49c06a95c8
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/171115f072e42b379238ed0dd438e9d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d11c0247220bf76a2c023b6769a33ed1e8485633bb536ca99f852b704ddf0ca6
+size 44138
diff --git a/marked/Rel-18/22_series/22835/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-18/22_series/22835/19a59d6b53059ebd27b13c98793f88e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f0786888ea51724c187f048b37c8b6b239920bb
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/19a59d6b53059ebd27b13c98793f88e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1979dbe209548928fbf159ba3c2e90c3ffd00f137af75c4731b5bf66b9a9361
+size 40042
diff --git a/marked/Rel-18/22_series/22835/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-18/22_series/22835/1c94fd3cebf58af136144f14160d128e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d94463078180759f3a517bd5f3f28e10e9923511
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/1c94fd3cebf58af136144f14160d128e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f11b29bf1b00634dad41246231afd7e6f3a1163cd82b3aa0fd4fe4d049ea383
+size 30935
diff --git a/marked/Rel-18/22_series/22835/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-18/22_series/22835/21ad58fee90f2be50708ff541d225507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f851848c975b0c9eb0f103d7247d2da5614b7255
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/21ad58fee90f2be50708ff541d225507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5a73e082048f2e8e606e6a81ca364df0ea13c8927c8f1c88c59d4e55c67781e
+size 25658
diff --git a/marked/Rel-18/22_series/22835/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/22_series/22835/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36a32bad1e219791783c3887998b1a4c5d475adf
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b93cbe8047d2c7e32efd896c898796bfc8c13daa0dfbaa8bae6bc580dfb71ce
+size 42351
diff --git a/marked/Rel-18/22_series/22835/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-18/22_series/22835/392a79ccd95e682ccd08f35ab2e64144_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7c48c9b3b8e7bd4efcdd52014f12d45b6a45039
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/392a79ccd95e682ccd08f35ab2e64144_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5870854718a364393e24f66ce9e4d526b1aa122a650ba0386816013162b4546f
+size 36755
diff --git a/marked/Rel-18/22_series/22835/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-18/22_series/22835/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a87b023ebb7b6e9b5a3e54c69825844a6b80db65
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64002ab66489610d92e1e86dd66532fc39b46c90c0b903f591d318a8a669e0e3
+size 25398
diff --git a/marked/Rel-18/22_series/22835/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-18/22_series/22835/55136bc716146672fc680fa05989f1d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37275f9a9275009865fe53a9a771b386018dbf8e
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/55136bc716146672fc680fa05989f1d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ebcf7a62cef21d5daca0fde776784989e3a47f9b69f5a09e03d46e4569f7a85
+size 34988
diff --git a/marked/Rel-18/22_series/22835/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/22_series/22835/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d90cf0c2f1478058ef5da745a5159b18e07ef78
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b235de689154ea70b5425701acdc261e533ea860d9ae552b9f6c51371ffd7f03
+size 42259
diff --git a/marked/Rel-18/22_series/22835/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22835/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6fcb1730beb669a0424260bd2b93a2fc975ae6ae
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13b96acf8eb74e3be396791bd57d935c14992c2d1a6fe122eae03fbca660402a
+size 9594
diff --git a/marked/Rel-18/22_series/22835/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22835/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6098c8075c10033492de6a25c4da8bdf202a6b63
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73e5b530791aa07c22ce0683dcc1c0e566c85fe8bc6bd213ec4ae599d82014dc
+size 5661
diff --git a/marked/Rel-18/22_series/22835/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/Rel-18/22_series/22835/66c2bf11a8f117cddf67eff92d4c736c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..438bad4f9000282975a2d095394b447f05b7658b
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/66c2bf11a8f117cddf67eff92d4c736c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee8eeabceb9808b9ba5322aa6208f19619d1b19018da904a374462085b98adb7
+size 23723
diff --git a/marked/Rel-18/22_series/22835/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-18/22_series/22835/759c7d62402f0b4651ddce292be5bdef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6b4ae9cbb5ee042f39bb61826e0b56b6abce9fea
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/759c7d62402f0b4651ddce292be5bdef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b9f5a800c1da6c69714cff38d8ab9eb78b656a9bc78c93864e31af476285491
+size 33079
diff --git a/marked/Rel-18/22_series/22835/a51105b2031bad93b818b82f071c6add_img.jpg b/marked/Rel-18/22_series/22835/a51105b2031bad93b818b82f071c6add_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34641f6216a7c1c903be098be04ee62595592c18
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/a51105b2031bad93b818b82f071c6add_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7c577c5f914c5fff725637af145aafd9fcc8b28fa97b51e8ca8563f2c3b47d6
+size 52537
diff --git a/marked/Rel-18/22_series/22835/ae05c5a58b4f9ae5751c216b280b0f72_img.jpg b/marked/Rel-18/22_series/22835/ae05c5a58b4f9ae5751c216b280b0f72_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd456627cebda0907adad6af6fcf15f9a2390eb2
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/ae05c5a58b4f9ae5751c216b280b0f72_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b129afc2641568f8cebd10ade5d23b0f1fd16c9f5debc674b4b292aa4123c7bc
+size 38011
diff --git a/marked/Rel-18/22_series/22835/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-18/22_series/22835/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..968c493dd8bdc0c610ffedf353f7ed40a99a5e1f
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5271806d5edadbbebec75ab534cd3f0925f3c4796f0862bb3f62f18715fda2e5
+size 42388
diff --git a/marked/Rel-18/22_series/22835/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/22_series/22835/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..306703c63a305eb2941180444f096120102216a2
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b89a617ad949eb2568122b6fb60da73adbb3818759ee458631e48a6c636b6a5
+size 32058
diff --git a/marked/Rel-18/22_series/22835/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/marked/Rel-18/22_series/22835/f324fbc5d5af1e4da9cd932389f0064c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d767d7baa90dc440d7e2f90916c39f54d1a535d
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/f324fbc5d5af1e4da9cd932389f0064c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d68c606429480260a3a31d4040829082a4aaded30fbdda017a354314fd9f217b
+size 26659
diff --git a/marked/Rel-18/22_series/22835/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/Rel-18/22_series/22835/f57a881fcbcaf494a7dedc4f61224991_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..120f9f85f66622e477e722fbaf516c6ccafaa28d
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/f57a881fcbcaf494a7dedc4f61224991_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36a3b8c6e2004730121b711d8e42deb04b7a6016049607139cd1876d9989d1e6
+size 28063
diff --git a/marked/Rel-18/22_series/22835/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/22_series/22835/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5a3115a6657d67bb2149e1cd1f71fc158173df4
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7833d92b618b0fa29ba68aa9455c18fb586b5abab9638714ccedd636c43f2454
+size 54300
diff --git a/marked/Rel-18/22_series/22835/raw.md b/marked/Rel-18/22_series/22835/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..55fa11842f18822ba051e6f7858376d358d1ebe3
--- /dev/null
+++ b/marked/Rel-18/22_series/22835/raw.md
@@ -0,0 +1,1237 @@
+
+
+# 3GPP TR 22.835 V18.2.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhanced Access to and Support of Network Slice (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+5G, Network Slice
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-----------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Overview..... | 7 |
+| 5 Use cases..... | 8 |
+| 5.1. Initial access scenario for a network slice service..... | 8 |
+| 5.1.1 Description ..... | 8 |
+| 5.1.2 Pre-conditions..... | 8 |
+| 5.1.3 Service Flows ..... | 9 |
+| 5.1.4 Post-conditions ..... | 9 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 10 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 10 |
+| 5.2. Mobility Handling scenario for a network slice service Use case ..... | 10 |
+| 5.2.1 Description ..... | 10 |
+| 5.2.2 Pre-conditions..... | 10 |
+| 5.2.3 Service Flows ..... | 11 |
+| 5.2.4 Post-conditions ..... | 13 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 14 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.3. Service scenario for disjoint network slices..... | 14 |
+| 5.3.1 Description ..... | 14 |
+| 5.3.2 Pre-conditions..... | 14 |
+| 5.3.3 Service Flows ..... | 15 |
+| 5.3.4 Post-conditions ..... | 15 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 15 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 15 |
+| 5.4. Use of Multi-RATs for network slices..... | 16 |
+| 5.4.1 Description ..... | 16 |
+| 5.4.2 Pre-conditions..... | 16 |
+| 5.4.3 Service Flows ..... | 16 |
+| 5.4.4 Post-conditions ..... | 17 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 17 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 17 |
+| 5.5 Use case on access to slices when roaming..... | 17 |
+| 5.5.1 Description ..... | 17 |
+| 5.5.2 Pre-conditions..... | 18 |
+| 5.5.3 Service Flows ..... | 18 |
+| 5.5.4 Post-conditions ..... | 18 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 18 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 18 |
+| 5.6 Use case on simultaneous access to multiple slices on different VPLMNs..... | 18 |
+| 5.6.1 Description ..... | 18 |
+| 5.6.2 Pre-conditions..... | 19 |
+| 5.6.3 Service Flows ..... | 19 |
+| 5.6.4 Post-conditions ..... | 19 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 19 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 19 |
+| 5.7 Slice Access with Application Preference ..... | 20 |
+| 5.7.1 Description ..... | 20 |
+| 5.7.2 Pre-conditions..... | 20 |
+| 5.7.3 Service Flows ..... | 21 |
+| 5.7.4 Post-conditions ..... | 21 |
+
+| | | |
+|-----------------|-----------------------------------------------------------------------------|-----------|
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 21 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 22 |
+| 5.8 | Use case for application-based preference..... | 22 |
+| 5.8.1 | Description ..... | 22 |
+| 5.8.2 | Pre-conditions..... | 22 |
+| 5.8.3 | Service Flows ..... | 23 |
+| 5.8.4 | Post-conditions ..... | 25 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 25 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 25 |
+| 5.9. | Regionally different resources for network slices..... | 25 |
+| 5.9.1 | Description ..... | 25 |
+| 5.9.2 | Pre-conditions..... | 26 |
+| 5.9.3 | Service Flows ..... | 26 |
+| 5.9.4 | Post-conditions ..... | 27 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 27 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 27 |
+| 5.10. | Isolation of resource for network slice..... | 27 |
+| 5.10.1 | Description ..... | 27 |
+| 5.10.2 | Pre-conditions..... | 28 |
+| 5.10.3 | Service Flows ..... | 28 |
+| 5.10.4 | Post-conditions ..... | 29 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 29 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 29 |
+| 5.11. | Interaction with Third party for network slice ..... | 29 |
+| 5.11.1 | Description ..... | 29 |
+| 5.11.2 | Pre-conditions..... | 30 |
+| 5.11.3 | Service Flows ..... | 30 |
+| 5.11.4 | Post-conditions ..... | 30 |
+| 5.11.5 | Existing features partly or fully covering the use case functionality ..... | 30 |
+| 5.11.6 | Potential New Requirements needed to support the use case..... | 31 |
+| 5.12. | Broadcast for network slice..... | 31 |
+| 5.12.1 | Description ..... | 31 |
+| 5.12.2 | Pre-conditions..... | 31 |
+| 5.12.3 | Service Flows ..... | 32 |
+| 5.12.4 | Post-conditions ..... | 32 |
+| 5.12.5 | Existing features partly or fully covering the use case functionality ..... | 32 |
+| 5.12.6 | Potential New Requirements needed to support the use case..... | 33 |
+| 5.13. | Relaying and backhauling data for a network slice..... | 33 |
+| 5.13.1 | Description ..... | 33 |
+| 5.13.2 | Pre-conditions..... | 33 |
+| 5.13.3 | Service Flows ..... | 34 |
+| 5.13.4 | Post-conditions ..... | 34 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 34 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 34 |
+| 6 | Consolidated Potential Requirements ..... | 35 |
+| 7 | Conclusions and Recommendations ..... | 37 |
+| Annex A: | Consideration for different type of frequency ..... | 38 |
+| Annex B: | Change history..... | 39 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document studies various use cases and scenarios using network slices, in order to identify potential service requirements for the 5G system, e.g.:
+
+- when there is a restriction of network slice to e.g., certain frequency bands/sub bands, RATs, geographical areas, networks and applications,
+- when a UE has a subscription to multiple network slices and these network slices are deployed for e.g., different frequency bands/sub bands, RATs, geographical area and applications,
+- when there is a preference or prioritization for a network slice over other network slices e.g. when there are conflicting constraints on network slice availability.
+
+The present document also includes a gap analysis of its derived potential requirements versus existing 3GPP requirements.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"
+- [2] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1"
+- [3] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
+- [4] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
+- [5] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [6] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+
+
+# --- 4 Overview
+
+The concept of network slice was discussed from the beginning of the study for 5G system. Network slicing supports the flexible use of network resources so that multiple networks customized to the needs of each set of applications can be provided simultaneously over the network resources while ensuring resource isolation and meeting different SLAs. As more diverse industries start to use the capabilities provided by 5G system and various new services are implemented over the 5G system, the expected service requirements on the 5G system vary. To meet these diverse requirements on the network, the use of network slices will increase further as 5G system deployments are expanded.
+
+When configuring network slices within its network, each network operator may consider various factors, such as required QoS of the applications supported over the network slices, the amount of required network resources to support the applications, the expected geographical and time boundary where the network slice services need to be provided, the usable and deployed network resources at the location where the applications are used, the number of users, the type of devices (e.g., IIoT), etc. After considering these factors, a network operator may provide a network slice for different services to users. Similarly, 3rd parties may be authorized by the network operator to configure their own network slices based on these various criteria, within the bounds of an SLA with the network operator.
+
+However, the provisioning of network slices can be complicated, such as when a UE requests the simultaneous use of multiple network slices where the configurations for those network slices may not be compatible, when network slices are deployed over different network resources due to isolation requirements, when location based applications have specific requirements based on time of the day, or when the available networks support different sets of network slices.
+
+# 5 Use cases
+
+## 5.1. Initial access scenario for a network slice service
+
+### 5.1.1 Description
+
+Typically, users want for their devices to camp on a cell and be online as soon as possible after power-on. Especially, for 5G System which can provide ultra-low-latency data transport service, it is also important to reduce the time that takes for a device to send a packet after power on, to satisfy overall 5G experience.
+
+### 5.1.2 Pre-conditions
+
+Figure 5.1.2-1 shows the use case scenario where different network slices are configured on different frequency bands at a certain geographical location. In this scenario, all network slices and radio frequency bands belong to the same operator.
+
+
+
+Figure 5.1.2-1: Initial Setup before-power on. A graph showing Frequency (Freq) on the Y-axis and Location on the X-axis. Two network slices, Slice M (light blue) and Slice N (yellow), are shown as horizontal ovals. Slice M is centered at frequency F1 and Slice N is centered at frequency F2. Below the graph, User Equipment (UE) icons are shown at two locations: GA and GB. At GA, UEs A1, A2, and A3 are shown. At GB, UEs B1, B2, B3, and B4 are shown. UEs A1 and B1 are associated with Slice M. UEs A2 and B2 are associated with Slice N. UEs A3, B3, and B4 are associated with both Slice M and Slice N. UEs A3 and B3 have a preference for Slice M, while UE B4 has a preference for Slice N.
+
+**Figure 5.1.2-1 Initial Setup before-power on**
+
+In this use case and figure 5.1.2-1, following is assumed as pre-condition:
+
+- Initially, UE A1, A2 and A3 are located at location GA and UE B1, B2 and B3 are located at location GB.
+- UE A1 and B1 have a subscription only to slice M, and UE A2 and B2 have a subscription only to slice N.
+- UE A3, B3 and B4 have a subscription to both slice M and slice N. A3 and B3 have preference to slice M while UE B4 has preference to slice N.
+
+- At location GA, cells are deployed over only frequency F1.
+- At location GB, cells are deployed on both frequency F1 and F2.
+
+Furthermore, in this use case and in figure 5.1.2-1, due to requirement such as slice-isolation, following is further assumed:
+
+- Slice M is configured to be provided only if it is accessed over F1.
+- Slice N is configured to be provided only if it is accessed over F2.
+- Slice N and Slice M are not simultaneously provided to UEs.
+
+### 5.1.3 Service Flows
+
+After power-up, following occurs for UE A1, A2 and A3:
+
+- UE A1, A2 and A3 start searching of available cells.
+- UE A1, A2 and A3 detect cells on Frequency F1.
+- UE A1, A2 and A3 start registration via cells on F1.
+- Based on subscription information, A1 and A3 are served with Slice M.
+- Because the UE A2 does not have subscription for slice M, A2 stays in limited service state on F1 and does not perform further activity toward the cells on F1.
+
+After power-up, following occurs for UE B1, B2, B3 and B4 when the UEs first try F1:
+
+- UE B1, B2, B3 and B4 start searching of available cells.
+- UE B1 and B3 select cells on Frequency F1 and start registration via the selected cell. Based on subscription information, the network provides services to UE B1 and B3 with Slice M over F1.
+- UE B2 and B4 switches to Frequency F2 as soon as possible and selects cells on Frequency F2 and start registration. Because the network does not provide service of F1, UE B2 needs to minimize unnecessary attempt on F1. Similarly, the preferred slice is provided over F1 than F2, the UE B4 needs to move to F2 as soon as possible.
+
+In this use case, it is desirable for the UEs to quickly camp on desired frequency where they can get required network slice services, to minimize time period of service unavailability. E.g. in above service flow, if UE B2 is stuck at F1, the UE B2 is out of service until it moves to F2.
+
+### 5.1.4 Post-conditions
+
+Figure 5.1.4-1 shows on which frequency each UE camps on finally to get desirable network slice service.
+
+
+
+The diagram illustrates the UE status after power-on in a 2D space defined by Frequency (Freq) on the vertical axis and Geography (Geo) on the horizontal axis.
+ - The vertical axis has two marked frequencies: F1 and F2.
+ - The horizontal axis has two marked geographical locations: GA and GB.
+ - Slice M is represented by a light blue oval centered around F1 and GB. It contains four cell icons labeled A1, A2, A3, and B1.
+ - Slice N is represented by a yellow oval centered around F2 and GB. It contains four cell icons labeled B2, B3, B4, and A1.
+
+Figure 5.1.4-1 UE status after-power on. A graph showing Frequency (Freq) on the Y-axis and Geography (Geo) on the X-axis. Two network slices, Slice M and Slice N, are shown. Slice M is associated with frequency F1 and geography GA, containing cells A1, A2, and A3. Slice N is associated with frequency F2 and geography GB, containing cells B1, B2, B3, and B4.
+
+Figure 5.1.4-1 UE status after-power on
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+When a UE is located in an area where there is an authorized network slice for the UE, the 5G system shall be able to efficiently enable the UE to camp on radio resources where the network slice is provided.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+[PR.5.1.6-2] When a UE is located in an area where there is at least one authorized network slice for the UE, the 5G system shall be able to minimize the time for the UE to access the network slices which is most suitable based on e.g., location of the UE, active applications, UE capability, frequency used by the network slice.
+
+[PR.5.1.6-1] When a UE is located in an area where there is no authorized network slice for the UE, the 5G system shall support a mechanism to efficiently enable the UE to minimize power consumption (e.g., cell search, cell measurement).
+
+## 5.2. Mobility Handling scenario for a network slice service Use case
+
+### 5.2.1 Description
+
+Due to various reasons, the availability of cell on a certain frequency is not homogeneous. For example, in an area where lots of people gather e.g. like office district, operator may deploy cells on all available frequencies. On the other hand, in an area whether population density is low, only part of owned frequency bands will be used to provide connectivity service.
+
+In this use case, the above situation is investigated with movement of terminals. I.e., as mobile devices move from an area where some frequency band is used to deploy cells to an area where other frequency band is used to deploy cells. Even in this case, it is important to reduce the time that the UE is not provided with network slice service which it deserves.
+
+### 5.2.2 Pre-conditions
+
+Figure 5.2.2-1 shows the use case scenario where different network slices are configured on different frequency bands at a certain geographical location. In this scenario, all network slices and radio frequency bands belong to the same operator.
+
+
+
+Figure 5.2.2-1: Initial Setup before-power on. A graph showing Frequency (Freq) on the Y-axis and Geography (Geo) on the X-axis. Two vertical dashed lines represent locations GA and GB. At GA, four User Equipment (UE) icons labeled A1, A2, A3, and A4 are shown. At GB, four UE icons labeled B1, B2, B3, and B4 are shown. Two horizontal ellipses represent network slices: Slice M (light blue) and Slice N (yellow). Slice M is associated with frequency F1 and location GB, containing UEs B1 and B3. Slice N is associated with frequency F2 and location GB, containing UEs B2 and B4. Arrows indicate the mapping of UEs to slices: A1 and B1 to Slice M; A2 and B2 to Slice N; A3, A4, B3, and B4 to both Slice M and Slice N, with A3 and B3 preferring Slice M and A4 and B4 preferring Slice N.
+
+**Figure 5.2.2-1 Initial Setup before-power on**
+
+In this use case and figure 5.2.2-1, following is assumed as pre-condition:
+
+- Location:
+ - Initially, UE A1, A2, A3 and A4 are located at location GA.
+ - Initially, UE B1, B2, B3 and B4 are located at location GB.
+- Subscription:
+ - UE A1 and B1 have a subscription only to slice M.
+ - UE A2 and B2 have a subscription only to slice N.
+ - UE A3, A4, B3 and B4 have a subscription to both slice M and slice N. A3 and B3 have preference to slice M while A4 and B4 have preference to slice N.
+- Deployment:
+ - At location GA, cells are available over frequency F1, but not over frequency F2.
+ - At location GB, cells are available over both F1 and F2.
+ - Slice M is configured to be available over only F1 and Slice N is configured to be available over only F2. Slice N is available only within a certain location, e.g. within a factory. Slice M is available in wide area
+ - Due to isolation policy, slice N and slice M are strictly isolated. I.e., hardware is not shared between the slices.
+ - Based on application policy, some applications are allowed to be served over either slice N and slice M, while some applications are restricted to use only specific slice.
+- Initial condition:
+ - A1, A2, A3, A4, B1 and B3 are on F1. B2 and B4 are on F2.
+
+### 5.2.3 Service Flows
+
+Following is potential service flow for UE A1, A2, A3 and A4:
+
+- UE A1, A2, A3 and A4 are on Frequency F1. UE A1, A3 and A4 are served with Slice M, but UE A2 is in limited service state, due to lack of subscription for slice M. Accordingly, the UE A2 needs to minimize power consumption, e.g., that may be caused due to unnecessary monitoring of other cells.
+- UE A1, A2, A3 and A4 move toward GB via GC.
+- UE A1 and A3 continues to be serviced with Slice M via Frequency F1 at location GC and GB.
+- At location GC, the UE A2 starts searching cells on Frequency F2. After moving to F2, the UE A2 starts to be served with Slice N. This should occur as soon as possible, because the UE A2 was out of service from location GA to location GC.
+- Somewhere between location GC and location GB, the UE A4 moves to Frequency F2 and starts to be served with Slice N, because the UE A4 prefers Slice N to Slice M. To minimize impact on the ongoing services over Slice M, when the UE A4 moves to Frequency F2 can be dependent on many other factors such as active applications on each slice.
+
+Following is potential service flow for UE B1, B2, B3 and B4:
+
+- UE B2 and B4 are on Frequency F2 and served with Slice N. UE B1 and B3 are on Frequency F1 and served with Slice M.
+- Due to lack of subscription of network slices provided over F1, the UE B2 may be allowed to minimize power consumption that may be caused, e.g., due to monitoring cells of other frequency F1.
+- UE B1, B2, B3 and B4 move toward GA via GC.
+- UE B1 and B3 are still serviced with Slice M via Frequency F1 from location GC to location GA.
+- As the UE B2 moves across location GC and moves toward GA, the UE B2 will eventually lose connectivity service because there is no available cell on Frequency F2 and there is no allowed network slice on F1 for the UE B2. In this case, it is desirable for the UE B2 to prepare for the sudden loss of connectivity service. Especially, if the service over slice N is kind of URLLC service that is available only within some specific places such as within a smart factory, the sudden loss of connectivity should be avoided as much as possible. Thus, before the UE crosses the location GC, the UE B2 needs to be given with grace time to prepare for the loss of connectivity, e.g. termination of ongoing applications.
+- As the UE B4 approaches location GC, the UE B4 needs to move to Frequency F1. As the UE B4 moved to Frequency F1, the UE starts to be served with Slice M. Because the UE B4 prefers Slice N to Slice M, the transition from F2 to F1 should not occur unnecessarily too early. On the other hand, if the transition from F2 to F1 occurs after the UE B4 crosses the location GC, there is potential loss of connectivity. Thus, the transition from F2 to F1 should occur before crossing location GC. To minimize impact on the ongoing services over Slice N, it may also be better for the UE to be notified in advance of the transition from F2 to F1. This may enable for the UE to do smooth adjustment of services, such as termination of application or relocation of application to one slice to another.
+
+
+
+The diagram illustrates the transition of User Equipment (UE) as they move from location GA to GB. The vertical axis represents Frequency (Freq) with levels F1 and F2. The horizontal axis represents Geography (Geo) with markers GA, GC, and GB. Vertical dashed lines are at GA, GC, and GB. A light blue oval labeled 'Slice M' is centered at F1, and a yellow oval labeled 'Slice N' is centered at F2. UEs are represented by smartphone icons. At GA, UEs A1, B1, A3, B3 are on F1 (Slice M); A2, B2, A4, B4 are on F2 (Slice N). As they move past GC, arrows show transitions: A1, B1, A3, B3 stay on F1; A2 and A4 move to F2; B2 stays on F1; B4 moves to F1. At GB, the final positions are: A1, B1, A3, B3 on F1 (Slice M); A2, A4 on F2 (Slice N); B2, B4 on F1 (Slice M).
+
+Figure 5.2.3-1 Transition: A graph showing UE movement from location GA to GB across frequencies F1 and F2. The graph includes two slices, Slice M (F1) and Slice N (F2). Arrows indicate the transition of UEs A1, A2, A3, A4, B1, B2, B3, and B4 between these slices as they move geographically.
+
+Figure 5.2.3-1 Transition
+
+Figure 5.2.3-1 shows the UE movement.
+
+### 5.2.4 Post-conditions
+
+After passing through location GC, following are desired results after mobility:
+
+- UE A1, B1, A3 and B3 keep on staying on F1 and are provided with slice M.
+- UE A2 moves to F2 and is now provided with slice N.
+- UE A4 moves to F2 and is now provided with slice N and is not provided anymore with slice M.
+- UE B2 camps on F1, is disconnected from slice N and is in limited state.
+- UE B4 moves to F1, is provided with slice M and not any more with slice N.
+
+Figure 5.2.4-1 shows on which frequency each UE camps on after movement.
+
+
+
+The diagram shows the status of UEs after movement, corresponding to the post-conditions. The axes and slices are the same as in Figure 5.2.3-1. At location GA, UEs B2, B4, B3, and B1 are all on frequency F1. UEs A3 and A1 are also on F1, within Slice M. At location GB, UEs A2 and A4 are on frequency F2 within Slice N. UEs A3 and A1 remain on F1 within Slice M. UEs B2, B4, B3, and B1 all remain on F1, with B2 and B4 now part of Slice M.
+
+Figure 5.2.4-1 UE status after movement: A graph showing the final status of UEs after movement. UEs A1, B1, A3, B3 are on F1 (Slice M). UEs A2, A4 are on F2 (Slice N). UEs B2, B4 are on F1 (Slice M).
+
+Figure 5.2.4-1 UE status after movement
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+When a UE moves from an area where there is no authorized network slice for the UE to an area where there is at least one authorized network slice for the UE, the 3GPP system shall be able to efficiently enable the UE to access the authorized network slices as soon as possible.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR.5.2.6-1] When a UE moves out of the service area of a network slice for an active application, the 5G system shall be able to minimize impact on the applications (e.g., providing early notification).NOTE: Various methods can be used to detect whether the UE moves toward the border area and to notify the UE.
+
+## 5.3. Service scenario for disjoint network slices
+
+### 5.3.1 Description
+
+As more network slices are deployed, it is likely that each UE can access to multiple network slices. While some network slice services can be simultaneously provided to the UE, there can be network slices which cannot simultaneously provide services to the UE. This is because there are multiple related factors for a network slice, e.g., enterprise use vs personal use, isolation requirement, general public use vs public safety use, frequency limitation, location restriction, etc.
+
+### 5.3.2 Pre-conditions
+
+Network slices are deployed by same geographical location but they are incompatible by configuration. Figure 5.3.2-1 shows the use case scenario where a RAN node connects to two network slices simultaneously. Slice M and Slice N have no shared/common core network nodes supporting these network slices due to network resources incompatibility in 5GC. For example, Slice M is used for public security and Slice N is used for Internet access. In the 5GC, dedicated network resources and network functionalities are separately customised for public security emergency service and video service to meet the isolation requirements, which ensures the independence of core network resources between different network slices. Accordingly, the two network slices are isolated and cannot be simultaneously provided to the UE.
+
+
+
+Diagram illustrating the initial condition for disjoint network slices. A RAN node (radio tower icon) is connected to two network slices: Slice N (yellow oval) and Slice M (light blue oval). Slice N is connected to a factory icon, and Slice M is connected to a grid icon. Three User Equipment (UE) icons are shown: A1, A2, and A3. A1 and A3 are connected to Slice M, while A2 and A3 are connected to Slice N. A dashed line separates Slice N and Slice M, indicating they are disjoint.
+
+Figure 5.3.2-1 Initial condition
+
+In this figure, it is assumed that
+
+- Subscription and configuration:
+ - UE A1 and A3 are authorized to access Slice M.
+ - UE A2 and A3 are authorized to access Slice N.
+ - For UE A3, it is configured which applications use which network slices.
+- Deployment:
+
+- Slice N and Slice M are deployed at the same geographical location. Slice N and Slice M are isolated. Due to the network resources incompatibility in 5G core network, there are no shared/common core network nodes supporting the Slice N and Slice M.
+- NG-RAN is able to connect to both Slice M and Slice N.
+- Slice M and Slice N are provided by the same PLMN.
+
+### 5.3.3 Service Flows
+
+Following is the service flow for UE A1, A2 and A3 when the signaling from these UEs is initially routed toward nodes managing Slice N:
+
+- UE A1, A2 and A3 select the NG-RAN and start registration.
+- Network slices provide connectivity services to UE A1, A2 and A3.
+- While the UE A3 is connected to Slice N, Slice M cannot provide the connectivity service to UE A3. The user traffic applicable to Slice N is transported.
+- Later, user traffic configured to use slice M is generated in UE A3. While the same NG-RAN is used, the traffic is switched to Slice M.
+- If the user prioritizes applications configured to use Slice N, as soon as applications configured to use Slice M finish, the UE A3 needs to move back to Slice N, to minimize the latency.
+
+### 5.3.4 Post-conditions
+
+UE A1 is connected to Slice M.
+
+UE A2 is connected to Slice N.
+
+UE A3 switches between Slice N and Slice M, depending on e.g. ongoing applications.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+There are related requirements on change of network slices based on services, as defined in clause 6.1.2.2 in TS 22.261 [2]:
+
+*The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice.*
+
+There are related requirements on impacts on other network slices caused by traffic and services from one network slice, as defined in clause 6.1.2.2 in TS 22.261 [2]:
+
+*Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network.*
+
+Based on TS 22.261 [2] clause 6.1 network slicing, the following service requirement is supported:
+
+*The 5G system shall enable a UE to be simultaneously assigned to and access services from more than one network slice of one operator.*
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+The following new requirements can be derived from this use case:
+
+[PR.5.3.6-1] For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall be able to allow the UE to access the most suitable network slice (e.g. based on the ongoing applications).
+
+[PR.5.3.6-2] For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall support the minimized interruption when
+
+the UE changes the access from one network slice to another network slice. (e.g. based on changes of active applications).
+
+## 5.4. Use of Multi-RATs for network slices
+
+### 5.4.1 Description
+
+5GC is connected to NG-RAN and the NG-RAN supports both E-UTRA and NR. However, for a third party who wants to utilize a network slice, the different potential and flexibility of E-UTRA and NR is not something that can easily be disregarded.
+
+Also, the unequal possibility of radio resource slicing for NR and E-UTRA leads to a unique use case scenario.
+
+### 5.4.2 Pre-conditions
+
+Figure 5.4.2-1 shows the use case scenario where an NG-RAN is supporting both NR and E-UTRA radio resources.
+
+
+
+Diagram illustrating the initial condition for network slicing across E-UTRA and NR. On the left, four User Equipment (UE) icons are shown: A1 (light blue), A2 (yellow), A3 (orange), and A4 (light blue). In the center, the NG-RAN is divided into two radio access technology (RAT) sections. The top section is labeled 'E-UTRA' and contains 'Slice M' (light blue). The bottom section is labeled 'NR' and contains 'Slice N' (yellow) and 'Slice O' (orange). A dashed line separates the E-UTRA and NR sections. To the right, an antenna icon labeled 'A' is connected to a box labeled '5GC'.
+
+**Figure 5.4.2-1 Initial condition**
+
+In this figure, it is assumed that
+
+- Subscription:
+ - UE A1 and A4 are subscribed to a service using Slice M.
+ - UE A2 and A4 are subscribed to a service using Slice N.
+ - UE A3 is subscribed to a service using Slice O.
+- Deployment:
+ - E-UTRA is configured to serve Slice M, e.g. for general eMBB services, including a slice for IMS service.
+ - NR is configured to serve Slice N and O, e.g. for URLLC or V2X. Due to demanding requirements of V2X application, V2X application providers (e.g. OEM) requests to use only NR for Slice O.
+
+The frequencies used for E-UTRA and NR can be the same or different. For example, when DSS (Dynamic Spectrum Sharing) is used, the same frequency is used for both E-UTRA and NR, but in different time slots.
+
+### 5.4.3 Service Flows
+
+The following is an example service flow based on the setting in the previous section:
+
+- After power-on, UE A1, A2, A3 and A4 start searching for cells.
+- UE A1, A2, A3 and A4 start registration in the found cells.
+- Depending on factors such as e.g., use of Dual Connectivity, priorities of network slices, different UEs may camp on different RATs. For example, the UE A1 may camp on E-UTRA.
+
+- Based on the various inputs, for the transport of user traffic for a network slice, the RAT and radio resources can be configured. For example, when user traffic for slice M is generated for UE A4, the network may configure E-UTRA resource for the UE to deliver the traffic. For this UE A4, when user traffic for slice N is generated, the network may configure NR resources for the UE. When both NR and E-UTRA resource are configured, the user traffic for the network slice only flows over the allowed RATs.
+- When service policy changes, e.g. when slice M is now set to use NR instead of E-UTRA, UEs camp NR cells instead of E-UTRA cells. For a UE with ongoing active communication, handover occurs to move the UE from E-UTRA to NR.
+
+### 5.4.4 Post-conditions
+
+The following figure 5.4.4-1 shows the status at the end of the service flow. For the transport of user traffic, UE A1 is served by E-UTRA, UE A2 and A3 are served by NR. UE A4 may camp on either E-UTRA or NR during Idle mode and be configured with E-UTRA, NR or both depending on the active application during Connected mode.
+
+
+
+Figure 5.4.4-1 End result: A diagram showing network slices and UEs. The top section is labeled 'E-UTRA' and contains 'Slice M' (light blue) with UE A1. The bottom section is labeled 'NR' and contains 'Slice N' (yellow) with UE A2 and 'Slice O' (orange) with UE A3. UE A4 is shown between the two sections, with a dashed line connecting it to a 5GC (5G Core) via an antenna icon labeled 'A'.
+
+Figure 5.4.4-1 End result
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 [2] contains many requirements related to user traffic management and network slices.
+
+- *The 5G system shall allow the operator to define and update the set of services and capabilities supported in a network slice.*
+- *Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.*
+- *Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party*
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+The following new requirements can be derived from this use case:
+
+[PR.5.4.6-1] 5G system shall minimize signaling exchange and service interruption when there is a change in the allowed radio resources (e.g. RATs) for a network slice.
+
+## 5.5 Use case on access to slices when roaming
+
+### 5.5.1 Description
+
+A UE subscribes to multiple network slices from its home operator. The home operator has agreements with various other operators to support the same slices for roaming UEs. In this case, the most preferred VPLMN in a specific area does not support all the needed slice; however, a second VPLMN does support the slice not available in the most preferred VPLMN. In this case, the home operator can provide the necessary information to allow the UE to use the second VPLMN to obtain the service available on that network slice, while otherwise being served by the most preferred VPLMN. Figure 5.5.1-1 illustrates the scenario.
+
+
+
+Figure 5.5.1-1: Roaming UE with subscriptions to services on network slices available on different networks. The diagram shows two horizontal ellipses representing network slices. The top ellipse is yellow and labeled 'Slice N', associated with 'Network A'. The bottom ellipse is blue and labeled 'Slice M', associated with 'Network B'. A small box labeled 'A1' is positioned to the left of the ellipses. Three vertical dashed lines labeled T1, T2, and T3 intersect both ellipses. The ellipses are centered between T1 and T3, with T2 in the middle.
+
+**Figure 5.5.1-1: Roaming UE with subscriptions to services on network slices available on different networks**
+
+### 5.5.2 Pre-conditions
+
+In this scenario, the UE A1 is roaming in an area covered by 2 VPLMNs, Network A and Network B. UE A1 subscribes to services that require use of slices M and N in its home network. The corresponding slices and services are available in the visited area, even though these slices are not offered by the same network in the visited area. Network A is the most preferred VPLMN in this area.
+
+### 5.5.3 Service Flows
+
+When UE A1 first enters the visited area, it registers with Network A and can use services from slice N.
+
+At a later time (T2), the user decides to activate a service that needs slice M. The UE, detecting that slice M is not available on Network A, looks for the network that provides the slice. The UE registers on Network B and the user is able to use the service of slice M.
+
+When the service concludes and slice M is no longer needed (T3), the UE returns to Network A.
+
+### 5.5.4 Post-conditions
+
+The user is able to access all their subscribed services while roaming, even though the needed slices are not available on a single VPLMN.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+Roaming and slice access work as usual, with the addition of being able to change VPLMNs to gain access to a slice not available on the most preferred VPLMN.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR.5.5.6-1] For a roaming UE activating a service/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice.
+
+## 5.6 Use case on simultaneous access to multiple slices on different VPLMNs
+
+### 5.6.1 Description
+
+A UE has access to multiple network slices when on the HPLMN. When the UE is roaming and the VPLMN where the UE is currently registered only provides a subset of the network slices that the UE needs to use, the UE can connect to other VPLMNs at the same time to access the other subscribed network slices.
+
+### 5.6.2 Pre-conditions
+
+- UE is subscriber of Operator Toffee
+- When on its home network, Operator Toffee, UE has access to three network slices: (A)pricot, (B)anana and (C)herry
+- UE runs different applications that require the UE to simultaneously access Apricot, Banana and Cherry slices
+- Operator Toffee has agreements with:
+ - Operator Chocolate to support Apricot and Banana slices
+ - Operator Fudge to support Cherry slice
+- Operator Chocolate is the preferred roaming network
+- UE moves out of Operator Toffee's coverage area, into an area where the coverage is provided by Operator Chocolate and Operator Fudge
+
+### 5.6.3 Service Flows
+
+1. UE connects with Operator Chocolate, and has access to Apricot and Banana slices
+2. UE requires simultaneous access to all three slices, Apricot, Banana and Cherry, due to the different applications running on the UE. However, the VPLMN the UE is registered to, Operator Chocolate, does not provide support for Cherry slice
+3. UE is authorised by the HPLMN to additionally access the Cherry slice in the Operator Fudge network.
+4. UE connects to Operator Fudge's network, while retaining the connection to Operator Chocolate
+
+### 5.6.4 Post-conditions
+
+Roaming UE is able to access all three network slices simultaneously from Operator Chocolate and Operator Fudge.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+There are related requirements in TS 22.261 [2], clause 6.18 on "Multi-network connectivity and service delivery across operators ":
+
+*The 5G system shall enable users to obtain services from more than one network simultaneously on an on-demand basis.*
+
+*For a user with a single operator subscription, the use of multiple serving networks operated by different operators shall be under the control of the home operator.*
+
+TS 23.501 clause 5.3.2.4 on "Support of a UE registered over both 3GPP and Non-3GPP access" indicates:
+
+*A UE supporting registration over both 3GPP and Non-3GPP access to two PLMNs shall be able to handle two separate registrations, including two 5G-GUTIs, one per PLMN, and two associated equivalent PLMN lists.*
+
+Also, TS 33.501 has a clause 6.3.2 on "Multiple registrations in same or different serving networks"
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR.5.6.6-1] For UEs that have the ability to obtain service from more than one VPLMN simultaneously, the following requirements apply:
+
+- When a roaming UE with a single PLMN subscription requires simultaneous access to multiple network slices and the network slices are not available in a single VPLMN, the 5G system shall enable the UE to:
+ - be registered to more than one VPLMN simultaneously; and
+- use network slices from more than one VPLMN simultaneously
+
+- The HPLMN shall be able to authorise a roaming UE with a single PLMN subscription to be registered to more than one VPLMN simultaneously in order to access network slices of those VPLMNs.
+- The HPLMN shall be able to provide a UE with permission and prioritisation information of the VPLMNs the UE is authorised to register to in order to use specific network slices.
+
+NOTE: The above requirements assume certain UE capabilities, e.g. the ability to be connected to more than one PLMN simultaneously.
+
+## 5.7 Slice Access with Application Preference
+
+### 5.7.1 Description
+
+This use case intends to bring a use case for network slice to support important applications like gaming and online video in a more flexible and efficient way. For gaming or online video applications, the end users, who have subscription with MNOs who may provide multiple network slices to different users or services, may still have different priority or membership e.g. VIP maintained by 3rd party Service Provider (SP). And depending on the priority or membership information from 3rd party SP perspective, based on the agreement between SP and MNO, the UE have different priority for the available network slices.
+
+Figure 5.7.1-1 shows an example scenario for this use case.
+
+
+
+The diagram illustrates three network slices provisioned by an MNO, grouped by a vertical bracket labeled "Provisioned by MNO".
+
+- Slice#1** (blue oval) is labeled "Online video". It is connected to **SP#1** (server icon) and **UE1** (mobile device icon with a game controller). **User A** is associated with UE1.
+- Slice#2** (yellow oval) is labeled "gaming". It is connected to **SP#2** (server icon) and **UE2** (mobile device icon with a film strip). **User B** is associated with UE2.
+- Slice#3** (light blue oval) is labeled "Web, chat, download". It is not connected to any specific SP or UE.
+
+Figure 5.7.1-1: Example scenario for this use case. The diagram shows three network slices provisioned by an MNO: Slice#1 (Online video), Slice#2 (gaming), and Slice#3 (Web, chat, download). Slice#1 is associated with SP#1 and UE1 (User A). Slice#2 is associated with SP#2 and UE2 (User B). Slice#3 is not associated with any specific SP or UE. A vertical bracket on the left labeled 'Provisioned by MNO' groups all three slices.
+
+Figure 5.7.1-1 Example scenario for this use case
+
+### 5.7.2 Pre-conditions
+
+1. MNO provisioned network slices Slice#1, Slice#2, Slice#3. As an example, Slice#1 is dedicated for online video services for SP#1. Slice#2 is dedicated for gaming for SP#2. Slice#3 is a network slice for eMBB service i.e. text or voice chat, file downloading or web surfing.
+2. UE 1 and UE 2 are registered to MNO's 5G network and they have subscription to slice#1, #2 and #3. The owner of UE 1, i.e., User A, have installed Game App x and Video App y. The owner of UE 2, i.e., User B, have installed Game App z and Video App y.
+3. User A and User B are high priority users for SP#1 and SP#2 which means when these users start to use game or video app, they can use the corresponding network slice to guarantee their QoS compared with other users with lower priority and the MNO network resource can accommodate high priority users.
+4. Due to the fact that the 3rd party SP may roll out new services/applications and the users may change their VIP membership dynamically, the 3rd party needs to negotiate the priority of a network slice for UE per application.
+
+### 5.7.3 Service Flows
+
+1. MNO and SP have agreements e.g. SLA and Slice#1, Slice#2 and Slice#3 are provisioned.
+ - a) The MNO provisioned the slices and maintains the user subscription to access these slices. The SP maintains the application related user membership information.
+ - b) UE 1 and UE 2 may or may not be accessing three slices simultaneously.
+2. User A's smart phone UE 1, and User B's smart phone UE 2 turns on and registered to MNO network. After registration, UE 1 and UE 2 are able to access corresponding network slices.
+ - c) User A can access Slice#1 for online video app x and Slice#2 for gaming, also Slice#3 for other services.
+ - d) User B can access Slice#1 for online video y and gaming app z, and also Slice#3 for other services.
+3. User A and User B started chat and web surfing service, it accesses network Slice#3
+4. User A started online video, UE A access to Slice#3 which can only provide a basic SLA for the online video e.g. with lower resolution1.
+5. User A's priority for slices is dynamically changed due to the SP side updates e.g. User A changes his/her VIP. membership, thus different SLA is provided to User A's online video via Slice#1..
+6. User B started game app, UE B access to Slice #3 which can only provide a basic SLA for the game service e.g. with lower resolution and low latency is not ensured.
+7. User B's priority for slices is dynamically changed due to the SP side updates e.g. User B changes his/her VIP membership, thus different SLA is provided to User A's game app via Slice#2.
+8. User A's priority for slices are changed back to original value due the SP side update e.g. VIP membership expired, thus the online video is provided via Slice#3.
+9. User B's priority for slices are changed back to original value due to SP side update e.g. VIP membership expired, thus the game app is provided via Slice#3.
+
+In the above service flows, the different slices may be provided by same or different frequency and the coverage may be different. If different slices are deployed in different frequency bands, access of different network slices due to application should not cause degradation of user experiences.
+
+### 5.7.4 Post-conditions
+
+SP and MNO may monitor the QoS of online video and game applications and also support flexible charging for these users which change their priority accessed slices per application.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+In Clause 6.1.2 of TS 22.261 [2], network slicing requirements are specified including general, management, network slice constraints and cross-network slice coordination.
+
+In 6.1.2.2 of TS 22.261 [2], there is a requirement as follows:
+
+*The 5G system shall enable the network operator to define a priority order between different network slices in case multiple network slices compete for resources on the same network.*
+
+This requirement enables priority mechanism from network resource configuration perspective.
+
+In 6.1.2.2 of TS 22.261 [2], there is another requirement as follows:
+
+*The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice.*
+
+This requirement is from operator perspective and doesn't cover the aspect whether 3rd party application can influent the priority of network slices.
+
+The existing requirements for network slicing, e.g. which is cited in this section, is from network resource configuration perspective.
+
+However, when UE can access multiple network slices which may be tailored for different applications, there is no support of changing the priority or the preferred network slicing for the UE based on application. And this process cannot be carried out efficiently without standard-based means for MNO and third party to communicate/negotiate the preferred network slices according to application.
+
+For this use case, additional two requirements below are considered already supported:
+
+- The 5G system shall support means to dynamically change the UE priority of network slices per application with minimized interruption, according to third party's policy.
+- The 5G system shall support mechanisms to allow a 3rd party and the 5G network to negotiate the UE priority of a network slice per application.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+No new requirement is derived from this use case.
+
+## 5.8 Use case for application-based preference
+
+### 5.8.1 Description
+
+Applications using Network Slice(s) offered on different radio resources may be used differently in location and time. This brings motivation for the 5G System to support a mechanism to establish and manage a preference ordering among subscribed applications/services for use in cell (re)selection.
+
+Application preference could be set by the user or derived based on the user's application usage pattern. Application preference information in the network can be overridden by application activation, such that activating an application with a lower preference order may trigger a change in serving network slice (assuming no other application is also active on that slice) and cell (re)selection if the newly activated application requires a different radio resource.
+
+### 5.8.2 Pre-conditions
+
+Slice M & Slice N are two slices provided by the same Operator. Services from Slice M are provided over frequency band FR1 and services from slice N are provided over frequency band FR2.
+
+Slice M provides VPN and streaming services while slice N provides VPN and AR/VR-Gaming services. The UE's shown in the illustration have subscriptions to applications provided by both the slices M and N. The key difference in network slice selection lies in the application preference order used by each UE.
+
+Rama and Krishna work in different companies at the same location (e.g., an office building). Rama has a WFH (Work from Home) option which he can use frequently while Krishna does not have a WFH option from his company but may be allowed WFH in rare situations. Both their homes are located in the same service area. Rama likes to use his AR/VR-Game application during office-breaks while at the office. Krishna mostly uses his streaming service during office-breaks while at the office. Both use their streaming service application most after office hours when at home.
+
+- Rama (UE1) and Krishna (UE2) have subscriptions to applications VPN, AR/VR-Game and a streaming service.
+- Rama has his preference profiles set in the following order:
+
+Rama's UE Application Preference Profile Setting
+
+| Profile | Time of Day, Day | Location | Preference-1 | Preference-2 | Preference-3 |
+|--------------|-----------------------|----------|-------------------|--------------|-------------------|
+| Work Profile | 9-5 Work Day Setting | Office | VPN | AR/VR-Game | Streaming service |
+| | Rest of the Time/Days | Any | Streaming Service | AR/VR-Game | VPN |
+
+| | | | | | |
+|-----------------|-----------------------|------|-------------------|-------------------|------------|
+| WFH Profile | 9-5 WFH Day Setting | Home | VPN | Streaming Service | AR/VR-Game |
+| | Rest of the Time/Days | Any | Streaming Service | AR/VR-Game | VPN |
+| Default Profile | Any | Any | Streaming Service | AR/VR-Game | VPN |
+
+- Krishna does not have his preference pre-set, however it is established by the 5G System based on his usage pattern in below order:
+
+Krishna's Application Preference Setting derived by 5G System
+
+| Time of Day | Location | Preference-1 | Preference-2 | Preference-3 |
+|-----------------------|----------|-------------------|-------------------|--------------|
+| 9-5 Work Days | Office | VPN | Streaming Service | AR/VR-Game |
+| Rest of the Time/Days | Any | Streaming Service | VPN | AR/VR-Game |
+
+### 5.8.3 Service Flows
+
+For a normal working day at the office, Rama's UE selects slice M and Krishna's UE selects slice N based on their preferences.
+
+
+
+The diagram illustrates the network slice preferences for Rama and Krishna during workdays. It is divided into two horizontal layers representing network slices: FR2 (top) and FR1 (bottom). The x-axis represents location, with 'Home' on the left and 'Office' on the right, separated by a vertical dashed line.
+
+- FR2 Slice (Slice N):** Represented by a blue oval. It contains a yellow box labeled 'VPN' and a pink box labeled 'AR/VR-Game'. Above the slice, a blue box labeled 'RAMA' lists 'VPN' and 'AR/VR-Game' as preferences.
+- FR1 Slice (Slice M):** Represented by a green oval. It contains a yellow box labeled 'VPN' and a green box labeled 'Streaming Service'. Above the slice, a dashed box labeled 'KRISHNA' lists 'VPN' and 'Streaming App' as preferences.
+
+The diagram shows that Rama's UE selects Slice N (FR2) and Krishna's UE selects Slice M (FR1) based on their preferences during workdays.
+
+Diagram illustrating network slice preferences for Rama and Krishna during workdays. The diagram shows two network slices, Slice N (FR2) and Slice M (FR1), across two locations: Home and Office. Rama's preferences are shown in a blue box above Slice N, and Krishna's preferences are shown in a dashed box above Slice M. Slice N contains VPN and AR/VR-Game, while Slice M contains VPN and Streaming Service.
+
+**Figure 5.8.3-1: Applications preferred network slices for Rama and Krishna during Workdays (Working Hours)**
+
+Both return to their homes after office hours. Both Rama's UE and Krishna's UE select slice M based on their preferences.
+
+
+
+This diagram illustrates the preferred network slices for two users, Rama and Krishna, during their evenings (off-working hours). The vertical axis represents two frequency ranges, FR1 and FR2. The horizontal axis represents two locations: Home and Office, separated by a dashed vertical line.
+
+- FR2:** Represented by a blue oval labeled "Slice N". At the "Home" location, there is a yellow box labeled "VPN". At the "Office" location, there is a pink box labeled "AR/VR-Game".
+- FR1:** Represented by a green oval labeled "Slice M". At the "Home" location, there is a yellow box labeled "VPN". At the "Office" location, there is a green box labeled "Streaming Service".
+
+On the left side, two boxes represent the users and their applications:
+
+- RAMA:** Contains "VPN" and "Streaming App".
+- KRISHNA:** Contains "VPN" and "Streaming App".
+
+Figure 5.8.3-2: Applications preferred network slices for Rama and Krishna during Evenings (off-Working Hours).
+
+**Figure 5.8.3-2: Applications preferred network slices for Rama and Krishna during Evenings (off-Working Hours)**
+
+During a WFH Day for Rama, he changes his profile setting to use 'WFH Profile'. While Krishna goes to office as usual. Rama's UE stays on slice M instead of switching to Slice N while Krishna's UE selects slice M as usual at the office.
+
+
+
+This diagram illustrates a scenario where Rama is working from home (WFH) and Krishna is on a normal work day. The vertical axis represents two frequency ranges, FR1 and FR2. The horizontal axis represents two locations: Home and Office, separated by a dashed vertical line.
+
+- FR2:** Represented by a blue oval labeled "Slice N". At the "Home" location, there is a yellow box labeled "VPN". At the "Office" location, there is a pink box labeled "AR/VR-Game".
+- FR1:** Represented by a green oval labeled "Slice M". At the "Home" location, there is a yellow box labeled "VPN". At the "Office" location, there is a green box labeled "Streaming Service".
+
+On the left side, two boxes represent the users and their applications:
+
+- RAMA:** Contains "VPN" and "Streaming App".
+- KRISHNA:** Contains "VPN" and "Streaming App".
+
+Figure 5.8.3-3: WFH Scenario for Rama and normal work day for Krishna.
+
+**Figure 5.8.3-3: WFH Scenario for Rama and normal work day for Krishna.**
+
+Once, both Rama and Krishna meet at a conference and become friends. Rama invites Krishna to join him to play an AR/VR game during office-breaks. Krishna accepts the invitation and subsequently starts playing the AR/VR game during office-breaks instead of watching his streaming service. Initiating the AR/VR-Gaming application triggers Krishna's UE to use the least preferred application during his office breaks and causes it to (re)select a cell offering Slice N
+
+
+
+Figure 5.8.3-4: Slice Switch Triggered for Krishna due to AR/VR-Game usage. The diagram shows two frequency bands, FR1 and FR2, and two locations, Home and Office. In FR1 (Home), Slice M contains a VPN, Krishna (Streaming App), and a Streaming Service. In FR2 (Office), Slice N contains a VPN, Rama (AR/VR-Game), Krishna (AR/VR-Game), and an AR/VR-Game. An arrow points from the Krishna box in Slice M to the Krishna box in Slice N, indicating a slice switch triggered by AR/VR-Game usage.
+
+**Figure 5.8.3-4: Slice Switch Triggered for Krishna due to AR/VR-Game usage**
+
+The 5G System now derives/updates the new preference for Krishna based on AR/VR-Game Usage during office breaks.
+
+**Krishna's Preference Setting derived by 5G System**
+
+| Time of Day | Location | Preference-1 | Preference-2 | Preference-3 |
+|-----------------------|----------|-------------------|--------------|-------------------|
+| 9-5 Work Days | Office | VPN | AR/VR-Game | Streaming Service |
+| Rest of the Time/Days | Any | Streaming Service | VPN | AR/VR-Game |
+
+### 5.8.4 Post-conditions
+
+Both Rama and Krishna are able to access their preferred application(s) in a timely and efficient manner.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice.
+
+Establishing UE usage patterns based on time/date/location is supported by TS 23.503 [3].
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR.5.8.6-1] The 5G system shall support a mechanism for a UE to select and access network slice(s) based on UE capability, ongoing application, radio resources assigned to the slice, and policy (e.g., application preference).
+
+[PR.5.8.6-2] The 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs.
+
+## 5.9. Regionally different resources for network slices
+
+### 5.9.1 Description
+
+Installation of radio equipment needs a lot of work to be done. Thus, typically, even if an operator owns a certain radio frequency nationally, the operator may gradually deploy radio equipment one region by one region, expanding coverage
+
+gradually. As a result, even if some network slice, for example, such as a slice for IMS service is provided nationally, the used frequency band for that network slice may be different per different areas.
+
+### 5.9.2 Pre-conditions
+
+Figure 5.9.2-1 shows the use case scenario where network slices use different radio resources for different areas.
+
+
+
+The diagram illustrates the initial condition of network slices and User Equipment (UE) across different geographic areas (GA, GD, GB, GC) and frequency bands (F1, F2). The Y-axis represents Frequency (Freq) with labels F1 and F2. The X-axis represents Location with labels GA, GD, GB, and GC.
+ - Slice M (light blue oval) is shown covering areas GA, GD, and GB at frequency F1.
+ - Slice N (yellow oval) is shown covering area GA at frequency F1 and area GB at frequency F2.
+ - UE A1 and A2 are located at GA, associated with Slice M.
+ - UE A3 is located at the boundary between GA and GD, associated with Slice N.
+ - UE A4 is located at GA, associated with Slice N.
+ - Dashed arrows indicate movement or coverage: from GA towards GB for Slice M, and from GA towards GB for Slice N.
+
+Figure 5.9.2-1 Initial condition: A graph showing Frequency (Freq) on the Y-axis and Location on the X-axis. The Y-axis has labels F1 and F2. The X-axis has labels GA, GD, GB, and GC. The diagram illustrates network slices (Slice M, Slice N) and User Equipment (UE) locations (A1, A2, A3, A4) across different areas. Slice M is shown as a light blue oval, and Slice N as a yellow oval. Areas GA, GD, GB, and GC are marked on the X-axis. UE A1 and A2 are at GA, UE A3 is at GD, and UE A4 is at GA. Arrows indicate movement or coverage areas for the slices and UEs.
+
+**Figure 5.9.2-1 Initial condition**
+
+In this figure, it is assumed that
+
+- Subscription and configuration:
+ - UE A1 has a subscription to slice M.
+ - UE A2, A3 and A4 have subscription to slice N.
+- Deployment:
+ - F1 is used at all areas. F2 is available only at area around GB, e.g. in a highly populated area.
+ - Due to high demand of applications related to Slice N, at area around GB, frequency F2 is dedicated to serve the network slice N, and F1 is dedicated to serve other network slices such as network slice M.
+
+### 5.9.3 Service Flows
+
+Following is service flow for UE A1 and A2 which move from area GA to area GC:
+
+- UE A1 and A2 are serviced with network slices over F1 at area GA.
+- UE A1 continues to be serviced with network slice M over F1 toward area GB. Because F1 at area GB does not support slice N, the network moves the UE A2 to F2 to provide service continuity for network slice N from area near GD. While the frequency used for Slice N changes, the service interruption to applications over Slice N is minimized.
+- UE A1 continues to be serviced with network slice M over F1 toward area GC. UE A2 moves back to F1 to get network slice N from as the UE moves along from GB to GC. While the frequency used for Slice N changes, the interruption to application over Slice N is minimized.
+
+Following is service flow for UE A3 which is stationary at area GD:
+
+- UE A3 is located at the boundary area where the used frequencies for a network slice N differ. To prevent unnecessary power consumption, service interruption and increased signaling, frequency change between F1 and F2 needs to be minimized, when the UE A3 is serviced with network slice N.
+
+Following is a service flow for UE A4 which moves from area GA to area GB:
+
+- UE A4 is serviced with network slice N over F1 at area GA. When application ends, the user of UE A4 switches off the UE A4.
+- While the UE A4 is switched off, the user moves from the area GA to the area GB.
+
+- When the user arrives at the area GB, the user turns on the UE A4 and starts finds cells, beginning with F1 which is the last used frequency.
+- The UE A4 finds out that F1 does not support Slice N. In the end, the UE access cells on F2 and gets service for network slice N over F2 at area GB.
+
+### 5.9.4 Post-conditions
+
+Following figure 5.9.4-1 shows the status at the end of service flow.
+
+
+
+Figure 5.9.4-1 End result: A diagram showing network slices and user equipment (UE) across different frequencies and locations. The vertical axis is labeled 'Freq' with markers for F1 and F2. The horizontal axis is labeled 'Location' with markers for GA, GD, GB, and GC. At GA, there is a yellow oval labeled 'Slice M, N'. At GD, there is a yellow oval labeled 'Slice N' containing UE A4 and A3. At GB, there is a light blue oval labeled 'Slice M' containing UE A2 and A1. At GC, there is a yellow oval labeled 'Slice M, N' containing UE A1 and A2. Dashed lines with arrows show the movement of UEs: A4 from GD to GA, A3 from GD to GA, A2 from GD to GB, A1 from GB to GC, and A2 from GB to GC.
+
+Figure 5.9.4-1 End result
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+Following are service requirements that can be drawn out of service description in previous sections and that can be supported with existing specifications:
+
+- 3GPP shall support the same network slice to be configured over different frequencies at different areas.
+- 3GPP shall support service continuity for a network slice at the boundary where radio resources configured for the network slice change, for a UE in Connected mode.
+
+However, the existing specification does not yet provide specific means when the UE moves between different regions in Idle mode.
+
+- 3GPP shall support to minimize the time that takes for a UE to be able to access radio resource configured for a network slice when the used radio resources for the network slice change e.g. during mobility, power cycle.
+
+Following service requirements may be supported with existing specifications:
+
+- 5G system shall support a mechanism to minimize service interruption for a UE when different radio resources are configured for a network slice in different geographical areas and when the UE crosses the geographic area boundaries.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+No new requirement is derived from this use case.
+
+## 5.10. Isolation of resource for network slice
+
+### 5.10.1 Description
+
+Due to various sources and ways to gain right to use specific frequency resources, even within a continuous frequency range, different blocks of frequency within the range can be restricted to different purposes.
+
+Also, based on the requirements on the levels of isolation and security, access by a network slice beyond the authorized blocks should not occur, even if the frequency blocks are adjacent.
+
+### 5.10.2 Pre-conditions
+
+Figure 5.10.2-1 shows the use case scenario where frequency band are partitioned into multiple subbands.
+
+
+
+The diagram illustrates the initial condition of a network slice deployment. On the left, four User Equipment (UE) icons are shown: A1 (light blue), A2 (yellow), A3 (orange), and A4 (light blue). A vertical axis on the left is labeled 'Freq' and has markers for F1, Fa, Fb, and F2. The frequency band from F1 to F2 is divided into three subbands: Subband 1 (F1 to Fa), Subband 2 (Fa to Fb), and Subband 3 (Fb to F2). These subbands are used for three network slices: Slice O (orange, bottom), Slice N (yellow, middle), and Slice M (light blue, top). A dashed line connects the slices to a radio tower icon on the right, indicating the network infrastructure.
+
+Figure 5.10.2-1 Initial condition diagram showing frequency bands and network slices.
+
+**Figure 5.10.2-1 Initial condition**
+
+In this figure, it is assumed that
+
+- Subscription:
+ - UE A1 and A4 have subscription to slice M, and this slice M is optimized e.g. for IoT type of application.
+ - UE A2 and A4 have subscription to slice N, and this slice N is optimized e.g. for eMBB type of application.
+ - UE A3 has subscription to slice O, and this slice O is optimized e.g. for URLLC. The users or application providers request isolation of radio resources used for this network slice.
+- Deployment:
+ - The cell is configured to use frequency band which is from F1 to F2.
+ - The frequency band is sub-divided into three subbands. The allocated frequency for the first subband spans from F1 to Fa. The allocated frequency for the second subband spans from Fa to Fb. The allocated frequency for the third subband spans from Fb to F2.
+ - The first subband is used for slice O. The second subband is used for slice N. The third subband is used for slice M. in addition, third subband can be used for common procedure, e.g. SIB.
+
+### 5.10.3 Service Flows
+
+Following is service flow for UE A1, A2, A3 and A4:
+
+- After power-on, UE A1, A2, A3 and A4 camp on a cell, where the subscribed slices can be provided. Because the UEs are accessing the same cell supporting at least one of the subscribed network slices, there is no need for the UEs to move to other cells.
+- When applications start, UE A1 transmits and receives data over Slice M, which is restricted to subband 3.
+- When applications start, UE A2 transmits and receives data over Slice N, which is restricted to subband 2.
+- When applications start, UE A3 transmits and receives data over Slice O, which is restricted to subband 1.
+- When applications start, UE A4 transmits and receives data. For traffic configured to use Slice M, the transmission and reception is performed using radio resources within subband 3. For traffic configured to use Slice N, the transmission and reception is performed within radio resources within subband 2. Due to isolation requirement or service agreement for the network slice, traffic for Slice M is not transported over subband 2. Similarly, traffic for Slice N is not transported over subband 3.
+
+- As demands for the network slice changes according to the number of UEs for the network slice or time of the day, the network adjusts the allowed frequency range of each network slice. There is no recognized impact to the user experience.
+
+### 5.10.4 Post-conditions
+
+Following figure 5.10.4-1 shows the status at the end of service flow.
+
+For the transport of user traffic, each UE may use different part of frequencies of the cells, which corresponds to the configured frequency range for each network slice.
+
+
+
+Figure 5.10.4-1 End result: A diagram illustrating the end result of network slicing. On the left, a vertical axis represents frequency (req) with markers F1, Fa, Fb, and F2. A vertical bar labeled 'Freq-Band' is divided into three sub-bands: 'Subband 1' (between F1 and Fa), 'Subband 2' (between Fa and Fb), and 'Subband 3' (between Fb and F2). Four user equipment (UE) icons are shown: A1 (light blue) is associated with Subband 3; A4 (yellow) is associated with Subband 2; A2 (yellow) is associated with Subband 1; and A3 (orange) is associated with Subband 1. To the right, three stacked rectangular boxes represent network slices: 'Slice M' (light blue) at the top, 'Slice N' (yellow) in the middle, and 'Slice O' (orange) at the bottom. Dashed lines connect each slice to its corresponding sub-band: Slice M to Subband 3, Slice N to Subband 2, and Slice O to Subband 1. On the far right, a radio tower icon is shown with dashed lines connecting it to the slices, indicating the network infrastructure.
+
+Figure 5.10.4-1 End result
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+Following service requirements are already supported by current specifications:
+
+- *3GPP system shall provide means to support flexibility in configuring the allowed or restricted radio resources for a network slice.*
+- *3GPP system shall support for a network slice to use specific portion of the radio resources (e.g. frequency range) within a cell.*
+- *3GPP system shall be able to allow or disallow user traffic for a network slice to be multiplex with the user traffic for other network slice, based on the security and isolation requirement of the network slice.*
+
+BWP (Bandwidth Part) operation defined in TS38.300 [4] does not provide a UE with the support for providing different network slices on different frequency bands, when the UE is authorized to use multiple network slices.
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+Following new requirements can be derived from this use case:
+
+[PR.5.10.6-1] 5G system shall be able to minimize service interruption when configured radio resource (e.g. frequency range) for a network slice changes.
+
+## 5.11. Interaction with Third party for network slice
+
+### 5.11.1 Description
+
+A network slice can be provided and customized based on the request of customers. For example, an application provider may want a dedicated network slice for its application and may expand or decrease the capacity of the network slices based on the dynamic demand for the application.
+
+In other scenario, the third party itself may get and have right to use a specific frequency band. For example, by applying for local spectrum license, third party itself may own the right to use some frequency band and this frequency band can be used for a network slice and UEs dedicated to this third party.
+
+### 5.11.2 Pre-conditions
+
+Application provider AP1 has a service agreement with operator OP1. With this service agreement, OP1 creates and runs a network slice NSz, which is dedicated for AP1. AP1 provides application App1 to its customers and this application requires very demanding QoS. Traffic generated for the application App1 are transported via NSz. Initially, frequency band FB1 with size of 50 MHz are allocated for NSz.
+
+There is another application provider AP2, which also has a service agreement with operator OP1. With this service agreement, OP1 creates and runs a network slice NSy, which is dedicated for AP2. AP2 provides application App2 to its customers and the QoS requirement for this application is not stringent. Thus, instead of using a licensed spectrum, application provider AP2 requests the OP1 to provide network slice NSy over unlicensed spectrum, which is frequency band UFB1.
+
+### 5.11.3 Service Flows
+
+Following is service flow for application provider AP1:
+
+- UEs using App1 transmit data over frequency band FB1.
+- As the App1 gets popular, the application provider decides to increase capacity for the network slice NSz. The application provider requests the operator OP1 to increase the dedicated frequency bandwidth.
+- The OP1 adjusts its 3GPP system so that additional frequency band is dedicated to support the network slice NSz.
+- Later, the application provider identifies that there is a periodicity in the usage pattern for its application. I.e., some specific time period during the day, there is a small demand for its application. So, the application provider requests to reduce the allocated frequency bandwidth for network slice NSz for a specific time period.
+- The OP1 takes into account the information from the application provider, and reduce the size of dedicated frequency during the time period.
+- Later, the application provider itself gets a right to use some specific frequency band FB2 at a certain location from authorities.
+- The application provider requests the OP1 to additionally use FB2 for network slice NSz. OP1 updates configuration for network slice NSz. From this point, OP1 keeps record usage of network slices per used frequency bands.
+
+Following is service flow for application provider AP2:
+
+- Application provider requests OP1 to create network slice NSy using unlicensed frequency band UFB1.
+- When there is a user traffic for App2, the traffic is delivered over frequency band UFB1.
+- For a UE subscribes to both App1 and App2, traffic for app2 is delivered through NSy over UFB1 while traffic for app1 is delivered over other frequency bands.
+
+### 5.11.4 Post-conditions
+
+The UEs using App1 are served with NSz over FB2.
+
+The UEs using App2 are served with NSy over UFB1.
+
+### 5.11.5 Existing features partly or fully covering the use case functionality
+
+Following are existing requirements specified in TS 22.261 [2]:
+
+- *Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to manage this trusted third-party owned application(s) in the operator's Service Hosting Environment.*
+- *Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to scale a network slice used for the third-party, i.e. to adapt its capacity.*
+
+- *The 5G network shall provide suitable APIs to allow a trusted third-party to get the network status information of a private slice dedicated for the ' party, e.g. the network communication status between the slice and a specific UE.*
+- *Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.*
+- *Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party.*
+- *Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.*
+- *Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.*
+
+*Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a UE to a network slice used for the third-party.*
+
+- *Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party.*
+- *Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a service to a network slice used for the third-party.*
+
+These existing requirements allow interaction between the third party and the 5G system. However, these requirements do not fully address the service flow in previous section:
+
+- Existing requirements focused on the capability of the network slice, and not on the details of configuration, e.g. using specific resources owned by third party.
+- Existing requirements do not address restriction that can be set by third party, in using network slice.
+
+### 5.11.6 Potential New Requirements needed to support the use case
+
+Following new potential requirements can be derived from this use case:
+
+[PR.5.11.6-1] In case a third party has requested provision of a network slice using specific radio resources for the network slice, 5G system shall be able to generate charging information regarding the used radio resources e.g. used frequency bands.
+
+## 5.12. Broadcast for network slice
+
+### 5.12.1 Description
+
+For a flexible and dynamic management, a network slice used for broadcast services can be provided over a dedicated frequency band. For example, in a specific frequency band or in a specific region, only sessions for broadcast can be allowed while all other unicast sessions are not allowed. This may trigger various deployment scenarios where third parties such as broadcasters may create their own network slices and the mobile operator packs these network slices into a specific dedicated frequency band.
+
+Typically, for broadcast service, all or most traffic flows in downlink direction only. This characteristic may fit well to some frequency spectrum allocation and can increase utilization ratio of frequency spectrum.
+
+### 5.12.2 Pre-conditions
+
+An operator OPM owns a bunch of spectrum. One of the spectrum is FB1, and this is an unpaired spectrum, e.g. downlink only spectrum. The other spectrum is FB2 and this spectrum supports both downlink and uplink.
+
+OPM decides to dedicate spectrum FB1 for broadcast service slices. Because, services over broadcast service slices are broadcast/multicast service which does not generates UL traffic. For example, TV service is best suited for this broadcast service slice.
+
+The operator OPM also provides network slices for unicast traffic services, and this network slices are configured to use frequency band FB2, because FB2 is a paired spectrum which supports both UL traffic and DL traffic.
+
+With OPM, a UEa has a subscription for the broadcast service slice, and also for a unicast traffic service slice. This UEa does not support simultaneous operation over FB1 and FB2 due to capability limitation. Thus, while the UE engaged in the broadcast service slice, the QoS over a unicast service slice may degrade or may stop.
+
+### 5.12.3 Service Flows
+
+Following is service flow for this use case:
+
+- User of UEa starts browsing internet contents. The internet traffic for the browsing is transported over unicast network slices, which is configured to use FB2.
+- The user discovers that a famous TV show is ongoing and he/she has a subscription for that. The user launches a TV application, which uses broadcast service slice. Now, the user does not use browsing application anymore because the user now watches TV service.
+- Because the broadcast service slice is provided over FB1, the UEa tunes to that frequency band.
+- The UEa starts to receive traffic for TV show via the broadcast service slice.
+- While the user is watching the TV show delivered over broadcast service slice, an incoming call is notified. From the phone number information, the user identifies it as a Robocall and decides not to take the call. In this step, i.e., while the UEa is engaged in the notification procedure of incoming call, the quality of experience of broadcast service slice is not degraded. I.e., there is no noticeable interruption of TV show.
+- Later, a friend of the user makes a phone call to the user. An incoming call is notified to the user who is in the middle of watching a TV program.
+- Once the user decides to take the phone call, the UEa may suspend TV application. I.e, the use of broadcast slice is suspended.
+
+### 5.12.4 Post-conditions
+
+The user ends TV reception and starts voice call with his/her friend.
+
+### 5.12.5 Existing features partly or fully covering the use case functionality
+
+Following are existing requirements specified in TS 22.261 [2]:
+
+- *The 5G system shall enable a UE to be simultaneously assigned to and access services from more than one network slice of one operator.*
+- *Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network.*
+
+These existing requirements specify the case where the UE access simultaneous access multiple network slices. However, the assumption here is that the UE can support multiple frequency spectrum simultaneously. If the UE cannot support multiple frequency bands and if each frequency band supports different network slices, the UE cannot simultaneously use network slices on different frequencies. For this UE, the UE can use multiple network slices only when the network slices are on the same frequencies.
+
+In the service flow in the previous section, the UE has limited capability so that the UE cannot support simultaneous reception/transmission on multiple frequency bands. And, this has not been addressed by existing service requirements.
+
+The ability for a 3rd party to configure a network slice is already supported in TS 22.261 [2], including configuring the direction (e.g., uplink only, downlink only, both) of supported traffic.
+
+Similarly, requirements to avoid interference between network slices are already included in TS 22.261 [2].
+
+- *Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network.*
+
+### 5.12.6 Potential New Requirements needed to support the use case
+
+N/A
+
+## 5.13. Relaying and backhauling data for a network slice
+
+### 5.13.1 Description
+
+Relay nodes can be used to provide extended coverage for a UE located in area where radio signal from radio access network is weak. Also, relay nodes can be used to reduce power consumption of UEs. When a user traffic generated by a UE is relayed by relay nodes, the radio resources used between the relay nodes and gNB can be different from the radio resource used between the relay nodes and the UEs.
+
+In most cases the relay node is more capable than the UE. E.g., it can support more different frequency ranges or support simultaneous use of different frequency bands.
+
+### 5.13.2 Pre-conditions
+
+Figure 5.13.2-1 shows the use case scenario where there are two possible frequency bands between the UEs, the intermediate nodes and gNBs.
+
+
+
+The diagram illustrates the initial condition for relaying and backhauling data. A vertical axis on the left is labeled 'Freq' with two horizontal dashed lines representing frequency bands F1 and F2. At the F1 level, there are two yellow rectangles labeled 'A1' and 'A2' (UEs) and a white rectangle labeled 'R2' (intermediate node) inside a dashed oval. At the F2 level, there is a white rectangle labeled 'R1' (intermediate node) inside a dashed oval. All three nodes (R1, R2, and the UEs A1/A2) have lines connecting them to a central antenna icon labeled 'A' (gNB). From node 'A', two lines branch out to ovals labeled 'Slice N' (yellow) and 'Slice M' (blue).
+
+Figure 5.13.2-1 Initial condition diagram showing a frequency axis (Freq) with two bands, F1 and F2. UE A1 and A2 are shown near F1. Intermediate node R1 is shown near F2, and intermediate node R2 is shown near F1. Both R1 and R2 are connected to a central node A (gNB). Node A is connected to two network slices: Slice N (yellow oval) and Slice M (blue oval).
+
+Figure 5.13.2-1 Initial condition
+
+In this figure, it is assumed that
+
+- UEs and intermediate nodes:
+ - UE A1 and A2 have subscription to slice N.
+ - R1 and R2 are intermediate nodes. These intermediate nodes can be IAB-nodes. Both are authorized to relay traffic for any network slice.
+ - Intermediate node R1 is configured to use F2 toward UEs, while intermediate node R2 is configured to use F1 toward UEs. The link between the intermediate node R1/R2 and NG-RAN can use either F1 or F2 or both.
+ - UE A1 is within coverage of R1 and UE A2 is within coverage of R2.
+- Deployment:
+ - Slice N is configured to use Frequency F2.
+ - Slice M is configured to use Frequency F1.
+
+### 5.13.3 Service Flows
+
+Following is service flow for this use case:
+
+- The UE A1 and A2 are out of coverage. After power-on, these UEs start search for potential intermediate nodes.
+- Intermediate nodes R1 and R2 are operational. R1 provides connectivity service to UEs via F2 and R2 provides connectivity service to UEs on F1. Both are connected to gNB.
+- The UE A1 detects intermediate node R1 on frequency F2, and establishes connection toward R1. Because the network slice N is configured to use F2, the UE A1 transmits and receives user traffic of network slice N to/from the intermediate node R1 over frequency band F2. Because the link between R1 and NG-RAN is backhauling link, the user traffic for the UE A1 for the network slice N can be transported either F1 or F2 over the link between intermediate node R1 and gNB.
+- The UE A2 detects intermediate node R2 on frequency F1, and establishes connection toward R2. Because the network slice N is configured to use F2, the UE A2 does not transmit and receive user traffic of network slice N to/from the intermediate node R2.
+
+### 5.13.4 Post-conditions
+
+UE A1 is provided with network service for the network slice N.
+
+UE A2 is not provided with network service for the network slice N.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+Following are existing requirements specified in TS 22.261 [2]:
+
+- *The 3GPP system shall support selection and reselection of relay UEs based on a combination of different criteria e.g.*
+ - *the capabilities/capacity/coverage when using the relay UE,*
+ - *the QoS that is achievable by selecting the relay UE,*
+ - *the power consumption required by relay UE and remote UE,*
+ - *the pre-paired relay UE,*
+ - *the 3GPP or non-3GPP access the relay UE uses to connect to the network,*
+ - *the 3GPP network the relay UE connects to (either directly or indirectly),*
+ - *the overall optimization of the power consumption/performance of the 3GPP system, or*
+ - *battery capabilities and battery lifetime of the relay UE and the remote UE.*
+
+The existing requirement talks about the criterion that is used by a remote UE for relay selection. However, it does not describe the radio resource usage restriction or configuration. Though the service flow in the previous section discusses some aspect of relay selection, the focus is the radio resource restriction that can be put in place when relay functionality is used. The existing requirements do not clarify whether restriction on frequency resource for a network slice also applies in case the relay is used.
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+Following new requirements can be derived from this use case:
+
+[PR.5.13.6-1] For traffic pertaining to a network slice offered via a relay node, 5G system shall use only radio resources (e.g. frequency band) allowed for the network slice.
+
+NOTE: Allowed radio resources (e.g., frequency band) may be different for direct network connections (between UE and NG-RAN) than for backhaul connections (between the relay node and the NG-RAN).
+
+# --- 6 Consolidated Potential Requirements
+
+Following are consolidated potential requirements.
+
+n of the VPLMNs the UE is authorised to register to in order to use specific network slices.
+
+**Table 6-1. Consolidated Potential Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR-001 | For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall be able to support the UE to access the most suitable network slice in minimum time (e.g. based on the location of the UE, ongoing applications, UE capability, frequency configured for the network slice). | [PR.5.3.6-1] | |
+| CPR-002 | For a UE authorized to access to multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall minimize service interruption time when the UE changes the access from one network slice to another network slice. (e.g. based on changes of active applications). | [PR.5.3.6-2] | |
+| CPR-003 | 5G system shall minimize signaling exchange and service interruption time for a network slice, e.g. when restrictions related to radio resources change (e.g., frequencies, RATs). | [PR.5.4.6-1] | |
+| CPR-004 | For a roaming UE activating a service/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice. | [PR.5.5.6-1] | |
+| CPR-005 | The 5G system shall be able to generate charging information regarding the used radio resources e.g. used frequency bands. | [PR.5.11.6-1] | |
+| CPR-006 | The 5G system shall be able to minimize power consumption of a UE (e.g. reduce unnecessary cell measurements), in an area where no authorized network slice is available. | [PR.5.1.6-1] | |
+| CPR-007 | When a UE moves out of the service area of a network slice for an active application, the 5G system shall be able to minimize impact on the active applications (e.g., providing early notification).
NOTE 1: Various methods can be used to detect whether the UE moves toward the border area and to notify the UE. | [PR.5.2.6-1] | |
+| CPR-008 | The 5G system shall support a mechanism for a UE to select and access network slice(s) based on UE capability, ongoing application, radio resources assigned to the slice, and policy (e.g., application preference). | [PR.5.8.6-1] | |
+| CPR-009 | The 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs. | [PR.5.8.6-2] | |
+| CPR-010 | For traffic pertaining to a network slice offered via a relay node, 5G system shall use only radio resources (e.g. frequency band) allowed for the network slice.
NOTE 2: Allowed radio resources (e.g., frequency band) may be different for direct network connections (between UE and NG-RAN) than for backhaul connections (between the relay node and the NG-RAN). | [PR.5.13.6-1] | |
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR-011 | For UEs that have the ability to obtain service from more than one VPLMN simultaneously, the following requirements apply:
- - When a roaming UE with a single PLMN subscription requires simultaneous access to multiple network slices and the network slices are not available in a single VPLMN, the 5G system shall enable the UE to:
- - be registered to more than one VPLMN simultaneously; and
- - use network slices from more than one VPLMN simultaneously
- - The HPLMN shall be able to authorise a roaming UE with a single PLMN subscription to be registered to more than one VPLMN simultaneously in order to access network slices of those VPLMNs.
- - The HPLMN shall be able to provide a UE with permission and prioritisation information of the VPLMNs the UE is authorised to register to in order to use specific network slices.
NOTE 3: The above requirements assume certain UE capabilities, e.g. the ability to be connected to more than one PLMN simultaneously.
| [PR.5.6.6-1] | |
+
+# 7 Conclusions and Recommendations
+
+This document analyses a number of use cases to enhance the support of network slice. The resulting potential requirements have been consolidated in clause 6.
+
+It is recommended that the consolidated potential requirements identified in this TR are considered as the basis of normative requirements in order to better serve the communication services.
+
+
+
+# Annex A: Consideration for different type of frequency
+
+Frequency band defined in 3GPP can be classified into FDD frequency and TDD frequency as shown in Table 5.2-1 of TS 38.101-1 [5] and TS38.101-2 [6]. In case of TDD system, the same frequency is used for both UL and DL. However, in case of FDD system, UL frequency is different from DL frequency. Thus, when radio resource restriction scenario is discussed, care should be taken by considering these variations e.g. frequency used for both DL/ UL, UL only or DL only.
+
+In addition, 5G system introduces further flexibility in using frequency band. For example, SUL (Supplementary UL) and SDL (Supplementary DL) are frequency band either defined only in DL or only in UL, as described in annex B of TS 38.300 [4]. This spectrum is used to assist other frequency band, e.g. when base frequency band lacks coverage in either DL or UL, then SUL or SDL can be used to replace the base frequency band. If the SUL and/or SDL band is restricted for a certain network slice, some UEs may experience reduced coverage for the network slice.
+
+Aspects related to carrier aggregation also needs to be considered similarly, because it is used to support QoS requirement by using different combination of DL bands and UL bands, e.g. using three DL bands together with one UL bands to boost downlink data rate. If allowed network slices differs for different frequency bands, then operation of CA also needs to take this into account for a network slice.
+
+DSS (Dynamic Spectrum Sharing) allows use of same frequency band for both NR and E-UTRA, to cater for various deployment scenario of operators. Thus, same frequency band is split in time to support both E-UTRA and NR. Thus, when there is active restriction for a RAT in using a frequency, consideration should be given in which case it is restricted and any potential impact on quality of service.
+
+# Annex B: Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------|-----|-----------------------------------------------------------------------------|--|-------------|
+| Date | Meeting | TDoc | CR | Re v | Cat | Subject/Comment | | New version |
+| 2020-08 | SA1#91e | S1-203025 | | | | TR Skeleton | | 0.0.0 |
+| 2020-09 | SA1#91e | S1-203280
S1-203408
S1-203321
S1-203322
S1-203323
S1-203410
S1-203326
S1-203409 | | | | Incorporating agreed use cases and scope | | 0.1.0 |
+| 2020-11 | SA1#92e | S1-204409
S1-204410
S1-204310
S1-204311
S1-204312
S1-204411
S1-204088
S1-204313
S1-204314
S1-204412
S1-204018
S1-204316
S1-204317
S1-204318
S1-204315 | | | | Incorporating agreed use cases | | 0.2.0 |
+| 2021-02 | SA1#93e | S1-210417
S1-210416
S1-210418
S1-210027
S1-210419
S1-210420
S1-210421
S1-210422
S1-210423
S1-210424
S1-210425
S1-210053 | | | | Incorporating agreements of SA1#93e | | 0.3.0 |
+| 2021-03 | SA#91e | SP-210203 | | | | Presented for one-step approval to SA.
MCC clean-up | | 1.0.0 |
+| 2021-03 | SA#91e | SP-210203 | | | | Raised to v.18.0.0 following SA one-step approval | | 18.0.0 |
+| 2021-06 | SA#92e | SP-210508 | 0002 | | F | Clarification on charging requirement | | 18.1.0 |
+| 2021-06 | SA#92e | SP-210508 | 0001 | 1 | B | on Resolution of Editor's NOTE and consolidation of remaining requirements | | 18.1.0 |
+| 2021-06 | SA#92e | SP-210508 | 0003 | 1 | C | Clarification for simultaneous access to multiple slices on different PLMNs | | 18.1.0 |
+| 2021-06 | SA#92e | SP-210508 | 0004 | 1 | B | Update to the requirements of application-based preference | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0005 | | D | EASNS CPR mapping to PR(s) | | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22839/02db3d5ca2c08af069727d3709c4a6fb_img.jpg b/marked/Rel-18/22_series/22839/02db3d5ca2c08af069727d3709c4a6fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e1249972f891a7fa961839e7597ed21148eb422
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/02db3d5ca2c08af069727d3709c4a6fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b900f293c555dc88c28a7dcecb5b79fa4b9bb149d2144fc0ec7f3ad44bb9c98c
+size 60460
diff --git a/marked/Rel-18/22_series/22839/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/Rel-18/22_series/22839/098802c99831a6a7d445310d5e874e16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4deee2dbf0ca994893997f11472d756f0afb309
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/098802c99831a6a7d445310d5e874e16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bd6e0b5b8e605d259d201b90d66a6fe2524b9eabfc9d16e41568e1f37ca7f5e
+size 41375
diff --git a/marked/Rel-18/22_series/22839/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-18/22_series/22839/0b87abe67b21a93777287649c33e755d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..337dd01ceb15cef06b9621e1873ef53beddda4bb
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/0b87abe67b21a93777287649c33e755d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:931e1d2a8d86d47326bd1639ba2b538f1afebd3b3fb53aab100ab95420987115
+size 25588
diff --git a/marked/Rel-18/22_series/22839/187bba66c887c745c512add37a577c5e_img.jpg b/marked/Rel-18/22_series/22839/187bba66c887c745c512add37a577c5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..732e562a1af2b27060a5508614048d4afcb845ba
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/187bba66c887c745c512add37a577c5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bf0f113d455fe81d43b8049f2fe7044671e42af73f9bb46f74d65f097aa6ac8
+size 28069
diff --git a/marked/Rel-18/22_series/22839/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/22_series/22839/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea2753e3af34ae991a4ec1a78c79bffb39c46b73
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c7e2a411d73ecb5f1e722ea90ea81dca638d3dbf8c757405a35b2fc1df50aba8
+size 28629
diff --git a/marked/Rel-18/22_series/22839/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/22_series/22839/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1014572afa79f6610072de1ef4ad82aaace49df6
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e53edf9b480666c7e7def24cd7e1f5d1a33d3040cfd8c0ddfb10a09173195f1c
+size 27654
diff --git a/marked/Rel-18/22_series/22839/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/22_series/22839/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8de1870a9563527375391e50711290ad6fa4b51
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c66b111714e77e8030b410909ce16e8c855171d1de2f21a44697bcf81274648
+size 31089
diff --git a/marked/Rel-18/22_series/22839/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-18/22_series/22839/2eb23c2210154279f8013a1594fbcc5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eac232b3a8972a4c4280213ec737e1920169e728
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/2eb23c2210154279f8013a1594fbcc5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15a934c77ebc82a96f08fe3bb04974f7f4572510f4061f1ab35eb32c7d74c56d
+size 48575
diff --git a/marked/Rel-18/22_series/22839/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-18/22_series/22839/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c625bcfc3a16efb975de1328ee934c9ddf12f71
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e07c13b386f078161acb62fc97465413d589b6393d90c10b00d7844ca197cae3
+size 44736
diff --git a/marked/Rel-18/22_series/22839/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/Rel-18/22_series/22839/409498e57b1f988b2b604d12cd997002_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c3cb20df546f7488e93c920e0a755617eea34df
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/409498e57b1f988b2b604d12cd997002_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de841773095538e1586c64bb88bfd25caf10db57f9c00ba8bb1f777a2c04afa6
+size 28832
diff --git a/marked/Rel-18/22_series/22839/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-18/22_series/22839/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95d166086932916f19578bb200863056cb143b21
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:883bb9783418f15a7f1db494b31c87d9fb1ccd94ef9e5a79c5623e4d6abbf7ad
+size 25796
diff --git a/marked/Rel-18/22_series/22839/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-18/22_series/22839/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..732c8b70244a1514cce88397ced809f7ce18b6a4
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c77259d9e071b1c9ba1cc834e536222a4921727027fee482dd003e055543021
+size 28030
diff --git a/marked/Rel-18/22_series/22839/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22839/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b58c2a14419d7f330a961180894bd7b3e7c342e
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87e8c770d1db9fef4851faec34071c7b639ac3e9f5c3a15b82431bd15841873e
+size 9568
diff --git a/marked/Rel-18/22_series/22839/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22839/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1b714f6e5c4dc4989e452a0feba6b4f5f8ded5b
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f89fa5286297a3c17802a2f9cc9d7e91a9b45dbe470e876592f85717ebb328c
+size 7574
diff --git a/marked/Rel-18/22_series/22839/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-18/22_series/22839/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a9977ee15c71770b5bae768ad4372fa2d4734ef
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bbe666402a5edae47293ded8b59743b2a6351f8307c98acf9acbc4726ee8326
+size 31762
diff --git a/marked/Rel-18/22_series/22839/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/marked/Rel-18/22_series/22839/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03d13f9e62b50bd1e680727be3db73e44bde98a2
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e615e2c1184b6540b775d06cff4fde504f09c72d7e6416736f8d866d17a9c3e6
+size 27853
diff --git a/marked/Rel-18/22_series/22839/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/22_series/22839/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fcd01a09c1599470ed6c1e802e270acbdc12ef9f
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ee354b180a2a99d189cc57e383a590dd2284a452ef08498eb45f234b8d764d3
+size 28222
diff --git a/marked/Rel-18/22_series/22839/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/marked/Rel-18/22_series/22839/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6373265c0a3112395e48b8a90cc717b7e973c85f
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddeed395aa569044c9aa4dbaf8aaf6143f8c23653efc9855705343b1ee8380be
+size 28465
diff --git a/marked/Rel-18/22_series/22839/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-18/22_series/22839/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2aba436f82d8472b3aafa9258767b42a520f1d6d
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d57ecd615012d6449837d8c3dbbb3a0eaef5a062a40a6310b9c2794156d25e3f
+size 24007
diff --git a/marked/Rel-18/22_series/22839/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-18/22_series/22839/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f64bbcb327a9e69f97b96f2e3696c999ecf1c8ae
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80927f5a29c8f42fb29ee6e9513703ec07929d1155a6e1dc7697c0a696936d34
+size 27803
diff --git a/marked/Rel-18/22_series/22839/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-18/22_series/22839/933ecd14c858bf3fc919222d8e357bc8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97cb173a606998029b525f79cae31a3fd4c85f0d
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/933ecd14c858bf3fc919222d8e357bc8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7152ddfe04b24ca4e842c62317ea4a4f8a4c593d518513445fb36357f303ae41
+size 63932
diff --git a/marked/Rel-18/22_series/22839/a89d151b67109378baed0c117830cf78_img.jpg b/marked/Rel-18/22_series/22839/a89d151b67109378baed0c117830cf78_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23e337e4b54b1e93fc678dcd74fd43e9b88d2e3d
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/a89d151b67109378baed0c117830cf78_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d39d42a87c683cfe88755021070c6110395fd15bda43811792b2c5e64ccb825f
+size 51789
diff --git a/marked/Rel-18/22_series/22839/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-18/22_series/22839/adc59ed6840bcb2d392ea323abfccedc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a595939211014ed9e7dca8d618f103306a5a944
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/adc59ed6840bcb2d392ea323abfccedc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1e0276ec060e78c7aaefc15eb0c223b4a459d12b1654c2fb07894e6b5a4fe6d
+size 73773
diff --git a/marked/Rel-18/22_series/22839/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-18/22_series/22839/b5335262987c819d7f71ce40f99cb71b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..84751a6c5b42b847cea5876a34a047540e30edae
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/b5335262987c819d7f71ce40f99cb71b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e76a5991f0079325493fc09414eb5309e25c57266c33de4a76e889d9a088f427
+size 20341
diff --git a/marked/Rel-18/22_series/22839/b54ce9bffd341cd643e196d5f4538829_img.jpg b/marked/Rel-18/22_series/22839/b54ce9bffd341cd643e196d5f4538829_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2608bf36c5fb412e1f20d7eb83f2d97c0bff133a
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/b54ce9bffd341cd643e196d5f4538829_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e24f3a202c3afc7477e5cbad741f7eb01e8da4557d8c0f6dae4d375611d432c
+size 30922
diff --git a/marked/Rel-18/22_series/22839/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-18/22_series/22839/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2aa9b1e798f77c26c6ce873bdcf7c6b719a1794d
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d0bcdf693a190d04ff0915545ed35a03b23c6f3b827a0a46721562168151c2f
+size 30253
diff --git a/marked/Rel-18/22_series/22839/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Rel-18/22_series/22839/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35e12de70280b2372603732e9e5015be1e41343e
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f36fac0fa0b8ccab9a6a2bdda07c8104c3ffe6856ec35aabbf99deb5fe0edb6
+size 62540
diff --git a/marked/Rel-18/22_series/22839/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg b/marked/Rel-18/22_series/22839/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0fe365e0a0487697484ebfc94a893306710d3d33
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d370fb2f6f052b1be6c2cd6d7ee0be416c7c8f3907b4e21ebf429c0fe8a361da
+size 17328
diff --git a/marked/Rel-18/22_series/22839/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-18/22_series/22839/db5ab5d386827a5d5f5fad0f45612b90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..162f2fd7acc53a9ecbd75932ce5be716547f1353
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/db5ab5d386827a5d5f5fad0f45612b90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:394d05f30cb3d33d0bfe510d91c9dc215b417f1f887c03cb2d668d3a4b97d791
+size 16644
diff --git a/marked/Rel-18/22_series/22839/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/22_series/22839/dd5771673aececa53d42ece89218299d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b90b8a8179a2b3e303be32b713ee760e51de719
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/dd5771673aececa53d42ece89218299d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97930050dc5e2bab3379d03bda1968e06445ec54fb0e082d168097922c64c2b0
+size 27604
diff --git a/marked/Rel-18/22_series/22839/e58a867750e4ae01604318506b79df7a_img.jpg b/marked/Rel-18/22_series/22839/e58a867750e4ae01604318506b79df7a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12dc43694fac8399c8e961cffb44e11cdd89612b
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/e58a867750e4ae01604318506b79df7a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d266262d1e76e9ff6b6daa6e46aaec77f15a326e756b1cb50df05887767ef7b
+size 20616
diff --git a/marked/Rel-18/22_series/22839/e8fd6c2eaa1626c8421bcf4842b9be92_img.jpg b/marked/Rel-18/22_series/22839/e8fd6c2eaa1626c8421bcf4842b9be92_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ffcb9ce3078b82d87c88654d8158a552cdf259a1
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/e8fd6c2eaa1626c8421bcf4842b9be92_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18b229779ea59a6cdc80e1b1d7f68cd700a7e56422d3d97d40366e27a936ccac
+size 23202
diff --git a/marked/Rel-18/22_series/22839/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-18/22_series/22839/e90987faabad6a6665cd8ed1151dc474_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14cba078228415c909aa3f75c1c65b4912653968
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/e90987faabad6a6665cd8ed1151dc474_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6534a078155fb004cd60a20d98518c470d4bcb7df2567060bb731a82c65c20d
+size 17603
diff --git a/marked/Rel-18/22_series/22839/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-18/22_series/22839/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..824c8f69e0419290f519cf62faea8c0b070e3fe9
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16c3f44a062a6d49c486d18a58d8dfce29ee62ac375622503ef1472388f0bb89
+size 31948
diff --git a/marked/Rel-18/22_series/22839/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/22_series/22839/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33ec4168d012d2224a803cf516807ba5093a2740
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b79fb4aaa34ee789802638b06364f05b7827b4e89e7ad2d7190bdf692b5d6670
+size 25772
diff --git a/marked/Rel-18/22_series/22839/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-18/22_series/22839/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f991726fdf7a13813cbec17b04832d727f195938
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a410810cf5c37e635c5d2d05928a96336a219915b0dcbbcab9dd552cd12ab6b0
+size 17699
diff --git a/marked/Rel-18/22_series/22839/raw.md b/marked/Rel-18/22_series/22839/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..85bd07df35c55aeef127f4cb47890d88d2371c83
--- /dev/null
+++ b/marked/Rel-18/22_series/22839/raw.md
@@ -0,0 +1,2004 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Vehicle-Mounted Relays; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|----------------------------------------------------------------------------------------|----|
+| Foreword ..... | 7 |
+| 1 Scope..... | 8 |
+| 2 References..... | 8 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Overview..... | 9 |
+| 5 Use cases..... | 10 |
+| 5.1 Basic support, configuration and control of mobile relays ..... | 10 |
+| 5.1.1 Description ..... | 10 |
+| 5.1.2 Pre-conditions..... | 10 |
+| 5.1.3 Service Flows ..... | 10 |
+| 5.1.4 Post-conditions ..... | 11 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 11 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 11 |
+| 5.2 Authorization and configuration for mobile base station relay..... | 11 |
+| 5.2.1 Description ..... | 11 |
+| 5.2.2 Pre-conditions..... | 11 |
+| 5.2.3 Service Flows ..... | 12 |
+| 5.2.4 Post-conditions ..... | 12 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 12 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 12 |
+| 5.3 Multiple working modes of vehicle mounted base station..... | 12 |
+| 5.3.1 Description ..... | 12 |
+| 5.3.2 Pre-conditions..... | 13 |
+| 5.3.3 Service Flows ..... | 13 |
+| 5.3.4 Post-conditions ..... | 13 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 13 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.4 Control of UEs access via mobile relays..... | 14 |
+| 5.4.1 Description ..... | 14 |
+| 5.4.2 Pre-conditions..... | 14 |
+| 5.4.3 Service Flows ..... | 14 |
+| 5.4.4 Post-conditions ..... | 15 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 15 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 15 |
+| 5.5 Control of UEs access via mobile relays using application-based subscription ..... | 15 |
+| 5.5.1 Description ..... | 15 |
+| 5.5.2 Pre-conditions..... | 16 |
+| 5.5.3 Service Flows ..... | 16 |
+| 5.5.4 Post-conditions ..... | 16 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 16 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 16 |
+| 5.6 Keep connectivity via mobile base station relay..... | 16 |
+| 5.6.1 Description ..... | 16 |
+| 5.6.2 Pre-conditions..... | 17 |
+| 5.6.3 Service Flows ..... | 17 |
+| 5.6.4 Post-conditions ..... | 17 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 17 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 17 |
+| 5.7 Optimizing mobility for UEs..... | 18 |
+| 5.7.1 Description ..... | 18 |
+| 5.7.2 Pre-conditions..... | 18 |
+| 5.7.3 Service Flows ..... | 18 |
+| 5.7.4 Post-conditions ..... | 19 |
+
+| | | |
+|----------|-------------------------------------------------------------------------------------|----|
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 19 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 19 |
+| 5.8 | Load balancing for mobile base station relays..... | 19 |
+| 5.8.1 | Description ..... | 19 |
+| 5.8.2 | Pre-conditions..... | 19 |
+| 5.8.3 | Service Flows ..... | 20 |
+| 5.8.4 | Post-conditions ..... | 20 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 20 |
+| 5.9 | Provide location service to a UE attached to the relay mounted in the vehicle ..... | 21 |
+| 5.9.1 | Description ..... | 21 |
+| 5.9.2 | Pre-conditions..... | 21 |
+| 5.9.3 | Service Flows ..... | 21 |
+| 5.9.4 | Post-conditions ..... | 21 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 21 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 22 |
+| 5.10 | Incentives and charging..... | 22 |
+| 5.10.1 | Description ..... | 22 |
+| 5.10.2 | Pre-conditions..... | 22 |
+| 5.10.3 | Service Flows ..... | 22 |
+| 5.10.4 | Post-conditions ..... | 23 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 23 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 23 |
+| 5.11 | Use cases on Service continuity ..... | 23 |
+| 5.11.1 | Mobility between macro and relay..... | 23 |
+| 5.11.1.1 | Use case 1: User entering/leaving the vehicle ..... | 23 |
+| 5.11.1.2 | Use case 2: User outside the vehicle..... | 24 |
+| 5.11.2 | Mobility of relay between macro nodes..... | 26 |
+| 5.11.2.1 | Use case 1: User inside the vehicle..... | 26 |
+| 5.11.2.2 | Use case 2: User outside the vehicle..... | 28 |
+| 5.11.3 | Mobility between relays ..... | 29 |
+| 5.11.3.1 | Use case 1: User inside the vehicle..... | 29 |
+| 5.11.3.2 | Use case 2: User outside the vehicle..... | 31 |
+| 5.11.4 | Group UEs' service continuity ..... | 32 |
+| 5.11.4.1 | Description..... | 32 |
+| 5.11.4.2 | Pre-conditions ..... | 32 |
+| 5.11.4.3 | Service Flows..... | 33 |
+| 5.11.4.4 | Post-conditions..... | 33 |
+| 5.11.4.5 | Existing features partly or fully covering the use case functionality..... | 33 |
+| 5.11.4.6 | Potential New Requirements needed to support the use case..... | 33 |
+| 5.12 | Optimizing UE mobility from planned or predicted mobility information..... | 33 |
+| 5.12.1 | Description ..... | 33 |
+| 5.12.2 | Pre-conditions..... | 34 |
+| 5.12.3 | Service Flows ..... | 34 |
+| 5.12.4 | Post-conditions ..... | 34 |
+| 5.12.5 | Existing features partly or fully covering the use case functionality ..... | 35 |
+| 5.12.6 | Potential New Requirement needed to support the use case ..... | 35 |
+| 5.13 | Use of mobile relay as secondary node..... | 35 |
+| 5.13.1 | Description ..... | 35 |
+| 5.13.2 | Pre-conditions..... | 35 |
+| 5.13.3 | Service Flows ..... | 36 |
+| 5.13.4 | Post-conditions ..... | 37 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 37 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 37 |
+| 5.14 | Optimized relay for in-vehicle devices ..... | 38 |
+| 5.14.1 | Description ..... | 38 |
+| 5.14.2 | Pre-conditions..... | 38 |
+| 5.14.3 | Service Flows ..... | 38 |
+| 5.14.4 | Post-conditions ..... | 39 |
+| 5.14.5 | Existing features partly or fully covering the use case functionality ..... | 39 |
+| 5.14.6 | Potential New Requirements needed to support the use case..... | 39 |
+| 5.16 | Non-terrestrial coverage for Mobile Vehicular Relays ..... | 41 |
+
+| | | |
+|--------|------------------------------------------------------------------------------------------------------|----|
+| 5.16.1 | Description ..... | 41 |
+| 5.16.2 | Pre-conditions ..... | 41 |
+| 5.16.3 | Service Flows ..... | 41 |
+| 5.16.4 | Post-conditions ..... | 42 |
+| 5.16.5 | Existing features partly or fully covering the use case functionality ..... | 42 |
+| 5.16.6 | Potential New Requirements needed to support the use case..... | 42 |
+| 5.17 | Vehicle Relay sharing ..... | 42 |
+| 5.17.1 | Description ..... | 42 |
+| 5.17.2 | Pre-conditions ..... | 42 |
+| 5.17.3 | Service Flows ..... | 43 |
+| 5.17.4 | Post-conditions ..... | 43 |
+| 5.17.5 | Existing features partly or fully covering the use case functionality ..... | 43 |
+| 5.17.6 | Potential New Requirements needed to support the use case..... | 43 |
+| 5.18 | Monitoring of vehicle-mounted relays ..... | 43 |
+| 5.18.1 | Description ..... | 43 |
+| 5.18.2 | Pre-conditions ..... | 44 |
+| 5.18.3 | Service Flows ..... | 44 |
+| 5.18.4 | Post-conditions ..... | 44 |
+| 5.18.5 | Existing features partly or fully covering the use case functionality ..... | 44 |
+| 5.18.6 | Potential New Requirements needed to support the use case..... | 44 |
+| 5.19 | Simultaneous connectivity via multiple mobile BS relays..... | 45 |
+| 5.19.1 | Description ..... | 45 |
+| 5.19.2 | Pre-conditions ..... | 45 |
+| 5.19.3 | Service Flows ..... | 45 |
+| 5.19.4 | Post-conditions ..... | 46 |
+| 5.19.5 | Existing features partly or fully covering the use case functionality ..... | 46 |
+| 5.19.6 | Potential New Requirements needed to support the use case..... | 46 |
+| 5.20 | Using a partner 5G network to transport vehicle relay traffic..... | 46 |
+| 5.20.1 | Description ..... | 46 |
+| 5.20.2 | Pre-conditions ..... | 47 |
+| 5.20.3 | Service Flows ..... | 47 |
+| 5.20.4 | Post-conditions ..... | 47 |
+| 5.20.5 | Existing features partly or fully covering the use case functionality ..... | 47 |
+| 5.20.6 | Potential New Requirements needed to support the use case..... | 48 |
+| 5.21 | Improved connectivity based on the relay mobility pattern..... | 48 |
+| 5.21.1 | Description ..... | 48 |
+| 5.21.2 | Pre-conditions ..... | 49 |
+| 5.21.3 | Service Flows ..... | 49 |
+| 5.21.4 | Post-conditions ..... | 49 |
+| 5.21.5 | Existing features partly or fully covering the use case functionality ..... | 49 |
+| 5.21.6 | Potential New Requirements needed to support the use case..... | 49 |
+| 5.22 | Mobility between Non-terrestrial coverage and terrestrial coverage for Mobile Vehicular Relays ..... | 50 |
+| 5.22.1 | Description ..... | 50 |
+| 5.22.2 | Pre-conditions ..... | 50 |
+| 5.22.3 | Service Flows ..... | 50 |
+| 5.22.4 | Post-conditions ..... | 51 |
+| 5.22.5 | Existing features partly or fully covering the use case functionality ..... | 51 |
+| 5.22.6 | Potential New Requirements needed to support the use case..... | 51 |
+| 5.23 | Mobile Vehicular Relays using Non-terrestrial and terrestrial access simultaneously..... | 51 |
+| 5.23.1 | Description ..... | 51 |
+| 5.23.2 | Pre-conditions ..... | 51 |
+| 5.23.3 | Service Flows ..... | 51 |
+| 5.23.4 | Post-conditions ..... | 52 |
+| 5.23.5 | Existing features partly or fully covering the use case functionality ..... | 52 |
+| 5.23.6 | Potential New Requirements needed to support the use case..... | 52 |
+| 6 | Other considerations ..... | 53 |
+| 7 | Potential Consolidated Requirements ..... | 53 |
+| 7.0 | Introduction ..... | 53 |
+| 7.1 | General requirements ..... | 55 |
+| 7.2 | Multi-link connectivity..... | 56 |
+
+| | | |
+|-----|---------------------------------------|----|
+| 7.3 | Mobility ..... | 56 |
+| 7.4 | Charging ..... | 56 |
+| 7.5 | Other aspects ..... | 57 |
+| 8 | Conclusions and Recommendations ..... | 57 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document is the outcome of the study on use cases and potential new requirements for 5GS support of mobile base station relays mounted on vehicles, using 5G NR over the radio links toward UEs and macro RAN (connected to 5GC). This study covers aspects related to:
+
+- Vehicle base station relays providing service to UEs inside the vehicle or in the vicinity of the vehicle;
+- End-to-end service continuity during mobility scenarios (including mobility of the relays);
+- Provisioning, policies and control, e.g. for
+ - Provisioning of spectrum used by the relays, geographic area restrictions;
+ - Control of relay operation, UEs access and connectivity via relays.
+- Aspects related to roaming of relays, security, regulatory requirements (e.g. for emergency services), charging, spectrum interference.
+- Gap analysis between the identified requirements and existing 5GS requirements or functionalities.
+
+# 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 38.821: "Solutions for NR to support non-terrestrial networks (NTN)"
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+
+
+# 4 Overview
+
+Demand for improved 5G cellular coverage and connectivity continues to increase, which may be challenging in many outdoor and mobility scenarios. In some outdoor environments, the availability of vehicles equipped with mobile base station relays, either following a certain known/predictable itinerary (e.g. buses, trams, etc), or situated in convenient locations (e.g. outside stadiums, hot-spot areas, or emergency sites), could provide very opportunistic boost to cellular coverage and capacity when/where needed. Those relays, using 5G wireless backhaul toward the macro network, could indeed offer better 5G coverage and connectivity to neighbouring UEs. Vehicle relays are obviously very suitable also for improving connectivity for users or devices inside the vehicle itself, in different environments, e.g. for passengers in buses, car/taxi, or trains, ad-hoc/professional personnel or equipment. Yet other target scenarios are where vehicle relays can be used for reaching users or devices that would otherwise have no or very poor macro coverage, e.g. in case of first responders dislocated in indoor buildings/areas, using 5G relays placed on their nearby/outside vehicles to get required 5G coverage and connectivity.
+
+The technical benefits of using vehicle relays include, among others, the ability of the BS relay to get better macro coverage than a nearby UE, e.g. exploiting better RF/antenna and power capabilities. Besides the value for network operators and end users, worthy incentives could be found for other parties as well, e.g. for vehicles manufacturers, vehicle/fleet owners or providers, to install and operate relays in their vehicles.
+
+In the context of this TR, from a high-level 5G system point of view, the target scenarios include moving vehicles equipped with small on board base station (BS) relays providing 5G coverage and communication to UEs (inside the vehicle and/or in its vicinity), and connected wirelessly to the 5G network via RAN (donor) nodes.
+
+
+
+```
+graph TD; UE[UE] -- "Uu NR" --> MBSR["Mobile Base Station Relay (on vehicle)"]; MBSR -- "Uu NR" --> DRAN[Donor RAN]; DRAN --> 5GC[5GC];
+```
+
+Figure 4-1: Mobile base station relay - High level concept. The diagram shows a UE (User Equipment) connected to a Mobile Base Station Relay (on vehicle) via a Uu NR link. The Mobile Base Station Relay is connected to a Donor RAN via a Uu NR link. The Donor RAN is connected to the 5GC (5G Core Network).
+
+**Figure 4-1. Mobile base station relay - High level concept**
+
+As shown in the figure above, the main connectivity assumptions are:
+
+- 5G NR is used for the radio link between mobile BS relay and donor RAN node, as well as the radio link between BS relay and UE.
+- The mobile BS relay connects, via donor RAN node, to the 5G Core network (5GC).
+- Single-hop relay is the main/baseline scenario (multi-hop can be a possible option)
+
+The study intends to cover use cases of BS relays mounted on ground/land type of mobile vehicles; nevertheless, some potential requirements may be general (for a “mobile base station relay”), i.e. could apply to BS relays mounted on different types of moving vehicles or devices.
+
+NOTE 1: the above (logical) diagram and assumptions do not intend to limit nor preclude specific RAN and relay architecture, or topology options.
+
+NOTE 2: While the identified new service requirements target potential 5G system (UE and/or NW) enhancements, this should not prevent support (also) for legacy UEs.
+
+In the paragraphs that follow, next section (sec. 5) captures several identified use cases and new potential requirements, covering (among others): basic operation of vehicle relays, relay configuration, UE access control, optimized connectivity and mobility, load balancing, support of location services, QoS and charging, service continuity during mobility (between relay and macro, or among relays or when macro node changes), multi-connectivity, ad-hoc coverage and topologies (e.g. for public safety), RAN/relay sharing, satellite backhauling.
+
+In addition to those, section 6 covers further aspects and requirements, e.g. about support of roaming, regulatory requirements, emergency services, security, priority services.
+
+The two concluding sections (sec. 7 and 8) contain the list of consolidated new potential requirements, from all use cases, and the final TR recommendations.
+
+# --- 5 Use cases
+
+## 5.1 Basic support, configuration and control of mobile relays
+
+### 5.1.1 Description
+
+It's almost summertime, and a series of outdoor festivals and events are planned in town, for the next weeks/months. This is known to attract many people and tourists, using public/private transportation (bus, taxi) to travel from/to airport and move around the city, as well as attending various shows and events scheduled in different city parks, stadiums and other outdoor areas. 5G traffic demand will be very high and challenging.
+
+The city administration and few partner companies provide transportation services with various buses/taxis inside the city, as well as shuttles between the airport (located outside the city area) and hotels. In addition, one of the partner companies provides small vehicles/carts used to display marketing/advertisement messages/banners, that can be deployed to drive/transit inside parks, around stadiums or recreational/tourist areas.
+
+Those vehicles are (or can be) equipped with 5G mobile BS relays for inside/outside users and, upon request and/or specific commercial agreements, can be used and configurable by MNOs to interconnect and operate as part of their 5G RAN.
+
+### 5.1.2 Pre-conditions
+
+Operator A, with existing 5G macro coverage in/around the city, decides to acquire the service offered by the transport administration and use some of those vehicle relays, in particular:
+
+- advertisement carts, to extend challenging macro 5G coverage and capacity for outdoor users in hot-spot locations where city's events or high-density gatherings are expected.
+- buses and taxis, to provide a better 5G in-vehicle experience to its subscribers (or inbound roamers), as well as improving the overall RAN capacity in certain challenging macro areas, e.g. along the highway to the airport, and/or macro cells serving popular bus/taxi locations/routes in the city.
+
+### 5.1.3 Service Flows
+
+1. Operator A enables the vehicle relays to operate and interconnect with its 5G macro RAN and network.
+2. Operator A configures initial relays operating parameters and conditions, e.g. in terms of radio spectrum, vehicles location/itinerary, time of the day, transit/stop in target areas, vehicle speed, etc.
+3. On a certain day, prior to the events season, Operator A activates the relays.
+4. 5G traffic starts flowing through all activated vehicle relays. Operator A can re-configure some of the relay operating parameters (e.g. spectrum, time/location of operation) based on observed 5G traffic and RAN performance.
+5. Toward the end of the summer, based on lower 5G traffic demand, Operator A decides to deactivate relay operation (on its network) for the advertisement carts and few of the city taxis. Service on city buses and shuttles from/to airport is continued.
+
+Note: in some of the actions above, there may also be involvement of a 3rd party entity (e.g. vehicle or relay manufacturer/owner, or relay O&M company), to allow or help the operator A to (de)activate and/or configure certain relay settings.
+
+### 5.1.4 Post-conditions
+
+The operator A is very happy about the improved performance of its 5G network during the busy city summer, and the better service provided to its 5G customers.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.1-1] The 5G system shall support efficient operation of mobile base station relays, e.g. on board of mobile vehicles, connected wirelessly to the NG-RAN and serving nearby 5G NR UEs (inside and/or outside the vehicle).
+
+[PR 5.1-2] The 5G system shall support means, for a mobile network operator, to configure, provision and control the operation of a mobile base station relay, including
+
+- activation and/or deactivation of mobile relay operation;
+- configuration of 5G spectrum (licensed or unlicensed) used by the mobile relay, over the radio links toward UE and RAN;
+- configuration of relay operating conditions e.g. based on geographic areas or locations, specific time period(s), vehicle's speed, itinerary, etc.
+
+Note: besides the MNO, a 3rd party entity could also be enabled to provision and control some of the mobile base station relay operation, e.g. (de)activation, location restrictions, or other operating conditions.
+
+## 5.2 Authorization and configuration for mobile base station relay
+
+### 5.2.1 Description
+
+In the urban environment, temporary needs are raised up for extra cellular coverage and connectivity during various social events (e.g., music festival, sport race, etc.) at a designated area, where pertinent QoS cannot be fulfilled for a large amount of users. In this case, vehicles installed with on board base stations may act as relay and help to offer convenient and efficient service to UEs. They can be situated in specific locations (e.g. outside stadiums), and provide 5G coverage to neighbouring UEs outside the vehicles.
+
+
+
+The diagram shows a mobile base station (represented by a car with antenna icons) connected wirelessly to the Operator 5G Core Network (represented by a cloud). A User Equipment (UE) (represented by a smartphone icon) is connected wirelessly to the mobile base station. The mobile base station is also connected wirelessly to the Operator 5G Core Network. The entire setup is enclosed in a dashed box.
+
+Diagram illustrating the authorization and configuration for mobile base station relay. A mobile base station (car) is connected wirelessly to the Operator 5G Core Network. A User Equipment (UE) is connected wirelessly to the mobile base station.
+
+Figure 5.2-1: Authorization and configuration for mobile base station relay
+
+### 5.2.2 Pre-conditions
+
+To enable this use, following pre-conditions should be met:
+
+- A car shall be equipped with on-board base station.
+
+- The mobile base station relay is capable of providing 5G connectivity to UEs in the vicinity of the car.
+- The mobile base station relay is able to connect the NG-RAN and 5G Core network.
+
+### 5.2.3 Service Flows
+
+1. When the car starts the engine, the mobile base station relay registers to the 5G network and obtains the necessary configuration information (e.g., operating frequency bands). After getting authorized, the mobile base station relay is able to provide 5G access.
+2. The car drives into the permitted area, where the mobile base station relay is able to provide 5G access to neighbouring UEs in the vicinity of the cars.
+3. UE A is connected to the mobile base station relay when it moves into the permitted area.
+4. As the car moves out of the permitted area, the mobile base station relay cannot work anymore and UE A is disconnected.
+5. When the car drives into another permitted area, the mobile base station relay works again and UE B is connected.
+6. When the car reaches the destination, its engine is turned off and the mobile base station relay stops working automatically.
+
+### 5.2.4 Post-conditions
+
+The authorized UEs in the vicinity of the car are provided with extended 5G connectivity by the mobile base station relay.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.2-1] The 5G system shall support the use of mobile base station relays (e.g. mounted on vehicles), which can provide 5G access to its authorized UEs in the vicinity.
+
+[PR 5.2-2] The 5G system shall enable the authorization of the mobile base station relays (e.g. mounted on vehicles) to work in a permitted area. When the mobile base station relay moves out of this area, it is not allowed to work as a base station.
+
+[PR 5.2-3] The 5G network can dynamically configure the operation parameters of a mobile base station relay, such as frequency band, permitted geographical area, etc.
+
+## 5.3 Multiple working modes of vehicle mounted base station
+
+### 5.3.1 Description
+
+In order to fulfil the high demand of extra cellular coverage and capacity in large cities with a dense population, either buses or cars with on board base stations, are expected to act as relay and help provide convenient and efficient data delivery service to the city residents.
+
+Generally speaking, car is privately owned and the base station mounted on it usually supports a private working mode, i.e., it only allows individual access to the car owner's UEs, e.g., his/her family members, friends, etc.
+
+On the contrary, base station mounted on a bus usually works in a public manner. All the passengers in the bus or in the vicinity can access to the base station on the bus along its predictable itinerary regarding their extra 5G cellular access requirements.
+
+
+
+Diagram illustrating a vehicle-mounted base station. A bus and a car, both labeled 'Uu', are shown with antennas. Arrows point from these antennas to a central base station icon (a tower on a hexagonal base). This base station is connected by a line to a cloud labeled 'Operator 5G Core Network'.
+
+**Figure 5.3-1: Vehicle mounted base station**
+
+### 5.3.2 Pre-conditions
+
+To enable this use, following pre-conditions should be met:
+
+- Alice wants to join a music festival and share the live show to her friend Bob.
+- Alice's car is installed with an on-board base station.
+- The bus that Bob takes is also equipped with on board base station along its itinerary.
+- In the area around the spot of the music festival, the base station mounted on the vehicle is allowed to provide 5G coverage to neighbouring UEs outside the vehicles.
+- Either the base station on a car or bus is able to connect the NG-RAN and 5G Core network.
+
+### 5.3.3 Service Flows
+
+1. Alice drives by her own car to the spot of the music festival with her family. Alice as well as her family's UEs is connected to the base station on her car, which has been set to provide private access only. Alice pickup her friend Mary at Mary's home when she drives her car to the fesitval, and Mary's UE is connected to the base station on Alice's car since Alice grant Mary to access, e.g. by giving Mary an Token. Mary uses her UE and the Token to access the Internet via the base station on the car during Alice drives.
+2. Alice parks her car in a parking lot near the spot of the music festival. John is a stranger in the nearby. His UE tries to connect to the base station on Alice's car, but it fails without be granted authentication from Alice.
+3. At the same time, Bob takes a bus back home, with a base station mounted on it. Bob's UE is connected to the base station on the bus, which provides public access to all the passengers on the bus.
+4. Alice starts sharing video with Bob the live video during the concert festival.
+5. At the festival, Alice meets three of her friends. Since long time no see, they decide to go back to Alice' home for further drinks and chatting. Then Alice set the base station on her car to provide open access. With this setting, all friends on the car can access the Internet via the base station on the car.
+6. When Alice arrived at home, she parked her car and turn off the base station on the car. All her friends and Alice then not able to access the base stations on the car.
+
+### 5.3.4 Post-conditions
+
+Alice shares the live video of the music festival to Bob via 5G access from the base station on her car.
+
+Bob is happy to watch a live show via 5G access from the base station on bus.
+
+Mary is happy to access the Internet via the base station on the Alice car during Alice drives.
+
+All friends of Alice are happy to access the Internet via the base station on the Alice car.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+The mobility management of the vehicle mounted base station shall be taken into account.
+
+Multi-network connectivity and service delivery across operators will be used to assist this use case. The 5G system shall be able to maintain service continuity with minimum service interruption when the serving network is changed to a different serving network operated by a different operator.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR 5.3-1] The 5G system shall support the use of vehicle mounted mobile base station relays, which provide 5G access to UEs in the vicinity.
+
+[PR 5.3-2] Subject to operator policy, the 5G system shall support means to configure and enable a vehicle mounted mobile base station relays to allow access to all UEs, or to only allow access to certain authorized UEs e.g., vehicle owner's family members, friends, etc.
+
+## 5.4 Control of UEs access via mobile relays
+
+### 5.4.1 Description
+
+As part of a nationwide campaign to stimulate and increase use of public transportation, a mobile operator (“Green”) and cities administrations launch a “premium 5G connection” service to be offered to Green subscribers, and tourists from partner roamers, when travelling on public buses, trams, trains and underground in the main cities of the country. The improved 5G connectivity would be provided by using 5G mobile base station relays installed on board of public transport vehicles, which inter-connect (wirelessly) to the 5G macro network as part of Green 5G network.
+
+Green decides to offer free and prioritized access to in-vehicle 5G relays to some of their executive customers, while for other Green subscribers (and roamers), access via relays would require and depend on a per-user permission, associated to a certain public transport ticket or membership. The user permission to access the relays may be specific per transport vehicles, and per geographic location/area. In addition, Green can configure other policies and parameters, as part of the RAN and/or relay settings, which may also depend on some macro RAN or other network constraints and conditions, for example it may limit/prioritize access to mobile relays based on time of the day, relay load, speed etc..
+
+### 5.4.2 Pre-conditions
+
+In the service flow below, as an example, the following public transport “city pass” options are assumed to be available, and corresponding relay access permission policies to be set and provisioned by Green:
+
+Note: a city pass can have different time duration/validity (1 - 12 months) and includes free ticket/ride for all public transportation (bus, tram, metro, trains) in all areas, plus other benefits like entrance to city museums, parks etc..
+
+- 1-month city pass: Access to mobile relays on all buses, city centre area only, during non-peak hours
+- 6-month city pass: Access to mobile relays on all buses and trams, inside & outside city centre, non-peak hours
+- 1-year city pass: Access to mobile relays on all public vehicles (including metro & trains), all city, any time
+- “Executive” pass (for Green executives only): Full/unrestricted permission to access mobile 5G relays, nationwide
+
+For executive users, further higher priority access could be configured in case of specific relay or RAN operating/capability conditions, e.g. related to relay load or mobility factors. As example, normal priority UEs may connect via relays on buses only if less than 5 users are active (via the relay) and/or at bus speed is in a certain range, while executive UEs would have unrestricted access/connection in the same conditions.
+
+### 5.4.3 Service Flows
+
+1. Three users, Alice, Bob and Charlie (Green customers) have the following city pass/status
+ - Alice: Executive;
+ - Bob: 1-month pass;
+ - Charlie: 6-months pass
+
+They work for the same company (Green) and same office building, located outside the main city area, and live in the same city centre neighbourhood.
+
+2. Every day they share same itinerary and public transport vehicles to commute between home to work, i.e.
+ - a. Around 6am (non-peak hour), one bus from home to the tram station (city centre area), then a tram to the office (from inside to outside city centre).
+ - b. Around 6pm (peak hour), opposite itinerary to return home
+3. During their commuting, they typically use their smartphone almost all the time (active 5G connection), to browse internet and/or various social media communication. Based on their city pass/membership and other policies assumed above, they will experience the following 5G access/connectivity situations:
+ - a. Alice:
+ - i. Home to office: connected via relay on the bus and the tram
+ - ii. Office to home: same as above, high priority access
+ - b. Bob:
+ - i. Home to office: connected via relay on the bus
+ - ii. Office to home: no access via relay
+ - c. Charlie:
+ - i. Home to office: connected via relay on the bus and part of the tram itinerary (till city centre limit)
+ - ii. Office to home: partially connected via relay on the bus and the tram (inside city centre);
+ - During peak hour, given normal priority rights, sometimes connection via relay on the bus is not possible, e.g. if/when other 5 Green passengers are on the bus and already actively connected via the relay.
+
+### 5.4.4 Post-conditions
+
+All three users enjoy the premium 5G service from Green during their daily commuting to/from office, and are happy about their membership to the 5G-friendly public transport system!
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+[PR 5.4-1] The 5G system shall support provisioning and configuration mechanisms to control UEs' access to the 5G network via a mobile base station relay, based on
+
+- User/UE subscription and/or permission (can be specific to each preferred relay);
+- User/UE or relay geographical location, time of the day, load, speed.
+
+## 5.5 Control of UEs access via mobile relays using application-based subscription
+
+### 5.5.1 Description
+
+A mobile operator (“Blue”) partners with the public transit organization of ConnectedTown to offer 5G connectivity to passengers of public city buses and trams. The 5G connectivity will be provided using 5G base station relays installed on board of those vehicles, connected to the Blue 5G RAN network.
+
+### 5.5.2 Pre-conditions
+
+Blue decides to give its own subscribers free access to 5G connectivity in city buses and trams, and to offer subscribers of other operators the possibility to subscribe to the service for a fee, with the following tariff plans available:
+
+- 20 min access in any bus or tram;
+- one day access in any bus or tram;
+- one month access in any bus or tram.
+
+### 5.5.3 Service Flows
+
+4. Three users, Jack, Jill and Francois are about to enter a bus equipped with a Blue 5G on board relay
+ - Jack is a Blue subscriber
+ - Jill is a Purple subscriber
+ - Francois is from France and visiting ConnectedTown during his vacation. He is a Rouge (French operator) subscriber
+5. When on the bus
+ - a. Jack's UE automatically connects to the vehicle relay
+ - b. Jill and Francois get a notification on the UI of their UE informing them about the availability of in-bus 5G service and listing the corresponding app available for download.
+6. Jill, who is commuting to work, recalls that Purple's coverage on the bus route is usually spotty. Since she rides the bus every weekday to go to work, she downloads the app and decides to sign up for the one month plan. Francois also downloads the app. He is only in town for a day and from the information provided by the app, he determines that the rate offered by Blue is cheaper than what he gets from the preferred VPLMN with which Rouge has a roaming agreement in ConnectedTown, so he signs up for the one day plan. Jill and Francois' UEs connect to the vehicle relay.
+
+### 5.5.4 Post-conditions
+
+All three users enjoy the 5G connectivity from Blue, and – when leaving the bus - give positive feedback to the driver about the efficient and high-tech public buses.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR 5.5-1] The 5G system shall support mechanisms to control UEs selection of mobile base station relays and UEs access to the 5G network via a mobile base station relay, based on
+
+- user/UE subscription and/or permission (can be specific to each preferred relay);
+- user preference, for manual selection of a specific relay.
+
+## 5.6 Keep connectivity via mobile base station relay
+
+### 5.6.1 Description
+
+In the urban environment, especially during the rush hour, a high density of passengers is waiting at the bus stop, which puts forwards a high demand for 5G area traffic capacity. A fleet of buses with on board base stations act as relays, which are expected to provide an efficient content delivery to these passengers. The buses typically move at a low speed and usually follow a certain predictable itinerary, along which the extra cellular capacity requirements are fulfilled.
+
+
+
+Diagram illustrating connectivity maintenance via mobile base station relay. A bus with a mobile base station relay is shown on the left, connected wirelessly to a terrestrial base station (Eiffel Tower icon) in the center. The terrestrial base station is connected to the Operator 5G Core Network (cloud icon) on the right. A lightning bolt symbol indicates the wireless connection between the bus and the base station.
+
+**Figure 5.6-1: Connectivity maintenance via mobile base station relay**
+
+### 5.6.2 Pre-conditions
+
+To enable this use, following pre-conditions should be met:
+
+- A bus shall be equipped with a mobile base station relay.
+- The mobile base station relay is capable of providing 5G connectivity to UEs in the bus along the bus itinerary.
+- The mobile base station relay is able to connect the NG-RAN and 5G Core network.
+
+### 5.6.3 Service Flows
+
+1. At a bus stop, there are two bus lines and passengers are either waiting for bus A or bus B.
+2. Before the bus is arriving, 5 people are waiting at the bus stop, namely #1, #2, #3, #4, #5. All of their UEs are connected to the terrestrial base stations.
+3. When bus A arrives, # 1 and #2 get on bus and their UEs access to the mobile base station relay A. Meanwhile, UEs of #3, #4 and #5 are still connected to the terrestrial base station.
+4. Bus A leaves the bus stop.
+5. During the driving process of bus A, UE #1 and UE #2 remain connected through mobile base station relay A.
+6. When bus A arrives at the next bus stop, # 1 gets off the bus A and UE #1 connects to the terrestrial base station. #2 is still on the bus, and UE #2 remains connected through mobile base station relay A.
+7. Bus A arrives at the destination, # 2 gets off the bus and connects to other base stations.
+
+### 5.6.4 Post-conditions
+
+UEs in the bus are provided with enhanced 5G area traffic capacity by the mobile base station.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR 5.6-1] The 5G system shall support the use of mobile base station relay, which provides 5G access to UEs in the vehicle along the vehicle itinerary.
+
+[PR 5.6-2] The 5G system shall provide means to ensure that UEs inside a vehicle, once provided with 5G access and connectivity via a mobile base station relay (e.g. mounted on the vehicle), remain connected via the mobile base station relay (e.g. mounted on the vehicle).
+
+## 5.7 Optimizing mobility for UEs
+
+### 5.7.1 Description
+
+When served by mobile base station relays which are, in nature, mobile (moving around), UEs may experience a large number of unnecessary mobility related burdens, such as unnecessary handovers, selection of a mobile base station relay to connect, and cell reselection.
+
+This use case addresses a scenario that UEs and their nearby mobile base station relay are from the same PLMN in general.
+
+### 5.7.2 Pre-conditions
+
+MNO1 operates mobile base station relays R1a and R1b.
+
+UE1a and UE1b are subscribed to MNO1.
+
+R1a resides in Zone 1 whereas R1b in Zone 2 (refer to Figure below).
+
+NOTE 1: A Zone is not necessarily the area covered by a gNB but denotes a virtual zone for illustration purposes.
+
+UE1a is on R1a whereas UE1b is on R1b.
+
+UE1a does not have active data communication with R1a in Zone 1.
+
+In Zone 2, there is a gNB.
+
+NOTE 2: This means that mobile base station relays residing in Zone 2 are closer to this gNB than any other relays residing outside Zone 2.
+
+
+
+Diagram illustrating the pre-conditions for mobility optimization. It shows three zones: Zone 1, Zone 2, and Zone 3. In Zone 1, UE1a (blue) is on relay R1a (dashed green box). An arrow labeled 'Moving to zone 2' shows R1a moving into Zone 2. In Zone 2, there is a gNB (radio tower icon) and relay R1b (solid green box). UE1a (red) is on R1a, and UE1b (red) is on R1b. A green arrow from R1a to R1b is labeled '(t1, t2)'. A green arrow from R1b to Zone 3 is labeled '(t1, t2+α) staying in Zone 2'. The diagram also shows the labels 'At time= t0' for R1a in Zone 1 and 'UE1a' and 'UE1b' in red text above their respective relays in Zone 2.
+
+Fig. 5.7-1: Pre-conditions
+
+R1a (with UE1a as passenger) moves from Zone 1 into Zone 2 (and stays there from time $t_1$ through time $t_2$ ) whereas R1b (with UE1b) stays in Zone 2 (from time $t_1$ through time $t_2+\alpha$ ) before moving to another destinations (e.g., somewhere in zone 3).
+
+### 5.7.3 Service Flows
+
+R1a moves from Zone 1 into Zone 2 whereas R1b stays on in Zone 2, and R1a stays in the proximity of R1b.
+
+UE1a wants to initiate data communication and performs smart selection of mobile base station relay/cell to which it can attempt for a connection.
+
+UE1a has estimated that R1a was probably with UE1a for a certain period of time (e.g., by seeing that R1a has been close to UE1a itself for a certain time interval $(t_0, t_1)$ as shown in the figure).
+
+UE1a tries to initiate a connection with R1a first and gets connected to R1a (Red in the figure, meaning active communication) if available.
+
+Likewise, UE1b attempts to R1b to initiate a connection (Red in the figure, meaning active communication).
+
+### 5.7.4 Post-conditions
+
+There is no need to make a handover for UE1a to other mobile base station relays or to other gNB as long as the connectivity provided by R1a is good enough.
+
+UE1a and UE1b continue their travels to the next destination (somewhere out of zone 2, e.g., zone 3) with R1a and R1b, respectively, enjoying their connections with no extra handovers.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR 5.7-1] The 5G system shall be able to provide a means to optimize cell selection and minimize unnecessary cell reselection (between mobile base station relays or between mobile base station relays and fixed gNB,) in the presence of mobile base station relays.
+
+NOTE: This requirement is intended to provide the capability for the 5G system (UEs/ mobile base station relays) to be able to optimize selection of a mobile base station relay, e.g., in a vehicle where the UE is on board (or that moved together so far or that is expected to move together).
+
+[PR 5.7-2] The 5G system shall be able to provide a means to minimize unnecessary handover (between mobile base station relays, or between mobile base station relays and a fixed gNB and between) for a UE while served via an mobile base station relay, e.g., based on UE and relay relative mobility or speed.
+
+## 5.8 Load balancing for mobile base station relays
+
+### 5.8.1 Description
+
+When serving a group of UE's (mostly passengers of a vehicle) via mobile base station relays, the traffic load (simply workload) of a relay can often be different from the others'. In an ordinary moving state of a mobile base station relays, a typical mechanism to make rearrangement of the load (often called load-balancing) is to find whether a macro node (gNB) is available and, if so, to perform necessary handover to that node.
+
+However, in the other states such as temporary stop at a bus stop or at a traffic signal, it is expected that several or more mobile base station relays are around, some of which are more overloaded than the others and therefore are suitable for accepting more UEs, if temporary.
+
+This use case addresses a scenario that some UEs being served by a mobile base station relays can get temporarily rearranged/relocated to another mobile base station relays (or to macro node, gNB) where they are all from the same PLMN in general.
+
+### 5.8.2 Pre-conditions
+
+MNO1 operates mobile base station relays R1a and R1b.
+
+NOTE 1: It is still possible that a third party authorised by an MNO operates mobile base station relays but in this use case it is simply regarded/described that the MNO operates them unless specifically needed to distinguish.
+
+UE(1), UE(2), ..., UE(n) are subscribed to MNO1.
+
+R1a resides in Zone 1 whereas R1b in Zone 2 (refer to Figure below).
+
+NOTE 2: A Zone is not necessarily the area covered by a gNB but denotes a virtual zone for illustration purposes.
+
+UE(1), UE(2), ..., UE(n) are on R1a and have active communications in Zone 1 whereas no UEs on R1b have any active communications in Zone 2.
+
+R1a is fairly overloaded/congested due to many UE's competing for network resources.
+
+In Zone 2, there is a gNB.
+
+NOTE 3: This means that mobile base station relays residing in Zone 2 are closer to this gNB than any other relays residing outside Zone 2.
+
+
+
+Diagram illustrating the pre-conditions for a network load balancing scenario. It shows three zones: Zone 1, Zone 2, and Zone 3. A gNB is located in Zone 2. In Zone 1, a relay R1a (dashed green box) contains UE(1) through UE(n) (red text). An arrow labeled 'Moving to zone 2' points from R1a in Zone 1 to R1a in Zone 2. In Zone 2, there are two relays: R1a (solid green box) containing UE(1) through UE(n-2) (red text) and R1b (solid black box) containing UE(n-1) and UE(n) (red text). Below R1a in Zone 2 is the time interval (t1, t2). Below R1b in Zone 2 is the time interval (t1, t5). An arrow labeled 'staying in Zone 2' points from R1b in Zone 2 to R1a in Zone 3. Below R1a in Zone 3 is the time interval (t3, t4). The gNB is shown as a tower icon with a signal symbol above it.
+
+**Fig. 5.8-1: Pre-conditions**
+
+R1a (with UE(1), ..., UE(n) as passengers having active communications) moves from Zone 1 into Zone 2 whereas R1b (with no UEs with active communications) stays in Zone 2.
+
+### 5.8.3 Service Flows
+
+R1a moves from Zone 1 into Zone 2 whereas R1b stays on in Zone 2, and R1a stays in the proximity of R1b.
+
+Some UE's, say UE(n-1) and UE(n), out of those being served by R1a are relocated to R1b.
+
+R1a has the burden a little bit alleviated and therefore those UE's, UE(1) through UE(n-2), can enjoy better communication performance during a certain length of time.
+
+R1a has now begun to move to next destination and those UE's (i.e., UE(n-1) and UE(n)) which had temporarily been deported from the steady friend R1a, are getting back to the steady friend.
+
+### 5.8.4 Post-conditions
+
+On average UE's using mobile base station relays can get better communication experience.
+
+It was fortunate that the (n-2) UE's can get better communication experience during that time period in Zone 2. They expect that this type of load balance will happen again whenever possible.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR 5.8-1] The 5G system shall be able to provide a means to perform load balancing among mobile base station relays.
+
+NOTE: This requirement is intended to provide the capability for the 5G system (UEs/ mobile base station relays) to be able to optimize the load of network resources whenever possible.
+
+## 5.9 Provide location service to a UE attached to the relay mounted in the vehicle
+
+### 5.9.1 Description
+
+In certain urban environments, tall buildings and other infrastructure sites make GNSS signal too weak for normal UEs, e.g., mobile phones. It is even harder to get GNSS signal when a user is navigating with a mobile phone in a vehicle in urban area.
+
+Some kinds of public vehicles (e.g., bus, light rail train) can take many passengers with a number of UEs. When any of them is using location service or is a target UE in a location service and when UE based location is not possible, e.g. GNSS signals are very weak, the network based location service is used to make sure that the UE can still be located.
+
+In another scenario, the target UE of a location service is in a poor 3GPP coverage area, and it then uses relay mounted in the vehicle to access to the network and to be located.
+
+### 5.9.2 Pre-conditions
+
+A bus takes some passengers who get internet service over the 3GPP access through the bus-mounted relay.
+
+The bus-mounted relay gets its location information through GNSS or 3GPP network based location services.
+
+The UEs of some passengers are in low battery.
+
+### 5.9.3 Service Flows
+
+Case 1: The passengers move into an area of poor GNSS coverage when GNSS based location service is used
+
+1. A passenger uses an application which need location service. GNSS based location service is used.
+2. The passengers move into an area of poor GNSS coverage
+3. The UE or an external AF sends location requests with the requested granularity (e.g. 5 meters) to the 5GS to trigger the network based location service.
+4. The 5GS responds the location information to the UE or the external AF.
+
+Case 2: The passengers move into an area of poor 3GPP coverage when 3GPP network based location service is used
+
+1. A passenger uses an application which need location service. 3GPP network based location service is used.
+2. The passengers move into an area of poor 3GPP coverage.
+3. The passengers uses relay mounted in the vehicle to access to the 3GPP network.
+4. The UE or an external AF sends location requests to the 5GS with the requested granularity (e.g. 5 meters) to trigger the network based location service.
+5. The 5GS responds the location information to the UE or the external AF.
+
+### 5.9.4 Post-conditions
+
+All passengers who need location service can still get the location information even when they move into an area of poor GNSS coverage or poor 3GPP coverage.
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+[PR 5.9-1]: The 5G system shall support providing location service for the UEs accessing to the 5GS network via a mobile base station relay (e.g. mounted on a vehicle).
+
+[PR 5.9-2]: The 5G system shall support providing location information to a requesting UE or other location entity, for UEs accessing the 5GS network via a mobile base station relay (e.g. mounted on a vehicle), considering e.g. specific location granularity, and efficient UE power consumption.
+
+## 5.10 Incentives and charging
+
+### 5.10.1 Description
+
+This use case describes the scenario of a transportation company (“Alfa”), owning different fleets of vehicles and transport services in the major cities of the country. Vehicles are for persons or goods transport, e.g taxis, shuttles, buses, vans, and can be equipped (installed or upgraded by the manufacturer) with on board mobile base station relays. The relays can be configured to provide better 5G coverage/connectivity to passengers inside the vehicle (e.g. as premium in-vehicle service), and/or outside users (for localized coverage/capacity boost)
+
+Alfa makes a nationwide commercial agreement with one MNO (“Beta”) offering the possibility to use, control and operate the relays on their vehicles. The agreement with Beta includes some direct payment to Alfa, and other arrangements, e.g. free or discounted service for 5G traffic used by Alfa employees or drivers (MNO subscribers) via the vehicle relays.
+
+On the other hand, Beta can offer and apply special subscription tariffs to some of their clients, e.g. enterprises or individual customers for premium in-vehicle 5G experience.
+
+In both cases, it is assumed that the commercial agreements and/or customer tariffs would depend on the amount of data exchanged over the relays, quality of service, and other conditions (maybe specific to certain geographical areas, days/time, users, etc).
+
+### 5.10.2 Pre-conditions
+
+The MNO Beta decides to use a certain type and amount of Alfa transport vehicles with relay capabilities, in particular for
+
+- Taxis and shuttles, used by Beta subscribers and/or client enterprises
+- Other transport vehicles, used by Beta for outdoor hot spot coverage/capacity boost, according to specific vehicles itineraries, routes (e.g. dense-urban streets), or transit/stop locations (e.g. bus/train stations, stadiums, airports).
+
+Relay operation is managed by and under the control of Beta, which will perform all proper provisioning, configuration and the necessary interconnection/integration with the Beta RAN.
+
+### 5.10.3 Service Flows
+
+1. Relays are activated by Beta.
+2. Beta’s network and relays collect and report charging data (online and offline) for the 5G traffic exchanged via the vehicle relays managed by Beta, i.e.
+ - Data exchanged by individual passengers, and experienced QoS, using 5G connectivity via in-vehicle relays
+ - Overall 5G traffic increase via vehicle relays in specific hot spot areas, days/times.
+3. Every billing period, Beta generates related billing records for
+ - Beta customers and/or client enterprises, paying for in-vehicle premium 5G service as part of their MNO membership/plan.
+ - Vehicles’ drivers and other Alfa employees, eligible for discounted tariffs when using 5G relays (as per deal with Alfa).
+
+4. Beta will compensate Alfa for the extra 5G traffic/capacity enabled by the relays, based on the amount of traffic exchanged via the relays, experienced QoS, specific location and time etc., as per their commercial contract and service conditions.
+
+### 5.10.4 Post-conditions
+
+Alfa and Beta meet their business goals. Beta customers are very pleased by their in-vehicle 5G experience.
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+[PR 5.10-1] The 5G system shall be able to configure and provision specific required QoS for traffic relayed via a mobile base station relay, e.g. may be based on user's subscription, geographical area, day/time of operation. relay type, itinerary/mobility, etc.
+
+NOTE: QoS is intended as end-to-end QoS, i.e. covering both UE access and relay backhaul QoS.
+
+[PR 5.10-2] The 5G system shall be able to identify and differentiate the traffic relayed via a mobile base station relay, e.g. to apply specific charging policies.
+
+[PR 5.10-3] Online and offline charging shall be supported for UEs connected via a mobile base station relay.
+
+[PR 5.10-4] The 5G system shall be able to provide and collect charging information for UEs using a mobile base station relay, including e.g.:
+
+- Identification of UEs/users involved;
+- Initiation/termination time of relay communication;
+- Duration and amount of data transmitted and received;
+- Type of service, QoS, other allocated resources (e.g. spectrum);
+- Geographic location(s) served by the relay
+- Other relay mobility information (e.g. itinerary, speed)
+
+## 5.11 Use cases on Service continuity
+
+### 5.11.1 Mobility between macro and relay
+
+#### 5.11.1.1 Use case 1: User entering/leaving the vehicle
+
+##### 5.11.1.1.1 Description
+
+When users/UEs enter or leave vehicles with on board relays, handover between macro and vehicle relays can happen, if an active connection is ongoing.
+
+The scenario described in this use case refers to a user, Alice, engaged in a phone call while going to her office via tram.
+
+##### 5.11.1.1.2 Pre-conditions
+
+Alice is at a tram station, waiting for her usual 8am tram to get to her office, located several miles away.
+
+The tram happens to be equipped with an on board base station relay, offering 5G connectivity from the same HPLMN as Alice is subscribed to.
+
+Before the tram arrives, Alice calls her secretary to discuss the busy meetings schedule of the day, using available radio coverage from her HPLMN macro network.
+
+##### 5.11.1.1.3 Service Flows
+
+1. Alice is at the tram station, with an ongoing call using macro 5G network (from her HPLMN)
+2. The tram arrives, and Alice enters the vehicle. Given the very good 5G relay coverage inside, much better than the macro NW, the call is handed over via the relay, without any discontinuity.
+3. The tram arrives at Alice's office location, and the call is still ongoing, via the tram relay.
+4. Alice leaves the tram; while exiting, the 5G connection switches back from the tram relay directly to the macro network, and the call continues seamlessly.
+
+
+
+Diagram illustrating the service flow for a user (Alice) moving from a macro network to a tram relay and back. The diagram shows four numbered steps: 1. Alice is at a tram station connected to a macro network (tower). 2. The tram arrives, and Alice enters, connecting to the tram's relay. 3. The tram arrives at the office location, and the call continues via the relay. 4. Alice leaves the tram and reconnects to the macro network. The diagram includes icons for a building (office), a tram with a relay, a house, and a macro network tower.
+
+Figure 5.11.1-1
+
+##### 5.11.1.1.4 Post-conditions
+
+While walking to the office building, Alice thanks her secretary for the helpful de-brief and hangs up; she feels very well prepared for the busy working day ahead.
+
+##### 5.11.1.1.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+##### 5.11.1.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.1-1] The 5G system shall be able to support efficient handover when a UE active communication changes from the macro network to a mobile base station relay (e.g. mounted on a vehicle) and vice versa, ensuring end-to-end service continuity during mobility of the UE (e.g. entering or leaving the vehicle) and/or the relay.
+
+#### 5.11.1.2 Use case 2: User outside the vehicle
+
+##### 5.11.1.2.1 Description
+
+When moving to an area where coverage from mobile base station relay(s) is available, the UE can be handed over from the macro network to a suitable mobile base station relay. Conversely, when the UE served by a mobile base station relay is heading out of the area where coverage from mobile base station relay(s) is available, the UE can be handed over from the relay to the macro network. In both cases, ensuring that there is no interruption in the ongoing services at the UE will yield an improved user experience.
+
+##### 5.11.1.2.2 Pre-conditions
+
+Anna lives in a residential area within walking distance of the city center. She gets good 5G service from the macro network around her house thanks to the lack of tall buildings and the fact that the area is not densely populated. Anna works in the city center and likes to go to the office on foot. Often, to save time, she takes conference calls on her way to work.
+
+
+
+The diagram illustrates a network scenario. On the left, a grey oval labeled 'City center' contains a bus icon labeled 'Relay' and a cell tower labeled 'gNB #2'. A blue arrow labeled 'Uu NR' points from gNB #2 to the relay. Above the relay, 'Other UE(s)' is shown with a phone icon. On the right, outside the city center, is a house icon labeled 'Anna's house' with a phone icon labeled 'Anna's phone'. A blue arrow labeled 'Uu NR' points from a cell tower labeled 'gNB #1' to Anna's phone. To the left of the city center oval is a building icon labeled 'Anna's office'.
+
+Figure 5.11.1-2: Network diagram showing Anna's phone connected to gNB #1 at her house, with a relay in the city center connected to gNB #2 at her office.
+
+Figure 5.11.1-2
+
+##### 5.11.1.2.3 Service Flows
+
+- (1) It's 7:55 am and Anna gets out of her house to walk to work. She has a conference call at 8 am so she starts the conferencing app on her phone and connects her headset.
+- (2) At 8:25 am, Anna arrives in the city center. Anna's boss asks her to give an update on the project she is working on. Anna starts giving her presentation.
+- (3) Due to the high-rise buildings in the center, the macro coverage gets spotty, and due to the high number of UEs, the data rate allocated to Anna's phone starts going down. Anna's boss starts asking her questions on the updates she has presented.
+- (4) Traffic in the center is very packed and there are buses equipped with mobile station relays on the avenue where Anna is walking. The macro network determines that Anna's phone can get better coverage from a relay than from the macro and hands over Anna's phone to the relay in the bus closest to Anna. All ongoing services in the phone, including the conference call, are transferred without service interruption.
+
+
+
+This diagram shows the network after a handover. The 'City center' oval contains the 'Relay' bus, 'gNB #2', and 'Other UE(s)'. A blue arrow labeled 'Uu NR' points from the relay to Anna's phone (now inside the oval). Another blue arrow labeled 'Uu NR' points from gNB #2 to the relay. The house icon labeled 'Anna's house' and the cell tower labeled 'gNB #1' are on the right, outside the oval. The building icon labeled 'Anna's office' is on the left.
+
+Figure 5.11.1-3: Network diagram showing Anna's phone connected to the relay bus in the city center, which is connected to gNB #2 at her office.
+
+Figure 5.11.1-3
+
+- (5) Anna's phone regains good coverage and maximum data rate, enabling Anna to not miss any of her boss's questions and to provide answers. Anna's boss congratulates her for the good progress on her project.
+- (6) Anna's conference call continues and her colleagues give updates on their own project. Anna arrives in front of her office building and enters the building, while the bus in which the relay is installed continue alongside the avenue
+
+- (7) The network determines that the serving relay and Anna's phone are moving in diverging directions and hands over Anna's phone the macro cell serving Anna's office building. All ongoing services in the phone, including the video call, are transferred without service interruption.
+
+
+
+The diagram shows a 'City center' area represented by a light blue oval. Inside this area, there is a bus labeled 'Relay', a smartphone labeled 'Anna's phone', and a base station labeled 'gNB #2'. Arrows indicate connections: from 'gNB #2' to 'Relay', from 'Relay' to 'Anna's phone', and from 'Relay' to 'Other UE(s)'. Outside the oval, to the left, is 'Anna's office' (represented by a building icon) with an arrow pointing to 'gNB #2'. To the right is 'gNB #1' (represented by a tower icon). To the top right is 'Anna's house' (represented by a house icon).
+
+Diagram illustrating the network configuration for a mobile relay scenario. A 'City center' area is shown with a bus labeled 'Relay'. Anna's phone is connected to the relay. The relay is connected to gNB #2. gNB #2 is connected to gNB #1. Anna's office is shown near gNB #2. Other UE(s) are shown near the relay. Anna's house is shown separately.
+
+Figure 5.11.1-4
+
+- (8) Anna finishes her conference call, and goes to her office.
+
+##### 5.11.1.2.4 Post-conditions
+
+Anna's conference call was transferred seamlessly from the macro network to the mobile base station relay and then back to the macro network.
+
+Anna is very pleased that she was able to participate in the call without service outage, which enabled her to complete her presentation, answer all questions, and listen to her colleagues' updates.
+
+##### 5.11.1.2.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+##### 5.11.1.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.1-2] The 5G system shall be able to support efficient handover when a UE active communication changes from the macro network to a mobile base station relay (e.g. mounted on a vehicle) and vice versa, ensuring end-to-end service continuity during mobility of the UE (e.g. moving outside the vehicle) and/or the relay.
+
+### 5.11.2 Mobility of relay between macro nodes
+
+#### 5.11.2.1 Use case 1: User inside the vehicle
+
+##### 5.11.2.1.1 Description
+
+While the UE is served by a mobile base station relay, as the vehicle is moving, it is possible for the relay to be handed over to a different macro node. Ensuring that there is no interruption to the ongoing services at the UE will yield an improved user experience.
+
+##### 5.11.2.1.2 Pre-conditions
+
+Jim is going on a business trip that was scheduled on very short notice. To prepare for the trip, he has set up a conference call with this team that will take place during his commute to the airport using his favorite ride-sharing service, whose vehicles happen to be equipped with mobile station relays.
+
+Jim settles into his ride and opens his laptop which has with a 5G modem. The modem in the laptop registers with the mobile base station relay mounted on the vehicle. Jim starts his conference call and shares the slides he has prepared.
+
+
+
+The diagram illustrates the initial state of the scenario. On the left, 'Jim's house' is represented by a house icon. In the center, a car labeled 'Relay' contains 'Jim's laptop'. A blue arrow labeled 'Uu NR' points from the laptop to a base station icon labeled 'gNB #1'. To the right, an airplane icon above a horizontal line represents an 'Airport'. Another base station icon labeled 'gNB #2' is shown to the right of gNB #1.
+
+Figure 5.11.2-1: Diagram showing Jim's house, a car with a relay and Jim's laptop, and an airport. The car is connected to gNB #1 via a Uu NR link. gNB #1 is connected to gNB #2.
+
+Figure 5.11.2-1
+
+##### 5.11.2.1.3 Service Flows
+
+1. Jim's ride goes onto the highway and heads for the airport. As the vehicle moves away from the city, coverage from the serving macro node to the relay becomes weaker.
+2. The macro network determines that the relay can be better served by another macro node, and hands over the relay to that macro node. All ongoing services on Jim's laptop, including the conference call with slide sharing, are transferred without service interruption.
+3. Jim arrives to the airport, thanks his team and ends the conference call.
+
+##### 5.11.2.1.4 Post-conditions
+
+Jim's conference call and slide sharing were transferred seamlessly during handover of the relay serving Jim's laptop from one macro node to another. Jim is very pleased that he was able to make the most of the ride time and go through the entire slide deck without any interruption in connectivity.
+
+
+
+This diagram shows the state after a handover. The car ('Relay') with 'Jim's laptop' is now positioned closer to 'gNB #2'. A blue arrow labeled 'Uu NR' points from the laptop to 'gNB #2'. 'gNB #1' remains on the left, and the 'Airport' is on the right.
+
+Figure 5.11.2-2: Diagram showing the state after handover. The car with the relay and Jim's laptop is now connected to gNB #2 via a Uu NR link. gNB #1 is still shown on the left.
+
+Figure 5.11.2-2
+
+Note: the use case does not assume a particular vehicle's speed, and may apply also to users and relays inside high-speed trains (up to 500kmph).
+
+##### 5.11.2.1.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+##### 5.11.2.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.2-1] The 5G system shall be able to support efficient handover of a UE active communication when a mobile base station relay (e.g. serving a UE inside a vehicle) changes between macro network nodes, ensuring end-to-end service continuity during mobility of the relay.
+
+#### 5.11.2.2 Use case 2: User outside the vehicle
+
+##### 5.11.2.2.1 Description
+
+In certain scenarios, a mobile base station relay mounted on a vehicle may serve UEs outside, and while the vehicle is moving the relay connection to the macro network can change, i.e. can be handed over to a different macro donor node. In such cases, the system should ensure seamless mobility and service continuity.
+
+The example scenario described here refers to an outdoor sport event (bike or pedestrian race), with motorbikes' camera transmitting real-time video via relays mounted on alongside vehicles, e.g. provided by the event organizer or TV broadcaster. During the race, the vehicle relay changes macro cell coverage, i.e. relay connection is handed over between two macro donor nodes.
+
+##### 5.11.2.2.2 Pre-conditions
+
+Before the race starts, cameras on motorbikes get configured and connected to a surrounding vehicle relay, providing 5G wireless backhauling connectivity toward a certain PLMN network.
+
+Real-time video transmission starts, and the vehicle relay is connected to macro cell (donor node) #1.
+
+
+
+The diagram shows a 'Sport race direction' indicated by a large blue arrow pointing to the left. On the right, a car labeled 'Relay' is connected to a base station labeled 'Donor gNB 1'. A motorbike with a camera labeled 'UE' is connected to the 'Relay'. On the left, another base station labeled 'Donor gNB 2' is shown. A group of motorbikes is depicted in the background, with one motorbike's camera connected to the relay car.
+
+Diagram illustrating the pre-conditions of the relay scenario. A car labeled 'Relay' is connected to 'Donor gNB 1'. A motorbike with a camera labeled 'UE' is connected to the 'Relay'. A large blue arrow labeled 'Sport race direction' points to the left. 'Donor gNB 2' is shown on the left side of the diagram.
+
+Figure 5.11.2-3
+
+##### 5.11.2.2.3 Service Flows
+
+- (1) The sport race starts; motorbikes with cameras and cars equipped with relays follow, on the side, the race group/platoon.
+- (2) While moving along the race itinerary, the relay coverage and connection quality from macro cell#1 gets weaker, and macro cell#2 becomes a stronger/better cell to connect to.
+- (3) Based on NW decision, at a certain point the relay backhaul connection is handed over from cell#1 to cell#2, while UEs (cameras) remain connected to the same relay.
+
+##### 5.11.2.2.4 Post-conditions
+
+The vehicle relay is connected to macro cell#2, and no service disruption occurred to the ongoing video transmission.
+
+
+
+The diagram shows a circular inset at the top representing a 'Sport race' area. Inside this area, a car labeled 'Relay' is shown with a 'UE' (User Equipment) icon inside it. A large blue arrow labeled 'Sport race direction' points to the left. Below the inset, two base station icons are shown: 'Donor gNB 2' on the left and 'Donor gNB 1' on the right. A smaller blue arrow labeled 'Change of macro donor cell' points from Donor gNB 2 towards Donor gNB 1, indicating the relay's movement between cells.
+
+Diagram illustrating a relay node (car) moving between two macro donor cells (Donor gNB 2 and Donor gNB 1) during a sport race. The relay is connected to a UE (User Equipment) inside the car. The sport race direction is indicated by a large blue arrow pointing left. The change of macro donor cell is indicated by a smaller blue arrow pointing left, showing the relay moving from Donor gNB 2 towards Donor gNB 1.
+
+Figure 5.11.2-4
+
+##### 5.11.2.2.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+##### 5.11.2.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.2-2] The 5G system shall be able to support efficient handover of a UE active communication when a mobile base station relay (e.g. serving a UE outside a vehicle) changes between macro network nodes, ensuring end-to-end service continuity during mobility of the relay.
+
+### 5.11.3 Mobility between relays
+
+#### 5.11.3.1 Use case 1: User inside the vehicle
+
+##### 5.11.3.1.1 Description
+
+Some big size vehicles, e.g. trains or trams, can require multiple 5G base station relays to provide good coverage to users/UEs located in different parts of the vehicle. In such cases, if active users/UEs move around the vehicle their connection can switch between different relays.
+
+In the example described hereafter, Tom is travelling on a high-speed train that provides 5G on board coverage (from his HLMN) by using relays installed 2-3 wagons apart, connected via wireless backhaul to the wide-area 5G macro RAN.
+
+##### 5.11.3.1.2 Pre-conditions
+
+Tom is seating on the train and his smartphone is camped on a local (HPLMN) 5G relay inside/nearby his wagon. It's almost lunch time, and he's thinking to go and eat something at the small restaurant/bar available on the train, located few wagons away. Meanwhile, Tom receives a video-chat call from his wife.
+
+
+
+The diagram shows a train consisting of several wagons. From left to right: a 'Restaurant wagon' (light blue), two 'Passenger wagons' (light grey), and a 'Front' section (dark grey). Each wagon has a 'Relay' unit. In the second passenger wagon, a person icon (Tom) is shown with a mobile phone, connected to the relay. A blue arrow points from Tom to a 5G base station icon located below the train, representing an ongoing call.
+
+Figure 5.11.3-1: Diagram showing a train with a Restaurant wagon and Passenger wagons. A user (Tom) is in a Passenger wagon, connected to a 5G relay. A blue arrow points from the user to a 5G base station below the train, indicating a call in progress.
+
+Figure 5.11.3-1
+
+##### 5.11.3.1.3 Service Flows
+
+1. Tom has started a call, using 5G connectivity from the close-by 5G relay (e.g. inside his wagon)
+2. During the call, Tom moves to the restaurant wagon, which is covered by another 5G relay.
+3. While moving between wagons, connectivity quality/strength of the first relay decreases, while coverage from the relay in the restaurant wagon becomes available and stronger.
+4. When Tom gets closer to restaurant wagon, the call is handed over from the first relay to the second relay, using the same donor macro node.
+
+##### 5.11.3.1.4 Post-conditions
+
+Tom arrives at the restaurant without perceiving any disruption to the ongoing call and can continue enjoying his phone conversation while seating at the bar.
+
+
+
+This diagram shows the same train as Figure 5.11.3-1, but Tom has moved from the second passenger wagon to the 'Restaurant wagon'. He is now connected to the relay in the restaurant wagon. A blue arrow points from Tom to the same 5G base station icon below the train, indicating that the call has been successfully handed over to the new relay.
+
+Figure 5.11.3-2: Diagram showing the train after Tom has moved to the Restaurant wagon. He is now connected to the relay in the Restaurant wagon, and a blue arrow points from him to the same 5G base station below the train, indicating the call has been handed over.
+
+Figure 5.11.3-2
+
+Note: the use case does not assume a specific vehicle's speed, and may apply also to high-speed trains (up to 500kmph).
+
+##### 5.11.3.1.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+##### 5.11.3.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.3-1] The 5G system shall be able to support efficient handover when a UE active communication changes between mobile base stations relays (e.g. mounted on a vehicle), ensuring end-to-end service continuity during mobility of the UE (e.g. moving inside the vehicle).
+
+#### 5.11.3.2 Use case 2: User outside the vehicle
+
+##### 5.11.3.2.1 Description
+
+While a user is located in an area where coverage from mobile base station relay(s) is available, the user's UE can be handed between mobile base station relays due to mobility of the relays. Ensuring that that there is no interruption in the ongoing services at the UE during such handover will yield an improved user experience.
+
+##### 5.11.3.2.2 Pre-conditions
+
+Tom has made plans to have lunch with friends at a sushi restaurant downtown. The food there is very good, plus the restaurant is conveniently located across from the downtown bus transit hub/station, which enables Tom to reach the restaurant easily by public transportation. All buses in Tom's city are equipped with mobile base station relays.
+
+Tom arrives early at the restaurant and sits down at a table. His phone registers with the mobile base station relay mounted on a bus across the street awaiting departure. Tom starts streaming his favorite TV show on his phone while waiting for his friends.
+
+
+
+Diagram illustrating the network architecture for the use case. A 'Sushi restaurant' and 'Tom's phone' are shown at the top. Below them is a 'Bus transit hub' with two buses labeled 'Relay #1' and 'Relay #2'. To the right is a 'gNB' (base station). Arrows labeled 'Uu NR' indicate network connections: from Tom's phone to Relay #1, from Relay #1 to the gNB, and from Relay #2 to the gNB. The entire scene is labeled 'Downtown'.
+
+Figure 5.11.3-3
+
+##### 5.11.3.2.3 Service Flows
+
+1. The driver of the bus equipped with the mobile base station relay serving Tom's phone gets in the bus and prepare to depart. The driver turns on the engine, closes the doors, and starts driving the bus toward the exit of the bus transit hub, then makes a left into the avenue.
+2. The network determines that the serving relay is moving away from Tom's phone and hands over Tom's phone to a relay located in another bus awaiting departure at the bus transit hub. All ongoing services in the phone, including the streaming of the TV show, are transferred without service interruption.
+3. Tom's friends arrive at the restaurant, and they order lunch.
+
+##### 5.11.3.2.4 Post-conditions
+
+Tom's streaming video was transferred seamlessly from the mobile base station relay mounted on the first bus, to a mobile base station relay mounted the second bus. Tom is very pleased that he was able to watch his TV show without interruption while he was waiting for his friends.
+
+
+
+Diagram illustrating the post-conditions of a video streaming session in a city environment. The scene is labeled 'Downtown' and includes icons for buildings, a 'Sushi restaurant', and a 'Bus transit hub'. Two buses are shown, labeled 'Relay #1' and 'Relay #2'. A smartphone icon labeled 'Tom's phone' is connected to 'Relay #1' via a 'Uu NR' link. 'Relay #2' is connected to a 'gNB' (base station) via a 'Uu NR' link. The diagram shows the transition of the video stream from Relay #1 to Relay #2 as the bus moves.
+
+Figure 5.11.3-4
+
+##### 5.11.3.2.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+##### 5.11.3.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.3-2] The 5G system shall be able to support efficient handover when a UE active communication changes between mobile base stations relays (e.g. mounted on a vehicle), ensuring end-to-end service continuity during mobility of the UE (e.g. moving outside the vehicle) and/or the relays.
+
+### 5.11.4 Group UEs' service continuity
+
+#### 5.11.4.1 Description
+
+After a bus is installed of mobile BS relay, the passengers in the bus can be served by the relay. When the bus is moving, it is possible for the relay to be handed over to a different macro node. Thus, no interruption to the ongoing services at the UEs in the bus will yield an improved user experience.
+
+#### 5.11.4.2 Pre-conditions
+
+The city bus company has assigned contract with operator AA to install mobile BS relay on the city buses. All the passengers in the buses can be served by the relay.
+
+Passenger Anna, Jim are in the city bus RED. Anna opens her tablet and registers with the mobile base station relay mounted on the bus. She begins to play online game through her tablet. Jim opens his smartphone to register with the relay mounted on the bus then begins to view online video.
+
+
+
+Diagram illustrating the use case of a mobile base station relay (RED bus) moving between two macro nodes. A red bus is shown moving from left to right, indicated by a red arrow labeled 'moving'. The bus is connected to a macro node (represented by a tower icon) via a dashed blue line. The bus is also connected to a second macro node (represented by a tower icon) via a dashed blue line. The bus is shown within a blue oval on the left and an orange oval on the right, representing the coverage areas of the two macro nodes.
+
+**Figure 5.11.4-1: Anna and Jim in the city bus RED**
+
+#### 5.11.4.3 Service Flows
+
+1. RED bus moves along its route and the mobile base station relay mounted on the bus connecting with the serving macro node provides communication service for its passengers.
+2. When it is moving, the radio signal which the relay received becomes weak.
+3. The 5G system identifies that the relay can be better served by another macro node, and hands over the relay to that macro node.
+4. All ongoing traffic of the passengers in the bus e.g. Jim's video, Anna's game etc. are transferred without service interruption.
+
+#### 5.11.4.4 Post-conditions
+
+Anna's online gaming can go well during she is in the bus.
+
+Jim's video can be viewed well either during he is in the bus.
+
+Note: the use case does not assume a particular vehicle's or speed, and may apply also to users and relays inside high-speed trains (up to 500kmph). And the number of active passengers in a vehicle can be large (e.g. up to 100 in a train).
+
+#### 5.11.4.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB), cover scenarios of autonomous configuration/adaptation of network topologies, but do not assume or fully address physical relay mobility.
+
+#### 5.11.4.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.4-1] The 5G system shall be able to support efficient handover of a group of UEs' active communications when a mobile base station relay serving a group of in vehicle UEs moves between donor gNBs, ensuring end-to-end service continuity during mobility of the relay.
+
+## 5.12 Optimizing UE mobility from planned or predicted mobility information
+
+### 5.12.1 Description
+
+Urban buses of a city are equipped with a mobile base station relay i.e. Vehicle-mounted Relays (VMRs).
+
+The city provides also autonomous cars rental for moving in the centre or in the suburb of the city. Autonomous cars of the city may follow the same corridors as the city buses.
+
+Each autonomous car is equipped with a built-in UE and a roof antenna.
+
+Bob is going to work. Bob hires one autonomous car and configures the path to go to his work office in the car.
+
+Along the path to the work office, the autonomous car's UE can connect to different fixed base stations or mobile base station relays providing a better signal quality for a short period, thereby triggering a large number of handovers. This can be inefficient, since it is preferred that his car's UE selects a fixed base station or a mobile base station relay that provides good connectivity for a longer duration.
+
+To minimize the number of handovers and to provide a service continuity, the 5G system can predict the usual itinerary of a UE as well as that of neighbouring VMRs to select the best fixed base station or mobile base station relay for the UE alongside a given usual travel itinerary.
+
+In the provided use-case, the car's UE connects to the VMR of Bus 2 that follow the car's UE itinerary for an important portion of the itinerary. Should the bus stop and the car continue, then the received Bus 2 VMR signal level will drop and a new handover decision will be necessary. In this case, both signal level and the mobility information will be used as before to select another fixed base station or a mobile base station relay.
+
+### 5.12.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- a) MNO 1 operates car's UE, VMR 1 (Bus 1), VMR 2 (Bus 2), BS 1 (Base Station).
+- b) Bob is going to work and hire an autonomous car embedding a car's UE.
+- c) Bob configures the path in the autonomous car with the itinerary to work.
+- d) Car's UE is currently connected to a Base station (BS 1).
+
+### 5.12.3 Service Flows
+
+1. The car (car's UE) is following two buses, Bus 1 (VMR 1) and Bus 2 (VMR 2).
+2. The network signal conditions become better from the mobile base station relays (VMRs) than from the fixed base station (BS 1).
+3. Bus 2 will be turning left at the next corner while Bus 1 will continue to follow the same direction as Bob's car.
+4. The 5G system finds that Car's UE itinerary has a high probability of following the direction of Bus 1 (VMR 1) and a low probability of following the direction of Bus 2 (VMR 2).
+5. Car's UE connects to VMR 1.
+
+
+
+The diagram illustrates a use case for service flow. A car (car's UE) is shown on a road, with a blue arrow indicating its path. A bus (VMR1) is also on the road, with a blue arrow indicating its path. Another bus (VMR2) is shown turning left at a corner. A base station (BS 1) is shown on the left, with a signal tower icon. A factory is shown on the right. The car's path is labeled 'Bus1 path' and the bus's path is labeled 'Bus2 path'. A dashed line with an arrow points from the car to the bus, labeled 'Mobility information'.
+
+Illustration of service flow / use case showing a car, two buses (VMR1 and VMR2), a base station (BS 1), and a factory. The car is following Bus 1 (VMR1) and Bus 2 (VMR2). The diagram shows the car's path, the buses' paths, and the base station's coverage area.
+
+Figure 5.12-1: Illustration of service flow / use case
+
+### 5.12.4 Post-conditions
+
+Bob continues to attend to his conference call with his UE while being in his car.
+
+### 5.12.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] clause 6.2.2: The 5G network shall allow operators to optimize network behaviour (e.g. mobility management support) based on the mobility patterns (e.g. stationary, nomadic, spatially restricted mobility, full mobility) of a UE or group of UEs.
+
+3GPP TS 22.261 [2] clause 6.2.2: The 5G system shall enable operators to specify and modify the types of mobility support provided for a UE or group of UEs.
+
+3GPP TS 22.261 [2] clause 6.2.2: The 5G system shall support inter- and/or intra- access technology mobility procedures within 5GS with minimum impact to the user experience (e.g. QoS, QoE).
+
+### 5.12.6 Potential New Requirement needed to support the use case
+
+[PR.5.12.6-001] The 5G system shall provide means for a UE to select a suitable mobile base station relay (e.g., a mobile base station relay that has a similar trajectory as the UE).
+
+## 5.13 Use of mobile relay as secondary node
+
+### 5.13.1 Description
+
+A user served by a macro cell can enter an area where vehicles equipped with mobile base station relays are parked or running a low speed. In this case, it can be beneficial to use a suitable candidate relay to provide a simultaneous access link for the UE, e.g. enabling to increase user data rates and/or improve coverage during the time the relay is in the vicinity of the user. Keeping the simultaneous link to the macro cell can ensure that there is no interruption of service, e.g. in case the user and/or the relay move away from each other too quickly (e.g. when a parked/stationary vehicle with a mobile base station relay drives off).
+
+### 5.13.2 Pre-conditions
+
+Tom lives in a residential area within walking distance of the city center. He gets good 5G service from the macro network around his house. Tom works in the city center and likes to go to the office on foot. Often, he takes conference calls from his smartphone on his way to work.
+
+It is assumed that
+
+- Primary RAN connectivity should be provided via a macro RAN link (i.e. non relayed link, as opposed to a link via a mobile BS relay). This may increase connection quality and availability, e.g. in case macro RAN connectivity uses lower frequency bands than BS relays, or in areas where vehicles (with mobile BS relays) are moving quickly and/or may provide only temporary connectivity.
+- The RAN cell (re)selection settings are such that Tom's UE tries to camp/reselect to a macro RAN node (preferred versus a mobile base station relay), if macro RF quality is suitable. This will increase the possibility to set up a 5G connection via the macro RAN as primary link.
+- The simultaneous UE access links to the RAN (via the macro link and mobile BS relay) could be connected to the same or different RAN node(s).
+
+
+
+The diagram illustrates two scenarios of simultaneous UE connection to a RAN. In the left scenario, a 'Macro RAN & Donor node' is connected to a 'Relay' (bus) via a 'Relay-donor link' (red arrow). The 'Relay' is connected to a 'UE' (phone) via a 'UE-RS relay link' (red arrow). The 'UE' is also connected to the 'Macro RAN & Donor node' via a 'UE-macro link' (blue arrow). In the right scenario, a 'Donor node' is connected to a 'Relay' (bus) via a 'Relay-donor link' (red arrow). The 'Donor node' is also connected to a 'Macro RAN node' via a dashed line. The 'Relay' is connected to a 'UE' (phone) via a 'UE-RS relay link' (red arrow). The 'UE' is also connected to the 'Macro RAN node' via a 'UE-macro link' (blue arrow).
+
+Figure 5.13: Simultaneous UE connection to RAN (via macro link and mobile relay link).
+
+**Figure 5.13 Simultaneous UE connection to RAN (via macro link and mobile relay link)**
+
+In the service flow below, the figures show the case of same (or co-located) RAN nodes, for simplicity.
+
+### 5.13.3 Service Flows
+
+- (1) It's 7:55 am and Tom gets out of his house to walk to work. His phone camps on a macro cell on frequency f1. Tom has a conference call at 8 am so he starts the conferencing app on his phone and connects his headset.
+
+
+
+The diagram shows a city environment with buildings and a bus transit hub. A 'RAN node' is shown at the top, connected to 'Tom's phone' via a 'Uu NR' link (blue arrow). Tom's phone is also connected to a 'Relay' (bus) at the 'Bus transit hub' via a 'Uu NR' link (blue arrow). The bus is moving towards 'Downtown'. Other buses are shown on the road.
+
+Figure 5.13-1: Service flow diagram showing Tom's phone connecting to a RAN node and then to a relay bus at a bus transit hub.
+
+**Figure 5.13-1**
+
+- (2) At 8:25 am, Tom arrives in the city center. Tom's boss asks him to urgently email him documents related to the project Tom is working on, in preparation for a briefing with executives.
+- (3) Due to the high-rise buildings in the center, the macro coverage gets spotty, and due to the high number of UEs, the data rate allocated to Tom's phone starts going down. Tom starts emailing the documents to his boss but the upload speed is very slow.
+- (4) Tom arrives next to the bus transit hub, where a bus equipped with a mobile base station relay operating on frequency f2 is parked. The macro network determines that Tom's phone can get supplemental throughput from the relay in the bus and adds the relay as secondary node.
+- (5) Tom's phone regains good data rate performance, and all his documents are uploaded successfully.
+
+
+
+This diagram illustrates a network scenario at a bus transit hub. A RAN node (tower) is at the top. A UE macro link (blue arrow) connects the RAN node to a smartphone labeled 'Tom'. A UE BS relay link (red arrow) connects the RAN node to a bus labeled 'Relay'. The bus is at the 'Bus transit hub', which is represented by a building icon. Other buses are shown at the hub, and a city skyline is in the background. A label 'Uu NR' is near the RAN node.
+
+Figure 5.13-2: Network diagram showing a RAN node, a UE macro link, a UE BS relay link, a Relay (bus), and a Bus transit hub.
+
+Figure 5.13-2
+
+- (6) The driver of the bus turns on the ignition and drives out of the bus transit hub on his scheduled bus route.
+- (7) The network determines that the relay in the bus is moving away from Tom's phone, and removes the relay as secondary node, while the link to the macro cell is kept as primary node.
+
+
+
+This diagram shows the network after the bus has moved. The bus labeled 'Relay' is now further away from the 'Bus transit hub' building, with an arrow pointing left indicating its movement. The 'UE macro link' (blue arrow) from the RAN node to 'Tom' remains. The 'UE BS relay link' is no longer shown. A label 'Downtown' with an arrow points to the right, indicating the bus's direction. Other buses are still at the transit hub.
+
+Figure 5.13-3: Network diagram showing the bus (Relay) moving away from the Bus transit hub, with a 'Downtown' label.
+
+Figure 5.13-3
+
+- (8) Tom ends his conference call.
+
+### 5.13.4 Post-conditions
+
+Tom is very pleased that he was able to upload all his documents in time, while participating in the conference call without service interruption throughout his commute to work.
+
+Upon call release, based on RAN settings (as described in the pre-conditions), Tom's phone camps on the macro cell, rather than surrounding mobile base station relays.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+Current requirements (e.g. related to wireless self-backhaul, see 22.261, sec 6.12) or existing functionalities (e.g. IAB plus CA/DC), cover some scenarios of simultaneous connectivity between relay and macro nodes, and do not assume or fully address physical relay mobility.
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+[PR.5.13.6-001] The 5G system shall be able to efficiently control UE idle mode mobility when mobile base station relays are used, e.g. to facilitate UEs connecting to the macro RAN (as opposed to a vehicle relay).
+
+[PR.5.13.6-002] The 5G system shall be able to support simultaneous UE connectivity to RAN, using a direct UE access link to the macro RAN together with an access link via a mobile base station relay (e.g. mounted on a vehicle).
+
+NOTE 1: the above requirement covers the scenarios where the UE access links (to the macro RAN and via the mobile BS relay) could be connected to the same or different RAN node(s).
+
+NOTE 2: the above requirement includes supporting efficient addition and removal of a simultaneous access link, e.g. adding and removing a UE access link via a mobile base station relay while the UE is connected to the macro RAN.
+
+## 5.14 Optimized relay for in-vehicle devices
+
+### 5.14.1 Description
+
+There are scenarios where it is possible to improve performance of 5G UEs inside a vehicle, camped or connected via the vehicle relay to the 5G network, in particular when the UE is known to be located inside the vehicle. Some examples are:
+
+- Medical devices in an ambulance (pre-installed, or portable)
+- IOT/tracking devices used for goods delivery/transport, vehicle/asset monitoring, etc
+- Cameras or other multi-media devices mounted on vehicles following an outdoor sport event
+- Users' UEs that "check-in" their presence in the vehicle
+
+In some cases, e.g. for devices in ambulances, or vehicles used for multimedia applications, where UEs could be pre-installed or have fixed location, the exact position inside the vehicle, relative to the BS relay, can also be identifiable.
+
+
+
+Figure 5.14-1: Example scenarios. The diagram shows a 'Donor RAN' represented by three radio towers inside a large oval. Below the oval, there are three vehicles: a red fire truck on the left, a red car in the center, and a blue van on the right. Each vehicle has a small radio tower icon on it. Green arrows point from the fire truck's tower to the leftmost donor RAN tower. A red arrow points from the red car's tower to the central donor RAN tower. A blue arrow points from the blue van's tower to the rightmost donor RAN tower. Below the vehicles, there are two groups of city buildings, one on the left and one on the right.
+
+Figure 5.14-1: Example scenarios
+
+### 5.14.2 Pre-conditions
+
+Vehicle is equipped with a mobile BS station relay.
+
+UEs can be pre-installed in the vehicle (permanently or semi-static), or can be portable and move in and out of the vehicle.
+
+The UEs inside the vehicle, authorized to access the 5GS via the in-vehicle 5G mobile BS relay, are set to camp and connect (only or preferably) via the vehicle relay.
+
+### 5.14.3 Service Flows
+
+Pre-installed UEs are configured to access via the vehicle relay.
+
+Portable IOT devices/wearables and/or UEs can "check-in" their presence/location in the vehicle, manually (e.g. user onboard, using UE's scan or app-based check-in), or based on some form of device-relay pairing (e.g. using 3GPP direct discovery/ranging, or other mechanisms).
+
+The RAN/relay can optimize mobility configuration (e.g. minimizing/disabling reselections and handovers) and/or UE battery life (e.g. minimizing/avoiding UE measurements, etc.).
+
+Radio signal and RF power settings could also be tuned to provide best link and connectivity quality for each device, if relative position between UE and relay is known.
+
+### 5.14.4 Post-conditions
+
+UEs inside the vehicle remain camped and connected all the time via the vehicle relay, with no unnecessary reselection/handover ping-pongs (to/from macro), experiencing very good performance and/or saving battery life.
+
+### 5.14.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.14.6 Potential New Requirements needed to support the use case
+
+[PR.5.14.6-001] The 5G system shall be able to support mechanisms to optimize mobility (e.g. re-selection, handover) and energy efficiency for a UE camped or connected via a vehicle mobile BS relay (e.g. for UEs located inside a vehicle, equipped with a BS relay).
+
+## 5.15 Transient Coverage Extension
+
+### 5.15.1 Description
+
+Mobile wireless communications apply to outdoor scenarios. In remote areas, satellite access or self-backhaul provide a clear solution for extending the range of / complementing a mobile network.
+
+For indoor scenarios, beyond the point where outdoor access penetrates, currently 3GPP offers two possibilities.
+
+One is for the indoor premises to deploy non-3GPP access. Through this, a terminal can access a mobile network to get telecommunication services (or access Internet services directly.) This possibility is enabled since Release 7 (IWLAN interworking) by this and later 3GPP standards.
+
+A second possibility is to offer coverage extension, indoors – either through wireless repeaters or a fixed infrastructure in the indoors premises. This is discussed in TR 22.867, Annex A.
+
+A new possibility is presented in this use case – to make use of a number of vehicles to create a transient wireless topology of multiple vehicular relays capable of supporting indoor coverage where it would otherwise not be feasible.
+
+A similar scenario was considered in FS\_REFEC (TR 22.866, clause 6.7) as a Traffic Scenario for Public Safety. A number of firefighters penetrate a building without indoor macro cellular coverage and deploy a set of portable (UE) relays in strategic places, e.g. the top and bottom of stairwells, as they access portions of the build with poor or no coverage otherwise.
+
+In this use case, there is a large underground parking structure with no coverage nor is there an incentive or possibility (e.g. due to safety issues) to create fixed coverage extension. Other examples of this could be waste disposal sites, inactive mines, abandoned properties, search and rescue operations in challenging terrain in remote areas (e.g. caves), through underground infrastructure (e.g. sewers, water supply, transit tunnels) or building complexes where investment in coverage extension does not occur.
+
+
+
+Diagram of an underground parking garage with transient network extension. A car at 'street level' is connected to a series of mobile vehicle relay nodes (represented by small car icons with signal waves) that extend coverage down through multiple levels of the garage. The levels are labeled L1, L3, L2, L5, L4, L7, and L6 from top to bottom. Arrows indicate the path of the relays as they move deeper into the garage to provide coverage.
+
+**Figure 5.15.1-1: Underground Parking Garage with Transient Network Extension**
+
+Unlike the case studied in REFEC, this scenario involves vehicular mobile relays providing 5G coverage extension from outdoor to indoor.
+
+### 5.15.2 Pre-conditions
+
+The following are assumed to be available for this use case:
+
+- 5G macro cellular coverage to the *exterior* of the facility into which transient coverage is required, e.g. to connect users, sensors or other IoT devices in the facility. In Figure 5.x.1-1, this is the vehicle parked across the entrance of the garage;
+- a set of vehicles equipped with relays, configured to work together to provide a network topology. These vehicles could proceed autonomously, controlled remotely or be driven by personnel. In Figure 5.x.1-1, these are the mobile vehicle relay nodes.
+- a topography consisting of regions that are accessible to vehicles, portions of which need coverage, even if temporarily or ad hoc coverage. In Figure 5.x.1-1, this is the concrete (and steel) underground parking complex shown only schematically.
+
+### 5.15.3 Service Flows
+
+The mobile relays proceed into the vicinity of the facility that lacks coverage, in this case the garage. Where necessary, vehicles remain in positions that advance the coverage into the topology. Other vehicles continue, to bring coverage specifically to portions of the facility that need it. The mobile relays topology may change depending on dynamic coverage demand, e.g the vehicle relays can move or reconfigure to provide access to different areas or moving users, when and where indoor coverage is required.
+
+### 5.15.4 Post-conditions
+
+Sensors and other IoT devices in the facility (for example air quality meters in the parking garage), as well as users who need only periodic connectivity (e.g. to upload and download data opportunistically), will receive connectivity from the transient coverage extension. This will enable data collection from a range of otherwise isolated devices and other communication on a periodic basis, or as needed (e.g. during a disaster response).
+
+The service that is provided to the end systems is 3GPP service (not ProSe UE to network.)
+
+### 5.15.5 Existing features partly or fully covering the use case functionality
+
+NR Rel-16 introduces a relaying architecture enabling routing across a backhaul network of relay nodes which uses NR-Uu interface to interconnect relay nodes, enabling data transfer from network access node to the end-user, and back: IAB. In Rel-17, IAB is currently being enhanced, although relay (IAB-node) mobility is not being taken into account.
+
+### 5.15.6 Potential New Requirements needed to support the use case
+
+[PR.5.15.6-001] The 5G System shall be able to support dynamic deployment and configuration of one or more mobile base station relays (e.g. mounted on vehicles) for providing ad-hoc indoor coverage extension in specific locations.
+
+## 5.16 Non-terrestrial coverage for Mobile Vehicular Relays
+
+### 5.16.1 Description
+
+Wireless self-backhauling relays considered in 3GPP generally assume a terrestrial (fixed) base station providing wireless access to the relay nodes. In this use case, access to a very remote mobile relay is supported by means of a non-terrestrial platform.
+
+This introduces two complicating factors:
+
+- The latency for signalling across the network (between the relay nodes and the node providing access to the relay) will be much higher than in terrestrial networks.
+- The non-terrestrial platform providing relay connectivity itself may be mobile (in all cases except a GEO NTN access node.)
+
+This could be needed – for example, to support vehicular relays that are out of coverage of terrestrial networks, e.g. in remote areas. Even where terrestrial coverage exists, the vehicular relay may use satellite coverage.
+
+Where satellite access is described in this use case, both the transparent and regenerative NG-RAN architectures could apply. [y]
+
+### 5.16.2 Pre-conditions
+
+The following are assumed to be available for this use case:
+
+- 5G access is provided in a certain area by a non-terrestrial platform (e.g. a LEO, MEO satellite);
+- a set of vehicles equipped with 5G mobile BS relays, configured to obtain access from a non-terrestrial platform;
+- vehicle relays provide 5G access to UEs inside the vehicle (e.g. those UEs could be normal smartphones, without satellite capabilities.)
+
+### 5.16.3 Service Flows
+
+Two vehicles drive across a remote landscape, 100s of km from any settlement. There is no terrestrial coverage. Some vehicles are equipped to support satellite access and provide passengers of the vehicle with coverage by way of mobile vehicular relay.
+
+In Figure 1, the two vehicles are roughly 1 km apart, driving in the same direction. The satellite platform is also in motion (see the displacement during T1 to T2 – which is not drawn to scale.) Satellite access is available for both vehicles. Even as the satellite moves, the vehicles continue to be in coverage and serve their passengers with relayed coverage.
+
+
+
+Figure 5.16-1: Vehicle Relays supported by a non-stationary satellite platform. The diagram shows two vehicles, A and B, driving from left to right. Above them, a satellite is shown in three positions: T1 (initial), T2 (moved left), and T3 (moved right). Arrows indicate the satellite's movement. Coverage areas are shown as concentric ellipses around the vehicles, indicating the range of the mobile relays. The satellite's coverage area is also shown as a large ellipse.
+
+**Figure 5.16-1: Vehicle Relays supported by a non-stationary satellite platform**
+
+At T3, the black satellite will no longer be able to provide coverage to the vehicles. A separate satellite platform (shown in gray) that is part of the same satellite network *follows*. Even as the first platform cannot offer coverage, the second takes its place. There is thus *continuity* of service by means of a *sequence of transitions* to make use of different satellite platforms offering access to the vehicular mobile relays.
+
+This use case does not differentiate (at the service level) between the situation where the satellites are transparent (in which case the donor RAN is terrestrial), or whether the satellite is regenerative (in which case the donor RAN is the satellite platform itself.)
+
+### 5.16.4 Post-conditions
+
+The vehicles and their passengers are able to access telecommunication services using the satellite relay platform to connect to the remote 5G network.
+
+### 5.16.5 Existing features partly or fully covering the use case functionality
+
+NR Rel-16 introduces a relaying architecture enabling routing across a backhaul network of relay nodes which uses NR-Uu interface to interconnect relay nodes, enabling data transfer from network access node to the end-user, and back: IAB. In Rel-17, IAB is currently being enhanced, although relay (IAB-node) mobility is not being taken into account.
+
+### 5.16.6 Potential New Requirements needed to support the use case
+
+[PR5.16.6-1] The 5G System shall be able to support mobile vehicle relays using NR satellite access to connect to a remote donor RAN node via a satellite link.
+
+[PR5.x.6-2] The 5G System shall be able to support a mobile vehicle relay using NR satellite access with service continuity in the scenario where there is a transition from one serving satellite to another serving satellite.
+
+## 5.17 Vehicle Relay sharing
+
+### 5.17.1 Description
+
+A nationwide company, 5G-travels, provides long-distance bus transport service and has recently installed 5G mobile BS relays on their bus fleet, for enhanced 5G connectivity to their passengers. Two national cellular MNOs, PLMN-A and PLMN-B, already using RAN sharing in several areas of the country, make commercial arrangements with the bus company and among themselves, for sharing the use of the bus relays, such that their customers can have access to their respective HPLMN, without roaming.
+
+
+
+Diagram illustrating Multi-PLMN sharing of donor RAN and vehicle relays. A bus labeled 'Vehicle Relay' is connected to a central 'Donor RAN' cloud. The Donor RAN is connected to two separate PLMN networks, PLMN-A (orange box) and PLMN-B (blue box). Arrows indicate bidirectional communication between the Vehicle Relay and the Donor RAN, and between the Donor RAN and each PLMN.
+
+**Figure 5.17-1: Multi-PLMN sharing of donor RAN and vehicle relays**
+
+### 5.17.2 Pre-conditions
+
+The following aspects and options are assumed in this use case:
+
+- Each PLMN operator has his own 5G core network; both core networks are connected to a certain number of shared donor RAN nodes, deployed along the bus routes, which provide wireless connectivity to the vehicle relays on the buses.
+- Spectrum and RAN resources used for UEs and wireless relays access could be managed by either PLMN A or B, or by a hosting operator different from operator A or B
+- The vehicle relays will broadcast both PLMN-IDs of the sharing operators, appearing to their users/UEs like their home PLMN network.
+
+- Based on user subscription/UE identity, the shared RAN can route traffic of PLMN-A and PLMN-B customers to/from their corresponding PLMN core network.
+- It is assumed that other passengers, without subscription or roaming agreement with either PLMN-A nor B, will not get access via the bus relays. If roaming agreement is in place, in-bound roamers would also be allowed to access the vehicle relay.
+
+### 5.17.3 Service Flows
+
+Two users, from South-ville, are taking an inter-regional bus, for visiting their parents living up in North-ville, over the weekend:
+
+- Ms Red, who is a PLMN-A subscriber
+- Mr. Blue, who is a PLMN-B subscriber
+
+Before entering the bus, their UEs are connected to the fixed macro-RAN (which may or may not be shared between PLMN-A and PLMN-B), and their UEs will display “PLMN-A” and “PLMN-B”, respectively.
+
+Upon entering the bus, their UE's display shows “PLMN-A\_BUS” and “PLMN-B\_BUS”, respectively, and both users receive a short message announcing the new “enhanced 5G-bus service” offered by their respective HPLMN operator, which they can use without additional charge.
+
+During the few hours trip, both Ms Red and Mr Blue use their smartphones to keep entertained, make few calls, check emails, social media etc.
+
+### 5.17.4 Post-conditions
+
+Mr Blue and Ms Red enjoy the very good 5G connectivity and service quality during the whole trip, much better than last month's trip, when the enhance 5G-Bus service was not available.
+
+At the arrival, when leaving the bus, their UEs will re-select and/or connect from the relay to the macro-RAN (which may or may not be shared between PLMN-A and PLMN-B)
+
+### 5.17.5 Existing features partly or fully covering the use case functionality
+
+Basic support of RAN sharing is defined for 5G NG-RAN (since Rel-15), including service requirements (e.g. in 22.101) and stage-2/3 capabilities (e.g. 23.501, 38.331); nevertheless, they do not cover or assume specific consideration for the case of shared wireless access via mobile base stations.
+
+### 5.17.6 Potential New Requirements needed to support the use case
+
+[PR-5.17-1] The 5G system shall be able to support RAN sharing between multiple PLMNs for UEs connected to 5G network via mobile base station relays (e.g. mounted on vehicles)
+
+NOTE 1: the above requirement assumes that the mobile base station relays broadcast all PLMN-IDs of the sharing PLMN operators.
+
+NOTE 2: the above requirement assumes both relay and donor RAN resources, including UE access link and relay backhaul link, are shared among operators.
+
+[PR-5.17-2] The 3GPP System shall support end-to-end service continuity for a UE active connection to RAN via a mobile base station relay (e.g. mounted on a vehicle) when there is a change between a shared RAN (e.g. inside the vehicle) and a non-shared RAN (e.g. outside a vehicle), or when RAN sharing changes (for the same mobile relay) between different sharing PLMNs.
+
+## 5.18 Monitoring of vehicle-mounted relays
+
+### 5.18.1 Description
+
+A transportation company CityBus owning a fleet of public buses equipped with mobile base station relays wants to identify the most in-demand/out-of-demand itineraries, peak/off-peak hours, areas with poor 5G connectivity.
+
+The 5G network constantly logs some statistics data related to mobile base station relays on the buses for example, number of UEs connected at the moment, amount of traffic relayed, current location, etc. This kind of data can be helpful for CityBus to improve and optimize its transportation system e.g., add new routes or change existing routes, ask the serving MNO to deploy additional terrestrial base stations along the itineraries for better 5G connectivity/coverage.
+
+### 5.18.2 Pre-conditions
+
+To enable this use, following pre-conditions should be met:
+
+- Buses of CityBus are equipped with 5G mobile base stations relays.
+- The 5G network is capable to monitor mobile base station relays and periodically generate monitoring data. The features to capture in the monitoring data and the periodicity of generating them are configured by CityBus.
+- CityBus is authorized to collect monitoring data for the mobile base station relays. The monitoring data can be collected in real-time as soon as a new monitoring record is generated or for a specified period of time.
+- CityBus has a commercial agreement with a serving MNO to monitor mobile base station relays and collect monitoring data via its network.
+
+### 5.18.3 Service Flows
+
+1. The 5G network monitors all mobile base station relays installed on CityBus's buses as configured by CityBus.
+2. CityBus retrieves the monitoring data from the 5G network.
+3. CityBus analyses the retrieved data and identifies that some routes are more in-demand and require buses to run more frequently. Additionally, some areas along some itineraries with poor 5G connectivity are identified.
+
+### 5.18.4 Post-conditions
+
+CityBus deploys more buses for identified on-demand routes and the serving MNO deploys additional base stations in identified areas with poor 5G connectivity. Passengers of CityBus are happy that buses are less crowded and enjoy improved 5G experience now.
+
+### 5.18.5 Existing features partly or fully covering the use case functionality
+
+The 5G system shall provide a mechanism for supporting real time E2E QoS monitoring within a system.
+
+The 5G system shall be able to provide real time QoS parameters and events information to an authorized application / network entity.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
+
+Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party.
+
+Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party.
+
+### 5.18.6 Potential New Requirements needed to support the use case
+
+[PR 5.18-1] The 5G system shall support means to expose monitoring information of a mobile base station relay (e.g. number of UEs connected, QoS, geographical location, time of data monitoring/collection, etc.) to an authorized third-party based on monitoring parameters configured by the authorized third-party (e.g. data to monitor/collect, periodicity/schedule of monitoring, etc.).
+
+**Editor's note: The requirement will be considered during consolidation phase, taking into account the existing mechanism of network capability exposure.**
+
+## 5.19 Simultaneous connectivity via multiple mobile BS relays
+
+### 5.19.1 Description
+
+In certain scenarios, where the UE is in the proximity of multiple mobile BS relays, it maybe convenient to use simultaneous connectivity to the macro RAN via more than one BS relay, e.g. to improve data rate, latency and/or increase communication reliability or robustness.
+
+One example, already described in other use case (sec 5.11.2.2), is the outdoor sport race/event, where 5G UEs (e.g. cameras), mounted on motorbikes' following the race, transmit real-time video via relays mounted on alongside vehicles, e.g. provided by the event organizer or TV broadcaster.
+
+
+
+The diagram shows a UE (camera) on a motorbike moving to the left, as indicated by a large blue arrow labeled 'Sport race direction'. The UE is connected to a 'Relay' mounted on a car. The relay is connected to a 'Donor gNB 1'. Another 'Donor gNB 2' is shown on the left, not connected to the UE. The UE and the relay are both connected to the same donor gNB (Donor gNB 1).
+
+Diagram illustrating a single radio link via a mobile BS relay. A UE (camera) on a motorbike is connected to a relay mounted on a car. The relay is connected to a donor gNB (Donor gNB 1). A large blue arrow indicates the 'Sport race direction' pointing left. Another donor gNB (Donor gNB 2) is shown on the left, not connected to the UE.
+
+**Fig. 5.19-1 Single radio link via mobile BS relay**
+
+In this scenario, depending on the radio conditions, required QoS, and available itinerary information, e.g. on number of vehicles with onboard relays planned to follow the race (maybe different in different parts of the itinerary), the network can decide to exploit simultaneous UE connectivity via two nearby mobile relays, if/when suitable.
+
+### 5.19.2 Pre-conditions
+
+5G UEs/cameras, and mobile BS relays mounted on vehicles, are provided by a local TV broadcaster, all pre-provisioned and configured to connect to a certain 5G PLMN network, with a sufficient RAN coverage for the mobile BS relays via dedicated donor RAN nodes covering the sport race itinerary. It is assumed that both relays and donor RAN nodes are part of the same PLMN.
+
+### 5.19.3 Service Flows
+
+1. The race is ongoing, and a certain UE (camera) is connected via one mobile BS relay mounted on a surrounding vehicle (from the TV broadcaster), as shown in figure 1.
+
+2. After a while, e.g. when the road size get larger, a second vehicle, equipped with a mobile BS relay from the TV broadcaster, approaches the peloton and the UE.
+
+RAN, based on RF measurements, mobility configuration, or other available information (e.g, the identified additional vehicle will be within a close distance from the UE for a certain amount of time/itinerary), decides to add a simultaneous radio link, for that UE, via the second vehicle's mobile relay .
+
+The two simultaneous mobile relay links could be connected to the same or different donor RAN node, as illustrated below.
+
+
+
+Figure 5.19-2: Simultaneous radio links via multiple mobile BS relays. The diagram shows two scenarios. The left scenario shows a single 'Donor node' connected to a 'UE' via two 'Relay' nodes (Relay1 and Relay2) mounted on vehicles. Red arrows represent 'Relay-Donor links' from the donor to the relays, and blue arrows represent 'UE-BS relay links' from the relays to the UE. The right scenario shows two 'Donor nodes' (Donor node1 and Donor node2) connected to a 'UE' via two 'Relay' nodes (Relay1 and Relay2) mounted on vehicles. Red arrows represent 'Relay-Donor links' from the donor nodes to the relays, and blue arrows represent 'UE-BS relay links' from the relays to the UE.
+
+**Fig. 5.19-2 Simultaneous radio links via multiple mobile BS relays**
+
+3. Later on, e.g. when the road gets narrower and/or one of the vehicles moves away from the UE, the RAN may remove the corresponding mobile BS relay link.
+
+### 5.19.4 Post-conditions
+
+UE connectivity and performance can exploit more robust and better performance using simultaneous mobile BS relay links, when multiple nearby vehicles are available.
+
+### 5.19.5 Existing features partly or fully covering the use case functionality
+
+Maybe partly covered by existing IAB, and related DC/CA functionalities, which do not assume full mobility of the relay nodes.
+
+### 5.19.6 Potential New Requirements needed to support the use case
+
+[PR 5.19-1] The 5G system shall be able to support simultaneous UE connectivity to RAN using multiple access links provided via different mobile base station relays (e.g. mounted on different vehicles).
+
+NOTE 1: The above requirement covers scenarios where the UE access links (via the mobile BS relays) could be connected to the same or different RAN node(s), assuming both relay and donor RAN node(s) belong to the same PLMN,
+
+NOTE 2: The above requirement includes supporting efficient addition and removal of a simultaneous access link via a mobile base station relay, while the UE is connected to the RAN via another mobile base station relay.
+
+[PR 5.19-2] The 5G system shall be able to support, for a UE simultaneously connected to RAN via different mobile base station relays (e.g. mounted on vehicles), service continuity during various mobility events, e.g. when the connected mobile BS relays and/or the macro donor node(s) change.
+
+## 5.20 Using a partner 5G network to transport vehicle relay traffic
+
+### 5.20.1 Description
+
+This use case covers certain deployment scenarios where traffic exchanged via vehicle relays for users of one MNO or service provider is carried over a transport 5G network managed by a second MNO. An example is illustrated in fig.1, where the MNO2 provides wireless access and transport between vehicle relays and the MNO1 5G network, allowing E2E connectivity to MNO1 users.
+
+
+
+Diagram illustrating mobile relays traffic from MNO-1 transported over MNO-2's network. A Vehicle Relay inside a car connects to an MNO1 User via a Uu interface. The Vehicle Relay connects to an MNO2 RAN via an MNO2 Uu interface. The MNO2 RAN connects to an MNO2 5GC via an MNO2 PDU session. The MNO2 5GC connects to an MNO1 5G NW via an MNO2 NG interface. The MNO1 5G NW connects to the MNO1 User via an MNO1 traffic interface. The diagram shows the flow of MNO1 traffic from the MNO1 User through the Vehicle Relay, MNO2 RAN, MNO2 5GC, and MNO1 5G NW.
+
+**Fig 5.20-1: Example of mobile relays traffic from MNO-1 transported over MNO-2's network.**
+
+Such scenarios can be based on business agreements among the two parties, specific NW deployment/operational constraints, coverage requirements, etc. For example, it could be used for:
+
+- A 5G mobile operator (MNO1), with limited macro-RAN deployment and coverage footprint, willing to exploit their spectrum to offer 5G access and services to their subscribers (travelling in vehicles, or located in specific hotspot areas). MNO1 could decide to leverage the better/ubiquitous 5G wireless (and transport) connectivity provided by a second operator (MNO2) to tunnel the MNO1 traffic to/from the vehicle relays.
+- Public Safety providers or other service/fleet operators, who could manage specific vehicles with on-board relays, together with ad-hoc 5G subscriptions and connectivity services for certain user categories, e.g. for first-responders, delivery personnel, public passengers etc. They may not necessarily own 5G spectrum, or RAN/network infrastructure, thus using MNO2's mobile network to reach connectivity to their relays (and users).
+
+### 5.20.2 Pre-conditions
+
+For this use case, the following options are assumed:
+
+- The access link between MNO1 UEs and the vehicle relay uses MNO1 spectrum; the relay can connect to the MNO2 RAN using MNO2 spectrum.
+- The MNO2 transport connection, between the vehicle relay and the MNO1 network, is used to carry relay traffic between the vehicle relay and MNO1 5GC.
+
+### 5.20.3 Service Flows
+
+1. Vehicle relays are provisioned and configured to register to the MNO2 network and establish necessary PDU session(s), with certain quality of service and policies (as negotiated for MNO1 traffic and subscribers).
+2. Vehicle relays are provisioned and configured to connect to the donor MNO1 network for communication between MNO1 users and MNO1 network.
+3. MNO1 subscribers/UEs inside the vehicle camp on the mobile relays, which will broadcast MNO1 PLMN-ID, and are able to register and connect to the MNO1 network.
+4. All traffic generated via vehicle relays by MNO1 UEs is tunnelled through the established relays' MNO2 5G connectivity.
+
+### 5.20.4 Post-conditions
+
+MNO1 users can exploit their 5G service and the good in-vehicle 5G coverage/connectivity provided by the vehicle relays, fully transparently.
+
+### 5.20.5 Existing features partly or fully covering the use case functionality
+
+TS23.501 (Annex D) describes the concept of overlay network connection on top of underlay network connection, which does not fully cover the target use case and requirements, intended to be specific to mobile BS relays.
+
+### 5.20.6 Potential New Requirements needed to support the use case
+
+[PR 5.20-1] The 5G system shall be able to support communication from/to users of one MNO (MNO-A) via mobile vehicle base station relays, where the relayed traffic is transported to/from the MNO-A network using 5G connectivity (RAN and 5GC) provided by a different MNO (MNO-B).
+
+NOTE 1: the above requirement includes support of necessary policies and provisioning for end-to-end user's QoS, e.g. based on MNO-A user/UE's subscription.
+
+NOTE 2: the 5G transport and connectivity provided by the different MNO (MNO-B) assumes a generic wireless BS backhaul, independent from the BS relay functionalities.
+
+## 5.21 Improved connectivity based on the relay mobility pattern
+
+### 5.21.1 Description
+
+Vehicles with onboard base stations, so called vehicle-mounted relays (VMR), are expected to act as relay and help provide efficient data delivery. This use case addresses the needs of users who are not moving with the vehicle-mounted relay but that can benefit from its offered connectivity when users and vehicle-mounted relays are close.
+
+In particular, this use case addresses the needs of those UEs that either have limited connectivity (e.g., when connected to a macro cell) or that have too demanding bandwidth needs.
+
+Our first use case is about a user, Tom, an emergency physician who just arrived at a car accident. Tom is attending several injured persons. Tom is having a call with other clinicians at a close-by hospital discussing the health state of the patients and to which hospital the patients should be transferred. Tom would also like to retrieve the Electronic Health Record (EHR) of the patients to do a better assessment. However, the network connectivity at his current location – the accident area -- is insufficient, in particular, to download some bulky files in the EHR of the patients. In this situation, it is beneficial if the 5G system can *schedule* the transfer of the EHR content requested by Tom so that the EHR is transferred by means of a relay mounted on one of the ambulances approaching the accident area. This example is shown in Figure x-1 where the ambulance is denoted AMR, i.e., Ambulance-Mounted Relay. In Figure x-1 Tom's UE is denoted UE. At location L0 and time T0 the EHR data transfer is requested by the UE. The data is then transferred when the AMR is at location L2 since at this location the communication link between donor gNB and AMR and between AMR and UE offer the best end-to-end performance. The location is chosen by using, known or predicted, the AMR mobility pattern to optimize the network behaviour. In some cases, the AMR could receive the EHR data from the donor gNB at location L1 and time T1 and when the AMR is at location L3 at time T3, the AMR could rapidly deliver the requested EHR data to Tom's UE. In this alternative approach, the locations L1 and L3 are chosen to optimize the individual link performance between donor gNB and AMR and between AMR and UE. The choice of these locations is also based on the known or predicted AMR mobility pattern.
+
+
+
+The diagram illustrates a scenario where an Ambulance-Mounted Relay (AMR) is moving from left to right, indicated by a dashed orange arrow. The AMR is shown at three positions: L1 (T1), L2 (T2), and L3 (T3). A User Equipment (UE) is shown at position L0 (T0). A donor gNB is shown in the top right. Arrows indicate the flow of data transfer: from the donor gNB to the AMR at location 1 (L1, T1), from the AMR at location 1 to the UE at location 2 (L2, T2), and from the AMR at location 2 to the UE at location 3 (L3, T3). The diagram also shows the AMR at location 2 (L2, T2) and location 3 (L3, T3).
+
+Figure 5.21-1. Example scenario diagram showing the movement of an Ambulance-Mounted Relay (AMR) and a User Equipment (UE) relative to a donor gNB. The diagram illustrates three potential data transfer points: location 1 (L1, T1), location 2 (L2, T2), and location 3 (L3, T3). The donor gNB is shown in the top right. The AMR is shown at three positions: L1 (T1), L2 (T2), and L3 (T3). The UE is shown at L0 (T0). Arrows indicate the flow of data transfer from the donor gNB to the AMR and then to the UE at different locations.
+
+Figure 5.21-1. Example scenario
+
+Other relevant and related use cases include:
+
+- IoT devices requiring the delivery of a software update. Some IoT devices might lack a good connection but be able to retrieve the software update from a vehicle-mounted relay, when it is close by.
+- Users requiring access to bulky resources, e.g., a movie, but with insufficient connectivity at their current location. Users might retrieve the files from an approaching vehicle-mounted relay selected based on the mobility pattern of the VMR.
+
+### 5.21.2 Pre-conditions
+
+- An MNO operates AMRs and macro cells in a city.
+- The user, Tom, has a UE and is subscribed to the MNO.
+- The user, Tom, is connected to a macro base station and Tom needs to retrieve certain files.
+
+### 5.21.3 Service Flows
+
+- Tom is connected to the 5G macro network.
+- Tom performs a call and tries to retrieve the EHR files of the patients.
+- The 5G macro network is capable of delivering Tom's normal communication needs, in particular, low bandwidth communication needs. The 5G macro network offers limited capacity for the download of large amounts of data due to spotty coverage and a high number of UEs at Tom's location.
+- The MNO operates AMRs that offer extra additional capacity. The mobile network determines that the download needs of our user Tom can be fulfilled by an AMR, an ambulance, approaching Tom's location.
+- The 5G system delivers the downlink traffic required by Tom to the ambulance that is approaching Tom's location. The transfer of this EHR content to the ambulance and from the ambulance to Tom's UE is done very fast since this is done where and when the communication links between macro gNB, AMR, and UE are expected to offer the best performance based on the known or predicted mobility pattern of the AMR.
+- When the ambulance moves away, Tom's UE releases its connection with the AMR.
+
+### 5.21.4 Post-conditions
+
+- Tom was able to retrieve the required EHR files in an efficient way so that he can attend the patients properly.
+
+### 5.21.5 Existing features partly or fully covering the use case functionality
+
+From Section 6.2.2 of TS 22.261: *“The 5G network shall allow operators to optimize network behaviour (e.g. mobility management support) based on the mobility patterns (e.g. stationary, nomadic, spatially restricted mobility, full mobility) of a UE or group of UEs.”* However, this requirement is not based on mobility information of vehicle-mounted relays.
+
+Section 6.6 (Efficient content delivery) of TS 22.261 includes various requirements on efficient content delivery. However, these requirements are not based on mobility information of vehicle-mounted relays.
+
+### 5.21.6 Potential New Requirements needed to support the use case
+
+[PR 5.21-1] The 5G system shall be able to provide a means to optimize network behaviour to efficiently deliver data based on the mobility information (e.g., itinerary), known or predicted, of the vehicle-mounted relays.
+
+## 5.22 Mobility between Non-terrestrial coverage and terrestrial coverage for Mobile Vehicular Relays
+
+### 5.22.1 Description
+
+In section 5.16, use case for Non-terrestrial coverage for Mobile Vehicular Relays has been specified.
+
+In actual 5G deployment, some areas could be covered by both non-terrestrial coverage and terrestrial coverage, and some area areas are only covered by either the non-terrestrial coverage and terrestrial coverage.
+
+It could be good to support mobility of mobile vehicular relays between non-terrestrial coverage and terrestrial coverage
+
+### 5.22.2 Pre-conditions
+
+The following are assumed to be available for this use case:
+
+- 5G non-terrestrial access is provided in a area A by a non-terrestrial platform (e.g. a LEO, MEO satellite) of one PLMN named O;
+- 5G terrestrial access is provided in a area B by a terrestrial (fixed) base station of same PLMN O;
+- 5G non-terrestrial and terrestrial access is provided in an area C, with is the overlapped area of A and B, by a terrestrial access of one PLMN;
+- One vehicle named V equipped with 5G mobile BS relays, is able to obtain access from a non-terrestrial platform and a terrestrial access of one PLMN;
+- The vehicle relays provide 5G access to UEs inside the vehicle and UEs nearby the vehicle (e.g. those UEs could be normal smartphones, without satellite capabilities.)
+
+### 5.22.3 Service Flows
+
+The vehicle V equipped with 5G mobile BS relays locates within area A, and connect via non-terrestrial access to PLMN O, and provide the 5G access to UEs inside the vehicle.
+
+The vehicle V drive within area A but heading to area B, then it moves into area C where both 5G non-terrestrial access and terrestrial access are available.
+
+Since vehicle V equipped with 5G mobile BS relays detected there is both 5G non-terrestrial access and terrestrial access, and based on some criteria the 5G mobile BS relays decides to using terrestrial access to connect to 5GC. The criteria includes operator policy, signal strength of the access and etc.
+
+
+
+The diagram shows a satellite in the top left connected by a dashed line to a cloud labeled '5G Core Network PLMN O'. Below, three regions are depicted: 'Area-A' (dotted pattern), 'Area-B' (hatched pattern), and 'Area-C' (overlapped area). A bus icon labeled 'Move Direction' is shown in Area-A, moving towards Area-C. Another bus icon is in Area-C, with a solid blue arrow pointing to a terrestrial base station in Area-B. A third bus icon is also shown in Area-B. The satellite has a dashed line pointing to the bus in Area-C, and a solid blue arrow pointing to the bus in Area-B.
+
+Diagram illustrating vehicle relays moving from a non-terrestrial access area to a terrestrial access area.
+
+Figure 5.22-1: Vehicle Relays move from a non-terrestrial access area to terrestrial access area
+
+During the “relay switch”, that is a period that 5G mobile BS relays switch from using the 5G non-terrestrial access to using the 5G terrestrial access to connect to 5GC, the 5G mobile BS relays continue to provide the 5G access to UEs inside the vehicle.
+
+After this “relay switch”, the vehicle V equipped 5G mobile BS relays drives in area B and provide the 5G access to UEs inside the vehicle.
+
+### 5.22.4 Post-conditions
+
+The vehicle V equipped with 5G mobile BS relays using 5G terrestrial access connect to 5GC, and provide the 5G access to UEs inside the vehicle.
+
+### 5.22.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.22.6 Potential New Requirements needed to support the use case
+
+[PR 5.22.6-1] The 5G System shall be able to support mobile base station relays using NR satellite access and using NR terrestrial access to connect to 5GC.
+
+[PR 5.22.6-2] The 5G System shall be able to support a mobile base station relay capable using both NR satellite access and NR terrestrial access with service continuity in the scenario when this mobile base station relay switch from using NR satellite access to using NR terrestrial access, and vice versa.
+
+## 5.23 Mobile Vehicular Relays using Non-terrestrial and terrestrial access simultaneously
+
+### 5.23.1 Description
+
+In section 5.16, use case for Non-terrestrial coverage for Mobile Vehicular Relays has been specified.
+
+In actual 5G deployment, some areas could be covered by both non-terrestrial coverage and terrestrial coverage.
+
+It could be good to support of mobile vehicular relays using non-terrestrial access and terrestrial access simultaneously to connect to 5GC.
+
+### 5.23.2 Pre-conditions
+
+The following are assumed to be available for this use case:
+
+- 5G non-terrestrial access is provided in an area A by a non-terrestrial platform (e.g. a LEO, MEO satellite) of one PLMN named O;
+- 5G terrestrial access is provided in an area B by a terrestrial (fixed) base station of same PLMN O;
+- Area A and area B are largely overlapped;
+- One vehicle named X equipped with 5G mobile BS relays, is able to using access from a non-terrestrial platform and a terrestrial access at same time;
+- The vehicle relays provide 5G access to UEs inside the vehicle and UEs nearby the vehicle (e.g. those UEs could be normal smartphones, without satellite capabilities.)
+
+### 5.23.3 Service Flows
+
+The vehicle X equipped with 5G mobile BS relay locates within area A, it detects the access could be used to 5GC. Then it decides to connect via terrestrial access to PLMN O. Once successes, it then provide the 5G access to UEs inside the vehicle.
+
+Due to some reasons, e.g. UE amounts accesses increase, huge demand of bandwidth, the vehicle X find that total bandwidth of current relay link could not meet above demands, and then vehicle X decides to use the non-terrestrial access as relay link.
+
+The vehicle X then detect whether there is non-terrestrial access coverage. If yes, the vehicle X equipped with 5G mobile BS relay connect to the PLMN O. If it is authorised to provide 5G access to UEs, then more UEs and more bandwidths requirements could be meet. That is, more and more UE could access the network via this vehicle X equipped with 5G mobile BS.
+
+The vehicle X equipped with 5G mobile BS monitors the usage of the relay link, and once the service demand decrease, it then decides to dis-connect one relay link, e.g. it dis-connect the terrestrial access link.
+
+The vehicle X also monitors the radio coverage. For example, if there is no terrestrial access available, or the radio conditions of terrestrial access deteriorates, the vehicle X has no choice but to dis-connect the terrestrial access link
+
+
+
+Diagram illustrating vehicle relays using non-terrestrial and terrestrial access simultaneously. A vehicle (bus) is shown in Area-A, connected to a 5G Core Network (PLMN O) via a satellite (non-terrestrial access) and a base station (terrestrial access) in Area-B. The vehicle is connected to the satellite via a dashed line, and the satellite is connected to the 5G Core Network via a solid line. The vehicle is also connected to the base station via a dashed line, and the base station is connected to the 5G Core Network via a solid line. The vehicle is shown with a 5G mobile BS, and the base station is shown with a 5G mobile BS. The diagram shows the vehicle (bus) in Area-A connected to a 5G Core Network (PLMN O) via a satellite (non-terrestrial access) and a base station (terrestrial access) in Area-B. The vehicle is connected to the satellite via a dashed line, and the satellite is connected to the 5G Core Network via a solid line. The vehicle is also connected to the base station via a dashed line, and the base station is connected to the 5G Core Network via a solid line. The vehicle is shown with a 5G mobile BS, and the base station is shown with a 5G mobile BS.
+
+**Figure 5.23-1: Vehicle Relays using non-terrestrial access and terrestrial access simultaneously**
+
+### 5.23.4 Post-conditions
+
+The vehicle X equipped with 5G mobile BS relays using both 5G terrestrial access and non-terrestrial access connect to 5GC, and provide the 5G access to UEs inside the vehicle and UEs nearby the vehicle (e.g. those UEs could be normal smartphones, without satellite capabilities).
+
+### 5.23.5 Existing features partly or fully covering the use case functionality
+
+Current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays.
+
+### 5.23.6 Potential New Requirements needed to support the use case
+
+[PR 5.23.6-1] The 5G System shall be able to support mobile base station relays capable of connecting via both NR satellite access and NR terrestrial access, to select one access as a relay link between the mobile base station relays and the 5GC.
+
+[PR 5.23.6-2] The 5G System shall be able to support mobile base station relays capable of connecting simultaneously via NR satellite access and NR terrestrial access as relay link to connect via both to 5GC at the same time.
+
+[PR 5.23.6-3] The 5G System shall be able to support mobile base station relays capable of connecting in parallel via NR satellite and NR terrestrial access to add a second relay link to allow more UEs to access the network and e.g. to adapt to increased bandwidths demand for access via this mobile base station relay.
+
+[PR 5.23.6-4] The 5G System shall be able to support mobile base station relays connected via both NR satellite and NR terrestrial access to remove one of two relay links to adapt to decreased bandwidths demand of UEs accessing via this mobile base station relay.
+
+[PR 5.23.6-5] The 5G System shall be able to support mobile relay traffic load balancing across satellite and terrestrial access links, for mobile base station relays that use both NR satellite access and NR terrestrial access as relay link at the same time.
+
+Note 1: The simultaneous satellite and terrestrial access links (from the relay) are assumed to carry traffic pertaining to different UEs.
+
+# --- 6 Other considerations
+
+This section includes other aspects of mobile vehicle relays deployments and potential service requirements, not specifically covered by the use cases and requirements described in the section 5, particularly related to:
+
+- The possibility for a relay to have a HPLMN subscription, and roam into other networks, together with the need to have proper control from both home and visited PLMNs;
+- The need to potentially support regulatory requirements, including emergency services;
+- The ability to support priority services, such as MPS;
+- The expected support of end-to-end security;
+- The ability to avoid or overcome challenges related to radio interference.
+
+Corresponding new potential service requirements are captured below.
+
+[PR 6-1a] The 5G System shall support means for a mobile base station relay to have a subscription with a HPLMN, used to get access and connectivity to the HPLMN 5GC (via a donor RAN).
+
+[PR 6-1b] The 5G System shall support the ability of a base station relay to roam from its HPLMN into a VPLMN.
+
+[PR 6-1c] The 5G system shall support mechanisms, for the HPLMN controlling a mobile base station relay, to enable/disable mobile relay operation if/when the relay (e.g. on a mobile vehicle) is roaming in a VPLMN.
+
+[PR 6-1d] The 5G system shall support mechanisms to disable mobile relay operation by VPLMN where a mobile base station relay is roaming to.
+
+[PR 6-2] The 5G system shall be able to fulfil necessary regulatory requirements (e.g. for support of emergency services) when UEs access the 3GPP network via a mobile base station relay.
+
+[PR 6-3] The 5G system shall be able to support priority services (e.g. MPS) when UEs access the 3GPP network via a mobile base station relay.
+
+[PR 6-4] The 5G system shall ensure that end-to-end 5G security between the UE and 3GPP network is supported when the UE accesses the 3GPP network via a mobile base station relay.
+
+[PR 6-5] The 5G system shall be able to minimize radio interference possibly caused by mobile base station relays (e.g. when mounted on moving vehicles).
+
+# --- 7 Potential Consolidated Requirements
+
+## 7.0 Introduction
+
+The requirements below refer to a “*mobile base station relay*” (or mobile BS relay), which is a mobile base station acting as a relay between a UE and the 5G network, i.e. providing a NR access link to UEs and connected wirelessly (using NR) through a donor NG-RAN to the 5G Core. Such mobile BS relay is assumed to be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle).
+
+NOTE: the radio link used between a mobile BS relay and served UEs, as well as between mobile BS relay and donor RAN, is assumed to be NR-Uu; in that regard, it should be clear that a mobile BS relay is different than a UE relay (which uses instead a PC5-based link to provide indirect connection to remote UEs).
+
+Few main underlying assumptions and notes (from the TR overview and gap analysis) are:
+
+- use cases and requirements cover single-hop relay scenarios as baseline (multi-hop is not precluded);
+- legacy UEs are supported;
+- current stage-1 requirements (e.g. on wireless self-backhaul, in TS 22.261), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. BS relays on board of moving vehicles), thus may not cover the identified new potential requirements, which are intended to be specific to mobile BS relays;
+- The identified requirements do not intend to imply or exclude specific network/relay architectures and topology solutions (e.g. could be IAB based, or others).
+
+## 7.1 General requirements
+
+**Table 7.1-1 – General Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------|
+| CPR 7.1-1 | The 5G system shall support efficient operation of mobile base station relays. | PR 5.1-1, 5.3-1, 5.6-1, 5.8-1 | |
+| CPR 7.1-2 | The 5G system shall be able to support means, for a mobile network operator, to configure, provision and control the operation of a mobile base station relay, e.g. activation/deactivation, permitted location(s) or time of operation. | PR 5.1-2, 5.2-2, 5.2-3 | |
+| CPR 7.1-3 | The 5G system shall be able to support provisioning and configuration mechanisms to control UEs' selection and access to a mobile base station relay, e.g. based on UE's authorization, geographic or temporary restrictions, relay's load | PR 5.2-1, 5.4-1, 5.3-2, 5.5-1 | |
+| CPR 7.1-4 | The 5G System shall be able to support mobile base station relays using 3GPP satellite NG-RAN. | PR 5.16.6-1 | |
+| CPR 7.1-5 | The 5G system shall be able to support RAN sharing between multiple PLMNs for UEs connected to the 5G network via mobile base station relays.
NOTE 1: the above requirement assumes both relay and (donor) RAN resources, including UE access link and relay backhaul link, are shared among operators | PR 5.17-1 | |
+| CPR 7.1-6 | The 5G system shall be able to configure and provision specific required QoS for traffic relayed via a mobile base station relay.
NOTE 2: QoS is end-to-end, i.e. from UE to 5GC. | PR 5.10-1 | |
+| CPR 7.1-7 | Subject to regulatory requirements and based on operator policy, the 5G system shall support means to configure and expose monitoring information of a mobile base station relay to an MNO's authorized third-party. | PR 5.18-1 | |
+| CPR 7.1-8 | The 5G system shall be able to support incremental deployment of connectivity by means of one or a series of mobile base station relays for use only in specific locations where UEs would receive no other 3GPP access (terrestrial or non-terrestrial) coverage, e.g., for public safety scenarios. | PR 5.15.6-1 | |
+| CPR 7.1-9 | The 5G system shall be able to provide means to optimize network behaviour to efficiently deliver data based on the mobility information (e.g., itinerary), known or predicted, of mobile base station relays. | PR 5.21-1 | |
+| CPR 7.1-10 | The 5G system shall be able to support communication from/to users of one MNO (MNO-A) via mobile base station relays, where the traffic between the relay and the MNO-A network is transported using 5G connectivity (RAN and 5GC) provided by a different MNO (MNO-B).
NOTE 3: The 5G connectivity provided to the MNO-A relays by the different MNO (MNO-B) assumes a generic wireless backhaul transport, independent from the mobile BS relay functionalities. | PR 5.20-1 | |
+
+## 7.2 Multi-link connectivity
+
+**Table 7.2-1 – Multi-link connectivity Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------|
+| CPR 7.2-1 | The 5G system shall be able to support UEs connectivity to RAN using simultaneously, a link without mobile BS relay and a link via a mobile BS relay, or simultaneous links via different mobile BS relays.
NOTE 4: the above requirements cover scenarios where the two links (to the RAN) could be connected to the same or different RAN node(s), and assuming both relay and RAN belong to the same PLMN.
| PR 5.13.6-2, 5.19-1 | |
+| CPR 7.2-2 | The 5G system shall be able to support mobile base station relays accessing to 5GC via NR satellite access and NR terrestrial access simultaneously.
| PR 5.22.6-1, 5.23.6-1/2/3/4/5 | |
+
+## 7.3 Mobility
+
+**Table 7.3-1 – Mobility Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|---------|
+| CPR 7.3-1 | The 5G system shall be able to provide means to support efficient UE cell selection and cell reselection (between mobile BS relays or between relays and RAN) in the presence of mobile base station relays.
| PR 5.7-1, 5.12.6-1, 5.13.6-1 | |
+| CPR 7.3-2 | The 5G system shall be able to support mechanisms to optimize mobility and energy efficiency for UEs located in a vehicle equipped with a base station relay.
NOTE 4a: The above requirements cover scenarios where mobile base station relays provide 5G access for both UEs in the vehicle and around the vehicle.
| PR 5.14.6-1 | |
+| CPR 7.3-3 | The 5G system shall be able to ensure end-to-end service continuity, in the presence of mobile base station relays
NOTE 5: the above requirement intends to cover different scenarios of UE mobility (e.g. UE moving between two mobile BS relays, or between macro RAN and BS relay) and BS relay mobility (e.g. BS relay moving between different donor RAN nodes).
| PR 5.7-2, 5.6-2, 5.11.1-1/2, 5.11.2-1/2, 5.11.3-1/2, 5.11.4-1, 5.13.6-1, 5.17-2, 5.19-2 | |
+| CPR 7.3-4 | The 5G System shall be able to support service continuity for mobile base station relays using at least one 3GPP satellite NG-RAN.
NOTE 6: This requirement applies to scenarios where there is a transition between two 3GPP NG-RAN, operated by the same MNO, involving at least one 3GPP satellite NG-RAN.
| PR 5.16.6-2, 5.22.6-2 | |
+
+## 7.4 Charging
+
+**Table 7.4-1 – Charging Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------|
+| CPR 7.4-1 | The 5G system shall be able to identify and differentiate UEs' traffic carried via a mobile base station relay and collect charging information, including specific relay information (e.g. geographic location served by the relay).
| PR 5.10-2, 5.10-3, 5.10-4 | |
+
+## 7.5 Other aspects
+
+**Table 7.5-1 – Other Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------------|
+| CPR 7.5-1 | The 5G System shall support means for a mobile base station relay to have a certain subscription with a HPLMN, used to get access and connectivity to the HPLMN network (via a donor RAN). | PR 6-1a | |
+| CPR 7.5-2 | The 5G System shall support the ability of a base station relay to roam from its HPLMN into a VPLMN. | PR 6-1b | |
+| CPR 7.5-3 | The 5G system shall support mechanisms, for the HPLMN controlling a mobile base station relay, to enable/disable mobile relay operation if the relay is roaming in a VPLMN. | PR 6-1c | |
+| CPR 7.5-4 | The 5G system shall support mechanisms to disable mobile relay operation by a VPLMN where a mobile base station relay is roaming to | PR 6-1d | |
+| CPR 7.5-5 | The 5G system shall be able to fulfil necessary regulatory requirements (e.g. for support of emergency services) when UEs access the 3GPP network via a mobile base station relay. | PR 6-2 | |
+| CPR 7.5-6 | The 5G system shall be able to support priority services (e.g. MPS) when UEs access the 3GPP network via a mobile base station relay. | PR 6-3 | |
+| CPR 7.5-7 | The 5G system shall be able to support location services for the UEs accessing 5GS via a mobile base station relay. | PR 5.9-1, 5.9-2 | |
+| CPR 7.5-8 | The 5G system shall ensure that existing end-to-end 5G security between the UE and 3GPP network is unaffected when the UE accesses the 3GPP network via a mobile base station relay. | PR 6-4 | |
+| CPR 7.5-9 | The 5G system shall be able to minimize radio interference possibly caused by mobile base station relays. | PR 6-5 | |
+| CPR 7.5-10 | The 5G system shall minimize the impact of the presence of mobile base station relays on radio network management (e.g. through automatic neighbour cell list configuration). | N.A | Added during consolidation |
+
+# 8 Conclusions and Recommendations
+
+This technical report identifies several use cases and potential new requirements for 5GS support of mobile base station relays. The resulting service requirements have been consolidated in clause 7.
+
+It is recommended to consider the consolidated requirements identified in this TR as the baseline for subsequent normative work.
+
+# Annex A: Change history
+
+| Change history | | | | | | | | |
+|----------------|-----------|-----------|------|-----|-----|-----------------------------------------------------------------|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2020-11 | SA1#92e | S1-204244 | | | | TR skeleton | | 0.0.0 |
+| 2020-11 | SA1#92e | S1-204362 | | | | Version incorporating use cases and inputs agreed at S1-92e | | 0.1.0 |
+| 2021-03 | SA1#93e | S1-210316 | | | | Version incorporating use cases and inputs agreed at S1-93e | | 0.2.0 |
+| 2021-05 | SA1#94e | S1-211312 | | | | Version incorporating use cases and inputs agreed at S1-94e | | 0.3.0 |
+| 2021-06 | SA#92e | SP-210515 | | | | Raised to v.1.0.0 for presentation for information | | 1.0.0 |
+| 2021-07 | SA1#94bis | S1-212100 | | | | Version incorporating use cases and inputs agreed at S1-94e-BIS | | 1.1.0 |
+| 2021-08 | SA1#95e | S1-213200 | | | | Version incorporating use cases and inputs agreed at S1-95e | | 1.2.0 |
+| 2021-09 | SA#93e | SP211048 | | | | Raised to v.2.0.0 for presentation for approval | | 2.0.0 |
+| 2021-09 | SA#93e | SP211048 | | | | Raised to v.18.0.0 following SA#93e's approval | | 18.0.0 |
+| 2021-12 | SP-94 | SP-211496 | 0001 | | D | CPR Mapping | | 18.1.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22844/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Rel-18/22_series/22844/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9762c17bf77b024ddf5c360868fba782c95803d1
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a0856f5b5d5dddae144fc2e8a3e757cf23d46da3dc5a34df4ccb5f33e89af80
+size 58145
diff --git a/marked/Rel-18/22_series/22844/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/22_series/22844/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5c78322f7c9700f1e30ec88a7541d4e22db651b
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d35de13280ddba69d9eada96641c18566056b05e0cdbb7f359997ccab35e8c5e
+size 20042
diff --git a/marked/Rel-18/22_series/22844/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-18/22_series/22844/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f16aee171e5146fb25571602f3be8576c4a0d45
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57b3ef468efab8a17ead71de4c7aa066e59b63e6874ecd66e6c45d46913433e2
+size 31139
diff --git a/marked/Rel-18/22_series/22844/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22844/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62e78ee06e8006e9d180582e5a790ddcf35d6fa4
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b55994dac295846169214ba8f2166cdc50f79975b951e811c3f5c1947b0fca14
+size 7562
diff --git a/marked/Rel-18/22_series/22844/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22844/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37ed9a33ac918168c7957637f7727f9249efe4f0
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7ef47f6ef699d1b4f075552e19c3d53c10559de3ee1e6f86d4ee23ecc64e7e5
+size 5722
diff --git a/marked/Rel-18/22_series/22844/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Rel-18/22_series/22844/f142b022cfc716cd967297f027efe647_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53784376fe942fe4bf188e1d045862e5dbc2f29b
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/f142b022cfc716cd967297f027efe647_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff32dca4ec9fb057d917a65c5fb0bd993dd17d978e1f3858df560ec38185b5f6
+size 65886
diff --git a/marked/Rel-18/22_series/22844/raw.md b/marked/Rel-18/22_series/22844/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..91ccd7b32388aeb19f580c1ab9102913db0a91ed
--- /dev/null
+++ b/marked/Rel-18/22_series/22844/raw.md
@@ -0,0 +1,1447 @@
+
+
+# 3GPP TR 22.844 V18.2.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on 5G Networks Providing Access to Localized Services; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+---
+
+## --- **Keywords**
+
+
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Overview..... | 8 |
+| 4.1 General ..... | 8 |
+| 4.2 Business Model for Providing Access to Localized Services..... | 8 |
+| 5 Use cases..... | 10 |
+| 5.1 Providing localized service over unlicensed band ..... | 10 |
+| 5.1.1 Description ..... | 10 |
+| 5.1.2 Pre-conditions..... | 10 |
+| 5.1.3 Service Flows ..... | 10 |
+| 5.1.4 Post-conditions ..... | 11 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 11 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 11 |
+| 5.2 New Use case for roaming service..... | 11 |
+| 5.2.1 Description ..... | 11 |
+| 5.2.2 Pre-conditions..... | 11 |
+| 5.2.3 Service Flows ..... | 11 |
+| 5.2.4 Post-conditions ..... | 12 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 12 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 12 |
+| 5.3 Use Case for UEs using home network services via hosting networks ..... | 13 |
+| 5.3.1 Description ..... | 13 |
+| 5.3.2 Pre-conditions..... | 13 |
+| 5.3.3 Service Flows ..... | 14 |
+| 5.3.4 Post-conditions ..... | 14 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 14 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.4 Use Case for UEs using localized services via hosting network..... | 15 |
+| 5.4.1 Description ..... | 15 |
+| 5.4.2 Pre-conditions..... | 15 |
+| 5.4.3 Service Flows ..... | 16 |
+| 5.4.4 Post-conditions ..... | 16 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 16 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 17 |
+| 5.5 (E-)Sports events at different venues: Hosting Network and 3 rd Party Provider service negotiation via standard mechanisms..... | 17 |
+| 5.5.1 Description ..... | 17 |
+| 5.5.2 Pre-conditions..... | 18 |
+| 5.5.3 Service Flows ..... | 18 |
+| 5.5.4 Post-conditions ..... | 18 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 19 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 19 |
+| 5.6 (E-)Sports events at a venue: Automatic discovery and selection of 3 rd party provider services over Hosting network access..... | 19 |
+| 5.6.1 Description ..... | 19 |
+| 5.6.2 Pre-conditions..... | 19 |
+| 5.6.3 Service Flows ..... | 20 |
+| 5.6.4 Post-conditions ..... | 20 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 20 |
+
+| | | |
+|--------|--------------------------------------------------------------------------------------------------------------------------|----|
+| 5.7 | (E-)Sports events at a venue: User selection of 3 rd party provider services over Hosting network access..... | 20 |
+| 5.7.1 | Description ..... | 20 |
+| 5.7.2 | Pre-conditions ..... | 21 |
+| 5.7.3 | Service Flows ..... | 21 |
+| 5.7.4 | Post-conditions ..... | 21 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 21 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 22 |
+| 5.8 | Hosting network deployment for a temporary event..... | 22 |
+| 5.8.1 | Description ..... | 22 |
+| 5.8.2 | Pre-conditions ..... | 22 |
+| 5.8.3 | Service Flows ..... | 22 |
+| 5.8.4 | Post-conditions ..... | 23 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 23 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 23 |
+| 5.9 | Regulatory requirements in a network providing access to localized services ..... | 23 |
+| 5.9.1 | Description ..... | 23 |
+| 5.9.2 | Pre-conditions ..... | 24 |
+| 5.9.3 | Service Flows ..... | 24 |
+| 5.9.4 | Post-conditions ..... | 24 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 24 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 24 |
+| 5.10 | Proximate Resources Use Case ..... | 24 |
+| 5.10.1 | Description ..... | 24 |
+| 5.10.2 | Pre-conditions ..... | 25 |
+| 5.10.3 | Service Flows ..... | 25 |
+| 5.10.4 | Post-conditions ..... | 25 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 26 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 26 |
+| 5.11 | Use Case of home network steering UEs to different localized service networks..... | 26 |
+| 5.11.1 | Description ..... | 26 |
+| 5.11.2 | Pre-conditions ..... | 26 |
+| 5.11.3 | Service Flows ..... | 26 |
+| 5.11.4 | Post-conditions ..... | 27 |
+| 5.11.5 | Existing features partly or fully covering the use case functionality ..... | 27 |
+| 5.11.6 | Potential New Requirements needed to support the use case..... | 27 |
+| 5.12 | Use case for Network selection based on application for localized services ..... | 27 |
+| 5.12.1 | Description ..... | 27 |
+| 5.12.2 | Pre-conditions ..... | 28 |
+| 5.12.3 | Service Flows ..... | 28 |
+| 5.12.4 | Post-conditions ..... | 28 |
+| 5.12.5 | Existing features partly or fully covering the use case functionality ..... | 29 |
+| 5.12.6 | Potential New Requirements needed to support the use case..... | 29 |
+| 5.13 | Broadcast and Multicast Local Service Use Case ..... | 29 |
+| 5.13.1 | Description ..... | 29 |
+| 5.13.2 | Pre-conditions ..... | 29 |
+| 5.13.3 | Service Flows ..... | 29 |
+| 5.13.4 | Post-conditions ..... | 30 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 30 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 30 |
+| 5.14 | Use case: managing a high number of UEs returning from a local hosting network to home network..... | 31 |
+| 5.14.1 | Description ..... | 31 |
+| 5.14.2 | Pre-conditions ..... | 31 |
+| 5.14.3 | Service Flows ..... | 31 |
+| 5.14.4 | Post-conditions ..... | 32 |
+| 5.14.5 | Existing features partly or fully covering the use case functionality ..... | 32 |
+| 5.14.6 | Potential New Requirements needed to support the use case..... | 32 |
+| 5.15.1 | Description ..... | 32 |
+| 5.15.2 | Pre-conditions ..... | 33 |
+| 5.15.3 | Service Flows ..... | 33 |
+| 5.15.4 | Post-conditions ..... | 34 |
+| 5.15.5 | Existing features partly or fully covering the use case functionality ..... | 34 |
+| 5.15.6 | Potential New Requirements needed to support the use case..... | 34 |
+
+| | | |
+|---------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------|
+| 5.16 | Localized network for a mass casualty incident..... | 34 |
+| 5.16.1 | Description ..... | 34 |
+| 5.16.2 | Pre-conditions ..... | 35 |
+| 5.16.3 | Service Flows ..... | 35 |
+| 5.16.4 | Post-conditions ..... | 35 |
+| 5.16.5 | Existing features partly or fully covering the use case functionality ..... | 35 |
+| 5.16.6 | Potential New Requirements needed to support the use case..... | 35 |
+| 5.17 | Steering of UEs between hosting local networks and PLMNs ..... | 35 |
+| 5.17.1 | Description ..... | 35 |
+| 5.17.2 | Pre-conditions ..... | 36 |
+| 5.17.3 | Service Flows ..... | 36 |
+| 5.17.4 | Post-conditions ..... | 36 |
+| 5.17.5 | Existing features partly or fully covering the use case functionality ..... | 36 |
+| 5.17.6 | Potential New Requirements needed to support the use case..... | 36 |
+| 6 | Consolidated Potential Requirements ..... | 37 |
+| 6.1 | Configuration of Localized Services in Hosting Network ..... | 37 |
+| 6.2 | User Manual Selection of Localized Services via Hosting Network ..... | 39 |
+| 6.3 | UE Configuration, Provisioning, Authentication and Authorization..... | 40 |
+| 6.4 | UE Discovery, Selection and Access ..... | 41 |
+| 6.5 | Hosting Network Localized Services and Home Operator Services..... | 42 |
+| 6.6 | Returning to Home Network ..... | 42 |
+| 6.7 | Charging..... | 42 |
+| 6.8 | Regulatory Services..... | 43 |
+| 6.9 | Multicast/Broadcast..... | 43 |
+| 7 | Conclusions and Recommendations ..... | 43 |
+| Annex A: Interworking between Networks Operators and Application Providers for localized services..... | | 43 |
+| Annex B: Change history..... | | 45 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document intends to capture the outcome of the study on use cases and potential new requirements for 5G networks providing access to localized services. The study aims to cover:
+
+- use cases for enhanced 5G system support of a hosting network providing users/devices access to specific services, offered by the hosting network operator, other mobile operator(s) or 3rd party provider(s). Including scenarios where:
+ - Access to services through the hosting network could be on demand, temporary and/or cover specific location(s);
+ - The operator of the hosting network, or other mobile operator offering services to users, can be a PLMN or NPN operator;
+ - Different RATs (3GPP or non-3GPP) and spectrum (licensed or unlicensed) could be considered;
+ - The hosting network can also provide specific network services, e.g., location-based service, time synchronization etc.
+- Investigate potential new service requirements, including:
+ - Enabling users/UEs to discover availability of specific target networks and specific services through a hosting network;
+ - Network functionalities to negotiate and configure access and requirements for a specific service (e.g., QoS, network slicing, charging, onboarding etc.);
+ - Can include policy management, service/QoS monitoring, and interaction between the hosting network and other mobile operator or 3rd party (offering the service) e.g., via API or other standard mechanisms
+ - Enabling users/UEs to concurrently use specific target services offered through a hosting network and the regular services offered by the HPLMN of the user/UE;
+ - Enabling access to the hosting network and specific services for users/UEs without previous relationship with the hosting network;
+ - Consideration of regulatory and security aspects.
+- Gap analysis between potential new requirements and existing requirements and functionalities supported by 3GPP, e.g., VIAPA, NPN, slicing, QoS, etc.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.261: "Service requirements for the 5G system".
+
+- [3] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)".
+- [4] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+- [5] 3GPP TS 22.011: "Service accessibility".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+
+
+# --- 4 Overview
+
+## 4.1 General
+
+The use cases contained in this technical report consider several service aspects. This study focusses on each of the concepts introduced in the next subclause, "Business Model for Providing Access to Localized Services," to some extent. The primary consideration, from which potential requirements are derived are how to set up services, ensure that users find, get access to and obtain services with proper control, and the scenarios and constraints that pertain to hosting networks.
+
+Key aspects that are addressed are how hosting networks are configured and what policies are applied to the services they offer. These networks are only available within a limited span of time and physical extent. The use cases consider how to allow flexibility to establish such networks easily, while still offering security and access to regulatory mandated services. Use cases balance the ability of users to discover and select access to hosting networks with the policies of their home network provider, as some services will be home routed, while others provided locally. The hosting network itself may use resources in a very controlled manner in some of the scenarios explored in the use cases in clause 5.
+
+Another key aspect of this study is the interaction with third parties who can request, configure and remain informed of the services provided by the hosting network.
+
+## 4.2 Business Model for Providing Access to Localized Services
+
+The following figure is a 'business model canvas' depicting a number of relevant aspects of the business model. The model is not meant to exhaustively list all aspects. Rather it draws out key elements of the goals study intends to achieve.
+
+| Key Partners | Key Activities | Value Propositions | Relationships | Customer Segments |
+|-------------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-----------------------------------|
+| Network Operators | De/commission access & services | Sufficient local resources | Automated Service | Entertainment, Hospitality (mass) |
+| Local SPs | initiate, provide & terminate access | Simplified access to services | Self Service | General (mobile telecom access) |
+| Individual Users | | Transient (easy to establish) | | Construction (sector) |
+| Facilities / Proprietors | Key Resources
Network components | Services not otherwise offered | Channels
Local business partner(s) | Public Safety (sector) |
+| 3 rd Party SPs | Service set-up processes | | 3rd party SPs | |
+| Cost Structure | | Revenue Streams | | |
+| Considerations of pricing and cost structure are out of scope of 3GPP. | | User use of network to access services - usage fees, advertising, 3rd party 'sponsor'...
Local SP offer of network to access services - service access (usage fee), set up fee... | | |
+
+**Figure 4.2-1: A Business Model Canvas for Providing Access to Local Services**
+
+Key Partners include Network Operators (MNOs, NPN operators, fixed operators, etc.), Local service providers, individuals (users), owners of facilities or proprietors of business in which the local access will occur and third party service providers. These stakeholders will work together to provide local access to services.
+
+The main activities that we will be concerned with in this study are first how to commission and decommission access, as including the relevant services. The access is not merely to a *network* but to a set of *services* offered by local service providers, the network operator and third parties. Since the access is *local* and may be bounded in time and space, the effort to de/commission accesses and services will have to be very light-weight (not requiring lots of lead-time, complexity, in-person consulting and customization, etc.)
+
+Secondly, from a user perspective, the user must become aware of access and local services, to choose to access them. The process by which the user and their equipment gain access to the network, use it and terminate access (and service) will be efficient, simple and result in a user experience that seems convenient and to offer resources and services that cannot be accessed any other way.
+
+Providing access to local services results in four distinct opportunities for users and service providers. First, access can be provided that is sufficient in areas that otherwise would lack them, for example, on a fairground established far from other infrastructure. Second, the access to local services will be simpler than access would be without this service. For example, obtaining network access may result in associated local service configuration and effortless presentation to the user. Third, the access and local services operation can be established as needed, without the need for long term business relationships such as facilities, permanently installed equipment, etc. (Of course this advantage does not remove the need for such to be established on a *short-term* basis.)
+
+To establish the complex set of business relationships and arrangements from the perspective of all the involved key partners, business processes will have to be automated, or at the very least available for self-service. This may have standards implications, to the extent that interaction with different stakeholders can proceed using electronic data interchange. These standards may be out of scope of 3GPP.
+
+The customer segments listed are meant to be examples. The use cases in this study will elaborate specific applications of this feature to different users in business relevant cases.
+
+The resources that must be brought to bear to provide access to local services are of two kinds. First, the network operator must have (or be able to make use of others') network infrastructure, both for mobile access and for configuration of services, authorization and other aspects. Second, the service providers (local service providers, third
+
+party service providers and the network operator provided services) need to be able to arrange for their services to be offered via the local access. For this purpose, a set of service set-up processes are in place.
+
+These local service access can be promoted and arranged through different channels. Principally the local service operators (e.g. brick and mortar businesses, entertainment venues, construction contractors, first responder agencies, etc.) will provide information and proper incentive or instructions to potential users so that they will seek to access the local services. Third party service providers, e.g. an athletics association, a regional corporation or national agency, can inform, motivate and prepare their users to expect local access to services (in a particular place, at a particular time.)
+
+While cost structures, billing and revenue models are out of scope of 3GPP, some consideration of the business approach is relevant to this study. The key partners need to either charge or be charged for their part in the service, or to make use of the local services without charge, if that is possible. Two models of revenue are considered in the table – usage based, in which either the user or a service provider is charged for that usage. The other revenue model is through the service providers that establish and configure both the access and their particular service offerings over that access. Here it is envisioned that the service provider is charged.
+
+# --- 5 Use cases
+
+## 5.1 Providing localized service over unlicensed band
+
+### 5.1.1 Description
+
+3GPP has introduced several features using unlicensed band for 3GPP RATs. As allocated amount of radio spectrum for unlicensed band increases, this will provide new opportunities for the increased usage of 3GPP RATs and further connectivity opportunities for users.
+
+Because this unlicensed band can be used by any technology and any user as long as certain requirements are met, and because the coordination between the users in this spectrum are weak, the QoS may not be equal to that can be provided over licensed band. Thus, the connectivity service provided over this band may be applicable to some applications, if provided with right usage policies.
+
+### 5.1.2 Pre-conditions
+
+Operator Universal owns a licensed spectrum. Also, in the region where Operator Universal operates, huge amount of unlicensed spectrum is available. Thus, the operator Universal decides to upgrade some of its NG-RANs to support both the unlicensed spectrum and the licensed spectrum.
+
+Charlie has subscription with Operator Universal with certain monthly data quota. Due to heavy watching of online streaming service, Charlie almost used up his monthly data quota. Charlie's smartphone is advanced one which also supports NR operation over unlicensed band.
+
+### 5.1.3 Service Flows
+
+Following is service flow for this use case:
+
+- Charlie is a fan of pro-baseball. One day, he goes to nearby stadium to directly watch one of pro-baseball games.
+- At the pro-baseball stadium, due to huge demand for connectivity, the Operator Universal already upgrades the NG-RAN equipment to support also unlicensed spectrum.
+- The Operator Universal decides to allow some of its customers to use connectivity service over unlicensed spectrum.
+- Charlie finds out that the Operator Universal provides connectivity service over unlicensed band within the stadium. He configures his smartphone to use unlicensed band only when he is located within this stadium, because his monthly quota has almost run out. This configuration information is also shared to the Operator Universal.
+
+- The Operator Universal approves the connectivity over unlicensed band. Except some essential operator service such as IMS, all the other the user traffic for Charlie is delivered only using the unlicensed bands.
+- Finally, the pro-baseball game ends.
+- Charlie leaves the stadium. Outside of the stadium, the Operator Universal does not provide connectivity service over unlicensed spectrum. Thus, the Charlies smartphones are served by the NG-RAN of the operator using licensed bands.
+
+### 5.1.4 Post-conditions
+
+The Operator Universal gathers charging information related to the use of connectivity service over unlicensed band.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+N/A
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+Following new requirements can be derived from this use case:
+
+[PR.5.1.6-1] 5G system shall be able to support for a UE to be provided with the temporary connectivity service over unlicensed spectrum at specific locations and specific period.
+
+[PR.5.1.6-2] 5G system shall be able to support to transport user traffic using unlicensed spectrum based on e.g. user preference or operator policy and so on.
+
+[PR.5.1.6-3] 5G system shall be able to support to transport specific service flow over unlicensed spectrum, licensed spectrum, or both based on operator policy or user preference.
+
+[PR.5.1.6-4] 5G system shall be able to gather charging information for the traffic transported over unlicensed spectrum.
+
+## 5.2 New Use case for roaming service
+
+### 5.2.1 Description
+
+When the user visits a foreign country for a few days, the user may want to have access to temporary mobile data service and prefer to have an arrangement directly with a local provider for the temporary mobile data service, while keeping an arrangement with its home provider for other services.
+
+The use case in this section assumes that the UE uses the credential of the home provider also for the temporary mobile data service, though the subscription for the temporary mobile data service is bound to the local provider. The case where the local provider uses a separate independent credential for the temporary mobile data service is not in the scope of this use case.
+
+### 5.2.2 Pre-conditions
+
+Lily is traveling around the world. She has no strict schedule and always wanders off on her own. Sometimes she stays in a new place for several days if she likes there. In some place where Lily decides to buy the roaming data service provided by a local network e.g. via an app that she has obtained from a 3rd party data service provider.
+
+### 5.2.3 Service Flows
+
+1. Lily turns on her smartphone to see what networks and what data service plans are available.
+2. the step 1 leads to a mobile data service shop which is displayed on the mobile screen, wherein there are several data combo services, each service is labelled with (network identifier, price, valid duration, valid location, data volume, type of service [e.g. data, voice etc] and optionally the mobile technology, e.g. 4G or 5G) and if there are anything that needs
+
+to be satisfied for that plan e.g. watching some advertisement may be required. Or, only foreigner is eligible for the service.
+
+3. according the time that Lily plans to stay at current location, Lily chooses to buy the most cost-effective data combo service. For example, if Lily plans to stay there for one day, she buys the one-day data combo service; if Lily plans to stay there for one week, she buys the seven-days data combo service; if Lily just stay at the transfer airport for several hours and the WLAN connection is under bad condition, she buys the 1G data combo service.
+
+4. Lily pays the bills for the data service she chooses at step 3. After a few seconds, Lily's mobile phone has download necessary information and is ready to provide temporary mobile data service to Lily. Since then, Lily becomes a temporary subscriber of the VPLMN for that temporary mobile data service.
+
+5. Lily may activate the mobile data service immediately or Lily may decide to activate the mobile data service when she lost WLAN connection. While this temporary subscription is valid, the UE selects and camps on the selected network providing the temporary local service.
+
+### 5.2.4 Post-conditions
+
+Lily can access to the internet and use apps via the mobile data service of the network where she is temporary subscriber now or can temporarily use the service during the validity period of the service within the valid location using the subscribed RAT, until the maximum data quota is reached.
+
+Lily uses her normal phone number for making and receiving calls or SMS over the VPLMN by means of traditional roaming and charging information per the roaming agreement is reported to Lily home operator.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+Existing specifications support the home-routed traffic service and local-breakout traffic service for roaming cases. For the local-breakout service, even if the traffic does not traverse the home network, the service is associated to the subscribed service toward the home network. In this use case, the temporary data service is different from the local-breakout service, because it is not the subscribed service toward the home network.
+
+TS 22.261 has following requirements:
+
+- The 5G system shall enable users to obtain services from more than one network simultaneously on an on-demand basis. For a user with a single operator subscription, the use of multiple serving networks operated by different operators shall be under the control of the home operator.
+
+Thus, following requirement is covered by above requirements:
+
+- 5G system shall be able to provide the UE simultaneously with both the temporary local services subscribed to the local hosting network and the services subscribed to home operator.
+- The 3rd party service provider shall be able to agree the details of a temporary subscription for local services (such as validity period, location, QoS, services etc.) with a local hosting network.
+- The 5G system shall allow a UE to present available local hosting networks to the user, which the user is allowed to use.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR.5.2.6-1] The 5G system shall support a mechanism to allow a user to manually select a specific local hosting network.
+
+NOTE: This allows the hosting network and home network to provide necessary information to the user to determine which network to select.
+
+[PR.5.2.6-2] The 5G system shall be able to authorize a UE to make use of a specific local hosting network
+
+## 5.3 Use Case for UEs using home network services via hosting networks
+
+### 5.3.1 Description
+
+Given the main objective of the study that UEs and their service providers are without previous relationship to the hosting network, automatic e-agreement mechanisms are needed to allow network operators to build short term relationship using application layer approaches. The e-agreement mechanisms allow the automation of multi-step processes in telecommunication domain to establish service level e-agreement among network operators for enabling the 5GS to facilitate the sharing of services and resources of the networks among network operators and to configure their networks and UEs accordingly at specific occasion, e.g. time and location.
+
+The application layer approaches require 5G network to expose network capabilities. For example, as shown in Figure 5.3.1-1, the e-agreement is established among service operators, e.g. SP-A, SP-B, and SP-C have no SLAs in place for the services provided by SP-A's hosting network-A.
+
+
+
+Diagram for building relationship between network operators using application layer approach. The diagram shows three service providers: SP-A, SP-B, and SP-C. SP-A is connected to a UE and a RAN, which is part of Hosting Network-A. SP-A's 5GC is connected to an SP-A App. SP-B is connected to a RAN, which is connected to a 5GC, which is connected to a PSA. SP-B's 5GC is connected to an SP-B App. SP-C is connected to an SP-C App, which is connected to a 5GC, which is connected to a RAN. An 'E-agreement' is shown as a dashed line connecting the SP-A App and the SP-C App. A cloud labeled 'Data Network SP-B's service' is connected to the PSA.
+
+**Figure 5.3.1-1: diagram for building relationship between network operators using application layer approach**
+
+The SP-A operator creates an e-agreement which provides the localized service configuration. The SP-B and SP-C operators can subscribe this localized service with required service policies for their UEs. The SP-B and SP-C can then configure their UEs for localized service.
+
+Based on the e-agreement, the hosting network can be configured with localized service at a specific time and location for its subscribers (other network operator), e.g. localized service policies of time, location, network-A access parameters, including spectrum, access technologies (3GPP or non-3GPP), network slice, charging policies, and subscriber's network policies for authentication, and routing.
+
+Based on the e-agreement, the hosting network configuration creation and termination can be performed by SP-A or a trusted third-party application of the subscriber representing other network operator. With the application layer approach, the localized service can be used by authorized UEs of SP-A, SP-B, and SP-C which subscribes the service.
+
+Note: the application approach for automatic e-agreement is an example that provides some insights for what the suitable APIs would be required for localized service enabler in 5GS.
+
+### 5.3.2 Pre-conditions
+
+At the Monster theme park built with genetically engineered living monsters on an island having a surface of 30 square miles, which only opens once a year to allow visitors to onboard and enjoy three days adventures. From the lessons learned from disaster happened in Jurassic park in 1993, the Monster park management as SP-A decides to replace the wirelines with 5G networks around the island for better network coverage and advanced and secure 5G features.
+
+For the past few years, the visitors had tons of service complains about the network connectivity for the availabilities of their home operators on the island. This year, SP-A decides to use their 5G network to offer a hosting network-A
+
+providing access to localized service for sharing this service using blockchain technologies with other service providers, e.g. SP-B, and SP-C, in which SP-B's network is not available in the whole island and SP-C's network is very spotty and available at some zones. Both SP-B and SP-C subscribe the localized service from SP-A for their UEs.
+
+When the schedule event is started, the network-A starts to provision localized services based on service contract with SP-B and SP-C and to broadcast related information via hosting networks on the island.
+
+Lexi and Timmy are Dr. Hammond's grandchildren who invited them to attend this annual event this year, and they have UEs, UE-C1 and UE-C2, with SP-C's subscriptions. The SP-C (NPN or PLMN) subscribed to SP-A's localized services configures their UEs with localized service provided by SP-A.
+
+### 5.3.3 Service Flows
+
+Step1: When Lexi and Timmy arrive the island, Lexi wants to use her UE-C1's home network service to call her Mom.
+
+Step2: Her UE-C1 configured with localized service found that only SP-A network is available.
+
+Step3: Her UE-C1 then selects and requests to register hosting network-A.
+
+Step4: Hosting network-A knows that UE-C1 has been configured to use localized service by its SP-C which has subscribed to localized service for their UEs but UE-C2 seems not being configured to use localized services by its SP-C. The Hosting network-A can authenticate the UE-C1 and UE-C2 based on UEs' credentials.
+
+Step5: Lexi happily finds that her UE-C1 which has been pre-configured with localized service can get connection from hosting network-A to call her Mom and grandfather for their safe arrivals. In the meantime, Timmy's UE-C2 has his UE-C2 configured for localized service on the spot via hosting network-A and then Timmy successfully gets data connection via hosting network-A automatically.
+
+Step6: Lexi and Timmy don't feel any differences on the user experience of applications (e.g. social media, streaming music, text messages) of UE-C1 and UE-C2 via hosting network-A or their home SP-C network when touring around the park with their grandfather to watch live monsters in different zones and continue service seamlessly even with spotty network coverages provided by different network operators (PLMN or NPN). Well, their new friend met on the tour Jeep was upset for not having connections from his UE-X of SP-X which does not subscribe the localized service from SP-A. He decides to switch to SP-C subscription after going home.
+
+### 5.3.4 Post-conditions
+
+The SP-A provides the localized service to authenticated and authorized visitors whose UEs' service providers subscribe the localized service based on the service contract. Lexi and Timmy enjoy good user experience on using their home network service of SP-C via network-A in the remote island.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+The existing service requirements for roaming users assume that roaming policies are in place for UEs to use their home network services.
+
+The UE is able to access visited network using UE's credential on UICC/eSIM based on its home network's subscription.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR.5.3.6-1]: The 5G network shall support suitable mechanisms to allow automatically establishing localized services agreements for a specific occasion (time and location) and building temporary relationship among a hosting network operator (NPN or PLMN) and other service operators including network operators (NPN or PLMN) or third-party content service providers.
+
+NOTE: Both the hosting network and the home network can be a PLMN or NPN but only subscribers of a public network can roam to a PLMN.
+
+[PR.5.3.6-2]: Subject to regulatory requirements, the 5G system shall support suitable mechanisms to allow another network operator to automatically negotiate roaming policies with the hosting network for allowing their subscribers to connect at a specific occasion, e.g. time and location, for their home network services.
+
+[PR.5.3.6-3]: Subject to localized services agreements, the 5G network shall enable a home network operator to authorize a UE for using its home network services via a visited hosting network for a certain period of time and/or location.
+
+[PR.5.3.6-4]: The 5G network shall be able to configure a UE with home operator policies on what services are preferred to be used from the home network for home routed services via authorized hosting networks.
+
+[PR.5.3.6-5]: Subject to localized services agreements between the hosting network operator and home network operator, for UE with only home network (NPN or PLMN) subscription and with authorization to access hosting networks (NPN or PLMN), the 5G system shall support:
+
+- access to the hosting network and use home network services or selected localized services via the hosting network.
+- seamless service continuity for home network services or selected localized services when moving between two hosting networks or a host network and the home network.
+
+## 5.4 Use Case for UEs using localized services via hosting network
+
+### 5.4.1 Description
+
+This use case assumes that network operators can build short term relationship using application layer approach, e.g. using smart contracts based blockchain technologies, for offering localized services provided by different service providers via a hosting network.
+
+The application layer approaches require 5G network to expose network capabilities for the localized service. For example, for the automatic e-agreement mechanism deployed by SP-A for a localized service at a specific occasion (starting time, duration and location), which allows localized services to be shared among service providers. In addition, the e-agreement can also allow the hosting network to accommodate temporary localized services provided by different service providers.
+
+Based on the e-agreement, the hosting network can be configured with localized service at a specific time and location for its service subscribers (other network operator), e.g. localized service policies of time (including duration, starting time), location, network-A access parameters, including spectrum, access technologies (3GPP or non-3GPP), network slice, charging policies, and subscriber's network policies for authentication, and routing. In the meantime, the SP-A and SP-B can further offer localized services via hosting network.
+
+The 5G network provides suitable mechanisms to allow establishing automatic roaming (e)-agreements for a specific occasion (time and location) and building temporary relationship among hosting network operator (NPN or PLMN) and other service operators including network operators or third-party content service providers. The localized service configuration can be provisioned in the hosting network based on the e-agreement. For example, SP-C can subscribe SP-A's localized service of the hosting network and SP-B's localized service based on e-agreement for their UEs and configures their UEs with localized service. When a UE configured with localized service connects to hosting network SP-A which can present available localized services provided by different service providers for UEs configured with localized services to select any one of them. When using SP-B's localized service, the SP-C's UEs can be charged by their home network.
+
+Note: the application approach for automatic e-agreement is an example that provides some insights for what the suitable APIs would be required for localized service enabler in 5GS.
+
+### 5.4.2 Pre-conditions
+
+At the Monster theme park on an island hosting three days adventures for visitors, the park has SP-A network coverage for a hosting network-A providing access to localized service which has been subscribed by SP-B and SP-C for their UEs based on e-agreement established by SP-A for sharing this localized service. In the meantime, SP-B's network is not available on the island and SP-C's network is very spotty and only available at some zones.
+
+For the on-demand dedicated services, SP-A deploys localized services on its owned Service Hosting Environment-A for streaming live video and immersive media in different monsters' zones. SP-B also provides localized services on its Service Hosting Environment-B connected to the hosting network for superhero interactive game via hosting network-A. SP-D is a content service provider which offers localized services on its application platform-D for streaming
+
+movies. The SP-C subscribes SP-A's and SP-B's localized services for their UEs attending adventures on the island. In addition, the SP-C rents the resource from the SP-A for providing localized services for interactive Monster hunting games on its owned Service Hosting Environment-C connected to the hosting network.
+
+When the scheduled event is started, the network-A starts to provision localized services as well as the temporary localized services provided by different service providers.
+
+Lexi and Timmy visit their grandfather and attend this annual event. Their UEs, UE-C1 and UE-C2, are both with SP-C's subscriptions. The SP-C subscribed SP-A's localized services configures their UEs with information of hosting network identity for selecting hosting network and credentials for accessing localized services via hosting network.
+
+### 5.4.3 Service Flows
+
+#### Use Case A: use of home network service and localized services when both networks are available
+
+Step1: When visiting the genetic engineering center where both SP-A and SP-C networks are available, Lexi's UE-C1 and Timmy's UE-C2 configured with localized service can select and connect to hosting network-A and its SP-C's network simultaneously. The hosting network-A authenticates the UE-C1 and UE-C2 and both UEs use their configured user credentials for accessing to localized services via hosting network.
+
+Step2: UE-C1 and UE-C2 present available on demand dedicated services to Lexi and Jimmy.
+
+Step3: Jimmy selects the superhero interactive game provided by SP-B and chooses to be the Spiderman playing with holograms of live monsters at the park (which enables specific hosting network-A 5G services). In the meantime, Lexi selects one immersive media provided by SP-A to watch the live monsters running around the park. The hosting network-A gets localized service authorization from service providers and creates the service session for the authorized UEs
+
+Step4: Both Lexi and Jimmy can share live videos with their friends on social media using home network services via SP-C network.
+
+#### Use Case B: use of local SP-A's localized services and SP-D's localized services via hosting network
+
+Step1: after one day's fun adventure at the park, Lexi is lying on the bed at the cabin where her UE-C1 finds only SP-A is available. Because the conditions (e.g., time, location) for selecting the SP-A are met according to the policy provisioned from SP-C, Lexi's UE connects to the hosting network.
+
+Step2: Lexi scrolls the localized services menu and determines to select an on demand movie, Jurassic Park (1993), provided by SP-D.
+
+Step2: in the meantime, she selects another localized services provided by SP-A to monitor live monsters night life in Zone X.
+
+Step3: The hosting network-A establishes required IP connections for two localized services and routes the UE-C1's traffic locally at SP-A's hosting network and to SP-D's network, respectively.
+
+### 5.4.4 Post-conditions
+
+Use Case A: Lexi and Timmy enjoy the adventure and good network services using their UE-C1 and UE-C2 for SP-A's and SP-B's localized service via hosting network, respectively. In the meantime, their UEs can connect SP-C networks and use home network services. Since SP-C subscribes to SP-A's and SP-B's localized service, the localized services charge will be in the next month statement from their SP-C's home network operator.
+
+Use Case B: Lexi needs to pay for the localized service provided by SP-D using online payment method before enjoying the movie. Lexi is happy to continue fun experience at night using her UE-C1 for localized services provided by SP-A and SP-D via SP-A's hosting network, respectively.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+The existing service requirements for roaming users assume that roaming policies are in place for UEs to use their home network services or localized services provided by other service providers.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+[PR.5.4.6-1]: The hosting network shall provide suitable APIs to allow a trusted third party application (other service providers) to provision their localized services policies (e.g. network slice, required IP connectivity, QoS) and routing policies for the application of the localized services to the hosting network.
+
+[PR.5.4.6-1A]: The 5G network shall provide capability to allow a trusted 3rd party to provision its UE with localized service policy (e.g. QoS, network slice, service restriction such as time and location) via the hosting network or the UE's home network.
+
+[PR.5.4.6-2]: The hosting network shall be able to allow a UE to manually/automatically select localized services which are provided via local breakout at the hosting network.
+
+NOTE: localized services are provided via local breakout at the hosting network based on interworking scenarios for hosting network owned/collaborative services as indicated in Annex A.
+
+[PR.5.4.6-2A]: The 5G network shall be able to allow a UE to automatically select a hosting network with the desired localized services which are provided via local breakout at the hosting network, based on the policy provisioned by its home network.
+
+[PR.5.4.6-3]: The hosting network shall be able to provide required connectivity and QoS for a UE connected to the hosting network to simultaneously use its home network services and localized services.
+
+[PR.5.4.6-4]: A UE shall be able to connect to the hosting network for using home network service and localized services at the same time.
+
+[PR.5.4.6-5]: A UE shall be able to simultaneously connect to its home network and to a hosting network if both networks are available, e.g. to use its home network services and localized services at the same time.
+
+[PR.5.4.6-6]: The 5G system shall be able to collect charging records for the use of localized services via local breakout at the hosting network and provide the charging records to UEs' home operators based on service and charging policies provided by the localized service providers.
+
+[PR.5.4.6-7]: The 5G system shall enable a UE to be able to use hosting network provided user credentials for authenticating the UE to make use of localized services via the hosting network with a certain time (including starting time and the duration) and location validity.
+
+[PR.5.4.6-8]: A UE shall be able to select and connect to authorized localized services via a hosting network based on configured user credentials.
+
+## 5.5 (E-)Sports events at different venues: Hosting Network and 3rd Party Provider service negotiation via standard mechanisms
+
+### 5.5.1 Description
+
+Network A infrastructure is deployed in multiple sport venues., e.g. from October 2020 to May 2021. Network A may be a PLMN or and NPN. The (e-) sports games are scheduled one month in advance throughout the season and may be subject to reschedule for different reasons. The venues are decided between the 3rd Party Provider B and venue owners. Once the venue and time are scheduled, the 3rd Party content provider needs to negotiate with Network A to set-up access to the 3rd party provider's services during the event and at the venue location, and for Network A to manage resources for that service.
+
+In order to facilitate such negotiation, Network A offers standard mechanisms for 3rd Party Content Provider B to request specific configuration of access to the service during the (e-)game event.
+
+Via the standard mechanism, the 3rd Party Content Provider may request one or more of the following:
+
+- Service area / location (e.g. venue)
+- Time period for service (e.g. game time)
+
+- Service requirements (including QoS requirements, slicing information)
+- Potentially different QoS requirements for different users (e.g., depending on pricing such as gold, silver, bronze)
+- Discovery information (dependent on other use cases) if needed, e.g. event name, 3rd party provider name, etc.
+- 3rd Party Portal information (e.g., for access to 3rd Party Content Provider Portal for online sign-up)
+- Expected or maximum number of users that will be accessing the service during the event.
+
+Network provider A then creates policy rules and performs network configuration accordingly.
+
+Network A confirms the accepted service set-up, including one or more of the following:
+
+- Confirmation of location/date/time.
+- Accepted QoS to be provided.
+- Network slicing information.
+- Limitation in number of subscribers to access the event.
+- Specific access/discovery information.
+
+The 3rd Party Content Provider may request to modify the previous request at any time (e.g. in case of game reschedule, change in expected number of spectators, etc).
+
+NOTE: User /UE discovery of the service and UE access are not covered in this use case and depends on other use cases.
+
+### 5.5.2 Pre-conditions
+
+Network A and 3rd Party Content Provider B have a service pre-agreement for 3rd Party Content Provider B to offer \ service(s) for Game events at different venues, via Network A's access for a whole season. Specific location and times to be determined as season progresses.
+
+### 5.5.3 Service Flows
+
+1. 3rd Party Content Provider B confirms venue and time for a game event.
+2. 3rd Party Content Provider B requests via standard mechanism to establish a service via Network A's access at the specific time and location. The 3rd party provider provides various service requirement requests, including QoS, expected/maximum number of users, event information for discovery, etc.
+3. Network A performs service authorization for the time and location, creates policies for the event and configures the network accordingly.
+4. Network A provides a confirmation of service including accepted QoS, slicing information if needed, maximum number of users allowed, and potentially other information for discovery.
+5. The 3rd Party Provider B may provide information to game event participants for accessing their services via Network A.
+
+NOTE: User discovery and access are not part of this use case and are dependent on other use cases.
+
+6. Network A activates the resources for 3rd party content provider's service at the agreed time period and location.
+
+### 5.5.4 Post-conditions
+
+E-game event participants are able to access 3rd Party Content Provider's services via Network A's access during the game at the specific location.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+[FFS]
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR.5.5.6-1] The 5G system shall support means for a 3rd Party Provider to request a Hosting Network via standard mechanisms to provide access to 3rd party provider services at a specific time and location.
+
+[PR.5.5.6-2] The 5G system shall support means for the 3rd Party Provider to request various service requirements, including QoS, expected/maximum number of users, event information for discovery, network slicing, etc.
+
+[PR.5.5.6-3] The 5G system shall support means for a hosting network to create policies and configure resources for the requested time and location for the 3rd Party Provider services based on the received request.
+
+[PR.5.5.6-4] The 5G system shall support means for a hosting network to notify the 3rd Party Provider of the accepted service parameters, including QoS, maximum allowed number of users, event information for discovery, network slicing, etc.
+
+## 5.6 (E-)Sports events at a venue: Automatic discovery and selection of 3rd party provider services over Hosting network access.
+
+### 5.6.1 Description
+
+Network A infrastructure is deployed in multiple sport venues. Network A may be a PLMN or an NPN. A 3rd Party content provider negotiates with Network A to set-up access to the 3rd party provider's services during the event and at the venue location, and for Network A to manage resources for that service.
+
+The 3rd party provider services are offered to people attending and/or participating in the event, without any previous subscription to Network A. The users have a previous relationship with the 3rd party provider. Neither the 3rd party provider nor Network A has relationship with the home network of the UE.
+
+During the event service negotiation between 3rd party provider and Network A, the Network A provides discovery information to 3rd party provider. The 3rd party provider configures the UE with event service discovery, which may contain Network A's information and the event service information, and time validity (e.g. starting time, duration).
+
+During the time validity the UE searches for Network A and event service based on configuration from the 3rd party provider. If the UE finds a suitable cell from Network A offering the event service, the UE notifies the user who can manually initiate access to Network A. The UE requests to connect to 3rd party event service(s) access, Network A validates with 3rd party provider that the UE is authorized to access content for event.
+
+If necessary, the UE is provisioned temporary access credentials for Network A. The UE then accesses Network A for 3rd party event service(s) with the temporary credentials.
+
+During registration Network A may provide UE with configuration based on negotiation with 3rd party, e.g. slicing configuration.
+
+Automatic selection of Network A is possible if the UE is capable to maintain two separate registrations, one with configured credentials to access Network A, and an independent registration using a USIM. In that case, if the UE was already registered to a PLMN when identifying the Network A, the UE may initiate access and registration to Network A with the configured credentials while maintaining the access to the registered PLMN independently.
+
+### 5.6.2 Pre-conditions
+
+Network A and 3rd Party Content Provider B have a service pre-agreement for 3rd Party Content Provider B to offer exclusive service via Network A's access during the game event at the event location.
+
+The 3rd party service is meant to be offered to event participants that may not have any subscription to Network A and have prior service agreement with 3rd party provider for the event service.
+
+### 5.6.3 Service Flows
+
+1. A user is made aware of the 3rd party service being offered via Network A's access. This may be done either offline (e.g., in ticket, flyer, posters) or online (e.g. Internet advertisement.)
+2. During the event service negotiation between 3rd party provider and Network A, the Network A provides configuration information to 3rd party provider.
+3. The 3rd party provider provides the UE with Network A's information, configuration (e.g. slicing configuration) for the event service and the event service information, and time validity. This is sent over any access.
+4. During the time validity the UE searches for Network A.
+5. If the UE finds a suitable cell from Network A, the UE notifies the user who can manually initiate access to Network A. The UE indicates request to access to 3rd party event service(s) access.
+6. Network A validates with 3rd party provider that the UE is authorized to access content for event.
+7. If necessary, the UE is provisioned temporary access credentials for Network A. The UE then accesses Network A for 3rd party event service(s) with the temporary credentials.
+8. The UE may if capable maintain two separate registrations, one with configured credentials for access to Network A, and an independent registration using a USIM. In that case, if the UE was already registered to a PLMN when identifying the Network A, the UE may initiate access and registration to Network A with the configured credentials while maintaining the access to the registered PLMN independently.
+
+### 5.6.4 Post-conditions
+
+The user is able to enjoy the e-game event services provided by 3rd party provider via Network A's access.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+From TS22.101:
+
+Note that Multiple USIM requirements apply in case credentials for hosting network access are from a USIM.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR.5.6.6-1] The 5G system shall support means for a hosting network to provide a 3rd party with configuration information for automatic discovery of the hosting network and available access to specific 3rd party services.
+
+[PR.5.6.6-2] The 5G system shall enable a UE to be able to use the 3rd party provided configuration to discover, select and access to a hosting network, and configuration and/or credentials to access for specific services with a certain time (starting time and duration) and location validity.
+
+[PR.5.6.6-3] The 5G system shall be able to inform a UE about available 3rd party services and hosting network the UE can use at a given point in time (starting time and duration) and location.
+
+## 5.7 (E-)Sports events at a venue: User selection of 3rd party provider services over Hosting network access.
+
+### 5.7.1 Description
+
+Network A infrastructure is deployed in multiple sport venues. Network A may be a PLMN or an NPN. A 3rd Party content provider has negotiated with Network A to set-up access to the 3rd party provider's services during the event and at the venue location, and for Network A to manage resources for that service.
+
+The 3rd party provider services are offered to anyone attending and/or participating in the event, without any previous subscription to Network A and without a previous service agreement with the 3rd party provider to access the event services.
+
+The user discovers the service when attending the event.
+
+Two main discovery possibilities are considered:
+
+1. Offline user awareness: The user is notified offline of the available service provided by the 3rd party provider during the event, e.g. this information is included in the event ticket, event flyers or posters.
+2. Online user awareness: The user discovers directly the available service based on information provided by network A. In this case, Network A provides 3rd party / event information, and (potentially on-demand) a human readable advertisement of exclusive content.
+
+The event information as provided by Network A is displayed to the user. A user interested in receiving the 3rd party services during the event selects a certain service. The UE then indicates the desired 3rd party provider service for the event to Network A.
+
+The user is directed to a 3rd party provider portal to subscribe to the event service, e.g. pay for the service, agree to terms and conditions, etc. The UE is then authorised to access the desired 3rd party provider service via Network A. The UE then accesses the 3rd party provider services via Network A's access at the event location.
+
+### 5.7.2 Pre-conditions
+
+Network A and 3rd Party Content Provider B have a service pre-agreement for 3rd Party Content Provider B to offer exclusive service via Network A's access during the game event at the event location. Network A is configured accordingly.
+
+The 3rd party service is meant to be offered to event participants that may not have any subscription to Network A or prior service agreement with 3rd party provider for the event service.
+
+### 5.7.3 Service Flows
+
+1. A user is made aware of the 3rd party service being offered via Network A's access. This may be done either offline (e.g., in ticket, flyer, posters) or provided online by Network A.
+2. The user manually selects 3rd party provider service.
+3. UE indicates the selected 3rd party provider service to Network A.
+4. The user is directed to a portal to receive the authorisation to use the event service of a 3rd party provider, e.g. pay for the service, agree to terms and conditions, etc.
+5. The UE is then authorised to access the 3rd party provider service via Network A.
+6. UE accesses the 3rd party provided service via Network A based on the received authorisation.
+7. The user is able to enjoy the e-game event services provided by 3rd party provider via Network A's access.
+
+### 5.7.4 Post-conditions
+
+The user is able to enjoy the e-game event services provided by 3rd party provider via Network A's access.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+From TS 22.261, clause 6.14.2:
+
+Based on operator policy, the 5G system shall support a mechanism to provision on-demand connectivity (e.g. IP connectivity for remote provisioning). This on-demand mechanism should enable means for a user to request on-the-spot network connectivity while providing operators with identification and security tools for the provided connectivity.
+
+Note that this use case may require enhancements to allow access for the purpose of subscribing to specific 3rd party provider event services via the hosting network access. See [PR.5.7.6-1] below.
+
+From TS22.011, clause 3.2.2.2:
+
+Text on “restricted local operator services” may partly cover the use case functionality.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR.5.7.6-1] The 5G system shall support means for a UE to access via a hosting network, with no prior subscription to that hosting network or to a 3rd party provider, for the purpose of making use of specific 3rd party provider service via the hosting network.
+
+## 5.8 Hosting network deployment for a temporary event
+
+### 5.8.1 Description
+
+A temporary Hosting Network A is set up at the mountain pass Col du Tourmalet in the French Pyrenees to support completion of the 14th stage of Tour de France. Hosting Network A is set up as a Standalone Private Network. A 3rd party service provider can lease this hosting network to provide the service (e.g. streaming video) to its users. The owner and operator of Hosting Network A can also be the operator of PLMN Network B, or the owner/operator of Hosting Network A can have a service agreement with PLMN Network B operator. According to the service agreement, PLMN Network B operator allows Hosting Network A operator to advertise services in the PLMN and solicit PLMN users to access the services provided by the hosting network for the temporary event. PLMN Network B’s billing infrastructure can be utilized to charge the users for the service and the two operators can share the revenue generated by the service.
+
+The users in PLMN Network B receive service advertisement over the PLMN, e.g. via SMS or broadcast information. If the users are interested and consent to use the service, they can request, over the PLMN, a temporary subscription to the hosting network and acquire network discovery/selection information (e.g. network identifier of the hosting network) and temporary credentials for accessing the hosting network. Based on the user’s subscription and credit information with the PLMN Network B, the PLMN network can specify relevant service requirements, like QoS requirements and charging information (e.g. monetary or volume credit), for the service usage in the Hosting Network A. When the users are within the service area, the user can manually or automatically select the hosting network according to the acquired network discovery/selection information and access the network using the acquired temporary credentials in addition to the existing PLMN connection, or manually select to leave the existing PLMN connection to connect to the hosting network.
+
+### 5.8.2 Pre-conditions
+
+The operator of Hosting Network A has a service agreement with the operator of PLMN Network B.
+
+The users of PLMN Network B don’t have any subscription or configuration data for the temporary Hosting Network A.
+
+### 5.8.3 Service Flows
+
+1. A PLMN user receives over its serving PLMN network a service advertisement of the event completion of the 14th stage of Tour de France. The service advertisement is broadcasted in the PLMN in a variety of ways such as SMS and system information.
+2. The user consent to use the service and submit a request over the PLMN to obtain a temporary subscription to the Hosting Network and the service.
+3. The PLMN network and the Hosting Network coordinate to generate the network access information and the temporary credentials for the user. The hosting network access information and the user’s temporary credentials is delivered to the UE over the PLMN network.
+4. During this process, the Hosting Network obtains the service requirements suggested by the PLMN and execute the requirements accordingly (e.g. selecting the proper slicing information and QoS rules) and also obtains the user’s information for charging so it can charge the user through the PLMN.
+5. During the time period that the service is available, and if the user is within the area where the service is available, the user can manually or automatically select the hosting network and access the hosting network
+
+using the obtained temporary credentials in addition to the existing PLMN connection, or manually select to leave the existing PLMN connection to connect to the hosting network.
+
+### 5.8.4 Post-conditions
+
+The user is able to enjoy the service provided by the hosting network.
+
+The user device automatically discards the hosting network access information and temporary credentials after the event is over.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+Providing information to the user can be done on user plane with SMS, MMS etc.
+
+From 3GPP TS 22.261 [2], clause 6.14.2:
+
+Based on MNO and NPN policy, the 5G system shall support a mechanism to enable MNO to update the subscription of an authorized UE in order to allow the UE to connect to a desired NPN. This on-demand mechanism should enable means for a user to request on-the-spot network connectivity which is authorized by its MNO.
+
+From 3GPP TS 22.261 [2], clause 6.18.2:
+
+The 5G system shall enable users to obtain services from more than one network simultaneously on an on-demand basis.
+
+For a user with a single operator subscription, the use of multiple serving networks operated by different operators shall be under the control of the home operator.
+
+From 3GPP TS 22.263 [3], clause 5.6:
+
+The 3GPP system shall be able to enable a UE to receive low-latency downlink multicast traffic from one network (e.g. NPN), and paging as well as data services from another network (e.g. PLMN) simultaneously.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR.5.8.6-1] The 5G system shall allow a network to coordinate with a hosting network to create temporary credentials for a subscriber for accessing the hosting network.
+
+[PR.5.8.6-2] A UE shall be able to automatically discover a hosting network based on received network access information. If the UE is able to obtain services from two networks simultaneously, it may automatically additionally select the hosting network. If the UE cannot maintain the connection to the PLMN while selecting the hosting network, the selection shall only be done on request by the user, i.e. using manual selection.
+
+[PR.5.8.6-3] The 5G system shall allow a UE to manually or automatically be disconnected from the hosting network and discard the hosting network access information and temporary credentials.
+
+[PR.5.8.6-4] The 5G system shall enable a mechanism for a hosting network to receive service requirements from the home PLMN network
+
+## 5.9 Regulatory requirements in a network providing access to localized services
+
+### 5.9.1 Description
+
+This use case describes how a hosting network will have to provide regulatory services such as PWS, LI and emergency calls. Even though the hosting network may be a Non-Public Network, from a regulatory point of view it will be seen as a telecommunications network that provides services to the public.
+
+### 5.9.2 Pre-conditions
+
+A football stadium is equipped with a hosting network. The network can support all kinds of services for spectators, fans, media production, security et cetera. Visitors to the stadium are provided with access to the network to get access to a host of different localized services aimed at fans/spectators. The hosting network with its excellent coverage and capacity in the stadium also provides access to non-localized operator services
+
+### 5.9.3 Service Flows
+
+The popular band, V3 is on a worldwide tour. One of the venues on their tour is the Acme Arena, a football stadium that can hold 50.000 spectators. The concert is sold out, 50.000 fans are enjoying the show. They are also enjoying the localized services provided in the stadium. Via their mobile phones, they can receive an enhanced audio experience, get song text and other additional information, and chat with other fans in a fan-oriented social media application.
+
+Unfortunately, there is an attempted terrorist attack during the pop concert. A member of the audience notices suspicious behaviour and makes an emergency call. The audience is then warned using PWS to evacuate part of the stadium. Because one of the terrorists was already a target for lawful intercept, law enforcement quickly found out that this terrorist was coordinating the attack with other persons, who were quickly apprehended.
+
+### 5.9.4 Post-conditions
+
+The situation in the stadium comes back to normal, thanks to timely response by law enforcement. This was made possible through the use of regulatory services (emergency calls, PWS, and LI).
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+PWS, LI, and emergency calls are already defined for PLMNs.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+[PR.5.9.6-1] A hosting network using the 5G system shall be able to support regulatory services (e.g. PWS, LI, and emergency calls) when Providing Access to Localized Services to the public, based on regional/national regulatory requirements.
+
+## 5.10 Proximate Resources Use Case
+
+### 5.10.1 Description
+
+This use case explores the need to constrain both the location of network services for localized access as well as the timing of these services. The justification for the network is an 'event' which occurs in a particular place for a limited duration. What is more, the event offers different services which have different requirements, as there is more infrastructure involved than just the telecommunications network.
+
+For this use case, we consider a fairground that includes an indoor and outdoor amphitheater. The events offered at this complex can include multimedia performances, with different events occurring at the same time at the two venues.
+
+
+
+Diagram of The Proxima Performing Arts Complex layout. A 'Parking Lot' rectangle is connected by a road to a 'Pavillion' oval. The 'Pavillion' is connected to an 'Outdoor Amphitheater' oval. The 'Outdoor Amphitheater' contains a 'Backstage' rectangle, a 'Stage' rectangle, and a 'Seating' oval. Below the 'Outdoor Amphitheater' is an 'Indoor Amphitheater' oval, which also contains a 'Backstage' rectangle.
+
+**Figure 5.10.1-1: The Proxima Performing Arts Complex**
+
+### 5.10.2 Pre-conditions
+
+The Proxima Performing Arts Complex offers network infrastructure that can be used to host events. One network covers the entire facility, including the entry road (in case there is heavy traffic), the parking lot, registration pavilion and the two amphitheatres. The amphitheatres can be configured to allow specific network services in the immediate locality. The use for this specific spatial configuration will be illustrated in the use case below. Another resource provided by the Proxima Performing Arts Complex is a data center (with easy extensibility for customer equipment.) This allows the deployment of a Service Hosting Environment on the premises to enable low latency communication if needed by the performance technology.
+
+This use case assumes interaction with the event organizers – to arrange specific space and time constraints, as well as procedures for allowing UEs of registered (paying) guests to gain access to the network. This could occur for example in the Pavillion – as one purchases a ticket, one is assisted with registration on the Proxima Performing Arts Complex network. Some specific equipment for spectators of the multimedia events is also supplied by the Arts Complex for use during the event.
+
+### 5.10.3 Service Flows
+
+Arnold parks his car and enters the Pavillion. As he pays for admission, he is able to configure his UE to gain access to the whole Proxima Performing Arts Complex. Arnold is issued a multimedia headset.
+
+Arnold attends the Outdoor Amphitheater for a musical and dance performance. The audience can experience the dancers' performance as if each were in the front row. The realistic experience is only possible through the ultra-low latency communication between the audience members' devices and the servers in the Service Hosting Environment in Amphitheater 1.
+
+At the same time, the indoor amphitheater provides a virtual pageant, where all the guests appear to be in costume (through augmented reality), roaming in a fanciful virtual architecture. There are separate smaller 'stages' in this amphitheater – depending on where the audience walks, they hear the performance of the musician they approach close enough to.
+
+These two programs are extremely network intensive, with a sophisticated data center backstage. They operate simultaneously.
+
+Later, performers are split between both stages and combined into a single concert for each amphitheater. This particular performance requires a single network to extend over both Amphitheatres with significant resources.
+
+As Arnold leaves the event, he can continue to listen to the extended encore from his UE, as he returns to his car and exits the parking lot.
+
+### 5.10.4 Post-conditions
+
+For Arnold, the event provided a set of unique localized experiences, lasting for as long as the performance. For the performers, the network enabled them access to all the resources they needed (especially important in the later event, where the musicians performed on different stages in different buildings). The network reconfigured localized services according to the schedule.
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+[PR5.10.6-1] The 5G System shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of their spatial extent (in terms of a particular topology, for example a single cell), as specified by a third party.
+
+[PR5.10.6-2] The 5G System shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of the resources or capacity available, to correspond to requirements that apply only to the locality of service delivery, as specified by a third party.
+
+[PR5.10.6-3] The 5G System shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of timing, as specified by a third party. This timing shall be flexible, so that a change in service provision can be decided at any time (e.g. to cancel or prolong local services in the locality of service delivery.)
+
+[PR5.10.6-4] The 5G System shall support a Service Hosting Environment in a network that provides access to localized services.
+
+## 5.11 Use Case of home network steering UEs to different localized service networks
+
+### 5.11.1 Description
+
+There can be different local host networks in one location with overlapping coverage but for different localized services. A home network may establish business agreements with some or all of those local hosting network providers in that location, based on different user demands or other business considerations. Therefore, it can be desirable for the home network to be able to steer its UEs in certain location to different local host networks.
+
+### 5.11.2 Pre-conditions
+
+Network A (NW-A) has a long-term business agreement with a local network B (NW-B) in city named Boring. Normally, when NW-A's UEs visit Boring, they connect to NW-B for connectivity service. In order to change the impression of being a boring city, Boring's city council decides to have a big city fair in their football stadium for 4 days. There will be multimedia shows and some famous internet video games being hosted locally in the stadium. Visitors can use their mobile devices to access those local services. The stadium decides to open-up its 5G private network as localized service network (NW-C) for that period of time to allow the authorized visitors to access those shows and games, as well as provide connectivity for other networks' UEs in that location. NW-C solicited the localized services to NW-A. Therefore, NW-A reaches agreement with this NW-C to have an option to allow its UEs to use NW-C's network in order to access the fair applications as well as other the connectivity service provided by NW-A during the period when NW-C provides localized service. NW-A may offer new subscription option to allow user to access the localized services provided by its partner.
+
+### 5.11.3 Service Flows
+
+Step 1: Before the fair starting, NW-A's UEs only roam into NW-B automatically when they are in Boring.
+
+Step 2: When the fair starts, NW-A finds that the number of its UEs in Boring increase significantly and most of them are concentrating in that stadium area. This causes NW-B to be overloaded, which leads to the QoS deterioration of the NW-A's UEs in NW-B.
+
+Step 3: Because NW-A has signed e-agreement with NW-C to enable NW-A's UE to get connected to NW-C during this fair period, NW-A decides to steer some UE with the new localized service agreement from NW-B to NW-C.
+
+Step 4: NW-A selects and steers some of its UEs in the coverage of NW-C to switch from NW-B to NW-C. NW-A may have the capability to only steer the UEs which are in the good coverage of NW-C and also subscribed to use the localized services (e.g., playing the games in the stadium) in NW-C. For those NW-A UEs, which are in Boring city
+
+but not near the stadium or even in the coverage of NW-C but considered not suitable to steer to NW-C by NW-A (e.g., without the needed subscriptions), will continue to use NW-B.
+
+Step 4a: Jacob of NW-A who has subscribed the localized service is in the fair and playing an internet game with his friends using the game edge server in Boring. He found out that the game is also hosted locally in the fair, and his friends are connecting to the local server to get better performance. Therefore, even he may not get steering instruction from NW-A, Jacob decides to switch from NW-B to NW-C. After connecting to NW-C, Jacob's IP connection with the game edge server in Boring has been seamlessly moved to the local server in the stadium associated with NW-C.
+
+### 5.11.4 Post-conditions
+
+Some of NW-A's UEs in the stadium leave NW-B and connect with NW-C per the instructions from NW-A, without any user involvement and the services being interruption. NW-A's users who are in the fair are enjoying the multimedia shows and games using their smartphones connecting to NW-C, while other NW-A's UEs who are not in the fair or not interested in the fair will continue to access other services via NW-B with good QoS quality.
+
+After the fair completes, all NW-A's UEs will continue to automatically select and use NW-B's network in Boring, even if stadium NW-C is still operating for its own users.
+
+### 5.11.5 Existing features partly or fully covering the use case functionality
+
+The existing service requirements for roaming users assume that roaming policies are in place for UEs to use their home network services.
+
+TS22.011 [5], 3.2.2.8:
+
+Steering of roaming allows the HPLMN to steer a UE to a VPLMN on which the HPLMN wants the UE to register, when the UE registers on another VPLMN. This capability may be needed for reasons e.g., reselection to a higher priority PLMN based on business arrangements.
+
+### 5.11.6 Potential New Requirements needed to support the use case
+
+[PR.5.11.6-1]: The 5G network shall be able to allow the home network to steer its UE(s) to a hosting network with the consideration of the location, times, coverage of the hosting network and services offered by the home network and hosting network.
+
+NOTE: Both the home and the hosting network can be a PLMN or NPN, but only subscribers of a public network can be steered to a PLMN
+
+## 5.12 Use case for Network selection based on application for localized services
+
+### 5.12.1 Description
+
+A live concert with high-resolution video application service is provided with service provider A. A local hosting network A (e.g., NPN) is available and provides localized services for high-resolution video service of the concert. The high-resolution video streaming service of the live concert is only available to be accessed from the local edge server which can only be connected via the local hosting network A while a PLMN network B can offer the connection to normal video application service provided by the service provider A. Hosting network A and PLMN network B are two separate networks with no roaming agreement. The service provider A and the hosting network A can be the same party or they have a service agreement. Hosting network A can have a service agreement with PLMN Network B operator. According to the service agreement, PLMN Network B operator can configure the UE with a policy (e.g., UE policy) in order to allow the UE to connect to the hosting network A with high resolution video if the user selects high resolution video from the start. Alternatively, with the service agreement, PLMN Network B operator can instruct the UE to connect to the hosting network A with the exclusive access to the high-resolution video if the user selects high resolution video from normal video service. Charging of the service can be done via the PLMN Network B's billing infrastructure and the two operators can share the revenue generated by the service. The UE mentioned in the use cases below is a single radio UE without specific capability required.
+
+The user may select to have the high-resolution video service from the start. The UE can be configured by the PLMN to have a UE policy (e.g., including a predefined time and a defined area) that instruct the UE to connect to the hosting network A for high-resolution video application service. The trigger for the UE policy configuration can be initiated by the service provider A who receives the request from application level that the user wants to watch high resolution video of the live concert. The user can watch the high-resolution video of the live concert after the UE automatically connect to the hosting network A.
+
+Alternatively, the user may select the high-resolution video service while watching normal video service at the concert. The UE can be instructed by the PLMN to switch to hosting network A for the high-resolution video service. The instruction can be initiated by the service provider A who receives the request from application level that the user want to watch high resolution video of the live concert. The user can watch the high-resolution video of the live concert after the UE automatically connects to the hosting network A.
+
+### 5.12.2 Pre-conditions
+
+The service provider A has a service agreement with the operator of PLMN network B and the hosting network A.
+
+The operator of hosting network A has a service agreement with the operator of PLMN network B.
+
+The users of PLMN Network B have the subscription for the hosting network A.
+
+### 5.12.3 Service Flows
+
+Use case A: User selects the high-resolution video application service from the start.
+
+1. A number of users use their UEs (e.g., smart phones) to buy tickets to the concert through the portal provided by service provider A before the concert.
+2. The service provider A triggers the PLMN to configure the UE with a UE policy for the network selection for the high-resolution video application service of the concert.
+3. After the start of the concert, users select to watch high-resolution video of the concert when they arrive the venue.
+4. The UE identifies the information of hosting network A based on the mapping relation between the application service information and the network information (e.g., the identity of hosting network A) in the UE policy and search for the broadcasting message from the hosting network A.
+5. UE connects to the hosting network A upon the receipt of the broadcast information, which contains the identity of hosting network A, from the hosting network A and gets access to the high-resolution video service of the concert.
+
+Use case B: User firstly watches normal video application service and triggers to watch high resolution video service.
+
+1. A number of users buy tickets to the concert through the portal provided by service provider A before the concert.
+2. After the start of the concert, user watches the normal video of the concert through PLMN and triggers to select the high-resolution video (e.g., with different selectable view angle of the concert) because the user may not satisfy with the normal video service of the concert.
+3. The service provider A triggers the PLMN to instruct the UE to get connected to the hosting network A in order to get access to the high-resolution video service which is only available through the hosting network A.
+4. UE connects to the hosting network A and gets access to the high-resolution video service of the concert.
+
+### 5.12.4 Post-conditions
+
+Users who select the high-resolution video service can enjoy their desired high-resolution video service of the live concert.
+
+### 5.12.5 Existing features partly or fully covering the use case functionality
+
+N/A
+
+### 5.12.6 Potential New Requirements needed to support the use case
+
+[PR.5.12.6-1] The 5G system shall enable a service provider to request the home network to instruct a UE under which conditions (e.g. predefined time, location) it could select a certain hosting network.
+
+[PR.5.12.6-2] 5G system shall enable the home network to instruct a UE to automatically select a hosting network for accessing localized services when specified conditions (e.g. predefined time, location) are fulfilled.
+
+## 5.13 Broadcast and Multicast Local Service Use Case
+
+### 5.13.1 Description
+
+This use case describes a local service network that provides numerous spectators with simultaneous media services in an efficient manner. As a scenario, we consider a stadium, that periodically hosts events that can benefit from multicast and broadcast services for the benefit of spectators.
+
+### 5.13.2 Pre-conditions
+
+Rajesh is big fan of Cricket and he loves watching Cricket matches in Stadium. Cricket matches are typically long e.g. about 7 hrs for one day matches and 3-4 hours for T20 matches. Rajesh looks forward to the variety of streaming videos / informative content for replays, scores and statistics that the organizers promise to provide to the spectator present.
+
+Rajesh has his ticket and thereby the event organizers have some information about Rajesh and can provide information to Rajesh.
+
+Commercial advertisements and other services in stadium e.g., related to food services etc. can be promoted via the communication services and may bring revenue generation options for host venue, host network and service providers.
+
+Arrangements between the commercial advertisers and service providers in the location have been established before the event.
+
+### 5.13.3 Service Flows
+
+Rajesh avidly watches a video streamed program using broadcast services provided by his home (or serving) PLMN.
+
+When Rajesh enters the stadium, he obtains access to the hosting network.
+
+Rajesh's broadcast service from his home (or serving) PLMN continues – with service continuity. While at the stadium, Rajesh continues to have access to the services in his home (or serving) PLMN, *including multicast and broadcast services* from his home network.
+
+Rajesh obtains access to the services provided in the stadium. This access includes a clear directory of services available, so that Rajesh can tune to different content. Some local services are provided using multicast and broadcast. These include different views of the play (from different perspectives), continuously updated scores and statistics and commentary by professional announcers on site.
+
+Both the streamed action and information may come with localized advertisement – included in the media stream as part of the content.
+
+The content delivery is itself may be a service for which Rajesh will be charged. This charging may take different forms: permission to access to the content or use of the content (e.g., pay per minute of use, etc.)
+
+Since Rajesh will access streamed services for long periods of time, it is extremely important that these services can be delivered in an energy efficient manner. Otherwise, Rajesh's UE will run out of batteries long before the exciting conclusion of the match.
+
+### 5.13.4 Post-conditions
+
+Rajesh's services (including multicast and broadcast services) functioned with continuity, from before he entered the stadium, even as he accessed the local service network. While at the stadium, Rajesh still was able to receive calls and access other services of his home network.
+
+He was able to access streaming and informative services at the stadium subsequent to getting access to the local service network. The costs of these services were either included in the cost of admission, covered by advertising or arranged for separately specifically for the services and content that Rajesh accessed. After hours of use, he had not drained his mobile device's battery due to the excellent energy efficient delivery of service.
+
+Rajesh is impressed with the congestion free reception of services (without lags and delays) and excellent responsiveness of network services in the stadium environment. While in the stadium, Rajesh continued to use services from his home network. As he leaves the stadium, there is a seamless transition, as these services continue, using the macro network. Rajesh returns home happily.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+Support for Flexible broadcast/multicast service as per TS 22.261 [2], clause 6.13.
+
+TS 22.261 [2], 5.1.2.1
+
+The 5G system shall support a UE with a 5G subscription roaming into a 5G Visited Mobile Network which has a roaming agreement with the UE's 5G Home Mobile Network.
+
+The 5G system shall enable a Visited Mobile Network to provide support for services provided in the home network as well as provide services in the visited network. Whether a service is provided in the visited network or in the home network is determined on a service by service basis.
+
+TS 22.261 [2], 6.13.2
+
+The 5G system shall support operation of downlink only broadcast/multicast over a specific geographic area (e.g. a cell sector, a cell or a group of cells).
+
+TS 22.261 [2], 6.25.2
+
+Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall support for non-public network subscribers:
+
+- access to subscribed PLMN services via the non-public network;
+- seamless service continuity for subscribed PLMN services between a non-public network and a PLMN;
+- access to selected non-public network services via a PLMN;
+- seamless service continuity for non-public network services between a non-public network and a PLMN.
+
+Service delivery and continuity of applications over unicast and multicast, as controlled by the application, as described (without naming these modes) in TS 22.468 GCSE\_LTE, more explicitly in TS 23.468 and TS 29.468. Also related are TS 26.346 Multicast operation on Demand and northbound APIs TS 26.348 (Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point).
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+[PR5.13.6-1] The operator of a hosting network shall support a mechanism allowing different local service providers and content providers to disseminate their services and content over broadcast/multicast transport. This mechanism should also provide a means to include diverse content in the same transmission, e.g., to include advertisements with other content, or to include multiple content in the same media delivered to the user.
+
+[PR5.13.6-2] A hosting network shall provide multicast and broadcast services in an energy efficient manner to UEs receiving this service.
+
+[PR5.13.6-3] A hosting network shall support resource efficient content delivery through multicast/broadcast and intelligent caching of contents at UEs.
+
+NOTE1: The intent of this requirement is to effectively achieving higher resource efficiency for service delivery.
+
+[PR5.13.6-4] A hosting network shall support a mechanism to provide low latency signalling for efficient delivery of content to the UE.
+
+NOTE2: Signalling may include many operations including session management and radio communication.
+
+[PR5.13.6-5] Subject to home operator policy, a hosting network shall be able to prioritize specific services for local access over home routed access, even if the same service is available in both networks.
+
+NOTE3: This requirement differs from the text in 22.261, 6.18 “In the event of the same service being offered by multiple operators, unless directed by the home operator's network, the UE shall be prioritized to receive subscribed services from the home operator's network.” This is intended to permit low latency access to certain content and services in the hosting network.
+
+## 5.14 Use case: managing a high number of UEs returning from a local hosting network to home network
+
+### 5.14.1 Description
+
+This use case describes a scenario where a local hosting network has provided event-based temporary local services to PLMN users to enjoy during either a live event such as a sport game, concert or a several days long event such as industry fairs or conferences. Once the event is over, the PLMN users who have accessed and enjoyed the event-based local service(s) will no longer need to use these services and therefore wish to terminate the services. Therefore, a high number of users (e.g. thousands in stadium venues) are likely to want to terminate their access/service to the local hosting network and attempt a fairly simultaneous registration back to their home PLMN. The hosting network operator may also decide to switch off the local network while there still are many UEs that are connected to the local network. This may lead to a signaling peak in the home PLMN and result in longer time scales for users to re-register to/re-select their home PLMN. Therefore, it is desirable that user registrations are managed by spreading out the registration attempts over time and limiting the number of users attempting to register simultaneously, to avoid signaling overload and unnecessary waiting times for the returning users.
+
+### 5.14.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- Hosting network and PLMN have an agreement (either short-term or long-term).
+- PLMN users are aware of the local services provided by the hosting network.
+
+### 5.14.3 Service Flows
+
+1. Before the event, PLMN users start to access the local services occasionally at different times.
+2. During the event, PLMN users consume the local services provided by the hosting network.
+3. When the event is over:
+ - a) the PLMN users terminate their access to the local services and attempt registration back to their home PLMN;
+ - b) the PLMN users leave the venue and attempt registration back to their home PLMN; or
+ - c) the hosting network is switched off and the PLMN users are forced to attempt registration back to their home PLMN.
+4. PLMN users register back to their home PLMN.
+
+### 5.14.4 Post-conditions
+
+The PLMN users who have temporarily accessed the local services of the hosting network return to their home PLMN without causing signaling overload/congestion and within the shortest possible time scales.
+
+### 5.14.5 Existing features partly or fully covering the use case functionality
+
+There are existing features that may support management of simultaneous registration attempts from a high number of users:
+
+3GPP TS 22.011 [5], clause 4.3.1: Access Class Barring
+
+- The serving network shall be able to broadcast mean durations of access control and barring rates (e.g. percentage value) that commonly applied to Access Classes 0-9 to the UE.
+
+3GPP TS 22.011 [5], clause 4.3.2: Service Specific Access Control
+
+- The serving network shall be able to indicate (as specified in clause 4.3.1) whether or not a UE subject to SSAC shall also apply Access Class Barring.
+- The UE determines the barring status with the information provided from the serving network, and perform the access attempt accordingly.
+
+3GPP TS 22.011 [5], clause 4.3.4: Extended Access Barring
+
+- Extended Access Barring shall be applicable regardless of whether the UE is in a Home or a Visited PLMN.
+
+3GPP TS 22.261 [2], clause 6.22.2: Unified access control: Requirements
+
+- The UE shall be able to determine whether or not a particular new access attempt is allowed based on barring parameters that the UE receives from the broadcast barring control information and the configuration in the UE.
+- The unified access control framework shall be applicable to inbound roamers to a PLMN.
+
+3GPP TS 22.261 [2], clause 6.19.2: 3GPP access network selection: Requirements
+
+- The 5G system shall support, subject to operator policies, a User Controlled PLMN Selector list stored in the 5G UE, allowing the UE user to specify preferred PLMNs with associated RAT identifier in priority order.
+
+3GPP TS 22.261 [2], clause 6.31.2.3: Minimization of Service Interruption: Requirements: Disaster Roaming:
+
+- Disaster Inbound Roamers shall perform network reselection when a Disaster Condition has ended.
+- The 3GPP system shall minimize congestion caused by Disaster Roaming.
+
+It is worth to note that the given existing features in 3GPP TS 22.261 [2] clause 6.31.2.3 are only applicable in case there is a Disaster Condition. Specific procedures are followed to notify Disaster Condition and identify Disaster Inbound Roamers. Thus, the noted features above cannot be applied to any use case that is not in Disaster Condition.
+
+### 5.14.6 Potential New Requirements needed to support the use case
+
+[PR 5.14.6-1] The 5G system shall provide mechanisms to mitigate overload caused by UEs returning from a temporary local access of a hosting network to their PLMN network.
+
+[PR 5.14.6-2] The 5G system shall provide mechanisms to minimize the impact on the UEs communication e.g. due to outages when returning to a PLMN after terminating their temporary local access to a hosting network.
+
+## 5.15 Localized 5G network access on a cruise ship
+
+### 5.15.1 Description
+
+Cruising has become a major part of the tourism industry, serving more than 13 million passengers worldwide. Cruise ships typically embark on round-trip voyages to various ports-of-call, where passengers may go on tours known as
+
+"shore excursions". Alternatively, cruise ships may also make two to three night round trips without visiting any ports of call, spending multiple days and nights in the sea. Telecommunication is one of the services offered onboard of the cruise ships enabling internet services for the passengers.
+
+In this use case Truman, a tourist, is embarking on a round-trip voyage in a 5G PALS enabled cruise ship called SeaQueen. The SeaQueen will voyage across the Pacific Ocean and is intended to make three different shore excursions before returning to its port of embarkment. Truman has a 5G enabled mobile phone and has subscribed for the premium 5G telecommunication services offered by the SeaQueen's parent company "Royalty cruises". Being a regular customer of the SeaQueen and its sister ships operated by "Royalty cruises", Truman has provided some personal identification information (e.g. passport, picture, biometrics) and his personal preferences while making the booking to allow for fast automatic check-in and to quickly gain access to the premium 5G telecommunication services.
+
+On the day of embarkment, Truman arrives at the port of embarkment. Upon entering the SeaQueen, Truman receives an invitation to an access portal on his mobile phone. The portal allows him to gain access to the SeaQueen's 5G system. Since Truman is a well-known customer, he does not fill in lengthy registration forms or fill in a user name and password. Instead, Truman identifies himself via a biometric scanner in his mobile phone to the access portal of the 5G system. Upon identification by the SeaQueen's 5G system, a network profile containing the necessary credentials and personalized network & device configurations for Truman (based on his premium service and personal preferences known to "Royalty cruises") is automatically provisioned in his 5G device. Truman's mobile phone can now obtain PALS services which, among others, are superfast 5G internet access (via backend satellite connection), access to premium video and payment services, and automatic access to specific locations in the ship (e.g. through ranging service). In addition, one or more profiles may be provisioned to Truman's mobile phone to allow 5G network access during activities on shore, for each country that they intend to visit, without having to worry about buying a local SIM card or identifying a roaming plan according to his personal preference during the excursion.
+
+At the end of the cruise voyage the 5G system on board of the SeaQueen decommissions the network profile of the local 5G network from Truman's device (e.g. based on a trigger, such as a timer expiring at the end of the trip or location of the user, e.g. the gangway to exit the ship).
+
+### 5.15.2 Pre-conditions
+
+Truman has a 5G enabled mobile phone UE with an eSIM.
+
+Various personal details of Truman, including some biometric identity information, are pre-shared with SeaQueen's parent company "Royalty cruises" in accordance with GDPR and other privacy regulations.
+
+The SeaQueen's 5G system has a direct satellite link for 5G services and may have contractual agreements with the local 5G network operators on shore (for each country that they plan to visit).
+
+The SeaQueen's 5G system may be an NPN or a PLMN.
+
+### 5.15.3 Service Flows
+
+- Upon arrival at the port of embarkation, Truman receives an invitation to an access portal on his 5G mobile phone.
+- Since Truman is a known customer, Truman can identify himself via the biometric sensor of his mobile phone.
+- The identity service of the SeaQueen 5G system identifies Truman based on his biometric identity data that he provided beforehand.
+- Upon identification the corresponding network profile is generated, which contains the necessary credentials, and personalized network and device configurations for Truman, based on his premium services and his personal preferences known to "Royalty cruises".
+- The personalized network profile is securely downloaded to his mobile phone via the SeaQueen 5G system.
+- Truman can now make use of the superfast 5G network connection and localized services onboard the SeaQueen vessel are enabled in alignment with his profile. This includes premium video services, automatic access to specific locations on the ship, and also includes getting 5G service on shore during the excursions in each country that they will visit.
+
+- Truman completes the trip and returns to the port of origin, which automatically triggers the de-registration of Truman from the SeaQueen 5G system and the SeaQueen's 5G network profiles are automatically decommissioned from Truman's mobile phone and his own network profile is enabled.
+- Thanks to the 5G PALS system, Truman has truly carefree experience during his cruise trip.
+
+### 5.15.4 Post-conditions
+
+5G device of Truman is decommissioned from the 5G system of SeaQueen. Truman continues to enjoy 5G services with his personal subscription with his home network operator.
+
+### 5.15.5 Existing features partly or fully covering the use case functionality
+
+From Section 8.3 of TS 22.261 [2]: "The 5G system shall support an efficient means to authenticate a user to an IoT device (e.g. biometrics)". However, it is not clear if this requirement also applies to UEs in general or only to a particular subset of UEs, and it is also not clear whether this requirement holds before the IoT device has a network profile for the hosting network installed on that device, i.e. to enable easy provisioning and installation of the respective network profile.
+
+Section 26a of TS 22.101: requirements related to user identity management.
+
+### 5.15.6 Potential New Requirements needed to support the use case
+
+[PR.5.15.6-1] The 5G system shall support a secure means for a UE with no prior subscription to the hosting network to receive human readable information on how to gain access to the hosting network (which may PLMN or NPN).
+
+[PR.5.15.6-2] The 5G system shall support a secure means to authenticate a user of a UE to a hosting network, including cases in which a UE has no subscription to the hosting network yet and still needs to get authorized to gain full access to the hosting network and its services.
+
+NOTE: It can be assumed that a service provider deploying a hosting network has access to respective identification information about the user, e.g. through a separate registration process outside the scope of 3GPP.
+
+[PR.5.15.6-3] The 5G system shall be able to authorize the UE of a user authenticated to a hosting network to access the hosting network and its localized services on request of the service provider.
+
+[PR.5.15.6-4] The 5G system shall be able to withdraw the UE authorization based on certain conditions, such as time or location of the user.
+
+## 5.16 Localized network for a mass casualty incident
+
+### 5.16.1 Description
+
+A mass casualty incident (MCI) describes an event in which the emergency medical services may get overwhelmed by the number and severity of the casualties.
+
+In this use case, a massive terrorist attack has taken place in the capital of the country Haniti. One of the multistorey buildings in the central market area has collapsed with more than 100 victims injured, classifying it as a mass casualty incident (MCI). The public telecommunication services are majorly interrupted since everyone in the vicinity of the incident is trying to contact their families and to stream videos of the incident. A team of first responders has arrived at the MCI location with an ambulance, with a built-in 5G base station. The base station is connected to a 5G network called HanCel capable of supporting PALS. The base station has a total coverage area of 500x500 meters. Also a team of the local police department has arrived and has secured the boundaries of the MCI area, requesting everyone that is not injured to leave the MCI area.
+
+As a feature of PALS, HanCel is capable to make a temporary network available with a delimited 5G service area, providing very good quality of service for the first responders, their devices (such as health monitors), for the injured victims trying to reach their families (using their own UEs) and for the (existing) wireless video surveillance cameras in the area.
+
+One of the first responders can demarcate the boundaries/contours of the MCI area on a map, and provides e.g. a set of coordinates/dimensions of the MCI area to the HanCel network. The HanCel network configures the temporary network in such a way that only the 5G devices present in the MCI area are allowed to connect. The MCI area may be smaller than the coverage of a single cell. In case of larger MCI areas, more cells may be needed to cover the area. The 5G devices of the bystanders that are present outside the crash area, but still within the coverage area of HanCel are not allowed to connect. In order to provide very good QoS in the MCI area, HanCel can configure the use of dedicated spectrum access in the targeted area.
+
+### 5.16.2 Pre-conditions
+
+HanCel is an PALS enabled network in the country Haniti, and is the preferred operator for many first responder organizations in Haniti.
+
+All the operators in the country Haniti have a roaming agreement with HanCel.
+
+### 5.16.3 Service Flows
+
+- A first responder configures the 5G system of HanCel with the dimensions/coordinates of the MCI area, which is a small area within the coverage area of the HanCel network.
+- The 5G system of HanCel network configures a temporary network in such a way that only the 5G devices present in the MCI area are allowed to connect. Bystanders and everyone else outside the MCI area are not allowed to access the network.
+- Thanks to the PALS ability to provide localized services in a targeted area within a larger coverage area, HanCel improved the communication and response time of the first responders in the MCI area, thereby reducing fatal casualties. Also, the victims were able to easily reach their families (using their own UEs), reducing the anxiety and stress of the victims, and the (existing) wireless video surveillance cameras in the area were able to capture all the details of the MCI event.
+
+### 5.16.4 Post-conditions
+
+### 5.16.5 Existing features partly or fully covering the use case functionality
+
+### 5.16.6 Potential New Requirements needed to support the use case
+
+[PR.5.16.6.-1] The 5G system shall be able to provide access to a hosting network only for UEs in a configurable targeted area within the coverage area in a privacy sensitive manner.
+
+NOTE 1: the targeted area may be smaller than the coverage area of a single cell.
+
+NOTE 2: determining location information related to a UE is subject to regional and national regulatory requirements, and is subject to authorization (e.g. of home network operator of a UE) and user consent.
+
+## 5.17 Steering of UEs between hosting local networks and PLMNs
+
+### 5.17.1 Description
+
+A live concert with high-resolution video application service is provided by service provider A and made available in the concert arena both by a local hosting network A and a PLMN network B. The service is offered in PLMN B to users that have credentials to access PLMN B and, in addition, has subscribed to the service. The service is offered in hosting network A to users that have credentials to access the service through hosting network A. It is assumed that the service comes with access credentials through Hosting network A, irrespective of if a user also has access to PLMN network B. This means that there will be UE's in the concert that can access the service either using PLMN network B or hosting network A.
+
+Before or during the concert, service provider A identify a need to move users from hosting network A (e.g., due to capacity limits, expected or occurring service quality issues) and would then update policies (UE policies) for UEs in hosting network A that also has credentials to access the service through PLMN network B, to leave network A and continue the service in PLMN network B.
+
+In the end of the concert, the situation in hosting network A may improve and the service provider A can then request PLMN network B to update UE policies for UE's that are being served by PLMN network B to instead continue the service in hosting network A. When users are, via updated UE policies, instructed to continue services in other network, this can be done without user interaction as long as availability of other services are not impacted.
+
+### 5.17.2 Pre-conditions
+
+The service provider A has a service agreement with the operator of PLMN network B and hosting network A and provides the same service in both networks.
+
+The operator of hosting network A may optionally have a (service or roaming) agreement with the operator of PLMN network B
+
+### 5.17.3 Service Flows
+
+1. Users use their UEs (e.g., smart phones) to buy tickets to the concert through the portal provided by service provider A. The service provider A provides the UE with credentials to access hosting network A and get the service. Additionally, the UE informs the service provider A about presence of credentials for PLMN network B.
+2. The service provider A request PLMN network B to configure the UE with a UE policy for the network selection to receive the high-resolution video application service of the concert via hosting network A.
+3. Service provider A identify a need to move users from hosting network A (e.g., due to capacity limits, expected or occurring service quality issues). Service provider A then request updates of the UE policies for UEs in hosting network A that also has credentials to access the service through PLMN network B, to leave network A and continue the service in network B.
+4. The UEs that switch to PLMN network B connects to the network and start using the service from service provider A.
+5. Service provider A identify that there are opportunities to move users into hosting network A for the service provided, and then trigger a request to PLMN B to update the UE policies for relevant users/UEs to instead continue the service in hosting network A.
+6. PLMN network B may choose to change policies for some of the UE's using the service in its network and subsequently, those UE's will select hosting network A and continue the services from service provider A
+
+### 5.17.4 Post-conditions
+
+Users who select the high-resolution video service can enjoy the service of the live concert from either of the network which service provider A has agreement with and the UE has credentials to.
+
+After the concert ends the UE will automatically select the best network according to normal network selection procedures.
+
+### 5.17.5 Existing features partly or fully covering the use case functionality
+
+N/A
+
+### 5.17.6 Potential New Requirements needed to support the use case
+
+[PR.5.17.6-1] The 5G system shall enable the home network to instruct a UE under which conditions (e.g. predefined time, location) it could select a certain hosting network based on the request from a service provider.
+
+[PR.5.17.6-2] The UE shall be able to select a hosting network or change to another hosting network, using the corresponding credentials as may be indicated, without any additional user consent as long as the delivered services, including the localized services, are unchanged.
+
+# --- 6 Consolidated Potential Requirements
+
+NOTE 1: Both the home and the hosting network can be a PLMN or NPN.
+
+NOTE 2: Only subscribers of a public network can roam into a PLMN.
+
+## 6.1 Configuration of Localized Services in Hosting Network
+
+**Table 6.1-1 – Configuration of Localized Services in Hosting Network Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------|
+| CPR 6.1-001 | The 5G network shall support suitable mechanisms to allow automatically establishing localized service agreements for a specific occasion (time and location) and building temporary relationship among hosting network operator and other service operators including network operators or 3 rd party service providers. | PR.5.3.6-1 | |
+| CPR 6.1-002 | The 5G system shall support means for the service operator to request the hosting network via standard mechanisms to provide access to 3 rd party services at a specific period of time and location. This period of time shall be flexible, so that a change in service provision can be decided at any time (e.g., to cancel or prolong local services in the locality of service delivery) based on localized services agreements. | PR.5.5.6-1 | |
+| CPR 6.1-003 | Based on localized services agreements, the 5G system shall provide suitable means to allow the service operator to request and provision various localized service requirements, including QoS, expected/maximum number of users, event information for discovery, network slicing, required IP connectivity etc, and routing policies for the application of the localized services via the hosting network. | PR.5.5.6-2 and
PR.5.4.6-1 | |
+| CPR 6.1-004 | The 5G system shall support means for a hosting network to create policies and configure resources for the requested time and location for the 3 rd party services based on the received request. | PR.5.5.6-3 | |
+| CPR 6.1-005 | The 5G system shall support means for a hosting network to notify the service operator of the accepted service parameters and routing policies. | PR.5.5.6-4 | |
+| CPR 6.1-006 | Subject to regulatory requirements and localized service agreements, the 5G network shall allow a home network operator to automatically negotiate policies with the hosting network for allowing the home network's subscribers to connect at a specific occasion, e.g., time and location, for their home network services. | PR.5.3.6-2 | |
+| CPR 6.1-007 | Subject to the automatic localized services agreements between the hosting network operator and home network operator, for UE with only home network subscription and with authorization to access hosting networks the 5G system shall support: - - access to the hosting network and use home network services or selected localized services via the hosting network.
- - seamless service continuity for home network services or selected localized services when moving between two hosting networks or a host network and the home network.
| PR.5.3.6-5 | |
+| CPR 6.1-008 | The 5G System shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of their spatial extent (in terms of a particular topology, for example a single cell), as specified by a 3 rd party. | PR.5.10.6-1 | |
+| CPR 6.1-009 | The 5G System shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of the resources or capacity available, to correspond to requirements that apply only to the locality of service delivery, as specified by a 3 rd party. | PR.5.10.6-2 | |
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.1-010 | The 5G system shall support means for a hosting network to provide a 3 rd party service provider with information for automatic discovery of the hosting network by the UEs to allow access to specific 3 rd party services. | PR.5.6.6-1 | |
+| CPR 6.1-011 | The 5G system shall support secure mechanisms to allow a home network to coordinate with a hosting network for a subscriber to temporarily access the hosting network (e.g., based on temporary credentials) at a given time (start time and duration) and location. | PR.5.8.6-1 | |
+
+## 6.2 User Manual Selection of Localized Services via Hosting Network
+
+**Table 6.2-1 – User Manual Selection of Localized Services via Hosting Network Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.2-001 | The hosting network shall allow a UE to manually select temporary localized services which are provided via local breakout at the hosting network.
NOTE : localized services are provided via local breakout at the hosting network based on interworking scenarios for hosting network owned/collaborative services as indicated in Annex A.
| PR.5.4.6-2 | |
+
+## 6.3 UE Configuration, Provisioning, Authentication and Authorization
+
+**Table 6.3-1 – UE Configuration, Provisioning, Authentication and Authorization Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|---------|
+| CPR 6.3-001 | Subject to localized services agreements, the 5G network shall enable a home network operator to authorize a UE for using its home network services via a hosting network for a certain period of time and/or location. | PR.5.3.6-3 | |
+| CPR 6.3-002 | The 5G network shall allow a trusted 3 rd party to provide UEs with localized service policy (e.g., QoS, network slice in the hosting or home network, service restriction such as time and location) via the hosting network or the UE's home network. | PR.5.4.6-1A | |
+| CPR 6.3-003 | The 5G system shall enable a UE to use credentials provided by the hosting network with or without coordination with the home network of the UE, to make use of localized services via the hosting network with a certain time (including starting time and the duration) and location validity. | PR.5.4.6-7 | |
+| CPR 6.3-004 | The 5G network shall be able to allow the home network to steer its UE(s) to a hosting network with the consideration of the location, times, coverage of the hosting network and services offered by the home network and hosting network. | PR.5.11.6-1 | |
+| CPR 6.3-005 | The 5G system shall provide support to enable secure means to authenticate and authorize a user of a UE accessing a hosting network, including cases in which a UE has no subscription to the hosting network and still needs to get authorized to use localized services via the hosting network.
NOTE : It can be assumed that a network provider deploying a hosting network has access to respective identification information about the user, e.g., through a separate registration process outside the scope of 3GPP.
| PR.5.15.6-2 | |
+| CPR 6.3-006 | The 5G system shall be able to authenticate and authorize the UE of a user authenticated to a hosting network to access the hosting network and its localized services on request of a service provider. | PR.5.15.6-3 and PR.5.2.6-2 | |
+
+## 6.4 UE Discovery, Selection and Access
+
+**Table 6.4-1 – UE Discovery, Selection and Access Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------|
+| CPR 6.4-001 | Subject to operator's policy and agreement between a 3 rd party service provider and operator, the 5G system shall enable a UE to receive and use configuration provided by a 3 rd party service provider to discover and access a hosting network and localized services, including the considerations of prior service agreement with a 3 rd party service provider and no prior subscription to hosting network. If the UE is able to obtain services from two networks simultaneously, it may additionally select the hosting network. If the UE cannot maintain the connection to the home network while selecting the hosting network, the selection shall only be done on request by the user, i.e., using manual selection. | PR.5.6.6-2 | |
+| CPR 6.4-002 | The 5G system shall support secure means for a UE to select and access localized services which may be provided by a 3 rd party service provider via a hosting network, independent of prior subscription to the hosting network or 3 rd party service provider. | PR.5.7.6-1 and
PR.5.4.6-8 | |
+| CPR 6.4-003 | The 5G system shall enable the home network to allow a UE to automatically select a hosting network for accessing localized services when specified conditions (e.g., predefined time, location) are fulfilled. | PR.5.12.6-2 | |
+| CPR 6.4-004 | The 5G system shall be able to prevent a UE to re-access the hosting network after the localized services were terminated if the authorization for the localized services is no longer valid (e.g., can be based on certain conditions such as time or location of the user). | PR.5.15.6-4 | |
+| CPR 6.4-005 | The 5G system may support means for a UE which may or may not have prior subscription to the hosting network to display human readable information on how to gain access to the hosting network and available 3 rd party services. | PR.5.15.6-1 | |
+| CPR 6.4-006 | The 5G system shall support a mechanism to allow a user to manually select a specific local hosting network. | PR.5.2.6-1 | |
+| CPR 6.4-007 | The 5G system shall be able to limit access of specific UEs to a configurable area of a hosting network's coverage area. | PR.5.16.6-1 | |
+| CPR 6.4-008 | The 5G system shall be able to maintain privacy of a user against the hosting network while the UE does not make use of the hosting network, for example, to prevent tracking of UEs by hosting networks. | PR.5.16.6-1 | |
+| CPR 6.4-009 | The 5G system shall enable the home network to instruct a UE to select a hosting network with certain conditions (e.g., predefined time, location) based on the request from a service provider. | PR.5.17.6-1 | |
+| CPR 6.4-010 | The 5G system shall enable the home network to allow a UE to select a hosting network or change to another hosting network, without any additional user intervention as long as the delivered services, both localized services and home routed services, are unchanged. | PR.5.17.6-2 | |
+
+## 6.5 Hosting Network Localized Services and Home Operator Services
+
+**Table 6.5-1 – Hosting Network Localized Services and Home Operator Services Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.5-001 | The 5G network shall enable the home network operator to indicate to the UE what services are preferred to be used from the home network when the UE connects to a hosting network and the requested services are available from both the hosting and the home network. | PR.5.3.6-4 | |
+| CPR 6.5-002 | Based on localized service agreements, the hosting network shall be able to provide required connectivity and QoS for a UE simultaneously connected to the hosting network for localized services and its home network for home network services. | PR.5.4.6-3 | |
+| CPR 6.5-003 | A UE shall be able to connect to its home network via the hosting network, if supported by the hosting network and the home network based on localized service agreements. | PR.5.4.6-4 | |
+
+## 6.6 Returning to Home Network
+
+**Table 6.6-1 – Returning to Home Network Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.6-001 | The 5G system shall provide mechanisms to mitigate user plane and control plane overload caused by a high number of UEs returning from a temporary local access of a hosting network to their home network in a very short period of time. | PR.5.14.6-1 | |
+| CPR 6.6-002 | The 5G system shall provide mechanisms to minimize the impact on the UEs communication e.g., to prevent user plane and control plane outages when returning to a home network together with other high number of UEs in a very short period of time, after terminating their temporary local access to a hosting network. | PR.5.14.6-2 | |
+
+## 6.7 Charging
+
+**Table 6.7-1 – Charging Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.7-001 | The 5G system shall be able to collect charging information for the use of localized services at the hosting network and provide the charging records to UEs' home operators based on localized service agreements and charging policies provided by the localized service providers | PR.5.4.6-6 | |
+
+## 6.8 Regulatory Services
+
+**Table 6.8-1 – Regulatory Services Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.8-001 | A hosting network using the 5G system shall be able to support regulatory services (e.g., PWS, LI, and emergency calls), based on regional/national regulatory requirements. | PR.5.9.6-1 | |
+
+## 6.9 Multicast/Broadcast
+
+**Table 6.9-1 – Multicast/Broadcast Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 6.9-001 | The operator of a hosting network shall support a mechanism allowing different local service providers and content providers to disseminate their services and content over broadcast/multicast transport. This mechanism should also provide means to include diverse content in the same transmission, e.g., to include advertisements with other content, or to include multiple content in the same media delivered to the user. | PR5.13.6-1 | |
+| CPR 6.9-002 | A hosting network shall provide multicast and broadcast services in an energy efficient manner to UEs receiving this service. | PR5.13.6-2 | |
+| CPR 6.9-003 | A hosting network shall support resource efficient content delivery through multicast/broadcast. | PR5.13.6-3 | |
+| CPR 6.9-004 | A hosting network shall support a mechanism to provide low latency signalling for efficient content delivery to many UEs. | PR5.13.6-4 | |
+| CPR 6.9-005 | Subject to home operator policy, a hosting network shall be able to prioritize specific multicast and broadcast services for local access over home routed access, even if the same service is available in both networks. | PR5.13.6-5 | |
+
+# --- 7 Conclusions and Recommendations
+
+This technical report provides use cases and potential new requirements. The resulting service requirements have been consolidated in clause 6.
+
+It is recommended to consider the consolidated requirements identified in this TR as the baseline for subsequent normative work.
+
+# --- Annex A: Interworking between Networks Operators and Application Providers for localized services
+
+In TS22.278, Annex B1 [4] provides various scenarios applicable for interworking between mobile operators and data applications for EPS and 5GS including:
+
+- Operator owned non-roaming scenario
+
+- Collaborative non-roaming scenario
+- Operator owned/collaborative roaming scenario – Home Routed
+- Collaborative roaming scenario – Local Breakout
+
+This clause extends the roaming scenarios applicable for interworking between hosting network operator (PLMN or NPN) and data applications based on service agreements for localized services among network operators and application/service providers:
+
+- Hosting network operator owns the 5G network which provides access and IP connectivity to roaming UEs.
+- Network operator owned application layer entities include Service Hosting Environment, and IMS network.
+- Application platforms in third party domain can be owned by third party application/service providers, or home/other network operators.
+- The Application platforms could be application servers (e.g. Video on Demand Server, Cloud gaming server, etc.), 3rd party software development platforms, and third party/operator Service Hosting Environments.
+
+The following figures show the collaborative relationship in three domains including network operator providing access and IP connectivity, network operators providing services via IMS/application platforms, and application/service providers providing services via application platforms or applications. The dashed lines between visited hosting network operator and Home network operators are based on service level e-agreement and the horizontal line represents the demarcation between the network operator domains and the 3rd party domain. In an operator network, the application layer entities include IMS network, Application platforms, and API Gateway for third party applications developed using APIs (e.g. REST, GSMA OneAPI).
+
+Figure A-1 provides the home-routed roaming scenario for collaborative scenarios where traffic is routed to home network operator and applications are delivered by the home operator owned IMS or Application platform via roaming agreements between network operators.
+
+
+
+Figure A-1: Home Operator owned/collaborative roaming scenario – Home Routed. The diagram illustrates the flow of traffic and service interactions between a UE, a Hosting Network Operator, a Home Operator, and various external entities. The UE is connected to the Hosting Network Operator. The Hosting Network Operator is connected to the Home Operator via a dashed line. The Home Operator is connected to the Home Operator IMS and Home Operator Owned Application Platforms via solid lines. The Home Operator is also connected to the API Gateway via a solid line. The API Gateway is connected to the Internet/3rd Party Domain via a solid line. The Internet/3rd Party Domain contains Application#n and Application#1. The Home Operator is also connected to Other operators IMS and Other operators Application Platforms via dashed lines. The Other operators IMS and Other operators Application Platforms are connected to Application Platform#1 and Application Platform#n via dashed lines. The diagram is divided into two main domains: Home Operator Domain and Visited Operator Domain, separated by a vertical line. The Home Operator Domain includes the Home Operator, Home Operator IMS, Home Operator Owned Application Platforms, and API Gateway. The Visited Operator Domain includes the Hosting Network Operator and UE. The Internet/3rd Party Domain is shown above the Home Operator Domain.
+
+**Figure A-1: Home Operator owned/collaborative roaming scenario – Home Routed**
+
+Note: The other network operators and service/application operators in 3rd party domain provides collaborative services in application platforms to Home operator. The arrow solid line represents the traffic routed over trusted domains within home operator network while the arrow dash line represents the traffic routed over untrusted domain outside of home operator network.
+
+Figure A-2 provides the local breakout scenario for both owned and collaborative scenarios between visited hosting network operator and operators in 3rd party domains where traffic is routed to application from the hosting network to
+
+1) hosting network owned application platforms, 2) collaborative home network owned application platforms, and 3) third parties via roaming agreements between visited hosting network operator and home/other network operators, and between hosting network operators and other application/service providers.
+
+
+
+Figure A-2: Hosting Network Operator owned/collaborative roaming scenario – Local Breakout. The diagram illustrates a network architecture with three main domains: Internet/3rd Party Domain, Home Operator Domain, and Visited Operator Domain. A central 'Hosting Network Operator' (solid blue circle) is connected to a 'UE' (User Equipment) box. Solid blue arrows represent traffic routed over trusted domains within the hosting network, while dashed blue arrows represent traffic routed over untrusted domains outside the hosting operator network. In the Home Operator Domain, the 'Home Operator' (solid blue circle) is connected to 'Home Operator Owned Application Platforms' and 'Home Operator IMS' (dashed blue circles). In the Visited Operator Domain, the 'Hosting Network Operator' is connected to 'API Gateway', 'Hosting Network Operator Owned Application Platforms', and 'Hosting Network Operator IMS' (dashed blue circles). The 'API Gateway' is connected to 'Application#n' and 'Application#1' (dashed blue circles). In the Internet/3rd Party Domain, 'Other Operators IMS' and 'Other Operators Owned Application Platforms' (dashed blue circles) are connected to the 'Hosting Network Operator'. The 'Hosting Network Operator' is also connected to 'Application Platform#n' and 'Application Platform#1' (dashed blue circles).
+
+**Figure A-2: Hosting Network Operator owned/collaborative roaming scenario – Local Breakout**
+
+Note: The other network operators and application/service operators in 3rd party domain provides collaborative services in application platform to hosting network operator. The arrow solid lines represent the traffic routed over trusted domains within hosting network while the arrow dash lines represent the traffic routed over untrusted domain outside of hosting operator network.
+
+Other interworking scenarios are not excluded.
+
+# Annex B: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|------|-----|--------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New version |
+| 2020-11 | SA1#92e | S1-204336 | | | | TR skeleton | 0.0.0 |
+| 2020-11 | SA1#92e | S1-204349 | | | | TR post-SA192e | 0.1.0 |
+| 2021-03 | SA1#93e | S1-210315 | | | | TR post-SA193e | 0.2.0 |
+| 2021-05 | SA1#94e | S1-211311 | | | | TR post-SA194e | 0.3.0 |
+| 2021-06 | SA#92e | SP-210514 | | | | Raised by MCC to v.1.0.0 for one-step approval | 1.0.0 |
+| 2021-06 | SA#92e | SP-210514 | | | | Raised by MCC to v.18.0.0 following one-step approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210514 | | | | Corrected logo (5G->5GA) | 18.0.1 |
+| 2021-09 | SA#93e | SP-211047 | 0001 | 1 | F | FS_PALS Update: Chapter 5.6.6 Requirement for User Awareness | 18.1.0 |
+| 2021-09 | SA#93e | SP-211047 | 0002 | 1 | F | Miscellaneous corrections from pCR implementation | 18.1.0 |
+| 2021-09 | SA#93e | SP-211047 | 0003 | 5 | F | Updating PALS Consolidated Potential Requirements | 18.1.0 |
+| 2021-09 | SA#93e | SP-211047 | 0004 | | D | Removal of Editor's Note from Clause 5.10.5 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211047 | 0005 | 1 | F | Update of manual selection | 18.1.0 |
+| 2021-09 | SA#93e | SP-211047 | 0006 | 1 | F | Clarification of use case 5.15 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211047 | 0008 | 1 | F | FS_PALS TR Cleanup | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0009 | 1 | F | CPR# to PR# Mapping for PALS | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22847/09ab686699bb9597b8025e78fb390069_img.jpg b/marked/Rel-18/22_series/22847/09ab686699bb9597b8025e78fb390069_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71f3cc3c361f78b3d027651b31b0793b89cdddb0
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/09ab686699bb9597b8025e78fb390069_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:461ed7a6d4d96ec8d88c4e5d563de722df82121a6dd608b5f82dd33b6d18a6d3
+size 95035
diff --git a/marked/Rel-18/22_series/22847/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-18/22_series/22847/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..771446e594bf77d16a320071734d3ccad3834ab8
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:feed3c85b8a040571dc72489a0761c444fddfbe5199413f1b1e028b8e54602b9
+size 78913
diff --git a/marked/Rel-18/22_series/22847/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22847/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c08222255fc313aa621eb86964b5a8b302367f0
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d29bb9cb25f3e232fa3e588a1471970fc3086d500f80c4717863da395e8f4ab1
+size 9523
diff --git a/marked/Rel-18/22_series/22847/5fbb4f0de01736f1293333e599410c99_img.jpg b/marked/Rel-18/22_series/22847/5fbb4f0de01736f1293333e599410c99_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36d5d203568ef215953375b634368cd5c5dd6321
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/5fbb4f0de01736f1293333e599410c99_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97b05c40388e56db08ca484246df55f01eb327607629e8838112c2f08f8d4667
+size 60604
diff --git a/marked/Rel-18/22_series/22847/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22847/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d9a831acc2b6bf16bdb7b13658ec29e6ed45a018
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80bb8815976c75e9e9b7012aeb892e53362fd8382c3ff52d253730c52d5d483e
+size 5677
diff --git a/marked/Rel-18/22_series/22847/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/marked/Rel-18/22_series/22847/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9921b156306dfd82eac2c2689dfabe36d9bd8ee
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9554f403ec00eadfd169e536d9d1cd9f76ae8dc3131943a0415f87975472977
+size 30473
diff --git a/marked/Rel-18/22_series/22847/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg b/marked/Rel-18/22_series/22847/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13ea628fadeadf8bcbfe6e7b016dcc33245569fa
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:022496e97c7c378994c5f9a03afbef0f9adc9f62627ff779e4c3046b0c32ba9b
+size 34789
diff --git a/marked/Rel-18/22_series/22847/b3c108e7145f2017957569d06ea359cb_img.jpg b/marked/Rel-18/22_series/22847/b3c108e7145f2017957569d06ea359cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cef606cf4f07a4fc2eb56fe97ea981ef3d3e26c6
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/b3c108e7145f2017957569d06ea359cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45d3580a45c0525b85a003131d6b08bbf7d74518d9bf7640dcca45007360f9a1
+size 27014
diff --git a/marked/Rel-18/22_series/22847/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-18/22_series/22847/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04a66e517019df5ef19e4b12f9aff98b667247fe
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a0e91016f364c5f3b5bd0f93ec00ef188a76f58d31bda3d5b413eb888055323
+size 98359
diff --git a/marked/Rel-18/22_series/22847/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/22_series/22847/dd5771673aececa53d42ece89218299d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a49ebfdabfa6c20f11cebcbab9ea6fed9bba5da
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/dd5771673aececa53d42ece89218299d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ed5442c40f17b2cdd22cab2bd49d0db417efbcddfdc674571804774c7ab3361
+size 44656
diff --git a/marked/Rel-18/22_series/22847/eca7fa4eb8dd1303e4bd56aee6555b2d_img.jpg b/marked/Rel-18/22_series/22847/eca7fa4eb8dd1303e4bd56aee6555b2d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2101bba98549330f82f2bd3ce79284564cba55af
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/eca7fa4eb8dd1303e4bd56aee6555b2d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e739ee0a6437e542bdacfc10ff34039960cf1496dacf444ddac353e6852eff23
+size 57931
diff --git a/marked/Rel-18/22_series/22847/raw.md b/marked/Rel-18/22_series/22847/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..676d02b31c1127145f49830892666e1f80ddc8e6
--- /dev/null
+++ b/marked/Rel-18/22_series/22847/raw.md
@@ -0,0 +1,977 @@
+
+
+# 3GPP TR 22.847 V18.2.0 (2022-03) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on supporting tactile and multi-modality communication services; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green wave-like graphic above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G ADVANCED logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'P' has a red signal icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, sans-serif font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|--------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Symbols..... | 8 |
+| 3.3 Abbreviations ..... | 8 |
+| 4 Overview..... | 8 |
+| 4.1 Multi-modal service ..... | 8 |
+| 4.2 Multi-modal interactive system..... | 10 |
+| 5 Use case..... | 10 |
+| 5.1 Immersive multi-modal Virtual Reality (VR) application ..... | 10 |
+| 5.1.1 Description ..... | 10 |
+| 5.1.2 Pre-conditions..... | 11 |
+| 5.1.3 Service Flows ..... | 11 |
+| 5.1.4 Post-conditions ..... | 12 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 12 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 12 |
+| 5.2 Remote control robot..... | 14 |
+| 5.2.1 Description ..... | 14 |
+| 5.2.2 Pre-conditions..... | 14 |
+| 5.2.3 Service Flows ..... | 14 |
+| 5.2.4 Post-conditions ..... | 14 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 14 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.3 Immersive VR games..... | 15 |
+| 5.3.1 Description ..... | 15 |
+| 5.3.2 Pre-conditions..... | 16 |
+| 5.3.3 Service Flows ..... | 16 |
+| 5.3.4 Post-conditions ..... | 16 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 16 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 16 |
+| 5.4 Support of skillset sharing for cooperative perception and manoeuvring of robots ..... | 17 |
+| 5.4.1 Description ..... | 17 |
+| 5.4.2 Pre-conditions..... | 18 |
+| 5.4.3 Service Flows ..... | 18 |
+| 5.4.4 Post-conditions ..... | 19 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 19 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 19 |
+| 5.5 Haptic feedback for a personal exclusion zone in dangerous remote environments ..... | 20 |
+| 5.5.1 Description ..... | 20 |
+| 5.5.2 Pre-conditions..... | 21 |
+| 5.5.3 Service Flows ..... | 21 |
+| 5.5.4 Post-conditions ..... | 22 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 22 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 22 |
+| 5.6 Live Event Selective Immersion ..... | 24 |
+| 5.6.1 Description ..... | 24 |
+| 5.6.2 Pre-conditions..... | 24 |
+| 5.6.3 Service Flows ..... | 25 |
+| 5.6.4 Post-conditions ..... | 25 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 25 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 26 |
+| 5.7 Support for IEEE P1918.1 architecture ..... | 26 |
+
+| | | |
+|-------|-----------------------------------------------------------------------------|----|
+| 5.7.2 | Pre-conditions ..... | 27 |
+| 5.7.3 | Service Flows ..... | 28 |
+| 5.7.4 | Post-conditions ..... | 28 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 28 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 28 |
+| 5.8 | Virtual factory ..... | 29 |
+| 5.8.1 | Description ..... | 29 |
+| 5.8.2 | Pre-conditions ..... | 30 |
+| 5.8.3 | Service Flows ..... | 30 |
+| 5.8.4 | Post-conditions ..... | 31 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 31 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 31 |
+| 6 | Consolidated requirements..... | 31 |
+| 6.1 | Consolidated potential requirements..... | 31 |
+| 6.2 | Consolidated potential KPIs..... | 31 |
+| 7 | Conclusions and recommendations..... | 34 |
+| | Annex A: Change history..... | 35 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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 present document provides stage 1 use cases and potential 5G requirements on supporting tactile and multi-modal communication services. In the context of the present document, the aspects addressed include:
+
+- 1) Study new scenarios and identify use cases and potential requirements for immersive real time experience involving tactile and multi-modal interactions, including:
+ - a) Network assistance for coordinated transmission of multiple modal representations associated with the same session,
+ - b) aspects of charging, security and privacy, and
+ - c) KPIs (including network reliability and availability).
+- 2) Gap analysis with existing requirements and functionalities on supporting tactile and multi-modal communication services.
+
+# --- 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] ITU-T, "Technology Watch Report: The Tactile Internet", August 2014.
+- [3] O. Holland et al., "The IEEE 1918.1 "Tactile Internet" Standards Working Group and its Standards," *Proceedings of the IEEE*, vol. 107, no. 2, Feb. 2019.
+- [4] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications".
+- [5] S. K. Sharma, I. Woungang, A. Anpalagan and S. Chatzinotas, "Toward Tactile Internet in Beyond 5G Era: Recent Advances, Current Issues, and Future Directions," in *IEEE Access*, vol. 8, pp. 56948-56991, 2020
+- [6] 3GPP TS 22.261: "Service requirements for the 5G system".
+- [7] Kwang Soon Kim, et al., "Ultrareliable and Low-Latency Communication Techniques for Tactile Internet Services", *PROCEEDINGS OF THE IEEE*, Vol. 107, No. 2, February 2019
+- [8] SAE Manoeuvre Sharing and Coordinating Service Task Force, .
+- [9] SAE Sensor-Sharing Task Force, .
+- [10] M. During and K. Lemmer, "Cooperative manoeuver planning for cooperative driving," *IEEE Intell. Transp. Syst. Mag.*, vol. 8, no. 3, pp. 8–22, Jul. 2016.
+- [11] D. Soldani, Y. Guo, B. Barani, P. Mogensen, I. Chih-Lin, S. Das, "5G for ultra-reliable low-latency communications". *IEEE Network*. 2018 Apr 2; 32(2):6-7.
+
+- [12] Void.
+- [13] IEEE SA, "P1918.1 - Tactile Internet: Application Scenarios, Definitions and Terminology, Architecture, Functions, and Technical Assumptions", [https://standards.ieee.org/project/1918\\_1.html](https://standards.ieee.org/project/1918_1.html)
+- [14] M. Eid, J. Cha, and A. El Saddik, "Admux: An adaptive multiplexer for haptic-audio-visual data communication", IEEE Tran. Instrument. and Measurement, vol. 60, pp. 21–31, Jan 2011.
+- [15] K. Iwata, Y. Ishibashi, N. Fukushima, and S. Sugawara, "QoE assessment in haptic media, sound, and video transmission: Effect of playout buffering control", Comput. Entertain., vol. 8, pp. 12:1–12:14, Dec 2010.
+- [16] N. Suzuki and S. Katsura, "Evaluation of QoS in haptic communication based on bilateral control", in IEEE Int. Conf. on Mechatronics (ICM), Feb 2013, pp. 886–891.
+- [17] E. Isomura, S. Tasaka, and T. Nunome, "A multidimensional QoE monitoring system for audiovisual and haptic interactive IP communications", in IEEE Consumer Communications and Networking Conference (CCNC), Jan 2013, pp. 196–202.
+- [18] A. Hamam and A. El Saddik, "Toward a mathematical model for quality of experience evaluation of haptic applications", IEEE Tran. Instrument. and Measurement, vol. 62, pp. 3315–3322, Dec 2013.
+- [19] M. Back et al., "The virtual factory: Exploring 3D worlds as industrial collaboration and control environments," 2010 IEEE Virtual Reality Conference (VR), 2010, pp. 257-258
+- [20] S. Schulte, D. Schuller, R. Steinmetz and S. Abels, "Plug-and-Play Virtual Factories," in IEEE Internet Computing, vol. 16, no. 5, pp. 78-82, Sept.-Oct. 2012
+- [21] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains"
+- [22] Altinsoy, M. E., Blauert, J., & Treier, C., "Inter-Modal Effects of Non-Simultaneous Stimulus Presentation," A. Alippi (Ed.), Proceedings of the 7th International Congress on Acoustics, Rome, Italy, 2001.
+- [23] Hirsh I.J., and Sherrick C.E, 1961. J. Exp. Psychol 62, 423-432
+- [24] Altinsoy, M.E. (2012). "The Quality of Auditory-Tactile Virtual Environments," Journal of the Audio Engineering Society, Vol. 60, No. 1/2, pp. 38-46, Jan.-Feb. 2012.
+- [25] M. Di Luca and A. Mahnan, "Perceptual Limits of Visual-Haptic Simultaneity in Virtual Reality Interactions," 2019 IEEE World Haptics Conference (WHC), 2019, pp. 67-72, doi: 10.1109/WHC.2019.8816173.
+- [26] Arnon, Shlomi, et al. "A comparative study of wireless communication network configurations for medical applications." IEEE Wireless Communications 10.1 (2003): page 56-61.
+- [27] K. Antonakoglou et al., "Toward Haptic Communications Over the 5G Tactile Internet", IEEE Communications Surveys & Tutorials, 20 (4), 2018.
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**end-to-end latency:** the time that takes to transfer a given piece of information from a source to a destination, measured at the communication interface, from the moment it is transmitted by the source to the moment it is successfully received at the destination.
+
+NOTE 1: This definition was taken from TS 22.261 [6].
+
+**Multi-modal Data:** Multi-modal Data is defined to describe the input data from different kinds of devices/sensors or the output data to different kinds of destinations (e.g. one or more UEs) required for the same task or application. Multi-modal Data consists of more than one Single-modal Data, and there is strong dependency among each Single-modal Data. Single-modal Data can be seen as one type of data.
+
+**reliability:** in the context of network layer packet transmissions, percentage value of the amount of sent network layer packets successfully delivered to a given system entity within the time constraint required by the targeted service, divided by the total number of sent network layer packets.
+
+NOTE 2: This definition was taken from TS 22.261 [6].
+
+**service area:** geographic region where a 3GPP communication service is accessible.
+
+NOTE 3: The service area can be indoors.
+
+NOTE 4: For some deployments, e.g., in process industry, the vertical dimension of the service area can be considerable.
+
+NOTE 5: This definition was taken from TS 22.261 [6].
+
+**synchronisation threshold:** A multi-modal synchronisation threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one of which is presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous.
+
+NOTE 6: This definition is based on [22].
+
+**Tactile Internet:** A network (or network of networks) for remotely accessing, perceiving, manipulating, or controlling real or virtual objects or processes in perceived real time by humans or machines.
+
+NOTE 7: This definition is based on IEEE P1918.1 [3].
+
+**user experienced data rate:** the minimum data rate required to achieve a sufficient quality experience, with the exception of scenario for broadcast like services where the given value is the maximum that is needed.
+
+NOTE 8: This definition was taken from TS 22.261 [6].
+
+## 3.2 Symbols
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|-----|--------------------|
+| DoF | Degrees of Freedom |
+|-----|--------------------|
+
+# --- 4 Overview
+
+## 4.1 Multi-modal service
+
+Tactile and multi-modal communication services enable multi-modal interactions, combining ultra-low latency with extremely high availability, reliability and security. Tactile Internet can be applied in multiple fields, including: industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road traffic, serious gaming, education and culture, smart grid, etc. [2]. Multiple modalities can be used in combination in a service to provide
+
+complementary methods that may convey redundant information but can convey information more effectively. With the benefit of combining input from more than one source and/or output to more than one destination, interpretation in communication services will be more accurate and faster, response can also be quicker, and the communication service will be smoother and more natural.
+
+For a typical tactile and multi-modal communication service/application, there can be different modalities affecting the user experience, e.g.:
+
+- Video/Audio media;
+- Information perceived by sensors about the environment, e.g. brightness, temperature, humidity, etc.;
+- Haptic data: can be feelings when touching a surface (e.g., pressure, texture, vibration, temperature), or kinaesthetic senses (e.g. gravity, pull forces, sense of position awareness).
+
+The ambient information may be further processed to generate IoT control instructions as the feedback. The haptic data, according to the physiological perception, has specific characteristics, e.g. frequency and latency, and may require adequate periodic, deterministic and reliable communication path. For example, the sampling rate of the haptic device for teleoperation systems may reach 1000 times per second and samples are typically transmitted individually hence 1000 packets per second, while the video is 60/90 frames per second. The high frequency transmission of small packets over a long distance would be a great challenge for 5G system.
+
+Multiple modalities can be transmitted at the same time to multiple application servers for further processing in a coordinated manner, in terms of QoS coordination, traffic synchronization, power saving, etc.
+
+- Multiple outcomes may be generated as the feedback. In the scenario of real time remote virtual reality service, a VR user may use a plurality of independent devices to separately collect video, audio, ambient and haptic data from the person and to receive video, audio, ambient and haptic feedback from one or multiple application servers for a same VR application. In this case, an end user could wear VR glasses to receive images and sounds, and a touch glove to receive a touch sensation, a camera to collect video inputs, a microphone to collect audio inputs, multiple wearable sensors to provide haptic information and environmental information associated to the user. The real time remote virtual reality service can also be conducted between two users.
+- Multiple outcomes may need to reach the distributed UEs at the very same time. In the scenario of sound field reappearing, different channels of sounds are sent to the distributed sound boxes to simulate the sound from a particular direction. A small time difference may cause big direction error to impact user experience. In some cases, time difference of 1ms may cause more than 30° angle error.
+- Multi-modal applications may involve a big number of UEs at a long distance. In the scenario of multi-modal telepresence, tens of UEs may need synchronization for time, control signal and visual signal.
+
+In another scenario, the devices associated to the same tactile and multi-modal communication service may be triggered to wake up by the discovery of a tactile and multi-modality capable user/UE in proximity. And a different group of tactile and multi-modality capable devices can serve the user as he moves.
+
+Other scenarios that can be investigated are industrial manufacturing and drones real-time applications, which require synchronous control of visual-haptic feedback.
+
+## 4.2 Multi-modal interactive system
+
+
+
+The diagram illustrates a multi-modal interactive system. On the left, an 'ambiguous perception/instructor' (represented by a human icon) provides 'Information from the user' and 'Information from ambient' sources. These inputs feed into a central 'Multi-modality input' block. This block contains several sub-components: 'Biometric from voice', 'Words from voice', 'Emotion from voice', 'Biometric from face', 'Emotion from face', 'Lips movements', 'Emotion from wearables', 'Gesture', 'Relative Location', 'Ambient information', and 'Haptic information from wearable'. Above this block are icons for a microphone, camera, face, wearables, and a location pin. To the right, three service blocks are shown: 'Service 1 Biometric recognition' (orange), 'Service 2 Intention perception' (green, with sub-points: Multi-modality NLP, Multi-modality emotion, Multi-modality haptic), and 'Service 3 Service presence' (grey, with sub-points: Audio/video service, IoT control). Arrows indicate data flow from the input block to these services. Below the input block, a 'Multi-modality output' block (blue) includes 'Haptic feedback', 'Brightness', 'Sensible temperature', 'Video', and 'Audio'. Arrows point from the services back to this output block, which then feeds back into the 'ambiguous perception/instructor' via icons representing a hand, light, temperature, video, and audio.
+
+Diagram of a Multi-modal interactive system showing input sources, processing blocks, and output modalities.
+
+Figure 4.2-1. Multi-modal interactive system
+
+As shown in figure 4.2-1, multi-modal outputs are generated based on the inputs from multiple sources. In the multi-modal interactive system, modality is a type or representation of information in a specific interactive system. Multi-modal interaction is the process during which information of multiple modalities are exchanged. Modal types consists of motion, sentiment, gesture, etc. Modal representations consists of video, audio, tactition (vibrations or other movements which provide haptic or tactile feelings to a person), etc.
+
+# 5 Use case
+
+## 5.1 Immersive multi-modal Virtual Reality (VR) application
+
+### 5.1.1 Description
+
+Immersive multi-modal VR application describes the case of a human interacting with virtual entities in a remote environment such that the perception of interaction with a real physical world is achieved. Users are supposed to perceive multiple senses (vision, sound, touch) for full immersion in the virtual environment. The degree of immersion achieved indicates how real the created virtual environment is. Even a tiny error in the preparation of the remote environment might be noticed, as humans are quite sensitive when using immersive multi-modal VR applications. Therefore, a high-field virtual environment (high-resolution images and 3-D stereo audio) is essential to achieve an ultimately immersive experience.
+
+One of the major objectives of VR designers and researchers is to obtain more realistic and compelling virtual environments. As the asynchrony between different modalities increases, users' sense of presence and realism will decrease. There have been efforts (since 1960s or even earlier) in multi-modal-interaction research regarding the detection of synchronisation thresholds. The obtained results vary, depending on the kind of stimuli and the psychometric methods employed. Hirsh and Sherrick measured the synchronisation thresholds regarding visual, auditory and tactile modalities [23].
+
+| Hirsh & Sherrick | | |
+|-----------------------------|--------------|---------------|
+| audio visual | audio delay | visual delay |
+| | 20 ms | 20 ms |
+| audio-tactile | audio delay | tactile delay |
+| | 25 ms | 12 ms |
+| visual-tactile | visual delay | tactile delay |
+| | 20 ms | 30 ms |
+
+**Figure 5.1.1-1 The synchronisation thresholds regarding visual, auditory and tactile modalities measured by Hirsh and Sherrick**
+
+M.E. Altinsoy and co. believe the audio-tactile synchronization has to be at least within an accuracy of $\pm 40$ ms [22]. More results have been reported based on extensive theoretical and experimental efforts. [24] further indicated the perceptual threshold values were 50 ms for the audio lag and the 25 ms for audio lead.
+
+As to the visual-tactile synchronisation threshold, Massimiliano Di Luca and Arash Mahnan provided test results in [25] that indicate that none of the participants could reliably detect the asynchrony if haptic feedback was presented less than 50ms after the view of the contact with an object. The asynchrony tolerated for haptic before visual feedback was instead only 15ms.
+
+### 5.1.2 Pre-conditions
+
+The devices for immersive multi-modal VR application may include multiple types of devices such as VR glass type device, the gloves and other potential devices that support haptic and/or kinaesthetic modal. These devices which are 5G UEs are connected to the immersive multi-modal VR application server via the 5G network without any UE relays, see Figure 5.1.2-1.
+
+NOTE: The devices that are connected to VR application via the 5G network are assumed to be 3GPP UEs.
+
+Based on the service agreement between MNO and immersive multi-modal VR application operator, the application operator may in advance provide the 5G network with the application information including the application traffic characteristics and the service requirement for network connection. For example, the packet size for haptic data is related to the Degrees Of Freedom (DoF) that the haptic devices supports, and packet size for one DoF is 2-8 Bytes [3] and the haptic device generates and sends 500 haptic packets within one second.
+
+
+
+Diagram showing immersive multi-modal VR application with multiple 5G UEs directly connected to 5G network. On the left, there are icons for '5G UE (VR glasses)' and '5G UE (gloves)'. Arrows labeled 'Service data flows' point from these UEs through a '5G network' icon (a radio tower) to an 'Application Server' box on the right.
+
+**Figure 5.1.2-1. Immersive multi-modal VR application with multiple 5G UEs directly connected to 5G network**
+
+### 5.1.3 Service Flows
+
+1. The application user utilizes the devices to experience immersive multi-modal VR application. The user powers on the devices to connect to the application server, then the user starts the gaming application.
+2. During the gaming running period, the devices periodically send the sensing information to the application server, including: haptic and/or kinesthetic feedback signal information which is generated by haptic device, and the sensing information such as positioning and view information which is generated by the VR glasses.
+
+- NOTE 1: The devices may send the haptic data and the sensing data with different periodic time. As an example, the device may send one packet containing haptic information to the application server every 2ms, and send the packets related to sensing information to application server every 4ms. Thus the haptic data and sensing data may be transferred in 5G network via two separate flows. The amount of haptic packets that are generated and transferred within one second may be 1K - 4K packets (without haptic compression encoding), or 100-500 packets (with haptic compression encoding). As indicated in IEEE 1918.1 [3], the size of each haptic packet is related to the DoF capacity that haptic device supports, the data size for one DoF is 2-8 Byte.
+3. According to the uplink data from the devices, the application server performs necessary process operations on immersive game reality including rendering and coding the video, the audio and haptic model data, then application server periodically sends the downlink data to the devices, with different time periods respectively, via 5G network.
+- NOTE 2: The application server may also send the haptic data and the video/audio data with different periodic time. For example, the application server sends one packet containing haptic information to the device every 2ms, and it sends the packets related to one video/audio frame to the device every 16.7ms in case 60 Frame Per Second which forms one burst traffic that goes on 3ms. Thus the haptic data and audio/video data may be transferred via two separate service data flows of a single session.
+4. The devices, respectively, receive the data from the application server and present the related sensing including video, audio and haptic to the user.
+- NOTE 3: To obtain more realistic and compelling virtual environments, network assistance may be needed to ensure synchronisation thresholds between different modal data thus improve the end users' sense of presence and realism.
+
+### 5.1.4 Post-conditions
+
+The user experiences the immersive game reality application enabled by 5G network, and the 5G system address the service requirements of the application.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [6] specifies KPIs for high data rate and low latency interactive services including Cloud/Edge/Split Rendering, Gaming or Interactive Data Exchanging, Consumption of VR content via tethered VR headset, and audio-video synchronization thresholds.
+
+Support of audio-video synchronisation thresholds has been captured in TS 22.261:
+
+*Due to the separate handling of the audio and video component, the 5G system will have to cater for the VR audio-video synchronisation in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization). To support VR environments, the 5G system shall support audio-video synchronisation thresholds:*
+
+- *in the range of [125 ms to 5 ms] for audio delayed and*
+- *in the range of [45 ms to 5 ms] for audio advanced.*
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.1.6-1] The 5G System shall provide the network connection to address the KPIs for immersive multi-modal VR applications, see table 5.1.6-1.
+
+**Table 5.1.6-1 – Potential key performance requirements for immersive multi-modal VR applications**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | | Remarks |
+|-----------------------------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------|--------------------------|------------------------------------------|-----------------------------------------------------------------------------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | # of UEs | UE Speed | Service Area | |
+| Immersive multi-modal VR (UL: device → application sever) | 5 ms (note 2) | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | [99.9%] (without haptic compression encoding)
[99.999%] (with haptic compression encoding) | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
More DoFs can be supported by the haptic device | - | Stationary or Pedestrian | typically < 100 km 2 (note 3) | Haptic feedback |
+| | 5 ms | < 1Mbit/s | [99.99%] | MTU | - | Stationary or Pedestrian | typically < 100 km 2 (note 3) | Sensor information e.g. position and view information generated by the VR glasses |
+| Immersive multi-modal VR (DL: application sever → device) | 10 ms (note1) | 1-100 Mbit/s | [99.9%] | 1500 | - | Stationary or Pedestrian | typically < 100 km 2 (note 3) | Video |
+| | 10 ms | 5-512 kbit/s | [99.9%] | 50 | - | Stationary or Pedestrian | typically < 100 km 2 (note 3) | Audio |
+| | 5 ms (note 2) | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | [99.9%] (without haptic compression encoding)
[99.999%] (with haptic compression encoding) | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | - | Stationary or Pedestrian | typically < 100 km 2 (note 3) | Haptic feedback |
+
+NOTE 1: Motion-to-photon delay (the time difference between the user's motion and corresponding change of the video image on display) is less than 20 ms, the communication latency for transferring the packets of one audio-visual media is less than 10 ms, e.g. the packets corresponding to one video/audio frame are transferred to the devices within 10 ms.
+
+NOTE 2: According to IEEE 1918.1 [3] as for haptic feedback, the latency is less than 25 ms for accurately completing haptic operations. As rendering and hardware introduce some delay, the communication delay for haptic modality can be reasonably less than 5 ms, i.e. the packets related to one haptic feedback are transferred to the devices within 10 ms.
+
+NOTE 3: In practice, the service area depends on the actual deployment. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
+
+[PR 5.1.6-2] Due to the separate handling of the multiple media components, synchronization between different media components is critical in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization). Applying synchronization thresholds in the 5G system may be helpful in support of immersive multi-modal VR applications when the synchronization threshold between two or more modalities is less than the latency KPI for the application. Typical synchronization thresholds (see [22], [23], [24] and [25]) are summarised in table 5.1.6-2.
+
+**Table 5.1.6-2: Typical synchronization thresholds for immersive multi-modal VR applications**
+
+| | synchronization threshold (note 1) | |
+|---------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------|
+| audio-tactile | audio delay:
50 ms | tactile delay:
25 ms |
+| visual-tactile | visual delay:
15 ms | tactile delay:
50 ms |
+| NOTE 1: For each media component, "delay" refers to the case where that media component is delayed compared to the other. | | |
+
+[PR 5.1.6-3] The 5G network shall support a mechanism to allow an authorized 3rd party to provide QoS policy for multiple flows (e.g., haptic, audio and video) of multiple UEs associated with a multi-modal application. The policy may contain e.g. coordination information.
+
+[PR 5.1.6-4] The 5G system shall support a mechanism to apply 3rd party provided policy for flows associated with an application. The policy may contain e.g. coordination information.
+
+NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs' flows (e.g., haptic, audio and video) of a multi-modal communication session.
+
+## 5.2 Remote control robot
+
+### 5.2.1 Description
+
+Human can use Remote control robot to operate some actions which they are not able to be on the spot. With real-time and synchronous visual, audio and haptic feedback, remote robot operator will perform reactions suitable for the situation, and remote control robot can follow operator's action to do the exact work. This can be used in many different scenarios. It can be applied to remote care for elderly, remote detonation, remote operation, remote maintenance of facility, remote firefighting, etc.
+
+### 5.2.2 Pre-conditions
+
+Alice is the operator of a remote robot for maintaining underground pipe. She has a sticker which has the same DoF and structure with the maintain tool on the remote robot. Both Alice and robot is connected to a 5G network with the ability to transfer video, audio and haptic information.
+
+### 5.2.3 Service Flows
+
+1. Remote robot is at the spot of a damaged underground pipe, using integrated camera and sensor to send back video, audio and haptic information.
+2. Alice hold the control stick and can receive the haptic information, and receive the video, audio information synchronous on the screen and from the sound.
+3. After analysing these information, Alice perform the next move on the operator sticker.
+4. The haptic information including force and DoF transfer to remote robot, and the robot performs the same action.
+
+### 5.2.4 Post-conditions
+
+Alice can remotely control the robot to finish the maintaining work.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+In 3GPP TS 22.263 [4], there are requirements for supporting video, imaging and audio for professional applications.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.2.6-1] The 5G system shall be able to support tactile and multi-modal communication service with following KPIs.
+
+**Table 5.2.6-2: Potential Key performance requirements for remote control robot [3]**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | | Remarks |
+|----------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|---------------------|----------|--------------------------------|--------------------------|--------------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | # of UEs | UE Speed | Service Area[21] | |
+| Remote control robot | 1-20ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.99% | 2-8/DoF | - | high-dynamic ( $\leq 50$ km/h) | $\leq 1$ km 2 | Haptic feedback |
+| | 20-100ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.99% | 2-8/DoF | - | Stationary or Pedestrian | $\leq 1$ km 2 | Haptic feedback |
+| | 5 ms | 1-100 Mbit/s | 99.9% | 1500 | - | Stationary or Pedestrian | $\leq 1$ km 2 | Video |
+| | 5 ms | 5-512 kbit/s | 99.9% | 50-100 | - | Stationary or Pedestrian | $\leq 1$ km 2 | Audio |
+| | 5 ms | < 1Mbit/s | 99.999% | - | - | Stationary or Pedestrian | $\leq 1$ km 2 | Sensor information |
+
+[PR 5.2.6-2] The 5G system shall support a mechanism to allow an authorized 3rd party to provide QoS policy for flows of multiple UEs associated with an application. The policy may contain e.g. the expected 5GS handling and the associated triggering event.
+
+## 5.3 Immersive VR games
+
+### 5.3.1 Description
+
+This use case is about supporting immersive VR games with tactile and multi-modal communication services. VR games have provided a better experience comparing to traditional games. As customers ask for more immersive game experience, haptic information has been taken into account including force and DOF. Traditional VR games provide video and audio information for players to create the real game scenarios. For better immersive VR games, haptic feedback is introduced and which provides the reality of touching things in games as well as the interaction of team players.
+
+To play the VR game, players buy VR games and related equipment like VR glasses, hand shank, analogue steering wheel and haptic gloves, which may be produced by different manufactures. In multi-player VR games, they act as
+
+different UEs and need to cooperate to complete the mission. On application level, the VR gaming application will be able to distinguish these UEs and share the information with network that these UEs and data flows are grouping under this VR gaming service, and network need to provide corresponding QoS accordingly.
+
+For smooth experience in VR, the motion-to-photon latency should be less than 20ms [7], which indicates that the latency between player do one movement and the corresponding new pixels show in VR sights should be less than 20ms. The uplink dataflow in this loop is motion or haptic information, while the downlink in this loop is the video data. The QoS requirements for these two types of data flows are different, which includes latency requirements. But for the service level, it requires the joint latency consist both uplink and downlink. [5]
+
+### 5.3.2 Pre-conditions
+
+Alice and Bob are playing a VR game together. They need to cover each other's back, find weapons and fight with zombies. The VR gaming equipment they wear are all connected to 5G network. The VR game application interacted with 5G network about the UE and dataflow information, and network provides the pre-agreed policy between application and operator on QoS requirements of each kind of modal data flow.
+
+### 5.3.3 Service Flows
+
+1. Alice and Bob both joined this VR games, and they can see each other's character in the view.
+2. Alice found two stones on the ground, she picks up both the stones. The delay between the real pick-up action and the virtual hand pick-up video is ignorable.
+3. Bob has nothing to arm himself. So he asks Alice to throw him a stone.
+4. Alice heard Bob and throws one of the stone to Bob.
+5. Bob catches the stone can feel the weight of the stone.
+
+### 5.3.4 Post-conditions
+
+Alice and Bob can feel the things in the game as they are in the real world. The experience of this VR games is very realistic and smooth.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+In TS 22.261 [6], there are performance requirements for supporting VR services.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR 5.3.6-1] The 5G system shall be able to support tactile and multi-modal communication service with following KPIs.
+
+**Table 5.3.6-1: Potential Key performance requirements for immersive VR games**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | | Remarks |
+|--------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|---------------------|----------|--------------------------|---------------------------------|-----------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | # of UEs | UE Speed | Service Area | |
+| Immersive multi-modal VR | [10-20 ms] | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | [99.99%] | 2-8/DoF | - | Stationary or Pedestrian | typically < 100 km 2 | Haptic feedback |
+| | | 1-100 Mbit/s | [99.999%] | [1-10000] | - | Stationary or Pedestrian | typically < 100 km 2 | Video |
+| | | 5-512 kbit/s | [99.9%] | [50-100] | - | Stationary or Pedestrian | typically < 100 km 2 | Audio |
+
+[PR 5.3.6-2] The 5G system shall support a mechanism to allow an authorized 3rd party to provide QoS policy for coordination between flows of multiple UEs associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected 5GS QoS handling(s) and associated triggering events, expected coordination assistance provided by 5G system between those multiple flows for different traffic types (e.g., haptic, audio and video).
+
+[PR 5.3.6-3] The 5G system shall enable means to meet a synchronization threshold for flows of multiple UEs associated with an application based on input received from an authorized 3rd party.
+
+[PR 5.3.6-4] Due to the separate handling of the multiple media components, synchronization between different media components is critical in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization). Applying synchronization thresholds in the 5G system may be helpful in support of immersive multi-modal VR applications when the synchronization threshold between two or more modalities is less than the latency KPI for the application. Typical synchronization thresholds (see [22], [23], [24] and [25]) are summarised in table 5.3.6-2.
+
+**Table 5.3.6-2: Typical synchronization thresholds for immersive VR games**
+
+| | synchronization threshold (note 1) | |
+|---------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------|
+| audio-tactile | audio delay:
50 ms | tactile delay:
25 ms |
+| visual-tactile | visual delay:
15 ms | tactile delay:
50 ms |
+| NOTE 1: For each media component, "delay" refers to the case where that media component is delayed compared to the other. | | |
+
+## 5.4 Support of skillset sharing for cooperative perception and manoeuvring of robots
+
+### 5.4.1 Description
+
+Today, most automated driving vehicles rely on a single controller, which is the vehicle itself: sensing and controlling features of its own [3]. Since 3GPP Rel-14, LTE-based support for V2V features have been developed and tested through collaborative participation from automotive and communication industry. However, it is still challenging to use
+
+automated driving functionalities in general unstructured settings, if the controlling features are based on a single controller, having no idea on how neighbouring vehicles will behave.
+
+This consequently requires that the automated driving system should allocate an extra safety margin into the planned trajectory which in turn causes traffic flow to be reduced and causes inefficiency to happen in a large scale network of vehicle networks where non-V2X vehicles and V2X-enabled vehicles possibly coexist. This is not even a problem for such an automated driving of road vehicles – the same applies to the operations of “automated manoeuvring robots” in unstructured settings. Without cooperation, the field of perception of a vehicle/robots is limited to the local coverage of the onboard sensors – not only for the relative distance, relative angle.
+
+As a technology enabler solution against such problems of guaranteeing safety and traffic efficiency, it is being studied to share the sensor information [9] and manoeuver sharing [8] in SAE. Tactile Internet for V2N (potentially with assistance from edge cloud instead of general cloud servers) or V2V can enable an ultra-fast and reliable exchange of highly detailed sensor data sets between nearby vehicles, along with haptic information on trajectory [3]. Also, it would be one of the key factors for so-called “cooperative perception and manoeuvring” functionalities [10]: planning cooperative manoeuvres among multiple automated driving vehicle (or robots), such as plan creation, target point generation and target point risk assessment. It is by the Tactile Internet connectivity that vehicles can perform a cooperative perception of the driving environment based on fast fusion of high definition local and remote maps collected by the onboard sensors of the surrounding vehicles (e.g., video streaming from camera, radar, or lidar). This allows to augment the sensing range of each vehicle and to extend the time horizon for situation prediction, with huge benefits for safety [3]. The onboard sensors in today automated driving vehicles generate data flows up to 8 Gbit/s [3]. All these requirements call for new network architectures interconnecting vehicles and infrastructure utilizing ultralow-latency networks based on the Tactile Internet for cooperative driving services [3].
+
+This use case is related to the support of (1) cooperative perception and manoeuvring and (2) extension of sensing range for cooperative automated driving scenarios using Tactile Internet, with some examples of moving robots (e.g., local delivery robots). Manoeuvring and perception obtained via haptic and multi-modal communications (also known as skillset sharing) are very timely shared between the controller and controllee.
+
+### 5.4.2 Pre-conditions
+
+Four robots S1, S2, C1 and C2 are working on delivery tasks from a geographic point to another, respectively.
+
+Robots UEs S1 and S2 are automated driving robots with a standalone steer/control, manoeuvring in a crowded village.
+
+Robots UEs C1 and C2 are automated driving robots with steer/control and manoeuver/skillset sharing functionalities, manoeuvring in another crowded village.
+
+The roads that robots are using in these villages are not structured road (i.e., no lane separator, no lane marks, etc.) and they are under the same conditions for robots to move.
+
+### 5.4.3 Service Flows
+
+1. S1 is moving at speed of X and is getting close to S2.
+ - a) S1 does not know exactly what trajectory S2 is planning to move along. Therefore, S1 reduces the current moving speed to $(0.5 * X)$ .
+ - b) During the operation at this reduced speed, S1 still does not know the detailed trajectory of S2. Therefore, S1 reserves a distance of Y1 meters relative to S2 and gets ready to further reduce the speed or to make a full stop, monitoring the movement of S2.
+ - c) S1 and S2 pass each other and continue their trip to the destinations, respectively.
+2. C1 is moving at speed of X and is getting close to C2.
+ - a) C1 knows exactly what trajectory C2 is planning to move along as they share the manoeuvres. Therefore, C1 reduces the current moving speed to $(0.9 * X)$ .
+ - b) During the operation at this reduced speed, C1 still knows the detailed trajectory of C2 through manoeuver sharing. Therefore, C1 reserves a distance of Y2 ( $Y2 \ll Y1$ ) meters relative to C2 and gets ready to further reduce the speed to avoid any change of collision but there is very little chance that both should make a full stop as both are sharing the steer/control: one can yield the space for the other only when necessary.
+
+- c) C1 and C2 pass each other and continue their trip to the destinations, respectively.
+
+### 5.4.4 Post-conditions
+
+The total time that S1 and S2 should spend is much greater than the total time that C1 and C2 should spend.
+
+The total energy consumption (e.g., to accelerate from a low speed level to X) for S1 and S2 is greater than that for C1 and C2.
+
+Fig. 5.4.4-1 provides a simplified explanation on the behaviours of speed changes for examples without (left section) and with (right section) real-time multi-modal communication for interactive haptic control and feedback (skillset sharing).
+
+
+
+The figure consists of two side-by-side sections, left and right, each showing a top-down view of two robots on a road and two corresponding graphs below.
+
+- Left Section (Without Communication):**
+ - Top View:** Shows two robots, S1 and S2, on a road. S1 is on the left, S2 is on the right. Four reference points P1, P2, P3, and P4 are marked with vertical dashed lines.
+ - Speed Graph:** The y-axis is labeled 'speed' and has values X and 0.5X. The x-axis is labeled 'displacement (w.r.t. the reference points of vehicles/robots)'. The speed curve starts at X, remains constant until P2, then drops linearly to 0.5X at P3, remains constant at 0.5X until P4, and then rises linearly back to X.
+ - Minimum Margin Graph:** The y-axis is labeled 'min. margin b/w vehicles' and has a value Y1. The x-axis is the same as the speed graph. The margin curve is a red U-shaped curve that starts high, decreases to a minimum between P3 and P4, and then increases. A horizontal purple line is drawn at Y1.
+- Right Section (With Communication):**
+ - Top View:** Shows two robots, C1 and C2, on a road. C1 is on the left, C2 is on the right. Four reference points P1, P2, P3, and P4 are marked with vertical dashed lines.
+ - Speed Graph:** The y-axis has values X and 0.9X. The x-axis is the same as the speed graph. The speed curve starts at X, remains constant until P2, then drops slightly to 0.9X at P3, remains constant at 0.9X until P4, and then rises linearly back to X.
+ - Minimum Margin Graph:** The y-axis has a value Y2. The x-axis is the same as the speed graph. The margin curve is a red U-shaped curve that starts high, decreases to a minimum between P3 and P4, and then increases. A horizontal purple line is drawn at Y2.
+
+Figure 5.4.4-1: Simplified examples on the stochastic behaviours of the speed change (and the minimum margin to set between robots (or vehicle-styled robots)) without (left section) and with (right section) real-time multi-modal communication for interactive haptic control and feedback (skillset sharing).
+
+**Fig. 5.4.4-1. Simplified examples on the stochastic behaviours of the speed change (and the minimum margin to set between robots (or vehicle-styled robots)) without (left section) and with (right section) real-time multi-modal communication for interactive haptic control and feedback (skillset sharing). The road is assumed to be in general unstructured setting, e.g., no lane separator or marks.**
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+V2X performance requirements found in TS 22.185, TS 22.186. (e)CAV requirements in TS 22.104 [21]. VIAPA requirements in TS 22.263 [4]
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+[PR 5.4.6-1] 5G system shall be able to support real-time multi-modal communication for interactive haptic control and feedback with KPIs as summarized in Table 5.4.6-1.
+
+**Table 5.4.6-1: Multi-modal communication service performance requirements.**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | | Remarks
(NOTE 1) |
+|------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------|----------|--------------------------|---------------------|-----------------------------|
+| | Max allowed end-to-end latency (NOTE 2) | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | # of UEs | UE Speed | Service Area | |
+| Skillset sharing low-dynamic robotics (including teleoperation) Controller to controllee | 5-10ms | 0.8 - 200 kbit/s (with compression) | [99,999%] | n DoFs: (2n)-(8n)
(n=1,3,6) | - | Stationary or Pedestrian | 100 km 2 | Haptic (position, velocity) |
+| Skillset sharing low-dynamic robotics (including teleoperation) Controllee to controller | 5-10ms | 0.8 - 200 kbit/s (with compression) | [99,999%] | n DoFs: (2n)-(8n)
(n=1,10,100) | - | Stationary or Pedestrian | 100 km 2 | Haptic feedback |
+| | 10ms | 1-100 Mbit/s | [99,999%] | 1500 | - | Stationary or Pedestrian | 100 km 2 | Video |
+| | 10ms | 5-512 kbit/s | [99,9%] | 50 | - | Stationary or Pedestrian | 100 km 2 | Audio |
+| Highly dynamic/mobile robotics Controller to controllee | 1-5ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | [99,999%] (with compression)
[99,9%] (w/o compression) | n DoFs: (2n)-(8n)
(n=1,3,6) | - | high-dynamic | 4 km 2 | Haptic (position, velocity) |
+| Highly dynamic/mobile robotics Controllee to controller | 1-5ms | 0.8 - 200 kbit/s | [99,999%] (with compression)
[99,9%] (w/o compression) | n DoFs: (2n)-(8n)
(n=1,10,100) | - | high-dynamic | 4 km 2 | Haptic feedback |
+| | 1-10ms | 1-10 Mbit/s | [99,999%] | 2000-4000 | - | high-dynamic | 4 km 2 | Video |
+| | 1-10ms | 100-500 kbit/s | [99,9%] | 100 | - | high-dynamic | 4 km 2 | Audio |
+
+NOTE 1: Haptic feedback is typically haptic signal, such as force level, torque level, vibration and texture.
+
+NOTE 2: The latency requirements are expected to be satisfied even when multi-modal communication for skillset sharing is via indirect network connection (i.e., relayed by one UE to network relay).
+
+## 5.5 Haptic feedback for a personal exclusion zone in dangerous remote environments
+
+### 5.5.1 Description
+
+With the assistance of 5G networks, many industries including mining, operate unmanned and automated. In mining scenarios, drilling safety and precise control for automated rigs and sending effective alarms when needed to the onsite crew is vital for their safety. When crew move heavy lifting equipment wearing personal protection equipment (PPE) for their safety or work in a noisy/poor visibility environment, audio/light alarm systems coverage may not be detected
+
+for immediate reaction therefore use of wearables (belts, shoe sole, arm/shoulder tactile equipment) can improve the reliability of alarm system.
+
+Furthermore, the nature of human brain response time to light and audio makes the use of haptic feedback to alert faster and more reliable. Human brain response to the sense of touch in range of 1 ms where the response to audio and video is in 100s of milliseconds. Therefore, the alarm system can be enriched with additional haptic information and multi-modal session can be relayed to the on-site crew over to accelerate human response time and improve the system reliability.
+
+While haptic alarm can be actuated on an extended PPE haptic device (e.g., belt) to improve alerting the on-site crew, the audio siren and light evacuation signals (where possible) need to be sent, as an alert to ambient actuators requiring a multi-modal information transfer via separate service data flows, to the proximity devices during an emergency for directing them to a safe location. Furthermore, affective wearables feedback and affective or biometric data collected from workers can adjust the navigation process to the workers' temperament in order to effectively guide them away from the hazard locations.
+
+As an example, in a large mining environment, a hazard scenario is detected by the remote control unit to notify and navigate on-site workers by a multi-modal alarm system to avoid exclusion zones. The multi-modal alarm system monitors the environment using surveillance cameras fixed in the local site, on drones, or on workers helmets as well as haptic information relayed by the workers. Ambient sensory information (smoke, temperature, audio/video) can be relayed to a remote central monitoring and control unit to predict/detect hazard scenarios.
+
+The personal exclusion zone needs to be defined to prohibit the entry of the on-site workers which can change over time. The detected exclusion zone information from remote control unit will actuate devices (e.g., siren and light) fixed in the local site or in drones as well PPE haptic belt actuator to navigate the workers.
+
+### 5.5.2 Pre-conditions
+
+Multi-modal UEs, with sensor, haptic and audio/visual capabilities, are interconnected, through the 5G Network provided by the MNO, both locally, or remotely over the MNO 5G Network.
+
+The MNO provides service data flows for multi-modal information delivered over one common session to different UEs. E.g., a single user may receive haptic information be sent to her/his haptic glove and belt and audio to be sent to her/his headset to help navigate the worker through the exclusion zone.
+
+
+
+Diagram illustrating the architecture of a personal exclusion zone system. On the left, the 'Local Site' contains various sensors and actuators: a surveillance camera, an alarm (actuator), a drone, a worker wearing a headset (Audio/Visual), affective wearables, a haptic glove (actuator), and a haptic belt (actuators). These components send 'Environmental info', 'Emotional data', and 'Haptic Alerts' to a central '5G Network' cloud. The 5G network connects to a 'Monitoring and Control Server'. From the server, data flows to the 'Remote Site' on the right. The remote site includes a 'Video' monitor, a 'UE with Voice direction' (represented by a blue stick figure), and a 'UE with Haptic Control Navigation capabilities' (represented by a robot). The server sends 'Video', 'Haptic Alerts', and control signals to these remote units.
+
+Figure 5.5.2-1. Example of a personal exclusion zone
+
+### 5.5.3 Service Flows
+
+1. A Worker using PPE connected to a monitoring and control unit walks through a mining site where multiple exclusion zones are defined to protect her/him from hazardous occurrences. As the worker gets closer to the
+
+exclusion zone, her/his PPE establishes a session to enable transmission of alarms to the monitoring and control unit, e.g., noise levels, visibility levels and user location.
+
+2. If a hazard situation is detected, on-site workers need to be alerted immediately and defined personal exclusion zone(s) should be communicated with the on-site miners according to their proximity to the exclusion zone. Thus, the monitoring system determines that the user must be alerted, through haptic and audio alerts, since the monitoring and control unit determined that those are the modal types the user can utilize safely in the dangerous environment.
+3. The monitoring and control system, navigates workers using both a trained haptic language instruction (single buzz on the right side: move right, single buzz on the left side: move left, etc.) set and audio/visual mechanism to enable the user to safely leave the hazard area.
+
+### 5.5.4 Post-conditions
+
+The site worker is safely navigated away from the dangerous exclusion zone as the 5G network enables the PPE to alert the monitoring and control unit of dangerous situations which triggers the monitor and control unit to use the 5G network to transmit multi-modal commands to steer away site workers from dangerous exclusion zones.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+In 3GPP TS 22.263 [4], there are requirements for supporting video, imaging, and audio for professional applications.
+
+In 3GPP TS 22.261 [6] there are requirements to support the following:
+
+Clause 6.3 Multiple Access Technologies
+
+“The 5G system shall support a set of identities for a single user in order to provide a consistent set of policies and a single set of services across 3GPP and non-3GPP access type”
+
+Clause 6.26.2.5 Traffic Types
+
+“The 5G system shall support traffic scenarios typically found in a home setting (from sensors to video streaming, relatively low amount of UEs per group, many devices are used only occasionally) for 5G LAN-type service”
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR. 5.5.6-1] The 5G network shall support a mechanism to allow an authorized 3rd party to provide QoS policy for flows of multiple UEs associated with an application. The policy may contain e.g. the expected 5GS handling and the associated triggering event.
+
+[PR. 5.5.6-2] The 5G system shall support a mechanism to apply QoS policy for flows of multiple UEs associated with an application received from an authorized 3rd party.
+
+[PR 5.5.6-3] The 5G system shall provide a network connection to address the KPIs for immersive multi-modal navigation applications, see Table 5.5.6-1.
+
+**Table 5.5.6-1: Potential Key performance requirements for a personal exclusion zone in dangerous remote environments.**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | | Remarks |
+|------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------------------------------|----------|------------------------------------------------------|---------------------------------|-----------------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | # of UEs | UE Speed | Service Area | |
+| Immersive multi-modal navigation applications
Remote Site → Local Site (DL) | 50 ms [11] | 16 kbit/s - 2 Mbit/s (without haptic compression encoding)
0.8 - 200 kbit/s (with haptic compression encoding) | [99.999 %] | 1 DoF: 2 to 8
10 DoF: 20 to 80
100 DoF: 200 to 800 | - | Stationary or Pedestrian | ≤ 100 km 2
NOTE 2 | Haptic feedback |
+| | < 400 ms [11] | 1-100 Mbit/s | [99.999 %] | 1500 | - | Workers: Stationary/ or Pedestrian, | ≤ 100 km 2
NOTE 2 | Video |
+| | < 150 ms [11] | 5-512 kbit/s | [99.9 %] | 50 | - | Stationary or Pedestrian | ≤ 100 km 2
NOTE 2 | Audio |
+| | < 300 ms | 600 Mbit/s | [99.9 %] | MTU | - | Stationary or Pedestrian | ≤ 100 km 2
NOTE 2 | VR |
+| Local Site → Remote Site (UL) | < 300 ms | 12 kbit/s [26] | [99.999 %] | 1 500 | - | Stationary or Pedestrian | ≤ 100 km 2
NOTE 2 | Biometric / Affective |
+| | < 400 ms [11] | 1-100 Mbit/s | [99.999 %] | 1 500 | - | Workers: Stationary/ or Pedestrian, UAV: [30-300mph] | ≤ 100 km 2
NOTE 2 | Video |
+| | < 150 ms [11] | 5-512 kbit/s | [99.9 %] | 50 | - | Stationary or Pedestrian | ≤ 100 km 2
NOTE 2 | Audio |
+| | < 300 ms | 600 Mbit/s | [99.9 %] | MTU | - | Stationary or Pedestrian | ≤ 100 km 2
NOTE 2 | VR |
+
+NOTE 1: The number of UEs is not indicated in the table, but the number depends on the application, the actual deployment, the service area and the distributed UEs chosen to improve / address required user experience.
+
+NOTE 2: The service area depends on the deployment but is the same for uplink and downlink traffic. A local approach can be used in order to satisfy requirements of low latency and high reliability (i.e. the application server will be hosted at the network edge).
+
+[PR 5.5.6-4] The 5G system shall support the following synchronization thresholds to support immersive multi-modal navigation applications, see Table 5.5.6-2.
+
+**Table 5.5.6-2: Potential Key performance requirements for synchronization thresholds for a personal exclusion zone in dangerous remote environments.**
+
+| synchronisation threshold | | |
+|---------------------------|--------------------------|---------------------------|
+| audio-tactile | audio delay:
[50 ms] | tactile delay:
[25 ms] |
+| visual-tactile | visual delay:
[15 ms] | tactile delay:
[50 ms] |
+
+## 5.6 Live Event Selective Immersion
+
+### 5.6.1 Description
+
+To provide immersive experience of a live football game to the audience not at the scene, multiple AI cameras are deployed in the stadium collecting data of the video and audio from different angles for the generation of footages at the Application Server. The footages are provided to the audience for selection.
+
+The AI camera predictively follows the live action, depending on the objects to follow e.g. ball or player. The Application Server predicts the potential actions of the object based on the data collected from the cameras and instructs the camera on what object to follow and how to follow. The AI camera acts based on the instructor from the Application Server.
+
+This use case shows an example of multi-modal service as defined in clause 4.1 and 4.2, in which the application server requires inputs from multiple UEs to generate the outputs. The service flows and potential new requirements of this use case also apply to other multi-modal interactive system use case scenarios.
+
+### 5.6.2 Pre-conditions
+
+
+
+```
+
+graph TD
+ AS[Application Server]
+ C1[Camera#1] -- "Motion+footage" --> AS
+ C2[Camera#2] -- "motion" --> AS
+ C3[Camera#3] -- "Motion+footage" --> AS
+ C4[Camera#4] -- "footage" --> AS
+ C5[Camera#5] -- "motion" --> AS
+ AS -.-> C1
+ AS -.-> C2
+ AS -.-> C3
+ AS -.-> C4
+ AS -.-> C5
+ AS -.-> Alice((Alice))
+
+```
+
+Diagram illustrating Live Event Selective Immersion. An Application Server (orange box) is connected to five AI cameras (Camera#1 to Camera#5) and a user (Alice). The cameras are connected to the server via dashed blue arrows. Camera#1 sends 'Motion+footage', Camera#2 sends 'motion', Camera#3 sends 'Motion+footage', Camera#4 sends 'footage', and Camera#5 sends 'motion'. The server sends dashed blue arrows to each camera and to Alice.
+
+**Figure 5.6.2-1. Live Event Selective Immersion**
+
+Each AI camera interacts with the Application Server over 5GS network as a UE.
+
+Alice is watching the football game, and the footages for selection are transmitted to her UE over 5GS network.
+
+Footages and motion prediction are generated at the Application Server based on the video and audio data collected by the AI camera.
+
+Each AI camera has its own responsibilities:
+
+- Camera#1: data collection for motion prediction and footage generation, the primary camera placed in a location owning the best view
+
+- Camera#2: data collection for motion prediction, placed in the best location for capturing the motion
+- Camera#3: data collection for motion prediction and footage generation
+- Camera#4: data collection for footage generation
+- Camera#5: data collection for motion prediction
+
+### 5.6.3 Service Flows
+
+1. The football game starts. Camera#1, Camera#2, Camera#3, Camera#4 and Camera#5, as the UEs, are switched on and registered to the 5GS network to collect video and audio data to conduct Live Event Selective Immersion service.
+2. The Application Server informs 5GS that UEs corresponding to Camera#1, Camera#2, Camera#3, Camera#4 and Camera#5 are subject to the service application, and provides QoS requirements of these UEs and the coordination policies for this multi-modal service for assistance from 5GS.
+3. The QoS requirements and the coordination policy are applied at 5GS. Camera#1, Camera#2, Camera#3, Camera#4 and Camera#5 transmit the collected data over 5GS to the Application Server at the target QoS.
+4. The Application Server makes motion prediction based on data received from Camera#1, Camera#2, Camera#3 and Camera#5, and generates footages based on data received from Camera#1, Camera#3 and Camera#4.
+5. The Application Server transmits motion prediction of the object(s) over 5GS to Camera#1, Camera#2, Camera#3 and Camera#5 and transmits footages over 5GS to Alice's UE.
+6. Some people are gathering at the gate of the stadium for the celebration of winning scores, then network congestion happens from time to time. Based on the coordination policy of the multi-modal service, when the target QoS of Camera#1 can't be guaranteed, 5GS reduces QoS of Camera#4 to make sure QoS of Camera#1 is guaranteed; when the congestion is relieved, 5GS increases QoS of Camera#4 while target QoS of Camera#1 is still guaranteed.
+7. The network congestion gets more serious, and target QoS of Camera#2 can't be guaranteed. Since the motion data collected by Camera#2 is mandatory for motion prediction without which the motion prediction can't be made, 5GS releases resources of Camera#2 and Camera#5 based on the coordination policy of the multi-modal service.
+
+NOTE: When motion prediction doesn't work, the Application Server may request the 5GS network to only guarantee QoS of Camera#1 or to release resources of all the cameras. This is beyond what 5GS can coordinate.
+
+### 5.6.4 Post-conditions
+
+Alice receives multiple footages and selects one of them to enjoy the immersive experience.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 clause 6.7.2 and clause 6.8 defined the following policy control requirements that can be reused to this use case:
+
+- The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service.
+- The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
+- The 5G system shall support the creation and enforcement of prioritisation policy for users and traffic, during connection setup and when connected.
+- Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration.
+
+3GPP TS 22.261 [6] clause 6.23.2 defines the following requirements enabling 5GS to notify an authorized entity of the communication events:
+
+- The 5G system shall be able to provide notification of communication events to authorized entities per pre-defined patterns (e.g. every time the bandwidth drops below a pre-defined threshold for QoS parameters the authorized entity is notified, and the event is logged).
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR 5.6.6-1] The 5G system shall support a mechanism to allow an authorized 3rd party to provide QoS policy for flows of multiple UEs associated with an application. The policy may contain e.g. the expected 5GS handling and the associated triggering event.
+
+[PR 5.6.6-2] The 5G system shall support a mechanism to apply QoS policy for flows of multiple UEs associated with an application received from an authorized 3rd party.
+
+## 5.7 Support for IEEE P1918.1 architecture
+
+### 5.7.1 Description
+
+The on-going IEEE project P1918.1 “Tactile Internet: Application Scenarios, Definitions and Terminology, Architecture, Functions, and Technical Assumptions” [13] facilitates the rapid realization of the Tactile Internet as a 5G and beyond application, across a range of different user groups. The standard defines a framework for the Tactile Internet, including descriptions of various application scenarios, definitions and terminology, functions, and technical assumptions. This framework prominently also includes a reference model and architecture, which defines common architectural entities, interfaces between those entities, and the mapping of functions to those entities. The Tactile Internet encompasses low latency high reliability applications (e.g., manufacturing, transportation, healthcare and mobility), as well as non-critical applications (e.g., edutainment and events).
+
+Tactile Internet provides a medium for remote physical interaction, including the exchange of haptic information. This interaction are among humans and / or machines (e.g., robots, networked functions, software, or any other connected entity). There are two broad categories of haptic information, namely, tactile or kinaesthetic. Tactile information refers to the perception of information by the various mechanoreceptors of the human skin, such as surface texture, friction, and temperature. Kinaesthetic information refers to the information perceived by the skeleton, muscles, and tendons of the human body, such as force, torque, position, and velocity. The goal of Tactile Internet in human-in-the-loop scenarios is that humans should not be able to distinguish between locally executing a manipulative task compared to remotely performing the same task across the Tactile Internet.
+
+Figure 5.8.1-1 illustrates the functional architecture for the Tactile Internet proposed by IEEE P1918.1 [3]. Each tactile edge consists of one or multiple tactile devices (TD), where TDs in tactile edge A communicate tactile / haptic information with TDs in tactile edge B through a network domain, to meet the requirements of a given Tactile Internet use case. The gateway node (GN) is an entity with enhanced networking capabilities that resides at the interface between the tactile edge and the network domain and is mainly responsible for user plane data forwarding. The GN is accompanied by a network controller (NC) that is responsible for control plane processing including intelligence for admission and congestion control, service provisioning, resource management and optimization, and connection management in order to achieve the required QoS for the Tactile Internet session. The network domain is shown to be composed of a radio access point or base station connected logically to control plane entities (CPEs) and user plane entities in the network core. 5G radio access and core network can be a network domain to meet the quality requirements of tactile use cases.
+
+![Diagram of IEEE P1918.1 [3] architecture with the GN and the NC residing as part of the network domain. The diagram shows two tactile edges (A and B) connected via a central network domain. Tactile Edge A contains a Tactile Device (TD) connected to a Sensor/Actuator (S/A) Gateway (SG/AG) and Sensor/Actuator Node (SN/AN) pair, which is further connected to a Human-System Interface Node (HN) and Controller Node (CN). This edge also connects to a computing and storage entity (SE) via an Open (O) interface. Tactile Edge B contains multiple nodes connected to a central hub. The Network Domain includes a Gateway Node (GN) and Network Controller (NC) pair, a Control Plane Entity (CPE), and a User Plane Entity (UPE). The GN & NC connects to the SE via an Open (O) interface, to the CPE via a Network (N) interface, and to the Tactile Service Manager (TSM) via a Service (S) interface. The TSM connects to External Application Service Providers via another Service (S) interface. A Bi-directional information exchange is shown between Tactile Edge A and Tactile Edge B through the network domain.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+Diagram of IEEE P1918.1 [3] architecture with the GN and the NC residing as part of the network domain. The diagram shows two tactile edges (A and B) connected via a central network domain. Tactile Edge A contains a Tactile Device (TD) connected to a Sensor/Actuator (S/A) Gateway (SG/AG) and Sensor/Actuator Node (SN/AN) pair, which is further connected to a Human-System Interface Node (HN) and Controller Node (CN). This edge also connects to a computing and storage entity (SE) via an Open (O) interface. Tactile Edge B contains multiple nodes connected to a central hub. The Network Domain includes a Gateway Node (GN) and Network Controller (NC) pair, a Control Plane Entity (CPE), and a User Plane Entity (UPE). The GN & NC connects to the SE via an Open (O) interface, to the CPE via a Network (N) interface, and to the Tactile Service Manager (TSM) via a Service (S) interface. The TSM connects to External Application Service Providers via another Service (S) interface. A Bi-directional information exchange is shown between Tactile Edge A and Tactile Edge B through the network domain.
+
+| | | | | | |
+|-------------|------------------------------|-------------|-------------------------|-------------|-------------------|
+| AG: | Actuator Gateway | AN: | Actuator Node | CN: | Controller Node |
+| CPE: | Control Plane Entity | GN: | Gateway Node | GNC: | GN & CN |
+| HN: | human-system interface node | NC: | Network Controller | S/A: | Sensor/Actuator |
+| SE: | computing and storage Entity | SG: | Sensor Gateway | SN: | Sensor Node |
+| TD: | Tactile Device | TSM: | Tactile Service Manager | UPE: | User Plane Entity |
+
+**Figure 5.7.1-1. IEEE P1918.1 [3] architecture with the GN and the NC residing as part of the network domain**
+
+The tactile service manager (TSM) plays a critical role in defining the characteristics and requirements of the service between the two tactile edges and in disseminating this information to key nodes in the tactile edge and network domain. The control information between the TSM and the GNC is carried over Service (S) Interface. SE, a computing and storage entity, provides both computing and storage resources for improving the performance of the tactile edges and meeting the delay and reliability requirements of the E2E communications. Open (O) Interface is used to carry information exchange between any architectural entity and the SE.
+
+We demonstrate how 5G network is used as the “network domain” in the IEEE P1918.1 [3] architecture to support a typical multi-modal use case -- teleoperation.
+
+### 5.7.2 Pre-conditions
+
+Teleoperation allows human users to immerse into an inaccessible environment to perform complex tasks. A typical teleoperation system includes a controller (i.e., the user) and a device (i.e., the tele-manipulator), which exchange haptic signals (forces, torques, position, velocity, vibration, etc.), video signals, and audio signals over a communication network. In particular, the communication of haptic information imposes strong demands on the communication network as it closes a global control loop between the user and the tele-operator. Four communication streams are involved in a typical multi-modal use case -- teleoperation:
+
+- Haptic Control stream. It carries command queries from the user to the remote haptic equipment.
+- Haptic Feedback stream. It carries sensor data and response queries from the remote haptic equipment back to the user.
+- Video stream. It carries an encoded video stream from the remote environment back to the user. Depending on the resolution of the video, this stream usually occupies the highest percentage of the bandwidth of the communicational channel.
+
+- Audio stream. It carries audio data from the remote environment back to the user.
+
+Note that multiple devices may be involved at both or either side of the multi-modal communication, and a single multi-modal communication session may comprise multiple streams between multiple devices. It is assumed that all the above streams are carried over the 5G network as the “network domain” as defined in IEEE P1918.1 functional architecture.
+
+### 5.7.3 Service Flows
+
+1. Both the controller (“Tactile Edge A”) and the tele-manipulator (“Tactile Edge B”) are equipped with multiple devices to capture, transmit and receive audio, video and haptic information.
+2. When a session starts, multiple streams are established over the 5G network (“Network Domain” in the IEEE P1918.1 architecture) between the corresponding devices at the controller and the tele-manipulator that carry multiple modalities data. Table 5.7.3-1 depicts the typical QoS requirements that have to be fulfilled in order for the users’ QoE to be satisfactory.
+
+**Table 5.7.3-1 Typical QoS requirements for multi-modal streams [14] [15] [16] [17] [18]**
+
+| | Haptics | Video | Audio |
+|---------------------|-------------|-------------------|------------|
+| Jitter (ms) | $\leq 2$ | $\leq 30$ | $\leq 30$ |
+| Delay (ms) | $\leq 50$ | $\leq 400$ | $\leq 150$ |
+| Packet loss (%) | $\leq 10$ | $\leq 1$ | $\leq 1$ |
+| Update rate (Hz) | $\geq 1000$ | $\geq 30$ | $\geq 50$ |
+| Packet size (bytes) | 64-128 | $\leq \text{MTU}$ | 160-320 |
+| Throughput (kbit/s) | 512-1024 | 2500 - 40000 | 64-128 |
+
+3. The controller starts to capture the first Media Units (MUs) of haptic information, video and voice at the same time. In this case, the three MUs have the same timestamp, which represents the generation time. Assuming that the sampling interval for haptics, video and audio are 1 ms, 30 ms and 20 ms. The source transmits the first haptic MU about 20-30 ms earlier than the MUs of audio and video, which may result in more 20 ms difference between the arrival time of the MUs of different modalities. If the destination outputs the MUs at the same time, it has to delay the output of the haptic MU until the voice and video MUs arrive at the destination.
+4. A Synchronization Unit is assumed to preserve the time relation of the original signal as steady as possible and synchronize the three media streams with each other. This unit can be part of TSM or can be located in the Tactile Edge. Synchronization becomes increasingly challenging with the increasing demand from the application itself, for example immersive XR experience, as well as the inevitable jitter/delay issues (especially due to the nature of the wireless communication) in the network domain. Necessary information is exchanged between the TSM (including the synchronization unit) and the 5G network for the assistance of the synchronization between different streams of a multi-modal communication session. Audio, video and haptic MUs arrive at the Synchronization Unit and are re-synchronized before getting to the destination.
+
+### 5.7.4 Post-conditions
+
+The user enjoys the good experiences in teleoperation enabled by 5G network and Tactile Internet, where human users are not being able to distinguish between locally executing a manipulative task compared to remotely performing the same task across the Tactile Internet.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 [6], TS 22.263 [4] and TS 22.104 [21] have captured the KPIs for high data rate and low latency interactive services including Cloud/Edge/Split Rendering, Gaming or Interactive Data Exchanging, Consumption of VR content via tethered VR headset, and audio-video synchronization thresholds.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR 5.7.6-1] The 5G system shall support a mechanism to ensure users’ QoE of the multi-modal communication service involving one or multiple devices at either end of the communication. QoE refers to the difference of the physical interaction across the 5G network and the same manipulation carried out locally.
+
+[PR 5.7.6-2] The 5G system shall support a mechanism for a 3rd party application server to provide real-time feedback on the traffic characteristics and service requirements of the multiple streams of a multi-modal communication session.
+
+[PR 5.7.6-3] The 5G system shall support a mechanism to assist the synchronisation between the multiple streams (e.g., haptic, audio and video) of a multi-modal communication session in order to avoid the negative impact on the user experience.
+
+## 5.8 Virtual factory
+
+### 5.8.1 Description
+
+Virtual factory is an important feature in industry 4.0, which provides people on remote site easy access to factory. Virtual factory could support immersive monitor of real scene, simulation and analysis on production line planning and practical production adjustment.
+
+![Figure 5.8.1-1: Virtual Factory and a photo of the real factory floor under construction [19].](eca7fa4eb8dd1303e4bd56aee6555b2d_img.jpg)
+
+The image consists of two vertically stacked panels. The top panel is a 3D virtual simulation of a factory interior. A male avatar with blonde hair, wearing a white dress shirt and a black blazer, stands in the center of a wide, well-lit factory floor. The floor is light grey, and the walls are white. In the background, there are various industrial machines, including a large grey cylindrical tank on the left and a conveyor belt system on the right. The ceiling has exposed yellow steel beams and industrial lighting. A logo for 'FX PAL' is visible on the wall. The bottom panel is a photograph of a real factory floor under construction. The floor is a smooth, reflective grey surface. In the background, there are large industrial tanks and machinery, similar to those in the virtual simulation. The ceiling has exposed steel beams and industrial lighting. The overall scene suggests a modern, industrial environment.
+
+Figure 5.8.1-1: Virtual Factory and a photo of the real factory floor under construction [19].
+
+**Figure 5.8.1-1. Virtual Factory and a photo of the real factory floor under construction [19].**
+
+Also it can provide an approach in managing distributed realistic factory when considering establishing a complex production line which need to combine the capability of several factories.
+
+
+
+Figure 5.8.1-2: A service-oriented virtual factory diagram. It shows two nested virtual factories: 'Virtual factory 1 - Manufacturing of standard car seats' and 'Virtual factory 2 - Manufacturing of high-quality car seats'. Virtual factory 1 contains a process flow: Car seat frame -> Upholstering -> Car seat cover -> Final assembly. Each step is associated with an SLA and a supplier: Supplier 1 (Car seat frame), Supplier 2 (Upholstering), and JD-Company (Car seat cover and Final assembly). Both virtual factories are managed by a 'Virtual factory management' layer containing four functions: Process definition, Process forecasting and simulation, Process execution, and Real-time monitoring.
+
+Figure 5.8.1-2. A service-oriented virtual factory [20]
+
+### 5.8.2 Pre-conditions
+
+1. Factory is covered by 5G signals. An industrial robot and a monitoring camera are connected to 5G network.
+2. The remote site where the virtual factory will be displayed is also covered by 5G signals.
+
+### 5.8.3 Service Flows
+
+1. The factory first tells 5G network that the data flows of motion information collector of robot and monitor video need coordination.
+2. The motion information of the robot is collected and transferred through dataflow 1. A monitor camera captures the real movement of the industrial robot and transmit video signal through dataflow 2. Network will mark these two data flows according to the information factory provided.
+3. Data flow1 which carries the motion information signal will be transferred to the VR server and produce VR video according to the motion information. Dataflow 2 will be transferred directly to a screen in the remote site.
+4. On the remote site, there's a VR glasses which will receive the video data from the VR server. Alongside the VR glasses there's the monitor screen of the real robot motion.
+5. As the processing from motion information to VR video need time, dataflow 2 should be hold by network for a certain period. The dataflow of VR and monitor video will arrive at the remote site within a certain time window, so that users will not feel the delay between these two flows.
+
+
+
+Figure 5.8.3-1: Service flow diagram on virtual factory. It illustrates the network architecture for data flows. At the source (factory), 'Control information of robot' and 'video' are sent. The control information goes through an 'upstream' path involving an SPN (Service Provider Network) and a UPF (User Plane Function) to a 'CMNET' cloud. The video goes directly to the 'VR server'. From the CMNET cloud, the control information is processed by the VR server and then sent back through a 'downstream' path involving another SPN and UPF to a remote site. At the remote site, the VR server sends 'video' to 'VR glasses' and a 'monitor screen'.
+
+Figure 5.8.3-1. Figure of service flow on virtual factory
+
+### 5.8.4 Post-conditions
+
+Due to the coordination processing network has done, users can see the virtual factory through VR glasses and the real scene in factory on screen without feeling any delay.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+none
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR 5.8.6-1] 5G system shall be able to support the interaction with applications on UEs or data flows grouping information within one tactile and multi-modal communication service.
+
+[PR 5.8.6-2] The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
+
+NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs' flows (e.g., haptic, audio and video) of a multi-modal communication session.
+
+# 6 Consolidated requirements
+
+## 6.1 Consolidated potential requirements
+
+**Table 6.1-1: Consolidated Requirements**
+
+| CPR # | Original PR # | Consolidated Potential Requirement | Comment |
+|-----------|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| CPR 6.1-1 | [PR 5.2.6-2],
[PR 5.3.6-2],
[PR 5.5.6-1],
[PR 5.6.6-1],
[PR 5.7.6-2],
[PR 5.8.6-1], | The 5G system shall enable an authorized 3rd party to provide policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs' flows (e.g., haptic, audio and video) of a multi-modal communication session.
| |
+| CPR 6.1-2 | [PR 5.5.6-2],
[PR 5.6.6-2],
[PR 5.7.6-3],
[PR 5.8.6-2] | The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs' flows (e.g., haptic, audio and video) of a multi-modal communication session.
| |
+
+## 6.2 Consolidated potential KPIs
+
+The 5G system shall support tactile and multi-modal communication services with the following KPIs.
+
+**Table 6.2-1: Multi-modal communication service performance requirements**
+
+| Use Cases | Characteristic parameter (KPI) | | | Influence quantity | | | Remarks |
+|-----------------------------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------|------------------------------------------------------------------------------------|
+| | Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | UE Speed | Service Area | |
+| Immersive multi-modal VR (UL: device → application sever) | 5 ms (note 2) | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.9% (without haptic compression encoding)
99.999% (with haptic compression encoding)
[3] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
More DoFs can be supported by the haptic device | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Haptic feedback |
+| | 5 ms | < 1Mbit/s | 99.99% [3] | 1500 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Sensing information e.g. position and view information generated by the VR glasses |
+| Immersive multi-modal VR (DL: application sever → device) | 10 ms (note1) | 1-100 Mbit/s | 99.9% [3] | 1500 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Video |
+| | 10 ms | 5-512 kbit/s | 99.9% [3] | 50 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Audio |
+| | 5 ms (note 2) | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.9% (without haptic compression encoding)
99.999% (with haptic compression encoding)
[3] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | Stationary or Pedestrian | typically < 100 km 2 (note 5) | Haptic feedback |
+| Remote control robot | 1-20ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.999% [3] | 2-8 (1 DoF) | high-dynamic (≤ 50 km/h) | ≤ 1 km 2 | Haptic feedback |
+| | 20-100ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.999% [3] | 2-8 (1 DoF) | Stationary or Pedestrian | ≤ 1 km 2 | Haptic feedback |
+| | 5 ms | 1-100 Mbit/s | 99.999% [3] | 1500 | Stationary or Pedestrian | ≤ 1 km 2 | Video |
+| | 5 ms | 5-512 kbit/s | 99.9% [3] | 50-100 | Stationary or Pedestrian | ≤ 1 km 2 | Audio |
+| | 5 ms | < 1Mbit/s | 99.999% [3] | - | Stationary or Pedestrian | ≤ 1 km 2 | Sensor information |
+
+| | | | | | | | |
+|------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------------------------------------|----------------------------|---------------------------------|-----------------------------|
+| Skillset sharing low-dynamic robotics (including teleoperation ) Controller to controlee | 5-10ms | 0.8 - 200 kbit/s (with compression) | 99,999% [3][27] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | Stationary or Pedestrian | 100 km 2 | Haptic (position, velocity) |
+| Skillset sharing low-dynamic robotics (including teleoperation ) Controlee to controller | 5-10ms | 0.8 - 200 kbit/s (with compression) | 99,999% [3][27] | 1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800 | Stationary or Pedestrian | 100 km 2 | Haptic feedback |
+| | 10ms | 1-100 Mbit/s | 99,999% [3] [27] | 1500 | Stationary or Pedestrian | 100 km 2 | Video |
+| | 10ms | 5-512 kbit/s | 99,9% [3] [27] | 50 | Stationary or Pedestrian | 100 km 2 | Audio |
+| Skillset sharing Highly dynamic/ mobile robotics Controller to controlee | 1-5ms | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99,999% (with compression)
99,9% (w/o compression) [3] [27] | 1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48 | high-dynamic | 4 km 2 | Haptic (position, velocity) |
+| Skillset sharing Highly dynamic/ mobile robotics Controlee to controller | 1-5ms | 0.8 - 200 kbit/s | 99,999% (with compression)
99,9% (w/o compression) [3] [27] | 1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800 | high-dynamic | 4 km 2 | Haptic feedback |
+| | 1-10ms | 1-10 Mbit/s | 99,999% [3] [27] | 2000-4000 | high-dynamic | 4 km 2 | Video |
+| | 1-10ms | 100-500 kbit/s | 99,9% [3] [27] | 100 | high-dynamic | 4 km 2 | Audio |
+| Immersive multi-modal navigation applications Remote Site → Local Site (DL) | 50 ms [39] | 16 kbit/s -2 Mbit/s (without haptic compression encoding);
0.8 - 200 kbit/s (with haptic compression encoding) | 99.999 % [3] | 1 DoF: 2 to 8
10 DoF: 20 to 80
100 DoF: 200 to 800 | Stationary or Pedestrian | ≤ 100 km 2 ( note 5) | Haptic feedback |
+| | <400 ms [39] | 1-100 Mbit/s | 99.999 % [3] | 1500 | Stationary/ or Pedestrian, | ≤ 100 km 2 (note 5) | Video |
+| | <150 ms [39] | 5-512 kbit/s | 99.9 % [3] | 50 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | Audio |
+| | <300 ms | 600 Mbit/s | 99.9 % [3] | 1500 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | VR |
+
+| | | | | | | | |
+|--------------------------------------------------------------------------------|--------------|----------------|--------------|------|------------------------------------------------------|--------------------------------|-----------------------|
+| Immersive multi-modal navigation applications
Local Site → Remote Site (UL) | <300 ms | 12 kbit/s [26] | 99.999 % [3] | 1500 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | Biometric / Affective |
+| | <400 ms [39] | 1-100 Mbit/s | 99.999 % [3] | 1500 | Workers: Stationary/ or Pedestrian, UAV: [30-300mph] | ≤ 100 km 2 (note 5) | Video |
+| | <150 ms [39] | 5-512 kbit/s | 99.9 % [3] | 50 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | Audio |
+| | <300 ms | 600 Mbit/s | 99.9 % [3] | 1500 | Stationary or Pedestrian | ≤ 100 km 2 (note 5) | VR |
+
+NOTE 1: Motion-to-photon delay (the time difference between the user's motion and corresponding change of the video image on display) is less than 20 ms, and the communication latency for transferring the packets of one audio-visual media is less than 10 ms, e.g. the packets corresponding to one video/audio frame are transferred to the devices within 10 ms.
+
+NOTE 2: According to IEEE 1918.1 [3] as for haptic feedback, the latency is less than 25 ms for accurately completing haptic operations. As rendering and hardware introduce some delay, the communication delay for haptic modality can be reasonably less than 5 ms, i.e. the packets related to one haptic feedback are transferred to the devices within 10 ms.
+
+NOTE 3: Haptic feedback is typically haptic signal, such as force level, torque level, vibration and texture.
+
+NOTE 4: The latency requirements are expected to be satisfied even when multimodal communication for skillset sharing is via indirect network connection (i.e., relayed by one UE to network relay).
+
+NOTE 5: In practice, the service area depends on the actual deployment. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
+
+# 7 Conclusions and recommendations
+
+This TR provides a number of use cases for tactile and multi-modality communication services such as immersive multi-modal virtual reality (VR) application, remote controlled robots, support of skillset sharing for robots, haptic feedback for dangerous environments, live event selective immersion, virtual factory, and others.
+
+The potential new requirements for each use cases are compiled into a set of potential consolidated requirements, including functional requirements and performance requirements, wherein a set of KPIs are defined, such as max allowed end-to-end latency, service bit rate, user-experienced data rate, reliability, message size, service area.
+
+The resulting consolidated potential requirements and KPIs identified in this TR can be considered for the development of normative requirements.
+
+# Annex A: Change history
+
+| Change history | | | | | | | | |
+|----------------|-------------|-----------|------|---------|-----|--------------------------------------------------------------------------------------------------------------------------|--|----------------|
+| Date | Meeting | TDoc | CR | R
ev | Cat | Subject/Comment | | New
version |
+| 2021-02 | SA1#93e | S1-210081 | | | | Skeleton | | 0.0.0 |
+| 2021-03 | SA1#93e | S1-210317 | | | | Including agreed docs: S1-210517, S1-210518, S1-210519, S1-210520, S1-210521, S1-210522, S1-210523 | | 0.1.0 |
+| 2021-05 | SA1#94e | S1-211313 | | | | Including agreed docs: S1-211100, S1-211214, S1-211228, S1-211494, S1-211495, S1-211496, S1-211497 | | 0.2.0 |
+| 2021-07 | SA1#94bis-e | S1-212101 | | | | Including agreed docs: S1-212058, S1-212142, S1-212143, S1-212144, S1-212145, S1-212146, S1-212147 | | 0.3.0 |
+| 2021-09 | SA1#95e | S1-213201 | | | | Including agreed docs: S1-213063, S1-213321, S1-213322, S1-213323, S1-213324, S1-213325, S1-213326, S1-213327, S1-213328 | | 0.4.0 |
+| 2021-09 | SA#93e | SP-211050 | | | | Raised to v.1.0.0 for one-step approval | | 1.0.0 |
+| 2021-09 | SA#93e | SP-211050 | | | | Raised to v.18.0.0 following one-step approval at SA#93e | | 18.0.0 |
+| 2021-12 | SP-94 | SP-211629 | 0001 | 1 | F | Verification of KPIs for the use case in clause 5.5 | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0002 | | D | Align the use of multi-modal | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0003 | 1 | F | Update of the KPI table in clause 5.4 | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0005 | 2 | B | TACMM CR Consolidation of potential requirements | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0006 | 2 | B | TACMM CR Consolidation of KPIs | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0007 | 2 | F | TACMM CR Clean up EN and TBD in KPI table in TR22.847 clause 5.2 | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0008 | 2 | F | TACMM CR Clean up TBD in KPI table in TR22.847 clause 5.3 | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0009 | 2 | F | TACMM CR Clean up EN in TR22.847 clause 5.8 | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0010 | 2 | B | TACMM CR Add conclusion | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0011 | 1 | F | Resolving the Editor's Notes in clause 5.1 | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0012 | 2 | D | Correction of editorial issues | | 18.1.0 |
+| 2021-12 | SP-94 | SP-211629 | 0013 | 1 | F | Resolving the Editor's Note in the KPI table in clause 5.1 | | 18.1.0 |
+| 2022-03 | SP#95e | SP-220079 | 0014 | 1 | D | Editorial corrections for quality improvement | | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22855/048e5a8baf735b071833f28b58d22e4f_img.jpg b/marked/Rel-18/22_series/22855/048e5a8baf735b071833f28b58d22e4f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d26cc2b7a6cdfa2cd71b89976665f00b4f80a977
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/048e5a8baf735b071833f28b58d22e4f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bda20e017473ebe9297ead1c02a49e0f7b26a820ddec686c0d55c34e0b0b2ef
+size 28743
diff --git a/marked/Rel-18/22_series/22855/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-18/22_series/22855/0ee9d674085524d589646a6c3fb21ec3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26c5565d55a1fe26c32ad836ad40c3c388fc9809
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/0ee9d674085524d589646a6c3fb21ec3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa1243042831e6ef4d77141ee6cf5a33fe897b095354fb7f8dc97ccbd42bc884
+size 50704
diff --git a/marked/Rel-18/22_series/22855/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Rel-18/22_series/22855/10781f43062bf3e9601a1e086710556c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..684719ec2d62976a0cf97d0472dc0772eb55903d
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/10781f43062bf3e9601a1e086710556c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27de702595354be92fa48e1cd430e25550923fe4ce01457d1b8321a11ea08d50
+size 44115
diff --git a/marked/Rel-18/22_series/22855/1271e2a879577b16665464014af5d1fe_img.jpg b/marked/Rel-18/22_series/22855/1271e2a879577b16665464014af5d1fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f2e174ffd4aa074f1ed694c7c9003066a813832
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/1271e2a879577b16665464014af5d1fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e0bfecb05c5e5bbe251ebb3f4e413b0e57e9e0987cef4c7a1e1c02fb83b254c
+size 7497
diff --git a/marked/Rel-18/22_series/22855/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-18/22_series/22855/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..829c6dcf8089f285a2f165be0a02472ddc6f1599
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:006be1df010fee258ccdae9973742ee0047e02a5acc0b25b8734cf15d60934e4
+size 70383
diff --git a/marked/Rel-18/22_series/22855/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/22_series/22855/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..625a16f81142e1dc8573b8137227de313b022e2f
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:28f8a36ef05f7f10bbea975507f5546fab3c0989cf65bb2e6e0cfcbc5176c50a
+size 51893
diff --git a/marked/Rel-18/22_series/22855/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-18/22_series/22855/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7d1818d5fb46d8a99c0ed37b25dded5229538c2
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8a3af064c8aee047ab67ad20405accc9b6147d81a6eac14f27510405acf8370
+size 58357
diff --git a/marked/Rel-18/22_series/22855/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg b/marked/Rel-18/22_series/22855/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94d089ed4dbbfe736081cd9aab05fbc8562149df
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b1a8a0e1d8cd924c7ec71e536af75e1989140001de8ec94f31601187b6697e9
+size 78538
diff --git a/marked/Rel-18/22_series/22855/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-18/22_series/22855/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..466c3eead72288d906a9e69042bf0df2ee490567
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b29b91f4ef67bdf8ae6ccaa1ab154370606aff3abe891ac526ee7e3c7f44a1e1
+size 70576
diff --git a/marked/Rel-18/22_series/22855/4386b8117f7248610045728eb21e1764_img.jpg b/marked/Rel-18/22_series/22855/4386b8117f7248610045728eb21e1764_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be299e00bb9400977e291a5423c18722117b146b
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/4386b8117f7248610045728eb21e1764_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98df81cb41281a2ae448be5ae8e5c51cc4541b208e6e7b91f382976dd90e867a
+size 16436
diff --git a/marked/Rel-18/22_series/22855/4a01d2a9ca92e9abd3caf874ba15430c_img.jpg b/marked/Rel-18/22_series/22855/4a01d2a9ca92e9abd3caf874ba15430c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..710cb140ed6e0f9eff8d1405de0a10797cd7f789
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/4a01d2a9ca92e9abd3caf874ba15430c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5c5bd59d06149d4f1161a775948f01ee80a4f0fd24d5d4756a4e6212daf01ed
+size 4516
diff --git a/marked/Rel-18/22_series/22855/4b00764d3c160ac6ade7502d9faeb615_img.jpg b/marked/Rel-18/22_series/22855/4b00764d3c160ac6ade7502d9faeb615_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f5afbec85c798951940d1c864601c81b4c33afe
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/4b00764d3c160ac6ade7502d9faeb615_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f80b500a2bbb0502f8a0fe53232713ba737dbc86f5b92175fb814168f3c337a5
+size 4955
diff --git a/marked/Rel-18/22_series/22855/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-18/22_series/22855/55136bc716146672fc680fa05989f1d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9660e79fab1ef3956f6580c51194ac7a6318bfb3
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/55136bc716146672fc680fa05989f1d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e65f6d80b1bd7e6ab3268988110adf7564fa2c07b8494e2a145fdcdfd15eea68
+size 11458
diff --git a/marked/Rel-18/22_series/22855/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22855/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..550b5822330b8a3ceff335c7446c000753893246
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32235761c6a13edda2dab54a54a32995e962fe03c84675f72e2977324a27b890
+size 9405
diff --git a/marked/Rel-18/22_series/22855/63a2519518616620ef0e53d98b923c05_img.jpg b/marked/Rel-18/22_series/22855/63a2519518616620ef0e53d98b923c05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b46c57c133130d270be21e48fed16b47966b9950
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/63a2519518616620ef0e53d98b923c05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75b72172650f779ceea72391f08b8cb66c994d29faff57d56ab9138accdb9d45
+size 20794
diff --git a/marked/Rel-18/22_series/22855/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22855/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..caf81d19d63813c9193fdaf898ceb5addcb1a469
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5aa3fe6f03bfb75e0dacf09dc6aa363d6db1db1823342ed1c321bb707ca682c
+size 5672
diff --git a/marked/Rel-18/22_series/22855/6c5332a475cc3b84f0989ed3df1e1ebd_img.jpg b/marked/Rel-18/22_series/22855/6c5332a475cc3b84f0989ed3df1e1ebd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3436d6c15e25796010141b7697b5a40bdfec18e1
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/6c5332a475cc3b84f0989ed3df1e1ebd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3741ce17c638d1bce9f063f19d0160ec622a522729ce9b7d140a5b2a5a172242
+size 6271
diff --git a/marked/Rel-18/22_series/22855/891ff9b651838b7f59e9a1612a739e15_img.jpg b/marked/Rel-18/22_series/22855/891ff9b651838b7f59e9a1612a739e15_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a344695993db9fab97300b5fd62b98f385901cab
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/891ff9b651838b7f59e9a1612a739e15_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1e0f687633bc9c03f3b0d1daf493a5dfeb3e66ff3d46c21b548ba0578f1e1b9
+size 29274
diff --git a/marked/Rel-18/22_series/22855/90a707f5e8b944c0fbb3be48addd16ae_img.jpg b/marked/Rel-18/22_series/22855/90a707f5e8b944c0fbb3be48addd16ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51fa463ac6791986145f1e8da544c06b0bfff478
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/90a707f5e8b944c0fbb3be48addd16ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b1a9ec0f779ae31c68abe26f45a3170e611f0bcec9041c5548eab23e4b3434c
+size 22034
diff --git a/marked/Rel-18/22_series/22855/92271d74f67effbd92583eb3fba71514_img.jpg b/marked/Rel-18/22_series/22855/92271d74f67effbd92583eb3fba71514_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44bad79d44c60c4553d2fbc2b00cabe7950af560
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/92271d74f67effbd92583eb3fba71514_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4027f27e1e71d9d1c90fca74d79daef0b5e49cda7a9d062902779d147656937f
+size 6138
diff --git a/marked/Rel-18/22_series/22855/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-18/22_series/22855/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..158ba8ba8b6d723c3db29f4781dd8920d905218e
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9500a7bc5906f8d2345837ee5f931678a5b65a1b08e1449af8e938d1f8ed31b4
+size 15281
diff --git a/marked/Rel-18/22_series/22855/93fa4105c1d3c48fee6b3fd97b631387_img.jpg b/marked/Rel-18/22_series/22855/93fa4105c1d3c48fee6b3fd97b631387_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..967fa144ab9d6150e9c4f62c132372b1198ba707
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/93fa4105c1d3c48fee6b3fd97b631387_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d045495d0409da9ec6a1b3f18bee5080ee4282004c1a3d2a9ac0941eb0d74270
+size 34034
diff --git a/marked/Rel-18/22_series/22855/9722ce414894942d7679c57745ca6aa4_img.jpg b/marked/Rel-18/22_series/22855/9722ce414894942d7679c57745ca6aa4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..31207d2b331d58a30b04cdbd609df021092ce60e
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/9722ce414894942d7679c57745ca6aa4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9e26af21e5b6d7b1494f6bd9db6fb38f0f8741e960a8edb7ed061e48fc54a100
+size 10027
diff --git a/marked/Rel-18/22_series/22855/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-18/22_series/22855/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..063c49eec5c9dd3a2c7a9a2baf405f3d4004da0b
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99ec627eed321c434aca4aae3dc39f812772db6dfbb89ef81dafb475ff26bf53
+size 51661
diff --git a/marked/Rel-18/22_series/22855/a13020013fec61a19fca51f0355467fe_img.jpg b/marked/Rel-18/22_series/22855/a13020013fec61a19fca51f0355467fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01c26268de45b270b0aeda744d4cb82343b9425b
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/a13020013fec61a19fca51f0355467fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b465d59d76d9646b1fa089267ec972fd335ece855722fbf8018732557e786366
+size 5145
diff --git a/marked/Rel-18/22_series/22855/a69d6cb43ee0ba9cdf803f6454db2f8e_img.jpg b/marked/Rel-18/22_series/22855/a69d6cb43ee0ba9cdf803f6454db2f8e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc89b52c0c05c6fc0afc379b864e1c7f44c4d386
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/a69d6cb43ee0ba9cdf803f6454db2f8e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc04a5944793d80bd9eb86a556d256d11acee33e6fc2855d63f918097e399f72
+size 38574
diff --git a/marked/Rel-18/22_series/22855/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-18/22_series/22855/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e66550d411fdedbb0aa73cfb88ceacb4cb5bbaa
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ba50ac7d844df5eece7ff97d3427b1fff1d7261b62257812246756c975637fd
+size 53787
diff --git a/marked/Rel-18/22_series/22855/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-18/22_series/22855/b904ac2472cab80892d1e783e6230d6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38476b403312a721ce9444e43461df718c5c1d3b
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/b904ac2472cab80892d1e783e6230d6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4da98857e6944ea301367cb305f6c00cc87dfa6e9d5299aa792bc300e3cb69a3
+size 23336
diff --git a/marked/Rel-18/22_series/22855/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-18/22_series/22855/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66e70c178529da6d47e1d495bf92b3c3f204ede9
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:744e5e7590bf79c2b8bfee45d87588e4ab4fe965f89030711abe0b2f47227128
+size 14442
diff --git a/marked/Rel-18/22_series/22855/da9505d99521f95115e588a0f9e87cc1_img.jpg b/marked/Rel-18/22_series/22855/da9505d99521f95115e588a0f9e87cc1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cec9ec32ea63dc6914f23cbb92f3a1f45195f633
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/da9505d99521f95115e588a0f9e87cc1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef9ec204297499beaca89c09cbaf45d3d91ab852590e2fecb44d18e9e0f7a78c
+size 33106
diff --git a/marked/Rel-18/22_series/22855/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-18/22_series/22855/e05b36c0d46549e681ce6581422c66b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3460d55aee58484f3cc36cc208dcac229df82c94
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/e05b36c0d46549e681ce6581422c66b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a158e2d39ce1032ce97134aab54d452df0bde19d1ba048687b911db6a545b1cd
+size 35206
diff --git a/marked/Rel-18/22_series/22855/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-18/22_series/22855/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eb0ee4329a594d3204caa83badb8818b122d7a06
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11ef5d7f9e6717bf2f4a4736c6444c92bd59a716571021a1c5e2441ae1ca581f
+size 22762
diff --git a/marked/Rel-18/22_series/22855/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-18/22_series/22855/e4c6fa93821e3546ee9fcae897ae2771_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..767ac5d8144c62455066cb7e52e8478857162e23
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/e4c6fa93821e3546ee9fcae897ae2771_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd653edc5f5d557bcd7e0e0275035e7f8927a5d8625067d86ba2f3d585f46d43
+size 76629
diff --git a/marked/Rel-18/22_series/22855/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg b/marked/Rel-18/22_series/22855/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f053e43e9d0158c57e695888e4e84d00ac13af41
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:956e832bf8cfdfb220ea8c13577da0aaff6bd36a709e456e521c539d44ce04c9
+size 31247
diff --git a/marked/Rel-18/22_series/22855/fcd0701b8435792250492247750dd33c_img.jpg b/marked/Rel-18/22_series/22855/fcd0701b8435792250492247750dd33c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2d6303e5fac3bdbbbfa649add4082d02d39ddfb9
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/fcd0701b8435792250492247750dd33c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa3ce93b1ff7cc7804a5e4a4149b0bcf98c8c89e472cf129174833925b6ccf02
+size 4012
diff --git a/marked/Rel-18/22_series/22855/raw.md b/marked/Rel-18/22_series/22855/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..595781bb259ebca5e1b5e7a2071d7880437aa384
--- /dev/null
+++ b/marked/Rel-18/22_series/22855/raw.md
@@ -0,0 +1,1831 @@
+
+
+# 3GPP TR 22.855 V18.0.1 (2021-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Ranging-based Services (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above it and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'G' is a red signal wave icon. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+Fifth generation, 5G, Ranging, use cases
+
+---
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+---
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-----------------------------------------------------------------------------------|----|
+| Foreword ..... | 7 |
+| 1 Scope..... | 8 |
+| 2 References..... | 8 |
+| 3 Definitions, symbols and abbreviations..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 9 |
+| 4 Overview..... | 9 |
+| 5 Use cases..... | 10 |
+| 5.1 Distance based Smart Home Device Control..... | 10 |
+| 5.1.1 Description ..... | 10 |
+| 5.1.2 Pre-conditions..... | 11 |
+| 5.1.3 Service Flows ..... | 11 |
+| 5.1.4 Post-conditions ..... | 12 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 12 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 12 |
+| 5.2 Smart Home TV control..... | 12 |
+| 5.2.1 Description ..... | 12 |
+| 5.2.2 Pre-conditions..... | 13 |
+| 5.2.3 Service Flows ..... | 14 |
+| 5.2.4 Post-conditions ..... | 14 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 14 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.3 Smart Vehicle Key ..... | 15 |
+| 5.3.1 Description ..... | 15 |
+| 5.3.2 Pre-conditions..... | 16 |
+| 5.3.3 Service Flows ..... | 16 |
+| 5.3.4 Post-conditions ..... | 17 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 17 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 17 |
+| 5.4 Finding items in a Supermarket ..... | 17 |
+| 5.4.1 Description ..... | 17 |
+| 5.4.2 Pre-conditions..... | 19 |
+| 5.4.3 Service Flows ..... | 20 |
+| 5.4.4 Post-conditions ..... | 20 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 20 |
+| 5.5 Museum Tour ..... | 21 |
+| 5.5.1 Description ..... | 21 |
+| 5.5.2 Pre-conditions..... | 21 |
+| 5.5.3 Service Flows ..... | 21 |
+| 5.5.4 Post-conditions ..... | 21 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 21 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 22 |
+| 5.6 Touchless Self-checkout Machine Control ..... | 22 |
+| 5.6.1 Description ..... | 22 |
+| 5.6.2 Pre-conditions..... | 23 |
+| 5.6.3 Service Flows ..... | 23 |
+| 5.6.4 Post-conditions ..... | 23 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 23 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 23 |
+| 5.7 Hands Free Access ..... | 24 |
+| 5.7.1 Description ..... | 24 |
+| 5.7.2 Pre-conditions..... | 24 |
+| 5.7.3 Service Flows ..... | 25 |
+| 5.7.4 Post-conditions ..... | 25 |
+
+| | | |
+|--------|-----------------------------------------------------------------------------|----|
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 25 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 25 |
+| 5.8 | Smart Transportation Metro/Bus Validation..... | 25 |
+| 5.8.1 | Description ..... | 25 |
+| 5.8.2 | Pre-conditions..... | 26 |
+| 5.8.3 | Service Flows ..... | 26 |
+| 5.8.4 | Post-conditions ..... | 27 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 27 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 27 |
+| 5.9 | Distance based Intelligent Perception for Public Safety ..... | 28 |
+| 5.9.1 | Description ..... | 28 |
+| 5.9.2 | Pre-conditions..... | 28 |
+| 5.9.3 | Service Flows ..... | 28 |
+| 5.9.4 | Post-conditions ..... | 28 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 28 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 28 |
+| 5.10 | Picture and video sharing based on ranging results ..... | 29 |
+| 5.10.1 | Description ..... | 29 |
+| 5.10.2 | Pre-conditions..... | 29 |
+| 5.10.3 | Service Flows ..... | 30 |
+| 5.10.4 | Post-conditions ..... | 31 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 31 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 31 |
+| 5.11 | Ranging of UE's in front of vending machine ..... | 31 |
+| 5.11.1 | Description ..... | 31 |
+| 5.11.2 | Pre-conditions..... | 31 |
+| 5.11.3 | Service Flows ..... | 31 |
+| 5.11.4 | Post-conditions ..... | 32 |
+| 5.11.5 | Existing features partly or fully covering the use case functionality ..... | 32 |
+| 5.11.6 | Potential New Requirements needed to support the use case..... | 32 |
+| 5.12 | Finding pets in a long distance based on energy efficient Ranging..... | 32 |
+| 5.12.1 | Description ..... | 32 |
+| 5.12.2 | Pre-conditions..... | 33 |
+| 5.12.3 | Service Flows ..... | 34 |
+| 5.12.4 | Post-conditions ..... | 34 |
+| 5.12.5 | Existing features partly or fully covering the use case functionality ..... | 34 |
+| 5.12.6 | Potential New Requirements needed to support the use case..... | 35 |
+| 5.13 | Power efficient Ranging Operation..... | 35 |
+| 5.13.1 | Description ..... | 35 |
+| 5.13.2 | Pre-conditions..... | 36 |
+| 5.13.3 | Service Flows ..... | 36 |
+| 5.13.4 | Post-conditions ..... | 37 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 37 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 37 |
+| 5.14 | Finding and Tracking Objects..... | 37 |
+| 5.14.1 | Description ..... | 37 |
+| 5.14.2 | Pre-conditions..... | 37 |
+| 5.14.3 | Service Flows ..... | 37 |
+| 5.14.4 | Post-conditions ..... | 38 |
+| 5.14.5 | Existing features partly or fully covering the use case functionality ..... | 38 |
+| 5.14.6 | Potential New Requirements needed to support the use case..... | 38 |
+| 5.15 | Clustering of devices..... | 38 |
+| 5.15.1 | Description ..... | 38 |
+| 5.15.2 | Pre-conditions..... | 39 |
+| 5.15.3 | Service Flows ..... | 40 |
+| 5.15.4 | Post-conditions ..... | 40 |
+| 5.15.5 | Existing features partly or fully covering the use case functionality ..... | 40 |
+| 5.15.6 | Potential New Requirements needed to support the use case..... | 40 |
+| 5.16 | Tracking of devices..... | 41 |
+| 5.16.1 | Description ..... | 41 |
+| 5.16.2 | Pre-conditions..... | 41 |
+| 5.16.3 | Service Flows ..... | 41 |
+
+| | | |
+|-----------------|-----------------------------------------------------------------------------|-----------|
+| 5.16.4 | Post-conditions ..... | 42 |
+| 5.16.5 | Existing features partly or fully covering the use case functionality ..... | 42 |
+| 5.16.6 | Potential New Requirements needed to support the use case..... | 42 |
+| 5.17 | Immersive sound based on multiple-UE ranging..... | 42 |
+| 5.17.1 | Description ..... | 42 |
+| 5.17.2 | Pre-conditions..... | 43 |
+| 5.17.3 | Service Flows ..... | 43 |
+| 5.17.4 | Post-conditions ..... | 44 |
+| 5.17.5 | Existing features partly or fully covering the use case functionality ..... | 44 |
+| 5.17.6 | Potential New Requirements needed to support the use case..... | 44 |
+| 5.18 | Remote Access Right Authorization..... | 44 |
+| 5.18.1 | Description ..... | 44 |
+| 5.18.2 | Pre-conditions..... | 45 |
+| 5.18.4 | Post-conditions ..... | 46 |
+| 5.18.5 | Existing features partly or fully covering the use case functionality ..... | 46 |
+| 5.18.6 | Potential New Requirements needed to support the use case..... | 46 |
+| 5.19 | Sharing Content to a Particular UE ..... | 46 |
+| 5.19.1 | Description ..... | 46 |
+| 5.19.2 | Pre-conditions..... | 47 |
+| 5.19.3 | Service Flows ..... | 47 |
+| 5.19.4 | Post-conditions ..... | 47 |
+| 5.19.5 | Existing features partly or fully covering the use case functionality ..... | 48 |
+| 5.19.6 | Potential New Requirements needed to support the use case..... | 48 |
+| 6 | Consolidated requirements..... | 48 |
+| 6.1 | Functional requirements..... | 48 |
+| 6.2 | Performance requirements..... | 49 |
+| 7 | Conclusions and recommendations..... | 50 |
+| Annex A: | Ranging accuracy ..... | 50 |
+| Annex B: | Consideration for reference of measurement ..... | 50 |
+| Annex C: | Changing Coordinates..... | 51 |
+| Annex D: | Change history ..... | 53 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document provides Stage 1 potential 5G service requirements for ranging based services. In the context of the present document, Ranging-based services are to be understood as the applications utilizing the distance between two UEs and/or the direction of one UE from the other one.
+
+The aspects addressed in the present document include:
+
+- Identify Use cases and potential requirements of ranging-based services directly between two or more UEs, e.g. accuracy of distance and direction, maximum range distance, ranging latency, energy/battery consumption.
+- Gap analysis with existing mechanisms to enable ranging-based services.
+
+NOTE: the study does not intend to address V2X specific use cases and requirements.
+
+# 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] .
+
+[3] [http://www.chnmuseum.cn/zx/gbxw/201802/t20180220\\_1967.shtml](http://www.chnmuseum.cn/zx/gbxw/201802/t20180220_1967.shtml).
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+Key performance indicators and key attributes for Ranging use cases are defined as follows:
+
+**Ranging accuracy:** describes the absolute value of the deviation of the measured distance and/or direction between two UEs to the true distance and/or direction value.
+
+**Confidence level:** describes the percentage of all the possible measured distance and/or direction that can be expected to include the true distance and/or direction considering the Ranging accuracy.
+
+**Effective Ranging distance:** the largest distance between the UE who initiates the Ranging and target UEs in the Ranging operation.
+
+**Environment of use:** the physical environment between the UE who initiate the Ranging and target UEs, such as LOS environment and NLOS environment. Also the physical environments of the UE who initiate ranging, such as in coverage and out of coverage.
+
+**Relative UE velocity:** the target UE can be either static or mobile relative to the UE who initiates the Ranging. In the latter, the attribute shall also provide some elements about its motion, e.g. maximum speed, trajectory.
+
+**Availability:** percentage value of the amount of time when a ranging system is able to provide the required Ranging-related data within the performance targets or requirements divided by the amount of time the system is expected to provide the Ranging service in a targeted service area.
+
+**Latency:** time elapsed between the event that triggers the determination of the Ranging-related data and the availability of the Ranging-related data at the Ranging system interface.
+
+**Power consumption:** electrical power used by Ranging during Ranging operation.
+
+**Ranging interval:** time difference between two consecutive Ranging operations.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+
+
+# 4 Overview
+
+Ranging service (or Ranging in short) in this document refers to the determination of the distance between two UEs and/or the direction of one UE from the other one via direct communication connection. As shown in the following celestial coordinate, the horizontal direction (i.e. the Azimuth) of the target UE is the angle formed between a reference direction and a line from the observer UE to target UE projected on the same plane as the reference direction orthogonal to the zenith. The elevation direction of the target UE is the angle above the horizontal plane [2].
+
+
+
+Figure 4-1: Illustration of horizontal/ elevation direction in celestial coordinate. The diagram shows a sphere with an 'Observer UE' at the 'Origin' (center). A vertical dashed line points to the 'Zenith' at the top. A horizontal dashed line points to the 'Reference direction' on the right. A solid line connects the Origin to a 'Target UE' on the sphere's surface. The angle between the horizontal plane and this line is labeled 'Elevation'. The angle between the reference direction and the projection of the Target UE onto the horizontal plane is labeled 'Azimuth'.
+
+**Figure 4-1 illustration of horizontal/ elevation direction in celestial coordinate**
+
+For better understanding, Ranging in 2D coordinate system is taken as an example in Fig.4-2, where UE1 initiates the ranging operation and the coordinate system is centered at UE1. Furthermore, y-axis is the UE1's pointing direction (reference direction). The ranging initiated by UE1 targets at knowing the distance of UE2 and UE3 to UE1 and also the direction (reference direction) of UE2 and UE3 relatively to UE1.
+
+As illustrated in Fig.4-2, at $T=t1$ UE2 is located at the 2-o'clock direction to UE1 with the direction information as $\theta_1 = 30^\circ$ and distance as $d_1$ . UE3 is located at the 9-o'clock direction to UE1 with the direction information as $\theta_2 = -90^\circ$
+
+and distance as $d_2$ . When the UE1 switches its pointing direction to UE2 at $T=t_2$ , the ranging results of UE2 change to $\theta_1' = 0^\circ$ and distance remains as $d_1$ , while the ranging results of UE3 change to $\theta_2' = -120^\circ$ and distance remains as $d_2$ .
+
+
+
+Figure 4-2: Example of ranging (from T=t1 to T=t2). (a) T=t1: UE1 is at the origin of an x-y coordinate system. UE2 is at distance d1 and angle theta1. UE3 is at distance d2 and angle theta2. (b) T=t2: UE1 has rotated. UE2 is now at angle theta1' = 0 degrees and distance d1. UE3 is at angle theta2' = -120 degrees and distance d2.
+
+Figure 4-2 Example of ranging (from $T=t_1$ to $T=t_2$ )
+
+Ranging service can be supported with or without 5G coverage. Fig. 4-3 is an illustration of 5G providing ranging service to UEs with or without 5G coverage. If licensed band is used for ranging, it shall be fully under operator control.
+
+
+
+Figure 4-3: Illustration of 5G providing ranging service to UEs with or without 5G coverage. The figure shows three scenarios: 'In 5G coverage' where both UE1 and UE2 are within the 5G signal range of a base station; 'Partial 5G coverage' where UE1 is in coverage and UE2 is out; and 'Out of 5G coverage' where both UE1 and UE2 are outside the base station's range. In all cases, a 'distance/direction' measurement is indicated between UE1 and UE2.
+
+Figure 4-3 illustration of 5G providing ranging service to UEs with or without 5G coverage
+
+# 5 Use cases
+
+## 5.1 Distance based Smart Home Device Control
+
+### 5.1.1 Description
+
+Smart speaker has been playing a more and more important role in smart home. People tends to use smart speaker to control smart devices given its convenience, especially for simple interactions, such as turn on TV/light.
+
+In a typical smart home scenario, there might be tens of smart devices, many of which may be with the same type. For example, people may have 5-10 smart lights, 2-3 smart TVs, etc. As a consequence, user has to tell the smart speaker which device he or she intends to control. Often, it requires user to give a different name for the devices. To make things worse, user may have multiple smart speakers in different rooms to be able to pick up user's voice, then the system may even not know which smart speaker to respond to user's voice. Ranging capable devices can simplify the interaction: with distance aware, the smart home system can automatically choose the one closest to the user to control. Distance accuracy plays an important role in this automatic device selection. If wrong device is selected due to distance
+
+error, user experience will be badly degraded. In a typical 3m\*4m bedroom, average distance between user and the smart device is 2 meter. If user intends to control a device based the distance, he/she needs to have enough confidence on which device is closer. On average, people can confidently tell the closer one if distance difference is more than 10-30% of distance, which corresponding to 0.2m~0.6m distance difference, and 0.1m~0.3m distance accuracy.
+
+Service latency is another important factor to consider. The following figure shows an example service flow for distance-based device control with smart speaker:
+
+
+
+```
+
+ graph TD
+ subgraph Room1
+ SS[Smart speaker]
+ RCD[Ranging capable device on user]
+ LA[Light A]
+ LB[Light B]
+ SS -- "3. Device command" --> RCD
+ RCD -- "4. ranging procedure" --> LA
+ RCD -- "5. Device response" --> SS
+ SS -- "6. Light control command" --> LB
+ end
+ RCD <--> |"1. voice data (RTT = 50~70ms)"| Cloud[Cloud: speech recognition and semantics understanding (average 500ms)]
+ Cloud -- "2. control command with list of potential target devices" --> SS
+ Note[3+5+6 take 400ms]
+
+```
+
+Figure 5.1.1-1: Example of distance based smart device control using smart speaker. The diagram shows a 'Room1' containing a 'Smart speaker', a 'Ranging capable device on user', 'Light A', and 'Light B'. Outside the room is a 'Cloud' for speech recognition. The flow is: 1. voice data (RTT = 50~70ms) from user to Cloud; 2. control command with list of potential target devices from Cloud to Smart speaker; 3. Device command from Smart speaker to Ranging capable device; 4. ranging procedure between Ranging capable device and Light A; 5. Device response from Ranging capable device to Smart speaker; 6. Light control command from Smart speaker to Light B. A note indicates steps 3+5+6 take 400ms.
+
+**Figure 5.1.1-1 Example of distance based smart device control using smart speaker**
+
+In the figure above, user instructs the smart speaker to turn on the light. For light control, typically around 1 second latency from user giving the voice instruction to the light being turned on/off is satisfying to user. The speech recognition and semantics understanding is usually handled in the cloud and takes on average 500ms for processing and takes on average 60ms for round trip transmission. One message exchange between smart speaker and other smart devices would consume around 130ms. Therefore message 3+5+6 would take about 390ms. Then, the budget for ranging service would be around 50ms. Besides, due to user movement, service latency should also ensure that the acquired ranging result is still valid. For 1m/s movement, 50ms latency would result in 5cm distance change. Then service latency below 50ms should be ensured to keep the validity of ranging result. To reduce the response latency of smart device, it might be sometimes useful that ranging is performed in advance, e.g. before UE giving the voice instruction (e.g. when UE arouses the smart speaker) if power consumption is less a concern. In this case, UE may need to perform ranging with all the smart devices around the UE. Typically, there might be no more than 20 smart devices within LOS distance.
+
+### 5.1.2 Pre-conditions
+
+There are many smart Ranging enabled devices in Alice's home, including:
+
+- Smart TV-1, smart light A and B, smart speaker A are in bedroom
+- Smart TV-2, smart light C, D and E, smart speaker B are in living room
+
+Alice wears a smart Ranging enabled watch.
+
+The smart home devices are capable of determining the range of Alice's wearable device.
+
+The smart speaker is capable of recognizing Alice's voice and identify her.
+
+### 5.1.3 Service Flows
+
+Alice enters the door of her house;
+
+Alice's smart watch discovers smart TV-1/TV-2, smart speaker A/B, smart light A/B/C/D;
+
+Ranging is performed between the wearable device and the discovered smart speakers;
+
+The nearest smart speaker is chosen as the responder speaker for Alice;
+
+When Alice is moving in the house, responder speaker is updated based on the latest ranging results;
+
+Alice enters the bedroom, and would like to turn on the nearest light in the bedroom;
+
+Alice arouse the smart speaker and tell it to turn on the light;
+
+The responder speaker responds, and the light nearest to the user is switched on.
+
+### 5.1.4 Post-conditions
+
+Alice's smart home system always knows which smart speaker to respond to Alice, and knows which smart device is closest to Alice, and thus being able to respond to Alice's command by choosing the nearest device if multiple of the same type devices exist and user doesn't tell which one to control.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.1.6-1] The 5G system shall be able to support Ranging enabled UEs to discover other Ranging enabled UEs.
+
+[PR 5.1.6-2] The 5G system shall be able to provide ranging service with following KPIs:
+
+**Table 5.1.6-1 – KPIs for distance based smart home control**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|-------------------------------------|---------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------|---------------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| Distance based smart device control | 10cm | - | 99 % | 50ms | 20m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 50ms | 20 | - |
+
+## 5.2 Smart Home TV control
+
+### 5.2.1 Description
+
+Smart TVs, much like smartphones and smart home devices, offer internet connectivity and support for a range of apps. It typically provides an interactive interface, allowing users to stream on-demand music and videos, browse the internet, access to OTT content and online interactive media, etc.
+
+In smart home scenario, smart TV is one of the most popular devices that people would heavily interact with. Traditional TV remoter is less convenient in control of smart TV, where the interactive interface includes many elements to choose and control. Ranging capable remoter can make the control of smart TV easier. An illustration of smart TV control using remoter is shown in Fig 5.2.1-1. In the figure, a1 and b1 are the horizontal direction and elevation direction of remoter from TV reference point as an observer. d is the distance between the TV reference point
+
+ant remoter. $a2$ and $b2$ are the horizontal direction and elevation direction of TV reference point from remoter as an observer. The TV reference point location in the TV coordinate system is known, the location of remoter relative to the TV reference point can be calculated based $a1$ , $b1$ and $d$ . The position on TV where the remoter is pointed can be calculated based on $a2$ , $b2$ and the location of remoter.
+
+
+
+Figure 5.2.1-1: Illustration of smart TV control based on remoter direction. The diagram shows a TV screen with a 'TV reference point' at the top center. Below it are two rows of content: the top row contains 'content 1' through 'content 6', and the bottom row contains three larger 'content 1' blocks. A 'Remoter' is shown at the bottom, with dashed lines indicating its pointing direction. One dashed line points to 'content 3' in the top row, labeled with angles 'a1' and 'b1', and distance 'd'. Another dashed line points to 'content 4' in the top row, labeled with angles 'a2' and 'b2'.
+
+**Figure 5.2.1-1 Illustration of smart TV control based on remoter direction**
+
+Both distance error and direction error would contribute to the error of estimated point on TV that the remote points at. From user point of view, what matters is the angle between the line from estimated point to the TV remote and the line from the TV remote to the actual point that TV remote points at, which is considered as angle error. The smaller the angle error, the better. The tolerable angle error is related to the direction range of the TV remote, i.e. the angle (call it $\alpha$ in the following discussion) between the line from the left side of the TV to the TV remote and the line from the TV remote to the right side of TV. Taking a 50 inch TV (110cm \* 62 cm) as an example, the typical viewing distance is 3 meter. The angle $\alpha$ is about 20 degree. We can consider 10% of angle $\alpha$ as tolerable angle error, that is 2 degree, and it corresponds to 10 cm distance error (3 meter \* $\tan(2)$ ).
+
+Due to the fast TV remote movement, distance and direction need to be measured with very low service latency. For 1m/s movement, the time for the mouse cursor on TV to move from left side to right side is on average 200ms for the case of 50 inch TV and 3 meter viewing distance. 10ms service latency would correspond to 5cm movement on TV. The distance and direction measurement result would also need to be updated frequently to trace the TV remote movement, 50ms ranging interval will provide a fine granularity for capturing TV remote movement.
+
+### 5.2.2 Pre-conditions
+
+Mary has a smart Ranging enabled TV and a Ranging enabled TV remoter.
+
+The smart Ranging enabled TV and The Ranging enabled TV remoter are in Mary' s living room.
+
+### 5.2.3 Service Flows
+
+Mary turns on the smart TV using the TV remoter;
+
+Smart TV shows an interactive interface for user to interact with;
+
+Smart TV shows the cursor on the interactive interface; the position of the cursor is where the TV remoter is pointing at;
+
+Mary points the TV remoter at a different position on the interactive interface, the cursor moves to that position accordingly;
+
+When Mary presses the OK button on the TV remoter, the element under the cursor is selected and clicked.
+
+### 5.2.4 Post-conditions
+
+Mary's smart TV responds to the click operation by e.g. entering a specific page corresponding to the clicked element.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.2.6-1] The 5G system shall be able to authorize Ranging for each individual UE.
+
+[PR 5.2.6-2] The 5G system shall be able to ensure that the use of ranging, if in licensed spectrum, is only permitted in network coverage under the full control of the operator who provides the coverage.
+
+[PR 5.2.6-3] The 5G system shall be able to provide ranging service with following KPIs:
+
+**Table 5.2.6-1 – KPIs for smart home TV control**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|------------------|---------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|----------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| | | | | | | | | | | | |
+
+| | | | | | | | | | | | |
+|-------------------------------------|-------------------------------|------------------------------------------------------------------------------------------------------|------|------|-----|-----------|-----|-----------------------|------|---|---|
+| Distance based smart device control | 10cm up to 3 meter separation | ±2° horizontal direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-60°) to (+60°); | 99 % | 10ms | 10m | IC/PC/OOC | LOS | Static/Moving (<1m/s) | 50ms | - | - |
+| | | ±2° Elevation direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-45°) to (+45°) | | | | | | | | | |
+
+## 5.3 Smart Vehicle Key
+
+### 5.3.1 Description
+
+The smart key allows the driver to keep the key pocketed when unlocking, locking and starting the vehicle. Vehicles with a smart-key system can distinguish whether the user carrying the key is approaching or not. When the key is approaching to the vehicle, it will be automatically unlocked; when the key is in the vehicle, the vehicle can be automatically started; when the key moving away from the vehicle, the vehicle will be automatically locked.
+
+In this case it is assumed that a standard parking slot is about 40 m2, and a parking place of 104 m2 can support 250 vehicles. We assume 20% of all the vehicles need ranging service at the same time of rush hour. So, the number of concurrent ranging operation in this parking place should be 50.
+
+In lock and unlock scenario, user's experience and security issues need to be balanced. There are several requirements need to be considered:
+
+- 1) The vehicle should be unlocked and keep unlocked, when the UE is within a certain distance (e.g., 1 meter) to any door of the vehicle. So that user can get friendly experience.
+- 2) The vehicle should be locked and keep locked, when the UE is out of a certain distance to all doors (e.g., 3 meters). So that the vehicle can keep safe.
+- 3) The vehicle should keep the same status, when the UE moves to a certain distance range (e.g., from 1 meter to 3 meters) to the closest door, in case the vehicle switches status to often.
+
+Above requirements need Ranging service to detect the smart key's position and measure the distance of 1 meter accurately, which need a distance accuracy of lower by one order of magnitude than 1 meter, i.e., 10 cm.
+
+Ranging interval should ensure that the measured result is still valid (with sufficient accuracy) during this period when user moves. For 2m/s user movement, 25ms ranging interval corresponds to 5cm distance change, which is acceptable for 10cm distance accuracy.
+
+Latency of 50 ms is needed to achieve 10 cm distance accuracy when the UE is moving at 2 m/s.
+
+In extreme cases, a vehicle can be 10 meters long, and the ranging service need to measure 10 meters to the vehicle. Considering the ranging application needs at least 5 seconds to get ready to unlock the car, the ranging service should
+
+be active 10 meters before the user arrive at the unlock point, if he is running at 2 m/s. So, the total active ranging service distance should be 30 meters.
+
+99% availability will ensure a user-friendly experience for predicting moving UE's position.
+
+### 5.3.2 Pre-conditions
+
+Alice's car, Bill's car and Jack's car are supporting for the smart key system, and are Ranging enabled.
+
+Alice' and Jack's smart phone are set as the smart key for her/his vehicle.
+
+Bill's smart watch is set as the smart key for his vehicle.
+
+The smart key is paired to the specific car (for Alice, Bill and Jack)
+
+There are hundreds of cars parked in the parking area in front of the shopping mall.
+
+### 5.3.3 Service Flows
+
+A typical service flow is as following:
+
+
+
+The diagram illustrates a use case for a smart vehicle key system. At the top, a large orange rectangle represents a 'Shopping Mall'. Below it is a parking lot grid. UE1 (Alice) is shown walking out of the mall. UE2 (Bill) is shown walking towards a car labeled 'Bill's Car'. A callout for Jack indicates he is closing to his car with his smart phone. Another callout identifies 'Alice's Car'. The parking lot contains various cars in different colors (blue, red, yellow, white). There are 'P' signs at the ends of the parking area.
+
+Figure 5.3.3-1 use case for the smart vehicle key. The diagram shows a 'Shopping Mall' at the top. Below it is a parking lot with a grid of cars. UE1 (Alice) is walking out of the mall. UE2 (Bill) is walking towards his car. A callout for Jack indicates he is closing to his car with his smart phone. Callouts also identify 'Alice's Car' and 'Bill's Car'.
+
+Figure 5.3.3-1 use case for the smart vehicle key
+
+- For unlock case:
+
+Alice is walking out of the Shopping mall with her smart phone. Alice's car discovers the Alice's smart phone
+
+Alice's car connects to Alice's smart phone after successful authentication and authorization between them.
+
+Alice is walking towards to her car based on the location information provided on her smart phone.
+
+The car is unlocked when it detects Alice has approached within certain distance (e.g., 1 meter)
+
+- For lock case:
+
+Bill stops his car in the parking spot.
+
+Bill is walking out of his car with his smart watch and moving away from his car.
+
+The car is locked when it detects Bill has got out of a certain distance (e.g., 3 meters).
+
+- For engine start case:
+
+(Assuming that Jack's car is already connecting to Jack's smart phone)
+
+Jack is approaching to his car within certain distance (e.g., 1meter)
+
+Jack's car is unlocked
+
+Jack is getting closer to his car within e.g., 0.5meter or Jack is getting into his car.
+
+### 5.3.4 Post-conditions
+
+Alice's car is unlocked automatically when she is approaching to her car within certain distance, e.g., 2meters.
+
+Bill's car is locked automatically when he is moving away from his car more that certain distance, e.g., 2meters
+
+The engine of Jack's car is started automatically when he is getting into the car or he is 0.5meter away from the car.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR 5.3.6-1] The 5G system shall be able to protect privacy of a UE and its user, ensuring that no identifiable information can be tracked by undesired entities during Ranging.
+
+**Table 5.3.6-1 – KPIs for smart vehicle key**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|-------------------|---------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|--------------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| Smart Vehicle Key | 10cm | - | 99 % | 50ms | 30m | IC/PC/OC | - | Static/Moving
(<2m/s) | 25ms | - | [50]UEs/
(10 4 m 2 ) |
+
+## 5.4 Finding items in a Supermarket
+
+### 5.4.1 Description
+
+Most supermarkets are large and have an extensive product range which makes it difficult for customers to find their desired items straightaway. Customers regularly take detours inside the store in order to find a particular product.
+
+Customers can download a mobile app which can help them to seek desired items in a supermarket. The mobile app can show the distance and direction between the mobile phone and the desired items. And thus, the customer can always take the best and shortest route to their desired items.
+
+It is assumed that:
+
+- Ranging distance is 100m. So, the coverage that a user/UE performing Ranging service is a circle with 100m radius ( $S_1 = 3.14 \times 10^4 \text{ m}^2$ ).
+
+- Shelves in supermarket are 50 cm wide.
+
+To ensure the user to find the right aisle of the desired item, the distance accuracy of the ranging service would be 50 cm, which is shown in figure below:
+
+
+
+The diagram shows three blue rectangular shelves with orange outlines, labeled 'Shelves' in blue text. The gaps between the shelves are labeled 'Aisles' in orange text. A person named 'Alice' is shown walking towards the shelves, carrying a bag and holding a device labeled 'UE'. A green line represents the 'real position of a tag(UE)', starting from a green dot on the middle shelf and ending at the UE. A yellow line represents the 'wrong position of the tag(UE)', starting from a yellow dot on the same shelf and ending at the UE. A blue double-headed arrow at the bottom indicates a distance of '50cm' between the real and wrong positions.
+
+Diagram illustrating distance accuracy for a ranging service in a supermarket aisle.
+
+**Figure 5.4.1-1: distance accuracy should ensure the user to find the right aisle**
+
+It's assumed that the shelves are 50 cm( $d$ ) wide and the item is 5 meters away from Alice. If the direction mistake is larger than $5.73$ degree ( $d/r * 180/\pi$ ), Ranging service would guide to a wrong aisle. So, the direction accuracy of the ranging service would be 5 degree, which is shown below:
+
+
+
+The diagram shows a top-down view of a supermarket layout. Three blue rectangular blocks represent 'Shelves', and two orange lines represent 'Aisles'. A user named 'Alice' is at the bottom, holding a 'UE' (User Equipment). A green dashed line, representing the 'real position of a tag(UE)', points from Alice to the middle aisle. A yellow dashed line, representing the 'wrong position of the tag(UE)', points from Alice to the right aisle. The distance between the shelves is labeled as 50cm. The distance from the UE to the shelves is labeled as 5m. The angle between the real and wrong positions is labeled as 5.73°. A legend in the top right corner identifies the green dot as the 'real position of a tag(UE)' and the yellow dot as the 'wrong position of the tag(UE)'.
+
+Diagram illustrating direction accuracy for finding the right aisle in a supermarket. A user named Alice is shown at the bottom, holding a UE. A green dashed line represents the 'real position of a tag(UE)' leading to the correct aisle, while a yellow dashed line represents the 'wrong position of the tag(UE)'. The diagram shows three shelves (blue) and two aisles (orange). The distance between shelves is 50cm, and the distance from the UE to the shelves is 5m. The angle between the real and wrong positions is 5.73°.
+
+**Figure 5.4.1-2: direction accuracy should ensure the user to find the right aisle**
+
+The time budget would be 500 ms to ensure 1 second total latency, because the application needs 500 ms to show the information on the UE.
+
+Ranging interval should ensure that the measured result is still valid (with sufficient accuracy) during this period when user moves. For 1m/s user movement 250ms ranging interval corresponds 25cm distance change, which is acceptable for 50cm distance accuracy.
+
+95% availability will ensure a user-friendly experience for Finding items in a Supermarket.
+
+A ranging service area of a supermarket can support 500 people at the same time. We suppose 20% of them need ranging service. There would be 100 UEs using Ranging service at the same time.
+
+### 5.4.2 Pre-conditions
+
+The shelf in area E carried the M-watch is tagged with tracker UE in the supermarket.
+
+A mobile app is installed on Alice's smart phone.
+
+Tracker UEs and the smart phone are Ranging enabled.
+
+### 5.4.3 Service Flows
+
+
+
+Diagram of a supermarket use case for ranging. Alice, represented by a person icon, is walking into the supermarket through an entrance. She is holding a UE (User Equipment). A dashed line with an arrow points from Alice to a watch icon in area E, indicating the direction and distance (d) to the watch. An angle theta is shown between the entrance and the direction to the watch. A speech bubble from Alice says 'Where is M-watch?'. The supermarket is divided into several areas: area C, area D, area E, area F, area G, area H, area I, area J, and area K. The entrance is at the bottom center.
+
+**Figure 5.4.3-1 use case for supermarket**
+
+Alice is walking into the supermarket with her smart phone. Alice opens the mobile app and search for the M-watch.
+
+Alice’s smart phone performs Ranging service and discovers the watch when Alice press the "find the item" button once the watch is found on the app.
+
+The smart phone keeps showing the distance and direction from Alice’s smart phone to the watch when she moves.
+
+### 5.4.4 Post-conditions
+
+Alice finds the M-watch as fast as possible according to the direction and distance information presented on the phone.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+**Table 5.4.6-1 – KPIs for finding items in a supermarket**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|------------------|---------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|----------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| | | | | | | | | | | | |
+
+| | | | | | | | | | | | |
+|--------------------------------|-------|----------|------|-------|------|----------|---|-----------------------|-------|---|-----------------------------------------------|
+| Finding Items in a supermarket | 50 cm | 5 degree | 95 % | 500ms | 100m | IC/PC/OC | - | Static/Moving (<1m/s) | 250ms | - | 100 UEs/
( $3.14 \times 10^4 \text{m}^2$ ) |
+|--------------------------------|-------|----------|------|-------|------|----------|---|-----------------------|-------|---|-----------------------------------------------|
+
+## 5.5 Museum Tour
+
+### 5.5.1 Description
+
+According to the visitor data report of National Museum of China (2017) [3], National Museum of China received totally 8,062,625 visitors in 2017, with an average of 26,000 visitors a day. The number of visitors reached a peak on China's National day, which was 47,431. Given the National Museum of China opens 8 hours per day, from 9:00 to 17:00, it can be assumed that every minute of the peak day there were nearly 100 visitors who entered the museum and stood in front of the same significant exhibit almost at the same time.
+
+Regarding to museum tour, users always hope to get further information about the exhibits automatically so as to have a better understanding of them. Nowadays, the media types of museum interpretation can be various not limited to traditional audio. If users/UEs can be discovered and identified based on the distance and direction angle when passing through exhibits, and then get audio/video or even interaction from the specific exhibit according to the service policy, users will feel like there is a real tour guide around and definitely have a better experience.
+
+### 5.5.2 Pre-conditions
+
+There are a lot of valuable exhibits in the museum, each of which has a ranging capable device nearby.
+
+Tom has a ranging capable UE (UE A).
+
+There are also many tour groups in the museum. They are all equipped with ranging capable UEs too.
+
+### 5.5.3 Service Flows
+
+1. Tom is visiting the museum with UE A.
+2. When Tom comes to a famous exhibit, UE A discovers the ranging capable device (Device B) nearby based on a certain distance and angle between the device and UE A.
+3. UE A connects to Device B.
+4. Device B identifies UE A, and then pushes the introduction audio/video of the exhibit to which Tom is standing and facing in real time.
+5. Tom keeps listening/watching the pushed media carefully, while a group of people are coming to the same exhibit.
+6. All the ranging capable UEs of the tour group connect to Device B.
+7. Device B discovers the tour group UEs and then performs the identification of the UEs belong to them.
+8. Device B starts multicasting introduction media to the tour group again, while Tom is still listening/watching his media smoothly without any interruption.
+9. Tom turns to another exhibit nearby after finished watching. Device B stops the media push to Tom.
+
+### 5.5.4 Post-conditions
+
+Tom and the tour group can automatically get the introduction of the exhibits they are interested. They all enjoy their museum tours.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR 5.5.6-1] The 5G system shall support identification of other ranging capable UE/UEs with which a ranging capable UE performs Ranging.
+
+[PR 5.5.6-2] The 5G system shall be able to support Ranging service between an initiating UE and up to 100 target UEs.
+
+## 5.6 Touchless Self-checkout Machine Control
+
+### 5.6.1 Description
+
+Currently, self-checkout machines could be found in almost every supermarket. If someone wants to use a self-checkout machine to pay for goods, he/she needs to click, slide or drag on the screen/keyboard to finish a series of control procedure until the payment is successful. However, because of the control device is a public device, it means that everyone can use it, so as to many people have to touch and use a same machine. This type of public touch mode would be risky, especially during the outbreak of a pandemic. For example, if an infected user leaves virus that may cause disease on a self-checkout machine through touching, then there would be a great health risk for subsequent users who may touch the public control device.
+
+To deal with this problem, self-devices such as mobile phones could be utilized to obtain the control authority from a public device, e.g. a public self-checkout machine, and perform interactive operations to indirectly control the public device, as shown in Fig 5.6.1-1.
+
+
+
+The image illustrates a touchless self-checkout machine control use case. On the left, a self-checkout machine's touchscreen displays a green smartphone icon and four orange buttons labeled 'Casually stroll', 'Barcode query', 'Purchase', and 'Return'. On the right, a hand holds a physical smartphone that displays a similar interface with the same four options in a list. This visualizes the process where a user's personal device (UE) obtains control authority over the public self-checkout machine's interface.
+
+Illustration of touchless self-checkout machine control Use Case. The image shows a self-checkout machine screen displaying a smartphone and options: 'Casually stroll', 'Barcode query', 'Purchase', and 'Return'. A hand holds a smartphone displaying the same options, indicating control authority.
+
+**Figure 5.6.1-1 Illustration of touchless self-checkout machine control Use Case**
+
+In this case, UE needs to obtain an authority when it is close to a public self-checkout machine. So timely and reliable ranging would be required to trigger the authority procedure and to improve user experience. For example, when a UE finds there is a self-checkout machine nearby (already within an authority area of a public self-checkout machine, e.g. the distance between the UE and the machine is less than 1m), the UE can trigger a corresponding procedure to obtain the authority to get control interface and indirectly control the machine, as shown in Fig 5.6.1-2.
+
+
+
+Diagram illustrating the touchless self-checkout machine control Use Case. A 'Public self-checkout machine' is shown at the top. Below it, a 'UE' (User Equipment) is shown. A red arrow labeled 'Ranging' points from the UE to the machine. A green oval labeled 'Authority Area (to obtain the authority to control the public self-checkout machine)' encompasses both the UE and the machine.
+
+**Figure 5.6.1-2 Illustration of touchless self-checkout machine control Use Case**
+
+Given that people occasionally go to supermarkets, this type of Ranging service can be turned on and off on demand. For example, when a customer enters a supermarket, a touchless self-checkout service can be enabled. When the customer leaves the supermarket, the service is disabled. In this way, the unnecessary ranging service can be avoided and the power consumption of UE can be reduced.
+
+### 5.6.2 Pre-conditions
+
+A supermarket has a public self-checkout machine.
+
+A user does not want to click, slide or drag on the screen of the public self-checkout machine considering the health risk during a pandemic period.
+
+The user has a smartphone and wants to use the smartphone to control the self-checkout machine to finish the payment.
+
+### 5.6.3 Service Flows
+
+Dorina heads for a self-checkout machine in a supermarket.
+
+Dorina's smartphone is aware that there is a self-checkout machine nearby, i.e. the UE is in the authority area of a public self-checkout machine now.
+
+The UE triggers an authority procedure to obtain the authority from the self-checkout machine.
+
+The UE shows an interactive interface for Dorina to interact with.
+
+Dorina presses a button on the shown interface on her smartphone, e.g. "purchase", and corresponding purchase procedure then is triggered on the self-checkout machine accordingly.
+
+### 5.6.4 Post-conditions
+
+Dorina indirectly controls the self-checkout machine through her smartphone and finishes the payment.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR 5.6.6-1] The 5G system shall be able to enable or disable the Ranging service.
+
+[PR 5.6.6-2] The 5G system shall be able to provide ranging service with following KPIs:
+
+**Table 5.6.6-1 – KPIs for touchless self-checkout machine control**
+
+| Ranging scenario | Ranging Accuracy (95 % confidence level) | | Availability | Latency | Coverage, environment of use, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation support in area | | | | | | |
+|-----------------------------------------|------------------------------------------|--------------------|--------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------|-----------------------|------------------|-------------------------------------------------|--------------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation support in area |
+| touchless self-checkout machine control | 10 cm | - | 99% | 50 ms | 1m | IC/PC/OOC | LOS | Static/Moving (<1m/s) | 100ms | - | = |
+
+## 5.7 Hands Free Access
+
+### 5.7.1 Description
+
+Hands free access is a better alternative to manual operations, especially in some public area. On one hand, it avoids many touches on public facilities so that they can keep clean for a long time. On the other hand, auto and smooth mechanism is good for public facilities' life extension.
+
+For example, hands free access can be used for opening the door. Once user takes unlocking devices with built-in ranging module, such as smart phones, smart watches, etc. The door with ranging module can automatically unlock and open according to the distance between the user and the door. Door and unlocking devices are able to pair flexibly and support encrypted communication to protect the user's private information. Depending on the location of areas, such procedures happen indoor or outdoor, even underground.
+
+Furthermore, hands free access can help the company keep some employees away from its sensitive or private area. Only employees with privileges can enter by ranging procedures. Under the circumstances, the unlocking device shall provide its credential information to the door (e.g. username and password) first, then the door checks its validation locally (e.g. cache in the door) or remotely (e.g. database in company server).
+
+Considering the time needed from ranging discovery to application authorization, the ranging service need to discover the unlocking UE when it's 10 meters away from the door, to ensure to open the door when the user get 5 meters away from the door.
+
+Under the circumstances, ranging service needs check whether the user is very close to the door to open it, in case the employee just wants to pass by. For tuning the application to satisfy the users, 10 cm of distance accuracy is necessary.
+
+Considering the user can move at 1 m/s and the distance accuracy is 10 cm, the time budget would be 50 ms ( $10\text{cm} / (1\text{m/s}) = 100\text{ ms}$ ).
+
+Ranging interval should ensure that the measured result is still valid (with sufficient accuracy) during this period when user moves. For 1m/s user movement 50ms ranging interval corresponds 5cm distance change, which is acceptable for 10cm distance accuracy.
+
+99% availability will ensure a user-friendly experience for predicting moving UE's position.
+
+In office scenario, people always move at 1 m/s.
+
+It's assumed that users walk in a line from both sides of the door. The distance between every 2 UEs is 1 meter. So, here are 20 unlocking UEs in the ranging area.
+
+### 5.7.2 Pre-conditions
+
+UE A is a ranging capable unlocking device(e.g. a smart phone or a wearable device) installed company App .
+
+Tom is the owner of UE A and he is an employee of Company A.
+
+UE B is a ranging capable door. UE A and UE B are able to discover each other under 5G coverage.
+
+### 5.7.3 Service Flows
+
+1. Tom carrying UE A gets close to UE B under a particular speed (e.g. 1m/s).
+2. UE B discovers UE A.
+3. UE B estimates the distance between itself and UE A. If the distance meets the criteria (e.g. smaller than 5 meter), UE B start performing ranging with the door.
+4. When Tom gets closer to the door, the distance between UE A and the door meets the criteria (e.g. smaller than 0.5 meter),
+ - a. if Tom is authorized or no authorization needed, the door automatically unlocks and opens.
+ - b. if Tom is unauthorized, the door keeps closed and alarms Tom by audio equipment.
+
+### 5.7.4 Post-conditions
+
+Follow option a) in Step 4, Tom enters without manually opening the door.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+The interactions for authorization between the two UEs before Step 4 can be fully covered by existing sidelink or PC5 communications.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR 5.7.6-1] The 5G system shall be able to support for a UE to discover other UEs supporting Ranging.
+
+[PR 5.7.6-2] The 5G system shall be able to provide Ranging service with following performance KPIs.
+
+**Table 5.3.6-1 – KPIs for hands free access**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|-------------------|---------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|------------------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| Hands Free Access | 10cm | - | [99 %] | 100ms | 10 m | IC/PC/OC | - | Static/
Moving
(1 m/s) | 50ms | - | 20
UEs/3.14*100m 2 |
+
+## 5.8 Smart Transportation Metro/Bus Validation
+
+### 5.8.1 Description
+
+Nowadays, heavy passenger flow shock the current public transportation system. However, passengers have to actively touch the billing device using public transportation card, which is so slow at rush time that it is easy to meet congestion.
+
+This problem can be effectively solved through the hands free metro/bus validation. It determines whether the user gets on or off the bus according to the relative distance, and then provides the information about getting on or off the bus/metro to a billing node. The billing node automatically deducts the corresponding fee from the user's account.
+
+At rush time, crowd get close to an entrance simultaneously, and the Ranging module inside the entrance performs Ranging with lots of smart phones (e.g. 20 smart phones) at the same time. Since entrance machines are always built in a row closely, one smart phone may perform Ranging procedures with 2 or more entrances simultaneously while it appears within their effective ranging distances (e.g. ranging distance $< 2\text{m}$ ). In this way, smart phones can distinguish which entrance is the nearest one to enter. A typical distance based metro entrance access is shown in figure below. There is one Ranging module for each aisle. The Ranging module can only perform Ranging with devices falling within the angle of view $\alpha$ , which is to avoid for performing Ranging with devices at backside. The threshold distance for triggering access to an aisle should be no more than $0.3+0.55=0.85\text{m}$ for normal size entrance and $0.5+0.9=1.4$ for larger size entrance to avoid mistakenly triggering aisle access by UE at another aisle. A safer distance threshold would be $0.6\text{m}$ with $0.1\text{m}$ distance accuracy for normal size entrance and $1\text{m}$ with $0.2\text{m}$ distance accuracy for larger size entrance. Then, effective Ranging distance $2\text{m}$ would be enough.
+
+
+
+Figure 5.8.1-1: Illustration of distance based metro entrance access. The diagram shows two scenarios: 'Normal Size entrance' and 'Larger Size entrance for disabled people'. In the 'Normal Size entrance' scenario, there are three rectangular blocks representing entrances. The first entrance has a 'Ranging module' at its base. Two User Equipment (UE) units, UE1 and UE2, are shown. UE1 is at a distance of 0.6m from the first entrance's ranging module, and UE2 is at a distance of 1m from the second entrance's ranging module. The angle of view for each entrance is labeled as alpha. Above the entrances, horizontal distances are marked: 0.3m, 0.55m, 0.3m, and 0.55m. In the 'Larger Size entrance for disabled people' scenario, the same setup is shown but with larger dimensions: horizontal distances are 0.5m, 0.9m, 0.5m, and 0.9m. UE1 is at a distance of 1m from the first entrance's ranging module, and UE2 is at a distance of 1.5m from the second entrance's ranging module. The angle of view alpha is also indicated.
+
+**Figure 5.8.1-1 Illustration of distance based metro entrance access**
+
+Typically, UE will move at $3\text{km/h}$ speed, it will result in $4\text{cm}$ distance change in $50\text{ms}$ . Thus, $50\text{ms}$ service latency and Ranging interval is able to ensure the distance change is well tracked.
+
+In case of crowded entrance, there could be over 20 UEs within the 2 meter radius of the entrance, so the Ranging module on the entrance would need to perform Ranging with more than 20 UEs simultaneously. Considering that there are 5 entrances in a row, the number of UEs within the 2 meter radius of these entrances (the size of the area would be $0.8 \times 5 \times 2 = 8\text{m}^2$ ) would be 100.
+
+### 5.8.2 Pre-conditions
+
+Tom downloads an app on his smart phone with Ranging module. The hands free metro/bus validation function is enabled on this APP, and the automatic payment function is also enabled.
+
+The metro and bus system have Ranging module, which can do ranging with the smart phone. This Ranging module can use a combination of 3GPP technologies and non-3GPP technologies. This includes, but not limited to, GNSS (e.g. BeiDou, Galileo, GLONASS, and GPS), Terrestrial Beacon Systems (TBS), Bluetooth, WLAN, RFID, UWB and sensors.
+
+### 5.8.3 Service Flows
+
+1. Tom carries his smart phone near the metro entrance.
+2. After the metro entrance detects the smart phone, it implements Ranging with the smart phone.
+3. When Tom gets close to the metro entrance from outside the station, if the Ranging results reach a certain distance, the entrance is automatically opened.
+
+4. The metro entrance detects the change of position relative to the mobile phone and determines whether Tom enters the station. If Tom enters the station, continue the following procedure, or close the entrance in time.
+5. Tom has completed his trip. When Tom gets close to the metro exit from inside the station, if the Ranging result reaches a certain distance, the exit is automatically opened.
+6. The metro exit detects the change of position relative to the mobile phone and determines whether Tom leaves the station. If Tom leaves the station, continue the following procedure, or close the exit in time.
+
+### 5.8.4 Post-conditions
+
+The billing node get his trip from the metro system, and deducts the corresponding fee from the Tom's account.
+
+- a) If the deduction is successful, the procedure ends.
+- b) If the deduction is unsuccessful, the hands free metro/bus validation function will be suspended. Tom needs to manually complete the payment on the APP to re-enable the function.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR 5.8.6-1] The 5G system shall be able to support for a UE to discover other UEs supporting Ranging.
+
+[PR 5.8.6-2] The 5G system shall be able to provide Ranging service with following performance KPIs.
+
+**Table 5.8.6-1 – KPIs for smart transportation metro/bus validation**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|-------------------------------------------|---------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS /LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| Smart Transportation Metro/Bus Validation | 10cm | - | 99 % | 50ms | 2m | IC/PC/OOC | LOS | Static/
Moving
(3km/h) | 50ms | 20 | 100 in the area of 8 m 2 |
+
+## 5.9 Distance based Intelligent Perception for Public Safety
+
+### 5.9.1 Description
+
+Nowadays, COVID-19 outbreaks all over the world without mercy, it has seriously affected people life and economics. Even we are capable to find out who has gone to the infected zone, or the track of infected people based on the interaction between UE and base station, there is still no clue to figure out who is close contact with the one infected.
+
+A smart device with distance based technique brings chances, it can record smart devices which appears nearby and stays for a long time. Ranging module makes it possible. Under emergency circumstances, people can active such a function to help government find out potential infected people more precisely and plot spreading diagram so as to stop serious spread at early time. In this way, many medical resources can be saved for testing or curing only the individual who is close exposure to the infected rather than wasting on everyone appears in high risk area.
+
+There is no difference for the ranging in both indoor and outdoor case. When the two UEs are getting close to each other less than specific distance (e.g., 5m), one UE will mark the presence of the other UE (vice versa), so it is assumed that ranging distance is less than 20m. The availability is relax with 99%, since it is just used to track the presence of other UEs. It assumes that there are 100UEs within the specific area (e.g., radius = 20m). The static/low moving UEs are still possible to get close to each other and being infected. The low moving UE could be for example pedestrian UE, or UE on bike/electrical bike, so the relative UE velocity is small than 20km/h.
+
+### 5.9.2 Pre-conditions
+
+Alice and Bob both wear smart devices (e.g. smarts phone, smart watch, etc), UE A and UE B, which are ranging capable and discoverable.
+
+The function of distance based intelligent perception for public safety is already switched on.
+
+### 5.9.3 Service Flows
+
+1. Alice with UE A meets Bob with UE B, they walk or run towards to each other under a particular relative velocity (e.g. 5km/h).
+2. UE A discovers UE B and UE B discovers UE A.
+3. Both UE A and UE B estimates the distance between each other. If the distance meets the criteria (e.g. smaller than 5 meter), both start a timer.
+4. After a talk, Alice and Bob say goodbye to each other, they walk towards different directions. If the distance between UE A and UE B exceed the limit (e.g. larger than 8 meter), the timers stop. At the same time, UE A generates a record including UE B's identifier, location, time length, etc. And UE B performs same actions.
+5. UE A and UE B periodically upload records to the server in department responsible for public safety.
+
+### 5.9.4 Post-conditions
+
+Alice feels bad and goes to hospital, and medical testing shows Alice is infected. Hospital report Alice as one infected to the public safety department. Then, the department alarms people Alice met based on the record UE A uploaded. Bob is told to go to hospital for testing infection.
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+[PR 5.9.6-1] The 5G system shall be able to support for a UE to discover other UEs supporting Ranging.
+
+Table 5.9.6-1 – KPIs for distance based intelligent perception for public safety
+
+| Ranging scenario | Ranging Accuracy (95 % confidence level) | | Availability | Latency | Coverage, environment of use, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation support in area | | | | | | |
+|---------------------------------------------------------|------------------------------------------|--------------------|--------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------|-------------------------|------------------|-------------------------------------------------|--------------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation support in area |
+| distance based intelligent perception for public safety | 50cm | - | 99 % | - | 20m | IC/P C/OO C | LOS | Static/Moving (<20km/h) | - | 100 | - |
+
+## 5.10 Picture and video sharing based on ranging results
+
+### 5.10.1 Description
+
+Picture and video sharing is popularly used in recent smart phone market and brings life fun. More interesting functions can be introduced when the target for sharing is visible to the user by using ranging.
+
+### 5.10.2 Pre-conditions
+
+This use case is about Mary and her friends who have a birthday party and take some pictures and videos by smart phone. These pictures and videos can be shared with each other and also displayed on some other devices with big screen, e.g., smart TV, laptop, pad, based on the ranging results between different devices. For example, Mary can share the picture to all of her friends or some friend by smart phone based on the distance and/or pointing direction of Mary's phone.
+
+We use a simple 2D example involving two smart phones and one pad to show how ranging works. In Fig 5.10.2-1, the smart phone 1 initiates the ranging operation towards smart phone 2 and the Pad, where the coordinate system changes with the movement of the smart phone 1. The accuracy for the ranging may affect the identification of multiple UEs. Considering various realistic scenarios, a direction accuracy of 2° is considered acceptable estimation. For example, when the distance between two smart phones is 3m, 2° direction accuracy results in about 10 cm deviation perpendicular to distance. For the media sharing between a smart phone and a smart screen, where the distance is around 10m, the same 2° direction accuracy results in about half a meter deviation. For the latter case, it's worth mentioning that the 2° direction accuracy still applies because larger surface screen area of the smart screen will naturally compensate for a larger deviation on the tangent line in this case.
+
+
+
+Figure 5.10.2-1 consists of two diagrams, (a) and (b), illustrating the ranging process of smart phone-1 with a coordinate system centered at smart phone-1.
+
+(a) Smart phone-1 points nowhere at t1: This diagram shows a coordinate system with x and y axes centered at smart phone-1. Smart phone-2 is located on the negative x-axis at a distance $d2$ . A Pad is located at a distance $d1$ from smart phone-1 at an angle $\theta1$ from the positive y-axis. Smart phone-1 is oriented vertically, pointing nowhere.
+
+(b) Smart phone-1 points to Pad at t2: This diagram shows the same setup as (a), but smart phone-1 is rotated such that it points directly towards the Pad. The angle between the positive y-axis and the direction to the Pad is now $\theta1'$ . The angle between the negative x-axis and the direction to smart phone-2 is $\theta2'$ . The Pad is shown with a small arrow indicating its orientation.
+
+Figure 5.10.2-1: Ranging of smart phone-1 with coordinate system centred at smart phone-1. (a) Smart phone-1 points nowhere at t1. (b) Smart phone-1 points to Pad at t2.
+
+**Figure 5.10.2-1: Ranging of smart phone-1 with coordinate system centred at smart phone-1**
+
+To achieve the ranging accuracy, the latency of the ranging needs to fulfill some requirements when the UE is moving. Even when UE is moving with a relatively low speed, if the latency is too large, the ranging result will be out of date, which leads to the derivation between the ranging results and the ground truth.
+
+In a typical scenario that smart phone-1 ranging a pad to share the video to the pad, where the distance between the smart phone-1 and pad is $d1=3$ meters as shown in Figure 5.10.2-2. According to the direction accuracy requirement $\Delta\theta= 2^\circ$ , the derivation $d1*\Delta\theta$ is around 10cm.
+
+
+
+Figure 5.10.2-2 illustrates the ranging accuracy of smart phone-1 with a coordinate system centered at smart phone-1. It shows smart phone-1 at the origin of an x-y coordinate system. A Pad is located at a distance $d1$ from smart phone-1 at an angle $\theta1$ from the positive y-axis. A second, slightly offset position for the Pad is shown at a distance $d2$ and an angle $\theta1 + \Delta\theta$ . The arc length between the two positions, representing the derivation in distance, is labeled $d1\Delta\theta$ .
+
+Figure 5.10.2-2: Ranging accuracy of smart phone-1 with coordinate system centred at smart phone-1.
+
+**Figure 5.10.2-2: Ranging accuracy of smart phone-1 with coordinate system centred at smart phone-1**
+
+Service latency should ensure that the acquired ranging result is still valid even when there exists relatively movement. Consider the movement of the user's hand during ranging may be up to 1m/s, the derivation in distance is about $1\text{m/s} * 50\text{ms} = 5\text{cm}$ or derivation in direction is about $\arctan(5\text{cm}/3\text{m}) = 0.95^\circ$ , which can fulfill the requirements of the ranging accuracy.
+
+### 5.10.3 Service Flows
+
+Mary selects the pictures and/or videos and decides to share or display, where Jay's smart phone is not far from Mary's smart phone.
+
+Mary's smart phone performs ranging based on the coordinate system defined by Mary's smart phone,
+
+Based on the ranging results, Jay's smart phone is detected and accordingly mapped in the coordinate system, which is visualized in Mary's UE screen with distance and direction information,
+
+Mary selects Jay's smart phone by touching Jay's phone icon in the screen or pointing at Jay's phone,
+
+Mary's smart phone starts to transmit picture and/or videos to jay's smart phone.
+
+### 5.10.4 Post-conditions
+
+None.
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+[PR 5.10.6-1] The 5G system shall be able to provide ranging service with following KPIs:
+
+**Table 5.10.6-1 – KPIs for picture and video sharing**
+
+| Ranging scenario | Ranging Accuracy (95 % confidence level) | | Availability | Latency | Coverage, environment of use, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation support in area | | | | | | |
+|---------------------------|------------------------------------------|--------------------|--------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------|-----------------------|------------------|-------------------------------------------------|--------------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation support in area |
+| Picture and video sharing | 10cm | 2° | 99 % | 50ms | 10m | IC/PC/OOC | LOS | Static/Moving (<1m/s) | 50ms | - | - |
+
+## 5.11 Ranging of UE's in front of vending machine
+
+### 5.11.1 Description
+
+Vending machines are popular on many public places. A lot of work has been done in improving the shopping experience. Contactless payment is one of those. Since most phones have some type of payment, a further enhanced experience can be created if the UE of the person who is going to buy goods can be accurately ranged in front of the vending machine. Additional authentication and authorization of the user prior to taking payment can then be enabled.
+
+### 5.11.2 Pre-conditions
+
+In a subway station there are a lot of people moving around and multiple vending machines. Bob has decided to buy a soda from one of them. The vending machines has the capability to accurately and with high precision determine which of all UE's that are right in front of the vending machine. Bobs phone also has the ranging functionality as well as possibility to do mobile payment. The vending machine might be in out of coverage area. The vending machine is located in a busy subway station and there may be in the magnitude of 10 other UE's in the vicinity that can have same ranging functionality.
+
+### 5.11.3 Service Flows
+
+Bob walks up to the vending machine and decides what soda he should buy. Since he is determined (by the vending machine) to be in the right position in front of the machine, he will be allowed to do the selection and his mobile wallet will be deducted accordingly.
+
+### 5.11.4 Post-conditions
+
+The experience of buying the soda is safe and effortless.
+
+### 5.11.5 Existing features partly or fully covering the use case functionality
+
+There are several online and offline methods for mobile payment, and this is not described here.
+
+### 5.11.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.6-1] The 5G system shall support mutual ranging, i.e. the two UE's involved shall be able to range each other.
+
+[PR 5.11.6-2] The 5G system shall be able to provide ranging service with following KPIs:
+
+**Table 5.11.6-1 – KPIs for ranging of UE's in front of vending machine**
+
+| Ranging scenario | Ranging Accuracy (95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|-----------------------------|------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|-----------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| Ranging for Vending Machine | 20cm | 10° | - | 150ms | 5m | IC/PC/OC | LOS | Static/Moving (<1m/s) | 50ms | - | 10 |
+
+## 5.12 Finding pets in a long distance based on energy efficient Ranging
+
+### 5.12.1 Description
+
+Pets provide company for people. They are friends and family of the human beings. For various reasons a pet can get lost. An indoor pet that often sits by windows could escape. Children that enjoy playing with pets outdoors usually have pets slip through the neighbourhood by missing to latch backyard gates. When walking a pet, even professional pet sitters or dog walkers could have pets escape by accident. When this happens, anxious owners would try their best to find them back. This use case focuses on how ranging can help to get people and pets together again by accurately and efficiently finding the missing pets.
+
+Some additional information on the technologies based on Time of Flight can be found below.
+
+Nowadays, there are multiple technologies which are used to measure the distance or angle between two radio transceivers based on multiplying the Time of Flight (ToF) by the speed of light, for example, Two Way Ranging (TWR), Time Difference of Arrival (TDoA), and Phase Difference of Arrival (PDoA). We provide some examples for better understanding on how it works in figure 5.12.1-1.
+
+
+
+(a) Example of TDoA method: A diagram showing a User Equipment (UE) sending a signal to three reference points labeled T1, T2, and T3. Each reference point has a timestamp (T1, T2, T3) and is connected to a central 'processing' block. The UE is positioned between the reference points.
+
+(b) Example of TWR method: A diagram showing two User Equipment (UE) units, 'Initiated UE' and 'Target UE', exchanging signals. The Initiated UE sends a signal at time T1, which is received by the Target UE and reflected back at time T2. The Initiated UE receives the reflected signal at a later time.
+
+(c) Example of PDoA method: A diagram showing an 'Initiated UE' with multiple antennas sending signals to a 'Target UE'. The signals are received at different times due to the 'Distance between antennas', allowing for phase difference measurement.
+
+Three diagrams illustrating different Time of Flight (ToF) methods: (a) TDoA method, (b) TWR method, and (c) PDoA method.
+
+#### 5.12.1-1 examples of different methods using ToF
+
+- The TDoA method is similar to GPS with the condition of the time synchronization of multiple reference points. For UWB, the UE sends beacons signal, which is marked by multiple reference points with timestamps. Then the timestamps from multiple reference points need to process together to compute the location of the UE that sent the beacon.
+- The TWR method relies on two-way communication between two UEs. The initiated UE measures the Time of Flight of the signal between them. By multiplying the round trip time of the signal by the speed of light, and then dividing by 2, the actual distance between the two UEs can be derived.
+- The PDoA method combines the TWR scheme to measure the Time of Flight between two UEs. The initiated UE also needs to carry multiple antennas and can measure the Phase Difference of Arrival of the signals sending by target UE.
+
+##### Effective Ranging Distance
+
+To ensure the accuracy of the ToF based methods, it is important to have LOS communication. The probability of having LOS communication decreases when the distance between two UEs increases. With LOS communication, the effective ranging distance can be several kilometres.
+
+NOTE: Line-of-sight propagation is a characteristic of electromagnetic radiation or acoustic wave propagation which means the waves are not diffracted, refracted, reflected, or absorbed by the atmosphere and obstructions with material.
+
+##### Power consumption
+
+Based on the TWR method, which relies on the two-way communication between two UEs, the target UE has to scan for ranging signals that can consume a lot of power. It is important to make the ranging operation energy efficient, especially for the target UEs.
+
+### 5.12.2 Pre-conditions
+
+This use case is about Tom and his pet dog Jerry. Jerry is a new family member of Tom's. For safety reasons, Tom bought Jerry a smart collar that is very simple. It only support ranging service (only response) to make sure that Tom can find Jerry, for example, with his phone or his drone, or via the smartphones of the friendly volunteers, that support initiating the ranging service. Tom can charge the smart collar weekly, and that is sufficient to ensure responses, whenever Tom seeks to find Jerry by initiating the ranging service.
+
+One day, Tom took Jerry out for a walk in a park. As a young puppy, curious Jerry got overly excited and ran to chase after a pitchy barn swallow. Soon Tom lost sight of Jerry and Jerry does not seem to return any time soon. Tom called Jerry but heard no answers. The park is too large for Tom to search every corner on foot. Considering Jerry might run away over a long distance, and worried that Jerry might even end up a stray dog, Tom decided to find Jerry immediately.
+
+### 5.12.3 Service Flows
+
+Tom decided to use his drone to search for Jerry.
+
+Tom switched on the ranging service of the drone and controlled it to a height under the restriction of regulation by Tom's smart phone.
+
+Thanks to the good channel condition of the drone, the drone received Jerry's smart collar's response and found Jerry was about several hundreds meters away from Tom's home and the moving direction was still not right.
+
+
+
+Diagram illustrating the service flow for finding a pet using a drone. Tom's smart phone controls Tom's Drone, which is shown in the air. The drone is connected to the phone by a dashed line labeled 'control'. The drone is also shown with a solid line pointing to Jerry's smart dog collar, which is on the ground. A circular inset shows a close-up of the drone and the dog collar, with a red line connecting them, indicating a ranging service.
+
+**Figure 5.12.3-1: Finding pets in a long distance**
+
+Otherwise, if there is not a drone ready to hand, Tom can also ask the smartphones of the friendly volunteers to operate the ranging service like the drone as showed above, to find the Jerry as fast as possible.
+
+### 5.12.4 Post-conditions
+
+According to the ranging results, Tom went to the place and found Jerry back.
+
+### 5.12.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 clause 6.15 energy efficiency:
+
+The 5G access network shall support an energy saving mode with the following characteristics:
+
+- the energy saving mode can be activated/deactivated either manually or automatically;
+- service can be restricted to a group of users (e.g. public safety user, emergency callers).
+
+NOTE: When in energy saving mode the UE's and Access transmit power may be reduced or turned off (deep sleep mode), end-to-end latency and jitter may be increased with no impact on set of users or applications still allowed.
+
+The 5G system shall support UEs using small rechargeable and single coin cell batteries (e.g. considering impact on maximum pulse and continuous current).
+
+TS 22.261 clause 6.27 Positioning services
+
+The 5G system shall support mechanisms to configure dynamically the update rate of the position-related data to fulfil different performances (e.g. power consumption, position service latency) or different location modes.
+
+NOTE 5: for example, the 5G System needs to be able to request the UE to provide its location periodically with an update rate ranging from one location every [1 s to 10 s] in location normal mode to one location every [30 s to 300 s, or more] in location power saving mode. The 5G System needs to allow UEs to sleep for extended periods (e.g. one week), without requiring the UE to update its position data.
+
+TS 22.261 clause 7.3 High-accuracy positioning:
+
+The 5G system shall support positioning technologies that allow the UE to operate at Service Level 1 for at least 12 years using less than 1800 mWh of battery capacity, assuming multiple position updates per hour.
+
+NOTE 2: This requirement aims energy-efficient positioning technologies draining a minimal energy on the UE battery. It derives from use cases, such as asset tracking, with a small form-factor battery representative of an IoT device. This requirement may translate into an energy consumption for the UE's positioning functions in the order of 20 mJ per fix.
+
+NOTE 3: This requirement does not preclude the use of higher energy consumption to fulfil higher position update rates than the one above, or other KPIs than those of Service Level 1 (e.g. more accurate service levels).
+
+In recent requirements captured in TS 22.261, 5G access network has been required to support energy saving mode and 5G system shall support UE using small batteries. In the positioning related requirements, power consumption is one of the considered factors for positioning service.
+
+However, ranging service that occurs between two UEs is not equal to positioning service that is usually operated by the network. For ranging service, the requirement is missing to require an energy efficient ranging.
+
+### 5.12.6 Potential New Requirements needed to support the use case
+
+[PR 5.12.6-1] The 5G system shall support energy efficient UE ranging services and operation.
+
+[PR 5.12.6-2] The 5G system shall be able to provide ranging service with following KPIs.
+
+**Table 5.12.6-1 – KPIs for finding pets in a long distance based on energy efficient Ranging**
+
+| Ranging scenario | Ranging Accuracy (95 % confidence level) | | Availability | Latency | Coverage, environment of use, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation support in area | | | | | | |
+|----------------------|------------------------------------------|--------------------|--------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|-----------------------------|------------------|-------------------------------------------------|--------------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation support in area |
+| Long distance search | 20 m | 5° | 99 % | 1s | 100m-1km | IC/PC/OC | LOS | Static/Moving (up to 10m/s) | 5s | - | - |
+
+## 5.13 Power efficient Ranging Operation
+
+### 5.13.1 Description
+
+Ranging service requires ranging UE to operate ranging action after the ranging service starts. And it is assumed that users can switch on or switch off the ranging service through application installed his or her smart phone. But in fact, users always switch on ranging service in his/her convenience time not just in the location where the ranging service goes well. Considering the use cases in the TR22.855, it is obvious that only in the ranging efficient distance, the ranging operation is required to operate with specified ranging interval e.g. 50ms and related performance.
+
+So, it makes sense for ranging service to consider more efficient operation when the distance is greater than the ranging efficient distance. For example, operating ranging with slow frequency if the distance is greater than ranging efficient distance and operating ranging with required ranging interval when the distance is within efficient ranging distance. Thus, the 5G system is required to change ranging working mode in time when the distance changes.
+
+The frequent/infrequent ranging operation transformation condition can be configured by ranging service application provider e.g.:
+
+- when the measured ranging distance $\leq$ Effective Ranging distance, to trigger frequent ranging operation;
+
+- or when the measured ranging distance > Effective Ranging distance, to trigger infrequent ranging operation;
+- or after some time (e.g. > (ranging service latency + ranging interval)), ranging information can't be received, to trigger infrequent ranging operation etc.
+
+Figure 5.13.1-1 illustrates the smart car key example considering frequent/infrequent ranging operations after ranging service is started. When the ranging service is started, the initial UE may or may not receive ranging information because the actual distance may exceed the effective ranging distance.
+
+
+
+Figure 5.13.1-1: infrequent and frequent ranging operation. The diagram shows a sequence of events starting with 'Ranging Service Start' at a smartphone (represented by a yellow character). The phone moves towards a car (represented by a blue car icon). Two types of ranging operations are shown: 'Infrequent Ranging Operation' (dashed green lines) and 'Frequent Ranging Operation' (solid green lines). The 'effective ranging distance' is indicated by a horizontal line between the phone and the car. The 'distance is greater than effective ranging distance' is indicated by a longer horizontal line starting from the 'Ranging Service Start' point.
+
+**Figure 5.13.1-1 infrequent and frequent ranging operation**
+
+Following service flow give an example of effective smart car key ranging operation.
+
+### 5.13.2 Pre-conditions
+
+The Tom's car support ranging service. Its paired ranging UE is Tom's smart phone.
+
+Tom's car is usually parked in his house during the night. And in working days, it is always parked in Tom's office underground parking port.
+
+Tom's car and his smart phone have registered one of Operator's Ranging service: Smart Car Key. The "infrequent ranging interval" is configured by the "Smart Car key" service as 10s through the interface supplied by 5G system and via the 5G system, the configuration is delivered to his car and his smart phone.
+
+Tom's car ranging operation is always switched on while his smart phone is switched on when needed.
+
+The following parameters refer to TR22.855 Table 5.3.6-1.
+
+### 5.13.3 Service Flows
+
+Tom's car is parking at home park garage and operating ranging with large ranging interval 10s.
+
+In the morning, Tom goes to his car with his smart phone switch on ranging service.
+
+The car detects that the distance with the paired smart phone is less than "Effective Ranging Distance" 30m.
+
+The car starts frequent ranging operation with required ranging Interval 50ms.
+
+The car automatically unlocks and opens the door when Tom is nearby $\leq 1\text{m}$ .
+
+Tom drives the car to his office, then parks his car in the office underground parking port. Tom leaves his car. His car identifies the distance between the car and Tom's smart phone exceeds the configured "lock door distance" 3m. The car automatically locks.
+
+The car continuously operates frequent ranging with Ranging Interval is 50ms until it detects that the distance exceeds "Effective Ranging Distance" i.e. 30m. It enters the infrequent ranging operation the ranging interval is 10s.
+
+Tom leaves his office and goes to his car. His car identifies the distance less than "Effective Ranging Distance" 30m.
+
+The car starts frequent ranging operation with the ranging interval back to 50ms.
+
+The car automatically opens the door when Tom is nearby. Tom drives his back home.
+
+At his home, Tom switches off ranging service in his phone.
+
+### 5.13.4 Post-conditions
+
+Tom's car can be automatically lock and unlock with more power efficiently.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 clause 6.27 Positioning services
+
+The 5G system shall support mechanisms to configure dynamically the update rate of the position-related data to fulfil different performances (e.g. power consumption, position service latency) or different location modes.
+
+NOTE 5: for example, the 5G System needs to be able to request the UE to provide its location periodically with an update rate ranging from one location every [1 s to 10 s] in location normal mode to one location every [30 s to 300 s, or more] in location power saving mode. The 5G System needs to allow UEs to sleep for extended periods (e.g. one week), without requiring the UE to update its position data.
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+[PR 5.13.6 -1] The 5G system shall be able to start ranging and stop ranging according to the application layer's demand.
+
+[PR 5.13.6 -2] The 5G system shall be able to provide mechanisms for a MNO, or authorized 3rd party, to provision and manage ranging operation and configurations.
+
+## 5.14 Finding and Tracking Objects
+
+### 5.14.1 Description
+
+There are many practical situations in which people need to find or locate objects or other people or to track them while they are moving. In this case consider a family with a young child in a very crowded environment in a fire breakout emergency. If the parents are separated from the child, locating him or her takes priority over all other activities and the process can be quite upsetting to the parents and the child. Of course this is not the only example possible: one may need to find missing objects in almost any environment, or track people or objects in situations in which it is difficult to maintain contact or when it is important to locate people as fast as possible.
+
+This use case does not require low latency interaction.
+
+### 5.14.2 Pre-conditions
+
+Marigold, three years old, is very venturesome and curious. She wears a wristwatch that is a smart Ranging enabled device.
+
+Francis, Marigold's father has a smartphone capable of determining the location of smart Range enabled devices.
+
+Marigold's watch has been configured so that Francis' smart phone is able to locate it.
+
+Francis and Marigold go shopping in an enormous Carrefour complex.
+
+### 5.14.3 Service Flows
+
+This use case covers two events: 'normal shopping' and 'fire breaks out.'
+
+One moment, Marigold was there, the next moment, she vanished! Francis looks up and down the aisle in the store, and cannot see her. After searching for a minute or so, he activates his Smart Ranging application on his smartphone.
+
+Marigold moved fast. She is already 200m away examining toys in a distant portion corner of the Carrefour market.
+
+Francis' smartphone uses Ranging functionality to identify her direction and approximate range. This gets Francis moving in the right direction.
+
+Once Francis is within 30m, he can use precision location capabilities to identify his daughter wandering along the 25m length of the toy aisle, even though she is hard to spot through the crowd of other children, similarly separated from their parents (during normal shopping,) or just beyond the emergency exit in the crowd of people who have exited the building (during the emergency situation.)
+
+### 5.14.4 Post-conditions
+
+Francis has successfully located his daughter, though he needed to traverse the enormous Carrefour complex. The longer range approximate location sufficed to close the distance between himself and Marigold, even while she continued to move. Once near enough, he could use the precise 5G Ranging facility to find her amongst the crowd.
+
+### 5.14.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.14.6 Potential New Requirements needed to support the use case
+
+[PR 5.14.6-1] The 5G system shall be able to provide ranging service with the following KPIs:
+
+**Table 5.14.6-1 – KPIs for Object Finding and Tracking**
+
+| Ranging scenario | Ranging Accuracy
(95 % confidence level) | | Availability | Latency | Effective Ranging distance, Coverage, NLOS/LOS, Relative UE velocity, Ranging interval, Number of concurrent ranging operation for a UE, Number of concurrent ranging operation in an area | | | | | | |
+|--------------------------------|-------------------------------------------------------------------------|--------------------|--------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|-------------------------------|------------------|-------------------------------------------------|---------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | Effective Ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+| Long range approximate Ranging | [10m] | ±[12.5°] | 99 % | - | 500m | IC/PC/O OC | NLOS | Static/
Moving
(<10m/s) | - | 1 | [50]UEs/
(10 4 m 2 ) |
+| Short range precise Ranging | As per KPIs in use case 5.4.6 “KPIs for finding items in a supermarket” | | | | | | | | | | |
+
+## 5.15 Clustering of devices
+
+### 5.15.1 Description
+
+A mass casualty incident (MCI) describes an event in which the emergency medical services may get overwhelmed by the number and severity of the casualties. An MCI may include e.g. chemical, biological, radiological emergencies, mass shootings, major road accidents, buildings being on fire, natural disasters such as earthquakes, etc. which can cause result in loss of human lives in the MCI area. Digital technologies can help to improve the response time of the first responders and reduce the amount of damage and/or loss of life by improving the logistics of clinical and non-clinical operations in an MCI event and real-time victim monitoring in the MCI area. Triaging is a process applied when there are more casualties requiring aid than there are medical personal available in the MCI area. Real-time positioning and grouping of the victims in the triage area and health monitoring can aid the first responders to save a lot of precious
+
+time for the first responders to make swift yet accurate and group-level decisions to reduce loss of life in the MCI area. A triage generally consists of a quick check for immediate life-threatening concerns for the victims present in the triage area. An example of the triaging process is the START system (simple triage and rapid treatment) in which the first responder assigns each patient to one of four color-coded triage levels, based on their breathing, circulation, and mental status. The triage levels as described in START system are:
+
+- i. Immediate (Red color): Victims with major life-threatening injuries, but are salvageable given the resources available
+- ii. Delayed (Yellow color): Victims with non-life-threatening injuries, but are unable to walk or exhibit an altered mental status
+- iii. Walking wounded (Green color): Victims who are able to move themselves out of the incident area to a treatment area
+- iv. Deceased or expectant (Black color): Victims who are dead, or whose injuries make survival unlikely.
+
+
+
+An aerial photograph showing a triage area set up on a street. There are three large colored tarps: a red one in the center, a yellow one to the right, and a blue one further back. Numerous people, some appearing to be in pain or being attended to, are on the tarps. Emergency responders in uniforms and vehicles, including an ambulance with 'Santa Fe Springs' written on it, are present around the triage area. The scene is cordoned off with yellow tape.
+
+Aerial view of a triage area with colored tarps (red, yellow, blue) and emergency responders.
+
+**Figure 5.15.1-1 Example of a triage area with colored tarps**
+
+In this use case, a massive earthquake has taken place in a metropolitan city of Asgard. One of the multistorey buildings in the central market area have collapsed to rubble with more than 100 victims injured, classifying the event as a mass casualty incident (MCI). The public telecommunication services are majorly interrupted. A first responder crew of 3 members have arrived at the scene to identify, triage, and transport the injured victims prioritized based on triage status to the nearest hospitals. Tom, a first responder, has arrived at the scene with a first responding vehicle which can serve as a temporary non-public mobile network AmbCel. Tom has started to triage the victims based on the severity of the injuries using color coding scheme similar to the START system. After being triaged, every victim receives a body-worn ranging-enabled victim-tags (e.g. wearable patient monitor) from Tom. The victims who are triaged as green can walk themselves to the designated safe area just outside of the MCI area, and the victims who are triaged as yellow and red will be moved by a logistics team who will arrive later at the scene. Colored tarps based on triage colors are not yet set in the MCI area, since Tom and his small crew are currently focusing on triaging. However, virtual tarps can be formed digitally with predetermined tarp size and location so that Tom can instruct the later arriving logistics team about the location of virtual tarps and set up a physical tarp to deliver treatment based on the triage status of each tarp. Moreover, each tarp can have their own QoS requirements, so that a network can provide a variety of network services to various medical devices in each tarp. The triage application of Tom will seek assistance from 5G network in order to have an overview of clusters in the MCI area, and optimize the allocation of network resources for various network services required by the first responders and their devices.
+
+### 5.15.2 Pre-conditions
+
+Tom has a 5G enabled mobile phone UE with a USIM and a valid 5G subscription and registered as a first responder device which has ranging service.
+
+The victim-tags are 5G enabled wearable monitoring devices such as smartwatches that can capture vitals and support distance measurement through the ranging service.
+
+### 5.15.3 Service Flows
+
+- Tom triaged Jerry as a yellow victim and attached a victim tag digitally marked as yellow onto his wrist
+- Jerry is moved by the logistics team to a designated area for yellow victims. Before doing so, the logistics team has designated yellow, red and green triage areas. This may be done in multiple ways, e.g. by configuring some virtual areas through an application (e.g. with reference coordinate system or floorplan), by putting some anchor devices in the center of an area and registering these as reference points to the AmbCel network. The AmbCel network also offers a feature to automatically detect areas where people are clustered together and for each of the clusters designate one of the devices in such cluster as the center of the cluster, which the logistics team can use to find these clusters and/or to quickly subdivide the area in different triage areas.
+- The logistics team may also configure some network parameters (such as QoS/URLLC requirements) for each triage area to the AmbCel cellular network.
+- As soon as Jerry is moved to the yellow tarp, it is recognized, by performing ranging between the victim tag of Jerry and other devices (including anchor devices or other device designated as a center of a group), that Jerry gets in close proximity of the yellow triage area (e.g. yellow tarp) and send this information to the AmbCel network, so that the AmbCel network can automatically allocate the specified network resources for medical devices in the yellow triage area.
+- After some time, the health condition of Jerry starts to deteriorate. One of the first responders moves Jerry to the red triage area (e.g. red tarp). Through the ranging functionality of Jerry's tag, it is recognized that Jerry has moved to the red triage area. The AmbCel network automatically allocates the specified network resources for medical devices in the red triage area. Also, the logistics team is notified about the change in triage status.
+- In parallel, Tom has moved to the other side of the building. Also there he found victims. Tom triaged James as a green victim and asked him to move to a safe place in the north of the market area.
+- Tom triages several other victims as green and asks them to gather near the safe place in the north of the market area. Ranging service in the victim tags are active, which starts to discover the neighbouring tags as people starts to move toward the north so they can be given directions and find each other.
+- A remotely located commanding officer of the first responding crew can request the AmbCel system information about the newly formed green cluster, receives the number of victims in that cluster and the relative location of the cluster.
+- A victim-tag is designated as the centre of the cluster based on the center of gravity of the cluster. As the cluster size grows beyond the predetermined tarp size, a new cluster is formed with set of green victim tags with a new center of gravity
+- The location of the clusters and the associated victims are continuously monitored as they walk towards the designated area of green tarp
+- Depending on the number of victim tags in each of the clusters, first responders can be directed to the relative location of the various clusters or triage areas by using their mobile phone UEs (that also support ranging).
+
+### 5.15.4 Post-conditions
+
+Tom and his crew are not exhausted about monitoring the location of the victims and time for triaging is significantly reduced. Therefore, they can pay more attention to the victims and their health conditions saving more lives in the MCI event.
+
+### 5.15.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.15.6 Potential New Requirements needed to support the use case
+
+[PR 5.15.6-1] The 5G system shall be able to support mechanisms for a UE to assist another UE to perform ranging of a third UE (if all UEs are in LOS conditions).
+
+NOTE: It cannot be assumed that all ranging UEs support the same application for exchange of information.
+
+## 5.16 Tracking of devices
+
+### 5.16.1 Description
+
+A mass casualty incident (MCI) describes an event in which the emergency medical services may get overwhelmed by the number and severity of the casualties. An MCI may include chemical, biological, radiological emergencies, mass shootings, major road accidents, buildings being on fire, natural disasters such as earthquakes, etc., which can cause result in loss of human lives in the MCI area. Digital technologies can help to improve the response time of the first responders and reduce the amount of damage and/or loss of life by improving the logistics of clinical and non-clinical operations in an MCI event and real-time victim monitoring in the MCI area. Triaging is a process applied when there are more casualties requiring aid than there are medical personal available in the MCI area. Real-time positioning and grouping of the victims in the triage area and health monitoring can aid the first responders to save a lot of precious time for the first responders to make swift yet accurate and group-level decisions to reduce loss of life in the MCI area. A triage generally consists of a quick check for immediate life-threatening concerns for the victims present in the triage area. An example of the triaging process is the START system (simple triage and rapid treatment) in which the first responder assigns each patient to one of four color-coded triage levels, based on their breathing, circulation, and mental status. The triage levels as described in START system are:
+
+- i. Immediate (Red color): Victims with major life-threatening injuries, but are salvageable given the resources available
+- ii. Delayed (Yellow color): Victims with non-life-threatening injuries, but are unable to walk or exhibit an altered mental status
+- iii. Walking wounded (Green color): Victims who are able to move themselves out of the incident area to a treatment area
+- iv. Deceased or expectant (Black color): Victims who are dead, or whose injuries make survival unlikely.
+
+In this use case, a massive terrorist attack has taken place in an airport at the arrivals hall located in the second floor of the airport building. More than 100 victims are injured, classifying the event as a mass casualty incident (MCI). The public telecommunication services are majorly interrupted, with no positioning system accessible within the airport building. A first responder crew of 3 members have arrived at the scene to identify, triage, and transport the injured victims prioritized based on triage status to the nearest hospitals. Tom, a first responder, has arrived at the scene with a first responding vehicle which can serve as a temporary non-public mobile network AmbCel. Tom have started to triage the victims based on the severity of the injuries using color coding scheme similar to the START system. After being triaged, every victim receives a body-worn ranging-enabled victim-tags (e.g. wearable patient monitor) from Tom. Once the logistics team has arrived, they started to deploy anchor nodes in the airport floor to enable accurate tracking of victims' tags in the airport. This allows later arriving teams (such as ambulance personnel) to be able to quickly find the respective victims and bring them to the hospital.
+
+### 5.16.2 Pre-conditions
+
+Tom has a 5G enabled mobile phone UE with a USIM and a valid 5G subscription and registered as a first responder device which has ranging service.
+
+The victim-tags are 5G enabled wearable monitoring devices such as smartwatches that can capture vitals and uses ranging services to measure distances.
+
+Anchor nodes have higher power rating therefore, can range over longer distances.
+
+### 5.16.3 Service Flows
+
+- Tom triaged Victor as a red victim and attached a victim tag digitally marked as red onto his wrist
+- Logistics team have arrived and started to deploy anchor nodes in the airport floor to enable accurate tracking of victims tags in the airport
+- A treatment team has arrived at the scene, which is notified about the number of red victims and their priority to receive treatment based on triage score
+
+- While arriving at the scene, the treatment team finds that there are multiple red victims that are scattered across the airport floors
+- A treatment officer, who has a treatment device and a mobile UE, picks Jerry from the list of victims. The mobile UE of the treatment officer shows that Jerry is located in bay two, row four of the departure halls in the first floor of the airport building.
+- The treatment officer is guided to the exact location of Jerry in the airport building.
+- Within seconds, Jerry is provided the first-aid treatment for his injuries. His bleeding is temporarily stopped and he is immediately transported to the nearest hospital in a helicopter ambulance.
+- Thanks to the ranging services of the AmbCel 5G system, many lives are saved at an unfortunate time of this tragic incident.
+
+### 5.16.4 Post-conditions
+
+Tom and his crew can easily track the location of all the victims and time for re-triaging is significantly reduced.
+
+### 5.16.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.16.6 Potential New Requirements needed to support the use case
+
+[PR 5.16.6-1] The 5G system shall be able to support ranging enabled UEs to determine the ranging capabilities (e.g. capabilities to perform distance and/or angle measurement) of other ranging enabled UEs.
+
+[PR 5.16.6-2] The 5G system shall be able to allow a ranging enable UE to determine if another ranging enabled UE is stationary or mobile, before and/or during ranging.
+
+NOTE: this may require assistance from other ranging enabled UEs.
+
+## 5.17 Immersive sound based on multiple-UE ranging
+
+### 5.17.1 Description
+
+When considering the ranging based on time or time difference of flight, LOS path among UEs is very important for accuracy. However, LOS paths among UEs do not always exist. In all timing-based positioning methods, additional random bias due to non-line-of-sight condition deteriorates performance of position estimation. This makes the accuracy of an initiating UE to range another UE who has no LOS path with the initiating UE unpredictable.
+
+In some scenarios, there may be multiple UEs which may provide help with ranging if the UE have both LOS paths with the UE initiating ranging and the target UE. For example, in home scenarios there may be multiple UEs and even if there is no LOS paths between the UE who initiates the ranging and the target UE, some UEs may “create” a LOS path for the two, i.e., some UE have LOS paths with both of the two UEs. For example in Fig. 5.17.1-1, UE A needs to range UE B but there is an obstacle between them which results in no LOS path. UE A needs to first find a UE who has a LOS path with UE A and also a LOS path with UE B, i.e., UE A needs to find a UE C. Also according to the requirement on the ranging accuracy, UE A may also needs to check the ranging accuracy level of UE C when ranging UE B. In this use case, we only consider the one-hop LOS path “creation”, i.e., only one UE helps with the ranging.
+
+
+
+Diagram illustrating the creation of a Line of Sight (LoS) path between UE A and UE B using UE C as a relay. UE A and UE B are at the top, separated by a wall. UE C is at the bottom, acting as a relay. A dashed line labeled 'No LoS path' connects UE A and UE B directly. Solid red lines labeled 'LoS path' connect UE A to UE C and UE C to UE B. UE C has a compass-like icon with a 'calibration' label, indicating its orientation is being used to establish the path.
+
+**Fig. 5.17.1-1 Create LoS path between UE A and UE B**
+
+Since the ranging operation proposed in other use cases is about peer to peer, the UE ranges other UE based on its own coordinate system. For example, UE A knows UE C is on its 4 o'clock direction, and UE C tells UE A that UE B is on its 11 o'clock direction. However, with the UE C's information about UE B, UE A cannot know where the UE B is. This is because UE A does not know which direction UE C is facing. To help UE A, UE C needs to first calibrate its own coordinate system with UE A to make sure they have the same understanding on the coordinate system, e.g., by providing and compensating for the UE C direction reference point. Then with the information collected from UE C and UE B, UE A can determine the range to UE B accurately even though UE B has no LoS path with UE A.
+
+It will be fantastic to have an immersive audio experience when watching movies in home. The speakers can provide this kind of experience if they can know the position of each other and also the user.
+
+Usually, to have immersive audio experience, several speakers are needed. Ranging may help the speakers to determine position relative to each other and to the listener. With the relative position of each other and to the listener, the speakers can adjust the sound field and provide a better experience to the listeners. The scenarios without LoS path may occur frequently due to the uncertainty of the interior design and decoration of the space. In a home, the speakers may be placed in any part of a room. In some cases, there may be no LoS path between two of them. The NLoS path results in inaccurate ranging between the two speakers, and it is hard to build the immersive audio experience. In addition, a NLoS scenario between any speaker and the UE representing the listener can be adapted for based on this method.
+
+### 5.17.2 Pre-conditions
+
+This use case is about Tom's home theatre plan. Tom bought a set of speakers, and placed them in his home to create an immersive audio experience. According to the instruction of the speakers, and also based on the availability of audio and power wiring Tom distributed the speakers in his living room. However, speaker A has detected that there is no LoS path to speaker B. Speaker A can detect that speaker C has LoS path with speaker A. And speaker C can detect that speaker B has LoS path with speaker B. This detection mechanism is outside the scope of this document.
+
+
+
+Diagram of Tom's home theatre setup. A TV is at the top. Speaker A is on the right, Speaker B is at the bottom, and Speaker C is on the left. A dashed line labeled 'LoS path' connects Speaker A and Speaker C. A dashed line labeled 'LoS path' connects Speaker C and Speaker B. A dashed line labeled 'No LoS path' connects Speaker A and Speaker B, with a red 'X' over it, indicating no direct line of sight between them.
+
+**Fig. 5.17.2-1 Tom's home theatre**
+
+### 5.17.3 Service Flows
+
+#### 1) Configuration procedure
+
+Tom switched on the power to speakers A, B and C to perform calibration. Speaker A discovers all UEs in the area to assist with ranging of a target UE. Speaker A discovers speaker B and C, and Tom's UE.
+
+Speaker A, speaker B and speaker C began ranging each other to adjust the sound field when in later use.
+
+Speaker A identifies by itself that it has NLOS path with speaker B, and a LOS path with speaker C and Tom's UE.
+
+Speaker B identifies by itself that it has NLOS path with speaker A and Tom's UE, and a LOS path with speaker C.
+
+Speaker C identifies by itself that it has LOS path with speaker A, B and Tom's UE.
+
+Note: the UE procedure for determining LOS and NLOS is out of scope of this document.
+
+Speaker A determines the relative position of speaker B through ranging with help of speaker C. Ranging service in this scenario only includes three UEs where Speaker A uses the ranging result of Speaker A to Speaker C, and the ranging result of Speaker B to Speaker C to calculate/calibrate/corroborate the ranging result of Speaker A to Speaker B. Therefore, Speaker A gathers the ranging results from the other speakers in order to perform these calculations.
+
+Speaker A prepares to adjust the sound field.
+
+2) Listening set-up procedure Speakers A, B and C began to range Tom's phone, when Tom places the phone near to his head and uses the phone as a reference point of his head. The speakers give quick feedback to Tom and adjust the sound field to provide an immersive audio experience to Tom.
+
+
+
+Diagram illustrating the ranging process for a listener (Tom) in a home theater setup. Tom is shown in a room with a TV. Three speakers (A, B, and C) are positioned around the room. Speaker A is on the right, Speaker B is on the left, and Speaker C is at the bottom left. Dashed lines represent signal paths. A solid line labeled 'LoS path' connects Speaker A to Tom. A dashed line labeled 'NLoS path' connects Speaker B to Tom, with a red 'X' over it. Another dashed line labeled 'NLoS path' connects Speaker C to Tom, also with a red 'X' over it. The diagram shows Speaker A as the primary source, with Speaker B and C acting as assisting UEs for ranging.
+
+Fig. 5.17.3-1 Ranging the listener
+
+### 5.17.4 Post-conditions
+
+Thanks to supporting ranging service, Tom gets a fantastic home theatre audio experience.
+
+### 5.17.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.17.6 Potential New Requirements needed to support the use case
+
+[PR 5.17.6-1] The 5G system shall be able to support mechanisms for a UE to assist another UE to perform ranging of a third UE (if the requesting UE is LOS with the assisting UE and the assisting UE is LOS with the third UE).
+
+## 5.18 Remote Access Right Authorization
+
+### 5.18.1 Description
+
+In many companies, suppliers can get temporary access right to get into some rooms or labs.
+
+A supplier, Alice, takes a UE with ranging capability. If Alice gets access right for some doors, her UE is authorized to use ranging service with the UEs on these doors. When she is getting closed to one of the doors, the UE on the door can get distance to Alice's UE and let the door open automatically.
+
+To follow the company's security policy, the supplier needs to get authorization every day from a particular employee of the company.
+
+The employee, Bill, needs to check the supplier's UE and authorize the UE access right for some doors.
+
+### 5.18.2 Pre-conditions
+
+A company, CICI, has very strict security policy. People need access right to get into some doors, each of which has a UE on it. All the doors' UEs have ranging capability to check people's access right.
+
+Alice is a supplier of company. She has a UE with ranging capability to get access right into some doors. But each time she arrives at the company, she needs to get permitted by a particular employee, Bill, so that she can get access right.
+
+Bill has a UE, with which Bill can authorize access right to Alice's UE via the 5G system.
+
+### 5.18.3 Service Flows
+
+#### Scenario 1
+
+Alice contacts Bill about her plan to visit CICI and her phone number. Bill needs to make sure that Alice herself has arrived at CICI to authorise her access right. Bill provides CICI door's ID, So that Alice's phone can be discovered by the door of CICI using internal IT system.
+
+
+
+Diagram illustrating the initial contact between Alice and Bill. Alice, represented by an orange figure, is shown on the left. Bill, represented by a blue figure, is inside a building labeled 'CICI'. A dashed blue line connects Alice to Bill, indicating a communication link. The building has several doors, some of which are marked with red squares.
+
+**Fig. 5.18.3-1 Alice contacts Bill and gets CICI door's ID from Bill**
+
+Alice arrives at CICI and her phone is discovered by the door of CICI. Bill gets alerted that Alice's phone is within the range of ranging service to the door. Then, Bill triggers ranging service between Alice's phone and CICI's doors, and provides a distance threshold, e.g., 10cm, to the doors for ranging service to Alice's UE. When Alice places her phone within distance of 10cm to one of CICI's doors, the door is opened automatically.
+
+
+
+Diagram illustrating Alice's arrival and access authorization. On the left, Alice (orange figure) is outside the 'CICI' building. A green line connects her to one of the doors. On the right, Alice is inside the building, and a blue line connects her to a door. The building has several doors, some of which are marked with green squares, indicating they are open or authorized.
+
+**Fig. 5.18.3-2 Alice arrives at CICI. Her phone is discovered by the door of CICI and gets the access right**
+
+When Alice finishes her job and leaves the area of the company, ranging service on her UE is disabled.
+
+
+
+Diagram showing Alice leaving CICI building. A multi-story building labeled 'CICI' has several doors. Alice, represented by an orange figure, is walking away from the building. A dashed blue line connects her phone to one of the doors, indicating a ranging service that is being disabled as she leaves.
+
+**Fig. 5.18.3-3 Alice leaves CICI and ranging service on her phone is disabled**
+
+#### Scenario 2
+
+Alice contacts Bill about her plan to visit CICI and her phone number. Bill needs to make sure that Alice herself has arrived at CICI to authorise her access right. Bill provides CICI door's ID and a distance threshold, e.g., 10cm, for ranging service to Alice's UE.
+
+
+
+Diagram showing Alice contacting Bill. Alice is at the bottom left, and Bill is at the CICI building. A dashed blue line connects them, representing a communication link where Alice gets the door's ID and distance threshold from Bill.
+
+**Fig. 5.18.3-4 Alice contacts Bill and gets CICI door's ID from Bill**
+
+Alice places her phone close to the door of CICI. Bill gets alerted from the door that Alice's phone is within 10cm distance to the door and allow CICI's door to be unlocked for Alice's UE.
+
+
+
+Diagram showing Alice placing her phone close to the door. On the left, Alice is near a door. An arrow points to the right, where Alice is shown with her phone very close to the door handle, and a purple line indicates the ranging service is active and close enough to unlock the door.
+
+**Fig. 5.18.3-5 Alice place her phone close to the door. Bill unlocks the door after gets alerted**
+
+When Alice finishes her job and leaves the area of the company, ranging service on her UE is disabled.
+
+
+
+Diagram showing Alice leaving CICI again. Similar to Fig. 5.18.3-3, Alice is walking away from the CICI building, and a dashed blue line indicates the ranging service is being disabled.
+
+**Fig. 5.18.3-6 Alice leaves CICI and ranging service on her phone is disabled**
+
+### 5.18.4 Post-conditions
+
+Bill can use ranging service to authorize Alice' UE to use ranging service with particular doors in CICI.
+
+After Alice leaves the area of the company, ranging service on her UE is disabled. When she gets back to the company, she cannot get into any door of the company.
+
+### 5.18.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.18.6 Potential New Requirements needed to support the use case
+
+[PR 5.18.6-1] The 5G system shall be able to support ranging service authorization for a UE or a group of UE.
+
+[PR 5.18.6-2] The 5G system shall be able to support ranging service policy/parameter provisioning to UE.
+
+[PR 5.18.6-3] The 5G system shall allow ranging service between 2 UEs triggered by and exposed to a third UE.
+
+[PR 5.18.6-4] The 5G system shall allow ranging service between 2 UEs triggered by and exposed to the application serve.
+
+## 5.19 Sharing Content to a Particular UE
+
+### 5.19.1 Description
+
+When we want to share a content to a UE in proximity, it may take a long time to find the target UE on the phone, as the UE always shows a long list of candidate UEs which can have direct communication. Sometimes, mistakes are unavoidable for distinguishing the name of the target UE when there are similar UE names in the list, especially when the list is changing on the fly.
+
+To efficiently find the target UE, the user who wants to share the content can hold his UE, which is the source UE, pointing to the target UE. With the help of ranging service running on both of the UEs, the source UE can easily find the target UE whose direction is the same as the reference direction of the source UE.
+
+In this use case, Bill wants to share different content from his phone to Alice and Cassie. Alice and Cassie's UEs are always shown at the bottom of UE list. Bill has to swipe screen for a long time to find their UEs on the list. But with ranging service, Bill's phone shows Alice's UE when Bill points to Alice with his phone. Bill's phone shows Cassie's phone when he points to Cassie with his phone.
+
+In this scenario, we need to consider: UEs of different users may subscribe to and use network of different operators. The 5G system shall be able to support ranging service of this scenario.
+
+### 5.19.2 Pre-conditions
+
+Alice, Bill and Cassie are chatting in a restaurant which is covered by network of both operator A and operator B. Their UEs subscribe to different operators:
+
+- Alice's phone subscribes to operator A.
+- Bill's phone subscribes to operator B.
+- Cassie's phone subscribes to operator C and is roaming to B's network.
+
+### 5.19.3 Service Flows
+
+The UEs of Alice Bill and Cassie subscribe to different operators. They want to share content based on ranging service.
+
+Bill wants to share different pictures to Alice and Cassie. He chooses a picture on his phone and clicks "share". A mini map is shown on Bill's phone. UEs around Bill's phone are shown on the map if they have authorized Bill's phone to discover them by ranging service. If Bill turns around, any phone his phone is pointing to is highlighted on the map.
+
+When Bill points to Alice with his phone, Alice's phone is shown on the map in the direction he is pointing to and is highlighted.
+
+Bill clicks Alice's phone. Then, the picture is sent to Alice.
+
+Bill shares another picture to Cassie using the same procedure.
+
+
+
+Diagram illustrating content sharing among UEs subscribing to different operators. Daniel is at the top, Alice and Cassie are in the middle, and Bill is at the bottom. Alice is labeled 'subscribe to A', Cassie is labeled 'subscribe to C roaming to B', and Bill is labeled 'subscribe to B'. Dashed lines connect Alice and Cassie to Bill, indicating content sharing. A box labeled 'Daniel' is at the top, and a box labeled 'Alice' is next to Alice. A box labeled 'Cassie' is next to Cassie. A box labeled 'Bill' is next to Bill.
+
+Fig. 5.19.3-1 Content sharing among UEs subscribing to different operators
+
+### 5.19.4 Post-conditions
+
+Bill's phone discovers Alice and Cassie's UEs with ranging service.
+
+Bill's phone can not discover Daniel's UE, because Bill and Daniel are not friends.
+
+Bill's phone shows the right UE's name when Bill points Alice or Cassie with his phone.
+
+Bill selects right UE to share the right content.
+
+### 5.19.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.19.6 Potential New Requirements needed to support the use case
+
+[PR 5.19.6-1] The 5G system shall be able to support ranging service authorization for a UE or a group of UEs when a UE or a group of UEs will use ranging in licenced band.
+
+[PR 5.19.6-2] The 5G system shall be able to support ranging service policy/parameter provisioning to UE.
+
+[PR 5.19.6-3] The 5G system shall be able to support one UE initiates ranging service to the other UE.
+
+[PR 5.19.6-4] The 5G system shall be able to support ranging service between UEs which subscribe to different operators.
+
+[PR 5.19.6-5] The 5G system shall be able to provide ranging service to roaming UEs.
+
+[PR 5.19.6-6] The 5G system shall be able to authenticate the UE supporting Ranging service.
+
+[PR 5.19.6-7] The 5G system shall be able to authorize the UE for enabling Ranging service.
+
+[PR 5.19.6-8] The 5G system shall be able to ensure the integrity and confidentiality of Ranging information used by Ranging-enabled UEs.
+
+[PR 5.19.6-9] The 5G system shall be able to ensure that user privacy is not violated during Ranging service, e.g., based on regulatory requirements.
+
+[PR 5.19.6-10] The 5G system shall be able to ensure security protection (e.g., interworking security) when the Ranging service concerns UEs subscribed with different operators.
+
+[PR 5.19.6-11] The level of security provided by the existing 5G system shall not be adversely affected when Ranging service is enabled.
+
+# 6 Consolidated requirements
+
+## 6.1 Functional requirements
+
+[CPR-1] The 5G system shall be able to support for a UE to discover other UEs supporting Ranging.
+
+[CPR-2] The 5G system shall be able to authorize Ranging for a UE or a group of UE when using licensed spectrum.
+
+[CPR-3] The 5G system shall be able to protect privacy of a UE and its user, ensuring that no identifiable information can be tracked by undesired entities during Ranging.
+
+[CPR-4] The 5G system shall be able to enable or disable Ranging.
+
+[CPR-5] The 5G system shall support mutual Ranging, i.e. two UEs shall be able to initiate Ranging to each other.
+
+[CPR-6] The 5G system shall be able to ensure that the use of Ranging, if in licensed spectrum, is only permitted in network coverage under the full control of the operator who provides the coverage.
+
+[CPR-7] The 5G system shall support energy efficient Ranging operation.
+
+[CPR-8] The 5G system shall be able to start ranging and stop ranging according to the application layer's demand.
+
+[CPR-9] The 5G system shall be able to provide mechanisms for a MNO, or authorized 3rd party, to provision and manage ranging operation and configurations.
+
+[CPR-10] The 5G system shall be able to support mechanisms for a UE to assist another UE to perform ranging of a third UE (if the requesting UE is LOS with the assisting UE and the assisting UE is LOS with the third UE).
+
+NOTE: It cannot be assumed that all ranging UEs support the same application for exchange of information.
+
+[CPR-11] The 5G system shall be able to support ranging enabled UEs to determine the ranging capabilities (e.g. capabilities to perform distance and/or angle measurement) of other ranging enabled UEs.
+
+[CPR-12] The 5G system shall be able to allow a ranging enable UE to determine if another ranging enabled UE is stationary or mobile, before and/or during ranging.
+
+NOTE: This may require assistance from other ranging enabled UEs.
+
+[CPR-13] The 5G system shall allow ranging service between 2 UEs triggered by and exposed to a third UE.
+
+[CPR-14] The 5G system shall allow ranging service between 2 UEs triggered by and exposed to the application server.
+
+[CPR-15] The 5G system shall be able to support one UE initiating Ranging to the other UE.
+
+[CPR-16] The 5G system shall be able to support ranging service between UEs which subscribe to different operators.
+
+[CPR-17] The 5G system shall be able to allow roaming UEs to perform Ranging.
+
+[CPR-18] The 5G system shall be able to ensure the integrity and confidentiality of Ranging information used by Ranging-enabled UEs.
+
+[CPR-19] The 5G system shall be able to ensure that user privacy is not violated during Ranging service, e.g., subject to regional or national regulatory requirements.
+
+[CPR-20] The 5G system shall be able to ensure security protection (e.g., interworking security) when the Ranging service concerns UEs subscribed with different operators.
+
+[CPR-21] The level of security provided by the existing 5G system shall not be adversely affected when Ranging service is enabled.
+
+[CPR-22] The 5G system shall support a means to securely identify other ranging capable UEs with which a ranging UE performs ranging.
+
+## 6.2 Performance requirements
+
+Table 6.2-1 – KPIs for Ranging
+
+| Ranging scenario | Ranging Accuracy (95 % confidence level) | | Availability | Latency | Effective Ranging distance | Coverage (note 1) | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area |
+|--------------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|----------------------------|-------------------|----------|---------------------------------|------------------|-------------------------------------------------|----------------------------------------------------|
+| | Distance Accuracy | Direction Accuracy | | | | | | | | | |
+| Distance based smart device | 10cm | - | 99 % | 50ms | 20m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 50ms | 20 | - |
+| Smart TV remote | 10cm up to 3 meter separation | ±2° horizontal direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-60°) to (+60°); ±2° Elevation direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-45°) to (+45°) | 99 % | 10ms | 10m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 50ms | - | - |
+| Smart Vehicle Key | 10 cm | - | 99 % | 50ms | 30m | IC/PC/OOC | LOS | Static/
Moving (<2m/s) | 25ms | - | 50UEs/
(10 4 m 2 ) |
+| Finding items in a supermarket | 50 cm | 5 degree | 95 % | 500ms | 100m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 250ms | - | 100 UEs/
(3.14*10 4 m 2 ) |
+| Touchless Self-checkout Machine | 10cm | - | 99 % | 50ms | 1m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 100ms | - | = |
+| Hands Free Access | 10cm | - | [99 %] | 100ms | 10 m | IC/PC/OOC | LOS | Static/
Moving (1 m/s) | 50ms | - | 20 UEs/3.14*10 4 m 2 |
+| Transportation MetroBus | 10cm | - | 99 % | 50ms | 2m | IC/PC/OOC | LOS | Static/
Moving (3km/h) | 50ms | 20 | 100 in the area of 8 m 2 |
+| passenger intelligent perception for | 50cm | - | 99 % | - | 20m | IC/PC/OOC | LOS | Static/
Moving (<20km/h) | - | 100 | - |
+| video sharing based | 10cm | 2° | 99 % | 50ms | 10m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 50ms | - | - |
+| of UE's in front of | 20cm | 10° | - | 150ms | 5m | IC/PC/OOC | LOS | Static/
Moving (<1m/s) | 50ms | - | 10 |
+| Long Distance Search | 20m | 5° | 99 % | 1s | 100m-1km | IC/PC/OOC | LOS | Static/
Moving (up to 10m/s) | 5s | - | - |
+| Long range approximate location | [10m] | [12.5°] | 99 % | - | 500m | IC/PC/OOC | LOS | Static/
Moving (<10m/s) | - | 1 | [50]UEs/
(10 4 m 2 ) |
+
+NOTE 1: In coverage (IC), Partial coverage (PC) and out of coverage (OOC) apply to unlicensed spectrum, or for public safety networks with dedicated spectrum. In coverage applies to licensed spectrum.
+
+# 7 Conclusions and recommendations
+
+The TR provides a number of use cases for Ranging-based services such as distance based smart home device control, smart home TV control, smart vehicle key, finding items in a supermarket, museum tour, touchless self-checkout machine, hands free access, smart transportation metro/bus validation, distance based intelligent perception for public safety, picture and video sharing, ranging of UE's in front of vending machine, finding pets in a long distance based on energy efficient Ranging.
+
+The potential new requirements for each use cases are compiled into a set of potential consolidated Ranging requirements, including functional requirements and performance requirements, wherein a set of KPIs are defined, such as distance accuracy, direction accuracy, availability, latency, effective Ranging distance, coverage, NLOS/LOS, ranging interval, number of concurrent Ranging operation for a UE or within an area.
+
+The resulting potential requirements identified in this TR can be considered for the development of normative requirements. It is therefore proposed to consider the inclusion of these requirements in existing specifications for 5G services (e.g. TS 22.261).
+
+# Annex A: Ranging accuracy
+
+Ranging accuracy is divided into distance accuracy and direction accuracy.
+
+For better understanding, we give an example for the ranging accuracy in 2D coordinate system in Fig.A-1. From the distance perspective, the ranging accuracy on distance is described as $\Delta d$ . Then the distance of UE3 from UE1 is $d \pm \Delta d$ with confidence level 95%. The direction of UE2 to UE1 is $\theta \pm \Delta \theta$ with confidence level 95%. Similar situation applied to the 3D coordinate system centred at the UE who initiates the ranging service.
+
+
+
+The diagram illustrates a 2D coordinate system with x and y axes. UE1 is positioned at the origin (0,0). UE2 is located at a distance $d_1$ from UE1 at an angle $\theta_1$ relative to the positive y-axis. A blue shaded cone represents the angular uncertainty, labeled with $\Delta\theta$ on both sides of the central line. UE3 is located on the negative x-axis at a distance $d_2$ from UE1. A blue shaded region around UE3 on the x-axis represents the distance uncertainty, labeled with $\Delta d$ on both sides of the UE3 position. The angle between the positive x-axis and the line to UE3 is labeled $\theta_2$ .
+
+Figure A-1: Example of ranging accuracy. A 2D coordinate system with x and y axes. UE1 is at the origin. UE2 is at a distance d1 from UE1 at an angle theta1. The angular uncertainty is labeled as Delta theta. UE3 is at a distance d2 from UE1 along the negative x-axis. The distance uncertainty is labeled as Delta d.
+
+Figure A-1. Example of ranging accuracy
+
+# Annex B: Consideration for reference of measurement
+
+To represent an object in some coordinates, it is important to set appropriate origin and reference axis, and for all parties to have same understanding of these.
+
+
+
+Figure B-1: Two diagrams illustrating measurement differences based on reference points. The left diagram shows a TV with reference points A, B, and C at its bottom corners and center. A remote controller (1) is below it, with a red arrow pointing to point B. The distance is labeled R and the angle is theta. The right diagram shows the same TV and remote (2), but with the red arrow pointing to point A. The distance is labeled R' and the angle is theta'.
+
+**Figure B-1: Different results depending on different origins**
+
+The Figure B-1 show how results can change, depending on how origin is defined. For example, in the figure which shows how the distance and direction between TV and remote controller is measured, the result can vary.
+
+Following is assumed in the Figure B-1.
+
+The television has three candidates for the selection of reference point of measurement. ⓐ, ⓑ and ⓒ. I.e, in the left side of Figure B-1, the reference point is set to ⓑ, and in the right side of Figure B-1, the reference point is set to ⓐ.
+
+The Red line shows the reference axis from which the angle and distance are determined.
+
+The remote controller is directed toward ⓑ.
+
+As the figure shows, distance and angle between the TV and the remote controller change depending on which point among ⓐ, ⓑ and ⓒ is selected as reference. When the target object is small, then this is not a major issue. However, as the target object gets larger, the setting of reference point has impact on the outcome.
+
+In addition, as the figure shows, angle between the TV and the remote controller can be further dependent on how reference axis is selected.
+
+# Annex C: Changing Coordinates
+
+To represent where an object is located, applications typically use Cartesian Coordinates. The object in the following figure can be represented as located in (a,b) in the Cartesian Coordinates, with perpendicular axis X and Y.
+
+
+
+Figure C-1: A Cartesian coordinate system with X and Y axes. A point is plotted at coordinates (a, b), with dashed lines connecting it to the axes at points labeled 'a' and 'b'.
+
+**Figure C-1: Object in Cartesian Coordinates**
+
+However, this object can also be represented in other ways. For example, following figure shows how Polar Coordinates can be used, with reference axis K. In Polar Coordinates, the location of an object is represented with $r$ and $\theta$ . $r$ is the distance from the origin to the object and $\theta$ is the angle from a reference direction.
+
+Then, the location of the object in the figure C-2 can be represented with $(r, \theta)$ in Polar Coordinate.
+
+
+
+Figure C-2: Object in Polar Coordinates. A diagram showing a blue circle representing an object. A dashed line of length 'r' connects the origin to the object. A horizontal reference axis labeled 'K' extends from the origin to the right. The angle between the reference axis K and the dashed line is labeled with the Greek letter theta (θ).
+
+**Figure C-2: Object in Polar Coordinates**
+
+Both representations are valid representations in locating the object. Furthermore, one form of representation can be easily converted to other form of representation, if all parameters in the original coordinates are available. I.e, the conversion from Polar Coordinates to Cartesian Coordinates are well known as:
+
+$$a = r * \cos \theta$$
+
+$$b = r * \sin \theta$$
+
+Using this formula, the measured result of distance and angle can be converted easily into points in Cartesian coordinates. Similar, the measured result in Cartesian Coordinates can be easily converted into values in Polar Coordinates.
+
+Similarly, as shown in the figure C-3, the accuracy and error of one coordinate can be easily converted to values in coordinates.
+
+
+
+Figure C-3: Error range conversion between Polar Coordinates and Cartesian Coordinates. A Cartesian coordinate system with X and Y axes is shown. A central blue circle represents an object. Two dashed lines from the origin represent the angular error range, with an angle theta indicated at the origin. Two concentric dashed circles represent the radial error range. Vertical dashed lines from the object's position to the X-axis are labeled 'a'. Horizontal dashed lines from the object's position to the Y-axis are labeled 'b'. Double-headed arrows indicate the error ranges in both polar (radial and angular) and Cartesian (x and y) coordinates.
+
+**Figure C-3: Error range conversion between Polar Coordinates and Cartesian Coordinates**
+
+# Annex D: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|---------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 09/2020 | SA1#91e | S1-203282 | | | | Add Scope | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203346 | | | | - Add Reference
- Add Definition: Secure Ranging, KPI
- Add Overview
- Add Annex A: Ranging accuracy | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203347 | | | | Add use case: Distance based Smart Home Device Control Use Case | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203412 | | | | Add use case: Smart Home TV control Use Case | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203349 | | | | Add use case: Smart Vehicle key | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203350 | | | | Add use case: Finding items in a supermarket use case | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203413 | | | | Add use case: Museum tour | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203352 | | | | Add use case: Touchless Self-checkout Machine Control | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203414 | | | | Add use case: Hands Free Access | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203415 | | | | Add use case: Smart Transportation Metro/Bus Validation | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203416 | | | | Add use case: Distance based Intelligent Perception for Public Safety | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203356 | | | | Add use case: Picture and video sharing based on ranging results | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203357 | | | | Add use case: Ranging of UE's in front of vending machine | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203358 | | | | Add Annex B: Consideration for reference of measurement | 0.1.0 |
+| 09/2020 | SA1#91e | S1-203359 | | | | Add Annex C: Changing Coordinates | 0.1.0 |
+| 11/2020 | SA1#92e | S1-204165,
S1-204425,
S1-204426,
S1-204234,
S1-204145,
S1-204121,
S1-204122,
S1-204120,
S1-204092,
S1-204094,
S1-204322 | | | | Add KPI analysis and update KPI values of existing use cases. | 0.2.0 |
+| 11/2020 | SA1#92e | S1-204427 | | | | Add new use case: Finding pets in a long distance based on energy efficient ranging | 0.2.0 |
+| 11/2020 | SA1#92e | S1-204428 | | | | Add security and authorization requirement | 0.2.0 |
+| 11/2020 | SA1#92e | S1-204097 | | | | Add PR number to requirements | 0.2.0 |
+| 03/2021 | SA1#93e | S1-210457 | | | | Update definition | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210129 | | | | Editorial change on use case finding pets in a long distance | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210458 | | | | updated Ranging use case - Touchless self-checkout machine control | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210459 | | | | KPI updates | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210460 | | | | New use case: power efficient ranging operation | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210461 | | | | New use case: Immersive sound based on multiple-UE ranging | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210462 | | | | New use case: Object Finding and Tracking | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210463 | | | | New use case: on clustering of devices | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210464 | | | | New use case: on tracking of devices | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210465 | | | | New use case: remote Access Right authorization | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210466 | | | | New use case: Sharing content to a particular UE | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210017 | | | | Add Conclusions and Recommendations | 0.3.0 |
+| 03/2021 | SA1#93e | S1-210467 | | | | Add Consolidated requirements | 0.3.0 |
+| 2021-03 | SA#91e | SP-210206 | | | | Presentation to SA for information
MCC clean-up | 1.0.0 |
+| 2021-05 | SA1#94e | S1-211436 | | | | Add consolidated requirements | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211125 | | | | Update on the use case of 5.12 Finding pets in a long | 1.1.0 |
+
+| | | | | | | | |
+|---------|---------|-----------|--|--|--|-------------------------------------------------------------------------|--------|
+| | | | | | | distance based on energy efficient Ranging | |
+| 2021-05 | SA1#94e | S1-211053 | | | | Update the effective ranging distance of use case: Long Distance Search | 1.1.0 |
+| 2021-06 | SA#92e | SP-210511 | | | | Raised to v.2.0.0 by MCC for approval | 2.0.0 |
+| 2021-06 | SA#92e | SP-210511 | | | | Raised to v.18.0.0 by MCC following approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210511 | | | | Corrected logo (5G->5GA) | 18.0.1 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22858/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-18/22_series/22858/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..612df5cd021da3aa2838136343e719a0a3321a95
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c96fc6540f17ff0eaabb08600426f44a2dde5d3905b9248c546bec550146eeb
+size 33330
diff --git a/marked/Rel-18/22_series/22858/0977b81510f7649846289ee785d20e74_img.jpg b/marked/Rel-18/22_series/22858/0977b81510f7649846289ee785d20e74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f88ed746f7a7aad33f79265e115acf1d852b34d3
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/0977b81510f7649846289ee785d20e74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24ffa2824ef2dbe45952e6b63baf2f76e6a73fec7761754a25a4fb9977583a11
+size 16908
diff --git a/marked/Rel-18/22_series/22858/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-18/22_series/22858/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..178184f2369c2a75847338f18018c70e0a929e68
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:845a1985b46463ef0094ea7aeae1a43c78ebe7bad26446f32f589188c52437da
+size 29194
diff --git a/marked/Rel-18/22_series/22858/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-18/22_series/22858/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d141cc2810b81af5bb46778a65c4690e5ee07d9f
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d78255d3a531248fb9ce239308007e93064a84c8eb682efb5090995f39459e9d
+size 46220
diff --git a/marked/Rel-18/22_series/22858/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-18/22_series/22858/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a731d4247cb53440672e816a695acf1b6c4aa68e
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d4a97d9400059265290e72e02579e3286a23e9a02fdcffe879580c8b9143617
+size 24820
diff --git a/marked/Rel-18/22_series/22858/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-18/22_series/22858/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95c2296c5779c63d600311fbdddecb614dc536ee
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e5d7cde73c94686a7416790084363730800f48b165822eb5a7c21338a10e35e
+size 35558
diff --git a/marked/Rel-18/22_series/22858/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22858/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d268ebe2e6120b5c25f83822832ba9f91b9b2d6
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4deb1facc0e84ff9f622973e0eb22cfefa24fa44271727910d1641abb6211956
+size 9305
diff --git a/marked/Rel-18/22_series/22858/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22858/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f0c25c1f97accad3293125728bdf4b5d396d93a6
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75c97515fc37bf7e9a5387a826a8912aff5108f8205478d3b02b8d1a02f7796d
+size 5693
diff --git a/marked/Rel-18/22_series/22858/6c6d2bce2630f62fb3a5345c9ec84f68_img.jpg b/marked/Rel-18/22_series/22858/6c6d2bce2630f62fb3a5345c9ec84f68_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d359fa53629a9ed14b7bcd9d43bbab82a5975af
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/6c6d2bce2630f62fb3a5345c9ec84f68_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d99ab7e6fd777b47a0b4d7bb4a03977e91b8c892bd93629beb071a3836236005
+size 26274
diff --git a/marked/Rel-18/22_series/22858/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-18/22_series/22858/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df0947e25dc2fd2c78f8f3ac99faa285fef7c37d
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2975e5142d21ae031767e0008c0170ffd00388b6be46b2ee3e463632c1b5c839
+size 41180
diff --git a/marked/Rel-18/22_series/22858/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/22_series/22858/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b04608a24fcef0d2835581c10549fe528d91fad9
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa0ea6f9606fe4fa9b2ae445d972d51d365b108b52ceb2cbd25851b5cb60587c
+size 27940
diff --git a/marked/Rel-18/22_series/22858/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/22_series/22858/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e47e3a540de9237eab3d53247a9a11c5aa06366
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dba87cd043cd4204eb29e0dc6db76b1be8032a50afc39e0461a31b2ff461c281
+size 54517
diff --git a/marked/Rel-18/22_series/22858/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/Rel-18/22_series/22858/9edb407536d4d4d4a6ac391527af047c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f10844ef52c1ad56d8df9106702136ca5c6f563
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/9edb407536d4d4d4a6ac391527af047c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:572d6168e61ed06814a8f5379d89f9c514cfc7a85d2038185f4adbf60571d5b0
+size 35956
diff --git a/marked/Rel-18/22_series/22858/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-18/22_series/22858/db5deafdae53dbc7d5972957f708c691_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0f4a415d51cdf70da4f9032d1ea9f654177c0d5
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/db5deafdae53dbc7d5972957f708c691_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22e29321fd08f521f1b61f8cdb5826d553a5d05e3fdf4088188694a799c96486
+size 38951
diff --git a/marked/Rel-18/22_series/22858/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/22_series/22858/dd5771673aececa53d42ece89218299d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f2e6df6cae407a557aa99e34f2c148a5e8f1505
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/dd5771673aececa53d42ece89218299d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b425bb8ed5f3cee0fed49950102f2f78a84168698feb9ad3c5416273ff7b5a27
+size 30089
diff --git a/marked/Rel-18/22_series/22858/eb450c92214e8409c1e0f0846e30d876_img.jpg b/marked/Rel-18/22_series/22858/eb450c92214e8409c1e0f0846e30d876_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d821017f2dda9c7b3efd491bde6153a417221e71
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/eb450c92214e8409c1e0f0846e30d876_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf4fb32b7f431b24d696e18f98458b82ab281352d48b27baf05d3f4f72380594
+size 32549
diff --git a/marked/Rel-18/22_series/22858/f519a5be118c846f631c992412353fb9_img.jpg b/marked/Rel-18/22_series/22858/f519a5be118c846f631c992412353fb9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1efda52ff60c762bf3facbddfd5e9004df67999
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/f519a5be118c846f631c992412353fb9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fabbf5ea82a311c7c850e6652162fdfe5b2a5435e2d330105b06747740f068e5
+size 34713
diff --git a/marked/Rel-18/22_series/22858/raw.md b/marked/Rel-18/22_series/22858/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c91d831fa4a20f90eea79b3921b6c18f337c63da
--- /dev/null
+++ b/marked/Rel-18/22_series/22858/raw.md
@@ -0,0 +1,1911 @@
+
+
+# 3GPP TR 22.858 V18.2.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study of enhancements for residential 5G; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+
+
+---
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+---
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 7 |
+| 1 Scope..... | 8 |
+| 2 References..... | 8 |
+| 3 Definitions and abbreviations ..... | 9 |
+| 3.1 Definitions..... | 9 |
+| 3.2 Abbreviations ..... | 9 |
+| 4 Overview..... | 9 |
+| 5 Use cases..... | 11 |
+| 5.1 Use case QoS for small indoor base station connectivity ..... | 11 |
+| 5.1.1 Description ..... | 11 |
+| 5.1.2 Pre-conditions..... | 11 |
+| 5.1.3 Service Flows ..... | 11 |
+| 5.1.4 Post-conditions ..... | 12 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 12 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 12 |
+| 5.2 Use case visitor access to small indoor base station ..... | 12 |
+| 5.2.1 Description ..... | 12 |
+| 5.2.2 Pre-conditions..... | 13 |
+| 5.2.3 Service Flows ..... | 13 |
+| 5.2.4 Post-conditions ..... | 13 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 13 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.3 Use case of QoS maintenance from outdoor to indoor ..... | 14 |
+| 5.3.1 Description ..... | 14 |
+| 5.3.2 Pre-conditions..... | 14 |
+| 5.3.3 Service Flows ..... | 15 |
+| 5.3.4 Post-conditions ..... | 15 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 15 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 15 |
+| 5.4 Use case on efficient routing between UE and non-3GPP device ..... | 15 |
+| 5.4.1 Description ..... | 15 |
+| 5.4.2 Pre-Conditions ..... | 16 |
+| 5.4.3 Service Flows ..... | 16 |
+| 5.4.4 Post-Conditions ..... | 16 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 16 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 16 |
+| 5.5 Use Case on efficient routing for UE-to-UE communications via residential gateway..... | 17 |
+| 5.5.1 Description ..... | 17 |
+| 5.5.2 Pre-Conditions..... | 17 |
+| 5.5.3 Service Flows ..... | 17 |
+| 5.5.4 Post-Conditions ..... | 18 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 18 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 18 |
+| 5.6 Use case on E2E QoS monitoring..... | 18 |
+| 5.6.1 Description ..... | 18 |
+| 5.6.2 Pre-Conditions..... | 19 |
+| 5.6.3 Service Flows ..... | 19 |
+| 5.6.4 Post-Conditions ..... | 19 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 19 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 20 |
+| 5.7 Provisioning evolved residential gateways and Premises Radio Access Stations ..... | 20 |
+| 5.7.1 Description ..... | 20 |
+| 5.7.2 Pre-conditions..... | 20 |
+| 5.7.3 Service Flows ..... | 20 |
+
+| | | |
+|--------|------------------------------------------------------------------------------------------------------------------------------------------|----|
+| 5.7.4 | Post-conditions ..... | 20 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 20 |
+| 5.8 | Use case on 5G LAN scalability ..... | 21 |
+| 5.8.1 | Description ..... | 21 |
+| 5.8.2 | Pre-conditions..... | 21 |
+| 5.8.3 | Service Flows ..... | 21 |
+| 5.8.4 | Post-conditions ..... | 21 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 22 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 22 |
+| 5.9 | Use case on indoor LAN to 5G LAN connectivity ..... | 22 |
+| 5.9.1 | Description ..... | 22 |
+| 5.9.2 | Pre-conditions..... | 22 |
+| 5.9.3 | Service Flows ..... | 22 |
+| 5.9.4 | Post-conditions ..... | 22 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 23 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 23 |
+| 5.10 | Use case: seamless path switch from a UE-to-UE direct communication to an indirect communication via an evolved residential gateway..... | 23 |
+| 5.10.1 | Description ..... | 23 |
+| 5.10.2 | Pre-conditions..... | 23 |
+| 5.10.3 | Service Flows ..... | 23 |
+| 5.10.4 | Post-conditions ..... | 24 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 24 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 24 |
+| 5.11 | Use case: seamless switching from a service hosting environment to an application server via an evolved residential gateway ..... | 25 |
+| 5.11.1 | Description ..... | 25 |
+| 5.11.2 | Pre-conditions..... | 25 |
+| 5.11.3 | Service Flows ..... | 25 |
+| 5.11.4 | Post-conditions ..... | 26 |
+| 5.11.5 | Existing features partly or fully covering the use case functionality ..... | 26 |
+| 5.11.6 | Potential New Requirements needed to support the use case..... | 26 |
+| 5.12 | Use case: local control of connectivity of UEs in a CPN..... | 27 |
+| 5.12.1 | Description ..... | 27 |
+| 5.12.2 | Pre-conditions..... | 28 |
+| 5.12.3 | Service Flows ..... | 28 |
+| 5.12.4 | Post-conditions ..... | 29 |
+| 5.12.5 | Existing features partly or fully covering the use case functionality ..... | 29 |
+| 5.12.6 | Potential New Requirements needed to support the use case..... | 29 |
+| 5.13 | Use case on IP Traffic offload..... | 29 |
+| 5.13.1 | Description ..... | 29 |
+| 5.13.2 | Pre-Conditions ..... | 30 |
+| 5.13.3 | Service Flows ..... | 30 |
+| 5.13.4 | Post-Conditions ..... | 30 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 30 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 31 |
+| 5.14 | Use case on PRAS sharing..... | 31 |
+| 5.14.1 | Description ..... | 31 |
+| 5.14.2 | Pre-Conditions ..... | 31 |
+| 5.14.3 | Service Flows ..... | 31 |
+| 5.14.4 | Post-Conditions ..... | 32 |
+| 5.14.5 | Existing features partly or fully covering the use case functionality ..... | 32 |
+| 5.14.6 | Potential New Requirements needed to support the use case..... | 32 |
+| 5.15 | Use case multicast service access control for legacy device(s) behind an eRG ..... | 32 |
+| 5.15.1 | Description ..... | 32 |
+| 5.15.2 | Pre-conditions..... | 32 |
+| 5.15.3 | Service Flows ..... | 33 |
+| 5.15.4 | Post-conditions ..... | 33 |
+| 5.15.5 | Existing features partly or fully covering the use case functionality ..... | 33 |
+| 5.15.6 | Potential New Requirements needed to support the use case..... | 33 |
+| 5.16 | Use case on the connection of 5G LAN with fixed IP VPN ..... | 33 |
+
+| | | |
+|--------|-------------------------------------------------------------------------------------------|----|
+| 5.16.1 | Description ..... | 33 |
+| 5.16.2 | Pre-conditions ..... | 34 |
+| 5.16.3 | Service Flows ..... | 34 |
+| 5.16.4 | Post-conditions ..... | 34 |
+| 5.16.5 | Existing features partly or fully covering the use case functionality ..... | 34 |
+| 5.16.6 | Potential New Requirements needed to support the use case..... | 35 |
+| 5.17 | Use case on loss of connectivity between eRG or PRAS and 5GC ..... | 35 |
+| 5.17.1 | Description ..... | 35 |
+| 5.17.2 | Pre-conditions ..... | 35 |
+| 5.17.3 | Service Flows ..... | 35 |
+| 5.17.4 | Post-conditions ..... | 35 |
+| 5.17.5 | Existing features partly or fully covering the use case functionality ..... | 36 |
+| 5.17.6 | Potential New Requirements needed to support the use case..... | 36 |
+| 5.18 | Control of Customer Premises Network by Authorised Administrator ..... | 36 |
+| 5.18.1 | Description ..... | 36 |
+| 5.18.2 | Pre-conditions ..... | 37 |
+| 5.18.3 | Service Flows ..... | 37 |
+| 5.18.4 | Post-conditions ..... | 37 |
+| 5.18.5 | Existing features partly or fully covering the use case functionality ..... | 37 |
+| 5.18.6 | Potential New Requirements needed to support the use case..... | 38 |
+| 5.19 | Use case: eRG supporting Multiple connectivity..... | 38 |
+| 5.19.1 | Description ..... | 38 |
+| 5.19.2 | Pre-conditions ..... | 38 |
+| 5.19.3 | Service Flows ..... | 39 |
+| 5.19.4 | Post-conditions ..... | 39 |
+| 5.19.5 | Existing features partly or fully covering the use case functionality ..... | 40 |
+| 5.19.6 | Potential New Requirements needed to support the use case..... | 40 |
+| 5.20 | Providing 5G Multicast-Broadcast Services (5MBS) for devices through eRG..... | 40 |
+| 5.20.1 | Description ..... | 40 |
+| 5.20.2 | Pre-conditions ..... | 40 |
+| 5.20.3 | Service Flows ..... | 40 |
+| 5.20.4 | Post-conditions ..... | 41 |
+| 5.20.5 | Existing features partly or fully covering the use case functionality ..... | 41 |
+| 5.20.6 | Potential New Requirements needed to support the use case..... | 41 |
+| 5.21 | Identification, Authentication, and Authorization for Premises Radio Access Stations..... | 42 |
+| 5.21.1 | Description ..... | 42 |
+| 5.21.2 | Pre-conditions ..... | 42 |
+| 5.21.3 | Service Flows ..... | 42 |
+| 5.21.4 | Post-conditions ..... | 42 |
+| 5.21.5 | Existing features partly or fully covering the use case functionality ..... | 43 |
+| 5.21.6 | Potential New Requirements needed to support the use case..... | 43 |
+| 5.22 | Use Case for supporting external services behind eRG in CPN ..... | 43 |
+| 5.22.1 | Description ..... | 43 |
+| 5.22.2 | Pre-conditions ..... | 43 |
+| 5.22.3 | Service Flows ..... | 44 |
+| 5.22.4 | Post-conditions ..... | 44 |
+| 5.22.5 | Existing features partly or fully covering the use case functionality ..... | 44 |
+| 5.22.6 | Potential Requirements..... | 44 |
+| 6 | Traffic Scenarios ..... | 45 |
+| 6.1 | Traffic Scenario: inHome ..... | 45 |
+| 6.1.1 | Description ..... | 45 |
+| 6.1.2 | Assumptions ..... | 45 |
+| 6.1.3 | Potential Functional Requirements..... | 46 |
+| 6.1.4 | Potential Key Performance Requirements..... | 46 |
+| 7 | Consolidated requirements..... | 47 |
+| 7.1 | Introduction ..... | 47 |
+| 7.2 | General ..... | 48 |
+| 7.3 | Gateway..... | 48 |
+| 7.4 | Service Discovery ..... | 48 |
+| 7.5 | Application Servers ..... | 49 |
+
+| | | |
+|-------------------------------------------------|--------------------------------------------|-----------|
+| 7.6 | Identification, Privacy, and security..... | 50 |
+| 7.7 | Direct Communications..... | 51 |
+| 7.8 | Connectivity - QoS - charging ..... | 51 |
+| 7.9 | Provisioning ..... | 52 |
+| 7.10 | Premises Radio Access Station ..... | 52 |
+| 7.11 | 5G-LAN ..... | 53 |
+| 7.12 | Broadcast Multicast..... | 53 |
+| 8 | Conclusions and recommendations..... | 53 |
+| Annex A: Resident networks overview..... | | 54 |
+| A.1 | Introduction ..... | 54 |
+| A.2 | Customer Premises Network overview ..... | 54 |
+| A.3 | Customer Premises Network entities ..... | 54 |
+| A.3.1 | evolved Residential Gateway (eRG) ..... | 54 |
+| A.3.2 | Premises Radio Access System (PRAS) ..... | 54 |
+| A.3.3 | Customer Premises Network (CPN)..... | 55 |
+| A.3.4 | User Equipment (UE) ..... | 55 |
+| A.3.3 | Non-3GPP device ..... | 55 |
+| Annex B: Change history..... | | 55 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document examines use cases and traffic scenarios in residential environments (e.g. homes and small offices) and identifies related new potential functional requirements and potential key performance requirements in the following three areas:
+
+- Enhancements for wireline wireless convergence,
+- Enhancements for fixed LAN - 5GLAN integration, and
+- Enhancements for indoor small base stations
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.261: " Service requirements for the 5G system; Stage 1".
+- [3] 3GPP TS 22.220: "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)".
+- [4] 3GPP TS 23.501: "System architecture for the 5G System (5GS)".
+- [5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
+- [6] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
+- [7] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS) "
+- [8] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service (MBMS); Stage 1".
+- [9] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1".
+- [10] 3GPP TR 22.904: "Study on user centric identifiers and authentication".
+- [11] 3GPP TS 22.101: "Service aspects; Service principles".
+- [12] 3GPP TS 22.346: "Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1".
+- [13] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Authorised Administrator:** a user or other entity authorised to partially configure and manage a network node in a CPN (e.g. a PRAS, or eRG).
+
+**Customer Premises Network:** a network located within a premises (e.g. a residence, office or shop), which is owned, installed and/or (at least partially) configured by the customer of a public network operator.
+
+**Evolved Residential Gateway:** a gateway between the public operator network (fixed/mobile/cable) and a customer premises network within a residence, office or shop.
+
+**Hybrid access:** access consisting of multiple different access types combined, such as fixed wireless access and wireline access
+
+**Non-3GPP device:** a non-3GPP device is a device that uses non-3GPP access technology and does not have 3GPP credentials
+
+**Premises Radio Access Station:** a base station installed at a customer premises network primarily for use within a residence, office or shop.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|-------------------------------|
+| CPN | Customer Premises Network |
+| eRG | Evolved Residential Gateway |
+| PRAS | Premises Radio Access Station |
+
+# --- 4 Overview
+
+Many operators around the world both have mobile network and fixed network operations. Operators provide triple-play, combining mobile communication, fixed telephony and broadband Internet, or even quad-play, adding TV, to customers in the consumer / residential market. In this market, operators can distinguish themselves by providing an optimal integration between the different services. Following the trend of wireline/wireless convergence, operators are integrating their fixed and mobile networks into a single core network with fixed and mobile access networks.
+
+Even for single play mobile network operators optimising 5G residential services is relevant. One of the main benefits that 5G brings to consumers is that it will provide higher bitrates. These higher bitrates will enable or improve eMBB services such as mobile TV, AR/VR, or mobile gaming. Remarkably, to a large extend such 'mobile' services are used by users that are not on the move. Generally hourly patterns for mobile data traffic show that the highest mobile data usage is in the evening, when people are enjoying mobile data services whilst at home.
+
+
+
+Figure 4-1: example daily pattern of cellular usage (source KPN). A line graph titled 'Working Day (representative)' showing Downlink (blue line) and Uplink (orange line) traffic over a 24-hour period. The x-axis represents time from 00:00 to 23:45 in 15-minute intervals. The y-axis represents relative traffic volume. The Downlink traffic starts high at 00:00, drops to a minimum around 03:00, then rises sharply to a peak around 12:00, and remains relatively high with some fluctuations until 21:00, after which it drops sharply. The Uplink traffic is much lower, starting low at 00:00, rising slightly to a peak around 12:00, and then remaining relatively stable until 21:00, after which it drops sharply.
+
+**Figure 4-1: example daily pattern of cellular usage (source KPN)**
+
+The pattern of cellular data usage implies that residential environments are very important in 5G usage. The residential environment is where a large portion of 5G traffic will be handled. And the residential environment is not the easiest environment to provide network coverage. With video/TV services and AR/VR gaming, residential users demand high bitrates and with a concentration of media traffic can easily require significant capacities. High bitrates and high capacity are best provided with mmwave frequencies. However, at mmwave frequencies it will be difficult to provide outside-to-inside coverage with operator base stations. Also with indoor base stations, it will not be easy to provide sufficient indoor coverage. Scenarios with a PRAS in every room (e.g. integrated in the light fixture in the centre of the ceiling) may be needed to provide really good in-home coverage. This also requires upgrades to fixed access, residential gateways and in-home cabling. At the same time, it is virtually impossible for an operator to install and manage their own radio access infrastructure in a residential environment. Where in a large office, the operator can provide and manage indoor coverage, in a residential environment the installation of radio equipment, cabling will likely be left to the homeowner (Authorised Administrator).
+
+Currently fixed broadband services work on a different premise than mobile services. With mobile services, each individual device is known and identifiable in the mobile network. That implies that services can be provided to individual devices. With fixed broadband services, the operator provides Internet access to a residential gateway. Behind that residential gateway is usually a LAN, but individual devices on that LAN are not known or identifiable in the core network. For an integrated fixed broadband / mobile residential 5G offering, it would be beneficial if devices behind an eRG can also be known and identified in the core network.
+
+The trend towards Wireline / Wireless Convergence is already recognised in 3GPP. In collaboration with the BroadBand Forum (BBF), architecture solutions have been specified where a single 5G core network is used to also control fixed broadband access. Also, solutions like 5G LAN and UE relaying have been specified with residential use cases (partly) in mind. Nevertheless, there are still areas where improvements for residential use are needed/useful to achieve the vision of a residential 5G without boundaries between fixed broadband and mobile.
+
+# --- 5 Use cases
+
+## 5.1 Use case QoS for small indoor base station connectivity
+
+### 5.1.1 Description
+
+In many cases, residential indoor coverage will require the deployment of indoor base stations or access points. Especially for multimedia services like UHD TV, or AR/VR gaming high bitrates are needed. This in turn requires the use of higher frequency bands (e.g. 3.5 GHz or 26/28 GHz for NR or 5 GHz, 6 GHz or 60 GHz for WiFi based radio access). At these frequencies, outdoor to indoor coverage from an outdoor PLMN is challenging. Also indoor penetration throughout a house is problematic, requiring multiple Premises Radio Access Stations (PRASs).
+
+For 5G services that require specific QoS (e.g. guaranteed bitrate, latency) or e.g. that rely on edge applications, it is important that the 5G network can differentiate the related service data flows in order to treat them accordingly. This also applies in case a PRAS is connected via an evolved Residential Gateway (eRG) and an indoor infrastructure. In the Wireline Wireless Convergence work between 3GPP and BBF, the eRG is seen as an UE. That way the eRG can request QoS for the fixed access network. Also on the radio interface between the UE and the PRAS, QoS control can work as normal. An issue however is how QoS is provided on the backhaul between the PRAS and the eRG and in the eRG. It is not guaranteed that this backhaul has sufficient QoS. Also prioritization of specific service data flows may be needed to provide the expected QoS. Finally, the eRG may have to request specific QoS for the fixed access network for specific service data flows.
+
+Note: in the use case, we generally refer to PRAS, but the similar requirements apply for e.g. a WiFi6 access point that is connected to the 5G core (non-3GPP access) via an eRG.
+
+### 5.1.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- A PRAS is deployed inside a residential home.
+- The PRAS provides access to the 5G system (e.g not local IP access)
+- UEs using the PRAS have individual subscriptions to access the 5G system.
+- The Premises Radio Access Stations (PRAS) is connected to an eRG
+- The eRG is connected to the same 5G system (and has a subscription to the same 5G system) as the PRAS.
+
+### 5.1.3 Service Flows
+
+Teenagers Oliver and Scott are avid gamers. They get together in the games room in the basement of Scott's house and discuss the new game that has become available that day. Scott decides to download the new game on his laptop. The size of that game is over 100 Gbyte so even on 5G it will take a while. Good thing that Scott's parents had PRASs installed in the house. 5G coverage would otherwise have been dismal in the basement and downloading would have taken forever.
+
+While the game is downloading, Oliver and Scott decide to play their favorite multi-user AR/VR game. Each put on a VR headset, get a controller and start gaming. The AR/VR game they play is cloud based with rendering in an edge node. This way they can play the game wherever they want and still have optimal quality of experience. The low latency ensures they have no 'lag' when they move their head or when they try to shoot each other in the game. Good thing also that the 5G system makes sure that the AR/VR game is prioritized over downloading the game. That the download takes a bit more time is not a big issue, but without the usual settings for frames per second and resolution or with additional lag because of the download the game would be 'unplayable'.
+
+### 5.1.4 Post-conditions
+
+The game consoles have set up a 5G connection to the Premises Radio Access Stations (PRAS). They have requested the same session with the same QoS, DNN, Slice, et cetera as they would have done with an outdoor base station.
+
+The eRG ensures that prioritization within the eRG and Customer Premises Network takes requested QoS into account. This e.g. implies that the AR/VR game gets priority over the downloading of the game.
+
+The eRG also ensures that the 5G core network can differentiate the service data flows for the AR/VR games from general Internet access, to ensure that specific handling of these service data flows (e.g. routing to an edge node) is possible.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.220 "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)" [3] specifies requirements for indoor base stations in a 3G (HNB) or 4G (HeNB) context. It is not very clearly specified whether these requirements also apply for 5G. Requirements are included to request resources from the IP backhaul in the fixed broadband access. Note that 3GPP TS 22.220 [3] does not assume WWC convergence. There are no requirements for the provision of QoS within the Customer Premises Network itself.
+
+3GPP TS 22.261 [2], clause 6.26.2.1 mentions indoor small base stations connected in the context of 5GLAN: "The 5G system shall enable the network operator to provide the same 5G LAN-type service to any 5G UE, regardless of whether it is connected via public base stations, indoor small base stations connected via fixed access, or via relay UEs connected to either of these two types of base stations."
+
+3GPP TS 22.261 [2], clause 6.3.2.4 discusses fixed broadband access. It does not really use WWC terminology (e.g. 5G-RG), but either assumes a residential gateway that functions as a relay UE, or a residential gateway that integrates an indoor base station. There is no mentioning of a base station that is connected to the residential gateway. 3GPP TS 23.316 [7] is the architecture specification for Wireline Wireless Convergence.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+[PR. 5.1.6-001] The 5G system shall enable the network operator to provide any 5G services to any 5G UE via a Premises Radio Access Station (PRAS) connected via an evolved Residential Gateway (eRG).
+
+NOTE1: The eRG may be connected via fixed access, via 5G Fixed Wireless Access, or hybrid access.
+
+NOTE2: The PRAS may also be co-located with the eRG
+
+[PR. 5.1.6-002] The 5G system shall enable the evolved Residential Gateway (eRG) to provide backhaul with the required QoS for the services provided via a Premises Radio Access Station (PRAS) connected via the eRG.
+
+NOTE3: Backhaul for the PRAS includes the Customer Premises Network between PRAS and eRG and the (fixed) access network between the eRG and the 5G core network.
+
+## 5.2 Use case visitor access to small indoor base station
+
+### 5.2.1 Description
+
+In many cases, residential indoor coverage will require the deployment of Premises Radio Access Stations (PRASs). The assumption is that these PRASs are installed by the home owner (Authorised Administrator). Nevertheless, it is quite possible that these PRASs can also be used by visitors to the home.
+
+Visitor access is only possible with a few security provisions. Communication for the visitor has to be protected against eavesdropping or manipulation in the residential in-home network and/or evolved residential gateway. These elements are not under control of the operator and cannot be sufficiently trusted.
+
+From the other hand, the homeowner needs to be shielded from the visitor. One aspect is that the homeowner may not want to be charged for traffic, services, and applications initiated by the visitor. Another aspect is that the homeowner may not want the visitor to access his private devices in the home (e.g., working PCs, security cameras, etc.) via PRAS and evolved residential gateway. For example, when the visitor's UE is connecting to the eRG, may receive unintended
+
+broadcast communication/data from the homeowner's devices, which are also connecting to the eRG. Also for lawful intercept, traffic originating from a visitor should be identifiable as such.
+
+In existing customer premises networks, generally internal credentials are used (e.g. WiFi username/password). Using 3GPP credentials to access a CPN will be an improvement of security and will relieve the home owner of having to manage (and remember) CPN internal credentials.
+
+### 5.2.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- A PRAS is deployed inside a residential home.
+- The PRAS provides access to the 5G system (e.g. not local IP access)
+- UEs using the PRAS have individual subscriptions to access the 5G system, these subscriptions may be with different operators.
+- The PRAS is connected to an eRG
+- The eRG is connected to the same 5G system (and has a subscription to the same 5G system) as the PRAS.
+
+### 5.2.3 Service Flows
+
+Doctor Joe is a general practitioner (GP) that works from a practice next to his home in a small village. Every day patients visit his practice for all kinds of consultations.
+
+Because of the local radio conditions (small village) and the construction of his home (concrete walls), there is very poor outdoor-to-indoor coverage in his practice. Doctor Joe has therefore installed Premises Radio Access Stations (PRASs) in his practice, both for himself and for waiting patients.
+
+Doctor Joe is happy that 3GPP credentials can be used for communication within the CPN. He no longer has to manage and configure username/password combinations for his devices and security is improved; he no longer needs the sticky note with the WiFi password he had on his computer.
+
+Doctor Joe does not mind that patients are using the PRAS that he has paid for. However, Doctor Joe does not want to pay for traffic, services, or applications that his patients may initiate via his PRAS and fixed access. Doctor Joe also does not want that these patients are able to access his PC or control the lights/cameras via his PRAS and eRG. Furthermore, he does not want to get in trouble when patients e.g. download illegal content via his fixed access. Therefore, Doctor Joe prefers that communication from/for his patients is identified as such.
+
+Patient Mary is waiting in the waiting room. She wants to communicate in private with her mother. Even though she is using a PRAS installed by Doctor Joe, she can trust that her communication remains private.
+
+### 5.2.4 Post-conditions
+
+Communication for each patient is identified and billed separately from the traffic from Doctor Joe and other patients.
+
+Communication for patients cannot be eavesdropped or manipulated.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.220 "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)" [3] specifies requirements for indoor base stations in a 3G (HNB) or 4G (HeNB) context. It is not very clearly specified whether these requirements also apply for 5G. 3GPP TS 22.220 [3] also includes requirements on security and privacy.
+
+3GPP TS 22.261 [2], clause 6.26.2.1 mentions indoor small base stations in the context of 5GLAN: "The 5G system shall enable the network operator to provide the same 5G LAN-type service to any 5G UE, regardless of whether it is connected via public base stations, indoor small base stations connected via fixed access, or via relay UEs connected to either of these two types of base stations."
+
+3GPP TS 22.261 [2], clause 6.3.2.4 discusses fixed broadband access and the use of a home base station. It mentions: "The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access)."
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR. 5.2.6-001] The 5G system shall enable the network operator to provide any 5G services via a Premises Radio Access Station (PRAS) to any 5G UE with a valid subscription to the HPLMN associated with the PRAS.
+
+[PR. 5.2.6-002] The 5G system shall enable the network operator to provide any 5G services via a Premises Radio Access Station (PRAS) to any 5G UE with a valid subscription to any VPLMN that has a roaming agreement with the HPLMN.
+
+NOTE: Whether 5G UEs from VPLMNs in the same country as the HPLMN can use the PRAS is subject to regulatory policy on national roaming.
+
+[PR. 5.2.6-003] The 5G system shall ensure the use of a Premises Radio Access Station (PRAS) does not compromise the security of any PLMN or broadband access network.
+
+[PR. 5.2.6-004] The 5G system shall ensure the use of a Premises Radio Access Station (PRAS) does not compromise the security of the UE. The PRAS (and its associated backhaul connectivity) shall provide a level of security equivalent to regular 5G base stations.
+
+[PR. 5.2.6-005] The 5G system shall enable the network operator associated with the Premises Radio Access Station (PRAS) to control the security policy of the PRAS.
+
+[PR. 5.2.6-006] The 5G system shall ensure the Premises Radio Access Station (PRAS) does not compromise user privacy for UEs that are using the PRAS, including communication confidentiality, location privacy and identity protection.
+
+[PR. 5.2.6-007] The 5G system shall be able to generate charging information that can differentiate between UEs connected to the Premises Radio Access Station (PRAS) and between backhaul for the PRAS and other data traffic over the same access.
+
+[PR. 5.2.6-008] The 5G system shall provide a mechanism to prevent or allow a (guest) UE to discover and/or use the services provided by the devices on the CPN.
+
+[PR. 5.2.6-009a] The 5G system shall support authentication of a UE with 3GPP credentials for communication with entities (UEs, devices) in a CPN.
+
+NOTE: To support this functionality the CPN needs to be connected with the 5G core network.
+
+[PR. 5.2.6-009] The 5G system shall ensure that communications associated with individual UEs in a CPN be identifiable (e.g., subscriber identifier) in the 5G network.
+
+## 5.3 Use case of QoS maintenance from outdoor to indoor
+
+### 5.3.1 Description
+
+UEs can get all way QoS support from the 5G system when accessing the network with 3GPP RATs outdoors. However, due to the issue of 5G outside-to-inside coverage, UEs will probably access to 5GC through an evolved residential gateway (eRG) when moving from outdoor to indoor. If the all way QoS control can still be guaranteed at this moment, especially when high bandwidth or low latency consuming service is ongoing (e.g. video gaming), users might have a better service experience.
+
+### 5.3.2 Pre-conditions
+
+Tom has a mobile phone which is registered to MNO1. Tom loves to play video game at his leisure time. He even made a specific QoS setting with MNO1 to guarantee the high quality of the gaming service.
+
+There is a eRG at Tom's house. The eRG also subscribes to the same MNO as Tom's mobile phone. Devices in Tom's house can automatically be connected to the eRG via non-3GPP (R)ATs (e.g. WIFI).
+
+### 5.3.3 Service Flows
+
+1. Tom is on his way home by bus. It is so boring, so he starts playing video game on his mobile phone.
+2. An hour later Tom arrives home. The video game is so exciting and fierce, so Tom is still obsessed with it. He keeps playing game when he enters the house.
+3. Once Tom enters the house, his mobile phone is automatically connected to the eRG. So that his mobile phone can still access to the network.
+4. The eRG identifies Tom's mobile phone.
+5. The eRG is informed of the relevant QoS characteristics of Tom's mobile phone at this moment.
+6. The 5G network and the eRG provide corresponding QoS control for Tom's mobile phone.
+
+### 5.3.4 Post-conditions
+
+Even if Tom moves from outdoor to indoor while playing UHD video game, the quality of the video game he's playing can be well maintained. Tom can still have a wonderful service experience.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2], clause 6.7.2 mentions the support of harmonised QoS framework to multiple accesses : "The 5G system shall be able to support a harmonised QoS and policy framework applicable to multiple accesses. "
+
+3GPP TS 22.261 [2], clause 6.26.2.8 mentions QoS requirement between remote UE and relay UE: "The 5G network shall be able to provide a remote UE using 5G LAN-type service with same level of service as if the remote UE would be using a direct network connection (i.e. provide required QoS for the Ethernet packets transferred between remote UE and relay UE if they are using 3GPP access)."
+
+3GPP TS 22.261 [2], clause 8.5 mentions different identifier association: "The HPLMN shall be able to associate a temporary identifier to a UE's subscriber identity." But it doesn't specify whether other entity (e.g., evolved residential gateway) can also perform the identity association.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR. 5.3.6-002] The 5G system shall be able to indicate to the evolved residential gateway that a specific UE connected to it either via 3GPP RAT or non-3GPP (R)AT needs specific QoS and what the required QoS characteristics are.
+
+[PR 5.3.6-003] The 5G system shall minimize service disruption for a UE that is moving between CPN access and operator provided mobile access.
+
+NOTE: CPN access can imply access via a PRAS or can imply access directly via an eRG. Operator provided mobile access implies access via an operator owned base station.
+
+## 5.4 Use case on efficient routing between UE and non-3GPP device
+
+### 5.4.1 Description
+
+This use case assumes that Premises Radio Access Stations were already deployed in individual rooms behind the Evolved Residential Gateway, to provide better cellular coverage at home. This use case is to enable efficient routing for the communications between UE and non-3GPP device via the Evolved Residential Gateway.
+
+
+
+Diagram illustrating efficient routing between a UE and a non-3GPP device. A residential home contains two Premises Radio Access Stations (RANs). A smartphone (UE) connects to the top RAN, and a 4K TV (non-3GPP device) connects to the bottom RAN. Both RANs are connected to an Evolved Residential Gateway (eRG). The eRG is connected to a Macro base station, which is in turn connected to the 5GC (5G Core Network). A yellow arrow shows the data path from the smartphone, through the top RAN, to the eRG, and then to the 4K TV via a wireline connection.
+
+**Figure 5.4.1-1: efficient routing between UE and non-3GPP device**
+
+### 5.4.2 Pre-Conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- Multiple Premises Radio Access Stations were deployed in individual rooms inside a residential home
+- The Premises Radio Access Station provides cellular access to UEs
+- The Premises Radio Access Station is connected to an Evolved Residential Gateway via wireline or wireless link
+
+In particular, a Premises Radio Access Station is deployed in the living room.
+
+There is a smart TV in the living room, which is a non-3GPP device, connecting to the Evolved Residential Gateway via wireline.
+
+### 5.4.3 Service Flows
+
+Alice is sitting in the living room. Her smartphone is connecting to the Premises Radio Access Station.
+
+Alice finds an interesting video in her smartphone and want to project to the smart TV in the living room.
+
+The request sent from the smartphone reaches the Evolved Residential Gateway via the Premises Radio Access Station and then routed by the residential gateway to the smart TV via the wireline.
+
+### 5.4.4 Post-Conditions
+
+Alice could enjoy the video on her smart TV.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.220 "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)" [3] specifies the requirements for local IP Access for 3G and 4G.
+
+3GPP TS 22.261 [2] specifies the requirements for routing efficiency, e.g., private communication for 5G LAN-type service, however, the efficient routing on Evolved Residential Gateway is not covered yet.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+[PR. 5.4.6-001] Subject to regulatory requirements and operator policy, the 5G system shall support an efficient data path through an Evolved Residential Gateway for intra-CPN data traffic to or from a UE.
+
+NOTE: For services an operator deploys in the 5G network (i.e. not in the CPN), local data routed via eRG does not apply.
+
+## 5.5 Use Case on efficient routing for UE-to-UE communications via residential gateway
+
+### 5.5.1 Description
+
+This use case assumes that multiple Premises Radio Access Stations were already deployed in individual rooms behind an Evolved Residential Gateway, in order to provide better coverage at home. This use case is to enable efficient routing for the communications between two UEs via the Evolved Residential Gateway.
+
+
+
+Diagram illustrating efficient routing for UE-to-UE communications via a residential gateway. A house contains two Premises Radio Access Stations (one in the attic, one in the basement) connected to an Evolved Residential Gateway (eRG). The eRG is connected to a Macro base station, which is connected to the 5GC. A smartphone in the attic is connected to the top Premises Radio Access Station, and a security sensor in the basement is connected to the bottom Premises Radio Access Station. A yellow arrow shows the communication path from the smartphone, through the top Premises Radio Access Station, to the eRG, then to the Macro base station, then to the 5GC, and finally back to the eRG, then to the bottom Premises Radio Access Station, and finally to the security sensor.
+
+Figure 5.5.1-1: efficient routing for UE-to-UE communications via residential gateway
+
+### 5.5.2 Pre-Conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- Multiple Premises Radio Access Stations were deployed in individual rooms inside a residential home.
+- The Premises Radio Access Station provides cellular access to UEs
+- The Premises Radio Access Station is connected to an Evolved Residential Gateway via wireline or wireless link
+- The Evolved Residential Gateway is connected to the same 5G system (and has a subscription to the same 5G system) as the Premises Radio Access Station belongs to.
+
+In particular, one Premises Radio Access Station is deployed at the attic and another one is deployed at the basement. The connections between the Premises Radio Access Stations and the Evolved Residential Gateway could have multiple options, e.g., fiber, WiFi, or 3GPP licensed spectrum.
+
+A security sensor is deployed at the basement which is capable of detecting smoke or fire. The sensor having a SIM is a 3GPP-capable UE which is connecting to the Premises Radio Access Station in the basement.
+
+### 5.5.3 Service Flows
+
+Alice is working alone at home, staying in her office in the attic. Her smartphone is connecting to the Premises Radio Access Station deployed in the attic.
+
+Suddenly there is a fire in the basement.
+
+The security sensor detects the fire and smoke, and then immediately sends an alarm to Alice's smartphone.
+
+The alarm message first reaches the Evolved Residential Gateway via the Premises Radio Access Station in the basement, and then routed by the Evolved Residential Gateway to Alice smartphone via the Premises Radio Access Station in the attic.
+
+### 5.5.4 Post-Conditions
+
+Alice reads the alarm message from her smartphone. After double-check the situations in the basement, Alice makes the call to the fire policy.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+The 5G system shall support on-demand establishment of UE to UE, multicast, and broadcast private communication between members UEs of the same 5G LAN-VN. Multiple types of data communication shall be supported, at least IP and Ethernet.
+
+3GPP TS 22.261 [2] specifies the requirement to support E2E QoS for a service, however, the existing requirement only consider QoS in the access networks, backhaul, core network and network to network interconnect. The QoS between UE, PRAS and eRG is not covered yet.
+
+3GPP TS 22.261 [2] specifies the requirements for routing efficiency within the 5GC, e.g., private communication for 5G LAN-type service. However, the efficient routing on eRG is not covered yet.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR. 5.5.6-001] The 5G system shall be able to provide QoS control for the communication path between a UE and an Evolved Residential Gateway via a Premises Radio Access Station.
+
+[PR. 5.5.6-002] Subject to regulatory requirements and operator policy, the 5G system shall support an efficient data path through an Evolved Residential Gateway for intra-CPN data traffic to or from a UE. routing efficiency for data traffic between two UEs through an Evolved Residential Gateway.
+
+NOTE: For services an operator deploys in the 5G network (i.e. not in the CPN), local data routed via eRG does not apply.eway.
+
+[PR. 5.5.6-003] The 5G system shall support a mechanism to minimize the security impact on any PLMN or broadband access network when using an Evolved Residential Gateway.
+
+[PR. 5.5.6-004] The 5G system shall support a mechanism to minimize the security impact on the UE when using an Evolved Residential Gateway.
+
+[PR. 5.5.6-005] The 5G system shall enable the network operator associated with an Evolved Residential Gateway to control the security policy of an Evolved Residential Gateway.
+
+[PR 5.5.6-006] The 5G system shall ensure an Evolved Residential Gateway does not compromise user privacy for UEs that are using the Evolved Residential Gateway, including communication confidentiality, location privacy and identity protection.
+
+[PR. 5.5.6-007] The 5G system shall support QoS control for intra-CPN data traffic between two UEs through an Evolved Residential Gateway.
+
+## 5.6 Use case on E2E QoS monitoring
+
+### 5.6.1 Description
+
+This use case assumes that multiple PRASs were already deployed in individual rooms behind an eRG, in order to provide better cellular coverage at home. This use case is to enable E2E QoS monitoring for the whole communication path, i.e., from/to a UE to/from the 5GC via a PRAS and an eRG.
+
+
+
+Diagram illustrating E2E QoS monitoring. A residential home contains multiple Premises Radio Access Stations (PRAS). One PRAS is connected via a wireline or wireless link to an evolved Residential Gateway (eRG). The eRG is connected to a 5G Core Network (5GC) via a fixed access link. A smartphone (UE) is connected to the PRAS. A video server in the cloud is connected to the 5GC. A red arrow labeled 'E2E QoS monitoring' shows the path from the video server, through the 5GC, eRG, and PRAS to the smartphone. A green arrow shows data flow from the 5GC, through the eRG, to the PRAS, and then to the smartphone. A macro base station is shown outside the house, connected to the 5GC.
+
+**Figure 5.6.1-1. E2E QoS monitoring**
+
+### 5.6.2 Pre-Conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- Multiple Premises Radio Access Stations were deployed in individual rooms inside a residential home.
+- The Premises Radio Access Station provides cellular access to UEs
+- The Premises Radio Access Station is connected to an Evolved Residential Gateway via wireline or wireless link
+- The Premises Radio Access Station is connected to the same 5G system (and has a subscription to the same 5G system) as the Premises Radio Access Station belongs to.
+
+In particular, a Premises Radio Access Station is deployed in the living room.
+
+### 5.6.3 Service Flows
+
+Alice sits in the living room and her smartphone connects to the Premises Radio Access Station.
+
+Alice is watching an interesting video on her smartphone. The smartphone downloads the video content in real time from the video application server in the cloud.
+
+After a while, the download speed becomes slow and the video is stuck.
+
+Alice makes a call to the network operator and reports the downgrade of the network performance.
+
+The network operator checks the E2E QoS status and identifies there is heavy interference on the Premises Radio Access Station. The network operator reconfigures the Premises Radio Access Station and recovers the E2E QoS.
+
+### 5.6.4 Post-Conditions
+
+The download speed recovers normal and Alice could continue enjoy the video.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] Section 6.23.2 "QoS monitoring".
+
+The 5G system shall be able to provide information that identifies the type and the location of a communication error for the Premises Radio Access Station (e.g. the ID of this Premises Radio Access Station).
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR. 5.6.6-001] The 5G system shall provide a mechanism for supporting real time E2E QoS monitoring for the data traffic path (i.e., from/to a UE to/from the 5GC via a Premises Radio Access Station and a Evolved Residential Gateway).
+
+## 5.7 Provisioning evolved residential gateways and Premises Radio Access Stations
+
+### 5.7.1 Description
+
+The use case illustrates how an evolved residential gateway or a Premises Radio Access Station can be connected and automatically provisioned to the operator's 5G network.
+
+### 5.7.2 Pre-conditions
+
+Ali has a home connectivity service subscription and a 5G subscription on his mobile phone with Network Operator Vanilla.
+
+Ali purchased an evolved residential gateway and one (or more) Premises Radio Access Stations, which were not provided by the operator.
+
+NOTE: it is assumed the evolved residential gateway is a fixed wireless access (FWA) gateway
+
+Ali is at home and has his mobile phone nearby.
+
+### 5.7.3 Service Flows
+
+1. Ali switches both the evolved residential gateway and Premises Radio Access Station on for the first time.
+2. Ali logs on to his account on Vanilla's portal to add both devices to his Vanilla account and to enable the devices in his home.
+3. Vanilla's 5G core network provisions both the evolved residential gateway and Premises Radio Access Station. Once this process is complete, both the evolved residential gateway and Premises Radio Access Station are successfully connected to Vanilla's core network and are now fully operational.
+4. Ali can now connect his TV to the Premises Radio Access Station in order to stream a movie.
+
+### 5.7.4 Post-conditions
+
+The evolved residential gateway and Premises Radio Access Station have been provisioned automatically with minimum user interaction.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+There are existing features that support remote provisioning, such as via support of (un-)trusted non-3GPP access 3GPP TS 23.501 [4]. Remote provisioning of H(e)NBs is defined in 3GPP TS 22.220 [3], which includes verification and configuration of H(e)NB identity, initial OA&M provisioning.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR 5.7.6-001] The 5G system shall provide mechanisms for the network operator or an Authorised Administrator (e.g. a homeowner) to trigger remote provisioning of evolved residential gateways and for the network operator to perform remote provisioning of eRGs, which includes verification and configuration of evolved residential gateway identity and initial OA&M provisioning.
+
+[PR 5.7.6-002] The 5G system shall provide mechanisms for the network operator or an Authorised Administrator (e.g. a homeowner) to trigger remote provisioning of Premises Radio Access Stations and for the network operator to perform remote provisioning of PRASs, which includes verification and configuration of Premises Radio Access Station identity and initial OA&M provisioning.
+
+## 5.8 Use case on 5G LAN scalability
+
+### 5.8.1 Description
+
+5G houses will aim to connect a diverse quantity of devices ranging from multimedia entertainment, laptops, tables to security cameras. This use case presents a house where all the devices are 5G devices. These devices belong to different 5G LAN-VNs deployed at the house.
+
+1. Basis 5G LAN-VN: for the TV, tablet, phones, other multimedia and entertainment devices.
+2. Work 5G LAN-VN.
+3. House security 5G-LAN VN: including security cameras and other security systems.
+4. Home control/automation 5G LAN-VN.
+
+Different family members have access to the different 5G LAN-VN. While all the family members have access to the basis and home control 5G LAN-VN, only the mom has access to the work 5G LAN-VN who connect her to her office. Dad and mom are the only ones with access to both house security 5G LAN-VN.
+
+Nevertheless, these devices may have different owners or users. The owner of the 5GLAN may decide that different users have access to different devices in a configurable way.
+
+### 5.8.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- All devices at the house are 5G devices.
+- A premises radio access station is deployed inside a residential home.
+- The premises radio access station provides access to the 5G system (e.g not local IP access)
+- UEs using the premises radio access station have individual subscriptions to access the 5G system.
+- The premises radio access station is connected to a evolved Residential Gateway (eRG)
+- The eRG is connected to the same 5G system (and has a subscription to the same 5G system) as the premises radio access station belongs to.
+
+Multiple premises radio access stations are deployed in the home and connected to the evolved residential gateway.
+
+### 5.8.3 Service Flows
+
+Teenagers Oliver and Scott are avid gamers. They get together in the games room in the basement of Scott's house. While they are playing, they heard weird noises from the outside. Scott access to the home control 5G-LAN VN to switch on the lights and check inside. Scott cannot the security cameras and alarm system and he calls his father to check that everything is ok in the different entrances of the house and the garden.
+
+After checking that everything is ok Scott's father decides to Scott is old enough, so he picks up his phone and he configures the system so Scott has now access and can access the security cameras.
+
+### 5.8.4 Post-conditions
+
+Scott has now access and can access the security cameras.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+A 5G system shall support 5G LAN-VNs with member UEs numbering between a few to tens of thousands.
+
+3GPP TS 23.501 [4] clause 5.29.2 contains a statement: "The 5G VN Group management can be configured by a network administrator or can be managed dynamically by AF". Not sure if "network administrator" implies a PLMN administrator or an authorized user for the specific 5GLAN VN-Group. Dynamic management by AF, seems to require additional functionality as a user cannot directly access an AF.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR. 5.8.6-001] The 5G system shall be able to support large amounts of small 5G LAN-VNs targeting residential deployments.
+
+NOTE: Targeting residential requirements translate into millions of 5GLAN-VN per operator per country. These 5G LAN-VNs may contain between 10-50 devices per LAN
+
+[PR. 5.8.6-002] The 5G system shall support authorized 3rd parties to authorize/deauthorize UEs to be able to access a 5G LAN-VN.
+
+## 5.9 Use case on indoor LAN to 5G LAN connectivity
+
+### 5.9.1 Description
+
+5G LAN-VNs aim to provide 5G UEs with similar functionalities to Local Area Networks (LANs) and VPN's but improved with 5G capabilities (e.g. high performance, long distance access, mobility and security). Nevertheless, not every home device will be 5G devices. The use of evolved Residential Gateways that can interact between 5G-LAN VNs and in-home LAN networks, can allow interaction between devices belonging to both deployments.
+
+### 5.9.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- There is a 5G LAN with 5G UEs.
+- The home also comprises a in-home LAN with non-3GPP devices.
+- There is an evolved Residential Gateway (eRG) that connects the in-home LAN with the public network
+
+### 5.9.3 Service Flows
+
+Tom updated his house during the last years into a fully smart house. The lights, kitchen facilities like the coffee machine and his multimedia entertainment system are connected to an in-home LAN deployed at the house.
+
+Tom decides to update the fixed broadband access to his house with a new evolved Residential Gateway (eRG).
+
+NOTE: Tom's operator has deployed Wireline-Wireless Convergence, which implies that the eRG is preceived as a UE by a 5G Core Network common for wireline and wireless access.
+
+Tom also decides to get a subscription to 5G LAN services. All his mobile devices (e.g. mobile phone, tablet, laptop) are added to the 5G LAN. However, he cannot yet get access to the devices on the in-home LAN from his mobile devices.
+
+Tom now includes his eRG into his 5G-LAN VN. The eRG now allows his mobile devices on the 5G-LAN to connect to the devices on his in-home LAN.
+
+### 5.9.4 Post-conditions
+
+Tom can access devices on the LAN network of the house now with his 5G-phone.
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+[PR. 5.9.6-001] The 5G system shall support the use of an evolved Residential Gateway to connect 5G devices from the 5G LAN VN it belongs to with non-3GPP devices on an in-home LAN.
+
+## 5.10 Use case: seamless path switch from a UE-to-UE direct communication to an indirect communication via an evolved residential gateway
+
+### 5.10.1 Description
+
+This use case is depicted in Figure 5.10.1-1. It shows the scenario where two UEs have been in direct communication via a first path (Path #1) using 3GPP technology, but as the two UEs move apart from each other, they have to switch seamlessly to an indirect communication via one of the paths (Path #2, or Path #3) using 3GPP technology.
+
+NOTE: The figure is not intended to capture all potential paths that might exist.
+
+
+
+The diagram shows a building with two floors. On Floor 2, UE1 and UE2 are connected via a direct green path labeled 'Path #1'. On Floor 1, UE1 is connected to PRAS 2, which is connected to an evolved Residential Gateway (eRG). UE2 on Floor 2 is also connected to PRAS 1, which is connected to the eRG. The eRG is connected to an Access Network, which is connected to the 5G Core Network. The 5G Core Network is connected to an Application Server and a Service Hosting Environment. Path #2 is an orange path from UE1 on Floor 1 through PRAS 2 and the eRG. Path #3 is a purple path from UE2 on Floor 2 through PRAS 1 and the eRG. Both paths #2 and #3 lead to the 5G Core Network.
+
+Diagram illustrating seamless switching from a direct UE-to-UE path to an indirect path via an evolved residential gateway (eRG).
+
+**Figure 5.10.1-1. Seamless switching from a direct UE-to-UE path to an indirect path going through an evolved residential gateway.**
+
+### 5.10.2 Pre-conditions
+
+Multiple Premises Radio Access Stations (PRASs) are deployed in the home (building) for serving different floors or rooms and interconnected via the eRG. The eRG is connected to the 5G-CN and the PRASs are connected to the 5G-CN via the eRG. UEs that are connected to PRASs can enjoy services offered by a Service Hosting Environment in the 3GPP network, and/or an Application Server (AS) via the eRG.
+
+### 5.10.3 Service Flows
+
+We consider a scenario where two UEs, UE1 and UE2, are connected via a 3GPP direct communication path (Path #1 in this example). Both UEs are assumed to be in proximity of one another (e.g. on the same floor) while enjoying their service via the direct link. An event occurs that triggers the move of UE1 away from UE2. While the UE1 moves away from UE2, it is the expectation of both UEs to continue their service seamlessly with the same QoS albeit through an indirect communication path via the network. Below we present the service flows:
+
+1. UE1 (e.g. smartphone or tablet) and UE2 (e.g. laptop) are both on the same floor (Floor 2 in this example) in the home and connected to each other via 3GPP direct communication path (Path #1 in this example). UE1 is receiving a direct service from UE2. This service has a specific QoS (e.g. latency sensitive).
+2. UE1 moves to another floor (Floor 1 in this example) whilst maintaining its service with UE2 with the same specific QoS.
+3. As the direct communication path (Path #1) between UE1 and UE2 degrades because the two UEs move apart, UE1 connects automatically to PRAS 2 while UE2 connects automatically to PRAS 1.
+4. The UE1-UE2 service is maintained with the same QoS through the indirect communication path (Path #2 in this example).
+
+### 5.10.4 Post-conditions
+
+The UE1-UE2 service is continued through indirect communication path going via the evolved residential gateway with the same QoS as through the original direct communication path.
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] clause 6.2.3 Service continuity: Requirements
+
+The 5G system shall support service continuity for a remote UE, when the remote UE changes from a direct network connection to an indirect network connection and vice-versa.
+
+3GPP TS 22.261 [2] clause 6.7.2: Priority, QoS, and policy control: Requirements
+
+The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
+
+NOTE: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
+
+The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
+
+3GPP TS 22.261 [2] clause 7.6.1 AR/VR: Gaming and Training Data Exchanging
+
+This use case is characterized by the exchange of the gaming or training service data between two 5G AR/VR devices.
+
+3GPP TS 22.278 [5]: clause 7A.1 includes requirements on managing the switch from a direct communication path to an indirect communication path. These requirements are addressed in 3GPP TS 23.287 [6].
+
+3GPP TS 22.261 [2] clause 6.23.2 includes requirements for QoS Monitoring which are addressed in 3GPP TS 23.501 [4] clause 5.33.3 QoS Monitoring to Assist URLLC Service.
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+[PR 5.10.6-001] The 5G system shall be able to minimize disruption to the user when a UE switches from a direct communication path between the UEs to an indirect communication path going through the eRG and there is connectivity to the 5G system.
+
+[PR 5.10.6-002] The 5G system shall support real time E2E QoS monitoring and control for any data traffic path (i.e. from/to a UE to/from the 5GC and to/from another UE) via a PRAS and an eRG when there is connectivity to the 5G system.
+
+NOTE 1: Related requirements on QoS are also outlined in clause 5.1 and clause 5.7.
+
+NOTE 2: The above requirements may result in no new stage 2/3 work unless it is shown there is impact from introducing the PRAS/eRG in the path.
+
+## 5.11 Use case: seamless switching from a service hosting environment to an application server via an evolved residential gateway
+
+### 5.11.1 Description
+
+This use case describes a scenario of service continuity for a UE consuming a low latency service provided by a service hosting environment. The low latency service (e.g. gaming) is maintained with the same QoS settings as the UE moves from the service hosting environment to an Application Server (AS) connected to an evolved Residential Gateway (eRG). While the AS can be a standalone platform, it can also be an on-site extension of an in-network Service Hosting Environment, e.g. an edge computing platform. In this case, the operator of the AS (e.g., a MEC server operator), can influence discovering/authorizing/orchestrating a residential application/service on the AS. The AS can be under the control of a 5G network operator, a customer or a third party. The service hosting environment and AS are served by the same 3GPP 5G core network (5G-CN).
+
+
+
+Diagram illustrating seamless switching from a service hosting environment to an application server via an evolved residential gateway. The diagram shows two floors (Floor 2 and Floor 1). On Floor 2, UE1 is connected to PRAS 1, which is connected to an eRG. The eRG is connected to an Access Network, which is connected to the 5G Core Network. The 5G Core Network is connected to the Service Hosting Environment. Path #1 (green line) shows the service flow from the Service Hosting Environment through the 5G Core Network, Access Network, and eRG to UE1. On Floor 1, UE1 is connected to PRAS 2, which is connected to an eRG. The eRG is connected to an Application Server. Path #2 (purple line) shows the service flow from the Application Server through the eRG to UE1. Both eRGs are connected to the same 5G Core Network via their respective Access Networks.
+
+**Figure 5.11.1-1. Seamless switching to an Application Server via an evolved residential gateway.**
+
+NOTE: The figure is not intended to capture all potential paths that might exist
+
+### 5.11.2 Pre-conditions
+
+A service hosting environment is attached to the 3GPP 5G-CN. An AS connects to the same 3GPP 5G-CN via an eRG. An indoor base station is deployed in the residential environment and is connected to the 3GPP 5G-CN via the eRG. The AS can be either in the MNO domain (i.e. a trusted application) or external to the MNO domain (i.e. an authorized third-party application).
+
+### 5.11.3 Service Flows
+
+We consider a scenario where a given UE, UE1, is receiving a service from a service hosting environment via a Premises Radio Access Station (PRAS 1) connected to the 3GPP 5G-CN. While the UE is enjoying its service, an event occurs that triggers the move of UE1 to an AS (e.g. UE1 arrives home). This AS is connected to the same 5G-CN via an eRG. As this event occurs, it is the expectation of UE1 to continue its service seamlessly with the same QoS albeit through the eRG in the AS. Below we present the service flows:
+
+1. UE consumes a low latency service (e.g. gaming) provided by a service hosting environment through the 3GPP 5G-CN (Path #1). This low latency service has a specific QoS.
+2. UE moves to an AS connected to the same 5G-CN via an eRG. The UE connects automatically to the PRAS 2 which in turn is connected to the eRG.
+
+3. The UE continues to receive its service seamlessly and with the same QoS through the eRG in the AS.
+
+### 5.11.4 Post-conditions
+
+The UE service is continued seamlessly through the eRG in the AS and with the same QoS as it was in the service hosting environment. For the purpose of demonstrating the path switch, Path #2 in Figure 5.11.1-1 is an example the 5G System can choose to ensure seamless switching.
+
+### 5.11.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] clause 6.5.2 Efficient user plane: Requirements
+
+Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path, modifying the path as needed when the UE moves or application changes location, between a UE in an active communication and:
+
+- an application in a Service Hosting Environment; or
+- an application server located outside the operator's network.
+
+The 5G network shall maintain user experience (e.g. QoS, QoE) when a UE in an active communication moves from a location served by a Service Hosting Environment to:
+
+- another location served by a different Service Hosting Environment; or
+- another location served by an application server located outside the operator's network, and vice versa.
+
+The 5G network shall maintain user experience (e.g. QoS, QoE) when an application for a UE moves as follows:
+
+- within a Service Hosting Environment; or
+- from a Service Hosting Environment to another Service Hosting Environment; or
+- from a Service Hosting Environment to an application server located place outside the operator's network, and vice versa.
+
+The 5G network shall support configurations of the Service Hosting Environment in the network (e.g. access network, core network), that provide application access close to the UE's point of attachment to the access network.
+
+The 5G system shall support mechanisms to enable a UE to access the closest Service Hosting Environment for a specific hosted application or service.
+
+The 5G network shall enable instantiation of applications for a UE in a Service Hosting Environment close to the UE's point of attachment to the access network.
+
+3GPP TS 22.261 [2] clause 6.7.2: Priority, QoS, and policy control: Requirements
+
+The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
+
+NOTE: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
+
+The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
+
+### 5.11.6 Potential New Requirements needed to support the use case
+
+[PR 5.11.6-001] The 5G system shall be able to provide support for an eRG to interconnect with an Application Server.
+
+[PR 5.11.6-002] The 5G system shall be able to maintain QoS for a UE, when it is moving between a Service Hosting Environment and an Application Server in the CPN that is connected to an eRG.
+
+## 5.12 Use case: local control of connectivity of UEs in a CPN
+
+### 5.12.1 Description
+
+In many residential scenarios, indoor coverage will require deployment of multiple PRASs or WLAN Access Points (APs). It is expected that both 3GPP RATs and non-3GPP RATs (e.g. WLAN) offer wireless connectivity allowing UEs to connect to local or external IP networks via the eRG, thus, as users move through the home, switching of connectivity between different PRASs or APs is required to maintain service quality.
+
+For certain services requiring low latency and high throughput such as playing an interactive game on a VR/AR headset UE, there is a need to connect to a dedicated device within the CPN, for example a gaming console or a set-top-box.
+
+The gaming console will provide the necessary service experience such as reactiveness when computing and rendering a new AR/VR scene displayed on the VR/AR headset (UE #1). In this use case, the gaming console can either be a 3GPP device, a non-3GPP device or support both RATs (3GPP and non-3GPP). The gaming console is part of the CPN.
+
+The VR/AR headset (UE #1) will connect to the gaming console via one of the points of access (PRAS or AP) connected to the eRG.
+
+To guarantee the required bandwidth and latency to the participants in the game, an authorized user e.g. the homeowner (Authorised Administrator) can initially, or dynamically via e.g. the gaming console or the eRG, reserve temporary access or capacity to particular UEs accessing particular PRASs and APs in the CPN during the game. Other UEs that generally are provided access to these PRASs and APs in the CPN, will during the game have a restricted or no access to certain PRASs and APs.
+
+As a player moves around in the home, there will be a need to handover the VR/AR headset (UE #1) connection from one PRAS or AP to another. Although the VR/AR headset (UE #1) can connect simultaneously to an AP and to a PRAS, the VR/AR headset (UE #1) is not able to take educated decisions on its own with regards to capabilities of alternative accesses in the home, e.g. if a candidate handover access is overloaded. However, a centralized application can distribute accesses with respect to relevant applicative parameters like VR/AR headset, the position and the direction of the UE and buffer level. Besides, the centralized application can know the building map and where (e.g. location) the different players are and where they can be expected to move as the game progress.
+
+The game application can also know the overall context for all players and can compute the best path for each UE for connecting to a particular point of access (PRAS or AP). This application can predict and adapt access to each 3GPP RAT or non-3GPP RAT for providing the best global service experience applied to each individual player at each time. The application can also learn from individual service experience resulting from past decisions applied to input parameters to improve access decisions.
+
+To optimise the gaming experience, the gaming console can control which particular VR/AR headset (UE #1 or UE #2) connects to a particular point of access (PRAS #1 or PRAS #2 or AP #1 or AP #2) to reach the application. For example, the gaming console can disable a VR/AR headset (UE #1) to connect PRAS (PRAS #2) in order to force this VR/AR headset (UE #1) to connect to PRAS (PRAS #1).
+
+
+
+Diagram illustrating the local control of PRASs for UE #1 to access CPN device. The diagram shows a house with various devices: UE #1 (VR/AR headset), UE #2 (VR/AR headset), a gaming console, Wi-Fi AP #1, Wi-Fi AP #2, PRAS #1, PRAS #2, and an eRG. A legend indicates: Existing control (dashed pink line), 5G local Control (solid pink line), and 5G Data under local Control (solid yellow line). The diagram shows UE #1 connected to PRAS #1 via a solid pink line (5G local Control) and a solid yellow line (5G Data under local Control). UE #2 is connected to Wi-Fi AP #1 via a dashed pink line (Existing control). The gaming console is connected to Wi-Fi AP #1 via a dashed pink line (Existing control). PRAS #1 and PRAS #2 are connected to the eRG via dashed pink lines (Existing control). The eRG is connected to a Fixed network via a dashed pink line (Existing control). The Fixed network is connected to a Mobile network via a dashed pink line (Existing control).
+
+**Figure 5.12.1-1. Local control of PRASs for UE #1 to access CPN device**
+
+### 5.12.2 Pre-conditions
+
+John and his game player friend Paul wear a 5G-enabled VR/AR headset (UE #1, UE #2). They love to play their favourite immersive game taking place throughout the whole house. The following pre-conditions and assumptions apply to this use case.
+
+- John, as the authorized user, has appropriately configured the devices in his house for the game.
+- Multiple PRASs (PRAS #1, PRAS #2) (3GPP RAT) are deployed in John's home, connected to the eRG. The home is equipped with several WLAN APs (AP #1, AP #2) (non-3GPP RAT), connected to the eRG.
+- Game players use VR/AR headsets (UE #1, UE #2) that require low latency and high throughput.
+- There is a gaming console in the home providing the expected gaming service experience such as reactivity when computing and rendering a new AR/VR scene to be displayed on a VR/AR headset (UE #1, UE #2).
+- Game players VR/AR headsets (UE #1, UE #2) can communicate with the gaming console over either of the 3GPP or non-3GPP RATs and the eRG.
+- The gaming console contains a map of the house.
+- The game play application knows the user locations.
+
+### 5.12.3 Service Flows
+
+The service flow for this use case is as follows:
+
+- a) John reserves temporary access or capacity for the relevant devices for the duration of the game;
+- b) John launches the multi-player augmented reality game from the residential gaming console indicating multi-RAT connectivity;
+- c) the gaming console communicates with the PRASs and APs to allow to control of the connectivity from the small base station to the gaming console;
+- d) John and Paul start playing the game from the living-room and power their VR/AR headset (UE #1 and UE #2);
+- e) each VR/AR headset (UE #1, UE #2) initially connects the gaming console from a suitable PRAS or AP;
+- f) the gaming console updates the game play each time a player moves indoor and forces the AR/VR headset (UE #1, UE #2) to connect to a particular point of access (PRAS #1 or PRAS #2 or AP #1 or AP #2); and
+
+- g) when Paul moves, the gaming console communicates with the PRASs (enable UE #1 on PRAS #1, disable UE #1 on PRAS #2) to force the VR/AR headset (UE #1) to connect to PRAS #1 to reach the gaming console.
+
+### 5.12.4 Post-conditions
+
+John and his friends can move throughout the home, from room to room on all floors, experiencing no latency when their VR/AR headset displays an augmented reality scene.
+
+### 5.12.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] clause 6.3.2.1: The 5G system shall be able to support mobility between the supported access networks (e.g. NG-RAN, WLAN, fixed broadband access network, 5G satellite access network).
+
+3GPP TS 22.261 [2] clause 6.3.2.4: The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+
+3GPP TS 22.261 [2] clause 6.7.2: A 5G system with multiple access technologies shall be able to select the combination of access technologies to serve a UE on the basis of the targeted priority, pre-emption, QoS parameters and access technology availability.
+
+3GPP TS 22.220 [3] clause 5.5.3: It shall be possible to support service continuity, including handover, between a H(e)NB cell and other cells and between H(e)NB cells. This includes H(e)NB cells in residential and enterprise environment.
+
+3GPP TS 22.220 [3] clause 5.7.2: A H(e)NB subsystem shall be able to support Local IP Access in order to provide access for IP capable UEs connected via a H(e)NB subsystem (i.e. using H(e)NB radio access) to other IP capable entities in the same residential/enterprise IP network.
+
+NOTE: 3GPP TS 22.220 [3] is referred, and it is not clear whether these requirements also apply to 5G.
+
+### 5.12.6 Potential New Requirements needed to support the use case
+
+[PR. 5.12.6-001] The 5G system shall provide means to enable/disable a UE to connect to a Customer Premises Network device via a particular Premises Radio Access Station.
+
+NOTE: Enabling/disabling a UE to a particular PRAS in the CPN does not prevent the UE to connect to other PRASs in the CPN.
+
+[PR. 5.12.6-002] The 5G system shall provide means for an authorized user to prioritize access for a certain UE in a PRAS and CPN, *within the limits given by the operator policy*.
+
+[PR. 5.12.6-003] The 5G system shall minimize service disruption when a CPN communication path changes between two PRASes.
+
+## 5.13 Use case on IP Traffic offload
+
+### 5.13.1 Description
+
+This use case assumes that one or more Premises Radio Access Stations (PRASs) were deployed in home. The IP traffic via the PRAS can be offloaded towards an external IP network at eRG directly, without going through 5GC, which is depicted in Figure 5.13.1-1. The external IP network can be enterprise private network, or internet.
+
+
+
+The diagram shows two User Equipment (UE) units, UE1 (blue) and UE2 (orange), connected to two Packet Router and Aggregator (PRAS) units, PRAS1 and PRAS2. PRAS1 and PRAS2 are connected to an edge Router/Gateway (eRG) unit. The eRG is connected to a 5G Core (5GC) unit and an External IP network unit. Red arrows indicate 'IP traffic to 5GC' from PRAS1 to 5GC. Blue arrows indicate 'IP traffic offload to External IP network' from PRAS1 and PRAS2 to the External IP network via the eRG.
+
+Diagram illustrating IP traffic offload by eRG. UE1 and UE2 are connected to PRAS1 and PRAS2 respectively. PRAS1 and PRAS2 are connected to eRG. eRG is connected to 5GC and External IP network. Arrows show IP traffic from PRAS1 to 5GC (red) and from PRAS1 and PRAS2 to External IP network (blue).
+
+Figure 5.13.1-1 IP traffic offload by eRG
+
+### 5.13.2 Pre-Conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- One or more PRAS were deployed in a residential home.
+- The PRAS provides cellular access to UEs.
+- The PRAS is connected to an eRG via wireline or wireless link.
+- The eRG can support an external IP connectivity.
+
+### 5.13.3 Service Flows
+
+Jim installed a PRAS in his house to improve the quality of experience.
+
+Some friends will come to Jim's house and play online games with extremely low latency together. Jim's game experience perhaps declined due to the excessive core network pressure.
+
+The specific IP traffic can be offloaded to the external IP network automatically at eRG when the QoS is detected not meet the requirement in PRAS or eRG.
+
+Jim can configure which types of service are prioritized to be offloaded in the systematic backstage of PRAS or eRG, and the systematic back-stage provides an approach to configure the PRAS or eRG.
+
+### 5.13.4 Post-Conditions
+
+Jim and his friend can enjoy the online game in a forever good user experience.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.101 "Service principles" [11] specifies the requirements for Selected IP Traffic Offload (SIPTO) for PS Domain only.
+
+3GPP TS 22.220 "Service requirements for Home Node B (HNB) and Home eNode B (HeNB) " [3] specifies the requirements for Selected IP Traffic Offload (SIPTO) at Local Network.
+
+3GPP TS 23.501 "System architecture for the 5G System (5GS) stage 2" [4] specifies the concept of "UL CL" (Uplink classifier) and BP (Branching Point). UL CL is a functionality supported by an UPF that aims at diverting (locally) some traffic matching traffic filters provided by the SMF, and BP provides forwarding of UL traffic towards the different PDU Session Anchors and merge of DL traffic to the UE i.e. merging the traffic from the different PDU Session Anchors on the link towards the UE.
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+[PR. 5.13.6-001] The 5G system shall be able to support IP traffic offload in CPN.
+
+NOTE: The priority of offload can be from default configuration, network or user.
+
+## 5.14 Use case on PRAS sharing
+
+### 5.14.1 Description
+
+This use case assumes that one or more Premises Radio Access Stations (PRASs) were already deployed in home. The mobile phones of family members or the visitors, which have different subscriptions to operators, need access to the 5GC via the deployed PRAS(s).
+
+
+
+```
+
+graph LR
+ PRAS[PRAS] --> UE1[UE1]
+ PRAS --> UE2[UE2]
+ PRAS --> UE3[UE3]
+ PRAS --> eRG[eRG]
+ eRG --> 5GC1[5GC1]
+ eRG --> 5GC2[5GC2]
+ eRG --> 5GC3[5GC3]
+ 5GC1 --> Server((Server))
+ 5GC2 --> Server
+ 5GC3 --> Server
+
+```
+
+Diagram illustrating PRAS sharing. A PRAS (Premises Radio Access Station) is connected to three User Equipment (UE) devices: UE1, UE2, and UE3. The PRAS is also connected to an eRG (edge Router). The eRG is connected to three 5GC (5G Core) units: 5GC1, 5GC2, and 5GC3. All three 5GC units are connected to a central Server cloud.
+
+Figure 5.14.1-1 PRAS sharing
+
+### 5.14.2 Pre-Conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- One or more PRAS were deployed in a residential home.
+- The PRAS provides cellular access to UEs.
+- The PRAS is connected to an eRG via wireline or wireless link.
+- The mobile phones of family members or the visitor have individual subscriptions to the 5G system, and these subscriptions may be different operators.
+
+Jim has a home connectivity service subscription and a 5G subscription on his mobile phone with Network Operator MNO1 and his wife, Alice, has a 5G subscription with MNO2.
+
+### 5.14.3 Service Flows
+
+Jim's smart phone is connecting to the PRAS and Jim can enjoy the internet service via MNO1's core network.
+
+Alice has no roaming subscription with MNO1, so she only accesses the internet service via MNO2's core network.
+
+Jim can enter the systematic backstage of PRAS to manage the MNOs that policy allowed access. He adds the MNO2 to the PRAS system, and the provisioning for PRAS and eRG can be completed automatically.
+
+### 5.14.4 Post-Conditions
+
+Alice could enjoy the internet service on her mobile phone via PRAS with MNO2's core network.
+
+### 5.14.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.101 "Service principles" [11] specifies the requirements for RAN sharing enhancements.
+
+### 5.14.6 Potential New Requirements needed to support the use case
+
+[PR. 5.14.6-001] The 5G system shall be able to support PRAS sharing between multiple PLMNs.
+
+## 5.15 Use case multicast service access control for legacy device(s) behind an eRG
+
+### 5.15.1 Description
+
+Multicast service access control is performed at 5GC, which is a mechanism to judge whether an UE is allowed to join a multicast group and receive the corresponding multicast service. When a UE requests to obtain multicast services, it sends an IGMP/MLD Join message to 5GC. When receiving the IGMP/MLD Join message, 5GC checks whether the UE is allowed to join the requested multicast group based on multicast service access control information. If the UE is allowed to join the requested multicast group, 5GC will transmit the corresponding multicast service to the UE. Otherwise, the UE is not allowed to receive the requested multicast service.
+
+IPTV service, a kind of multicast service, is defined as multimedia services such as television/video/audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. Set Top Box (STB) is a legacy device used to obtain IPTV service via an eRG, which is connected to 5GC as shown in Figure 5.x.1-1. Currently, the IPTV network access control granularity is RG level, which means that all STBs behind a RG will share the same access right. If network can perform a more granular multicast service access control when multiple devices connect to an eRG, users might have a better service experience.
+
+
+
+```
+graph LR; STB1[STB 1] --- RG[Residential Gateway]; STB2[STB 2] --- RG; STB3[STB 3] --- RG; RG <--> BS[Macro base station]; BS <--> 5GC((5GC));
+```
+
+Diagram showing three STBs (STB 1, STB 2, STB 3) connected to a Residential Gateway. The Residential Gateway is connected to a Macro base station, which is connected to the 5GC (5G Core Network). Arrows indicate the flow of data from the 5GC through the base station and gateway to the STBs.
+
+Figure 5.15.1-1: STB obtaining IPTV services via residential gateway
+
+### 5.15.2 Pre-conditions
+
+Mary would like to subscribe to IPTV service which is provided by IPTV network operated by IPTV operators. She needs to buy an eRG and a STB that are placed at home. The eRG is used to connect to the 5GC, while the STB is a legacy device used to obtain IPTV service via the eRG.
+
+Mary has two children, who are Jack and David. Jack is a 5-year-old boy, while David is a 14-year-old teenager. Both of them have their own bedrooms.
+
+### 5.15.3 Service Flows
+
+Mary desires to place one STB in each bedroom so that she and her sons can enjoy IPTV services in their own bedrooms simultaneously. Moreover, she hopes that the STB in each bedroom can obtain different IPTV service according to their hobbies. Therefore, she bought another two STBs which are going to be placed in her sons' bedrooms.
+
+For the STB placed in Jack's bedroom, Mary prefer to subscribe some cartoon IPTV channels because Jack loves watching cartoon. For the STB placed in David's bedroom, Mary prefer to subscribe some movie IPTV channels because David is a big fan of movie. As for Mary, she prefers to subscribe to news IPTV channels. Additionally, Mary wishes to restrict both Jack and David from watching IPTV channels with violent content.
+
+Mary requests the customised IPTV network access control for her user account to IPTV network operator.
+
+IPTV network operator updates the IPTV service access control information to 5GC according to the request from Mary so that 5GC can perform different IPTV service access control for each of the STB.
+
+### 5.15.4 Post-conditions
+
+Mary, Jack and David can enjoy their favourite IPTV channels simultaneously. Moreover, Mary does not need to worry that her sons are exposed to violent content.
+
+### 5.15.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 23.316 [7] clause 4.9.1 and clause 7.7.1 mention that:
+
+- The support of IPTV services at 5GC: "The SMF controls the support of IPTV by the UPF acting as PSA using PDR, FAR, QER, URR";
+- In the case of IPTV network access control based on the DHCP procedure, 5G-RG may be configured to retrieve via DHCP the IP address that it will use to access IPTV services.
+- When the SMF receives the Uplink DHCP message, the SMF may be configured to insert the IPTV access control information as received in subscription data from UDM to the uplink DHCP message.
+
+In Release 16 5WWC, the existing feature of multicast service access control is UE/RG level granularity. Therefore, 5GC does not support to perform different multicast service access control for legacy devices behind a RG.
+
+### 5.15.6 Potential New Requirements needed to support the use case
+
+[PR. 5.15.6-001] The 5G system shall support multicast service access control based on eRG subscription that enables eRG to forward authorized multicast services to multiple non-3GPP devices behind the eRG.
+
+NOTE: The multicast services that each of multiple non-3GPP devices is allowed to access may be different.
+
+## 5.16 Use case on the connection of 5G LAN with fixed IP VPN
+
+### 5.16.1 Description
+
+This use case intends to make use of the 5G capabilities (e.g., high performance, long-distance access, mobility and security) to build a secure connection between the 5G LAN and the fixed IP VPN. For example, when people are working from home, they probably need to access the enterprise's intranet by using the devices connecting to the home 5G LAN. The connection of 5G LAN with fixed IP VPN aims to enable the devices within the 5G LAN to access the intranet through the fixed IP VPN.
+
+
+
+The diagram shows a house containing a 'Premises Radio Access Station' (PRAS) and a '5G LAN'. The PRAS is connected to an 'eRG' (edge Router/Gateway). The 'eRG' is connected via a 'Wireline or Wireless link' to a 'Macro base station'. The 'Macro base station' is connected to the '5GC' (5G Core). The '5GC' is connected to a 'Fixed IP VPN server'. Inside the house, various devices (laptop, tablet, TV, smartphone) are connected to the '5G LAN'.
+
+Diagram illustrating the connection of a 5G LAN with a fixed IP VPN. A house contains a 'Premises Radio Access Station' connected to an 'eRG'. Inside the house is a '5G LAN' with various devices (laptop, tablet, TV, smartphone). The 'eRG' is connected via a 'Wireline or Wireless link' to a 'Macro base station', which is connected to the '5GC' (5G Core). The '5GC' is connected to a 'Fixed IP VPN server'.
+
+**Figure 5.16.1-1: connection of 5G LAN with the fixed IP VPN**
+
+### 5.16.2 Pre-conditions
+
+The following pre-conditions and assumptions apply to this use case:
+
+- There are multiple 5G UEs within a 5G LAN-VN at home.
+- There is a fixed IP VPN server deployed by the enterprise for intranet connection.
+
+### 5.16.3 Service Flows
+
+1. John works for company Tree and John is working from home.
+2. John has a subscription to the 5G LAN services. John adds all the available devices (e.g., mobile phone, laptop, tablet, printer) in his house to the 5G LAN-VN.
+3. John needs to access up-to-date data from his company's intranet and has an e-meeting with his colleagues.
+4. John uses his laptop to build a connection to Tree's intranet through the fixed IP VPN.
+5. John can access the intranet through the VPN server and he can also access the devices within the 5G LAN.
+6. John sends a request to the VPN server for authorization for his mobile phone and tablet as trusted devices for intranet access through his laptop.
+
+### 5.16.4 Post-conditions
+
+While having the e-meeting with the colleagues using his phone, John can access the up-to-date data using his mobile phone or laptop or any other authorised devices connected to the home 5G LAN. John can also exchange files or data within the home 5G LAN.
+
+### 5.16.5 Existing features partly or fully covering the use case functionality
+
+The 5G system supports the interconnection of a UE with a fixed IP VPN.
+
+3GPP TS 22.261 [2] Section 6.26.2.2 "5G LAN-virtual network (5G LAN-VN) "
+
+There are existing features that support the on-demand establishment of UE to UE, multicast, and broadcast private communication between members UEs of the same 5G LAN-VN. Multiple types of data communication shall be supported, at least IP and Ethernet.
+
+A 5G system shall support 5G LAN-VNs with member UEs numbering between a few to tens of thousands.
+
+### 5.16.6 Potential New Requirements needed to support the use case
+
+[PR. 5.16.6-001] The 5G system shall support interconnection of a 5G LAN-Virtual Network (5G LAN-VN) with a fixed IP VPN.
+
+**Editor's Note:** This requirement may need to be further studied.
+
+## 5.17 Use case on loss of connectivity between eRG or PRAS and 5GC
+
+### 5.17.1 Description
+
+When a UE under a PRAS coverage, whose communication path remains within the home, is either:
+
+- using an application server on e.g. an eRG or a compute and storage resource in the home; or
+- communicating with another UE or non-3GPP device within the home, as described in clauses 5.4 and 5.5.
+
+The use case considers what happens if the eRG or PRAS loses its connectivity with the 5GC.
+
+### 5.17.2 Pre-conditions
+
+- The user is using a client application on her UE.
+- The UE is connected via a PRAS to an application server available on the eRG.
+
+### 5.17.3 Service Flows
+
+The connectivity between the eRG and the 5GC is lost, which is detected by the eRG.
+
+
+
+Diagram illustrating the loss of connectivity between eRG and 5GC. Inside a house, multiple UEs (smartphones, tablet, 4K TV, security camera) are connected to a central 'eRG' (edge router) via 'Premises Radio Access Station' units. The eRG is connected to an external 'Macro base station' (represented by a tower icon). A red 'X' is placed over the connection line between the eRG and the Macro base station, indicating a loss of connectivity. A green arrow points from the Macro base station to a cloud labeled '5GC' (5G Core Network).
+
+**Figure 5.17.1-1: Loss of connectivity between eRG and 5GC**
+
+### 5.17.4 Post-conditions
+
+The user experiences no interruption with her application, as it is using an application server on the eRG. However, she can no longer use her UE for communications via 5GC.
+
+### 5.17.5 Existing features partly or fully covering the use case functionality
+
+There are existing features and requirements that cover a similar scenario to the case where the connectivity between eRG or PRAS and the 5GC is lost.
+
+From a Home (e)Node B perspective, a requirement in 3GPP TS 22.220 [3] clause 5.2 states:
+
+*If the connection between H(e)NB and the rest of the operator network is out of service, then it shall be possible within an operator's defined time period for the H(e)NB to deactivate the air-interface.*
+
+From an Isolated E-UTRAN operation for public safety (IOPS) perspective, 3GPP TS 22.346 [12] supports the scenario with no backhaul with a *Fully Isolated E-UTRAN operation using local routing of UE-UE data traffic*.
+
+From 3GPP TS 22.346 [12] clause 5.3.2:
+
+*An eNB supporting Isolated E-UTRAN operation shall be able to detect a loss of backhaul connection and shall be able to initiate Isolated E-UTRAN operation.*
+
+This feature is intended to be used for public safety purposes with public safety UEs.
+
+Rel-16 IAB as defined in 3GPP TS 38.331 [13] can provide coverage even if connection to parent node is lost, as there are no mechanisms to disable IAB nodes from continuing to transmit if the connection to the parent node is lost. The latest agreement from RAN2#109bis is that IAB-DU behaviour after RLF declaration is left up to implementation. IAB-DU should be able to send RLF notification when RLF recovery fails.
+
+For the detection of loss of connection between the CPN and the wider 5G network (core network), it is expected that this is based on the normal operation of the entities in the CPN that rely on co-ordination with the 5G network. Therefore, a new requirement is not needed to cover this case.
+
+For the case where eRG is routing local communications within the CPN, if the connection between the CPN and the wider 5G network (core network) is lost, this requirement is covered within BBF specifications.
+
+### 5.17.6 Potential New Requirements needed to support the use case
+
+[PR. 5.17.6-001] void
+
+[PR. 5.17.6-002] void
+
+[PR. 5.17.6-003] When the CPN has lost connectivity with the 5G network, the 5G system shall provide an operator-controlled mechanism to enable:
+
+- in the default configuration, or under certain conditions configured by the operator, the PRAS radio interface shall be deactivated; and
+- under certain other conditions configured by the operator, the CPN shall continue existing intra-CPN communication, as long as no interaction with the 5G network is needed (e.g. refreshing security keys).
+
+NOTE 1: The requirement above relates to intra-CPN operations and subject to operator policy and control, under certain situations.
+
+NOTE 2: Setting up new intra-CPN communication sessions without CPN connection to the 5G network is only possible with non-3GPP provided credentials
+
+## 5.18 Control of Customer Premises Network by Authorised Administrator
+
+### 5.18.1 Description
+
+The Customer Premises Network (CPN), including the eRG and PRAS, is at least owned, configured and managed by the customer of a public network operator. This implies that the public network operator is at least not fully in control of the configuration and management of the eRG, PRAS and CPN.
+
+Some aspects of the eRG and PRAS can be under control of the public network operator. For example if the PRAS uses licensed frequencies the radio configuration will be under control of the PLMN. Another example could be network settings in the eRG for the interface to the 5G core network.
+
+Other settings are configured / managed by the 'customer of the public network operator'. It is proposed to specify more clearly how this configuration and management by the 'customer of the public network operator' works. We are proposing to define the role of an Authorized Administrator. The Authorized Administrator may be authorized to configure / manage a specific node (e.g. a specific PRAS, eRG), or may be authorized to configure / manage a specific customer premises network (including one or more eRGs and/or PRASs).
+
+### 5.18.2 Pre-conditions
+
+None
+
+### 5.18.3 Service Flows
+
+Joe is installing a new Customer Premises Network in his home.
+
+First thing, Joe installs the eRG, in this case a wireline eRG. He has obtained the eRG from the operator and now connects it to the fixed access line.
+
+The fixed operator has arranged that various setting in the eRG are automatically configured (e.g. using TR-069 management).
+
+The eRG also enables Joe to configure a username / password combination that Joe can use for configuration / management of settings that are not under operator control from any device within the CPN. With this username / password, Joe is now Authorized Administrator for the eRG.
+
+The public network operator also provides a service where Joe as Authorized Administrator can manage his eRG via a webpage (Ut interface) provided by the operator. Great aspect of this webpage is that the operator provides help with configuration. Joe is not exactly a network expert. Additionally, Joe can also manage his PRAS via a local webpage, on which some default configuration (e.g. password for the visitor accessing network via the PRAS) can be configured.
+
+Joe now connects more devices (e.g. media server, home controller, printer, etc) to the eRG. Within the Customer Premises Network, devices can automatically discover what services other devices may provide (e.g. printer) using existing service discovery mechanisms (UPnP, zero config). Joe wants some of these services to be available also to devices that are connected to the PLMN. As Authorized Administrator of his 5GLAN service Joe can add his eRG to his 5GLAN VN group. Joe now configures which of the services from the devices on the CPN should be exposed to UEs on the PLMN. A specific service that Joe configures to be available for UEs on his 5GLAN is the configuration of his eRG.
+
+Now Joe connects a PRAS to the eRG. Joe has obtained credentials for the PRAS from the PLMN. During installation the PRAS connects to the PLMN to obtain the settings under control of the operator (e.g. radio settings).
+
+Joe can also log on to the PRAS using credentials (e.g. username / password) that were supplied with the PRAS. Using these credentials, Joe can configure settings of the PRAS via devices on the CPN. An example is that Joe can set whether visitor access network via his PRAS is allowed (allowing all or no visitors, or allowing specific visitors only). Joe can also use a webpage provided by his PLMN to configure his PRAS.
+
+### 5.18.4 Post-conditions
+
+Joe is Authorised Administrator of his Customer Premises Network, including PRAS and eRG. Joe can configure and manage the devices and services on his CPN from anywhere in the CPN and also from UEs that are connected to his 5GLAN VN Group.
+
+### 5.18.5 Existing features partly or fully covering the use case functionality
+
+Configuring nodes such as an eRG or PRAS is widely supported functionality.
+
+Service discovery within a Customer Premises Network (e.g. UPnP, zero config, or proprietary protocols) is existing functionality.
+
+Management of fixed eRG settings by an operator are specified by BBF in TR-069.
+
+### 5.18.6 Potential New Requirements needed to support the use case
+
+[PR 5.18.6-001] The 5G system shall enable configuration and management of an eRG by both the operator of the public (mobile) network the eRG is connected to and, within the boundaries defined by the operator, by an Authorised Administrator.
+
+[PR 5.18.6-002] The 5G System shall support PRAS that use licensed spectrum, use unlicensed spectrum, or can use both unlicensed and licensed spectrum.
+
+[PR 5.18.6-003] The 5G system shall enable configuration and management of a PRAS by a PLMN and, within the boundaries defined by the operator, by an Authorised Administrator. Specifically the PLMN shall be able to configure:
+
+- radio settings pertaining to licensed spectrum shall be configured by the PLMN that owns the spectrum.
+
+Specifically the Authorised Administrator shall be able to configure:
+
+- Whether visitor access network via the PRAS is allowed (allowing all or no visitors, or allowing specific visitors only)
+
+## 5.19 Use case: eRG supporting Multiple connectivity
+
+### 5.19.1 Description
+
+This use case is depicted in Figure 5.19.1-1. It shows the scenario where an eRG can support both wireline connection and 5G NR wireless connection simultaneously.
+
+
+
+Diagram illustrating the eRG supporting both wireline and 5G wireless connectivity. On the left, a box labeled 'Wireline or Wireless' contains two user equipment (UE) units, UE1 and UE2. Both UE1 and UE2 are connected to a central box labeled 'eRG'. The 'eRG' box has two outgoing connections: one is a solid line to a box labeled 'W-AGF', and the other is a dashed line with a lightning bolt symbol to a box labeled '5G-RAN'. Both the 'W-AGF' and '5G-RAN' boxes are connected to a final box on the right labeled '5G-CN'.
+
+Figure 5.19.1-1: eRG supporting both wireline connection and 5G wireless connectivity
+
+### 5.19.2 Pre-conditions
+
+Lily moved into her new home and got IPTV service combined with internet. The IPTV providers offers 2 eRG solutions, just cable or cable with wireless. Cable provides an order magnitude higher speed but Lily has heard sometimes lot of people use the internet in the evenings and it crashes so she chooses for the one with cable access and the additional wireless capability as the wireless service can both compliment the cable and either can act as a backup in case one fails. The IPTV provider also supports the download of a media server onto the eRG to enable localized access to popular contents that Lily and her family watches often but at different times. The contents have an expiration for when it will be removed from the media server, but Lisa has the option to extend the expiration. The media server also supports streaming live high definition pay-per-view events and is able to utilize both wireless and cable accesses to meet the required QoS. Lily also has a home security alarm system. She is able to configure the eRG so the security alarm system can use the cable access as the primary access and the wireless access as the backup access. In addition, she also has IoT devices such as cameras, window and door sensors, humidity and temperature sensors, etc. Some of the IoT devices do not have subscription for cellular access and the wireless operator can configure the eRG to block traffic from those devices from being routed onto the cellular access.
+
+Lily's friend Lisa owns a small business and also employs an eRG that supports both cable and wireless access connectivity. The eRG not only provides communication path redundancy for the business but also network management services for the devices behind the eRG. Lisa is able to configure the eRG so that the security system uses the cable access as the primary access and the wireless access as the backup access. In addition, Lisa has requested from the wireless operator a firewall function that runs on the eRG to provide network security for the business. Both Lisa and the wireless operator are able to configure the firewall for different aspects of the firewall operations. Lisa is able to configure firewall rules while the wireless operator is able to configure and manage the orchestration and update of the firewall software in the eRG.
+
+### 5.19.3 Service Flows
+
+Home eRG:
+
+1. Lily was watching TV at home, wherein the eRG used wireline connection for service.
+2. there was an accident in the building, the wireline was destroyed or partially destroyed. There is a lot of commotion outside with people complaining they have no service.
+3. eRG detects that the wireline was out of service or the data rate of wireline connection become very low.
+4. eRG turns on the wireless work mode and optional may provide an indication on TV screen that now cable works in multiple connection mode.
+5. The IPTV provider automatically downloads popular content Lily and her family watches to the media server when new content becomes available.
+6. Lily and her family watch the contents at different times without any service interruption.
+7. Lilly's husband and son like to watch professional wrestling and enjoy the live stream of pay-per-view events in high definition.
+
+Business eRG:
+
+1. The wireline network experiences a temporary failure where no connectivity is available for the eRG.
+2. The security system sends a normal communication to the cloud server to the eRG.
+3. The eRG detects the wireline access is not available and forwards the security system communication to the wireless access.
+4. The firewall function monitors all traffic entering the eRG through the wireless and wireline accesses.
+5. Lisa is unable to perform a download from a certain site that she knows is trustworthy and discovers the firewall function is blocking the download. Lisa configures the firewall to allow the download for this one instance only and the downloads proceeds.
+6. Meanwhile, a security patch for the firewall software is available and the wireless operator informs Lisa of its availability.
+7. Lisa schedules the update for a time when the business is close to minimize interruptions.
+
+### 5.19.4 Post-conditions
+
+Lily could continue to watch TV while the people in the same building lose IPTV service combined with internet.
+
+Lily's husband and son enjoys live stream of professional wrestling without interruption since the media server is able to use both wireless and cable accesses.
+
+The eRG is configured to not send unauthorized traffic onto the cellular access.
+
+Lisa is able to protect her business network by configuring rules for the firewall while leaving the maintenance of the firewall software to the wireless operator.
+
+### 5.19.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] clause 6.3.2.4 Fixed broadband access
+
+The 5G system shall support use of a relay UE that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+
+NOTE 1: This is for a UE that uses indirect connection to communicate with the network. It does not cover an eRG that uses direct network connections.
+
+The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+
+NOTE 2: It is unclear whether concurrent access is allowed. It is also unclear if this is applicable to an eRG.
+
+3GPP TS 23.316 [7] may include support for the hybrid access by RG.
+
+### 5.19.6 Potential New Requirements needed to support the use case
+
+[PR 5.19.6-001] The 5G system shall support use of an eRG that is connected to the 5G Core Network over 5G fixed wireless access, fixed broadband access or hybrid access.
+
+NOTE: When related to 5G-RG [PR 5.19.6-001] is fulfilled and [PR 5.19.6-002] does not apply.
+
+[PR 5.19.6-002] The 5G system shall support a mechanism for the network operator to provide policies to the eRG on which transport (e.g. wireless, cable, etc.) is best suited for different services.
+
+## 5.20 Providing 5G Multicast-Broadcast Services (5MBS) for devices through eRG.
+
+### 5.20.1 Description
+
+Broadcast/Multicast services in 5GC (5MBS) are available, potentially limited by a given service area.
+
+A user can receive such a service either outdoor or at home.
+
+The MNO wants to keep the benefits of multicast/broadcast distribution for in-home access. When at home, the user device (Smartphone, TV set, STB, PC, tablet...) can receive the service through the eRG. The device may be a 3GPP UE connected via a PRAS or the CPN access (e.g. Wi-Fi), or a non-3GPP device connected via the CPN access.
+
+### 5.20.2 Pre-conditions
+
+To enable this use case, following pre-conditions should be met:
+
+- a) The eRG is 5G multicast/broadcast capable.
+- b) The user is at home.
+- c) The user device is able to connect to the eRG.
+
+### 5.20.3 Service Flows
+
+- a) The device connects to the eRG.
+- b) The eRG discovers the available 5G multicast/broadcast services (if not yet discovered).
+- c) The user selects one of the available 5G multicast/broadcast services.
+- d) The eRG connects to the 5GC to be provisioned with the selected broadcast/multicast service.
+
+- e) The eRG serves the received broadcast/multicast content to the device through the Customer Premise Network.
+
+### 5.20.4 Post-conditions
+
+The user is able to consume the selected broadcast/multicast service at home through the connection to the eRG.
+
+### 5.20.5 Existing features partly or fully covering the use case functionality
+
+Features described in 3GPP TS 22.146 [8] are all relevant for devices behind the residential gateway. However, this specific configuration is not explicitly considered, with the exception of clause 4.2.1:
+
+- 3b) As an alternative, the Home Environment can join the user to the selected multicast group on behalf of the user, that has previously subscribed to this multicast group.
+
+Related aspects for this use case from 3GPP TS 22.261 [2]:
+
+Clause 6.3 Multiple access technologies:
+
+- For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP or non-3GPP access technology for a service,
+- Based on operator policy, the 5G system shall enable the UE to select, manage, and efficiently provision services over the 3GPP or non-3GPP access.
+- The 5G system shall be able to efficiently support connectivity using fixed broadband access.
+- The 5G system shall support use of a relay UE that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+- The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
+
+Clause 6.9 Connectivity models:
+
+- The UE (remote UE) can connect to the network directly (direct network connection), connect using another UE as a relay UE (indirect network connection), or connect using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, Public Safety and others). In these cases, the use of relays UEs can be used to improve the energy efficiency and coverage of the system.
+
+Related aspects for this use case from 3GPP TS 22.246 [9]:
+
+- The user should be able to receive MBMS user services via generic IP access systems.
+
+### 5.20.6 Potential New Requirements needed to support the use case
+
+[PR.5.20.6-001] The 5G system shall provide means to deliver 5G multicast/broadcast services to an eRG.
+
+[PR.5.20.6-002] Under operator control, an eRG shall be able to receive multicast/broadcast services from its access network.
+
+NOTE: The access network can be wireless or wireline.
+
+[PR.5.20.6-003] Under operator control, an eRG, shall be able to efficiently deliver 5G multicast/broadcast services to authorized UEs and non-3GPP devices in the CPN.
+
+## 5.21 Identification, Authentication, and Authorization for Premises Radio Access Stations
+
+### 5.21.1 Description
+
+To ensure providing the secure connectivity for UEs connected to 5G network via Premises Radio Access Stations (PRAS) behind eRG, this use case illustrates the need to have 5G system support for identification, authentication, and authorization of a PRAS which is not provided by the operators and has not previously been provided with credentials.
+
+The use case is to ensure that there is 3GPP mechanism to protect the weak-link between these (assuming untrusted) PRAS(es) not provided by the operators and the eRG.
+
+### 5.21.2 Pre-conditions
+
+Alicia purchased a promotion deal from her smartphone's operator Wallowa to upgrade her home network with a bundle package including one eRG and one PRAS-A. When receiving both devices, Alicia installed the eRG and PRAS-A in the second floor and connected both via wireline. Alicia powered on both devices. Both devices register to the 5G network and are provisioned with configuration of operation settings and authorizations from the 5G network. Both eRG and the PRAS-A are up and running well to provide 5G coverage in Alicia's home.
+
+Later, Alicia found there were still some coverage holes in the corner of the first floor so she decided to purchase one PRAS-B which is not provided by the operator and has not previously provided with credentials which thus considered as untrusted devices for the operator's network.
+
+When returning home, Alicia logs on to her account on Operator Wallowa's portal to upgrade the eRG subscription for allowing connecting this PRAS-B and then add this PRAS-B by configuring the device settings manually or via scanning QR code of the PRAS-B and associating it to the trusted 3GPP device, eRG, which it will be connected with tethering connection. Alicia may e.g. use an application on her smartphone to assist in selecting the correct eRG to connect to and/or to set up the initial connection between the PRAS and the eRG, to avoid the PRAS to connect to the neighbor's eRG and to make it easier to perform the initial setup.
+
+Alicia installed the PRAS-B in the first floor and connected the PRAS-B to 5G network via operator's eRG.
+
+### 5.21.3 Service Flows
+
+1. Alicia turns on the PRAS-B and connects the PRAS-B to the eRG. The PRAS-B connects to 5G network via the eRG. The 5G system detects that PRAS-B has not previously been provided with credentials and then provision a credential to the PRAS-B which may be based on eRG subscription or PRAS subscription if available. Operator Wallowa's 5G network identifies, authenticates, and authorizes the PRAS-B based on the credentials provided to the PRAS.
+2. The 5G network provisions configurations, e.g. PRAS operation authorization, operator's settings, etc., to the PRAS via eRG.
+3. When the PRAS-B completes installation, it reconnects to Operator Wallowa's 5G network via eRG based on provisioned PRAS-B configuration.
+4. The Operator Wallowa's 5G network can identify PRAS-B, authenticate its identity, and authorize the PRAS-B operation based on the provisioned credentials and configuration of the PRAS-B.
+5. Once this process is complete, the PRAS-B is successfully authenticated, authorized, configured, and connected to Operator Wallowa's network via eRG and are now fully operational.
+
+### 5.21.4 Post-conditions
+
+The 5G network ensures that the E2E connection from the 5G core network to the UE connected to the operator's PRAS-A and the PRAS-B behind eRG are secure because both PRAS(es) connected via operator's eRG are authenticated, authorized, and managed by the operator.
+
+Alicia can now connect her UEs to both PRAS(es). She is happy that she can speak to the phone when walking around the house with good 5G service coverage.
+
+### 5.21.5 Existing features partly or fully covering the use case functionality
+
+The following service requirement in 3GPP TS 22.101 [11] clause 26a provide the principle for user centric identifiers and authentication and authorization by the 3GPP system:
+
+*The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services.*
+
+In the 3GPP TS 22.101 [11] clause 26a, the 5G network operator can act as an identity provider for Users, e.g. an individual human user, using a UE with a certain subscription, or an application running on or connecting to a UE, or a device ("thing") behind a gateway UE. These Users are associated to the 3GPP devices (UE or gateway UE) which are 5G subscribers of the operator's network. The 5G network can identify and authenticate a User Identity based on the authenticated 3GPP device that is associated to the user. In the context of CPN, the 5G network can also enable support for identifying and authenticating a PRAS which is not provided by the operator and does not have 3GPP credentials based on the authenticated 3GPP device (eRG) that provides tethering connection.
+
+### 5.21.6 Potential New Requirements needed to support the use case
+
+[PR 5.21.6-001] The 5G system shall provide support for a network operator to authenticate a PRAS.
+
+[PR 5.21.6-002] The 5G system shall provide support for a network operator to authorize a PRAS for its use in a CPN.
+
+[PR 5.21.6-003] The 5G system shall support a secure mechanism for a network operator to provision a PRAS with an associated subscription and authentication credentials, and to identify a PRAS (e.g. for management purposes or to provide backhaul connectivity to the PRAS).
+
+**Editor's Note: This requirement is FFS.**
+
+[PR 5.21.6-004] The 5G system shall provide mechanisms for the network operator to provision an authenticated PRAS with operation settings, e.g. carrier frequencies.
+
+## 5.22 Use Case for supporting external services behind eRG in CPN
+
+### 5.22.1 Description
+
+According to 3GPP TS 22.101 [11] clause 26a, the 3GPP system can support an operator to act as identity provider and enable auto-log-in and single-sign-on to operator and non-operator services. This use case is extended from the use case 5.2, Identity provisioning to external services, in 3GPP TR 22.904 [10] which considers the applications are hosted in the cloud.
+
+In support of external services provided behind an eRG in CPN, this use case describes the enhancement of functionalities and provides the potential service requirements in addition to those described in [11].
+
+### 5.22.2 Pre-conditions
+
+Dora is a subscriber of network operator Cannon-Beach where she has a user account and subscriptions for her UE and the eRG in the CPN. Based on the subscriptions for the eRG, operator Cannon-Beach enables a strong user authentication mechanism at the 5G system to ensure that the users accessing to the eRG in the CPN are authenticated and authorized.
+
+Dora installs a local cloud with the application platform on a device connected to the eRG in the CPN in her home. The local cloud provides storage services for files, video, and photo album, etc. Dora configures applications/services information and registers to these applications with her user account of the network operator Cannon-Beach for the local cloud storage services hosted on the device behind the eRG in the CPN, by which each application/service is associated to a User Identity and corresponding User Profiles.
+
+When enabling these applications/services in her user account, these services/applications can use strong user authentication from the 5G system to the applications running on the device behind the eRG in the CPN. As such, auto-log-in and single-sign-on is enabled for the applications.
+
+### 5.22.3 Service Flows
+
+Step1: Dora logged in her user account using her UE and her User Identity has been authenticated over the 5G system using a strong authentication mechanism for the connection to the eRG.
+
+Step2: Dora opens a book on the bookshelf application hosted by the local cloud on the device behind the eRG for which the bookshelf application has been configured to require strong user authentication by the 5G system.
+
+Step3: The bookshelf application accepts her request to access without further needs for Dora to provide additional credentials for the application. Since her UE has been authenticated by the 5G system and she has already been authenticated for the connection to the eRG, there is a high level of confidence regarding her identity. This level of confidence is increased based on Dora's location and the elapse time from the last authentication of her identity.
+
+Step4: In the meantime, the application client of photo album on her UE automatically synchronize her photos to the photo album application on the local cloud in the CPN. Since Dora also enabled the strong user authentication by the 5G system for this photo album application, her UE can automatically sign in and upload the photos to the photo album application on the local cloud.
+
+Step5: The 5G system may request her strong re-authentication so as to ensure that she is still the actual authorized user behind the UE, which is achieved by having Dora re-authenticated by operator Cannon-Beach, e.g. over the biotech sensors (e.g. for face, fingerprint, voice) of the UE.
+
+### 5.22.4 Post-conditions
+
+Because of operator's supports for non-operator services on the local cloud in the CPN and the support of strong user authentication by the 5G system, Dora is worries free to install more applications hosted by the local cloud on the devices connected to the eRG in the CPN in her home.
+
+### 5.22.5 Existing features partly or fully covering the use case functionality
+
+The following service requirement in 3GPP TS 22.101 [11] clause 26a provide the principle for user centric identifiers and authentication and authorization by the 3GPP system:
+
+*The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services.*
+
+#### 26a.2.1 User Identifiers and user authentication
+
+*The 3GPP system shall be able to assess the level of confidence in the User Identity by taking into account information regarding the used mechanism for obtaining that User Identity (e.g. algorithms, key-length, time since last authentication), information from the network (e.g. UE or device in use, access technology, location).*
+
+#### 26a.2.5 Privacy requirements
+
+*The 3GPP system shall protect the privacy of the user by transferring to a service only User Identity information that is necessary to provide the service and for which the user has consented to when registering for the service.*
+
+The use case considers that the external services are provided as a local cloud application platform behind an eRG in CPN and proposes to enable 5G system support for identity provisioning to external services behind eRG in CPN.
+
+### 5.22.6 Potential Requirements
+
+[PR 5.22.6-001] The 5G system should support "User Identity" requirements (as defined in 3GPP TS 22.101 [11] clause 26.a) for a user (human) using a CPN authorized UE to access external non-3GPP applications/services hosted in a CPN (behind a eRG).
+
+[PR 5.22.6-002] The 5G system shall support to allow a CPN authorized UE or non-3GPP device accessing to a CPN based on successful User Identity authentication.
+
+# 6 Traffic Scenarios
+
+## 6.1 Traffic Scenario: inHome
+
+### 6.1.1 Description
+
+Many houses suffer from problems of coverage due to the number of floors and other obstacles (i.e. walls, doors, columns, furniture). Outdoor-to-indoor coverage may be an issue at 3.5 GHz and will certainly be difficult at mmwave frequencies. Providing coverage with indoor solutions may be the answer; Premises Radio Access Stations (PRASs) can be connected via fixed access. 3GPP together with BBF has provided Wireline Wireless Convergence architecture solutions where fixed access is considered part of the 5G System.
+
+Most houses have only one entry network point where the evolved Residential Gateway (eRG) will be installed. Connectivity to the eRG may be fixed access, 5G Fixed Wireless Access, or a hybrid of both.
+
+
+
+The diagram illustrates an 'InHome Scenario' within a house. The house is divided into several rooms. In the top left room, there is a UHD TV displaying a bird. In the top right room, there is a VR headset and a gaming console. In the bottom left room, a person is working at a desk with a computer. In the bottom right room, another person is using a VR headset. Each room contains a small icon labeled '5G', representing a Premises Radio Access Station (PRAS). All four PRAS units are connected by lines to a central green box labeled 'eRG' (evolved Residential Gateway) located in the bottom right. The eRG is then connected by a line to a cloud icon on the right, which is also labeled '5G', representing the external 5G network.
+
+Diagram of the InHome Scenario showing a house with multiple 5G PRAS units and an eRG connected to a 5G cloud.
+
+Figure 6.1.1-1 – InHome Scenario
+
+Providing connectivity throughout the house from a single PRAS will not be feasible. Concrete floors and walls, will require multiple PRASs to be deployed in the house. That way it can be guaranteed that even in the attic, cellar and garage, there is sufficient coverage. At mmwave frequencies, even a PRAS per room (living room, kitchen, bed rooms, attic) may be required as higher frequencies will be blocked significantly by walls, et cetera.
+
+### 6.1.2 Assumptions
+
+Let's consider a fairly large house with dimensions 10m x 10m and 3 floors. The owners of the house are a family of four; mother, father and two teen age children.
+
+The traffic scenario for in the house is mainly determined by multimedia application usages. Most other services (e.g. mobile telephony) will not significantly contribute to the traffic load.
+
+We assume the house has two UHD TVs, two VR headsets for gaming, and two office settings for working from home (for e.g. multimedia conferencing). Not all devices will be used at the same time. On the other hand, visitors may also bring/use devices. Assumption is that one UHD TV, two VR headsets for gaming and two office settings are used simultaneously, each at the maximum user experienced data rates of 1 Gbit/s DL and 500 Mbit/s UL. This results in an overall capacity for the house of 5 Gbit/s DL (UHD TV is DL only) and 2 Gbits/s UL.
+
+The assumption is that different Premises Radio Access Stations (PRASs) are deployed around the house. Not all devices will use the same PRAS. Maximum per PRAS data rates are assumed to be half of that per house.
+
+### 6.1.3 Potential Functional Requirements
+
+None
+
+### 6.1.4 Potential Key Performance Requirements
+
+Values for max data rate and area capacity per home are based on values in 3GPP TS 22.261 [2] for InHome scenario and indoor hotspot. The area capacity per base station is calculated based on two base stations per home (10m x 10m with 3 floors).
+
+**Table 6.1.4-1 – Potential key performance requirements for InHome scenario**
+
+| Scenario | Max. data rate (DL) | Max. data rate (UL) | End-to-end latency | Area traffic capacity (DL) (note 1) | Area traffic capacity (UL) (note 1) | Area traffic capacity (DL) (note 2) | Area traffic capacity (UL) (note 2) | Area |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------------------|--------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|----------------------|
+| InHome Scenario | 1 Gbit/s | 500 Mbit/s | 10 ms | 5 Gbit/s/home | 2 Gbit/s/home | 2.5 Gbit/s/PRAS | 1 Gbit/s/PRAS | 10m x 10m – 3 floors |
+| NOTE 1: Area traffic capacity is determined by high bandwidth consuming devices (e.g. ultra HD TVs, VR headsets, ...) assuming a family of 4 members (one UHD TV with DL only and 4 high bandwidth consuming devices with UL and DL used simultaneously). | | | | | | | | |
+| NOTE 2: Multiple Premises Radio Access Stations (PRASs) are assumed (e.g. one per room), maximum traffic per PRAS assumed to be half of the overall traffic per house. | | | | | | | | |
+
+# --- 7 Consolidated requirements
+
+## 7.1 Introduction
+
+This section provides Consolidated Potential Requirements for consideration to include in the normative specifications. The CPRs have been grouped into different functional categories, each category contains a table that lists the original PR.
+
+## 7.2 General
+
+**Table 7.2-1 – RESIDENT General Consolidated Requirements**
+
+| CPR ## | Original Potential Requirement No. | Consolidated Consolidated Potential Requirement | | C |
+|-----------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|--|---|
+| CPR 7.2-1 | | Subject to local regulations, the 5G system shall support regulatory requirements for emergency calls, PWS and eCall for UEs connected to a CPN. | | |
+
+## 7.3 Gateway
+
+**Table 7.3-1 – RESIDENT Gateway Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | C |
+|-----------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------------------|
+| | | | | D
th
fro |
+| CPR 7.3-1 | PR 5.13.6-001 | The 5G system shall be able to support IP traffic offload within the CPN.
NOTE: The priority of offload can be from default configuration, network or user. | PR 5.13.6-001 | |
+| | PR 5.19.6-001 | | PR 5.19.6-001 | D
th
co
N
ac
ac |
+| CPR 7.3-2 | PR. 5.17.6-003 | When the CPN has lost connectivity with the 5G network, the 5G system shall provide an operator-controlled mechanism to enable:
- in the default configuration, or under certain conditions configured by the operator, the PRAS radio interface shall be deactivated; and
- under certain other conditions configured by the operator, the CPN shall continue existing intra-CPN communication, as long as no interaction with the 5G network is needed (e.g. refreshing security keys).
NOTE 1: The requirement above relates to intra-CPN operations and subject to operator policy and control, under certain situations.
NOTE 2: Setting up new intra-CPN communication sessions without CPN connection to the 5G network is only possible with non-3GPP provided credentials | PR. 5.17.6-003 | |
+
+## 7.4 Service Discovery
+
+**Table 7.4-1– RESIDENT Service Discovery Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | C |
+|-----------|------------------------------------|--------------------------------------------------------------------------------------------------------|---------------|---|
+| CPR 7.4-1 | PR 5.2.6-008 | The 5G system shall enable a UE in a CPN to discover other UEs or non-3GPP devices within the same CPN | PR 5.2.6-008 | |
+
+| | | | | |
+|-----------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|
+| CPR 7.4-2 | PR 5.2.6-008 | The 5G system shall efficiently support service discovery mechanisms where UEs in a CPN can discover, subject to access rights:
- availability and reachability of other entities (e.g. other UEs or non-3GPP devices) on the CPN
- capabilities of other entities on the CPN (e.g. eRG, relay UE) and/or;
- services provided by other entities on the CPN (e.g. the entity is a printer). | PR 5.2.6-008 | C
R
T |
+|-----------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|
+
+## 7.5 Application Servers
+
+**Table 7.5-1 – RESIDENT Application Servers Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | C |
+|-----------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|----------------------------|
+| CPR 7.5-1 | PR 5.11.6-001 | The 5G system shall support applications on an Application Server connected to the Customer Premises Network. | PR 5.11.6-001 | |
+| CPR 7.5-2 | PR 5.11.6-002 | Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path, modifying the path as needed when the UE moves or application changes location, between a UE in an active communication and:
- an application in a Service Hosting Environment; or
- an application server located outside the operator's network; or
- an application server located in a customer premises network. | PR 5.11.6-002 | Th
of
re
th
to |
+| CPR 7.5-3 | PR 5.11.6-002 | The 5G network shall maintain user experience (e.g. QoS, QoE) when a UE in an active communication moves from a location served by a Service Hosting Environment to:
- another location served by a different Service Hosting Environment; or
- another location served by an application server located in a customer premises network, and vice versa. | PR 5.11.6-002 | Th
of
re
th
to |
+| CPR 7.5-4 | PR 5.11.6-002 | The 5G network shall maintain user experience (e.g. QoS, QoE) when an application for a UE moves as follows:
- within a Service Hosting Environment; or
- from a Service Hosting Environment to another Service Hosting Environment; or
- from a Service Hosting Environment to an application server located place outside the operator's network; or
- from a Service Hosting Environment to an application server located in a customer premises network, and vice versa | PR 5.11.6-002 | Th
of
re
th
to |
+
+## 7.6 Identification, Privacy, and security
+
+**Table 7.6-1 – RESIDENT Identification, Privacy, and security Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | C |
+|------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------------------|
+| | PR 5.22.6-001
PR 5.22.6-002 | | PR 5.22.6-001
PR 5.22.6-002 | S
de
20
de |
+| CPR 7.6-1 | PR 5.5.6-006 | The 5G system shall provide user privacy protection for UEs that are using the Evolved Residential Gateway, including communication confidentiality, location privacy and identity protection.
NOTE: Privacy protection should not block differentiated routing and QoS at the eRG for different destinations and services for the UE(s). | PR 5.5.6-006 | |
+| CPR 7.6-2 | PR 5.2.6-006 | The 5G system shall provide user privacy for UEs that are using the PRAS, including communication confidentiality, location privacy and identity protection.
NOTE: Privacy protection should not block differentiated routing, QoS, and services for the UE(s). | PR 5.2.6-006 | |
+| CPR 7.6-3 | PR 5.5.6-003
PR 5.5.6-004 | The 5G system shall support a mechanism to minimize the security risk of communications using an eRG. | PR 5.5.6-003
PR 5.5.6-004 | |
+| CPR 7.6-4 | PR 5.5.6-005 | The 5G system shall enable the network operator associated with an Evolved Residential Gateway to control the security policy of an Evolved Residential Gateway. | PR 5.5.6-005 | |
+| CPR 7.6-5 | PR 5.2.6-003
PR 5.2.6-004 | The 5G system shall support a mechanism to minimize the security risk of communications via a PRAS. | PR 5.2.6-003
PR 5.2.6-004 | |
+| CPR 7.6-6 | PR 5.2.6-004 | The PRAS (and its associated backhaul connectivity) shall provide a level of security equivalent to regular 5G base stations. | PR 5.2.6-004 | |
+| CPR 7.6-7 | PR 5.2.6-005 | The 5G system shall enable the network operator associated with the Premises Radio Access Station (PRAS) to control the security policy of the PRAS. | PR 5.2.6-005 | |
+| CPR 7.6-8 | PR 5.2.6-009a | The 5G system shall support authentication of a UE with 3GPP credentials for communication with entities (UEs, devices) in a CPN.
NOTE: To support this functionality the CPN needs to be connected with the 5G core network. | PR 5.2.6-009a | |
+| CPR 7.6-9 | PR 5.21.6-001 | The 5G system shall provide support for a network operator to authenticate a PRAS. | PR 5.21.6-001 | |
+| CPR 7.6-10 | PR 5.21.6-002 | The 5G system shall provide support for a network operator to authorize a PRAS for its use in a CPN. | PR 5.21.6-002 | |
+
+## 7.7 Direct Communications
+
+Table 7.7-1 – RESIDENT Direct Communications Consolidated Requirements
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | Comment |
+|-------|------------------------------------|------------------------------------|---------------|---------------------|
+| | PR 5.10.6-001 | | PR 5.10.6-001 | S
co
sv
de |
+
+## 7.8 Connectivity - QoS - charging
+
+Table 7.8-1 – RESIDENT Connectivity, QoS and Charging Consolidated Requirements
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------|
+| CPR 7.8-1 | PR 5.5.6-002
PR 5.4.6-001 | Subject to regulatory requirements and operator policy, the 5G system shall support an efficient data path through an Evolved Residential Gateway for intra-CPN data traffic to or from a UE.
NOTE: For services an operator deploys in the 5G network (i.e. not in the CPN), local data routed via eRG does not apply. | PR 5.5.6-002
PR 5.4.6-001 | |
+| CPR 7.8-2 | PR 5.6.6-001
PR 5.1.6-002
PR 5.5.6-001
PR 5.3.6-002
PR 5.10.6-002
PR 5.5.6-007 | The 5G system shall support real time E2E QoS monitoring and control for any intra-CPN data traffic to or from a UE (i.e. via eRG or via PRAS and eRG) | PR 5.6.6-001
PR 5.1.6-002
PR 5.5.6-001
PR 5.3.6-002
PR 5.10.6-002
PR 5.5.6-007 | |
+| CPR 7.8-3 | PR 5.6.6-001
PR 5.1.6-002
PR 5.5.6-001
PR 5.3.6-002
PR 5.10.6-002 | The 5G system shall support real time E2E QoS monitoring and control for any data traffic between a UE within a CPN and the 5G network (i.e. via eRG or via PRAS and eRG) | PR 5.6.6-001
PR 5.1.6-002
PR 5.5.6-001
PR 5.3.6-002
PR 5.10.6-002 | |
+| CPR 7.8-5 | PR 5.2.6-007
PR 5.2.6-009 | The 5G system shall support charging data collection and LI for data traffic to/from individual UEs in a CPN (i.e. UEs behind the eRG and/or PRAS). | PR 5.2.6-007
PR 5.2.6-009 | |
+| CPR 7.8-6 | PR 5.2.6-007 | The 5G system shall be able to generate charging data that can differentiate between backhaul for the PRAS and other data traffic over the same access. | PR 5.2.6-007 | |
+| CPR 7.8-7 | PR 5.3.6-003 | The 5G system shall minimize service disruption for a UE that is moving between CPN access and operator provided mobile access.
NOTE: CPN access can imply access via a PRAS or can imply access directly via an eRG. Operator provided mobile access implies access via an operator owned base station. | PR 5.3.6-003 | |
+
+## 7.9 Provisioning
+
+**Table 7.9-1 – RESIDENT Provisioning Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------|
+| CPR 7.9-1 | PR 5.18.6-001
PR 5.19.6-002
PR 5.7.6-001 | The 5G system shall support a mechanism for the network operator to provision an eRG with:
- policies on which transport (e.g. wireless, cable, etc.) is best suited for different negotiated QoS levels.
- authentication credentials
- identification,
- initial OA&M information, and
- associated subscription | PR 5.18.6-001
PR 5.19.6-002
PR 5.7.6-001 | |
+| CPR 7.9-2 | PR 5.18.6-003
PR 5.12.6-002
PR 5.21.6-004
PR 5.7.6-001
PR 5.21.6-003 | The 5G system shall enable the network operator to configure a PRAS with:
- radio settings pertaining to licensed spectrum,
- authentication credentials,
- identification,
- initial OA&M information, and
- associated subscription. | PR 5.18.6-003
PR 5.12.6-002
PR 5.21.6-004
PR 5.7.6-001
PR 5.21.6-003 | |
+| CPR 7.9-3 | PR 5.18.6-003 | Subject to operator policy, the 5G system shall enable the Authorised Administrator to provision a PRAS with UE access considerations (allowing all UEs, or allowing specific UEs only) | PR 5.18.6-003 | |
+| CPR 7.9-4 | PR 5.7.6-001 | The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of an eRG. | PR 5.7.6-001 | |
+| CPR 7.9-5 | PR 5.7.6-002 | The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of a PRAS. | PR 5.7.6-002 | |
+
+## 7.10 Premises Radio Access Station
+
+**Table 7.10-1 – RESIDENT Premises Radio Access Station Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | Comment |
+|------------|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|----------------------------------------------------------------------|
+| CPR 7.10-1 | PR 5.1.6-001
PR 5.2.6-001
PR 5.2.6-001
PR 5.2.6-002 | The 5G system shall enable the network operator to provide any 5G services to any UE via a Premises Radio Access Station (PRAS) connected via an evolved Residential Gateway (eRG).
NOTE1: Whether the PRAS can be used by UEs from other PLMNs in the same country as the PLMN associated with the PRAS is subject to regulatory policy on national roaming. | PR 5.1.6-001
PR 5.2.6-001
PR 5.2.6-001
PR 5.2.6-002 | |
+| CPR 7.10-2 | PR 5.12.6-001 | The 5G system shall provide means to control which UEs can connect to a PRAS. | PR 5.12.6-001 | |
+| CPR 7.10-3 | PR 5.12.6-003 | The 5G system shall minimize service disruption when a CPN communication path changes between two PRASEs. | PR 5.12.6-003 | |
+| CPR 7.10-4 | PR 5.14.6-001 | The 5G system shall be able to support PRAS sharing between multiple PLMNs. | PR 5.14.6-001 | |
+| | PR 5.18.6-002 | | PR 5.18.6-002 | Operation in Lic and Unlicensed will be treated in descriptive text. |
+
+## 7.11 5G-LAN
+
+**Table 7.11-1 – RESIDENT 5G-LAN Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | C |
+|------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|
+| CPR 7.11-1 | PR 5.8.6-001 | The 5G system shall be able to support large numbers of small 5G LAN-VNs.
NOTE: Targeting residential deployments translate into millions of 5GLAN-VN per operator per country. These 5G LAN-VNs may contain between 10-50 devices per LAN | PR 5.8.6-001 | |
+| CPR 7.11-2 | PR 5.8.6-002 | The 5G system shall support a mechanism to enable authorized 3rd parties to authorize/deauthorize UEs to access a 5G LAN-VN. | PR 5.8.6-002 | |
+| CPR 7.11-3 | PR 5.9.6-001 | The 5G system shall support the use of an evolved Residential Gateway to connect 5G devices from the 5G LAN VN it belongs to with non-3GPP devices on an in-home LAN. | PR 5.9.6-001 | |
+| | PR 5.16.6-001 | | PR 5.16.6-001 | t
c
r |
+
+## 7.12 Broadcast Multicast
+
+**Table 7.12-1 – RESIDENT Broadcast Multicast Consolidated Requirements**
+
+| CPR # | Original Potential Requirement No. | Consolidated Potential Requirement | Original PR # | C |
+|------------|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|---|
+| CPR 7.12-1 | PR.5.20.6-001
PR.5.20.6-002
PR.5.20.6-003
PR. 5.15.6-001 | Under operator control, an eRG, shall be able to efficiently deliver 5G multicast/broadcast services to authorized UEs and non-3GPP devices in the CPN.
NOTE: The multicast service(s) that each of the authorized UEs and/or non-3GPP devices is allowed to receive may be different. | PR.5.20.6-001
PR.5.20.6-002
PR.5.20.6-003
PR. 5.15.6-001 | |
+
+# 8 Conclusions and recommendations
+
+This Technical Report analyses a number of use cases related to the use of 5G in a residential setting. It is argued that providing an excellent 5G experience in an in-home setting is very important as in-home is where many 5G users will spend a large amount of time, especially when using highly demanding services such as UHD-TV, AR/VR or mobile gaming. Based on the different use cases, requirements have been generated on topics such as Premises Radio Access System, evolved Residential Gateway, service discovery, provisioning, et cetera.
+
+There are also some requirements related to 5G-LAN, where the existing 5G-LAN requirements already in [2] are being expanded.
+
+The resulting potential requirements have been consolidated in clause 7 of the TR. The content of clause 7 should be considered as the basis of normative Release 18 requirements to support 5G for residential use cases.
+
+# Annex A: Resident networks overview
+
+## A.1 Introduction
+
+The following provides an overview of the entities defined in this Technical Report and their relations.
+
+## A.2 Customer Premises Network overview
+
+
+
+```
+
+graph LR
+ subgraph CPN
+ UE1[UE] --- PRAS[PRAS]
+ PRAS --- eRG[eRG]
+ UE2[UE] --- eRG
+ Non3GPP[Non-3GPP device] --- eRG
+ end
+ eRG --- FixedAccess(Fixed Access)
+ eRG --- MobileAccess(Mobile Access)
+ eRG --- OtherAccess(Other Access)
+ FixedAccess --- 5GC((5GC))
+ MobileAccess --- 5GC
+ OtherAccess --- 5GC
+
+```
+
+Diagram of Customer Premises Network (CPN) connected to 5GC. The CPN is an oval containing a UE, PRAS, another UE, a Non-3GPP device, and an eRG. The first UE is connected to the PRAS. The PRAS is connected to the eRG. The second UE and the Non-3GPP device are also connected to the eRG. The eRG is connected to three access types: Fixed Access, Mobile Access, and Other Access, which are all connected to the 5GC.
+
+**Figure A.2-1: Customer Premises Network connected to 5GC**
+
+The Resident networks overview contains the following entities.
+
+- evolved Residential Gateway (eRG).
+- Premises Radio Access System (PRAS).
+- Customer Premises Network (CPN)
+- User Equipment (UE).
+- Non-3GPP Device.
+
+## A.3 Customer Premises Network entities
+
+### A.3.1 evolved Residential Gateway (eRG)
+
+The evolved Residential Gateway is defined in clause 3.1.
+
+The eRG is connected to the 5GC via e.g. fixed, mobile, or hybrid access following specifications for Wireline-Wireless Convergence [7]
+
+Connectivity between the eRG and the UE, non-3GPP Device, or PRAS can use any suitable non-3GPP technology (e.g. Ethernet, optical, WiFi).
+
+NOTE: the eRG does not provide PRAS functionality (i.e. there is no NR Uu access between the eRG and a UE). Ofcourse it is possible to implement an eRG and PRAS in a single box.
+
+### A.3.2 Premises Radio Access System (PRAS)
+
+The Premises Radio Access System is defined in clause 3.1.
+
+A PRAS can use licensed spectrum, but also can use unlicensed spectrum.
+
+Connectivity between the PRAS and the UE can use NR radio access (Uu) or non-3GPP radio access.
+
+The PRAS only provides non-3GPP radio access to UEs with 3GPP credentials that are checked by the 5GC (similar to other non-3GPP access to the 5GC). The PRAS is not e.g. a WiFi AP that provides non-3GPP access to devices with non-3GPP credentials that are checked by the WiFi AP itself.
+
+The PRAS is part of the Customer Premises Network and therefore connected to the eRG.
+
+The PRAS may also provide E-UTRA radio access.
+
+### A.3.3 Customer Premises Network (CPN)
+
+The Customer Premises Network is defined in clause 3.1.
+
+### A.3.4 User Equipment (UE)
+
+The User Equipment is defined in [1].
+
+### A.3.3 Non-3GPP device
+
+The Non-3GPP device is defined in clause 3.1.
+
+# Annex B: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|------|-----|-----------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New version |
+| 2021-03 | SA#91e | SP-210209 | | | | Presentation to SA for information
MCC Clean-up | 1.0.0 |
+| 2021-05 | SA1#94e | S1-211307 | | | | Output version of SA1#94e | 1.1.0 |
+| 2021-06 | SA#92e | SP-210512 | | | | Raised to v.2.0.0 by MCC for approval | 2.0.0 |
+| 2021-06 | SA#92e | SP-210512 | | | | Raised to v.18.0.0 by MCC following approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210512 | | | | Corrected logo (5G->5GA) | 18.0.1 |
+| 2021-09 | SA#93e | SP-211099 | 0001 | 1 | C | FS_ Resident: Clarification of Loss of 5GC connectivity requirements | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0002 | 1 | B | Update Use Case 5.21 for PRAS | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0003 | 1 | C | Clause5.5 routing via residential IP network | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0005 | 1 | C | Alignment and clarification of PR5.4.6-001 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0006 | 1 | C | Consolidation of Resident requirements | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0007 | 1 | C | Hybrid access in definitions | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0008 | 1 | D | Consistent usage of definition Authorised Administrator | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0009 | | C | Change residential network to CPN | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0010 | | D | Editorial changes to TR | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0011 | 1 | D | Remove Editor's Note on requirements E2E QoS Monitoring. | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0012 | | D | Remove Editor's Notes on requirements consolidation | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0013 | | D | Removing editor's note on rephrasing requirements | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0014 | 1 | D | Remove Editor's Notes on requirement 5G LAN with fixed IP VPN | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0015 | | C | Remove Editor's Notes in 5.18 on requirements Control by Authorised Administrator | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0016 | | D | Remove Editor's Note in 5.22 on requirements external services behind eRG in CPN | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0017 | 1 | B | Update of use case 5.2 use of 3GPP credentials | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0018 | 1 | B | Update use case 5.3 on service continuity between CPN and public network | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0020 | 1 | F | FS_ Resident Correction of clause 5.10 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0021 | 1 | F | FS_ Resident Correction of clause 5.11.1 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0024 | 1 | B | Clarification of PRAS configuration | 18.1.0 |
+| 2021-09 | SA#93e | SP-211099 | 0025 | 1 | B | Clarification of QoS between two UEs | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0027 | | D | Resident consolidated requirements table update | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22859/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-18/22_series/22859/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f63b489d989d809223310d7368fff57b64028c8
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0968d0911083826578f3216479a14cec418636c8257665ef14d23f91b9ad084b
+size 39928
diff --git a/marked/Rel-18/22_series/22859/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-18/22_series/22859/51db757d054ce1ce83c436a3578b56ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b3bb0fd38b29994abb8f2a3560763fa99b7e8d7
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/51db757d054ce1ce83c436a3578b56ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0a1c8c6ff7c7c6e4af3abde06b4b32db61c463200a51c58a14ab4cc6958456e
+size 36045
diff --git a/marked/Rel-18/22_series/22859/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-18/22_series/22859/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f41a6d036afc43fe3059146c1fe476c3caec0719
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50b5a5cf1a28a41ea0fbcfa65505babd13a620f062fb35b64f735cc95ebf3571
+size 47095
diff --git a/marked/Rel-18/22_series/22859/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22859/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cee5523dba025183f573ff3f6421b8fc032e7e0c
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7197c5703f0cd7cc972540a7038dcfe842c291e14ebbbab38b93072e33ce5785
+size 9595
diff --git a/marked/Rel-18/22_series/22859/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22859/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c57c2e12dd7854c954c55b4df273aedc1e61d771
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:167777b3e33a7ca68d1a3f0672ab03f0fe91751e38e47cc7ff7df223d13556e0
+size 5701
diff --git a/marked/Rel-18/22_series/22859/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-18/22_series/22859/6470d350326789d5306eabcb76533951_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bb21130650a0d9e77380f59d2137379f480b1e55
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/6470d350326789d5306eabcb76533951_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa3c901d67a300ec45e9ea89629fc11ca0bf19742f8aaa8260fa014203ca413e
+size 37322
diff --git a/marked/Rel-18/22_series/22859/772cc583a60eeb058cc19de48269ad22_img.jpg b/marked/Rel-18/22_series/22859/772cc583a60eeb058cc19de48269ad22_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..55fd2ce6511f8d92eb69373bd7a88559c0cb3f52
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/772cc583a60eeb058cc19de48269ad22_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e8c59f4cd158d4b7c7f830dd58d545df17ca8a58cb2dbb59eacd07e54361a30
+size 79305
diff --git a/marked/Rel-18/22_series/22859/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-18/22_series/22859/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c8595a7b0b51b83d9116c4a8608f09e5f618d21
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec801033283066f57ceff9a71c83db9bb34870687dcb8a21388de14d4195b499
+size 75082
diff --git a/marked/Rel-18/22_series/22859/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-18/22_series/22859/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..699561ddd0a0fc266c5cb1907426f54ce44183fc
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d05c830a3a754ea8b41751a636c5c15e6644eb64f4826c6ef751793a897c5833
+size 97952
diff --git a/marked/Rel-18/22_series/22859/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-18/22_series/22859/9cd90f495b95ad2116ff780248c26d95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96a600a5f62e2a6e6796e0148d3bce415b696597
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/9cd90f495b95ad2116ff780248c26d95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3ad4675a67811fca81ed95af3898a5cb9e446d6b78f278b0c54f7d1af868d42
+size 48587
diff --git a/marked/Rel-18/22_series/22859/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/22_series/22859/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..706b104b437ffb0f6c99be2f7d26aa2c83bbea6c
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd0fe3379d46cca6acc025dd6afc4825ec20f67c7d2db315f2ab21c6a53ce5a2
+size 71826
diff --git a/marked/Rel-18/22_series/22859/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/22_series/22859/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d2670ea7ebab6b629888da1533271eff85f629ee
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e9893d6772b14e7cf7acb57f7f08fd42c411770a0a3752df33e21a4f28e5b5a
+size 58317
diff --git a/marked/Rel-18/22_series/22859/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/marked/Rel-18/22_series/22859/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b79c8405b3b5abda3e59b67ab91b3b2e5ec2068d
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71fdbf92ada5e9106966f2fe440baf212dad6010008fd4d409980fa1b4c3929d
+size 38787
diff --git a/marked/Rel-18/22_series/22859/raw.md b/marked/Rel-18/22_series/22859/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4c97ec45f24565b314b331a94bd61d096c735a1
--- /dev/null
+++ b/marked/Rel-18/22_series/22859/raw.md
@@ -0,0 +1,1670 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Personal Internet of Things (PIoT) networks (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'G' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+5G, Network Slice
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-------------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 9 |
+| 4 Overview..... | 9 |
+| 5 Use cases..... | 11 |
+| 5.1 Traffic Scenario: inHome..... | 11 |
+| 5.1.1 Description ..... | 11 |
+| 5.1.2 Pre-conditions..... | 12 |
+| 5.1.3 Service Flows ..... | 13 |
+| 5.1.3.1 General..... | 13 |
+| 5.1.3.2 Onboarding ..... | 14 |
+| 5.1.4 Existing features partly or fully covering the use case functionality ..... | 15 |
+| 5.1.5 Potential Requirements..... | 15 |
+| 5.1A The lost dog..... | 16 |
+| 5.1A.1 Description ..... | 16 |
+| 5.1A.2 Pre-conditions..... | 17 |
+| 5.1A.3 Service Flows ..... | 17 |
+| 5.1A.4 Post-conditions ..... | 18 |
+| 5.1A.5 Existing features partly or fully covering the use case functionality ..... | 18 |
+| 5.1A.6 Potential New Requirements needed to support the use case..... | 18 |
+| 5.2 Positioning with VR and AR..... | 19 |
+| 5.2.1 Description ..... | 19 |
+| 5.2.2 Pre-conditions..... | 19 |
+| 5.2.3 Service Flows ..... | 19 |
+| 5.2.4 Post-conditions ..... | 20 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 20 |
+| 5.3 Media share within PINs Use case..... | 20 |
+| 5.3.1 Description ..... | 20 |
+| 5.3.2 Pre-conditions..... | 20 |
+| 5.3.3 Service Flows ..... | 21 |
+| 5.3.4 Post-conditions ..... | 22 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 22 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 22 |
+| 5.4 Switching between non-3GPP RAT and 3GPP RAT direct device connections Use case..... | 23 |
+| 5.4.1 Description ..... | 23 |
+| 5.4.2 Pre-conditions..... | 23 |
+| 5.4.3 Service Flows ..... | 23 |
+| 5.4.4 Post-conditions ..... | 24 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 24 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 25 |
+| 5.5 Use case: UE accessing Services provided by PIN Elements behind 5G enabled gateway(s) ..... | 25 |
+| 5.5.1 Description ..... | 25 |
+| 5.5.2 Pre-conditions..... | 27 |
+| 5.5.3 Service Flows ..... | 27 |
+| 5.5.4 Post-conditions ..... | 28 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 28 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 29 |
+| 5.6 UE accessing PIN applications hosted by a PIN Element with Gateway Capability ..... | 29 |
+| 5.6.1 Description ..... | 29 |
+| 5.6.2 Pre-conditions..... | 30 |
+| 5.6.3 Service Flows ..... | 30 |
+
+| | | |
+|--------|-----------------------------------------------------------------------------|----|
+| 5.6.4 | Post-conditions ..... | 31 |
+| 5.6.5 | Existing features partly or fully covering the use case functionality ..... | 31 |
+| 5.6.6 | Potential New Requirements needed to support the use case..... | 31 |
+| 5.7 | Tour Guide Use case ..... | 32 |
+| 5.7.1 | Description ..... | 32 |
+| 5.7.2 | Pre-conditions..... | 32 |
+| 5.7.3 | Service Flows ..... | 32 |
+| 5.7.4 | Post-conditions ..... | 33 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 33 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 33 |
+| 5.8 | Use case support of broadcast-based service discovery..... | 34 |
+| 5.8.1 | Description ..... | 34 |
+| 5.8.2 | Pre-conditions..... | 34 |
+| 5.8.3 | Service Flows ..... | 34 |
+| 5.8.4 | Post-conditions ..... | 35 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 35 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 35 |
+| 5.9 | Adding personal health devices to PIN..... | 35 |
+| 5.9.1 | Description ..... | 35 |
+| 5.9.2 | Pre-conditions..... | 35 |
+| 5.9.3 | Service Flows ..... | 36 |
+| 5.9.4 | Post-conditions ..... | 36 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 36 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 37 |
+| 5.10 | Personal health monitoring PIN Elements ..... | 37 |
+| 5.10.1 | Description ..... | 37 |
+| 5.10.2 | Pre-conditions..... | 37 |
+| 5.10.3 | Service Flows ..... | 38 |
+| 5.10.4 | Post-conditions ..... | 38 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 38 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 39 |
+| 5.11 | Dynamic creation of an on-demand PIN at home ..... | 39 |
+| 5.11.1 | Description ..... | 39 |
+| 5.11.2 | Pre-conditions..... | 39 |
+| 5.11.3 | Service Flows ..... | 40 |
+| 5.11.4 | Post-conditions ..... | 40 |
+| 5.11.5 | Existing features partly or fully covering the use case functionality ..... | 41 |
+| 5.11.6 | Potential New Requirements needed to support the use case..... | 41 |
+| 5.12 | Operator managed PIN..... | 41 |
+| 5.12.1 | Description ..... | 41 |
+| 5.12.2 | Pre-conditions..... | 41 |
+| 5.12.3 | Service Flows ..... | 41 |
+| 5.12.4 | Post-conditions ..... | 42 |
+| 5.12.5 | Existing features partly or fully covering the use case functionality ..... | 42 |
+| 5.12.6 | Potential New Requirements needed to support the use case..... | 42 |
+| 5.13 | A smart hospital bed as a PIN element ..... | 42 |
+| 5.13.1 | Description ..... | 42 |
+| 5.13.2 | Pre-conditions..... | 42 |
+| 5.13.3 | Service Flows ..... | 43 |
+| 5.13.4 | Post-conditions ..... | 43 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 43 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 43 |
+| 6 | Considerations..... | 44 |
+| 7 | Potential Consolidated Requirements ..... | 44 |
+| 7.0 | PIN Element Requirements..... | 44 |
+| 7.1 | Gateway..... | 45 |
+| 7.2 | Device and Service Discovery ..... | 45 |
+| 7.3 | Application Servers ..... | 45 |
+| 7.4 | Privacy and Security..... | 46 |
+| 7.5 | Direct Communications..... | 46 |
+
+| | | |
+|-----------------|---------------------------------------------|-----------|
+| 7.6 | Connectivity - QoS - charging ..... | 46 |
+| 7.7 | PIN Management..... | 47 |
+| 7.8 | Void..... | 47 |
+| 7.9 | KPIs..... | 47 |
+| 7.10 | Charging..... | 47 |
+| 8 | Conclusions and Recommendations ..... | 48 |
+| Annex A | Connectivity models ..... | 49 |
+| A.1 | General ..... | 49 |
+| A.2 | PIN direct connectivity with no relay ..... | 49 |
+| A.3 | PIN direct connection using a relay. .... | 50 |
+| Annex B: | Change history..... | 51 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document is aiming at documenting potential new use cases and service requirements to enhance 5GS for the support of Personal IoT networks (PINs), including when the PIN is connected to 5GC.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.261: "Service requirements for the 5G system".
+- [3] 3GPP TS 22.101: "Service principles".
+- [4] Christiane Attig, Nadine Rauh, Thomas Franke, & Josef F. Krems (May 2017) "System Latency Guidelines Then and Now – is Zero Latency Really Considered Necessary?"
+[https://www.researchgate.net/publication/317801643\\_System\\_Latency\\_Guidelines\\_Then\\_and\\_Now\\_-\\_Is\\_Zero\\_Latency\\_Really\\_Considered\\_Necessary/link/5ae18fc4458515c60f662370/download](https://www.researchgate.net/publication/317801643_System_Latency_Guidelines_Then_and_Now_-_Is_Zero_Latency_Really_Considered_Necessary/link/5ae18fc4458515c60f662370/download)
+- [5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS); Stage 1".
+- [6] 3GPP TR 22.858: " Study of Enhancements for Residential 5G; Stage 1".
+- [7] 3GPP TS 22.115: "Service aspects; Charging and billing".
+- [8] 3GPP TS 22.228: "Service requirements for the IP multimedia core network subsystem".
+- [9] ZigBee® Specification
+
+- [10] Z-Wave® Specifications
+
+- [11] 2020 US Census
+[https://www.census.gov/construction/chars/highlights.html#:~:text=The%20median%20size%20of%20a\\_house%20was%202%2C301%20square%20feet.](https://www.census.gov/construction/chars/highlights.html#:~:text=The%20median%20size%20of%20a_house%20was%202%2C301%20square%20feet.)
+- [12] Minimum provision of electrical Socket-outlets in the home
+
+- [13] David Wilson Homes
+
+- [14] National Electrical Code 70®
+
+- [15] 3GPP TR 22.104: "Service requirements for cyber-physical control applications in vertical domains; Stage 1".
+
+- [16]
+- [17] USATODAY 17th Dec 2020
+
+- [18]
+- [19] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2"
+- [20] 3GPP TS 23.558: "Architecture for enabling Edge Applications (EA)"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**direct device connection:** See definition in 3GPP TS 22.261 [2].
+
+**direct network connection:** See definition in 3GPP TS 22.261 [2].
+
+**Guest PIN Element:** Is a PIN Element that is a member of one PIN (Home PIN) and can access any other PIN, if allowed to by that PIN to communicate with the Home PIN.
+
+**IoT device:** See definition in 3GPP TS 22.261 [2].
+
+**PIN direct connection:** the connection between two PIN Elements without any 3GPP RAN or core network entity in the middle.
+
+NOTE 1: A PIN direct connection could internally be relayed amongst other PIN Elements.
+
+NOTE 2 When a PIN direct connection is between two PIN Elements that are UEs this direct connection is typically known as a direct device connection as defined in 3GPP TS 22.261 [2].
+
+**PIN Element:** UEs or non 3GPP devices that can communicate within a PIN.
+
+**PIN Element with Gateway Capability:** a UE PIN Element that has the ability to provide connectivity to and from the 5G network for other PIN Elements that use PIN direct connections.
+
+NOTE 3: A PIN Element can have both PIN management capability and Gateway Capability.
+
+**Editor's Note:** The relationship with FS\_RESIDENT Evolved Residential Gateway will be resolved in the normative phase.
+
+**PIN Element with Management Capability:** A PIN Element with PIN management Capability has capability to manage the PIN.
+
+**Personal IoT Network:** A configured and managed group of at least one UE and one or more PIN Elements or UEs that are (pre-)authorised to communicate with each other.
+
+NOTE 4: The configuration and management of the PIN can be maintained locally or by the 3GPP network.
+
+**PIN-User:** The person who owns the PIN.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|---------------------------------|
+| PIN | Personal IoT Network |
+| UPnP | Universal Plug and Play |
+| DNLA | Digital Living Network Alliance |
+
+# --- 4 Overview
+
+IoT capabilities have been designed for devices that communicate using the traditional cellular network, including battery constrained devices where it is expected that the battery should last in the order of years. Recently standards have been extended to support more vertical IoT devices for factory based, audio visual, medical, mission critical and vehicular solutions. In some contexts, e.g. factory based solutions the concept of a private network has been introduced, this has the added benefit for devices that generate very little user plane traffic (e.g. sensors etc.) the traditional cellular operator might not have to dedicate resources to them in the network and the traffic can stay within the local “factory (private network) environment”. There are 2 consumer segments that have similar traffic characteristics where private networks provide an advantage, where communications are predominately within the constraints of a localized IoT network:
+
+- i) Wearable devices;
+- ii) Home automation
+
+For the purpose of this discussion these will be called “Personal IoT networks” (PINs). These types of networks are very different to commercial IoT device, they are usually less rugged, most highly battery constrained and lifespan of the battery typically a couple of days or weeks. User plane traffic typically stays with a constrained environment, around the body or in the home i.e. within the PIN. Notifications can be received on smartphones that events have occurred within the PIN.
+
+PINs have been around for a long time using others standards however their take up / adoption rate has been low compared to the general smartphone UE.
+
+- a) An example of a home automation PIN can be seen in Figure 4-1 where there are a number of devices in the home that either communicate directly with the hub or indirectly via a relay to the hub. A smartphone in the 5G system can receive notifications regarding events (e.g. door opens) from the home automation PIN.
+
+NOTE 1: The diagram shows home automation but it could equally be a smart office environment, smart police or fire station etc.
+
+
+
+The diagram illustrates a home automation network. A central Gateway (GW) is connected to an Ethernet device and a 5G Core Network. The 5G Core Network is connected to a smartphone for notifications via a (Uu) interface. The GW is connected to several devices: a door lock, a motion sensor, a smart light, a smart plug, and a Guest PIN Element. The door lock, motion sensor, smart light, and smart plug are connected to the GW via relays. The Guest PIN Element is connected to the door lock.
+
+Figure 4-1: Home automation PIN diagram showing various smart home devices connected to a central gateway (GW) which is connected to a 5G Core Network. The devices include a door lock, motion sensor, smart light, smart plug, and a Guest PIN Element. The GW is connected to an Ethernet device and a smartphone for notifications.
+
+**Figure 4-1: Home automation PIN**
+
+- b) Wearables can use a multitude of different access technologies, battery life can in some situations be severely constrained just by the physical dimension limitations e.g. glasses frames, earbuds, blood pressure monitor, pacemaker and rings. Space is also at a premium, capabilities are limited (memory, processing power, even USIM functionality might not be available). Location requirements on wearable devices, especially those with Uu interfaces can contribute to battery drain. Earbuds / Rings are very small, even an ESIM chip takes up valuable space, battery consumption and adds weight to the device. Figure 4-2 shows two wearable networks, one where all the devices communicate via the smartphone and another where glasses act as a relay for smart earbuds.
+
+
+
+The diagram shows two wearable networks, PINa and PINb, connected to a central 5GS (5G System). PINa includes earbuds, glasses, and a watch connected to a smartphone. PINb includes glasses, a watch, and a smartphone connected to a glasses device. Both networks are connected to the 5GS via a smartphone.
+
+Figure 4-2: Wearable PINs diagram showing two separate wearable networks (PINa and PINb) connected to a central 5GS (5G System). PINa includes earbuds, glasses, and a watch connected to a smartphone. PINb includes glasses, a watch, and a smartphone connected to a glasses device.
+
+**Figure 4-2: Wearable PINs**
+
+NOTE 2: The diagram shows wearable networks as used today by consumers, a wearable network could also be employed in industrial, medical or even first responder situations.
+
+In summary, it is considered beneficial for 3GPP specification to address 5G system support of different use cases for PINs.
+
+# 5 Use cases
+
+## 5.1 Traffic Scenario: inHome
+
+### 5.1.1 Description
+
+Houses, offices, light industrial have many opportunities to be automated, the traditional light bulbs, power sockets, thermostats, sprinkler systems, leak detection and the new smart appliances such as ovens, washing machines, faucets etc. can communicate with each other via a Personal IoT Network (PIN). These devices, to be known as PIN Elements, can have the following characteristics:
+
+- i) some have continuous power and others don't;
+- ii) some have strict latency requirements e.g. items that are part of an alarm system, while others provide delay tolerant data;
+- iii) some need to perform an action so an individual sees an action as instantaneous (e.g. ask the voice assistance to turn the light bulb on and it appears instantaneous); and
+- iv) need to perform an action but they don't have strict latency requirements e.g. sprinklers need to come on but it doesn't matter if it's few seconds late.
+
+The PIN Elements listed above and many others that are not listed above can communicate with hubs / gateways within the PIN where some control can take place at the gateway (e.g. thermostats and sprinkler controllers are usually self-contained within the PIN Element, whereas power sockets and light bulbs might communicate with a PIN Element that manages the PIN that control their actions). In addition, thermostats etc. can also communicate with these PIN Elements that manage the network known as PIN Element with Management Capability. Power sockets, light bulbs and switches can also act as relay type devices extending the coverage of the PIN.
+
+NOTE 1: A thermostat controller may have remote sensors that communicate with the thermostat. Effectively there can be a PIN within a PIN.
+
+In case of the PIN Element that provides access to the 5GS, known as PIN Element with Gateway Capability (shown as a GW in Figure 5.1.1-1) these could be placed in one corner of the house.
+
+NOTE 2: The PIN Element with Gateway Capability in this diagram also manages the PIN and also is a PIN Element with Management Capability.
+
+When planning a network in a house many houses suffer from problems of coverage due to the number of floors and other obstacles (i.e. walls, doors, columns, furniture), users will plan or configure their PIN Networks based on their needs and may install or move PIN Elements. When the PIN Element with Management Capability connects to a broadband (also acting as a PIN Element with Gateway Capability) network most houses have only one entry network point where the PIN Element with Gateway Capability can be installed.
+
+
+
+The diagram illustrates an in-home network (PIN) within a house outline. Inside the house, various smart devices are shown: a printer, a tablet, a smart TV displaying a fish, a thermostat, a security camera, and a red smart plug. These devices are connected via dashed lines to a central green box labeled 'GW' (Gateway). The 'GW' is connected by a solid line to a street lamp, which is further connected to a cloud labeled '5G', representing a broadband network connection.
+
+Diagram of an in-home network (PIN) connected to a 5G network.
+
+###### Figure 5.1.1-1: inHome scenario
+
+Furthermore, with the use of millimetre waves there is the danger that the signal is blocked even by people while moving and alternative connection paths are needed. Therefore, enhanced "fully meshed relays" will play a key role in achieving extensive fault tolerant coverage in inHome scenarios. These fully meshed relays allow the resident of the home to position relays (PIN Elements) to create a network that is fault tolerant e.g. should a relay fail, devices such as those that detect motion or a door opening can still reach the PIN Element with Management Capabilities. Data is encrypted from the end device to the PIN Element with Management Capabilities.
+
+NOTE 3: It is up to the home resident to plan their network accordingly so a single failure in the PIN does not stop a PIN Element communicating with any other PIN Element. The home resident is aware that certain types of devices can act as relays.
+
+### 5.1.2 Pre-conditions
+
+Let's consider an average house can be around 100m2-120m2 with 3 floors. Regarding devices and applications within the home we can categorize them in the following groups:
+
+- a) Lighting, appliances, sockets and climate control: This is the traditional home automation and control network where continuous power is available to each PIN Element. These PIN Elements can act as fully mesh relays due to being continually powered. Their time to change state (e.g. light bulb from off to on) needs to occur within 200ms [4].
+- b) Security Systems: This includes traditional security components such as motion detector, door / window sensors, automatic lock (PIN Elements). These items are battery powered, in case of door / window sensors it can be expected that the battery should last for 2+ years. Due to nature of these PIN Elements the delay to inform the PIN Element with Management Capabilities that an event has occurred needs to be 200ms [4]. Some devices will need to rely on mesh relays for routing their data. PIN Elements that are also critical to life and safety e.g. motion sensors, alarms, door locks, alarm systems etc can only be offline for seconds a week. Using an availability calculator [16] 99.999% equates to 1 second or less per day.
+
+PIN-user is aware that they need to plan their network (PIN) and walls, doors etc can present challenges to planning a network. Given PIN Elements can be moved the configuration of a network can change e.g. PIN Element A might have used PIN Element B and Element C as relays however PIN Element B is moved and thus the user who created the PIN needs the PIN Elements within the PIN to discover the network configuration/layout/plan has changed. A user can request the PIN to perform a network configuration/layout/plan test to see what PIN Elements can communicate with other PIN Elements with or without relays.
+
+PIN-user is aware which PIN Elements can act as a relay and which ones cannot.
+
+Some example dimensions of products PIN Elements are:
+
+- I Light switch: 1.76 x 2.2 x 4.1 inches (USA), 86 x 86 x 41 mm (EU);
+- II Power outlet: 1.75 x 2.1 x 4.2 inches (USA), 86 x 86 x 50 mm (EU);
+- III Motion sensor: 18 x 71 x 19 mm, Battery ER142501;
+- IV Light bulb: 3 x 4.9 x 3 inches (USA), 6.5 × 6.5 × 14 cm (EU).
+
+A PIN has at least one PIN Element with Management Capabilities. This PIN Element contains a list of PIN Elements that are in the PIN, what each PIN Element is allowed to do (act as a relay in the PIN, end device), if the PIN Element can be communicated with and what credentials they use to access the PIN. A PIN Device may be used to provision each PIN Element in the PIN Element that manages the PIN (PIN Element with Management Capabilities). The PIN Element with Management capability will need to know information about a PIN Element, some attributes could include:
+
+- Unique identifier for the PIN Element within that PIN;
+- Application(s) (e.g. Application ID) hosted on the PIN Element;
+
+---
+
+1 An example product
+
+- PIN direct connections types supported by a PIN Element
+- Metadata associated with the application (e.g. event has occurred, type of event, timestamp etc);
+- Security credentials;
+
+Approximate no more than [500] bytes of data.
+
+PIN Elements use PIN direct connections to communicate with each other.
+
+### 5.1.3 Service Flows
+
+#### 5.1.3.1 General
+
+Florence (PIN-User) has decided to build a home automation network (PIN) and has purchased a number of PIN devices i.e. some light bulbs, power sockets, a gateway that acts as a voice assistant and door / window sensors (these are known as PIN Elements). The instructions on the PIN Elements indicate that the PIN Device should be no more than 100m direct line of sight from the PIN device managing the PIN however this might be affected by walls, furniture etc. To improve connectivity some PIN Elements can help extend coverage of the PIN e.g. relays (PIN Relay). The light bulbs and power sockets indicate that these devices can help extend the coverage and that the purchaser should position them around their house / condominium so that devices that cannot communicate directly with the device acting as a gateway can use multiple relays if necessary. PIN relays can also be daisy chained together to greatly improve coverage. Florence provisions her PIN Elements into the PIN Element with Management Capabilities. Checking her APP she sees one of the PIN Elements, a door sensors, is offline. Florences moves a PIN Element that acts as a relay, smart light bulb, per instructions she does a “Network configuration check” and then opens and closes the door and sees in real time the door sensor reports the action. A while later, at 10am, her son turns the light switch off as he sees it in the wrong position. Later that day Florence sees the PIN Device, door sensor, offline again as a notification has been provided on her smartphone and finds out her son turned the light switch off at 10am. She decides to install a smart light switch near the door sensor to prevent that issue of the door sensor going offline from occurring again.
+
+Florence speaks to the voice assistant to give it a command to change the state of the light bulb, the light bulbs turns on and off in real time. The door sensor reports when the door is opened and closed with notifications on her smartphone in real-time. Later Florence install a smart door lock on the door with the door sensor. The door lock created a secure connection with the PIN. When she activates the door to open using her app she notices it takes a second before the bolt moves.
+
+Figure 5.1.3.1-1 gives a pictorial view of the new configuration that Florence network can support where if a PIN Element fails communications can still take place via alternative route/path (see dotted blue lines). The diagram shows if the lightbulb is turned off communications can still take place via a power socket or light switch. It also shows Florence’s smartphone receiving a notification of the failures.
+
+
+
+Diagram illustrating a light bulb failure in a Home Automation PIN network. The diagram shows a 'Home Automation PIN' area containing various devices: a door lock, a motion sensor, a Guest PIN Element, a smart light bulb (which is crossed out with a red X, indicating failure), and several 'Relay' units connected to 'SMART PLUG' units. These devices are connected to a central 'GW' (Gateway) unit. The Gateway is connected to an 'Ethernet' device and to a '5G Core Network' cloud. A 'Notification On smartphone' is shown connected to the 5G Core Network via a '(Uu)' interface. A legend at the bottom indicates that a red 'X' represents a 'Failed PIN Element / Connection' and a dashed blue arrow represents a 'New communication path'. The diagram shows new communication paths bypassing the failed light bulb.
+
+**Figure 5.1.3.1-1: light bulb failure (turned off)**
+
+When Florence installs a new PIN Element into the PIN the instructions indicate that the PIN Element with Management Capabilities has to be within 2m so that the 2 PIN Elements can successfully communicate. After that a PIN Element may use a PIN Element that extends the PIN network coverage to successfully communicate with the PIN Element with Management Capabilities.
+
+#### 5.1.3.2. Onboarding
+
+When Florence first setup her PIN she had one device that was designated as a gateway UE. She is aware of the following capabilities of the gateway (it is in the instruction manual and available by the UI). Florence also configures one PIN Element to be able to add subsequent PIN Element to the PIN by scanning in a QR or bar code from the PIN Element.
+
+NOTE 1: Other methods could be possible whereby Florence needs to type in information including encryption keys. This could be by the authorised PIN device (e.g. smartphone) or a UI etc. on the gateway.
+
+She knows that the PIN Element that needs to be added has to be within communications range of the gateway device (i.e. no relay devices can be used yet) so that it can be provisioned into the PIN. Florence is aware that she can provision devices without the gateway UE being connected to the 5G network, but if the gateway UE is connected to the 5G network it will give her the option to:
+
+- allow her PIN to be more secure2. In this situation the PIN Element vendor provides the credentials that need to be downloaded into the PIN Element with Gateway capability; and
+- if a PIN Element, if it supports the capability, to have a better user experience e.g. security equipment, door locks have guaranteed real time operation. (e.g. using operator managed PIN direct connection).
+
+NOTE 2: b) requires credentials to be managed by Florence's service provider.
+
+2 Window, door sensors should be secure as they provide information related to the integrity of a building and the security mechanisms used on those communications links should be more secure than those probably on a light bulb. In the case of the sensor credentials are stored by e.g. the sensor vendor whereas the light bulb ones could be on packaging or provisioned in a more an open fashion.
+
+In both a) and b) the PIN can function (continue to operate) when the PIN Element with Gateway capability has connectivity to Florence's service provider or does not have connectivity. In the case of b) and operator managed PIN direct connection is used the PIN element has to be in coverage of Florence's service provider.
+
+Feature, b), requires Florence to call her service provider to activate the capability. The service provider also provides a service that allows Florence to easily move a PIN Element from using one gateway to another gateway. Service provider services are flat rate or volume charged (e.g. data size, number times operation occurs).
+
+Florence also has the option to allow which PIN Elements can interact with other PIN Elements via the UI of the PIN device that acts as a gateway.
+
+### 5.1.4 Existing features partly or fully covering the use case functionality
+
+See sub-clause 5.5.5.
+
+### 5.1.5 Potential Requirements
+
+[PR 5.1.5-1] The 5G system shall support the ability for a network operator or authorised 3rd party to create a Personal IoT Network.
+
+[PR 5.1.5-2] A PIN shall support both delay and non-delay tolerant services. Maximum delay for non-delay tolerant services can be up to 200ms [4] from the sending PIN Element to the receiving PIN Element (e.g. ask the voice assistant [sending PIN Element] to turn a light on [receiving PIN Element]). Other communication KPIs are shown in Table 5.1.5-1.
+
+**Table 5.1.5-1 – KPIs for communications within a home automation PIN**
+
+| Use case # | Characteristic parameter | | | Influence quantity | | | | | |
+|------------|------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------|-------------------|---------------|-------------------|---------------------------------------|-----------------------|
+| | Communication service availability: target value [%] | Communication service reliability: mean time between failures | End-to-end latency: maximum | Message size [byte] | Transfer interval | Survival time | PIN Element speed | # of PIN Elements in the service area | Service area (note 1) |
+| US Home | 99.999 | TBD | 200ms[4] | TBD | TBD | TBD | stationary | [150] 3 | 214 sq m [11] |
+| UK Home | 99.999 | TBD | 200ms[4] | TBD | TBD | TBD | stationary | 31 [12] + [12]
NOTE 1 | 90 sq m [13] |
+
+NOTE 1 This assumes a UK house has medium rooms of: 3 bedrooms (2 double, 1 single), living room, kitchen, garage, 2 bathrooms, hallway and dining room. 31 sockets plus 12 lightbubs
+
+NOTE: The definitions for the titles of each column can be found in 3GPP TS 22.104 [15].
+
+[PR.5.1.5-3] The PIN shall support fault tolerant operations.
+
+[PR.5.1.5-4] The 5G system shall support mechanisms to provision a PIN to use PIN direct connection in non-operator managed spectrum when it has no connectivity to the 5G system.
+
+[PR.5.1.5-5] The 5G system shall support mechanisms for the PIN to collect charging information (e.g. timestamp for start and stop of communications, amount of data sent/received) regarding PIN Elements that use operator managed spectrum for PIN direct connections, and to report charging data to the 5G system.
+
+[PR.5.1.5-6] The 5G system shall support a PIN Element using either non-operator managed credentials (e.g. provided by a third party), or credentials that are managed by a service provider (e.g. see 3GPP TS 22.101 [3] clause 26A).
+
+3 This is based on calculation done at this website (below). However accurate references need to be provided. Figure has been increased to account for lights, appliances, door bells etc
+
+
+
+[PR.5.1.5-7] A PIN shall be able to still operate when no connectivity exists from a PIN Gateway to the 5CN and or internet.
+
+NOTE 1: PIN Elements can only use non-operator managed spectrum for communications and authentication mechanisms that do not require 5CN and or internet connectivity i.e. PIN Elements that are managed locally.
+
+[PR.5.1.5-8] A PIN shall have a least one PIN Element with Management Capabilities.
+
+[PR.5.1.5-9] The 5G network shall be able to provide backup of management data for PIN elements with management capability based on operator's policy and local regulations.
+
+[PR.5.1.5-10] A PIN Element shall efficiently support a PIN discovery mechanism where PIN Elements can discover, subject to access rights:
+
+- identity of other PIN elements;
+- status of other PIN Element (e.g. on/off);
+- if the topology of the PIN has changed;
+- capabilities of other PIN Elements (e.g. relay, PIN Element with management capabilities, PIN Element with gateway capabilities);
+- PIN Element with gateway capability has external IP connectivity.
+
+NOTE 2: External IP connectivity could be local break out or via the 5G core network.
+
+- connection types support by other PIN Elements (e.g. operator managed, non-operator managed); and/or;
+- battery operated.
+
+[PR.5.1.5-11] The 5G System shall support mechanism(s) to identify a PIN and a PIN Element.
+
+## 5.1A The lost dog
+
+### 5.1A.1 Description
+
+As more and more Personal IoT Networks are deployed there starts to become ubiquitous coverage provided by these networks. This allows for new service offerings to be offered to subscribers. One such offering is where PIN network owners, via user and or service provider authorisation can allow nomadic (guest) PIN Elements to use their PIN networks to reach a specific service in the cloud or in their own personal PIN. A small amount of bandwidth can be dedicated to this. One such offering can be found here [17].
+
+In addition, the PIN network can contain multitude of devices, some using PIN direct connection's that use operator managed spectrum and some that do not. Figure 5.1A.1-1 shows a possible guest PIN Element obtaining access via a PIN2. The user plane data is sent transparently (via a user plane pipe) from the guest PIN2 to a server in the cloud and then server communicates the user plane data to the smartphone (PIN Element) in PIN1.
+
+NOTE 1: The contents of the user plane is outside the scope of 3GPP.
+
+
+
+The diagram illustrates two PIN configurations, PIN 1 and PIN 2, separated by a dashed blue line. Both configurations show a chain of PIN elements connected to a Gateway PIN Element, which is then connected to an antenna and a base station.
+
+- PIN 1:** A Light bulb PIN Element and a Door Bell PIN Element are connected to a Relay PIN Element. The Relay PIN Element is connected to a Gateway PIN Element. A Smartphone is also connected to the Relay PIN Element. The Gateway PIN Element is connected to an antenna, which is connected to a base station.
+- PIN 2:** A Guest PIN Element is connected to a Light bulb PIN Element, which is connected to a Relay PIN Element, which is connected to a Gateway PIN Element. The Gateway PIN Element is connected to an antenna, which is connected to a base station.
+
+**Legend:**
+
+- Red arrow: Direct device connection (operator Managed)
+- Green arrow: Direct device connection (non operator Managed)
+- Purple arrow: Direct network connection
+- Blue pipe: User plane pipe (user data passes transparently)
+
+Diagram illustrating Guest PIN Element accessing a PIN. The diagram is split into two sections, PIN 1 and PIN 2, by a dashed blue line. PIN 1 shows a Light bulb PIN Element and a Door Bell PIN Element connected to a Relay PIN Element, which is connected to a Gateway PIN Element. A Smartphone is also connected to the Relay PIN Element. The Gateway PIN Element is connected to an antenna, which is connected to a base station. PIN 2 shows a Guest PIN Element connected to a Light bulb PIN Element, which is connected to a Relay PIN Element, which is connected to a Gateway PIN Element. The Gateway PIN Element is connected to an antenna, which is connected to a base station. A legend indicates that red arrows represent direct device connections (operator managed), green arrows represent direct device connections (non operator managed), purple arrows represent direct network connections, and a blue pipe represents the user plane pipe.
+
+Figure 5.1A.1-1. Guest PIN Element accessing a PIN
+
+### 5.1A.2 Pre-conditions
+
+Florence (Use case 5.1 as described in Clause 5.1) who lives at number 5 has installed her PIN. Florence has signed up for the guest PIN Element offering from her MNOa.
+
+Houses Number 7 and 25 have installed PINs. They have been given a discount by their respective MNOs if they allow guest PIN Element usage of their PINs. Guest PIN Elements only get small amount of bandwidth from the PIN Network.
+
+Houses 7 MNOc connection is having issues and has no connectivity to the 5G system.
+
+Adrian has a wearables PIN and has been given the same respective discount by his MNOD. He has signed up as he is pet lover and wants lost dogs to be found.
+
+Ellen has a PIN network and has a PIN Element (dog collar) on her dog Pilot to keep a track of him, it is configured to be a guest PIN Element. When the collar detects it's outside of a geofence it will report its location (10 bytes in length [18]4) and Ellen will be alerted within 1 second. Ellen uses MNOc. According to the instructions that came with the dog collar it states it will report its location by using other PINs that have been deployed by people (e.g. doorbells, cameras, power sockets, watches etc) and that a person who deployed them has allowed them to use guest PINs. The owner of the dog collar does not have to ask every PIN owner to allow access.
+
+MNOs provide a guarantee that guest PIN Elements will only consume X bytes a month.
+
+4 Looking for this as a starting point for coding in ASN.1
+ThreeDLocation := SEQUENCE {
+
+```
+latitude Latitude,
+longitude Longitude,
+elevation Elevation
+}
+```
+
+### 5.1A.3 Service Flows
+
+Pilot is a very smart and naughty dog, he loves to explore the neighbourhood and is an escape artist. Ellen has put a PIN Element (i.e low power tracking device) on his collar which when it is outside of a geofence area reports Pilot's location. One day Pilot chases some squirrels and escapes from the backyard. As he roams the neighbourhood he passes houses with PINs, his collar reports its location via Florence's network (light bulb PIN element in House 5) to a dog tracking service.
+
+
+
+Figure 5.1A.3-1: Pilot accessing Florence's PIN. This diagram illustrates the service flow when Pilot (a dog) passes by House 5. Pilot's Guest PIN element connects via a green arrow (Direct device connection, non operator Managed) to a Light bulb PIN Element. This element connects via a green arrow to a Relay PIN Element. A red arrow (Direct device connection, operator Managed) also connects the Relay PIN Element to a Door Bell PIN Element. The Relay PIN Element connects via a red arrow to a Gateway PIN Element. The Gateway PIN Element connects via a purple arrow (Direct network connection) to a base station, which in turn connects via a yellow arrow (User plane (location reporting)) to a server. A thick blue horizontal pipe represents the User plane pipe (user data passes transparently) from Pilot to the server.
+
+**Figure 5.1A.3-1. Pilot accessing Florence's PIN**
+
+House 7 is next, but as it has no connectivity the dog collar makes no report. He also passes Adrian who is in the park with his dog Pongo, Pilot says hello to Pongo and runs off. Adrian has a wearable PIN network and was listening to music so didn't spot Pilot. As Pilot passed his collar reported its location via Adrian's PIN.
+
+
+
+Figure 5.1A.3-2: Pilot accessing Adrian's PIN. This diagram illustrates the service flow when Pilot (a dog) passes by Adrian's location. Pilot's Guest PIN element connects via a green arrow (Direct device connection, non operator Managed) to a Smartphone. The Smartphone connects via a purple arrow (Direct network connection) to a base station, which in turn connects via a yellow arrow (User plane (location reporting)) to a server. A green arrow (Direct device connection, non operator Managed) also connects the Smartphone to an Earbuds PIN Element. A thick blue horizontal pipe represents the User plane pipe (user data passes transparently) from Pilot to the server.
+
+**Figure 5.1A.3-2. Pilot accessing Adrian's PIN.**
+
+Ellen is out grocery shopping and gets notifications on her phone, Pilot was seen at 1:10pm outside House 5 (House 7 also has a PIN but had no 5G connectivity) and later in the park near the dog park area. Ellen pays for her grocery's and starts home. She sees on her smartphone Pilot has stopped at his favourite spot which happens to be by House 25 whose PIN Element door lock picked up Pilot's tracking device.
+
+### 5.1A.4 Post-conditions
+
+Ellen picks up naughty Pilot and takes him home. House 5, 25 and Adrian are not even aware that Pilot was by them. They are aware that some bandwidth was used but not by whom.
+
+### 5.1A.5 Existing features partly or fully covering the use case functionality
+
+3GPP 22.261 [2] clause 6.14 contains requirements regarding IoT devices accessing 5G system using a relay UE:
+
+*An IoT device which is able to connect to a UE in direct device connection mode shall have a 3GPP subscription, if the IoT device needs to be identifiable by the core network (e.g. for IoT device management purposes or to use indirect network connection mode).*
+
+This also applies when using a non-3GPP direct device connection between the IoT device and the relay UE. In this use case the IoT device needs to be identifiable by the core network as the host UE and the guest PIN element have no relationship with each other, the host UE probably does not know the guest PIN element and is not responsible for its traffic. As such lawful interception and data retention etc. as well as charging should not be based on the identity of the host UE but of the guest PIN element.
+
+### 5.1A.6 Potential New Requirements needed to support the use case
+
+None identified.
+
+## 5.2 Positioning with VR and AR
+
+### 5.2.1 Description
+
+It is more and more popular that immersive visual and game with the development of AR and VR. People are always looking for a realistic and interactive experience in the virtual and mixed world. Position tracking of UE devices (such as glasses, Handheld, and wearable devices) is crucial for the interactive experience.
+
+### 5.2.2 Pre-conditions
+
+The PIN Element (termed for glasses, smartphone, etc. wearable devices, power point, light bulb etc.) can send out signals that can enable other PIN Elements to measure and conduct positioning based on the measurements from the signals. The PIN user is aware that they need to position a number of PIN Elements in their room / house so that their PIN Elements that participate in AR/VR games can provide precise position into AR/VR games.
+
+The PIN Devices use PIN direct connections to communicate with each other.
+
+There is an immersive game called NEXGalaxy. In the game, the BOAT(s) are chasing and competing for limited resources on different planets in the universe. Each player has control of the speed and direction of a BOAT with a smartphone (PIN Element). Each player is also viewing the planet with the glasses (PIN Element) they are wearing. The BOAT can also be moved laterally if the controller/player walks or jumps left and right. Depending where the player stands in the room dictates where the player starts in the game e.g. which lane etc. When the game console was setup that hosts the NEXGalaxy game the user (PIN User) had to enter the game consoles position in the room, including room rough dimensions and a rough map of major obstacles e.g. sofa, dining table etc. The map is such that participants in the game are kept at least half a bodies distance from obstacles. This allows the game console to allow a person to move around in the room without hitting obstacles there as the game requires a lot of movement, the movement being reflected as actions in the game. E.g. in NEXGalaxy there is volcano that you can look around, the game console can setup the AR such as a dining table could be the volcano and as person walks around the dining table they walk around the volcano. Players also jump to perform actions in the game, however as a person jumps they change their position in the room and the game display has to adapt to ensure the person does not hit a table, sofa, chair etc.
+
+Friends Yuan and Xun each have their own smartphone (PIN Element) and a smart ring (PIN Element). Yuan owns a pair of VR glasses (PIN Element). Each has configured a personal PIN:
+
+- Yuan's PIN consists of the following PIN Elements: her smartphone, smart ring, 2 VR glasses, a number of smart home automation devices e.g. power socket, light bulbs;
+- Xun's PIN consists of the following PIN Elements: her smartphone and smart ring.
+
+Each PIN Element has at least an accelerometer in it.
+
+Yuan has subscribed to a service from her service provider to provide an operator managed games service that among other things provides the ability to provide accurate absolute positioning. This operator managed game services uses the operator direct device connections capability using the operators managed spectrum.
+
+### 5.2.3 Service Flows
+
+Yuan and her friend Xun want to play the immersive game NEXGalaxy in Yuan's home. They want to enjoy virtual scenarios and real interaction in Yuan home through some PIN Elements (e.g. glasses, smartphone, and wearable devices). Yuan scans a QR code on Xun's smartphone (PIN Element) screen so that Yuan can allow Xun to play the game via Yuan smartphone (PIN Element). Yuan also lets Xun borrow one of her VR glasses (PIN Element). Xun configures her smartphone (PIN Element) to communicate with the borrowed set of VR glasses (PIN Element).
+
+- Yuan and Xun put on some VR glasses (PIN Element) and hold their smartphone (PIN Element) and began the games. They each control a BOAT. They start the BOAT using the smartphone (PIN Element) at the same time from the Base in MARs and compete to see who get to the Volcano first.
+- Yuan starts more quickly by controlling the BOAT using the smartphone (PIN Element).
+- Xun launches a missile targeting Yuan by using the smartphone (PIN Element) to aim at Yuan.
+- Yuan jumps right and left to avoid the missile.
+- During the time when Yuan tries to avoid the missile, Xun accelerates her BOAT through the smartphone (PIN Element) and begins to lead in the race.
+- Xun wins the game. She walks off the plane and turns her head around to check the views around the volcano. It's really beautiful.
+
+Yuan and Xun feel excited about the games. They continue to play the game about an hour.
+
+### 5.2.4 Post-conditions
+
+Yuan and Xun take off their glasses (PIN Element) and put their smartphone (PIN Element) down. They are discussing the details in the game and check the details through replay on their smartphones.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+None identified.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.2.6-1] The 5G system shall support that a PIN Element may be a member of more than one PIN.
+
+[PR 5.2.6-2] The 5G system shall support a PIN Element being added or removed from a PIN by an authorised 3rd party.
+
+[PR 5.2.6-3] The 5G system shall enable PIN direct connections between PIN Elements in a PIN to use licensed spectrum (under the control of a MNO) or between PIN Elements to use unlicensed spectrum (may be under the control of the MNO, or not).
+
+[PR 5.2.6-4] The 5G system shall be able to support positioning for PIN Elements in a PIN.
+
+## 5.3 Media share within PINs Use case
+
+### 5.3.1 Description
+
+Nowadays a person has many electronic devices, such as smart phone, TV, earbuds, speaker, watch, and AR glasses (known as PIN Elements). Ideally the user should be able to choose the device he/she wants to watch the video/listen to the audio among all the devices the user has, with simple operation, without interruption the media being watched.
+
+The media transmitted by a PIN Element could voice, video, Game audio/video and other type of data traffic. The media could be generated locally in the PIN network or from application server. Media share within PINs mean:
+
+- the owner of PIN could choose any device to play the media; or
+- the owner of PIN could switch from one PIN Element to another PIN Element and the media continue to play during the switch between the PIN Elements.
+
+### 5.3.2 Pre-conditions
+
+The User has a smartphone (PIN Element) and at least one of smart earbuds, AR glasses, watch and TV, baby monitor speaker (PIN Elements). The first 3 (smart earbuds, AR glasses, watch) are collectively known as wearables. The collection of all 6 is known as a Personal IoT Network (PIN). All the PIN Elements communicate wirelessly using PIN direct connections.
+
+The user uses the PIN Elements for entertainment, for example, listening to music, watching videos and having WeChat video and phone calls. The earbuds will play notifications, sound and the AR glasses will display video images and notifications. The speaker will play sound.
+
+The user uses the PIN Element to check the real-time monitoring recording (baby camera) of the baby or the house when in or outside of house.
+
+Media (video, audio, voice and etc.) originates from within the PIN e.g. music from smartphone, video and audio from the baby monitor.
+
+### 5.3.3 Service Flows
+
+Whenever the user listens to music, watches movie and has WeChat video and phone calls, the media(audio/video) can be shared among all the devices belonging to the same PIN, and therefore the media can be easily switched to other PIN Elements in the same PIN without interruption to the user entertainment.
+
+#### Service flow 1\_watch a movie:
+
+1. The user starts to watch a movie on the smart phone. The movie is coming from a streaming platform.
+2. The user finds this movie very interesting and decide to watch the movie using AR glasses for 3D audio-visual enjoyment which uses PIN direct connections to transfer the media from the smartphone to AR glasses.
+3. The user wears the AR glasses and choose the movie that was being watched on the smart phone.
+4. The AR glass continue to play the movie from the part that was paused on the smart phone.
+5. The user starts enjoying the movie on the AR glass with better 3D audio-visual enjoyment.
+
+#### Service flow 2\_listening to an audio book or music
+
+1. The User is doing housework with the speaker playing some audio book or music that are stored on the user's smartphone. The connection from the smartphone to the speaker is using PIN direct connection.
+2. The user decides to go running after finishing the house work.
+3. The User wears the earbuds and the audio seamlessly switched from the speaker to the earbuds that communication with the smartphone using PIN direct connection.
+4. The user goes out for running wearing the earbuds and watch, without carrying the smart phone.
+5. The audio continues to play while the user runs outside using the cellular network to communicate with the watch which subsequently uses direct device connection to communicate with the earbuds.
+
+#### Service flow 3\_ baby monitor
+
+1. The user has bought a baby monitor (PIN Element) in their house, the instructions indicate that other PIN Elements can be used to extend the range of the baby monitor and as well if the purchaser wants they can use multiple PIN devices to make the baby monitor solution more resilient.
+2. The baby is put for a daytime nap and the user needs to do some housework. The video from the camera that is in the house is sent to his smartwatch via a PIN direct connection so he can keep an eye on the baby.
+3. In a few rooms of the house he has a large TV and as he goes into a room with a TV the video then appears on the TV from the baby monitor using PIN direct connections to the TV so the user can get on with what he needs to do but can keep an eye on the baby, this is more convenient than looking at a small image on the smartwatch.
+4. The TV/smartwatch detects when the user cannot see the TV and stops displaying the video stream.
+5. The user enters another room with a large TV and the same thing happens, again PIN direct connection is used from the video camera to the TV.
+6. He then moves to the kitchen. As he is cleaning in the kitchen the baby wakes up and he hears the baby crying on the voice assistant that is in the kitchen. The voice is from the video camera and uses PIN direct connections to communicate with the voice assistant.
+
+7. The user uses the PIN Element to check the real-time monitoring recording of the baby when outside of house.
+
+#### Service flow 4 \_Over the top application call
+
+1. when the user is running outside wearing his watch, that uses direct network connection, he receives an over the top application call from his friend.
+2. The user starts to talking to his friend on the over the top application using his watch and his earbud while walking back home.
+3. When the user arrives home, he got a notification that the battery of his watch is low, so he picks up his smartphone that uses a direct network connection and continues to talk to his friend on the over the top application using his smartphone and earbuds.
+4. During his over the top application call with his friend, his friend experiences no interruption at all.
+
+NOTE: In service flow 4 there is only one PIN however it has 2 entry points from the operator's network, the watch and the smartphone.
+
+### 5.3.4 Post-conditions
+
+The users can freely switch the video and/or audio between PIN Elements used and enjoy the same media (audio/video/voice calls) without interruption.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.228 [8] specifies the IP Multimedia (IM) Core Network (CN) subsystem inter-UE transfer (IUT), which provides the capability of continuing ongoing communication sessions with multiple media across different user equipment's (UEs) under the control of the same or different subscribers, and as part of Service Continuity (SC).
+
+3GPP TS 22.228 [8] is not applicable to non-IMS session inter-UE transfer when using direct device connections.
+
+3GPP TS 22.261 [2] clause 6.2.3 has following requirements
+
+- The 5G system shall support service continuity for a remote UE, when the remote UE changes from a direct network connection to an indirect network connection and vice-versa.
+- The 5G system shall support service continuity for a remote UE, when the remote UE changes from one relay UE to another and both relay UEs use 3GPP access to the 5G core network.
+
+3GPP TS 22.261 [2] clause 6.9.2.1 has the following requirements:
+
+The 5G system shall support the relaying of traffic between a remote UE and a gNB using one or more relay UEs.
+
+The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode.
+
+3GPP TS 22.278 [5] defines ProSe Group Communication:
+
+**ProSe Group Communication:** a one-to-many ProSe Communication, between more than two UEs in proximity, by means of a common ProSe Communication path established between the UEs.
+
+In 3GPP TS 22.278 [5] clause 7A.1 defines precisely the means and constraints by which ProSe Group Communication can be enabled and used.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR 5.3.6-1] For intra-PIN communications, a PIN Element shall be able to transmit media to one or more PIN Element at the same time.
+
+[PR 5.3.6-2] A PIN Element shall support service continuity when a PIN Element changes the communication path from one PIN Element to another PIN Element. The communication path between PIN devices may include both 3GPP and non-3GPP access.
+
+[PR 5.3.6-3] The 5G system shall be able to support a PIN which has more than one PIN Element with Gateway Capability.
+
+**Editors Note: SA3 need to be consulted on the security aspects of having more than one PIN Element with Gateway Capability in the PIN.**
+
+## 5.4 Switching between non-3GPP RAT and 3GPP RAT direct device connections Use case
+
+### 5.4.1 Description
+
+There are lots of cases that Smart glasses are paired with a smartphone using non 3GPP RAT for transmitting video information from the smartphone to smart glasses. However, non 3GPP RATs are based on unlicensed frequency. In some areas, if lots of people use unlicensed frequency, the quality of service will be bad. If and when the quality of service goes down the service could be switched to a 3GPP RAT (direct communications) autonomously and the user could have a better experience. In addition, the opposite could be true in that the direct communications could be congested, and therefore it makes sense that both non 3GPP RAT and direct communications could be used together.
+
+### 5.4.2 Pre-conditions
+
+Lihua has one smartphone and one smart glass. The Smartphone (PIN Element) can connect with the Smart glasses (PIN Element) using non 3GPP RAT direct device connections capability. This is Lihua's Personal IoT Network (PIN).
+
+Lihua has also subscribed to her service provider for an operator managed video service, therefore, the Smartphone (PIN Element) can also connect with the Smart glasses (PIN Element) using the operator direct device connections capability using operators managed spectrum. The service provider bills based on data consumption, time, or the operator managed resources used for the service data transmission, e.g. operators managed spectrum. The Smart glasses (PIN Element) can determine if non 3GPP RAT and or the operator managed direct device connections capabilities are congested or not. If operator managed direct device connection service is not available e.g. out of 3GPP coverage the service will not be used by a PIN Element and non 3GPP RAT direct device connection can be used.
+
+The Smart glass (PIN Element) can transmit the video service via both the WLAN and the operator managed direct device connections capability simultaneously. The smartphone is allowed to select to transmit over non 3GPP RAT direct device connection or the non-operator managed spectrum based on some criteria, which are provided by lihua or the operator. The smartphone (PIN Element) allows Lihua to set up a set of parameters to control the video quality when her operator managed video service will be used so that she can control the usage of her operator managed direct device connections provided service.
+
+If requested by the operator, the Smartphone (PIN Element) collects and reports to the operator network the statistics information of the non 3GPP RAT direct device connection, such as the data volume transmitted over non 3GPP RAT direct device connection or the non-operator managed spectrum, if 3GPP authentication was used, service discovery was used.
+
+### 5.4.3 Service Flows
+
+Lihua has one smartphone (PIN Element) and one smart glasses (PIN device). The Smartphone (PIN Element) connects with the Smart glasses (PIN Element) using non 3GPP RAT direct device connection for transmitting video data from the smartphone (PIN Element) to the smart glasses (PIN Element). After work Lihua take the subway back home, she lives in Vienna that has great continuous coverage in the subway system. Lihua watches the video on her smart glasses (PIN Element). The video is being played from her smartphone (PIN Element). When Lihua enters the subway station where there are lots of people, the smart glasses (PIN Element) detects that the quality of non 3GPP RAT direct device connections is bad and the smart glasses (PIN Element) requests the smart phone (PIN Element) to switch all or some of the video packets to operator managed direct device connection service. Lihua may get a notification that this happens however it's the start of the month and she has turned off notifications. Based on some criteria, which are provided by lihua or the operator, the smart phone (PIN Element) requests from the network for some operator managed direct device connections resource to stream the video from the smartphone (PIN Element) to smart glasses (PIN Element). While the video service is transmitted from the smart phone (PIN Element) to smart glasses (PIN Element) using the operator managed direct device connection resource and when requested by the operator, the smart phone gathers the information needed for charging and reported to the operator network. The information needed for charging includes the data transmitted for the video service over the operator managed direct device connection between the PIN Element, time, the operator managed resources used for the service data transmission, e.g. operators managed spectrum and etc.
+
+As Lihua rides the subway, more and more passengers get on. These passengers have also subscribed to the same video service. After some time, the network has limited operator managed direct device connections service resources to give Lihua. However, the smart glasses (PIN Element) finds that some non 3GPP RAT direct device connections resources
+
+can be used. The smart phone then aggregates non 3GPP RAT with operator managed direct device connection services Lihua can receive uninterrupted viewing experience.
+
+If requested by the operator, the Smartphone (PIN Element) collects and reports to the operator network the statistics information of the non 3GPP RAT direct device connection, such as the data volume transmitted over non 3GPP RAT direct device connection or the non-operator managed spectrum if 3GPP authentication was used, service discovery was used.
+
+### 5.4.4 Post-conditions
+
+Lihua watches the movie and notices no degradation in video quality moving into and out of the subway as other people around have issues with their connectivity.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] "The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode" indicates that a UE can transmit simultaneously however direct network mode is between a UE and the network. The use case in sub-clause 5.4.3 has no user plane traffic (i.e. movie) going to the network.
+
+3GPP TS 22.261 [2] sub-clause 6.3.2.1 has the following requirements:
+
+*"Based on operator policy, the 5G system shall be able to provide simultaneous data transmission via different access technologies (e.g. NR, E-UTRA, non-3GPP), to access one or more 3GPP services.*
+
+*When a UE is using two or more access technologies simultaneously, the 5G system shall be able to optimally distribute user traffic over select between access technologies in use, taking into account e.g. service, traffic characteristics, radio characteristics, and UE's moving speed.*
+
+*The 5G system shall be able to support data transmissions optimized for different access technologies (e.g. 3GPP, non-3GPP) for UEs that are simultaneously connected to the network via different accesses."*
+
+These requirements talk about “access technologies” which if you read 3GPP TS 22.261 [2] clause 6.3.1 identifies NR, E-UTRA and non 3GPP. There is no reference to direct device connection in the section.
+
+3GPP TS 22.261 [2] sub-clause 6.5.2 "Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path between UEs attached to the same network, modifying the path as needed when the UE moves during an active communication." This requirement is regarding a UE that connects to the network and not using direct device connectivity.
+
+3GPP TS 22.261 [2] sub-clause 6.9.2.1 contains following requirements:
+
+*"The connection between a remote UE and a relay UE shall be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed band.*
+
+*The connection between a remote UE and a relay UE shall be able to use fixed broadband technology.*
+
+*The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode."*
+
+These requirements do not make mention to any aggregating, switching or splitting of data across non-3GPP RAT and licensed 3GPP RAT.
+
+3GPP TS 22.261 [2] sub-clause 6.19.1 contains selection criteria for 3GPP access network selection. These requirements, as they for “access network” have same deficiencies as list above when analysing 3GPP TS 22.261 [2] clause 6.3.1.
+
+3GPP TS 22.278 [5] sub-clauses 7a-7c contain numerous requirements for ProSe Communication path and EPC Path. ProSe Communications path can also be WLAN. An extract from 3GPP TS 22.278 [5] is below.
+
+#### 7A.0A.2 ProSe Communication
+
+*ProSe Communication enables establishment of new communication paths between two or more ProSe-enabled UEs that are in Communication Range. The ProSe Communication path could use E-UTRA or WLAN. In the case of WLAN, only ProSe-assisted WLAN direct communication (i.e. when ProSe assists with connection establishment management and service continuity) is considered part of ProSe Communication.*
+
+*The network controls the use of E-UTRAN resources used for ProSe Communication for a ProSe-enabled UE served by E-UTRAN. The use of ProSe Communication must be authorised by the operator.*
+
+*According to operator policy a UE's communication path can be switched between an EPC Path and a ProSe Communication path and a UE can also have concurrent EPC and ProSe Communication paths.*
+
+These requirements make no reference to using non-3GPP RAT and licensed 3GPP RAT direct network connection at the same time, and hence do not cover aggregating, switching or splitting of data across. The last sentence from 3GPP TS 22.278 [5] sub-clauses 7a illustrates that concurrent direct network connection and direct device connections are possible.
+
+3GPP TS 22.278 [5] "Subject to operator policy and user consent the EPC and a ProSe-enabled UE shall be capable of negotiating the move of a traffic flow between the EPC Path and the ProSe-assisted WLAN direct path." Indicates that a UE can move traffic between an EPC Path and ProSe WLAN direct path however the use case in sub-clause 5.4.3 has no user plane traffic (i.e. movie) going to the network
+
+3GPP TS 22.278 [5] "Both the HPLMN and VPLMN operators shall be able to charge for ProSe-assisted WLAN direct communications. " however these requirements are written in the context of the network being involved and user plane traffic going to the network.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+[PR 5.4.6-1] The PIN Element can act upon user and operator preferences to aggregate, switch or split the service between non-3GPP RAT and operator managed PIN direct connection services.
+
+[PR 5.4.6-2] When operator managed PIN direct connections are used for PIN UE Element communications the 5G System shall be able to collect charging data, including data transmitted over the operator managed PIN direct connections between the PIN Elements, time, the operator managed resources used for the data transmission, e.g. operators managed spectrum and etc.
+
+[PR 5.4.6-3] When PIN UE Element uses unlicensed spectrum for direct device connections for intra PIN UE device communications the 5G System may, subject to local/regional regulations and user consent, collect statistics data, including if 3GPP authentication was used.
+
+## 5.5 Use case: UE accessing Services provided by PIN Elements behind 5G enabled gateway(s)
+
+### 5.5.1 Description
+
+There are more and more IoT devices or none-3GPP devices, e.g. media server, printer, smart thermostat/sprinkler/blinds, NAS server, smart plug, smart watch, smart pet collar, earbuds, VR goggle headset, smart garage door, etc., that can provide services for users at home or out of home in the home settings. These devices are usually behind a wireless gateway. In recent years, there are some security risks found in such settings due to port forwarding and unsecure connectivity provided by the wireless gateway for in home devices.
+
+When considering the gateway with 5G capability for accessing 5G services, , it is important to enable the support of the secure connectivity for allowing authorized users from anywhere in the world to access authorized services provided by these IoT devices or none-3GPP devices in terms of user authentication and authorization.
+
+These IoT devices or non-3GPP devices acting as a PIN Elements can be smart plug, smart watch, smart pet collar, earbuds, VR goggle headset, etc. that usually are connected to the UE as a PIN Element with Gateway Capability via non-3GPP access, e.g. WLAN, Bluetooth®. When the UE moves, the PIN moves with the UE and its associated PIN Elements. These PIN Elements authorized to communicate with each other are regarded in a Personal IoT Network (PIN). There are other IoT devices, or non-3GPP devices usually stationary connected to the eRG using non-3GPP access (WLAN, wireline), e.g. media server, printer, smart thermostat, smart sprinkler, smart blinds, smart garage, etc. These IoT devices or non-3GPP devices authorized to communicate with each other directly or via the eRG are regarded in a Customer Premises Network (CPN).
+
+**Editor's Note:** this use case assumes that evolved residential gateway (eRG) defined in 3GPP TR 22.858 [6] can operate as a PIN Element with Gateway Capability, which needs further clarification between two studies. For example, in the home or office settings, the PIN Element (non-3GPP device) is stationary installed and can be media server, printer, smart thermostat, smart sprinkler, smart blinds, smart garage door, etc., which can connect to the eRG using non-3GPP access, e.g. WLAN, wireline.
+
+Figure 5.5.1-1 shows the scenarios of the 5G network enabling connectivity service support for the UE using direct network connection (case a) or direct device connection or PIN direct connection (case b and case c) to access services provided by PIN Element. Each PIN Element may provide one or more services. For example, the PIN Element is a smart watch, earbuds, VR goggles, media server, smart TV, smart video doorbell, etc., which provide one media service. For another example, the PIN Element is a NAS server which can provide multiple services, e.g. media service, web server service, live security cams services, etc.
+
+
+
+The diagram illustrates three scenarios for 5G network support for a User/UE accessing services provided by a PIN Element. A horizontal dashed line separates the 'at Home' environment from the external 5G network environment.
+
+- Case (a):** The UE is outside the 'at Home' environment. It has a solid red line connection to the 5G Network. The 5G Network has a solid black line connection to a 'PIN Element with Gateway Capability' inside the 'at Home' environment. This gateway element has a dashed blue line connection to a 'PIN Element (PIN#1)'.
+- Case (b):** The UE (labeled 'PIN#1') is inside the 'at Home' environment. It has a dashed blue line connection to a 'PIN Element with Gateway Capability'. This gateway element has a solid black line connection to the 5G Network and a dashed blue line connection to another 'PIN Element (PIN#1)'.
+- Case (c):** The UE is inside the 'at Home' environment. It has a dashed blue line connection to a 'PIN Element with Gateway Capability', which in turn has a solid black line connection to the 5G Network. The gateway element also has a dashed blue line connection to a 'PIN Element (PIN#1)'.
+
+Figure 5.5.1-1: 5G network support for a User/UE accessing services provided by PIN Element. The diagram shows three cases (a, b, c) illustrating different network configurations. Case (a) shows a UE connected to a 5G Network, which is connected to a PIN Element with Gateway Capability, which is connected to a PIN Element (PIN#1). Case (b) shows a UE (PIN#1) connected to a PIN Element with Gateway Capability, which is connected to a 5G Network and a PIN Element (PIN#1). Case (c) shows a UE connected to a PIN Element with Gateway Capability, which is connected to a 5G Network and a PIN Element (PIN#1).
+
+**Figure 5.5.1-1: 5G network support for a User/UE accessing services provided by PIN Element (dash line is direct device connection or PIN direct connection; solid line is direct network connection)**
+
+In Figure 5.5.1-1, a user using an authorized UE, e.g. smartphone or tablet, accesses the service A provided by an PIN Element which has connection with PIN Element with Gateway Capability via a non-3GPP access technologies, e.g. WLAN, Bluetooth®, etc.
+
+Case (a): the user/UE is out of Home and uses authorised service A provided by a PIN Element behind a PIN Element with Gateway Capability which relays traffic to and from 5G network. The PIN Element with Gateway Capability and the PIN Element connects to each other using direct device connection or PIN direct connection while the PIN Element with Gateway Capability connects to the 5G network using direct network connection.
+
+Case (b): the user/UE operating as a PIN Element is at home and uses authorised service A on the other PIN Element via PIN Element with Gateway Capability which supports relay communication between two PIN Elements. The UE and the PIN Element connect to PIN Element with Gateway Capability using direct device connection or PIN direct connections. One or more PIN Elements can connect to the PIN Element with Gateway Capability.
+
+Case (c): the user/UE operating as a PIN Element is at home and uses authorised service A directly provided by the PIN Element using direct device connection or PIN direct connection. If connecting to 5G network is required by the PIN Element, the UE can operate as a PIN Element with Gateway Capability to relay traffic to/from the PIN Element.
+
+To avoid the potential security/privacy risks that invade the PIN Elements and services, it is important that the 5G network can enable supports of secure access to the PIN Elements and their services for authenticated and authorized users. According to 3GPP TS 22.101 [3] clause 26a, an "User" to be identified could be
+
+- an individual human user, using a UE with a certain subscription, or
+- an application running on or connecting via a UE, or
+- a device ("thing") behind a gateway UE.
+
+In the context of PIN (personal IoT network), a "User" includes a service ("application") running on or connected via a PIN Element behind a PIN Element with Gateway Capability.
+
+The following service aspects for IoT device and non-3GPP device as PIN Element connected to the 5G network via a PIN Element with Gateway Capability, needs to be considered:
+
+- User Identity and user authentication;
+ 1. User Identity of PIN Element or application running on PIN Element;
+
+2. The authentication of User Identity or application running on the PIN Element;
+ - Access to PIN Element or its application running on the PIN Element;
+ - User Profiles and User Identifiers for PIN Element or its applications provided by an PIN Element;
+ - UE policies in the home settings.
+
+### 5.5.2 Pre-conditions
+
+The Incredible family adopts civilian identities and lives at suburbs for a normal life to hide their superheroes identities. To ensure secure communication for the Incredible family accessing services of PIN Elements from anywhere in the world, Mr. Incredible sets up many PIN Elements and subscribes to a reliable network operator's services, which can act as User Identity provider and provide secure access to his PIN Elements and the applications running on or connected to the PIN Element behind the PIN Element with Gateway Capability, for all UEs of his family, including smartphones, tablets.
+
+### 5.5.3 Service Flows
+
+#### Step1: [Users configuration]
+
+Mr. Incredible, signs in his account at operator's network that provides 5G connectivity services for all UEs of his family. In his account, there are two listed subscriptions with gateway capabilities, including one smartphone , i.e. a UE as PIN Element with Gateway Capability, and one eRG. In Mr. Incredible's account, he can create Users with User Identities for family members, PIN Elements, and services provided by PIN Elements.
+
+Further, for each service of the PIN Element behind a PIN Element with Gateway Capability, Mr. Incredible configures User Profiles, e.g. via scanning the QR code of the PIN Element to get some information and editing details manually. For each service identified by a User Identity, it can have one or more User Profile(s) and each User Profile contains the following information:
+
+- User Identifier
+- Specific service settings and parameters, e.g. active/inactive time, number of accesses, etc.
+- Authentication/authorization policy and access restriction policy required for the service, which are going to be used to authenticate/authorize a User for accessing to the PIN Element or application running on the PIN Element.
+- Credential information, e.g. password for the authorized service, security keys for encryption/decryption, and hash algorithm for message digital signing, etc.
+
+For an authorized human user(s), its User Profile can indicate the authorized service identified by User Identity and allowed User Identifiers.
+
+#### Step2: [Registration of PIN Element and Update of User Profiles for services provided by the PIN Element]
+
+(2a): When an PIN Element is turned on, the PIN Element with Gateway Capability discovers and connects to the PIN Device at the first time, the PIN Element with gateway Capability determines if the PIN Element is an authorized User identified by a User Identity indicated in its UE configuration.
+
+(2b): The serving network of the PIN Element with gateway Capability authenticates User Identity of the PIN Element based on its credentials, and then updates User Profiles of the services provided by the PIN Element. In return, the network responds the PIN Element with gateway Capability with the authentication result and updated User Profiles of the registered services.
+
+(2c): The serving network of the PIN Element with gateway Capability further provides updated User Profiles of the services to 5G subscriber's HPLMN. The HPLMN of PIN Element with gateway Capability updates its stored User Profiles of all impacted Users.
+
+(2d): Based on serving network's policies, the serving network can update User Profiles of impacted Users and UE configuration towards PIN Element with gateway Capability.
+
+#### Step3: [User/UE at home or out of home accessing services provided by PIN devices]
+
+Violeta, Mr. Incruedible's daughter as an authorized user (User) of the service provided by a PIN Element, would like to use the authorized UE to access a registered application-A of a PIN Element behind a PIN Element with gateway Capability. For example, the PIN Element is a smart garage door and Violeta would like to request the smart home application-A on the PIN Element to open the garage door for the delivery crew to put the package inside the garage. The communication method that connects her UE and the PIN Element is different based on the location of her UE as follows:
+
+- Case (a): When Violeta (User) using authorized UE is out of home, the 5G network connects the UE to the PIN Element behind the PIN Element with gateway Capability.
+- Case (b): When Violeta (User) using authorized UE is at home, the PIN Element with gateway Capability discovers and connects the UE acting as an PIN Element and using PIN direct connection or direct device connection based on stored UE policies or user preferences.
+- Case (c): When Violet (User) using authorized UE is at home, the UE acting as a gateway UE discovers and connects with PIN Device directly via a non-3GPP access technologies, e.g. Bluetooth, WiFi, or via 3GPP direct communication, instead of via indirect communication over 5RG, based on stored UE policies of the UE or user preferences.
+
+(3b): Based on stored User Profiles of the PIN Element with authorised Users, the PIN Element with gateway Capability can determine whether to accept access request of the PIN Element from the User/UE.
+
+(3c): The PIN Element with gateway Capability can further perform user authentication of the application-A based on the security policies and credentials in stored User Profiles of the application-A. If the application-A is configured to apply user authentication by the 5G system, the PIN Element with Gateway Capability requests user authentication for the application-A by the 5G system.
+
+(3d): The PIN Element with gateway Capability forwards the service access request to the PIN Element only if the user authentication is successful. Otherwise, the PIN Element with gateway Capability rejects the request for service access.
+
+(3e): The PIN Element with gateway Capability starts to forward the traffic to/from the PIN Elements.
+
+#### **Step4: [UE policies in the home settings]**
+
+When the authorized User/UE moves from out of home, i.e. case (a), to in home, i.e. case (b) or case (c), the User can manually determine how the used UE adopts case(a)/case (b)/case(c), or UE can automatically adapt to case(a)/case(b)/case (c) based on the UE policies, including the following information provisioned by the 5G network:
+
+- one or more operation modes (e.g. PIN Element, UE, PIN Element with gateway Capability);
+- communication methods (e.g. direction network connection, direct device connection, PIN direct connection);
+- location information.
+
+### **5.5.4 Post-conditions**
+
+The Incruedible family can safely live with hidden superheroes identities by securely accessing application of the PIN Elements from anywhere in the world without compromising the security of the PIN Elements/services at home.
+
+### **5.5.5 Existing features partly or fully covering the use case functionality**
+
+Referring to 3GPP TS 22.101 [3] clause 26a, the user to be identified could be an individual human user, using a UE with a certain subscription, or an application running on or connecting via a UE, or a device ("thing") behind a gateway UE. The following service requirements have been supported:
+
+- The 3GPP network shall be able to provide a User Identifier for a non-3GPP device that is connected to the network via a UE that acts as a gateway.
+- The 3GPP network shall support to perform authentication of a User Identity used by devices that are connected via a UE that acts as a gateway.
+- The User Identifier may be provided by some entity within the operator's network or by a 3rd party.
+- The 3GPP system shall be able to take User Identity specific service settings and parameters into account when delivering a service.
+
+NOTE: The requirement applies to 3GPP services and non-3GPP services that are accessed via the 3GPP System
+
+- The 3GPP system shall be able to store and update a User Profile for a user.
+- The 3GPP System shall support to authenticate a User Identity to a service with a User Identifier.
+- When a user requests to access a service, the 3GPP System shall support authentication of the User Identity with a User Identifier towards the service if the level of confidence for the correct association of a User Identity with a User Identifier complies to specified policies of the service.
+- A service shall be able to request the 3GPP network to only authenticate users to the service for which the association of the user with a User Identifier has been established according to specified authentication policies of the service.
+- Subject to operator policy, the 3GPP system shall be able to update User Profile related to a User Identifier, according to the information shared by a trusted 3rd party.
+- The User Profile may include one or more pieces of the following information:
+ - additional User Identifiers of the user's User Identities and potentially linked 3GPP subscriptions,
+ - used UEs (identified by their subscription and device identifiers),
+ - capabilities the used UEs support for authentication,
+ - information regarding authentication policies required by different services and slices to authenticate a user for access to these services or slices.
+ - User Identity specific service settings and parameters.
+Those shall include network parameters (e.g. QoS parameters), IMS service (e.g. MMTEL supplementary services) and operator deployed service chain settings.
+ - User Identity specific network resources (e.g., network slice).
+
+The following service requirement in 3GPP TS 22.101 [3] clause 26a provide the principle for user centric identifiers and authentication by the 3GPP system:
+
+- The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services.
+
+This use case and requirements consider that the application running on the PIN Element is a non-operator deployed (i.e. external non-3GPP) services behind a PIN Element with Gateway Capability in a PIN.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[PR-5.5.6-1]: The 5G system shall support secure mechanisms for a PIN Element using direct PIN connection or via PIN Element with Gateway Capability to access and communicate with another PIN Element for a PIN.
+
+**Editor's Note:** evolved residential gateway (eRG) defined in 3GPP TR 22.858 [6] is assuming with PIN element gateway capability which needs further clarification in both studies.
+
+[PR-5.5.6-2]: The 5G system shall be able to support “User Identity and Authentication” requirements (as defined in 3GPP TS 22.101 [3] clause sec 26.a) for PIN Elements of a PIN.
+
+## 5.6 UE accessing PIN applications hosted by a PIN Element with Gateway Capability
+
+### 5.6.1 Description
+
+PIN elements (e.g. media server, printer, smart thermostat/sprinkler/blinds, smart lightning system, NAS server, etc.) can be located behind a PIN Element with Gateway Capability (e.g., a residential gateway with PIN capability, or a UE with gateway PIN capability). This PIN Element with Gateway Capability can host, or locally be connected to, significant compute and storage resources. , which can host an Application Server. An application on an Application
+
+Server can be either in the MNO domain (i.e. a trusted application) or external to the MNO domain (i.e. an authorized third-party application).
+
+An AS can be useful to process sensitive data locally. Data generated by some PIN elements can be sensitive, it is therefore important to limit the scope of its dissemination (e.g. temperature and light readings can be used to know if there is someone at home). The AS can also be useful to perform latency sensitive processing. For games and office applications it can be beneficial to render a latency sensitive application locally. The AS can be accessed by local users located in the PIN network, or by remote users connected through the 5G network.
+
+The AS can be hosted on a locally connected hardware hosting platform (e.g., a game console, an application server), and/or be embedded in a PIN Element with Gateway Capability (e.g., leveraging virtualization technology to host AS on the PIN element). While an AS can be a standalone service, it can also be an on-site extension of an in-network service hosted on a hosting environment such as an edge computing platform. In this case, the service operator (e.g., a MEC server operator), can influence discovering/authorizing/orchestrating an AS. The AS can be under the control of a 5G network operator, a customer or an authorized third party.
+
+
+
+Diagram illustrating UE Accessing a PIN application hosted by a PIN Element with Gateway Capability. The diagram shows a PIN network containing a PIN Element and UE1. A PIN Element with Gateway Capability (and any locally connected PIN computing/storage devices) contains a Hosting environment and an AS. UE1 is connected to the PIN Element. UE2 is connected to the 5G Network, which is connected to the AS. Dashed orange arrows indicate the flow of data from UE1 to the AS and from the AS to UE2.
+
+**Figure 5.6.1-1. UE Accessing a PIN application hosted by a PIN Element with Gateway Capability**
+
+Case (a): the user/UE1 is at home and uses a client application that connects to an AS deployed at home.
+
+Case (b): the user/UE2 is out of home and uses a client application that connects to an AS deployed at home (on the PIN Element with Gateway Capability or on other hardware at home). UE2 is connected to the 5G network, e.g., it may be in another PIN.
+
+Service aspects:
+
+- 1) Deployment of an AS on a hosting platform on, or locally attached to, a PIN Element with a Gateway Capability hosted Service Hosting Environment and hosted on the applications by service provider.
+- 2) Access to AS hosted in PIN, by UE2 outside of home.
+- 3) Additional aspects are already covered in 3GPP TR 22.858 [6], clause 5.4 and clause 5.5. Therefore no specific new routing support is needed between PIN element/UE1 and AS:
+ - a) Access to AS in PIN by UE1 or PIN device from inside home.
+ - b) Access to services offered by PIN elements or UE1 from AS in PIN.
+
+### 5.6.2 Pre-conditions
+
+User deploys PIN elements behind a PIN Element with Gateway Capability and subscribes with a service provider for AS. This subscription can be directly with the service provider(s), or through a 5G network operator.
+
+### 5.6.3 Service Flows
+
+- 1) Setup:
+ - a) Hosting environment is installed on PIN Element with Gateway Capability or other PIN element with compute/storage capability (by service provider, 5G network operator or User). User requests some
+
+compute/storage resources (in PIN Element with Gateway Capability or other PIN element with compute/storage capability) to be reserved for usage by the hosting environment
+
+b) Service provider can provide and configure an AAA server to control access to AS hosted in PIN.
+
+c) AS is enabled on hosting environment (by service provider, 5G network operator or User).
+
+#### 2) Using an AS:
+
+a) User installs client applications on UE, e.g. a client application that configures temperature at home based on time or day or other triggers.
+
+b) Service provider provisions corresponding serving AS in hosting environment in PIN.
+
+c) Client application on UE connects through 5G network to serving AS in PIN, after authorisation from AAA server. User configures application through the client. The serving AS can communicate with PIN element, e.g. to collect and process data locally.
+
+### 5.6.4 Post-conditions
+
+The user can install and use a different UE application supported by the service provider. The service provider deploys corresponding AS in PIN. Suitable AS include all kind of applications acting on privacy sensitive data, and, when the client UE is at home or close to home, latency sensitive rendering or interactive application components for games or office applications.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+The following potential requirements defined in 3GPP TR 22.858 [6] partly cover the use case functionality:
+
+[PR. 5.4.6-001] The 5G system shall be able to support efficient routing, without going through the 5GC, for the communication between a UE and a non-3GPP device, via the residential gateway and an indoor small base station connected to that residential gateway.
+
+[PR. 5.5.6-001] The 5G system shall be able to provide E2E QoS control for the communication path between the UE and a residential gateway via an indoor small base station.
+
+[PR. 5.5.6-002] The 5G system shall be able to support efficient routing for communication between UEs via a residential gateway without going through the 5GC.
+
+[PR. 5.5.6-003] The 5G system shall ensure the use of a residential gateway does not compromise the security of any PLMN or broadband access network.
+
+[PR. 5.5.6-004] The 5G system shall ensure the use of a residential gateway does not compromise the security of the UE.
+
+[PR. 5.5.6-005] The 5G system shall enable the network operator associated with a residential gateway to control the security policy of the residential gateway.
+
+The following 3GPP solutions are incompatible with this use case as they address different areas of the 3GPP system architecture:
+
+3GPP TS 23.548 [19]: 5G System Enhancements for Edge Computing: Figure 4.3-1 in clause 4 defines the reference architecture and connectivity models for Edge Computing support in the 3GPP system.
+
+3GPP TS 23.558 [20]: Architecture for enabling Edge Applications (EA). This specification defines the application enablers for Edge Computing.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[PR 5.6.6-1] Subject to the PIN being connected to the 5G Network, the 5G system shall be able to provide support for a PIN element discover and access an application on another PIN element. Discovery mechanisms are needed both inside the PIN and to UEs connected to the 5G network, e.g., PIN elements in other PINs, subject to the PIN being connected to the 5G Network.
+
+NOTE: Discovery mechanisms on PIN elements when there is no connectivity to the 5G system may also be needed.
+
+[PR 5.6.6-2] Based on operator policy and subject to the PIN being connected to the 5G network, the 5G network shall be able to support routing of data traffic between a PIN element and an application on another PIN element.
+
+[PR 5.6.6-3] Subject to the PIN being connected to the 5G network, the 5G system shall be able to support QoS for access by a PIN element to an application on another PIN element.
+
+[PR 5.6.6-4] Subject to the PIN being connected to the 5G network, the 5G system shall support a secure mechanism for a PIN element to access an application on another PIN element.
+
+## 5.7 Tour Guide Use case
+
+### 5.7.1 Description
+
+There are many attractions around the world that are very popular with tourists. Some of the things to see at an attraction have a lot of history or a lot information to be convey about it e.g. how it works etc. In order to help the tourists and provide them with more information tourists can participate in tours, be they either audio tours where by the tourist is given a digital media player, the digital media player being configured for the tourist language or a personalised tour where a tour guide provides a description. In the latter case the tour guide probably gives the tour in one language and can also answer questions.
+
+In both the audio tour and tour guide tour a headset and digital media device are provided to the tourist. The headsets and media devices are usually all the same meaning that the tourist is unfamiliar with how they operate. In addition, a large number of these need to be maintained by the tour company including spares in case there are operational problems. Batteries also need to be charged. When digital media device is provided if additional information for tourists needs to be added / removed all of the digital media players need to be updated.
+
+This use case looks at how a user with a smartphone and set of wearable devices can participate in a tour without specialised equipment.
+
+### 5.7.2 Pre-conditions
+
+Each tourist has a smartphone (UE) (PIN Element) and at least one of smart earbuds and eye glasses (additional PIN Elements). The later 2 are collectively known as wearables. The collection of all 3 is known as a Personal IoT Network. The earbuds and eye glasses communicate wirelessly using PIN direct connections. Tourists use their PINs for listening to music, watching videos and having messenger application video and phone calls. The earbuds will play notifications, sound and the eye glasses will display video images and notifications.
+
+A tour guide has a smartphone (UE), smart earbuds and eye glasses. The earbuds and/or eyeglasses may be IoT devices that communicate with the UE within the PIN.
+
+In popular tourist destinations the Quality Tour Guide (QTG) has a Service Level Agreement (SLA) with service provider C to ensure that the tour guide tours are of the best quality. QTG has been authorised by service provider C to be able to add tourists into QTG PIN. Service provider C also ensures that the security of the service provided to QTG is such that those that have not been authorised by QTG to join the group cannot hear or see QTG tour. Cheaper Tour Guide (CTG) has the same equipment but does not have an SLA, they cannot guarantee a high level of security as QTG can to their tour participants.
+
+### 5.7.3 Service Flows
+
+Terracotta Warriors is a very popular place in China where millions of visitors go each year. Peng (uses service provider A) and Pan (uses service provider B) have decided to visit and are going to take a tour with Quality Tour Guide (QTG) (uses service provider C). They also invite their friend Adrian (uses service provider D from another country, data roaming is turned off) to join. While Adrian is on his way to meet his friends he listens to music on his earbuds from his smartphone.
+
+Meanwhile Pongo and Poppet have also decided to visit but have decided to take a tour with Cheaper Tour Guide (CTG).
+
+When Peng, Pan and Adrian arrive at QTG their earbuds provide a notification sound and the smart glasses provide a visual indication that QTG service is available. They all acknowledge on their smartphone that they authorise QTG to
+
+provide the service. In the authorisation information collateral provided by QTG it indicates that QTG has no access to personal information from tour participants (e.g. phone number, IMEI, UICC ID etc) however QTG's service provider will have access to such information for quality assurance purposes. The collateral also indicates that QTG requires access to microphone, earbuds and display capabilities. Pan further configures the service so that he can get notifications from all his other services while Peng has chosen to not be disturbed while in the tour. Adrian has no data service and can only participate in the tour offered by QTG but can still listen to his music. QTG is notified that 3 tourists are ready for a tour and sees a picture of them on their headset.
+
+Pongo and Poppet arrive at CTG where they scan a QR code for the CTG service. CTG receives notification that 2 tourists are ready for a tour.
+
+QTG and CTG take their respective tourists to the 1st sight of a clay warrior. It is very busy at the exhibit with lots of tourists and other tour guides giving their tours. QTG, and CTG give basically the same tour. At this exhibit they provide a verbal description of the clay figure, provide some pictures of the clay figure being excavated and small video clip from the farmer who discovered the clay figure. As Peng, Adrian and Pan listen it is just like standing next to the tour guide with no other tourists, the audio quality is superb. As the pictures are displayed on the smartglasses with some audio description the video then starts to play and can be seen on the smartglasses. Suddenly Pan receives a notification on the glass's and less pounced notification tone of a WeChat group message, it is from their manager Fei who wants to talk to Pan and Peng. Peng does not get the notification as he has opted not to be disturbed. Adrian has no other service apart from the tour. Pan receives a messenger application call from Fei, the audio from the video display is muted and the messenger application is received from the smartphone UE. Pan walks into a huge metal structure, as Pan is on the messenger application call all of the sudden the call stops. Pan looks at his phone and notices that there is no cellular service.
+
+While Peng, Adrian and Pan were having their tour Poppet and Pongo were receiving the same type of tour from CTG. Poppet and Pongo's audio quality was not as good as Peng and Pan's, and when the video stream was playing at times the sound would be lost or a video frame corrupted. The problems seemed to get worse when there were more people around, especially when it got very crowded.
+
+Later that week QTG receives a bill from service provider C indicating that 3 tourists used the service for time Y and consumed Z bytes of data.
+
+### 5.7.4 Post-conditions
+
+Service provider C is provided with a set of records indicating that QTG used a specific amount of PIN data.
+
+Service provider C is provided with the identities of the UEs that joined QTG PIN.
+
+All the individuals had successful tours.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] clause 6.9.2 contains requirements for UE communications with the 5GS using a relay and direct device communications.
+
+3GPP TS 22.261 [2] clause 6.3 contains requirement
+
+- The 5G system shall support the capability to operate in licensed and/or unlicensed bands.
+
+3GPP TS 22.101 [3] clause 26a.
+
+3GPP TS 22.261 [2] sub-clause 6.3.2 and 3GPP TS 22.278 [5] sub-clauses 7a-7c contains requirements. See clause 5.4.5 for an analysis of these requirements.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR 5.7.6-1] The 5G system shall support that a PIN Element may be a member of more than one Personal IoT Network.
+
+[PR 5.7.6-2] The 5G system shall support a PIN Element being added or removed from a PIN by an authorised 3rd party.
+
+[PR 5.7.6-3] The 5G system shall enable PIN direct communications between PIN Elements in a PIN to use licensed spectrum (under the control of a MNO) or between PIN Elements to use unlicensed spectrum (may be under the control of the MNO, or not).
+
+[PR 5.7.6-4] The 5G system shall be able to provision PIN Elements that have been authorised to use that PIN with the necessary configuration parameters to use that PIN subject to MNO and local policies.
+
+[PR 5.7.6-5] The 5G system shall be able to support a PIN Element shall be able to concurrently use both operator managed and non-operator managed PIN direct connectivity with another PIN Element.
+
+[PR 5.7.6-6] The 5G system shall be able to support that a PIN Element can support concurrent communications with PIN Elements in more than one PIN.
+
+[PR 5.7.6-7] The 5G system shall be able to provide secure communications between PIN Elements in a PIN or across different PIN.
+
+## 5.8 Use case support of broadcast-based service discovery
+
+### 5.8.1 Description
+
+In a home network, services are provided for e.g. home automation and wireless hi-fi, which often are based on e.g. UPnP/DNLA, Bonjour and other protocols that can make extensive use of discovery and other broadcast-type messages. The user wants to be able to use the service via both the home network (e.g. Wi-Fi) as well as via the public network.
+
+Several services make extensive use of broadcast messages, e.g. smart home systems. The status or discovery-like messages in e.g. UPnP/DNLA, Bonjour and other protocols are broadcast to all 'participating' IoT devices in the network. This is less of a problem when the service is used in a home network (e.g. via LAN) only. However, when the PIN is used outside the home network via a public network (e.g. smartphone joins the PIN via the 3GPP Network), the phone still receives all broadcast messages. This can cause increased messaging to the UE, while these messages are not always relevant to the user.
+
+The user should have the choice to receive discovery and status messages on demand, or filtered (e.g. only when there is a status change) when using the service via the public network.
+
+Furthermore, the 5G system needs to ensure that the service discovery messages are authentic and sent in sufficiently low numbers as to be not present an obstacle to useful transmissions within the PIN.
+
+### 5.8.2 Pre-conditions
+
+The following pre-conditions apply to this use case:
+
+- IoT devices and the residential gateway are connected to an in-home network
+- Service discovery protocols are used to discover services, provide service control and exchange service status
+- The residential gateway has a subscription to the 5G system
+- IoT devices do not have an individual subscription to the 5G system
+
+### 5.8.3 Service Flows
+
+Mary has a smart home system in her home, in which wireless hi-fi systems (IoT device) are connected to a media server (IoT device) via a non-3GPP wireless radio technology in an in-home network. The IoT devices use a broadcast-based service discovery to find other IoT devices in the network. If Mary wants to control the IoT devices in this smart home system, she uses her smartphone which is also connected to the same in-home network.
+
+Mary is in her living room and wants to turn on the hi-fi system to listen to music from her media server. Mary can easily do this using her smartphone.
+
+It is a nice day outside and Mary decides to sit in the garden. Mary wants to listen to the music outside but cannot hear the music, so she tries to change the volume of the wireless hi-fi system using her smartphone. However, Mary discovers that she is using the public network instead of the in-home network, and therefore cannot control the smart home system using her smartphone.
+
+Mary is unhappy with the situation and therefore she purchases a solution from her network operator that allows her to control the wireless hi-fi system via the public mobile network using her smartphone.
+
+Now she can control the music from her smartphone, even when she is outside. Fortunately, the operator solution filters the broadcast traffic, so that these broadcast messages are not counted for the amount of data she is sending via the mobile network.
+
+### 5.8.4 Post-conditions
+
+The person can control the wireless Hi-Fi system **indoor and outdoor**, using both in the in-home network and via the public mobile network (PLMN).
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+3GPP TS 22.261 [2] specifies service discovery for UEs, but not in the context of a PIN.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR 5.8.6-1] The 5G system shall enable service discovery of PIN Elements (e.g. based on certain device applications) in PIN by UEs in the PIN or via the public network.
+
+[PR 5.8.6-1a] The 5G system shall enable an authorized PIN user to configure which UEs connected to the public network can perform service discovery of PIN Elements in a PIN. The 5G system shall support configuration per 5GLAN VN, per group of UEs, or per individual UE.
+
+[PR 5.8.6-2] The The PIN Element with gateway capability shall support optimization of service discovery of PIN Elements in a PIN by UEs on the public network, e.g. by reducing the amount and frequency of service discovery messages sent from PIN Elements.
+
+[PR 5.8.6-3] The 5G system shall support a mechanism(s) to mitigate a malicious flood of service discovery messages.
+
+[PR 5.8.6-4] The 5G system shall support a mechanism(s) to mitigate spoofing of service discovery messages.
+
+## 5.9 Adding personal health devices to PIN
+
+### 5.9.1 Description
+
+Due to the increasing costs and pressure on the healthcare system, care providers, insurance companies and people themselves are looking at new ways to monitor their health, and manage people's health remotely. One way this could be achieved until now is that people buy for example a smartwatch or step counter themselves, pair it to their phone, and download an application to their phone to monitor some of their health data. As the requirements for these devices are getting more demanding, requiring to monitor additional physiological data with higher accuracy and improved reliability, and moving towards cloud/edge based analysis of these streams of data, also the requirements on the underlying network connections and manageability of these devices gets more demanding. It also should be made as easy as possible for the user to be able to connect and manage these networked health devices.
+
+In this use case, Fred has been feeling exhausted in the last weeks and went to his general practitioner for a check up. The general practitioner performed a thorough exam and told Fred that he is quite worried about his health, given that his blood pressure is way too high, his cholesterol is at alarming levels, and that he has initial signs of diabetes and heart problems. If Fred continues like this, he has a serious chance of heart failure or ending up in the hospital. Next to some medicines, his general practitioner subscribes him to a new program offered by his insurance company in cooperation with a health provider to monitor Fred's health. This new program includes a 24/7 wearable monitoring device combined with a cloud service operated by the health provider for early detection and warning of heart arrhythmia and heart failure and hypertension. The device will be sent to Fred's home in a few days.
+
+### 5.9.2 Pre-conditions
+
+Fred has a 5G enabled mobile phone UE with a USIM and a valid 5G subscription, and supports the PIN gateway UE function. Fred also has a Wi-Fi Access Point at home that may be integrated in or associated with a residential gateway connected to the 5G network.
+
+The 24/7 wearable monitoring device uses non-3GPP RAT (e.g. Wi-Fi) and may not be equipped with a (e)UICC.
+
+This use case assumes that the health provider has an SLA with Fred's mobile operator and that the insurance company either pays or allows Fred to get reimbursed for any additional data or subscription extensions.
+
+### 5.9.3 Service Flows
+
+Fred receives a package that includes a 24/7 wearable monitoring device from his insurance company. The package also includes a set of instructions to follow. All he has to do is use the camera on his 5G enabled UE to scan a QR code on the wearable monitoring device (or e.g. touch the device with NFC).
+
+Fred unpacks the 24/7 wearable monitoring device and scans the QR code using his 5G enabled UE, acting as a PIN gateway UE. Upon doing this, a sequence of events is initiated, which includes the provisioning of credentials (and other configuration information) onto the 24/7 wearable monitoring device enabling it to setup an identifiable connection to an application server through the 5G core network to which the 5G enabled UE is connected.
+
+The connection may be an indirect network connection through the 5G enabled UE, and may be operated by a slice that offers the QoS and reliability guarantees required for this application. In order to facilitate that the 24/7 wearable monitoring device can always connect to the application server, without requiring the 5G enabled UE to be always available or nearby (e.g. wearing the 24/7 wearable monitoring device under the shower, in bed or when the 5G enabled UE is out-of-energy), the 24/7 wearable monitoring device also gets temporary credentials to allow the device to temporarily disconnect from the 5G enabled UE and directly connect to the 5G core network via non-3GPP access to communicate with the application server.
+
+NOTE 1: The direct network connection via non-3GPP access could be enabled e.g. via a trusted network access entity, such as a managed residential gateway or a non-3GPP interworking function. This direct connection does not necessarily need to be permanently enabled, e.g. only be valid when the 24/7 wearable monitor device can temporarily not connect via the 5G enabled UE or when the signal between the 24/7 wearable monitor device and the 5G enabled UE is weak, or only be valid as long as the 5G enabled UE can once in a while update the credentials or validate that the 24/7 wearable monitor is still within operating range.
+
+NOTE 2: The wearable monitoring device can start beeping if it has not been in range of the gateway UE before the credentials expire. The device can also beep if it gets out of coverage of both the gateway UE and AP.
+
+NOTE 3: How the 24/7 wearable monitor device gets paired with a Wi-Fi access point is not in scope of this use case.
+
+### 5.9.4 Post-conditions
+
+The data from the 24/7 wearable monitoring device is continuously sent to the application server through the 5G network. Fred feels very safe knowing that his health is constantly being monitored.
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+#### **From 3GPP TS 22.261 [2] "Service requirements for the 5G system":**
+
+The connection between a remote UE and a relay UE shall be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed band.
+
+The 5G system shall support a secure mechanism for a home operator to remotely provision the 3GPP credentials of a uniquely identifiable and verifiably secure IoT device.
+
+- *Note that the above requirement only partially covers the above mentioned uses case. 3GPP currently relies on the external GSMA remote provisioning framework to perform this function. However, the remote provisioning framework requires a (e)UICC to be supported on the UE, which is not required in this use case. This requirement may need to be further clarified or additional requirements may need to be added to cover non-UICC, non-3GPP RAT devices and the use of a gateway UE to be involved in the provisioning or communication.*
+
+#### **From 3GPP TS 22.101 [3] "Service aspects; Service principles":**
+
+The 3GPP network shall be able to provide a User Identifier for a non-3GPP device that is connected to the network via a UE that acts as a gateway.
+
+The 3GPP network shall support to perform authentication of a User Identity used by devices that are connected via a UE that acts as a gateway.
+
+A subscriber shall be able to link and unlink one or more user Identities with his 3GPP subscription.
+
+The User Identifier may be provided by some entity within the operator's network or by a 3rd party.
+
+The 3GPP system shall support to interwork with a 3rd party network entity for authentication of the User Identity.
+
+The 3GPP system shall support to perform authentication of a User Identity regardless of the user's access, the user's UE and its HPLMN as well as the provider of the User Identifier.
+
+The 3GPP system shall support user authentication with User Identifiers from devices that connect via the internet; the 3GPP system shall support secure provisioning of credentials to those devices to enable them to access the network and its services according to the 3GPP subscription that has been linked with the User Identity.
+
+**NOTE:** it is not clear whether these requirements only covers provisioning of devices that are already properly configured to have a working internet connection or not. For this use case the PIN Element may initially only be able to set up a direct device connection with the gateway UE for onboarding, but it may not have a fully working internet connection. Therefore, this requirement may require further clarification. It may also need to be clarified that the PIN Element may be a headless device.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+[PR 5.9.6-1] The 5G system shall support an authorized PIN Element to access the 5G network and its services via a PIN Element with Gateway Capability, via non-3GPP access when the PIN Element is associated to a 3GPP subscription and configured with credentials or via direct network connection when the PIN Element is a UE.
+
+[PR 5.9.6-2] The 3GPP system shall support secure provisioning of credentials to a device which User Identifier has been linked with the 3GPP subscription of the UE that acts as gateway, via that UE, to enable it to access the network and its services according to the linked subscription when connected via the internet
+
+**NOTE:** This requirement is expected to be added to Section 26a of TS 22.101.
+
+## 5.10 Personal health monitoring PIN Elements
+
+### 5.10.1 Description
+
+Personal health monitoring devices are becoming more readily available to consumers and may be used by doctors to provide remote monitoring of patients. Doctors may provide the devices to their patients and ask the patients to regularly upload measurements to the doctor's office.
+
+### 5.10.2 Pre-conditions
+
+The personal health monitoring devices are PIN Elements that are designed to provide patient data to the doctor's servers via the 5G network through a gateway UE. The devices belong to doctors and/or hospitals, who are the owners of the devices, and are configured to use both cellular access networks as well as wifi networks. The devices are configured by the doctor's office or hospital with credentials belonging to the doctor or hospital to enable communications over the cellular network. Since the devices may be re-used for different patients at different times, the credentials must be offboarded and onboarded properly to ensure the collected data is associated with the correct patient. The devices can also use PIN direct connection to communicate with other PIN Elements in the network.
+
+John has recently suffered from a heart attack and is recovering from treatments in a hospital. Before John is discharged, his cardiologist provides a heart rate monitoring device that he can use so the doctor can monitor his heart rate while doing light exercises at home. While at the hospital, the staff shows John how to associate the device with his smartphone so the device can send data to the doctor's office server through the smartphone using the cellular network. John needs to also participate in a cardiac rehabilitation program at a local clinic where nurses can monitor his heart rate when he participates in a medically supervised exercise program. He attends the clinic 3 days a week and for other days of the week, John is encouraged to exercise lightly at home. While at the clinic, the heart rate data is shared with the clinic, which is reported back to John's doctor. He uses the heart rate monitoring device provided by his doctor to record his heart rate while exercising at home and also when he is resting. However, John needs to be careful to maintain his heart rate within a safe range as to not overextend his heart and trigger another heart attack. To ensure the data can still be sent to the doctor's office in case there is an issue with John's smartphone, John also associate the device with his spouse's smartphone. This would provide redundancy for when John is walking outside.
+
+John also suffers from diabetes and his endocrinologist has provided him with a glucose monitoring device. The glucose monitoring device is a PIN Element that is configured with credentials belonging to his endocrinologist so that measurements from the device can be sent to the endocrinologist's servers via the 5G network. Similar to the heart rate
+
+monitoring device, credentials must be offboarded and onboarded to ensure the collected data is associated with the correct patient. John needs to measure his glucose levels before and after each meal and sometimes on-demand if requested by his endocrinologist or when John experiences unusual symptoms. John needs to maintain his blood sugar level above a certain level to avoid experiencing hypoglycemia symptoms such as dizziness, trembling, weakness, seizures, or even loss of consciousness.
+
+Since both the heart monitoring device and the glucose monitoring device may provide measurements that indicate a life-threatening situation, the devices are configured to provide redundant access to the 5G network to ensure John's doctors are notified in case the measurements are beyond safe levels. The devices are configured to be able to connect to multiple gateway UEs to provide concurrent access for the devices to send measurements to his doctors in case of emergency. The devices can connect to and send measurements through both John's smartphone and his spouse's smartphone in addition to connecting to and sending measurements through his home network.
+
+When John visits his daughter's house, he brings both the heart rate monitoring device and the glucose monitoring device so he can continue to provide measurements to both his doctors. The PIN Elements may communicate concurrently to the gateway UE at his daughter's house (if one is available) John's smartphone, and his daughter's smartphone if an emergency arises. Either way, the data traffic sent from each device is charged to the respective doctor's servers (PIN Elements).
+
+**NOTE:** The sensor measurements (heart rate, sugar levels etc) could be sent over multiple connections at the same time or the sensor is informed that connectivity is unavailable by one route and chooses an alternative route. The mechanism would be dependent on how life threatening the lack of communicating information is.
+
+### 5.10.3 Service Flows
+
+John brings the PIN Elements that were provided by his doctors to his home and connects them to his home network.
+
+- Each PIN Element connects to the home network and to other gateway UEs
+- A gateway UE allows the PINs within the home to connect to the 5G system
+- Each PIN Element sends data through the gateway UE and the 5G system to the corresponding doctor's servers
+- The 5G system is able to identify what PIN Elements sent each piece of data and generates charging records accordingly
+
+### 5.10.4 Post-conditions
+
+John's doctors are able to monitor his health remotely through the measurements provided by the PIN Elements.
+
+John doesn't need to see his doctors as often as he recovers and if his vitals show he is relatively in good health.
+
+The 5G system can correctly identify traffic sent by each PIN Element and generate the appropriate charging records.
+
+The 5G system can provide network access for PIN Elements in medical emergency situations.
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+From 3GPP TS 22.101 [3],
+
+The 3GPP system shall be able to provide User Identities with related User Identifiers for a user.
+
+The User Identifier may be provided by some entity within the operator's network or by a 3rd party.
+
+The 3GPP network shall be able to provide a User Identifier for a non-3GPP device that is connected to the network via a UE that acts as a gateway.
+
+From 3GPP TS 22.115 [7],
+
+The 3GPP system shall be able to create charging data containing the User Identifier and the subscription to which it is linked for access and use of network services by a non-3GPP device that was authorized with its User Identifier linked to a subscription.
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+[PR 5.10.6-1] A PIN Element may be a member of more than 1 PIN.
+
+[PR 5.10.6-2] A PIN Element shall be aware in case of loss of its connectivity to 5GS.
+
+[PR 5.10.6-3] The 5G system shall support a PIN Element to be configured with credentials of multiple user identities.
+
+[PR 5.10.6-4] The 5G system shall support access to the 5G network and its services for an authorized PIN Element (linked to a 3GPP subscription and provisioned with credentials) via one or more PIN Element with Gateway Capability.
+
+[PR 5.10.6-5] A PIN Element with Management Capability shall be able to assist a PIN Element that lost its connection to the 5G network in establishing a connection to another PIN Element with Gateway Capability.
+
+[PR 5.10.6-6] A PIN Element shall be able to discover PIN Elements with Gateway Capability and PIN Elements with Management Capability.
+
+## 5.11 Dynamic creation of an on-demand PIN at home
+
+### 5.11.1 Description
+
+Nowadays, most of the operators and smartphones provide a personal hotspot service, which allows the phone to become a WLAN hotspot that provides internet connections to other devices via the UE's mobile connections. But this only provides internet connectivity to those devices while the smartphone only acts as connection gateway. With the deployment of PIN and the support of the Mobile operators to use this as a new added value service, authorized mobile devices, such as smartphones, tablets, CPEs can be also used as a PIN gateway to dynamically create and manage an on-demand temporary PIN. This on-demand PIN will not only provides connectivity to the devices in the proximity, but also provides more flexibility and authority to the PIN-user to manage the PIN, such as to decide which devices to be connected into this PIN; to manage the service and the traffic within the PIN, so on.
+
+The PIN uses licensed spectrum as well as unlicensed spectrum, Therefore, the creation and management of this type of on-demand PIN requires the authorization and supervision from the PLMN that owns the license spectrum. The PLMN can offer this new on-demand PIN service in certain constrained locations for authorized users with authorized devices. Although the on-demand PIN is provided and controlled by the PLMN, the authorized user of the on-demand PIN can have certain flexibility to manage this PIN, such as to decide when to create and terminate the PIN, coordinate with PLMN to authorize the devices to be allowed to access this PIN, manage the services being allowed in this PIN, so on.
+
+### 5.11.2 Pre-conditions
+
+Tom is an avid game player and his local operator M offers a service where by the operator allows a customer to create on-demand PIN and download games to PIN element(s) with gateway and management functionality (e.g. 5G home access router as example in this use case, but it can also be a mobile phone so that the players can create a gaming session everywhere, e.g. at the school yard or in the park), the home access router is provided by operator M and supports device connectivity using a variety of access technologies (e.g. operator managed 3GPP RAT, WLAN, Bluetooth®). Collectively operator M calls this “PIN Functionality”
+
+NOTE: These variety of access technologies are supported as avid game players usually have a variety of new and old devices they want to use.
+
+The 5G home access router also stores games meta data that can be uploaded Operator's M network so that the game can be played later on other PIN element(s) or the same 5G home access router at different location.
+
+Today is the game night, Tom invites his friend Mike, James and Howard to his house to try the new air-combat video game that he just bought recently. The air-combat video game provider has partnership with the Operator M which hosts the game edge server in its network. Tom installed a local version of the game application in the 5G home access router.
+
+Mike, James and Howard bring their own wireless game consoles as well as wireless VR glasses. Mike, James's console and VR glasses are 5G capable of supporting 26GHz spectrum with the subscription of operator M. Howard has the subscription of Operator A for his 5G game console which also support WLAN and Bluetooth®. Howard also has a VR glass which can link to his 5G game console with PIN direct connection, such as Bluetooth®.
+
+### 5.11.3 Service Flows
+
+- 1 After his friends arrive, Tom turns on its PIN function in his 5G access router. This 5G router sends on-demand PIN creation authentication and authorization request to Operator M, for creating a PIN in this device for 4 hours in his house using mmWave spectrum owned by M. Per the subscription Tom bought, the maximum number of devices to be allowed in this PIN is 10, and tonight he only requires 8 devices. Because the on-demand PIN subscription which Tom bought is the basic and only allows local traffic, it means that guest devices in this PIN will not be able to access services outside the PIN. The PIN subscription also has other restrictions, such as the PIN only allowed operating in Tom's house and for maximum 10 hours for each time the PIN being created.
+
+NOTE: Basic+ is the same as Basic subscription but allows devices, if supported, to use operators managed spectrum. Tom upgraded tonight because in the past when Mike and others came over and they just used non 3GPP access technologies sometimes there was too much delay and parts of games became unplayable.
+
+- 2 After being authorized by M, this 5G home access router is reconfigured by PLMN remotely, which may include getting some necessary functions downloaded from M, to be able to act as PIN gateway.
+- 3 When the 5G home access router is ready, it starts to use and broadcast its own PIN network ID which can be assigned by M or named by Tom depended on the M's policy.
+- 4 Mike and James have connected to Tom's game night PIN before on other game nights, so their devices automatically discover and connect their 5G home access router and VR glasses to this PIN after being authenticated & authorized via Tom's 5G home access router. It's Howard first time to use the PIN, and since he has no subscription of M, he has to manually select and connect his game console to "game night" PIN using WLAN.
+- 5 An local game server is created and hosted in the 5G router after the PIN is up, so everyone's game consoles can be connected to that local game server for playing locally. Before coming to Tom's house, James played the game at his home and his game console was connected to the game server hosted in the PLMN's cloud. After being connected to "game night" PIN, James's connection with the game server is relocated to the local game service in the "game night" PIN. Within this PIN, Tom, Mike, James's game consoles and VR glasses can communicate with each other using direct device communication with the 26Ghz spectrum, while their consoles communicate with the local game server via Tom's 5G home access router. Howard's console can communicate with others' consoles and the local game server via the connection to Tom's 5G Home access router using WLAN.
+- 6 Tom's 5G home access router monitors and controls the communication of those devices in "game night" PIN based on the policy from M, also may coordinate with M for some necessary network managements, such as interference management.
+- 7 All the gaming content being exchanged between these players is conveyed locally, only the game status information can be conveyed back to the central game server in the cloud via the local game function in Tom's 5G home access router.
+- 8 Because the PIN is created for only 4 hours, the service and connections associated with PIN elements as well as operators 5GC are configured accordingly to the lifetime of the PIN, to avoid sudden service disruption when the PIN has ended after time life expires.
+- 9 Tom and Mike are one team to against the team of James and Howard in the game. Tom and Mike establish an encrypted communication between their game consoles to exchanges some private information (e.g. screen shots, game maps, private chat, voice etc), while another secured communication between James and Howard's devices is also created.
+
+### 5.11.4 Post-conditions
+
+Tom, Mike, James and Howard happily play the game in Tom's house for 3 hours. After 3 hours, they are so into the game and don't want to finish in 1 hour and decide to extend the game night for 3 more hours. So, Tom sends the PIN modification request to M to extend the PIN for 3 more hour and is approved. When 7 hour PIN life time expires, all the game consoles and VR glasses have been disconnected from the PIN as well as the game service, then the "game night" PIN is terminated. 5G access route sends the charging information for this 7-hour operation of PIN.
+
+### 5.11.5 Existing features partly or fully covering the use case functionality
+
+### 5.11.6 Potential New Requirements needed to support the use case
+
+[PR.5.11.6-1] 5G system shall be able to support creation / termination / modification of an PIN in certain location for a requested period of time (e.g., hours) with the authorization from the operator based on the subscription of the PIN-User.
+
+[PR-5.11.6-2] 5G system shall be able to allow authorized PIN Elements automatically or manually to discover other PIN element(s) for communication.
+
+[PR-5.11.6-3] 5G system shall be able to support authentication and authorization of PIN elements whose subscriptions can belong to different operators to access the PIN.
+
+[PR-5.11.6-4] 5G system shall be able to support secured communications between two or more individual PIN elements within a PIN.
+
+[PR-5.11.6-5] 5G system shall be able to support mechanism to provide life span information of the PIN to an authorized party and/or the PIN elements when the PIN is created for limited time span.
+
+[PR-5.11.6-6] 5G system shall be able to support an authorized party to set policies on which PIN Elements can access which services or PIN elements in an PIN.
+
+[PR-5.11.6-7] 5G system shall be able to support an authorized party to set policies duration of access, IP connectivity type (local break out 5GC etc) local services etc.
+
+## 5.12 Operator managed PIN
+
+### 5.12.1 Description
+
+This use case describes the required support from operator to manage PIN Elements including IoT devices or non-3GPP devices in a PIN, in a home or in an office.
+
+### 5.12.2 Pre-conditions
+
+Bob has a mobile subscription with MNOa.
+
+Bob has a smart home network using a gateway (i.e. a PIN Element with Gateway Capability) that is provided and managed by MNOa.
+
+Bob's smart home network supports several wireless technologies, including 3GPP direct device connection, WLAN, Bluetooth®, wireline, etc.
+
+The 5G network of MNOa has a list (also referred to as a collection or group) of PIN Elements in Bob's smart home network, which can be managed by the 5G network. This list is called the list of *managed* PIN Elements. This list contains information for each PIN Element, such as an identity, connectivity capabilities, credentials, communication restrictions (e.g. other PIN Elements it cannot communicate with), etc.
+
+### 5.12.3 Service Flows
+
+Step1: Bob buys a new PIN Element, e.g. a smart plug with WLAN capability.
+
+Step2: Bob connects this PIN Element to the WLAN of his smart home network and the PIN Element obtains an IP address.
+
+Step3: The 5G network of MNOa detects that a new PIN Element is connected to Bob's PIN.
+
+Step4: The 5G network acting as an Identity provider creates a User Identity and User Profile for the PIN Element based on UIA Framework in 3GPP TS 22.101 [3].
+
+Step5: The 5G network of MNOa sends a notification to Bob's UE (a member of the PIN) requesting permission to add this device to the list of managed PIN Elements of his PIN.
+
+Step6: Bob grants permission and the 5G network of MNOa adds the PIN Element to the list of "managed" PIN Elements.
+
+### 5.12.4 Post-conditions
+
+Bob is now able to monitor and control the PIN element (and any other PIN element in the list of "managed" PIN Elements), e.g. by using a web application provided by MNOa.
+
+### 5.12.5 Existing features partly or fully covering the use case functionality
+
+The service requirements in 3GPP TS 22.101 [3] clause 26a provide the principle for user centric identifiers and authentication by the 3GPP system:
+
+- The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services.
+
+This use case and requirements consider that the application running on the PIN Element is a non-operator deployed (i.e. external non-3GPP) services behind a PIN Element with Gateway Capability in PIN.
+
+### 5.12.6 Potential New Requirements needed to support the use case
+
+[PR 5.12.6-1] The 5G system shall support a mechanism for a network operator or an authorized party to create a PIN and manage the PIN Elements for the PIN.
+
+## 5.13 A smart hospital bed as a PIN element
+
+### 5.13.1 Description
+
+Hummel is a 70-year-old cardiac patient who is equipped with a pacemaker at the TeleCare hospital, who have their own 5G network. During the recent remote intervention, the doctors decided that he must admit himself for a surgery to replace the batteries of his pacemaker. In order to monitor the health of his heart continuously, Hummel has received a 5G enabled wearable heart monitor from another hospital, which is capable of continuously monitoring the vitals including the heart rate and send its data via a 5G network to a cloud server. He also has other personal connected health devices such as an SpO2 monitor and a connected insulin pump attached to his body that are wirelessly connected to his mobile phone for complete overview of his health. He also has a special sleep mask enabling him to breathe better during his sleep and monitor the quality of his sleep that is also connected to his mobile phone when he is using it. It is assumed that all his health devices are clinically qualified to be used for diagnosis in a hospital.
+
+Upon arriving at the hospital reception, Hummel is immediately directed to the cardiology department, where a 5G enabled smart hospital bed is allocated for him. The smart hospital bed is configured as a PIN element with gateway capability and with management capability. The smart hospital bed enables personal devices of the patient to be connected to the 5G network of the hospital. It also allows some of the PIN elements connected to the hospital bed, such as some controls over the elevation of the head of the bed and a personal screen connected to the bed (e.g. to watch TV or to stream some video content to watch). The hospital bed is also connected to a high-end patient monitor, located behind the patient. Although it cannot be controlled by the patient, the output of the monitor can be displayed and browsed by the patient on his mobile phone or the attached personal screen.
+
+Upon reaching the smart hospital bed, the devices that are carried and worn by Hummel and the hospital bed (with its connected PIN elements) can discover each other, and together form a PIN. Via the smart hospital bed, the necessary credentials to securely communicate with each other, and to connect to the hospital 5G network are downloaded and configured in Hummel's devices. The data from Hummel's health devices can now be sent to the TeleCare's 5G network, where it can be processed and used for health monitoring by the hospital staff. The high-end patient monitor linked to the smart hospital bed can receive the data from Hummel's devices directly from the devices and generate an alarm if Hummel's condition deteriorates. Using the PIN, Hummel can also control the elevation of his bed via his mobile phone and stream some videos from his mobile phone on the screen connected to the bed, and browse the output of the patient monitor.
+
+### 5.13.2 Pre-conditions
+
+Hummel has a 5G PIN enabled mobile phone (i.e. a UE), with several personal health devices wirelessly connected to it. The mobile phone may be a PIN element with gateway capability and/or management capability.
+
+Hummel also has a 5G PIN enabled wearable heart monitor capable of sending its data via a 5G network to a cloud server.
+
+The hospital bed is 5G PIN enabled UE and is a PIN element with gateway capability and/or management capability. For its management capability it may use the attached screen to display a user interface to the user.
+
+TeleCare may function as an NPN, preventing full access to the network services for unregistered devices. TeleCare may deploy not only a single NPN, but may deploy multiple NPNs, e.g. one for staff (with full access to the network services) and one for patients (with limited access to the network services).
+
+### 5.13.3 Service Flows
+
+- Upon entering the cardiology department inpatient room, Hummel's mobile phone and the smart hospital bed can discover each other. Also the 5G PIN enabled wearable heart monitor and the smart hospital bed can discover each other.
+- When Hummel looks at his mobile phone, he notices that it has discovered the smart hospital bed. It also shows the list of connected PIN elements connected to the hospital bed.
+- Hummel can connect his mobile phone to the smart hospital bed and upon connecting, Hummel's mobile phone gets added to the hospital's bed PIN. Also the personal devices that are connected to Hummel's mobile phone can be discovered by the hospital bed and added to the hospital bed's PIN. Hummel can decide which personal devices can be discovered and added to the hospital bed's PIN. Similarly, the IT department of the hospital can decide which devices of the hospital bed's PIN can be discovered by Hummel's mobile phone and/or other UEs outside the PIN.
+- On the screen of the mobile phone (or the screen attached to the hospital bed), it also shows that the 5G PIN enabled wearable heart monitor in the list of discovered PIN elements. Hummel presses a button to also add that device to the hospital bed's PIN.
+- After exchange of credentials, the PIN elements can now securely communicate between each other. This allows Hummel to use the screen attached to the bed for streaming some videos from his mobile phone, allows the data from his heart monitor to be received by the high-end patient monitor, and show the patient monitor's data on his mobile phone.
+- As part of the PIN configuration, the PIN elements are also allowed to gain patient access to the hospital network (via the hospital bed's PIN gateway capability). On the screen of his mobile phone (or the screen attached to the hospital bed), Hummel allows his wearable heart monitor and his other connected health devices to send their data to the hospital network.
+- The data from the connected devices are useful in improving the pre-surgical preparation of Hummel and saves operational overhead for the hospital staffs.
+- Thanks to the PIN feature, Hummel had an easy transfer to the hospital and had a fairly comfortable experience (despite his condition) in his smart hospital bed.
+
+### 5.13.4 Post-conditions
+
+Upon discharge, the network profiles from his mobile phone, his heart monitor and his personal connected health devices are decommissioned from the PIN and from the hospital network and return to their original operating state.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+**Editor's note: TBD**
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+[PR 5.13.6-1] The 5G system shall enable PIN elements to discover and identify each other.
+
+NOTE 1: This may be done directly (depending on the discovery capabilities of the PIN elements) or via a PIN element with gateway capability or via a PIN with management capability.
+
+[PR 5.13.6-2] The 5G system shall enable PIN elements with management capability to add PIN elements to the PIN.
+
+[PR 5.13.6-3] The 5G system shall allow only authorized PIN elements to connect to the 5G network via a PIN element with gateway capability.
+
+NOTE 2: Next to authorization of the 5G network operator, additional authorization/consent from the PIN user may be needed depending on whether the user wants to allow PIN elements to connect to the 5G network or not.
+
+[PR 5.13.6-4] The 5G system shall support a mechanism for the PIN user to indicate whether a PIN element is discoverable by other PIN elements of the same PIN.
+
+[PR 5.13.6-5] The 5G system shall support a mechanism for the PIN user to indicate whether a PIN element is discoverable by UEs that are not members of the PIN.
+
+[PR 5.13.6-7] The 5G system shall support a mechanism to enable the user of a UE or a device that is not a member of the PIN to request PIN membership.
+
+# 6 Considerations
+
+A lot of the use cases in this document are based on existing systems (e.g. ZigBee® Specification [9], Z-Wave ® [10]) that can be deployed today, in fact the overview identifies two main Personal IoT Networks, wearables and home automation. These existing Personal IoT Networks use a number of different technologies that provide a set of capabilities.
+
+# 7 Potential Consolidated Requirements
+
+This section provides Consolidated Potential Requirements for consideration to include in the normative specifications. The CPR's have been grouped into different functional categories, each category contains a table that lists the original PR and any relationship to 3GPP TR 22.858 [6].
+
+## 7.0 PIN Element Requirements
+
+**Table 7.0-1 – PIN Element Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|---------|
+| CPR 7.0-1 | The 5G System shall support mechanisms to identify a PIN and a PIN Element. | PR.5.1.5-11 | |
+| CPR 7.0-2 | The 5G system shall allow PIN Elements to communicate when there is no connectivity between a PIN Element with Gateway Capability and a 5G network. For a Public Safety PIN licensed spectrum may be used for PIN direct communications otherwise unlicensed spectrum shall be used.
Editors note: This requirement is FFS. | PR.5.1.5-7 | |
+| CPR 7.0-3 | The 5G system shall support a mechanism for a PIN Element to be member of more than one PIN. | PR 5.2.6-1,
PR 5.7.6-1,
PR 5.10.6-1, | |
+| CPR 7.0-4 | The 5G system shall support a PIN Element that can:
- simultaneously unicast to multiple PIN Elements within a PIN; and
- multicast to multiple PIN elements within a PIN.
NOTE: The above assumes PIN direct connection is used. | PR 5.3.6-1 | |
+
+## 7.1 Gateway
+
+**Table 7.1-1 – PIN Gateway Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|---------|
+| CPR 7.1-1 | A PIN shall include at least one PIN Element with Gateway Capability. | PR 5.3.6-3 | |
+| CPR 7.1-2 | The 5G system shall support access to the 5G network and its services for an authorized PIN Element (linked to a 3GPP subscription and provisioned with credentials) via one or more PIN Elements with gateway capability or directly via non-3GPP access. | PR 5.9.6-1,
PR 5.10.6-4 | |
+| CPR 7.1-3 | The 5G system shall allow only authorized PIN elements to connect to the 5G network via a PIN element with gateway capability.
NOTE: Next to authorization of the 5G network operator, additional authorization/consent from the PIN user may be needed depending on whether the user wants to allow PIN elements to connect to the 5G network or not. | PR 5.13.6-3 | |
+
+## 7.2 Device and Service Discovery
+
+**Table 7.2-1– PIN Device and Service Discovery Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|---------|
+| CPR 7.2-1 | The 5G system shall enable a PIN Element in a PIN to discover other PIN Elements within the same PIN subject to access rights. | | |
+| CPR 7.2-2 | The 5G system shall efficiently support service discovery mechanisms where PIN Elements can discover, subject to access rights: - - availability and reachability of other PIN Elements (e.g. whether a PEGC has external data network connectivity);
- - capabilities of other PIN Elements (e.g. PEMC, PEGC, connection types) and/or;
- - services provided by other PIN Elements (e.g. the PIN Element is an AR/VR headset).
| PR 5.1.5-10, PR 5.6.6-1,
PR 5.8.6-1,
PR 5.8.6-2
PR 5.10.6-2,
PR 5.10.6-6,
PR 5.11.6-2 | |
+| CPR 7.2-3 | The 5G system shall support a mechanism for a PIN Element to select a relay for PIN direct connection that enables access to the target PIN Element. | PR 5.10.6-5 | |
+| CPR 7.2-4 | The 5G system shall support a mechanism for the PIN user to indicate whether a PIN element is discoverable by other PIN elements of the same PIN. | PR 5.13.6-4 | |
+| CPR 7.2-5 | The 5G system shall support a mechanism for the PIN user to indicate whether a PIN element is discoverable by UEs that are not members of the PIN. | PR 5.13.6-5 | |
+
+## 7.3 Application Servers
+
+**Table 7.3-1 – PIN Application Servers Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| None | NOTE: The PRs 5.6.6-1, 5.6.6-2, 5.6.6-3, 5.6.6-4 are integrated with other potential requirements, on aspects related to discovery of, and connectivity to, application/services on PIN elements. Whether service hosting within PIN requires additional requirements will be determined during the normative work. | None | |
+
+## 7.4 Privacy and Security
+
+**Table 7.4-1 – PIN Privacy Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|---------|
+| CPR 7.4-1 | The 5G system shall be able to provide secure communications between two or more PIN Elements in a PIN. | PR 5.6.6-4,
PR 5.7.6-7,
PR 5.11.6-4,
PR 5.5.6-1 | |
+| CPR 7.4-2 | The 5G system shall support a mechanism to mitigate repeated and unauthorized attempts to access PIN Elements (e.g. mitigate a malicious flood of messages). | PR 5.8.6-3,
PR 5.8.6-4 | |
+| CPR 7.4-3 | The 5G system shall support a PIN Element using non-operator managed credentials (e.g. provided by a third party) for performing communications within the PIN when those communications use PIN direct connections. | PR 5.1.5-6 | |
+| None | NOTE: These requirements (PR 5.10.6-3, PR 5.5.6-2) will be considered in descriptive text in the normative phase. | PR 5.10.6-3,
PR 5.5.6-2 | |
+| CPR 7.4-4 | The 5G system shall be able to support PINs with PIN Elements subscribed to more than 1 network operator. | PR 5.11.6-3 | |
+
+## 7.5 Direct Communications
+
+**Table 7.5-1 – PIN Direct Communications Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------|
+| CPR 7.5-1 | The 5G system shall support mechanisms to provision a PIN Element to use either licensed (under control of a MNO) or unlicensed spectrum (may be under the control of the MNO, or not) (e.g., when it has no connectivity to the 5G system). | PR 5.2.6-3,
PR 5.7.6-3,
PR 5.1.5-4 | |
+| CPR 7.5-2 | The 5G system shall support mechanisms to aggregate, switch or split the service between non-3GPP RAT and PIN direct connections using licensed spectrum. | PR 5.4.6-1 | |
+| CPR 7.5-3 | The 5G system shall be able to support concurrent use of both licenced spectrum and non-licensed spectrum PIN direct connectivity between PIN Elements. | PR 5.7.6-5 | |
+| CPR 7.5-4 | The 5G system shall be able to minimize service disruption when a PIN Element changes the communication path from one PIN Element to another PIN Element. The communication path between PIN devices may include both licensed and unlicensed spectrum 3GPP and non-3GPP access. | PR 5.3.6-2 | |
+
+## 7.6 Connectivity - QoS - charging
+
+**Table 7.6-1 – PIN Connectivity, QoS and Charging Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------|
+| CPR 7.6-1 | The 5G system shall support a mechanism to manage QoS for communications between PIN Elements when supported by the radio access technology. | PR 5.6.6-2,
PR 5.6.6-3 | |
+
+## 7.7 PIN Management
+
+**Table 7.7-1 – PIN Provisioning Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------|
+| CPR 7.7-1 | A PIN shall include at least one PIN Element with Management Capability | PR.5.1.5-8,
PR.5.1.5-9 | |
+| CPR 7.7-2 | The 5G system shall support mechanisms for a PIN User, network operator or authorized 3rd party to create and manage a PIN, including:
- - Authorizing/deauthorizing PIN Elements;
- - Authorizing/deauthorizing PIN Elements with Management Capability;
- - Authorizing/deauthorizing PIN Elements with Gateway Capability;
- - Establishing duration of the PIN;
- - Configure PIN Elements to enable service discovery of other PIN Elements;
- - Authorize/deauthorise if a PIN Element can use a PEGC to communicate with the 5GS;
- - Authorize/deauthorise for a PIN Element(s):
- - which other PIN Element it can communicate with,
- - which applications/service or service in that PIN it can access'
- - which PIN Element it can use as a relay.
- - Authorize/deauthorise a UE to perform service discovery of PIN Elements over the 5G network;
- - Configure a PIN Element for external connectivity e.g. via 5G system;
NOTE: The authorization can include the consideration of the location and time validity of the PIN and its PIN elements.
| PR 5.1.5-1,
PR 5.2.6-2,
PR 5.7.6-2,
PR 5.13.6-2,
PR 5.8.6-1a,
PR 5.11.6-1
PR 5.11.6-6,
PR 5.11.6-7,
PR 5.12.6-1 | |
+| CPR 7.7-3 | The 5G system shall support mechanisms for a network operator to configure the following policies in a PIN:
- - Configure the connectivity type (e.g. licensed or unlicensed PIN direct connection) a PIN Element can use.
| | |
+| CPR 7.7-4 | 5G system shall be able to support mechanism to provide life span information of the PIN to the authorized 3rd party or the PIN elements when the PIN is created for limited time span | PR-5.11.6-5 | |
+| CPR 7.7-5 | The 5G system shall support a mechanism to enable a UE or a non-3GPP device that is not a PIN element of the PIN to request to join the PIN. | PR 5.13.6-7 | |
+
+## 7.8 Void
+
+## 7.9 KPIs
+
+Editor's note: KPI still need to be completed at SA1#95e, this section will be updated then.
+
+## 7.10 Charging
+
+**Table 7.8A-1 – Charging Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---------|
+| CPR 7.10-1 | The 5G system shall support mechanisms to collect charging information on PIN Element communications (e.g., start and stop of communications, amount of data transmitted, radio resources used, PIN identification) when 3GPP access is used. | PR.5.1.5-5,
PR 5.4.6-2 | |
+
+# --- 8 Conclusions and Recommendations
+
+This document analyses a number of use cases related to Personal IoT Networks, the resulting potential requirements have been consolidated in clause 7. In addition, when the use cases were being written for this TR some overlap was seen with use cases TR 22.858 [6].
+
+It is recommended that the consolidated potential requirements identified in this TR and TR 22.858 [6] are considered together as the basis of normative requirements.
+
+# Annex A Connectivity models
+
+## A.1 General
+
+This annex provides a diagrammatic view of the types of connectivity models that are supported in a PIN. Each diagram will contain 2 types of lines, one that shows a PIN Element to PIN Element transport and a second line that shows the end to end communication. In both diagrams PIN Elements use PIN direct connections, however PIN Element to PIN Element end to end communication may require a relay.
+
+A PIN Element may support more than one form of connectivity but this is not shown in the diagrams.
+
+## A.2 PIN direct connectivity with no relay
+
+
+
+**Home Automation
+PIN**
+
+— Non 3GPP communication
+— Licensed spectrum 3GPP Direct device connection
+— Non licensed spectrum 3GPP Direct device connection
+— End to End communication
+
+Diagram titled 'Home Automation PIN' showing various PIN elements and their direct connections. A door sensor connects to a smart light via non-3GPP (blue) and end-to-end (purple) lines. A motion sensor connects to the same smart light via licensed spectrum 3GPP (red) and end-to-end (purple) lines. A door handle connects to a key via non-licensed spectrum 3GPP (green) and end-to-end (purple) lines. A smart plug connects to a smartphone via non-licensed spectrum 3GPP (red) and end-to-end (purple) lines. A legend at the bottom defines the line types: blue for Non 3GPP communication, red for Licensed spectrum 3GPP Direct device connection, green for Non licensed spectrum 3GPP Direct device connection, and purple for End to End communication.
+
+**Figure A2-1: Examples PIN direct connectivity in a PIN**
+
+Figure A2-1 shows PIN Elements that communicate directly, without any relay elements to another PIN Element, this is collectively known as PIN direct connection. PIN direct connection can encompass different types of direct connection as show in Figure A2-1:
+
+- Door sensor (a device PIN Element) uses PIN direct connection (e.g. WLAN) to communicate with a light bulb (e.g. door opens and the light turns on).
+- Motion sensor (UE PIN Element) uses PIN direct connection in licensed spectrum to communicate with the light bulb (e.g. motion is detected in the room and the light bulb turns on).
+
+- NOTE PIN direct connection in 3GPP licensed spectrum is direct device connection as defined in TS 22.261 [2].
+- c) The key uses PIN direct connection in non licensed spectrum to communicate with the door lock (e.g. key opens the door).
+ - d) The smart plug (UE PIN Element) uses PIN direct connection in licensed spectrum to communicate with the smartphone (e.g. notification that it is using 60 watts of energy).
+
+## A.3 PIN direct connection using a relay.
+
+
+
+The diagram, titled "Home Automation PIN", illustrates two examples of PIN direct connections using relays. In the top example, a Door sensor and a Motion Sensor are shown. The Door sensor uses Non 3GPP communication (blue line) to a Relay (Smart Plug), which then uses End to End communication (purple line) to a PIN Element with management capability. The Motion Sensor uses Licensed spectrum 3GPP Direct device connection (red line) to a Relay (Smart Light), which then uses End to End communication (purple line) to the same PIN Element. In the bottom example, a Door lock uses Non 3GPP communication (blue line) to a Smart Plug Relay, which then uses End to End communication (purple line) to a Smartphone. The Smart Plug Relay also uses Licensed spectrum 3GPP Direct device connection (red line) to the Smartphone. The legend identifies four communication types: Non 3GPP communication (blue line), Licensed spectrum 3GPP Direct device connection (red line), Non licensed spectrum 3GPP Direct device connection (green line), and End to End communication (purple line).
+
+Diagram illustrating PIN direct connection using a relay in a Home Automation PIN environment. The diagram shows various devices (Door sensor, Motion Sensor, Smart Light, Smart Plug, PIN Element with management capability, Smartphone) connected via relays (Relay, Smart Plug Relay). The legend defines four types of communication: Non 3GPP communication (blue line), Licensed spectrum 3GPP Direct device connection (red line), Non licensed spectrum 3GPP Direct device connection (green line), and End to End communication (purple line).
+
+**Figure A3-1: Examples PIN direct connection using a relay in a PIN**
+
+Figure A3-1 shows PIN Elements that communicate directly but there is a relay in the communication path. Figure A3-1 shows the following:
+
+- a) Door sensor (device PIN Element) uses PIN direct connection (Non 3GPP communication) to communicate with a PIN Element with management capability via 2 relays (light bulb and smart switch).
+- b) Motion sensor (UE PIN Element) uses PIN direct connection in licensed spectrum to communicate with the a PIN Element with management capability via a relays (light bulb) (e.g. to configure the motion sensor to turn the light bulb on or off).
+- c) The door lock (UE PIN Element) uses PIN direct connection in licensed spectrum to communicate with the smartphone (e.g. notification that it opened) via a relay (smart socket).
+
+# Annex B: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-08 | SA1#91e | S1-203283 | | | | TR Skeleton | 0.0.0 |
+| 2020-09 | SA1#91e | S1-203390 | | | | Incorporated the following PCRs into TR:
S1-203422, S1-203418, S1-203419, S1-203420, S1-203371, S1-203421 | 0.1.0 |
+| 2020-11 | SA1#92e | S1-204360 | | | | Incorporated the following PCRs into TR:
S1-204443, S1-204334, S1-204331, S1-204333, S1-204438, S1-204439, S1-204063, S1-204440, S1-204445, S1-204441, S1-204444, S1-204442, S1-204332, S1-204066 | 0.2.0 |
+| 2021-03 | SA1#93e | S1-210314 | | | | Incorporated the following PCRs into TR:
S1-210486, S1-210487, S1-210488, S1-210489, S1-210490, S1-210491, S1-210492, S1-210493, S1-210494, S1-210495, S1-210496, S1-210497 | 0.3.0 |
+| 2021-03 | SA#91e | SP-210208 | | | | Presented for information, MCC clean-up | 1.0.0 |
+| 2021-05 | SA1#94e | S1-211309 | | | | S1-211457, S1-211458, S1-211459, S1-211460, S1-211461, S1-211469, S1-211092, S1-211508, S1-211464, S1-211157, S1-211158, S1-211465, S1-211467, S1-211468, S1-211466 | 1.1.0 |
+| 2021-06 | SA#92e | SP-210513 | | | | Raised to v.2.0.0 by MCC for SA approval | 2.0.0 |
+| 2021-06 | SA#92e | SP-210513 | | | | Raised to v.18.0.0 by MCC following SA approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210513 | | | | Corrected logo (5G->5GA) | 18.0.1 |
+| 2021-09 | SA#93e | SP-211098 | 0001 | 1 | B | Requirements on PIN element discovery restriction | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0001 | 3 | B | Requirements on PIN element discovery restriction | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0002 | 1 | F | PIN Element definition update and abbreviations added | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0003 | 1 | B | Use case 5.4 & 5.7: Update existing requirements section | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0004 | | B | Conclusions | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0005 | 1 | B | Requirements consolidation - part 1 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0007 | 1 | B | Clarification for potential requirements of UCs 5.3, 5.9 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0008 | | D | Editorials | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0009 | 1 | C | Addition of potential requirements on PIN and PIN Element identity and discovery of PIN Element identity | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0012 | 1 | B | Providing credentials via gateway UE | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0013 | 1 | F | Clarifying subscription aspects | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0017 | 1 | B | Addition of consolidated requirements for use case on PIN element discovery restriction | 18.1.0 |
+| 2021-09 | SA#93e | SP-211098 | 0018 | 1 | B | UE requesting to be added to a PIN | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0019 | 1 | F | Format Corrections on Consolidated Potential requirements | 18.2.0 |
+| 2021-12 | SP-94 | SP-211496 | 0020 | 1 | F | Adding leftover PIN requirement to consolidated requirements | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22867/014daefdecf9d847ca82cb5b9f50731f_img.jpg b/marked/Rel-18/22_series/22867/014daefdecf9d847ca82cb5b9f50731f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92f60e058a6dcba4124cdfc2001e84630251ad3b
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/014daefdecf9d847ca82cb5b9f50731f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5af12a0b4977b3e94c3c917dd0219ac34265246c69db31e77307071943133177
+size 14647
diff --git a/marked/Rel-18/22_series/22867/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/Rel-18/22_series/22867/08f6ace0c83e7394657fa372b47aec04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..971748f616624fea29656540b1c9826eb6e0f032
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/08f6ace0c83e7394657fa372b47aec04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da5becb72bace4781985e40f246b532a331ad3fe03ef7a906158655f051a2c80
+size 85745
diff --git a/marked/Rel-18/22_series/22867/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Rel-18/22_series/22867/0997dbaa9dfecedd60029d70b53327b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e95f78182bf75bc2d840ef54016e52460cb22035
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/0997dbaa9dfecedd60029d70b53327b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9c4a4c7fe2f26cde86c24c2adba350ae285ca63b2f8297319393affafa4707f
+size 27244
diff --git a/marked/Rel-18/22_series/22867/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg b/marked/Rel-18/22_series/22867/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38c2f04a31f2ef2eea6581b7e35c970e5f7ed39e
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/0af1ba85ab6e4e50befbef3d63e017dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91cfa59553fb192a8a0df9a8ba80fe909d4f40a5496bf99b057aad25472f3014
+size 71488
diff --git a/marked/Rel-18/22_series/22867/29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg b/marked/Rel-18/22_series/22867/29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f268e73ff1b1924029540800e526fc34d2e9a636
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86b99551024840f561c68fedb5d2d28b08bc79be42fc8fef9b52172d17ce82ed
+size 98613
diff --git a/marked/Rel-18/22_series/22867/30a26f2d17ca95672702bf50fb4f0242_img.jpg b/marked/Rel-18/22_series/22867/30a26f2d17ca95672702bf50fb4f0242_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0779a7b4828bd38108c59a30e9be071e7b77cf69
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/30a26f2d17ca95672702bf50fb4f0242_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:510ac974993fc9e768c91927e18e462a1004714c6b69d79dec9683e561dd5a8c
+size 5663
diff --git a/marked/Rel-18/22_series/22867/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/Rel-18/22_series/22867/365b54f616aff249b4e6c0edafdcb9b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12b499b402d9fb56921be04a122bbbc8de19f06f
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/365b54f616aff249b4e6c0edafdcb9b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:195c3dab3ef7868f123337a29ceccccbfc103b556e0a123fcd16570bc130a42a
+size 81757
diff --git a/marked/Rel-18/22_series/22867/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/Rel-18/22_series/22867/399a5af4f606059626c92c92279d54b7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..318b8e4a8fa90a7c9354abbb175b4ad9e2376e7d
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/399a5af4f606059626c92c92279d54b7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca14a7c1ddafeb309cf9a8aa91647942d1afff1890d36fde2ac4951895f325aa
+size 50258
diff --git a/marked/Rel-18/22_series/22867/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/marked/Rel-18/22_series/22867/3ce04f1c7128814978c6b34d654a25cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b64b5e2dda624975f7e8f091d57ef06ead9e2a9b
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/3ce04f1c7128814978c6b34d654a25cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3730da979976a797c49ba57d6c6336c6969633e4784ace7a1b5ba6458b1e2811
+size 37674
diff --git a/marked/Rel-18/22_series/22867/4390b89fdb95cba102ee1f88e218b07b_img.jpg b/marked/Rel-18/22_series/22867/4390b89fdb95cba102ee1f88e218b07b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c196e8140d7f9cecc25df3e3c79dde201a74adf
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/4390b89fdb95cba102ee1f88e218b07b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5be2f5fbc1121af27536c7fddbfd4e96a37068017b11336777b875bec47bb4a8
+size 16460
diff --git a/marked/Rel-18/22_series/22867/4ae4505e885586e481a3ad3bff5198b7_img.jpg b/marked/Rel-18/22_series/22867/4ae4505e885586e481a3ad3bff5198b7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fab19d76868429109ebc8acc96e516af064da6e
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/4ae4505e885586e481a3ad3bff5198b7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03240cd69449369b666f9b0e6b26fdb82ccd1c2b4a1821c24bf0ea88fd706345
+size 111338
diff --git a/marked/Rel-18/22_series/22867/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/Rel-18/22_series/22867/5a1abd59a95fa47ae192807de151e9eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48ac8ed9c1254edb6bf0dddc22988420d10d8328
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/5a1abd59a95fa47ae192807de151e9eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c528512dfd1b04d6d3f154238c0e9c31744009a2f17216444f76b2df5ad68044
+size 42267
diff --git a/marked/Rel-18/22_series/22867/5db6545aedab79741ebae9b27bb363b3_img.jpg b/marked/Rel-18/22_series/22867/5db6545aedab79741ebae9b27bb363b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8e41007617ef57991859c3bee867eb874b3a71f
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/5db6545aedab79741ebae9b27bb363b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2afa567a62db02f47bd340c66566eb34551cb6b2ccb3868536db037b05d5fcd
+size 40357
diff --git a/marked/Rel-18/22_series/22867/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22867/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89bdead0a31aac223baf25796d316572efb642a4
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2ea64307b7c50c68900136af635fb2765a45a05e24d5ca1b2b4955feb31f7722
+size 9539
diff --git a/marked/Rel-18/22_series/22867/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-18/22_series/22867/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3ae40418a57de7326ca1fdc508a3c80b5eb6fa2
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cdddc0503ff8f1ffa64ea6d24c5e2dc4d25419206f652e860552c453d0b0c1d
+size 44899
diff --git a/marked/Rel-18/22_series/22867/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/Rel-18/22_series/22867/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30f93b3ab13e8e883c990a2a3eb16d204d23e507
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/7f25db95ce3916c0e09803b861a2f7bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:463ab1e6f16b00c48cd67876a0ecd9b2151c0cbed4977be2575b87dbdf8120c5
+size 23985
diff --git a/marked/Rel-18/22_series/22867/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg b/marked/Rel-18/22_series/22867/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddb94162511918d3933f46e75644d0faa75d24e1
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:186d9eeb80648deb9bea5b9795dbd694dada469c464d015dadfb0254fb13a059
+size 40761
diff --git a/marked/Rel-18/22_series/22867/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-18/22_series/22867/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..028c9c27e0a1ddd081670a08462057a445ab1924
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0694ac591a97b18a5850d452ac3fb72ca6106b1225f0d8e171d8dec7d1a8c8e
+size 54494
diff --git a/marked/Rel-18/22_series/22867/a057800564be3506d2d87b6a4daee25b_img.jpg b/marked/Rel-18/22_series/22867/a057800564be3506d2d87b6a4daee25b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b59f5b415a504ab5a579323ed12f7ca8862dac2e
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/a057800564be3506d2d87b6a4daee25b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:078b5dbe15c936d46858fab4b338f9107a0117a52285e3de52efaa35f8bb62c8
+size 33164
diff --git a/marked/Rel-18/22_series/22867/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-18/22_series/22867/adc59ed6840bcb2d392ea323abfccedc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7c8abc106e4a2bb4ab503d26a70ee96c7cd8530
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/adc59ed6840bcb2d392ea323abfccedc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4446af23a1abfc5d81e937875a55f77976790ee9e6520f364e38643be096ce3
+size 19456
diff --git a/marked/Rel-18/22_series/22867/b5b908b453ca50ed3b4cca88aef080fa_img.jpg b/marked/Rel-18/22_series/22867/b5b908b453ca50ed3b4cca88aef080fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c188b3f42f7ef7f04f036e15c3646152624d508d
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/b5b908b453ca50ed3b4cca88aef080fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:742de3336677488059c980d49fdb95da3f42a7f66c79d00803dfa574260ead35
+size 63362
diff --git a/marked/Rel-18/22_series/22867/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/Rel-18/22_series/22867/b9c0d46c1148cf65cb79f27fac420981_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29e502a99d3a7a25e241091ef48dd99c9ca572c0
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/b9c0d46c1148cf65cb79f27fac420981_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df66c7a6eed96a4b4dada2a721d256055f83eac98662eadedbc1c6175ae3a6ea
+size 42876
diff --git a/marked/Rel-18/22_series/22867/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg b/marked/Rel-18/22_series/22867/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b77f78aabf1bd102f12fd689433b2e68d644cbdc
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/dbfe5a97dc7e71fd9ae813d4bb865e29_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39d2646060ea93241c5ff5cb42fdb7266866821f5d6839f0c8b1db4427c1791f
+size 53286
diff --git a/marked/Rel-18/22_series/22867/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-18/22_series/22867/e636d7ccca0ad14c6b95201404324823_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46d088cfc45a6334b35a5b434d835e7a996e202f
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/e636d7ccca0ad14c6b95201404324823_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbf66585e1364378f6bef644ebccc73974b77d3013176b25dfb603728855f9fc
+size 39705
diff --git a/marked/Rel-18/22_series/22867/ed48e24e36ea0501953177401c900f86_img.jpg b/marked/Rel-18/22_series/22867/ed48e24e36ea0501953177401c900f86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe7bd82aa98fb61c6a48208097cb4c2884d43150
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/ed48e24e36ea0501953177401c900f86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed5cb8ecbe6bb33dd8cd311dd997c4c8082deb65350710823418a625e6da2d17
+size 62108
diff --git a/marked/Rel-18/22_series/22867/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-18/22_series/22867/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc907c8e0faf77c1a8bdb66e752b815e6384831a
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:449c1aa8f9e9bef48208a3cc63150644389443469147cb57f07cdfc9b74fd148
+size 33784
diff --git a/marked/Rel-18/22_series/22867/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Rel-18/22_series/22867/f142b022cfc716cd967297f027efe647_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6b43909ce7524a849ada461bc7fe0186f2f0c40
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/f142b022cfc716cd967297f027efe647_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fae31dddb5d3e7e49eb7abc1b1123aca0ca9b6f47b73df169db64a25fa2b8977
+size 26160
diff --git a/marked/Rel-18/22_series/22867/raw.md b/marked/Rel-18/22_series/22867/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..48a329ae44c2f96ceac75d3b304553dce49bbd72
--- /dev/null
+++ b/marked/Rel-18/22_series/22867/raw.md
@@ -0,0 +1,2986 @@
+
+
+# 3GPP TR 22.867 V18.2.0 (2021-12) ---
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on 5G Smart Energy and Infrastructure (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## Keywords ---
+
+Power, Meter, Automation
+
+## **3GPP**
+
+## Postal address ---
+
+## 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet ---
+
+
+
+## ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+
+
+# Contents
+
+| | |
+|---------------------------------------------------------------------------------------|----|
+| Foreword ..... | 7 |
+| 1 Scope..... | 8 |
+| 2 References..... | 8 |
+| 3 Definitions and abbreviations ..... | 11 |
+| 3.1 Definitions..... | 11 |
+| 3.2 Abbreviations ..... | 12 |
+| 4 Overview..... | 13 |
+| 5 Use cases..... | 14 |
+| 5.1 Use case of Distributed Energy Storage..... | 14 |
+| 5.1.1 Description ..... | 14 |
+| 5.1.2 Pre-conditions..... | 15 |
+| 5.1.3 Service Flows ..... | 15 |
+| 5.1.4 Post-conditions ..... | 16 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 16 |
+| 5.1.6 Potential requirements ..... | 16 |
+| 5.2 Use case of advanced metering ..... | 17 |
+| 5.2.1 Description ..... | 17 |
+| 5.2.2 Pre-Conditions ..... | 18 |
+| 5.2.3 Service Flows ..... | 18 |
+| 5.2.4 Post-Conditions ..... | 20 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 20 |
+| 5.3 Use case of Distributed Feeder Automation ..... | 21 |
+| 5.3.1 Description ..... | 21 |
+| 5.3.2 Pre-Conditions..... | 23 |
+| 5.3.3 Service Flows ..... | 23 |
+| 5.3.4 Post-Conditions ..... | 23 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 24 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 24 |
+| 5.4 Use case of line current differential protection in power distribution grid ..... | 24 |
+| 5.4.1 Description ..... | 24 |
+| 5.4.2 Pre-conditions..... | 26 |
+| 5.4.3 Service Flows ..... | 26 |
+| 5.4.4 Post-conditions ..... | 27 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 27 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 27 |
+| 5.5 Smart Energy Differentiated QoS For Transported Encrypted Data ..... | 27 |
+| 5.5.1 Description ..... | 27 |
+| 5.5.2 Pre-conditions..... | 28 |
+| 5.5.3 Service Flows ..... | 28 |
+| 5.5.4 Post-conditions ..... | 28 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 28 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 30 |
+| 5.6 Service Lifetime for Utility Communication Services Deployments ..... | 31 |
+| 5.6.1 Description ..... | 31 |
+| 5.6.2 Pre-conditions..... | 31 |
+| 5.6.3 Service Flows ..... | 31 |
+| 5.6.4 Post-conditions ..... | 32 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 32 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 32 |
+| 5.7 Remote DSO management of connectivity for Smart Energy ..... | 32 |
+| 5.7.1 Description ..... | 32 |
+| 5.7.2 Pre-conditions..... | 34 |
+
+| | | |
+|----------|----------------------------------------------------------------------------------------------|----|
+| 5.7.3 | Service Flows ..... | 37 |
+| 5.7.4 | Post-conditions ..... | 38 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 38 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 39 |
+| 5.8 | Use case of Smart Distribution Transformer Terminal..... | 40 |
+| 5.8.1 | Description ..... | 40 |
+| 5.8.2 | Pre-Conditions ..... | 41 |
+| 5.8.3 | Service Flows ..... | 41 |
+| 5.8.4 | Post-Conditions ..... | 42 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 42 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 42 |
+| 5.9 | Use case of isolation demand for energy applications..... | 43 |
+| 5.9.1 | Description ..... | 43 |
+| 5.9.2 | Pre-Conditions ..... | 44 |
+| 5.9.3 | Service Flows ..... | 44 |
+| 5.9.4 | Post-Conditions ..... | 44 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 45 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 45 |
+| 5.10 | Utility End to End Security ..... | 45 |
+| 5.10.1 | Description ..... | 45 |
+| 5.10.2 | Pre-conditions..... | 45 |
+| 5.10.3 | Service Flows ..... | 46 |
+| 5.10.4 | Post-conditions ..... | 46 |
+| 5.10.5 | Existing features partly or fully covering the use case functionality ..... | 46 |
+| 5.10.6 | Potential New Requirements needed to support the use case..... | 47 |
+| 5.11 | QoS Monitoring and Reporting Mechanisms..... | 47 |
+| 5.11.1 | Description ..... | 47 |
+| 5.11.2 | Pre-conditions..... | 47 |
+| 5.11.3 | Service Flows ..... | 48 |
+| 5.11.4 | Post-conditions ..... | 48 |
+| 5.11.5 | Existing features partly or fully covering the use case functionality ..... | 48 |
+| 5.11.6 | Potential New Requirements needed to support the use case..... | 48 |
+| 5.12 | Distribution Intelligence – FLISR (Fault Location, Isolation, and Service Restoration) ..... | 49 |
+| 5.12.1 | Overview ..... | 49 |
+| 5.12.2 | Feeder automation ..... | 50 |
+| 5.12.2.1 | Description..... | 50 |
+| 5.12.2.2 | Pre-condition..... | 50 |
+| 5.12.2.3 | Service flow ..... | 50 |
+| 5.12.2.4 | Post-condition ..... | 51 |
+| 5.12.2.5 | Existing features partly or fully covering the use case functionality..... | 51 |
+| 5.12.2.6 | Potential New Requirements needed to support the use case..... | 52 |
+| 5.12.3 | High speed current differential protection..... | 52 |
+| 5.12.3.1 | Description..... | 52 |
+| 5.12.3.2 | Pre-condition..... | 52 |
+| 5.12.3.3 | Service flow ..... | 52 |
+| 5.12.3.4 | Post-condition ..... | 52 |
+| 5.12.3.5 | Existing features partly or fully covering the use case functionality..... | 53 |
+| 5.12.3.6 | Potential New Requirements needed to support the use case..... | 53 |
+| 5.13 | Use case of 5GS support for synchrophasors in wide-area Smart Grid ..... | 54 |
+| 5.13.1 | Description ..... | 54 |
+| 5.13.2 | Pre-conditions..... | 55 |
+| 5.13.3 | Service Flows ..... | 55 |
+| 5.13.4 | Post-conditions ..... | 56 |
+| 5.13.5 | Existing features partly or fully covering the use case functionality ..... | 56 |
+| 5.13.6 | Potential New Requirements needed to support the use case..... | 57 |
+| 5.14 | Energy Substation Surveillance ..... | 57 |
+| 5.14.1 | Description ..... | 57 |
+| 5.14.2 | Pre-conditions..... | 58 |
+| 5.14.3 | Service Flows ..... | 58 |
+
+| | | |
+|----------|-------------------------------------------------------------------------------------|----|
+| 5.14.4 | Post-conditions ..... | 58 |
+| 5.14.5 | Existing features partly or fully covering the use case functionality ..... | 58 |
+| 5.14.6 | Potential New Requirements needed to support the use case..... | 58 |
+| 5.15 | Distributed Energy Resources and Microgrids ..... | 59 |
+| 5.15.1 | Description ..... | 59 |
+| 5.15.2 | Pre-condition ..... | 60 |
+| 5.15.3 | Service flow..... | 60 |
+| 5.15.4 | Post-condition..... | 61 |
+| 5.15.5 | Existing features partly or fully covering the use case functionality ..... | 61 |
+| 5.15.6 | Potential New Requirements needed to support the use case..... | 61 |
+| 5.16 | Protection of DER and grid interconnection ..... | 62 |
+| 5.16.1 | Description ..... | 62 |
+| 5.16.2 | Pre-condition ..... | 64 |
+| 5.16.3 | Service flow..... | 64 |
+| 5.16.4 | Post-condition..... | 65 |
+| 5.16.5 | Existing features partly or fully covering the use case functionality ..... | 65 |
+| 5.16.6 | Potential New Requirements needed to support the use case..... | 65 |
+| 5.17 | Utility Service Operator M2M service management platform in Smart Energy ..... | 65 |
+| 5.17.1 | Description ..... | 65 |
+| 5.17.2 | Pre-condition ..... | 68 |
+| 5.17.3 | Service flow..... | 69 |
+| 5.17.4 | Post-condition..... | 69 |
+| 5.17.5 | Existing features partly or fully covering the use case functionality ..... | 69 |
+| 5.17.6 | Potential New Requirements needed to support the use case..... | 70 |
+| 5.18 | Coordination for Energy Recovery Use Case ..... | 70 |
+| 5.18.1 | Description ..... | 70 |
+| 5.18.2 | Pre-conditions..... | 71 |
+| 5.18.3 | Service Flows ..... | 71 |
+| 5.18.4 | Post-conditions ..... | 72 |
+| 5.18.5 | Existing features partly or fully covering the use case functionality ..... | 72 |
+| 5.18.6 | Potential New Requirements needed to support the use case..... | 72 |
+| 5.19 | Applications Using IEC 61850-9-2 Sampled Values..... | 73 |
+| 5.19.1 | Description ..... | 73 |
+| 5.19.2 | Pre-conditions..... | 73 |
+| 5.19.3 | Service flows ..... | 74 |
+| 5.19.4 | Post-conditions ..... | 74 |
+| 5.19.5 | Existing feature partly or fully covering use case functionality..... | 74 |
+| 5.19.6 | Potential new requirements and KPIs..... | 74 |
+| 5.19.6.1 | Potential Requirements ..... | 74 |
+| 5.19.6.2 | Potential KPIs ..... | 74 |
+| 5.20 | Use case of power distribution grid state estimation service ..... | 75 |
+| 5.20.1 | Description ..... | 75 |
+| 5.20.2 | Pre-conditions..... | 75 |
+| 5.20.3 | Service flows ..... | 75 |
+| 5.20.3.1 | Introduction..... | 75 |
+| 5.20.3.2 | Power system requirements of SE service..... | 76 |
+| 5.20.4 | Post-conditions ..... | 76 |
+| 5.20.5 | Existing feature partly or fully covering use case functionality..... | 76 |
+| 5.20.6 | Potential New Requirements needed to support the use case..... | 77 |
+| 5.21 | Use case of power distribution grid power control service ..... | 77 |
+| 5.21.1 | Description ..... | 77 |
+| 5.21.2 | Pre-conditions..... | 77 |
+| 5.21.3 | Service flows ..... | 77 |
+| 5.21.3.1 | Introduction..... | 77 |
+| 5.21.3.2 | Power system requirements of PC service..... | 78 |
+| 5.21.4 | Post-conditions ..... | 79 |
+| 5.21.5 | Existing feature partly or fully covering use case functionality..... | 79 |
+| 5.21.6 | Potential New Requirements needed to support the use case..... | 80 |
+| 5.22 | Use Case of ensuring uninterrupted MTC service availability during emergencies..... | 80 |
+
+| | | |
+|-----------------------------------------------|----------------------------------------------------------------------------------|-----------|
+| 5.22.1 | Description ..... | 80 |
+| 5.22.2 | Pre-conditions ..... | 81 |
+| 5.22.3 | Service flows ..... | 81 |
+| 5.22.4 | Post-conditions ..... | 82 |
+| 5.22.5 | Existing feature partly or fully covering use case functionality ..... | 82 |
+| 5.22.6 | Potential New Requirements needed to support the use case ..... | 82 |
+| 5.23 | Edge cloud driven data acquisition (edgePMU) ..... | 82 |
+| 5.23.1 | Description ..... | 82 |
+| 5.23.2 | Pre-conditions ..... | 83 |
+| 5.23.3 | Service Flows ..... | 83 |
+| 5.23.4 | Post-conditions ..... | 83 |
+| 5.23.5 | Existing features partly or fully covering the use case functionality ..... | 84 |
+| 5.23.6 | Potential New Requirements needed to support the use case ..... | 84 |
+| 5.24 | Use case of power distribution grid load and generation prediction service ..... | 84 |
+| 5.24.1 | Description ..... | 84 |
+| 5.24.2 | Pre-conditions ..... | 84 |
+| 5.24.3 | Service Flows ..... | 85 |
+| 5.24.3.1 | Introduction ..... | 85 |
+| 5.24.3.2 | Power system requirements of LP/GP service ..... | 85 |
+| 5.24.4 | Post-conditions ..... | 85 |
+| 5.24.5 | Existing features partly or fully covering the use case functionality ..... | 85 |
+| 5.24.6 | Potential New Requirements needed to support the use case ..... | 86 |
+| 6 | Considerations ..... | 86 |
+| 6.1 | Potential security considerations ..... | 86 |
+| 6.2 | Potential charging considerations ..... | 87 |
+| 7 | Consolidated potential requirements and KPIs ..... | 88 |
+| 7.1 | Consolidated potential requirements ..... | 88 |
+| 7.2 | Consolidated potential KPIs ..... | 91 |
+| 8 | Conclusion and recommendations ..... | 95 |
+| Annex A: Underground 3GPP Access ..... | | 96 |
+| A.1 | Description ..... | 96 |
+| A.2 | Pre-conditions ..... | 97 |
+| A.3 | Service Flows ..... | 97 |
+| A.4 | Post-conditions ..... | 97 |
+| A.5 | Existing features partly or fully covering the use case functionality ..... | 97 |
+| A.6 | Potential New Requirements needed to support the use case ..... | 98 |
+| Annex B: Change history ..... | | 99 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document is to address study use cases, potential new service requirements for 5G system to support Smart Grid including the following topics:
+
+- Smart Grid services, e.g. IEC standards, and their communications requirements including capacity, latency, availability, end-to-end QoS, resilience/redundancy and security.
+- Deployment requirements when considering constraints e.g. service lifetime, coverage (ubiquity), electromagnetic applicability (e.g. penetration, ability to operate in high EM environments,) etc.
+- Additional requirements due to operational manageability – e.g. the ability to configure and monitor the real (achieved & up to date) availability of virtual network topologies
+- New Smart Grid use cases and potential service function requirements: e.g. on-demand power supply, distributed power supply system, distribution automation, higher accuracy power load measurement and control, meter automation, etc.
+- Communication KPI and service requirements for enabling microgrids, DER and specifically distributed generation (DG) that require 5G wireless communication (e.g. wind and solar energy generation, including scenarios at or near residential / consumer premises, etc.)
+
+# --- 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] SunWeiqing etc. Generalized Energy Storage Control Strategies on User Side in Power Ancillary Service Market. Automation of Electric Power System Vol.44 No.2 Jan.25, 2020
+- [3] IEEE C37.2-2008 IEEE Standard Electrical Power System Device Function Numbers, Acronyms, and Contact Designations.
+- [4] IEC TR 61850-90-1:2010, Communication Networks and Systems for Power Utility automation – Part 90-1: Use of IEC61850 for the communication between substations.
+- [5] IEEE 1588-2019 – IEEE Standard for a precision clock synchronization protocol for networked measurement and control systems.
+- [6] IEEE Guide for Application of Digital Line Current Differential Relays Using Digital Communication.
+- [7] IEC 61850-9-3-2016 – IEC/IEEE International Standard - Communication Networks and Systems for Power Utility automation – Part 9-3: Precision time protocol profile for power utility
+- [8] 3GPP TR 22.804: "Study on Communication for Automation in Vertical domains (CAV)".
+- [9] Sendin, A., et. al., "Telecommunication Networks for the Smart Grid," Artech House, 2016.
+
+- [10] Goel, S., S. F. Bush, and D. Bakken, (eds.), IEEE Vision for Smart Grid Communications: 2030 and Beyond, New York: IEEE, 2013.
+- [11] US Department of Energy, "Communications Requirements of Smart Grid Technologies, 2010", accessed 14.08.20, [http://energy.gov/sites/prod/files/gcprod/documents/Smart\\_Grid\\_Communications\\_Requirements\\_Report\\_10-05-2010.pdf](http://energy.gov/sites/prod/files/gcprod/documents/Smart_Grid_Communications_Requirements_Report_10-05-2010.pdf)
+- [12] IT Process Wiki – The ITIL Wiki: Content is available according to Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Germany License. Access 14.10.20.
+- [13] Incident Management: [https://wiki.en.it-processmaps.com/index.php/Incident\\_Management](https://wiki.en.it-processmaps.com/index.php/Incident_Management) Content is available according to Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Germany License. Access 14.10.20.
+- [14] Change Management: [https://wiki.en.it-processmaps.com/index.php/Change\\_Management](https://wiki.en.it-processmaps.com/index.php/Change_Management) Content is available according to Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Germany License. Access 14.10.20.
+- [15] Service Asset and Configuration Management: [https://wiki.en.it-processmaps.com/index.php/Service\\_Asset\\_and\\_Configuration\\_Management](https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management) Content is available according to Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Germany License. Access 14.10.20.
+- [16] Open PLC European Research Alliance (OPERA).
+- [17] "Applications of ITU-T G.9960, ITU-T G.9961 transceivers for Smart Grid applications: Advanced metering infrastructure, energy management in the home and electric vehicles", 06/2020. [https://www.itu.int/dms\\_pub/itu-t/opb/tut/T-TUT-HOME-2010-PDF-E.pdf](https://www.itu.int/dms_pub/itu-t/opb/tut/T-TUT-HOME-2010-PDF-E.pdf)
+- [18] M. Amin and A. Giacomoni, "Toward more secure, stronger and smarter electric power grids," IEEE PES'11, 2011.
+- [19] Eric D. Knapp, Raj Samani, "Smart Grid Network Architecture", "Applied Cyber Security and the Smart Grid", 2013
+- [20] 5G DNA White Paper: "5GDN@Smart Grid White Paper: Requirements, Technologies, and Practices"
+- [21] IEEE Std 1344™-1995 (R2001), IEEE Standard for Synchrophasors for Power Systems
+- [22] IEEE Std C37.118™-2011, IEEE Standard for Synchrophasors for Power Systems
+- [23] IEEE Std 1588-2008, Precision Clock Synchronization Protocol for Networked Measurement and Control Systems
+- [24] IEEE Std C37.238-2017 , IEEE Standard Profile for Use of IEEE Std 1588™ Precision Time Protocol in Power System Applications.
+- [25] IEEE Std C37.224-2013
+- [26] IEC 61850-90-5:2012, use of IEC 61850 to transmit Synchrophasors information according to IEEE C37.118
+- [27] IEEE Std C37.118.1a-2014: amendment 1 with modification of selected performance requirements.
+- [28] IEEE Std C37.118.2-2011
+- [29] IEC 61850-90-3-2016 – IEC/IEEE International Standard - Communication Networks and Systems for Power Utility automation – Part 90-3:Using IEC 61850 for condition monitoring diagnosis and analysis
+- [30] Budka, K, et. al., "Communication Networks for Smart Grids", Springer Verlag, 2014.
+
+- [31] Microgrid Knowledge:
+- [32] M. A. Haj-ahmed and M. S. Illindala, "The influence of inverter-based DGs and their controllers on distribution network protection," in Proc. IEEE Ind. Appl. Soc. Annu. Meeting, Oct. 2013.
+- [33] IEC, IEC 61850-5 communication networks and systems in substations – Part 5: communication requirements for functions and device models. <>.
+- [34] Moreira, N., Molina, E., Lázaro, J., et al: "Cyber-security in substation automation systems", Renew. Sustain. Energy Rev., 2016
+- [35] EN 50549-1, "Requirements for generating plants to be connected in parallel with distribution networks—Part 1: Connection to a LV distribution network— generating plants up to and including Type B"
+- [36] EN 50438, "Requirements for micro-generating plants to be connected in parallel with public low-voltage distribution networks"
+- [37] IEEE 1547 -2018, "Standard for Interconnecting Distributed Resources with Electric Power Systems"
+- [38] IEEE 1547.4-2011, "IEEE Guide for Design, Operation, and Integration of Distributed Resources Island Systems with Electric Power Systems"
+- [39] IEC 63547, "Interconnecting distributed resources with electric power systems"
+- [40] IEC 62898-1, "Microgrids—Part 1: Guidelines for microgrid projects planning and specification"
+- [41] IEC 62898-2, "Microgrids—Part 2: Guidelines for operation"
+- [42] IEC 62898-3-1, "Microgrids—Part 3: Technical requirements - Protection and dynamic control"
+- [43] BDEW, "Generating Plants Connected to the Medium-Voltage Network"
+- [44] IEEE 929-2000, "IEEE recommended practice for utility interface of photovoltaic systems"
+- [45] IEEE Std. 2030.7, "the Specification of Microgrid Controllers"
+- [46] DLMS/COSEM – Device Language Message Specification:
+- [47] DLMS/COSEM Architecture and Protocols, Companion Specification for Energy Metering
+- [48] European Commission Electricity Directive 2009/72/EC
+- [49] IEC 61850-9-2:2011 Communication networks and systems for power utility automation - Part 9-2: Specific communication service mapping (SCSM) - Sampled values over ISO/IEC 8802-3
+- [50] IEC/IEEE 60255-118-1-2018 - IEEE/IEC International Standard - Measuring relays and protection equipment - Part 118-1: Synchrophasor for power systems – Measurements
+- [51] 3GPP TR 22.878: "Feasibility Study on 5G Timing Resiliency System"
+- [52] SOGNO project, Deliverable 4.6, "Description of the integration and testing of the solution including the 5G based advanced communication", [https://www.sogno-energy.eu/global/images/cms/Deliverables/774613\\_deliverable\\_D4.6.pdf](https://www.sogno-energy.eu/global/images/cms/Deliverables/774613_deliverable_D4.6.pdf), June 2020.
+- [53] McKeever, P.; De Din, E.; Sadu, A.; Monti, A: "MAS for automated black start of multi-microgrids". In Proceedings of the 2017 IEEE International Conference on Smart Grid Communications (SmartGridComm), Dresden, Germany, 23–27 October 2017; pp. 32–37.
+- [54] Gazis, V. A Survey of Standards for Machine-to-Machine and the Internet of Things. IEEE Commun. Surv. Tutor. 2017, 19, 482–511. [[CrossRef](#)]
+
+- [55] Ghorbanian, M.; Dolatabadi, S.; Masjedi, M.; Siano, P. Communication in Smart Grids: A Comprehensive Review on the Existing and Future Communication and Information Infrastructures. *IEEE Syst. J.* 2019, 13, 4001–4014. [[CrossRef](#)]
+- [56] Oueis, J.; Conan, V.; Lavaux, D.; Stanica, R.; Valois, F. Overview of LTE Isolated E-UTRAN Operation for Public Safety. *IEEE Commun. Stand. Mag.* 2017, 1, 98–105. [[CrossRef](#)]
+- [57] Ali, S. *Next Generation and Advanced Network Reliability Analysis Using Markov Models and Software Reliability Engineering*; Springer Nature Switzerland AG: Basel, Switzerland, 2019.
+- [58] McKeever, Padraic & Sadu, Abhinav & Rohilla, Shubham & Mehdi, Zain & Monti, Antonello. (2020). Ensuring Uninterrupted MTC Service Availability during Emergencies Using LTE/5G Public Mobile Land Networks. *Telecom.* 1. 181-195. 10.3390/telecom1030013.
+- [59] eSafeNet Project, [Online], Available:
+- [60] Insulae Project, [Online], Available:
+- [61] SOGNO project, Deliverable 2.2, "Description of initial interfaces & services for grid awareness", [https://www.sogno-energy.eu/global/images/cms/Deliverables/774613\\_SOGNO\\_D2.2.pdf](https://www.sogno-energy.eu/global/images/cms/Deliverables/774613_SOGNO_D2.2.pdf), December 2018.
+- [62] edgeFLEX project, Deliverable 1.2, "Dynamic-phasor driven voltage control concept for current VPPs in large scale deployment deliverable", , 31.03.2021.
+- [63] edgeFLEX project, Deliverable 4.1, "Description of edgeFLEX platform design", , 31.03.2021.
+- [64] National Institute of Standards and Technology (NIST), "Timing Challenges in the Smart Grid", January 2017.
+- [65] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
+- [66] V. Cagri Gungor, Dilan Sahin, Taskin Kocak, Salih Ergut, Concettina Buccella, Carlo Cecati, and Gerhard P. Hancke, "A Survey on Smart Grid Potential Applications and Communication Requirements", [https://repository.up.ac.za/bitstream/handle/2263/58376/Gungor\\_Survey\\_2013.pdf](https://repository.up.ac.za/bitstream/handle/2263/58376/Gungor_Survey_2013.pdf)
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Smart Distribution Transformer Terminal:** The smart terminal is usually deployed in the distribution transformer area. It can support multiple energy applications simultaneously. On the one hand, it connects with multiple energy application platforms through 5G communication system to exchange collected data and management data with multiple energy application platforms; on the other hand, it connects with diverse energy end equipment to collect related electricity data, some of which can be analysed and take action in the smart terminal.
+
+**Physical Isolation communication service:** the physical isolation communication service for energy application means the communication network supporting the energy application utilizes dedicated network element and dedicated radio resource e.g. PRB pool, spectrum etc.
+
+**Logical Isolation communication service:** the logical isolation for energy application means the communication network supporting the energy application may utilize shared network element or shared network resource e.g. VLAN etc.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|------------------------------------|
+| BC | Boundary Clock |
+| GNSS | Global Navigation Satellite System |
+| PMU | Phasor Measurement Unit |
+| PTP | Precision Time Protocol |
+| TC | Transparent Clock |
+| TVE | Total Vector Error |
+
+# --- 4 Overview
+
+Communication infrastructure is essential to the successes of smart energy, generally termed the 'Smart Grid'. A power grid consists of four building blocks: power generation, transmission, distribution, and consumption. These different phases require different services, and these services have distinct communication requirements. Examples of communication include data collection, control and ongoing regulation, though these are functions of diverse services – e.g. SCADA applications for the Energy Management System (EMS) or Distribution Management System (DMS). Smart Grid communication infrastructure, overcomes different challenges in order to provide:
+
+- Distributed power generation, increasingly including 'renewable' or 'clean' energy sources
+- Safe & highly efficient power transforming & transmission
+- Flexible & reliable power distribution
+- Efficient & available power consumption
+- Cyber security & resilience/redundancy
+
+Smart Grid services today rely upon a range of telecommunications services, delivered through a blend of private networks and commercially provided services. As the energy system goes through changes, becoming more pervasive (in territorial terms,) complex and sophisticated to meet the above goals, there is a distinct opportunity for 5G to meet more of the utility communication sector's needs and thereby become increasingly relevant to this vertical, addressing existing shortcomings, as it builds out further capacity and enhances existing infrastructure. Many of these grid services are standardized by other standards bodies, e.g. IEC60870, IEC61850 and IEEE.
+
+In summary, it is considered beneficial for 3GPP specifications in addressing 5G system support of different use cases and service requirements for Smart Grid.
+
+# 5 Use cases
+
+## 5.1 Use case of Distributed Energy Storage
+
+### 5.1.1 Description
+
+Distributed energy includes various forms such as solar energy, wind energy, fuel cell and gas combined. It is generally distributed in the user site, or near locations to realize energy generation, storage and supply. Distributed energy system has the characteristics of flexible location and decentralization, which adapts well to decentralized energy demand, and has reduced the huge investment required for upgrading the transmission and distribution power grid. It also works as a backup for the large power grid to improve reliability of whole energy supply. In storms, ice and snow weather, when the large power grid is severely damaged, distributed energy sources can form islands or microgrids on their own to provide emergency energy to important users such as hospitals, transportation hubs, radio and television.
+
+But the distributed energy system has brought new technical problems and challenges to the power grid operation. When the distributed energy is connected to the large power grid, the energy flow on the distributed power grid becomes more complicated for that the user is becoming both the electricity user and the generator, and the current presents two-way flow and real-time dynamic changes. To improve the reliability, flexibility and efficiency of the distributed power grid, the communication system with a low latency, high reliability, massive connections and a high data rate is considered.
+
+
+
+The diagram shows a central cloud representing the WAN. Connected to this cloud are several Distributed Energy Devices (DEDs). On the top left, a DED is connected to solar panels (labeled 'Solar monitoring'), a 'Solar inverter', a 'Temp. sensor', and a 'Current meter'. Another DED is connected to a 'Wind sensor'. On the bottom left, a DED is connected to 'Electric Vehicle Energy monitoring' (showing two cars). On the bottom center, a DED is connected to 'Energy Storage station monitoring' (showing a building). On the top right, a DED is connected to a 'Local SCADA' system (showing a monitor). All DEDs are connected to a 'Distributed Energy Storage Management Platform (DESMP)' represented by a cloud on the right side of the diagram.
+
+Figure 5.1.1-1: Example of Distributed Energy Storage grid architecture. The diagram illustrates a network of Distributed Energy Devices (DEDs) connected to a central Distributed Energy Storage Management Platform (DESMP) via a Wide Area Network (WAN). The DEDs are connected to various energy sources and loads: solar panels (with monitoring and inverter), wind turbines (with sensors), electric vehicles (with energy monitoring), and an energy storage station (with monitoring). A local SCADA system is also connected to one of the DEDs.
+
+**Figure 5.1.1-1: Example of Distributed Energy Storage grid architecture**
+
+Seeing Figure 5.1.1-1, it is one example of Distributed Energy storage grid architecture. The distributed power grid which is comprised of residential, commercial and light storage users, requires to exchange information among the Distributed Energy Storage Management Platform (DESMP) and the diverse Distributed Energy Devices (DED). The information exchanged in the distributed energy grid is not only to collect energy related data, but also to coordinate working flows of the distributed energy storage equipment, to change the equivalent load characteristics, and to realize flexible energy grid through load interaction etc.
+
+The DED is plug-and-play and periodically collects the operating information, such as battery energy, charge and discharge energy, alarm information, etc., and transfers them to DESMP. The DESMP regularly maintains connections with the DED and determines the online status and issue instructions to the DED to control the switch of the device and set the energy etc. Further, it obtains the electricity, energy, load and other information of the grid-connected users in the area from the DED to support the decision-making of flexible interaction between the distributed energy storage and the large power grid, or to analyze the user's electricity habits to guide the operation of distributed energy storage.
+
+### 5.1.2 Pre-conditions
+
+Distributed energy system has the following functions: data acquisition and processing, active power adjustment, voltage and reactive power control, island detection, dispatch and coordination control, etc. It is mainly composed of DESMP, the DED and communication system.
+
+The DESMP is located in region center. And the diverse DED can be deployed in buildings, indoors, outdoors, tunnels, ports and electric vehicles which may be faced a poor communication signal condition or even out of network coverage.
+
+The 5G system connects the DEDs with the DESMP.
+
+### 5.1.3 Service Flows
+
+Every time after the DED and the DESMP establish a communication connection, the DED reports its configuration data to DESMP. For reliability, in general, the communications between DESMP and DED should be supported by multiple connections and backup each other.
+
+The heartbeat data is always transmitted between the DESMP and DED to maintain a normal connection.
+
+In the process of general service flow, there are three kinds of data exchange:
+
+- a) Command delivering: DESMP sends control commands to the DED. It always requires <10ms latency with 99.9% reliability communication service for control frequency, power etc.
+- b) Data reporting: equipment normal operation information, mainly including energy storage battery, energy storage converter, AC and DC charging and discharging equipment and other current operating data. It always requires <1s latency.
+- c) Other data: For example, the DED actively requests data, such as requesting the electricity price information from DESMP, and the AC/DC charging and discharging facility sends relevant information about the current charging and discharging under abnormal conditions.
+
+Based on the general service flow, in different scenarios, the data collection requirement is different. The following lists two typical scenarios in distributed energy storage service (NOTE: these data are from CEPRI).
+
+#### Case 1: data collection for energy storage in rural area
+
+In the typical scenario of energy storage in rural area, it is always a large energy storage in one location. Considering the data collection, taking 100Ah lithium iron phosphate batteries as an example, the integration of a 2MWh energy storage container requires 6,250 batteries. So there are 6250 voltage and temperature collection points, and 780 current collection points, plus other 12-bit data e.g. alarms, internal auxiliary equipment such as air-conditioning, environmental monitoring and video. The collection data for the 2 MWh energy storage container is about 20,000 16-bit data and among them, the current related collection points is about 800, which need implement collection every millisecond and report every 10 ms, other 13000 points need implement collection and report every second.
+
+Thus, there are at least two traffic models (except video) in the typical 100MWh energy storage station which is constructed by 50 2MWh energy storage containers. One is for current flow with $(800 \times 50 = 40000)$ collection 16-bit data per millisecond, and every 10ms, the UL reported data volume is $(40000 \times 2 \times 10 = 800 \text{ kbyte}/10\text{ms})$ which data rate is 640Mbit/s. The others are $(13000 \times 50 = 650000)$ collection 16-bit data per second, and every second, the UL reported data volume is $(650000 \times 2 = 1300 \text{ kbyte}/\text{s})$ which data rate is 10.4 Mbit/s.
+
+Besides above, the surveillance video is the third kind of collected data. In every storage container, the typical video data is 12.5 Mbytes for every second. And in one energy storage station, there need 50 storage containers. Thus, the UL data rate per storage station is up to $12.5 \text{ Mbytes}/\text{s} \times 50(\text{containers}) \times 8 = 5 \text{ Gbit}/\text{s}$ .
+
+#### Case 2: data collection for distributed energy storage in urban area
+
+Virtual energy storage (VES) is a new type of energy storage system formed by the aggregation of user side power loads (such as air conditioning, refrigeration, heating, electric vehicles, etc.) with certain adjustment capabilities. [2]
+
+In urban area scenario, electric vehicle is one type of VES element. It is a trend that the DED will be installed in the electric vehicle not only in the charging pole.
+
+For electric vehicle, it is generally installed with about 7000 batteries which requires 7000 voltages, about 1000 current & temperature collection points at least. Further considering other collected data such as electronic control, charging and vehicle-grid interaction, for one electric vehicle, there is total about 10,000 16-bit data and among them, the current related collection data is more than 1000 16-bit data which need to be collected every millisecond and reported every 10ms, the others is more than 8000 16-bit data which need to be collected and reported every second.
+
+So, there are also at least two traffic models in this case, one is the current model, every 10 ms, the UL reported data volume is $(1000*2*10=20 \text{ kbytes})$ which data rate is 16 Mbit/s. The other is reported every second and the data volume is $(8000*2=16 \text{ kbytes/s})$ which data rate is 128 kbit/s.
+
+### 5.1.4 Post-conditions
+
+In urban public building, community, industrial park, rural village, this kind of distributed energy storage system with the help of 5G system works well and can supply reliable power for users.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+The 5G system shall be able to provide required communication service for distributed power storage where it is indoor, outdoor, underground etc.
+
+When required by regulations, the 5G system shall be able to utilize dedicated communication resource including core network and radio network to support physical isolation communication service for energy applications.
+
+### 5.1.6 Potential requirements
+
+[PR.5.1-001] The 5G system shall be able to provide required communication service for distributed energy storage according to the KPIs given in table 5.1.6-1 and table 5.1.6-2.
+
+**Table 5.1.6-1: periodic communication service performance requirements - data for distributed energy storage**
+
+| scenario | use case | transfer interval target value (ms) | message size (byte) | data rate per storage location (bit/s) (note 1) | communication latency (ms) | reliability | storage node density # /km2 (note 2) | active factor/ km2 (note 3) |
+|-------------|--------------------------------------------------------------|-------------------------------------|-------------------------|-------------------------------------------------|----------------------------|-------------|--------------------------------------|-----------------------------|
+| Dense Urban | Virtual energy storage monitoring | UL: 10 | UL:>20k | UL: >16 M
DL: >100 k | DL:10
UL:10 | DL: >99.90% | >1k | 10% |
+| | Virtual energy storage: other data collection | UL: 1000 | UL: 16k
DL: >100k | UL: >128 k
DL: >100 k | DL:<10
UL:<1000 | DL: >99.90% | >1k | 10% |
+| Rural | Power storage station monitoring | UL: 10 | UL: 16k*50 | UL: > 640 M
DL: > 100 k | DL:<10
UL:<10 | DL: >99.90% | >100 | 10% |
+| | Energy storage station operation data collection: other data | UL: 1000 | UL: 26k*50
DL: >100k | UL: > 10.4 M
DL: > 100 k | DL:<10
UL:<1000 | DL: >99.90% | >100 | 10% |
+
+| | |
+|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NOTE 1: | This KPI is to require data rate in one Energy storage station which may via one or more 5G connections and via one or more 3GPP UE(s) at the same time. |
+| NOTE 2: | It is used to deduce data volume in an area which has multiple energy storage stations. The data volume can be deduced through follow formula: $(\text{Current} + \text{other data}) \text{ data rate per storage station} * (\text{Storage node density /km}^2) * (\text{Active factor/km}^2) + \text{video data rate per storage station} * (\text{Storage node density /km}^2)$ |
+| NOTE 3: | Active factor means the proportion that the number of active DED which are delivering its collected data during one second time window compared with whole number of DED in the area which has multiple energy storage station |
+
+**Table 5.1.6-2: Aperiodic communication service performance requirements - video for distributed energy storage**
+
+| scenario | use case | data rate per storage station (bit/s) (note 1) | communication latency (ms) | reliability | storage node density # / km 2 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|------------------------------------------------|----------------------------|-------------|------------------------------------------|
+| Rural | Energy storage station: video | UL: >5 G
DL: >100 k | DL:<10
UL:<1000 | DL: >99.90% | >100 |
+| NOTE 1: The data rate is to require data rate in one Energy storage station which may via one or more 5G connections and one or more 3GPP UE(s) at the same time. It can be calculated with following formula: $12.5 \text{ Mbytes/s} * 50(\text{containers}) * 8 = 5 \text{ Gbit/s}$ | | | | | |
+
+## 5.2 Use case of advanced metering
+
+### 5.2.1 Description
+
+Instead of recording and sending the metering data from a traditional wired electricity meter unit, electricity metering collecting can be executed by an UE integrated smart meter unit Smart meter units can send real-time metering data to the server in the Power Enterprise through mobile networks. In this way, the Power Enterprise based on the analysis of the user's power consumption behavior give users more scientific and reasonable power consumption suggestions, to develop users' power consumption and energy-saving habits. This is also a possible usage of AMI.
+
+Advanced Metering utilizes AMI (Advanced Meter Infrastructure) system to collect, count, analyze, distribute and manage abnormal electrical energy data in the generation, transmission, distribution and using stages. It can collect real-time data of user power, monitor line loss, and power outage, real-time identify the change of household, calculate of three-phase imbalance, and monitor station voltage.
+
+NOTE: The information obtained from smart appliances are never considered accurate nor guaranteed by certification authorities. This information is useful to customers to understand and influence their consumption patterns.
+
+The AMI is usually comprised of smart meter, concentrator, two-way communication network, measurement data management system (MDMS), and an optional user indoor network (HAN). See Figure 5.2.1-1.
+
+
+
+Figure 5.2.1-1: AMI example architecture diagram. The diagram shows a hierarchical structure. At the top is a box labeled 'MDMS'. Below it is a cloud labeled 'Communication system'. Below the cloud is a box labeled 'Smart master meter'. Below this meter is a horizontal bus line. Connected to this bus line are several 'Smart meter' boxes. The first four are shown individually, with dotted lines between the second and third, and between the third and fourth. The fifth and sixth are also shown individually, with a dotted line between them. Ellipses indicate additional meters are connected to the bus.
+
+**Figure 5.2.1-1: AMI example architecture**
+
+In general, the electric smart meter co-works with MDMS to deliver and perform control command for measuring instruments. The electric smart meters monitor relevant user energy status and deliver these data through concentrator to MDMS. The MDMS sends control commands according to its policy and status data collected. The remote commands from the MDMS include: tripping, closing permission, alarm, alarm release, power protection, power protection release.
+
+Accurate Fee control is one of the basic service of advanced metering, when the user owes the fee or there is an emergency, it should be able to cut off or restore power supply in time, as the operation involves the safety& QoE of power users, a real-time response is required.
+
+For the advanced metering application, the application layer through the communication protocol to encrypt and protect these key data, in order to protect all data, at least logical isolation is required, physical isolation is better.
+
+**NOTE:** Billing may or may not be correlated with use of MDMS service, as in many geographies the DSO is a distinct business entity from the Retailer, who has the direct business relationship with the customer. In such a case, the smart meter information will not be correlated with any billing information and cannot therefore provide feedback to customers concerning the billing impact of their energy usage.
+
+Due to massive electricity meter boxes and household appliances keep online at the same time, the amount of connections the mobile network maintains simultaneously is so enormous that challenging to the mobile network capacity. It is estimated that the increased connections will up to 50-100 times.
+
+### 5.2.2 Pre-Conditions
+
+SS is a power company and it constructs AMI system to deploy advanced meter service for its users. Operator TT has a contract with the power company SS to supply communication service for the AMI system.
+
+Tom is one of the user of SS. In his house, all the electric equipment's energy data can be collected by smart meter and then reported to the MDMS of SS.
+
+The smart meter is located in Tom's house or nearby and the MDMS is located in the remote city center. The distance between the smart meter and the energy management center can be as far as a middle size city range (e.g. Tens of km).
+
+Peter is another user of SS. He has a contract with SS about smart energy usage in his house. SS provides electrical sockets with metering function for typical electrical appliances in his house and all the electrical energy generated by typical electrical appliances that from the electrical socket is measured in real time.
+
+### 5.2.3 Service Flows
+
+Scenario 1:
+
+- 1) The smart meter in Tom's house report related energy usage data to SS.
+
+- 2) The MDMS of SS sends commands to smart meter in Tom's home to adjust smart meter report frequency and content considering its whole energy working status.
+- 3) The smart meter in Tom's home changes the report scheme accordingly.
+- 4) When the MDMS detects that the user's remaining electricity will be run out, it will send an alarm command to remind the user to recharge as soon as possible;
+- 5) When the user's remaining electricity is exhausted, the MDMS will issue a trip command and the smart meter need implement the trip action accordingly which requires the latency less than 200ms (command delivery + command action);
+- 6) When there are special circumstances that cannot be cut off, the MDMS can issue a power protection command in advance to ensure that the smart meter will not trip for related circumstances.
+
+#### Scenario 2:
+
+- 1) After the smart meter in Tom's house reports the status data to the MDMS, it detects that something is wrong with Tom's home electricity supply system.
+- 2) The MDMS asks the smart meter to report more information for troubleshooting.
+- 3) The smart meter co-works with MDMS to resolve the problem.
+
+#### Scenario 3:
+
+The smart energy meter works as a home gateway, and every electric equipment with metering functions is connected and interacted with the smart energy meter through HPLC (high-speed power line carrier) or 5G. The figure 5.2.3-1 illustrates the typical scenario.
+
+The electricity consumption information of various smart household appliances is delivered to the smart energy meter. Then the smart energy meter uploads them to backend platform through 5G system. These information are user private data and require physical isolation delivery with other application data.
+
+
+
+```
+
+graph TD
+ Backend[Backend system] <--> |5G channel| SmartMeter[Smart meter with 5G module]
+ subgraph Household
+ direction TB
+ subgraph EnergyCost [Energy cost data interaction]
+ direction LR
+ P1[Plug with metering]
+ P2[Plug with metering]
+ P3[Plug with metering]
+ P4[Plug with metering]
+ end
+ A1[Airconditioner] --- P1
+ A2[Refrigerator] --- P2
+ A3[Electric heater] --- P3
+ A4[Kitchen appliance] --- P4
+ P1 & P2 & P3 & P4 --- HPLC[ ]
+ style HPLC fill:none,stroke:none
+ end
+ SmartMeter --- HPLC
+ style HPLC fill:none,stroke:none
+
+```
+
+Diagram illustrating the smart meter as a home gateway. A 'Backend system' is connected to a 'Smart meter with 5G module' via a '5G channel'. The smart meter is connected to four 'Plug with metering' units via 'HPLC' lines. These units are further connected to 'Airconditioner', 'Refrigerator', 'Electric heater', and 'Kitchen appliance' respectively. The entire household appliance section is labeled 'Household' and 'Energy cost data interaction'.
+
+**Figure 5.2.3-1: smart meter works as home gateway**
+
+- 1) The socket measures energy data in real time and deliver it to the smart energy meter. The communication link between them can be HPLC (High-speed power line carrier) or 5G.
+- 2) The smart energy meter acting as a data gateway can receive all the energy data in Peter's house and send them to the backend platform of SS.
+- 3) According to the actual load of the energy grid, SS has the possibility to adjust user's energy usage in real time. For example, when the energy is overload, the backend platform sends control command to adjust the temperature of the air conditioner in Peter's house; when the energy load is reduced, it can encourage users to use more energy such as electric vehicle charging.
+
+### 5.2.4 Post-Conditions
+
+The energy related information from electric equipment can be reported to the MDMS on demand with required content and required communication performance.
+
+The electric accurate fee control function can be implemented.
+
+Co-working with smart meter, the MDMS can remotely troubleshoot energy problem for its user.
+
+The power grid company regularly provides users with detailed energy consumption analysis reports based on the collected data, and guides users to use electricity scientifically and rationally.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+The 5G system shall be able to support resilience to dynamic adjust connection service performance considering advanced metering demand.
+
+The 5G system shall be able to provide connection service wherever indoor, outdoor, low and medium altitude for advanced metering applications.
+
+The 5G system shall be able to support at least logical isolation communication service for advanced meter applications.
+
+NOTE: The logical isolation communication service can utilize shared network element or shared network resource. To advanced meter application, it is the minimum requirement.
+
+The 5G IoT device shall be able to connect energy equipment via 3GPP/non-3GPP connections to get energy data and to deliver the data to back-end energy applications via 5G connection.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR.5.2-001] The 5G system shall be able to provide required communication service for advanced metering application according to KPI given in table 5.2.6-1.
+
+**Table 5.2.6-1: Communication KPI for advanced metering (note 1)**
+
+| User experienced data rate (bit/s) | Latency (ms) | Reliability % | Connection density | Coverage |
+|------------------------------------|-------------------------------------------------------------------------------------|---------------|---------------------------------|----------|
+| UL:<2M
DL:<1M | Accuracy fee control: < 100 (note 2);
General information data collection: <3000 | >99.99 | <10000/km 2 (note 3) | N/A |
+
+NOTE 1: The KPI values refer [66].
+
+NOTE 2: The accuracy fee control latency here is for communication one way latency from 5G IoT device to backend system while the distance between them is no more than 40 km i.e. city range. The command implementation needs 100 ms.
+
+NOTE 3: It is the typical connection density in today city environment. With the evolution from meter centralization collection to sockets in home directly collection, the connection density is expected to increase 5-10 times.
+
+## 5.3 Use case of Distributed Feeder Automation
+
+### 5.3.1 Description
+
+With the increased requirements for a more reliable, uninterrupted and continuous power supply, shorten the accident isolation time to milliseconds is required to support regional non-stop power services which makes severe challenges for the master station in centralized distribution automation.
+
+Therefore, intelligent distributed feeder automation has become one of the trends in the development of the power distribution grid. Its characteristic lies in the distributed sinking of the processing logic of the original master station to the intelligent power distribution terminal. Through the 5G communication among the intelligent power distribution terminals and distributed master station, intelligent judgment, analysis, fault location, fault isolation and non-fault area power supply restoration operations can be realized.
+
+In this way, the fault handling process can be fully automated, the fault scope can be restricted and fault handling time of the distribution network can be decreased from seconds to milliseconds.
+
+As illustrated in the Figure 5.3.1-1, the distributed feeder automation system is mainly composed of distributed master station, distribution monitoring terminal and the communication system. The distribution master station is mainly used for information gathering and human-computer interaction, and the distributed terminal is used for feeder status information collection, judgment, fault location, isolation and power supply restoration. The implementation result will be reported to the distribution master station. The communication system is to provide the communication link among the distribution terminals.
+
+The distribution master station is usually connected with the 5G system via wired or LAN which is out of 3GPP scope. Distribution master station manages multiple distributed terminals.
+
+Each distributed terminal here is served by 5G UE to exchange the collected data with other distributed terminals. And from application aspect, the communication between distributed terminals is peer-to-peer. The connection between the distributed terminal and the 5G UE is out of 3GPP scope.
+
+The 5G communication here should have high reliability. Therefore at least two communication links are usually deployed for hot standby or transmitting data synchronously between two distributed monitoring terminals. And it has the same condition between one distributed terminal and the distributed master station.
+
+
+
+Figure 5.3.1-1: Example of distributed feeder automation architecture. The diagram shows a central 'Distribution Master Station' connected to a central '5G' cloud. The 5G cloud is connected to four 'substation' units. Each substation contains a 'Switch station' and a 'Distributed Terminal'. The Switch stations are interconnected by solid black lines, forming a mesh. The Distributed Terminals are connected to the Switch stations by dashed red lines, representing 5G communication links. The legend indicates that dashed red lines represent '5G communication link' and purple icons represent '5G UE'.
+
+**Figure 5.3.1-1: Example of distributed feeder automation architecture**
+
+GOOSE protocol is a burst-based transmission application protocol used in Smart Grid. During the feeder system normal working phase, the heartbeat packet is periodic transmitted with 1s. When a fault occurs, it performs incremental periodic transmission with 2ms, 2ms, 4ms or 8ms time interval. After there is no sudden change in collected data, the heartbeat packet transmission of 1s is restored.
+
+In general, the feeder distributed terminals can be deployed along the overhead line or integrated in one power distribution cabinet per one square kilometre. These two topologies will require different communication density.
+
+Assumption of one CBD of a national sub provincial city, by calculating the load of various types of electricity consumption, it can be estimated the future power load in this area. Table 5.3.1-1 illustrates the typical estimated power load now and future in the area.
+
+**Table 5.3.1-1: the typical power load estimated in the CBD**
+
+| Growth rate | Now(2020) (MW) | Long future (2030) (MW) | Power load density (Now) (MW/km 2 ) | Power load density (future) (MW/km 2 ) |
+|-------------|----------------|-------------------------|------------------------------------------------|---------------------------------------------------|
+| High | 1043 | 1454 | 20.72 | 28.89 |
+| Middle | 1003 | 1348 | 19.93 | 26.78 |
+| Low | 952 | 1277 | 18.91 | 25.37 |
+
+Generally, one single urban medium voltage distribution line should not be separated exceed 4 segments, and the load of each segment should not exceed 1MW. So, for one single circuit 10kV distribution line, the line load should not be higher than 4MW (1MW\*4 = 4MW). In the medium level listed in the above table, the load density of the CBD area is about 20MW / km2, the number of 10kV lines per square kilometre can be calculated as follows:
+
+$$N = 20\text{MW} / 4\text{MW} = 5.$$
+
+According to the distribution network reliability configuration principle, one backup is required and the N will be 6.
+
+Considering the switches per segment and additional switches on the high voltage side, the number of required distribution terminal n can be calculated as follow:
+
+- Overhead line scenario: $n = 6 * (5+4) = 54$ .
+
+NOTE: "6" represents the number of 10kV lines per square kilometre, "5" is switches number per line, "4" is the number of the boundary switch which is installed on the high voltage side of the distribution transformer of each segment of the line.
+
+- Power distribution cabinets scenario: $n = 6 * (4 * 3 + 1) = 78$ .
+
+NOTE: "6" represents the number of 10kV lines, "4" means the number of distribution cabinet in one 10kV line. "3" is the number of switch including the boundary switch in each power distribution cabinet, "1" means every line end has a switch to monitor the line.
+
+In the future, when the power load density increases, or with differential protection utilized in the Feeder automation, more distribution terminals (e.g. more than 100) need to be considered.
+
+### 5.3.2 Pre-Conditions
+
+Typically, the distributed Grid can be divided into urban and agricultural parts. In urban area, the power load is relatively concentrated, and the distributed grid working environment is better. But in the agricultural area, the power service range is very large, while the distributed grid has to face so many issues e.g. a large number of harmonic sources, three-phase unbalance, voltage flicker pollution.
+
+Two 5G communication links are deployed for hot standby or transmitting data synchronously between UEs in distributed terminals and the network.
+
+### 5.3.3 Service Flows
+
+- 1) Data collection: The distributed terminal collects and reports related status information to the distribution master station or other distributed terminals in real time.
+- 2) Fault detection and localization: The distributed terminal collects fault signal from itself and neighboring terminals. Then it executes data processing and fault location logic, and judges the fault whether an instantaneous or permanent fault.
+ - a) When the distribution fault is an instantaneous fault, it will be skipped.
+ - b) When the fault is a permanent fault, the distributed terminal will locate the feeder fault based on the signals of each power distribution terminal. The upstream power distribution terminal of the node will continue to send status information, while the downstream power distribution terminal will not report the fault signal. Therefore, in the corresponding fault node, only one switch should send out the fault signal. According to this feature, when a feeder fault occurs, every distributed terminal could judge its position relative to the fault location.
+- 3) Fault isolation: When the fault node is determined, according to the preconfigured action order, all switches around the faulty node will be open to realize effective identification and isolation of the faulty area.
+- 4) Fault restoration: For the restoration of power supply in non-fault area, it is necessary to clarify the number and wiring of the switches it tied to, e.g. when a fault occurs in the cabinet of the one-in-two-out ring main unit, if two outgoing lines have isolated power-loss area. The related distributed terminals will reconstruct the power distribution structure, and close the tie switch, to restore the power supply in the power-loss area.
+- 5) Restoration confirmation: After the power supply is restored in the power-loss area, the system needs the distribution terminals report status information to determine whether the restoration is well done.
+
+### 5.3.4 Post-Conditions
+
+It can identify and shorten the power feed accident isolation time to milliseconds and support regional non-stop power services.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+The 5G system shall be able to provide connection service wherever the distributed terminal is indoor, outdoor, low and medium altitude, or underground.
+
+The 5G system shall be able to provide suitable APIs to enable application layer to monitor communication link status.
+
+The 5G system shall be able to provide at least two back up communication links between every IoT device in a distributed terminal and the network.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+[PR.5.3-001] The 5G system shall be able to provide required communication service according to KPI given in table 5.3.6-1.
+
+**Table 5.3.6-1: KPI for Distributed Feeder Automation (note 1)**
+
+| User experienced data rate (bit/s) | IoT device to 5G network latency (ms)(note 2) | Latency jitter (μs) (note 3) | Synchronicity budget requirement (μs) | Reliability % | Connection density | Coverage |
+|-------------------------------------------|------------------------------------------------------|-------------------------------------|----------------------------------------------|----------------------|--------------------------------------------------------------|-----------------|
+| 2 M-10 M | <10 | <50 | <10 | 99.999 | 54 /km 2 (note 4)
78 /km 2 (note 5) | |
+
+NOTE 1: The KPI values are sourced from [20]
+
+NOTE 2: It is the one way delay from a distributed terminal to 5G network.
+
+NOTE 3: The latency jitter is required for the switch off between the active and standby communication links
+
+NOTE 4: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre with the power load density is 20 MW/km2.
+
+NOTE 5: When the distributed terminals are deployed in power distribution cabinets, and considering the power load density is 20MW/km2, there are about 78 terminals in one square kilometre.
+
+## 5.4 Use case of line current differential protection in power distribution grid
+
+### 5.4.1 Description
+
+Line current differential protection (defined as 87L in IEEE C37.2-2008 [3]) has been widely used in electrical transmission systems to protect High-Voltage (HV) transmission lines. As a proven protection mechanism, it is also deployed for power distribution networks to protect (Medium-Voltage) MV distribution lines where applicable. The popularity of line current differential protection comes from the fast protection mechanism, reliability and the absolute selectivity of protected zones. Therefore, for Low-Voltage (LV) and MV power lines (both underground and overhead), current differential protection could be deployed easily with cellular technology without having to lay dedicated communication cables, either in refurbishment or new distribution substation construction projects.
+
+The mechanism of line current differential protection follows the Kirchhoff's current law, which is that the sum of currents at a junction of a circuit equals to zero. As illustrated in Figure 5.4.1-1, two protection relays deployed at two
+
+substations form the protection zone, within which the power line is protected from incidents such as short circuit. Each protection relay continuously measures its local current and transmits it towards the other. Each protection relay compares the locally measured current and the current received from the remote relay to calculate the differential current at a specific instant of time. Figure 5.4.1-1 shows two communication channels (illustrated as dashed arrow boxes) between the two protection relays. Here in this contribution the "communication channel" refers to the channel used for transferring the phase segregated current value data between the two protection relays. The current phasors from the two protection relays, deployed geographically apart from each other, should be aligned in time for the current differential algorithm to execute correctly. For Relay\_a, at a given moment the local current is $I\_a'\_Tx$ , and the time-aligned remote current from Relay\_b is $I\_b'\_Rx$ . Using them as input, the protection algorithm in Relay\_a derives the differential current. The same mechanism functions in Relay\_b. Whenever the differential current exceeds the threshold values as determined by the relay restraint characteristics, the relay will send a trip command to the circuit breaker (XCBR) to open the circuit, thus protecting the power line from being burnt down and any secondary damages a fireball blaze on the power line can cause.
+
+
+
+The diagram illustrates a power line protected by two substations. On the left substation, a circuit breaker (XCBR) is connected to a current transformer (CT), which in turn connects to Relay\_a. The local current measured by Relay\_a is labeled $I\_a'$ . On the right substation, a similar setup exists with XCBR, CT, and Relay\_b, with local current $I\_b'$ . A communication channel, represented by dashed double-headed arrows, connects Relay\_a and Relay\_b. Below each relay, two sinusoidal waveforms are shown. For Relay\_a, the top waveform is the transmitted local current $I\_a'\_Tx$ and the bottom is the received remote current $I\_b'\_Rx$ . For Relay\_b, the top waveform is $I\_b'\_Tx$ and the bottom is $I\_a'\_Rx$ . Red vertical lines indicate the time alignment of the samples. The voltage $Uu$ is also indicated for each relay.
+
+Diagram of Line Current Differential Protection by two protection relays (Relay\_a and Relay\_b), deployed in two substations. The diagram shows a power line connected to two substations. Each substation has a circuit breaker (XCBR) and a current transformer (CT). The CTs are connected to protection relays (Relay\_a and Relay\_b). The relays are connected to a communication channel (dashed arrow boxes) for transferring current data. Below each relay, there are two waveforms: the local current (I\_a'\_Tx or I\_b'\_Tx) and the received remote current (I\_b'\_Rx or I\_a'\_Rx). The relays compare these currents to calculate the differential current. The voltage (Uu) is also shown for each relay.
+
+**Figure 5.4.1-1: Line Current Differential Protection by two protection relays (Relay\_a and Relay\_b), deployed in two substations**
+
+The protection function of the protection relay depends on three things:
+
+- Sampling, buffering and transferring local current.
+- Receiving the sampled current values from the remote protection relay.
+- Time synchronization of the two protection relays - performing time-alignment of the locally buffered current samples with received remote samples.
+
+In terms of sampling, a protection relay needs to sample the local current periodically, and transfers sampled data within a pre-defined time period $T$ . In other words, the communication latency should not exceed $T$ . Max of $T$ is specified in IEC 61850-90-1 [4] to be between 5ms and 10ms, which infers the latency requirement for this use case. Secondly, once the buffered samples pertinent to the same instant in time are available, the relay must align them in time. As a relay needs to perform correct alignment of local and received data before calculating the differential current, the relay needs to know well enough when the remote relay transmits a specific data packet. Current clock synchronization is realized by relays attaching timestamps to measurement samples before transmission. A modern relay with an Ethernet interface normally needs to resort to IEEE 1588 Precision Time Protocol [5] for synchronization, since the relay assumes the Ethernet network to be non-deterministic.
+
+Regarding time alignment of local and received remote data, two methods exist, namely the method to use external time source such as GNSS, or "channel-based" alignment method. Due to various reasons in some smaller substations a GNSS receiver is not available. Even for a substation installed with a GNSS receiver, relays shall fall back to channel-based alignment for time synchronization, should GNSS become unavailable. For this reason, support of the "channel-based alignment" is the focus of the proposed use case.
+
+Different from GNSS-based alignment that is not adversely affected by communication channel asymmetry, the channel-based alignment is critically dependent on channel symmetry – near equal latency in transmission and reception directions between two protection relays respectively. Currently in the Smart Grid automation market, the max communication channel asymmetry is dependent on the chosen type of differential protection relay and is vendor-specific. For instance, an old-fashioned TDM-based differential protection relay is more sensitive to asymmetry than a modern type differential protection relay with an Ethernet interface. The latter can deal with asymmetry till 3ms, above which the relay will enter blocking mode. According to the IEEE C37.243 Guide [6], the asymmetry in terms of communication channel latency is around 2ms. From here on, focus is on how to satisfy channel-based alignment requirements using services from 5G system.
+
+#### Option 1:
+
+Per existing protection relay algorithm implementation, channel-based alignment presumes the delay in each communication direction to be (nearly) half of the RTT. If 5G system provides this condition, existing relay algorithm can be reused. According to IEEE C37.243 Guide, 2ms can be required as the max communication channel latency asymmetry between the two protection relays. Below are some additional details how protection relays performs channel-based alignment:
+
+Relay\_a attaches a timestamp to the transmitted measurement data, Relay\_b receives the timestamp from Relay\_a and re-attaches the same timestamp to the next out-going data packet towards Relay\_a. By receiving the original timestamp in return packet, Relay\_a determines the RRT by subtracting the present local time with the returned timestamp. Halving the RTT, Relay\_a obtains the amount of time shift/alignment it shall apply to the current samples received from Relay\_b. Therefore, it is required that the communication channel from Relay\_a to Relay\_b incurs near-equal latency as the channel from Relay\_b to Relay\_a. Following this approach, excessive communication channel asymmetry between Relay\_a and Relay\_b will lead to misalignment of currents (such as the $I\_b'\_Tx$ and $I\_a'\_Rx$ at Relay\_b in Figure 5.4.1-1), manifesting in phase shift. This will result in increase or decrease of the apparent differential current, causing blocking of the protection or in the worst case a false trip and further negatively impact Smart Grid availability and reliability.
+
+#### Option 2:
+
+Alternatively, instead of requiring the communication channels (from Relay\_a to Relay\_b, and from Relay\_b to Relay\_a) to be highly symmetrical regarding latency, a different approach could be proposed as a new 5G service to improve protection relay design by the Smart Grid OEMs. To achieve the same goal as for Relay\_a to know how much it needs to time shift the received current samples from Relay\_b to align with its local current, it is sufficient if the 5G system could provide such a protection relay with the latency of the relevant communication channel (latency from Relay\_b to Relay\_a for Relay\_a, and latency from Relay\_a to Relay\_b for Relay\_b) with good confidence/precision. This provided latency value could either be estimated or assigned by the 5G system. In this way, the channel latency information is directly provided to relays by the 5G system, a protection relay does not need to carry out its own estimation. This could open new possibilities for the protection relay manufacturers to design new and possibly simpler time-alignment algorithms.
+
+#### Option 3:
+
+Using the existing IEEE 1588 time master of the NG-RAN. In this case, the complexity could be the use of the IEEE 1588 power/utility profile (a.k.a. IEC 61850-9-3 [7]) instead of using the telecom profile.
+
+### 5.4.2 Pre-conditions
+
+Typically in a distribution grid, a MV power line transmits electricity between two substations. Two protection relays are installed at both ends of the power line. Relay\_a continuously samples and measures the local current $I\_a'$ and sends it to Relay\_b, so does Relay\_b.
+
+### 5.4.3 Service Flows
+
+- 1) Relay\_a samples local current values $I\_a'$ , stores them locally and sends them to Relay\_b periodically. Timestamp is attached to the sampled values to help Relay\_b match the data correctly.
+- 2) Relay\_b samples local current values $I\_b'$ , stores them locally and sends them to Relay\_a periodically. Timestamp is attached to the sampled values to help Relay\_a match the data correctly.
+
+- 3) Relay\_a receives samples from Relay\_b within the latency required by IEC 61850-90-1. Depending on the applied voltage levels, the max allowed latency is between 5ms and 10ms. Relay\_a stores the received samples in a local buffer.
+
+Relay\_b receives samples from Relay\_a within the latency required by IEC 61850-90-1. Depending on the applied voltage levels, the max allowed latency is between 5ms and 10ms. Relay\_b stores the received samples in a local buffer.
+
+- 4) Inside both Relay\_a and Relay\_b, a microprocessor decides that all the relevant data for a same instant in time are collected. The Relay then aligns these data and uses the algorithm to calculate the differential current for this time instant.
+- 5) Differential current calculated at both Relay\_a and Relay\_b stays in the restraining region (below threshold). None of the relays trips. The system continues to function in normal condition.
+- 6) (Example incident) Suddenly, a strong wind blows down a tree branch, which during the fall with its additional weight brings down the overhead distribution line close to the ground. The voltage of the power line causes an electric discharge with objects on the ground, causing spark leakage. This discharge causes current from both substations to flow with increased magnitude into the power line.
+- 7) Since both the relays are still measuring the current and sends the sampled values to each other. Relay\_a detects from a very instant in time, the differential current exceeds the threshold. Relay\_a triggers a trip signal to the connected circuit breaker.
+- 8) Circuit breaker opens, stops current from flowing into the power line to cause more serious damage.
+
+### 5.4.4 Post-conditions
+
+The abnormal condition of the power line in the protected zone is duly isolated from the electrical grid.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+The communication mechanism is partly covered by existing 5G functionalities. Support of IEEE 1588 PTP is an existing feature. Additional traffic from running IEEE 1588 PTP is around 0.004 Mbit/s. In TR22.804 [8] there is attempt to touch upon the similar case, where the clock synchronization accuracy $\leq 10 \mu\text{s}$ , and latency requirement is 15 ms.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+[PR.5.4-001] The 5G system shall support an end-to-end latency of less than 5 ms or 10 ms, depending on the applied voltage level. Here the end-to-end latency is between two UEs including two wireless links.
+
+[PR.5.4-002.option1] The 5G system shall support communication channel symmetry in terms of latency (latency from UE1 to UE2, and latency from UE2 to UE1) between the two relays, with the max asymmetry $< 2 \text{ ms}$ .
+
+[PR.5.4-002.option2] The 5G system shall provide a UE with communication channel latency from the remote UE, with an accuracy of the provided latency $< 1 \text{ ms}$ .
+
+[PR.5.4-002.option3] The 5G system shall provide the protection relay with timing information with the comparable precision as GNSS-based precision. The IEEE 1588 time master in NG-RAN should provide protection relays with IEC 61850-9-3 based power/utility profile
+
+## 5.5 Smart Energy Differentiated QoS For Transported Encrypted Data
+
+### 5.5.1 Description
+
+This use case describes a common need of Utilities with diverse substations that require communication. Diverse services' communication traffic need to be aggregated over a communication service in an encrypted form. This would prevent the 3GPP system from inspecting the traffic to identify and classify it (either in the downlink or uplink.)
+
+The services that are listed in this section – Advanced Metering Infrastructure (AMI), Distributed Automation, Demand Response (DR), Distributed Generation (DG), Power Line Differential Protection are the 'classic Smart Grid services'. These are distinct from the services described in other sections that offer more advanced architectures. A single table of QoS values is provided in clause 5.5.6, with notes added to call out differences where they exist.
+
+### 5.5.2 Pre-conditions
+
+A Distribution System Operator (DSO) "U" receives telecommunication services from a MNO "T". U has deployed 100s to 10,000s of substations that generate service traffic of diverse criticality, QoS requirements, etc. U has arranged, via service level agreements (SLAs) specific QoS treatment for these different classes of service traffic with T. The use case focuses on a particular substation "S" and its communication by means of T's 3GPP network, to connect multiple services of different nature and traffic patterns, multiplexed over a single WAN connectivity.
+
+### 5.5.3 Service Flows
+
+S establishes sessions with the T's network. S appears as a UE to the 3GPP system. Behind S is a local network (in the substation). S serves as a router to the traffic in that network. S is able to categorize the traffic into different classes, each requiring distinct QoS treatment in the 3GPP system. S encrypts the traffic uplink, using an end to end encryption with the service termination in the DSO's network.
+
+
+
+Diagram illustrating Multiple End-to-End QoS Flows from Substation to DSO Service Network. On the left, a 'Substation' box contains four colored ovals: OAM (red), AMI (purple), DA (cyan), and Security (Video+) (yellow). These are connected to a 'Router' (pink rectangle) which is connected to a 'UE' (pink rectangle). The UE is connected to a '3GPP System' (grey box). From the 3GPP System, four colored lines (red, purple, cyan, yellow) enter a cloud labeled 'PDN'. Inside the PDN cloud, there is an 'MPLS network' (blue box) with two routers. The lines exit the MPLS network and enter another 'Substation' box on the right. This box contains the same four colored ovals: OAM (red), AMI (purple), DA (cyan), and Security (Video+) (yellow).
+
+**Figure 5.5.3-1: Multiple End-to-End QoS Flows from Substation to DSO Service Network**
+
+Downlink flows are also encrypted and characterized in such a way as that the 3GPP system handles the traffic with the appropriate QoS.
+
+Instability of the connection with primary subscription could be an additional, more specific, KPI although this can be part of Availability KPI. This KPI will be measured by means of the number of Service Availability Failure Events (that is, the availability of the service could not be maintained beyond an acceptable threshold.) Another way of describing these failure events is as Fallback events carried out by the Dual SIM cellular device, where the UE employs the 'secondary' subscription (USIM) in order to achieve continual service when the primary service is not available.
+
+This 'Service Availability Failure Event' metric is measured over a period of time, e.g. over the preceding month and accumulated during the last year.
+
+### 5.5.4 Post-conditions
+
+Traffic is delivered by the 5G system to support U from and to each S as required by the SLA. The traffic confidentiality is maintained.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 clause 6.7.2:
+
+The 5G system shall allow flexible mechanisms to establish and enforce priority policies among the different services (e.g. MPS, Emergency, medical, Public Safety) and users.
+
+NOTE 1: Priority between different services is subject to regional or national regulatory and operator policies.
+
+The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service.
+
+The 5G system shall be able to support a harmonised QoS and policy framework applicable to multiple accesses.
+
+The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
+
+NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
+
+A 5G system with multiple access technologies shall be able to select the combination of access technologies to serve an UE on the basis of the targeted priority, pre-emption, QoS parameters and access technology availability.
+
+TS 22.261 clause 6.8:
+
+Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration.
+
+TS 22.261 clause 6.10.2:
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
+
+TS 22.261 clause 8.2:
+
+The 5G system shall provide integrity protection and confidentiality for communications between authorized UEs using a 5G LAN-type service.
+
+The 5G system shall provide suitable means to allow use of a trusted third-party provided encryption between any UE served by a private slice and a core network entity in that private slice.
+
+The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a non-public network and a core network entity in that non-public network.
+
+Smart Grid services specified by IEC generally are defined only at layer 7. This means there are no defined KPIs for lower layer implementation. These values are determined through measurements and analysis. The research is already some years old. The bandwidth requirements are known to be increasing with time, as more services are added and services are deployed more extensively.
+
+Specific QoS for different services is included in this section as it clearly corresponds to needs by Smart Grid. The following KPIs can be supported by existing requirements.
+
+**Table 5.5.5-1: KPIs for Smart Energy Services**
+
+| Service | Bandwidth (kbit/s) | Latency | Availability (%) | Density #customers/ km 2 | Coverage | Power supply backup (note1) |
+|------------------------------------------------|------------------------|--------------------------------------------------------|------------------|---------------------------------------------------------------------------------|----------|-----------------------------|
+| Advanced metering infrastructure (AMI) (note2) | 10-100 | 2-15 s | 99-99.99 | Minimum density 0.00136
Average density 106.56371
Max Density 22937.78217 | | Not necessary |
+| Advanced Metering (5.2.6) | UL: <2000
DL: <1000 | <100ms
fee control <3000
general data collection | 99.99 | 10 5 | | - |
+
+| | | | | | | |
+|--------------------------------------|-----------|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------|
+| Distribution Automation (DA) (note3) | 9.6-100 | 100 ms – 2 s | 99-99.99 | Concentrated rural
70.79562
Dispersed rural
Semi-urban
7.63437
Mandatory rural support
0.04765
Urban
11.02120 | | 24h-72 h |
+| Demand Response (DR) | 14-100 | 500 ms – several minutes | 99-99.99 | TBD | | Not necessary |
+| Distributed Generation (DG) | 9.6-56 | 20 ms – 5 min | 99-99.99 | TBD | | 1 h |
+| Surveillance (5.14.5) | 3000-5000 | (note4) | (note4) | 100/km 2 | <40km (city range) | - |
+
+NOTE 1: The Power supply backup KPI is provided for background information and a deployment issue.
+NOTE 2: AMI referred to in this section is for remotely reading meters in real time
+NOTE 3: DA referred to in this section uses a centralized architecture.
+NOTE 4: The latency and availability of surveillance data can be compensated by local storage on-site. Therefore, no KPIs are given in the table.
+
+These values are given in [1] cited from [2] and [3].
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+Specific QoS for the Distributed Automation (DA) service due to its extreme availability requirements is included in this section as it clearly corresponds to needs by the Smart Grid.
+
+**Table 5.5.6-1: KPIs for Smart Energy Services**
+
+| Service | Bandwidth (kbit/s) | Latency | Availability (%) | Density #customers/km 2 | Coverage | Power supply backup (note 1) |
+|---------------------------------------|--------------------|------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------|------------------------------|
+| Distribution Automation (DA) (note 2) | 9.6-100 | 100 ms-2 s | 99.999 | Concentrated rural
70.79562
Dispersed rural
Semi-urban
7.63437
Mandatory rural support
0.04765
Urban
11.02120 | TBD | 24h-72 h |
+
+NOTE 1: The Power supply backup KPI is provided for background information and a deployment issue.
+NOTE 2: DA referred to in this section uses a centralized architecture.
+
+These values are given in [1] cited from [2] and [3].
+
+Smart Grid services specified by IEC generally are defined only at layer 7. This means there are no defined KPIs for lower layer implementation. These values are determined through measurements and analysis. The research is already some years old. The *bandwidth requirements* are known to be increasing with time, as more services are added and services are deployed more extensively.
+
+[PR 5.5.6-001] The 5G system should support a KPI associated with the "stability of the connection with a PLMN associated with a subscriber" as a more specific KPI (although this can be part of Availability KPI.) This KPI shall be measured by the number of Service Availability Failure Events (where availability cannot be maintained as required) during a time period, as specified in the service level agreement.
+
+## 5.6 Service Lifetime for Utility Communication Services Deployments
+
+### 5.6.1 Description
+
+Energy infrastructure deployment occurs within a context where there is an expectation regarding service lifetime. The process of creating civic infrastructure requires significant oversight and consideration, and aims at long term solutions. This is true for all components of the energy system – generation, transport, distribution and customer premises components. The energy system is vast, so serviceability has to be considered so that the overall components require as little manual repair and maintenance as possible. Electrical infrastructure as a whole is meant to serve for multiple decades. Like physical civic infrastructure, utilities are mandated to target long term stable communication infrastructure that serve the public interest over an extended period of time. The service lifetime of diverse components are so long that newly deployed equipment must always consider interworking with legacy deployments.
+
+Communication components of the energy system are no exception. Some communication services were deployed decades ago and continue operation (e.g. legacy teleprotection using copper wires as telecommunication.) In general, energy system communication services are defined at the application layer (e.g. by IEC). The role of the communication service is to carry these protocols with sufficient performance (throughput, reliability, maximum latency, jitter etc.) While it is possible to change communication infrastructure while maintaining the same services, this is done gradually. The communication infrastructure components are deployed with the intention that they will serve for an extended period of time – often decades, *the same time scales as the energy system components expected lifetime*. If more communication capacity is needed, this is added incrementally for new services, with attention paid to reduce change for existing components operation as much as possible.
+
+The telecommunications system standardized by 3GPP supports backwards compatibility. There is a very strong commitment to support of legacy terminals. Cell phones from the mid-90s can still operate today. At the same time, the standard moves quite quickly (from an energy system perspective) with new 'generations' every decade – using different spectrum, radio protocols and networks. With 5G, service continuity and interworking with 2G and 3G has been discontinued, except for a few capabilities (e.g. 5G to 3G service continuity.) For energy infrastructure planning purposes, the 3GPP system needs to support long (e.g. 30-40 year) service lifetimes, in which terminals will be in continuous operation. The percentage of M2M-type operational services over 4G today is very low today, compared with the use of 2G and 3G.
+
+Some features have been developed in 3GPP to facilitate backwards compatibility at different layers of the system. For example Dynamic Spectrum Sharing (DSS) in 5G allows different 3GPP RATs to coexist in the same carrier. This can facilitate migration or preservation of legacy radio technology.
+
+The 'deployment' use case below considers these aspects from the perspective of a utility system operator. Unlike many use cases, this takes place over years.
+
+### 5.6.2 Pre-conditions
+
+Volt, a publicly traded utility company, operates the electrical transport and distribution network in more than one country. Interest in and regulatory requirements for Smart Grid services grows, and with it the demand for communication services. The existing communication infrastructure that Volt has deployed will become insufficient in the future, so Volt plans for deploying additional capacity. The target is to deploy communications equipment that will operate for 30-40 years. There are many technologies that Volt could choose for infrastructure, among them 5G standards. These technologies could be the basis for the utility private infrastructure, or could be used as a service if provided through a MNO. The entire process of planning, acquisition and deployment itself takes several years, but it has begun.
+
+### 5.6.3 Service Flows
+
+Volt identifies particular communication services to be addressed with LTE access to a 5GC, completes the evaluation, approval and investment process and begins to deploy. From the time that the planning started until deployment beings, five years have elapsed.
+
+Some components of the system are 'IoT' sensors – in the transport and distribution system. These sensors are often deployed in locations that are inaccessible, where physical replacement would be unduly expensive. The overall
+
+planning and expectation is that these terminals will be in service for 35 years. (That is 40 years since the planning process began.)
+
+The years go by, and Volt's 5G communication infrastructure continues to function. As 8G standards emerge on the market, Volt begins to consider how to replace that infrastructure – the 5G IoT sensors and other communications equipment deployed earlier. Some of the 5G components are not going to be supported by the new communication system (including integration of the 8G network with 5G networks, for example, due to the need for greater system security.)
+
+### 5.6.4 Post-conditions
+
+Volt has successfully operated their energy utility services, relying on 5G communication services, for over 35 years. They begin to deploy 8G technology fully expecting this to remain in operation until 2100.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+Though not formally stated in 3GPP, successive releases and indeed changes to any release after it has been frozen, avoid incompatible changes. Any change, for enhancement, correction or simplification of the standards based system occurs only after comprehensive review and acceptance by the community of stakeholders. This expresses 3GPP standards' commitment to and emphasis on backwards compatibility.
+
+Each generation includes comprehensive support for diverse telecommunications services. The degree of integration and service continuity offered by 2G through 4G was extensive. With 5G the compatibility has been reduced. This however does not mean that a 2G, 3G or 4G system cannot be operated at the same time as the 5G system, to maintain support for existing services. However, realistically, MNO access to spectrum and the efficient use of it, make it suboptimal for operations to maintain diverse legacy access networks. Utility equipment (routers and switches in operation) are therefore subject to different decisions to be taken by the different MNO's in the different world regions where Volt operates.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+None.
+
+## 5.7 Remote DSO management of connectivity for Smart Energy
+
+### 5.7.1 Description
+
+5G is expected to provide a highly reliable platform for communications. Requirements for industrial automation and URLLC (e.g. in TS 22.104) are extremely high and appropriate for connectivity for Smart Energy. However, network incidents could happen and the scenario in use case below may mitigate the impact of such a failure to further increase the system reliability.
+
+It is important to emphasize that this use case is not theoretical. There are many substations around the world that use 3GPP access for communication services in more or less ad hoc fashion (where management interfaces between the 3GPP system and the DSO are not standardized.) This use case focusses on how 5G can provide service to DSOs as well.
+
+A DSO has many, e.g. 100s to 10,000s of substations. These substations are managed from operation centers typically referred to as control centers.
+
+
+
+Diagram illustrating Remote DSO management of connectivity for Smart Energy. On the left, a box labeled 'ACCESS - X0,000' contains a 'Switch' connected to five services: Service 1: Remote metering, Service 2: Automation, Service 3: MV Superv., Service 4: LV Superv., and Service 5: Any other. A thick red line represents the termination of communication outside the substation. A green line labeled 'SS' connects the switch to a green box on the right labeled 'PLC LV'. Inside the PLC box, there are several small icons representing devices, and a label '-Millions' is present.
+
+**Figure 5.7.1-1: Remote DSO management of connectivity for Smart Energy**
+
+Within the substation there are many services (shown here remote metering, automation, MV supervision, LV supervision, etc.) In addition, there are power line communication links beyond, to customer premises equipment, that increasingly will spread the reach of IP services up to the smart meters. The thick red line represents the termination of communication outside the substation. For 3GPP telecommunication services supporting the DSO, the model of the interface between the switch and the network can be considered a 5GLAN service.
+
+The actual topology between substations is more complex than shown, since there may be several communication services (back up links to provide greater reliability, etc.) For the purposes of this use case this is not considered further.
+
+The traffic from the diverse services in the substation is aggregated before it leaves the switch and may be encrypted – the 5G system will not see the individual service flows. Of particular importance to the DSO is the interface exposed by the switch. Information about *this* from the mobile network that has proved very important in the past.
+
+Previous generations of 3GPP systems, as deployed, did not effectively achieve high availability.
+
+There are different alternatives to achieve high availability that a DSO might choose. This use case focuses on one of the alternatives: closely monitoring actual performance. This is a way to enable DSOs to respond to possible future problems proactively. DSOs can troubleshoot more effectively. DSOs can continue service in the case of reductions in performance due to a number of factors. To identify these problems proactively, obtaining sufficient information about configuration and radio operation has been the key to identifying 'communication health' by the DSO, so as to identify patterns that result in poor performance and be able to react in a timely manner before communications performance declined to an inadequate level, e.g. by activating alternative access options to the 3GPP access whose performance shows signs of decline.
+
+It is important to note that for the purpose of this use case, the UE that is considered is the devices that connects the substation network to the DSO's network, not any UE (e.g. a smart phone, or IoT device.) Nevertheless, it is seen by the 5G system as a UE.
+
+Specific information that is required includes UE information, Connectivity status including QoS parameters, and session status information including user plane performance and fault information. Specific events should trigger a notification to the DSO from the MNO in a timely manner. Utilities (DSOs) can choose to rely on 3GPP technologies to enable telecommunications connectivity for mission critical services and sites. These technologies are used to connect endpoints (Substations) and a set of different Smart Grid traffic flows by means of a device with cellular WAN access.
+
+As with any other type of telecommunications networks, the connectivity status and performance management information must be available.
+
+In the event of an incident affecting the MNO's network, utilities need to be notified in a timely manner regarding the potential communication performance failure, so that a DSO can take proactive measures such as switching to an 'alternative' connection. This information could be predicted future events related to possible communication service degradation (derived from information exposed by an operator's network analytics), or it would be some additional information identified in close correlation with communication service degradation. The latter is the approach described further. This use case shows how an interface could deliver this information that could provide network management information to be accessible to utilities in a manageable way.
+
+### 5.7.2 Pre-conditions
+
+A DSO "U" has a service contract with a MNO "A" and MNO "B" to provide telecommunication service to U's substations. (U has *more than one* service contract in order to increase the *redundancy* and to achieve greater coverage, as a means of achieving higher availability.)
+
+The requirements described in clause 5.7.6 below do not depend on there being 2 USIM contracts. There is no interaction or communication between the two MNOs (A and B) implied by this use case.
+
+U has shared parameters for delivery of information (e.g. monitoring and alarms) with A and B in advance from a standard set of them grouped in a SNMP MIB or any similar standard artefact offering the needed functionality, and established standard communication interfaces (e.g. APIs) that allow secure and highly available exchange of management data between U and A and B. The parameters and the communication interface must be standard for all MNOs and DSOs be able to receive a consistent service in the different world regions independently of the service provider.
+
+In the following text IT management is discussed to motivate the management requirements and to explain the need. There is no intention however to require IT management at the process level be supported by 3GPP standards. Nor does this use case imply exposure or integration of IT management processes of the DSO or MNO.
+
+The smart energy applications motivating this use case are distribution automation and distribution / substation automation applications involving supervision, control and data acquisition in order to recover from or avoid communication problems in substations. Though the availability requirements of these applications can be met by the 5G system, taken as an aggregate of several applications in a substation with critical importance to the energy system, the availability has to be extremely high. This is because the consequence of failure is severe – in terms of loss of business productivity and even risk of human life in a power outage. A DSO faces severe regulatory penalties in the event of outages that could be prevented.
+
+The following IT processes are in place in U's network. Specific IT management objectives require timely and sufficiently detailed input. The processes that most concern this use case are Incident Management, Change Management and Service Configuration Management. These services are defined in [12]. The processes discussed in this section occur within the DSO network. Though there is no doubt a parallel set of processes within the MNO network, these are (aside from incident reporting and management data acquisition by the DSO network) out of scope. This may surprise the reader, but the reasons are the following.
+
+- 1) It is the IT process requirements of the DSO that motivate the exposure of information by the MNO.
+- 2) Though the details of the IT processes of both DSO and MNO are not matters of standardization, the interface between the two must be considered. If the DSO needs to employ different management standards with each communications provider, this increases complexity and the lack of standards based management interfaces constitutes a significant drawback when considering whether to employ and integrate services over a particular communication system.
+
+Incident Management [13] is a process that can be triggered by a customer upon reporting an issue or raised automatically by an event monitoring system. Incident records correspond to the reported or raised event. It is vital to link incident management records to link them to Configuration Items (maintained in a database by means of the Configuration Management process [14].) A set of incidents may also motivate a Change, according to the Service Asset and Change Management Process [15].
+
+Configuration Management is particularly important for the DSO, since they must track the total configuration of all essential systems, especially any change that occurs to components that could cause a system failure. Each item in the IT system is identified and has a controlled configuration that can be verified and audited. This allows other processes to be automated and the complete IT status to be taken into consideration in real-time, e.g. during an incident. If some components of the IT system are outside of the control of the DSO, the configuration of these must however remain constantly known. Any change to the configuration of these components requires notification to the DSO as it could possibly trigger an incompatibility with other configuration.
+
+Change Management provides a process with significant oversight (record keeping and authorization), ability to undo the change if required through the linked process of Release Management, and an evaluation of the consequences of the change. It is particularly important that it is unacceptable under the Change Management regime that changes occur without passing through the process. For example, if a UE were to change the terms of its contract and service, or its
+
+SIM card and its configurations without going through the Change Management process this would be considered an Incident, resulting in immediate actions by DSO, and possibly further interactions with MNO.
+
+The delivery of relevant information would be part of the service level agreement between the DSO and MNO. The information required by the relevant interfaces are listed below at a high level. A further analysis of the details of these requirements and how to fulfil them is out of scope of stage 1 specification.
+
+In a DSO network operation center for U's distribution services, a technician "Fred" observes a number of substation local area networks, ready to detect and resolve any sign of trouble that arises. Supplementing the DSO's network management information, the MNO exposes management data to enable Fred to properly respond to failures in the DSO network.
+
+U uses a Dual SIM router which is configured to use MNO A as primary in normal conditions, failover mechanism to B is enabled so that standby connection can be triggered in the event of complete loss of connection or quality of connection below thresholds.
+
+Utility DSO U's NOC (Network Operating Center) will perform efficient and effective monitoring of Smart Grid assets connectivity and incident resolution if it can rely on trustworthy information coming from the following sources:
+
+- Health Check platform to monitor availability of the connection
+- Performance Check procedures to monitor that performance levels are above required thresholds
+
+NOTE 1: Failure of the Health Check or Performance Check will trigger the Incident Management process.
+
+- Accurate and updated Inventory to geographically locate the Cellular connection (USIM) at a specific Smart Grid asset (typically Substation)
+- Real time Access to MNO's SIM card Management and operation platforms (lifecycle control, i.e. whether the subscription is active, suspended, in 'test' mode, deactivated, etc. APN configuration,)
+- Information provided by the MNO on a timely manner and related to radio access, for example RAT type and CellID.
+
+NOTE 2: The timeliness requirements for monitoring depend upon the circumstances of the deployment. An example granularity for monitoring information is once per minute. This has proven sufficient in many deployments, but others with greater observed variation in performance could require greater granularity, e.g. every 30 seconds.
+
+NOTE 3: The information provided for inventory, SIM platform configuration and cellular control plan operational parameters could be required for the Configuration Management process.
+
+The usage of this data as a combined input to a single utility-owned "Monitoring and Management" (M&M) platform are instrumental for the DSO to make decisions and start actions that will impact the availability of the Smart Grid and, thus, the final service delivered to its customers. The utility DSO counts on a dashboard to represent the most relevant KPIs to the connectivity health status of the Substation switches and routers, to monitor the stability of the connection and the quality of the service delivered by the MNO.
+
+
+
+Figure 5.7.2-1: A DSO-MNO Management Model diagram. The diagram shows two main entities: DSO (top) and MNO (bottom), separated by a dashed line labeled 'Standardized interfaces'. The DSO contains an 'M&M Platform' with three components: 'Alarms Panel', 'Report Generation', and 'KPI Dashboard'. The MNO contains a 'Service Desk' and 'MNO OAM'. Arrows show data flow: 'incident' from Alarms Panel to Service Desk; 'incident' from Service Desk to M&M Platform; 'request configuration' from KPI Dashboard to Service Desk; 'report configuration' from Service Desk to KPI Dashboard. To the right, 'DSO internal interfaces' connect the M&M Platform to 'Inventory', 'Performance Check', and 'Health Check'.
+
+**Figure 5.7.2-1: A DSO-MNO Management Model**
+
+The elements in this model are explained below.
+
+The KPI Dashboard in the figure above contains information regarding the
+
+- **Connectivity status** of the UEs and their status with respect to their service with the MNOs A and B. Inputs: volume of data consumption per substation and MNO A. Output: check whether expected traffic levels persist. If there is a massive failure to achieve KPIs, Fred (U) can switch to use the other MNO B. This permits detection of failure in a way that avoids massive incidents (part of the Incident Management process.)
+- **Stability** of service of the UEs in terms of their mobile telecommunication service.
+
+NOTE 4: Determination of which specific parameters should be exposed is out of scope of the present document.
+
+Configuration is another aspect of stability. Any change to the service configuration (as agreed between U and MNOs A and B) needs to be reported. In addition, U needs to be able to request the configuration information. (This is an essential part of the Configuration Management process.)
+
+- **Performance** determines if the mobile telecommunication network continues to perform as expected. U checks the performance by means of network tools, based on ping packets being sent (this increases traffic used over the connection with A and B.) This information is combined with AAA events (e.g. registration and deregistration with networks.) Output: Information on average performance indicators is obtained, including latency, packet loss rates, per technology. (This is an essential part of the Service Level Management process, not considered further in this use case.)
+
+NOTE 5: QoS performance that becomes acutely inadequate constitutes a service failure incident. This is dealt with in a separate use case.
+
+#### Report Generation
+
+Reports from U are provided to A and B on a monthly basis. U expects a certain quality of service delivered by A and B. The achieved service levels are tracked and presented in the report. If A or B do not comply with the service level agreement, actions are specified in the SLA (and these are out of scope of this study.)
+
+A DSO might request the following to be included in the report:
+
+- (1) Network performance (latency and packet loss above threshold),
+- (2) Network stability (the connection remains stable over time),
+- (3) Accumulated alarms arising due to the MNOs network (e.g. massive or isolated RAN issues.)
+
+NOTE 6: The list above is an example only. The specifics of report generation of is out of scope of the present document.
+
+#### Alarms Panel
+
+Alarms can be triggered so that incident's responsible parties are informed in real time and the remediation actions and/or escalation processes can be initiated. Alarms are reported by U to A and B as part of the Incident Management process. Incidents may be of the following forms (this is not an exclusive list):
+
+- Massive incident where all UEs connectivity is affected whose SIM cards are provided by A or B.
+
+NOTE 7: An incident reported by U to A or B could be caused (at least in part) by incidents in a single access point.
+
+### 5.7.3 Service Flows
+
+The service flows below are examples of typical situations encountered by "Fred", a technician at Utility U's Network Management Center (NMC), to illustrate the normal operation and maintenance processes (with emphasis on Change Management, Incident Management and Configuration Management):
+
+- 1) Fred is checking M&M "KPI Dashboard" and, while looking at the Weekly graph of Connectivity status, he notices a sudden drop of accumulated traffic consumption of MNO A and a sudden increase of MNO B traffic. At the same time at "Alarms" panel there is an incoming alarm informing of a Massive event. An automatic ticket is created to MNO A and the counter of massive events is updated to be reflected in the next SLA monthly report to track MNO A's quality of service.
+- 2) Fred tries to remotely perform a firmware upgrade to the Substation Automation unit and, after a couple of unsuccessful attempts, notices that the firmware upgrade cannot be fully completed because the connection is unstable. Fred checks the Stability graph on "KPI Dashboard" for this particular Substation code and confirms that there is a recurring cell roaming of MNO A's SIM card during the last 12 hours. Fred accesses remotely to the cellular router that is providing cellular access to the substation Automation units and provokes a failover to MNO B. This turns out into a stable connection which enables a successful completion of firmware upgrade process. At the same time, he checks the "Alarm panel" and confirms that a notification has been sent to the MNO A because this bad behaviour has been happening for the last month.
+- 3) Utility U is embarked in the renewal of electric MV cables of a group of 10 Substations located in the proximity of "Main Convention centre". These Substations are using BPL (Broadband PLC over Medium Voltage) as the main backhaul connection with failover to cellular backhaul in case of main connection failure. Fred observes that the backup cell communication with MNO A for the 10 Substations is working, though runs unstably. Fred checks the "Dashboard KPI" Performance graph and confirms that the Substations' cellular connections have high latency and packet loss rate during day working hours for the last two weeks. At the same time, after checking Stability graph on "KPI Dashboard" Fred confirms that the USIM cards in the 10 Substations also present constant technology roaming from E-UTRAN service to UTRAN service. This issue has been affecting hourly smart meter readings. Fred remembers that there has been an Automobile Fair at the Convention centre in the last two weeks that might have affected the Radio resources available at the eNodeB. He checks the alarms and sees that there has been an alarm sent to MNO A to report on Service Quality degradation. This alarm triggers an auditing process lead by MNO's radio team in order to increase the capacity of 2 specific sectors of 1 eNodeB serving the Convention centre area. (This is an example of a performance based trigger for Change Management as part of the overall Service Level Management process between U and A.)
+- 4) While analysing MNO A's monthly SLA report, Fred observes that the average latency of all connected SIM cards has dramatically increased in the last two months from an average of 200 ms up to 630 ms. Furthermore, there has been an accumulated amount of 10 massive incidents in the last month. This information is instrumental to contact MNO A that was aware of the massive incidents but was not of the increase in latency. In order to solve it the MNO takes appropriate action.
+- 5) While monitoring the Performance graph on "KPI Dashboard", Fred observes high packet loss rate affecting all connected Substations through MNO B. This issue is starting to affect the smart meter reading rates. Fred promptly opens a ticket to MNO B (as part of the Incident Management process.)
+
+Alternatively, if B detects a problem in their network that will degrade service levels in U's network, B will use a standard mechanism to raise an alarm in U's network. This will alert Fred, who will note that there is already an open ticket related to the incident, as well as other data associated with the service degradation.
+
+- 6) MNOs A and B have recently informed DSO "U" about the imminent phase out of 3G services at national level. They inform about the process timeline which is planned to start in the next 6 months to be fully completed along one year starting in urban areas. Fred has been designated to coordinate the remediation activities that will avoid MNO's network operations to affect DSO U's Smart Grid operations. Fred checks "KPI dashboard" in "M&M platform" to do a first evaluation of the dimensions of the situation. The accumulated graph per technology and frequency band for each MNO shows that there are 20,000 substations currently connected by means of Cellular 3G. "3G remediation" project definition starts. (This is an example of the Change Management process informed by Configuration Management and performance data.)
+- 7) "3G remediation" project requires DSO "U" to undertake both field and administrative operations. Field operations will consist on replacing cellular devices and SIM cards of MNOs A and B all over 20,000 substations. Inventory information of SIM cards' location available on "M&M" platform allows to efficiently coordinate field operations. (Configuration Management is needed during Release Management process. The release management process is not discussed further in this use case.)
+- 8) Administrative operations consist on provisioning 20,000 new generation technology SIM cards of both MNOs A and B. "M&M" platform will enable a single interface of operation which will make the task more efficient and straightforward than it was before when provisioning had to be performed by means of two separate MNO's Web Portals. This is possible thanks to the fact that SIM card parameters (APN, status, IP, Subscription group, etc.) for both MNO's A and B are standard, delivered through the same API definition. This allows an easy integration of all MNO information into a single operating platform. (This is an example of Configuration management processes making use of standard interfaces.)
+
+### 5.7.4 Post-conditions
+
+U is able to work to maintain and improve the services they provide to their customers both during incidents and over time as part of Incident Management and Change Management processes. U is able to report incidents to A and B with standard mechanisms and content that will help the identification and solution of it with less effort and time. A and B receive input from U and is able to improve and maintain their service quality. A and B provide notifications to U regarding changes *for selected components* (e.g. specific UE aspects) to status and configuration (both long term and every time that specified components change) as per their service agreement. A and B can inform U of service changes in advance. A and B inform U when an incident occurs by means of standards based mechanisms.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 clause 6.10.2:
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party.
+
+The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide the 3GPP network via encrypted connection with the expected communication behaviour of UE(s).
+
+NOTE 1: The expected communication behaviour is, for instance, the application servers a UE is allowed to communicate with, the time a UE is allowed to communicate, or the allowed geographic area of a UE.
+
+The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide via encrypted connection the 3GPP network with the actions expected from the 3GPP network when detecting behaviour that falls outside the expected communication behaviour.
+
+NOTE 2: Such actions can be, for instance, to terminate the UE's communication, to block the transferred data between the UE and the not allowed application.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to scale a network slice used for the third-party, i.e. to adapt its capacity.
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
+
+Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party.
+
+Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party.
+
+Based on operator policy, the 5G system shall provide suitable means to allow a trusted and authorized third-party to consult security related logging information for the network slices dedicated to that third-party.
+
+Based on operator policy, the 5G network shall be able to acknowledge within 100ms a communication service request from an authorized third-party via a suitable API.
+
+The 5G network shall provide suitable APIs to allow a trusted third-party to monitor the status (e.g. locations, lifecycle, registration status) of its own UEs.
+
+NOTE 3: The number of UEs could be in the range from single digit to tens of thousands.
+
+The 5G system shall provide suitable APIs to allow third-party infrastructure (i.e. physical/virtual network entities at RAN/core level) to be used in a private slice.
+
+A 5G system shall provide suitable APIs to enable a third-party to manage its own non-public network and its private slice(s) in the PLMN in a combined manner.
+
+TS 22.261 clause 6.26.2.3:
+
+The 5G network shall enable the network operator to create, manage, and remove 5G LAN-VN including their related functionality (subscription data, routing and addressing functionality).
+
+TS 22.261 clause 6.26.2.5:
+
+The 5G system shall support traffic scenarios typically found in an industrial setting (from sensors to remote control, large amount of UEs per group) for 5G LAN-type service.
+
+TS 22.261 clause 6.26.2.9:
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to create/remove a 5G LAN-VN.
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to manage a 5G LAN-VN dedicated for the usage by the trusted third-party, including the address allocation.
+
+Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to add/remove an authorized UE to/from a specific 5G LAN-VN managed by the trusted third-party.
+
+TS 22.261 clause 8.5:
+
+For a private network using 5G technology, the 5G system shall support network access using identities, credentials, and authentication methods provided and managed by a third-party and supported by 3GPP.
+
+23.628, 5.6.1 provides monitoring of UE location, IMSI-IMEI association changes, UE connectivity and PDN connection status.
+
+23.502, 4.15.3.1 provides the analogous monitoring capabilities for the 5GC.
+
+It may be possible for the utility to interact using non-standard means with the MNO to determine the status of any of their subscriptions (and associated UICC/USIMs.) This capability is entirely out of scope of 3GPP.
+
+It also may be possible using non-standard means for the utility to request configuration default information related to their subscriptions (and associated UICC/USIMs.) This capability is entirely out of scope of 3GPP.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+[PR.5.7-001] Based on MNO policy, the 5G network shall provide means to allow a trusted third party to monitor LAN-VN performance parameters, to configure and receive information for conditions relevant to a specific UE, specifically performance of the network and configuration aspects of the UE in the VN.
+
+[PR.5.7-002] The 5G system shall provide a means by which an MNO informs 3rd parties of network events (failure of network infrastructure affecting UEs in a particular area, etc.).
+
+[PR.5.7-003] The 5G system shall provide a means by which an MNO informs 3rd parties of congestion or other general performance degradation (especially if planned or known).
+
+[PR.5.7-004] The 5G system shall provide a means by which an MNO can report site specific and massive events to 3rd parties.
+
+[PR.5.7-005] The 5G system shall provide means by which an MNO informs 3rd parties of changes in UE subscription information. The 5G system shall also provide a means for 3rd parties to request this information at any time from the MNO.
+
+NOTE: Examples of UE subscription information include IP address, 5G LAN-VN membership and APN/DNN. These changes can have strong impacts in the stability of the 3rd party service.
+
+[PR.5.7-005a] Based on operator policy, the 5G system shall provide means for the 3rd parties to request changes to UE subscription parameters for access to data networks, e.g. static IP address, APN/DNN.
+
+[PR.5.7-006] The 5G system shall provide a means by which an MNO can inform 3rd parties of changes in the RAT type serving UE, cell ID, quality of signal information, change in frequency band assigned with a suitable frequency via OAM and/or 5G core network to aid the 3rd party user in taking proactive actions to achieve their own service availability.
+
+## 5.8 Use case of Smart Distribution Transformer Terminal
+
+### 5.8.1 Description
+
+The Smart Distribution Transformer Terminal is usually deployed in the distribution transformer area. It could support multiple energy applications simultaneously. Multiple kinds of energy data are collected firstly by the terminal and then delivered to related energy application platform. Some kind of data could be analysed, or even the terminal itself can make decision to perform real-time action. Figure 5.8.1-1 illustrates a work flow example of Smart Distribution Transformer Terminal.
+
+
+
+The diagram illustrates the work flow of a Smart Distribution Transformer Terminal. At the top, three application platforms are shown: **Connection Management Platform**, **Distribution Master Station**, and **Electric Energy Data Acquire System Master Station** (with an ellipsis indicating additional platforms). Below these, two communication channels are depicted: **Channel 1: Broad bandwidth** and **Channel 2: Low latency, high stability**. Channel 1 is associated with data such as Electrical analog data, Meter reading data, Topology relationship, Decision-making information, Edge computing conclusion, Equipment OA&M data, Parameter tune, Remote upgrading, and Scheduled communication. Channel 2 is associated with Fault / Alarming events, Switch state variation, Device abnormal changes, Remote control operation, and other events. Both channels connect to a central **Smart Distribution Transformer Terminal**. Below this terminal, six end devices are connected: **Smart meter**, **Power consumption concentrator**, **Cable head temperature sensor**, **Charging pile**, **Smoke detector**, and **Smart RCD**.
+
+Figure 5.8.1-1: Example of Smart Distribution Transformer Terminal work flow. The diagram shows a central 'Smart Distribution Transformer Terminal' connected to various end devices (Smart meter, Power consumption concentrator, Cable head temperature sensor, Charging pile, Smoke detector, Smart RCD) and to two communication channels. Channel 1 (Broad bandwidth) connects to the 'Connection Management Platform' and handles data like electrical analog data, meter reading data, and scheduled communication. Channel 2 (Low latency, high stability) connects to the 'Distribution Master Station' and 'Electric Energy Data Acquire System Master Station' and handles fault/alarming events, switch state variation, and remote control operations.
+
+**Figure 5.8.1-1: Example of Smart Distribution Transformer Terminal work flow**
+
+With the assistance of 5G system, it could report massive energy data separately to multiple energy application platforms according to their requirements. And data from energy application platforms could also be sent to terminal through 5G network, no matter it is business data or management data. Typical interactive data includes fault / alarming events, switch state variation, device abnormal changes, remote control operation, electrical analog data, meter reading data, topology relationship, decision-making information, edge computing conclusion, equipment OA&M data, remote upgrading, scheduled communication, etc. Some of this data is event triggered and requires a high priority for real-time communication while others may need a regular latency but broad bandwidth channel to fit their demands.
+
+The energy application platform could be connection management platform (a.k.a. IoT platform), master station of distribution automation system and master station of electric energy data acquire system. In the future, there might be more platforms that need to transfer data through the 5G network.
+
+In general, the connections between the Smart Distribution Transformer Terminal and application platform are provided by 5G system, while the connections between energy end equipment and Smart Distribution Transformer Terminal may be provided by 5G system either. When they are 5G connections, about 300 ~ 500 energy end equipment are connected to a Smart Distribution Transformer Terminal. The average application layer packet data rate for one kind of Smart Grid application between the Smart Distribution Transformer Terminal and energy end equipment is more than 2 Mbit/s in uplink e.g. smart metering, while the communication range is from 100m to 500m. In some cases, the data delivered to the Smart Distribution Transformer Terminal can be locally processed by the Terminal directly to improve working efficiency with the authorization of application platform. These energy applications and different data flows in one application require different communication services and different safety & isolation protection according to the Industry regulation. So, the Smart Distribution Transformer Terminal is required to isolate these energy data according to different application demands.
+
+### 5.8.2 Pre-Conditions
+
+The energy company EE has a contract with Tele-Operator TT. TT will provide 5G communication service for EE's energy services.
+
+EE has deployed a lot of Smart Distribution Transformer Terminals which could utilize 5G communication links to connect with multiple energy application platforms. In general, one Smart Distribution Transformer Terminal is deployed in one distribution transformer area.
+
+The energy application platform could be connection management platform (AKA IoT platform), master station of distribution automation system and master station of electric energy data acquire system. In future, there might be more platforms that need to transfer data through this network.
+
+EE configures different communication services demands and safety & isolation demands for different energy applications.
+
+EE also deploys a management platform to operate and manage its Smart Distributed Transformer Terminals which may be up to millions in the platform management scope. The connections between them also can be supplied by 5G system and are required as permanent links once they are established. The heart-beat information is transmitted when there is no management data.
+
+### 5.8.3 Service Flows
+
+- 1) The 5G system gets the demands of communication and isolation to establish two 5G communication links between the Smart Distribution Transformer Terminal and the energy application platform. One link is required with high data rate to deliver data e.g. electrical analog data, meter reading data, topology relationship, decision-making information, edge computing conclusion, equipment OA&M data, remote upgrading, scheduled communication, etc. The other link is required with low latency and high stability to deliver data e.g. fault / alarming events, switch state variation, device abnormal changes, remote control operation, etc.
+- 2) In distribution transformer area A, 5G system is required to establish communication links for 500 energy end equipment to connect with the Smart Distributed Transformer Terminal. Thus, the Smart Distributed Transformer Terminal works as a service relay or gateway.
+- 3) The energy end equipment in area A and area B e.g. smart meters, cable head temperature sensors, power consumption concentrators, smoke detectors, smart RCDs, charging piles and phase change switches, collect related data and secured deliver the data them to Smart Distribution Transformer Terminal.
+- 4) The Terminal continues to deliver the collected data and analysis / decision information to different energy application platforms through the two 5G communication links with different isolation demands mentioned above.
+ - Some data e.g. energy consumption data in the distribution transformer, power line, and user point can be analysed by the Terminal and take some action e.g. adjust topology. Then the result data will be reported to related energy application platform.
+ - Some data is periodic collected and reported, e.g. energy quality data and energy equipment status data.
+ - Some data is event trigger and need to be reported in real time, e.g. the voltage, current, alarm data of each node in the low-voltage area.
+- 5) The Smart Distributed Transformer Terminals management platform monitors all the working status of terminals and if needed, sends order to the terminal through the 5G communication link to maintain the Smart Distributed Transformer Terminal's normal work.
+
+### 5.8.4 Post-Conditions
+
+The energy application platforms receive the collected data in time and with required isolation protection.
+
+The communication links status also can be monitored by energy company EE.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 clause 6.5.2, there is a related requirement:
+
+Based on operator policy, the 5G network shall be able to support routing of data traffic between a UE attached to the network and an application in a Service Hosting Environment for specific services, modifying the path as needed when the UE moves during an active communication.
+
+The 5G system shall be able to provide suitable APIs for the energy application platform to monitor the quality of the communication link.
+
+The 5G system shall be able to supply end to end unified quality of communication service for Smart Distribution Transformer Terminal, i.e. from the energy end equipment to energy application platforms.
+
+The 5G system shall be able to support millions of communication links between Smart Distributed Transformer Terminals management platform and Smart Distributed Transformer Terminals under its management scope.
+
+When required by regulatory requirement, the 5G system shall be able to simultaneously supply multiple different isolation communication services for different energy applications.
+
+The 5G system shall be able to support up to 500 communication links between the Smart Distribution Transformer Terminal and energy end equipments with the communication distance from 100m to 500m in one distribution transformer area.
+
+The 5G system shall be able to support routing of data traffic between the Smart Distribution Transformer Terminal in the network and an application processing the data in a service hosting environment.
+
+NOTE: The smart distribution transformer terminal is one kind of Grid terminal and may be deployed in network edge node.
+
+The 5G system shall be able to supply a method for the application layer to authenticate and authorize communication network element used for the Smart Distribution Transformer Terminal.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+[PR.5.8-001] The 5G system shall be able to provide required communication service according to KPI given in table 5.8.6-1.
+
+**Table 5.8.6-1: Key Performance for Smart Distribution Transformer Terminal**
+
+| Average data rate (UL) (note 1) | End-to-end latency (note 2) | Area user density | Range |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|-----------------------------------------|----------------------------------------------|
+| >2 Mbit/s | 10 ms, 100 ms, 3 s | 500 devices /distribution area (note 3) | 100 m ~ 500 m, outdoor, indoor / deep indoor |
+| NOTE 1: It is the smart metering application data rate between the Smart Distribution Transformer Terminal and energy end equipment. Once there are multiple Smart Grid applications, it is required more data rate.
NOTE 2: It depends on different applications supported by the Smart Distribution Transformer Terminal. The less the latency is, the more applications can be supported.
NOTE 3: The distribution area can be calculated as $3.14 \times \text{Range}^2$ . It is in general $0.031\text{km}^2 \sim 0.785\text{km}^2$ . | | | |
+
+## 5.9 Use case of isolation demand for energy applications
+
+### 5.9.1 Description
+
+According to the regulation of China Grid industry, the power grid business is mainly divided into two working categories: production control and information management. The production control can be further divided into safety zone I and safety zone II. All the real-time monitoring, detection, and controlling energy production applications belong to safety zone I. And other non-controlling energy production applications belong to the safety zone II. The information management also can be further divided into safety zone III and safety zone IV. The applications belong to the safety zone III are information systems for power production, while the internal information services for the energy enterprises belong to safety zone IV. Following Table 5.9.1-1 lists the typical applications belong to different safety zones.
+
+**Table 5.9.1-1: typical safety zone and related energy application**
+
+| Safety Zone type | Typical energy applications |
+|------------------|-----------------------------|
+|------------------|-----------------------------|
+
+| | |
+|-----|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| I | distribution automation system, substation automation system, relay protection, distributed energy storage, etc. |
+| II | Reservoir dispatch automation system, electric energy metering system, relay protection and fault recording information management system, etc. |
+| III | Dispatch production management system (DMIS), lightning monitoring system, power line inspection, statistical report system, etc. |
+| IV | Management Information System (MIS), Office Automation System (OA), Customer Service System, etc. |
+
+According to, different kinds of safety isolation requirements are applied to different safety zones:
+
+- The energy applications belong to production control category i.e. safety zone I and II need to be physically isolated from other applications which don't belong to production control working category.
+- The energy applications belong to information management working category i.e. safety zone III and IV can be logically isolated from other applications including non-energy applications.
+- The energy applications belong to a same working category can be logically isolated each other.
+- The energy applications belong to a same safety zone can be logically isolated each other
+
+
+
+The diagram shows the 'Energy Working Domain' divided into two main categories: 'production control' and 'information management'. The 'production control' category contains 'Safety Zone I' (red box) and 'Safety Zone II' (purple box), which are separated by a solid vertical line representing physical isolation. The 'information management' category contains 'Safety Zone III' (green box) and 'Safety Zone IV' (blue box), which are separated by a dashed vertical line representing logical isolation. A legend at the top right indicates that a solid line represents 'physical isolation' and a dashed line represents 'logical isolation'.
+
+Diagram illustrating isolation demand for energy applications. It shows two main categories: 'production control' and 'information management'. 'production control' includes Safety Zone I and Safety Zone II, which are separated by a solid line representing physical isolation. 'information management' includes Safety Zone III and Safety Zone IV, which are separated by a dashed line representing logical isolation. A legend indicates that a solid line represents physical isolation and a dashed line represents logical isolation.
+
+**Figure 5.9.1-1: isolation demand for energy applications**
+
+Typically, the physical isolation requires the traditional wired communication link utilizing different time slots, wavelengths, and physical media to guarantee the safety demand. And the logical isolation may be supported by shared communication resource.
+
+With 5G system is utilized to support Smart Grid applications, the different isolation modes will also be supported by 5G system. Not only core network, but also radio network and UE are involved. For 5G system, the physical isolation communication service means dedicated core network element and dedicated radio resource e.g. PRB pool, spectrum etc. The logical isolation communication service on the other hand may be supported by shared network element or shared network resource.
+
+### 5.9.2 Pre-Conditions
+
+The energy company EE utilizes 5G system to support multiple energy applications with different isolation communication services. Among them, the PMU belongs to safety isolation I, the electricity information collection belongs to safety isolation II, power line on-site patrol belongs to safety isolation III, Office Automation System (OA) belongs to safety isolation IV.
+
+### 5.9.3 Service Flows
+
+The 5G system deploys several communication links to support multiple energy applications.
+
+One link is used to support PMU application and the dedicated core network element and dedicated radio resource have been configured in this link to guarantee the physical isolation demand.
+
+One link is used to support electricity information collection application. It also belongs to safety isolation II which can be logical isolation with applications belong to safety isolation I and physical isolation with applications belong to safety isolation III and IV. So, it also can share network resource e.g. core network element and dedicated resource with PMU application.
+
+One link is used to support power line on-site patrol application. It belongs to safety isolation III which require logical isolation. Considering applications belong to safety isolation I & II require physical isolation with applications belong to safety isolation III and IV, it can't share the network resource e.g. core network element and dedicated resource with PMU, differential protection and electricity information collection applications. But it can share network resource with other applications belong to safety isolation III and IV, even other internet applications.
+
+One link is used to support Office Automation System (OA). It also requires logical isolation. So, it can share network resource with power line on-site patrol application.
+
+The energy company EE also can monitor the above communication resource usage and communication link quality.
+
+### 5.9.4 Post-Conditions
+
+The energy applications can be work well and fulfil the isolation requirements with the assistance of 5G system.
+
+The communication resource usage status and communication link quality also can be monitored by energy company EE.
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+When required by regulations, the 5G system shall be able to provide suitable mechanism for the energy application to monitor the communication link quality and network resource usage.
+
+When required by regulations, the 5G system shall be able to utilize dedicated communication resource including core network and radio network to support physical isolation communication service for energy applications.
+
+When required by regulations, the 5G system shall be able to utilize shared communication resource including core network and radio network to support logical isolation communication service for energy applications.
+
+The 5G system shall be able to simultaneously support multiple communication links with different isolation requirements according to energy management regulation.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+None.
+
+## 5.10 Utility End to End Security
+
+### 5.10.1 Description
+
+In some networks, communication is done in different security domains.
+
+
+
+The diagram shows three distinct security domains represented by colored boxes. The 'Premises Network' (yellow) on the left contains three small square icons representing devices, each with a wireless signal symbol, connected by lines to a central white box labeled 'ROUTER' and 'UE'. This central box is connected to the '3GPP Network' (blue) box in the middle by a blue line. The '3GPP Network' box is connected to the 'Service Network' (pink) box on the right by a black line, which leads to a white box labeled 'Service Platform'.
+
+Diagram illustrating three different security domains: Premises Network, 3GPP Network, and Service Network. The Premises Network (yellow) contains three devices connected to a central ROUTER/UE unit. The ROUTER/UE unit is connected to the 3GPP Network (blue) via a blue line. The 3GPP Network is connected to the Service Network (pink) via a black line, which is connected to a Service Platform unit.
+
+**Figure 5.10.1-1: Different Security Domains**
+
+There are three domains depicted above. One is in the premises with the devices at the edge of the utility network, e.g. sensors. The second domain is the 3GPP network. The third is the service network. This scenario, to secure communication, requires application communication above the network layer (e.g. TLS or another transport layer security mechanism, S/MIME or another presentation layer security mechanism or encryption at the application layer.)
+
+The situation becomes even more complex if there are multiple applications, different networks used at the edge and different communications systems used for the end to end service.
+
+In this use case, integration of communication end to end with the 5G system presents benefits to end to end service delivery.
+
+### 5.10.2 Pre-conditions
+
+A gateway (UE and router) provides 5GLAN service from a Distribution Service Operator (DSO), EnergyCo to 1000s of sites (e.g. substations) in which there is diverse communication-enabled equipment.
+
+This set of devices is provisioned with security configuration sufficient for authorization and registration with the 5G system. Specifically, the devices are equipped with USIMs or, in NPNs, with non-3GPP credentials, to allow for the network operator to perform Authentication, Authorization and Accounting (AAA.)
+
+The service platform of EnergyCo is also has sufficient configuration to obtain services with the 5G system from a 'northbound interface'.
+
+### 5.10.3 Service Flows
+
+EnergyCo's equipment (e.g. sensors, remote controllable devices, etc.) within the premises of 1000s of substations uses its configuration authorize access to the UE/Gateway, which provides access to the 5G System for communication services. One such device sends an alert message to EnergyCo's service platform.
+
+
+
+The diagram shows three distinct security domains represented by colored boxes. On the left, a yellow box labeled 'Premises Network' contains three IoT device icons connected by blue lines to a central white box labeled 'ROUTER' with 'UE' below it. This router/UE is connected to a blue box labeled '3GPP Network' via a white box labeled 'GW'. The 'GW' is then connected to a pink box labeled 'Service Network' via a white box labeled 'Service Platform'. Blue lines represent the communication paths between these components across the domain boundaries.
+
+Diagram illustrating three security domains: Premises Network, 3GPP Network, and Service Network. The Premises Network (yellow) contains three IoT devices connected to a ROUTER/UE. The ROUTER/UE is connected to the 3GPP Network (blue) via a GW (Gateway). The GW is connected to the Service Network (pink) via a Service Platform.
+
+**Figure 5.10.3-1: Different Security Domains**
+
+The communication between the device and the Router/UE is secured with respect to the constraints acceptable to EnergyCo. The communication through the 5G system employs 5G security, which provides secure communication to the service levels expected by EnergyCo. Finally, a secure session can be provided using credentials between the Service Platform and the 3GPP system – whose edge is depicted as a gateway (GW), if network layer security services are required by EnergyCo.
+
+### 5.10.4 Post-conditions
+
+The EnergyCo equipment to Service platform communication is secured end-to-end in a uniform manner for all their equipment, meeting EnergyCo's security requirements.
+
+### 5.10.5 Existing features partly or fully covering the use case functionality
+
+There are several ways that the existing 5G system could support this use case.
+
+First, by means of alternative authentication methods between the equipment and the UE. The 'uniformity' in this case would rely upon establishing the same configuration and operation regime in the equipment and UE/Router in all installations.
+
+TS 22.261 v17.3.0, clause 8.3:
+
+The 5G system shall support operator controlled alternative authentication methods (i.e. alternative to AKA) with different types of credentials for network access for IoT devices in isolated deployment scenarios (e.g. for industrial automation).
+
+The 5G network shall support a 3GPP supported mechanism to authenticate legacy non-3GPP devices for 5G LAN-VN access.
+
+While this may suffice to secure the Equipment to UE/Router communication, it is not significantly different than the scenario described in 5.10.1. There is no 'end-to-end' support in this scenario, unless a security association is established between the equipment and the service platform (by means outside of the scope of 3GPP, i.e. over the top.)
+
+Second, the equipment could establish a security association with the 5G system (not just with the router.)
+
+TS 22.261 v17.3.0, clause 8.3:
+
+The 5G system shall support a suitable framework (e.g. EAP) allowing alternative (e.g. to AKA) authentication methods with non-3GPP identities and credentials to be used for UE network access authentication in non-public networks.
+
+NOTE 2: Non-public networks can use 3GPP authentication methods, identities, and credentials for a UE to access network but are also allowed to utilize non-AKA based authentication methods such as provided by the EAP framework.
+
+In this approach, assuming the EAP framework chosen afforded sufficient security protections for the non-public network, the communication from the equipment to the Router/UE and through the 5G System would be in the same security domain. A gap (described below in 5.10.6) is the communication between the 5G System and the EnergyCo service platform, which is currently not defined in the 5G standard.
+
+Third, the equipment in the EnergyCo network could be provided with sufficient credentials (including a USIM) to fully become authorized with the 5G System. In this case, end to end security is possible by means of the GAA framework.
+
+TS 33.220 v16.2.0, clause 4:
+
+The 3GPP authentication infrastructure, including the 3GPP Authentication Centre (AuC), the USIM or the ISIM, and the 3GPP AKA protocol run between them, is a very valuable asset of 3GPP operators. It has been recognised that this infrastructure could be leveraged to enable application functions in the network and on the user side to establish shared keys.
+
+### 5.10.6 Potential New Requirements needed to support the use case
+
+[PR.5.10-001] The 5G system shall enable support of a mechanism to support authentication and secured communication between the 5G system Core Network and a 3rd party's application function, in order to provide secure end to end communication service.
+
+## 5.11 QoS Monitoring and Reporting Mechanisms
+
+### 5.11.1 Description
+
+This use case explores in more detail an aspect of service level management that is the business relationship between an energy utility operator, "EnergyCo" and the telecommunications operator, "Telecomm1". While their business relationship itself is out of scope of 3GPP standardization, there are aspects of the SLA, specifically agreements for achieving and monitoring performance and satisfaction of KPIs, and managing incidents improve the suitability of Telecomm1's service offerings for EnergyCo.
+
+### 5.11.2 Pre-conditions
+
+The different services offered by Telecomm1 should behave as expected according to the KPIs defined in the Table 5.5.1. Only if that is the case, is service delivery acceptable according to the SLA, to meet the different services' requirements (whether mission critical or not.) If the telecommunication service degrades below these KPIs, EnergyCo may experience a service interruption or degradation. This might affect mission critical operations and/or quality of service delivered ultimately to the customer.
+
+The granularity of the use case considers the support of QoS to a particular UE, per class of service. This is the model described in 22.867, clause 5.5. Here the UE is a gateway serving as a router to a network: the UE is essentially a router with a mobile telecommunication interface for communication beyond the local network. Smart energy applications are not generally running on the UE – they are deployed in the network behind the UE. See figure 5.5.3-1.
+
+This use case assumes that the SLA is in place and service is offered by Telecomm1 to EnergyCo. In addition, both interfaces and procedures are in place to respond to failures to deliver KPIs according to the SLA.
+
+NOTE: The use case is based on real experience between utility and telecom providers but the identities of EnergyCo and Telecomm1 are fictitious.
+
+### 5.11.3 Service Flows
+
+For the KPIs, part of SLA definition between EnergyCo and Telecomm1, there is a report sent by EnergyCo to Telecomm1 on a monthly basis in order to inform of the degree of compliance of the requirements set in the SLA for the different KPIs. Telecomm1 will reconcile this report with their own records.
+
+KPIs will be measured by means of EnergyCo owned Network Management platforms in real time. These platforms will check periodically the availability, latency and packet loss rate of the connection. Different periodicities can be configured and as a result average information will be obtained. Reports are available in order to deliver accumulated information of the different parameters on a daily, weekly, monthly or yearly basis.
+
+This information will be checked in order to verify the degree of compliance of the SLA. Connectivity status, stability and Performance will be part the technology reports. Only Latency and Packet loss rate will be constantly measured as a part of Performance parameters, Throughput will only be measured during commissioning process. If there is a problem such as quality of service degradation (high latency and packet loss rate below thresholds) or instability of the connection affecting a specific substation or group of substations (connected to the same server) for more than one week an automatic alarm will be generated towards the MNO.
+
+In the event of massive communication loss affecting most services and substations (quantity above % threshold), this will be detected in real time and an automatic alarm will be sent to the MNO.
+
+In the event of sustained connection loss events affecting a number of Substations located within a well limited geographical area this might shed light on a problem related to a specific eNB site or sector. An automatic alarm will be generated and sent to the MNO.
+
+### 5.11.4 Post-conditions
+
+Since EnergyCo provides Telecomm1 with their report of service degradations, and Telecomm1 provides their report to EnergyCo, both organizations have a full set of records with respect to achieved performance of service according to KPIs in the SLA. It is possible for EnergyCo and Telecomm1 to reconcile the SLA and the achieved performance at any time.
+
+Further, EnergyCo is able to alert Telecomm1 when critical events occur that affect performance in a manner that requires intervention (or at least scrutiny) by the MNO.
+
+Finally, Telecomm1 can alert EnergyCo to issues they have detected.
+
+This explains why regular periodic QoS reporting needs to be shared from the customer to the provider and vice versa.
+
+### 5.11.5 Existing features partly or fully covering the use case functionality
+
+No existing features have been identified that partially or fully cover the use case functionality.
+
+### 5.11.6 Potential New Requirements needed to support the use case
+
+[PR.5.11-001] The 5G system shall provide a mechanism for a 3rd party to report to a MNO service degradations, communications loss and sustained connection loss. These reports use a standard form. The specific values, thresholds and conditions upon which alarms occur could include e.g. the measured values for Latency, Data Rate, Availability, Jitter, etc. for a UE, its location, and the time(s) in which the degradation occurred.
+
+NOTE 1: What the MNO does with such reports is out of scope of 3GPP specifications.
+
+NOTE 2: The above potential requirement expresses the need for reporting by a third party to the 5GS and leaves it to downstream groups (in this case SA5) to work out the implications.
+
+[PR.5.11-002] The 5G system shall provide a mechanism for a MNO to report to 3rd parties service degradations, communications loss and sustained connection loss. These reports use a standard form. The specific values, thresholds and conditions upon which alarms occur could include e.g. the measured values for Latency, Data Rate, Availability, Jitter, etc. for a UE, its location, and the time(s) in which the degradation occurred.
+
+NOTE 3: What the 3rd party does with such reports is out of scope of 3GPP specifications.
+
+NOTE 4: The above potential requirement expresses the need for reporting by the 5GS to a third party and leaves it to downstream groups (in this case SA5) to work out the implications.
+
+## 5.12 Distribution Intelligence – FLISR (Fault Location, Isolation, and Service Restoration)
+
+### 5.12.1 Overview
+
+"Distribution intelligence" refers to the part of the Smart Grid that applies to the distribution system, that is, the wires, switches, and transformers that connect the utility substation to the customers. A key component of distribution intelligence is outage detection and response. Today, many utility companies rely on customer phone calls to know which areas of their distribution system are being affected by a power outage. Along with smart meters, distribution intelligence will help to quickly pinpoint the source of a power outage so that repair team can be immediately dispatched to the problem area. Most utility companies count on complex power distribution schemes and manual switching to keep power flowing to most of their customers, even when power lines are damaged and destroyed. However, this approach has its limitations, and in many cases an automated system could respond more quickly and could keep the power flowing to more customers. By having sensors that can indicate when parts of the distribution system have lost power, and by combining automated switching with an intelligent system that determines how best to respond to an outage, power can be rerouted to most customers in a matter of seconds, or perhaps even milliseconds.
+
+
+
+Figure 5.12.1-1: the big picture of Smart Energy. This diagram illustrates the flow of energy and data across different sectors of the grid. On the left, the 'Generation' section includes Nuclear Power Import, Cross-Border Interconnection, Local Generation, and Renewable Generation. The central 'Transmission & Distribution' section features Grid Automation, an Intelligent Substation, and Smart Switch & Distribution Automation, all connected to a Remote Control / Condition Monitoring / Wide-Area Monitoring system. The 'Residential' section shows Smart Control/Smart Appliances, a Home Display Unit, Energy Storage, and Smart Meter/Advanced Metering Infrastructure. The 'Commercial & Industrial' section includes a Car Park with Electric Vehicle Charging, Energy Storage, a Distributed Energy Management System, and a Smart Building with Distributed Generation. A legend at the bottom left distinguishes between the Power Network (solid orange line) and Telecommunication (dashed green line).
+
+**Figure 5.12.1-1: the big picture of Smart Energy**
+
+The automation in distribution with self-healing solutions is surely a critical challenge to consider in this transformational evolution towards Smart/Smarter Energy. Self-healing will enable system operators to benefit from a significant reduction in the outage duration and number of affected customers, which reacts quickly and precisely to power disturbances so that only those in the immediate neighbourhood are affected, while avoiding any interruption in power. Self-healing not only acts against grid disturbances, but secures the grid against disturbances spread. The basic requirements include [18]:
+
+- Fast and proper detection of grid disturbances.
+- Redistribution of grid resources to avoid adversative impacts.
+- Assuring the continuity of service under any conditions.
+- Minimization of service restoration time.
+
+Reliable and secure communications are essential to enable self-healing in the Smart Energy. A precise and effective decision is based on analysing the power grid data, hence collecting and exchanging information, transferring results, executing decisions, and monitoring real-time device states in the grid are the responsibility of the communication system. To support fast and precise detection of grid disturbances 5G system is expected to provide communication
+
+services with ultra-low latency, ultra-high reliability and availability, as well as high data rate at both uplink and downlink.
+
+Two approaches to detect grid disturbances are discussed:
+
+- 1) feeder automation
+- 2) line current differential protection
+
+### 5.12.2 Feeder automation
+
+#### 5.12.2.1 Description
+
+Feeder automation is designed to utilise controller devices that are especially designed to support the self-healing of power distribution grids with overhead lines. The self-healing logic resides in individual controller devices located at the poles at the feeder level. Using peer-to-peer communication (e.g. via IEC 61850 GOOSE) among the controller devices, the system operates autonomously without the need of a regional controller or control centre. All self-healing steps carried out are reported immediately to the control centre to keep the grid status up-to-date.
+
+
+
+The diagram illustrates a distributed feeder automation system. It shows a network of distribution lines (labeled 'Distribution Lines') with several poles. At one pole, there are 'Fault Indicators'. At another pole, there are 'Reclosers' and 'RTUs'. Arrows indicate communication flow: 'From / to Central Controller' (pointing to a pole), 'From Distribution Substation' (pointing to a pole), and 'To Metering' (pointing away from a pole). The lines connect these components to form a mesh-like network.
+
+Diagram of Distributed Feeder Automation showing a network of distribution lines with various components connected to a central controller and a distribution substation.
+
+Figure 5.12.2.1-1: Distributed Feeder Automation
+
+#### 5.12.2.2 Pre-condition
+
+The controller devices have been mounted, connected, and configured during commissioning and deployment. The configuration is usually not done via the mobile network but via local wired connection.
+
+The controller devices are connected to the 5G network, and the peer-to-peer communication is enabled using IEC 61850 GOOSE (OSI Layer 2, broadcast/subscription Ethernet-based protocol).
+
+#### 5.12.2.3 Service flow
+
+Communications are enabled via 5G network among the controller devices
+
+- among controller devices serving the same feeder and
+- among the controller devices of the whole area and the control centre.
+
+A feeder fault occurs. The controller device in the upstream of the fault point generates and transmits GOOSE signals to other controller devices serving the same feeder. Each controller device compares the GOOSE signals with the overcurrent signals of the current level, identifies the fault range, and then isolates the fault, implementing automatic power recovery in non-fault areas.
+
+To prevent power disturbance, the overall feeder automation process must be completed within 100 ms. As discussed in [x3] with regards to the delay budget, the latency for one way transmission from one controller device to another needs to be kept at approximately 20 ms (this would allow for the necessary margin). To ensure precise fault detection and isolation, 10 µs or less time synchronization accuracy is also required.
+
+Typically there are 10s of controller devices per km2. The geographical dimension of feeders is usually up to several km2.
+
+#### 5.12.2.4 Post-condition
+
+5G communication runs and power distribution is restored in the affected area.
+
+#### 5.12.2.5 Existing features partly or fully covering the use case functionality
+
+The use case "Distributed automated switching for isolation and service restoration" has been captured in TS 22.104 Annex 2.4.4, while the corresponding performance requirements have been specified in table 5.2-1 "Periodic deterministic communication service performance requirements":
+
+**Table 5.12.2.5-1: performance requirements applicable to this use case**
+
+| Characteristic parameter | | | | Influence quantity | | | | | | |
+|-----------------------------------------------------------|---------------------------------------------------------------|------------------------------------------|-------------------------------------------------------|------------------------------|----------------------------------------------|------------------------|-------------------|----------|-----------------------|-------------------------------------------------------------------------------------------------------------------|
+| Communication service availability: target value (note 1) | Communication service reliability: mean time between failures | End-to-end latency: maximum (notes 2, 5) | Service bit rate: user experienced data rate (note 5) | Message size [byte] (note 5) | Transfer interval: target value (note 5) | Survival time (note 5) | UE speed (note 6) | # of UEs | Service area (note 3) | Remarks |
+| 99.9999 % | – | < 5 ms | 1 kbit/s (steady state)
1.5 Mbit/s (fault case) | < 1500 | < 60 s (steady state)
≥ 1 ms (fault case) | transfer interval | stationary | 20 | 30 km x 20 km | Electrical Distribution – Distributed automated switching for isolation and service restoration (A.4.4); (note 4) |
+
+NOTE 1: One or more retransmissions of network layer packets may take place in order to satisfy the communication service availability requirement.
+NOTE 2: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+NOTE 3: Length x width (x height).
+NOTE 4: Communication includes two wireless links (UE to UE).
+NOTE 5: It applies to both UL and DL unless stated otherwise.
+NOTE 6: It applies to both linear movement and rotation unless stated otherwise.
+
+The gaps identified include:
+
+- < 5ms end-to-end latency has been captured with no explanation in TS 22.104 (neither in TR 22.804);
+- time synchronicity requirement is not addressed;
+- fault detection and isolation is typically event driven and aperiodic communication may be sufficient.
+
+#### 5.12.2.6 Potential New Requirements needed to support the use case
+
+[PR.5.12.2-001] The 5G system shall be able to provide a periodic deterministic communication with the service performance requirements reported in the tables below.
+
+**Table 5.12.2.6-1: service performance requirements for Feeder automation**
+
+| Communication service availability | Max Allowed End-to-end latency (note 1) | Message size [byte] | UE speed | # of UEs | Service Area |
+|------------------------------------|-----------------------------------------|---------------------|------------|-----------------------|-------------------------|
+| > 99.999 % | 20 ms | < 100 | Stationary | ≤ 100/km 2 | several km 2 |
+| NOTE 1: UE to UE communication. | | | | | |
+
+**Table 5.12.2.6-2: service performance requirements for Feeder automation continued**
+
+| Number of devices in one Communication group for clock synchronisation | 5GS synchronicity budget requirement | Service area |
+|------------------------------------------------------------------------|--------------------------------------|-------------------------|
+| ≤ 100/km 2 | ≤ 10 µs | several km 2 |
+
+### 5.12.3 High speed current differential protection
+
+#### 5.12.3.1 Description
+
+The high speed current differential protection for smart energy distribution systems is capable of sub-millisecond fault detection. The approach utilises the natural characteristics of differential current measurements to significantly reduce fault detection times, which has been described in detail in clause 5.4. This use case focuses on the traffic characteristics.
+
+#### 5.12.3.2 Pre-condition
+
+Protection relays (e.g. relay\_a and relay\_b in Figure 5.4.1-1) are deployed and switched on in the distribution grid. All relays are connected to the 5G network and are synchronised with neighbouring relays in the distribution grid with a precision of <10 µs to ensure that the current values are sampled at the same time.
+
+#### 5.12.3.3 Service flow
+
+The protection relays exchanges the current samples via the 5G system. Each relay then compares the sent and received samples to determine if a fault has occurred in a protected area in order to isolate the fault. The detail of fault detection can be found in clause 5.4.
+
+The sampling rate varies dependent on the algorithms designed by the manufacturers. A protection relay collects the current samples (with the typical message size of up to 245 bytes) at a frequency in the range of [600, 1200, 1600, 3000] Hz. The exchange of measurement samples is done in a strictly cyclic and deterministic manner. [6] [20] With the sampling rate of 600 Hz (6 times per 10 ms), the transfer interval would be 1,667 ms with the required bandwidth of 1.18 Mbit/s; for 1200 Hz (12 times per 10 ms), the transfer interval would be 0,833 ms with the required bandwidth of 2.36 Mbit/s.
+
+As to the latency, as pointed out in clause 5.4 the maximum allowed end-to-end delay between two protection relays would be between 5ms and 10ms depending on the voltage levels as specified in IEC 61850-90-1 [6]. For some legacy systems the latency usually is set to 15ms [20].
+
+#### 5.12.3.4 Post-condition
+
+5G communication runs and power distribution is restored in the affected area.
+
+#### 5.12.3.5 Existing features partly or fully covering the use case functionality
+
+The use case "Application of differential protection in distribution Network of Smart Grid" has been captured in TR 22.804. However the use case and the associated service requirements are missing in TS 22.104.
+
+The missing requirements based on differential protection in distribution network need to be captured.
+
+#### 5.12.3.6 Potential New Requirements needed to support the use case
+
+[PR.5.12.3-001] The 5G system shall be able to provide periodic deterministic communication with the service performance requirements reported in the tables below.
+
+**Table 5.12.3.6-1: performance requirement for High speed current differential protection**
+
+| Communication service availability | End-to-end latency: maximum (note 1) | Service bitrate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+|------------------------------------|--------------------------------------|---------------------------------------------|---------------------|---------------------------------|------------------------------------|------------|-----------------------|-------------------------|
+| > 99.999 % | 15 ms | 2.5 Mbit/s | < 245 | ≤ 1 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| > 99.999 % | 15 ms | 1.2 Mbit/s | < 245 | ≤ 2 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| > 99.999 % | 10 ms | 2.5 Mbit/s | < 245 | ≤ 1 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| > 99.999 % | 10 ms | 1.2 Mbit/s | < 245 | ≤ 2 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| > 99.999 % | 5 ms | 2.5 Mbit/s | < 245 | ≤ 1 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+| > 99.999 % | 5 ms | 1.2 Mbit/s | < 245 | ≤ 2 ms | transfer interval (one frame loss) | stationary | ≤ 100/km 2 | several km 2 |
+
+NOTE 1: UE to UE communication.
+
+**Table 5.12.3.6-2:**
+
+| Number of devices in one Communication group for clock synchronisation | 5GS synchronicity budget requirement | Service area |
+|------------------------------------------------------------------------|--------------------------------------|-------------------------|
+| ≤ 100/km 2 | ≤ 10 µs | several km 2 |
+
+## 5.13 Use case of 5GS support for synchrophasors in wide-area Smart Grid
+
+### 5.13.1 Description
+
+Using phasors as a mathematical approach to describe a power system operation quantities is not new. With the advent of GNSS and other time sources that provide phasor measurement units (PMUs) with accurate timing signals, the concept of synchrophasor came into existence [21]. Modern PMUs and accompanying entities such as Phasor Data Concentrators (PDCs) [22] could connect to the time source and with each other in a number of different ways such as: using direct connection with GPS via an internal GPS receiver, using a connection via IRIG-B (legacy method) or IEEE Std 1588-2008 [23]/IEEE C37.238-2011 [24] or PTP time synchronization profile in IEC 61850-9-3 [7], over an Ethernet to achieve 1 $\mu\text{s}$ time accuracy. This 1 $\mu\text{s}$ time accuracy as referred to in these IEC standards assumes every PMU is has a built-in synchronization modem.
+
+As a result, the phasors throughout a wide-area power system can be measured at different but strategically selected locations (such as at tie-lines and on the key network buses) in a synchronized fashion. This powerful possibility releases huge potential for power utility operators to innovate, so as to achieve various goals in safe, robust and efficient network operation and maintenance. Some interesting applications based on synchrophasors are: power system model validation, wide-area protection, advanced state estimation, frequency-control and oscillation mitigation, etc. With the fast adoption of DERs, the power system will undergo challenges of increased variability and unpredictability, which means the synchrophasors could offer utility operators an effective means to understand, respond and predict the real-time dynamics of the power systems.
+
+Up till now, wide-area measurement systems based on synchrophasors have been under expansion in large scale throughout America, Europe, and Asia. It is an area of opportunity for 5G systems to provide connectivity and services. Thanks for the wide-area coverage of 5G, it is seen by many utilities that 5G could play a major role in supporting PMU wide-area applications paradigm.
+
+Synchrophasors are measured and collected in a hierarchical structure to meet the power system needs. The figure below comes from [25]. But it is important to know that PDCs can have one to many interconnections with each other for the sake of e.g. redundancy. There could be many internal and external functions defined at each PDC, and PDCs could eventually interface with SCADA, EMS and DMS, where applicable. As defined in [25], a PMU and a PDC may transmit its data in one or more separate data streams. Each stream may have different content and may be sent at a different rate. The destination of each stream may be different device(s) and location(s) (multicast data is sent to multiple destinations). Each stream must then be individually controllable, and have its own identification and a separate configuration control. This feature is useful for sending data to different devices with different purposes, allowing streams with different wait times and class of service (M and P class), as specified in [22].
+
+
+
+```
+
+graph LR
+ PMU1[PMU] -- "PDC input streams" --> PDC[PDC]
+ PMU2[PMU] -- "PDC input streams" --> PDC
+ PMU3[PMU] -- "PDC input streams" --> PDC
+ PDC -- "PDC output stream" --> corporatePDC[corporate PDC]
+ corporatePDC <--> regionalPDC[regional PDC]
+ corporatePDC --> dataStorage1[data storage and application]
+ regionalPDC --> dataStorage2[data storage and application]
+
+```
+
+Diagram of a synchrophasor data collection network. Three PMUs on the left send 'PDC input streams' to a central 'PDC' block. The 'PDC' block sends a 'PDC output stream' to a 'corporate PDC' block. The 'corporate PDC' block is connected to a 'regional PDC' block via a bidirectional arrow. Both the 'corporate PDC' and the 'regional PDC' blocks have arrows pointing up to 'data storage and application' blocks.
+
+**Figure 5.13.1.1: Synchrophasor data collection network [X6]**
+
+Within the synchrophasor system, PMUs can be configured with various reporting rates [25]. In a 60Hz system, reporting rates could be {12, 15, 20, 3, 60} per second, and in a 50Hz system, the reporting rates could be {25, 50} per second. It is encouraged to adopt higher rates up to 120 per second. Table 1 shows the corresponding reporting period $1/F_s$ .
+
+**Table 5.13.1-1: PMU reporting rate and the corresponding Reporting Period in IEEE Std C37.118™-2011 [25]**
+
+| | | | | | | | | | |
+|------------------------------------------|------|-------|----|----|------|----|-------|-----|-----|
+| Reporting Rate (Fs)
in Hz | 12 | 15 | 20 | 25 | 30 | 50 | 60 | 100 | 120 |
+| Reporting Period (1/Fs)
in ms | 83.3 | 66.67 | 50 | 40 | 33.3 | 20 | 16.67 | 10 | 8.3 |
+
+With regard to the data flows, each synchrophasor data flow could have an individual QoS – the performance aspects are addressed in [27]. In [28], the real-time communication between PMUs is addressed, and there two performance classes (P and M) are specified with the corresponding dynamic performance requirements. The P class is mainly for protection and control purposes, which requires fast response, minimum filtering and minimum delay. The M class is mainly used for measurements in the presence of out-of-band signals, which requires greater precision and significant filtering, and allows slower response and longer delay. Intuitively, the higher the PDC in the hierarchy (as in Figure 1), the more prone to class M an application deployed there seems to be.
+
+The measurement reporting latency compliance specification defines the PMU real-time output reporting latency is dependent on the corresponding reporting rate Fs. For both performance classes, the measurement reporting latency is defined in Table 2 [25].
+
+**Table 5.13.1-2: PMU measurement reporting latency**
+
+| Performance Class | Max Measurement Reporting Latency |
+|--------------------------|------------------------------------------|
+| P Class | $2/F_s$ |
+| M Class | $5/F_s$ |
+
+The communication end-to-end latency shall be the reporting latency subtracted from the reporting period. Therefore for different reporting rate, the communication latency is shown in Table 3.
+
+**Table 5.13.1-3: max End-to-end communication latency (ms) at different PMU reporting rate**
+
+| | | | | | | | | | |
+|---------|-------|--------|-----|-----|-------|----|-------|-----|------|
+| | 12 | 15 | 20 | 25 | 30 | 50 | 60 | 100 | 120 |
+| P Class | 83.3 | 66.67 | 50 | 40 | 33.3 | 20 | 16.67 | 10 | 8.3 |
+| M Class | 333.3 | 266.67 | 200 | 160 | 133.3 | 80 | 66.67 | 40 | 33.3 |
+
+### 5.13.2 Pre-conditions
+
+Throughout the wide-area power system, according to the smart-grid application architecture, PMUs and PDCs are deployed at selected locations. A 5G UE is integrated into a PMU or a PDC. They are switched on. According to specified reporting rate, the synchrophasor data is collected, aggregated and made available to the applications accordingly.
+
+### 5.13.3 Service Flows
+
+- 1) In general, a PMU in a wired network can operate in unicast mode and multicast mode. The communication between PMU and its peers in wired networks is usually multicast in spontaneous mode [28] of operation. Thus, while the use case is based on multicast in existing, wired networks, in this use case, we consider 5G technology to be capable of resembling the connectivity needs for the aforementioned spontaneous mode of PMU in a resource efficient way that might not always be multicast but could also be unicast.
+
+- 2) PMUs are configured to operate in spontaneous mode to provide the measurement data to PDCs. According to U's deployment choice, a PDC can make use of data from multiple PMUs and/or from other PDCs.
+- 3) In the grid, some busses may have priority over others, therefore data produced by PMUs deployed at different busses can have different priority too.
+- 4) For a PMU deployed at a given bus in the grid, different types of data are generated to feed different applications of divergent criticality (such as monitoring, control, protection, state estimation, etc.). Also, the same data can be needed by different destinations requiring different QoS treatment. Because of that, these different streams of data is needed by different destinations with different QoS. Additionally, the algorithms a TSO or DSO decides to use further influences the difference in criticality (QoS requirements in other words) of various streams of data this PMU generates.
+- 5) At company U, the automation engineer Antoine is installing PMUs in U's distribution networks according to the PMU-based WAN application design. For each PMU, he configures the data types, calibration factors, and other meta-data for the data that the PMU will send. Antoine also configures the PMU to transmit multiple data streams, each with different content, rate, format, priority. Each data stream shall have its own IDCODE so that the data, configuration, header, and command messages can be appropriately identified. Each stream shall be independently operable including command execution and data, header, and configuration messages.
+- 6) PMUs transmits measurement according to the configured reporting period. Multiple data streams generated by the same PMU are transmitted by the 5G network with different QoS treatment as Antoine has configured on the PMU.
+- 7) PDCs received the synchrophasors, performs configured local processing functions, forwards data further down the hierarchy.
+- 8) Advanced logics in the applications receive the synchrophasors as prescribed, the designed logics such as control, protection and measurement are carried out as expected.
+
+### 5.13.4 Post-conditions
+
+Applications can execute designed logic to perform protection, control and monitor actions per design.
+
+### 5.13.5 Existing features partly or fully covering the use case functionality
+
+1. In TR 22.804, a similar PMU study proposes 10ms end-to-end communication latency.
+2. In TS 22.104, for PMUs synchronization, 1 $\mu\text{s}$ is specified as 5GS synchronicity budget requirement in a service area $< 20 \text{ km}^2$ .
+3. Support of IEEE 1588 PTP is an existing feature. Additional traffic from running IEEE 1588 PTP is around 0.004 Mbit/s.
+4. In TS 22.261, 5G system shall support operation of downlink only broadcast/multicast over a specific geographic area (e.g. a cell sector, a cell or a group of cells).
+5. In TS 22.261, the 5G system shall support downlink parallel transfer of the same content, via broadcast/multicast and/or unicast, such that all receiver group members in a given area receive the media at the same time according to user perception.
+6. In TS 22.261, the 5G system shall be able to apply QoS, priority and pre-emption to a broadcast/multicast service area.
+7. In TS 22.261, The 5G network shall support parallel transfer of multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service to the same UE taking into account e.g. UE capability, radio characteristics, application information.
+8. In TS 22.261, the Ethernet transport service shall support routing based on information extracted from Virtual LAN (VLAN) ID by the 3GPP system.
+
+9. 5G system can provide 5ms with existing 5QI to support the 8.33ms latency as required by the class P PMU with highest reporting rate 120Hz.
+10. In TS 22.261, the 5G system shall support on-demand establishment of unicast, multicast, and broadcast private communication between members UEs of the same 5G LAN-VN. Multiple types of data communication shall be supported, at least IP and Ethernet.
+11. In TS 22.261, the 5G network shall enable member UEs of a 5G LAN-VN to use multicast/broadcast over a 5G LAN-type service to communicate with required latency (e.g. 180ms).
+12. In TS 22.263 (VIAPA), Table 6.3.1-1 includes Note 4 that mentions the UL stream originating from a UE may be the source of a DL multicast stream.
+
+### 5.13.6 Potential New Requirements needed to support the use case
+
+[PR.5.13-001] 5G System should support the IEC 61850-9-3 [7] profile and IEEE Std C37.238-2017 [24].
+
+[PR 5.13-002] 5G system should support at least one of the two profiles for synchrophasor communications: IEC 61850-90-5:2012 [26], or IEEE Std C37.118.2-2011 [28].
+
+[PR.5.13-003] The 5G system should support the IEEE 802.1Q as the QoS profile, as defined in IEC 61850-90-5 [26].
+
+[PR.5.13-004] The 5G system shall support delivery of the same UE originated data in a resource-efficient manner in terms of bandwidth to UEs distributed over a large geographical area.
+
+[PR.5.13-005] The 5G system shall allow a UE to request a communication service to send data to different groups of UEs at the same time.
+
+[PR.5.13-006] The 5G system shall allow a UE to request different QoS for the communication in each of those groups.
+
+## 5.14 Energy Substation Surveillance
+
+### 5.14.1 Description
+
+The use case concerns the use of surveillance cameras in sensitive locations and the implications on telecommunications where that serves as the means by which the surveillance media data is collected in a remote location.
+
+Closed-circuit video (CCTV) is the most bandwidth-intensive of all utility applications. The data rates depend on the required resolution of images, number of colors and frame rate. There are existing standards that reduce this data rate considerably while still providing excellent video quality. During incidents (such as security breaches, equipment malfunctions and power outages,) a higher resolution can be used.
+
+Many utility substations today use fiber optic cables to provide sufficient communications capacity to transport surveillance media data. This use case explores the use of 5G instead either as the sole means for transporting surveillance media data, or as a backup in case the primary means of transport (fiber) has been compromised. This could occur inadvertently if the fixed communication network suffers damage, or intentionally as part of a coordinated local attack that compromises substation security.
+
+While it is often necessary and prudent to transport surveillance media data continuously, there are approaches that reduce this need, e.g. triggers based on motion detectors, tampering (e.g. with cameras, locks, etc.), heat sensors, etc. In addition, video analytics can identify suspicious changes in a field of view within the secure permission, such as people present when they are unexpected, or people present at places within the secure perimeter for too long, etc. In this case, video could be stored locally and only transmitted on demand, or when triggered by an event. The design of a secure facility is beyond the scope of this use case. In any case, there are times in which transport of all surveillance data is needed – so the capacity model is based on this situation. This capacity may only be needed intermittently, for the reasons given above, or it may be required constantly.
+
+Some regulations however, e.g. NERC CIP in North America, require continuous live video transport from cameras monitoring the substation's Electronic Security Perimeter.
+
+Further, given the use of fiber optic cables, the networks are vastly over-provisioned. For this reason, even where regulation does not require constant video media transport for perimeter security, there is a tendency to transport all surveillance media, at all times.
+
+The most common video codecs used are MPEG-2, MPEG-4 and more recently, the Motion-Joint Photographic Expert Group (M-JPEG). The frame rate commonly used is 25-30 video frames per second. The resolutions often used, per the Common Interchange Format (CIF), are QCIF (176x120), CIF (352x240), 2CIF (704x240), and 4CIF (704x480). [16] This reference is 7 years out of date, though, and the current rate used by some energy utilities is now HDTV (1280x720) resolution.
+
+For the purposes of this use case HDTV with continual media transport will be considered as the service requirement, as this is most realistic looking forward in time. $1280 \times 720 \times 8 \text{ bit resolution} \times 30 \text{ frames per second} = 2.4 (10)^7 \text{ bits per second (uncompressed.)}$ For H.264 compression (MPEG-4), this can be transported with 3 Mbit/s.
+
+### 5.14.2 Pre-conditions
+
+The substation has the capacity to generate surveillance data. The utility operator "U" needs for this data to be sent from the substation to a central operation center reliably, so they arrange services with a telecommunications service provider "T" for this purpose.
+
+Surveillance cameras use mechanisms for mechanical panning, zooming and tilting (PZT) so they do not need to be more than high definition (HD).
+
+### 5.14.3 Service Flows
+
+There are two potential service flows.
+
+- a) Continuously transport surveillance media from the substation site to a central operation center.
+- b) When triggered due to local conditions or remote control, transport surveillance media from the substation site to a central operations center.
+
+### 5.14.4 Post-conditions
+
+The substation security has some assurance, as the substation surveillance media data that is generated on the site can be transported reliably to a central operations center.
+
+### 5.14.5 Existing features partly or fully covering the use case functionality
+
+The video rates described below can be supported by 5G. In fact, 4G suffices as a 'backup' mechanism to carry surveillance video data in some existing substations today.
+
+**Table 5.14.5-1: Transport of Surveillance HDTV KPI Requirements**
+
+| Scenario | User experienced data rate (Mbit/s per camera) | Latency (ms) | Reliability % | Connection density | Coverage (km) |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|--------------|---------------|--------------------|---------------------|
+| Surveillance HD camera media | 3 (up 5 if a lot is going on) | (note 1) | (note 1) | ~12/sub-station | >=30km (city range) |
+| NOTE 1: Media transport typically uses a streaming protocol that allows for buffering of media in the event of changes of latency (jitter) or intermittent failure. This may result in transient interruptions of the video stream but does not result in loss of media. For this reason, no KPI target is given for these metrics. | | | | | |
+
+### 5.14.6 Potential New Requirements needed to support the use case
+
+This use case is included for completeness but no new requirements have been identified.
+
+## 5.15 Distributed Energy Resources and Microgrids
+
+### 5.15.1 Description
+
+Distributed energy resources (DER) become more and more important because of its close proximity to the user side and the convenience of complementary energy forms. The potentially large number of DERs have a direct impact on the operation and power trading of the power system, affecting the security, stability and operation efficiency of the system. The concept of microgrid was introduced to aggregate and optimise DER thus reduce the negative impact on power grids. As defined in [31], a microgrid is a self-sufficient energy system that serves a discrete geographic footprint, such as a university campus, a hospital complex, a business centre, or a residential area. Within microgrids there are one or more kinds of distributed energy (solar panels, wind turbines, combined heat & power, generators) that produce its power. In addition, many newer microgrids contain energy storage, typically from batteries. Some also now have electric vehicle charging stations.
+
+The integration of DERs into the energy system cause many challenges into the communication field. The operational conditions of a microgrid may vary rapidly due to DER contribution with low inertia of nonrotating elements and rapid changes in weather conditions (wind and solar radiation) [32]. To incorporate more renewable and alternative energy sources, the communication infrastructure must have the ability to easily handle an increasing amount of data traffic or service requests and must provide a real - time monitoring and control operation of all these nodes. A reliable communication between the system elements is crucial. In fact, any type of communication dependent electrical protection scheme requires robustness, a virtually full-time availability, and strictly bounded latency.
+
+
+
+Figure 5.15.1-1: IEC 61850 communication stack diagram. The diagram shows a layered communication stack. At the top is the IEC 61850 Data Model. Below it is the Abstract Communication Service Interface (ACSI), followed by Specific Communication Service Mapping (SCSM). A dashed line separates the top three layers from the bottom layers. The bottom layers consist of Application (MMS, GOOSE, SV), Presentation (ASN.1), Session (X.225), Transport/Network (TCP/IP), Datalink (Ethernet Link Layer), and Physical (Ethernet Physical Layer 100 Mb/s). A 'TIME CRITICAL' label is placed between the Application layer and the Transport/Network layer, with arrows pointing to the GOOSE and SV paths. An SCL file icon is shown on the right, with an arrow pointing to the IEC 61850 Data Model.
+
+**Figure 5.15.1-1: IEC 61850 communication stack**
+
+When it comes to communications architecture, IEC61850 is a widely accepted standard for automation and equipment of power utilities and DER, specifically for defining protocols for IEDs (Intelligent electronic devices) at electrical substations. IEC 61850 standard specifies the timing constraints for messages typically used in substations (table 5.15.1-1). GOOSE (Generic Object Oriented Substation Events) and SV (Sampled Values) messages are assumed as time critical messages, having the tightest deadlines (maximum allowed transfer time) among all IEC 61850 messages, corresponding to 3 ms. While GOOSE is typically used to transfer information closely related to monitoring and control functions (circuit breaker status etc.), SV is used to transfer numerical samples of current and voltage signals. The SV protocol works on a periodic information transmission model, regularly sending messages at a fixed rate. For protection purposes, the default rate is 4000 or 4800 messages per second for, respectively, 50 or 60 Hz power systems. On the other hand, the GOOSE protocol operates in a sporadic information transmission model, where a continuous flow of data is maintained to increase communication reliability. The typical sizes of GOOSE and SV messages are, respectively, 160 and 140 bytes. GOOSE messages are transmitted at two different modes: 1) Safe operation: 1 message / second (with the bitrate of 1.28 kbit/s); 2) Emergency operation: 32 message / second (with the bitrate of 40.96 kbit/s). SV messages are transmitted at much high rate 4800 message / second (with the bitrate of 5.376 Mbit/s).
+
+**Table 5.15.1-1: Time constraints for IEC 61850 messages [33]**
+
+| Message Type | Example Application | Time Constraint |
+|---------------------------------|-------------------------------------------------------|-----------------|
+| 1A—Fast messages, trip | Circuit breaker commands and states (GOOSE) | ≤3 ms |
+| 1B—Fast messages, other | The same as above | ≤20 ms |
+| 2—Medium speed messages | RMS values calculated from type 4 messages | ≤100 ms |
+| 3—Low speed messages | Alarms, non-electrical measurements, configurations | ≤500 ms |
+| 4—Raw data messages | Digital representation of electrical measurement (SV) | ≤3 ms |
+| 5—File transfer functions | Files of data for recording settings | ≤1000 ms |
+| 6—Time synchronization messages | IED internal clock synchronization | none |
+
+In addition, the increasing number of renewable energy sources and micro-generators as well as the integration of a large amount of DER units in the microgrid has an impact on the scalability and the stability of the communication system. A certain level of redundancy is required in the system, e.g., backup channels, software components and devices, etc. Critical functionalities in a smart microgrid demand high reliability (99.999%) and stringent availability requirement (99.9999%).
+
+The integration of networking and communication technologies in microgrids may cause vulnerabilities of cyber-attacks. In addition, due to the increasing number of distributed energy resources in the grid, the attack targets are also rising, producing more access points to disrupt the grid. Thus, a microgrid needs to be robust against security attacks. Table 5.15.1-2 summarizes the [34].
+
+**Table 5.15.1-2: general security requirements for different communication services [34]**
+
+| Security requirements | Communication services | | | | | Security protocols | | |
+|--------------------------|------------------------|-------|------|---------|---------|--------------------|-------|--------|
+| | MMS | GOOSE | SVs | E2E PTP | P2P PTP | TLS | IPsec | MACsec |
+| Source authentication | MUST | MUST | MUST | MUST | - | X | X | - |
+| Group authentication | - | - | - | MUST | MUST | - | - | X |
+| Hop-by-hop integrity | - | MAY | MAY | MUST | MUST | - | - | X |
+| End-to-end integrity | MUST | MUST | MUST | MUST | - | X | X | - |
+| Confidentiality | MUST | - | - | - | - | X | X | X |
+| Unicast key management | MUST | - | - | SHOULD | - | X | X | - |
+| Multicast key management | - | MUST | MUST | SHOULD | SHOULD | - | - | X |
+
+### 5.15.2 Pre-condition
+
+The central controller(s) and IEDs have been mounted, connected, and configured during commissioning and deployment.
+
+All devices are connected to the 5G network, and the communication is enabled using IEC 61850 standards.
+
+### 5.15.3 Service flow
+
+Communications are enabled via 5G network among the controller devices and IEDs.
+
+SV messages are used to transfer numerical samples of current and voltage signals from Current/Voltage Transformers (CTs/VTs) to IEDs. The SV protocol works on a periodic information transmission model, regularly sending messages at a fixed rate. For protection purposes, the default rate is 4000 or 4800 messages per second for, respectively, 50 or 60 Hz power systems.
+
+GOOSE is typically used to transfer information closely related to monitoring and control functions (circuit breaker status etc.), and GOOSE messages generally transmit binary data such as indications, alarms and tripping signals. For instance, a protection function issuing a trip command requires transfer times below 3 ms and hence, information is directly mapped into a GOOSE message. The GOOSE protocol operates in a sporadic information transmission model, where each message in a GOOSE transmission sequence has an attribute called Time allowed To Live (TTL) that informs the receiver about the maximum time to wait for the next transmission.
+
+For such time critical applications, data is directly mapped to the Ethernet data link layer as GOOSE messages or SVs transmission using connectionless multicast addressing of frames.
+
+### 5.15.4 Post-condition
+
+5G communication runs and the "health" of the microgrid is maintained.
+
+### 5.15.5 Existing features partly or fully covering the use case functionality
+
+There is no specific description of the described use case in the existing SA1 TR/TS, and the KPI requirements are not captured yet. The use case "Distributed automated switching for isolation and service restoration" has been captured in TS 22.104 Annex 2.4.4, while the corresponding performance requirements have been specified in table 5.2-1 "Periodic deterministic communication service performance requirements":
+
+As to the security requirements, there are existing requirements in TS 22.261 clause 8.9 "Data security and privacy":
+
+The 5G system shall support data integrity protection and confidentiality methods that serve URLLC, high data rates and energy constrained devices.
+
+The 5G system shall support a mechanism to verify the integrity of a message as well as the authenticity of the sender of the message.
+
+The 5G system shall support encryption for URLLC services within the requested end-to-end latency.
+
+### 5.15.6 Potential New Requirements needed to support the use case
+
+[PR.5.15-001] The 5G system shall be able to provide periodic deterministic communication with the service performance requirements reported in the tables below.
+
+**Table 5.15.6-1**
+
+| Characteristic parameter | | | | Influence quantity | | | | Remarks |
+|--------------------------------------------------|---------------------------------------------------------------|-----------------------------|----------------------------------------------|---------------------|---------------------------------|-------------------|------------|-------------------|
+| Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum | Service bit rate: user experienced data rate | Message size [byte] | Transfer interval: target value | Survival time | UE speed | |
+| 99.9999 % | – | < 3 ms | 4.5 Mbit/s | 140 | ≤ 1 ms | transfer interval | stationary | 50Hz power system |
+| 99.9999 % | – | < 3 ms | 5.4 Mbit/s | 140 | ≤ 1 ms | transfer interval | stationary | 60Hz power system |
+| NOTE: | UE to UE communication is assumed. | | | | | | | |
+
+[PR 5.15-002] The 5G system shall be able to provide a periodic deterministic communication with the service performance requirements reported in the tables below.
+
+**Table 5.15.6-2**
+
+| Communication service availability | Max Allowed End-to-end latency | Message size [byte] | UE speed | # of UEs | Service Area |
+|------------------------------------------|--------------------------------|---------------------|------------|----------|--------------|
+| > 99.9999 % | < 3 ms | 160 | Stationary | - | - |
+| NOTE: UE to UE communication is assumed. | | | | | |
+
+## 5.16 Protection of DER and grid interconnection
+
+### 5.16.1 Description
+
+Distributed Energy Resources (DER) and microgrid are typical ways to use renewables (e.g. wind, photovoltaic parks, etc.). They are fundamental elements of energy transition that form the pathway toward the global energy transformation to combat the global warming and the climate change. Take European Union as an example, the policy frameworks of EU 2020 Climate & Energy Package (COM/2010/0639), EU 2030 Climate & Energy Framework (COM/2014) and EU 2050 Climate-Neutral Economy (COM/2011/0885) have duly produced EU Climate Laws, EU Emission Trading Systems (ETS) and union strategy to stimulate the transformation. European member states interact with the European Commission to set up integrated National Energy and Climate Plans (NECPs). In many European countries, ENTSO-E grid code (RfG, DCC, HVDC) compliance guidelines for electricity transition framework are applied by energy and utility players with diverse focuses on the energy markets, system operation, and electricity connections.
+
+Worldwide, for similar reasons, the renewable market is flourishing, as government and private sectors willingly encourage its adoption. With more DERs and microgrids maturing to participate in utility grid, their impact on the distribution networks need to be properly addressed. This contribution discusses the interconnection between renewables and the utility distribution network, and proposes the corresponding communication service requirements for protection mechanisms specifically.
+
+Shown in Figure 5.16.1-1 is the ecosystem with existing DSOs and potential new stakeholders such as DER owners, DER operators, and/or DER aggregators. The focus of this paper is the interface for energy transport shown in red dashed lines. This interface includes both power interface (green line) and communication interface (blue line).
+
+
+
+The diagram illustrates a three-part ecosystem. At the top is a circle labeled 'Market parties'. Below it, a dashed horizontal line separates the 'flexibility' layer (above) from the 'energy transport' layer (below). In the flexibility layer, two double-headed arrows labeled 'Flex' connect 'Market parties' to the bottom nodes, with currency symbols (€ \$ ¥ £) next to them. The bottom layer contains two circles: 'DSO/utility distribution on grid' on the left and 'DER/microgrid' on the right. A red dashed rectangle labeled 'Interface energy transport' encloses the connection between these two nodes, which consists of a green line (power interface) and a blue line (communication interface).
+
+Diagram of the new ecosystem showing Market parties, DSO/utility distribution on grid, and DER/microgrid. It illustrates the flow of flexibility and energy transport, with a specific 'Interface energy transport' highlighted between the DSO and DER.
+
+**Figure 5.16.1-1: New ecosystem and the positioning of interfaces**
+
+The "interface energy transport" shown in Figure 5.16.1-1 could be embodied with a single Point of Common Coupling (PCC) illustrated in in Figure 5.16.1-2, where the power grid could be a medium voltage (MV) substation, and the microgrid could be controlled by its own micro-Energy Management System (μEMS). μEMS communicates with the Distribution Management System (DMS) of a DSO. It is worth mentioning that when the microgrid in Figure 5.16.1-2
+
+is replaced with a single DER, the interconnection with the utility power grid can be more precisely called the Point of Connection (PoC).
+
+
+
+Diagram of a microgrid controlled by its own EMS. The diagram shows a 'Power grid' connected to a 'DMS' (Distribution Management System) at a 'PCC' (Point of Connection). The 'PCC' is connected to a 'Microgrid' (enclosed in a dashed red line). Inside the microgrid, there are various energy resources: a solar panel, a wind turbine, a transformer, and several houses (loads). A 'μEMS' (Microgrid Energy Management System) is shown within the microgrid, connected to the 'PCC' via a blue arrow. The 'μEMS' is also connected to 'Sensors' and 'Actuators' within the microgrid via bidirectional communication arrows. The 'μEMS' is also connected to the 'DMS' via a blue arrow.
+
+**Figure 5.16.1-2: Microgrid controlled by its own EMS (Source: DNV GL). A microgrid is a group of interconnected loads and distributed energy resources with defined electrical boundaries that acts as a single controllable entity and is able to operate in both grid-connected and islanded mode [44]**
+
+From the electrical system's safety and operation resiliency point of view, renewables are not just plugged in to feed the utility grid energy. Because of renewable generation's unpredictability (generation with increased variability), connecting DER or microgrid into the public distribution network need to fulfil a number of standards and requirements – to consider the fluctuating capacity flowing into the grid, more bidirectional flows at distribution level, issues like generator synchronization, and operation threshold conditions for voltage and frequency (i.e. under-/over-voltage, under-/over-frequency). Aside from possibly being used for power flow management (e.g. downward dispatch/curtailment trigger, etc.), PCC is also a control reference point for two power systems to interact, including the control of voltage magnitude and frequency regulation, injection and absorption of reactive power by DER, etc. Based on abnormal operation conditions, many regional and international standards have produced guidelines for measurements and specified conditions for triggering protection [42] at the PCC interconnection. In this paper, the focus is on voltage and frequency protection. Tripping in this context is the action to clear abnormal conditions within a specific duration of time. Table 5.16.1-1 lists the required trip time values for different types of possible trips at PCC, based on a number of regional and international standards.
+
+**Table 5.16.1-1 Tripping time under certain abnormal conditions (s). The interconnection protection requirements vary among standards**
+
+| | Under Voltage Threshold 2 | Under Voltage Threshold 1 | Over Voltage Threshold 2 | Under Frequency Threshold 2 |
+|------------------------|---------------------------|---------------------------|--------------------------|-----------------------------|
+| IEEE 1547 Cat I [37] | 0.16 | 2 | 0.16 | 0.16 |
+| IEEE 1547 Cat II [37] | 0.16 | 10 | 0.16 | 0.16 |
+| IEEE 1547 Cat III [37] | 2 | 21 | 0.16 | 0.16 |
+| IEC 63547 [39] | 0.16 | 2 | 0.16 | n.a. |
+| EN 50438 [36] | n.a. | 1.5 | n.a. | n.a. |
+| IEEE 929 [44] | 0.1 | 2 | 0.03 | n.a. |
+| BDEW [42] | 0.3 | 1.5 – 2.4 | n.a. | n.a. |
+
+It does not take much effort to notice that here the tripping time values for DERs are much more relaxed than those for a regular MV/HV substation. That is because for the PCC interconnect, protection functions are required to coordinate with other functions such as frequency ride-through and even ROCOF ride-through, meaning DERs are required to stay "on" for much longer. Furthermore, two thresholds are introduced for DER tripping to prevent it from happening prematurely, which would compromise the stability of the bulk power system.
+
+There are many available algorithms available for an IED to detect abnormal conditions and to further determine whether the tripping conditions are met. More algorithms are based on continuous measurements and comparison of local and remote measurement provided by PMUs. With renewables and DERs proliferating in the distribution networks, decisions on PCCs would need real-time measurements from multiple strategically chosen measurement points in the network.
+
+Purely based on the values in Table 5.16.1-1, it could be true that a PV-owner might opt for CS104 (or even OPC-DA, Profinet) that is simpler and cheaper to deploy. But these protocols are less flexible to support PMU multicast mode. That is where IEC 61850 adds value to the WAN protection mechanisms. In this case, multicast PMU data could be transferred via routable sampled values (R-SV) profile (IEC 61850-90-5). Similarly, the tripping command could be sent out by routable GOOSE (R-GOOSE) profile, or even as normal GOOSE provided the IED with protection functions and the circuit breaker for PCC are in the same LAN. When PMU data is multicast using R-SV profile, the transport should support source-specific advanced route path determination. This mechanism helps to mitigate the DDOS attacks known to multicast group addresses.
+
+### 5.16.2 Pre-condition
+
+A number of wind and PV-parks are connected to the medium voltage substations of a utility DSO. Interfaces including PCCs are established between these systems. P class PMUs are installed at selected busses containing a load. PMUs and IEDs with control and protection functions are connected to the 5G network. The DSO also has a centralized Wide Area Monitoring Protection Automation Control (WAMPAC) application in the control centre. Depending on the control and protection functions, PMUs and WAMPAC can subscribe to different data such as synchrophasor, frequency, frequency and the rate of change of frequency (ROCOF) generated from a specific source PMU. The communication is supported by IEC 61850-90-5 standards.
+
+### 5.16.3 Service flow
+
+Company U operates a large national grid. Thanks to U's existing IP/MPLS infrastructure, PMUs deployed in substations belonging to transmission grid are connected to this IP/MPLS network. The number of PMUs can range from a few hundred to tens of thousands. Each individual PMU continually streams measurement data to a number of PDCs located in control centers at different levels for monitoring and analysis performed by different teams (or analysis by IEDs – Intelligence Electronic Devices with e.g. protection functions). The network engineer Arjen configures in each IP/MPLS router, so that a dedicated VPN is used for transmitting R-SV (routed-Sampled Values) datagrams (Sampled Values can be generated by MU-Merging Unit, but here PMUs are able to generate Sampled Values too). Then, Arjen assigns IP addresses to PMUs from the IP/MPLS network. Due to the high number of PMUs, Arjen configures the IP/MPLS network to efficiently transfer the PMU data to destination PDCs. In the meantime, to improve security, Arjen uses the source specific multicast (SSM) feature to ensure the IP/MPLS network only forwards datagrams to receiving PDCs from only the source PMUs to which the receiving PDCs have explicitly joined. The multicast trees are static once the PMU application is up and running. Worth mentioning is that for each PMU, its corresponding multicast tree is built based on the WAN Smart Grid protection application logics. In other words, the multicast tree reflects where in the Smart Grid the R-SV measurement data from a particular PMU is needed.
+
+With the renewables booming, the distribution grid of company U is connected to an increasing amount of PV parks and wind parks. At and around the interconnections, gradually more new PMUs are deployed. It is impractical to extend the IP/MPLS network physically to all these locations. Therefore, company U decides to make use of the 5G service from an operator KTT.
+
+Now, for U's DERs and microgrids, Arjen again refers to the WAN Smart Grid protection application logics to configure the newly installed PMUs. The purpose is that these PMUs will virtually take part in the existing multicast trees in U's IP/MPLS network. Thanks to KTT's 5G\_LAN service, these PMUs and control centre IP gateways are added to the VPN that Arjen previously configured in the IP/MPLS network. See as the extension of U's IP/MPLS network footprint, 5G delivers the PMUs' datagrams conforming the source-specific multicast a priori.
+
+As a result, 5G network provides communication among the PMUs with PDCs in the control centres. A PMU produces a single source of R-SV measurements, and the 5G network delivers the measurements efficiently to the intended group of recipients.
+
+Suddenly an outage of a distributed generator at a given site causes generation load imbalance (site 1). Similar conditions happen to another distributed generators connected nearby (site 2).
+
+PMUs measure synchrophasors, frequency and ROCOF associated with the fundamental/primary components at various interconnections with DERs.
+
+PMUs multicast measurement data to the subscribers, which could be other PMUs and the WAMPAC.
+
+At abnormal site 1, based on the PMU's locally measured ROCOF, the protection function decides the problem to be a weak load imbalance. So the protection will not be triggered since the frequency is supposed to restore after some time. At other abnormal sites 2, similar decisions are made by the local protection functions.
+
+However, the WAMPAC receives measurement from all of these PMUs. Based on its global view, it detects that area with prevalence of under frequency conditions spread among a number of DERs could potentially cause severe impact on the overall distribution grid. The WAMPAC decides to trip the generators in some of these problematic sites (treating the under voltage condition as severe imbalance), so as to prevent system collapse.
+
+### 5.16.4 Post-condition
+
+5G communication works properly. System collapse is prevented ensuring system resiliency. Additionally, with data measured by PMUs, the DSO has a good real-time view of operation states of DERs and how the energy flows throughout the networks.
+
+### 5.16.5 Existing features partly or fully covering the use case functionality
+
+The communication delay KPIs can be supported by the existing requirements.
+
+### 5.16.6 Potential New Requirements needed to support the use case
+
+[PR.5.16-001] The 5G system shall be able to deliver data originated by a UE to a group of recipient UEs distributed over a large geographical area.
+
+[PR.5.16-002] The 5G system shall allow the originating UE to send data to several groups at the same time.
+
+[PR.5.16-003] The 5G system shall enable recipient UEs to indicate their interest in receiving data from a specific originating UE.
+
+## 5.17 Utility Service Operator M2M service management platform in Smart Energy
+
+### 5.17.1 Description
+
+It is important to understand that this use case is widely present in the DSO networks in many regions across the world. This use case resembles the realistic situation in which a utility M2M system interacts with an MNO for consuming cellular technologies. This use case focuses on how 5G can provide improved management related services offered to DSOs, in the realistic real-life context. To bring context to this paper, the use case of AMI is used.
+
+M2M has existed in DSO networks for a long time. Started with the support by legacy GPRS, CDMA, UMTS and later LTE, smart metering and AMI systems have enjoyed rapid deployment by a DSO to reach their operation and business targets. Not only for metering systems, but also a large number of DSOs have brought cellular connectivity to substations that are remotely located and have relatively less sophisticated Smart Grid applications running. For the sake of clear and comprehensive explanation, the architecture with TCP-UDP/IP communication profile from the DLMS/COSEM UA [46] international standard is referred to, so as to elaborate the topic of the hour in truthful context.
+
+The concept is well-known, a device with a cellular module connects to the target server(s) via cellular connectivity. Figure 5.17.1-1 shows how the utility-adopted DLMS/COSEM standard utilizes this concept.
+
+
+
+Diagram illustrating a TCP-UDP/IP profile based utility M2M system. It shows three host devices connected to a central Network cloud. The 'Host device for Clients' contains two COSEM Client APs (AP\_01 and AP\_02) connected to a wrapper, which is connected to N (Network) layers, then TCP and UDP layers, then IP (163.187.45.19), and finally Data Link and Physical layers. The 'Host\_device\_01 for Servers' contains two servers (Server\_01 and Server\_02) connected to a wrapper, which is connected to M (Management) layers, then TCP and UDP layers, then IP (163.187.45.36), and finally Data Link and Physical layers. The 'Host\_device\_02 for Servers' contains three servers (Server\_01, Server\_02, and Server\_03) connected to a wrapper, which is connected to M (Management) layers, then TCP and UDP layers, then IP (163.187.45.78), and finally Data Link and Physical layers. All three host devices are connected to a central Network cloud. Arrows indicate the flow of COSEM Application Processes and the COSEM Application Layer, and the Protocol Layers of the TCP-UDP/IP profile.
+
+**Figure 5.17.1-1: TCP-UDP/IP profile based utility M2M system illustrating a client reporting to two different head-end servers in the DSO's data centre [50].**
+
+Since the cellular connectivity is provided by an MNO, usually the DSO need to setup a dedicated VPN connection between its own RADIUS server and the MNO's RADIUS (as a proxy) to ensure the DSO's own RADIUS server will be responsible for the E2E authentication of the meters or the Smart Grid terminal devices. Figure 5.17.1-2 illustrates a typical situation, where a DSO called EDL has two separate subscriptions with two mobile operators for the many M2M devices they need to connect. The DSO manages its own RADIUS servers (RADIUS A and RADIUS B) in its own IT domain (e.g. own data centre or in a hosting environment), each RADIUS server has a secure tunnel to the peer RADIUS proxy in the corresponding MNO network (here namely the Operator A RADIUS and the Operator B RADIUS). The mechanism of a DSO's M2M system and the related RADIUS interaction is illustrated in Figure 5.17.1-3.
+
+For the target M2M applications based on the TCP-UDP/IP profile in DLMS/COSEM [47], and the actual existing M2M management platform widely adopted in DSO's utility M2M infrastructure, it is very important for the DSO to expect successful data connection fulfilling the application's communication needs, as agreed in the SLA. In reality, even the most recently known metering applications in the European Union is the 15-minutes reading cycle [48]. That means, the successful meter reading as required by legislation is changing from once a month, to recently once a day and in the future once every 15 minutes. For a DSO's M2M head-end server, Smart Grid sector specifications have standardized wake-up mechanisms for the head-end server to contact the end devices for data retrieval, so that the data can be fetched within the service window determined by a specific business process. Realistically speaking, if the data must be available every 15 minutes, then the M2M service administrator has sufficient time (roughly a 15-minute window in this case) to trigger this wake-up process multiple times for retrieving the data. Another well-used resort has been that the DSO uses APIs of the MNO's SIM management platform to "reanimate" the device back to the mobile network connectivity by means of mechanisms such as reattach and re-registration.
+
+
+
+Diagram of DSO EDL's management platform of MSM service. The diagram shows a central 'EDL's M2M Management Tool' connected to two main network paths. The left path leads to a cloud labeled 'Management VLAN of DSO EDL', which contains 'VLAN X' and 'VLAN Y' (each with a firewall icon) and two RADIUS servers labeled 'RADIUS A' and 'RADIUS B'. The right path leads to a cloud labeled 'EDL's Intranet' (with a firewall icon), which is connected to a 'Public Network' cloud. Below the Public Network are two RADIUS servers labeled 'Operator A RADIUS' and 'Operator B RADIUS', each preceded by a firewall icon.
+
+**Figure 5.17.1-2: DSO EDL's management platform of MSM service. EDL has two subscriptions to two mobile operators.**
+
+From the experience of some DSOs, it has happened that some M2M systems relying on 2G/3G connectivity did lose contact with the head-end server(s) for hours or even for days, and sometimes a wake-up push message manually sent from the head-end might also fail in getting the M2M device back online (w.r.t connectivity). Apparently, the most and foremost target of 5G is to focus on how to provide more reliable connectivity to the M2M devices, through enhancement of technology evolution, and introduce adequate quality assurance mechanisms to add to warranty. In respect of this, the 5G technology already introduces ground-breaking improvement in connectivity KPIs including reliability.
+
+Equally important, as the industry-wide wake-up procedure goes, a service maintenance personnel of a DSO might look into their RADIUS server to check the session establishment status. This process has been in existence, ever since legacy cellular technologies were used. But this manual process has been labour-intensive and at times impractical for utility the personnel, who in general do not always have sufficient mobile telecom expertise to analyse the RADIUS call flows. Therefore, it makes sense for a 5G operator to inform the DSO in easy-to-comprehend terms of the following information on a per-M2M-device basis:
+
+- RADIUS session setup information
+- Device session status information
+- Device session setup success rate
+
+Exposing these information during M2M service trouble-shooting can effectively improve the DSO's incident management process.
+
+Certainly the M2M systems and applications will continue to proliferate in utility network. The reliance on 5G technology encourages the telecom providers to provide more relevant performance and events data to the DSOs. The genuine pursuit of a DSO is that by means of effective reporting the DSO obtains timely information and advice on maintaining resilient operation of their utility grid and services. This basically includes the following:
+
+- 5G should introduce to an MNO means to keeping track of the offered connectivity's status, and to abide by the factually contracted service KPIs (incl. availability) in the SLA;
+- 5G should enable notifying a DSO in time the events related to MNO-planned maintenance (e.g. time period and impacted cell sites), for the DSO to timely adjust its service operation;
+- 5G should enable reporting to a DSO the forecasted performance degradation over a specific geographic area (e.g. a cell sector, a cell or a group of cells).
+
+
+
+```
+
+sequenceDiagram
+ participant SM as Smart Meter
+ participant MS as M2M system
+ participant R as Radius
+ participant App as Application
+
+ SM->>MS: APN login
+ MS->>R: Radius authentication
+ R-->>MS: Radius authentication response
+ MS->>R: Radius accounting start
+ R-->>MS: Radius accounting response
+ MS->>SM: IP address
+ MS->>App: Meter session start
+ App-->>SM: Push message
+ MS->>App: Meter session end
+ App->>MS: Application session
+ MS->>App: commands
+ App-->>MS: results
+ MS->>App: Application session end
+ SM->>MS: End GPRS session
+ MS->>R: Radius accounting stop
+ R-->>MS: Radius accounting response
+
+```
+
+Sequence diagram illustrating a typical utility M2M management mechanism. The diagram shows interactions between four entities: Smart Meter, M2M system, Radius, and Application. The sequence starts with the Smart Meter sending an APN login to the M2M system. The M2M system then sends a Radius authentication request to the Radius server, which responds with a Radius authentication response. The M2M system then sends a Radius accounting start to the Radius server, which responds with a Radius accounting response. The M2M system then sends an IP address to the Smart Meter. The M2M system then sends a Meter session start to the Application. The Application then sends a Push message to the Smart Meter. The M2M system then sends a Meter session end to the Application. The Application then sends an Application session to the M2M system. The M2M system then sends commands to the Application. The Application then sends results to the M2M system. The M2M system then sends an Application session end to the Application. The Smart Meter then sends an End GPRS session to the M2M system. The M2M system then sends a Radius accounting stop to the Radius server, which responds with a Radius accounting response.
+
+**Figure 5.17.1-3: Illustration of a typical utility M2M management mechanism [50], implemented ubiquitously in currently available commercial M2M systems for utility operators.**
+
+### 5.17.2 Pre-condition
+
+1. A DSO "UT" has a service contract with an MNO "TEL" for supporting its M2M services. In the service contract, UT and TEL have agreed on the SLA covering many aspects including the following:
+
+- Justification of business needs
+- Business process already in place on UT (the customer side)
+- Desired outcome of the connectivity service in terms of e.g. availability, reliability, performances, etc.
+- The classification of incidents (w.r.t. urgency etc.), and per classification the required response time, MTTR, and relevant information exposure if specifically requested.
+
+2. UT has its ITIL process in place, of which the incident management process is expected to speed up incident resolution while minimizing operational and customer impact, in an efficient and cost-effective manner.
+
+3. For event reporting and management related information exchange, UT and TEL have invested in setting up the infrastructure, which includes a secured highly-reliable BW-abundant OOB transport tunnel, secure interfaces (incl.
+
+layers across physical, VPN, APIs), and paid and governed by UT a special data collection and storage infrastructure (data centre or in the cloud) scaled properly to contain and store the exposed data from TEL, etc. UT is obliged by the CTO and the CFO to carefully consider the cost of such infrastructure.
+
+4. M2M system of UT is up-and-running on 5G. The procured 5G service with provisioned availability provides reliable connectivity with sufficient performance to the M2M application.
+
+### 5.17.3 Service flow
+
+- 1) Pieter-Jansen is the M2M service administrator at UT. Every day his primary job is to monitor the service status of the applications underpinning the M2M service. Pieter-Jansen uses the GUI to check application status, and whether the M2M data has arrived in the head-end systems before the service window closes (e.g. new data should arrive in the system from an M2M device every 15 minutes). This is normally the case, and Pieter-Jansen could spend time learning UT's business processes related to this M2M service.
+- 2) One morning while Pieter-Jansen arrives at work, eager as he always is he logs in the service manager portal to take a quick glance of the M2M service status collected last night. Frowning, Pieter-Jansen notices the GUI of the head-end system alerts missing data from a particular M2M device --- data missing for several continuous service cycles (e.g. 120 data points missing in the past 8 hour). Pieter-Jansen has the admin login credential to UT's RADIUS server, however, Pieter-Jansen is not specialized in telecom and has not gained experience in the corresponding IEEE protocols. His supervisor, one of the very few personnel at UT who understands both electricity and telecom was unfortunately under the weather and had called in sick. Pieter-Jansen therefore switches to the GUI that visualizes RADIUS session status in the historian with the data received from TEL's RADIUS servers. The data from TEL is translated in layman's terms, hence Pieter-Jansen easily understands that the authentication process of this M2M device has failed due to wrong credentials.
+- 3) Pieter-Jansen goes on to check the logbook whether any recent changes have been introduced in UT's M2M system. He realized for this particular M2M device, the corresponding credential at the RADIUS server has been updated by the administrator of the RADIUS server at UT. Hence Pieter-Jansen calls that personnel to revert the credential. This M2M device soon comes back on the network and resumes to deliver data to the M2M head-end server.
+- 4) Time goes on, summer holiday arrives and lots of people are leaving for the passionate south. TEL usually plans network maintenance services during this period. However, since TEL and UT have an SLA in the contract, TEL informs UT of the network activity and the perceived interruption of mobile service.
+- 5) UT checks that the service interruption is within the availability window of the telecom service, and UT can timely inform the customers when the M2M service is expected to be unavailable. This process is agreed beforehand and is conformant with the grid code of the country where UT operates.
+- 6) Therefore, UT confirms with TEL the acceptance of the period for the planned network maintenance to be carried out by TEL.
+- 7) UT fulfils its role as public sector service provider conforming the national norm. TEL provides 5G service that fits UT's actual needs with minimal burden on the customer side.
+
+### 5.17.4 Post-condition
+
+UT is able to provide to their customers the M2M services both during incidents and over time.
+
+### 5.17.5 Existing features partly or fully covering the use case functionality
+
+TS 22.261 Table 7.5-2-1 captures performance requirements for high availability IoT traffic.
+
+Under normal conditions, 5G service performance KPIs regarding bandwidth, delay, jitter, and availability are sufficient for utility M2M applications.
+
+5G system can provide periodic performance reporting, the corresponding report interval can be configured by the application layer.
+
+TS 22.261 clause 6.1.2.2:
+
+The 5G system shall support means by which the operator can differentiate policy control, functionality and performance provided in different network slices. Therefore, the M2M service performance KPIs could be provided by means of network slicing.
+
+TS 22.261 clause 6.23.2:
+
+The 5G system shall provide a mechanism for supporting real time E2E QoS monitoring within a system.
+
+The 5G network shall provide an interface to application for QoS monitoring (e.g. to initiate QoS monitoring, request QoS parameters, events, logging information).
+
+The 5G system shall be able to log the history of the communication events. This includes for examples parts of the SLA that are not met, time-stamp of the events, and event position (e.g. UEs and radio access points associated with the events).
+
+The 5G system shall support different levels of granularity for QoS monitoring (e.g. per flow or set of flows).
+
+The 5G system shall be able to provide event notification upon detecting error that the negotiated QoS level cannot be met/guaranteed.
+
+The 5G system shall be able to provide information that identifies the type and the location of a communication error. (e.g. cell id).
+
+The 5G system shall be able to provide notification of communication events to authorized entities per pre-defined patterns (e.g. every time the bandwidth drops below a pre-defined threshold for QoS parameters the authorized entity is notified and event is logged).
+
+The 5G system shall be able to respond to a request from an authorized entity to provide real-time QoS monitoring information within a specified time after receiving the request (e.g. within 5s).
+
+The 5G system shall be able to provide statistical information of service parameters and error types while a communication service is in operation.
+
+The 5G system shall provide information on the current availability of a specific communication service in a particular area (e.g. cell id) upon request of an authorized entity.
+
+### 5.17.6 Potential New Requirements needed to support the use case
+
+[PR.5.17-001] Based on MNO policy, the 5G network shall provide suitable means to expose to a trusted third party the communication network performance parameters
+
+[PR.5.17-002] Based on MNO policy, the 5G network shall provide suitable means to proactively inform a trusted third party of possible events that could interrupt or cause performance degradation of the 5G service over a specific geographic area (e.g. a cell sector, a cell or a group of cells).
+
+## 5.18 Coordination for Energy Recovery Use Case
+
+### 5.18.1 Description
+
+Utilities (DSO) make use of both Private and Public Wireless networks as access technologies for Smart Grid assets providing Smart Grid services, some of which can have a high level of criticality.
+
+Public cellular networks are sometimes the only option to provide remote access to Distribution Automation (DA) assets.
+
+Remote access to DA assets in a fault situation causing a power outage is a necessary condition to isolate the fault and restore the service promptly.
+
+In order to guarantee high availability, the communication system providing remote access to the Smart Grid assets needs an uninterruptable power supply.
+
+When DA assets are connected by means of Public 3GPP networks, they are typically served by a Node located in the proximity of the fault and hence affected by it because it happens to be fed by the faulty power line.
+
+Power autonomy of cellular nodes is a key variable of a fault scenario in order to guarantee the correct and prompt resolution of the issue and the service recovery. Power autonomy of the mobile telecommunication system nodes is a variable that escapes the control of the DSO and relies exclusively on MNO's policies and 'implementation'.
+
+A standard communication flow between parties would enable mutually beneficial coordination towards energy recovery. Both MNO and DSO could adapt their processes to the existing constraints,
+
+### 5.18.2 Pre-conditions
+
+Utility "U" has a significant percentage of Distribution Automation assets connected by Public cellular services. U relies on MNOs A and B for 5G services.
+
+Distribution Automation is considered a critical service requiring high availability.
+
+Cellular routers that enable remote access to the assets have dual cellular configuration in order to provide an extra level of redundancy and availability. This configuration enables a backup cellular connection with MNO B in case of failure of MNO A.
+
+Access to Distribution Automation assets such as reclosers or SCADA switches must be available in a fault situation in order to restore the service. If the 5G node providing cellular coverage to the connected Smart Grid asset is fed by a line affected by the fault and the Node does not have an adequate UPS that enables access to remote operations to restore the fault, the loss of connectivity and the corresponding loss of remote control of the asset is inevitable.
+
+DSO and MNO have an available channel for communication of energy outage incidents. This channel is bidirectional. The MNO can be made aware real time of an incident affecting DSO's distribution network with a result of power failure affecting MNO's Node(s) serving the Smart Grid asset. The communication channel can also inform the DSO of the MNO's autonomous power status in areas affected by energy outage.
+
+### 5.18.3 Service Flows
+
+Remote access and operation of Distribution Automation assets is performed from the Energy Control Center (ECC). Charles is an operator working at the ECC.
+
+Service flow 1.
+
+- Charles observes a service interruption caused by a faulty power line. The power outage affects a significant number of customers in an urban area. In order to isolate the issue and restore the service to the affected customers, Charles needs to access a recloser (Distribution Automation Smart Grid Asset) connected by means of a cellular router served by MNOs A and B.
+
+Service flow 1, alternative 1:
+
+- Remote Access to the recloser is possible but, after a short period of time, the connection is lost as both MNOs A and B's facilities in proximity of the energy outage have exhausted their autonomous power reserves.
+- The fault cannot be isolated remotely in time and in order to restore the service to customers, field crews need to be mobilised for onsite operation. Restoration time increases dramatically.
+
+NOTE: If the power outage only affected one of the MNOs (e.g. A) providing coverage to the site where the DSO would apply DA to end the outage, then the other MNO (e.g. B) could provide communication service to enable the DSO to restore service.
+
+Service flow 1, alternative 2:
+
+- U is informed by MNOs A and B that cellular Nodes serving the router suffered a power outage coincident in time with U's power line fault event.
+- Both A and B inform U that their nodes have UPS with very limited capacity.
+
+- 1.2.3 Using information from U, the MNOs A and B have information that they can use to conserve the limited power capacity and enable U to communicate with the site of the fault.
+
+#### Service Flow 2.
+
+Some days later, a storm situation causes a service interruption in a rural area. The recloser located closest to the fault is connected by means of Private Wireless connection. Private Wireless repeater site is owned and maintained by U. Power autonomy in the repeater site is appropriately dimensioned to meet U's needs according to operations parameters. The access to the recloser is possible and the fault can be solved in a minimal time with no service interruption to final customer in the area.
+
+### 5.18.4 Post-conditions
+
+The outcome of Service Flow 1, alternative 1 is unfortunate because it causes a lengthy service interruption for both energy and telecommunications service.
+
+The outcome of Service Flow 1, alternative 2, allows this situation to be avoided. As the DSO and MNO have a standard channel for communication of energy outage incidents, they are both able to plan and execute recovery effectively.
+
+The DSO can provide locality, communication requirements and estimated time of repair of an issue in DSO's Distribution network. The MNO can use this information, especially the recovery schedule, the location and the communication requirements, to enable remote access to the Smart Grid asset that will solve the issue.
+
+For example, in the event of a service interruption or outage affecting a 5G node with a limited power autonomy, the Node has access to information coming from the Network so that it is able to detect the root cause of the problem and react accordingly. The Node is able to efficiently manage the resources and prioritize granting access to U's traffic. All the rest of processes that are not strictly necessary to the final aim of serving U's need of cellular resources become dormant.
+
+MNO will inform DSO of the Power autonomy and location of the Node serving the Smart Grid asset that needs to be accessed for remote operations. The DSO will react accordingly, adjusting the operations taking into account the MNO communication constraints.
+
+Thus, both parties will react accordingly, adjusting their processes to facilitate the resolution of the issue. U is able to successfully restore the issue affecting the line remotely so that the Node recovers the power supply after a short period of time. Once Power supply is back to normal, 5G node can resume its normal processes.
+
+Energy system comes back online, taking into consideration the timing and UPS resource constraints of both MNO and DSO, as well as the locality of the incident. This is a marked improvement of the current system in which for availability considerations DSOs cannot rely upon mobile telecommunications for recovery with building a redundant infrastructure. This reduces the applicability of mobile telecommunications infrastructure to support energy utility communication.
+
+Another alternative, shown in Service Flow 2, is that the MNO provisions their UPS resources sufficiently to suffer loss of service in the event of an energy system outage for a sufficiently long period of time to enable the DSO to restore service. The provisioning of the UPS can be informed by the outcome of past energy outage incidents, as well as historical information exchanged as per Service Flow 1, alternative 1 and 2 – as lessons learned.
+
+### 5.18.5 Existing features partly or fully covering the use case functionality
+
+Network slicing and QoS implementation in 5G networks enable the identification of DSO's service criticality.
+
+### 5.18.6 Potential New Requirements needed to support the use case
+
+[PR.5.18-001] Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the uninterruptable power supply status of the MNO's infrastructure, specifying which physical regions would be affected in terms of physical topology, as this information will facilitate energy system recovery operations.
+
+[PR.5.18-002] Subject to regulatory requirements, the 5G system shall support a mechanism by which a third party can communicate the energy system recovery status in terms of location and time table to the MNO, as this information will facilitate MNO operations to facilitate energy system recovery.
+
+NOTE: It is assumed that once aware of the proximity and duration of the energy outage, the MNO may manage the 5G Nodes affected by the outage to make use of the power autonomy remaining in the 5G Nodes, e.g. prioritizing the delivery of resources to support the energy system operations communications. Power consumption for energy system operations must be optimized so that the service recovery can be remotely orchestrated by the energy utility.
+
+## 5.19 Applications Using IEC 61850-9-2 Sampled Values
+
+### 5.19.1 Description
+
+As electric grids are expanding, there is an increasing need for fault detection and location as well as maintaining system stability in real time which requires precision timing. There is also a raising interest to have other clock synchronization sources in addition to GNSS.
+
+IEC 61850-9-2 standard [49] specifies the protocol for transmitting measurement information in a power system using Ethernet. Standard also recommends the use of PTP (Precision Time Protocol) for clock synchronization and IEC 61850-9-3 standard [7] shall be followed whenever PTP is used. PTP accuracy is affected by network structure and devices in the network. Since different types of clock devices produce different time errors and jitters, overall time inaccuracy must be verified to make sure that application time accuracy requirements are fulfilled. Requirements in IEC 61850-9-3 [7] aim at achieving a network time inaccuracy better than 1 $\mu$ s after crossing 15 transparent clocks or 3 boundary clocks. PTP profile for power utility automation defines the inaccuracy as follows:
+
+**Table 5.19.1-1. Allowed inaccuracy defined by IEC 61850-9-3 [7]**
+
+| Clock type | Inaccuracy |
+|------------------------|------------|
+| Transparent clock (TC) | < 50ns |
+| Boundary clock (BC) | < 200ns |
+| Grandmaster clock | < 250ns |
+
+Grandmaster clocks in substations today use a GNSS receiver to achieve accurate clock synchronization with holdover time even up to 24h (corresponding to <1 $\mu$ s accuracy). However, since the time source (GNSS) may become unavailable due to failure (e.g. broken antenna, satellite availability or interference), 5G is a candidate resiliency solution (see [51] clause 5.2). In order to reach the same level of measurement accuracy, 5G capable grandmaster clock should fulfil the requirement of maximum 250ns inaccuracy when its timing reference is used in the same location as of the Grandmaster clock that is used to synchronize the Smart Grid devices over Ethernet.
+
+Synchronization requirements are related to various aspects. In particular, IEC/IEEE 60255-118-1:2018 [50] defines a Phasor Measurement Unit (PMU) that must maintain less than a 1% total vector error (TVE). Such error includes time, phasor angle, and phasor magnitude estimation errors. Standard also recommends that a time source that reliably provides time, should be at least 10 times better than values corresponding to 1 % TVE. Therefore IEC 61850-9-3 [7] should be followed whenever substation has PMUs either as standalone devices or PMU capable protection relays.
+
+By using PTP within a substation the system can have multiple grandmaster capable clocks which, in case of failure of the current grandmaster, can be used to maintain accurate time between devices and processing sampled values. However, when sampled values are processed outside the substation, time inaccuracy limits defined by IEC 61850-9-3 [7] must be followed since the devices are not connected to the same grandmaster clock and therefore measurement timestamps may have too much inaccuracy. Application outside substation may be but not limited to Wide Area Protection.
+
+### 5.19.2 Pre-conditions
+
+A Smart Grid operator utilizes 5G wireless communications across primary and secondary substations. These communications report events and error detection recordings to a centralized monitoring station. Accurate time stamping across the sources is essential to provide a clear picture of the system. As outages in one area may have impact throughout the system, the 5G system may be used as a supplement to (e.g., integrated as alternative radio in the grandmaster clock) or as an alternative grandmaster clock. As a capable grandmaster clock, the 5G system should fulfil the accuracy requirements defined by IEC 61850-9-3 [7].
+
+### 5.19.3 Service flows
+
+Sensors across the secondary distribution centres provide timestamped event reporting to a centralized monitoring system. Each event is timestamped to aid in analysis.
+
+The 5G system and the Smart Grid operator have 5G wireless communications configured across the Smart Grid network. Each source uses the same master clock and communicates over the 5G system, timestamps on the recordings are aligned for accurate analysis to be done at a centralized point.
+
+Additionally, the 5G system will need to be compatible with requirements from IEC 61850-9-3 [3] when used in conjunction with GNSS for a timing service in a Smart Grid environment.
+
+- Power system time accuracy from time source (ex. GNSS or UTC) to 5G end device when used as part of IEEE 1588 PTP sync device is 1 $\mu$ s (absolute time-synchronization in substation local area networks IEC 61850 Sample Values).
+- For a 5G system entity acting as a PTP grandmaster in a subsystem, 250 ns accuracy applies between time source (ex. GNSS or UTC) and 5G end device.
+
+### 5.19.4 Post-conditions
+
+The Smart Grid can use 5G system as a supplement or backup to their GNSS receiver based (or wired) clock synchronization systems to improve accuracy and availability of the clock synchronization across the Smart Grid.
+
+### 5.19.5 Existing feature partly or fully covering use case functionality
+
+Rel-16 and Rel-17 requirements cover a good portion of the accuracy requirements for a 5GS timing resiliency system, including:
+
+- Capability to meet 5GS synchronicity budget of $\leq 900$ ns (factory) to $< 1$ $\mu$ s (wide area) as defined for Industry 4.0 applications in TS 22.104 [65]
+- Propagation delay compensation, to ensure that clock synchronization can be conducted accurately across wide area deployments needed for power sub-station support
+- Support for IEEE 1588 PTP [23]
+- Clock synchronization to UTC leveraging 5G system C-Plane and/or U-Plane
+
+### 5.19.6 Potential new requirements and KPIs
+
+#### 5.19.6.1 Potential Requirements
+
+[PR.5.19-001] The 5G system shall support a clock synchronicity budget requirement in a range between 1000 ns (when the timing reference is directly provided to the end station) and 250ns (when acting as a PTP grandmaster of the existing Ethernet-based synchronization network with up to 15 transparent clocks or 3 boundary clocks).
+
+#### 5.19.6.2 Potential KPIs
+
+**Table 5.19.6.2-1: Clock synchronization service performance requirements**
+
+| User-specific clock synchronicity accuracy level [6] | Number of devices in one Communication group for clock synchronisation | Clock synchronicity requirement (note 1) | Service area | Scenario |
+|------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------|--------------|----------|
+|------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------|--------------|----------|
+
+| | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 4 | Up to 100 UEs | <250ns - 1 µs [7] | < 20 km 2 | Smart Grid:
Synchronicity between sync master and PMUs
This range covers the extreme cases where the
PTP clock in the end device uses 5G sync modem as direct time-source (1 µs)
The 5G sync modem acts as PTP GM or 5G sync modem provides PPS output to PTP GM at the top of the Ethernet based synchronization chain with up to 15 transparent clocks or 3 boundary clocks (250 ns).
|
+| 4a | Up to 100 UEs | <10-20 µs [64] | < 20 km 2 | Smart Grid: Power system protection in digital substation with merging units, line differential protection and synchronization |
+| 4b | Up to 100 UEs | <1 ms [64] | < 20 km 2 | Smart Grid: Event reporting and Disturbance recording use-cases |
+| NOTE 1: The clock synchronicity requirement refers to the clock synchronicity budget for the 5G system, as described in Clause 5.19.6.1. | | | | |
+
+## 5.20 Use case of power distribution grid state estimation service
+
+### 5.20.1 Description
+
+The State Estimation (SE) service [52] supports the monitoring of the power grid. The goal of SE is to create insight into the operational state of the power network at any given instant in time, by processing the measurement information collected by the instrumentation deployed in the field. The SE service provides monitoring data which can be used by grid operators to assess the performance of their network and to detect possible anomalies in the grid operation. In addition, it can serve as an input for more complex management functions implemented by the Distribution System Operators (DSOs) to more reliably and efficiently operate. An example of a service which could use the SE monitoring data is the power control service [52]. Other services which could use the SE monitoring data include, but are not limited to, network topology reconfiguration, Volt-VAR control and, in the future, demand side management and demand response services.
+
+### 5.20.2 Pre-conditions
+
+The measurement devices are deployed in the field and capable to send the data to the DSO control centre (or whatever data concentrator).
+
+### 5.20.3 Service flows
+
+#### 5.20.3.1 Introduction
+
+The SE service relies as input on the information of the electric grid topology, the electric line parameters and the real-time measurements provided by the instrumentation deployed on the field. Given this set of inputs, the SE service processes the received data to provide the most likely operating state of the network at the considered instant of time (the same time at which the measurements are collected). Finally, the results of the SE service are sent to the control centre (or whatever data concentrator) to give situational awareness to the DSO and, if needed, are made available for other control functions requiring this information. SE results are usually also stored in a database for possible a posteriori analysis.
+
+For its operation, the SE service thus needs as input some important information of the grid characteristics, the deployed measurement infrastructure, as well as the real-time measurement data collected from the measurement units in the field. In addition, if the electric grid is reconfigurable (i.e. topology changes can be applied), the status of the switches and breakers should be also provided in input to the SE tool to make sure that the service is always considering the correct topology of the grid.
+
+Beyond the grid data, which can be determined by the DSOs with a different degree of accuracy as the information of low voltage grids may be incomplete and inaccurate, the key point for enabling the SE service is the availability of measurement devices with real-time communication capabilities. Different from the transmission system, where a large coverage of devices is often available, the instrumentation penetration at the distribution level is usually poor with only few devices installed in specific points, like primary substations (high/medium voltage substations). As a matter of fact, the main power system requirement to enable the grid monitoring via SE is thus the deployment of devices providing the needed measurement data. Due to the large size of the distribution grids and obvious economic constraints, guaranteeing a full observability of the grid is mostly impractical and hardly achievable. The SE solution duly takes into account this aspect and aims at enabling the SE service using only few low-cost measurement devices deployed at strategic points of the grid (chosen by means of ad hoc meter placement strategies). Moreover, the conceived SE solutions are designed to maximize the accuracy performance even in presence of few measurement units in the field. However, it is worth noting that the accuracy of the estimation results strongly depends on the number of available measurements.
+
+#### 5.20.3.2 Power system requirements of SE service
+
+Needed components in the field: sensors and meters.
+
+Information about the electrical grid: topology of the network; grid parameters (line impedance, transformer data, etc.); nominal power of connected loads and generators; location of the meters.
+
+Type of measurements: voltage (both magnitude and phase angle), current (both magnitude and phase angle), active and reactive power are the measurements that can be used for SE purposes (it is not mandatory to have all the types of measurements reported).
+
+Measurements number: the higher the number, the better the results.
+
+Measurement accuracy: the higher the better; information on the uncertainty characteristics of both sensors and measurement units has to be known.
+
+Measurement synchronization: highly recommended.
+
+Additional data needed from the field: notification of switching events leading to a change in the network topology.
+
+Real-time communication capability: yes, required.
+
+Bi-directional communication: not required; the communication flow is mono-directional from the meters to the control centre.
+
+Use of edge cloud. The concept of SE is based on a distributed architecture where both low voltage and medium voltage grids are divided in multiple, smaller areas. This is a solution to reduce the computational cost and execution time of the SE service, as the SE analyses for all areas may operate in parallel. One benefit of this solution is guaranteed scalability
+
+of the proposed architecture for SE. Given this framework, it is highly feasible that each local SE runs on a dedicated edge cloud.
+
+### 5.20.4 Post-conditions
+
+The operating state of the network provided to DSO at a given instant of time.
+
+### 5.20.5 Existing feature partly or fully covering use case functionality
+
+Table 5.20.5-1 shows communications requirements for the State Estimation service.
+
+**Table 5.20.5-1: Communications requirements of SE service**
+
+| Characteristic parameter | | | | Influence quantity | | | | | |
+|------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------|------------------------------------|------------------------------------------------------|--------------------------------|-----------------|--------------------------------|----------------------------------------------------------------|
+| Comm-
unication
service
availab-
ility:
target
value | Comm-
unication
service
reliabilit-
y: mean
time
between
failures | End-to-
end
latency:
maximu-
m
(notes 1,
2) | Service
bit rate:
user
experien-
ced data
rate
(note 2) | Message
size [byte]
(note 2) | Transfer
interval:
target
value
(note 2) | Surviva-
l time
(note 2) | UE
speed | # of
UEs | Service
area |
+| 99.99% | | 100 ms
to few
seconds | ~ 5 kbit/s | < 1000 | 1 s | | Statio-
nary | < 30
per
km 2 | several
km 2 up to
100,000
km 2 |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node) rather than two wireless links (UE to UE).
+NOTE 2: It applies to UL.
+
+### 5.20.6 Potential New Requirements needed to support the use case
+
+None.
+
+## 5.21 Use case of power distribution grid power control service
+
+### 5.21.1 Description
+
+The Power Control (PC) service [52] optimises the management of the distribution grid power flows (at both medium voltage and low voltage level) for preventing possible contingencies, such as violation of the voltage limits, and overloading of grid components. The service also fosters a more efficient and reliable system operation. This is obtained through the smart control of the active and reactive power injected (or consumed) by converter-based components connected to the grid, such as Distributed Generation (e.g. photovoltaic plants, wind turbines) and energy storage units. For the management of the Distributed Generation based on renewable energy sources, an additional objective is to maximize the use of green energy while respecting the operational constraints of the electric grid, thus minimizing as much as possible the power curtailment of renewable generation. The use of smart power control service in the power grid with high penetration of renewable energy sources is expected to significantly improve the efficient operation of the grid, the power quality, and the grid reliability. This service can be defined as an "active service", since it actively acts on some of the power system components to modify their operation.
+
+### 5.21.2 Pre-conditions
+
+The State Estimation service (see clause 5.20 "Use case of power distribution grid state estimation service" above) is deployed and active in the power distribution grid. Output of the State Estimation service can be used by the PC service.
+
+### 5.21.3 Service flows
+
+#### 5.21.3.1 Introduction
+
+The developed PC service is based on the operating conditions of the grid and processes this information to determine the optimal setting of active and reactive power generation for the distributed generation or, when available, of storage units. Different goals can be pursued to enhance the operation of the distribution grid, such as: the reduction of power losses during the operation with normal conditions; the minimization of voltage unbalance in case of high differences in the status of the three phases of the system; the minimization of possible active power generation curtailments during circumstances with over-voltage issues in the grid. The output of the PC service is a list of set points of active and reactive power (PQ set points) for the converter-based components connected to the grid. Consequently, the service needs bi-directional communication with the field to ensure proper delivery of the generated control commands.
+
+The design of the PC service is coupled with the State Estimation service. According to this idea, the PC service takes as input the results of the State Estimation service, namely the voltage profile at the different buses and the information about the branch power flows and the power consumption (or injection) at the nodes. Together with this information, the service needs as input also the model of the electric grid, expressed in terms of network topology and line characteristics. More specifically, the list of inputs needed to enable the PC service includes the following data.
+
+Static grid data:
+
+- Electric grid topology (information about the nodes and the connection among the different nodes in the grid).
+- Electric component parameters (e.g. impedances of the lines, impedances of transformers, etc.).
+
+Real-time data:
+
+- Estimation of the bus voltages, power flows in the branches, power consumption or injection at the nodes (as provided by the State Estimation service).
+- Real-time notification of a change in a switch or breaker status.
+
+The output of the PC service is the pair of active and reactive power set points for each converter-based component in the grid. The output of the power control service has to be sent to the converters in the field through communication technologies available in the field for control commands. Results can also be sent to the control room of the Distribution System Operator (DSO) for monitoring and can be stored in the database for possible a posteriori analysis.
+
+Since the PC service relies on the results of the State Estimation service, some of the power system requirements for this service are in common with the State Estimation service. First, measurement devices with real-time communication capabilities are needed to guarantee meaningful monitoring of the electric grid. The accuracy of the estimated results provided by the State Estimation service can also affect the performance of the PC service. Similar to the case of the State Estimation service, a critical challenge for the application of PC at distribution level is the large size of the distribution grids. This calls for the design of distributed approaches where PC services act on small areas, possibly sharing some data with an upper level controller to ensure the coordination of the power control strategy in the whole grid.
+
+Due to the active nature of this service, a bi-directional communication is needed with the field. Data are collected from the grid to enable the State Estimation service, while the output of the PC service is sent to the converter-based components for the control of their power generation (or consumption). This also implies the need to have converters able to communicate remotely, both for sending measurement data (if available) and for receiving the actuation commands. While converters available today do not always guarantee this behaviour, this requirement can be considered as realistic in future scenarios where the availability of communication capabilities is essential to enable the Smart Grid.
+
+The PC service runs continuously and synchronously with the State Estimation service. In particular, a new iteration of the service is triggered by the collection of a new set of estimation results provided by the State Estimation service. Similar to the case of State Estimation service, there are not strict requirements on the reporting rate for the PC service. However, due to the highly intermittent behaviour of renewable energy sources and the possibility of sudden changes in the operating conditions of the distribution grid, it is recommended to run the PC service with at intervals shorter than one minute and possibly close to a few seconds.
+
+#### 5.21.3.2 Power system requirements of PC service
+
+Needed components in the field: inverters (controllable from remote), sensors and meters.
+
+Information about the electrical grid: topology of the network; grid parameters (line impedance, transformer data, etc.); nominal power of connected loads and generators; location of the meters.
+
+Type of measurements: the State Estimation service results are used in input to the PC service, so the same requirements as to the State Estimation service apply for this point.
+
+Measurement number: the State Estimation service results are used in input to the PC service, so the same requirements as to the State Estimation service apply for this point.
+
+Data volume: limited. In typical operations, one set of setpoints (i.e., active and reactive power, P and Q) is transmitted per minute with volt-reactive volt ampere curve; as an alternative, dynamic voltage control is recommended in case of disturbances. In such situations, the solution will transmit approximately 1 set of setpoints per second. P and Q are floating point numbers. The communication should be scalable, i.e., supporting changing grid topology with an increasing number of actors in the electrical grid.
+
+Measurement accuracy: the State Estimation service results are used in input to the PC service, so the same requirements as to the State Estimation service apply for this point.
+
+Measurement synchronization: the State Estimation service results are used in input to the PC service, so the same requirements as to the State Estimation service apply for this point.
+
+Additional data needed from the field: notification of switching events leading to a change in the network topology.
+
+Real-time communication capability: yes, required
+
+Bi-directional communication: yes required; needed to collect measurement and switch notifications in one direction (uplink) and to apply the control signals to the inverter in the other direction (downlink).
+
+Communication reliability and security: very high. PC service uses only a limited amount of command messages per actor, typically one actor for each switch, transformer, or major power generation unit. Since there will be only a limited set of such actors, the reliability of the data communication becomes particularly important, because losing just a single actor would impact the impact of the PC service. Likewise, it is essential that the data are transmitted in a secure way ensuring full data integrity because of automatic modification of grid edge settings; and in this context, higher security than for monitoring services expected.
+
+### 5.21.4 Post-conditions
+
+The management of the distribution grid power flows is optimised in terms of preventing possible contingencies and overloading of grid components. The efficient operation of the power grid, the power quality and the grid reliability are significantly improved.
+
+### 5.21.5 Existing feature partly or fully covering use case functionality
+
+None.
+
+### 5.21.6 Potential New Requirements needed to support the use case
+
+**Table 5.21.6-1**
+
+| Characteristic parameter (KPI) | | | | Influence quantity | | | | |
+|------------------------------------|---------------------------------------------------------------|---------------------------------------------|----------------------------------------------|------------------------------|---------------|------------|---------------------------|-------------------------------------------------------|
+| Communication service availability | Communication service reliability: mean time between failures | Max Allowed End-to-end latency (notes 1, 2) | Service bit rate: user-experienced data rate | Message size [byte] (note 2) | Survival time | UE speed | # of UEs | Service area |
+| 99.99 % | | < 30 ms | UL: < 100 Kbit/s | < 1000 | | Stationary | < 300 per km 2 | several km 2 up to 100,000 km 2 |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+NOTE 2: It applies to both UL and DL unless stated otherwise.
+
+## 5.22 Use Case of ensuring uninterrupted MTC service availability during emergencies
+
+### 5.22.1 Description
+
+During emergencies, public mobile land networks (PLMNs) may restrict network access, which may lead to a lack of service reliability for machine-type communication (MTC) in critical applications, such as power systems and in particular in microgrids. Microgrids are separate parts of a power grid, which can be controlled and operated individually in a so-called island mode or together as a whole. Existing features of a mobile network can be used to differentiate MTC of devices in a microgrid from other MTC or human-to-human (H2H) communication and ensure that these microgrid devices have service during emergencies, which enables use of mobile communication to coordinate the use of Distributed Energy Resources (DER) in microgrids, so that they can autarkically perform blackout recovery of an islanded microgrid. The idea is to ensure reliable communications for selected MTC devices during emergency conditions, without giving these devices additional priority over other network users during normal conditions or adversely affecting the service to prioritised users during emergencies. It was shown that this method allows the blackout recovery 100 times faster than with a conventional black start [58].
+
+Figure 5.22.1-1 shows an example of power grid restoration after a large-scale blackout using conventional and autarkic microgrid blackout recovery methods.
+
+
+
+The diagram illustrates two grid restoration scenarios. Part (a) shows a conventional hierarchical top-down restoration where a 'Grid Control Centre' and 'Grid Operator's Private Comms Network' are connected to a 'Main Grid' via 'Substation' nodes. The restoration process is shown by dashed lines expanding from the main grid to various loads. Part (b) shows an autarkic microgrid restoration where the grid is divided into multiple islanded microgrids. Each microgrid contains its own 'Base Station (eNodeB)' and is connected to a 'Mobile Core Network' and a 'Grid Control Centre'. The restoration is shown by dashed lines within each microgrid, indicating autonomous recovery.
+
+Figure 5.22.1-1: (a) Conventional grid restoration (hierarchical top-down blackout recovery) and (b) autarkic microgrid restoration (each islanded microgrid autonomously recovers from blackout).
+
+**Figure 5.22.1-1: (a) Conventional grid restoration (hierarchical top-down blackout recovery) and (b) autarkic microgrid restoration (each islanded microgrid autonomously recovers from blackout)**
+**Figure taken from [58]**
+
+Grid restoration after a large-scale blackout is conventionally done by first starting power stations with black start capability, then expanding the re-energised grid to include more large synchronous power stations and expanding the re-energised grid. In this way, medium voltage and low voltage levels are re-energised hierarchically and top-down, i.e., from the transmission level.
+
+The autarkic microgrid blackout recovery method presented in [53] assumes that the MV/LV grid is divided into a set of microgrids (Figure 5.22.1-1 (b)), which can be operated in island mode and are assumed to be autarkic, meaning that they have sufficient local energy generation and storage to be self-sufficient, and autonomous, meaning that they can manage themselves, although in normal operation they may be managed by distribution grid (DG) management systems external to the microgrid.
+
+In the context of a microgrid, having reliable communications during a blackout means that the microgrid can continue to manage itself during blackout, i.e., even when the distributed energy resources (DER) in the microgrid are connected to a de-energised grid, the distributed controllers at the DER sites can continue to communicate with each other.
+
+If communications from the microgrid to external management systems are working, the microgrid can perform autarkic blackout recovery under their direction. If, however, there is a loss of communication from the microgrid to external management systems, the microgrid can autonomously perform the autarkic blackout recovery. In any case, the autarkic blackout recovery relies on having communications which continue to function locally in the microgrid during blackout to allow the agents to act together to perform a black start using local DERs.
+
+In the autarkic microgrid blackout recovery method, the medium/low voltage grid is assumed to be divided into a set of autarkic microgrids, as shown in Figure 5.22.1-1 (b), which are islanded in case of blackout. The DERs remain connected to the grid and continue to use their Multi-Agent System (MAS) MTC devices to communicate with each other and with the distribution grid control centre during the blackout [53]. In this scenario, each microgrid has its own gNB equipped with an emergency power supply. In case the emergency power supply for a gNB is not available, only this specific microgrid covered by the affected gNB cannot perform autarkic blackout recovery. However, other microgrids which are not affected by the malfunctioning gNB can still perform blackout recovery.
+
+### 5.22.2 Pre-conditions
+
+The MAS's within one microgrid must be covered by a large-scale, wide-area communications network, and the communications network must continue to operate during blackouts.
+
+The network must support MTC and the MAS's can communicate within the microgrid using MTC.
+
+### 5.22.3 Service flows
+
+Blackout recovery using autarkic microgrids:
+
+- Identify which nodes in the MAS are working
+- Identify the current microgrid topology and DER capacity
+- Re-energise the microgrid and the loads.
+
+### 5.22.4 Post-conditions
+
+The microgrids have recovered from the blackout and operate normally again.
+
+### 5.22.5 Existing feature partly or fully covering use case functionality
+
+None.
+
+### 5.22.6 Potential New Requirements needed to support the use case
+
+Table 5.22.6-1
+
+| Characteristic parameter (KPI) | | | | Influence quantity | | | | |
+|------------------------------------|----------------------------------------------------------------|---------------------------------------------|-------------------------------------------------------|---------------------|---------------|------------|----------|--------------|
+| Communication service availability | Communication service reliability : mean time between failures | Max Allowed End-to-end latency (notes 1, 2) | Service bit rate: user-experienced data rate (note 2) | Message size [byte] | Survival time | UE speed | # of UEs | Service Area |
+| 99.9999 % | | 100 ms | < 1 Kbit/s per DER | | | Stationary | | |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+NOTE 2: It applies to both UL and DL unless stated otherwise.
+
+## 5.23 Edge cloud driven data acquisition (edgePMU)
+
+### 5.23.1 Description
+
+In the power grid, there are devices deployed to measure physical quantities from the grid, such quantities are e.g. electrical quantities such as amplitudes of voltage and current, phase, frequency or rate of change of frequency (ROCOF). One device that can provide such measurements is called a Phasor Measurement Unit (PMU). This particular device provides the above-mentioned values synchronized to a global time clock derived, for example from GPS. Such synchronized values can be used as an input to power distribution grid services, such as state estimation service [61]. Another possible service that relies on measurements of voltage, current and phase is a voltage control service [62].
+
+As PMUs are very expensive devices, they are placed only at key points of interest. However, it is possible to use cheaper field devices that collect sampled measurement data and then process them in the edge cloud hosted PMU software, virtualizing the processing functionality of a traditional PMU, thus enabling the concept of the edgePMU [63]. Due to the lower processing requirements of the field devices, their cost is reduced, and they can also be deployed in the distribution grid providing power system operators with a more precise knowledge of the state of their grids. The edgePMU concept separates the data acquisition from the data processing by exploiting the computational capabilities offered by distributed 5G edge clouds.
+
+The edgePMU, with its modular approach, tackles the growing need for low-cost measurement devices in distribution networks from a new perspective. It utilizes the scalability of cloud infrastructure and decreases the specialization needed in the data acquisition device, by providing flexible cloud solutions for different data use cases. Furthermore, the overall deployment is simplified from a communication point of view since there is no need for special communications cabling and a network infrastructure managed by distribution grid operators. This approach simplifies the adoption of PMUs in distribution networks by helping distribution grid operators gradually deploy their
+
+measurement architectures. In fact, the cloud-based approach offers great flexibility in the development of monitoring and automation functionalities, by gradually stacking services and processing modules. It also provides scalability opportunities, thanks to the cloud technology-based computational infrastructure. The increased computational power offered by 5G edge cloud compared to that of low-cost single board computers enables more computationally challenging algorithms to be deployed.
+
+Here are the key features of the edgePMU concept [63]:
+
+- High rate raw data transmission between the data acquisition unit and the edge cloud using 5G wireless connectivity
+- The ability to deploy services or other applications on edge cloud infrastructure instead of having to deploy them in a traditional PMU with its high processing power
+- A single field device can be used as a data acquisition unit for different services hosted in the edge cloud
+- Services can be deployed, modified and upgraded on demand without the need to physically visit the sites
+- The cloud-based software is not limited to only providing phasor measurements, but could also be used to calculate other metrics for power distribution grid services
+
+### 5.23.2 Pre-conditions
+
+Coverage by 5G communications networks of regions in which measurement devices and edge cloud are to be located is required. The voltage or current measurement sensors and their associated secure data acquisition units have to be deployed in the power grid.
+
+The secure data acquisition unit is connected wirelessly by the 5G network to the edge cloud hosted services.
+
+The service of phasor calculation is deployed in the edge cloud infrastructure.
+
+### 5.23.3 Service Flows
+
+
+
+```
+
+graph LR
+ subgraph SDU [Secure Data Acquisition Unit]
+ DAU[Data Acquisition Unit]
+ SC1[Secure Communication]
+ end
+ SS[Signal Source
+Voltage or current sensor] --> DAU
+ DAU --> SC1
+ SC1 -.-> SC2[Secure Communication]
+ subgraph ECHS [Edge Cloud-Hosted Service Software]
+ PC[Phasor calculation]
+ UI[Upstream Interface]
+ end
+ SC2 --> PC
+ PC --> UI
+
+```
+
+Service flow diagram for edgePMU use case. The diagram shows two main components: 'Secure Data Acquisition Unit' and 'Edge Cloud-Hosted Service Software'. On the left, a 'Signal Source' (Voltage or current sensor) feeds into the 'Secure Data Acquisition Unit'. Inside this unit, data flows from 'Data Acquisition Unit' to 'Secure Communication'. A wireless 5G connection (represented by two antennas) links the 'Secure Communication' unit to the 'Edge Cloud-Hosted Service Software'. Inside the edge cloud, the data flows from 'Secure Communication' to 'Phasor calculation' to 'Upstream Interface'.
+
+Source: ACS Institute, RWTH Aachen University
+
+**Figure 5.23.3-1: Service flow diagram for edgePMU use case**
+
+- The data acquisition unit is collecting data, such as voltage and current values, from the power grid.
+- This data is then sent via secure 5G communication to the relevant service hosted on the edge cloud.
+- After the data has been collected in the edge cloud, the service processes the data. A small buffer is needed for post-processing with the service hosted on the edge cloud.
+- In the case of the phasor calculation service, the estimated phasors can be forwarded to further applications or actors, either hosted by the edge cloud or external to it.
+
+### 5.23.4 Post-conditions
+
+The relevant power distribution grid service is successfully deployed in the edge cloud and running smoothly.
+
+The voltage or current measurements are collected by the data acquisition units and transmitted to the service hosted on the edge cloud.
+
+The service deployed in the edge cloud provides upstream services, such as state estimation or voltage control, with the input data they need.
+
+The resulting service output data, hosted on the edge cloud, is stored permanently or forwarded to upstream services.
+
+### 5.23.5 Existing features partly or fully covering the use case functionality
+
+Existing LTE wireless connectivity, if configured to provide the required latency, could support the transmission of field device measurement data to services hosted on clouds hosted on distribution system operator owned servers.
+
+Latency: Lower than $2/F_s$ , where $F_s$ is the output reporting rate of the edge cloud service. Example: 60 phasors per second at 60 Hz means $F_s = 60$ and $2/60=0.033$ means the overall latency budget is less than 33 ms. Typical networks aim for 50 or 60 phasors, depending on the geo location. Higher reporting rates are also allowed by the standard.
+
+**Table 5.23.5-1:**
+
+| Characteristic parameter | | | | Influence quantity | | | | | |
+|--------------------------------------------------|---------------------------------------------------------------|------------------------------------------|----------------------------------------------------------|---------------------|---------------------------------|---------------|------------|----------|--------------|
+| Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum (notes 1, 2) | Service bit rate: user experienced data rate (note 1, 2) | Message size [byte] | Transfer interval: target value | Survival time | UE speed | # of UEs | Service area |
+| | > 1 year | < 33 ms | < 20 Mbit/s | | ≤ 1 ms | | Stationary | | |
+
+NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
+
+NOTE 2: It applies to UL.
+
+### 5.23.6 Potential New Requirements needed to support the use case
+
+None.
+
+## 5.24 Use case of power distribution grid load and generation prediction service
+
+### 5.24.1 Description
+
+The Load Prediction (LP) and Generation Prediction (GP) service [52] aim at forecasting the future values of power consumption and injection, respectively, in order to give to the Distribution System Operator (DSO) the awareness on how the grid operating conditions are expected to evolve in the future. This service works by processing the historical data on the power consumption/injection of the customer, generator, or substation under analysis, and possibly taking into account other information that is likely to affect the power levels (e.g. like weather conditions, temperature, etc.). The forecast given by the LP and GP can refer to different time horizons and can have a different time resolution, according to the requirements of the DSOs. As an example, day ahead forecasts (for example with a time resolution of 15 minutes) can be generated in order to predict possible contingencies and, in case, to be prepared to take adequate countermeasures. Day ahead forecasts could be refined by shorter-term forecasts, e.g. a forecast referred to the next hour, which in general could be more reliable since it can be based on more recent information on the grid status. This could be, for example, a solution to apply preventive control schemes aimed at minimizing the risk of problems in the grid. On the other side, longer term forecasts (e.g. on a seasonal or yearly basis) are also possible and they can support DSOs in planning, and in supporting strategical decisions on managing and reinforcing the grid.
+
+### 5.24.2 Pre-conditions
+
+Power meters are available at the customer (or substation) site where the forecast is required. The State Estimation service (see clause 5.20 "Use case of power distribution grid state estimation" above) is deployed and active in the power distribution grid. Output of the State Estimation service can be used by the LP and GP service.
+
+### 5.24.3 Service Flows
+
+#### 5.24.3.1 Introduction
+
+LP and GP service is based on historical data as the input information. In the case of the LP service, the needed historical data include the power consumption (demand) measured in the past with a time resolution that is equal (or better) than the one required in output for the service. As a consequence, the application of the LP service automatically implies the need to have power meters available at the customer (or substation) site where the forecast is required. In the case of the GP service, similar requirements also apply. Moreover, since the generation can be largely affected by external factors, additional information can be also needed. E.g., in case of a GP service to forecast the power generation from photovoltaic (PV) plants, additional factors such as weather conditions (irradiance, temperature, cloudiness, etc.) can play a relevant role to determine the expected power generation and they need to be duly considered by the service. In summary, the data required as input to the LP/GP service are:
+
+- Active and reactive power consumption (or generation) measured at the customer (generator) or substation that is object of the analysis; data should possibly cover a quite long period of time (months or years) to lead to accurate results.
+- Weather forecast data (irradiance, temperature, cloudiness, etc.) as input to the GP service.
+
+Generally, the LP/GP service has loose power system requirements. It is worth noting that no data about the grid are needed for this service and that the measurement devices deployed to get the needed power data do not need real-time communication requirements.
+
+#### 5.24.3.2 Power system requirements of LP/GP service
+
+Needed components in the field: sensors and meters.
+
+Information about the electrical grid: no details on the electric grid are needed.
+
+Type of measurements: power measurements at the monitored load, generator, or substation (or both voltage and current in order to be able to compute the associated power).
+
+Measurement number: for each point where an accurate forecast is needed, a meter providing power measurements (or information on both voltage and current) is needed.
+
+Measurement accuracy: no strict requirements on the accuracy of the measurement chain.
+
+Measurement synchronization: no need for accurate synchronization, but meter data need to have a time tag.
+
+Additional data needed from the field: no additional data needed from the field.
+
+Real-time communication capability: not required.
+
+Bi-directional communication: not required, the communication flow is mono-directional from the meters to the control centre.
+
+### 5.24.4 Post-conditions
+
+The future values of power consumption and injection are forecasted. DSO is aware of how the grid operating conditions are expected to evolve in the future, e.g., to predict possible contingencies. Longer term forecasts can support DSO in planning, and in supporting strategical decisions on managing and reinforcing the grid.
+
+### 5.24.5 Existing features partly or fully covering the use case functionality
+
+Data transmission is based on the uplink direction only, when using historic values for load and power generated.
+
+Load and generation prediction service does not take data from the field, but only the data stored in the database. Of course, the data stored in the database arrived at some point from the field.
+
+Connection density. See State Estimation service (clause 5.20 "Use case of power distribution grid state estimation" above) for the number of substations where measurements that will be used for Load and Generation Prediction service
+
+can be collected. Additional measurements can arrive from generation plants and in this case the density of the connection end points will become higher comparing to State Estimation service.
+
+In addition, residential smart meters could be also used in for LP/GP service. In this case the number of connection end points would increase drastically.
+
+The connection density is the most critical requirements for LP/GP service. Accordingly, it requires enhanced coverage.
+
+Latency. There are no critical latency requirements, since data are taken a posteriori from the database.
+
+Sampling rate. See State Estimation service (clause 5.20 "Use case of power distribution grid state estimation" above) since the same data are likely to be used for LP/GP service. Note that for LP/GP service, sampling rate of 1 message per minute is enough.
+
+Message size. See State Estimation service (clause 5.20 "Use case of power distribution grid state estimation" above) since the same measurement device can be used also for LP/GP service measurements collection.
+
+Communications service reliability. Important but not critical. Prediction service works also if there are some missing values, since there are procedures to replace them.
+
+Communication service availability. Not critical. 99.9% (3 nines meaning communications downtime per month of 43 minutes) or even more is acceptable.
+
+Security. Important but not critical. If a few data are corrupted, it is not a big problem. Of course, if all the data of a certain period are wrong then also the prediction would be wrong. But in such scenario, there will be already other services that are more critical suffering from the bad data.
+
+Table 5.24.5-1 shows communications requirements for the LP/GP service.
+
+**Table 5.24.5-1: Communications requirements of Load and Generation Prediction service**
+
+| Characteristic parameter | | | | Influence quantity | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------------------------|-------------------------------------------------------|------------------------------|------------------------------------------|------------------------|------------|--------------------------|-------------------------------------------------------|
+| Communication service availability: target value | Communication service reliability: mean time between failures | End-to-end latency: maximum (notes 1, 2) | Service bit rate: user experienced data rate (note 2) | Message size [byte] (note 2) | Transfer interval: target value (note 2) | Survival time (note 2) | UE speed | # of UEs | Service area |
+| 99.9% | | Not critical | 100 bit/s | < 1000 | 1 minute | | Stationary | < 30 per km 2 | several km 2 up to 100,000 km 2 |
+| NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node) rather than two wireless links (UE to UE). | | | | | | | | | |
+| NOTE 2: It applies to UL. | | | | | | | | | |
+
+### 5.24.6 Potential New Requirements needed to support the use case
+
+None.
+
+# 6 Considerations
+
+## 6.1 Potential security considerations
+
+(void)
+
+In order to guarantee high level of secured communication for energy applications, as described in clause 5.10, it is important to support secured communication between the 5G core network and energy applications.
+
+A new potential security requirement i.e. [CPR 009] is identified in clause 7.1.
+
+## 6.2 Potential charging considerations
+
+None.
+
+# --- 7 Consolidated potential requirements and KPIs
+
+## 7.1 Consolidated potential requirements
+
+**Table 7.1-1 - Consolidated Potential Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|
+| CPR-7.1-1 | The 5G system shall support an end-to-end latency of less than 5ms or 10ms, as requested by the UE initiating the communication. | PR[5.4]-001 | |
+| CPR-7.1-2 | The 5G system shall support communication channel symmetry in terms of latency (latency from UE1 to UE2, and latency from UE2 to UE1) between the two UEs, with the max asymmetry < 2ms. | PR[5.4]-002.option1 | |
+| CPR-7.1-3 | Based on MNO policy, the 5G network shall provide suitable means to allow a trusted third party to monitor LAN-VN performance parameters, to configure and receive information for conditions relevant to a specific UE, network and specific configuration aspects of the UE in the VN. | PR[5.7]-001 | |
+| CPR-7.1-4 | The 5G system shall provide a means by which an MNO informs 3rd parties of network events (failure of network infrastructure affecting UEs in a particular area, etc.). | PR[5.7]-002 | |
+| CPR-7.1-5 | Based on operator policy, the 5G system shall provide means by which an MNO informs 3rd parties of changes in UE subscription information. The 5G system shall also provide a means for 3rd parties to request this information at any time from the MNO. (note 1) | PR[5.7]-005 | |
+| CPR-7.1-6 | Based on operator policy, the 5G system shall provide means for the 3rd parties to request changes to UE subscription parameters for access to data networks, e.g. static IP address and APN. | PR[5.7]-005a | |
+| CPR-7.1-7 | The 5G system shall provide a means by which an MNO can inform 3rd parties of changes in the RAT type serving UE, cell ID, quality of signal information, change in frequency band assigned with a suitable frequency via OAM and/or 5G core network to aid the 3rd party user in taking proactive actions to achieve their own service availability. | PR[5.7]-006 | |
+| CPR-7.1-8 | The 5G system shall enable support of a mechanism to support authentication and secured communication between the 5G system Core Network and a 3rd party's application function, in order to provide secure end to end communication service. | PR[5.10]-001 | |
+| CPR-7.1-9 | The 5G system shall provide a mechanism for a 3rd party to report to an MNO service degradations, communications loss and sustained connection loss. These reports use a standard form. The specific values, thresholds and conditions upon which alarms occur could include e.g. the measured values for latency, data rate, availability, jitter, etc. for a UE, its location, and the time(s) in which the degradation occurred. (notes 2, 3) | PR[5.11]-001 | |
+| CPR-7.1-10 | The 5G System should support the IEC 61850-9-3 [29] profile and IEEE Std C37.238-2017 [24]. | PR[5.13]-001 | |
+
+| | | | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--|
+| CPR-7.1-11 | 5G system should support at least one of the two profiles for synchrophasor communications: IEC 61850-90-5:2012 [26], or IEEE Std C37.118.2-2011 [28]. | PR[5.13]-002 | |
+| CPR-7.1-12 | The 5G system should support the IEEE 802.1Q QoS profile as defined IEC 61850-90-5 [26]. | PR[5.13]-003 | |
+| CPR-7.1-13 | The 5G system shall support delivery of the same UE originated data to a group of recipient UEs distributed over a large geographical area in a resource-efficient manner in terms of bandwidth. | PR[5.13]-004 | |
+| CPR-7.1-14 | The 5G system shall allow an originating UE to request a communication service to send data to different groups of UEs at the same time. | PR[5.13]-005 | |
+| CPR-7.1-15 | The 5G system shall allow a UE to request different QoS for the communication in each of those groups. | PR[5.13]-006 | |
+| CPR-7.1-16 | The 5G system shall provide a mechanism for an MNO, based on MNO policy, to automatically report to 3rd party' service degradations, communications loss and sustained connection loss in a specific geographic area (e.g. a cell sector, a cell or a group of cells.) These reports use a standard form. The specific values, thresholds and conditions upon which alarms occur could include e.g. the measured values for latency, data rate, availability, jitter, etc. for a UE, its location, and the time(s) in which the degradation occurred. | PR[5.17]-002 | |
+| CPR-7.1-17 | Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the uninterruptable power supply status of the MNO's infrastructure, specifying which physical regions would be affected in terms of physical topology, as this information will facilitate energy system recovery operations | PR[5.18]-001 | |
+| CPR-7.1-18 | Subject to regulatory requirements, the 5G system shall support a mechanism by which a third party can communicate the energy system recovery status in terms of location and time table to the MNO, as this information will facilitate MNO operations to facilitate energy system recovery. (note 4) | PR[5.18]-002 | |
+| CPR-7.1-19 | The 5G system shall enable recipient UEs to indicate their interest in receiving data from a specific originating UE. | PR[5.16]-003 | |
+| NOTE 1: Examples of UE subscription information include IP, 5G LAN-VN membership address and APN/DNN. These changes can have strong impacts in the stability of the 3rd party service. | | | |
+| NOTE 2: What the MNO does with such reports is out of scope of 3GPP specifications. | | | |
+| NOTE 3: The above potential requirement expresses the need for reporting by a third party to the 5GS and leaves it to downstream groups (in this case SA5) to work out the implications. | | | |
+| NOTE 4: It is assumed that once aware of the proximity and duration of the energy outage, the MNO may manage the 5G nodes affected by the outage to make use of the power autonomy remaining in the 5G nodes, e.g. prioritizing the delivery of resources to support the energy system operations communications. Power consumption for energy system operations must be optimized so that the service recovery can be remotely orchestrated by the energy utility. | | | |
+
+## 7.2 Consolidated potential KPIs
+
+Table 7.2-1 KPI Table of Periodic Communication Services
+
+| Use case | Experienced data rate | availability | Transfer interval: target value | Message size | Service area | Max Allowed End-to-End latency | density |
+|----------------------------------------------------------------------|-------------------------------------------------------------------------------|--------------|---------------------------------|-------------------------------------|--------------|--------------------------------------------------------|--------------------------------------------------------------------------------------------------|
+| 5.1
Distributed Energy Storage - monitoring | UL: > 16 Mbit/s (urban),
640 Mbit/s (rural)
DL: > 100 kbit/s (note 1) | DL: >99.90% | UL: 10 ms | UL: 50 x 16 kbyte | - | DL:<10 ms
UL:<10 ms | >10 /km 2 (urban),
>100 /km 2 (rural)
(storage node density, note 2) |
+| 5.1
Distributed Energy - Storage Data collection | UL: > 128 kbit/s (urban),
10.4 Mbit/s (rural)
DL: > 100 kbit/s (note 1) | DL: >99.90% | UL: 1000 ms | UL: 50 x 26 kbyte
DL: >100 kbyte | - | DL:<10 ms
UL:<1000 ms | >10 /km 2 (urban),
>100 /km 2 (rural)
(storage node density, note 2) |
+| 5.2
advanced metering | UL:<2 Mbit/s
DL:<1 Mbit/s | >99.99% | - | - | - | General information data collection: <3000 ms (note 3) | <10000/km 2 (connection density, note 4) |
+| 5.3
Distributed Feeder Automation | 2 Mbit/s to 10 Mbit/s | 99.999% | Normal:- 1s;
Fault:2ms
- | - | - | <10 ms (see note 6)-
Latency jitter <50 µs (note 5) | 54/km 2 (see note 7)
78/km 2 (connection density, note 8) |
+| 5.5
Distribution Automation (DA), centralized architecture | 9.6-100 kbit/s | 99.999% | - | - | - | 100 ms – 2 s | 100/km 2 concentrated rural, 10/km 2 semi-urban |
+
+| | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------|----------------------|------------|------------------------|-----------|----------------------------------------------|-----------------------------|----------------------------------|
+| 5.8
Smart Distribution Transformer Terminal | >2 Mbit/s (note9) | | | | 100 m ~ 500 m, outdoor, indoor / deep indoor | 10 ms, 100 ms, 3 s (note10) | 500 /distribution area (note 11) |
+| 5.12
Distribution Intelligence – FLISR
High speed current differential protection (see NOTE 13 ) | 1,2Mbit/s~2,5 Mbit/s | > 99,999 % | $\leq 1$ ms~2ms | <245 byte | - several km 2 | 5 ms~15ms | $\leq 100/\text{km}^2$ |
+| 5.15
Distributed Energy Resources and Microgrids (note 9 ) | 5.4 Mbit/s | 99.9999 % | $\leq 1$ ms | 140 byte | - | 3 ms | - |
+| 5.22
ensuring uninterrupted MTC service availability during emergencies | < 1 kbit/s per DER | 99.9999 % | 100 ms (notes 10, 11 ) | - | - | - | - |
+
+| | |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NOTE 1: | This KPI is to require data rate in one Energy storage station which may provide via one or more 5G connections and via one or more 3GPP UE(s) at the same time. |
+| NOTE 2: | It is used to deduce data volume in an area which has multiple energy storage stations. The data volume can be deduced through follow formula: ( Current + other data) data rate per storage station * (Storage node density /km2) * (Active factor/km2) + video data rate per storage station * (Storage node density /km2). In general, the Active factor is 10% |
+| NOTE 3: | It is one way latency from 5G IoT device to backend system while the distance between them is no more than 40 km i.e. city range. The command implementation need 100 ms. |
+| NOTE 4: | It is the typical connection density in today city environment. With the evolution from meter centralization collection to sockets in home directly collection, the connection density is expected to increase 5-10 times. |
+| NOTE 5: | The latency jitter is required for the switch off between the active and standby communication links |
+| NOTE 6: | It is the one way delay from a distributed terminal to 5G network. |
+| NOTE 7: | When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre with the power load density is 20MW/km2. |
+| NOTE 8: | When the distributed terminals are deployed in power distribution cabinets, and considering the power load density is 20 MW/km2, there are about 78 terminals in one square kilometre. |
+| NOTE 9: | It is the smart metering application data rate between the Smart Distribution Transformer Terminal and energy end equipment. Once there are multiple smart grid applications, it is required more data rate. |
+| NOTE 10: | It depends on different applications supported by the Smart Distribution Transformer Terminal. The less the latency is, the more applications can be supported. |
+| NOTE 11: | The distribution area is circular with range between 100 m and 500 m (0.031 km2 to 0.785 km2). |
+| NOTE 12: | UE to UE communication is assumed. |
+| NOTE 13: | Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE). |
+| NOTE 14: | It applies to both UL and DL unless stated otherwise. |
+
+**Table 7.2-2 KPI Table of Aperiodic Communication Services**
+
+| Use case | Max allowed end-to-end latency | Experienced data rate | Communication service availability | Message size | Service area | Reliability | Storage node density # /km2 (note 2) |
+|-------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------|------------------------------------|--------------|-------------------------|-------------|--------------------------------------|
+| 5.1
Distributed Energy Storage
Energy storage station: video | DL:<10 ms
UL:<1000 ms (rural) | UL: >5 Gbit/s
DL: >100 kbit/s (see note 1) | - | - | - | DL: >99.90% | >[x]*100 |
+| 5.2
Advanced metering | Accuracy fee control: < 100 ms (note2); | DL:<1 Mbit/s | | | | >99,99% | |
+| 5.12
Distribution Intelligence – FLISR
Feeder automation (note 2) | 20 ms | - | > 99.999 % | < 100 byte | several km 2 | - | - |
+| 5.15
Distributed Energy Resources and Microgrids (note 2) | <3 ms | - | > 99.9999 % | 160 byte | - | - | - |
+
+NOTE 1: The required data rate in one Energy storage station which may provide via one or more 5G connections and one or more 3GPP UE(s) at the same time. It can be calculated with following formula: $12.5 \text{ Mbytes/s} \times 50(\text{containers}) \times 8 = 5 \text{ Gbit/s}$
+
+NOTE 2: The accuracy fee control latency here is for communication one way latency from backend system to 5G IoT device while the distance between them is no more than 40 km i.e. city range.
+
+NOTE 3: UE to UE communication is assumed.
+
+**Table 7.2-3 Clock Synchronization Service Performance Requirements**
+
+| Use case | User-specific clock synchronicity accuracy level [65] | Number of devices in one Communication group for clock synchronisation | Clock synchronicity requirement | Service area | 5GS synchronicity budget requirement |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------|---------------------------------|-------------------------|--------------------------------------|
+| 5.3
Distributed Feeder Automation | - | 54/km 2
(note 1)
78/km 2
(note 2) | - | several km 2 | <10 µs |
+| 5.12
Distribution Intelligence – FLISR
feeder automation aperiodic deterministic communication and High speed current differential protection periodic deterministic communication | - | ≤ 100/km 2 | - | several km 2 | ≤ 10 µs |
+| 5.19
Applications Using IEC 61850-9-2 Sampled Values Smart Grid: Synchronicity between sync master and PMUs
This range covers the extreme cases where the PTP clock in the end device uses 5G sync modem as direct time-source (1 µs)
The 5G sync modem acts as PTP GM or 5G sync modem provides PPS output to PTP GM at the top of the Ethernet based synchronization chain with up to 15 transparent clocks or 3 boundary clocks (250 ns). | 4 | Up to 100 UEs | <250 ns-1 µs [7]
(note 3) | < 20 km 2 | - |
+
+| | | | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|---------------|-------------------------|----------------------|--|
+| 5.19 Applications Using IEC 61850-9-2 Sampled Values Smart Grid: Power system protection in digital substation with merging units, line differential protection and synchronization | 4a | Up to 100 UEs | <10-20 µs [64] (note 3) | < 20 km 2 | |
+| 5.19 Applications Using IEC 61850-9-2 Sampled Values Smart Grid: Event reporting and Disturbance recording use-cases | 4b | Up to 100 UEs | <1 ms [64] (note 3) | < 20 km 2 | |
+| NOTE 1: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre with the power load density is 20MW/km 2 .
NOTE 2: When the distributed terminals are deployed in power distribution cabinets, and considering the power load density is 20MW/km 2 , there are about 78 terminals in one square kilometer.
NOTE 3: The clock synchronicity requirement refers to the clock synchronicity budget for the 5G system, as described in Clause 5.19.6.1. | | | | | |
+
+# 8 Conclusion and recommendations
+
+The study has analysed a number of use cases of Smart Grid which are enabled by 5G system. The use cases demonstrate the anticipated enhancements in the 5G system in order to use the 5G system
+
+- to support periodic communication and aperiodic communication required by different Smart Grid use cases;
+- to support clock synchronization required by Smart Grid use cases;
+- to support required information exchange between 5G system and a trusted 3rd party;
+- to support one or multiple profiles standardized in IEC or IEEE;
+- to support secured communication between the 5G system and a 3rd party's application function.
+
+Security considerations are captured in clause 6. The consolidated potential requirements and KPIs are in clause 7 of the TR. The contents of clause 6 and clause 7 is proposed to be considered as the basis of normative Release 18 requirements to support the Smart Grid service.
+
+# Annex A: Underground 3GPP Access
+
+### A.1 Description
+
+The topic of this annex is transport networks, normally out of scope of 3GPP standardization. For this reason, the material is provided as an informative annex.
+
+This use case considers how to provide 3GPP access underground. Equivalently, this use case considers providing 3GPP access anywhere in which 3GPP access cannot penetrate.) The use case considers what actions to take from the perspective of a facility – to provide smart energy services to components that are located underground.
+
+This is a relevant use case for smart energy because there are many facilities in the energy system which are either underground or inside structures that have thick walls with little or no ability for transmissions to penetrate.
+
+There are essentially three possible approaches – as shown in Figure A.1-1, below.
+
+
+
+Diagram illustrating three approaches for underground 3GPP access. A house is shown above ground, with a basement. A pink line (cable) runs from a radio unit on the roof, down through the house, and into the basement, connecting to a radio unit in the basement. Green lines (wireless extension) run from a radio unit on the roof, down through the house, and into the basement, connecting to a radio unit in the basement. A third approach, not explicitly shown but described in the text, involves power line deployment.
+
+**Figure A.1-1: Underground Access Approaches**
+
+The radio access on the roof can be **extended inside** by means of a cable as shown in pink (e.g. coaxial cable, with support hardware) to provide radio access to an indoor station (on the lower right, underground.)
+
+Another approach is to provide a **gateway and a wireless extension topology**, as shown in green. This could provide backhaul to a 3GPP access station in the lower right. Alternatively, all access within the building and underground could be accomplished by means of non-3GPP access. The (fixed mobile) 3GPP access remains on the roof, as a gateway providing network access.
+
+The third approach is to make use of the existing **power line deployment** in the building and underground as a means of providing backhaul to the underground access point. There are a number of Power Line Communications (PLC) standards that are already used to provide data access to the edge of the electrical network, especially to physical locations that cannot be accessed easily in other ways.
+
+Two prominent examples are Open PLC European Research Alliance (OPERA) [16] and G.9960 [17], which are used for support of Ethernet functionality over medium and low voltage power lines in a restricted range. In OPERA, information is modulated using OFDM with a set of 1536 sub-carriers. Effectively, this network provides an Ethernet over a power-line. G.9960 achieves PHY data rates up to 20 Mbit/s and highly robust communications with PHY bit rates up to 5 Mbit/s (using 4x repetition encoding.) 3GPP components can be integrated above this layer two standard that carries Ethernet frames.
+
+OPERA achieves PHY data rates of up to 200 Mbit/s with a bandwidth of 30 MHz (this is typically not achieved in practice. Implementation is done in either 5 MHz or 10 MHz channels with much lower maximum PHY bit rate up to
+
+40 Mbit/s and 80 Mbit/s respectively), for medium voltage (MV) cables. These throughput levels are not achievable at all in low voltage (LV) scenarios in which medium conditions are different to MV's. (This is an area of current development at the time this document was written, with researchers currently performing tests to evaluate the LV scenario.) The evolution of Ghn defined in ITU standard G.9960 might be more adequate for LV broadband power line (BPL) and for this use case (use of the LV cabling within a building) because it was specifically defined for domestic cables.
+
+Whereas adding a cable for range extension through a structure or wireless extension topologies entail extra planning, materials and complexity, power lines already exist in all (modern) structures.
+
+## A.2 Pre-conditions
+
+A facility will include components of the Smart Grid. The facility may either exist, or be planned and built from scratch.
+
+The builders provide an efficient and effective means to extend wireless communication for Smart Grid communications underground (or in a portion of the facility which cannot be penetrated by emissions for wireless communications.)
+
+Figure A.2-1 depicts an example deployment architecture.
+
+
+
+Diagram illustrating an example underground 3GPP access deployment using PLC. A building structure is shown with a User Equipment (UE) on the roof and a gNB (base station) underground. A dashed red line represents the PLC connection between the UE and the gNB, following the power lines within the building's walls and floor. The UE is connected to the gNB via this PLC link, which then connects to the external network.
+
+**Figure A.2-1: Example Underground 3GPP Access Deployment using PLC**
+
+A PLC connection between the UE and the underground gNB has been configured. The UE has a preconfigured tunnel to the MNO's network. The UE's user plane tunnel transports both the user plane and control plane traffic of the underground gNB. The UEs that camp on the underground gNB have full 5G service, limited only by the (limited) bandwidth available (and added latency) due to the PLC and UE to gNB links.
+
+## A.3 Service Flows
+
+The power lines in the facility are checked for their suitability for transmission of communications data. Power line communication termination is placed in the radio access station in the roof and the 3GPP access indoor station underground. Communications through the facility enable communication to be performed by the indoor station, then using the backhaul provided by the PLC, to communication via the access station on the roof.
+
+## A.4 Post-conditions
+
+The facility has underground 3GPP communication without need for additional wires (for a coverage repeater) or an indoor wireless extension topology. While the performance of the underground access will be limited to the capabilities of the PLC performance, this suffices for the smart energy services operating in the underground location.
+
+## A.5 Existing features partly or fully covering the use case functionality
+
+There are multiple ways that the configuration described in A.3 could be realized with existing 3GPP standards. For example, the indoor station could be a gNB whose backhaul is supported by means of PLC.
+
+Another possibility would be for the indoor station to provide non-3GPP wireless access underground. The PLC could provide backhaul to the rooftop UE. The rooftop UE would then provide network access through a PLMN.
+
+## **A.6 Potential New Requirements needed to support the use case**
+
+This use case is included for completeness but no new requirements have been identified.
+
+---
+
+## Annex B: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/comment | New version |
+| 2020-08 | SA1#91e | S1-203164 | | | | TR Skeleton agreed | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203165 | | | | FS 5GSEI overview | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203166 | | | | FS 5GSEI scope | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203337 | | | | Use Case of Distributed Power Storage | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203338 | | | | Use Case of Advanced Metering for Smart Grid | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203339 | | | | Use case of Smart Metering | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203340 | | | | Use Case of Distributed Automation | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203342 | | | | Use case of line current differential protection in power distribution grid | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203343 | | | | Smart Energy Differentiated QoS for Transported Encrypted Data | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203344 | | | | Service Lifetime for Utility Communication Services Deployments | 0.1.0 |
+| 2020-08 | SA1#91e | S1-203345 | | | | Remote DSO management of connectivity for Smart Energy | 0.1.0 |
+| 2020-11 | SA1#92e | S1-204093 | | | | Remove editor note about underground coverage | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204417 | | | | Update to Advanced Metering UC | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204418 | | | | Update to distributed automation UC | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204419 | | | | Update to Remote DSO management of connectivity for Smart Energy Use Case | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204420 | | | | Update: Smart Energy Differentiated QoS for Transported Encrypted Data | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204421 | | | | Use case of Smart Distribution Transformer Terminal | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204422 | | | | UC of Isolation for Smart Grid Applications | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204423 | | | | Gateway vs. End to End Security Use Case | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204424 | | | | QoS Monitoring and Reporting Mechanisms | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204202 | | | | Energy Substation Surveillance | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204341 | | | | Underground 3GPP Access | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204342 | | | | Use case on "Distribution Intelligence – self-healing" | 0.2.0 |
+| 2020-11 | SA1#92e | S1-204343 | | | | Use Case of supporting communication for the transmission of synchrophasors in wide-area Smart Grid | 0.2.0 |
+| 2021-03 | SA1#93e | S1-210438 | | | | Clarify the KPI table in section 5.2 | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210437 | | | | Update to Distributed Feeder Automation use case | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210156 | | | | Review of new requirements identified by 22.867 for 5.5 Smart Energy Differentiated QoS For Transported Encrypted Data | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210439 | | | | P-CR 22.267 clause 5.5 – update KPIs and requirements | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210441 | | | | Update to 5.8 Smart Distribution Transformer Terminal | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210442 | | | | Review of new requirements identified by 22.867 for 5.9 Use case of isolation demand for energy application | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210443 | | | | P-CR 22.267 clause 5.11 – QoS Reporting Requirement Update | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210444 | | | | Smart Grid clarifications to requirements | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210445 | | | | Update to the Use Case of supporting communication for the transmission of synchrophasors in wide-area Smart Grid | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210212 | | | | Smart Grid Update to sec 5.13 | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210446 | | | | Use case on "Distributed Energy Resources and Micro-Grids" | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210447 | | | | Use Case for Protection of interconnection between renewable and utility grid | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210448 | | | | Use Case of Utility Service Operator M2M service management platform in Smart Energy | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210449 | | | | 22.876 P-CR: Coordination for Energy Recovery Use Case | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210450 | | | | Use case on applications using IEC 61850-9-2 sampled values | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210451 | | | | Use Case of power distribution grid state estimation service | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210452 | | | | Use Case of power distribution grid load and generation prediction service | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210453 | | | | Use Case of power distribution grid power control service | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210454 | | | | Use Case of ensuring uninterrupted MTC service availability during emergencies | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210455 | | | | Edge cloud driven data acquisition (edgePMU) | 0.3.0 |
+| 2021-03 | SA#91e | SP-210205 | | | | Presentation for information, MCC clean-up | 1.0.0 |
+| 2021-05 | SA1#94e | S1-211101 | | | | remove the editor notes in section 5.1.5 and 5.1.6 | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211427 | | | | Add reference for KPI in section 5.2 | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211428 | | | | remove the editor notes in section 5.3 | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211429 | | | | update KPI table and question to section 5.5.6 | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211430 | | | | 22.867 P-CR: FS 5GSEI P-CR for 5.7 – revisiting requirements | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211431 | | | | Add a KPI table for section 5.8 | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211432 | | | | Update to the Use Case of 5_13 supporting communication for the transmission of synchrophasors in wide-area Smart Grid | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211433 | | | | Update to the Use Case of 5_16 Protection of DER and grid interconnection | 1.1.0 |
+
+| | | | | | | | |
+|---------|---------|-----------|------|---|---|--------------------------------------------------------------|--------|
+| 2021-05 | SA1#94e | S1-211434 | | | | Proposal for consolidated potential requirements in FS 5GSEI | 1.1.0 |
+| 2021-05 | SA1#94e | S1-211435 | | | | Consolidated KPI for FS_SEI | 1.1.0 |
+| 2021-06 | SA#92e | SP-210510 | | | | Raised to v.2.0.0 by MCC for approval | 2.0.0 |
+| 2021-06 | SA#92e | SP-210510 | | | | Raised to v.18.0.0 by MCC following approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210510 | | | | Corrected logo (5G->5GA) | 18.0.1 |
+| 2021-09 | SA#93e | SP-211097 | 0001 | 1 | B | Addressing EN resolution in 7.1 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0002 | 1 | D | Addressing EN resolution for timely term meaning | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0003 | 1 | D | Addressing EN resolution for standard use cases in 5.7.1 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0004 | 1 | D | Addressing EN resolution for RAN parameters in 5.7.1 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0005 | 1 | D | Addressing EN resolution in clause 5.7.5 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0006 | 1 | D | Addressing EN resolution in clause 5.7.2 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0007 | 3 | F | Addressing EN resolution in clause 5.7.6 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0008 | 1 | F | Update Consolidated PR and KPI tables in Section 7 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0009 | 1 | F | Update to conclusion and recommendation | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0010 | 1 | B | Security considerations | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0011 | 1 | D | Editorial Updates to TR22.867 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0012 | | F | Resolution of Editor's Notes from Clause 5.5.6 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0013 | | F | USIM Related Requirements for Manageability | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0014 | 1 | D | Removal of Editor's Notes from Clause 5.11 | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0015 | | D | Removal of Editor's Note in Annex A | 18.1.0 |
+| 2021-09 | SA#93e | SP-211097 | 0016 | 1 | B | Update Consolidated PR in Section 7 | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0017 | 2 | D | Get the missing figure A.1-1 back | 18.2.0 |
+| 2021-12 | SP-94 | SP-211496 | 0018 | 1 | D | Removal of all existing Editor's Notes in TR 22.867 | 18.2.0 |
+| 2021-12 | SP-94 | SP-211496 | 0019 | 1 | C | Reference corrections for clause 2 and clauses in 5.13 | 18.2.0 |
+| 2021-12 | SP-94 | SP-211496 | 0020 | 2 | D | Filling all CPRs into a normalized table | 18.2.0 |
+
+---
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22873/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22873/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c08222255fc313aa621eb86964b5a8b302367f0
--- /dev/null
+++ b/marked/Rel-18/22_series/22873/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d29bb9cb25f3e232fa3e588a1471970fc3086d500f80c4717863da395e8f4ab1
+size 9523
diff --git a/marked/Rel-18/22_series/22873/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22873/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92bca1355c31caf8acf1e97e3ed0a15cf739de30
--- /dev/null
+++ b/marked/Rel-18/22_series/22873/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:979f622293a630726656b98d7676846e954a1648d3e44945845a289d7c8d8780
+size 5678
diff --git a/marked/Rel-18/22_series/22873/9570393729046e571e3d8d0dc951956b_img.jpg b/marked/Rel-18/22_series/22873/9570393729046e571e3d8d0dc951956b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcf024c84628f906488eda862873bdcb2eaa2559
--- /dev/null
+++ b/marked/Rel-18/22_series/22873/9570393729046e571e3d8d0dc951956b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd5808f3edcc3ff6eefcc44b008f763a24769492f8852976a76772e72b9cb9f3
+size 37577
diff --git a/marked/Rel-18/22_series/22873/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-18/22_series/22873/df1d0e45191302de72176e4390224c16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f376a9d1422a7f5c427b831c0a2dbb67eb71019
--- /dev/null
+++ b/marked/Rel-18/22_series/22873/df1d0e45191302de72176e4390224c16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b7e6bb5a78f816785d6254046d75ade88fa8b4d2bb49c1c578d73b53cf54e0f
+size 29180
diff --git a/marked/Rel-18/22_series/22873/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/22_series/22873/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eba12594e2529788775a8878bfd8735f5f37f30c
--- /dev/null
+++ b/marked/Rel-18/22_series/22873/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5821f7faac6ef3739281eb63e4108ea40055b035d9a2dc45ab767f8cde9bcb57
+size 79293
diff --git a/marked/Rel-18/22_series/22873/raw.md b/marked/Rel-18/22_series/22873/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6791f557be7ad5e383743313d04e46116c5734bb
--- /dev/null
+++ b/marked/Rel-18/22_series/22873/raw.md
@@ -0,0 +1,587 @@
+
+
+# 3GPP TR 22.873 V18.0.0 (2021-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on evolution of IMS multimedia telephony service (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|---------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Symbols..... | 6 |
+| 3.3 Abbreviations ..... | 7 |
+| 4 Overview..... | 7 |
+| 5 Use cases..... | 7 |
+| 5.1 Conference call with AR holography..... | 7 |
+| 5.1.1 Description ..... | 7 |
+| 5.1.2 Pre-conditions..... | 7 |
+| 5.1.3 Service Flows ..... | 7 |
+| 5.1.4 Post-conditions ..... | 8 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 8 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 8 |
+| 5.2 Real-time speech translation ..... | 8 |
+| 5.2.1 Description ..... | 8 |
+| 5.2.2 Pre-conditions..... | 8 |
+| 5.2.3 Service Flows ..... | 8 |
+| 5.2.4 Post-conditions ..... | 8 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 8 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 9 |
+| 5.3 AR call..... | 9 |
+| 5.3.1 Description ..... | 9 |
+| 5.3.2 Pre-conditions..... | 9 |
+| 5.3.3 Service Flows ..... | 9 |
+| 5.3.4 Post-conditions ..... | 9 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 10 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 10 |
+| 5.4 Real-time screen sharing ..... | 10 |
+| 5.4.1 Description ..... | 10 |
+| 5.4.2 Pre-conditions..... | 10 |
+| 5.4.3 Service Flows ..... | 10 |
+| 5.4.4 Post-conditions ..... | 10 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 10 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 11 |
+| 5.5 Multimedia CLIP (Calling Line Identification Presentation) and COLP (Connected Line Identification Presentation)..... | 11 |
+| 5.5.2 Pre-conditions..... | 12 |
+| 5.5.3 Service Flows ..... | 12 |
+| 5.5.4 Post-conditions ..... | 12 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 12 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 13 |
+| 5.6 3 rd party specific user identities..... | 14 |
+| 5.6.1 Description ..... | 14 |
+| 5.6.2 Pre-conditions..... | 14 |
+| 5.6.3 Service Flows ..... | 14 |
+| 5.6.4 Post-conditions ..... | 15 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 15 |
+| 5.6.6 Potential New Requirements needed to support the use case..... | 15 |
+| 5.7 Real-time visual interactive menu..... | 15 |
+| 5.7.1 Description ..... | 15 |
+| 5.7.2 Pre-conditions..... | 16 |
+
+| | | |
+|-----------------|-----------------------------------------------------------------------------|-----------|
+| 5.7.3 | Service Flows ..... | 16 |
+| 5.7.4 | Post-conditions ..... | 16 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 16 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 17 |
+| 6 | Consolidated potential requirements..... | 17 |
+| 6.1 | Media handling capability ..... | 17 |
+| 6.2 | Authorization and authentication ..... | 17 |
+| Annex A: | Change history ..... | 18 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document studies new scenarios (e.g. AR/VR communication) for IMS Multimedia Telephony service, identifies potential service requirements, and identifies additional potential requirements on 5G system.
+
+This document also does a gap analysis to existing requirements in 3GPP to identify potential requirements for introduction into 3GPP.
+
+NOTE: Use cases in this document have references to those already specified in 3GPP TR26.918 [2] and TR26.928[3]. This allows an easier breakdown of these use cases to existing features and potential new requirements as well as relevant performance figures. New use cases in this TR are highlighted if they are not covered in 3GPP SA4 work.
+
+# 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 26.918: "Virtual Reality (VR) media services over 3GPP ".
+- [3] 3GPP TR 26.928: "Extended Reality (XR) in 5G ".
+- [4] 3GPP TR 22.823: " Study on Enhancements to IMS for new real time communication Services ".
+- [5] 3GPP TS 22.173: " IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services ".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| | |
+|----------|---------------|
+| | |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|----|------------------------|
+| AR | Augmented Reality |
+| AI | Artificial Intelligent |
+| VR | Virtual Reality |
+| XR | Extended reality |
+
+# --- 4 Overview
+
+With the evolution and capability enhancement of telecommunication system, telephony service has evolved from CS voice call to IMS multimedia telephony service. Nowadays 3GPP has introduced new network capabilities and new types of devices (e.g. AR/VR devices, robot, etc.), which can bring promising improvements to IMS multimedia telephony service.
+
+XR (an umbrella term for different types of realities, such as AR/VR) technologies have proven themselves to be valuable additions to the fields of digital entertainment, information and workspace.
+
+While more and more individual consumers enjoy MMTEL services across the globe, MMTEL services become popular also among business customers. There are several primary business functions that organizations use MMTEL services for, including internal communication, talking with prospects (sales call), contacting current customers and clients, customer support, and contact centre (or call centre) activities. While business customers consider the MMTEL services offer attractive features to their business, they also experience some practical issues that may benefit from support from the 5G system.
+
+# --- 5 Use cases
+
+## 5.1 Conference call with AR holography
+
+### 5.1.1 Description
+
+International companies have offices all over the world. The staffs of the company may have conference calls very often. If AR holography can be applied in the conference call, and AR holography data can be transmitted in the conference call session, all the staffs can feel the expression and action of the other parties, or even communicate with each other through body gestures. It just feels like having face-to-face meeting at the same location. It can really improve the immersive experience of the conference.
+
+### 5.1.2 Pre-conditions
+
+User A, user B and user C are the staffs of the same company but in different location. They always have to discuss their product schemes through conference call. Each of their own office has AR holography camera and glasses.
+
+### 5.1.3 Service Flows
+
+1. User A, user B and user C plan to have a conference call to discuss the latest product scheme.
+2. Each of them goes to their own office in which there is an AR holography camera.
+3. When meeting begins, they all initiate the AR holography camera. The AR cameras scan their whole bodies, then have the data processed in a dedicated device to build up the models of themselves.
+4. All the AR holography data and audio/video will be uploaded to the IMS Application Server. The Application Server makes media processing, including synchronizing AR holography data and audio/video, AR rendering, etc.
+
+5. After media processing, the IMS Application Server will generate new media streams (i.e. video, audio) and transmit them to each end user's AR glasses in the conference call.
+6. When AR glasses receive the generated media streams, they decode the media streams and present the product. Users can see the AR holography images of the other parties and hear their sound from the smartphone. The images can be updated in real time when conference call is processing.
+
+### 5.1.4 Post-conditions
+
+People in the IMS conference call can see the action and expression of the other parties. They can present the product with their body gestures. They can communicate and interact with each other (e.g., shaking hands, etc.). It just feels like having face-to-face meeting at that moment.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+Part of requirements for AR is covered in TR22.823 [4] already.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+The MMTEL service shall support synchronization between media/data streams belonging to the same MMTEL session.
+
+## 5.2 Real-time speech translation
+
+### 5.2.1 Description
+
+People may need to communicate with others speaking different languages. With AI technology(e.g. Skype translator), it is possible to provide instantaneous voice translation for the calling parties in a call and further perform speech-to-text or speech-to-speech for the translated voice.
+
+### 5.2.2 Pre-conditions
+
+User A and user B speak different languages.
+
+### 5.2.3 Service Flows
+
+1. User A makes an audio or video call to user B.
+2. User B chooses the translation service and text presentation. User A's voice is recognized and translated to user B's chosen language. Then the translation will be presented as texts or subtitles on user A's smartphone screen during the call.
+3. User A chooses the translation service and audio presentation. User B's voice is recognized and translated to user A's chosen language. Then the translation will be presented as audio replacing user B's original audio during the call.
+4. User A and user B are able to communicate in their native languages.
+
+### 5.2.4 Post-conditions
+
+User A can hear the translated audio and user B can see the translated texts on his screens synchronized with the voice and video.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+Currently in order to support real time voice translation in a MMTEL call, the MMTEL session shall end when the user trigger the translation service and another MMTEL session to the user shall be set up for transmitting translated audio.
+
+The MMTEL service can't incorporate the translation service within the end-to-end call, just like transcoding.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+**Editor's Note:** text to be provided.
+
+## 5.3 AR call
+
+### 5.3.1 Description
+
+This use case focuses on the multimedia call, equipped with AR to enrich the user experience and to be more helpful for users. AR call can be used in many areas like: person-to-person communication, emergency call, remote cooperation, and consumer-to-business call.
+
+Take remote cooperation supporting AR as an example, when local technicians have some difficulty in repairing consumers' cars, they can cooperate with the remote engineer of technical support department via multimedia telephony communication supporting AR. When making the AR call, UEs produce some data needed to perform rendering computing, all or part of which is done in the cloud/edge servers in this use case.
+
+The car technician makes a video call with the remote engineer to get more support. The technician can capture the car parts as video contents and mark possible points of failure in-call, in order to enable remote engineer to understand the problem. During the discussion, both parties can modify the video contents about the car in-call via their UEs, such as marking graphics and overlaying AR models. At the same time, both parties can receive the updated video contents in real time with the continuous modification. It looks like that the remote engineer is beside the technician, discusses and solves the problems together. AR call provides a solution which is less time-consuming and less costly.
+
+### 5.3.2 Pre-conditions
+
+User A is a local technician in a car repair shop and user B is a remote engineer arranged by the technical support department.
+
+### 5.3.3 Service Flows
+
+1. User A has some difficulty in repairing consumer's cars and hopes to get help from the technical support department by phone.
+2. User A makes a video call to user B, then he captures the car being repaired using his phone camera during the call.
+3. User A further turns on the AR call function and marks possible points of failure to the captured video contents.
+4. The AR data are produced within user A's UE and these data are sent to the AR cloud/edge server. The cloud server performs media processing (e.g. AR rendering, synchronizing multiple media streams) and produce multimedia. The multimedia is sent to user B's UE.
+5. User B sees the captured video contents related to the car being repaired with user A's marks via user B's call screen.
+6. In order to demonstrate the repairing procedures, user B deletes user A's marks and overlays AR models to the video contents captured by user A.
+7. User A can see the virtual demonstration, and follows the instructions step by step.
+8. User A and user B are sure that the problem is solved, and then hang up the video call.
+
+### 5.3.4 Post-conditions
+
+Both User A and User B can see and modify the marks and AR models on their respectively in-call screen. User A can cooperate with the remote engineer to repair the car well.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+Traditional video call is fully covered by existing IMS functionalities.
+
+Part of requirements for AR is covered in TR22.823 already.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+The IMS multimedia telephony service shall support AR media processing (e.g. MRFC and MRFP).
+
+## 5.4 Real-time screen sharing
+
+### 5.4.1 Description
+
+This use case is about the real-time screen sharing experience in a video call or a video conference. During a video call or a video conference, you can not only view real-time information on each other's screens but also directly perform “hands-on” operations on the shared screen. You can explain to other participants on the shared screen with doodles in real-time as if you were having a face-to-face white-board discussion. For example, you can remotely attend a customer meeting and present the solution to the customers via the shared mobile screen. In addition, you can also mark the key points on the slides displayed on the shared screen.
+
+With the support of IMS network that has been enhanced for the mobile screen sharing, the UE captures the screenshots and sends the data to the IMS network. The IMS network transfers the data to all other parties. After receiving the data, the receiving UEs can adapt the screen resolution and display the data clearly.
+
+### 5.4.2 Pre-conditions
+
+Mr. Anderson is having a multi-party video call with his son Mike and daughter Joan, asking for instructions on how to purchase tickets on the airline website.
+
+All UEs (smart phones, tablets) used in this call are able to capture screenshots, which may have subscriptions with different MNOs.
+
+### 5.4.3 Service Flows
+
+1. Mr. Anderson initiates a video call, inviting his son Mike and his daughter Joan to the call, and asking them for help to purchase tickets online.
+2. Mike asks if he could share his mobile screen to show his old father step by step. Mr. Anderson then “requests” Mike to share his mobile screen.
+3. Mike accepts the request and starts mobile screen sharing.
+4. Mike browses the airline website, selects an itinerary, and purchases a ticket. His smart phone, meanwhile, collects the screenshots and sends the data to the IMS network.
+5. The smart phones of Mr. Anderson and Joan receive the screen sharing data and display the data locally.
+
+### 5.4.4 Post-conditions
+
+Both Mr. Anderson and Joan can view the online ticket purchase process on Mike's screen by using the screen-sharing function.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+The related existing requirements can be found in TS 22.173[5] “Multimedia Telephony Service and supplementary services”:
+
+*IMS Multimedia Telephony service includes the following standardized media capabilities:*
+
+- *Full duplex speech;*
+- *Real time video (simplex, full duplex), synchronized with speech if present;*
+- *Real-Time Text communication;*
+- *File transfer;*
+- *Video clip sharing, picture sharing, audio clip sharing. Transferred files may be displayed/replayed on receiving terminal for specified file formats*
+- *Fax;*
+- *Data (CS).*
+
+*The support of each of these media capabilities is optional for a UE.*
+
+Real-time screen-sharing is similar to capture a sequence of screenshots and transfer them in real-time and on the receiving party display the screenshots in the right order in real-time.
+
+The MMTEL service supports a user participating in a MMTEL session to deliver to all other participants simultaneously a sequence of files in real-time.
+
+In addition, the features of “flexible data channel handling” cover the required functionality – “Data channels do not require use of any codec but allows for real-time interaction in parallel to the conversational media”. The details of data channel can be found in TS 26.114 “IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction”. Alternatively this functionality can also be supported in IMS with MSRP (Message Session Relay Protocol) using RFC 5547 (“A SDP Offer/Answer Mechanism to Enable File Transfer”).
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+**Editor's Note:** text to be provided.
+
+## 5.5 Multimedia CLIP (Calling Line Identification Presentation) and COLP (Connected Line Identification Presentation)
+
+### 5.5.1 Description
+
+The traditional calling card function provides the calling party identification information to the called party, and it also provides the calling party with the possibility to receive the line identity of the connected party. Such information can be enriched to include a subject, location, picture, and even video clips. There have been on-going efforts across the globe in enhancing the protection against unwanted robocalls, among which STIR/SHAKEN are most well-known solutions to verify the caller, minimizing unwanted robocalls and protecting consumers from fraudulent intentions from bad actors. IETF-defined STIR (Secure Telephone Identity Revisited) is considered one of the most promising technologies to combat unwanted robocalls, while SHAKEN (Signature-based Handling of Asserted information using tokens) framework provides a mechanism to implement STIR to authenticate calls. The STIR/SHAKEN works for authenticating and thus proving that a call has not been spoofed, but it does not determine caller intent. This means that bad actors may continue making unwanted calls by registering telephone numbers, which, as long as registered, are authentically theirs.
+
+Meanwhile in vertical applications (such as hospitality industry and tourism industry), multimedia Calling Line Identification Presentations (CLIP) and multimedia Connected Line Identification Presentation (COLP) can help companies to promote and advertise their business with promotional videos / pictures, office location information, etc. While MMTEL and the supplementary services offers attractive features, the biggest practical issue for lots of businesses is that calls sometimes are rejected as fraudulent robocalls. It would be beneficial to enable business customers to be involved in controlling/managing the business specific information of their users (e.g. the identity of its own employees), which will help to confirm the authenticity of the business specific identity information and to provide additional support in preventing fraudulent robocalls.
+
+### 5.5.2 Pre-conditions
+
+Hotel California has a service contract with an operator iCA, including IMS subscription for the MMTEL services and the supplementary services such as CLIP and COLP.
+
+### 5.5.3 Service Flows
+
+Example 1:
+
+1. Eagles called the hotel reservation hot line to book rooms for the band to stay in Baja California.
+2. When connected, they could see the promotional video of the hotel, as well as the identity information to confirm the authenticity of the called number.
+
+Example 2:
+
+1. As part of pre-check-in service, the hotel customer service called Eagles who would check in the next week to learn about the room requirements.
+2. When receiving the call, the guests could see the video introduction of the hotel with the available facilities and the scheduled entertainment events, as well as the identity information to confirm the authenticity of the calling number.
+
+### 5.5.4 Post-conditions
+
+When calling the hotel reservation hot line, customers can see the promotional video of the hotel.
+
+When receiving a call from the hotel customer service centre, guests can see the video introduction of the hotel.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+Note that the general requirements of Calling Line Identification Presentation (CLIP) and (Connected Line Identification Presentation) COLP are defined in TS 22.081 “Line identification Supplementary Services”, and for MMTEL in TS 22.173, clause 8.2.1 “Originating Identification Presentation (OIP)” and clause 8.2.3 “Terminating Identification Presentation (TIP)”.
+
+The existing service requirements relate to the use case functionality can be found in TS 22.183 “Customized Ringing Signal (CRS) Requirements” clause 4.1 “Basic functionality of CRS service”:
+
+*The service shall support the CRS content types of audio, video, image, graphic, text, location, and electronic business card.*
+
+*CRS can contain one or several content types, and at most one element of each type.*
+
+*The called party should be able to simultaneously experience multiple CRS contents, e.g. audio and video.*
+
+Rich Communication Services (RCS) defined in GSMA partially cover the required use case functionality, where the call composer functionality enables caller to enrich session establishment by sending e.g. reason, priority, location and other data to called party.
+
+In addition, the features of “flexible data channel handling” partially cover the required use case functionality. The details of data channel can be found in TS 26.114 “IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction”:
+
+
+
+*Data channels do not require use of any codec but allows for real-time interaction in parallel to the conversational media (see clause 6.2.10)...*
+
+*The data channel application is created prior to the DCMTSI call where it is intended to be used, by means left out of scope for this specification. The data channel application workflow is depicted by Figure 6.2.10.1-1 below.*
+
+**Figure 6.2.10.1-1 Data Channel Workflow**
+
+Figure 6.2.10.1-1 Data Channel Workflow diagram. The diagram is divided into 'Local' and 'Remote' sections by a vertical dashed line. On the Local side, there is a 'Data channel application repository' (cylinder icon), an 'Offline procedures' box (dashed border), and a 'Data channel server' box. On the Remote side, there are two User Equipment (UE) boxes labeled 'UE A' and 'UE B'. Arrows indicate the workflow: 1. Offline procedures to Data channel server; 2. Data channel server to Data channel application repository; 3. Data channel application repository to Data channel server; 4. Data channel server to UE A; 5. Data channel server to UE B; 6. UE A to UE B.
+
+**Figure 5.5.5-1: copy of Figure 6.2.10.1-1 of TS 26.114 on Data Channel Workflow**
+
+The existing features related Caller ID authentication are STIR/SHAKEN Standards. STIR (Secure Telephone Identity Revisited) provides the ability within SIP to authenticate Caller ID, and SHAKEN (Signature-based Handling of Asserted information using tokens) defines the end-to-end architecture to implement Caller ID authentication using STIR in the telephone network. Note that the related work for STIR/SHAKEN support in 3GPP systems is being referred to as caller ID attestation in the downstream WGs (i.e., CT work item on enhancements to call spoofing functionality eSPECTRE).
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+The following requirements apply to the originating side.
+
+[5.5.6-1] Subject to regulatory requirements and operator policy, the 3GPP network shall provide a means for third parties (e.g. enterprises) to be authorized to attest to the use of calling identity information by its authorized representatives.
+
+[5.5.6-2] Subject to regulatory requirements and operator policy, the 3GPP network shall provide a means for authorized third parties to attest that an authenticated representative is authorized to include or reference the pre-established calling identity information included in the call setup or retrieved by the called party.
+
+[5.5.6-3] Subject to regulatory requirements and operator policy, the 3GPP network shall provide a means to demonstrate the authenticity of the pre-established stored identity content that is referenced by the call setup and retrieved by the called party.
+
+The following requirements apply to the terminating side.
+
+[5.5.6-4] Subject to regulatory requirements and operator policy, the 3GPP network shall provide a means for third parties (e.g. enterprises) to be able to securely verify the caller's authorization to use the caller identity information either in addition to any verification by the terminating PLMN or instead of verification performed by the terminating PLMN (PLMN skips the verification).
+
+[5.5.6-5] Subject to regulatory requirements and operator policy, the 3GPP network shall provide a means to securely verify the authenticity of any stored identity content referenced by the call setup to be presented to the called party.
+
+## 5.6 3rd party specific user identities
+
+### 5.6.1 Description
+
+The majority of businesses use MMTEL services not just for making voice calls, but also for other services, such as online meetings, AR/VR calls. There are several primary business functions that organizations use MMTEL services for, including internal communication, talking with prospects (sales call), contacting current customers and clients, customer support, and contact centre (or call centre) activities. While business customers consider the MMTEL services offer attractive features to their business, they also point out some practical issues:
+
+#1 internal communication – MMTEL for internal communication can include voice calling, hosting online meetings, messaging co-workers, and team collaboration features like screen sharing. It could be challenging to manage the individual subscriptions for employees, especially considering employees may leave or join the companies or (for international companies) relocation to different countries.
+
+#2 communication with current or potential customers – while MMTEL offers attractive pre-call, in-call and post-call features, the biggest issue for lots of businesses is that calls sometimes are rejected as fraudulent robocalls.
+
+To target these pain points, this use case illustrates how businesses can be involved in the management and authentication of the user identities for its own employees when accessing MMTEL services.
+
+### 5.6.2 Pre-conditions
+
+Swift Delivery, a parcel delivery company, has a service contract with an operator iCA, including IMS subscription for the MMTEL services.
+
+### 5.6.3 Service Flows
+
+1. Rob Smith joined Swift Delivery recently, the company enabled him to use MMTEL services for business by updating the IMS business subscription with iCA with a user identity created for him
+2. When Rob calls the customer, the customer can easily identify that it is a legitimate call from the Swift Delivery and not a fraudulent robocall.
+
+The figure below illustrates an example where the operator authenticated caller identity can be displayed to the called party.
+
+
+
+The image shows two side-by-side smartphone screens representing a call interface. Both screens show the phone number '027 527 4136' at the top. The left screen shows a standard call interface with 'Remind Me', 'Message', 'Decline' (red button), and 'Accept' (green button) options. A large red arrow points from the left screen to the right screen. The right screen shows the same phone number but adds the caller's identity: 'Swift Delivery', 'Rob Smith', and 'Employee ID: 10001' in the center. The bottom interface with 'Remind Me', 'Message', 'Decline', and 'Accept' remains the same.
+
+Figure 5.6.3-1: Two smartphone screens showing a call from 027 527 4136. The left screen shows the number only. The right screen shows 'Swift Delivery Rob Smith Employee ID: 10001'. A red arrow points from the left screen to the right screen, indicating the display of authenticated caller identity.
+
+Figure 5.6.3-1 an example of CLIP for authenticated business callers
+
+### 5.6.4 Post-conditions
+
+With the company specific user identity, Rob can use the MMTEL services for internal communication with co-workers and external communications with customers.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+The related existing features partially covering the required use case functionality can be found in TS 22.173 “IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services” clause 4.6 “Multi-device and Multi-Identity”:
+
+*The owner (e.g. individual subscriber, operator/company) of the added identity needs to give its permission for others to use the identity.*
+
+*The owner (e.g. individual subscriber, operator/company) of the identity shall be able to revoke the permission for others to use the identity.*
+
+With regards to Caller ID authentication, there have been on-going efforts across the globe in enhancing the protection against unwanted robocalls, among which STIR/SHAKEN are most well-known solutions to verify the caller, minimizing unwanted robocalls and protecting consumers from fraudulent intentions from bad actors. IETF-defined STIR (Secure Telephone Identity Revisited) is considered one of the most promising technologies to combat unwanted robocalls, while SHAKEN (Signature-based Handling of Asserted information using tokens) framework provides a mechanism to implement STIR to authenticate calls. The STIR/SHAKEN works for authenticating and thus proving that a call has not been spoofed, but it does not determine caller intent. This means that bad actors may continue making unwanted calls by registering telephone numbers, which, as long as registered, are authentically theirs.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+[5.6.6-1] Subject to regulatory requirements and operator policy, the 3GPP network shall provide suitable and secure means to allow an authorized and trusted third-party (e.g. business customers) to update the MMTEL subscription and create a specific identity to an authorized user.
+
+NOTE: The third party is authorized to change user identities for those subscriptions authorized by the operator.
+
+[5.6.6-2] Subject to regulatory requirements and operator policy, the 3GPP network shall provide suitable and secure means to allow an authorized and trusted third-party (e.g. business customers) to authorize the use of identity information the third party is authorized to use by the third-party's users when that user is originating MMTEL services.
+
+[5.6.6-3] Subject to regulatory requirements and operator policy, the 3GPP network shall provide suitable and secure means to allow an authorized and trusted third-party (e.g. business customers) to attest that the third party's user is authorized to use the identity information when that user is originating MMTEL services.
+
+[5.6.6-4] Subject to regulatory requirements and operator policy, the 3GPP network shall provide suitable and secure means to allow an authorized and trusted third-party (e.g. business customers) to authenticate the identity information of its users at the terminating network.
+
+## 5.7 Real-time visual interactive menu
+
+### 5.7.1 Description
+
+This use case is about the call centre that provides customers with self-service information, such as hotels, banks, and restaurants. Such information is provided via the voice platform with the voice navigation prompts to guide a customer. The customer can then select the desired services according to the voice prompts. The traditional method of displaying multiple options in sequence on the voice interface may appear confusing or even misleading. Customers often need to listen to the voice navigation very carefully in order to follow the instructions correctly and obtain the desired services. Unclear voice navigation and/or misunderstanding of voice navigation are among the main reasons for customer service processing delay and suboptimal customer relations.
+
+To overcome this issue, the interactive menu can be made available to the customers corresponding to the voice navigation prompts. The customer can then interact with the call centre through the menu selection in a faster and error-free manner, improving the customer service satisfaction.
+
+### 5.7.2 Pre-conditions
+
+Isabelle is a customer of Universal Bank. Universal Bank provides online self-service via its customer service hot lines. Universal Bank has the subscription with the visual interactive menu services.
+
+### 5.7.3 Service Flows
+
+1. Isabelle calls the bank's customer service hot line.
+2. After the call is connected, the customer service centre answers with voice navigation prompt via the voice platform. At the same time, the customer service also sends the visual interactive menu of the service options via the data channel added via APIs provided by MMTEL service.
+3. Isabelle listens to the announcement about the available banking services while viewing the service options on her smart phone.
+4. She then selects the "debit card service" option on her phone following the instruction. The voice platform receives her selection and plays the next-level service options available for the debit card service. At the same time, Isabelle can also see the next-level service options on her phone.
+5. She then selects the "service bundle query" option on the phone. The related information on the subscribed service bundle is then displayed on her phone.
+
+### 5.7.4 Post-conditions
+
+During a MMTEL call with the bank's customer service hot line (out of 3GPP system), Isabelle carries out the self-service banking activities following the instruction provided by both the voice navigation prompts and the corresponding visual menu displayed on her smart phone.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+The features of "flexible data channel handling" partially cover the required use case functionality. The details of data channel can be found in TS 26.114 "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction":
+
+*Data channels do not require use of any codec but allows for real-time interaction in parallel to the conversational media (see clause 6.2.10). The User interface in Figure 4.2 interacts with a web page and a related script received through a downlink data channel to handle the data channel I/O and data formatting. All conversational media components are transported over RTP with each respective payload format mapped onto the RTP (RFC 3550 [9]) streams. The data channels are using SCTP (RFC 4960 [173]) over DTLS (IETF RFC 8261 [174]), used as specified for WebRTC data channels ([175]).*
+
+
+
+| Conversational Multimedia Application | | | | |
+|---------------------------------------|-------|------|------|--------------|
+| Speech | Video | Text | RTCP | Data channel |
+| Payload formats | | | | SCTP |
+| RTP | | | | DTLS |
+| UDP | | | | |
+| IP | | | | |
+
+**Figure 4.3: User plane protocol stack for a basic MTSI client**
+
+**Figure 5.7.5-1: copy of Figure 4.3 of TS 26.114 on User plane protocol stack for a basic MTSI client**
+
+In addition, the related existing service requirements about service exposure with 3rd party service providers can be found in TS 22.101 “Service principles” clause 29.2 “Exposed Services and capabilities”:
+
+*The 3GPP Core Network shall be able provide a standardized interface to enable exposure of the following services and capabilities to 3rd party service providers:*
+
+*Support of 3rd party requested session QoS and priority*
+
+*-The 3GPP Core Network shall enable a 3rd party service provider to request setting up data sessions with specified QoS (e.g. low latency or jitter) and priority handling to a UE that is served by the 3rd party service provider.*
+
+The IMS Multimedia Telephony service supports providing suitable APIs for a trusted third-party (e.g. enterprise call center) to control media components (e.g. establish, modify or terminate voice, video ,data channels ) during an ongoing MMTEL session.
+
+Note: third-party application may be out of scope.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+Void.
+
+# --- 6 Consolidated potential requirements
+
+## 6.1 Media handling capability
+
+The IMS multimedia telephony service shall support AR media processing.
+
+## 6.2 Authorization and authentication
+
+Requirements in this section are subject to regulatory requirements and operator policy.
+
+[6.2-1] The 5G system shall provide means to allow a trusted third-party to update the MMTEL subscription and allocate a third-party specific identity to an authorized user.
+
+NOTE 1: The third party is authorized to change user identities for those subscriptions authorized by the operator.
+
+The following requirements apply to the originating side.
+
+[6.2-2] The 5G network shall provide a means for third parties (e.g. enterprises) to be authorized to verify the use of calling identity information by its authorized users.
+
+[6.2-3] The 5G network shall provide a means for authorized third parties to verify that an authenticated user is authorized to include or reference the pre-established calling identity information included in the call setup or retrieved by the called party.
+
+[6.2-4] The 5G network shall provide a means to verify the authenticity of the pre-established stored identity information that is referenced by the call setup and retrieved by the called party.
+
+The following requirements apply to the terminating side.
+
+[6.2-5] The 5G network shall provide a means for third parties (e.g. enterprises) to be able to verify the caller's authorization to use the identity information either in addition to or instead of verification performed by the terminating PLMN.
+
+[6.2-6] The 5G network shall provide a means to verify the authenticity of any stored identity information referenced by the call setup to be presented to the called party.
+
+# Annex A: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|----|-----|-----|----------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2019-11 | SA1#88 | S1-193221 | | | | First revision | 0.2.0 |
+| 2020-09 | SA1#90e | S1-203380 | - | - | - | Including agreed docs: S1-203277, S1-203308 | 0.3.0 |
+| 2021-01 | SA1#93e | S1-210011 | - | - | - | Identical to v.0.4.0 which should have been provided in S1-204350 but problem with upload. | 0.4.1 |
+| 2021-03 | SA1#93e | S1-210300 | | | | Including agreed docs: S1-210106, S1-210407, S1-210408, S1-210370, S1-210371, S1-210372, S1-210373 | 0.5.0 |
+| 2021-05 | SA1#94e | S1-211300 | - | - | - | Output of SA1#94e | 0.6.0 |
+| 2021-06 | SA#92e | SP-210505 | - | - | - | Raised by MCC to v.1.0.0 for one-step approval | 1.0.0 |
+| 2021-06 | SA#92e | SP-210505 | - | - | - | Raised by MCC to v.18.0.0 following one-step approval | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22874/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-18/22_series/22874/0931f3e098bd4539041de11c50cec2d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0516284698ee5e46281b94e58ab05998016fd84b
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/0931f3e098bd4539041de11c50cec2d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b69dbb40c88dcf2424d30e16e3a863407e58144a2ceaf8c06970d053d42f5b4
+size 23812
diff --git a/marked/Rel-18/22_series/22874/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-18/22_series/22874/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f07c9ac31cf42ed23df6cc3299ba5ed3d0e2ab3c
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ec7b9fad2090ed85d8b3fcf3eec775210b48b25ea5121d342bd2858e3c5cb03
+size 33009
diff --git a/marked/Rel-18/22_series/22874/0e252770f8f0573617e0112b36a93d2f_img.jpg b/marked/Rel-18/22_series/22874/0e252770f8f0573617e0112b36a93d2f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..324e3ca30b342a0c00189d78a77c2768b4672c8e
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/0e252770f8f0573617e0112b36a93d2f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7f7cdb8e1062b1a214cc933e8117301de8079664f8b1f460188090f0e193794
+size 19238
diff --git a/marked/Rel-18/22_series/22874/0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg b/marked/Rel-18/22_series/22874/0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4599f66fdf894b235f20695b7008cf91d630e345
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1fef1616ac63d9f47924dbb0d986b207ff4f7da66b9648ab40d2823f16d37c7
+size 24447
diff --git a/marked/Rel-18/22_series/22874/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-18/22_series/22874/11f18bf0233d812ad2604f88f3385d60_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..491e1982a428140826b798f3f89e646b27505e32
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/11f18bf0233d812ad2604f88f3385d60_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:546c21bdd82284d0ef421c1017615296624c785af803057204a0fbfd19f60a58
+size 9067
diff --git a/marked/Rel-18/22_series/22874/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-18/22_series/22874/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fe21b401d39c472161a982ad4ebcc87d7df32fa
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84033f1744ee934e64ac039e84bb099c3c2810da74e0159b67a4e6180281f763
+size 34973
diff --git a/marked/Rel-18/22_series/22874/144e1d61e8738b22dcf4a683f869ac6f_img.jpg b/marked/Rel-18/22_series/22874/144e1d61e8738b22dcf4a683f869ac6f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ba7c31efabb691a80a0f32a06d05e498014717a
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/144e1d61e8738b22dcf4a683f869ac6f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78979d6b7ad62243dadab484148c999c397129090a407ab22e21f5d27215d5b6
+size 25191
diff --git a/marked/Rel-18/22_series/22874/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/Rel-18/22_series/22874/18442e4e239480f0c3c95b547aa8fde2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d28ef8439a885750c1b482731c1fdf61ee38b6e7
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/18442e4e239480f0c3c95b547aa8fde2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f50deb3dd042b4aab5d740823cb8351f76650119fa642d0e3631f6166e746e5e
+size 33406
diff --git a/marked/Rel-18/22_series/22874/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-18/22_series/22874/18bb06865e2dada3656ea3d57f290f7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14fa0f5a8593224e88b56afd6392851bb6ea15ca
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/18bb06865e2dada3656ea3d57f290f7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a713bd9307cc78b1220a4287669b4cd55a0191b793a2e0ed02ae9a2802c57adf
+size 18254
diff --git a/marked/Rel-18/22_series/22874/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-18/22_series/22874/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b244e67e722d2f021786a00678f42581bf9bf16
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84e82473366b5480c191781b18cac4029d3e9b88931f6dd3bf189b9c55c35aa4
+size 14826
diff --git a/marked/Rel-18/22_series/22874/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-18/22_series/22874/201de44da5d99899a8cf58eac2fa7bc9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b2d5ab7ec4ed4239052ff89fd3e615a7ab5f51e
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/201de44da5d99899a8cf58eac2fa7bc9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e9b9120a2c6b2e6f46046d3696da5396e0fad364050578ec1d2aa9d4491aa67
+size 23411
diff --git a/marked/Rel-18/22_series/22874/2fbb410da68e626ba5e994d872031f14_img.jpg b/marked/Rel-18/22_series/22874/2fbb410da68e626ba5e994d872031f14_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9175a4e2127d3185a3233fc45374bbefefcd995b
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/2fbb410da68e626ba5e994d872031f14_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac6125b651bf2ba2c13d9d006775e97eb40586301965cda984d671fece070682
+size 10526
diff --git a/marked/Rel-18/22_series/22874/3252037b597c9317aced0feed4cb5af0_img.jpg b/marked/Rel-18/22_series/22874/3252037b597c9317aced0feed4cb5af0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36a07c538815b6bd164080dba5bde0cccc84d878
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/3252037b597c9317aced0feed4cb5af0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:186d5063b45d0f47fd2c33360d1dfb9e3a86e28f5d4704fd386d10c931a5899c
+size 38263
diff --git a/marked/Rel-18/22_series/22874/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-18/22_series/22874/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf5c4c5a4336ca22a11d56e6dffb8c821cacb186
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/33a8f3f01dfa8bce75d23017855a13c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a7435dcca32604c883b9cc224eeeb260b0bc5c320496a0eec0cd1105153e913
+size 35364
diff --git a/marked/Rel-18/22_series/22874/411fa16c3211377525ba37c57784fee0_img.jpg b/marked/Rel-18/22_series/22874/411fa16c3211377525ba37c57784fee0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e04e0343cdc46021e9d0ad8f67941ba894f00060
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/411fa16c3211377525ba37c57784fee0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b453ea9f49c44fd59f8b9a6343988329c7ff4d4df158700ce39baf173e445680
+size 73947
diff --git a/marked/Rel-18/22_series/22874/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-18/22_series/22874/49fe8fe978c0f7e73112d231feb377eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e159e548de3706ea832c06f9dea990aa08ed075b
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/49fe8fe978c0f7e73112d231feb377eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b4e2798e33c51d910a12692aeb11d18b1bcbd4696113ae90cf21f9029c74edf
+size 52070
diff --git a/marked/Rel-18/22_series/22874/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/marked/Rel-18/22_series/22874/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ace21f2db16abcb47dc08f3f7483866feed54be6
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da951d4a7cf1f1688e849b9309eb31ce1cfba5bca0f27da883a0b528e9efda3b
+size 21351
diff --git a/marked/Rel-18/22_series/22874/5bba23cc120ad806779f82df1c01bebf_img.jpg b/marked/Rel-18/22_series/22874/5bba23cc120ad806779f82df1c01bebf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93a08c8cdbbdc2109e336867dad5c37842474867
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/5bba23cc120ad806779f82df1c01bebf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0787b653c13307ceb1b078a80ebe0fc37f3b97a887007bb4dee4f28f4490b43a
+size 14965
diff --git a/marked/Rel-18/22_series/22874/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-18/22_series/22874/5e9af8986a5845504f251d3079da8078_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9ddcc52a10d6bca700db4d9c635fe2231c52169
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/5e9af8986a5845504f251d3079da8078_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7415ba939832e328cca844930b82be76ea2023534b52ad587df5952852a4a4f7
+size 32531
diff --git a/marked/Rel-18/22_series/22874/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22874/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c0fe74b83cb0f5c36bdaf5d8c8713b8313fbcee
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3c1123fd1cabd2005e126e0ce4573a9d75b9f1da3d8ec720111009d4f4f18b2
+size 9291
diff --git a/marked/Rel-18/22_series/22874/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22874/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3ef83f8cf705d6bcc12f07319f75a9e2ed52625
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6de0d2aeb69fd0e1f8805831160e3f05c5949391c5af8a33703f1c2e42db8b00
+size 5594
diff --git a/marked/Rel-18/22_series/22874/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-18/22_series/22874/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10d0886dd8d4d0f7b7138c28297fa0eedc371ddf
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e13134a6fa89cba7769ec28be1f2602cd4edff05b1b0a26e9f8a42ed9757e1f9
+size 35095
diff --git a/marked/Rel-18/22_series/22874/6b29ab7e77b37eb167c955b26206c169_img.jpg b/marked/Rel-18/22_series/22874/6b29ab7e77b37eb167c955b26206c169_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad589de8a0772728174e3cf7e4a82164aef5022c
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/6b29ab7e77b37eb167c955b26206c169_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:012dbfd2fcf6e23fe566b1fe72b35ba37328830f2c150c73f7bc563e836a2e4a
+size 29810
diff --git a/marked/Rel-18/22_series/22874/6dcf3c6357538aad08b1cee84fb05985_img.jpg b/marked/Rel-18/22_series/22874/6dcf3c6357538aad08b1cee84fb05985_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dcec21112fc8f7ce642087fc15e052012a078eb1
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/6dcf3c6357538aad08b1cee84fb05985_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cef558182608aac0be701cee3943456be5b94e4fab29033440753a391a99b785
+size 31809
diff --git a/marked/Rel-18/22_series/22874/79aaab5889060cf8264226764a109cdb_img.jpg b/marked/Rel-18/22_series/22874/79aaab5889060cf8264226764a109cdb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da6fc858342533a986f9a72a43ef2ecdce4281f8
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/79aaab5889060cf8264226764a109cdb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4932a8aae75c539298b2b90a47e309573673ea1ee1ef6764954277df548feca
+size 8260
diff --git a/marked/Rel-18/22_series/22874/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-18/22_series/22874/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19ba7b6da5e17b19e28a4f5f89c0362c7e40d04e
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b95cff42dbe9da7396246e8bb4d21b4931c61c4ca1054d889ddc8f87297dd0ad
+size 30514
diff --git a/marked/Rel-18/22_series/22874/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-18/22_series/22874/8d66c9c295023a1380f9986d3663bb1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5f84abff1b2d1599336d2ee3058629e7e2bbd12
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/8d66c9c295023a1380f9986d3663bb1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:324873c0c550c63a1e3f2ed99d5de8f5b2a530e4adf749882e1f24347df85f71
+size 240846
diff --git a/marked/Rel-18/22_series/22874/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-18/22_series/22874/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca0ade49bee31faefc90926a29b8269d38a2993c
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fd85d45e9ba7f1b6ed050d567e10c5baf43c72e988588d62f796abf4aca4b91
+size 57144
diff --git a/marked/Rel-18/22_series/22874/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/22_series/22874/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c0a16e74bb447a1bff669ec648bc8e79dcabf91
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e851c9a25339bc77852120ad44e5e7bda84eaae41c9a4d398350b3b7287488ed
+size 44089
diff --git a/marked/Rel-18/22_series/22874/910aca984b27c368361b38751ab5eea6_img.jpg b/marked/Rel-18/22_series/22874/910aca984b27c368361b38751ab5eea6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..157fdc83494145ee082d4a8289f6ffc66b197809
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/910aca984b27c368361b38751ab5eea6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:54144d12cafcf3dfbacb64a36739362a02e7107a64c56649c3fea603f9b22c4b
+size 27745
diff --git a/marked/Rel-18/22_series/22874/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg b/marked/Rel-18/22_series/22874/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bb4eb2e20d811064b0fc0c9267048bcea1dcbb18
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c51dc38a563f3e6c8f47cc48b24131ce4459cd6973ad51cdd15f3f49ed3bc09a
+size 26465
diff --git a/marked/Rel-18/22_series/22874/94b29382cae475b008a608597ea9b8af_img.jpg b/marked/Rel-18/22_series/22874/94b29382cae475b008a608597ea9b8af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d9a7fa87d64b23cb5b2e16302bd7352950ad7be
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/94b29382cae475b008a608597ea9b8af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57dd457e4d8a7b1b3683bf5f9ee431cbf4359c288f8356fca9e132095137c83b
+size 19995
diff --git a/marked/Rel-18/22_series/22874/aef7fa3e55b1477058e5b4f630f21d12_img.jpg b/marked/Rel-18/22_series/22874/aef7fa3e55b1477058e5b4f630f21d12_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e379e936eef6bba1aa01d06ad258d408a862982
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/aef7fa3e55b1477058e5b4f630f21d12_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b4b71afa0b60f01f027d99cbcfdd43d9d801a051fbab533ee519e2063d0dac5
+size 26002
diff --git a/marked/Rel-18/22_series/22874/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-18/22_series/22874/b44f89b176c971c7dd264c07bfef2c2a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ebbdd94c1dbdb15e09ebba246d1e6559ca1b63bb
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/b44f89b176c971c7dd264c07bfef2c2a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a8cf9d345a3a7d8f116259589b85a28e178574d379653467254f5b7c7943fdb
+size 83873
diff --git a/marked/Rel-18/22_series/22874/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-18/22_series/22874/bccc028d0e75bc30c41528056f581545_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a35d0dbaef221f6c07b7f35be13180c7aa4a00d6
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/bccc028d0e75bc30c41528056f581545_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7df054f5993c624c3b8660cda3bbfc9b0637501766a7c35115b500b08f73fc4a
+size 39595
diff --git a/marked/Rel-18/22_series/22874/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-18/22_series/22874/c0ca823603794512478906b302176bca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ec78a17c70b1c5ffbc598cf137380c5625e7180
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/c0ca823603794512478906b302176bca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96f435846f5249fcdb179e9b6b6ec21cc7b4ac2f81fa62a985a2f2669991bb5e
+size 15721
diff --git a/marked/Rel-18/22_series/22874/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg b/marked/Rel-18/22_series/22874/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e420c3db62d0dc5f925903a15de16c4363ddf0e
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ac8bb444fb1b29a1a0b356da75c4f79f79c6ba1bd4d618d4129a0c12068e575
+size 60271
diff --git a/marked/Rel-18/22_series/22874/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-18/22_series/22874/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f38689c349ca45bbcdd259f9290b75fe065cf65b
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:182e156e9d15a044d99cc8eaa50f7291822f9b5e3be66b67c1a3caaa49a1db9f
+size 40776
diff --git a/marked/Rel-18/22_series/22874/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg b/marked/Rel-18/22_series/22874/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75178c800bba6e8a24d33194147e7d338932f544
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f281e6682f3de31988db984bac24b495f4ecd3d6dd7404cca75b2c8f32f77190
+size 10881
diff --git a/marked/Rel-18/22_series/22874/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-18/22_series/22874/d9cfc30025244dcd75766061f27ee09f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7a56ee0001f202b7c012db4a4e6477975df0e72
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/d9cfc30025244dcd75766061f27ee09f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44520e5fc76240a6f7ab4331833af90bc55f9ff6647c29428912a940027ec48e
+size 33965
diff --git a/marked/Rel-18/22_series/22874/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-18/22_series/22874/db39acbd11df5eb7e79ab84562fb8f74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f2b3afdf76509aa64489448174d9f270b6c7564
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/db39acbd11df5eb7e79ab84562fb8f74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88f7855397b5df56ab2f0ff1bd7bf6eeab7af1161ef28338083bf2bafc463b69
+size 33412
diff --git a/marked/Rel-18/22_series/22874/dc8d4323c2d4a62089422b77927e9e00_img.jpg b/marked/Rel-18/22_series/22874/dc8d4323c2d4a62089422b77927e9e00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6578edd0f90cb7f4754a645a9ee8cd70d9534c21
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/dc8d4323c2d4a62089422b77927e9e00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69c52625e7da0a5c25877cc0c03e0c1bdc09cd0fa53c744e8c7e80bee3a8fdb6
+size 40620
diff --git a/marked/Rel-18/22_series/22874/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-18/22_series/22874/e4c6fa93821e3546ee9fcae897ae2771_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77189e8593042e3ced1655523d5aa7c721b7a493
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/e4c6fa93821e3546ee9fcae897ae2771_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24190e7b3b8dc90723b77de7a3346c24877c0235ea7b8befe170200adb8fd6b5
+size 18301
diff --git a/marked/Rel-18/22_series/22874/e5293502d8d5885d71defe1150aa12fc_img.jpg b/marked/Rel-18/22_series/22874/e5293502d8d5885d71defe1150aa12fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2cb48378989c9116aa8784bc8b90531d4282e1ca
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/e5293502d8d5885d71defe1150aa12fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc6f24bdbd27426e0dc99640136f710ec5faac9757626bada51a26cb74c059d3
+size 13230
diff --git a/marked/Rel-18/22_series/22874/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/marked/Rel-18/22_series/22874/e60c2d24a97a2855d98671d27ea43d0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcd565a9a2bbb8303bfe6637a9e34586d1f5778a
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/e60c2d24a97a2855d98671d27ea43d0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d58d89790ce691e39753b3b3f41ff4a7a1828adb3c43de809a8455ed78a9efd7
+size 17734
diff --git a/marked/Rel-18/22_series/22874/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-18/22_series/22874/e7010c66da16316c2935dfbbef5056b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11480b8642829dbcd610c0bdcac472c209489bc5
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/e7010c66da16316c2935dfbbef5056b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7188ded18b15c24a5ac3bbb4d145101feb543bf3bf5d41f971cb868e6f22746d
+size 33214
diff --git a/marked/Rel-18/22_series/22874/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Rel-18/22_series/22874/f142b022cfc716cd967297f027efe647_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..931f2f163918c281885a1cde27532ee1b4cd28a9
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/f142b022cfc716cd967297f027efe647_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93cce5cbd061e2357a8911f9bf97ead68bd8ac06752fc6fc9f573a46b1e4231b
+size 35132
diff --git a/marked/Rel-18/22_series/22874/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/22_series/22874/fd8369b549b3d1a5c848cbd83659cae9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d1aef1c6c6629bcd3939b4e9c602a4171fc9229
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/fd8369b549b3d1a5c848cbd83659cae9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:958fcfc891d941c3a0f17c12d08710c4ec6a2c862ee1c6a78ffe4f92f2252a02
+size 29097
diff --git a/marked/Rel-18/22_series/22874/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-18/22_series/22874/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c1acfd8a5846230afdfa4565906a58c7e202dcf
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3e4ede60950ca44839b8f67d58c10801db0a63a394b30033f5566c51b3cce03
+size 35528
diff --git a/marked/Rel-18/22_series/22874/raw.md b/marked/Rel-18/22_series/22874/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f1a370de7f82495139ef5fdae074fef37e2689c
--- /dev/null
+++ b/marked/Rel-18/22_series/22874/raw.md
@@ -0,0 +1,2594 @@
+
+
+# 3GPP TR 22.874 V18.2.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on traffic characteristics and performance requirements for AI/ML model transfer in 5GS (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+AMMT, AI, ML
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-----------------------------------------------------------------------------------|----|
+| Foreword ..... | 6 |
+| Introduction ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions, symbols and abbreviations..... | 10 |
+| 3.1 Definitions..... | 10 |
+| 3.2 Abbreviations ..... | 10 |
+| 4 Overview..... | 11 |
+| 5 Split AI/ML operation between AI/ML endpoints ..... | 12 |
+| 5.1 Split AI/ML image recognition ..... | 12 |
+| 5.1.1 Description ..... | 12 |
+| 5.1.2 Pre-conditions..... | 14 |
+| 5.1.3 Service Flows ..... | 14 |
+| 5.1.4 Post-conditions ..... | 15 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 15 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 15 |
+| 5.1.6.1 Potential KPI Requirements..... | 15 |
+| 5.2 Enhanced media recognition: Deep Learning Based Vision Applications ..... | 16 |
+| 5.2.1 Description ..... | 16 |
+| 5.2.2 Pre-conditions..... | 17 |
+| 5.2.3 Service Flows ..... | 17 |
+| 5.2.4 Post-conditions ..... | 17 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 17 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 18 |
+| 5.3 Media quality enhancement: Video streaming upgrade..... | 18 |
+| 5.3.1 Description ..... | 18 |
+| 5.3.2 Pre-conditions..... | 19 |
+| 5.3.3 Service Flows ..... | 19 |
+| 5.3.4 Post-conditions ..... | 19 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 19 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 19 |
+| 5.4 Split control for robotics ..... | 20 |
+| 5.4.1 Description ..... | 20 |
+| 5.4.2 Pre-conditions..... | 21 |
+| 5.4.3 Service Flows ..... | 21 |
+| 5.4.4 Post-conditions ..... | 22 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 22 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 22 |
+| 5.4.6.1 Potential KPI Requirements..... | 22 |
+| 5.5 Session-specific model transfer split computation operations ..... | 23 |
+| 5.5.1 Description ..... | 23 |
+| 5.5.2 Pre-conditions..... | 23 |
+| 5.5.3 Service Flows ..... | 23 |
+| 5.5.4 Post-conditions ..... | 24 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 24 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 25 |
+| 6 AI/ML model/data distribution and sharing over 5G system ..... | 25 |
+| 6.1 AI/ML model distribution for image recognition ..... | 25 |
+| 6.1.1 Description ..... | 25 |
+| 6.1.2 Pre-conditions..... | 26 |
+| 6.1.3 Service Flows ..... | 26 |
+| 6.1.4 Post-conditions ..... | 27 |
+| 6.1.5 Existing features partly or fully covering the use case functionality ..... | 27 |
+
+| | | |
+|---------|---------------------------------------------------------------------------------------|----|
+| 6.1.6 | Potential New Requirements needed to support the use case..... | 27 |
+| 6.1.6.1 | Potential KPI Requirements..... | 27 |
+| 6.2 | Real time media editing with on-board AI inference..... | 28 |
+| 6.2.1 | Description ..... | 28 |
+| 6.2.2 | Pre-conditions..... | 29 |
+| 6.2.3 | Service Flows ..... | 30 |
+| 6.2.4 | Post-conditions ..... | 30 |
+| 6.2.5 | Existing features partly or fully covering the use case functionality ..... | 30 |
+| 6.2.6 | Potential New Requirements needed to support the use case..... | 30 |
+| 6.2.6.1 | Introduction..... | 30 |
+| 6.2.6.2 | Potential KPI Requirements..... | 32 |
+| 6.3 | AI/ML model distribution for speech recognition ..... | 33 |
+| 6.3.1 | Description ..... | 33 |
+| 6.3.2 | Pre-conditions..... | 33 |
+| 6.3.3 | Service Flows ..... | 34 |
+| 6.3.4 | Post-conditions ..... | 34 |
+| 6.3.5 | Existing features partly or fully covering the use case functionality ..... | 34 |
+| 6.3.6 | Potential New Requirements needed to support the use case..... | 34 |
+| 6.3.6.1 | Potential KPI Requirements..... | 34 |
+| 6.4 | AI model management as a Service..... | 35 |
+| 6.4.1 | Description ..... | 35 |
+| 6.4.2 | Pre-conditions..... | 35 |
+| 6.4.3 | Service Flows ..... | 36 |
+| 6.4.4 | Post-conditions ..... | 36 |
+| 6.4.5 | Existing features partly or fully covering the use case functionality ..... | 36 |
+| 6.4.6 | Potential New Requirements needed to support the use case..... | 36 |
+| 6.5 | AI/ML based Automotive Networked Systems ..... | 36 |
+| 6.5.1 | Description ..... | 36 |
+| 6.5.2 | Pre-conditions..... | 38 |
+| 6.5.3 | Service Flows ..... | 38 |
+| 6.5.4 | Post-conditions ..... | 39 |
+| 6.5.5 | Existing features partly or fully covering the use case functionality ..... | 40 |
+| 6.5.6 | Potential New Requirements needed to support the use case..... | 40 |
+| 6.6 | Shared AI/ML model monitoring..... | 41 |
+| 6.6.1 | Description ..... | 41 |
+| 6.6.2 | Pre-conditions..... | 41 |
+| 6.6.3 | Service Flows ..... | 42 |
+| 6.6.4 | Post-conditions ..... | 42 |
+| 6.6.5 | Existing features partly or fully covering the use case functionality ..... | 42 |
+| 6.6.6 | Potential New Requirements needed to support the use case..... | 42 |
+| 6.7 | Prediction of AI/ML model distribution ..... | 42 |
+| 6.7.1 | Description ..... | 42 |
+| 6.7.2 | Pre-conditions..... | 43 |
+| 6.7.3a | Service Flows for Prediction based on monitoring function of the 5G network..... | 43 |
+| 6.7.3b | Service Flows for Prediction based on NWDAF analytics function of the 5G network..... | 43 |
+| 6.7.4 | Post-conditions ..... | 44 |
+| 6.7.5 | Existing features partly or fully covering the use case functionality ..... | 44 |
+| 6.7.6 | Potential Requirements..... | 44 |
+| 7 | Distributed/Federated Learning over 5G system ..... | 44 |
+| 7.1 | Uncompressed Federated Learning for image recognition ..... | 44 |
+| 7.1.1 | Description ..... | 44 |
+| 7.1.2 | Pre-conditions..... | 46 |
+| 7.1.3 | Service Flows ..... | 46 |
+| 7.1.4 | Post-conditions ..... | 47 |
+| 7.1.5 | Existing features partly or fully covering the use case functionality ..... | 47 |
+| 7.1.6 | Potential New Requirements needed to support the use case..... | 47 |
+| 7.1.6.1 | Potential KPI Requirements..... | 47 |
+| 7.2 | Compressed Federated Learning for image/video processing ..... | 48 |
+| 7.2.1 | Description ..... | 48 |
+| 7.2.2 | Pre-conditions..... | 50 |
+| 7.2.3 | Service Flows ..... | 50 |
+
+| | | |
+|-----------------|-------------------------------------------------------------------------------------------|------------|
+| 7.2.4 | Post-conditions ..... | 50 |
+| 7.2.5 | Existing features partly or fully covering the use case functionality ..... | 50 |
+| 7.2.6 | Potential New Requirements needed to support the use case..... | 52 |
+| 7.3 | Data Transfer Disturbance in Multi-agent multi-device ML Operations..... | 52 |
+| 7.3.1 | Description ..... | 52 |
+| 7.3.2 | Pre-conditions..... | 54 |
+| 7.3.3 | Service Flows ..... | 55 |
+| 7.3.4 | Post-conditions ..... | 56 |
+| 7.3.5 | Existing features partly or fully covering the use case functionality ..... | 57 |
+| 7.3.6 | Potential New Requirements needed to support the use case..... | 57 |
+| 7.4 | Group Performance “Flocking” Use Case ..... | 59 |
+| 7.4.1 | Description ..... | 59 |
+| 7.4.2 | Pre-conditions..... | 60 |
+| 7.4.3 | Service Flows ..... | 60 |
+| 7.4.4 | Post-conditions ..... | 61 |
+| 7.4.5 | Existing features partly or fully covering the use case functionality ..... | 61 |
+| 7.4.6 | Potential New Requirements needed to support the use case..... | 61 |
+| 8 | Consolidated potential requirements..... | 61 |
+| 8.1 | KPI for AMMT services..... | 61 |
+| 8.2 | Functional requirements for AMMT services ..... | 63 |
+| 9 | Conclusion and recommendations ..... | 64 |
+| Annex A: | Introduction to AI/ML models ..... | 66 |
+| A.1 | AI and ML..... | 66 |
+| A.2 | Deep neural network ..... | 69 |
+| A.3 | Training and inference ..... | 72 |
+| A.4 | Widely-used DNN models and algorithms ..... | 75 |
+| Annex B: | General principle of split AI/ML operation between AI/ML endpoints ..... | 83 |
+| Annex C: | General principle of AI/ML model/data distribution and sharing over 5G system..... | 95 |
+| Annex D: | General principle of Distributed/Federated Learning over 5G system..... | 100 |
+| Annex E: | Change history ..... | 109 |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+This document covers use cases and potential requirements for 5G system support of Artificial Intelligence (AI)/Machine Learning (ML) model distribution and transfer (download, upload, updates, etc.). The TR on AI/ML services includes three aspects: AI/ML operation splitting between AI/ML endpoints, AI/ML model/data distribution and sharing over 5G system, distributed/Federated Learning over 5G system.
+
+# 1 Scope
+
+This report captures the study of the use cases and the potential performance requirements for 5G system support of Artificial Intelligence (AI)/Machine Learning (ML) model distribution and transfer (download, upload, updates, etc.), and identifies traffic characteristics of AI/ML model distribution, transfer and training for various applications, e.g. video/speech recognition, robot control, automotive, other verticals.
+
+The aspects addressed include:
+
+- AI/ML operation splitting between AI/ML endpoints;
+- AI/ML model/data distribution and sharing over 5G system;
+- Distributed/Federated Learning over 5G system.
+
+Study of the AI/ML models themselves are not in the scope of the TR.
+
+# 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.891, Feasibility Study on New Services and Markets Technology Enablers
+- [3] 3GPP TR 22.863, Feasibility study on new services and markets technology enablers for enhanced mobile broadband
+- [4] 3GPP TS 22.261, Service requirements for the 5G system
+- [5] 3GPP TS 22.104, Service requirements for cyber-physical control applications in vertical domains
+- [6] 3GPP TS 23.273, 5G System (5GS) Location Services (LCS); Stage 2
+- [7] A. Krizhevsky, I. Sutskever, and G. E. Hinton, "ImageNet classification with deep convolutional neural networks", in Proc. NIPS, 2012, pp. 1097–1105.
+- [8] K. Simonyan and A. Zisserman, "Very deep convolutional networks for large-scale image recognition," 2014, arXiv:1409.1556. [Online]. Available:
+- [9] C. Szegedy, et al., "Going deeper with convolutions", in Proc. CVPR, 2015, pp. 1-9.
+- [10] Zhi Zhou, Xu Chen, En Li, Liekang Zeng, Ke Luo, Junshan Zhang, "Edge intelligence: Paving the last mile of artificial intelligence with edge computing", Proceeding of the IEEE, 2019, Volume 107, Issue 8.
+- [11] Jiasi Chen, Xukan Ran, "Deep learning with edge computing: A review", Proceeding of the IEEE, 2019, Volume 107, Issue 8.
+- [12] I. Stoica et al., "A Berkeley view of systems challenges for AI", 2017, arXiv:1712.05855. [Online]. Available:
+- [13] Y. Kang et al., "Neurosurgeon: Collaborative intelligence between the cloud and mobile edge", ACM SIGPLAN Notices, vol. 52, no. 4, pp. 615–629, 2017.
+
+- [14] E. Li, Z. Zhou, and X. Chen, "Edge intelligence: On-demand deep learning model co-inference with device-edge synergy", in Proc. Workshop Mobile Edge Commun. (MECOMM), 2018, pp. 31–36.
+- [15] 3GPP TR 38.913, Study on Scenarios and Requirements for Next Generation Access Technologies (Release 15)
+- [16] B. Kehoe, S. Patil, P. Abbeel, and K. Goldberg, "A survey of research on cloud robotics and automation," IEEE Transactions on automation science and engineering, vol. 12, no. 2, pp. 398–409, 2015.
+- [17] Huaijiang Zhu, Manali Sharma, Kai Pfeiffer, Marco Mezzavilla, Jia Shen, Sundeep Rangan, and Ludovic Righetti, "Enabling Remote Whole-body Control with 5G Edge Computing", to appear, in Proc. 2020 IEEE/RSJ International Conference on Intelligent Robots and Systems. Available at:
+- [18] K. He, X. Zhang, S. Ren, and J. Sun, "Deep residual learning for image recognition," in Proc. IEEE CVPR, Jun. 2016, pp. 770-778.
+- [19] A. G. Howard et al., "MobileNets: Efficient convolutional neural networks for mobile vision applications," 2017, arXiv:1704.04861. [Online]. Available:
+- [20] B. Taylor, V. S. Marco, W. Wolff, Y. Elkhatib, and Z. Wang, "Adaptive deep learning model selection on embedded systems," in Proc. ACM LCTES, 2018, pp. 31–43.
+- [21] G. Shu, W. Liu, X. Zheng, and J. Li, "IF-CNN: Image-aware inference framework for CNN with the collaboration of mobile devices and cloud", IEEE Access, vol. 6, pp. 621–633, 2018.
+- [22] D. Stamoulis et al., "Designing adaptive neural networks for energy-constrained image classification", in Proc. ACM ICCAD, 2018, Art. no. 23.
+- [23] Sergey Ioffe and Christian Szegedy. "Batch normalization: Accelerating deep network training by reducing internal covariate shift", In ICML., 2015.
+- [24] C.-J. Wu et al., "Machine learning at facebook: Understanding inference at the edge," in Proc. IEEE Int. Symp. High Perform. Comput. Archit. (HPCA), Feb. 2019, pp. 331–344.
+- [25] Vivienne Sze, Yu-Hsin Chen, Tien-Ju Yang, Joel S. Emer, "Efficient processing of deep neural networks: A tutorial and survey", Proceeding of the IEEE, 2017, Volume 105, Issue 12.
+- [26] Y. LeCun, Y. Bengio, and G. Hinton, "Deep learning," Nature, vol. 521, no. 7553, pp. 436-444, May 2015.
+- [27] "An All-Neural On-Device Speech Recognizer", March 12, 2019, Posted by Johan Schalkwyk,
+- [28] Yanzhang He, etc., "Streaming End-to-end Speech Recognition for Mobile Devices", 2019 IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP 2019)
+- [29] 3GPP TS 22.243: "Speech recognition framework for automated voice services; Stage 1".
+- [30] H. B. McMahan, E. Moore, D. Ramage, S. Hampson, and B. A. Y. Arcas, "Communication-efficient learning of deep networks from decentralized data", Proc. of the International Conference on Artificial Intelligence and Statistics, Apr. 20 17. [Online]. Available:
+- [31] "Federated Learning",
+- [32] T. Nishio and R. Yonetani, "Client selection for federated learning with heterogeneous resources in mobile edge", 2018, arXiv:1804.08333. [Online]. Available:
+- [33] E. Park et al., "Big/little deep neural network for ultra low power inference", in Proc. 10th Int. Conf. Hardw./Softw. Codesign Syst. Synth., 2015, pp. 124–132.
+
+- [34] Nguyen H. Tran ; Wei Bao ; Albert Zomaya ; Minh N. H. Nguyen ; Choong Seon Hong, "Federated Learning over Wireless Networks: Optimization Model Design and Analysis", In proc. IEEE INFOCOM 2019 - IEEE Conference on Computer Communications
+- [35] Song Han, Xingyu Liu, Huizi Mao, Jing Pu, Ardavan Pedram, Mark A Horowitz, and William J Dally. "EIE: efficient inference engine on compressed deep neural network", In 43rd International Symposium on Computer Architecture, IEEE Press, 243–254.
+- [36] V. Sze, "Efficient Computing for Deep Learning, AI and Robotics," Dept EECS, MIT, Available online at [https://lexfridman.com/files/slides/2020\\_01\\_15\\_vivienne\\_sze\\_efficient\\_computing.pdf](https://lexfridman.com/files/slides/2020_01_15_vivienne_sze_efficient_computing.pdf)
+- [37] V. Sze, Y. Chen, "Efficient Processing of Deep Neural Networks: A Tutorial and Survey" Proc. of IEEE, 2017, Available online at:
+- [38] Stanford University, CS231n – Lecture 5-7: CNN, Training NNs, Available at YouTube.com
+- [39] S. Han, J. Pool, J. Tran, and W. J. Dally, "Learning both weights and connections for efficient neural networks", NIPS, May 2015
+- [40] P. A. Merolla, et al., "A million spikingneuron integrated circuit with a scalable communication network and interface",Science, vol. 345, no. 6197, pp. 668–673, Aug. 2014.
+- [41] R. Collobert, J. Weston, L. Bottou, M. Karlen, K. Kavukcuoglu, and P. Kuksa, "Natural language processing (almost) from scratch," J. Mach. Learn. Res., vol. 12 pp. 2493–2537, Aug. 2011.
+- [42] T. N. Sainath, A.-R. Mohamed, B. Kingsbury, and B. Ramabhadran, "Deep convolutionalneural networks for LVCSR", in Proc. ICASSP, 2013, pp. 8614–8618.
+- [43] L. P. Kaelbling, M. L. Littman, and A. W. Moore, "Reinforcement learning: A survey", J. Artif. Intell. Res., vol. 4, no. 1, pp. 237–285, Jan. 1996.
+- [44] 3 AI Trends for Enterprise Computing. [Online]. Available:
+- [45] Shiming Ge ; Zhao Luo ; Shengwei Zhao ; Xin Jin ; Xiao-Yu Zhang, "Compressing deep neural networks for efficient visual inference", In proc. 2017 IEEE International Conference on Multimedia and Expo (ICME)
+- [46] 3GPP TS 22.186, Enhancement of 3GPP support for V2X scenarios; Stage 1 (Release 16) v16.2.0
+- [47] "Develop Smaller Speech Recognition Models with NVIDIA's NeMo Framework",
+- [48] 3GPP TS 23.501, System architecture for the 5G System (5GS)
+- [49] 3GPP TS 23.502, Procedures for the 5G System (5GS)
+- [50] S. Ren, K. He, R. Girshick, J. Sun, "Faster R-CNN: Towards Real-Time Object Detection with Region Proposal Networks"
+- [51] J. Redmon, A. Farhadi, "YOLOv3: An Incremental Improvement"
+- [52] W. Sun, Z. Chen, "Learned Image Downscaling for Upscaling using Content Adaptive Resampler"
+- [53] C. Ledig et al., "Photo-Realistic Single Image Super-Resolution Using a Generative Adversarial Network"
+- [54] A. G. Howard et al., "MobileNets: Efficient convolutional neural networks for mobile vision applications," 2017, arXiv:1704.04861. [Available online: ]
+- [55] SSD-ResNet34 - [https://github.com/IntelAI/models/tree/master/benchmarks/object\\_detection/tensorflow/ssd-resnet34](https://github.com/IntelAI/models/tree/master/benchmarks/object_detection/tensorflow/ssd-resnet34)
+
+- [56] MLCommons Mobile Inference Benchmark v0.7 -
+- [57] MASK C-RNN -
+- [58]
+- [59] 3GPP TR 28.809, Study on enhancement of management data analytics
+- [60] Mingzhe Chen, "A Joint Learning and Communications Framework for Federated Learning over Wireless Networks", Oct 2020
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**communication service availability:** percentage value of the amount of time the end-to-end communication service is delivered according to an agreed QoS, divided by the amount of time the system is expected to deliver the end-to-end service according to the specification in a specific area.
+
+NOTE 1: This definition was taken from TS 22.261 [4].
+
+**End-to-End Latency:** the time that takes to transfer a given piece of information from a source to a destination, measured at the communication interface, from the moment it is transmitted by the source to the moment it is successfully received at the destination.
+
+NOTE 2: The end point in "end-to-end" is assumed to be the communication service interface.
+
+NOTE 3: This definition was taken from TS 22.261 [4].
+
+**reliability:** in the context of network layer packet transmissions, percentage value of the amount of sent network layer packets successfully delivered to a given system entity within the time constraint required by the targeted service, divided by the total number of sent network layer packets.
+
+NOTE 4: This definition was taken from TS 22.261 [4].
+
+**user experienced data rate:** the minimum data rate required to achieve a sufficient quality experience, with the exception of scenario for broadcast like services where the given value is the maximum that is needed.
+
+NOTE 5: This definition was taken from TS 22.261 [4].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|-----|----------------------------|
+| AI | Artificial Intelligence |
+| CNN | Convolution Neural Network |
+| DNN | Deep Neural Network |
+| FL | Federated Learning |
+| GPU | Graphics Processing Units |
+| IDC | Internet Data Center |
+| ML | Machine Learning |
+
+# 4 Overview
+
+Artificial Intelligence (AI)/Machine Learning (ML) is being used in a range of application domains across industry sectors. In mobile communications systems, mobile devices (e.g. smartphones, automotive, robots) are increasingly replacing conventional algorithms (e.g. speech recognition, image recognition, video processing) with AI/ML models to enable applications. The 5G system can at least support three types of AI/ML operations:
+
+- AI/ML operation splitting between AI/ML endpoints;
+- AI/ML model/data distribution and sharing over 5G system;
+- Distributed/Federated Learning over 5G system.
+
+The scheme of split AI/ML inference can be depicted as in Figure 4-1. The AI/ML operation/model is split into multiple parts according to the current task and environment. The intention is to offload the computation-intensive, energy-intensive parts to network endpoints, whereas leave the privacy-sensitive and delay-sensitive parts at the end device. The device executes the operation/model up to a specific part/layer and then sends the intermediate data to the network endpoint. The network endpoint executes the remaining parts/layers and feeds the inference results back to the device.
+
+
+
+Figure 4-1: Example of split AI/ML inference. The diagram shows a flow from 'Inputs' to an 'End device' (represented by a mobile phone icon) which contains an 'End device partition (partial AI/ML operation/model)'. This partition processes the inputs and sends 'Intermediate data' to a 'Network AI/ML endpoint' (represented by a server icon) which contains a 'Network partition (partial AI/ML operation/model)'. The network partition then produces 'Inference outputs'.
+
+**Figure 4-1. Example of split AI/ML inference**
+
+The scheme of AI/ML model distribution can be depicted as in Figure 4-2. Multi-functional mobile terminals might need to switch the AI/ML model in response to task and environment variations. The condition of adaptive model selection is that the models to be selected are available for the mobile device. However, given the fact that the AI/ML models are becoming increasingly diverse, and with the limited storage resource in a UE, it can be determined to not pre-load all candidate AI/ML models on-board. Online model distribution (i.e. new model downloading) is needed, in which an AI/ML model can be distributed from a NW endpoint to the devices when they need it to adapt to the changed AI/ML tasks and environments. For this purpose, the model performance at the UE needs to be monitored constantly.
+
+
+
+Figure 4-2: AI/ML model downloading over 5G system. The diagram shows a cloud labeled 'AI/ML model pool' containing various model icons. An arrow labeled 'Online AI/ML model downloading' points from the cloud to a car icon. The car icon is associated with an 'Updated AI/ML model for new task and environment'. A dashed double-headed arrow labeled 'Change of task/environment' connects the car icon to another car icon, which is associated with an 'AI/ML model for current task and environment'.
+
+**Figure 4-2. AI/ML model downloading over 5G system**
+
+The scheme of Federated Learning (FL) can be depicted as in Figure 4-3. The cloud server trains a global model by aggregating local models partially-trained by each end devices. Within each training iteration, a UE performs the training based on the model downloaded from the AI server using the local training data. Then the UE reports the interim training results to the cloud server via 5G UL channels. The server aggregates the interim training results from the UEs and updates the global model. The updated global model is then distributed back to the UEs and the UEs can perform the training for the next iteration.
+
+
+
+Diagram of Federated Learning over 5G system. At the top, a cloud labeled '5G/6G cloud (Updating DNN by Federated averaging)' contains a DNN icon. Below it, two identical groups of devices (car, robot, smartphone, drone) are shown. Each group has a circular arrow labeled 'Iterative training'. Inside the circle, a DNN icon is shown with 'Subset of training data' pointing to it. Arrows between the cloud and the devices show 'Updated DNN with new weithts' (cloud to devices) and 'Partially-trained DNN with new gradients' (devices to cloud).
+
+Figure 4-3. Federated Learning over 5G system
+
+# 5 Split AI/ML operation between AI/ML endpoints
+
+## 5.1 Split AI/ML image recognition
+
+### 5.1.1 Description
+
+The AI/ML-based mobile applications are increasingly computation-intensive, memory-consuming and power-consuming. Meanwhile end devices usually have stringent energy consumption, compute and memory limitations for running a complete offline AI/ML inference on-board. Many AI/ML applications, e.g. image recognition, currently intent to offload the inference processing from mobile devices to internet datacenters (IDC). For example, photos shot by a smartphone are often processed in a cloud AI/ML server before shown to the user who shot them. However, the cloud-based AI/ML inference tasks need to take into account the computation pressure at IDCs, required data rate/latency and privacy protection requirement.
+
+Image and video are the biggest data on today's Internet. Videos account for over 70% of daily Internet traffic [4]. Convolutional Neural Network (CNN) models have been widely used for image/video recognition tasks on mobile devices, e.g. image classification, image segmentation, object localization and detection, face authentication, action recognition, enhanced photography, VR/AR, video games. Meanwhile, CNN model inference requires an intensive computation and storage resource. For example, AlexNet [7], VGG-16 [8] and GoogleNet [9] require 724M, 15.5G and 1.43G MACs (multiply-add computation) respectively for a typical image classification task.
+
+Many references [10-14] have shown that AI/ML inference for image processing with device-network synergy can alleviate the pressure of computation, memory footprint, storage, power and required data rate on devices, reduce end-to-end latency and energy consumption, and improve the end-to-end accuracy, efficiency and privacy when compared to the local execution approach on either side. The scheme of split AI/ML image recognition can be depicted in Figure 5.1.1-1. The CNN is split into two parts according to the current image recognition task and environment. The intention is to offload the computation-intensive, energy-intensive parts to network server, whereas leave the privacy-sensitive and delay-sensitive parts at the end device. The device executes the inference up to a specific CNN layer and sends the intermediate data to the network server. The network server runs through the remaining CNN layers. While the model is developed or invoked, the split AI/ML operation is based on the legacy model.
+
+Due to the characteristics of some algorithms in the model training phase, a model has a certain degree of robustness[xx-xy]. Therefore, if there are errors in the intermediate data transmission, the model has a certain tolerance
+
+and can still guarantee the accuracy of the inference results. Since the inference result needs to be forwarded to the UE, the reliability of the inference result transmission needs to be guaranteed.
+
+
+
+Figure 5.1.1-1: Example of split AI/ML image recognition. The diagram shows an image of a tree being processed by a CNN. The CNN is split into two parts: 'End device partition of CNN' and 'Network partition of CNN'. The 'End device partition' is located on the 'End device' (represented by a mobile phone icon) and processes the input image through several layers. The output of this partition is 'Intermediate data', which is then transmitted to the 'Network server' (represented by a server icon). The 'Network partition of CNN' processes the intermediate data through the remaining layers and produces the final output, which is the word 'tree'.
+
+**Figure 5.1.1-1. Example of split AI/ML image recognition**
+
+The split AI/ML image recognition algorithms can be analyzed based on the computation and data characteristics of the layers in the CNN. As shown in figure 5.1.1-2 and 5.1.1-3 (based on figures adopted from [13]), the intermediate data size transferred from one CNN layer to the next depends on the location of the split point. Hence, the required UL data rate is related to the model split point and the frame rate for the image recognition, as also observed by [13-14]. For example, assuming images from a video stream with 30 frames per second (FPS) need to be classified, the required UL data rate for different split points ranges from 4.8 to 65 Mbit/s (listed in Table 5.1.1-1). The result is based on the $227 \times 227$ input images. In case of images with a higher resolution, higher data rates would be required.
+
+
+
+Figure 5.1.1-2: Layer-level computation/communication resource evaluation for an AlexNet model. This is a dual-axis bar chart showing 'Latency (ms)' on the left Y-axis (0 to 40) and 'Data size (MB)' on the right Y-axis (0 to 1.5) for various layers of the AlexNet CNN. The X-axis lists the layers: input, conv1, relu1, pool1, norm1, conv2, relu2, pool2, norm2, conv3, relu3, conv4, relu4, conv5, relu5, pool5, fc6, relu6, drop6, fc7, relu7, drop7, fc8, softmax, and argmax. Five candidate split points are marked with vertical lines: 0 (after input), 1 (after pool1), 2 (after pool2), 3 (after pool5), and 4 (after argmax). Light blue bars represent layer latency, and dark blue bars represent the size of output data. The legend indicates 'Layer latency' for light blue and 'Size of output data' for dark blue.
+
+**Figure 5.1.1-2. Layer-level computation/communication resource evaluation for an AlexNet model**
+
+**Table 5.1.1-1: Required UL data rate for different split points of AlexNet model for video recognition @30FPS**
+
+| Split point | Approximate output data size (MByte) | Required UL data rate (Mbit/s) |
+|-----------------------------------------------------|--------------------------------------|--------------------------------|
+| Candidate split point 0
(Cloud-based inference) | 0.15 | 36 |
+| Candidate split point 1
(after pool1 layer) | 0.27 | 65 |
+| Candidate split point 2
(after pool2 layer) | 0.17 | 41 |
+| Candidate split point 3
(after pool5 layer) | 0.02 | 4.8 |
+| Candidate split point 4
(Device-based inference) | N/A | N/A |
+
+VGG-16 is another widely-used CNN model for image recognition. Still assuming images from a video stream with 30 FPS need to be classified, the required UL data rate for different split points ranges from 24 to 720 Mbit/s (listed in Table 5.1.1-2).
+
+
+
+Figure 5.1.1-3: Layer-level computation/communication resource evaluation for a VGG-16 model. This is a dual-axis bar chart showing 'Layer latency (ms)' on the left Y-axis (0 to 250) and 'Data size (MB)' on the right Y-axis (0 to 14). The X-axis lists layers of the VGG-16 CNN: input, conv1\_1, conv1\_2, pool1, conv2\_1, conv2\_2, pool2, conv3\_1, conv3\_2, conv3\_3, conv3\_4, pool3, conv4\_1, conv4\_2, conv4\_3, conv4\_4, pool4, conv5\_1, conv5\_2, conv5\_3, conv5\_4, pool5, fc6, drop6, fc7, drop7, fc8, softmax. Candidate split points are marked with arrows: 0 (before input), 1 (after pool1), 2 (after pool2), 3 (after pool3), 4 (after pool4), 5 (after pool5), and 6 (after softmax). Light blue bars represent layer latency, and dark blue bars represent the size of output data at each layer.
+
+Figure 5.1.1-3. Layer-level computation/communication resource evaluation for a VGG-16 model
+
+Table 5.1.1-2: Required user experienced UL data rate for different split points of VGG-16 model @30FPS
+
+| Split point | Approximate output data size (MByte) | Required user experienced UL data rate (Mbit/s) |
+|--------------------------------------------------|--------------------------------------|-------------------------------------------------|
+| Candidate split point 0 (Cloud-based inference) | 0.6 | 145 |
+| Candidate split point 1 (after pool1 layer) | 3 | 720 |
+| Candidate split point 2 (after pool2 layer) | 1.5 | 360 |
+| Candidate split point 3 (after pool3 layer) | 0.8 | 192 |
+| Candidate split point 4 (after pool4 layer) | 0.5 | 120 |
+| Candidate split point 5 (after pool5 layer) | 0.1 | 24 |
+| Candidate split point 6 (Device-based inference) | N/A | N/A |
+
+### 5.1.2 Pre-conditions
+
+The involved AI/ML endpoints (e.g. UE, AI/ML cloud/edge server) run applications providing the capability of AI/ML model inference for image recognition, and support the split AI/ML image recognition operation.
+
+The 5G system has the ability to provide 5G network related information to the AI/ML server.
+
+### 5.1.3 Service Flows
+
+- 1) The AI/ML based image recognition application is requested by the user to start recognizing the image/video shot by the UE.
+- 2) Under the determined split mode and split point, the AI/ML based image recognition application in an involved AI/ML endpoint executes the allocated part of AI/ML model, and sends the intermediate data to the next endpoint in the AI/ML pipeline.
+
+- 3) After all the involved AI/ML endpoints finish the co-inference, the image recognition results are fed to the user using the results.
+- 4) The AI/ML based image recognition applications in the endpoints perform the split image recognition until the image recognition task is terminated.
+
+Redo Step 3) and 4) for split mode/point re-selection/switching if needed to adapt to the changing conditions.
+
+### 5.1.4 Post-conditions
+
+The objects in the input images or videos are recognized and the recognition accuracy and latency need to be guaranteed.
+
+The image recognition task can be completed under the available computation and energy resource of the UE. And the consumed the computation, communication and energy resources over the AI/ML endpoints are optimized.
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+This use case mainly requires high data rate together with low latency. The high data rate requirements to 5G system are listed in Clause 7.1 and 7.6 of TS22.261 [4]. As in Table 7.1-1 of [4], 300Mbps DL experienced data rate and 50Mbps UL experienced data rate are required in dense urban scenario, and 1Gbps DL experienced data rate and 500Mbps UL experienced data rate are required in indoor hotspot scenario. As in Table 7.6.1-1 of [4], cloud/edge/split rendering-related data transmission requires up to 0.1Gbps data rate with [5-10]ms latency countrywide.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+The “image recognition latency” can be defined as the latency from the image is captured to the recognition results of the image are output to the user application, which was not specially addressed in [4][15]. Following the principle of analyzing the latency and data rate requirements of split image recognition introduced in Section 5.1.1, the image recognition latency is related to the user application the recognition is used for.
+
+Computer vision and image recognition have been widely used for many important mobile applications such as object recognition, photo enhancements, intelligent video surveillance, mobile AR, remote-controlled automotive, industrial control and robotics. The image recognition is usually a step of the processing pipeline of the application. And the recognition latency is a part of the end-to-end latency, as depicted in Figure 5.1.6-1.
+
+
+
+The diagram shows two sequential rounded rectangular boxes. The first box is labeled 'Image recognition' and the second box is labeled 'Subsequent processing for the application'. An arrow points from the first box to the second. Below the first box, a horizontal bracket labeled 'Image recognition latency' spans its width. Below both boxes, a larger horizontal bracket labeled 'End-to-end latency for the application' spans the combined width of both boxes.
+
+Diagram illustrating image recognition latency as a part of end-to-end latency.
+
+**Figure 5.1.6-1. Image recognition latency is a part of end-to-end latency**
+
+For example, if the image recognition results are just used for the object recognition e.g. unknown object recognition for smartphone user or criminal searching in database for intelligent security, it is acceptable that the image recognition is finished in seconds. If the image recognition result is used as an input to another time-sensitive application, e.g. AR display/gaming, remote-controlled automotive, industrial control and robotics, a much more stringent latency will be required. Based on the end-to-end latency requirements of the applications, the image recognition latency requirement can be derived, as listed in Table 5.1.6-1.
+
+#### 5.1.6.1 Potential KPI Requirements
+
+The potential KPI requirements needed to support the use case include:
+
+[P.R.5.1-001] The 5G system shall support intermediate data uploading for split image recognition with a maximum latency as given in Table 5.1.6.1-1.
+
+[P.R.5.1-002] The 5G system shall support intermediate data uploading for split image recognition with a user experienced UL data rate as given in Table 5.1.6.1-1.
+
+[P.R.5.1-003] The 5G system shall support intermediate data uploading for split image recognition with communication service availability not lower than 99.999 %.
+
+[P.R.5.1-004] The 5G system shall support inference results downloading for split image recognition with reliability not lower than 99.999 % and intermediate data uploading for split image recognition with reliability not lower than 99.9%.
+
+NOTE: Above requirements apply to intermediate data with a maximum size of 0.27MB (for AlexNet model) or 1.5 MB (for VGG-16 model).
+
+**Table 5.1.6.1-1: Image recognition latency and UL data rate for intermediate data uploading**
+
+| User application | Latency: maximum | | | User experienced UL data rate | |
+|-------------------------------------------------------|-----------------------|---------------------------|-------------------------------------|---------------------------------------|--------------------------------------|
+| | End-to-end latency | Image recognition latency | Intermediate data uploading latency | AlexNet
(Fig. 5.1.1-1, see note 4) | VGG-16
(Fig. 5.1.1-2, see note 4) |
+| One-shot object recognition at smartphone | Several seconds | ~1s | ~100ms | 1.6~21.6Mbit/s | 8~240Mbit/s |
+| Person identification in security surveillance system | Several seconds | ~1s | ~100ms | 1.6~21.6Mbit/s | 8~240Mbit/s |
+| Photo enhancements at smartphone | Several seconds | ~1s | ~100ms | 1.6~21.6Mbit/s | 8~240Mbit/s |
+| Video recognition | Several seconds | 33ms@30FPS | ~10ms | 16~216Mbit/s | 80Mbit/s~2.4Gbit/s |
+| AR display/gaming | 7~15ms (see note 1) | <5ms | 2ms | 80Mbit/s~1.08Gbit/s | 0.4~12Gbit/s |
+| Remote driving | 10ms (see note 2) | <5ms | 2ms | 80Mbit/s~1.08Gbit/s | 0.4~12Gbit/s |
+| Remote-controlled robotics | 10~100ms (see note 3) | <5ms | 2ms | 80Mbit/s~1.08Gbit/s | 0.4~12Gbit/s |
+
+NOTE 1: According to [4][5], the VR motion-to-photon latency is in the range of 5-15ms.
+NOTE 2: According to [46] the one-way latency required for remote driving is 5ms. The round-trip latency is assumed to be 10ms.
+NOTE 3: According to [5] the end-to-end latency required for video-operated remote-controlled robotics is 10~100ms.
+NOTE 4: As listed in table 5.1.1-1 and table 5.1.1-2, the intermediate data size for the split points of AlexNet and VGG-16 is 0.02 ~ 0.27MByte and 0.1 ~ 3MByte respectively.
+
+## 5.2 Enhanced media recognition: Deep Learning Based Vision Applications
+
+### 5.2.1 Description
+
+A tourist is wandering around a city and discovering the attractions and sights of the city. The user sees a beautiful object and she decides to shoot a video of the object. The application uses deep learning algorithms to process the video and identify the object of interest and provide historical information about it to the user. Furthermore, the application uses deep learning to reconstruct a 3D model of the object of interest by using the captured 2D video.
+
+As an example, we investigate Feature Pyramid Network (FPN)-based object detection approaches. These networks are usually composed of a backbone FPN and a head that performs task-specific inference. The FPN processes the input images at different scales to allow for the detection of small-scale and large-scale features. The head may for instance segment the objects, infer a bounding box for the objects, or classify the objects.
+
+The FPN backbone constitutes the most complex portion of the network and lends itself to be offloaded to the edge/cloud. The backbone is a common part to a wide range of networks that can perform different tasks. The produced feature maps can then be sent back to the UE for task-specific inference.
+
+A breakdown of the network architecture is shown in the following figure:
+
+
+
+Figure 5.2.1-1: Example Multi-Task Network. The diagram illustrates a CNN architecture with a Backbone ConvNet on the left. The backbone consists of multiple stages, with Res2, Res3, and Res4 stages highlighted. The Res2 stage output is at 1/4 image resolution, Res3 at 1/8, and Res4 at 1/16. These outputs are fed into an FPN (Feature Pyramid Network) on the right. The FPN consists of three prediction heads, each labeled 'predict'. A dashed box shows a detail of the FPN structure: it takes an input, passes it through a '1x1 conv' layer, then adds it to the input via a skip connection (indicated by '+'), and finally applies a '2x up' sampling operation. A note indicates that FPN weights are initialized randomly and that the diagram is simplified with 3 levels (typically 5 or 6).
+
+**Figure 5.2.1-1. Example Multi-Task Network**
+
+As shown in figure 5.2.1-1, a classical CNN architecture is used as the core. The FPN is used to extract features at different scales of the image, making it scale-invariant. The prediction tasks constitute the head of the network. By plugging in different network heads, different AI tasks can be performed. This makes the network a Multi-Task Network (MTN). For example, a Region Proposal Network can be appended to detect and frame objects in the input sequence by outputting bounding boxes. Other Task-specific Heads can be appended to detect humans and poses, classify objects, track objects, etc.
+
+### 5.2.2 Pre-conditions
+
+The user wants to receive instantaneous information and reconstruction to enhance their experience. The user's device is battery operated.
+
+### 5.2.3 Service Flows
+
+1. User opens their camera app and starts shooting a video
+2. Application pre-processes the video to prepare it for inference
+ - NOTE: Pre-processing is assumed to be not very intensive in this use case, e.g. downscaling the video, adjusting the frame rate, extracting simple features.
+3. The application streams the extracted features and/or the video to the edge/cloud for processing.
+4. The network performs the split-inference (e.g. only running the backbone) and streams the results back to the client
+5. The application runs task-specific inference to solve the specific task of interest (e.g. object detection, tracking, ...)
+6. The application uses the inferred labels and classes to enhance the user's view
+
+### 5.2.4 Post-conditions
+
+The user gets enhanced information extracted from the video about the object of interest that the user was shooting a video of.
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+The potential KPI requirements to support the use case are as given in Table 5.2.6.1-1, based on two examples of object detection models/algorithms:
+
+- uplink streaming latency not higher than [100-200ms] and a user experienced UL data rate of [100-1500] kbit/s;
+- downlink streaming latency not higher than [100-500ms] and a user experienced DL data rate of [32-150] Mbit/s;
+
+**Table 5.2.6.1-1: Recognition: latency breakdown and user experienced UL/DL data rates**
+
+| Recognition Task | Latency: maximum (see note 4) | User experienced DL data rate | | User experienced UL data rate | |
+|--------------------------------|-------------------------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------|-----------------|
+| | | Faster R-CNN [50] (see note 1) | YOLOv3 [51] (see note 2) | Faster R-CNN | YOLOv3 |
+| Uplink Streaming | 100-200ms | | | 100-1000 kbit/s | 200-1500 kbit/s |
+| Generic FPN Inference | 100-500ms | FPN:
4-10fps
Sum(Pi)~1MB/frame
32-100Mbit/s
uncompressed (see note 3)
Compression factor 10~100 | Multiple scale (similar to FPN):
1.5 MB feature map/frame
40-150 Mbit/s
uncompressed
Compression factor 10~100 | | |
+| Object Classification | 20-50ms | Performed on UE | Performed on UE | | |
+| Bounding Box Detection | 20-50ms | Performed on UE | Performed on UE | | |
+| Object Tracking | 50-150ms | Performed on UE | Performed on UE | | |
+| Enhanced Information Retrieval | | Few kBytes per request | | Few kBytes per request | |
+| Overlay Rendering | 10ms | Performed on UE | | Performed on UE | |
+
+Note 1: Faster R-CNN uses an input image size of 3x224x224. The video is downscaled on the UE to that target resolution and then compressed (e.g. using HEVC) and streamed to the edge for further processing.
+
+Note 2: YOLOv3 uses an input image size of 3x416x416. The captured video is downscaled on the UE to the target resolution and compressed prior to streaming to the edge.
+
+Note 3: Faster R-CNN uses an FPN with ResNet 101 as backbone; thus resulting in feature maps {P2=(256x56x56), P3=(256x28x2), P4=(256x14x14), P5=(256x7x7)}.
+
+Note 4: the latency estimates assume an overall latency of around 1s from a user pointing at an object until overlay information is displayed to the user.
+
+## 5.3 Media quality enhancement: Video streaming upgrade
+
+### 5.3.1 Description
+
+A user is playing a VR game on the cloud using their VR headset. The game is being rendered on the cloud and streamed down to the UE. The user wants to enjoy an immersive gaming experience which requires very high quality video, e.g. 8K per eye at 120 frames per second. The cloud game server can only produce 4K video data due to hardware, load, and networking restrictions. AI is used to upscale the 4K content into 16K content for a better user experience.
+
+The following figure shows an example of such a network:
+
+
+
+Diagram of a DNN-based Down/Up-scaler architecture. An HR image is processed by a ResamplerNet (containing ConvBlock, ResBlock, and DownsampleBlock components) to produce kernel weights and offsets. These are used in a Resample Down scaling step to generate an LR output. The LR output is then processed by an SRNet (EDSR) containing ConvBlock, ResBlock, and UpsampleBlock components to produce the final SR image. A legend at the bottom defines the internal structures of the ConvBlock, ResBlock, DownsampleBlock, and UpsampleBlock.
+
+**Figure 5.3.1-1. Example DNN-based Down/Up-scaler**
+
+The Low Resolution video is streamed to the UE, which will process the video to infer the high resolution version. The down-sampling and up-sampling parts of the network are matched to produce best results. Any updates to the down-sampling part of network would require updates on the UE-side to the up-sampling part of the network. In addition to the LR version of the video, model weights and topology updates may need to be sent to the UE.
+
+The pre-trained models are optimized to the type of content (e.g. sport, cartoons, movie, ...) and to the scale factor. As the user switches to a different piece of content, the device will check if the corresponding pre-trained model weights are already downloaded in the cache. If not available, the UE will download the pre-trained model weights for the selected piece of content and based on the desired up-scaling factor. The new content is shown to the user in less than 3 seconds from the user selecting it.
+
+### 5.3.2 Pre-conditions
+
+The remote gaming server generates streams metadata together with the stream that is extracted by running AI autoencoder on the originally captured content.
+
+### 5.3.3 Service Flows
+
+1. Users starts a cloud VR gaming session on their HMD
+2. The game is launched on the cloud server and the game can start
+3. The cloud server renders and captures the content and downscales it to 4K video
+4. The cloud server also runs a DNN to produce a metadata stream that will be used for upscaling
+5. The UE uses a reverse DNN network to upscale the received 4K stream to 16K. The input to the DNN is the 4K video and the metadata stream.
+6. The UE renders the high quality 16K view on the HMD.
+
+### 5.3.4 Post-conditions
+
+The user enjoys a high-quality VR experience.
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+The potential KPI requirements to support the use case are:
+
+[P.R.5.3-001] The 5G system shall support the delivery of pre-trained model weights and weight updates with a latency no more than 3 seconds.
+
+NOTE 1: the model download time takes into account acceptable channel switch time, which generally should not exceed 2-3 seconds.
+
+The following table provides an estimate of the model weight sizes:
+
+**Table 5.3.6.1-1: Model Weight Sizes and Data rates**
+
+| Model Name (see note 2) | Model Weight Size (see note 4) | Data Rate (see note 3) |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------------------------------|
+| CAR 4x [52] | Downsampling: ~40MB
Upsampling: ~170MB | Upsampling model download:
450Mbit/s (downloaded over a period of 3 seconds) |
+| SR-GAN 4x [53] | Downsampling: N/A (bicubic)
Upsampling: ~6MB | Upsampling model download:
12Mbit/s (downloaded over a period of 3 seconds) |
+| SRResNet 4x [53] | Downsampling: N/A (bicubic)
Upsampling: ~6MB | Upsampling model download:
12Mbit/s (downloaded over a period of 3 seconds) |
+| NOTE 2: the size of the weights of the pre-trained models depends on the nature of the content and the scaling factor of the video. | | |
+| NOTE 3: model weight download is triggered by change of content by the user and thus results in bursty traffic by nature with relatively long off periods. | | |
+| NOTE 4: all model weight sizes are from pre-trained PyTorch models. | | |
+
+## 5.4 Split control for robotics
+
+### 5.4.1 Description
+
+Mobile robots have been playing an increasingly important role in some scenarios, e.g. warehouse, disaster rescue and smart factories [5], thanks to their high mobility. The mobile robots need to work in an ever-changing environment, hence need to perform fast and reliable sensing, planning and controlling. If the corresponding computation is performed on board in the robot, it will require intensive computations which lead to increased requirements of computation capabilities and power consumption. However, a light-weight form factor is always a requirement to the mobile robots working in the real-world environment, which prevents the robots to be equipped with a large number of CPU/GPU units and large-capacity batteries. As the example provided in [17], an advanced commercially available quadruped robot, carries 3kg of batteries of about 650Wh energy, while the high-end GPU consumes more than 250W of power, significantly impacting battery life if such computational power was embedded on the robot.
+
+Offloading computations from robots to the cloud has been studied in many references [16]. Meanwhile relying on either data or code from a network to support the robot's operation, the designers of autonomous mobile robots have to consider the scenarios where the robots must include capacity of local processing for low-latency responses during periods when network access quality is varying worse.
+
+The resulting system is different from the fully remote-controlled robot system described in [5], in which the planning and controlling are carried out by cloud computing, and the robots only reports the sensing data (incl. video), and receives the control commands. Since the complete cloud computing can hardly meet the latency requirement of the ms-level feedback control loop of some types of mobile robots, e.g. legged robots, the split control of mobile robots is an agreeable solution in this case.
+
+[17] introduces a robot whole-body balance control split over 5G network. The AI inference for the controlling can be split between the robot and the cloud server: As shown in Figure 5.4.1-1, the part which is complex but less susceptible to delays is offloaded to the remote computation in the cloud or edge control server. The low-complexity part which contains the error feedback terms and is latency-critical can be efficiently done by the local computation in the robot. If the robot fails to receive the optimal control from "remote control part" from the cloud/edge control server due to communication delays or packet loss, it can approximate the "remote control part" using pre-computed feedback matrices received previously. And in certain duration, the approximation will still enable the robot to perform feedback control for the tasks approximately and ensure that the robot can still operate.
+
+
+
+The diagram illustrates the split control architecture for a legged robot. On the left, a 'Robot' icon is shown. Above it, a box labeled 'Local computation (Low complexity)' is connected to the robot. Below this box, an arrow labeled 'Local control (latency-critical)' points down to the robot. On the right, a 'Cloud/edge control server' icon is shown. Above it, a box labeled 'Remote computation (High complexity)' is connected to the server. In the center, a 5G network icon (tower) is shown. Two arrows pass through the network: the top arrow is labeled 'Remote control (Less delay sensitive)' and points from the server to the robot; the bottom arrow is labeled 'Sensing data' and points from the robot to the server.
+
+Figure 5.4.1-1: Split control of legged robot over 5G network. The diagram shows a robot on the left and a cloud/edge control server on the right, connected via a 5G network. The robot performs 'Local computation (Low complexity)' and 'Local control (latency-critical)'. The 5G network handles 'Remote control (Less delay sensitive)' and 'Sensing data'. The server performs 'Remote computation (High complexity)'.
+
+**Figure 5.4.1-1. Split control of legged robot over 5G network**
+
+The results in [17] show that, in case the robot is completely controlled by a cloud server, the robot cannot finish the walking task if the round-trip latency is larger than 3ms (from sending sensing data to receiving control commands, including processing at cloud/edge). Due to delayed control commands, the robot would fall down (as shown in Figure 5.4.1-2 (a)). However, if the split control is employed, a worse-case 25ms round-trip latency can be sustained, and the robot can still perform the walking task (as shown in Figure 5.4.1-2 (b)).
+
+
+
+The image displays two simulation results side-by-side. Both show a green and yellow legged robot on a grey grid floor. In (a), the robot is tilted at a steep angle, with its right leg on the ground and its body falling towards the left. In (b), the robot is standing upright and stable on the grid.
+
+Figure 5.4.1-2: Simulated performance of robot whole-body balance control over 5G network with 25ms round-trip latency. The image shows two side-by-side simulation views. (a) shows the robot falling over, indicating failure. (b) shows the robot maintaining balance, indicating success.
+
+**(a) 5G remote control without local control (b) 5G remote control with local control at robot**
+
+**Figure 5.4.1-2. Simulated performance of robot whole-body balance control over 5G network with 25ms round-trip latency**
+
+### 5.4.2 Pre-conditions
+
+The involved AI/ML endpoints (e.g. UE (robot), AI/ML cloud/edge server) run applications providing the capability of AI/ML model inference for robot control task, and support the split robot control operation.
+
+The 5G system has the ability to provide 5G network related information to the AI/ML server.
+
+### 5.4.3 Service Flows
+
+1. The UE (robot) is connected with the cloud/edge control server via 5G network.
+2. The split of the control operations on robot side and cloud/edge control server side for the robot control task is determined by the robot or the network.
+3. Under the determined split mode and split point, the robot performs the local control computation based on the collected sensing data, and sends the sensing data to the cloud/edge control server. The cloud/edge control server performs the remote control computation, and feeds the outputs back to the robot.
+4. The robot controls its motion jointly based on the outputs of local and remote control computations.
+
+5. Start with Step 3) with more control operations, until the robot control task is terminated.
+
+### 5.4.4 Post-conditions
+
+The robot receives the control from local and remote with required accuracy and latency, so to finish the moving tasks, e.g. balance task and walking task.
+
+The robot control task can be completed under the available computation and energy resource of the robot. And the consumed the computation, communication and energy resources over the AI/ML endpoints are optimized.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+This use case mainly requires high data rate together with low latency. The high data rate requirements to 5G system are listed in Clause 7.1 and 7.6 of TS22.261 [4]. As in Table 7.1-1 of [4], 300Mbps DL experienced data rate and 50Mbps UL experienced data rate are required in dense urban scenario, and 1Gbps DL experienced data rate and 500Mbps UL experienced data rate are required in indoor hotspot scenario. As in Table 7.6.1-1 of [4], cloud/edge/Split rendering-related data transmission requires up to 0.1Gbps data rate with [5-10]ms latency countrywide.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+If everything is done on the edge part, the robot needs to send 592B sensing data per control cycle (every millisecond) and receive 200B per control cycle from the “remote controller”, which leads to a UL data rate of 4.7Mbit/s and a DL data rate of 1.6Mbit/s. However maximum round-trip latency is limited to 3ms, and the one-way latency for downloading “remote control part” needs to be limited to 1ms. If the splitting strategy is followed, downloading the “remote control part” from the cloud/edge control server requires downloading a 40kB data burst per control cycle (every millisecond) as more information is needed to ensure the local controller can take over in case of unexpected latencies, which leads to a user experienced DL data rate of 320Mbit/s. In that case, a maximum round-trip latency of 25ms can be tolerated between each control cycle, and the one-way latency for downloading “remote control part” can be relaxed to 12ms.
+
+This implies a trade-off between DL data rate and latency: Compared with the full control at edge, the split control mode requires a higher user experienced DL data rate, but relaxes the stringent latency requirement. Different from the traditional URLLC services requiring continuous coverage of 5G network which can only be provided with FR1 spectrum, for a 5G operator with FR2 spectrum, the split control for robotics can be offloaded to the 5G mmWave network with non-continuous coverage.
+
+#### 5.4.6.1 Potential KPI Requirements
+
+The potential KPI requirements needed to support the use case include:
+
+[P.R.5.4-001] The 5G system shall support “Remote control part” downloading for split control for robotics with a maximum latency as given in Table 5.4.6.1-1 (corresponding size of “Remote control part” is also listed in the table).
+
+[P.R.5.4-002] The 5G system shall support “Remote control part” downloading for split control for robotics with a user experienced DL data rate as given in Table 5.4.6.1-1 (corresponding size of “Remote control part” is also listed in the table).
+
+[P.R.5.4-003] The 5G system shall support “Remote control part” downloading for split control for robotics with communication service availability not lower than 99.999 %.
+
+**Table 5.4.6.1-1: Data rate and latency requirements for robotic control**
+
+| Control mode | User experienced UL data rate for sensing data uploading | Size of “Remote control part” : maximum | User experienced DL data rate for “Remote control part” downloading | Latency for “Remote control part” downloading: maximum |
+|----------------------|----------------------------------------------------------|-----------------------------------------|---------------------------------------------------------------------|--------------------------------------------------------|
+| Full control at edge | 4.7Mbit/s | 200Bytes | 1.6Mbit/s | 1ms |
+| Split control | 4.7Mbit/s | 40kBytes | 320Mbit/s | 12ms |
+
+## 5.5 Session-specific model transfer split computation operations
+
+### 5.5.1 Description
+
+A UE, to achieve results for the user, employs split computation (The split computation is for offloading computation intensive task between UE and network). Computation intensive tasks (machine learning, complex computation using input data and the model, etc.) can be fully or partially offloaded. This use case considers a particular use – rendering augmented reality in a headset with modest computational resources. The decision how to split the computation task between the UE and other computation resources can depend on the conditions of the communication network and on computational resources available in the UE.
+
+NOTE 1: The decision of how to split computation is itself out of scope of 3GPP and not discussed here.
+
+### 5.5.2 Pre-conditions
+
+Abigail has Augmented Reality glasses, a UE with limited computational power. She leaves a bus and stands at the bus stop, where, behind a large advertisement display, a gNB is installed. Abigail's glasses get access through the access point. She seeks to augment her view of the city with directions and annotations (opening hours, local history, description of businesses, etc.) Augmenting the visual scene of the city in real time is a computationally intensive task, accomplished by a model developed through ML. the model has two candidate split points, each candidate split point has a different workload and communication requirement shown as below. This strategy for splitting computation has been installed in the UE and Application Server so that the split point can be adjusted dynamically based on change of communication performance and/or UE's capabilities. The Application Server can be either in the MNO domain (i.e. a trusted application) or external to the MNO domain (i.e. an authorized third party application.) . This use case does not consider how the splitting strategy is determined, whether this can be done autonomously or what form the strategy has.
+
+**Table 5.5.2-1: Workload and communication requirement for split points**
+
+| | Approximate output UL data rate (Mbit/s) | Computation load in UE |
+|-------------------------|------------------------------------------|------------------------|
+| Candidate split point 1 | 120 | Low |
+| Candidate split point 2 | 24 | High |
+
+The glasses have limited computational capacity, and this capacity varies over time. A means for identifying the current status (AI-ML information) of the UE is available to the network i.e. via application layer. Initially it is determined that the UE has the capability to support either candidate split point 1 or 2.
+
+The network communication resources are enormous, it is determined by the augmented reality service to apply candidate split point 1 so that computation is executed mainly in the network, receiving large quantities of data provided by her glasses and this helps reduce computation in UE. The large quantity of data is transmitted via the QoS flow with guaranteed data rate (GBR) 200 Mbit/s.
+
+### 5.5.3 Service Flows
+
+#### Case-a (split point adjusted based on communication performance):
+
+Abigail walks away from the bus stop and the vicinity of the hot spot.
+
+As Abigail stood a few meters from the gNB hotspot, The insufficient communication resources leads to the serving gNB becoming unable to keep the QoS flow with GBR 200 Mbit/s anymore Thus the policy decision point (which could be anywhere – we leave out what takes the decision and how) determines to downgrade will be executed at the time point-a the GBR from 200 Mbit/s to 30 Mbit/s and immediately notifies UE and Application server of this downgrade. The strategy for splitting computation for the AR application now must be adjusted, i.e. change to candidate split point 2, for which more computation needs to be done locally but the required bit rate for UL transmission is reduced to 24 Mbit/s .
+
+The strategy and constraints for the partition of work is out of scope of this use case. (These could include e.g. partial results could be sent to the UE, which could perform sub-optimally with reduced resources, can model information be
+
+sent in a lossy / compressed form that is still useful, etc.) In any case, one of the crucial inputs to the decision of how to split the work is *the current set of communication resources available*.
+
+The network provides current network resource information concerning the UE to network communication performance such as new QoS parameters (GBR=20Mbit/s), the condition information (time point-a) for update of a new QoS, as well as end to end performance between the UE and the computation resources (e.g. in the Service Hosting Environment). This information is made available (exposed) to the split computation 'policy decision point' (which could be anywhere – in the UE, the edge, the cloud, etc., this is not relevant to the use case.)
+
+#### **Case-b (split point adjusted based on UE's AI-ML information):**
+
+Originally candidate split point-2 is selected when UE's capability can support a high work load.
+
+Abigail's UE's computational information is monitored at the application layer. When the communication resources are sufficient to support Candidate split point 1, if the UE's conditions degraded sufficiently (e.g. due to depleted battery, lack of storage, reduced computation capacity) then this would be a reason to select Candidate split point 1.
+
+Then the split computation decision point then adjusts the split computation strategy:
+
+**For case-a:** to avoid service interruption, the split computation decision point selects the new split point-2 before the time point-a arrives. How this is communicated or 'enforced' is out of scope of this use case and it is not suggested that this would be standardized.
+
+**For case-b:** to guarantee the user experience, the split computation decision point selects the split point-1 as the UE's status is insufficient to support a high work load anymore.
+
+The UE status information is assumed to be collected via application layer.
+
+### **5.5.4 Post-conditions**
+
+Abigail has no awareness of the change of model split point and continues to enjoy acceptable performance as she ventures into the city, even if perhaps it is not as good as when she stood at the bus stop. Note that this use case doesn't conclude as long as Abigail continues to use the service – as the UE to network communication performance can change at any time.
+
+### **5.5.5 Existing features partly or fully covering the use case functionality**
+
+From TS 22.261 v17.1.0, clause 6.6.2:
+
+Based on operator policy, the 5G system shall support an efficient mechanism for selection of a content caching application (e.g. minimize utilization of radio, backhaul resources and/or application resource) for delivery of the cached content to the UE.
+
+NOTE 1: The selection of content caching relies upon knowledge of communication resources (e.g. radio, backhaul, application) for delivery of content to the UE. Thus this requirement satisfies the requirements partly.
+
+From TS 22.261 v17.1.0, clause 6.7.2:
+
+The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service.
+
+The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
+
+NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
+
+The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
+
+From TS 22.261 v17.1.0, clause 6.8:
+
+Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration.
+
+Based on operator policy, the 5G system shall maintain a session when prioritization of that session changes in real time, provided that the new priority is above the threshold for maintaining the session.
+
+From TS 22.261 v17.1.0, clause 6.10.2:
+
+Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
+
+Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party.
+
+Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+[P.R.5.5-001] Based on operator policy, the 5G network shall be able to provide the means to allow an authorized third-party to monitor the resource utilisation of the network service that are associated with the third-party.
+
+[P.R.5.5-002] Based on operator policy, the 5G system shall be able to expose QoS information to an authorized 3rd party. The QoS information can include e.g. UE UL/DL bitrate, latency, reliability per location.
+
+[P.R.5.5-003] The 5G system shall be able to provide the means to predict and expose network condition changes (e.g. bitrate, latency, reliability) to the authorized third party.
+
+# 6 AI/ML model/data distribution and sharing over 5G system
+
+## 6.1 AI/ML model distribution for image recognition
+
+### 6.1.1 Description
+
+Image recognition is an area where a rich set of pre-trained AI/ML models are available. The optimum model depends on the feature of the input image/video, environment and the precision requirement. The model used for vision processing at device needs to be adaptively updated for different vision objects, backgrounds, lighting conditions, purposes (e.g. image recovery vs. classification), and even target compression rates. Although a static model can also work as default in some cases, adapting the model to different working conditions will provide improved recognition accuracy and better user experience.
+
+An example was given in [20] for the motivation of selecting the optimum model for different image recognition tasks and environments. As shown in Figure 6.1.1-1, 4 typical CNN models were evaluated and compared for different image recognition tasks, i.e. MobileNet\_v1\_025 [19], ResNet\_v1\_50 (ResNet [18] with 50 layers), Inception\_v2 [23], and ResNet\_v2\_152 (ResNet with 152 layers). This example shows that the best model depends on the type of input image and the task requirement. For a mobile device which needs to recognize diverse types of images and meet various requirements for different applications, the model needs to be adaptively switched.
+
+
+
+The figure illustrates the trade-off between inference time and model accuracy for different image recognition tasks. It includes three sample images: (a) Image 1 (a rabbit), (b) Image 2 (a cat), and (c) Image 3 (a document). The bar chart (d) shows the inference time in seconds for four CNN models across these three images. The legend indicates that the orange asterisk (\*) represents the 'Best top-1 score model' and the red plus (+) represents the 'Best top-5 score model'.
+
+| Model | Image 1 (s) | Image 2 (s) | Image 3 (s) |
+|------------------|-------------|-------------|-------------|
+| MobileNet_v1_025 | ~0.2 | ~0.2 | ~0.2 |
+| ResNet_v1_50 | ~0.7 | ~0.9 | ~0.8 |
+| Inception_v2 | ~0.7 | ~0.6 | ~0.7 |
+| ResNet_v2_152 | ~1.7 | ~1.9 | ~1.8 |
+
+Figure 6.1.1-1: Example of selecting the optimum model for different image recognition tasks/environments. The figure shows three sample images (a rabbit, a cat, and a document) and a bar chart comparing inference times for four CNN models (MobileNet\_v1\_025, ResNet\_v1\_50, Inception\_v2, ResNet\_v2\_152) across three image tasks. MobileNet\_v1\_025 is the fastest but has lower accuracy, while ResNet\_v2\_152 is the most accurate but slowest.
+
+Figure 6.1.1-1. Example of selecting the optimum model for different image recognition tasks/environments (figure adopted from [20])
+
+In case the selected model has not pre-loaded in the device, the device needs to download it from the network before the image recognition task can start. A model can be reused if it is kept in storage after the previous use. But due to the limited storage resource, the device cannot retain all models for potential use in storage. The data rate for downloading the needed models depends on the size of the model and the required downloading latency.
+
+Along with the increasing performance requirements to AI/ML operations, the size of the models also keeps increasing, although model compression techniques are under improvements. The typical sizes of typical DNN models for image recognition are listed in Table 6.1.1-1. A DNN parameter can be expressed in 32 bits for a higher inference accuracy. The model size and downloading overhead can be compressed if the size of a parameter is reduced to 8 bits, by potentially sacrificing the image recognition accuracy.
+
+The required model downloading latency depends on how fast the model needs to be ready at the device. It is impacted by the extent to which the oncoming application can be predicted. In the use case, we assume the device cannot predict and download the needed model in advance. In this case, the downloading of the AI/ML model needs to be finished in seconds or even in milliseconds. Different from a streamed video which can be played when a small portion is buffered, a DNN model can only be used until the whole model is completely downloaded.
+
+For example, if the downloading latency is 1s, the required DL data rate ranges from 134.4 Mbit/s to 1.92Gbit/s in case of 32-bit parameters, as shown in Table 6.1.1-1. In case of 8-bit parameters, the required DL data rate can be limited to 33.6Mbit/s~1.1Gbit/s.
+
+A model consists of model topology and model weight factors. The topology reflects the structure of a neural network (e.g. neurons of each layer, the connections of neurons between two neighboring layers). The size of the model parameters is shown in Table 6.1.1-1. The size of the configuration file of a model (i.e. the model topology), usually does not exceed 1Mbits. When an application of the UE requests a model, the third-party server sends one model profile which may consist of two parts, i.e. model topology and model weight factors. Because the model topology and model weight factors are from the same server, probably they have the same IP tuple. The transmission error of model topology matters a lot comparing to model weight factors (the UE can hardly run the model if model topology has an error while the weight factors may have a high transmission error tolerance due to model robustness). Therefore, the transmission of data of model topology is more important and requires higher reliability.
+
+**Table 6.1.1-1: Sizes of typical image-recognition models and required DL data rates for downloading in 1s**
+
+| DNN model for image recognition | Number of parameters (Million) | 32 bits per parameter | | 8 bits per parameter | |
+|---------------------------------|--------------------------------|---------------------------|--------------------------------|---------------------------|--------------------------------|
+| | | Size of the model (MByte) | Required DL data rate (Mbit/s) | Size of the model (MByte) | Required DL data rate (Mbit/s) |
+| AlexNet [7] | 60 | 240 | 1920 | 60 | 480 |
+| VGG16 [8] | 138 | 552 | 4416 | 138 | 1104 |
+| ResNet-152 [18] | 60 | 240 | 1920 | 60 | 480 |
+| ResNet-50 [18] | 25 | 100 | 800 | 25 | 200 |
+| GoogleNet [9] | 6.8 | 27.2 | 217.6 | 6.8 | 54.4 |
+| Inception-V3 [23] | 23 | 92 | 736 | 23 | 184 |
+| 1.0 MobileNet-224 [19] | 4.2 | 16.8 | 134.4 | 4.2 | 33.6 |
+
+### 6.1.2 Pre-conditions
+
+The UE runs an application providing the capability of AI/ML model inference for image recognition.
+
+An AI/ML server manages the AI/ML model pool, and is capable to download the requested model to the application providing AI/ML based image recognition.
+
+The 5G system has the ability to provide 5G network related information to the AI/ML server.
+
+### 6.1.3 Service Flows
+
+1. The AI/ML based image recognition application is requested by the user to start recognizing the image/video shot by the UE.
+2. The AI/ML model is downloaded from the model server to the AI/ML based image recognition application via 5G network.
+
+3. The AI/ML based image recognition application employs the AI/ML model for inference until the image recognition task is finished.
+4. Redo Step 2) to 3) for AI/ML model re-selection and re-downloading if needed to adapt to the changing conditions.
+
+### 6.1.4 Post-conditions
+
+The objects in the input images or videos are recognized by the AI/ML based image recognition application and the inference accuracy and latency need to be guaranteed.
+
+The image recognition task can be completed under the available computation and energy resource of the UE.
+
+### 6.1.5 Existing features partly or fully covering the use case functionality
+
+This use case mainly requires high data rate together with low latency. The high data rate requirements to 5G system are listed in Clause 7.1 and 7.6 of TS22.261 [4]. As in Table 7.1-1 of [4], 300Mbps DL experienced data rate and 50Mbps UL experienced data rate are required in dense urban scenario, and 1Gbps DL experienced data rate and 500Mbps UL experienced data rate are required in indoor hotspot scenario. As in Table 7.6.1-1 of [4], cloud/edge/split rendering-related data transmission requires up to 0.1Gbps data rate with [5-10]ms latency countrywide.
+
+### 6.1.6 Potential New Requirements needed to support the use case
+
+Considering the time taken by the device to finish the image recognition task, a small portion of the recognition latency budget can be used to download the model. For one-shot object recognition at smartphone and photo enhancements at smartphone, a pre-installed sub-optimal model can be temporarily employed while downloading the optimal model. The optimal model in need should be downloaded on level of 1s, and then replaces the pre-installed model. If 8-bit parameters are used for describing the DNN, the required DL data rate ranges from 33.6Mbit/s to 1.1Gbit/s. For video recognition, the target can be updating the model in one frame duration (so to adopt the updated model for the next frame). But for an application with an always-on camera, the device can predict the needed model and start the downloading in-advance. Downloading the model within 1s is acceptable. Similarly, for other applications with an always-on camera, i.e. person identification in security surveillance system, AR display/gaming, remote driving, remote-controlled robotics, the required DL data rate ranges from 33.6Mbit/s to 1.1Gbit/s. It should be noted that the size of the model may be further reduced if more advanced model compression techniques can be adopted.
+
+#### 6.1.6.1 Potential KPI Requirements
+
+The potential KPI requirements needed to support the use case include:
+
+[P.R.6.1-001] The 5G system shall support AI/ML model downloading for image recognition with a maximum latency as given in Table 6.1.6.1-1.
+
+[P.R.6.1-002] The 5G system shall support AI/ML model downloading for image recognition with a user experienced DL data rate as given in Table 6.1.6.1-1.
+
+[P.R.6.1-003] The 5G system shall support AI/ML model downloading for image recognition with communication service availability not lower than 99.999 %.
+
+[P.R.6.1-004] The 5G system shall support AI/ML model downloading with a reliability for the transmission of data of model topology not lower than 99.999% and a reliability for the transmission of data of model weight factors not lower than 99.9%.
+
+**Table 6.1.6.1-1: Image recognition model downloading latency analysis for example applications (8-bit parameters for the DNN)**
+
+| User application | Latency: maximum | | User experienced DL data rate for model downloading |
+|-------------------------------------------------------|---------------------------|---------------------------|-----------------------------------------------------|
+| | Image recognition latency | Model downloading latency | |
+| One-shot object recognition at smartphone | ~1s | 1s (Note 1) | 33.6Mbit/s~1.1Gbit/s |
+| Person identification in security surveillance system | ~1s | 1s (Note 2) | 33.6Mbit/s~1.1Gbit/s |
+
+| | | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|----------------------|
+| Photo enhancements at smartphone | ~1s | 1s (Note 1) | 33.6Mbit/s~1.1Gbit/s |
+| Video recognition | 33ms@30FPS | 1s (Note 2) | 33.6Mbit/s~1.1Gbit/s |
+| AR display/gaming | <5ms (Note 3) | 1s (Note 2) | 33.6Mbit/s~1.1Gbit/s |
+| Remote driving | <5ms (Note 4) | 1s (Note 2) | 33.6Mbit/s~1.1Gbit/s |
+| Remote-controlled robotics | <5ms (Note 5) | 1s (Note 2) | 33.6Mbit/s~1.1Gbit/s |
+| NOTE 1: A pre-installed sub-optimal model can be temporarily employed while downloading the optimal model. The optimal model should be downloaded in the order of 1s. | | | |
+| NOTE 2: For applications with an always-on camera, the device can predict the needed model and start the downloading in-advance. Downloading the model within 1s is acceptable. | | | |
+| NOTE 3: According to [4][5], the VR motion-to-photon latency is in the range of 7-15ms. It can be assumed that the AR display or gaming requires a similar end-to-end latency. Considering the time taken by the AR rendering (e.g. 3D rendering of the virtual objects, rendering augmentation in overlay), the background video recognition should be finished within 5ms. | | | |
+| NOTE 4: According to [46] the one-way latency required for remote driving is 5ms. The round-trip latency is assumed to be 10ms. Considering the time taken by the vision-based driving inference at server, the latency budget for traffic object recognition can be estimated to be 5ms. | | | |
+| NOTE 5: According to [5] the end-to-end latency required for video-operated remote-controlled robotics is 10~100ms. Considering the time taken by the robot controlling inference at server, the robot vision recognition needs to be finished within 5ms. | | | |
+
+## 6.2 Real time media editing with on-board AI inference
+
+### 6.2.1 Description
+
+Smartphone is the #1 device that people carry and use everywhere for audio and video recording. It also becomes the first device to exchange media content with friends and family, to publish on social media. High end smartphones embed more and more powerful CPU and GPU and even dedicated AI hardware accelerators. As camera and picture/video quality become a differentiator among high end smartphones, AI/ML models to enhance photo shoots locally emerge on these high-end devices. AI accelerators are expected to enable the execution of complex AI/ML models directly on end-users connected devices; not only photo enhancements but high-quality audio and video content analysis and enhancement are expected to be executed locally on smartphones. Smartphones will consequently become a device to edit media content prior to sharing over the network. With the advent of 5G, new services relying on on-demand downloads of large AI/ML models to be executed in (near) real time on end user device will emerge; depending on the service, the environment, the user's preference, the device characteristics, etc., these DNN models will need to be adapted or updated under strict latency constraints which prevent all of them to be stored locally in advance.
+
+Media content analysis combines tasks as object detection, segmentation, face recognition, people counting, human activity tracking. In table 6.2.1-1, examples of commonly used DNN models for object detection (with their respective sizes) are listed.
+
+**Table 6.2.1-1: Sizes of typical object detection models**
+
+| Model for object detection | Number of parameters (Million) | Size of the model (MByte) 32 bits parameters | Size of the model (MByte) 8 bit parameters |
+|----------------------------|--------------------------------|----------------------------------------------|--------------------------------------------|
+| MobileNet | 3.2 | 12.8 | 3.2 |
+| DarkNet | 20 | 80 | 20 |
+| SE ResNet | 26 | 104 | 26 |
+| Inception v4 | 41 | 164 | 41 |
+| YOLONet | 64 | 256 | 64 |
+| VGGNet | 134 | 536 | 134 |
+
+Media content edition combines tasks as audio and video quality improvement, language translation, face anonymisation. In tables 6.2.1-2 and 6.2.1-3, examples of commonly used DNN models for image super-resolution and for video super-resolution are listed.
+
+**Table 6.2.1-2: Sizes of typical image super-resolution models**
+
+| Model for image super-resolution | Number of parameters (Million) | Size of the model (MByte) 32 bits parameters | Size of the model (MByte) 8 bits parameters |
+|----------------------------------|--------------------------------|----------------------------------------------|---------------------------------------------|
+| RCAN | 15.44 | 61.78 | 15.44 |
+| SAN | 15.71 | 62.82 | 15.71 |
+
+| | | | |
+|----------|-------|--------|-------|
+| RDN | 22.12 | 88.48 | 22.12 |
+| EDSR | 40.73 | 162.92 | 40.73 |
+| OISR-RK3 | 41.91 | 167.64 | 41.91 |
+
+**Table 6.2.1-3: Sizes of typical video super-resolution models**
+
+| Model for video super-resolution | Number of parameters (Million) | Size of the model (MByte) 32 bits parameters | Size of the model (MByte) 8 bits parameters |
+|----------------------------------|--------------------------------|----------------------------------------------|---------------------------------------------|
+| RBP4N/4-PF | 12.7 | 50.8 | 12.7 |
+| RBP4N/6-PF | 12.7 | 50.8 | 12.7 |
+| VSR-DUF | 6.8 | 27.2 | 6.8 |
+| DRDVSR | 0.7 | 2.8 | 0.7 |
+
+Two settings are considered for the use case:
+
+- a) Independent user: a person takes a video or starts a video call on its UE in a noisy environment, with difficult lighting conditions, and automatic tagging of scene and objects are embedded in the video.
+- b) Crowd: During a large event, like a live concert, several thousand people use their UEs to film or photograph the musician band at the same time, and request additional information on the concert like band discography, lyrics, artist facial recognition, instrument/equipment brand. In this context, UEs request the downloads of DNN models to improve the capture and recording of the concert, and to provide information requested by people attending the concert. Several DNN models can be requested by each UE to e.g. execute the following tasks: image shooting and video optimization, artist face recognition, musical instrument identification, audio improvement and lyrics generation. Given the heterogeneous fleet of UEs, thousands of DNN models required by the application/service – can be requested for download. These DNN models are adapted or updated to the UEs operating system type and version, hardware characteristics and environment.
+
+### 6.2.2 Pre-conditions
+
+The setting for this use case is as follows. Alice is attending a crowded live concert. She is eager to get movie clips and pictures as a great souvenir of the concert, but she is worried about difficult conditions to get this great souvenir as the conditions for light and sound are very variable, with limited light for the spectators and too much light on the scene. The audio stereo is variable and not well-balanced dependent on where she is among the audience and has a very noisy background.
+
+Alice would like to store good quality movie clips and pictures on her private account on the internet for the future, and also post photos and videos tagged with artist name and other relevant information during the concert. As Alice is also an amateur musician, she also wants to get detailed real-time information about the structure of the song, the lyrics and the instruments.
+
+The pre-conditions are:
+
+- a. Alice is attending a crowded live concert.
+- b. Her UE is registered to the 5G network.
+- c. Applications of Alice's smartphone can rely on fine-tuned machine learning models that are available via the network that covers the concert hall. These models are:
+ - 1) An ML model improving photo capture for this concert hall (a model specially fine-tuned for this concert place).
+ - 2) An ML model improving audio capture for this concert hall (a model specially fine-tuned for this concert place).
+ - 3) An ML model specialized in the discography and the lyrics of the band.
+ - 4) An ML model specialized in the artists face recognition.
+ - 5) An ML model specialized in music instrument identification.
+
+NOTE: The listed models above are examples for this use-case and is not an exhaustive list.
+
+### 6.2.3 Service Flows
+
+- 1) Shortly after the start of the concert, Alice, as most of the fans, launches the camera application on her mobile phone to film the scene and to get additional information about the band, the individual artists or the songs or instruments.
+- 2) She points her device's camera towards the scene.
+- 3) The environment is very dark with strong light spots. To be fully functional and to render the best user experience, the camera application downloads ad-hoc ML models.
+- 4) The proposed ML models are very performant in this environment but also very heavy in size.
+- 5) The ML models can be used for the whole capture especially if environment remains stable. If the environment changes substantially, or better ML models become available, ML models can be progressively updated accordingly with respect of some operating rules (like a maximum number of ML update per second). In all cases, the camera application continues working seamlessly.
+- 6) The audio and video streams are captured, improved in quality, processed to extract and display additional information, and either stored in real-time on the mobile phone itself or provided as a live stream.
+
+### 6.2.4 Post-conditions
+
+Alice can see that even in harsh light conditions and with the noisy background the photos and videos are great, additional information is provided and all is correctly tagged as requested.
+
+The post-conditions are:
+
+- 1) Photos and videos are either stored on the mobile phone in the improved high quality, ready to be uploaded and shared on social media, or directly shared on social media.
+- 2) Audio recording is high quality with ambient noise reduction, improved stereo balance.
+- 3) Additional information about band, song/lyrics, instruments, etc. are displayed on the mobile phone and stored in media recordings' metadata.
+- 4) Alice can visualize additional information and upload the photos and videos on her social network(s) with the associated tags and information provided by the models, and also store the above on her personal media server.
+
+### 6.2.5 Existing features partly or fully covering the use case functionality
+
+The performance requirements for high data rate and traffic density scenarios are found in TS 22.261 [4] clause 7.1. The scenario Broadband access in a crowd is relevant for the use case of very dense crowds, for example at stadiums or concerts. In addition to a very high connection density, the users can share their experience, i.e. what they see and hear. This can put a higher requirement on the uplink than the downlink.
+
+This new use case has some requirements on the downlink not covered by the existing requirements, see table 6.2.5-1.
+
+**Table 6.2.5-1. Excerpt from TS 22.261 [4] Table 7.1-1**
+
+| | Scenario | Experienced data rate (DL) | Experienced data rate (UL) | Area traffic capacity (DL) | Area traffic capacity (UL) | Overall user density | Activity factor | UE speed | Coverage |
+|---|-----------------------------|----------------------------|----------------------------|-------------------------------|------------------------------|---------------------------|-----------------|-------------|---------------|
+| 4 | Broadband access in a crowd | 25 Mbit/s | 50 Mbit/s | [3,75] Tbit/s/km 2 | [7,5] Tbit/s/km 2 | [500 000]/km 2 | 30% | Pedestrians | Confined area |
+
+### 6.2.6 Potential New Requirements needed to support the use case
+
+#### 6.2.6.1 Introduction
+
+Potential new requirements needed to support the use case result of the following parameters:
+
+- a) AI/ML model size.
+- b) Accuracy of the model.
+- c) latency constraint of the application or service.
+- d) number of concurrent downloads, i.e. number of UEs requesting AI/ML model downloads within same time window.
+
+The number of concurrent downloads further depends on the density of UE in the covered area and the covered area size.
+
+The tables 6.2.6.1-1, 6.2.6.1-2 and 6.2.6.1-3 contain KPI for different aspects of the real-time media editing use case.
+
+**Table 6.2.6.1-1. Typical sizes of AI/ML models for the UC**
+
+| AI/ML Model | Number of parameters (Million) | Size of the AI/ML model (MByte) | Comments |
+|--------------|--------------------------------|---------------------------------|-------------------|
+| MobileNet | 3.2 | 3.2 | 8-bit parameters |
+| MobileNet | 3.2 | 12.8 | 32-bit parameters |
+| RCAN | 15.44 | 15.44 | 8-bit parameters |
+| DarkNet | 20 | 20 | 8-bit parameters |
+| Inception v4 | 41 | 41 | 8-bit parameters |
+| RCAN | 15.44 | 61.78 | 32-bit parameters |
+| YOLONet | 64 | 64 | 8-bit parameters |
+| DarkNet | 20 | 80 | 32-bit parameters |
+| VGGNet | 134 | 134 | 8-bit parameters |
+| Inception v4 | 41 | 164 | 32-bit parameters |
+| YOLONet | 64 | 256 | 32-bit parameters |
+| VGGNet | 134 | 536 | 32-bit parameters |
+
+From table 6.2.6.1-1, AI/ML models currently available to elaborate the use case have sizes that vary from 3.2 MB to 536 MB.
+
+As indicated in the use case in clause 6.1, it can be noted that the size of AI/ML models can be reduced prior to transmission with dedicated model compression techniques. On the contrary, AI/ML models with more neural network layers and more complex architectures arise to solve more complex tasks and to improve accuracy. This trend is expected to continue in the coming years. Typical model sizes in the range of 3 MB to 500 MB appear to be a reasonable compromise to consider for this use case.
+
+In the following, two categories are considered for AI/ML model sizes:
+
+- a) AI/ML model sizes below 64 MB, which can be associated to models optimized for fast transmission,
+- b) AI/ML model sizes below 500 MB, which can be associated to models optimized for higher accuracy.
+
+Maximum latency in function of application or service:
+
+- a) Videocall service: end-to-end latency below 200 ms,
+- b) Video recording, video streaming, and object recognition applications: latency below 1 s.
+
+User experienced DL data rate results from above AI/ML models' sizes and maximum latency values are summarized in the table 6.2.6.1-2.
+
+**Table 6.2.6.1-2. UC AI/ML model download – single UE – KPIs**
+
+| UC model download | AI/ML model size | Latency: maximum | User experienced DL data rate |
+|--------------------------|------------------|------------------|-------------------------------|
+| Single Model / Single UE | [3 MB – 64 MB] | <1 s | [24 Mb/s ~ 512 Mb/s] |
+| Single Model / Single UE | [3 MB – 64 MB] | <200 ms | [120 Mb/s ~ 2.56 Gb/s] |
+| Single Model / Single UE | [64 MB – 500 MB] | <1 s | [512 Mb/s ~ 4 Gb/s] |
+| Single Model / Single UE | [64 MB – 500 MB] | <200 ms | [2.56 Gb/s ~ 20 Gb/s] |
+
+As indicated above, the number of concurrent downloads is a third parameter to determine potential new requirements. This corresponds to the maximum number of UEs requesting a AI/ML model download in a same time window and same covered area/cell.
+
+The case of a concert hall is an illustration of the scenario, “Broadband access in a crowd” from TS 22.261 [4]. This scenario assumes an overall user density of 500 000 UE / km2 (i.e. 0.5 UE / m2) and an activity factor of 30 %.
+
+In the concert hall case, it is also assumed that only a part of the UEs intends to request AI/ML model downloads. Moreover, only a subpart will request AI/ML model download during the same time window in the same cell. The activity factor is finally estimated to 1 % (i.e. % of UE requesting an AI/ML model download within same time window).
+
+Typical number of UEs in a concert hall varies from ~1000 seats to ~ 5000 seats.
+
+Based on these figures and UE activity assumption, the number of concurrent downloads is estimated as given in table 6.2.6.1-3.
+
+**Table 6.2.6.1-3. Estimated number of concurrent downloads**
+
+| Number of UEs | Estimated area (density of 0.5 UE / m 2 ) | Activity Factor | Number of concurrent downloads in the same cell |
+|---------------|------------------------------------------------------|-----------------|-------------------------------------------------|
+| 1000 | 2000 m 2 | 1 % | 10 |
+| 5000 | 10000 m 2 | 1 % | 50 |
+
+From table 6.2.6.1-2 and table 6.2.6.1-3, requirements on the covered area are estimated as follows:
+
+**Table 6.2.6.1-4. Estimated covered area DL data rate requirements**
+
+| Number of UEs | Activity Factor | Number of concurrent downloads | AI/ML model size | Latency: maximum | User experienced DL data rate | Aggregated user experience DL data rate for covered area |
+|---------------|-----------------|--------------------------------|------------------|------------------|-------------------------------|----------------------------------------------------------|
+| 1000 | 1 % | 10 | [3 MB – 64 MB] | <1 s | [24 Mb/s ~ 512 Mb/s] | [240 Mb/s ~ 5.12 Gb/s] |
+| | | | [3 MB – 64 MB] | <200 ms | [120 Mb/s ~ 2.56 Gb/s] | [1.2 Gb/s ~ 25.6 Gb/s] |
+| | | | [64 MB – 500 MB] | <1 s | [512 Mb/s ~ 4 Gb/s] | [5.12 Gb/s ~ 40 Gb/s] |
+| 5000 | 1 % | 50 | [3 MB – 64 MB] | <1 s | [24 Mb/s ~ 512 Mb/s] | [1.2 Gb/s ~ 25.6 Gb/s] |
+| | | | [3 MB – 64 MB] | <200 ms | [120 Mb/s ~ 2.56 Gb/s] | [6 Gb/s ~ 128 Gb/s] |
+| | | | [64 MB – 500 MB] | <1 s | [512 Mb/s ~ 4 Gb/s] | [25.6 Gb/s ~ 200 Gb/s] |
+
+Another approach to estimate the number of concurrent downloads is to estimate the number of different AI/ML models requested by UEs instead of the number of UEs requesting AI/ML models. The AI/ML models can then be broadcast/multicast to multiple UEs. The number of different AI/ML models depends on the accuracy expectations of the AI/ML models, the execution environments and the hardware characteristics of end devices. When the number of UE requesting AI/ML models is very high, the number of different AI/ML models can remain smaller. This approach is well suited for very large crowd.
+
+The number of concurrent downloads when transmitted in broadcast/multicast to many UEs can be estimated between 1 (i.e. all UEs request the same AI/ML model) and 50 (i.e. all UEs request different AI/ML models).
+
+#### 6.2.6.2 Potential KPI Requirements
+
+##### Independent user:
+
+[P.R.6.2-I-001] The 5G system shall support the download of AI/ML models with a latency below 1s and a user experienced data rate of 512 Mb/s.
+
+NOTE 1: This requirement concerns AI/ML models having a size below 64 MB.
+
+[P.R.6.2-I-002] The 5G system shall support the download of AI/ML models with a latency below 1 s and a user experienced data rate of 4 Gb/s.
+
+NOTE 2: This requirement concerns AI/ML models having a size below 500 MB.
+
+##### Crowd:
+
+[P.R.6.2-C-001] The 5G system shall support the parallel download of up to 50 AI/ML models with a latency below 1 s.
+
+NOTE 3: This requirement concerns AI/ML models having a size below 64 MB.
+
+[P.R.6.2-C-002] The 5G system should support the functionality to broadcast/multicast a same AI/ML model to many UEs with a latency below 1 s.
+
+NOTE 4: This requirement concerns AI/ML models having a size below 64 MB.
+
+## 6.3 AI/ML model distribution for speech recognition
+
+### 6.3.1 Description
+
+AI/ML-based speech processing has been widely used in applications on mobile devices (e.g. smartphone, personal assistant, language translator), including automatic speech recognition (ASR), voice translation, speech synthesis. Speech recognition for dictation, search, and voice commands has become a standard feature on smartphones and wearable devices.
+
+Service requirements to ASR have been addressed in [29]. Traditional ASR systems are based on hidden Markov model (HMM) and Gaussian mixture model (GMM). However, the HMM-GMM systems suffer a relatively high WER (Word Error Rate) with presence of environmental noise. Although some enhancements were developed including “feature enhancement” (attempts to remove the corrupting noise from the observations prior to recognition) and “model adaptation” (leaves the observations unchanged and instead updates the model parameters of the recognizer to be more representative of the observed speech), the traditional models can hardly fulfil the requirements of commercial applications. Acoustic models based on deep neural networks (DNN) have remarkable noise robustness [25-26], and have been widely used in the ASR applications in mobile devices.
+
+Nowadays, most of ASR applications on smartphones are operating in cloud servers. The end device uploads the speech to the cloud server, and then downloads the decoded results back to the device. However, cloud-based speech recognition potentially introduces a higher latency (not only due to the 4G/5G network latency, but also the internet latency), and the reliability network connection and privacy issue need to be considered.
+
+An embedded speech recognition system running on a mobile device is more reliable and can have lower latency. Currently, some ASR apps would switch from cloud-based model inference to offline model inference when uplink coverage of the mobile user turns weak, e.g. when entering a basement or an elevator. However, the ASR models for cloud servers are too complex for computation and storage resources on mobile devices. The size of a ML-based ASR model running on cloud server has rapidly increased in the recent year, from ~1GByte to ~10GByte, which cannot be run on a mobile device. Due to the restriction, only the simple ASR applications, e.g. wakeword detection, can be implemented on smart phones. Realizing more complicated ASR applications, e.g. large vocabulary continuous speech recognition (LVCSR) is still a challenging area for an offline speech recognizer.
+
+In 2019, a state-of-the-art offline LVCSR recognizer for Android mobile devices was announced. The streaming end-to-end recognizer is based on the recurrent neural network transducer (RNN-T) model [27-28]. It was stated that, by employing all kinds of improvements and optimizations, the memory footprint can be dramatically reduced and the computation can be speed up. The model can be compressed to 80MB. Meanwhile the ASR model is compressed to fit the use at mobile device, the robustness to the various types of background noises has to been sacrificed. When the noise environment changes, the model needs to be re-selected, and in case the model is not kept in the device, the model needs to be downloaded from the cloud/edge server of the AI/ML model owner via 5G network.
+
+### 6.3.2 Pre-conditions
+
+The UE runs an application providing the capability of AI/ML model inference for speech recognition.
+
+An AI/ML server manages the AI/ML model pool, and is capable to download the requested model to the application providing AI/ML based speech recognition.
+
+The 5G system has the ability to provide 5G network related information to the AI/ML server.
+
+### 6.3.3 Service Flows
+
+1. The AI/ML based speech recognition application is requested by the user to start recognizing the speech recorded.
+2. The AI/ML model is downloaded from the model server to the AI/ML based speech recognition application via 5G network.
+3. The AI/ML based speech recognition application employs the AI/ML model for inference until the speech recognition task is finished.
+4. Redo Step 2) to 3) for AI/ML model re-selection and re-downloading if needed to adapt to the changing conditions.
+
+### 6.3.4 Post-conditions
+
+The content in the input speech is recognized by the AI/ML based speech recognition application and the inference accuracy and latency need to be guaranteed.
+
+The speech recognition task can be completed under the available computation and energy resource of the UE.
+
+### 6.3.5 Existing features partly or fully covering the use case functionality
+
+This use case mainly requires high data rate together with low latency. The high data rate requirements to 5G system are listed in Clause 7.1 and 7.6 of TS22.261 [4]. As in Table 7.1-1 of [4], 300Mbps DL experienced data rate and 50Mbps UL experienced data rate are required in dense urban scenario, and 1Gbps DL experienced data rate and 500Mbps UL experienced data rate are required in indoor hotspot scenario. As in Table 7.6.1-1 of [4], cloud/edge/split rendering-related data transmission requires up to 0.1Gbps data rate with [5-10]ms latency countrywide.
+
+### 6.3.6 Potential New Requirements needed to support the use case
+
+An ASR model can only be used until the whole model is completely downloaded. And device needs to adopt the noise-robust ASR model which adapts to the changing noise environment. In general, the device's microphone is switched on only when the speech recognition application is triggered. The device needs to identify the noise environment and download the corresponding ASR model in a low latency (level of 1s). The sizes of some typical ASR models are listed [27][47] in Table 6.3.6-1, which are used to derive the required data rate.
+
+#### 6.3.6.1 Potential KPI Requirements
+
+The potential KPI requirements needed to support the use case include:
+
+[P.R.6.3-001] The 5G system shall support AI/ML model downloading for speech recognition with a latency not higher than 1s.
+
+[P.R.6.3-002] The 5G system shall support AI/ML model downloading for speech recognition with a user experienced DL data rate as given in Table 6.3.6-1.
+
+[P.R.6.3-003] The 5G system shall support AI/ML model downloading for speech recognition with communication service availability not lower than 99.999 %.
+
+**Table 6.3.6-1: Sizes of typical speech-recognition models and user experienced DL data rates for downloading in 1s (8 bits per parameter)**
+
+| DNN model for speech recognition | Number of parameters (Million) | Size of the model (MByte) | User experienced DL data rate (Mbit/s) |
+|----------------------------------|--------------------------------|---------------------------|----------------------------------------|
+| RNN-CTC [47] | 26.5 | 26.5 | 212 |
+| ResCNN-LAS [47] | 6.6 | 6.6 | 52.8 |
+| QuartzNet-15×5 [47] | 19 | 19 | 152 |
+| Gboard speech recognizer | N.A. | 80 | 640 |
+
+| | | | |
+|------|--|--|--|
+| [27] | | | |
+|------|--|--|--|
+
+## 6.4 AI model management as a Service
+
+### 6.4.1 Description
+
+The AI/ML models can be classified and generated from different perspectives, such as services, users, time, locations, etc. So there can be a large number of AI/ML models (incl. data for structure and weight factors, gradient) used for inference and training. Due to the limitation of storage, UE cannot always preload all AI/ML models for different works. It can be a new commercial opportunity that operators provide services to help manage and distribute the AI/ML models so that UE can acquire a proper model immediately.
+
+In the future, it is expected that 3rd party companies will make use of AI models to support different kinds of services such as panorama tourist guide using Augmented Reality (AR) in a resort. However, most of 3rd party does not have the resource (server) in distributed places. Considering the large size of AI models, strict downloading time (illustrated in use case 6.1, 6.2, 6.3) and limited UE storage, it is appropriate for 3rd party companies to authorize professional companies to manage their AI models rather than doing the same thing locally by themselves.
+
+Since operator cloud resource has advantage to manage different AI/ML models centrally (e.g. cloud server) and locally (e.g. MEC server), such services can be exposed to 3rd party users as well. Specifically,
+
+- The operator has its own need to maintain a AI/ML model pool for its own business like network optimization;
+- The 3rd party would like to use some common AI/ML models already stored in operator's cloud;
+- Due to resource limitation of 3rd party, they would like to lease operator's cloud resource to manage their AI models.
+
+Therefore, as shown in Fig.6.4.1-1, The AI model management includes:
+
+- Let 3rd party invoke capabilities exposed by 5GS to upload/download/update/delete/store/monitor AI models.
+- Transmitting AI models to user efficiently per situation (e.g. entering into a certain area)
+- As the 5GS may collect communication data, user experience, etc., it may perform a data analytics for user experience, which can generate analyzing results to help operator's cloud train and improve AI models for the 3rd party.
+
+
+
+```
+
+graph LR
+ UE[UE] <--> |AI/ML model downloading| OC((Operator Cloud
+(e.g. Edge server)))
+ OC <--> RP[3rd Party]
+
+```
+
+Diagram illustrating Operator cloud for model management. A stack of boxes labeled 'UE' is on the left. A double-headed arrow labeled 'AI/ML model downloading' connects the UE to a cloud icon labeled 'Operator Cloud (e.g. Edge server)'. Another double-headed arrow connects the Operator Cloud to a box labeled '3rd Party' on the right.
+
+Figure 6.4.1-1: Operator cloud for model management
+
+### 6.4.2 Pre-conditions
+
+The operator cloud (e.g. Edge server) stores a variety of AI/ML models according to operator's or 3rd party's requirement.
+
+The operator cloud (e.g. Edge server) is capable to distribute a model stored in the operator cloud to devices.
+
+### 6.4.3 Service Flows
+
+1. Company A provides panorama tourist guide using Augmented Reality (AR) technology. They provide guide services in a commercial area and a tourist resort. UE needs to download Model A and B (both are 32 bits VGGnet, 536MByte) respectively;
+2. To reach the SLA, company A indicates to the operator that UE requires model A in area A and model B in area B.
+3. When UE moves to one place, The local Edge server trigger to establish a QoS acceleration and UE downloads the corresponding Model (A or B) stored in the local Edge server timely so that user can enjoy the continuous AR world without obvious interruption when model changes.
+
+### 6.4.4 Post-conditions
+
+UE uses the Model for panorama tourist guide.
+
+### 6.4.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 6.4.6 Potential New Requirements needed to support the use case
+
+[P.R.6.4-001] Subject to user consent, operator policies and the regional or national regulatory requirements, the 5G system shall be able to provide the capability to expose information (e.g. measured data rate, delay, network analytics results) to an authorized third-party application to support the training and monitoring of the AI/ML models.
+
+[P.R.6.4-002] The 5G system shall be able to support an authorized third-party application to distribute an AI/ML model ranging from 3.2~536MB to an third-party application running on the device in less than 1 second with a user density of up to 5000~10000/km2 in an urban area.
+
+## 6.5 AI/ML based Automotive Networked Systems
+
+### 6.5.1 Description
+
+This use-case is illustrative for a specific example but is readily extensible for more advanced scenarios involving disaster scenarios, rescue operations or even autonomous vehicle operations. The focus of this scenario is on machine-to-machine AI/ML transfer learning and inference systems that are networked together using 5G networks to provide smart automotive applications and services.
+
+The scenario assumes that there exist multiple AI/ML systems available, in a high-reliability, low-latency, high-bandwidth system optimized for machine-to-machine interaction. The proposed AI/ML systems may continuously exchange and share AI-ML model layers in a distributed and or federated network as determined by the system in response to a change of events, conditions or emergency situations, to improve some or all of the ML system prediction accuracy. These systems may optimize the AI/ML inference latency by executing different layers on various AI/ML networked systems.
+
+There are two main types of ML models and model processing considered in this use-case:
+
+1. Large ML models updates using non-real time training – These ML models are trained and optimized with millions or billions of parameters using extensive computing resources to achieve the highest accuracy possible based on specific sets of input training data. This training is performed over a long period of time and the resulting fully-trained ML model is the baseline model installed at initial production for the devices in the use-cases described below. These fully trained models may be updated with externally provided AI-ML model data and may also improve themselves based on external sensor data.
+2. Partial transfer and exchange of AI-ML model data – This use case describes different applications where different types of ML systems are networked to exchange parts of AI-ML model data to improve prediction accuracy. In some systems, local ML models can continuously improve their baseline model using data gathered from the existing environment and other sensor input. These systems upload improved model data
+
+at relatively slow rates to a larger cloud-based network where further processing takes place to further refine the full ML model. The specific method used for continuous improvement is outside the scope of this use case.
+
+Different example scenarios are described below.
+
+#### AI/ML Systems Emergency Response to Disabled Vehicle
+
+Figure 6.5.1-1 illustrates a vehicle that has broken down hidden by a blind curve in the road. This breakdown is considered high-severity for the purposes of illustrating this use-case.
+
+
+
+A white car with its trunk open is parked on the shoulder of a road. The road curves to the right, and the car is positioned such that it is hidden from view by a blind curve. In the background, there is a modern building with a grid-like window pattern and some greenery. The sky is clear and blue.
+
+A white car with its trunk open, broken down on a road that curves to the right, hidden by a blind curve.
+
+**Figure 6.5.1-1: Dangerous vehicle break-down hidden by a blind curve**
+
+On-board vehicle sensors detect the following: mechanical failure, speed reduction, GPS coordinates and a variety of technical parameters are used by on-board ML inferencing systems to immediately diagnose the failure and notify surrounding networks of the severity of the failure.
+
+Different non-real time AI models can use the gathered failure training data to refine prediction and prevention models updates.
+
+#### Traffic Surveillance Camera and MEC Metro Traffic Safety System
+
+Surveillance cameras use ML models to analyze image sensor data to detect and categorize the type of accident using ML inference with continuous AI-ML model improvement. This processed accident information is uploaded along with the model updates to the local near-edge MEC for AI/ML system model prediction and algorithm processing to suggest the immediate next course of action. These AI/ML systems suggest an automated warning broadcast. The automated AI/ML systems relying on trained ML models to predict the position of the vehicle is especially dangerous due to the hidden blind curve and informs local Emergency Response Unit dispatch to send help to set up a traffic bypass earlier on the road. The local near-edge MEC models are capable of continuous model improvement and return this model data back to the surveillance camera for further inference accuracy improvement.
+
+The uploading of data, possibly pre-processed by the local AI/ML model, from the surveillance camera to the MEC may happen with low-latency depending on the severity of the accident while returned data to update the local model may happen on a much slower timeframe.
+
+#### Approaching Intelligent Vehicle Reaction
+
+
+
+A black car is shown from a rear perspective, driving on a multi-lane highway. The car has "Autonomous Driving" and "Qualcomm" text on its rear license plate area. The road is straight, and there is a concrete barrier on the right side. In the background, there are hills and a clear sky.
+
+A black car with 'Autonomous Driving' and 'Qualcomm' text on its rear, approaching a vehicle on a highway.
+
+**Figure 6.5.1-2: Approaching Autonomous Vehicle**
+
+Figure 6.5.1-2 illustrates a vehicle rapidly approaching the car illustrated in Figure 1. The vehicle's sensors are unable to detect the hazard and must rely upon other AI/ML systems for a warning.
+
+An approaching autonomous vehicle receives multiple warning notifications and AI/ML systems in the vehicle use trained models predict and suggest appropriate automatic manoeuvres to move the vehicle to the far lane to avoid any danger. Sharing of data with other systems allows for constantly refining their models; this sharing of data does not have non-real requirements.
+
+### 6.5.2 Pre-conditions
+
+The scenarios described above assume the following pre-conditions:
+
+- All existing AI/ML systems have existing pre-trained default AI-ML models that will perform predictions at a baseline accuracy and are capable of updating/re-fining the AI-ML models for continuously improving accuracy for the specific purpose.
+
+**Table 6.5.2-1: Use-Case Pre-Conditions**
+
+| Broken Autonomous Vehicle | Approaching Autonomous Vehicle | Road Surveillance Camera | Smart City Metro Traffic Control | Smart City Emergency Services Network |
+|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------------|------------------------------------------------------------|
+| AI/ML Vehicle model has detected the fault. All comm. systems are available & active. | AI/ML Vehicle models are all functioning properly. All comms systems ready & active. | Camera is powered, active and connected to the network. | Software and comms are running properly. | Software, Comms and emergency assets are running properly. |
+
+### 6.5.3 Service Flows
+
+Appropriate AI/ML systems shall provide security and data protection as dictated by law and other appropriate policies.
+
+The service flows described in Figure 3 are all machine-to-machine AI/ML intelligent system interactions designed for the sharing of information to with a range of demands from lowest-latency for critical situations (e.g. alarm messages) and relaxed latency for less critical problems. Shared information (possibly including an extensive set of data) can also be exchanged with relaxed latency to support training and updating of the AI/ML model. Each level of service may be owned and operated by a different organization.
+
+This use-case assumes that no more than [10%] of the total ML model size needs to be shared or to updated in a single-low latency transmission.
+
+
+
+```
+
+graph TD
+ SC[Smart City Core Network] <--> RMV[Road Maintenance Vehicle]
+ SC <--> TC[Traffic Camera]
+ SC <--> AUTO[Automobile]
+ SC <--> GW[General Weather]
+ AUTO <--> MAN[Manufacturer]
+ AUTO <--> VMS[Vehicle Maintenance Shop]
+
+```
+
+Diagram illustrating examples of AI-ML interactions. A central 'Smart City Core Network' box is connected to 'Road Maintenance Vehicle', 'Traffic Camera', 'Automobile', and 'General Weather'. The 'Automobile' box is further connected to 'Manufacturer' and 'Vehicle Maintenance Shop'.
+
+**Figure 6.5.3-1: Examples of AI-ML interactions**
+
+#### Vehicle to other AI Systems
+
+Examples of AI-ML model data exchange are:
+
+- Vehicle health and inspection monitoring ML models – Local ML models sense and react to crash, fire, temperature and electrical sensor information. These models are continuously improving and optimizing but not necessarily sharing data if the system is nominal. However, once an emergency situation has occurred, emergency information can be sent to the appropriate emergency response services in the Smart City Core
+
+network, local cameras and road sensors. Extended information can also be shared with relaxed latency demands to support model updates/training.
+
+- Vehicle sensing for vehicle dynamics under ML model sensing and control. Local ML models sense and react to skids, slides, acceleration and breaking. These models are continuously improving and optimizing but not necessarily sharing data if the system is nominal. However, once an emergency situation has occurred, emergency information is immediately broadcasted to appropriate emergency response services and other system applying related ML models to inform them. Extended information can also be shared with relaxed latency demands to support improve the systems prediction accuracy.
+
+#### Traffic Surveillance Camera to Metro Traffic Control
+
+Camera senses accident using local AI/ML models and sends notification to traffic control. Traffic control may use multiple cameras to cover the same incident and, thereby, improve its inference accuracy. Extended information exchanged with low-latency demands can be used to re-train and redistribute reference AI model layers accordingly.
+
+Examples of AI-ML Model data exchange are:
+
+- Camera and Road sensors detect emergency situations – Local camera and road sensor ML models are constantly improving their prediction of emergency situations. Once an emergency situation has occurred emergency information data is shared with appropriate systems to improve the response for all emergency responders. Extended information can also be shared with relaxed latency demands to support improve the systems prediction accuracy.
+
+#### Metro Traffic Control to Metro Emergency Services Network
+
+AI/ML models use automation and prediction to send appropriate EMS vehicles to the accident site.
+
+Examples of AI-ML Model data exchange are:
+
+- Camera, Road and Weather sensor use ML models. ML models sensors are continuously improving and optimizing prediction results. Once an emergency situation is detected, emergency information from these systems can be shared with emergency vehicles to, e.g. improve their routing time through traffic based on the situation.
+
+#### Stalled Vehicle to Manufacturer
+
+Stalled vehicle sends data (possibly pre-processed, e.g. AI/ML model data) to automobile manufacturer to help diagnose the problem. Manufacturer uses the information to improve product quality, reliability and performance. Federated and/or Distributed Learning techniques can be used to improve on-board vehicle AI/ML model.
+
+#### Stalled Vehicle to Metro Traffic Control (MTC)
+
+Stalled vehicle sends emergency information to MTC to help warn others. E.g., The specific blind curve location along with other regional data is used to improve all MTC responses. Extended information can also be shared with relaxed latency demands to improve MTC response models.
+
+#### Stalled Vehicle to Repair Service
+
+Stalled vehicle sends data (possibly pre-processed, e.g. AI/ML model data) to repair service to ensure appropriate response vehicles provide proper tools and equipment. Repair service response use Federated and/or Distributed Learning techniques for constant model improvement.
+
+#### Approaching Vehicle communication with Metro Traffic Control
+
+MTC warns approaching vehicle of upcoming danger and depending on the SAE level of driving automation, the vehicle responds appropriately. Extended information can also be shared with relaxed latency demands to support improve the systems prediction accuracy.
+
+### 6.5.4 Post-conditions
+
+All systems identified in this scenario use independent, networked AI/ML Distributed or Federated Learning algorithms to aggregate information from multiple sources to improve layer of the system AI/ML model. Independent AI/ML
+
+training systems ensure that improved models are distributed back to each end-system to improve the overall safety and robustness of the next response.
+
+### 6.5.5 Existing features partly or fully covering the use case functionality
+
+None.
+
+### 6.5.6 Potential New Requirements needed to support the use case
+
+Table 6.5.6-1 provides example ML models (sizes and DL data rates) that are considered for the use-cases above and Table 6.5.6-2 outlines latency requirements. It is assumed that a maximum of 10% of the (full) model size is exchanged among the participating systems.
+
+**Table 6.5.6-1: ML Networks/models and potential DL data rates**
+
+| DNN model | 32 bits per parameter | | |
+|------------------------|-----------------------|---------------------------------------------|--------------------------------|
+| | Full Model (MBytes) | Exchanged data (Mbytes) [10% of full model] | Max DL user data rate (Mbit/s) |
+| 1.0 MobileNet-224 [54] | 16.8 | 1.68 | 13.4 |
+| SSD-ResNet34 [55] | 81 | 8.1 | 64.8 |
+| SSD-MobileNet-v1 [56] | 27.3 | 2.37 | 21.8 |
+| MASK R-CNN [57] | 245 | 24.5 | ~100 |
+| DLRM [58] | 400 | 40.0 | 10 |
+
+**Table 6.5.6-2: Potential Latency Requirements**
+
+| User application | Potential Latency Requirements |
+|------------------------------------------------------------------|-----------------------------------|
+| | Exchanged data – Download latency |
+| Vehicle Detects Fault and Pulls Over to Avoid Accident | ~500ms – 1sec |
+| Roadside Camera Detects Road Hazard and Warns Smart City Network | ~500ms – 1sec |
+| On-Coming Traffic Detects Hazard and Avoids Accident | ~500ms – 1sec |
+| Video recognition | ~500ms – 1sec |
+| Smart City Detect Accident and Issues Local Warning | ~up to few sec |
+| Car Manufacturer/Insurance warned about fault | Up to few mins |
+
+Requirements:
+
+[P.R.6.5-001] The 5G system shall be able to support downloading of data with a maximum size of ~2-40 MB to update the local AI/ML model with latency up to 500ms – 1s.
+
+[P.R.6.5-002] The 5G system shall be able to support downloading of data with a maximum size of ~2-40 MB to update the local AI/ML model with (user experienced) DL data rate of up to 100 Mbit/s.
+
+[P.R.6.5-003] The 5G system shall be able support downloading of data to update the local AI/ML model with communication service availability up to 99.999 %.
+
+## 6.6 Shared AI/ML model monitoring
+
+### 6.6.1 Description
+
+AI/ML models are trained on a training data set to accomplish an established task. The tasks may vary from image or speech recognition to forecasting to optimize, as example, handover performance (see 3GPP TR 28.809 [59]) or tuning Core Network assisted parameters (see clause 5.4.6.2, TS 23.501).
+
+In each of these tasks, the provider of the shared AI/ML model may benefit from sharing a trained AI/ML model with the consumer(s) of the shared AI/ML model or may benefit from a distributed/federated AI/ML model training or a split AI/ML model training over the 5G system. Furthermore, AI/ML model monitoring is a requirement to enable online learning in the network (e.g. via Reinforcement Learning), a set of techniques more suited to promptly react to service degradation.
+
+NOTE: The following terms are used in this use case:
+
+**Shared AI/ML model:** AI/ML model that is shared among different applications, e.g., the AI/ML model is pre-trained and provisioned to different consumers, or the AI/ML model is trained using distributed/federated learning approach or by splitting the model training phase to different parts executed in different network locations.
+
+**Shared AI/ML model provider:** application server that is providing or managing a "shared AI/ML model".
+
+**Shared AI/ML model consumer:** application, e.g. running on the UE, that is using/consuming a "shared AI/ML model".
+
+Due to changes in the scenario (i.e., in the context from which training data are collected), an AI/ML model may provide poor performances compared with the performance of the AI/ML model measured during the model testing phase. This can happen when over time the distribution of the input data for inference differs from the distribution of the training data, or if the AI/ML model is utilized in a different context. In this case, the shared AI/ML model provider should be able to promptly detect the performance degradation and react in order to avoid service degradation or disruptions. Quite often, update of a shared AI/ML model is not solely dependent on inference results of one shared AI/ML model consumer as performance degradation could be due to some other error source, e.g., model input measurement errors. To detect outdated shared AI/ML model, the shared AI/ML model provider can make use of inference results from multiple shared AI/ML model consumers and a spatial and temporal analysis is performed before triggering shared AI/ML model update.
+
+Therefore, the shared AI/ML model provider, once sharing an AI/ML model over 5G System with a shared AI/ML model consumer, needs to keep track of the model performances to detect possible performance degradation of the shared AI/ML model (e.g. based on inference feedback from AI/ML model consumer such as a lower confidence level).
+
+Alternatively, the shared AI/ML model provider can split the AI/ML model training with a shared AI/ML model consumer to constantly improve the performance of the shared AI/ML model based on a local training and/or inference feedback from the shared AI/ML model consumer. The local part of the shared AI/ML model will be trained/fine-tuned under the shared AI/ML model provider guidance. The input to this training will be data available at the shared AI/ML model consumer. The output of local model training or an inference at shared AI/ML model consumer can be provided to the shared AI/ML model provider and be used by the shared AI/ML model provider to provide further information for the 5G System to improve its operations.
+
+### 6.6.2 Pre-conditions
+
+The shared AI/ML model provider stores multiple AI/ML models along with their performances measured during the test phase.
+
+The shared AI/ML model provider is capable of sharing AI/ML models with shared AI/ML model consumers leveraging on 5GS.
+
+The AI/ML model provider is capable of splitting and/or distributing the AI/ML model training with/to a shared AI/ML model consumer leveraging on 5GS.
+
+The shared AI/ML model consumer may run applications requiring the usage of AI/ML models and download them from the AI/ML model provider via the 5GS.
+
+### 6.6.3 Service Flows
+
+1. The shared AI/ML model provider wants to optimize performance of some process by means of shared AI/ML model performance.
+2. The shared AI/ML model provider sends the trained shared AI/ML model to the shared AI/ML model consumer at the UE leveraging on the 5GS.
+3. The UE receives the model and employs the model to perform local training and inference using data available on the UE.
+4. The shared AI/ML model provider monitors the context scenario (e.g. the UE data which is available to the application) in which the UE is running the shared AI/ML model and the model performance.
+5. If a change in the context scenario or model performance is detected, e.g. based on an inference feedback from the shared AI/ML model consumer, the shared AI/ML model provider, in order to avoid model performance degradation, shares with the AI/ML model consumer an updated version of the shared AI/ML model retrained to capture the new context with expected better performance.
+6. The UE continues to run the updated model without experiencing performance degradation.
+
+### 6.6.4 Post-conditions
+
+Following the example in the use case, the shared AI/ML model provider receives an accurate forecast regarding AI/ML model performance, and the AI/ML model consumer is using an AI/ML model with high performance.
+
+### 6.6.5 Existing features partly or fully covering the use case functionality
+
+### 6.6.6 Potential New Requirements needed to support the use case
+
+[P.R.6.6-001] The 5GS shall be able to transfer an updated AI/ML model from the shared AI/ML model provider to the shared AI/ML model consumer within [1s-1min] latency for AI/ML models of a maximal size of [100-500] MB.
+
+## 6.7 Prediction of AI/ML model distribution
+
+### 6.7.1 Description
+
+If the AI/ML model server was intelligent enough, it would be ideal that the AI/ML model server could predict that the User would need to use some AI/ML model and download the AI/ML model to the UE in advance.
+
+Take image recognition for example, the AI/ML model could be able to predict and download specific AI/ML model in advance based on the user's location, direction of travel and users use of image recognition functionality. For the users located in a famous history museum or moving towards a famous history museum, the 5G network functions and the AI/ML model server could interact with each other and predict that the users could possibly need to use the AI/ML model designed specifically for such history museum which is suitable for the indoor environment and good at historic pictures recognition. Similarly, for the users located in a zoo or moving towards a zoo, the 5G network functions and the AI/ML model server could interact with each other and predict that the users could possibly need to use the AI/ML model designed specifically for animal recognition. In contrast, for the users located in an arboretum or moving towards an arboretum, the 5G network functions and the AI/ML model server could interact with each other and predict that the users could possibly need to use the AI/ML model designed specifically for flower or plant recognition.
+
+**Editor's Note:** it is FFS whether other examples than image recognition need to be studied.
+
+The 5G network and the AI/ML model shall not violate the user privacy policies for the prediction or pre-download of AI/ML models.
+
+According to user privacy policies, the AI/ML model server may not to be able to get access to the UE's location information.
+
+If the AI/ML model server is allowed to access to the UE's location information according to user privacy policies, the AI/ML model server could obtain the UE's location information via two options:
+
+Option 1: the AI/ML model server could obtain the UE's location information directly from the UE, over the application layer. This is pure application layer interaction between the AI/ML based image recognition application and the AI/ML model server.
+
+Option 2: the AI/ML model server could obtain the UE's location information via the location service provided by the 5G network. This is already specified in TS 23.273 [6] (see further analysis in section 6.1.4).
+
+If the AI/ML model server is not allowed to access to the UE's location information according to user privacy policies, the 5G network has the UE's location information and is not allowed to expose the UE location information to the AI/ML model server. The 5G network function could still interaction with the AI/ML model server for prediction of need of certain AI/ML model without breaking the user privacy policies. There could be lots of workable solutions. Here daftly describe two possible solutions:
+
+Option a): Prediction based on monitoring function of the 5G network. New monitoring event could to be introduced to assist the prediction by the AI/ML model server without disclosure of User location information to the AI/ML model server. Option b) Prediction based on NWDAF analytics function of the 5G network. Based on analytics of UE's location, mobility, download data size and etc, the 5G network could predict that lots UE will download certain amount of data from an AI/ML model server in some location area and inform the AI/ML model that certain UE will probably download certain amount of data. The AI/ML model server could use such information to adjust its prediction.
+
+### 6.7.2 Pre-conditions
+
+The UE runs an application providing the capability of AI/ML model inference for image recognition.
+
+An AI/ML server manages the AI/ML model pool, and is capable to download the requested model to the application providing AI/ML based image recognition.
+
+The 5G system is able to provide 5G network related information to the AI/ML server.
+
+### 6.7.3a Service Flows for Prediction based on monitoring function of the 5G network
+
+- 1) The AI/ML model server provides to the 5G network function with some criteria. Each criterion could have different rules. For example, one criterion could contain a list of location areas which contains all the museums, galleries and antique shops all over the country.
+- 2) If the 5G network functions determine the UE meets one criterion, for example, the UE is located in the list of location areas, then the 5GS network function (e.g., NEF) notify the AI/ML model server which criterion the UE meets.
+- 3) According the criterion that the UE meets, the AI/ML model server determines that the UE might need to use the AI/ML model designed specifically for such history museum which is suitable for the indoor environment and good at historic pictures recognition.
+- 4) The 5G operator need to make sure that the criteria provided by the AI/ML model does not break the user privacy policies.
+
+#### 6.7.3b Service Flows for Prediction based on NWDAF analytics function of the 5G network
+
+- 1) The NWDAF do the data collection and analytics work for the UE's location, mobility, download data size etc.
+- 2) Based on the NWDAF analytics, the 5G network could predict that lots UE will download certain amount of data from an AI/ML model server in some location area.
+- 3) For the AI/ML model server that has subscribed the data analytics service from 5G network, 5G network inform AI/ML model server directly or via NEF that certain UE will probably download certain amount of data.
+
+- 4) The AI/ML model server could use such information to adjust its prediction.
+
+### 6.7.4 Post-conditions
+
+The 5G network and the AI/ML model server could predict the need of download certain AI/ML model from the UE and refine the prediction during the interaction.
+
+The 5G network could adjust its resource for download of data from AI/ML without expansion of capacity based on the prediction.
+
+The AI/ML model server could predict the user preference and needs without knowing UE's private information, such as location information.
+
+The UE could get better user experience during the use of AI/ML model application via 5G network.
+
+### 6.7.5 Existing features partly or fully covering the use case functionality
+
+TS23.273[6] clause 4.1:
+
+Location information for one or multiple target UEs may be requested by and reported to an LCS client or an AF within or external to a PLMN, or a control plane NF within a PLMN. Location information contained in the location request and location information contained in the location response are defined in clause 5.5.
+
+For location request from LCS client (neither in the UE nor in the NG-RAN) or AF external to a PLMN, privacy verification of the target UE shall be enabled to check whether it is allowed to acquire the UE location information based on UE LCS privacy profile and whether the LCS client or the AF is authorised to use the location service as defined in clause 5.4.
+
+Note: the AI/ML server plays the role of AF to acquire the UE location information.
+
+TS 23.501[48] clause 4.15.3.1
+
+Currently the Monitoring Events feature defined in TS 23.501 [48] is intended for monitoring of specific events in the 3GPP system and reporting such Monitoring Events via the NEF. Location Reporting is one of the supported monitoring events is specified in Table 4.15.3.1-1 of TS 23.502 [49]. However, the current monitoring event features indicates either the Current Location or the Last Known Location of a UE to an AF via NEF, this is not applicable when the AI/ML model server is not allowed to access to the UE's location information according to user privacy policies.
+
+### 6.7.6 Potential Requirements
+
+[P.R.6.7-001] Subject to user consent, operator policy and regulatory constraints, the 5G system shall support the provision of monitoring information or analytics information to a trusted 3rd party AI/ML server for allowing this 3rd party AI/ML server to make a prediction for a suitable AI/ML model to be downloaded to the concerned UE.
+
+# --- 7 Distributed/Federated Learning over 5G system
+
+## 7.1 Uncompressed Federated Learning for image recognition
+
+### 7.1.1 Description
+
+Nowadays, the smartphone camera has become the most popular tool to shoot image and video, which holds many valuable vision data for image recognition model training. For many image recognition tasks, the images/videos collected by mobile devices are essential for training a global model. Federated Learning (FL) is an increasingly widely-used approach for training computer vision and image recognition models.
+
+In Federated Learning mode, the cloud server trains a global model by aggregating local models partially-trained by each end devices based on the iterative model averaging [30]. As depicted in Figure 7.1-2, within each training iteration, a device performs the training based on the model downloaded from the AI server using the local training
+
+data. Then the device reports the interim training results (e.g., gradients for the DNN) to the cloud server via 5G UL channels. The server aggregates the gradients from the devices, and updates the global model. Next, the updated global model is distributed to the devices via 5G DL channels, the devices can perform the training for the next iteration.
+
+
+
+Figure 7.1.1-1: Federated Learning over 5G system. This diagram illustrates the interaction between a 5G/6G cloud server and multiple devices (car, robot, smartphone, drone). The cloud server is labeled '5G/6G cloud (Updating DNN by Federated averaging)' and contains a neural network icon. Devices send 'Partially-trained DNN with new gradients' to the cloud. The cloud performs 'Iterative training' and returns an 'Updated DNN with new weithts' (sic) to the devices. Devices also receive a 'Subset of training data' from the cloud.
+
+**Figure 7.1.1-1. Federated Learning over 5G system**
+
+An iterative Federated Learning procedure is illustrated in Figure 7.1.1-2. In the $N$ th training iteration, the device performs the training based on the model downloaded from the FL training server using the images/videos collected locally. Then the device reports the $N$ th-iteration interim training results (e.g., gradients for the DNN) to the server via 5G UL channels. Meanwhile, the global model and training configuration for the $(N+1)$ th iteration are sent to the device. When the server aggregates the gradients from the devices for the $N$ th iteration, the device performs the training for the $(N+1)$ th iteration. The federated aggregation outputs are used to update the global model, which will be distributed to devices, together with the updated training configuration.
+
+
+
+Figure 7.1.1-2: Federated Learning timeline for image recognition. This timeline diagram shows the sequence of events between an 'FL training server' (cloud icon) and a 'Device' (smartphone icon) over 'Time'. The device performs 'Training N', 'Training N+1', and 'Training N+2'. During 'Training N', the device sends a 'Training result report N-1' to the server. The server performs 'Federated aggregation' and returns a 'Global model & training configuration N+1' to the device. This process repeats for subsequent iterations.
+
+**Figure 7.1.1-2. Federated Learning timeline for image recognition**
+
+In order to fully utilizing the training resource at device and minimizing the training latency, the training pipeline shown in Figure 7.1.1-2 requires the training results report for the $(N-1)$ th iteration and the global model/training configuration distribution for the $(N+1)$ th iteration are finished during the device's training process for the $N$ th iteration. The analysis in Section 7.1.6 will be developed based on the processing timeline. In practice, more relaxing FL timeline can also be considered with sacrificing the training convergence speed.
+
+The training time should be minimized since mobile devices may only stay in an environment for a short period of time. Further, considering the limited storage at device, it may not realistic to require the training device to store a large amount of training data in the memory for a training after it moves outside the environment.
+
+Different from the decentralized training operated in cloud datacenters, Federated Learning over wireless communications systems need to be modified to adapt to the variable wireless channel conditions, unstable training resource on mobile devices and the device heterogeneity [10, 32, 34]. The Federated Learning protocol for wireless communications can be depicted in Figure 7.1.1-3 [10, 31-32].
+
+For each iteration, the training devices can firstly be selected. The candidate training devices report their computation resource available for the training task to the FL server. The FL server makes the training device selection based on the reports from the devices and other conditions, e.g. the devices' wireless channel conditions, geographic location, etc..
+
+Hereby, besides performing federated learning task, the training devices in a communication system have their other data to transmit at uplink (e.g. for ongoing service transactions), that may be high priority and not latency-tolerant and
+
+its transmission may affect a device's ability to upload the locally trained model. Device selection must therefore account for a trade-off to upload the training results as compared to uploading other uplink data. Furthermore, skipping a device from federated learning model aggregation for one or more iterations affects the convergence of the federated learning model. Therefore, candidate training device selection over wireless links is more complex as compared to federated learning in data centers.
+
+After the training devices are selected, the FL server will send the training configurations to the selected training devices, together with global model for training. A training device starts training based on the received global model and training configuration. When finishing the local training, a device reports its interim training results (e.g., gradients for the DNN) to the FL server. In Figure 7.1.1-3, the training device selection is performed, and the training configurations are sent to the training devices at the beginning of each iteration. If the conditions (e.g. device's computation resource, wireless channel condition, other service transactions of the training devices) are not changed, the training device re-selection and training re-configuration might not be needed for each iteration, i.e. the same group of training devices can participate the training with the same configuration for multiple iterations. Still, the selection of training devices should be alternated over time in order to achieve an independent and identically distributed sampling from all devices, i.e., give a fair chance to all devices to contribute to the aggregated model.
+
+
+
+Figure 7.1.1-3: Typical Federated Learning protocol over wireless communication systems. The diagram illustrates the interaction between an FL training server and five devices (Device A to E) over two training iterations, N-th and N+1-th. The process is divided into three main phases: Training device selection, Model distribution & training configuration, and Training result reporting. In the first iteration (N-th), the server initiates device selection, and devices A, B, C, and D report their training resource reports. The server then distributes the global model and training configuration to these devices. They perform training and report their training result reports. The server performs federated aggregation. In the second iteration (N+1-th), the process repeats with device selection, model distribution, training, and result reporting. Device E is shown participating in the second iteration. The timeline is marked with 'Time' at the bottom right.
+
+Figure 7.1.1-3. Typical Federated Learning protocol over wireless communication systems
+
+### 7.1.2 Pre-conditions
+
+The UE runs an application providing the capability of Federated Learning (FL) for the image recognition task.
+
+The FL application on the UE is capable to report its interim training results to the FL server.
+
+The FL server is capable to aggregate the interim training results from the federated UE, form the global model, and distribute the global model for training in the next iteration.
+
+The 5G system has the ability to provide 5G network related information to the FL server.
+
+### 7.1.3 Service Flows
+
+1. The FL server selects a set of federated UEs based on different own criteria. One possibility is to use available information on UE geographic location (subject to user consent and/or operator/regulatory requirements).
+2. The FL server distributes the global model to be federated UEs via 5G network.
+3. The FL application in a federated UE performs the training based on the local training data set collected by the UE, and then reports the interim training results (e.g., gradients for the DNN) to the FL server via 5G network.
+4. The FL server aggregates the gradients from the UEs, and updates the global model.
+5. Redo Step 1) to 4) for the training for the next iteration.
+
+### 7.1.4 Post-conditions
+
+The AI/ML model for image recognition is trained and converges, and the training accuracy and latency need to be guaranteed.
+
+The FL training task for image recognition can be completed under the available computation and energy resource of the federated UEs. And the consumed the computation, communication and energy resources over the federated UEs and the FL server are optimized.
+
+### 7.1.5 Existing features partly or fully covering the use case functionality
+
+This use case mainly requires high data rate together with low latency. The high data rate requirements to 5G system are listed in Clause 7.1 and 7.6 of TS22.261 [4]. As in Table 7.1-1 of [4], 300Mbps DL experienced data rate and 50Mbps UL experienced data rate are required in dense urban scenario, and 1Gbps DL experienced data rate and 500Mbps UL experienced data rate are required in indoor hotspot scenario. As in Table 7.6.1-1 of [4], cloud/edge/split rendering-related data transmission requires up to 0.1Gbps data rate with [5-10]ms latency countrywide.
+
+### 7.1.6 Potential New Requirements needed to support the use case
+
+As introduced in clause 7.1.1, in order to minimizing the training latency for Federated Learning for image recognition, the computation resource at device for the training task should be fully utilized, i.e. the training pipeline in figure 7.1.1-1 is desired to be maintained.
+
+If considering to train a 7-bit CNN model VGG16\_BN using 224×224×3 images as training data, table 7.1.6-1 shows the sum of gradient uploading latency, the federated aggregation latency and the global model downloading latency should be no larger than the GPU computation time at device for one iteration. For different batch sizes, the gradient uploading and the global model downloading for each iteration needs to be finished in [52~162ms], respectively.
+
+Different from the “single-UE latency” considered by previous requirement study [15], what is more essential for synchronous Federated Learning is the latency within which all federated devices can finish the gradient uploading. In other words, all training devices need to finish the gradient uploading within the latency in table 7.1.6-1, even if multiple training devices are present in a cell.
+
+The size of the 8-bit VGG16\_BN model is 132MByte for either the trained gradients or the global model. Hence in order to finish the gradient uploading and the global model downloading within the duration, the required UL and DL data rate are shown in table 7.1.6.1-1, which are [6.5Gbit/s to 20.3Gbit/s] respectively. And it should be noted that 132MByte is the size without compression. The size may be reduced if advanced model/gradient compression techniques can be adopted.
+
+In the legacy requirements to 5G system, e.g. [4], the full coverage is always desired for all UEs. However, the AI/ML model training task may to some extent relax the requirements on continuous network coverage. When a FL server selects the training devices for a Federated Learning task, it can try to pick the UEs in a satisfactory coverage, if they can collect the training data needed. This implies that even in a non-continuous coverage of 5G mmWave, the Federated Learning task can be well carried out. This provides to 5G operators a service better exploring the use of their FR2 spectrum resource.
+
+#### 7.1.6.1 Potential KPI Requirements
+
+The potential KPI requirements needed to support the use case include:
+
+[P.R.7.1-001] The 5G system shall support a user experienced DL data rate as given in table 7.1.6.1-1, to enable uncompressed Federated Learning for image recognition.
+
+[P.R.7.1-002] The 5G system shall support a user experience UL data rate as given in from table 7.1.6.1-1, to enable uncompressed Federated Learning for image recognition.
+
+**Table 7.1.6.1-1: Latency and user experienced UL/DL data rates for uncompressed Federated Learning**
+
+| Mini-batch size (images) | GPU computation time (ms) | Maximum latency for trained gradient uploading and global model distribution (see note 1) | User experienced UL/DL data rate for trained gradient uploading and global model distribution (see note 2) |
+|--------------------------|---------------------------|-------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+|--------------------------|---------------------------|-------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+
+| Mini-batch size (images) | GPU computation time (ms) | Maximum latency for trained gradient uploading and global model distribution (see note 1) | User experienced UL/DL data rate for trained gradient uploading and global model distribution (see note 2) |
+|--------------------------|---------------------------|-------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+| 64 | 325 | 3.24s | 325Mbit/s |
+| 32 | 191 | 1.9s | 55Mbit/s |
+| 16 | 131 | 1.3s | 810Mbit/s |
+| 8 | 111 | 1.1s | 960Mbit/s |
+| 4 | 105 | 1.04s | 1.0Gbit/s |
+
+NOTE 1: Latency in this table is assumed 20 times the device GPU computation time for the given mini-batch size.
+NOTE 2: Values provided in the table are calculative needs for an 8-bit VGG16 BN model with 132MByte size, given mini-batch sizes and a duration of [FFS] seconds per iteration. Necessary user experience UL/DL data rates can be reduced by e.g. setting longer times per iteration, applying compressed FL, or using another AI/ML model.
+
+## 7.2 Compressed Federated Learning for image/video processing
+
+### 7.2.1 Description
+
+Federated learning can be used to train AI/ML models based on number of images and videos generated by cameras in mobile devices by iteratively exchanging gradient of updating models instead of direct user images and videos. Because this method can utilize images and videos from many users, the performance of a trained AI/ML model can be significantly higher than a stand-alone case. However, the basic federated learning methods can have disadvantages by massive uplink traffics and high computational cost at a mobile device. Therefore, it is beneficial to consider a compressed federated learning (CFL) method, which allows compressed (not full) models to be transferred during a learning period.
+
+Figure 7.2.1-1 shows the essential procedure of CFL. CFL iteratively performs a set of the three operation stages. In order to describe the iterations in CFL, we introduce a cycle of I: each cycle begins with the 1st iteration and ends with I-th iteration, which is immediately followed by the 1st iteration of the next cycle (e.g., (I+1)st iteration). For each iteration, the three operation stages include the training UE selection, the sparse weight distribution, and the training result reporting stages. The operations of these three stages in the first iteration and the operation in the last iteration are different from the operations in the other iterations.
+
+Each iteration in CFL starts with the training UE selection stage, at which the CFL server selects a set of available users from the candidate users to associate with the same purpose AI/ML model. To the selected users, ready to participate in the learning process because of being an available state, the CFL server transmits the train configuration information. At the next stage, the CFL server sends the sparse global model, which could be an initial version of the AI/ML model in the first iteration. Otherwise, the sparse global model is an aggregated version based on user reporting information.
+
+Then, each UE trains a received model after expanding the spatial model and reports an intermediate training result to the CFL server, where the training result is comprised only of significant value weight gradients for applying a model compression. By doing so, uplink throughout requirement can be significantly reduced in comparison with the basic federated learning method without compression. In the last iteration, I-th iteration, the CFL Server sends 'train stop message' to UEs so that the UEs can stop sending its update any longer, and the CFL Server performs fine-tuning by pruning unnecessary nodes. Throughout these multiple iterations of a cycle (i.e., from the 1st iteration through the I-th iteration) as in the figure, the AI/ML model will be progressively enhanced based on user data in mobile networks at reduced requirements of uplink and downlink throughout.
+
+
+
+The figure illustrates the timeline for Compressed Federated Learning (CFL) across three iterations. Each iteration involves a series of steps between a Base Station (BS) and multiple User Equipment (UE) units (UE 1, UE 2, UE 3, UE 4).
+
+**1-th Compressed Federated Learning iteration:**
+
+- Training UE selection:** BS sends Device selection to UEs; UEs send UE resource report to BS.
+- Global Initial Sparse Model multicast:** BS sends Sparse Model multicast to UEs; UEs perform Sparse to Dense Training.
+- Training result reporting:** UEs send Training result report $diff(w_k)$ to BS; BS performs Compressed Federated aggregation.
+
+**2-th Compressed Federated Learning iteration:**
+
+- Training UE selection:** BS sends Device selection to UEs; UEs send UE resource report to BS.
+- Sparse weight multicast:** BS sends Sparse weight multicast to UEs; UEs perform Sparse to Dense Training.
+- Training result reporting:** UEs send Training result report $diff(w_k)$ to BS; BS performs Compressed Federated aggregation.
+
+**(I-1)-th Compressed Federated Learning iteration:**
+
+- Training UE selection:** BS sends Device selection to UEs; UEs send UE resource report to BS.
+- Sparse weight multicast:** BS sends Sparse weight multicast to UEs; UEs perform Sparse to Dense Training.
+- Training result reporting:** UEs send Training result report $diff(w_k)$ to BS; BS performs Compressed Federated aggregation.
+
+**I-th Compressed Federated Learning iteration:**
+
+- Training UE selection:** BS sends Device selection to UEs; UEs send UE resource report to BS.
+- Sparse weight multicast:** BS sends Sparse weight multicast to UEs; UEs perform Sparse to Dense Training.
+- Training result reporting:** UEs send Training result report $diff(w_k)$ to BS; BS performs BS pruning Step and sends "train stop msg" to UEs.
+
+**(I+1)-th Compressed Federated Learning iteration:**
+
+- Training UE selection:** BS sends Device selection to UEs; UEs send UE resource report to BS.
+- New Global Sparse Model-info multicast:** BS sends New Sparse Model-info multicast to UEs; UEs perform Sparse to Dense Training.
+- Training result reporting:** UEs send Training result report $diff(w_k)$ to BS; BS performs Compressed Federated aggregation.
+
+Sequence diagrams showing Compressed Federated Learning timelines for image recognition across three iterations: 1-th, 2-th, and (I+1)-th. The diagrams show interactions between a Base Station (BS) and four User Equipment (UE) units (UE 1 to UE 4).
+
+Figure 7.2.1-1. Compressed Federated Learning timeline for image recognition
+
+### 7.2.2 Pre-conditions
+
+UE can have a computational hardware and algorithm capability to train an AI/ML model such as for an image and video cognition.
+
+UE can send intermediate training results to a CFL server.
+
+A CFL server can select training devices and determine training configuration.
+
+A CFL server can aggregate intermediate training results and generate a sparse global model for the next learning iteration.
+
+A CFL server can distribute a global AI/ML model to a set of selected users.
+
+### 7.2.3 Service Flows
+
+Step 1: The CFL server selects the training users from candidate users.
+
+Step 2: The CFL server sends the configuration information to the selected users.
+
+Step 3: The CFL server distributes the initial (or, aggregated) sparse global model to the selected users through a 5G networks.
+
+Step 4: Each UE expands the sparse global model and train the expanded model using its local data. Then, each UE sends only significant value weight gradients to the CFL server.
+
+Step 5: The CFL server aggregates the training results received from the training UEs and update a global model using the aggregated results.
+
+Step 6: Until the AI/ML model reaches saturated performance enhancement, the process runs repeatedly from step 1.
+
+Step 7: Otherwise, the CFL server performs fine-tuning for a global model compression for a global model. This process can be applied regularly so as to improve bandwidth and computation resource efficiency before the training finalization.
+
+Finally, the CFL server distributes the new sparse global model to all users which needs the same AI/ML model.
+
+### 7.2.4 Post-conditions
+
+For a UE prospective, CFL can reduce uplink and downlink throughput requirements for the federated learning process. Also, the computational complexity in UEs can be significantly reduced because of enabling a compressed model.
+
+### 7.2.5 Existing features partly or fully covering the use case functionality
+
+#### Latency analysis for gradient uploading and the global model downloading for image recognition
+
+AI/ML model training data for CFL is a new type of traffic. Consider CFL to train an 8-bit CNN VGG16 model with 224x224x3 images. Table 7.2.5-1 shows that the single GPU computation time should be larger than the addition of gradient uploading latency and global model downloading latency.
+
+**Table 7.2.5-1: GPU computation time for different mini-batch sizes for Compressed Federated Learning**
+
+| Mini-batch size (images) | GPU computation time (ms) | Required latency for trained gradient uploading (sec) (see note 1) | Required latency for global model distribution (sec) (see note 1) |
+|--------------------------|---------------------------|--------------------------------------------------------------------|-------------------------------------------------------------------|
+| 64 | 325 | 3.25 | 3.25 |
+| 32 | 191 | 1.91 | 1.91 |
+| 16 | 131 | 1.31 | 1.31 |
+| 8 | 111 | 1.11 | 1.11 |
+
+| Mini-batch size (images) | GPU computation time (ms) | Required latency for trained gradient uploading (sec) (see note 1) | Required latency for global model distribution (sec) (see note 1) |
+|------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------------------------------|-------------------------------------------------------------------|
+| 4 | 105 | 1.05 | 1.05 |
+| NOTE 1: Latency in this table is assumed 20 times the device GPU computation time for the given mini-batch size. | | | |
+
+#### Data rate analysis for gradient uploading and the global model downloading for image recognition
+
+Table 7.2.5-2 shows the required data rate for gradient uploading and global model downloading for the above 8-bit VGG16 model when CFL is applied. We calculated the required data rate based on table 1 in [39], in which the pruning size of the 8-bit VGG16 model can be reduced 13 times from the original size of 138 Mbyte. It is noteworthy that 13 times model compression gives almost no accuracy degradation for the 8-bit VGG16 model. If we assume that the minibatch size is 4, the uplink required rate is $\text{compressed trained parameter size} \times 8 / (\text{GPU computation time} / 2) = (138 / 13) \text{ Mbyte} \times 8 \text{ bits} / ((105\text{ms} \times 20 / 1000) / 2) = 80.88 \text{ Mbit/s}$ which is same to the downlink require rate.
+
+**Table 7.2.5-2: User experienced data rate for gradient uploading and global model downloading**
+ User experienced data rate = $\text{compressed trained parameter size} \times 8 / (\text{GPU computation time} / 2)$
+
+| Mini-batch size (images) | User experienced UL data rate for trained gradient uploading (Mbit/s) (see note 2) | User experienced DL data rate for global model distribution (Mbit/s) (see note 2) |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
+| 64 | 26.13 | 26.13 |
+| 32 | 44.46 | 44.46 |
+| 16 | 64.83 | 64.83 |
+| 8 | 76.51 | 76.51 |
+| 4 | 80.88 | 80.88 |
+| NOTE 2: Values provided in the table are calculative needs for an 8-bit VGG16 BN compressed model with 10.61MByte size, given mini-batch sizes per iteration. | | |
+
+In the case of 8-bit CNN VGG16, CFL compared to FL can transmit up to 13 times more model information through model compression. Hence, when using the same uplink payload as FL, up to 13 times more users can be simultaneously supported. For example, as shown in Figure 7.2.5-1 which is redrawing using the associated data in [50], the accuracy performance of the FL with 15 participants, which is five times than the FL with 3 participants, can be significantly increased by 6.5%. If we consider the maximum compression efficiency of CFL with supporting 13 times more users, a further performance gain is expected.
+
+
+
+| Total number of users | Accuracy |
+|-----------------------|----------|
+| 3 | 0.835 |
+| 6 | 0.885 |
+| 9 | 0.895 |
+| 12 | 0.900 |
+| 15 | 0.900 |
+| 18 | 0.900 |
+
+Figure 7.2.5-1: A line graph showing Federated Learning accuracy as the total number of users increases. The x-axis is 'Total number of users' (3, 6, 9, 12, 15, 18) and the y-axis is 'Accuracy' (0.83 to 0.91). The accuracy increases from approximately 0.835 at 3 users to about 0.90 at 18 users.
+
+**Figure 7.2.5-1: Federated Learning accuracy as the total number of users**
+Redrawing using the associated data in [60]
+
+For the flexibility and accuracy of FL, the compression rate of CFL can be adjusted according to the user's channel conditions. For example, even in the case of a user with a bad channel, the problem of not participating in FL can be solved by increasing the compression ratio of the model.
+
+### 7.2.6 Potential New Requirements needed to support the use case
+
+[P.R.7.2.6-001] The 5G system shall support to upload a trained gradient for each iteration of Compressed Federated Learning with a maximum latency of 1.05~3.25s.
+
+[P.R.7.2.6-002] The 5G system shall support downloading the global model for each iteration of Compressed Federated Learning with a maximum latency of 1.05~3.25s.
+
+[P.R.7.2.6-003] The 5G system shall support UL unicast transmission with 26.13~80.88Mbit/s user experienced UL data rates and a communication service availability not lower than [99.9%] for reporting the trained gradients for Compressed Federated Learning.
+
+[P.R.7.2.6-004] The 5G system shall support DL multicast transmission with 26.13~80.88Mbit/s user experienced DL data rates and a communication service availability not lower than [99.9%] for distributing the global model for Compressed Federated Learning.
+
+## 7.3 Data Transfer Disturbance in Multi-agent multi-device ML Operations
+
+### 7.3.1 Description
+
+A brief story of machine learning is nothing but a computer (that has no or limited imprinted programs for a certain task) exploiting its own capability (“performance”) towards a certain task using data (“experience”). There are several criteria to classify the types of Machine Learning depending on the characteristics of the method used. This use case is intended to describe a case of multi-agent multi-device ML operations with heavy data (i.e., the data size is huge) when there is partial or total disturbance for data collection/transfer (e.g., privacy regulation or temporary technical limitation like shortage of network resources or temporary failure). As depicted in Fig. 7.3.1-1, this use case, Part I, is specifically related to a scenario that there are multiple agents and multiple collecting devices where the devices can perform ML operations, not necessarily in full but as much as they can (i.e., functional splitting is possible between a device and one or more learning agents).
+
+NOTE 1: MBL (Multiple Batch Learning) is one of examples that belong to this scenario, which is known to be better performing when the data is too big for a single agent/server to handle.
+
+NOTE 2: A learning agent is a type of AI/ML training servers that can be inside 5GS (e.g., AI/ML-based support for communication) or outside 5GS (e.g., communication support for AI/ML). Multi-agent training has multiple collaborating agents involved as depicted in Fig. 7.3.1-1 where dotted lines denote collaboration relation between two or more learning agents. The respective learning agents may have different operational situations (e.g., different technical issues, such as congestion or breakdown, and different jurisdiction-related restrictions). In this use case, it is assumed that the learning agent is typically in the cloud, interacting with UE (as a collecting agent). Learning agents A1, A2, ..., An are not an UE.
+
+
+
+The diagram illustrates the functional relation between multiple devices (M1, M2, ..., Mk) and multiple agents (A1, A2, ..., An). At the top, there are several cyan circles representing agents A1, A2, ..., An. At the bottom, there are several yellow rectangles representing devices M1, M2, ..., Mk. Solid arrows point from each device Mi to each agent Aj. Dashed lines connect the agents A1, A2, ..., An, indicating collaboration. A red 'X' is placed over a dashed line between agent An and device M3, with the word 'disturbed' written below it.
+
+Figure 7.3.1-1: Functional relation between multiple devices (M1, M2, ..., Mk) and multiple agents (A1, A2, ..., An).
+
+**Figure 7.3.1-1: Functional relation between multiple devices (M1, M2, ..., Mk in the form of UE) and multiple agents (A1, A2, ..., An). Data sharing between any pair of agents, if exists, is not disturbed/restricted. In “sharing scenario”, the data would generally be *deep-processed data* as opposed to *simply pre-processed or raw data*.**
+
+In the age that privacy was not affecting the flow of data from the source to the learning agent (e.g., a computer), the expected performance is the outcome of all possible computational considerations of the data collected (e.g., refer to the green solid curve of Fig. 7.3.1-2). However, if there is a certain level of disturbance in data collection, the achievable performance toward the given task would not be as good as the one with no such disturbances (refer to the gap between the green solid curve and blue dotted curve in the same figure). Some examples of such disturbances include:
+
+- (1) privacy regulations, such as EU’s General Data Protection Regulation (GDPR) or California Consumer Privacy Act (CCPA);
+- (2) limited capability of transport-layers, such as lack of network resources (e.g., radio resources due to temporal degradation, higher noise/interference level, highly crowded situations, partial/total break-down, and so on) preventing *input data* from being delivered in time:
+ - a. case 1: a portion of input data delivered in time, if any, is still useful (i.e., entropy can get increased/ improved)
+ - b. case 2: a portion of input data delivered in time, if any, is not useful (i.e., it’s not enough to get entropy increased/ improved)
+
+NOTE 3: “input data” can be raw data, trained data, or an intermediate combination of them that is to be transferred from a UE (or a group of UEs, respectively) to one of learning agents.
+
+It is commonly understood that the more data a learning model utilizes the better performance the learning model can achieve (assuming the data are reasonably independent from statistics perspectives or sufficiently correctly labelled (when supervised learning is concerned)), if not too large. However, if there is some disturbance in data collection/transfer, such as regional regulations or technical limitations (as described above), the expected performance would not be as good as the case without the disturbance (the *vertical difference* in figure 7.3.1-2); in addition, it is expected that the learning model would need to take more time to accumulate “experience” with the reduced feeding-rate of learning data caused by such disturbance (the *horizontal difference* in figure 7.3.1-2).
+
+
+
+Figure 7.3.1-2: Performance gap vs. experience of learning for a given task. The graph plots performance on the y-axis against experience of learning on the x-axis. Two curves are shown: a solid green line (1) representing performance with disturbance of input data collection/transfer, and a dotted blue line (2) representing performance without disturbance. The green curve is above the blue curve. Vertical and horizontal red arrows indicate the performance gap between the two curves at experience levels E1 and E2.
+
+**Figure 7.3.1-2: Performance gap vs. experience of learning for a given task: (1) with disturbance of input data collection/transfer (green, solid) (2) without disturbance of input data collection/transfer (blue, dotted).**
+
+Fig. 7.3.1-3 shows an example of possible preparation action that can be taken in UE side if some predictive information can be made available when disturbance is about to happen. In the figure, the preferred deadline for input data transfer is 1 sec ( $t = t_0+1$ ) with the amount of useful “input data” 3 bits in which two different kinds of scheduling are given: (a) is imperfect scheduling whereas (b) is good scheduling as an example, respectively. In reality, the transfer payload type is not limited to “input data” for learning agent(s) and it can also be applied to “learning model” transfer. The transfer direction can be “uplink” (e.g., for input data transfer) or “downlink” (e.g., for model distribution/transfer). This simplified example is intended to explain the justification why new technical requirements would be needed especially when some disturbance exists (e.g., by regulatory or technical causes).
+
+
+
+Figure 7.3.1-3: Example of disturbance of input data transfer within a preferred deadline of 1 sec. The graph plots allowed data rate (bps) on the y-axis against time (s) on the x-axis. (a) shows imperfect scheduling where the data rate is 2 bps from t0 to t0+1, then decreases linearly to 0 bps at t0+2. The area under the curve is a trapezoid. (b) shows good scheduling where the data rate is 3 bps from t0 to t0+1, then decreases linearly to 0 bps at t0+2. The area under the curve is a rectangle. Red arrows indicate the disturbance at t0+1.
+
+**Figure 7.3.1-3: Example of disturbance of input data transfer within a preferred deadline of 1 sec ( $t = t_0+1$ ) with the amount of useful “input data” 3 bits (as an example): (a) For the 3-bit input data amount (“trapezoid” in grey), it takes 2 sec with “imperfect scheduling” (b) For the 3-bit input data amount (“rectangle” in grey), it takes 1 sec with “good scheduling” where the network resources can be assigned to others (other UEs) during $(t_0+1, t_0+2)$ .**
+
+Given the regulatory disturbance, it is intended to minimize (or to prepare to minimize) the impact on transfer caused by technology (e.g., scheduling and/or information necessary for 3GPP entity to perform “good scheduling”). The expected requirements and service flow description are as follows.
+
+### 7.3.2 Pre-conditions
+
+There are three UEs M1, M2 and M3 (computers or learning machines in the form of a UE).
+
+There are two learning agents/servers in the cloud.
+
+UEs M1, M2 and M3 collect data and they process the data for learning they have collected or are collecting, if available, but they don't have to complete the processing due to limited computational capability.
+
+Each UE (M1, M2 and M3, respectively) has a functional splitting point negotiated with their agent(s) regarding data processing for learning.
+
+Agent A1 working with agent A2 for a task can share its outcome with agent A2 so that the outcome from agent A2 can jointly improve the outcome, if possible, which is possibly better than A1's individual outcome and A2's individual outcome.
+
+UE M1 and UE M2 are located in Area 1 of some jurisdiction that doesn't restrict collecting certain type of data.
+
+*Initial connections:*
+
+UE M1 is connected to agent A1 (via eNB, ng-eNB, or gNB) when data connection is necessary (e.g., when needed to upload some data or when needed to download some model).
+
+- Agent A1 provides UE M1 with an alternative agent (i.e., Agent A2) for the use of disturbance, which is (one of) participating agent(s) that agent A1 shares data. [See Description clause for typical types of data]
+- UE M1 is transferring learning data to agent 1.
+
+UE M2 is connected to agent A1.
+
+- Agent A1 provides UE M2 with an alternative agent (i.e., Agent A2) for the use of disturbance, which is (one of) participating agent(s) that agent A1 shares data.
+- UE M2 is transferring learning data to agent 1.
+
+UE M3 is connected to agent A2.
+
+- Agent A2 provides UE M3 with an alternative agent (i.e., Agent A1) for the use of disturbance, which is (one of) participating agent(s) that agent A2 shares data.
+- UE M3 is transferring learning data to agent 2.
+
+
+
+Diagram illustrating initial connections between mobile devices (UEs) and agents. Two agents, A1 and A2, are shown as cyan circles. A1 is connected to two UEs, M1 and M2, which are located within 'Area 1' (indicated by an oval). A2 is connected to UE M3. All connections are shown with double-headed blue arrows. A dashed line connects A1 and A2, indicating they are both learning agents/servers in the cloud.
+
+**Figure 7.3.2-1: Initial connections b/w mobile devices and agents**
+
+### 7.3.3 Service Flows
+
+While transferring learning data to agent A1, UEs M1 and M2 move into Area 2 of some jurisdiction that has restrictive regulations for agent A1 to collect data from UEs within a specific area (or outside a specific area).
+
+As a result, UEs M1 and M2 are restricted to transfer their data to agent 1.
+
+While transferring learning data to agent A2, UE M3 moves into a different area where 5G system provides prior notification on possible traffic congestion which might disturb UE M3 from keeping transferring learning data to agent A2.
+
+UE M3 makes a selection of an action policy: (action 1) to defer the transfer or (action 2) to request to speed up the transfer.
+
+- If action 1 is selected, UE M3 will resume transferring when it becomes available (not the main focus of this use case);
+- If action 2 is selected, UE M3 will be able to (2a) more urgent/useful segment of data (send priority one over the other) and/or (2b) request more network resources to use.
+
+*Modified connections (UEs M1 and M2):*
+
+UE M1 attempts to get connected to agent A2 based on the information that agent A1 has provided when initially connected.
+
+- UE M1 keeps transferring the data to agent A2
+- Agent A1 can share the collected data or its processed form of data, vice versa
+
+UE M2 is connected to agent A2
+
+- UE M1 keeps transferring the data to agent A2
+- Agent A1 can share the collected data or its processed form of data, vice versa
+
+UE M3 is allowed to use more network resources to speed up the transfer to agent A2 (case 2b).
+
+
+
+Diagram illustrating modified connections between mobile devices (UEs) and agents. Agents A1 and A2 are shown as cyan circles. UEs M1 and M2 are shown as yellow squares within 'Area 2'. UE M3 is shown as a yellow square. Solid lines represent active connections to agent A2. Dashed lines with red 'X' marks represent restricted connections to agent A1. A dashed line with a red 'X' mark connects UE M3 to agent A2, labeled 'Prior Notification of congestion'. A dashed line with a red 'X' mark connects UE M3 to agent A1, labeled 'restriction'. A dashed line with a red 'X' mark connects UE M1 to agent A1, labeled 'restriction'. A dashed line with a red 'X' mark connects UE M2 to agent A1, labeled 'restriction'. A dashed line with a red 'X' mark connects UE M3 to agent A2, labeled 'More data rate allowed'.
+
+**Figure 7.3.3-1: Modified connections b/w mobile devices and agents**
+
+### 7.3.4 Post-conditions
+
+NOTE: Post-conditions are described in two different aspects (communication aspect and ML operation aspect).
+
+**Table 7.3.4-1: Post-conditions in communication aspect and ML operation aspect.**
+
+| Post-condition | Description in Communication aspects | Description in AI/ML operation aspects |
+|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| #1 | UE M1 and UE M2 can continue to transfer data. | Agent A1 and Agent A2 could continue to improve the outcome (e.g., learning model) even when disturbance happens. |
+| #2 | UE M3 can (1) send priority portion of data over the other and/or (2) complete the transfer or maximize the transfer completion ratio before congestion happens . | Agent A2 could minimize the impact of temporal traffic congestion as UE M3 (1) transferred priority portion of data and (2) transferred more data to Agent A2 before traffic congestion happens and disturbs. |
+
+### 7.3.5 Existing features partly or fully covering the use case functionality
+
+Editor's note: text to be provided.
+
+### 7.3.6 Potential New Requirements needed to support the use case
+
+In Table 7.3.6-1, the service-level implications of AI/ML operation are summarized in the third column of Table 7.3.6-1, which are used to derive high-level potential service requirements in communication layer in order to support the AI/ML operation.
+
+**Table 7.3.6-1: High level service requirements (in Communication and AI/ML operation aspects)**
+
+| PR | Potential Requirements in Communication aspects | Implications in AI/ML operation aspects (see note 1) |
+|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [PR.7.3-001]
(see note 2) | 5G system shall provide a suitable means for a learning agent of the AI/ML operations service to use when providing a 5GS using AI/ML application with information (e.g., required increase in data rate due to changes in AI/ML operation, etc. requested by AI/ML application (e.g., of the learning agent or of UE)) necessary to minimize or avoid the impact of communication disruption on AI/ML service/performance.
Editor's Note: Further performance requirements are FFS. | From this Use Case, the relevant AI/ML aspect is "A learning agent is able to provide a UE with information on candidate participating learning agents." The above aspect can be supported by application layer above 3GPP transport layer. However, when transferring the learning data (processed, unprocessed or half-processed), if there are some changes in AI/ML layer to satisfy (e.g., triggered by some cause (e.g., due to technical or jurisdiction issue), it is intended that 3GPP help minimize or avoid the service disruption. |
+| [PR.7.3-002] | 5G system shall provide a suitable means for a UE to provide the AI/ML application of a learning agent with information (e.g., experienced data rate, communication disturbance, geographical location to the extent of jurisdiction (e.g., State level, country level), etc.) necessary to minimize or avoid the impact of communication disruption on AI/ML service/performance.
Editor's Note: Further performance requirements are FFS | From this Use Case, the relevant AI/ML aspect is "A UE is able to inform a learning agent of learning task splitting point."
In the formulation of communication aspect, it is necessary that a collecting agent (UE in this case) provide some information for AI/ML application at the counterpart (which is the learning agent in the cloud) so that the learning agent can perform necessary actions in order to avoid or minimize the AI/ML service disruption. For this to happen, it is necessary that certain information in 5GS (UE) side be shared the learning agent in the cloud. |
+| [PR.7.3-003]
(see note 3) | 5G system shall provide a means to supply prediction info (e.g., on traffic congestion, the related geographical area/spot) so that a UE or learning agent can minimize the impact of learning data transfer disturbance. | |
+| [PR.7.3-004]
(see note 4)
(see note 5) | 5G system shall be able to support adaptive scheduling (e.g., for network resource utilization for the communication between the 5G system and AI/ML application of a learning agent) according to increase or decrease of AI/ML traffic demand due to switching to a different AI/ML mode.
Editor's Note: the above PR is FFS. | From this Use Case, the relevant AI/ML aspect is "The learning agent in the cloud needs to be aware of data rate change (e.g., traffic demand increase or decrease) that has been caused or will be caused by changes in workload sharing such as start using or stop using task splitting, or changing task splitting point that can increase or decrease the workload to UE as a collecting agent, in other words, decrease or increase the traffic demand)". And this needs to be shared with 5GS in order for 5GS to be able to schedule efficiently. |
+| [PR.7.3-004a] | The 5G system shall be able to obtain from the AI/ML application of a learning agent the information about traffic demand increase or decrease (e.g. start/stop task splitting, change task splitting point) by that application (if available). | |
+| [PR.7.3-xx] | | From this Use Case, what is required in AI/ML aspect is "The learning agent in the cloud or the learning agent in a UE is able to be aware of the |
+
+| | | |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|----------------------------------------------------------------------------------------------------------------------------------------|
+| | | disturbance that has happened in the counterpart (i.e., entity/UE that was transferring learning-related data to the learning agent).” |
+| NOTE 1: From this Use Case, the AI/ML aspects/implications are summarized based on which the PR in the left-hand column is formulated
NOTE 2: It is one of possible scenarios that the learning agent can be located within MNO's network (e.g., for learning-based signal processing optimization for RAN entity (e.g., gNB)), which operation is outside the scope of 3GPP but is used for optimization in RAN operations. It is intended that some information (e.g., QoS monitoring info) becomes available for 5G system so that 5G system can take necessary actions (e.g., “impact of communication disruption” for heavy data transfer can be minimized or avoided, which are service disruption in real-world applications, such as basic service robots). It is not intended to violate the QoS level (e.g., 5QI) when increasing or decreasing data rate.
NOTE 3: Disturbance by both jurisdiction (e.g., regional laws that prohibit personal data from being transferred) or by technical difficulty (e.g., traffic congestion for transferring heavy data for AI/ML) are considered in prediction.
NOTE 4: The intended scope of optimizing the network resources includes: to minimize the performance degradation, to minimize temporary imbalance among multiple AI/ML sessions that have changes in their data rate demand due to switching to a different mode (e.g., start using task splitting or stop using task splitting due to some communication disturbance or release from such disturbing factors, respectively) of AI/ML learning operation for a given model.
NOTE 5: the learning agent described in this requirement is in the cloud. | | |
+
+Table 7.3.6-2 provides a summary of performance requirements for different usage scenarios. The required KPIs are dependent upon usage scenarios, especially on the task splitting points of given tasks even under the same usage scenarios. The calculation procedure can be referred to in [36-39].
+
+For an example of image size 32 x 32 x 3 (32 wide, 32 high, 3 depth/colour channels), the weight is 3072; for images with more respectable size 200 x 200 x 3 = 120,000 weights; For a simple ConvNet for CIFAR-10 classification, the regular Neural Network architecture is INPUT→CONV→RELU→POOL→FC (Input layer, convolutional layer, pooling layer and fully-connected layer).
+
+EXAMPLE 1: 32 x 32 x 3 image and six 5 x 5 filters produce a new image of size 28 x 28 x 6! = 564,480
+
+EXAMPLE 2 (Language understanding): BERT\_{base} with L = 12 (layers), H = 768 (hidden size), A = 12 (heads). The number of parameters = 110M
+
+EXAMPLE 3 (Language understanding): BERT\_{large} with L = 24 (layers), H = 1024 (hidden size), A = 16 (heads). The number of parameters = 340M
+
+EXAMPLE 4: [39] for 8-bit VGG16 Pruned, it can reduce the original size (VGG-16 Ref) of 138MB by a factor of (1/13), which size will be approximately 10.3MB. Thus, 10.3MB / (GPU time / 2) ≈ 196MB/sec = 1.56Gb/sec.
+
+NOTE 2: Compared to raw data, the latency requirement for trained data is considered more rigorous as it belongs to the category of data that is more readily usable by the related machine (e.g., by UE, or by agent).
+
+**Table 7.3.6-2: Performance requirements (KPI vectors)**
+
+| | Description in Communication aspects | | | Description in AI/ML operation aspects (all inclusive) | | | Range (see note 2) |
+|------------------------------------------------------------------------------|--------------------------------------|------------------------------------------|---------------------------|--------------------------------------------------------|-----------|---------------------------|--------------------|
+| | End-to-end latency (see note 1) | User experienced data rate (see note 1) | Service interruption time | End-to-end latency | Data rate | Service interruption time | |
+| Learning data (raw data) at Service robot at initial launch (see note 4) | < 100 ms | UL: < [1.5] Gbit/s
DL: < [500] Mbit/s | | < 10 s | | < [100] ms | < [500] km |
+| Learning data (trained data) at Service robot at initial launch (see note 4) | < 50 ms | UL: < [50] Mbit/s
DL: < [500] Mbit/s | | < 10 s | | < [100] ms | < [500] km |
+| Learning | < 100 ms | UL: 700 | | < 1 s | | < [100] ms | < [200] km |
+
+| | | | | | | | |
+|---------------------------------------------------------------------------------|-----------|--------------------------------------------|--|-----------|--|------------|---------------------------------------------------|
+| data (raw data) at Service robot in routine operation (see note 4) | | Mbit/s
DL: < [500]
Mbit/s | | | | | |
+| Learning data (trained data) at Service robot in routine operation (see note 4) | < 50 ms | UL: 50
Mbit/s
DL: < [500]
Mbit/s | | < 1 s | | < [100] ms | < [200] km |
+| Remote control of robots (type 1) (see note 3) | < [5] ms | UL: < [700]
Mbit/s
DL: [1]
Mbit/s | | < [10] ms | | < [10] ms | < [3] km (aerial, outdoor);
< [500] m (indoor) |
+| Remote control of robots (type 2) (see note 3) | < [20] ms | UL: < [700]
Mbit/s
DL: [1]
Mbit/s | | < [25] ms | | < [100] ms | < [3] km |
+
+NOTE 1: The end-to-end latency and user experienced data rate are dependent on which learning model the UE and agent have selected to use. The expected user experienced data rate varies depending on the task splitting point between UE and the learning agent. The suggested number in this table is based on the maximum possible value (e.g., non-splitting cases or on splitting stage at pooling).
+
+NOTE 2: The range is a rough measure, which may include radio and core network segments, between a Service Robot (as a UE) and the learning agent (including candidate learning agent). For routing operation, the range is typically smaller than that for initial launch of a task/job site.
+
+NOTE 3: For robot control, only two categories are suggested. A refined use of more categories is FFS. Type 1 requires more rigorous KPIs (e.g., helicopter, humanoid robots). This case is not intended to cover more rigorous and/or complicated operational environments such as a use case with a very long communication range and tactile/haptic feedback related use cases demanding ultra-fast delivery of skillssets, e.g., in (or less than) the order of milliseconds.
+
+NOTE 4: In these scenarios, service robots are assumed to have basic robotics mobility. DL (downlink) data rate requirement is characterised by the required upper bound that can often happen sporadically, e.g., when downloading AI/ML models.
+
+## 7.4 Group Performance “Flocking” Use Case
+
+### 7.4.1 Description
+
+A new ‘service enabler’ is introduced that allows a service provider to achieve effective performance for the entire group of devices. The term ‘Flock’ stands for a group that has performance requirements that consider the performance ‘as a team’ as opposed to the ‘total’ or results of the ‘best performers.’
+
+The example of a Flock provided in this use case (an application of this service enabler) is for Synchronous Federated Learning. Please note that “Flocking” is a **general service enabler**. Synchronous Federated Learning is discussed here because (a) it is a concrete application of the “Flocking” service enabler, (b) the topic of this study is model and AI data set communication. To explain and motivate “Flocking” we need an example, and fortunately this application is directly within the scope of the FS\_AMMT study.
+
+Synchronous federated learning involves a set of contributing terminals, as described in clause 7 of this TR. In a federation, a hierarchy exists that provides an effective delegation of work and information. This federation functions as if it were a single (non-federated) system to the extent that the distributed components can operate within the same expectations. For synchronous federated learning some number of the federation’s components lag, these become stragglers. Information and function availability of the whole federation suffers when the performance of individual components fall significantly behind the others as the entire group should complete the iteration.
+
+Synchronous federated learning works best by eliminating bias – allowing diverse users and devices to participate and bring to the learning task diversity of input data, as the users will have different attributes. It is important not to merely
+
+focus on the ‘best performing devices’ in the federation and drop the rest. It may increase the performance in terms of time to iterate the synchronous federated learning task to drop stragglers, but this will reduce the diversity of the data set and introduce bias.
+
+Where group performance is defined by the weakest member (as in the slowest flying bird), we term this a “flock.” The 5GS normally considers performance objectives and QoS for individual communicating terminals. Here, the 5GS QoS objective relates to the entire set of terminals making up the federation, the “flock” of UEs.
+
+### 7.4.2 Pre-conditions
+
+A set of UEs that participated in federated learning exists. These UEs have registered with a PLMN and operate in a federation to perform federated learning tasks.
+
+The federated learning service provider “Avian” organizes the work of these UEs so that repeated iterations of training will occur over time.
+
+It is assumed that the UEs provide federated learning input using the same network resources (e.g. network slice) and that the policy for this network communication is distinct from the policy for other activities that the UE performs. In this way, the network can adjust the QoS policy for federated learning communication for individual UEs without any service impact except to the federated learning service.
+
+### 7.4.3 Service Flows
+
+As the performance and quality of the output of the entire set of UEs is bounded by the performance of the weakest members of the group, Avian provides the 5GS with a policy identifying the reporting interval for which different iterations should conclude. Avian also provides reports on the progress of different UEs as they proceed. The 5GS is then in a position to adjust the QoS policies of some UEs *to allocate more resources* for those UEs that lag, and *less resources* for those that are ahead of the flock. Therefore, the slowest UEs (e.g. at producing a report after an iteration of a federated learning task) achieve an improved performance. The fastest UEs (e.g. also at producing a report after a federated learning task) do not need as much network resources (higher QoS), so the 5GS can reduce the QoS guarantees for these, and thereby saves these resources. The overall result is more efficient for the Synchronous Federated Learning service and for the network operator. The resource allocated to UE is maintained for at least one iteration.
+
+The 5GS can inform Avian of any additional UEs with good communication performance (e.g. due to radio resources) and/or existing UEs whose connection has degraded to a level which is no longer sufficient for FL tasks. This enables Avian to determine when to add new UEs into the flock or remove existing UEs from the flock.
+
+NOTE: While it is clear that the speed with which training occurs and reports are generated by UEs is only partially bounded by communication, it is assumed that the communication resources available to the UE is a significant contributor to the time it requires to complete a training iteration.
+
+When a new UE joins the federation, it will register with Avian. Avian can then notify the 5GS (by means of a standard interface) of this addition. This interface is depicted logically in Figure 7.4.3-1 below.
+
+
+
+```
+graph TD; FLSP[Federated Learning Service Provider] --- 5GS[5G System]; 5GS --- UEs[UE_a, UE_b, UE_c, UE_d, UE_e, UE_f, UE_g, UE_h];
+```
+
+Diagram of the 5G Service Enabler interface for Synchronous Federated Learning. At the top is a box labeled 'Federated Learning Service Provider'. Below it is a box labeled '5G System'. At the bottom are eight boxes labeled UE\_a, UE\_b, UE\_c, UE\_d, UE\_e, UE\_f, UE\_g, and UE\_h, arranged in two rows of four. A line with a circle at the bottom connects the Service Provider to the 5G System, and another line connects the 5G System to the group of UEs.
+
+Figure 7.4.3-1: 5G Service Enabler interface, Example for Synchronous Federated Learning
+
+Similarly, when a UE leaves the federation, the 5GS is notified. This allows the 5GS to modify the policy to balance the QoS policy to achieve the most consistent performance across the involved UEs. During the adjustment of QoS policy, the total communication resource (e.g. total GBR of all members in the flock) can be given a maximum set of resources, (e.g. a GBR aggregate that should not exceed a maximum value).
+
+As the data transmission for Federated Learning is not for regular data services such as video, voice call, webpage browsing, etc., the 5GS needs to have a charging exemption or rewarding to this kind of traffic.
+
+### 7.4.4 Post-conditions
+
+The ‘flock’ of UEs performs consistently.
+
+### 7.4.5 Existing features partly or fully covering the use case functionality
+
+The existing QoS features controlled by the network with reconfigurable policy provide necessary but not sufficient functionality to support the use case.
+
+### 7.4.6 Potential New Requirements needed to support the use case
+
+[P.R.7.4-001] The 5G system shall be able to support ‘aggregated performance’ for a group of UEs where the worst performing member defines the performance of the entire group. E.g. the 5G system could achieve performance for the entire group so as to avoid members achieving either significantly less or more performance than others in the group.
+
+[P.R.7.4-002] The 5G system shall be able determine whether a required QoS for each member in a group can be maintained.
+
+[P.R.7.4-003] The 5G system shall be able to expose QoS information for a group of UEs to an authorized service provider.
+
+**Editor’s Note:** the requirement above is FFS.
+
+[P.R.7.4-004] The 5G core network shall support collection of charging information based on whether the traffic is for AI/ML services.
+
+**Editor’s Note:** it is to check whether it is already covered by existing requirement
+
+# 8 Consolidated potential requirements
+
+## 8.1 KPI for AMMT services
+
+**Editor’s Note:** This section summarizes the available KPI values from the various approved use cases based on v0.3.0. The KPI values in the tables may be corrected/modified aligned with the newly-added use-cases and the updates to the approved use-cases.
+
+In table 8.1-1, 8.1-2 and 8.1-3, only the subset of experienced data rate values which are agreeable for the expected 5G enhancements are captured from the use cases.
+
+- The agreeable upper bound for split AI/ML inference is [1.1Gbit/s] in DL and UL respectively.
+- The agreeable upper bound for AI/ML model downloading is [1.1Gbit/s] in DL. The upper bound is [4Gbit/s] in DL if the downloading is only supported in hotspot coverage.
+- The agreeable upper bound for Federated Learning is [1.1Gbit/s] in DL and UL respectively.
+
+**NOTE:** It might be possible in the selection of members for the federated/distributed learning to prioritize users in good coverage areas. In that case, higher data rates can be possible.
+
+**Table 8.1-1 KPI Table of split AI/ML inference between UE and Network Server/Application function**
+
+| Uplink KPI | Downlink KPI | Remarks |
+|------------|--------------|---------|
+|------------|--------------|---------|
+
+| Max allowed UL end-to-end latency | Experienced data rate | Payload size | Communication service availability | Reliability | Max allowed DL end-to-end latency | Experienced data rate | Payload size | Reliability | |
+|-----------------------------------|-----------------------------------------|--------------|------------------------------------|--------------------|-----------------------------------|---------------------------|------------------|----------------------|-------------------------------|
+| [CPR-001]
2ms | [CPR-002]
1.08Gbit/s
(see note 1) | 0.27 MByte | [CPR-003]
99.999 % | [CPR-037]
99.9% | | | | [CPR-038]
99.999% | Split AI/ML image recognition |
+| [CPR-004]
[100ms] | [CPR-005]
[1.5Mbit/s] | | | | [CPR-006]
[100ms] | [CPR-007]
[150] Mbit/s | 1.5 MByte /frame | | Enhanced media recognition |
+| | | 4.7Mbit/s | | | [CPR-008]
12ms | [CPR-009]
320Mbit/s | 40kByte | | Split control for robotics |
+
+NOTE 1: Only the values corresponding to AlexNet model is captured.
+NOTE 2: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets may take place in order to satisfy the reliability requirement.
+
+Table 8.1-2 KPI Table of AI/ML model downloading
+
+| Max allowed DL end-to-end latency | Experienced data rate (DL) | Model size | Communication service availability | Reliability | User density | # of downloaded AI/ML models | Remarks |
+|-----------------------------------|----------------------------------------------------|-----------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|--------------------------------------------|----------------------------------------------------|
+| [CPR-010]
1s | [CPR-011]
1.1Gbit/s | 138MByte | [CPR-012]
99.999 % | [CPR-039]
99.9% for data transmission of model weight factors;
99.999% for data transmission of model topology | | | AI/ML model distribution for image recognition |
+| [CPR-013]
1s | [CPR-014]
640Mbit/s | 80MByte | [CPR-015]
99.999 % | | | | AI/ML model distribution for speech recognition |
+| [CPR-016]
1s | [CPR-017]
512Mbit/s / [4Gbit/s]
(see note 1) | < 64MByte / 500MByte | | | | Parallel download of up to 50 AI/ML models | Real time media editing with on-board AI inference |
+| [CPR-018]
1s | | 536MByte | | | [CPR-019]
up to 5000~
10000/km2
in an urban area | | AI model management as a Service |
+| [CPR-020]
[500ms] | [CPR-021]
[100 Mbit/s] | [40MByte] | [CPR-022]
99.999 % | | | | AI/ML based Automotive Networked Systems |
+| [CPR-023]
[1s] | | [500]MByte | | | | | Shared AI/ML model monitoring |
+| [CPR-024]
3s | [CPR-025]
450Mbit/s | [CPR-026]
170MByte | | | | | Media quality enhancement |
+
+NOTE 1: 512Mbit/s concerns AI/ML models having a size below 64 MB. 4Gbit/s concerns AI/ML models having a size below 500 MB where the model downloading is only supported in hotspot coverage.
+NOTE 2: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets may take place in order to satisfy the reliability requirement.
+
+Table 8.1-3 KPI Table of Federated Learning between UE and Network Server/Application function
+
+| Max allowed DL or UL end-to-end latency | DL experienced data rate | UL experienced data rate | DL packet size | UL packet size | Communication service availability | Remarks |
+|-----------------------------------------|--------------------------|--------------------------|----------------|----------------|------------------------------------|---------|
+|-----------------------------------------|--------------------------|--------------------------|----------------|----------------|------------------------------------|---------|
+
+| | | | | | | |
+|-------------------|--------------------------|--------------------------|----------|----------|----------------------|---------------------------------------------------------------------------------|
+| [CPR-027]
[1s] | [CPR-028]
1.0Gbit/s | [CPR-029]
1.0Gbit/s | 132MByte | 132MByte | | Uncompressed
Federated
Learning for
image
recognition |
+| [CPR-030]
[1s] | [CPR-031]
80.88Mbit/s | [CPR-032]
80.88Mbit/s | 10Mbyte | 10Mbyte | [CPR-033]
[99.9%] | Compressed
Federated
Learning for
image/video
processing |
+| [CPR-034]
[1s] | [CPR-035]
[1.1Gbit/s] | [CPR-036]
[500Mbit/s] | 10MByte | 10MByte | | Data Transfer
Disturbance in
Multi-agent
multi-device ML
Operations |
+
+## 8.2 Functional requirements for AMMT services
+
+Editor's Note: This section summarizes the available requirements from the various approved use cases based on v18.1.0. The requirements in the tables may be corrected/modified aligned with the newly-added use-cases and the updates to the approved use-cases.
+
+**Table 8.2-1 Functional requirements for AMMT services**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CPR 8.2-1 | Based on operator policy, the 5G network shall provide the means to allow an authorized third-party to monitor the resource utilisation of the network service that is associated with the third-party.
NOTE: Resource utilization in the preceding requirement refers to measurements relevant to the UE's performance such as the data throughput provided to the UE. | PR.5.5-001 | |
+| CPR 8.2-2 | Based on operator policy, the 5G system shall be able to provide an indication about a planned change of bitrate, latency, or reliability for a QoS flow to an authorized 3rd party so that the 3rd party AI/ML application is able to adjust the application layer behaviour if time allows. The indication shall provide the anticipated time and location of the change, as well as the target QoS parameters. | PR.5.5-002 | |
+| CPR 8.2-3 | Based on operator policy, 5G system shall be able to provide the means to predict (to the extent possible) and expose predicted network condition changes (i.e. bitrate, latency, reliability) per UE to the authorized third party. | PR.5.5-003 | |
+| CPR 8.2-4 | Subject to user consent, operator policy and regulatory constraints, the 5G system shall support a mechanism to expose monitoring and status information of an AI-ML session, (e.g. measured data rate/delay and other traffic analytics information), to a 3rd party AI/ML application.
NOTE: such mechanism is needed for AI/ML application to determine an in-time transfer of AI/ML model | PR.6.4-001
PR.6.7-001 | The two PRs are proposing to make 5GS provide information including measured data rate, delay, analytics result, and prediction for communication to 3rd party, for AI model downloading and training. It is proposed to merge the two PRs |
+| CPR 8.2-5 | 5G system shall provide a means to supply event alerting to an authorized 3rd party, together with a predicted time of the event. (e.g., alerting about traffic congestion or UE moving into/out of a different geographical area).
NOTE: A 3rd party AI/ML application may use the prediction information to minimize disturbance in the transfer of learning data and AI/ML model data. | PR.7.3-003 | It is proposed to adopt it with the modification "learning agent -> 3rd party" and rewording |
+| CPR 8.2-6 | The 5G system shall be able to support an authorised 3rd party to change aggregated QoS parameter values associated with a group of UEs, e.g. UEs of a FL group. | PR 7.4-001 | |
+| CPR 8.2-7 | Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to expose information to an authorized 3rd party to support the 3rd party to determine members of a group of UEs, e.g. UEs of a FL group, based upon criteria provided in the request from the 3rd party. | PR 7.4-001 | |
+| CPR 8.2-8 | The 5G system shall be able to expose aggregated QoS parameter values for a group of UEs to an authorized service provider. | PR.7.4-002
PR.7.4-003
PR.7.4-004 | It is proposed to adopt the three potential requirements into CPRs |
+| CPR 8.2-9 | The 5G system shall be able to support collection of charging information for a group of UEs, e.g. UEs of a AI/ML FL group. | PR 7.4-004 | The CPR is changed from the original PR to support the charging for FL group where the member may be dynamically changed. |
+
+# 9 Conclusion and recommendations
+
+Regarding the Feasibility Study on traffic characteristics and performance requirements for AI/ML model transfer in 5GS, the TR analyses use cases of AMMT as follows:
+
+- Use cases on AI/ML operation splitting between AI/ML endpoints:
+ - o Split AI/ML image recognition;
+ - o Enhanced media recognition: Deep Learning Based Vision Applications;
+ - o Media quality enhancement: Video streaming upgrade;
+ - o Split control for robotics;
+ - o Session-specific model transfer split computation operations.
+- Use cases on AI/ML model/data distribution and sharing over 5G system:
+ - o AI/ML model distribution for image recognition;
+ - o Real time media editing with on-board AI inference;
+ - o AI/ML model distribution for speech recognition;
+ - o AI model management as a Service;
+ - o AI/ML based Automotive Networked Systems;
+ - o Shared AI/ML model monitoring;
+ - o Prediction of AI/ML model distribution.
+- Use cases on Distributed/Federated Learning over 5G system:
+ - o Uncompressed Federated Learning for image recognition;
+ - o Compressed Federated Learning for image/video processing;
+ - o Data Transfer Disturbance in Multi-agent multi-device ML Operations;
+ - o Group Performance “Flocking” Use Case.
+
+It is recommended to proceed with normative work, and include the potential new requirements identified by this TR into a new TS. The consolidated potential requirements in Clause 8 are candidates for the normative requirements.
+
+# --- Annex A: Introduction to AI/ML models
+
+## A.1 AI and ML
+
+Artificial Intelligence (AI)/Machine Learning (ML) is being used in a range of application domains across industry sectors, realizing significant productivity gains. In particular, in mobile communications systems, mobile devices (e.g. smartphones, smart vehicles, UAVs, mobile robots) are increasingly replacing conventional algorithms (e.g. speech recognition, machine translation, image recognition, video processing, user behaviour prediction) with AI/ML models to enable applications like enhanced photography, intelligent personal assistants, VR/AR, video gaming, video analytics, personalized shopping recommendation, autonomous driving/navigation, smart home appliances, mobile robotics, mobile medicals, as well as mobile
+
+finance. As forecast by Gartner [44], more than 80% of enterprise IoT projects will include an AI component by 2022, up from only 10% today.
+
+***Artificial Intelligence (AI)*** is the science and engineering to build intelligent machines capable of carrying out tasks as humans do, defined by John McCarthy in 1956. The categorization of AI approaches can be illustrated in figure A.1-1 [25].
+
+
+
+The diagram illustrates the hierarchy of AI/ML approaches. At the top level is 'Artificial Intelligence', which contains 'Machine Learning'. 'Machine Learning' contains 'Brain-Inspired' approaches. 'Brain-Inspired' approaches are divided into 'Spiking' and 'Neural Networks'. 'Deep Learning' is a subset of 'Neural Networks'.
+
+A nested diagram showing the categorization of AI/ML approaches. The outermost layer is 'Artificial Intelligence', followed by 'Machine Learning', then 'Brain-Inspired'. Inside 'Brain-Inspired' are two circles: 'Spiking' and 'Neural Networks'. 'Deep Learning' is shown as a subset within 'Neural Networks'.
+
+Figure A.1-1. Categorization of AI/ML approaches (figure adopted from [25])
+
+Within AI is a large subfield called *machine learning (ML)*, which was defined in 1959 by Arthur Samuel as the field of study that gives computers the ability to learn without being explicitly programmed. Instead of the laborious and hit-or-miss approach of creating a distinct, custom program to solve each individual problem in a domain, a single ML algorithm simply needs to learn, via a process called training, to handle each new problem [25]. Many ML methodologies as exemplified by decision tree, K-means clustering, and Bayesian network have been developed to train the model to make classifications and predictions, based on the data obtained from the real world [19].
+
+## A.2 Deep neural network
+
+Within the ML field, there is an area that is often referred to as brain-inspired computation, which is a program aiming to emulate some aspects of how we understand the brain to operate. Since it is believed that the main computational elements a human brain are 86 billion neurons, the two subareas of brain-inspired computation are both inspired by the architecture of a neuron [25], as shown in figure A.2-1 (a).
+
+Compared to spiking computing approaches, e.g. [3], the more popular ML approaches are using “*neural network*” as the model. Neural networks (NN) take their inspiration from the notion that a neuron’s computation involves a weighted sum of the input values. But instead of simply outputting the weighted sum, a NN applies a nonlinear function to generate an output only if the inputs cross some threshold, as shown in figure A.2-1(a). Figure A.2-1(b) shows a diagrammatic picture of a computational neural network. The neurons in the input layer receive some values and propagate them to the neurons in the middle layer of the network, which is also called a “hidden layer”. The weighted sums from one or more hidden layers are ultimately propagated to the output layer, which presents the final outputs of the network [25].
+
+
+
+(a)
+
+(b)
+
+Diagram (a) depicts a single artificial neuron. Three input lines labeled \$x\_0\$, \$x\_1\$, and \$x\_2\$ enter from the left. Each line is associated with a weight: \$w\_0x\_0\$, \$w\_1x\_1\$, and \$w\_2x\_2\$. These lines converge into a circle labeled "Neuron". Inside the circle, the mathematical operation is shown as $y_j = f\left(\sum w_i x_i + b\right)$ . An output arrow labeled \$y\_j\$ exits the neuron to the right.
+
+Diagram (b) depicts a multi-layer neural network. It consists of three vertical columns of circles (neurons). The first column on the left is labeled "Input Layer" and contains three neurons. The middle column is labeled "Hidden Layer" and contains four neurons. The rightmost column is labeled "Output Layer" and contains two neurons. Lines (representing weights) connect every neuron in one layer to every neuron in the subsequent layer. Specific labels point to a single circle as a "Neuron", a column as a "Layer", and a connecting line as a "Weight".
+
+Figure A.2-1. Architecture of neuron and neural network. (a) shows a single neuron with inputs x0, x1, x2 and weights w0, w1, w2, with the output yj calculated as yj = f(sum(wi\*xi + b)). (b) shows a neural network with an input layer, a hidden layer, and an output layer, with labels for layers, neurons, and weights.
+
+**Figure A.2-1. Architecture of neuron and neural network**
+
+Neural networks having more than three layers, i.e., more than one hidden layer are called *deep neural networks (DNN)*. In contrast to the conventional shallow-structured NN architectures, DNNs, also referred to as deep learning, made amazing breakthroughs since 2010s in many essential application areas because they can achieve human-level accuracy or even exceed human accuracy. Deep learning techniques use supervised and/or unsupervised strategies to automatically learn hierarchical representations in deep architectures for classification [26]. With a large number of hidden layers, the superior performance of DNNs comes from its ability to extract high-level features from raw sensory data after using statistical learning over a large amount of data to obtain an effective representation of an input space [25]. In recent years, thanks to the big data obtained from the real world, the rapidly increased computation capacity and continuously-evolved algorithms, DNNs have become the most popular ML models for many AI applications.
+
+## A.3 Training and inference
+
+*Training* is a process in which a AI/ML model learns to perform its given tasks, more specifically, by optimizing the value of the weights in the DNN. A DNN is trained by inputting a training set, which are often correctly-labelled training samples. Taking image classification for instance, the training set includes correctly-classified images. When training a network, the
+
+weights are usually updated using a hill-climbing optimization process called gradient descent. The gradient indicates how the weights should change in order to reduce the loss (the gap between the correct outputs and the outputs computed by the DNN based on its current weights). The training process is repeated iteratively to continuously reduce the overall loss [25]. Until the loss is below a predefined threshold, the DNN with high precision is obtained.
+
+There are multiple ways to train the network for different targets. The introduced above is supervised learning which uses the labelled training samples to find the correct outputs for a task. Unsupervised learning uses the unlabelled training samples to find the structure or clusters in the data. Reinforcement learning can be used to output what action the agent should take next to maximize expected rewards. Transfer learning is to adjust the previously-trained weights (e.g. weights in a global model) using a new training set, which is used for a faster or more accurate training for a personalized model [25].
+
+After a DNN is trained, it can perform its task by computing the output of the network using the weights determined during the training process, which is referred to as *inference*. In the model inference process, the inputs from the real world are passed through the DNN. Then the prediction for the task is output, as shown in Figure A.3-1. For instance, the inputs can be pixels of an image, sampled amplitudes of an audio wave or the numerical representation of the state of some system or game. Correspondingly, the outputs of the network can be a probability that an image contains a particular object, the probability that
+
+an audio sequence contains a particular word or a bounding box in an image around an object or the proposed action that should be taken [25].
+
+
+
+```
+graph LR; Input[Input image of a tree] -- Input --> Model[AI/ML model inference]; Model -- Output --> OutputText["'tree'"];
+```
+
+Diagram illustrating AI/ML inference. An input image of a tree is processed by an AI/ML model inference block, resulting in the output 'tree'.
+
+**Figure A.3-1. Example of AI/ML inference**
+
+The performance of DNNs is gained at the cost of high computational complexity. Hence more efficient compute engines are often used, e.g. graphics processing units (GPU) and network processing units (NPU). Compared to the inference which only involves the feedforward process, the training often requires more computation and storage resources because it involves also the backpropagation process [10].
+
+## A.4 Widely-used DNN models and algorithms
+
+Many DNN models have been developed over the past two decades. Each of these models has a different “network architecture” in terms of number of layers, layer types, layer shapes (i.e., filter size, number of channels and filters), and connections between layers [25]. Figure A.4-1 presents three popular structures of DNNs: multilayer perceptrons (MLPs), convolution neural networks (CNNs), and recurrent neural networks (RNNs). ***Multilayer perceptrons (MLP)*** model is the most basic DNN, which is composed of a series of fully connected layers [41]. In a fully connected layer, all outputs are connected to all inputs, as shown in Figure A.4-1. Hence MLP requires a significant amount of storage and computation.
+
+
+
+The diagram illustrates an MLP DNN model. On the left, an input image of a green tree is shown. Three arrows point from the image to a gray rectangular box labeled "MLP DNN". Inside the box, there are four layers of neurons, each represented by a circle. The first layer has three neurons, the second has four, the third has three, and the fourth has one. All neurons in adjacent layers are fully connected by lines. An arrow points from the single output neuron to the word "tree", with the word "Output" written above the arrow.
+
+Diagram of an MLP DNN model for image classification.
+
+**Figure A.4-1. MLP DNN model**
+
+An approach to limiting the number of weights that contribute to an output is to calculate the output only using a function of a fixed-size window of inputs. An extremely popular window-based DNN model uses a convolution operation to structure the computation, hence is named as *convolution neural network (CNN)* [25]. A CNN is composed of multiple convolutional layers, as shown in figure A.4-2. Applying various convolutional filters, CNN models can capture the high-level representation of the input data, making it popular for image classification [7] and speech recognition [42] tasks. In recent years, the modern
+
+CNN models have dramatically improved the performance of image classification tasks (e.g., AlexNet [7], VGG network [8], GoogleNet [9], ResNet [18], MobileNet [19]), as shown in figure A.4-3 [25].
+
+
+
+The diagram illustrates a Convolutional Neural Network (CNN) architecture for image classification. It starts with an input image of a tree. This image is processed through three sequential stages: Convolution, Pooling, and Full-connected. The Convolution stage is represented by a blue rectangular block, the Pooling stage by a purple rectangular block, and the Full-connected stage by a vertical column of circles. Arrows indicate the flow of data from the input image through these stages. The final output is a list of classification scores: Tree: 0.7, Tower: 0.1, House: 0.05, and Human: 0.02.
+
+| Class | Score |
+|-------|-------|
+| Tree | 0.7 |
+| Tower | 0.1 |
+| House | 0.05 |
+| Human | 0.02 |
+
+Diagram of a CNN model architecture showing an input image of a tree being processed through Convolution, Pooling, and Full-connected layers to produce classification scores for Tree, Tower, House, and Human.
+
+Figure A.4-2. CNN model
+
+
+
+| Year / Model | Accuracy (Top-5 error) |
+|------------------|------------------------|
+| 2010 | ~28 |
+| 2011 | ~26 |
+| 2012 (AlexNet) | ~16 |
+| 2013 (OverFeat) | ~14 |
+| 2013 (Clarifai) | ~12 |
+| 2014 (VGG) | ~8 |
+| 2014 (GoogLeNet) | ~7 |
+| 2015 (ResNet) | ~4 |
+| Human | ~5 |
+
+Bar chart showing Image classification improvements made by CNN models from 2010 to 2015, compared to human performance. The Y-axis is Accuracy (Top-5 error) ranging from 0 to 30. The X-axis shows years (2010, 2011, 2012, 2013, 2014, 2015) and Human performance. Bars for 2010 and 2011 are gray, representing pre-CNN methods. Bars for 2012 (AlexNet), 2013 (OverFeat, Clarifai), 2014 (VGG, GoogLeNet), and 2015 (ResNet) are blue, representing Deep CNN models. A red arrow points from the 2011 bar to the 2012 bar, labeled 'Large error rate reduction due to Deep CNN'. The Human performance bar is red.
+
+**Figure A.4-3. Image classification improvements made by CNN models (Figure adopted from [25])**
+
+**Recurrent neural network (RNN)** models are another type of DNNs, which use sequential data feeding. The input of RNN consists of the current input and the previous samples. Each neuron in an RNN owns an internal memory that keeps the information of the computation from the previous samples. As shown in figure A.4-4, the basic unit of RNN is called cell, and
+
+further, each cell consists of layers and a series of cells enables the sequential processing of RNN models. RNN models have been widely used in the natural language processing task on mobile devices, e.g., language modelling, machine translation, question answering, word embedding, and document classification.
+
+
+
+The diagram illustrates an RNN model over time steps $t_0, t_1, t_2, \dots, t_i$ . At each time step $t_j$ , an input node $x_j$ (represented by a circle) feeds into a processing block labeled 'Func' (represented by a rectangle). The 'Func' block produces an output node $o_j$ (represented by a circle). The 'Func' blocks are connected sequentially from left to right. A horizontal arrow labeled 'Sequential Input' points from left to right below the input nodes. A horizontal arrow labeled 'Sequential Output' points from left to right above the output nodes. The sequence of time steps is indicated by an ellipsis between $t_2$ and $t_i$ .
+
+Diagram of an RNN model showing sequential input and output processing over time steps.
+
+**Figure A.4-4. RNN model**
+
+***Deep reinforcement learning (DRL)*** is not another DNN model. It is composed of DNNs and reinforcement learning [43]. As illustrated in figure A.4-5, the goal of DRL is to create an intelligent agent that can perform efficient policies to maximize the
+
+rewards of long-term tasks with controllable actions. The typical application of DRL is to solve various scheduling problems, such as decision problems in games, rate selection of video transmission, and so on.
+
+
+
+The diagram illustrates the reinforcement learning architecture. It features two main components: an 'Agent' and an 'Environment'. The 'Agent' is represented by a large rectangle containing a neural network structure with four layers of nodes: an input layer of 3 nodes, two hidden layers of 4 nodes each, and an output layer of 3 nodes. The 'Environment' is represented by a smaller rectangle. The interaction is as follows: an arrow labeled 'State' points from the Environment to the Agent's input layer; an arrow labeled 'Action' points from the Agent's output layer to the Environment; and two arrows labeled 'Reward' and 'State' point from the Environment back to the Agent's input layer.
+
+Diagram of Reinforcement Learning architecture showing Agent, Environment, State, Reward, and Action components.
+
+**Figure A.4-5. Reinforcement learning**
+
+# --- Annex B:
+
+## General principle of split AI/ML operation between AI/ML endpoints
+
+In recent years, the AI/ML-based mobile applications are increasingly computation-intensive, memory-consuming and power-consuming. Meanwhile end devices usually have stringent energy consumption, compute and memory cost limitations for running a complete offline AI/ML inference onboard. Hence many AI/ML applications currently intent to offload the inference processing from mobile devices to internet datacenters (IDC). Nowadays, even photos shot by a smartphone are often processed in a cloud AI/ML server before shown to the user who shot them. However, the cloud-based AI/ML inference tasks need to take the following factors into account:
+
+- 1) Computation pressure at IDCs
+
+As the estimates in [44], by 2021, nearly 850ZB data will be generated by end devices per year, whereas the global IDC traffic can only reach 20.6ZB. That means most of the data can only be left at network edge (i.e. devices and MEC) for AI/ML processing.
+
+## 2) Required data rate and latency
+
+Increasing number of AI/ML applications are requiring a high data rate meanwhile a low latency for communications between devices and the network, e.g. VR/AR, automatic driving, remote-controlled robotics. According to the estimates in [44] on device-initiated traffic, offloading all the data to cloud servers for AI/ML inference would consume excessive uplink bandwidth. This introduces challenging requirements on mobile communications system capacity, including for the 5G system.
+
+## 3) Privacy protection requirement
+
+The sensing/perception data supporting the inference in the cloud server often carry privacy of the end users. Different types of privacy protection problems need to be considered in case of either processing the data at the device or
+
+reporting it to the cloud/edge server. Compared to reporting it to the server, keeping the raw data at the device can reduce the pressure of privacy protection at the network side.
+
+Hence in many cases, the split AI/ML inference over device and network are required, to enable the AI/ML applications with conflicting requirements which are computation-intensive, energy-intensive as well as privacy-sensitive and delay-sensitive. Many references [10-14] have shown that processing AI/ML inference with device-network synergy can alleviate the pressure of computation, memory footprint, storage, power and required data rate on devices, reduce end-to-end latency and energy consumption, and improve the end-to-end accuracy and efficiency when compared to the local execution approach on either side.
+
+The scheme of split AI/ML inference can be depicted in Figure B.1-1. The AI/ML operation/model is split into multiple parts according to the current task and environment. The intention is to offload the computation-intensive, energy-intensive parts to network endpoints, whereas leave the privacy-sensitive and delay-sensitive parts at the end device. The device executes the operation/model up to a specific part/layer and sends the intermediate data to the network endpoint. The network endpoint executes the remaining parts/layers and feeds the inference results back to the device. It should be noted that, in the example in
+
+Figure B.1-1, the final inference result is output by network AI/ML endpoint 2. According to actual use case, the inference result can also be output by other endpoints, e.g. network AI/ML endpoint 1.
+
+
+
+The diagram illustrates a split AI/ML inference process. It begins with an input image of a tree. This image is processed by the 'End device partition (partial AI/ML operation/model)' located on the 'End device' (represented by a mobile phone icon). The output of this partition is 'Intermediate data', which is then passed to the 'Network partition 1 (partial AI/ML operation/model)' located on 'Network AI/ML endpoint 1' (represented by a server icon). The output of this second partition is again 'Intermediate data', which is then passed to the 'Network partition 2 (partial AI/ML operation/model)' located on 'Network AI/ML endpoint 2' (represented by a server icon). The final output of the entire process is the classification result: "tree".
+
+Diagram illustrating split AI/ML inference across an end device and two network endpoints.
+
+Figure B.1-1. Example of split AI/ML inference
+
+The modes for split AI/ML operations between device and network are illustrated in Figure B.1-2. The modes are in general applicable for AI/ML training as well as inference. In this section, we focus on the inference processing. Mode a) and b) are traditional schemes operating the AI/ML inference wholly on one endpoint. Mode c) - g) attempt to split the AI/ML inference or even the model into multiple parts according to the current task and environment, to alleviate the pressure of computation, memory/storage, power and required data rate on both device and NW endpoints, as well as to obtain a better model inference performance on latency, accuracy and privacy protection.
+
+### - Mode a): Cloud/edge-based inference
+
+In this mode (as shown in Figure B.1-2 (a)), the AI/ML model inference is only carried out in a cloud or edge server. The device only reports the sensing/perception data to the server, and does not need to support AI/ML inference operations. The server returns the inference results to the device. The advantage of this mode is limiting the device complexity. One disadvantage is that the inference performance depends on communications data rate and latency between the device and the server. Real-time uploading some perception data (e.g. high-resolution video streaming) requires a stably-high data rate and some AI/ML services (e.g. remote-controlled robotics) requires a stably-low
+
+latency, which are challenging to be guaranteed in 5G system due to different network coverages. And due to the disclosure of the privacy-sensitive data to the network, corresponding privacy protection measurements are required.
+
+### - Mode b): Device-based inference
+
+In this mode (as shown in Figure B.1-2 (b)), the AI/ML model inference is performed locally at the mobile device. The advantage is that, during the inference process, the device does not need to communicate with the cloud/edge server. Another motivation of this mode is preserving the privacy at the data source, i.e. the device, although the privacy protection problem needs also be considered at the device side. The disadvantage is potentially imposing an excessive computation/memory/storage resource to the device. And also pointed out by [10], we cannot assume the device always keep all the potentially-needed AI/ML models onboard. In some cases, the mobile device may need to obtain the AI/ML model from the edge cloud/server, which requires a corresponding downloading data rate from the 5G system, as introduced in Section 7.
+
+### - Mode c): Device-cloud/edge split inference
+
+In this mode (as shown in Figure B.1-2 (c)), an AI/ML inference operation or model is firstly split into two parts between the device and the cloud/edge server according to the current system environmental factors such as communications data rate, device resource, and server workload. Then, the device will execute the AI/ML inference up to a specific part or the DNN model up to a specific layer, and send the intermediate data to the cloud/edge server. The server will execute the remaining part/layers and sends the inference results to the device. Compared to Mode a) and b), this mode is more flexible and more robust to the varying computation resource and communications condition. A key link for this mode is to properly select the optimum split point between device side and network side based on the conditions.
+
+### - Mode d): Edge-cloud split inference
+
+This mode (as shown in Figure B.1-2 (d)) can be regarded as an extension of Mode a). The difference is that the DNN model is executed through edge-cloud synergy, rather than executed only on either cloud or edge server. The latency-sensitive part of an AI/ML inference operation or layers of an AI/ML model can be performed at the edge server. The computation-intensive parts/layers that the edge server cannot perform can be offloaded to cloud server. The device only reports the sensing/perception data to the server, and does not need to support AI/ML inference operations. The
+
+intermediate data are sent from the edge server to the cloud server. A proper split point needs to be selected for an efficient cooperation between edge server and cloud server.
+
+### - Mode e): Device-edge-cloud split inference
+
+This mode (as shown in Figure B.1-2 (e)) is the combination of Mode c) and d). An AI/ML inference operation or an AI/ML model is split over the mobile device, the edge server and the cloud server. The computation-intensive parts/layers of an AI/ML operation/model can be distributed among the cloud and/or edge server. The latency-sensitive parts/layers can be performed on the device or the edge server. The privacy-sensitive data can be left at the device. The device sends the intermediate data outcome from its computation to the edge server. And the edge server sends the intermediate data outcome from its computation to the cloud server. Two split points need to be selected for an efficient cooperation between the device, the edge server and the cloud server.
+
+### - Mode f): Device-device split inference
+
+This mode (as shown in Figure B.1-2 (f)) provides a de-centralized split inference. An AI/ML inference operation or model can be split over different mobile devices. A group of mobile devices can perform different parts of an AI/ML
+
+operation or different DNN layers for an inference task, and exchange intermediate data between each other. The computation load can be distributed over devices meanwhile each device preserves its private information locally.
+
+### - Mode g): Device-device-cloud/edge split inference
+
+Mode g) can be further combined with Mode c) or e). As shown in Figure B.1-2 (g), an AI/ML inference operation or model is firstly split into the device part and network part. Then the device part can be executed in a de-centralized manner, i.e. further split over different mobile devices. The intermediate data can be sent from one device to the cloud/edge server. Or multiple devices can send intermediate data to the cloud/edge server.
+
+
+
+Diagram (a) illustrates a 'Device' (represented by a mobile phone icon) connected via a double-headed vertical arrow to a 'Cloud/edge server' (represented by a cloud containing a server icon). Inside the cloud, there is an 'Online model' represented by a neural network diagram.
+
+Diagram (a) showing a device connected to a cloud/edge server with an online model.
+
+(a)
+
+
+
+Diagram (b) illustrates a 'Device' (represented by a mobile phone icon) connected via a double-headed vertical arrow to a 'Cloud/edge server' (represented by a cloud containing a server icon and a 'Model pool' cylinder). The device itself contains an 'Offline model' represented by a neural network diagram.
+
+Diagram (b) showing a device with an offline model connected to a cloud/edge server with a model pool.
+
+(b)
+
+
+
+Diagram (c) illustrates a 'Device' (represented by a mobile phone icon) connected via a double-headed vertical arrow to a 'Cloud/edge server' (represented by a cloud containing a server icon). The device contains 'Model partition 1' (neural network diagram), and the cloud contains 'Model partition 2' (neural network diagram).
+
+Diagram (c) showing a device with model partition 1 connected to a cloud/edge server with model partition 2.
+
+(c)
+
+
+
+Diagram (d) illustrates a 'Device' (represented by a mobile phone icon) connected via a double-headed vertical arrow to an 'Edge server' (represented by a server icon). The device contains 'Model partition 1' (neural network diagram). The 'Edge server' is connected via a double-headed horizontal arrow to a 'Cloud server' (represented by a cloud containing a server icon), which contains 'Model partition 2' (neural network diagram).
+
+Diagram (d) showing a device connected to an edge server with model partition 1, which is connected to a cloud server with model partition 2.
+
+(d)
+
+
+
+Diagram (g) illustrates a federated learning architecture involving three entities: a Device, an Edge server, and a Cloud server. The Device contains 'Model partition 1'. It is connected via a vertical double-headed arrow to the Edge server, which contains 'Model partition 2'. The Edge server is connected via a horizontal double-headed arrow to the Cloud server, which contains 'Model partition 3'.
+
+Diagram (g) showing a Device connected to an Edge server, which is connected to a Cloud server. The Device contains Model partition 1, the Edge server contains Model partition 2, and the Cloud server contains Model partition 3.
+
+(g)
+
+
+
+Diagram (e) illustrates a federated learning architecture between two devices. 'Device A' contains 'Model partition 1' and 'Device B' contains 'Model partition 2'. They are connected to each other via a horizontal double-headed arrow.
+
+Diagram (e) showing Device A and Device B connected to each other. Device A contains Model partition 1 and Device B contains Model partition 2.
+
+(e)
+
+
+
+Diagram (f) illustrates a federated learning architecture involving two devices and a cloud/edge server. 'Device A' contains 'Device-side model partition 1' and 'Device B' contains 'Device-side model partition 2'. They are connected to each other via a horizontal double-headed arrow. Both devices are also connected via vertical double-headed arrows to a 'Cloud/edge server' which contains 'NW-side Model partition'.
+
+Diagram (f) showing Device A and Device B connected to each other and both connected to a Cloud/edge server. Device A contains Device-side model partition 1, Device B contains Device-side model partition 2, and the Cloud/edge server contains NW-side Model partition.
+
+(f)
+
+**Figure B.1-2. Split AI/ML inference modes over endpoints**
+
+# --- Annex C:
+
+## General principle of AI/ML model/data distribution and sharing over 5G system
+
+For the inference tasks which requires low latency and desires the privacy-sensitive data to be preserved at the UE side, offline AI/ML inference is desired, rather than the cloud-based inference. However, an offline AI/ML model running on mobile devices must have a relatively low computation complexity and a small storage size. An approach to enabling offline DNN models on mobile devices is to compress the model to reduce its resource and computational requirements [27-28, 35, 45]. However, DNN compression will lead to loss of inference accuracy and adaptivity to various tasks and environments. A solution to this challenge is to adaptively select the model for inference from a set of trained models [10]. The model selection
+
+is motivated by the observation that the optimum model for inference depends on the input data and the precision requirement [20][45]. Multi-functional mobile terminals usually need to switch the AI/ML model in response to task and environment variations.
+
+The condition of adaptive model selection is that the models to be selected have been available for the mobile device. However, given the fact that the DNN models are becoming increasingly diverse, and with the limited storage resource in a UE, it is unfeasible to pre-load all candidate AI/ML models on-board. Online model distribution (i.e. new model downloading) or online transfer learning (i.e. partial model updating) is needed. As illustrated in Figure C.1-1, an AI/ML model can be distributed from a NW endpoint to the devices when they need it to adapt to the changed AI/ML tasks and environments.
+
+
+
+The diagram illustrates the process of downloading an AI/ML model over a 5G system. At the top, a cloud labeled "DNN pool" contains several icons representing different neural network models. A solid arrow labeled "Online DNN downloading" points from this cloud to a car and smartphone icon on the left. Above this icon is a neural network diagram labeled "Updated DNN for new task and environment". To the right, another car and smartphone icon is shown with a neural network diagram above it labeled "DNN for current task and environment". A dashed double-headed arrow between the two car/phone icons is labeled "Change of task/environment", indicating the context for the model update.
+
+Diagram illustrating AI/ML model downloading over 5G system. A cloud labeled 'DNN pool' contains various neural network icons. An arrow labeled 'Online DNN downloading' points from the cloud to a car and smartphone icon. Above the car and phone is a neural network icon labeled 'Updated DNN for new task and environment'. To the right, another car and phone icon is shown with a neural network icon above it labeled 'DNN for current task and environment'. A dashed double-headed arrow between the two car/phone icons is labeled 'Change of task/environment'.
+
+Figure C.1-1. AI/ML model downloading over 5G system
+
+The model to be distributed can be determined in two ways: Requested by a device, or controlled by a network server. The condition of the first mechanism is that the device can make the model selection/re-selection decision based on the understanding to the oncoming AI/ML task, environment and the list of the models available at the network server. As shown in Figure C.1-2, a model selector on the device is trained to select the best DNN for different input data.
+
+The model selector is trained to determine the optimum DNN model for a new, unseen input using a set of automatically tuned features of the DNN model input, and taking into consideration the precision constraint and the characteristics of the input.
+
+
+
+```
+graph LR; Input[Input Data] --> FE[AI/ML task/environment feature extraction]; FE --> MS[AI/ML Model selection]; MS --> MD[AI/ML Model downloading]; MD --> MI[AI/ML inference]; MI --> Output[Output]; MI --> FE;
+```
+
+The diagram illustrates a sequential process for AI/ML model selection and downloading. It begins with an input icon (a mountain and a sun), which leads to a rounded rectangle labeled 'AI/ML task/environment feature extraction'. This is followed by a 'AI/ML Model selection' rounded rectangle, which features a small icon of four colored spheres (red, yellow, green, blue) above it. The next step is 'AI/ML Model downloading', represented by a rounded rectangle with a cloud and download arrow icon above it. The final step is 'AI/ML inference', shown as a rounded rectangle. An arrow points from the 'AI/ML inference' block to the right, indicating the output. A feedback loop is shown as a line originating from the top of the 'AI/ML inference' block, extending upwards and then back to the left, pointing towards the 'AI/ML task/environment feature extraction' block.
+
+Flowchart of AI/ML model selection and downloading process
+
+**Figure C.1-2. AI/ML model selection and downloading**
+
+The data rate for downloading the needed models depends on the following factors:
+
+## - Size of the model
+
+This depends on different AI/ML applications. Along with the increasing performance requirements to AI/ML operations, the sizes of the models also keep increasing, although model compression techniques are under improvements.
+
+## - Required downloading latency
+
+This depends on how fast the model needs to be ready at the device. It is impacted by the extent to which the oncoming application can be predicted. Considering the unpredictability of user behaviour and typical waiting time a user can tolerate, the downloading of the AI/ML model needs to be finished in seconds or even in milliseconds. Different from a streamed video which can be played when a small portion is buffered, a DNN model can only be used until the whole model is completely downloaded.
+
+In should be noted that the network-based and split AI/ML inference often requires a high and constant uplink data rate for continuously offloading sensing/intermediate data to the cloud/edge server. On the contrary, AI/ML model distribution mainly requires a high downlink data rate in a burst. This makes model distribution more suitable to the downlink-dominant (e.g.
+
+employing a high DL-to-UL ratio) mobile communications systems or systems with an unstable coverage. Of course the condition is that the mobile device's computation resource can afford the on-board execution of the AI/ML model. If the computation load is beyond the device's capability, the network-based or split inference has to be adopted.
+
+# --- Annex D: General principle of Distributed/Federated Learning over 5G system
+
+With continuously improving capability of cameras and sensors on mobile devices, valuable training data, which are essential for AI/ML model training, are increasingly generated on the devices. For many AI/ML tasks, the fragmented data collected by mobile devices are essential for training a global model. In the traditional approaches, the training data gathered by mobile devices are centralized to the cloud datacenter for a centralized training.
+
+However, an AI/ML model training often requires a large data set and significant computational resources for multiple weight-update iterations. Nowadays, most of the AI/ML model training tasks are performed in the power cloud datacenters since the resource consumption of the training phase significantly overweights the inference phase. In many cases, training a DNN model still takes several hours to multiple days. However, cloud-based training means that the enormous amount of training data should be shipped from devices to the cloud, incurring prohibitive communication overhead as well as the data privacy pressure at the network side [10]. Similar to the split AI/ML inference introduced in Annex B, AI/ML model training tasks can also work in a cloud-device coordination manner. Distributed Learning and Federated Learning are examples in this manner.
+
+In Distributed Learning mode, as shown in Figure D.1-1, each computing node trains its own DNN model locally with local data, which preserves private information locally. To obtain the global DNN model by sharing local training improvement, nodes in the network will communicate with each other to exchange the local model updates. In this mode, the global DNN model can be trained without the intervention of the cloud datacenter [10].
+
+
+
+The diagram shows four end devices arranged in a square: a smartphone at the top left, a security camera at the top right, a robot at the bottom left, and a car at the bottom right. Each device is connected to a central cloud server icon by a double-headed arrow. Additionally, each device is connected to a local neural network icon (represented by a cluster of nodes) by a double-headed arrow, indicating local training or data exchange.
+
+Diagram illustrating Distributed Learning. Four end devices (smartphone, security camera, robot, and car) are arranged in a square, each connected to a central cloud server icon. Each device is also connected to a local neural network icon, representing local training data or models.
+
+**Figure D.1-1. Distributed Learning**
+
+In Federated Learning (FL) mode, the cloud server trains a global model by aggregating local models partially-trained by each end devices. The most agreeable Federated Learning algorithm so far is based on the iterative model averaging [30]. As depicted in Figure D.1-2, within each training iteration, a UE performs the training based on the model downloaded from the
+
+AI server using the local training data. Then the UE reports the interim training results (e.g., gradients for the DNN) to the cloud server via 5G UL channels. The server aggregates the gradients from the UEs, and updates the global model. Next, the updated global model is distributed to the UEs via 5G DL channels. Then the UEs can perform the training for the next iteration.
+
+
+
+The diagram illustrates the Federated Learning (FL) process over a 5G system. At the top, a cloud icon represents the '5G/6G cloud (Updating DNN by Federated averaging)'. Below it, two client devices, each consisting of a car, a robot, a smartphone, and a drone, are shown. Each client device has a local DNN model. The process involves 'Iterative training' on a 'Subset of training data' at each client. This results in a 'Partially-trained DNN with new gradients' which are then sent to the cloud. The cloud performs 'Federated averaging' to produce an 'Updated DNN with new weithts' (misspelled in the original image), which are then sent back to the client devices to update their local models.
+
+Diagram of Federated Learning over 5G system showing a central cloud and two client devices (car, robot, phone, drone) performing iterative training and sending gradients for federated averaging.
+
+Figure D.1-2. Federated Learning over 5G system
+
+The performance requirements for Distributed/Federated Learning are listed below. The requirements to 5G communication links (e.g. data rate, latency, reliability) can be derived from the following requirements.
+
+## - Training loss:
+
+Training loss is the gap between the correct outputs and the outputs computed by the DNN model which indicates how well the trained DNN model fits the training data. Aim of training task is to minimize the training loss. Training loss is mainly affected by the quality of the training data and the efficiency of the training methods, i.e. whether the meaning of training data can be fully and properly explored. For Federated Learning, only when the valuable local training data can be fully learned in the duration of the iteration and the local training updates can be correctly reported to the cloud server within the target duration, the training loss can be minimized.
+
+This implies that the requirements to the devices joining in the training process on the achievable UL data rate, latency and reliability for reporting the trained updates, and the achievable UL data rate, latency and reliability for distributing the model for training in next iteration. And to minimize the training loss with device heterogeneity (in computation and communication performance), training device selection and training configuration are needed before the training is performed in an iteration [31, 48] (will be introduced later in this section). The QoS of the relevant controlling
+
+messages, e.g. for training request, training resource reporting, training device selection, training configuration, and resource allocation for the training updates reporting, also needs to be guaranteed.
+
+## - Training latency:
+
+Training latency is one of the most fundamental performance metrics of AI/ML model training task since it directly influences when the trained model is available for use. Nowadays, cloud-based training often takes several hours to multiple days. The latency of the Distributed/Federated Learning process would take even a longer time if the computation latency or the communication latency is not minimized.
+
+The latency of the Distributed/Federated Learning process is determined by the convergence rate (e.g. number of iterations before the training process converges to a consensus) and the latency of each iteration which consists of computation latency and communication latency. The computation latency depends on the computation/memory resource available on training devices. The communication latency depends on the DL data rate available for model distribution and UL data rate available for trained model updating. The latency of the whole training process is determined by the larger one between the computation latency and the communication latency. Hence the latencies of the computation and communication links need to be cooperatively minimized. If the communication latency cannot
+
+match to the computation latency, the communication link will become the bottleneck and prolong the whole training process.
+
+For synchronous Federated Learning, in each iteration, the training latency is determined by the last device that reports its training update because the federated aggregation can be finished when all needed training updates are correctly gathered. That means the device heterogeneity (in computation and communication performance) will also highly impact the overall training latency. Rather than requiring the UL transmission latency of a specific device, the overall latency required for all training devices to upload the training updates (device-group latency) needs to be defined. And the QoS of the controlling messages for minimizing the device-group latency, e.g. for training request, training resource reporting, training device selection, training configuration, and resource allocation for the training updates reporting, also needs to be guaranteed.
+
+## Energy efficiency:
+
+For Distributed/Federated Learning, both the computation and communication processes consume considerable energy. The Federated Learning architecture and protocol should also consider the power constraints on the training devices and the energy efficiency on device as well as the network side.
+
+## - Privacy:
+
+When training the DNN model by using the data originated at a massive of end devices, the raw data or intermediate data should be transferred out of the end devices. Compared to reporting it to the cloud/edge server, preserving privacy at the end devices can reduce the pressure of privacy protection at network side. For example, Federated Learning is an agreeable approach to avoid uploading the raw data from device to network, as a cloud-based training requires.
+
+# Annex E: Change history
+
+| Change history | | | | | | | |
+|----------------|----------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-09 | SA1#91-e | S1-203150 | | | | TR Skeleton agreed | 0.0.0 |
+| 2020-09 | SA1#91-e | S1-203382 | | | | Agreements in SA1#91-e: S1-203137, S1-203284, S1-203074, S1-203135, S1-2031356, S1-203312, S1-203133, S1-203314, S1-203315, S1-203316, S1-203317, S1-203318, S1-203144, S1-203145, S1-203146, S1-203158 | 0.1.0 |
+| 2020-11 | SA1#92-e | S1-204352 | | | | Agreements in SA1#92-e: S1-204014, S1-204339, S1-204394, S1-204395, S1-204396, S1-204397, S1-204398, S1-204399, S1-204400, S1-204401, S1-204402, S1-204403, S1-204404 | 0.2.0 |
+
+| | | | | | | | |
+|---------|----------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| 2021-03 | SA1#93-e | S1-210303 | | | | Agreements in SA1#93-e: S1-210014, S1-210015, S1-210267, S1-210321, S1-210330, S1-210331, S1-210332, S1-210333, S1-210334, S1-210336, S1-210337, S1-210374, S1-210375, S1-210376, S1-210377, S1-210378, S1-210379, S1-210380, S1-210381, S1-210382, S1-210383, S1-210384, S1-210385, S1-210386, S1-210387, S1-210388, S1-210389, S1-210390, S1-210391, S1-210409, S1-210410 | 0.3.0 |
+| 2021-05 | SA1#94-e | S1-211303 | | | | Agreements in SA1#94-e: S1-211075, S1-211254, S1-211396, S1-211397, S1-211398, S1-211399, S1-211400, S1-211401, S1-211402, S1-211403, S1-211404, S1-211405, S1-211406, S1-211407, S1-211408, S1-211409, S1-211410, S1-211411, S1-211412, S1-211413 | 1.1.0 |
+| 2021-06 | SA#92e | SP-210507 | | | | Raised by MCC to v.2.0.0 for Approval | 2.0.0 |
+| 2021-06 | SA#92e | SP-210507 | | | | Raised by MCC to v.18.0.0 following Approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210507 | | | | Corrected logo (5G->5GA) | 18.0.1 |
+| 2021-09 | SA#93e | SP-211040 | 0001 | 1 | B | FS_AMMT update to Functional requirements for AMMT services | 18.1.0 |
+| 2021-09 | SA#93e | SP-211040 | 0002 | 1 | B | FS_AMMT update to clause 7.4 Group performance Flocking Use Case | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0003 | 1 | D | FS_AMMT update to CPR tables with new format | 18.2.0 |
+
diff --git a/marked/Rel-18/22_series/22878/4495fbec19aac6861f1a0b35c4dc38bc_img.jpg b/marked/Rel-18/22_series/22878/4495fbec19aac6861f1a0b35c4dc38bc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8512436bb247e25c803e22b5f52c0b90eceefe24
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/4495fbec19aac6861f1a0b35c4dc38bc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4c221c5dd77d1e20cc3beb6570a9621f364a8d0d8ba940929f10cc4f838eab9
+size 15921
diff --git a/marked/Rel-18/22_series/22878/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/22_series/22878/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6010a662188280e780718dd474e6a6b94520869b
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1346818d8aa91ee43d887e5a5728f056a89a9775ef7ad6dae8171f4e8348151
+size 56790
diff --git a/marked/Rel-18/22_series/22878/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22878/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d268ebe2e6120b5c25f83822832ba9f91b9b2d6
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4deb1facc0e84ff9f622973e0eb22cfefa24fa44271727910d1641abb6211956
+size 9305
diff --git a/marked/Rel-18/22_series/22878/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22878/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39816bcf7b0c3a418ba429dd197b054a79dd3ca3
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c855236a6afb96f594cd6846c619f00703a978ab9f1155223d5c09411658802a
+size 5639
diff --git a/marked/Rel-18/22_series/22878/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-18/22_series/22878/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d2d7c363b0d21f753ab7b21916b14ee80cb5286
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e01b90bd563a3ea64e398c40be90560a1fcf89025c248975a9afe8473b8cd3c8
+size 51889
diff --git a/marked/Rel-18/22_series/22878/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/22_series/22878/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c842fbed8821efa9dd30a506560dcd89b26af477
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a63f7e8a8c980b30aca1c026ddc58b9538db5b290d443ad167486131373e2d1b
+size 56752
diff --git a/marked/Rel-18/22_series/22878/925f55ce69802b9d3b00546382663ee2_img.jpg b/marked/Rel-18/22_series/22878/925f55ce69802b9d3b00546382663ee2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca3ab3765f5e688990fef1b16a646dd806a52b07
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/925f55ce69802b9d3b00546382663ee2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2358e8c2146c243bc7b0d99127abb25212cc5d27288dcf10fa324345af96279
+size 33908
diff --git a/marked/Rel-18/22_series/22878/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-18/22_series/22878/ddc7460821484f1ae2835c67955c554c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e532cb9443ecdcc4016453cce448db4fb276b340
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/ddc7460821484f1ae2835c67955c554c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcf8b05151f7651e0b5fb3eb270569aaa5689afff4bd02b659f7e39d9930ec36
+size 49907
diff --git a/marked/Rel-18/22_series/22878/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/22_series/22878/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35a98dc2978355944fb39398f1949b4965aaae5f
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eed7535af56df75100d4fbf6018a4ac24d2ec5546ad165c9545b5290354f2cf7
+size 87735
diff --git a/marked/Rel-18/22_series/22878/raw.md b/marked/Rel-18/22_series/22878/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..11a85426290b79b90c54df39a1fca97f1534920c
--- /dev/null
+++ b/marked/Rel-18/22_series/22878/raw.md
@@ -0,0 +1,728 @@
+
+
+# 3GPP TR 22.878 V18.2.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Feasibility Study on 5G Timing Resiliency System (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo.
+
+A GLOBAL INITIATIVE
+
+3GPP logo
+
+## --- **Keywords**
+
+5G, Time, Resiliency
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|----------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Overview..... | 7 |
+| 4.1 Applicability of 5G timing resiliency service in the smart grid sector ..... | 7 |
+| 4.1.1 General ..... | 7 |
+| 4.1.2 Timing Accuracy ..... | 8 |
+| 4.1.3 Timing Resiliency ..... | 9 |
+| 4.2 Applicability of 5G timing resiliency service in the financial sector..... | 12 |
+| 5 Use cases..... | 13 |
+| 5.1 Use case on resilient 5G system time synchronization ..... | 13 |
+| 5.1.1 Description ..... | 13 |
+| 5.1.2 Pre-conditions..... | 14 |
+| 5.1.3 Service flows ..... | 14 |
+| 5.1.4 Post-condition..... | 14 |
+| 5.1.5 Existing feature partly or fully covering use case functionality..... | 14 |
+| 5.1.6 Potential new requirements ..... | 14 |
+| 5.2 Use case on 5G timing resiliency for smart grids ..... | 14 |
+| 5.2.1 Description ..... | 14 |
+| 5.2.2 Pre-conditions..... | 14 |
+| 5.2.3 Service flows ..... | 15 |
+| 5.2.4 Post-conditions ..... | 15 |
+| 5.2.5 Existing feature partly or fully covering use case functionality..... | 15 |
+| 5.2.6 Potential new requirements and KPIs..... | 15 |
+| 5.2.6.1 Potential Requirements ..... | 15 |
+| 5.2.6.2 Potential KPIs ..... | 16 |
+| 5.3 Use case on 5G secure clock signals to devices and application servers ..... | 16 |
+| 5.3.1 Use case description ..... | 16 |
+| 5.3.2 Pre-conditions..... | 16 |
+| 5.3.3 Service flows ..... | 17 |
+| 5.3.4 Post-conditions ..... | 17 |
+| 5.3.5 Existing feature partly or fully covering use case functionality..... | 17 |
+| 5.3.6 Potential new requirements ..... | 17 |
+| 5.4 Use Case on 5G timing resiliency for financial sector..... | 17 |
+| 5.4.1 Description ..... | 17 |
+| 5.4.2 Pre-conditions..... | 18 |
+| 5.4.3 Service flows ..... | 19 |
+| 5.4.4 Post-conditions ..... | 19 |
+| 5.4.5 Existing feature partly or fully covering use case functionality..... | 19 |
+| 5.4.6 Potential new requirements and KPIs..... | 20 |
+| 5.4.6.1 Potential Requirements ..... | 20 |
+| 5.4.6.2 Potential KPIs ..... | 20 |
+| 6 Considerations..... | 20 |
+| 6.1 Potential security considerations..... | 20 |
+| 6.2 Potential charging considerations..... | 21 |
+| 7 Consolidated potential requirements and KPIs..... | 21 |
+| 7.1 Consolidated potential requirements..... | 21 |
+| 7.1.1 General ..... | 21 |
+| 7.1.2 Monitoring and Reporting ..... | 22 |
+| 7.1.3 Service Exposure ..... | 22 |
+
+7.1.4 (void) ................................................................................................................................................................. 22
+
+7.2 Consolidated potential KPIs......................................................................................................................... 22
+
+8 Conclusion and recommendations ................................................................................................................. 23
+
+**Annex A: Change history ............................................................................................................................. 24**
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document identifies additional potential requirements on the 5G system to support time-synchronization services in public and vertical domains, including both the ability to improve resiliency of timing services involving technologies supported by 5G and the ability to act as a backup for GNSS timing services.
+
+The use cases address:
+
+- the use of 5G system in concert with other timing technologies as a resilient timing source for end-users in complement/back-up/alternate to GNSS, and
+- enhancement to the 5G system to enable time synchronization resiliency if GNSS or other timing services are compromised.
+
+# --- 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] National Institute of Standards and Technology (NIST), "Timing Challenges in the Smart Grid", January 2017.
+- [3] 61850-9-3-2016 - IEC/IEEE International Standard - Communication networks and systems for power utility automation – Part 9-3: Precision time protocol profile for power utility automation.
+- [4] IEEE 1588-2019, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems.
+- [5] Used with permission from ABB Distribution Solutions.
+- [6] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
+- [7] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN"
+- [8] ATIS-0900005: "Technical Report on GPS Vulnerability", [https://access.atis.org/apps/group\\_public/download.php/36304/ATIS-0900005.pdf](https://access.atis.org/apps/group_public/download.php/36304/ATIS-0900005.pdf)
+- [9] 3GPP TR 22.867: "Study on 5G Smart Energy and Infrastructure"
+- [10] NPL: "Time Traceability for the Finance Sector, Fact Sheet", version 2.0.
+- [11] BIPM Time Department,
+- [12] Markets in Financial Instruments (MiFID II) - Directive 2014/65/EU [https://ec.europa.eu/info/law/markets-financial-instruments-mifid-ii-directive-2014-65-eu\\_en](https://ec.europa.eu/info/law/markets-financial-instruments-mifid-ii-directive-2014-65-eu_en)
+- [13] Regulatory Technical Standard 25. Level of accuracy of business clocks [https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25\\_en.pdf](https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25_en.pdf)
+
+- [14] Annex to Regulatory Technical Standard 25,
+[https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex\\_en.pdf](https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex_en.pdf)
+- [15] ESMA: “Guidelines on transaction reporting, order record keeping and clock synchronisation under MiFID II”, [https://www.esma.europa.eu/sites/default/files/library/2016-1452\\_guidelines\\_mifid\\_ii\\_transaction\\_reporting.pdf](https://www.esma.europa.eu/sites/default/files/library/2016-1452_guidelines_mifid_ii_transaction_reporting.pdf)
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**holdover:** A clock A, previously synchronized/syntonized to another clock B (normally a primary reference or a Master Clock) but whose frequency is determined in part using data acquired while it was synchronized/syntonized to B, is said to be in holdover or in the holdover mode as long as it is within its accuracy requirements.
+
+NOTE: holdover is defined in [4]
+
+**Holdover time:** the time period that is available to repair the first priority timing source when it is lost (e.g., when the primary GNSS reference is lost). During this period the synchronization accuracy requirement should be guaranteed, e.g., by means of defining multiple synchronization references.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|----------|-----------------------------------------------|
+| BIPM | International Bureau of Weights and Measures |
+| CAT | Consolidated Audit Trail |
+| DS-TT | Device-side TSN translator |
+| ESMA | European Securities and Markets Authority |
+| MiFID II | Markets in Financial Instruments Directive II |
+| MiFIR | Markets in Financial Instruments Regulation |
+| NMS | National Market Systems |
+| NTP | Network Time Protocol |
+| RTS 25 | Regulatory Technical Standard 25 |
+| SCADA | Supervisory control and data acquisition |
+| SNTP | Simple Network Time Protocol |
+| TBS | Terrestrial Beacon System |
+| UTC | Coordinated Universal Time |
+
+# --- 4 Overview
+
+## 4.1 Applicability of 5G timing resiliency service in the smart grid sector
+
+### 4.1.1 General
+
+Power grids are critical to the world economy as most other critical infrastructure including communications depend on them. Electric utilities are transitioning towards smart power grids to enhance efficiency and reliability, with real-time
+
+measurements and control between smart devices in the field with centralized data facilities running intelligent analytics.
+
+The timing solutions for Smart Grid must address a significant list of concerns. Time synchronization is in general considered a key security vulnerability of Smart Grids, and an area of direct relevance to timing resiliency systems and the 5G System is ensuring timing integrity, e.g., providing solutions to the increasing prevalence of satellite signal loss, jamming, and the potential for spoofing [2]. Power utility companies do not want to be dependent only on satellite-based time synchronization due to several factors:
+
+- Interference: Either caused intentionally or by environment (e.g. solar flares).
+- Governmental decision: Public time synchronization service can be disabled or weakened remotely; GPS selective availability as an example.
+- Maintenance: Changing the faulty GPS antenna may take some time.
+- Other: Long downtime time when updating or fixing satellite systems; Galileo downtime of 100h as an example. As a comparison, 24h holdover time has been specified for power systems.
+
+Although there are a large range of applications possible in Smart Grids in need of timing resiliency, the focus here is mainly on power sub-stations where robust time synchronization is needed for e.g., synchro phasor applications. Those are relevant for 5G System-based timing resiliency solutions and simultaneously represent the most demanding application in terms of required time synchronization performance. However, other applications are also mentioned and captured.
+
+### 4.1.2 Timing Accuracy
+
+Precise timing is key to operating the smart power grid. One area relates to controlling the frequency (50Hz/60Hz), while another area relates to providing events with timestamped measurement values, with required accuracies down to a few hundred nanoseconds [2]. Correct timing is a key enabler for communication and orchestration of technologies for accurate and optimal wide area monitoring, protection and control in the power industry [2].
+
+In a typical smart grid architecture, centralized monitoring systems have visibility to events occurring in a distributed hierarchy of substations and distribution systems. Having very accurate timing across the endpoints allows the monitoring systems to readily detect faults, identify the source and extent of impact, and take corrective action in a manner affecting the smallest possible portion of the grid. For such event reporting, a 1ms timing accuracy is sufficient.
+
+#### Sequence of events
+
+- Relays can provide events e.g. to SCADA system for reporting
+- Events from different locations aligned
+- Enables monitoring status of power system and fault analysis
+- For event reporting about 1 ms timing accuracy is acceptable.
+( - Table 1)
+
+| Date | Time | Device | Object Tag | Event |
+|------------|--------------|-------------|-----------------------------------|--------|
+| 12.06.2018 | 15:40:03.378 | J01_Control | DCSXSW12 DCSXSW11 switch position | open |
+| 12.06.2018 | 15:40:03.378 | J01_Control | DCSXSW11 switch position | open |
+| 12.06.2018 | 15:40:03.378 | J01_Control | CBXCBR1 switch position | open |
+| 12.06.2018 | 15:39:53.477 | Testing | MAPGAPC1 OPERATE | True |
+| 12.06.2018 | 15:39:53.378 | J01_Control | DCSXSW12 DCSXSW11 switch position | closed |
+| 12.06.2018 | 15:39:53.378 | J01_Control | DCSXSW11 switch position | closed |
+| 12.06.2018 | 15:39:53.378 | J01_Control | CBXCBR1 switch position | closed |
+| 12.06.2018 | 15:39:53.377 | Testing | MAPGAPC1 START | True |
+| 12.06.2018 | 15:39:43.378 | J01_Control | DCSXSW12 DCSXSW11 switch position | open |
+| 12.06.2018 | 15:39:43.378 | J01_Control | DCSXSW11 switch position | open |
+| 12.06.2018 | 15:39:43.378 | J01_Control | CBXCBR1 switch position | open |
+| 12.06.2018 | 15:39:33.478 | Testing | MAPGAPC1 OPERATE | True |
+| 12.06.2018 | 15:39:33.377 | Testing | MAPGAPC1 START | True |
+| 12.06.2018 | 15:39:33.377 | J01_Control | DCSXSW12 DCSXSW11 switch position | closed |
+| 12.06.2018 | 15:39:33.377 | J01_Control | DCSXSW11 switch position | closed |
+| 12.06.2018 | 15:39:33.377 | J01_Control | CBXCBR1 switch position | closed |
+| 12.06.2018 | 15:39:23.376 | J01_Control | DCSXSW12 DCSXSW11 switch position | open |
+| 12.06.2018 | 15:39:23.376 | J01_Control | DCSXSW11 switch position | open |
+| 12.06.2018 | 15:39:23.376 | J01_Control | CBXCBR1 switch position | open |
+| 12.06.2018 | 15:39:13.476 | Testing | MAPGAPC1 OPERATE | True |
+| 12.06.2018 | 15:39:13.377 | J01_Control | DCSXSW12 DCSXSW11 switch position | closed |
+
+Figure 4.1.2-1: Time stamped events [5]
+
+Timing accuracy is also needed for power system measurements for fault detection in the current phase. Recordings of the phase may be triggered at various points when a fault is detected. Running analysis on multiple time-aligned recordings can provide a clear picture of the extent of impact. For reliable analysis, 1 ms timing accuracy is typically needed across all recordings and is today limited mostly by SNTP time sync methods typically in use.
+
+#### Disturbance recorder
+
+- Recording of power system measurements and binary signals
+- Recording triggered manually or automatically with programmable logic e.g. when a fault detected in power system
+- Used e.g. in fault analysis
+- Typically stored in standardized COMTRADE format with time information
+- Alignment of recordings from different sources is important
+- Required time accuracy 1ms.
+( - Table 1)
+
+![Figure 4.1.2-2: Current disturbance recording [5]. The figure shows three stacked plots of phase currents (I1, I2, I3) over time. Each plot shows a sinusoidal current waveform that experiences a sharp, transient disturbance (a spike and subsequent oscillation) at a specific point in time, indicating a fault event. The y-axis is labeled 'Current (A)' and the x-axis is labeled 'Time'.](925f55ce69802b9d3b00546382663ee2_img.jpg)
+
+Figure 4.1.2-2: Current disturbance recording [5]. The figure shows three stacked plots of phase currents (I1, I2, I3) over time. Each plot shows a sinusoidal current waveform that experiences a sharp, transient disturbance (a spike and subsequent oscillation) at a specific point in time, indicating a fault event. The y-axis is labeled 'Current (A)' and the x-axis is labeled 'Time'.
+
+**Figure 4.1.2-2: Current disturbance recording [5]**
+
+Monitoring the power system frequency also requires timing accuracy for fault detection and resolution. In this case, accuracy between 1 $\mu\text{s}$ to 10 $\mu\text{s}$ is needed to provide accurate correlation of frequency.
+
+#### Power system protection and synchronization
+
+- Power system frequency is e.g. 50 Hz, cycle time $1/50\text{ s} = 20\text{ ms}$
+- 1 deg $\approx 0.056\text{ ms}$ (56 $\mu\text{s}$ )
+- Measurement inaccuracy impacts on e.g. protection performance of differential and impedance based protection functions and may lead to maloperation
+- Measurements from two or more sources must be from the same point of time when aligned
+- Time sync requirement within microseconds.
+( - Table 1)
+
+![Figure 4.1.2-3: Frequency synchronization [5]. The figure contains two phasor diagrams. The left diagram shows three phase voltages (U1, U2, U3) and three phase currents (I1, I2, I3) originating from a common point. The right diagram shows a zero-sequence voltage (U0) and zero-sequence current (I0). Arrows indicate the phase angles between the voltage and current phasors, with labels like '5deg' and '10deg'.](4495fbec19aac6861f1a0b35c4dc38bc_img.jpg)
+
+Figure 4.1.2-3: Frequency synchronization [5]. The figure contains two phasor diagrams. The left diagram shows three phase voltages (U1, U2, U3) and three phase currents (I1, I2, I3) originating from a common point. The right diagram shows a zero-sequence voltage (U0) and zero-sequence current (I0). Arrows indicate the phase angles between the voltage and current phasors, with labels like '5deg' and '10deg'.
+
+**Figure 4.1.2-3: Frequency synchronization [5]**
+
+Finally, the accuracy needed depends on the timing role of the component within the power sub-system. E.g., a PTP sync device within the sub-network generally needs to fulfil the application requirements as discussed above (e.g., down to 1 $\mu\text{s}$ accuracy requirement) whereas a component that is a PTP Grand Master needs to be accurate to a 250 ns requirement [3], specifically, 250 ns are assumed in (section 7.2 [3]) in order to distribute synchronization over a chain of up to 15 transparent clocks while meeting the requirement of 1 $\mu\text{s}$ at the end-device.
+
+### 4.1.3 Timing Resiliency
+
+A simple overview of a power sub-station is provided in Figure 4.1.3-1. In a typical deployment today, the sub-station achieves time synchronization by means of a grandmaster clock that uses the IEEE 1588 Precision Time Protocol (PTP) [4] protocol to synchronize elements inside the power sub-station via an Ethernet connection. The grandmaster clock often uses a GNSS receiver to achieve time synchronization information. To access the GNSS signal, an external GNSS antenna is typically required. The figure shows how time and communication redundancy can be achieved within substation by means defined in IEC 61850-9-3-2016 [3]. However, since the time source (GNSS) illustrated is a single point of failure (e.g. whenever satellite(s) are not available or there is interference), 5G is a candidate resiliency solution.
+
+
+
+Figure 4.1.3-1: Example power sub-system setup leveraging 2x GNSS based clock grandmasters. The diagram shows two GNSS-based clock grandmasters, MCA (Grandmaster 1) and MCB (Grandmaster 2), both with a 250ns accuracy requirement. MCA is connected to a DSC\_9248 switch (A), which is connected to a SCADA system and a Boundary clock 1 (200ns accuracy requirement). MCB is connected to another DSC\_9248 switch (B), which is also connected to a SCADA system and a Boundary clock 2 (200ns accuracy requirement). The two switches are interconnected. Below the switches, a series of Transparent clock devices (50ns accuracy requirement) and other Boundary clocks are connected in a chain. The entire setup is labeled with 'A' and 'B' to indicate the two main synchronization paths.
+
+**Figure 4.1.3-1: Example power sub-system setup leveraging 2x GNSS based clock grandmasters [5]**
+
+The GNSS receiver elements of the clock grandmaster installed in power-subsystems have some desirable characteristics including intrinsic multi-layer jamming and spoofing detection capabilities, e.g., autonomous disruption detection and intelligent protection and control. The timing accuracy requirement of the GNSS receiver is <250 ns according to the grandmaster requirements listed in [4]. This allows sufficient budget for synchronization distribution errors within the power sub-station versus the E2E requirements of the Smart Grid operation (e.g., where every PTP sync device needs to be synchronized to a <1 $\mu$ s accuracy).
+
+Many power sub-systems already have cellular 4G coverage. A 5G System-based timing solution offers multiple potential enhancements, including:
+
+- As a resiliency solution to the GNSS received timing solution if GNSS fails or is compromised, e.g., integrated as alternative radio in each grandmaster clock or as an alternative grandmaster clock with 5G capability in the power sub-system.
+- As an alternative to GNSS use, e.g., integrated with PTP grandmaster clock avoiding installation of external GNSS antenna and receiver at the power sub-station.
+
+These alternatives are illustrated in Figure 4.1.3-2. In both cases, time synchronization may be provided from the 5G System to 5G sync modem by either C-Plane method (e.g., via System Information Broadcast or unicast RRC messaging) or using PTP method according to the power sub-system configuration requirements.
+
+The latter requires also some actions from the 5G System in case time source is lost is missing, e.g., similar to IEC 61850-9-3, clockClass should be dropped when the 5G System is in holdover state. Further, PPS output has significant use-cases and is commonly used today and can be desired property of 5G sync modem.
+
+
+
+Figure 4.1.3-2: 5G integration into system – resilience and alternative mode. The diagram shows two configurations (a and b) for a power sub-station. In (a), a GNSS modem and a 5G sync modem are connected to a PTP Ethernet switch (GM 1) via PPS lines. The 5G sync modem receives UTC time-sync over 5G from a Public 5G network. In (b), a 5G sync modem (GM 2) is connected to a PTP Ethernet switch (GM 1) via PTP. The 5G sync modem receives UTC time-sync over 5G from a Public 5G network.
+
+**Figure 4.1.3-2: 5G integration into system – resilience and alternative mode**
+
+Another key requirement is holdover capability, the ability to continue providing accurate timing service in the event of loss of an external source (e.g., GNSS), for the 5G System. For option (a) in Figure 4.1.3-2 a 24 h holdover capability is automatically supported as this is the case for today's distributed solution where GM1 and GNSS is always one and the same device. 5G modem functionality could be either integrated into the same device as a chip or as an input using option (a) type external modem, e.g., for this case, no specific holdover capability is required from the 5G System. With option (b), holdover capability is mainly determined by the 5G network. Here it is desirable that the 5G sync modem has a holdover capability of at least 5 s to comply with [3] and that the 5G network can support up to 24 h of holdover capability. However, as option (a) can be a solution when 24 h holdover capability is strictly needed for the power utility, this requirement could be more scalable, e.g., allow for wider range of performance of 5G networks and 5G sync modems with exploiting also hold-over capability (stability) of GM1.
+
+High level requirements to the 5G System to support these alternatives are highlighted in Table 4.1.3-1
+
+**Table 4.1.3-1 High level requirements for 5G timing resiliency in smart grid**
+
+| Area | Requirement |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Time Domain | UTC, delivered from network to end-point device in power sub-station. An absolute time difference to GPS/GNSS is acceptable (can be preconfigured) as long as 5G end device provides PPS output which can be used for measuring the difference. |
+| Deployment | Wide area support is needed to reach power sub-systems, e.g., should support full coverage requirements. Mobility is low, e.g., power sub-systems are static structures.
Public Network [5]: - • Minimum density 5 devices per km2
- • Maximum density 100 devices per km2
Private Network [5]: - • Up to 1000 devices per km2
|
+| Mobility | None, synchronization devices are static and vehicles connect to grid in a static location when in need of time synchronization. |
+| Synchronization accuracy | <250-1000 ns for synchro phasor use-cases, e.g., to supplement/replace existing GNSS receiver based solutions 1:1. |
+
+| | |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| (examples) | <1-10 µs for Power system protection and synchronization
<1 ms for Event reporting use-cases, Disturbance recording use-cases |
+| Holdover capability | Up to 24h for 5G network, e.g., the 5G network needs to maintain its ability to synchronize power sub-systems even after general loss or failure of UTC time source.
>5 s for 5G sync modem [3] |
+| Services provided by 5G System | Time resilience service provides 5G clock properties, e.g., clockClass, accuracy, etc to reflect the possible selection of clock source e.g., during GNSS unavailability.
When acting as a backup or replacement time source, the 5G System provides secure timing service to UEs and application servers. |
+
+## 4.2 Applicability of 5G timing resiliency service in the financial sector
+
+For financial markets, the ability to verify continuously when events take place, i.e., time traceability, is fundamental to enable regulatory oversight and analyse the order in which trades are placed (e.g. accurate time stamps are used to settle disagreements and to prevent fraud). Market participants may execute orders on stocks in seconds or microseconds depending on the type of trading activity (e.g., high-frequency algorithmic, voice trading systems, human intervention, concluding negotiated transactions, etc). Financial markets are distributed systems; therefore, a common regulated timekeeping system can only be done if every market participant at each end point of the system involved in the transaction maintains an accurate clock.
+
+There are several means to access UTC time such as using an atomic clock, NTP servers, GNSS signal, or UTC(k) delivery over fiber, where UTC(k) is a realisation of UTC maintained by the contributing institute (e.g., NPL, NIST) identified by k. The 5G system can be operate in collaboration with or as backup to other timing solutions used already by financial markets to comply with financial directives for timekeeping. As illustrated in Figure 4.2-1, the 5G system can be integrated as another time source within the clock distribution infrastructure of the financial customer.
+
+
+
+Figure 4.2-1: Example of time resilience use case for financial markets. The diagram shows a 'Firm / business location A' containing 'Trading desks' and a 'Brokerage data center'. These are connected to a 'Clock distribution' unit which includes a '5G sync modem', 'GNSS modem', and 'SW-NTP HW-PTP module'. The '5G sync modem' is connected to a 'Public 5G network' via a base station. The 'Public 5G network' is connected to a 'DN' (Data Network) via 'PTP, NTP over Fiber/ETH'. The 'DN' is connected to a 'Stock exchange data center' (Market). A 'GNSS' satellite is shown providing signals to the 'GNSS modem' and the 'Public 5G network'. Dashed lines indicate the flow of time information from the GNSS satellite through the 5G network and DN to the Stock exchange data center, and also from the Stock exchange data center back to the GNSS satellite.
+
+**Figure 4.2-1 Example of time resilience use case for financial markets**
+
+Financial regulations for time source and time dissemination require the market participants must provide traceability back to UTC. This requires the time information sent to financial exchanges should be measured and verified at every link in the chain, i.e. from UTC generated at the BIPM (global 'paper' time scale [11]) up to the timestamping engine within the financial customer domain. Depending on the time source and distribution method the financial customer has, the traceability to UTC to comply with the regulations is achieved in different ways. For example (for more information see [10]):
+
+- If GNSS satellite signals are used, these signals alone do not readily provide traceability to UTC, but users can demonstrate traceability by obtaining GNSS monitoring bulletins from one of the regional UTC(k) timing centres. In this case, the end user will use these bulletins in addition to perform calibration and monitoring of the GNSS receiver equipment to demonstrate traceability to UTC.
+- If services for time delivery over fibers are used (e.g., as delivered by a national metrology institutes), the UTC is disseminated over managed fiber links. The traceability to UTC is maintained using PTP to distribute the time
+
+and continuously monitoring and audit the provision point to ensure the agreed level of accuracy defined in the service SLA. Note: this option may not be generally available.
+
+The 5G system could follow similar approaches when applied in this use case (Figure 4.2-2 illustrates the two approaches):
+
+- a) The 5G system provides traceability to UTC up to the DS-TT: In this approach, the 5G system needs to continuously monitor and audit each link within the time distribution chain within the 5G system domain. The UTC traceability is certified up to the provision point at the DS-TT. Therefore, monitoring, calibration, and certification functionalities are required at the DS-TT. Two alternatives can be considered:
+ 1. The 5G system supports these new functionalities including the required mechanisms in the standard.
+ 2. Proprietary solutions are used in collaboration with the 5G system. For example, a client for the service of time delivery over fiber is installed within the DS-TT to combine NPL service and 5G wireless time distribution to provide traceability to UTC.
+- b) The 5G system does not provide traceability to UTC: Similar to GNSS signal delivery described before, the 5G system is not responsible of monitoring, calibrating or documenting evidence for traceability to UTC, the financial customer is taking care of these functionalities.
+
+
+
+The diagram illustrates the UTC(k) time distribution chain. It starts with a GNSS constellation providing signals to a GNSS Receiver. Two UTC sources, UTC(k1) and UTC @ BIPM, are also shown. The GNSS Receiver outputs UTC(k2) via a 'UTC(k2) delivery over fiber' to a gNB. The gNB is part of the '5GS domain'. A dashed line connects the gNB to a UE/DS-TT. At the UE/DS-TT, there are two calibration points, C\_a and C\_b, and two monitoring points, M\_a and M\_b. The UE/DS-TT connects to an 'Internal distribution' block, which contains 'Transfer protocol' and 'Physical layer' layers. Below this block is a monitoring point M, labeled 'Point of compliance with financial regulation'. The 'Internal distribution' block connects to a 'Trading server' in the 'Financial customer domain'. The Trading server contains 'Transfer protocol', 'NIC', 'Network stack', and 'Timestamping engine' layers. Below the Trading server is another monitoring point M. A legend on the right indicates:
+
+
+- Solid line: Wired interface
+- Dashed line: Wireless interface
+- Yellow circle: Calibration point (x indicates the approach a or b)
+- Blue circle: Monitoring point (x indicates the approach a or b)
+
+Figure 4.2-2: UTC(k) time distribution with 5G system indicating the traceability chain. The diagram shows the flow of time from GNSS constellations and UTC(k1) sources through a 5G system (gNB, UE/DS-TT) to a financial customer domain (Internal distribution, Trading server). It highlights calibration points (C\_x) and monitoring points (M\_x) within the 5G domain and at the point of compliance with financial regulation.
+
+Figure 4.2-2 UTC(k) time distribution with 5G system indicating the traceability chain (modified from source [10])
+
+# 5 Use cases
+
+## 5.1 Use case on resilient 5G system time synchronization
+
+### 5.1.1 Description
+
+Many 5G systems rely on reference precision timing signals for network synchronization in order to operate. Today, 5G networks generally rely on GNSS for accurate reference time and frequency. This dependency has resulted in vulnerabilities for these systems in the event of GNSS jamming/interference, data or measurement spoofing of GNSS signals, environmental conditions and/or anomalies.
+
+This use case describes how 5G systems may maintain time synchronization in the event of a loss or degradation of GNSS reference timing.
+
+### 5.1.2 Pre-conditions
+
+The 5G system receives GNSS precision timing signals for network synchronization.
+
+### 5.1.3 Service flows
+
+1. The 5G system maintains time synchronization from a single GNSS timing source.
+2. A GNSS service degradation or outage takes place.
+3. The 5G system detects primary GNSS reference timing signals are no longer viable.
+4. The 5G system receives accurate timing signals from an independent timing source, e.g. Terrestrial Beacon System [7] [8], which can offer a timing alternative to GNSS.
+
+### 5.1.4 Post-condition
+
+The 5G system maintains accurate time synchronization during GNSS reference time service degradation.
+
+### 5.1.5 Existing feature partly or fully covering use case functionality
+
+Since Release 15, RAT-independent positioning technologies that leverage precision timing signals have been enabled in 5G systems, e.g. TBS/MBS [7]. Similar to GNSS, these technologies support positioning, navigation and timing (PNT) applications, while also being able to operate independently from GNSS. The timing features of these technologies may be leveraged to maintain reliable 5G time synchronization in the event of a degradation or loss of GNSS timing signals.
+
+### 5.1.6 Potential new requirements
+
+[PR 5.1.6-1] The 5G system shall be able to receive accurate timing signals from one or more independent timing source(s), which can offer a timing alternative to GNSS, e.g. TBS/MBS [7] [8], Sync over Fiber [7].
+
+[PR 5.1.6-2] The 5G system shall be able to detect when GNSS reference timing signals are no longer viable for network time synchronization.
+
+[PR 5.1.6-3] The 5G system shall be able to maintain accurate time synchronization as appropriate for the supported applications in the event of degradation or loss of GNSS timing signals.
+
+[PR 5.1.6-4] The 5G system shall be able to collect charging information based on the timing source (e.g., the source in use, start and stop of source usage).
+
+## 5.2 Use case on 5G timing resiliency for smart grids
+
+### 5.2.1 Description
+
+The focus for this use-case description is power sub-stations where robust time synchronization is needed for e.g., synchro phasor and other Smart Grid applications.1
+
+### 5.2.2 Pre-conditions
+
+Power sub-systems use wireless means to achieve time synchronization, as is the case today leveraging GNSS receiver capabilities. In today's power sub-system, the timing resiliency is based on e.g., having multiple grandmasters leveraging multiple GNSS receivers. In this use case the 5G system is used as a supplement to, e.g., integrated as alternative radio in the grandmaster clock or as an alternative grandmaster clock with 5G capability in the power sub-system, or alternative to the GNSS, e.g., integrated with PTP grandmaster clock avoiding installation of external GNSS antenna and receiver at the power sub-station.
+
+In this use case, the smart grid is subscribed to and authorized to use the 5G timing resiliency service to ensure reliable timing signals are always available. The 5G timing resiliency service monitors the accuracy and availability of timing
+
+signals from a designated timing source and is able to provide an alternate source (e.g., 5G holdover capacity, atomic clock) in case of failure in the primary source. An SLA may be in place to establish the primary and any alternate timing sources that can be used.
+
+### 5.2.3 Service flows
+
+This section should also describe how the timing resiliency is enhanced when the 5G system is used in conjunction with the GNSS, how the system is notified of a failure of GNSS, how the 5G system picks up the slack to keep the system running smoothly in the absence of GNSS. The UEs are preconfigured to enable the provision of time synchronization service from the 5G system. In addition to the initial pre-configuration the UEs may have, additional information may be used for dynamically configuring the management of the 5G system time synchronization network within the smart grid system.
+
+The configuration of the smart grid system includes timing service from GNSS with resiliency support provided by the 5G system. Based on the 5G time resilience requirements, the time distribution method used, and type of time synchronization device connected to the UE (e.g., DS-TT), the 5G system may configure different network entities (i.e., gNBs, UEs/DS-TTs, UPFs/NW-TTs) and the behaviour when an issue is detected (e.g., notification towards the UE or application, back-up configuration).
+
+The 5G system detects that the GNSS is experiencing a problem (e.g., loss of satellite access, detection of inconsistent timing information).
+
+The 5G system communicates the loss of GNSS to UEs or applications subscribed to the timing resilience service. Additionally, the 5G system may indicate the UEs should use the timing service provided by the 5G system until further notice instead of GNSS signal. The 5G system is configured to provide an accurate timing service for a specified holdover time. Depending on the detected problem and the impacted area, the 5G system may reconfigure its own network to ensure the distribution of an accurate timing service to the UEs.
+
+The 5G system provides timing information to the UEs using a secure mechanism.
+
+The UEs are able to verify the integrity and accuracy of the timing information provided by the 5G system
+
+The 5G system continues to monitor for a return to service by the GNSS. When the GNSS service recovery is detected, the 5G system informs the UEs or application subscribed to the resilience timing service that they can again receive GNSS timing information.
+
+### 5.2.4 Post-conditions
+
+The Smart Grid can use 5G system as a resiliency backup to their GNSS receiver based (or wired) time synchronization systems to improve availability and reliability of the time synchronization. Alternatively, existing GNSS receiver-based solutions may be replaced with a 5G system-based solution where it improves efficiency and/or reliability.
+
+### 5.2.5 Existing feature partly or fully covering use case functionality
+
+Many 5G system features specified in Rel-16 and expected in Rel-17 will be required for the use-case:
+
+- Time synchronization to UTC leveraging 5G system C-Plane and/or U-Plane
+- Support for IEEE 1588 PTP
+- Propagation delay compensation, to ensure that time synchronization can be conducted accurately across wide area deployments needed for power sub-station support
+- Exposure framework supports time synchronization based on the needs of the service
+
+### 5.2.6 Potential new requirements and KPIs
+
+#### 5.2.6.1 Potential Requirements
+
+[PR 5.2.6.1-1] The 5G system shall monitor for timing source failure.
+
+[PR 5.2.6.1-2] The 5G system shall be able to indicate to devices (e.g., UEs, applications) that they need to use an alternate time source (e.g., use 5G system with internal holdover capability or an alternate source, e.g. atomic clock, Sync over Fiber, TBS), taking into account the holdover capability of the devices.
+
+[PR 5.2.6.1-3] The 5G system shall support a holdover capability (e.g., maintaining required accuracy to UTC) of up to 24h.
+
+[PR 5.2.6.1-4] The 5G system shall be able to detect when a timing source fails or is restored for network time synchronization.
+
+[PR 5.2.6.1-5] The 5G system shall be able to collect charging information per UE for use of a timing resiliency service (e.g., start/stop time and source used by a UE, timing service used by UE, holdover capability of the service).
+
+[PR 5.2.6.1-6] The 5G system shall be able to collect charging information on 5G system timing resiliency service (e.g., service KPIs, holdover capability, number of UEs using the service).
+
+#### 5.2.6.2 Potential KPIs
+
+**Table 5.2.6.2-1: Timing resiliency service performance requirements for 5G System**
+
+| Use-case | Holdover Time | Sync Target | Sync accuracy | Service area | Mobility | Remarks |
+|------------------------------------------|---------------|--------------|--------------------------------|----------------------|----------|----------------------------------------------------------------------------------------------------------------|
+| Power grid (5G network) | Up to 24 hour | UTC (note 1) | <250ns-1000ns [3], [9] (note2) | < 20 km 2 | low | When 5G System provides direct PTP Grandmaster capability to sub-stations |
+| Power grid (time synchronization device) | >5 s | UTC (note 1) | <250ns-1000ns [3], [9] (note2) | < 20 km 2 | Low | When 5G sync modem is integrated into PTP grandmaster solution (with 24h holdover capability) at sub-stations) |
+
+Note 1: A different synchronization target is acceptable as long as the offset is preconfigured when an alternatively sourced time differs from GNSS. In this case, a 5G end device shall provide PPS output which can be used for measuring the difference.
+
+Note 2: Use case [New] in [9] illustrates the different accuracy measurements based on different configurations needed to support the underlying requirements from IEC [3]. The range is between 250 ns and 1000 ns. The actual requirement depends on the specific deployment.
+
+## 5.3 Use case on 5G secure clock signals to devices and application servers
+
+### 5.3.1 Use case description
+
+This use case describes the need for secure clock signals to be made available to devices and application servers in a reliable manner by a 5G timing resiliency service. The clock signals may be used for timing synchronization in a variety of applications, such as highly sensitive industrial IoT applications, Power grid, commercial banking and stock trading platforms. All these application domains are highly time sensitive and provide critical infrastructure. As such, these domains may be subject to attacks by spoofing the clock source. To prevent such attacks, in all these scenarios, the clock signals can be accepted only if they are authenticated to be genuine without any manipulation by an external source. Hence it is essential that there is a means to verify the authenticity and integrity of these clock signals.
+
+### 5.3.2 Pre-conditions
+
+Devices and application servers connecting to a 5G system providing a 5G timing resiliency service are expected to go through the 5G authentication process. As part of 5G authentication, the subscription records for these devices are verified and they are authorized for service. During this process, the devices also learn to generate the application specific keys. Hence when these devices invoke the 5G timing resiliency service, and receive the clock signals, it is possible to verify the authenticity of the clock server as well as verify the integrity of the clock signals.
+
+### 5.3.3 Service flows
+
+The 5G timing resiliency service needs to support multiple granularity and accuracy KPIs based on what these clock signals provided by the 5G system are used for. For example, there can be premium service with high accuracy and redundancy, whereas ordinary service may be just time of the day up to minutes. Hence the clock signals need to be made available based on the service subscription.
+
+**Table 5.3.3-1: Clock granularity examples**
+
+| Timing Service type | Application | Clock Granularity |
+|---------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------|
+| Premium timing service | Industrial controls | Highly accurate with nano second, microsecond granularity with redundancy |
+| Commercial timing service | Commercial banking applications | Medium granularity up to seconds. |
+| Regular timing service | Regular Time of the day | Medium granularity up to seconds. |
+| Dedicated timing service | Clock signals with application specific format and frequency | Dedicated granularity and frequency |
+
+### 5.3.4 Post-conditions
+
+The UEs connected to 5G system are mutually authenticated and authorized for the 5G timing resiliency service. The UEs such as industrial precision robots requiring clock signals have a subscription for timing service. The 5G system is able verify the identity of the UE and authorize it for a timing service with the precise granularity needed. The UE, after completing the authentication and authorization, is able to invoke the timing service either through a specific API or a messaging interface. The UE is able to authenticate the clock server (source of clock signal) as genuine or not. If the UE finds that the clock server is failing the authentication verification, the UE does not accept the timing signals. The UE is also able to verify the integrity of clock signals received. If the integrity check fails, the UE doesn't accept the signals.
+
+Similarly, an application server also is able to connect to the 5G system. To receive required clock signals provided by the 5G system, the application server may be connected to the 5G system either over a wireless link or a wireline interface.
+
+### 5.3.5 Existing feature partly or fully covering use case functionality
+
+Currently TS 22.104 [6] has requirements on timing which provide the base for additional requirements for a timing service.
+
+### 5.3.6 Potential new requirements
+
+[PR 5. 3.6-1] The 5G system shall support a mechanism to verify authorization of a 3rd party application server to use a 5G timing resiliency service.
+
+[PR 5.3.6-2] The 5G system shall support a mechanism to provide timing service to UEs and application servers with specific KPIs (e.g., accuracy, interval, coverage area).
+
+[PR 5.3.6-3] The 5G system shall support a mechanism for a 3rd party application server to request a timing service with specific KPIs (e.g., accuracy, interval, coverage area).
+
+## 5.4 Use Case on 5G timing resiliency for financial sector
+
+### 5.4.1 Description
+
+The focus for this use-case description is financial sector. Markets and market participants are highly interconnected, absolutely accurate time stamping is essential to determine exactly who made what trade, and precisely when. Market
+
+participants may execute orders on stocks in seconds or microseconds depending on the type of trading activity (e.g. high-frequency algorithmic, voice trading systems, human intervention, concluding negotiated transactions, etc). Without a reliable common reference time to provide synchronized time stamps, transactions across locations and stock exchanges are impossible to audit or to detect wrongdoing. To achieve a more regulated timekeeping system, the European Securities and Markets Authority (ESMA) has issued new rules in support of the MiFID II (Markets in Financial Instruments Directive II) regulations [12]. The Regulatory Technical Standard (RTS) 25 is a part of the standards developed by ESMA in the context of MiFID II. RTS 25 defines standards for clock synchronization [13]. Similar to MiFID II, U.S. Securities and Exchange Commission (SEC) introduced Rule 613 and the Consolidated Audit Trail (CAT) to accurately track all activity throughout the U.S. markets in National Market Systems (NMS) securities. Rule 613 requires electronic trading business clocks to be accurate to the National Institute of Standards and Technology (NIST) clocks (i.e. 50 ms for automated orders, 1s for manual orders). MiFID II generally has the strictest requirements when it comes to time stamping (i.e. $\leq 100\mu\text{s}$ for high frequency algorithmic trading, $\leq 1\text{s}$ for voice trading, human intervention, or concluded negotiated transactions, and $\leq 1\text{ms}$ for other type of trading activities), and is of relevance also to foreign regions as foreign regimes need to have regulations of comparable quality in order for companies in that regime to transact with European entities.
+
+To ensure MiFID II compliance, market participants must have the ability to demonstrate where the timestamp is applied and that it remains consistent, it is not enough just having an accurate time source. Satellite signals or systems that provide direct traceability to the UTC time issued and maintained by a timing centre listed in the BIPM Annual Report on Time Activities are considered as acceptable as time sources. However, if satellite signals are used, the ESMA states the users should be aware of the relevant risks with those signals and must mitigate them [15]. In addition to document and monitor their timing network architecture, market participants also need to consider impacts MiFID II compliance brings in their system such as the security and integrity of the reports collected (e.g. access management that ensures only a certain group of nodes can access the data, authentication to protect the data, data integrity to maintain the consistency and accuracy of the data).
+
+### 5.4.2 Pre-conditions
+
+MiFID II and MiFIR regulation requirements mandate firms and venues to time stamp events accurately to UTC and to an appropriate level. Particularly, article 4 of RTS 25 [13] also states:
+
+*Operators of trading venues and their members or participants shall establish a system of traceability to UTC. They shall be able to demonstrate traceability to UTC by documenting the system design, functioning and specifications. They shall be able to identify the exact point at which a timestamp is applied and demonstrate that the point within the system where the timestamp is applied remains consistent. Reviews of the compliance with this Regulation of the traceability system shall be conducted at least once a year.*
+
+In this use case, both the time synchronization at the end devices (to enable the time stamp accuracy required) and how the time synchronization is distributed to these devices (to enable UTC traceability) are crucial to comply with MiFID II regulation. The market participant is subscribed to and authorized to use the 5G timing resilience service to receive accurate absolute time, directly traceable to UTC, resilient and worldwide available. The 5G timing distribution and resilience service ensures time traceability through either real-time monitoring (e.g., the continuous comparisons of the clock to ensure the device is working properly) or offline (e.g. calibration of the equipment) handling of the following:
+
+- A continuous chain of comparisons with known uncertainties.
+- Time equipment calibration.
+- Continuous monitoring to demonstrate compliance and correct functioning.
+- Calibration evidence and monitoring results to be archived.
+
+For UTC traceability, each link involved in the time dissemination chain from the reference time scale UTC up to the point of provision must be documented, as illustrated in Figure 5.4.2-1. An SLA will be in place to establish the time synchronization accuracy and traceability requirement to UTC.
+
+The time synchronization accuracy provided by the 5G System domain at the output of the 5G Device will be a suitable portion of the target requirement applicable at the application layer of the Financial customer domain, as an example in order to meet $100\mu\text{s}$ , the 5G System domain could provide at least $10\mu\text{s}$ accuracy.
+
+
+
+Figure 5.4.2-1: UTC time distribution chain to the financial customer. The diagram shows a timeline divided into two domains: 5G System domain and Financial customer domain. The 5G System domain includes UTC (R) BIPM, UTC(k), 5G Grandmaster clocks (gNB or NW-TT/UPF), and 5G device (DS-TT/UE). The Financial customer domain includes Financial customer internal distribution (NTP/PTP/pps) and Timestamping engine. A dashed line separates the two domains. A downward arrow from the 5G System domain to the Financial customer domain is labeled '5G certified SLA on traceability to UTC'. Another downward arrow from the Financial customer domain is labeled 'Traceability requirement for MiFID II compliance'. A blue double-headed arrow on the right is labeled 'Increasing uncertainty'. The entire timeline is labeled 'Time distribution chain'.
+
+Figure 5.4.2-1: UTC time distribution chain to the financial customer
+
+### 5.4.3 Service flows
+
+1. The 5G system and the market participant establish an SLA for the 5G timing resilience including UTC traceability and required accuracy of the time distribution service.
+2. The 5G system provides UTC timing information to the UEs using the 5G timing resilience service.
+3. The 5G system maintains time synchronization to UTC time scale at the UE, monitors the time distribution and ensures UTC traceability.
+4. The 5G system provides UTC traceability evidence to subscribed applications.
+
+### 5.4.4 Post-conditions
+
+The financial sector can use 5G system as a solution to access UTC and comply with MiFID II requirements. The 5G system can be used in collaboration with or as backup to other timing solutions used already by financial markets such as atomic clocks, NTP servers, GNSS, UTC(k) delivery over fiber (e.g. NPLTime or similar services).
+
+### 5.4.5 Existing feature partly or fully covering use case functionality
+
+Many 5G system features specified in Rel-16 and expected in Rel-17 will be required for the use-case:
+
+- Time synchronization of UE to UTC leveraging 5G system C-Plane and/or U-Plane
+- Time distribution from device to local data network using Ethernet, PPS, etc
+- Support for IEEE 1588 PTP
+- Propagation delay compensation
+- Exposure framework supports time synchronization based on the needs of the service
+
+### 5.4.6 Potential new requirements and KPIs
+
+#### 5.4.6.1 Potential Requirements
+
+[PR 5.4.6.1-1] The 5G system shall support a mechanism to determine the time uncertainty of the 5G time synchronization.
+
+[PR 5.4.6.1-2] The 5G system shall support mechanisms to monitor different time sources and adopt the most appropriate.
+
+[PR 5.4.6.1-3] The 5G system shall support a mechanism to report time resiliency information (e.g., divergence from UTC, time uncertainty) to 3rd party applications.
+
+[PR 5.4.6.1-4] The 5G system shall be able to collect charging information per application, including 3rd party application (e.g., timing resiliency service KPIs, holdover capability, number of UEs using the service, timing source).
+
+[PR 5.4.6.1-5] The 5G system shall support a mechanism to monitor and verify authenticity of the timing source, where supported by the time source.
+
+[PR 5.4.6.1-6] The 5G system should verify the availability of the external time sources.
+
+#### 5.4.6.2 Potential KPIs
+
+**Table 5.4.6.2-1: Level of accuracy for members or participants of a trading venue [13, 14]**
+
+| Type of trading activity | Maximum divergence from UTC | Granularity of the timestamp (note 1) |
+|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------------|
+| Activity using high frequency algorithmic trading technique | 100 $\mu$ s | $\leq 1\mu$ s |
+| Activity on voice trading systems | 1s | $\leq 1$ s |
+| Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading | 1s | $\leq 1$ s |
+| Activity of concluding negotiated transactions | 1s | $\leq 1$ s |
+| Any other trading activity | 1ms | $\leq 1$ ms |
+
+Note 1: Only relevant for the case where the time synchronization service assists in configuring the required granularity for the timestamp (for direct use), otherwise it will be configured separately as part of the financial transaction timestamp process.
+
+# 6 Considerations
+
+## 6.1 Potential security considerations
+
+[CPR 6.1-1] The 5G system shall support a mechanism to verify authorization of a 3rd party application to use 5G timing resiliency.
+
+[CPR 6.1-2] The 5G system shall support a mechanism to monitor and verify authenticity of the timing source, where supported by the time source.
+
+[CPR 6.1-3] The 5G system should verify the availability of the external time sources.
+
+## 6.2 Potential charging considerations
+
+[CPR 6.2-1] The 5G system shall be able to collect charging information based on the timing source (e.g., the source in use, start and stop of source usage).
+
+[CPR 6.2-2] The 5G system shall be able to collect charging information per UE for use of a timing source (e.g., start/stop time and source used by a UE, timing source used by UE, holdover capability).
+
+[CPR 6.2-3] The 5G system shall be able to collect charging information on 5G system timing resiliency (e.g., resiliency KPIs, holdover capability, number of UEs using a certain timing source).
+
+[CPR 6.2-4] The 5G system shall be able to collect charging information per application, including 3rd party application (e.g., timing resiliency KPIs, holdover capability, number of UEs using a certain timing source).
+
+# 7 Consolidated potential requirements and KPIs
+
+## 7.1 Consolidated potential requirements
+
+### 7.1.1 General
+
+**Table 7.1.1-1 – General Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 7.1.1-1 | The 5G system shall be able to receive accurate timing signals from one or more independent timing source(s), which can offer a timing alternative to GNSS, e.g. TBS/MBS [7] [8], Sync over Fiber [7]. | [PR 5.1.6-1] | |
+| CPR 7.1.1-2 | The 5G system shall be able to maintain accurate time synchronization as appropriate for the supported applications in the event of degradation or loss of GNSS timing signals. | [PR 5.1.6-3] | |
+
+### 7.1.2 Monitoring and Reporting
+
+**Table 7.1.2-1 – Monitoring and Reporting Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------|
+| CPR 7.1.2-1 | The 5G system shall monitor for timing source failure. | [PR 5.2.6.1-1] | |
+| CPR 7.1.2-2 | The 5G system shall be able to detect when reference timing signals (e.g., from GNSS or other timing source) are no longer viable for network time synchronization. | [PR 5.1.6-2] | |
+| CPR 7.1.2-3 | The 5G system shall support a mechanism to determine the time uncertainty of the 5G time synchronization. | [PR 5.4.6.1-1] | |
+| CPR 7.1.2-4 | The 5G system shall be able to indicate to devices (e.g., UEs, applications) that they need to use an alternate time source (e.g., to 5G system internal holdover capability, atomic clock, Sync over Fiber, TBS, GNSS), taking into account the holdover capability of the devices. | [PR 5.2.6.1-2] | |
+| CPR 7.1.2-5 | The 5G system shall be able to detect when a timing source fails or is restored for network time synchronization. | [PR 5.2.6.1-4] | |
+| CPR 7.1.2-6 | The 5G system shall support mechanisms to monitor different time sources and adopt the most appropriate. | [PR 5.4.6.1-2] | |
+| CPR 7.1.2-7 | The 5G system shall support a mechanism to report timing resiliency information (e.g., divergence from UTC, time uncertainty) to 3rd party applications. | [PR 5.4.6.1-3] | |
+
+### 7.1.3 Service Exposure
+
+**Table 7.1.3-1 – Service Exposure Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------|
+| CPR 7.1.3-1 | The 5G system shall support a mechanism for a 3rd party application to request resilient timing with specific KPIs (e.g., accuracy, interval, coverage area). | [PR 5.3.6-3] | |
+
+### 7.1.4 (void)
+
+## 7.2 Consolidated potential KPIs
+
+The 5G system shall be able to support a holdover capability with timing resiliency performance requirements defined in table 7.2-1.
+
+**Table 7.2-1: Timing resiliency performance requirements for 5G System**
+
+| Use-case | Holdover Time (note 3) | Sync Target | Sync accuracy | Service area | Mobility | Remarks |
+|------------------------------|------------------------|--------------|--------------------------------|----------------------|----------|-----------------------------------------------------------------------------------------------|
+| Power grid (5G network) | Up to 24 hour | UTC (note 1) | <250ns-1000ns [3], [9] (note2) | < 20 km 2 | low | When 5G System provides direct PTP Grandmaster capability to sub-stations |
+| Power grid (time synchroniza | >5 s | UTC (note 1) | <250ns-1000ns [3], [9] (note2) | < 20 km 2 | Low | When 5G sync modem is integrated into PTP grandmaster solution (with 24h holdover capability) |
+
+| | | | | | | |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|--|------------------|
+| tion device) | | | | | | at sub-stations) |
+| Note 1: A different synchronization target is acceptable as long as the offset is preconfigured when an alternatively sourced time differs from GNSS. In this case, a 5G end device shall provide PPS output which can be used for measuring the difference.
Note 2: Use case [New] in [9] illustrates the different accuracy measurements based on different configurations needed to support the underlying requirements from IEC [3]. The range is between 250 ns and 1000 ns. The actual requirement depends on the specific deployment.
Note 3: This requirement will vary based on deployment options.
| | | | | | |
+
+**Table 7.2-2: Level of accuracy for members or participants of a trading venue [13, 14]**
+
+| Type of trading activity | Maximum divergence from UTC | Granularity of the timestamp (note 1) |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------------|
+| Activity using high frequency algorithmic trading technique | 100 $\mu$ s | $\leq 1\mu$ s |
+| Activity on voice trading systems | 1s | $\leq 1$ s |
+| Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading | 1s | $\leq 1$ s |
+| Activity of concluding negotiated transactions | 1s | $\leq 1$ s |
+| Any other trading activity | 1ms | $\leq 1$ ms |
+| Note 1: Only relevant for the case where the time synchronization assists in configuring the required granularity for the timestamp (for direct use), otherwise it will be configured separately as part of the financial transaction timestamp process.
| | |
+
+# 8 Conclusion and recommendations
+
+The study has analysed a number of use cases supporting 5G timing resiliency for various vertical uses. The use cases demonstrate the anticipated enhancements in the 5G system in order to
+
+- \* use the 5G system in concert with other timing technologies as a resilient timing source in complement/backup/alternate to GNSS, and
+- \* to enable time synchronization resiliency is available if GNSS or other timing sources are compromised.
+
+The resulting considerations on security and charging have been consolidated in clause 6 and the potential requirements and KPIs have been consolidated in clause 7 of the TR. The content of clauses 6 and 7 should be considered as the basis of normative Rel-18 requirements to support 5G timing resiliency.
+
+# Annex A: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|---------|-----|----------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | R
ev | Cat | Subject/Comment | New version |
+| 2020-08/09 | SA1#91e | | | | | Agreements in SA1#91e: S1-203080, S1-203331, S1-203332, S1-203334, S1-203335, S1-203411.
And rapporteur's clean up. | 0.1.0 |
+| 2020-11/19 | SA1#92e | | | | | Agreements in SA1#92e: S1-204319, S1-204415, S1-204416.
And rapporteur's clean up. | 0.2.0 |
+| 2021-03/06 | SA1#93e | | | | | Agreements in SA1#93e: S1-210043, S1-210431, S1-210432, S1-210433, S1-210434, S1-210435
And rapporteur's clean up. | 0.3.0 |
+| 2021-03 | SA#91e | SP-210204 | | | | Presented for one-step approval to SA.
MCC clean-up | 1.0.0 |
+| 2021-03 | SA#91e | SP-210204 | | | | Raised to v.18.0.0 following SA one-step approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210509 | 0001 | | D | Update of inclusive language | 18.1.0 |
+| 2021-06 | SA#92e | SP-210509 | 0002 | 1 | F | 0 Corrections of holdover related aspects | 18.1.0 |
+| 2021-12 | SP-94 | SP-211496 | 0003 | | D | Update CPR tables | 18.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22881/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22881/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..06e89da17143c6edcae9a681b88f7e3906a6143c
--- /dev/null
+++ b/marked/Rel-18/22_series/22881/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a102d068befb1407c835526fc60f165961f999f0b0a0460e999fb55c8bebc6ee
+size 9362
diff --git a/marked/Rel-18/22_series/22881/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22881/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67e62e66323b7478e5f51ea3e9c93f2a7e6a1cf8
--- /dev/null
+++ b/marked/Rel-18/22_series/22881/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f70638c1289b706102d5470eecdadfabbe3aaac0e04a9729c4adcfafcb762615
+size 5655
diff --git a/marked/Rel-18/22_series/22881/raw.md b/marked/Rel-18/22_series/22881/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..48063b72542fcd5fd510a7a20f52e29fbf81e709
--- /dev/null
+++ b/marked/Rel-18/22_series/22881/raw.md
@@ -0,0 +1,359 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on sharing administrative configuration between interconnected MCX systems (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+LTE, 5G, MCPTT, MCVideo, MCData
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+### --- **Internet**
+
+
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-----------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions of terms, symbols and abbreviations ..... | 5 |
+| 3.1 Terms..... | 5 |
+| 3.2 Symbols..... | 5 |
+| 3.3 Abbreviations ..... | 5 |
+| 4 Overview..... | 5 |
+| 5 Use cases..... | 6 |
+| 5.1 Changing group membership in a Partner MCX Service System..... | 6 |
+| 5.1.1 Description ..... | 6 |
+| 5.1.2 Pre-conditions..... | 6 |
+| 5.1.3 Service Flows ..... | 6 |
+| 5.1.4 Post-conditions ..... | 7 |
+| 5.1.5 Existing features partly or fully covering the use case functionality ..... | 7 |
+| 5.1.6 Potential New Requirements needed to support the use case..... | 7 |
+| 5.2 Incident response involving multiple countries ..... | 7 |
+| 5.2.1 Description ..... | 7 |
+| 5.2.2 Pre-conditions..... | 8 |
+| 5.2.3 Service Flows ..... | 8 |
+| 5.2.4 Post-conditions ..... | 9 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 9 |
+| 5.2.6 Potential New Requirements needed to support the use case..... | 9 |
+| 6 Security Aspects..... | 9 |
+| 6.1 Introduction ..... | 9 |
+| 6.2 Potential requirements..... | 9 |
+| 7 Additional considerations ..... | 10 |
+| 8 Consolidated Potential Requirements ..... | 10 |
+| 8.1 Changing group membership in a Partner MCX Service System..... | 10 |
+| 8.2 Incident response involving multiple countries ..... | 10 |
+| 8.3 Security Aspects..... | 11 |
+| 9 Conclusions and Recommendations ..... | 11 |
+| Annex : ..... | 12 |
+| <b>Annex <B> (informative): Bibliography .....</b> | <b>13</b> |
+| <b>Annex <X> (informative): Change history .....</b> | <b>14</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+Editor's note: Text to be provided.
+
+# --- 1 Scope
+
+The present document studies use cases that assess under which circumstances interconnected MCX Service Systems exchange administrative and security relevant data and information.
+
+Its objective is to identify new potential requirements related to the use cases and new high-level security requirements related to interconnection of MCX Service Systems and migration of MCX Users and MCX Service Groups.
+
+# --- 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".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Overview
+
+Considering public safety users specifically, different scenarios of public safety broadband wireless communications systems deployments will emerge, but some requirements remain common. In international or multi agency collaboration scenarios public safety MCX Service Users are required to roam or migrate from one system to another, need to use MCX Services or be included in specific communication events in a Partner MCX Service System on a temporary basis.
+
+Public safety may also deploy their own mobile, local, countrywide or national broadband communications systems. In order to grant visiting MCX Service Users access to a Partner MCX Service System and its services, a mechanism is
+
+required which allows the request and/or transmission of administrative configuration data, to be exchanged between connected MCX Service Systems. This type of administrative configuration data is used for adding MCX Service Users into a Partner MCX Service System's user database and for enabling or disabling certain services. Relevant information can be exchanged prior to the visiting MCX Service Users arriving from a Partner MCX Service System or dynamically during events for example.
+
+Such mechanism can be realised with the administrative configuration data and information exchange concept, discussed in this study.
+
+# --- 5 Use cases
+
+## 5.1 Changing group membership in a Partner MCX Service System
+
+### 5.1.1 Description
+
+A Dutch police officer currently located in Germany is witnessing a traffic accident involving a Dutch truck. The Dutch MC UE is equipped with a roaming SIM card, is registered in a public German EPS/5GS, which allows the Dutch police officer to use Dutch MCPTT services only and there is no affiliation to German police or emergency services talk groups granted.
+
+In order to offer support to local law enforcement the police officer contacts the Dutch command and control centre in the Dutch MCX Service System and offers assistance at the scene of the accident. The Dutch control centre contacts the German MCX Service System via the High Level Protocol and announces that a police officer with Dutch and German language skills is available at the scene of the accident and requests the ability to participate in the local police incident communications.
+
+The relevant German command and control room receives the support offer and approves the request. The Dutch police officer then receives configuration data and authorisation allowing him to affiliate to the local Police talk group in the German MCX Service System.
+
+The Dutch police officer can now communicate directly with the German police officers on site to support the accident investigation, adding a witness statement.
+
+### 5.1.2 Pre-conditions
+
+1. The Dutch police officer has to have a valid MCX subscription in the Dutch MCX Service System
+2. There is an operational agreement between the Dutch and the German Mission Critical Organization and a link has been established between the systems that allows exchange of administrative configuration information
+3. An agreement has to be in place that allows the Dutch police officer's UE to register on a public German EPS/5GS which enables initial communication with the Dutch MCX Service System authorized user(s)
+
+### 5.1.3 Service Flows
+
+1. The Dutch Police officer informs their Dutch MCX Service System's authorized user(s)
+2. The authorized user(s) in the Dutch Police officers Primary MCX Service System analyses the received information and collects additional information, which need to be provided to the Partner MCX Service System
+3. The authorized user(s) in the Dutch MCX Service System establishes contact via a separate administrative configuration protocol with the German MCX Service System
+4. The Dutch and the German MCX Service Systems exchange the relevant administrative and security information via the separate administrative configuration protocol
+
+5. The relevant authorized user(s) in the German MCX Service System, either automatically or manually, processes the request
+6. After acceptance or successful checks/authorisations, the Dutch Police officer's user profile is updated to include the relevant information, such as user group configuration and encryption key material, assigned by the German MCX Service System
+7. The Dutch police officer's UE affiliates to the German MCX Service Group via the Dutch MCX Service System and its Group communication is routed from the public German EPS/5GS through the Dutch MCX Service System to the German MCX Service System
+
+### 5.1.4 Post-conditions
+
+1. The Dutch Police officer can now select and participate in the relevant German talk group(s)
+
+### 5.1.5 Existing features partly or fully covering the use case functionality
+
+The following requirements refer to 3GPP TS 22.280.
+
+[R-6.17.2-004] An MCX Service shall provide mechanisms to allow an MCX User on the Primary MCX Service System to affiliate and communicate in an MCX Service Group from a Partner MCX Service System, subject to authorization from the Primary MCX Service System and the Partner MCX Service System where the MCX Service Group is defined.
+
+[R-6.17.2-007] End to end security of an MCX Service Group communication (including in Partner MCX Service Systems) shall be based on parameters obtained from the MCX Service system where the MCX Service Group is defined.
+
+### 5.1.6 Potential New Requirements needed to support the use case
+
+[PR 5.1.6.1] An MCX Service shall provide secure mechanisms to allow an authorised MCX User to request MCX User configuration changes in one or more Partner MCX Service Systems.
+
+[PR 5.1.6.2] An MCX Service shall provide secure mechanisms to allow an authorised MCX User to evaluate and respond to requests for configuration changes from Partner MCX Service Systems.
+
+[PR 5.1.6.3] An MCX Service shall provide secure mechanisms to allow an authorised MCX User to configure automatic responses to categories of requests for configuration changes from Partner MCX Service Systems.
+
+## 5.2 Incident response involving multiple countries
+
+### 5.2.1 Description
+
+A train carrying passengers and cargo has derailed in the border region between Belgium, The Netherlands and Germany and collided with a freight train transporting chemicals and other flammable material. Injured persons need to be rescued, derailed carriages need to be secured, chemicals have to be neutralised or cleaned up and fires nearby any flammable material need to be controlled.
+
+The accident happened in Germany, which means the German PPDR organization carry the responsibility to deal with the incident and coordinate the rescue efforts. Calls from the public to report the incident reach the relevant Belgian, Dutch and German command and control centres. As the relevant PPDR organizations in the region have bi-lateral incidence support agreements in place, the Belgian and Dutch PPDR organizations immediately offer resources to the relevant German authorities.
+
+Administrative information is transmitted in a pre-agreed format to the relevant German command and control centre and includes capability information, such as what type of rescue equipment can be made available or what type of hazardous materials can be dealt with, as well as the MCX user IDs of the first responder able to operate the relevant equipment. The information transmitted includes an estimated time to reach the incident site.
+
+Since the accident involves trains and rail equipment, the relevant rail authorities and support groups need to be contacted and brought into the rescue efforts.
+
+In order to ensure operational safety of the first responders on-site and a quick response to on-site emergency calls, their respective MCX Service UE's emergency call communication is reconfigured to be routed to a specific mobile on-site emergency call centre.
+
+The relevant German command and control centre analyses the information received and requests the resources that are deemed necessary to support the rescue efforts. Information such as configuration data and authorizations are then transmitted back to the relevant Belgian and Dutch control centres and rail emergency command and control centre authorized user(s) to allow the relevant MCX UEs to affiliate with the relevant German MCX Service System talk groups.
+
+This allows the multi-agency rescue and first response efforts to be coordinated efficiently and ensures communication is possible with all resources involved in the incident.
+
+### 5.2.2 Pre-conditions
+
+All relevant Belgian and Dutch MC UEs are equipped with roaming SIM cards, which allow the MC UEs to register in the German LTE/5GS networks. Capability information is linked to an MCX user ID record and by requesting a specific capability, such as “chemical incident”, “medical air lift” or “heavy equipment handling” the relevant resources can be made available by the partner organisations and MC UEs can be affiliated and linked to the relevant talk groups.
+
+1. The Dutch and Belgian first responders have to have valid MCX subscriptions in their respective MCX Service Systems
+2. MCX User capability information is available for efficient request/deployment of relevant resources
+3. Connections between the relevant systems have been established that allow exchange of administrative configuration information
+
+### 5.2.3 Service Flows
+
+1. The relevant Dutch and Belgian command and control centres receive incident information from the public
+2. The relevant Dutch and Belgian authorized user(s) analyse the response requirements, collect additional information which resources and capabilities are available
+3. After it has been understood that the incident site is located in Germany, the authorized user(s) in the Dutch and Belgian MCX Service System establish contact via a separate administrative configuration protocol with the German MCX Service System
+4. The train emergency system sends information about the incident to the relevant rail emergency command and control centre(s) or authorities
+5. The relevant authorized user(s) in the Dutch and Belgian command and control centres inform the relevant German authorized user(s) which resources, such as heavy lifting machinery, air lift, fire engines or ambulances and capabilities, such as handling chemical spills or weight limitations for lifting equipment are available and when they could be available at the incident site
+6. The relevant authorized user(s) in the German Primary MCX Service System collect the information and either automatically or manually, processes the information and request the required resources and capabilities from the Dutch and Belgian MCX Service Systems, plus the relevant rail authorized user(s)
+7. The Dutch, Belgian MCX Service Systems and relevant rail authorized user(s) exchange the relevant administrative and security information via the separate administrative configuration protocol with the German MCX Service System
+8. After acceptance or successful checks/authorisations, user profiles of the Dutch and Belgian and rail incident support MCX Service Users are updated to include the relevant information, such as user group configuration and encryption key material, assigned by the German MCX Service System
+
+9. The Dutch, Belgian MCX Service Users UEs affiliate to the German MCX Service Groups via the Dutch and Belgian MCX Service System and their Group communication is routed from the public German LTE/5GS through the Dutch and Belgian MCX Service System to the German MCX Service System
+10. The relevant rail incident support MCX Service Users UEs affiliate to the incident related and relevant MCX Service Groups
+
+### 5.2.4 Post-conditions
+
+1. First responders from the Dutch and Belgian MCX Service organizations can select and participate in the relevant German talk groups
+2. The relevant rail authorities, key personnel and first responders can participate in the MCX services (MCPTT, MCVideo and MCData) with the relevant authorized MCX Services Users
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+The following requirements refer to 3GPP TS 22.280.
+
+[R-5.6.2.2.1-013] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated MCX Service Emergency Group) is used for the MCX Service Emergency Group Communication by an MCX User.
+
+The following requirements refer to 3GPP TS 33.180.
+
+Clause 5.1.5 MC user migration service authentication and authorisation.
+
+### 5.2.6 Potential New Requirements needed to support the use case
+
+[PR 5.2.6.1] An MCX Service shall provide secure mechanisms to allow an authorised MCX User to request configuration information from Partner MCX Service Systems.
+
+[PR 5.2.6.2] An MCX Service shall provide secure mechanisms to allow an authorised MCX User to send configuration information to Partner MCX Service Systems.
+
+[PR 5.2.6.3] An MCX Service shall provide secure mechanisms to allow an authorised MCX User to exchange MCX User relevant information with Partner MCX Service Systems.
+
+# --- 6 Security Aspects
+
+## 6.1 Introduction
+
+This section proposes potentially new security requirements that allow Primary and Partner MCX Service Systems to exchange administrative and security relevant information without compromising integrity of the connected MCX Service Systems.
+
+## 6.2 Potential requirements
+
+[PR 6.2.001] Exchange of administrative and security related information between MCX Service systems shall not compromise the integrity and security of either MCX Service System.
+
+[PR 6.2.002] Exchange of administrative and security related information shall not expose the internal structure or configuration of either MCX Service System.
+
+[PR 6.2.003] MCX Service Systems shall detect and prevent unauthorized connection attempts
+
+[PR 6.2.004] Exchange of administrative and security related information between MCX Service Systems shall cover prevention of replay attacks
+
+[PR 6.2.005] Exchange of administrative and security related information between MCX Service Systems shall cover algorithm negotiation and prevention of bidding down attacks
+
+[PR 6.2.006] Mutual authentication and authorization between the connected MCX Service Systems shall be supported
+
+[PR 6.2.007] Separate, mutual authentication and authorization shall be possible with more than one MCX Service System at any time
+
+[PR 6.2.008] Messages that travers trust boundaries shall follow 3GPP specifications for protection, if not protected by end-to-end security
+
+# 7 Additional considerations
+
+Editor's note: Add clauses as needed. Text to be provided.
+
+# 8 Consolidated Potential Requirements
+
+## 8.1 Changing group membership in a Partner MCX Service System
+
+**Table 8.1-1 – Changing group membership in a Partner MCX Service System - Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------------------------|
+| CPR 8.1 | An MCX Service shall provide a mechanism to allow an authorised MCX User to request MCX User configuration changes in one or more Partner MCX Service Systems. | PR 5.1.6.1 | CPR 8.1 identical to PR 5.1.6.1 |
+| CPR 8.2 | An MCX Service shall provide a mechanism to allow an authorised MCX User to evaluate and respond to requests for configuration changes from Partner MCX Service Systems. | PR 5.1.6.2 | CPR 8.2 identical to PR 5.1.6.2 |
+| CPR 8.3 | An MCX Service shall provide a mechanism to allow an authorised MCX User to configure automatic responses to categories of requests for configuration changes from Partner MCX Service Systems. | PR 5.1.6.3 | CPR 8.3 identical to PR 5.1.6.3 |
+
+## 8.2 Incident response involving multiple countries
+
+**Table 8.2-1 – Incident response involving multiple countries - Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CPR 8.4 | An MCX Service shall provide a mechanism to allow an authorised MCX User to request configuration information from Partner MCX Service Systems. | PR 5.2.6.1 | CPR 8.4 identical to PR 5.2.6.1 |
+| CPR 8.5 | An MCX Service shall provide a mechanism to allow an authorised MCX User to send configuration information to Partner MCX Service Systems. | PR 5.2.6.2 | CPR 8.5 identical to PR 5.2.6.2 |
+| CPR 8.6 | An MCX Service shall provide a mechanism to allow an authorised MCX User to exchange operational MCX User relevant information, e.g. MCX User capability information, with Partner MCX Service Systems. | PR 5.2.6.3 | Original PR: An MCX Service shall provide secure mechanisms to allow an authorised MCX User to exchange MCX User relevant information with Partner MCX Service Systems. |
+
+## 8.3 Security Aspects
+
+**Table 8.3-1 – Security Aspects - Consolidated Requirements**
+
+| CPR # | Consolidated Potential Requirement | Original PR # | Comment |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------------------------------------------------------------------------------------------|
+| CPR 8.7 | Exchange of administrative and security related information between MCX Service systems shall not compromise the integrity and security of either MCX Service System. | PR 6.2.001 | CPR 8.7 identical to PR 6.2.001 |
+| CPR 8.8 | Exchange of administrative and security related information shall not expose the internal structure or configuration of either MCX Service System. | PR 6.2.002 | CPR 8.8 identical to PR 6.2.002 |
+| CPR 8.9 | Exchange of administrative and security related information between interconnected MCX Service systems shall be secure. | PR 6.2.003 | Original PR: MCX Service Systems shall detect and prevent unauthorized connection attempts |
+| CPR 8.9 | Merged into [CPR 8.9] | PR 6.2.004 | |
+| CPR 8.9 | Merged into [CPR 8.9] | PR 6.2.005 | |
+| CPR 8.9 | Merged into [CPR 8.9] | PR 6.2.006 | |
+| CPR 8.9 | Merged into [CPR 8.9] | PR 6.2.007 | |
+| CPR 8.9 | Merged into [CPR 8.9] | PR 6.2.008 | |
+
+# 9 Conclusions and Recommendations
+
+This study has examined a number of use cases that form the basis for the consolidated potential requirements identified in clause 8.
+
+It is proposed to consider the content in clause 8 as a basis for normative work in Rel-18 to support requirements to enable the exchange of administrative configuration and security relevant information between interconnected MCX Service systems.
+
+# --- Annex <A>: <Title>
+
+# --- Annex <B> (informative): Bibliography
+
+The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information.
+
+# Annex <X> (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|---------|-----|------------------------------------------------------------------------------|----------------|
+| Date | Meeting | TDoc | CR | R<br>ev | Cat | Subject/Comment | New<br>version |
+| 2019-11 | SA1#88 | S1-193222 | | | | First revision | 0.2.0 |
+| 2020-09 | SA1#91e | S1-203233 | | | | Addition of Overview clause | 0.3.0 |
+| 2020-09 | SA1#91e | S1-203310 | | | | Addition of use case – change group membership in Partner MCX Service System | 0.3.0 |
+| 2020-09 | SA1#91e | S1-203311 | | | | Addition of Security Aspects and Potential requirements | 0.3.0 |
+| 2021-03 | SA1#93e | S1-210164 | | | | Addition of use case - Incident response involving multiple countries | 0.4.0 |
+| 2021-03 | SA1#93e | S1-210166 | | | | Clarification for clauses 5.1.1, 5.1.2, 5.1.3 | 0.4.0 |
+| 2021-05 | SA1#94e | S1-211395 | | | | Addition of content in clause 8, Consolidated potential requirements | 0.5.0 |
+| 2021-05 | SA1#94e | S1-211084 | | | | Addition of content in clause 9, Conclusions and recommendations | 0.5.0 |
+| 2021-06 | SA#92e | SP-210506 | | | | Raised by MCC to v.1.0.0 for one-step approval | 1.0.0 |
+| 2021-06 | SA#92e | SP-210506 | | | | Raised by MCC to v.18.0.0 following one-step approval | 18.0.0 |
+| 2021-06 | SA#92e | SP-210506 | | | | Corrected logo (5G->5GA) | 18.0.1 |
+| 2021-12 | SP-94 | SP-211496 | 0001 | | D | Table linking CPRs to their PRs and use cases | 18.1.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22926/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22926/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6f2459e5118861351dd17076bc33824e292a495
--- /dev/null
+++ b/marked/Rel-18/22_series/22926/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2cab1eed5a582d1189f592431115f74285b076069767a466a2b6198a9b382305
+size 9544
diff --git a/marked/Rel-18/22_series/22926/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22926/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5dc62f6b02231c7660a77bb655d9db611af2aea9
--- /dev/null
+++ b/marked/Rel-18/22_series/22926/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0da2e1b9b189faf88efd0809f12fda43a0eac154701146783fb5bef5a1fe6b9
+size 5530
diff --git a/marked/Rel-18/22_series/22926/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-18/22_series/22926/77464a47f104d0d647b2414591137b64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5470c95c1e774472c2aef5fad21f3bd790e4feb3
--- /dev/null
+++ b/marked/Rel-18/22_series/22926/77464a47f104d0d647b2414591137b64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2127bc840fab2856678e84d554012e3bea9ab1267422dbcd8986362adbfd8181
+size 25580
diff --git a/marked/Rel-18/22_series/22926/f38515370322934490a456fa51195cdf_img.jpg b/marked/Rel-18/22_series/22926/f38515370322934490a456fa51195cdf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e54ecdc63aec4bb9aa4a832ef6cce08e0a4422fb
--- /dev/null
+++ b/marked/Rel-18/22_series/22926/f38515370322934490a456fa51195cdf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03564aedeaf25e22696c4c324829045f051f14abb20bc8dbe8b788fb23767c6b
+size 12264
diff --git a/marked/Rel-18/22_series/22926/raw.md b/marked/Rel-18/22_series/22926/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..14c54de96434f99ecbf57e10a7388614a886fe07
--- /dev/null
+++ b/marked/Rel-18/22_series/22926/raw.md
@@ -0,0 +1,709 @@
+
+
+# 3GPP TR 22.926 V18.0.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Guidelines for Extraterritorial 5G Systems; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+<Guidelines, Extraterritorial >
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Overview..... | 7 |
+| 5 Overview of territories affected by regulatory requirements on communication..... | 8 |
+| 5.1 Introduction ..... | 8 |
+| 5.2 Country..... | 8 |
+| 5.3 Exclusion areas..... | 8 |
+| 5.4 Maritime Areas..... | 9 |
+| 5.5 Aeronautical Areas..... | 9 |
+| 5.6 Extraterritorial Areas..... | 9 |
+| 6 3GPP Services/features affected by extraterritoriality..... | 10 |
+| 6.1 Introduction ..... | 10 |
+| 6.2 Public Warning System..... | 10 |
+| 6.3 Charging and Billing ..... | 11 |
+| 6.4 Emergency calls ..... | 11 |
+| 6.5 Lawful Intercept..... | 11 |
+| 6.6 Data Retention Policy in cross-border scenarios and international regions..... | 12 |
+| 6.7 Network access..... | 12 |
+| 7 5G ET UE location related used use cases..... | 13 |
+| 7.1 Introduction ..... | 13 |
+| 7.2 Regulatory implications for UEs in border regions ..... | 13 |
+| 7.2.1 Description ..... | 13 |
+| 7.2.2 Identified applicable regulatory requirements..... | 14 |
+| 7.2.3 Potential 3GPP approach..... | 14 |
+| 7.3 Regulatory implications for UEs in Vessels ..... | 14 |
+| 7.3.1 Description ..... | 14 |
+| 7.3.2 Identified applicable regulatory requirements..... | 15 |
+| 7.3.3 Potential 3GPP approach..... | 15 |
+| 7.4 Regulatory implications for UEs in Exclusion Areas ..... | 16 |
+| 7.4.1 Description ..... | 16 |
+| 7.4.2 Identified applicable regulatory requirements..... | 16 |
+| 7.4.3 Potential 3GPP approach..... | 16 |
+| 7.5 Regulatory implications for UEs in Extraterritorial Areas..... | 16 |
+| 7.5.1 Description ..... | 16 |
+| 7.5.2 Identified applicable regulatory requirements..... | 16 |
+| 7.5.3 Potential 3GPP approach..... | 17 |
+| 7.6 Regulatory implications for UEs Migrating between Areas ..... | 17 |
+| 7.6.1 Description ..... | 17 |
+| 7.6.2 Identified applicable regulatory requirements..... | 17 |
+| 7.6.3 Potential 3GPP approach..... | 17 |
+| 8 5G ET Network location related use cases ..... | 17 |
+| 8.1 Introduction ..... | 17 |
+| 8.2 Network selection with extra territoriality ..... | 18 |
+| 8.2.1 Description ..... | 18 |
+| 8.2.2 Identified applicable regulatory requirements..... | 18 |
+| 8.2.3 Potential 3GPP approach..... | 18 |
+| 8.3 Network access and Exclusion Areas..... | 19 |
+| 8.3.1 Description ..... | 19 |
+
+8.3.2 Identified applicable regulatory requirements..... 19
+8.3.3 Potential 3GPP approach..... 19
+9 Guidelines ..... 20
+9.1 Introduction ..... 20
+9.2 Guidelines for handling extraterritoriality in the 3GPP system ..... 21
+**Annex A: Change history ..... 22**
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+The present document identifies use cases and associated guidelines for the provision of services when a 5G public network has an extraterritoriality access component.
+
+This Technical Report (TR) addresses:
+
+- Use cases and associated conditions generating extraterritoriality of public 5G systems (e.g. HAPS covering multiple countries, satellite access covering international waters, aeronautical networks),
+- 3GPP features (e.g. emergency calls, PWS, LI, charging) and technical aspects (e.g. MCC/MNC, location of UE/NW) for which extraterritoriality may be relevant, and types of regulations that may be applicable.
+- Guidelines on the fulfilment of relevant regulatory requirements (e.g. routing to a core network in a specific country, use of MCC).
+
+This 900 series TR is meant to serve as the basis for technical work in other 3GPP Working Groups when considering the above topics. This TR is not normative. It has been developed by SA1 to capture relevant high-level considerations associated with of the provision of 5G public network and access services in extraterritorial contexts, and provide corresponding guidelines.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.011: Service accessibility
+- [3] [https://www.un.org/depts/los/convention\\_agreements/texts/unclos/part7.htm](https://www.un.org/depts/los/convention_agreements/texts/unclos/part7.htm)
+- [4] 3GPP TS 22.268: "Public Warning System (PWS) requirements"
+- [5] 3GPP TS 22.101: Service aspects; Service principles
+- [6] Global Maritime Distress and Safety System Manual, 2015 Edition, UN IMO, ISBN 978-92-801-1624-3.
+- [7] SOLAS Consolidated Edition, 2020, UN IMO, ISBN 978-92-801-1690-8.
+- [8] 3GPP TS 33.126: "Lawful interception requirements"
+- [9] Data Protection & Privacy Laws, <https://unctad.org/page/data-protection-and-privacy-legislation-worldwide>, Accessed: 19.10.20.
+- [10] ITU RADIO REGULATORY FRAMEWORK FOR SPACE SERVICES;
+[https://www.itu.int/en/ITU-R/space/snl/Documents/ITU-Space\\_reg.pdf](https://www.itu.int/en/ITU-R/space/snl/Documents/ITU-Space_reg.pdf)
+- [11] UN Convention No. 10106 , "Convention on Offences and Certain Other Acts Committed on Board Aircraft", Tokyo, 14 September 1963, <<https://treaties.un.org/doc/db/Terrorism/Conv1-english.pdf>> Accessed 11.02.21.
+
+- [12] UN Convention No. 6456, "CONVENTION ON THE HIGH SEAS", Geneva, 1958.
+<https://sedac.ciesin.columbia.edu/entri/texts/high.seas.1958.html>> Accessed 11.02.21[13]
+ Brisibe, T. C. "International law and regulation of aeronautical public correspondence by satellite", Doctoral Thesis, Faculty of Law, Leiden University, 2006.
+- [13] Title 47, Chapter I, Subchapter B, Part 22, Subpart H, §22.925 “ Prohibition on airborne operation of cellular telephones.” United States Federal Communications Commission.
+- [14] “Impact of exclusion zone policies on siting base stations: Australian case study analysis”. GSMA, August 2012.
+- [15] 3GPP TS 22.119: "Maritime Communication Services over 3GPP system"
+- [16] HCM Agreement: "Agreement between the Administrations of Austria, Belgium, the Czech Republic, Germany, France, Hungary, the Netherlands, Croatia, Italy, Liechtenstein, Lithuania, Luxembourg, Poland, Romania, the Slovak Republic, Slovenia and Switzerland on the co-ordination of frequencies between 29.7 MHz and 43.5 GHz for the fixed service and the land mobile service.", agreed by correspondence in 2020, <http://www.hcm-agreement.eu/>
+- [17] General Data Protection Regulation: "REGULATION (EU) 2016/679 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on the protection of natural persons with regard to the processing of personal data and on the free movement of such data", 27 April 2016
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|-------------------------------------|
+| RPOA | Recognized Private Operating Agency |
+| NTN | Non Terrestrial Network |
+
+# 4 Overview
+
+In some cases, PLMN access can be offered through radio access technologies whose coverage could extend well beyond the political borders of countries. This is the case for instance with satellite access, and this could also be the case with High Altitude Platforms. Another example of extraterritorial access is where a PLMN ID is used for a local network on e.g. a ship or plane travelling in/over international waters. When considering RAN sharing on a satellite network or High-Altitude Platform, PLMN IDs as authorised by one administration in one country, could also be transmitted by a RAN another country. A further scenario could be the transmission of an international PLMN ID (as authorised by ITU according to ITU Rec E.212) over a number of countries territories.
+
+When dealing with services over international waters, aeronautical communications, or terrestrial mobile networks, the question of which requirements apply to the design and operation of the corresponding 5G system ?.
+
+Extraterritoriality is considered in this document as either:
+
+- the location of the UE and its access to the 5G network;
+
+- the location of the 5G network for the services to be delivered.
+
+Guidelines have been developed on this basis for 3GPP specified services of 5G public networks.
+
+# --- 5 Overview of territories affected by regulatory requirements on communication
+
+## 5.1 Introduction
+
+This clause describes different types of territories that are relevant in the discussion of extraterritoriality
+
+## 5.2 Country
+
+Within the context of the document, a country is defined as the area embedded within a set of borders and for which a unique set of regulations applies for the provision of communication services through mobile networks.
+
+For instance, in 3GPP TS 22.011 [2], A Public Land Mobile Network is defined as follows:
+
+"
+
+PLMN
+
+A Public Land Mobile Network (PLMN) is a network established and operated by an Administration or RPOA for the specific purpose of providing land mobile communication services to the public. It provides communication possibilities for mobile users. For communications between mobile and fixed users, interworking with a fixed network is necessary.
+
+A PLMN may provide service in one, or a combination, of frequency bands.
+
+As a rule, a PLMN is limited by the borders of a country. Depending on national regulations there may be more than one PLMN per country.
+
+"
+
+NOTE: Regulations can apply beyond the land borders of a country. Generally the regulations that apply within the land borders of a country also apply to the territorial waters (12 nautical miles). Furthermore also Exclusive Economic Zones (200 nautical miles) should be considered as areas where telecommunication regulations can apply. Overseas areas can sometimes have the same regulations, but sometimes will have to be considered as areas with different regulations.
+
+## 5.3 Exclusion areas
+
+Within a country, some specific areas may be excluded from the general regime which is generally enforced for mobile communication networks. This exclusion regime may be temporary or not, and may be related to some security or safety requirements for instance.
+
+Within a country, some specific areas may be excluded from the general regulatory regime which applies to and is enforced for mobile communications. This exclusion regime may be temporary or not, and may be related to some national security, heterogeneous use of frequency resources (that is, for policies that do not apply uniformly throughout a territory), research or safety requirements for instance. An exclusion area has a well-defined extent within a national territory.
+
+Consideration of Electromagnetic Field regulations for public health are out of scope of this Technical Report. It is assumed that all deployed equipment, whether UE or base station, will comply with all relevant regulations and therefore emissions are not a relevant regulatory consideration for 3GPP standards with respect to Exclusion Areas. Though there are some local governments that pursue exclusion area regulation of this kind, it is a concern both for users (whose service suffers from lack of nearby deployment of base stations) and service providers (whose planning is made more complicated.) [14]
+
+## 5.4 Maritime Areas
+
+In maritime areas, different regulatory regimes may be applicable according to the type of communication services considered in Maritime Areas:
+
+- Passenger communications
+- Operations (including IoT)
+- Maritime Traffic Management
+ - o Surveillance and Tracking
+ - o Bridge voice communication
+ - o Search & Rescue communications
+
+High seas are defined in Reference [3] as a maritime area where no sovereignty can be claimed by any state. (see Article 89).
+
+Article 94 stipulates further that the duties of a Flag State is to effectively exercise its jurisdiction and control in administrative, technical and social matters over ships flying its flag. In particular this shall include that the master, officers .....are fully conversant ...with the applicable international regulations concerning ... the maintenance of communications by radio.
+
+## 5.5 Aeronautical Areas
+
+As for maritime areas, different regulatory regimes may be applicable according to the type of communication services considered in Aeronautical Areas:
+
+- Passenger communications
+- Operations (including IoT)
+- Air Traffic Management
+- Surveillance and Tracking
+ - Cockpit voice communication
+ - Emergency communications
+
+International regulations and standards apply to all but the first category. It is the first category "Passenger communications" that directly applies to 3GPP standards.
+
+There are two scenarios for Aeronautical areas:
+
+- 1) Sovereign Airspace
+- 2) International Airspace
+
+The distinction is relevant as different regulations apply.
+
+## 5.6 Extraterritorial Areas
+
+There are regions that have no territorial claims, e.g. the Antarctic. In these regions, as in the Maritime Areas, no sovereignty is claimed.
+
+Where territorial boundaries are ambiguous, as in disputed or territorial regions, the regulatory implications are described in clause 7.2.
+
+# 6 3GPP Services/features affected by extraterritoriality
+
+## 6.1 Introduction
+
+This clause identifies 3GPP services and features that are affected by extraterritoriality and that are considered in the use cases in this Technical Report (see clause 7 and 8).
+
+## 6.2 Public Warning System
+
+PWS as described in [4] provides the public with alerts, warnings and critical information regarding disasters and other emergencies. The general PWS requirements in [4] are supplemented with regional specific requirements for the Earthquake and Tsunami Warning System (ETWS), the Commercial Mobile Alert System (CMAS), EU-ALERT, and the Korean Public Alert System (KPAS). There is also an Extended PWS, with additional requirements for UEs with no user interface or with a user interface that is incapable of displaying text-based Warning Notifications. In addition, enhancements of Public Warning System (ePWS) is intended to improve the comprehension of a Warning Notification for users with disabilities or for user who are not fluent in the language of the Warning Notifications.
+
+PWS and its different regional variants are generally covered by regulatory requirements (e.g. laws or other regulations). These regulatory requirements can take the form of regulations on operators to support PWS and/or in the form of regulations on devices that are sold in a particular country/region to support PWS. Issues with extraterritoriality can appear when it is not clear which of the national or regional regulatory requirements apply, e.g. in maritime or aeronautical areas. This can include that it is unclear whether PWS should be supported and/or which of the regional versions of PWS must be supported by the operator.
+
+With PWS, Warning Notifications are provided by a Warning Notification Provider. In each country where PWS services are provided, there are procedures in place to determine who (e.g. which agencies or local authorities) can be a Warning Notification Provider. It is unclear whether there will be an organisation with responsibility for coordinating Warning Notifications in extraterritorial areas (e.g. maritime or aeronautical authorities). An alternative is that the network operator selects which Warning Notifications Provider(s) to use for extraterritorial areas. It is clear that a satellite operator with a satellite network covering multiple countries and/or extraterritorial areas will have to interface with multiple Warning Notification Providers.
+
+The Warning Notifications likely include the following five elements:
+
+- Event Description
+- Area Affected
+- Recommended Action
+- Expiration Time (with time zone)
+- Sending Agency
+
+The Warning Notification Provider will provide information determining in which area the Warning Notifications should be distributed. Based on the geographical information indicated by the Warning Notification Provider, it shall be possible for the operators to define the Notification Area based on their network configuration of the area coverage such as distribution of cells.
+
+With satellite networks, it is possible that the area covered by a single cell is much larger than a cell area in the terrestrial network. This can become a problem when satellite coverage and terrestrial coverage overlap. The difference in coverage areas may cause confusion between users of different types of access that get different messages even though they are in the same location. Furthermore, satellite users may receive information that is not targeted at the area they are in. A possible way of addressing these issues is by filtering Warning Notifications on the UE based on Area Affected information within the Warning Notification and location information available on the UE.
+
+## 6.3 Charging and Billing
+
+Several countries have concluded that income deriving from satellite services is income generated within their territory. This implies that the satellite operator may be subject to paying value added and income tax for the services provided to customers in that country.
+
+It is therefore important that the charging and billing system of the satellite operator can identify in which country a UE was located when it was receiving services from the satellite network.
+
+## 6.4 Emergency calls
+
+Requirements for emergency calls are listed in [5].
+
+Different countries and regions can have different types of emergency calls. Furthermore, similar types of emergency calls may use different numbers in different countries. [5] provides the following examples:
+
+| | |
+|-----|-------------------------------------------------|
+| 19 | Police (Albania) |
+| 100 | Police and Fire Brigade (Greek cities) |
+| 100 | Ambulance and Fire Brigade (Belgium) |
+| 112 | Police and Ambulance (Italy) |
+| 112 | General emergency call, all categories (Sweden) |
+| 115 | Fire Brigade (Italy) |
+| 144 | Ambulance (Austria) |
+
+An issue with extraterritoriality may therefore be that it is not clear which emergency call numbers need to be supported. Fortunately, the UE will be able to recognize many of the emergency call numbers and translate a call to an emergency number to an emergency number request. That way on most phones you can either use 911 or 112 to make an emergency call, irrespective of where you are. Note that this is not the case for all emergency call numbers. A non-terrestrial network operators will have to take the location of the UE into account to determine which emergency call numbers apply for which purposes in case the UE has not recognised the emergency call number as a general emergency call.
+
+One of the main aspects related to extraterritoriality is that emergency calls need to be routed to the correct Public Safety Answering Point (PSAP). Routing to the right PSAP may be done based on the basis of UE determined location; it is assumed it is in the best interest also of the UE owner to route to the right PSAP.
+
+A specific issue is to determine what kind of emergency call support should be provided in extraterritorial areas (e.g. at sea outside territorial waters). Users may expect support for emergency calls in areas where there is no clear PSAP that would be able to organise an emergency response. For maritime users the GMDSS (Gross Maritime Distress Safety System) [6] in the context of SOLAS (Saving of Lives at Sea) [7] provides a communication system for emergency response. Satellite operators may provide both GMDSS and/or terrestrial emergency calls. Note that SOLAS regulations impose requirements on maritime users but does not impose regulatory requirements on satellite operators to provide GMDSS and/or emergency calls.
+
+## 6.5 Lawful Intercept
+
+Interception requirements are subject to national law and international treaties and should be interpreted in accordance with applicable national policies.
+
+Lawful Intercept requirements may apply both on the HPLMN and the VPLMN. In both the HPLMN and the VPLMN, the operator will have to provide Intercept Related Information and Content of Communication.
+
+Requirements universally called out in regional interception regulatory requirements are supported by the system defined in [8]. There may also be requirements unique to a specific region or country.
+
+In many cases, national regulation will require that LI activity is performed entirely within a particular legal jurisdiction. Specifically information indicating the target of interception, is often not allowed to be provided to
+
+networks outside the jurisdiction of the particular country of the law enforcement agency that request interception. This may e.g. imply that the satellite ground station and/or base station and the core network all have to be in the same country as the UE, unless countries have made specific agreements. It should therefore be possible to route satellite communication to the right core network based on UE location.
+
+Location Dependent Interception, (LDI) allows a 3GPP network to service multiple interception jurisdictions within its service area. Multiple law enforcement agencies with their own interception areas can be served by the 3GPP network. All the information or rules given for interception within a 3GPP network apply to interception within an Interception Area (IA) when LDI is invoked. A target may be marked in one or more different IAs within the same 3GPP network.
+
+Depending on national requirements, the network operator may be required to report the location of a LI target at the beginning and end of a call and/or session. It may also be a national requirement for the CSP to report the location:
+
+- during on-going communications;
+- for any mobility management event detected in the 3GPP core network which includes a target's location change or update.
+
+The location information associated with target communication reported to the law enforcement agency shall be at least location information trusted by the 3GPP network (i.e. the location information is either 3GPP network derived or verified).
+
+NOTE: Country-specific regulations may include further requirements on location (e.g. on the frequency of reporting)
+
+## 6.6 Data Retention Policy in cross-border scenarios and international regions
+
+Data protection laws, and in particular data retention policies vary between countries [9]. While many of these laws refer to financial transactions, use of a mobile telecommunication system in some sense involves charging records which are directly related to commercial transactions.
+
+Regulations for data retention as part of data privacy and trade law exists for different sovereign states. In some cases there are negotiated treaties between bordering sovereign states regarding the law applicable in cross-border regions.
+
+The NTN access provider and PLMN operator identify the location of the UE. If the location is ambiguous with respect to the sovereign state territory in which the UE operates, then a cross-border condition arises. The NTN access provider and PLMN operator apply the regulations according to the regulations, treaties and conventions that apply to that particular cross border region. This means, in effect, retaining data according to a specific (single) set of regulations.
+
+Data associated with the UE's activity, such as charging records and other operational information is maintained according to international regulations (where no national regulation exists, e.g. on the high seas,) and according to sovereign state law, where this law applies. Where there is ambiguity, the data retention regulation to apply depends on international treaties between the neighbouring sovereign states.
+
+## 6.7 Network access
+
+Countries provide frequency licenses for terrestrial networks. Non-terrestrial networks can cover multiple countries and extraterritorial areas. When a non-terrestrial network uses spectrum that is subject to licensing in a specific country or region the non-terrestrial network will have to ensure it has permission from the countries or regions that are covered [10]. Note furthermore it may be possible that a non-terrestrial network cannot get the same frequency bands in all countries or regions it covers. Non-terrestrial networks will have to ensure that their use of radio spectrum in each country or region complies with the frequency license they have in that country or region and the frequency regulation of the sovereign territories which border that country or region.
+
+Regional/national regulators may also define exclusion areas where non-terrestrial communication is not allowed. Operators of non-terrestrial network should ensure that their networks do not provide service in exclusion areas. Further consideration of this is given in clause 7.4 when UEs are in an exclusion area and in clause 8.3 for non-terrestrial networks operation with respect to exclusion areas.
+
+National regulators can assign numbers and identifiers to the network operator (e.g. Mobile Network Code, IMSI/SUPI ranges, E.164 numbers). Also the ITU can provide MNCs (with the Mobile Country Code 901) and E.164 numbers
+
+(country code 88x). Mobile and satellite networks broadcast one (or more in case of network sharing) Mobile Country Code (MCC) and Mobile Network Code (MNC) combinations. Broadcast of the MCC for one country in another country should be avoided. This may be a challenge for satellite operators that have large radio cells. An option is to use the international MCC 901. Using the international MCC is also a good choice for extra-territorial areas.
+
+# 7 5G ET UE location related used use cases
+
+## 7.1 Introduction
+
+This clause describes use cases for which Extraterritoriality is expressed with respect to the UE and its access to the 5G network.
+
+## 7.2 Regulatory implications for UEs in border regions
+
+### 7.2.1 Description
+
+This use case considers a common scenario in which the UE operates in a location not definitively within one sovereign territory. There are regulations that apply to each sovereign territory. How should the UE and network behave in this situation?
+
+There are two aspects of this use case – frequency regulation and operational regulation (e.g. lawful interception.)
+
+Where there are frequency emissions aspects, there are pre-existing regulations as a result of bilateral or multilateral negotiations between sovereignties. Where this is not successful, the ITU may be involved. It is therefore assumed that there are radio emissions restrictions across borders.
+
+Examples of border regions include:
+
+- Along a river or natural feature defining a border
+- In disputed territory
+- In a border region which is too complex to entirely control all radio transmissions
+
+In ITU regulations this is termed a ‘cross-border’ scenario.
+
+In cross-border scenarios where there is ambiguity (or impossibility to adequately restrict emissions across the borders) there may be special arrangements, e.g. an exclusionary zone. In a specific example, there are frequencies that are of concern to Russia, so a treaty with Finland restricts use of these within a number of km of the border it shares with Russia.
+
+For a UE operating in a cross-border scenario, especially with access provided by a NTN network operator, the situation is more complex and is treated below.
+
+
+
+The diagram shows a satellite in the upper right corner with a beam directed towards a river. The river is depicted as a winding line that serves as a border. On the left side of the river, there is a label 'T1'. On the right side, there is a label 'T2'. The area on the right bank, immediately adjacent to the river and across from T1, is shaded in light purple and labeled 'Ambiguous'. The entire scene is enclosed within a large, thin, irregular oval shape.
+
+Diagram illustrating an ambiguous territory served by NTN access. A satellite is shown in the upper right, with a beam pointing towards a river that forms a border. The river is labeled T1 on the left bank and T2 on the right bank. The area on the right bank, just across the river from T1, is labeled 'Ambiguous'.
+
+**Figure 7.2.1-1 Ambiguous territory served by NTN access**
+
+Figure 7.2.1-1 depicts an ambiguous strip of territory between two sovereign territories T1 and T2. A UE whose subscriber is 'Amalia' is currently in this cross-border location, between T1 and T2. The NTN network operator 'BigSky' provides access to Amalia's UE. The PLMN that Amalia's UE will register with is PLMN A. The CN of PLMN A may be in T1, T2, on the NTN platform or located in a third sovereign territory.
+
+Amalia turns on her UE. The UE registers with access provided by BigSky to PLMN A.
+
+The access, as it straddles T1 and T2, must use frequency that is already in compliance with regulations of T1 and T2.
+
+PLMN A determines Amalia's UE's location and determines that it is an ambiguous cross-border region.
+
+In T1, the regulatory regime of T1 applies (e.g. for Lawful Interception.) In T2, the regulatory regime of T2 applies. In the ambiguous zone it is not clear whose regulations applies. This requires specific consideration, as in some cases, where there are access restrictions, data retention and privacy laws, mandatory encryption of traffic, etc. the regulations may not be compatible: it may be impossible to apply both the regulations of T1 and T2 at the same time. In these cases, there must be a negotiated and harmonized set of regulations between T1 and T2.
+
+Amalia's UE, according to the regulatory framework established by T1 and T2, will have set of policies that apply to its telecommunications service. The NTN operator and the PLMN A operator (which could be the same operator) will apply those regulations.
+
+There are three potential ways in which the UE will behave:
+
+- 1) the UE complies with regulations of *both* sovereign territories (where this is in accord with regulations and the regulations are not incompatible) ), e.g. emergency call regulations in many situations apply on both sides of the border, cross country collaboration can ensure the right assistance is provided even across the border;
+- 2) the UE complies with the bilateral or multilateral regulations established between the territories, e.g. the HCM agreement [16] contains a multilateral regulation on cross border interference;
+- 3) the UE may be in a situation in which a joint (or uniform) regulation applies even though it is in a border region, e.g. the European GDPR regulation [17] is an example of a uniform regulation that applies to all countries within the European Union, including border regions between these countries.
+
+### 7.2.2 Identified applicable regulatory requirements
+
+Regulatory aspects are specified in several 3GPP TSs and external to 3GPP.
+
+UEs will apply regulations according to the regulations applicable to the sovereign territory in which the UE is positioned.
+
+### 7.2.3 Potential 3GPP approach
+
+Applying regulation properly to a UE requires detailed information regarding the UE location.
+
+## 7.3 Regulatory implications for UEs in Vessels
+
+### 7.3.1 Description
+
+A vessel in this clause refers to either a ship or aircraft. Vessels operate in both international and sovereign waters and airspace. At such times as the vessel is in international waters and airspace, the vessel's passenger communication must comply with the regulations of the territory with sovereignty over the location they are in.
+
+At the same time, the vessel and – this is the point - the UEs operating in that vessel may be subject to regulations *of the country of its registration*. The regulatory context changes when the ship is in port or the aircraft is on the ground. There it is clearly the case that sovereign regulations of the territory apply. However, even in this case, there are some regulatory aspects that relate to the country of registration.
+
+NOTE: Unmanned Aerial Vehicles that are also a UE are not considered in this Technical Report.
+
+### 7.3.2 Identified applicable regulatory requirements
+
+The Tokyo Convention [11] states that the laws of the country of registration of the aircraft apply to acts committed on board.
+
+The Convention on the High Seas [12] defines the notion of a 'flag state' registration of the vessel. These laws apply to the passengers on board. From Article 6 "Ships shall sail under the flag of one State only and, save in exceptional cases expressly provided for in international treaties or in these articles, shall be subject to its exclusive jurisdiction on the high seas."
+
+This implies that passenger communication requirements of the vessel in international regions are subject to the regulations of the country of registration.
+
+A separate regime applies to vessels in sovereign waters and airspace. In this case, international law is more complex. The Tokyo Convention Article IV states "A Contracting State which is not the State of registration may not interfere with an aircraft in flight in order to exercise its criminal jurisdiction over an offence committed on board except in the following cases:
+
+- a) the offence has effect on the territory of such State;
+- b) the offence has been committed by or against a national or permanent resident of such State;
+- c) the offence is against the security of such State;
+- d) the offence consists of a breach of any rules or regulations relating to the flight or manoeuvre of aircraft in force in such State;
+- e) the exercise of jurisdiction is necessary to ensure the observance of any obligation of such State under a multilateral international agreement."
+
+Thus, it is entirely possible for an aircraft to impose communication regulations of the registered state while at the same time complying with the above convention. This is analogous to the situation of a vessel in national waters.
+
+While an aircraft is in sovereign airspace, regulations may apply to communications by passengers' UEs. For example, over the United States of America, use of mobile telecommunications using a terrestrial radio access is not permitted. [13]
+
+A third important scenario is the ship in port or an aircraft that has landed. In this case the sovereign regulations of the territory apply. However, there are – for telecommunications especially – certain conditions that are necessary to consider. If communications equipment on board the vessel has been certified by their registered state, these certification requirements may apply to communications rather than those of the territory where they are in port. [12]
+
+The relevance to satellite communication arises due to the distinct regulatory implications based not only on the location of the aircraft or vessel, but also its status (is it airborne? Is it at port?)
+
+### 7.3.3 Potential 3GPP approach
+
+It is recommended that for UEs that are operating outside of sovereign territory, the context of the operation is taken into account, i.e. the national registration of the vessel will determine the regulatory regime applying to the UEs on the vessel.
+
+When a vessel is operating in national waters, or sovereign airspace, the regulations of the corresponding territory apply *in addition* to those of the national registration of the vessel for communication by UEs in that vessel.
+
+When a vessel is in port (i.e. a harbour or an airport), the regulations of the sovereign territory apply for communication by UEs on that vessel. The notable exception to this is that the communication equipment certification of the vessel may be those of the national registration of the vessel.
+
+It is assumed that applicable regulations will be presented to passengers and that passengers will fully comply. From a 3GPP perspective there are no additional standards requirements to identify and comply with related to maritime-specific or airspace-specific regulations for UEs on board vessels.
+
+## 7.4 Regulatory implications for UEs in Exclusion Areas
+
+### 7.4.1 Description
+
+UE operations must take into account and comply with exclusion areas. A UE that does not operate in a manner that violates any exclusion area regulations in a given territory obviously is compliant with regulation. Where a UE might violate an exclusion area, it is necessary to control the operation so that the violation does not occur.
+
+### 7.4.2 Identified applicable regulatory requirements
+
+There are several reasons why exclusion areas are defined – for example to reassign spectrum to more than one purpose depending on the location. There is therefore no attempt to exhaustively or completely treat, list or consider the purposes of exclusion areas, though some examples are given.
+
+One example is the use of CBRS spectrum in the United States. Regulations permit use of this spectrum that respects exclusion zones in which Citizens Broadband Radio Service Devices are not allowed to operate.
+
+Another source of such regulations are international treaties in which spectrum that is used in one country can only be employed by a neighbouring country if emissions are prevented in an exclusion zone extending (sometimes several kilometres) from the mutual border.
+
+Scientific and research exclusion areas exist, for example, in the vicinity of some facilities used for astronomical research.
+
+Exclusion areas where no mobile communication is allowed are not something the 3GPP System can enforce, however there are measures discussed in clauses 7.4.3 and 8.3 to restrict service.
+
+Finally, there are areas defined for operation in some cases, and everything else that is not included is implicitly an exclusion area.
+
+### 7.4.3 Potential 3GPP approach
+
+3GPP network shall be able to restrict radio operations in a specific geographical area.
+
+Firstly, a UE shall not transmit using a frequency that is prohibited in this area.
+
+Secondly a UE shall be prevented to operate if not specifically allowed (by means of a configured Geographic Area.) This has for example been added to the standard for Proximity Services (TS 23.303, 4.5.1.1.2.3.1, TS 23.304, 5.10 and TS 23.501, 5.3.4.1.1.)
+
+## 7.5 Regulatory implications for UEs in Extraterritorial Areas
+
+### 7.5.1 Description
+
+Extraterritorial areas, as defined in clause 5.6 in this document, are regions that have no territorial claims. This does not include vessels and aircraft, whose passengers are effectively considered to be subject to the regulations of the country to which the vessel or aircraft is registered. Rather, we consider the rare case where the UE operates in an unclaimed, disputed, or otherwise extraterritorial area. This clause is added for completeness.
+
+### 7.5.2 Identified applicable regulatory requirements
+
+There are no regulatory requirements in extraterritorial areas.
+
+However, it is essentially impossible for a UE to obtain service in an extraterritorial area except by means of a non-terrestrial access. Non-terrestrial access will be subject to the regulations of the sovereign territory in which the network operates.
+
+An exception may be for UEs that represent a vessel or aircraft (i.e. not the passengers on board). In this case, the UE will have to follow regulatory requirements for maritime or aeronautical communication. For example the International
+
+Maritime Organisation (IMO) sets regulatory requirements for radiocommunication in e.g. the SOLAS (Saving Lives at Sea) convention [7]. Part of the SOLAS regulations is the Global Maritime Distress and Safety System (GMDSS) [6]. Under the GMDSS, all passenger ships and all cargo ships over 300 gross tonnage on international voyages have to carry specified terrestrial and satellite radiocommunication equipment for sending and receiving distress signals and maritime safety information.
+
+### 7.5.3 Potential 3GPP approach
+
+There are no 3GPP requirements or considerations that apply to a UE operating in an extraterritorial area. 3GPP standards that concern regulatory compliant network operation will apply to the UE's service, however there is no need to consider this category of service specifically. Some regulations may be difficult to apply to a UE in Extraterritorial Areas – for example emergency call service may be impossible to route to an appropriate agency.
+
+UEs that follow maritime or aeronautical regulations may want to select specific non-terrestrial networks that provide such services, overriding e.g. PLMN selection considerations related to emergency calls. Note that requirements for Maritime Communication Services over 3GPP systems are defined in [15].
+
+## 7.6 Regulatory implications for UEs Migrating between Areas
+
+### 7.6.1 Description
+
+UEs that operate in a particular regulatory context, as defined in subclauses clause 7, may move to another area, as defined in clause 5. While there may or may not be continuity of service offered in all these situations, the regulatory implications of transitioning (or 'migrating') is considered here.
+
+### 7.6.2 Identified applicable regulatory requirements
+
+The regulatory implications of the area in which the UE operate apply to the UE at that time. Please refer to the different subsection of clause 7 of this document.
+
+While the UE may move between areas, the UE may continue to be served by the same network. For example, if the UE is served by non-terrestrial access, the UE may pass from one sovereign territory to another, from a sovereign territory onto the high seas, etc. and continue to remain registered on the same network.
+
+For terrestrial access, transition from one sovereign territory generally will entail a change from one PLMN operator network to another. However, there are many cases where a PLMN operator covers multiple sovereign territories with a single PLMN. In border regions, cross border coverage is unintentional. In other cases, e.g. covering small states, enclaves, island states, that are too small to have their own PLMN covering multiple sovereign territories is intentional.
+
+### 7.6.3 Potential 3GPP approach
+
+3GPP standards support inter-PLMN handover. It is the responsibility of each network operator to comply with regulations of the sovereign territory in which they operate. This may imply that the PLMN will have to determine the location of the UE at regular intervals in order to determine if the UE is migrating from one area to another and subsequently implement the regulatory implications of that. This may imply e.g. that the PLMN will have to terminate its service to the UE, or treat it differently for regulatory services.
+
+# --- 8 5G ET Network location related use cases
+
+## 8.1 Introduction
+
+This clause describes use cases for which Extraterritoriality is expressed with respect to the UE and its access to the 5G network.
+
+## 8.2 Network selection with extra territoriality
+
+### 8.2.1 Description
+
+Non-terrestrial networks often span multiple countries. This can create issues with network selection. Both with which Mobile Country Code the non-terrestrial network can broadcast, as well as with how to determine the right network for the location of the UE.
+
+Consider the situation in figure, where a satellite network for country A also covers (parts of) country B and country C. Note that in some cases a satellite network may also completely cover a different country. This specifically may be the case with smaller countries (e.g. Vatican City is a different country). In many cases it will be very difficult to target satellite access to only a specific country, without spilling into or completely covering neighbouring countries.
+
+
+
+The diagram shows three overlapping circles representing countries: a yellow circle on the left labeled 'Country B', an orange circle in the center labeled 'Country A', and a green circle on the right labeled 'Country C'. A satellite is positioned above the circles, with a grey shaded area representing its coverage beam. This beam covers all three countries. An arrow points from the text 'MCC A MNC X' to the coverage area over Country A.
+
+Diagram illustrating satellite access covering multiple countries. A satellite is shown in the sky, with a beam covering three countries: Country B (yellow circle), Country A (orange circle), and Country C (green circle). The beam is labeled 'MCC A MNC X'.
+
+Figure 8.2.1-1: Satellite access covering multiple countries.
+
+### 8.2.2 Identified applicable regulatory requirements
+
+One of the regulatory requirements relates to lawful intercept. In many cases, local applicable regulatory requirements dictate that the communication for a UE is handled by a core network in the country in which the UE is located. Note that alternative arrangements may also apply.
+
+NOTE: For example, some countries or islands are too small to have their own mobile network. They therefore rely on a mobile network from a neighbouring country.
+
+Another regulatory requirement is related to the MCC that can be used. Regulatory requirements indicate that MCC usage should be restricted to the country of the MCC represents. However, here in practice there are exceptions to this rule, with e.g. MCCs shared amongst multiple countries.
+
+### 8.2.3 Potential 3GPP approach
+
+First aspect is to determine which MCC shall apply. For satellite networks that intentionally cover a multitude of countries, a shared MCC (e.g. 90x) is probably best. But satellite networks that focus on a specific country, but may have some cross border coverage, should be allowed to use a national MCC. A specific situation is a satellite access network that is shared among a number of operators from different countries. Here the intention of each of these network operators is to cover their own country with their PLMN ID, but the satellite access network will broadcast PLMN IDs for all the countries that it covers. This may happen especially in areas with multiple smaller countries or island regions, where country specific satellite access networks are not feasible. Agreement from the countries involved is required for cross border use of MCCs.
+
+Next step is to ensure that the correct network is selected, even where there may be relatively large areas where multiple MCCs are broadcast. Selecting a network in the country where the UE is located is the best way to ensure that national regulatory requirements are fulfilled.
+
+**NOTE:** Networks with shared MCC will have to make their own arrangements to comply with international regulations and all the different regulations of the countries in which they provide services; this is beyond 3GPP specifications.
+
+Assuming localisation of the UE is supported, there are two issues with selecting a network in the country the UE is located in:
+
+- How to determine which country the location of UE belongs to?
+- Who is responsible for the determination of the country?
+
+The borders of a country can be expressed in a polygon of points with lines in between these points. For some borders this is easily done, but many borders are very irregular requiring very large polygons. Furthermore, country borders are sometimes disputed between different countries and are subject to changes (e.g. regions that gain independence, settlements between countries on borders or the extend of economic zones). This makes creating and maintaining a database of all country borders with sufficient accuracy a complicated and politically sensitive task.
+
+Which country the UE location belongs to in can be determined by the UE or by the network. Note that the UE and the network may come to different conclusions. The network should have the definitive authority to determine if it wants to provide service for the location of the UE.
+
+## 8.3 Network access and Exclusion Areas
+
+### 8.3.1 Description
+
+A network must operate according to regulations. Since exclusion areas prohibit terrestrial radio transmissions in a specific region, networks must be deployed taking account of these constraints.
+
+Terrestrial network access emissions with respect to exclusion areas are regulated by both national and international institutions. These regulations and their operational implications are not in scope of 3GPP.
+
+To some extent the problem of network access and exclusion areas is much simpler for terrestrial access. Network access may simply be absent in exclusion zones by means of deployment in which base station transmitters do not cover such regions. International spectrum usage treaty compliance relies upon such placement and configuration of base stations. This approach however does not match either the constraints or the existing regulatory practices of non-terrestrial access.
+
+This section considers network aspects of compliance with exclusion area policy for non-terrestrial access, given the above considerations.
+
+### 8.3.2 Identified applicable regulatory requirements
+
+As described in clause 7.4.2, exclusion area regulations exist to prevent transmissions and service in certain regions.
+
+Non-terrestrial access transmissions are regulated by governments and international institutions, legal and business arrangements and treaties out of scope of 3GPP.
+
+The 3GPP system authorizes UE use of network access (both terrestrial and non-terrestrial) according to network operator policy and applicable regulations. When regulatory requirements prevent access by a particular UE due to its location, the network can deny this access.
+
+It is not possible for the network to completely prevent misuse, for example, if terminal equipment is misused or tampered with to violate policy. The network can support functionality to deny service in such circumstances.
+
+### 8.3.3 Potential 3GPP approach
+
+The 3GPP network should support a means to identify the location of the UE and apply a corresponding policy that will deny service if the UE operates in an exclusion area.
+
+# 9 Guidelines
+
+## 9.1 Introduction
+
+This clause summarizes the key extraterritoriality requirements associated with each of the identified use cases together with the proposed approach to address these requirements in a 5G system.
+
+The following table captures the regulatory guidance for UEs and networks in different operating areas, for the identified regulatory service. In the table below the 'General' column refers to all stage 1 requirements that are specified as 'subject to regulatory requirements' other than those listed in the other columns.
+
+**Table 9.1-1: Consolidated Regulatory Services in Scenarios considered in TR 22.926**
+
+| | PWS | Charging and Billing | Emergency Call | LI | Data Retention | Network Access | General |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------|----------------|---------|----------------|----------------|---------|
+| 7.2 UE in border region | [NOTE1] | [NOTE2] | [NOTE2] | [NOTE2] | [NOTE1] | [NOTE2] | [NOTE1] |
+| 7.3 UE in Vessels | [NOTE3] | [NOTE3] | [NOTE3] | [NOTE3] | [NOTE3] | [NOTE3] | [NOTE3] |
+| 7.X UE in exclusion area | [NOTE4] | [NOTE4] | [NOTE4] | [NOTE4] | [NOTE4] | [NOTE4] | [NOTE4] |
+| 7.Y UE in extraterritorial area | [NOTE5] | [NOTE6] | [NOTE5] | [NOTE6] | [NOTE6] | [NOTE6] | [NOTE6] |
+| 7.Z UE migrating between areas | [NOTE7] | [NOTE7] | [NOTE7] | [NOTE7] | [NOTE7] | [NOTE7] | [NOTE7] |
+| 8.2 Extraterritorial Network Operation | | | | | | [NOTE2] | |
+| 8.M Network operating in an Aeronautic Area or At Sea | [NOTE8] | [NOTE8] | [NOTE8] | [NOTE8] | [NOTE8] | [NOTE8] | [NOTE8] |
+| 8.N Network access and exclusion areas | [NOTE9] | [NOTE9] | [NOTE9] | [NOTE9] | [NOTE9] | [NOTE9] | [NOTE9] |
+| [NOTE1] The service is offered by the network operator according to the regulatory regime. | | | | | | | |
+| [NOTE2] The service is supported by the network operator according to the regulatory regime, but the location of the UE may be difficult to determine precisely or in an unusual place (offshore, airborne, along the border, etc.) | | | | | | | |
+| [NOTE3] The UE may either be in sovereign territory (airspace, waters), in which case the national regulations apply; or the UE may be in international territory (airspace, waters), in which case the regulations are more complex. See 7.3. It may be impossible to offer some regulatory services to UEs in international territories (e.g. emergency call). | | | | | | | |
+| [NOTE4] A UE in an exclusion area shall not use the network in a prohibited fashion. It is assumed that regulatory services apply to a UE whether or not it is in compliance with the exclusion area. Specifically, no service is provided to a UE in an exclusion area that is not allowed, though regulatory required services will still be supported (including lawful interception.) | | | | | | | |
+| [NOTE5] A UE in an extraterritorial area normally cannot receive national warning messages or perform emergency call. If this is possible, e.g. via non-terrestrial access, this would not be a regulatory service (as no such service has been defined.) | | | | | | | |
+| [NOTE6] A UE receiving service while in an extraterritorial area (e.g. from non-terrestrial access) would have no specific regulation applied <i>to the UE</i> . Regulations would apply to the network, depending on the territory where the network is located. | | | | | | | |
+| [NOTE7] Service for a UE migrating from one area to another will comply with the service of the area the UE is in at the time. | | | | | | | |
+| [NOTE8] A vessel or aircraft is a complex regulatory environment because it can operate both in and out of sovereign territory, and it applies regulations of the country to which the vessel or aircraft is registered. See 8.M. | | | | | | | |
+| [NOTE9] A network deployment will not violate exclusion area restrictions. See 8.N. | | | | | | | |
+
+## 9.2 Guidelines for handling extraterritoriality in the 3GPP system
+
+To support regulated services and features (e.g. Public Warning System, Charging and Billing, Emergency calls, Lawful Intercept, Data Retention Policy in cross-border scenarios and international regions, Network access), 3GPP networks should have the capability to locate each UE in a reliable manner and determine the policy that applies to their operation depending on their location and/or context.
+
+Most terrestrial networks can determine the regulatory policies that apply to the location of UE based on cell areas. For example satellite networks, with generally much larger coverage areas, can maintain a detailed map of borders of areas for which a unique set of regulations applies for the provision of communication services through mobile networks (e.g. Countries including the areas where they claim sovereignty for telecommunication regulations as well as Exclusive Economic Zones).
+
+NOTE: The regulator of the country where the network is located can have regulatory requirements on the definition and use of borders.
+
+Moreover, the network should have knowledge of the specific policy to apply in each of the areas where the network provides services.
+
+In order to determine whether maritime or aeronautical regulations apply, the network may also have to know the context of a UE (e.g. whether it is a ship or plane).
+
+Based on UE location and/or context, the UE should be able to operate following regulatory policies that apply in that specific location and/or context (e.g. not to transmit in an exclusion area where transmission is not permitted.)
+
+# Annex A: Change history
+
+| Change history | | | | | | | |
+|----------------|----------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-09 | SA1#91-e | S1-203278 | | | | TR Skeleton for 5G Extra Territorial 5G systems | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203079 | | | | TR Scope | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203023 | | | | TR Overview | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203023 | | | | TR Section 2 (References) 3 (Definitions) & 5 (Overview of territories) | 0.1.0 |
+| 2020-11 | SA1#92-e | S1-204405 | | | | TR Section 7.2 (Regulatory implications for UEs in border regions) | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204406 | | | | TR Section 6.2 (PWS) and Section 2 (References) | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204410 | | | | TR Section 6.3 (Charging & Billing) and Section 2 (References) | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204407 | | | | TR Section 6.4 (Emergency Calls) and Section 2 (References) | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204408 | | | | TR Section 6.5 (Lawful Intercept) and Section 2 (References) | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204323 | | | | TR Section 6.6 (Data Retention Policy) and Section 2 (References) | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204324 | | | | TR Section 6.7 (Network Access) and Section 2 (References) | 0.2.0 |
+| 2021-03 | SA1#93-e | S1-210117 | | | | TR Section 5.5 (Aeronautical Areas) | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210413 | | | | TR Section 5.6 (Extraterritorial Areas) | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210414 | | | | TR Section 7.3 (Communication Regulation in Vessels) | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210415 | | | | TR Section 8.2 (Network selection with extraterritoriality) | 0.3.0 |
+| 2021-05 | SA1#94-e | S1-211317 | | | | TR Title | 0.4.0 |
+| 2021-05 | SA1#94-e | S1-211414 | | | | TR Section 1 (Scope) & 2 (Overview) | 0.4.0 |
+| 2021-05 | SA1#94-e | S1-211415 | | | | TR Section 7.3 (Regulatory implications for UEs in Vessels) | 0.4.0 |
+| 2021-05 | SA1#94-e | S1-211416 | | | | TR Sections 5.3, 7.4 and 8.4 (Exclusion areas) | 0.4.0 |
+| 2021-05 | SA1#94-e | S1-211417 | | | | TR 7.5 (Regulatory implications for UEs in Extraterritorial Areas) | 0.4.0 |
+| 2021-05 | SA1#94-e | S1-211418 | | | | TR 7.6 (Regulatory implications for UEs Migrating between Areas) | 0.4.0 |
+| 2021-05 | SA1#94-e | S1-211419 | | | | TR 9.1 (Introduction) | 0.4.0 |
+| 2021-09 | SA1#95-e | S1-213132 | | | | TR Section 7.4 Regulatory implications for UEs in Exclusion Areas<br>TR Section 8.3 Network access and Exclusion Areas | 0.5.0 |
+| 2021-09 | SA#93e | SP-211042 | | | | Raised to v.1.0.0 for presentation for information | 1.0.0 |
+| 2021-11 | SA1#96-e | S1-214122 | | | | Editorial changes | 1.1.0 |
+| 2021-11 | SA1#96-e | S1-214123 | | | | Adding a Note on country borders in clause 5.2 | 1.1.0 |
+| 2021-11 | SA1#96-e | S1-214142 | | | | Resolving editor notes + adding 2 references | 1.1.0 |
+| 2021-11 | SA1#96-e | S1-214271 | | | | TR 9.2 (Guidelines for handling extraterritoriality in the 3GPP system) | 1.1.0 |
+| 2021-12 | SA#94e | SP-21xxx | | | | Raised to v.2.0.0 for presentation for approval | 2.0.0 |
+| 2021-12 | SA#94e | SP-211503 | | | | Raised to v.18.0.0 following SA#94e's approval | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22989/10bf8762a8e8d9385609cc6fb11061fe_img.jpg b/marked/Rel-18/22_series/22989/10bf8762a8e8d9385609cc6fb11061fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb5b123bd2f6f4f77fcba875aae557592ae1e9e3
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/10bf8762a8e8d9385609cc6fb11061fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4c0f3e91ec25fa4264687f7a553aa6995d61eb3bae41286f6d01f17eeb632aa
+size 99330
diff --git a/marked/Rel-18/22_series/22989/2d45fd26ca8eff46ba98a969eb2876f4_img.jpg b/marked/Rel-18/22_series/22989/2d45fd26ca8eff46ba98a969eb2876f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54cd9d5303168f0f1ba3356899734f8094698f7b
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/2d45fd26ca8eff46ba98a969eb2876f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:deb43dffdd507fdd03785331f8c3b0f19863000593a5f34508a1592fc8640eb4
+size 62790
diff --git a/marked/Rel-18/22_series/22989/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-18/22_series/22989/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82813a1662462f7e17f081d5ae4ffadfa9516eef
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9421fc42595eeea9c5e6a7c35383ddc4de04e8a85b7fb2a3117df7d519ff9ce
+size 68658
diff --git a/marked/Rel-18/22_series/22989/34fccd22313e0b3b2350c8689f2de9e2_img.jpg b/marked/Rel-18/22_series/22989/34fccd22313e0b3b2350c8689f2de9e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..127ba14029480d9cdb9401075c0152a0511de4ec
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/34fccd22313e0b3b2350c8689f2de9e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e1533e92080a0c89bda84f03e809c104c04bbbb5f330b68eca812f224c52d22
+size 69155
diff --git a/marked/Rel-18/22_series/22989/4391cd8ac8f58d1b46439ea0cb130782_img.jpg b/marked/Rel-18/22_series/22989/4391cd8ac8f58d1b46439ea0cb130782_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c45d15d3e83c7703fa876ffaed1b1c7122b8ba5
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/4391cd8ac8f58d1b46439ea0cb130782_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83d9318ae0a79b2c3ebfe1f90054f01eadc5e672eddabce420ce7be04f25c63b
+size 9301
diff --git a/marked/Rel-18/22_series/22989/58ab1110847fe57c438cad1cdf3b9454_img.jpg b/marked/Rel-18/22_series/22989/58ab1110847fe57c438cad1cdf3b9454_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3265d3a2e5c7617be0c2866a51f7a59fb5db362a
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/58ab1110847fe57c438cad1cdf3b9454_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fad8cc820401a6e910cef3b42018096adb76a0bac65b374ed7cb49e386d20c7
+size 64633
diff --git a/marked/Rel-18/22_series/22989/5cdc04ba574b7b819a3cb6dbbd91306c_img.jpg b/marked/Rel-18/22_series/22989/5cdc04ba574b7b819a3cb6dbbd91306c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e898db8324a23ea70f1f7114b70031c7fe1264d
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/5cdc04ba574b7b819a3cb6dbbd91306c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3d01862bbd5e2fdb01e521b741bff8bee283b20fa13bc4e3012f864f62b5a80
+size 74304
diff --git a/marked/Rel-18/22_series/22989/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22989/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b97b21db20c34cf15fdb5760969a1ef5a938f397
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1303506659c8eed1b7d01bb91774b90a9637cea29665be2bcf7699be59cd93f6
+size 9590
diff --git a/marked/Rel-18/22_series/22989/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22989/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..915bc52a06835f6cb71f7ec312d13078179e7e00
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ddedadd709ac9cc46ef9c894da0bc883e823c3d6e394a62bee10e7a7eff793ac
+size 5711
diff --git a/marked/Rel-18/22_series/22989/667b755d2a359d7b9a54cfceac78350a_img.jpg b/marked/Rel-18/22_series/22989/667b755d2a359d7b9a54cfceac78350a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d27f86b91b94225d7ed1677e22bfd2d9f4a01a7b
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/667b755d2a359d7b9a54cfceac78350a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c689ab62b62dc7150f47966522a88d1375534666e9bedac4400b937600e7d6f4
+size 10537
diff --git a/marked/Rel-18/22_series/22989/6afe6d81119e1f153c5111c029bba637_img.jpg b/marked/Rel-18/22_series/22989/6afe6d81119e1f153c5111c029bba637_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d40bfe751ce16684ad161f5e6557eefbe95d7588
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/6afe6d81119e1f153c5111c029bba637_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa1774105f962c118fa3cf45d1790f4a587c56d84ab4bf54e4a57d158a5df6f9
+size 60874
diff --git a/marked/Rel-18/22_series/22989/7031fc65fd9b760de8fc3d0bbc5b2002_img.jpg b/marked/Rel-18/22_series/22989/7031fc65fd9b760de8fc3d0bbc5b2002_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..839a28ec6e987efef83a31505222c4da4287755f
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/7031fc65fd9b760de8fc3d0bbc5b2002_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f0a4f0b44b892246999a430763e2d8c67d019eaf55652c29c5d3ada88e8acf2
+size 48616
diff --git a/marked/Rel-18/22_series/22989/9988023de78edb2ebe0f265ff913516b_img.jpg b/marked/Rel-18/22_series/22989/9988023de78edb2ebe0f265ff913516b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97daffed489513fa26a5dfd31f1b3a0c19c26625
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/9988023de78edb2ebe0f265ff913516b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3461a6ea0e04ea0a5bb6336678a40f6a2017a14bcf711c22fccf6c0bbfb22e9c
+size 39160
diff --git a/marked/Rel-18/22_series/22989/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-18/22_series/22989/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a34528c7948f0f73e8d66f6c6479c1cb7b58730d
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:940f979c39a966154d462848de3d4a281b932a2428cc231d83a2914e0dc463ce
+size 178349
diff --git a/marked/Rel-18/22_series/22989/abf91c0fe8bc45562f2bc9adc2d5d58a_img.jpg b/marked/Rel-18/22_series/22989/abf91c0fe8bc45562f2bc9adc2d5d58a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e9d84d1094043b41af9853b17873d64e768e757
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/abf91c0fe8bc45562f2bc9adc2d5d58a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43f26c9c80a74a9ac05e465bc3190e56ab3ba2a6c24301dbe5bbf441ada05641
+size 38537
diff --git a/marked/Rel-18/22_series/22989/acc2dc1b1ef27a44f32c3f355e9774d5_img.jpg b/marked/Rel-18/22_series/22989/acc2dc1b1ef27a44f32c3f355e9774d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b224772e3338f97544e941f730423f6d84708fe
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/acc2dc1b1ef27a44f32c3f355e9774d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e30292db4c5b865f9fa8aee2bec22a0fb80af22386d131bd84afd6cf22173483
+size 37237
diff --git a/marked/Rel-18/22_series/22989/ad50411c0472d8e10ed41d723da37b32_img.jpg b/marked/Rel-18/22_series/22989/ad50411c0472d8e10ed41d723da37b32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2582eae0d0efb176c6e0d1932116c6162477320c
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/ad50411c0472d8e10ed41d723da37b32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8584926d085a93fe82b98fbf5fa1201b46bf87f8293e1b48fc28adb497ea383d
+size 41143
diff --git a/marked/Rel-18/22_series/22989/b7636707604e45cc57c71271bc094be1_img.jpg b/marked/Rel-18/22_series/22989/b7636707604e45cc57c71271bc094be1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe407d9795560b5015bde35827d2c38afb3e2355
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/b7636707604e45cc57c71271bc094be1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffd075f273eed58aa1a1ded0867de77fa28bc719d3731e4ea4f2144c4d2e2aa5
+size 37887
diff --git a/marked/Rel-18/22_series/22989/bec54a43401eceb0270c022d21e71a3e_img.jpg b/marked/Rel-18/22_series/22989/bec54a43401eceb0270c022d21e71a3e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d37aa4a6e07a9c428c3838b12c323a1dea078121
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/bec54a43401eceb0270c022d21e71a3e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fcab2fd66ce2a334d5f6a71f9a24ab8ca9ccf7429263f92539f9c4563fcd005
+size 75768
diff --git a/marked/Rel-18/22_series/22989/cc4a284d42136d1539eb2e13a68cbc50_img.jpg b/marked/Rel-18/22_series/22989/cc4a284d42136d1539eb2e13a68cbc50_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bb37277daf492aca8c50d365144dd52ecf2d096
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/cc4a284d42136d1539eb2e13a68cbc50_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a844277f7e8c61dde0512fce1e9f842406ff2085e26eccf6a92a0f3868277653
+size 81174
diff --git a/marked/Rel-18/22_series/22989/cfbacf9a1a61ea0192e73612989ab5ec_img.jpg b/marked/Rel-18/22_series/22989/cfbacf9a1a61ea0192e73612989ab5ec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..78e9a762d0d7dc9cdd2ae4c483a7f71f7393009a
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/cfbacf9a1a61ea0192e73612989ab5ec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d79dec2a9c663801f740cb46be934e716b76f2096d4e3569e9375c797d4e087f
+size 6471
diff --git a/marked/Rel-18/22_series/22989/d49c6ed7cc2cd764f77a0a43ecc9e636_img.jpg b/marked/Rel-18/22_series/22989/d49c6ed7cc2cd764f77a0a43ecc9e636_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c52236b24d977e832499592fc4d1e06bfd0b059b
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/d49c6ed7cc2cd764f77a0a43ecc9e636_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bdf27a447a2f245357caace3b631513882f004070cf210d81a72b211b41c7cf2
+size 72264
diff --git a/marked/Rel-18/22_series/22989/dbe8bef1723acb3e03e8616be4faf939_img.jpg b/marked/Rel-18/22_series/22989/dbe8bef1723acb3e03e8616be4faf939_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9dd48f0143b828a360517eb589862336943a10ff
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/dbe8bef1723acb3e03e8616be4faf939_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:611cbe6e46670f69969c723a1cc736d920621e3ba95e0ebb2d31c6e6ce6ecd75
+size 66883
diff --git a/marked/Rel-18/22_series/22989/e6bcf4c944debe56f4117e9b12e6805a_img.jpg b/marked/Rel-18/22_series/22989/e6bcf4c944debe56f4117e9b12e6805a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bacdd5032ec599c3152423014ac0e65733f4b7b
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/e6bcf4c944debe56f4117e9b12e6805a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4652b978728c8c522dff7edcc0fc901b7ce104dce874913e79aaaed9fc11e580
+size 4561
diff --git a/marked/Rel-18/22_series/22989/e8b07536a16ca769da58e1cfed8a4f3a_img.jpg b/marked/Rel-18/22_series/22989/e8b07536a16ca769da58e1cfed8a4f3a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba313650edb0543cf9aa7a29180627ea4740c398
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/e8b07536a16ca769da58e1cfed8a4f3a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9df8a476aef40c77109602660b9e4995293afb14b5730babba6f2dd6e257f0e
+size 43987
diff --git a/marked/Rel-18/22_series/22989/f63a226da2589601e834e9c210899128_img.jpg b/marked/Rel-18/22_series/22989/f63a226da2589601e834e9c210899128_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..98e4883548d422f9ae3631dfd8caefec7c2ac300
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/f63a226da2589601e834e9c210899128_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d4861b598782f555107d5ddbd95647f255d8f7f098d55339f0390109cb8c31e
+size 39557
diff --git a/marked/Rel-18/22_series/22989/f76667602b24dfd8b3292e05c81d9e00_img.jpg b/marked/Rel-18/22_series/22989/f76667602b24dfd8b3292e05c81d9e00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42e1bdfc0d2273ca76e6dface58710da5a30faba
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/f76667602b24dfd8b3292e05c81d9e00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fc25c29d931207b2d3c3e1a82524a1d70694a0f3ff1a77cb08f82a6a091d37c
+size 8502
diff --git a/marked/Rel-18/22_series/22989/raw.md b/marked/Rel-18/22_series/22989/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..02c76889ded1ea1c3515d0e4356c9bba4b4f137f
--- /dev/null
+++ b/marked/Rel-18/22_series/22989/raw.md
@@ -0,0 +1,8613 @@
+
+
+# 3GPP TR 22.989 V18.5.0 (2022-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Future Railway Mobile Communication System; Stage 1 (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black text to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, black font.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Report is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## Keywords
+
+Railway
+
+## **3GPP**
+
+Postal address
+
+3GPP support office address
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+©2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|-------------------------------------------------------------------------------|----|
+| Foreword..... | 18 |
+| Introduction..... | 18 |
+| 1 Scope..... | 20 |
+| 2 References..... | 20 |
+| 3 Definitions, and abbreviations..... | 21 |
+| 3.1 Definitions..... | 21 |
+| 3.2 Abbreviations..... | 22 |
+| 4 Overview..... | 22 |
+| 5 Basic functionality use cases..... | 24 |
+| 5.1 Introduction..... | 24 |
+| 5.2 Device power on and shut-down related use cases..... | 25 |
+| 5.3 Use case: Power on the UE..... | 25 |
+| 5.3.1 Description..... | 25 |
+| 5.3.2 Pre-conditions..... | 25 |
+| 5.3.3 Service flows..... | 25 |
+| 5.3.4 Post-conditions..... | 25 |
+| 5.3.5 Potential requirements and gap analysis..... | 26 |
+| 5.4 Use case: Access to the FRMCS System to activate the FRMCS Equipment..... | 26 |
+| 5.4.1 Description..... | 26 |
+| 5.4.2 Pre-conditions..... | 26 |
+| 5.4.3 Service flows..... | 26 |
+| 5.4.4 Post-conditions..... | 26 |
+| 5.4.5 Potential requirements and gap analysis..... | 26 |
+| 5.5 Use case: Controlled power down of UE..... | 26 |
+| 5.5.1 Description..... | 26 |
+| 5.5.2 Pre-conditions..... | 26 |
+
+| | | |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| 5.5.3 | Service flows..... | 27 |
+| 5.5.4 | Post-conditions..... | 27 |
+| 5.5.5 | Potential requirements and gap analysis..... | 27 |
+| 5.6 | Use case: Uncontrolled power down UE..... | 27 |
+| 5.6.1 | Description..... | 27 |
+| 5.6.2 | Pre-conditions..... | 27 |
+| 5.6.3 | Service flows..... | 27 |
+| 5.6.4 | Post-conditions..... | 27 |
+| 5.6.5 | Potential requirements and gap analysis..... | 28 |
+| 6 | Critical communication applications related use cases..... | 28 |
+| 6.1 | Introduction..... | 28 |
+| 6.2 | Multi-train voice communication for Drivers and Ground FRMCS User(s)..... | 28 |
+| 6.2.1 | Introduction..... | 28 |
+| 6.2.2 | Use case: Initiation of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication..... | 28 |
+| 6.2.2.1 | Description..... | 28 |
+| 6.2.2.2 | Pre-conditions..... | 28 |
+| 6.2.2.3 | Service flows..... | 29 |
+| 6.2.2.4 | Post-conditions..... | 29 |
+| 6.2.2.5 | Potential requirements and gap analysis..... | 30 |
+| 6.2.3 | Use case: Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication..... | 31 |
+| 6.2.3.1 | Description..... | 31 |
+| 6.2.3.2 | Pre-conditions..... | 31 |
+| 6.2.3.3 | Service flows..... | 31 |
+| 6.2.3.4 | Post-conditions..... | 32 |
+| 6.2.3.5 | Potential requirements and gap analysis..... | 33 |
+| 6.2.4 | Use case: Service Interworking and service continuation between GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication..... | 34 |
+| 6.2.4.1 | Description..... | 34 |
+| 6.2.4.2 | Pre-conditions..... | 34 |
+
+| | | |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------|----|
+| 6.2.4.3 | Service flows..... | 34 |
+| 6.2.4.4 | Post-conditions..... | 35 |
+| 6.2.4.5 | Potential requirements and gap analysis..... | 36 |
+| 6.3 | On-train outgoing voice communication from the Driver towards the Controller(s) of the train..... | 37 |
+| 6.3.1 | Introduction..... | 37 |
+| 6.3.2 | Use case: Initiation of Driver to Controller(s) voice communication..... | 37 |
+| 6.3.2.1 | Description..... | 37 |
+| 6.3.2.2 | Pre-conditions..... | 37 |
+| 6.3.2.3 | Service flows..... | 37 |
+| 6.3.2.4 | Post-conditions..... | 38 |
+| 6.3.2.5 | Potential requirements and gap analysis..... | 39 |
+| 6.3.3 | Use case: Termination of Driver to Controller(s) voice communication..... | 40 |
+| 6.3.3.1 | Description..... | 40 |
+| 6.3.3.2 | Pre-conditions..... | 41 |
+| 6.3.3.3 | Service flows..... | 41 |
+| 6.3.3.4 | Post-conditions..... | 41 |
+| 6.3.3.5 | Potential requirements and gap analysis..... | 42 |
+| 6.3.4 | Use case: Service Interworking and service continuation between GSM-R and FRMCS of Driver to Controller(s) voice communication..... | 42 |
+| 6.3.4.1 | Description..... | 42 |
+| 6.3.4.2 | Pre-conditions..... | 43 |
+| 6.3.4.3 | Service flows..... | 43 |
+| 6.3.4.4 | Post-conditions..... | 43 |
+| 6.3.4.5 | Potential requirements and gap analysis..... | 44 |
+| 6.4 | Railway emergency communication..... | 45 |
+| 6.4.1 | Introduction..... | 45 |
+| 6.4.2 | General overview..... | 45 |
+| 6.4.3 | Use case: Initiation of the railway emergency alert..... | 47 |
+| 6.4.3.1 | Description..... | 47 |
+| 6.4.3.2 | Pre-conditions..... | 47 |
+| 6.4.3.3 | Service flows..... | 47 |
+
+| | | |
+|----------|-----------------------------------------------------------|----|
+| 6.4.3.4 | Post-conditions..... | 48 |
+| 6.4.3.5 | Potential requirements and gap analysis..... | 49 |
+| 6.4.4 | Use case: New entry to the railway emergency alert..... | 50 |
+| 6.4.4.1 | Description..... | 50 |
+| 6.4.4.2 | Pre-conditions..... | 50 |
+| 6.4.4.3 | Service flows..... | 50 |
+| 6.4.4.4 | Post-conditions..... | 51 |
+| 6.4.4.5 | Potential requirements and gap analysis..... | 52 |
+| 6.4.5 | Use case: Changing of the railway emergency alert..... | 52 |
+| 6.4.5.1 | Description..... | 53 |
+| 6.4.5.2 | Pre-conditions..... | 53 |
+| 6.4.5.3 | Service flows..... | 53 |
+| 6.4.5.4 | Post-conditions..... | 53 |
+| 6.4.5.5 | Potential requirements and gap analysis..... | 54 |
+| 6.4.5a | Use case: Merging of Railway Emergency Alerts..... | 55 |
+| 6.4.5a.1 | Description..... | 55 |
+| 6.4.5a.2 | Pre-conditions..... | 55 |
+| 6.4.5a.3 | Service flows..... | 55 |
+| 6.4.5a.4 | Post-conditions..... | 56 |
+| 6.4.5a.5 | Potential requirements and gap analysis..... | 56 |
+| 6.4.6 | Use case: Leaving of the railway emergency alert..... | 56 |
+| 6.4.6.1 | Description..... | 56 |
+| 6.4.6.2 | Pre-conditions..... | 56 |
+| 6.4.6.3 | Service flows..... | 56 |
+| 6.4.6.4 | Post-conditions..... | 57 |
+| 6.4.6.5 | Potential requirements and gap analysis..... | 57 |
+| 6.4.7 | Use case: Termination of the railway emergency alert..... | 57 |
+| 6.4.7.1 | Description..... | 57 |
+| 6.4.7.2 | Pre-conditions..... | 57 |
+| 6.4.7.3 | Service flows..... | 57 |
+
+| | | |
+|----------|--------------------------------------------------------------------------------|----|
+| 6.4.7.4 | Post-conditions..... | 58 |
+| 6.4.7.5 | Potential requirements and gap analysis..... | 58 |
+| 6.4.8 | Use case: Initiation of railway emergency voice communication..... | 58 |
+| 6.4.8.1 | Description..... | 58 |
+| 6.4.8.2 | Pre-conditions..... | 58 |
+| 6.4.8.3 | Service flows..... | 58 |
+| 6.4.8.4 | Post-conditions..... | 59 |
+| 6.4.8.5 | Potential requirements and gap analysis..... | 60 |
+| 6.4.9 | Use case: Termination of railway emergency voice communication..... | 61 |
+| 6.4.9.1 | Description..... | 61 |
+| 6.4.9.2 | Pre-conditions..... | 61 |
+| 6.4.9.3 | Service flows..... | 61 |
+| 6.4.9.4 | Post-conditions..... | 61 |
+| 6.4.9.5 | Potential requirements and gap analysis..... | 62 |
+| 6.4.10 | Use case: Initiation of Data communication during railway emergency alert..... | 62 |
+| 6.4.10.1 | Description..... | 62 |
+| 6.4.10.2 | Pre-conditions..... | 62 |
+| 6.4.10.3 | Service flows..... | 62 |
+| 6.4.10.4 | Post-conditions..... | 63 |
+| 6.4.10.5 | Potential requirements and gap analysis..... | 63 |
+| 6.4.9.10 | Potential requirements and gap analysis..... | 64 |
+| 6.4.11 | Use case: Service interworking and service continuation with GSM-R..... | 64 |
+| 6.4.11.1 | Description..... | 64 |
+| 6.4.11.2 | Pre-conditions..... | 64 |
+| 6.4.11.3 | Service flows..... | 65 |
+| 6.4.11.4 | Post-conditions..... | 66 |
+| 6.4.11.5 | Potential requirements and gap analysis..... | 67 |
+| 6.4.12 | Use case: Interface to train borne recorder..... | 69 |
+| 6.4.12.1 | Description..... | 69 |
+| 6.4.12.2 | Pre-conditions..... | 69 |
+
+| | | |
+|----------|------------------------------------------------------------------------------------|----|
+| 6.4.12.3 | Service flows..... | 69 |
+| 6.4.12.4 | Post-conditions..... | 69 |
+| 6.4.12.5 | Potential requirements and gap analysis..... | 70 |
+| 6.5 | Use case: Automatic Train Protection (ATP) support by the FRMCS System..... | 70 |
+| 6.5.1 | Description..... | 70 |
+| 6.5.2 | Pre-conditions..... | 70 |
+| 6.5.3 | Service flows..... | 70 |
+| 6.5.4 | Post-conditions..... | 70 |
+| 6.5.5 | Potential requirements and gap analysis..... | 71 |
+| 6.6 | Trackside Maintenance Warning System communication related use cases..... | 71 |
+| 6.6.1 | Introduction..... | 71 |
+| 6.6.2 | Use case: Initiation of a trackside maintenance warning system communication..... | 71 |
+| 6.6.2.1 | Description..... | 71 |
+| 6.6.2.2 | Pre-conditions..... | 72 |
+| 6.6.2.3 | Service flows..... | 72 |
+| 6.6.2.4 | Post-conditions..... | 72 |
+| 6.6.2.5 | Potential requirements and gap analysis..... | 72 |
+| 6.6.3 | Use case: Termination of a trackside maintenance warning system communication..... | 72 |
+| 6.6.3.1 | Description..... | 72 |
+| 6.6.3.2 | Pre-conditions..... | 72 |
+| 6.6.3.3 | Service flows..... | 73 |
+| 6.6.3.4 | Post-conditions..... | 73 |
+| 6.6.3.5 | Potential requirements and gap analysis..... | 73 |
+| 6.7 | Pushed Real Time Video streaming..... | 73 |
+| 6.7.1 | Introduction..... | 73 |
+| 6.7.2 | Description..... | 73 |
+| 6.7.3 | Use case: Initiation of a real time video streaming..... | 73 |
+| 6.7.3.1 | Description..... | 73 |
+| 6.7.3.2 | Pre-conditions..... | 73 |
+| 6.7.3.3 | Service flows..... | 74 |
+
+| | | |
+|---------|---------------------------------------------------------------------|----|
+| 6.7.3.4 | Post-conditions..... | 74 |
+| 6.7.3.5 | Potential requirements and gap analysis..... | 75 |
+| 6.7.4 | Use case: Termination of a real time video communication..... | 75 |
+| 6.7.4.1 | Description..... | 75 |
+| 6.7.4.2 | Pre-conditions..... | 75 |
+| 6.7.4.3 | Service flows..... | 75 |
+| 6.7.4.4 | Post-conditions..... | 75 |
+| 6.7.4.5 | Potential requirements and gap analysis..... | 75 |
+| 6.8 | Public emergency call related use cases..... | 75 |
+| 6.8.1 | Introduction..... | 75 |
+| 6.8.2 | Use case: Initiation of a public emergency call..... | 76 |
+| 6.8.2.1 | Description..... | 76 |
+| 6.8.2.2 | Pre-conditions..... | 76 |
+| 6.8.2.3 | Service flows..... | 76 |
+| 6.8.2.4 | Post-conditions..... | 76 |
+| 6.8.2.5 | Potential requirements and gap analysis..... | 76 |
+| 6.8.3 | Use case: Termination of a public emergency call..... | 76 |
+| 6.8.3.1 | Description..... | 76 |
+| 6.8.3.2 | Pre-conditions..... | 77 |
+| 6.8.3.3 | Service flows..... | 77 |
+| 6.8.3.4 | Post-conditions..... | 77 |
+| 6.8.3.5 | Potential requirements and gap analysis..... | 77 |
+| 6.8.4 | Use case: Call back the public emergency call initiator..... | 77 |
+| 6.8.4.1 | Description..... | 77 |
+| 6.8.4.2 | Pre-conditions..... | 77 |
+| 6.8.4.3 | Service flows..... | 77 |
+| 6.8.4.4 | Post-conditions..... | 78 |
+| 6.8.4.5 | Potential requirements and gap analysis..... | 78 |
+| 6.9 | Data communication for possession management related use cases..... | 78 |
+| 6.9.1 | Introduction..... | 78 |
+
+| | | |
+|----------|------------------------------------------------------------------------------------|----|
+| 6.9.2 | Use case: Initiation of a possession management data communication..... | 78 |
+| 6.9.2.1 | Description..... | 78 |
+| 6.9.2.2 | Pre-conditions..... | 78 |
+| 6.9.2.3 | Service flows..... | 78 |
+| 6.9.2.4 | Post-conditions..... | 78 |
+| 6.9.2.5 | Potential requirements and gap analysis..... | 79 |
+| 6.10 | Recording of communication..... | 80 |
+| 6.10.1 | Introduction..... | 80 |
+| 6.10.2 | Use case: Recording..... | 80 |
+| 6.10.2.1 | Description..... | 80 |
+| 6.10.2.2 | Pre-conditions..... | 80 |
+| 6.10.2.3 | Service flows..... | 80 |
+| 6.10.2.4 | Post-conditions..... | 80 |
+| 6.10.2.5 | Potential requirements and gap analysis..... | 80 |
+| 6.11 | Remote control of engines communication related use cases..... | 81 |
+| 6.11.1 | Introduction..... | 81 |
+| 6.11.2 | Use case: Initiation/termination of a remote control of engines communication..... | 81 |
+| 6.11.2.1 | Description..... | 81 |
+| 6.11.2.2 | Pre-conditions..... | 81 |
+| 6.11.2.3 | Service flows..... | 81 |
+| 6.11.2.4 | Post-conditions..... | 81 |
+| 6.11.2.5 | Potential requirements and gap analysis..... | 82 |
+| 6.12 | Automatic Train Operation data communication..... | 82 |
+| 6.12.1 | Introduction..... | 82 |
+| 6.12.2 | Description..... | 82 |
+| 6.12.3 | Use case: Initiation of an Automatic Train Operation data communication..... | 83 |
+| 6.12.3.1 | Description..... | 83 |
+| 6.12.3.2 | Pre-conditions..... | 83 |
+| 6.12.3.3 | Service flows..... | 83 |
+| 6.12.3.4 | Post-conditions..... | 83 |
+
+| | | |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------|----|
+| 6.12.3.5 | Potential requirements and gap analysis..... | 83 |
+| 6.13 | Monitoring and control of critical infrastructure related use cases..... | 83 |
+| 6.13.1 | Introduction..... | 83 |
+| 6.13.2 | Use case: Initiation of a Monitoring and control of critical infrastructure communication..... | 84 |
+| 6.13.2.1 | Description..... | 84 |
+| 6.13.2.2 | Pre-conditions..... | 84 |
+| 6.13.2.3 | Service flows..... | 84 |
+| 6.13.2.4 | Post-conditions..... | 84 |
+| 6.13.2.5 | Potential requirements and gap analysis..... | 85 |
+| 6.13.3 | Use case: Termination of a Monitoring and control of critical infrastructure communication..... | 85 |
+| 6.13.3.1 | Description..... | 85 |
+| 6.13.3.2 | Pre-conditions..... | 85 |
+| 6.13.3.3 | Service flows..... | 85 |
+| 6.13.3.4 | Post-conditions..... | 85 |
+| 6.13.3.5 | Potential requirements and gap analysis..... | 86 |
+| 6.14 | Use case: Data transmission in real time..... | 86 |
+| 6.14.1 | Description..... | 86 |
+| 6.14.2 | Pre-conditions..... | 86 |
+| 6.14.3 | Service flows..... | 86 |
+| 6.14.4 | Post-conditions..... | 86 |
+| 6.14.5 | Potential requirements and gap analysis..... | 87 |
+| 6.15 | On-train incoming voice or video communication from the Controller(s) of the train towards the drivers.... | 87 |
+| 6.15.1 | Introduction..... | 87 |
+| 6.15.2 | Use case: Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers..... | 88 |
+| 6.15.2.1 | Description..... | 88 |
+| 6.15.2.2 | Pre-conditions..... | 88 |
+| 6.15.2.3 | Service Flows..... | 88 |
+| 6.15.2.4 | Post-conditions..... | 88 |
+| 6.15.2.5 | Potential requirements and gap analysis..... | 89 |
+
+| | | |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------|----|
+| 6.15.3 | Use case: Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers..... | 89 |
+| 6.15.3.1 | Description..... | 89 |
+| 6.15.3.2 | Pre-conditions..... | 89 |
+| 6.15.3.3 | Service Flows..... | 89 |
+| 6.15.3.4 | Post-conditions..... | 89 |
+| 6.15.3.5 | Potential requirements and gap analysis..... | 89 |
+| 6.16 | Use cases on data communication for Train Operation System Communication..... | 90 |
+| 6.16.1 | Introduction..... | 90 |
+| 6.16.2 | Use case: Train dispatch order data communication between controller and driver..... | 90 |
+| 6.16.2.1 | Description..... | 90 |
+| 6.16.2.2 | Pre-conditions..... | 90 |
+| 6.16.2.3 | Service flows..... | 90 |
+| 6.16.2.4 | Post-conditions..... | 90 |
+| 6.16.2.5 | Potential requirements and gap analysis..... | 90 |
+| 6.16.3 | Use case: LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive..... | 91 |
+| 6.16.3.1 | Description..... | 91 |
+| 6.16.3.2 | Pre-conditions..... | 91 |
+| 6.16.3.3 | Service flows..... | 91 |
+| 6.16.3.4 | Post-conditions..... | 91 |
+| 6.16.3.5 | Potential requirements and gap analysis..... | 91 |
+| 6.16.4 | Use case: data communication for security between two approaching trains..... | 91 |
+| 6.16.4.1 | Description..... | 91 |
+| 6.16.4.2 | Pre-conditions..... | 91 |
+| 6.16.4.3 | Service flows..... | 92 |
+| 6.16.4.4 | Post-conditions..... | 92 |
+| 6.16.4.5 | Potential requirements and gap analysis..... | 92 |
+| 6.17 | On-train safety device to ground communication..... | 92 |
+| 6.17.1 | Introduction..... | 92 |
+| 6.17.2 | Use case: Initiation of safety device to ground data communication..... | 92 |
+
+| | | |
+|----------|-------------------------------------------------------------------------------------|-----|
+| 6.17.2.1 | Description..... | 92 |
+| 6.17.2.2 | Pre-conditions..... | 93 |
+| 6.17.2.3 | Service flows..... | 93 |
+| 6.17.2.4 | Post-conditions..... | 93 |
+| 6.17.2.5 | Potential requirements and gap analysis..... | 94 |
+| 6.18 | Train Integrity monitoring data communication..... | 95 |
+| 6.18.1 | Introduction..... | 95 |
+| 6.18.2 | Use case: Data communication for train integrity information exchange..... | 95 |
+| 6.18.2.1 | Description..... | 95 |
+| 6.18.2.2 | Pre-conditions..... | 95 |
+| 6.18.2.3 | Service flows..... | 95 |
+| 6.18.2.4 | Post-conditions..... | 96 |
+| 6.18.2.5 | Potential requirements and gap analysis..... | 97 |
+| 6.19 | Use case: Broadcast of public emergency warning information..... | 97 |
+| 6.19.1 | Introduction..... | 97 |
+| 6.19.2 | Description..... | 97 |
+| 6.19.2a | Pre-conditions..... | 98 |
+| 6.19.3 | Service flows..... | 98 |
+| 6.19.4 | Post-conditions..... | 98 |
+| 6.20 | Safety related critical advisory messaging..... | 99 |
+| 6.20.1 | Introduction..... | 99 |
+| 6.20.2 | Use case: Initiation/Termination of safety device to ground data communication..... | 99 |
+| 6.20.2.1 | Description..... | 99 |
+| 6.20.2.2 | Pre-conditions..... | 99 |
+| 6.20.2.3 | Service flows..... | 99 |
+| 6.20.2.4 | Post-conditions..... | 99 |
+| 6.20.2.5 | Potential requirements and gap analysis..... | 100 |
+| 6.20.3 | Use case: Service interworking with GSM-R..... | 100 |
+| 6.20.3.1 | Description..... | 100 |
+| 6.20.3.2 | Void..... | 100 |
+
+| | | |
+|----------|--------------------------------------------------------------------------------|-----|
+| 6.20.3.3 | Void..... | 100 |
+| 6.20.3.4 | Void..... | 100 |
+| 6.20.3.5 | Void..... | 100 |
+| 6.21 | Automatic Train Protection data communication..... | 100 |
+| 6.21.1 | Introduction..... | 100 |
+| 6.21.2 | Description..... | 101 |
+| 6.21.3 | Use case: Initiation of an Automatic Train Protection data communication..... | 101 |
+| 6.21.3.1 | Description..... | 101 |
+| 6.21.3.2 | Pre-conditions..... | 101 |
+| 6.21.3.3 | Service flows..... | 101 |
+| 6.21.3.4 | Post-conditions..... | 101 |
+| 6.21.3.5 | Potential requirements and gap analysis..... | 102 |
+| 6.21.4 | Use case: Termination of an Automatic Train Protection data communication..... | 102 |
+| 6.21.4.1 | Description..... | 102 |
+| 6.21.4.2 | Pre-conditions..... | 102 |
+| 6.21.4.3 | Service flows..... | 102 |
+| 6.21.4.4 | Post-conditions..... | 102 |
+| 6.21.4.5 | Potential requirements and gap analysis..... | 103 |
+| 6.22 | Voice communication transfer related use cases..... | 103 |
+| 6.22.1 | Introduction..... | 103 |
+| 6.22.2 | Use case: Transfer of an incoming voice communication..... | 103 |
+| 6.22.2.1 | Description..... | 103 |
+| 6.22.2.2 | Pre-conditions..... | 103 |
+| 6.22.2.3 | Service flows..... | 103 |
+| 6.22.2.4 | Post-conditions..... | 104 |
+| 6.22.2.5 | Potential requirements and gap analysis..... | 104 |
+| 6.22.3 | Use case: Transfer of an ongoing voice communication..... | 105 |
+| 6.22.3.1 | Description..... | 105 |
+| 6.22.3.2 | Pre-conditions..... | 105 |
+| 6.22.3.3 | Service flows..... | 105 |
+
+| | | |
+|----------|----------------------------------------------------------------------------------------------|-----|
+| 6.22.3.4 | Post-conditions..... | 105 |
+| 6.22.3.5 | Potential requirements and gap analysis..... | 105 |
+| 6.22.4 | Use case: Service interworking with GSM-R..... | 105 |
+| 6.22.4.1 | Description..... | 105 |
+| 6.22.4.2 | Pre-conditions..... | 105 |
+| 6.22.4.3 | Service flows..... | 106 |
+| 6.22.4.4 | Post-conditions..... | 106 |
+| 6.22.4.5 | Potential requirements and gap analysis..... | 106 |
+| 7 | Performance communication applications related use cases..... | 106 |
+| 7.1 | Use cases related to transmission of real time video..... | 106 |
+| 7.1.1 | Introduction..... | 106 |
+| 7.1.2 | Use Case: An FRMCS User requesting another FRMCS User to transmit real time video..... | 106 |
+| 7.1.2.1 | Description..... | 106 |
+| 7.1.2.2 | Pre-conditions..... | 106 |
+| 7.1.2.3 | Service flows..... | 107 |
+| 7.1.2.4 | Post-conditions..... | 107 |
+| 7.1.2.5 | Potential requirements and gap analysis..... | 107 |
+| 7.1.3 | Use Case: An FRMCS User receiving a real time video request to transmit real time video..... | 107 |
+| 7.1.3.1 | Description..... | 107 |
+| 7.1.3.2 | Pre-conditions..... | 107 |
+| 7.1.3.3 | Service flows..... | 108 |
+| 7.1.3.4 | Post-conditions..... | 108 |
+| 7.1.3.5 | Potential requirements and gap analysis..... | 108 |
+| 7.1.4 | Use case: An FRMCS User accepting a request to transmit real time video..... | 108 |
+| 7.1.4.1 | Description..... | 108 |
+| 7.1.4.2 | Pre-conditions..... | 108 |
+| 7.1.4.3 | Service flows..... | 108 |
+| 7.1.4.4 | Post-conditions..... | 108 |
+| 7.1.4.5 | Potential requirements and gap analysis..... | 109 |
+| 7.1.5 | Use case: An FRMCS User rejecting a request to transmit real time video..... | 109 |
+
+| | | |
+|---------|-----------------------------------------------------------------------------------------------------|-----|
+| 7.1.5.1 | Description..... | 109 |
+| 7.1.5.2 | Pre-conditions..... | 109 |
+| 7.1.5.3 | Service flows..... | 109 |
+| 7.1.5.4 | Post-conditions..... | 109 |
+| 7.1.5.5 | Potential requirements and gap analysis..... | 110 |
+| 7.1.6 | Use case: An FRMCS User ignoring a request to transmit real time video..... | 110 |
+| 7.1.6.1 | Description..... | 110 |
+| 7.1.6.2 | Pre-conditions..... | 110 |
+| 7.1.6.3 | Service flows..... | 110 |
+| 7.1.6.4 | Post-conditions..... | 110 |
+| 7.1.6.5 | Potential requirements and gap analysis..... | 110 |
+| 7.2 | Transfer of CCTV archives related use cases..... | 110 |
+| 7.2.1 | Introduction..... | 110 |
+| 7.2.2 | Use Case: Bulk Transfer of CCTV archives from Train to Ground..... | 111 |
+| 7.2.2.1 | Description..... | 111 |
+| 7.2.2.2 | Pre-conditions..... | 114 |
+| 7.2.2.3 | Service flows..... | 114 |
+| 7.2.2.4 | Post-conditions..... | 114 |
+| 7.2.2.5 | Potential requirements and gap analysis..... | 115 |
+| 7.3 | Use Case: Massive Inter-carriage data transfer..... | 115 |
+| 7.3.1 | Description..... | 115 |
+| 7.3.2 | Pre-conditions..... | 115 |
+| 7.3.3 | Service flows..... | 115 |
+| 7.3.4 | Post-conditions..... | 115 |
+| 7.3.5 | Potential requirements and gap analysis..... | 116 |
+| 7.4 | Void..... | 116 |
+| 7.5 | On-train outgoing voice communication from train staff towards a ground user related use cases..... | 116 |
+| 7.5.1 | Introduction..... | 116 |
+| 7.5.2 | Use case: Initiation of on-train outgoing voice communication from train staff..... | 116 |
+| 7.5.2.1 | Description..... | 116 |
+
+| | | |
+|---------|--------------------------------------------------------------------------------------|-----|
+| 7.5.2.2 | Pre-conditions..... | 116 |
+| 7.5.2.3 | Service flows..... | 116 |
+| 7.5.2.4 | Post-conditions..... | 117 |
+| 7.5.2.5 | Potential requirements and gap analysis..... | 118 |
+| 7.5.3 | Use case: Termination of on-train outgoing voice communication from train staff..... | 118 |
+| 7.5.3.1 | Description..... | 118 |
+| 7.5.3.2 | Pre-conditions..... | 119 |
+| 7.5.3.3 | Service flows..... | 119 |
+| 7.5.3.4 | Post-conditions..... | 119 |
+| 7.5.3.5 | Potential requirements and gap analysis..... | 120 |
+| 7.5.4 | Use case: Service interworking with GSM-R..... | 121 |
+| 7.5.4.1 | Description..... | 121 |
+| 7.5.4.2 | Pre-conditions..... | 121 |
+| 7.5.4.3 | Service flows..... | 121 |
+| 7.5.4.4 | Post-conditions..... | 121 |
+| 7.5.4.5 | Potential requirements and gap analysis..... | 122 |
+| 7.6 | Real-time video communication (video conferencing) related use cases..... | 122 |
+| 7.6.1 | Introduction..... | 122 |
+| 7.6.2 | Use case: Initiation of video conference..... | 123 |
+| 7.6.2.1 | Description..... | 123 |
+| 7.6.2.2 | Pre-conditions..... | 123 |
+| 7.6.2.3 | Service flows..... | 123 |
+| 7.6.2.4 | Post-conditions..... | 123 |
+| 7.6.2.5 | Potential requirements and gap analysis..... | 123 |
+| 7.6.3 | Use case: Leave and re-join a video conference..... | 123 |
+| 7.6.3.1 | Description..... | 123 |
+| 7.6.3.2 | Pre-conditions..... | 124 |
+| 7.6.3.3 | Service flows..... | 124 |
+| 7.6.3.4 | Post-conditions..... | 124 |
+| 7.6.3.5 | Potential requirements and gap analysis..... | 124 |
+
+| | | |
+|---------|---------------------------------------------------------------------------|-----|
+| 7.6.4 | Void..... | 124 |
+| 7.6.5 | Use case: Termination of a video conference..... | 124 |
+| 7.6.5.1 | Description..... | 124 |
+| 7.6.5.2 | Pre-conditions..... | 124 |
+| 7.6.5.3 | Service flows..... | 124 |
+| 7.6.5.4 | Post-conditions..... | 124 |
+| 7.6.5.5 | Potential requirements and gap analysis..... | 124 |
+| 7.6.6 | Use case: Changes from a video conference to a voice-only conference..... | 125 |
+| 7.6.6.1 | Description..... | 125 |
+| 7.6.6.2 | Pre-conditions..... | 125 |
+| 7.6.6.3 | Service flows..... | 125 |
+| 7.6.6.4 | Post-conditions..... | 125 |
+| 7.6.6.5 | Potential requirements and gap analysis..... | 125 |
+| 7.6.7 | Use case: Change from a voice-only conference to a video conference..... | 126 |
+| 7.6.7.1 | Description..... | 126 |
+| 7.6.7.2 | Pre-conditions..... | 126 |
+| 7.6.7.3 | Service flows..... | 126 |
+| 7.6.7.4 | Post-conditions..... | 126 |
+| 7.6.7.5 | Potential requirements and gap analysis..... | 126 |
+| 7.6.8 | Use case: Join an ongoing video conference..... | 127 |
+| 7.6.8.1 | Description..... | 127 |
+| 7.6.8.2 | Pre-conditions..... | 127 |
+| 7.6.8.3 | Service flows..... | 127 |
+| 7.6.8.4 | Post-conditions..... | 127 |
+| 7.6.8.5 | Potential requirements and gap analysis..... | 127 |
+| 8 | Business communication applications related use cases..... | 127 |
+| 8.1 | Multimedia applications related use cases..... | 127 |
+| 8.1.1 | Introduction..... | 127 |
+| 8.2 | Use Case: Live streaming of multimedia..... | 128 |
+| 8.2.1 | Description..... | 128 |
+
+| | | |
+|---------|-----------------------------------------------------------------|-----|
+| 8.2.2 | Pre-conditions..... | 128 |
+| 8.2.3 | Service flows..... | 128 |
+| 8.2.4 | Post-conditions..... | 128 |
+| 8.2.5 | Potential requirements and gap analysis..... | 128 |
+| 8.3 | Use Case: Bulk transfer of multimedia from ground to train..... | 128 |
+| 8.3.1 | Description..... | 128 |
+| 8.3.2 | Pre-conditions..... | 129 |
+| 8.3.3 | Service flows..... | 129 |
+| 8.3.4 | Post-conditions..... | 129 |
+| 8.3.5 | Potential requirements and gap analysis..... | 129 |
+| 9 | Critical support applications related use cases..... | 130 |
+| 9.1 | Overview..... | 130 |
+| 9.2 | Assured voice communication (AVC)..... | 130 |
+| 9.2.1 | Introduction..... | 130 |
+| 9.2.2 | Use case: Invocation of Assured Voice Communication..... | 130 |
+| 9.2.2.1 | Description..... | 130 |
+| 9.2.2.2 | Pre-conditions..... | 130 |
+| 9.2.2.3 | Service flows..... | 130 |
+| 9.2.2.4 | Post-conditions..... | 130 |
+| 9.2.2.5 | Potential requirements and gap analysis..... | 131 |
+| 9.2.3 | Use case: Stopping Assured Voice Communication..... | 131 |
+| 9.2.3.1 | Description..... | 131 |
+| 9.2.3.2 | Pre-conditions..... | 131 |
+| 9.2.3.3 | Service flows..... | 131 |
+| 9.2.3.4 | Post-conditions..... | 131 |
+| 9.2.3.5 | Potential requirements and gap analysis..... | 132 |
+| 9.2.4 | Use case: Degradation of a communication link..... | 132 |
+| 9.2.4.1 | Description..... | 132 |
+| 9.2.4.2 | Pre-conditions..... | 132 |
+| 9.2.4.3 | Service flows..... | 132 |
+
+| | | |
+|---------|---------------------------------------------------------|-----|
+| 9.2.4.4 | Post-conditions..... | 133 |
+| 9.2.4.5 | Potential requirements and gap analysis..... | 134 |
+| 9.2.5 | Use case: Extension of Assured Voice Communication..... | 135 |
+| 9.2.5.1 | Description..... | 135 |
+| 9.2.5.2 | Pre-conditions..... | 135 |
+| 9.2.5.3 | Service flows..... | 135 |
+| 9.2.5.4 | Post-conditions..... | 135 |
+| 9.2.5.5 | Potential requirements and gap analysis..... | 135 |
+| 9.3 | Functional identities and role management..... | 135 |
+| 9.3.1 | Introduction..... | 135 |
+| 9.3.2 | General pre-conditions..... | 136 |
+| 9.3.2.1 | Potential requirements and gap analysis..... | 139 |
+| 9.3.3 | Use case: Registration to a functional identity..... | 139 |
+| 9.3.3.1 | Description..... | 139 |
+| 9.3.3.2 | Pre-conditions..... | 139 |
+| 9.3.3.3 | Service flows..... | 139 |
+| 9.3.3.4 | Post-conditions..... | 140 |
+| 9.3.3.5 | Potential requirements and gap analysis..... | 141 |
+| 9.3.4 | Use case: Deregistration of a functional identity..... | 142 |
+| 9.3.4.1 | Description..... | 142 |
+| 9.3.4.2 | Pre-conditions..... | 142 |
+| 9.3.4.3 | Service flows..... | 142 |
+| 9.3.4.4 | Post-conditions..... | 142 |
+| 9.3.4.5 | Potential requirements and gap analysis..... | 143 |
+| 9.3.5 | Use case: User log-in to the FRMCS System..... | 143 |
+| 9.3.5.1 | Description..... | 143 |
+| 9.3.5.2 | Pre-conditions..... | 143 |
+| 9.3.5.3 | Service flows..... | 144 |
+| 9.3.5.4 | Post-conditions..... | 144 |
+| 9.3.5.5 | Potential requirements and gap analysis..... | 144 |
+
+| | | |
+|---------|---------------------------------------------------------------------|-----|
+| 9.3.6 | Use case: User log-out from FRMCS System..... | 144 |
+| 9.3.6.1 | Description..... | 144 |
+| 9.3.6.2 | Pre-conditions..... | 144 |
+| 9.3.6.3 | Service flows..... | 144 |
+| 9.3.6.4 | Post-conditions..... | 145 |
+| 9.3.6.5 | Potential requirements and gap analysis..... | 145 |
+| 9.3.7 | Use case: Presentation of identities..... | 145 |
+| 9.3.7.1 | Description..... | 145 |
+| 9.3.7.2 | Pre-conditions..... | 146 |
+| 9.3.7.3 | Service flows..... | 146 |
+| 9.3.7.4 | Post-conditions..... | 146 |
+| 9.3.7.5 | Potential requirements and gap analysis..... | 147 |
+| 9.3.8 | Use case: Interrogation of identities within a certain context..... | 147 |
+| 9.3.8.1 | Description..... | 147 |
+| 9.3.8.2 | Pre-conditions..... | 147 |
+| 9.3.8.3 | Service flows..... | 147 |
+| 9.3.8.4 | Post-conditions..... | 148 |
+| 9.3.8.5 | Potential requirements and gap analysis..... | 149 |
+| 9.3.9.5 | Potential requirements and gap analysis..... | 152 |
+| 9.4 | Location services related use cases..... | 153 |
+| 9.4.1 | Introduction..... | 153 |
+| 9.4.2 | Use Case: Provide location information..... | 153 |
+| 9.4.2.1 | Description..... | 153 |
+| 9.4.2.2 | Pre-conditions..... | 153 |
+| 9.4.2.3 | Service flows..... | 153 |
+| 9.4.2.4 | Post-conditions..... | 154 |
+| 9.4.2.5 | Potential requirements and gap analysis..... | 154 |
+| 9.4.3 | Use Case: Request for location information..... | 154 |
+| 9.4.3.1 | Description..... | 154 |
+| 9.4.3.2 | Pre-conditions..... | 154 |
+
+| | | |
+|---------|----------------------------------------------------------------------------|-----|
+| 9.4.3.3 | Service flows..... | 155 |
+| 9.4.3.4 | Post-conditions..... | 155 |
+| 9.4.3.5 | Potential requirements and gap analysis..... | 155 |
+| 9.4.4 | Use Case: Request for identities in a certain area..... | 155 |
+| 9.4.4.1 | Description..... | 155 |
+| 9.4.4.2 | Pre-conditions..... | 156 |
+| 9.4.4.3 | Service flows..... | 156 |
+| 9.4.4.4 | Post-conditions..... | 156 |
+| 9.4.4.5 | Potential requirements and gap analysis..... | 156 |
+| 9.5 | FRMCS User communication handling related use cases..... | 156 |
+| 9.5.1 | Introduction..... | 156 |
+| 9.5.2 | Use Case: Inviting-FRMCS User(s) to a voice communication..... | 157 |
+| 9.5.2.1 | Description..... | 157 |
+| 9.5.2.2 | Pre-conditions..... | 157 |
+| 9.5.2.3 | Service flows..... | 157 |
+| 9.5.2.4 | Post-conditions..... | 157 |
+| 9.5.2.5 | Potential requirements and gap analysis..... | 158 |
+| 9.5.3 | Use Case: FRMCS User receiving an invitation to a voice communication..... | 158 |
+| 9.5.3.1 | Description..... | 158 |
+| 9.5.3.2 | Pre-conditions..... | 158 |
+| 9.5.3.3 | Service flows..... | 158 |
+| 9.5.3.4 | Post-conditions..... | 158 |
+| 9.5.3.5 | Potential requirements and gap analysis..... | 159 |
+| 9.5.4 | Use case: FRMCS User accepting an invitation to a voice communication..... | 159 |
+| 9.5.4.1 | Description..... | 159 |
+| 9.5.4.2 | Pre-conditions..... | 159 |
+| 9.5.4.3 | Service flows..... | 159 |
+| 9.5.4.4 | Post-conditions..... | 159 |
+| 9.5.4.5 | Potential requirements and gap analysis..... | 160 |
+| 9.5.5 | Use case: FRMCS User rejecting an invitation to a voice communication..... | 160 |
+
+| | | |
+|---------|---------------------------------------------------------------------------|-----|
+| 9.5.5.1 | Description..... | 160 |
+| 9.5.5.2 | Pre-conditions..... | 160 |
+| 9.5.5.3 | Service flows..... | 160 |
+| 9.5.5.4 | Post-conditions..... | 160 |
+| 9.5.5.5 | Potential requirements and gap analysis..... | 161 |
+| 9.5.6 | Use case: FRMCS User ignoring an invitation to a voice communication..... | 161 |
+| 9.5.6.1 | Description..... | 161 |
+| 9.5.6.2 | Pre-conditions..... | 161 |
+| 9.5.6.3 | Service flows..... | 161 |
+| 9.5.6.4 | Post-conditions..... | 161 |
+| 9.5.6.5 | Potential requirements and gap analysis..... | 161 |
+| 9.5.7 | Service interworking with GSM-R..... | 161 |
+| 9.5.7.1 | Description..... | 161 |
+| 9.5.7.2 | Pre-condition..... | 163 |
+| 9.5.7.3 | Service flow..... | 163 |
+| 9.5.7.4 | Post-condition..... | 163 |
+| 9.5.7.5 | Potential requirements..... | 164 |
+| 9.6 | Void..... | 164 |
+| 9.7 | Multiuser talker control related use cases..... | 164 |
+| 9.7.1 | General Description and potential requirements..... | 164 |
+| 9.7.1.1 | General Description..... | 164 |
+| 9.7.1.2 | Potential requirements and gap analysis..... | 164 |
+| 9.7.2 | Use case: Set the number of simultaneous talkers..... | 164 |
+| 9.7.2.1 | Description..... | 164 |
+| 9.7.2.2 | Pre-conditions..... | 164 |
+| 9.7.2.3 | Service flows..... | 165 |
+| 9.7.2.4 | Post-conditions..... | 165 |
+| 9.7.2.5 | Potential requirements and gap analysis..... | 165 |
+| 9.7.3 | Use case: Set initial talker permissions and priorities..... | 165 |
+| 9.7.3.1 | Description..... | 165 |
+
+| | | |
+|---------|----------------------------------------------|-----|
+| 9.7.3.2 | Pre-conditions..... | 165 |
+| 9.7.3.3 | Service flows..... | 166 |
+| 9.7.3.4 | Post-conditions..... | 166 |
+| 9.7.3.5 | Potential requirements and gap analysis..... | 167 |
+| 9.7.4 | Use case: Request permission to talk..... | 167 |
+| 9.7.4.1 | Description..... | 167 |
+| 9.7.4.2 | Pre-conditions..... | 168 |
+| 9.7.4.3 | Service flows..... | 168 |
+| 9.7.4.4 | Post-conditions..... | 168 |
+| 9.7.4.5 | Potential requirements and gap analysis..... | 168 |
+| 9.7.5 | Use case: Grant permission to talk..... | 168 |
+| 9.7.5.1 | Description..... | 168 |
+| 9.7.5.2 | Pre-conditions..... | 168 |
+| 9.7.5.3 | Service flows..... | 169 |
+| 9.7.5.4 | Post-conditions..... | 169 |
+| 9.7.5.5 | Potential requirements and gap analysis..... | 170 |
+| 9.7.6 | Use case: Revoke permission to talk..... | 170 |
+| 9.7.6.1 | Description..... | 170 |
+| 9.7.6.2 | Pre-conditions..... | 171 |
+| 9.7.6.3 | Service flows..... | 171 |
+| 9.7.6.4 | Post-conditions..... | 171 |
+| 9.7.6.5 | Potential requirements and gap analysis..... | 172 |
+| 9.8 | Authorisation of communication..... | 172 |
+| 9.8.1 | Introduction..... | 172 |
+| 9.8.2 | Use case: Permit / deny communication..... | 172 |
+| 9.8.2.1 | Description..... | 172 |
+| 9.8.2.2 | Pre-conditions..... | 172 |
+| 9.8.2.3 | Service flows..... | 172 |
+| 9.8.2.4 | Post-conditions..... | 173 |
+| 9.8.2.5 | Potential requirements and gap analysis..... | 173 |
+
+| | | |
+|----------|-------------------------------------------------------------------------------------------------------------|-----|
+| 9.9 | Authorisation of application..... | 173 |
+| 9.9.1 | Introduction..... | 173 |
+| 9.9.2 | Use case: Enabling/Disabling applications..... | 174 |
+| 9.9.2.1 | Description..... | 174 |
+| 9.9.2.2 | Pre-conditions..... | 174 |
+| 9.9.2.3 | Service flows..... | 174 |
+| 9.9.2.4 | Post-conditions..... | 174 |
+| 9.9.2.5 | Potential requirements and gap analysis..... | 175 |
+| 9.9.3 | Use case: Robust mission critical group communication services..... | 176 |
+| 9.9.3.1 | Description..... | 176 |
+| 9.9.3.2 | Pre-conditions..... | 176 |
+| 9.9.3.3 | Service Flows..... | 177 |
+| 9.9.3.4 | Post-conditions..... | 177 |
+| 9.9.3.5 | Potential requirements and gap analysis..... | 178 |
+| 9.9.3a | Use case: Enabling/Disabling communication privileges per FRMCS User based on identities/talker status..... | 178 |
+| 9.9.3a.1 | Description..... | 178 |
+| 9.9.3a.2 | Pre-conditions..... | 178 |
+| 9.9.3a.3 | Service flows..... | 178 |
+| 9.9.3a.4 | Post-conditions..... | 179 |
+| 9.9.3a.5 | Potential requirements and gap analysis..... | 180 |
+| 9.10 | Sharing FRMCS Equipment by FRMCS Users..... | 182 |
+| 9.10.1 | Description..... | 182 |
+| 9.10.2 | Pre-conditions..... | 182 |
+| 9.10.3 | Service Flows..... | 182 |
+| 9.10.4 | Post-conditions..... | 182 |
+| 9.10.5 | Potential requirements and gap analysis..... | 183 |
+| 9.11 | FRMCS naming authority..... | 183 |
+| 9.11.1 | Description..... | 183 |
+| 9.11.2 | Pre-conditions..... | 183 |
+| 9.11.3 | Service Flows..... | 183 |
+
+| | | |
+|----------|----------------------------------------------|-----|
+| 9.11.4 | Post-conditions..... | 183 |
+| 9.11.5 | Potential requirements and gap analysis..... | 184 |
+| 9.12 | Wayside-Centric Automatic Train Control..... | 184 |
+| 9.12.1 | Description..... | 184 |
+| 9.12.2 | Pre-conditions..... | 184 |
+| 9.12.3 | Service flows..... | 185 |
+| 9.12.4 | Post-conditions..... | 185 |
+| 9.12.5 | Potential requirements and gap analysis..... | 185 |
+| 9.13 | Autonomous Train Control and Operation..... | 185 |
+| 9.13.1 | Description..... | 185 |
+| 9.13.2 | Pre-conditions..... | 186 |
+| 9.13.3 | Service Flows..... | 186 |
+| 9.13.4 | Post-conditions..... | 186 |
+| 9.13.5 | Potential requirements and gap analysis..... | 187 |
+| 9.14 | Virtual Coupling..... | 187 |
+| 9.14.1 | Description..... | 187 |
+| 9.14.2 | Pre-conditions..... | 188 |
+| 9.14.3 | Service Flows..... | 189 |
+| 9.14.4 | Post-conditions..... | 189 |
+| 9.14.5 | Potential requirements and gap analysis..... | 190 |
+| 9.15 | Composite-based train operation..... | 190 |
+| 9.15.1 | Description..... | 190 |
+| 9.15.2 | Pre-conditions..... | 190 |
+| 9.15.3 | Service Flows..... | 190 |
+| 9.15.4 | Post-conditions..... | 191 |
+| 9.15.5 | Potential requirements and gap analysis..... | 191 |
+| 9.16 | Arbitration related use cases..... | 191 |
+| 9.16.1 | Introduction..... | 191 |
+| 9.16.2 | Use case: Arbitration..... | 192 |
+| 9.16.2.1 | Description..... | 192 |
+
+| | | |
+|----------|--------------------------------------------------------------------------------------------|-----|
+| 9.16.2.2 | Pre-conditions..... | 192 |
+| 9.16.2.3 | Service flows..... | 192 |
+| 9.16.2.4 | Post-conditions..... | 192 |
+| 9.16.2.5 | Potential requirements and gap analysis..... | 192 |
+| 9.16.3 | Use case: Arbitration for communication auto-connection..... | 193 |
+| 9.16.3.1 | Description..... | 193 |
+| 9.16.3.2 | Pre-conditions..... | 193 |
+| 9.16.3.3 | Service flows..... | 193 |
+| 9.16.3.4 | Post-conditions..... | 194 |
+| 9.16.3.5 | Potential requirements and gap analysis..... | 195 |
+| 9.17 | Data communication to exchange key information for train safety application use cases..... | 196 |
+| 9.17.1 | Introduction..... | 196 |
+| 9.17.2 | Use case: Initiation of a Key Management data communication..... | 196 |
+| 9.17.2.1 | Description..... | 196 |
+| 9.17.2.2 | Pre-conditions..... | 196 |
+| 9.17.2.3 | Service flows..... | 196 |
+| 9.17.2.4 | Post-conditions..... | 196 |
+| 9.17.2.5 | Potential requirements and gap analysis..... | 198 |
+| 9.17.3 | Use case: Termination of a Key Management data communication..... | 199 |
+| 9.17.3.1 | Description..... | 199 |
+| 9.17.3.2 | Pre-conditions..... | 199 |
+| 9.17.3.3 | Service flows..... | 199 |
+| 9.17.3.4 | Post-conditions..... | 199 |
+| 9.17.3.5 | Potential requirements and gap analysis..... | 200 |
+| 9.17.4 | Use case: service interworking and service continuation with GSM-R..... | 200 |
+| 9.17.4.1 | Description..... | 200 |
+| 9.17.4.2 | Pre-conditions..... | 200 |
+| 9.17.4.3 | Service flows..... | 200 |
+| 9.17.4.4 | Post-conditions..... | 201 |
+
+| | | |
+|----------|------------------------------------------------------------------------------------|-----|
+| 10 | Performance support applications related use cases..... | 201 |
+| 11 | Business support applications related use cases..... | 201 |
+| 11.1 | Charging and Billing information related use cases..... | 201 |
+| 11.1.1 | Introduction..... | 201 |
+| 11.1.2 | Use case: Obtaining charging and billing information..... | 202 |
+| 11.1.2.1 | Description..... | 202 |
+| 11.1.2.2 | Pre-conditions..... | 202 |
+| 11.1.2.3 | Service flows..... | 202 |
+| 11.1.2.4 | Post-conditions..... | 202 |
+| 11.1.2.5 | Potential requirements and gap analysis..... | 202 |
+| 12 | FRMCS System principles related use cases..... | 202 |
+| 12.1 | FRMCS System principles overview..... | 202 |
+| 12.2 | Area Broadcast Group Communication interworking between GSM-R and FRMCS Users..... | 203 |
+| 12.2.1 | Description..... | 203 |
+| 12.2.2 | Pre-condition..... | 203 |
+| 12.2.3 | Service flow..... | 204 |
+| 12.2.4 | Post-condition..... | 204 |
+| 12.2.5 | Potential requirements..... | 204 |
+| 12.3 | Location Service interworking between GSM-R and FRMCS Users..... | 204 |
+| 12.3.1 | Description..... | 204 |
+| 12.3.2 | Pre-condition..... | 204 |
+| 12.3.3 | Service flow..... | 205 |
+| 12.3.4 | Post-condition..... | 205 |
+| 12.3.5 | Potential requirements..... | 205 |
+| 12.4 | Presence interworking between GSM-R and FRMCS Users..... | 205 |
+| 12.4.1 | Description..... | 205 |
+| 12.4.2 | Pre-condition..... | 205 |
+| 12.4.3 | Service flow..... | 205 |
+| 12.4.4 | Post-condition..... | 205 |
+
+| | | |
+|----------|-----------------------------------------------------------------------------------------------------------------------------|-----|
+| 12.4.5 | Potential requirements..... | 205 |
+| 12.5 | Point to Point communication between GSM-R and FRMCS Users..... | 206 |
+| 12.5.1 | Description..... | 206 |
+| 12.5.2 | Pre-condition..... | 206 |
+| 12.5.3 | Service flow..... | 206 |
+| 12.5.4 | Post-condition..... | 206 |
+| 12.5.5 | Potential requirements..... | 206 |
+| 12.6 | Interworking with legacy systems including LMR..... | 206 |
+| 12.6.1 | Description..... | 206 |
+| 12.6.2 | Pre-conditions..... | 206 |
+| 12.6.3 | Service flows..... | 207 |
+| 12.6.4 | Post-conditions..... | 207 |
+| 12.6.5 | Potential requirements and gap analysis..... | 207 |
+| 12.7 | Use case: Builds stable positioning framework for FRMCS services and devices including trainborne and handheld devices..... | 207 |
+| 12.7.1 | Description..... | 207 |
+| 12.7.2 | Pre-conditions..... | 208 |
+| 12.7.3 | Service flows..... | 208 |
+| 12.7.4 | Post-conditions..... | 208 |
+| 12.7.5 | Potential requirements and gap analysis..... | 208 |
+| 12.8 | Interworking between GSM-R and FRMCS..... | 208 |
+| 12.8.1 | Introduction..... | 208 |
+| 12.8.2 | Circuit Switched interworking between GSM-R and FRMCS..... | 209 |
+| 12.8.2.1 | Description..... | 209 |
+| 12.8.2.2 | Pre-conditions..... | 209 |
+| 12.8.2.3 | Service flows..... | 209 |
+| 12.8.2.4 | Post-conditions..... | 209 |
+| 12.8.2.5 | Potential requirements and gap analysis..... | 210 |
+| 12.8.3 | Packet Switched interworking between GSM-R and FRMCS..... | 210 |
+| 12.8.3.1 | Description..... | 210 |
+| 12.8.3.2 | Pre-conditions..... | 210 |
+
+| | | |
+|-----------|-------------------------------------------------------------------------------------------------------------|-----|
+| 12.8.3.3 | Service flows..... | 210 |
+| 12.8.3.4 | Post-conditions..... | 210 |
+| 12.8.3.5 | Potential requirements and gap analysis..... | 211 |
+| 12.8.4 | SMS/SDS interworking between GSM-R and FRMCS..... | 211 |
+| 12.8.4.1 | Description..... | 211 |
+| 12.8.4.2 | Pre-conditions..... | 211 |
+| 12.8.4.3 | Service Flows..... | 211 |
+| 12.8.4.4 | Post-conditions..... | 211 |
+| 12.8.4.5 | Potential requirements and gap analysis..... | 211 |
+| 12.9 | Use case: Bearer flexibility..... | 211 |
+| 12.9.1 | Description..... | 211 |
+| 12.9.2 | Pre-conditions..... | 212 |
+| 12.9.3 | Service flows..... | 212 |
+| 12.9.4 | Post-conditions..... | 213 |
+| 12.9.5 | Potential requirements and gap analysis..... | 215 |
+| 12.10 | Use Case: QoS in a railway environment..... | 216 |
+| 12.10.1 | Introduction..... | 216 |
+| 12.10.2 | Use case: Quality of Service and railway environment..... | 217 |
+| 12.10.2.1 | Description..... | 217 |
+| 12.10.2.2 | Pre-conditions..... | 217 |
+| 12.10.2.3 | Service flows..... | 217 |
+| 12.10.2.4 | Post-conditions..... | 220 |
+| 12.10.2.5 | Potential requirements and gap analysis..... | 220 |
+| 12.11 | Use case: Provide broadband and mission critical services with seamless connectivity..... | 225 |
+| 12.11.1 | Description..... | 225 |
+| 12.11.2 | Pre-conditions..... | 225 |
+| 12.11.3 | Service flows..... | 225 |
+| 12.11.4 | Post-conditions..... | 226 |
+| 12.11.5 | Potential requirements and gap analysis..... | 226 |
+| 12.12 | Use case: Offer railway services high-quality control functions with real-time train status monitoring..... | 226 |
+
+| | | |
+|-----------|-------------------------------------------------------------------|-----|
+| 12.12.1 | Description..... | 226 |
+| 12.12.2 | Pre-conditions..... | 226 |
+| 12.12.3 | Service flows..... | 227 |
+| 12.12.4 | Post-conditions..... | 227 |
+| 12.12.5 | Potential requirements and gap analysis..... | 227 |
+| 12.13 | Use case: Provide call priority during interworking with LMR..... | 227 |
+| 12.13.1 | Description..... | 227 |
+| 12.13.2 | Pre-conditions..... | 228 |
+| 12.13.3 | Service flows..... | 228 |
+| 12.13.4 | Post-conditions..... | 228 |
+| 12.13.5 | Potential requirements and gap analysis..... | 229 |
+| 12.14 | Use Case: FRMCS Positioning Accuracy..... | 229 |
+| 12.14.1 | Introduction..... | 229 |
+| 12.14.2 | Use case: FRMCS Positioning Accuracy..... | 230 |
+| 12.14.2.1 | Description..... | 230 |
+| 12.14.2.2 | Pre-conditions..... | 231 |
+| 12.14.2.3 | Service flows..... | 231 |
+| 12.14.2.4 | Post-conditions..... | 232 |
+| 12.14.2.5 | Potential requirements and gap analysis..... | 232 |
+| 12.15 | Use Case: FRMCS System security framework..... | 232 |
+| 12.15.1 | Introduction..... | 232 |
+| 12.15.2 | Use case: FRMCS System security framework..... | 233 |
+| 12.15.2.1 | Description..... | 233 |
+| 12.15.2.2 | Pre-conditions..... | 233 |
+| 12.15.2.3 | Service flows..... | 233 |
+| 12.15.2.4 | Post-conditions..... | 233 |
+| 12.15.2.5 | Potential requirements and gap analysis..... | 234 |
+| 12.16 | Use Case: Interworking to external networks..... | 235 |
+| 12.16.1 | Introduction..... | 235 |
+| 12.16.2.2 | Pre-conditions..... | 236 |
+
+| | | |
+|-----------|----------------------------------------------------------------|-----|
+| 12.16.2.3 | Service flows..... | 236 |
+| 12.16.2.4 | Post-conditions..... | 237 |
+| 12.16.2.5 | Potential requirements and gap analysis..... | 238 |
+| 12.17 | Use Case: FRMCS On-network/Off-network communication..... | 239 |
+| 12.17.1 | Introduction..... | 239 |
+| 12.17.2 | Use case: On-network/Off-network communication..... | 240 |
+| 12.17.2.1 | Description..... | 240 |
+| 12.17.2.2 | Pre-conditions..... | 242 |
+| 12.17.2.3 | Service flows..... | 242 |
+| 12.17.2.4 | Post-conditions..... | 243 |
+| 12.17.2.5 | Potential requirements and gap analysis..... | 244 |
+| 12.18 | Call restriction service..... | 245 |
+| 12.18.1 | Description..... | 245 |
+| 12.18.2 | Pre-conditions..... | 245 |
+| 12.18.3 | Service Flows..... | 245 |
+| 12.18.4 | Post-conditions..... | 245 |
+| 12.18.5 | Potential requirements and gap analysis..... | 245 |
+| 12.19 | Allocation and isolation of FRMCS communication resources..... | 245 |
+| 12.19.1 | Introduction..... | 245 |
+| 12.19.2 | Use case: Isolation of FRMCS communication resources..... | 246 |
+| 12.19.2.1 | Description..... | 246 |
+| 12.19.2.2 | Pre-conditions..... | 246 |
+| 12.19.2.3 | Service flows..... | 246 |
+| 12.19.2.4 | Post-conditions..... | 246 |
+| 12.19.2.5 | Potential requirements and gap analysis..... | 247 |
+| 12.20 | FRMCS Equipment capabilities for multiple FRMCS Users..... | 247 |
+| 12.20.1 | Introduction..... | 247 |
+| 12.20.2 | Description..... | 248 |
+| 12.20.3 | Pre-conditions..... | 248 |
+| 12.20.4 | Service flows..... | 248 |
+
+| | | |
+|-----------|-------------------------------------------------------------------------------------------------|-----|
+| 12.20.5 | Post-conditions..... | 248 |
+| 12.20.6 | Potential requirements and gap analysis..... | 248 |
+| 12.21 | FRMCS System/FRMCS User roaming capabilities..... | 248 |
+| 12.21.1 | Introduction..... | 248 |
+| 12.21.2 | Use case: FRMCS User is relocating towards a Visited (FRMCS) Network..... | 249 |
+| 12.21.2.1 | Description..... | 249 |
+| 12.21.2.2 | Pre-conditions..... | 249 |
+| 12.21.2.3 | Service flows..... | 249 |
+| 12.21.2.4 | Post-conditions..... | 249 |
+| 12.21.2.5 | Potential requirements and gap analysis..... | 250 |
+| 12.21.3 | Use case: Functional Identities in FRMCS Roaming situations..... | 250 |
+| 12.21.3.1 | Description..... | 250 |
+| 12.21.3.2 | Pre-conditions..... | 251 |
+| 12.21.3.3 | Service flows..... | 251 |
+| 12.21.3.4 | Post-conditions..... | 251 |
+| 12.21.3.5 | Potential requirements and gap analysis..... | 252 |
+| 12.22 | Use case: Availability – increasing measures..... | 252 |
+| 12.22.1 | Description..... | 252 |
+| 12.22.2 | Pre-conditions..... | 253 |
+| 12.22.3 | Service flows..... | 253 |
+| 12.22.4 | Post-conditions..... | 253 |
+| 12.22.5 | Potential requirements and gap analysis..... | 253 |
+| 12.23 | Use case: Flexible use of available contiguous spectrum blocks(s) and related bandwidth(s)..... | 253 |
+| 12.23.1 | Introduction..... | 253 |
+| 12.23.2 | Description..... | 254 |
+| 12.23.3 | Pre-conditions..... | 254 |
+| 12.23.4 | Service flows..... | 254 |
+| 12.23.5 | Post-conditions..... | 254 |
+| 12.23.6 | Potential requirements and gap analysis..... | 254 |
+
+| | | |
+|-----------------|------------------------------------------------------------------------------------------------------------------------------|------------|
+| 13 | Potential New Requirements..... | 254 |
+| 14 | Conclusion and Recommendations..... | 254 |
+| <b>Annex A:</b> | <b>Examples of Role management.....</b> | <b>255</b> |
+| <b>Annex B:</b> | <b>Minimum functional and performance requirements for FRMCS from a perspective of Korea LTE-based railway services.....</b> | <b>257</b> |
+| <b>Annex C:</b> | <b>Applicability to On-network/Off-network communication.....</b> | <b>261</b> |
+| <b>Annex D:</b> | <b>Change history.....</b> | <b>266</b> |
+
+## Foreword
+
+This Technical Report 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 railway community is considering a successor communication system to GSM-R, as the forecasted obsolescence of the 2G-based GSM-R technology is envisaged around 2030, with first FRMCS trial implementations expected to start around 2020.
+
+The Future Railway Mobile Communication System (FRMCS) Functional Working Group (FWG) of the International Union of Railways (UIC) have investigated and summarised their requirements for the next generation railway communication system in the Future Railway Mobile Communication User Requirements Specification (FRMCS URS) [2]. The present document is based on this input given by the UIC/ETSI TC-RT
+
+---
+
+# 1 Scope
+
+The present document analyses FRMCS Use cases, system principles of FRMCS and Interworking between GSM-R and FRMCS in order to derive potential requirements.
+
+---
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 36.213 V14.0.0, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial radio Access (E-UTRA); Physical layer procedures, 2016.
+- [3] 3GPP TS 23.179 V13.3.0, Technical Specification Group Services and System Aspects; Functional architecture and information flows to support mission critical communication services; Stage 2. 2016.
+- [4] TTA TTAK.KO-06.0437, LTE Based Railway Communication System Requirements (Conventional and High Speed Railway), Dec. 2016.
+- [5] TTA TTAK.KO-06.0370, User Requirements for LTE-Based Railway Communication System, Oct. 2014.
+- [6] TTA TTAK KO-06.0-369, Functional Requirements for LTE-Based Communication System, Oct. 2014.
+- [7] Y.-S. Song, J. Kim, S. W. Choi, and Y.-K. Kim, "Long term evolution for wireless railway communications: Testbed deployment and performance evaluation," *IEEE Comm. Mag.*, Feb. 2016.
+- [8] J. Kim, S. W. Choi, Y.-S. Song, and Y.-K. Kim, "Automatic train control over LTE: Design and performance evaluation," *IEEE Comm. Mag.*, Oct. 2015.
+- [9] UNISIG Subset-041 ERTMS/ETCS Performance Requirements for Interoperability
+- [10] UIC FU-7100: "FRMCS User Requirements Specification".
+- [11] UIC MG-7900: "FRMCS Use Cases".
+- [12] UIC CODE 950: "EIRENE Functional Requirements Specification (FRS)".
+- [13] UIC CODE 951: "EIRENE System Requirements Specification (SRS)".
+
+## 3 Definitions, and abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Automatic Train Operation (ATO):** Automatic Train Operation applications are responsible for acceleration to the permitted speed, speed reduction where necessary due to speed restrictions and stop at designated stations in the correct location.
+
+**Automatic Train Protection (ATP):** Automatic Train Protection applications are responsible for giving Limit of Movement Authority to a train based on the train's current speed, its braking capability and the distance it can go before it must stop.
+
+**Balise:** An electronic beacon or transponder placed between the rails of a railway as part of an automatic train protection or operation (ATP/ATO) system.
+
+**Business communication applications:** communication applications that support the railway business operation in general, such as wireless internet, etc.
+
+**Controller (Train Controller):** A Ground FRMCS User provided with special capabilities by the FRMCS System.
+
+**Driver (Train Driver):** A Mobile FRMCS User provided with special capabilities by the FRMCS System.
+
+**External System(s):** A general category of stationary FRMCS Users. For example, External Systems could be systems monitoring for trains passing a red light to initiate a railway emergency call.
+
+**FRMCS Application:** The application on a 3GPP UE offering railway specific communication services to the FRMCS User by making use of the communication capabilities offered by the 3GPP UE and the 3GPP network.
+
+**FRMCS Equipment Identity:** The identity by which a FRMCS equipment can be addressed.
+
+**FRMCS Equipment Type:** Indicates the purpose the FRMCS equipment is being used for, FRMCS equipment of different equipment types do have different capabilities.
+
+**FRMCS Equipment:** The FRMCS Equipment consists of a 3GPP UE and a FRMCS Application residing on it. It may be combined with legacy railway communication equipment (e.g. GSM-R or TRS)
+
+**FRMCS Functional Identity:** The identity related to a user or related to the equipment, as specified in 9.3 "Role management and presence" indicating its special Role (e.g. as Driver of a specific train, usually a train number) can be addressed.
+
+**FRMCS Network:** this is a sub-part of the FRMCS System.
+
+**FRMCS Roaming:** The ability for a FRMCS User to make use of FRMCS Applications in a Visited (FRMCS) Network.
+
+**FRMCS System:** The system providing railway specific communication constituted of the FRMCS Equipment, the 3GPP transport and the application servers in the network. Legacy networks are not included in the FRMCS System.
+
+**FRMCS User Identity:** The identity by which a FRMCS User can be addressed.
+
+**FRMCS User:** A human user or a machine making use of the railway specific communication. FRMCS Users can be connected via 3GPP RAT, wired connectivity or other radio technology
+
+**Ground FRMCS User:** A general category of FRMCS Users that are predominantly stationary. Mostly they are connected via wired connectivity but may be using also wireless in certain conditions.
+
+**Home FRMCS Network:** The Home FRMCS Network is the network in which the FRMCS User is engaged in a subscription.
+
+**Mobile FRMCS User:** A general category of FRMCS Users that are mobile. Thus, they are connected via wireless connectivity all the time.
+
+**Off-Network communication:** direct communication between FRMCS Users in proximity.
+
+**On-Network communication:** indirect communication between FRMCS Users connected to FRMCS Network(s).
+
+**Performance communication applications:** applications that help to improve the performance of the railway operation, such as train departure, telemetry, etc.
+
+**Radio Block Centre (RBC):** A train sends its position and speed information periodically to the RBC. The RBC uses the received information to decide movement authority of the train.
+
+**Rail Infrastructure Manager:** A company that owns or manages rail infrastructure; within this document the Rail Infrastructure Manager owns, administers and operates the FRMCS Network.
+
+**Railways Undertaking:** A company that offers train freight or passenger transportation services, making use of FRMCS network for their operational communication needs that is operated by a Rail Infrastructure Manager.
+
+**Role (Functional Role):** The function a FRMCS User or a FRMCS Equipment is currently performing. Examples of Roles are Driver, Controller or shunting staff, etc. This is indicated by the FRMCS Functional Identity.
+
+**Shunting:** manoeuvring trains in order to change their location or composition.
+
+**Trackside staff:** Staff working as trackside maintenance and/or shunting members
+
+**Trainborne equipment:** FRMCS Equipment which is physically embedded in train
+
+**Visited (FRMCS) Network:** A Visited (FRMCS) Network can be either another FRMCS Network than the Home FRMCS Network, or a Public Land Mobile Network (PLMN).
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|-------------------------------------|
+| ATO | Automatic Train Operation |
+| ATP | Automatic Train Protection |
+| AVC | Assured Voice Communication |
+| DoS | Denial of Service |
+| GNSS | Global Navigation Satellite System |
+| LMR | Land Mobile Radio |
+| MACN | Multi Access Core Network |
+| NA | Naming Authority |
+| OATP | On-board Automatic Train Protection |
+| PSAP | Public Safety Answering Point |
+| RBC | Radio Block Centre |
+| REC | Railway Emergency Communication |
+| TRS | Trunked Radio System |
+
+---
+
+## 4 Overview
+
+The present document is an 800 series Technical Report (TR) written by 3GPP TSG SA WG1 (SA1). Such a TR is not normative, i.e. cannot be used for implementation directly and cannot be referred to by other 3GPP specifications. It was primarily written by SA1 to summarise the high-level communication needs of the railway community and to identify the corresponding requirements, which, in another step have been introduced into normative Technical Specifications (TS) of 3GPP.
+
+An 800 series TR will not be updated when in the process of introduction of the requirements to TS changes are made to those requirements, i.e. the text of the requirements listed here in this TR will not be aligned with the requirements in the TS. Due to the fact that most of the requirements identified in this document were introduced in already existing Mission Critical Communication (MCX) TS, an alignment with the MCX terminology and functionality was made resulting in most of the requirements in here being reworded in the TS. Also, TS requirements changes due to future work affecting requirements stemming from this TR will not result in updates of this TR.
+
+However, the columns “Comments” of the requirements tables listed below were updated to indicate the disposition of the requirement in the TS and most of the time summarising deviations and decisions taken when introducing those requirement into normative TS. By following these references into the normative TS the functionality provided by 3GPP for railway communication can be derived by the reader.
+
+FRMCS will adapt 3GPP transport to provide communication to railway users. It eventually will resemble GSM-R and will additionally provide communication capabilities beyond what GSM-R has been able to. It will provide higher data rates, lower data latencies, multimedia communication, and improved communication reliability. FRMCS considers end-to-end use cases and also provides requirements that might or might not be in scope of 3GPP existing specifications. To facilitate smooth migration from legacy communication systems (e.g. GSM) to FRMCS, interworking requirements between legacy communication systems and FRMCS are provided.
+
+FRMCS Equipment shall connect to application domain through 3GPP radio access or other access. It provides emergency group communication, low latency and high reliable data and video service in high speed train environment. Amongst others it has the following important features:
+
+- Prioritized emergency group communication, train control data and video service
+- Seamless connectivity in high speed railway moving environments
+- Low latency and high reliable data and video service
+- Real time train monitoring and management for safe train operation
+- Reliable location tracking including in tunnel tracking
+- Legacy railway communication interworking to GSM-R system
+
+
+
+Figure 4-1: High-level relation of FRMCS and legacy systems. The diagram shows the interconnection between a Public Fixed Network (PSTN), Public GSM, GSM-R System, GSM-R UE, GSM-R User, FR(M)CS-System, and FR(M)CS-User. The FR(M)CS-System is a large box containing Railway Sub-System (Application domain), Core domain, 3GPP radio access (4G and beyond), non3GPP radio access, Wireline access, and FR(M)CS-Equipment. Arrows indicate bidirectional connections between the PSTN, GSM-R System, and FR(M)CS-System, and between the GSM-R UE and the FR(M)CS-Equipment. The GSM-R User is connected to the GSM-R UE, and the FR(M)CS-User is connected to the FR(M)CS-Equipment.
+
+**Figure 4-1: High-level relation of FRMCS and legacy systems**
+
+Basically, railway communication services [5] can be categorized into
+
+- Train control services
+- Maintenance services
+- Railway specific services (such as Railway Emergency Call, functional addressing, and location-based addressing)
+- Other services (providing train crews or train Drivers with information of train operation and interworking with the existing railway communication systems)
+
+This study categorizes all the use cases by considering inherent characteristics of railway applications. Specifically, the following categories of use cases are considered.
+
+- Basic functionality
+- Critical communication applications
+- Performance communication applications
+- Business communication applications
+- Critical support applications
+- Performance support applications
+- Business support applications
+- FRMCS System principles
+
+The categories can be depicted conceptually as follows:
+
+
+
+The diagram illustrates the hierarchy of FRMCS applications. At the top level (High), there are support applications: Critical, Performance, and Business. The middle level contains communication applications of the same categories. The bottom level (Low) consists of basic functionality.
+
+Diagram showing the grouping of FRMCS Applications by application level. A vertical blue arrow on the left indicates levels from 'High' at the top to 'Low' at the bottom. The applications are organized into a grid within a rounded rectangle labeled 'FRMCS system principles'. The top two rows contain six boxes: 'Critical support applications', 'Performance support applications', 'Business support applications' in the first row; 'Critical communication applications', 'Performance communication applications', 'Business communication applications' in the second row. The bottom row contains a single wide box labeled 'Basic functionality'.
+
+**Figure 4-2: Grouping of FRMCS Applications**
+
+## 5 Basic functionality use cases
+
+### 5.1 Introduction
+
+The basic functionality use cases describe the behaviour of the FRMCS Equipment when powered up and down. For power up it takes the already powered up 3GPP UE as starting point conversely the same applies for power down.
+
+### 5.2 Device power on and shut-down related use cases
+
+In this chapter the use cases related to the function Initialisation and shut-down are defined.
+
+- Power on the UE
+- Access to the FRMCS System
+- Controlled power down UE
+- Uncontrolled power down UE
+
+Note: Annex A provides examples of Role management (such as functional identities or FRMCS Equipment Identities) in the railway environment.
+
+### 5.3 Use case: Power on the UE
+
+#### 5.3.1 Description
+
+This use case provides the user with a powered-on UE.
+
+#### 5.3.2 Pre-conditions
+
+The UE is switched off.
+
+Note: In this use case and all the following it is assumed the UE contains a FRMCS Application, thus an UE with FRMCS Application is further referred to as FRMCS Equipment.
+
+### 5.3.3 Service flows
+
+#### Successful self-test
+
+The user switches on the UE.
+
+The FRMCS Application performs a self-test. If the test is successful, the user is informed about this.
+
+#### Unsuccessful self-test
+
+The user switches on the UE.
+
+The FRMCS Application performs a self-test. If the test is not successful, the user is informed about this.
+
+### 5.3.4 Post-conditions
+
+The UE is switched on and attached to a 3GPP network following normal 3GPP defined network selection procedures but not logged into any FRMCS System. The user is informed about the results of the self-test.
+
+### 5.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------|
+| [R-5.3-001] | The FRMCS Application shall be capable to perform a self-test and inform the user about the results. | A | N/A | Implementation requirement |
+
+## 5.4 Use case: Access to the FRMCS System to activate the FRMCS Equipment
+
+### 5.4.1 Description
+
+This use case describes how the FRMCS Equipment registers to the FRMCS System.
+
+### 5.4.2 Pre-conditions
+
+The UE is powered on and attached to a 3GPP network but is not registered to the FRMCS System.
+
+The UE has a subscriber identity.
+
+### 5.4.3 Service flows
+
+The FRMCS Equipment selects an applicable FRMCS System and logs on to it.
+
+The FRMCS Equipment is initialised by the FRMCS System according to its type.
+
+### 5.4.4 Post-conditions
+
+The FRMCS Equipment capabilities are activated.
+
+The FRMCS Application(s) are running on the device.
+
+The FRMCS Equipment is logged in to the FRMCS System
+
+## 5.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------|
+| [R-5.4-001] | When a FRMCS Equipment registers to the FRMCS System, the FRMCS Equipment capabilities are activated and the FRMCS Equipment shall be reachable by its FRMCS Equipment Identity. | A | N/A | Implementation requirement |
+
+## 5.5 Use case: Controlled power down of UE
+
+### 5.5.1 Description
+
+The UE is powered down.
+
+### 5.5.2 Pre-conditions
+
+The UE is switched on and the FRMCS Equipment is registered to the FRMCS System.
+
+### 5.5.3 Service flows
+
+The user / FRMCS User initiates power-down of the UE.
+
+If logged in, a FRMCS User is logged-out from the FRMCS System.
+
+The FRMCS Equipment will deregister all identities which are active.
+
+The FRMCS Equipment de-registers from the FRMCS System.
+
+The UE is switched off.
+
+### 5.5.4 Post-conditions
+
+The UE is de-registered from the FRMCS System and switched off.
+
+## 5.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------|
+| [R-5.5-001] | When the UE is about to be powered down, a FRMCS User logged into the FRMCS System shall be logged off first. | A | N/A | Implementation requirement |
+| [R-5.5-002] | By logging off the functional Role of a FRMCS User shall be deregistered from the FRMCS System. | A | N/A | Implementation requirement |
+| [R-5.5-003] | After logging off the FRMCS User, the FRMCS Equipment capabilities shall be deactivated and the FRMCS Equipment shall be removed from the FRMCS System. | A | N/A | Implementation requirement |
+
+## 5.6 Use case: Uncontrolled power down UE
+
+### 5.6.1 Description
+
+This use case describes the case when the UE is powered down in an uncontrolled way e.g. due to battery failure.
+
+### 5.6.2 Pre-conditions
+
+The UE is switched on, the FRMCS Equipment is registered to the FRMCS System.
+
+### 5.6.3 Service flows
+
+The UE loses power probably without being able to notify the FRMCS System.
+
+The UE is without power.
+
+The FRMCS System will deregister all identities associated with the FRMCS Equipment.
+
+### 5.6.4 Post-conditions
+
+The UE is de-registered from the FRMCS System and switched off.
+
+### 5.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------|
+| [R-5.6-001] | When the UE is uncontrolled powered down, a FRMCS User logged into the FRMCS System shall be logged out from the FRMCS System. | A | N/A | Implementation requirement |
+| [R-5.6-002] | By logging out the functional Role of the FRMCS User shall be deregistered from the FRMCS System. | A | N/A | Implementation requirement |
+
+---
+
+## 6 Critical communication applications related use cases
+
+### 6.1 Introduction
+
+Critical communications applications are essential for train movements, safety, shunting, presence, trackside maintenance, legal aspects such as emergency communications, etc.
+
+### 6.2 Multi-train voice communication for Drivers and Ground FRMCS User(s)
+
+#### 6.2.1 Introduction
+
+In this chapter the use cases related to the function of Multi-train voice communication from the Drivers and/or a Ground FRMCS User towards the Driver and/or Ground FRMCS Users are defined. Ground FRMCS Users may include Controllers. The following use cases are defined:
+
+- Initiation of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
+- Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
+- Interworking GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
+
+#### 6.2.2 Use case: Initiation of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
+
+##### 6.2.2.1 Description
+
+A Driver and/or a Ground FRMCS User shall be able to initiate a voice communication to other Drivers and/or Ground FRMCS Users.
+
+##### 6.2.2.2 Pre-conditions
+
+The Driver and the Ground FRMCS User are authorised to initiate the communication. This is managed by the authorisation of communication application.
+
+The authorisation application authorises the Driver and the Ground FRMCS User to use the Multi-train voice communication for Drivers and Ground FRMCS User(s)
+
+##### 6.2.2.3 Service flows
+
+The Driver and/or Ground FRMCS User initiates the voice communication to the (other) Driver(s) and/or Ground FRMCS Users. The priority of the communication is managed by the prioritisation application.
+
+The FRMCS System determines the Driver(s) and the Ground FRMCS User(s) to be included in the communication, based on:
+
+- location information of all users provided by the locations services application, and/or
+- functional identity of all users provided by the Role management and presence application.
+
+The FRMCS System establishes the voice communication within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Driver(s) and Controller(s). The initiating Driver is indicated to the Controller(s). Also the location of the Driver(s) in the voice communication is presented to the Controller(s) which is retrieved from the location services application.
+
+If the Driver and/or Ground FRMCS User is connected to more than one Drivers and/or Controllers, the multiuser talker control application is used.
+
+The precedence of the incoming voice communication at the Driver and the Controller is managed by the prioritisation application.
+
+The voice communication is recorded by the Voice recording and access application.
+
+#### 6.2.2.4 Post-conditions
+
+The Driver and/or the Controller is connected to requested Driver(s) and/or Controller(s).
+
+## 6.2.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.2.2-001] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the FRMCS Users shall be able to initiate the voice communication to FRMCS Users in trains or on ground. | A | 22.280<br>22.179 | TS 22.179 Floor Control clause 6.2.3.2 Req #1,<br><br>TS 22.280 clause 5.1 Req # 2 |
+| [R-6.2.2-002] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the application layer priority of the communication shall be managed by the prioritisation application. | A | 22.280 | 6.8.7 Application layer priority, 7.6 MCX Service priority requirements |
+| [R-6.2.2-003] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the FRMCS System shall be able to determine the FRMCS User(s) to be included in the voice communication, based, amongst others, on the following criteria:<br>location information, speed and direction of travel provided by the locations services application, and/or functional identity provided by the Role management and presence application.<br>System configuration on which Controller is responsible for which part of the track/station/etc. | A | 22.280 | 6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X<br>6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b<br>5.9a-006, 5.9a-008a |
+| [R-6.2.2-004] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the FRMCS System shall be able to add or remove FRMCS User from the communication once criteria are met or no more met, e.g. by a FRMCS User entering or leaving an area | A | 22.280 | 6.4.9 req #6, 5.17 req # 3, 6.1 req #5, R-6.1.005, R6.6.5.2-00X<br>6.6.4.1.1, 6.6.4.1.2, 6.6.4.2-002a,002b<br>5.9a-006, 5.9a-008a |
+| [R-6.2.2-005] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s) the FRMCS System shall establish the communication within a setup time specified as NORMAL (see 12.10). | A/T | N/A | See section 12.10 below |
+| [R-6.2.2-006] | The FRMCS System shall be able to mutually present the identities of all communication partners involved in a Multi-train voice communication for | A | 22.280 | 5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2<br>Presentation of the id of the speaker is sufficient<br>See reqs in 6.4.5 |
+
+| | | | | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | Drivers and Ground FRMCS User(s). | | | |
+| [R-6.2.2-006a] | The FRMCS System shall be able to present the location of the Driver(s) to the Ground FRMCS Users involved in a Multi-train voice communication for Drivers and Ground FRMCS User(s). | A | 22.280 | 5.11 001, 008, 015<br>6.12 001,006,007<br>6.4.5 001, 003, 004 |
+| [R-6.2.2-006b] | The FRMCS System shall be able to update the presentation of the location of the Drivers as they move. | A | 22.280 | 5.11 007, 009, 013<br>6.12 006 |
+| [R-6.2.2-007] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s), always includes more than two participants.<br>If only two participants remain, the communication shall be treated as a user-to-user communication. | A | N/A | This is not a service requirement. It is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication. |
+| [R-6.2.2-008] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s), multiuser talker control shall be used (See "9.7 Multiuser talker control related use cases"). | A | N/A | This is not a service requirement. It is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication. |
+| [R-6.2.2-009] | For a Multi-train voice communication for Drivers and Ground FRMCS User(s) on the application layer the precedence of the incoming voice communication at the Driver and the Ground FRMCS User shall be managed by the prioritisation application. | A | N/A | See section 9.16 below |
+| [R-6.2.2-010] | The FRMCS System shall be able to make available the speech and communication related data of a Multi-train voice communication for Drivers and Ground FRMCS User(s) for recording. | A | 22.280 | On-Net:6.15.4-001 – 010<br>Off-Net: Not implemented |
+
+## 6.2.3 Use case: Termination of Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
+
+### 6.2.3.1 Description
+
+The Driver shall be able to either put on hold, leave, or terminate the voice communication.
+
+The Controller(s) shall be able to either put on hold, leave or terminate the voice communication.
+
+### 6.2.3.2 Pre-conditions
+
+The Driver to Controller and/or Driver voice communication is ongoing.
+
+### 6.2.3.3 Service flows
+
+#### **Driver on hold**
+
+The Driver shall be able to put the voice communication on hold.
+
+After the Driver has put the voice communication on hold, the communication remains in the FRMCS System, and the Driver is able to return to the communication again. When put on hold the other participants in the communication are informed and can continue the communication.
+
+#### **Driver leaving**
+
+The Driver shall be able to leave the voice communication. The Driver is not able to return to the communication after he has left. The Driver is not able to terminate the voice communication. When a Driver has left the other participants in the communication are informed and can continue the communication if there are still Driver(s) involved in the communication.
+
+The FRMCS System terminates the voice communication if the last Driver has left (although (multiple) Controllers are still active in the communication). All involved users are informed.
+
+#### **Ground FRMCS User on hold**
+
+A Ground FRMCS User shall be able to put the voice communication on hold in the case that more than one Ground FRMCS User is part of the voice communication. The Ground FRMCS User is able to return to the communication again.
+
+When put on hold the other participants in the communication are informed and can continue the communication.
+
+#### **Ground FRMCS User leaving**
+
+A Ground FRMCS User shall be able to leave the voice communication. The Ground FRMCS User is not able to return to the communication after he has left.
+
+After the Ground FRMCS User has left the voice communication, the remaining users are informed.
+
+#### **Controller termination**
+
+Any Controller shall be able to terminate the voice communication.
+
+The FRMCS System terminates the voice communication. All involved users are informed.
+
+#### **Driver termination**
+
+Only the Driver who initiates the call is able to terminate the voice communication with other Drivers.
+
+The FRMCS System terminates the voice communication if only one Driver remains in the voice communication.
+
+### 6.2.3.4 Post-conditions
+
+A Controller or the Driver has left the voice communication or the Controller or the system has terminated, put on hold or left the communication.
+
+### 6.2.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.2.3-001] | For a Multi-train voice communication for Drivers including Ground FRMCS User(s) a Driver or a Ground FRMCS User shall be able to put the voice communication on hold. The voice communication between the remaining users shall not be affected by a Driver or Ground FRMCS User putting the voice communication on hold. | A | 22.280 | 5.4.1, 5.4.2, 5.1.5<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is considered sufficient to mimic the desired behaviour. |
+| [R-6.2.3-002] | For a Multi-train voice communication for Drivers including Ground FRMCS User(s) the Driver shall be able to leave the communication.<br>Note: After a Driver has left the communication he is not able to return to it. | A | 22.280 | 5.4.1, 5.4.2, 5.1.5<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is considered sufficient to mimic the desired behaviour. |
+| [R-6.2.3-003] | For a Multi-train voice communication for Drivers including Ground FRMCS User(s) the Driver is not able to terminate the communication. | A | 22.179 | 6.2.3.4, 6.2.3.5, 6.2.4 |
+| [R-6.2.3-005] | For a Multi-train voice communication for Drivers including Ground FRMCS User(s) the FRMCS System terminates the voice communication if the last Driver has left (although (multiple) Ground FRMCS Users are still active in the communication). All involved users are informed. | A | 22.280<br>22.179 | 22.179 6.2.4 008<br>22.280 6.4.9 001<br>CR 22.280 0048 rev1: R-6.1-006, R-6.4.9-001 |
+| [R-6.2.3-006] | For a Multi-train voice communication for Drivers including Ground FRMCS User(s) a Ground FRMCS Users shall be able to leave the communication. After a Ground FRMCS User or a Driver has left the communication, the remaining users are informed. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is considered sufficient to mimic the desired behaviour. |
+| [R-6.2.3-007] | For a Multi-train voice communication for Drivers including Ground FRMCS User(s) any Controller shall be able to terminate the communication. All involved users are informed. | A | N/A | Due to the use of the affiliation mechanism and the burst-oriented nature of the MCPTT communication there is no such thing like a termination of a communication. It is simply not used anymore and the |
+
+| | | | | |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | MCX Service deletes the identifiers and reservation for it after some time. |
+| [R-6.2.3-008] | For a Multi-train voice communication between Drivers, the FRMCS System shall allow only the initiating Driver to terminate the voice communication. | A | N/A | Due to the use of the affiliation mechanism and the burst-oriented nature of the MCPTT communication there is no such thing like a termination of a communication. It is simply not used anymore and the MCX Service deletes the identifiers and reservation for it after some time. |
+| [R-6.2.3-009] | For a Multi-train voice communication between Drivers, the FRMCS System shall terminate the voice communication if only one Driver remains in the voice communication. | A | N/A | Due to the use of the affiliation mechanism and the burst oriented nature of the MCPTT communication there is no such thing like a termination of a communication. It is simply not used anymore and the MCX Service deletes the identifiers and reservation for it after some time. |
+
+## 6.2.4 Use case: Service Interworking and service continuation between GSM-R and FRMCS for Multi-train voice communication for Drivers and Ground FRMCS User(s) communication
+
+### 6.2.4.1 Description
+
+For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS System for Multi-train voice communication for Drivers including Ground FRMCS User(s) communication needs to be defined.
+
+Interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system.
+
+Depending on the migration scenario a Ground FRMCS User or a Driver can be attached to the FRMCS system, to the GSM-R system or both. The Driver can be attached either in the GSM-R system or in the FRMCS System. Functional identities are applicable in one system only.
+
+This use case only applies to end user devices supporting both FRMCS and GSM-R systems.
+
+### 6.2.4.2 Pre-conditions
+
+None.
+
+### 6.2.4.3 Service flows
+
+#### Driver attached to GSM-R
+
+When the Driver is attached to the GSM-R system and is initiating voice communication to other Drivers and Ground FRMCS User, the GSM-R system will route the voice communication to other Drivers the Ground FRMCS User (s) accordingly.
+
+If the Driver or the Ground FRMCS User is located in the FRMCS System, the GSM-R system can only route the call if it can be reached by an address or identity understood by the GSM-R system. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
+
+The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Ground FRMCS User.
+
+#### **Driver attached to FRMCS**
+
+When the Driver is attached to the FRMCS System and is initiating voice communication to other Drivers and Ground FRMCS User, the FRMCS System will route the communication to the Ground FRMCS User accordingly. The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Ground FRMCS User. The Role management in FRMCS shall provide the appropriate address or identity e.g. by provide a mapping of GSM-R identities and FRMCS identities.
+
+#### **Driver moving from GSM-R to FRMCS**
+
+When the GSM-R user equipment of the Driver is detached from the GSM-R system the FRMCS end user device shall provide service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable.
+
+Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE.
+
+#### **Driver moving from FRMCS to GSM-R**
+
+When the FRMCS User equipment of the Driver is detached from the FRMCS System the FRMCS end user device shall provide service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable.
+
+Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE.
+
+#### **6.2.4.4 Post-conditions**
+
+None.
+
+#### 6.2.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------|
+| [R-6.2.4-001] | The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-6.2.4-002] | The FRMCS System shall provide the necessary means to FRMCS Users to set up a Multi-train voice communication for Drivers and Ground FRMCS User(s) also to users in legacy GSM-R systems. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-6.2.4-003] | For Multi-train voice communication for Drivers and Ground FRMCS User(s), when the GSM-R UE becomes detached from the GSM-R system, e.g. due to coverage problems, the end user device, if capable of making use of the FRMCS System shall be able set up the communication on the FRMCS System. An interruption of voice communication is acceptable.<br>Note 1: This use case only applies to end user devices containing a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device. | A | 22.280 | Covered by 6.6.4.1.2 and 6.6.5.2 |
+| [R-6.2.4-004] | For Multi-train voice communication for Drivers and Ground FRMCS User(s), when the FRMCS Equipment, becomes detached from the FRMCS System, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R shall be able to set up the | A | | Covered by GSM-R "Late Entry" |
+
+| | | | | |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+| | <p>communication on legacy GSM-R. An interruption of voice communication is acceptable.</p> <p>Note 2: This use case only applies to end user devices containing a FRMCS Equipment and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.</p> | | | |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+
+## 6.3 On-train outgoing voice communication from the Driver towards the Controller(s) of the train
+
+### 6.3.1 Introduction
+
+In this chapter the use cases related to the function of On-train outgoing voice communication from the Driver towards the Controller(s) of the train are defined. This use case allows the Driver to only communicate with Controllers. The following use cases are defined:
+
+- Initiation of Driver to Controller(s) voice communication
+- Termination of Driver to Controller(s) voice communication
+- Interworking GSM-R and FRMCS of Driver to Controller(s) communication
+
+### 6.3.2 Use case: Initiation of Driver to Controller(s) voice communication
+
+#### 6.3.2.1 Description
+
+The Driver shall be able to initiate a voice communication to the Controller(s) that was, is, or will be responsible for the movement of the train.
+
+#### 6.3.2.2 Pre-conditions
+
+The Driver is authorised to initiate the voice communication to the Controller. This is managed by the authorisation of voice communication application.
+
+The Driver is authorised to use the On-train outgoing voice communication from the Driver towards the Controller(s) of the train application by the application authorisation of application.
+
+#### 6.3.2.3 Service flows
+
+##### Driver to responsible Controller(s)
+
+The Driver initiates the voice communication to the Controller. The priority of the communication is managed by the prioritisation application.
+
+The FRMCS System determines the responsible Controller(s), based on:
+
+- location information of the train provided by the locations services application, and/or
+- functional identity provided by the Role management and presence application.
+- system configuration on which Controller is responsible for which part of the track/station/etc.
+
+The FRMCS System establishes the voice communication to the Controller(s) within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Driver and Controller. Also, the location of the Driver is presented to the Controller which is retrieved from the location services application.
+
+If the Driver is connected to more than one Controller, the multiuser talker control application is used.
+
+The precedence of the incoming voice communication at the Controller is managed by the prioritisation application.
+
+The voice communication is recorded by the voice recording and access application.
+
+#### **Driver to another Controller(s)**
+
+The Driver initiates the voice communication to the Controller who was or will be responsible for the movement of the train. The addressing is performed by selecting an entry from a list or entered manually. The priority of the communication is managed by the prioritisation application.
+
+The FRMCS System presents the list of Controllers to the Driver, based on:
+
+- location information provided by the locations services application, and/or
+- functional identity provided by the Role management and presence application.
+- system configuration on which Controller is responsible for which part of the track/station/etc.
+
+The FRMCS System establishes the voice communication to the Controller(s) within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the identities for both Driver and Controller. Also, the location of the Driver is presented to the Controller which is retrieved from the location services application.
+
+If the Driver is connected to more than one Controller, the multiuser talker control application is used.
+
+The precedence of the incoming voice communication at the Controller is managed by the prioritisation application.
+
+The voice communication is recorded by the Voice recording and access application.
+
+#### **6.3.2.4 Post-conditions**
+
+The Driver is connected to the requested Controller.
+
+### 6.3.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.3.2-001] | For Driver to Controller voice communication, the Driver shall be able to initiate a voice communication to the Controller who is currently responsible for the train. The application layer priority of the voice communication shall be managed by the prioritisation application. | A | 22.280 | 22.280 6.8.7.1, 6.8.7.2; 5.1.1 002<br>22.179 6.2.3.7.3 001 |
+| [R-6.3.2-002] | For Driver to Controller voice communication the FRMCS System shall be able to determine the responsible Controller(s), based on e.g.: location information, speed and direction provided by the locations services application, and/or functional identity provided by the Role management and presence application. System configuration on which Controller is responsible for which part of the track/station/etc. | A | 22.280 | CR 22.280 0049rev3, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b |
+| [R-6.3.2-003] | For Driver to Controller voice communication the FRMCS System shall add or remove FRMCS User from the communication once criteria are met or no more met, e.g. by a FRMCS User entering or leaving an area. | A | 22.280 | CR 22.280 0049rev3, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b |
+| [R-6.3.2-004] | For Driver to Controller communication the FRMCS System shall establish the communication to the Controller(s) within a setup time specified as NORMAL (see 12.10). | A/T | N/A | See section 12.10 below |
+| [R-6.3.2-005] | The FRMCS System shall be able to mutually present the identities of all communication partners involved in a Driver to Controller(s) voice communication. | A | 22.280 | TS 22.280, 5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2<br>22.280 6.12-006<br>The id of the speaker is considered sufficient<br>See reqs in 6.4.5 |
+| [R-6.3.2-006] | The FRMCS System shall be able to present the location of the Driver to the Controller(s) involved in a Driver to Controller(s) voice communication. | A | 22.280 | 22.280<br>5.11 001, 008, 015<br>6.12 001,006,007<br>6.4.5 001, 003, 004<br>22.280 R-6.4.4-003, R-6.4.4-004 |
+| [R-6.3.2-007] | The FRMCS System shall be able to update the presentation of the location of | | 22.280 | 22.280<br>5.11 007, 009, 013<br>6.12 006 |
+
+| | | | | |
+|--|---------------------------|--|--|--|
+| | the Drivers as they move. | | | |
+|--|---------------------------|--|--|--|
+
+| | | | | |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.3.2-007 a] | For Driver to Controller communication, if the Driver is connected to just one Controller, the communication shall be considered as a user-to-user communication. | A | 22.280 | This is not a service requirement it is up to 3GPP SA6 to decide whether a communication with only two has to change the mode of operation to 1-2-1 communication |
+| [R-6.3.2-008] | For Driver to Controller voice communication, if the Driver is connected to more than one Controller, the multiuser talker control shall be used (See "9.7 Multiuser talker control related use cases"). | A | 22.179 | CRs 22.179 adding and CRs subsequently changing Section 5.9a |
+| [R-6.3.2-009] | For Driver to Controller communication on application layer the precedence of the incoming voice communication at the Controller shall be managed by the prioritisation application. | A | 22.280 | See section 9.16 below |
+| [R-6.3.2-010] | The FRMCS System shall be able to make available the speech and communication related data of a Multi-train voice communication for Drivers including Ground FRMCS User(s) for recording. | A | 22.280 | On-Net:6.15.4-001 – 010<br>Off-Net: Not implemented |
+| [R-6.3.2-011] | For Driver to Controller communication the Driver shall be able to initiate the communication to the Controller who was previously or will be responsible next for the movement of the train. The selection shall be performed by selecting an entry from a list or entered manually. The priority of the communication on application layer shall be managed by the prioritisation application. | A | 22.280 | CR 22.280 0049rev3: 5.9a-006, 5.9a-008a, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b |
+| [R-6.3.2-012] | For Driver to Controller communication the FRMCS System shall be able to present the list of Controllers to the Driver in order to select from, based on, amongst others, the following criteria: location information, speed and direction provided by the locations services application, and/or functional identity provided by the Role management and presence application. System configuration on which Controller is responsible for | A | 22.280 | CR 22.280 0049rev3: 5.9a-006, 5.9a-008a, 6.6.4.1.1, 6.6.4.1.2, Req 6.6.4.2-002a,002b |
+
+| | | | | |
+|--|--------------------------------------|--|--|--|
+| | which part of the track/station/etc. | | | |
+|--|--------------------------------------|--|--|--|
+
+### 6.3.3 Use case: Termination of Driver to Controller(s) voice communication
+
+#### 6.3.3.1 Description
+
+The Driver shall be able to terminate the Driver to Controller voice communication. The Driver is not able to leave the communication or to put on hold.
+
+The Controller(s) shall be able to either put on hold, leave or terminate the Driver to Controller communication.
+
+#### 6.3.3.2 Pre-conditions
+
+The Driver to Controller voice communication is ongoing.
+
+#### 6.3.3.3 Service flows
+
+##### **Driver termination**
+
+The Driver shall be able to terminate the voice communication. The FRMCS System terminates the voice communication. All involved Controllers are informed.
+
+Note: The Driver is not able to leave the communication or to put on hold.
+
+##### **Controller on hold**
+
+A Controller shall be able to put the Driver to Controller voice communication on hold in the case that more than one Controller is part of the voice communication.
+
+After the Controller has put the voice communication on hold, the communication remains in the FRMCS System, and the Controller is able to be part of the communication again.
+
+##### **Controller leaving**
+
+A Controller shall be able to leave the Driver to Controller voice communication in the case that more than one Controller is part of the voice communication.
+
+After the Controller has left the voice communication he is not able to return to the communication and the remaining users are informed.
+
+##### **Controller termination**
+
+Any Controller shall be able to terminate the Driver to Controller voice communication.
+
+The FRMCS System terminates the voice communication. All involved users are informed.
+
+#### 6.3.3.4 Post-conditions
+
+A Controller has left the voice communication or the Driver to Controller voice communication is terminated.
+
+### 6.3.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.3.3-001] | For Driver to Controller communication the Driver shall be able to terminate the communication. | A | 22.280<br>22.179 | 22.280 6.4.9 001<br>22.179 6.4.9 002, 6.2.4 008 |
+| [R-6.3.3-002] | For Driver to Controller communication the FRMCS System shall allow the operator to configure whether a Driver shall be able to leave the voice communication. | A | 22.280 | CR 22.280: 5.9a-012a, 5.9a-012b |
+| [R-6.3.3-003] | For Driver to Controller communication the FRMCS System shall allow the operator to configure whether a Driver shall be able to put the voice communication on hold. | A | 22.280 | 22.280, 5.4.1, 5.4.2, 5.1.5<br>The affiliation mechanism is considered sufficient to mimic the desired behavior. |
+| [R-6.3.3-004] | For Driver to Controller communication a Controller shall be able to put the voice communication on hold in the case that more than one Controller is part of the communication. The voice communication between the remaining users shall not be affected by a Controller putting the voice communication on hold. | A | 22.280 | 22.280 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>22.280 R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is considered sufficient to mimic the desired behavior. |
+| [R-6.3.3-005] | For Driver to Controller communication a Controller shall be able to leave the Driver to Controller communication in the case that more than one Controller is part of the communication. After a Controller has left the communication, the remaining users shall be informed. | A | 22.280 | 22.280 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>22.280 R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is considered sufficient to mimic the desired behavior. |
+| [R-6.3.3-006] | For Driver to Controller communication any Controller shall be able to terminate the Driver to Controller communication. All involved users shall be informed. | A | 22.280<br>22.179 | 22.280 6.4.9 001<br>22.179 6.2.4 008 |
+
+### 6.3.4 Use case: Service Interworking and service continuation between GSM-R and FRMCS of Driver to Controller(s) voice communication
+
+#### 6.3.4.1 Description
+
+For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS System for Driver to Controller(s) voice communication needs to be defined.
+
+Interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system.
+
+Depending on the migration scenario a Controller can be attached to the FRMCS system, to the GSM-R system or both. The Driver can be attached either in the GSM-R system or in the FRMCS System. Functional identities are applicable in one system only.
+
+This use case only applies to end user devices supporting both FRMCS and GSM-R systems.
+
+#### 6.3.4.2 Pre-conditions
+
+None.
+
+#### 6.3.4.3 Service flows
+
+##### **Driver attached to GSM-R**
+
+When the Driver is attached to the GSM-R system and is initiating voice communication to Controller(s), the GSM-R system will route the voice communication to the Controller(s) accordingly.
+
+If the Controller is located in the FRMCS System, the GSM-R system can only route the call to the Controller if the Controller can be reached by an address or identity understood by the GSM-R system. The Role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
+
+The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Controller.
+
+##### **Driver attached to FRMCS**
+
+When the Driver is attached to the FRMCS System and is initiating voice communication to Controller(s), the FRMCS System will route the communication to the Controller(s) accordingly. The information from the Role management and presence application is used to route the communication and to present the identities of both Driver and Controller. The Role management in FRMCS shall provide the appropriate address or identity e.g. by provide a mapping of GSM-R identities and FRMCS identities.
+
+##### **Driver moving from GSM-R to FRMCS**
+
+When the GSM-R user equipment of the Driver is detached from the GSM-R system the FRMCS end user device shall provide service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable.
+
+Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE.
+
+##### **Driver moving from FRMCS to GSM-R**
+
+When the FRMCS User equipment of the Driver is detached from the FRMCS System the FRMCS end user device shall provide service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable.
+
+Note: This use case only applies to end user devices supporting both FRMCS and GSM-R systems, i.e. contains a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE.
+
+#### 6.3.4.4 Post-conditions
+
+None.
+
+### 6.3.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------------------------------|
+| [R-6.3.4-001] | The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-6.3.4-002] | The FRMCS System shall provide the necessary means to FRMCS Users to set up a Driver to Controller voice communication also to users in legacy GSM-R systems. Interworking between FRMCS and GSM-R shall not require any changes on GSM-R network side. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-6.3.4-003] | For Driver to Controller communication, when the GSM-R UE becomes detached from the GSM-R system, e.g. due to coverage problems, the end user device, if capable of making use of the FRMCS System shall be able set up the communication on the FRMCS System. An interruption of voice communication is acceptable.<br>Note 1: This use case only applies to end user devices containing a FRMCS UE and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device. | A | N/A | Call has to be re-established by UE. This is UE function outside scope of 3GPP standardization |
+| [R-6.3.4-004] | For Driver to Controller communication, when the FRMCS Equipment, becomes detached from the FRMCS System, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R shall be able to set up the communication on legacy GSM-R. An interruption of voice communication is | A | N/A | Call has to be re-established by UE. This is UE function outside scope of 3GPP |
+
+| | | | | |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+| | <p>acceptable.<br/>Note 2: This use case only applies to end user devices containing a FRMCS Equipment and a GSM-R UE. It is assumed the FRMCS Application on the FRMCS Equipment will have some control of the GSM-R part of the UE which is referred to here as end user device.</p> | | | |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+
+## 6.4 Railway emergency communication
+
+### 6.4.1 Introduction
+
+In this chapter the use cases related to Railway emergency communication are defined. The following use cases are defined:
+
+- Initiation of the Railway emergency alert
+- New entry to the Railway emergency alert
+- Changing of the Railway emergency alert
+- Merging of Railway emergency alerts
+- Leaving of the Railway emergency alert
+- Termination of the Railway emergency alert;
+- Initiation of railway emergency voice communication
+- Termination of railway emergency voice communication
+- Initiation of Data communication during Railway emergency Alert
+- Service interworking and service continuation with GSM-R
+- Interface to train borne recorder
+
+### 6.4.2 General overview
+
+Railway emergency communication serves two main purposes in railway operation
+
+- Alert Drivers or other railway staff about an emergency. Receiving such alert will result in immediate actions to be taken by the recipients. These actions are defined by operational rules, e.g. a Driver will slow down train speed to 40km/h, drive on sight, etc.
+- Based on operational rules, additional information about the emergency can be exchanged using voice and/or data communication.
+
+While the alert needs to be setup very fast, the information part that may follow is less time critical and not always required. The Railway emergency Communication consists of:
+
+1. A mandatory alert phase indicating the emergency;
+2. An optional voice and/or data communication phase depending on operational situation and / or operational rules.
+
+Alert is the general term used that encompasses the different phases initiation, continuation and termination. This receives priority handling which is linked to the application category within the FRMCS System (see 12.10).
+
+When a railway emergency alert is triggered by a FRMCS User, the FRMCS System determines which other FRMCS Users shall receive an alert, depending on following conditions:
+
+- Location, accuracy of the location, track, functional identity, direction of movement, speed of the initiating entity
+- Location, accuracy of the location, track, functional identity, direction of movement, speed of the FRMCS Users which are concerned of the emergency
+- Any additional information provided by the initiating entity
+
+By applying alert conditions, only FRMCS Users who are concerned by this emergency will receive an alert. Figure 6.4.2-1 outlines this principle.
+
+
+
+Legend:
+
+- Affected area (e.g accident)
+- .- Traffic Controller's area of responsibility
+- Poor accuracy of location information available
+- ! No alert due to location, speed, direction and/or accuracy of location information
+- ! Alert due due to location, speed, direction and/or accuracy of location information
+
+Figure 6.4.2-1: Illustration of FRMCS Users in a railway emergency alert area. The diagram shows a railway track with a train that has derailed at a junction, marked by a yellow starburst. A red dashed circle indicates the 'Affected area (e.g accident)'. A blue dash-dot circle indicates the 'Traffic Controller's area of responsibility'. Several workers are shown: some with green exclamation marks (no alert) and others with orange exclamation marks (alert). Arrows labeled 'MOVE' point away from the accident area. A legend on the left explains the symbols: red dashed circle for affected area, blue dash-dot circle for traffic controller's area, green dashed circle for poor accuracy, green exclamation mark for no alert, and orange exclamation mark for alert.
+
+**Figure 6.4.2-1 Illustration of FRMCS Users in a railway emergency alert area**
+
+Independently of any ongoing interactions between the FRMCS User and the FRMCS Equipment, the railway emergency alert has to be continuously indicated to the FRMCS User until the railway emergency is over (alert is terminated).
+
+While an alert is active, the FRMCS System shall continuously check:
+
+- If additional FRMCS Users do match to the conditions of the railway emergency alert. FRMCS User entering the emergency area/location/etc. will receive the alert.
+- If an FRMCS User does not fulfil the conditions to be alerted anymore, because the FRMCS User has moved away from the emergency area, the alert will be withdrawn from this FRMCS User.
+
+A Controller is able to change the conditions to select the applicable FRMCS Users while an alert is active.
+
+While an alert is active on a FRMCS Equipment, the FRMCS User is still able to establish and / or receive other types of communication. If a railway emergency voice communication is established by the FRMCS User of an ongoing alert, any other ongoing voice communications are terminated.
+
+## 6.4.3 Use case: Initiation of the railway emergency alert
+
+### 6.4.3.1 Description
+
+An FRMCS- user is able to initiate a railway emergency alert. Based on a set of conditions the FRMCS System will determine which FRMCS Users that shall be informed about the emergency.(see 6.4.2 General overview) The targeted FRMCS User can be e.g. a mobile FRMCS User, a Driver, an External System, a Controller, maintenance staff or a member of a shunting team.
+
+### 6.4.3.2 Pre-conditions
+
+The initiating FRMCS User is authorised to establish a railway emergency alert.
+
+### 6.4.3.3 Service flows
+
+In any service flow, a mobile FRMCS User, e.g. a Driver, a maintenance staff or a member of a shunting team, is not able to leave or terminate the railway emergency alert.
+
+#### **Controller initiated**
+
+The Controller provides the conditions (e.g. train number/area/track section/station) to the FRMCS System selecting the appropriate recipients of the railway emergency alert. The conditions (e.g. train number/area/track section/station) can be pre-configured for comfortable selection by the Controller. The Controller may need to confirm the selection.
+
+The FRMCS System will determine, based on the conditions, which FRMCS Users are to receive the railway emergency alert.
+
+The FRMCS System alerts the FRMCS Users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which is presented to the FRMCS User.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+In case a FRMCS User is already involved in another railway emergency alert, FRMCS System does not forward new alerts to this particular FRMCS User. The waiting alert is sent as soon as the FRMCS User is no longer involved in the other railway emergency alert.
+
+The Controller is informed about the alerted FRMCS Users.
+
+The FRMCS Equipment of a Controller shows multiple alerts when active.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### **External system initiated**
+
+FRMCS System receives the conditions from the External System (e.g. a list/train number/area/track section/station) to address/determine the appropriate recipients of the railway emergency alert.
+
+The FRMCS System will determine, based on the conditions, which users will receive the railway emergency alert.
+
+The FRMCS System alerts the FRMCS Users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which are presented to the FRMCS Users.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+In the case that a mobile FRMCS User is already active in another railway emergency alert, the FRMCS System does not forward new alerts to this particular FRMCS User. A waiting alert is sent as soon as the FRMCS User is no longer involved in an ongoing railway emergency alert. The Controller is informed about the alerted FRMCS Users and the alert initiating External System.
+
+The FRMCS Equipment of a Controller shows multiple alerts when active.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### **Mobile FRMCS User initiated**
+
+A FRMCS User, like a Driver, maintenance staff or a member of a shunting team, presses the railway emergency button.
+
+The FRMCS Equipment requests the alert communication to the FRMCS System.
+
+The FRMCS System determines the FRMCS Users to be included in the railway emergency alert. This is based on the location information of the initiator and certain conditions (e.g. functional identity, track area, accuracy of the location, maximum track speed, station, shunting yard, location/speed/direction of users).
+
+The FRMCS System alerts the FRMCS- users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which are forwarded to the concerned FRMCS Users.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+In the case that a mobile FRMCS User is already active in another railway emergency alert, the FRMCS System does not forward new alerts to this particular FRMCS User. A waiting alert is sent as soon as the FRMCS User is no longer involved in an ongoing railway emergency alert. The applicable Controller(s) is informed about the alerted FRMCS Users, including which user initiated the alert.
+
+The FRMCS Equipment of a Controller shows multiple alerts when active.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### **6.4.3.4 Post-conditions**
+
+The applicable FRMCS Users are alerted.
+
+### 6.4.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.3-001] | The FRMCS System shall be able to deliver railway emergency alerts. Requests to initiate a railway emergency alerts may come from Controllers, External Systems or mobile FRMCS Users | A | 22.280 | R-5.6.2.4.1-002 ( etc.)<br>R-5.6.2.1.2-002<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>R-6.15.5.2-001 |
+| [R-6.4.3-002] | For requests from Controllers or External Systems, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway emergency alert, based on the conditions supplied with the requests (e.g. a list/train number/area/track section/station). | A | 22.280 | R-5.6.2.4.1-004<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>R-6.15.5.2-001 & R-6.15.5.2-014 |
+| [R-6.4.3-003] | For requests from FRMCS-users, based on the location information of the initiator and certain other conditions such as functional identity, track area, accuracy of the location, maximum track speed, station, shunting yard, speed and direction, the FRMCS System shall be able to determine which FRMCS Users shall receive the railway emergency alert. | A | 22.280 | R-5.6.2.1.2-002<br>R-5.6.2.4.1-004<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>R-6.15.5.2-001 & R-6.15.5.2-014 |
+| [R-6.4.3-004] | In case no FRMCS- users can be determined to be alerted the FRMCS System shall apply the behaviour as specified in 6.4.4 "New entry". | A | 22.280 | R-6.6.4.2-002b<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>R-6.15.5.2-014 |
+| [R-6.4.3-005] | The FRMCS System shall be able to provide additional information (e.g. text, voice prompts) in the railway emergency alert to be forwarded to the FRMCS Users | A | 22.282 | Using MCData SDS and File Distribution for that - based on the same group i.e. after the MCX Emergency Alert a SDS is initiated and potentially a File Dist. as described in MCData<br>22.282 R-5.2.2-XXX & 5.3.2-XXX |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.3-006] | The FRMCS System shall be able to prevent FRMCS User(s), other than a Controller, involved in another railway emergency alert, to receive an additional railway emergency alert. In this case when the FRMCS User is no more involved in the other railway emergency alert, the FRMCS System shall forward the railway emergency alert to this FRMCS User. | A | 22.280 | 5.4.2-XXX<br>[R-5.4.2-007a] |
+| [R-6.4.3-007] | The FRMCS System shall be able to provide all applicable alerts to a Controller independent of whether involved in another alert or not to allow the Controllers to switch between different alerts. | A | 22.280 | 5.4.2-XXX<br>[R-5.4.2-007a] |
+| [R-6.4.3-008] | The FRMCS System shall not prevent a FRMCS User to make use of other communication services while involved in a railway emergency alert. | A | 22.280 | Covered by the affiliation mechanism |
+| [R-6.4.3-009] | The FRMCS System shall be able to deliver the railway emergency alert within a time specified as IMMEDIATE (see 12.10). | A&T | N/A | See section 12.10 below |
+| [R-6.4.3-010] | For railway emergency alert the application layer priority of the communication shall be managed by the prioritisation application. | A | 22.280 | 5.4.2-XXX<br>5.6.X, 6.8.7.X, etc<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.3-011] | When setting up and during the alert, the FRMCS System shall inform the initiator and the involved Controller(s) which FRMCS Users are alerted and who initiated the railway emergency alert. | A | 22.280 | 5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2<br>6.12-006<br>The id of the speaker is considered sufficient |
+| [R-6.4.3-012] | The FRMCS System shall be able to make available the speech and communication related data of a railway emergency alert for recording. | A | 22.280 | 6.15.4-001 - 010 |
+
+## 6.4.4 Use case: New entry to the railway emergency alert
+
+### 6.4.4.1 Description
+
+The FRMCS System shall continuously check if additional FRMCS Users meet the conditions of the railway emergency alert. The FRMCS User can be e.g. a mobile FRMCS User, a Driver, maintenance staff, a member of a shunting team or a Controller. The additional FRMCS Users receive the railway emergency alert.
+
+### 6.4.4.2 Pre-conditions
+
+The FRMCS User is authorised (referring to authorisation of application) to receive the railway emergency alert. There is an ongoing railway emergency alert.
+
+### 6.4.4.3 Service flows
+
+The FRMCS System shall continuously check if additional FRMCS Users meet the conditions of the railway emergency alert. The FRMCS User can be e.g. a mobile FRMCS User, a Driver, maintenance staff, a member of a shunting team or a Controller.
+
+The FRMCS System alerts the FRMCS- users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g. text, voice prompts) which is forwarded to the FRMCS Equipment.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+In the case of an ongoing railway emergency voice communication, the additional FRMCS User is added to the ongoing voice communication.
+
+In case that a FRMCS User is already active in another railway emergency alert, FRMCS System does not forward the new alerts to this particular FRMCS- user. The waiting alert is sent as soon as the FRMCS User is no longer involved in an ongoing railway emergency alert.
+
+A mobile FRMCS User, e.g. a Driver, maintenance staff or a member of a shunting team, is not able to leave or terminate the railway emergency alert.
+
+The Controller is informed about additionally alerted FRMCS User.
+
+The FRMCS Equipment of a Controller shows multiple alerts when active.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+### 6.4.4.4 Post-conditions
+
+The additional FRMCS Users are alerted.
+
+#### 6.4.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.4-001] | The FRMCS System shall continuously check if additional FRMCS Users meet the conditions of a railway emergency alert. | A | 22.280 | R-6.6.4.2-002b<br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-014 |
+| [R-6.4.4-002] | The FRMCS System shall be able to deliver the railway emergency alert to the new FRMCS User(s) within a setup time specified as IMMEDIATE (see 12.10). | A&T | N/A | See section 12.10 below<br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.4-003] | The FRMCS System shall be able to forward additional information (e.g. text, voice prompts) in the railway emergency alert to the new FRMCS Users. | A | 22.280 | [R-5.2.2-014] |
+| [R-6.4.4-004] | When added to a railway emergency alert a FRMCS User shall still be able to use other communications. | A | N/A | No requirements identified that might prevent a MCX User to receive other communication while in MEA |
+| [R-6.4.4-005] | For railway emergency alert the application layer priority of the communication shall be managed by the prioritisation application. | A | 22.280 | 5.4.2-XXX<br>5.6.X, 6.8.7.X<br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.4-006] | If a FRMCS User, other than a Controller, is involved in another railway emergency alert, the FRMCS System shall not forward the railway emergency alert to this FRMCS User. When the FRMCS User is no more involved in the other railway emergency alert, the FRMCS System shall forward the railway emergency alert to this FRMCS User. | A | 22.280 | 5.4.2-XXX<br>[R-5.4.2-007a] |
+| [R-6.4.4-007] | The FRMCS System shall provide all applicable alerts to a Controller independent of whether involved in another alert or not to allow the Controllers to switch between different alerts. | A | 22.280 | 5.4.2-XXX<br>[R-5.4.2-007a] |
+| [R-6.4.4-008] | The FRMCS System shall inform the initiator and the involved Controller(s) which FRMCS Users are additionally alerted. | A | 22.280 | 5.3 req #2, 5.7 req # 3, 6.4.3 req # 1 & #2<br>22.280 6.12-006<br>See reqs in 6.4.5 |
+| [R-6.4.4-009] | The FRMCS System shall be able to make available the speech and communication | A | 22.280 | 6.15.4-001 - 010 |
+
+| | | | | |
+|--|------------------------------------------------------------------------|--|--|--|
+| | related data of a railway emergency voice communication for recording. | | | |
+|--|------------------------------------------------------------------------|--|--|--|
+
+## 6.4.5 Use case: Changing of the railway emergency alert
+
+### 6.4.5.1 Description
+
+An authorised Controller or an External System is able to change the conditions selecting the appropriate recipients of the railway emergency alert. The change may result in an expansion or a reduction of FRMCS Users that shall be informed about the emergency.
+
+### 6.4.5.2 Pre-conditions
+
+The FRMCS User is authorised to change the conditions of the railway emergency alert. This is managed by the application authorisation of application.
+
+There is an ongoing railway emergency alert.
+
+### 6.4.5.3 Service flows
+
+The Controller or an External System shall be able to change the conditional criteria selecting the appropriate recipients of the railway emergency alert.
+
+The FRMCS System shall continuously check if FRMCS Users still meet the conditions of the railway emergency alert. The FRMCS User can be e.g., a mobile FRMCS User, a Driver, maintenance staff, a member of a shunting team or a Controller.
+
+The FRMCS System shall forward the railway emergency alert to all additional FRMCS Users within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include additional information (e.g., text, voice prompts) which are forwarded to the FRMCS User.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+In case of an ongoing railway emergency voice communication, the additional FRMCS Users are added.
+
+In case FRMCS User is already active in another railway emergency alert, the new alert is not forwarded by the FRMCS System to this particular FRMCS User. If the FRMCS User is no longer involved in an ongoing railway emergency alert, the waiting alert is forwarded by the FRMCS System.
+
+The FRMCS System shall update the FRMCS Users for whom the railway emergency alert is no longer applicable and terminates the alert. The termination notification of the alert can include additional information (e.g., text, voice prompts) which are forwarded to the FRMCS User.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority that matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+In case railway emergency alert conditions does not match any longer to a FRMCS User and if there is an ongoing railway emergency voice communication, the FRMCS User will remain in the ongoing railway emergency voice communication.
+
+FRMCS System informs the Controller about the FRMCS Users who have left and have joined the railway emergency alert.
+
+A mobile FRMCS User, e.g., a Driver, maintenance staff or a member of a shunting team, is not able to leave or terminate the Railway emergency alert.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### 6.4.5.4 Post-conditions
+
+The appropriate recipients remain as alerted, while non-appropriate recipients are not alerted anymore.
+
+#### 6.4.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.5-001] | If alert conditions are changed by an authorised Controller or an External System, the FRMCS System shall check if additional FRMCS Users match the conditions of the railway emergency alert. | A | 22.280 | R-6.6.4.2-002b<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-014 |
+| [R-6.4.5-002] | The FRMCS System shall forward the railway emergency alert to new FRMCS Users that match the conditions and inform the initiating Driver and Controller(s) accordingly. | A | 22.280 | [R-5.2.2-014]<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-014 |
+| [R-6.4.5-003] | The FRMCS System shall withdraw the alert from those FRMCS Users who do not match the conditions anymore and inform them and the initiating Driver and Controller(s) accordingly. | A | 22.280 | R-5.3-XXX<br>R-5.6.2.4.1-004<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-014 |
+| [R-6.4.5-004] | The FRMCS System shall be able to forward the railway emergency alert to new FRMCS User(s) within a setup time specified as IMMEDIATE (see 12.10). | A&T | N/A | See section 12.10 below<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.5-005] | Void. | | | |
+| [R-6.4.5-006] | The FRMCS System shall be able to forward additional information (e.g., text, voice prompts) in the railway emergency alert to new FRMCS Users. | A | 22.280 | [R-5.2.2-014] |
+| [R-6.4.5-007] | For railway emergency alert the application layer priority of the communication shall be managed by the prioritisation application. | A | 22.280 | 5.4.2-XXX<br>5.6.X, 6.8.7.X<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.5-008] | The FRMCS System shall be able to prevent new FRMCS User(s), other than a Controller, involved in an ongoing railway emergency alert, to receive an additional railway emergency alert. In this case when the ongoing railway emergency alert has ended the FRMCS System shall forward the railway emergency alert to the new FRMCS User. | A | 22.280 | 5.4.2-XXX<br>[R-5.4.2-007a] |
+
+| | | | | |
+|---------------|-------|--|--|--|
+| [R-6.4.5-009] | Void. | | | |
+|---------------|-------|--|--|--|
+
+## 6.4.5a Use case: Merging of Railway Emergency Alerts
+
+### 6.4.5a.1 Description
+
+An authorized FRMCS User (i.e., Controller) or an External System (e.g., Traffic Management System or Train Tracking System) is able to merge two or more existing Railway Emergency Alerts. The merging may result in changed alert conditions. The affected FRMCS Users are notified.
+
+### 6.4.5a.2 Pre-conditions
+
+An FRMCS User (i.e., Controller) is authorized to merge Railway Emergency Alerts. There are two or more ongoing Railway Emergency Alerts. FRMCS Users involved in those alerts have been regrouped into separate temporary groups for use during the alerts.
+
+### 6.4.5a.3 Service flows
+
+It has been determined that the alert area must be extended to include users involved in the ongoing alerts.
+
+An authorized FRMCS User (i.e., Controller) or an External System is able to provide the FRMCS System with changed alert conditions (e.g., extension of the area or combination of track sections) including selection of the appropriate recipients of the new (i.e., merged) Railway Emergency Alert. The FRMCS Users involved in the new/merged alert are regrouped into a new temporary group.
+
+The alert condition is declared by the Controller, or authorized FRMCS User, on this new temporary group. The FRMCS system sends the new/merged Railway Emergency Alert to all FRMCS Users in the new temporary group within a setup time specified as IMMEDIATE (see 12.10). The alert notification can include all relevant information including details of the merged alerts, if needed, (e.g., text, voice prompts) which is forwarded to and presented on the end user device of the regrouped FRMCS Users.
+
+The FRMCS system continuously check's if FRMCS Users still meet the alert conditions of the Railway Emergency Alert. The FRMCS User can be, for example, a mobile user, a driver, maintenance staff, a member of a shunting team or a controller.
+
+The priority of the Railway Emergency Alert is managed by the arbitration application. The alert has the priority which matches the application category CRITICAL DATA (see 12.10).
+
+In the case that a mobile FRMCS User is already active in a Railway Emergency Alert, the new Railway Emergency Alert is sent by the FRMCS System to the end user device. The presentation of the alert(s) to the user is managed by the client arbitration application.
+
+In case that a mobile FRMCS User is already active in an ongoing Railway Emergency Voice and/or Data communications of another Railway Emergency Alert (i.e., call in progress), the ongoing Railway Emergency Voice and/or Data communications is terminated either using normal termination condition (e.g., an authorized user terminate the call) or using configuration parameters of the FRMCS System (e.g., timeout when latest transmission ends).
+
+When ongoing Railway Emergency Voice and/or Data communications of another Railway Emergency Alert are terminated, the next request to establish Railway Emergency Voice and/or Data communication is made on the associated merged Railway Emergency Alert (i.e., next call occurs on regroup group).
+
+If a Railway Emergency Voice and/or Data communication is established by the FRMCS User of an ongoing Railway Emergency Alert, any other ongoing non-emergency-voice communications are put in the queue.
+
+A FRMCS User - other than the initiating FRMCS User (i.e., Controller) - is not able to manually leave the temporary group of the new Railway Emergency Alert.
+
+The FRMCS system notifies the FRMCS Users for whom the Railway Emergency Alert is no longer applicable and terminates the alert of these FRMCS Users. The termination notification of the alert can include additional information (e.g., text, voice prompts) which is presented on the end user device of the FRMCS Users. These FRMCS Users are removed from the merged alert temporary group.
+
+In the case an FRMCS User no longer meets the conditions of the Railway Emergency Alert, but there is an ongoing Railway Emergency Voice or Data Communication, the FRMCS User will remain in the ongoing Railway Emergency Voice or Data communication.
+
+The initiating FRMCS User (i.e., Controller) is notified which FRMCS Users are still part of the Railway Emergency Alert. FRMCS Users who have left the Railway Emergency Alert are separately indicated to the initiating FRMCS User (i.e., Controller).
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### 6.4.5a.4 Post-conditions
+
+The appropriate FRMCS Users remain in the temporary group of the merged Railway Emergency Alert, while non-appropriate FRMCS Users are returned to their previous condition.
+
+#### 6.4.5a.5 Potential requirements and gap analysis
+
+### 6.4.6 Use case: Leaving of the railway emergency alert
+
+#### 6.4.6.1 Description
+
+The FRMCS System shall continuously check if FRMCS Users do match to the condition of the railway emergency alert. If not, FRMCS System terminates the alert of the concerned FRMCS User.
+
+#### 6.4.6.2 Pre-conditions
+
+The FRMCS User is authorised to receive the railway emergency alert. This is managed by the application authorisation of application.
+
+There is an ongoing railway emergency alert.
+
+#### 6.4.6.3 Service flows
+
+##### Mobile FRMCS User
+
+The FRMCS System shall continuously check if FRMCS Users do match to the conditions of the railway emergency alert.
+
+The FRMCS System shall update the FRMCS Users for whom the railway emergency alert is no longer valid and terminates the alert of these FRMCS Users. The termination notification of the FRMCS System can include additional information (e.g. text, voice prompts) which are forwarded to the FRMCS User.
+
+A mobile FRMCS User, e.g. a Driver, maintenance staff or a member of a shunting team, is not able to leave or terminate the railway emergency alert.
+
+The priority of the railway emergency alert is managed by the prioritisation application. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS-System
+
+In case a FRMCS User does not match to the conditions of the railway emergency alert and the particular FRMCS User is part of an ongoing railway emergency voice communication, the FRMCS User will remain in the ongoing railway emergency voice communication.
+
+The Controller is informed by the FRMCS System about the remaining FRMCS Users of the railway emergency alert. The applicable Controller is updated by the FRMCS System about the particular FRMCS Users which do not match to the conditions of the railway emergency alert.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### **Controller**
+
+An entitled Controller is able to leave the railway emergency alerts, unless the leaving Controller is the last Controller in the alert.
+
+The Controller also leaves the ongoing railway emergency voice communication.
+
+The FRMCS Equipment of a Controller shows multiple alerts when active.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### **6.4.6.4 Post-conditions**
+
+The appropriate recipients are still alerted, while non-appropriate recipients are not alerted anymore.
+
+## 6.4.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.6-001] | The FRMCS System shall continuously check if FRMCS Users do not match the conditions of the railway emergency alert anymore. The FRMCS System shall withdraw the alert from those FRMCS Users who do not match the conditions anymore and inform them and the initiating Driver and Controller(s) accordingly. | A | 22.280 | R-5.3-XXX<br>R-5.6.2.4.1-004<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>R-6.15.5.2-014 |
+| [R-6.4.6-002] | The FRMCS System shall provide all applicable alerts to a Controller independent of whether involved in another alert or not to allow the Controllers to switch between different alerts | A | 22.280 | 5.1.2, 5.1.5, 5.4.2, 6.8.8.4.1-005 |
+| [R-6.4.6-003] | The FRMCS System shall be able to ensure that at least one Controller is always involved in the railway emergency alert.<br>Note: The FRMCS will prevent other FRMCS User, e.g. Drivers, maintenance staff or members of a shunting team, to leave railway emergency alert. | A | 22.280 | [R-6.6.4.2-002a/b]<br>6.4.6.1-002/003<br>R-6.4.4-003, R-6.4.4-004<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>not covered |
+
+## 6.4.7 Use case: Termination of the railway emergency alert
+
+### 6.4.7.1 Description
+
+The Controller is able to terminate the railway emergency alert.
+
+### 6.4.7.2 Pre-conditions
+
+The Controller is authorised to terminate the railway emergency alert.
+
+There is an ongoing railway emergency alert.
+
+### 6.4.7.3 Service flows
+
+The Controller terminates the railway emergency alert. A mobile FRMCS User, e.g. a Driver, maintenance staff or a member of a shunting team, is not able to terminate the railway emergency alert via actions on the end user device.
+
+Based on the alert termination request, FRMCS System forwards a termination notification to all FRMCS Users involved in the railway emergency alert. The alert termination notification can include additional information (e.g. text, voice prompts) which are forwarded by the FRMCS System presented on the FRMCS User.
+
+The priority of the termination of the railway emergency alert is managed by the prioritisation application. The termination of the alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+When the Controller terminated the railway emergency alert, in the case of manual initiation of railway emergency voice communication, the related ongoing railway emergency voice communication remains unaffected. On the FRMCS Equipment this can be a separate action for the Controller or can be triggered as a combined action with the termination of the alert.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### 6.4.7.4 Post-conditions
+
+The railway emergency alert is terminated.
+
+#### 6.4.7.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------|
+| [R-6.4.7-001] | The FRMCS System shall only allow a Controller to terminate the railway emergency alert. | A | 22.280 | R-6.8.8.4.2-XXX |
+| [R-6.4.7-002] | The FRMCS System shall notify the FRMCS Users of the terminated railway emergency alert.<br>The FRMCS System shall be able to forward additional information (e.g. text, voice prompts) as part of the alert termination. | A | 22.282 | R-5.6.2.4.2-003<br>R-5.2.2-014 |
+
+### 6.4.8 Use case: Initiation of railway emergency voice communication
+
+#### 6.4.8.1 Description
+
+Based on operational rules, additional information about the emergency can be exchanged using voice communication. E.g. the initiator of the railway emergency voice communication may inform other involved FRMCS Users about the emergency.
+
+Railway emergency voice communication is based on on-net communication.
+
+#### 6.4.8.2 Pre-conditions
+
+The railway emergency alert is active.
+
+#### 6.4.8.3 Service flows
+
+##### Automatic initiation of Emergency Voice Communication
+
+Upon activation of the railway emergency alert, the FRMCS System automatically initiates voice communication.
+
+FRMCS Users that are part of an active railway emergency alert shall be included in the voice communication.
+
+The railway emergency voice communication does not interrupt the railway emergency, but is able to pre-empt any other ongoing voice communication.
+
+The FRMCS System establishes the railway emergency voice communication within a setup time specified as IMMEDIATE (see 12.10). The information from the Role management and presence application is used to present the identities to the FRMCS Users involved in the communication.
+
+The location of the initiator of the railway emergency voice communication is forwarded and presented to the Controller. The necessary location information is retrieved from the location services application.
+
+Multiuser talker control application is used in railway emergency voice communication.
+
+The precedence handling of the incoming railway emergency voice communication for the FRMCS User is managed by the prioritisation application. The railway emergency voice communication has the priority which matches the application category of CRITICAL VOICE (see 12.10) within the FRMCS System.
+
+The communication is recorded by the FRMCS System voice recording and access to recorded data application.
+
+The FRMCS Equipment of a Controller shows multiple railway emergency voice communications when active.
+
+#### **Manual initiation of Emergency Voice Communication**
+
+Any FRMCS User having an active railway emergency alert shall be able to initiate voice communication by a simple user action.
+
+All the users receiving the active railway emergency alert shall be included in the voice communication.
+
+The railway emergency voice communication shall not interrupt the railway emergency alert but shall pre-empt any other ongoing voice communication.
+
+The FRMCS System establishes the railway emergency voice communication within a setup time specified as IMMEDIATE (see 12.10). The information from the Role management and presence application is used to forward the identities to the FRMCS Users involved in communication.
+
+The location of the initiator of the railway emergency voice communication is forwarded to the Controller. The location information is retrieved from the location services application.
+
+The multiuser talker control application is used in railway emergency voice communication.
+
+The handling of the incoming railway emergency voice communication for both the Controllers and mobile FRMCS Users is managed by the prioritisation application. The railway emergency voice communication has the priority which matches the application category of CRITICAL VOICE (see 12.10) within the FRMCS System.
+
+The communication is recorded by the FRMCS System voice recording and access to recorded data application.
+
+The FRMCS Equipment of a Controller shows multiple railway emergency voice communications when active.
+
+#### **6.4.8.4 Post-conditions**
+
+The railway emergency voice communication is active.
+
+#### 6.4.8.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.8-001] | Following a railway emergency alert the FRMCS System shall be able to automatically initiate a railway emergency voice communication. | A | 22.282 | R-5.6.2.4.1-013 |
+| [R-6.4.8-002] | The railway emergency voice communication does not interrupt the railway emergency, but is able to pre-empt any other ongoing voice communication. | A | N/A | Can be achieved by proper priority configuration further alert and (voice) communication do not compete for the same user interface resources |
+| [R-6.4.8-003] | The FRMCS System shall also be able to initiate a railway emergency voice communication on manual request by FRMCS Users e.g. Controllers and External Systems | A | 22.280 | R-5.6.2.2.1-XXX |
+| [R-6.4.8-004] | To determine which FRMCS Users have to be included in the communication the FRMCS System shall apply the mechanism as defined in [R-6.4.3-003] | N/A | 22.280 | R-5.6.2.1.2-002<br>R-5.6.2.4.1-004<br>R-6.8.8.4.1-006<br>(Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-001 & R-6.15.5.2-014 |
+| [R-6.4.8-005] | The FRMCS System shall be able to establish the railway emergency voice communication within a time specified as IMMEDIATE (see 12.10). | A | N/A | See section 12.10 below<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.8-006] | For railway emergency voice communication the application layer priority of the communication shall be managed by the prioritisation application. | A | 22.280 | 5.4.2-XXX<br>5.6.X, 6.8.7.X<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup: R-6.15.5.2-008 |
+| [R-6.4.8-007] | The location of the initiator of the railway emergency voice communication is forwarded and presented to the Controller. | A | 22.280 | 5.11 001, 008, 015<br>6.12 001,006,007<br>6.4.5 001, 003, 004 |
+| [R-6.4.8-008] | The FRMCS System shall be able to mutually forward and continuously update the location of all FRMCS Users involved in a railway emergency voice communication. | A | 22.280 | 5.11 007, 009, 013<br>6.12 006 |
+| [R-6.4.8-009] | For railway emergency voice communication the FRMCS | A | 22.179 | 6.2.3.7.2-XXX |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------|
+| | System shall apply multiuser talker control (See "9.7 Multiuser talker control related use cases"). | | | |
+| [R-6.4.8-010] | The FRMCS Equipment of a Controller shows multiple railway emergency voice communications when active. | | 22.280 | 5.4.2-XXX<br>[R-5.4.2-007a] |
+| [R-6.4.8-011] | The FRMCS System shall be able to make available the content and communication related data of the railway emergency voice communication for recording purposes. | A | 22.280 | 6.15.4-001 - 010 |
+
+## 6.4.9 Use case: Termination of railway emergency voice communication
+
+### 6.4.9.1 Description
+
+Only the Controller(s) shall be able to put on hold, leave or terminate the railway emergency voice communication.
+
+### 6.4.9.2 Pre-conditions
+
+The railway emergency voice communication is ongoing.
+
+### 6.4.9.3 Service flows
+
+In the case a user no longer meets the conditions of the railway emergency alert and if there is an ongoing railway emergency voice communication, the user will remain in the ongoing railway emergency voice communication.
+
+#### Controller on hold
+
+A Controller is able to put the railway emergency voice communication on hold.
+
+After the Controller has put the railway emergency voice communication on hold, the communication remains active in the FRMCS System. The Controller is able to revert back to the communication again.
+
+#### Controller leaving
+
+An entitled Controller is able to leave the railway emergency voice communication unless the leaving Controller is the last Controller involved in the railway emergency voice communication.
+
+#### Controller termination
+
+An entitled Controller is able to terminate the railway emergency voice communication.
+
+After termination request by the entitled Controller, FRMCS System terminates the railway emergency voice communication. All involved FRMCS Users are informed about the termination.
+
+### 6.4.9.4 Post-conditions
+
+A Controller has left, put on hold or terminated the railway emergency voice communication.
+
+## 6.4.9.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.9-001] | In the case a FRMCS User no longer meets the conditions of railway emergency voice communication, the user shall be removed from the ongoing railway emergency voice communication. | A | 22.280 | R-5.3-XXX<br>R-5.6.2.4.1-004<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.1-XXX User regroup<br><br>MCX service Ad hoc Group Communication as an alternative to User regroup:<br>R-6.15.5.2-014 |
+| [R-6.4.9-002] | For a railway emergency voice communication only a Controller shall be able to put the voice communication on hold. The voice communication between the remaining users shall not be affected by a Controller putting the railway emergency voice communication on hold. The Controller is able to take up the communication again. All involved users are informed. | A | 22.280 | 5.4.1, 5.4.2, 5.1.5<br>6.4.4-003, 6.4.4-004 |
+| [R-6.4.9-003] | For a railway emergency voice communication only a Controller shall be able to leave the communication unless the leaving Controller is the last Controller involved in the railway emergency voice communication. All involved users are informed. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>6.4.4-003, 6.4.4-004 |
+| [R-6.4.9-004] | For a Railway emergency voice communication only a Controller shall be able to terminate the communication. All involved users are informed. | A | 22.280 | R-6.8.8.4.2-XXX |
+
+## 6.4.10 Use case: Initiation of Data communication during railway emergency alert
+
+### 6.4.10.1 Description
+
+Based on operational rules, additional information about the emergency can be exchanged using data communication. A system or a user is able to send the additional information (e.g. text, voice prompts).
+
+### 6.4.10.2 Pre-conditions
+
+The railway emergency alert is active.
+
+### 6.4.10.3 Service flows
+
+A FRMCS User, Controller or an External System is able to send additional information (e.g. text, voice prompts).
+
+All the FRMCS Users shall receive the additional information.
+
+The FRMCS System establishes the data communication within a setup time specified as IMMEDIATE (see 12.10). The information from the Role management and presence application is used to present the identities to the users involved in communication.
+
+The location of the initiator of the data communication is presented to a mobile FRMCS User, Controller or to an External System. The location information is retrieved from the location services application.
+
+The handling of the incoming data communication is managed by the prioritisation application. The alert has the priority which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS System.
+
+It shall be possible to receive data communication during railway emergency voice communication.
+
+In the case of an ongoing Data communication during railway emergency alert, the additional user is added to the ongoing Data communication during railway emergency alert.
+
+The communication is recorded by the FRMCS System Data recording and access to recorded data application.
+
+### 6.4.10.4 Post-conditions
+
+Data communication is initiated.
+
+### 6.4.10.5 Potential requirements and gap analysis
+
+Independently on any actions between the user and the end user device, the additional information provided by data communication is presented to the user.
+
+The user shall be able to send additional information by data communication using simple user actions e.g. by selecting predefined messages.
+
+## 6.4.9.10 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------|
+| [R-6.4.10-001] | The FRMCS System shall allow a FRMCS User, Controller or an External System to send additional information (e.g. text, voice prompts) to FRMCS Users involved in a railway emergency alert or railway emergency voice communication. | A | 22.282 | R-5.2.2-014 |
+| [R-6.4.10-002] | The FRMCS System shall be able to deliver the additional data to a railway emergency alert or railway emergency voice communication within a time specified as IMMEDIATE (see 12.10). | A | N/A | See section 12.10 below |
+| [R-6.4.10-003] | The location of the initiator of the data communication shall be presented to all participants in the railway emergency alert or railway emergency voice communication. | A | 22.280 | 5.11 001, 008, 015<br>6.12 001,006,007<br>6.4.5 001, 003, 004 |
+| [R-6.4.10-004] | For railway emergency alert /railway emergency voice communication the application layer priority of the communication shall be managed by the prioritisation application. | A | 22.280 | 5.4.2-XXX<br>5.6.X, 6.8.7.X |
+| [R-6.4.10-005] | The FRMCS System shall be able to make available the content and communication related data of the railway emergency data communication for recording purposes. | A | 22.280 | 6.15.4-001 - 010 |
+
+## 6.4.11 Use case: Service interworking and service continuation with GSM-R
+
+### 6.4.11.1 Description
+
+For migration purposes, the service interworking and service continuation between the GSM-R system and FRMCS System for railway emergency alerts and railway emergency voice communication needs to be defined.
+
+Service interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system specifications.
+
+Depending on the migration scenario, a Controller can be attached to the FRMCS System, to the GSM-R system or both. The mobile FRMCS User can be attached either to the GSM-R system or to the FRMCS System.
+
+The service continuation use cases only apply where a FRMCS Equipment and a GSM-R UE are linked together.
+
+#### 6.4.11.2 Pre-conditions
+
+None.
+
+#### 6.4.11.3 Service flows
+
+##### **Mobile FRMCS User attached to GSM-R**
+
+When the mobile FRMCS User is attached to the GSM-R system and is initiating a Railway Emergency Call, the GSM-R system, (in parallel to processing the railway emergency call internally according to GSM-R definitions), routes the Railway Emergency Call to the FRMCS System, which requires the FRMCS System to be reachable by identities that are understood by the GSM-R system. The FRMCS System will determine, based on configuration, if a railway emergency alert needs to be established. If a railway emergency alert is established a railway emergency voice communication is initiated automatically.
+
+The Railway Emergency Call in the GSM-R system and the railway emergency voice communication in the FRMCS System are linked together and controlled by the FRMCS System.
+
+Service interworking between the talker control in the GSM-R system and the FRMCS System is required, but without changing the GSM-R system.
+
+When the Railway Emergency Call in the GSM-R system is terminated, the railway emergency alert and the railway emergency voice communication in the FRMCS System is terminated too.
+
+When the railway emergency voice communication in the FRMCS System is terminated and there is a Railway Emergency Call in the GSM-R system linked together, Railway Emergency Call in the GSM-R system and railway emergency alert / the Railway emergency voice communication in the FRMCS System are terminated too.
+
+When the railway emergency alert in the FRMCS System is terminated and there is a railway emergency Call in the GSM-R system connected, both the Railway Emergency Call in the GSM-R system and Railway emergency voice communication in the FRMCS System are not terminated.
+
+The information from the Role management and presence application is used to forward the identities between the systems. The identity of the initiator of the Railway Emergency Call in the GSM-R system is made available to the FRMCS System.
+
+##### **Mobile FRMCS User attached to FRMCS**
+
+When the FRMCS User is attached to the FRMCS System and is initiating a railway emergency alert, and the railway emergency alert is also relevant for the GSM-R system based on configuration, the railway emergency voice communication becomes initiated in the FRMCS System and as railway emergency Call in the GSM-R system.
+
+The railway emergency voice communication in the FRMCS System and Railway Emergency Call in the GSM-R system are linked and controlled by the FRMCS System.
+
+Service interworking between the talker control in the FRMCS System and the GSM-R system is required, but without changing the GSM-R system.
+
+When the railway emergency voice communication in the FRMCS System is terminated and there is a railway emergency Call in the GSM-R system linked, railway emergency Call in the GSM-R system and Railway emergency alert / the Railway emergency voice communication in the FRMCS System are also terminated.
+
+When the railway emergency alert in the FRMCS System is terminated and there is a linked Railway Emergency Call in the GSM-R system, both the Railway Emergency Call in the GSM-R system and railway emergency voice communication in the FRMCS System remain active.
+
+When the Railway Emergency Call in the GSM-R system is terminated, the railway emergency alert and the railway emergency voice communication in the FRMCS System is terminated.
+
+The information from the Role management and presence application is used to forward the identities between FRMCS System and GSM-R system. The identity of the initiator of the railway emergency alert in the FRMCS System is made available to the GSM-R system to be used accordingly.
+
+#### **Mobile FRMCS User moving from GSM-R to FRMCS**
+
+When the GSM-R system becomes unavailable e.g. lack of coverage, the FRMCS Equipment should provide service continuation by setting up the communication via the FRMCS System. An interruption of voice communication is acceptable. It is up to the end user device implementation how this service continuation is as seamless as possible presented to the user.
+
+#### **Mobile FRMCS User moving from FRMCS to GSM-R**
+
+When the FRMCS radio access becomes unavailable, the FRMCS Equipment shall able to provide service continuation by setting up the communication via the GSM-R system. An interruption of voice communication is acceptable. It is up to the end user device implementation how this service continuation is as seamless as possible presented to the user.
+
+Note: Both scenarios described above only apply when a FRMCS Equipment and a GSM-R UE are linked together. It is further assumed the FRMCS Application on the FRMCS Equipment to have some control of the GSM-R UE.
+
+#### **6.4.11.4 Post-conditions**
+
+None.
+
+#### 6.4.11.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.11-001] | The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R should not require any changes on GSM-R network side | A/T | 22.179 | Covered in 6.18.4.2 |
+| [R-6.4.11-002] | The FRMCS System shall provide the necessary means to FRMCS Users to set up a railway emergency alert and / or railway emergency voice communication also to users in the legacy GSM-R system. Interworking between FRMCS and GSM-R should not require any changes on GSM-R system. | A | 22.179 | Partially covered in 6.18.4.2. Voice is covered, Alert not, as there is no Emergency alert functionality available in GSM-R. |
+| [R-6.4.11-003] | In case of overlapping GSM-R and FRMCS serving the same geographical area the FRMCS System shall update GSM-R about ongoing Railway Emergency Communication/railway emergency alert in the FRMCS System.<br>Note: To allow the FRMCS System to be updated of Railway Emergency Communication initiated in the GSM-R needs to be configured accordingly. | A | 22.179 | Basic functionality covered by 6.18.4.2. However, the areas in FRMCS and GSM-R will not exactly match, due to the fact that the capabilities wrt, to granularity of location in the two systems are different. |
+| [R-6.4.11-004] | The FRMCS System shall provide service interworking between the talker control in the GSM-R system and the FRMCS System without changing the GSM-R system. | A | N/A | Based on latest decisions in ETSI-RT, there will be no interaction of talker control between the systems. As a consequence, only two related requirements on unmute/mute remain on the IWF |
+| [R-6.4.11-005] | When the Railway Emergency Call in the GSM-R system is terminated, the linked railway emergency alert and the railway emergency voice communication in the FRMCS System shall also be terminated. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-6.4.11-006] | When the railway emergency voice communication in the FRMCS System is terminated and there is a linked Railway Emergency Call in the GSM-R system, the Railway Emergency Call in the GSM-R | A | 22.179 | Covered in 6.18.4.2 |
+
+| | | | | |
+|--|----------------------------------|--|--|--|
+| | system shall also be terminated. | | | |
+|--|----------------------------------|--|--|--|
+
+| | | | | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.11-007] | When the railway emergency alert in the FRMCS System is terminated and there is a Railway Emergency Call in the GSM-R system linked, the Railway Emergency Call in the GSM-R system shall not be terminated. | A | N/A | No I/W between FRMCS emergency alert and GSM-R voice communication. Therefore, requirement becomes obsolete. |
+| [R-6.4.11-008] | When the Railway Emergency Call in the GSM-R system is terminated, the railway emergency alert and the railway emergency voice communication in the FRMCS System shall be terminated. | A | N/A | Voice communications gets terminated. No I/W between FRMCS emergency alert and GSM-R voice communication. Therefore, that part becomes obsolete |
+| [R-6.4.11-009] | The information from the Role management and presence application of the FRMCS System shall be used to identify and address GSM-R users to be included in the railway emergency alert /railway emergency voice communication. | A | N/A | Approach has changed now, linked calls are used instead. |
+| [R-6.4.11-010] | The identity of the initiator of a Railway Emergency Call in the GSM-R system shall be presented to the FRMCS Users involved in that railway emergency voice communication. | A | TS 22.179 | Covered for on-network: [R-6.18.4.2-003] |
+| [R-6.4.11-011] | For a Railway Emergency Call, when the GSM-R system becomes unavailable, e.g. due to coverage problems, the FRMCS Equipment, if capable of making use of the FRMCS System shall be able to reconnect to the railway emergency alert and, if applicable, the railway emergency voice communication on the FRMCS System. An interruption of voice communication is acceptable.<br>Note 1: This use case only applies when a FRMCS Equipment and a GSM-R UE are linked together. It is further assumed the FRMCS Application on the FRMCS Equipment to have some control of the GSM-R UE. | A | 22.280 | Communication aspect covered by 6.6.4.1.2 and 6.6.5.2 |
+| [R-6.4.11-012] | For railway emergency alert / | A | | Covered by GSM-R late entry |
+
+| | | | | |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+| | <p>railway emergency voice communication, when the FRMCS System becomes unavailable, e.g. due to coverage problems, the end user device, if capable of making use of legacy GSM-R shall be able to reconnect to the railway emergency voice communication via GSM-R. An interruption of voice communication is acceptable.</p> <p>Note 2: This use case only applies when a FRMCS Equipment and a GSM-R UE are linked together. It is further assumed the FRMCS Application on the FRMCS Equipment to have some control of the GSM-R UE.</p> | | | |
+|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|
+
+## 6.4.12 Use case: Interface to train borne recorder
+
+### 6.4.12.1 Description
+
+The FRMCS Equipment shall provide information about railway emergency communication to the train borne recorder or other equipment via a dedicated interface.
+
+### 6.4.12.2 Pre-conditions
+
+The FRMCS Equipment is switched on.
+
+### 6.4.12.3 Service flows
+
+The following events on the FRMCS Equipment related to the railway emergency communication is provided to the train borne recorder:
+
+- Initiation of the railway emergency alert
+- Reception of the railway emergency alert
+- Leaving of the railway emergency alert
+- Termination of the railway emergency alert
+- Initiation of railway emergency voice communication
+- Termination of railway emergency voice communication
+
+### 6.4.12.4 Post-conditions
+
+User actions related to the railway emergency communication have been provided to the train borne recorder.
+
+## 6.4.12.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------|
+| [R-6.4.12-001] | FRMCS Equipment shall provide a dedicated interface for train borne recording purposes | A | N/A | Interface for train borne recorder is outside scope of 3GPP. |
+| [R-6.4.12-002] | FRMCS Equipment shall provide following information to the train borne recorder: <ul style="list-style-type: none"> <li>• Initiation of the railway emergency alert</li> <li>• Reception of the railway emergency alert</li> <li>• Leaving of the railway emergency alert</li> <li>• Termination of the railway emergency alert</li> <li>• Initiation of railway emergency voice communication</li> <li>• Termination of railway emergency voice communication</li> </ul> | A | TS 22.280 | Covered for on-network: [R-6.15.4-004] [R-6.15.4-007] [R-6.15.4-008]<br>Not applicable to off-network (see table C-1). |
+
+## 6.5 Use case: Automatic Train Protection (ATP) support by the FRMCS System
+
+### 6.5.1 Description
+
+For Automatic Train Protection (ATP) the train transmits its information (such as current location, current speed, etc.) to a radio block centre (RBC). As soon as a connection has been established between a train, a radio block centre and a train centre, the train sends its position and speed information periodically. The RBC uses the received information to decide movement authority of the train.
+
+### 6.5.2 Pre-conditions
+
+It is assumed the current position of the train and its speed is provided by the Location Service as defined in 9.4.
+
+It is assumed that there is a bearer of suitable QoS established between the train the radio block centre and the train control centre.
+
+### 6.5.3 Service flows
+
+Via the bearer of suitable QoS the train provides its related information, e.g. train number, location, to the RBC. Via this bearer the train can request movement authority from the RBC and the RBC can grant this to the train.
+
+## 6.5.4 Post-conditions
+
+A train Driver controls the speed of the train according to movement authority.
+
+## 6.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------|----------------|
+| [R-6.5-001] | The FRMCS System shall be able to provide the necessary QoS for a data bearer to be used for the Automatic Train Protection (ATP) used for e.g. movement authority messages or emergency brake messages. | A/T | TS 22.282 (MCData) | Sub-clause 5.5 |
+
+# 6.6 Trackside Maintenance Warning System communication related use cases
+
+## 6.6.1 Introduction
+
+Generally, trackside maintenance occur during daily train operation. For safety reasons trackside maintenance staff need to be informed about approaching trains entering the area of maintenance. Thus, the intention of a trackside warning system is to inform trackside staff about the approaching train.
+
+Trackside warning system consists of several specific sensors and warning entities. The sensors are responsible to detect the approaching train and warning entities indicate trackside workers about the approaching train. A warning entity provides this indication in form of visual signal e.g. flashing light and an audio signal e.g. tone. In addition, the local maintenance staff will receive the train approaching indication on its FRMCS Equipment. When the train has left the track section, the warning system withdraws the indication.
+
+Sensors and warning entities constitute the warning system that requires continuous communication between the sensors and the warning entities. In addition, it encompasses the communication among the warning system and the FRMCS Equipment of the local maintenance staff.
+
+Due to the fact that such a warning system deployment is temporary and not always fixed network communication facilities are available at the track, FRMCS System provides necessary mobile communication services for the trackside warning system.
+
+Hence this chapter describes the use cases related to Trackside Maintenance Warning System communication. The following use cases are identified:
+
+- Initiation of a Trackside Maintenance Warning System communication
+- Termination of a Trackside Maintenance Warning System communication
+
+## 6.6.2 Use case: Initiation of a trackside maintenance warning system communication
+
+### 6.6.2.1 Description
+
+The FRMCS User (sensors of the warning system entity) shall be able to initiate data communication to the FRMCS Equipment of trackside maintenance staff and/or trackside warning indication entities (FRMCS User) in the applicable area/track.
+
+When a train approaches that FRMCS User (FRMCS Equipment of the trackside maintenance staff) and/or the warning indication entities of the warning system get notified.
+
+### 6.6.2.2 Pre-conditions
+
+The FRMCS Users as part of the warning system and the FRMCS Users as part of the maintenance crew are authorised to initiate the trackside maintenance warning system communication.
+
+### 6.6.2.3 Service flows
+
+The FRMCS Users (trackside maintenance warning system) and FRMCS User (trackside workers in the applicable area) initiate the trackside maintenance warning system communication to the receiving side.
+
+A secure data communication application is used for the trackside maintenance warning system communication. The communication requests the QoS class which matches the application category of CRITICAL DATA (see QoS section 12.10) within the FRMCS System.
+
+The arbitration is managed by the arbitration application.
+
+The communication is recorded by the Data recording application.
+
+### 6.6.2.4 Post-conditions
+
+The FRMCS Users are part of the (warning system) communication are able to exchange data.
+
+## 6.6.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------|
+| [R-6.6.2-001] | The FRMCS System shall be able to initiate data communication for Trackside Maintenance Warning System to FRMCS Users upon a request from a functional identity entitled to raise such communication. | A | 22.282 | Covered by R-5.2.2-XXX, 5.3.2-XXX, , R-5.4.2-XXX, 5.5.2-XXX |
+| [R-6.6.2-002] | For Trackside Maintenance Warning System the FRMCS System shall provide QoS, priority and communication setup time as defined in [Reference to QoS section 12.10]. | A | N/A | See section 12.10 below |
+| [R-6.6.2-003] | The FRMCS System shall be able to select FRMCS users to deliver the Trackside Maintenance Warning to base on their functional identity and their location. | A | 22.280 | Covered by [R-6.6.4.2-002a], [R-6.6.5.2-007] ] |
+
+## 6.6.3 Use case: Termination of a trackside maintenance warning system communication
+
+### 6.6.3.1 Description
+
+FRMCS Users are able to terminate data communication.
+
+### 6.6.3.2 Pre-conditions
+
+The data (trackside maintenance warning system) communication is ongoing.
+
+### 6.6.3.3 Service flows
+
+The FRMCS User terminates the trackside maintenance warning system communication with the receiving trackside worker applications.
+
+### 6.6.3.4 Post-conditions
+
+The data communication has been released disconnected.
+
+### 6.6.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------|
+| [R-6.6.3-001] | The FRMCS System shall be able to terminate the Trackside Maintenance Warning System data communication upon a request received from the functional identity that initiated the Trackside Maintenance Warning System data communication. | A | 22.282 | Covered by [R-6.2.3-001], [R-6.2.3-013] |
+
+## 6.7 Pushed Real Time Video streaming
+
+### 6.7.1 Introduction
+
+In this chapter the use cases related to real time video streaming are described, the following use cases are identified
+
+- Initiation of a real time video streaming
+- Termination of a real time video streaming
+
+### 6.7.2 Description
+
+The video image quality depends on the application needs, e.g. lip reading, pattern detection.
+
+Video based supervision for rail operational purposes requires also the support of Real time video capabilities from the FRMCS System. Multiple recipients are able to use the real time video for different purposes.
+
+The FRMCS Users in this case are applications both onboard of the train and on the ground, for example FRMCS Users in a train control center.
+
+For real time video streaming, both video and audio information are combined.
+
+### 6.7.3 Use case: Initiation of a real time video streaming
+
+#### 6.7.3.1 Description
+
+Video is streamed between FRMCS Users or FRMCS Equipment.
+
+#### 6.7.3.2 Pre-conditions
+
+The streaming FRMCS User or FRMCS Equipment has registered to a functional identity that is authorised to initiate a real time video stream.
+
+Note: Successful registration of a functional identity authorised to stream video implies the FRMCS Equipment is able to support streaming video (e.g. camera available)
+
+The receiving FRMCS User or FRMCS Equipment has registered to a functional identity that is authorised to receive a real time video stream.
+
+Note: Successful registration of a functional identity authorised to receive streaming video implies the FRMCS Equipment is able to support streaming video (e.g. monitor or recording device available)
+
+### 6.7.3.3 Service flows
+
+The initiating FRMCS User requests a real time video streaming to another FRMCS User.
+
+The video streaming requests the QoS class which matches to the application category of VIDEO or CRITICAL VIDEO within the FRMCS System, depending on the application needs.
+
+The video quality requested to the FRMCS System by the FRMCS User is checked by the FRMCS Application.
+
+If the requested quality can be reached, the FRMCS System establishes the real time video data communication with a setup time specified as NORMAL (see 12.12).
+
+If the requested quality cannot be reached, the FRMCS Application or the FRMCS User can decide to stop the request or to continue the setup of video streaming with a lower video quality, depending on the application needs.
+
+During the real time video streaming the FRMCS Application constantly monitors the quality. If the delivered quality of the real time video data communication changes, the FRMCS Application or the FRMCS User is informed about the change. The FRMCS Application or the FRMCS User may decide to change the quality of the real time video streaming, depending on the applications needs.
+
+If authorized, the real time video communication is recorded by the data recording and access to recorded data application.
+
+The arbitration is managed by the arbitration application.
+
+### 6.7.3.4 Post-conditions
+
+Depending on the QoS offered, the FRMCS Application or a FRMCS User decide if video streaming is set up.
+
+### 6.7.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|------------------------------------------------------------------------------------------|
+| [R-6.7.3-001] | Depending on the information associated with the functional identity used by the initiator, the FRMCS System shall setup the real time video streaming to one or more FRMCS User(s) identified by functional identities that are able and authorised to receive streaming video. | A | TS 22.281 (MCVideo) | Functional identities covered under User identities in 4.7 |
+| [R-6.7.3-002] | Real time video streaming requests shall be set up by the FRMCS System with a QoS, priority and setup time as defined in [Reference to QoS section 12.10]. | A | TS 22.281 (MCVideo) | Priority covered under Imminent Peril and Emergency cases. Corresponds to Critical Video |
+
+## 6.7.4 Use case: Termination of a real time video communication
+
+### 6.7.4.1 Description
+
+The FRMCS User is able to terminate a real time video communication.
+
+### 6.7.4.2 Pre-conditions
+
+There is an ongoing real time video data communication.
+
+### 6.7.4.3 Service flows
+
+The FRMCS Applications or FRMCS Users involved terminate the real time video data communication.
+
+### 6.7.4.4 Post-conditions
+
+The real time video data communication is terminated. The FRMCS Application or the FRMCS User is informed about the termination.
+
+### 6.7.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|----------------------------------------------------------|
+| [R-6.7.4-001] | Upon request from the streaming or receiving FRMCS User, the FRMCS System shall be able to terminate the real time video streaming. | A | TS 22.281 (MCVideo) | This is covered in requirement R-5.2.8-001 clause 5.2.8. |
+
+## 6.8 Public emergency call related use cases
+
+### 6.8.1 Introduction
+
+FRMCS Users have to indicate events that endanger public safety or emergency that requires the public safety involvement. For this reason, the FRMCS System is able to route the emergency call based on the current position of the initiating FRMCS User. The initiation of an emergency call has no dependency on the registration status of the FRMCS User.
+
+Depending on the national rules, the operator of the FRMCS System may decide if the routing of the public emergency numbers is supported.
+
+Following use cases related to public emergency call handling has been identified.
+
+- Initiation of a public emergency call
+- Termination of a public emergency call
+- Call back the public emergency call initiator
+
+## 6.8.2 Use case: Initiation of a public emergency call
+
+### 6.8.2.1 Description
+
+If enabled by the FRMCS System, an FRMCS User is able to report an emergency to an officer of the Public Safety Answering Point (PSAP) that will be responsible of bringing assistance or organizing response. The second scenario addresses the call back of a PSAP officer to the originator of the public emergency call which is a FRMCS User.
+
+### 6.8.2.2 Pre-conditions
+
+The underlying transport of the FRMCS System supports emergency calls and the FRMCS System allows FRMCS Users to make use of emergency calls.
+
+### 6.8.2.3 Service flows
+
+The FRMCS User or a public user initiates the public emergency call voice communication by dialling a public emergency call number.
+
+The voice communication is recorded by the voice recording and access application.
+
+The arbitration is managed by the arbitration application.
+
+### 6.8.2.4 Post-conditions
+
+The PSAP officer has received the public emergency call.
+
+### 6.8.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------|
+| [R-6.8.2-001] | The FRMCS System shall be able to allow or inhibit the processing of public emergency numbers. | A | TS 22.280 | TS 22.280 sub-clause 6.16 Requirement [R-6.16-001] |
+| [R-6.8.2-002] | In case public emergency call setup is allowed, the 3GPP defined handling of public emergency calls shall be applied. | A | TS 22.280 | TS 22.280 sub-clause 6.16 Requirement [R-6.16-001] |
+
+## 6.8.3 Use case: Termination of a public emergency call
+
+### 6.8.3.1 Description
+
+Both the initiating user, FRMCS User or a public user, and the PSAP officer shall be able to terminate the public emergency call voice communication.
+
+The PSAP officer shall be able to put on hold the public emergency communication.
+
+### 6.8.3.2 Pre-conditions
+
+The public emergency call is ongoing.
+
+### 6.8.3.3 Service flows
+
+#### PSAP officer on hold
+
+A PSAP officer shall be able to put the public emergency call on hold.
+
+After the PSAP officer has put the voice communication on hold, the communication remains in the FRMCS System, and the PSAP officer is able to be part of the communication again.
+
+#### Termination
+
+The FRMCS User or a public user, and/or the PSAP officer shall be able to terminate the public emergency call.
+
+The FRMCS System terminates the voice communication. All involved users are informed.
+
+### 6.8.3.4 Post-conditions
+
+The public emergency call voice communication is terminated.
+
+### 6.8.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------|
+| | No requirements.<br><br>Note: Procedures for normal emergency call behaviour applies if a call is allowed to be established. | | | |
+
+## 6.8.4 Use case: Call back the public emergency call initiator
+
+### 6.8.4.1 Description
+
+The PSAP officer shall be able to establish the communication towards the FRMCS user or a public user, who previously initiated the public emergency call (e.g. in the case the initial call was dropped).
+
+### 6.8.4.2 Pre-conditions
+
+The public emergency call initiator is reachable via FRMCS System or a public network.
+
+The FRMCS System is connected to the Public Safety Answering Point.
+
+### 6.8.4.3 Service flows
+
+The PSAP officer initiates the voice communication by using the subscriber identity or the device identity of the previous calling user, FRMCS User or a public user, of a public emergency call. The QoS class of the communication is managed by the QoS class application. The voice communication requests the QoS class which matches the application category of CRITICAL VOICE (see [QoS]) within the FRMCS System.
+
+The FRMCS System establishes the voice communication to the public emergency initiator within a setup time specified as IMMEDIATE (see [QoS]).
+
+The arbitration is managed by the arbitration application.
+
+The voice communication is recorded by the voice recording and access application.
+
+#### 6.8.4.4 Post-conditions
+
+The call-back of the public emergency call is ongoing.
+
+#### 6.8.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------|
+| | No requirements.<br><br>Normal emergency call service behaviour applies if a call is allowed to be established. | | | |
+
+### 6.9 Data communication for possession management related use cases
+
+#### 6.9.1 Introduction
+
+In this chapter the use cases related to possession management data communication are described, the following use cases are identified:
+
+- Initiation of a possession management data communication
+- Termination of a possession management data communication
+- Service interworking and service continuation with GSM-R
+
+#### 6.9.2 Use case: Initiation of a possession management data communication
+
+##### 6.9.2.1 Description
+
+The application supports the processes involved in taking possession of an area of railway infrastructure for engineering purposes (for example for track maintenance). This application is intended to allow track side workers to remotely take control of infrastructure elements to perform safe engineering works on those elements. The application provides the communication bearer in a safe and secure way. The possession management application is able to initiate, release data communication for possession related data of a certain track section.
+
+##### 6.9.2.2 Pre-conditions
+
+The initiator (Controller(s), trackside maintenance personnel, ground system) is authorised to initiate the possession management data communication.
+
+##### 6.9.2.3 Service flows
+
+The FRMCS Equipment initiates the possession management data communication towards the track possession management system.
+
+### 6.9.2.4 Post-conditions
+
+The communication for possession management has been established.
+
+Application messages can be exchanged between the possession management application and the possession management system.
+
+### 6.9.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.9.2-001] | The FRMCS System shall be able to support the transfer of messages to/from an authorised FRMCS Equipment identity, FRMCS User identity or functional identity with a QoS, priority and setup time as defined in clause 12.10 to/from an external system. | A | 22.280 | <p>[R-5.9a-020] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority to which a Private Communication (without Floor control) can be made by an MCX User registered to this particular functional alias.</p> <p>[R-5.9a-021] The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular functional alias, a set of functional aliases under the same authority from which Private Communication (without Floor control) is allowed to an MCX User registered to this particular functional alias.</p> <p>[R-5.9a-022] For private calls to functional aliases the authorizations in clause 5.9a.2 shall replace the authorizations defined in clause 6.7.3.</p> <p>[R-5.9a-023] The MCX Service system shall be capable of handling private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users by using group call mechanisms and by using first-to-answer private</p> |
+
+| | | | | |
+|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | <p>call mechanisms.</p> <p>[R-5.9a-024] The MCX Service system shall enable an MCX Service Administrator to select the mechanism to be used for handling of private calls to functional aliases that are allowed to be simultaneously active for multiple MCX Users.</p> |
+|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+## 6.10 Recording of communication
+
+### 6.10.1 Introduction
+
+In this chapter the use cases related to recording and access are described, the following use cases are identified
+
+- Recording
+
+### 6.10.2 Use case: Recording
+
+#### 6.10.2.1 Description
+
+The FRMCS System is able to provide means to record communication and communication related information for voice, video and data services. The means of recording include FRMCS User identities, functional identities and location information of all involved users.
+
+Which communication is applicable for recording is configurable. Criteria for recording can be based on different attributes or a combination of those e.g. communication application, functional identity, type of communication, location, certain context.
+
+#### 6.10.2.2 Pre-conditions
+
+A communication is configured to be recorded.
+
+#### 6.10.2.3 Service flows
+
+Recording of the communication starts when the particular communication becomes initiated.
+
+The recording stops when the communication is terminated.
+
+#### 6.10.2.4 Post-conditions
+
+The recorded communication is stored and ready for post-analysis
+
+#### 6.10.2.5 Potential requirements and gap analysis
+
+| Reference | Requirement text | Applicati | SA1 spec | Comments |
+|-----------|------------------|-----------|----------|----------|
+|-----------|------------------|-----------|----------|----------|
+
+| <b>Number</b> | | <b>on /<br/>Transport</b> | <b>covering</b> | |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.10.2-001] | The FRMCS System shall provide the means to record communication and communication related information to an external system. That encompasses voice, video and data services. | A | 22.280 | <p>On-Network: 6.15.4-001 - 010</p> <p>Off-Network: covered by [R-7.14-001]: Only metadata are logged, no recording of transmissions of group/private communications as provided in on-network ([R-6.15.4-003]).</p> |
+| [R-6.10.2-002] | <p>The FRMCS System shall be able to select the communication to be provided to the external system based on the following criteria:</p> <ul style="list-style-type: none"> <li>• Communication application / use case</li> <li>• FRMCS User identities</li> <li>• functional identities</li> <li>• location information of all involved users</li> </ul> | A | 22.280 | <p>On-Network: 6.15.4-001 - 010</p> <p>Off-Network: not applicable. No selection mechanism are supported. All communication and non-communication activity metadata from an MCX UE are collected.</p> |
+
+## 6.11 Remote control of engines communication related use cases
+
+### 6.11.1 Introduction
+
+In this chapter the use cases related to remote control of engines communication are described, the following use cases are identified
+
+- Initiation of a remote control of engines communication
+- Termination of a remote control of engines communication
+
+## 6.11.2 Use case: Initiation/termination of a remote control of engines communication
+
+### 6.11.2.1 Description
+
+Remote control requires secure data communication between the FRMCS Equipment as part of on-board control system and the FRMCS User as part of a remote-control device, either via Off-network or On-network communication.
+
+### 6.11.2.2 Pre-conditions
+
+The FRMCS User are authorised to initiate engine remote control communication.
+
+### 6.11.2.3 Service flows
+
+The FRMCS User at the ground initiates the engine remote control communication to the FRMCS Equipment in the locomotive.
+
+The communication requests the QoS which matches to the application category as defined by the operator within the FRMCS System.
+
+The FRMCS User at the ground terminates the engine remote control communication to the FRMCS Equipment in the locomotive.
+
+### 6.11.2.4 Post-conditions
+
+Remote control communication for the engine is established.
+
+## 6.11.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.11.2-001] | Upon a request received from an authorised FRMCS User, the FRMCS System shall establish or terminate communication for remote control of engines communication. | A | Covered 22.280 | Covered by [R-5.21.1.2-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely initiate an MCX Service Private Communication or MCX Service Group Communication from another user's MCX UE. [R-5.21.2.1-001] The MCX Service shall provide a mechanism for an authorized MCX User (e.g. dispatch operator) to remotely terminate an MCX Service Private Communication or MCX Service Group Communication from another user's MCX UE. |
+| [R-6.11.2-002] | The FRMCS System shall support engine remote control communication in both On-network and off-network communication mode. | A | Covered by 22.280 | As the whole section 5 is applicable for both on-network and off-network. i.e., "MCX Service requirements common for on the network and off the network"<br><br>So the requirements ("[R-5.21.1.2-001] and[R-5.21.2.0-001]") are naturally supported by on/off – network communication. |
+
+## 6.12 Automatic Train Operation data communication
+
+### 6.12.1 Introduction
+
+In this chapter the use cases related Automatic Train Operation (ATO) communication are described, the following use cases are identified
+
+- Initiation of an Automatic Train Operation data communication
+- Termination of an Automatic Train Operation data communication
+
+Note: A plain 3GPP bearer is requested below, as additional layers such as MCData are adding additional hurdles in achieving certification by railway regulatory authorities.
+
+## 6.12.2 Description
+
+Automatic Train Operation (ATO) is the application which performs some or all the functions of automatic speed regulation, accurate stopping, door opening and closing, performance level regulation, and other functions assigned to a train driver or train attendant.
+
+Some ATO systems require radio communication to interchange performance and/or safety relevant data between a train and the corresponding trackside control center.
+
+The (FRMCS) users in this case are the ATO application both on-board of the train and in the control center at the trackside (ground system).
+
+ATO systems may require communication between on-board applications of different trains (on-network).
+
+Some modes of ATO operation require real time video between a train and the corresponding trackside control center. Please refer to the Real Time Video streaming use cases.
+
+## 6.12.3 Use case: Initiation of an Automatic Train Operation data communication
+
+### 6.12.3.1 Description
+
+The FRMCS Application is able to initiate data communication.
+
+### 6.12.3.2 Pre-conditions
+
+The initiating functional identity is authorised to initiate the automatic train operation data communication to the trackside control centre.
+
+### 6.12.3.3 Service flows
+
+The initiating FRMCS Application (e.g. on-board of the train) initiates the Automatic Train Operation data communication to the receiving side (e.g. control centre at the trackside).
+
+### 6.12.3.4 Post-conditions
+
+ATO communication is established.
+
+Data can be exchanged between the Automatic Train Operation applications.
+
+### 6.12.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|-------------------------------------------------------|
+| [R-6.12.3-001] | Upon request received from a functional identity entitled to set up ATO communication the FRMCS System shall be able to setup and terminate a data bearer for ATO operation of a QoS, priority and setup time as defined in clause 12.10. | A | TS 22.282 (data bearer)<br>N/A (QoS) | TS 22.282 sub-clause 5.5.2<br>See section 12.10 below |
+
+## 6.13 Monitoring and control of critical infrastructure related use cases
+
+### 6.13.1 Introduction
+
+In this chapter the use cases related to monitoring and control of critical infrastructure communication are described. The following use cases are identified
+
+- Initiation of Monitoring and control of critical infrastructure communication
+- Termination of a Monitoring and control of critical infrastructure
+
+### 6.13.2 Use case: Initiation of a Monitoring and control of critical infrastructure communication
+
+#### 6.13.2.1 Description
+
+This use case enables FRMCS to setup data communication between infrastructure systems and a ground based or train based system in order to monitor or control critical infrastructure such as train detection, signals and indicators, movable infrastructure, level crossing elements, including barrier controls vehicle sensors, lighting controls and alarms.
+
+#### 6.13.2.2 Pre-conditions
+
+The initiating application is authorised to initiate Monitoring and control of critical infrastructure communication.
+
+The receiving application is authorised to use the Monitoring and control of critical infrastructure communication.
+
+#### 6.13.2.3 Service flows
+
+The initiating application initiates the monitoring and control of critical infrastructure communication to the receiving side.
+
+#### 6.13.2.4 Post-conditions
+
+Monitoring and control of critical infrastructure data is made available to the application.
+
+### 6.13.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.13.2-001] | Upon request from an authorised FRMCS Application the FRMCS System shall be able to establish data communication between a FRMCS Equipment and a central monitoring infrastructure system for monitoring and controlling critical infrastructures. | A | Covered by 22.282 | <p>[R-6.1.2.1.2-001] The MCData Service shall enable the control of robots.</p> <p>1) A FRMCS Equipment can be seen as a certain kind of robots.</p> <p>[R-6.1.3.2-001] The MCData Service shall provide a means to share in real-time operational status information between members of a selected group.</p> <p>2) Sharing the operational status information can be seen as monitoring.</p> |
+| [R-6.13.2-002] | The FRMCS System shall setup the monitoring of critical infrastructure communication with an operator defined QoS and priority and setup time as defined in clause 12.10. | A | TS 22.282 (data bearer)<br>N/A (QoS) | <p>Mission critical is already supported by 3GPP QoS (QCI or 5QI)</p> <p>[R-5.1.7-002] The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).</p> <p>See section 12.10 below.</p> |
+
+### 6.13.3 Use case: Termination of a Monitoring and control of critical infrastructure communication
+
+#### 6.13.3.1 Description
+
+Terminate data communication between infrastructure systems and a ground based or train-based system used to monitor or control critical infrastructure.
+
+#### 6.13.3.2 Pre-conditions
+
+The Monitoring and control of critical infrastructure applications have an ongoing data communication.
+
+### 6.13.3.3 Service flows
+
+One of the communication entities terminates the monitoring and control of critical infrastructure communication.
+
+### 6.13.3.4 Post-conditions
+
+The terminating Monitoring and control of critical infrastructure application entity is disconnected from the receiving application entity.
+
+### 6.13.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.13.3-001] | The FRMCS System shall be able to terminate data communication between the infrastructure systems and a central monitoring infrastructure system upon request by either communication partner. | A | Covered by 22.280, 22.282, | <p>TS 22.280 [R-6.7.6-002] The MCX Service shall provide a means by which an MCX User ends a Private Communication (without Floor control) in which the MCX User is a Participant. TS 22.282</p> <p>[R-5.4.2-008] The MCData data streaming capability shall allow an authorised user to terminate streaming of data being sent and cancel streaming of data remaining buffered in the system waiting to be streamed.</p> |
+
+## 6.14 Use case: Data transmission in real time
+
+### 6.14.1 Description
+
+This use case allows the authorized FRMCS Users to exchange data in real time from each other, for example, health and status of train are transferred between intelligent on-train systems and train maintenance.
+
+### 6.14.2 Pre-conditions
+
+The user A is authorized FRMCS User (e.g., administrator who has authorization to the data).
+
+User B is an equipment for monitoring the train.
+
+User C is a normal FRMCS User (e.g., user without authorization to the data)
+
+### 6.14.3 Service flows
+
+User A requests User B to transmit the data (e.g., health, status of train, etc.) in real time.
+
+User B receives the request from User A and accepts the request.
+
+User B starts to transmit the requested data in real time to User A.
+
+User C requests User B to transmit the data (e.g., health, status of train, etc.) in real time.
+
+User B receives the request from C and rejects the request (e.g., without authorization to the data).
+
+User C receives a notification that the request was rejected by User B.
+
+## 6.14.4 Post-conditions
+
+The data of User B is sent to User A in real time.
+
+The data of User B is not sent to User C in real time.
+
+## 6.14.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.14.5-001] | The FRMCS System shall enable an authorized FRMCS User to request another FRMCS User to establish real time data transmission. | A | TS 22.282 | Covered by 22.282 [R-5.5.2-003]: remote initiation of MCData Point-to-point IP connectivity between two MCData Users |
+| [R-6.14.5-002] | The FRMCS System shall provide a list of identities for the requesting authorized FRMCS User to select from. The list may contain functional identities, FRMCS User identities, or FRMCS Equipment Identities | A | TS 22.280 | Covered by functional alias requirements. |
+| [R-6.14.5-003] | The real time data request shall either be based on the functional identity, FRMCS User Identity, or FRMCS Equipment Identity. | A | TS 22.280 | [R-5.9a-002] If the MCX Service system supports functional aliases, the MCX User shall be reachable by its functional alias(es).<br><br>Functional Alias is specified by merging functional identity, user identity, and equipment identity. |
+| [R-6.14.5-004] | The FRMCS User shall be able to accept a real time data transmission request. | A | TS 22.282 | Only an authorised person can enable authorisation of IP connectivity to a specific destination. |
+| [R-6.14.5-005] | The FRMCS User shall be able to reject a data in real time transmission request. | A | TS 22.282 | Only an authorised person can revoke authorisation of IP connectivity to a specific destination. |
+| [R-6.14.5-006] | The requesting FRMCS User shall be notified if the request is rejected or ignored. | A | TS 22.282 | Implicit requirement. |
+
+## 6.15 On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
+
+### 6.15.1 Introduction
+
+This use case is based on the International Union of Railways User Requirements Specification on FRMCS [15].
+
+It is considered as a necessary scenario in China railway market that an authorised controller shall be able to set up a voice communication to a driver. As stated in URS 2.0, this application allows an authorised controller to establish voice communication with the driver of a specific train for operational purposes, for example to support the transfer of orders, to advise of delays, reporting of a disturbance, assault or staff security support.
+
+The controller shall be able to call the drivers located in the area managed by the controller.
+
+The controller can initiate the voice or video call to the drivers using the function alias.
+
+The following use cases related to the function of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers are defined.
+
+- Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
+- Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
+
+### 6.15.2 Use case: Initiation of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
+
+#### 6.15.2.1 Description
+
+An authorised Controller shall be able to set up a voice or video communication to the drivers within a configured area.
+
+#### 6.15.2.2 Pre-conditions
+
+The authorisation application authorises the Controller to call the drivers.
+
+#### 6.15.2.3 Service Flows
+
+##### Controller(s) to Drivers
+
+The Controller initiates the voice or video communication to the drivers. The priority of the communication is managed by the prioritisation application.
+
+The FRMCS System determines the drivers, based on:
+
+- Location information of the train provided by the locations services application, and/or
+- Functional identity provided by the Role management and presence application.
+- System configuration (To identify which Controller is responsible for which part of the track/station/etc.)
+
+The FRMCS System establishes the voice or video communication to the drivers within a setup time specified as NORMAL (see 12.10). The information from the Role management and presence application is used to present the
+
+identities for both Drivers and Controller. Also, the location of the Drivers is presented to the Controller which is retrieved from the location services application.
+
+If the controller is connected to more than one train, the multiuser talker control application is used.
+
+The voice or video communication is recorded by the Voice or video recording and access application.
+
+#### 6.15.2.4 Post-conditions
+
+The controller is connected to the requested drivers.
+
+#### 6.15.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------|
+| [R-6.15.2-001] | For Controller to drivers voice or video communication, the FRMCS System shall be able to determine the responsible driver(s), based on the location of the train and/or the function alias and/or the System configuration on the Controller who is responsible for which part of the track/station/etc. | A | 22.280 | 6.6.4.2 |
+
+#### 6.15.3 Use case: Termination of On-train incoming voice or video communication from the Controller(s) of the train towards the drivers
+
+##### 6.15.3.1 Description
+
+Only the controller can terminate the On-train incoming voice or video communication from the Controller(s) of the train towards the drivers.
+
+##### 6.15.3.2 Pre-conditions
+
+The controller is connected to the requested drivers.
+
+##### 6.15.3.3 Service Flows
+
+Only the controller is able to terminate the voice or video communication.
+
+##### 6.15.3.4 Post-conditions
+
+The controller terminates the voice or video communication.
+
+### 6.15.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------|
+| [R-6.15.3-001] | For Controller to Driver communication, only the controller shall be able to terminate the On-train incoming voice or video communication. | A | 22.280 | R-5.9a-012a<br>R-5.9a-012b |
+
+## 6.16 Use cases on data communication for Train Operation System Communication
+
+### 6.16.1 Introduction
+
+In this chapter the use cases related to data communication for Train Operation System are described. The following use cases are identified:
+
+- Train dispatch order data communication between driver and controller
+- LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive
+- Data communication for Security use cases between two approaching trains
+
+### 6.16.2 Use case: Train dispatch order data communication between controller and driver
+
+#### 6.16.2.1 Description
+
+In this use case, the FRMCS system transmits the train dispatch order between Controller and Driver, including train orders, station receiving route, running tokens, etc.
+
+It is needed that the information are received in due time by the driver to avoid any collision with any other train standing in another lines.
+
+#### 6.16.2.2 Pre-conditions
+
+User A and User B are authorized FRMCS User.
+
+User A is a Driver entering in the train station.
+
+User B is Controller of the train responsible for the train's current area.
+
+#### 6.16.2.3 Service flows
+
+User B initiates a data communication to User A in order to send station route within short time.
+
+#### 6.16.2.4 Post-conditions
+
+User A receives the station line to follow when entering in the train station.
+
+#### 6.16.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|-------------------------------------------------------|
+| 6.16.2-001 | The FRMCS system shall support data communication between Controller and Driver with a QoS, priority and setup time as defined in clause 12.10. | A | TS 22.282 (data bearer)<br>N/A (QoS) | TS 22.282 sub-clause 6.1.2<br>See section 12.10 below |
+
+### 6.16.3 Use case: LOCOTROL information transmission between leading engine and subordinate engine on a multi-headed locomotive
+
+#### 6.16.3.1 Description
+
+The multi-headed locomotive has several engines, all the engines act synchronized as the LOCOTROL information will be sent between engines through FRMCS system.
+
+It is quite important to ensure this LOCOTROL information is sent to the corresponding locomotives safely and in an integrated way so that synchronized actions can be taken.
+
+#### 6.16.3.2 Pre-conditions
+
+User A and User B are authorized FRMCS User.
+
+User A is a leading locomotive.
+
+User B is a subordinate locomotive.
+
+#### 6.16.3.3 Service flows
+
+User A initiates a data communication to send the LOCOTROL information to transport information regarding synchronization with the User B in safely and timely method, e.g., with a QoS and priority.
+
+#### 6.16.3.4 Post-conditions
+
+User B receives the LOCOTROL information, so User B can be kept synchronized with User A.
+
+### 6.16.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|-------------------------------------------------------|
+| 6.16.3-001 | The FRMCS system shall provide a mean to exchange messages between different FRMCS Equipment with a QoS, priority and setup time as defined in clause 12.10. | A | TS 22.282 (data bearer)<br>N/A (QoS) | TS 22.282 sub-clause 6.1.2<br>See section 12.10 below |
+
+## 6.16.4 Use case: data communication for security between two approaching trains
+
+### 6.16.4.1 Description
+
+This use case describes data communication between FRMCS Users in order to avoid train accident, for example, two trains exchange warning data to each other when one train is approaching to another train.
+
+And it is also used for the case that different devices in different carriages send detection data to head device in the train, so that the Driver can take appropriate actions.
+
+This data information needs to be transported in a safe and timely manner so that the train can operate in a safe way.
+
+### 6.16.4.2 Pre-conditions
+
+User A, User B, User C and User D are authorized FRMCS Users.
+
+User A is a Driver of train A.
+
+User B is FRMCS Equipment used for detection of the environment (sensor).
+
+User C is a Driver of train B.
+
+Train A is approaching to train B.
+
+### 6.16.4.3 Service flows
+
+Train driver User A initiates a data communication to the other train driver User C to indicate the approaching event to train B.
+
+The sensor User B initiates a data communication to train driver User A, to report what User B detected if some threshold is reached.
+
+These two communications are transported in safely and timely method
+
+### 6.16.4.4 Post-conditions
+
+Train driver User C receives the approaching event and takes appropriate action.
+
+Train driver User A receives the message from sensor User B.
+
+#### 6.16.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|-------------------------------------------------------|
+| 6.16.4-001 | The FRMCS system shall support data communication between FRMCS Users with a QoS, priority and setup time as defined in clause 12.10 | A | TS 22.282 (data bearer)<br>N/A (QoS) | TS 22.282 sub-clause 6.1.2<br>See section 12.10 below |
+
+### 6.17 On-train safety device to ground communication
+
+#### 6.17.1 Introduction
+
+Based on a critical situation in the train (for example, triggered by a Driver Safety Device (DSD) or Dead Man Switch, a voice and/or data communication is automatically set up towards a ground user (controller or ground system).
+
+In this chapter the use cases related to On-train safety device to ground communication are defined. The following use case describes:
+
+- Initiation, termination of the On-train safety device data communication
+- Voice communication between driver/train staff and controller/train control system
+
+#### 6.17.2 Use case: Initiation of safety device to ground data communication
+
+##### 6.17.2.1 Description
+
+- 1.) Based on a train safety issue, the Driver Safety Device will automatically establish a data communication to FRMCS User(s) at the ground (controller or train management system). The functional identity of the DSD and other FRMCS User(s) at the train are indicated to the FRMCS User(s) at the ground.
+- 2.) On demand a voice communication can be established by the train staff (FRMCS User) or the FRMCS User at the ground.
+
+##### 6.17.2.2 Pre-conditions
+
+The FRMCS User at the train is authorised to initiate Driver Safety Device data communication.
+
+The FRMCS User at the ground (controller or train management system) is authorised to receive Driver Safety Device data communication.
+
+##### 6.17.2.3 Service flows
+
+If the driver is not reacting to the DSD, the Driver Safety Device (FRMCS User) may initiate a data communication to the FRMCS User at the ground to notify the controller or train management system about the safety issue of a running train.
+
+After reception of this train safety issue, other trains in the same area get notified by an emergency alert to lower the instantaneous velocity of the train or stops completely.
+
+The FRMCS User at the ground (controller or train management system) acknowledges the reception of DSD emergency notification. The DSD emergency notification remains active and is continuously transmitted until the train safety has been recovered.
+
+In addition, the entitled train staff or entitled ground staff establishes a voice communication to commence further steps, to recover train safety again.
+
+#### 6.17.2.4 Post-conditions
+
+The emergency didn't cause a safety issue at other trains as well as the people in those trains.
+
+## 6.17.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------|
+| [R-6.17.2-001] | The FRMCS Equipment shall be able to integrate the Driver Safety Device (DSD). | A/T | N/A | Outside scope of 3GPP |
+| [R-6.17.2-002] | Triggering the Driver Safety Device (DSD) the FRMCS User related to the DSD shall be able to establish a non-pre-emptible data communication that matches with QoS category CRITICAL DATA (see QoS section), to FRMCS Users in the same area i.e. trains, controller and/or a train management system. | A | 22.280<br>22.282 | Covered by 22.282-5.2.2-XXX, 5.3.2-XXX, R-5.4.2-XXX, 5.5.2-XXX, 22.280 [R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007] |
+| [R-6.17.2-003] | The FRMCS System shall be able to forward the Driver Safety Device trigger to the Controller or external systems e.g. train operation management. | A | 22.280 | [R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007] |
+| [R-6.17.2-004] | Upon request by an authorised FRMCS user at the ground or the train, the FRMCS System shall be able to establish a non-pre-emptible voice communication. | A | 22.280 | Covered by [R-5.1.7-002], [R-5.6.2.2.1-006], [R-6.8.1-002], [R-6.8.1-003] |
+| [R-6.17.2-005] | <p>The FRMCS system shall determine the responsible FRMCS Users (e.g. trains, controllers or train management system) based on.</p> <ul style="list-style-type: none"> <li>• location information, instantaneous velocity and direction of the concerned train (DSD trigger active)</li> <li>• functional identity associated with the Driver Safety Device</li> </ul> | A | 22.280 | [R-5.1.7-002], [R-6.6.4.2-002a], [R-6.6.5.2-007] |
+
+| | | | | |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|-----------------------------------------|
+| | <ul style="list-style-type: none"> <li>responsible controller</li> </ul> | | | |
+| [R-6.17.2-006] | Upon request by the Driver Safety Device (DSD), authorised FRMCS Users or authorised external systems, the FRMCS System shall terminate the data communication related to the DSD. | A | 22.282 | Covered by [R-6.2.3-001], [R-6.2.3-013] |
+| [R-6.17.2-007] | For On-train safety device to ground communication, the communication shall be recorded by the recording and access to recorded data application. | A | 22.280 | [R-6.15.4-XXX] |
+
+## 6.18 Train Integrity monitoring data communication
+
+### 6.18.1 Introduction
+
+Train integrity encompasses the continuous verification of the train completeness, i.e. trains integrity status, for the time of mission. The safety system on-board the train and/or at the ground will apply the foreseen safety reaction when the train integrity status becomes undefined or is unknown.
+
+Due to its safety relevance, train integrity information exchange requires a very high reliable communication as well as very low packet data latency.
+
+### 6.18.2 Use case: Data communication for train integrity information exchange
+
+#### 6.18.2.1 Description
+
+The FRMCS System will be used to exchange such train integrity information. Every train regardless the type of composition requires this kind of data communication in a fully automated train operation scenario.
+
+The FRMCS Users in this case are the train integrity entities on-board of the train and the ground system. There several options to determine train integrity:
+
+- 1.) Train integrity information will be only determined by the applicable entities at the train. For this approach train integrity entities are located at the front and the end of the train as well as on demand partially between the front and the end. The front entity supplies the train's integrity status to the safety entity on-board the train responsible for Control Command Signalling. This scenario requires Off-network communication bearer services for multi-user communication.
+- 2.) Train integrity information will be determined by the applicable entities at the train and the ground. Train integrity entities are distributed equally over the total length of a train. The ground (train) integrity entity will collect the reported train integrity information and compute the train integrity status of a particular train. This scenario requires On-network communication bearer services.
+
+### 6.18.2.2 Pre-conditions
+
+The FRMCS Users (train integrity entities) are authorised to initiate a train integrity data communication.
+
+The FRMCS Users (train integrity entities) are authorised to use the train integrity application.
+
+### 6.18.2.3 Service flows
+
+#### Off-network communication
+
+On demand by the FRMCS Users (train integrity entities), the FRMCS System establishes a communication between the authorised FRMCS Users at the train. The data communication for train integrity requires the QoS class which matches the application category of CRITICAL DATA (see chapter 12.10) within the FRMCS system. The FRMCS system establishes the bearer service required for the data communication within a setup time specified as NORMAL (see 12.10).
+
+The FRMCS System verifies if the FRMCS Users are authorised to use the train integrity application.
+
+The FRMCS Users are exchanging continuously information about the train integrity until the end of the mission.
+
+The entire train integrity communication will be recorded.
+
+#### On-network communication
+
+On demand by the FRMCS Users (train integrity entities), the FRMCS System establishes a communication between the authorised FRMCS Users at the train and the ground. The data communication for train integrity requires the QoS class which matches the application category of CRITICAL DATA (see 12.10) within the FRMCS system. The FRMCS system establishes the bearer service required for the data communication within a setup time specified as NORMAL (see 12.10).
+
+The FRMCS System verifies if the FRMCS Users are authorised to use the train integrity application.
+
+The FRMCS Users are exchanging continuously information about the train integrity until the end of the mission.
+
+The entire train integrity communication will be recorded.
+
+### 6.18.2.4 Post-conditions
+
+Train integrity information can be exchanged continuously between the involved FRMCS Users
+
+The train approaches its final destination without any delay.
+
+## 6.18.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.18.2-001] | The FRMCS System shall allow authorised FRMCS Users to establish/terminate train integrity communication. | A | TS 22.282 | Sub-clause 5.5<br>The whole section 5 is applicable for both on-network and off-network. |
+| [R-6.18.2-002] | The FRMCS System shall allow authorised FRMCS Users to use train integrity monitoring. | A | TS 22.280 | TS 22.280 sub-clauses 5.1.x<br>The whole section 5 is applicable for both on-network and off-network. |
+| [R-6.18.2-003] | The FRMCS System shall provide the necessary communication means to support train integrity monitoring. | T | TS 22.282 | TS 22.282 sub-clause 5.5 (IP connectivity)<br><br>The whole section 5 is applicable for both on-network and off-network. |
+| [R-6.18.2-004] | The FRMCS System shall support train integrity monitoring in Off-network, On-network and a combination of On-network/Off-network mode. | T | TS 22.282<br>TS 22.280 | TS 22.282: IP connectivity sub-clause 5.5. The whole section 5 is applicable for both on-network and off-network.<br>TS 22.280:<br>On network is covered by sub-clause 6.<br>Off network covered (see all R-6.18.2-XXX requirements). |
+| [R-6.18.2-005] | The FRMCS System shall provide the QoS class as defined for CRITICAL DATA (see 12.10) within the FRMCS System. | A/T | N/A | See section 12.10 below |
+| [R-6.18.2-006] | The FRMCS System shall setup train integrity monitoring within the time specified as NORMAL (see 12.10). | A/T | N/A | See section 12.10 below |
+| [R-6.18.2-007] | The FRMCS System shall allow arbitration for Train Integrity communication. | A | TS 22.280 | TS 22.280 sub-clause 5.4.2<br>The whole section 5 is applicable for both on-network and off-network. |
+
+## 6.19 Use case: Broadcast of public emergency warning information
+
+### 6.19.1 Introduction
+
+A Public Safety Authority is able to broadcast a public emergency warning to a subset of the civil population based on their location. The subset can include FRMCS Users because of the location or functional identity of the FRMCS User.
+
+## 6.19.2 Description
+
+The Public Safety Authority (PSA) is able to broadcast textual messages, pictures, audio and video content to a subset of FRMCS Users.
+
+### 6.19.2a Pre-conditions
+
+The FRMCS User is active (logged in) in the FRMCS system.
+
+The FRMCS System provides interworking with a Public Safety Authority.
+
+## 6.19.3 Service flows
+
+The FRMCS System is receiving broadcasting information from the PSA.
+
+The FRMCS System determines the set of FRMCS Users based on:
+
+- The location provided by the PSA broadcast system and/or;
+- The functional addressing information of the concerned FRMCS Users provided by PSA and/or;
+- The system configuration (e.g. a fixed routing or other conditions).
+
+The FRMCS System establishes a data bearer services for PSA data communication which matches to the application category of CRITICAL DATA (see [QoS]).
+
+The FRMCS System establishes the data bearer service(s) within the timeframe specified as IMMEDIATE (see [QoS]).
+
+The data communication is recorded by the data recording and access application.
+
+## 6.19.4 Post-conditions
+
+The concerned FRMCS Users are informed about the public emergency information provided by the PSA.
+
+## 6.19.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------|
+| [R-6.19.5-001] | The FRMCS System shall provide the interworking to the Public Safety Authority broadcast information system to convey public emergency warning information to authorised FRMCS Users. | A/T | 22.268 | This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level. |
+| [R-6.19.5-002] | The FRMCS System shall be able to locate FRMCS User for PSA broadcast information based on the location information provided by the PSA broadcast system and/or the functional identities of the authorised FRMCS Users. | A | 22.268 | This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level. |
+| [R-6.19.5-003] | The FRMCS System shall be able to address PSA broadcast information to FRMCS User functional identities by using a "broadcast" functional identity. | A | 22.268 | This can be (partly) solved with existing PWS system [TS 22.268] or can be handled at application level. |
+
+## 6.20 Safety related critical advisory messaging
+
+### 6.20.1 Introduction
+
+Critical advisory information are exchanged among railway users in order to, for example, provide safety related instructions/information from a controller to a driver (e.g. written order, to inform about traffic disturbances, a change in the maximum authorized speed), provide information on how to proceed during an emergency, confirm to the controller the readiness of the train to start, exchange information between control centres on the traffic situation, etc.
+
+Messages can be exchanged on user-to-user or on multi-user level and the exchange is applicable in On-network, Off-network as well as a combination of On-network and Off-network mode.
+
+## 6.20.2 Use case: Initiation/Termination of safety device to ground data communication
+
+### 6.20.2.1 Description
+
+In this chapter the use cases related to Critical advisory messaging services – safety related- communication are described; the following use cases are identified:
+
+- The communication mode e.g. group communication required for Critical advisory messaging services
+- Service interworking with GSM-R
+
+### 6.20.2.2 Pre-conditions
+
+The FRMCS Users are authorised to initiate and terminate safety related - Critical advisory messaging service communication.
+
+### 6.20.2.3 Service flows
+
+The authorised FRMCS User at the train/ground establishes safety related – Critical advisory messaging session that corresponds to the category CRITICAL DATA (see QoS chapter).
+
+The FRMCS system establishes the bearer service required for the messaging-based communication within a setup time specified as IMMEDIATE (see QoS chapter).
+
+The FRMCS System assigns a certain priority of the safety related – Critical advisory messaging within arbitration management.
+
+The FRMCS Users provide their functional identity associated with the safety related – Critical advisory messaging communication.
+
+The FRMCS Users are reachable by their functional identity associated with the safety related – Critical advisory messaging communication.
+
+The FRMCS System records the communication of the involved FRMCS Users.
+
+An authorised FRMCS User is able to terminate the safety related – Critical advisory messaging communication.
+
+### 6.20.2.4 Post-conditions
+
+Safety related – Critical advisory messages can be exchanged among FRMCS Users.
+
+On demand by an authorised FRMCS User, the safety related – Critical advisory messaging communication is terminated.
+
+The FRMCS System was able to record the communication among the FRMCS Users.
+
+## 6.20.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.20.2-001] | The FRMCS System shall allow authorised FRMCS Users to establish/terminate Critical advisory messaging. | A | TS 22.280 | TS 22.280 sub-clauses 5.1.x |
+| [R-6.20.2-002] | The FRMCS System shall allow authorised FRMCS Users to use Critical advisory messaging. | A | TS 22.280 | TS 22.280 sub-clauses 5.1.x |
+| [R-6.20.2-003] | The FRMCS System shall be able to support Critical advisory messaging in Off-network mode, On-network mode as well as a combination of On-network and Off-network mode. | A | TS 22.280<br>TS 22.282 | .On network covered by TS 22.280 sub-clause 6.<br>.Partly covered by TS 22.282 sub-clause 5.2 SDS one-to-one and group but no predefined messages (not a 3GPP topic).<br>.Off-network is FFS. |
+| [R-6.20.2-004] | The FRMCS System shall be able to provide for Critical advisory messaging the QoS class of CRITICAL DATA (see QoS chapter). | A | N/A | See section 12.10 below |
+| [R-6.20.2-005] | The FRMCS System shall be able to manage Critical advisory messaging communication in the arbitration management. | A | TS 22.280 | TS 22.280 sub-clause 5.4.2 |
+| [R-6.20.2-006] | The FRMCS Users shall be reachable by their functional identity/ies. | A | TS 22.280 | [R-5.9a-002] |
+
+## 6.20.3 Use case: Service interworking with GSM-R
+
+### 6.20.3.1 Description
+
+Service interworking of safety related - Critical advisory messaging service communication with GSM-R is not required.
+
+6.20.3.2 Void
+
+6.20.3.3 Void
+
+6.20.3.4 Void
+
+6.20.3.5 Void
+
+## 6.21 Automatic Train Protection data communication
+
+### 6.21.1 Introduction
+
+In this chapter the use cases related Automatic Train Protection (ATP) data communication are described, the following use cases are identified:
+
+- Initiation of an Automatic Train Protection data communication
+- Termination of an Automatic Train Protection data communication
+- Service interworking with GSM-R
+
+### 6.21.2 Description
+
+Automatic Train Protection (ATP) is the application which performs some or all the functions that ensures the safe movement of a train. ATP supervises the train ensuring that speed and movement limits are kept and the train proceeds only when it is allowed to do so.
+
+Some ATP systems require radio communication to interchange safety relevant data between a train and the corresponding control center.
+
+The FRMCS Users in this case are the Automatic Train Protection applications both on-board of the train and in the control center at the trackside (ground system).
+
+Depending on the implementations, ATP systems require communication between on-board applications of different trains using On-network communication mode.
+
+ATP is considered to be user-to-user communication. Due to safety relevance of Automatic Train Protection (ATP), data communication requires a non-delay tolerant bearer service.
+
+### 6.21.3 Use case: Initiation of an Automatic Train Protection data communication
+
+#### 6.21.3.1 Description
+
+The FRMCS Application is able to initiate data communication for communication having continuous characteristics between the on-board applications and ground system and/or the on-board applications of other trains.
+
+#### 6.21.3.2 Pre-conditions
+
+The FRMCS User at the train and at the FRMCS User at ground are authorised to initiate the Automatic Train Protection data communication.
+
+The receiving application is authorised to use the Automatic Train Protection data communication.
+
+### 6.21.3.3 Service flows
+
+The FRMCS User (i.e. on-board of the train or the control center at the track side) initiates the Automatic Train Protection data communication (i.e. control center at the trackside or on-board the train).
+
+For the operation of ATP, a non-delay tolerant bearer service is required that corresponds to application category CRITICAL DATA/VERY CRITICAL DATA according to QoS definition in chapter 12.10.
+
+The FRMCS system takes into account the appropriate access criterion to establish the data bearer service within a setup time specified as IMMEDIATE (see QoS).
+
+The arbitration among ATP and other applications applies. The communication is recorded by the data recording application.
+
+### 6.21.3.4 Post-conditions
+
+ATP related data can be exchanged between the Automatic Train Protection communication entities.
+
+### 6.21.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|---------------------------------------------------------------------------------|
+| [R-6.21.3-001] | Upon request of an authorised FRMCS User, the FRMCS System shall be able to provide a non-delay tolerant data bearer for ATP data communication that matches to the application category of CRITICAL DATA/ VERY CRITICAL DATA (see QoS). | A/T | TS 22.282 (data bearer)<br>N/A (QoS) | TS 22.282 sub-clause 5.5.2<br>See section 12.10 below |
+| [R-6.21.3-002] | For ATP, the FRMCS System shall take into account the appropriate access criterion to establish the bearer service required for ATP communication within a setup time specified as IMMEDIATE (see 12.10). | A/T | N/A | See section 12.10 below |
+| [R-6.21.3-003] | The FRMCS System shall apply arbitration to ATP data communication. | A | TS 22.280 | Arbitration:<br>[R-5.4.2-004]<br>[R-5.4.2-004A]<br>[R-5.4.2-004B] |
+| [R-6.21.3-004] | The ATP data communication shall be recorded. | A | TS 22.280 | [R-6.15.4-003] for on-network<br>Not applicable to off-network (see table C-1). |
+
+## 6.21.4 Use case: Termination of an Automatic Train Protection data communication
+
+### 6.21.4.1 Description
+
+The FRMCS User is able to terminate data communication.
+
+#### 6.21.4.2 Pre-conditions
+
+The Automatic Train Protection related data communication is ongoing.
+
+#### 6.21.4.3 Service flows
+
+The FRMCS User (i.e. on-board of the train or the control centre at the track side) terminates the Automatic Train Protection data communication.
+
+The FRMCS System terminates the bearer service required for ATP related data communication.
+
+#### 6.21.4.4 Post-conditions
+
+The Automatic Train Protection data communication has been released.
+
+#### 6.21.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.21.4-001] | The FRMCS User shall be able to terminate the Automatic Train Protection data communication. The FRMCS System shall terminate the bearer service. | A | TS 22.280 | TS 22.280 Requirements [R-6.4.9-001] on termination conditions.<br>[R-6.7.6-002]<br>7.4: specific termination conditions for off-net. |
+
+### 6.22 Voice communication transfer related use cases
+
+#### 6.22.1 Introduction
+
+In this chapter the use cases related to the transfer of incoming or ongoing voice communication are defined. The following use cases are defined:
+
+- Transfer of an incoming voice communication
+- Transfer of an ongoing voice communication
+- Service interworking and service continuation with GSM-R
+
+To provide some background, a description of one use case based on operational rules is described: a railway station could temporarily be closed for any operational reasons. In that case, railway staff could not be joined anymore. A mechanism of transferring calls to railway staff located in another railway stations shall be provided.
+
+The use cases are applicable for user-to-user voice communications.
+
+#### 6.22.2 Use case: Transfer of an incoming voice communication
+
+##### 6.22.2.1 Description
+
+When FRMCS User receives a notification of an incoming voice communication, and the FRMCS Equipment does not automatically accept the communication, the FRMCS User, if authorised, shall be able to transfer the communication to another FRMCS User.
+
+#### 6.22.2.2 Pre-conditions
+
+FRMCS User is registered to a single or multiple FRMCS Equipment.
+
+FRMCS User is or is not part of an ongoing communication.
+
+#### 6.22.2.3 Service flows
+
+The FRMCS System provides and activates a mechanism to transfer communications.
+
+FRMCS User is authorised to use the mechanism to transfer communications.
+
+When the notification of an incoming voice communication is received by the FRMCS equipment, a notification is presented to appropriate FRMCS User allowing the transfer of the incoming voice communication to another FRMCS User.
+
+FRMCS User selects the new FRMCS User out of a list (e.g. telephone book) or entered manually based on either FRMCS User Identity, FRMCS Functional Identity or MSISDN.
+
+The arbitration is managed by the arbitration application.
+
+#### 6.22.2.4 Post-conditions
+
+The incoming voice communication is transferred to the new FRMCS User by the FRMCS System.
+
+## 6.22.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-6.22.2-001] | The FRMCS System shall enable FRMCS User to transfer incoming voice communications based on different criteria | A/T | 22.179 | Limited to private calls because group communication already provides other mechanisms [R-5.6.3-015], [R-6.7.4-016] |
+| [R-6.22.2-002] | The FRMCS System shall support the transfer of incoming voice communications based on following criteria: <ul style="list-style-type: none"> <li>• Unconditional;</li> <li>• When not reachable;</li> <li>• Busy;</li> <li>• Not answering;</li> </ul> | A/T | 22.179<br>22.280 | Partly covered (Busy excluded). Limited to private calls because group communication already provides other mechanisms [R-5.6.3-015], [R-6.7.4-016]. Busy concept no more applicable to MCX: an MCX UE/client can be simultaneously engaged in multiple private calls, or even mixed in private and group calls (see 22.179 5.5 & 22.280 5.4 & 6.14). |
+| [R-6.22.2-003] | The FRMCS System shall be able to support configurable time when the FRMCS User is busy and shall be able to support configurable time when the FRMCS User is not answering | A/T | 22.179<br>22.280 | Partly covered (Busy excluded). Limited to private calls because group communication already provides other mechanisms [R-5.6.3-015], [R-6.7.4-016]. Busy concept no more applicable to MCX: an MCX UE/client can be simultaneously engaged in multiple private calls, or even mixed in private and group calls (see 22.179 5.5 & 22.280 5.4 & 6.14). |
+| [R-6.22.2-004] | The FRMCS System shall support the transfer of incoming voice communications for user-to-user. | A/T | 22.179 | Indicated by sub-clause 5.6.3 Private Call (with Floor control) commencement requirements<br>6.7.4 Private Call (without Floor control) commencement requirements |
+| [R-6.22.2-005] | The FRMCS System shall be aware of the busy condition of the targeted FRMCS user to forward the incoming voice communication to another FRMCS User. | A/T | 22.179 | Partly covered (Busy excluded). Limited to private calls because group communication already provides other mechanisms [R-5.6.3-015], [R-6.7.4-016]. Busy concept no more applicable to MCX: an MCX UE/client can be simultaneously engaged in multiple private calls, or even mixed in private and group calls (see 22.179 5.5 & 22.280 5.4 & 6.14). |
+
+## 6.22.3 Use case: Transfer of an ongoing voice communication
+
+### 6.22.3.1 Description
+
+When FRMCS User is part of an ongoing voice communication, FRMCS User, if authorised, shall be able to transfer the communication to another FRMCS User.
+
+### 6.22.3.2 Pre-conditions
+
+FRMCS User is registered to a single or multiple FRMCS Equipment.
+
+FRMCS User is part of an ongoing voice communication.
+
+The FRMCS System provides and activates a mechanism to transfer communications.
+
+FRMCS User is authorised to use the mechanism to transfer communications.
+
+### 6.22.3.3 Service flows
+
+Whilst in an ongoing voice communication, the FRMCS Equipment provides an option to the FRMCS User allowing the transfer of the current communication to another FRMCS User.
+
+FRMCS User selects the new FRMCS User out of a list (e.g. telephone book) or entered manually based on either FRMCS User Identity, FRMCS Functional Identity or MSISDN.
+
+### 6.22.3.4 Post-conditions
+
+The ongoing voice communication is transferred to the new FRMCS User by the FRMCS System.
+
+### 6.22.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------|
+| [R-6.22.3-001] | The FRMCS System shall enable FRMCS User to transfer ongoing voice communications. | A/T | 22.179 | Limited to private calls because group communication already provides other mechanisms [R-5.6.3-014], [R-6.7.4-015] |
+
+## 6.22.4 Use case: Service interworking with GSM-R
+
+### 6.22.4.1 Description
+
+For coexistence between FRMCS System and the legacy GSM-R communication system, service interworking among the systems is required.
+
+Transfer of incoming voice communication to a GSM-R User shall be provided by the FRMCS System.
+
+Transfer of ongoing communication to a GSM-R User shall be provided by the FRMCS System.
+
+Service interworking for the automatic transfer function is not required.
+
+#### 6.22.4.2 Pre-conditions
+
+FRMCS User is attached to the FRMCS System.
+
+GSM-R User is attached to GSM-R System.
+
+The transfer procedure (either transfer of incoming voice communication or transfer of ongoing communication) has been initiated by the FRMCS User.
+
+#### 6.22.4.3 Service flows
+
+FRMCS User selects the new GSM-R User out of a list (e.g. telephone book) or entered manually based on the functional address of the GSM-R User or E.164 numbering plan.
+
+#### 6.22.4.4 Post-conditions
+
+The incoming voice communication or the ongoing voice communication is transferred to the new GSM-R User by the FRMCS System.
+
+#### 6.22.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------|
+| [R-6.22.4-001] | The FRMCS System shall allow FRMCS User to forward of incoming voice communications and transfer of ongoing communication to GSM-R User using the applicable the addressing scheme. | A/T | 22.280 | [R-5.19.2-006] |
+
+---
+
+## 7 Performance communication applications related use cases
+
+### 7.1 Use cases related to transmission of real time video
+
+#### 7.1.1 Introduction
+
+In this clause, the use cases related to the function of transmitting video in real time are defined.
+
+- An FRMCS User requesting another FRMCS User to transmit real time video
+- An FRMCS User receiving a request to transmit real time video
+- An FRMCS User accepting a request to transmit real time video
+- An FRMCS User rejecting a request to transmit real time video
+- An FRMCS User ignoring a request to transmit real time video
+
+## 7.1.2 Use Case: An FRMCS User requesting another FRMCS User to transmit real time video
+
+### 7.1.2.1 Description
+
+An FRMCS User can request another FRMCS User to transmit real time video.
+
+### 7.1.2.2 Pre-conditions
+
+The FRMCS User has a functional Role entitled to request other FRMCS Users to transmit real time video.
+
+The requested FRMCS User can be addressed by the assigned functional identity(ies), FRMCS User Identity, or FRMCS Equipment Identity.
+
+The FRMCS Equipment of the requested user is capable of providing video
+
+### 7.1.2.3 Service flows
+
+#### Requesting FRMCS User
+
+From a list of FRMCS Users provided by the FRMCS System, or by entering an unlisted identity, the requesting FRMCS User selects another FRMCS User to be invited. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities, or phone numbers.
+
+### 7.1.2.4 Post-conditions
+
+The FRMCS User has been requested transmission of real time video.
+
+### 7.1.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------|
+| [R-7.1.2-001] | The FRMCS System shall enable an entitled FRMCS User to request another FRMCS User to transmit video in real time. | A | 22.281 | 5.1.2.2.2-xxx |
+| [R-7.1.2-002] | The FRMCS System shall provide a list of identities for the requesting FRMCS User to select from. The list may contain functional identities, FRMCS User identities, FRMCS Equipment Identities or E.164 numbers. | A | 22.281 | 5.1.3.2.2-xxx |
+| [R-7.1.2-003] | The real time video request shall either be based on the functional identity, FRMCS User Identity, FRMCS Equipment Identity or E.164 number. | A | 22.280 | This requirement is covered by MCCore for rail esp. 5.9a |
+
+### 7.1.3 Use Case: An FRMCS User receiving a real time video request to transmit real time video
+
+#### 7.1.3.1 Description
+
+An FRMCS User will receive a real time video request originated by the requesting FRMCS User.
+
+#### 7.1.3.2 Pre-conditions
+
+The FRMCS User has a functional Role that is entitled to receive real time video request from other FRMCS Users.
+
+The FRMCS User's equipment has a capability to capture real time video.
+
+NOTE: Examples of Role management, like functional Roles, functional identities, FRMCS Equipment Identities, etc. in the railway environment are covered by Annex A.
+
+The FRMCS User may or may not be transmitting real time video to an FRMCS User different from the requesting FRMCS User.
+
+#### 7.1.3.3 Service flows
+
+##### Requested FRMCS User
+
+The real time video request is indicated to the FRMCS User by audible and visual notification. If the FRMCS User is not managed by a human, the audible and visual notification is not necessary.
+
+#### 7.1.3.4 Post-conditions
+
+The FRMCS User has received the real time video request.
+
+Ongoing real time video transmission of the requested FRMCS User continues unaffected.
+
+#### 7.1.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------|
+| [R-7.1.3-001] | The FRMCS System shall be able to deliver requests for real time video to a FRMCS User entitled to provide real time video independent of the FRMCS User being involved in another ongoing real time video transmission without excessively using radio resources. | A | 22.281 | 5.1.3.2.2-xxx |
+
+### 7.1.4 Use case: An FRMCS User accepting a request to transmit real time video
+
+#### 7.1.4.1 Description
+
+An FRMCS User can accept the invitation sent by the requesting FRMCS User.
+
+#### 7.1.4.2 Pre-conditions
+
+The FRMCS User has received a request to transmit real time video.
+
+#### 7.1.4.3 Service flows
+
+##### Requested FRMCS User
+
+The FRMCS User accepts the request to transmit real time video.
+
+##### Requesting FRMCS User
+
+The FRMCS User receives a notification that the requested FRMCS User accepted the request.
+
+#### 7.1.4.4 Post-conditions
+
+The requested FRMCS User captures and transmits video in real time to the requesting FRMCS User.
+
+In case the FRMCS User receives multiple requests to stream the video, the FRMCS System will handle this in a resource efficient way i.e. by streaming the video from the FRMCS User to the FRMCS System via the radio only once and distributing it from there to the different FRMCS Users.
+
+#### 7.1.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------|
+| [R-7.1.4-001] | The FRMCS User shall be able to accept to accept a real time video transmission request. | A | 22.281 | 5.1.3.2.2-xxx esp. 5.1.3.2.2-003<br>5.2.6.2.1-xxx |
+| [R-7.1.4-002] | If entitled to, a FRMCS User shall be able to provide real time video captured by itself to the FRMCS User requesting the video. | A | 22.281 | 5.1.3.2.2-xxx esp. 5.1.3.2.2-003<br>5.2.6.2.1-xxx |
+| [R-7.1.4-003] | In case of multiple requests to stream the same video to several FRMCS Users the FRMCS System shall handle this in a resource efficient manner. | A | 22.281 | 5.2.6.2.4-001 |
+
+### 7.1.5 Use case: An FRMCS User rejecting a request to transmit real time video
+
+#### 7.1.5.1 Description
+
+An FRMCS User can reject the invitation sent by the requesting FRMCS User.
+
+#### 7.1.5.2 Pre-conditions
+
+The FRMCS User has received a request to transmit real time video.
+
+#### 7.1.5.3 Service flows
+
+##### Requested FRMCS User
+
+The FRMCS User rejects the request to transmit real time video.
+
+#### Requesting FRMCS User
+
+The FRMCS User receives a notification that the requested FRMCS User rejected the request.
+
+#### 7.1.5.4 Post-conditions
+
+The requested FRMCS User does not transmit video to the requesting FRMCS User.
+
+#### 7.1.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------|
+| [R-7.1.5-001] | The FRMCS User shall be able to reject a real time video transmission request. | A | 22.281 | 5.2.6.2.4-xxx |
+| [R-7.1.5-002] | The FRMCS System shall automatically reject requests to FRMCS Users not entitled to provide video or not capable of providing video (e.g. no camera in the FRMCS Equipment). | A | 22.281 | 5.2.6.2.4-001<br>5.1.3.1.2-001 |
+| [R-7.1.5-003] | The requesting FRMCS User shall be notified of the reason for rejection. | A | 22.280 | This is an implicit functionality of group communication setup 6.2.1-xxx |
+
+### 7.1.6 Use case: An FRMCS User ignoring a request to transmit real time video
+
+#### 7.1.6.1 Description
+
+An FRMCS User can ignore the invitation sent by the requesting FRMCS User.
+
+#### 7.1.6.2 Pre-conditions
+
+The FRMCS User has received a request to transmit real time video.
+
+#### 7.1.6.3 Service flows
+
+The requested FRMCS User does not respond.
+
+The timeout expires.
+
+The requesting FRMCS User receives a notification that the invitation was rejected due to a timeout.
+
+#### 7.1.6.4 Post-conditions
+
+The requested FRMCS User does not transmit video to the requesting FRMCS User.
+
+### 7.1.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------|
+| | FRMCS User | | | |
+| [R-7.1.6-001] | If the receiving FRMCS User has not reacted on the invitation within a certain period of time [t1] the FRMCS System shall notify the inviting FRMCS User accordingly and stop the invitation request. | | 22.280 | This is an implicit functionality of group communication setup 6.2.1-xxx |
+
+## 7.2 Transfer of CCTV archives related use cases
+
+### 7.2.1 Introduction
+
+In this chapter, the use cases related to CCTV and the use of FRMCS are defined.
+
+- Transfer of CCTV archives from Train to Ground
+- Massive Inter-carriage data transfer
+
+### 7.2.2 Use Case: Bulk Transfer of CCTV archives from Train to Ground
+
+#### 7.2.2.1 Description
+
+This use case describes the bulk transfer of CCTV archives from the on-board system to the ground system. This use case assumes the following:
+
+- The retention time for the recordings in the on-board system is seven days.
+- The minimum retention time for the CCTV recordings in the ground system is 31 days.
+- Bulk transfer of CCTV archives is performed only when train approaches stations in order to stop and at the depot.
+
+An example calculation of the CCTV storage need during 31 days period is provided in Figure.7.2.2.1-1.
+
+
+
+**Onboard CCTV storage sizes with different offload rates**
+
+The graph illustrates the onboard CCTV storage sizes (in TBytes) over a period of 35 days for different offload rates. The parameters used for the calculation are:
+
+- Num of cams: 16
+- resolution: 1080p
+- 15 fps
+- h264
+- 4.1 Mbps / cam
+
+The legend indicates the following offload rates:
+
+- 7 day storage (orange line)
+- No Offload (blue line)
+- 25% offload (black line)
+- 50% Offload (light blue line)
+- 75% Offload (grey line)
+
+| Number of days | 7 day storage (TBytes) | No Offload (TBytes) | 25% offload (TBytes) | 50% Offload (TBytes) | 75% Offload (TBytes) |
+|----------------|------------------------|---------------------|----------------------|----------------------|----------------------|
+| 0 | 4.8 | 0.0 | 0.0 | 0.0 | 0.0 |
+| 5 | 4.8 | 3.3 | 2.5 | 1.6 | 0.8 |
+| 10 | 4.8 | 6.6 | 5.0 | 3.3 | 1.6 |
+| 15 | 4.8 | 9.9 | 7.5 | 5.0 | 2.4 |
+| 20 | 4.8 | 13.2 | 10.0 | 6.6 | 3.2 |
+| 25 | 4.8 | 16.5 | 12.5 | 8.3 | 4.0 |
+| 30 | 4.8 | 19.8 | 15.0 | 10.0 | 4.8 |
+| 35 | 4.8 | 23.1 | 17.5 | 11.7 | 5.6 |
+
+Line graph showing onboard CCTV storage sizes in TBytes over 35 days for different offload rates. The graph shows that storage size increases with time for all offload rates, but is significantly lower for higher offload percentages. A horizontal orange line represents the 7-day storage limit.
+
+**Figure.7.2.2.1-1. Onboard CCTV storage sizes with different offload rates.**
+
+Next, an example estimation is provided to illustrate the offload performance with different uplink speeds, when the train is commuting from Helsinki to Kemijärvi. The parameters for the calculation are provided in Table 1, whereas the offload results for uplink speeds of 400 Mbps, 750 Mbps and 1000 Mbps are provided respectively in Figure 7.2.2.1-2, Figure 7.2.2.1-3 and in Figure 7.2.2.1-4.
+
+| Station | Arrives | Departs | Stop time | Time between stations |
+|-------------|---------|---------|-----------|-----------------------|
+| HELSINKI | | 18:52 | | |
+| PASILA | 18:57 | 19:00 | 0:03 | 0:08 |
+| TIKKURILA | 19:41 | 19:44 | 0:03 | 0:44 |
+| RIIHIMÄKI | 20:19 | 20:22 | 0:03 | 0:38 |
+| HÄMEENLINNA | 20:46 | 20:48 | 0:02 | 0:26 |
+| TAMPERE | 21:38 | 22:11 | 0:33 | 1:23 |
+| PARKANO | 23:03 | 23:06 | 0:03 | 0:55 |
+| SEINÄJOKI | 0:08 | 0:10 | 0:02 | 1:04 |
+| KOKKOLA | 1:37 | 1:39 | 0:02 | 1:29 |
+| YLIVIESKA | 3:10 | 3:12 | 0:02 | 1:33 |
+
+| | | | | |
+|-----------|------|------|------|------|
+| | | | | |
+| OULU | 4:42 | 5:00 | 0:18 | 1:48 |
+| KEMI | 6:08 | 6:12 | 0:04 | 1:12 |
+| ROVANIEMI | 7:47 | 7:55 | 0:08 | 1:43 |
+| MISI | 8:31 | 8:32 | 0:01 | 0:37 |
+| KEMIJÄRVI | 9:00 | 9:05 | 0:05 | 0:33 |
+
+Table 7.2.2.1-1. The parameters for the offload calculation for the train route between Helsinki and Kemijärvi.
+
+
+
+| Location | Data In (Mbits) | Data Output capacity (Mbits) | Left (Mbits) |
+|-------------|-----------------|------------------------------|--------------|
+| HELSINKI | 0 | 0 | 0 |
+| PASILÄ | 50000 | 100000 | 50000 |
+| TIKKURILA | 150000 | 100000 | 100000 |
+| RIIHIMÄKI | 250000 | 100000 | 150000 |
+| HÄMEENLINNA | 280000 | 100000 | 200000 |
+| TAMPERE | 550000 | 900000 | 350000 |
+| PARKANO | 220000 | 100000 | 150000 |
+| SEINÄJOKI | 380000 | 100000 | 350000 |
+| KOKKOLA | 680000 | 100000 | 650000 |
+| YLIVIESKA | 1000000 | 100000 | 950000 |
+| OULU | 1380000 | 500000 | 880000 |
+| KEMI | 1180000 | 100000 | 1050000 |
+| ROVANIEMI | 1480000 | 200000 | 1250000 |
+| MISI | 1400000 | 100000 | 1380000 |
+| KEMIJÄRVI | 1500000 | 150000 | 1350000 |
+
+Bar chart showing offload results in Mbits for various locations along a train route. The Y-axis represents Mbits from 0,00 to 1600000,00. The X-axis lists locations: HELSINKI, PASILA, TIKKURILA, RIIHIMÄKI, HÄMEENLINNA, TAMPERE, PARKANO, SEINÄJOKI, KOKKOLA, YLIVIESKA, OULU, KEMI, ROVANIEMI, MISI, KEMIJÄRVI. The legend indicates three data series: Data In (blue), Data Output capacity (brown), and Left (red).
+
+Figure 7.2.2.1-2. The offload results with uplink speed of 450 Mbps.
+
+
+
+| Station | Data In (Mbits) | Data Output capacity (Mbits) | Left (Mbits) |
+|-------------|-----------------|------------------------------|--------------|
+| HELSINKI | ~10,000 | ~10,000 | ~10,000 |
+| PASILA | ~10,000 | ~150,000 | ~10,000 |
+| TIKKURILA | ~180,000 | ~150,000 | ~10,000 |
+| RIIHIMÄKI | ~180,000 | ~150,000 | ~10,000 |
+| HÄMEENLINNA | ~150,000 | ~100,000 | ~10,000 |
+| TAMPERE | ~400,000 | ~1450,000 | ~10,000 |
+| PARKANO | ~220,000 | ~100,000 | ~10,000 |
+| SEINÄJOKI | ~350,000 | ~250,000 | ~10,000 |
+| KOKKOLA | ~600,000 | ~500,000 | ~10,000 |
+| YLIVIESKA | ~850,000 | ~800,000 | ~10,000 |
+| OULU | ~1200,000 | ~400,000 | ~10,000 |
+| KEMI | ~700,000 | ~200,000 | ~10,000 |
+| ROVANIEMI | ~900,000 | ~550,000 | ~10,000 |
+| MISI | ~700,000 | ~200,000 | ~10,000 |
+| KEMIJÄRVI | ~800,000 | ~550,000 | ~10,000 |
+
+Bar chart showing offload results for 750 Mbps uplink speed across various stations. The Y-axis is labeled 'Mbits' and ranges from 0,00 to 1600000,00. The X-axis lists stations: HELSINKI, PASILA, TIKKURILA, RIIHIMÄKI, HÄMEENLINNA, TAMPERE, PARKANO, SEINÄJOKI, KOKKOLA, YLIVIESKA, OULU, KEMI, ROVANIEMI, MISI, KEMIJÄRVI. The legend indicates three data series: Data In (blue), Data Output capacity (red), and Left (dark red).
+
+Figure 7.2.2.1-3. The offload results with uplink speed of 750 Mbps.
+
+
+
+| Station | Data In (Mbits) | Data Output capacity (Mbits) | Left (Mbits) |
+|-------------|-----------------|------------------------------|--------------|
+| HELSINKI | ~10,000 | ~10,000 | ~10,000 |
+| PASILA | ~10,000 | ~200,000 | ~10,000 |
+| TIKKURILA | ~200,000 | ~200,000 | ~10,000 |
+| RIIHIMÄKI | ~200,000 | ~200,000 | ~10,000 |
+| HÄMEENLINNA | ~150,000 | ~100,000 | ~10,000 |
+| TAMPERE | ~350,000 | ~2000,000 | ~10,000 |
+| PARKANO | ~250,000 | ~200,000 | ~10,000 |
+| SEINÄJOKI | ~300,000 | ~200,000 | ~10,000 |
+| KOKKOLA | ~500,000 | ~400,000 | ~10,000 |
+| YLIVIESKA | ~800,000 | ~650,000 | ~10,000 |
+| OULU | ~1100,000 | ~1100,000 | ~10,000 |
+| KEMI | ~300,000 | ~250,000 | ~10,000 |
+| ROVANIEMI | ~450,000 | ~450,000 | ~10,000 |
+| MISI | ~150,000 | ~100,000 | ~10,000 |
+| KEMIJÄRVI | ~250,000 | ~300,000 | ~10,000 |
+
+Bar chart showing offload results for 1000 Mbps uplink speed across various stations. The Y-axis is labeled 'Mbits' and ranges from 0,00 to 2500000,00. The X-axis lists stations: HELSINKI, PASILA, TIKKURILA, RIIHIMÄKI, HÄMEENLINNA, TAMPERE, PARKANO, SEINÄJOKI, KOKKOLA, YLIVIESKA, OULU, KEMI, ROVANIEMI, MISI, KEMIJÄRVI. The legend indicates three data series: Data In (blue), Data Output capacity (red), and Left (dark red).
+
+Figure 7.2.2.1-4. The offload results with uplink speed of 1000 Mbps.
+
+### 7.2.2.2 Pre-conditions
+
+- Bulk transfer of CCTV archives is performed only when the train stops at the stations.
+- Mobile communication infrastructure between train and ground system enables transfer of CCTV archives from train to the ground system while the train stops at the stations.
+
+- The ground system supports sufficient archiving system for the transferred recordings.
+
+### 7.2.2.3 Service flows
+
+1. The train approaches the station.
+2. Mobile communication system in train establishes connection dedicated for the transfer of CCTV archives with the ground system at a priority level allowing critical communication to continue in parallel
+3. The transfer of CCTV archives is started upon successful connection with the ground system.
+4. The transfer of CCTV archives is stopped when the connection is no longer available.
+
+### 7.2.2.4 Post-conditions
+
+- The on-board CCTV system may re-write over the seven days and older recordings that have been transferred.
+- The on-board mobile communication system remains monitoring the next approach of station.
+
+### 7.2.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-7.2.2-001] | The FRMCS System shall be able to support that CCTV archives can be transferred into the ground system in a time and resource efficient way with a minimum of 1 Gbps in dedicated places such as stations or train depots. | A/T | TS 22.289 | See:<br><a href="http://www.3gpp.org/technologies/keywords-acronyms/97-lte-advanced">http://www.3gpp.org/technologies/keywords-acronyms/97-lte-advanced</a><br>TS 22.289<br>[R4.1.2-1]<br>[R4.1.2-2]<br>[R4.1.2-3]<br>[R4.1.2-4] |
+| [R-7.2.2-002] | Transferring CCTV archives shall not affect mission critical communication.<br>NOTE: Transferring CCTV archives is not considered to be a mission critical service. | A/T | TS 22.289 | TS 22.289<br>[R4.1.2-1]<br>[R4.1.2-2]<br>[R4.1.2-3]<br>[R4.1.2-4] |
+
+## 7.3 Use Case: Massive Inter-carriage data transfer
+
+### 7.3.1 Description
+
+This use case describes the transfer of CCTV archives inside the train from different storages and through Inter-carriage links into the FRMCS node providing the uplink connection with the ground system.
+
+### 7.3.2 Pre-conditions
+
+- Mobile communication infrastructure between train and ground system enables transfer of CCTV archives from train to the ground system while the train stops at the stations.
+- The ground system supports sufficient archiving system for the transferred recordings.
+
+- The Inter-carriage links support the same throughput speed as the FRMCS node providing the uplink.
+
+### 7.3.3 Service flows
+
+Mobile communication system in train establishes connection between carriages of the train dedicated for the transfer of CCTV archives to a central node in the train from which the uplink to the ground system will take place.
+
+### 7.3.4 Post-conditions
+
+Recording capacity is freed up in the carriages.
+
+### 7.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------|
+| [R-7.3-001] | The FRMCS System shall facilitate the onboard CCTV communication between carriages of a train, to collect CCTV content at one place on the train for transfer to the ground system. | A/T | 22.289 | CR 22.289<br>R4.3.1-001-003 |
+| [R-7.3-002] | The onboard CCTV communication between carriages of a train shall not impact mission critical communication<br>NOTE: Transferring CCTV archives is not considered to be a mission critical service. | A/T | 22.289 | CR 22.289<br>R4.3.1-001-003 |
+
+## 7.4 Void
+
+## 7.5 On-train outgoing voice communication from train staff towards a ground user related use cases
+
+### 7.5.1 Introduction
+
+In this chapter the use cases related to on-train outgoing voice communication from train staff towards a ground user e.g. controller are defined. The following use cases are defined:
+
+- Initiation of on-train outgoing voice communication by the train staff
+- Termination of on-train outgoing voice communication by the train staff
+- Service interworking with GSM-R
+
+## 7.5.2 Use case: Initiation of on-train outgoing voice communication from train staff
+
+### 7.5.2.1 Description
+
+FRMCS User at the train shall be able to initiate a voice communication to any FRMCS User (s) at the ground.
+
+### 7.5.2.2 Pre-conditions
+
+The FRMCS User, member of the train staff, is authorised to initiate the voice communication.
+
+The FRMCS System is able to retrieve location information of the FRMCS User at the train to address the appropriate FRMCS Users at the ground.
+
+### 7.5.2.3 Service flows
+
+The FRMCS User at the train (member of the train staff) initiates the voice communication to an FRMCS User at the ground (one or multiple). This kind of voice communication requires the QoS category of NON-CRITICAL VOICE (see [QoS]) within the FRMCS system.
+
+The FRMCS System establishes the voice communication among the FRMCS user(s) within a setup time specified as NORMAL (see [QoS]).
+
+The activated identities to the FRMCS User(s) are presented to all FRMCS Users during the entire voice communication.
+
+This kind of communication can become part of the communication arbitration management.
+
+On demand this voice communication can be recorded for post processing purposes.
+
+If two or more than two FRMCS Users are part of the voice communication, multi talker control applies.
+
+### 7.5.2.4 Post-conditions
+
+The FRMCS User at the train is able to communicate to the FRMCS Users at the ground.
+
+### 7.5.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-7.5.2-001] | The FRMCS System shall setup a voice communication between one FRMCS User at the train and one/multiple FRMCS Users on the ground based. The NON-CRITICAL VOICE QoS class shall apply for this kind of communication. | A | 22.179<br>22.280 | TS 22.179 Floor Control clause 6.2.3.2 Req #1,<br>TS 22.280 clause 5.1 req # 2 |
+| [R-7.5.2-002] | The location information of the FRMCS User at the train shall be used to locate and address the responsible FRMCS Users on the ground. | A | 22.280 | R-5.6.2.1.2-002<br>R-5.6.2.4.1-004<br>R-6.8.8.4.1-006 (Using User regroup, not 5.6.2.4.1-005)<br>R-6.6.4.2-002b<br>R-6.6.4.1-XXX User regroup |
+| [R-7.5.2-003] | The FRMCS System shall verify if the FRMCS User at the train as well as the FRMCS Users on the ground are authorised to establish the communication. | A | 22.280 | 5.1.x |
+| [R-7.5.2-004] | The FRMCS System shall establish the voice communication between the FRMCS User at the train and the FRMCS Users on the ground within a setup time specified as NORMAL (see [QoS]). | A | N/A | See section 12.10 below |
+| [R-7.5.2-005] | The FRMCS System shall provide for on-train to one/multiple ground FRMCS User: <ul style="list-style-type: none"> <li>- arbitration information to the FRMCS User</li> <li>- communication recording</li> <li>- Multi-Talker Control.</li> </ul> | A | 22.280 | Arbitration:<br>[R-5.4.2-004]<br>[R-5.4.2-004A]<br>[R-5.4.2-004B]<br>Multiuser talker control, recording: See relevant section |
+
+## 7.5.3 Use case: Termination of on-train outgoing voice communication from train staff
+
+### 7.5.3.1 Description
+
+The FRMCS User that is member of train staff shall be able to terminate the voice communication towards the FRMCS Users on the ground.
+
+The FRMCS User on the ground shall be able to put on hold, leave or terminate the on-train voice communication.
+
+### 7.5.3.2 Pre-conditions
+
+The on-train outgoing voice communication is ongoing.
+
+### 7.5.3.3 Service flows
+
+#### **Member of train staff termination**
+
+The FRMCS User that is member of the train staff terminates the voice communication.
+
+The FRMCS system releases the voice communication.
+
+#### **Communication on hold**
+
+A FRMCS User on the ground put the voice communication on hold.
+
+The communication remains active in the FRMCS system and the FRMCS User on the ground user is able to re-join the communication.
+
+#### **Leaving the communication**
+
+The FRMCS User at the ground user is able to leave the voice communication if more than one FRMCS User at the ground is part of the voice communication.
+
+#### **Communication Termination by the ground FRMCS User**
+
+Any FRMCS User on the ground is able to terminate the voice communication between train staff and the ground user.
+
+The FRMCS system releases the voice communication. All involved FRMCS Users are informed about.
+
+### 7.5.3.4 Post-conditions
+
+The on-train outgoing voice communication is terminated.
+
+### 7.5.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-7.5.3-001] | The FRMCS System shall allow an authorised FRMCS User at the train that is part of the On-train outgoing voice communication, to terminate the voice communication. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior" |
+| [R-7.5.3-002] | Based on the On-train outgoing voice communication termination request, the FRMCS System shall release the voice communication. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior" |
+| [R-7.5.3-003] | If authorised, a FRMCS User on the ground shall be able to put the train staff to ground user voice communication on hold if more than one ground FRMCS Users are part of the voice communication. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior" |
+| [R-7.5.3-004] | After the FRMCS User has put the voice communication on hold, the communication shall remain active and the FRMCS User on the ground shall be able to re-join the communication. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior" |
+| [R-7.5.3-005] | If more than one FRMCS Users on the ground participate to an On-train outgoing voice communication from train staff towards a ground user, the FRMCS User on the ground user shall be able to withdraw from the communication with ability to re-join. The remaining FRMCS Users shall be informed about the withdrawn FRMCS User. | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior" |
+| [R-7.5.3-006] | If authorised, the FRMCS User at the train or the FRMCS Users on the ground shall be able to terminate the train staff to ground user voice communication. The FRMCS system shall inform the involved FRMCS Users | A | 22.280 | 6.4.4 002; 6.4.5 001; 5.1.5 003-008<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior" |
+
+| | | | | |
+|--|-----------------------------------------|--|--|--|
+| | about the release of the communication. | | | |
+|--|-----------------------------------------|--|--|--|
+
+## 7.5.4 Use case: Service interworking with GSM-R
+
+### 7.5.4.1 Description
+
+For coexistence between FRMCS System and the legacy GSM-R communication system, service interworking among the systems is required.
+
+Depending on the scenario a ground FRMCS User can be attached to the FRMCS system, to the GSM-R system or both. The FRMCS User at the train can be attached either to the GSM-R system or to the FRMCS system.
+
+This use case only applies to an FRMCS Equipment that supports FRMCS System and GSM-R.
+
+### 7.5.4.2 Pre-conditions
+
+The FRMCS User is either attached to the FRMCS System or to GSM-R.
+
+### 7.5.4.3 Service flows
+
+#### **FRMCS User (Train staff) attached to GSM-R**
+
+When the FRMCS User (member of the train staff) is attached to the GSM-R system and is initiating voice communication to FRMCS Users on the ground, the GSM-R system will route the voice communication to the FRMCS User on the ground accordingly.
+
+If the FRMCS User on the ground is registered to the FRMCS System, the GSM-R system establishes the communication considering the appropriate addressing scheme.
+
+#### **FRMCS User (Train staff) attached to FRMCS System**
+
+When the FRMCS User (member of train staff) is active in the FRMCS system and is initiating voice communication to FRMCS Users on the ground, the FRMCS system will establish the communication considering the appropriate addressing schemes applicable for FRMCS System as well as to GSM-R accordingly.
+
+#### **FRMCS User (Train staff) relocates between GSM-R and FRMCS System/FRMCS System and GSM-R**
+
+When the FRMCS User (train staff) relocates between GSM-R - FRMCS System or vice versa the communication service requires continuation. An interruption of the applicable bearer service is acceptable.
+
+### 7.5.4.4 Post-conditions
+
+The communication continues if the FRMCS User at the train relocates between GSM-R and FRMCS System or vice versa.
+
+### 7.5.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------|
+| [R-7.5.4-001] | The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from the legacy GSM-R system. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-7.5.4-002] | The FRMCS System shall provide the necessary means to allow FRMCS Users to set up On-train outgoing voice communication including users registered to the GSM-R system. | A | 22.179 | Covered in 6.18.4.2 |
+| [R-7.5.4-003] | <p>When the FRMCS User has to relocate between FRMCS System and GSM-R or vice a versa, the voice communication service shall continue. The interruption of the bearer service associated with the relocating FRMCS User is acceptable.</p> <p>Note : This requirement applies to FRMCS Equipment that contains FRMCS UE and GSM-R UE capabilities.</p> | A | N/A | Call has to be re-established by UE. This is UE function outside scope of 3GPP |
+
+## 7.6 Real-time video communication (video conferencing) related use cases
+
+### 7.6.1 Introduction
+
+A real-time video communication (video conferencing) can be used to support railway operations, such as maintenance staff when investigating infrastructure or vehicles components where help is needed from other staff or during testing of infrastructure or vehicles.
+
+Real-time video communication (video conferencing) is supported by the FRMCS System. That encompasses user-to-user as well as multiuser video communication, including audio, and is applicable to On-network only.
+
+In this chapter the use cases related to real-time video communication (video conferencing) are described. The following use cases are identified:
+
+- An FRMCS User initiates a video conference
+- An FRMCS User leaves and re-joins a video conference
+- An FRMCS User terminates a video conference
+- An FRMCS User changes from a video conference to a voice-only conference
+- An FRMCS User changes from a voice-only conference to a video conference
+
+- An FRMCS User joins an ongoing video conference
+
+## 7.6.2 Use case: Initiation of video conference
+
+### 7.6.2.1 Description
+
+An FRMCS User is able to set up a video conference to other FRMCS User(s). This encompasses transmission of synchronized video and audio information under conditions.
+
+### 7.6.2.2 Pre-conditions
+
+The initiating FRMCS User is authorised to initiate a video conference.
+
+The receiving FRMCS User(s) is(are) authorised to use video conference.
+
+### 7.6.2.3 Service flows
+
+An authorised FRMCS User initiates a video conference that corresponds to the application category VIDEO (see QoS chapter).
+
+The FRMCS System determines the FRMCS User(s) to be included in the communication, based on:
+
+- Selection by the initiating FRMCS User, or
+- Location of all FRMCS Users, and/or
+- Functional identity of all FRMCS Users, and/or
+- System configuration.
+
+The FRMCS system establishes the bearer service(s) required for the video conference within a setup time applicable to application category VIDEO (see QoS chapter). FRMCS User(s) are using their registered functional identities and provide furthermore their location.
+
+The FRMCS System assigns a certain priority of the video conference.
+
+The receiving FRMCS User(s) is able to accept, reject, or ignore the incoming video conference.
+
+The involved FRMCS Users are able to select which video content is to be presented (at both sender and receiver sides).
+
+The FRMCS System records the communication of the initiating and receiving FRMCS Users.
+
+### 7.6.2.4 Post-conditions
+
+Real-time video (synchronized video and audio information) can be transmitted and received among authorised FRMCS Users involved in the ongoing video conference.
+
+### 7.6.2.5 Potential requirements and gap analysis
+
+This use case is not in the scope of current normative work.
+
+A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
+
+It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases.
+
+## 7.6.3 Use case: Leave and re-join a video conference
+
+### 7.6.3.1 Description
+
+An FRMCS User is able to leave and re-join an ongoing video conference under conditions.
+
+### 7.6.3.2 Pre-conditions
+
+The video conference is ongoing.
+
+The FRMCS User is authorised to leave and re-join an ongoing video conference.
+
+### 7.6.3.3 Service flows
+
+The authorised FRMCS User is able to leave the video conference while receiving a new incoming communication or initiating another outgoing communication. The other involved FRMCS User(s) are informed and can continue the ongoing video conference if the number of remaining participants is sufficient.
+
+The authorised FRMCS Users is then able to re-join the video conference.
+
+The ongoing video conference is terminated if the number of remaining participants is not sufficient.
+
+### 7.6.3.4 Post-conditions
+
+The authorised FRMCS User has left the ongoing video conference.
+
+### 7.6.3.5 Potential requirements and gap analysis
+
+This use case is not in the scope of current normative work.
+
+A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
+
+It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases.
+
+## 7.6.4 Void
+
+## 7.6.5 Use case: Termination of a video conference
+
+### 7.6.5.1 Description
+
+Any authorised FRMCS User is able to terminate an ongoing video conference.
+
+### 7.6.5.2 Pre-conditions
+
+The video conference is ongoing.
+
+The FRMCS User is authorised to terminate an ongoing video conference.
+
+### 7.6.5.3 Service flows
+
+The authorised FRMCS User is able to terminate the video conference. The involved FRMCS User(s) are informed and the video conference is terminated.
+
+### 7.6.5.4 Post-conditions
+
+The authorised FRMCS User has terminated the ongoing video conference.
+
+### 7.6.5.5 Potential requirements and gap analysis
+
+This use case is not in the scope of current normative work.
+
+A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
+
+It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases.
+
+## 7.6.6 Use case: Changes from a video conference to a voice-only conference
+
+### 7.6.6.1 Description
+
+Any authorised FRMCS User is able to change from a video conference to a voice-only conference only.
+
+### 7.6.6.2 Pre-conditions
+
+There is an ongoing video conference.
+
+The initiating FRMCS User is authorised to change from a video conference to a voice-only conference.
+
+The initiating FRMCS User is authorised to initiate voice-only conference.
+
+### 7.6.6.3 Service flows
+
+An authorised FRMCS User initiates the change from a video conference to a voice-only conference.
+
+The FRMCS System determines if the change can be proceeded, based on:
+
+- Authorisation from initiating FRMCS User, and/or
+- Authorisation from receiving FRMCS User(s), and/or
+- System configuration.
+
+The FRMCS system establishes the bearer service required for the voice-only conference within a setup time applicable to application category CRITICAL VOICE or VOICE (see QoS chapter). FRMCS User(s) are using their registered functional identities and provide furthermore their location.
+
+The FRMCS System assigns a certain priority of the voice-only conference.
+
+The receiving FRMCS User(s) shall be able to accept, reject or ignore the change to a voice-only conference.
+
+The bearer service required for the video conference is maintained under conditions (e.g. timer) to allow FRMCS Users to return to the video conference.
+
+The receiving FRMCS User(s) are notified that a change from video conference to voice-only conference has been initiated by the authorised FRMCS User.
+
+The FRMCS System records the communication of the initiating and receiving FRMCS Users.
+
+#### 7.6.6.4 Post-conditions
+
+After the change from video conference to voice-only conference, the FRMCS Users are not able to transmit and receive video anymore.
+
+#### 7.6.6.5 Potential requirements and gap analysis
+
+This use case is not in the scope of current normative work.
+
+A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
+
+It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases.
+
+### 7.6.7 Use case: Change from a voice-only conference to a video conference
+
+#### 7.6.7.1 Description
+
+Any authorised FRMCS User is able to change from a voice-only conference to a video conference.
+
+#### 7.6.7.2 Pre-conditions
+
+There is an ongoing voice-only conference.
+
+The initiating FRMCS User is authorised to change from a voice-only conference to a video conference.
+
+The initiating FRMCS User is authorised to initiate a video conference.
+
+#### 7.6.7.3 Service flows
+
+An authorised FRMCS User initiates the change from a voice-only conference to a video conference.
+
+The FRMCS System determines if the change can be proceeded, based on:
+
+- Authorisation from initiating FRMCS User, and/or
+- Authorisation from receiving FRMCS User(s), and/or
+- System configuration.
+
+The FRMCS system establishes the bearer service required for the video conference within a setup time applicable to application category VIDEO (see QoS chapter). FRMCS User(s) are using their registered functional identities and provide furthermore their location.
+
+The FRMCS System assigns a certain priority of the video conference.
+
+The receiving FRMCS User(s) is able to accept, reject or ignore the change to a video conference.
+
+The bearer service required for the voice-only conference is maintained under conditions (e.g. timer) to allow FRMCS Users to return to the voice-only conference.
+
+The receiving FRMCS User(s) are notified that a change has been initiated by the authorised FRMCS User.
+
+The FRMCS System records the communication of the initiating and receiving FRMCS Users.
+
+#### 7.6.7.4 Post-conditions
+
+After the change from voice-only conference to video conference, the FRMCS Users are able to transmit and receive video and audio.
+
+#### 7.6.7.5 Potential requirements and gap analysis
+
+This use case is not in the scope of current normative work.
+
+A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
+
+It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases.
+
+### 7.6.8 Use case: Join an ongoing video conference
+
+#### 7.6.8.1 Description
+
+Any authorised FRMCS User is able to join an ongoing video conference under conditions.
+
+#### 7.6.8.2 Pre-conditions
+
+There is an ongoing video conference.
+
+An FRMCS User is authorised to join an ongoing video conference.
+
+#### 7.6.8.3 Service flows
+
+The FRMCS System determines if the authorised FRMCS User can join an ongoing video conference, based on:
+
+- Selection/Invitation by the initiating FRMCS User of the ongoing video conference, or
+- Location of all FRMCS Users, and/or
+- Functional identity of all FRMCS Users, and/or
+- System configuration.
+
+The authorised FRMCS User joins an ongoing video conference.
+
+The involved FRMCS User(s) are notified that an FRMCS User has joined the ongoing video conference. FRMCS User(s) are using their registered functional identities and provide furthermore their location.
+
+#### 7.6.8.4 Post-conditions
+
+The authorised FRMCS User has joined the ongoing video conference. All involved FRMCS Users of the ongoing video conference are able to transmit and receive video and audio.
+
+### 7.6.8.5 Potential requirements and gap analysis
+
+This use case is not in the scope of current normative work.
+
+A decision has to be taken to consider a fully OTT solution, or if MCVideo current group communications functionality are sufficient, or if MMTel conference could be used, or if we need a new technical study on MCVideo conferencing.
+
+It is recommended that MCVideo Service (MCVideo group communications as stated in TS 22.281) or MCData Service using IP connectivity (MCData group communications as stated in TS 22.282) and Functional Alias to reach MCX Users as 3GPP building blocks to support Real-time video communication (video conferencing) related use cases.
+
+---
+
+## 8 Business communication applications related use cases
+
+### 8.1 Multimedia applications related use cases
+
+#### 8.1.1 Introduction
+
+In this chapter, the following use cases related to Multimedia applications are defined:
+
+- Live streaming of multimedia
+- Bulk transfer of multimedia data bases from ground to train
+
+### 8.2 Use Case: Live streaming of multimedia
+
+#### 8.2.1 Description
+
+This use case describes the live streaming of multimedia content from ground to train.
+
+#### 8.2.2 Pre-conditions
+
+- FRMCS User equipment is registered into the FRMCS System.
+- Passengers can access live streaming services through the FRMCS System in the train.
+
+#### 8.2.3 Service flows
+
+1. FRMCS System provides data communication for the live streaming services.
+2. FRMCS User equipment requests data communication for the live streaming services from the FRMCS System.
+3. FRMCS System allocates requested data communication for the FRMCS User equipment.
+4. FRMCS User equipment allocates the communication to the passengers.
+
+#### 8.2.4 Post-conditions
+
+FRMCS User equipment deregisters from the FRMCS System upon the reception of live streaming is ceased.
+
+## 8.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------|
+| [R-8.2.5-001] | The FRMCS System SHALL enable bandwidth for the live streaming inside the train through the FRMCS System. | | 22.261 | Live streaming service covered by 22.261 Table 7.1-1. |
+| [R-8.2.5-002] | The FRMCS User equipment SHALL be able to balance the bandwidth between the passengers. | | 22.261 | Live streaming service covered by 22.261 Table 7.1-1. |
+
+NOTE: Live streaming of multimedia from ground to train is not considered to be a mission critical service.
+
+## 8.3 Use Case: Bulk transfer of multimedia from ground to train
+
+### 8.3.1 Description
+
+This use case describes the transfer of multimedia databases from ground to train. The multimedia may contain movies, TV shows, cached webpages etc.
+
+Figure 1 illustrates an example calculation of upload time of movies with different bitrates, when 1-100 movies are uploaded, and the upload speed is 1 Gbps.
+
+
+
+| Number of movies | 1 Mbps | 2 Mbps | 3 Mbps | 4 Mbps | 5 Mbps |
+|------------------|--------|--------|--------|--------|--------|
+| 1 | 0.6 | 1.2 | 1.8 | 2.4 | 3.0 |
+| 2 | 1.2 | 2.4 | 3.6 | 4.8 | 6.0 |
+| 3 | 1.8 | 3.6 | 5.4 | 7.2 | 9.0 |
+| 4 | 2.4 | 4.8 | 7.2 | 9.6 | 12.0 |
+| 5 | 3.0 | 6.0 | 9.0 | 12.0 | 15.0 |
+| 6 | 3.6 | 7.2 | 10.8 | 14.4 | 18.0 |
+| 7 | 4.2 | 8.4 | 12.6 | 16.8 | 21.0 |
+| 8 | 4.8 | 9.6 | 14.4 | 19.2 | 24.0 |
+| 9 | 5.4 | 10.8 | 16.2 | 21.6 | 27.0 |
+| 10 | 6.0 | 12.0 | 18.0 | 24.0 | 30.0 |
+| 20 | 12.0 | 24.0 | 36.0 | 48.0 | 60.0 |
+| 30 | 18.0 | 36.0 | 54.0 | 72.0 | 90.0 |
+| 40 | 24.0 | 48.0 | 72.0 | 96.0 | 120.0 |
+| 50 | 30.0 | 60.0 | 90.0 | 120.0 | 150.0 |
+| 100 | 60.0 | 120.0 | 180.0 | 240.0 | 300.0 |
+
+Bar chart titled 'Upload time with 1 Gbps upload rate' showing upload time in minutes for 1 to 100 movies at bitrates of 1, 2, 3, 4, and 5 Mbps. The x-axis represents the number of movies (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 100) and the y-axis represents time in minutes (0 to 60). The legend indicates five bitrates: 1 Mbps (blue), 2 Mbps (red), 3 Mbps (green), 4 Mbps (purple), and 5 Mbps (cyan). The chart shows that upload time increases linearly with the number of movies and is significantly higher for higher bitrates. For example, at 100 movies, the upload times are approximately 12, 24, 36, 48, and 60 minutes for 1, 2, 3, 4, and 5 Mbps respectively.
+
+Figure 8.3.1-1. An example calculation of upload time of movies with different bitrates and 1 Gbps upload speed.
+
+### 8.3.2 Pre-conditions
+
+FRMCS System enables transfer of multimedia databases from ground to train while the train stops at the stations or is at the depot.
+
+### 8.3.3 Service flows
+
+1. Train has stopped at the station or at the depot and
+2. FRMCS User equipment responsible for the bandwidth allocation for the transfer of on-board multimedia database is registered into the FRMCS System
+3. FRMCS User equipment asks from FRMCS System to allocate needed bandwidth for the transfer of the multimedia database upon request by the content server.
+
+### 8.3.4 Post-conditions
+
+FRMCS User equipment responsible for the bandwidth allocation for the transfer of on-board multimedia database de-registers from the FRMCS System.
+
+### 8.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------|
+| [R-8.3.5-001] | For the sufficient transfer of large sized multimedia databases, the FRMCS System SHALL support throughput speed minimum of 1 Gbps. | | 22.289<br>22.261 | TS 22.289 [R4.2.2-2] s |
+
+NOTE: Bulk transfer of multimedia from ground to train is not considered to be a mission critical service.
+
+---
+
+## 9 Critical support applications related use cases
+
+### 9.1 Overview
+
+Critical applications are essential for train movements, safety, shunting, presence, trackside maintenance, legal aspects such as emergency communications, etc.
+
+### 9.2 Assured voice communication (AVC)
+
+#### 9.2.1 Introduction
+
+In this chapter the use cases related to the function of assured voice communication are defined. Assured Voice Communication (AVC) shall provide an indication to FRMCS Users as soon as a voice communication link is interrupted. It is invoked on an existing voice communication between two or more FRMCS Users.
+
+The following use cases are defined:
+
+- Invocation of AVC
+- Stopping AVC
+- Degradation of a communication link (e.g. bad quality of the signal quality or interruption of a communication link)
+
+- Extension of AVC
+
+## 9.2.2 Use case: Invocation of Assured Voice Communication
+
+### 9.2.2.1 Description
+
+This use case describes the invocation of Assured Voice Communication.
+
+### 9.2.2.2 Pre-conditions
+
+A FRMCS User is part of a voice communication with one or more FRMCS Users for which Assured Voice Communication can be invoked either automatically or manually.
+
+### 9.2.2.3 Service flows
+
+#### Automatic Invocation
+
+Upon establishment of a voice communication for which automatic AVC is activated, AVC will be invoked by the FRMCS System.
+
+The involved FRMCS Users are informed about the successful activation of AVC.
+
+#### Manual Invocation
+
+The user invokes AVC in the FRMCS System.
+
+The involved FRMCS Users are informed about the successful activation of AVC.
+
+### 9.2.2.4 Post-conditions
+
+The voice communication links of all FRMCS Users involved in the communication are supervised.
+
+### 9.2.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.2.2-001] | Upon establishment of a voice communication for which automatic AVC is activated, AVC shall be invoked by the FRMCS System. | A | 22.280 | R-6.2.1-001<br>But the AVC remains as OTT application while 3GPP building block provides the enabling framework." |
+| [R-9.2.2-002] | If entitled, a FRMCS User shall be able to invoke AVC manually. | A | 22.280 | MCX Services take the approach that all communication are acknowledged and the MCPTT User is given the choice to proceed without acknowledgement 22.280<br>R-6.2.1-010 |
+
+## 9.2.3 Use case: Stopping Assured Voice Communication
+
+### 9.2.3.1 Description
+
+This use case describes the deactivation of the communication link supervision.
+
+### 9.2.3.2 Pre-conditions
+
+A FRMCS User is part of a voice communication with one or more FRMCS Users for which Assured Voice Communication was invoked.
+
+### 9.2.3.3 Service flows
+
+#### Automatic stopping
+
+If the ongoing voice communication is terminated by one of the involved users, the Assured Voice Communication is stopped.
+
+The involved FRMCS Users are informed about the successful stop of AVC.
+
+#### Manual stopping
+
+The FRMCS User who has previously manually invoked AVC may stop AVC.
+
+The involved FRMCS Users are informed about the successful stop of AVC.
+
+### 9.2.3.4 Post-conditions
+
+#### Automatic stopping
+
+The FRMCS User is no longer part of a voice communication with one or more FRMCS Users.
+
+#### Manual stopping
+
+The FRMCS User is still part of a voice communication with one or more FRMCS Users.
+
+### 9.2.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.2.3-001] | If the voice communication is terminated stopping of AVC shall be done by the FRMCS System automatically. | A | N/A | Implicit as done on burst basis |
+| [R-9.2.3-002] | Only the FRMCS User who requested the end-to-end supervision shall be able to stop AVC. | A | 22.280 | Communication is acknowledged on a per talk burst basis so stopping that ack processing can be done by<br>R-6.2.1-008<br>R-6.2.1-010" |
+
+## 9.2.4 Use case: Degradation of a communication link
+
+### 9.2.4.1 Description
+
+Alternative 1: The FRMCS System provides a so called negative notification to the FRMCS Users as soon as voice communication link is interrupted.
+
+Alternative 2: A positive notification will be given by the FRMCS System as long as the voice communication link is unaffected.
+
+#### 9.2.4.2 Pre-conditions
+
+A FRMCS User is part of a voice communication with one or more FRMCS Users.
+
+AVC is invoked on all links of the voice communication.
+
+#### 9.2.4.3 Service flows
+
+##### Positive Notification
+
+The FRMCS System continuously checks whether the voice communication links are unaffected (e.g. bad quality of the signal quality or interruption of a communication link).
+
+The FRMCS System indicates to all FRMCS Users involved in the voice communication service is working properly e.g. by a periodic audio signal.
+
+If an interruption of at least one of the communication links is detected, the positive notification is immediately stopped.
+
+If AVC itself fails, the positive notification shall be stopped immediately.
+
+Active speech transmission shall suppress the positive notification to all FRMCS Users involved.
+
+Optionally all FRMCS Users have to confirm their availability periodically (e.g. by pressing a button or by talking). If this confirmation is not received, AVC shall be stopped immediately.
+
+A FRMCS User terminating his participation in the voice communication shall immediately stop AVC.
+
+When AVC is stopped the ongoing voice communication is continued. Assured Voice Communication may be reinvoked for the remaining FRMCS Users of the ongoing voice communication.
+
+##### Negative Notification
+
+The FRMCS System continuously checks whether the voice communication links are unaffected (e.g. bad quality of the signal quality or interruption of a communication link).
+
+If a degradation of a voice communication link is detected the FRMCS System warns all involved FRMCS Users, e.g. by generating a warning audio signal. If possible, the FRMCS User with the interrupted communication link shall also be warned.
+
+If AVC itself fails, the negative notification shall be given immediately e.g. by a warning tone.
+
+A FRMCS User terminating his participation in the voice communication shall stop AVC and a negative notification shall be given immediately e.g. by a warning tone.
+
+Optionally all FRMCS Users have to confirm their availability periodically (e.g. by pressing a button or by talking). If this confirmation is not received, AVC shall be stopped and a negative notification shall be given immediately e.g. by a warning tone.
+
+When AVC is stopped the ongoing voice communication is continued. Assured Voice Communication may be reinvoked for the remaining FRMCS Users of the ongoing voice communication.
+
+#### 9.2.4.4 Post-conditions
+
+The voice communication between the remaining FRMCS Users continues.
+
+#### 9.2.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.2.4-001] | The FRMCS System shall be able to continuously supervise the voice communication links to all involved FRMCS Users. | A | 22.280<br>22.179 | Result of this supervision is provided by<br>22.179 6.2.1-001-010<br>22.280 5.20.2-001 |
+| [R-9.2.4-001a] | The FRMCS System shall be able to provide indications to AVC on the signal quality of the link/connection to take decision to maintain a reliable communication path. | T | 22.261 | Covered by QoS monitoring. |
+| [R-9.2.4-002] | If a degradation of a voice communication link is detected, the remaining FRMCS Users shall be informed. The ongoing voice communication among the remaining FRMCS Users shall continue.<br>A FRMCS User quitting the communication shall cause the AVC to stop. | A | 22.280<br>22.179 | Done by<br>22.179 6.2.1-001-010<br>22.280 5.20.2-001<br>Supervision is done on a per talk burst basis, if user drops out or de-affiliates during the burst 22.280 5.20.2-001 takes effect, if user drop out between the bursts this will be noticed during the ack process as described in 22.179 6.2.1-001-010 |
+| [R-9.2.4-003] | The FRMCS System shall be able to inform the FRMCS Users of an interrupted voice communication link by either positive or negative notification. | A | 22.179 | R-6.2.1-008<br>R-6.2.1-009 |
+| [R-9.2.4-004] | In case of positive notification all FRMCS Users shall receive a periodic audio signal while no voice communication is ongoing. Active speech transmission shall suppress the positive notification. | A | 22.280<br>22.179" | Information conveyed to UE by<br>22.179 6.2.1-001-010<br>22.280 5.20.2-001R-6.2.1-002<br>how this information is presented to the user is user I/F design, due to the talk burst nature of the communication it does not make sense while not talking to have that indication<br>It rather should be notified at the set-up that certain users did not acknowledge see<br>22.179 6.2.1-010 |
+| [R-9.2.4-005] | In case of negative notification all FRMCS Users shall receive an audio signal when an interrupted voice communication link is detected, the AVC has failed or a FRMCS terminated his participation in the voice communication. | A | 22.280<br>22.179" | Information conveyed to UE by<br>22.179 6.2.1-001-010<br>22.280 5.20.2-001R-6.2.1-002<br>how this information is presented to the user is user I/F design, due to the talk burst nature of the communication it does not make sense while not talking to have that indication<br>It rather should be notified at the set-up that certain users did not acknowledge see<br>22.179 6.2.1-010a |
+| [R-9.2.4-006] | Negative notification shall be | A | 22.280 | Information conveyed to UE |
+
+| | | | | |
+|--|----------------------------------------------------------------------------------------|--|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | stopped after acknowledgement by all remaining FRMCS Users in the voice communication. | | 22.179" | by<br>22.179 6.2.1-001-010<br>22.280 5.20.2-001R-6.2.1-002<br>how this information is presented to the user is user I/F design, due to the talk burst nature of the communication it does not make sense while not talking to have that indication It rather should be notified at the set-up that certain users did not acknowledge see 22.179 6.2.1-010a |
+|--|----------------------------------------------------------------------------------------|--|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+## 9.2.5 Use case: Extension of Assured Voice Communication
+
+### 9.2.5.1 Description
+
+The assured voice communication application shall provide the ability to extend an assured voice communication to a user who has joined an ongoing communication.
+
+### 9.2.5.2 Pre-conditions
+
+The use of Assured Voice Communication is activated for the ongoing voice communication.
+
+### 9.2.5.3 Service flows
+
+If a user joins an ongoing assured voice communication, the initiator of the assured voice communication is informed. The joining user is not supervised yet but is part of the communication.
+
+The initiator shall have the option to extend the assured voice communication to this new user.
+
+### 9.2.5.4 Post-conditions
+
+If the assured voice communication is extended, the new user is supervised by the assured voice communication.
+
+If the assured voice communication is not extended to the new user, the new user is not supervised by the assured voice communication but remains part of the existing ongoing communication.
+
+### 9.2.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.2.5-001] | The initiator shall be able to extend the AVC to a new FRMCS User in the communication. | A | 22.280 | This is done automatically due to the talk burst nature and the Automatic user regrouping in 22.280 6.6.4.2.<br>Question is whether this always makes sense if the group membership changes frequently from talk burst to talk burst<br>For this reason, a requirement is added allowing to exclude such automatic user regrouping groups from the ack mechanism in general. |
+
+## 9.3 Functional identities and role management
+
+### 9.3.1 Introduction
+
+In this chapter the use cases related to functional identities and role management are defined:
+
+- Registration to a functional identity
+- Deregistration of a functional identity
+- FRMCS User changing functional identity
+- User log-in to the system
+- User log-out from the system
+- Presentation of identities
+- Interrogation of identities within a certain context
+
+Examples of Role management, like functional identities, FRMCS Equipment Identities, etc. in the railway environment are covered by annex A.
+
+### 9.3.2 General pre-conditions
+
+In order to fully understand the uses cases in this chapter, Figure 9.3.2-1 illustrates the different steps required to complete the registration process.
+
+
+
+```
+
+graph TD
+ Start[UE Power on] --> AppStart[Start FRMCS application]
+ AppStart --> EquipLogin[FRMCS Equipment login]
+ EquipLogin --> InitEquip[Initialize Equipment Type]
+
+ InitEquip --> RegFuncEquip[Register to functional identity related to an equipment]
+ RegFuncEquip --> FuncAddedEquip[Functional identity added]
+ FuncAddedEquip --> UserLogin[User login dialog]
+
+ InitEquip --> UserLogin
+
+ UserLogin --> FRMCSUser[FRMCS User (FRMCS User identity)]
+ FRMCSUser --> RegFuncUser[Register to functional identity]
+ RegFuncUser --> FuncAddedUser[Functional identity added]
+ FuncAddedUser --> RegComp[Registration Completed]
+
+ RegComp --> InitEquip
+
+ subgraph EquipmentTypes [Equipment Types]
+ TypeA[Type a]
+ TypeB[Type b]
+ TypeC[Type c]
+ end
+
+ InitEquip --> TypeA
+ InitEquip --> TypeB
+ InitEquip --> TypeC
+
+```
+
+A complex flowchart illustrating Role management in FRMCS. It shows a sequence of steps from UE Power on, through equipment initialization, registration of functional identities, and user login. The flow includes decision points and loops for different equipment types and user scenarios.
+
+**Figure 9.3.2-1: Example of Role management**
+
+In this definition, it is needed to make a distinction between different types of FRMCS Equipment. The following are, as a principle, defined:
+
+- a) FRMCS Equipment without MMI, without the possibility to be addressed via a functional identity related to the equipment (e.g. sensor in the track or simple modem operation)
+- b) FRMCS Equipment that can be registered to a functional identity related to the equipment (e.g. maintenance log collecting device connected to a power station) but without other FRMCS User login
+
+- c) FRMCS Equipment that can be registered to a functional identity and that allows a FRMCS User to login and register to functional identities related to the user (e.g. cab radio)
+- d) FRMCS Equipment that cannot register to a functional identity, but that allows a FRMS User to login and to register to functional identities related to the user (e.g. a generic handheld device)
+
+Steps:
+
+1. UE-Power on: The UE has started up and is attached to the FRMCS network on telecoms level. The UE is reachable via its subscriber identity address.
+2. Start FRMCS Application: On the UE the FRMCS Application start up and is ready for use.
+3. FRMCS Equipment login: The FRMCS Application is logging in into the FRMCS System and the FRMCS Equipment becomes known to the FRMCS System.
+4. Initialise FRMCS Equipment type: the type of FRMCS Equipment used is identified.
+
+At this stage of the user flow four different routes can be followed, based on the determined FRMCS Equipment type of the FRMCS Equipment.
+
+Type a) “sensor”:
+
+- No action required. The FRMCS Equipment is now reachable via its subscriber identity address.
+
+After this step the process of registration is completed.
+
+Type b) “Announcement System”:
+
+- Register to a functional identity: the FRMCS Equipment will request for a registration on a functional number. This functional number is related to the equipment and identifies the device, like a PA system on a train.
+- Functional identity added: the request for a functional identity is granted by the FRMCS System. The end user device is now reachable via its functional identity.
+
+After this step the process of registration is completed.
+
+Type c) “cab radio”:
+
+- Register to a functional identity: the FRMCS Equipment will request for a registration on a functional identity. This functional identity is related to the FRMCS Equipment and identifies the environment where the equipment is used, like a cab radio in a cabin of a train.
+- Functional identity added: The FRMCS User is now only reachable via all of its functional identities related to the FRMCS Equipment.
+
+Type d) “Handheld”:
+
+Next, for both the types c) and d) the following steps apply:
+
+- User login dialog: the user is presented with a log-in MMI action. The user can now login into the FRMCS System. By successfully logging into the FRMCS System the user becomes a FRMCS User.
+- FRMCS User: The FRMCS User is now reachable via its FRMCS User Identity (and in case c) the functional identity registered by the FRMCS Equipment).
+- Register to a functional identity: the FRMCS User may request for a registration on a functional identity. This functional identity relates to the FRMCS User and identifies the role of the FRMCS User e.g. driver, controller etc. and the environment e.g. train number.
+
+- Functional identity added: The FRMCS User is now reachable via all the functional identities registered to the user (Further, the FRMCS Equipment is reachable via its registered functional identity(ies)).
+
+After this step the process of registration is completed.
+
+Note: Use cases related to power up the UE until complete initialisation of the equipment type are covered in chapter 5.
+
+### 9.3.2.1 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.2-001] | The FRMCS System shall be able to make use of the underlying transport system's subscriber identities. | A | 22.280 | This requirement can be supported by existing MCCore requirements. |
+| [R-9.3.2-002] | The FRMCS System shall support a FRMCS User identity per FRMCS User. | A | 22.280 | This requirement can be supported by existing MCCore requirements. |
+| [R-9.3.2-003] | The FRMCS System shall support functional identities. | A | 22.280 | This requirement is partly covered by MCCore, new and additional types of identities need to be supported. |
+| [R-9.3.2-004] | The UE shall be reachable by its subscriber identity. | A | 22.280 | This requirement can be supported by existing 3GPP requirements. |
+| [R-9.3.2-004a] | The FRMCS system shall be able to inhibit the use of the underlying transport system's subscriber identities for communication | A | 22.280 | Implicit.<br>[R-5.12-002] The MCX Service supports MCX Service User ID + functional alias, independent of subscriber identity assigned by 3GPP operator to UE. |
+| [R-9.3.2-005] | The FRMCS User shall be reachable by its FRMCS User identity. | A | 22.280 | This requirement can be supported by existing MCCore requirements. |
+| [R-9.3.2-006] | The FRMCS User shall be reachable by its functional identity/ies. | A | 22.280 | This requirement is partly covered by MCCore, new and additional types of identities need to be supported. |
+| [R-9.3.2-007] | At the time of initialisation the FRMCS-system shall be able to determine the FRMCS Equipment Type. | A | N/A | Outside scope of 3GPP standardization. |
+
+## 9.3.3 Use case: Registration to a functional identity
+
+### 9.3.3.1 Description
+
+A FRMCS User or the FRMCS Equipment shall be able to register to one or multiple functional identities. A functional identity can therefore be equipment related or user related.
+
+### 9.3.3.2 Pre-conditions
+
+The equipment type is identified.
+
+Functional registration of the user, the user is logged in into the FRMCS System.
+
+### 9.3.3.3 Service flows
+
+#### **Requested functional identity is not in use**
+
+The FRMCS User or the FRMCS-equipment selects the functional identity. The identity can be selected from a list based on the location of the FRMCS User, operational schedules, etc. or the functional identity can be entered manually.
+
+The FRMCS User or the FRMCS-equipment requests the FRMCS System to register the new functional identity.
+
+The FRMCS System informs the FRMCS User or the FRMCS-equipment about the outcome of the registration request.
+
+#### **Requested functional identity that is in use**
+
+The FRMCS User or the FRMCS-equipment selects the functional identity. The identity can be selected from a list based on the location of the FRMCS User, operational schedules, etc. or the functional identity can be entered manually.
+
+The FRMCS User or the FRMCS-equipment requests the FRMCS System to register the new functional identity.
+
+The FRMCS User is or the FRMCS-equipment informed of the functional identity already in use.
+
+The FRMCS User or the FRMCS-equipment shall be able to select from the following options:
+
+- Cancel the registration
+- If the selected functional identity allows take over the functional identity.
+- If the selected functional identity allows register as an additional FRMCS User to this functional identity.
+
+The FRMCS System informs the FRMCS User about the outcome of the registration request.
+
+In the case of taking over a functional identity, the FRMCS System deregisters the other FRMCS User or FRMCS-equipment from this particular functional identity. The deregistered FRMCS User or the FRMCS-equipment gets informed about the deregistration by the FRMCS System.
+
+#### **Registration by the Railway Subsystem of the FRMCS System**
+
+Based on the user identification, operational conditions, like schedules when entering the train, location, time, recent activity etc., the Railway Subsystem shall be able automatically register a FRMCS User or an FRMCS Equipment to a functional identity.
+
+The FRMCS User gets informed about the registration by the FRMCS System.
+
+### 9.3.3.4 Post-conditions
+
+In case of successful registration, the FRMCS User or the FRMCS-equipment can be reached based on the functional identity. The FRMCS User or the FRMCS-equipment can be registered to different functional identities. The FRMCS User or the FRMCS-equipment are also reachable by using the FRMCS Equipment Identity, the FRMCS User Identity (if logged in) and its subscriber identity.
+
+In case of successful registration and based on system configuration, the FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully registered functional identity.
+
+If the FRMCS System has not accepted the registration, the FRMCS User or the FRMCS-equipment cannot be reached on a particular functional identity.
+
+### 9.3.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.3-001] | The FRMCS User or the FRMCS-equipment shall be able to register to a functional identity. | A | TS 22.280 | 5.9a2 |
+| [R-9.3.3-002] | To select from, the FRMCS System shall provide the FRMCS User or the FRMCS-equipment a list of functional identities. The list contains functional identities based on a certain context, like location of the user, operational schedule, etc. The FRMCS User or the FRMCS-equipment shall also be able to perform a registration of an unlisted functional identity. | A | TS 22.280 | .Predefined list of functional identities based on criteria: [R-5.9a-004]<br>.Unlisted functional identity: [R-5.9a-010] |
+| [R-9.3.3-003] | The FRMCS System shall inform the FRMCS User or the FRMCS-equipment of the outcome of the registration request. | A | TS 22.280 | [R-5.9a-025] |
+| [R-9.3.3-004] | In the case the functional identity is already in use, the FRMCS System shall advise the FRMCS User or the FRMCS-equipment about options to <ul style="list-style-type: none"> <li>cancel the registration,</li> <li>take over the functional identity</li> <li>register as an additional identity.</li> </ul> | A | TS 22.280 | Covered.<br>[R-5.9a-007]: sharing FA first (no user selection), then<br>[R-5.9a-008]: take over (with user selection). If take over not selected, registration considered canceled. |
+| [R-9.3.3-005] | The FRMCS System shall be able to register a FRMCS-user or the Railway Subsystem without human intervention. For example, automatic registration can be initiated by: <ul style="list-style-type: none"> <li>user identification</li> <li>operational conditions, like schedules when entering the train (for example by using Near Field Communication, Smart Card etc.)</li> <li>location</li> <li>time</li> <li>recent activity</li> <li>Smart cards or RFID tokens in the vicinity of the UE</li> <li>FRMCS Equipment Type</li> <li>etc.</li> </ul> | A | TS 22.280 | [R-5.9a-015]<br>[R-5.9a-018] |
+| [R-9.3.3-006] | The FRMCS System shall support multiple functional identities per FRMCS User or FRMCS Equipment. | A | TS 22.280 | [R-5.9a-001] |
+| [R-9.3.3-007] | The FRMCS System shall be | A | TS 22.280 | Covered in on-network with |
+
+| | | | | |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|-----------------------------------------------------------------------------------------------------------------|
+| | able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully registered functional identity. | | | affiliation mechanism + automatic information when affiliation information changes in a group ([R-6.4.5-003a]). |
+|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|-----------------------------------------------------------------------------------------------------------------|
+
+### 9.3.4 Use case: Deregistration of a functional identity
+
+#### 9.3.4.1 Description
+
+A FRMCS User or the FRMCS-equipment shall be able to deregister from one or multiple functional identities.
+
+#### 9.3.4.2 Pre-conditions
+
+The FRMCS User or the FRMCS-equipment has at least one functional identity.
+
+#### 9.3.4.3 Service flows
+
+##### **Deregistration functional identity initiated by the FRMCS User**
+
+The FRMCS User or the FRMCS-equipment chooses the functional identities to be deregistered among the list of currently registered functional identities by:
+
+- electing a set of functional identities (the application may select the appropriate set of functional identities automatically)
+- selecting one functional identity
+
+The FRMCS System informs the FRMCS User or the FRMCS-equipment about the outcome of the registration request.
+
+##### **Deregistration by the Railway Subsystem**
+
+Based on certain criteria the FRMCS System deregisters a FRMCS User or the FRMCS-equipment from one or multiple functional identities and informs the FRMCS User or the FRMCS-equipment about the deregistration.
+
+For example, possible criteria are timer, location, operational schedules, another FRMCS User taking over the functional identity.
+
+#### 9.3.4.4 Post-conditions
+
+If the FRMCS System has deregistered the functional identity, the previously registered FRMCS User (s) or FRMCS-equipment are not any longer reachable on this particular functional identity.
+
+If the FRMCS System has deregistered the functional identity and based on system configuration, the FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully deregistered functional identity.
+
+If the FRMCS System was unable to deregister the functional identity, the actually registered FRMCS User or FRMCS-equipment remains active and can be reached on this functional identity.
+
+In addition, the FRMCS User is reachable using the FRMCS Equipment Identity, its user identity (if logged in) and its subscriber identity.
+
+### 9.3.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.4-001] | The FRMCS User or the FRMCS-equipment shall be able to deregister from a functional identity. | A | TS 22.280 | 5.9a2 |
+| [R-9.3.4-002] | During the deregistration process, the FRMCS System shall provide a list of functional identities to the FRMCS User or the FRMCS-equipment, to select for deregistration. | A | TS 22.280 | [R-5.9a-004] |
+| [R-9.3.4-003] | The FRMCS User or the FRMCS-equipment shall also be able to perform a deregistration of a functional identity that might not be part of the list provided by the FRMCS System. Then a manual input is required by the FRMCS User. | A | TS 22.280 | [R-5.9a-010] |
+| [R-9.3.4-004] | The FRMCS System shall inform the FRMCS User or the FRMCS-equipment about the outcome of a deregistration request. | A | TS 22.280 | [R-5.9a-025] |
+| [R-9.3.4-005] | <p>At any time, the Railway Subsystem of the FRMCS System shall be able to deregister any functional identity.</p> <p>An automatic deregistration request can be based on:</p> <ul style="list-style-type: none"> <li>• user identification</li> <li>• operational conditions, like schedules when entering the train (for example by using Near Field Communication, Smart Card etc.)</li> <li>• location</li> <li>• time</li> <li>• recent activity</li> <li>• Smart cards or RFID tokens in the vicinity of the UE</li> <li>• FRMCS Equipment Type</li> <li>• etc.</li> </ul> | A | TS 22.280 | [R-5.9a-015]<br>[R-5.9a-018] |
+| [R-9.3.4-006] | The FRMCS System shall be able to notify a specific group of FRMCS User(s) registered to functional identity(ies) with similarities in the structure of the successfully deregistered functional identity. | A | TS 22.280 | Covered in on-network with affiliation mechanism + automatic information when affiliation information changes in a group ([R-6.4.5-003a]). |
+
+## 9.3.5 Use case: User log-in to the FRMCS System
+
+### 9.3.5.1 Description
+
+The user is identified by the FRMCS System.
+
+### 9.3.5.2 Pre-conditions
+
+The equipment type is initialized.
+
+The FRMCS Equipment provides suitable means to the user to log in.
+
+### 9.3.5.3 Service flows
+
+The user performs the log-in procedure.
+
+#### Successful identification
+
+The user is informed about the successful log-in into the FRMCS System. The user has now become a FRMCS User identified by a FRMCS User identity.
+
+#### Unsuccessful identification
+
+The user is informed about the unsuccessful log-in to the FRMCS System. The user is redirected to the log-in procedure.
+
+### 9.3.5.4 Post-conditions
+
+The FRMCS User is identified in the FRMCS System and can register a functional identity.
+
+The FRMCS User is reachable by the FRMCS User identity.
+
+### 9.3.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.5-001] | The FRMCS System shall allow a user to log into the FRMCS System using its FRMCS User Identity to make use of the services provided by the FRMCS System | A | TS 22.280<br>TS 22.179 | 3GPP building blocks = user authentication, service authorization and group affiliation.<br>Sign-in/sign-off and 3GPP building blocks:<br>22.280 [R-5.1.1-001]<br>22.179 section 4.5. |
+| [R-9.3.5-002] | The FRMCS System shall provide service only to FRMCS Users logged in into the FRMCS System. | A | TS 22.280<br>TS 22.179 | 3GPP building blocks = user authentication, service authorization and group affiliation.<br>Sign-in/sign-off and 3GPP building blocks:<br>22.280 [R-5.1.1-001]<br>22.179 section 4.5 |
+
+## 9.3.6 Use case: User log-out from FRMCS System
+
+### 9.3.6.1 Description
+
+The FRMCS User is logged out of the FRMCS System.
+
+### 9.3.6.2 Pre-conditions
+
+The FRMCS User is logged-in the FRMCS System.
+
+### 9.3.6.3 Service flows
+
+The FRMCS User performs the log-out procedure.
+
+#### **Successful log-out**
+
+The FRMCS System deregisters all functional identities of the FRMCS User.
+
+The FRMCS System logs out the FRMCS User.
+
+The FRMCS User is informed about the successful log-out from the FRMCS System.
+
+#### **Unsuccessful log-out**
+
+The FRMCS User is informed about the unsuccessful log-out to the FRMCS System.
+
+### 9.3.6.4 Post-conditions
+
+The FRMCS User is logged out of the FRMCS System. The FRMCS Equipment is still registered to the FRMCS System.
+
+The FRMCS Equipment is reachable by the subscriber identity.
+
+### 9.3.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.6-001] | The FRMCS System shall provide a notification to the FRMCS User when the FRMCS User is logged-out of the FRMCS System | A | Partly covered by TS 22.280 & 22.179. Remaining functionality are outside scope of 3GPP. | No specific login/logout procedure in TS 22.280. so no notification.<br>3GPP building blocks = user authentication, service authorization and group affiliation.<br>Sign-in/sign-off and 3GPP building blocks:<br>22.280 [R-5.1.1-001]<br>22.179 section 4.5. |
+| [R-9.3.6-002] | The FRMCS System shall provide the FRMCS User the necessary means to log out of the FRMCS System. | A | Partly covered by TS 22.280 & 22.179. Remaining functionality are outside scope of 3GPP. | No specific login/logout procedure in TS 22.280.<br>3GPP building blocks = user authentication, service authorization and group affiliation.<br>Sign-in/sign-off and 3GPP building blocks:<br>22.280 [R-5.1.1-001]<br>22.179 section 4.5. |
+| [R-9.3.6-003] | By logging out all functional identities of a FRMCS User are deregistered from the FRMCS User. | A | Partly covered by TS 22.280 & 22.179. Remaining functionality are outside scope of 3GPP. | Partly covered by [R-5.9a-018] but login/logout from the MCX Service system not defined.<br>3GPP building blocks = user authentication, service authorization and group affiliation.<br>Sign-in/sign-off and 3GPP building blocks:<br>22.280 [R-5.1.1-001]<br>22.179 section 4.5. |
+| [R-9.3.6-004] | After logging out the FRMCS User, the FRMCS Equipment shall be reachable via the subscriber identity. | A | Covered | This requirement can be supported by existing MCCore requirements in TS:<br>22.280,<br>22.278,<br>22.261. |
+
+### 9.3.7 Use case: Presentation of identities
+
+#### 9.3.7.1 Description
+
+A FRMCS User or the FRMCS-equipment shall be able to be identified by the functional identity (ies) to other FRMCS Users
+
+#### 9.3.7.2 Pre-conditions
+
+The FRMCS User or the FRMCS-equipment is registered to at least one functional identity.
+
+#### 9.3.7.3 Service flows
+
+##### During call initiation
+
+The identities of the initiating entity (functional identity of a user, functional identity of equipment, user identity and subscriber identity) are to be passed and presented to the other FRMCS Users during communication.
+
+The FRMCS System passes the appropriate functional identity(ies) based on a certain context (like location, destination, time, local configuration, selection from the initiating entity, etc.).
+
+If multiple functional identities are used by the FRMCS User, the presentation is based on certain context (e.g. a call to a train Controller shows the running number, a call to a maintenance Controller shows the engine number).
+
+If the functional identity is not available, the FRMCS User identity is to be presented.
+
+If the functional identity and the FRMCS User identity are not available, the subscriber identity is to be presented.
+
+#### **During a call**
+
+The identities of the connected FRMCS User (s) (functional identity of a user, functional identity of equipment, user identity and subscriber identity) are forwarded to the FRMCS Users participating to the call.
+
+The FRMCS System passes the appropriate functional identity(ies) based on a certain context (like location, destination, time, local configuration, etc.).
+
+If multiple functional identities are used by the FRMCS User, the presentation is based on certain context (e.g. a call to a train Controller shows the running number, a call to a maintenance Controller shows the engine number).
+
+If the functional identity is not available, the FRMCS User identity is to be presented.
+
+If the functional identity and the FRMCS User identity are not available, the subscriber identity is to be presented.
+
+The functional identity(ies) of the talking FRMCS User is/are to be indicated to the listening FRMCS User (s).
+
+If the functional identity is not available, the FRMCS User identity is to be presented.
+
+If the functional identity and the FRMCS User identity are not available, the subscriber identity is to be presented.
+
+#### **9.3.7.4 Post-conditions**
+
+The FRMCS Users are informed about the FRMCS User initiating the communication initiator.
+
+The FRMCS User is informed about who are the participants of the call.
+
+The FRMCS User has at least one functional identity.
+
+### 9.3.7.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.7-001] | During communication initiation, the identities of the initiating entity (functional identity of a user, functional identity of equipment, user identity and subscriber identity) shall be passed to the FRMCS User (s) of the receiver(s) of the call. | A | TS 22.280 | This requirement is partly covered by MCCore, new and additional types of identities need to be supported.]<br>[R-6.4.3-001]: only identification of the transmitting participant is sent to all other affiliated members.<br>TS 22.280<br>[R-5.9a-002]<br>[R-5.9a-020]<br>[R-5.9a-022]<br>[R-5.9a-023] |
+| [R-9.3.7-002] | During a communication, the identities of the connected FRMCS User (s) (functional identity of a user, functional identity of equipment, user identity and subscriber identity) shall be sent to the FRMCS User (s) participants of the call. | A | TS 22.280 | This requirement is partly covered by MCCore, new and additional types of identities need to be supported.<br>TS 22.280<br>[R-5.9a-002]<br>[R-5.9a-020]<br>[R-5.9a-022]<br>[R-5.9a-023]<br>[R-6.9-004] |
+| [R-9.3.7-003] | The FRMCS User (s) shall be presented with the appropriate functional identity(ies) based on a certain context (like location, destination, time, local configuration, etc.). | A | TS 22.280 | Partly covered: functional identity based on context are provide to the FRMCS User on demand for activation. Only activated functional alias(ses) are presented.<br>TS 22.280<br>[R-5.9a-002]<br>[R-5.9a-020]<br>[R-5.9a-022]<br>[R-5.9a-023] |
+| [R-9.3.7-004] | If a functional identity is not available, the FRMCS System shall present the FRMCS User identity. | A | TS 22.280 | Partly covered: [R-6.4.3-001]<br>Only the MCX Service User ID of the transmitting participant is sent to all other affiliated members. |
+| [R-9.3.7-005] | If both the functional identity and the FRMCS User identity are not available, the FRMCS System shall present the subscriber identity. | A | TS 22.280<br>TS 22.278<br>TS 22.261 | This requirement can be supported by existing MCCore requirements. |
+
+### 9.3.8 Use case: Interrogation of identities within a certain context
+
+#### 9.3.8.1 Description
+
+A FRMCS User or the FRMCS-equipment is able to recognize which other functional identities are present within a certain context (for example train, region, communication group, Railway Emergency Communication, all Drivers on a station, etc.).
+
+### 9.3.8.2 Pre-conditions
+
+The FRMCS-equipment is initialised.
+
+### 9.3.8.3 Service flows
+
+#### **Interrogation of functional identities**
+
+The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the own functional identity(ies) or the functional identity of other FRMCS Users or FRMCS-equipment based on a FRMCS User identity or a subscriber identity.
+
+The FRMCS System returns the functional identity(ies) of the particular FRMCS User or FRMCS-equipment.
+
+#### **Interrogation of FRMCS User identities**
+
+The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the own or other FRMCS User identity of FRMCS User (s) based on a functional identity or a subscriber identity.
+
+The FRMCS System returns the FRMCS User identity of the particular FRMCS User (s).
+
+#### **Interrogation of a subscriber identity**
+
+The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the own or other FRMCS Equipment Identity based on a functional identity or a FRMCS User identity.
+
+The FRMCS System returns the particular subscriber identity.
+
+#### **Interrogation of functional identity(ies) in a certain context**
+
+The FRMCS User or the FRMCS-equipment can interrogate the FRMCS System to recognize the functional identities of own or other FRMCS Users within a certain context.
+
+The FRMCS System returns to the FRMCS User or the FRMCS-equipment a set of functional identities (own or other) within the certain context.
+
+### 9.3.8.4 Post-conditions
+
+The requesting FRMCS User or FRMCS-equipment is informed about the own or other FRMCS Users / FRMCS-equipment with a functional identity within a certain context, for example train, region, communication group, Railway Emergency Communication, all Drivers on a station, etc.
+
+### 9.3.8.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------|
+| [R-9.3.8-001] | The FRMCS User or the FRMCS-equipment shall be able to interrogate the FRMCS System to provide the functional identity(ies) registered to a certain FRMCS User identity.<br>The FRMCS System shall return the functional identity(ies) of the FRMCS User. | A | TS 22.280 | TS 22.280<br>R-5.9a-011<br>R-5.9a-012 |
+| [R-9.3.8-002] | The FRMCS User or the FRMCS-equipment shall be able to interrogate the FRMCS System to provide the functional identity(ies) based on a subscriber identity.<br>The FRMCS System shall return the functional identity(ies) of a subscriber identity. | A | TS 22.280 | TS 22.280<br>R-5.9a-011<br>R-5.9a-012 |
+| [R-9.3.8-003] | The FRMCS User or the FRMCS-equipment, shall be able to interrogate the FRMCS System to provide the FRMCS User identity registered to a functional identity.<br>The FRMCS System shall return the FRMCS User identity/identities. | A | TS 22.280 | TS 22.280<br>R-5.9a-011<br>R-5.9a-012 |
+| [R-9.3.8-004] | The FRMCS User or the FRMCS-equipment, shall be able to interrogate the FRMCS System to provide the FRMCS User identity based on a subscriber identity.<br>The FRMCS System shall return the FRMCS User identity/identities. | A | TS 22.280 | TS 22.280<br>R-5.9a-011<br>R-5.9a-012 |
+| [R-9.3.8-005] | The FRMCS User or the FRMCS-equipment, shall be able to interrogate the FRMCS System to provide the subscriber identity based on a functional identity<br>The FRMCS System shall return the subscriber identity(ies). | A | TS 22.280 | [R-5.9a-011] |
+
+## 9.3.9 Use case: Service interworking with GSM-R
+
+### 9.3.9.1 Description
+
+Service interworking with legacy communication systems is of importance for the time period both systems have to coexist. In this section service interworking between the GSM-R System and the FRMCS System for functional identities and its associated roles will be addressed.
+
+#### Functional Address
+
+On top of the E.164 numbering plan alternative addressing scheme called functional addressing is used in the context with GSM-R. Functional addressing scheme allows the establishment of communication without knowing each E.164 number associated with a particular train. A functional address consists of:
+
+IC+CT+UN
+
+- IC International code is used to route calls to the appropriate GSM-R network
+- CT Call Type prefix defines how to interpret the User Number (UN) as train function number, engine function number, group calls etc.
+- UN User Number is of variable length and depends on the information i.e. train function number etc. Within the UN a Functional Code (FC) is associated and provides the information of the person or equipment on a particular train, or a particular team within a given area. Therefore, the UN consists of User Identification Number (UIN) i.e. train number etc. and the Functional Code (FC) resulting into: UN= UIN+FC
+
+A functional address only consists of numeric characters.
+
+### 9.3.9.2 Pre-conditions
+
+Following user addressing scenarios applies between FRMCS System and GSM-R system when using alternative addressing schemes in FRMCS:
+
+A GSM-R user is able to obtain communication services from the GSM-R system. E.164 numbering plan and functional addressing scheme applies.
+
+A FRMCS User is able to obtain communication services from the FRMCS System or from the GSM-R system. If the FRMCS User, in this sense the FRMCS Equipment is registered to the FRMCS System, user addressing of the FRMCS system applies comprising the use of functional identity addressing scheme. If the FRMCS Equipment is registered to the GSM-R system, E.164 numbering plan and functional addressing i.e. IC+CT+UIN+FC scheme applies.
+
+For a train route which encompasses both GSM-R and FRMCS coverage areas the functional identity registration for users and equipment travelling this route shall be made in two parallel entries in the respective GSM-R functional addressing and FRMCS Functional Aliasing databases.
+
+Any subsequent modification of functional addressing or functional aliasing while the user or equipment is registered shall be done in parallel on both systems
+
+The deregistration of the functional aliasing or functional addressing for the user or equipment with parallel registration shall be deregistered in parallel.
+
+### 9.3.9.3 Service flows
+
+#### FRMCS User relocates from GSM-R system to the FRMCS System
+
+When the FRMCS Equipment relocates from GSM-R system to the FRMCS System, the applicable functional address(es) associated with the FRMCS User require(s) a conversion to the functional identity format applicable within
+
+the FRMCS System. The functional address remains active until the corresponding functional identity becomes deactivated.
+
+#### **FRMCS User relocates from FRMCS System to the GSM-R system**
+
+When the FRMCS Equipment relocates from FRMCS System to the GSM-R system, the applicable functional identity or identities associated with FRMCS user require(s) a conversion to the functional address format applicable within the GSM-R system. The functional identity or identities remains active until the corresponding functional address becomes deactivated.
+
+#### **Bilateral communication addressing between FRMCS System and GSM-R**
+
+A FRMCS User establishes a communication using the functional identity of another FRMCS User whose FRMCS Equipment is registered to GSM-R.
+
+A FRMCS User establishes a communication using the functional address of a GSM-R user whose GSM-R equipment is registered to GSM-R.
+
+A GSM-R user establishes a communication using the functional identity of a FRMCS User.
+
+#### **9.3.9.4 Post-conditions**
+
+After successful relocation following is applicable:
+
+- From GSM-R point of view, the FRMCS User is reachable for communication by its functional address.
+- From FRMCS System point of view, the FRMCS User is reachable for communication by its functional identity.
+
+### 9.3.9.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.3.9-001] | The FRMCS System shall support the conversion between functional identity encompassing the associated role and functional addressing as part of the GSM-R system. | A | 22.179<br>22.280 | 22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005] |
+| [R-9.3.9-002] | <p>The FRMCS System shall support functional addressing format consisting of:</p> <p>IC+CT+UN</p> <p>IC International code is used to route calls to the appropriate GSM-R network</p> <p>CT Call Type prefix defines how to interpret the User Number (UN) as train function number, engine function number, group calls etc.</p> <p>UN User Number is of variable length and depends on the information i.e. train function number etc. Within the UN a Functional Code (FC) is associated and provides the information of the person or equipment on a particular train, or a particular team within a given area. Therefore, the UN consists of User Identification Number (UIN) i.e. train number etc. and the Functional Code (FC) resulting into: UN= UIN+FC</p> <p>A functional address only consists of numeric characters.</p> | A | 22.280 | [ [R-5.9a-014] |
+| [R-9.3.9-003] | A FRMCS User shall be | A | 22.179<br>22.280 | 22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2- |
+
+| | | | | |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------|---|------------------|---------------------------------------------------------------------------------------------------------------------------------|
+| | reachable by its FRMCS Functional Identity if the FRMCS Equipment is registered to the GSM-R system | | | 002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005] |
+| [R-9.3.9-004] | A GSM-R User shall be reachable if a FRMCS User is registered to the FRMSC System using the functional address of the particular GSM-R user. | A | 22.179<br>22.280 | 22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005] |
+| [R-9.3.9-005] | A FRMCS User shall be reachable if a GSM-R user uses the functional identity of the particular FRMCS User. | A | 22.179<br>22.280 | [ 22.179 [R-6.18.4.2-002], [R-6.18.4.2-002a], [R-6.18.4.2-002b] and 22.280 [R-6.17.3.1-003], [R-6.17.3.1-004], [R-6.17.3.1-005] |
+
+## 9.4 Location services related use cases
+
+### 9.4.1 Introduction
+
+In this chapter the use cases related to location services are defined. The following use cases are defined:
+
+- Provide location information
+- Request for location information
+- Request for identities based on location
+
+The location information of an FRMCS Equipment consists of the following elements:
+
+- Geographic Location,
+- Velocity (the combination of speed and direction),
+- Infra Location (additional information specifying railway infra elements; for example: signal 123, switch 456, track section 789A, etcetera), and
+- Quality of Service information (horizontal and vertical accuracy, response time, QoS class, accuracy of Infra Location).
+
+### 9.4.2 Use Case: Provide location information
+
+#### 9.4.2.1 Description
+
+The FRMCS Equipment provides its location information to the FRMCS System for further processing e.g. for automatic train operation. External systems can be supported in providing additional location information with or without functional identity reference to the FRMCS System for further processing.
+
+The location information may be shared directly with other applications on the same FRMCS Equipment without the involvement of the FRMCS System.
+
+#### 9.4.2.2 Pre-conditions
+
+The FRMCS Equipment supports some mechanisms to obtain its location.
+
+### 9.4.2.3 Service flows
+
+The FRMCS Equipment determines its current location in a periodic or an event-triggered manner. The frequency of the location reporting may change according to the application requirements.
+
+The FRMCS Equipment reports location information that may include its applicable FRMCS Equipment Identity. At any time, upon request, the FRMCS Equipment shall be able to report its location information.
+
+External systems can provide additional information to the FRMCS System in order to improve location accuracy of an FRMCS Equipment.
+
+The received location information is stored by FRMCS System.
+
+In case of periodic location reporting, the FRMCS System supervises the continuous supply of the location information. If the supply of periodic location information by the FRMCS Equipment stops, the FRMCS System initiates the re-establishment of the periodic location information data flow. The FRMCS System can correlate other identities from the FRMCS Equipment Identity.
+
+### 9.4.2.4 Post-conditions
+
+The location information of the FRMCS Equipment is available in the FRMCS System.
+
+### 9.4.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.4.2-001] | The FRMCS Equipment shall be able to provide its location to the FRMCS System. | A | 22.280 | This requirement can be supported by existing 3GPP requirements |
+| [R-9.4.2-001a] | The location information of an FRMCS Equipment shall consist of: <ul style="list-style-type: none"> <li>• The geographic location,</li> <li>• The velocity,</li> <li>• The infra location, and</li> <li>• The Quality of service information.</li> </ul> | A | 22.071 | Partly covered by TS 22.071. Location Information of a UE consists of Geographic Location, Velocity, <b>Civic Location</b> and Quality of Service information. Civic location (also called Dispatchable Location) is only applicable to emergency services based on regional regulatory requirements (wireless 911 calls). |
+| [R-9.4.2-002] | The FRMCS System shall be able to request the FRMCS Equipment to provide its location. | A | 22.280 | This requirement can be supported by existing 3GPP requirements |
+| [R-9.4.2-003] | The FRMCS System shall be able to request the FRMCS Equipment to provide its location periodically. | A | 22.280 | This requirement can be supported by existing 3GPP requirements |
+| [R-9.4.2-004] | The FRMCS System shall be able to request the FRMCS Equipment to stop providing its location periodically. | A | 22.280 | This requirement can be supported by existing 3GPP requirements |
+| [R-9.4.2-005] | The FRMCS System shall be able to handle additional location information from other external sources. | A | 22.280 | |
+
+## 9.4.3 Use Case: Request for location information
+
+### 9.4.3.1 Description
+
+A FRMCS User, an application or an External System can request the location information of a functional identity, FRMCS User identity or FRMCS Equipment Identity from the FRMCS System.
+
+### 9.4.3.2 Pre-conditions
+
+The FRMCS User, an application or an External System, is entitled to request location information from the FRMCS System.
+
+### 9.4.3.3 Service flows
+
+A FRMCS User, an application or an External System requests location information to the FRMCS System based on a functional identity, FRMCS User identity or FRMCS Equipment Identity.
+
+The location requesting entity can request for a single location information or a periodical update of the location information.
+
+The location requesting entity can send a request to the FRMCS System to stop the periodical update of location information.
+
+#### ***Positive outcome***
+
+The FRMCS System provides the location information as requested, either once or periodically.
+
+#### ***Negative outcome***
+
+The location information is not available, or the identity is not known in the FRMCS System.
+
+The FRMCS System sends a response back to the requesting FRMCS User, application or External System if the location information is not available.
+
+### 9.4.3.4 Post-conditions
+
+The location information is provided, if available.
+
+### 9.4.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| [R-9.4.3-001] | Upon request from FRMCS Users, applications or External Systems the FRMCS System shall be able to provide the location information of a functional identity, FRMCS User identity or FRMCS Equipment Identity. | A | Partly covered by TS 22.280. Remaining functionality are outside scope of 3GPP. | This requirement is partly covered by TS 22.280 [R-5.9a-027] and TS 22.280 [R-6.12-006]. |
+| [R-9.4.3-002] | Upon request from FRMCS Users, applications or External Systems the FRMCS System shall be able to periodically provide the location information of a functional identity, FRMCS User identity or FRMCS Equipment Identity. | A | Partly covered by TS 22.280. Remaining functionality are outside scope of 3GPP. | This requirement is partly covered by TS 22.280 [R-6.12-006]. |
+| [R-9.4.3-003] | The FRMCS System shall only allow the FRMCS User, the application or the External System initially requesting periodic location reporting to stop the periodic location reporting. | A | Partly covered by TS 22.280. Remaining functionality are outside scope of 3GPP. | This requirement is partly covered by TS 22.280 [R-5.11-005] and TS 22.280 [R-6.12-007]. |
+
+## 9.4.4 Use Case: Request for identities in a certain area
+
+### 9.4.4.1 Description
+
+A FRMCS User, an application or an External System can request identities based on location information from the FRMCS System.
+
+### 9.4.4.2 Pre-conditions
+
+The FRMCS User, an application or an External System, is entitled to request location information from the FRMCS System.
+
+### 9.4.4.3 Service flows
+
+The FRMCS User, an application or an External System requests the FRMCS System to provide a list of functional identities, FRMCS User identities or FRMCS Equipment Identities at a certain point, area, station, track section, etc.
+
+The FRMCS User, an application or an External System can request the list of identities to be given once or periodically by the FRMCS System.
+
+Only the FRMCS User, the application or the External System initially requesting periodic reporting can stop the periodic reporting by the FRMCS System.
+
+### 9.4.4.4 Post-conditions
+
+The FRMCS System provides the list of identities as requested.
+
+#### 9.4.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|
+| [R-9.4.4-001] | The FRMCS System shall allow a FRMCS User, an application or an External System to request a list of functional identities, FRMCS User identities or FRMCS Equipment Identities in a certain area either periodically or as a onetime request. | A | Covered by TS 22.280.<br>Serving an external system is outside the scope of 3GPP. | This requirement is covered by existing 3GPP Location Services and MCCore requirements.<br>[R-5.9a-031] |
+| [R-9.4.4-002] | The FRMCS System shall be able to provide the list of identities and their location to the requesting FRMCS User, application or External System either periodically or as a onetime report. | A | Covered by TS 22.280.<br>Serving an external system is outside the scope of 3GPP. | This requirement is covered by existing 3GPP Location Services and MCCore requirements.<br>[R-5.9a-031] |
+| [R-9.4.4-003] | The FRMCS System shall allow only the requesting FRMCS User, application or External System to stop the periodic reporting. | A | Covered by TS 22.280.<br>Serving an external system is outside the scope of 3GPP. | This requirement is covered by existing 3GPP Location Services and MCCore requirements.<br>[R-5.9a-031] |
+
+### 9.5 FRMCS User communication handling related use cases
+
+#### 9.5.1 Introduction
+
+In this chapter the use cases related to the function of inviting a FRMCS User to a communication are defined.
+
+- Invite-a-FRMCS User to a FRMCS communication
+- FRMCS User receiving an invitation to a FRMCS communication
+- FRMCS User accepting an invitation to a FRMCS communication
+- FRMCS User rejecting an invitation to a FRMCS communication
+- FRMCS User ignoring an invitation to a FRMCS communication
+- Service interworking with GSM-R
+
+#### 9.5.2 Use Case: Inviting-FRMCS User(s) to a voice communication
+
+##### 9.5.2.1 Description
+
+An authorized FRMCS User can invite other(s) FRMCS User(s) to join an ongoing voice communication.
+
+### 9.5.2.2 Pre-conditions
+
+The inviting FRMCS User is part of an already established FRMCS voice communication of two or more FRMCS Users.
+
+### 9.5.2.3 Service flows
+
+#### Inviting user
+
+From a list of FRMCS Users provided by the FRMCS System or by entering an unlisted identity, the inviting FRMCS User selects another FRMCS User, or a pre-defined group of users, to be invited.
+
+### 9.5.2.4 Post-conditions
+
+The FRMCS User (s) have been invited.
+
+The inviting FRMCS User remains connected to the FRMCS voice communication involving two or more FRMCS Users.
+
+### 9.5.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.5.2-001] | If authorized to, a FRMCS User shall be able to invite other(s) FRMCS User(s) to join an ongoing voice communication. | A | 22.280 | Partially covered by 6.4.6.2 Negotiated change" provides the basic functionality (limited to ongoing group communications). |
+| [R-9.5.2-002] | The FRMCS System shall provide a list of identities for the inviting FRMCS User to select from. | A | N/A | Implementation option: 22.280 6.4.6.2 Negotiated change does not make any assumption on the way and means an authorised user gets the identities to be included - i.e. this happens on application layer |
+| [R-9.5.2-003] | The invitation request shall either be based on the functional identity, FRMCS User Identity, FRMCS Equipment Identity. | A | N/A | Implementation option: Keep it on application layer as otherwise, considering the sheer number of users, we would have to give an indication on how to filter that list. |
+
+## 9.5.3 Use Case: FRMCS User receiving an invitation to a voice communication
+
+### 9.5.3.1 Description
+
+A FRMCS User will receive the invitation originated by the inviting FRMCS User.
+
+### 9.5.3.2 Pre-conditions
+
+The FRMCS User may or may not be involved in voice communication.
+
+### 9.5.3.3 Service flows
+
+The invitation is indicated to the FRMCS User by audible and visual notification.
+
+### 9.5.3.4 Post-conditions
+
+The FRMCS User has received the invitation.
+
+Voice communication of the invited FRMCS User continues unaffected.
+
+### 9.5.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------|
+| [R-9.5.3-001] | If entitled to, a FRMCS User shall be able to receive invitations to voice communication(s), independent of being involved in communication. | A | 22.280 | Implicitly provided by the normal function of MCX Communication |
+
+## 9.5.4 Use case: FRMCS User accepting an invitation to a voice communication
+
+### 9.5.4.1 Description
+
+A FRMCS User can accept the invitation sent by the inviting FRMCS User.
+
+### 9.5.4.2 Pre-conditions
+
+The FRMCS User has received an invitation to a voice communication which is not yet expired.
+
+### 9.5.4.3 Service flows
+
+#### **Invited FRMCS User not involved in a voice communication**
+
+The FRMCS User accepts the invitation of the voice communication.
+
+The FRMCS User joins the ongoing voice communication. If the ongoing voice communication involves two users (user-to-user), the ongoing voice communication is translated into a multi-users voice communication.
+
+Other FRMCS Users involved in the voice communication receive a notification that the FRMCS User has joined the communication by which the joining FRMCS User is identified to the other FRMCS Users.
+
+#### **Invited FRMCS User is involved in a voice communication**
+
+The FRMCS User accepts the invitation of the voice communication.
+
+The FRMCS System prompts the invited FRMCS User about the treatment of the existing voice communication.
+
+The FRMCS User may have the choice between some or all of these options:
+
+- **Terminate:** The FRMCS User terminates the current voice communication.
+- **Leave** the existing voice communication. If the communication consisted only of two participants, a participant leaving the communication will cause the communication to be terminated.
+
+- **Merge:** The FRMCS System merges the two voice communications into one single voice communication.
+
+The FRMCS User joins the ongoing voice communication. If the ongoing voice communication involves two users (user-to-user), the ongoing voice communication is translated into a multi-users voice communication.
+
+Other FRMCS Users involved in the voice communication(s) are notified that the invited user has joined the communication or the communication has been merged.
+
+#### 9.5.4.4 Post-conditions
+
+The invited FRMCS User is participating in the voice communication he was invited to.
+
+The invited FRMCS User is indicated as connected to the voice communication to all FRMCS Users in the communication.
+
+The presence status of the invited user is updated with the appropriate attributes.
+
+#### 9.5.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.5.4-001] | The FRMCS User shall be able to accept an invitation to join a voice communication. | A | 22.280 | R-6.4.6.2-005 |
+| [R-9.5.4-002] | When accepting a communication invitation, in case the FRMCS User has a voice communication, the FRMCS User shall be able to leave, terminate or merge the voice communication. If the FRMCS User decides to merge the communications both voice communications shall be merged. | A | 22.280 | 5.4.1, 5.4.2, 5.1.5<br>R-6.4.4-003, R-6.4.4-004<br>The affiliation mechanism is sufficient to mimic the desired behavior of leave and terminate<br>Merging can be done by 22.280 6.6.1 Group regrouping" |
+| [R-9.5.4-003] | When accepting a communication invitation (i.e. the FRMCS User joins the ongoing voice communication), If the ongoing voice communication involves two users (user-to-user), the ongoing voice communication is translated into a multi-users voice communication. | A | Not covered | TS 22.280 6.4.6.2 Negotiated change is limited to group communications. |
+| [R-9.5.4-004] | When accepting a communication invitation, other FRMCS Users involved in the voice communication(s) are notified that the invited user has joined the communication, or the communication has been merged. | A | 22.280 | Covered by the affiliation mechanism. |
+
+## 9.5.5 Use case: FRMCS User rejecting an invitation to a voice communication
+
+### 9.5.5.1 Description
+
+A FRMCS User can reject the invitation sent by the inviting FRMCS User.
+
+### 9.5.5.2 Pre-conditions
+
+The FRMCS User has received an invitation to a voice communication which is not expired yet.
+
+### 9.5.5.3 Service flows
+
+The FRMCS User rejects the invitation.
+
+The inviting FRMCS User receives a notification that the invitation was rejected by the invited FRMCS User.
+
+### 9.5.5.4 Post-conditions
+
+The invited FRMCS User is not participating in the voice communication related to the received invitation.
+
+### 9.5.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------|
+| [R-9.5.5-001] | The FRMCS User shall be able to reject the invitation to join a voice communication. | A | 22.280 | R-6.4.6.2-005 |
+| [R-9.5.5-002] | The inviting FRMCS User sending the invitation shall be informed.<br>The inviting FRMCS User shall be notified. | A | 22.280 | R-6.4.6.2-005 |
+
+## 9.5.6 Use case: FRMCS User ignoring an invitation to a voice communication
+
+### 9.5.6.1 Description
+
+A FRMCS User can ignore the invitation sent by the inviting FRMCS User.
+
+### 9.5.6.2 Pre-conditions
+
+The FRMCS User has received an invitation which is not yet expired.
+
+### 9.5.6.3 Service flows
+
+The invited FRMCS User does not respond to the received invitation within a certain period of time
+
+The inviting FRMCS User receives a notification that the invitation was rejected as it was not accepted within a certain period of time.
+
+### 9.5.6.4 Post-conditions
+
+The invited FRMCS User does not participate in the voice communication.
+
+### 9.5.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------|
+| [R-9.5.6-002] | If the receiving FRMCS User has not reacted on the invitation within a certain period of time [t1] the FRMCS System shall notify the inviting FRMCS User accordingly and stop the invitation request. | A | N/A | This is left to the app layer design to decide what happens if a MCX User does not react in due time. |
+
+## 9.5.7 Service interworking with GSM-R
+
+### 9.5.7.1 Description
+
+For migration purposes, the service interworking between the GSM-R system and FRMCS system for inviting a user needs to be defined.
+
+The following interworking use cases are needed for alerting a controller functionality: the case that there is a group call in GSM-R and a user would like to invite a controller who is in FRMCS:
+
+Inviting-a-FRMCS User to a GSM-R voice group communication:
+operational scenarios to support service interworking between GSM-R and FRMCS
+
+
+
+The diagram illustrates the interworking between GSM-R and FRMCS. On the left, the GSM-R coverage area shows an ongoing group call between three mobile phones and a user labeled 'CT7'. A dispatcher icon is also present. Step (1) shows the dispatcher inviting the CT7 user. Step (2) shows the interconnection between the GSM-R and FRMCS networks via ISDN or SIP-R to invite the dispatcher. The FRMCS coverage area on the right shows three mobile phones and a computer monitor connected to a base station.
+
+Diagram illustrating the service interworking between GSM-R and FRMCS for inviting a user. The diagram is split into two halves: GSM-R coverage (left, blue background) and FRMCS coverage (right, orange background). In the GSM-R coverage area, an 'Ongoing Group Call' is shown involving three mobile phones and a user labeled 'CT7'. A dispatcher icon is also present. Step (1) shows the dispatcher inviting the CT7 user. Step (2) shows the interconnection between the GSM-R and FRMCS networks via ISDN or SIP-R to invite the dispatcher. The FRMCS coverage area shows three mobile phones and a computer monitor connected to a base station.
+
+Note: Group calls may be used by shunting or trackside workers when their dispatcher has already migrated to FRMCS
+
+Figure 9.5.7.1-1. Inviting-a-user from GSM-R to FRMCS
+
+The case that there is a group communication in FRMCS, and a user would like to invite a controller who is in GSM-R also applies:
+
+Inviting-a-GSM-R User to a FRMCS voice group communication:
+operational scenarios to support service interworking between GSM-R and FRMCS
+
+
+
+Diagram illustrating the operational scenario for inviting a GSM-R user to a FRMCS voice group communication. The diagram is split into two coverage areas: GSM-R coverage (left, blue background) and FRMCS coverage (right, orange background). In the FRMCS coverage area, an 'Ongoing Group Call' is shown with three mobile devices and a dispatcher (DS). A worker (represented by a yellow figure) initiates step (1), 'Invites his dispatcher'. The dispatcher then initiates step (2), 'Interconnection between GSM-R and FRMCS networks via ISDN or SIP-R to invite his dispatcher'. This interconnection is shown as a line passing through a base station in the FRMCS area, across the boundary, to a base station in the GSM-R area, and finally to a computer icon representing the dispatcher's terminal in the GSM-R area.
+
+Note: Group calls may be used by shunting or trackside workers when their dispatcher has not migrated to FRMCS yet
+
+Figure 9.5.7.1-2. Inviting-a-user from FRMCS to GSM-R
+
+The above use cases only apply if the controller system is connected to only one system. If the controller system is connected to both FRMCS and GSM-R systems, there is no need.
+
+This use case only applies to end user devices supporting both FRMCS and GSM-R systems.
+
+### 9.5.7.2 Pre-condition
+
+#### Group call in GSM-R and controller in FRMCS
+
+A voice group call has been established in GSM-R System.
+
+The controller in charge of the area is attached to FRMCS System only. This controller is not part of the voice group call.
+
+#### Group call in FRMCS and controller in GSM-R
+
+A voice group call has been established in FRMCS System.
+
+The controller in charge of the area is attached to GSM-R System only. This controller is not part of the voice group call.
+
+### 9.5.7.3 Service flow
+
+#### Group call in GSM-R and controller in FRMCS
+
+When there is an ongoing voice group call in GSM-R system and when a GSM-R User part of this group call is initiating an *alerting-a-controller* to invite a controller to join this group call, the request to join this group call shall be routed to the relevant Controller(s) attached to FRMCS System.
+
+#### Group call in FRMCS and controller in GSM-R
+
+When there is an ongoing voice group call in FRMCS system and when a FRMCS User part of this group call is initiating an *Inviting-FRMCS User(s) to a voice communication* to invite a controller to join this group call, the request to join this group call shall be routed to the relevant Controller(s) attached to GSM-R System.
+
+### 9.5.7.4 Post-condition
+
+#### Group call in GSM-R and controller in FRMCS
+
+The relevant Controller(s) attached to FRMCS System are invited to join the ongoing voice group call in GSM-R system.
+
+#### Group call in FRMCS and controller in GSM-R
+
+The relevant Controller(s) attached to GSM-R System are invited to join the ongoing voice group call in FRMCS system.
+
+### 9.5.7.5 Potential requirements
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------|
+| [9.5.7-001] | The FRMCS System shall provide service interworking between the alerting a controller functionality in the GSM-R system and in the FRMCS System. | A | 22.280 | Covered by [R-6.17.3.1-002] to [R-6.17.3.1-005]. |
+
+## 9.6 Void
+
+## 9.7 Multiuser talker control related use cases
+
+### 9.7.1 General Description and potential requirements
+
+#### 9.7.1.1 General Description
+
+In this chapter the use cases related to multiuser talker control for voice communication are defined. The following use cases are defined:
+
+- Set the number of simultaneous talkers
+- Set initial talker permissions and priorities
+- Request permission to talk
+- Grant permission to talk
+- Revoke permission to talk
+
+Note: For examples of Role management, like functional identities, FRMCS Equipment Identities, etc. in the railway environment, see annex A.
+
+#### 9.7.1.2 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------|
+| [R-9.7.1-001] | Multiuser talker control shall be available for both on-net and off-net communication. | A | 22.179 | Covered for On-net only |
+
+## 9.7.2 Use case: Set the number of simultaneous talkers
+
+### 9.7.2.1 Description
+
+For multiuser communication, i.e. when several users are involved in the same communication, the number of users that are granted the right to talk at the same time can be limited to either one, a limited number or unrestricted number.
+
+The communication application (e.g. shunting team communication) will set the number of simultaneous talkers and/or the identities of involved FRMCS Users and if required other application specific criteria.
+
+### 9.7.2.2 Pre-conditions
+
+An active communication application capable to use the multiuser talker control.
+
+### 9.7.2.3 Service flows
+
+The communication application sends the number of simultaneous talker(s) information to the multiuser talker control.
+
+This information is used by multiuser talker control when setting up the communication.
+
+If there is a need to change the number of simultaneous talkers, it is the communication application which sends this information to the multiuser talker control.
+
+The multiuser talker control then uses this updated information for controlling the number of simultaneous talkers in the communication.
+
+### 9.7.2.4 Post-conditions
+
+The multiuser talker control is aware about the number of simultaneous FRMCS Users and uses this information during communication.
+
+### 9.7.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------|
+| [R-9.7.2-001] | The FRMCS System shall be able to limit the number of simultaneous talkers in a multiuser communication. | A | 22.179 | R-6.2.3.7.2-005 |
+| [R-9.7.2-002] | The maximum number of simultaneous talkers in a multiuser communication shall be provided by the communication application. The number of simultaneous talkers can be either one, a limited number or an unrestricted number and shall be changeable during the communication. | A | 22.179 | R-6.2.3.7.2-006 |
+
+## 9.7.3 Use case: Set initial talker permissions and priorities
+
+### 9.7.3.1 Description
+
+There are different requirements for talker permissions and to prioritise talkers in different communication applications.
+
+The FRMCS Users are identified by their functional identities.
+
+The communication application defines the talker permissions and priorities based on the functional identities and the type of communication application, e.g., railway emergency call, shunting, multi train.
+
+One or multiple FRMCS Users can be granted with the permission to perform as talker in a certain communication. These FRMCS Users are able to request permission to talk during communication.
+
+Certain FRMCS User(s) that have requested the permission to talk at the same time or while another user is talking can be granted with an initial talker permission i.e., they will be given the permission first before requests of others are served independent of whether they were the first requesting the permission to talk or not. This initial talker permission granted for certain FRMCS User(s) is limited in time by system configuration.
+
+Different FRMCS Users can be granted with a different talker priority. In case of parallel requests for permission to talk, the permission is granted to the FRMCS User(s) with highest talker priority. The requests with identical talker priorities will be queued based on the time of request.
+
+### 9.7.3.2 Pre-conditions
+
+An active communication application capable to use the multiuser talker control.
+
+### 9.7.3.3 Service flows
+
+The communication application sends information about talker permissions and talker priorities to the multiuser talker control application.
+
+This information is used in multiuser talker control when setting up the communication.
+
+If there is a need to change the information about talker permissions and talker priorities, it is the communication application that sends this information to multiuser talker control.
+
+The multiuser control then uses this updated information for controlling the talker permissions and talker priorities in the communication.
+
+### 9.7.3.4 Post-conditions
+
+The multiuser control is aware of the talker permissions and talker priorities and uses this information for communication control/setup.
+
+### 9.7.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.7.3-001] | The FRMCS System shall be able to handle talker permissions and priorities as provided by the communication application, e.g., railway emergency call, shunting, multi train | A | 22.179 | R-6.2.3.7.4.1-002<br>R-6.2.3.7.4.1-004 |
+| [R-9.7.3-002] | The FRMCS System shall allow to grant several FRMCS Users with the permission to perform as talker in a certain communication. | A | 22.179 | R-6.2.3.7.4.1-002<br>R-6.2.3.7.4.1-003 |
+| [R-9.7.3-003] | FRMCS Users shall be able to request permission to talk during communication. | A | 22.179 | R-6.2.3.7.3-004 |
+| [R-9.7.3-004] | The FRMCS System shall be able to grant FRMCS Users an initial talker permission (i.e., be the first speaker in the communication) ensuring that the entitled FRMCS User(s) are able to talk first, once the communication is established. | A | 22.179 | R-6.2.3.7.4.1-003 |
+| [R-9.7.3-004a] | This initial talker permission granted for certain FRMCS User(s) is limited in time by system configuration. | A | 22.179 | Partly covered by floor priority, override mechanism and dynamic change of maximum number of simultaneous talkers (section 6.2.3.7). How to identify that certain user(s) can be granted (e.g., train driver initiating the call) is not in the scope of 3GPP. No timer in current specification to limit time for initial talker permission. |
+| [R-9.7.3-005] | The FRMCS System shall be able to grant the permission to talk based on a FRMCS User talker priority. In case of pending requests for permission to talk, the permission shall be granted to the FRMCS User with highest talker priority. Requests of identical talker priority shall be handled based on the time of request. | A | 22.179 | R-6.2.3.7.4.1-004<br>R-6.2.3.7.4.1-004 |
+
+### 9.7.4 Use case: Request permission to talk
+
+#### 9.7.4.1 Description
+
+There are occasions in the railway environment where it is needed to mitigate the risk of miscommunication. Use cases include, for example:
+
+- Emergency communication
+- Shunting communication
+- Trackside worker communication
+
+The system shall therefore be able to limit the number of simultaneous talkers in a voice communication.
+
+An entitled FRMCS User shall be able to select and de-select FRMCS User (s) being able to talk in a voice communication.
+
+The FRMCS User shall be able to request the permission to talk (raise the hand).
+
+#### 9.7.4.2 Pre-conditions
+
+The FRMCS User is involved in an active voice communication. The number of simultaneous talkers is limited in this communication.
+
+#### 9.7.4.3 Service flows
+
+The FRMCS User requests permission to talk on the MMI of the communication application (e.g. by pressing a Push-to-talk button)
+
+The communication application sends the request to the multiuser talker control in the FRMCS System.
+
+The communication application indicates on the MMI that talker permission has been requested.
+
+#### 9.7.4.4 Post-conditions
+
+Permission to talk has been requested and a response from the multiuser talker control in the FRMCS System expected.
+
+#### 9.7.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------|
+| [R-9.7.4-001] | An entitled FRMCS User shall be able to select and de-select FRMCS User (s) being able to talk in a voice communication. | A | 22.179 | [R-6.2.3.7.2-002] |
+| [R-9.7.4-002] | The FRMCS User shall be able to request permission to talk of the FRMCS UE (e.g. by pressing a Push-to-talk button). The FRMCS UE shall indicate the talker permission has been requested. | A | 22.179 | [R-6.2.3.7.3-001] |
+
+### 9.7.5 Use case: Grant permission to talk
+
+#### 9.7.5.1 Description
+
+There are occasions in the railway environment where it is needed to mitigate the risk of miscommunication. Use cases include, for example:
+
+- Emergency communication
+- Shunting communication
+
+- Trackside worker communication
+
+The system shall be able to limit the number of simultaneous talkers in a voice communication.
+
+The list of FRMCS Users with permission to talk and those who have requested it, shall be available to the Multiuser Talker Control application.
+
+### 9.7.5.2 Pre-conditions
+
+The FRMCS User is an active voice communication.
+
+Multiuser Talker Control is configured by the communication application to limit the number of simultaneous talkers.
+
+By default, the Multiuser Control uses a set of criteria, like priorities, identities, etc. to manage the requests automatically
+
+In addition, an entitled FRMCS User (i.e. based on functional identity) who is monitoring the progress of the communication can select and de-select simultaneous talkers.
+
+### 9.7.5.3 Service flows
+
+#### **Automatic management of requests**
+
+The Multiuser Talker Control in the FRMCS System receives a request to talk from a FRMCS User.
+
+The Multiuser Talker Control in the FRMCS System verifies the number of FRMCS Users who already have permission to talk.
+
+If the number of FRMCS Users with permission to talk does not exceed the maximum number of simultaneous talkers, the Multiuser Talker Control grants automatically the permission to the requester.
+
+If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers, the Multiuser Talker Control decides based on certain criteria, like priorities, functional identity, etc. who will keep the right to speak and who will be granted the permission to talk the Multiuser Talker Control configures the system accordingly.
+
+If the number of talker permissions are reduced and the reduction results in having more active talkers than permitted, the active talkers lose their permission to talk as soon as they stop talking (i.e. release PTT) until the new maximum allowed number of talkers is met.
+
+The Multiuser Talker Control service sends an indication to the FRMCS Users whose permission to talk has been changed due to that.
+
+#### **Management of requests by an entitled FRMCS User**
+
+The Multiuser Talker Control in the FRMCS System receives a request to talk from a FRMCS User.
+
+The Multiuser Talker Control service in the FRMCS System verifies the number of FRMCS Users who already have permission to talk.
+
+If the number of FRMCS Users with permission to talk does not exceed the maximum number of simultaneous talkers, the Multiuser Talker Control service grants automatically the permission to the requester.
+
+If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers, the Multiuser Talker Control service alerts the entitled FRMCS User that is monitoring the communication, who is presented with the list of simultaneous talkers and the list of pending requests and decides who will keep the right to speak and who will be granted the permission to talk by selecting and de-selecting the corresponding FRMCS User.
+
+The Multiuser Talker Control service configures the system accordingly.
+
+The Multiuser Talker Control service sends an indication to the FRMCS Users whose permission to talk has been changed due to that.
+
+#### 9.7.5.4 Post-conditions
+
+Permission to talk is granted to the selected FRMCS Users.
+
+### 9.7.5.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------|
+| [R-9.7.5-001] | Multiuser Talker Control shall keep track of FRMCS Users with permission to talk and FRMCS Users requesting to talk. | A | 22.179 | [R-6.2.3.7.3-004]<br>[R-6.2.3.7.4.1-002] |
+| [R-9.7.5-002] | Multiuser Control shall use a set of criteria provided by the communication application, like priorities, identities, etc. to manage the requests automatically. | A | 22.179 | [R-6.2.3.7.4.1-003] |
+| [R-9.7.5-003] | Based on its functional identity an entitled FRMCS User shall be able to select and de-select simultaneous talkers. | A | 22.179 | Partly covered by participant type [R-6.2.3.7.4.1-002]<br>[R-6.2.3.7.4.1-006] override mechanism by authorized participant. |
+| [R-9.7.5-004] | If the number of FRMCS Users with permission to talk does not exceed the maximum number of simultaneous talkers, the Multiuser Talker Control service shall grant automatically the permission to additional requestors. | A | 22.179 | [R-6.2.3.7.4.1-001]<br>[R-6.2.3.7.4.1-004] |
+| [R-9.7.5-005] | If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers:<br>the Multiuser Talker Control shall decide based on certain criteria, like priorities, functional identity, etc. who will keep the right to talk and who will be granted the permission to talk. Affected FRMCS Users shall be informed of their changed permission to talk. | A | 22.179 | [R-6.2.3.7.4.1-001]<br>[R-6.2.3.7.4.1-004] |
+| [R-9.7.5-006] | If the number of FRMCS Users with permission to talk exceeds the maximum number of simultaneous talkers:<br>the Multiuser Talker Control service shall present an entitled FRMCS User is monitoring the communication, with the list of simultaneous talkers and the list of pending requests to decides who will keep the right to speak, who will be granted the permission to talk. Affected FRMCS Users shall be informed of their changed | A | 22.179 | [R-6.2.3.7.4.1-005]<br>[R-6.2.3.7.4.1-006] |
+
+| | | | | |
+|--|---------------------|--|--|--|
+| | permission to talk. | | | |
+|--|---------------------|--|--|--|
+
+## 9.7.6 Use case: Revoke permission to talk
+
+### 9.7.6.1 Description
+
+There are occasions in the railway environment where it is needed to mitigate the risk of miscommunication. Use cases include, for example:
+
+- Emergency communication
+- Shunting communication
+- Trackside worker communication
+
+The system shall be able to limit the number of simultaneous talkers in a voice communication.
+
+The list of FRMCS Users with permission to talk shall be available to the Multiuser Talker Control service.
+
+An entitled FRMCS User who monitors the progress of the communication shall be able at any point to revoke the permission to talk of any of the FRMCS Users with permission to talk. Automatic revocation of talkers in case the maximum number of simultaneous talkers has been reached and a request to talk is received, is included in the use case above.
+
+### 9.7.6.2 Pre-conditions
+
+A number of FRMCS Users are in an active voice communication for which Multiuser Talker Control is enabled and have been granted permission to talk.
+
+An entitled FRMCS User is monitoring the progress of the communication and shall be able at any point to revoke the permission to talk of any of the FRMCS Users currently with permission to talk.
+
+### 9.7.6.3 Service flows
+
+The Multiuser Talker Control service presents a list of simultaneous talkers to an entitled FRMCS User, who decides who will not keep the right to speak by de-selecting the corresponding FRMCS User.
+
+The Multiuser Talker Control service configures the system accordingly.
+
+The Multiuser Talker Control service sends an indication to the FRMCS Users who have modified their situation with respects to the permission to talk.
+
+The FRMCS User is no longer able to talk after the entitled FRMCS User has changed the permission.
+
+### 9.7.6.4 Post-conditions
+
+Permission to talk is revoked for the de-selected FRMCS Users.
+
+### 9.7.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------|
+| [R-9.7.6-001] | An entitled FRMCS User who monitors the progress of the communication shall be able at any point to revoke the permission to talk of any of the FRMCS Users currently with permission to talk. | A | 22.179 | [R-6.2.3.7.4.1-008] |
+| [R-9.7.6-002] | The FRMCS User who's permission to talk has been revoked, shall no longer be able to talk after the entitled FRMCS User has revoked the permission. | A | 22.179 | [R-6.2.3.7.4.1-004] |
+
+## 9.8 Authorisation of communication
+
+### 9.8.1 Introduction
+
+In this chapter the use cases related to authorisation of communication are described, the following use cases are identified:
+
+- Permit / deny communication
+
+### 9.8.2 Use case: Permit / deny communication
+
+#### 9.8.2.1 Description
+
+The purpose of the authorisation function is to allow the network operator to control and regulate communications in order to avoid disruption/distraction to the users (for example Drivers during voice communication) and preventing unauthorised communication and to minimise network load.
+
+The FRMCS System may therefore restrict communication based on a configurable access matrix related to the FRMCS subscriber identity, the FRMCS Functional Identity of the equipment, the FRMCS User Identity, the FRMCS Functional Identity of the FRMCS Users considering the source and destination address.
+
+Decision to permit or deny communication is based on full or subparts of the FRMCS Functional Identity of the FRMCS Users. An example of a full FRMCS Functional Identity of an FRMCS User is a specific driver on a specific train. An example of a subpart of an FRMCS Functional Identity of an FRMCS User is all train drivers.
+
+#### 9.8.2.2 Pre-conditions
+
+An FRMCS User attempts to establish a communication.
+
+#### 9.8.2.3 Service flows
+
+Upon an attempt to establish a communication, the FRMCS System checks if the source FRMCS User address is allowed to invite the destination FRMCS User address. The FRMCS System shall consider for the verification process the source and destination FRMCS User address.
+
+If multiple identities are simultaneously active to a FRMCS User, the following order shall be applied to determine the authorisation of the communication establishment:
+
+- Functional identities or subparts of functional identities related to the FRMCS User
+- FRMCS User Identity
+- FRMCS functional identities related to the equipment
+- FRMCS subscriber identity
+
+If the FRMCS User is allowed to establish the communication, the FRMCS System proceeds the communication setup.
+
+If the FRMCS User is not allowed establish the communication, the FRMCS System shall reject the attempt including the reason of the rejection.
+
+#### 9.8.2.4 Post-conditions
+
+Either the communication has been established or the FRMCS User has been informed about the denial of the call attempt.
+
+#### 9.8.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.8.2-001] | The FRMCS System shall be able to control and restrict the establishment of communication in order to avoid disruption/distraction of the FRMCS Users (for example Drivers). | A | TS 22.280 | TS 22.280 sub-clause 6.7.3 Requirement [R-6.7.3-007a] |
+| [R-9.8.2-002] | The FRMCS System shall be able to restrict communication based on related to the FRMCS subscriber identity, the FRMCS Equipment Identity, the FRMCS Functional Identity of the equipment, the FRMCS User Identity, the FRMCS Functional Identity or subparts of the FRMCS Functional Identity of the FRMCS Users considering the source and destination address. | A | TS 22.280 | TS 22.280 Requirements [R-5.17-001] for group calls and [R-6.7.2-002] for private calls. Covered by [R-5.9a-020] and [R-5.9a-021] for functional identities. Not covered for subparts of functional identities. |
+| [R-9.8.2-003] | The FRMCS System shall inform the FRMCS User in case the FRMCS User is not allowed to establish a communication. | A | TS 22.280 | Implicit in many requirements. |
+
+### 9.9 Authorisation of application
+
+#### 9.9.1 Introduction
+
+In this chapter the use cases related to authorisation of application are described, the following use case is identified
+
+- Enabling/Disabling applications
+
+- Robust mission critical group communication services
+- Enabling/Disabling communication privileges per FRMCS User based on identities/talker status
+
+## 9.9.2 Use case: Enabling/Disabling applications
+
+### 9.9.2.1 Description
+
+The FRMCS System shall allow the network operators to control the use of FRMCS Applications in order to avoid disruption/distraction to the FRMCS Users (for example Drivers), preventing unauthorised usage according to his Role.
+
+The FRMCS System shall therefore be able to enable / disable FRMCS Applications for a FRMCS User depending on subscriber identity, the functional identity of the FRMCS Equipment, the FRMCS User Identity or the functional identity/ies of the FRMCS User. Also, context based criteria like location and other conditions are to be taken into account.
+
+### 9.9.2.2 Pre-conditions
+
+The FRMCS User equipment is powered on and the FRMCS Application on the FRMCS User equipment has started.
+
+### 9.9.2.3 Service flows
+
+#### Power-on
+
+After powering on the FRMCS Equipment and start of the FRMCS Application on the FRMCS Equipment, the FRMCS System enables the FRMCS Application(s) on the FRMCS Equipment according to the Role related to the FRMCS subscriber identity.
+
+#### Change of registration status
+
+Upon a change in registration status by registration / deregistration to / from a functional identity, change of a functional identity, user login /logout to / from the FRMCS System, the FRMCS System enables / disables applications.
+
+If multiple identities are active, the following order is used to determine the correct state:
+
+- FRMCS functional identities related to the FRMCS User
+- FRMCS User identity
+- FRMCS functional Identities related to the FRMCS Equipment
+- FRMCS subscriber identity
+
+If a FRMCS User has registered to multiple functional identities, the FRMCS User is authorised to use all applicable FRMCS Applications related to the different FRMCS functional identities.
+
+If an FRMCS Application is relying on other FRMCS Applications, enabling of all required FRMCS Applications is managed by the FRMCS System.
+
+Only authorised FRMCS Applications shall be presented to the FRMCS User.
+
+#### Change of location
+
+If the FRMCS User enters a certain area, the FRMCS System may prevent the use of FRMCS Application(s) which had been authorised previously.
+
+If the FRMCS User enters a certain area, the FRMCS System may enable the use of FRMCS Application(s) which had not been authorised previously.
+
+If a FRMCS Application is relying on other FRMCS Applications, enabling of all required FRMCS Applications is managed by the FRMCS System.
+
+Only authorised FRMCS Applications shall be presented to the FRMCS User.
+
+#### **9.9.2.4 Post-conditions**
+
+The FRMCS User has access to all authorised FRMCS Applications.
+
+### 9.9.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| [R-9.9.2-001] | The FRMCS System shall allow the network operator to control the use of FRMCS Applications in order to avoid disruption/distraction to the FRMCS Users (for example Drivers), preventing unauthorised usage according to his Role. | A | TS 22.280, requirement [R-6.6.4.2-002]<br>[R-6.7.3-007]<br>[R-6.7.3-007a] | Covered for both group and private communications with CR 0053 to TS 22.280 |
+| [R-9.9.2-002] | The FRMCS System shall be able to enable / disable FRMCS Applications for a FRMCS User depending on subscriber identity, the functional identity of the FRMCS Equipment, the FRMCS User Identity or the functional identity/ies of the FRMCS User. The FRMCS System shall also be able to take context-based criteria like location, speed, direction of travel and other conditions be taken into account. | A | TS 22.280, requirement [R-6.6.4.2-002] | Covered for group communication with CR 0053 to TS 22.280 |
+| [R-9.9.2-003] | After powering on the FRMCS Equipment and start of the FRMCS Application on the FRMCS Equipment, the FRMCS System shall enable the FRMCS Application(s) on the FRMCS Equipment according to the Role related to the FRMCS subscriber identity. | A | Not applicable | This is related to implementation and is outside 3GPP scope. |
+| [R-9.9.2-004] | Upon a change in registration status by registration / deregistration to / from a functional identity, a change of a functional identity, user login /logout to / from the FRMCS System, the FRMCS System shall be able to enable / disable applications. | A | [TS 22.280, requirement [R-5.9a-001] | |
+| [R-9.9.2-005] | The FRMCS System shall allow the operator to configure the order in which the FRMCS functional Identities related to the FRMCS User identity FRMCS functional Identities related to the FRMCS Equipment FRMCS subscriber identity are evaluated to determine with the set of application authorised for use | A | Not covered | TS 22.280: only authorisation based on MCX Service User ID is supported. |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.9.2-006] | If a FRMCS User has registered to multiple functional identities, the FRMCS User shall be authorised to use all applicable FRMCS Applications related to the different FRMCS functional identities. | A | Implicitly covered | This requirement is implicitly covered.<br>Chapter 5.9a.1 in TS 22.280 states that "The activation of the functional alias(es) will take place after the user has signed in to the MCX Service using the MCX User ID."<br>So the user is already authorized to use the services when functional ID is activated. |
+| [R-9.9.2-007] | If the FRMCS User enters a certain area, the FRMCS System shall prevent the use of FRMCS Application(s) which had been authorised previously. | A | Covered by [R-5.9a-015] in TS 22.280 | |
+| [R-9.9.2-008] | If the FRMCS User enters a certain area, the FRMCS System shall enable the use of FRMCS Application(s) which had not been authorised previously. | A | Covered by [R-5.9a-015] in TS 22.280 | |
+| [R-9.9.2-009] | If a FRMCS Application is relying on other FRMCS Applications, enabling of all required FRMCS Applications shall be managed by the FRMCS System. | A | Not applicable | This requirement should be covered in implementation. |
+
+### 9.9.3 Use case: Robust mission critical group communication services
+
+#### 9.9.3.1 Description
+
+For reliable railway services, conventional way is to use dualization methodology. Most of railway services are based on on-network communication, which is supported by base station and core networks under 3GPP standard. However, when disaster happens so that the communication infrastructure is not feasible, railway service based on the communication infrastructure cannot be maintained any more. From 3GPP Rel. 12, device-to-device communications has been considered to be supported not only in the transport layer but also in the application layer. In addition, interworking of FRMCS System with legacy systems including GSM-R and TRS is expected to be supported in Rel. 15. As a consequence, off-network and legacy systems will become feasible for group communication services in 3GPP technology. Therefore, by considering not only off-network but also legacy systems, reliability of mission critical group communication service in the on-network can be enhanced. Figure 9.9-1 depicts a required transformation of group communication service mode.
+
+#### 9.9.3.2 Pre-conditions
+
+FRMCS Equipment for train driver, customer service staff, and train operations staff support device to device communications in the perspective of transport layer.
+
+FRMCS Equipment for train driver, customer service staff, and train operations staff support on-network, off-network group communication services in the perspective of applications layer.
+
+
+
+The diagram illustrates the transformation of group communication service mode. It is divided into two horizontal sections by a large blue downward-pointing arrow. The top section shows a 'Customer Service Staff or Train Ops. Staff' box on the left and a 'Driver' box on the right, connected by a double-headed arrow labeled 'Group call service (via on-network)'. A thick blue curved line arches over these boxes. The bottom section shows the same 'Customer Service Staff or Train Ops. Staff' box on the left and 'Driver' box on the right, connected by a double-headed arrow labeled 'Group call service (via off-network or legacy network)'. A thick blue horizontal line is at the bottom of this section. The text 'Transformation of group call service mode by switching underlying communication network' is positioned to the right of the central arrow.
+
+Diagram illustrating the transformation of group communication service mode from on-network to off-network or legacy network.
+
+**Figure 9.9.3.2-1. Transformation of group communication service mode**
+
+### 9.9.3.3 Service Flows
+
+1. After initial disaster happens, emergency message (including voice or data) delivery service based on on-network group communication among train driver, customer service staff, or train operations staff have been preceded without any problem.
+2. Disaster becomes worse, and associated communication infrastructure is destroyed and is not usable anymore.
+3. Transformation of on-network group communication service into off-network or legacy network-based group communication service is accomplished among group members for maintaining the group communication services even in the worse disaster.
+
+### 9.9.1.4 Post-conditions
+
+Off-network or legacy network-based group communication among train driver, customer service staff, or train operations staff is activated and group communication service is maintained normally.
+
+### 9.9.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.9.3-001] | FRMCS Equipment shall support on-network based group communications. | A/T | TS 22.179<br>V.14.2.0 | Support |
+| [R-9.9.3-002] | FRMCS Equipment shall support off-network based group communications. | A/T | TS 22.179<br>V.14.2.0 | Support |
+| [R-9.9.3-003] | FRMCS Equipment should support legacy network- based group communications optionally. | A/T | N/A | Implementation option. |
+| [R-9.9.3-004] | FRMCS System shall provide a mechanism in the application layer to transform on-network based group communication into off-network based group communication. | A | TS 22.280 | Automatic and manual switching from on-network service to off-network service are supported.<br>[R-7.13-004] Ongoing MCX service communication interruption are minimized when switching from on-network to -off-network services. |
+| [R-9.9.3-005] | FRMCS System shall provide a mechanism in the application layer to transform on-network based group communication into legacy networkbased group communication. | A | 22.179<br>22.280 | TS 22.179<br>Project 25:<br>subclause 6.18.3.2.<br>TETRA: subclause 6.18.3.3.<br>TIA-603 systems:<br>subcla use 6.18.3.4.<br>GSM-R: 6.18.4.<br>TS 22.280<br>GSM-R: subclause 6.17.3.1. |
+
+### 9.9.3a Use case: Enabling/Disabling communication privileges per FRMCS User based on identities/talker status
+
+#### 9.9.3a.1 Description
+
+In addition to enable the control of use of FRMCS Applications, the FRMCS System shall allow the network operators and/or the FRMCS Users to control the use of FRMCS Applications with communication privileges per FRMCS User.
+
+FRMCS User authorization shall be based on the FRMCS User Identity and/or the functional identity/ies of the FRMCS User, the functional identity of the FRMCS Equipment, and/or the talker status for ongoing communications.
+
+Regarding this last parameter (i.e., communication privileges based on talker status), as an example, if an FRMCS User A who is involved as a listener in a voice communication, and FRMCS User B is talking in this voice communication, FRMCS User A is allowed or not to put on hold/leave/terminate the call, and/or to kick out FRMCS User B based on talker status of both FRMCS Users A and B.
+
+### 9.9.3a.2 Pre-conditions
+
+The FRMCS User equipment is powered on and the FRMCS Application on the FRMCS User equipment has started.
+
+### 9.9.3a.3 Service flows
+
+#### **Change of FRMCS User authentication and authorisation status**
+
+Upon a change in FRMCS User authentication and authorisation status, the FRMCS System triggers a change of communication privileges (e.g., FRMCS User profiles) for that particular FRMCS User.
+
+The following use cases are concerned:
+
+- An FRMCS User is authorised or not to initiate a private or group voice, video or data communication;
+- An FRMCS User is authorised or not to put a group voice communication on hold;
+- An FRMCS User is authorised or not to leave a group voice communication;
+- An FRMCS User is authorised or not to terminate a private or group voice communication;
+- An FRMCS User is authorised or not to merge Railway Emergency Alerts;
+- An FRMCS User is authorised or not to kick out another FRMCS User from a group voice communication;
+- An FRMCS User is authorised or not to invite another FRMCS User to a group voice communication.
+
+#### **Change of FRMCS User registration status**
+
+Upon a change in registration status by registration / deregistration to / from a functional identity, the FRMCS System triggers a change of communication privileges (e.g., FRMCS User profiles) for that particular FRMCS User.
+
+The following use cases are concerned:
+
+- An FRMCS User is authorised or not to initiate a private or group voice, video or data communication;
+- An FRMCS User is authorised or not to put a group voice communication on hold;
+- An FRMCS User is authorised or not to leave a group voice communication;
+- An FRMCS User is authorised or not to terminate a private or group voice communication;
+- An FRMCS User is authorised or not to merge Railway Emergency Alerts;
+- An FRMCS User is authorised or not to kick out another FRMCS User from a group voice communication;
+- An FRMCS User is authorised or not to invite another FRMCS User to a group voice communication.
+
+#### **Change of FRMCS User's talker status during ongoing group voice communication**
+
+Upon a change of talker status when an FRMCS User is involved in an ongoing group voice communication (i.e., the current talker becomes listener and vice-versa), the FRMCS System may be able to trigger a change of communication privileges (e.g., FRMCS User profiles) for all FRMCS Users affiliated to that group.
+
+The following use cases are concerned:
+
+- An FRMCS User is authorised or not to put an ongoing group voice communication on hold;
+- An FRMCS User is authorised or not to leave an ongoing group voice communication;
+- An FRMCS User is authorised or not to terminate an ongoing group voice communication;
+
+- An FRMCS User is authorised or not to merge Railway Emergency Alerts;
+- An FRMCS User is authorised or not to kick out another FRMCS User from an ongoing group voice communication;
+- An FRMCS User is authorised or not to invite another FRMCS User to an ongoing group voice communication.
+
+#### 9.9.3a.4 Post-conditions
+
+The FRMCS User is authorized or not to use FRMCS Applications.
+
+### 9.9.3a.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.9.2-001] | When an FRMCS User performs MCX authentication and authorisation, the FRMCS System shall be able to trigger a change of communication privileges for that particular FRMCS User. | A | Partly covered (refer to communication privileges below) | <p>Identification of the targeted user of the communication privilege status change: partly covered by MCX authentication and authorisation mechanism (MC ID only, no FA).</p> <p>Change of user profiles on MCX authentication and authorisation: covered → MCX User Service Authorization is the function that validates whether or not a MCX user has the authority to access certain MCX services.</p> |
+| [R-9.9.2-002] | When an FRMCS User activates or deactivates Functional Alias(es), the FRMCS System shall be able to trigger a change of communication privileges for that particular FRMCS User. | A | Partly covered (refer to communication privileges below) | <p>Identification of the targeted user of the communication privilege status change: covered by FA mechanism (MC ID + list of FA(s)).</p> <p>Change of user profiles on FA activation or creation of new profiles for FA: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+| [R-9.9.2-003] | When the floor is granted or released for a particular FRMCS User (including multi-talker floor control), the FRMCS System shall be able to trigger a change of communication privileges for all FRMCS Users <u>affiliated to that group</u> . | A | Partly covered | <p>Identification of the targeted users of the communication privilege status change: Partly covered. Only MCPTT ID(s) and list of FA(s) of the requester(s) (floor control request & multi-talker) are known by the system.<br/><b>Editor's note: CR is needed</b></p> <p>Change of user profiles when floor granted/released: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+| [R-9.9.2-004] | The FRMCS System shall support Communication privilege as (1) authorisation to put a group voice communication on hold. | A | Covered | <p>Put a group voice communication on hold: covered by the affiliation mechanism which is considered sufficient to mimic the desired behaviour.</p> <p>Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.9.2-005] | The FRMCS System shall support Communication privilege as (2) authorisation to leave a group voice communication. | A | Covered | <p>Leave a group voice communication: covered by the affiliation mechanism which is considered sufficient to mimic the desired behaviour.</p> <p>Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+| [R-9.9.2-006] | The FRMCS System shall support Communication privilege as (3) authorisation to terminate a group voice communication. | A | Not covered | <p>Terminate a group voice communication: strictly performed by the system.</p> <p>Authorisation mechanism: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+| [R-9.9.2-007] | The FRMCS System shall support Communication privilege as (4) authorisation to merge Railway Emergency Alerts. | A | [Need analysis] | [Need analysis – finalize potential requirements for Merging of Railway Emergency Alerts first] |
+| [R-9.9.2-008] | The FRMCS System shall support Communication privilege as (5) authorisation to kick out another FRMCS User from a group voice communication. | A | Covered by 22.280 | <p>Kick out another user: covered by remote change of affiliation (mandatory mode) 22.280 6.4.6.1.</p> <p>Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+| [R-9.9.2-009] | The FRMCS System shall support Communication privilege as (6) authorisation to invite another FRMCS User to a group voice communication. | A | Covered by 22.280 | <p>Invite a user to join: covered by remote change of affiliation (negotiated mode) 22.280 6.4.6.2.</p> <p>Authorisation mechanism: authorization of changing affiliation based on registration status by registration / deregistration to / from a functional identity or by talker status: not covered.<br/><b>Editor's note: CR is needed</b></p> |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.9.2-010] | The FRMCS System shall support Communication privilege as (7) authorisation to initiate private voice, video or data communication. | A | Covered by 22.280 | Initiate private voice, video or data communication: covered by MC private call request mechanism.<br><br>Authorisation mechanism: covered by authorisation check based on user profile. |
+| [R-9.9.2-011] | The FRMCS System shall support Communication privilege as (8) authorisation to initiate group voice, video or data communication. | A | Covered by 22.280 | Initiate group voice, video or data communication: covered by group call request mechanism.<br><br>Authorisation mechanism: covered by authorisation check based on user profile. |
+
+## 9.10 Sharing FRMCS Equipment by FRMCS Users
+
+### 9.10.1 Description
+
+Commonly, FRMCS Users may share FRMCS Equipment, e.g. a trainborne UE. To use the shared equipment securely, it is needed to identify the user for the equipment.
+
+### 9.10.2 Pre-conditions
+
+A train driver is in a train.
+
+The train driver has an identification card.
+
+### 9.10.3 Service Flows
+
+The train driver wants to use a trainborne UE to make communication to train control centre.
+
+The train driver puts his/her identification card in the trainborne UE to identify himself/herself. In this case, the identification card is an example. It can be a type of ID number, finger-print, etc. instead.
+
+The trainborne UE reads the identification information from the card and requests authentication to FRMCS security server.
+
+FRMCS security server confirms the information and replies the authentication information to the trainborne UE.
+
+FRMCS registers the train driver as the user of the trainborne UE to relay a call for the train driver to the trainborne UE.
+
+The trainborne UE indicates readiness to use for the train driver.
+
+### 9.10.4 Post-conditions
+
+The train driver makes a call to the train control centre.
+
+The train driver receives a call using the trainborne UE that is relayed by FRMCS.
+
+## 9.10.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------|
+| [R-9.10-001] | The FRMCS System shall be able to provide a mean to identify a FRMCS User (for example, the train driver). | A | TS 22.280 | TS 22.280 sub-clause 5.9a and covered by many requirements in MCX |
+| [R-9.10-002] | The FRMCS System shall be able to provide a mapping between the FRMCS User identification information and FRMCS Equipment in order to route communication. | A | TS 22.280 | Covered by many requirements in MCX |
+| [R-9.10-003] | The FRMCS System shall be able to provide communication routing based on the mapping information. | A | TS 22.280 | Covered by many requirements in MCX |
+| [R-9.10-004] | The FRMCS System should provide functions for the shared FRMCS Equipment to get identification information from the FRMCS User who wants to use the equipment. | A | TS 22.280 | Covered by many requirements in MCX |
+
+## 9.11 FRMCS naming authority
+
+### 9.11.1 Description
+
+The FRMCS Naming Authority (NA) is a registry service provided by FRMCS System to facilitate the handling of various namespaces, number spaces or other information sets needed to support FRMCS services.
+
+For example, FRMCS User identification requires a registry to manage the identification information which shall not be duplicated during its registration process.
+
+### 9.11.2 Pre-conditions
+
+A new train driver is registered as a new user of FRMCS.
+
+A new trainborne UE is installed in a train.
+
+### 9.11.3 Service Flows
+
+The new train driver wants to use FRMCS System.
+
+The train driver makes a request to register the user identification information in FRMCS with his/her finger-print as an identification method.
+
+The FRMCS checks the duplication of the user identification under the guidance of FRMCS NA and registers the user identification information in its registry.
+
+The train driver installs a new trainborne UE in the train. During the installation process, the trainborne UE is registered as a new FRMCS UE in FRMCS registry under the guidance of FRMCS NA to avoid duplication of FRMCS UE address.
+
+### 9.11.4 Post-conditions
+
+The train driver is registered as a new user in FRMCS System without duplication of user identification information.
+
+The trainborne UE is installed in the train and is registered as a new FRMCS UE in FRMCS System without duplication of UE address.
+
+### 9.11.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------|-------------------------|-------------------|-------------------------------|
+| [R-9.11-001] | The FRMCS System shall be able to avoid duplication of identities. | A | 22.280 | covered by 22.280 [R-6.9-002] |
+
+## 9.12 Wayside-Centric Automatic Train Control
+
+### 9.12.1 Description
+
+Signalling block system, which is a fundamental factor in the perspective of train control, enables the safe and efficient operation of railways to avoid collisions between trains. The signalling block system basically keeps a train away from entering the block occupied by the other train. It is commonly known that moving block system compared to fixed block system. As shown in Figure 9.12-1, the train in moving block system can approach the leading train more closely.
+
+
+
+Figure 9.12-1: Examples of various railways block systems. The diagram illustrates three scenarios of train control on a single-track line. In the top scenario (Fixed Block System), a train is approaching a red signal from the left, and another train is ahead of it. The signals are connected by orange lines, indicating fixed blocks. In the middle scenario (Moving Block System), the train is closer to the red signal, and the orange line representing the block boundary is shorter. In the bottom scenario (Moving Block System), the train is even closer to the red signal, and the orange line is the shortest, showing that the train can approach the leading train more closely in a moving block system.
+
+Figure 9.12-1 Examples of various railways block systems
+
+One way to realize the moving block system is that a centralized server communicates with trains and manages the moving block based on the positions of the trains. The On-board Automatic Train Protection (OATP), which is on the train, report the position of the train to the Wayside Automatic Train Protection (WATP), and the WATP decides and provide the movement authority of the train to the OATP. The train controls itself based on the movement authority, and trigger brake when it approaches the border of its authorized moving area.
+
+### 9.12.2 Pre-conditions
+
+1. The user equipment dedicated to train control gets power-on, and registers to the train control system.
+2. WATPs are located in the Packet Data Network (PDN), and each train knows the nearby WATP which can offer a movement authority and make it move.
+3. The user equipment establishes a connection through the 3GPP network for transporting periodical data between WATP and OATP.
+
+### 9.12.3 Service flows
+
+1. The OATP periodically report its position to the serving WATP.
+2. The WATP periodically provide movement authority to the OATP
+3. The train accelerates, or triggers brake based on the last received movement authority. It moves till the position that it is authorized to move, and stops if it reaches to the border of the authorized area.
+
+### 9.12.4 Post-conditions
+
+The train triggers emergency brake and stops immediately if the connection is lost and data is not received for a certain time from WATP.
+
+### 9.12.5 Potential requirements and gap analysis
+
+| Requirement Reference Number | Requirement text | Application/ Transport | SA1 spec covering | Comments |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------|
+| [9.12-001] | The FRMCS System shall provide a mechanism for a train to autonomously discover an assigned application server which can offer movement authority. | A/T | 22.280 | This requirement is covered by the combination of functional alias, affiliation mechanism, and IP connectivity. |
+| [9.12-002] | Train control data shall be able to be transported with the highest priority. | T | 22.280 | Covered by 22.280 [R-6.8.7.2-001], [R-6.8.7.2-010] and [R-5.1.7-002]. |
+
+## 9.13 Autonomous Train Control and Operation
+
+### 9.13.1 Description
+
+In legacy train control systems, trains typically decide its movement by interacting with trackside devices (e.g. track circuits, balise, radio block system) or communicating with a trackside server. If a train can autonomously figure out the positions of the nearby trains and decide its movement authority, the transport capacity of the railway will be enhanced. In the autonomous train control system whose service concept is aligned to the eV2X service, trains share its position by exchanging the information without any centralized server, and each train decides how far it can be authorized to move based on the position information. It is expected that main application area will be mass transportation such as subway.
+
+
+
+Figure 9.13.-1: An example of autonomous train control scenario. The diagram shows two states of a railway track. On the left, two trains are on a track with a switch. Above the track, there are two signal boxes connected by a double-headed arrow. Below the signal boxes, there are four antennas. Dashed lines connect the antennas to the trains. On the right, the trains have moved past the switch. The signal boxes and antennas are still present. Dashed lines connect the antennas to the trains, and a dashed line also connects the trains to the signal boxes. The track has a switch that leads to a lower level.
+
+Figure 9.13.-1 An example of autonomous train control scenario
+
+### 9.13.2 Pre-conditions
+
+1. Trains know the overall schedule, and the user equipment of each train is connected to the user equipment of the other trains operating at the same time.
+2. A user equipment of each train is able to establish a connection with the object Controller for the nearby point machine.
+
+### 9.13.3 Service Flows
+
+1. A train gets started and try registration to the currently operating trains. The registration message includes the position of the train.
+2. The train gets the responses of the registration from the other trains and estimates the positions of the trains.
+3. The train decides its movement authority based on the position information and starts moving.
+4. The train positions in the corresponding areas are shared through multicasting.
+5. Based on the periodically updated information, each train updates its movement authority and conduct train control based on it.
+6. If needed, the train connects to the nearby point machine and sends switch command.
+
+### 9.13.4 Post-conditions
+
+The autonomous train control is achieved by activating movement authority for each train or activating object Controller for nearby point machine.
+
+### 9.13.5 Potential requirements and gap analysis
+
+| Requirement Reference Number | Requirement text | Application/ Transport | SA1 spec covering | Comments |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [9.13-001] | The 3GPP network shall provide a mechanism using on-network communications to establish a bearer from a user equipment to the other user equipment | A | 22.280 | The requirement of [R-5.9a-002] "The MC User shall be reached by its functional alias(es) from within the MCX Service system where the functional alias was activated." Includes point to point MCData transport service. |
+| [9.13-002] | The 3GPP network shall provide an efficient way to disseminate data to multiple FRMCS UEs for train control. | A/T | 22.282<br>22.280 | The requirements of [R-6.2.2.1-002a] and [R-6.2.2.1-002b] of 22.282 include a dissemination of data to multiple receiving users. The efficient way of the dissemination is covered by functional alias in 5.9a requirements of 22.280. |
+| [9.13-003] | The 3GPP network shall be able to multicast train control data originated from one FRMCS UE to the other FRMCS UE. | A/T | 22.282 | The requirements of [R-6.2.2.1-002a] and [R-6.2.2.1-002b] include a multicast of data to chosen receiving users. |
+| [9.13-004] | The FRMCS System shall provide a mechanism to discover feasible objects for point machine. | A | 22.280 | Covered by [R-5.9a-002] "The MCX User shall be reachable by its functional alias(es) from within the MCX Service system where the functional alias was activated." |
+
+## 9.14 Virtual Coupling
+
+### 9.14.1 Description
+
+One of the important missions that the future railway service should achieve is to increase its transport capacity. A straight-forward solution is to minimize the distance between successive trains so that train interval is reduced. It is difficult to do so in a legacy train control system, because the successive trains need to have distance as much as a safety margin, which should be larger than the full braking distance.
+
+
+
+The diagram shows two blue trains on a track. Above the track is a long blue double-headed arrow representing a communication channel. Four vertical lines with antenna icons connect this channel to the trains. The first train on the left has a yellow arrow pointing right. The second train on the right has a yellow arrow pointing right. A dashed blue line connects the first train to the second train, and a solid orange line connects the second train back to the first train, representing the exchange of control information.
+
+Diagram illustrating the sharing of acceleration and braking control information between two trains to shorten the safety margin.
+
+**Figure 9.14-1 Sharing acceleration and braking control information to shorten safety margin**
+
+This safety margin can be further shortened if the successive trains share control information (acceleration and braking) and apply it to its own train control. As shown in Figure 9.14.1, the safety margin can be shortened if the following train immediately knows that the leading train starts braking and also triggers braking. This is the fundamental principle and the main purpose of virtual coupling. Figure 9.14.2 shows the basic concept of the virtual coupling scenario. Multiple trains which are in close distance move together *as they are physically coupled*. As the distance between two trains gets smaller, the control information of a train should be delivered to the other in shorter time.
+
+
+
+The diagram shows three blue trains on a track, each with a yellow arrow pointing right. Above the track is a long blue double-headed arrow representing a communication channel. Four vertical lines with antenna icons connect this channel to the trains. A large blue padlock icon is positioned above the middle train, symbolizing the 'virtual coupling' of the trains.
+
+Diagram illustrating the concept of virtual coupling scenario with three trains.
+
+**Figure 9.14-2 The concept of virtual coupling scenario**
+
+### 9.14.2. Pre-conditions
+
+1. The leading and following trains in operation recognize each other and have just got configured to be coupled virtually.
+2. The user equipment for train control support device to device communications in the perspective of transport layer.
+
+
+
+Figure 9.14-3: Overall procedure of virtual coupling. The diagram shows three stages of two trains (leading and following) on a track. In the first stage, the trains are far apart, connected by a dashed orange line representing a 3GPP network connection. In the second stage, the trains are closer, and the connection is still dashed orange. In the third stage, the trains are very close, and the connection is a solid blue line, indicating a switch to a PC5 interface. A yellow circle with a lock icon is shown between the trains in the third stage, representing a safety barrier or secure connection.
+
+Figure 9.14-3 Overall procedure of virtual coupling
+
+### 9.14.3 Service Flows
+
+1. The following train begins to approach to the leading train by exchanging the information about their position. The two trains, which are far enough to allow a certain amount of end-to-end latency, are initially connected through the 3GPP network.
+2. As the following train approaches to the leading train, they start exchanging the information about movement control and each train then controls itself while considering the control of the other train. The two trains, which are still far enough to allow a certain amount of end-to-end latency, keep the connection through the 3GPP network.
+3. As the following train further approaches to the leading train, the safe braking distance gets shorter and they are required to have a connection of which end-to-end latency is very short for delicate train control. At this moment, they seamlessly switch the connection from the 3GPP network to PC5 interface
+
+### 9.14.4 Post-conditions
+
+For safety train operation, integrity needs to be checked for train control information delivery in the perspective of application or transport layer. Any error on integrity check shall be immediately reported to the train control application.
+
+## 9.14.5 Potential requirements and gap analysis
+
+| Requirement Reference Number | Requirement text | Application/ Transport | SA1 spec covering | Comments |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [9.14-001] | An On-board FRMCS UE for automatic train control shall be able to communicate through off-network up to 3km in the line of sight channel environment. | T | 22.289 | This requirement is covered by section 5.2.2 of TS22.289 |
+| [9.14-002] | Integrity protection shall be provided for each data transfer between FRMCS UEs for train control | A/T | 22.280 | Covered by [R-5.12-001] The MCX Service shall provide a means to support the confidentiality and integrity of all user traffic and signalling at the application layer." |
+| [9.14-003] | The 3GPP system shall support service continuity between on-network based connection and off-network based connection. | A/T | 22.280 | [R-7.11-001] An MCX UE shall be capable of utilizing off-network MCX Service communications and on-network MCX Service communications at the same time. [R-7.13-004] On-going MCX service communication interruption are minimized when switching from on-network to -off-network services. |
+| [9.14-004] | FRMCS UEs for train control shall communicate through off-network, where the FRMCS UEs' relative speed is less than 40km/h. | T | 22.289 | This requirement is covered by section 5.2.2 of TS22.289 |
+
+## 9.15 Composite-based train operation
+
+### 9.15.1 Description
+
+This use case considers the composition and decomposition of trains or tractions. One is the case, where two autonomous trains / traction (train A and train B) are conducted as one composition (Train C). The other case describes the decomposition of a train set (Train C) into autonomous train A and train B. For these scenarios, specific FRMCS Equipment Identity management need to be provided by the FRMCS System.
+
+## 9.15.2 Pre-conditions
+
+Train A and Train B share information for train operation such as position and velocity profile.
+
+## 9.15.3 Service Flows
+
+### Train composition
+
+1. Train/traction A and Train/traction B are autonomous trains and moving on different tracks.
+2. Train/traction A and the train/traction B are put together into one train composition using the same railway.
+3. Consequently, the different FRMCS UE identities of train/traction A and train/traction B are changed into common FRMCS UE identity composite train C/traction C.
+
+### Train decomposition
+
+1. Train/traction C which is the composition of train/traction A and train/traction B is moving along the railway.
+2. Based on the train routing i.e. different destination of train/traction A and train/traction B of train/traction A and train/traction B uses two different railways.
+
+Consequently, the FRMCS UE identity of train/traction C is decomposed again into FRMCS UE identities of train/traction A and train/traction B.
+
+## 9.15.4 Post-conditions
+
+1. Train/traction C arrives at the destination consisting of train/traction A&B
+2. Train A and Train B arrive at the planned destination.
+
+## 9.15.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [9.15-001] | The FRMCS System shall be able to assign and withdraw an FRMCS Equipment Identity common to several FRMCS Equipment, e.g. for trains being coupled together in order to be reachable under the same FRMCS Equipment Identity. | A | 22.280 | Covered by [R-5.9a-015] The MCX Service system shall allow an MCX Service Administrator to make use of information (e.g. operational schedules, locations, velocity or direction) from external sources to create or delete a functional alias. and [R-5.9a-18] The MCX Service shall support automatic activation and de-activation of a functional alias based on the operational criteria (e.g. MCX User ID, login/logoff from the MCX Service system, specific external information supplied by external systems). |
+
+## 9.16 Arbitration related use cases
+
+### 9.16.1 Introduction
+
+In this chapter the use cases related to arbitration are defined. The following use cases are defined:
+
+- Arbitration
+- Arbitration for communication auto-connection
+
+### 9.16.2 Use case: Arbitration
+
+#### 9.16.2.1 Description
+
+The FRMCS System shall be able to perform arbitration, based on the context of the communication. Arbitration in this context means that the FRMCS System is able to determine the behaviour of the end user device in case of multiple competing communications. Additionally, the FRMCS System may ask the FRMCS User which communication to accept.
+
+#### 9.16.2.2 Pre-conditions
+
+The FRMCS System is authorised to perform arbitration on communication on the end user device.
+
+#### 9.16.2.3 Service flows
+
+##### Incoming communication
+
+When the communication is received by the FRMCS User on any of its registered functional identities, the FRMCS System provides to the FRMCS User arbitration information.
+
+FRMCS System is able to present arbitration options to the FRMCS User to select from.
+
+Arbitration of communication determines automatically to accept, reject, put on hold or queue the incoming and/or the ongoing communication, based on both the incoming and the ongoing communication characteristics.
+
+##### Outgoing communication
+
+The FRMCS User is initiating a new communication. Arbitration information is available from the FRMCS application.
+
+The arbitration application has the possibility to present arbitration options to the end user to select from.
+
+The arbitration application decides to accept, reject, and put on hold or queue, the ongoing and/or the new communication, based on both the incoming and the ongoing communication characteristics.
+
+#### 9.16.2.4 Post-conditions
+
+The communication is established to the FRMCS Equipment the FRMCS User has selected.
+
+#### 9.16.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------|-------------------------|--------------------------|----------|
+| [R-9.16.2-001] | The FRMCS System shall be able to provide communication to the | A | TS 22.280 section 6.19.1 | |
+
+| | | | | |
+|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | FRMCS User based on the arbitration information associated with the communication. | | | |
+| [R-9.16.2-002] | The FRMCS System shall be able to accept, reject, hold, queue or prompt the user for his choice on the incoming communication. | A | TS 22.280 | <p>Automatic arbitration in on-network mode: <b>covered</b> by requirements in section 6.19.1: MCX request to transmit are granted, rejected or queued (put on hold and queue are considered as similar mechanism).</p> <p>Automatic arbitration in off-network mode: <b>covered</b> by requirements in section 7.3.2.</p> <p>Manual arbitration (user selection) in on-network mode: accept and reject are covered by section 6.7.6. Mechanism to queue is <b>not covered</b>.</p> <p>Manual arbitration (user selection) in off-network mode is <b>not covered</b>.</p> |
+| [R-9.16.2-003] | When the FRMCS User is using multiple FRMCS Equipment simultaneously, the FRMCS System shall be able to establish the communication to the appropriate FRMCS Equipment, based on FRMCS User selected option. | A | TS 22.280 | [R-6.7.2-005] |
+
+## 9.16.3 Use case: Arbitration for communication auto-connection
+
+### 9.16.3.1 Description
+
+The FRMCS System shall be able to automatically accept incoming communications without asking the FRMCS User, based on configuration (i.e., configured arbitration rules).
+
+### 9.16.3.2 Pre-conditions
+
+The FRMCS System is authorised to perform arbitration on communication on the FRMCS Equipment (i.e., end user device).
+
+### 9.16.3.3 Service flows
+
+#### **FRMCS User is using a single FRMCS Equipment**
+
+When the communication is received by the FRMCS User on any of its identities (including registered functional identities), the FRMCS System automatically accepts the incoming private or group communication if arbitration rules are configured to do so.
+
+#### **FRMCS User is using multiple FRMCS Equipment simultaneously**
+
+If arbitration rules allow configuration for automatic answering and if an FRMCS User is logged in multiple FRMCS Equipment simultaneously, the FRMCS System automatically accepts the incoming private or group communication to the FRMCS User's default FRMCS Equipment when the communication is received by the FRMCS User on any of its registered functional identities.
+
+The FRMCS User's default FRMCS Equipment is set up by either the FRMCS User or by the FRMCS System Administrator.
+
+If the FRMCS System fails to automatically accept the incoming private or group communication to the FRMCS User's default FRMCS Equipment, the FRMCS System automatically accepts the incoming private or group communication to another FRMCS Equipment the FRMCS User is logged in.
+
+#### **Arbitration rules**
+
+Arbitration rules allows configuration for automatic answering based on:
+
+- The FRMCS User identities;
+- The FRMCS User registered functional identities;
+- The FRMCS Application identities;
+- The FRMCS User's default FRMCS Equipment.
+
+### 9.16.3.4 Post-conditions
+
+The incoming communication is automatically accepted to the relevant FRMCS Equipment the FRMCS User is logged in.
+
+### 9.16.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.16.3-001] | When an incoming private communication is received by the FRMCS User, the FRMCS System shall be able to automatically accept the communication if arbitration rules are configured to do so (based on FRMCS User identities, registered functional identities or FRMCS Application types). | A | 22.280 | Partly covered by private call setup in automatic commencement mode (request for automatic commencement mode – automatic answering – is triggered by the calling party, not by the System).<br>In addition, configuration for automatic commencement mode is based on MC User ID only. Arbitration rules based on FRMCS Application types (i.e., MCPTT, MCData or MCVideo) is supported but not on Functional Alias(es).<br><b>Editor's note: CR is needed.</b> |
+| [R-9.16.3-002] | When an incoming group communication is received by the FRMCS User, the FRMCS System shall be able to automatically accept the communication if arbitration rules are configured to do so (based on FRMCS User identities, registered functional identities or FRMCS Application types). | A | 22.280 | Covered by affiliation and functional alias mechanisms. |
+| [R-9.16.3-003] | When the FRMCS User is using multiple FRMCS Equipment simultaneously, the FRMCS System shall be able to automatically accept an incoming private communication to the default FRMCS Equipment. | A | 22.280 | Covered by 5.10 Support for multiple devices (i.e., multiple MCX UEs) and [R-6.7.2-005] default device designated by the receiving user.<br><b>Editor's note on multiple devices support: default UE covered by stages 2&3? (didn't find it)</b> |
+| [R-9.16.3-004] | The default FRMCS Equipment is configured by either the FRMCS User or by the FRMCS System Administrator. | A | 22.280 | Partly covered by 5.10 Support for multiple devices (i.e., multiple MCX UEs) and [R-6.7.2-005]: only the receiving user can designate the default device. |
+| [R-9.16.3-005] | When the FRMCS User is using multiple FRMCS Equipment simultaneously, the FRMCS System shall be able to automatically accept an incoming private communication to other FRMCS Equipment if communication to the default FRMCS Equipment fails to be established. | A | 22.280 | Not covered by [R-6.7.2-005]: it is up to the receiving user to detect that something is wrong with default UE and then to select another UE to receive incoming call.<br><b>Editor's note on multiple devices support: selection of default UE “on the fly” supported or only during MC Registration?</b> |
+
+## 9.17 Data communication to exchange key information for train safety application use cases
+
+### 9.17.1 Introduction
+
+In this chapter the use cases related to Key management communication are defined. The following use cases are defined:
+
+- Initiation of a Key Management data communication
+- Termination of a Key Management data communication
+- Service interworking and service continuation with GSM-R
+
+### 9.17.2 Use case: Initiation of a Key Management data communication
+
+#### 9.17.2.1 Description
+
+Key Management communication is the application which performs the functions that ensure the exchange of credentials/keys required by other applications (such as ATO, ATP) to ensure the correct authentication of the end users of each application and the integrity of the messages exchanged.
+
+Some Key Management systems require radio communication to interchange the relevant data between a train and its corresponding key distribution centre (Key Management Center). This key distribution centre may be located in the same network or in an external network.
+
+The users in this case are the Key Management applications both on-board of the train and in the key distribution centre at the trackside (ground system).
+
+Key Management communication is considered to be user-to-user data communication.
+
+The communication of keys may be requested each time that an ATP or ATO communication session is established or at any other time, depending on the specific configuration of the Key Management application.
+
+#### 9.17.2.2 Pre-conditions
+
+The initiating application on the FRMCS equipment is authorised to initiate the Key Management data communication. This is managed by the authorisation of communication application.
+
+The receiving application on the FRMCS equipment is authorised to use the Key Management data communication. This is managed by the authorisation of communication application.
+
+#### 9.17.2.3 Service flows
+
+The initiating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) initiates the Key Management data communication to the receiving side on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train). The QoS profile of the communication is managed by the QoS Profile application. The data communication requests the QoS profile which matches the application category of CRITICAL DATA (see [QoS]) within the FRMCS system, depending on the application needs.
+
+The FRMCS system establishes the bearer service required for the data communication within a setup time specified as IMMEDIATE (see [QoS]).
+
+The arbitration is managed by the arbitration application on the FRMCS equipment.
+
+The communication is recorded by the Data recording and access to recorded data application.
+
+#### **9.17.2.4 Post-conditions**
+
+The initiating application on the FRMCS equipment is connected to the receiving application.
+
+Data can be exchanged between the Key Management applications.
+
+### 9.17.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.17.2.5-001] | For Key management communication, the communication shall be considered to be user-to-user data communication. | A | TS 22.282 | TS 22.282<br>Sub-clause: 5.5<br><br>Note: Application Layer Key Management is transparent to the transport and communications services. Reference transport. |
+| [R-9.17.2.5-002] | For Key management communication, the initiating and the receiving application on the FRMCS equipment shall be able to be authorised to initiate the Key management communication. This shall be managed by the authorisation of data communication application. | A | TS 22.280 | TS 22.280<br>Sub-clause: 5.5, and 5.12.<br><br>Note: Application Layer Key Management is transparent to the transport and communications services. |
+| [R-9.17.2.5.2-003] | For Key management communication, the initiating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) shall be able to initiate the Key Management data communication to the receiving side on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train). The QoS profile of the communication shall be managed by the QoS Profile application. The data communication shall be able to request the QoS profile which matches the application category of CRITICAL DATA (see [QoS]) within the FRMCS system, depending on the application needs. | A | N/A | See sub-clause 12.10. |
+| [R-9.17.2.5-004] | For Key management communication, the FRMCS system shall be able to establish the bearer service required for the data communication within a setup time specified as IMMEDIATE (see [QoS]). | A | N/A | See sub-clause 12.10. |
+
+| | | | | |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------|---|-----------|-----------------------------|
+| [R-9.17.2.5-005] | For Key management communication, the arbitration shall be managed by the arbitration application on the FRMCS equipment. | A | TS 22.280 | TS 22.280 Sub-clause: 6.4.7 |
+| [R-9.17.2.5-006] | For Key management communication, the communication shall be recorded by the recording and access to recorded data application. | A | TS 22.280 | TS 22.280 sub-clause 6.15.4 |
+
+### 9.17.3 Use case: Termination of a Key Management data communication
+
+#### 9.17.3.1 Description
+
+The initiating or the receiving application can terminate the Key Management data communication.
+
+#### 9.17.3.2 Pre-conditions
+
+The Key Management applications on-board and trackside have a data communication initiated.
+
+#### 9.17.3.3 Service flows
+
+The terminating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) terminates the Key Management data communication with the receiving side application on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train).
+
+The FRMCS system terminates the bearer service required for the data communication.
+
+#### 9.17.3.4 Post-conditions
+
+The terminating Key Management data application is disconnected from the receiving application.
+
+### 9.17.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-9.17.3.5-001] | For Key management communication, the terminating application on the FRMCS equipment (e.g. on-board of the train or the key distribution centre at the track side) shall be able to terminate the Key Management data communication with the receiving side application on the FRMCS equipment (e.g. key distribution centre at the trackside or on-board of the train). | A | TS 22.280 | TS 22.280<br>Sub-clause: 5.5, and 5.12.<br><br>Note: Application Layer Key Management is transparent to the transport and communications services. |
+| [R-9.17.3.5-002] | For Key management communication, the FRMCS system shall be able to terminate the bearer service required for the data communication. | A | TS 22.282 | TS 22.282<br>Sub-clause: 5.5<br><br>Note: Application Layer Key Management is transparent to the transport and communications services.<br>Reference transport. |
+
+### 9.17.4 Use case: service interworking and service continuation with GSM-R
+
+#### 9.17.4.1 Description
+
+For migration purposes the service interworking and service continuation between the GSM-R system and FRMCS system for Key Management data communication needs to be clear.
+
+Depending on the migration scenario a key distribution centre can be attached to the FRMCS system, to the GSM-R system or both. The on-board Key Management application can be attached either in the GSM-R system or in the FRMCS system. Functional identities are applicable in one system only.
+
+This use case only applies to end user devices supporting both FRMCS and GSM-R systems.
+
+Online Key Management data exchange is supported only with a packet switched (PS) bearer in the GSM-R system. Therefore, for service interworking and service continuation only the PS bearer is required.
+
+#### 9.17.4.2 Pre-conditions
+
+The initiating application on the FRMCS equipment is authorised to initiate the Key Management data communication. This is managed by the authorisation of communication application.
+
+The receiving application on the FRMCS equipment is authorised to use the Key Management data communication. This is managed by the authorisation of communication application.
+
+#### 9.17.4.3 Service flows
+
+##### Initiating Key Management application attached to GSM-R
+
+When the initiating Key Management application on the FRMCS equipment is attached to the GSM-R system and is initiating data communication to another Key Management application, the GSM-R system will route the data communication accordingly.
+
+If the other Key Management application on the FRMCS equipment is attached to the FRMCS system, the GSM-R system can only route the data communication if the destination can be reached by an address or identity understood by the GSM-R system. The role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
+
+The information from the role management and presence application is used to route the communication and to present the identities.
+
+#### **Initiating Key Management application attached to FRMCS**
+
+When the initiating Key Management application on the FRMCS equipment is attached to the FRMCS system and is initiating data communication to another Key Management application, the FRMCS system will route the communication accordingly.
+
+If the other Key Management application on the FRMCS equipment is attached to the GSM-R system, the FRMCS system can only route the data communication if the destination can be reached by an address or identity understood by the FRMCS system. The role management in FRMCS provides the appropriate address or identity e.g. by providing a mapping of GSM-R identities and FRMCS identities.
+
+The information from the role management and presence application is used to route the communication and to present the identities.
+
+#### **Key Management application moving from GSM-R to FRMCS**
+
+When the Key Management application on the FRMCS equipment is detached from the GSM-R system the FRMCS end user device shall provide service continuation by setting up the communication via the FRMCS system. An interruption of data communication is acceptable.
+
+#### **Key Management application moving from FRMCS to GSM-R**
+
+When the Key Management application on the FRMCS equipment is detached from the FRMCS system, the FRMCS end user device shall provide service continuation by setting up the communication via the GSM-R system. An interruption of data communication is acceptable.
+
+#### **9.17.4.4 Post-conditions**
+
+None.
+
+---
+
+## **10 Performance support applications related use cases**
+
+**Editor's Note: Text to be provided.**
+
+---
+
+## 11 Business support applications related use cases
+
+### 11.1 Charging and Billing information related use cases
+
+#### 11.1.1 Introduction
+
+In this chapter the use cases related to charging and billing are defined. The following use cases are defined:
+
+- Obtaining charging and billing information
+
+#### 11.1.2 Use case: Obtaining charging and billing information
+
+##### 11.1.2.1 Description
+
+The Railway operators may have the obligation or the desire to charge FRMCS Users of their FRMCS Networks, or to use billing information for statistical reasons.
+
+An entitled FRMCS User shall be able to obtain information for any type of FRMCS communications from the FRMCS system, to be able to generate bills.
+
+##### 11.1.2.2 Pre-conditions
+
+An entitled FRMCS User is logged on to the FRMCS system.
+
+##### 11.1.2.3 Service flows
+
+The entitled FRMCS User requests billing information for a single FRMCS User or a group of FRMCS Users.
+
+The entitled FRMCS User selects defined criterias (e.g. timeframe, incoming communications, outgoing communications, numbers and/or any kind of FRMCS Identity) to get more detailed results.
+
+The entitled FRMCS User configures the FRMCS system to generate the billing information once or periodically.
+
+##### 11.1.2.4 Post-conditions
+
+The requested billing information is generated from the FRMCS System.
+
+### 11.1.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|
+| [R-11.1.2-001] | The FRMS System shall be able to generate charging records for one or multiple FRMCS Users based on defined criterias (e.g. timeframe, incoming communications, outgoing communications, numbers and/or any kind of FRMCS Identity). | A/T | Partly covered (only CDR covered by 3GPP – billing system outside the 3GPP domain). | 6.15.4 |
+| [R-11.1.2-002] | The FRMCS System shall allow to charge separately for each type of FRMCS Application and/or each type of application category. | A/T | TS 22.261 section 9.2 | Support collection of charging information based on resource usage (e.g. QoS, applications). |
+| [R-11.1.2-003] | The FRMCS System shall allow to charge for different Service Attributes. | A/T | TS 22.261 section 9.2 | Support collection of charging information based on resource usage (e.g. QoS, applications). |
+
+---
+
+## 12 FRMCS System principles related use cases
+
+### 12.1 FRMCS System principles overview
+
+In this chapter, FRMCS System related use cases are described which are complying with principles such as:
+
+- Provide broadband and/or mission critical services with seamless connectivity
+- Offer high-quality control functions and real-time performance monitoring
+- Interworking with legacy systems including GSM-R and LMR
+- Build stable positioning framework for FRMCS services and devices including trainborne (in-train) and handheld (in-train, and in/out-door) UEs
+- Bearer flexibility
+- QoS in a railway environment
+- FRMCS System security framework
+
+To describe the use cases, an example system is assumed by adapting LTE for railway communication [4] as follows:
+
+
+
+Figure 12.1-1: An example system for FRMCS System principle use cases. The diagram shows a central 'FRMCS Domain' (dashed blue box) containing a 'Train Control Centre', a 'Backbone Network', a '3GPP Network (e.g. LTE)', 'UE', and 'Trainborne UE'. The 'Train Control Centre' is connected to the 'Backbone Network'. The 'Backbone Network' is connected to the '3GPP Network (e.g. LTE)' and also to an external 'Public Safety Mobile Comm. Network'. The '3GPP Network (e.g. LTE)' is connected to the 'UE' and 'Trainborne UE'. Outside the 'FRMCS Domain', 'GSM-R UE' and 'TRS UE' are connected to 'GSM-R' and 'TRS' clouds, which are in turn connected to the 'Backbone Network'. A 'Public Safety Centre' is connected to the 'Public Safety Mobile Comm. Network'.
+
+**Figure 12.1-1. An example system for FRMCS System principle use cases**
+
+The example system is consisted of the train control centre, 3GPP network such as LTE with UE and the trainborne UE. The backbone network connects the train control centre, 3GPP network and legacy systems. FRMCS System is interworking with the legacy systems such as GSM-R and TRS.
+
+## 12.2 Area Broadcast Group Communication interworking between GSM-R and FRMCS Users
+
+### 12.2.1 Description
+
+This use case describes an area broadcast group communication between FRMCS User(s) and GSM-R User(s), and vice versa.
+
+### 12.2.2 Pre-condition
+
+FRMCS User A and GSM-R User B and User C are authorized Users to perform group communication together by the FRMCS System.
+
+User A and User B and User C are in the same group communication area defined by the FRMCS System.
+
+### 12.2.3 Service flow
+
+#### FRMCS System to GSM-R
+
+FRMCS User A initiates a new area broadcast group communication (based on location etc., of GSM-R User B and C).
+
+FRMCS User A broadcasts group communication invitations to all Users in the same area.
+
+GSM-R User B and User C receive the group communication invitations.
+
+GSM-R User B and User C accept the invitation and join the group communication. Or GSM-R User B and User C automatically join this group communication.
+
+#### **GSM-R to FRMCS**
+
+GSM-R User B initiates a new group call (based on location etc., of FRMCS User A and GSM-R User C).
+
+GSM-R User B broadcasts group call invitations to all Users in the same area.
+
+FRMCS User A and GSM-R User C receive the group call invitations.
+
+FRMCS User A and GSM-R User C accept the invitation and join the group call. Or FRMCS User A and GSM-R User C automatically join this group call.
+
+### **12.2.4 Post-condition**
+
+FRMCS User A, GSM-R User B and User C can communicate among each other in a group call.
+
+### **12.2.5 Potential requirements**
+
+| <b>Reference Number</b> | <b>Requirement text</b> | <b>Application / Transport</b> | <b>SA1 spec covering</b> | <b>Comments</b> |
+|-------------------------|---------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------|-----------------|
+| [12.2-001] | FRMCS System shall provide a means to initiate group communication between FRMCS Users and GSM-R Users. | A | 22.179 | R-6.18.3.5-003 |
+| [12.2-002] | FRMCS System shall provide means to FRMCS Users to join the group calls of GSM-R | A | 22.179 | R-6.18.3.5-003 |
+
+## **12.3 Location Service interworking between GSM-R and FRMCS Users**
+
+### **12.3.1 Description**
+
+This use case allows FRMCS System and GSM-R system to obtain and share the location information of their users.
+
+### **12.3.2 Pre-condition**
+
+User A is an authorized FRMCS User.
+
+User B is an authorized GSM-R User.
+
+User A and User B are affiliated to a group that consists of FRMCS User(s) and GSM-R User(s).
+
+### **12.3.3 Service flow**
+
+#### ***FRMCS System to GSM-R***
+
+FRMCS User A sends a location request to the specific GSM-R User B.
+
+GSM-R User B accepts and return his location information as requested.
+
+#### ***GSM-R to FRMCS System***
+
+GSM-R User B sends a location request to the specific FRMCS User A.
+
+FRMCS User A accepts and returns his location information as requested.
+
+### **12.3.4 Post-condition**
+
+FRMCS User A's location information is sent to GSM-R User B.
+
+GSM-R User B's location information is sent to FRMCS User A.
+
+### **12.3.5 Potential requirements**
+
+| <b>Reference Number</b> | <b>Requirement text</b> | <b>Application / Transport</b> | <b>SA1 spec covering</b> | <b>Comments</b> |
+|-------------------------|-------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------|-----------------|
+| [12.3-001] | FRMCS System shall provide a means to obtain and share with FRMCS User the location information of GSM-R User(s). | A | 22.280 | R-6.17.3.1-001 |
+| [12.3-002] | FRMCS System shall provide means to provide location information of FRMCS User to GSM-R. | A | 22.280 | R-6.17.3.1-001 |
+
+## **12.4 Presence interworking between GSM-R and FRMCS Users**
+
+### **12.4.1 Description**
+
+Service interworking of user's presence between GSM-R and FRMCS Systems is not required.
+
+### **12.4.2 Pre-condition**
+
+Void.
+
+### **12.4.3 Service flow**
+
+Void.
+
+### **12.4.4 Post-condition**
+
+Void.
+
+### **12.4.5 Potential requirements**
+
+Void.
+
+## 12.5 Point to Point communication between GSM-R and FRMCS Users
+
+### 12.5.1 Description
+
+This use case allows a FRMCS User to communicate with a GSM-R User, vice versa.
+
+### 12.5.2 Pre-condition
+
+User A is an authorized FRMCS User.
+
+User B is an authorized GSM-R Users.
+
+### 12.5.3 Service flow
+
+#### FRMCS System to GSM-R
+
+FRMCS User A initiates a point to point communication to GSM-R User B.
+
+GSM-R User B accepts the communication and joins the communication.
+
+#### GSM-R to FRMCS System
+
+GSM-R User B initiates a point to point call to FRMCS User A.
+
+FRMCS User A accepts the call and joins the call.
+
+### 12.5.4 Post-condition
+
+GSM-R User B and FRMCS User A are communicating with each other.
+
+### 12.5.5 Potential requirements
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------|
+| [12.5-001] | FRMCS System shall provide a means for point to point communication between an authorized FRMCS User and a GSM-R User, | A | 22.179 | R-6.18.3.5-004 |
+
+FRMCS System
+
+## 12.6 Interworking with legacy systems including LMR
+
+### 12.6.1 Description
+
+This use case describes the way of interworking with legacy systems including LMR.
+
+## 12.6.2 Pre-conditions
+
+The train driver uses the trainborne UE.
+
+Train crews have a LMR UE for each.
+
+The operator at the train control centre has a 3GPP UE.
+
+The train control centre is connected to the public safety centre via 3GPP network.
+
+## 12.6.3 Service flows
+
+The train driver calls the train control centre to report an emergency of the train and wants to share the report with train crews in the train.
+
+The FRMCS System initiates a 3GPP call to the operator at train control centre.
+
+The FRMCS System initiates a LMR call to all of train crews.
+
+The train driver reports the situation. The FRMCS System transmits the report to the train control centre via 3GPP network and to train crews in the train via LMR.
+
+The train control centre received the report and forward the call via 3GPP network to report the situation to the public safety centre.
+
+The train control centre activates the switching device on the railway track to pass other trains via the signal control network.
+
+The train control centre orders the train crews to do a counter-action on the situation.
+
+Train crews are shared with the report and order, and deal with the situation properly.
+
+## 12.6.4 Post-conditions
+
+The situation has been handled.
+
+The train control centre has the information on the situation, the counter-action and its result.
+
+The public safety centre gets the report on the situation in real-time.
+
+## 12.6.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------|
+| [12.6-001] | The FRMCS System shall provide interworking related functionality between the 3GPP network and the legacy network of LMR, e.g. TETRA and P25. | A/T | 22.179 | The requirement is covered by 6.18.3 Interworking with non-3GPP PTT systems of 22.179 |
+| [12.6-002] | The FRMCS System should provide interworking with the signal control network. | A | 22.280 | This requirement is covered by the combination of functional alias, affiliation mechanism, and IP connectivity. |
+
+## 12.7 Use case: Builds stable positioning framework for FRMCS services and devices including trainborne and handheld devices
+
+### 12.7.1 Description
+
+This use case considers stable positioning framework for FRMCS services and devices are placed in indoor and/or outdoor. The use case focuses covering “GPS shadow area” with ad-hoc positioning technology such as LTE location service.
+
+### 12.7.2 Pre-conditions
+
+The trainborne UE has GNSS function.
+
+The trainborne UE has 3GPP Communication Module.
+
+The train control centre monitors the train traffics.
+
+### 12.7.3 Service flows
+
+The operator at the train control centre requests location information from a train.
+
+The train is running through a very long tunnel, therefore the GNSS in the trainborne UE does not work.
+
+The operator at the train control centre connects the location service in the 3GPP system as an alternative way and obtains the train’s location which is actually the location of the trainborne UE.
+
+The operator at the train control centre determines the train path and controls railway tracks by signalling the track circuit device.
+
+### 12.7.4 Post-conditions
+
+The train control centre obtains the location of the train.
+
+The track circuit for the train is reorganized.
+
+## 12.7.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [12.7-001] | The FRMCS System shall provide the alternative means than GNSS to obtain the position of the FRMCS Equipment. | A | TS 22.280 | The interfacing method and format of the location information from the LTE system is covered by 3GPP specification such as UE positioning in E-UTRAN[5]. Covered by [R-5.11-002a] of TS 22.280 which is “The MCX Service shall be able to provide a mechanism for obtaining high accuracy Location information by integrating position information from multiple external sources (e.g. magnetometers, orientation sensors, GNSS)”. |
+| [12.7-002] | The positioning information shall provide an accuracy of [TBD] whilst the UE is travelling at a maximum of 500 km/h. | A/T | TS 22.261 | TS 22.261 sub-clause 6.27.2<br>TS 22.261 sub-clause 7.3.2 – refer to positioning service level 3 (only one speed limit supported – up to 500 km/h – with horizontal accuracy of 1m)<br>See [R-12.14.2-001] of clause 12.14.2.5. |
+
+## 12.8 Interworking between GSM-R and FRMCS
+
+### 12.8.1 Introduction
+
+GSM-R is the widely used wireless communication system of the railways. It provides the bearer service for current critical and supportive railway applications. The deployment of FRMCS and the migration to FRMCS is expected to encompass a large timeframe estimated currently at 10 years. During this period, coexistence and interworking of both communication systems is required. Interworking between the FRMCS System and GSM-R system shall be provided.
+
+Interworking on functional level e.g. numbering plan alignment is not part of this use case.
+
+Note 1: Interworking is the functionality of two networks to talk to each other enabling services to be delivered across the two networks (source: GSMA Document IR.65 "IMS Roaming, Interconnection and Interworking Guidelines").
+
+Note 2: 3GPP MCX specifications have different understandings of Interworking and Interconnection than GSMA and the Railways.
+
+### 12.8.2 Circuit Switched interworking between GSM-R and FRMCS
+
+#### 12.8.2.1 Description
+
+##### Background:
+
+Circuit switched bearer services are used in GSM-R for voice and data communication. That encompasses user-to-user as well as multiuser voice communication.
+
+**Description:**
+
+FRMCS and the GSM-R will coexist for a period estimated currently at 10 years that demands interworking for circuit switched bearer services to cover voice. It requires the necessary circuit switched transport adaptation, the necessary conversion of the signalling and the user data coding among the systems.
+
+**12.8.2.2 Pre-conditions**
+
+GSM-R user is attached to the GSM-R system.
+
+FRMCS Users is attached to the FRMCS System.
+
+**12.8.2.3 Service flows**
+
+GSM-R user establishes a user-to-user voice communication to a FRMCS User.
+
+GSM-R user establishes a multiuser communication including FRMCS Users.
+
+FRMCS User establishes a user-to-user voice communication to a GSM-R user.
+
+FRMCS User establishes a multiuser voice communication including GSM-R users.
+
+**12.8.2.4 Post-conditions**
+
+User-to-user voice communication between GSM-R user and FRMCS User are established.
+
+Multiuser voice communication between GSM-R user and FRMCS Users are established.
+
+**12.8.2.5 Potential requirements and gap analysis**
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------|
+| [R-12.8.2-001] | FRMCS-system to GSM-R circuit switched signalling and bearer service interworking shall be supported for user-to-user and multiuser voice communication. | A/T | 22.179 | [R-6.18.4.2-003], [R-6.18.4.2-004] |
+| [R-12.8.2-002] | FRMCS System shall support the current voice codecs used by GSM-R. | A/T | 22.179 | [R-6.18.4.2-005] |
+| [R-12.8.2-003] | The FRMCS System shall be able to support interworking of GSM-R MLPP based call priorities to the priority mechanisms of the FRMCS System. | A | 22.179 | [R-6.18.4.2-003] |
+| [R-12.8.2-004] | The FRMCS System shall be able to support interworking between the arbitration scheme used in GSM-R and the arbitration scheme used in the FRMCS System. | A | 22.179 | [R-6.18.4.2-003] |
+
+## 12.8.3 Packet Switched interworking between GSM-R and FRMCS
+
+### 12.8.3.1 Description
+
+Packet switched bearer services i.e. GPRS/EGPRS are used in GSM-R for data communication e.g. ATP. FRMCS and the GSM-R will coexist for a period estimated currently at 10 years that demands an interconnection for packet switched based communication. It requires the necessary packet switched transport adaptation to FRMCS, the conversion of the signalling and the user data coding among the systems.
+
+### 12.8.3.2 Pre-conditions
+
+GSM-R user is attached to the GSM-R system.
+
+FRMCS Users are attached to the FRMCS System.
+
+### 12.8.3.3 Service flows
+
+GSM-R user establishes a user-to-user packet switched communication to a FRMCS User.
+
+FRMCS User establishes a user-to-user packet switched communication to a GSM-R user.
+
+### 12.8.3.4 Post-conditions
+
+Packet Switched communication among GSM-R user and FRMCS User are established.
+
+### 12.8.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.8.3-001] | FRMCS-system to GSM-R packet switched interworking shall be supported. | A/T | N/A | According to latest decision from UIC (see FRMCS project activities status report in ERIG#70 (July 2018), the requirement is not required. No use case has been identified by UIC ((E )GPRS EVC could not be connected to any FRMCS RBC). |
+
+## 12.8.4 SMS/SDS interworking between GSM-R and FRMCS
+
+### 12.8.4.1 Description
+
+SMS has been widely used in GSM-R.
+
+FRMCS and GSM-R will coexist for some period. So, interworking between the FRMCS System and Short Message Service in GSM-R is needed.
+
+A possible scenario is that a GSM-R user sends a short message to a FRMCS User to transfer some information.
+
+### 12.8.4.2 Pre-conditions
+
+GSM-R user is attached to the GSM-R system.
+
+FRMCS User is attached to the FRMCS system.
+
+#### 12.8.4.3 Service Flows
+
+A GSM-R user sends a short message to a FRMCS User to transfer some information.
+
+#### 12.8.4.4 Post-conditions
+
+The FRMCS User can communicate with the GSM-R user.
+
+#### 12.8.4.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------|-------------------------|-------------------|-------------|
+| [R-12.8.4-001] | The FRMCS System shall be able to interwork with the Short Message Service in GSM-R. | A | 22.282 | [R-7.2-001] |
+
+### 12.9 Use case: Bearer flexibility
+
+#### 12.9.1 Description
+
+FRMCS envisages bearer flexibility to allow a certain level of independence between Railway Applications and the underlying transport system. FRMCS includes wireless and wireline access. It comprises multiple access systems and shall support various voice and data applications.
+
+The rationale behind these requirements is that the lifecycle of railway applications is in general much longer than the lifecycle of telecommunication access/transport systems. Moreover, bearer flexibility aims at improving service availability and performance.
+
+The characteristics of bearer flexibility are:
+
+1. A Railway Application may use one or several access systems as appropriate.
+2. Connection of FRMCS Equipment to different access systems is dynamic (i.e. the most appropriate 3GPP or non-3GPP access technologies are selected automatically, potentially using multiple access technologies for one or more Railway Applications).
+3. The set of access systems chosen meets the defined QoS and the service requirements e.g. FRMCS User mobility and connectivity which are necessary to guarantee the functionality.
+4. The introduction of a new access system should not negatively impact existing Railway Applications.
+
+The approach taken within FRMCS allows the integration of 3GPP and non-3GPP radio access evolution.
+
+IP is used as a generic interface towards Railway Applications, facilitating connectivity, quality of service control, security and the separation of transport system and applications. NOTE: Non-3GPP access can consist of non-terrestrial e.g. Satellite as well as of terrestrial access systems.
+
+## 12.9.2 Pre-conditions
+
+The Railway Adaptation Sub-System as part of the FRMCS System is embedded between the Railway Applications and the Multi Access Core Network (MACN) and enables the access system independence towards those applications. This Sub-System adapts application characteristics to the access systems. It manages e.g. QoS, address conversion, functional roles and train location information.
+
+The MACN has the ability to manage and interwork with wireless access systems (i.e. 3GPP and non-3GPP) as well as with wireline access systems. It encompasses for example the management of FRMCS User mobility, FRMCS User session/communication handling and control of end-to-end communication prioritisation. The MACN interworks with legacy communication systems and other FRMCS Systems.
+
+The Access Control & Management function of the FRMCS Equipment is able to manage the different access systems as well as access via GSM-R (for roaming and simultaneous operation).
+
+## 12.9.3 Service flows
+
+### Case 1 (data communication)
+
+As an example the Automatic Train Protection (ATP) application of a train establishes a data communication session with the applicable ground communication entity which is connected via the fixed network service. For ATP message exchange, the on-board system can encompass a railway operated private 3GPP 4G access system and a public 3GPP 5G access system (e.g. a VPN service) as part of the FRMCS System. ATP periodically reports train position information and receives Control Command instructions from the ground communication entity. The FRMCS Equipment is registered to both access systems and uses these simultaneously if applicable.
+
+Simultaneous use of radio access systems may improve communication resilience, availability, and QoS and increases bandwidth.
+
+The concept as described here can generally be extended to other data communication applications and (non-)3GPP access systems.
+
+### Case 2 (railway emergency voice communication)
+
+The on-board FRMCS Users are registered to the FRMCS System. An on-board FRMCS User establishes a Railway Emergency Communication (REC) from a specific location in the FRMCS network. This particular communication request takes into account the most appropriate radio access system, for example the railway-operated private 3GPP network. The FRMCS System notifies the applicable users determined by the location of the initiator of the communication by using all available access system(s) e.g. 3GPP (public and private), WLAN or wireline. The applicable Controller is notified via the wireline access system. The intended recipients of the call may be using different access systems.
+
+The concept as described here can in general be extended to other voice group communication applications and point to point communication services.
+
+### Case 3 (telemetry operation at a railway depot)
+
+A train is located in a railway depot where only WLAN coverage (non-3GPP access) as part of the FRMCS System is provided. FRMCS Users of this train are attached to the FRMCS System. An FRMCS User starts a data session towards the applicable vehicle diagnostic entity. At that point in time WLAN provides the radio access system for this telemetry communication. Once the train leaves the depot and enters into a 3GPP coverage area, the FRMCS Equipment adapts the transmission of the telemetry data session to the most QoS effective radio access system (3GPP access). The telemetry session continues uninterrupted when the train changes its location.
+
+The concept as described here can in general be extended to other voice and data applications where other combinations of access systems at specific locations are possible.
+
+### Case 4 (Backup operation/resilience)
+
+In a certain area with dedicated 3GPP access, coverage fails. Despite unavailability of the dedicated railway 3GPP access, FRMCS Users have the capability to continue communications by using public 3GPP access using an access system which may support the required or some degraded form of QoS and which is provided in the area and which serves as a backup or complementary system. Communication applications on trains continue to operate, service continuity is preserved. When the functionality of the dedicated 3GPP access system is restored, the FRMCS Equipment resumes operation on that system.
+
+The concept as described here can generally be extended to any combination of access systems, e.g. WLAN and private 3GPP access.
+
+#### **Case 5 (Notification of radio bearer availability)**
+
+In general, there is only little radio spectrum resources allocated to railways in most regions. These should be preferably used for operational rail communication purposes. In parallel, there are communications that require broadband wireless communication services. The availability of broadband wireless access can be limited e.g. to railway stations. Thus, the FRMCS System is able to take into account radio bearer availability at the FRMCS User's position allowing to start communication such as a file download/upload not harming operational rail communication.
+
+#### **Case 6 (Use of Satellite Communication)**
+
+In some regions, trains are circulating in rural areas, on low traffic lines. For such situation, deploying dedicated rail terrestrial radio access is not economically viable and public mobile operator's service is very limited due to low population density rate. Satellite access is foreseen as an alternative to terrestrial radio access that reduces investment in access infrastructure. In this first approach, satellite access is considered as an enabler to extend communication service of rail lines with FRMCS.
+
+Some rail applications require service continuity for railways operation. In some situation, rail traffic is stopped when communication services are not available. To overcome situations of temporary outage or total destruction of terrestrial access, use of non-terrestrial access systems by the FRMCS system could be envisaged to deliver a highly resilient transport service. In this second approach, satellite access is foreseen as a backup from terrestrial radio access.
+
+It is envisaged that the FRMCS application could be configured with preconditions that trigger an alternate mode of operation.
+
+### **12.9.4 Post-conditions**
+
+#### **Case 1 (data communication)**
+
+The train protected by ATP arrives on time without service interruptions of the communication.
+
+#### **Case 2 (railway emergency voice communication)**
+
+Railway emergency voice communication is established to all FRMCS Users in the designated area independent of the used access network.
+
+#### **Case 3 (telemetry operation at a railway depot)**
+
+Telemetry communication continued while relocating the train/vehicle.
+
+#### **Case 4 (Backup operation/resilience)**
+
+Communication continued when the private 3GPP access is unavailable in an area.
+
+#### **Case 5 (Notification of radio bearer availability)**
+
+none
+
+#### **Case 6 (Use of Satellite Communication)**
+
+Communication continued when the 3GPP terrestrial radio access coverage is physically not provided in an area.
+
+Communication continued when the 3GPP terrestrial radio access is temporarily not available in an area.
+
+
+
+## 12.9.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------------------|---------------------------------------------------------------------------------------------|
+| [R-12.9-001] | The FRMCS System shall be able to manage 3GPP access systems and non-3GPP access systems (terrestrial and non-terrestrial) simultaneously. | A/T | TS 22.278<br>TS 22.261 | TS 22.278 sub-clause 5.0<br>TS 22.261 sub-clause 6.3.2.1 |
+| [R-12.9-002] | If provided by the FRMCS Equipment, the FRMCS Application on the FRMCS Equipment shall be able to make use of 3GPP and non-3GPP access systems simultaneously. | A | TS 22.278<br>TS 22.261 | TS 22.278 sub-clause 6.2<br>TS 22.261 sub-clause 6.3.2.1 |
+| [R-12.9-003] | The FRMCS User shall not experience service interruptions in the usage of applications due to a change of an access system. | A | TS 22.278<br>TS 22.261 | TS 22.278 sub-clause 5.0<br>TS 22.261 sub-clause 6.2.3<br>broader functional spectrum |
+| [R-12.9-004] | The FRMCS transport system including 3GPP and non-3GPP access shall be agnostic to Railway Applications. | T | TS 22.278<br>TS 22.261 | TS 22.278 sub-clause 5.0<br>TS 22.261 sub-clause 6.2.1/6.2.3<br>broader functional spectrum |
+| [R-12.9-005] | New access technology shall not require changes for the pre-existing application layer to be able to make use of this new access technology.<br>Note: Changes are required if the application layer wants to make use of the new capabilities of a new access technology. | A/T | TS 22.261 | TS 22.278 only partially compliant because of missing satellite access support |
+| [R-12.9-006] | The transport layer shall allow using IP as a generic interface. | T | TS 22.278<br>TS 22.261 | TS 22.278 sub-clause 7.2<br>TS 22.261 sub-clause 5.1.2.3 |
+| [R-12.9-007] | For recording purposes, the FRMCS System shall be able to provide communication content as well as the associated communication related information. | A | TS 22.280<br>TS 22.278<br>TS 22.261 | TS 22.280 sub-clause 6.15.4<br>TS 22.278 sub-clause 9.2<br>TS 22.261 sub-clause 8.6 |
+| [R-12.9-008] | The FRMCS System shall be able to make use of one or more of the followings:<br>3GPP radio access (i.e. 4G and/or 5G) through railway-dedicated licensed spectrum<br>3GPP radio access (i.e. 4G and/or 5G) provided by public providers<br>3GPP radio access (e.g. LTE- | T | TS 22.261 | TS 22.278 reduced capabilities; partially encompasses only 4G access |
+
+| | | | | |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | U) through unlicensed spectrum<br>Non-3GPP radio access (e.g. IEEE 802.11 based and/or satellite based)<br>Wireline access<br>Note 1: GSM-R, TETRA, and P25 are not considered as a radio access technology of FRMCS.<br>Note 2: Not all of the radio access technologies may support all of the FRMCS requirements. | | | |
+| [R-12.9-009] | The FRMCS System shall consider the availability of radio bearer services at the position of the FRMCS User to allow communication. | A | TS 22.261 | 6.3.2.1: The 5GS shall be able to dynamically offload part of the traffic (e.g. from 3GPP RAT to non-3GPP access technology), taking into account traffic load and traffic type. |
+| [R-12.9-010] | The FRMCS System shall select appropriate radio bearer service with consideration of the FRMCS applications configurable preconditions (e.g. ranking of the available bearer services). | T | TS 22.261 | TS 22.261 sub-clause 6.3.2.1<br><br>TS 22.278 reduced capabilities; partially encompasses only 4G access<br>TS 22.278 sub-clause 7.1.6 |
+| [R-12.9-011] | The FRMCS System shall provide indication to FRMCS application on which bearer service is being used. | T | N/A | Implementation requirement |
+| [R-12.9-012] | Session continuity between 3GPP access and non-3GPP access shall not require FRMCS Users intervention. | T | TS 22.261 | 6.2.3: service continuity<br>6.3.2.1: The 5GS shall be able to support mobility between the supported access networks |
+
+## 12.10 Use Case: QoS in a railway environment
+
+### 12.10.1 Introduction
+
+This system principle use case provides the framework for Quality of Service within the FRMCS System including the railway applications. The main purpose is to specify the list of attributes applicable to the FRMCS bearer service.
+
+Railway applications exhibit different characteristics, e.g., in terms of latency or reliability. On the other hand, the FRMCS System offers bearer services with different properties.
+
+In this context, two types of applications can be distinguished:
+
+1. Applications that are aware of their transport service requirements and that are able to request those from the FRMCS System.
+2. Applications that are not aware of their transport service requirements and that are therefore not able to request those.
+
+Railway applications require a QoS classification ranging from high to low as low is “best effort”. The most important QoS parameters that determine the quality of the transport system are latency of the user data and reliability of the communication. In addition, guaranteed bandwidth assures the continuation of critical communication.
+
+QoS impacts train punctuality and the entire utilisation of the track system. Therefore, the FRMCS System has to consider the various QoS requirements.
+
+Apart from high train speed operation, which goes up to $500\text{kmh}^{-1}$ , other fundamental factors affect wireless communication. Railways are facing various radio signal propagation conditions such as in free space and in tunnels. Free space encompasses various structural and constructional scenarios. Railway corridors in hilly terrain or forest aisle are some examples.
+
+Radio propagation in large railway stations and shunting yards is different from the one of the main lines. Moving trains in stations or moving cargo wagons in shunting yards cause different propagation conditions.
+
+Radio tower site-to-site distance requires special attention. This distance varies depending on the type of area (rural or urban) and is determined by the boundary conditions of the RF signal (e.g. frequency band and power budget). Railways clearly require to deploy FRMCS while keeping the same distance between the radio towers in order to reuse the infrastructure deployed for GSM-R.
+
+Voice communication is commonly used during rail operation to give instructions to a driver of a locomotive in shunting operation, track maintenance etc. Rail environmental conditions like slowdown or movement of a train can impact the understandability of the voice.
+
+Radio propagation conditions in a rail environment are quite specific. For example train speed up to $500\text{km/h}$ or the insertion loss of the radio signal into a train. Staff has to work in the train, beside a train or under the train etc. while voice communication is ongoing. Such conditions shall not lower the intelligibility of the voice.
+
+Radio spectrum constraints in some regions require high efficiency in terms of radio bandwidth utilisation where voice communication coexists with other communication types simultaneously. The resulting voice codec has to consider these specific conditions.
+
+## 12.10.2 Use case: Quality of Service and railway environment
+
+### 12.10.2.1 Description
+
+The basis for this use case is the UIC FRMCS URS wherein communication attributes define the QoS to be achieved for the various kinds of railway applications. These attributes are not part of the functional use case description but relevant for the FRMCS System and therefore subject of this use case.
+
+Regarding the URS communication attributes, not all attributes are covered in the QoS use case. The following items are considered:
+
+- Type of communication
+- Latency, the delay between action and reaction
+- Session Reliability
+- Setup of communication, the time to establish a voice or data communication session
+- Talker assignment time in group communication
+- Audio (Voice) Quality
+
+For further details, refer to the corresponding use cases in chapters 5 – 9. In these chapters the QoS requirements are specified on functional level. A reference is used which refers to real values' in this QoS use case.
+
+### 12.10.2.2 Pre-conditions
+
+The pre-conditions of the functional use cases out of chapter 5 – 9 are applicable.
+
+### 12.10.2.3 Service flows
+
+The service flows of the functional use cases out chapter 5 – 9 are applicable.
+
+#### Application categories
+
+Application categories describe the data transfer characteristic to be achieved by a bearer service. The FRMCS System shall consider the following user plane application categories:
+
+**Voice** for user to user or multiuser communication; Voice follows the typical conversational pattern and requires low delay inside the transport system;
+
+**Critical Voice** follows the voice conversational pattern but requires immediate session setup;
+
+**Video** used for general observations purposes, e.g. maintenance;
+
+**Critical Video** with indirect impact on train operation, e.g. passenger surveillance;
+
+**Very Critical Video** with direct impact on safety- related critical train control and operation, e.g. used in driverless ( e.g. GoA3/GoA4) operation for automated detection of objects (no human in the loop) or video-based remote control (human in the loop).
+
+**Very critical data** for future rail applications;
+
+**Critical data** follows the response pattern and requires high reliable transport. This category comprises future and legacy applications e.g. ETCS;
+
+**Non-Critical data** used for the exchange of railway system or communication relevant information; requires high reliable transmission and preservation of the response pattern;
+
+**Messaging** for the exchange of non-critical short information messages, recorded voice (for example voicemail), data, pictures, video; requires reliable transmission;
+
+#### Priority Level
+
+In order to reach the QoS applicable for each application category, transport priority levels are required to differentiate among the communication urgency. Priority handling of communication service encompasses the assignment of a priority to a communication and involves the seizing of resources, which are in use by a communication having a lower ranking in the absence of idle resources. Priority handling includes as well discontinuation of an ongoing communication having a lower priority to allow an incoming communication of higher priority. Priority handling needs to be provided to a FRMCS User for all communications.
+
+Priorities are treated by the FRMCS User/Equipment in the FRMCS System based on the following conditions:
+
+- The priority level depends on the FRMCS User initiating the communication.
+- The communication can have the priority level selected by the FRMCS User at setup or the priority level is predefined at registration. The treatment of priority level also applies when the FRMCS User is registered to a visited FRMCS network.
+- The definition of the priority level which may cause pre-emption of another ongoing communication needs to be stored and can be changed by the FRMCS User.
+- The FRMCS System is able to allocate setup classes i.e. communication setup time requirements and resource pre-emption capabilities to each priority level.
+
+- In case of resource pre-emption, the pre-empted FRMCS user needs to be provided with a suitable indication.
+- The priority level can be selected by the FRMCS User on a per communication basis.
+
+The FRMCS User may select any priority level up to the authorised priority level. The maximum priority level needs to be stored on the UICC. At communication setup, the FRMCS Equipment and the FRMCS System verify the priority level at setup against the maximum authorised priority level. If the FRMCS User has not selected a priority level at setup, the FRMCS System applies a FRMCS User specific default priority level. If the FRMCS User has selected at setup a priority level higher than the maximum authorised priority level, the maximum authorised priority level is applied for the communication.
+
+### Service Attributes
+
+From FRMCS User point of view there are two main service attributes latency and communication reliability.
+
+For the **Latency** two classifications are applicable:
+
+- Low User data delay harms the functioning of the application.
+- Normal User data delay does not harm the sequence and progress of the application.
+
+From FRMCS System point of view, latency quantifies the end-to-end user data transport delay between the involved communication entities.
+
+**Reliability** (in accordance to TS 22.261): in the context of network layer packet transmissions, percentage value of the amount of sent network layer packets successfully delivered to a given system entity within the time constraint required by the targeted service, divided by the total number of sent network layer packets.
+
+Two levels are to be taken into account:
+
+- High The packet loss at transport level is exceptional rare.
+- Normal The packet loss at transport level is seldom.
+
+The FRMCS System is able to assign multiple individual FRMCS User communications having individual QoS profile to a single IP address.
+
+To meet the different application characteristics e.g. conversational pattern, real-time or critical data further itemisation is necessary. The mapping of the service attributes latency and reliability among functional requirements and FRMCS System as well as their target values are summarised in Table 12.10-1.
+
+| Service Attribute | FRMCS - Functional Requirement | FRMCS – System Requirement | Service Attribute value |
+|-------------------|--------------------------------|----------------------------|-------------------------|
+| Latency | Low | Ultra-Low | ≤10ms |
+| | | Low | ≤100ms |
+| | Normal | Normal | ≤500ms |
+| | | Best Effort | >500ms |
+| Reliability | High | Ultra-High | 99.9999% |
+| | | High | 99.9% |
+| | Normal | Normal | 99% |
+
+**Table 12.10-1 - Service attribute mapping**
+
+Some application categories are time stringent e.g. critical voice or critical data.
+
+The range of latency and reliability requirements have a certain dependency on the speed of the trains. In general, the requirement is that the service attributes can be guaranteed up to 500kmh<sup>-1</sup>. Certain combinations of latency and reliability apply only to **Low Speed** (≤ 40kmh<sup>-1</sup>).
+
+The applications are considered as real-time when the FRMCS functional requirement for the latency is specified as “Low” and “Ultra Low”, according to table 12.10 1.
+
+### Session handling
+
+**Setup time** of a communication session is essential because of their safety related character. Communication session setup encompasses the value of the elapsed time between the communication establishment request and the indication of successful communication session establishment. The FRMCS User requires two classes:
+
+**Immediate** The FRMCS User requires immediate setup of the communication session. The duration of the immediate communication session establishment shall not exceed 1 second.
+
+**Normal** Normal communication session setup time range does not harm the use of the application. The time duration of the normal communication session establishment shall not exceed 3 seconds.
+
+**Talker assignment time** comprises the timeframe between talker request and the permission to talk applicable to group communication. This timeframe shall be lower than 300ms. Talker assignment time assumes that a group communication has been set up.
+
+**Session Loss Rate (SLR)** indicates the number of sessions released unintentionally per accumulated session time. SLR shall be $<10^{-2}/h$ .
+
+### Communication and QoS assignment
+
+In order to provide the required level of communication quality, the FRMCS System will request the applicable resources as required for the communication service from the underlying 3GPP transport system and if appropriate also from non-3GPP transport systems. The transport resources are characterised by latency, reliability, guaranteed bitrate/non-guaranteed bitrate and communication service priority.
+
+If no specific service attributes are required for a certain communication service, the FRMCS System is able to apply a predefined default.
+
+Each communication service resource characteristic can be requested independently of the others.
+
+As result of the request to the underlying transport system, the FRMCS System may offer different values than the ones requested but which fit to the categories summarised in Table 12.10-1.
+
+The available radio spectrum in certain regions, for example in Europe is rather limited, therefore the FRMCS System might apply different resources for the same communication service in different regions to achieve a radio resource efficient use of the available bandwidth.
+
+### Audio quality
+
+Voice intelligibility strongly depends on the audio bandwidth. FRMCS System has to consider for voice communication following minimum requirements:
+
+- Encoding of speech encompass in minimum the range of 200–7000 Hz;
+- The codec meets the local radio channel and capacity requirements of the FRMCS system;
+- The coding of speech signals is robust to radio impairments sacrificing voice clarity;
+
+#### 12.10.2.4 Post-conditions
+
+The post conditions of the functional use cases out of chapter 5 – 9 are applicable.
+
+#### 12.10.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|------------------------------------------------------------------|
+| [R-12.10.2-001] | The FRMCS System shall be capable of providing different levels of QoS. | (A)T | TS 22.261 | sub-clause 6.7.2 paragraph 1 |
+| [R-12.10.2-002] | The FRMCS-system service attributes shall be allocated unambiguously per application and/or per session and/or per FRMCS User. | (A)T | TS 22.261 | sub-clause 6.7.2 paragraph 1<br>sub-clause 6.8 paragraph 3, 4 |
+| [R-12.10.2-003] | The FRMCS System shall support the efficient use of the radio resources. | (A)T | TS 22.261 | sub-clause 6.7.2 paragraph 3<br>sub-clause 6.23.2 |
+| [R-12.10.2-004] | The FRMCS System shall provide service attribute control on a peer to peer basis. | (A)T | TS 22.261 | sub-clause 6.7.2 paragraph 6<br>sub-clause 6.8 paragraph 3 |
+| [R-12.10.2-005] | The FRMCS System shall provide a mapping between application characteristics and the bearer service attributes. | (A)T | TS 22.261 | sub-clause 6.7.2 paragraph 1 |
+| [R-12.10.2-006] | The FRMCS System shall be able to support different QoS for uplink and downlink of asymmetric bearers. | (A)T | TS 22.261 | sub-clause 6.7.2 paragraph 2 |
+| [R-12.10.2-007] | The FRMCS System shall be able to modify service attributes during an active communication session. | A/T | TS 22.261<br>TS 22.280 | TS 22.261 sub-clause 6.8 paragraph 1<br>TS 22.280 sub-clause 6.8 |
+| [R-12.10.2-008] | The FRMCS System shall detect and process the various user data traffic characteristics, latency and session reliability requirements. These requirements are summarised in Table 12.10-2. | (A)T | TS 22.261 | sub-clause 6.8 paragraph 6 |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------|
+| [R-12.10.2-009] | The FRMCS System shall support the applicable QoS requirements up to a train speed of 500kmh <sup>-1</sup> at all locations along the track unless restrictions are indicated which are:<br><br>Low speed $\leq 40\text{kmh}^{-1}$ . | T | 22.289 | sub-clause 5.2.2 |
+| [R-12.10.2-010] | To prioritize among the application categories and their related QoS, the FRMCS System shall support 15 priority levels. | T | 22.280 | [R-6.8.7.2-005] |
+| [R-12.10.2-011] | The FRMCS System shall be able to request service attributes (latency, reliability, guaranteed bitrate/ non-guaranteed bitrate and priority) from the underlying 3GPP transport system and if appropriate also from non-3GPP transport systems. | T | TS 22.261 | sub-clause 6.7.2 paragraph 5, 8 |
+| [R-12.10.2-012] | The FRMCS System shall be able to apply predefined default service attributes. | T | TS 22.261 | sub-clause 6.8 paragraph 4-6 |
+| [R-12.10.2-013] | The FRMCS System shall be able to request each communication service attributes independently of the others. | T | TS 22.261 | sub-clause 6.7.2 paragraph 1, 2, 6 |
+| [R-12.10.2-014] | The FRMCS System shall be able to assess whether the communication service attributes received from the transport system are sufficient to support the communication service fully or in a restricted way and report this information to the FRMCS application. | T | TS 22.261 | sub-clause 6.7.2 paragraph 3 |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.10.2-015] | The FRMCS System shall be able to keep the communication priority independent from the QoS parameters latency, reliability, guaranteed/non-guaranteed bitrate. | T | TS 22.261 | sub-clause 6.7.2 paragraph 4 |
+| [R-12.10.2-016] | The FRMCS System shall provide a radio resource efficient allocation of the communication bandwidth. | T | TS 22.261 | sub-clause 6.7.2 paragraph 3<br>sub-clause 6.23.2 |
+| [R-12.10.2-017] | Talker assignment time, the timeframe between talker request and the permission to talk in a multi-user voice communication, shall be lower than 300ms. | A/T | 22.179 | [R-6.15.3.2-012] The MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 95% of all MCPTT Request.<br><br>[R-6.15.3.2-013] For MCPTT Emergency Group Calls and Imminent Peril Calls the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 99% of all MCPTT Requests. |
+| [R-12.10.2-018] | FRMCS system shall support at least encoding of speech signals between 200–7000 Hz. | A/T | 22.280<br>26.441 | TS 22.280<br>sub-clause 5.13<br>TS 26.441<br>entire document |
+| [R-12.10.2-019] | The FRMCS voice codec shall be robust to meet different radio channel impairments caused by the different working conditions in the train, beside or under the train. | A/T | 22.280<br>26.445 | clause 5<br>s0504-s0506 |
+| [R-12.10.2-020] | The encoding of speech signals in the FRMCS system shall be efficient to meet limited radio resource availability. | A/T | 22.280<br>26.445 | clause 5<br>s0504-s0506 |
+
+| <b>Reference Number</b> | <b>Requirement text</b> | <b>Application / Transport</b> | <b>SA1 spec covering</b> | <b>Comments</b> |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------|-----------------|
+| [R-12.10.2-021] | Priority handling of communication service in the FRMCS System shall encompass the assignment of a priority to a communication and involves the seizing of resources, which are in use by a communication having a lower ranking in the absence of idle resources. | A/T | 22.280 | [R-6.8.7.2-001] |
+| [R-12.10.2-022] | Priority handling of the FRMCS System shall support discontinuation of an ongoing communication having a lower priority to allow an incoming communication of higher priority. | A/T | 22.280 | [R-6.8.7.2-004] |
+| [R-12.10.2-023] | The FRMCS System shall always consider the priority of the FRMCS User initiating the communication. | A | 22.280 | [R-6.8.7.2-002] |
+| [R-12.10.2-024] | The FRMCS System shall consider for a communication the priority level selected by the FRMCS User at setup or the priority level predefined at registration. | A | 22.280 | [R-6.8.7.2-004] |
+| [R-12.10.2-025] | The FRMCS System shall treat the communication priority levels when the FRMCS User is registered to a FRMCS network. | A | 22.280 | [R-6.8.7.2-001] |
+| [R-12.10.2-026] | The definition of the priority level which may cause pre-emption of another ongoing communication shall be stored and can be changed by the FRMCS User. | A | 22.280 | [R-6.8.7.2-004] |
+| [R-12.10.2-027] | The FRMCS System shall be able to allocate setup classes i.e. communication setup time requirements and resource pre-emption capabilities to each priority level. | A/T | 22.280 | [R-6.8.7.2-003] |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------|
+| [R-12.10.2-028] | In case of resource pre-emption, the pre-empted FRMCS user shall be provided with a suitable indication. | A | N/A | It is an implementation choice |
+| [R-12.10.2-029] | The priority level shall be selected by the FRMCS User on a per communication basis. | A/T | 22.280 | [R-6.8.7.2-001] |
+| [R-12.10.2-030] | The FRMCS User shall be able to select any priority level up to the authorised priority level. The maximum priority level shall be stored on the UICC. | A | 22.280 | [R-6.8.7.2-006]<br>[R-6.8.7.2-007] |
+| [R-12.10.2-031] | At communication setup, the FRMCS Equipment/UE and the FRMCS System shall verify the priority level at setup against the maximum authorised priority level. | A | 22.280 | [R-6.8.7.2-008] |
+| [R-12.10.2-032] | If the FRMCS User has not selected a priority level at setup, the FRMCS System shall apply a FRMCS User specific default priority level. | A | 22.280 | [R-6.8.7.2-009] |
+| [R-12.10.2-033] | If the FRMCS User has selected at setup a priority level higher than the maximum authorised priority level, the maximum authorised priority level shall be applied by the FRMCS System for the communication. | A | 22.280 | [R-6.8.7.2-010] |
+| [R-12.10.2-034] | The FRMCS System shall take into account the service attributes to allow selection of the available bearer services. | T | TS 22.261 | sub-clause 6.7.2 paragraph 5, 8 |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|-------------------------------------------------------------------------|
+| [R-12.10.2-035] | The FRMCS System shall be able to assign multiple individual FRMCS User communications having individual QoS profile to a single IP address. | A/T | TS 22.261<br>TS 22.280 | TS 22.261<br>sub-clause 6.8 paragraph 3<br>TS 22.280<br>sub-clause 5.15 |
+| [R-12.10.2-036] | The FRMCS System shall provide a mechanism to derive the communication characteristics of an application and map those on a data flow with a predefined QoS profile. | A/T | TS 22.261<br>TS 22.280 | TS 22.261<br>sub-clause 6.8 paragraph 3<br>TS 22.280<br>sub-clause 5.15 |
+
+Application categories and their related service attributes are grouped into specific QoS class. Table 12.10-2 summarises the QoS classes and their applicable service attributes.
+
+| Application Category | Service Attribute (according to Table 12.10-1) | | Session establishment | Session Loss Rate |
+|-------------------------------------|------------------------------------------------|-------------|-----------------------|----------------------|
+| | Latency peer to peer | Reliability | | |
+| Voice | Low | Normal | Normal | NA |
+| Critical Voice | Low | High | Immediate | NA |
+| Video | Normal | High | Normal | NA |
+| Critical Video | Low | High | Immediate | NA |
+| Very Critical Video | Ultra Low or Low Note 1 | High | Normal | NA |
+| Critical Data (future applications) | Low | Ultra-High | Immediate | NA |
+| Very Critical Data | Ultra-Low or Low (Note 1) | Ultra- High | Immediate | NA |
+| Critical Data (legacy applications) | Normal | High | Normal | <10 <sup>-2</sup> /h |
+| Non-Critical data | Normal | High | Normal | NA |
+| Messaging | Best Effort | High | Normal | NA |
+
+Note 1: The latency “Ultra low” is restricted to low speed $\leq 40 \text{ kmh}^{-1}$ .
+
+**Table 12.10-2 - Service and Service Attribute requirements**
+
+### Railway specific conditions
+
+1.) Following propagation conditions are to be considered:
+
+- Free space in general
+
+- Railway corridors in general and especially in hilly terrain
+ - Forest Aisle
+ - Underground / tunnel environment
+ - Moving trains or objects in a railway station and shunting yards
+- 2.) FRMCS System should be able to reuse the existing GSM-R sites. A non-exhaustive [example list](#) provides the typical site-to-site deployment scenarios:
+Rural environment: between 5 - 7km.
+Urban environment: <5km.
+
+## 12.11 Use case: Provide broadband and mission critical services with seamless connectivity
+
+### 12.11.1 Description
+
+The FRMCS shall provide the broadband and mission critical services with seamless connectivity.
+
+### 12.11.2 Pre-conditions
+
+The operator at the train control centre has a Railway Emergency Call to a train which is in operation with 500km/h speed via 3GPP network.
+
+Using a trainborne UE, the train driver is discussing an issue on operation of the train with train crews by a video call via a proximity-based services such as ProSe.
+
+### 12.11.3 Service flows
+
+The operator at the train control centre calls the train driver to give an emergency information including broadband video via the 3GPP network of FRMCS System.
+
+The FRMCS System indicates the train driver is currently having a video call which has a normal priority with train crews.
+
+The FRMCS System compares the priority of the Railway Emergency Call and the ongoing call.
+
+Due to the higher priority of the Railway Emergency Call, the FRMCS System puts the ongoing call on hold and the participants receive a notification.
+
+Within 300ms, the train driver is connected to the railway emergency call.
+
+During the Railway Emergency Call, the train driver watches the broadband video as a supplement material to understand the emergency easier.
+
+The train driver recognizes the emergency and does some proper works.
+
+### 12.11.4 Post-conditions
+
+After the Railway Emergency Call is ended, the hold call is resumed.
+
+## 12.11.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-------------------------------------------------------------------------------|
+| [R-12.11.5-001] | The FRMCS System shall be able to define the priority level of Railway Emergency Call. | A | 22.280 | This requirement is <u>covered</u> by 22.280 [R-5.16.2-002] |
+| [R-12.11.5-002] | The FRMCS System shall be able to handle the priority level of Railway Emergency Call. | A | 22.280 | This requirement is covered by 22.280 [R-5.16.2-002] |
+| [R-12.11.5-003] | The FRMCS System shall support switching between on-network service and off-network service. | A | 22.280 | [This requirement is covered by 22.280 [R-6.18-001] to [R-6.18-006].] |
+| [R-12.11.5-004] | The FRCMS system shall handle a priority call less than 300ms of call setup time in the environment of train speed up to 500km/h. | A | 22.289 | This requirement is covered by section 5.2.2 of 22.289. |
+| [R-12.11.5-005] | The FRMCS System shall be able to present a video included in the Railway Emergency Call. | A | 22.281 | This requirement is covered by 22.281 [R-5.1.9.2.2-001] to [R-5.1.9.2.2-003]. |
+
+## 12.12 Use case: Offer railway services high-quality control functions with real-time train status monitoring
+
+### 12.12.1 Description
+
+The FRMCS System offers high-quality control functions for railway services with real-time train status monitoring.
+
+The train runs on railway by 500km/h of speed. The operator at the train control centre makes request to get the status of the train.
+
+### 12.12.2 Pre-conditions
+
+The train runs on railway by 500km/h of speed.
+
+In the train, there is a trainborne UE and it is connected via 3GPP network.
+
+### 12.12.3 Service flows
+
+The operator at the train control centre makes request to get the status of a train which runs on railway by 500km/h of speed.
+
+The request is made with the train number, rather than the trainborne UE equipment identity.
+
+The request goes through the backbone network and 3GPP network, reaches a trainborne UE.
+
+The trainborne UE gets the train status such as speed and location and records the video monitoring data of the train.
+
+The train status data are encrypted in the security reason by the trainborne UE and is responded back to the train control centre via the 3GPP network.
+
+The trainborne UE requests the moving authority data to the train control system in the train control centre. The moving authority is a permission for a train to move to a specific location with supervision of speed.
+
+The train control system responds the moving authority data to the trainborne UE within a time which is defined in FRMCS QoS.
+
+### 12.12.4 Post-conditions
+
+The train control centre de-crypts the train status data and is able to see the status of the train including the streaming video of monitoring.
+
+The train receives the moving authority data and references the data.
+
+### 12.12.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|------------------------------------------------------------------------|
+| [R-12.12-001] | The FRMCS System shall provide a mapping between FRMCS Equipment Identity and the train number. | A | 22.280 | This requirement is covered by [R-5.9a-018] of 22.280 |
+| [R-12.12-002] | The FRMCS System shall be able to maintain a secure data channel for the train status monitoring communication. | A | 22.280 | This requirement is covered by [R-5.12-001] and [R-5.12-009] of 22.280 |
+| [R-12.12-003] | The FRMCS should be able to define a minimum bandwidth of video monitoring. | A | 22.289 | This requirement is covered by section 5.2.2 of 22.289 |
+| [R-12.12-004] | The FRMCS should be able to define a minimum delay time of communicating the train status monitoring. | A | 22.289 | This requirement is covered by section 5.2.2 of 22.289 |
+| [R-12.12-005] | The FRMCS should be able to define a minimum delay time of communicating the moving authority data. | A | 22.289 | This requirement is covered by section 5.2.2 of 22.289. |
+
+## 12.13 Use case: Provide call priority during interworking with LMR
+
+### 12.13.1 Description
+
+There are Mission Critical Services such as Railway, use many kinds of communication technology, e.g. TRS and LTE. To make interworking between the networks to during provide FRMCS communication, it needs to manage call priority between calls which are made between the networks.
+
+During the interworking between FRMCS and LMR systems including TETRA and P25, FRMCS provides call priority based on factors such as the situation, group priority, level of user, etc. For example, a Railway Emergency Call could be categorized as a public announcement on emergency (low-level priority) or an operation emergency call (high-level priority).
+
+Examples on the priority of calls in FRMCS are provided in the following table:
+
+**Table 12.13-1: Priority of calls in FRMCS**
+
+| Call Type | Priority | Related Action |
+|--------------------------|----------|-------------------------------------------------------------------------------------|
+| Operation Emergency Call | 0 | Stop all the calls have priority lower than or equal to Control Safety Announcement |
+
+| | | |
+|-------------------------------------------------------|---------------|------------------------------------------------------------------------------------------|
+| | (the highest) | |
+| Control Safety Announcement (between Operation Users) | 1 | Stop all the calls have priority lower than or equal to Public Announcement on Emergency |
+| Public Announcement on Emergency | 2 | Stop all the calls have priority lower than or equal to Operation Call |
+| Operation Call (not emergency case) | 3 | Stop all the calls have priority lower than or equal to Service Information Announcement |
+| Service Information Announcement | 4 | - |
+
+The examples in the table 12.13-1 are made by modifying of the call priority of the railway communication system as a mission critical service [4].
+
+If an operation emergency call is invoked by a user (maybe a train driver), it should have higher level of priority than the public announcement on emergency call of other user. In this case, all the lower priority calls may need to be pre-empted or queued to allow the operation emergency call.
+
+In order to provide the call priority, the interworking needs to be able to maintain the information on the priority of each call and each user who invoked a call or a group call. When a call is invoked, FRMCS should compare the priority between the current call and the new call and decide which one is allowed to go through.
+
+## 12.13.2 Pre-conditions
+
+The operator at the train control centre has a Railway Emergency Call to a train which is in operation with 500km/h speed via 3GPP network.
+
+Using a trainborne UE, the train driver has an announcement of control safety to the train crews via LMR such as TRS.
+
+## 12.13.3 Service flows
+
+The operator at the train control centre calls the train driver and the train crews to give an emergency notice via the 3GPP network of FRMCS System.
+
+The FRMCS System indicates the train driver and the train crews are currently having a group call which has a lower priority then the emergency notice call.
+
+The FRMCS System queues the ongoing TRS call and connects the train control centre and the trainborne UE.
+
+The emergency notice call from the train control centre via the 3GPP network, is relayed to TRS to make announce to the train driver and the train crews.
+
+The train driver and the train crews recognize the emergency and do some proper works.
+
+## 12.13.4 Post-conditions
+
+After the emergency notice call is ended, the queued TRS call is resumed.
+
+### 12.13.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.13-001] | FRMCS should be able to handle call priority when interworking with LMR communication systems. | A | 22.179<br>22.280 | <p>This requirement is covered by 22.179 [R-6.18.3.2-006] to [R-6.18.3.2-009] and 22.179 [R-6.18.3.3-006] to [R-6.18.3.3-007].</p> <p>The high level requirements of handling call priority are covered by many sections of 22.280, e.g. section 5.1.7 and 5.6.</p> <p>TETRA and P25 may need considerations as follows:</p> <ul style="list-style-type: none"> <li>a. TETRA may provide some customizable features to maintain the call priority such as Call ownership and Call priority.</li> <li>b. P25 has no features to support the call priority.</li> <li>c. FRMCS has many basic information to handle the call priority such as 'Priority of the user for initiating/receiving calls' in the user profile data and 'Priority of the group' in the group configuration data.]</li> </ul> |
+| [R-12.13-002] | The FRMCS System should be able to define a maximum call setup time for a call between 3GPP system and LMR system. | A | 22.289 | This requirement is covered by section 5.2.3 of 22.289 |
+| [R-12.13-003] | FRMCS should provide the call priority supporting features to interworking with LMR. | A | 22.179<br>22.280 | <p>This requirement is covered by 22.179 [R-6.18.3.2-006] to [R-6.18.3.2-009] and 22.179 [R-6.18.3.3-006] to [R-6.18.3.3-007].</p> <p>The high level requirements of handling call priority are covered by many sections of 22.280, e.g. section 5.1.7 and 5.6.</p> |
+| [R-12.13-004] | FRMCS should provide interworking between FRMCS System and LMR system. | A | 22.179 | covered by 22.179 [R-6.18.3.2-001] and [R-6.18.3.3-001] |
+
+## 12.14 Use Case: FRMCS Positioning Accuracy
+
+### 12.14.1 Introduction
+
+This system principle use case describes the positioning accuracy requirements to position a train, track side worker as well as other stationary and non-stationary object inside the track system. In general, positioning accuracy will become a major building block to increase the automation level of train operation. The main purpose is to specify the accuracy parameter values.
+
+### 12.14.2 Use case: FRMCS Positioning Accuracy
+
+#### 12.14.2.1 Description
+
+Today fixed mounted balise are used to derive the train position inside the track-system. This kind of train positioning is precise enough when the train is moving. Static conditions like in stations, push-pull train operation or the frequent change between static and dynamic conditions during shunting operation require hundreds of fixed mounted balise. Thus, a balise without stationary reference shall overcome this circumstance.
+
+According to Figure 12.14-1, individual coaches, trains, track side worker get equipped which such devices that report continuously the process status towards the applicable control centre enriched with the actual position information.
+
+
+
+Figure 12.14-1: Positioning application areas. The diagram shows a track layout with multiple parallel tracks. On the top track, there are two yellow maintenance vehicles. Below them, a train consisting of five blue rectangular coaches is shown. The first coach has a green light on its left side, and the last coach has a red light on its right side. Below the train, another track shows a single blue coach with a green light on its left side. At the bottom, a track side worker wearing a yellow safety vest and holding a green flag is standing on a track. The tracks are divided into segments by vertical lines, and some segments are highlighted with pink or green background colors. The entire diagram is enclosed in a perspective view frame.
+
+**Figure 12.14-1 Positioning application areas**
+
+Tracks/lines or shunting areas are subdivided into autonomous hazard areas (red blocks see Figure 12.14-1). The continuous processing of positioning information allows the control centre to detect when hazard areas start to overlap. Based on the computed risk integral, the control centre is able to instruct the vehicles or trains in the concerned area to lower the speed up to a full stop.
+
+To guarantee fail-safe operation in deriving the position of the vehicle, track-side worker etc., and independent positioning sources need to be provided. Beside inertial navigation, GNSS and others, the FRMCS System is required to be part of the positioning data acquisition process. This results from rather low predictable availability of satellite
+
+systems especially in mountain regions, multilevel railway station as well as in tunnels. In the worst case, “rough” positioning information only derived from the FRMCS – Land Mobile Network is present.
+
+The combination of 3GPP radio access network and the train on-board system is able to support mechanisms that can be used to locate an entire train, stationary as well as non-stationary objects. Together with the positioning information of other sources (see Figure 12.14-2) e.g. inertial navigation and GNSS, consolidated positioning information of the train/object will be computed that is able to fulfil higher accuracy of the positioning information. Train Onboard system as well as FRMCS location information system will receive the consolidated location positioning information for further processing by the train safety applications and/or FRMCS location information system.
+
+
+
+The diagram illustrates the flow of positioning information. At the top, a grey rounded rectangle is labeled 'User' with a white rectangular box next to it. Below this is a long grey rounded rectangle labeled 'Train'. Inside the 'Train' rectangle, there are four separate white rectangular boxes arranged horizontally, each containing placeholder text. Upward-pointing arrows connect each of these four boxes to the 'User' box. Below the 'Train' rectangle is another long grey rounded rectangle labeled 'Ground', which also contains placeholder text. A small grey square is positioned between the 'Train' and 'Ground' rectangles.
+
+Figure 12.14-2: Consolidation of positioning source information. The diagram shows a 'User' block at the top, a 'Train' block in the middle, and a 'Ground' block at the bottom. The 'Train' block contains four sub-blocks representing different FRMCS users. Arrows point from each of these four sub-blocks up to the 'User' block, indicating the consolidation of positioning information.
+
+**Figure 12.14-2 Consolidation of positioning source information**
+
+The subject described is applicable to other FRMCS functional use cases. The resulting positioning requirements in this use case are relevant for the FRMCS System.
+
+### 12.14.2.2 Pre-conditions
+
+Railway line consist of station A, B and C. Station B is between station A and C.
+
+FRMCS User 1 is used by an InterRegio train that stops in station A, B and C.
+
+FRMCS User 2 is used by a high speed train that stops in station A and station C.
+
+FRMCS User 3 is used on a parked train in station B.
+
+FRMCS User 4 is used by mobile warning equipment located in station B.
+
+Ground FRMCS User processes the received positioning information of the different train FRMCS Users for safety purposes.
+
+FRMCS Users on the train (safety application) established the communication to the ground FRMCS User (safety application) that is responsible for train safety purposes on the line between the stations A and C including station B.
+
+Base stations are covering the line between station A and station C. The structure of the base station along the line is linear. In some cases dual base stations per site can be used. The distance between adjacent base stations varies between 1 and 10km.
+
+Train speed profile ranges between 0 - 500km/h.
+
+The base stations covering the line between station A and C are enhanced cellular base stations that are able to form a carrier grade positioning network.
+
+### 12.14.2.3 Service flows
+
+Train FRMCS User 1 (safety application) as part of the InterRegio train approaches station B coming from station A.
+
+Train FRMCS User 2 (safety application) as part of a high speed train passes station B coming from station C.
+
+Train FRMCS User 3 (safety application) as part of the parked train in station B that continuous later.
+
+Train FRMCS User as part of a mobile warning system protects a line section that is under construction.
+
+All train FRMCS Users (safety application) periodically report their current position to the ground FRMCS User (safety application).
+
+### 12.14.2.4 Post-conditions
+
+Every train approached his final destination.
+
+No harm to the ongoing construction work in station B.
+
+## 12.14.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.14.2-001] | <p>The consolidated positioning information i.e. the location information resulting from the combination of all positioning sources available to the FRMCS System shall support following absolute positioning accuracy based on the train speed at <math>\geq 90\%</math> of the occasions:</p> <p>0 - 40km/h Longitudinal: <math>\leq 1</math> m<br/>lateral: 1 - 3 m</p> <p>Up to 120km/h<br/>Longitudinal: <math>\leq 34</math>m lateral: 1 - 3 m</p> <p>Up to 160km/h<br/>Longitudinal: <math>\leq 45</math>m lateral: 1 - 3 m</p> <p>Up to 320km/h<br/>Longitudinal: <math>\leq 89</math>m lateral: 1 - 3 m</p> <p>Up to 500km/h<br/>Longitudinal: <math>\leq 200</math>m lateral: 1 - 3 m</p> <p>See [9]</p> | A/T | TS 22.261 | <p>TS 22.261 sub-clause 6.27.2<br/>TS 22.261 sub-clause 7.3.2 – refer to positioning service level 3 (only one speed limit supported – up to 500 km/h – with horizontal accuracy of 1m)</p> <p>TS 22.278 does not consider this requirement.</p> |
+| [R-12.14.2-002] | FRMCS System shall be able to support an initial positioning fix time of $\leq 5$ s. | A/T | TS 22.261 | <p>TS 22.261 sub-clause 7.3.2</p> <p>TS 22.278 does not consider this requirement.</p> |
+| [R-12.14.2-003] | To avoid large offsets between adjacent hazard areas due to limited track space in a railway station, FRMCS System shall be able to support a sampling interval between two positioning cycles of $< 1$ s. | A/T | Not covered | <p>TS 22.261<br/>TS 22.261 sub-clause 7.3.2 (Positioning service latency = 1 s)</p> <p>TS 22.278 does not consider this requirement.</p> |
+| [R-12.14.2-004] | FRMCS Equipment power consumption due to the use of positioning capabilities shall be minimised. | A/T | TS 22.261 | <p>TS 22.261 sub-clause 6.27.2 and 7.3.2.3 (location power saving mode with restriction in update rate)</p> <p>TS 22.278 does not consider this requirement.</p> |
+
+## 12.15 Use Case: FRMCS System security framework
+
+### 12.15.1 Introduction
+
+The security framework protects the FRMCS System against attacks and threats, like misuse, Denial of Service (DoS), unauthorized access to services, interception, man-in-the-middle attacks, replay attacks and intended data modification. It encompasses the protection of security attributes confidentiality, privacy, integrity, availability and non-reputation.
+
+## 12.15.2 Use case: FRMCS System security framework
+
+### 12.15.2.1 Description
+
+The security framework protects:
+
+- Services provided by the FRMCS System;
+- Bearer flexible access including 3GPP as well as non-3GPP access;
+- Direct interaction between FRMCS Equipment;
+- Interaction between the FRMCS end user devices and FRMCS network;
+- Interaction between FRMCS network functions;
+- Stored data within the FRMCS System;
+- Interworking between a FRMCS System and another FRMCS System;
+- Interworking between a FRMCS System and a legacy system.
+
+### 12.15.2.2 Pre-conditions
+
+FRMCS System is in use.
+
+### 12.15.2.3 Service flows
+
+FRMCS System security framework related service flows cover the following aspects:
+
+- identity management;
+- authentication;
+- authorization;
+- key management;
+- data protection (regarding integrity, confidentiality, privacy, non-reputation);
+- prevention of attacks;
+- detection of attacks;
+- reaction on detected attacks.
+
+### 12.15.2.4 Post-conditions
+
+The FRMCS System is protected.
+
+### 12.15.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.15.2-001] | The FRMCS System security framework shall enable the use of unique identities. | A | TS 22.228<br>TS 22.280 | A- TS 22.228 sub-clause 7.5.1<br>A- TS 22.280 [R-5.12-002] |
+| [R-12.15.2-002] | The FRMCS System security framework shall allow the grouping of identities. | A | TS 22.228<br>TS 22.280 | A- TS 22.228 sub-clause 7.5.1<br>A- TS 22.280 sub-clause 5.1.3, 5.12 |
+| [R-12.15.2-003] | The FRMCS System security framework shall provide mechanisms to authenticate a unique identity. | A/T | TS 22.278<br>TS 22.261<br>TS 22.228<br>TS 22.280 | T- TS 22.278 sub-clause 9.2<br>T- TS 22.261 sub-clause 8.3<br>A- TS 22.228 sub-clause 11.2, H 2.3, H 3.3, H 4.3<br>A- TS 22.280 sub-clause 5.12 |
+| [R-12.15.2-004] | The FRMCS System security framework shall provide authentication mechanisms required for the secured interaction between FRMCS network functions. | A/T | N/A | Implementation requirement |
+| [R-12.15.2-005] | The FRMCS System security framework shall provide mechanisms to authorise communications and the use of applications. | A | TS 22.280<br>TS 22.228 | sub-clauses:5.9a2, 5.12, 5.16, 5.19, 6.4.2, 6.4.5, 6.4.6, 6.6, 6.7, 6.8, 6.13, 6.19.1<br>TS 22.228: sub-clause 5 |
+| [R-12.15.2-006] | The FRMCS System security framework shall provide a management of identities, passwords and keys required for the protection of FRMCS User communication, the interaction between FRMCS network functions as well as subscribers and service related data. | A/T | TS 22.261<br>TS 22.280 | TS 22.261: Identity management (see section 8.5)<br>TS 22.280: Key management, profile management (see section 5.12)<br>Password management is an implementation requirement. |
+| [R-12.15.2-007] | The FRMCS System security framework shall be able to block the use of any FRMCS Equipment when it is detected as being stolen or lost. | A/T | TS 22.261<br>TS 22.280 | T TS 22.261 sub-clause 8.7<br>A TS 22.280 sub-clause 6.13.4 |
+| [R-12.15.2-008] | The FRMCS System security framework shall be able to unblock the use any recovered stolen or lost FRMCS Equipment. | A/T | TS 22.278<br>TS 22.261<br>TS 22.280 | T TS 22.261 sub-clause 8.7<br>A TS 22.280 sub-clause 6.13.4 |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------|-------------------------------------------------------|
+| [R-12.15.2-009] | The FRMCS System security framework shall protect the services provided by the FRMCS System; bearer flexible access including 3GPP as well as non-3GPP access; interaction between the FRMCS end user devices and FRMCS network; interaction between FRMCS network functions; stored data within the FRMCS System; interworking between a FRMCS System and another FRMCS System; Interworking between a FRMCS System and a legacy system. | A/T | TS 22.261<br>TS 22.280 | TS 22.261 sub-clause 8.2<br>TS 22.280: [R-6.13.6-001] |
+| [R-12.15.2-010] | The FRMCS System security framework shall prevent software based attacks which have an impact on any of the following security attributes:<br>data confidentiality;<br>information privacy;<br>data integrity;<br>non-repudiation of data;<br>FRMCS System availability. | T | N/A | Implementation requirement |
+| [R-12.15.2-011] | The FRMCS System security framework shall be able to detect software based attacks which have an impact on any of the following security attributes:<br>data confidentiality;<br>information privacy;<br>data integrity;<br>non-repudiation of data transfer;<br>FRMCS System availability. | T | N/A | Implementation requirement |
+| [R-12.15.2-012] | The FRMCS System security framework shall be able to react on detected software based attacks: which have an impact on any of the following security attributes:<br>data confidentiality;<br>information privacy;<br>data integrity;<br>non-repudiation of data transfer;<br>FRMCS System availability. | T | N/A | Implementation requirement |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|-----------------------------|
+| [R-12.15.2-013] | The FRMCS System security framework shall provide procedures and mechanisms for management of FRMCS System security. | T | N/A | Implementation requirement |
+| [R-12.15.2-014] | The FRMCS System security framework shall be able to track users' actions such as usage of communication services, management operations, configuration changes etc. | A | TS 22.280 | TS 22.280 sub-clause 6.15.4 |
+| [R-12.15.2-015] | The FRMCS System security framework shall be able to store security related data for post-analysis, e.g. forensic. | A | TS 22.280 | TS 22.280 sub-clause 6.15.4 |
+
+## 12.16 Use Case: Interworking to external networks
+
+### 12.16.1 Introduction
+
+This section describes the general interworking between FRMCS System, based on 3GPP transport and external communication/data networks.
+
+### 12.16.2 Use case: FRMCS System external network interworking
+
+#### 12.16.2.1 Description
+
+Apart from the communication facilities within one FRMCS network, FRMCS User(s) require as well communication facilities to and from other external networks. Thus an FRMCS System has to provide various communication facilities between FRMCS User(s) and external network user(s).
+
+The term “user” is hereby meant as either an individual or an application.
+
+The necessary interworking to external networks is able to provide incoming and outgoing voice- and data bearer services.
+
+The following are considered as external networks:
+
+- Public Switched Telephone Network (PSTN)
+- Private Telephone Network
+- Private Mobile Radio (PMR) or Land Mobile Radio (LMR): refer to section 12.6 for additional use cases to interworking between FRMCS and LMR.
+- Public Land Mobile network (PLMN)
+- Other GSM-R networks: refer to section 12.8 for additional use cases to interworking between FMCS and GSM-R.
+- Other FRMCS networks
+- Other Wireless Access
+
+- Other packet data networks, e.g. Internet.
+
+### 12.16.2.2 Pre-conditions
+
+The FRMCS User is attached to the FRMCS System.
+
+The external network user is attached to the external network.
+
+Authentication and authorization of the FRMCS User(s) and communications initiated by the FRMCS Users are managed within the FRMCS System.
+
+The required Quality of Service is managed by the FRMCS System.
+
+### 12.16.2.3 Service flows
+
+#### **Case 1 (Communication is to be established from FRMCS system towards an external network)**
+
+An entitled FRMCS User enters a destination address for establishment of a communication session. The destination address can be of the following formats:
+
+- E.164 address
+- Uniform Resource Identifier (URI) (e.g. SIP address, URL, e-mail address...)
+- EIRENE functional number
+- FRMCS Functional Identity
+- FRMCS User Identity
+- FRMCS subscriber identity
+
+Based on the destination address, the FRMCS System performs the following:
+
+- Detects the correct bearer type including characteristics
+- Translates the destination address to a routable format
+- Analyses if the destination is external to FRMCS System
+- Selects an available interconnection for the bearer type. (Interconnection selection can be either a direct or indirect connection, e.g. gateway)
+- Attempts to setup the communication session
+
+#### **Case 2 (Communication is to be established from an external network towards FRMCS system)**
+
+An external network user tries to establish a communication session towards an FRMCS User. The destination address can be of the following formats, depending of the capabilities of the external network:
+
+- E.164 address
+- Uniform Resource Identifier (URI) (e.g. SIP address, URL, e-mail address...)
+- FRMCS Functional Identity (other FRMCS networks)
+- FRMCS User Identity (other FRMCS networks)
+- FRMCS subscriber identity (other FRMCS networks)
+
+Based on the destination address, the FRMCS System does the following:
+
+- Locates user(s) within the FRMCS System to detect possible roaming case
+- Translates the destination address into a routable format
+- Detects the correct bearer characteristics
+- Establishes the communication session.
+
+#### 12.16.2.4 Post-conditions
+
+##### **Case1**
+
+An FRMCS User is able to establish voice and/or data communication with intended user(s) in an external network.
+
+##### **Case2**
+
+An external network user is able to establish voice and/or data communication with intended user(s) managed by the FRMCS System.
+
+## 12.16.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.16.2-001] | The FRMCS System shall provide means of regulated interworking (s) for telephony services to/from external public networks e.g. system administrator has the ability to restrict access telephony services to/from external networks. | T | Covered by TS 22.179<br>TS 22.280 | For GSM-R, covered in 22.179 [R-6.18.4.2-001-5].<br>For other MCX systems, covered in 22.280 [R-6.17.2-001-7]<br>For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.<br>For PLMN and PSTN, covered by 22.280 [R-6.17.3.2-002] |
+| [R-12.16.2-002] | The FRMCS System shall provide Packet switched (PS) interworking (s) to/from external networks. | T | Partly covered by TS 22.280 | For GSM-R and according to latest decision from UIC (see FRMCS project activities status report in ERIG#70 (July 2018), the requirement is not required. No use case has been identified by UIC ((E )GPRS EVC could not be connected to any FRMCS RBC).<br>For other MCX systems, covered in 22.280 [R-6.17.2-001-7].<br>For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.<br>For PLMN and PSTN, interworking is not covered. |
+| [R-12.16.2-003] | The FRMCS System shall provide the necessary signalling and voice codec adaptation in the context of interworking with external networks. | T | Partly covered by TS 22.179 | For GSM-R covered in 22.179 [R-6.18.4.2-005] For other MCX systems, not required.<br>For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.<br>For PLMN and PSTN, interworking is not covered |
+| [R-12.16.2-004] | The FRMCS System shall provide interworking for supplementary services related to the external network. | A | Not covered. | For other MCX systems, not applicable (other mechanisms are provided).<br>For LMR/PMR (e.g. TETRA, P25 and TIA-603-D refer to section 12.6.<br>For other external systems, not covered. |
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.16.2-005] | The FRMCS System shall provide interworking communication with external networks in a secured way. | A/T | Partly covered by TS 22.280 | For other MCX systems covered in 22.280 [R-6.17.2-001], [R-6.17.2-002], [R-6.17.2-007].<br>For LMR/PMR (e.g. TETRA, P25 and TIA-603-D) refer to section 12.6.<br>For PLMN and PSTN, interworking is not covered.<br>For other external systems, not covered. |
+| [R-12.16.2-006] | The FRMCS System shall provide interworking communication with external networks with the required Quality of Service. | T | Partly covered by TS 22.280 | For other MCX systems, not covered.<br>For GSM-R, covered by [R-6.17.3.1-002].<br>For LMR/PMR (e.g. TETRA, P25 and TIA-603-D) refer to section 12.6.<br>For PLMN and PSTN, interworking is not covered. |
+| [R-12.16.2-007] | The FRMCS System shall be able to select interconnection based on multiple interconnections of the same type (i.e. redundancy of physical/logical paths and transmission links for both control and user planes including load aggregation and/or warm stand-by techniques). | A/T | N/A (physical paths)<br>TS 22.280 | Implementation requirement for redundant physical paths.<br>Partly covered by clause 6.17.3.1 for GSM-R.<br>Load aggregation and/or warm stand-by techniques to be supported by the Interworking Function (IWF). |
+| [R-12.16.2-008] | The FRMCS System shall select the bearer characteristics based on exchanged signalling information (i.e. dynamic and automatic configuration of interconnections parameters). | T | TS 22.280 | Partly covered by clause 6.17.3.1 for GSM-R.<br>Dynamic and automatic configuration of interconnections parameters to be supported by the Interworking Function (IWF). |
+| [R-12.16.2-009] | The FRMCS System shall select the appropriate interconnection type, e.g. CS or PS based on the destination address of the target user. | T | N/A | For GSM-R, PS interworking is not required (see above). |
+
+## 12.17 Use Case: FRMCS On-network/Off-network communication
+
+### 12.17.1 Introduction
+
+Typical communication will involve the transport capabilities of the FRMCS network but some of the FRMCS communication scenarios require the use of Off-network bearer services. Also a combination of On-network and Off-
+
+network bearer services can increase the entire availability of the entire FRMCS transport system which is essential for railways especially in Automated Train Operation.
+
+This results into three global FRMCS communications modes:
+
+- On-network only communication
+- Off-network only communication
+- Combined On-network and Off-network communication.
+
+Note: The different types of communication use cases related to On-network and/or Off-network are summarised in Annex C.
+
+## 12.17.2 Use case: On-network/Off-network communication
+
+### 12.17.2.1 Description
+
+**On-network** only communication mode uses the bearer services that are provided by the FRMCS land mobile network. It relies on the flexible use of 3GPP and non 3GPP bearer services and allows user to user as well as multi-user communication.
+
+
+
+The diagram illustrates the on-network communication mode. On the left, a white circle with a thick black outline represents the Mobile FRMCS User (onboard). On the right, a solid black square represents the Ground FRMCS User (controller). A solid black arrow points from the mobile user to the ground user, indicating the direction of communication.
+
+Diagram of FRMCS On-network communication mode showing a Mobile FRMCS User (onboard) communicating with a Ground FRMCS User (controller).
+
+**Figure 12.17-1 FRMCS On-network communication mode**
+
+On-network communication is used for Mobile FRMCS User (onboard) to Ground FRMCS User (controller) communication.
+
+**Off-network** only communication mode uses a dedicated radio bearer service for proximity communication which is supported by FRMCS Equipment. It relies on an appropriate 3GPP bearer service that allows user to user as well as multi-user communication without direct involvement of FRMCS land mobile network. A relay function in Off-network communication mode can extend the range of the communication facilities. FRMCS Equipment may bridge a distance for proximity communications of up to 3km.
+
+
+
+The diagram illustrates the off-network communication mode. On the left, two solid black circles represent Mobile FRMCS Users (onboard). On the right, a solid black circle with a crosshair symbol represents the Ground FRMCS User (controller). Dashed arrows point from each mobile user to the ground user, indicating the direction of communication. A solid arrow points from the ground user to a third solid black circle on the far right, representing another mobile user or equipment.
+
+Diagram of FRMCS Off-network communication mode showing two Mobile FRMCS Users (onboard) communicating via a Ground FRMCS User (controller).
+
+**Figure 12.17-2: FRMCS Off-network communication mode**
+
+Off-network communication can be used for e.g. shunting or banking communication where not always a ground FRMCS User i.e. controller is necessary. Off-network communication provides also the backup if On-network communication is unavailable.
+
+**Combined On-and Off-network** communication mode encompasses the parallel use of the FRMCS land mobile network and the radio bearer service for proximity communication. There are various sub-categories for this communication mode:
+
+**Relay mode 1:** A FRMCS Equipment uses On-network and Off-network communication and constitutes an On- and Off-network relay function to other FRMCS Equipment's that are in Off-network only communication mode.
+
+
+
+Diagram of FRMCS Off-network communication mode. Two black circles on the left have dashed arrows pointing to a central circle with a black center. This central circle has a solid arrow pointing to a black square on the right.
+
+**Figure 12.17-3: FRMCS On-network and Off-network communication mode - Relay mode 1**
+
+On-network and off network communication mode relay mode 1 bridge over the coupling loss for FRMCS Users in a train that do not have access to the roof antenna. Hence, relay mode 1 helps to overcome radio link issues in a train.
+
+**Relay mode 2:** FRMCS equipment encompasses On-network and Off-network communication that enables Off-network bearer service for an Off-network only communication relay function.
+
+
+
+Diagram of FRMCS On-network and Off-network communication mode - Relay mode 1. Two black circles on the left have dashed arrows pointing to a central circle with a cross inside. This central circle has a dashed arrow pointing to a circle with a black center. This circle has a solid arrow pointing to a black square on the right.
+
+**Figure 12.17- 4: FRMCS On-network/Off-network communication mode - Relay mode 2**
+
+Relay mode 2 is an extension of relay mode 1 that allows e.g. the concatenation of maintenance teams during tunnel maintenance activities.
+
+**Relay mode 3:** FRMCS Equipment encompasses On-network and Off-network communication. Each FRMCS Equipment is able to constitute an On-network and Off-network relay function. Interworking between one and several of such relay functions allows the use of multipath transport facilities for communication purposes.
+
+
+
+Diagram illustrating FRMCS On-network-and Off-network communication mode - Relay mode 3. It shows three nodes: a top node (circle with a dot), a bottom-left node (circle with a dot), and a bottom-right node (solid black square). The top node has a dashed double-headed arrow to the bottom-left node and a solid double-headed arrow to the bottom-right node. The bottom-left node has a solid double-headed arrow to the bottom-right node.
+
+**Figure 12.17-5: FRMCS On-network-and Off-network communication mode - Relay mode 3**
+
+Relay mode 3 allows multipath transport facilities for FRMCS Applications that require extreme high communication reliability e.g. control command signaling applications like ATP.
+
+## 12.17.2.2 Pre-conditions
+
+### On-network only communication
+
+FRMCS Equipment is authorised to use On-network communication mode.
+
+FRMCS Users are attached to the FRMCS System and is authorised to establish user to user and/or multi-user communication.
+
+### Off-network only communication
+
+FRMCS Equipment is authorised to use Off-network only communication mode. Some of the FRMCS Equipment's are authorised to establish an Off-network communication relay function.
+
+The FRMCS Users are authorised to establish user to user and/or multi-user communication.
+
+### Combined On-network-and Off-network communication
+
+The FRMCS Users are authorised to establish user to user and/or multi-user communication.
+
+#### Relay Mode 1
+
+The FRMCS Equipment that supports in On-network/Off-network relay communication mode is authorised to establish Off-network communication to other FRMCS Equipment's which are in Off-network only communication mode.
+
+#### Relay Mode 2
+
+FRMCS Equipment that supports Off-network relay communication mode is authorised to establish a communication to other FRMCS Equipment's that are in Off-network communication mode. FRMCS Equipment that is in Off-network relay communication mode is authorised to establish an Off-network communication to an On-network and Off-network relay communication mode FRMCS Equipment.
+
+### **Relay Mode 3**
+
+FRMCS Equipment's in On-network and Off-network communication mode are authorised to establish On- and Off-network communications.
+
+## **12.17.2.3 Service flows**
+
+FRMCS Users are involved in the different types of communication modes establishes user to user and/or multi-user communications.
+
+### **On-network only communication**
+
+The FRMCS equipment establishes On-network only communication.
+
+### **Off-network only communication**
+
+The FRMCS Equipment in Off-network relay communication mode and the FRMCS Equipment's in Off-network communication mode establish the Off-network communication.
+
+### **Combined On-network-and Off-network communication**
+
+#### **Relay Mode 1**
+
+The FRMCS Equipment in On-network/Off-network communication mode establishes:
+
+- an On-network communication
+- Off-network communication to FRMCS Equipment's in Off-network only communication mode
+
+#### **Relay Mode 2**
+
+The FRMCS Equipment in On-network and Off-network communication mode establishes:
+
+- an On-network communication
+- Off-network communication to a FRMCS Equipment in Off-network relay communication mode
+
+The FRMCS equipment in Off-network relay communication mode establishes Off-network communication to FRMCS equipment's in Off-network only communication mode.
+
+#### **Relay Mode 3**
+
+The FRMCS equipment's in On-network and Off-network communication mode establishes:
+
+- an On-network communication
+- Off-network communication to a FRMCS Equipment in On-network-and Off-network relay communication mode.
+
+## **12.17.2.4 Post-conditions**
+
+### **On-network only communication**
+
+User-to-user and/or multi-user communication is established.
+
+### **Off-network only communication**
+
+User-to-user and/or multi-user communication is established.
+
+### **Combined On-network/Off-network communication**
+
+User-to-user and/or multi-user communication is established that encompasses both communication modes.
+
+## 12.17.2.5 Potential requirements and gap analysis
+
+| Reference Number | | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.17.2-001] | FRMCS security requirements according to chapter 12.15 shall apply to On-network and Off-network communication. | A/T | TS 22.278<br>TS 22.261<br>TS 22.228<br>TS 22.280 | Covered for on-network (refer to section 12.15). |
+| [R-12.17.2-002] | FRMCS QoS requirements (reference QoS section 12.10) shall apply to On-network and Off-network communication. | A/T | TS 22.261<br>TS 22.280<br>TS 22.289 | Covered for on-network (refer to section 12.10). |
+| [R-12.17.2-003] | FRMCS positioning accuracy requirements according to chapter 12.14 shall apply to On-network and Off-network communication. | A/T | TS 22.261 | Partly covered for on-network (refer to section 12.14). |
+| [R-12.17.2-004] | The FRMCS System requirements applicable for communication recording as specified in the recording and access application use cases shall apply to On-network and Off-network communication. | A/T | TS 22.280 | See gap analysis of sub-clause 6.10. |
+| [R-12.17.2-005] | FRMCS On-network communication shall support the flexible use of different radio bearers (see Bearer Flexibility). | A/T | TS 22.278<br>TS 22.261<br>TS 22.280 | TS 22.280<br>See sub-clauses in chapter 5 and 6 |
+| [R-12.17.2-006] | FRMCS Equipment shall support On-network only as well as On- and Off-network relay communication. | T | TS 22.278<br>TS 22.261<br>TS 22.280 | 22.278 – sub-clause 7A:<br>Mode 1 covered by ProSe UE-to-Network relay (single-hop relay with UE-to-Network relay UE between remote UE and gNb)<br>Mode 2 not covered by ProSe UE-to-UE Relay (multi-hop relays not covered)<br>Mode 3 not covered (multi-hop relays not covered).<br>22.261: UE-to-Network Relay not covered in 5GS.<br>22.280 [R-7.11-001]: use of off-net and on-net MCX Services simultaneously |
+| [R-12.17.2-007] | FRMCS shall be able to support Off-network communication that tide over a distance between FRMCS UE's of up to 3km. | T | TS 22.289 | Covered by table 5.2.2-2 (relevant for Off-Network MCData Service only) |
+
+| Reference Number | | Application / Transport | SA1 spec covering | Comments |
+|------------------|--------------------------------------------------------------------------------------------|-------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.17.2-008] | FRMCS Equipment shall support Off-network only as well as Off-network relay communication. | T | TS 22.278<br>TS 22.261<br>TS 22.280 | 22.278 – sub-clause 7A:<br>Mode 1 covered by ProSe UE-to-Network relay (single-hop relay with UE-to-Network relay UE between remote UE and gNb)<br>Mode 2 not covered by ProSe UE-to-UE Relay (multi-hop relays not covered)<br>Mode 3 not covered (multi-hop relays not covered).<br>22.261: UE-to-Network Relay not covered in 5GS.<br>22.280 [R-7.11-001]: use of off-net and on-net MCX Services simultaneously |
+
+## 12.18 Call restriction service
+
+### 12.18.1 Description
+
+Call restriction based on location information and/or user identity is widely used in China railway market. It is proposed that FRMCS supports this service. This service restricts calls outside specific area according to the location information and/or user identity.
+
+### 12.18.2 Pre-conditions
+
+FRMCS user is attached to the FRMCS system.
+
+### 12.18.3 Service Flows
+
+Scenario 1: The dispatcher calls the driver; the call shall be allowed in the area managed by the dispatcher according to the location information (i.e. calls outside area managed by dispatcher are restricted)
+
+Scenario 2: The user calls the dispatcher, whether the call is allowed or restricted depends on the user identity.
+
+### 12.18.4 Post-conditions
+
+If the driver is located within the area managed by the dispatcher, the call is allowed.
+
+If the driver is outside the area managed by the dispatcher, the call is restricted.
+
+Only an authorised user (e.g. the driver) is able to initiate the call to dispatcher, calls from other users to dispatcher will be restricted.
+
+## 12.18.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|----------------------------------------------------------------------------------------|
+| [R-12.18-001] | The FRMCS System shall be able to support the call restriction service taking into account the user identity and/or location information. | A | 22.280 | Covered by R-5.9a-020, R-5.9a-021, R-5.11-0XX, in particular R-5.11-007 and R-5.11-009 |
+
+## 12.19 Allocation and isolation of FRMCS communication resources
+
+### 12.19.1 Introduction
+
+Rail communication distinguishes between critical, performance and business applications. It is an essential task of the FRMCS System to support segregation of data transmission, in this context the isolation of railway application data utilizing the same available transport resources. The principle of segregation of data transmission applies to:
+
+- FRMCS communication infrastructure may be shared by multiple railway undertakings;
+- Different railway applications of one railway undertaking require isolated and customized communication resources (transport resources and functionalities) for each application.
+
+In general, it is anticipated that isolated transport services can be provided with a predictable and guaranteed QoS.
+
+### 12.19.2 Use case: Isolation of FRMCS communication resources
+
+#### 12.19.2.1 Description
+
+##### **Scenario 1: Isolation for individual railway undertakings**
+
+An FRMCS System infrastructure manager may have to host different railway undertakings. Due to isolation reasons, these railway undertakings require segregation of their communication and a predictable and guaranteed QoS.
+
+##### **Scenario 2: Isolation among categories of applications belonging to one railway undertaking**
+
+Railway community has classified their application to different categories, i.e. critical, performance and business. Due to isolation reasons, the related communications require segregation of data transmission having a predictable and guaranteed QoS for the different categories of applications.
+
+#### 12.19.2.2 Pre-conditions
+
+##### **General**
+
+Segregation of data transmission is supported by the FRMCS system.
+
+##### **Scenario 1: Isolation reasons for individual railway undertakings**
+
+Railway undertakings need their own segregated transport resources and network functionalities needed for their communications.
+
+##### **Scenario 2: Isolation among categories of applications belonging to one railway undertaking**
+
+Railway undertaking assigns each application category to their own segregated transport resources and network functionalities needed for their communications.
+
+### 12.19.2.3 Service flows
+
+#### **Scenario 1: Isolation reasons for individual railway undertakings**
+
+Each railway undertaking in a country utilises dedicated and isolated transport resources and network functionalities.
+
+#### **Scenario 2: Isolation among categories of applications belonging to one railway undertaking**
+
+Each application category of one railway undertaking utilises dedicated and isolated transport resources and network functionalities.
+
+### 12.19.2.4 Post-conditions
+
+#### **Scenario1**
+
+Each railway undertaking in a country obtains dedicated and segregated transport resources and network functionalities.
+
+#### **Scenario2**
+
+Each application category of one railway undertaking obtains dedicated and segregated transport resources and network functionalities.
+
+## 12.19.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|-------------------|-------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.19.2.5-001] | The FRMCS System shall be able to support the segregation of transport data for different application categories. | A/T | 22.261, clause 4 | “Flexible network operations are the mainstay of the 5G system. The capabilities to provide this flexibility include network slicing, network capability exposure, scalability, and diverse mobility. Other network operations requirements address the necessary control and data plane resource efficiencies, as well as network configurations that optimize service delivery by minimizing routing between end users and application servers.” |
+| [R-12.19.2.5-002] | The FRMCS System shall support dedicated QoS handling for segregation of transport data. | T | 22.261 clause 6.1.1 | “Network slicing allows the operator to provide customised networks. For example, there can be different requirements on functionality (e.g., priority, charging, policy control, security, and mobility), differences in performance requirements (e.g., latency, mobility, availability, reliability and data rates), or they can serve only specific users (e.g., MPS users, Public Safety users, corporate customers, roamers, or hosting an MVNO).” |
+
+## 12.20 FRMCS Equipment capabilities for multiple FRMCS Users
+
+### 12.20.1 Introduction
+
+For communication, rail vehicles today have a dedicated terminal approach. For each type of application, voice or data (e.g. ATP), one (1:1) or several mobile terminals (1: n) are used. Multiple Mobile Terminals for one application are required for operational or availability reasons.
+
+With the introduction of the FRMCS System, the number of applications will multiply. More recent train compositions already have a large number of sensors whose information is exchanged for control or diagnosis between the vehicle and the ground control centre.
+
+With the continuation of the 1:1 principle (application equals mobile terminal) this would correspond to a multiplication of the mobile terminals. In addition, the space required for mobile terminals and roof antennas would significantly increase.
+
+## 12.20.2 Description
+
+In the case of vehicle/train composition, FRMCS Users can take full advantage of the transport facilities of the 3GPP system while ensuring priority, latency and reliability for each communication. FRMCS User and the associated communication applications need to be decoupled from the FRMCS Equipment.
+
+## 12.20.3 Pre-conditions
+
+At least one FRMCS Equipment is installed at the vehicle/train that provides transport capabilities between vehicle/train to ground or vice versa.
+
+## 12.20.4 Service flows
+
+Multiple FRMCS Users starts communication, for example:
+
+- ATP;
+- ATO;
+- Sensor information exchange.
+
+## 12.20.5 Post-conditions
+
+FRMCS Users on the vehicle/train are able to communicate to FRMCS Users on the ground or to other vehicles/trains.
+
+## 12.20.6 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------|
+| [R-12.20.6-001] | Multiple FRMCS Users in the vehicle/train shall be able to use one FRMCS Equipment simultaneously. | A/T | TS 22.280 | TS 22.280 sub-clause 5.15 5.15-001 |
+| [R-12.20.6-002] | The service capabilities of an FRMCS Equipment shall be attributable individually to multiple FRMCS Users. | A/T | TS 22.280 | TS 22.280 [R-5.15-002] & [R-5.15-003] |
+| [R-12.20.6-003] | When an FRMCS Equipment is simultaneously used by multiple FRMCS Users, the communication for each of the FRMCS Users shall receive its required priority and QoS (latency and reliability) within the FRMCS System. | T | TS 22.280 | TS 22.280 [R-5.15-003] [ |
+| [R-12.20.6-004] | When an FRMCS Equipment is simultaneously used by multiple FRMCS Users, each of the FRMCS Users shall be individually addressable. | A | TS 22.280 | TS 22.280 [R-5.15-002] |
+
+## 12.21 FRMCS System/FRMCS User roaming capabilities
+
+### 12.21.1 Introduction
+
+FRMCS Roaming use cases address the ability for an FRMCS User to make use of FRMCS Applications when he is provided service by a network different from his Home FRMCS Network. A specific use case applies for FRMCS Functional Identities (see 12.21.3 use case).
+
+It is essential for the operation of international trains, transporting passenger or freight across borders, that FRMCS Users are using the capabilities and services of other FRMCS networks.
+
+The situations envisaged also encompass situations where trains are moving to an area where a dedicated FRMCS network has been deployed for an urban area, for a region, for a rail track operated by a different company in a tunnel, in a large industrial area.
+
+Other cases are pertinent for rail operation such as trains running in countries or regions where communications services provided by the local responsible Rail Infrastructure Manager are different from the one where they have subscription or where service can only be provided by a Public Mobile Network Operator.
+
+FRMCS Roaming capabilities are necessary to ensure that Railways Undertaking will be able to use a single FRMCS Equipment for their FRMCS Users while roaming.
+
+### 12.21.2 Use case: FRMCS User is relocating towards a Visited (FRMCS) Network
+
+#### 12.21.2.1 Description
+
+This use case addresses the situation where an FRMCS User is moving beyond the coverage of its Home FRMCS Network and where communications services can be provided by another Visited (FRMCS) Network. Following scenarios for an FRMCS User are:
+
+- Relocation from Home FRMCS Network to a Visited (FRMCS) Network and vice versa;
+- Relocation from a Visited (FRMCS) Network to another Visited (FRMCS) Network.
+
+#### 12.21.2.2 Pre-conditions
+
+The Visited (FRMCS) Network is capable to retrieve FRMCS Users information from applicable Home FRMCS network.
+
+#### 12.21.2.3 Service flows
+
+FRMCS User is relocating from Home FRMCS Network to Visited (FRMCS) Network, or from a Visited (FRMCS) Network to another Visited (FRMCS) Network.
+
+FRMCS User makes use of FRMCS Applications that are applicable in the Home FRMCS Network and the FRMCS Application that are applicable in the Visited (FRMCS) Network.
+
+#### 12.21.2.4 Post-conditions
+
+FRMCS User is able to use FRMCS Applications after relocating to a Visited (FRMCS) Network.
+
+FRMCS User has not experienced service interruption of FRMCS Application while relocating.
+
+## 12.21.2.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------|---------------------------------------------------------------------|
+| [R-12.21.2-001] | The FRMCS System shall provide the technical means to allow communication services between FRMCS Users that are belonging to different administrative realms of the FRMCS System i.e. Home FRMCS Network and Visited (FRMCS) Network. | A/T | T TS 22.261<br>A TS 22.280 | T sub-clause 5.1.2.1<br>T sub-clause 5.1.2.2<br>A sub-clause 6.17.2 |
+| [R-12.21.2-002] | The FRMCS System shall provide communication services to FRMCS Users visiting another administrative realm i.e. Visited (FRMCS) Network. | A/T | T TS 22.261<br>A TS 22.280 | T sub-clause 5.1.2.1<br>T sub-clause 5.1.2.2<br>A sub-clause 6.17.2 |
+| [R-12.21.2-003] | The FRMCS System shall support a mechanism for an administrator to determine if a FRMCS User is able to use communication services in the Visited (FRMCS) Network. | A/T | T TS 22.261<br>A TS 22.280 | T sub-clause 5.1.2.1<br>A sub-clause 6.17.2 |
+| [R-12.21.2-004] | The FRMCS System shall be able to provide service continuity when relocating between FRMCS Network without the FRMCS User noticing the change. | A/T | T TS 22.261<br>A TS 22.280 | T sub-clause 6.18.2<br>A sub-clause 6.17.2 |
+| [R-12.21.2-005] | The FRMCS system shall be able to provide the same Quality of Service for the use of FRMCS Applications regardless of whether the FRMCS User is using the Home FRMCS Network or Visited (FRMCS) Network. | A/T | T TS 22.261<br>A TS 22.280 | T sub-clause 5.1.2.1<br>A sub-clause 6.17.2 |
+
+## 12.21.3 Use case: Functional Identities in FRMCS Roaming situations
+
+### 12.21.3.1 Description
+
+This use case addresses the situation where an FRMCS User or FRMCS Equipment is moving beyond the coverage of its Home FRMCS Network and where communications services can be provided by another Visited (FRMCS) Network.
+
+An FRMCS User or FRMCS Equipment in FRMCS Roaming situations (referring to 12.21.2 use case) shall be able to make use of FRMCS Functional Identities, from its Home FRMCS Network and, when applicable, from Visited (FRMCS) Networks. For instance, an FRMCS User or FRMCS Equipment in a train can be registered to a permanent FRMCS Functional Identity with its Home FRMCS Network (associated with the engine), and an FRMCS Functional Identity registered with a Visited (FRMCS) Network. For train cross border operations (e.g. FRMCS Roaming situations), some registered FRMCS Functional Identities shall remain valid for the duration of the train international run, the same FRMCS Functional Identity keeping the same association to FRMCS Equipment while border crossing.
+
+Each FRMCS Network shall maintain its own FRMCS Functional Identity addressing scheme. For the purpose of FRMCS roaming, an international FRMCS Functional Identity scheme will be used and national scheme will align on it. If a train (e.g. an FRMCS User) is involved in cross border operation, the FRMCS System shall detect automatically if an activated FRMCS Functional Identity requires a re-association to the local applicable addressing domain. The responsible local functional addressing entity in the Visiting (FRMCS) Network aligns the Home FRMCS Network functional addressing entity about FRMCS Functional Identity re-association. The activation status of the re-associated FRMCS Functional Identity will be aligned accordingly. The responsible entity of the functional address is keeping the status (active/inactive).
+
+### 12.21.3.2 Pre-conditions
+
+FRMCS User is registered to at least one FRMCS Functional Identity F1 with its Home FRMCS Network.
+
+FRMCS Equipment is associated with a permanent Functional Identity administrated by the Home FRMCS Network.
+
+The Visited (FRMCS) Network is capable to retrieve FRMCS Users information from applicable Home FRMCS network.
+
+### 12.21.3.3 Service flows
+
+FRMCS User is relocating from Home FRMCS Network to Visited (FRMCS) Network, or from a Visited (FRMCS) Network to another Visited (FRMCS) Network.
+
+FRMCS Users and FRMCS Equipment register to at least one FRMCS Functional Identity F2 with the Visited (FRMCS) Network.
+
+FRMCS User makes use of FRMCS Functional Identities associated with the Home FRMCS Network, at least F1, and the FRMCS Functional Identities associated with the Visited (FRMCS) Network, at least F2.
+
+### 12.21.3.4 Post-conditions
+
+An FRMCS User and FRMCS Equipment in FRMCS Roaming situations are able to use FRMCS Functional Identities associated with both Home FRMCS Network and Visited (FRMCS) Networks.
+
+### 12.21.3.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.21.3-001] | The FRMCS System shall be able to establish communication services based on FRMCS Functional Identity(ies) between FRMCS Users or FRMCS Equipment associated with different FRMCS Networks. | A/T | TS 22.280 | For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]<br>Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a] |
+| [R-12.21.3-002] | The FRMCS System shall be able to establish a communication services based on FRMCS Functional Identity(ies) associated with different FRMCS Networks. | A/T | TS 22.280 | For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]<br>Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a] |
+| [R-12.21.3-003] | The FRMCS System shall provide the necessary means for a FRMCS User or FRMCS Equipment to register and deregister FRMCS Functional Identity(ies) with the Home FRMCS Network and/or with the Visited (FRMCS) network. | A/T | TS 22.280 | For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]<br>Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a] |
+| [R-12.21.3-004] | When the FRMCS User or FRMCS Equipment is relocating between networks, the FRMCS System shall provide a mechanism to perform necessary registration/deregistration of one or multiple FRMCS Functional Identity(ies) with the Visited (FRMCS) Network operator and inform the Home FRMCS Network. | A/T | TS 22.280 | For communication TS 22.280, subclause 6.17.2 requirements [R-6.17.2-004] , [R-6.17.2-005], [R-6.17.2-006]<br>Functional alias: TS 22.280 subclause 5.9a, requirements [R-5.9a-001] up to [R-5.9a-002a] |
+
+## 12.22 Use case: Availability – increasing measures
+
+### 12.22.1 Description
+
+In some regions railways are a major constituent for the economy. Disturbance in the complex railway system can have a significant impact for example in the manufacturing process if components cannot be delivered in-time. There are significant improvements in train punctuality and track utilisation by using Automatic Train Protection (ATP) systems. Unavailability of the FRMCS System, FRMCS sub-systems or simple components can cause a significant impact to railway operation.
+
+ATP provides different levels of operation. The moving block mode is the most demanding one that requires multiple times more information in one second, e.g., position reports from the train towards the ground controlling entity which computes continuously the risk that consecutive trains can collide.
+
+In order to minimise the risk of FRMCS System unavailability, Single Point of Failures (SPOF) need to be eliminated. There are different strategies such as duplication of components, subsystems or the entire system. The mode of system redundancy ranges from hot-standby, warm-standby to cold-standby. Hot-standby is the most demanding mode and requires an instantaneous continuation of the end-to-end service. Also the use of only one spectrum block represents a SPOF. In case one spectrum block become unavailable due to wideband jamming or similar, the FRMCS System needs to be able to make flexible use of spectrum to minimize the risk of radio path unavailability.
+
+FRMCS System or sub-system maintenance may cause outages of some minutes or hours. Today, a high utilisation of rail tracks already reduces the number of maintenance windows. A redundant deployment of the radio access sub-system allows continuation of rail operation while one part of radio access sub-system is under maintenance.
+
+## 12.22.2 Pre-conditions
+
+The basis for setting up the FRMCS System takes into account the elimination of Single Point Of Failure which encompasses:
+
+- Usage of multiple independent spectrum blocks;
+- Duplication of system functionalities/entities of the FRMCS System.
+
+## 12.22.3 Service flows
+
+### Case 1:
+
+During train control operation, some portion of the used spectrum block is disturbed, e.g., through interference from an external source.
+
+### Case 2:
+
+During train control operation a FRMCS sub-system fails or has been put under maintenance.
+
+## 12.22.4 Post-conditions
+
+The communication service continues without interruption.
+
+Train operation efficiency is not affected in any way despite the disturbances caused by:
+
+- Interference (intentional or unintentional);
+- Unavailability of FRMCS sub-systems due to planned (maintenance) or unplanned (outage) reasons.
+
+## 12.22.5 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.22-001] | The FRMCS System shall be able to provide a mechanism to allow redundancy of transmission paths making use of multiple spectrum blocks. | T | Covered in TS 22.261 chapter 7.2 by referring to TS 22.289 | The reliability figures for rail is included in 22.289 (KPI for rail) and referenced in 22.261 sub-clause 7.2 on low latency and high reliability. |
+| [R-12.22-002] | The FRMCS System shall provide a mechanism that minimizes the risk of single point of failure. | A/T | Covered in TS 22.261 chapter 7.2 by referring to TS 22.289 | The reliability figures for rail is included in 22.289 (KPI for rail) and referenced in 22.261 sub-clause 7.2 on low latency and high reliability. |
+
+## 12.23 Use case: Flexible use of available contiguous spectrum block(s) and related bandwidth(s)
+
+### 12.23.1 Introduction
+
+Globally, different contiguous spectrum block(s) with related bandwidth(s) may be available for rail communication in different areas. An FRMCS Equipment may also support different contiguous spectrum block(s) with related bandwidth(s) than the infrastructure deployed in the area. The use case addresses the general requirements related to the ability of the FRMCS System to flexibly use the maximum extent of rail spectrum available in an area, also considering the capabilities of the FRMCS Equipment that is served.
+
+### 12.23.2 Description
+
+It is essential that the FRMCS system can flexibly utilize the available bandwidth of the contiguous spectrum block(s), for both On-network and Off-network communication, also considering the contiguous spectrum block(s) and related bandwidth(s) supported by served FRMCS Equipment.
+
+### 12.23.3 Pre-conditions
+
+In certain areas, specific contiguous spectrum block(s) and related bandwidth(s) are available for rail communication. An FRMCS Equipment served in the area supports (possibly different) specific contiguous spectrum block(s) and their related bandwidth(s).
+
+### 12.23.4 Service flows
+
+The FRMCS System obtains information about the specific contiguous spectrum block(s) and their related bandwidth(s) supported by the FRMCS Equipment.
+
+The FRMCS System allocates the locally available contiguous spectrum block(s) and their related bandwidth(s), and serves FRMCS Equipment according to its supported contiguous spectrum block(s) and their related bandwidth(s).
+
+### 12.23.5 Post-conditions
+
+The FRMCS System is able to flexibly use the maximum extent of rail spectrum available in a given area, also considering the capabilities of the FRMCS Equipment that is served.
+
+### 12.23.6 Potential requirements and gap analysis
+
+| Reference Number | Requirement text | Application / Transport | SA1 spec covering | Comments |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------|
+| [R-12.23-001] | The FRMCS System shall be able to support for individual contiguous spectrum blocks, bandwidths less than 5 MHz (e.g. 1.4 MHz or 3 MHz). | T | N/A | Covered by RAN specifications: <ul style="list-style-type: none"> <li>Covered by E-UTRA,</li> <li>Not covered by NR.</li> </ul> |
+
+## 13 Potential New Requirements
+
+This chapter lists the potential new requirements that have been considered for introduction in Rel-15 normative specifications. Only parts of “9.3 Role management and presence” and “9.7 Multiuser talker control related use cases” were introduced. All other requirements identified in the TR above but not listed below are not covered in Rel-15.
+
+The third column “SA1 spec covering” identifies the specification and the requirement number within that specification where the 22.889 requirement with the number as specified in the first column of the table is covered. The fourth column provide additional explanation if needed.
+
+---
+
+## 14 Conclusion and Recommendations
+
+This TR provides use cases and potential requirements for Railway Communication. It is proposed to start normative work based on these potential requirements.
+
+Where applicable, it is proposed to include the requirements identified by this work into the set of existing stage 1 missing critical and other specifications.
+
+Requirements not fitting to any existing specification are proposed to go into a new TS.
+
+## Annex A: Examples of Role management
+
+This annex gives some examples on how Role management is used in the railway environment. This is to better understand the use.
+
+### Functional identity
+
+Every operational railway function e.g. train driver, a shunter or Controller is identified by their functions. A non-exhaustive list is provided in the table underneath.
+
+| <b>Functional identities</b> |
+|----------------------------------|
+| Leading train driver |
+| Driver 2 |
+| Driver 3 |
+| Shunting leader |
+| Shunting member |
+| Track side maintenance leader |
+| Track side maintenance member |
+| Primary train controller |
+| Secondary train controller |
+| Power controller |
+| Shunting controller |
+| Trackside maintenance controller |
+| Platform inspector |
+| Public announcement |
+| Chief conductor |
+| Second conductor |
+| Third conductor |
+| Catering staff chief |
+| Diagnostics |
+
+In order to make a function of a user known to other users, the user has to register itself to a specific functional identity.
+
+For example, user can be authorised by the railway undertaking to be a train driver (functional Role) of a train. When the Driver starts the scheduled train ride, from A to B at time x, the train running schedule assigns a specific train running number for this train. In principle the train keeps this number for the complete journey. The train driver uses his communication equipment to register himself, as the leading train driver (functional Role), of train number 123 (functional identity). After registration the train driver is now registered to the FRMCS System as the leading train driver of train 123. In some cases there can be multiple Drivers on one train, so the individual Drivers can register themselves accordingly.
+
+### FRMCS Equipment Type
+
+The equipment used in the railway environment can be very specific. The FRMCS Equipment is constituted of an UE and the FRMCS Application on this UE. This depends on the location and situation the equipment is used. The following different equipment types can be used, as an example:
+
+| <b>Equipment type</b> | <b>Equipment Capabilities<br/>(Examples)</b> |
+|-----------------------------|--------------------------------------------------------------------------------------|
+| Cabin radio | Emergency button, external loudspeaker |
+| Shunting radio | Loudspeaker, hands free |
+| Trackside maintenance radio | |
+| Security staff radio | Emergency button, public emergency call button |
+| Catering staff radio | |
+| Train controller device | Emergency button, call to maintenance staff button, call to power controllers button |
+| Shunting controller device | |
+| Sensor | No HMI |
+
+These different types of FRMCS Equipment are relevant for the registration process of functional identities. For example a train driver cannot register to a functional identity using a FRMCS Equipment which is not fit for the train driver to perform his Role. So a train driver cannot perform a registration as train driver of train 123 if he uses a catering staff FRMCS Equipment (where there is no train emergency button available, no loudspeaker and handset, etc.). The registration request will be rejected by the FRMCS System.
+
+The FRMCS Equipment shall also be reachable based on the identity of the FRMCS Equipment. For example the cabin radio of a specific train can be reached by their FRMCS Equipment Identity.
+
+### **FRMCS User identity**
+
+The railway employee (a specific person) is also reachable even if no functional identity has been assigned. This is done by using a unique FRMCS User identity. This can be an E.164 number, any other number according to a specific railways numbering plan or by fully qualified domain names (FQDN). Such a number or FQDN is dedicated/ assigned to a specific railway employee. After the employee has performed the log-in procedure to the FRMCS System, he is reachable via his individual FRMCS User identity.
+
+## Annex B: Minimum functional and performance requirements for FRMCS from a perspective of Korea LTE-based railway services
+
+In this annex, minimum functional and performance requirements [5]-[6] are introduced for FRMCS from a perspective of Korea's LTE-based railway services. Here, the term 'minimum' is used from the fact that the requirements are expected to be satisfied even with previous Rel. version of 3GPP LTE. Specifically, all the functionalities and performance requirements except for the high speed (500km/h) listed in the above have been shown to be fully supported by LTE Rel. 9, which have been validated in a commercial railway with a length of 54.2km [7]. Also, train control service named as Korea Radio-Based Train Control System (KRTCS) has been shown to be feasible by handling priorities among multiple data, where the level of KRTCS is equivalent to European Train Control System (ETCS) level 3 in a train control perspective. All the specific test scenarios regarding functional and performance requirements including KRTCS have been validated in a commercial railway [8]. For promising FRMCS supporting LTE Rel. 15, more enhanced and sophisticated requirements should be provided. In that sense, these requirements can be considered as basic functional and performance requirements for FRMCS.
+
+### Minimum functional requirements
+
+In a communication perspective, the followings can be minimum functional requirements for LTE based railway communication systems. The contents of each function and each digital radio equipment are described in detail in [5]-[6].
+
+| Service | Detailed service | Description | Mandatory/Optional |
+|----------------------|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| <b>Voice service</b> | <b>Individual voice call</b> | <b>The system shall support voice calling between two callers.</b> | <b>M</b> |
+| | <b>Public emergency</b> | <b>The system shall allow the user to make a public emergency call.</b> | <b>M</b> |
+| | <b>Broadcasting voice call</b> | <b>The system shall support a broadcasting call.</b> | <b>M</b> |
+| | <b>Group voice call</b> | <b>The system shall support a group call.</b> | <b>M</b> |
+| | <b>Multi-party voice call</b> | <b>The system shall support a multi-party call between at least 3 different parties.</b> | <b>M</b> |
+| <b>Data service</b> | <b>Multimedia message service</b> | <b>The network shall support point-to-point and point-to-multi-point message transmission from the ground to mobile radio equipment users.</b> | <b>M</b> |
+| | <b>General data service</b> | <b>The system shall support broadband data communication between ground and mobile radio equipment users.</b> | <b>M</b> |
+| | <b>Train control service</b> | <b>The system shall support seamless data communication for stable train control.</b> | <b>M</b> |
+
+| Service | Detailed service | Description | Mandatory/Optional |
+|-----------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| <b>Video service</b> | <b>Individual video call</b> | <b>The system shall support video calling between two callers.</b> | <b>M</b> |
+| | <b>Group video call</b> | <b>The system shall support group video calling.</b> | <b>M</b> |
+| | <b>Video information transmission</b> | <b>The system shall support the video information transmission function related to safe train operation.</b> | <b>M</b> |
+| <b>Call related service</b> | <b>Receiver /Caller ID display</b> | <b>The equipment shall display the receiver or caller ID in the form of a standard telephone number.</b> | <b>M</b> |
+| | <b>Receiver /caller ID display restriction</b> | <b>The system shall allow the ID of a specific user to be prevented from being displayed on the mobile radio equipment.</b> | <b>O</b> |
+| | <b>Priority and preemptive right</b> | <b>A function in which a call is allocated to the member who has top priority among the members who have different priority levels shall be provided.</b> | <b>M</b> |
+| | <b>Closed user group</b> | <b>The user group who can access the Korean railway integrated radio network from outside shall be restricted.</b> | <b>M</b> |
+| | <b>Call transfer</b> | <b>The incoming call or data message for one user shall be transferred to other devices in the network.</b> | <b>M</b> |
+| | <b>Call holding</b> | <b>The network shall allow the user to hold a call temporarily from an existing call.</b> | <b>M</b> |
+| | <b>Call waiting</b> | <b>The network shall be able to notify the user of the existing call that another user is attempting to access.</b> | <b>M</b> |
+| | <b>Charging information</b> | <b>When there is a network service charge, the network shall be able to provide the information on call charge and ongoing call charges.</b> | <b>O</b> |
+| | <b>Call restriction</b> | <b>The system shall be able to restrict a call using the network management or maintenance facility.</b> | <b>M</b> |
+| | <b>Automatic answering service</b> | <b>A call shall be answered automatically according to the priority of an incoming call.</b> | <b>M</b> |
+| | <b>All voice/ Video call recording</b> | <b>A call shall be answered automatically according to the priority of an incoming call.</b> | <b>M</b> |
+
+| Service | Detailed service | Description | Mandatory/Optional |
+|------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| <b>Railway specialized service</b> | <b>Functional addressing</b> | The system shall provide the addressing system in which the Controller can set communication with the train driver | <b>M</b> |
+| | <b>Location-dependent addressing</b> | The system shall provide the location-dependent addressing system in order to identify the destination number, which varies depending on the location of users | <b>M</b> |
+| | <b>Railway emergency</b> | The network shall provide the system to handle a voice call with high priority for a railway emergency call | <b>M</b> |
+| | <b>Shunting mode</b> | The network shall provide the system to regulate and control the user's access to the function and features of mobile radio equipment being used for shunting mode communication | <b>M</b> |
+| | <b>Direct communication</b> | The system shall support direct communication between terminals in the event that an LTE-based railway communication service is not normally available due to a failure in gNB | <b>O</b> |
+
+### Minimum performance requirements
+
+In the following table, specific performance requirements are listed as a base line of performance requirements for real FRMCS. The detailed performance of a railway communications system and the contents of the interface for each equipment are described in detail in [5]-[6].
+
+| Items | Description | Remarks |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|
+| <b>Coverage and performance</b> | <p>Coverage shall be continuous from a time and space perspective, and the temporal and spatial range to guarantee stability shall be more than 98% based on the vehicle being equipped with an external antenna.</p> <p>The network shall be able to accommodate the mobile terminal for railway communication.</p> <p>The system shall be able to provide communication when moving at track speed limit or 500 km/h, whichever is lower.</p> | |
+| <b>Call setting time</b> | <p>Railway emergency call < 1s (90%), < 2s (99% or more)</p> <p>Broadcasting or group call < 1s (90%), < 2.5s (99% or more)</p> | <p>*</p> <p><b>External PSTN connection not</b></p> |
+| <b>Handover</b> | The network shall be able to have seamless data transmission. and the handover success rate shall be 99%. | |
+| <b>Call access success</b> | The call access success rate shall be 99% or more. | |
+| <b>Connection drop rate</b> | The system shall be able to guarantee a call disconnection rate less than 0.01 times per hour during a lengthy call | |
+| <b>Train control data transmission</b> | The network shall guarantee more than 99% data reliability to transmit data for train control. | |
+| <b>Network redundancy</b> | The network including eNb equipment, core equipment and server shall be designed to be redundant for stability and availability. | However, the application scope of redundancy is determined by the operator. |
+| <b>Broadcasting and group call area</b> | Radio equipment in a restricted area can participate in broadcasting and group call, and the radio equipment out of broadcasting and group call area during call shall be excluded from call. | |
+
+## Annex C: Applicability to On-network/Off-network communication
+
+The different types of communication and support applications related to On-Network and Off-Network are covered by the table below:
+
+| Section | Use case | Applicability to On-Network | Applicability to Off-Network |
+|---------|----------|-----------------------------|------------------------------|
+|---------|----------|-----------------------------|------------------------------|
+
+| | | | |
+|------|--------------------------------------------------------------------------------------------------------|-----|----------------|
+| 5.3 | Power on the UE | Yes | Not applicable |
+| 5.4 | Access to the FRMCS System to activate the FRMCS Equipment | Yes | Not applicable |
+| 5.5 | Controlled power down of UE | Yes | Not applicable |
+| 5.6 | Uncontrolled power down UE | Yes | Not applicable |
+| 6.2 | Multi-train voice communication for Drivers and Ground FRMCS User(s) | Yes | Yes |
+| 6.3 | On-train outgoing voice communication from the Driver towards the Controller(s) of the train | Yes | No |
+| 6.4 | Railway emergency communication | Yes | No |
+| 6.5 | Automatic Train Protection (ATP) support by the FRMCS System | Yes | No |
+| 6.6 | Trackside Maintenance Warning System communication | | |
+| | 6.6.2 | Yes | Yes |
+| | 6.6.3 | Yes | Yes |
+| 6.7 | Pushed Real Time Video streaming | Yes | No |
+| 6.8 | Public emergency call | Yes | No |
+| 6.9 | Data communication for possession management | Yes | No |
+| 6.10 | Recording of communication | | |
+| | 6.10.2 | Yes | Yes |
+| 6.11 | Remote control of engines communication | | |
+| | 6.11.2 | Yes | Yes |
+| 6.12 | Automatic Train Operation data communication | | |
+| | 6.12.3 | Yes | Yes |
+| 6.13 | Monitoring and control of critical infrastructure | Yes | No |
+| 6.14 | Data transmission in real time | Yes | No |
+| 6.15 | On-train incoming voice or video communication from the Controller(s) of the train towards the drivers | Yes | No |
+| 6.16 | Data communication for Train Operation System Communication | | |
+| | 6.16.2 | Yes | No |
+| | 6.16.3 | Yes | Yes |
+| | 6.16.4 | Yes | Yes |
+| 6.17 | On-train safety device to ground communication | Yes | No |
+| 6.18 | Train Integrity monitoring data communication | | |
+| | 6.18.2 | Yes | Yes |
+
+| | | | |
+|--------|------------------------------------------------------------------------------|-----|-----|
+| 6.19 | Broadcast of public emergency warning information | Yes | No |
+| 6.20 | Safety related Critical advisory messaging | | |
+| 6.20.2 | | Yes | Yes |
+| 6.20.3 | | Yes | No |
+| 6.21 | Automatic Train Protection data communication | Yes | No |
+| 6.22 | Voice communication transfer | Yes | No |
+| 7.1 | Transmission of real time video | Yes | No |
+| 7.2 | Transfer of CCTV archives | Yes | No |
+| 7.3 | Massive Inter-carriage data transfer | Yes | Yes |
+| 7.5 | On-train outgoing voice communication from train staff towards a ground user | Yes | No |
+| 8.2 | Live streaming of multimedia | Yes | Yes |
+| 8.3 | Bulk transfer of multimedia from ground to train | Yes | Yes |
+| 9.2 | Assured voice communication (AVC) | | |
+| 9.2.2 | | Yes | Yes |
+| 9.2.3 | | Yes | Yes |
+| 9.2.4 | | Yes | Yes |
+| 9.2.5 | | Yes | Yes |
+| 9.3 | Functional identities and role management | | |
+| 9.3.3 | | Yes | Yes |
+| 9.3.4 | | Yes | Yes |
+| 9.3.5 | | Yes | Yes |
+| 9.3.6 | | Yes | Yes |
+| 9.3.7 | | Yes | Yes |
+| 9.3.8 | | Yes | Yes |
+| 9.3.9 | | Yes | No |
+| 9.4 | Location services | | |
+
+| | | | |
+|-------|----------------------------------------------|-----|------------------|
+| | 9.4.2 | Yes | Yes |
+| | 9.4.3 | Yes | Yes |
+| | 9.4.4 | Yes | Yes |
+| 9.5 | FRMCS-user communication handling | | |
+| | 9.5.2 | Yes | Yes |
+| | 9.5.3 | Yes | Yes |
+| | 9.5.4 | Yes | Yes |
+| | 9.5.5 | Yes | Yes |
+| | 9.5.6 | Yes | Yes |
+| 9.7 | Multiuser talker control | | |
+| | 9.7.2 | Yes | Yes |
+| | 9.7.3 | Yes | Yes |
+| | 9.7.4 | Yes | Yes |
+| | 9.7.5 | Yes | Yes |
+| | 9.7.6 | Yes | Yes |
+| 9.8.1 | Robust mission critical group communications | Yes | Yes |
+| 9.8 | Authorisation of communication | | |
+| | 9.8.2 | Yes | Yes |
+| 9.9 | Authorisation of application | | |
+| | 9.9.2 | Yes | Yes <sup>a</sup> |
+| | 9.9.1 | Yes | Yes |
+| 9.10 | Sharing FRMCS Equipment by FRMCS Users | Yes | Yes |
+| 9.11 | FRMCS naming authority | Yes | No |
+| 9.12 | Wayside-Centric Automatic Train Control | Yes | No |
+| 9.13 | Autonomous Train Control and Operation | Yes | Yes |
+
+<sup>a</sup> A default profile shall be considered.
+
+| | | | |
+|------|-----------------------------------------------------------------------------|-------------|-------------|
+| | | | |
+| 9.14 | Virtual Coupling | Yes | Yes |
+| 9.15 | Composite-based train operation | Yes | Yes |
+| 9.16 | Arbitration<br><br>9.16.2 | <br><br>Yes | <br><br>Yes |
+| 9.17 | Data communication to exchange key information for train safety application | Yes | No |
+| 11.1 | Charging and Billing information | Yes | No |
+
+**Table C-1. Applicability to On-network/Off-network to use cases.**
+
+## Annex D: Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-09 | SA#89 | - | - | - | - | Created from TR 22.889, same technical content as TR 22.889 v.17.3.0 | 18.0.0 |
+| 2021-03 | SA#91e | SP-210200 | 0001 | 1 | D | Align TR with SA1 drafting rules on Inclusive Language | 18.1.0 |
+| 2021-03 | SA#91e | SP-210223 | 0002 | 1 | C | Changes to Critical Support Applications "Inviting-a-FRMCS User to a voice communication" use case | 18.1.0 |
+| 2021-03 | SA#91e | SP-210223 | 0003 | 1 | C | Merging of Railway Emergency Communications | 18.1.0 |
+| 2021-09 | SA#93e | SP-211049 | 0004 | 1 | C | Changes to Critical Support Applications Inviting-a-FRMCS User to a voice communication use case to support Interworking with GSM-R | 18.2.0 |
+| 2021-09 | SA#93e | SP-211049 | 0006 | 1 | C | Changes to Critical Support Applications Multiuser talker control use case to support configurable initial talker permission | 18.2.0 |
+| 2021-12 | SP-94 | SP-211489 | 0008 | 2 | C | Triggering a change of communication privileges for a particular FRMCS User based on identities and/or talker status | 18.3.0 |
+| 2021-12 | SP-94 | SP-211489 | 0009 | | C | Arbitration: automatic answer | 18.3.0 |
+| 2021-12 | SP-94 | SP-211489 | 0010 | 2 | C | Alignment between Changing conditions of Railway Emergency Alert and Merging Railway Emergency Alert | 18.3.0 |
+| 2021-12 | SP-94 | SP-211489 | 0011 | | C | Service interworking between FRMCS and GSM-R of presence is no more required | 18.3.0 |
+| 2022-03 | SP#95e | SP-220079 | 0012 | 1 | B | Adding MCX Service Ad hoc Group Communication as alternative capability to support Railway Emergency Communication | 18.4.0 |
+| 2022-06 | SA#96 | SP-220430 | 15 | 1 | F | Call restriction based on subparts of functional identities | 18.5.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/22_series/22990/08e28a86c71221f509c8f3a828e89af2_img.jpg b/marked/Rel-18/22_series/22990/08e28a86c71221f509c8f3a828e89af2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01e890687e5c348ff59c3fd55263577ca4cd0755
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/08e28a86c71221f509c8f3a828e89af2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:838c2a56f8c7aa15be7977f2c5781d4ec581418b327d9087e35c6d8607374096
+size 115420
diff --git a/marked/Rel-18/22_series/22990/15e4a144a88176b71ea3eff2722253b0_img.jpg b/marked/Rel-18/22_series/22990/15e4a144a88176b71ea3eff2722253b0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45d10d8dc8dcb9792012d50d4e09e0246772ece1
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/15e4a144a88176b71ea3eff2722253b0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6504c82fcf0a3566a7dcff6a628234fd3cda018aeee7fe86038279fe1e45fa0d
+size 48808
diff --git a/marked/Rel-18/22_series/22990/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/22_series/22990/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c8f7dcd299e3a40ef1ec947f1a9a08ca521e185
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4c195dc3cf274a49eeb4525ca96851df60e8056dc3026871496d784467a5fe9
+size 34135
diff --git a/marked/Rel-18/22_series/22990/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/Rel-18/22_series/22990/2de714cedbbdd36f901f71bafa78f75a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6deeb2d7c31cfd5a926e6db7d73c00931d446ce3
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/2de714cedbbdd36f901f71bafa78f75a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a08729ae36cf5b63fc0137652ab01d396103164a1de84c2367f0eb6aac5f2e79
+size 41589
diff --git a/marked/Rel-18/22_series/22990/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/22_series/22990/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c08222255fc313aa621eb86964b5a8b302367f0
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d29bb9cb25f3e232fa3e588a1471970fc3086d500f80c4717863da395e8f4ab1
+size 9523
diff --git a/marked/Rel-18/22_series/22990/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/22_series/22990/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92bca1355c31caf8acf1e97e3ed0a15cf739de30
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:979f622293a630726656b98d7676846e954a1648d3e44945845a289d7c8d8780
+size 5678
diff --git a/marked/Rel-18/22_series/22990/7b4218684dabfd7cc15685f82dbe5faf_img.jpg b/marked/Rel-18/22_series/22990/7b4218684dabfd7cc15685f82dbe5faf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..741da7c6dfe9d54aae9848e03226deff72cec082
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/7b4218684dabfd7cc15685f82dbe5faf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f6e1c9eb4fd46a3562c0d132621bf5feae7c4e4250f384e391b9ba224f7ad7c
+size 29750
diff --git a/marked/Rel-18/22_series/22990/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/Rel-18/22_series/22990/805c475f0859e607af0530ba43194bf1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2080006480be532eb4ac154aee3bc25ba254be4
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/805c475f0859e607af0530ba43194bf1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d767ac774a85f956383b5dce4302ebcfe3acbd0575eeee55d10d78440c937651
+size 73657
diff --git a/marked/Rel-18/22_series/22990/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-18/22_series/22990/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f79faeb36724276f779af37ff54f75ec27d9050e
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:713fa069d94dee790d34c7386eafd3deff086215a75a6a488bfe10e960ef5b66
+size 130285
diff --git a/marked/Rel-18/22_series/22990/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-18/22_series/22990/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29428c8e687ff1e1d6758ebcdab38c2d7e7ad5c3
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46f4c877cdf5857b5c6779fc4732838b3ef08406375552890dba8977fc51b589
+size 42636
diff --git a/marked/Rel-18/22_series/22990/836008eb3303ade9e269f93c04dc0a2e_img.jpg b/marked/Rel-18/22_series/22990/836008eb3303ade9e269f93c04dc0a2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc7b092fc09fd8394699a0d1503a50ef2f83b828
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/836008eb3303ade9e269f93c04dc0a2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4fa2c4da91547d6df9e4d66bd01c88d4ad9e610bfadfe2aa6d02c1f4fe1fc16
+size 35460
diff --git a/marked/Rel-18/22_series/22990/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/22_series/22990/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ce36c81b77811f56042001ef1bb0ead38df14d38
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f0a5d4e9ac14e8c5d029d60b0bedd52c8d210ed27899ba2d4cfab6c6aadee66
+size 59772
diff --git a/marked/Rel-18/22_series/22990/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-18/22_series/22990/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2714a425793f07a625d93481c69ee163324e62c9
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9317daf18f61fea9f39f3f4f2f1a7fa3e5e4d3d2428318caaef5c6a37c714767
+size 53997
diff --git a/marked/Rel-18/22_series/22990/e159e9f78612406820a4d40e26e01413_img.jpg b/marked/Rel-18/22_series/22990/e159e9f78612406820a4d40e26e01413_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..448bda4608fb00da80bb4630539ec4ede223c612
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/e159e9f78612406820a4d40e26e01413_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c258e8432b094485cee4920c6380ea2f8e792eafacd9795ad21e14068c24f34
+size 27144
diff --git a/marked/Rel-18/22_series/22990/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/marked/Rel-18/22_series/22990/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..053831a37883a478e273f8064be91ec5240ddb65
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb5ce2918d0be8e636dce154da3e554e67d046528d69f431fd73a2761a5b592d
+size 39649
diff --git a/marked/Rel-18/22_series/22990/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/Rel-18/22_series/22990/f64e1e0997695248c0cd4122c5b1a170_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0d124ba8e2a614601e9deaf07ee73798bec9718
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/f64e1e0997695248c0cd4122c5b1a170_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f61994690578d0d826289dd06148ea9c0d57803a222f290ec24316abe0d8e2e3
+size 33013
diff --git a/marked/Rel-18/22_series/22990/raw.md b/marked/Rel-18/22_series/22990/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c3959b51b40e1553b4eebc8385229e5188fe1b5
--- /dev/null
+++ b/marked/Rel-18/22_series/22990/raw.md
@@ -0,0 +1,1241 @@
+
+
+# 3GPP TR 22.990 V18.0.0 (2021-12) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Off-Network for Rail; Stage 1 (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+---
+
+3GPP logo
+
+## --- **Keywords**
+
+<Rail, Off-network, MCX, ProSe>
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|----------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Symbols..... | 6 |
+| 3.3 Abbreviations ..... | 7 |
+| 4 Overview..... | 7 |
+| 5 Communication Applications related use cases..... | 7 |
+| 5.1 Introduction ..... | 7 |
+| 5.2 Trackside Maintenance Warning System communication..... | 7 |
+| 5.2.1 Description ..... | 7 |
+| 5.2.2 Pre-conditions..... | 9 |
+| 5.2.3 Service Flows ..... | 9 |
+| 5.2.4 Post-conditions ..... | 10 |
+| 5.2.5 Existing features partly or fully covering the use case functionality ..... | 10 |
+| 5.2.6 Potential New Requirements needed to support the use case and gap analysis ..... | 10 |
+| 5.2.6.1 Requirements related to the Service layer ..... | 10 |
+| 5.2.6.2 Requirements related to the Transport layer..... | 11 |
+| 5.3 Remote Control of Engines communications..... | 11 |
+| 5.3.1 Description ..... | 11 |
+| 5.3.2 Pre-conditions..... | 13 |
+| 5.3.3 Service Flows ..... | 13 |
+| 5.3.4 Post-conditions ..... | 14 |
+| 5.3.5 Existing features partly or fully covering the use case functionality ..... | 14 |
+| 5.3.6 Potential New Requirements needed to support the use case..... | 14 |
+| 5.3.6.1 Requirements related to the Service layer ..... | 14 |
+| 5.3.6.2 Requirements related to the Transport layer..... | 15 |
+| 5.4 Train integrity monitoring data communication ..... | 15 |
+| 5.4.1 Description ..... | 15 |
+| 5.4.2 Pre-conditions..... | 16 |
+| 5.4.3 Service Flows ..... | 16 |
+| 5.4.4 Post-conditions ..... | 17 |
+| 5.4.5 Existing features partly or fully covering the use case functionality ..... | 17 |
+| 5.4.6 Potential New Requirements needed to support the use case..... | 17 |
+| 5.4.6.1 Requirements related to the Service layer ..... | 17 |
+| 5.4.6.2 Requirements related to the Transport layer..... | 18 |
+| 5.5 Shunting communication..... | 18 |
+| 5.5.1 Description ..... | 18 |
+| 5.5.2 Pre-conditions..... | 18 |
+| 5.5.3 Service Flows ..... | 18 |
+| 5.5.4 Post-conditions ..... | 20 |
+| 5.5.5 Existing features partly or fully covering the use case functionality ..... | 20 |
+| 5.5.6 Potential New Requirements needed to support the use case..... | 20 |
+| 5.5.6.1 Requirements related to the Service layer ..... | 20 |
+| 5.5.6.2 Requirements related to the Transport layer..... | 21 |
+| 5.6 Train ready for departure communication..... | 22 |
+| 5.6.1 Description ..... | 22 |
+| 5.6.2 Pre-conditions..... | 23 |
+| 5.6.3 Service Flows ..... | 23 |
+| 5.6.4 Post-conditions ..... | 24 |
+| 5.6.5 Existing features partly or fully covering the use case functionality ..... | 24 |
+
+| | | |
+|-----------------|-----------------------------------------------------------------------------|-----------|
+| 5.6.6 | Potential New Requirements needed to support the use case..... | 24 |
+| 5.6.6.1 | Requirements related to the Service layer ..... | 24 |
+| 5.6.6.2 | Requirements related to the Transport layer..... | 24 |
+| 5.7 | Autonomous Train Control and Operation..... | 25 |
+| 5.7.1 | Description ..... | 25 |
+| 5.7.2 | Pre-conditions..... | 26 |
+| 5.7.3 | Service Flows ..... | 26 |
+| 5.7.4 | Post-conditions ..... | 26 |
+| 5.7.5 | Existing features partly or fully covering the use case functionality ..... | 26 |
+| 5.7.6 | Potential New Requirements needed to support the use case..... | 26 |
+| 5.7.6.1 | Requirements related to the Service layer ..... | 26 |
+| 5.7.6.2 | Requirements related to the Transport layer..... | 26 |
+| 5.8 | Virtual Coupling..... | 27 |
+| 5.8.1 | Description ..... | 27 |
+| 5.8.2 | Pre-conditions..... | 28 |
+| 5.8.3 | Service Flows ..... | 29 |
+| 5.8.4 | Post-conditions ..... | 29 |
+| 5.8.5 | Existing features partly or fully covering the use case functionality ..... | 29 |
+| 5.8.6 | Potential New Requirements needed to support the use case..... | 29 |
+| 5.8.6.1 | Requirements related to the Service layer ..... | 29 |
+| 5.8.6.2 | Requirements related to the Transport layer..... | 29 |
+| 5.9 | Monitoring and control of critical infrastructure communication..... | 30 |
+| 5.9.1 | Description ..... | 30 |
+| 5.9.2 | Pre-conditions..... | 31 |
+| 5.9.3 | Service Flows ..... | 31 |
+| 5.9.4 | Post-conditions ..... | 31 |
+| 5.9.5 | Existing features partly or fully covering the use case functionality ..... | 31 |
+| 5.9.6 | Potential New Requirements needed to support the use case..... | 32 |
+| 5.9.6.1 | Requirements related to the Service layer ..... | 32 |
+| 5.9.6.2 | Requirements related to the Transport layer..... | 32 |
+| 6 | Void..... | 33 |
+| 6.1 | Void..... | 33 |
+| 7 | Void..... | 33 |
+| 7.1 | Void..... | 33 |
+| 8 | Identified issues..... | 33 |
+| 8.1 | Introduction ..... | 33 |
+| 8.2 | Identified issue 1: Communication range..... | 33 |
+| 8.2.1 | Description ..... | 33 |
+| 8.2.2 | Limitations, missing requirements and gaps ..... | 33 |
+| 8.3 | Identified issue 2: MCX Support ..... | 33 |
+| 8.x.1 | Description ..... | 33 |
+| 8.x.2 | Limitations, missing requirements and gaps ..... | 34 |
+| 8.x | Identified issue y: <Identified issue title> ..... | 34 |
+| 8.x.1 | Description ..... | 34 |
+| 8.x.2 | Limitations, missing requirements and gaps ..... | 34 |
+| 9 | Consolidated potential requirements..... | 35 |
+| 10 | Conclusion and recommendations ..... | 35 |
+| <b>Annex A:</b> | <b>Change history .....</b> | <b>36</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd 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
+
+This document studies if further enhancements to the 5G system are feasible or not for the support of Off-Network for Rail.
+
+This document collects all Off-Network use cases from SA1 Study on Future Railway Mobile Communication System (FRMCS) in order to refine them and new use cases to support Off-Network for Rail in clause 5 for Communication Applications.
+
+The potential new service requirements are also consolidated in clause 5.
+
+The results of gap analysis identify limitations, missing requirements and existing functionalities supported by 3GPP in clause 5.
+
+Following the gap analysis, the assessment of technical feasibility, complexity and overhead of normative 3GPP adjustments to support limitations, missing requirements and functionalities as required by Off-Network for Rail is considered in clause 8.
+
+Potential requirements are then consolidated in clause 9.
+
+The conclusions and recommendations are proposed in clause 10 to conclude if further enhancements to the 5G system are needed and feasible for the support of Off-Network for Rail.
+
+# --- 1 Scope
+
+The present document analyses Rail Off-Network use cases in order to derive potential requirements and investigate if normative adjustments are feasible or not.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 22.289: "Mobile Communication System for Railways".
+- [3] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT)".
+- [4] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
+- [5] 3GPP TS 22.281: "Mission Critical Video services".
+- [6] 3GPP TS 22.282: "Mission Critical Data services".
+- [7] 3GPP TS 22.261: "Service requirements for the 5G system".
+- [8] 3GPP TS 22.185: "Service requirements for V2X services".
+- [9] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios".
+- [10] UIC MG-7900: "Future Railway Mobile Communication System Use Cases".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| | |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+<ACRONYM> <Explanation>
+
+# --- 4 Overview
+
+The present document is a 900 series Technical Report (TR) written by 3GPP TSG SA WG1 (SA1). Such a TR is not normative, i.e. cannot be used for implementation directly. It is primarily written by SA1 to summarise the high-level Off-Network communication needs of the railway community and to identify the corresponding requirements.
+
+## Rail Context
+
+Future rail communication is an important part of the digitalization of rail operations. In addition to network-oriented communication, this also includes that without involving the network. GSM-R already used this and was called Direct Mode to describe the ability of a User Equipment to communicate directly with each other, independent of the network.
+
+Off-Network is a new terminology for the Rail sector, already introduced within 3GPP MCX specifications. UIC will promote the use of Off-Network to replace Direct Mode. But unfortunately, the terminology has slight differences in the meaning. For example, the Rail sector considers use of Off-Network communications where no network services are available either due to network failure (e.g. coverage, capacity, etc.) or due to lack of coverage (remote area's). In 3GPP MCX specifications, Off-Network communications can be setup even when network services are available.
+
+In addition to voice communication, Off-Network communication will also increasingly be used for the exchange of train safety data in the future.
+
+Examples of use cases which require Direct Mode:
+
+- Automatic Train Protection (ATP) data communication
+- Automatic Train Operation (ATO) data communication
+- Critical real-time video
+- Virtual Coupling data communication
+
+Virtual Coupling data communication is the only use case where Off-Network is the intended mode of operation (also called “default mode”) even if the network is available.
+
+All other use cases shall consider Network-Oriented mode as the default mode when the network is available (for the first and following attachments) and shifting to Off-Network when the network is not available.
+
+# --- 5 Communication Applications related use cases
+
+## 5.1 Introduction
+
+This clause describes use cases of Communication Applications (e.g. Virtual Coupling data communication).
+
+## 5.2 Trackside Maintenance Warning System communication
+
+### 5.2.1 Description
+
+Generally, trackside maintenance occurs during daily train operation. For safety reasons, trackside maintenance staff need to be informed about approaching trains entering the worksite. Thus, the intention of a trackside warning system is to inform trackside staff about the approaching train to keep rail capacity available while working on the tracks.
+
+The trackside maintenance warning system consists of a single or multiple train detector entity(ies) (sensors, lookout man or interlocking station information + communication device), and a single or multiple warning entity(ies). The train detector entity is responsible to detect the approaching train and to trigger the alarm to the warning entities (as an option, the alarm should be triggered to a central/control entity also that relays the alarm to all warning entities). The warning entity indicates trackside workers about the approaching train on existing or adjacent tracks in form of visual signal e.g. flashing light and audio signal e.g. tone/horn. In large worksites or areas of high-speed trains, multiple warning entities can be spread out along the worksite to repeat the train approaching indication. In addition, the trackside maintenance staff will receive the train approaching indication on its FRMCS Equipment (i.e. wearable device).
+
+When the train has cleared the warning zone, the indication is withdrawn automatically by the warning system, by the interlocking or manually by an authorised operator located inside or at the edge of the warning zone.
+
+
+
+The diagram illustrates the trackside maintenance warning system. A train (1) is shown approaching a worksite (4) from the left at a speed of 500 km/h. The worksite is marked by a yellow and black striped barrier. The warning zone is indicated by a light blue shaded area. The distance from the train to the start of the warning zone is labeled 'Min 3 500 m'. The distance from the start of the warning zone to the start of the worksite is labeled 'Max 5 000 m'. The distance from the end of the worksite to the end of the warning zone is labeled 'Min 3 500 m'. Stationary trackside warning devices (2) and personal UE(s) (3) are shown at the entrance and exit of the warning zone. A worker (4) is shown inside the worksite, receiving a warning signal from a stationary trackside warning device (2) and a personal UE (3).
+
+Diagram of the Trackside Maintenance Warning System showing a train approaching a worksite with warning zones and communication devices.
+
+1. Train approaches warning zone
+2. Train is detected by stationary trackside warning device (automatically) or look-out man (manually)
+3. Stationary unit or look-out man sends warning to [1..30] worker(s) (via stationary trackside warning device(s) or via personal UE(s))
+4. Warning receives at worksite not less than 25 seconds (time for worker(s) to protect themselves)
+
+**Figure 5.2.1-1: Description of the Trackside Maintenance Warning System**
+
+Train detector entities and warning entities constitute the warning system that requires secured/safe continuous radio transmission of data between the sensors and the warning entities (e.g. keep alive messages for robustness and location information of entities/workers to differentiate between the tracks with a lateral distance accuracy of less than 1 meter). In addition, it encompasses the secured/safe radio transmission of the train approaching indication (i.e. start/stop transmitting the indication to the track workers) among the warning system and the FRMCS Equipment of the trackside staff. Train detection is outside scope of the warning system.
+
+Due to the fact that such a warning system deployment is temporary and on-network communication services are not always available at the track, the FRMCS System provides necessary off-network communication services for the trackside warning system. Trackside maintenance warning system in off-network mode is well suited for small, short-term construction sites but should also be relevant for large and long-term construction sites.
+
+The maximum train speed in the warning zone is 500 kmph.
+
+Note: no speed limit applies in worksites in some Countries.
+
+Communications between train detector entities located at both edges of the warning zone are not supported by the Trackside maintenance warning system.
+
+As a deployment option, communication between the approaching train and the trackside warning system should be supported to e.g. avoid train detectors.
+
+Fixed and moving worksites e.g. carrying out inspection work are supported by the Trackside maintenance warning system.
+
+One-way (i.e. one train detector entity) and two-way (i.e. two train detector entities) traffic protection are supported by the Trackside maintenance warning system.
+
+The minimum configuration of a warning system is:
+
+- One train detector entity located closed or inside the worksite (i.e. detection by visual detection)
+- One warning entity located inside the worksite
+
+The maximum configuration of a warning system is:
+
+- Two train detector entities located at both edges of the warning zone
+- The maximum number of warning entities is 30, located inside the worksite
+- The maximum number of workers (e.g. wearing warning devices through FRMCS Equipment) located inside the worksite is 50.
+
+Different groups of workers can work at the same time along the worksite.
+
+Workers or work group can join/leave the worksite based on their locations.
+
+The warning system shall be flexible enough to easily setup.
+
+Energy efficiency of the warning system for battery-powered entities is not supported.
+
+Configuration and control of the warning system shall be available locally.
+
+Configuration and control of the warning system should be available through on-network communication.
+
+Positioning of the train detectors with accurate distance from the worksite is in the scope of the warning system with distance accuracy of +/- 1 meter.
+
+The trackside maintenance warning system communication shall be reliable in tunnels, in bad weather conditions and in unfavourable geographical conditions.
+
+Multiple and flexible use of spectrum bands shall be supported.
+
+### 5.2.2 Pre-conditions
+
+The FRMCS Users as part of the warning system are authorised to initiate, transmit/receive data and terminate the trackside maintenance warning system communication.
+
+### 5.2.3 Service Flows
+
+The entitled FRMCS User initiate, transmit/receive and terminate the trackside maintenance warning system communication.
+
+A secure data communication application is used for the trackside maintenance warning system communication. The communication requests the QoS class which matches the application category of **XXX** within the FRMCS System.
+
+**Editor's note:** applications categories applicable to Off-Network communications will be an outcome of the present study.
+
+The arbitration is managed by the Arbitration application.
+
+**Editor's note:** the Arbitration application use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The metadata are recorded by the Data recording application.
+
+**Editor's note:** the Data recording application use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The communication is secured by the Assured data communication.
+
+**Editor's note:** the Assured data communication use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The identities, presence and functional addressing is managed by the Role management & presence.
+
+**Editor's note:** the Role management & presence use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The authorisation of communication is managed by the Authorisation of communication.
+
+**Editor's note:** the Authorisation of communication use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The authorisation of application is managed by the Authorisation of application.
+
+**Editor's note:** the Authorisation of application use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The location of the FRMCS Equipment is managed by the Location services.
+
+**Editor's note:** the Location services use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+### 5.2.4 Post-conditions
+
+The entitled FRMCS User(s) as part of the warning system is able to securely exchange data in the appropriate area to intended FRMCS User(s).
+
+### 5.2.5 Existing features partly or fully covering the use case functionality
+
+TS 22.280 [4], 22.179 [32], 22.281 [5] and 22.282 [6] have a set of specific requirements on Off-Network MCX Services (including MCCoRe and MCData Services for Off-Network).
+
+TS 22.289 [2] has a set of performance requirements for Off-Network communications for Rail to be refined based on outcomes of the present study.
+
+TS 22.261 [7] has no requirement on 5G Proximity Services.
+
+TS 22.185 [8] and 22.186 [9] have a set of specific requirements on 5G Proximity Services to support V2X communications.
+
+### 5.2.6 Potential New Requirements needed to support the use case and gap analysis
+
+#### 5.2.6.1 Requirements related to the Service layer
+
+**Editor's note :** the following potential new MCX requirements are relevant for SA6.
+
+[PR 5.2.6.1-1] The FRMCS System shall be able to initiate data communication for Trackside Maintenance Warning System to FRMCS Users upon a request from a functional identity entitled to initiate such communication.
+
+[PR 5.2.6.1-2] The FRMCS System shall be able to select FRMCS user(s) to deliver the Trackside Maintenance Warning System data based on their functional identity and location either periodically or as a onetime request.
+
+[PR 5.2.6.1-3] The FRMCS System shall allow FRMCS Users to join an ongoing data communication for Trackside Maintenance Warning System based on their functional identity and location.
+
+[PR 5.2.6.1-4] The FRMCS System shall allow FRMCS Users to leave an ongoing data communication for Trackside Maintenance Warning System based on their functional identity and location.
+
+[PR 5.2.6.1-5] The FRMCS System shall be able to terminate data communication for Trackside Maintenance Warning System upon a request received from a functional identity entitled to terminate the communication.
+
+[PR 5.2.6.1-6] The FRMCS System shall allow configuration (e.g. functional identities of maintenance staff and warning entities) and control of the Trackside Maintenance Warning System when the FRMCS Equipment are served by a 3GPP RAT.
+
+[PR 5.2.6.1-7] The FRMCS System shall allow configuration (e.g. functional identities of maintenance staff and warning entities) and control of the Trackside Maintenance Warning System when the FRMCS Equipment are not served by a 3GPP RAT.
+
+#### 5.2.6.2 Requirements related to the Transport layer
+
+**Editor's note : the following potential new requirements are relevant for SA2 and RAN.**
+
+[PR 5.2.6.2-1] The FRMCS System shall support the following traffic characteristics of data transfer for data communication for Trackside Maintenance Warning System:
+
+Note: This table is intended to be aligned with TS 22.289 table 5.2.2-2 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experience data rate (UL and DL) | Payload size (Note 2) | Area traffic density (UL and DL) | Overall UE density | Communication range (note 6) | Service area dimension (note 3) |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------|----------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| Trackside maintenance warning system Communication | ≤500 ms | 99,9999% (note 7) | Stationary (warning system entities) and pedestrians (workers).<br>Option: ≤500kmph for train detection via onboard system | 10 kbps up to 500 kbps | Small to medium | Up to 10 Mbps /km | ≤80/worksite | ≥8.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions (note 4) | ≥12 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions (note 5) |
+| NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1. | | | | | | | | | |
+| NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets. | | | | | | | | | |
+| NOTE 3: Estimates of maximum dimensions. | | | | | | | | | |
+| NOTE 4: Distance is equal to the distance for train of maximum speed of 500 kmph to enter the worksite + the maximum distance of a worksite | | | | | | | | | |
+| NOTE 5: Minimum distance of the warning zone | | | | | | | | | |
+| NOTE 6: Supported via a single or a combination of 3GPP capabilities of 5GS that best serve these use case in areas with no FRMCS RAN nodes/no FRMCS network coverage. | | | | | | | | | |
+| NOTE 7: Reliability figures could be achieved using multiple 3GPP 5GS-compatible spectrum bands simultaneously. | | | | | | | | | |
+
+**Table 5.2.6.2-1: Traffic characteristics for Trackside Maintenance Warning System**
+
+## 5.3 Remote Control of Engines communications
+
+### 5.3.1 Description
+
+It shall be possible for a remote driver to operate/control an engine (e.g. control movement and speed) of a vehicle typically for shunting operation in depots, shunting yards and/or for banking via a ground-based system or an on-board system located at opposite ends of the engine.
+
+
+
+Diagram illustrating the remote control of engines. A train with a locomotive and four cars is shown on the left, moving towards the right. Above the locomotive, a speed limit of 'Max 40 km/h' is indicated. A remote driver, represented by an icon with a smartphone and a hard hat, is shown below the train. Two arrows labeled 'Max 1 000 m' point from the remote driver to the locomotive and to a second locomotive on the right, indicating the maximum range of control. The second locomotive is also shown moving towards the right.
+
+**Figure 5.3.1-1: Description of the Remote Control of Engines**
+
+
+
+A photograph showing a person wearing a blue hard hat and a high-visibility vest standing on a railway track, looking towards a red locomotive in the distance.
+
+
+
+A photograph of a yellow locomotive with a person in a red safety suit standing on its front platform. The locomotive is pulling a series of white cylindrical tank cars.
+
+**Figure 5.3.1-2: Pictures of the Remote Control of Engines in operation**
+
+Onboard system should have a distinct and unambiguous audible or visual warning device that indicates to nearby personnel that the vehicle is under active remote control and subject to movement.
+
+Remote driver/ground-based entity and controlled engine(s)/onboard entity constitute the remote control of engines system that requires secured/safe continuous radio transmission of data between the remote driver and the controlled engine(s) (e.g. keep alive messages for robustness, dynamic speed and brake control, report direction of travel and speed of the vehicle).
+
+A remote driver shall be able to control up to 10 engines but only one engine at a time. To supply sufficient power, a locomotive may consist of one or more engines operated from a single remote driver. In that case, commands from the remote control shall be synchronized. A single onboard system is used to control the engines. Only one communication from the remote driver to the onboard system is required.
+
+A remote driver having the capability to control more than one engine should have a mean to prevent simultaneous control over more than one locomotive.
+
+If on-network mode is available, the remote driver shall be able to exchange data with the traffic control system to automatically operate the track switches to free the tracks before remotely operating the train.
+
+If on-network mode is available, trains have to be geographically tracked by the traffic control system to prevent from traveling past predetermined boundaries (i.e. remote control zones to e.g. avoid other train movements).
+
+If on-network mode is available, the system shall alert the traffic control system when a safety case happens to the remote driver (e.g. remote driver down) including the accurate location of the remote driver.
+
+As an option, real-time video monitoring of tracks from onboard system in the cab or from trackside to the remote driver should be required simultaneously to the transmission of data for remote control of engines.
+
+The remote control of engines is designed to be fail-safe so that if communication is lost the vehicle is brought to a stop automatically.
+
+Due to the fact that very low latency is required, and on-network communication services are not always available at the depot, the FRMCS System provides necessary off-network communication services for the remote control of engines even if on-network communication services are available.
+
+The maximum speed of the train remotely controlled shall be restricted not to exceed 40 kmph.
+
+The remote control of engines shall be flexible enough to easily setup.
+
+Configuration and control of the remote control of engines shall be available locally.
+
+It shall be possible for a remote driver to awaken an onboard entity.
+
+The remote control of engines communication shall be reliable in depots, in tunnels, with clear line of sight.
+
+Multiple and flexible use of spectrum bands shall be supported.
+
+As an option, the remote control application should be used to remotely control by maintenance staff other equipment such as overhead cranes in depots, see below:
+
+
+
+Figure 5.3.1-3: Alternative of Remote Control Application. The image consists of two side-by-side photographs. The left photograph shows a white and red tram or light rail vehicle on a track inside a large industrial building. A yellow overhead crane is visible above the vehicle. The right photograph shows a white and yellow train or tram on a track, also inside a large industrial building. A yellow overhead crane is visible above the vehicle, and a person is standing near the front of the vehicle.
+
+**Figure 5.3.1-3: Alternative of Remote Control Application**
+
+The remote control of overhead cranes has the same requirements on communication characteristics as the remote control of engines.
+
+### 5.3.2 Pre-conditions
+
+The FRMCS User is authorised to initiate, transmit/receive data/video and terminate the remote control of engines communication.
+
+### 5.3.3 Service Flows
+
+The entitled FRMCS User initiate, transmit/receive and terminate the remote control of engines communication.
+
+A secure data communication application is used for the remote control of engines communication. The communication requests the QoS class which matches the application category of **XXX** within the FRMCS System.
+
+**Editor's note:** applications categories applicable to Off-Network communications will be an outcome of the present study.
+
+The arbitration is managed by the Arbitration application.
+
+**Editor's note:** the Arbitration application use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The metadata are recorded by the Data recording application.
+
+**Editor's note:** the Data recording application use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The communication is secured by the Assured data communication.
+
+**Editor's note:** the Assured data communication use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The identities, presence and functional addressing is managed by the Role management & presence.
+
+**Editor's note:** the Role management & presence use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The authorisation of communication is managed by the Authorisation of communication.
+
+**Editor's note:** the Authorisation of communication use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The authorisation of application is managed by the Authorisation of application.
+
+**Editor's note:** the Authorisation of application use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+The location of the FRMCS Equipment is managed by the Location services.
+
+**Editor's note:** the Location services use case in Off-Network mode is FFS in the context of FS\_OFFNETRAIL.
+
+### 5.3.4 Post-conditions
+
+The entitled FRMCS User is able to securely exchange data/video in the appropriate area to intended FRMCS User(s).
+
+### 5.3.5 Existing features partly or fully covering the use case functionality
+
+TS 22.280 [4], 22.179 [3], 22.281 [5] and 22.282 [6] have a set of specific requirements on Off-Network MCX Services (including MCCoRe and MCData Services for Off-Network).
+
+TS 22.289 [2] has a set of performance requirements for Off-Network communications for Rail to be refined based on outcomes of the present study.
+
+TS 22.261 [7] has no requirement on 5G Proximity Services.
+
+TS 22.185 [8] and 22.186 [9] have a set of specific requirements on 5G Proximity Services to support V2X communications.
+
+### 5.3.6 Potential New Requirements needed to support the use case
+
+#### 5.3.6.1 Requirements related to the Service layer
+
+**Editor's note :** the following potential new MCX requirements are relevant for SA6.
+
+[PR 5.3.6.1-1] The FRMCS System shall be able to initiate data communication for Remote Control of Engines to FRMCS User(s) upon a request from a functional identity entitled to initiate such communication.
+
+[PR 5.3.6.1-2] The FRMCS System shall be able to select one or multiple FRMCS user(s) to deliver the Remote Control of Engines data based on their functional identity and location either periodically or as a onetime request.
+
+[PR 5.3.6.1-3] The FRMCS System shall be able to limit the number of FRMCS User(s) to be selected to deliver the Remote Control of Engines data at any one time.
+
+[PR 5.3.6.1-4] An entitled FRMCS User shall be able to awake an FRMCS Equipment.
+
+[PR 5.3.6.1-5] The FRMCS System shall be able to terminate data communication for Remote Control of Engines upon a request received from a functional identity entitled to terminate the communication.
+
+[PR 5.3.6.1-6] The FRMCS System shall allow local configuration (e.g. functional identities of engines and remote drivers) and control of the Remote Control of Engines even when the FRMCS Equipment is served by a 3GPP RAT.
+
+#### 5.3.6.2 Requirements related to the Transport layer
+
+**Editor's note :** the following potential new requirements are relevant for SA2 and RAN.
+
+[PR 5.3.6.2-1] If the FRMCS Equipment is served by a 3GPP RAT, using NR for direct communication for Remote Control of Engines shall not interfere with on-network services.
+
+[PR 5.3.6.2-2] The FRMCS System shall support the following traffic characteristics for communication for Remote Control of Engines:
+
+Note: This table is intended to be aligned with TS 22.289 table 5.2.2-2 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experience data rate (UL and DL) | Payload size (Note 2) | Area traffic density (UL and DL) | Overall UE density | Communication range (note 4) | Service area dimension (note 3) |
+|-----------------------------------------------|--------------------|----------------------|------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------|----------------------------------|--------------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| Remote control of engines data communication | ≤10 ms | 99,9999% (note 4) | Stationary (trackside remote driver) and ≤40kmph (onboard remote control system and onboard remote driver) | 100 kbps up to 1 Mbps | Small to Medium | Up to 100 Mbps/s/km | 2 (remote driver and onboard system) | ≤1000m along rail tracks including depots and tunnels with clear line of sight | ≤2000m along rail tracks including depots and tunnels with clear line of sight |
+| Remote control of engines video communication | ≤100 ms | 99,9% (note 4) | Stationary (trackside remote driver) and ≤40kmph (onboard remote control system and onboard remote driver) | 10 Mbps | Medium | Up to 1 Gbps/km | 2 (remote driver and onboard system) | ≤1000m along rail tracks including depots and tunnels with clear line of sight | ≤2000m along rail tracks including depots and tunnels with clear line of sight |
+
+NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.
+NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.
+NOTE 3: Estimates of maximum dimensions.
+NOTE 4: Supported via a single or a combination of 3GPP capabilities of 5GS that best serve these use case in areas with no FRMCS RAN nodes/no FRMCS network coverage.
+NOTE 5: Reliability figures could be achieved using multiple 3GPP 5GS-compatible spectrum bands simultaneously
+
+**Table 5.3.6.2-1: Traffic characteristics for Remote Control of Engines**
+
+## 5.4 Train integrity monitoring data communication
+
+### 5.4.1 Description
+
+The Train Integrity is an on-board function responsible for verifying the completeness of a train composition, while the train is in operation, to guarantee safety on tracks. Train integrity consists concretely in monitoring the status of the train's tail to check that last wagon is regularly advancing in a coherent way in relation to the movement of the remaining train. The event of accidental train separation constitutes a serious danger for the next train, being a possible unexpected obstacle on the line, and therefore it needs to be promptly reported to the rail signalling system.
+
+The main difference between train integrity monitoring in on-network mode and off-network mode consists in train integrity criteria that (1) is based on communication liveliness in on-network mode, whereas (2) requires verifying train tail coherent movement respect to front cabin, based on train tail odometry data (i.e. position, speed or acceleration of train tail and front cabin) in off-network mode. In fact, off-network communication between train tail and front cabin could be present also after train splitting with limited distance of separated waggons.
+
+### 5.4.2 Pre-conditions
+
+The On-board Train Integrity (OTI) entities (i.e. the FRMCS Users) are authorised to initiate Train Integrity Monitoring Data Communication.
+
+### 5.4.3 Service Flows
+
+James is the lead driver of a cargo train of 1 000 metres long with 50 wagons that are not fully equipped with power supply.
+
+The front cabin, the train tail wagon and, optionally some or all of the intermediate wagons to offer more flexibility in train composition, are equipped with On-board Train Integrity (OTI) entities connected to UEs in off-network mode at the lower part of the wagons (i.e. no direct line-of-sight between OTI entities). UEs may not be dedicated to On-board Train Integrity.
+
+James powers on the front cabin before starting to operate the train. The OTI entities establish communications with each other and begin exchanging status (i.e. position, speed or acceleration information, and if supported wagon diagnostic information) via the connected UEs in off-network mode. The train integrity status is “Confirmed” (all wagons connected and operational). The Train Integrity system shall avoid pairing James’ OTI entities with other trains’ OTI entities in proximity.
+
+Train Integrity data exchanges are encrypted to prevent eavesdropping.
+
+Train Integrity data exchanges are recorded in case something bad happens (e.g. wrong pairing between OTI entities) and somebody wants to review the incident later.
+
+James starts running its train to its destination on non-electrical lines where there is no network coverage. The Train Integrity Monitoring procedure restarts every 30 seconds (configurable timer) until the train stops running.
+
+
+
+Diagram illustrating train integrity confirmation. A train is shown moving to the right, indicated by a blue arrow labeled 'Trains direction'. The train consists of several wagons. The front wagon (OTI1) is labeled 'James: Lead Driver #1' and has a green box representing the 'Onboard Signalling System'. The rear wagon (OTI3) is labeled 'OTI3'. A yellow curved arrow connects OTI1 and OTI3, labeled 'Distance D1 = Max. 1 000m'. A yellow box above the front wagon contains the text 'Train integrity confirmed'. A timeline at the bottom is labeled 'Time T1'. A legend at the bottom left shows a yellow square for 'Onboard Train Integrity entity' and a green square for 'Onboard Signalling System'.
+
+**Figure 5.4.3-1: Train integrity confirmed**
+
+For some reason, the train tail splits off of James’ train. The Train Integrity system detects the event and the train integrity status becomes “Lost”.
+
+In the meantime, James is communicating with its train operating centre to prepare its next mission. The Train Integrity system informs on-board signalling system about train integrity status. The on-board signalling system takes priority on James ongoing communication to inform him thus allowing him to intervene rapidly and appropriately (e.g. reducing the speed and breaking the train in a safe location).
+
+
+
+Diagram illustrating a train integrity loss scenario. A train is shown moving from left to right, indicated by a blue arrow labeled 'Trains direction'. The train consists of several cars, with three Onboard Train Integrity (OTI) entities labeled OTI1, OTI2, and OTI3. OTI1 is at the front (right side), OTI2 is in the middle, and OTI3 is at the rear (left side). A red 'X' is placed between OTI3 and the next car, indicating a separation. A red callout box labeled 'Train integrity lost' points to the front of the train, with the text 'James: Lead Driver #1'. A yellow arc connects OTI1 and OTI3, with a distance label 'Distance D2 = Min. 2 x D1 = 2 000m'. A timeline at the bottom left shows 'Time T1 + T2'. A legend at the bottom left indicates that yellow squares represent 'Onboard Train Integrity entity' and green squares represent 'Onboard Signalling System'.
+
+**Figure 5.4.3-2: Train integrity lost**
+
+### 5.4.4 Post-conditions
+
+Train integrity status can be continuously exchanged between On-board Train Integrity (OTI) entities to warn accidental train separation and avoid any rail safety issue.
+
+### 5.4.5 Existing features partly or fully covering the use case functionality
+
+TS 22.280 [4], 22.179 [3], 22.281 [5] and 22.282 [6] have a set of specific requirements on Off-Network MCX Services (including MCCoRe and MCData Services for Off-Network).
+
+TS 22.289 [2] has a set of performance requirements for Off-Network communications for Rail to be refined based on outcomes of the present study.
+
+TS 22.261 [7] has no requirement on 5G Proximity Services.
+
+TS 22.185 [8] and 22.186 [9] have a set of specific requirements on 5G Proximity Services to support V2X communications.
+
+### 5.4.6 Potential New Requirements needed to support the use case
+
+#### 5.4.6.1 Requirements related to the Service layer
+
+[PR 5.4.6.1-1] The FRMCS Service in Off-Network mode shall be able to initiate data communication for Train Integrity Monitoring to relevant FRMCS Users upon a request from a functional identity entitled to initiate such communication.
+
+[PR 5.4.6.1-2] The FRMCS Service in Off-Network mode shall provide the necessary communication means to support Train Integrity Monitoring.
+
+[PR 5.4.6.1-3] The FRMCS Service in Off-Network mode shall allow arbitration for Train Integrity Monitoring communication.
+
+[PR 5.4.6.1-4] The FRMCS Service in Off-Network mode shall allow FRMCS Users to join an ongoing data communication for Train Integrity Monitoring based on their functional identity and location.
+
+[PR 5.4.6.1-5] The FRMCS Service in Off-Network mode shall allow FRMCS Users to leave an ongoing data communication for Train Integrity Monitoring based on their functional identity and location.
+
+[PR 5.4.6.1-6] The FRMCS Service in Off-Network mode shall provide means to obtain and exchange odometry information of FRMCS Users (e.g. position, speed or acceleration).
+
+[PR 5.4.6.1-7] When an FRMCS Equipment in Off-Network mode is simultaneously used by multiple FRMCS Users, each of the FRMCS Users shall be individually addressable.
+
+[PR 5.4.6.1-8] The FRMCS Service in Off-Network mode shall be able to terminate data communication for Train Integrity Monitoring upon a request received from a functional identity entitled to terminate such communication.
+
+[PR 5.4.6.1-9] The FRMCS Service in Off-Network mode shall provide the means to record Train Integrity Monitoring data communication and communication related information (e.g. FRMCS Users involved) to an external system.
+
+[PR 5.4.6.1-10] The FRMCS Service Security Framework shall provide mechanisms in Off-Network mode to cover identity management, authentication, authorisation and data protection in respect to Train Integrity Monitoring.
+
+#### 5.4.6.2 Requirements related to the Transport layer
+
+[PR 5.4.6.2-1] The FRMCS Equipment power consumption in Off-Network mode shall be minimised.
+
+[PR 5.4.6.2-2] The FRMCS Service in Off-Network mode shall support the following traffic characteristics of data transfer for direct data communication for Train Integrity Monitoring:
+
+Note: This table is intended to be aligned with TS 22.289 table 5.2.2-2 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experienced data rate (UL and DL) | Payload size (Note 2) | Area traffic density (UL and DL) | Overall UE density | Communication range (Note 3) | Service area dimension (Note 4) |
+|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------|----------------------------------------|-----------------------|----------------------------------|--------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Train integrity monitoring data Communication | ≤1 s | 99,9% | ≤350k mph | 10 kbps up to 500 kbps | Small to Medium | Up to 25 Mbps /km | ≤50/train | ≤2 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5)<br>(Note 6) | ≤2 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5)<br>(Note 6) |
+| | NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.<br>NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.<br>NOTE 3: Supported via a single or a combination of 3GPP capabilities of 5GS that best serve these use case in areas with no FRMCS RAN nodes/no FRMCS network coverage.<br>NOTE 4: Estimates of maximum dimensions.<br>NOTE 5: Distance is equal to twice the maximum length of a train to cover train tail split<br>NOTE 6: Non-Line-of-Sight (NLOS) between UEs shall be supported. | | | | | | | | |
+
+**Table 5.4.6.2-1: Traffic characteristics for Train Integrity Monitoring**
+
+## 5.5 Shunting communication
+
+### 5.5.1 Description
+
+Changing the locomotive of a train, coupling/uncoupling wagons, changing the order in which wagons are arranged in a train are all kinds of shunting movements. Shunting movements can be differentiated from other regular movements: this main point of differentiation is that almost all shunting is done within a single station or a shunting yard.
+
+Shunting movements between shunting members can be ordered by radio, in on-network or in off-network modes. This section describes shunting communications in off-network mode where a ground user e.g. controller/dispatcher is not necessary.
+
+### 5.5.2 Pre-conditions
+
+The Shunting members (i.e. the FRMCS Users) of the shunting team #1 (i.e. Shunting Service Area #1 and Shunting Team ID #1) are authorised to initiate Shunting Communications.
+
+### 5.5.3 Service Flows
+
+A cargo train has to be prepared by coupling the main locomotive to the rest of the wagons. A Shunting Service Area is defined to avoid any other train movements in the same area. There is no network coverage in this Shunting service area.
+
+Bob has been assigned the role of the shunting leader of a shunting team in charge of this operation. Bob prepares its mission together with James, which has been assigned the role of the shunting driver. The shunting team members are all equipped with a Shunting device connected to a UE. They are operating their UEs in off-network mode and have selected their role and shunting service area to enable voice and data exchanges between the shunting members. The Shunting group voice and data communications are encrypted to prevent eavesdropping.
+
+Bob exchanges with the shunting members secured and reliable information required to perform safe shunting movements of trains, (e.g. issuing route requests, route confirmation, giving driving commands, confirmation for driving commands, etc.). Bob receives confirmation upon successful reception of the message for all shunting members.
+
+Service Flow#1 (shunting movements ordered by human): James, located in the front cabin (indoor) and without direct line-of-sight of the track, pushes a group of wagons (i.e. going backwards), continuously and securely ordered by Bob, located at train tail (outdoor or indoor) as a lookout man. To do so, Bob enables an assured safety link function that periodically send tones or keep alive messages to the shunting members. Bob may shout orders periodically into his Shunting device. Bob's orders take priority on the periodic assured safety link tones and every team member is able to hear him.
+
+If the voice/data can not be exchanged for more than 2 seconds (configurable time), every member of the shunting team is informed, thus allowing them to intervene rapidly and appropriately (e.g. James breaking the train).
+
+When Bob orders James to stop its train, he disables the assured safety link function and invites Dave, a member of another shunting team located on the trackside, to be part of their shunting team to couple James' train to the rest of the wagons. Shunting team members of both teams are now part of the same shunting team.
+
+Dave, James and Bob are simultaneously talking to each other to couple James' train safely.
+
+Dave notices that another worker is in the area and, to avoid collision with James' train shouts a warning into his UE. Dave's warning takes priority, and member of the shunting team is able to hear him to intervene rapidly and appropriately (e.g. James breaking the train).
+
+Shunting communications are recorded (e.g. shunting members composition) in case something bad happens and somebody wants to review the incident later.
+
+Service Flow#2 (shunting movements self-controlled using video by the driver): James, located in the front cabin (indoor) and without direct line-of-sight of the track, pushes a group of wagons (i.e. going backwards), continuously and securely monitoring the track using video communication with camera connected to a UE located at the train tail.
+
+If the video can not be exchanged for more than 2 seconds (configurable time), James is informed, thus allowing him to intervene rapidly and appropriately (e.g. James braking the train).
+
+Shunting video communications are recorded (including metadata e.g. timestamp, originator, receiver, roles) in case something bad happens and somebody wants to review the incident later.
+
+
+
+Figure 5.5.3-1: Examples of Shunting communications. The diagram illustrates a 'Rail Shunting Yard' with multiple tracks. Track 1 (top) is 'Shunting Service area#1', marked with a red 'DANGER' sign. It shows a Shunting Member (purple) and a Shunting Leader (blue) communicating, with a distance indicator '10m...5m...'. A train is moving from right to left, indicated by a blue arrow labeled 'Train direction'. Track 2 (middle) has a 'Metallic structure'. Track 3 (bottom) is 'Shunting Service area#2', marked with a yellow 'BIP...BIP...' sign. It shows a Shunting Driver (green) and a Shunting Leader (blue) communicating. A train is moving from left to right, indicated by a blue arrow labeled 'Train direction'. A 'Building' is shown on the right side of the yard. A legend at the bottom identifies the icons: Shunting Leader (blue), Shunting Driver (green), Shunting Member (purple), and Shunting device (yellow).
+
+**Figure 5.5.3-1: Examples of Shunting communications**
+
+### 5.5.4 Post-conditions
+
+Shunting movement orders can be continuously exchanged between the Shunting members of the shunting team to avoid any rail safety issue while shunting.
+
+Shunting videos can be continuously exchanged between the Driver and the shunting cameras to avoid any rail safety issue while shunting.
+
+### 5.5.5 Existing features partly or fully covering the use case functionality
+
+TS 22.280 [4], 22.179 [3], 22.281 [5] and 22.282 [6] have a set of specific requirements on Off-Network MCX Services (including MCCoRe and MCData Services for Off-Network).
+
+TS 22.289 [2] has a set of performance requirements for Off-Network communications for Rail to be refined based on outcomes of the present study.
+
+TS 22.261 [7] has no requirement on 5G Proximity Services.
+
+TS 22.185 [8] and 22.186 [9] have a set of specific requirements on 5G Proximity Services to support V2X communications.
+
+### 5.5.6 Potential New Requirements needed to support the use case
+
+#### 5.5.6.1 Requirements related to the Service layer
+
+[PR 5.5.6.1-1] The FRMCS Service in Off-Network mode shall be able to initiate voice, data and video communication for Shunting movements to relevant FRMCS Users upon a request from a functional identity entitled to initiate such communication.
+
+[PR 5.5.6.1-2] The FRMCS Service in Off-Network mode shall provide the necessary communication means to support Shunting.
+
+[PR 5.5.6.1-3] The FRMCS Service in Off-Network mode shall allow the multi-talker control.
+
+[PR 5.5.6.1-4] The FRMCS Service in Off-Network mode shall provide the means to enable/disable continuous monitoring of the communication links to all involved FRMCS Users of a specific voice, data or video group communication.
+
+[PR 5.5.6.1-5] An authorised FRMCS User in Off-Network mode shall be able to enable/disable continuous monitoring of the communication links to all involved FRMCS Users of a specific voice, data or video group communication.
+
+[PR 5.5.6.1-6] If a degradation or loss of a communication link is detected, the remaining FRMCS Users shall be informed. The ongoing communications among the remaining FRMCS Users shall continue.
+
+[PR 5.5.6.1-7] The FRMCS Service in Off-Network mode shall allow arbitration for Shunting communication.
+
+[PR 5.5.6.1-8] The FRMCS Service in Off-Network mode shall allow FRMCS Users to join an ongoing voice and data communication for Shunting based on their functional identity and location.
+
+[PR 5.5.6.1-9] An authorised FRMCS User shall be able to invite another FRMCS User to join a voice communication, based on his functional identity, FRMCS User Identity, or FRMCS Equipment Identity, even if he is already involved in another active communication.
+
+[PR 5.5.6.1-10] When accepting a communication invitation, in case the FRMCS User has an active voice communication, the FRMCS User shall be able to leave, terminate or merge the voice communication(s).
+
+[PR 5.5.6.1-11] The FRMCS User sending the invitation shall be informed if the targeted FRMCS User receives, accepts, rejects or ignores the invitation.
+
+[PR 5.5.6.1-12] All involved FRMCS User shall be informed when group communication status of an FRMCS user changes e.g. join, leave, on hold, terminate, invite, merge.
+
+[PR 5.5.6.1-13] The FRMCS Service in Off-Network mode shall allow FRMCS Users to leave an ongoing voice and data communication for Shunting based on their functional identity and location.
+
+[PR 5.5.6.1-14] The FRMCS Service in Off-Network mode shall be able to terminate voice, data and video communication for Shunting upon a request received from a functional identity entitled to terminate such communication.
+
+[PR 5.5.6.1-15] The FRMCS Service in Off-Network mode shall provide the means to record Shunting communication and communication related information (e.g. FRMCS Users involved and their roles) to an external system.
+
+[PR 5.5.6.1-16] The FRMCS Service Security Framework shall provide mechanisms in Off-Network mode to cover identity management, authentication, authorisation and data protection in respect to Shunting.
+
+#### 5.5.6.2 Requirements related to the Transport layer
+
+[PR 5.5.6.2-1] The FRMCS Service in Off-Network mode shall not interfere with FRMCS Services in On-Network mode.
+
+[PR 5.5.6.2-2] The FRMCS Service in Off-Network mode shall support the following traffic characteristics of voice, data and video transfer for direct communication for Shunting:
+
+Note: this table is intended to be aligned with TS 22.289 table 5.2.2-2 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experience data rate (UL and DL) | Payload size (Note 2) | Area traffic density (UL and DL) | Overall UE density | Communication range (Note 3) | Service area dimension (Note 4) |
+|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------|---------------------------------------|-----------------------|----------------------------------|----------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| Shunting voice Communication | ≤100 ms | 99,9999% | ≤40 kmph | 100 kbps up to 300 kbps | Small | Up to 1 Mbps/line km | ≤10 shunting members | ≤1.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5) | ≤1.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5) |
+| Shunting data Communication | ≤500 ms | 99,9999% | ≤40 kmph | 10 kbps up to 500 kbps | Small to medium | Up to 10 Mbps/km | ≤10 shunting members | ≤1.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5) | ≤1.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5) |
+| Shunting video Communication | ≤100 ms | 99,9% | ≤40 kmph | 10 Mbps | Medium | Up to 100 Mbps/km | ≤10 | ≤1.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5) | ≤1.5 km along rail tracks including tunnels, bad weather conditions and unfavourable geographical conditions<br>(Note 5) |
+| | NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.<br>NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.<br>NOTE 3: Supported via a single or a combination of 3GPP capabilities of 5GS that best serve these use case in areas with no FRMCS RAN nodes/no FRMCS network coverage.<br>NOTE 4: Estimates of maximum dimensions.<br>NOTE 5: Non-Line-of-Sight (NLOS) between UEs, UE to UE both inside locomotives and unfavourable radio propagation conditions in shunting yards shall be supported. | | | | | | | | |
+
+**Table 5.5.6.2-1: Traffic characteristics for Shunting communications**
+
+## 5.6 Train ready for departure communication
+
+### 5.6.1 Description
+
+Station departure and the platform/train interface is one of the biggest risk areas in railway operations today.
+
+Rail operators implement various different processes for managing station departure with similar objective of ensuring that passengers are safely onboard the train and that the train can safely depart the platform.
+
+Train departure communications includes (1) driver to controller communication and (2) conductor to driver communication. Train ready message sent from the driver to the controller is typically used in main railway stations, in on-network mode. Train ready for departure from a platform involving platform staff (e.g. chief conductor) and driver sent from the platform staff to the driver, is typically used in remote station e.g. rural area, in off-network mode. Another train ready for departure communication scenario in remote stations involves the driver and platform camera(s) to check closing doors and that no passengers are left on the platform without any platform staff.
+
+This section describes Train ready for departure communications in off-network mode. No service handover between on-network and off-network modes is foreseen.
+
+### 5.6.2 Pre-conditions
+
+The Chief conductor (i.e. the FRMCS User) is authorised to initiate Train ready for departure Communications.
+
+### 5.6.3 Service Flows
+
+Monday, 9:30 in the morning. James has been assigned the role of the lead driver of train #12345. His train #12345 stands in platform A, located in a rural railway station where there is no network coverage. The train is ready for boarding. His train should leave at 10:00. James is located in the front cabin (indoor).
+
+Service Flow#1 (driver and platform staff): Bob has been assigned the role of the chief conductor in charge of ensuring a safe boarding for passengers. He stands in platform A, near the train tail.
+
+James and Bob are equipped with devices connected to a UE. They are operating their UEs in off-network mode and have selected their role and platform area to enable data exchanges between each other. The data communications are encrypted to prevent eavesdropping.
+
+Passengers are boarding.
+
+09:59. Train is ready for departure but Bob notes that a Family is running not to miss train #12345. 10:03. All passengers are onboard. Doors are closing. When all doors are safely closed, Bob sends a secured and reliable “Train #12345 is ready for departure” message to James. Bob receives confirmation upon successful reception of the message by James. James acknowledges the message and starts running his train.
+
+Train ready for departure message is recorded (e.g. timestamp, originator, receiver, roles, content) in case something bad happens and somebody wants to review the incident later.
+
+Service Flow#2 (driver and platform camera(s)): two fixed cameras are located on platform A. Camera C1 is located one near the train tail, camera C2 is located at the front cabin. Each camera is connected to a UE operating in off-network mode. Each camera has automatically selected its role and platform area (via static or dynamic configuration) to enable video exchanges with the driver’s UE. The video communication is encrypted to prevent eavesdropping.
+
+Passengers are boarding.
+
+09:59. Train is ready for departure, but a Family is running not to miss train #12345. 10:03. All passengers are onboard. James enables video from camera C1 to check passengers on the platform. Then James switch video from camera C1 to C2. James may also enable video from both cameras C1 and C2. Doors are closing. When all doors are safely closed, James disable videos from cameras C1 and C2. James starts running his train.
+
+Train ready for departure video is recorded (including metadata e.g. timestamp, originator, receiver) in case something bad happens and somebody wants to review the incident later.
+
+
+
+The diagram shows a rural station with two platforms, Platform A and Platform B. A train is stopped at Platform A. A Chief Conductor (blue icon) is on Platform A, and a Lead Driver (green icon) is in the front cabin of the train. A yellow speech bubble from the Chief Conductor contains the text "Train ready for departure". An orange arrow points from the Chief Conductor to the Lead Driver, representing the communication. A blue arrow indicates the train's direction. A legend at the bottom identifies the icons: Chief Conductor (blue), Lead Driver (green), and UE (yellow).
+
+Diagram illustrating the train ready for departure communications scenario at a rural station.
+
+**Figure 5.6.3-1: Train ready for departure communications**
+
+### 5.6.4 Post-conditions
+
+Train ready for departure messages are safely exchanged between the Chief Conductor and the Lead Driver to avoid any safety related issue for passengers before departure.
+
+Train ready for departure videos are safely exchanged between the Chief Conductor and the Fixed Cameras to avoid any safety related issue for passengers before departure.
+
+### 5.6.5 Existing features partly or fully covering the use case functionality
+
+TS 22.280 [4], 22.179 [3], 22.281 [5] and 22.282 [6] have a set of specific requirements on Off-Network MCX Services (including MCCoRe and MCData Services for Off-Network).
+
+TS 22.289 [2] has a set of performance requirements for Off-Network communications for Rail to be refined based on outcomes of the present study.
+
+TS 22.261 [7] has no requirement on 5G Proximity Services.
+
+TS 22.185 [8] and 22.186 [9] have a set of specific requirements on 5G Proximity Services to support V2X communications.
+
+### 5.6.6 Potential New Requirements needed to support the use case
+
+#### 5.6.6.1 Requirements related to the Service layer
+
+[PR 5.6.6.1-1] The FRMCS Service in Off-Network mode shall be able to initiate data and video communications for Train Ready for Departure to relevant FRMCS User upon a request from a functional identity entitled to initiate such communication.
+
+[PR 5.6.6.1-2] The FRMCS Service in Off-Network mode shall provide the necessary communication means to support Train Ready for Departure.
+
+[PR 5.6.6.1-3] The FRMCS Service in Off-Network mode shall allow arbitration for Train Ready for Departure communication.
+
+[PR 5.6.6.1-4] The FRMCS Service in Off-Network mode shall be able to terminate data and video communications for Train Ready for Departure upon a request received from a functional identity entitled to terminate such communication.
+
+[PR 5.6.6.1-5] The FRMCS Service in Off-Network mode shall provide the means to record Train Ready for Departure communication and communication related information (e.g. FRMCS Users involved and their roles) to an external system.
+
+[PR 5.6.6.1-6] The FRMCS Service Security Framework shall provide mechanisms in Off-Network mode to cover identity management, authentication, authorisation and data protection in respect to Train Ready for Departure.
+
+#### 5.6.6.2 Requirements related to the Transport layer
+
+[PR 5.6.6.2-1] The FRMCS Service in Off-Network mode shall support the following traffic characteristics of data and video transfer for direct communication for Train Ready for Departure:
+
+Note: This table is intended to be aligned with TS 22.289 table 5.2.2-2 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experience data rate (UL and DL) | Payload size (Note 2) | Area traffic density (UL and DL) | Overall UE density | Communication range (Note 3) | Service area dimension (Note 4) |
+|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|------------|---------------------------------------|-----------------------|----------------------------------|--------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------|
+| Train Ready for Departure data Communication | ≤500 ms | 99,9% | Stationary | 10 kbps up to 500 kbps | Small to medium | Up to 10 Mbps /km | 2 | ≤1 000 m along rail tracks including bad weather conditions<br>(Note 5) | ≤1 000 m along rail tracks including bad weather conditions<br>(Note 5) |
+| Train Ready for Departure video Communication | ≤100 ms | 99,9% | Stationary | 10 Mbps | Medium | Up to 100 Mbps /km | ≤10 | ≤1 000 m along rail tracks including bad weather conditions<br>(Note 5) | ≤1 000 m along rail tracks including bad weather conditions<br>(Note 5) |
+| | NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.<br>NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.<br>NOTE 3: Supported via a single or a combination of 3GPP capabilities of 5GS that best serve these use case in areas with no FRMCS RAN nodes/no FRMCS network coverage.<br>NOTE 4: Estimates of maximum dimensions.<br>NOTE 5: Non-Line-of-Sight (NLOS) between UEs and UE to UE inside locomotives shall be supported. | | | | | | | | |
+
+**Table 5.6.6.2-1: Traffic characteristics for Train Ready for Departure communication**
+
+## 5.7 Autonomous Train Control and Operation
+
+### 5.7.1 Description
+
+This section describes autonomous train control and operation in off-network mode, where no network is available. In legacy train control systems, trains typically decide its movement by interacting with trackside devices (e.g. track circuits, balise, radio block system) or communicating with a trackside server. If a train can autonomously figure out the positions of the nearby trains and decide its movement authority, the transport capacity of the railway will be enhanced. In the autonomous train control system whose service concept is aligned to the eV2X service, trains share its position by exchanging the information without any centralized server, and each train decides how far it can be authorized to move based on the position information. It is expected that main application area will be mass transportation such as subway.
+
+
+
+Diagram illustrating an autonomous train control scenario. The diagram is split into two parts by a large arrow pointing from left to right. The left part shows a traditional setup where a train (consisting of a locomotive and several cars) is on a track. Above the track, there are two boxes labeled 'EI' and 'ATP'. The 'EI' box is connected to the train and has arrows pointing to the 'ATP' box, labeled 'position' and 'path'. The 'ATP' box is connected to a 'Point machine' on the track. The right part shows an autonomous setup where the train is on the track, and there is a box labeled 'Object controller' above the track. The train is connected to the 'Object controller' by a dashed line, and the 'Object controller' is connected to the 'Point machine' on the track. The train is also connected to another train on the track by a dashed line, representing communication between trains.
+
+**Figure 5.7.1-1 An example of autonomous train control scenario**
+
+### 5.7.2 Pre-conditions
+
+1. Trains know the overall schedule, and the user equipment of each train is connected to the user equipment of the other trains operating at the same time in on-network mode. If on-network mode is not available, the user equipment is connected to the user equipment of other trains in proximity using off-network mode.
+2. A user equipment of each train is able to establish a connection with the object controller for the nearby point machine, where the point machine is a trackside element.
+
+### 5.7.3 Service Flows
+
+1. A train gets started and try registration to the currently operating trains. As a result of the registration, every train positions are known before running.
+2. The train gets the responses of the registration from the other trains and estimates the positions of the trains.
+3. The train decides its movement authority based on the position information and starts moving.
+4. The train positions in the corresponding areas are shared through broadcasting or multicasting. Here, the train position information is updated in a periodic manner.
+5. Based on the periodically updated information, each train updates its movement authority and conduct train control based on it.
+6. If the train needs to connect to the nearby point machine, the train sends switch command with a reliable mechanism in the application layer.
+
+### 5.7.4 Post-conditions
+
+The autonomous train control is achieved by activating movement authority for each train or activating object controller for nearby point machine.
+
+### 5.7.5 Existing features partly or fully covering the use case functionality
+
+The potential new requirement in the followings have been considered only in TR 22.989 V18.0.0.
+
+### 5.7.6 Potential New Requirements needed to support the use case
+
+#### 5.7.6.1 Requirements related to the Service layer
+
+[PR 5.7.6.1-1] The FRMCS System shall provide a reliable mechanism to discover a FRMCS UEs in proximity in off-network.
+
+[PR 5.7.6.1-2] The FRMCS System shall be able to share the train position periodically from one single UE to multiple FRMCS UEs in proximity for train control in off-network.
+
+[PR 5.7.6.1-3] The FRMCS System shall be able to transmit train control data originated from one FRMCS UE to another FRMCS UE in off-network.
+
+#### 5.7.6.2 Requirements related to the Transport layer
+
+[PR 5.7.6.2-1] The FRMCS Service in Off-Network mode shall support the following traffic characteristics of data transfer for direct communication for autonomous train control and operation:
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experienced data rate (UL and DL and SL) | Payload size (Note 2) | Area traffic density (UL and DL and SL) | Overall UE density | Communication range | Service area dimension (Note 3) |
+|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------|-----------------------------------------------|-----------------------|-----------------------------------------|--------------------|---------------------|---------------------------------------------------------------------|
+| Autonomous train control and operation data communication (Korea, urban railway) | ≤100 ms | 99.99 % | ≤100 km/h | ≤1 Mbps | Small to large | ≤5 Mbps/km | ≤15 (3000 m) | ≤3000 m (Note 5) | ≤3000 m along rail tracks including bad weather conditions (Note 4) |
+| | NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.<br>NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.<br>NOTE 3: Estimates of maximum dimensions.<br>NOTE 4: Non-Line-of-Sight (NLOS) between UEs shall be supported.<br>NOTE 5: UEs are assumed to be located at the tail of the leading train and the front of the following train | | | | | | | | |
+
+**Table 5.7.6.2-1: Traffic characteristics for autonomous train control and operation communication – off network communication**
+
+Note: This table is intended to be included in Section 6.2.2.3-1 of TS 22.289 [2]
+
+## 5.8 Virtual Coupling
+
+### 5.8.1 Description
+
+One of the important missions that the future railway service should achieve is to increase its transport capacity. A straight-forward solution is to minimize the distance between successive trains so that train interval is reduced. It is difficult to do so in a legacy train control system, because the successive trains need to have distance as much as a safety margin, which should be larger than the full braking distance.
+
+
+
+Diagram illustrating Virtual Coupling between two trains, T1 and T2. Train T1 is the leading train and Train T2 is the following train. Above the trains, a horizontal blue double-headed arrow indicates the communication range. Below the trains, a dashed blue line represents the 'Present speed' profile of T1, and a solid orange line represents the 'Speed profile of T1'. Another dashed blue line represents the 'Speed profile of T2'. The diagram shows T1 and T2 moving towards the right, with T1 slightly ahead of T2. The speed profiles indicate that T1 is decelerating while T2 is maintaining a constant speed, and the system aims to shorten the safety margin between them.
+
+**Figure 5.8.1-2 Sharing acceleration and braking control information to shorten safety margin**
+
+This safety margin can be further shortened if the successive trains share control information (acceleration and braking) and apply it to its own train control. As shown in Figure 5.8.1-1, the safety margin can be shortened if the following train (T1) immediately knows that the leading train (T2) starts braking and also triggers braking. This is the fundamental principle and the main purpose of virtual coupling. Figure 5.8.2 shows the basic concept of the virtual coupling scenario. Multiple trains which are in close distance move together as they are physically coupled. As the distance between two trains gets smaller, the control information of a train should be delivered to the other in shorter time.
+
+
+
+The diagram illustrates the concept of a virtual train set. At the top, a long horizontal double-headed arrow is labeled "Virtual Train Set". Below it, three trains labeled T1, T2, and T3 are shown on a track, each moving to the right as indicated by yellow arrows. Each train has a "Lock" icon above it. Vertical arrows with radio signal icons connect each train to the "Virtual Train Set" arrow. The entire group of trains and their connections is enclosed in a light blue rounded rectangle.
+
+Diagram of virtual train set concept showing three trains T1, T2, and T3 with locks, connected to a 'Virtual Train Set' via radio signals.
+
+Figure 5.8.1-2 The concept of virtual coupling scenario
+
+### 5.8.2 Pre-conditions
+
+- 1. The leading and following trains in operation recognize each other and have just got configured to be coupled virtually. Here, the recognition is achieved by on-network or off-network.
+- 2. The user equipments for train control support device to device communications in the perspective of transport layer.
+
+
+
+This diagram shows the overall procedure of virtual coupling in three stages. The top stage shows two trains, T1 and T2, on a track with yellow arrows pointing right. A dashed orange line with radio signal icons connects them, and a long horizontal double-headed arrow is above them. The middle stage is similar, but the dashed orange line is more defined. The bottom stage shows the trains closer together, with a yellow circle highlighting the gap. A "Lock" icon is placed over this gap, and a dashed orange double-headed arrow is between the trains. A long horizontal double-headed arrow remains above them.
+
+Three-part diagram showing the overall procedure of virtual coupling between trains T1 and T2, including initial state, connection establishment, and locked state.
+
+Figure 5.8.1-3 Overall procedure of virtual coupling
+
+### 5.8.3 Service Flows
+
+1. The following train begins to approach to the leading train by exchanging the information about their position. The two trains, which are far enough to allow a certain amount of end-to-end latency, are initially connected through the on-network.
+2. As the following train approaches to the leading train, they start exchanging the information about movement control and each train then controls itself while considering the control of the other train. The two trains, which are still far enough to allow a certain amount of end-to-end latency, keep the connection through the on-network.
+3. As the following train further approaches to the leading train, the safe braking distance gets shorter and they are required to have a connection of which end-to-end latency is very short for delicate train control. At this moment, they seamlessly switch the connection from the on-network to off-network. Each train can maintain the on-network connection, as an auxiliary connection, as long as it is within the coverage.
+4. As the following train even further approaches the leading train so that the distance between the tail-end of the leading train and the front-end of the following train becomes shorter than the safe braking distance, the off-network connection requires extremely high reliability as well as short end-to-end latency to prevent potential accidents. In this case, two trains can be regarded as if they are physically coupled, communicating via wireless train backbone (WLTB).
+
+### 5.8.4 Post-conditions
+
+For safety train operation, integrity needs to be checked for train control information delivery in the perspective of application or transport layer. Any error on integrity check shall be immediately reported to the train control application.
+
+### 5.8.5 Existing features partly or fully covering the use case functionality
+
+The potential new requirement in the followings have been considered only in TR 22.989 V18.0.0.
+
+### 5.8.6 Potential New Requirements needed to support the use case
+
+#### 5.8.6.1 Requirements related to the Service layer
+
+Note: Off-network is used even when network coverage is available.
+
+[PR 5.8.6.1-1] The FRMCS system shall be able to provide integrity protection for off-network train control communication.
+
+[PR 5.8.6.1-2] The FRMCS System shall support seamless service continuity between on-network based connection and off-network based connection
+
+[PR 5.8.6.1-3] The FRMCS System shall support UEs capable of utilizing off-network and on-network communications at the same time.
+
+[PR 5.8.6.1-4] The FRMCS System shall provide a mechanism to change the QoS requirements of the off-network communication adaptively.
+
+#### 5.8.6.2 Requirements related to the Transport layer
+
+[PR 5.8.6.2-1] The FRMCS system shall be able to provide integrity protection for off-network train control communication
+
+[PR 5.8.6.2-2] The FRMCS Service in Off-Network mode shall support the following traffic characteristics of data transfer for direct communication for virtual coupling:
+
+Note: This table is intended to be included in Section 6.2.2.3-1 of TS 22.289 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | UE Relative Speed | User experienced data rate (UL and DL and SL) | Payload size (Note 2) | Area traffic density (UL and DL and SL) | Overall UE density | Communication range | Service area dimension (Note 3) |
+|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-----------|-------------------|-----------------------------------------------|-----------------------|-----------------------------------------|--------------------|---------------------|--------------------------------------------------------------------|
+| Virtual coupling, critical data communication on (Korea, urban railway) | ≤ 100 ms | 99.99% | ≤100 km/h | ≤ 50km/h | ≤1Mbps | Small to large | ≤5 Mbps/km | ≤15 (3000 m) | ≤3000 m (Note 6) | ≤3 000 m along rail tracks including bad weather conditions |
+| Virtual coupling, Very critical data communication on (Korea, urban railway) (Note 5) | ≤ 10 ms | 99.9999 % | ≤100 km/h | ≤ 50km/h | ≤1Mbps | Small to large | ≤20 Mbps/km | ≤6 (300 m) | ≤ 300 m (Note 6) | ≤300 m along rail tracks including bad weather conditions (Note 4) |
+| | NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.<br>NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.<br>NOTE 3: Estimates of maximum dimensions.<br>NOTE 4: Non-Line-of-Sight (NLOS) between UEs shall be supported.<br>NOTE 5: Data link between trains can work as like wireless train backbone<br>NOTE 6: UEs are assumed to be located at the tail of the leading train and the front of the following train | | | | | | | | | |
+
+**Table 5.8.6.2-1: Traffic characteristics for Virtual coupling communication**
+
+[PR 5.8.6.2-3] The FRMCS System shall establish an immediate communication session between entities for virtual coupling.
+
+**Editor's note: The requirement above is FFS**
+
+[PR 5.8.6.2-4] The FRMCS System shall support seamless service continuity between on-network based connection and off-network based connection.
+
+**Editor's note: The requirement above is FFS**
+
+[PR 5.8.6.2-5] The FRMCS System shall support UEs capable of utilizing off-network and on-network communications at the same time.
+
+**Editor's note: The requirement above is FFS**
+
+## 5.9 Monitoring and control of critical infrastructure communication
+
+### 5.9.1 Description
+
+Monitoring and controlling critical infrastructure such as train detection, signals and indicators, movable infrastructure, level crossing elements, including barrier controls, vehicle sensors, lighting controls and alarms, are essential part of operating trains in areas where no network is available e.g. rural areas, harbours.
+
+Monitoring and controlling critical infrastructure can be done by radio, in on-network or in off-network modes. This section describes monitoring and control of critical infrastructure communications in off-network mode, where no network is available. No service handover between on-network and off-network modes is foreseen.
+
+### 5.9.2 Pre-conditions
+
+The Chief conductor (i.e. the FRMCS User) is authorised to initiate Monitoring or controlling critical infrastructure communications.
+
+### 5.9.3 Service Flows
+
+Monday, 9:30 in the morning. James has been assigned the role of the lead driver of train #12345. His train #12345 stands in platform A, located in a Harbour railway station where there is no network coverage. The train is ready for boarding and starts running at 10:00. James is located in the front cabin (indoor).
+
+Before leaving the Harbour area, James has to run its train through many level crossings. In order to run safely the level crossing (LX), James has to detect vehicles in the level crossing area using fixed video camera of this area.
+
+James is equipped with an onboard device with display connected to a UE. LX surveillance camera is also connected to a UE. James and the camera are operating their UEs in off-network mode and have selected their role to enable video exchanges. The video communications are encrypted to prevent eavesdropping.
+
+When James approaching the LX, James enables video from LX surveillance camera to detect vehicles. James primarily relies on the remote LX surveillance camera vision to identify obstacles (e.g. vehicles) and to make decision on whether to enter the LX area. When no vehicles are detected, James is allowed to run its train through the LX area. When the train has left the LX area, James disable videos from LX surveillance camera. James continues running his train to next LX.
+
+
+
+Diagram illustrating the monitoring and control of critical infrastructure communications at a level crossing (LX). A train is shown moving from left to right, indicated by a blue arrow labeled 'Train direction'. The train is approaching a level crossing where a car is stopped behind a barrier. A yellow box labeled 'Trackside LX train detector' is positioned on the tracks. A yellow arrow points from the detector to a camera labeled 'LX surveillance camera' mounted on a pole. Another yellow arrow points from the camera to a blue box labeled 'LX controller' located near the barrier. The barrier is red and white striped.
+
+**Figure 5.9.3-1: Monitoring and control of critical infrastructure communications**
+
+### 5.9.4 Post-conditions
+
+Monitoring and controlling critical infrastructure videos are safely exchanged between the Chief Conductor and the Fixed Cameras to avoid any safety related issue at level crossings.
+
+### 5.9.5 Existing features partly or fully covering the use case functionality
+
+TS 22.280 [4], 22.179 [3], 22.281 [5] and 22.282 [6] have a set of specific requirements on Off-Network MCX Services (including MCCoRe and MCData Services for Off-Network).
+
+TS 22.289 [2] has a set of performance requirements for Off-Network communications for Rail to be refined based on outcomes of the present study.
+
+TS 22.261 [7] has no requirement on 5G Proximity Services.
+
+TS 22.185 [8] and 22.186 [9] have a set of specific requirements on 5G Proximity Services to support V2X communications.
+
+### 5.9.6 Potential New Requirements needed to support the use case
+
+#### 5.9.6.1 Requirements related to the Service layer
+
+[PR 5.9.6.1-1] The FRMCS Service in Off-Network mode shall be able to initiate video communications for Monitoring and controlling critical infrastructure to relevant FRMCS User upon a request from a functional identity entitled to initiate such communication.
+
+[PR 5.9.6.1-2] The FRMCS Service in Off-Network mode shall provide the necessary communication means to support Monitoring and controlling critical infrastructure.
+
+[PR 5.9.6.1-3] The FRMCS Service in Off-Network mode shall allow arbitration for Monitoring and controlling critical infrastructure.
+
+[PR 5.9.6.1-4] The FRMCS Service in Off-Network mode shall be able to terminate video communications for Monitoring and controlling critical infrastructure upon a request received from a functional identity entitled to terminate such communication.
+
+[PR 5.9.6.1-5] The FRMCS Service in Off-Network mode shall provide the means to record Monitoring and controlling critical infrastructure communication and communication related information (e.g. FRMCS Users involved and their roles) to an external system.
+
+[PR 5.9.6.1-6] The FRMCS Service Security Framework shall provide mechanisms in Off-Network mode to cover identity management, authentication, authorisation and data protection in respect to Monitoring and controlling critical infrastructure.
+
+#### 5.9.6.2 Requirements related to the Transport layer
+
+[PR 5.9.6.2-1] The FRMCS Service in Off-Network mode shall support the following traffic characteristics of video transfer for direct communication for Monitoring and controlling critical infrastructure:
+
+Note: this table is intended to be aligned with TS 22.289 table 5.2.2-2 [2]
+
+| Scenario | End-to-end latency | Reliability (Note 1) | UE speed | User experience data rate (UL and DL) | Payload size (Note 2) | Area traffic density (UL and DL) | Overall UE density | Communication range (Note 3) | Service area dimension (Note 4) |
+|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------|---------------------------------------|-----------------------|----------------------------------|--------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------|
+| Monitoring and controlling critical infrastructure video Communication | ≤100 ms | 99,9% | ≤40 km/h | 10 Mbps | Medium | Up to 20 Mbps/km | 2 | ≤1 000 m along rail tracks including bad weather conditions<br>(Note 5) | ≤1 000 m along rail tracks including bad weather conditions<br>(Note 5) |
+| | NOTE 1: Reliability as defined in TS 22.289 sub-clause 3.1.<br>NOTE 2: Small: payload ≤ 256 octets, Medium: payload ≤512 octets; Large: payload 513 -1500 octets.<br>NOTE 3: Supported via a single or a combination of 3GPP capabilities of 5GS that best serve these use case in areas with no FRMCS RAN nodes/no FRMCS network coverage.<br>NOTE 4: Estimates of maximum dimensions.<br>NOTE 5: Non-Line-of-Sight (NLOS) between UEs and UE to UE inside locomotives shall be supported. | | | | | | | | |
+
+**Table 5.9.6.2-1: Traffic characteristics for Monitoring and controlling critical infrastructure communication**
+
+# --- 6 Void.
+
+## 6.1 Void.
+
+# --- 7 Void.
+
+## 7.1 Void.
+
+# --- 8 Identified issues
+
+## 8.1 Introduction
+
+This section summarizes open points identified by SA1 as part of the gap analysis of the use cases captured above, e.g. about limitations, missing requirements and gaps in existing functionalities supported by 3GPP.
+
+## 8.2 Identified issue 1: Communication range
+
+### 8.2.1 Description
+
+Some of the use cases described in clauses 5, 6 and 7 of the present document (e.g. the Trackside Maintenance Warning System communication) require communication range of up to several kilometres (e.g. 8.5 km) along rail tracks including tunnels, bad weather conditions, unfavourable geographical conditions, and non-Line-of-Sight (NLOS) between UEs i.e. obstructions.
+
+Communication range is to be understood as the maximum distance between users operating UEs without performance degradations. Users may be stationary, pedestrians or in motion up to 500 kmph.
+
+### 8.2.2 Limitations, missing requirements and gaps
+
+<Describe limitations, missing requirements and gaps in existing functionalities supported by 3GPP, identified during this study.>
+
+## 8.3 Identified issue 2: MCX Support
+
+### 8.x.1 Description
+
+Some of the use cases described in clauses 5, 6 and 7 of the present document (refer to subclauses describing requirements to the Service layer) require support of MCX Services.
+
+The following MCX capabilities should be supported by Off-Network for Rail.
+
+Due to the nature of Off-Network communication, it is expected that the functionality of those MCX capabilities might be reduced compared to On-Network communication.
+
+- MCX Service common capabilities:
+ - Group communications,
+ - Private communications,
+ - Late Communication Entry,
+
+- Functional Alias,
+- Location Service,
+- E2E Security,
+- User Authentication and Service Authorization,
+- Service Arbitration,
+- QoS and Priority,
+- Performance Monitoring and Exposure Service,
+- Recording Metadata,
+- Transition from Off-Network to On-Network (and vice-versa) (i.e. Service Continuity),
+- Service Configuration (i.e. local + central when transiting from Off-Network to On-Network),
+- MCX Service Types:
+ - MCPTT,
+ - MCData,
+ - MCVideo.
+- MCX Service capabilities per Service Type:
+ - MCPTT
+ - Floor Control,
+ - Multi-Talker Control.
+ - MCData
+ - SDS,
+ - IP Connectivity.
+ - MCVideo
+ - Video Streams.
+
+### 8.x.2 Limitations, missing requirements and gaps
+
+<Describe limitations, missing requirements and gaps in existing functionalities supported by 3GPP, identified during this study.>
+
+## 8.x Identified issue y: <Identified issue title>
+
+### 8.x.1 Description
+
+<Describe the issue (i.e. problem statement).>
+
+### 8.x.2 Limitations, missing requirements and gaps
+
+<Describe limitations, missing requirements and gaps in existing functionalities supported by 3GPP, identified during this study.>
+
+# --- 9 Consolidated potential requirements
+
+# --- 10 Conclusion and recommendations
+
+This technical report identifies several use cases, and potential new requirements for 5GS support of Rail Off-Network. Some open points identified as part of the gap analysis of the use cases have been collected and detailed in clause 8 (e.g., communication range, MCX support).
+
+A further step is necessary to identify limitations, missing requirements and gaps in existing functionalities supported by 3GPP before any potential normative work. This step could be performed by external bodies involved in the definition of Rail Off-Network use cases (e.g., UIC, ETSI TC RT).
+
+It is therefore recommended to wait for further gap analysis before finalizing consolidated requirements in this TR and trigger potential subsequent normative work (if deemed necessary).
+
+# Annex A: Change history
+
+| Change history | | | | | | | | |
+|----------------|----------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------|--|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2020-09 | SA1#91-e | S1-203281 | | | | TR Skeleton for Study on Off-Network for Rail | | 0.0.0 |
+| 2020-09 | SA1#91-e | S1-203254 | | | | FS_OFFNETRAIL TR 22.990 Introduction | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203355 | | | | FS_OFFNETRAIL TR 22.990 Scope | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203256 | | | | FS_OFFNETRAIL TR 22.990 Overview | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203257 | | | | FS_OFFNETRAIL TR 22.990 Chapter 5 | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203258 | | | | FS_OFFNETRAIL TR 22.990 Chapter 6 | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203259 | | | | FS_OFFNETRAIL TR 22.990 Chapter 7 | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203328 | | | | FS_OFFNETRAIL TR 22.990 Key Issues | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203329 | | | | FS_OFFNETRAIL TR 22.990 UC Trackside Maintenance Warning System | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203330 | | | | FS_OFFNETRAIL TR 22.990 UC Remote Control of Engines | | 0.1.0 |
+| 2020-09 | SA1#91-e | S1-203385 | | | | Incorporated all agreed contributions to TR 22.990 at SA1#91e | | 0.1.0 |
+| 2020-11 | SA1#92-e | S1-204035 | | | | Introduce "Train integrity monitoring data communication" use case | | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204036 | | | | Introduce "Shunting communication" use case | | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204037 | | | | Introduce "Train ready for departure communication" use case | | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204413 | | | | Autonomous Train Control and Operation: Moving Authority Perspective | | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204414 | | | | Virtual Coupling Use Case | | 0.2.0 |
+| 2020-11 | SA1#92-e | S1-204148 | | | | Identified issue: Communication range | | 0.2.0 |
+| 2021-03 | SA1#93-e | S1-210228 | | | | Enhance "Train ready for departure communication" use case with video | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210230 | | | | Enhance "Shunting communication" use case with video | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210427 | | | | New "Monitoring and Control of Critical Infrastructure communication" use case | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210428 | | | | Off-Net Railways Update to sec.8 | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210429 | | | | Add "MCX Support" as an identified issue to be solved by 3GPP technology as required by Off-Network for Rail | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210430 | | | | Enhancement of "Virtual coupling" use case | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210240 | | | | Do not exclude any single or a combination of 3GPP capabilities to support Rail Off-Network use cases | | 0.3.0 |
+| 2021-03 | SA1#93-e | S1-210244 | | | | Request for clarification on relationship between TR 22.990 and TS 22.289 QoS scenarios and traffic characteristics | | 0.3.0 |
+| 2021-09 | SA1#95-e | S1-213292 | | | | Updates to "Virtual coupling" use case | | 0.4.0 |
+| 2021-09 | SA1#95-e | S1-213293 | | | | Updates to "Autonomous train control and operation" use case | | 0.4.0 |
+| 2021-09 | SA1#95-e | S1-213294 | | | | Updates to "Conclusion and Recommendations" clause | | 0.4.0 |
+| 2021-09 | SA#93e | SP-211043 | | | | Raised to v.1.0.0 for presentation for information | | 1.0.0 |
+| 2021-11 | SA1#96-e | S1-214031 | | | | Global clean up to remove unnecessary clauses | | 1.1.0 |
+| 2021-11 | SA1#96-e | S1-214032 | | | | Clean up of references | | 1.1.0 |
+| 2021-12 | SA#94e | SP-211504 | | | | Raised to v.2.0.0 for presentation for approval | | 2.0.0 |
+| 2021-12 | SA#94e | SP-211504 | | | | Raised to v.18.0.0 following SA#94e's approval | | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32130/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-18/32_series/32130/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..847b9bd569abbf80716455c525ccf4baa2a09f8b
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1d67d7a6f813eb6b875b35c8cf6622ef9694be61334617c2ea42b660b743edd
+size 54305
diff --git a/marked/Rel-18/32_series/32130/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32130/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcfe5d2d6a391aa958fcabc8430ab5afd99d52e6
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9755410aa1361e1dca8998ebdb2d5c90e8fda9518b7ae67c77c9442011e81c52
+size 9200
diff --git a/marked/Rel-18/32_series/32130/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32130/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..248fdcfd81c8742d7ccfe78b179f98d62f269470
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6414a0765a8c4ca4d92c242268dbf81a6b7454b63f33b1197d4fb2e1edd35033
+size 5171
diff --git a/marked/Rel-18/32_series/32130/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/32_series/32130/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5c59c8909b17428617749bc53b0017f0385bf93
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5c941424e29e853c6aff4399ce688a7114a54dfb0d70f03a1a97fdf011881da
+size 40356
diff --git a/marked/Rel-18/32_series/32130/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-18/32_series/32130/a7c51c18111139f9aca2805114108565_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c746947d1ec18febc07620c0b0130def1f899b3
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/a7c51c18111139f9aca2805114108565_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:334dae35ab9732e290ebc0c6ddeab2f20c53068ee4e1fbf0cc691b57b620fe5a
+size 65883
diff --git a/marked/Rel-18/32_series/32130/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-18/32_series/32130/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..85efe170cf5ee82d7fb8de2225c25320ec3f4676
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b57f294903d52ae50f5035b330a411d6bcb6287b0b65dd1a6171ed95f3ee2abc
+size 38554
diff --git a/marked/Rel-18/32_series/32130/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-18/32_series/32130/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d94d9eed6595498adab79aec6632c271feab29a1
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46348033a64704e4ceec4b63cb5c43025629411afb08f86f43e93276e07e4335
+size 55413
diff --git a/marked/Rel-18/32_series/32130/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-18/32_series/32130/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38a980fef4db2ed62391d7afa84d88e9e9f5ceab
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95a8852a2917e531cdd4d6c8cc37f0c4d2376d6ce3d4dd9265fcebe2817d16e9
+size 52553
diff --git a/marked/Rel-18/32_series/32130/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/Rel-18/32_series/32130/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16200eb922d95fb06e359c0764e0a4ec01770bfe
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39d6191356c9af437e17da745ce4085a359e203fc4df0169f473230108081a8f
+size 17875
diff --git a/marked/Rel-18/32_series/32130/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-18/32_series/32130/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a864fce3d04d8b6758d9d16069e70617dd7b5035
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77f103064db98198f08edf67e8e7b625445e43db480858c7d7466d7c642410e9
+size 58578
diff --git a/marked/Rel-18/32_series/32130/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-18/32_series/32130/dbe553cf16dd14073b89a8263a428664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96109f40e51268e2a3b59827fa2e1a9e9537ae46
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/dbe553cf16dd14073b89a8263a428664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03d41829843b9c0c1e19b179184b074e9d65f07e590c867db982e1d70ca0cebc
+size 56801
diff --git a/marked/Rel-18/32_series/32130/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/32_series/32130/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51e4bed714bdb79cd0edd224e9dcea0e3f517db8
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b04d75c839c89f39e3dfe3c23bdaf4f5d53a8ea43bc76342a1688e1acc666e68
+size 42919
diff --git a/marked/Rel-18/32_series/32130/raw.md b/marked/Rel-18/32_series/32130/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6ca030678b420e5553ca30b9b8d59378e6f11a6
--- /dev/null
+++ b/marked/Rel-18/32_series/32130/raw.md
@@ -0,0 +1,693 @@
+
+
+# 3GPP TS 32.130 V18.1.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Network sharing; Concepts and requirements (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+Network sharing, Management, 3GPP
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Concepts and background ..... | 7 |
+| 4.1 RAN sharing scenarios..... | 7 |
+| 4.2 Management architecture ..... | 9 |
+| 5 Business level requirements..... | 10 |
+| 5.1 Requirements..... | 10 |
+| 5.1.1 Requirements for the OAM&P of shared RAN ..... | 10 |
+| 5.1.2 Requirements for the OA&M of shared core network elements ..... | 11 |
+| 5.1.3 Requirements for the management of measurements for cross-operator accounting based on data volume and QoS ..... | 11 |
+| 5.1.4 Requirements for management support for NG-RAN MOCN network sharing scenario with same Cell Identity broadcast..... | 12 |
+| 5.1.5 Requirements for management support for NG-RAN MOCN network sharing scenario with multiple Cell Identity broadcast..... | 12 |
+| 5.1.6 Requirements for the OAM&P of shared NG-RAN ..... | 12 |
+| 5.2 Actor roles ..... | 13 |
+| 5.3 Telecommunications resources ..... | 13 |
+| 5.4 High-level use cases..... | 13 |
+| 5.4.1 Fully pooled radio resources between two POPs ..... | 13 |
+| 5.4.2 Alarm raised on a shared cell (MOCN scenario) ..... | 14 |
+| 5.4.3 Single DM for managing S-RAN and POP own RAN..... | 15 |
+| 5.4.4 Management of measurements for cross-operator accounting based on data volume and QoS ..... | 15 |
+| 5.4.5 Management support for the mixed deployment scenario of shared NG-RAN network elements and non-shared NG-RAN network elements ..... | 15 |
+| 5.4.6 Radio resources partitioning between two POPs for the shared NG-RAN ..... | 16 |
+| 6 Specification level requirements..... | 17 |
+| 6.1 Requirements..... | 17 |
+| 6.2 Actor roles ..... | 17 |
+| 6.3 Telecommunications resources ..... | 17 |
+| 6.4 Use cases ..... | 17 |
+| 6.4.1 Management of measurements for cross-operator accounting based on data volume and QoS ..... | 17 |
+| 7 Management workflows for requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario ..... | 18 |
+| 7.1 Management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the same cell Identity broadcast ..... | 18 |
+| 7.2 Management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the multiple cell Identity broadcast ..... | 19 |
+| <b>Annex A (informative): Network sharing agreement .....</b> | <b>21</b> |
+| <b>Annex B (informative): Change history .....</b> | <b>22</b> |
+
+# --- 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
+
+Network sharing is emerging as a mechanism for operators to substantially and sustainably improve network costs and to efficiently utilize network capacity. The traditional model of single ownership of all network layers and elements is being challenged and more and more operators are adopting network sharing as a means of cutting the heavy costs involved in initial roll-out, capital expenditure (CAPEX) and operational expenditure (OPEX).
+
+In general, an increasing number of operators are sharing their mobile networks. Main arguments presented are:
+
+- Increased rollout speed.
+- Quickly expanding coverage to meet customer demand for wider coverage.
+- Sharing low traffic areas.
+- Sharing high license burdens.
+- Lower CAPEX and OPEX.
+
+Network sharing has some major implications on the operations of the network. Alignment on operational priorities, common network planning/evolution strategy, sharing end user data/subscriber data, sharing performance data, alarms etc. in the shared network need to be considered carefully. Privacy, security and competitive information are also important for the operations of a shared network.
+
+# --- 1 Scope
+
+The present document describes concepts and high-level requirements for the Operations, Administration, Maintenance and Provisioning (OAM&P) of network sharing.
+
+Network sharing scenarios considered in the present document are Multiple Operator Core Network (MOCN) and Gateway Core Network (GWCN) for GERAN, UTRAN and E-UTRAN, as defined in TS 23.251 [7] , and Multiple Operator Core Network (MOCN) for NG-RAN as defined in TS 23.501[7].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [3] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [4] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
+- [5] 3GPP TS 23.251: "Network sharing; Architecture and functional description".
+- [6] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 – Measurements"
+- [7] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage2".
+- [8] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
+- [9] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TS 32.101 [2], TS 32.102 [3] and 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 TS 32.101 [2], TS 32.102 [3] and TR 21.905 [1], in that order.
+
+Organizational roles:
+
+**Master Operator (MOP):** In Radio Access Network (RAN) and/or Core Network (CN) sharing scenarios, deployment and daily operation of shared network elements are entrusted to a single Actor, called the Master Operator. The Master
+
+Operator provides network and OAM&P services to other Operators, called Participating Operators (POPs). The Master Operator is the only one to have a direct OAM&P connection from its Domain Manager (DM) to the shared network elements.
+
+**Participating Operator (POP):** Participating Operators are service providers who share, alongside other Participating Operators, the network (RAN and/or CN) facilities provided by the Master Operator. According to TS 36.300 [4] up to 6 operators can share a RAN.
+
+NOTE: In a RAN/CN sharing scenario where Company A and Company B are POPs, MOP represents a role which can be played by either:
+
+- Company A or Company B: in that case, Company A or Company B plays both roles, i.e. is the MOP and one of the POPs simultaneously, or
+- A joint-venture between Company A and Company B, or
+- A third-party entity: in this context, third party is referring to a wholesale mobile connectivity provider.
+
+In the two latter cases, companies A and B rely on another company to play the role of MOP. This company cannot play the role of POP.
+
+Management systems:
+
+**Master Operator Network Manager (MOP-NM):** Network Manager enabling the Master Operator to manage the shared RAN and/or shared CN.
+
+**Master Operator Shared CN DM (MOP-SC-DM):** Domain Manager enabling the Master Operator to manage the Shared CN.
+
+**Master Operator Shared RAN DM (MOP-SR-DM):** Domain Manager enabling the MOP to manage the Shared RAN.
+
+**Participating Operator CN DM (POP-CORE-DM):** Domain Manager enabling a Participating Operator to manage its own (not shared) Core Network.
+
+**Participating Operator Network Manager (POP-NM):** Network Manager enabling a Participating Operator to manage its own (not shared) network and its portion of the shared network.
+
+**Participating Operator RAN DM (POP-RAN-DM):** Domain Manager enabling a Participating Operator to manage its own (not shared) RAN.
+
+Managed resources in a shared Radio Access Network (RAN) environment:
+
+**Shared RAN (S-RAN):** A set of Radio Access Network elements shared among Participating Operators.
+
+Managed resources in a shared Core Network (CN) environment:
+
+**Shared CN (S-CORE):** A set of Core Network elements shared among Participating Operators. It may or may not include all core network elements. For example, the Participating Operators may share only the MMEs while having independent S/P GWs.
+
+## 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].
+
+| | |
+|-----|-----------------------------------|
+| ARP | Allocation and Retention Priority |
+| DL | Downlink |
+
+| | |
+|-------------|----------------------------------------------------------|
+| DM | Domain Manager |
+| GBR | Guaranteed Bit Rate |
+| GWCN | Gateway Core Network |
+| MDT | Minimization of Drive Tests |
+| MOCN | Multiple Operator Core Network |
+| MOP | Master Operator |
+| MOP-NM | Master Operator Network Manager |
+| MOP-SC-DM | Master Operator Shared CN DM |
+| MOP-SR-DM | Master Operator Shared RAN DM |
+| NGCOR | Next Generation Converged Operations Requirements |
+| OAM&P | Operations, Administration, Maintenance and Provisioning |
+| POP | Participating Operator |
+| POP-CORE-DM | Participating Operator CN DM |
+| POP-NM | Participating Operator Network Manager |
+| POP-RAN-DM | Participating Operator RAN DM |
+| QCI | Quality of Service Class Indicator |
+| QoS | Quality of Service |
+| SON | Self-Organizing Networks |
+| S-CORE | Shared CN |
+| S-RAN | Shared RAN |
+| UL | Uplink |
+
+# --- 4 Concepts and background
+
+## 4.1 RAN sharing scenarios
+
+Various network sharing scenarios exist, amongst which one category is RAN sharing which can be divided into the following (non exhaustive) list of sub-categories:
+
+- Passive RAN sharing, also known as infrastructure sharing (including site sharing).
+- Active RAN sharing, where active network elements of the RAN are shared:
+ - RAN-only sharing (MOCN; see TS 23.251 [5] and TS 23.501 [7]), i.e. BTSs / BSCs (respectively NodeBs / RNCs and eNodeBs) in a 2G Radio Access Network (respectively a 3G Radio Access Network and an E-UTRA network) , and gNBs in a 5G NR network;
+ - Gateway Core Network (GWCN; see TS 23.251 [5]), in which not only the Radio Access Network elements are shared but also part or all of the Core Network elements (there is no passive core network sharing).
+
+The following figures depict the MOCN scenarios:
+
+
+
+The diagram illustrates an E-UTRAN MOCN network sharing scenario. At the top, two clouds represent the core networks for 'Participating Operator A' and 'Participating Operator B'. Each cloud contains two boxes labeled 'MME' and 'S/P-GW'. Below the core networks, the RAN is divided into three zones: 'Op A owned zone', 'Shared zone', and 'Op B owned zone'. The 'Op A owned zone' contains two 'eNB' (evolved NodeB) icons and is associated with 'PLMN A'. The 'Shared zone' contains two 'eNB' icons and is associated with both 'PLMN A' and 'PLMN B'. The 'Op B owned zone' contains two 'eNB' icons and is associated with 'PLMN B'. Lines connect the 'MME' and 'S/P-GW' in Operator A's core network to the eNBs in the Op A owned zone and the Shared zone. Similarly, lines connect the 'MME' and 'S/P-GW' in Operator B's core network to the eNBs in the Shared zone and the Op B owned zone.
+
+Diagram of E-UTRAN MOCN network sharing scenario showing two operators (A and B) sharing a common radio access network (RAN) with eNBs and core network elements (MME, S/P-GW).
+
+Figure 4.1-1: E-UTRAN MOCN network sharing scenario
+
+
+
+The diagram illustrates an NG-RAN MOCN Network Sharing scenario with the same cell identity broadcast. At the top, two clouds represent the core networks for 'Participating Operator A' and 'Participating Operator B'. Each cloud contains two boxes labeled '5GC NF(s)'. Below the core networks, the RAN is divided into three zones: 'Op A owned zone', 'Shared zone', and 'Op B owned zone'. The 'Op A owned zone' contains two 'gNB' (next-generation NodeB) icons and is associated with 'PLMN A'. The 'Shared zone' contains two 'gNB' icons and is associated with both 'PLMN A' and 'PLMN B'. The 'Op B owned zone' contains two 'gNB' icons and is associated with 'PLMN B'. Lines connect the '5GC NF(s)' in Operator A's core network to the gNBs in the Op A owned zone and the Shared zone. Similarly, lines connect the '5GC NF(s)' in Operator B's core network to the gNBs in the Shared zone and the Op B owned zone.
+
+Diagram of NG-RAN MOCN Network Sharing with same cell identity broadcast scenario, showing two operators (A and B) sharing a common radio access network (RAN) with gNBs and 5GC NF(s).
+
+Figure 4.1-2: NG-RAN MOCN Network Sharing with same cell identity broadcast scenario
+
+
+
+Diagram of NG-RAN MOCN Network Sharing with multiple cell identity broadcast scenario. It shows two core networks, 'Participating Operator A Core Network' and 'Participating Operator B Core Network', each containing two '5GC NF(s)' blocks. These are connected to three zones: 'Op A owned zone' (with PLMN A and two gNBs), 'Shared zone' (with PLMN A, NR cell A, TAC A, PLMN B, NR cell B, TAC B and two gNBs), and 'Op B owned zone' (with PLMN B and two gNBs).
+
+Figure 4.1-3 NG-RAN MOCN Network Sharing with multiple cell identity broadcast scenario
+
+In GWCN, besides sharing Radio Access Network nodes, the POPs also share Core Network nodes (see TS 23.251 [5] – clause 4.1).
+
+
+
+Diagram of GateWay Core Network (GWCN). It shows two core networks, 'Participating Operator A Core Network' and 'Participating Operator B Core Network', each containing an 'MME' and an 'S-/P-GW'. These are connected to three zones: 'Op A owned zone' (with PLMN A and two eNBs), 'Shared zone' (with PLMN A, PLMN B and two eNBs), and 'Op B owned zone' (with PLMN B and two eNBs). The 'S-/P-GW' and 'MME' are shared across the zones, with the 'MME' being centrally located in the shared zone.
+
+Figure 4.1-4: GateWay Core Network (GWCN)
+
+## 4.2 Management architecture
+
+The management architecture for MOCN is depicted in figure 4.2-1. It is compliant with 3GPP management reference model (TS 32.101 [2]).
+
+
+
+The diagram illustrates the management architecture for MOON. At the top, there are two stacks of boxes labeled 'POP-NM' and 'MOD-NM'. Below these, a dashed horizontal line represents the 'Itf-N' interface. Below the interface, there are three boxes: 'POP-RAN-DM', 'MOP-SR-DM', and 'POP-RAN-DM'. The 'MOP-SR-DM' box is connected to the 'MOD-NM' and 'MOP-NM' boxes above it. Below each 'POP-RAN-DM' box is a box labeled 'MSC/SGSN/HLR/MME/HSS'. Below each 'MSC/SGSN/HLR/MME/HSS' box is a box labeled 'BTS/BSC/RNC/(e)NodeB'. Below the 'MOP-SR-DM' box is a box labeled 'S-RAN (BTS/BSC/RNC/(e)NodeB)'. At the bottom, there are three labels: 'NEs owned by Participating Operator A (MCC 1, MNC 1)' under the left 'BTS/BSC/RNC/(e)NodeB', 'NEs owned by Master Operator and shared between POs' under the 'S-RAN', and 'NEs owned by Participating Operator B (MCC 1, MNC 2)' under the right 'BTS/BSC/RNC/(e)NodeB'.
+
+Management architecture for MOON diagram showing POP-NM, MOD-NM, MOP-NM, POP-RAN-DM, MOP-SR-DM, MSC/SGSN/HLR/MME/HSS, and BTS/BSC/RNC/(e)NodeB connected via Itf-N interface.
+
+Figure 4.2-1: Management architecture for MOON
+
+In the MOON scenario, all cells of the S-RAN are shared between POPs.
+
+The management architecture for GWCN is depicted in figure 4.2-2. It is compliant with 3GPP management reference model (TS 32.101 [2]).
+
+
+
+The diagram illustrates the management architecture for GWCN. At the top, there are two stacks of boxes labeled 'POP-NM' and 'MOD-NM'. Below these, a dashed horizontal line represents the 'Itf-N' interface. Below the interface, there are three boxes: 'POP-RAN-DM', 'MOP-SR-DM', and 'POP-RAN-DM'. The 'MOP-SR-DM' box is connected to the 'MOD-NM' and 'MOP-NM' boxes above it. Below each 'POP-RAN-DM' box is a box labeled 'POP-CORE-DM'. Below each 'POP-CORE-DM' box is a box labeled 'MSC/SGSN/HLR/MME/HSS'. Below each 'MSC/SGSN/HLR/MME/HSS' box is a box labeled 'BTS/BSC/RNC/(e)NodeB'. Below the 'MOP-SR-DM' box is a box labeled 'MOP-SC-DM'. Below the 'MOP-SC-DM' box is a box labeled 'S-CORE (MSC/SGSN/MME)'. Below the 'S-CORE (MSC/SGSN/MME)' box is a box labeled 'S-RAN (BTS/BSC/RNC/(e)NodeB)'. At the bottom, there are three labels: 'NEs owned by Participating Operator A (MCC 1, MNC 1)' under the left 'BTS/BSC/RNC/(e)NodeB', 'NEs owned by Master Operator and shared between POs' under the 'S-RAN', and 'NEs owned by Participating Operator B (MCC 1, MNC 2)' under the right 'BTS/BSC/RNC/(e)NodeB'.
+
+Management architecture for GWCN diagram showing POP-NM, MOD-NM, MOP-NM, POP-RAN-DM, MOP-SR-DM, POP-CORE-DM, MOP-SC-DM, S-CORE (MSC/SGSN/MME), MSC/SGSN/HLR/MME/HSS, and BTS/BSC/RNC/(e)NodeB connected via Itf-N interface.
+
+Figure 4.2-2: Management architecture for GWCN
+
+# 5 Business level requirements
+
+## 5.1 Requirements
+
+### 5.1.1 Requirements for the OAM&P of shared RAN
+
+**REQ-NS\_GEN-CON-1** The 3GPP management system of the MOP shall support a capability allowing its authorized consumer to manage S-RAN of any of the following radio access technologies:
+
+- i/ GERAN;
+- ii/ UTRAN;
+
+iii/ E-UTRAN;
+
+iv/ NG-RAN.
+
+**REQ-NS\_GEN-CON-2** The 3GPP management system of the MOP shall support a capability allowing its authorized consumer to manage S-RAN according to any of the following scenarios:
+
+i/ Multi-Operator Core Network
+
+ii/ Gateway Core Network.
+
+**REQ-NS\_GEN-CON-3** The 3GPP management system of the MOP shall support a capability allowing its authorized consumer to know which POPs the shared resources belong to.
+
+**REQ-NS\_GEN-CON-4** The 3GPP management system of the MOP shall support a capability allowing its authorized consumer to configure which POPs share each cell.
+
+**REQ-NS\_GEN-CON-5** Any POP shall be able to activate a signaling-based trace / MDT session on its subscribers, whether they are attached to the POP own RAN or to the S-RAN, provided:
+
+a/ this is compliant with the RAN sharing contract; and
+
+b/ user consent for participation in MDT is respected.
+
+**REQ-NS\_GEN-CON-6** The MOP shall be able, on behalf of any POP, to activate an area-based trace / MDT session, on the portion of the S-RAN that the POP shares and on the POP subscribers only, from the 3GPP management system of MOP, provided
+
+a/ only the POP related subscriber data are collected;
+
+b/ this is compliant with the RAN sharing contract; and
+
+c/ user consent for participation in MDT is respected.
+
+**REQ-NS\_GEN-CON-7** The MOP shall be able, on behalf of multiple POPs, to activate an area-based trace / MDT session, on the portion of the S-RAN that each POP shares and on each POP subscribers only, from the 3GPP management system of MOP, provided:
+
+a/ each POP has access only to its subscriber data (i.e. not to other POPs' subscriber data);
+
+b/ this is compliant with the RAN sharing contract; and
+
+c/ user consent for participation in MDT is respected.
+
+### 5.1.2 Requirements for the OA&M of shared core network elements
+
+**REQ-NS\_GEN-CON-8** In the GWCN scenario, the MOP shall be able to manage **S-CORE**.
+
+**REQ-NS\_GEN-CON-9** The MOP shall be able to know which POPs the shared core network elements belong to.
+
+**REQ-NS\_GEN-CON-10** The MOP shall be able to configure which POPs share each core network element.
+
+### 5.1.3 Requirements for the management of measurements for cross-operator accounting based on data volume and QoS
+
+**REQ-NS\_PM-CON-1** The MOP shall be able to charge the POPs for the data volume used by POP's users per selected QoS profile criteria via measurements defined for shared networks.
+
+- The QoS profile criteria may include QCI Indicator, GBR Indicator, ARP Indicator.
+- It shall be possible to differentiate between DL and UL.
+
+**REQ-NS\_PM-CON-2** The MOP shall be able to set the reliability for the selected measurements defined for cross operator accounting purpose in shared networks.
+
+**REQ-NS\_PM-CON-3** A maximum number of 200 counter instances (for measurements defined for cross operator accounting purpose in shared networks) can be recorded per granularity period.
+
+### 5.1.4 Requirements for management support for NG-RAN MOCN network sharing scenario with same Cell Identity broadcast
+
+**Req-MOCN\_SameCellId\_Cfg-CON-1** The 3GPP management system of the MOP shall have the capability to configure NgC and NgU individually for each POP.
+
+**Req- MOCN\_SameCellId\_Cfg-CON-2** The 3GPP management system of the MOP shall have the capability to configure PLMNId individually for each POP.
+
+**Req- MOCN\_SameCellId\_Per-CON-3** The 3GPP management system of the MOP shall have the capability to collect and report some measurements (e.g. active UEs measurements, packet delay measurements) in PLMN granularity for each POP.
+
+**Req-MOCN-SameCellId-Cfg-CON-4** The 3GPP management system of the MOP shall have the capability to support operator-specific configurations.
+
+**Req-MOCN-SameCellId-Cfg-CON-5** The 3GPP management system of the MOP shall have the capability to support operator-specific performance measurement jobs.
+
+### 5.1.5 Requirements for management support for NG-RAN MOCN network sharing scenario with multiple Cell Identity broadcast
+
+**Req-MOCN-MultiCellId-Cfg-CON-1** The 3GPP management system of the MOP shall have the capability to configure NgC and NgU individually for each POP.
+
+**Req-MOCN-MultiCellId-Cfg-CON-2** The 3GPP management system of the MOP shall have the capability to configure PLMN-IdentityInfo (including PLMNId, NR Cell Identity, TAC) individually for each POP.
+
+**Req-MOCN-MultiCellId-Perf-CON-3** The 3GPP management system shall have the capability to collect and report some measurements (e.g. active UEs measurements, packet delay measurements) in PLMN granularity for each POP.
+
+**Req-MOCN-MultiCellId-Cfg-CON-4** The 3GPP management system of the MOP shall have the capability to configure the common F1 interface for all POPs.
+
+**Req-MOCN-MultiCellId-Cfg-CON-5** The 3GPP management system of the MOP shall have the capability to configure the individual F1 interface for each POP.
+
+**Req-MOCN-MultiCellId-Cfg-CON-6** The 3GPP management system of the MOP shall have the capability to configure the individual NR cell relation individually for each POP.
+
+**Req-MOCN-MultiCellId-Cfg-CON-7** The 3GPP management system of the MOP shall have the capability to support operator-specific configurations.
+
+**Req-MOCN-MultiCellId-Cfg-CON-8** The 3GPP management system of the MOP shall have the capability to support operator-specific performance measurement jobs.
+
+### 5.1.6 Requirements for the OAM&P of shared NG-RAN
+
+**REQ-NS\_NG-CON-1** The 3GPP management system of the MOP shall support a capability to manage both the non-shared network elements and shared network elements in a NG-RAN network at the same time.
+
+**REQ-NS\_NG-CON-2** The 3GPP management system of the MOP shall support a capability to configure the NG-RAN network element to start the sharing of one currently non-shared NG-RAN network element or stop the sharing of one currently shared NG-RAN network element.
+
+**REQ-NS\_NG-CON-3** The 3GPP management system of the MOP shall support a capability to configure the POP-specific attributes of the shared NG-RAN individually based on the POPs' requirements.
+
+**REQ-NS\_NG-CON-4** The 3GPP management system of the MOP shall have the capability to configure the radio resources partitioning policies for the POPs based on the agreement between POPs.
+
+**Req-MOCN-MultiCellId-Cfg-CON-5** The 3GPP management system of the MOP shall have the capability to configure the administrative state of the operator specific NR Cell DU.
+
+## 5.2 Actor roles
+
+For GERAN, UTRAN, and E-UTRAN:
+
+MOP-SR-DM: An entity performing an IRP Agent role in MOCN and in GWCN.
+
+MOP-SC-DM: An entity performing an IRP Agent role in GWCN.
+
+MOP-NM: An entity performing the IRP Manager role in MOCN and in GWCN.
+
+For NG-RAN:
+
+MOP-SR-DM: An entity performing the Management Service Producer role for the management of shared NG-RAN in MOCN.
+
+MOP-NM: An entity performing the Management Service Consumer role for the management of shared NG-RAN in MOCN.
+
+## 5.3 Telecommunications resources
+
+For MOCN and GWCN, the managed GERAN, UTRAN, E-UTRAN, NG-RAN network elements are viewed as relevant telecommunications resources in the present document.
+
+For GWCN, MSC, SGSN and MME are viewed as relevant telecommunications resources in the present document.
+
+## 5.4 High-level use cases
+
+### 5.4.1 Fully pooled radio resources between two POPs
+
+In this use case, cells are shared between POP A and POP B. As agreed by MOP and POPs in their RAN sharing agreement:
+
+- Radio resources of the **S-RAN** are fully pooled between POP A and POP B; UEs from POP A and POP B are served in the **S-RAN** in a first come first served mode;
+- MOP is responsible for configuring the **S-RAN** accordingly.
+
+
+
+This diagram illustrates the network architecture for fully pooled radio resources between two Packet Operator Networks (PONs), POP A and POP B. At the top, the Network Manager (NM) of POP A (MCC 1, MNC 1) and the NM of POP B (MCC 1, MNC 2) are shown. Each NM is connected to a stack of three boxes labeled 'POP-NM'. These POP-NM boxes are connected to a central stack of three boxes labeled 'MOP-NM'. A dashed horizontal line labeled 'Itf-N' separates the management plane (MOP-NM) from the data plane. Below the Itf-N line is a box labeled 'MOP-SR-DM'. This box is connected to two radio nodes, each with three cells labeled 'cell #1', 'cell #2', and 'cell #3'. The cells are represented by icons of antennas with signal waves. The text 'NEs shared between POP A and POP B' is located at the bottom, indicating that the radio resources are shared between the two operators.
+
+Diagram of fully pooled radio resources between two POPs (Figure 5.4.1-1).
+
+Figure 5.4.1-1: Fully pooled radio resources between two POPs
+
+### 5.4.2 Alarm raised on a shared cell (MOCN scenario)
+
+In this use case, an alarm is raised on cell #1 of a shared (e)NodeB. According to the RAN sharing agreement, the two POPs A and B are informed by the MOP of the occurrence of this new alarm, as well as of the alarm clearance by the MOP.
+
+
+
+This diagram shows the sequence of events for handling an alarm on a shared cell in a Multi-Operator Core Network (MOCN) scenario. The sequence is numbered 1 through 8:
+
+
+- Alarm is raised on cell #1 (shared by POP A and POP B) and sent to MOP-SR-DM.
+- Alarm is displayed on MOP-SR-DM GUI.
+- Alarm is handled by Master Operator.
+- Alarm is forwarded to MOP-NM.
+- Alarm is notified to POP A and POP B (for INFO only).
+- Alarm is cleared by MOP at DM level.
+- Alarm clearance is notified to MOP-NM.
+- Alarm clearance is notified to POP A and POP B.
+
+ The diagram uses the same network elements as Figure 5.4.1-1: NM of POP A (MCC 1, MNC 1), NM of POP B (MCC 1, MNC 2), POP-NM boxes, MOP-NM boxes, Itf-N interface, MOP-SR-DM box, and shared cells (cell #1, cell #2, cell #3) between POP A and POP B.
+
+Diagram showing the handling of an alarm raised on a shared cell (MOCN) (Figure 5.4.2-1).
+
+Figure 5.4.2-1. Handling of an alarm raised on a shared cell (MOCN)
+
+### 5.4.3 Single DM for managing S-RAN and POP own RAN
+
+In this use case, Operator A is a POP and manages its own (non-shared) NEs from its POP-RAN-DM while Operator B is both MOP and POP and manages **S-RAN** and its own (non-shared) NEs from a single DM.
+
+Operator B has several possibilities:
+
+Example #1: configure, NE per NE, which POPs share the cells that it manages; or
+
+Example #2: define two separate groups of BTSs / (e)NodeBs:
+
+- one for the **S-RAN** NEs – it shall then configure which POPs share the cells of this group of BTSs / (e)NodeBs; and
+- one for its own (non-shared) RAN NEs.
+
+
+
+Diagram illustrating the Single DM for managing both S-RAN and own RAN. The diagram is split into two main sections by a vertical dashed line labeled 'Itf-N'. The left section, labeled 'Operator A manages its own NEs', shows a stack of three 'POP-NM' boxes connected to a 'POP-RAN-DM' box, which is in turn connected to a 'BTS/BSC/RNC/(e)NodeB' box. The right section, labeled 'Operator B manages the Shared RAN (Sub-network #1) and its own NEs (Sub-network #2) from the same DM', shows a stack of three 'MOP-NM' boxes and a stack of three 'POP-NM' boxes both connected to a 'Single DM' box. The 'Single DM' box is connected to two boxes: 'EM-Shared RAN' and 'EM - POP-RAN'. Below these are two boxes: 'S-RAN (BTS/BSC/RNC/(e)NodeB)' and 'Operator B only BTS/BSC/RNC/(e)NodeB'.
+
+Figure 5.4.3-1: Single DM for managing both S-RAN and own RAN
+
+### 5.4.4 Management of measurements for cross-operator accounting based on data volume and QoS
+
+The operator has made an agreement to act as a Master Operator, MOP, for another operator (Participating Operator, POP) for RAN sharing. The agreement is regulated in an SLA, which states the following: The QoS profile criteria ARP-1 – 10 and GBR-5 for QCI-4 and QCI-8 is supported. The DL QCI-4, GBR-5, and ARP-1 – 10 is charged by x Euro per Mbit, while UL QCI-4, GBR-5, and ARP-1 – 10 is charged by y Euro per Mbit. QCI-8 is charged z Euro per Mbit regardless of QoS. For cross operator accounting purpose, the network needs to provide data volume measurements with high reliability for the used QoS profile criteria to the MOP.
+
+### 5.4.5 Management support for the mixed deployment scenario of shared NG-RAN network elements and non-shared NG-RAN network elements
+
+In this use case, Operator A owns and manages a NG-RAN network. Operator A and Operator B get a NG-RAN sharing agreement that Operator A will share some of the NG-RAN network elements in its NG-RAN network with Operator B. Operator A may need to configure the NG-RAN network to start the sharing of one currently non-shared NG-RAN network element or stop the sharing of one currently shared NG-RAN network element according to the requests from Operator B in the future.
+
+### 5.4.6 Radio resources partitioning between two POPs for the shared NG-RAN
+
+In this use case, radio access network (i.e. one of multiple shared NG-RAN network elements) are shared between two POPs (POP A identified by PLMN A, POP B identified by PLMN B).
+
+As agreed by POP A and POP B in their RAN sharing agreement:
+
+- Radio resources (e.g. PRB, RRC connection, DRB) of the shared radio access network are partitioned for POP A and POP B, which means the radio resource partitioning policies (e.g. RRMPolicyRatio) of the radio access network is agreed for POP A and POP B. The detailed RRMPolicy definition for NG-RAN see the clause 4.3.36 of TS 28.541 [8]. Following is one example of RRMPolicy for corresponding POP A and POP B. In this example,
+ - POP A has 20% dedicated radio resources, 30% prioritized resources and 50% shared resources. In this case, there are 20% radio resources are dedicated for the POP A, 30% radio resources are guaranteed for POP A when it needs to use them, and 50% resources are shared with POP B.
+ - POP B has 30% prioritized resources and 20% shared resources. In this case, there are 30% radio resources are guaranteed for POP B when it needs to use them, and 20% resources are shared with POP A.
+
+
+
+The diagram illustrates the resource partitioning for two Point of Presence (POP) entities, POP A and POP B, sharing a common radio access network. Both bars represent 100% of the available radio resources.
+
+- Structure of RRMPolicyRatio for POP A:** This bar is divided into three segments:
+ - Dedicated resources:** 20% (red segment at the bottom).
+ - Prioritized resources:** 30% (blue segment in the middle).
+ - Shared resources:** 50% (green segment at the top).
+- Structure of RRMPolicyRatio for POP B:** This bar is divided into two segments:
+ - Prioritized resources:** 30% (blue segment at the bottom).
+ - Shared resources:** 20% (green segment above the prioritized resources).
+ - The top 50% of the bar is empty, representing unused capacity or resources available to POP A when not needed by POP B.
+
+Figure 5.4.6-1: Example of structure RRMPolicy for radio access network resource partitioning for POP A and POP B. The diagram shows two vertical bars representing resource allocation. The left bar for POP A shows 100% total resources divided into Shared resources (50%, green), Prioritized resources (30%, blue), and Dedicated resources (20%, red). The right bar for POP B shows 100% total resources divided into Shared resources (20%, green) and Prioritized resources (30%, blue), with the remaining 50% being unused capacity.
+
+**Figure 5.4.6-1 Example of structure RRMPolicy for radio access network resource partitioning for POP A and POP B**
+
+Note: If the network slicing feature is supported, the RRMPolicy is defined for each RRMPolicyMemberList which contains both PLMNId and S-NSSAI. In this case, the RRMPolicy is defined in RRMPolicyMember (combination of PLMNId and S-NSSAI) granularity.
+
+MOP-NM (play the role of MnS consumer) obtains the radio resource partitioning policies the shared radio access network based on above agreement, and sends the radio resource partitioning policies to MOP-SR-DM (play the role of MnS producer) to configure the shared NG-RAN NEs. MOP-SR-DM derives the radio resource partitioning policies for corresponding cells of each shared NG-RAN NE and configures the corresponding shared NG-RAN NE with corresponding radio resource partitioning policies for corresponding cells (see RRMPolicy defined in TS 28.541[8] which is contained by RRMPolicyManagedEntity).
+
+MOP-SR-DM monitors the radio usage resources measurement (e.g. UL/DL PRB used for data traffic, RRC connections) for POP A and POP B, and send such radio usage resources measurements to MnS consumer. Based on the radio resources usage measurements and other information (e.g. service traffic requirements changes) for POP A and POP B, the radio resources partitioning policies may be updated based on the agreement between POP A and POP B. The MOP-NM requests the MOP-SR-DM to reconfigure the updated radio resources partitioning policies of the shared radio access network for corresponding POP A and POP B.
+
+# 6 Specification level requirements
+
+## 6.1 Requirements
+
+**REQ-NS\_GEN-FUN-1** The IRP Agent shall support a capability allowing the IRP Manager to configure which POPs share each cell.
+
+**REQ-NS\_GEN-FUN-2** The IRP Agent shall support a capability allowing the IRP Manager to know which POPs share each cell.
+
+**REQ-NS\_GEN-FUN-3** In GWCN, the IRP Agent shall support a capability allowing the IRP Manager to configure which POPs share each core network element.
+
+**REQ-NS\_GEN-FUN-4** In GWCN, the IRP Agent shall support a capability allowing the IRP Manager to know which POPs share each core network element.
+
+**REQ-NS\_PM-FUN-1** The IRP Agent shall have the capability to support subscription of UL and DL data volume measurements per QoS profile criteria for cross operator accounting purpose from the IRP Manager. The QoS profile criteria may include one or more of the following criteria: one QCI indicator, one GBR Indicator, one ARP Indicator, where:
+
+- a QCI Indicator identifies one specific QCI value. If the indicator is not set then all QCI values should be taken into account.
+- a GBR Indicator identifies one GBR range value defined by the management system. If the indicator is not set then all GBR ranges should be taken into account.
+- an ARP Indicator identifies one ARP priority value. If the indicator is not set then all ARP priority values should be taken into account.
+
+**REQ-NS\_PM-FUN-2** The IRP Agent shall support the IRP Manager setting the reliability for the counter instances in a measurement job. The detailed definition of reliability is vendor specific.
+
+**REQ-NS\_PM-FUN-3** The IRP Agent shall support up to a maximum number of 200 recorded counter instances per granularity period of data volume measurements for cross operator accounting purpose.
+
+**REQ-NS\_PM-FUN-4** The IRP Agent shall support the IRP Manager to access a file containing data volume measurements for cross operator accounting purposes every granularity period.
+
+## 6.2 Actor roles
+
+See clause 5.2.
+
+## 6.3 Telecommunications resources
+
+See clause 5.3.
+
+## 6.4 Use cases
+
+### 6.4.1 Management of measurements for cross-operator accounting based on data volume and QoS
+
+The network manager requests a measurement job for data volume measurements for shared network for charging purposes with high reliability, for a subset of data volume counters per shared PLMN, per UL/DL traffic direction and per QoS profile criteria. The QoS profile criteria may include one or more of the following criteria: one QCI Indicator, one GBR Indicator, one ARP Indicator, where:
+
+- a QCI Indicator identifies one specific QCI value. QCI values range from 0 to 255. If the indicator is not set then all QCI values should be taken into account.
+- a GBR Indicator identifies one GBR range value defined by the management system. GBR range values can range from 1 to N, where N is bigger than 1 (e.g. N=5). If the indicator is not set then all GBR ranges should be taken into account.
+- an ARP Indicator identifies one ARP priority value. ARP priority values range from 1 to 15. If the indicator is not set then all ARP priority values should be taken into account.
+
+An overall maximum number of 200 counter instances (measurement instances) can be recorded per granularity period.
+
+The measurement type is specified by sub-clause 4.1.9 in TS 36.314 [6].
+
+All the counters instances in the measurement job should be subject to high reliability as it is for cross operator accounting purpose. The detailed definition of reliability is vendor specific.
+
+The network provides the counters each granularity period.
+
+# --- 7 Management workflows for requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario
+
+## 7.1 Management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the same cell Identity broadcast
+
+The NG-RAN MOCN Network Sharing with same cell identity broadcast scenario is illustrated in Figure 4.1-2 and corresponding requirements is defined in clause 5.1.4. This clause describes the workflows for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the same cell identity broadcast.
+
+In this workflow, the radio access network (i.e. one or multiple shared NG-RAN NE(s)) is shared between two POPs (POP A identified by PLMN#1 and POP B identified by PLMN#2). Both MnS consumer and MnS producer for the management of shared NG-RAN NE(s) belong to MOP. For the **Req-MOCN\_SameCellId\_Cfg-CON-1**:
+
+MnS consumer determines the individual EP\_NgC MOI and EP\_NgU MOI (see the attributes of NgC and NgU in TS 28.541[X]) for each POP (POP A and POP B), and requests MnS producer to create and configure EP\_NgC MOI and EP\_NgU MOI for each POP.
+
+MnS producer creates and configures the EP\_NgC MOI and EP\_NgU MOI for each POP based on the requests from MnS consumer. The EP\_NgC MOI and EP\_NgU MOI are name contained by same GNBCUCPFunction MOI and GNBCUUPFunction MOI which is shared for different POPs.
+
+For the **Req-MOCN\_SameCellId\_Cfg-CON-2**:
+
+MnS consumer determines the attribute "PLMNInfoList" in NRCellIDU MOI and NRCellCU MOI (see the attribute definition in TS 28.541[X]), which includes the PLMN#1 and PLMN#2, and requests MnS producer to configure NRCellIDU MOI and NRCellCU MOI with attribute "PLMNInfoList".
+
+MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement MOI) based on the requests from MnS consumer, including configuring the NRCellIDU MOI and NRCellCU MOI with attribute "PLMNInfoList" to include PLMN#1 and PLMN#2.
+
+For the **Req-MOCN\_SameCellId\_Per-CON-3**:
+
+MnS producer collects the individual measurements for POP A and POP B in PLMN granularity by utilizing PLMN granularity subcounter. For the concrete PLMN granularity measurements, see TS 28.552[9].
+
+MnS producer sends the individual measurements for POP A and POP B in PLMN granularity to MnS consumer.
+
+## 7.2 Management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the multiple cell Identity broadcast
+
+The NG-RAN MOCN Network Sharing with multiple cell identity broadcast scenario is illustrated in Figure 4.1-3 and corresponding requirements is defined in clause 5.1.5. This clause describes the workflows for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario with the multiple cell identity broadcast.
+
+In this workflow, the radio access network (i.e. one or multiple shared NG-RAN NE(s)) is shared between two POPs (POP A identified by PLMN#1 and POP B identified by PLMN#2). Both MnS consumer and MnS producer for the management of shared NG-RAN NE(s) belong to MOP.
+
+For the **Req-MOCN-MultiCellId-Cfg-CON-1**:
+
+MnS consumer determines the individual EP\_NgC MOI and EP\_NgU MOI (see the attributes of NgC and NgU in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure EP\_NgC MOI and EP\_NgU MOI for each POP.
+
+MnS producer creates and configures the EP\_NgC MOI and EP\_NgU MOI for each POP based on the requests from MnS consumer. The EP\_NgC MOI and EP\_NgU MOI are name contained by corresponding POP's GNBCUCPFunction MOI and GNBCUUPFunction MOI.
+
+For the **Req-MOCN-MultiCellId-Cfg-CON-2**
+
+MnS consumer determines the individual OperatorDU MOI and NROperatorCellDU MOI (see the attributes of OperatorDU and NROperatorCellDU in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure OperatorDU MOI and NROperatorCellDU MOI for each POP.
+
+MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement) based on the requests from MnS consumer, including creates and configures OperatorDU and NROperatorCellDU MOI for each POP.
+
+MnS consumer determines the individual NRCellCU MOI (see the attributes of NRCellCU in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure NRCellCU MOI for each POP.
+
+MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement) based on the requests from MnS consumer, including creates and configures NRCellCU MOI for each POP.
+
+For the **Req-MOCN-MultiCellId-Cfg-CON-3**
+
+MnS producer collects the individual measurements for POP A and POP B in PLMN granularity by utilizing PLMN granularity subcounter or associated with OperatorDU and NROperatorCellDU. For the concrete PLMN granularity measurements, see TS 28.552[9].
+
+MnS producer sends the individual measurements for POP A and POP B in PLMN granularity to MnS consumer.
+
+For the **Req-MOCN-MultiCellId-Cfg-CON-4** and **Req-MOCN-MultiCellId-Cfg-CON-5**
+
+MnS consumer determines the individual EP\_F1C MOI and EP\_F1U MOI (see corresponding attributes in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure these MOIs for each POP. In case of common F1 interface configuration, the values of the EP\_F1C MOI and EP\_F1U MOI attributes (including localAddress and remoteAddress) contained by different POP's OperatorDU MOI of the same GNBDFUFunction MOI should be same.
+
+MnS producer creates and configures the individual EP\_F1C MOI and EP\_F1U MOI for each POP based on the requests from MnS consumer. The EP\_F1C MOI and EP\_F1U MOI are name contained by corresponding POP's OperatorDU and associated to it's own GNBCUCPFunction MOI and GNBCUUPFunction MOI.
+
+For the **Req-MOCN-MultiCellId-Cfg-CON-6**
+
+MnS consumer determines the NRCellRelation MOI(s) (see corresponding attributes in TS 28.541[8]) for each POP (POP A and POP B), and requests MnS producer to create and configure NRCellRelation MOI(s) for each POP.
+
+MnS producer configures the NG-RAN NE(s) (i.e. subtree of ManagedElement) based on the requests from MnS consumer, including creates and configures the individual NRCellRelation MOI for each POP.
+
+
+
+# --- Annex A (informative): Network sharing agreement
+
+Prior to any network sharing deployment, the MOP and the POPs have to agree on legal, financial, technical and operational aspects. Among operational aspects, the network sharing agreement captures the following (non-exhaustive list):
+
+- Organizations involved (i.e. Operators) and their roles in the network sharing deployment.
+- Exhaustive list of shared and unshared resources in the shared network.
+- Rights attached to each role (e.g. rights to configure network resources, rights to receive alarms, etc.).
+- Duties attached to each role (e.g. obligation for the MOP to provide POPs with monthly KPIs, etc.).
+- Delegations (if any) given by any organization to another organization.
+- Service Level Agreements (SLAs).
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|----|-----|--------------------------------|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 2014-12 | SA#66 | SP-140795 | | | Presented for approval | 1.2.0 | 2.0.0 |
+| 2014-12 | | | | | Version after approval | 2.0.0 | 12.0.0 |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | <b>13.0.0</b> |
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------|-------------|--------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | |
+| 2016-12 | SA#74 | SP-160856 | 0001 | 2 | B | Add use cases and requirements for Management of measurements for cross-operator accounting based on data volume and QoS | | 14.0.0 |
+| 2018-01 | SA#78 | SP-170964 | 0002 | - | F | Correcting requirements tags | | 14.1.0 |
+| 2018-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | | 15.0.0 |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | | 16.0.0 |
+| 2021-03 | SA#91e | SP-210141 | 0003 | 1 | B | Update the scope and background of network sharing scenarios | | 17.0.0 |
+| 2021-03 | SA#91e | SP-210141 | 0006 | 1 | B | Update the business requirements to support NG-RAN sharing | | 17.0.0 |
+| 2021-03 | SA#91e | SP-210141 | 0009 | 1 | B | Update business requirements to applicable for SBMA | | 17.0.0 |
+| 2021-06 | SA#92e | SP-210415 | 0011 | - | B | Add requirements for management support for 5G MOCN network sharing scenario with same Cell Identity | | 17.1.0 |
+| 2021-06 | SA#92e | SP-210415 | 0012 | 1 | B | Add requirements for management support for 5G MOCN network sharing scenario with multiple Cell Identity | | 17.1.0 |
+| 2021-06 | SA#92e | SP-210415 | 0013 | 1 | B | Add mixed NG-RAN sharing use case and requirements | | 17.1.0 |
+| 2021-09 | SA#93e | SP-210877 | 0014 | 2 | B | Add NG-RAN sharing individual management use case and requirements | | 17.2.0 |
+| 2021-12 | SA#94e | SP-211471 | 0015 | - | B | Update RAN sharing scenarios to cover 5G RAN sharing | | 17.3.0 |
+| 2021-12 | SA#94e | SP-211471 | 0016 | - | B | Update RAN sharing scenarios to cover 5G RAN sharing | | 17.3.0 |
+| 2022-03 | SA#95e | SP-220184 | 0017 | - | F | Clean up on concept and business level requirements | | 17.4.0 |
+| 2022-03 | SA#95e | SP-220184 | 0018 | - | B | Add missing use case and requirements for radio resources partitioning between POPs | | 17.4.0 |
+| 2022-03 | SA#95e | SP-220184 | 0019 | 1 | B | Solution description for the requirements for the management of the shared NG-RAN NE(s) in MOCN network sharing scenario | | 17.4.0 |
+| 2022-03 | SA#95e | SP-220184 | 0020 | - | B | Add requirement about administrative management capability for operator specific cell | | 17.4.0 |
+| 2022-12 | SA#98e | SP-221168 | 0022 | - | F | delete redundant figure | | 17.5.0 |
+| 2023-03 | SA#99 | SP-230196 | 0023 | - | F | correct the wrong figure number | | 17.6.0 |
+| 2023-09 | SA#101 | SP-230966 | 0024 | 1 | B | Add new requirements for management support for NG-RAN MOCN network sharing scenario | | 18.0.0 |
+| 2023-12 | SA#102 | SP-231494 | 0026 | - | B | Rel-18 CR TS 32.130 Add requirements for NG-RAN MOCN network sharing scenario with multiple Cell Identity broadcast | | 18.1.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32153/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32153/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5eef52bd5febdd311709f2f538ca9c6cea1c447
--- /dev/null
+++ b/marked/Rel-18/32_series/32153/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:446754ca0bb17b4a2a0587f9d84b96c00ae0c9961ee7235e36de0e0226045679
+size 9370
diff --git a/marked/Rel-18/32_series/32153/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32153/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24b4e0f6153bcb31e5768d4c6eba8e831e25cc33
--- /dev/null
+++ b/marked/Rel-18/32_series/32153/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84b1e2e243992fc5e075ea2fbbd2aa1db95c73b5c0e03fb33b66cbcd826b776d
+size 6144
diff --git a/marked/Rel-18/32_series/32153/raw.md b/marked/Rel-18/32_series/32153/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb20366df8219f3568d4fab7705cc08c5d755afa
--- /dev/null
+++ b/marked/Rel-18/32_series/32153/raw.md
@@ -0,0 +1,1284 @@
+
+
+# 3GPP TS 32.153 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+UMTS, management
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-----------------------------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Interface IRP SS template..... | 8 |
+| 5 NRM IRP SS template ..... | 14 |
+| <b>Annex A (normative): General rules for Solution Sets (SS) .....</b> | <b>16</b> |
+| A.1 Introduction..... | 16 |
+| A.2 Solution Set (SS) versioning..... | 16 |
+| A.3 Referenced Information Service (IS) specification..... | 16 |
+| <b>Annex B (normative): Technology specific rules & guidelines for CORBA Solution Sets.....</b> | <b>17</b> |
+| B.1 Rules..... | 17 |
+| B.1.1 Introduction ..... | 17 |
+| B.1.2 Rules for specification of CORBA Solution Sets ..... | 17 |
+| B.1.2.1 Introduction ..... | 17 |
+| B.1.2.2 Pragma prefix ..... | 17 |
+| B.1.3 Implementation aspects of Interface IRP CORBA Solution Sets ..... | 17 |
+| B.1.3.1 Introduction ..... | 17 |
+| B.1.3.2 IRP Agent behaviour on incoming optional method ..... | 18 |
+| B.1.3.3 IRP Agent behaviour on incoming optional parameter of operation ..... | 18 |
+| B.1.3.4 IRP Agent behaviour on outgoing attributes of notification ..... | 18 |
+| B.1.3.5 Encoding rule of absence semantics..... | 18 |
+| B.1.4 Rules for NRM IRP CORBA SS extensions..... | 19 |
+| B.1.4.1 Allowed extensions..... | 19 |
+| B.1.4.2 Extensions not allowed..... | 19 |
+| B.2 Guidelines (Style Guide for CORBA SS IDL) ..... | 20 |
+| B.2.1 Modules and File..... | 20 |
+| B.2.1.1 Use of Modules..... | 20 |
+| B.2.1.2 File Names ..... | 20 |
+| B.2.1.3 Include Conventions ..... | 20 |
+| B.2.1.4 File Structure ..... | 21 |
+| B.2.1.4.1 File Internal Identification ..... | 21 |
+| B.2.1.4.2 File Guard ..... | 21 |
+| B.2.1.4.3 Required Contents..... | 21 |
+| B.2.1.4.4 Example illustrating a File Structure ..... | 21 |
+| B.2.2 Identifiers ..... | 22 |
+| B.2.2.1 Mixed Case, Beginning Upper, No Underscores ..... | 22 |
+| B.2.2.2 Lower Case with Underscores..... | 22 |
+| B.2.2.3 Upper Case with Underscores ..... | 23 |
+| B.2.2.4 Naming IDL Sequence Types ..... | 23 |
+| B.2.3 Interface IRP ..... | 24 |
+| B.2.3.1 Constant String and Type Definitions ..... | 24 |
+| B.2.3.2 Operations..... | 25 |
+| B.2.3.3 Notifications ..... | 25 |
+| B.2.4 NRM IRP..... | 27 |
+
+| | | |
+|-------------------------------|--------------------------------------------------------------------------------|-----------|
+| <b>Annex C (normative):</b> | <b>Technology specific rules & guidelines for SOAP SSs.....</b> | <b>28</b> |
+| C.1 | Rules..... | 28 |
+| C.1.1 | Introduction ..... | 28 |
+| C.1.2 | Rules for specification of SOAP Solution Sets ..... | 28 |
+| C.1.2.1 | Introduction ..... | 28 |
+| C.1.2.2 | File names..... | 28 |
+| C.1.2.3 | Void ..... | 28 |
+| C.1.2.4 | XML version encoding..... | 28 |
+| C.1.2.5 | Namespaces ..... | 29 |
+| C.1.3 | Implementation aspects of Interface IRP SOAP Solution Sets ..... | 29 |
+| C.1.3.1 | Introduction ..... | 29 |
+| C.1.3.n | XXXX rule ..... | 29 |
+| C.2 | Guidelines (Style Guide for SOAP SS WSDL) ..... | 29 |
+| C.2.1 | File structure..... | 29 |
+| C.2.1.1 | Definitions ..... | 29 |
+| C.2.1.2 | Namespaces ..... | 30 |
+| C.2.1.3 | Documentation ..... | 30 |
+| C.2.1.4 | Types ..... | 30 |
+| C.2.1.5 | Message ..... | 30 |
+| C.2.1.6 | Port type..... | 30 |
+| C.2.1.7 | Binding ..... | 30 |
+| C.2.1.8 | Port ..... | 30 |
+| C.2.1.9 | Service ..... | 30 |
+| C.2.2 | Identifiers ..... | 30 |
+| C.2.2.n | <i>Rule n</i> ..... | 30 |
+| C.3 | XML Schema Guidelines..... | 30 |
+| C.3.1 | XSD guidelines for messages definition ..... | 30 |
+| C.3.1.1 | Request message..... | 30 |
+| C.3.1.2 | Response messages..... | 30 |
+| C.3.1.3 | Fault messages..... | 31 |
+| C.3.2 | XSD guidelines for parameters definition..... | 31 |
+| C.3.1.1 | General guidelines ..... | 31 |
+| C.3.1.1 | Simple type definitions ..... | 31 |
+| C.3.1.2 | Complex type definition ..... | 31 |
+| C.3.3 | Identifiers ..... | 31 |
+| <b>Annex D (normative):</b> | <b>Technology specific rules & guidelines for XML specifications .....</b> | <b>32</b> |
+| D.1 | Rules..... | 32 |
+| D.1.1 | XSD Use Cases ..... | 32 |
+| D.1.1.1 | Background..... | 32 |
+| D.1.1.2 | Use Cases Set 1 ..... | 32 |
+| D.1.1.3 | Use Cases Set 2 ..... | 33 |
+| D.1.2 | Rules for NRM IRP XML specification extensions..... | 33 |
+| D.1.3 | XML version encoding..... | 33 |
+| D.2 | Guidelines ..... | 34 |
+| <b>Annex E (informative):</b> | <b>Change history.....</b> | <b>35</b> |
+
+# --- 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- TS 32.150: "Integration Reference Point (IRP) Concept and definitions".
+- TS 32.153: "Integration Reference Point (IRP) technology specific templates, rules and guidelines"**
+- TS 32.154: "Backward and Forward Compatibility (BFC); Concept and definitions".
+- TS 32.155: "Requirements template".
+- TS 32.156: "Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire";
+- TS 32.157: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template".
+
+## --- 1 Scope
+
+The present document contains the templates to be used for the production of Integration Reference Point (IRP) technology-specific specifications.
+
+## --- 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [4] Void
+- [5] Void
+- [6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [7] Void
+- [8] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>).
+- [9] OMG IDL Style Guide, ab/98-06-03, June 17, 1998.
+- [10] W3C WSDL 1.1 specification (<http://www.w3.org/TR/wsdl>)
+- [11] Void.
+- [12] Void.
+- [13] Void.
+- [14] Void.
+- [15] Void.
+- [16] IETF RFC 3629 (<http://tools.ietf.org/html/rfc3629#ref-UNICODE>).
+- [17] 3GPP TS 28.652: "Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
+
+## 3 Definitions and abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+**IRP Agent:** See 3GPP TS 32.150 [3].
+
+**IRP Manager:** See 3GPP TS 32.150 [3].
+
+**SOAP:** See [8].
+
+### 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [3] and the following apply:
+
+| | |
+|-------|-------------------------------------------------|
+| CM | Conditional Mandatory |
+| CM | Configuration Management |
+| CO | Conditional Optional |
+| CORBA | Common Object Request Broker Architecture (OMG) |
+| FF | File Format |
+| IDL | Interface Definition Language |
+| IOC | Information Object Class |
+| IOC | Information Object Class |
+| IRP | Integration Reference Point |
+| IS | Information Service |
+| M | Mandatory |
+| MO | Managed Object |
+| MOC | Managed Object Class |
+| NRM | Network Resource Model |
+| O | Optional |
+| OMG | Object Management Group |
+| TS | Technical Specification |
+| SOAP | W3C acronym |
+| SS | Solution Set |
+| SuM | Subscription Management |
+| UML | Unified Modelling Language (OMG) |
+| URI | Uniform Resource Identifier |
+| WSDL | Web Service Description Language |
+| XML | eXtensible Markup Language |
+| XSD | XML Schema Definition |
+
+# 4 Interface IRP SS template
+
+This clause contains the Interface IRP SS template.
+
+The clauses in this template (that shall be used in the SS specifications) are numbered starting with "X", which in general should correspond to clause 4 that is the beginning of the normative part of a TS. However, if there is a need in a specific SS to introduce additional clauses in the TS body, X may correspond to a number higher than 4.
+
+The SS templates use qualifiers M, O, CM and CO. The semantics of these qualifiers are defined in TS 32.150 [3].
+
+The introductory clauses (from clause 1 to clause 3) for the SS should be modelled similarly to that of clause 1 to 3 of this specification.
+
+Instructions are written in *italics*.
+
+Usage of fonts shall be according to the following table.
+
+**Table: Usage of fonts**
+
+| Item | Font |
+|--------------------|-------------|
+| Class names | Courier New |
+| Attribute names | Courier New |
+| Operation names | Courier New |
+| Parameter names | Courier New |
+| Assertion names | Courier New |
+| Notification names | Courier New |
+| Exception names | Courier New |
+| State names | Arial |
+| Enumerated values | Arial |
+
+## X Architectural Features
+
+"X" represents a clause number in the actual SS. It contains at least the following this subclause:
+
+### X.1 General
+
+This subclause contains the following paragraph:
+
+"The overall architectural feature of <subject IRP> is specified in 3GPP TS <relevant specification number> [<relevant reference>]. This clause specifies features that are specific to the <specific technology> SS."
+
+Example:
+
+"The overall architectural feature of Alarm IRP is specified in 3GPP TS 32.111-2 [6]. This clause specifies features that are specific to the CORBA SS."
+
+*Specific for SOAP SS: the supported XSD, WSDL and SOAP versions shall be indicated together with the style and encoding style, and the namespaces with corresponding prefixes used in the WSDL specifications. Therefore the SOAP SS also contains the information quoted below:*
+
+"The SOAP <supported version> specification [relevant reference], XSD <supported version> specification [relevant reference] and WSDL <supported version> specification [relevant reference] are supported.
+
+This specification uses "<RPC/Document>" style in WSDL file.
+
+This specification uses "<Literal/Encoded>" encoding style in WSDL file.
+
+This specification uses a number of namespace prefixes which are listed in Table X.1.
+
+| Prefix | Namespace |
+|-----------------------|---------------------------------------------------------------------------------------------------|
+| http | <a href="http://schemas.xmlsoap.org/wsdl/http/">http://schemas.xmlsoap.org/wsdl/http/</a> |
+| soap | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a> |
+| xs or xsd | <a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a> |
+| xsi | <a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a> |
+| <IRP specific prefix> | <Namespace's URI> |
+
+**Table X.1: Prefixes and Namespaces used in this specification**
+
+#### »X.a <Feature [a-1]>
+
+<Description of architectural feature "a">
+
+"a" represents a number, starting at 2 and increasing by 1 with each new feature.
+
+*NOTE: This subclause is optional.*
+
+## Y Mapping
+
+"Y" represents a clause number, immediately following "X".
+
+### Y.1 Operation and Notification mapping
+
+*It contains this leading paragraph:*
+
+"The <subject IRP>: IS (see 3GPP TS <relevant specification number> [<relevant reference number>]) defines semantics of operation and notification visible across the Itf-N. Table Y.1.1 indicates mapping of these operations and notifications to their equivalents defined in this SS."
+
+*Example:*
+
+"Alarm IRP: IS 3GPP TS 32.111-2 [6] defines semantics of operation and notification visible across the Itf-N. Table Y.1.1 indicates mapping of these operations and notifications to their equivalents defined in this SS."
+
+*The table includes all operations and notifications, including those inherited. The table lists the operations first and then the notifications. The list order is the same as the one used in the IS. Semantics for the Qualifier is defined in Ref [x].*
+
+**Table Y.1.1: Mapping from IS Operation/Notification to SS equivalents**
+
+| IS Operation/Notification<br>in 3GPP TS <relevant TS number> [<relevant reference number>] | SS Method | Qualifier |
+|--------------------------------------------------------------------------------------------|-----------|----------------|
+| <operation1> | <method1> | M, O, CM or CO |
+| <operation2> | <method2> | M, O, CM or CO |
+| ... | | |
+| .. | | |
+| notify<notification1> | <notify1> | M, O, CM or CO |
+| ... | ... | |
+
+### Y.2 Operation parameter mapping
+
+*It contains this leading paragraph:*
+
+"Reference 3GPP TS <relevant version> [<relevant reference number>] defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS."
+
+*Example:*
+
+"Reference 3GPP TS 32.111-2 [6] defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS."
+
+**Table Y.2.1: Mapping from IS <operation1> parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|--------------------------------|----------------|
+| <parameter-1> | <type definition> <parameter1> | M, O, CM or CO |
+| <parameter-2> | <type definition> <parameter2> | M, O, CM or CO |
+| ... | ... | ... |
+| ... | ... | ... |
+| status | ... | M |
+
+**Table Y.2.2: Mapping from IS <operation2> parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|--------------------------------|----------------|
+| <parameter-1> | <type definition> <parameter1> | M, O, CM or CO |
+| ... | ... | ... |
+| status | ... | M |
+
+**Table Y.2.x:**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|---------------------|-----------|
+| ... | ... | ... |
+| ... | ... | ... |
+| status | ... | M |
+
+### Y.3 Notification parameter mapping
+
+*It contains this leading paragraph:*
+
+"Reference 3GPP TS <relevant version number> [<relevant referenced number>] defines semantics of parameters carried in notifications. The following tables indicate the mapping of these parameters to their SS equivalents."
+
+*Specific for CORBA SS: CORBA SS uses OMG CORBA Structured Event to carry IS-defined notification parameters. The Structured Event has the OMG defined parameters. These parameters will be related to the SS equivalents. So, the SS contains this paragraph.*
+
+"
+
+The following tables indicate the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification Service [<relevant reference number>]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [<relevant reference number>], is:
+
+#### Header
+
+- Fixed Header
+ - domain\_name
+ - type\_name
+ - event\_name
+- Variable Header
+
+#### Body
+
+- filterable\_body\_fields
+- remaining\_body
+
+The following tables list all OMG Structured Event attributes in the second column. The first column identifies the <subject> IRP: IS [<relevant reference number>] defined notification parameters.
+
+"
+
+**Table Y.3.1: Mapping for notifyKkk**
+
+| IS Parameters | <SS> Parameters | Qualifier | Comment |
+|---------------|-----------------|-----------|---------|
+| <parameter-1> | <parameter-A> | M or O | ... |
+| <parameter-2> | <parameter-B> | M or O | ... |
+| ... | ... | M or O | ... |
+
+## Z Notification Interface
+
+"Z" represents a number, immediately following "Y".
+
+This sub-clause captures SS technology specific details required to realize the IS-defined <interface> for notifications.
+
+Specific for CORBA SS:
+
+The SS contains this:
+
+"
+
+OMG CORBA Notification push operation is used to realise the notification of AlarmIRPNotifications. All the notifications in this interface are implemented using this `push_structured_event` method.
+
+### Z.1 Method push (M)
+
+```
+module CosNotifyComm {
+...
+Interface SequencePushConsumer : NotifyPublish {
+ void push_structured_events(
+ in CosNotification::EventBatch notifications)
+ raises( CosEventComm::Disconnected );
+ ...
+}; // SequencePushConsumer
+...
+}; // CosNotifyComm
+```
+
+NOTE 1: The `push_structured_events` method takes an input parameter of type `EventBatch` as defined in the OMG `CosNotification` module (OMG Notification Service [1]). This data type is the same as a sequence of Structured Events. Upon invocation, this parameter will contain a sequence of Structured Events being delivered to IRPManager by IRPAgent to which it is connected.
+
+NOTE 2: The maximum number of events that will be transmitted within a single invocation of this operation is controlled by IRPAgent wide configuration parameter.
+
+NOTE 3: The amount of time the supplier (IRPAgent) of a sequence of Structured Events will accumulate individual events into the sequence before invoking this operation is controlled by IRPAgent wide configuration parameter as well.
+
+NOTE 4: IRPAgent may push `EventBatch` with only one Structured Event.
+
+"
+
+# --- 5 NRM IRP SS template
+
+This clause contains the NRM IRP SS template.
+
+The clauses in this template (that shall be used in the SS specifications) are numbered starting with "X", which in general should correspond to clause 4 that is the beginning of the normative part of a TS. However, if there is a need in a specific SS to introduce additional clauses in the TS body, X may correspond to a number higher than 4.
+
+The introductory clauses (from clause 1 to clause 3) for the SS should be modelled similarly to that of this specification.
+
+Usage of fonts shall be according to the following table.
+
+**Table: Usage of fonts**
+
+| Item | Font |
+|--------------------|-------------|
+| Class names | Courier New |
+| Attribute names | Courier New |
+| Assertion names | Courier New |
+| Notification names | Courier New |
+| State names | Arial |
+| Enumerated values | Arial |
+
+---
+
+## X Architectural Features
+
+*"X" represents a clause number in the actual SS. It contains at least the following subclause:*
+
+### X.1 General
+
+*This subclause contains the following paragraph:*
+
+"The overall architectural feature of <subject IRP> is specified in 3GPP TS <relevant specification number> [<relevant reference>]. This clause specifies features that are specific to the <specific technology> SS."
+
+*Example:*
+
+"The overall architectural feature of UTRAN Network Resources IRP is specified in 3GPP TS 28.652 [17]. This clause specifies features that are specific to the CORBA SS."
+
+### X.a <Feature [a-1]>
+
+*<Description of architectural feature "a">*
+
+*"a" represents a number, starting at 2 and increasing by 1 with each new feature.*
+
+*NOTE: This subclause is optional.*
+
+## Y Mapping
+
+"Y" represents a number, immediately following "X".
+
+### Y.1 General
+
+*This subclause contains a general introduction to the mapping.*
+
+*For CORBA SSs, it contains the following paragraph:*
+
+"Attributes modelling associations as defined in the NRM (here also called "reference attributes") are in this SS mapped to attributes. The names of the reference attributes in the NRM are mapped to the corresponding attribute names in the MOC. When the cardinality for an association is 0..1 or 1..1 the datatype for the reference attribute is defined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the cardinality for an association allows more than one referred MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references."
+
+*For XML FF specifications, it contains the following paragraph:*
+
+"An IOC maps to an XML element of the same name as the IOC's name in the IS. An IOC attribute maps to a sub-element of the corresponding IOC's XML element, and the name of this sub-element is the same as the attribute's name in the IS."
+
+### Y.2 Information Object Class (IOC) mapping
+
+*This subclause is only applicable to NRM IRP CORBA Solution Sets. This clause contains the mapping tables of all iS-defined IOCs to corresponding SS-level MOCs, excluding those inherited.*
+
+#### Y.2.a IOC <IOC name >
+
+*It contains one table with Mapping from NRM IS IOC attribute name to the SS equivalent MOC attribute name and attribute types.*
+
+*"a" in the subclause heading represents a number, starting at 1 and increasing by 1 for each IOC.*
+
+| Attribute of IOC <IOC name > in<br>3GPP TS <relevant TS number> [<relevant<br>reference number>] | SS<br>Attribute | SS<br>Type | Support<br>Qualifier | Read<br>Qualifier | Write<br>Qualifier |
+|--------------------------------------------------------------------------------------------------|-----------------|------------|----------------------|-------------------|--------------------|
+| attribute-a | attribute-1 | <type> | ... | ... | ... |
+| attribute-b | attribute-2 | <type> | ... | ... | ... |
+| ... | ... | ... | ... | ... | ... |
+
+### Y.2 Information Object Class (IOC) mapping
+
+*This subclause is only applicable to NRM IRP XML FF specifications. This subclause describes the mapping of all IS-defined IOCs to corresponding XML definitions, excluding the inherited IOCs.*
+
+*Note: This subclause is also numbered Y.2, directly following Y.1, since every NRM SS-level TS is made for only one SS technology.*
+
+# --- Annex A (normative): General rules for Solution Sets (SS)
+
+## A.1 Introduction
+
+The intent of this annex is twofold.
+
+The first intent is for 3GPP-internal use to document how a 3GPP Solution Set is (SS) produced and what it shall contain.
+
+The second intent is to give the reader of an Information Service (IS) or a Solution Set (SS) a better understanding on how to interpret the IS or SS specifications.
+
+## --- A.2 Solution Set (SS) versioning
+
+*Editor's note: For Further Study.*
+
+## --- A.3 Referenced Information Service (IS) specification
+
+A sentence shall be included in the clause "Scope" of all SS specifications. The sentence shall read as follows:
+
+"This Solution Set specification is related to Z".
+
+where Z is the 3GPP Information Service (IS) specification number including the version, such as "TS 32.111-2 V4.1.X" for the case of Alarm Integration Reference Point (IRP): Information Service (IS).
+
+NOTE: that "X", rather than the actual digit, is actually used in the sentence. This is because the value of X is not relevant for the reference purpose since different values of X identify different 3GPP published specifications that reflect only editorial changes.
+
+# --- Annex B (normative): Technology specific rules & guidelines for CORBA Solution Sets
+
+## B.1 Rules
+
+### B.1.1 Introduction
+
+The intent of this annex is threefold.
+
+- 1) The first intent is for 3GPP internal use to document how a 3GPP CORBA SS is produced and how it is structured.
+- 2) The second intent with the annex is to give the reader or implementer of a CORBA SS a better understanding on how to interpret the CORBA SS specification.
+- 3) The third and maybe most important intent is to put requirement on an implementer of a CORBA SS.
+
+It is expected that this annex is to be extended in later versions of the present document.
+
+### B.1.2 Rules for specification of CORBA Solution Sets
+
+#### B.1.2.1 Introduction
+
+This subclause identifies rules for specification of CORBA SSs. This subclause is mainly for 3GPP-internal use. It is only for information for the implementer of a CORBA SS.
+
+#### B.1.2.2 Pragma prefix
+
+All IDL-code shall define the pragma prefix using the following statement:
+
+```
+#pragma prefix "3gppsa5.org"
+```
+
+See clause B.2.1.4.3 for information of this `#pragma` statement in relation to other IDL statements.
+
+### B.1.3 Implementation aspects of Interface IRP CORBA Solution Sets
+
+#### B.1.3.1 Introduction
+
+This subclause identifies rules for the implementation of CORBA SSs. This subclause is normative for the implementer of a CORBA SS.
+
+#### B.1.3.2 IRP Agent behaviour on incoming optional method
+
+The IRP Agent, claiming compliance to a particular SS version of a particular IRP such as the Alarm IRP, shall implement all Mandatory and all Optional methods. Each method implementation shall have a signature specifying all Mandatory and all Optional parameters.
+
+- If the IRP Agent does not support a particular optional method, it shall throw the `OperationNotSupportedException` when the IRP Manager invokes that method.
+- If the IRP Agent have not implemented a particular method (because it is compiled with an IDL version that does not define the method), the CORBA ORB of the IRP Agent shall throw a system exception if the IRP Manager invokes that method.
+
+In all the above cases when an exception is thrown, the IRP Agent shall restore its state before the method invocation.
+
+#### B.1.3.3 IRP Agent behaviour on incoming optional parameter of operation
+
+An IRP Agent must implement all optional parameters, as well as mandatory parameters, in all methods.
+
+If the IRP Agent supports the implemented method but does not support its (one or more) optional input parameters, upon method invocation, the IRP Agent shall check if those parameters carry "no information" or absence semantics (defined later in subclause B.1.3.5). If the check is negative, the IRP Agent shall throw the `ParameterNotSupportedException` exception with a string carrying the name of the unsupported optional parameter.
+
+#### B.1.3.4 IRP Agent behaviour on outgoing attributes of notification
+
+CORBA SS uses OMG defined structured event to carry notification. The structured event is partitioned into header and body.
+
+The absence semantics of attribute in the header is realized by a string of zero length.
+
+The body consists of one or more name-value pair attributes. The absence semantics of these attributes is realized by their absence.
+
+For optional sub-attributes of an attribute carried by the name-value pair, their absence semantics is realized by the encoding rule of "absence semantics". See subclause B.1.3.5.
+
+#### B.1.3.5 Encoding rule of absence semantics
+
+The operation parameters are mapped to method parameters of CORBA SS. The absence semantics for an operation (input and output) parameter is method parameter type dependent.
+
+- For a string type, if the parameter is specified as a string type, the absence semantics is a string of zero length. If the parameter is specified as a union structure (preferred), the absence semantics is conveyed via a `FALSE` Boolean value switch.
+- For an integer type, if the parameter is specified as a signed, unsigned, long, etc type, the absence semantics is the highest possible positive number. If the parameter is specified as a union structure (preferred), the absence semantics is conveyed via a `FALSE` Boolean value switch.
+- For a boxed `valueType` (supported by CORBA 2.3), it is the null value.
+
+The notification parameters are mapped to attributes of the CORBA Structured Events. The absence semantics for a notification parameter is attribute position (within the Structured Event) dependent.
+
+- For the fixed header of the Structured Event header, the absence semantics is realized by a string of zero length.
+- For the filterable body fields of the Structured Event body, the absence semantics is realized by the absence of the corresponding attribute.
+
+### B.1.4 Rules for NRM IRP CORBA SS extensions
+
+This clause discusses how the models and IDL definitions provided in a particular NRM IRP CORBA SS can be extended for a particular implementation and still remain compliant with IRP specifications.
+
+Note: Protocol-neutral rules for NRM IRP IS-level extensions are defined in TS 32.150 [3] Annex G.
+
+#### B.1.4.1 Allowed extensions
+
+Vendor-specific MOCs may be supported. The vendor-specific MOCs may support new types of attributes. The standardised notifications may be issued referring to the vendor-specific MOCs and vendor-specific attributes. New MOCs shall be distinguishable from standardised MOCs by name. Standardised and vendor-specific attributes may be used in vendor-specific MOCs. Vendor-specific attribute names shall be distinguishable from existing attribute names.
+
+MOCs may be subclassed. Subclassed MOCs shall maintain the specified behaviour of the superior classes. They may add vendor-specific behaviour with vendor-specific attributes. When subclassing, naming attributes cannot be changed. The subclassed MOC shall support all attributes of its superior class. Vendor-specific attributes cannot be added to MOCs without subclassing.
+
+When subclassing, the standardised containment rules and their specified cardinality shall still be followed. As an example, ManagementNode (or its subclasses) shall be contained under SubNetwork (or its subclasses).
+
+Managed Object Instances may be instantiated as CORBA objects. This requires that the MOCs be represented in IDL. MOCs are not currently specified in IDL, but may be specified in IDL for instantiation or subclassing purposes. However, management information models should not require that IRPManagers access the instantiated managed objects other than through supported methods in the present document.
+
+Extension rules related to notifications (Notification categories, Event Types, Extended Event Types etc.) are for further study.
+
+#### B.1.4.2 Extensions not allowed
+
+The IDL specifications in the present document cannot be edited or altered. Any additional IDL specifications shall be specified in separate IDL files.
+
+IDL interfaces (note: not MOCs) specified in the present document may not be subclassed or extended. New interfaces may be defined with vendor-specific methods.
+
+## B.2 Guidelines (Style Guide for CORBA SS IDL)
+
+This subclause describes the style guide for writing IDL statements for Interface IRP and NRM IRP. The guidelines are largely based on the OMG IDL Style Guide (OMG document: ab/98-06-03) [9] with extensions for IRP use.
+
+The guide sets out consistent naming, structural conventions and usage of SS interface for the IDL in IRP CORBA SS specifications.
+
+### B.2.1 Modules and File
+
+#### B.2.1.1 Use of Modules
+
+All declarations of IDL shall be contained in modules. No declarations of interfaces and definitions shall appear in the global scope.
+
+Nesting modules is a useful technique when dealing with large namespaces to avoid name clashes and clarify relationships. A module nested within another module shall not have the same name as a top-level module in any other IRP CORBA SS specification.
+
+#### B.2.1.2 File Names
+
+CORBA SS specifications contain IDL statements.
+
+The rule defined below specifies:
+
+- a) How to partition/extract these IDL statements to be placed in a file; and
+- b) How to name the file.
+
+Note that IDL uses "#include "X"" statement where X is a name of a file containing IDL statements.
+
+##### Rule:
+
+In the annex where IDL statements are defined, use a special marker to indicate that a set of IDL statements shall be contained in one file. The name of the file shall be the name of the first IDL module, concatenated with four characters ".idl". Within a CORBA SS, multiple markers (implying multiple files), can be used.
+
+It is not allowed to have an IDL module split into multiple files.
+
+#### B.2.1.3 Include Conventions
+
+All included IDL files shall be specified using the <...> form of #include. For example:
+
+```
+#include <ManagedGenericIRPConstDefs.idl>
+```
+
+#### B.2.1.4 File Structure
+
+##### B.2.1.4.1 File Internal Identification
+
+The first line of the IDL file shall contain "//File:" followed by a single space followed by the name of the file. For example,
+
+```
+//File: ExampleIRPConstDefs.idl
+```
+
+##### B.2.1.4.2 File Guard
+
+An IDL file shall use a *guard* (consisting of three pre-processor lines) to avoid multiple definition errors. An example of a guard for the file called TestManagementIRPConstDefs.idl is:
+
+```
+#ifndef _TestManagementIRPConstDefs_idl_
+#define _TestManagementIRPConstDefs_idl_
+
+...remainder of the IDL
+
+#endif // _TestManagementIRPConstDefs_idl_
+```
+
+##### B.2.1.4.3 Required Contents
+
+If any other files are to be included, the #include statements come after the guard.
+
+After #include lines, if any, and immediately before the module statement, the following line shall appear:
+
+```
+#pragma prefix "3gppsa5.org"
+```
+
+##### B.2.1.4.4 Example illustrating a File Structure
+
+```
+//File: ExampleIRPConstDefs.idl
+#ifndef _EXAMPLE_IRP_CONST_DEFS_IDL_
+#define _EXAMPLE_IRP_CONST_DEFS_IDL_
+
+// This module describes/is part of...
+#include "ExampleIncludeOne.idl"
+#include "ExampleIncludeTwo.idl"
+
+#pragma prefix "3gppsa5.org"
+module ExampleIRPConstDefs {
+
+ // IDL Definitions here
+
+};
+#endif // _EXAMPLE_IRP_CONST_DEFS_IDL_
+```
+
+### B.2.2 Identifiers
+
+#### B.2.2.1 Mixed Case, Beginning Upper, No Underscores
+
+The following categories of identifiers follow the *Mixed Case, Beginning Upper, No Underscores* rules:
+
+- module
+- interface
+- typedef
+- Constructed types (struct, union, enum)
+- exception
+
+The "No underscores" rule is also applicable to all words that begin with an upper case letter with the remaining letters being lower case.
+
+As a further note on naming, it is not necessary to append the value "*Type*" to an identifier. The fact that it is a type is obvious from the consistent application of this naming convention.
+
+Examples:
+
+```
+module PMIRPConstDefs(...);
+interface AttributeNameValue(...);
+```
+
+#### B.2.2.2 Lower Case with Underscores
+
+The following categories of identifiers follow the *Lower Case with Underscores* rules. All letters are lower case and words (if more than one) are separated with underscores.
+
+- Operation name and notification name
+- Attribute name
+- Parameter name
+- Structure member name
+
+Examples:
+
+```
+get_notification_categories(...);
+string comment_text;
+void get_alarm_count (... , out unsigned long critical_count, ..);
+struct Comment { ...; string user_id; string system_id; ..};
+```
+
+#### B.2.2.3 Upper Case with Underscores
+
+The following categories of identifiers follow *Upper Case with Underscores* rules. All letters are in upper case and words have an underscore separating them.
+
+- Enum value
+- Constant
+
+Examples:
+
+```
+enum SubscriptionState {ACTIVE, SUSPENDED, INVALID};
+const string JOB_ID = "JOB_ID";
+```
+
+#### B.2.2.4 Naming IDL Sequence Types
+
+Typically a new type declared as an IDL sequence of another type will have the text "List" appended to the name of the base type. Another convention is to declare such types as unordered sequences or ordered sets for consistency with ASN.1 notation. In this case they should have the "Seq" or "Set" (instead of "List") appended respectively.
+
+Example of an "ordered set":
+
+```
+typedef sequence <SubscriptionId> SubscriptionIdSet;
+```
+
+### B.2.3 Interface IRP
+
+Every Interface IRP should have 3 IDL modules (each specified in a separate IDL file):
+
+```
+module YyyIRPConstDefs {...}; // no change from Rel-5 practice.
+
+module YyyIRPSystem {...}; // no change from Rel-5 practice.
+
+module YyyIRPNotifications {...}; // new compared to Rel-5 practice
+```
+
+The first module defines all necessary IDL constructs, such as constant strings and type definitions, for the methods and notifications. The second module defines the methods. The third module defines the notifications.
+
+#### B.2.3.1 Constant String and Type Definitions
+
+This first module defines all necessary IDL constructs used by the methods (defined in the second module) and notifications (defined in the third module). The name of this module is YyyIRPConstDefs where Xxx is the name of the subject Interface IRP. An example is "PMIRPConstDefs".
+
+Within this module, define data types used in the methods.
+
+Also, define the data types of the attribute values used in the notifications.
+
+CORBA SS authors should always check the generic types defined in "ManagedGenericIRPConstDefs" before creating a new type.
+
+For the attribute names of the structured notifications, define an interface AttributeNameValue that captures the string definitions. Make sure these definitions do not clash with those defined for the notification header, i.e. notification id, event time, system DN, managed object class and managed object instance (see NotificationIRPNotification::Notify).
+
+An example from PMIRPConstDefs:
+
+```
+/**
+ * This block identifies attributes which are included as part of the
+ * PMIRP. These attribute values should not
+ * clash with those defined for the attributes of notification
+ * header (see IDL of Notification IRP).
+ */
+
+interface AttributeNameValue
+{
+ const string JOB_ID = "JOB_ID";
+ const string JOB_STATUS = "JOB_STATUS";
+ const string REASON = "REASON";
+ const string MONITOR_ID = "MONITOR_ID";
+ const string MONITOR_STATUS = "MONITOR_STATUS";
+};
+```
+
+#### B.2.3.2 Operations
+
+The second module defines the methods. The name of the module is `YyyIRPSystem` where `Yyy` is the name of the subject Interface IRP. An example is `AlarmIRPSystem`.
+
+At the beginning of this module, define all required exceptions. Naming conventions for exception are covered in B.2.2.1 above. CORBA SS authors should always check if the generic exceptions defined in the `ManagedGenericIRPSystem` can be reused before declaring new exception types.
+
+Then define one interface called `YyyIRP` encapsulating all methods of the subject `Yyy` Interface IRP. If the subject Interface IRP IS specifies that its `YyyIRP` inherits from `XxxIRP`, then reflect the inheritance relation in the interface definition. The following is an example of `AlarmIRP` that inherits from `ManagedGenericIRP`.
+
+```
+module AlarmIRPSystem
+{
+...
+...
+interface AlarmIRP : ManagedGenericIRPSystem:: ManagedGenericIRP {...};
+...
+};
+```
+
+Naming conventions for operations are covered in B.2.2.2 above.
+
+#### B.2.3.3 Notifications
+
+Use a separate module to define the notifications. The name the module is `YyyIRPNotifications` where `Yyy` is the name of the subject Interface IRP. Examples are `KernelCMIRPNotifications` and `PMIRPNotifications`.
+
+For `NotificationIRPNotifications`, do:
+
+- Define one IDL interface `Notify`. Capture the four constant strings that are the names of the four NV (name value) pairs of `filterable_body_field` of the CORBA structured event. These four CORBA NV pairs are mapped from the five notification header attributes (defined by the Notification IRP IS), i.e. the `objectClass`, `objectInstance`, `notificationId`, `eventTime` and `systemDN`.
+
+For `YyyIRPNotifications` where `Yyy` is not `Notification`, do:
+
+- At the beginning of this module, define the const strings for the notification types that correspond to the set of notifications specified by (and not inherited by and not imported by) the subject Interface IRP.
+- Then define a number of IDL interfaces corresponding to notifications specified in the subject Interface IRP. These interfaces should inherit from `NotificationIRPNotifications::Notify`. Within each interface, the first IDL statement defines the notification type (that is used as the second field of the fixed header of the structured notification). The second and subsequent IDL statements define the attribute names of this notification type, excepting those already defined by `NotificationIRPNotifications::Notify`. The data type of the attribute value, which is defined in `YyyIRPConstDefs`, should be mentioned in the comment block of this IDL statement.
+- Then define a number of IDL interfaces corresponding to notifications imported, if any. These interfaces should inherit from the imported interface. An example is `interface NotifyObjectCreation : KernelCMIRPNotifications::NotifyObjectCreation`. Within this interface, define all necessary IDL constructs, if any, which are not defined in the imported interface. This interface may contain no IDL statement if the IDL constructs defined in the imported interface are sufficient. For each interface imported, insert a comment "The first field of this notification carries the IRPVersion of this CORBA SS."
+- There is no need to re-define interfaces for notifications that are already specified in other Interface IRP, and from which the subject IRP inherits.
+
+The following is an extract from `PMIRPNotifications`.
+
+```
+module PMIRPNotifications
+{
+ const string ET_MEASUREMENT_JOB_STATUS_CHANGED = "notifyMeasurementJobStatusChanged";
+ const string ET_THRESHOLD_MONITOR_STATUS_CHANGED = "notifyThresholdMonitorStatusChanged";
+
+ interface NotifyMeasurementJobStatusChanged: NotificationIRPNotifications::Notify
+ {
+ const string EVENT_TYPE = ET_MEASUREMENT_JOB_STATUS_CHANGED;
+
+ /**
+ * This constant defines the name of the jobId property,
+ * which is transported in the filterable_body fields.
+ * The data type for the value of this property
+ * is PMIRPConstDefs::JobIdType.
+ */
+ const string JOB_ID = PMIRPConstDefs::AttributeNameValue::JOB_ID;
+
+ ...
+ ...
+ };
+
+ interface NotifyXXX : NotificationIRPNotifications::Notify
+ {
+ ...
+ };
+
+ ...
+};
+```
+
+### B.2.4 NRM IRP
+
+Use one module to define the IDL constructs for the managed object classes. The name of this module is XxxNRIRPConstDefs where Xxx is the name of the subject NRM IRP.
+
+An example is UtranNRIRPConstDefs.
+
+Within the module, define a set of IDL interfaces each of which corresponds to a managed object class specified. The interface definition respects the inheritance relation specified.
+
+After the interface definition, the type definition for each attribute defined for the managed object class is defined (including inherited attributes). The type is defined in one of two ways:
+
+- 1) With a typedef of the type that matches the attribute definition in the NRM Information Object Class (IOC) mapping table, or
+- 2) With a CORBA IDL comment if the same attribute name is already defined in managed object classes already defined in this NRM.
+
+An example of managed object class RncFunction, which inherits from GenericNRIRPConstDefs::ManagedFunction, is shown below.
+
+```
+module UtranNRIRPConstDefs
+{
+ ...
+
+ /**
+ * Definitions for MO class RncFunction
+ */
+ interface RncFunction : GenericNRIRPConstDefs::ManagedFunction
+ {
+ const string CLASS = "RncFunction";
+
+ // Attribute Names
+ //
+ const string rncFunctionId = "rncFunctionId";
+
+ const string mcc= "mcc";
+ const string mnc= "mnc";
+ const string rncId= "rncId";
+ };
+
+ typedef string rncFunctionId;
+ typedef long mcc;
+ typedef long mnc;
+ typedef long rncId;
+ // userLabel
+ ...
+};
+```
+
+# --- Annex C (normative): Technology specific rules & guidelines for SOAP SSs
+
+## C.1 Rules
+
+### C.1.1 Introduction
+
+The intent of this annex is threefold.
+
+- 1) The first intent is for 3GPP internal use to document how a 3GPP SOAP SS is produced and how it is structured.
+- 2) The second intent with the annex is to give the reader or implementer of a SOAP SS a better understanding on how to interpret the SOAP SS specification.
+- 3) The third and maybe most important intent is to put requirement on an implementer of a SOAP SS.
+
+It is expected that this annex is to be extended in later versions of the present document.
+
+### C.1.2 Rules for specification of SOAP Solution Sets
+
+#### C.1.2.1 Introduction
+
+This subclause identifies rules for specification of SOAP SSs. This subclause is mainly for 3GPP-internal use. It is only for information for the implementer of a SOAP SS.
+
+#### C.1.2.2 File names
+
+The WSDL files should follow the naming convention:
+
+WSDLTarget.wsdl
+
+with:
+
+WSDLTarget being the text after the character '#' in the target namespace of the definitions
+
+Examples:
+
+If the 3GPP WSDL document contains
+
+<definitions ...
+
+targetNamespace="http://www.3gpp.org/ftp/specs/archive/32\_series/32.666#KernelCMIRPSystem">,
+
+then the WSDL filename shall be `KernelCMIRPSystem.wsdl`.
+
+If the WSDL document contains
+
+<definitions ... targetNamespace="http://www.3gpp.org/ftp/specs/archive/32\_series/32.111-6#AlarmIRPSystem">,
+
+then the WSDL filename shall be `AlarmIRPSystem.wsdl`.
+
+#### C.1.2.3 Void
+
+#### C.1.2.4 XML version encoding
+
+The first line of each wsdl and xsd file shall indicate the XML version and encoding. The supported XML version is defined in the subject TS. The supporting encoding is UTF-8 (refer to [16]).
+
+Therefore, an example for the wsdl and xsd file is :
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+```
+
+#### C.1.2.5 Namespaces
+
+The WSDL namespace URI shall follow the naming convention:
+
+```
+http://www.3gpp.org/ftp/specs/archive/IRP_series/IRPNumber#SchemaName
+```
+
+with:
+
+- IRP\_series is the 3GPP specification series;
+- IRPNumber is the number before the 3GPP document version number, corresponding to the 3GPP document which defines the resource;
+- SchemaName is the name of the WSDL specification or the name of the XML Schema in which the resource is defined.
+
+Examples:
+
+The 3GPP document "3GPP TS 32.111-6 V11.0.0 (2012-09)" defines the resource "AlarmIRPSystem". It defines the WSDL specification "AlarmIRPSystem.wsdl" in which the resource AlarmIRPSystem is defined. Then the namespace URI shall be:
+
+```
+http://www.3gpp.org/ftp/specs/archive/32_series/32.111-6#AlarmIRPSystem
+```
+
+The 3GPP document "3GPP TS 28.623 V11.1.0 (2013-06)" defines the resource "SubNetwork". It defines the XML schema "genericNrm.xsd" in which the resource SubNetwork is defined. Then the namespace URI shall be:
+
+```
+http://www.3gpp.org/ftp/specs/archive/28_series/28.623#genericNrm
+```
+
+```
+http://www.3gpp.org/ftp/specs/archive/32_series/32.127#AAMIRPData
+```
+
+### C.1.3 Implementation aspects of Interface IRP SOAP Solution Sets
+
+#### C.1.3.1 Introduction
+
+This subclause identifies rules for the implementation of SOAP SSs. This subclause is normative for the implementer of a SOAP SS.
+
+#### C.1.3.n XXXX rule
+
+## C.2 Guidelines (Style Guide for SOAP SS WSDL)
+
+This subclause describes the style guide for writing WSDL documents for Interface IRP.
+
+The guide sets out consistent naming, structural conventions and usage of SS interface for the WSDL in IRP SOAP SS specifications.
+
+### C.2.1 File structure
+
+The structure of the wsdl file shall follow the W3C WSDL Document Structure defined in [10] specifications.
+
+#### C.2.1.1 Definitions
+
+*Guidelines for the Definitions section.*
+
+#### C.2.1.2 Namespaces
+
+*Guidelines for the Namespaces section.*
+
+#### C.2.1.3 Documentation
+
+*Guidelines for the optional Documentation section.*
+
+#### C.2.1.4 Types
+
+*Guidelines for Types*
+
+#### C.2.1.5 Message
+
+*Guidelines for Messages*
+
+#### C.2.1.6 Port type
+
+*Guidelines for Port types*
+
+#### C.2.1.7 Binding
+
+*Guidelines for Bindings*
+
+#### C.2.1.8 Port
+
+*Guidelines for Ports*
+
+#### C.2.1.9 Service
+
+*Guidelines for Services*
+
+### C.2.2 Identifiers
+
+#### C.2.2.n Rule n
+
+*Identify the categories of identifiers which follow the Rule n rules.*
+
+## --- C.3 XML Schema Guidelines
+
+This subclause describes the style guide for writing XML Schema for Operation/Notification messages and parameters to be imported into the WSDL file for the IRP SOAP SS specifications.
+
+### C.3.1 XSD guidelines for messages definition
+
+#### C.3.1.1 Request message
+
+*Guidelines for the Request message.*
+
+#### C.3.1.2 Response messages
+
+*Guidelines for the Response messages.*
+
+#### C.3.1.3 Fault messages
+
+*Guidelines for the Fault messages.*
+
+### C.3.2 XSD guidelines for parameters definition
+
+#### C.3.1.1 General guidelines
+
+*General guidelines for the parameters definitions.*
+
+##### C.3.1.1.1 Simple type definitions
+
+*Guidelines for the simple type definitions.*
+
+#### C.3.1.2 Complex type definition
+
+*Guidelines for the complex type.*
+
+### C.3.3 Identifiers
+
+The identifiers should follow the rules defined in paragraph C.2.2.
+
+# Annex D (normative): Technology specific rules & guidelines for XML specifications
+
+## D.1 Rules
+
+### D.1.1 XSD Use Cases
+
+#### D.1.1.1 Background
+
+3GPP defines a number of IOCs, say in Release-N. 3GPP also defines an XSD schema that can capture these IOCs, in Release-N.
+
+Release-N+1 authors can/may also extend these Release-N IOCs to capture the newly agreed capabilities and publish them as Release-N+1 IOCs. Authors also define a Release-N+1 XSD schema.
+
+The Use Cases here illustrate the capabilities of the Release-N+1 XSD schema.
+
+The "?" in the Use Case tables are for further study.
+
+#### D.1.1.2 Use Cases Set 1
+
+Suppose the old-XSD has SubNetwork (SN) containing ManagedElement (ME).
+
+Suppose the new-XSD has enhanced-SN containing enhanced-ME.
+
+Suppose we want the XML-instance-documents (doc-1, doc-2, etc) to contain instances as identified below:
+
+- Doc-1 has SN instance containing ME instances
+- Doc-2 has SN instance containing enhanced-ME instances
+- Doc-3 has SN instance containing ME instances and enhanced-ME instances
+- Doc-4 has enhanced-SN containing enhanced-ME instances
+- Doc-5 has enhanced-SN containing ME instances
+- Doc-6 has enhanced-SN containing enhanced-ME instances and ME instances
+
+Can a XML-instance-doc-creator (IRPAgent or IRPManager) produce the doc (column) using the XSD (row) identified?
+
+| | Doc-1 | Doc-2 | Doc-3 | Doc-4 | Doc-5 | Doc-6 |
+|---------|-------|-------|-------|-------|-------|-------|
+| Old-XSD | ? | ? | ? | ? | ? | ? |
+| New-XSD | ? | ? | ? | ? | ? | ? |
+
+Can a XML-instance-doc-reader (IRPAgent or IRPManager) validate the doc (i.e. confirm that the document is well-formed) (column) using the XSD (row) identified?
+
+| | Doc-1 | Doc-2 | Doc-3 | Doc-4 | Doc-5 | Doc-6 |
+|---------|-------|-------|-------|-------|-------|-------|
+| Old-XSD | ? | ? | ? | ? | ? | ? |
+| New-XSD | ? | ? | ? | ? | ? | ? |
+
+#### D.1.1.3 Use Cases Set 2
+
+Suppose one old-XSD has SubNetwork (SN) containing ManagedElement (ME) that in turn, contained an RNCFunction (RNC) defined by the other Old-XSD.
+
+Suppose the new-XSD has enhanced-SN containing enhanced-ME. Suppose also another new-XSD has enhanced-RNC.
+
+- Doc-7 has ME instance containing RNC instances
+- Doc-8 has ME instances containing enhanced-RNC instances
+- Doc-9 has ME instances containing RNC instances and enhanced-RNC instances
+- Doc-10 has enhanced-ME instances containing enhanced-RNC instances
+- Doc-11 has enhanced-ME instances containing RNC instances
+- Doc-12 has enhanced-ME instances containing RNC instances and enhanced-RNC instances
+
+Can a XML-instance-doc creator (IRPAgent or IRPManager) produce the doc (column) using the XSD (row) identified?
+
+| | Doc-7 | Doc-8 | Doc-9 | Doc-10 | Doc-11 | Doc-12 |
+|---------|-------|-------|-------|--------|--------|--------|
+| Old-XSD | ? | ? | ? | ? | ? | ? |
+| New-XSD | ? | ? | ? | ? | ? | ? |
+
+Can a reader (IRPAgent or IRPManager) validate the doc (i.e. confirm that the document is well-formed) (column) using the XSD (row) identified?
+
+| | Doc-1 | Doc-2 | Doc-3 | Doc-4 | Doc-5 | Doc-6 |
+|---------|-------|-------|-------|-------|-------|-------|
+| Old-XSD | ? | ? | ? | ? | ? | ? |
+| New-XSD | ? | ? | ? | ? | ? | ? |
+
+### D.1.2 Rules for NRM IRP XML specification extensions
+
+Void
+
+### D.1.3 XML version encoding
+
+The first line of each XML schema description file shall indicate the XML version and encoding. The supported XML version is specified in the subject TS. The supported encoding is UTF-8 (refer to [16]).
+
+Therefore, an example for xsd file is:
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+```
+
+## --- D.2 Guidelines
+
+Void
+
+# Annex E (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|---------------------------------------------------------------|-----|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| Mar 2008 | SA_39 | SP-080070 | -- | -- | Submitted to SA#39 for Information | -- | -- | 1.0.0 |
+| Mar 2009 | SA-43 | SP-090057 | -- | -- | Submitted to SA for approval | -- | 2.0.0 | 8.0.0 |
+| Dec 2009 | SA_46 | SP-090719 | 001 | -- | Discontinuation of the maintenance of WSDL/XML schema folders | F | 8.0.0 | 9.0.0 |
+| Jun 2010 | SA_48 | SP-100264 | 002 | -- | New rule for WSDL namespace URIs | F | 9.0.0 | 10.0.0 |
+| Sep 2010 | SA_49 | SP-100489 | 003 | -- | Change rule for WSDL filenames | F | 10.0.0 | 10.1.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | | 10.1.0 | 11.0.0 |
+| 2014-09 | SA-65 | SP-140558 | 004 | - | Name space URI convention | F | 11.0.0 | 11.1.0 |
+| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) | | 11.1.0 | 12.0.0 |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | 13.0.0 |
+| 2016-03 | SA_71 | SP-160032 | 0010 | - | Correcting references | A | 13.0.0 | 13.1.0 |
+| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | | 13.1.0 | 14.0.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|--------------------------------|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-01 | SA#78 | SP-170964 | 0011 | - | F | Update erroneous references | 14.1.0 |
+| 2018-12 | - | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 |
+| 2022-03 | - | - | - | - | - | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32154/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-18/32_series/32154/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b492cd0ce4f3023499d07632661275ffa44f69db
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c90e9cc07e3b60c25d28f4df7b9817241f27c78504fa00f1e69eb687db4ea8c8
+size 67465
diff --git a/marked/Rel-18/32_series/32154/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-18/32_series/32154/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2ceb297ba7a7e200445bdcd8dcf6b89cfe75eb2
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e876a27a990d86cc8f4231b6bd0c3e93cbea03a277b6dbba58588c13c7b78ba
+size 60429
diff --git a/marked/Rel-18/32_series/32154/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32154/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/32_series/32154/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32154/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1134c67760259e845c8960324505f060a9d0eece
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:125561d2e36a3dc18f4be88d0a06d2f7e62e1484de9ef2d52e22787082d633e9
+size 5524
diff --git a/marked/Rel-18/32_series/32154/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/Rel-18/32_series/32154/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4bd7fc4941c8a4f1ca7444dff66df264dc2c7682
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e157a7d8dec99e918cbb4c5b3aaf931da8bca513480fad02fc38679cc8d2c30e
+size 29254
diff --git a/marked/Rel-18/32_series/32154/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-18/32_series/32154/ddc7460821484f1ae2835c67955c554c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ce5db8281e2f23e42e18733077a56c456e1e913
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/ddc7460821484f1ae2835c67955c554c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e59d7c214adbc92c0afc1313edcf29502bb77742817fe2d655f392a1411d198c
+size 63419
diff --git a/marked/Rel-18/32_series/32154/raw.md b/marked/Rel-18/32_series/32154/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..30a9f22ff836c8b71ba2ccd9e9e6871e5b667466
--- /dev/null
+++ b/marked/Rel-18/32_series/32154/raw.md
@@ -0,0 +1,402 @@
+
+
+# 3GPP TS 32.154 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G ADVANCED logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+GSM, UMTS, management
+
+### **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+### --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|-------------------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 BC between 3GPP TS 32-series specifications..... | 6 |
+| 4.1 Prerequisite..... | 6 |
+| 4.2 Rules..... | 7 |
+| 5 BC context..... | 8 |
+| 5.1 General ..... | 8 |
+| 5.2 IRP level..... | 9 |
+| 5.3 IRP Agent level ..... | 10 |
+| 6 BC Recommendations..... | 12 |
+| 6.1 Requirement ..... | 12 |
+| 6.2 IS-level ..... | 12 |
+| 6.3 SS-level ..... | 12 |
+| 6.3.1 CORBA ..... | 12 |
+| 6.3.2 Void ..... | 12 |
+| 6.3.3 File format description XML..... | 12 |
+| 6.3.4 File format description ASN.1 ..... | 12 |
+| 6.3.5 SOAP ..... | 12 |
+| <b>Annex A (informative): BC and Conformance Tests.....</b> | <b>13</b> |
+| <b>Annex B (informative): Change history.....</b> | <b>14</b> |
+
+# --- 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 Itf-N partitions two groups of interacting entities called IRPManager(s) and IRPAgent(s).
+
+The interactions between an IRPManager and IRPAgent are specified by the set of IRP specifications the IRPAgent supports, and which the IRPManager uses.
+
+Each YyyIRP (where "Yyy" stands for Alarm, BasicCM, etc.) permits a manager to, via `getIRPVersion`, inspect it's supported IRPVersion(s). Each such IRPVersion uniquely identifies one supported Interface IRP SS.
+
+Each YyyIRP may also permit an IRPManager to, via `getNRMIRPVersions`, inspect it's supported NRM IRPVersion(s). Each such IRPVersion uniquely identifies one supported NRM IRP SS.
+
+The 3GPP IRP specifications are expected to evolve. For example, 3GPP Release 6 specifications include more or modified features compared to the corresponding set in Release 5.
+
+An IRPManager and IRPAgent, with implementations conformant to the same IRP specification (at the same IRPVersion(s)) will be able to communicate.
+
+However, an upgrade of the IRPVersion, if not performed by both IRPAgent and IRPManager, can result in inter-working failure if Backward Compatibility (BC) issues are not addressed.
+
+The present document is applicable/relevant to a system context of a group of interacting IRPManagers and IRPAgents where some members are using one IRPVersion while others are using an upgraded IRPVersion.
+
+# --- 1 Scope
+
+The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
+
+The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
+
+Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.
+
+**Editor's Note:** The “forward compatibility” part is FFS.
+
+# --- 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 and/or edition number or version number) 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Element Manager (EM):** See 3GPP TS 32.101 [1].
+
+**IRPAgent:** See 3GPP TS 32.102 [2].
+
+**IRPManager:** See 3GPP TS 32.102 [2].
+
+**IRPVersion:** See "IRP document version number string" or "IRPVersion" in 3GPP TS 32.311 [4] clause 3.1.
+
+**Network Manager (NM):** See 3GPP TS 32.101 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|-------------------------------------------------------|
+| ASN.1 | Abstract Syntax Notation One |
+| BC | Backward Compatible or Backward Compatibility |
+| CMIP | Common Management Information Protocol |
+| CORBA | Common Object Request Broker Architecture |
+| EM | Element Manager |
+| IS | Information Service |
+| IRP | Integration Reference Point |
+| NE | Network Element |
+| NM | Network Manager |
+| NRM | Network Resource Model |
+| VSE | Vendor Specific Extension (to 3GPP IRP specification) |
+| SS | Solution Set |
+| XML | eXtensible Markup Language |
+
+# --- 4 BC between 3GPP TS 32-series specifications
+
+## 4.1 Prerequisite
+
+The words old and new, when qualifying an IRPVersion, refer to a single Interface IRPVersion of the same kind, e.g. Alarm IRP. They also refer to NRM IRPVersion of the same kind, e.g. Core NRM. The 'new' refers to a later release compared to the 'old'.
+
+The words old and new, when qualifying an IRPManager, refer to an entity that is using the old or the new (Interface or NRM) IRPVersion.
+
+The words old and new, when qualifying an IRPAgent, refer to an entity that contains an IRP that is supporting the old or the new (Interface or NRM) IRPVersion.
+
+In majority cases, an IRPAgent instance contains multiple IRPs, each of which is using a particular Interface IRPVersion. In these cases, each Recommendation statement should be repeated to cover all IRPs involved.
+
+The Recommendations do not imply that equipment vendors shall always supply their new IRPAgents in compliance to the solutions satisfying the Recommendations. The Recommendations simply identify the expected behaviours of a new system when it, claiming BC, interacts with an old system. Whether or not an IRPAgent should satisfy the Recommendations is a decision of the equipment vendor/supplier.
+
+The Recommendations do not imply that the next release of 3GPP Interface IRP or NRM IRP specification must be BC (to the older one). Whether or not a new release of an Interface IRP or NRM IRP should be BC to its older version is a decision of the 3GPP specification author, on a case-by-case basis.
+
+## 4.2 Rules
+
+[REC-1] An old IRPManager inter-operates with an old IRPAgent-A and a new IRPAgent-B.
+
+The interaction shall be successful in that the IRPManager can obtain the network management services (capabilities and features) defined by the old IRPVersion from both IRPAgents.
+
+The IRPManager needs not have knowledge of new network management services defined by the new IRPVersion.
+
+[REC-2] A new IRPManager inter-operates with a new IRPAgent-A and an old IRPAgent-B.
+
+The interaction shall be successful in that the IRPManager can obtain the network management services defined by (a) the new IRPVersion from IRPAgent-A and (b) the old IRPVersion from IRPAgent-B.
+
+NOTE: If the next minor and/or major release of 3GPP Interface IRP or NRM IRP specification is BC (to the older one), one could reduce or eliminate the difficult coordination task to introduce IRPVersion upgrades in a large management domain containing multiple IRPManagers and IRPAgents.
+It can be more cost-effective if IRPVersion upgrades to individual entity (i.e. IRPManager and IRPAgent) are done at different times.
+
+# 5 BC context
+
+## 5.1 General
+
+This clause defines the context under which the requirements specified in the present document are applicable.
+
+The word 'old' qualifies the related entity (i.e. the AlarmIRP of an IRP Agent instance or Alarm IRP Manager) that is using an older 3GPP IRP Version (called old version). The word 'new' qualifies the related entity that is using a newer (upgraded) 3GPP IRP Version.
+
+EXAMPLE: A hypothetical 3GPP TS 32.123 V6.0.0 is considered the old version with reference to 3GPP TS 32.123 V6.1.0. The two versions in question can belong to the same or different major releases (e.g. Rel-5 or Rel-6).
+
+The box labelled EM in figure 5.1 conveys the same idea as the box of the same label in the System Context-A of other IRP specifications such as Alarm IRP IS 3GPP TS 32.111-2 [3].
+
+One or all EM-labelled boxes of figure 5.1 can be interchanged with the NE-labelled box (see System Context-B of other IRP specifications such as Alarm IRP IS 3GPP TS 32.111-2 [3]). The NE entities are not shown in order to make the figure easier to read.
+
+
+
+Figure 5.1: Overall BC System Context diagram. The diagram shows four boxes representing entities: 'Old IRPManager' (NM), 'New IRPManager' (NM), 'New IRP Agent' (EM), and 'Old IRP Agent' (EM). A vertical dashed line labeled 'Itf-N' runs down the center, separating the Manager entities on the left from the Agent entities on the right. Horizontal lines connect the Old IRPManager to the Old IRP Agent and the New IRPManager to the New IRP Agent. Diagonal lines cross the Itf-N interface, connecting the Old IRPManager to the New IRP Agent and the New IRPManager to the Old IRP Agent.
+
+**Figure 5.1: Overall BC System Context**
+
+In general, an IRP Agent instance may contain several Interface YyyIRP instances and associated supporting Yyy NRM IRPs (where one IRP can be for example Alarm IRP, Test Management IRP, or "Notification IRP", etc and where the other IRP can be for example Generic IRP). The Interface and NRM YyyIRP specifications of particular IRP Version(s) together specify the behaviour of an Interface IRP and the supporting NRM IRP(s).
+
+NOTE: The IRP Version concept is related to the IRP.
+The IRP Version concept is not related to the IRP Agent as this may contain multiple IRPs.
+
+Given this background, the BC issues are addressed at two separate but related levels as described in clauses 5.2 and 5.3.
+
+## 5.2 IRP level
+
+The two diagrams here illustrate conceptually the two possible contexts when we address BC at this IRP level.
+
+
+
+The diagram illustrates two system contexts for BC at the IRP level. Both contexts show a Network Manager (NM) on the left and an Element Manager (EM) on the right, separated by an interface labeled 'Itf-N'.
+
+In the top context, the NM contains two boxes: 'Old IRPManager' and 'New IRPManager'. The 'Old IRPManager' is connected to the 'Itf-N' interface. The 'New IRPManager' is connected to the 'Old IRPManager' and also to the 'Itf-N' interface. The EM contains two boxes: 'YyyIRP IRPVersion-new' and 'IRP Agent'. The 'YyyIRP IRPVersion-new' is connected to the 'Itf-N' interface and to the 'IRP Agent'.
+
+In the bottom context, the NM contains a box labeled 'Old IRPManager', which is connected to the 'Itf-N' interface. The EM contains two boxes: 'YyyIRP IRPVersion-old' and 'IRP Agent'. The 'YyyIRP IRPVersion-old' is connected to the 'Itf-N' interface and to the 'IRP Agent'.
+
+Figure 5.2: Specification BC System Context. The diagram consists of two parts. The top part shows an 'Old IRPManager' and a 'New IRPManager' (both in NM) connected via an 'Itf-N' interface to a 'YyyIRP IRPVersion-new' and an 'IRP Agent' (both in EM). The bottom part shows an 'Old IRPManager' (in NM) connected via an 'Itf-N' interface to a 'YyyIRP IRPVersion-old' and an 'IRP Agent' (both in EM).
+
+**Figure 5.2: Specification BC System Context**
+
+An YyyIRP instance supports a particular Interface IRPVersion and a particular set of NRM IRPVersions.
+An IRPManager uses a particular Interface IRPVersion and a particular set of NRM IRPVersions.
+
+If an YyyIRP instance supports Interface IRPVersion-X and NRM IRPVersions-Y, then it can interact successfully with an IRPManager that uses the same IRPVersions. This is illustrated by the case of the "Old IRPManager" and the "Old IRPAgent" of the bottom diagram (and note that the diagram does not show the NRM IRP version support).
+
+If this same YyyIRP instance upgrades its Interface IRPVersion-X to X2 that is BC to X, then it can interact successfully with an IRPManager that uses the Interface IRPVersion-X or IRPVersion-X2. The top diagram of figure 5.2 illustrates this case (and note that the diagram does not show the NRM IRP version support).
+
+If this same YyyIRP instance upgrades its NRM IRPVersion-Y to Y2 that is BC to Y, then it can interact successfully with an IRPManager that uses the NRM IRPVersion-Y or NRM IRPVersion-Y2. The top diagram of figure 5.2 illustrated this case (and note that the diagram does not show the NRM IRP version support).
+
+Given the above, the BC issues addressed at the present document level are:
+
+- How to determine if an IRP IS or SS specification (Interface IRP or NRM IRP) is BC to an earlier version ? This can be addressed in another way.
+
+What are the BC-rules that the author of a 3GPP IRP specification should use to extend an old-version to produce a new version that can claim BC (to that old-version) ?
+
+At this level, the specification author shall define BC-rules for each of the following:
+
+- Interface IRP- Requirements.
+- Interface IRP IS.
+- Interface IRP SS(s).
+- NRM IRP requirements.
+- NRM IRP IS.
+- NRM IRP SS(s).
+- Data Definition IRP IS.
+- Data Definition IRP SS(s).
+
+One reason why the specification author addresses BC at this IRP level is that, for certain technologies, such as CORBA, it is possible that one entity using (compiles with) one IRP SS specification (i.e. the CORBA SS) while the other communicating entity using a new but BC version can interact successfully (such as the case of the IRPManager and IRPAgent-A of [REC-1]).
+
+## 5.3 IRPAgent level
+
+Figure 5.3 illustrates the two possible contexts when addressing BC at this IRPAgent level.
+
+
+
+The diagram consists of two parts. The top part shows two Network Management (NM) boxes on the left, labeled 'Old IRPManager' and 'New IRPManager'. Both are connected via a common interface 'Itf-N' (indicated by a vertical dashed line) to two separate boxes on the right. These boxes are part of an Environment Management (EM) system and contain 'YyyIRP IRPVersion-old' and 'YyyIRP IRPVersion-new' respectively, each connected to an 'IRPAgent' box. The bottom part shows a single NM box labeled 'Old IRPManager' connected via 'Itf-N' to one EM box containing 'YyyIRP IRPVersion-old' connected to an 'IRPAgent' box.
+
+Two diagrams illustrating system contexts for IRPAgent level BC. The top diagram shows 'Old IRPManager' and 'New IRPManager' (both NM) connected via 'Itf-N' to two 'IRPAgent' boxes (both EM) labeled 'YyyIRP IRPVersion-old' and 'YyyIRP IRPVersion-new'. The bottom diagram shows 'Old IRPManager' (NM) connected via 'Itf-N' to one 'IRPAgent' box (EM) labeled 'YyyIRP IRPVersion-old'.
+
+Figure 5.3: System/Implementation BC System Context
+
+NOTE 1: An IRP Agent instance contains multiple YyyIRP instances such as AlarmIRP, NotificationIRP, TestManagementIRP, etc. Each YyyIRP instance implements/supports the corresponding YyyIRP specification of a particular IRPVersion.
+
+Suppose IRP Agent-A contains YyyIRP of Interface IRPVersion-4, YyyIRP of Interface IRPVersion-5 and YyyIRP of Interface IRPVersion-6 and all IRPs support NRM IRPVersion-7 (see Note 2), this IRP Agent-A is BC if it can inter-operate successfully with the following:
+
+- IRP Manager 1 using Interface IRPVersion-4 or 3 using NRM IRPVersion-7 or 6.
+- IRP Manager 2 using Interface IRPVersion-5 or 4 using NRM IRPVersion-7 or 6.
+- IRP Manager 3 using Interface IRPVersion-6 or 5 using NRM IRPVersion-7 or 6.
+
+NOTE 2: All IRPs contained by the same IRP Agent instance should support the same set of NRM IRP Versions.
+
+It is anticipated that the IRP Agent level BC solution includes:
+
+- An IRP Agent service allowing IRP Manager to discover all the IRP Agent supported Interface IRPVersion(s).
+- An IRP Agent service allowing IRP Manager to discover the IRP Agent supported NRM IRPVersion(s).
+- An IRP Agent service allowing IRP Manager to discover the reference/address of the IRP instance (of the IRP Agent) supporting a particular Interface IRPVersion.
+
+The two diagrams in figure 5.3 illustrate the two possible ways to support BC at this so-called IRP Agent level.
+
+The IRPVersion-new needs not to be BC to IRPVersion-old. In the case that IRPVersion-new is BC to IRPVersion-old, it is EM supplier's choice if "IRP level" or "IRP Agent level" solution will be used to support BC. In the case that the IRPVersion-new is not BC to IRPVersion-old, then the EM supplier will have no choice but to use "IRP Agent level" solution if it wants its EM to support BC.
+
+NOTE 3: IRP Agent service supporting "discovery" (as stated by the above three bullets) is not illustrated in the two diagrams
+
+# --- 6 BC Recommendations
+
+## 6.1 Requirement
+
+The Requirement specification is in subclause 4.2 Rules.
+
+## 6.2 IS-level
+
+There is no text specifically written related to IS-level specification for BC systems. The two system context diagrams of subclauses 5.2 and 5.3 would be necessary and sufficient to describe the management services provided by EM to support the so-called Old IRPManager and New IRPManager.
+
+## 6.3 SS-level
+
+### 6.3.1 CORBA
+
+For CORBA Solution Set, the IRPAgent level (see subclause 5.3) context would be used.
+
+### 6.3.2 Void
+
+### 6.3.3 File format description XML
+
+*Editor's Note: This part is FFS.*
+
+### 6.3.4 File format description ASN.1
+
+*Editor's Note: This part is FFS.*
+
+### 6.3.5 SOAP
+
+*Editor's Note: This part is FFS.*
+
+# Annex A (informative): BC and Conformance Tests
+
+This annex illustrates that:
+
+- an IRP, implementing a new-version IRP specification that is BC to an old-version IRP specification, may or may not be compliant to the old-version IRP specification.
+
+
+
+```
+
+graph TD
+ OVS[Old-version IRP specification] -- "extend, based on BC-Rules" --> NVS[New-version IRP specification]
+ OIRP[Old-IRP] -- implement --> OVS
+ NIRP[New-IRP] -- implement --> NVS
+ CTO[Conformance tests] -- depend --> OVS
+ CTN[Conformance tests] -- depend --> NVS
+ OIRP -- "test (should be OK)" --> CTO
+ NIRP -- "test (should be OK)" --> CTN
+ NIRP -- "test (should fail)" --> CTO
+
+```
+
+Diagram illustrating the BC and Conformance Tests Scenario. It shows two parallel tracks: Old-version and New-version. 'Old-version IRP specification' is extended to 'New-version IRP specification' based on BC-Rules. 'Old-IRP' implements 'Old-version IRP specification' and is tested against 'Conformance tests' (should be OK), which depend on the 'Old-version IRP specification'. 'New-IRP' implements 'New-version IRP specification' and is tested against its own 'Conformance tests' (should be OK). A diagonal arrow shows 'New-IRP' being tested against the old 'Conformance tests' with the label 'test (should fail)'.
+
+**Figure A.1: BC and Conformance Tests Scenario**
+
+Suppose 3GPP has an older-version IRP specification (the "Old-version IRP specification" box) and there is a valid/correct implementation (the "Old-IRP" box).
+Suppose also that 3GPP produce a "New-version IRP specification" by extending the "Old-version IRP specification" using the BC-rules.
+
+The "New-IRP" should interwork with IRPManager that uses the "New-version IRP specification".
+This "New-IRP" should also interwork with IRPManager that uses the "Old-version IRP specification".
+
+The "Old-IRP" should pass the conformance test that is based on (see "depend" relation) the "Old-version IRP specification".
+Likewise, the "New-IRP" should pass the conformance test that is based on the "New-version IRP specification".
+
+However, this "New-IRP" may not be able to pass the conformance test that is based on "Old-version IRP specification" (see "test (should fail)" relation).
+Likewise, the "Old-IRP" should not be able to pass the conformance test that is based on "New-Version IRP specification".
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|-----|-----|--------------------------------------------------|-----|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| Mar 2007 | SA_35 | SP-070065 | -- | -- | Submitted to TSG SA#35 for Information | -- | 1.0.0 | |
+| Jun 2007 | SA_36 | SP-070283 | -- | -- | Submitted to TSG SA#36 for Approval | -- | 2.0.0 | 7.0.0 |
+| Dec 2008 | SA_42 | -- | -- | -- | Upgrade to Release 8 | - | 7.0.0 | 8.0.0 |
+| Dec 2009 | - | - | - | - | Update to Rel-9 version (MCC) | - | 8.0.0 | 9.0.0 |
+| Mar 2010 | SA_47 | SP-100036 | 001 | -- | Introduction of SOAP SS | C | 9.0.0 | 10.0.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | | 10.0.0 | <b>11.0.0</b> |
+| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) | | 11.0.0 | <b>12.0.0</b> |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | <b>13.0.0</b> |
+| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | | 13.0.0 | <b>14.0.0</b> |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-06 | | | | | | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
+| 2022-03 | - | - | - | - | - | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32302/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-18/32_series/32302/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..735399a06d73c3a043710bded8b5cb07548ccc05
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a96e4a69ad406a0efe445436d1ebfa30d3aef3cad73f9750abb160b3b105386
+size 44366
diff --git a/marked/Rel-18/32_series/32302/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Rel-18/32_series/32302/2ba086df3506f81bae3a9b53725dcfea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5311c8e39c5b8307cf528007f147868e71097f70
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/2ba086df3506f81bae3a9b53725dcfea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51fa24b943d11bc6cd75d4ee34f8aa2b65ffcd1596152b896d79cf1f283ba242
+size 18853
diff --git a/marked/Rel-18/32_series/32302/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32302/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5eef52bd5febdd311709f2f538ca9c6cea1c447
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:446754ca0bb17b4a2a0587f9d84b96c00ae0c9961ee7235e36de0e0226045679
+size 9370
diff --git a/marked/Rel-18/32_series/32302/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32302/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..973a9f062e3e3ffb8e9d22a3bdc4e168ffce1fe6
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90bc7f07da9debdc6628b36ad585905e430ac4370f3980c44c29f2f0fa839b2b
+size 6218
diff --git a/marked/Rel-18/32_series/32302/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-18/32_series/32302/7f17c430b9598e4d748a8041457810b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..56d58f9df7705868eb12934e074490b36b40ff30
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/7f17c430b9598e4d748a8041457810b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6e5045a27065f408664bc9f5126c4b361d8f434cd53979eeeb5ae933b59e7a37
+size 69481
diff --git a/marked/Rel-18/32_series/32302/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-18/32_series/32302/99bae07626f60f9ede10e2e387ef7051_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd0ab333866ed84a27fba1be533bb71ee8393f73
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/99bae07626f60f9ede10e2e387ef7051_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cbadd550414d0d7635ab0bb2c21f68f196c3ea09da77ba24264c9fc42814e570
+size 23574
diff --git a/marked/Rel-18/32_series/32302/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-18/32_series/32302/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88755553d382786761323a637c620d17d19f7a36
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:236dd0e46f09628ad0d2fbdf5dab462c9fe22d4e1c270a4f1e353f5e56848aea
+size 119592
diff --git a/marked/Rel-18/32_series/32302/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/Rel-18/32_series/32302/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..749cd588ec76e3d3b5ae3498b2cdd418acf98549
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33e35a4d9816561a4924fa215bd4a42239645813743ac88d673d9e6b0aa13a17
+size 17829
diff --git a/marked/Rel-18/32_series/32302/raw.md b/marked/Rel-18/32_series/32302/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4e71f624acf490c4348511aca3b1d8bcbf0ce97
--- /dev/null
+++ b/marked/Rel-18/32_series/32302/raw.md
@@ -0,0 +1,951 @@
+
+
+# 3GPP TS 32.302 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+UMTS, management
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|---------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions and abbreviations ..... | 8 |
+| 3.1 Definitions..... | 8 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 System overview ..... | 9 |
+| 4.1 System Context ..... | 9 |
+| 5 Information Object Classes..... | 9 |
+| 5.1 Imported information entities and local labels..... | 9 |
+| 5.2 Class Diagram ..... | 10 |
+| 5.2.1 Attributes and relationships..... | 10 |
+| 5.2.2 Inheritance ..... | 10 |
+| 5.3 Information object classes definition ..... | 11 |
+| 5.3.1 NtfSubscriber..... | 11 |
+| 5.3.1.1 Definition ..... | 11 |
+| 5.3.1.2 Attributes ..... | 11 |
+| 5.3.2 NtfSubscription..... | 11 |
+| 5.3.2.1 Definition ..... | 11 |
+| 5.3.2.2 Attributes ..... | 11 |
+| 5.3.2.3 State diagram ..... | 12 |
+| 5.3.3 NotificationIRP ..... | 12 |
+| 5.3.3.1 Definition ..... | 12 |
+| 5.4 Information relationship definitions..... | 13 |
+| 5.4.1 relation-ntfSubscriber-ntfSubscription (M)..... | 13 |
+| 5.4.1.1 Definition ..... | 13 |
+| 5.4.1.2 Roles ..... | 13 |
+| 5.4.1.3 Constraints ..... | 13 |
+| 5.4.2 relation-ntfIRP-ntfSubscriber (M)..... | 13 |
+| 5.4.2.1 Definition ..... | 13 |
+| 5.4.2.2 Roles ..... | 13 |
+| 5.4.2.3 Constraints ..... | 13 |
+| 5.5 Information attribute definitions ..... | 14 |
+| 5.5.1 Definitions and legal values ..... | 14 |
+| 5.5.2 Constraints..... | 14 |
+| 6 Interface Definition ..... | 15 |
+| 6.1 Class diagram representing interfaces..... | 15 |
+| 6.2 Generic rules ..... | 15 |
+| 6.3 notificationIRPManagement Interface (M)..... | 16 |
+| 6.3.1 Operation subscribe (M)..... | 16 |
+| 6.3.1.1 Definition ..... | 16 |
+| 6.3.1.2 Input parameters ..... | 16 |
+| 6.3.1.3 Output parameters..... | 16 |
+| 6.3.1.4 Pre-condition..... | 16 |
+| 6.3.1.5 Post-condition ..... | 17 |
+| 6.3.1.6 Exceptions..... | 17 |
+| 6.3.2 Operation unsubscribe (M)..... | 17 |
+| 6.3.2.1 Definition ..... | 17 |
+| 6.3.2.2 Input parameters ..... | 17 |
+| 6.3.2.3 Output parameters..... | 18 |
+| 6.3.2.4 Pre-condition..... | 18 |
+| 6.3.2.5 Post-condition ..... | 18 |
+
+| | | |
+|-------------------------------|---------------------------------------------------|-----------|
+| 6.3.2.6 | Exceptions..... | 18 |
+| 6.4 | subscriberManagement Interface (O)..... | 18 |
+| 6.4.1 | Operation getSubscriptionIds (M) ..... | 18 |
+| 6.4.1.1 | Definition ..... | 18 |
+| 6.4.1.2 | Input parameters ..... | 18 |
+| 6.4.1.3 | Output parameters..... | 19 |
+| 6.4.1.4 | Pre-condition..... | 19 |
+| 6.4.1.5 | Post-condition ..... | 19 |
+| 6.4.1.6 | Exceptions..... | 19 |
+| 6.5 | subscriptionStatusOperations Interface (O) ..... | 19 |
+| 6.5.1 | Operation getSubscriptionStatus (M) ..... | 19 |
+| 6.5.1.1 | Definition ..... | 19 |
+| 6.5.1.2 | Input parameters ..... | 19 |
+| 6.5.1.3 | Output parameters..... | 20 |
+| 6.5.1.4 | Pre-condition..... | 20 |
+| 6.5.1.5 | Post-condition ..... | 20 |
+| 6.5.1.6 | Exceptions..... | 20 |
+| 6.6 | subscriptionFilterOperations Interface (O) ..... | 20 |
+| 6.6.1 | Operation changeSubscriptionFilter (M)..... | 20 |
+| 6.6.1.1 | Definition ..... | 20 |
+| 6.6.1.2 | Input parameters ..... | 20 |
+| 6.6.1.3 | Output parameters..... | 21 |
+| 6.6.1.4 | Pre-condition..... | 21 |
+| 6.6.1.5 | Post-condition ..... | 21 |
+| 6.6.1.6 | Exceptions..... | 21 |
+| 6.7 | subscriptionSuspendOperations Interface (O) ..... | 21 |
+| 6.7.1 | Operation suspendSubscription (M) ..... | 21 |
+| 6.7.1.1 | Definition ..... | 21 |
+| 6.7.1.2 | Input parameters ..... | 21 |
+| 6.7.1.3 | Output parameters..... | 21 |
+| 6.7.1.4 | Pre-condition..... | 22 |
+| 6.7.1.5 | Post-condition ..... | 22 |
+| 6.7.1.6 | Exceptions..... | 22 |
+| 6.7.2 | Operation resumeSubscription (M)..... | 22 |
+| 6.7.2.1 | Definition ..... | 22 |
+| 6.7.2.2 | Input parameters ..... | 22 |
+| 6.7.2.3 | Output parameters..... | 22 |
+| 6.7.2.4 | Pre-condition..... | 22 |
+| 6.7.2.5 | Post-condition ..... | 23 |
+| 6.7.2.6 | Exceptions..... | 23 |
+| 6.8 | IRPManagementOperations Interface (O) ..... | 24 |
+| 6.8.1 | Operation getNotificationCategories (M)..... | 24 |
+| 6.8.1.1 | Definition ..... | 24 |
+| 6.8.1.2 | Input parameters ..... | 24 |
+| 6.8.1.3 | Output parameters..... | 24 |
+| 6.8.1.4 | Pre-condition..... | 24 |
+| 6.8.1.5 | Post-condition ..... | 24 |
+| 6.8.1.6 | Exceptions..... | 24 |
+| 6.9 | NotificationIRPNotification Interface..... | 25 |
+| <b>Annex A (informative):</b> | <b>Change history.....</b> | <b>27</b> |
+
+# Foreword
+
+This Technical Specification (TS) 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements
+- 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)**
+- 32.303: Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
+- 32.305: Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition
+- 32.307: Configuration Management (CM); Notification Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS)
+
+The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [5] and 3GPP TS 32.102 [6].
+
+Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in Alarm IRP: Information Service [1], is one possible kind of event, an object creation as specified in Basic CM IRP: Information Service [8] is another possible kind of event.
+
+Information of an event is carried in notification. An IRP Agent (typically an EM or a NE) emits notifications. IRP Manager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRP Manager can subscribe to IRP Agent for receiving notifications.
+
+This IRP bases its design on work captured in ITU-T Recommendation X.734 [2], OMG Notification Service [4]. The central design ideas are:
+
+- Separation of notification Consumers (IRP Managers) from Producers (IRP Agents);
+
+- Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications.
+
+Common characteristics related to notifications in all other IRPs are gathered in one IRP.
+
+# 1 Scope
+
+The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Information Service" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
+
+An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information Service [1]) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent's emission of notifications (suspendSubscription and resumeSubscription operations).
+
+Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
+
+Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
+
+This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, *perceivedSeverity* is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP: Information Service [1].
+
+How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
+
+This IRP IS is aligned with ITU-T M.3702 [13] in terms of the definitions of operations for Notification management.
+
+# 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 TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [2] ITU-T Recommendation X.734 (1992): "Information technology - Open Systems Interconnection - Systems management: Event report management function".
+- [3] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+- [4] Void
+- [5] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+
+- [6] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [7] 3GPP TS 32.301: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements".
+- [8] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
+- [9] Void.
+- [10] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management: Information Service (IS)".
+- [11] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements".
+- [12] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [13] ITU-T M.3702 (01/2012): "Telecommunication Management, Including TMN and Network Maintenance; Integrated services digital networks; Common management services – Notification management – Protocol neutral requirements and analysis".
+- [14] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [14], 3GPP TS 32.101 [5], 3GPP TS 32.102 [6] and 3GPP TS 32.301 [7] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [14], 3GPP TS 32.101 [5], 3GPP TS 32.102 [6] and 3GPP TS 32.301 [7].
+
+**IRP Agent:** See 3GPP TS 32.102 [6].
+
+**IRP Manager:** See 3GPP TS 32.102 [6].
+
+**event:** it is an occurrence that is of significance to network operators, the NEs under surveillance and network management applications
+
+Events can indicate many types of network management information, such as network alarms, network configuration change information and network performance data.
+
+**notification:** it refers to the transport of information regarding events from event producer to consumer (receiver)
+In this IRP, notification is used to carry information about network events from IRP Agent to IRP Manager. Producer sends notifications to consumers as soon as new events occur. Consumer does not need to check ("pull") for events.
+
+**IRP:** See 3GPP TS 32.102 [6].
+
+**notification category:** The semantics and syntax of the notification category string are identical to that defined for "IRP document version number string", see 3GPP TS 32.311 [11] subclause 3.1.
+
+**qualifiers:** the meaning of qualifiers for operations, parameters and information attributes (whether they are Mandatory(M)/ Conditional(C)/ Optional(O)) defined in the present (Information Service) document is provided in 3GPP TS 32.102 [6].
+
+Moreover, qualifiers of information attributes, when those information attributes are re-used in other IRP ISs, obey to the following rule: Mandatory and Conditional qualifiers of information attributes shall always be the same in other IRPs ISs, Optional qualifiers of information attributes may be set to either Optional or Mandatory in the other IRP ISs.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [14] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [14].
+
+| | |
+|-----|--------------------------|
+| CM | Configuration Management |
+| DN | Distinguished Name |
+| IOC | Information Object Class |
+| NM | Network Manager |
+| SS | Solution Set |
+
+# 4 System overview
+
+## 4.1 System Context
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [12] subclause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in figure 1 and figure 2.
+
+
+
+Diagram illustrating System Context A. On the left, a box labeled 'NM' contains 'IRPManager'. On the right, a box labeled 'EM' contains 'IRPAgent'. A solid line connects 'IRPManager' and 'IRPAgent', crossing a vertical dashed line labeled 'Itf-N'. To the right of 'IRPAgent', a dotted line connects to a box labeled 'NEs'. Below the dashed line, a curved arrow labeled 'Notification IRP' points towards the 'Itf-N' interface.
+
+Figure 1: System Context A
+
+Figure 1: System Context A
+
+
+
+Diagram illustrating System Context B. On the left, a box labeled 'NM' contains 'IRPManager'. On the right, a box labeled 'NE' contains 'IRPAgent'. A solid line connects 'IRPManager' and 'IRPAgent', crossing a vertical dashed line labeled 'Itf-N'. Below the dashed line, a curved arrow labeled 'Notification IRP' points towards the 'Itf-N' interface.
+
+Figure 2: System Context B
+
+Figure 2: System Context B
+
+# 5 Information Object Classes
+
+## 5.1 Imported information entities and local labels
+
+| Label reference | Local label |
+|-----------------------------------------------------|-------------------|
+| 3GPP TS 32.312 [10], Support IOC, ManagedGenericIRP | ManagedGenericIRP |
+
+## 5.2 Class Diagram
+
+### 5.2.1 Attributes and relationships
+
+This subclause depicts the set of Support IOCs that encapsulate information within the notification IRP. The intent is to identify the information required for the notification IRP implementation of its operations and notification emission. This subclause provides the overview of all Support IOCs in UML. Subsequent subclauses provide more detailed specification of various aspects of these Support IOCs.
+
+
+
+```
+
+classDiagram
+ class NotificationIRP {
+ <<SupportIOC>>
+ }
+ class NtfSubscriber {
+ <<SupportIOC>>
+ }
+ class NtfSubscription {
+ <<SupportIOC>>
+ }
+ NotificationIRP "1" *-- "0..n" NtfSubscriber : +theNotificationIRP, relation-ntfIRP-ntfSubscriber
+ NtfSubscriber "1" -- "1..n" NtfSubscription : +theNtfSubscriber, +theNtfSubscription, relation-ntfSubscriber-ntfSubscription
+
+```
+
+The diagram illustrates three classes: **NotificationIRP**, **NtfSubscriber**, and **NtfSubscription**, all marked as **<<SupportIOC>>**. **NotificationIRP** has a composition relationship with **NtfSubscriber**, labeled **+theNotificationIRP** at the **NotificationIRP** end and **relation-ntfIRP-ntfSubscriber** for the association. The multiplicity is **1** at **NotificationIRP** and **0..n** at **NtfSubscriber**. **NtfSubscriber** has a bidirectional association with **NtfSubscription**, labeled **+theNtfSubscriber** at the **NtfSubscriber** end and **+theNtfSubscription** at the **NtfSubscription** end, with the association name **relation-ntfSubscriber-ntfSubscription**. The multiplicity is **1** at **NtfSubscriber** and **1..n** at **NtfSubscription**.
+
+UML Class Diagram showing relationships between NotificationIRP, NtfSubscriber, and NtfSubscription.
+
+### 5.2.2 Inheritance
+
+This subclause depicts the inheritance relationships that exist between Support IOCs.
+
+
+
+```
+
+classDiagram
+ class ManagedGenericIRP {
+ <<SupportIOC>>
+ ManagedGenericIRP (from TS 32.312)
+ }
+ class NotificationIRP {
+ <<SupportIOC>>
+ }
+ NotificationIRP --|> ManagedGenericIRP
+
+```
+
+The diagram shows an inheritance relationship where **NotificationIRP** (marked as **<<SupportIOC>>**) inherits from **ManagedGenericIRP** (marked as **<<SupportIOC>>** and noted as being from TS 32.312). The inheritance is indicated by a solid line with an open triangle arrowhead pointing from **NotificationIRP** to **ManagedGenericIRP**.
+
+UML Class Diagram showing inheritance from NotificationIRP to ManagedGenericIRP.
+
+## 5.3 Information object classes definition
+
+### 5.3.1 NtfSubscriber
+
+#### 5.3.1.1 Definition
+
+This Support IOC represents a Subscriber from a notification IRP perspective : a subscriber is fully identified by a manager reference. An IRPManager using multiple managerReference attributes to subscribe will result in multiple NtfSubscriber instances.
+
+#### 5.3.1.2 Attributes
+
+| Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
+|---------------------|-------------------|----------------|-----------------|
+| ntfManagerReference | M | M | M |
+
+### 5.3.2 NtfSubscription
+
+#### 5.3.2.1 Definition
+
+This Support IOC represents a subscription that has been requested by an IRPManager and created.
+
+#### 5.3.2.2 Attributes
+
+| Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
+|----------------------------|-------------------|----------------|-----------------|
+| ntfSubscriptionId | M | M | - |
+| ntfSubscriptionState | M | M | M |
+| ntfTimeTick | M | M | M |
+| ntfTimeTickTimer | M | - | - |
+| ntfNotificationCategorySet | M | M | M |
+| ntfFilter | M | M | M |
+
+#### 5.3.2.3 State diagram
+
+The diagram below depicts states that can be supported by a NtfSubscription.
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> notSuspended : subscribe / ntfTimeTickTimer initialised
+ state "notSuspended" as notSuspended
+ notSuspended --> [*] : ntfTimeTickTimer=0 / ntfSubscription (and possibly ntfSubscriber) is deleted.
+ notSuspended --> notSuspended : resumeSubscription
+ notSuspended --> suspended : suspendSubscription
+ suspended --> notSuspended : resumeSubscription
+ suspended --> [*] : unsubscribe / ntfSubscription (and possibly ntfSubscriber) is deleted
+ notSuspended --> notSuspended : getSubscriptionStatus / ntfTimeTickTimer re-initialised
+ notSuspended --> [*] : ntfTimeTickTimer=0 / ntfSubscription is not deleted
+
+```
+
+State diagram for NtfSubscription. The diagram shows a start state leading to a 'notSuspended' state within a composite state. Transitions include 'subscribe', 'suspendSubscription', 'resumeSubscription', 'getSubscriptionStatus', and 'unsubscribe'.
+
+NotificationIRP can lose the list of `managerReference` that identifies current IRPManagers under subscription. Under this condition, IRP Agent is incapable of sending events to the affected subscriber(s).
+
+This Notification IRP recommends that IRPManager should invoke the `getSubscriptionStatus` operation periodically to confirm that IRP Agent still has the IRPManager's reference in its list. In case `getSubscriptionStatus` returns the exception `operation_failed`, IRPManager should assume that IRP Agent has lost the IRPManager's reference.
+
+This IRP does not recommend the frequency IRPManager should use to invoke `getSubscriptionStatus` operation.
+
+### 5.3.3 NotificationIRP
+
+#### 5.3.3.1 Definition
+
+This Support IOC represents a notification IRP. It inherits from Support IOC `ManagedGenericIRP`.
+
+## 5.4 Information relationship definitions
+
+### 5.4.1 relation-ntfSubscriber-ntfSubscription (M)
+
+#### 5.4.1.1 Definition
+
+This relationship defines the relationship between a NtfSubscriber and its current subscriptions.
+
+#### 5.4.1.2 Roles
+
+| Name | Definition |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| theNtfSubscriber | This role represents the one who has subscribed. It can be played by instances of Support IOC NtfSubscriber |
+| theNtfSubscription | This role represents the subscriptions which were made and not unsubscribed. It can be played by instances of Support IOC NtfSubscription |
+
+#### 5.4.1.3 Constraints
+
+| Name | Definition |
+|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| inv_notificationCategoriesAllDistinct | The notification categories contained in the ntfNotificationCategorySet attribute of NtfSubscription playing the role theNtfSubscription are all distinct from each other. |
+
+### 5.4.2 relation-ntfIRP-ntfSubscriber (M)
+
+#### 5.4.2.1 Definition
+
+This relationship defines the relationship between the NotificationIRP and the current subscribers of notifications.
+
+#### 5.4.2.2 Roles
+
+| Name | Definition |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| theNtfSubscriber | This role represents the entities to which IRP Agent will notify events. It is played by instances of Support IOC NtfSubscriber |
+| theNotificationIRP | This role represents the NotificationIRP to which an IRP Manager has subscribed. It is played by instances of Support IOC NotificationIRP |
+
+#### 5.4.2.3 Constraints
+
+| Name | Definition |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| inv_uniqueManagerReference | All NtfSubscriber involved in the subscriptionRegistration relationship with NotificationIRP are distinguished from each other by their ntfManagerReference Attribute. |
+
+## 5.5 Information attribute definitions
+
+This subclause defines the semantics of the Attributes used in Support IOCs.
+
+### 5.5.1 Definitions and legal values
+
+| Attribute Name | Definition | Legal Values |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|
+| ntfSubscriptionId | It identifies uniquely a subscription | N/A |
+| ntfSubscriptionState | It indicates the activation state of a subscription | "suspended": the subscription is suspended<br>"notSuspended": the subscription is active |
+| ntfTimeTick | this Attribute represents the initial value of ntfTimeTickTimer. It is in unit of whole minute. This value defines a time window within which IRPManager intends to invoke getSubscriptionStatus (or subscribe) operation to confirm its subscription. A special value indicates infinity which is such that timer will never expire and IRPAgent needs other means to decide when to delete resources allocated to the IRPManager | Integer greater or equal to 15, OR special infinite value |
+| ntfTimeTickTimer | this Attribute represents the current value of a timer | integer greater or equal to zero |
+| ntfNotificationCategorySet | this Attribute represents a set of notification categories (see also Definition of notification category in subclause 3.1) | |
+| ntfFilter | this Attribute represents the filter of a subscription. The filter can be applied to parameters of notification header (see NotificationIRPNotification interface) and to parameters of notifications defined as filterable in other IRP ISs. IRPAgent shall notify IRPManagers if the event satisfies the filter constraint. | |
+| ntfManagerReference | this Attribute contains the reference of a manager. It uniquely identifies a subscriber | |
+
+### 5.5.2 Constraints
+
+- "ntfTimeTickTimer is lower or equal to ntfTimeTick".
+
+# 6 Interface Definition
+
+## 6.1 Class diagram representing interfaces
+
+
+
+```
+
+classDiagram
+ class SubscriptionStatusOperations {
+ <<Interface>>
+ getSubscriptionStatus()
+ }
+ class SubscriptionFilterOperations {
+ <<Interface>>
+ changeSubscriptionFilter()
+ }
+ class SubscriptionSuspendOperations {
+ <<Interface>>
+ suspendSubscription()
+ resumeSubscription()
+ }
+ class IRPManagementOperations {
+ <<Interface>>
+ getNotificationCategories()
+ }
+ class NotificationIRPManagement {
+ <<Interface>>
+ subscribe()
+ unsubscribe()
+ }
+ class SubscriberManagement {
+ <<Interface>>
+ getSubscriptionIds()
+ }
+ class NotificationIRP {
+ <<SupportIOC>>
+ }
+ class NotificationIRPNotification {
+ <<Interface>>
+ notify()
+ }
+
+ NotificationIRP --> SubscriptionStatusOperations : <<may realize>>
+ NotificationIRP --> SubscriptionFilterOperations : <<may realize>>
+ NotificationIRP --> SubscriptionSuspendOperations : <<may realize>>
+ NotificationIRP --> IRPManagementOperations : <<may realize>>
+ NotificationIRP --> NotificationIRPManagement : <<may realize>>
+ NotificationIRP --> SubscriberManagement : <<may realize>>
+ NotificationIRP --> NotificationIRPNotification : <<use>> 0..1
+
+```
+
+This <<interface>> defines the notificationHeader. Other <<interface>>, such as AlarmIRPNotification, inherits from this <<interface>> and the notifications emitted by these other <<interface>> shall support the inherited notificationHeader.
+
+UML Class diagram showing the NotificationIRP interface and its associated interfaces.
+
+## 6.2 Generic rules
+
+- Rule 1:** Each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+- Rule 2:** Each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+- Rule 3:** Each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 notificationIRPManagement Interface (M)
+
+### 6.3.1 Operation subscribe (M)
+
+#### 6.3.1.1 Definition
+
+IRPManager invokes this operation to establish subscription to receive network events via notifications, under the filter constraint specified in this operation.
+
+#### 6.3.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|------------------------|-----------|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| managerReference | M | NtfSubscriber.ntfManagerReference | It specifies the reference of IRPManager to which notifications shall be sent. |
+| timeTick | O | NtfSubscription.ntfTimeTick | It specifies the value of a timer hold by NotificationIRP for the subject IRPManager.<br>The value is in unit of whole minute.<br>A special infinite value is assumed when parameter is absent or present but equal to zero. |
+| notificationCategories | O | SET OF (name of IRP, version of IRP) | It identifies one or more Notification Category (see also Definition in subclause 3.1) |
+| filter | O | NtfSubscription.ntfFilter<br><br>Filter constraint grammar is SS dependent | It specifies a filter constraint that IRPAgent shall use to filter notification of the category specified in notificationCategories parameter.<br>If this parameter is absent, then no filter constraint shall be applied. |
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionId | M | NtfSubscription.ntfSubscriptionId | It holds an unambiguous identity of this subscription. |
+| status | M | ENUM (OperationSucceeded, OperationFailedExistingSubscription, OperationFailed) | If subscriptionCreated is true, status = OperationSucceeded.<br>If operation_failed_existing_subscription is true, status = OperationFailedExistingSubscription<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.3.1.4 Pre-condition
+
+notificationCategoriesNotAllSubscribed OR notificationCategoriesParameterAbsentAndNotAllSubscribed.
+
+| Assertion Name | Definition |
+|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| notificationCategoriesNotAllSubscribed | At least one notificationCategory identified in the notificationCategories input parameter is supported by IRPAgent and is not a member of the ntfNotificationCategorySet attribute of an NtfSubscription which is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter. |
+| notificationCategoriesParameterAbsentAndNotAllSubscribed | The notificationCategories input parameter is absent and at least one notificationCategory supported by IRPAgent is not a member of the ntfNotificationCategorySet attribute of an ntfSubscription which is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter. |
+
+#### 6.3.1.5 Post-condition
+
+subscriberPossiblyCreated AND subscriptionCreated.
+
+| Assertion Name | Definition |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriberPossiblyCreated | An NtfSubscriber with a ntfManagerReference attribute equal to the value of the managerReference input parameter is involved in a subscriptionRegistration relationship with NotificationIRP. |
+| subscriptionCreated | An NtfSubscription has been created according to the following rules: <ul style="list-style-type: none"> <li>- ntfSubscriptionState attribute value has been set to "notSuspended";</li> <li>- ntfTimeTick attribute value has been set to the value of the timeTick input parameter if this value was higher or equal to 15, or set to 15 if this parameter value was between 1 and 15, or set to a special infinite value if the parameter value was lower or equal to 0 or if parameter was absent;</li> <li>- ntfTimeTickTimer has been reset with the value of timeTick attribute;</li> <li>- ntfFilter attribute value has been set to the value of the filter input parameter if present;</li> <li>- NtfSubscription is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter;</li> <li>- attribute ntfNotificationCategorySet of NtfSubscription contains EITHER the notification categories identified by the notificationCategories input parameter that were not already contained in the ntfNotificationCategorySet attribute of other NtfSubscription of the same NtfSubscriber identified by the managerReference input parameter OR if notificationCategories input parameter is absent, all notification categories supported by IRPAgent that were not already contained in the ntfNotificationCategorySet attribute of other subscriptions of the same NtfSubscriber identified by the managerReference input parameter.</li> </ul> |
+
+#### 6.3.1.6 Exceptions
+
+| Name | Definition |
+|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed_existing_subscription | <b>Condition:</b> (notificationCategoriesNotAllSubscribed OR notificationCategoriesParameterAbsentAndNotAllSubscribed) not true<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+| Operation_failed | <b>Condition:</b> Post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+### 6.3.2 Operation unsubscribe (M)
+
+#### 6.3.2.1 Definition
+
+The IRPManager invokes this operation to cancel subscriptions. The IRPManager can cancel one subscription made with a managerReference by providing the corresponding subscriptionId or all subscriptions made with the same managerReference by leaving the subscriptionId parameter absent.
+
+#### 6.3.2.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|------------------|-----------|-----------------------------------|---------------------------------------------------------------------------------------|
+| managerReference | M | NtfSubscriber.ntfManagerReference | It specifies the reference of an IRPManager. |
+| subscriptionId | O | NtfSubscription.ntfSubscriptionId | It holds a subscriptionId carried as the output parameter in the subscribe operation. |
+
+#### 6.3.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| status | M | ENUM<br>(OperationSucceeded,<br>OperationFailed) | If (subscriptionDeleted OR allSubscriptionDeleted) is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.3.2.4 Pre-condition
+
+validSubscriptionId&ManagerReference OR SubscriptionIdAbsent&ValidManagerReference
+
+| Assertion Name | Definition |
+|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId&ManagerReference | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter. |
+| SubscriptionIdAbsent&ValidManagerReference | The subscriptionId input parameter is absent and the NtfSubscriber identified by the managerReference input parameter exists. |
+
+#### 6.3.2.5 Post-condition
+
+subscriptionDeleted OR allSubscriptionDeleted.
+
+| Assertion Name | Definition |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionDeleted | The NtfSubscription identified by subscriptionId input parameter is no more involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter and has been deleted. If this NtfSubscriber has no more NtfSubscription, it is deleted as well. |
+| allSubscriptionDeleted | In the case subscriptionId input parameter was absent, the NtfSubscriber identified by the managerReference input parameter is no more involved in any subscription relationship and is deleted, the corresponding NtfSubscription have been deleted as well. |
+
+#### 6.3.2.6 Exceptions
+
+| Name | Definition |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.4 subscriberManagement Interface (O)
+
+### 6.4.1 Operation getSubscriptionIds (M)
+
+#### 6.4.1.1 Definition
+
+IRPManager invokes this operation to get the values of all still valid (not unsubscribed or removed by IRPAgent) subscriptionIds assigned by NotificationIRP as result of previously subscribe operations performed by this IRPManager.
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|------------------|-----------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| managerReference | M | NtfSubscriber.ntfManagerReference | It specifies the reference of IRPManager that requests the set of identifiers of active subscriptions related to this IRPManager. |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionIdSet | M | SET OF NtfSubscription.ntfSubscriptionId where NtfSubscription is involved in a subscription relationship with the NtfSubscriber identified by the managerReference input parameter | It holds a set of the subscriptionId, each assigned as output parameter in previous subscribe operations invoked by the current IRPManager. This value should contain no information if the IRPManager did not yet subscribed to that System or System lost all subscription related information. |
+| status | M | ENUM (Operation succeeded, Operation failed) | If validSubscriptionIdSet is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.4.1.4 Pre-condition
+
+validManagerReference.
+
+| Assertion Name | Definition |
+|-----------------------|------------------------------------------------------------------------------|
+| validManagerReference | The NtfSubscriber identified by the managerReference input parameter exists. |
+
+#### 6.4.1.5 Post-condition
+
+None specific
+
+#### 6.4.1.6 Exceptions
+
+| Name | Definition |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.5 subscriptionStatusOperations Interface (O)
+
+### 6.5.1 Operation getSubscriptionStatus (M)
+
+#### 6.5.1.1 Definition
+
+IRPManager invokes this operation to query the subscription status of a particular subscription. IRPManager can use getSubscriptionStatus operation to know about the filter constraint in effect, the state of subscription (i.e. if subscription is suspended/inactive or resumed/active), the timeTick value that may be set at subscribe invocation time and the notificationCategory currently in used in the subscription.
+
+#### 6.5.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|----------------|-----------|-----------------------------------|----------------------------------------------------------------------------------------|
+| subscriptionId | M | NtfSubscription.ntfSubscriptionId | It holds the subscriptionId carried as the output parameter in the subscribe operation |
+
+#### 6.5.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-------------------------|-----------|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| notificationCategorySet | C | NtfSubscription.ntfNotificationCategorySet | It identifies the notification Category(ies) supported in this subscription. |
+| filterInEffect | O | NtfSubscription.ntfFilter | It contains the filter constraint currently set. |
+| SubscriptionState | O | NtfSubscription.ntfSubscriptionState | |
+| timeTick | O | NtfSubscription.ntfTimeTick | It carries the same value as the one in subscribe operation |
+| status | M | ENUM (Operation succeeded, Operation failed) | If (timeTickReset) is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.5.1.4 Pre-condition
+
+validSubscriptionId.
+
+| Assertion Name | Definition |
+|---------------------|---------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId | "the NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship" |
+
+#### 6.5.1.5 Post-condition
+
+timeTickReset
+
+| Assertion Name | Definition |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| timeTickReset | The ntfTimeTickTimer attribute of NtfSubscription identified as input parameter has been reset with the value of ntfTimeTick attribute of the same NtfSubscription. |
+
+#### 6.5.1.6 Exceptions
+
+| Name | Definition |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.6 subscriptionFilterOperations Interface (O)
+
+### 6.6.1 Operation changeSubscriptionFilter (M)
+
+#### 6.6.1.1 Definition
+
+IRPManager invokes this operation to replace the present filter constraint with a new one.
+
+#### 6.6.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|----------------|-----------|-----------------------------------|-------------------------------------------------------------------------------------------|
+| subscriptionId | M | NtfSubscription.ntfSubscriptionId | It carries the subscriptionId carried as the output parameter in the subscribe operation. |
+| filter | M | NtfSubscription.ntfFilter | It specifies a filter constraint |
+
+#### 6.6.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| status | M | ENUM (Operation succeeded, Operation failed) | If filterUpdated is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.6.1.4 Pre-condition
+
+validNtfSubscriptionId.
+
+| Assertion Name | Definition |
+|------------------------|--------------------------------------------------------------------------------------------------------------|
+| validNtfSubscriptionId | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship. |
+
+#### 6.6.1.5 Post-condition
+
+filterUpdated.
+
+| Assertion Name | Definition |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| filterUpdated | The ntfFilter attribute value of the NtfSubscription identified by subscriptionId input parameter has been set to the value of the filter input parameter. |
+
+#### 6.6.1.6 Exceptions
+
+| Name | Definition |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.7 subscriptionSuspendOperations Interface (O)
+
+### 6.7.1 Operation suspendSubscription (M)
+
+#### 6.7.1.1 Definition
+
+IRPManager invokes this operation to request IRPAgent to stop emission of notifications. IRPAgent may lose notification(s) if subscription is suspended.
+
+#### 6.7.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|----------------|-----------|-----------------------------------|-------------------------------------------------------------------------------------------|
+| subscriptionId | M | NtfSubscription.ntfSubscriptionId | It carries the subscriptionId carried as the output parameter in the subscribe operation. |
+
+#### 6.7.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| status | M | ENUM (Operation succeeded, Operation failed) | If subscriptionStateSuspended is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.7.1.4 Pre-condition
+
+validSubscriptionId.
+
+| Assertion Name | Definition |
+|---------------------|--------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship. |
+
+#### 6.7.1.5 Post-condition
+
+subscriptionStateSuspended.
+
+| Assertion Name | Definition |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionStateSuspended | The ntfSubscriptionState attribute value of the NtfSubscription identified by subscriptionId input parameter has been set to or kept as "suspended". |
+
+#### 6.7.1.6 Exceptions
+
+| Name | Definition |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+### 6.7.2 Operation resumeSubscription (M)
+
+#### 6.7.2.1 Definition
+
+IRPManager invokes this operation to request IRPAgent to resume emission of notifications.
+
+#### 6.7.2.2 Input parameters
+
+| Parameter Name | Qualifier | Information Type | Comment |
+|----------------|-----------|-----------------------------------|-------------------------------------------------------------------------------------------|
+| subscriptionId | M | NtfSubscription.ntfSubscriptionId | It carries the subscriptionId carried as the output parameter in the subscribe operation. |
+
+#### 6.7.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| status | M | ENUM (Operation succeeded, Operation failed) | If subscriptionStateNotSuspended is true, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.7.2.4 Pre-condition
+
+validSubscriptionId.
+
+| Assertion Name | Definition |
+|---------------------|--------------------------------------------------------------------------------------------------------------|
+| validSubscriptionId | The NtfSubscription identified by subscriptionId input parameter is involved in a subscription relationship. |
+
+#### 6.7.2.5 Post-condition
+
+subscriptionStateNotSuspended.
+
+| Assertion Name | Definition |
+|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| subscriptionStateNotSuspended | The ntfSubscriptionState attribute value of the NtfSubscription identified by subscriptionId input parameter has been set to or kept as "notSuspended". |
+
+#### 6.7.2.6 Exceptions
+
+| Name | Definition |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation_failed | <b>Condition:</b> Pre-condition is false or post-condition is false<br><b>Returned Information:</b> The output parameter status<br><b>Exit state:</b> Entry State |
+
+## 6.8 IRPManagementOperations Interface (O)
+
+### 6.8.1 Operation getNotificationCategories (M)
+
+#### 6.8.1.1 Definition
+
+IRPManager invokes this operation to query the categories of notification supported by IRPAgent. IRPAgent returns the list of categories of notification supported. Each category of notification defines the name and the version of the IRP specification. The list of category of notification returned shall only contain the name and version of the IRP specifications that actually have notifications defined.
+
+IRPManager does not need to be in subscription to invoke this operation.
+
+#### 6.8.1.2 Input parameters
+
+None.
+
+#### 6.8.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|--------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|
+| NotificationCategoryList | M | SET OF (name and version of IRP specification) where each IRP is contained by IRPAgent and the attribute notificationNameProfile of the ManagedGenericIRP is not empty. | |
+| status | M | ENUM (Operation succeeded, Operation failed) | OperationFailed only if operation failed internal problem |
+
+#### 6.8.1.4 Pre-condition
+
+None specific.
+
+#### 6.8.1.5 Post-condition
+
+None specific.
+
+#### 6.8.1.6 Exceptions
+
+None specific.
+
+## 6.9 NotificationIRPNotification Interface
+
+IRP Agent notifies the subscribed IRP Manager that an event has occurred and that the event has satisfied the filter constraints used for this subscription. One event example is the notification defined in Alarm IRP: IS (3GPP TS 32.111-2 [1]).
+
+It should be possible to pack multiple notifications together for sending to NM. This provides more efficient use of data communication resources. In order to pack multiple notifications, an EM/NE configurable parameter defines the maximum number of notifications to be packed together. Additionally an EM/NE configurable parameter defines the maximum time delay before the notifications have to be sent.
+
+Under normal operations, an IRP Agent shall send, to each IRP Manager, notifications in the same order they were generated, i.e. in the First-In, First-Out order. There shall not be any priority given to types of notifications.
+
+This interface doesn't define any specific notification but instead defines information that is commonly found in notifications defined by other IRPs. This information is called notificationHeader. Notification interfaces defined in other IRPs, such as Alarm IRP: IS (3GPP TS 32.111-2 [1]), shall inherit from this interface and define their notifications by:
+
+- Identifying and qualifying the Notification Header attributes for their use;
+- Specify additional attributes specific to their use.
+
+Despite the fact that the semantic of notifications is defined by other IRP ISs, it is notification IRP and not those IRP that is responsible for the emission of those notifications.
+
+The Notification Header is defined here below.
+
+| Attribute Name | Qualifier | Comment |
+|------------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| objectClass | M, Y | It specifies the class name of the IOC. A network event has occurred in an instance of this class. |
+| objectInstance | M, Y | It specifies the instance of the above IOC in which the network event occurred by carrying the Distinguished Name (DN) of this object instance. This object may or may not be identical to the object instance actually emitting the notification. |
+| notificationId | O,N | <p>This is an identifier for the notification, which may be used to correlate notifications. The identifier of the notification shall be chosen to be unique across all notifications of a particular managed object throughout the time that correlation is significant, it uniquely identifies the notification from other notifications generated by the subject Information Object.</p> <p>If IRPManager receives notifications from one IRPAgent, IRPManager shall use the identifier of the notification and the <code>objectInstance</code> to uniquely identify all received notifications.</p> <p>If IRPManager receives notifications from multiple IRPAgents and notifications of each Information Object are reported at most through one IRPAgent, IRPManager shall use the identifier of the notification and <code>objectInstance</code> to uniquely identify all received notifications.</p> <p>If IRPManager receives notifications from multiple IRPAgents and notifications of one or more Information Objects are reported through two or more IRPAgents, IRPManager shall use the identifier of the notification together with <code>objectInstance</code> and the identity of IRPAgent (<code>systemDN</code>), to uniquely identify all received notifications. If the information <code>systemDN</code> is absent, IRPManager needs other means, which are outside the scope of this IRP, to determine the identity of IRPAgent.</p> <p>How identifiers of notifications are re-used to correlate notifications is outside of the scope of this recommendation.</p> |
+| eventTime | M, Y | It indicates the event occurrence time. The semantics of Generalised Time specified by ITU-T shall be used here. |
+| systemDN | C, Y | <p>The <code>systemDN</code> of that notification shall carry either (1) the <code>IRPAgent</code> instance containing that Interface IRP instance, or (2) the DN of that particular Interface IRP instance responsible for the emission of the notification.</p> <p>(1) If the <code>IRPAgent</code> contains single (not multiple) Interface IRP instance of a particular class, then the <code>systemDN</code> of a notification may carry the DN of the <code>IRPAgent</code> or DN of the subject Interface IRP instance.</p> <p>(2) If the <code>IRPAgent</code> contains multiple Interface IRP instances of the same class, then the <code>systemDN</code> of a notification shall carry the DN of a particular Interface IRP instance responsible for the emission of that notification.</p> <p>Example of item (2) above:</p> <ul style="list-style-type: none"> <li>- Alarm IRP:IS specifies <code>notifyNewAlarm</code>. If there are multiple <code>AlarmIRP</code> instances under one <code>IRPAgent</code>, then the <code>systemDN</code> of <code>notifyNewAlarm</code> shall be present and carry the DN of the <code>AlarmIRP</code>.</li> </ul> |
+| notificationType | M, Y | The type of notification which is reported by the notification |
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| Jun 2001 | S_12 | SP-010283 | -- | -- | Approved at TSG SA #12 and placed under Change Control | -- | 2.0.0 | 4.0.0 |
+| Dec 2001 | S_14 | SP-010642 | 0001 | -- | Remove ambiguity of the return information for getNotificationCategories() operation | F | 4.0.0 | 4.1.0 |
+| Dec 2001 | S_14 | SP-010653 | 0002 | -- | Change from Mandatory to Conditional the qualifier of the output parameter 'NotificationCategorySet' of the operation 'getSubscriptionStatus' | C | 4.1.0 | 5.0.0 |
+| Mar 2002 | -- | -- | -- | -- | Cosmetics (changed styles on cover) | -- | 5.0.0 | 5.0.1 |
+| Dec 2002 | -- | -- | -- | -- | Cosmetics | -- | 5.0.1 | 5.0.2 |
+| Jun 2003 | S_20 | SP-030278 | 0004 | -- | Correction of the description of the objectClass and objectInstance parameter of the notification header | A | 5.0.2 | 5.1.0 |
+| Mar 2004 | S_23 | SP-040118 | 0005 | -- | Update Ntf IRP IS using new Template and UML Repertoire | F | 5.1.0 | 6.0.0 |
+| Dec 2004 | S_26 | SP-040793 | 0007 | -- | Add missing rules on how to construct the string NotificationCategory | A | 6.0.0 | 6.1.0 |
+| Mar 2005 | S_27 | SP-050035 | 0008 | -- | Apply Generic System Context | F | 6.1.0 | 6.2.0 |
+| Jun 2005 | -- | -- | -- | -- | Introduction update : added 32.305 new TS-family member | -- | 6.2.0 | 6.2.1 |
+| Mar 2006 | SA_31 | SP-060089 | 0009 | -- | Correct the use/meaning of systemDN in notification header | F | 6.2.1 | 6.3.0 |
+| Jun 2007 | SA_36 | -- | -- | -- | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | -- | 6.3.0 | 7.0.0 |
+| Dec 2008 | SA_42 | -- | -- | -- | Upgrade to Release 8 | - | 7.0.0 | 8.0.0 |
+| Dec 2009 | SA_46 | SP-090719 | 0010 | -- | Align usage of SupportIOC according to repertoire and template | C | 8.0.0 | 9.0.0 |
+| Sep 2010 | SA_49 | SP-100489 | 0011 | -- | Correction of incorrect attribute name for NtfSubscription | F | 9.0.0 | 10.0.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | | 10.0.0 | <b>11.0.0</b> |
+| 2012-12 | SA_58 | SP-120783 | 0012 | - | add reference to ITU-T Rec | F | 11.0.0 | <b>11.1.0</b> |
+| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) | | 11.1.0 | <b>12.0.0</b> |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | <b>13.0.0</b> |
+| 2017-03 | Sa#75 | - | - | - | Promotion to Release 14 without technical change | | 13.0.0 | <b>14.0.0</b> |
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------|---------------|--|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | |
+| 2018-06 | | | | | | Update to Rel-15 version (MCC) | 15.0.0 | |
+| 2019-09 | SA#85 | SP-190752 | 0013 | - | F | Correct definition of NR to align with RAN2 | 15.1.0 | |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | <b>16.0.0</b> | |
+| 2022-03 | - | - | - | - | - | Update to Rel-17 version (MCC) | <b>17.0.0</b> | |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> | |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32332/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-18/32_series/32332/053f1077d592e6622cd21dc4bb4cb366_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..724c81e5cb7b634b8a258e79fab02336536e9fd5
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/053f1077d592e6622cd21dc4bb4cb366_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc6648cca2bbbb99f4ce3f0a5d9e53e9449cb3d503f3328720519dd262d9a433
+size 91412
diff --git a/marked/Rel-18/32_series/32332/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-18/32_series/32332/1c94fd3cebf58af136144f14160d128e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0bf6013783afbd71d2594d4ee464de7a71c81a8
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/1c94fd3cebf58af136144f14160d128e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60f074de79e7563ba64b5850f825743dbe27d0b9418378323b4b5b10e31d2ec1
+size 17151
diff --git a/marked/Rel-18/32_series/32332/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-18/32_series/32332/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aee23283201533f9067e576d2f7d9998760f8ac1
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8cd0b051d3d4ce919ba992c8da4cb2a50c1a06b2704c89a903169742d132d866
+size 102710
diff --git a/marked/Rel-18/32_series/32332/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32332/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2722b334b5e700e83d2c7f4eee85d7f5cfd79d2
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2de95384a199ef4d8219f870e6e2c4738e76ec0eefc425dd761b9ed3779c167
+size 9430
diff --git a/marked/Rel-18/32_series/32332/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32332/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f8b21d0512017cf4d64a1c90003c8823a74e440
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0147016550636d91f2b1dc6e9a5061d8e508ffba28fe9f0232c32ecdadb08a7f
+size 8073
diff --git a/marked/Rel-18/32_series/32332/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-18/32_series/32332/731f533b0599c8e42a063f06e4332045_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..03255d250f8ddf346fd6ad9f5525bdec80460b8a
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/731f533b0599c8e42a063f06e4332045_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0a854f43f6e4bfdcf2e8d508a629f26decd98892c2c1c373b1535bd2ed9ae8d
+size 20293
diff --git a/marked/Rel-18/32_series/32332/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-18/32_series/32332/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50622173731db347a78d59d04c9e3e2b7f4c0f99
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d4ad2d7e67610d30785ae1aee874a5c7c81a993e68f6b3dd32170212304ffc0
+size 33876
diff --git a/marked/Rel-18/32_series/32332/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-18/32_series/32332/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26bbc9effac79324baeaebcc3813637e3155318a
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:597c997cfda6086bdef4c9db183a1f1f8013b318af0b7375a6d9557e97d7a272
+size 98773
diff --git a/marked/Rel-18/32_series/32332/raw.md b/marked/Rel-18/32_series/32332/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3204ab6b45c92e641f93acd81939184f59cccea
--- /dev/null
+++ b/marked/Rel-18/32_series/32332/raw.md
@@ -0,0 +1,1046 @@
+
+
+# 3GPP TS 32.332 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS) (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+UMTS, Management
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## 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 System overview ..... | 8 |
+| 4.2 Compliance rules..... | 8 |
+| 5 Information Object Classes (IOCs)..... | 9 |
+| 5.1 Information entities imported and local labels..... | 9 |
+| 5.2 Class diagram..... | 10 |
+| 5.2.1 Attributes and relationships..... | 10 |
+| 5.2.2 Inheritance ..... | 11 |
+| 5.3 Information Object Class (IOC) definitions..... | 12 |
+| 5.3.1 NLIRP..... | 12 |
+| 5.3.1.1 Definition ..... | 12 |
+| 5.3.1.2 Attributes ..... | 12 |
+| 5.3.2 Log..... | 12 |
+| 5.3.2.1 Definition ..... | 12 |
+| 5.3.2.2 Attributes ..... | 12 |
+| 5.3.2.3 State diagram ..... | 13 |
+| 5.3.3 LogRecord ..... | 13 |
+| 5.3.3.1 Definition ..... | 13 |
+| 5.4 Information relationship definitions..... | 14 |
+| 5.4.1 Relation-nLIRP-log (M) ..... | 14 |
+| 5.4.1.1 Definition ..... | 14 |
+| 5.4.1.2 Role..... | 14 |
+| 5.4.1.3 Constraint..... | 14 |
+| 5.4.2 Relation-log-logRecord (M) ..... | 14 |
+| 5.4.2.1 Definition ..... | 14 |
+| 5.4.2.2 Role..... | 14 |
+| 5.4.2.3 Constraint..... | 14 |
+| 5.4.3 Relation-logRecord-notificationIRPNotification (M) ..... | 15 |
+| 5.4.3.1 Definition ..... | 15 |
+| 5.4.3.2 Role..... | 15 |
+| 5.4.3.3 Constraint..... | 15 |
+| 5.5 Information attribute definition..... | 16 |
+| 5.5.1 Definition and legal values..... | 16 |
+| 5.5.2 Constraints ..... | 17 |
+| 6 Interface definition ..... | 17 |
+| 6.1 Class diagram..... | 17 |
+| 6.2 Generic rules ..... | 18 |
+| 6.3 NLIRPOperations_1 Interface (M) ..... | 18 |
+| 6.3.1 Operation subscribeLog (M) ..... | 18 |
+| 6.3.1.1 Definition ..... | 18 |
+| 6.3.1.2 Input parameters ..... | 18 |
+| 6.3.1.3 Output parameters..... | 19 |
+| 6.3.1.4 Pre-condition..... | 19 |
+| 6.3.1.5 Post-condition ..... | 19 |
+| 6.3.1.6 Exceptions..... | 19 |
+
+| | | |
+|-----------|----------------------------------------------------|----|
+| 6.3.2 | Operation unsubscribeLog (M) ..... | 20 |
+| 6.3.2.1 | Definition ..... | 20 |
+| 6.3.2.2 | Input parameters ..... | 20 |
+| 6.3.2.3 | Output parameters ..... | 20 |
+| 6.3.2.4 | Pre-condition ..... | 20 |
+| 6.3.2.5 | Post-condition ..... | 20 |
+| 6.3.2.6 | Exceptions ..... | 20 |
+| 6.3.3 | Operation exportLogRecords (O) ..... | 21 |
+| 6.3.3.1 | Definition ..... | 21 |
+| 6.3.3.2 | Input parameters ..... | 21 |
+| 6.3.3.3 | Output parameters ..... | 21 |
+| 6.3.3.4 | Pre-condition ..... | 21 |
+| 6.3.3.5 | Post-condition ..... | 21 |
+| 6.3.3.6 | Exceptions ..... | 21 |
+| 6.3.4 | Operation getLogRecords (O) ..... | 22 |
+| 6.3.4.1 | Definition ..... | 22 |
+| 6.3.4.2 | Input parameters ..... | 22 |
+| 6.3.4.3 | Output parameters ..... | 22 |
+| 6.3.4.4 | Pre-condition ..... | 22 |
+| 6.3.4.5 | Post-condition ..... | 22 |
+| 6.3.4.6 | Exceptions ..... | 22 |
+| 6.4 | NLIRPOperations_2 Interface (O) ..... | 23 |
+| 6.4.1 | Operation getLogSubscriptionIds (M) ..... | 23 |
+| 6.4.1.1 | Definition ..... | 23 |
+| 6.4.1.2 | Input parameters ..... | 23 |
+| 6.4.1.3 | Output parameters ..... | 23 |
+| 6.4.1.4 | Pre-condition ..... | 23 |
+| 6.4.1.5 | Post-condition ..... | 23 |
+| 6.4.1.6 | Exceptions ..... | 23 |
+| 6.4.2 | Operation getLogSubscriptionStatus (M) ..... | 24 |
+| 6.4.2.1 | Definition ..... | 24 |
+| 6.4.2.2 | Input parameters ..... | 24 |
+| 6.4.2.3 | Output parameters ..... | 24 |
+| 6.4.2.4 | Pre-condition ..... | 24 |
+| 6.4.2.5 | Post-condition ..... | 24 |
+| 6.4.2.6 | Exceptions ..... | 24 |
+| 6.5 | NLIRPNotifications_1 Interface (M) ..... | 25 |
+| 6.5.1 | Notification notifyLogSubscribed (M) ..... | 25 |
+| 6.5.1.1 | Definition ..... | 25 |
+| 6.5.1.2 | Input Parameters ..... | 25 |
+| 6.5.1.3 | Triggering Event ..... | 25 |
+| 6.5.1.3.1 | From-state ..... | 25 |
+| 6.5.1.3.2 | To-state ..... | 25 |
+| 6.5.2 | Notification notifyLogUnsubscribed (M) ..... | 26 |
+| 6.5.2.1 | Definition ..... | 26 |
+| 6.5.2.2 | Input Parameters ..... | 26 |
+| 6.5.2.3 | Triggering Event ..... | 26 |
+| 6.5.2.3.1 | From-state ..... | 26 |
+| 6.5.2.3.2 | To-state ..... | 26 |
+| 6.6 | NLIRPNotifications_2 Interface (O) ..... | 27 |
+| 6.6.1 | Notification notifyOccupancyLevelCrossed (M) ..... | 27 |
+| 6.6.1.1 | Definition ..... | 27 |
+| 6.6.1.2 | Input Parameters ..... | 27 |
+| 6.6.1.3 | Triggering Event ..... | 27 |
+| 6.6.1.3.1 | From-state ..... | 27 |
+| 6.6.1.3.2 | To-state ..... | 27 |
+| 6.6.2 | Notification notifyLoggingResumed (O) ..... | 28 |
+| 6.6.2.1 | Definition ..... | 28 |
+| 6.6.2.2 | Input Parameters ..... | 28 |
+| 6.6.2.3 | Triggering Event ..... | 28 |
+
+6.6.2.3.1 From-state..... 28
+6.6.2.3.2 To-state..... 28
+**Annex A (informative): Change history..... 29**
+
+# --- Foreword
+
+This Technical Specification (TS) 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+TS 32.331 "Notification Log (NL) Integration Reference Point (IRP): Requirements"
+
+**TS 32.332 "Notification Log (NL) Integration Reference Point (IRP): Information Service (IS)"**
+
+TS 32.336 "Notification Log (NL) Integration Reference Point (IRP); Solution Set (SS) definitions"
+
+The present document describes the requirements and information model necessary for Telecommunication Management (TM). The TM principles and TM architecture are specified in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+A communications system is composed of a multitude of Network Elements (NE) of various types and, typically, different vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users' communication requirements.
+
+The occurrence of faults in an NE may cause deterioration or loss of this NE's function. Fault Management is the functional area, which allows the operator to detect the occurrence of faults in the network in real-time. Configuration Management and Performance Management are two more functional areas, which require the operator to be alerted to certain conditions in the network.
+
+A standard general-purpose mechanism for the management of logs containing selected notifications from the network is required to provide an ability to perform historical analysis on faults and conditions, which occurred in the network. The TS 32.33x-series, constituting the Notification log IRP, sets forth such a mechanism - and the present document contains the IS definition.
+
+# --- 1 Scope
+
+The present document specifies the Information Service for the Notification Log Integration Reference Point (NLIRP) as it applies to Itf-N.
+
+This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
+
+# --- 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [5] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+- [6] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [7] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements".
+- [8] 3GPP TS 32.342 "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
+- [9] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.111-2 [5] and 3GPP TS 32.331 [7] apply.
+
+**notification category:** it refers to the set of notifications of one 3GPP IRP Information Service specification
+A Notification Category is identified by the name of the IRP specification and the IRP specification version number.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|----------------------------------------------|
+| DN | Distinguished Name |
+| EM | Element Manager |
+| FT | File Transfer |
+| IOC | Information Object Class |
+| IRP | Integration Reference Point |
+| M | Mandatory |
+| NE | Network Element |
+| NL | Notification Log |
+| NLIRP | Notification Log Integration Reference Point |
+| NM | Network Manager |
+| O | Optional |
+| UML | Unified Modelling Language |
+
+# 4 System overview
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [9] clause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below
+
+
+
+Figure 4.1: System Context A. A block diagram showing the system context for the present IRP. On the left, a box labeled 'IRPManager' is associated with 'NM' (Network Manager). On the right, a box labeled 'IRPAgent' is associated with 'EM' (Element Manager). A solid line connects the IRPManager and the IRPAgent. A dashed vertical line separates the IRPManager and IRPAgent from a box labeled 'NEs' (Network Elements) on the far right. Below the IRPAgent, a curved arrow labeled 'Itf-N' points to a list of three IRPs: 'Notification IRP', 'Notification Log IRP', and 'File Transfer IRP'.
+
+Figure 4.1: System Context A
+
+
+
+Figure 4.2: System Context B. A block diagram showing the system context for the present IRP. On the left, a box labeled 'IRPManager' is associated with 'NM' (Network Manager). On the right, a box labeled 'IRPAgent' is associated with 'NE' (Network Element). A solid line connects the IRPManager and the IRPAgent. A dashed vertical line separates the IRPManager and IRPAgent from the 'NE' box on the far right. Below the IRPAgent, a curved arrow labeled 'Itf-N' points to a list of three IRPs: 'Notification IRP', 'Notification Log IRP', and 'File Transfer IRP'.
+
+Figure 4.2: System Context B
+
+## 4.2 Compliance rules
+
+For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for *operations, notifications and parameters* (of operations and notifications) please refer to 3GPP TS 32.102 [2].
+
+# --- 5 Information Object Classes (IOCs)
+
+## 5.1 Information entities imported and local labels
+
+| Label reference | Local label |
+|---------------------------------------------------------------------------|-----------------------------|
+| 3GPP TS 32.622 [4], information object class, Top | Top |
+| 3GPP TS 32.312 [6], information object class, ManagedGenericIRP | ManagedGenericIRP |
+| 3GPP TS 32.342 [8], information object class, FileTransferIRP | FileTransferIRP |
+| 3GPP TS 32.302 [3], information object class, NotificationIRP | NotificationIRP |
+| 3GPP TS 32.302 [3], information object class, NotificationIRPNotification | NotificationIRPNotification |
+
+## 5.2 Class diagram
+
+### 5.2.1 Attributes and relationships
+
+This clause introduces the set of IOCs that encapsulate information within the IRP Agent. The intent is to identify the information required for NLIRP operations and notification. This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes.
+
+
+
+```
+
+classDiagram
+ class NLIRP {
+ maxLogs
+ }
+ class Log {
+ logSubscriptionId
+ loggingEndTime
+ maxSize
+ currentSize
+ creationTime
+ logState
+ logRecordCount
+ notificationCategories
+ filter
+ logFullAction
+ occupancyLevels
+ logManagerToken
+ }
+ class LogRecord {
+ logRecordId
+ logRecordContent
+ }
+ class NotificationIRPNotification {
+ notificationId
+ eventTime
+ systemDN
+ notificationType
+ }
+ NLIRP "1" --> "0..*" Log : <<names>>
+ Log "1" --> "0..*" LogRecord : relation-log-logRecord
+ LogRecord "1" --> "1" NotificationIRPNotification : relation-logRecord-notification
+
+```
+
+UML Class diagram showing four classes: NLIRP, Log, LogRecord, and NotificationIRPNotification. NLIRP has attribute maxLogs and is associated with Log via a directed association named <> with a 0..\* multiplicity. Log has attributes logSubscriptionId, loggingEndTime, maxSize, currentSize, creationTime, logState, logRecordCount, notificationCategories, filter, logFullAction, occupancyLevels, and logManagerToken. Log is associated with LogRecord via a directed association named relation-log-logRecord with a 1 to 0..\* multiplicity. LogRecord has attributes logRecordId and logRecordContent. LogRecord is associated with NotificationIRPNotification via a directed association named relation-logRecord-notification with a 1 to 1 multiplicity. NotificationIRPNotification (from TS32.302) has attributes notificationId, eventTime, systemDN, and notificationType.
+
+Figure 5.1: Information Object Class (IOC) UML diagram
+
+To change: change logid, add logrecordcontent, remove logrecordsource.
+
+### 5.2.2 Inheritance
+
+
+
+```
+classDiagram
+ class ManagedGenericIRP["ManagedGenericIRP (from TS32.312)"]
+ class NLIRP["<<InformationObjectClass>> NLIRP"] {
+ maxLogs
+ }
+ class Top["<<InformationObjectClass>> Top (from TS32.622)"] {
+ objectClass
+ objectInstance
+ }
+ class Log["<<InformationObjectClass>> Log"] {
+ logSubscriptionId
+ loggingEndTime
+ maxSize
+ currentSize
+ creationTime
+ logState
+ logRecordCount
+ notificationCategories
+ filter
+ logFullAction
+ occupancyLevels
+ logManagerToken
+ }
+ class LogRecord["<<InformationObjectClass>> LogRecord"] {
+ logRecordId
+ logRecordContent
+ }
+ ManagedGenericIRP <|-- NLIRP
+ Top <|-- Log
+ Top <|-- LogRecord
+```
+
+UML diagram showing Information Object Class (IOC) inheritance. ManagedGenericIRP (from TS32.312) is the base class for NLIRP (maxLogs). Top (from TS32.622) with attributes objectClass and objectInstance is the base class for Log and LogRecord. Log has attributes: logSubscriptionId, loggingEndTime, maxSize, currentSize, creationTime, logState, logRecordCount, notificationCategories, filter, logFullAction, occupancyLevels, logManagerToken. LogRecord has attributes: logRecordId, logRecordContent.
+
+Figure 5.2: Information Object Class (IOC) inheritance UML diagram
+
+## 5.3 Information Object Class (IOC) definitions
+
+### 5.3.1 NLIRP
+
+#### 5.3.1.1 Definition
+
+LogIRP is the representation of the notification log management capabilities specified by the present document. This IOC inherits from ManagedGenericIRP IOC specified in TS 32.312 [6].
+
+#### 5.3.1.2 Attributes
+
+| Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
+|----------------|-------------------|----------------|-----------------|
+| maxLogs | O | M | – |
+
+### 5.3.2 Log
+
+#### 5.3.2.1 Definition
+
+The Log IOC is the representation of a Notification Log.
+
+#### 5.3.2.2 Attributes
+
+| Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
+|------------------------|-------------------|----------------|-----------------|
+| logSubscriptionId | M | M | – |
+| loggingEndTime | O | M | – |
+| logManagerToken | O | – | – |
+| maxSize | O | M | – |
+| currentSize | O | M | – |
+| creationTime | O | M | – |
+| logState | M | M | – |
+| logRecordCount | O | M | – |
+| notificationCategories | O | M | – |
+| filter | O | M | – |
+| logFullAction | M | M | – |
+| occupancyLevels | M | M | – |
+
+#### 5.3.2.3 State diagram
+
+
+
+```
+
+stateDiagram-v2
+ [*] --> logging : startLog
+ logging --> logging : occupancyLevelChanged
+ logging --> logWrapping : logFull[ logFullAction==wrap ]
+ logging --> stopped : stopLog || logLifeTimeExpired
+ logging --> logHalted : logFull[ logFullAction==halt ]
+ logWrapping --> logging : stopLog || logLifeTimeExpired
+ logWrapping --> stopped : stopLog || logLifeTimeExpired
+ logHalted --> logging : logNotFull / notifyLoggingResumed()
+ logHalted --> stopped : stopLog || logLifeTimeExpired
+ stopped --> [*]
+
+```
+
+State diagram for Notification Log showing states: logging, logWrapping, stopped, and logHalted with transitions between them.
+
+Figure 5.3: State diagram for Notification Log
+
+The disposition of a log that has been stopped, that is, whether the log remains visible across the Itf-N, is left as vendor specific functionality. The time of the deletion of logs is vendor specific.
+
+### 5.3.3 LogRecord
+
+#### 5.3.3.1 Definition
+
+The LogRecord IOC is the representation of an individual Notification Log Record.
+
+| Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
+|------------------|-------------------|----------------|-----------------|
+| logRecordId | M | M | - |
+| logRecordContent | O | M | - |
+
+## 5.4 Information relationship definitions
+
+### 5.4.1 Relation-nLIRP-log (M)
+
+#### 5.4.1.1 Definition
+
+This represents the relationship between NLIRP and the Log.
+
+#### 5.4.1.2 Role
+
+| Name | Definition |
+|-------|--------------------------|
+| nLIRP | It represents the NLIRP. |
+| log | It represents the Log. |
+
+#### 5.4.1.3 Constraint
+
+| Name | Definition |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| uniqueLogSubscriptionId | The log subscription id must be unique amongst all logs managed by a given NLIRP instance. |
+| uniqueLogManagerToken | The log manager token must be unique amongst all managers and logs utilizing logging services from a given NLIRP instance. |
+
+### 5.4.2 Relation-log-logRecord (M)
+
+#### 5.4.2.1 Definition
+
+This represents the relationship between Log and the LogRecord.
+
+#### 5.4.2.2 Role
+
+| Name | Definition |
+|-----------|------------------------------|
+| log | It represents the Log. |
+| logRecord | It represents the LogRecord. |
+
+#### 5.4.2.3 Constraint
+
+| Name | Definition |
+|-------------------|-------------------------------------------------------------------------------|
+| uniqueLogRecordId | The log record id must be unique amongst all logs records within a given log. |
+
+### 5.4.3 Relation-logRecord-notificationIRPNotification (M)
+
+#### 5.4.3.1 Definition
+
+This represents the relationship between `LogRecord` and the notification header represented by `NotificationIRPNotification`.
+
+#### 5.4.3.2 Role
+
+| Name | Definition |
+|---------------------------|--------------------------------------------------------------|
+| <code>logRecord</code> | It represents the <code>LogRecord</code> . |
+| <code>notification</code> | It represents the <code>NotificationIRPNotification</code> . |
+
+#### 5.4.3.3 Constraint
+
+| Name | Definition |
+|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logRecordIdRelatesNotificationId</code> | Within a given log, there is a one-to-one relationship between <code>Notification Id</code> and <code>Log Id</code> (as each notification can only be recorded once). |
+
+## 5.5 Information attribute definition
+
+### 5.5.1 Definition and legal values
+
+| Attribute Name | Definition | Legal Values |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| creationTime | The time when the log is created. | YYYYMMDDhhmmss |
+| currentSize | This attribute provides the number of bytes currently utilized by a given log. When taken in conjunction with maxSize, the amount of space remaining in the log can be determined. | Either:<br>- zero<br>- a positive whole number |
+| filter | It specifies a filter constraint that IRPAgent shall use to filter notification of the category specified in notificationCategories parameter.<br>Support of time based filter is mandatory. Support of other filter constraints is optional. | Filter constraint grammar is SS dependent |
+| logFullAction | Indicate the action that will be taken by this instance of NLIRP when the Log.maxSize has been reached. | An ENUM that can have one of the following values:<br>- wrap: The oldest LogRecord(s) in the Log, based on the log time, will be deleted to free resources for the logging of new LogRecord(s).<br>- halt: No more LogRecord(s) will be logged and all incoming events are discarded. LogRecord/s already in the Log will be retained. |
+| loggingEndTime | Defines the date and time when the log stops logging. | If log is created by IRPManager:<br>o value provided by the IRP Manager - the IRP Agent may reject the value provided by the IRP Manager in case this value is excessive<br>o in case no value is provided by the IRP Manager then this value is set by the IRP Agent.<br><br>If log is created by IRPAgent:<br>o value indicates date and time or<br>o value is expressed as "indefinite". |
+| logManagerToken | This attribute contains the token of a manager utilizing logging services from a given NLIRP instance, assigned by the IRPAgent. | The value of this attribute must be unique amongst all managers and logs utilizing logging services from the given NLIRP instance. |
+| logRecordContent | The notification information of a log record, excluding the notification header information. | The content format varies depending on the type of the notification. |
+| logRecordCount | The number of log records currently logged within a given log. | positive whole number, including zero |
+| logRecordId | This attribute contains the id of a log record within a given log, assigned by the IRPAgent. | The value of this attribute must be unique amongst all log record contained by a given log. |
+| logState | Provides an indication of the current state of a specific log | An ENUM that can have one of the following values:<br>o logging<br>o logFull<br>o stopped |
+| logSubscriptionId | This attribute contains the id of a log subscription within a given NLIRP instance, assigned by the IRPAgent. | The value of this attribute must be unique amongst all log subscriptions managed by a given NLIRP instance. |
+| maxLogs | Defines the maximum number of logs that can be supported by a given Notification Log IRP, assigned by the IRPAgent. | Non-zero, positive whole number |
+| maxSize | This attribute defines the maximum number of bytes that may be utilized by a given log, assigned by the IRPAgent. | Either:<br>o Non-zero, positive whole number<br>o Zero indicates no limit on the number of records is set by the IRPAgent (log full handling will provide limitation information) |
+| notificationCategories | Specifies the notification categories that can be recorded within a given log - SET OF (name of IRP, version of IRP) | It identifies one or more Notification Category (see also Definition in clause 3.1) |
+| occupancyLevels | Case Log.logFullAction == 'halt' and Log.maxSize is non-zero:<br>o this attribute contains a list of 3 values fixed (determined by the IRPAgent and never changed) of percentage, of Log.maxLog<br>o the NLIRP will generate notifyOccupancyLevelCrossed to alert IRPManagers about the Log capacity currently used.<br><br>Case Log.logFullAction == 'wrap':<br>o this attribute contains 1 value fixed (determined by the IRPAgent and never changed) of percentage of Log.maxLog<br>the NLIRP will generate notifyOccupancyLevelCrossed to alert IRPManagers that the specified percentage of the capacity has been written to the wrapping Log. | Case of 'halt': a set of 3 values.<br><br>Case of 'wrap': 1 value. |
+
+### 5.5.2 Constraints
+
+| Name | Definition |
+|----------------------|---------------------------------------------------------------|
+| inv_lastModifiedTime | Time indicated shall be greater than or equal to creationTime |
+| inv_logRecordCount | Number indicated shall be less than or equal to maxSize |
+
+# 6 Interface definition
+
+## 6.1 Class diagram
+
+
+
+```
+
+classDiagram
+ class NLIRPOperations_1 {
+ <<Interface>>
+ subscribeLog()
+ unsubscribeLog()
+ <<optional>> exportLogRecords()
+ <<optional>> getLogRecords()
+ }
+ class NLIRPOperations_2 {
+ <<Interface>>
+ getLogSubscriptionIds()
+ getLogSubscriptionStatus()
+ }
+ class NLIRP {
+ <<InformationObjectClass>>
+ maxLogs
+ }
+ class NLIRPNotifications_1 {
+ <<Notification>>
+ notifyLogSubscribed()
+ notifyLogUnsubscribed()
+ }
+ class NLIRPNotifications_2 {
+ <<Notification>>
+ notifyOccupancyLevelCrossed()
+ <<optional>> notifyLoggingResumed()
+ }
+ class FileTransferIRP {
+ FileTransferIRP (from TS32.342)
+ }
+ class NotificationIRP {
+ <<InformationObjectClass>>
+ NotificationIRP (from TS32.302)
+ }
+
+ NLIRP ..|> NLIRPOperations_1
+ NLIRP --> NLIRPOperations_2 : <<may realize>>
+ NLIRP --> NLIRPNotifications_1 : <<use>>
+ NLIRP --> NLIRPNotifications_2 : <<may use>>
+ NLIRP ..|> FileTransferIRP : <<agent-internal-usage>>
+ NLIRPNotifications_1 ..|> NotificationIRP : <<agent-internal-usage>>
+ NLIRPNotifications_2 ..|> NotificationIRP : <<agent-internal-usage>>
+
+ note for NLIRPOperations_1 "NLIRPOperations_1 shall support either operation exportLogRecords or operation getLogRecords as mandatory."
+
+```
+
+The class diagram illustrates the relationships between the NLIRP class and various interfaces and notifications. The NLIRP class implements the NLIRPOperations\_1 interface and may realize the NLIRPOperations\_2 interface. It uses the NLIRPNotifications\_1 and NLIRPNotifications\_2 notifications. The NLIRP class also has an agent-internal usage relationship with the FileTransferIRP and NotificationIRP classes. The NLIRPNotifications\_1 and NLIRPNotifications\_2 notifications have an agent-internal usage relationship with the NotificationIRP class. A note indicates that the NLIRPOperations\_1 interface shall support either the exportLogRecords or getLogRecords operation as mandatory.
+
+UML Class diagram showing NLIRP class and its associated interfaces and notifications.
+
+**Figure 6.1: Class diagram**
+
+NLIRPOperations\_1 shall support either operation exportLogRecords or operation getLogRecords as mandatory.
+
+## 6.2 Generic rules
+
+- Rule 1:** Each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+- Rule 2:** Each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+- Rule 3:** Each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 NLIRPOperations\_1 Interface (M)
+
+### 6.3.1 Operation subscribeLog (M)
+
+#### 6.3.1.1 Definition
+
+Using this operation, an IRPManager is initiating the logging of notifications. Resulting from this operation an IRPAgent shall start logging of notifications and, if necessary, also create an associated log.
+
+#### 6.3.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|-------------------------------------|-----------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logSubscriptionId</code> | M | <code>Log.logSubscriptionId</code> | See clause 5.5.1<br>If empty, then IRPAgent shall create a new log and return the <code>logSubscriptionId</code> as output parameter. However not all IRPAgents will provide this capability, i.e. IRPManager must provide an existing <code>logSubscriptionId</code> . |
+| <code>loggingEndTime</code> | O | <code>Log.loggingEndTime</code> | See clause 5.5.1 |
+| <code>notificationCategories</code> | O | <code>Log.notificationCategories</code> | See clause 5.5.1; if <code>notificationCategories</code> is absent than all notifications are logged |
+| <code>filter</code> | O | <code>Log.ntfFilterfilter</code><br>Filter constraint grammar is SS dependent | See clause 5.5.1; if this parameter is absent, then no filter constraint shall be applied. |
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-------------------|-----------|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionId | M | Log.logSubscriptionId | See clause 5.5.1<br>This parameter contains either <ul style="list-style-type: none"> <li>the logSubscriptionId of the log created resulting from this operation or</li> <li>the value of the input parameter logSubscriptionId.</li> </ul> |
+| logManagerToken | O | Log.logManagerToken | See clause 5.5.1<br>See also comment 6.3.2.2.<br>Note: Security Management IRP may provide capabilities that make this parameter redundant. |
+| loggingEndTime | O | Log.loggingEndTime | See clause 5.5.1<br>If supported by the Log IOC (5.3.2) and not already provided by the IRP Manager then the output of this operation must support this parameter. |
+| status | M | ENUM<br>(OperationSucceeded, OperationFailed) | If loggingEndTime is valid and notificationCategories is valid or absent, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed.<br>If loggingEndTime excessive, status = OperationFailed. |
+
+#### 6.3.1.4 Pre-condition
+
+logsNotMaxed
+
+| Assertion Name | Definition |
+|----------------|---------------------------------------------------------------------|
+| logsNotMaxed | The number of logs is less than the maximum number of logs allowed. |
+
+#### 6.3.1.5 Post-condition
+
+logStarted
+
+| Assertion Name | Definition |
+|----------------|--------------------------------------------------------------------------------------------|
+| logStarted | A log is started with the specified characteristics (lifetime and notificationCategories). |
+
+#### 6.3.1.6 Exceptions
+
+| Exception Name | Definition |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionId_required | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+| maxLogs_reached | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.2 Operation unsubscribeLog (M)
+
+#### 6.3.2.1 Definition
+
+Using this operation, the IRPManager that started a specific log is able to stop this log via unsubscribing. Note stopping a log implies that the log becomes invisible across Itf-N, independent from the loggingEndTime; therefore the IRPManager should retrieve log information of interest before using this unsubscribeLog operation, e.g. through the exportLogRecords operation.
+
+The disposition of a log that has been stopped, that is, whether the log remains visible across the Itf-N, is left as vendor specific functionality. The time of the deletion of logs is vendor specific.
+
+In consideration of a multi-manager environment, the log can only be stopped by the creating IRPManager if this IRPManager provided a related token while initiating subscribeLog.
+
+#### 6.3.2.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|-------------------|-----------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionId | M | Log.logSubscriptionId | See clause 5.5.1 |
+| logManagerToken | O | Log.logManagerToken | See clause 5.5.1<br>If subscribeLog returned a logManagerToken for a log with logSubscriptionId="X", then logManagerToken must be provided as input parameter of this operation to successfully stop log with logSubscriptionId="X".<br><br>If subscribeLog did not return a logManagerToken for a log with logSubscriptionId="X", then logManagerToken must contain NULL value to successfully stop log with logSubscriptionId="X". |
+
+#### 6.3.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| status | M | ENUM (OperationSucceeded, OperationFailed) | If logSubscriptionId is valid and logManagerToken (if supported) is matching, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.3.2.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.3.2.5 Post-condition
+
+logStopped
+
+| Assertion Name | Definition |
+|----------------|-------------------------------|
+| logStopped | The specified log is stopped. |
+
+#### 6.3.2.6 Exceptions
+
+| Exception Name | Definition |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.3 Operation exportLogRecords (O)
+
+Support for this operation is mandatory if getLogRecords is not supported.
+
+#### 6.3.3.1 Definition
+
+Using this operation, an IRPManager can initiate export of all or part of a log into a file. This file then is being transferred to the IRPManager using the File Transfer IRP (note also that the FTIRP is providing the file location to the IRPManager).
+
+#### 6.3.3.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|------------------------|-----------|----------------------------|------------------|
+| logSubscriptionId | M | Log.logSubscriptionId | See clause 5.5.1 |
+| notificationCategories | O | Log.notificationCategories | See clause 5.5.1 |
+| filter | O | Log.filterLog.filter | See clause 5.5.1 |
+
+#### 6.3.3.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| invocationId | M | -- | <p>This parameter carries an identifier that NLIRP assigns to identify the request if the status is OperationSucceeded. This parameter carries no information if the status is not OperationSucceeded.</p> <p>One identifier can at most identify one request. NLIRP should not reuse identifier values.</p> <p>This identifier shall also appear in the file name of the exported log file as <specificIRP_extension> (as part specified in Appendix A: File Name Convention of [8]).</p> <p>When the exported log file is ready, FTIRP issues notifyFileReady notification which carries the exported log file name.</p> |
+
+#### 6.3.3.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.3.3.5 Post-condition
+
+logRecordsExported
+
+| Assertion Name | Definition |
+|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logRecordsExported | The specified log records have been exported as requested. In case the log is empty or in case that all the log records do not satisfy the criteria of input parameters notificationCategories and filter, this post-condition is true. |
+
+#### 6.3.3.6 Exceptions
+
+| Exception Name | Definition |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| export_failed | The NLIRP was unable to export the specified records. |
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.4 Operation `getLogRecords` (O)
+
+Support for these operations is mandatory if `exportLogRecords` is not supported.
+
+#### 6.3.4.1 Definition
+
+Using this operation, an IRPManager can retrieve one or more log records from a certain log.
+
+Note that this operation might be preferred for retrieval of small amounts of log records, while operation `exportLogRecords` might be preferred for retrieval of medium to large amounts of log records, as providing a more efficient bulk transfer mechanism.
+
+#### 6.3.4.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|-------------------------------------|-----------|-----------------------------------------|------------------|
+| <code>logSubscriptionId</code> | M | <code>Log.logSubscriptionId</code> | See clause 5.5.1 |
+| <code>notificationCategories</code> | O | <code>Log.notificationCategories</code> | See clause 5.5.1 |
+| <code>filter</code> | O | <code>Log.filter</code> | See clause 5.5.1 |
+
+#### 6.3.4.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------------------------|-----------|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>getLogRecordsResult</code> | M | List of <code>logRecord</code> 's | List of <code>logRecords</code> ; each entry of the list holds all supported attributes of <code>IOC LogRecord</code> (see 5.3.3.2). |
+| <code>status</code> | M | ENUM ( <code>OperationSucceeded</code> , <code>OperationFailed</code> ) | If <code>logSubscriptionId</code> is valid and ( <code>logRecordIdList</code> is empty or <code>logRecordIdList</code> contains valid Id's), <code>status</code> = <code>OperationSucceeded</code> .<br>If <code>operation_failed</code> is true, <code>status</code> = <code>OperationFailed</code> . |
+
+#### 6.3.4.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.3.4.5 Post-condition
+
+`logRecordsRetrieved`
+
+| Assertion Name | Definition |
+|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>logRecordsRetrieved</code> | The specified log records have been retrieved as requested. If the log is empty or all the log records do not satisfy the criteria of input parameters <code>notificationCategories</code> and <code>filter</code> , this post-condition is true. |
+
+#### 6.3.4.6 Exceptions
+
+| Exception Name | Definition |
+|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>operation_failed</code> | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter <code>status</code> .<br><b>Exit state:</b> Entry state. |
+
+## 6.4 NLIRPOperations\_2 Interface (O)
+
+### 6.4.1 Operation getLogSubscriptionIds (M)
+
+#### 6.4.1.1 Definition
+
+Using this operation, an IRPManager can query the NLIRP for all available log subscriptions.
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|----------------|-----------|------------------|---------|
+| -- | -- | -- | -- |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|--------------------|-----------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| logSubscriptionIds | M | List of logSubscriptionId's | See clause 5.5.1 & 6.4.1.2.<br>Note that empty list is a valid value. |
+| status | M | ENUM (OperationSucceeded, OperationFailed) | If operation is successful, status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.4.1.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.4.1.5 Post-condition
+
+There are no post-conditions. Querying of log subscription Id's does not result in any changes within the IRP Agent.
+
+#### 6.4.1.6 Exceptions
+
+| Exception Name | Definition |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.4.2 Operation getLogSubscriptionStatus (M)
+
+#### 6.4.2.1 Definition
+
+Using this operation, an IRPManager can query the NLIRP for available log status information of an individual log.
+
+#### 6.4.2.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|-------------------|-----------|-----------------------|------------------|
+| logSubscriptionId | M | Log.logSubscriptionId | See clause 5.5.1 |
+
+#### 6.4.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|------------------|-----------|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| logAttributeList | M | Attributes of related Log IOC except logManagerToken | List of all supported attributes of IOC Log except logManagerToken (see clause 5.3.2.2). |
+| status | M | ENUM (OperationSucceeded, OperationFailed) | If logSubscriptionId is valid status = OperationSucceeded.<br>If operation_failed is true, status = OperationFailed. |
+
+#### 6.4.2.4 Pre-condition
+
+There are no pre-conditions, other than those established by the generic rules (see clause 6.2).
+
+#### 6.4.2.5 Post-condition
+
+There are no post-conditions. Querying of log attributes does not result in any changes within the IRPAgent.
+
+#### 6.4.2.6 Exceptions
+
+| Exception Name | Definition |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> Pre-condition is true AND post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+## 6.5 NLIRPNotifications\_1 Interface (M)
+
+### 6.5.1 Notification notifyLogSubscribed (M)
+
+#### 6.5.1.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Managers that a log subscription has been successfully initiated.
+
+#### 6.5.1.2 Input Parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|------------------------|-----------|----------------------------|---------------------------------------------------------------------|
+| objectClass | M,Y | Log.objectClass | Notification header - see [3]. It shall carry the Log class name. |
+| objectInstance | M,Y | Log.objectInstance | Notification header - see [3]. It shall carry the DN of Log. |
+| notificationId | M,N | -- | Notification header - see [3]. |
+| eventTime | M,Y | -- | Notification header - see [3]. |
+| notificationType | M,Y | "notifyLogSubscribed" | Notification header - see [3]. |
+| systemDN | C,Y | -- | Notification header - see [3]. |
+| logSubscriptionId | M,N | Log.logSubscriptionId | See clause 5.5.1 |
+| loggingEndTime | O,N | Log.loggingEndTime | See clause 5.5.1 |
+| notificationCategories | O,N | Log.notificationCategories | See clause 5.5.1; if absent than all notifications are being logged |
+| filter | O,N | Log.filter | See clause 5.5.1 |
+
+#### 6.5.1.3 Triggering Event
+
+##### 6.5.1.3.1 From-state
+
+subscribeLog
+
+| Assertion Name | Definition |
+|----------------|----------------------------------------------------|
+| subscribeLog | An IRP Manager requests that a new log be started. |
+
+##### 6.5.1.3.2 To-state
+
+logStarted
+
+| Assertion Name | Definition |
+|----------------|-------------------------------------------------------|
+| logStarted | The NLIRP has started the requested logging activity. |
+
+### 6.5.2 Notification `notifyLogUnsubscribed` (M)
+
+#### 6.5.2.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Manager that a log subscription has stopped.
+
+#### 6.5.2.2 Input Parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-------------------|-----------|-------------------------|--------------------|
+| objectClass | M,Y | Log.objectClass | See table 6.5.1.2. |
+| objectInstance | M,Y | Log.objectInstance | See table 6.5.1.2. |
+| notificationId | M,N | -- | See table 6.5.1.2. |
+| eventTime | M,Y | -- | See table 6.5.1.2. |
+| notificationType | M,Y | "notifyLogUnsubscribed" | See table 6.5.1.2. |
+| systemDN | C,Y | --. | See table 6.5.1.2. |
+| logSubscriptionId | M,N | Log.logSubscriptionId | See table 6.5.1.2. |
+
+#### 6.5.2.3 Triggering Event
+
+##### 6.5.2.3.1 From-state
+
+`unsubscribeLog` OR `loggingEndTimeReached`
+
+| Assertion Name | Definition |
+|------------------------------------|-------------------------------------------------------------------------------------------|
+| <code>unsubscribeLog</code> | The IRP Manager that started the log requests that the log be unsubscribed. |
+| <code>loggingEndTimeReached</code> | The logging end time specified for the log in <code>subscribeLog</code> has been reached. |
+
+##### 6.5.2.3.2 To-state
+
+`logStopped`
+
+| Assertion Name | Definition |
+|-------------------------|-----------------------------------|
+| <code>logStopped</code> | The logging activity has stopped. |
+
+## 6.6 NLIRPNotifications\_2 Interface (O)
+
+### 6.6.1 Notification notifyOccupancyLevelCrossed (M)
+
+#### 6.6.1.1 Definition
+
+Using this notification, an IRPAgent informs all subscribed IRPManagers about the occupancy level of a certain log according with levels defined in 5.5.1 (in addition also the log full action type of this NLIRP instance is being provided for context purposes).
+
+#### 6.6.1.2 Input Parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-----------------------|-----------|-----------------------------------------------------------------------------|--------------------|
+| objectClass | M,Y | Log.objectClass | See table 6.5.1.2. |
+| objectInstance | M,Y | Log.objectInstance | See table 6.5.1.2. |
+| notificationId | M,N | -- | See table 6.5.1.2. |
+| eventTime | M,Y | -- | See table 6.5.1.2. |
+| notificationType | M,Y | "notifyOccupancyLevelCrossed" | See table 6.5.1.2. |
+| systemDN | C,Y | -- | See table 6.5.1.2. |
+| logSubscriptionId | M,Y | Log.logSubscriptionId | See table 6.5.1.2. |
+| currentOccupancyLevel | M,N | The integer portion of $((\text{Log.currentSize}/ \text{Log.maxSize})*100)$ | See clause 5.5.1. |
+| logFullAction | O,N | Log.logFullAction | See clause 5.5.1. |
+
+#### 6.6.1.3 Triggering Event
+
+##### 6.6.1.3.1 From-state
+
+logFull OR occupancyLevelCrossed
+
+| Assertion Name | Definition |
+|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logFull | The log is full, that is, the number of log records contained within the log has exceeded the maximum number of log records that was established at log startup (log capacity has reached 100 %). |
+| occupancyLevelCrossed | The number of log records within the log has crossed one of the threshold boundaries (see 5.5.1 Log.occupancyLevels). |
+
+##### 6.6.1.3.2 To-state
+
+logWrapping OR (logHalted OR logging)
+
+| Assertion Name | Definition |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logWrapping | Applicable for case Log.logFullAction='wrap': The number of log records within the log has exceeded the maximum number of allowed log records (100 % capacity has been crossed). The logging of new records will cause the oldest records within the log to be deleted and replaced (first in, first out). The deletion of records may occur in a block, such that the log transitions back to the "started" state prior to any new records being written. |
+| logHalted | Applicable for case Log.logFullAction='halt': The number of log records within the log has exceeded the maximum number of allowed log records (100 % capacity has been crossed). The logging of new records will be discontinued until the deletion of records has occurred (deletion of records is outside the scope of this IRP). |
+| logging | Applicable for case Log.logFullAction='halt': The number of log records within the log is below the maximum number of allowed records. The generation of the notification is done to inform the subscribed IRPManagers that the log is filling up. |
+
+### 6.6.2 Notification notifyLoggingResumed (O)
+
+#### 6.6.2.1 Definition
+
+Using this notification, an IRP Agent informs all subscribed IRP Managers that the amount of data within a given log has been reduced, allowing logging to resume continue (according to the information provided when the log was created). Note that this notification only applies to Log.logFullAction == 'halt'.
+
+#### 6.6.2.2 Input Parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-------------------|-----------|------------------------|--------------------|
+| objectClass | M,Y | Log.objectClass | See table 6.5.1.2. |
+| objectInstance | M,Y | Log.objectInstance | See table 6.5.1.2. |
+| notificationId | M,N | -- | See table 6.5.1.2. |
+| eventTime | M,Y | -- | See table 6.5.1.2. |
+| notificationType | M,Y | "notifyLoggingResumed" | See table 6.5.1.2. |
+| systemDN | C,Y | -- | See table 6.5.1.2. |
+| logSubscriptionId | M,Y | Log.logSubscriptionId | See table 6.5.1.2. |
+
+#### 6.6.2.3 Triggering Event
+
+##### 6.6.2.3.1 From-state
+
+logFull
+
+| Assertion Name | Definition |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logHalted | The log is full, that is, the number of log records contained within the log has exceeded the maximum number of log records that was established at log startup (log capacity has reached 100 % and Log.logFullAction='halt'). |
+| occupancyLevelCrossed | The number of log records within the log has crossed one of the threshold boundaries (see 5.5.1 Log.occupancyLevels). |
+
+##### 6.6.2.3.2 To-state
+
+| Assertion Name | Definition |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| logging | The number of log records within the log is below the maximum number of allowed records. The generation of the notification is done to inform the subscribed IRP Managers that the log is filling up. |
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------|-----|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
+| Mar 2004 | S_23 | SP-040123 | -- | -- | Submitted to SA#23 for Information | -- | 1.0.0 | |
+| Dec 2004 | S_26 | SP-040798 | -- | -- | Submitted to SA#26 for Approval | -- | 2.0.0 | 6.0.0 |
+| Jun 2005 | S_28 | SP-050290 | 0001 | -- | Correct mapping info of currentOccupancyLevel and some editorial errors | F | 6.0.0 | 6.1.0 |
+| Jun 2005 | S_28 | SP-050329 | 0002 | -- | Apply Generic System Context – Align with TS 32.150 | F | 6.0.0 | 6.1.0 |
+| Mar 2006 | SA_31 | SP-060091 | 0003 | -- | Add invocationId output parameter of exportLogRecords operation | F | 6.1.0 | 6.2.0 |
+| Mar 2006 | SA_31 | SP-060089 | 0004 | -- | Correct ambiguity of object class and object instance usage in notification | F | 6.1.0 | 6.2.0 |
+| Dec 2006 | SA_34 | SP-060709 | 0005 | -- | Correct the errors in the definition of occupancyLevels and currentOccupancyLevel | F | 6.2.0 | 6.3.0 |
+| Jun 2007 | SA_36 | -- | -- | -- | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | -- | 6.3.0 | 7.0.0 |
+| Sep 2007 | SA_37 | SP-070614 | 0006 | -- | Remove the use of visibility symbol | C | 7.0.0 | 8.0.0 |
+| Dec 2009 | - | - | - | - | Update to Rel-9 version (MCC) | - | 8.0.0 | 9.0.0 |
+| Mar 2011 | - | - | - | - | Update to Rel-10 version (MCC) | - | 9.0.0 | 10.0.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | | 10.0.0 | <b>11.0.0</b> |
+| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) | | 11.0.0 | <b>12.0.0</b> |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | <b>13.0.0</b> |
+| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | | 13.0.0 | <b>14.0.0</b> |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-06 | | | | | | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
+| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32361/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-18/32_series/32361/0236eff05bcb8f3a343ea7933aaa306b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ff299dab819aed10bea9db4bdaa24ecdc1aa12d
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/0236eff05bcb8f3a343ea7933aaa306b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad04bf593b2bedf34e06bd0ab1d2a1857e5807c04117f7c7fecbcf458e366f3c
+size 53437
diff --git a/marked/Rel-18/32_series/32361/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-18/32_series/32361/0b87abe67b21a93777287649c33e755d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f6519ac7a3f823839d3785f7eb14ed79dd38d6e
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/0b87abe67b21a93777287649c33e755d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84db1abbbd6024d7b05fc7b66c82b3e5e4651685cc0058449cdb8c91659bc4b6
+size 38713
diff --git a/marked/Rel-18/32_series/32361/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-18/32_series/32361/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7374b2bd4b789cf8ca0c130a222c4b851f9420c
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9c103a236257ddf04d9fce8e242786dde9c92897216b32683a4986a32bfdc392
+size 26623
diff --git a/marked/Rel-18/32_series/32361/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32361/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/32_series/32361/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32361/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a2fa3db597f1f7f282bf6fe11d2de00974828aa
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ee98efc694f62bf3687c2586147c5ae46238996ce18e67416248bac9114a18c
+size 5614
diff --git a/marked/Rel-18/32_series/32361/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-18/32_series/32361/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1bb0d86303e0f97efc65bdec4ae2b49493a6ed7
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b8e3eadde139777211d8b5f0b9644e2734fbf69362962a89ef3e2ad7269deae
+size 34051
diff --git a/marked/Rel-18/32_series/32361/raw.md b/marked/Rel-18/32_series/32361/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f961303b80ece83188be1941f96f9693543c91a8
--- /dev/null
+++ b/marked/Rel-18/32_series/32361/raw.md
@@ -0,0 +1,317 @@
+
+
+# 3GPP TS 32.361 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+UMTS, management
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|----------------------------------------------------|-----------|
+| Foreword ..... | 4 |
+| Introduction ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 Entry Point concept and requirements ..... | 6 |
+| 5 Itf-N interface..... | 8 |
+| 5.1 Entry point..... | 8 |
+| 5.1.1 Access point..... | 8 |
+| 5.1.2 Version negotiation ..... | 8 |
+| 5.1.3 Changes indication ..... | 8 |
+| 5.1.4 Security ..... | 8 |
+| <b>Annex A (informative): EPIRP knowledge.....</b> | <b>9</b> |
+| <b>Annex B (informative): Change history.....</b> | <b>10</b> |
+
+# --- 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
+
+- 32.361: "Entry Point (EP) Integration Reference Point (IRP): Requirements".**
+- 32.362: "Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)".
+- 32.366: "Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions".
+
+The present document is part of a set of technical specifications defining the Telecommunication Management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 [1]. The TM architecture is described in 3GPP TS 32.102 [2]. The other specifications define the interface (Itf-N) between the managing system (manager), which is in general the Network Manager (NM) and the managed system (agent), which is either an Element Manager (EM) or the managed NE itself. The Itf-N is composed of a number of Integration Reference Points (IRPs) defining the information in the agent that is visible for the manager, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. EPIRP is one of these IRPs with special function.
+
+It is difficult for an NM to discover all IRPs in the environment where there are several managed systems and/or if there are multiple IRPs related to each managed system. This Entry Point is proposed to provide a convenient mechanism for NM to discover the managed systems and their related IRPs.
+
+# --- 1 Scope
+
+The present document describes the requirements of the EPIRP.
+
+# --- 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.111-1: "Telecommunication management; Fault management; Part 1: 3G fault management requirements".
+- [4] 3GPP TS 32.601: " Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Requirements".
+- [5] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**Entry Point (EP):** access point between NM and the managed systems and provides the way for NM to discover the References of IRPs in the managed systems
+
+**Reference:** defines the IRP network management service access point. The IRPManagers connect to this IRP Reference in order to request and obtain the network management services (provided by that IRP). The implementation of IRP Reference is technology dependent. For example, in CMIP, this is the address of the CMIP IRP Agent and application context of the CMIP IRP. In CORBA, this is the IOR of the IRP contained by the IRP Agent.
+
+**Version negotiation:** when the managed system supports more than one IRP versions, there is a mechanism for NM to select the needed IRP version, and invoke the most appropriate management operations
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|-------------------------------------------|
+| CM | Configuration Management |
+| CORBA | Common Object Request Broker Architecture |
+| DN | Distinguished Name |
+| EP | Entry Point |
+| EPIRP | Entry Point IRP |
+| EM | Element Manager |
+| EP | Entry Point |
+| IOC | Information Object Class |
+| IOR | (CORBA) Interoperable Object Reference |
+| IRP | Integration Reference Point |
+| NE | Network Element |
+| NM | Network Manager |
+| NRM | Network Resource Model |
+| PM | Performance Management |
+
+# 4 Entry Point concept and requirements
+
+In the 3GPP Release 5 specifications and earlier Releases, the IRPs (such as the Basic CM IRP Requirements in 3GPP TS 32.601 [4], the fault management requirements in 3GPP TS 32.111-1 [3], etc.) are defined for specific management domains and are all published. 3GPP specifications do not provide standard mechanism for NM to discover the References of the IRPs in the managed systems. The discovery is a vendor-specific matter.
+
+In a large network, multiple IRPs, providing different network management domains services exist. Multiple IRPs providing the same network management services (e.g. fault management) but of different management scope may exist (e.g. one AlarmIRP managing the eastern region while another AlarmIRP manages the western region). It's difficult and fallible for an NM to discover all of them. The matter is further complicated in a multi-vendor environment where each vendor provides different way for NM to discover the References of its IRP Agent and related IRPs.
+
+A management service, allowing the NM to discover the References, in a standard way would eliminate the NM's difficulties mentioned above. The Entry Point is the name of such management service.
+
+Entry Point provides the following:
+
+- 1) It allows NM to discover outline information of IRPs, including the DN of IRPs and the supported IRP Versions and their scope of management (e.g. the set of network resources that it is responsible for) in the managed systems.
+- 2) It supports NM to obtain the References of the IRPs of specific IRP Version by means of the IRP Manager inputting the DN of the IRP which supports the IRP Version number it needs. Entry Point allows NM to indicate to the managed system the References it will not use again. Whether the managed system should release them or not is outside the scope of this specification.
+
+A notification shall be supported for keeping IRP Manager timely informed about the changes of Entry Point contents, e.g. latest IRP Agent register information or latest IRP Agent deregister information or their scope of management stored in EPIRP at run time.
+
+The EPIRP provides the References of various IRPs to the IRP Manager at run time. That interaction, to be standardised by this IRP specification, is shown as the arrow from EPIRP to IRP Manager in the Figure 1. Using the provided Reference, say the Reference to PMIRP, the IRP Manager invokes operations to access the PM domain specific management services.
+
+The context diagram figure 1 does not show the IRP Agent(s) and their containment relations with IRPs. There can be a single or multiple IRP Agents. Each IRP Agent can contain one or more IRPs.
+
+An EPIRP is contained by an IRP Agent. This containing IRP Agent may or may not contain other instances of other IRPs such as AlarmIRP. This is the choice of the vendor producing such product.
+
+The IRP Agent containment relation, with respect to other IOCs such as SubNetwork, is defined by the Generic NRM IRP in 3GPP TS 32.622 [5]. This containment relation has no relation to the EPIRP knowledge regarding IRP
+
+References. To say it in another way, the EPIRP knowledge about IRP References has no relationship to its Distinguished Name. An EPIRP, named under one IRP Agent instance can have knowledge of IRP References of IRPs named under other IRP Agent instances. An EPIRP, named under one particular SubNetwork instance can have knowledge of IRP References of IRPs under other SubNetwork instances. This is the choice of the vendor producing such product. See annex A for example figures to show EPIRP knowledge.
+
+All the IRP References provided by one vendor's product should be found in at least in one of the EPIRPs implemented by that vendor, but not necessarily all IRP References in one EPIRP. Each vendor should minimize the number of EPIRPs for the support of all their IRP References.
+
+How EPIRP is made aware of IRP References are outside the scope of standardization.
+
+
+
+```
+graph TD; subgraph Itf-N; direction LR; IRPManager[IRPManager] --- AlarmIRP[AlarmIRP]; IRPManager --- PerfMgr[Performance Management IRP]; IRPManager --- ConfigMgr["Configuration (Basic, Bulk) Management IRP"]; end; NM[NM] --- IRPManager; EPIRP[EPIRP] -.->|*| IRPManager;
+```
+
+Diagram illustrating the EPIRP context. A central box labeled 'IRPManager' is connected to three boxes on the right: 'AlarmIRP', 'Performance Management IRP', and 'Configuration (Basic, Bulk) Management IRP'. These connections are labeled 'Itf-N'. Below the IRPManager box is a label 'NM'. At the bottom, a box labeled 'EPIRP' is connected to the IRPManager box via a dashed line with an asterisk (\*).
+
+NOTE: The '\*' depicts the IRP Reference returned by EPIRP. See Reference definition.
+
+Figure 1: EPIRP context
+
+# --- 5 Itf-N interface
+
+## 5.1 Entry point
+
+### 5.1.1 Access point
+
+Before IRPManager can interact with an IRP to obtain network management services, say AlarmIRP, it must know the IRP's Reference.
+
+Without the EPIRP, the IRPManager shall get information about these IRP References in a vendor-specific way.
+
+With the EPIRP, the IRPManager can discover these IRP References using the EPIRP defined protocol.
+
+Before the IRPManager can interact with the EPIRP, it must know the EPIRP Reference. How the IRPManager acquire this knowledge is outside the scope of this specification.
+
+### 5.1.2 Version negotiation
+
+The version of IRPs may be updated for some appropriate reasons. Version negotiation means that when a managed system supports several versions of one IRP, there is a mechanism for NM to select the needed IRP version, and invoke the most appropriate management operations.
+
+In order to support version negotiation, the procedure for NM to achieve IRP References can be divided into two steps. First, the managed system provides the outline information of the IRPs it supports, including DNs of the IRPs, versions of IRPs and their scope of management. Second, the NM obtains the Reference of the IRP of specific version by inputting the DN of the IRP which supports the version number it needs.
+
+### 5.1.3 Changes indication
+
+When the References or their scope of management of IRPs contained in IRPAgent changed (create, delete or modified), the relative information shall be reflected in EPIRP.
+
+In addition, a notification shall be supported for keeping IRPManager timely informed about the changes of Entry Point contents, e.g. latest IRPAgent register information (e.g. IRP Reference) or latest IRPAgent deregister information or their scope of management stored in EPIRP at run time.
+
+### 5.1.4 Security
+
+As an access point between NM and managed system, Entry Point needs security guarantee on its access and the EP contents.
+
+**Editor's note:** Other requirements to be added (FFS).
+
+# Annex A (informative): EPIRP knowledge
+
+Figures A.1 to A.3 give the possible solutions to show EPIRP knowledge about all the products of one vendor.
+
+
+
+```
+
+graph TD
+ SN1((SubNetwork1)) --- IA1((IRPAgent1))
+ SN1 --- IA2((IRPAgent2))
+ IA1 --- EPIRP1((EPIRP1))
+ IA1 --- PMIRP1((PMIRP1))
+ IA2 --- AlarmIRP1((AlarmIRP1))
+ IA2 --- EPIRP2((EPIRP2))
+ EPIRP1 -.- KL1[EPIRP1 Know ledge:
+- PMIRP1 Outline]
+ EPIRP2 -.- KL2[EPIRP2 Know ledge:
+- AlarmIRP1 Outline]
+
+```
+
+Figure A.1: EPIRP knowledge 1. A tree diagram showing SubNetwork1 at the top, connected to IRPAgent1 and IRPAgent2. IRPAgent1 is connected to EPIRP1 and PMIRP1. IRPAgent2 is connected to AlarmIRP1 and EPIRP2. Two knowledge boxes are shown: EPIRP1 Know ledge: - PMIRP1 Outline, and EPIRP2 Know ledge: - AlarmIRP1 Outline.
+
+Figure A.1: EPIRP knowledge 1
+
+
+
+```
+
+graph TD
+ SN1((SubNetwork1)) --- IA1((IRPAgent1))
+ SN1 --- IA2((IRPAgent2))
+ IA1 --- EPIRP1((EPIRP1))
+ IA1 --- PMIRP1((PMIRP1))
+ IA2 --- AlarmIRP1((AlarmIRP1))
+ SN2((SubNetwork2)) --- IA3((IRPAgent3))
+ IA3 --- BasicCMIRP1((BasicCMIRP1))
+ IA3 --- EPIRP2((EPIRP2))
+ EPIRP1 -.- KL1[EPIRP1 Know ledge:
+- PMIRP1 Outline
+- AlarmIRP1 Outline]
+ EPIRP2 -.- KL2[EPIRP2 Know ledge:
+- BasicCMIRP1 Outline]
+
+```
+
+Figure A.2: EPIRP knowledge 2. A tree diagram showing SubNetwork1 and SubNetwork2 at the top. SubNetwork1 is connected to IRPAgent1 and IRPAgent2. IRPAgent1 is connected to EPIRP1 and PMIRP1. IRPAgent2 is connected to AlarmIRP1. SubNetwork2 is connected to IRPAgent3. IRPAgent3 is connected to BasicCMIRP1 and EPIRP2. Two knowledge boxes are shown: EPIRP1 Know ledge: - PMIRP1 Outline, - AlarmIRP1 Outline, and EPIRP2 Know ledge: - BasicCMIRP1 Outline.
+
+Figure A.2: EPIRP knowledge 2
+
+
+
+```
+
+graph TD
+ SN1((SubNetwork1)) --- IA1((IRPAgent1))
+ SN1 --- IA2((IRPAgent2))
+ IA1 --- EPIRP1((EPIRP1))
+ IA1 --- PMIRP1((PMIRP1))
+ IA2 --- AlarmIRP1((AlarmIRP1))
+ SN2((SubNetwork2)) --- IA3((IRPAgent3))
+ IA3 --- BasicCMIRP1((BasicCMIRP1))
+ EPIRP1 -.- KL1[EPIRP1 Know ledge:
+- PMIRP1 Outline
+- AlarmIRP1 Outline
+- BasicCMIRP1 Outline]
+
+```
+
+Figure A.3: EPIRP knowledge 3. A tree diagram showing SubNetwork1 and SubNetwork2 at the top. SubNetwork1 is connected to IRPAgent1 and IRPAgent2. IRPAgent1 is connected to EPIRP1 and PMIRP1. IRPAgent2 is connected to AlarmIRP1. SubNetwork2 is connected to IRPAgent3. IRPAgent3 is connected to BasicCMIRP1. A single knowledge box is shown: EPIRP1 Know ledge: - PMIRP1 Outline, - AlarmIRP1 Outline, - BasicCMIRP1 Outline.
+
+Figure A.3: EPIRP knowledge 3
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------------------------------------------------------|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| Sep 2003 | SA 21 | SP-030423 | -- | -- | Submitted to TSG SA#21 for Information | 1.0.0 | |
+| Dec 2003 | SA 22 | SP-030634 | -- | -- | Submitted to TSG SA#22 for Approval | 2.0.0 | 6.0.0 |
+| Jun 2007 | SA_36 | -- | -- | -- | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | 6.0.0 | 7.0.0 |
+| Mar 2009 | SA 43 | SP-090207 | 001 | -- | Include reference to SOAP Solution Set specification | 7.0.0 | 8.0.0 |
+| Dec 2009 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 |
+| Mar 2011 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | <b>11.0.0</b> |
+| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | <b>12.0.0</b> |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | <b>13.0.0</b> |
+| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | <b>14.0.0</b> |
+| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | <b>15.0.0</b> |
+| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | <b>16.0.0</b> |
+| 2022-04 | - | - | - | - | Update to Rel-17 version (MCC) | 16.0.0 | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | Update to Rel-18 version (MCC) | 17.0.0 | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32366/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32366/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7af81d9920a8777e4e84c920b8330dfe00ca16dc
--- /dev/null
+++ b/marked/Rel-18/32_series/32366/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a70c748cc521283e57a2f4f81f05bb1ee5e86ced6e0e5ec4cd3831ca67152d80
+size 9530
diff --git a/marked/Rel-18/32_series/32366/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32366/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b27b1107c7ca45366101529fe92eb72c22f62272
--- /dev/null
+++ b/marked/Rel-18/32_series/32366/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bac9284a7c432bee7c7d8e09899909d4ba0795fa5b23a7379adad522d557d268
+size 8437
diff --git a/marked/Rel-18/32_series/32366/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/32_series/32366/90ddb84c323b956e2d50a54d3f870566_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1773b952b654f5cf5b10cf27c2c4b2109f996ac2
--- /dev/null
+++ b/marked/Rel-18/32_series/32366/90ddb84c323b956e2d50a54d3f870566_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:673e78818bc1b308e3365335ae9675e309e3048456e1febc4a60063929b0a0e5
+size 74223
diff --git a/marked/Rel-18/32_series/32366/9a047c6501a487b3f18cfff971bcb33f_img.jpg b/marked/Rel-18/32_series/32366/9a047c6501a487b3f18cfff971bcb33f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..546c383b068bc67a4e0ef3751a8b6bf1c7458a52
--- /dev/null
+++ b/marked/Rel-18/32_series/32366/9a047c6501a487b3f18cfff971bcb33f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e61af52d64e2fe90f25b5dec8d1cc5a39be32d0f1717660463b4211bb117ab62
+size 38053
diff --git a/marked/Rel-18/32_series/32366/raw.md b/marked/Rel-18/32_series/32366/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..442ce5eea938cb8d5aa7c11f3a8a46e1c5ad91ee
--- /dev/null
+++ b/marked/Rel-18/32_series/32366/raw.md
@@ -0,0 +1,1260 @@
+
+
+# 3GPP TS 32.366 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+management, architecture, entry point,
+CORBA, XML, SOAP
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-----------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions ..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Solution Set definitions..... | 7 |
+| <b>Annex A (normative): CORBA Solution Set.....</b> | <b>8</b> |
+| A.1 Architectural Features ..... | 8 |
+| A.1.1 Syntax for Distinguished Names and Versions..... | 8 |
+| A.1.2 Notifications ..... | 8 |
+| A.2 Mapping ..... | 8 |
+| A.2.1 Operation and Notification mapping..... | 8 |
+| A.2.2 Operation parameter mapping..... | 8 |
+| A.2.3 Notification parameter mapping..... | 10 |
+| A.3 EPIRPNotification Interface ..... | 11 |
+| A.3.1 Method push (M)..... | 11 |
+| A.4 Solution Set definitions..... | 12 |
+| A.4.1 IDL definition structure..... | 12 |
+| A.4.2 IDL specification “EPIRPConstDefs.idl” ..... | 13 |
+| A.4.3 IDL specification “EPIRPSystem.idl” ..... | 15 |
+| A.4.4 IDL specification “EPIRPNotifications.idl” ..... | 17 |
+| A.5 Convention when using INS to fulfill part of EPIRP functions..... | 18 |
+| <b>Annex B (normative): XML definitions.....</b> | <b>20</b> |
+| B.1 Architectural features..... | 20 |
+| B.1.1 Syntax for Distinguished Names..... | 20 |
+| B.2 Mapping ..... | 20 |
+| B.3 Solution Set definitions..... | 20 |
+| B.3.1 XML definition structure ..... | 20 |
+| B.3.2 Graphical Representation ..... | 20 |
+| B.3.3 XML Schema “ePIRPNotif.xsd”..... | 21 |
+| <b>Annex C (normative): SOAP Solution Set.....</b> | <b>22</b> |
+| C.1 Architectural Features ..... | 22 |
+| C.1.1 Syntax for Distinguished Names and versions..... | 22 |
+| C.1.2 General ..... | 22 |
+| C.2 Mapping ..... | 23 |
+| C.2.1 Operation and Notification mapping..... | 23 |
+| C.2.2 Operation parameter mapping..... | 23 |
+| C.2.2.1 Operation getIRPOutline..... | 23 |
+| C.2.2.1.1 Input parameters ..... | 23 |
+| C.2.2.1.2 Output parameters..... | 24 |
+| C.2.2.1.3 Fault definition..... | 24 |
+| C.2.2.2 Operation getIRPReference ..... | 24 |
+| C.2.2.2.1 Input parameters ..... | 24 |
+| C.2.2.2.2 Output parameters..... | 24 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------|-----------|
+| C.2.2.2.3 | Fault definition..... | 24 |
+| C.2.2.3 | Operation releaseIRPReference..... | 25 |
+| C.2.2.3.1 | Input parameters ..... | 25 |
+| C.2.2.3.2 | Output parameters..... | 25 |
+| C.2.2.3.3 | Fault definition..... | 25 |
+| C.3 | Solution Set definitions ..... | 25 |
+| C.3.1 | WSDL definition structure ..... | 25 |
+| C.3.2 | Graphical Representation ..... | 25 |
+| C.3.3 | WSDL specification “EntryPointIRPSystem.wsdl” ..... | 27 |
+| <b>Annex D (informative):</b> | <b>Change history.....</b> | <b>30</b> |
+
+# 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+- 32.361: "Entry Point (EP) Integration Reference Point (IRP): Requirements"
+- 32.362: "Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)"
+- 32.366: "Entry Point (EP) Integration Reference Point (IRP): Solution Set (SS) definitions"**
+
+The present document is part of a set of technical specifications defining the Telecommunication Management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 [1]. The TM architecture is described in 3GPP TS 32.102 [2]. The other specifications define the interface (Itf-N) between the managing system (manager), which is in general the Network Manager (NM) and the managed system (agent), which is either an Element Manager (EM) or the managed NE itself. The Itf-N is composed of a number of Integration Reference Points (IRPs) defining the information in the agent that is visible for the manager, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. EP (Entry Point) IRP is one of these IRPs with special function.
+
+It's difficult for an NM to discover all IRPs in the environment that there are several managed systems and/or if there are multiple IRPs related to each managed systems. This Entry Point is proposed to provide a convenient mechanism for NM to discover the managed systems and their related IRPs.
+
+# --- 1 Scope
+
+The present document specifies the Solution Set definitions for the IRP whose semantics are specified in the Entry Point IRP: Information Service (3GPP TS 32.362 [6]).
+
+This Solution Set definitions specification is related to 3GPP TS 32.362 V14.0.X [6].
+
+# --- 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.361: "Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Requirements".
+- [4] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP): Information Service (IS)".
+- [5] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP): Requirements".
+- [6] 3GPP TS 32.362: "Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)".
+- [7] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [8] OMG TC Document telecom/98-11-01: "OMG Notification Service".
+<http://www.omg.org/technology/documents/>
+- [9] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
+- [10] ITU-T Recommendation Q.816.1 Recommendation "CORBA based TMN services: Extensions to support coarse-grained interfaces".
+- [11] OMG TC Document telecom/98-12-09: "CORBA services: Common Object Services Specification". <http://www.omg.org/technology/documents/>
+- [12] ISO 8859-1: "Information technology - 8-bit single-byte coded graphic character sets - Part 1: Latin alphabet No. 1".
+- [13] 3GPP TS 32.336: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions".
+- [14] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements".
+
+- [15] 3GPP TS 32.316: "Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions".
+ - [16] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+ - [17] W3C SOAP 1.1 specification (<http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>)
+ - [18] W3C XPath 1.0 specification (<http://www.w3.org/TR/1999/REC-xpath-19991116>)
+ - [19] W3C WSDL 1.1 specification (<http://www.w3.org/TR/2001/NOTE-wsdl-20010315>)
+ - [20] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>)
+-
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.361 [3], 3GPP TS 32.331 [14], 3GPP TS 32.150 [16] and the following apply:
+
+**IRP document version number string (or "IRPVersion"):** See 3GPP TS 32.311 [5].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|-------------------------------------------|
+| CORBA | Common Object Request Broker Architecture |
+| DN | Distinguished Name |
+| EM | Element Manager |
+| EP | Entry Point |
+| EPIRP | Entry Point IRP |
+| IRP | Integration Reference Point |
+| IOC | Information Object Class |
+| IS | Information Service |
+| NE | Network Element |
+| NL | Notification Log |
+| NM | Network Manager |
+| SS | Solution Set |
+| WSDL | Web Service Description Language |
+| XML | eXtensible Markup Language |
+
+---
+
+# 4 Solution Set definitions
+
+This specification defines the following 3GPP EP IRP Solution Set definitions:
+
+- 3GPP EP IRP CORBA SS (Annex A)
+- 3GPP EP IRP XML definitions (Annex B)
+- 3GPP EP IRP SOAP Solution Set (Annex C)
+
+# Annex A (normative): CORBA Solution Set
+
+This annex contains the CORBA Solution Set for the IRP whose semantics is specified in EP IRP: Information Service (TS 32.362 [6]).
+
+## A.1 Architectural Features
+
+The overall architectural feature of EP IRP is specified in 3GPP TS 32.362 [6].
+
+This clause specifies features that are specific to the CORBA SS.
+
+### A.1.1 Syntax for Distinguished Names and Versions
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [9].
+
+The version of this IRP is represented as a string (see also clause 3 for versions).
+
+### A.1.2 Notifications
+
+Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.306 [7]).
+
+The contents of the EP IRP notifications are defined in the present document.
+
+## A.2 Mapping
+
+### A.2.1 Operation and Notification mapping
+
+EPIRP: IS (3GPP TS 32.362 [6]) defines semantics of operation and notification visible across the EPIRP.
+
+Table A.2.1 indicates the mapping of these operations and notifications to their equivalents defined in this SS.
+
+**Table A.2.1: Mapping from IS Operations and Notification to SS equivalents**
+
+| IS Operations/ notification TS 32.362 [6] | SS Method | Qualifier |
+|-----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-----------|
+| getIRPOutline | get irp outline | M |
+| getIRPReference | get irp reference | M |
+| releaseIRPReference | release irp reference | M |
+| notifyIRPInfoChanges | push_structured_event (See clause A.3.1) | M |
+| getIRPVersion (see note) | get ep irp versions | M |
+| getOperationProfile (see note) | get ep irp operations profile | O |
+| getNotificationProfile (see note) | get ep irp notification profile | O |
+| NOTE: This operation is of ManagedGenericIRP IOC specified in 3GPP TS 32.312 [4]. The EPIRP IOC of 3GPP TS 32.362 [6] inherits from it. | | |
+
+### A.2.2 Operation parameter mapping
+
+The EPIRP: IS 3GPP TS 32.362 [6] defines semantics of parameters carried in operations across the EPIRP. The following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table A.2.2.1: Mapping from IS getIRPOutline parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-----------------------------------------------------------------------------------------------|-----------|
+| iRPVersion | ManagedGenericIRPConstDefs::VersionNumber irp_version | M |
+| supportedIRPList | EPIRPConstDefs::SupportedIRPList supported_irp_list | M |
+| status | Return value of type EPIRPConstDefs::Result<br>Exception:<br>GetIRPOutline, InvalidIRPVersion | M |
+
+**Table A.2.2.2: Mapping from IS getIRPReference parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------|
+| managerIdentifier | EPIRPConstDefs::ManagerIdentifier manager_identifier | M |
+| systemDn | EPIRPConstDefs::DN system_dn | M |
+| rDN | EPIRPConstDefs::RDN r_DN | M |
+| iRPReference | string irp_reference (stringified IOR) | M |
+| status | Return value of type EPIRPConstDefs::Result<br>Exception:<br>GetIRPReference, ManagedGenericIRPSystem::InvalidParameter | M |
+
+**Table A.2.2.3: Mapping from IS releaseIRPReference parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------------------------------------------------|-----------|
+| managerIdentifier | EPIRPConstDefs::ManagerIdentifier manager_identifier | M |
+| iRPReference | string irp_reference (stringified IOR) | M |
+| status | Return value of type EPIRPConstDefs::Result<br>Exception:<br>ReleaseIRPReference, UnknownIRPReference | M |
+
+**Table A.2.2.4: Mapping from IS getIRPVersion parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------------|-----------|
+| versionNumberSet | Return value of type ManagedGenericIRPConstDefs::VersionNumberSet | M |
+| status | Exception:<br>GetEPIRPVersions | M |
+
+**Table A.2.2.5: Mapping from IS getOperationProfile parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iRPVersion | ManagedGenericIRPConstDefs::VersionNumber irp_version | M |
+| operationNameProfile,<br>operationParameterProfile | Return value of type ManagedGenericIRPConstDefs::MethodList | M |
+| status | Exception:<br>GetEPIRPOperationsProfile,<br>ManagedGenericIRPSystem::OperationNotSupported,<br>ManagedGenericIRPSystem::InvalidParameter | M |
+
+**Table A.2.2.6: Mapping from IS getNotificationProfile parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iRPVersion | ManagedGenericIRPConstDefs::VersionNumber<br>irp_version | M |
+| notificationNameProfile,<br>notificationParameterProfile | Return value of type<br>ManagedGenericIRPConstDefs::MethodList | M |
+| status | Exception:<br>GetEPIRPNotificationProfile,<br>ManagedGenericIRPSystem::OperationNotSupported,<br>ManagedGenericIRPSystem::InvalidParameter | M |
+
+### A.2.3 Notification parameter mapping
+
+The EPIRP: IS (3GPP TS 32.362 [6]) defines semantics of parameters carried in notifications. The following table indicates the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification Service [8]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [8], is:
+
+```
+Header
+ Fixed Header
+ domain_name
+ type_name
+ event_name
+ Variable Header
+Body
+ filterable_body_fields
+ remaining_body
+```
+
+The following table lists all OMG Structured Event attributes in the second column. The first column identifies the EPIRP: IS (3GPP TS 32.362 [6]) defined notification parameters.
+
+Table A.2.3: Mapping for notifyIRPInfoChanges
+
+| IS Parameters | OMG CORBA Structured Event attribute | Qualifier | Comment |
+|-----------------------------------------|---------------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| There is no corresponding IS attribute. | domain_name | M | It carries the IRP document version number string. See clause 3.1.<br>It indicates the syntax and semantics of the Structured Event as defined by the present document. |
+| notificationType | type_name | M | This is the ET_IRPINFO_CHANGES of module of EPIRPSYSTEM. |
+| There is no corresponding IS attribute. | event_name | M | It carries no information. |
+| There is no corresponding IS attribute. | Variable Header | | |
+| objectClass, objectInstance | One NV pair of filterable_body_fields | M | NV stands for name-value pair. Order arrangement of NV pairs is not significant. The name of NV-pair is always encoded in string.<br><br>Name of this NV pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [7]). |
+| notificationId | One NV pair of remaining_body | M | Name of NV pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is a long. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [7]). |
+| eventTime | One NV pair of filterable_body_fields | M | Name of NV pair is the EVENT_TIME of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is IRPTime. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [7]). |
+| systemDN | One NV pair of filterable_body_fields | M | Name of NV pair is the SYSTEM_DN of interface AttributeNameValue of module NotificationIRPConstDefs.<br><br>Value of NV pair is a string. See corresponding table in Notification IRP: CORBA SS (3GPP TS 32.306 [7]). |
+| iRPDn | One NV pair of remaining_body | M | Name of NV pair is the IRP_DN of interface NotifyIRPInfoChanges of module EPIRPNotifications.<br><br>Value of NV pair is a EPIRPConstDefs::DN. |
+| changeMode | One NV pair of remaining_body | M | Name of NV pair is the CHANGE_MODE of interface NotifyIRPInfoChanges of module EPIRPNotifications.<br><br>Value of NV pair is a EPIRPConstDefs::ChangeMode. |
+| additionalText | One NV pair of remaining_body | M | Name of NV pair is the ADDITIONAL_TEXT of interface NotifyIRPInfoChanges of module EPIRPNotifications.<br><br>Value of NV pair is a string. |
+
+## A.3 EPIRPNotification Interface
+
+OMG CORBA Notification push operation is used to realise the notification of EPIRPNotifications. All the notifications in this interface are implemented using this push\_structured\_event method.
+
+### A.3.1 Method push (M)
+
+```
+module CosNotifyComm {
+ ...
+ Interface SequencePushConsumer : NotifyPublish {
+```
+
+```
+ void push_structured_events(
+ in CosNotification::EventBatch notifications)
+ raises( CosEventComm::Disconnected);
+ ...
+ }; // SequencePushConsumer
+}; // CosNotifyComm
+```
+
+- 1) The `push_structured_events` method takes an input parameter of type `EventBatch` as defined in the OMG `CosNotification` module (OMG Notification Service [8]). This data type is the same as a sequence of Structured Events. Upon invocation, this parameter shall contain a sequence of Structured Events being delivered to `IRPManager` by `IRP Agent` to which it is connected.
+- 2) The maximum number of events that shall be transmitted within a single invocation of this operation is controlled by `IRP Agent` wide configuration parameter.
+- 3) The amount of time the supplier (`IRP Agent`) of a sequence of Structured Events shall accumulate individual events into the sequence before invoking this operation is controlled by `IRP Agent` wide configuration parameter as well.
+- 4) `IRP Agent` may push `EventBatch` with only one Structured Event.
+
+## --- A.4 Solution Set definitions
+
+### A.4.1 IDL definition structure
+
+Clause A.4.2 defines the constants and types used by the EP IRP.
+
+Clause A.4.3 defines the operations which are performed by the EP IRP agent.
+
+Clause A.4.4 defines the notifications which are performed by the EP IRP agent.
+
+### A.4.2 IDL specification “EPIRPConstDefs.idl”
+
+```
+//File: EPIRPConstDefs.idl
+#ifndef _EP_IRP_CONST_DEFS_IDL_
+#define _EP_IRP_CONST_DEFS_IDL_
+
+#include <ManagedGenericIRPConstDefs.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/** Module: EPIRPSystem
+ */
+module EPIRPConstDefs
+{
+ enum Result {OK, FAILURE};
+ /**
+ The RDN carries an optional instance class name and a mandatory
+ instance identifier. This type (a string) may contain 0 or 1
+ equal sign. If an equal sign is present, the substring before
+ the equal sign is the class name, and the substring after the
+ equal sign is the instance identifier. If the equal sign is
+ absent, the entire string is the instance identifier.
+ */
+ typedef string RDN;
+ typedef string DN;
+ typedef sequence<DN> DNList;
+
+ /**
+ IRPManagementScopeOpt is a type carrying an optional parameter.
+ If the boolean is TRUE, then the value is present.
+ Otherwise the value is absent.
+ */
+ union IRPManagementScopeOpt switch (boolean)
+ {
+ case TRUE: DNList value;
+ };
+
+ /**
+ The IRPElement defines the structure to be returned as part of
+ get_irp_outline().
+ */
+ struct IRPElement
+ {
+ RDN r_DN;
+ ManagedGenericIRPConstDefs::VersionNumberSet irp_versions;
+ IRPManagementScopeOpt irp_management_scope;
+ };
+
+ /**
+ List of all IRPElement and their associated parameters.
+ */
+ typedef sequence<IRPElement> IRPList;
+
+ struct SupportedIRP
+ {
+ DN system_dn;
+ IRPList irp_list;
+ };
+
+ typedef sequence<SupportedIRP> SupportedIRPList;
+
+ typedef string ManagerIdentifier;
+
+ enum ChangeMode {REGISTER, DEREGISTER, MODIFY};
+
+ /**
+ Define the parameters specified in
+ the notifyEpInfoChanges notification.
+ */
+ interface AttributeNameValue
+ {
+ const string IRP_DN = "IRP_DN";
+ const string CHANGE_MODE = "CHANGE_MODE";
+ const string ADDITIONAL_TEXT = "ADDITIONAL_TEXT";
+ }
+}
+```
+
+```
+};
+```
+
+```
+};
+```
+
+```
+#endif// _EP_IRP_CONST_DEFS_IDL_
+```
+
+### A.4.3 IDL specification “EPIRPSystem.idl”
+
+```
+
+//File: EPIRPSystem.idl
+#ifndef _EP_IRP_SYSTEM_IDL_
+#define _EP_IRP_SYSTEM_IDL_
+
+#include <ManagedGenericIRPConstDefs.idl>
+#include <ManagedGenericIRPSystem.idl>
+#include <EPIRPConstDefs.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/** Module: EPIRPSystem
+ */
+module EPIRPSystem
+{
+ exception InvalidIRPVersion { string reason; };
+ exception UnknownIRPReference { string reason; };
+
+ /**
+ System fails to complete the operation. System can provide reason
+ to qualify the exception. The semantics carried in reason
+ is outside the scope of this IRP.
+ */
+ exception GetIRPOutline { string reason; };
+ exception GetIRPReference { string reason; };
+ exception ReleaseIRPReference { string reason; };
+ exception GetEPIRPVersions { string reason; };
+ exception GetEPIRPOperationsProfile { string reason; };
+ exception GetEPIRPNotificationProfile { string reason; };
+
+ interface EPIRP
+ {
+ /**
+ * The IRPManager uses this operation to request the EPIRP to
+ * return the outline information of the supported IRPs. The EPIRP
+ * shall return the outline information of all the IRPs supported by the
+ * IRPAgent that contains the EPIRP. The EPIRP may
+ * additionally return the outline information of all the IRPs supported
+ * by other IRPAgents.
+ */
+ EPIRPConstDefs::Result get_irp_outline(
+ in ManagedGenericIRPConstDefs::VersionNumber irp_version,
+ out EPIRPConstDefs::SupportedIRPList supported_irp_list
+ )
+ raises (GetIRPOutline, InvalidIRPVersion);
+
+ /**
+ * The IRPManager uses this operation to request the EPIRP to return
+ * the stringified IOR of the IRP identified by system_dn and r_DN.
+ */
+ EPIRPConstDefs::Result get_irp_reference(
+ in EPIRPConstDefs::ManagerIdentifier manager_identifier,
+ in EPIRPConstDefs::DN system_dn,
+ in EPIRPConstDefs::RDN r_DN,
+ out string irp_reference
+ )
+ raises (GetIRPReference,
+ ManagedGenericIRPSystem::InvalidParameter);
+
+ /**
+ * The IRPManager uses this operation to request the IRPAgent to
+ * release a specific IRP reference. Whether the IRP reference
+ * is really released or not in the IRPAgent is outside the
+ * scope of this document.
+ */
+ EPIRPConstDefs::Result release_irp_reference(
+ in EPIRPConstDefs::ManagerIdentifier manager_identifier,
+ in string irp_reference
+ )
+ raises (ReleaseIRPReference,
+ UnknownIRPReference);
+
+ /**
+
+```
+
+```
+ * Return the list of all supported EPIRP versions.
+ */
+ ManagedGenericIRPConstDefs::VersionNumberSet get_ep_irp_versions (
+ )
+ raises (GetEPIRPVersions);
+
+ /**
+ * Return the list of all supported operations and their supported
+ * parameters for a specific EPIRP version.
+ */
+ ManagedGenericIRPConstDefs::MethodList get_ep_irp_operations_profile (
+ in ManagedGenericIRPConstDefs::VersionNumber irp_version
+ )
+ raises (GetEPIRPOperationsProfile,
+ ManagedGenericIRPSystem::OperationNotSupported,
+ ManagedGenericIRPSystem::InvalidParameter);
+
+ /**
+ * Return the list of all supported notifications and their supported
+ * parameters for a specific EPIRP version.
+ */
+ ManagedGenericIRPConstDefs::MethodList get_ep_irp_notification_profile
+ (
+ in ManagedGenericIRPConstDefs::VersionNumber irp_version
+ )
+ raises (GetEPIRPNotificationProfile,
+ ManagedGenericIRPSystem::OperationNotSupported,
+ ManagedGenericIRPSystem::InvalidParameter);
+};
+
+};
+
+#endif // _EP_IRP_SYSTEM_IDL_
+```
+
+### A.4.4 IDL specification “EPIRPNotifications.idl”
+
+```
+//File: EPIRPNotifications.idl
+#ifdef _EP_IRP_NOTIFICATIONS_IDL_
+#define _EP_IRP_NOTIFICATIONS_IDL_
+
+#include <NotificationIRPNotifications.idl>
+#include <EPIRPConstDefs.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: EPIRPNotifications
+*/
+module EPIRPNotifications
+{
+ interface NotifyIRPInfoChanges: NotificationIRPNotifications::Notify
+ {
+ const string ET_IRPINFO_CHANGES = "notifyIrpInfoChanges";
+
+ /**
+ * This constant defines the name of the iRPDn property.
+ * The data type for the value of this property
+ * is DN.
+ */
+ const string IRP_DN =
+ EPIRPConstDefs::AttributeNameValue::IRP_DN;
+
+ /**
+ * This constant defines the name of the changeMode property.
+ * The data type for the value of this property is ChangeMode.
+ */
+ const string CHANGE_MODE =
+ EPIRPConstDefs::AttributeNameValue::CHANGE_MODE;
+
+ /**
+ * This constant defines the name of the additionalText property.
+ * The data type for the value of this property is string.
+ */
+ const string ADDITIONAL_TEXT =
+ EPIRPConstDefs::AttributeNameValue::ADDITIONAL_TEXT;
+ };
+};
+
+#endif // _EP_IRP_NOTIFICATIONS_IDL_
+```
+
+## A.5 Convention when using INS to fulfill part of EPIRP functions
+
+The implementation of the EPIRP and in particular, the management of CORBA object references within EPIRP, is not a subject matter for 3GPP standardization.
+
+ITU-T SG4 Framework for CORBA-Based Telecommunications Management Network Interfaces (ITU-T Recommendation Q.816.1 [10]) uses OMG Interoperable Naming Service (INS) [11] for the management of CORBA object references. Furthermore, it specifies a convention to name and populate the CORBA object entries within the INS.
+
+This Annex notes that, in the event that an EPIRP implementation uses INS to fulfill part of EPIRP functions, it is advantageous to populate the INS using the ITU-T defined convention.
+
+### Convention
+
+The OMG INS CORBA *name component* (in short, called CORBA compound name) has the following IDL definition:
+
+```
+// IDL
+typedef string Istring;
+struct NameComponent {
+ Istring id;
+ Istring kind;
+};
+```
+
+*Istring* is a placeholder for a future IDL internationalized string. The *id* and *kind* attributes must be composed of characters from the ISO 8859-1 [12] character set, excluding the null character and other non-printable characters. The strings cannot exceed 255 characters. The *id* attribute cannot be an empty string but the *kind* attribute can be an empty string.
+
+The CORBA compound name (see *Name* below) is defined as a sequence of name components:
+
+```
+// IDL
+typedef sequence<NameComponent> Name;
+```
+
+The 3GPP defined DN (in short, called DN) of a managed object is represented by the CORBA *compound name*. For example, a DN, quoted from 3GPP TS 32.300 [9], say
+
+“DC=se.companyZ.lmc, Network=9, SubNetwork=1, IRPAgent=1, AlarmIRP.iRPId=2”, shall be represented by a sequence of 6 *name components* where the *id* and *kind* of the first *name component* shall be “se\_companyZ\_lmc” and “DC” respectively. The CORBA *compound name*, shall be:
+
+| index | kind | id |
+|-------|------------------|-------------------|
+| 0 | “DC” | “se_companyZ_lmc” |
+| 1 | “Network” | “9” |
+| 2 | “SubNetwork” | “1” |
+| 3 | “IRPAgent” | “1” |
+| 4 | “AlarmIRP.iRPId” | “2” |
+| 5 | “” | “Object” |
+
+The CORBA *compound name*, in stringified name form, shall be
+
+“se\_companyZ\_lmc.DC/9.Network/1.SubNetwork/1.IRPAgent/2.AlarmIRP.iRPId/Object”.
+
+NOTE 1: DN appears in interactions (e.g. operations, notifications) across the Itf-N.
+
+NOTE 2: The CORBA compound name is used internally with the IRPAgent (and its INS) and does not appear in interactions across the Itf-N.
+
+The use of the last row of the CORBA *compound name*, i.e. kind == "" and id == "Object", is in accordance to the convention standardized by ITU-T Recommendation Q.816.1 [10]. According to convention standardized by ITU-T Recommendation Q.816.1 [10], the use of index 0 to 4 inclusive is to indicate the naming context of the object and the use of index 0 to 5 inclusive is to indicate the object itself.
+
+DN DC component is composed of multiple words separated by separator, i.e. a dot. It is suggested that the applications (e.g. IRP Agent codes) that process CORBA compound name and DN should map the dot, used as separator in DN DC component, with underscore. This mapping is necessary because in the stringified CORBA *compound name*, the dot is used for the separation of *id* and *kind*. This replacement rule also implies that underscore should not be used as character of DC words.
+
+# Annex B (normative): XML definitions
+
+The annex specifies the XML Definitions for the EP Integration Reference Point (IRP) as it applies to Itf-N, in accordance with EP IRP IS definitions [6], for usage with the Notification Log IRP XML Definitions [13].
+
+## B.1 Architectural features
+
+The overall architectural feature of EP IRP is specified in 3GPP TS 32.352 [6].
+
+This clause specifies features that are specific to the XML Schema definitions.
+
+### B.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [9].
+
+## B.2 Mapping
+
+Not present in the current version of this specification.
+
+## B.3 Solution Set definitions
+
+### B.3.1 XML definition structure
+
+Clause B.3.2 provides a graphical representation of the XML elements.
+
+Clause B.3.3 provides XML definitions of EP IRP notifications as defined in 3GPP TS 32.362 [6].
+
+### B.3.2 Graphical Representation
+
+
+
+```
+graph LR; Root[NotifyIRPInfoChanges] --> S1((sequence)); S1 --> H[xe:header]; Root --> S2((sequence)); S2 --> B[xep:body]; B --> S3((sequence)); S3 --> IRPDN[xep:IRPDN]; S3 --> CM[xep:ChangeMode]; S3 --> AT[xep:AdditionalText]; style AT stroke-dasharray: 5 5;
+```
+
+Graphical representation of the XML definition structure for NotifyIRPInfoChanges. The diagram shows a root element 'NotifyIRPInfoChanges' branching into two main paths. The first path leads to 'xe:header' via a 'sequence' symbol (a circle with four dots). The second path leads to 'xep:body' via another 'sequence' symbol. From 'xep:body', the path continues through another 'sequence' symbol to a group of three elements: 'xep:IRPDN', 'xep:ChangeMode', and 'xep:AdditionalText'. The elements 'xep:IRPDN' and 'xep:ChangeMode' are solid boxes, while 'xep:AdditionalText' is a dashed box. The entire structure is enclosed in a yellow dashed box labeled 'xep:NotifyIRPInfoChanges'.
+
+NOTE: The use of XML schema key word “sequence” to support IS-defined set (not sequence) is for the purpose of XML processor efficiency. This shall not imply the use of “sequence” in other technology.
+
+### B.3.3 XML Schema “ePIRPNotif.xsd”
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ 3GPP TS 32.366 EPIRP Notification XML Schema
+ ePIRPNotif.xsd
+-->
+<schema xmlns:xep="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#ePIRPNotif"
+ xmlns:xe="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#notification"
+ xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"
+ xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#ePIRPNotif"
+ elementFormDefault="qualified" attributeFormDefault="unqualified">
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#notification"/>
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"/>
+ <simpleType name="ChangeMode">
+ <restriction base="string">
+ <enumeration value="Register"/>
+ <enumeration value="Deregister"/>
+ <enumeration value="Modify"/>
+ </restriction>
+ </simpleType>
+ <complexType name="NotifyIRPInfoChanges">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="IRPDN" type="xn:dn"/>
+ <element name="ChangeMode" type="xep:ChangeMode"/>
+ <element name="AdditionalText" type="string" minOccurs="0"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+ </complexType>
+ <element name="NotifyIRPInfoChanges" type="xep:NotifyIRPInfoChanges"/>
+</schema>
+```
+
+# Annex C (normative): SOAP Solution Set
+
+The overall architectural feature of the Entry Point IRP is specified in 3GPP TS 32.362 [6]. This clause specifies features that are specific to the SOAP solution set.
+
+## C.1 Architectural Features
+
+### C.1.1 Syntax for Distinguished Names and versions
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [9].
+
+The version of this IRP is represented as a string (see also clause 3.1).
+
+### C.1.2 General
+
+The SOAP 1.1 specification [17] and WSDL 1.1 specification [19] are supported.
+
+The SOAP 1.2 specification [20] is supported optionally.
+
+This specification uses "document" style in WSDL file.
+
+This specification uses "literal" encoding style in WSDL file.
+
+The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification [18]). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex.
+
+The Entry Point IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.306 [7]. The IRPAgent shall support the push interface model, which means that the IRPAgent sends Entry Point notifications to the IRPManager as soon as new events occur. The IRPManager does not need to check ("pull") for events.
+
+This specification uses a number of namespace prefixes throughout that are listed in Table C.1.2
+
+**Table C.1.2: Prefixes and Namespaces used in this specification**
+
+| PREFIX | NAMESPACE |
+|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| (no prefix) | <a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a> |
+| soap | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a> |
+| entryPointIRPSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPSystem</a> |
+| entryPointIRPData | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPData">http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPData</a> |
+| xn | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm">http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm</a> |
+| genericIRPSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem</a> |
+| genericIRPData | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData">http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData</a> |
+| ntfIRPNtfSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem</a> |
+
+## C.2 Mapping
+
+### C.2.1 Operation and Notification mapping
+
+The Entry Point IRP IS (3GPP TS 32.362 [6]) defines the operations and their semantics.
+
+Table C.2.1 maps the operations defined in the Entry Point IRP IS to their equivalent types, messages, port type operation, and binding operation in this Solution Set (SS).
+
+Table C.2.1 also maps the notifications of the Entry Point IRP IS, as well as inherited operations.
+
+Table C.2.1 also qualifies if an operation is Mandatory (M) or Optional (O).
+
+**Table C.2.1: Mapping from IS Operation to SS Equivalents**
+
+| IS Operation in 3GPP TS 32.362 [6] | SS: Operation for WSDL port type and WSDL binding | SS: Port of EntryPointIRPService | Qualifier |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|----------------------------------|-----------|
+| getIRPOutline | getIRPOutline (note 1) | EntryPointIRPPort | M |
+| getIRPReference | getIRPReference (note 1) | EntryPointIRPPort | M |
+| releaseIRPReference | releaseIRPReference (note 1) | EntryPointIRPPort | M |
+| notifyIRPInfoChanges | notify (note 2) | NotificationIRPNtfPort | M |
+| getIRPVersion (note 3) | See TS 32.316 [15] | GenericIRPPort | M |
+| getOperationProfile (note 3) | See TS 32.316 [15] | GenericIRPPort | O |
+| getNotificationProfile (note 3) | See TS 32.316 [15] | GenericIRPPort | O |
+| NOTE 1: The operation is under the port type entryPointIRPSystem:EntryPointIRPPortType and under the binding entryPointIRPSystem:EntryPointIRPBinding. | | | |
+| NOTE 2: The IS equivalent maps to an XML definition specified in Annex B, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3GPP TS 32.306 [7]. This binding is linked to a port of the EntryPointIRPService as indicated in the table above. | | | |
+| NOTE 3: The IS operation is inherited from the ManagedGenericIRP IOC specified in 3GPP TS 32.312 [4]. This inheritance is by the EPIRP IOC of 3GPP TS 32.362 [6] inheriting from the ManagedGenericIRP IOC. The corresponding binding is linked to a port of the EntryPointIRPService as indicated in the table above. | | | |
+
+### C.2.2 Operation parameter mapping
+
+The Entry Point IRP IS (3GPP TS 32.362 [6]) defines semantics of parameters carried in the operations. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+#### C.2.2.1 Operation getIRPOutline
+
+##### C.2.2.1.1 Input parameters
+
+**Table C.2.2.1.1: Mapping from IS getIRPOutline input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iRPVersion | iRPVersion | M |
+
+##### C.2.2.1.2 Output parameters
+
+**Table C.2.2.1.2: Mapping from IS getIRPOutline output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding output message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| supportedIRPList | supportedIRPList | M |
+| status | status | M |
+
+##### C.2.2.1.3 Fault definition
+
+**Table C.2.2.1.3: Mapping from IS getIRPOutline exceptions to SS equivalents**
+
+| Assertion name | SS WSDL type enumeration value used in corresponding fault message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| invalidIRPVersion | InvalidIRPVersion | M |
+| operationFailed | OperationFailed | M |
+
+#### C.2.2.2 Operation getIRPReference
+
+##### C.2.2.2.1 Input parameters
+
+**Table C.2.2.2.1: Mapping from IS getIRPReference input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| managerIdentifier | managerIdentifier | M |
+| systemDN | systemDN | M |
+| rDN | rDN | M |
+
+##### C.2.2.2.2 Output parameters
+
+**Table C.2.2.2.2: Mapping from IS getIRPReference output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding output message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| iRPReference | iRPReference | M |
+| status | status | M |
+
+##### C.2.2.2.3 Fault definition
+
+**Table C.2.2.2.3: Mapping from IS getIRPReference exceptions to SS equivalents**
+
+| Assertion name | SS WSDL type enumeration value used in corresponding fault message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| invalidRequestedParameters | InvalidRequestedParameters | M |
+| operationFailed | OperationFailed | M |
+
+#### C.2.2.3 Operation releaseIRPReference
+
+##### C.2.2.3.1 Input parameters
+
+**Table C.2.2.3.1: Mapping from IS releaseIRPReference input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| managerIdentifier | managerIdentifier | M |
+| iRPReference | iRPReference | M |
+
+##### C.2.2.3.2 Output parameters
+
+**Table C.2.2.3.2: Mapping from IS releaseIRPReference output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding output message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| status | status | M |
+
+##### C.2.2.3.3 Fault definition
+
+**Table C.2.2.3.3: Mapping from IS releaseIRPReference exceptions to SS equivalents**
+
+| Assertion name | SS WSDL type enumeration value used in corresponding fault message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| unknownIRPReference | UnknownIRPReference | M |
+| operationFailed | OperationFailed | M |
+
+## C.3 Solution Set definitions
+
+### C.3.1 WSDL definition structure
+
+Clause C.3.2 provides a graphical representation of the EP IRP service.
+
+Clause C.3.3 defines the services which are supported the EP IRP agent.
+
+### C.3.2 Graphical Representation
+
+The WSDL structure is depicted in Figure C.3.2 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service.
+
+
+
+The diagram illustrates the WSDL structure for the Entry Point IRP SOAP Solution Set, organized into three columns: PortTypes, Bindings, and Services.
+
+- PortTypes:**
+ - NotificationIRPIntf**: Contains the operation `notify`.
+ - GenericIRPPortType**: Contains the operations `getIRPVersion`, `getOperationProfile`, and `getNotificationProfile`.
+ - EntryPointIRPPortType**: Contains the operations `getIRPOutline`, `getIRPReference`, and `releaseIRPReference`.
+- Bindings:**
+ - NotificationIRPIntf**: SOAP binding with transport `http://schemas.xmlsoap.org/soap/http`. It includes the operation `notify` and links to `doc` and `def` elements.
+ - GenericIRPBinding**: SOAP binding with transport `http://schemas.xmlsoap.org/soap/http`. It includes operations `getIRPVersion`, `getOperationProfile`, and `getNotificationProfile`, each with a `doc` link.
+ - EntryPointIRPBinding**: SOAP binding with transport `http://schemas.xmlsoap.org/soap/http`. It includes operations `getIRPOutline`, `getIRPReference`, and `releaseIRPReference`, each with a `doc` link.
+- Services:**
+ - NotificationIRPIntf**: A service with the location `To be defined.`
+ - EntryPointIRPService**: A service containing three ports:
+ - NotificationIRPIntfPort**: Location: [http://www.3gpp.org/ftp/specs/archive/32\\_series/32.306#NotificationIRPIntf](http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPIntf)
+ - GenericIRPPort**: Location: [http://www.3gpp.org/ftp/specs/archive/32\\_series/32.316#GenericIRP](http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRP)
+ - EntryPointIRPPort**: Location: [http://www.3gpp.org/ftp/specs/archive/32\\_series/32.366#EntryPointIRP](http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRP)
+
+WSDL structure diagram showing PortTypes, Bindings, and Services for Entry Point IRP SOAP Solution Set.
+
+Figure C.3.2: Entry Point IRP SOAP Solution Set WSDL structure
+
+### C.3.3 WSDL specification “EntryPointIRPSystem.wsdl”
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ 3GPP TS 32.366 Entry Point IRP SOAP Solution Set
+-->
+<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
+ xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
+ xmlns:entryPointIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPSystem"
+ xmlns:entryPointIRPData="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPData"
+ xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"
+ xmlns:genericIRPSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem"
+ xmlns:genericIRPData="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData"
+ xmlns:ntfIRPNtfSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem"
+ targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPSystem">
+ <import
+ namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem" />
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem" />
+ <types>
+ <schema
+ targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRPData"
+ xmlns="http://www.w3.org/2001/XMLSchema">
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"/>
+ <import
+ namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPData"/>
+ <!-- The following types are defined for the Entry Point IRP operations -->
+ <simpleType name="OperationStatusTwo">
+ <restriction base="string">
+ <enumeration value="OperationSucceeded"/>
+ <enumeration value="OperationFailed"/>
+ </restriction>
+ </simpleType>
+ <complexType name="IRPManagementScope">
+ <sequence>
+ <element name="subTreeDN" type="xn:dn" minOccurs="0" maxOccurs="unbounded"/>
+ </sequence>
+ </complexType>
+ <complexType name="IRPElement">
+ <sequence>
+ <element name="rDN" type="xn:dn"/>
+ <element name="IRPVersionSet" type="genericIRPData:VersionNumberSetType"/>
+ <element name="IRPManagementScope" type="entryPointIRPData:IRPManagementScope"
+ minOccurs="0"/>
+ </sequence>
+ </complexType>
+ <complexType name="IRPList">
+ <sequence>
+ <element name="IRPElement" type="entryPointIRPData:IRPElement"
+ maxOccurs="unbounded"/>
+ </sequence>
+ </complexType>
+ <complexType name="SupportedIRP">
+ <sequence>
+ <element ref="xn:systemDN"/>
+ <element name="IRPList" type="entryPointIRPData:IRPList"/>
+ </sequence>
+ </complexType>
+ <complexType name="SupportedIRPList">
+ <sequence>
+ <element name="supportedIRP" type="entryPointIRPData:SupportedIRP"
+ maxOccurs="unbounded"/>
+ </sequence>
+ </complexType>
+ <!-- getIRPOutline Request-->
+ <element name="getIRPOutline">
+ <complexType>
+ <sequence>
+ <element name="IRPVersion" type="genericIRPData:VersionNumberType"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!-- getIRPOutline Response -->
+ <element name="getIRPOutlineResponse">
+ <complexType>
+ <sequence>
+
+```
+
+```
+
+ <element name="supportedIRPList" type="entryPointIRPData:SupportedIRPList"/>
+ <element name="status" type="entryPointIRPData:OperationStatusTwo"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!-- getIRPOutline Fault -->
+ <element name="getIRPOutlineFault">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="InvalidIRPVersion"/>
+ <enumeration value="OperationFailed"/>
+ </restriction>
+ </simpleType>
+ </element>
+ <!-- getIRPReference Request -->
+ <element name="getIRPReference">
+ <complexType>
+ <sequence>
+ <element name="managerIdentifier" type="xn:dn"/>
+ <element ref="xn:systemDN"/>
+ <element name="rDN" type="xn:dn"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!-- getIRPReference Response -->
+ <element name="getIRPReferenceResponse">
+ <complexType>
+ <sequence>
+ <element name="irpReference" type="xn:dn"/>
+ <element name="status" type="entryPointIRPData:OperationStatusTwo"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!-- getIRPReference Fault -->
+ <element name="getIRPReferenceFault">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="InvalidRequestedParameters"/>
+ <enumeration value="OperationFailed"/>
+ </restriction>
+ </simpleType>
+ </element>
+ <!-- releaseIRPReference Request -->
+ <element name="releaseIRPReference ">
+ <complexType>
+ <sequence>
+ <element name="managerIdentifier" type="xn:dn"/>
+ <element name="irpReference" type="xn:dn"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!-- releaseIRPReference Response -->
+ <element name="releaseIRPReferenceResponse">
+ <complexType>
+ <sequence>
+ <element name="status" type="entryPointIRPData:OperationStatusTwo"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!-- releaseIRPReference Fault -->
+ <element name="releaseIRPReferenceFault">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="UnknownIRPReference"/>
+ <enumeration value="OperationFailed"/>
+ </restriction>
+ </simpleType>
+ </element>
+</schema>
+</types>
+<message name="getIRPOutline">
+ <part name="parameter" element="entryPointIRPData:getIRPOutline"/>
+</message>
+<message name="getIRPOutlineResponse">
+ <part name="parameter" element="entryPointIRPData:getIRPOutlineResponse"/>
+</message>
+<message name="getIRPOutlineFault">
+ <part name="parameter" element="entryPointIRPData:getIRPOutlineFault"/>
+
+```
+
+```
+</message>
+<message name="getIRPReference">
+ <part name="parameter" element="entryPointIRPData:getIRPReference"/>
+</message>
+<message name="getIRPReferenceResponse">
+ <part name="parameter" element="entryPointIRPData:getIRPReferenceResponse"/>
+</message>
+<message name="getIRPReferenceFault">
+ <part name="parameter" element="entryPointIRPData:getIRPReferenceFault"/>
+</message>
+<message name="releaseIRPReference">
+ <part name="parameter" element="entryPointIRPData:releaseIRPReference"/>
+</message>
+<message name="releaseIRPReferenceResponse">
+ <part name="parameter" element="entryPointIRPData:releaseIRPReferenceResponse"/>
+</message>
+<message name="releaseIRPReferenceFault">
+ <part name="parameter" element="entryPointIRPData:releaseIRPReferenceFault"/>
+</message>
+<portType name="EntryPointIRPPortType">
+ <operation name="getIRPOutline">
+ <input message="entryPointIRPSystem:getIRPOutline"/>
+ <output message="entryPointIRPSystem:getIRPOutlineResponse"/>
+ <fault name="getIRPOutlineFault" message="entryPointIRPSystem:getIRPOutlineFault"/>
+ </operation>
+ <operation name="getIRPReference">
+ <input message="entryPointIRPSystem:getIRPReference"/>
+ <output message="entryPointIRPSystem:getIRPReferenceResponse"/>
+ <fault name="getIRPReferenceFault" message="entryPointIRPSystem:getIRPReferenceFault"/>
+ </operation>
+ <operation name="releaseIRPReference">
+ <input message="entryPointIRPSystem:releaseIRPReference"/>
+ <output message="entryPointIRPSystem:releaseIRPReferenceResponse"/>
+ <fault name="releaseIRPReferenceFault"
+message="entryPointIRPSystem:releaseIRPReferenceFault"/>
+ </operation>
+</portType>
+<binding name="EntryPointIRPBinding" type="entryPointIRPSystem:EntryPointIRPPortType">
+ <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+ <operation name="getIRPOutline">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#getIRPOutline" style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+ <fault name="getIRPOutlineFault">
+ <soap:fault name="getIRPOutlineFault" use="literal"/>
+ </fault>
+ </operation>
+ <operation name="getIRPReference">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#getIRPReference"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+ <fault name="getIRPReferenceFault">
+ <soap:fault name="getIRPReferenceFault" use="literal"/>
+ </fault>
+ </operation>
+ <operation name="releaseIRPReference">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#releaseIRPReference"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+ <fault name="releaseIRPReferenceFault">
+ <soap:fault name="releaseIRPReferenceFault" use="literal"/>
+ </fault>
+ </operation>
+</binding>
+```
+
+```
+ </fault>
+ </operation>
+ </binding>
+ <service name="EntryPointIRPService">
+ <port name="EntryPointIRPPort" binding="entryPointIRPSystem:EntryPointIRPBinding">
+ <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.366#EntryPointIRP"/>
+ </port>
+ <port name="GenericIRPPort" binding="genericIRPSystem:GenericIRPBinding">
+ <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRP"/>
+ </port>
+ <port name="NotificationIRPNtfPort" binding="ntfIRPNtfSystem:NotificationIRPNtf">
+ <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtf"/>
+ </port>
+ </service>
+ </definitions>
+```
+
+# Annex D (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2010-09 | SA#49 | SP-100510 | -- | -- | | Presentation to SA for Information and Approval | 1.0.0 |
+| 2010-10 | -- | -- | -- | -- | | Publication | 10.0.0 |
+| 2012-09 | -- | -- | -- | -- | | Automatic upgrade from previous Release version | 11.0.0 |
+| 2014-09 | SA#65 | SP-140559 | 0001 | - | | Update the link from Solution Set to Information Service due to the end of Release 12 | 12.0.0 |
+| 2016-01 | - | - | - | - | | Update to Rel-13 version (MCC) | 13.0.0 |
+| 2016-06 | SA#72 | SP-160407 | 0002 | - | F | Update the link from IRP Solution Set to IRP Information Service | 13.1.0 |
+| 2017-03 | SA#75 | - | - | - | | Promotion to Release 14 without technical change | 14.0.0 |
+| 2017-06 | SA#76 | SP-170502 | 0003 | - | F | Update the link from IRP Solution Set to IRP Information Service | 14.1.0 |
+| 2018-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 |
+| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32392/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-18/32_series/32392/07b17a620c75522d53916a11e12d1bff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b82800a33be55c6013f35a19ab5a970bdab0bed9
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/07b17a620c75522d53916a11e12d1bff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:578a51af8d64b01a190aaa32a3bd3401a0ee8ae822caf464a642f551d8cbbbbe
+size 23527
diff --git a/marked/Rel-18/32_series/32392/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32392/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/32_series/32392/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32392/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bdc8fa31f9bcc431ae7836ba10eb67df219f28d
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d77fa2f642a69c86e5143a61f4ded7b1d7101cca3b8e44e9ff3167c3f9ab64fd
+size 5627
diff --git a/marked/Rel-18/32_series/32392/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-18/32_series/32392/731f533b0599c8e42a063f06e4332045_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb6579a62b112acc60737ff4bb91502ad13e2e47
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/731f533b0599c8e42a063f06e4332045_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c4b82887499a87b52cb3db7acf05cb2bcd52bd913e2a7af3ab7f5f81e18b6df
+size 24009
diff --git a/marked/Rel-18/32_series/32392/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-18/32_series/32392/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a38a4cb4d0b549f205858928477a5c05d3d9b24
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dd1ce9d6de6f1c1b3f48bf519bad07a24f828af559bda113864cb278f49f75b
+size 76332
diff --git a/marked/Rel-18/32_series/32392/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-18/32_series/32392/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a3acb02e057da71295733e6365d2182a77f0590
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30ff4cb907e118af9659bdcc4e33f4cbf866a2dfcd6c910f6c84914b52fa2bb6
+size 39782
diff --git a/marked/Rel-18/32_series/32392/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-18/32_series/32392/dbe553cf16dd14073b89a8263a428664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6176da433acda1e9ac919ac2939e0f426a5132a
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/dbe553cf16dd14073b89a8263a428664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1cba277b19636bc1a900c3aba6ea85c65364b10f562844d0fb0a27e8a2a0b55
+size 17770
diff --git a/marked/Rel-18/32_series/32392/raw.md b/marked/Rel-18/32_series/32392/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1369ac03190d1da0d50f42a062a2d9ba48417aff
--- /dev/null
+++ b/marked/Rel-18/32_series/32392/raw.md
@@ -0,0 +1,744 @@
+
+
+# 3GPP TS 32.392 V18.0.0 (2024-04)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Delta synchronization Integration Reference Point (IRP); Information Service (IS) (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+## --- **Keywords**
+
+telecom management
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|-------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 System overview ..... | 8 |
+| 4.1 System context ..... | 8 |
+| 5 Information Object Classes..... | 8 |
+| 5.1 Information entities imported and local labels..... | 8 |
+| 5.2 Class Diagram ..... | 9 |
+| 5.2.1 Attributes and relationships..... | 9 |
+| 5.2.2 Inheritance ..... | 9 |
+| 5.3 Information Object Class (IOC) definitions..... | 10 |
+| 5.3.1 DeltaSynchronizationLRP ..... | 10 |
+| 5.3.1.1 Definition ..... | 10 |
+| 5.4 Information relationship definitions..... | 10 |
+| 5.5 Information attribute definition..... | 10 |
+| 6 Interface definition..... | 11 |
+| 6.1 Class diagram..... | 11 |
+| 6.2 Generic rules ..... | 11 |
+| 6.3 deltaSynchGenericParts Interface (M) ..... | 12 |
+| 6.3.1 Operation manageDeltaSynchronization (M)..... | 12 |
+| 6.3.1.1 Definition ..... | 12 |
+| 6.3.1.2 Input parameters ..... | 12 |
+| 6.3.1.3 Output parameters..... | 12 |
+| 6.3.1.4 Pre-condition..... | 12 |
+| 6.3.1.5 Post-condition ..... | 12 |
+| 6.3.1.6 Exceptions..... | 13 |
+| 6.3.2 Operation getAvailableDeltaSynchPoints (O)..... | 14 |
+| 6.3.2.1 Definition ..... | 14 |
+| 6.3.2.2 Input parameters ..... | 14 |
+| 6.3.2.3 Output parameters..... | 14 |
+| 6.3.2.4 Pre-condition..... | 15 |
+| 6.3.2.5 Post-condition ..... | 15 |
+| 6.3.2.6 Exceptions..... | 15 |
+| 6.3.3 Notification notifyNewDeltaSynchPoint (O)..... | 16 |
+| 6.3.3.1 Definition ..... | 16 |
+| 6.3.3.2 Input Parameters ..... | 16 |
+| 6.3.3.3 Triggering Event..... | 17 |
+| 6.3.3.3.1 From-state..... | 17 |
+| 6.3.3.3.2 To-state..... | 17 |
+| 6.3.4 Notification notifyStatusOfDeltaSynchChanged (O)..... | 18 |
+| 6.3.4.1 Definition ..... | 18 |
+| 6.3.4.2 Input Parameters ..... | 18 |
+| 6.3.4.3 Triggering Event..... | 18 |
+| 6.3.4.3.1 From-state..... | 18 |
+| 6.3.4.3.2 To-state..... | 18 |
+| 6.4 deltaSynchOfCMData Interface (O)..... | 19 |
+| 6.4.1 Operation triggerDeltaSynchOfCMData (M)..... | 19 |
+
+| | | |
+|-------------------------------|-----------------------------------------------------------|-----------|
+| 6.4.1.1 | Definition ..... | 19 |
+| 6.4.1.2 | Input parameters ..... | 20 |
+| 6.4.1.3 | Output parameters ..... | 21 |
+| 6.4.1.4 | Pre-condition ..... | 22 |
+| 6.4.1.5 | Post-condition ..... | 22 |
+| 6.4.1.6 | Exceptions ..... | 22 |
+| 6.5 | deltaSynchOfAlarmData Interface (O) ..... | 23 |
+| 6.5.1 | Operation triggerDeltaSynchOfAlarms (M) ..... | 23 |
+| 6.5.1.1 | Definition ..... | 23 |
+| 6.5.1.2 | Input parameters ..... | 24 |
+| 6.5.1.3 | Output parameters ..... | 25 |
+| 6.5.1.4 | Pre-condition ..... | 25 |
+| 6.5.1.5 | Post-condition ..... | 26 |
+| 6.5.1.6 | Exceptions ..... | 26 |
+| 7 | Operation Modes ..... | 27 |
+| 7.1 | Delta Synchronization Mode DSM1 ..... | 27 |
+| 7.2 | Delta Synchronization Mode DSM2 ..... | 27 |
+| 7.3 | Delta Synchronization Mode DSM3 ..... | 27 |
+| <b>Annex A (informative):</b> | <b>Modes of operation for delta synchronization .....</b> | <b>28</b> |
+| A.1 | Operation Mode DSM1 ..... | 28 |
+| A.2 | Operation Mode DSM2 ..... | 28 |
+| A.3 | Operation Mode DSM3 ..... | 28 |
+| <b>Annex B (informative):</b> | <b>Change history .....</b> | <b>29</b> |
+
+# --- 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
+
+32.391: "Delta Synchronization Integration Reference Point (IRP); Requirements".
+
+**32.392: "Delta Synchronization Integration Reference Point (IRP); Information Service (IS)".**
+
+32.396: "Delta Synchronization Integration Reference Point (IRP); Solution Set (SS) definitions".
+
+The Itf-N interface is built up by a number of IRPs and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+IRPManagers (typically Network Management Systems) and IRPAgents (typically EMs or NEs) synchronize their data concerning alarms or configuration data. In certain scenarios this synchronization is lost or not done. This IRP provides functionality to significantly reduces the amount of data which needs to be transferred in order to re-establish synchronization.
+
+# --- 1 Scope
+
+The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e. changed, were created or deleted) from a synchronization point onwards.
+
+The present document is the Information Service of Delta Synchronization IRP. It defines, for the purpose of Delta Synchronization, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
+
+# --- 2 References
+
+The following documents contain provisions that, 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
+- [4] 3GPP TS 32.391: "Telecommunication management; Delta Synchronization Integration Reference Point (IRP): Requirements".
+- [5] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [6] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
+- [7] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [8] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
+- [9] 3GPP TS 32.662: "Telecommunication management; Configuration Management (CM); Kernel CM; Information Service (IS)".
+- [10] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT); Integration Reference Point (IRP): Information Service (IS)".
+- [11] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.391 [4] apply.
+
+**synchPoint Creation Policy:** The IRP Agent may create synchronizationPoint in different policies. These policies are called synchPoint creation policies. There are two synchPoint Creation policies:
+
+**AgentScheduledPolicy:** A new synchronizationPoint is created by the IRP Agent on the IRP Agent's internal decision, that decision is not related to any IRP Manager's operations. In this mode, after successful delta synchronization, the IRP Agent does not create a new synchronizationPoint.
+
+**ManagerRequestPolicy:** The new synchronizationPoint is requested by the IRP Manager. The exact time for this synchronizationPoint is determined by the IRP Agent.
+
+The IRP Agent that supports either AgentScheduledPolicy or ManagerRequestPolicy to create a new synchronizationPoint can claim compliance to this specification.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|-------|----------------------------------------------|
+| CM | Configuration Management |
+| EM | Element Manager |
+| IOC | Information Object Class |
+| IRP | Integration Reference Point |
+| IS | Information Service (see 3GPP TS 32.101 [1]) |
+| Itf-N | Interface N |
+| NE | Network Element |
+
+# 4 System overview
+
+## 4.1 System context
+
+The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [5], clause 4.7.
+
+In addition, the set of related IRP(s) relevant to the present IRP is shown in figures 4.1-1 and 4.1-2.
+
+
+
+The diagram illustrates System Context A. On the left, a box labeled 'IRPManager' is inside a larger box labeled 'NM'. A solid line connects the 'IRPManager' box to another box labeled 'IRPAgent' inside a larger box labeled 'EM'. A dashed vertical line separates the NM and EM boxes, with the label 'Itf-N' below it. A curved arrow points from the 'Itf-N' label to a list of three items: 'Notification IRP', 'Delta', and 'Synchronization IRP'. To the right of the 'IRPAgent' box, a dotted line connects it to a box labeled 'NEs'.
+
+Figure 4.1.1: System Context A. A diagram showing an IRPManager (NM) connected to an IRPAgent (EM) via an Itf-N interface. The IRPAgent is connected to multiple NEs. The Itf-N interface is associated with Notification IRP, Delta, and Synchronization IRP.
+
+Figure 4.1.1: System Context A
+
+
+
+The diagram illustrates System Context B. On the left, a box labeled 'IRPManager' is inside a larger box labeled 'NM'. A solid line connects the 'IRPManager' box to another box labeled 'IRPAgent' inside a larger box labeled 'NE'. A dashed vertical line separates the NM and NE boxes, with the label 'Itf-N' below it. A curved arrow points from the 'Itf-N' label to a list of three items: 'Notification IRP', 'Delta', and 'Synchronization IRP'.
+
+Figure 4.1.2: System Context B. A diagram showing an IRPManager (NM) connected to an IRPAgent (NE) via an Itf-N interface. The Itf-N interface is associated with Notification IRP, Delta, and Synchronization IRP.
+
+Figure 4.1.2 : System Context B
+
+# 5 Information Object Classes
+
+## 5.1 Information entities imported and local labels
+
+| Label reference | Local label |
+|-----------------------------------------------------------------|-------------------|
+| 3GPP TS 32.622 [6], information object class, Top | Top |
+| 3GPP TS 32.622 [6], information object class, IRPAgent | IRPAgent |
+| 3GPP TS 32.622 [6], information object class, GenericIRP | GenericIRP |
+| 3GPP TS 32.312 [7], information object class, ManagedGenericIRP | ManagedGenericIRP |
+| 3GPP TS 32.302 [3], information object class, NotificationIRP | NotificationIRP |
+
+## 5.2 Class Diagram
+
+### 5.2.1 Attributes and relationships
+
+This clause introduces the set of Information Object Classes (IOCs) that encapsulate information within the IRP Agent. The intent is to identify the information required for the delta synchronization IRP Agent implementation of its operations and notification emission. This clause provides the overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes.
+
+
+
+```
+classDiagram
+ class ManagedGenericIRP["<<InformationObjectClass>> ManagedGenericIRP (from TS 32.312)"]
+ class DeltaSynchronizationIRP["<<InformationObjectClass>> DeltaSynchronizationIRP"]
+ ManagedGenericIRP <|-- DeltaSynchronizationIRP
+```
+
+The diagram shows two classes. The top class is labeled <<InformationObjectClass>> ManagedGenericIRP (from TS 32.312). The bottom class is labeled <<InformationObjectClass>> DeltaSynchronizationIRP. A vertical line with an open triangle arrowhead points from the bottom class to the top class, indicating inheritance.
+
+UML Class Diagram showing ManagedGenericIRP and DeltaSynchronizationIRP classes.
+
+Figure 5.2.1: Information Object Class (IOC) UML Diagram
+
+### 5.2.2 Inheritance
+
+
+
+```
+classDiagram
+ class Top["<<InformationObjectClass>> Top (from TS 32.622)"]
+ class GenericIRP["<<InformationObjectClass>> GenericIRP (from TS 32.622)"]
+ class ManagedGenericIRP["<<InformationObjectClass>> ManagedGenericIRP (from TS 32.312)"]
+ class DeltaSynchronizationIRP["<<InformationObjectClass>> DeltaSynchronizationIRP"]
+ Top <|-- GenericIRP
+ GenericIRP <|-- ManagedGenericIRP
+ ManagedGenericIRP <|-- DeltaSynchronizationIRP
+```
+
+The diagram shows a vertical inheritance hierarchy of four classes. From top to bottom, they are: Top (from TS 32.622), GenericIRP (from TS 32.622), ManagedGenericIRP (from TS 32.312), and DeltaSynchronizationIRP. Each class is connected to the one above it by a vertical line with an open triangle arrowhead pointing upwards, indicating that each class inherits from the one above it.
+
+UML Class Diagram showing the inheritance hierarchy of Top, GenericIRP, ManagedGenericIRP, and DeltaSynchronizationIRP classes.
+
+Figure 5.2.2: Information Object Class (IOC) Inheritance UML Diagram
+
+## 5.3 Information Object Class (IOC) definitions
+
+### 5.3.1 DeltaSynchronizationIRP
+
+#### 5.3.1.1 Definition
+
+DeltaSynchronizationIRP is the representation of the delta synchronization capabilities specified by the present document. This IOC inherits from ManagedGenericIRP IOC specified in 3GPP TS 32.312 [7].
+
+## 5.4 Information relationship definitions
+
+none
+
+## 5.5 Information attribute definition
+
+none
+
+# 6 Interface definition
+
+## 6.1 Class diagram
+
+
+
+```
+classDiagram
+ class DeltaSynchronizationIRP {
+ <<InformationObjectClass>>
+ }
+ class DeltaSynchOfCMData {
+ <<Interface>>
+ triggerDeltaSynchOfCMData
+ }
+ class DeltaSynchGenericParts {
+ <<Interface>>
+ manageDeltaSynchronization
+ getAvailableDeltaSynchPoints {
+ <<opt>>
+ }
+ notifyNewDeltaSynchPoint {
+ <<opt>>
+ }
+ notifyStatusOfDeltaSynchronization {
+ <<opt>>
+ }
+ }
+ class DeltaSynchOfAlarmData {
+ <<Interface>>
+ triggerDeltaSynchOfAlarms
+ }
+ DeltaSynchronizationIRP --> DeltaSynchOfCMData : <<may realize>>
+ DeltaSynchronizationIRP --> DeltaSynchGenericParts : <<realizes>>
+ DeltaSynchronizationIRP --> DeltaSynchOfAlarmData : <<may realize>>
+```
+
+The diagram illustrates the relationship between a base class and three interfaces. The base class, `DeltaSynchronizationIRP` (labeled as `<<InformationObjectClass>>`), is shown at the top. Below it are three interface boxes. The first interface, `DeltaSynchOfCMData` (labeled as `<<Interface>>`), contains the operation `triggerDeltaSynchOfCMData`. The second interface, `DeltaSynchGenericParts` (labeled as `<<Interface>>`), contains the operation `manageDeltaSynchronization` and three optional operations: `getAvailableDeltaSynchPoints`, `notifyNewDeltaSynchPoint`, and `notifyStatusOfDeltaSynchronization`, each marked with `<<opt>>`. The third interface, `DeltaSynchOfAlarmData` (labeled as `<<Interface>>`), contains the operation `triggerDeltaSynchOfAlarms`. Arrows indicate the relationships: `<<may realize>>` from the base class to the first and third interfaces, and `<<realizes>>` from the base class to the second interface.
+
+UML Class diagram showing DeltaSynchronizationIRP class and its associated interfaces.
+
+Figure 6.1: Class diagram
+
+## 6.2 Generic rules
+
+**Rule 1:** each operation with at least one input parameter supports a pre-condition `valid_input_parameter` which indicates that all input parameters shall be valid with regards to their information type. Additionally, each such operation supports an exception `operation_failed_invalid_input_parameter` which is raised when pre-condition `valid_input_parameter` is false. The exception has the same entry and exit state.
+
+**Rule 2:** each operation with at least one optional input parameter supports a set of pre-conditions `supported_optional_input_parameter_xxx` where "xxx" is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation supports an exception `operation_failed_unsupported_optional_input_parameter_xxx` which is raised when (a) the pre-condition `supported_optional_input_parameter_xxx` is false and (b) the named optional input parameter is carrying information. The exception has the same entry and exit state.
+
+**Rule 3:** each operation shall support a generic exception `operation_failed_internal_problem` which is raised when an internal problem occurs and that the operation cannot be completed. The exception has the same entry and exit state.
+
+## 6.3 deltaSynchGenericParts Interface (M)
+
+### 6.3.1 Operation manageDeltaSynchronization (M)
+
+#### 6.3.1.1 Definition
+
+This operation allows an IRPManager to activate or deactivate the delta synchronization functionality for CMData or/and AlarmData. A change of at least one activation status triggers the sending of `notifyStatusOfDeltaSynchronization`.
+
+As default settings the delta synchronization functionality for both alarms and CM data is deactivated.
+
+#### 6.3.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|-------------------------------------------|-----------|----------------------------------------|--------------------------------------------------------------------|
+| <code>managerReference</code> | M | See 32.302 [3] | See 3GPP TS 32.302 [3] |
+| <code>manageDeltaSynchForAlarmData</code> | CM | ENUM (<br>Activate,<br>Deactivate<br>) | Constraint:<br><code>manageDeltaSynchForCMData</code> is absent. |
+| <code>manageDeltaSynchForCMData</code> | CM | ENUM (<br>Activate,<br>Deactivate<br>) | Constraint:<br><code>manageDeltaSynchForAlarmData</code> is absent |
+
+#### 6.3.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|---------------------|-----------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>status</code> | M | ENUM (<br>Success,<br>Failure<br>) | If the functionality is already activated/deactivated the output value is <code>Success</code> and no <code>notifyStatusOfDeltaSynchronization</code> is triggered.<br>Failure reasons are:<br><code>DeltaSynchNotSupportedForCMData</code> ,<br><code>DeltaSynchNotSupportedForAlarmData</code> and other unspecified reasons. |
+
+#### 6.3.1.4 Pre-condition
+
+`deltaSynchSupported`
+
+| Assertion Name | Definition |
+|----------------------------------|-----------------------------------------------------------------|
+| <code>deltaSynchSupported</code> | The IRP Agent supports the delta synchronization functionality. |
+
+#### 6.3.1.5 Post-condition
+
+`requestGranted`
+
+| Assertion Name | Definition |
+|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>requestGranted</code> | The delta synchronization functionality is activated or deactivated according to the input parameters <code>manageDeltaSynchForAlarmData</code> and <code>manageDeltaSynchForCMData</code> . |
+
+#### 6.3.1.6 Exceptions
+
+| Name | Properties |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.2 Operation getAvailableDeltaSynchPoints (O)
+
+#### 6.3.2.1 Definition
+
+This operation allows an IRPManager to request information about the synchronization points for which the IRPManager can request delta synch data from the IRPAgent.
+
+#### 6.3.2.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|----------------------------------|-----------|------------------|-----------------------------------------------------------|
+| managerReference | O | See 32.302 [3] | See 3GPP TS 32.302 [3] |
+| synchPointsForCMDataRequested | CM | Boolean | Constraint:<br>synchPointsForAlarmDataRequested is absent |
+| synchPointsForAlarmDataRequested | CM | Boolean | Constraint:<br>synchPointsForCMDataRequested is absent |
+
+Remark: The constraints allow the simultaneous presence of both synchPointsForCMDataRequested and synchPointsForAlarmDataRequested in the input.
+
+#### 6.3.2.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|-------------------------|-----------|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| synchPointListForAlarms | CM | LIST of SynchPoint | Constraint:<br>synchPointsForAlarmDataRequested was present in the input and had value TRUE.<br><br>If synchPointsForAlarmDataRequested was not present, then this parameter shall not be present in the output.<br><br>If delta synchronization for alarm data is deactivated, then this list shall be empty.<br><br>The content of this list is valid, if the status is either Success or DeltaSynchNotSupportedForCMData or DeltaSynchForCMDataDeactivated |
+| synchPointListForCMData | CM | LIST of SynchPoint | Constraint:<br>synchPointsForCMDataRequested was present in the input and had value TRUE.<br><br>If synchPointsForCMDataRequested was not present, then this parameter shall not be present in the output.<br><br>If delta synchronization for CM data is deactivated, then this list shall be empty.<br><br>The content of this list is valid, if the status is either Success or DeltaSynchNotSupportedForAlarmData or DeltaSynchForAlarmDataDeactivated |
+| status | M | ENUM ( Success, Failure ) | If both delta synchronization for CM data and alarm data are deactivated, then status == DeltaSynchNotActive.<br>Failure reasons are:<br>DeltaSynchNotSupportedForCMData,<br>DeltaSynchNotSupportedForAlarmData,<br>DeltaSynchNotActive,<br>DeltaSynchForCMDataDeactivated,<br>DeltaSynchForAlarmDataDeactivated,<br>Failure and other unspecified reasons. |
+
+#### 6.3.2.4 Pre-condition
+
+deltaSynchronizationSupported
+
+| Assertion Name | Definition |
+|-------------------------------|-------------------------------------------------------|
+| deltaSynchronizationSupported | The delta synchronization functionality is supported. |
+
+#### 6.3.2.5 Post-condition
+
+synchPointListsReturned
+
+| Assertion Name | Definition |
+|-------------------------|----------------------------------------|
+| synchPointListsReturned | The available information is returned. |
+
+#### 6.3.2.6 Exceptions
+
+| Name | Properties |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+### 6.3.3 Notification notifyNewDeltaSynchPoint (O)
+
+#### 6.3.3.1 Definition
+
+If the IRP Agent has successfully performed the creation of a new delta synchronization point, then this notification is sent out to all subscribed IRP Managers. If an implementation chooses that the new delta synchronization point shall only be valid for specific IRP Managers, it can send the notification only to those.
+
+This notification is triggered by any of the following:
+
+1. An operation `triggerDeltaSynchOfCMData` or `triggerDeltaSynchOfAlarmData` returns the status `== Success` and a new synchronization point is created).
+2. An IRP Agent's internal decision to create a new synchronization point and that decision is not related to any IRP Manager's operations.
+
+The use of the `synchronizationPoint` delivered in this notification may result in different views of the managed instances by IRP Manager and IRP Agent, in some scenarios. To avoid such pitfall, it is recommended that the IRP Manager should do the following:
+
+1. Establish the first `synchronizationPoint` using the full synchronization; and
+2. Use the operations in the future to a) maintain/track the list of synchronization points and b) to update its view of the CM managed instances and FM alarm information.
+
+#### 6.3.3.2 Input Parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------------------------------|-----------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>newSynchPoint</code> | M, Y | GeneralizedTime | |
+| <code>requestedSynchPoint</code> | M, N | GeneralizedTime | This parameter allows an IRP Manager to relate this notification to its <code>triggerDeltaSynchOfCM/AlarmData</code> request.<br>In case the <code>newSynchPoint</code> was triggered by an IRP Agent's internal decision this parameter carries the value 0. |
+| <code>deltaSynchPointType</code> | M, Y | ENUM (<br><code>deltaSynchPointForAlarm</code> ,<br><code>deltaSynchPointForCMData</code><br>) | |
+| <code>triggeredByAgentOrManager</code> | M, Y | ENUM (<br><code>iRPAgent</code> ,<br><code>iRPManager</code><br>) | This parameter indicates whether the creation of the new synchronization point was triggered by an IRP Agent's internal decision or by the request of an IRP Manager for an operation <code>triggerDeltaSynchOfCMData/alarms</code> |
+| <code>agentOrManagerReference</code> | M, Y | String | In case the new synch point was triggered by an IRP Agent's internal decision this parameter carries the reference of the IRP Agent, else the <code>managerReference</code> of the IRP Manager which requested the operation <code>triggerDeltaSynchOfCMData/alarms</code> |
+
+#### 6.3.3.3 Triggering Event
+
+##### 6.3.3.3.1 From-state
+
+`newSynchPointSuccessfullyCreated`
+
+| Assertion Name | Definition |
+|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| <code>newSynchPointSuccessfullyCreated</code> | The IRP Agent has successfully performed the to creation of a new delta synchronization point, see clause 6.3.3.1. |
+
+##### 6.3.3.3.2 To-state
+
+`irpManagersInformedAboutNewSynchPoint`
+
+| Assertion Name | Definition |
+|----------------------------------------------------|------------------------------------------------------------------|
+| <code>irpManagersInformedAboutNewSynchPoint</code> | The involved IRP Managers are informed about the new synchPoint. |
+
+### 6.3.4 Notification notifyStatusOfDeltaSynchChanged (O)
+
+#### 6.3.4.1 Definition
+
+If the IRP Agent has successfully performed a `manageDeltaSynchronization` request and the status of delta synchronization for alarm data and/or for CM data has changed, then this notification is sent out.
+
+#### 6.3.4.2 Input Parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|-------------------------------------------|-----------|------------------------------------------|------------------------|
+| <code>managerReference</code> | M, Y | See 32.302 [3] | See 3GPP TS 32.302 [3] |
+| <code>deltaSynchStatusForCMData</code> | M, Y | ENUM (<br>Activated,<br>Deactivated<br>) | |
+| <code>deltaSynchStatusForAlarmData</code> | M, Y | ENUM (<br>Activated,<br>Deactivated<br>) | |
+
+#### 6.3.4.3 Triggering Event
+
+##### 6.3.4.3.1 From-state
+
+`statusOfDeltaSynchWasChanged`
+
+| Assertion Name | Definition |
+|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>statusOfDeltaSynchWasChanged</code> | The IRP Agent has successfully performed a <code>manageDeltaSynchronization</code> request and at least one delta synchronization status changed. |
+
+##### 6.3.4.3.2 To-state
+
+`irpManagersInformedAboutTheStatusChange`
+
+| Assertion Name | Definition |
+|------------------------------------------------------|-----------------------------------------------------------------|
+| <code>irpManagersInformedAboutTheStatusChange</code> | The IRP Managers are informed about the new delta synch status. |
+
+## 6.4 `deltaSynchOfCMDData` Interface (O)
+
+### 6.4.1 Operation `triggerDeltaSynchOfCMDData` (M)
+
+#### 6.4.1.1 Definition
+
+This operation allows an IRPManager to request information about CMDData which has changed since the specified synchronization point. The information returned may be filtered/restricted by the input parameters `baseMOInstance` and `scope`.
+
+If the operation is successful, then a new delta synchronization point for CMDData is created, if the IRPAgent supports the `ManagerRequestPolicy`.
+
+If the IRPAgent only supports `AgentScheduledPolicy`, the latest synchronizationPoint is returned to the IRPManager as the `newSynchPoint`.
+
+The Synchronization points created are not related to `baseMOInstance` and `scope` used in operations. In other words, it is not possible to establish synchronization points for just a subset of the managed objects.
+
+For obtaining an initial synchronization point (e.g. in the case that the IRPManager does not have any valid configuration management information), IRPManager shall use this operation `triggerDeltaSyncOfCMDData` as follows to obtain the first synch point:
+
+- the input parameter `synchPoint` is present and the value is set to 0.
+
+The IRPAgent responds with `newSynchPoint` a Synchronization point that the IRPManager can use as the input parameter `synchPoint` for future `triggerDeltaSynchOfCMDData` requests.
+
+A Solution Set may choose to split this operation in several operations (e.g. operations to get "iterator" which fulfil the criteria and other operations to retrieve the detailed information of the files from the "iterator").
+
+If in the output of this operation a reference to a file is identified, then the availability of the file shall be announced by a `notifyFileReady` notification (see [10]).
+
+#### 6.4.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|------------------|-----------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| managerReference | O | See TS 32.302 [3] | See 3GPP TS 32.302 [3] |
+| cmDataRequested | M | ENUM (<br>DNsOnly,<br>CompleteDataSet) | <p>If cmDataRequested==DNsOnly: Only the DNs of MOIs are delivered in the output, not the complete data set of the MOIs.</p> <p>If dataRequested==CompleteDataSet: The complete data set of MOIs (including the attributes and their values) are delivered in the output.</p> |
+| baseMOInstance | O | See TS 32.602 [8] | <p>See 3GPP TS 32.602 [8]</p> <p>This parameter is used to reduce the amount of data which is returned in deltaLists.</p> <p>Remark: The parameter objectInstance of a notifyCMsynchronizationRecommended notification could be used as input here.</p> <p>If this parameter is absent, then the all MOIs are used.</p> |
+| scope | O | See TS 32.662 [9] | <p>See 3GPP TS 32.662 [9]</p> <p>This parameter can be used to reduce the amount of delta data which is returned in deltaLists.</p> <p>If baseMOInstance is present, then this parameter shall be present. If the parameter baseMOInstance is absent, then this parameter must be absent.</p> <p>If the IRP-Agent has no complete view of the requested scope, then it shall deliver all known delta data within the scope.</p> |
+| synchPoint | M | GeneralizedTime | The IRPManager asks for data which changed since this synchPoint. |
+
+#### 6.4.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| deltaLists | CM | <pre> STRUCT < STRUCT < startTime, endTime > , STRUCT < listOfCreatedInstances , listOfChangedInstances , listOfDeletedInstances > > listOf...Instances LIST: either LIST of STRUCT <MOInstance [, attributeList] > or a list of file reference </pre> | <p>The second STRUCT contains the data which changed between <code>startTime</code> and <code>endTime</code>.</p> <p>In case the value of <code>status</code> equals "Success" an empty list indicates that the information at <code>startTime</code> and the information at <code>endTime</code> are identical..</p> <p>Constraint:<br/>If <code>status</code> is different from <code>Success</code> OR input <code>synchPoint==0</code>, then this parameter shall be absent, else it shall be present.</p> <p>Remark: Square brackets indicate optional parts in the data structure. If the IRPManager requested <code>DNsOnly</code>, then the attribute list shall be absent.</p> <p>If the values of a managed object, identified by its DN, at <code>startTime</code> and at <code>endTime</code> are identical, then</p> <ul style="list-style-type: none"> <li>▪ either nothing about it shall be reported in the <code>listOfChangedInstances</code></li> </ul> <p>or</p> <ul style="list-style-type: none"> <li>▪ the value at <code>endTime</code> (or <code>startTime</code>) reported, provided that the value has changed between <code>startTime</code> and <code>endTime</code></li> </ul> <p>If the managed object does not exist at <code>startTime</code> and <code>endTime</code>, then nothing about it shall be reported, if the IRPAgent can fulfil the delta synchronization request exactly, i.e. for exactly the request <code>synchPoint</code>.</p> <p>If an instance is deleted and a new instance is created with the same identifier as the deleted instance, then both the creation and the deletion shall be reported.</p> <p>If several file references are used, then IRPManager shall process them in sequence, i.e. first file first, second file as second, etc. .</p> |
+| newSynchPoint | CM | GeneralizedTime | <p>Constraint:<br/><code>baseMOInstance</code> and <code>scope</code> were absent in the input</p> <p>This parameter defines a new synchronization point which can be used as input to this operation in the future.</p> |
+| Status | M | <pre> ENUM ( Success, Failure ) </pre> | <p>Failure reasons are:<br/><code>SynchPointTooLongAgo</code>,<br/><code>TooManyChangesFullSynchronizationRecommended</code>,<br/><code>SynchPointUnknown</code>,<br/><code>DeltaSynchNotSupportedForCMData</code>,<br/><code>DeltaSynchForCMDataDeactivated</code>,<br/>and other unspecified reasons.</p> <p>In case the deltaSynchronizationIRP's data has been rebuilt, e.g. after a "crash", <code>SynchPointUnknown</code> is used.</p> |
+
+#### 6.4.1.4 Pre-condition
+
+baseMOInstanceExists AND deltaSynchronizationOfCMDataIsActive
+
+| Assertion Name | Definition |
+|--------------------------------------|-----------------------------------------------------------------------------------|
+| baseMOInstanceExists | baseMOInstance does exist (Assertion == TRUE if no baseMOInstance was specified). |
+| deltaSynchronizationOfCMDataIsActive | The delta synchronization functionality for CMData is active |
+
+#### 6.4.1.5 Post-condition
+
+deltaListsReturned
+
+| Assertion Name | Definition |
+|--------------------|---------------------------------------|
+| deltaListsReturned | The required information is returned. |
+
+#### 6.4.1.6 Exceptions
+
+| Name | Properties |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| operation_failed | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+## 6.5 deltaSynchOfAlarmData Interface (O)
+
+### 6.5.1 Operation triggerDeltaSynchOfAlarms (M)
+
+#### 6.5.1.1 Definition
+
+This operation allows an IRPManager to request information about all alarm information which has changed since the specified synchronization point. The information returned may be filtered/restricted by the input parameters `baseMOInstance` and `scope`.
+
+If the operation is successful, then a new delta synchronization point for alarm data is created, if the IRPAgent supports the `ManagerRequestPolicy`.
+
+If the IRPAgent only supports `AgentScheduledPolicy`, the latest synchronizationPoint is returned to the IRPManager as the `newSynchPoint`.
+
+The synchronization points created are not related to `baseMOInstance` and `scope` used in operations. In other words, it is not possible to establish synchronization points for just a subset of the managed objects
+
+For obtaining an initial synchronization point (e.g. in the case that the IRPManager does not have any valid alarm information), IRPManager shall use this operation `triggerDeltaSynchOfAlarms` as follows to obtain the first synch point:
+
+- the input parameter `synchPoint` is present and the value is set to 0.
+
+The IRPAgent responds with `newSynchPoint` a synchronization point that the IRPManager can use as input parameter `synchPoint` for future `triggerDeltaSynchOfAlarms` requests.
+
+A Solution Set may choose to split this operation in several operations (e.g. operations to get "iterator" which fulfil the criteria and other operations to retrieve the detailed information of the files from the "iterator").
+
+If in the output of this operation a reference to a file is identified, then the availability of the file shall be announced by a `notifyFileReady` notification (see [10]).
+
+#### 6.5.1.2 Input parameters
+
+| Parameter Name | Qualifier | Information type | Comment |
+|--------------------|-----------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| managerReference | O | See 3GPP TS 32.302 [3] | See 3GPP TS 32.302 [3] |
+| alarmDataRequested | M | ENUM (<br>AlarmIdsOnly,<br>CompleteAlarmInformation<br>) | <p>If dataRequested== AlarmIdsOnly: Only the alarmed values are delivered in the output, not the complete alarm information.</p> <p>If dataRequested==CompleteDataSet: The complete alarm information are delivered in the output.</p> |
+| baseMOInstance | O | See 3GPP TS 32.602 [8] | <p>See 3PP TS 32.602 [8]</p> <p>This parameter is used to reduce the amount of data which is returned in deltaLists.</p> <p>Remark: The parameter objectInstance of a notifyAlarmListRebuilt notification could be used as input here.</p> <p>If this parameter is absent, then the all MOIs visible via Itf-N is used.</p> |
+| scope | O | See 3PP TS 32.662 [9] | <p>See 3PP TS 32.662 [9]</p> <p>This parameter can be used to reduce the amount of delta data which is returned in deltaLists.</p> <p>If the parameter baseMOInstance is present, then this parameter shall be present. If the parameter baseMOInstance is absent, then this parameter must be absent.</p> <p>If the IRP-Agent has no complete view of the requested scope, then it shall deliver all known delta data within the scope.</p> |
+| synchPoint | M | GeneralizedTime | The IRPManager asks for data which changed since this synchPoint. |
+
+#### 6.5.1.3 Output parameters
+
+| Parameter Name | Qualifier | Matching Information | Comment |
+|----------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| deltaLists | CM | <pre> STRUCT < STRUCT < startTime, endTime > , STRUCT < listOfNewAlarms , listOfChangedAlarms, listOfDeletedAlarms > > listOf...Alarms LIST: either LIST of STRUCT <alarm [, parameterList] > or a filename </pre> | <p>These second STRUCT contains the data which changed between <code>startTime</code> and <code>endTime</code>.</p> <p>In case the value of <code>status</code> equals "Success" an empty list indicates that the information at <code>startTime</code> and the information at <code>endTime</code> are identical.</p> <p>Constraint:<br/>If value of <code>status</code> is different from <code>Success</code> OR input <code>synchPoint==0</code>, then this parameter shall be absent, else it shall be present.</p> <p>Remark: Square brackets indicate optional parts in the data structure. If the <code>IRPManager</code> requested <code>AlarmIdsOnly</code>, then the parameter list shall be absent.</p> <p>If an alarm information, identified by its <code>alarmId</code>, at <code>startTime</code> and at <code>endTime</code> is identical, then either</p> <ul style="list-style-type: none"> <li>nothing about it shall be reported</li> </ul> <p>or</p> <ul style="list-style-type: none"> <li>the alarm information at <code>endTime</code> (or <code>startTime</code>) reported, provided that the alarm information has changed between <code>startTime</code> and <code>endTime</code>.</li> </ul> <p>If an alarm is raised and cleared again and acknowledged between <code>startTime</code> and <code>endTime</code>, then these changes should not be reported, if the <code>IRPAgent</code> can fulfil the delta synchronization request exactly</p> <p>If an alarm is deleted and a new alarm occurs with the same parameter values as the deleted alarm, then both the occurrence and the deletion shall be reported.</p> <p>If several file references are used, then <code>IRPManager</code> shall process them in sequence, i.e. first file first, second file as second, etc. .</p> |
+| newSynchPoint | CM | GeneralizedTime | <p>Constraint:<br/><code>baseMOInstance</code> and <code>scope</code> were absent in the input</p> <p>This parameters defines a new synchronization point which can be used as input to this operation in the future.</p> |
+| Status | M | <pre> ENUM ( Success, Failure ) </pre> | <p>Failure reasons are:<br/><code>SynchPointTooLongAgo</code>,<br/><code>TooManyChangesFullSynchronizationRecommended</code>,<br/><code>SynchPointUnknown</code>,<br/><code>DeltaSynchNotSupportedForAlarmData</code>,<br/><code>DeltaSynchForAlarmsNotActive</code>,<br/>and other unspecified reasons.</p> <p>In case the <code>deltaSynchronizationIRP</code>'s data has been rebuilt, e.g. after a "crash", <code>SynchPointUnknown</code> is used.</p> |
+
+#### 6.5.1.4 Pre-condition
+
+`baseMOInstanceExists` AND `deltaSynchOfAlarmDataIsActive`
+
+| Assertion Name | Definition |
+|--------------------------------------------|--------------------------------------------------------------------------------------------------------------|
+| <code>baseMOInstanceExists</code> | <code>baseMOInstance</code> does exist. (Assertion == TRUE if no <code>baseMOInstance</code> was specified). |
+| <code>deltaSynchOfAlarmDataIsActive</code> | The delta synchronization functionality for alarms is active |
+
+#### 6.5.1.5 Post-condition
+
+`deltaListsReturned`
+
+| Assertion Name | Definition |
+|---------------------------------|--------------------------------------------|
+| <code>deltaListsReturned</code> | The required file information is returned. |
+
+#### 6.5.1.6 Exceptions
+
+| Name | Properties |
+|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <code>operation_failed</code> | <b>Condition:</b> the pre-condition is false or the post-condition is false.<br><b>Returned Information:</b> The output parameter status.<br><b>Exit state:</b> Entry state. |
+
+# 7 Operation Modes
+
+Several modes of operation for delta Synchronization are possible. An implementation supporting at least one of them can claim compliance to this specification.
+
+For each mode of operation, the `DeltaSynchronizationIRP` needs to support `CMData` delta Synchronization or `AlarmData` delta Synchronization or both.
+
+Further details to the operation modes and examples how to use them are supplied in Annex A.
+
+## 7.1 Delta Synchronization Mode DSM1
+
+In this operation mode DSM1 the `DeltaSynchronizationIRP` only needs to support the following operations and notifications:
+
+- `triggerDeltaSynchOfCMData`
+- `triggerDeltaSyncOfAlarmData`
+- optionally `notifyNewDeltaSynchPoint`
+
+In this mode of operation, the `DeltaSynchronizationIRP` may ignore the use of `managerReference` input parameter.
+
+## 7.2 Delta Synchronization Mode DSM2
+
+In this operation mode DSM2, the use of `managerReference` is mandatory.
+
+Otherwise, in this mode of operation the `DeltaSynchronizationIRP` supports all operations and notifications and their parameters which are qualified as `M(andatory)` in this specification.
+
+## 7.3 Delta Synchronization Mode DSM3
+
+In this mode of operation DSM3, the `DeltaSynchronizationIRP` supports all operations and notifications and their parameters as defined in this specification.
+
+# --- Annex A (informative): Modes of operation for delta synchronization
+
+The following two modes of operations are possible. IRP Agent can claim compliance if only one is supported.
+
+## --- A.1 Operation Mode DSM1
+
+Example for this mode of operation:
+
+Suppose $t_0, t_1, t_2, t_3, t_4$ and so on are the synchPoints.
+
+Suppose an IRPManager invokes a trigger with $\text{synchPoint} == 0$ (requesting full sync data) at $t_x$ where $t_2 < t_x < t_3$ , the `DeltaSynchronizationIRP` will return all data up to $t_2$ and return the $t_2$ as the newSynchPoint.
+
+This IRPManager should use $t_2$ as the synchPoint for future trigger.
+
+Suppose this IRPManager invokes a trigger with $\text{synchPoint} == t_2$ at $t_y$ where $t_4 < t_y < t_5$ , the `DeltaSynchronizationIRP` will return delta data between $t_2$ and $t_4$ .
+
+This mode of operation is suitable for IRPManagers that do not require synchronization of data at all time.
+
+In this mode of operation, the `DeltaSynchronizationIRP` may pre-assign the synch points based on a fixed frequency. In the example above, the durations between sync points $t_0, t_1, t_2$ and so on would be identical. This frequency can be a system configuration time parameter and made known to IRPManager via non-standard means.
+
+## --- A.2 Operation Mode DSM2
+
+This mode of operation supports to handle requests of individual IRPManagers individually.
+
+This mode of operation is suitable for an IRPManager that require synchronization of data at any time, i.e. not requiring synchronization of data at some predefined fixed intervals.
+
+## --- A.3 Operation Mode DSM3
+
+This mode of operation provides all options of delta Synchronization.
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|-------|-----------|------|----|-----------------------------------------------------------------------------|-----|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | R | Subject/Comment | Cat | Old | New |
+| Dec 2006 | SA_34 | SP-060735 | -- | -- | Submitted to SA#34 for Information | -- | 1.0.0 | |
+| Mar 2007 | SA_35 | SP-070053 | -- | -- | Submitted to SA#35 for Approval | -- | 2.0.0 | 7.0.0 |
+| Jun 2007 | SA_36 | SP-070276 | 0001 | -- | Correct the information type of the input parameter | F | 7.0.0 | 7.1.0 |
+| Jun 2007 | SA_36 | SP-070276 | 0002 | -- | Add missing mode of operations | F | 7.0.0 | 7.1.0 |
+| Sep 2007 | SA_37 | SP-070612 | 0003 | -- | Add missing type definition | F | 7.1.0 | 7.2.0 |
+| Sep 2007 | SA_37 | SP-070675 | 0004 | 1 | Correct the parameter definitions of operation getAvailableDeltaSynchPoints | F | 7.1.0 | 7.2.0 |
+| Dec 2008 | SA_42 | -- | -- | -- | Upgrade to Release 8 | -- | 7.0.0 | 8.0.0 |
+| Dec 2009 | - | - | - | - | Update to Rel-9 version | -- | 8.0.0 | 9.0.0 |
+| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | | 9.0.0 | 10.0.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | | 10.0.0 | <b>11.0.0</b> |
+| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) | | 11.0.0 | <b>12.0.0</b> |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | <b>13.0.0</b> |
+| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | | 13.0.0 | <b>14.0.0</b> |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-06 | | | | | | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
+| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32501/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/32_series/32501/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f96dff4129d9a0dcd130ebae9690419b915c1f0f
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:259b6e9bea33893a3d1d14a0cfbe1f0be461f76b1ec314f0812108ae6f5139b2
+size 110441
diff --git a/marked/Rel-18/32_series/32501/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-18/32_series/32501/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..31090795ce29edafefac709f29ba83d7740540da
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ef2eb567c01713995c1c601fe6a27f3ed9377c271d749b66c663a32ba31f179
+size 102735
diff --git a/marked/Rel-18/32_series/32501/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/32_series/32501/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4615ceeb6b1d73c105e37e4a475ced606f1b1a83
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63db3eab707fbf1cc6ad6d98e4a8604bf1f465530bd7256cb9c5a4ac2b033e2a
+size 48410
diff --git a/marked/Rel-18/32_series/32501/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32501/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4de7dd97b9337b3aaf072e746405ad520d5d45de
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
+size 9370
diff --git a/marked/Rel-18/32_series/32501/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32501/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..befa7d0aab7a27d907df9a48accf6d9115609306
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9faff289c269ff2b0f41d2267933e4cc43c36969d345e79d9a3b32ee4d7b5dbd
+size 5420
diff --git a/marked/Rel-18/32_series/32501/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-18/32_series/32501/90ddf538ef276510e2b631f7b96654e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..159caa0a0b82df073c05df2a5910c408c0d1e7af
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/90ddf538ef276510e2b631f7b96654e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d274eeeaed56a69c801fb187090160dd8a36ce6e227e68b05f4c0155195839e
+size 51504
diff --git a/marked/Rel-18/32_series/32501/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-18/32_series/32501/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e4ddbbf8a23b953a7f023a643fe70082de35b9a3
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88f55402d5f1952a2a047f6353f63cbc06742ad1b989a10c7c5440ec1f2c1097
+size 62042
diff --git a/marked/Rel-18/32_series/32501/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-18/32_series/32501/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f294b5ee253ab0b50a2905f18fb8ee53d3a82230
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06b83a89b161504bb6da1c7b6f619bda643d896b528f4c7215d449873d5f4dec
+size 44927
diff --git a/marked/Rel-18/32_series/32501/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/32_series/32501/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..260875a476ad9dddf916e45570ccd4ff28211616
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1aff7c48b64d073ccc64be16d81250364d79af2bab99ddab67033053cd8fca2
+size 53871
diff --git a/marked/Rel-18/32_series/32501/raw.md b/marked/Rel-18/32_series/32501/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee34ff7f5b102b51b485e82db246d415092eae43
--- /dev/null
+++ b/marked/Rel-18/32_series/32501/raw.md
@@ -0,0 +1,740 @@
+
+
+# 3GPP TS 32.501 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Self-configuration of network elements; Concepts and requirements (Release 18)** ---
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+Management, 3GPP
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|---------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 Concepts and background..... | 7 |
+| 4.1 Self-Configuration Concept ..... | 7 |
+| 4.1.1 Logical Function Blocs..... | 7 |
+| 4.1.1.1 Address Allocation Function (AAF): ..... | 7 |
+| 4.1.1.2 OAM Connectivity Establishment Function (OAM_CO_EF): ..... | 7 |
+| 4.1.1.3 Software Management Function (SW_MF): ..... | 7 |
+| 4.1.1.4 Inventory Update Function (Inv_UF): ..... | 7 |
+| 4.1.1.5 Self-Test Function (ST_F): ..... | 8 |
+| 4.1.1.6 Self-Configuration Monitoring and Management Function (SC_MM_F): ..... | 8 |
+| 4.1.1.6.1 Self-Configuration Monitoring and Management Function (SC_MM_F_NM): ..... | 8 |
+| 4.1.1.6.2 Self-Configuration Monitoring and Management Function (SC_MM_F_EM): ..... | 8 |
+| 4.1.1.7 Call Processing Link (CPL) Set Up Function (CPL_SUF): ..... | 8 |
+| 4.1.1.8 Radio Network Configuration Data Function (R_CD_F): ..... | 8 |
+| 4.1.1.9 Transport Network Configuration Data Function (T_CD_F): ..... | 8 |
+| 4.1.1.10 NRM IRP Update Function (NRM_UF): ..... | 8 |
+| 4.1.1.11 Radio Network and Transport Network Configuration Data Preparation Function ..... | 8 |
+| 4.2 Automatic Radio Configuration Data handling Function (ARCF) Concept..... | 8 |
+| 4.2.1 Definitions ..... | 8 |
+| 4.3 Multi-Vendor Plug and Play eNB connection to network Concept..... | 9 |
+| 4.3.1 General description..... | 9 |
+| 4.3.2 Network Scenarios..... | 9 |
+| 4.3.2.1 eNB connected via a Non-Secure, Operator Controlled Network..... | 9 |
+| 4.3.2.2 eNB connected via an External Network..... | 10 |
+| 4.3.2.3 eNB connection to the OAM Network and multiple CNs via separate SeGWs..... | 10 |
+| 4.3.3 Security Aspects ..... | 11 |
+| 4.3.3.1 Root Certificate Acquisition: ..... | 11 |
+| 4.3.3.2 Number of CA servers ..... | 12 |
+| 4.3.3.3 Number of OAM SeGWs ..... | 12 |
+| 5 Business Level Requirements ..... | 13 |
+| 5.1 Self- Configuration of eNodeB's ..... | 13 |
+| 5.1.1 Actor roles ..... | 13 |
+| 5.1.2 Telecommunications resources..... | 13 |
+| 5.1.3 High-level use cases ..... | 13 |
+| 5.2 Business Requirements for Multi Vendor Plug and Play eNB connection to network..... | 13 |
+| 6 Specification level requirements..... | 15 |
+| 6.1 General ..... | 15 |
+| 6.2 Actor roles ..... | 15 |
+| 6.3 Telecommunications resources ..... | 15 |
+| 6.4 Use cases ..... | 15 |
+| 6.4.1 Use case for Automatic Radio Network Configuration Data Handling ..... | 15 |
+| 6.4.1.1 Use case radio network configuration data request, transfer and validity check..... | 15 |
+| 6.4.2 Use case Self-configuration of a new eNodeB..... | 15 |
+| 6.4.3 Use case Multi Vendor Plug and Connect eNB to network ..... | 18 |
+| 6.5 Requirements..... | 19 |
+| 6.5.1 Automatic Radio Network Configuration Data Handling..... | 19 |
+| 6.5.2 Self-configuration of a new eNodeB..... | 19 |
+
+| | | |
+|-------------------------------|------------------------------------------------------------------------------------------|-----------|
+| 6.5.2.1 | Self-Configuration Management and Monitoring ..... | 20 |
+| 6.5.2.1.1 | Management Part..... | 20 |
+| 6.5.2.1.2 | Monitoring Part ..... | 20 |
+| 6.5.2.2 | Software Management..... | 20 |
+| 6.5.2.3 | Address Allocation and OAM Connectivity Establishment ..... | 21 |
+| 6.5.2.4 | Inventory Update ..... | 21 |
+| 6.5.2.5 | Self-Test..... | 21 |
+| 6.5.2.6 | Radio Configuration Data..... | 21 |
+| 6.5.2.7 | Transport Configuration Data..... | 21 |
+| 6.5.2.8 | Call Processing Link Set-Up..... | 21 |
+| 6.5.2.9 | NRM IRP Update..... | 21 |
+| 6.5.3 | Specification Requirements for Multi-Vendor Plug and Play eNB connection to network..... | 21 |
+| 7. | Functions and Architecture ..... | 22 |
+| 7.1 | Self-Configuration Logical Architecture ..... | 22 |
+| 7.2 | Self-Configuration Reference Model..... | 23 |
+| <b>Annex A (informative):</b> | <b>Graphical representation of the PnC Use Case .....</b> | <b>24</b> |
+| <b>Annex B (informative):</b> | <b>Change history .....</b> | <b>29</b> |
+
+# --- 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below:
+
+- 32.501: Self-Configuration of Network Elements; Concepts and Integration Reference Point (IRP) Requirements;**
+- 32.502: Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS);
+- 32.506: Self-Configuration of Network Elements Integration Reference Point (IRP); Solution Set (SS) definitions.
+
+# --- 1 Scope
+
+The present document describes the concepts how self-configuration works and what IRP requirements need to be met to support this functionality. The document also captures if a requirement shall be met via the Itf-N interface or via other protocols. This version of the TS is restricted to self-configuration of eNBs. The requirements in this document are not imposed on HNBs.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [3] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [4] 3GPP TR 32.816: "Telecommunication management; Study on Management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC)".
+- [5] 3GPP TS 32.531: "Telecommunication management; Architecture; Software Management Concepts and IRP Requirements ".
+- [6] ITU-T Recommendation X.800: "Security architecture for Open Systems Interconnection for CCITT applications".
+- [7] 3GPP TS 33.310: " Network Domain Security (NDS); Authentication Framework (AF)".
+
+# --- 3 Definitions and abbreviations
+
+For the purposes of the present document, the terms and definitions given in TS 32.101 [2], TS 32.102 [3] and TS 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 TS 32.101 [1], TS 32.102 [2] and TS 21.905 [5], in that order.
+
+## 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].
+
+**Credentials:** Data that is transferred to establish the claimed identity of an entity, see ITU-T Recommendation X.800 [6].
+
+**Plug and Play:** The process of connecting a minimally preconfigured node to the transport network, whereby the node, with minimum operator attention, can exchange information with the OAM system and other relevant nodes to an extent that the node is configured and ready to handle traffic.
+
+**Plug and Connect:** The procedure by which an eNodeB gets basic connectivity information after it is powered up and gets connected to its EM system in a multi-vendor environment. Multi-vendor Plug and Connect is part of the Multi-Vendor Plug and Play.
+
+**Self Configuration:** The process which brings a network element into service requiring minimal human operator intervention or none at all.
+
+## 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].
+
+| | |
+|-------|-------------------------------------|
+| CA | Certification Authority |
+| CMP | Certificate Management Protocol |
+| DHCP | Dynamic Host Configuration Protocol |
+| DNS | Domain Name System |
+| EM | Element Manager |
+| FQDN | Fully Qualified Domain Name |
+| IP@ | IP address |
+| MvPnC | Multi-vendor Plug and Connect |
+| MvPnP | Multi-vendor Plug and Play |
+| NAT | Network Address Translation |
+| PnC | Plug and Connect |
+| PnP | Plug and Play |
+| RA | Registration Authority |
+| SC | Self Configuration |
+| SeGW | Security Gateway |
+| TLS | Transport Layer Security |
+| VLAN | Virtual LAN |
+| VM | Vendor Mediator |
+
+# --- 4 Concepts and background
+
+Provide here an update of See TS 32.816 [4] §5.1.3.1.1 “Establishment of new eNodeB in network”
+
+## 4.1 Self-Configuration Concept
+
+### 4.1.1 Logical Function Blocs
+
+#### 4.1.1.1 Address Allocation Function (AAF):
+
+This functional bloc supports the following functions: [SC1], [SC3].
+
+#### 4.1.1.2 OAM Connectivity Establishment Function (OAM CO\_EF):
+
+This functional bloc supports the following functions: [SC2], [SC3], [SC4], [SC5], [SC13].
+
+#### 4.1.1.3 Software Management Function (SW\_MF):
+
+This functional bloc supports the following functions: [SC3], [SC6], [SC7], [SC8], [SC20], [SC21].
+
+#### 4.1.1.4 Inventory Update Function (Inv\_UF):
+
+This functional bloc supports the following functions: [SC16].
+
+#### 4.1.1.5 Self-Test Function (ST\_F):
+
+This functional bloc supports the following functions: [SC17].
+
+This function performs eNodeB self-tests.
+
+#### 4.1.1.6 Self-Configuration Monitoring and Management Function (SC\_MMF):
+
+This functional bloc supports the following functions: [SC18].
+
+This function monitors the self-configuration process and provides the operator with this information. This function must be able to get information about all other functional blocs. In addition to this it allows the operator to control the execution of the self-configuration process.
+
+##### 4.1.1.6.1 Self-Configuration Monitoring and Management Function (SC\_MMF\_NM):
+
+SC\_MMF\_NM (IRP Manager): representing the NM portion of SC\_MMF (necessary monitoring and limited interaction capabilities to support an automated optimization), as well as related IRPManager functionality
+
+##### 4.1.1.6.2 Self-Configuration Monitoring and Management Function (SC\_MMF\_EM):
+
+SC\_MMF\_EM (IRP Agent): representing the portion of SC\_MMF operating below Itf-N, as well as related IRPAgent functionality
+
+#### 4.1.1.7 Call Processing Link (CPL) Set Up Function (CPL\_SUF):
+
+This functional bloc supports the following functions: [SC14], [SC15].
+
+#### 4.1.1.8 Radio Network Configuration Data Function (R\_CD\_F):
+
+This functional bloc supports the following functions: [SC9], [SC11], [SC12].
+
+#### 4.1.1.9 Transport Network Configuration Data Function (T\_CD\_F):
+
+This functional bloc supports the following functions: [SC9], [SC11], [SC12].
+
+#### 4.1.1.10 NRM IRP Update Function (NRM\_UF):
+
+This functional bloc supports the following functions: [SC19].
+
+This function updates the E-UTRAN and EPC NRM IRP with information about the new eNodeB.
+
+#### 4.1.1.11 Radio Network and Transport Network Configuration Data Preparation Function
+
+This functional bloc supports the following functions: [SC10].
+
+## 4.2 Automatic Radio Configuration Data handling Function (ARCF) Concept
+
+### 4.2.1 Definitions
+
+**ARCF Data:** ARCF data are the data which are required for successful activation (of e.g. cell, eNB) that require coordination between several cells and cannot be generated below Itf-N. Some of the ARCF data may be used directly as eNodeB configuration data and some of the ARCF data may be used to generate more other eNodeB configuration
+
+data. eNodeB will use the ARCF data together with other configuration data as initial eNodeB radio configuration data. The eNodeB initial radio configuration data will be used for self-configuration.
+
+**ARCF Handling:** This includes ARCF data preparation, ARCF Data Transfer and ARCF Data Validation.
+
+**ARCF Data Preparation:** This makes the ARCF data ready in operator's network management system. How to prepare the ARCF data in operator's network management system is out of scope of this specification.
+
+**ARCF Data Transfer:** This transfers the ARCF data from IRPManager to the IRPAgent,
+
+**ARCF Data Validation:** This validates the syntax and semantics of ARCF data. It takes place in the IRPAgent.
+
+## 4.3 Multi-Vendor Plug and Play eNB connection to network Concept
+
+### 4.3.1 General description
+
+The basic idea of Plug and Play is to avoid pre-configuration of an eNB as far as possible. In an ideal PnP world an eNB equipment is totally agnostic of its future purpose, its location in the network, its addresses, its basic configuration parameters etc... All this information is only supplied step by step during the PnP process.
+
+The required information for the new eNB is stored at specific places. The eNB needs to know how to access these places. The PnP process provides this information to the eNB.
+
+The entities involved in the PnP concept are eNB, DHCP server, DNS Server, Certification Authority server, Element Manager (including the Initial and Serving Element Managers that could be the same in certain deployment scenarios), Security Gateway.
+
+The Plug and Play includes "Plug and Connect" and Self-Configuration. The basic steps of Plug and Connect are described in clause 6.4.3.
+
+After Plug and Connect Self-Configuration procedures are used to complete Plug and Play.
+
+### 4.3.2 Network Scenarios
+
+#### 4.3.2.1 eNB connected via a Non-Secure, Operator Controlled Network
+
+An eNB is typically connected to the operator's network according to one of the following scenarios:
+
+In Figure 4.3.2-1, the eNB is connected directly to a network controlled by the operator. The eNB can use IP Infrastructure services (DHCP Server, DNS Server, etc.) in the Non-secure Operator Network. The Operator has full control of these nodes. One or more Security Gateways protect the Secure Operator Network from malicious eNBs. Within the Secure Operator Network, there are also IP Infrastructure nodes.
+
+
+
+This diagram illustrates an eNB connected to a Non-Secure Operator Network. On the left, an 'eNB' box is connected by a line to a 'Security Gateway(s)' box. The 'Security Gateway(s)' box is situated within a large oval representing the 'Non-Secure Operator Network'. Inside this oval, there are two stacks of boxes labeled 'IP Infrastructure'. Below the oval, a callout box labeled 'Non-Secure Operator Network' points to the oval. To the right, another oval represents the 'Secure Operator Network', which also contains a stack of 'IP Infrastructure' boxes. A callout box labeled 'Secure Operator Network' points to this oval. The 'Security Gateway(s)' box is positioned at the boundary between the two ovals.
+
+Diagram of eNB connected to a Non-Secure Operator Network
+
+**Figure 4.3.2-1 eNB connected to an Non-Secure Operator Network**
+
+#### 4.3.2.2 eNB connected via an External Network
+
+In Figure 4.3.2-2, the eNB is connected to a network controlled by an entity external to the Operator. In contrast to the first scenario, the IP Infrastructure nodes in the External Network are not fully controlled by the operator. In both cases, the eNB needs to traverse the Security Gateway(s) to access the nodes in the Secure Operator Network.
+
+
+
+This diagram illustrates an eNB connected to an External Network. On the left, an 'eNB' box is connected by a line to a 'Security Gateway(s)' box. The 'Security Gateway(s)' box is situated within a circle representing the 'External Network'. Inside this circle, there is a stack of boxes labeled 'IP Infrastructure'. Below the circle, a callout box labeled 'External Network' points to it. To the right, a large oval represents the 'Secure Operator Network', which contains a stack of 'IP Infrastructure' boxes. A callout box labeled 'Secure Operator Network' points to this oval. The 'Security Gateway(s)' box is positioned at the boundary between the External Network circle and the Secure Operator Network oval.
+
+Diagram of eNB connected to an External Network
+
+**Figure 4.3.2-2 eNB connected to an External Network**
+
+#### 4.3.2.3 eNB connection to the OAM Network and multiple CNs via separate SeGWs
+
+Following certificate enrolment with the operator's CA, an eNB establishes a secure tunnel to the SeGW of the OAM network. Through this tunnel it then connects to its DM from which it receives software updates and configuration information, including its transport configuration to the core network(s) it is supposed to connect to. It then typically establishes a separate secure tunnel to the SeGW of the operator's core network. In the case of RAN Sharing, the eNB may establish further tunnels to other Participating Operators' core networks. The OAM and CN SeGWs may or may not be separate physical entities in practice.
+
+Figure 4.3.2-3 shows an example of an eNB connected to the OAM Network and multiple CNs via separate SeGWs.
+
+
+
+Diagram showing an eNB connected to an OAM SeGW and multiple CN SeGWs (1 to n). Each SeGW is connected to a corresponding network element (DM, CN 1, CN m) within a shaded oval representing a network domain. The eNB is on the left, and the connections fan out to the right. The OAM SeGW is at the top, followed by CN SeGW 1, then a vertical ellipsis, and finally CN SeGW n (n <= 6) at the bottom. The corresponding network elements are DM, CN 1, and CN m.
+
+Figure 4.3.2-3 Example of eNB connected to OAM Network and multiple CNs via separate SeGWs
+
+### 4.3.3 Security Aspects
+
+#### 4.3.3.1 Root Certificate Acquisition:
+
+In accordance to TS 33.310 [yy] §9.2 there are two options how to obtain the operator root certificate:
+
+Option 1: The operator root certificate is provisioned in the base station prior to the CMPv2 protocol run
+
+Option 2: The operator root certificate is provisioned in the base station during the CMPv2 protocol run (as part of the Initialisation Response)
+
+The required pre-provisioning in option 1 is against the basic idea of PnP to minimize pre-provisioning. Therefore from the PnP perspective Option 2 is more interesting. From a security point of view the following considerations are relevant:
+
+Option 2 has the risk that during the CMP initialisation a man-in the middle attack could take place. In order to be successful, such an attack must happen timely during the actual CMP initialization run and the attacker must have access to the access network between base station and RA/CA.
+
+This risk can be assessed as acceptable, given (a) the risks which are present at Options 1's prior provisioning – see below, (b) the short time window of vulnerability, (c) the closed access networks of many operators. In addition, most attacks will only lead to inability of the base station to connect to the network, or to misuse of the new base station by the attacker. The operator should notice it soon if the base station does not connect, and will investigate the issue.
+
+Option 1 avoids the above “time window of vulnerability”. On the other hand it requires pre-provisioning of the operator root certificate, either in factory or on-site by service personnel. There is the risk of a security leak during the provisioning of the root certificate within the vendor / commissioning environment.
+
+It seems questionable from a security point of view to allow option 2 also in public Internet (without operator-trusted access network). There the attacks stated above are more probable, and an attacker may even install some (static) catching or spoofing equipment in the public Internet to always capture such “initialization requests”.
+
+It is up to the network operator to choose the option which is preferable from his point of view (risk assessment, Plug and Play importance).
+
+#### 4.3.3.2 Number of CA servers
+
+There could be one or more RA/CA server, e. g. one per vendor. If more than one RA/CA server is deployed with one RA/CA server per vendor then the vendor identification would be needed either in the FQDN of the RA server or in the information from the IP AutoConfiguration Service carrying the information about RA/CA server.
+
+#### 4.3.3.3 Number of OAM SeGWs
+
+There could be one or more OAM SeGW, e. g. one per vendor. If more than one OAM SeGW is deployed with one OAM SeGW per vendor then the vendor identification would be needed either in the FQDN of the OAM SeGW or in the information from the IP AutoConfiguration Service carrying the information about OAM SeGW.
+
+# 5 Business Level Requirements
+
+## 5.1 Self- Configuration of eNodeB's
+
+**REQ\_SCMAN\_CON\_1** The actor on NM level shall be able to manage the self-configuration process.
+
+**REQ\_SCMON\_CON\_1** The actor on NM level shall be able to monitor the execution of the self-configuration process.
+
+**REQ\_SCMON\_CON\_2** To support the monitoring of the execution of the self-configuration process, existing capabilities shall be reused as much as possible.
+
+**REQ\_SCSW\_CON\_1** The software download, installation, activation and fallback should be automated as much as possible so that no or only minimal manual intervention is required.
+
+**REQ\_SCSW\_CON\_1** see **REQ\_SW\_CON\_4**
+
+**REQ\_SCSW\_CON\_2** see **REQ\_SW\_CON\_2**
+
+**REQ\_SCOCE\_CON\_1** The OAM connectivity (incl. the IP address allocation) should be established in a fully automated manner.
+
+**REQ\_SCOCE\_CON\_2** The amount of parameters that needs to be preconfigured should be minimized.
+
+**REQ\_SCIU\_CON\_1** Inventory information about the new equipment shall be reported to the actor at NM level as part of the self-configuration process.
+
+**REQ\_SCIU\_CON\_2** Inventory information shall be made available to the IRPManager reusing existing capabilities as much as possible.
+
+**REQ\_SCRCD\_CON\_1** The radio configuration data shall be made available to the eNodeB as part of the self-configuration process.
+
+**REQ\_SCTCD\_CON\_1** The transport configuration data shall be made available to the eNodeB as part of the self-configuration process.
+
+**REQ\_SCCPLSU\_CON\_1** X2- and S1-interfaces shall be set up as part of the self-configuration process, based on the radio configuration, the transport configuration and Neighbour cell Relation information made available to the eNodeB.
+
+Note: If there is no Neighbour cell Relation information provided, then no X2 interface is set up as part of the self-configuration process.
+
+### 5.1.1 Actor roles
+
+### 5.1.2 Telecommunications resources
+
+### 5.1.3 High-level use cases
+
+## 5.2 Business Requirements for Multi Vendor Plug and Play eNB connection to network
+
+**REQ\_PnP\_CON\_1** Plug and Play for an eNB's connection to the network shall use standard protocols.
+
+**REQ\_PnP\_CON\_2** VPN tunnels needed for Plug and Play for an eNB's connection to the network shall be set-up automatically.
+
+- REQ\_PnP\_CON\_3** The complete key management during Plug and Play for an eNB's connection to the network shall be a full automatic secure procedure, based on procedures defined by 3GPP SA3.
+- REQ\_PnP\_CON\_4** After Plug and connect an eNB and potentially additional self-configuration of the eNB it shall be possible to bring an eNB into service
+- REQ\_PnP\_CON\_5** As a result of Plug and Play for an eNB's connection to the network and potentially additional self-configuration of the eNB, the newest software and parameter settings as defined by the network operator shall be used in the eNB.
+- REQ\_PnP\_CON\_6:** It shall be possible to perform the MvPnP procedures using secure protocols and procedures between the eNB and OAM.
+- REQ\_PnP\_CON\_7** eNB shall be able to get its own IP addresses and EM IP address without manual configuration.
+- REQ\_PnP\_CON\_8** For Plug and Connect the Element Manager shall only be accessible by authenticated and authorized eNBs.
+- REQ\_PnP\_CON\_9** For Plug and Connect the initial and final configuration of the eNB (or the information how to retrieve them) shall only be accessible by authenticated and authorized eNBs.
+- REQ\_PnP\_CON\_10** The MvPnP solution shall be usable for IPv4-only networks, for IPv6-only networks and for dual stack IP networks.
+- REQ\_PnP\_CON\_11** MvPnP procedures shall support Network Sharing including the connection of an eNB to multiple core networks and PLMNs.
+- REQ\_PnP\_CON\_12** MvPnP procedures shall support connection of eNBs with and without NAT and via External Networks or Non-Secure Operator Networks.
+
+# 6 Specification level requirements
+
+## 6.1 General
+
+## 6.2 Actor roles
+
+## 6.3 Telecommunications resources
+
+## 6.4 Use cases
+
+### 6.4.1 Use case for Automatic Radio Network Configuration Data Handling
+
+#### 6.4.1.1 Use case radio network configuration data request, transfer and validity check
+
+| Use Case Stage | Evolution / Specification | <<Uses>><br>Related use |
+|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| Goal (*) | Transfer the radio network configuration data to the IRP Agent and ensure that it is valid when it is used during self-configuration. | |
+| Actors and Roles (*) | IRP Manager as user | |
+| Telecom resources | The E-UTRAN network including its OSS. | |
+| Assumptions | OAM connection is working.<br>IRP Agent cannot determine all radio configuration data on its own. | |
+| Pre conditions | NA | |
+| Begins when | Radio network configuration data is to be made known to the IRP Agent. | |
+| Step 1 (O) | [ARCF-1-1] IRP Agent indicates need for radio configuration data to the IRP Manager | |
+| Step 2 (M) | [ARCF-1-2] IRP Manager transfers the radio configuration data to IRP Agent or indicates to IRP Agent where the radio configuration data is available and IRP Agent retrieves the data from there | |
+| Step 3 (O) | [ARCF-1-3] IRP Manager requests IRP Agent to validate the received radio configuration data | |
+| Step 4 (M) | [ARCF-1-4] IRP Agent validates the received radio configuration data | |
+| Ends when | Ends when all steps identified above are completed or when an exception occurs | |
+| Exceptions | One of the steps identified above fails. | |
+| Post Conditions | The self-configuration process can use the radio configuration data. | |
+| Traceability | FFS | |
+
+### 6.4.2 Use case Self-configuration of a new eNodeB
+
+This use case starts with the first initial self test and ends when the eNodeB is taken into operation.
+
+| Use Case Stage | Evolution / Specification | <<Uses>><br>Related use |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| Goal (*) | After physical installation, put in an automated manner the eNodeB into a state to be ready to carry traffic. | |
+| Actors and Roles (*) | FFS | |
+| Telecom resources | The E-UTRAN/EPC network including its OSS. | |
+| Assumptions | IP network connectivity exists between the eNodeB and the OAM (sub) systems providing support for the self-configuration process. | |
+| Pre conditions | The eNodeB is physically installed and physically connected to an IP network. | |
+| Begins when | The field personnel start the self-configuration process. It is also possible that the process is triggered automatically after the completion of an eNodeB self-test. | |
+| Step 1 (*)<br>(M/O) | <p>The order of the bullet points in the list below does not imply any statements on the order of execution.</p> <ul style="list-style-type: none"> <li>[SC1] An eNodeB IP address is allocated to the new eNodeB.</li> <li>[SC2] Basic information about the transport network (e. g. gateways) environment is provided to the eNodeB. With this information the eNodeB is able to exchange IP packets with other internet hosts.</li> <li>[SC3] The eNodeB provides information about its type, hardware and other relevant data about itself to the OAM (sub) systems providing support for the self-configuration process.</li> <li>[SC4] The address(es) of the OAM (sub) system(s) providing support for the self-configuration process (e.g. subsystem for software download, subsystem for configuration data download) is provided to the eNodeB. The address is equal to an IP address and a port number, or a DNS name and port number, or an URI.</li> <li>[SC5] The address(es) of the OAM (sub)system(s) providing support for normal OAM functions after completion of the self-configuration process are provided to the eNodeB. The address is equal to an IP address and a port number, or a DNS name and port number, or an URI.</li> <li>[SC6] The eNodeB connects to the OAM system providing support for the software download.</li> <li>[SC7] The decision which software or software packages have to be downloaded to the eNodeB is taken.</li> <li>[SC8] The software is downloaded into the eNodeB.</li> <li>[SC9] The eNodeB connects to the OAM system providing support for the configuration data download.</li> <li>[SC10] The (transport and radio) configuration data for the eNodeB is made available by either preparing it or making prepared configuration data available.</li> <li>[SC11] The (transport and radio) configuration data is downloaded into the eNodeB.</li> <li>[SC12] Dependent nodes (MMEs, eNodeBs) are updated with new configuration data as well (if required).</li> <li>[SC13] The eNodeB connects to the OAM (sub) system(s) providing support for normal OAM functions after completion of the self-configuration process.</li> <li>[SC14] The S1-links are be set up.</li> <li>[SC15] The (planned) X2-links are be set up.</li> <li>[SC16] The inventory system in the OAM is informed that a new eNodeB is in the field.</li> <li>[SC17] The eNodeB performs a self-test. Self-tests of different types can run at different places within the self-configuration procedure.</li> <li>[SC18] The operator is informed about the progress of the self-configuration process and important events occurring during the self-configuration process.</li> <li>[SC19] The network resource models visible over Itf-N are updated during and after the self-configuration process.</li> <li>[SC20] SW is installed, i.e. prepared in such a way, that the NE is ready to use it. For some implementations this step is done not at all or considered part of [SC21] or of [SC8].</li> <li>[SC21] SW is activated, i.e. final provisions are done such that the NE is allowed to use the SW. For some implementations this step is considered part of [SC20] or of [SC8].</li> </ul> | |
+| Ends when (*) | Ends when all steps identified above are successfully completed or when an exception occurs. | |
+| Exceptions | FFS. | |
+| Post Conditions | The eNodeB is ready to carry traffic. | |
+| Traceability (*) | | |
+
+Security aspects are FFS.
+
+### 6.4.3 Use case Multi Vendor Plug and Connect eNB to network
+
+Table 6.4.3-1
+
+| Use Case Stage | Evolution / Specification | <<Uses>><br>Related use |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| Goal | After physical installation, connect the eNB to its initial Element Manager and to the Core Network(s) as automatically as possible. | |
+| Actors and Roles | eNB as user | |
+| Telecom resources | eNB; IP networks: Non-Secure Operator Network, External Network, and its elements like DHCP server optionally DNS, CA/RA servers, Security Gateway(s) (each protecting one or more Secure Operator Networks), Secure Operator Network(s) including Element Manager(s), Core Network(s) | |
+| Assumptions | There is a functional power supply for the eNB.<br>There may be one or more IP Autoconfiguration Services like DHCP and Router Advertisements and zero or more DNS servers. | |
+| Pre conditions | The eNB is physically installed.<br>IP connectivity exists between the involved telecom resources.<br>The involved telecom resources are functional.<br>The relevant information is stored and available: <ul style="list-style-type: none"> <li>- Vendor Certificate at the eNB</li> <li>- Operator Certificate at the CA/RA</li> <li>- For the External Network or Non-Secure Operator Network: <ul style="list-style-type: none"> <li>- (Outer) IP autoconfiguration information at the IP Autoconfiguration Service</li> <li>- FQDN of the initial OAM SeGW at the eNB and/or FQDN or IP address of the initial OAM SeGW at the IP Autoconfiguration Service</li> <li>- FQDN of the CA/RA servers at the eNB and/or FQDN or IP address of the CA/RA servers at the IP Autoconfiguration Service</li> <li>- If FQDNs need to be resolved, corresponding IP address(es) at the DNS server(s)</li> </ul> </li> <li>- For the Secure Operator Network: <ul style="list-style-type: none"> <li>- (Inner) IP autoconfiguration information at the IP Autoconfiguration Service or at the initial OAM SeGW</li> <li>- FQDN or IP address of the initial EMS at the eNB and/or DHCP Server of the Secure Operator Network.</li> <li>- If FQDNs need to be resolved, corresponding IP address(es) at the DNS server(s)</li> <li>- Configuration and software for the eNB at the EM(s)</li> </ul> </li> </ul> | |
+| Begins when | The eNB is powered up. | |
+| Step 1 (M) | If a VLAN ID is available the eNB uses it. Otherwise the eNB uses the native VLAN where PnP traffic is sent and received untagged | |
+| Step 2 (M) | The eNB acquires its IP address through stateful or stateless IP autoconfiguration. This may provide 0 or more DNS server addresses. | |
+| Step 3 (M) | The eNB acquires the IP address of the CA/RA server. The FQDN of the CA/RA server may be pre-configured in the eNB or the FQDN or IP address of the CA/RA server may be provided by the IP Autoconfiguration Service. FQDNs are resolved through the DNS if necessary. Information provided by the IP Autoconfiguration Services shall supersede those pre-configured at the eNB. | |
+| Step 4 (M) | The eNB performs Certificate Enrolment. | |
+| Step 5 (M) | The eNB acquires the IP address of the OAM SeGW. The FQDN of the OAM SeGW may be pre-configured in the eNB or the FQDN or the IP address of the OAM SeGW may be provided by the IP Autoconfiguration Service. FQDNs are resolved through the DNS if necessary. | |
+| Step 6 (M) | The eNB establishes a secure connection (tunnel) to the Security Gateway given by Step 5.<br>The eNB receives its (inner) IP autoconfiguration information (which may be the same as the outer IP address obtained in step2) and optionally the address of one or more DNS servers within the Secure Operator Network from the Configuration Parameters of IKEv2 during tunnel establishment. | |
+
+| Use Case Stage | Evolution / Specification | <<Uses>> Related use |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| Step 7 (M) | The eNB acquires the IP address of the correct Element Manager by either, issuing a DHCP request including the eNB's vendor information, resolving FQDNs via DNS if necessary, or by having a pre-configured FQDN (including the eNB's vendor information) resolved via DNS. | Secure connection |
+| Step 8 (M) | The eNB establishes a connection to the provided EM and acquires its configuration and software if any.<br>The configuration may contain an address to another EM that this specific node shall use as EM.<br>The configuration may contain an address to another SeGW that should be used before connecting to the EM.<br>The eNB may then <ul style="list-style-type: none"> <li>- release the connection to the current EM and OAM SeGW and then restart (returning to step 1),</li> <li>- release the connection to the current EM and OAM SeGW and then return to step 6,</li> <li>- release the connection to the current EM and then repeat step 8, or</li> <li>- continue with step 9.</li> </ul> | Secure connection |
+| Step 9 (M) | The eNB establishes a connection to the Core Network(s) using the transport (VLAN ID, IP addresses) and security parameters provided in step 8. | |
+| Ends when | Ends when all mandatory steps identified above are successfully completed or when an exception occurs. | |
+| Exceptions | One of the steps identified above fails. | |
+| Post Conditions | One or more secure connections exist between the eNB and the Element Manager and the Core Network(s). Via the connection to the Element Manager the eNB can receive further instructions to become operational and carry user traffic, e.g. the administrativeState is set to "unlocked". | |
+| Traceability | All requirements of clause 5.2 and 6.5.3. | |
+
+Editor's note: The CA/RA server itself may be protected by a SeGW.
+
+Security aspects – e.g. prevention of unauthorized network access and of fake parameters supplied to the eNBs etc. - have special importance. Security related sub-steps to establish secure connections are not shown in table 6.4.3-1. More security aspects are described in a specific chapter (see clause 4.3.3).
+
+## 6.5 Requirements
+
+### 6.5.1 Automatic Radio Network Configuration Data Handling
+
+**REQ-ARCF-FUN-1:** IRPManager shall be able to transfer the ARCF data to IRPAgent or indicate to IRPAgent where the ARCF data is available for downloading.
+
+**REQ-ARCF-FUN-2:** IRPManager should be able to request IRPAgent to validate the previously downloaded ARCF data.
+
+**REQ-ARCF-FUN-3:** IRPAgent shall be able to check the consistency, syntax and semantic of the downloaded ARCF data to ensure that the ARCF data can be implemented in the network.
+
+### 6.5.2 Self-configuration of a new eNodeB
+
+The following requirements apply to the macro eNB only. Requirements for the HNB can be found in TR 32.821.
+
+The way to make any information available to eNB is outside the scope of standardisation.
+
+Conflict resolution in case of contradicting information made aware to the eNodeB is outside the scope of standardisation.
+
+#### 6.5.2.1 Self-Configuration Management and Monitoring
+
+##### 6.5.2.1.1 Management Part
+
+###### **REQ\_SCMAN\_FUN\_1**
+
+It shall be possible for an IRPManager to retrieve
+
+- information regarding how an NE or a group of NEs behaves during self-configuration, i.e. in which sequence the essential steps of self-configuration are executed
+ - information regarding where the IRPManager can interact with a self-configuration - by suspending the self-configuration process at one or more self-configuration stop points.
+- Steps, their sequence and their stop point qualification are not imposed by the standard.
+
+###### **REQ\_SCMAN\_FUN\_2**
+
+If choices for stop points to suspend the SWM process are offered, then it shall be possible for an IRPManager to choose/select among them where it will suspend (stop) a self-configuration process (i.e. to ensure fulfillment of pre-conditions for the step like the fulfillment of the presence of required input data for the step).
+
+The IRPManager shall be able to read or select or de-select the stop points offered.
+
+The IRPManager shall be informed about creation and deletion of a profile which is a holder of information regarding the offered self configuration steps, the offered sequence of the steps and the configuration steps stop points.
+
+The IRPManager should be able to change the content of a created profile and be informed about the change.
+
+###### **REQ\_SCMAN\_FUN\_3**
+
+It shall be possible for an IRPManager to resume a suspended self-configuration for one or multiple NEs.
+
+###### **REQ\_SCMAN\_FUN\_4**
+
+It shall be possible for an IRPManager to terminate an currently ongoing self-configuration for one or multiple NEs. After a termination it is not possible to resume the self-configuration.
+
+##### 6.5.2.1.2 Monitoring Part
+
+###### **REQ\_SCMON\_FUN\_1**
+
+The IRPAgent shall send an alarm in case of failures during the self-configuration process.
+
+###### **REQ\_SCMON\_FUN\_2**
+
+The IRPAgent should report the progress of a self-configuration of one or multiple NEs to the IRPManager.
+
+###### **REQ\_SCMON\_FUN\_3**
+
+When a self-configuration profile is created or deleted, then the IRPAgent shall inform the IRPManager about this creation and deletion.
+
+When the optional change of a self-configuration profile is performed, then the IRPAgent shall inform the IRPManager about such a change.
+
+###### **REQ\_SCMON\_FUN\_4**
+
+It shall be possible for IRPManager to retrieve information about the progress of a self-configuration.
+
+###### **REQ\_SCMON\_FUN\_5**
+
+The IRPAgent shall send a notification about the start, stop, completion and optionally cancellation of a self-configuration.
+
+###### **REQ\_SCMON\_FUN\_6**
+
+The IRPAgent shall inform the IRPManager whenever the self-configuration process has been suspended or resumed
+
+#### 6.5.2.2 Software Management
+
+**REQ\_SCSW\_FUN\_1** see **REQ\_SWM\_FUN\_1** in 32.531
+
+**REQ\_SCSW\_FUN\_2** see **REQ\_SWM\_FUN\_2** in 32.531
+
+**REQ\_SCSW\_FUN\_3** see **REQ\_SWM\_FUN\_4** in 32.531
+
+**REQ\_SCSW\_FUN\_4** see **REQ\_SWM\_FUN\_5** in 32.531
+
+**REQ\_SCSW\_FUN\_5** see **REQ\_ASWM\_FUN\_1** in 32.531
+
+**REQ\_SCSW\_FUN\_6** see **REQ\_ASWM\_FUN\_2** in 32.531
+
+**REQ\_SCSW\_FUN\_7** see **REQ\_ASWM\_FUN\_3** in 32.531
+
+**REQ\_SCSW\_FUN\_8** see **REQ\_ASWM\_FUN\_4** in 32.531
+
+**REQ\_SCSW\_FUN\_9** see **REQ\_ASWM\_FUN\_5** in 32.531
+
+#### 6.5.2.3 Address Allocation and OAM Connectivity Establishment
+
+##### **REQ\_SCOCE\_FUN\_1**
+
+The automatic establishment of the OAM connectivity shall be fully secured.
+
+##### **REQ\_SCOCE\_FUN\_2**
+
+The IRPManager shall be informed that the eNB has reached OAM connectivity.
+
+#### 6.5.2.4 Inventory Update
+
+The details of the inventory information to be reported are FFS.
+
+#### 6.5.2.5 Self-Test
+
+FFS
+
+#### 6.5.2.6 Radio Configuration Data
+
+FFS
+
+#### 6.5.2.7 Transport Configuration Data
+
+FFS
+
+#### 6.5.2.8 Call Processing Link Set-Up
+
+FFS
+
+#### 6.5.2.9 NRM IRP Update
+
+##### **REQ\_SCNRMU\_FUN\_1**
+
+The related E-UTRAN NRM IRP and EPC NRM IRP instances shall be created and updated.
+
+### 6.5.3 Specification Requirements for Multi-Vendor Plug and Play eNB connection to network
+
+**REQ\_PnP\_FUN\_1** The establishment of secure tunnels from the eNB to the OAM or Core Network(s) shall support NAT traversal.
+
+# 7. Functions and Architecture
+
+## 7.1 Self-Configuration Logical Architecture
+
+The lines between the functional blocks do not indicate specific 3GPP interfaces.
+
+For the abbreviations used, please see the headlines of chapter 4.
+
+
+
+The diagram illustrates the Self-Configuration Logical Architecture. At the top, an **Actor** is connected via a double-headed vertical arrow to a green rectangular block labeled **SC\_MMF**. Below **SC\_MMF**, a horizontal line acts as a communication bus. Below this bus, there are two rows of orange rectangular functional blocks. The top row contains five blocks: **AAF**, **SW\_MF**, **Inv\_UF**, **R\_CD\_F**, and **CPL\_SUF**. The bottom row contains four blocks: **OAM CO\_EF**, **ST\_F**, **NRM\_UF**, and **T\_CD\_F**. Each block in the top row is connected to the bus via a double-headed vertical arrow. Each block in the bottom row is connected to the bus via a double-headed vertical arrow. Additionally, each block in the bottom row is connected to the block directly above it via a double-headed vertical arrow: **OAM CO\_EF** to **AAF**, **ST\_F** to **SW\_MF**, **NRM\_UF** to **Inv\_UF**, and **T\_CD\_F** to **R\_CD\_F**.
+
+Diagram of Self-Configuration Logical Architecture showing functional blocks and their interactions.
+
+Figure 7.1-1: Self-Configuration Logical Architecture
+
+## 7.2 Self-Configuration Reference Model
+
+The SC\_MMF has a part located in the EM and a part located at the NM.
+
+For the abbreviations used, please refer to Chapter 4.
+
+
+
+The diagram illustrates the Self-Configuration Reference Model hierarchy. At the top is a green box labeled 'SC\_MMF\_NM (IRPManager)'. Below it is a horizontal red line labeled 'Itf-N'. Below the interface is another green box labeled 'SC\_MMF\_EM (IRPAgent)'. Below this box is a horizontal black line representing a bus. Below the bus are two rows of orange boxes. The top row contains five boxes: 'AAF', 'SW\_MF', 'Inv\_UF', 'R\_CD\_F', and 'CPL\_SUF'. The bottom row contains four boxes: 'OAM CO\_EF', 'ST\_F', 'NRM\_UF', and 'T\_CD\_F'. Double-headed vertical arrows connect the 'SC\_MMF\_EM' box to the bus, and each box in the top row to the bus. Additionally, double-headed vertical arrows connect each box in the top row to its corresponding box in the bottom row: 'AAF' to 'OAM CO\_EF', 'SW\_MF' to 'ST\_F', 'Inv\_UF' to 'NRM\_UF', 'R\_CD\_F' to 'T\_CD\_F', and 'CPL\_SUF' to 'T\_CD\_F'.
+
+Diagram of the Self-Configuration Reference Model showing the hierarchy from SC\_MMF\_NM (IRPManager) down to various functional blocks like AAF, SW\_MF, Inv\_UF, R\_CD\_F, CPL\_SUF, OAM CO\_EF, ST\_F, NRM\_UF, and T\_CD\_F, separated by the Itf-N interface.
+
+Figure 7.2-1: Self-Configuration Reference Model
+
+# --- Annex A (informative): Graphical representation of the PnC Use Case
+
+The Multi-Vendor eNB Plug and Connect procedure, given in section 6.4.3 are classified into two sets corresponding to those conducted at External Network (or Non-secure Operator Network) and those conducted at the Secure Operator Network. An interpretation of these procedures is depicted in figures A.1 and A.2 respectively.
+
+
+
+```
+graph TD; PnP_eNB([PnP eNB Factory-preconfigured]) --> eNB_Power_up[eNB Power up]; PnP_eNB --> Config[Vendor Certificate, FQDN of CA/RA Server, FQDN of OAM SeGW, FQDN/IP address of EMs]; ConfigInfo[Outer IP auto-configuration Information, FQDN/IP Address of OAM SeGW, FQDN/IP Address of CA/RA Servers] --> IP_Auto[IP Autoconfiguration services]; IP_Auto --> eNB_Power_up; eNB_Power_up --> eNB_Comm[eNB starts communicating on native VLAN & acquires its Outer IP autoconfig information]; eNB_Comm --> IP_CARA_Avail{IP Address of CA/RA servers available?}; IP_CARA_Avail -- yes --> IP_CARA_Acquired[IP Address of CA/RA acquired]; IP_CARA_Avail -- No --> FQDN_CARA_Avail{FQDN of CA/RA servers available?}; FQDN_CARA_Avail -- yes --> FQDN_CARA_DNS[FQDN resolved to IP Address by DNS]; FQDN_CARA_Avail -- No --> IP_OAM_Avail; FQDN_CARA_DNS --> IP_CARA_Acquired; IP_CARA_Acquired --> Cert_Enrol[eNB completes Certificate Enrolment]; Cert_Enrol --> IP_OAM_Avail{IP Address of OAM SeGW available?}; IP_OAM_Avail -- yes --> IP_OAM_Acquired[IP Address of initial OAM SeGW acquired]; IP_OAM_Avail -- No --> FQDN_OAM_Avail{FQDN of OAM SeGW available?}; FQDN_OAM_Avail -- yes --> FQDN_OAM_DNS[FQDN resolved to IP Address by DNS]; FQDN_OAM_Avail -- No --> IP_CARA_Avail; FQDN_OAM_DNS --> IP_OAM_Acquired; IP_OAM_Acquired --> Secure_Conn[Secure Connection to OAM SeGW Established]; Secure_Conn --> B((B));
+```
+
+Flowchart of PnC procedure for the External Network or Non-secure Operator Network. The process starts with a PnP eNB Factory-preconfigured, which receives initial configuration (Vendor Certificate, FQDN of CA/RA Server, FQDN of OAM SeGW, FQDN/IP address of EMs) and IP Autoconfiguration services (Outer IP auto-configuration Information, FQDN/IP Address of OAM SeGW, FQDN/IP Address of CA/RA Servers). The eNB powers up and starts communicating on native VLAN to acquire Outer IP autoconfig information. It then checks if the IP Address of CA/RA servers is available. If not, it checks if the FQDN of CA/RA servers is available. If the FQDN is available, it resolves it to an IP Address by DNS. Both paths lead to 'IP Address of CA/RA acquired'. Next, the eNB completes Certificate Enrolment. It then checks if the IP Address of OAM SeGW is available. If not, it checks if the FQDN of OAM SeGW is available. If the FQDN is available, it resolves it to an IP Address by DNS. Both paths lead to 'IP Address of initial OAM SeGW acquired'. Finally, a Secure Connection to OAM SeGW is Established, leading to connector B.
+
+Figure A.1: PnC procedure for the External Network or Non-secure Operator Network.
+
+
+
+
+
+```
+graph TD; B((B)) --> PnP_eNB(PnP eNB With Secure Connection to OAM SeGW); IP_Auto[IP Autoconfiguration services] -- "(Inner) IP auto-configuration Information" --> PnP_eNB; Initial_OAM[Initial OAM SeGW] -- "(Inner) IP auto-configuration Information" --> PnP_eNB; PnP_eNB --> DNS_Info["(Inner) IP auto-configuration information & IP address of one or more DNS obtained (from either IP Auto. Config Services or OAM SeGW)"]; DNS_Info --> EMS_IP_Avail{IP Address of EMS available?}; EMS_IP_Avail -- yes --> EMS_IP_Acquired[IP Address of EMS acquired]; EMS_IP_Avail -- No --> EMS_FQDN_Avail{FQDN of EMS available?}; EMS_FQDN_Avail -- yes --> FQDN_Resolved[FQDN resolved to IP Address by DNS]; EMS_FQDN_Avail -- No --> PnP_eNB; FQDN_Resolved --> EMS_IP_Acquired; EMS_IP_Acquired --> Conn_Established[Connection Established to EMS]; Conn_Established --> Acquire_SW[eNB acquires its configuration & SW]; Acquire_SW --> Core_Net[eNB Establish a connection to the Core Network (using transport VLAN ID & IP address)];
+```
+
+Flowchart of PnC Procedure for the secure Operator Network. The process starts at connector 'B', leading to 'PnP eNB With Secure Connection to OAM SeGW'. This eNB receives '(Inner) IP auto-configuration Information' from 'IP Autoconfiguration services' and 'Initial OAM SeGW'. It then obtains '(Inner) IP auto-configuration information & IP address of one or more DNS obtained (from either IP Auto. Config Services or OAM SeGW)'. A decision 'IP Address of EMS available?' follows. If 'yes', it proceeds to 'IP Address of EMS acquired'. If 'No', it checks 'FQDN of EMS available?'. If 'yes', it performs 'FQDN resolved to IP Address by DNS' before proceeding to 'IP Address of EMS acquired'. If 'No', it loops back to the input of 'PnP eNB'. Subsequent steps are 'IP Address of EMS acquired', 'Connection Established to EMS', 'eNB acquires its configuration & SW', and finally 'eNB Establish a connection to the Core Network (using transport VLAN ID & IP address)'.
+
+Figure A.2: PnC Procedure for the secure Operator Network.
+
+
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|-----|-----|-----------------------------------------------------------|--------|---------------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
+| 2008-12 | SP-42 | SP-080713 | -- | -- | Submitted to SA#42 information and approval | 1.0.0 | 8.0.0 |
+| 2009-09 | SP-45 | SP-090627 | 001 | -- | Removal of inconsistency | 8.0.0 | 9.0.0 |
+| 2010-03 | SP-47 | SP-100035 | 002 | -- | Clarifying Editor's Notes in TS 32.501 | 9.0.0 | 9.1.0 |
+| 2010-03 | SP-47 | SP-100035 | 003 | -- | Introducing ARCF (Automatic Radio Configuration Function) | 9.0.0 | 9.1.0 |
+| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 |
+| 2012-09 | SP-57 | SP-120645 | 004 | 1 | Clarification of eNodeB state after self-configuration | 10.0.0 | 11.0.0 |
+| 2013-09 | SP-61 | SP-130465 | 006 | - | Introducing MUPPET features | 11.0.0 | 12.0.0 |
+| 2013-12 | SP-62 | SP-130629 | 007 | 3 | VLAN option for Stage 1 | 12.0.0 | 12.1.0 |
+| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.1.0 | <b>13.0.0</b> |
+| 2017-04 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | <b>14.0.0</b> |
+| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | <b>15.0.0</b> |
+| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | <b>16.0.0</b> |
+| 2022-04 | - | - | - | - | Update to Rel-17 version (MCC) | 16.0.0 | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | Update to Rel-18 version (MCC) | 17.0.0 | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32506/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/32_series/32506/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f6a54d75f7e84399910303fc77fb434870632b2
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62c848a3330337c6698cb9fe89cbe191e2db3ce6e032808b81154b13967f0b59
+size 32125
diff --git a/marked/Rel-18/32_series/32506/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-18/32_series/32506/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1eedc4c826076eb49f6efd2cf69cdfaad7c8f9a4
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41843222d74d3f5e711758975e0338c36d4ef15b5a76703e7bd751c1f81a41da
+size 24577
diff --git a/marked/Rel-18/32_series/32506/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-18/32_series/32506/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed05466b483ce3c95d3ac549d653b3465abead56
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5a17e2036b5fb1972e0b58bd68dad8234d0d92ce1dcf2260c1b1ba9b8f93886
+size 42920
diff --git a/marked/Rel-18/32_series/32506/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/32_series/32506/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cba51b3be117b51cda6acab288e94f5ed1ebd58a
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66fa09ed3a102e337db0a02a7d882960f5028d7f4ebc7aacd92ea4822618ffa5
+size 9584
diff --git a/marked/Rel-18/32_series/32506/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/32_series/32506/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be393bfd08010e2b3a57bb6eeb4161772d2ad6ec
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:134825dde16dd49cdda8cef7549d9071eacc2a54aea8e414fdc73527928bba29
+size 7201
diff --git a/marked/Rel-18/32_series/32506/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-18/32_series/32506/844077b3034f0030b404207db0ad76b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe5e43352e86f9ea388ca92dc248514b67b3e94f
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/844077b3034f0030b404207db0ad76b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b4f6d81bd04b96e92b23efa2c762cd695fcdd69a5b9da08e11a8540c5d336f3
+size 98422
diff --git a/marked/Rel-18/32_series/32506/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-18/32_series/32506/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..06366e1549e275bc39bb175930466925c3351df1
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06f94f3627f173e8755954c48cebcc1d6c36adcad8d943bd8fa9879fa5d153d4
+size 36807
diff --git a/marked/Rel-18/32_series/32506/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/32_series/32506/90ddb84c323b956e2d50a54d3f870566_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c530b0993eab016acb8077652b8e06ef8fd0c8e
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/90ddb84c323b956e2d50a54d3f870566_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d11830cd66e96293ba64483b123fafeba7302f3f8302fafa4eb50d4dcd820554
+size 48274
diff --git a/marked/Rel-18/32_series/32506/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-18/32_series/32506/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bb329414696dae586619696212d4b26dda52227a
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f83794ebd3df0f9beb1314c1231e5bf85933be912aaaeb4ade521dd210949838
+size 30009
diff --git a/marked/Rel-18/32_series/32506/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Rel-18/32_series/32506/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..22f7bd7f270141835f320baca8cc6be93bcecb3a
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6cb51c7514fcfe21d91b6109cc00aa886b19191c4e9da94cf66e2ae633701a55
+size 86968
diff --git a/marked/Rel-18/32_series/32506/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-18/32_series/32506/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62f0afe7eaf9bf05e129fbb751a50c4bdef41e26
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9eb912e045c0ee254cbfc9131479582aaf640b2f574f531f73136e7ecf3aea9
+size 162281
diff --git a/marked/Rel-18/32_series/32506/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-18/32_series/32506/e354b57563dae469c00b412b2abdf765_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..802c29dc3605c4fe486d32027ca1587bcc1aa990
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/e354b57563dae469c00b412b2abdf765_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8941152fdd1622cff2751feecd43e92112a74fd80f66779c5c6588062426cac3
+size 22273
diff --git a/marked/Rel-18/32_series/32506/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-18/32_series/32506/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4464d8014ce3298f1d7ee2dbd4d35b0b6fac673a
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7886ddc258a1c018461f27fc0399b2d88b3c665424dc6d228c903b840a365f75
+size 58324
diff --git a/marked/Rel-18/32_series/32506/raw.md b/marked/Rel-18/32_series/32506/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b68ebfe87429ce8029faa910a71e35450fd69c50
--- /dev/null
+++ b/marked/Rel-18/32_series/32506/raw.md
@@ -0,0 +1,2220 @@
+
+
+# 3GPP TS 32.506 V18.0.0 (2024-04) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Solution Set (SS) definitions (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## --- **Keywords**
+
+management, CORBA XML SOAP
+
+## **3GPP**
+
+### --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| Introduction ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 8 |
+| 4 Solution Set definitions ..... | 9 |
+| <b>Annex A (normative): CORBA Solution Set.....</b> | <b>10</b> |
+| A.1 Architectural features..... | 10 |
+| A.1.1 Syntax for Distinguished Names..... | 10 |
+| A.1.2 Notification Services ..... | 10 |
+| A.1.3 Push and Pull Style..... | 10 |
+| A.1.4 Support multiple notifications in one push operation ..... | 10 |
+| A.2 Mapping ..... | 11 |
+| A.2.1 Operation and Notification mapping..... | 11 |
+| A.2.2 Operation parameter mapping..... | 11 |
+| A.2.3 Notification parameter mapping..... | 14 |
+| A.3 Solution Set definitions ..... | 15 |
+| A.3.1 IDL definition structure..... | 15 |
+| A.3.2 IDL specification (file name "SelfConfIRPConstDefs.idl") ..... | 16 |
+| A.3.3 IDL specification (file name "SelfConfIRPSystem.idl") ..... | 17 |
+| A.3.4 IDL specification (file name "SelfConfIRPNotifications.idl") ..... | 20 |
+| <b>Annex B (normative): XML definitions.....</b> | <b>22</b> |
+| B.1 Architectural Features ..... | 22 |
+| B.1.1 Syntax for Distinguished Names..... | 22 |
+| B.1.2 Notification Services ..... | 22 |
+| B.1.3 IOC Definitions ..... | 22 |
+| B.2 Mapping ..... | 22 |
+| B.3 Solution Set definitions ..... | 22 |
+| B.3.1 XML definition structure ..... | 22 |
+| B.3.2 Graphical Representation ..... | 23 |
+| B.3.3 XML Schema "scIRPNotif.xsd" ..... | 27 |
+| B.3.4 XML Schema "scIRPIOCs.xsd" ..... | 30 |
+| <b>Annex C (normative): SOAP Solution Set.....</b> | <b>32</b> |
+| C.1 Architectural features..... | 32 |
+| C.1.1 Syntax for Distinguished Names..... | 32 |
+| C.1.2 Notification Services ..... | 32 |
+| C.1.3 Supported W3C specifications ..... | 32 |
+| C.1.4 Prefixes and namespaces..... | 32 |
+| C.2 Mapping ..... | 33 |
+| C.2.1 Operation and Notification mapping..... | 33 |
+| C.2.2 Operation parameter mapping..... | 33 |
+| C.2.2.1 Operation listScManagementCapabilities ..... | 34 |
+| C.2.2.1.1 Input parameters ..... | 34 |
+| C.2.2.1.2 Output parameters..... | 34 |
+| C.2.2.1.3 Fault definition..... | 34 |
+
+| | | |
+|-------------------------------|---------------------------------------------|-----------|
+| C.2.2.2 | Operation listScManagementProfiles ..... | 34 |
+| C.2.2.2.1 | Input parameters ..... | 34 |
+| C.2.2.2.2 | Output parameters ..... | 34 |
+| C.2.2.3 | Operation createScManagementProfile ..... | 35 |
+| C.2.2.3.1 | Input parameters ..... | 35 |
+| C.2.2.3.2 | Output parameters ..... | 35 |
+| C.2.2.4 | Operation deleteScManagementProfile ..... | 35 |
+| C.2.2.4.1 | Input parameters ..... | 35 |
+| C.2.2.4.2 | Output parameters ..... | 36 |
+| C.2.2.5 | Operation listScProcesses ..... | 36 |
+| C.2.2.5.1 | Input parameters ..... | 36 |
+| C.2.2.5.2 | Output parameters ..... | 36 |
+| C.2.2.6 | Operation resumeScProcess ..... | 36 |
+| C.2.2.6.1 | Input parameters ..... | 36 |
+| C.2.2.6.2 | Output parameters ..... | 36 |
+| C.2.2.7 | Operation terminateSetProcess ..... | 37 |
+| C.2.2.7.1 | Input parameters ..... | 37 |
+| C.2.2.7.2 | Output parameters ..... | 37 |
+| C.2.2.8 | Operation changeScManagementProfile ..... | 37 |
+| C.2.2.8.1 | Input parameters ..... | 37 |
+| C.2.2.8.2 | Output parameters ..... | 37 |
+| C.3 | Solution Set definitions ..... | 38 |
+| C.3.1 | WSDL definition structure ..... | 38 |
+| C.3.2 | Graphical Representation ..... | 38 |
+| C.3.3 | WSDL specification "ScIRPSystem.wsdl" ..... | 39 |
+| <b>Annex D (informative):</b> | <b>Change history .....</b> | <b>47</b> |
+
+# --- Foreword
+
+This Technical Specification (TS) 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 present document is part of a TS-family covering the 3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
+
+- 32.501: Self-Configuration of Network Elements; Concepts and Integration Reference Point (IRP) Requirements
+- 32.502: Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS)
+- 32.506: Self-Configuration of Network Elements Integration Reference Point (IRP): Solution Set (SS) definitions "**
+
+The present document is part of a TS-family which describe the requirements and information model necessary for the Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
+
+For the purpose of Self-Configuration of Network Elements IRP, see TS 32.501 [3]
+
+# --- 1 Scope
+
+The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Self-Configuration of Network Elements Integration Reference Point (IRP): Information Service (3GPP TS 32.502 [4]).
+
+This Solution Set specification is related to 3GPP TS 32.502 V14.0.X [4].
+
+# --- 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.) 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 TS 32.101: "Telecommunication management; Principles and high level requirements".
+- [2] 3GPP TS 32.102: "Telecommunication management; Architecture".
+- [3] 3GPP TS 32.501: " Technical Specification Group Services and System Aspects; Telecommunication management; Self-Configuration of Network Elements; Concepts and Integration Reference Point (IRP) Requirements ".
+- [4] 3GPP TS 32.502: " Technical Specification Group Services and System Aspects; Telecommunication management; Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS)".
+- [5] 3GPP TR 32.816: "Telecommunication management; Study on Management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC)".
+- [6] OMG TC Document telecom/98-11-01: "OMG Notification Service".
+<http://www.omg.org/technology/documents/>
+- [7] 3GPP TS 32.531: "Telecommunication management; Software management; Concepts and Integration Reference Point (IRP) Requirements".
+- [8] 3GPP TS 32.532: "Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS)".
+- [9] 3GPP TS 32.536: "Telecommunication management; Software management Integration Reference Point (IRP); Solution Set definitions ".
+- [10] W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
+- [11] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
+- [12] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
+- [13] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
+- [14] W3C REC-xml-names-19990114: "Namespaces in XML".
+- [15] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements"
+
+- [16] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)".
+- [17] 3GPP TS 32.316: "Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set definitions ".
+- [18] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
+- [19] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions".
+- [20] W3C SOAP 1.1 specification (<http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>)
+- [21] W3C XPath 1.0 specification (<http://www.w3.org/TR/1999/REC-xpath-19991116>)
+- [22] W3C WSDL 1.1 specification (<http://www.w3.org/TR/2001/NOTE-wsdl-20010315>)
+- [23] W3C SOAP 1.2 specification (<http://www.w3.org/TR/soap12-part1/>)
+- [24] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], 3GPP TS 32.150 [18] and 3GPP TS 32.501 [3] and the following apply:
+
+**IRP document version number string (or "IRPVersion"):** See 3GPP TS 32.311 [15]
+
+**IRP:** See 3GPP TS 32.150 [18].
+
+**IRP Agent:** See 3GPP TS 32.150 [18].
+
+**IRP Manager:** See 3GPP TS 32.150 [18].
+
+**Self Configuration:** The process which brings a network element into service requiring minimal human operator intervention or none at all.
+
+**XML file:** file containing an XML document
+
+**XML document:** composed of the succession of an optional XML declaration followed by a root XML element
+
+NOTE: See [10]; in the scope of the present document.
+
+**XML declaration:** it specifies the version of XML being used
+
+NOTE: See [10].
+
+**XML element:** has a type, is identified by a name, may have a set of XML attribute specifications and is either composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements
+
+NOTE: See [10].
+
+**empty XML element:** having an empty XML content; an empty XML element still possibly has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag
+
+NOTE: See [10].
+
+**XML content (of an XML element):** empty if the XML element is simply composed of an XML empty-element tag; otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag
+
+**XML start-tag:** the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML element
+
+NOTE: See [10].
+
+**XML end-tag:** the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element
+
+NOTE: See [10].
+
+**XML empty-element tag:** composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element.
+
+NOTE: See [10].
+
+**XML attribute specification:** has a name and a value
+
+NOTE: See [10].
+
+**DTD:** defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD
+
+NOTE: See [10].
+
+**XML schema:** more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document to conform with this XML schema; through the use of XML namespaces several XML schemas can be used together by a single XML document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas
+
+NOTE: See [11], [12] and [13].
+
+**XML namespace:** enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas
+
+NOTE: See [14], in the scope of the present document.
+
+**XML complex type:** defined in an XML schema; cannot be directly used in an XML document; can be the concrete type or the derivation base type for an XML element type or for another XML complex type; ultimately defines constraints for an XML element on its XML attribute specifications and/or its XML content
+
+NOTE: See [11], [12] and [13].
+
+**XML element type:** declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type
+
+NOTE: See [11], [12] and [13].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|------|----------------------------------|
+| IS | Information Service |
+| SC | Self Configuration |
+| SS | Solution Set |
+| WSDL | Web Service Description Language |
+| XML | eXtensible Markup Language |
+
+# --- 4 Solution Set definitions
+
+This specification defines the following 3GPP Self-Configuration of Network Elements IRP Solution Set definitions:
+
+Annex A provides the CORBA Solution Set.
+
+Annex B provides the XML Definitions.
+
+Annex C provides the SOAP Solution Set.
+
+# --- Annex A (normative): CORBA Solution Set
+
+This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Self-Configuration of Network Elements IRP: Information Service (3GPP TS 32.502 [4]).
+
+## --- A.1 Architectural features
+
+The overall architectural feature of Self-Configuration of Network Elements IRP is specified in 3GPP TS 32.502 [4].
+
+### A.1.1 Syntax for Distinguished Names
+
+The format of a Distinguished Name is defined in 3GPP TS 32.300 [24].
+
+The version of this IRP is represented as a string (see also clause 3 for versions).
+
+### A.1.2 Notification Services
+
+Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.306 [19]).
+
+The contents of the SCIRP notifications are defined in the present document.
+
+### A.1.3 Push and Pull Style
+
+OMG Notification Service defines two styles of interaction. One is called push style. In this style, IRPAgent pushes notifications to IRPManager as soon as they are available. The other is called pull style. In this style, IRPAgent keeps the notifications till IRPManager requests for them.
+
+This CORBA SS specifies that support of Push style is Mandatory (M) and that support of Pull style is Optional (O).
+
+### A.1.4 Support multiple notifications in one push operation
+
+For efficiency reasons, IRPAgent may send multiple notifications using one single push operation. To pack multiple notifications into one push operation, IRPAgent may wait and not invoke the push operation as soon as notifications are available. To avoid IRPAgent to wait for an extended period of time that is objectionable to IRPManager, IRPAgent shall implement an IRPAgent wide timer configurable by administrator. On expiration of this timer, IRPAgent shall invoke push if there is at least one notification to be conveyed to IRPManager. This timer is re-started after each push invocation.
+
+## A.2 Mapping
+
+### A.2.1 Operation and Notification mapping
+
+Software Management IRP: IS 3GPP TS (see 3GPP TS 32.502 [4]) defines semantics of operations and notifications visible across the Itf-N. Table A.2.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
+
+**Table A.2.1: Mapping from IS Notification/Operation to SS equivalents**
+
+| IS Operation/ notification<br>Self-Configuration IRP: IS 3GPP TS 32.502[4] | SS Method | Qualifier |
+|----------------------------------------------------------------------------|-----------------------------------------------|-----------|
+| listScManagementCapabilities | listScManagementCapabilities | M |
+| listScManagementProfiles | listScManagementProfiles | M |
+| createScManagementProfile | createScManagementProfile | M |
+| deleteScManagementProfile | deleteScManagementProfile | M |
+| listScProcesses | listScProcesses | M |
+| resumeScProcess | resumeScProcess | M |
+| swFallback | swFallback | M |
+| terminateScManagementProcess | terminateScManagementProcess | M |
+| changeScManagementProfile | changeScManagementProfile | O |
+| notifyScManagementProfileCreation | notifyScManagementProfileCreation | M |
+| notifyScManagementProfileDeletion | notifyScManagementProfileDeletion | M |
+| notifyScManagementProcessCreation | notifyScManagementProcessCreation | M |
+| notifyScManagementProcessStage | notifyScManagementProcessStage | M |
+| notifyScManagementProcessDeletion | notifyScManagementProcessDeletion | M |
+| notifyNewScManagementCapabilitiesAvailability | notifyNewScManagementCapabilitiesAvailability | O |
+| notifyScManagementProfileChange | notifyScManagementProfileChange | O |
+
+### A.2.2 Operation parameter mapping
+
+Reference 3GPP TS 32.302 defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+**Table A.2.2-1: Mapping from IS listScManagementCapabilities parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| result | Exceptions:<br>SelfConfIRPConstDefs::ListScManagementCapabilities,<br>GenericIRPManagementSystem::ParameterNotSupported,<br>GenericIRPManagementSystem::InvalidParameter,<br>GenericIRPManagementSystem::ValueNotSupported,<br>GenericIRPManagementSystem::OperationNotSupported | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS listSwMCapabilities parameters to SS equivalents
+
+**Table A.2.2-2: Mapping from IS listScManagementProfiles parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| result | Exceptions:<br>SelfConfIRPConstDefs::ListScManagementProfile,<br>GenericIRPManagementSystem::ParameterNotSupported,<br>GenericIRPManagementSystem::InvalidParameter,<br>GenericIRPManagementSystem::ValueNotSupported,<br>GenericIRPManagementSystem::OperationNotSupported | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS listSwMProfiles parameters to SS equivalents
+
+**Table A.2.2-3: Mapping from IS `createScManagementProfile` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>result</code> | Exceptions:<br><code>SelfConfIRPConstDefs::CreateScManagementProfile</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `createSwMProfile` parameters to SS equivalents
+
+**Table A.2.2-4: Mapping from IS `deleteScManagementProfile` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>result</code> | Exceptions:<br><code>SelfConfIRPConstDefs::DeleteScManagementProfile</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `deleteSwMProfile` parameters to SS equivalents
+
+**Table A.2.2-5: Mapping from IS `listScManagementProcesses` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>Result</code> | Exceptions:<br><code>SelfConfIRPConstDefs::ListScManagementProcesses</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `listSwMProcesses` parameters to SS equivalents
+
+**Table A.2.2-6: Mapping from IS `resumeScManagementProcess` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>Result</code> | Exceptions:<br><code>SelfConfIRPConstDefs::ResumeScManagementProcess</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `resumeSwMProcess` parameters to SS equivalents
+
+**Table A.2.2-7: Mapping from IS `swFallback` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>Result</code> | Exceptions:<br><code>SelfConfIRPConstDefs::SwFallback</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `swFallback` parameters to SS equivalents
+
+**Table A.2.2-8: Mapping from IS `terminateScManagementProcess` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| <code>Result</code> | Exceptions:<br><code>SelfConfIRPConstDefs::TerminateScManagementProcess</code> ,<br><code>GenericIRPManagementSystem::ParameterNotSupported</code> ,<br><code>GenericIRPManagementSystem::InvalidParameter</code> ,<br><code>GenericIRPManagementSystem::ValueNotSupported</code> ,<br><code>GenericIRPManagementSystem::OperationNotSupported</code> | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `terminateSwMProcess` parameters to SS equivalents
+
+**Table A.2.2-9: Mapping from IS `changeScManagementProfile` parameters to SS equivalents**
+
+| IS Operation parameter | SS Method parameter | Qualifier |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| Result | Exceptions:<br>SelfConfIRPConstDefs::CreateScManagementProfile,<br>GenericIRPManagementSystem::ParameterNotSupported,<br>GenericIRPManagementSystem::InvalidParameter,<br>GenericIRPManagementSystem::ValueNotSupported,<br>GenericIRPManagementSystem::OperationNotSupported | M |
+
+For all other parameters see TS 32.536 [9] mapping from IS `changeSwMProfile` parameters to SS equivalents
+
+### A.2.3 Notification parameter mapping
+
+Reference 3GPP TS 32.502 [4] defines semantics of parameters carried in notifications. The following tables indicate the mapping of these parameters to their SS equivalents."
+
+The following tables indicate the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification Service [6]) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service [6], is:
+
+```
+Header
+ Fixed Header
+ domain_name
+ type_name
+ event_name
+ Variable Header
+Body
+ filterable_body_fields
+ remaining_body
+```
+
+The following tables list all OMG Structured Event attributes in the second column. The first column identifies the Software Management IRP: IS [8] defined notification parameters.
+
+**Table A.2.3.1: Mapping for notifyScManagementProfileCreation**
+
+See TS 32.536 [9] mapping from IS **notifySwMProfileCreation**
+
+**Table A.2.3.2: Mapping for notifyScManagementProfileDeletion**
+
+See TS 32.536 [9] mapping from IS **notifySwMProfileDeletion**
+
+**Table A.2.3.3: Mapping for notifyScProcessCreation**
+
+See TS 32.536 [9] mapping from IS **notifySwMProcessCreation**
+
+**Table A.2.3.4: Mapping for notifyScProcessStage**
+
+See TS 32.536 [9] mapping from IS **notifySwMProcessStage**
+
+**Table A.2.3.5: Mapping for notifyScProcessDeletion**
+
+See TS 32.536 [9] mapping from IS **notifySwMProcessDeletion**
+
+**Table A.2.3.6: Mapping for notifyNewScManagementCapabilityAvailability**
+
+| IS Parameters | <SS> Parameters | Qualifier | Comment |
+|--------------------------------------------|-------------------------------------------------------------|-----------|---------|
+| id | SwMIRPConstDefs::Id | M | |
+| nEInformation | SwMIRPConstDefs::NEInformation | M | |
+| stepsAndOfferedStopPointList | SwMIRPConstDefs::StepsAndOfferedStopPointList | M | |
+| offeredFinalAdministrativeStateInformation | SwMIRPConstDefs::OfferedFinalAdministrativeStateInformation | M | |
+| swVersionToBeInstalledOfferList | SwMIRPConstDefs::SwVersionToBeInstalledOfferListConditional | C | |
+
+**Table A.2.3.7: Mapping for notifyScManagementProfileChange**
+
+See TS 32.536 [9] mapping from IS **notifySwMProfileChange**
+
+## --- A.3 Solution Set definitions
+
+### A.3.1 IDL definition structure
+
+Clause A.3.2 defines the constants and types used by the SC Management IRP.
+
+Clause A.3.3 defines the operations which are performed by the SC Management IRP agent.
+
+Clause A.3.4 defines the notifications which are emitted by the SC Management IRP agent.
+
+### A.3.2 IDL specification (file name "SelfConfIRPConstDefs.idl")
+
+```
+// File: SelfConfIRPConstDefs.idl
+#ifndef _SELF_CONF_IRP_CONST_DEFS_IDL_
+#define _SELF_CONF_IRP_CONST_DEFS_IDL_
+
+#include <KernelCmConstDefs.idl>
+#include <NotificationIRPConstDefs.idl>
+#include <SwMIRPConstDefs.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: SelfConfIRPConstDefs */
+
+module SelfConfIRPConstDefs
+{
+
+/*****
+ * definition of types used in operations for Self-Configuration : */
+/*****
+
+/* currently all types used in operations imported from 32.536 */
+
+/*****
+ * definition of types in notifications for self-configuration : */
+/*****
+
+ enum TriggerForDeletion { IRP_AGENT_TERMINATION, IRP_MANAGER_TERMINATION,
+ SELF_CONFIGURATION_SUCCESSFULLY_CONCLUDED };
+
+ interface AttributeNameValue
+ {
+ const string ID = "ID";
+ const string NE_INFORMATION = "NE_INFORMATION";
+ const string STEPS_AND_OFFERED_STOP_POINT_LIST = "STEPS_AND_OFFERED_STOP_POINT_LIST";
+ const string OFFERED_FINAL_ADMINISTRATIVE_STATE_INFORMATION =
+ "OFFERED_FINAL_ADMINISTRATIVE_STATE_INFORMATION";
+ const string SW_VERSION_TO_BE_INSTALLED_OFFER_LIST = "SW_VERSION_TO_BE_INSTALLED_OFFER_LIST";
+ };
+
+};
+
+#endif // _SELF_CONF_IRP_CONST_DEFS_IDL_
+```
+
+### A.3.3 IDL specification (file name "SelfConfIRPSystem.idl")
+
+```
+//File: SelfConfIRPSystem.idl
+#ifndef _SELF_CONF_IRP_SYSTEM_IDL_
+#define _SELF_CONF_IRP_SYSTEM_IDL_
+
+#include <SelfConfIRPConstDefs.idl>
+#include <SwMIRPConstDefs.idl>
+#include <GenericIRPManagementSystem.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/* ## Module: SelfConfIRPSystem */
+
+module SelfConfIRPSystem
+{
+
+ /*
+ If the system fails to complete an operation, then it can provide a reason
+ to qualify the exception. The semantics carried in this reason are outside
+ the scope of the present document.
+ */
+ exception ListScManagementCapabilities { string reason; };
+ exception ListScManagementProfiles { string reason; };
+ exception CreateScManagementProfile { string reason; };
+ exception DeleteScManagementProfile { string reason; };
+ exception ListScProcesses { string reason; };
+ exception ResumeScProcess { string reason; };
+ exception SwFallback { string reason; };
+ exception TerminateScProcess { string reason; };
+ exception ChangeScManagementProfile { string reason; };
+
+ interface SelfConfIRPOperations_1
+ {
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result listScManagementCapabilities
+ (
+ in SwMIRPConstDefs::NEInformationOpt nEInformation,
+ out SwMIRPConstDefs::CapabilitiesList capabilitiesList
+ )
+ raises
+ (
+ ListScManagementCapabilities,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result listScProfiles
+ (
+ in SwMIRPConstDefs::NEInformationOpt nEInformation,
+ out SwMIRPConstDefs::ProfileList profileList
+ )
+ raises
+ (
+ ListScProfiles,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result createScManagementProfile
+ (
+ in SwMIRPConstDefs::IdOpt id,
+ in SwMIRPConstDefs::NEInformation nEInformation,
+ in SwMIRPConstDefs::SwVersionToBeInstalledOpt swVersionToBeInstalled,
+ in SwMIRPConstDefs::StepsAndSelectedStopPointList stepsAndSelectedStopPointList,
+ in SwMIRPConstDefs::SelectedFinalAdministrativeState selectedFinalAdministrativeState
+ )
+ }
+}
+```
+
+```
+ )
+ raises
+ (
+ CreateScManagementProfile,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result deleteScManagementProfile
+ (
+ in SwMIRPConstDefs::Id id
+ )
+ raises
+ (
+ DeleteScManagementProfile,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result listScProcesses
+ (
+ in SwMIRPConstDefs::NEIdentificationOpt nEIdentification,
+ out SwMIRPConstDefs::ProcessList processList
+ )
+ raises
+ (
+ ListScProcesses,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result resumeScProcess
+ (
+ in SwMIRPConstDefs::Id id
+ )
+ raises
+ (
+ ResumeScProcess,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result swFallback
+ (
+ in SwMIRPConstDefs::Filter filter,
+ out SwMIRPConstDefs::NEList nEList
+ )
+ raises
+ (
+ SwFallback,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result terminateScProcess
+ (
+ in SwMIRPConstDefs::Id id
+ )
+```
+
+```
+ raises
+ (
+ TerminateScProcess,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+ };
+
+ interface SelfConfIRPOperations_2
+ {
+ /* for the purpose of this operation see 3GPP TS 32.502 */
+ SwMIRPConstDefs::Result changeScManagementProfile
+ (
+ in SwMIRPConstDefs::Id id,
+ in SwMIRPConstDefs::NEInformation nEInformation,
+ in SwMConfIRPConstDefs::SwVersionToBeInstalledOpt swVersionToBeInstalled,
+ in SwMConfIRPConstDefs::StepsAndSelectedStopPointList stepsAndSelectedStopPointList,
+ in SwMIRPConstDefs::SelectedFinalAdministrativeState selectedFinalAdministrativeState
+ )
+ raises
+ (
+ ChangeScManagementProfile,
+ GenericIRPManagementSystem::ParameterNotSupported,
+ GenericIRPManagementSystem::InvalidParameter,
+ GenericIRPManagementSystem::ValueNotSupported,
+ GenericIRPManagementSystem::OperationNotSupported
+ );
+ };
+
+};
+
+#endif // _SELF_CONF_IRP_SYSTEM_IDL_
+```
+
+### A.3.4 IDL specification (file name "SelfConfIRPNotifications.idl")
+
+```
+
+//File: SelfConfIRPNotifications.idl
+#ifdef _SELF_CONF_IRP_NOTIFICATIONS_IDL_
+#define _SELF_CONF_IRP_NOTIFICATIONS_IDL_
+
+#include <SelfConfIRPConstDefs.idl>
+#include <SwMIRPConstDefs.idl>
+#include <NotificationIRPNotifications.idl>
+#include <SwMIRPNotifications.idl>
+
+// This statement must appear after all include statements
+#pragma prefix "3gppsa5.org"
+
+/** Module: SelfConfIRPNotifications
+This contains the specification of notifications of Software Management.
+=====
+*/
+module SelfConfIRPNotifications
+{
+
+ /* Constant definitions for the notifyScManagementProfileCreation notification */
+
+ interface NotifyScManagementProfileCreation: SwMIRPNotifications::NotifySwMProfileCreation
+ {
+ const string EVENT_TYPE = "notifyScManagementProfileCreation";
+
+ };
+
+ /* Constant definitions for the notifyScManagementProfileDeletion notification */
+
+ interface NotifyScManagementProfileDeletion: SwMIRPNotifications::NotifySwMProfileDeletion
+ {
+ const string EVENT_TYPE = "notifyScManagementProfileDeletion";
+
+ };
+
+ /* Constant definitions for the notifyScProcessCreation notification */
+
+ interface NotifyScProcessCreation: SwMIRPNotifications::NotifySwMProcessCreation
+ {
+ const string EVENT_TYPE = "notifyScProcessCreation";
+
+ };
+
+ /* Constant definitions for the notifyScProcessStage notification */
+
+ interface NotifyScProcessStage: SwMIRPNotifications::NotifySwMProcessStage
+ {
+ const string EVENT_TYPE = "notifyScProcessStage";
+
+ };
+
+ /* Constant definitions for the notifyScProcessDeletion notification */
+
+ interface NotifyScProcessDeletion: SwMIRPNotifications::NotifyScProcessDeletion
+ {
+ const string EVENT_TYPE = "notifyScProcessDeletion";
+
+ };
+
+ /* Constant definitions for the notifyNewScManagementCapabilityAvailability notification */
+
+ interface NotifyNewScManagementCapabiliyAvailability: NotificationIRPNotifications::Notify
+ {
+ const string EVENT_TYPE = "notifyNewScManagementCapabilityAvailability";
+
+ /**
+ * This constant defines the name of the id property,
+ * which is transported in the filterable_body_fields.
+ */
+ };
+}
+
+```
+
+```
+ * The data type for the value of this property is
+ * SwMIRPConstDefs::Id.
+ */
+ const string ID =
+ SelfConfIRPConstDefs::AttributeNameValue::ID;
+
+ /**
+ * This constant defines the name of the nEInformation property,
+ * which is transported in the filterable_body_fields.
+ * The data type for the value of this property is
+ * SwMIRPConstDefs::NEInformation.
+ */
+ const string ID =
+ SelfConfIRPConstDefs::AttributeNameValue::NE_INFORMATION;
+
+ /**
+ * This constant defines the name of the stepsAndOfferedStopPointList property,
+ * which is transported in the remaining_body.
+ * The data type for the value of this property is
+ * SwMIRPConstDefs::StepsAndOfferedStopPointList.
+ */
+ const string ID =
+ SelfConfIRPConstDefs::AttributeNameValue::STEPS_AND_OFFERED_STOP_POINT_LIST;
+
+ /**
+ * This constant defines the name of the offeredFinalAdministrativeStateInformation property,
+ * which is transported in the remaining_body.
+ * The data type for the value of this property is
+ * SwMIRPConstDefs::OfferedFinalAdministrativeStateInformation.
+ */
+ const string ID =
+ SelfConfIRPConstDefs::AttributeNameValue::OFFERED_FINAL_ADMINISTRATIVE_STATE_INFORMATION;
+
+ /**
+ * This constant defines the name of the swVersionToBeInstalledOfferList property,
+ * which is transported in the remaining_body.
+ * The data type for the value of this property is
+ * SwMIRPConstDefs::SwVersionToBeInstalledOfferListOpt.
+ */
+ const string ID =
+ SelfConfIRPConstDefs::AttributeNameValue::SW_VERSION_TO_BE_INSTALLED_OFFER_LIST;
+
+};
+
+ /* Constant definitions for the notifyScManagementProfileChange notification */
+ interface NotifyScManagementProfileChange: SwMIRPNotifications::NotifySwMProfileChange
+ {
+ const string EVENT_TYPE = "notifyScManagementProfileChange";
+
+ };
+
+};
+
+#endif // _SELF_CONF_IRP_NOTIFICATIONS_IDL_
+```
+
+# --- Annex B (normative): XML definitions
+
+This annex contains the XML Definitions for the SC Management IRP for the IRP whose semantics is specified in Trace Management IRP: Information Service (3GPP TS 32.502 [4]).
+
+This XML Definitions specification defines the XML syntax of the SC Management IRP XML Data File.
+
+## --- B.1 Architectural Features
+
+The overall architectural feature of SC Management IRP is specified in 3G TS 32.502 [4]. This clause specifies features that are specific to the XML definitions.
+
+### B.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [24].
+
+### B.1.2 Notification Services
+
+This annex defines the XML syntax of SC Management IRP notifications that is to be used for the SC Management IRP SOAP Solution Set and in conjunction with Notification Log IRP XML Definitions for Notification Log IRP XML Data File and the NL IRP XML Notification Format.
+
+### B.1.3 IOC Definitions
+
+This annex defines the XML syntax for the IOC definitions of the SC Management IRP IS [4], which are used by the XML definitions for the SC Management IRP notifications and the SC Management IRP IS operations.
+
+## --- B.2 Mapping
+
+Not present in the current version of this specification.
+
+## --- B.3 Solution Set definitions
+
+### B.3.1 XML definition structure
+
+Clause B.3.2 provides a graphical representation of the XML elements.
+
+Clause B.3.3 provides XML definitions of SC Management IRP notifications as defined in [4]. These definitions are to be used for the Trace Management IRP SOAP Solution Set.
+
+Clause B.3.4 provides XML definitions of SC Management IOC as defined in [4].
+
+### B.3.2 Graphical Representation
+
+
+
+The diagram illustrates the graphical representation of three XML message structures:
+
+- NotifyScManagementProfileCreate:** This message structure starts with the root element `NotifyScManagementProfileCreate`, which contains a `xsc:body` element. The `xsc:body` element contains a list of six child elements: `xsc:id`, `xsc:versionNumber`, `xsc:nInformation`, `xsc:swVersionToBeInstalled`, `xsc:stepsAndSelectedStopPoint...`, and `xsc:selectedFinalAdministrative...`.
+- notifyScManagementProfileChan:** This message structure starts with the root element `notifyScManagementProfileChan`, which contains a `xsc:body` element. The `xsc:body` element contains a list of six child elements: `xsc:id`, `xsc:versionNumber`, `xsc:nInformation`, `xsc:swVersionToBeInstalled`, `xsc:stepsAndSelectedStopPoint...`, and `xsc:selectedFinalAdministrative...`.
+- NotifyScManagementProfileDelet:** This message structure starts with the root element `NotifyScManagementProfileDelet`, which contains a `xsc:body` element. The `xsc:body` element contains a single child element: `xsc:id`.
+
+Three XML tree diagrams showing the structure of NotifyScManagementProfileCreate, notifyScManagementProfileChan, and NotifyScManagementProfileDelet messages.
+
+
+
+The diagrams illustrate the structure of various notification messages in the 3GPP TS 32.506 specification. Each diagram shows a message name, a 'body' element, and its constituent fields.
+
+- NotifyScProcessCreation**: Contains a **xsc:body** element with the following fields:
+ - xsc:id**
+ - xsc:nEIdentification**
+ - xsc:profileId**
+ - xsc:matchingNEInformation**
+ - xsc:stepInfoList**
+- NotifyScProcessDeletion**: Contains a **xsc:body** element with the following fields:
+ - xsc:id**
+ - xsc:triggerForDeletion**
+ - xsc:additionalInformation** (optional)
+- NotifyScProcessStage**: Contains a **xsc:body** element with the following fields:
+ - xsc:id**
+ - xsc:stepInfoList**
+- notifyNewScManagementCapabil...**: Contains a **xsc:body** element with the following fields:
+ - xsc:id**
+ - xsc:nEInformation**
+ - xsc:stepsAndOfferedStopPoint...**
+ - xsc:offeredFinalAdministrativeS...**
+ - xsc:swVersionToBeInstalledOff...**
+- OfferedFinalAdministrativeStateL...**: Contains a **xsc:OfferedFinalAdministrativeS...** element.
+- ProfileId**: Contains the following fields:
+ - xsc:id**
+ - xsc:versionNumber**
+- StepsAndOfferedStopPointListE...**: Contains the following fields:
+ - xsc:nameOfStep**
+ - xsc:sequenceNumberInProcess**
+ - xsc:stopPointCanBeSetBeforeT...**
+
+A series of six diagrams showing the structure of various notification messages. Each diagram shows a message name, a 'body' element, and its constituent fields. The fields are listed vertically and include identifiers like xsc:id, xsc:nEIdentification, xsc:profileId, xsc:matchingNEInformation, xsc:stepInfoList, xsc:triggerForDeletion, xsc:additionalInformation, xsc:nEInformation, xsc:stepsAndOfferedStopPoint..., xsc:offeredFinalAdministrativeS..., xsc:swVersionToBeInstalledOff..., xsc:versionNumber, xsc:nameOfStep, xsc:sequenceNumberInProcess, and xsc:stopPointCanBeSetBeforeT...
+
+
+
+ASN.1 diagram for **StepsAndOfferedStopPointList**. The list contains **xsc:stepsAndOfferedStopPoint...** entries (1..∞). Each entry is defined in a box labeled **xsc:StepsAndOfferedStopPointEntry** and contains the following fields:
+
+- xsc:nameOfStep
+- xsc:sequenceNumberInProcess
+- xsc:stopPointCanBeSetBeforeT...
+
+ASN.1 diagram for StepsAndOfferedStopPointList. It shows a list containing xsc:stepsAndOfferedStopPoint... entries (1..∞). Each entry is defined in a box labeled xsc:StepsAndOfferedStopPointEntry and contains fields: xsc:nameOfStep, xsc:sequenceNumberInProcess, and xsc:stopPointCanBeSetBeforeT...
+
+
+
+ASN.1 diagram for **StepsAndSelectedStopPointList...**. The list contains entries with the following fields:
+
+- xsc:nameOfStep
+- xsc:sequenceNumberInProcess
+- xsc:stopPointSetIndication
+
+ASN.1 diagram for StepsAndSelectedStopPointList... showing a list containing entries with fields: xsc:nameOfStep, xsc:sequenceNumberInProcess, and xsc:stopPointSetIndication.
+
+
+
+ASN.1 diagram for **StepsAndSelectedStopPointList**. The list contains **xsc:stepsAndSelectedStopPoint...** entries (1..∞). Each entry is defined in a box labeled **xsc:StepsAndSelectedStopPointEntry** and contains the following fields:
+
+- xsc:nameOfStep
+- xsc:sequenceNumberInProcess
+- xsc:stopPointSetIndication
+
+ASN.1 diagram for StepsAndSelectedStopPointList. It shows a list containing xsc:stepsAndSelectedStopPoint... entries (1..∞). Each entry is defined in a box labeled xsc:StepsAndSelectedStopPointEntry and contains fields: xsc:nameOfStep, xsc:sequenceNumberInProcess, and xsc:stopPointSetIndication.
+
+
+
+ASN.1 diagram for **StepInfoListEntry**. The entry contains the following fields:
+
+- xsc:nameOfStep
+- xsc:sequenceNumberInProcess
+- xsc:stopPointSetIndication
+- xsc:stepProgress
+
+ASN.1 diagram for StepInfoListEntry showing a single entry with fields: xsc:nameOfStep, xsc:sequenceNumberInProcess, xsc:stopPointSetIndication, and xsc:stepProgress.
+
+
+
+ASN.1 diagram for **StepInfoList**. The list contains **xsc:stepInfoListEntry** entries (1..∞). Each entry is defined in a box labeled **xsc:StepInfoListEntry** and contains the following fields:
+
+- xsc:nameOfStep
+- xsc:sequenceNumberInProcess
+- xsc:stopPointSetIndication
+- xsc:stepProgress
+
+ASN.1 diagram for StepInfoList. It shows a list containing xsc:stepInfoListEntry entries (1..∞). Each entry is defined in a box labeled xsc:StepInfoListEntry and contains fields: xsc:nameOfStep, xsc:sequenceNumberInProcess, xsc:stopPointSetIndication, and xsc:stepProgress.
+
+
+
+This diagram shows the structure of **scManagementCapabilityIOC**. It contains the following elements:
+
+- xsc:id**
+- xsc:nameInformation**
+- xsc:stepsAndOfferedStopPoint...**: A list element that points to **xsc:StepsAndOfferedStopPointList**. Inside this list, there is an entry **xsc:stepsAndOfferedStopPoint...** (multiplicity 1..∞) which contains:
+ - xsc:nameOfStep**
+ - xsc:sequenceNumberInProcess**
+ - xsc:stopPointCanBeSetBeforeT...**
+- xsc:offeredFinalAdministrativeS...**: A list element that points to **xsc:OfferedFinalAdministrativeStateInformation**, which contains the element **xsc:OfferedFinalAdministrativeS...**
+
+XSD diagram for scManagementCapabilityIOC. It includes elements xsc:id, xsc:nameInformation, xsc:stepsAndOfferedStopPoint... (linked to xsc:StepsAndOfferedStopPointList), and xsc:offeredFinalAdministrativeS... (linked to xsc:OfferedFinalAdministrativeStateInformation).
+
+
+
+This diagram shows the structure of **scManagementProfileIOC**. It contains the following elements:
+
+- xsc:id**
+- xsc:versionNumber**
+- xsc:nameInformation**
+- xsc:stepsAndSelectedStopPoint...**: A list element that points to **xsc:StepsAndSelectedStopPointList**. Inside this list, there is an entry **xsc:stepsAndSelectedStopPoint...** (multiplicity 1..∞) which contains:
+ - xsc:nameOfStep**
+ - xsc:sequenceNumberInProcess**
+ - xsc:stopPointSetIndication**
+- xsc:selectedFinalAdministrative...**: A list element that points to **xsc:SelectedFinalAdministrativeStateInformation**, which contains the element **xsc:SelectedFinalAdministrativeS...**
+
+XSD diagram for scManagementProfileIOC. It includes elements xsc:id, xsc:versionNumber, xsc:nameInformation, xsc:stepsAndSelectedStopPoint... (linked to xsc:StepsAndSelectedStopPointList), and xsc:selectedFinalAdministrative... (linked to xsc:SelectedFinalAdministrativeStateInformation).
+
+
+
+This diagram shows the structure of **scProcessIOC**. It contains the following elements:
+
+- xsc:id**
+- xsc:nameIdentification**
+- xsc:profileId**: An element that points to **xsc:ProfileId**, which contains:
+ - xsc:id**
+ - xsc:versionNumber**
+- xsc:stepInfoList**: A list element that points to **xsc:StepInfoList**. Inside this list, there is an entry **xsc:stepInfoListEntry** (multiplicity 1..∞) which contains:
+ - xsc:nameOfStep**
+ - xsc:sequenceNumberInProcess**
+ - xsc:stopPointSetIndication**
+ - xsc:stepProgress**
+
+XSD diagram for scProcessIOC. It includes elements xsc:id, xsc:nameIdentification, xsc:profileId (linked to xsc:ProfileId), and xsc:stepInfoList (linked to xsc:StepInfoList).
+
+### B.3.3 XML Schema “scIRPNotif.xsd”
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ 3GPP TS 32.506 SCIRP Notification XML Schema
+ sCIRPNotif.xsd
+-->
+<schema targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scnIRPNotif"
+ xmlns:xsc="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scnIRPNotif"
+ xmlns:swm="http://www.3gpp.org/ftp/specs/archive/32_series/32.536#swManagementIRPNotif"
+ xmlns:xe="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#notification"
+ xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
+ attributeFormDefault="unqualified">
+ <import namespace="xe:Notification" schemaLocation="notification.xsd"/>
+ <complexType name="NotifyScManagementProfileCreation">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ <element name="versionNumber" type="swm:VersionNumber"/>
+ <element name="nEInformation" type="swm:NEInformation"/>
+ <element name="swVersionToBeInstalled"
+type="swm:SwVersionToBeInstalledConditional"/>
+ <element name="stepsAndSelectedStopPointList"
+type="swm:StepsAndSelectedStopPointList"/>
+ <element name="selectedFinalAdministrativeState"
+type="swm:FinalAdministrativeStateValue"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+ </complexType>
+ <complexType name="NotifyScManagementProfileDeletion">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+ </complexType>
+ <complexType name="NotifyScProcessCreation">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ <element name="nEIdentification" type="swm:Id"/>
+ <element name="profileId" type="swm:ProfileId"/>
+ <element name="matchingNEInformation" type="swm:NEInformation"/>
+ <element name="stepInfoList" type="swm:StepInfoList"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+ </complexType>
+ <complexType name="NotifyScProcessStage">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+
+```
+
+```
+
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ <element name="stepInfoList" type="swm:StepInfoList"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+</complexContent>
+</complexType>
+<complexType name="NotifyScProcessDeletion">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ <element name="triggerForDeletion" type="swm:TriggerForDeletion"/>
+ <element name="additionalInformation" type="string" minOccurs="0"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+</complexType>
+<complexType name="notifyNewScManagementCapabilityAvailability">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ <element name="nEInformation" type="swm:NEInformation"/>
+ <element name="stepsAndOfferedStopPointList"
+type="swm:StepsAndOfferedStopPointList"/>
+ <element name="offeredFinalAdministrativeStateInformation"
+type="swm:OfferedFinalAdministrativeStateInformation"/>
+ <element name="swVersionToBeInstalledOfferList"
+type="swm:swVersionToBeInstalledOfferList"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+</complexType>
+<complexType name="notifyScManagementProfileChange">
+ <complexContent>
+ <extension base="xe:Notification">
+ <sequence>
+ <element name="body">
+ <complexType>
+ <sequence>
+ <element name="id" type="swm:Id"/>
+ <element name="versionNumber" type="swm:VersionNumber"/>
+ <element name="nEInformation" type="swm:NEInformation"/>
+ <element name="swVersionToBeInstalled"
+type="swm:SwVersionToBeInstalledConditional"/>
+ <element name="stepsAndSelectedStopPointList"
+type="swm:StepsAndSelectedStopPointList"/>
+ <element name="selectedFinalAdministrativeState"
+type="swm:FinalAdministrativeStateValue"/>
+ </sequence>
+ </complexType>
+ </element>
+ </sequence>
+ </extension>
+ </complexContent>
+</complexType>
+<element name="notifyScManagementProfileCreation" type="swm:NotifyScManagementProfileCreation"/>
+<element name="notifyScManagementProfileDeletion" type="swm:NotifyScManagementProfileDeletion"/>
+<element name="notifyScManagementProcessCreation" type="swm:NotifyScManagementProcessCreation"/>
+<element name="notifyScProcessStage" type="swm:NotifyScProcessStage"/>
+<element name="notifyScManagementProcessDeletion" type="swm:NotifyScManagementProcessDeletion"/>
+
+```
+
+```
+<element name="notifyNewScManagementCapabilityAvailability"
+type="swm:notifyNewScManagementCapabilityAvailability"/>
+<element name="notifyScManagementProfileChange" type="swm:NotifyScManagementProfileChange"/>
+</schema>
+```
+
+### B.3.4 XML Schema “scIRPIOCs.xsd”
+
+```
+
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+3GPP TS 32.506 Self Configuration IRP IOC XML Schema
+scIRPIOCs.xsd
+-->
+<schema xmlns="http://www.w3.org/2001/XMLSchema"
+ xmlns:xsc="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scIRPIOCs"
+ xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.536#swManagementIRPIOCs"
+ xmlns:ns1="http://www.3gpp.org/ftp/specs/archive/32_series/32.536#swManagementIRPIOCs "
+ targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scIRPIOCs"
+ elementFormDefault="qualified" attributeFormDefault="unqualified">
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.536#swManagementIRPIOCs "
+ schemaLocation=" swManagementIRPIOCs.xsd"/>
+ <simpleType name="id">
+ <restriction/>
+ </simpleType>
+ <simpleType name="neInformation">
+ <restriction/>
+ </simpleType>
+ <simpleType name="VersionNumber">
+ <restriction base="unsignedShort"/>
+ </simpleType>
+ <complexType name="ProfileId">
+ <sequence>
+ <element name="id" type="xsc:Id"/>
+ <element name="versionNumber" type="xsc:VersionNumber"/>
+ </sequence>
+ </complexType>
+ <simpleType name="FinalAdministrativeStateValue">
+ <restriction base="string">
+ <enumeration value="LOCKED"/>
+ <enumeration value="UNLOCKED"/>
+ <enumeration value="DETERMINED_BY_CONFIGURATION_DATA"/>
+ </restriction>
+ </simpleType>
+ <complexType name="OfferedFinalAdministrativeStateInformation">
+ <sequence>
+ <element name="OfferedFinalAdministrativeStateValue"
+ type="xsc:FinalAdministrativeStateValue"/>
+ </sequence>
+ </complexType>
+ <complexType name="StepsAndOfferedStopPointListEntry">
+ <sequence>
+ <element name="nameOfStep" type="xsc:NameOfStep"/>
+ <element name="sequenceNumberInProcess" type="xsc:SequenceNumberInProcess"/>
+ <element name="stopPointCanBeSetBeforeThisStep"
+ type="xsc:StopPointCanBeSetBeforeThisStep"/>
+ </sequence>
+ </complexType>
+ <complexType name="StepsAndOfferedStopPointList">
+ <sequence>
+ <element name="stepsAndOfferedStopPointListEntry"
+ type="xsc:StepsAndOfferedStopPointListEntry" maxOccurs="unbounded"/>
+ </sequence>
+ </complexType>
+ <simpleType name="StopPointCanBeSetBeforeThisStep">
+ <restriction base="boolean"/>
+ </simpleType>
+ <complexType name="StepsAndSelectedStopPointListEntry">
+ <sequence>
+ <element name="nameOfStep" type="xsc:NameOfStep"/>
+ <element name="sequenceNumberInProcess" type="xsc:SequenceNumberInProcess"/>
+ <element name="stopPointSetIndication" type="xsc:StopPointSetIndication"/>
+ </sequence>
+ </complexType>
+ <complexType name="StepsAndSelectedStopPointList">
+ <sequence>
+ <element name="stepsAndSelectedStopPointListEntry"
+ type="xsc:StepsAndSelectedStopPointListEntry" maxOccurs="unbounded"/>
+ </sequence>
+ </complexType>
+ <simpleType name="StopPointSetIndication">
+ <restriction base="string">
+ <enumeration value="STOP_POINT_IS_SET_BEFORE_THIS_STEP"/>
+ </restriction>
+ </simpleType>
+</schema>
+
+```
+
+```
+<enumeration value="STOP_POINT_IS_NOT_SET"/>
+</restriction>
+</simpleType>
+<simpleType name="SequenceNumberInProcess">
+ <restriction base="unsignedShort"/>
+</simpleType>
+<simpleType name="NameOfStep">
+ <restriction base="string">
+ <enumeration value="SW_DOWNLOAD"/>
+ <enumeration value="SW_INSTALLATION"/>
+ <enumeration value="SW_ACTIVATION"/>
+ <enumeration value="PREPARE_BASIC_CONFIGURATION_AND_OAMLINK"/>
+ <enumeration value="RETRIEVE_CONFIGURATION_DATA"/>
+ <enumeration value="SETUP_PRECONFIGURED_SIGNALLING_LINKS"/>
+ <enumeration value="SET_FINAL_STATE_OF_NE "/>
+ </restriction>
+</simpleType>
+<simpleType name="StepProgress">
+ <restriction base="string">
+ <enumeration value="NOT_YET_STARTED"/>
+ <enumeration value="RUNNING"/>
+ <enumeration value="COMPLETED"/>
+ <enumeration value="AWAITING_RESUME"/>
+ <enumeration value="FAILURE"/>
+ <enumeration value="TERMINATED"/>
+ </restriction>
+</simpleType>
+<complexType name="StepInfoListEntry">
+ <sequence>
+ <element name="nameOfStep" type="xsc:NameOfStep"/>
+ <element name="sequenceNumberInProcess" type="xsc:SequenceNumberInProcess"/>
+ <element name="stopPointSetIndication" type="xsc:StopPointSetIndication"/>
+ <element name="stepProgress" type="xsc:StepProgress"/>
+ </sequence>
+</complexType>
+<complexType name="StepInfoList">
+ <sequence>
+ <element name="stepInfoListEntry" type="xsc:StepInfoListEntry" maxOccurs="unbounded"/>
+ </sequence>
+</complexType>
+<complexType name="scManagementCapabilityIOC">
+ <sequence>
+ <element name="id" type="xsc:Id"/>
+ <element name="neInformation" type="xsc:NEInformation"/>
+ <element name="stepsAndOfferedStopPointList" type="xsc:StepsAndOfferedStopPointList"/>
+ <element name="offeredFinalAdministrativeStateInformation"
+type="xsc:OfferedFinalAdministrativeStateInformation"/>
+ </sequence>
+</complexType>
+<complexType name="scManagementProfileIOC">
+ <sequence>
+ <element name="id" type="xsc:Id"/>
+ <element name="versionNumber" type="xsc:VersionNumber"/>
+ <element name="neInformation" type="xsc:NEInformation"/>
+ <element name="stepsAndSelectedStopPointList" type="xsc:StepsAndSelectedStopPointList"/>
+ <element name="selectedFinalAdministrativeState"
+type="xsc:FinalAdministrativeStateValue"/>
+ </sequence>
+</complexType>
+<complexType name="scProcessIOC">
+ <sequence>
+ <element name="id" type="xsc:Id"/>
+ <element name="neIdentification" type="xsc:NEInformation"/>
+ <element name="profileId" type="xsc:ProfileId"/>
+ <element name="stepInfoList" type="xsc:StepInfoList"/>
+ </sequence>
+</complexType>
+</schema>
+```
+
+# Annex C (normative): SOAP Solution Set
+
+This annex specifies the SOAP Solution Set for the IRP whose semantics are specified in Self-Configuration of Network Elements IRP: Information Service (3GPP TS 32.502 [4]).
+
+## C.1 Architectural features
+
+The overall architectural feature of the Self-Configuration of Network Elements IRP is specified in 3GPP TS 32.502 [4]. This clause specifies features that are specific to the SOAP solution set.
+
+### C.1.1 Syntax for Distinguished Names
+
+The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [24].
+
+### C.1.2 Notification Services
+
+The Self-Configuration of Network Elements IRP SOAP SS uses the Notification IRP SOAP SS of 3GPP TS 32.306[19].
+
+### C.1.3 Supported W3C specifications
+
+The SOAP 1.1 specification [20] and WSDL 1.1 specification [22] are supported.
+
+The SOAP 1.2 specification [23] is supported optionally.
+
+This specification uses "document" style in WSDL file.
+
+This specification uses "literal" encoding style in WSDL file.
+
+The filter language used in the SS is the XPath Language (see W3C XPath 1.0 specification [21]). IRPAgents may throw a FilterComplexityLimit fault when a given filter is too complex.
+
+Relevant definitions are imported from the Self-Configuration of Network Elements XML definitions of Annex B
+
+### C.1.4 Prefixes and namespaces
+
+This specification uses a number of namespace prefixes throughout that are listed in Table C.1.4.
+
+**Table C.1.4: Prefixes and Namespaces used in this specification**
+
+| PREFIX | NAMESPACE |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| (no prefix) | <a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a> |
+| soap | <a href="http://schemas.xmlsoap.org/wsdl/soap/">http://schemas.xmlsoap.org/wsdl/soap/</a> |
+| ScIRPSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPSystem</a> |
+| ScIRPData | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPData">http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPData</a> |
+| xsc | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scIRPIOCs">http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scIRPIOCs</a> |
+| genericIRPSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSystem</a> |
+| ntfIRPNtfSystem | <a href="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem">http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem</a> |
+
+## C.2 Mapping
+
+### C.2.1 Operation and Notification mapping
+
+The Self-Configuration of Network Elements IRP IS (3GPP TS 32.502 [4]) defines the operations and their semantics.
+
+Table C.2.1 maps the operations defined in the Self-Configuration of Network Elements IRP IS to their equivalent port type and binding operations in this Solution Set (SS).
+
+Table C.2.1 also maps the notifications of the Self-Configuration of Network Elements IRP IS, as well as inherited operations.
+
+Table C.2.1 also qualifies if an operation is Mandatory (M) or Optional (O).
+
+**Table C.2.1: Mapping from IS Operation to SS Equivalents**
+
+| IS Operation in 3GPP TS 32.502 [4] | SS: Operation for WSDL port type and WSDL binding | SS: Port of SCIRPService | Qualifier |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|--------------------------|-----------|
+| listScManagementCapabilities | listScManagementCapabilities (note 1) | SCIRPOperation1 | M |
+| listScManagementProfiles | listScManagementProfiles (note 1) | SCIRPOperation1 | M |
+| createScManagementProfile | createScManagementProfile (note1) | SCIRPOperation1 | M |
+| deleteScManagementProfile | deleteScManagementProfile (note1) | SCIRPOperation1 | M |
+| listScProcesses | listScProcesses (note1) | SCIRPOperation1 | M |
+| resumeScProcess | resumeScProcess (note1) | SCIRPOperation1 | M |
+| terminateScProcess | terminateScProcess (note1) | SCIRPOperation1 | M |
+| changeScManagementProfile | changeScManagementProfile (note1) | SCIRPOperation1 | O |
+| notifyScManagementProfileCreation | notify (note 2) | NotificationIRPNtfPort | M |
+| notifyScManagementProfileDeletion | notify (note 2) | NotificationIRPNtfPort | M |
+| notifyScProcessCreation | notify (note 2) | NotificationIRPNtfPort | M |
+| notifyScProcessStage | notify (note 2) | NotificationIRPNtfPort | M |
+| notifyScProcessDeletion | notify (note 2) | NotificationIRPNtfPort | M |
+| notifyNewScManagementCapabilityAvailability | notify (note 2) | NotificationIRPNtfPort | M |
+| notifyScManagementProfileChange | notify (note 2) | NotificationIRPNtfPort | O |
+| getIRPVersion (note 3) | See TS 32.316 [17] | GenericIRPPort | M |
+| getOperationProfile (note 3) | See TS 32.316 [17] | GenericIRPPort | O |
+| getNotificationProfile (note 3) | See TS 32.316 [17] | GenericIRPPort | O |
+| NOTE 1: The operation is under the port type SCIRPSystem:SCIRPPortType and under the binding SCIRPSystem:SCIRPBinding. | | | |
+| NOTE 2: The IS equivalent maps to an XML definition specified in Annex B, and this being an input parameter to the operation notify under the port type ntfIRPNtfSystem:NotificationIRPNtf and under the binding ntfIRPNtfSystem:NotificationIRPNtf of 3GPP TS 32.306 [19]. This binding is linked to a port of the SCIRPService as indicated in the table above.. | | | |
+| NOTE 3: The IS operation is inherited from the ManagedGenericIRP IOC specified in 3GPP TS 32.312 [16]. This inheritance is by the SelfConfigurationIRP IOC of 3GPP TS 32.502 [4] inheriting from the ManagedGenericIRP IOC. The corresponding binding is linked to a port of the SCIRPService as indicated in the table above. | | | |
+
+### C.2.2 Operation parameter mapping
+
+The SCIRP IS (3GPP TS 32.502 [4]) defines semantics of parameters carried in the operations. The tables below show the mapping of these parameters, as per operation, to their equivalents defined in this SS.
+
+#### C.2.2.1 Operation listScManagementCapabilities
+
+##### C.2.2.1.1 Input parameters
+
+**Table C.2.2.1.1: Mapping from IS listScManagementCapabilities input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| nEInformation | nEInformation | M |
+
+##### C.2.2.1.2 Output parameters
+
+**Table C.2.2.1.2: Mapping from IS listScManagementCapabilities output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| capabilitiesList | capabilitiesList | M |
+| Result | Result | M |
+
+##### C.2.2.1.3 Fault definition
+
+**Table C.2.2.1.3: Mapping from IS listScManagementCapabilities exceptions to SS equivalents**
+
+| Assertion name | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| operation_failed | operation_failed | M |
+
+#### C.2.2.2 Operation listScManagementProfiles
+
+##### C.2.2.2.1 Input parameters
+
+**Table C.2.2.2.1: Mapping from IS listScManagementProfiles input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| nEInformation | nEInformation | M |
+
+##### C.2.2.2.2 Output parameters
+
+**Table C.2.2.2.2: Mapping from IS listScManagementProfiles output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| ScManagementProfileList | ScManagementProfileList | M |
+| result | result | M |
+
+#### C.2.2.3 Operation createScManagementProfile
+
+##### C.2.2.3.1 Input parameters
+
+**Table C.2.2.3.1: Mapping from IS createScManagementProfile input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| id | id | O |
+| nEInformation | nEInformation | M |
+| swVersionToBeInstalled | swVersionToBeInstalled | M |
+| stepsAndSelectedStopPointList | stepsAndSelectedStopPointList | M |
+| selectedFinalAdministrativeState | selectedFinalAdministrativeState | M |
+
+##### C.2.2.3.2 Output parameters
+
+**Table C.2.2.3.2: Mapping from IS createScManagementProfile output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| id | id | CM |
+| result | result | M |
+
+#### C.2.2.4 Operation deleteScManagementProfile
+
+##### C.2.2.4.1 Input parameters
+
+**Table C.2.2.4.1: Mapping from IS deleteScManagementProfile input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| id | id | M |
+
+##### C.2.2.4.2 Output parameters
+
+**Table C.2.2.4.2: Mapping from IS deleteScManagementProfile output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| result | result | M |
+
+#### C.2.2.5 Operation listScProcesses
+
+##### C.2.2.5.1 Input parameters
+
+**Table C.2.2.5.1: Mapping from IS listScProcesses input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| nEIdentification | nEIdentification | O |
+
+##### C.2.2.5.2 Output parameters
+
+**Table C.2.2.5.2: Mapping from IS listScProcesses output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| ScManagementprocessList | ScManagementprocessList | M |
+| result | result | M |
+
+#### C.2.2.6 Operation resumeScProcess
+
+##### C.2.2.6.1 Input parameters
+
+**Table C.2.2.6.1: Mapping from IS resumeScProcess input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| id | id | M |
+| startStepName | startStepName | M |
+
+##### C.2.2.6.2 Output parameters
+
+**Table C.2.2.6.2: Mapping from IS resumeScProcess output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| result | result | M |
+
+#### C.2.2.7 Operation terminateSctProcess
+
+##### C.2.2.7.1 Input parameters
+
+**Table C.2.2.7.1: Mapping from IS terminateSctProcess input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| id | id | M |
+
+##### C.2.2.7.2 Output parameters
+
+**Table C.2.2.7.2: Mapping from IS terminateSctProcess output parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| result | result | M |
+
+#### C.2.2.8 Operation changeScManagementProfile
+
+##### C.2.2.8.1 Input parameters
+
+**Table C.2.2.8.1: Mapping from IS changeScManagementProfile input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| id | id | M |
+| nEInformation | nEInformation | M |
+| swVersionToBeInstalled | swVersionToBeInstalled | M |
+| stepsAndSelectedStopPointList | stepsAndSelectedStopPointList | M |
+| selectedFinalAdministrativeState | selectedFinalAdministrativeState | M |
+
+##### C.2.2.8.2 Output parameters
+
+**Table C.2.2.8.2: Mapping from IS changeScManagementProfile input parameters to SS equivalents**
+
+| IS Operation parameter | SS WSDL type sub-element used in corresponding input message under corresponding port type operation as indicated in Table C.2.1 | Qualifier |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------|
+| result | result | M |
+| versionNumber | versionNumber | M |
+| conflictingProfileId | conflictingProfileId | C *) |
+
+## C.3 Solution Set definitions
+
+### C.3.1 WSDL definition structure
+
+Clause C.3.2 provides a graphical representation of the Self-Configuration of Network Elements IRP service.
+
+Clause C.3.3 defines the services which are supported the Self-Configuration of Network Elements IRP agent.
+
+### C.3.2 Graphical Representation
+
+The WSDL structure is depicted in Figure C.3.2 below, depicting port type, binding and service. The port type contains port type operations, which again contains input, output and fault messages. The binding contains binding operations, which have the same name as the port type operations. The binding connects to a port inside the service.
+
+
+
+Figure C.3.2: Self-Configuration of Network Elements IRP SOAP Solution Set WSDL structure. The diagram shows the hierarchical structure of a WSDL. At the top level, there are three main components: ScIRPOperation1, ScIRPOperation2, and ScIRPSERVICE. ScIRPOperation1 is a port type with operations: listScManagementCapabilities, listScManagementProfiles, createScManagementProfile, deleteScManagementProfile, listScProcesses, resumeScProcess, and terminateScProcess. ScIRPOperation2 is a port type with operation: ChangeScManagementProfile. ScIRPSERVICE is a service that contains two ports: GenericIRPPort and NotificationIRPNtfPort. GenericIRPPort is bound to ScIRPOperation1 and ScIRPOperation2. NotificationIRPNtfPort is bound to ScIRPOperation2. The diagram also shows the transport and document types for each operation.
+
+Figure C.3.2: Self-Configuration of Network Elements IRP SOAP Solution Set WSDL structure
+
+### C.3.3 WSDL specification “ScIRPSYSTEM.wsd1”
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ 3GPP TS 32.506 Self Configuration IRP SOAP Solution Set
+-->
+<definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
+ xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
+ xmlns:ScIRPSYSTEM="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPSYSTEM"
+ xmlns:ScIRPData="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPData"
+ xmlns:xsc="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scIRPIOCs"
+ xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"
+ xmlns:genericIRPSYSTEM="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSYSTEM"
+ xmlns:ntfIRPNtfSystem="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSyst
+em" xmlns:ns="http://www.w3.org/2001/XMLSchema"
+ xmlns:ns1="http://schemas.xmlsoap.org/soap/encoding/"
+ targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPSYSTEM">
+ <import
+ namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtfSystem"/>
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRPSYSTEM"/>
+ <types>
+ <schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRPData">
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#scIRPIOCs"/>
+ <import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm"/>
+ <!-- The following types are defined for the SC IRP operations -->
+ <simpleType name="NEInformation">
+ <restriction base="string"/>
+ </simpleType>
+ <simpleType name="Id">
+ <restriction base="xn:dn"/>
+ </simpleType>
+ </schema>
+ </types>
+</definitions>
+```
+
+```
+
+<complexType name="capability">
+ <sequence>
+ <element name="Id" type="ScIRPData:Id"/>
+ <element name="NEInformation" type="ScIRPData:NEInformation"/>
+ <element name="StepsAndOfferedStopPointList"
+type="xsc:StepsAndOfferedStopPointList"/>
+ <element name="OfferedFinalAdministrativeStateInformation"
+type="xsc:OfferedFinalAdministrativeStateInformation"/>
+ </sequence>
+</complexType>
+<complexType name="capabilitiesList">
+ <sequence>
+ <element name="capability" type="ScIRPData:capability" maxOccurs="unbounded"/>
+ </sequence>
+</complexType>
+<complexType name="ScProfile">
+ <sequence>
+ <element name="Id" type="ScIRPData:Id"/>
+ <element name="VersionNumber" type="xsc:VersionNumber"/>
+ <element name="NEInformation" type="ScIRPData:NEInformation"/>
+ <element name="StepsAndSelectedStopPointList"
+type="xsc:StepsAndSelectedStopPointList"/>
+ <element name="FinalAdministrativeStateValue"
+type="xsc:FinalAdministrativeStateValue"/>
+ <element name="swVersionToBeInstalled" type=" xsc:VersionNumber" minOccurs="0"/>
+ </sequence>
+</complexType>
+<complexType name="ScProfileList">
+ <sequence>
+ <element name="ScProfile" type=" ScIRPData:ScProfile" maxOccurs="unbounded"/>
+ </sequence>
+</complexType>
+<complexType name="ScProcess">
+ <sequence>
+ <element name="Id" type="ScIRPData:Id"/>
+ <element name="NEInformation" type="ScIRPData:NEInformation"/>
+ <element name="ProfileId" type="xsc:ProfileId"/>
+ <element name="StepInfoList" type="xsc:StepInfoList"/>
+ </sequence>
+</complexType>
+<complexType name="ScProcessList">
+ <sequence>
+ <element name="ScProcess" type="ScIRPData:ScProcess" maxOccurs="unbounded"/>
+ </sequence>
+</complexType>
+<complexType name="startStepName">
+ <sequence>
+ <element name="startStepName" type="string"/>
+ </sequence>
+</complexType>
+<!--listScManagementCapabilities Request-->
+<element name="listScManagementCapabilitiesRequest">
+ <complexType>
+ <sequence>
+ <element name="nEInformation" type="ScIRPData:NEInformation"/>
+ </sequence>
+ </complexType>
+</element>
+<!--listScManagementCapabilities Response -->
+<element name="listScManagementCapabilitiesResponse">
+ <complexType>
+ <sequence>
+ <element name="capabilitiesList" type="ScIRPData:capabilitiesList"/>
+ <element name="Result">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="success"/>
+ <enumeration value="failure"/>
+ <enumeration value="stepNameNotMatch"/>
+ <enumeration value="nEInformationIntersection"/>
+ </restriction>
+ </simpleType>
+ </element>
+ </sequence>
+ </complexType>
+</element>
+<!--listScManagementCapabilities Fault -->
+<element name="listScManagementCapabilitiesFault">
+
+```
+
+```
+
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="operationfailed"/>
+ </restriction>
+ </simpleType>
+ </element>
+ <!--listScManagementProfiles Request -->
+ <element name="listScManagementProfilesRequest">
+ <complexType>
+ <sequence>
+ <element name="nEInformation" type="ScIRPData:NEInformation"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!--listScManagementProfiles Response -->
+ <element name="listScManagementProfilesResponse">
+ <complexType>
+ <sequence>
+ <element name="ScProfileList" type="ScIRPData:ScProfileList"/>
+ <element name="Result">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="success"/>
+ <enumeration value="failure"/>
+ <enumeration value="stepNameNotMatch"/>
+ <enumeration value="nEInformationIntersection"/>
+ </restriction>
+ </simpleType>
+ </element>
+ </sequence>
+ </complexType>
+ </element>
+ <!--createScManagementProfile Request -->
+ <element name="createScManagementProfileRequest">
+ <complexType>
+ <sequence>
+ <element name="id" type="ScIRPData:Id" minOccurs="0"/>
+ <element name="nEInformation" type="ScIRPData:NEInformation"/>
+ <element name="swVersionToBeInstalled" type="xsc:VersionNumber"/>
+ <element name="stepsAndSelectedStopPointList"
+type="xsc:StepsAndSelectedStopPointList"/>
+ <element name="selectedFinalAdministrativeState"
+type="xsc:FinalAdministrativeStateValue"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!--createScManagementProfile Response -->
+ <element name="createScManagementProfileResponse">
+ <complexType>
+ <sequence>
+ <element name="id" type="ScIRPData:Id" minOccurs="0"/>
+ <element name="Result">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="Success"/>
+ <enumeration value="Failure"/>
+ <enumeration value="nEInformationIntersection"/>
+ <enumeration value="notAllowedBecauseOfOngoingSwmActivity"/>
+ </restriction>
+ </simpleType>
+ </element>
+ </sequence>
+ </complexType>
+ </element>
+ <!--deleteScManagementProfile Request -->
+ <element name="deleteScManagementProfileRequest">
+ <complexType>
+ <sequence>
+ <element name="id" type="ScIRPData:Id"/>
+ </sequence>
+ </complexType>
+ </element>
+ <!--deleteScManagementProfile Response -->
+ <element name="deleteScManagementProfileResponse">
+ <complexType>
+ <sequence>
+ <element name="Result">
+ <simpleType>
+
+```
+
+```
+<restriction base="string">
+ <enumeration value="success"/>
+ <enumeration value="failure"/>
+ <enumeration value="stepNameNotMatch"/>
+ <enumeration value="nEInformationIntersection"/>
+</restriction>
+</simpleType>
+</element>
+</sequence>
+</complexType>
+</element>
+<!--listScProcesses Request -->
+<element name="listScProcessesRequest">
+ <complexType>
+ <sequence>
+ <element name="nEIdentification" type="ScIRPData:NEInformation"
+minOccurs="0"/>
+ </sequence>
+ </complexType>
+</element>
+<!--listScProcesses Response -->
+<element name="listScProcessesResponse">
+ <complexType>
+ <sequence>
+ <element name="ScProcessList" type="ScIRPData:ScProcessList"/>
+ <element name="Result">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="success"/>
+ <enumeration value="failure"/>
+ <enumeration value="stepNameNotMatch"/>
+ <enumeration value="nEInformationIntersection"/>
+ </restriction>
+ </simpleType>
+ </element>
+ </sequence>
+ </complexType>
+</element>
+<!--resumeScProcess Request -->
+<element name="resumeScProcessRequest">
+ <complexType>
+ <sequence>
+ <element name="id" type="ScIRPData:Id"/>
+ <element name="startStepName" type="ScIRPData:startStepName"/>
+ </sequence>
+ </complexType>
+</element>
+<!--resumeScProcess Response -->
+<element name="resumeScProcessResponse">
+ <complexType>
+ <sequence>
+ <element name="Result">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="success"/>
+ <enumeration value="failure"/>
+ <enumeration value="stepNameNotMatch"/>
+ <enumeration value="nEInformationIntersection"/>
+ </restriction>
+ </simpleType>
+ </element>
+ </sequence>
+ </complexType>
+</element>
+<!--terminateScProcess Request -->
+<element name="terminateScProcessRequest">
+ <complexType>
+ <sequence>
+ <element name="id" type="ScIRPData:Id"/>
+ </sequence>
+ </complexType>
+</element>
+<!--terminateScProcess Response -->
+<element name="terminateScProcessResponse">
+ <complexType>
+ <sequence>
+ <element name="Result">
+ <simpleType>
+```
+
+```
+<restriction base="string">
+ <enumeration value="success"/>
+ <enumeration value="failure"/>
+ <enumeration value="stepNameNotMatch"/>
+ <enumeration value="nEInformationIntersection"/>
+</restriction>
+</simpleType>
+</element>
+</sequence>
+</complexType>
+</element>
+<!--ChangeScManagementProfile Request -->
+<element name="ChangeScManagementProfileRequest">
+ <complexType>
+ <sequence>
+ <element name="id" type="ScIRPData:Id"/>
+ <element name="nEInformation" type="ScIRPData:NEInformation"/>
+ <element name="swVersionToBeInstalled" type="xsc:VersionNumber"/>
+ <element name="stepsAndSelectedStopPointList"
+type="xsc:StepsAndSelectedStopPointList"/>
+ <element name="selectedFinalAdministrativeState"
+type="xsc:FinalAdministrativeStateValue"/>
+ </sequence>
+ </complexType>
+</element>
+<!--ChangeScManagementProfile Response -->
+<element name="ChangeScManagementProfileResponse">
+ <complexType>
+ <sequence>
+ <element name="Result">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="Success"/>
+ <enumeration value="Failure"/>
+ <enumeration value="nEInformationIntersection"/>
+ <enumeration value="notAllowedBecauseOfOngoingSwmActivity"/>
+ </restriction>
+ </simpleType>
+ </element>
+ <element name="versionNumber" type="xsc:VersionNumber"/>
+ <element name="conflictingProfileId" minOccurs="0">
+ <simpleType>
+ <restriction base="string">
+ <enumeration value="swMprofileId"/>
+ <enumeration value="swMprofileAId"/>
+ <enumeration value="swMprofileBId"/>
+ <enumeration value="empty"/>
+ </restriction>
+ </simpleType>
+ </element>
+ </sequence>
+ </complexType>
+</element>
+</schema>
+</types>
+<message name="listScManagementCapabilitiesRequest">
+ <part name="parameter" element="ScIRPData:listScManagementCapabilitiesRequest"/>
+</message>
+<message name="listScManagementCapabilitiesResponse">
+ <part name="parameter" element="ScIRPData:listScManagementCapabilitiesResponse"/>
+</message>
+<message name="listScManagementCapabilitiesFault">
+ <part name="parameter" element="ScIRPData:listScManagementCapabilitiesFault"/>
+</message>
+<message name="listScManagementProfilesRequest">
+ <part name="parameter" element="ScIRPData:listScManagementProfilesRequest"/>
+</message>
+<message name="listScManagementProfilesResponse">
+ <part name="parameter" element="ScIRPData:listScManagementProfilesResponse"/>
+</message>
+<message name="createScManagementProfileRequest">
+ <part name="parameter" element="ScIRPData:createScManagementProfileRequest"/>
+</message>
+<message name="createScManagementProfileResponse">
+ <part name="parameter" element="ScIRPData:createScManagementProfileResponse"/>
+</message>
+<message name="deleteScManagementProfileRequest">
+ <part name="parameter" element="ScIRPData:deleteScManagementProfileRequest"/>
+```
+
+```
+
+</message>
+<message name="deleteScManagementProfileResponse">
+ <part name="parameter" element="ScIRPData:deleteScManagementProfileResponse"/>
+</message>
+<message name="listScProcessesRequest">
+ <part name="parameter" element="ScIRPData:listScProcessesRequest"/>
+</message>
+<message name="listScProcessesResponse">
+ <part name="parameter" element="ScIRPData:listScProcessesResponse"/>
+</message>
+<message name="resumeScProcessRequest">
+ <part name="parameter" element="ScIRPData:resumeScProcessRequest"/>
+</message>
+<message name="resumeScProcessResponse">
+ <part name="parameter" element="ScIRPData:resumeScProcessResponse"/>
+</message>
+<message name="terminateScProcessRequest">
+ <part name="parameter" element="ScIRPData:terminateScProcessRequest"/>
+</message>
+<message name="terminateScProcessResponse">
+ <part name="parameter" element="ScIRPData:terminateScProcessResponse"/>
+</message>
+<message name="ChangeScManagementProfileRequest">
+ <part name="parameter" element="ScIRPData:ChangeScManagementProfileRequest"/>
+</message>
+<message name="ChangeScManagementProfileResponse">
+ <part name="parameter" element="ScIRPData:ChangeScManagementProfileResponse"/>
+</message>
+<portType name="ScIRPOperation1">
+ <operation name="listScManagementCapabilities">
+ <input message="ScIRPSystem:listScManagementCapabilitiesRequest"/>
+ <output message="ScIRPSystem:listScManagementCapabilitiesResponse"/>
+ <fault name="listScManagementCapabilitiesFault"
+message="ScIRPSystem:listScManagementCapabilitiesFault"/>
+ </operation>
+ <operation name="listScManagementProfiles">
+ <input message="ScIRPSystem:listScManagementProfilesRequest"/>
+ <output message="ScIRPSystem:listScManagementProfilesResponse"/>
+ </operation>
+ <operation name="createScManagementProfile">
+ <input message="ScIRPSystem:createScManagementProfileRequest"/>
+ <output message="ScIRPSystem:createScManagementProfileResponse"/>
+ </operation>
+ <operation name="deleteScManagementProfile">
+ <input message="ScIRPSystem:deleteScManagementProfileRequest"/>
+ <output message="ScIRPSystem:deleteScManagementProfileResponse"/>
+ </operation>
+ <operation name="listScProcesses">
+ <input message="ScIRPSystem:listScProcessesRequest"/>
+ <output message="ScIRPSystem:listScProcessesResponse"/>
+ </operation>
+ <operation name="resumeScProcess">
+ <input message="ScIRPSystem:resumeScProcessRequest"/>
+ <output message="ScIRPSystem:resumeScProcessResponse"/>
+ </operation>
+ <operation name="terminateScProcess">
+ <input message="ScIRPSystem:terminateScProcessRequest"/>
+ <output message="ScIRPSystem:terminateScProcessResponse"/>
+ </operation>
+</portType>
+<portType name="ScIRPOperation2">
+ <operation name="ChangeScManagementProfile">
+ <input message="ScIRPSystem:ChangeScManagementProfileRequest"/>
+ <output message="ScIRPSystem:ChangeScManagementProfileResponse"/>
+ </operation>
+</portType>
+<binding name="ScIRPOperation1" type="ScIRPSystem:ScIRPOperation1">
+ <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+ <operation name="listScManagementCapabilities">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#listScManagementCapabilities"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+ </operation>
+
+```
+
+```
+<fault name="listScManagementCapabilitiesFault"/>
+</operation>
+<operation name="listScManagementProfiles">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#listScManagementProfiles"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+</operation>
+<operation name="createScManagementProfile">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#createScManagementProfile"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+</operation>
+<operation name="deleteScManagementProfile">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#deleteScManagementProfile"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+</operation>
+<operation name="listScProcesses">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#listScProcesses"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+</operation>
+<operation name="resumeScProcess">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#resumeScProcess"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+</operation>
+<operation name="terminateScProcess">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#terminateScProcess"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+ <output>
+ <soap:body use="literal"/>
+ </output>
+</operation>
+</binding>
+<binding name="ScIRPOperation2" type="ScIRPSystem:ScIRPOperation2">
+ <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
+ <operation name="ChangeScManagementProfile">
+ <soap:operation
+soapAction="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ChangeScManagementProfile"
+style="document"/>
+ <input>
+ <soap:body use="literal"/>
+ </input>
+```
+
+```
+<output>
+ <soap:body use="literal"/>
+</output>
+</operation>
+</binding>
+<service name="ScIRPService">
+ <port name="ScIRPOperation1" binding="ScIRPSystem:ScIRPOperation1">
+ <soap:address location="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRP"/>
+ </port>
+ <port name="GenericIRP" binding="genericIRPSystem:GenericIRPBinding">
+ <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.316#GenericIRP"/>
+ </port>
+ <port name="NotificationIRPNtfPort" binding="ntfIRPNtfSystem:NotificationIRPNtf">
+ <soap:address
+location="http://www.3gpp.org/ftp/specs/archive/32_series/32.306#NotificationIRPNtf"/>
+ </port>
+ <port name="ScIRPOperation2" binding="ScIRPSystem:ScIRPOperation2">
+ <soap:address location="http://www.3gpp.org/ftp/specs/archive/32_series/32.506#ScIRP"/>
+ </port>
+</service>
+</definitions>
+```
+
+# Annex D (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------|--|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2010-09 | SA#49 | SP-100509 | -- | -- | | Presentation to SA for Information and Approval | | 1.0.0 |
+| 2010-10 | -- | -- | -- | -- | | Publication | | 10.0.0 |
+| 2012-09 | SA#57 | - | - | - | | Automatic upgrade from previous Release version 10.0.0 | | 11.0.0 |
+| 2014-09 | SA#65 | SP-140559 | 001 | - | | Update the link from Solution Set to Information Service due to the end of Release 12 | | 12.0.0 |
+| 2016-01 | - | - | - | - | | Update to Rel-13 version (MCC) | | 13.0.0 |
+| 2016-06 | SA#72 | SP-16407 | 0002 | - | F | Update the link from IRP Solution Set to IRP Information Service | | 13.1.0 |
+| 2017-04 | SA#75 | - | - | - | | Promotion to Release 14 without technical change | | 14.0.0 |
+| 2017-06 | SA#76 | SP-170502 | 0003 | - | F | Update the link from IRP Solution Set to IRP Information Service | | 14.1.0 |
+| 2018-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | | <b>15.0.0</b> |
+| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | | <b>16.0.0</b> |
+| 2022-04 | - | - | - | - | - | Update to Rel-17 version (MCC) | | <b>17.0.0</b> |
+| 2024-04 | - | - | - | - | - | Update to Rel-18 version (MCC) | | <b>18.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-18/32_series/32591/18722c46c9e8475524e634dedd08bac2_img.jpg b/marked/Rel-18/32_series/32591/18722c46c9e8475524e634dedd08bac2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16b4603941f8b667b3985c41498e96b1fefeff03
--- /dev/null
+++ b/marked/Rel-18/32_series/32591/18722c46c9e8475524e634dedd08bac2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a94aee17b0444d63fd3db0af1a5e10cf6d1464a51f56c93d687585628d8e2bf
+size 15562
diff --git a/marked/Rel-18/32_series/32591/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-18/32_series/32591/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9f82548da86a77b5655c831dd8749e98ac147c3
--- /dev/null
+++ b/marked/Rel-18/32_series/32591/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02fc5ff014c2862bfb24b475fc61103a739b592ebf0500e42c1b4a1fc7a004ea
+size 21191
diff --git a/marked/Rel-18/38_series/38412/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38412/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac0918ec81139fd28b157b6a94c21aaa9609d717
--- /dev/null
+++ b/marked/Rel-18/38_series/38412/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa3e310ae07f8c6b6cc797408d842ecf0dd18213ae13a952727d76379a0abeae
+size 9575
diff --git a/marked/Rel-18/38_series/38412/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38412/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a92cdbfa36eca4d43ac5582b86151cc6d528d1d
--- /dev/null
+++ b/marked/Rel-18/38_series/38412/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3047f1ebcd71d05983326694ec594ca2a412446b7f60c1c29b9ac22531d23fa8
+size 6263
diff --git a/marked/Rel-18/38_series/38412/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg b/marked/Rel-18/38_series/38412/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..60a8a78f24016a4455964cb939faee317f99d7bc
--- /dev/null
+++ b/marked/Rel-18/38_series/38412/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8cc5d5c08ee7c501a1d4c69efd5e2b984b3fd944c96c32facb7134ac82f5967b
+size 19495
diff --git a/marked/Rel-18/38_series/38412/raw.md b/marked/Rel-18/38_series/38412/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..187689d7917731929de76e487f1dacccd35d8616
--- /dev/null
+++ b/marked/Rel-18/38_series/38412/raw.md
@@ -0,0 +1,197 @@
+
+
+# 3GPP TS 38.412 V18.1.0(2024-06)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG signalling transport (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|----------------------------------------------------|----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 6 |
+| 4 NG signalling bearer ..... | 6 |
+| 4.1 Functions and protocol stack..... | 6 |
+| 5 Data link layer ..... | 7 |
+| 6 IP layer ..... | 7 |
+| 7 Transport layer ..... | 7 |
+| <b>Annex A (informative): Change history .....</b> | <b>9</b> |
+
+# --- 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
+
+The present document specifies the standards for signalling transport to be used across NG interface. NG interface is a logical interface between the NG-RAN and the 5GC. The present document describes how the NGAP signalling messages are transported over NG.
+
+# --- 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] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [3] 3GPP TS 23.501: "System Architecture for the 5G System".
+- [4] 3GPP TS 23.502: "Procedures for the 5G System".
+- [5] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification".
+- [6] IETF RFC 791 (1981-09): "Internet Protocol".
+- [7] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [8] IETF RFC 6083 (2011-01): "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)".
+- [9] IETF RFC 6335 (2011-08): "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry".
+- [10] IANA: "Stream Control Transmission Protocol (SCTP) Parameters", [<https://www.iana.org/assignments/sctp-parameters/sctp-parameters.xhtml#sctp-parameters-25>].
+- [11] IANA: "Service Name and Transport Protocol Port Number Registry", [<https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml>].
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**NG:** interface between a NG-RAN node and a 5GC, providing an interconnection point between the NG-RAN and the 5GC.
+
+**NG-C:** Reference point for the control plane protocol between NG-RAN and AMF.
+
+**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [5]
+
+**SCTP association:** as defined in IETF RFC 4960 (2007-09) [5]
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|----------|-----------------------------------------|
+| 5GC | 5G Core Network |
+| IP | Internet Protocol |
+| SCTP | Stream Control Transmission Protocol |
+| DiffServ | Differentiated Service |
+| PPP | Point to Point Protocol |
+| IANA | Internet Assigned Number Authority |
+| AMF | Access and Mobility management Function |
+
+# 4 NG signalling bearer
+
+## 4.1 Functions and protocol stack
+
+NG-C signalling bearer provides the following functions:
+
+- Provision of reliable transfer of NGAP message over NG-C interface.
+- Provision of networking and routeing function.
+- Provision of redundancy in the signalling network.
+- Support for flow control and congestion control.
+
+The protocol stack for NG-C Signalling Bearer is shown in figure 4.1-1 and details on each protocol are described in the following clauses.
+
+
+
+Diagram of the NG-C signalling bearer protocol stack. The stack consists of five layers. At the top is the NGAP layer. Below it is a horizontal line with an oval in the center, representing the NG-C interface. Below the interface are four layers: SCTP, IP, Data link layer, and Physical layer. To the left of the stack, the 'Radio Network Layer' label is positioned next to the NGAP layer, and the 'Transport Network Layer' label is positioned next to the SCTP and IP layers.
+
+**Figure 4.1-1: NG-C signalling bearer protocol stack**
+
+The Transport Network Layer is based on IP transport, comprising SCTP on top of IP.
+
+# 5 Data link layer
+
+The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.
+
+# 6 IP layer
+
+The 5GC and NG-RAN shall support IPv6 (IETF RFC 8200 [5]) and/or IPv4 (IETF RFC 791 [6]).
+
+The IP layer of NG-C only supports point-to-point transmission for delivering NG AP message.
+
+The 5GC and NG-RAN shall support the Diffserv Code Point marking as described in IETF RFC 2474 [7].
+
+# 7 Transport layer
+
+SCTP (IETF RFC 4960 [2]) shall be supported as the transport layer of NG-C signalling bearer. The Payload Protocol Identifier (ppid) to be used by SCTP for the application layer protocol NGAP and for DTLS over SCTP (IETF RFC 6083 [8]) is assigned by IANA in [10]. The byte order of the ppid shall be big-endian.
+
+SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network.
+
+NG-RAN node and AMF shall support a configuration with a single SCTP association per NG-RAN node/AMF pair. Configurations with multiple SCTP endpoints per NG-RAN node/AMF pair should be supported. When configurations with multiple SCTP associations are supported, the AMF may request to dynamically add/remove SCTP associations between the NG-RAN node/AMF pair. Within the set of SCTP associations established between one AMF and NG-RAN node pair, the AMF may request the NG-RAN node to restrict the usage of SCTP association for certain types of NG-C signalling. If no restriction information is provided for an SCTP association, any type of NG-C signalling is allowed via the SCTP association. Selection of the SCTP association by the NG-RAN node and the AMF is specified in TS 23.501 [3] and TS 23.502 [4]. The NG-RAN node shall establish the SCTP association. The SCTP Destination Port number value to be used by NGAP is assigned by IANA in [11]. When the AMF requests to dynamically add additional SCTP associations between the NG-RAN node/AMF pair, the SCTP Destination Port number value may be the one assigned by IANA in [11], or any dynamic port value (IETF RFC 6335 [9]). When the configuration with multiple SCTP endpoints per NG-RAN node is supported and the NG-RAN node wants to add additional SCTP endpoints, the RAN configuration update procedure shall be the first NGAP procedure triggered on an additional TNLA of an already setup NG-C interface instance after the TNL association has become operational, and the AMF shall associate the TNLA to the NG-C interface instance using the included Global RAN node ID.
+
+Between one AMF and NG-RAN node pair:
+
+- A single pair of stream identifiers shall be reserved over at least one SCTP association for the sole use of NGAP elementary procedures that utilize non UE-associated signalling.
+- At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of NGAP elementary procedures that utilize UE-associated signallings. However, a few pairs (i.e. more than one) should be reserved.
+- For a single UE-associated signalling, the NG-RAN node shall use one SCTP association and one SCTP stream, and the SCTP association/stream should not be changed during the communication of the UE-associated signalling until after current SCTP association is failed or removed, or TNL binding update is performed as described in TS 23.502 [3].
+
+Transport network redundancy can be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy, an SCTP endpoint (in the NG-RAN node or AMF) may send an INIT, at any time for an already established SCTP association, which the other SCTP endpoint shall handle as defined in IETF RFC 4960 [2] in subclause 5.2.
+
+The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages.
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38415/3a33f3d9710df2b4c805247cd69facc3_img.jpg b/marked/Rel-18/38_series/38415/3a33f3d9710df2b4c805247cd69facc3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..115a9e15ca276e7db1caa7e5f05163ff712ee04a
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/3a33f3d9710df2b4c805247cd69facc3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff570c7c57496be010f50fa42633e1c5a03a7e9f0c0827e1542bc70d0e08abda
+size 15444
diff --git a/marked/Rel-18/38_series/38415/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg b/marked/Rel-18/38_series/38415/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14bacc13865d273b2bfc3d4b903d357b876cde94
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b3a92eedecf0d5f7726be0b0fc43025dc4393369d736535394519720b88ac91
+size 17406
diff --git a/marked/Rel-18/38_series/38415/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38415/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..167ad6dc4870f29b7a9d0f99f478fd7e952aa566
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1adcb07084c9a81a9403e65de330448e05e00bbeccb4666a78f5d25c4e3f94d
+size 9637
diff --git a/marked/Rel-18/38_series/38415/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38415/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a10f769b9ea3bca9468b9a1211bfbbf1b1614af3
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5a9959338e8483259bbd54b75a5dcce8396e878f4425435e64934d0730340f3
+size 7232
diff --git a/marked/Rel-18/38_series/38415/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/Rel-18/38_series/38415/65550960f5c5afd9d27706aaeddb0638_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f57a072c9e4343e791bb525fd3b4ce03a2b5e3b
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/65550960f5c5afd9d27706aaeddb0638_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3122e716b51f66a6e153733efe6ab1d15f642f6c09b3d0553cb9cf68c09a2ddd
+size 9999
diff --git a/marked/Rel-18/38_series/38415/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/38_series/38415/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a134075581e9d6bc72fe49a1aa421760512cd8d7
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ebab307dc470b18bd712be55f3ad833e9b831b469b0ca6e85570e259f3869619
+size 61973
diff --git a/marked/Rel-18/38_series/38415/f4535959316aea381fb56b9225d8e4bd_img.jpg b/marked/Rel-18/38_series/38415/f4535959316aea381fb56b9225d8e4bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92c946abc8c46df8a23d02c4b5a219c9bd5242bc
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/f4535959316aea381fb56b9225d8e4bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51ab6b03e3ae764a166af60ea0addaf70f3b22aa243777f588d3240a1129d1eb
+size 14531
diff --git a/marked/Rel-18/38_series/38415/raw.md b/marked/Rel-18/38_series/38415/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..82bfaa43e192a1a130d94192977cbb63ff6d23d5
--- /dev/null
+++ b/marked/Rel-18/38_series/38415/raw.md
@@ -0,0 +1,886 @@
+
+
+# 3GPP TS 38.415 V18.0.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; PDU Session User Plane Protocol (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|----------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 General..... | 7 |
+| 4.1 General aspects..... | 7 |
+| 5 PDU Session user plane protocol..... | 7 |
+| 5.1 General ..... | 7 |
+| 5.2 PDU Session user plane protocol layer services..... | 7 |
+| 5.3 Services expected from the Transport Network Layer..... | 8 |
+| 5.4 Elementary procedures..... | 8 |
+| 5.4.1 Transfer of DL PDU Session Information..... | 8 |
+| 5.4.1.1 Successful operation ..... | 8 |
+| 5.4.1.2 Unsuccessful operation..... | 9 |
+| 5.4.2 Transfer of UL PDU Session Information..... | 9 |
+| 5.4.2.1 Successful operation ..... | 9 |
+| 5.4.2.2 Unsuccessful operation ..... | 9 |
+| 5.5 Elements for the PDU Session user plane protocol..... | 9 |
+| 5.5.1 General ..... | 9 |
+| 5.5.2 Frame format for the PDU Session user plane protocol..... | 10 |
+| 5.5.2.1 DL PDU SESSION INFORMATION (PDU Type 0)..... | 10 |
+| 5.5.2.2 UL PDU SESSION INFORMATION (PDU Type 1)..... | 11 |
+| 5.5.3 Coding of information elements in frames ..... | 12 |
+| 5.5.3.1 PDU Type ..... | 12 |
+| 5.5.3.2 Spare ..... | 12 |
+| 5.5.3.3 QoS Flow Identifier (QFI) ..... | 12 |
+| 5.5.3.4 Reflective QoS Indicator (RQI)..... | 12 |
+| 5.5.3.5 Padding ..... | 13 |
+| 5.5.3.6 Paging Policy Presence (PPP)..... | 13 |
+| 5.5.3.7 Paging Policy Indicator (PPI) ..... | 13 |
+| 5.5.3.8 QoS Monitoring Packet (QMP) ..... | 13 |
+| 5.5.3.9 DL Sending Time Stamp ..... | 13 |
+| 5.5.3.10 DL Sending Time Stamp Repeated ..... | 13 |
+| 5.5.3.11 DL Received Time Stamp..... | 14 |
+| 5.5.3.12 UL Sending Time Stamp ..... | 14 |
+| 5.5.3.13 DL Delay Ind. .... | 14 |
+| 5.5.3.14 DL Delay Result ..... | 14 |
+| 5.5.3.15 UL Delay Ind. .... | 14 |
+| 5.5.3.16 UL Delay Result ..... | 14 |
+| 5.5.3.17 Sequence Number Presence (SNP)..... | 15 |
+| 5.5.3.18 DL QFI Sequence Number ..... | 15 |
+| 5.5.3.19 UL QFI Sequence Number ..... | 15 |
+| 5.5.3.20 N3/N9 Delay Ind..... | 15 |
+| 5.5.3.21 N3/N9 Delay Result..... | 15 |
+| 5.5.3.22 D1 UL PDCP Delay Result Ind ..... | 15 |
+| 5.5.3.23 MBS Sequence Number Presence (MSNP)..... | 15 |
+| 5.5.3.24 DL MBS QFI Sequence Number..... | 16 |
+| 5.5.3.25 DL Congestion Information..... | 16 |
+| 5.5.3.26 UL Congestion Information..... | 16 |
+| 5.5.4 Timers..... | 16 |
+| 5.6 Handling of unknown, unforeseen and erroneous protocol data..... | 16 |
+
+| | | |
+|-------------------------------|-------------------------------------------------------------------|-----------|
+| 6 | PDU Set Information user plane protocol..... | 16 |
+| 6.1 | General ..... | 16 |
+| 6.2 | PDU Set Information user plane protocol layer services ..... | 16 |
+| 6.3 | Services expected from the Transport Network Layer..... | 17 |
+| 6.4 | Elementary procedures..... | 17 |
+| 6.4.1 | Transfer of DL PDU Set Information..... | 17 |
+| 6.4.1.1 | Successful operation ..... | 17 |
+| 6.4.1.2 | Unsuccessful operation..... | 17 |
+| 6.5 | Elements for the PDU Set Information user plane protocol..... | 18 |
+| 6.5.1 | General ..... | 18 |
+| 6.5.2 | Frame format for the PDU Set Information user plane protocol..... | 18 |
+| 6.5.2.1 | DL PDU SET INFORMATION (PDU Type 0) ..... | 18 |
+| 6.5.3 | Coding of information elements in frames ..... | 18 |
+| 6.5.3.1 | PDU Type ..... | 18 |
+| 6.5.3.2 | Spare ..... | 18 |
+| 6.5.3.3 | QoS Flow Identifier (QFI) ..... | 19 |
+| 6.5.3.5 | PSSI (PDU Set Size indicator)..... | 19 |
+| 6.5.3.6 | EDBI (End Data Burst indicator)..... | 19 |
+| 6.5.3.7 | End PDU of the PDU Set (EPDU)..... | 19 |
+| 6.5.3.8 | End of Data Burst (EDB)..... | 19 |
+| 6.5.3.9 | PDU Set Importance (PSI)..... | 19 |
+| 6.5.3.10 | PDU Set Sequence Number (PSSN)..... | 19 |
+| 6.5.3.11 | PDU Sequence Number within a PDU Set (PSN)..... | 20 |
+| 6.5.3.12 | PDU Set Size (PSSize) ..... | 20 |
+| 6.5.4 | Timers..... | 20 |
+| 6.6 | Handling of unknown, unforeseen and erroneous protocol data..... | 20 |
+| <b>Annex A (informative):</b> | <b>Example of using Future Extension Field .....</b> | <b>21</b> |
+| A.1 | Example of using Future Extension field..... | 21 |
+| A.1.1 | New IE Flags ..... | 21 |
+| <b>Annex B (informative):</b> | <b>Change history .....</b> | <b>22</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document specifies the PDU Session user plane protocol being used over the NG-U, Xn-U and N9 interfaces. Applicability to other interfaces is not precluded.
+
+This present document also specifies the PDU Set Information user plane protocol being used over the NG-U, Xn-U, F1-U and N9 interfaces. Applicability to other interfaces is not precluded.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+ - For a specific reference, subsequent revisions do not apply.
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.300: "NextGen Radio Access Network (NG-RAN); Overall description; Stage 2".
+- [3] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
+- [4] 3GPP TS 37.324: "E-UTRA and NR; Service Data Application Protocol (SDAP) specification".
+- [5] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [6] IETF RFC 5905 (2010-06): "Network Time Protocol Version 4: Protocol and Algorithms Specification".
+- [7] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
+- [8] 3GPP TS 38.470: "NG-RAN; F1 general aspects and principles".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Multicast Broadcast User Plane Function:** as defined in TS 23.501 [5].
+
+**NG-U:** as defined in TS 38.300 [2].
+
+**Xn-U:** logical interface between NG-RAN nodes as defined in TS 38.300 [2].
+
+**Data Burst:** as defined in TS 23.501 [5].
+
+**PDU Set:** as defined in TS 23.501 [5].
+
+**F1-U:** logical interface between gNB-CU and gNB-DU as defined in TS 38.470 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|--------|-----------------------------------------|
+| MBS | Multicast Broadcast Service |
+| MB-UPF | Multicast Broadcast User Plane Function |
+| PDCP | Packet Data Convergence Protocol |
+| PPI | Paging Policy Indicator |
+| PPP | Paging Policy Presence |
+| QFI | QoS Flow Identifier |
+| RQA | Reflective QoS Attribute |
+| RQI | Reflective QoS Indication |
+| SN | Sequence Number |
+| UP | User Plane |
+| UPF | User Plane Function |
+| EPDU | End PDU of the PDU Set |
+| EDB | End of Data Burst |
+| PSI | PDU Set Importance |
+| PSSN | PDU Set Sequence Number |
+| PSN | PDU Sequence Number within a PDU Set |
+| PSSize | PDU Set Size |
+
+# --- 4 General
+
+## 4.1 General aspects
+
+The PDU Session User Plane protocol and PDU Set Information User Plane protocol are located in the User Plane of the Radio Network Layer above the Transport Network Layer of the interface.
+
+Each PDU session User Plane protocol instance and PDU Set Information User Plane protocol instance are associated to one PDU Session.
+
+In this version of the present document, the PDU session user plane protocol data is conveyed by GTP-U protocol means, more specifically, by means of the "PDU Session Container" GTP-U Extension Header as defined in TS 29.281 [3].
+
+In this version of the present document, the PDU set information user plane protocol data is conveyed by GTP-U protocol means, more specifically, by means of the "GTP-U Container" GTP-U Extension Header as defined in TS 29.281 [3].
+
+# --- 5 PDU Session user plane protocol
+
+## 5.1 General
+
+The PDU session UP layer uses the services of the Transport Network Layer in order to send its packets over the interface.
+
+## 5.2 PDU Session user plane protocol layer services
+
+The following functions are provided by the PDU Session User Plane protocol:
+
+- Provision of control information elements (e.g. QFI, RQI) associated with a PDU session.
+
+## 5.3 Services expected from the Transport Network Layer
+
+The PDU session UP layer expects the following services from the Transport Network Layer:
+
+- Transfer of PDU session User Plane PDUs.
+
+## 5.4 Elementary procedures
+
+### 5.4.1 Transfer of DL PDU Session Information
+
+#### 5.4.1.1 Successful operation
+
+The purpose of the Transfer of DL PDU Session Information procedure is to send control information elements related to the PDU Session from UPF to NG-RAN.
+
+In the case of uplink and downlink data forwarding the DL PDU Session Information procedure shall also be used to send control information elements related to the PDU Session from NG-RAN node to UPF, or from UPF to NG-RAN node, or between NG-RAN nodes.
+
+A PDU Session user plane instance making use of the Transfer of DL PDU Session Information procedure is associated to a single PDU Session. The Transfer of DL PDU Session Information procedure may be invoked whenever packets for that particular PDU Session need to be transferred across the related interface instance.
+
+The DL PDU SESSION INFORMATION frame includes a QoS Flow Identifier (QFI) field associated with the transferred packet. The NG-RAN shall use the received QFI to determine the QoS flow and QoS profile which are associated with the received packet.
+
+The DL PDU SESSION INFORMATION frame shall include the Reflective QoS Indicator (RQI) field to indicate whether user plane Reflective QoS shall be activated or not. The NG-RAN shall, if RQA has been configured for the involved QoS flow as specified in TS 38.413 [7], take the RQI into account as specified in TS 37.324 [4].
+
+The DL PDU SESSION INFORMATION frame may also include a Paging Policy Indicator (PPI) field associated with the transferred packet. The NG-RAN shall use the received PPI to determine the paging policy differentiation which is associated with the received packet as described in TS 23.501 [5].
+
+The DL PDU SESSION INFORMATION frame may also include a QoS Monitoring Packet (QMP) field and a DL sending time stamp field. The NG-RAN shall, if QoS monitoring has been configured for the included QFI field, perform delay measurement and QoS monitoring, as specified in TS 23.501 [5].
+
+The DL PDU SESSION INFORMATION frame may also include a DL QFI Sequence Number field associated with the transferred packet. The NG-RAN shall, if the QoS flow has been configured eligible for redundant transport bearer in TS 38.413 [6], use the received DL QFI Sequence Number field to determine and eliminate duplicated packets for a given QoS flow as specified in TS 23.501 [5].
+
+The DL PDU SESSION INFORMATION frame may also include a DL MBS QFI Sequence Number field associated with the transferred packet. The NG-RAN shall use the received DL MBS QFI Sequence Number field to determine the PDCP count that should be used when transferring the packet over the radio as specified in TS 38.300 [2].
+
+When needed, the NG-RAN shall propagate the DL PDU Session Information to a peer NG-RAN.
+
+
+
+The diagram illustrates the successful transfer of DL PDU Session Information. It features two vertical lifelines: 'NG-RAN/UPF' on the left and 'UPF/NG-RAN' on the right. A horizontal arrow points from the 'UPF/NG-RAN' lifeline to the 'NG-RAN/UPF' lifeline, labeled 'DL PDU SESSION INFORMATION'.
+
+Sequence diagram showing the successful transfer of DL PDU Session Information from UPF to NG-RAN.
+
+Figure 5.4.1.1-1: Successful Transfer of DL PDU Session Information
+
+#### 5.4.1.2 Unsuccessful operation
+
+Void.
+
+### 5.4.2 Transfer of UL PDU Session Information
+
+#### 5.4.2.1 Successful operation
+
+The purpose of the Transfer of UL PDU Session Information procedure is to send control information elements related to the PDU Session from NG-RAN to UPF.
+
+An UL PDU Session user plane instance making use of the Transfer of UL PDU Session Information procedure is associated to a single PDU Session. The Transfer of UL PDU Session Information procedure may be invoked whenever packets for that particular PDU Session need to be transferred across the related interface instance.
+
+The UL PDU SESSION INFORMATION frame includes a QoS Flow Identifier (QFI) field associated with the transferred packet.
+
+If QoS monitoring has been requested for the included QFI field, the UL PDU SESSION INFORMATION frame may include a QoS Monitoring Packet (QMP) field, a DL Sending Time Stamp Repeated field, a DL Receiving Time Stamp field, a UL Sending Time Stamp field, and/or Delay Result for UL or DL. If QoS monitoring with N3/N9 delay reporting has been requested for the included QFI field, the I-UPF may include in the UL PDU SESSION INFORMATION frame a N3/N9 Delay Ind. field, a N3/N9 Delay Result field and delay result for UL and DL if received from the RAN. The UPF shall, if supported, use this information to calculate UL, DL, or RTT delay as specified in TS 23.501 [5].
+
+The UL PDU SESSION INFORMATION frame may also include a UL QFI Sequence Number field associated with the transferred packet. The UPF shall, if the QoS flow has been configured eligible for redundant transport bearer in TS 38.413 [6], use the received UL QFI Sequence Number field to determine and eliminate duplicated packets for a given QoS flow as specified in TS 23.501 [5].
+
+If the ECN Marking or Congestion Information Reporting Status is active for a QoS flow indicated by the QFI field, the UL PDU SESSION INFORMATION frame should include a UL Congestion Information field and/or a DL Congestion Information field. The UPF shall, if supported, use this information to perform ECN marking at UPF or information exposure as specified in TS 23.501 [5].
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN
+ participant UPF
+ Note left of NG-RAN:
+ NG-RAN->>UPF: UL PDU SESSION INFORMATION
+ Note right of UPF:
+ Note left of NG-RAN:
+ Note right of UPF:
+```
+
+The diagram illustrates a sequence of events between two entities: NG-RAN and UPF. Both are represented by rectangular boxes with a horizontal line at their base. A single horizontal arrow points from the NG-RAN box to the UPF box, labeled 'UL PDU SESSION INFORMATION'. This represents the transfer of information from the NG-RAN to the UPF.
+
+Sequence diagram showing the successful transfer of UL PDU Session Information from NG-RAN to UPF.
+
+**Figure 5.4.2.1-1: Successful Transfer of UL PDU Session Information**
+
+#### 5.4.2.2 Unsuccessful operation
+
+Void.
+
+## 5.5 Elements for the PDU Session user plane protocol
+
+### 5.5.1 General
+
+In the present document the structure of frames are specified by using figures similar to figure 5.5.1-1.
+
+
+
+| Bits | | | | | | | | Number of Octets | |
+|------------------|---|---|---|--------------|---|---------|---|------------------|---------|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | |
+| Field 1 | | | | Field 2 | | | | 1 | Octet 1 |
+| Field 3 | | | | | | Field 4 | | 2 | Octet 2 |
+| Field 4 continue | | | | Spare | | | | | Octet 3 |
+| Field 6 | | | | | | | | 2 | Octet 4 |
+| Field 6 continue | | | | Padding bits | | | | | Octet 5 |
+| Future Extension | | | | | | | | 0-m | |
+| Padding | | | | | | | | 0-3 | |
+
+**Figure 5.5.1-1: Example frame format**
+
+Unless otherwise indicated, fields which consist of multiple bits within an octet have the most significant bit located at the higher bit position (indicated above frame in figure 5.5.1-1). In addition, if a field spans several octets, most significant bits are located in lower numbered octets (right of frame in figure 5.5.1-1).
+
+On the NG interface, the frame is transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according to decreasing bit position (bit position 7 first).
+
+Spare bits should be set to "0" by the sender and should not be checked by the receiver.
+
+The header part of the frame is always an integer number of octets. The payload part is octet aligned (by adding 'Padding Bits' when needed).
+
+The receiver should be able to remove an additional Future Extension field that may be present. See description of Future Extension field in A.1.
+
+Padding octets may be added at the end of the frame, see Padding in 5.5.3.5.
+
+### 5.5.2 Frame format for the PDU Session user plane protocol
+
+#### 5.5.2.1 DL PDU SESSION INFORMATION (PDU Type 0)
+
+This frame format is defined to allow the NG-RAN to receive some control information elements which are associated with the transfer of a packet over the interface.
+
+The following shows the respective DL PDU SESSION INFORMATION frame.
+
+| Bits | | | | | | | | Number of Octets | | | | | |
+|----------------------------|-----|---------------------|-------|-----|-----|------|-------|------------------|--|--|--|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | |
+| PDU Type (=0) | | | | QMP | SNP | MSNP | Spare | 1 | | | | | |
+| PPP | RQI | QoS Flow Identifier | | | | | | 1 | | | | | |
+| PPI | | | Spare | | | | | 0 or 1 | | | | | |
+| DL Sending Time Stamp | | | | | | | | 0 or 8 | | | | | |
+| DL QFI Sequence Number | | | | | | | | 0 or 3 | | | | | |
+| DL MBS QFI Sequence Number | | | | | | | | 0 or 4 | | | | | |
+| Padding | | | | | | | | 0-3 | | | | | |
+
+Figure 5.5.2.1-1: DL PDU SESSION INFORMATION (PDU Type 0) Format
+
+#### 5.5.2.2 UL PDU SESSION INFORMATION (PDU Type 1)
+
+This frame format is defined to allow the UPF to receive some control information elements which are associated with the transfer of a packet over the interface.
+
+The following shows the respective UL PDU SESSION INFORMATION frame.
+
+| Bits | | | | | | | | Number of Octets | | | | | | |
+|--------------------------------|---------------|---------------------|---------------|---------------|---------------|---------------|---------------|------------------------------|--|--|--|--|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | |
+| PDU Type (=1) | | | | QMP | DL Delay Ind. | UL Delay Ind. | SNP | 1 | | | | | | |
+| N3/N9 Delay Ind. | New IE Flag | QoS Flow Identifier | | | | | | 1 | | | | | | |
+| DL Sending Time Stamp Repeated | | | | | | | | 0 or 8 | | | | | | |
+| DL Received Time Stamp | | | | | | | | 0 or 8 | | | | | | |
+| UL Sending Time Stamp | | | | | | | | 0 or 8 | | | | | | |
+| DL Delay Result | | | | | | | | 0 or 4 | | | | | | |
+| UL Delay Result | | | | | | | | 0 or 4 | | | | | | |
+| UL QFI Sequence Number | | | | | | | | 0 or 3 | | | | | | |
+| N3/N9 Delay Result | | | | | | | | 0 or 4 | | | | | | |
+| New IE flag 7(E) | New IE Flag 6 | New IE Flag 5 | New IE Flag 4 | New IE Flag 3 | New IE Flag 2 | New IE Flag 1 | New IE Flag 0 | 0 or 1<br>New IE Flags Octet | | | | | | |
+
+| | | |
+|---------------------------|-----------------------------------------|--------|
+| Spare | D1 UL<br>PDCP<br>Delay<br>Result<br>Ind | 0 or 1 |
+| UL Congestion Information | | 0 or 2 |
+| DL Congestion Information | | 0 or 2 |
+| Padding | | 0-3 |
+
+**Figure 5.5.2.2-1: UL PDU SESSION INFORMATION (PDU Type 1) Format**
+
+The New IE Flag in bit 6 of 2<sup>nd</sup> octet in UL PDU SESSION INFORMATION (PDU Type 1) indicates if the first octet of New IE Flags Octet is present or not.
+
+Bit 0 of New IE Flags Octet in UL PDU SESSION INFORMATION (PDU Type 1) indicates if the D1 UL PDCP Delay Result Ind is present (1) or not (0)
+
+Bit 1 of New IE Flags Octet in UL PDU SESSION INFORMATION (PDU Type 1) indicates if the UL Congestion Information is present (1) or not (0)
+
+Bit 2 of New IE Flags Octet in UL PDU SESSION INFORMATION (PDU Type 1) indicates if the DL Congestion Information is present (1) or not (0)
+
+### 5.5.3 Coding of information elements in frames
+
+#### 5.5.3.1 PDU Type
+
+**Description:** The PDU Type indicates the structure of the PDU session UP frame. The field takes the value of the PDU Type it identifies; i.e. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame.
+
+**Value range:** {0= DL PDU SESSION INFORMATION, 1=UL PDU SESSION INFORMATION, 2-15=reserved for future PDU type extensions}.
+
+**Field length:** 4 bits.
+
+#### 5.5.3.2 Spare
+
+**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver. This field is reserved for later versions.
+
+**Value range:** (0-2<sup>n</sup>-1).
+
+**Field Length:** n bits.
+
+#### 5.5.3.3 QoS Flow Identifier (QFI)
+
+**Description:** When present this parameter indicates the QoS Flow Identifier of the QoS flow to which the transferred packet belongs.
+
+**Value range:** {0..2<sup>6</sup>-1}.
+
+**Field length:** 6 bits.
+
+#### 5.5.3.4 Reflective QoS Indicator (RQI)
+
+**Description:** This parameter indicates activation of the reflective QoS towards the UE for the transferred packet as described in clause 5.4.1.1. It is used only in the downlink direction. If RQA (Reflective QoS Activation) has not been configured for the involved QoS flow, the RQI shall be ignored by the NG-RAN node.
+
+**Value range:** {0= Reflective QoS activation not triggered, 1= Reflective QoS activation triggered}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.5 Padding
+
+**Description:** The padding is included at the end of the frame to ensure that the PDU Session user plane protocol PDU length (including padding and the future extension) is $(n*4-2)$ octets, where $n$ is a positive integer. If there is any future extension, the padding should be added after the future extensions.
+
+**Field Length:** 0–3 octets.
+
+#### 5.5.3.6 Paging Policy Presence (PPP)
+
+**Description:** This parameter indicates the presence of the Paging Policy Indicator (PPI).
+
+**Value range:** {0= Paging Policy Indicator not present, 1= Paging Policy Indicator present}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.7 Paging Policy Indicator (PPI)
+
+**Description:** When present, the Paging Policy Indicator is used for paging policy differentiation (see details in 3GPP TS 23.501 [5]). This field applies to PDU sessions of IP type.
+
+**Value range:** {0..2<sup>3</sup>-1}.
+
+**Field length:** 3 bits.
+
+#### 5.5.3.8 QoS Monitoring Packet (QMP)
+
+**Description:** This parameter indicates that the transferred packet is used for QoS monitoring as described in clause 5.4.1.1 and clause 5.4.2.1. This parameter also indicates the presence of the DL Sending Time Stamp in the DL PDU Session Information frame and the presence of the DL Sending Time Stamp Repeated, the DL Receiving Time Stamp, the UL Sending Time Stamp in the UL PDU Session Information frame. If QoS monitoring has not been configured for the involved QoS flow, the QMP shall be ignored by the NG-RAN node.
+
+**Value range:** {0= not used for QoS monitoring, 1= used for QoS monitoring}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.9 DL Sending Time Stamp
+
+**Description:** This field indicates the time when the UPF sends the DL PDU Session Information frame with the QMP field set to 1. It is used only in the downlink direction and encoded in the same format as the 64-bit timestamp format as defined in Section 6 of IETF RFC 5905 [6].
+
+**Value range:** {0..2<sup>64</sup>-1}.
+
+**Field length:** 8 octets.
+
+#### 5.5.3.10 DL Sending Time Stamp Repeated
+
+**Description:** This field indicates the value of the DL Sending Time Stamp field that the NG-RAN has received in the DL PDU Session Information frame with the QMP field set to 1 for the involved QoS flow. It is used only in the uplink direction and encoded in the same format as the 64-bit timestamp format as defined in Section 6 of IETF RFC 5905 [6]. The UPF shall, if supported, use this information to calculate DL or RTT delay between the NG-RAN and the UPF as specified in TS 23.501 [5].
+
+**Value range:** {0..2<sup>64</sup>-1}.
+
+**Field length:** 8 octets.
+
+#### 5.5.3.11 DL Received Time Stamp
+
+**Description:** This field indicates the time when the NG-RAN node receives the DL PDU Session Information frame with the QMP field set to 1 for the involved QoS flow. It is used only in the uplink direction and encoded in the same format as the 64-bit timestamp format as defined in Section 6 of IETF RFC 5905 [6]. The UPF shall, if supported, use this information to calculate DL or RTT delay between the NG-RAN and the UPF as specified in TS 23.501 [5].
+
+**Value range:** $\{0..2^{64}-1\}$ .
+
+**Field length:** 8 octets.
+
+#### 5.5.3.12 UL Sending Time Stamp
+
+**Description:** This field indicates the time when the NG-RAN node sends this UL PDU Session Information frame. It is used only in the uplink direction and encoded in the same format as the 64-bit timestamp format as defined in Section 6 of IETF RFC 5905 [6]. The UPF shall, if supported, use this information to calculate UL or RTT delay between the NG-RAN and the UPF as specified in TS 23.501 [5].
+
+**Value range:** $\{0..2^{64}-1\}$ .
+
+**Field length:** 8 octets.
+
+#### 5.5.3.13 DL Delay Ind.
+
+**Description:** This parameter indicates the presence of DL Delay Result.
+
+**Value range:** $\{0= \text{DL Delay Result not present}, 1= \text{DL Delay Result present}\}$ .
+
+**Field length:** 1 bit.
+
+#### 5.5.3.14 DL Delay Result
+
+**Description:** This field indicates the downlink delay measurement result which is the sum of the delay incurred in NG-RAN (including the delay at gNB-CU-UP, on F1-U and on gNB-DU) and the delay over Uu interface in milliseconds for the involved QoS flow. It is used only in the uplink direction and encoded as an Unsigned32 binary integer value. The UPF shall, if supported, use this information to calculate DL or RTT delay as specified in TS 23.501 [5].
+
+**Value range:** $\{0..2^{32}-1\}$ .
+
+**Field length:** 4 octets.
+
+#### 5.5.3.15 UL Delay Ind.
+
+**Description:** This parameter indicates the presence of UL Delay Result.
+
+**Value range:** $\{0= \text{UL Delay Result not present}, 1= \text{UL Delay Result present}\}$ .
+
+**Field length:** 1 bit.
+
+#### 5.5.3.16 UL Delay Result
+
+**Description:** This field indicates the uplink delay measurement result which is the sum of the delay incurred in NG-RAN (including the delay at gNB-CU-UP, on F1-U and on gNB-DU), the delay over Uu interface and the delay in the UE in milliseconds for the involved QoS flow. It is used only in the uplink direction and encoded as an Unsigned32 binary integer value. The UPF shall, if supported, use this information to calculate UL or RTT delay as specified in TS 23.501 [5].
+
+**Value range:** $\{0..2^{32}-1\}$ .
+
+**Field length:** 4 octets.
+
+#### 5.5.3.17 Sequence Number Presence (SNP)
+
+**Description:** This parameter indicates the presence of the DL QFI Sequence Number in the DL PDU Session Information frame or the presence of the UL QFI Sequence Number in the UL PDU Session Information frame.
+
+**Value range:** {0= DL/UL QFI Sequence Number not present, 1= DL/UL QFI Sequence Number present}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.18 DL QFI Sequence Number
+
+**Description:** This parameter indicates the sequence number as assigned by the UPF associated with a given QoS Flow.
+
+**Value range:** {0..2<sup>24</sup>-1}.
+
+**Field length:** 3 octets.
+
+#### 5.5.3.19 UL QFI Sequence Number
+
+**Description:** This parameter indicates the sequence number as assigned by the NG-RAN node associated with a given QoS flow.
+
+**Value range:** {0..2<sup>24</sup>-1}.
+
+**Field length:** 3 octets.
+
+#### 5.5.3.20 N3/N9 Delay Ind.
+
+**Description:** This parameter indicates the presence of N3/N9 Delay Result.
+
+**Value range:** {0= N3/N9 Delay Result not present, 1= N3/N9 Delay Result present}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.21 N3/N9 Delay Result
+
+**Description:** This field indicates the accumulated N3 and N9 packet delay as specified in [5], and is reported by the I-UPF. The reported value is expressed in milliseconds and encoded as an Unsigned32 binary integer value.
+
+**Value range:** {0..2<sup>32</sup>-1}.
+
+**Field length:** 4 octets.
+
+#### 5.5.3.22 D1 UL PDCP Delay Result Ind
+
+**Description:** This parameter indicates if the UL Delay Result includes or not includes the D1 measurement (UL PDCP Packet Average Delay). This parameter shall be ignored if the UL Delay Ind is set to “0”.
+
+**Value range:** {0= D1 UL PDCP Packet Average Delay measurement is not included, 1= D1 UL PDCP Packet Average Delay measurement is included}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.23 MBS Sequence Number Presence (MSNP)
+
+**Description:** This parameter indicates the presence of the DL MBS QFI Sequence Number in the DL PDU Session Information frame.
+
+**Value range:** {0= DL MBS QFI Sequence Number not present, 1= DL MBS QFI Sequence Number present}.
+
+**Field length:** 1 bit.
+
+#### 5.5.3.24 DL MBS QFI Sequence Number
+
+**Description:** This parameter indicates the sequence number as assigned by the MB-UPF associated with a given MBS QoS Flow.
+
+**Value range:** $\{0..2^{32}-1\}$ .
+
+**Field length:** 4 octets.
+
+#### 5.5.3.25 DL Congestion Information
+
+**Description:** For the cases of ECN marking at UPF request, this field indicates the percentage of DL IP packets up to two decimal points that should be ECN marked for a QoS flow.
+
+For the case of congestion information request, this field should be interpreted as a percentage of congestion level in DL up to two decimal points for a QoS flow.
+
+As an example, value 9574 corresponds to a percentage of 95.74%.
+
+**Value range:** $\{0..10000\}$ .
+
+**Field length:** 2 octets.
+
+#### 5.5.3.26 UL Congestion Information
+
+**Description:** For the cases of ECN marking at UPF request, this field indicates the percentage of UL IP packets up to two decimal points that should be ECN marked for a QoS flow.
+
+For the case of congestion information request, this field should be interpreted as a percentage of congestion level in UL up to two decimal points for a QoS Flow.
+
+As an example, value 9574 corresponds to a percentage of 95.74%
+
+**Value range:** $\{0..10000\}$ .
+
+**Field length:** 2 octets.
+
+### 5.5.4 Timers
+
+Void.
+
+## 5.6 Handling of unknown, unforeseen and erroneous protocol data
+
+Void.
+
+# --- 6 PDU Set Information user plane protocol
+
+## 6.1 General
+
+The PDU Set Information UP layer uses the services of the Transport Network Layer in order to send its packets over the interface.
+
+## 6.2 PDU Set Information user plane protocol layer services
+
+The following functions are provided by the PDU Set Information user plane protocol:
+
+- Provision of PDU Set information elements associated with a QoS flow.
+
+- Provision of Indication of End of Data Burst for a QoS flow.
+
+## 6.3 Services expected from the Transport Network Layer
+
+The PDU set information UP layer expects the following services from the Transport Network Layer:
+
+- Transfer of PDU Set Information User Plane PDUs.
+
+## 6.4 Elementary procedures
+
+### 6.4.1 Transfer of DL PDU Set Information
+
+#### 6.4.1.1 Successful operation
+
+The purpose of the Transfer of DL PDU Set Information procedure is to send PDU Set information and indication of End of Data Burst related to a QoS flow from UPF to NG-RAN node or between NG-RAN nodes, or from gNB-CU to gNB-DU.
+
+The DL PDU SET INFORMATION frame includes a QoS Flow Identifier (QFI) field associated with the transferred packet. The NG-RAN shall use the received QFI to determine the QoS flow and QoS profile which are associated with the received packet.
+
+The DL PDU SET INFORMATION frame may include the PDU Set Information (i.e., PDU Set Sequence Number, PDU Sequence Number within a PDU Set, PDU Set Size, PDU Set Importance, and End PDU of the PDU Set) as specified in TS 23.501 [5].
+
+The DL PDU SET INFORMATION frame may include indication of End of Data Burst as specified in TS 23.501 [5].
+
+
+
+```
+sequenceDiagram
+ participant UPF/NG-RAN node
+ participant NG-RAN node
+ Note left of NG-RAN node:
+ Note right of UPF/NG-RAN node:
+ UPF/NG-RAN node->>NG-RAN node: DL PDU SET INFORMATION
+ Note left of NG-RAN node:
+```
+
+Sequence diagram showing the successful transfer of DL PDU Set Information from a UPF/NG-RAN node to an NG-RAN node.
+
+Figure 6.4.1.1-1: Successful Transfer of DL PDU Set Information
+
+
+
+```
+sequenceDiagram
+ participant gNB-CU
+ participant gNB-DU
+ Note left of gNB-DU:
+ Note right of gNB-CU:
+ gNB-CU->>gNB-DU: DL PDU SET INFORMATION
+ Note left of gNB-DU:
+```
+
+Sequence diagram showing the successful transfer of DL PDU Set Information from a gNB-CU to a gNB-DU.
+
+Figure 6.4.1.1-2: Successful Transfer of DL PDU Set Information
+
+#### 6.4.1.2 Unsuccessful operation
+
+Void.
+
+## 6.5 Elements for the PDU Set Information user plane protocol
+
+### 6.5.1 General
+
+The structure of frames is specified as in the section 5.5.1.
+
+### 6.5.2 Frame format for the PDU Set Information user plane protocol
+
+#### 6.5.2.1 DL PDU SET INFORMATION (PDU Type 0)
+
+This frame format is defined to allow the NG-RAN to receive PDU Set Information and indication of End of Data Burst of a QoS flow.
+
+The following shows the respective DL PDU SET INFORMATION frame.
+
+| Bits | | | | | | | | Number<br>of Octets | | | | | | | | |
+|---------------|-----|---------------------------|---|-------|---|------|------|---------------------|--|--|--|--|--|--|--|--|
+| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | |
+| PDU Type (=0) | | | | Spare | | PSSI | EDBI | 1 | | | | | | | | |
+| Spare | | QoS Flow Identifier (QFI) | | | | | | 1 | | | | | | | | |
+| PSSN | | | | | | | | 2 | | | | | | | | |
+| PSN | | | | | | | | 1 | | | | | | | | |
+| EPDU | EDB | | | PSI | | | | 0 or 1 | | | | | | | | |
+| PSSize | | | | | | | | 0 or 3 | | | | | | | | |
+| Padding | | | | | | | | 0-3 | | | | | | | | |
+
+Figure 6.5.2.1-1: DL PDU SET INFORMATION (PDU Type 0) Format
+
+### 6.5.3 Coding of information elements in frames
+
+#### 6.5.3.1 PDU Type
+
+**Description:** The PDU Type indicates the structure of the PDU Set UP frame. The field takes the value of the PDU Type it identifies; i.e. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame.
+
+**Value range:** {0= DL PDU SET INFORMATION, 1-15=reserved for future PDU type extensions}.
+
+**Field length:** 4 bits.
+
+#### 6.5.3.2 Spare
+
+**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver. This field is reserved for later versions.
+
+**Value range:** (0–2<sup>n</sup>-1).
+
+**Field Length:** n bits.
+
+#### 6.5.3.3 QoS Flow Identifier (QFI)
+
+**Description:** When present this parameter indicates the QoS Flow Identifier of the QoS flow to which the transferred packet belongs.
+
+**Value range:** $\{0..2^6-1\}$ .
+
+**Field length:** 6 bits.
+
+#### 6.5.3.5 PSSI (PDU Set Size indicator)
+
+**Description:** This parameter indicates the presence of PDU Set Size (PSSize).
+
+**Value range:** $\{0= \text{PSSize not present}, 1= \text{PSSize present}\}$ .
+
+**Field length:** 1 bit.
+
+#### 6.5.3.6 EDBI (End Data Burst indicator)
+
+**Description:** This parameter indicates the presence of End of Data Burst (EDB).
+
+**Value range:** $\{0= \text{EDB not present}, 1= \text{EDB present}\}$ .
+
+**Field length:** 1 bit.
+
+#### 6.5.3.7 End PDU of the PDU Set (EPDU)
+
+**Description:** This parameter indicates whether the current PDU is the last PDU of the PDU set.
+
+**Value range:** $\{0= \text{all other PDUs of the PDU Set}, 1= \text{last PDU of the PDU set}\}$ .
+
+**Field length:** 1 bit.
+
+#### 6.5.3.8 End of Data Burst (EDB)
+
+**Description:** This parameter indicates the end of a Data Burst.
+
+**Value range:** $\{0..2^3-1\}$ .
+
+**Field length:** 3 bits.
+
+#### 6.5.3.9 PDU Set Importance (PSI)
+
+**Description:** This parameter indicates the importance of the current PDU Set compared to other PDU Sets within the same QoS flow. Lower values shall indicate a higher importance. PDU Set with the highest importance PDU Set is indicated by 0 and the lowest importance PDU Set is indicated by 15.
+
+**Value range:** $\{0..2^4-1\}$ .
+
+**Field length:** 4 bits.
+
+#### 6.5.3.10 PDU Set Sequence Number (PSSN)
+
+**Description:** This parameter indicates the sequence number of the PDU Set to which the current PDU belongs acting as an identifier for the PDU Set.
+
+**Value range:** $\{0..2^{16}-1\}$ .
+
+**Field length:** 2 octets.
+
+#### 6.5.3.11 PDU Sequence Number within a PDU Set (PSN)
+
+**Description:** This parameter indicates the sequence number of the current PDU within the PDU Set. The PSN shall be set to 0 for the first PDU in the PDU Set and incremented monotonically for every PDU in the PDU set in order of transmission from the sender.
+
+**Value range:** $\{0..2^8-1\}$ .
+
+**Field length:** 1 octet.
+
+#### 6.5.3.12 PDU Set Size (PSSize)
+
+**Description:** This parameter indicates the total size of all PDUs of the PDU Set to which the current PDU belongs.
+
+**Value range:** $\{0..2^{24}-1\}$ .
+
+**Field length:** 3 octets.
+
+### 6.5.4 Timers
+
+Void.
+
+## 6.6 Handling of unknown, unforeseen and erroneous protocol data
+
+Void.
+
+# Annex A (informative): Example of using Future Extension Field
+
+## A.1 Example of using Future Extension field
+
+| New IE flag 7(E) | New IE flag 6 | New IE flag 5 | New IE flag 4 | New IE flag 3 | New IE flag 2 | New IE flag 1 | New IE flag 0 | 1 Octet New IE Flags |
+|------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|----------------------|
+| New IE 1 | | | | | | | | 3 Octets |
+| New IE 2 | | | | | | | | 2 Octets |
+
+Figure A.1-1: Example of future Extension Field
+
+In the Example of the future Extension Field, New IE flag 0 indicates if the New IE 1 is present or not. New IE flag 1 indicates if the new IE 2 is present or not.
+
+### A.1.1 New IE Flags
+
+**Description:** The *New IE Flags* IE is only present if at least one new IE is present. The *New IE Flags* IE contains flags indicating which new IEs that are present following the *New IE Flags* IE. The last bit position of the *New IE Flags* IE is used as the Extension Flag to allow the extension of the *New IE Flags* IE in the future. Extension octets of the *New IE Flags* IE shall follow directly after the first octet of the *New IE Flags* IE. When an extension octet of the *New IE Flags* IE is present, then all previous extension octets of the *New IE Flags* IE and the *New IE Flags* IE shall also be present, even if they have all their flag bits indicating no presence of their respective new IEs.
+
+# Annex B (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2018-04 | R3#99bis | R3-181720 | | | | TS skeleton. | 0.0.1 |
+| 2018-04 | R3#99bis | R3-182525 | | | | Integration of R3-182399 with sections 4 and 5 and annex A1. | 0.1.0 |
+| 2018-05 | R3#100 | R3-183594 | | | | Integration of R3-182619 to remove editor's notes, remove FFS and fix some editorials; integration of R3-183413 introducing PDU type for downlink and uplink; removing the FFS of uplink frame type in line with R3-182619 for downlink frame type; integration of R3-183000 solving the FFS on QFI. | 0.2.0 |
+| 2018-06 | RAN#80 | RP-180740 | | | | For approval. | 1.0.0 |
+| 2018-06 | RAN#80 | | - | - | - | Specification approved at TSG-RAN and placed under change control | 15.0.0 |
+| 2018-09 | RAN#81 | RP-181922 | 0001 | 4 | F | NR Corrections (38.415 Baseline CR covering RAN3#101 agreements) | 15.1.0 |
+| 2018-12 | RAN#82 | RP-182446 | 0003 | - | F | Rapporteur's CR for TS38.415 | 15.2.0 |
+| 2020-03 | RAN#87-e | RP-200425 | 0012 | 3 | B | E2E delay measurement for QoS monitoring for URLLC | 16.0.0 |
+| 2020-07 | RAN#88-e | RP-201079 | 0010 | 5 | B | Introduction of NR IIOT support to TS 38.415 | 16.1.0 |
+| 2020-07 | RAN#88-e | RP-201085 | 0013 | 1 | F | QoS monitoring for URLLC | 16.1.0 |
+| 2020-09 | RAN#89-e | RP-201950 | 0014 | - | F | Need of D1 and Reporting interval for QoS monitoring for URLLC | 16.2.0 |
+| 2020-09 | RAN#89-e | RP-201948 | 0015 | 1 | F | Rapporteur Correction of QoS Flow Redundancy | 16.2.0 |
+| 2020-12 | RAN#90-e | RP-202313 | 0016 | 1 | F | N3/N9 packet delay reporting for GTP-U path QoS monitoring | 16.3.0 |
+| 2021-03 | RAN#91-e | RP-210240 | 0019 | 2 | F | UE support for D1 part of UL Delay and adding New IE Flag for extensibility | 16.4.0 |
+| 2021-06 | RAN#92-e | RP-211333 | 0027 | | A | Correction of PDU Type Frame | 16.5.0 |
+| 2021-12 | RAN#94-e | RP-212863 | 0030 | 2 | F | Correction for UL PDU Session Information | 16.6.0 |
+| 2022-03 | RAN#95-e | RP-220236 | 0033 | | D | Rapporteur Corrections of TS 38.415 | 17.0.0 |
+| 2022-03 | RAN#95-e | RP-220224 | 0034 | 1 | B | Introduction of NR MBS | 17.0.0 |
+| 2023-12 | RAN#102 | RP-233849 | 0038 | 2 | F | Correction of NG-U | 17.1.0 |
+| 2023-12 | RAN#102 | RP-233830 | 0037 | 5 | B | Introduction of XR enhancements | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38423/025f85981c69ed3274f1aa6c4844266e_img.jpg b/marked/Rel-18/38_series/38423/025f85981c69ed3274f1aa6c4844266e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdf4a5da5628958c5bdcebc50b866038846e2617
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/025f85981c69ed3274f1aa6c4844266e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:196dc2b10ad66d33275df28188dad77e1cbb8c350204fc243401e0bbf373728c
+size 9460
diff --git a/marked/Rel-18/38_series/38423/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-18/38_series/38423/0f26e70157bd4c45f825795cdcd20fbd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1063760487bb7d3da82ef4c0155882f9aa3cd795
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/0f26e70157bd4c45f825795cdcd20fbd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3018f9c5dbbf8cea666db22ea9a74d67effd281a85d1cebe5f257c5e51fa9e0b
+size 22501
diff --git a/marked/Rel-18/38_series/38423/1274805226c5a1f8b875aea0296b9f0f_img.jpg b/marked/Rel-18/38_series/38423/1274805226c5a1f8b875aea0296b9f0f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5dfb2dd4b1198a7f8cdb1e3cb9a11959eb7f004d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/1274805226c5a1f8b875aea0296b9f0f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dfe7bf80a30eaf82571f2ed9c9e20fa3d65fc9b9144b22b1f1638b6c39515472
+size 26374
diff --git a/marked/Rel-18/38_series/38423/132ad076dd59b60fd549f7a612ed568b_img.jpg b/marked/Rel-18/38_series/38423/132ad076dd59b60fd549f7a612ed568b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f34fd93e11683d29c5a0ea853bbc6aa51f0da1cb
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/132ad076dd59b60fd549f7a612ed568b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21dd8109a84458daa92ecf9894dfd4febd3c07c08671f90441ad24c29664f317
+size 40259
diff --git a/marked/Rel-18/38_series/38423/153a3b99a6b0e88ef9099455837acec7_img.jpg b/marked/Rel-18/38_series/38423/153a3b99a6b0e88ef9099455837acec7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ba7662182b27993003fb85b42f43fe306331603
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/153a3b99a6b0e88ef9099455837acec7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29db744f35c9121e3ebd4fb78ec951f641c07bb0d7d7ab63d0a32ebfb86394c1
+size 19367
diff --git a/marked/Rel-18/38_series/38423/15d5c901284409186049549eec95c4a4_img.jpg b/marked/Rel-18/38_series/38423/15d5c901284409186049549eec95c4a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d9e3ccf9660a564e583877802aa22a546741439
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/15d5c901284409186049549eec95c4a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b947394a2d7f667867fac608e847055a5f3b9828d4a5f45d89f8e01450306935
+size 42352
diff --git a/marked/Rel-18/38_series/38423/16766297a5918739f471ec2a3130cca9_img.jpg b/marked/Rel-18/38_series/38423/16766297a5918739f471ec2a3130cca9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a6f56b5cea8033b3a06e4efce31bf36137d08dc
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/16766297a5918739f471ec2a3130cca9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:951f205751edcef9b80b0c43d135ca5a9e5b44d27022a71e666be04789ec9cd0
+size 22616
diff --git a/marked/Rel-18/38_series/38423/19f90331494ba1e143d915d8d0061942_img.jpg b/marked/Rel-18/38_series/38423/19f90331494ba1e143d915d8d0061942_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cf53cd4f76c84af3e795093a9f07e233b791e5d1
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/19f90331494ba1e143d915d8d0061942_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02237b6773c65252ff6d4f33bb99db0fc15f526a0802ab17855944e97929af3b
+size 22104
diff --git a/marked/Rel-18/38_series/38423/1b2ce053624064d94a4143854da46702_img.jpg b/marked/Rel-18/38_series/38423/1b2ce053624064d94a4143854da46702_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..beb8e0e0e3a5801754d1ace340428761d980cac5
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/1b2ce053624064d94a4143854da46702_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d14250a69716fbfa672f59e87aae6ba5d2cb46c586fda37660c1691890a2d6b0
+size 21864
diff --git a/marked/Rel-18/38_series/38423/1e7bcf217ac77b893ea8387bb60ef224_img.jpg b/marked/Rel-18/38_series/38423/1e7bcf217ac77b893ea8387bb60ef224_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..959ad90959de5a03dc4fc139ac9c8411da35d3aa
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/1e7bcf217ac77b893ea8387bb60ef224_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1e8339120cedbccaa41a8adc937c2fa0bf731a0f3deb6260608f6053a4cc47c1
+size 19327
diff --git a/marked/Rel-18/38_series/38423/1fa325e34e0974a6426c93e541a7ee86_img.jpg b/marked/Rel-18/38_series/38423/1fa325e34e0974a6426c93e541a7ee86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f2bf11c238c82984de95da6131c66b95e4cc91d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/1fa325e34e0974a6426c93e541a7ee86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e9620c8cbfaa97b0fba05d119c3dbf0e6778dfec9fbe51d306bc53d93735c63
+size 20912
diff --git a/marked/Rel-18/38_series/38423/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-18/38_series/38423/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bb9d976ff4b20c0e7c839b2baabe4bee33dbdd6
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2a02bf9dd04223aae9cf5ef9e27988ef7c03f12d7633eb5b3fdee9d4fa1e133
+size 28281
diff --git a/marked/Rel-18/38_series/38423/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-18/38_series/38423/28085f681b9fff76a53c5b8b32338ee1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e38b85b51f468d999d86ce72ac8f0d66234c55d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/28085f681b9fff76a53c5b8b32338ee1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d66c2106efe34285c93af649c7200768bfc460a62729e5c07d3a55d99cdbd96
+size 19626
diff --git a/marked/Rel-18/38_series/38423/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/Rel-18/38_series/38423/28f2f470a7b2446ae5f525123534383c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..477e4e1c1d44f9a72026ec58f35d4d2f9ece4428
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/28f2f470a7b2446ae5f525123534383c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d024d040100d3bcebcbdc127a0fbb596c1c80004a0248dbe062d152abc7a78d2
+size 26875
diff --git a/marked/Rel-18/38_series/38423/2914642fbfe4ae35924bdf4beb189c1f_img.jpg b/marked/Rel-18/38_series/38423/2914642fbfe4ae35924bdf4beb189c1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b01d3f3d0a96a54cc0bd5dd280cb78a47b066a5f
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/2914642fbfe4ae35924bdf4beb189c1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b19cc82ec17b0e57b39fa32aa839542719757d37b3c370bf0fcb3b0cdbbbd5c
+size 24419
diff --git a/marked/Rel-18/38_series/38423/294444660b1376c49aeca748b8184e77_img.jpg b/marked/Rel-18/38_series/38423/294444660b1376c49aeca748b8184e77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34017f12a0a23ba48cb6df073a316e5a3e491e4f
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/294444660b1376c49aeca748b8184e77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76199cc2bffd7c185291a5226b6585ad2178ad4bfcc584cfb9f1e605b611e5b9
+size 21333
diff --git a/marked/Rel-18/38_series/38423/2ab8f576e02a51b403b2eed3bae53caa_img.jpg b/marked/Rel-18/38_series/38423/2ab8f576e02a51b403b2eed3bae53caa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8160e4067f18001645e7246054397900f692ef68
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/2ab8f576e02a51b403b2eed3bae53caa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a4c13a2f5b5ea0d12238df36146619b2784e19fd18d06f91339fce3b83762e6
+size 27431
diff --git a/marked/Rel-18/38_series/38423/2eb73eee0ca246cd09f43c2044f3fb49_img.jpg b/marked/Rel-18/38_series/38423/2eb73eee0ca246cd09f43c2044f3fb49_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bab2d4746ad93de60d9147b795ea9fdbc88d95de
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/2eb73eee0ca246cd09f43c2044f3fb49_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f0908156af8c2ca01701f9be5b53038fb00d98136300dc9f99de05ca65309a1
+size 14383
diff --git a/marked/Rel-18/38_series/38423/32d2783121efa86871886ed9d7678637_img.jpg b/marked/Rel-18/38_series/38423/32d2783121efa86871886ed9d7678637_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6058c78a937a0085b15b7e0ab4aa6bb9251c6621
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/32d2783121efa86871886ed9d7678637_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb11a32e3d88df3f2675e043c442e9ce33222734284e996f7fbbc43c37def881
+size 27524
diff --git a/marked/Rel-18/38_series/38423/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg b/marked/Rel-18/38_series/38423/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c9ef636f85771a4543f6598bdd9299322ec2d381
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6329c1b2ecd9f2167523c285736f5d9c8739fd013dbc181094c337719fc88d40
+size 20257
diff --git a/marked/Rel-18/38_series/38423/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg b/marked/Rel-18/38_series/38423/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a066068b89cca279491b04e979f0a0f35734b4ab
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/3e1e0cd2dc80989a84f05b7fe05ec207_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4c8fb7f3833d944b5e05e205b81e9d841e380f8b95da5bb3dde815f9c065ebe
+size 24168
diff --git a/marked/Rel-18/38_series/38423/4001fdeece60df718407b9cec5b257ca_img.jpg b/marked/Rel-18/38_series/38423/4001fdeece60df718407b9cec5b257ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2505d7bac0309dbfe9524c3ec63b2284d5e77f9
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/4001fdeece60df718407b9cec5b257ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17d7b1c61234f7c5a0724fb7a72047d16139bfe6ffdb62f573eccf3a53285f1b
+size 25433
diff --git a/marked/Rel-18/38_series/38423/49806c5ac206335a657bc126f17d37e8_img.jpg b/marked/Rel-18/38_series/38423/49806c5ac206335a657bc126f17d37e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82ae235fe45e1fb34a5de189c97451d09b45aaac
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/49806c5ac206335a657bc126f17d37e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dfdbc8d6aaeff10308603e1204383dffbc29bcbf6b99ab14e6c5e09df1591323
+size 24995
diff --git a/marked/Rel-18/38_series/38423/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/Rel-18/38_series/38423/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3655baa113c80328662bce08332104ab005cef6
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f90aa285dda7d2bd75897c9155092761a86ac571439ada159b3b93a52a8e79b
+size 27594
diff --git a/marked/Rel-18/38_series/38423/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg b/marked/Rel-18/38_series/38423/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7011d0b2549486fd9cf97fa1117df236e5978cb4
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9b9ae1432f231c550edec28f696b8d2430856f4e61960afb31d50ad263750a2
+size 26317
diff --git a/marked/Rel-18/38_series/38423/51167ecef86d85cdc6dde05a3afb74b8_img.jpg b/marked/Rel-18/38_series/38423/51167ecef86d85cdc6dde05a3afb74b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9e17a4a03c4b03d83a2656cef5c177f9268da77
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/51167ecef86d85cdc6dde05a3afb74b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d62e9df360bb7a0d264c51f0c51693d89584a88991dd17000b41ee69cea7fd0
+size 22093
diff --git a/marked/Rel-18/38_series/38423/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/marked/Rel-18/38_series/38423/5ec3284657e4df0df3653dd61d0ecd13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd0d34d179ce034833fe4d6d8e0bd452be6ed0db
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/5ec3284657e4df0df3653dd61d0ecd13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20ca0623f6d4ca59ca2cce0cf95f84fee7ababafd27396686e114aa895009ef7
+size 19180
diff --git a/marked/Rel-18/38_series/38423/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38423/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23f719d31a70fb6a990f97aba120edf8e2fee9b1
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0015f2857f5c84221c898c2be7faeb5049c90aea8ce42189ba200c9727c8a36
+size 9766
diff --git a/marked/Rel-18/38_series/38423/605625ddfc3363a6205ab0d43b184eaf_img.jpg b/marked/Rel-18/38_series/38423/605625ddfc3363a6205ab0d43b184eaf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..849e711bfdd58aed336cae214ae8ba175ab0ae57
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/605625ddfc3363a6205ab0d43b184eaf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4061d3f0f1796f655cc81147e195e22927e657445d4a708a788981706351296
+size 20750
diff --git a/marked/Rel-18/38_series/38423/61339c8e7f0655dd44a606430e2ec5ae_img.jpg b/marked/Rel-18/38_series/38423/61339c8e7f0655dd44a606430e2ec5ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9280c3ebfb5e1efe79fc8cabf06374f81769cc1
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/61339c8e7f0655dd44a606430e2ec5ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b5510087c1ecb12885c3d74df0499b7d2ffa6870498bb8d991ff20e6933af5a
+size 26068
diff --git a/marked/Rel-18/38_series/38423/61a49f3179b455e4d35242fc3d187a29_img.jpg b/marked/Rel-18/38_series/38423/61a49f3179b455e4d35242fc3d187a29_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48a4acec4152f41c3ad47f3dbe1505c52e82d312
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/61a49f3179b455e4d35242fc3d187a29_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f26b1339fd0185b6df7b02895b616555c790ec1e9bf7a52cdb2d85eb1930077
+size 23455
diff --git a/marked/Rel-18/38_series/38423/629606c93e8d5f98d72a90044ef4b15a_img.jpg b/marked/Rel-18/38_series/38423/629606c93e8d5f98d72a90044ef4b15a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4826e38b0f557a876e34dc4e2e82b13010d8a0dc
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/629606c93e8d5f98d72a90044ef4b15a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:81f3d604537a3465fd5be2f0af51f1ebbbfc3ba96cf7e80e625421f78e19bb98
+size 41882
diff --git a/marked/Rel-18/38_series/38423/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38423/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dad5b265705cd05f86c9823f8e51566955716391
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c115b386df16ca0ef359dfcf7b0ded5722c663ee6e16f5af905690d1492b8943
+size 6740
diff --git a/marked/Rel-18/38_series/38423/67c5b121b58d497a6de5addf4e7bd555_img.jpg b/marked/Rel-18/38_series/38423/67c5b121b58d497a6de5addf4e7bd555_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9df8e24ef3cb8789a2391d41019a530a63a97df
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/67c5b121b58d497a6de5addf4e7bd555_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:809d862836c872780a2cda3a81346620201f4e1ef461772608f8444cbb2eac58
+size 19846
diff --git a/marked/Rel-18/38_series/38423/6d67eee81b97a14e06a6fe57a95aff36_img.jpg b/marked/Rel-18/38_series/38423/6d67eee81b97a14e06a6fe57a95aff36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f2e5d8e25b4ecd2c2fb0a6c9edec1d207ec0b007
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/6d67eee81b97a14e06a6fe57a95aff36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53a37a98895925a6613ef900bf93fb3a618e7b11dc3ec31b69ee1022f2213e1d
+size 27525
diff --git a/marked/Rel-18/38_series/38423/7155d055d79462bd2d5aa15131922975_img.jpg b/marked/Rel-18/38_series/38423/7155d055d79462bd2d5aa15131922975_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e54d983186208ab8476e4b7cb41131804814d3c3
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/7155d055d79462bd2d5aa15131922975_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffbb0257618818233a52820a5f86e101888d2b9b630f11d902d2d940db95d664
+size 26062
diff --git a/marked/Rel-18/38_series/38423/762a17cd79880dbca172bcbbe9375223_img.jpg b/marked/Rel-18/38_series/38423/762a17cd79880dbca172bcbbe9375223_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9286635ebdd94fa692a1e44e98bbfc24912193c5
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/762a17cd79880dbca172bcbbe9375223_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53a325bcb0d61d53d01518591abdd59b0e118a3c82e3abdcbbcbf1b425481267
+size 26660
diff --git a/marked/Rel-18/38_series/38423/77534ce9b1e09b533f730d8f45e01956_img.jpg b/marked/Rel-18/38_series/38423/77534ce9b1e09b533f730d8f45e01956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c8e11c3ea913fa59f3752f965f8da7bada1cb89e
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/77534ce9b1e09b533f730d8f45e01956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a81b151feb900cfd8e17098e8eb18972c35c6f0010bc899dfe8f1024b876d31e
+size 25814
diff --git a/marked/Rel-18/38_series/38423/7818b1bd115c04ee738bcf90f51d945b_img.jpg b/marked/Rel-18/38_series/38423/7818b1bd115c04ee738bcf90f51d945b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..36436759e5452f3269ede7467d73833e4cfb977d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/7818b1bd115c04ee738bcf90f51d945b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfd9d1756b8c4f0ec4ae9c011ce1d185e3ffb1257e14d2eaacbd2c094e097a58
+size 24079
diff --git a/marked/Rel-18/38_series/38423/7c57192c514175021e4560a1a46126c1_img.jpg b/marked/Rel-18/38_series/38423/7c57192c514175021e4560a1a46126c1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6e20ac7c08e1ff357efd9529fc44947494bdbd2
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/7c57192c514175021e4560a1a46126c1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53388d3d08f286356e3432120861bb40b64f71847391d10c236e5883ad391b32
+size 27116
diff --git a/marked/Rel-18/38_series/38423/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/marked/Rel-18/38_series/38423/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..102f7597fc229e768654dc29d84ef960b7ff974a
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55f0bac309b2df2a07ecf6bd8398732b371923bbca28ba854866946f786dcf04
+size 21358
diff --git a/marked/Rel-18/38_series/38423/7d78469417c76901ecf6e36600a721cb_img.jpg b/marked/Rel-18/38_series/38423/7d78469417c76901ecf6e36600a721cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16b686081ee5362ff937865386ba92f1486f9ba0
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/7d78469417c76901ecf6e36600a721cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79a18350d8ed9fbe8dd72c5e2fdad2fcab2db5497eb811e032a9857337c07eed
+size 17934
diff --git a/marked/Rel-18/38_series/38423/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-18/38_series/38423/7ed5d5770331f31ade15439a21c31425_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f801a49db2dbbbefbd0312674931eebb0c94c245
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/7ed5d5770331f31ade15439a21c31425_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b81243bb6617379bbb0e0da3fa1edbb4deb2fe6af275e7bb6a0c4b3dbd74e04
+size 19383
diff --git a/marked/Rel-18/38_series/38423/8d6b56ea28d70ce527efde127103e045_img.jpg b/marked/Rel-18/38_series/38423/8d6b56ea28d70ce527efde127103e045_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bb1018207f3b3e9eddf8e2e28be426377bff2f2a
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/8d6b56ea28d70ce527efde127103e045_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a420a8dceaef3b036e6f15dfcccb369bb7c6c83d2126e7570cd37e780c90ac1d
+size 11461
diff --git a/marked/Rel-18/38_series/38423/901800172164e0494762ffa57a09993f_img.jpg b/marked/Rel-18/38_series/38423/901800172164e0494762ffa57a09993f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acd4821f84b2039071ec8a7e9c6145f0a10453ff
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/901800172164e0494762ffa57a09993f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c19089b501d4e0fe0aeaca18bc1c039c74948bd8a5194249700424872f6bca7b
+size 19917
diff --git a/marked/Rel-18/38_series/38423/907cc0e0bfee6288b926d1c38c232e5d_img.jpg b/marked/Rel-18/38_series/38423/907cc0e0bfee6288b926d1c38c232e5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39373f1dd54d45df61f59382f7058b8788447319
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/907cc0e0bfee6288b926d1c38c232e5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ae7583326d4342abd57cc0215aaae76c2e09bdcfe940ddbb39a135d0df9b7d8
+size 20929
diff --git a/marked/Rel-18/38_series/38423/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/Rel-18/38_series/38423/921458d4fc1b778c2450592ac9745b48_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ed40a8230c4b749d565a760688c7df77decee1d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/921458d4fc1b778c2450592ac9745b48_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ac45a0991a9a1583d96e562f672f771b6e4b361e6b598c3767f8b9b089d0a83
+size 20078
diff --git a/marked/Rel-18/38_series/38423/981668c6be5792b778cccb1af38477e2_img.jpg b/marked/Rel-18/38_series/38423/981668c6be5792b778cccb1af38477e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a98e7d63ef629259652cda75ab95bf720d164e23
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/981668c6be5792b778cccb1af38477e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89b1fcf52f9416fbb88ca98c96fab111d76c0eb0b502fca6afa718deaa6e36f4
+size 27049
diff --git a/marked/Rel-18/38_series/38423/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-18/38_series/38423/9b1ec0090070bdf52ea28763b8d52477_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01c175781829983b3003f04369712073663219c2
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/9b1ec0090070bdf52ea28763b8d52477_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7d59be6df95bd86f6dbc1edad5af9db599aad05632f5540bedbf9a383f315ed
+size 18461
diff --git a/marked/Rel-18/38_series/38423/9dd03da031e134bfc9ecc730dd5f6583_img.jpg b/marked/Rel-18/38_series/38423/9dd03da031e134bfc9ecc730dd5f6583_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..834b80efd440978a6f9e334831a1f9352fb1bb06
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/9dd03da031e134bfc9ecc730dd5f6583_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a176716eb445fada4a0ea7a963b4efe96ec675737adf3b74adf8041411a0f0ca
+size 19801
diff --git a/marked/Rel-18/38_series/38423/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg b/marked/Rel-18/38_series/38423/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df67c457d0fda0eec7a9d0b7f36cb4e842a186f0
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:628be92ad55e6e554dffd91e792d3640c591d5eab7e794437db8a62132fab899
+size 29126
diff --git a/marked/Rel-18/38_series/38423/a2ce6b025527528c4a040b77e0795a3d_img.jpg b/marked/Rel-18/38_series/38423/a2ce6b025527528c4a040b77e0795a3d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..194c57662ac1f9538b7503cafb41284e0647f69a
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/a2ce6b025527528c4a040b77e0795a3d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d47651d1215ab7bb540cf107ab2fa8e90e54fd040cecc93a491cc087fbfc5fa
+size 19058
diff --git a/marked/Rel-18/38_series/38423/a471382fa73185ead4f9b83e3e64ee96_img.jpg b/marked/Rel-18/38_series/38423/a471382fa73185ead4f9b83e3e64ee96_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..16575f6c17ea05a7150ce9c6116eb39303b0b3a4
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/a471382fa73185ead4f9b83e3e64ee96_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09c743626f2ce109d74025ebcea1d0b56425e4e63489af1b5952fa280db95eb4
+size 18466
diff --git a/marked/Rel-18/38_series/38423/a5481fd31c02b525617e70f2de357039_img.jpg b/marked/Rel-18/38_series/38423/a5481fd31c02b525617e70f2de357039_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc09a22547af5bb602dc71696cd3e7df47ecd236
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/a5481fd31c02b525617e70f2de357039_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c18ef1d7a6d7cb236ebacaebc06d6a061ed9a33edd24863b5fc6372d680e4bf1
+size 20797
diff --git a/marked/Rel-18/38_series/38423/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Rel-18/38_series/38423/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1073acd2352f0fc0b3528fb4a356bf1b1c75cfd
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09f96233332ad803d0aaea195c33f4351dbfd19b2ee3ccbe77d58f4f735c96ba
+size 26823
diff --git a/marked/Rel-18/38_series/38423/a92e47ea99d1810474cecc9ca4574e34_img.jpg b/marked/Rel-18/38_series/38423/a92e47ea99d1810474cecc9ca4574e34_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..534175822321d8f87dd1400e3d245eeebb5897e5
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/a92e47ea99d1810474cecc9ca4574e34_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5bfe8b49b21d384ea2c64ff4cfb688867dd8bbc38e4bd7c606860ba3e381d5f3
+size 20252
diff --git a/marked/Rel-18/38_series/38423/ac42de838505beb048fb1267c46de428_img.jpg b/marked/Rel-18/38_series/38423/ac42de838505beb048fb1267c46de428_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d33ba69fe7619b1241e010337fcbc193e449b849
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/ac42de838505beb048fb1267c46de428_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f2b8707153e46d773e741b5aa363ac4e664cdfebd5ec6bce0051b350d65e674
+size 18181
diff --git a/marked/Rel-18/38_series/38423/af90aabfe3c8c65617da060d82bf99c5_img.jpg b/marked/Rel-18/38_series/38423/af90aabfe3c8c65617da060d82bf99c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12a2b27bb024d69aaf59bb2ba94fbd7e73db8188
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/af90aabfe3c8c65617da060d82bf99c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be39cde8e3868a5bd89b6f880bab1cd53a591a8898a542f6e05f691b14188c82
+size 17404
diff --git a/marked/Rel-18/38_series/38423/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-18/38_series/38423/b06a4c871dfd0ce034cf801519d0039a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70b8129347b8296891f976f755be183d96497be6
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/b06a4c871dfd0ce034cf801519d0039a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e4d6b997987116635981a869818e41fcb463d4a70611bfa8ecff332fd144b3e
+size 18531
diff --git a/marked/Rel-18/38_series/38423/b73fce8bb6592c6a3c0cd51e9c08d517_img.jpg b/marked/Rel-18/38_series/38423/b73fce8bb6592c6a3c0cd51e9c08d517_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddd6893b7fdfd8c87a52889e5d72f06683ae2b61
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/b73fce8bb6592c6a3c0cd51e9c08d517_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0ad89e07bbedb6280701a8cd8d8a4e2a25182159800a887feee66cb1579b741
+size 27034
diff --git a/marked/Rel-18/38_series/38423/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg b/marked/Rel-18/38_series/38423/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..570b656edc24fa996c94fa2d15ffe3f0e865eeb2
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6fafedb2f85e031343bb5edfb8b6e963e6a29edfbf8fa0c2450783287ea6bc06
+size 22842
diff --git a/marked/Rel-18/38_series/38423/c7e27041e661260fd0c8e89c763bb32e_img.jpg b/marked/Rel-18/38_series/38423/c7e27041e661260fd0c8e89c763bb32e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db7634a044979f68b40c81835e3e1b2b558c51f2
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/c7e27041e661260fd0c8e89c763bb32e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:29f655f5e6d881875c0565d420adce1549024ab093e170813f2762df9baf9cd7
+size 25964
diff --git a/marked/Rel-18/38_series/38423/c96780e69fd790e1e62e1c3e5431636a_img.jpg b/marked/Rel-18/38_series/38423/c96780e69fd790e1e62e1c3e5431636a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7198390bfa1f249c1aa8f2e0f2df0601d6a9dc3d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/c96780e69fd790e1e62e1c3e5431636a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7da8f3d8b69a13c3a8b53bf459765564e39a67e8621a32100fe407049e898bc3
+size 32042
diff --git a/marked/Rel-18/38_series/38423/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg b/marked/Rel-18/38_series/38423/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99fc1972bfda668e280b600133cb0dc39950af53
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f98bb49ab4a294bf688a0049e5d1542cf2bf6f59897fc2ca1dd133f3ac10c1c
+size 24664
diff --git a/marked/Rel-18/38_series/38423/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg b/marked/Rel-18/38_series/38423/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fe4ea5b3bb6784423381405483dc62f33157565
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b04ee2f0a11768bd269260c338cb7df515cd005b7381c61846eba4f290cdd0bb
+size 27592
diff --git a/marked/Rel-18/38_series/38423/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-18/38_series/38423/d9cfc30025244dcd75766061f27ee09f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f602c3c6bf738484021e4c8aab273a1cb660e2f
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/d9cfc30025244dcd75766061f27ee09f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0b3dee2ee858870f98877fdc937de0822e07b845fdb1f834a50c0265564a9f5a
+size 27853
diff --git a/marked/Rel-18/38_series/38423/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/marked/Rel-18/38_series/38423/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37fda42d2c3e5c80377989ab2eefb10738c625d7
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bd2a9691025150115462d512995f6c1be4da9d409e553941c199455730312db
+size 25574
diff --git a/marked/Rel-18/38_series/38423/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-18/38_series/38423/db5deafdae53dbc7d5972957f708c691_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12a7c64549623317ed08c9cf8162ff310b949558
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/db5deafdae53dbc7d5972957f708c691_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcfceb5c863bfb31d321a9bed14bdc8907ad14ff877db53762e8eb388aa933b4
+size 27315
diff --git a/marked/Rel-18/38_series/38423/dde1a42ca58cd189901556a0cbfe7d57_img.jpg b/marked/Rel-18/38_series/38423/dde1a42ca58cd189901556a0cbfe7d57_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b486f4654f60d6fbeac5c9c8691892fb3328267
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/dde1a42ca58cd189901556a0cbfe7d57_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96b4de0f1c0fc039003c06166ac6d80d401720c9d821808024d8bc15818cd019
+size 27379
diff --git a/marked/Rel-18/38_series/38423/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-18/38_series/38423/df935fc9efbd024af4ba77e46bb0bb19_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef5187f5d67fcb372951f598b732ee0c92e3991b
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/df935fc9efbd024af4ba77e46bb0bb19_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9209c431d97472338ba5cb609dadc9c239a201cdc43e0e96e78ab301e73a6f72
+size 18833
diff --git a/marked/Rel-18/38_series/38423/e1136c8a41c5a8081a8a554e513cd86e_img.jpg b/marked/Rel-18/38_series/38423/e1136c8a41c5a8081a8a554e513cd86e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9403eac1f1cd0b840ae49ff5fd58933323d5f6e0
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/e1136c8a41c5a8081a8a554e513cd86e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:43ac8ef4972a2e7b780f7ed8a75e0ff56a24e3a86c1f461f2705de3c617386e5
+size 20571
diff --git a/marked/Rel-18/38_series/38423/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg b/marked/Rel-18/38_series/38423/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cd6ac029e1c05bcda811e38be3f736874e51ef1
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83a88742b3412405c8f2f4e92766bc4f121ce0ffd9971dfb07766e218565716d
+size 20607
diff --git a/marked/Rel-18/38_series/38423/e26bb66586e464339df27951d5c9355e_img.jpg b/marked/Rel-18/38_series/38423/e26bb66586e464339df27951d5c9355e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..52981816e344329376f4ea0667a999aee489370d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/e26bb66586e464339df27951d5c9355e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fff229bbafb712d705e371c10af038a7f6b7b49f40269bd1b375557bc31938b
+size 16789
diff --git a/marked/Rel-18/38_series/38423/ef3cc411849a8effc80adb5a6ad57b36_img.jpg b/marked/Rel-18/38_series/38423/ef3cc411849a8effc80adb5a6ad57b36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4279c7e3d2fc58878cd7fffbf5563a667c84fac
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/ef3cc411849a8effc80adb5a6ad57b36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bd7050c54d0fa191fa15f158cb4434322943381f6446af6c8486aa27f82e858
+size 17538
diff --git a/marked/Rel-18/38_series/38423/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/marked/Rel-18/38_series/38423/f1ba1e68228ebd4c3109371574a723e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa40cff0732fa7c592d64ac7265688e2e508b4ed
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/f1ba1e68228ebd4c3109371574a723e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9688a31037047daed558cb55e4fcfd1787c92aaef8f3322b09609cba8435d304
+size 21372
diff --git a/marked/Rel-18/38_series/38423/f5698523df298c80a0c6b5d4ca657993_img.jpg b/marked/Rel-18/38_series/38423/f5698523df298c80a0c6b5d4ca657993_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d1adf9ca81bbd06348932bcbddf94f3b4af7a31
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/f5698523df298c80a0c6b5d4ca657993_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3778e11102f17f3da7a934cefec90de85dc26eeebad78a80f8d0eee20b4ad2e
+size 23111
diff --git a/marked/Rel-18/38_series/38423/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-18/38_series/38423/fd3cbb53e991f8209ba17b398f426e13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..318e84007e9f31ef1e49557086dc28d26e7bdd5d
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/fd3cbb53e991f8209ba17b398f426e13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d26eea87c66b1628cd6a67471e22715f17678f8629fe2301ffee22516cf2cea
+size 20914
diff --git a/marked/Rel-18/38_series/38423/raw.md b/marked/Rel-18/38_series/38423/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed5fa231bafe5f22cc8239853b82f0f1ce78ac99
--- /dev/null
+++ b/marked/Rel-18/38_series/38423/raw.md
@@ -0,0 +1,32229 @@
+
+
+# 3GPP TS 38.423 V18.0.0 (2023-12)
+
+*Technical Specification*
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a large '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP..
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+
+Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# **3GPP**
+
+Postal address
+
+3GPP support office address
+650 Route des Lucioles – Sophia Antipolis
+Valbonne – FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+<http://www.3gpp.org>
+
+# --- Contents
+
+| | |
+|----------------------------------------------------|----|
+| Foreword..... | 16 |
+| 1 Scope..... | 17 |
+| 2 References..... | 17 |
+| 3 Definitions, symbols and abbreviations..... | 19 |
+| 3.1 Definitions..... | 19 |
+| 3.2 Abbreviations..... | 20 |
+| 4 General..... | 21 |
+| 4.1 Procedure specification principles..... | 21 |
+| 4.2 Forwards and backwards compatibility..... | 21 |
+| 4.3 Specification notations..... | 21 |
+| 5 XnAP services..... | 21 |
+| 5.1 XnAP procedure modules..... | 22 |
+| 5.2 Parallel transactions..... | 22 |
+| 6 Services expected from signalling transport..... | 22 |
+| 7 Functions of XnAP..... | 22 |
+| 8 XnAP procedures..... | 22 |
+| 8.1 Elementary procedures..... | 22 |
+| 8.2 Basic mobility procedures..... | 25 |
+| 8.2.1 Handover Preparation..... | 25 |
+
+# **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+| | | |
+|---------|------------------------------|----|
+| 8.2.1.1 | General..... | 25 |
+| 8.2.1.2 | Successful Operation..... | 25 |
+| 8.2.1.3 | Unsuccessful Operation..... | 32 |
+| 8.2.1.4 | Abnormal Conditions..... | 33 |
+| 8.2.2 | SN Status Transfer..... | 33 |
+| 8.2.2.1 | General..... | 33 |
+| 8.2.2.2 | Successful Operation..... | 34 |
+| 8.2.2.3 | Unsuccessful Operation..... | 35 |
+| 8.2.2.4 | Abnormal Conditions..... | 35 |
+| 8.2.3 | Handover Cancel..... | 35 |
+| 8.2.3.1 | General..... | 35 |
+| 8.2.3.2 | Successful Operation..... | 35 |
+| 8.2.3.3 | Unsuccessful Operation..... | 35 |
+| 8.2.3.4 | Abnormal Conditions..... | 35 |
+| 8.2.4 | Retrieve UE Context..... | 36 |
+| 8.2.4.1 | General..... | 36 |
+| 8.2.4.2 | Successful Operation..... | 36 |
+| 8.2.4.3 | Unsuccessful Operation..... | 39 |
+| 8.2.4.4 | Abnormal Conditions..... | 40 |
+| 8.2.5 | RAN Paging..... | 40 |
+| 8.2.5.1 | General..... | 40 |
+| 8.2.5.2 | Successful operation..... | 40 |
+| 8.2.5.3 | Unsuccessful Operation..... | 41 |
+| 8.2.5.4 | Abnormal Condition..... | 41 |
+| 8.2.6 | XN-U Address Indication..... | 41 |
+| 8.2.6.1 | General..... | 41 |
+| 8.2.6.2 | Successful Operation..... | 42 |
+| 8.2.6.3 | Unsuccessful Operation..... | 43 |
+| 8.2.6.4 | Abnormal Conditions..... | 43 |
+| 8.2.7 | UE Context Release..... | 43 |
+
+| | | |
+|----------|----------------------------------|----|
+| 8.2.7.1 | General..... | 43 |
+| 8.2.7.2 | Successful Operation..... | 44 |
+| 8.2.7.3 | Unsuccessful Operation..... | 45 |
+| 8.2.7.4 | Abnormal Conditions..... | 45 |
+| 8.2.8 | Handover Success..... | 45 |
+| 8.2.8.1 | General..... | 45 |
+| 8.2.8.2 | Successful Operation..... | 45 |
+| 8.2.8.3 | Unsuccessful Operation..... | 46 |
+| 8.2.8.4 | Abnormal Conditions..... | 46 |
+| 8.2.9 | Conditional Handover Cancel..... | 46 |
+| 8.2.9.1 | General..... | 46 |
+| 8.2.9.2 | Successful Operation..... | 46 |
+| 8.2.9.3 | Unsuccessful Operation..... | 46 |
+| 8.2.9.4 | Abnormal Conditions..... | 47 |
+| 8.2.10 | Early Status Transfer..... | 47 |
+| 8.2.10.1 | General..... | 47 |
+| 8.2.10.2 | Successful Operation..... | 47 |
+| 8.2.10.3 | Unsuccessful Operation..... | 48 |
+| 8.2.10.4 | Abnormal Conditions..... | 48 |
+| 8.2.11 | RAN Multicast Group Paging..... | 49 |
+| 8.2.11.1 | General..... | 49 |
+| 8.2.11.2 | Successful operation..... | 49 |
+| 8.2.12 | Retrieve UE Context Confirm..... | 49 |
+| 8.2.12.1 | General..... | 49 |
+| 8.2.12.2 | Successful Operation..... | 49 |
+| 8.2.12.3 | Unsuccessful Operation..... | 50 |
+| 8.2.12.4 | Abnormal Conditions..... | 50 |
+| 8.2.13 | Partial UE Context Transfer..... | 50 |
+| 8.2.13.1 | General..... | 50 |
+| 8.2.13.2 | Successful Operation..... | 50 |
+
+| | | |
+|----------|---------------------------------------------------------------------|----|
+| 8.2.13.3 | Unsuccessful Operation..... | 51 |
+| 8.2.13.4 | Abnormal Condition..... | 51 |
+| 8.3 | Procedures for Dual Connectivity..... | 51 |
+| 8.3.1 | S-NG-RAN node Addition Preparation..... | 51 |
+| 8.3.1.1 | General..... | 51 |
+| 8.3.1.2 | Successful Operation..... | 51 |
+| 8.3.1.3 | Unsuccessful Operation..... | 58 |
+| 8.3.1.4 | Abnormal Conditions..... | 58 |
+| 8.3.2 | S-NG-RAN node Reconfiguration Completion..... | 59 |
+| 8.3.2.1 | General..... | 59 |
+| 8.3.2.2 | Successful Operation..... | 59 |
+| 8.3.2.3 | Abnormal Conditions..... | 59 |
+| 8.3.3 | M-NG-RAN node initiated S-NG-RAN node Modification Preparation..... | 60 |
+| 8.3.3.1 | General..... | 60 |
+| 8.3.3.2 | Successful Operation..... | 60 |
+| 8.3.3.3 | Unsuccessful Operation..... | 69 |
+| 8.3.3.4 | Abnormal Conditions..... | 69 |
+| 8.3.4 | S-NG-RAN node initiated S-NG-RAN node Modification..... | 70 |
+| 8.3.4.1 | General..... | 70 |
+| 8.3.4.2 | Successful Operation..... | 70 |
+| 8.3.4.3 | Unsuccessful Operation..... | 73 |
+| 8.3.4.4 | Abnormal Conditions..... | 74 |
+| 8.3.5 | S-NG-RAN node initiated S-NG-RAN node Change..... | 74 |
+| 8.3.5.1 | General..... | 74 |
+| 8.3.5.2 | Successful Operation..... | 75 |
+| 8.3.5.3 | Unsuccessful Operation..... | 76 |
+| 8.3.5.4 | Abnormal Conditions..... | 76 |
+| 8.3.6 | M-NG-RAN node initiated S-NG-RAN node Release..... | 76 |
+| 8.3.6.1 | General..... | 76 |
+| 8.3.6.2 | Successful Operation..... | 77 |
+
+| | | |
+|----------|-----------------------------------------------------|----|
+| 8.3.6.3 | Unsuccessful Operation..... | 78 |
+| 8.3.6.4 | Abnormal Conditions..... | 78 |
+| 8.3.7 | S-NG-RAN node initiated S-NG-RAN node Release..... | 78 |
+| 8.3.7.1 | General..... | 78 |
+| 8.3.7.2 | Successful Operation..... | 78 |
+| 8.3.7.3 | Unsuccessful Operation..... | 79 |
+| 8.3.7.4 | Abnormal Conditions..... | 79 |
+| 8.3.8 | S-NG-RAN node Counter Check..... | 79 |
+| 8.3.8.1 | General..... | 79 |
+| 8.3.8.2 | Successful Operation..... | 79 |
+| 8.3.8.3 | Unsuccessful Operation..... | 80 |
+| 8.3.8.4 | Abnormal Conditions..... | 80 |
+| 8.3.9 | RRC Transfer..... | 80 |
+| 8.3.9.1 | General..... | 80 |
+| 8.3.9.2 | Successful Operation..... | 80 |
+| 8.3.9.3 | Unsuccessful Operation..... | 81 |
+| 8.3.9.4 | Abnormal Conditions..... | 81 |
+| 8.3.10 | Notification Control Indication..... | 81 |
+| 8.3.10.1 | General..... | 81 |
+| 8.3.10.2 | Successful Operation – M-NG-RAN node initiated..... | 82 |
+| 8.3.10.3 | Successful Operation – S-NG-RAN node initiated..... | 82 |
+| 8.3.10.4 | Abnormal Conditions..... | 82 |
+| 8.3.11 | Activity Notification..... | 83 |
+| 8.3.11.1 | General..... | 83 |
+| 8.3.11.2 | Successful Operation..... | 83 |
+| 8.3.11.3 | Abnormal Conditions..... | 83 |
+| 8.3.12 | E-UTRA – NR Cell Resource Coordination..... | 84 |
+| 8.3.12.1 | General..... | 84 |
+| 8.3.12.2 | Successful Operation..... | 84 |
+| 8.3.13 | Secondary RAT Data Usage Report..... | 85 |
+
+| | | |
+|----------|---------------------------------------|----|
+| 8.3.13.1 | General..... | 85 |
+| 8.3.13.2 | Successful Operation..... | 85 |
+| 8.3.13.3 | Unsuccessful Operation..... | 85 |
+| 8.3.13.4 | Abnormal Conditions..... | 85 |
+| 8.3.14 | Trace Start..... | 85 |
+| 8.3.14.1 | General..... | 85 |
+| 8.3.14.2 | Successful Operation..... | 86 |
+| 8.3.14.3 | Abnormal Conditions..... | 86 |
+| 8.3.15 | Deactivate Trace..... | 87 |
+| 8.3.15.1 | General..... | 87 |
+| 8.3.15.2 | Successful Operation..... | 87 |
+| 8.3.15.3 | Abnormal Conditions..... | 87 |
+| 8.3.16 | Cell Traffic Trace..... | 87 |
+| 8.3.16.1 | General..... | 87 |
+| 8.3.16.2 | Successful Operation..... | 88 |
+| 8.3.17 | SCG Failure Information Report..... | 88 |
+| 8.3.17.1 | General..... | 88 |
+| 8.3.17.2 | Successful Operation..... | 88 |
+| 8.3.17.3 | Unsuccessful Operation..... | 89 |
+| 8.3.17.4 | Abnormal Conditions..... | 89 |
+| 8.3.18 | SCG Failure Transfer..... | 89 |
+| 8.3.18.1 | General..... | 89 |
+| 8.3.18.2 | Successful Operation..... | 89 |
+| 8.3.18.3 | Unsuccessful Operation..... | 89 |
+| 8.3.18.4 | Abnormal Conditions..... | 89 |
+| 8.3.19 | Conditional PSCell Change Cancel..... | 89 |
+| 8.3.19.1 | General..... | 89 |
+| 8.3.19.2 | Successful Operation..... | 90 |
+| 8.3.19.3 | Unsuccessful Operation..... | 90 |
+| 8.3.19.4 | Abnormal Conditions..... | 90 |
+
+| | | |
+|----------|---------------------------------------|-----|
+| 8.3.20 | RACH Indication..... | 90 |
+| 8.3.20.1 | General..... | 90 |
+| 8.3.20.2 | Successful Operation..... | 90 |
+| 8.3.20.3 | Abnormal Conditions..... | 90 |
+| 8.4 | Global procedures..... | 91 |
+| 8.4.1 | Xn Setup..... | 91 |
+| 8.4.1.1 | General..... | 91 |
+| 8.4.1.2 | Successful Operation..... | 91 |
+| 8.4.1.3 | Unsuccessful Operation..... | 93 |
+| 8.4.1.4 | Abnormal Conditions..... | 94 |
+| 8.4.2 | NG-RAN node Configuration Update..... | 94 |
+| 8.4.2.1 | General..... | 94 |
+| 8.4.2.2 | Successful Operation..... | 95 |
+| 8.4.2.3 | Unsuccessful Operation..... | 99 |
+| 8.4.2.4 | Abnormal Conditions..... | 99 |
+| 8.4.3 | Cell Activation..... | 100 |
+| 8.4.3.1 | General..... | 100 |
+| 8.4.3.2 | Successful Operation..... | 100 |
+| 8.4.3.3 | Unsuccessful Operation..... | 101 |
+| 8.4.3.4 | Abnormal Conditions..... | 101 |
+| 8.4.4 | Reset..... | 101 |
+| 8.4.4.1 | General..... | 101 |
+| 8.4.4.2 | Successful Operation..... | 101 |
+| 8.4.4.3 | Unsuccessful Operation..... | 102 |
+| 8.4.4.4 | Abnormal Conditions..... | 102 |
+| 8.4.5 | Error Indication..... | 102 |
+| 8.4.5.1 | General..... | 102 |
+| 8.4.5.2 | Successful Operation..... | 103 |
+| 8.4.5.3 | Unsuccessful Operation..... | 103 |
+| 8.4.5.4 | Abnormal Conditions..... | 103 |
+
+| | | |
+|----------|-------------------------------------------|-----|
+| 8.4.6 | Xn Removal..... | 103 |
+| 8.4.6.1 | General..... | 103 |
+| 8.4.6.2 | Successful Operation..... | 104 |
+| 8.4.6.3 | Unsuccessful Operation..... | 104 |
+| 8.4.6.4 | Abnormal Conditions..... | 104 |
+| 8.4.7 | Failure Indication..... | 105 |
+| 8.4.7.1 | General..... | 105 |
+| 8.4.7.2 | Successful Operation..... | 105 |
+| 8.4.7.3 | Unsuccessful Operation..... | 105 |
+| 8.4.7.4 | Abnormal Conditions..... | 105 |
+| 8.4.8 | Handover Report..... | 105 |
+| 8.4.8.1 | General..... | 105 |
+| 8.4.8.2 | Successful Operation..... | 106 |
+| 8.4.8.3 | Unsuccessful Operation..... | 106 |
+| 8.4.8.4 | Abnormal Conditions..... | 106 |
+| 8.4.9 | Mobility Settings Change..... | 107 |
+| 8.4.9.1 | General..... | 107 |
+| 8.4.9.2 | Successful Operation..... | 107 |
+| 8.4.9.3 | Unsuccessful Operation..... | 107 |
+| 8.4.9.4 | Abnormal Conditions..... | 108 |
+| 8.4.10 | Resource Status Reporting Initiation..... | 108 |
+| 8.4.10.1 | General..... | 108 |
+| 8.4.10.2 | Successful Operation..... | 108 |
+| 8.4.10.3 | Unsuccessful Operation..... | 109 |
+| 8.4.10.4 | Abnormal Conditions..... | 109 |
+| 8.4.11 | Resource Status Reporting..... | 110 |
+| 8.4.11.1 | General..... | 110 |
+| 8.4.11.2 | Successful Operation..... | 110 |
+| 8.4.11.3 | Unsuccessful Operation..... | 110 |
+| 8.4.11.4 | Abnormal Conditions..... | 110 |
+
+| | | |
+|----------|-------------------------------------------|-----|
+| 8.4.12 | Access And Mobility Indication..... | 110 |
+| 8.4.12.1 | General..... | 110 |
+| 8.4.12.2 | Successful Operation..... | 111 |
+| 8.4.12.3 | Abnormal Conditions..... | 111 |
+| 8.4.13 | Data Collection Reporting Initiation..... | 111 |
+| 8.4.13.1 | General..... | 111 |
+| 8.4.13.2 | Successful Operation..... | 111 |
+| 8.4.13.3 | Unsuccessful Operation..... | 113 |
+| 8.4.13.4 | Abnormal Conditions..... | 113 |
+| 8.4.14 | Data Collection Reporting..... | 114 |
+| 8.4.14.1 | General..... | 114 |
+| 8.4.14.2 | Successful Operation..... | 114 |
+| 8.4.14.3 | Unsuccessful Operation..... | 114 |
+| 8.4.14.4 | Abnormal Conditions..... | 114 |
+| 8.5 | IAB Procedures..... | 114 |
+| 8.5.1 | F1-C Traffic Transfer..... | 114 |
+| 8.5.1.1 | General..... | 114 |
+| 8.5.1.2 | Successful Operation..... | 115 |
+| 8.5.1.3 | Unsuccessful Operation..... | 115 |
+| 8.5.1.4 | Abnormal Conditions..... | 115 |
+| 8.5.2 | IAB Transport Migration Management..... | 115 |
+| 8.5.2.1 | General..... | 115 |
+| 8.5.2.2 | Successful Operation..... | 116 |
+| 8.5.2.3 | Unsuccessful Operation..... | 117 |
+| 8.5.2.4 | Abnormal Conditions..... | 117 |
+| 8.5.3 | IAB Transport Migration Modification..... | 117 |
+| 8.5.3.1 | General..... | 117 |
+| 8.5.3.2 | Successful Operation..... | 117 |
+| 8.5.3.3 | Unsuccessful Operation..... | 118 |
+| 8.5.3.4 | Abnormal Conditions..... | 118 |
+
+| | | |
+|----------|------------------------------------------------|-----|
+| 8.5.4 | IAB Resource Coordination..... | 118 |
+| 8.5.4.1 | General..... | 118 |
+| 8.5.4.2 | Successful Operation..... | 119 |
+| 8.5.4.3 | Unsuccessful Operation..... | 119 |
+| 8.5.4.4 | Abnormal Conditions..... | 119 |
+| 9 | Elements for XnAP Communication..... | 120 |
+| 9.0 | General..... | 120 |
+| 9.1 | Message Functional Defnition and Content..... | 120 |
+| 9.1.1 | Messages for Basic Mobility Procedures..... | 120 |
+| 9.1.1.1 | HANDOVER REQUEST..... | 120 |
+| 9.1.1.2 | HANDOVER REQUEST ACKNOWLEDGE..... | 124 |
+| 9.1.1.3 | HANDOVER PREPARATION FAILURE..... | 125 |
+| 9.1.1.4 | SN STATUS TRANSFER..... | 126 |
+| 9.1.1.5 | UE CONTEXT RELEASE..... | 126 |
+| 9.1.1.6 | HANDOVER CANCEL..... | 127 |
+| 9.1.1.7 | RAN PAGING..... | 127 |
+| 9.1.1.8 | RETRIEVE UE CONTEXT REQUEST..... | 128 |
+| 9.1.1.9 | RETRIEVE UE CONTEXT RESPONSE..... | 130 |
+| 9.1.1.10 | RETRIEVE UE CONTEXT FAILURE..... | 131 |
+| 9.1.1.11 | XN-U ADDRESS INDICATION..... | 132 |
+| 9.1.1.12 | HANDOVER SUCCESS..... | 133 |
+| 9.1.1.13 | CONDITIONAL HANDOVER CANCEL..... | 134 |
+| 9.1.1.14 | EARLY STATUS TRANSFER..... | 134 |
+| 9.1.1.15 | RAN MULTICAST GROUP PAGING..... | 136 |
+| 9.1.1.16 | RETRIEVE UE CONTEXT CONFIRM..... | 137 |
+| 9.1.1.17 | PARTIAL UE CONTEXT TRANSFER..... | 137 |
+| 9.1.1.18 | PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE..... | 137 |
+| 9.1.1.19 | PARTIAL UE CONTEXT TRANSFER FAILURE..... | 138 |
+| 9.1.2 | Messages for Dual Connectivity Procedures..... | 138 |
+| 9.1.2.1 | S-NODE ADDITION REQUEST..... | 138 |
+
+| | | |
+|----------|------------------------------------------------------|-----|
+| 9.1.2.2 | S-NODE ADDITION REQUEST ACKNOWLEDGE..... | 142 |
+| 9.1.2.3 | S-NODE ADDITION REQUEST REJECT..... | 145 |
+| 9.1.2.4 | S-NODE RECONFIGURATION COMPLETE..... | 145 |
+| 9.1.2.5 | S-NODE MODIFICATION REQUEST..... | 146 |
+| 9.1.2.6 | S-NODE MODIFICATION REQUEST ACKNOWLEDGE..... | 151 |
+| 9.1.2.7 | S-NODE MODIFICATION REQUEST REJECT..... | 154 |
+| 9.1.2.8 | S-NODE MODIFICATION REQUIRED..... | 154 |
+| 9.1.2.9 | S-NODE MODIFICATION CONFIRM..... | 156 |
+| 9.1.2.10 | S-NODE MODIFICATION REFUSE..... | 158 |
+| 9.1.2.11 | S-NODE CHANGE REQUIRED..... | 158 |
+| 9.1.2.12 | S-NODE CHANGE CONFIRM..... | 160 |
+| 9.1.2.13 | S-NODE CHANGE REFUSE..... | 161 |
+| 9.1.2.14 | S-NODE RELEASE REQUEST..... | 162 |
+| 9.1.2.15 | S-NODE RELEASE REQUEST ACKNOWLEDGE..... | 162 |
+| 9.1.2.16 | S-NODE RELEASE REJECT..... | 163 |
+| 9.1.2.17 | S-NODE RELEASE REQUIRED..... | 163 |
+| 9.1.2.18 | S-NODE RELEASE CONFIRM..... | 164 |
+| 9.1.2.19 | S-NODE COUNTER CHECK REQUEST..... | 164 |
+| 9.1.2.20 | RRC TRANSFER..... | 165 |
+| 9.1.2.21 | NOTIFICATION CONTROL INDICATION..... | 168 |
+| 9.1.2.22 | ACTIVITY NOTIFICATION..... | 168 |
+| 9.1.2.23 | E-UTRA – NR CELL RESOURCE COORDINATION REQUEST..... | 169 |
+| 9.1.2.24 | E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE..... | 170 |
+| 9.1.2.25 | SECONDARY RAT DATA USAGE REPORT..... | 171 |
+| 9.1.2.26 | TRACE START..... | 172 |
+| 9.1.2.27 | DEACTIVATE TRACE..... | 172 |
+| 9.1.2.28 | CELL TRAFFIC TRACE..... | 172 |
+| 9.1.2.29 | SCG FAILURE INFORMATION REPORT..... | 173 |
+| 9.1.2.30 | SCG FAILURE TRANSFER..... | 174 |
+| 9.1.2.31 | CONDITIONAL PSCELL CHANGE CANCEL..... | 174 |
+
+| | | |
+|----------|---------------------------------------------------|-----|
+| 9.1.2.32 | RACH INDICATION..... | 175 |
+| 9.1.3 | Messages for Global Procedures..... | 175 |
+| 9.1.3.1 | XN SETUP REQUEST..... | 175 |
+| 9.1.3.2 | XN SETUP RESPONSE..... | 176 |
+| 9.1.3.3 | XN SETUP FAILURE..... | 178 |
+| 9.1.3.4 | NG-RAN NODE CONFIGURATION UPDATE..... | 178 |
+| 9.1.3.5 | NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE..... | 181 |
+| 9.1.3.6 | NG-RAN NODE CONFIGURATION UPDATE FAILURE..... | 183 |
+| 9.1.3.7 | CELL ACTIVATION REQUEST..... | 183 |
+| 9.1.3.8 | CELL ACTIVATION RESPONSE..... | 184 |
+| 9.1.3.9 | CELL ACTIVATION FAILURE..... | 185 |
+| 9.1.3.10 | RESET REQUEST..... | 185 |
+| 9.1.3.11 | RESET RESPONSE..... | 186 |
+| 9.1.3.12 | ERROR INDICATION..... | 186 |
+| 9.1.3.13 | XN REMOVAL REQUEST..... | 187 |
+| 9.1.3.14 | XN REMOVAL RESPONSE..... | 187 |
+| 9.1.3.15 | XN REMOVAL FAILURE..... | 187 |
+| 9.1.3.16 | FAILURE INDICATION..... | 188 |
+| 9.1.3.17 | HANDOVER REPORT..... | 189 |
+| 9.1.3.18 | RESOURCE STATUS REQUEST..... | 190 |
+| 9.1.3.19 | RESOURCE STATUS RESPONSE..... | 192 |
+| 9.1.3.20 | RESOURCE STATUS FAILURE..... | 192 |
+| 9.1.3.21 | RESOURCE STATUS UPDATE..... | 193 |
+| 9.1.3.22 | MOBILITY CHANGE REQUEST..... | 195 |
+| 9.1.3.23 | MOBILITY CHANGE ACKNOWLEDGE..... | 195 |
+| 9.1.3.24 | MOBILITY CHANGE FAILURE..... | 195 |
+| 9.1.3.25 | ACCESS AND MOBILITY INDICATION..... | 196 |
+| 9.1.3.26 | DATA COLLECTION REQUEST..... | 197 |
+| 9.1.3.27 | DATA COLLECTION RESPONSE..... | 199 |
+| 9.1.3.28 | DATA COLLECTION FAILURE..... | 200 |
+
+| | | |
+|----------|----------------------------------------------------------------------|-----|
+| 9.1.3.29 | DATA COLLECTION UPDATE..... | 201 |
+| 9.1.4 | Messages for IAB Procedures..... | 202 |
+| 9.1.4.1 | FI-C TRAFFIC TRANSFER..... | 202 |
+| 9.1.4.2 | IAB TRANSPORT MIGRATION MANAGEMENT REQUEST..... | 202 |
+| 9.1.4.3 | IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE..... | 204 |
+| 9.1.4.3a | IAB TRANSPORT MIGRATION MANAGEMENT REJECT..... | 205 |
+| 9.1.4.4 | IAB TRANSPORT MIGRATION MODIFICATION REQUEST..... | 205 |
+| 9.1.4.5 | IAB TRANSPORT MIGRATION MODIFICATION RESPONSE..... | 206 |
+| 9.1.4.6 | IAB RESOURCE COORDINATION REQUEST..... | 207 |
+| 9.1.4.7 | IAB RESOURCE COORDINATION RESPONSE..... | 208 |
+| 9.2 | Information Element definitions..... | 209 |
+| 9.2.0 | General..... | 209 |
+| 9.2.1 | Container and List IE definitions..... | 209 |
+| 9.2.1.1 | PDU Session Resources To Be Setup List..... | 209 |
+| 9.2.1.2 | PDU Session Resources Admitted List..... | 211 |
+| 9.2.1.3 | PDU Session Resources Not Admitted List..... | 212 |
+| 9.2.1.4 | QoS Flow List with Cause..... | 212 |
+| 9.2.1.4a | QoS Flow List..... | 213 |
+| 9.2.1.5 | PDU Session Resource Setup Info – SN terminated..... | 213 |
+| 9.2.1.6 | PDU Session Resource Setup Response Info – SN terminated..... | 214 |
+| 9.2.1.7 | PDU Session Resource Setup Info – MN terminated..... | 216 |
+| 9.2.1.8 | PDU Session Resource Setup Response Info – MN terminated..... | 218 |
+| 9.2.1.9 | PDU Session Resource Modification Info – SN terminated..... | 219 |
+| 9.2.1.10 | PDU Session Resource Modification Response Info – SN terminated..... | 222 |
+| 9.2.1.11 | PDU Session Resource Modification Info – MN terminated..... | 225 |
+| 9.2.1.12 | PDU Session Resource Modification Response Info – MN terminated..... | 228 |
+| 9.2.1.13 | UE Context Information – Retrieve UE Context Response..... | 229 |
+| 9.2.1.14 | DRBs Subject To Status Transfer List..... | 231 |
+| 9.2.1.15 | DRB to QoS Flow Mapping List..... | 233 |
+| 9.2.1.16 | Data Forwarding Info from target NG-RAN node..... | 233 |
+
+| | | |
+|----------|---------------------------------------------------------------------------|-----|
+| 9.2.1.17 | Data Forwarding and Offloading Info from source NG-RAN node..... | 234 |
+| 9.2.1.18 | PDU Session Resource Change Required Info – SN terminated..... | 235 |
+| 9.2.1.19 | PDU Session Resource Change Confirm Info – SN terminated..... | 235 |
+| 9.2.1.20 | PDU Session Resource Modification Required Info – SN terminated..... | 235 |
+| 9.2.1.21 | PDU Session Resource Modification Confirm Info – SN terminated..... | 238 |
+| 9.2.1.22 | PDU Session Resource Modification Required Info – MN terminated..... | 240 |
+| 9.2.1.23 | PDU Session Resource Modification Confirm Info – MN terminated..... | 241 |
+| 9.2.1.24 | PDU Session List with data forwarding request info..... | 241 |
+| 9.2.1.25 | PDU Session List with data forwarding info from the target node..... | 241 |
+| 9.2.1.26 | PDU Session List with Cause..... | 241 |
+| 9.2.1.27 | PDU Session List..... | 242 |
+| 9.2.1.28 | DRB List with Cause..... | 242 |
+| 9.2.1.29 | DRB List..... | 242 |
+| 9.2.1.30 | PDU Session Resource Setup Complete Info – SN terminated..... | 243 |
+| 9.2.1.31 | Secondary Data Forwarding Info from target NG-RAN node List..... | 243 |
+| 9.2.1.32 | Additional UL NG-U UP TNL Information at UPF List..... | 243 |
+| 9.2.1.33 | DAPS Request Information..... | 244 |
+| 9.2.1.34 | DAPS Response Information..... | 244 |
+| 9.2.1.35 | Data Forwarding Info from target E-UTRAN node..... | 244 |
+| 9.2.1.36 | MBS Session Information List..... | 245 |
+| 9.2.1.37 | MBS Session Associated Information..... | 245 |
+| 9.2.1.38 | MBS Session Information Response List..... | 246 |
+| 9.2.1.39 | MBS Mapping and Data Forwarding Request Info from source NG-RAN node..... | 246 |
+| 9.2.1.40 | MBS Data Forwarding Response Info from target NG-RAN node..... | 247 |
+| 9.2.2 | NG-RAN Node and Cell Configuration related IE definitions..... | 247 |
+| 9.2.2.1 | Global gNB ID..... | 247 |
+| 9.2.2.2 | Global ng-eNB ID..... | 247 |
+| 9.2.2.3 | Global NG-RAN Node ID..... | 248 |
+| 9.2.2.4 | PLMN Identity..... | 248 |
+| 9.2.2.5 | TAC..... | 248 |
+
+| | | |
+|----------|-----------------------------------------------|-----|
+| 9.2.2.6 | RAN Area Code..... | 248 |
+| 9.2.2.7 | NR CGI..... | 249 |
+| 9.2.2.8 | E-UTRA CGI..... | 249 |
+| 9.2.2.9 | NG-RAN Cell Identity..... | 249 |
+| 9.2.2.10 | NG-RAN Cell PCI..... | 249 |
+| 9.2.2.11 | Served Cell Information NR..... | 249 |
+| 9.2.2.12 | Served Cell Information E-UTRA..... | 256 |
+| 9.2.2.13 | Neighbour Information NR..... | 259 |
+| 9.2.2.14 | Neighbour Information E-UTRA..... | 260 |
+| 9.2.2.15 | Served Cells To Update NR..... | 260 |
+| 9.2.2.16 | Served Cells to Update E-UTRA..... | 261 |
+| 9.2.2.17 | Cell Assistance Information NR..... | 262 |
+| 9.2.2.18 | SUL Information..... | 262 |
+| 9.2.2.19 | NR Frequency Info..... | 263 |
+| 9.2.2.20 | NR Transmission Bandwidth..... | 264 |
+| 9.2.2.21 | E-UTRA ARFCN..... | 265 |
+| 9.2.2.22 | E-UTRA Transmission Bandwidth..... | 265 |
+| 9.2.2.23 | Number of Antenna Ports E-UTRA..... | 265 |
+| 9.2.2.24 | E-UTRA Multiband Info List..... | 265 |
+| 9.2.2.25 | E-UTRA PRACH Configuration..... | 266 |
+| 9.2.2.26 | MBSFN Subframe Allocation E-UTRA..... | 266 |
+| 9.2.2.27 | Global NG-RAN Cell Identity..... | 266 |
+| 9.2.2.28 | Connectivity Support..... | 266 |
+| 9.2.2.29 | Protected E-UTRA Resource Indication..... | 267 |
+| 9.2.2.30 | Data Traffic Resource Indication..... | 268 |
+| 9.2.2.31 | Data Traffic Resources..... | 269 |
+| 9.2.2.32 | Reserved Subframe Pattern..... | 269 |
+| 9.2.2.33 | MR-DC Resource Coordination Information..... | 270 |
+| 9.2.2.34 | E-UTRA Resource Coordination Information..... | 270 |
+| 9.2.2.35 | NR Resource Coordination Information..... | 271 |
+
+| | | |
+|-----------|------------------------------------------------------|-----|
+| 9.2.2.36 | E-UTRA Coordination Assistance Information..... | 273 |
+| 9.2.2.37 | NR Coordination Assistance Information..... | 273 |
+| 9.2.2.38 | NE-DC TDM Pattern..... | 273 |
+| 9.2.2.39 | Interface Instance Indication..... | 273 |
+| 9.2.2.39a | Configured TAC Indication..... | 274 |
+| 9.2.2.40 | Intended TDD DL-UL Configuration NR..... | 274 |
+| 9.2.2.41 | Cell and Capacity Assistance Information NR..... | 275 |
+| 9.2.2.42 | Cell and Capacity Assistance Information E-UTRA..... | 275 |
+| 9.2.2.43 | Cell Assistance Information E-UTRA..... | 275 |
+| 9.2.2.44 | Maximum Cell List Size..... | 276 |
+| 9.2.2.45 | Message Oversize Notification..... | 276 |
+| 9.2.2.46 | Partial List Indicator..... | 276 |
+| 9.2.2.47 | Offset of NB-IoT Channel Number to EARFCN..... | 276 |
+| 9.2.2.48 | NB-IoT UL DL Alignment Offset..... | 277 |
+| 9.2.2.49 | TNL Capacity Indicator..... | 277 |
+| 9.2.2.50 | Radio Resource Status..... | 277 |
+| 9.2.2.51 | Composite Available Capacity Group..... | 280 |
+| 9.2.2.52 | Composite Available Capacity..... | 280 |
+| 9.2.2.53 | Cell Capacity Class Value..... | 280 |
+| 9.2.2.54 | Capacity Value..... | 281 |
+| 9.2.2.55 | Slice Available Capacity..... | 281 |
+| 9.2.2.56 | RRC Connections..... | 282 |
+| 9.2.2.57 | Number of RRC Connections..... | 282 |
+| 9.2.2.58 | Available RRC Connection Capacity Value..... | 282 |
+| 9.2.2.59 | UE RLF Report..... | 282 |
+| 9.2.2.60 | Mobility Parameters Information..... | 283 |
+| 9.2.2.61 | Mobility Parameters Modification Range..... | 283 |
+| 9.2.2.62 | Number of Active UEs..... | 283 |
+| 9.2.2.63 | NR Carrier List..... | 284 |
+| 9.2.2.64 | SSB Positions In Burst..... | 284 |
+
+| | | |
+|----------|-------------------------------------------------|-----|
+| 9.2.2.65 | NID..... | 285 |
+| 9.2.2.66 | CAG-Identifier..... | 285 |
+| 9.2.2.67 | Broadcast NID List..... | 285 |
+| 9.2.2.68 | Broadcast SNPN ID List..... | 285 |
+| 9.2.2.69 | Broadcast CAG-Identifier List..... | 285 |
+| 9.2.2.70 | Broadcast PNI-NPN ID Information..... | 286 |
+| 9.2.2.71 | NPN Broadcast Information..... | 286 |
+| 9.2.2.72 | NPN Support..... | 286 |
+| 9.2.2.73 | Global Cell Identity..... | 286 |
+| 9.2.2.74 | NPRACH Configuration..... | 287 |
+| 9.2.2.75 | SFN Offset..... | 288 |
+| 9.2.2.76 | CHO Configuration..... | 288 |
+| 9.2.2.77 | SSB Offset Information..... | 289 |
+| 9.2.2.78 | SSB Offset Modification Range..... | 289 |
+| 9.2.2.79 | Multiplexing Info..... | 289 |
+| 9.2.2.80 | Traffic Index..... | 290 |
+| 9.2.2.81 | Traffic Profile..... | 290 |
+| 9.2.2.82 | F1-Terminating Topology BH Information..... | 290 |
+| 9.2.2.83 | Non-F1-terminating Topology BH Information..... | 291 |
+| 9.2.2.84 | Traffic To Be Released Information..... | 292 |
+| 9.2.2.85 | IAB TNL Address Request..... | 292 |
+| 9.2.2.86 | IAB TNL Address Response..... | 293 |
+| 9.2.2.87 | BAP Routing ID..... | 293 |
+| 9.2.2.88 | BH RLC Channel ID..... | 293 |
+| 9.2.2.89 | BAP Address..... | 293 |
+| 9.2.2.90 | BAP Path ID..... | 293 |
+| 9.2.2.91 | IAB QoS mapping information..... | 294 |
+| 9.2.2.92 | IAB TNL Address..... | 294 |
+| 9.2.2.93 | IAB TNL Addresses Requested..... | 294 |
+| 9.2.2.94 | IAB Cell Information..... | 294 |
+
+| | | |
+|-----------|-----------------------------------------|-----|
+| 9.2.2.95 | gNB-DU Cell Resource Configuration..... | 296 |
+| 9.2.2.96 | IAB STC Info..... | 298 |
+| 9.2.2.97 | RB Set Configuration..... | 298 |
+| 9.2.2.98 | IAB TNL Address Exception..... | 299 |
+| 9.2.2.99 | BH Info List..... | 299 |
+| 9.2.2.100 | Non-UP traffic..... | 300 |
+| 9.2.2.101 | Local NG-RAN Node Identifier..... | 300 |
+| 9.2.2.102 | Served Cell Specific Info Request..... | 301 |
+| 9.2.2.103 | CPAC Configuration..... | 302 |
+| 9.2.2.104 | Radio Resource Status NR-U..... | 302 |
+| 9.2.2.105 | Mobile IAB Authorization Status..... | 302 |
+| 9.2.2.106 | Mobile IAB Cell..... | 303 |
+| 9.2.3 | General IE definitions..... | 303 |
+| 9.2.3.1 | Message Type..... | 303 |
+| 9.2.3.2 | Cause..... | 303 |
+| 9.2.3.3 | Criticality Diagnostics..... | 309 |
+| 9.2.3.4 | Bit Rate..... | 310 |
+| 9.2.3.5 | QoS Flow Level QoS Parameters..... | 310 |
+| 9.2.3.6 | GBR QoS Flow Information..... | 311 |
+| 9.2.3.7 | Allocation and Retention Priority..... | 312 |
+| 9.2.3.8 | Non dynamic 5QI Descriptor..... | 313 |
+| 9.2.3.9 | Dynamic 5QI Descriptor..... | 314 |
+| 9.2.3.10 | QoS Flow Identifier..... | 315 |
+| 9.2.3.11 | Packet Loss Rate..... | 315 |
+| 9.2.3.12 | Packet Delay Budget..... | 315 |
+| 9.2.3.13 | Packet Error Rate..... | 315 |
+| 9.2.3.14 | Averaging Window..... | 315 |
+| 9.2.3.15 | Maximum Data Burst Volume..... | 316 |
+| 9.2.3.16 | NG-RAN node UE XnAP ID..... | 316 |
+| 9.2.3.17 | UE Aggregate Maximum Bit Rate..... | 316 |
+
+| | | |
+|----------|------------------------------------------------|-----|
+| 9.2.3.18 | PDU Session ID..... | 316 |
+| 9.2.3.19 | PDU Session Type..... | 316 |
+| 9.2.3.20 | TAI Support List..... | 317 |
+| 9.2.3.21 | S-NSSAI..... | 317 |
+| 9.2.3.22 | Slice Support List..... | 317 |
+| 9.2.3.23 | Index to RAT/Frequency Selection Priority..... | 318 |
+| 9.2.3.24 | GUAMI..... | 318 |
+| 9.2.3.25 | Target Cell Global ID..... | 318 |
+| 9.2.3.26 | AMF UE NGAP ID..... | 318 |
+| 9.2.3.27 | SCG Configuration Query..... | 319 |
+| 9.2.3.28 | RLC Mode..... | 319 |
+| 9.2.3.29 | Transport Layer Address..... | 319 |
+| 9.2.3.30 | UP Transport Layer Information..... | 319 |
+| 9.2.3.31 | CP Transport Layer Information..... | 320 |
+| 9.2.3.32 | Masked IMEISV..... | 320 |
+| 9.2.3.33 | DRB ID..... | 320 |
+| 9.2.3.34 | DL Forwarding..... | 320 |
+| 9.2.3.35 | Data Forwarding Accepted..... | 320 |
+| 9.2.3.36 | COUNT Value for PDCP SN Length 12..... | 321 |
+| 9.2.3.37 | COUNT Value for PDCP SN Length 18..... | 321 |
+| 9.2.3.38 | RAN Paging Area..... | 321 |
+| 9.2.3.39 | RAN Area ID..... | 321 |
+| 9.2.3.40 | UE Context ID..... | 322 |
+| 9.2.3.41 | Assistance Data for RAN Paging..... | 322 |
+| 9.2.3.42 | RAN Paging Attempt Information..... | 322 |
+| 9.2.3.43 | UE RAN Paging Identity..... | 323 |
+| 9.2.3.44 | Paging Priority..... | 323 |
+| 9.2.3.45 | Delivery Status..... | 323 |
+| 9.2.3.46 | I-RNTI..... | 323 |
+| 9.2.3.47 | Location Reporting Information..... | 324 |
+
+| | | |
+|----------|----------------------------------------------------|-----|
+| 9.2.3.48 | Area of Interest Information..... | 324 |
+| 9.2.3.49 | UE Security Capabilities..... | 325 |
+| 9.2.3.50 | AS Security Information..... | 326 |
+| 9.2.3.51 | S-NG-RAN node Security Key..... | 326 |
+| 9.2.3.52 | Security Indication..... | 327 |
+| 9.2.3.53 | Mobility Restriction List..... | 327 |
+| 9.2.3.54 | Xn Benefit Value..... | 329 |
+| 9.2.3.55 | Trace Activation..... | 329 |
+| 9.2.3.56 | Time To Wait..... | 330 |
+| 9.2.3.57 | QoS Flow Notification Control Indication Info..... | 330 |
+| 9.2.3.58 | Request Reporting Reference ID..... | 331 |
+| 9.2.3.59 | User plane traffic activity report..... | 331 |
+| 9.2.3.60 | Lower Layer presence status change..... | 331 |
+| 9.2.3.61 | RRC Resume Cause..... | 331 |
+| 9.2.3.62 | Priority Level..... | 332 |
+| 9.2.3.63 | PDCP SN Length..... | 332 |
+| 9.2.3.64 | UE History Information..... | 332 |
+| 9.2.3.65 | Last Visited Cell Information..... | 332 |
+| 9.2.3.66 | Paging DRX..... | 333 |
+| 9.2.3.67 | Security Result..... | 333 |
+| 9.2.3.68 | UE Context Kept Indicator..... | 333 |
+| 9.2.3.69 | PDU Session Aggregate Maximum Bit Rate..... | 333 |
+| 9.2.3.70 | LCID..... | 334 |
+| 9.2.3.71 | Duplication Activation..... | 334 |
+| 9.2.3.72 | RRC Config Indication..... | 334 |
+| 9.2.3.73 | Maximum Integrity Protected Data Rate..... | 334 |
+| 9.2.3.74 | PDCP Change Indication..... | 335 |
+| 9.2.3.75 | UL Configuration..... | 335 |
+| 9.2.3.76 | UP Transport Parameters..... | 335 |
+| 9.2.3.77 | Desired Activity Notification Level..... | 336 |
+
+| | | |
+|-----------|--------------------------------------------------|-----|
+| 9.2.3.78 | Number of DRB IDs..... | 336 |
+| 9.2.3.79 | QoS Flow Mapping Indication..... | 336 |
+| 9.2.3.80 | RLC Status..... | 336 |
+| 9.2.3.81 | Expected UE Behaviour..... | 336 |
+| 9.2.3.82 | Expected UE Activity Behaviour..... | 337 |
+| 9.2.3.83 | AMF Region Information..... | 337 |
+| 9.2.3.84 | TNL Association Usage..... | 338 |
+| 9.2.3.85 | Network Instance..... | 338 |
+| 9.2.3.86 | PDCP Duplication Configuration..... | 338 |
+| 9.2.3.87 | Secondary RAT Usage Information..... | 338 |
+| 9.2.3.88 | Volume Timed Report List..... | 339 |
+| 9.2.3.89 | Maximum IP Rate..... | 339 |
+| 9.2.3.90 | UL Forwarding..... | 340 |
+| 9.2.3.91 | UE Radio Capability for Paging..... | 340 |
+| 9.2.3.92 | Common Network Instance..... | 340 |
+| 9.2.3.93 | Default DRB Allowed..... | 340 |
+| 9.2.3.94 | Split Session Indicator..... | 340 |
+| 9.2.3.95 | UL Forwarding Proposal..... | 340 |
+| 9.2.3.96 | TNL Configuration Info..... | 341 |
+| 9.2.3.97 | NG-RAN Trace ID..... | 341 |
+| 9.2.3.98 | Non-GBR Resources Offered..... | 342 |
+| 9.2.3.99 | Extended RAT Restriction Information..... | 342 |
+| 9.2.3.100 | 5GC Mobility Restriction List Container..... | 342 |
+| 9.2.3.101 | Maximum Number of CHO Preparations..... | 342 |
+| 9.2.3.102 | Alternative QoS Parameters Set List..... | 343 |
+| 9.2.3.103 | Alternative QoS Parameters Set Index..... | 343 |
+| 9.2.3.104 | Alternative QoS Parameters Set Notify Index..... | 343 |
+| 9.2.3.105 | NR V2X Services Authorized..... | 343 |
+| 9.2.3.106 | LTE V2X Services Authorized..... | 344 |
+| 9.2.3.107 | NR UE Sidelink Aggregate Maximum Bit Rate..... | 344 |
+
+| | | |
+|-----------|-------------------------------------------------|-----|
+| 9.2.3.108 | LTE UE Sidelink Aggregate Maximum Bit Rate..... | 344 |
+| 9.2.3.109 | PC5 QoS Parameters..... | 344 |
+| 9.2.3.110 | UE History Information from the UE..... | 345 |
+| 9.2.3.111 | RLC Duplication Information..... | 345 |
+| 9.2.3.112 | Redundant PDU Session Information..... | 345 |
+| 9.2.3.113 | Extended Packet Delay Budget..... | 346 |
+| 9.2.3.114 | TSC Traffic Characteristics..... | 346 |
+| 9.2.3.115 | TSC Assistance Information..... | 346 |
+| 9.2.3.116 | Periodicity..... | 346 |
+| 9.2.3.117 | Burst Arrival Time..... | 347 |
+| 9.2.3.118 | Redundant QoS Flow Indicator..... | 347 |
+| 9.2.3.119 | NPN Mobility Information..... | 347 |
+| 9.2.3.120 | Allowed PNI-NPN ID List..... | 348 |
+| 9.2.3.121 | NPN Paging Assistance Information..... | 348 |
+| 9.2.3.122 | Void..... | 348 |
+| 9.2.3.123 | PNI-NPN Restricted Information..... | 348 |
+| 9.2.3.124 | URI..... | 349 |
+| 9.2.3.125 | MDT Configuration..... | 349 |
+| 9.2.3.126 | MDT Configuration-NR..... | 349 |
+| 9.2.3.127 | MDT Configuration-EUTRA..... | 353 |
+| 9.2.3.128 | M1 Configuration..... | 353 |
+| 9.2.3.129 | M4 Configuration..... | 355 |
+| 9.2.3.130 | M5 Configuration..... | 355 |
+| 9.2.3.131 | M6 Configuration..... | 356 |
+| 9.2.3.132 | M7 Configuration..... | 356 |
+| 9.2.3.133 | MDT PLMN List..... | 357 |
+| 9.2.3.134 | Bluetooth Measurement Configuration..... | 357 |
+| 9.2.3.135 | WLAN Measurement Configuration..... | 357 |
+| 9.2.3.136 | Sensor Measurement Configuration..... | 358 |
+| 9.2.3.137 | Logged Event Trigger Config..... | 358 |
+
+| | | |
+|------------|-----------------------------------------------------------------|-----|
+| 9.2.3.138 | UE Radio Capability ID..... | 359 |
+| 9.2.3.139 | Extended Slice Support List..... | 359 |
+| 9.2.3.140 | Area Scope of Neighbour Cells..... | 359 |
+| 9.2.3.141 | Extended UE Identity Index Value..... | 359 |
+| 9.2.3.142 | E-UTRA Paging eDRX Information..... | 360 |
+| 9.2.3.143 | UE Specific DRX..... | 360 |
+| 9.2.3.144 | QoS Mapping Information..... | 360 |
+| 9.2.3.144a | Hashed UE Identity Index Value..... | 360 |
+| 9.2.3.145 | MRB ID..... | 360 |
+| 9.2.3.146 | MBS Session ID..... | 361 |
+| 9.2.3.147 | MRB Progress Information..... | 361 |
+| 9.2.3.148 | MBS Area Session ID..... | 361 |
+| 9.2.3.149 | MBS Service Area information..... | 361 |
+| 9.2.3.150 | MBS Service Area..... | 362 |
+| 9.2.3.151 | SCG UE History Information..... | 362 |
+| 9.2.3.152 | Survival Time..... | 362 |
+| 9.2.3.153 | Time Synchronisation Assistance Information..... | 362 |
+| 9.2.3.154 | SCG Activation Request..... | 363 |
+| 9.2.3.155 | SCG Activation Status..... | 363 |
+| 9.2.3.156 | QMC Configuration Information..... | 363 |
+| 9.2.3.157 | UE Application Layer Measurement Configuration Information..... | 363 |
+| 9.2.3.158 | Available RAN Visible QoE Metrics..... | 366 |
+| 9.2.3.159 | 5G ProSe Authorized..... | 366 |
+| 9.2.3.160 | 5G ProSe PC5 QoS Parameters..... | 367 |
+| 9.2.3.161 | NR Paging eDRX Information..... | 367 |
+| 9.2.3.162 | NR Paging eDRX Information for RRC INACTIVE..... | 368 |
+| 9.2.3.163 | SDT Support Request..... | 368 |
+| 9.2.3.164 | Partial UE Context Information for SDT..... | 368 |
+| 9.2.3.165 | SRB ID..... | 369 |
+| 9.2.3.166 | PEIPS Assistance Information..... | 370 |
+
+| | | |
+|-----------|-------------------------------------------------------|-----|
+| 9.2.3.167 | UE Slice Maximum Bit Rate List..... | 370 |
+| 9.2.3.168 | Positioning Information..... | 370 |
+| 9.2.3.169 | MDT PLMN Modification List..... | 370 |
+| 9.2.3.170 | TAI NSAG Support List..... | 371 |
+| 9.2.3.171 | Excess Packet Delay Threshold Configuration..... | 371 |
+| 9.2.3.172 | MT-SDT Information..... | 371 |
+| 9.2.3.173 | Partial UE Context Information for Positioning..... | 372 |
+| 9.2.3.174 | DL LBT Failure Information..... | 372 |
+| 9.2.3.175 | Aerial UE Subscription Information..... | 372 |
+| 9.2.3.176 | NR A2X Services Authorized..... | 372 |
+| 9.2.3.177 | LTE A2X Services Authorized..... | 372 |
+| 9.2.3.178 | A2X PC5 QoS Parameters..... | 373 |
+| 9.2.3.179 | UE Performance..... | 373 |
+| 9.2.3.180 | Cell Based UE Trajectory Prediction..... | 373 |
+| 9.2.3.181 | Predicted Trajectory Cell Information..... | 374 |
+| 9.2.3.182 | Measured UE Trajectory..... | 374 |
+| 9.2.3.183 | Measured Trajectory Cell Information..... | 375 |
+| 9.2.3.184 | Data Collection ID..... | 375 |
+| 9.2.3.185 | UE Trajectory Collection Configuration..... | 375 |
+| 9.2.3.186 | UE Performance Collection Configuration..... | 375 |
+| 9.2.3.187 | Average Packet Delay..... | 375 |
+| 9.2.3.188 | Candidate Relay UE Info List..... | 376 |
+| 9.2.3.189 | Clock Quality Reporting Control Information..... | 376 |
+| 9.2.3.190 | Clock Quality Acceptance Criteria..... | 376 |
+| 9.2.3.191 | PNI-NPN Area Scope of MDT..... | 377 |
+| 9.2.3.192 | S-CPAC Request Information..... | 377 |
+| 9.2.3.193 | S-CPAC Security Configurations List..... | 378 |
+| 9.2.3.194 | Complete Configuration Indicator..... | 378 |
+| 9.2.3.195 | NR Paging Long eDRX Information for RRC INACTIVE..... | 378 |
+| 9.2.3.196 | MBS Assistance Information..... | 378 |
+
+| | | |
+|-------------------------------|-------------------------------------------------------------------|------------|
+| 9.2.3.197 | QMC Coordination Request..... | 379 |
+| 9.2.3.198 | QMC Coordination Response..... | 380 |
+| 9.2.3.199 | SN-related QMC Information at MN..... | 381 |
+| 9.2.3.200 | QoE and RVQoE Reporting Paths..... | 382 |
+| 9.2.3.201 | RAN Visible QoE Configuration..... | 382 |
+| 9.2.3.202 | CHO-CPAC Information..... | 382 |
+| 9.2.3.203 | PDU Set QoS Parameters..... | 383 |
+| 9.2.3.204 | N6 Jitter Information..... | 383 |
+| 9.2.3.205 | ECN Marking or Congestion Information Reporting Request..... | 383 |
+| 9.2.3.206 | PDU Set based Handling Indicator..... | 384 |
+| 9.2.3.207 | TAI Slice Unavailable Cell List..... | 384 |
+| 9.3 | Message and Information Element Abstract Syntax (with ASN.1)..... | 385 |
+| 9.3.1 | General..... | 385 |
+| 9.3.2 | Usage of Private Message Mechanism for Non-standard Use..... | 385 |
+| 9.3.3 | Elementary Procedure Definitions..... | 386 |
+| 9.3.4 | PDU Definitions..... | 399 |
+| 9.3.5 | Information Element definitions..... | 467 |
+| 9.3.6 | Common definitions..... | 637 |
+| 9.3.7 | Constant definitions..... | 638 |
+| 9.3.8 | Container definitions..... | 651 |
+| 9.4 | Message transfer syntax..... | 656 |
+| 9.5 | Timers..... | 656 |
+| 10 | Handling of unknown, unforeseen and erroneous protocol data..... | 656 |
+| <b>Annex A (informative):</b> | <b>Change history.....</b> | <b>657</b> |
+
+---
+
+## 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
+
+The present document specifies the radio network layer signalling procedures of the control plane between NG-RAN nodes in NG-RAN. XnAP supports the functions of the Xn interface by signalling procedures defined in this document. XnAP is developed in accordance to the general principles stated in TS 38.401 [2] and TS 38.420 [3].
+
+---
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.401: "NG-RAN; Architecture Description".
+- [3] 3GPP TS 38.420: "NG-RAN; Xn General Aspects and Principles".
+- [4] 3GPP TS 38.422: "NG-RAN; Xn Signalling Transport".
+- [5] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP) ".
+- [6] 3GPP TS 25.921: "Guidelines and principles for protocol description and error handling".
+- [7] 3GPP TS 23.501: "System Architecture for the 5G System".
+- [8] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
+- [9] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
+- [10] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) Protocol specification".
+- [11] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification".
+- [12] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
+- [13] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [14] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".
+- [15] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER) ".
+- [16] ITU-T Recommendation X.680 (2002-07): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+
+- [17] ITU-T Recommendation X.681 (2002-07): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification".
+- [18] 3GPP TS 29.281: "General Packet Radio Service (GPRS); Tunnelling Protocol User Plane (GTPv1-U)".
+- [19] 3GPP TS 38.424: "NG-RAN; Xn data transport".
+- [20] 3GPP TS 38.414: "NG-RAN; NG data transport".
+- [21] 3GPP TS 38.412: "NG-RAN; NG Signalling Transport".
+- [22] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [23] 3GPP TS 32.422: "Trace control and configuration management".
+- [24] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".
+- [25] 3GPP TS 36.104: "Base Station (BS) radio transmission and reception ".
+- [26] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation".
+- [27] 3GPP TS 36.101: "User Equipment (UE) radio transmission and reception".
+- [28] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
+- [29] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
+- [30] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
+- [31] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
+- [32] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".
+- [33] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state".
+- [34] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
+- [35] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
+- [36] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
+- [37] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification".
+- [38] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
+- [39] 3GPP TS 38.211: "NR; Physical channels and modulation".
+- [40] 3GPP TS 38.213: "NR; Physical layer procedures for control".
+- [41] 3GPP TS 38.473: "NG-RAN; F1 application protocol (F1AP)".
+- [42] 3GPP TS 38.314: "NR; Layer 2 measurements".
+- [43] 3GPP TS 37.320: " Radio measurement collection for Minimization of Drive Tests (MDT),"
+
+- [44] 3GPP TS 36.423: " Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP)".
+- [45] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes; Stage 3".
+- [46] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
+- [47] 3GPP TS 26.247: "“Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)”".
+- [48] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
+- [49] 3GPP TS 38.455: "NG-RAN; NR Positioning Protocol A (NRPPa)".
+- [50] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [51] 3GPP TS 37.213: "NR; Physical layer procedures for shared spectrum channel access".
+- [52] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [53] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
+- [54] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications".
+- [55] 3GPP TS 28.405: "Telecommunication management; Quality of Experience (QoE) measurement collection; Control and configuration".
+- [56] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
+
+---
+
+## 3 Definitions, symbols and abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**CAG Cell:** As defined in TS 38.300 [9].
+
+**Conditional Handover:** As defined in TS 38.300 [9].
+
+**Conditional PSCell Change:** As defined in TS 37.340 [8].
+
+**DAPS Handover:** As defined in TS 38.300 [9].
+
+**Elementary Procedure:** XnAP protocol consists of Elementary Procedures (EPs). An XnAP Elementary Procedure is a unit of interaction between two NG-RAN nodes. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:
+
+- **Class 1:** Elementary Procedures with response (success or failure),
+- **Class 2:** Elementary Procedures without response.
+
+**F1-terminating IAB-donor:** as defined in TS 38.401 [2].
+
+**Immediate Handover:** Used in the context of Conditional Handover, to refer to a handover that is executed immediately after the UE receives the Handover Command.
+
+**MBS Session Resource:** As defined in TS 38.401 [2].
+
+**NG-RAN MBS session resource context:** as defined in TS 38.401 [2].
+
+**NG-RAN node:** as defined in TS 38.300 [9].
+
+**Non-CAG Cell:** As defined in TS 38.300 [9].
+
+**Non-F1-terminating IAB-donor:** as defined in TS 38.401 [2].
+
+**PDU Session Resource:** As defined in TS 38.401 [2].
+
+**PDU session split:** as defined in TS 37.340 [8].
+
+**Public Network Integrated NPN:** as defined in TS 23.501 [7].
+
+**Stand-alone Non-Public Network:** as defined in TS 23.501 [7].
+
+**Subsequent Conditional PSCell Addition or Change (Subsequent CPAC):** as defined in TS 37.340 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|---------------|-----------------------------------------------------------------------------|
+| 5QI | 5G QoS Identifier |
+| AI | Artificial Intelligence |
+| AMF | Access and Mobility Management Function |
+| A2X | Aircraft-to-Everything |
+| BH | Backhaul |
+| CAG | Closed Access Group |
+| CGI | Cell Global Identifier |
+| CHO | Conditional Handover |
+| CP | Control Plane |
+| CPA | Conditional PSCell Addition |
+| CPAC | Conditional PSCell Addition or Change |
+| CPC | Conditional PSCell Change |
+| DAPS | Dual Active Protocol Stack |
+| DL | Downlink |
+| EN-DC | E-UTRA-NR Dual Connectivity |
+| E-RAB | E-UTRAN Radio Access Bearer |
+| GUAMI | Globally Unique AMF Identifier |
+| IAB | Integrated Access and Backhaul |
+| IMEISV | International Mobile station Equipment Identity and Software Version number |
+| MBS | Multicast/Broadcast Service |
+| MCG | Master Cell Group |
+| ML | Machine Learning |
+| MT-SDT | Mobile Terminated Small Data Transmission |
+| M-NG-RAN node | Master NG-RAN node |
+| NGAP | NG Application Protocol |
+| NID | Network Identifier |
+| NPN | Non-Public Network |
+
+| | |
+|---------------|-------------------------------------------------------|
+| NSAG | Network Slice AS Group |
+| NSSAI | Network Slice Selection Assistance Information |
+| PEIPS | Paging Early Indication with Paging Subgrouping |
+| PNI-NPN | Public Network Integrated Non-Public Network |
+| ProSe | Proximity Services |
+| RANAC | RAN Area Code |
+| RedCap | Reduced Capability |
+| RSN | Redundancy Sequence Number |
+| SCG | Secondary Cell Group |
+| SCTP | Stream Control Transmission Protocol |
+| SNPN | Stand-alone Non-Public Network |
+| S-CPAC | Subsequent CPAC |
+| S-NG-RAN node | Secondary NG-RAN node |
+| S-NSSAI | Single Network Slice Selection Assistance Information |
+| SUL | Supplementary Uplink |
+| SDT | Small Data Transmission |
+| TAC | Tracking Area Code |
+| TAI | Tracking Area Identity |
+| UL | Uplink |
+| UPF | User Plane Function |
+| V2X | Vehicle-to-Everything |
+
+---
+
+## 4 General
+
+### 4.1 Procedure specification principles
+
+The principle for specifying the procedure logic is to specify the functional behaviour of the terminating NG-RAN node exactly and completely. Any rule that specifies the behaviour of the originating NG-RAN node shall be possible to be verified with information that is visible within the system.
+
+The following specification principles have been applied for the procedure text in clause 8:
+
+- The procedure text discriminates between:
+
+- 1) Functionality which "shall" be executed
+
+The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the initiating message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
+
+- 2) Functionality which "shall, if supported" be executed
+
+The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
+
+- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including *Criticality Diagnostics* IE, see section 10.
+
+## 4.2 Forwards and backwards compatibility
+
+The forwards and backwards compatibility of the protocol is assured by a mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.
+
+## 4.3 Specification notations
+
+For the purposes of the present document, the following notations apply:
+
+| | |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Handover Preparation procedure. |
+| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. HANDOVER REQUEST message. |
+| IE | When referring to an information element (IE) in the specification the <i>Information Element Name</i> is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. <i>PDU Session ID</i> IE. |
+| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in sub clause 9.2 enclosed by quotation marks, e.g. "Value". |
+
+---
+
+## 5 XnAP services
+
+The present clause describes the services an NG-RAN node offers to its neighbours.
+
+### 5.1 XnAP procedure modules
+
+The Xn interface XnAP procedures are divided into two modules as follows:
+
+1. XnAP Basic Mobility Procedures;
+2. XnAP Global Procedures;
+
+The XnAP Basic Mobility Procedures module contains procedures used to handle the UE mobility within NG-RAN.
+
+The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module are in contrast to the above module involving two peer NG-RAN nodes.
+
+### 5.2 Parallel transactions
+
+Unless explicitly indicated in the procedure specification, at any instance in time one protocol peer shall have a maximum of one ongoing XnAP procedure related to a certain UE.
+
+---
+
+## 6 Services expected from signalling transport
+
+The signalling connection shall provide in sequence delivery of XnAP messages. XnAP shall be notified if the signalling connection breaks.
+
+Xn signalling transport is specified in TS 38.422 [4].
+
+## 7 Functions of XnAP
+
+The functions of XnAP are specified in TS 38.420 [3].
+
+## 8 XnAP procedures
+
+### 8.1 Elementary procedures
+
+In the following tables, all EPs are divided into Class 1 and Class 2 EPs.
+
+**Table 8.1-1: Class 1 Elementary Procedures**
+
+| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome |
+|----------------------------------------------------------------|----------------------------------|----------------------------------------------|------------------------------------------|
+| | | Response message | Response message |
+| Handover Preparation | HANDOVER REQUEST | HANDOVER REQUEST ACKNOWLEDGE | HANDOVER PREPARATION FAILURE |
+| Retrieve UE Context | RETRIEVE UE CONTEXT REQUEST | RETRIEVE UE CONTEXT RESPONSE | RETRIEVE UE CONTEXT FAILURE |
+| S-NG-RAN node Addition Preparation | S-NODE ADDITION REQUEST | S-NODE ADDITION REQUEST ACKNOWLEDGE | S-NODE ADDITION REQUEST REJECT |
+| M-NG-RAN node initiated S-NG-RAN node Modification Preparation | S-NODE MODIFICATION REQUEST | S-NODE MODIFICATION REQUEST ACKNOWLEDGE | S-NODE MODIFICATION REQUEST REJECT |
+| S-NG-RAN node initiated S-NG-RAN node Modification | S-NODE MODIFICATION REQUIRED | S-NODE MODIFICATION CONFIRM | S-NODE MODIFICATION REFUSE |
+| S-NG-RAN node initiated S-NG-RAN node CHANGE | S-NODE CHANGE REQUIRED | S-NODE CHANGE CONFIRM | S-NODE CHANGE REFUSE |
+| M-NG-RAN node initiated S-NG-RAN node Release | S-NODE RELEASE REQUEST | S-NODE RELEASE REQUEST ACKNOWLEDGE | S-NODE RELEASE REJECT |
+| S-NG-RAN node initiated S-NG-RAN node Release | S-NODE RELEASE REQUIRED | S-NODE RELEASE CONFIRM | |
+| Xn Setup | XN SETUP REQUEST | XN SETUP RESPONSE | XN SETUP FAILURE |
+| NG-RAN node Configuration Update | NG-RAN NODE CONFIGURATION UPDATE | NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE | NG-RAN NODE CONFIGURATION UPDATE FAILURE |
+
+| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome |
+|----------------------------------------|------------------------------------------------|-------------------------------------------------|-------------------------------------------|
+| | | Response message | Response message |
+| Cell Activation | CELL ACTIVATION REQUEST | CELL ACTIVATION RESPONSE | CELL ACTIVATION FAILURE |
+| Reset | RESET REQUEST | RESET RESPONSE | |
+| Xn Removal | Xn REMOVAL REQUEST | Xn REMOVAL RESPONSE | Xn REMOVAL FAILURE |
+| E-UTRA - NR Cell Resource Coordination | E-UTRA - NR CELL RESOURCE COORDINATION REQUEST | E-UTRA - NR CELL RESOURCE COORDINATION RESPONSE | |
+| Resource Status Reporting Initiation | RESOURCE STATUS REQUEST | RESOURCE STATUS RESPONSE | RESOURCE STATUS FAILURE |
+| Mobility Settings Change | MOBILITY CHANGE REQUEST | MOBILITY CHANGE ACKNOWLEDGE | MOBILITY CHANGE FAILURE |
+| IAB Transport Migration Management | IAB TRANSPORT MIGRATION MANAGEMENT REQUEST | IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE | IAB TRANSPORT MIGRATION MANAGEMENT REJECT |
+| IAB Transport Migration Modification | IAB TRANSPORT MIGRATION MODIFICATION REQUEST | IAB TRANSPORT MIGRATION MODIFICATION RESPONSE | |
+| IAB Resource Coordination | IAB RESOURCE COORDINATION REQUEST | IAB RESOURCE COORDINATION RESPONSE | |
+| Partial UE Context Transfer | PARTIAL UE CONTEXT TRANSFER | PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE | PARTIAL UE CONTEXT TRANSFER FAILURE |
+| Data Collection Reporting Initiation | DATA COLLECTION REQUEST | DATA COLLECTION RESPONSE | DATA COLLECTION FAILURE |
+
+**Table 8.1-2: Class 2 Elementary Procedures**
+
+| <b>Elementary Procedure</b> | <b>Initiating Message</b> |
+|------------------------------------------|----------------------------------|
+| Handover Cancel | HANDOVER CANCEL |
+| SN Status Transfer | SN STATUS TRANSFER |
+| RAN Paging | RAN PAGING |
+| Xn-U Address Indication | XN-U ADDRESS INDICATION |
+| S-NG-RAN node Reconfiguration Completion | S-NODE RECONFIGURATION COMPLETE |
+| S-NG-RAN node Counter Check | S-NODE COUNTER CHECK REQUEST |
+| UE Context Release | UE CONTEXT RELEASE |
+| RRC Transfer | RRC TRANSFER |
+| Error Indication | ERROR INDICATION |
+| Notification Control Indication | NOTIFICATION CONTROL INDICATION |
+| Activity Notification | ACTIVITY NOTIFICATION |
+| Secondary RAT Data Usage Report | SECONDARY RAT DATA USAGE REPORT |
+| Trace Start | TRACE START |
+| Deactivate Trace | DEACTIVATE TRACE |
+| Handover Success | HANDOVER SUCCESS |
+| Conditional Handover Cancel | CONDITIONAL HANDOVER CANCEL |
+| Early Status Transfer | EARLY STATUS TRANSFER |
+| Failure Indication | FAILURE INDICATION |
+| Handover Report | HANDOVER REPORT |
+| Resource Status Reporting | RESOURCE STATUS UPDATE |
+| Access And Mobility Indication | ACCESS AND MOBILITY INDICATION |
+| Cell Traffic Trace | CELL TRAFFIC TRACE |
+| RAN Multicast Group Paging | RAN MULTICAST GROUP PAGING |
+| SCG Failure Information Report | SCG FAILURE INFORMATION REPORT |
+| SCG Failure Transfer | SCG FAILURE TRANSFER |
+| F1-C Traffic Transfer | F1-C TRAFFIC TRANSFER |
+| Retrieve UE Context Confirm | RETRIEVE UE CONTEXT CONFIRM |
+| Conditional PSCell Change Cancel | CONDITIONAL PSCELL CHANGE CANCEL |
+| RACH Indication | RACH INDICATION |
+| Data Collection Reporting | DATA COLLECTION UPDATE |
+
+## 8.2 Basic mobility procedures
+
+### 8.2.1 Handover Preparation
+
+#### 8.2.1.1 General
+
+This procedure is used to establish necessary resources in an NG-RAN node for an incoming handover. If the procedure concerns a conditional handover, parallel transactions are allowed. Possible parallel requests are identified by the target cell ID when the source UE AP IDs are the same.
+
+The procedure uses UE-associated signalling.
+
+#### 8.2.1.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant source NG-RAN node
+ participant target NG-RAN node
+ Note left of source:
+ source->>target: HANDOVER REQUEST
+ Note right of target:
+ target-->>source: HANDOVER REQUEST ACKNOWLEDGE
+ Note left of source:
+
+```
+
+Sequence diagram showing the successful operation of Handover Preparation. A source NG-RAN node sends a HANDOVER REQUEST message to a target NG-RAN node, which responds with a HANDOVER REQUEST ACKNOWLEDGE message.
+
+**Figure 8.2.1.2-1: Handover Preparation, successful operation**
+
+The source NG-RAN node initiates the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. When the source NG-RAN node sends the HANDOVER REQUEST message, it shall start the timer $T_{XnRELOCprep}$ .
+
+If the *Conditional Handover Information Request* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall consider that the request concerns a conditional handover and shall include the *Conditional Handover Information Acknowledge* IE in the HANDOVER REQUEST ACKNOWLEDGE message.
+
+If the *Target NG-RAN node UE XnAP ID* IE is contained in the *Conditional Handover Information Request* IE included in the HANDOVER REQUEST message, then the target NG-RAN node shall remove the existing prepared conditional HO identified by the *Target NG-RAN node UE XnAP ID* IE and the *Target Cell Global ID* IE. It is up to the implementation of the target NG-RAN node when to remove the HO information.
+
+Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall stop the timer $T_{XnRELOCprep}$ and terminate the Handover Preparation procedure. If the procedure was initiated for an immediate handover, the source NG-RAN node shall start the timer $T_{XnRELOCoverall}$ . The source NG-RAN node is then defined to have a Prepared Handover for that Xn UE-associated signalling.
+
+For each *E-RAB ID* IE included in the *QoS Flow To Be Setup List* IE in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the content of the IE in the UE context and use it for subsequent inter-system handover.
+
+If the *Masked IMEISV* IE is contained in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.
+
+At reception of the HANDOVER REQUEST message the target NG-RAN node shall prepare the configuration of the AS security relation between the UE and the target NG-RAN node by using the information in the *UE Security Capabilities* IE and the *AS Security Information* IE in the *UE Context Information* IE, as specified in TS 33.501 [28].
+
+Upon reception of the *PDU Session Resource Setup List IE*, contained in the HANDOVER REQUEST message, the target NG-RAN node shall behave the same as specified in TS 38.413 [5] for the PDU Session Resource Setup procedure. The target NG-RAN node shall report in the HANDOVER REQUEST ACKNOWLEDGE message the successful establishment of the result for all the requested PDU session resources. When the target NG-RAN node reports the unsuccessful establishment of a PDU session resource, the cause value should be precise enough to enable the source NG-RAN node to know the reason for the unsuccessful establishment.
+
+For each PDU session if the *PDU Session Aggregate Maximum Bit Rate IE* is included in the *PDU Session Resources To Be Setup List IE* contained in the HANDOVER REQUEST message, the target NG-RAN node shall store the received PDU Session Aggregate Maximum Bit Rate in the UE context and use it when enforcing traffic policing for Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [7].
+
+For each QoS flow for which the source NG-RAN node proposes to perform forwarding of downlink data, the source NG-RAN node shall include the *DL Forwarding IE* set to "DL forwarding proposed" within the *Data Forwarding and Offloading Info from source NG-RAN node IE* in the *PDU Session Resources To Be Setup List IE* in the HANDOVER REQUEST message. The source NG-RAN node shall include the *DL Forwarding IE* set to "DL forwarding proposed" for all the QoS flows mapped to a DRB, if it requests a DAPS handover for that DRB.
+
+For each PDU session for which the target NG-RAN node decides to admit the data forwarding for at least one QoS flow, the target NG-RAN node may include the *PDU Session level DL data forwarding UP TNL Information IE* within the *Data Forwarding Info from target NG-RAN node IE* in the *PDU Session Resource Admitted Info IE* contained in the *PDU Session Resources Admitted List IE* in the HANDOVER REQUEST ACKNOWLEDGE message.
+
+For each QoS flow for which the source NG-RAN node has not yet received the SDAP end marker packet if QoS flow re-mapping happened before handover, the source NG-RAN node shall include the *UL Forwarding Proposal IE* within the *Data Forwarding and Offloading Info from source NG-RAN node IE* in the HANDOVER REQUEST message, and if the target NG-RAN node decides to admit uplink data forwarding for at least one QoS flow, the target NG-RAN node may include the *PDU Session Level UL Data Forwarding UP TNL Information IE* in the *Data Forwarding Info from target NG-RAN node IE* in the *PDU Session Resources Admitted Item IE* contained in the *PDU Session Resources Admitted List IE* in the HANDOVER REQUEST ACKNOWLEDGE message to indicate that it accepts the uplink data forwarding.
+
+For each PDU session resource successfully setup at the target NG-RAN, the target NG-RAN node may allocate resources for additional Xn-U PDU session resource GTP-U tunnels, indicated in the *Secondary Data Forwarding Info from target NG-RAN node List IE*.
+
+If the direct data forwarding path is available between the target NG-RAN node and the source S-NG-RAN node for a PDU session, the target M-NG-RAN node shall, if supported, include the *Direct Forwarding Path Availability IE* in the *Data Forwarding Info from target NG-RAN node IE* or in the *Secondary Data Forwarding Info from target NG-RAN node IE* corresponding to the target node of that PDU session in the HANDOVER REQUEST ACKNOWLEDGE message.
+
+For each PDU session in the HANDOVER REQUEST message, if the *Alternative QoS Parameters Set List IE* is included in the *GBR QoS Flow Information IE* in the *PDU Session Resources To Be Setup List IE*, the target NG-RAN node may accept the setup of the involved QoS flow when notification control has been enabled if the requested QoS parameters set or at least one of the alternative QoS parameters sets can be fulfilled at the time of handover as specified in TS 23.501 [7]. In case the target NG-RAN node accepts the handover fulfilling one of the alternative QoS parameters it shall indicate the alternative QoS parameters set which it can currently fulfil in the *Current QoS Parameters Set Index IE* within the *PDU Session Resources Admitted List IE* of the HANDOVER REQUEST ACKNOWLEDGE message while setting the QoS parameters towards the UE according to the requested QoS parameters set as specified in TS 23.501 [7].
+
+For each DRB for which the source NG-RAN node proposes to perform forwarding of downlink data, the source NG-RAN node shall include the *DRB ID IE* and the mapped *QoS Flows List IE* within the *Source DRB to QoS Flow Mapping List IE* contained in the *PDU Session Resources To Be Setup List IE* in the HANDOVER REQUEST message. The source NG-RAN node may include the *QoS Flow Mapping Indication IE* in the *Source DRB to QoS Flow Mapping*
+
+*List* IE to indicate that only the uplink or downlink QoS flow is mapped to the DRB. If the target NG-RAN node decides to use the same DRB configuration and to map the same QoS flows as the source NG-RAN node, the target NG-RAN node includes the *DL Forwarding GTP Tunnel Endpoint* IE within the *Data Forwarding Response DRB List* IE in the HANDOVER REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding of downlink data for this DRB.
+
+The target NG-RAN node may additionally include the *Redundant DL Forwarding UP TNL Information* IE if at least one of the QoS flow mapped to the DRB is eligible to the redundant transmission feature as indicated in the *Redundant QoS Flow Indicator* IE within the *PDU Session Resource To Be Setup List* IE received in the HANDOVER REQUEST message for the QoS flow.
+
+If the HANDOVER REQUEST ACKNOWLEDGE message contains the *UL Forwarding UP TNL Information* IE for a given DRB in the *Data Forwarding Response DRB List* IE within *Data Forwarding Info from target NG-RAN node* IE in the *PDU Session Resources Admitted List* IE and the source NG-RAN node accepts the data forwarding proposed by the target NG-RAN node, the source NG-RAN node shall perform forwarding of uplink data for the DRB.
+
+If the HANDOVER REQUEST includes PDU session resources for PDU sessions associated to S-NSSAIs not supported by target NG-RAN, the target NG-RAN node shall reject such PDU session resources. In this case, and if at least one *PDU Session Resource To Be Setup Item* IE is admitted, the target NG-RAN node shall send the HANDOVER REQUEST ACKNOWLEDGE message including the *PDU Session Resources Not Admitted List* IE listing corresponding PDU sessions rejected at the target NG-RAN.
+
+If the *Mobility Restriction List* IE is
+
+- contained in the HANDOVER REQUEST message, the target NG-RAN node shall
+ - store the information received in the *Mobility Restriction List* IE in the UE context;
+ - use this information to determine a target for the UE during subsequent mobility action for which the NG-RAN node provides information about the target of the mobility action towards the UE, except when one of the PDU sessions has a particular ARP value (TS 23.501 [7]) in which case the information shall not apply;
+ - use this information to select a proper SCG during dual connectivity operation.
+ - use this information to select proper RNA(s) for the UE when moving the UE to RRC\_INACTIVE.
+- not contained in the HANDOVER REQUEST message, the target NG-RAN node shall
+ - consider that no roaming and no access restriction apply to the UE except for the PNI-NPN mobility as described in TS 23.501 [7].
+
+The target NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the *Allowed PNI-NPN ID List* IE is contained in the HANDOVER REQUEST message, as described in TS 23.501 [7].
+
+If the *Trace Activation* IE is included in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, initiate the requested trace function as specified in TS 32.422 [23].
+
+If the *Index to RAT/Frequency Selection Priority* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall store this information and use it as defined in TS 23.501 [7].
+
+If the *UE Context Reference at the S-NG-RAN* IE is contained in the HANDOVER REQUEST message the target NG-RAN node may use it as specified in TS 37.340 [8]. In this case, the source NG-RAN node may expect the target NG-RAN node to include the *UE Context Kept Indicator* IE set to "True" in the HANDOVER REQUEST ACKNOWLEDGE message, which shall use this information as specified in TS 37.340 [8].
+
+For each PDU session, if the *Network Instance* IE is included in the *PDU Session Resource To Be Setup List* IE and the *Common Network Instance* IE is not present, the target NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].
+
+Redundant transmission:
+
+- For each PDU session, if the *Redundant UL NG-U UP TNL Information at UPF* IE is included in the *PDU Session Resource To Be Setup List* IE, the target NG-RAN node shall, if supported, use it as the uplink termination point for the user plane data for the redundant transmission for the concerned PDU session.
+- For each PDU session, if the *Additional Redundant UL NG-U UP TNL Information at UPF List* IE is included in the *PDU Session Resource To Be Setup List* IE, the target NG-RAN node shall, if supported, use them as the uplink termination points for the user plane data for the redundant transmission for the concerned PDU session.
+- For each PDU session, if the *Redundant Common Network Instance* IE is included in the *PDU Session Resource To Be Setup List* IE, the target NG-RAN node shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [7].
+- For each PDU session, if the *Redundant PDU Session Information* IE is included in the *PDU Session Resource To Be Setup List* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the received information in the UE context and set up the redundant user plane for the concerned PDU session, as specified in TS 23.501 [7]. If the *PDU Session Pair ID* IE is included in the *Redundant PDU Session Information* IE, the target NG-RAN node may store and use it to identify the paired PDU sessions.
+
+If the *TSC Traffic Characteristics* IE is included in the *QoS Flows To Be Setup List* in the *PDU Session Resource To Be Setup List* IE, the target NG-RAN node shall, if supported, use it as specified in TS 23.501 [7].
+
+For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource To Be Setup List* IE or in the *Additional UL NG-U UP TNL Information at UPF List* IE, or in the *Additional Redundant UL NG-U UP TNL Information at UPF List* IE, the target NG-RAN node shall, if supported, use it when selecting transport network resource for the concerned NG-U transport bearer as specified in TS 23.501 [7].
+
+For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Be Setup List* IE and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "required", the target NG-RAN node shall perform user plane integrity protection or ciphering, respectively. If the NG-RAN node is not able to perform the user plane integrity protection or ciphering, it shall reject the setup of the PDU Session Resources with an appropriate cause value.
+
+If the NG-RAN node is an ng-eNB, it shall behave as specified in TS 33.501 [28].
+
+For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Be Setup List* IE and the *Integrity Protection Indication* IE or the *Confidentiality Protection Indication* IE is set to "preferred", the target NG-RAN node should, if supported, perform user plane integrity protection or ciphering, respectively and shall notify the SMF whether it succeeded the user plane integrity protection or ciphering or not for the concerned security policy.
+
+For each PDU session for which the *Maximum Integrity Protected Data Rate* IE is included in the *Security Indication* IE in the *PDU Session Resources To Be Setup List* IE, the NG-RAN node shall store the respective information and, if integrity protection is to be performed for the PDU session, it shall enforce the traffic corresponding to the received *Maximum Integrity Protected Data Rate* IE, for the concerned PDU session and concerned UE, as specified in TS 23.501 [7].
+
+For each PDU session for which the *Security Indication* IE is included in the *PDU Session Resource To Be Setup List* IE and the *Integrity Protection Indication* IE or *Confidentiality Protection Indication* IE is set to "not needed", the target NG-RAN node shall not perform user plane integrity protection or ciphering, respectively, for the concerned PDU session.
+
+For each PDU session, if the *Additional UL NG-U UP TNL Information List* IE is included in the *PDU Session Resources To Be Setup List* IE contained in the HANDOVER REQUEST message, the target NG-RAN node may forward the UP transport layer information to the target S-NG-RAN node as the uplink termination point for the user plane data for this PDU session split in different tunnel.
+
+If the *Location Reporting Information* IE is included in the HANDOVER REQUEST message, then the target NG-RAN node should initiate the requested location reporting functionality as defined in TS 38.413 [5].
+
+Upon reception of *UE History Information* IE in the HANDOVER REQUEST message, the target NG-RAN node shall collect the information defined as mandatory in the *UE History Information* IE and shall, if supported, collect the information defined as optional in the *UE History Information* IE, for as long as the UE stays in one of its cells, and store the collected information to be used for future handover preparations.
+
+If the *Trace Activation* IE is included in the HANDOVER REQUEST message which includes
+
+- the *MDT Activation* IE set to "Immediate MDT and Trace", then the target NG-RAN node shall if supported, initiate the requested trace session and MDT session as described in TS 32.422 [23].
+- the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", the target NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422 [23] and the target NG-RAN node shall ignore the *Interfaces To Trace* IE, and the *Trace Depth* IE.
+- the *MDT Location Information* IE, within the *MDT Configuration* IE, the target NG-RAN node shall, if supported, store this information and take it into account in the requested MDT session.
+- the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", and if the *Signalling based MDT PLMN List* IE is included in the *MDT Configuration* IE, the target NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [43].
+- the *Bluetooth Measurement Configuration* IE, within the *MDT Configuration* IE, the target NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *WLAN Measurement Configuration* IE, within the *MDT Configuration* IE, the target NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *Sensor Measurement Configuration* IE, within the *MDT Configuration* IE, the target NG-RAN node shall take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *MDT Configuration* IE and if the target NG-RAN node is a gNB receiving a *MDT Configuration-EUTRA* IE, or the target NG-RAN node is a ng-eNB receiving a *MDT Configuration-NR* IE, the target NG-RAN node shall store it as part of the UE context, and use it as described in TS 37.320 [43].
+
+If the *Area Scope* IE is not present in the *MDT Configuration* IE, the target NG-RAN node shall consider that the MDT Configuration is applied to all PLMNs indicated in the MDT PLMN List, as described in TS 32.422 [23].
+
+If the *Management Based MDT PLMN List* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the received information in the UE context, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [23].
+
+If the HANDOVER REQUEST message includes the *Management Based MDT PLMN List* IE, the target NG-RAN node shall, if supported, store it in the UE context, and take it into account if it includes information regarding the PLMN serving the UE in the target NG-RAN node.
+
+If the *Mobility Information* IE is provided in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information. The target NG-RAN shall, if supported, store the C-RNTI assigned at the source cell as received in the HANDOVER REQUEST message.
+
+Upon reception of the *UE History Information from the UE* IE in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the collected information and use it for future handover preparations.
+
+For each QoS flow which has been successfully established in the target NG-RAN node, if the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall store this information, and shall, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [7]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS*
+
+*Flow Level QoS Parameters* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall store this information, and shall, if supported, use it for RAN part delay reporting. For each QoS Flow, if the *PDU Set QoS Parameters* IE is included in the *QoS Flow Level QoS Parameters* IE in the *PDU Session Resources To Be Setup List* IE, the target NG-RAN node shall, if supported, use it as specified in TS 23.501 [7].
+
+If the HANDOVER REQUEST message includes the *PDU Set QoS Parameters* IE, the target NG-RAN node shall, if supported, report in the HANDOVER REQUEST ACKNOWLEDGE message the *PDU Set based Handling Indicator* IE.
+
+For each QoS flow which has been successfully established in the target NG-RAN node, if the *ECN Marking or Congestion Information Reporting Request* IE is included in the *PDU Session Resources To Be Setup List* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it accordingly for the specific QoS flow.
+
+For a QoS flow established with PDU Set QoS parameters, if the *PDU Set based Handling Indicator* IE set to "supported" is included in the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall, if supported, include the PDU Set information in the data to be forwarded. Otherwise, the source NG-RAN node may not include the PDU Set information in the data to be forwarded.
+
+If the *5GC Mobility Restriction List Container* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information in the UE context and use it as specified in TS 38.300 [9].
+
+#### V2X:
+
+- If the *NR V2X Services Authorized* IE is included in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the target NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *LTE V2X Services Authorized* IE is included in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the target NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *NR UE Sidelink Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for NR V2X services.
+- If the *LTE UE Sidelink Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services.
+
+#### A2X:
+
+- If the *NR A2X Services Authorized* IE is included in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the target NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *LTE A2X Services Authorized* IE is included in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the target NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *NR A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for NR A2X services.
+- If the *LTE A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services.
+
+- If the *A2X PC5 QoS Parameters* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it as defined in TS 23.256 [56].
+
+5G ProSe:
+
+- If the *5G ProSe Authorized* IE is included in the HANDOVER REQUEST message and it contains one or more IEs set to "authorized", the target NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *5G ProSe UE PC5 Aggregate Maximum Bit Rate* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services.
+- If the *5G ProSe PC5 QoS Parameters* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it as defined in TS 23.304 [48].
+
+If the *PC5 QoS Parameters* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it as defined in TS 23.287 [38].
+
+If the *Aerial UE Subscription Information* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 38.300 [9].
+
+If the *Candidate Relay UE Info List* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it to configure the path switch to indirect path as specified in TS 38.300 [9].
+
+If the *DAPS Request Information* IE is included for a given DRB in the HANDOVER REQUEST message, the target NG-RAN node shall consider that the request concerns a DAPS handover for that DRB, as described in TS 38.300 [9]. Accordingly, the target NG-RAN node shall include the *DAPS Response Information* IE in the HANDOVER REQUEST ACKNOWLEDGE message.
+
+If the *Maximum Number of CHO Preparations* IE is included in the *Conditional Handover Information Acknowledge* IE contained in the HANDOVER REQUEST ACKNOWLEDGE message, then the source NG-RAN node should not prepare more candidate target cells for a CHO for the same UE towards the target NG-RAN node than the number indicated in the IE.
+
+If the *Estimated Arrival Probability* IE is contained in the *Conditional Handover Information Request* IE included in the HANDOVER REQUEST message, then the target NG-RAN node may use the information to allocate necessary resources for the incoming CHO.
+
+If the *Conditional Handover Time Based Information* IE is contained in the *Conditional Handover Information Request* IE included in the HANDOVER REQUEST message, then the target NG-RAN node may use this information to allocate necessary resources for the incoming CHO.
+
+If the *Maximum Number of Conditional Reconfigurations to Prepare* IE is contained in the *Conditional Handover Information Request* IE included in the HANDOVER REQUEST message, then the target NG-RAN node may use the information to prepare for CHO with candidate PSCell(s) configuration and may include the *CHO-CPAC Information* IE within the *Conditional Handover Information Acknowledge* IE in the HANDOVER REQUEST ACKNOWLEDGE message. The target NG-RAN node may also provide a CHO-only configuration, which is counted as one toward the maximum number indicated by the *Maximum Number of Conditional Reconfigurations to Prepare* IE.
+
+If the *IAB Node Indication* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, consider that the handover is for an IAB node. In addition:
+
+- If the *No PDU Session Indication* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, consider the UE as an IAB-node which does not have any PDU sessions activated, and ignore the *PDU Session Resources To Be Setup List* IE, and shall not take any action with respect to PDU session setup. Subsequently, the source NG-RAN node shall, if supported, ignore the *PDU Session Resources Admitted To Be Added List* IE in the HANDOVER REQUEST ACKNOWLEDGE message.
+
+If the *UE Radio Capability ID* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [7] and TS 23.502 [13].
+
+If for a given QoS Flow the *Source DL Forwarding IP Address* IE is included within the *Data Forwarding and Offloading Info from source NG-RAN node* IE in the *PDU Session Resources To Be Setup List* IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.
+
+If the *MBS Session Information List* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, establish an NG-RAN MBS session resources context as specified in TS 23.247 [46] and TS 38.300 [9], if applicable.
+
+If the HANDOVER REQUEST message includes the *MBS Area Session ID* IE, the target NG-RAN, if supported, shall use this information as an indication from which MBS Area Session ID the UE is handed over. For each MBS session for which the *Active MBS Session Information* IE is included in the *MBS Session Information Item List* IE, the target NG-RAN shall, if supported, use this information to setup respective MBS session resources. The target NG-RAN node shall, if supported, consider that the MBS sessions for which the *Active MBS Session Information* IE is not included are inactive.
+
+If the HANDOVER REQUEST ACKNOWLEDGE message contains in the *MBS Session Information Response List* IE the *MBS Data Forwarding Response Info* IE that the source NG-RAN node shall use the information for forwarding MBS traffic to the target NG-RAN node.
+
+If the *MBS Session Associated Information List* IE is included in the *PDU Session Resources To Be Setup List* IE in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use the information contained in the *Associated QoS Flows Information List* IE as specified in TS 23.247 [46].
+
+For each MRB indicated in the *MBS Mapping and Data Forwarding Request Info from source NG-RAN node* IE, the target NG-RAN node shall use the *MRB ID* IE and, if included, the *MRB Progress Information* IE which includes the highest PDCP SN of the packet which has already been delivered to the UE for the MRB, to decide whether to apply data forwarding for that MRB and to establish respective resources.
+
+The source NG-RAN shall, for each MRB in the *MBS Data Forwarding Response Info from target NG-RAN node* IE in the HANDOVER REQUEST ACKNOWLEDGE message, start data forwarding to the indicated DL Forwarding UP TNL Information. If the *MRB Progress Information* IE is included the source NG-RAN node may use the information to determine when to stop data forwarding.
+
+If the *Time Synchronisation Assistance Information* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [7].
+
+If the *QMC Configuration Information* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, take it into account for QoE measurements handling, as described in TS 38.300 [9].
+
+If the *SN-related QMC Information at MN* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it for QoE measurements handling, as specified in TS 38.300 [9].
+
+If the *Source SN to Target SN QMC Information* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it for QoE measurements handling, as specified in TS 38.300 [9].
+
+If the *UE Slice-Maximum Bit Rate List* IE is contained in HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the received UE Slice Maximum Bit Rate List in the UE context, and use the received UE Slice Maximum Bit Rate value for each S-NSSAI for the concerned UE as specified in TS 23.501 [7].
+
+If the *Cell Based UE Trajectory Prediction* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, consider the content of this list as the predicted cells for UE trajectory by the source NG-RAN node, and may use it for e.g. mobility decisions.
+
+If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN. Upon reception of the *PNI-NPN Area Scope of MDT* IE, the target NG-RAN node shall consider that the area scope for MDT measurement collection of PNI-NPN areas is defined only by the areas included in the *PNI-NPN Area Scope of MDT* IE.
+
+If the *RRC Config Indication* IE is contained in the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall, if supported, consider that the target NG-RAN node applied a full configuration or delta configuration, e.g., as part of conditional handover procedure involving dual connectivity operation.
+
+If the *Mobile IAB Authorization Status* IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the received Mobile IAB authorization status information in the UE context and consider that the handover is for a mobile IAB node. If the *Mobile IAB Authorization Status* IE is set to "not authorized" for a mobile IAB-MT, the target NG-RAN node shall, if supported, refrain from establishing backhaul resources for this mobile IAB-node.
+
+#### Interaction with SN Status Transfer procedure:
+
+If the *UE Context Kept Indicator* IE set to "True" and the *DRBs transferred to MN* IE are included in the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall, if supported, include the uplink/downlink PDCP SN and HFN status received from the S-NG-RAN node in the SN Status Transfer procedure towards the target NG-RAN node, as specified in TS 37.340 [8].
+
+#### Interaction with the Data Collection Reporting and the Data Collection Reporting Initiation procedures:
+
+If the *Data Collection ID* IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, report to the source NG-RAN node after the completion of handover procedure, via the Data Collection Reporting procedure, the requested information configured via the previous Data Collection Reporting Initiation procedure corresponding to the *NG-RAN node1 Measurement ID* and the *NG-RAN node2 Measurement ID* IEs.
+
+### 8.2.1.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant source NG-RAN node
+ participant target NG-RAN node
+ Note left of source:
+ source->>target: HANDOVER REQUEST
+ Note right of target:
+ target-->>source: HANDOVER PREPARATION FAILURE
+ Note left of source:
+
+```
+
+Sequence diagram showing an unsuccessful handover preparation. A source NG-RAN node sends a HANDOVER REQUEST to a target NG-RAN node. The target NG-RAN node responds with a HANDOVER PREPARATION FAILURE message. Both nodes are represented by rectangular boxes with a vertical line extending downwards to a horizontal bar representing the timeline.
+
+Figure 8.2.1.3-1: Handover Preparation, unsuccessful operation
+
+If the target NG-RAN node does not admit at least one PDU session resource, or a failure occurs during the Handover Preparation, the target NG-RAN node shall send the HANDOVER PREPARATION FAILURE message to the source NG-RAN node. The message shall contain the *Cause* IE with an appropriate value.
+
+If the *Conditional Handover Information Request* IE is contained in the HANDOVER REQUEST message and the target NG-RAN node rejects the handover or a failure occurs during the Handover Preparation, the target NG-RAN node shall include the *Requested Target Cell ID* IE in the HANDOVER PREPARATION FAILURE message.
+
+#### Interactions with Handover Cancel procedure:
+
+If there is no response from the target NG-RAN node to the HANDOVER REQUEST message before timer $T_{XN_{RELOCprep}}$ expires in the source NG-RAN node, the source NG-RAN node should cancel the Handover Preparation
+
+procedure towards the target NG-RAN node by initiating the Handover Cancel procedure with the appropriate value for the *Cause* IE. The source NG-RAN node shall ignore any HANDOVER REQUEST ACKNOWLEDGE or HANDOVER PREPARATION FAILURE message received after the initiation of the Handover Cancel procedure and remove any reference and release any resources related to the concerned Xn UE-associated signalling.
+
+#### 8.2.1.4 Abnormal Conditions
+
+If the supported algorithms for encryption defined in the *UE Security Capabilities* IE in the *UE Context Information* IE, plus the mandated support of the EEA0 and NEA0 algorithms in all UEs (TS 33.501 [28]), do not match any allowed algorithms defined in the configured list of allowed encryption algorithms in the NG-RAN node (TS 33.501 [28]), the NG-RAN node shall reject the procedure using the HANDOVER PREPARATION FAILURE message.
+
+If the supported algorithms for integrity defined in the *UE Security Capabilities* IE in the *UE Context Information* IE, plus the mandated support of the EIA0 and NIA0 algorithms in all UEs (TS 33.501 [28]), do not match any allowed algorithms defined in the configured list of allowed integrity protection algorithms in the NG-RAN node (TS 33.501 [28]), the NG-RAN node shall reject the procedure using the HANDOVER PREPARATION FAILURE message.
+
+If the *CHO trigger* IE is set to "CHO-replace" in the HANDOVER REQUEST message, but there is no CHO prepared for the included Target NG-RAN node UE XnAP ID, or the candidate cell in the *Target Cell ID* IE was not prepared using the same UE-associated signaling connection, the NG-RAN node shall reject the procedure using the HANDOVER PREPARATION FAILURE message.
+
+If the HANDOVER REQUEST message includes information for a PLMN not serving the UE in the target NG-RAN node in the *Management Based MDT PLMN List* IE, the target NG-RAN node shall ignore information for that PLMN within the Management Based MDT PLMN List.
+
+If both the *PNI-NPN Area Scope of MDT* IE and the *Area Scope of MDT-NR* IE are included in the *MDT Configuration-NR* IE in the HANDOVER REQUEST message, and the *Area Scope of MDT-NR* IE is set to "PNI-NPN based", the target NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collections in PNI-NPN areas, and ignore the *PNI-NPN Area Scope of MDT* IE.
+
+If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE in the HANDOVER REQUEST message, and the *Area Scope of MDT-NR* IE is not included, the target NG-RAN node shall ignore the *PNI-NPN Area Scope of MDT* IE, and consider that the MDT Configuration for NR is applied to all PLMNs indicated in the MDT PLMN List described in TS 32.422 [23].
+
+### 8.2.2 SN Status Transfer
+
+#### 8.2.2.1 General
+
+The purpose of the SN Status Transfer procedure is to transfer the uplink PDCP SN and HFN receiver status and the downlink PDCP SN and HFN transmitter status either, from the source to the target NG-RAN node during an Xn handover, between the NG-RAN nodes involved in dual connectivity, or after retrieval of a UE context for RRC reestablishment, for each respective DRB of the source DRB configuration for which PDCP SN and HFN status preservation applies.
+
+In case that the Xn handover is a DAPS handover, the SN Status Transfer procedure may also be used to transfer the uplink PDCP SN and HFN receiver status, and the downlink PDCP SN and HFN transmitter status for a DRB associated with RLC-UM and configured with DAPS as described in TS 38.300 [9].
+
+In case that the Xn handover is a CHO, the SN Status Transfer procedure may also be used to transfer handover related information.
+
+If the SN Status Transfer procedure is applied in the course of dual connectivity or RRC connection re-establishment in the subsequent specification text
+
+- the behaviour of the NG-RAN node from which the DRB context is transferred, i.e. the NG-RAN node involved in dual connectivity or RRC connection re-establishment, from which data is forwarded, is specified by the behaviour of the "source NG-RAN node",
+- the behaviour of the NG-RAN node to which the DRB context is transferred, i.e., the NG-RAN node involved in dual connectivity or RRC connection re-establishment, to which data is forwarded, is specified by the behaviour of the "target NG-RAN node".
+
+The procedure uses UE-associated signalling.
+
+### 8.2.2.2 Successful Operation
+
+
+
+```
+
+graph LR
+ source[source NG-RAN node] -- "SN STATUS TRANSFER" --> target[target NG-RAN node]
+ source --- radio1[ ]
+ target --- radio2[ ]
+ style radio1 fill:black,stroke:none
+ style radio2 fill:black,stroke:none
+
+```
+
+Diagram illustrating the SN Status Transfer procedure. A 'source NG-RAN node' box on the left sends a horizontal arrow labeled 'SN STATUS TRANSFER' to a 'target NG-RAN node' box on the right. Both boxes have a vertical line extending downwards to a thick horizontal bar at the bottom, representing the radio interface.
+
+**Figure 8.2.2.2-1: SN Status Transfer, successful operation**
+
+The source NG-RAN node initiates the procedure by stop assigning PDCP SNs to downlink SDUs and stop delivering UL SDUs towards the 5GC and sending the SN STATUS TRANSFER message to the target NG-RAN node at the time point when it considers the transmitter/receiver status to be frozen. The target NG-RAN node using full configuration for this handover as per TS 38.300 [9] or for the MR-DC operations as per TS 37.340 [8] shall ignore the information received in this message. In case of MR-DC, if the target NG-RAN node performs PDCP SN length change or RLC mode change for a DRB as specified in TS 37.340 [8], it shall ignore the information received for that DRB in this message.
+
+In case that the Xn handover is a DAPS handover, the source NG-RAN node may continue assigning PDCP SNs to downlink SDUs and delivering uplink SDUs toward the 5GC when initiating this procedure for DRBs not configured with DAPS as in TS 38.300 [9].
+
+For each DRB in the *DRBs Subject to Status Transfer List* IE, the source NG-RAN node shall include the *DRB ID* IE, the *UL COUNT Value* IE and the *DL COUNT Value* IE.
+
+The source NG-RAN node may also include in the SN STATUS TRANSFER message the missing and the received uplink SDUs in the *Receive Status of UL PDCP SDUs* IE for each DRB for which the source NG-RAN node has accepted the request from the target NG-RAN node for uplink forwarding.
+
+For each DRB in the *DRBs Subject to Status Transfer List* IE, the target NG-RAN node shall not deliver any uplink packet which has a PDCP-SN lower than the value contained within the *UL COUNT Value* IE.
+
+For each DRB in the *DRBs Subject to Status Transfer List* IE, the target NG-RAN node shall use the value of the PDCP SN contained within the *DL COUNT Value* IE for the first downlink packet for which there is no PDCP-SN yet assigned.
+
+If the *Receive Status of UL PDCP SDUs* IE is included for at least one DRB in the SN STATUS TRANSFER message, the target NG-RAN node may use it in a Status Report message sent to the UE over the radio interface.
+
+If the SN STATUS TRANSFER message contains in the *DRBs Subject To Status Transfer List* IE the *Old QoS Flow List - UL End Marker expected* IE, the target NG-RAN node shall be prepared to receive the SDAP end marker for the QoS flow via the corresponding DRB, as specified in TS 38.300 [9].
+
+If the *CHO Configuration* IE is included in the SN STATUS TRANSFER message, the target NG-RAN node shall, if supported, store this information in the UE context and use it as specified in TS 38.300 [9].
+
+If the *Mobility Information* IE is included in the SN STATUS TRANSFER message, the target NG-RAN node shall, if supported, store this information in the UE context and use it as specified in TS 38.300 [9].
+
+### 8.2.2.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.2.4 Abnormal Conditions
+
+If the target NG-RAN node receives this message for a UE for which no prepared handover exists at the target NG-RAN node, the target NG-RAN node shall ignore the message.
+
+## 8.2.3 Handover Cancel
+
+### 8.2.3.1 General
+
+The Handover Cancel procedure is used to enable a source NG-RAN node to cancel an ongoing handover preparation or an already prepared handover.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.3.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant source NG-RAN node
+ participant target NG-RAN node
+ Note left of source: source NG-RAN node
+ Note right of target: target NG-RAN node
+ source NG-RAN node->>target NG-RAN node: HANDOVER CANCEL
+```
+
+Sequence diagram showing the successful operation of Handover Cancel. A source NG-RAN node sends a HANDOVER CANCEL message to a target NG-RAN node.
+
+**Figure 8.2.3.2-1: Handover Cancel, successful operation**
+
+The source NG-RAN node initiates the procedure by sending the HANDOVER CANCEL message to the target NG-RAN node. The source NG-RAN node shall indicate the reason for cancelling the handover by means of an appropriate cause value.
+
+If the *Candidate Cells To Be Cancelled List* IE is included in the HANDOVER CANCEL message, the target NG-RAN node shall consider that the source NG-RAN node is cancelling only the handover associated to the candidate cells identified by the included NG-RAN CGI and associated to the same UE-associated signaling connection identified by the *Source NG-RAN node UE XnAP ID* IE and, if included, also by the *Target NG-RAN node UE XnAP ID* IE.
+
+### 8.2.3.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.3.4 Abnormal Conditions
+
+If the HANDOVER CANCEL message refers to a context that does not exist, the target NG-RAN node shall ignore the message.
+
+If the *Candidate Cells To Be Cancelled List* IE is included in the HANDOVER CANCEL message and the handover is not associated to a conditional handover, the target NG-RAN node shall ignore the *Candidate Cells To Be Cancelled List* IE.
+
+If one or more candidate cells in the *Candidate Cells To Be Cancelled List* IE included in the HANDOVER CANCEL message were not prepared using the same UE-associated signaling connection, the target NG-RAN node shall ignore those non-associated candidate cells.
+
+## 8.2.4 Retrieve UE Context
+
+### 8.2.4.1 General
+
+The purpose of the Retrieve UE Context procedure is to either retrieve the UE context from the old NG-RAN node and transfer it to the NG-RAN node where the UE RRC Connection has been requested to be established, or to enable the old NG-RAN node to forward an RRC message to the UE via the new NG-RAN node without context transfer, or to request for small data transmission. The procedure can also be used to transfer the authorization status information of the mobile IAB-node.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.4.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant new NG-RAN node
+ participant old NG-RAN node
+ Note left of old NG-RAN node:
+ Note right of new NG-RAN node:
+ new NG-RAN node->>old NG-RAN node: RETRIEVE UE CONTEXT REQUEST
+ old NG-RAN node-->>new NG-RAN node: RETRIEVE UE CONTEXT RESPONSE
+```
+
+Sequence diagram showing the successful operation of the Retrieve UE Context procedure. A 'new NG-RAN node' sends a 'RETRIEVE UE CONTEXT REQUEST' message to an 'old NG-RAN node'. The 'old NG-RAN node' responds with a 'RETRIEVE UE CONTEXT RESPONSE' message.
+
+**Figure 8.2.4.2-1: Retrieve UE Context, successful operation**
+
+The new NG-RAN node initiates the procedure by sending the RETRIEVE UE CONTEXT REQUEST message to the old NG-RAN node.
+
+If the old NG-RAN node is able to identify the UE context by means of the UE Context ID, and to successfully verify the UE by means of the integrity protection contained in the RETRIEVE UE CONTEXT REQUEST message, and decides to provide the UE context to the new NG-RAN node, it shall respond to the new NG-RAN node with the RETRIEVE UE CONTEXT RESPONSE message.
+
+If the *Trace Activation* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, initiate the requested trace function as specified in TS 32.422 [23].
+
+If the *Index to RAT/Frequency Selection Priority* IE is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall store this information and use it as defined in TS 23.501 [7].
+
+If the *Location Reporting Information* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, then the new NG-RAN node should initiate the requested location reporting functionality as defined in TS 38.413 [5].
+
+If the *Trace Activation* IE is included in the RETRIEVE UE CONTEXT RESPONSE message which includes
+
+- the *MDT Activation* IE set to "Immediate MDT and Trace", then the new NG-RAN node shall if supported, initiate the requested trace session and MDT session as described in TS 32.422 [23].
+- the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", the new NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422 [23] and the target NG-RAN node shall ignore the *Interfaces To Trace* IE, and the *Trace Depth* IE.
+- the *MDT Location Information* IE, within the *MDT Configuration* IE, the new NG-RAN node shall, if supported, store this information and take it into account in the requested MDT session.
+- the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", and if the *Signalling based MDT PLMN List* IE is included in the *MDT Configuration* IE, the new NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [43].
+- the *Bluetooth Measurement Configuration* IE, within the *MDT Configuration* IE, the new NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *WLAN Measurement Configuration* IE, within the *MDT Configuration* IE, the new NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *Sensor Measurement Configuration* IE, within the *MDT Configuration* IE, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *MDT Configuration* and if the new NG-RAN node is a gNB receiving a *MDT Configuration-EUTRA* IE, or the target NG-RAN node is a ng-eNB receiving a *MDT Configuration-NR* IE, the new NG-RAN node shall store it as part of the UE context, and use it as described in TS 37.320 [43].
+
+If the *Area Scope* IE is not present in the *MDT Configuration* IE, the new NG-RAN node shall consider that the MDT Configuration is applied to all PLMNs indicated in the MDT PLMN List, as described in TS 32.422 [23].
+
+For each QoS flow in the RETRIEVE UE CONTEXT RESPONSE message, if the *QoS Monitoring Request* IE is included in the *QoS Flow Level QoS Parameters* IE in the *PDU Session Resources To Be Setup List* IE, the new NG-RAN node shall store this information, and shall, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [7]. If the *QoS Monitoring Reporting Frequency* IE is included in the *QoS Flow Level QoS Parameters* IE in the *PDU Session Resources To Be Setup List* IE, the new NG-RAN node shall store this information, and shall, if supported, use it for RAN part delay reporting. For each QoS Flow, if the *PDU Set QoS Parameters* IE is included in the *QoS Flow Level QoS Parameters* IE in the *PDU Session Resources To Be Setup List* IE, the new NG-RAN node shall, if supported, use it as specified in TS 23.501 [7].
+
+For each QoS flow which has been successfully established in the new NG-RAN node, if the *ECN Marking or Congestion Information Reporting Request* IE is included in the *PDU Session Resources To Be Setup List* IE contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use it accordingly for the specific QoS flow.
+
+If the *5GC Mobility Restriction List Container* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, store this information in the UE context and use it as specified in TS 38.300 [9].
+
+V2X:
+
+- If the *NR V2X Services Authorized* IE is included in the RETRIEVE UE CONTEXT RESPONSE message and it contains one or more IEs set to "authorized", the new NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+
+- If the *LTE V2X Services Authorized* IE is included in the RETRIEVE UE CONTEXT RESPONSE message and it contains one or more IEs set to "authorized", the new NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *NR UE Sidelink Aggregate Maximum Bit Rate* IE is included in the *UE Context Information Retrieve UE Context Response* IE in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for NR V2X services.
+- If the *LTE UE Sidelink Aggregate Maximum Bit Rate* IE is included in the *UE Context Information Retrieve UE Context Response* IE in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services.
+
+## A2X:
+
+- If the *NR A2X Services Authorized* IE is included in the RETRIEVE UE CONTEXT RESPONSE message and it contains one or more IEs set to "authorized", the new NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *LTE A2X Services Authorized* IE is included in the RETRIEVE UE CONTEXT RESPONSE message and it contains one or more IEs set to "authorized", the new NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *NR A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the *UE Context Information – Retrieve UE Context Response* IE in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for NR A2X services.
+- If the *LTE A2X UE PC5 Aggregate Maximum Bit Rate* IE is included in the *UE Context Information – Retrieve UE Context Response* IE in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services.
+- If the *A2X PC5 QoS Parameters* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use it as defined in TS 23.256 [56].
+
+## 5G ProSe:
+
+- If the *5G ProSe Authorized* IE is included in the RETRIEVE UE CONTEXT RESPONSE message and it contains one or more IEs set to "authorized", the new NG-RAN node shall, if supported, consider that the UE is authorized for the relevant service(s).
+- If the *5G ProSe UE PC5 Aggregate Maximum Bit Rate* IE is included in the *UE Context Information - Retrieve UE Context Response* IE in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use the received value for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services.
+- If the *5G ProSe PC5 QoS Parameters* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use it as defined in TS 23.304 [48].
+
+If the *PC5 QoS Parameters* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use it as defined in TS 23.287[38].
+
+In case of RRC Re-establishment, the old NG-RAN may include the *UE History Information* IE or the *UE History Information from the UE* IE in the RETRIEVE UE CONTEXT RESPONSE message. Upon reception of the *UE History Information* IE or the *UE History Information from the UE* IE in the RETRIEVE UE CONTEXT RESPONSE
+
+message, the new NG-RAN node shall, if supported, store the collected information and use it for future handover preparations.
+
+If the *UE Radio Capability ID IE* is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported store this information in the UE context and use it as defined in TS 23.501 [7] and TS 23.502 [13].
+
+If the *Aerial UE Subscription Information IE* is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 38.300 [9].
+
+If the *Management Based MDT PLMN List IE* is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, store it in the UE context, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [23].
+
+If the *MBS Session Information List IE* is included in the *UE Context Information – Retrieve UE Context Response IE* contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use this information to establish an NG-RAN MBS session resources context, if applicable.
+
+If the RETRIEVE UE CONTEXT RESPONSE message includes the *MBS Area Session ID IE*, the new NG-RAN node shall, if supported, use this information as an indication in which MBS Area Session ID the UE has been suspended. For each MBS session for which the *Active MBS Session Information IE* is included in the *MBS Session Information Item IE*, the new NG-RAN node shall, if supported, use this information to setup respective MBS session resources. The new NG-RAN node shall, if supported, consider that the MBS sessions for which the *Active MBS Session Information IE* is not included are inactive.
+
+If the *IAB Node Indication IE* is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, consider that the procedure is performed for an IAB-node. In addition:
+
+- If the *No PDU Session Indication IE* is contained in the *UE Context Information – Retrieve UE Context Response IE* of the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, consider the UE as an IAB-node which does not have any PDU sessions activated, and ignore the *PDU Session Resources To Be Setup List IE* in the *UE Context Information – Retrieve UE Context Response IE*, and shall not take any action with respect to PDU session setup.
+
+If the *Time Synchronisation Assistance Information IE* is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [7].
+
+If the *QMC Configuration Information IE* is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, take it into account for QoE measurements handling, as described in TS 38.300 [9].
+
+If the *SDT Support Request IE* is included in the RETRIEVE UE CONTEXT REQUEST message, the old NG-RAN node shall, if supported, consider that the UE has requested for SDT as defined in TS 38.300 [9].
+
+If the *UE Slice-Maximum Bit Rate List IE* is contained in RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, store the received UE Slice Maximum Bit Rate List in the UE context, and use the received UE Slice Maximum Bit Rate value for each S-NSSAI for the concerned UE as specified in TS 23.501 [7].
+
+If the *Positioning Information IE* is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, take it into account to allocate proper SRS resources and make corresponding response to LMF when positioning a UE.
+
+If the *PNI-NPN Area Scope of MDT IE* is included in the *MDT Configuration-NR IE* included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN. Upon reception of the *PNI-NPN Area Scope of MDT IE*, the new NG-RAN node shall consider that the area scope for MDT measurement collections of PNI-NPN areas is defined only by the areas included in the *PNI-NPN Area Scope of MDT IE*.
+
+If the UE is a mobile IAB-node, the old NG-RAN node shall include the *Mobile IAB Authorization Status* IE in the RETRIEVE UE CONTEXT RESPONSE message. If the *Mobile IAB Authorization Status* IE is included in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node shall, if supported, store the received mobile IAB authorization status information in the UE context and use it accordingly.
+
+#### Interaction with the Retrieve UE Context Confirm procedure
+
+If the *UE Context Reference at the S-NG-RAN* IE is contained in the RETRIEVE UE CONTEXT RESPONSE message, the new NG-RAN node may use it to establish dual connectivity with the S-NG-RAN node and shall trigger the Retrieve UE Context Confirm procedure to the old NG-RAN node when the UE successfully resumes on the new NG-RAN node.
+
+### 8.2.4.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant old NG-RAN node
+ participant new NG-RAN node
+ Note left of old NG-RAN node:
+ Note right of new NG-RAN node:
+ new NG-RAN node->>old NG-RAN node: RETRIEVE UE CONTEXT REQUEST
+ old NG-RAN node-->>new NG-RAN node: RETRIEVE UE CONTEXT FAILURE
+
+```
+
+The diagram illustrates a sequence of messages between two nodes: 'old NG-RAN node' on the left and 'new NG-RAN node' on the right. Each node is represented by a rectangle with a vertical line extending downwards to a horizontal bar. The 'new NG-RAN node' sends a 'RETRIEVE UE CONTEXT REQUEST' message to the 'old NG-RAN node'. The 'old NG-RAN node' responds with a 'RETRIEVE UE CONTEXT FAILURE' message to the 'new NG-RAN node'.
+
+Sequence diagram showing an unsuccessful Retrieve UE Context operation between an old NG-RAN node and a new NG-RAN node.
+
+**Figure 8.2.4.3-1: Retrieve UE Context, unsuccessful operation**
+
+If the old NG-RAN node is not able to identify the UE context by means of the UE Context ID, or if the integrity protection contained in the RETRIEVE UE CONTEXT REQUEST message is not valid, or, if it decides not to provide the UE context to the new NG-RAN node, it shall respond to the new NG-RAN node with the RETRIEVE UE CONTEXT FAILURE message.
+
+If the old NG-RAN node decides to keep the UE context in case of periodic RNAU or in case of RACH based SDT, it shall store the *Allocated C-RNTI* IE and the *Access PCI* IE in the *UE Context ID* IE, as described in TS 38.300 [9].
+
+If the *Old NG-RAN node to New NG-RAN node Resume Container* IE is included in the RETRIEVE UE CONTEXT FAILURE message, the new NG-RAN node should transparently forward the content of this IE to the UE as described in TS 38.300 [9].
+
+#### Interaction with Partial UE Context Transfer procedure
+
+In case of RACH based SDT, if the old NG-RAN node decides to not transfer/relocate the UE Context to the new NG-RAN node, it may trigger the Partial UE Context Transfer procedure as specified in TS 38.300 [9]. After the old NG-RAN node has decided to end the SDT session, it shall terminate the Retrieve UE Context procedure by sending the RETRIEVE UE CONTEXT FAILURE message.
+
+### 8.2.4.4 Abnormal Conditions
+
+If both the *PNI-NPN Area Scope of MDT* IE and the *Area Scope of MDT-NR* IE are included in the *MDT Configuration-NR* IE in the RETRIEVE UE CONTEXT RESPONSE message, and the *Area Scope of MDT-NR* IE is set to "PNI-NPN based", the new NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas, and ignore the *PNI-NPN Area Scope of MDT* IE.
+
+If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE in the RETRIEVE UE CONTEXT RESPONSE message, and the *Area Scope of MDT-NR* IE is not included, the target NG-RAN node shall ignore the
+
+*PNI-NPN Area Scope of MDT IE*, and consider that the MDT Configuration for NR is applied to all PLMNs indicated in the MDT PLMN List described in TS 32.422 [23].
+
+## 8.2.5 RAN Paging
+
+### 8.2.5.1 General
+
+The purpose of the RAN Paging procedure is to enable the NG-RAN node<sub>1</sub> to request paging of a UE in the NG-RAN node<sub>2</sub>.
+
+The procedure uses non UE-associated signalling.
+
+### 8.2.5.2 Successful operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+ NG-RAN node1->>NG-RAN node2: RAN PAGING
+
+```
+
+Diagram illustrating the successful operation of RAN Paging. Two vertical lines represent NG-RAN node1 and NG-RAN node2. A horizontal arrow labeled 'RAN PAGING' points from node1 to node2. Each node has a small horizontal bar at its base.
+
+**Figure 8.2.5.2-1: RAN Paging: successful operation**
+
+The RAN Paging procedure is triggered by the NG-RAN node<sub>1</sub> by sending the RAN PAGING message to the NG-RAN node<sub>2</sub>, in which the necessary information e.g. UE RAN Paging Identity should be provided.
+
+If the *Paging Priority IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> may use it to prioritize paging.
+
+If the *Assistance Data for RAN Paging IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> may use it according to TS 38.300 [9].
+
+If the *UE Radio Capability for Paging IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> may use it to apply specific paging schemes.
+
+If the *Extended UE Identity Index Value IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> may use it according to TS 36.304 [34], and for eDRX or the UE\_ID based subgrouping according to TS 38.304 [33]. When available, NG-RAN node<sub>1</sub> may include the *Extended UE Identity Index Value IE* in the RAN PAGING message towards the NG-RAN node<sub>2</sub>.
+
+When available, the NG-RAN node<sub>1</sub> shall include the *E-UTRA Paging eDRX Information IE* in the RAN PAGING message towards the NG-RAN node<sub>2</sub>. If the *E-UTRA Paging eDRX Information IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 36.304 [34].
+
+When available, the NG-RAN node<sub>1</sub> shall include the *UE Specific DRX IE* in the RAN PAGING message towards the NG-RAN node<sub>2</sub>. If the *UE specific DRX IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 36.304 [34].
+
+When available, the NG-RAN node<sub>1</sub> shall include the *NR Paging eDRX Information IE* in the RAN PAGING message towards the NG-RAN node<sub>2</sub>. If the *NR Paging eDRX Information IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.304 [33].
+
+If the *NR Paging eDRX Information for RRC INACTIVE IE* is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.304 [33].
+
+When available, the NG-RAN node<sub>1</sub> shall include the *Paging Cause* IE in the RAN PAGING message towards the NG-RAN node<sub>2</sub>. If the *Paging Cause* IE is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.331 [10].
+
+When available, the NG-RAN node<sub>1</sub> shall include the *Hashed UE Identity Index Value* IE in the RAN PAGING message towards the NG-RAN node<sub>2</sub>. If the *Hashed UE Identity Index Value* IE is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.304 [33] or TS 36.304 [34].
+
+If the *PEIPS Assistance Information* IE is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.300 [9].
+
+If the *MT-SDT Information* IE is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.300 [9].
+
+If the *NR Paging Long eDRX Information for RRC INACTIVE* IE is included in the RAN PAGING message, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.304 [33].
+
+### 8.2.5.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.5.4 Abnormal Condition
+
+Void.
+
+## 8.2.6 XN-U Address Indication
+
+### 8.2.6.1 General
+
+For the retrieval of a UE context, the Xn-U Address Indication procedure is used to provide forwarding addresses from the new NG-RAN node to the old NG-RAN node for all PDU session resources successfully established at the new NG-RAN node for which forwarding was requested, and/or all MBS session resources successfully established at the new NG-RAN node for which forwarding was requested.
+
+For MR-DC with 5GC, the Xn-U Address Indication procedure is used to provide data forwarding related information, and Xn-U bearer address information for completion of setup of SN terminated bearers from the M-NG-RAN node to the S-NG-RAN node as specified in TS 37.340 [8].
+
+The procedure uses UE-associated signalling.
+
+### 8.2.6.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant old NG-RAN node
+ participant new NG-RAN node
+ Note right of new NG-RAN node: Successful operation for UE context retrieval
+ new NG-RAN node->>old NG-RAN node: XN-U ADDRESS INDICATION
+```
+
+Sequence diagram showing the Xn-U Address Indication procedure. A 'new NG-RAN node' on the right sends an 'XN-U ADDRESS INDICATION' message to an 'old NG-RAN node' on the left. Both nodes are represented by boxes with vertical lines extending downwards to horizontal bars representing the timeline.
+
+Figure 8.2.6.2-1: Xn-U Address Indication, successful operation for UE context retrieval
+
+
+
+```
+
+graph LR
+ M[M-NG-RAN node] -- XN-U ADDRESS INDICATION --> S[S-NG-RAN node]
+ M --- UP(( ))
+ S --- UP
+ style UP fill:black,stroke:none
+
+```
+
+Diagram showing the Xn-U Address Indication procedure. An M-NG-RAN node on the left sends an XN-U ADDRESS INDICATION message to an S-NG-RAN node on the right. Both nodes are connected to a common horizontal line at the bottom, representing the user plane path.
+
+**Figure 8.2.6.2-2: Xn-U Address Indication, successful operation for MR-DC with 5GC**
+
+#### UE Context Retrieval
+
+The Xn-U Address Indication procedure is initiated by the new NG-RAN node. Sending the XN-U ADDRESS INDICATION message, the new NG-RAN node informs the old NG-RAN node of successfully established PDU Session Resource contexts, or MBS session resource contexts, or both, to which user data pending at the old NG-RAN node can be forwarded.
+
+The new NG-RAN node may include *Secondary Data Forwarding Info from target NG-RAN node List* IE for an additional Xn-U tunnel for data forwarding.
+
+Upon reception of the XN-U ADDRESS INDICATION message, the old NG-RAN node should forward pending user data to the indicated TNL addresses.
+
+If the XN-U ADDRESS INDICATION message includes the *MBS Data Forwarding Indicator* IE set to "MBS-only", the old NG-RAN node shall, if supported, consider that the XN-U ADDRESS INDICATION message only concerns data forwarding of the indicated MBS sessions.
+
+If the XN-U ADDRESS INDICATION message includes the *MBS Session Information Response List* IE, the old NG-RAN node shall, if supported, use the information for forwarding MBS traffic to the new NG-RAN node.
+
+#### MR-DC with 5GC
+
+The Xn-U Address Indication procedure is initiated by the M-NG-RAN node.
+
+Upon reception of the XN-U ADDRESS INDICATION message, in case of data forwarding, the S-NG-RAN node should forward pending DL user data to the indicated TNL addresses; in case *Data Forwarding Info from target E-UTRAN node* IE is received, the S-NG-RAN node should perform inter-system direct data forwarding to the indicated TNL addresses as specified in TS38.300 [9]; in case of completion of Xn-U bearer establishment for SN terminated bearers, the S-NG-RAN node may start delivery of user data to the indicated TNL address, and shall, if supported, use the received *QoS Mapping Information* IE within the *DRBs to Be Setup List* IE in the *PDU Session Resource Setup Complete Info – SN terminated* IE to set DSCP and/or IPv6 flow label fields for the delivery of user data to the indicated TNL address.
+
+If the XN-U ADDRESS INDICATION message includes the *DRB IDs taken into use* IE, the S-NG-RAN node shall, if applicable, act as specified in TS 37.340 [8].
+
+If the XN-U ADDRESS INDICATION message includes the *CHO MR-DC Indicator* IE, the S-NG-RAN node shall, if supported, consider that the XN-U ADDRESS INDICATION message concerns a Conditional Handover, and act as specified in TS 37.340 [8].
+
+If the XN-U ADDRESS INDICATION message includes the *CHO MR-DC Early Data Forwarding Indicator* IE set to "stop", the S-NG-RAN node shall, if supported and if already initiated, stop early data forwarding for the provided Data Forwarding Address information.
+
+If the XN-U ADDRESS INDICATION message includes the *CPC Data Forwarding indicator* IE set to "triggered", the S-NG-RAN node shall, if supported, consider that the XN-U ADDRESS INDICATION message concerns a
+
+Conditional PSCell Change, and act as specified in TS 37.340 [8]. If the *CPC Data Forwarding Indicator* IE is present and value set to "early data transmission stop", the S-NG-RAN node shall, if supported and if already initiated, stop early data forwarding for the provided Data Forwarding Address information.
+
+**Interaction with the S-NG-RAN node initiated S-NG-RAN node Modification procedure:**
+
+If the *CHO MR-DC Indicator* IE or the *CPC Data Forwarding indicator* IE is set to "coordination-only" in the XN-U ADDRESS INDICATION message and if any SCG reconfiguration is executed, the S-NG-RAN node shall, if supported, trigger the S-NG-RAN node initiated S-NG-RAN node Modification procedure to inform the M-NG-RAN node as specified in TS 37.340 [8].
+
+### 8.2.6.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.6.4 Abnormal Conditions
+
+Void.
+
+## 8.2.7 UE Context Release
+
+### 8.2.7.1 General
+
+For handover, the UE Context Release procedure is initiated by the target NG-RAN node to indicate to the source NG-RAN node that radio and control plane resources for the associated UE context are allowed to be released.
+
+For dual connectivity, the UE Context Release procedure is initiated by the M-NG-RAN node to initiate the release the UE context at the S-NG-RAN node. For dual connectivity specific mobility scenarios specified in TS 37.340 [8], where SCG radio resources in the S-NG-RAN node are kept, only resources related to the UE-associated signalling connection between the M-NG-RAN node and the S-NG-RAN node are released.
+
+For UE context retrieval, the UE Context Release procedure is initiated by the new NG-RAN node to indicate to the old NG-RAN node that radio and control plane resources for the associated UE context are allowed to be released.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.7.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant target NG-RAN node
+ participant source NG-RAN node
+ Note right of target: UE CONTEXT RELEASE
+ target->>source: UE CONTEXT RELEASE
+```
+
+Sequence diagram showing the successful operation of UE Context Release for handover. A 'target NG-RAN node' sends a 'UE CONTEXT RELEASE' message to a 'source NG-RAN node'.
+
+**Figure 8.2.7.2-1: UE Context Release, successful operation for handover**
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of S-NG-RAN node: UE
+ Note right of M-NG-RAN node: UE
+ M-NG-RAN node->>S-NG-RAN node: UE CONTEXT RELEASE
+
+```
+
+Sequence diagram for UE Context Release in dual connectivity. It shows two nodes: S-NG-RAN node and M-NG-RAN node. A message labeled 'UE CONTEXT RELEASE' is sent from the M-NG-RAN node to the S-NG-RAN node. Both nodes have a vertical timeline with a black bar at the bottom representing the user equipment (UE).
+
+Figure 8.2.7.2-2: UE Context Release, successful operation for dual connectivity
+
+
+
+```
+
+sequenceDiagram
+ participant New NG-RAN node
+ participant Old NG-RAN node
+ Note left of Old NG-RAN node: UE
+ Note right of New NG-RAN node: UE
+ New NG-RAN node->>Old NG-RAN node: UE CONTEXT RELEASE
+
+```
+
+Sequence diagram for UE Context Release in UE context retrieval. It shows two nodes: Old NG-RAN node and New NG-RAN node. A message labeled 'UE CONTEXT RELEASE' is sent from the New NG-RAN node to the Old NG-RAN node. Both nodes have a vertical timeline with a black bar at the bottom representing the user equipment (UE).
+
+Figure 8.2.7.2-3: UE Context Release, successful operation for UE context retrieval
+
+#### Handover
+
+The UE Context Release procedure is initiated by the target NG-RAN node. By sending the UE CONTEXT RELEASE message the target NG-RAN node informs the source NG-RAN node of Handover success and triggers the release of resources.
+
+Upon reception of the UE CONTEXT RELEASE message, the source NG-RAN node may release radio and control plane related resources associated to the UE context. If data forwarding has been performed, the source NG-RAN node should continue forwarding of user plane data as long as packets are received at the source NG-RAN node.
+
+#### Dual Connectivity
+
+The UE Context Release procedure is initiated by the M-NG-RAN node. By sending the UE CONTEXT RELEASE message the M-NG-RAN node informs the S-NG-RAN node that the UE Context can be removed.
+
+Upon reception of the UE CONTEXT RELEASE message, the S-NG-RAN node may release radio and control plane related resources associated to the UE context. If data forwarding has been performed, the S-NG-RAN node should continue forwarding of user plane data as long as packets are received at the S-NG-RAN node.
+
+#### UE Context Retrieval
+
+The UE Context Release procedure is initiated by the new NG-RAN node. By sending the UE CONTEXT RELEASE message the new NG-RAN node informs the old NG-RAN node of RRC connection reestablishment success or RRC connection resumption success and triggers the release of resources.
+
+#### Interaction with the M-NG-RAN node initiated S-NG-RAN node Release procedure:
+
+The S-NG-RAN node may receive the S-NODE RELEASE REQUEST message including the *UE Context Kept Indicator* IE set to "True", upon which the S-NG-RAN node shall, if supported, only release the resources related to the UE-associated signalling connection between the M-NG-RAN node and the S-NG-RAN node, as specified in TS 37.340 [8].
+
+### 8.2.7.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.7.4 Abnormal Conditions
+
+If the UE Context Release procedure is not initiated towards the source NG-RAN node from any prepared NG-RAN node before the expiry of the timer $TXn_{RELOCoverall}$ , the source NG-RAN node shall request the AMF to release the UE context.
+
+If the UE returns to source NG-RAN node before the reception of the UE CONTEXT RELEASE message or the expiry of the timer $TXn_{RELOCoverall}$ , the source NG-RAN node shall stop the $TXn_{RELOCoverall}$ and continue to serve the UE.
+
+## 8.2.8 Handover Success
+
+### 8.2.8.1 General
+
+The Handover Success procedure is used during a conditional handover or a DAPS handover to enable a target NG-RAN node to inform the source NG-RAN node that the UE has successfully accessed the target NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.8.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant target NG-RAN node
+ participant source NG-RAN node
+ Note left of target: UE successfully accessed
+ target->>source: HANDOVER SUCCESS
+ Note right of source: Received HANDOVER SUCCESS
+```
+
+Sequence diagram showing the Handover Success procedure. A 'target NG-RAN node' sends a 'HANDOVER SUCCESS' message to a 'source NG-RAN node'. The message is represented by a horizontal arrow pointing from the target node to the source node. Both nodes are represented by rectangular boxes with vertical lines extending downwards to horizontal bars representing the timeline of the procedure.
+
+**Figure 8.2.8.2-1: Handover Success, successful operation**
+
+The target NG-RAN node initiates the procedure by sending the HANDOVER SUCCESS message to the source NG-RAN node.
+
+If late data forwarding was configured for this UE, the source NG-RAN node shall start data forwarding using the tunnel information related to the global target cell ID provided in the HANDOVER SUCCESS message.
+
+When the source NG-RAN node receives the HANDOVER SUCCESS message, it shall consider all other CHO preparations accepted for this UE under the same UE-associated signalling connection in the target NG-RAN node as cancelled.
+
+### Interactions with other procedures
+
+If a CONDITIONAL HANDOVER CANCEL message was received for this UE prior the reception of the HANDOVER SUCCESS message, the source NG-RAN node shall consider that the UE successfully executed the handover.
+
+The source NG-RAN node may initiate Handover Cancel procedure towards the other signalling connections or other candidate target NG-RAN nodes for this UE, if any.
+
+### 8.2.8.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.8.4 Abnormal Conditions
+
+If the HANDOVER SUCCESS message refers to a context that does not exist, the source NG-RAN node shall ignore the message.
+
+## 8.2.9 Conditional Handover Cancel
+
+### 8.2.9.1 General
+
+The Conditional Handover Cancel procedure is used to enable a target NG-RAN node to cancel an already prepared conditional handover or an already prepared conditional reconfiguration.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.9.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant Target NG-RAN node
+ participant Source NG-RAN node
+ Note left of Target NG-RAN node:
+ Note right of Source NG-RAN node:
+ Target NG-RAN node->>Source NG-RAN node: CONDITIONAL HANDOVER CANCEL
+```
+
+Sequence diagram showing the successful operation of Conditional Handover Cancel. A Target NG-RAN node sends a CONDITIONAL HANDOVER CANCEL message to a Source NG-RAN node.
+
+**Figure 8.2.9.2-1: Conditional Handover Cancel, successful operation**
+
+The target NG-RAN node initiates the procedure by sending the CONDITIONAL HANDOVER CANCEL message to the source NG-RAN node. The target NG-RAN node shall indicate the reason for cancelling the conditional handover or the conditional reconfiguration by means of an appropriate cause value.
+
+At the reception of the CONDITIONAL HANDOVER CANCEL message, the source NG-RAN node shall consider that the target NG-RAN node is about to remove any reference to, and release any resources previously reserved for candidate cells associated to the UE-associated signalling identified by the *Source NG-RAN node UE XnAP ID* IE and the *Target NG-RAN node UE XnAP ID* IE. If the *Candidate Cells To Be Cancelled List* IE is included in CONDITIONAL HANDOVER CANCEL message, the source NG-RAN node shall consider that only the resources reserved for the cells identified by the included NG-RAN CGI are about to be released.
+
+If the *Conditional Reconfigurations To Be Cancelled List* IE is included in the CONDITIONAL HANDOVER CANCEL message, the source NG-RAN node shall, if supported, consider that only the resources reserved for the cell(s) identified by the included NG-RAN CGI(s) are about to be released.
+
+### 8.2.9.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.9.4 Abnormal Conditions
+
+If the CONDITIONAL HANDOVER CANCEL message refers to a context that does not exist, the source NG-RAN node shall ignore the message.
+
+If one or more candidate cells in the *Candidate Cells To Be Cancelled List* IE included in the CONDITIONAL HANDOVER CANCEL message were not prepared using the same UE-associated signaling connection, the source NG-RAN node shall ignore those non-associated candidate cells.
+
+## 8.2.10 Early Status Transfer
+
+### 8.2.10.1 General
+
+The purpose of the Early Status Transfer procedure is to transfer the COUNT of the first downlink SDU that the source NG-RAN node forwards to the target NG-RAN node or the COUNT for discarding of already forwarded downlink SDUs for respective DRB during DAPS Handover or Conditional Handover.
+
+For MR-DC with 5GC, the Early Status Transfer procedure is also used from the source S-NG-RAN node to the source M-NG-RAN node during a Conditional Handover as specified in TS 37.340 [8].
+
+For Conditional PSCell Addition in MR-DC with NR SCG, the Early Status Transfer procedure is also used, from the M-NG-RAN node to the S-NG-RAN node as specified in TS 37.340 [8].
+
+For Conditional PSCell Change in MR-DC with NR SCG, the Early Status Transfer procedure is also used from the source S-NG-RAN node to the M-NG-RAN node, and from the M-NG-RAN node to the target S-NG-RAN node as specified in TS 37.340 [8].
+
+The procedure uses UE-associated signalling.
+
+### 8.2.10.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant source NG-RAN node
+ participant target NG-RAN node
+ Note left of source: source NG-RAN node
+ Note right of target: target NG-RAN node
+ source->>target: EARLY STATUS TRANSFER
+```
+
+The diagram shows two vertical lines representing the source and target NG-RAN nodes. Each node is represented by a box with its name and a thick horizontal bar at the bottom. A horizontal arrow labeled 'EARLY STATUS TRANSFER' points from the source node to the target node.
+
+Diagram illustrating the Early Status Transfer procedure during DAPS Handover or Conditional Handover, successful operation. A source NG-RAN node sends an EARLY STATUS TRANSFER message to a target NG-RAN node.
+
+**Figure 8.2.10.2-1: Early Status Transfer during DAPS Handover or Conditional Handover, successful operation**
+
+
+
+Diagram of Early Status Transfer during Conditional Handover in MR-DC operation, successful operation. It shows a 'source S-NG-RAN node' on the left and a 'source M-NG-RAN node' on the right. A horizontal arrow labeled 'EARLY STATUS TRANSFER' points from the S-NG-RAN node to the M-NG-RAN node. Both nodes are connected to a common horizontal line at the bottom, representing the UE.
+
+**Figure 8.2.10.2-2: Early Status Transfer during Conditional Handover in MR-DC operation, successful operation**
+
+
+
+Diagram of Early Status Transfer during CPAC, successful operation. It shows an 'M-NG-RAN node/ source S-NG-RAN node' on the left and a '(target) S-NG-RAN node/ M-NG-RAN node' on the right. A horizontal arrow labeled 'EARLY STATUS TRANSFER' points from the left node to the right node. Both nodes are connected to a common horizontal line at the bottom, representing the UE.
+
+**Figure 8.2.10.2-3: Early Status Transfer during CPAC, successful operation**
+
+#### From source NG-RAN node to target NG-RAN node
+
+The *DRBs Subject To Early Status Transfer List* IE included in the EARLY STATUS TRANSFER message contains the DRB ID(s) corresponding to the DRB(s) subject to be simultaneously served by the source and the target NG-RAN nodes during DAPS Handover or the DRB(s) transferred during Conditional Handover.
+
+For each DRB in the *DRBs Subject To Early Status Transfer List* IE, the target NG-RAN node shall use the value of the *FIRST DL COUNT Value* IE as the COUNT of the first downlink SDU that the source NG-RAN node forwards to the target NG-RAN node.
+
+For each DRB in the *DRBs Subject To Early Status Transfer List* IE for which the *DISCARD DL COUNT Value* IE is received in the EARLY STATUS TRANSFER message, the target NG-RAN node does not transmit forwarded downlink SDUs to the UE whose COUNT is less than the provided and discards them if transmission has not been attempted.
+
+#### From source S-NG-RAN node to source M-NG-RAN node, the source NG-RAN node for Conditional Handover
+
+The *DRBs Subject To Early Status Transfer List* IE included in the EARLY STATUS TRANSFER message contains the DRB ID(s) corresponding to the DRB(s) transferred during Conditional Handover.
+
+For each DRB in the *DRBs Subject To Early Status Transfer List* IE, the source M-NG-RAN node shall forward to the target, the value of the received *FIRST DL COUNT Value* IE or *DISCARD DL COUNT Value* IE.
+
+#### From M-NG-RAN node to S-NG-RAN node, for Conditional PSCell Addition
+
+The *DRBs Subject To Early Status Transfer List* IE included in the EARLY STATUS TRANSFER message contains the DRB ID(s) corresponding to the DRB(s) transferred during Conditional PSCell Addition.
+
+For each DRB in the *DRBs Subject To Early Status Transfer List* IE, the M-NG-RAN node shall forward to the S-NG-RAN node, the value of the received *FIRST DL COUNT Value* IE or *DISCARD DL COUNT Value* IE.
+
+**From source S-NG-RAN node to M-NG-RAN node, and from M-NG-RAN node to target S-NG-RAN node, for Conditional PSCell Change**
+
+The *DRBs Subject To Early Status Transfer List* IE included in the EARLY STATUS TRANSFER message contains the DRB ID(s) corresponding to the DRB(s) transferred during Conditional PSCell Change.
+
+For each DRB in the *DRBs Subject To Early Status Transfer List* IE, the source S-NG-RAN node shall forward to the M-NG-RAN node and the M-NG-RAN node shall forward to the target S-NG-RAN node, during Conditional PSCell Change, the value of the received *FIRST DL COUNT Value* IE or *DISCARD DL COUNT Value* IE.
+
+#### 8.2.10.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.2.10.4 Abnormal Conditions
+
+If the target NG-RAN node receives this message for a UE for which no prepared DAPS Handover or Conditional Handover exists at the target NG-RAN node, the target NG-RAN node shall ignore the message.
+
+### 8.2.11 RAN Multicast Group Paging
+
+#### 8.2.11.1 General
+
+The purpose of the RAN Multicast Group Paging procedure is to enable the NG-RAN node<sub>1</sub> to request paging of UEs that have joined an MBS Session in the NG-RAN node<sub>2</sub>.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.2.11.2 Successful operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: RAN MULTICAST GROUP PAGING
+ Note right of NG-RAN node2:
+ style NG-RAN node1 fill:#fff,stroke:#000
+ style NG-RAN node2 fill:#fff,stroke:#000
+```
+
+The diagram illustrates the successful operation of RAN Multicast Group Paging. It features two vertical lifelines representing NG-RAN node<sub>1</sub> and NG-RAN node<sub>2</sub>. A horizontal arrow labeled "RAN MULTICAST GROUP PAGING" originates from the lifeline of NG-RAN node<sub>1</sub> and points to the lifeline of NG-RAN node<sub>2</sub>. Both lifelines terminate in a thick horizontal bar at the bottom.
+
+Sequence diagram showing the successful operation of RAN Multicast Group Paging. NG-RAN node1 sends a RAN MULTICAST GROUP PAGING message to NG-RAN node2.
+
+**Figure 8.2.11.2-1: RAN Multicast Group Paging, successful operation**
+
+The RAN Multicast Group Paging procedure is triggered by the NG-RAN node<sub>1</sub> by sending the RAN MULTICAST GROUP PAGING message to the NG-RAN node<sub>2</sub>.
+
+If the RAN MULTICAST GROUP PAGING message includes the *Paging DRX* IE, the NG-RAN node<sub>2</sub> shall, if supported, use it according to TS 38.304 [33].
+
+## 8.2.12 Retrieve UE Context Confirm
+
+### 8.2.12.1 General
+
+The Retrieve UE Context Confirm procedure is used by the new NG-RAN node to inform the old NG-RAN node whether the S-NG-RAN node associated with the old NG-RAN node for the UE that was indicated during UE context retrieval is kept or not by the new NG-RAN node during RRC resumption.
+
+In case of RACH based SDT without UE context relocation, the Retrieve UE Context Confirm procedure is also used to request the termination of SDT session from the new NG-RAN node to the old NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.12.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant old NG-RAN node
+ participant new NG-RAN node
+ Note left of old NG-RAN node:
+ Note right of new NG-RAN node:
+ new NG-RAN node->>old NG-RAN node: RETRIEVE UE CONTEXT CONFIRM
+ Note left of old NG-RAN node:
+ Note right of new NG-RAN node:
+```
+
+Sequence diagram showing the successful operation of Retrieve UE Context Confirm. A 'new NG-RAN node' sends a 'RETRIEVE UE CONTEXT CONFIRM' message to an 'old NG-RAN node'.
+
+**Figure 8.2.12.2-1: Retrieve UE Context Confirm, successful operation**
+
+The new NG-RAN node initiates the procedure by sending the RETRIEVE UE CONTEXT CONFIRM message to the old NG-RAN node.
+
+Upon reception of the RETRIEVE UE CONTEXT CONFIRM message, the old NG-RAN node shall release the resources related to the UE-associated signalling connection between the old NG-RAN node and the new NG-RAN node, as specified in TS 37.340 [8].
+
+If the *UE Context Kept Indicator* IE is included and set to "True", the old NG-RAN node shall consider that the S-NG-RAN node was kept by the new NG-RAN node and use this information as specified in TS 37.340 [8].
+
+If the old NG-RAN node receives the *SDT Termination Request* IE in the RETRIEVE UE CONTEXT CONFIRM message, the old NG-RAN node shall, if supported, consider that the termination of the ongoing SDT session is requested from the new NG-RAN node for this UE and act as specified in TS 38.300 [9]. If the *SDT Termination Request* IE set to "Large SDT volume from BSR" is included, the old NG-RAN node shall, if supported, consider that the UL SDT data size in the BSR received from the UE is larger than the SDT volume threshold of the new NG-RAN node, and act as specified in TS 38.300 [9].
+
+### 8.2.12.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.2.12.4 Abnormal Conditions
+
+If the RETRIEVE UE CONTEXT CONFIRM message refers to a context that does not exist, the old NG-RAN node shall ignore the message.
+
+## 8.2.13 Partial UE Context Transfer
+
+### 8.2.13.1 General
+
+The purpose of the Partial UE Context Transfer procedure is to partially transfer the UE context from the old NG-RAN node to the new NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.2.13.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant old NG-RAN node
+ participant new NG-RAN node
+ Note left of new NG-RAN node:
+ Note right of old NG-RAN node:
+ old NG-RAN node->>new NG-RAN node: PARTIAL UE CONTEXT TRANSFER
+ new NG-RAN node-->>old NG-RAN node: PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE
+```
+
+The diagram illustrates the successful operation of the Partial UE Context Transfer procedure. It features two vertical lifelines: 'new NG-RAN node' on the left and 'old NG-RAN node' on the right. Each lifeline has a solid black horizontal bar at its base. The sequence of messages is as follows: an arrow labeled 'PARTIAL UE CONTEXT TRANSFER' points from the old NG-RAN node to the new NG-RAN node; a return arrow labeled 'PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE' points from the new NG-RAN node back to the old NG-RAN node.
+
+Sequence diagram for successful Partial UE Context Transfer
+
+**Figure 8.2.13.2-1: Partial UE Context Transfer, successful operation**
+
+The old NG-RAN node initiates the procedure by sending the PARTIAL UE CONTEXT TRANSFER message to the new NG-RAN node.
+
+If the new NG-RAN node is able to accept the SDT session without anchor relocation, it shall, if supported, respond to the old NG-RAN node with the PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE message.
+
+If the *Partial UE Context Information for SDT* IE is included in the PARTIAL UE CONTEXT TRANSFER message, the new NG-RAN node may include data forwarding related information in the *SDT Data Forwarding DRB List* IE in the PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE message.
+
+If the *Partial UE Context Information for Positioning* IE is contained in the PARTIAL UE CONTEXT TRANSFER message, the new NG-RAN node may take it into account to allocate proper SRS resources and include the *SRS Configuration* IE in the PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE message.
+
+### 8.2.13.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant old NG-RAN node
+ participant new NG-RAN node
+ Note left of new NG-RAN node:
+ Note right of old NG-RAN node:
+ old NG-RAN node->>new NG-RAN node: PARTIAL UE CONTEXT TRANSFER
+ new NG-RAN node-->>old NG-RAN node: PARTIAL UE CONTEXT TRANSFER FAILURE
+```
+
+The diagram illustrates the unsuccessful operation of the Partial UE Context Transfer procedure. It features two vertical lifelines: 'new NG-RAN node' on the left and 'old NG-RAN node' on the right. Each lifeline has a solid black horizontal bar at its base. The sequence of messages is as follows: an arrow labeled 'PARTIAL UE CONTEXT TRANSFER' points from the old NG-RAN node to the new NG-RAN node; a return arrow labeled 'PARTIAL UE CONTEXT TRANSFER FAILURE' points from the new NG-RAN node back to the old NG-RAN node.
+
+Sequence diagram for unsuccessful Partial UE Context Transfer
+
+**Figure 8.2.13.3-1: Partial UE Context Transfer, unsuccessful operation**
+
+If the new NG-RAN is not able to accept the SDT session without anchor relocation, it shall respond to the old NG-RAN node with the PARTIAL UE CONTEXT TRANSFER FAILURE message.
+
+### 8.2.13.4 Abnormal Condition
+
+Void.
+
+## 8.3 Procedures for Dual Connectivity
+
+### 8.3.1 S-NG-RAN node Addition Preparation
+
+#### 8.3.1.1 General
+
+The purpose of the S-NG-RAN node Addition Preparation procedure is to request the S-NG-RAN node to allocate resources for dual connectivity operation for a specific UE. Possible parallel requests are identified by the PCell ID when the source UE AP IDs are the same.
+
+The procedure uses UE-associated signalling.
+
+#### 8.3.1.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE ADDITION REQUEST
+ Note right of S-NG-RAN node:
+ S-NG-RAN node-->>M-NG-RAN node: S-NODE ADDITION REQUEST ACKNOWLEDGE
+ Note left of M-NG-RAN node:
+
+```
+
+Sequence diagram showing the successful operation of S-NG-RAN node Addition Preparation. The M-NG-RAN node sends an S-NODE ADDITION REQUEST to the S-NG-RAN node, and the S-NG-RAN node responds with an S-NODE ADDITION REQUEST ACKNOWLEDGE.
+
+**Figure 8.3.1.2-1: S-NG-RAN node Addition Preparation, successful operation**
+
+The M-NG-RAN node initiates the procedure by sending the S-NODE ADDITION REQUEST message to the S-NG-RAN node.
+
+When the M-NG-RAN node sends the S-NODE ADDITION REQUEST message, it shall start the timer $TXn_{DCprep}$ .
+
+The allocation of resources according to the values of the *Allocation and Retention Priority* IE included in the *QoS Flow Level QoS Parameters* IE for each QoS flow shall follow the principles specified for the PDU Session Resource Setup procedure in TS 38.413 [5].
+
+The S-NG-RAN node shall choose the ciphering algorithm based on the information in the *UE Security Capabilities* IE and locally configured priority list of AS encryption algorithms and apply the key indicated in the *S-NG-RAN node Security Key* IE as specified in TS 33.501 [28].
+
+If the *TSC Traffic Characteristics* IE is included for a QoS flow in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [5].
+
+If the *Additional QoS Flow Information* IE is included for a QoS flow in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [5].
+
+For each GBR QoS flow, if the *Alternative QoS Parameters Sets* IE is included in the *GBR QoS Flow Information* IE, the S-NG-RAN node shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure specified in TS 38.413 [5].
+
+For each PDU session, if the *Network Instance* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE contained in the *PDU Session Resources To Be Added List* IE and the *Common Network Instance* IE is not present, the S-NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].
+
+For each GBR QoS flow, if the *Offered GBR QoS Flow Information* IE is included in the *QoS Flows To Be Setup List* IE contained in the *PDU Session Resource Setup Info – SN terminated* IE, the S-NG-RAN node may request the M-NG-RAN node to configure the DRB to which that QoS flow is mapped with MCG resources.
+
+For each PDU session, if the *Non-GBR Resources Offered* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE contained in the *PDU Session Resources To Be Added List* IE and set to "true", the S-NG-RAN node may request the M-NG-RAN node to configure DRBs to which non-GBR QoS flows of the PDU session are mapped with MCG resources.
+
+For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE contained in the *PDU Session Resources To Be Added List* IE, the S-NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].
+
+Redundant transmission:
+
+- For each PDU session, if the *Redundant UL NG-U UP TNL Information at UPF* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE, the S-NG-RAN node shall, if supported, use it as the uplink termination point for the user plane data for this PDU session for the redundant transmission and it shall include the *Redundant DL NG-U UP TNL Information at NG-RAN* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE as described in TS 23.501 [7].
+- For each PDU session, if the *Redundant Common Network Instance* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE the S-NG-RAN node shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [7].
+- For each PDU session for which the *Redundant QoS Flow Indicator* IE is include in *QoS Flows To Be Setup List* IE contained in the *S-NODE ADDITION REQUEST* message, the S-NG-RAN node shall, if supported, store and use it as specified in TS 23.501 [7].
+- For each PDU session, if the *Redundant PDU Session Information* IE is included in the *PDU Session Resource Setup Info - SN terminated* IE in the *S-NODE ADDITION REQUEST* message, the S-NG-RAN node shall, if supported, store the received information in the UE context and setup the redundant user plane resources for the concerned PDU session, as specified in TS 23.501 [7].
+- For each PDU session resource successfully setup for which the *Redundant PDU Session Information* IE is included in the *S-NODE ADDITION REQUEST* message, the S-NG-RAN node shall, if supported, include the *Used RSN Information* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE in the *S-NODE ADDITION REQUEST ACKNOWLEDGE* message. If the *PDU Session Pair ID* IE is included in the *Redundant PDU Session Information* IE, the S-NG-RAN node may store and use it to identify the paired PDU sessions.
+
+If the *S-NODE ADDITION REQUEST* message contains the *Selected PLMN* IE, the S-NG-RAN node may use it for RRM purposes. If the *S-NODE ADDITION REQUEST* message also contains the *Selected NID* IE, the S-NG-RAN node may decide to use the SNPN identified by the *Selected PLMN* IE and *Selected NID* IE for its own usage.
+
+If the *S-NODE ADDITION REQUEST* message contains the *Expected UE Behaviour* IE, the S-NG-RAN node shall, if supported, store this information and may use it to optimize resource allocation.
+
+If the *S-NODE ADDITION REQUEST* message contains the *Mobility Restriction List* IE, the S-NG-RAN node, if supported, shall store this information and use it to select an appropriate SCG.
+
+If the *S-NODE ADDITION REQUEST* message contains the *Index to RAT/Frequency Selection Priority* IE, the S-NG-RAN node may use it for RRM purposes.
+
+If the S-NG-RAN node is a gNB and the S-NODE ADDITION REQUEST message contains the *PCell ID* IE, the S-NG-RAN node shall search for the target NR cell among the NR neighbour cells of the PCell indicated, as specified in the TS 37.340 [8].
+
+If the S-NODE ADDITION REQUEST message contains the *S-NG-RAN node PDU Session Aggregate Maximum Bit Rate* IE, the S-NG-RAN node may use it for RRM purposes.
+
+If the S-NODE ADDITION REQUEST message contains the *MR-DC Resource Coordination Information* IE, the S-NG-RAN node should forward it to lower layers and it may use it for the purpose of resource coordination with the M-NG-RAN node, or to coordinate with sidelink resources used in the M-NG-RAN node. The S-NG-RAN node shall consider the value of the received *UL Coordination Information* IE valid until reception of a new update of the IE for the same UE. The S-NG-RAN node shall consider the value of the received *DL Coordination Information* IE valid until reception of a new update of the IE for the same UE. If the *E-UTRA Coordination Assistance Information* IE or the *NR Coordination Assistance Information* IE is contained in the *MR-DC Resource Coordination Information* IE, the S-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the S-NG-RAN node and the M-NG-RAN node.
+
+If the S-NODE ADDITION REQUEST message contains the *NE-DC TDM Pattern* IE, the S-NG-RAN node should forward it to lower layers and use it for the purpose of single uplink transmission. The S-NG-RAN node shall consider the value of the received *NE-DC TDM Pattern* IE valid until reception of a new update of the IE for the same UE.
+
+If the S-NODE ADDITION REQUEST message contains the *QoS Flow Mapping Indication* IE, the S-NG-RAN node may take it into account that only the uplink or downlink QoS flow is mapped to the DRB.
+
+For each bearer for which allocation of the PDCP entity is requested at the S-NG-RAN node:
+
+- the M-NG-RAN node may propose to apply forwarding of downlink data by including the *DL Forwarding* IE within *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE ADDITION REQUEST message. For each bearer that it has decided to admit, the S-NG-RAN node may include the *DL Forwarding GTP Tunnel Endpoint* IE within the *PDU Session Resource Setup Response Info – SN terminated* IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding of downlink data for this bearer.
+- the S-NG-RAN node may include for each bearer in the *PDU Session Resource Setup Response Info – SN terminated* IE the *UL Forwarding GTP Tunnel Endpoint* IE to indicates it request data forwarding of uplink packets to be performed for that bearer.
+- the M-NG-RAN node shall include *RLC Mode* IE for each bearer offloaded from M-NG-RAN node to S-NG-RAN node in the *DRBs to QoS Flow Mapping List* IE within the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE ADDITION REQUEST message, and the *RLC Mode* IE indicates the mode that the M-NG-RAN used for the DRB when it was hosted at the M-NG-RAN node.
+
+For each bearer for which the PDCP entity is at the M-NG-RAN node:
+
+- the M-NG-RAN node shall include the *RLC mode* IE for each bearer in the *DRBs To Be Setup List* IE within the *PDU Session Resource Setup Info – MN terminated* IE of the S-NODE ADDITION REQUEST message to indicate the RLC mode has been configured at the M-NG-RAN node, so that the S-NG-RAN node shall configure the same RLC mode for this MN terminated split bearer.
+
+The M-NG-RAN node may also propose to apply forwarding of UL data when offloading QoS flows for which in-order delivery is requested by including the *UL Forwarding Proposal* IE in the *Data Forwarding and Offloading Info from source NG-RAN node* IE within the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE ADDITION REQUEST message. The S-NG-RAN node may include the *PDU Session Level UL Data Forwarding UP TNL Information* IE in the *Data Forwarding Info from target NG-RAN node* IE within the *PDU Session Resource Setup Response Info – SN terminated* IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding.
+
+If the *Masked IMEISV* IE is contained in the S-NODE ADDITION REQUEST message the S-NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.
+
+If the *UE Radio Capability ID* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [7] and TS 23.502 [13].
+
+The S-NG-RAN node shall report to the M-NG-RAN node, in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the result for all the requested PDU session resources in the following way:
+
+- A list of PDU session resources which are successfully established shall be included in the *PDU Session Resources Admitted To Be Added List* IE.
+- A list of PDU session resources which failed to be established shall be included in the *PDU Session Resources Not Admitted List* IE.
+
+Upon reception of the S-NODE ADDITION REQUEST ACKNOWLEDGE message the M-NG-RAN node shall stop the timer TX<sub>NDCprep</sub>.
+
+If the S-NODE ADDITION REQUEST ACKNOWLEDGE message contains the *MR-DC Resource Coordination Information* IE, the M-NG-RAN node may use it for the purpose of resource coordination with the S-NG-RAN node. The M-NG-RAN node shall consider the value of the received *UL Coordination Information* IE valid until reception of a new update of the IE for the same UE. The M-NG-RAN node shall consider the value of the received *DL Coordination Information* IE valid until reception of a new update of the IE for the same UE. If the *E-UTRA Coordination Assistance Information* IE or the *NR Coordination Assistance Information* IE is contained in the *MR-DC Resource Coordination Information* IE, the M-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the M-NG-RAN node and the S-NG-RAN node.
+
+The S-NG-RAN node may include for each bearer in the *DRBs To Be Setup List* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message the *PDCP SN Length* IE to indicate the PDCP SN length for that DRB.
+
+If the *S-NG-RAN node UE XnAP ID* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information and use it as defined in TS 37.340 [8].
+
+If the S-NODE ADDITION REQUEST message contains the *PDCP SN Length* IE, the S-NG-RAN node shall, if supported, store this information and use it for lower layer configuration of the concerned MN terminated bearer.
+
+If the S-NODE ADDITION REQUEST message contains the *SN Addition Trigger Indication* IE, the S-NG-RAN node shall include the *RRC config indication* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message to inform the M-NG-RAN node if the S-NG-RAN node applied full or delta configuration, as specified in TS 37.340 [8].
+
+If the S-NODE ADDITION REQUEST message contains the *S-NG-RAN node Maximum Integrity Protected Data Rate Uplink* IE or the *S-NG-RAN node Maximum Integrity Protected Data Rate Downlink* IE, the S-NG-RAN node shall use the received information when enforcing the maximum integrity protected data rate for the UE.
+
+If the *Security Indication* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE ADDITION REQUEST message, the behaviour of the S-NG-RAN node shall be the same as specified for the same IE in the *PDU Session Resources To Be Setup List* IE in the Handover Preparation procedure, for the concerned PDU session, and the S-NG-RAN node shall include the *Security Result* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE. If either the S-NG-RAN node or the M-NG-RAN node is an ng-eNB, the S-NG-RAN node shall behave as specified in TS 33.501 [28].
+
+If the *Security Result* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE ADDITION REQUEST message, the S-NG-RAN node may take the information into account when deciding whether to perform user plane integrity protection or ciphering for the DRBs that it establishes for the concerned PDU session, except if the *Split Session Indicator* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE and set to "split", in which case it shall perform user plane integrity protection or ciphering according to the information in the *Security Result* IE.
+
+The S-NG-RAN node may include the *Location Information at S-NODE* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, if respective information is available at the S-NG-RAN node.
+
+If the *Location Information at S-NODE Reporting* IE set to "pscell" is included in the S-NODE ADDITION REQUEST, the S-NG-RAN node shall, start providing information about the current location of the UE. If the *Location Information at S-NODE* IE is included in the S-NODE ADDITION REQUEST ACKNOWLEDGE, the M-NG-RAN node shall store the included information so that it may be transferred towards the AMF.
+
+If the *Default DRB Allowed* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE ADDITION REQUEST message and set to "true", the S-NG-RAN node may configure the default DRB for the PDU session.
+
+If the S-NODE ADDITION REQUEST ACKNOWLEDGE message includes the *DRB IDs taken into use* IE, the M-NG-RAN node, if applicable, shall act as specified in TS 37.340 [8].
+
+If *Trace Activation* IE has previously been received for this UE, it shall be included in the S-NODE ADDITION REQUEST message. If the *Trace Activation* IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [23].
+
+If the *Trace Activation* IE is included in the S-NODE ADDITION REQUEST message which includes
+
+- the *MDT Activation* IE set to "Immediate MDT and Trace", then the S-NG-RAN node shall if supported, initiate the requested trace session and MDT session as described in TS 32.422 [23].
+- the *MDT Activation* IE set to "Immediate MDT Only", the S-NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422 [23] and the S-NG-RAN node shall ignore the *Interfaces To Trace* IE, and the *Trace Depth* IE.
+- the *MDT Location Information* IE, within the *MDT Configuration* IE, the S-NG-RAN node shall, if supported, store this information and take it into account in the requested MDT session.
+- the *MDT Activation* IE set to "Immediate MDT Only", and if the *Signalling based MDT PLMN List* IE is included in the *MDT Configuration* IE, the S-NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [43].
+- the *Bluetooth Measurement Configuration* IE, within the *MDT Configuration* IE, the S-NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *WLAN Measurement Configuration* IE, within the *MDT Configuration* IE, the S-NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *Sensor Measurement Configuration* IE, within the *MDT Configuration* IE, the S-NG-RAN node shall take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *MDT Configuration* IE and if the S-NG-RAN node is a gNB at least the *MDT Configuration-NR* IE shall be present, while if the S-NG-RAN Node is an ng-eNB at least the *MDT Configuration-EUTRA* IE shall be present.
+
+If the *Area Scope* IE is not present in the *MDT Configuration* IE, the S-NG-RAN node shall consider that the MDT Configuration is applied to all PLMNs indicated in the MDT PLMN List, as described in TS 32.422 [23].
+
+If the *Requested Fast MCG recovery via SRB3* IE set to "true" is included in the S-NODE ADDITION REQUEST message and the S-NG-RAN node decides to configure fast MCG link recovery via SRB3 as specified in TS 37.340 [8], the S-NG-RAN node shall, if supported, include the *Available fast MCG recovery via SRB3* IE set to "true" in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.
+
+If the *QoS Monitoring Request* IE is included in the *QoS Flow Level QoS Parameters* IE for a QoS flow contained in the *DRBs To Be Setup List* IE of the *PDU Session Resource Setup Info – MN terminated* IE, the S-NG-RAN node shall, if supported, use it to configure lower layers for the purpose of delay measurement and QoS monitoring as specified in TS 23.501 [7]. If the *QoS Monitoring Reporting Frequency* IE is included in the *QoS Flow Level QoS Parameters* IE
+
+for a QoS flow contained in the *DRBs To Be Setup List* IE of the *PDU Session Resource Setup Info – MN terminated* IE, the S-NG-RAN node shall, if supported, use it for RAN part delay reporting.
+
+For each QoS flow which has been successfully established in the S-NG-RAN node, if the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the *PDU Session Resource Setup Info – SN terminated* IE, the S-NG-RAN node shall store this information, and shall, if supported, perform delay measurement and QoS monitoring as specified in TS 23.501 [7]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the *PDU Session Resource Setup Info – SN terminated* IE, the S-NG-RAN node shall store this information, and shall, if supported, use it for RAN part delay reporting. In case such a QoS flow is included in the *DRBs To Be Setup List* IE of the *PDU Session Resource Setup Response Info – SN terminated* IE, the M-NG-RAN node shall, if supported, use it to configure lower layers for the purpose of delay measurement and QoS monitoring. If the *QoS Monitoring Reporting Frequency* IE is included in the *DRBs To Be Setup List* IE of the *PDU Session Resource Setup Response Info – SN terminated* IE, the M-NG-RAN node shall, if supported, use it for RAN part delay reporting.
+
+For each DRB configured as MN-terminated split bearer/SCG bearer, if the *QoS Mapping Information* IE is included in the *DRBs Admitted List* IE in the *PDU Session Resource Setup Response Info – MN terminated* IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets which are transmitted from M-NG-RAN node to S-NG-RAN node through the GTP tunnels indicated by the *UP Transport Layer Information* IE.
+
+If the *Source NG-RAN Node ID* IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, use it to decide the direct data path availability with the indicated source NG-RAN node, and if the direct data forwarding path is available, include the *Direct Forwarding Path Availability* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.
+
+If for a given QoS Flow the *Source DL Forwarding IP Address* IE or both, the *Source DL Forwarding IP Address* IE and the *Source Node DL Forwarding IP Address* IE are included within the *Data Forwarding and Offloading Info from source NG-RAN node* IE in the *PDU Session Resource Setup Info – SN terminated* IE contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.
+
+If for a given QoS Flow the *Source DL Forwarding IP Address* IE is included within the *QoS Flows Mapped To DRB List* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE contained in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality to identify source TNL address for data forwarding in case of subsequent handover preparation, if such ACL functionality is deployed.
+
+If the *Management Based MDT PLMN List* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store the received information in the UE context, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [23].
+
+Upon reception of the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, start collecting SCG information and continue for as long as the UE stays in one of its cells.
+
+If the *UE History Information from the UE* IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information.
+
+If the *PSCell Change History* IE set to "reporting full history" is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, signal the latest SCG UE History Information upon each PSCell change, to the M-NG-RAN node, using the S-NG-RAN node initiated S-NG-RAN node Modification procedure.
+
+If the *IAB Node Indication* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that dual connectivity operation is requested for an IAB-node. In addition:
+
+- If the *No PDU Session Indication* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider the UE as an IAB-node which does not have any PDU sessions activated,
+
+and ignore the *PDU Session Resources To Be Added List* IE, and shall not take any action with respect to PDU session setup. Subsequently, the M-NG-RAN node shall, if supported, ignore the *PDU Session Resources Admitted To Be Added List* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.
+
+- If the *F1-terminating IAB-donor Indicator* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, assume that it will become the F1-terminating IAB-donor of the IAB-node, and act as described in TS 38.401 [2].
+
+If the *CHO Information SN Addition* IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall consider that the S-NG-RAN node Addition Preparation procedure has been triggered as part of a conditional handover. It may use the *Source M-NG-RAN node ID* IE and the *Source M-NG-RAN node UE XnAP ID* IE to identify other active S-NG-RAN node Addition Preparations related to this UE. If the *PCell ID* IE is also included in the S-NODE ADDITION REQUEST message, then the S-NG-RAN node shall, if supported, include the *PCell ID* IE within the *CHO Information SN Addition Acknowledge* IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message. If the *Estimated Arrival Probability* IE is contained in the *CHO Information SN Addition* IE included in the S-NODE ADDITION REQUEST message, then the S-NG-RAN node may use the information to allocate necessary resources for the UE. If the *Direct Forwarding Path Availability with source M-NG-RAN node* IE set to "direct path available" is included in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, consider that the direct forwarding path is available between the target S-NG-RAN node and the source M-NG-RAN node.
+
+If the *SCG Activation Request* IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node may use it to configure SCG resources as specified in TS 37.340 [8], and shall, if supported, include the *SCG Activation Status* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message. If the *SCG Activation Request* IE in the S-NODE ADDITION REQUEST message is set to "Activate SCG", the S-NG-RAN node shall, if supported, activate the SCG resources and set the *SCG Activation Status* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message to "SCG activated".
+
+If the *Conditional PSCell Addition Information Request* IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that the request concerns CPAC, as described in TS 37.340 [8]. Accordingly, the S-NG-RAN node shall, if supported, include the *Conditional PSCell Addition Acknowledge* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.
+
+If the *S-CPAC Request Information* IE is contained in the *Conditional PSCell Addition Information Request* IE included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that the procedure is triggered for S-CPAC preparation.
+
+If the *S-CPAC Reference Configuration Request* IE set to "request" is contained in the *Conditional PSCell Addition Information Request* IE included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, provide the SCG reference configuration for S-CPAC.
+
+If the *S-CPAC Multiple Target S-NG-RAN Node List* IE is contained within the *S-CPAC Request Information* IE in the *Conditional PSCell Addition Information Request* IE included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that the information pertains to a list of PSCells suggested for other candidate SN(s) also prepared for S-CPAC, and act as described in TS 37.340 [8].
+
+If the *Conditional PSCell Addition Information Acknowledge* is included in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, shall, if supported, consider the indicated PSCells are selected by the target SN as candidate PSCells for CPAC.
+
+If the *CG-CandidateList* is included in the *S-NG-RAN node to M-NG-RAN node Container* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it for the purpose of CPAC.
+
+If the *Estimated Arrival Probability* IE is contained in the *Conditional PSCell Addition Information Request* IE included in the S-NODE ADDITION REQUEST message, then the candidate target S-NG-RAN node may use the information to allocate necessary resources for the incoming CPAC procedure.
+
+If the *S-NG-RAN node UE Slice Maximum Bit Rate* IE for a specific S-NSSAI is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store and use the received S-NG-RAN node UE Slice Maximum Bit Rate for all PDU sessions associated with the S-NSSAI for the concerned UE as defined in TS 23.501 [7].
+
+If the S-NODE ADDITION REQUEST ACKNOWLEDGE message includes the *SN Mobility Information* IE, the M-NG-RAN node shall, if supported, store this information and use it as defined in TS 38.300 [9].
+
+If the *QMC Coordination Request* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node may use it as specified in TS 37.340 [8], and shall, if supported, include the *QMC Coordination Response* IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.
+
+If the *Source SN to Target SN QMC Information* IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, use it for QoE measurements handling, as specified in TS 37.340 [8].
+
+#### Interactions with the S-NG-RAN node Reconfiguration Completion procedure:
+
+If the S-NG-RAN node admits at least one PDU session resource, the S-NG-RAN node shall start the timer $TXn_{DCoverall}$ when sending the S-NODE ADDITION REQUEST ACKNOWLEDGE message to the M-NG-RAN node except for a request for conditional configuration. The reception of the S-NODE RECONFIGURATION COMPLETE message shall stop the timer $TXn_{DCoverall}$ if $TXn_{DCoverall}$ is running.
+
+#### Interaction with the Activity Notification procedure
+
+Upon receiving an S-NODE ADDITION REQUEST message containing the *Desired Activity Notification Level* IE, the S-NG-RAN node shall, if supported, use this information to decide whether to trigger subsequent Activation Notification procedures according to the requested notification level.
+
+### 8.3.1.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE ADDITION REQUEST
+ Note right of S-NG-RAN node:
+ S-NG-RAN node-->>M-NG-RAN node: S-NODE ADDITION REQUEST REJECT
+ Note left of M-NG-RAN node:
+
+```
+
+Sequence diagram showing an unsuccessful S-NG-RAN node addition preparation. The M-NG-RAN node sends an S-NODE ADDITION REQUEST to the S-NG-RAN node, which responds with an S-NODE ADDITION REQUEST REJECT.
+
+Figure 8.3.1.3-1: S-NG-RAN node Addition Preparation, unsuccessful operation
+
+If the S-NG-RAN node is not able to accept any of the bearers or a failure occurs during the S-NG-RAN node Addition Preparation, the S-NG-RAN node sends the S-NODE ADDITION REQUEST REJECT message with an appropriate cause value to the M-NG-RAN node.
+
+If the *CHO Information SN Addition* IE is included in the S-NODE ADDITION REQUEST message and the *PCell ID* IE is also included, but the S-NG-RAN node is not able to accept any of the bearers or a failure occurs during the S-NG-RAN node Addition Preparation, the S-NG-RAN node shall, if supported, include the *PCell ID* IE in the S-NODE ADDITION REQUEST REJECT message.
+
+### 8.3.1.4 Abnormal Conditions
+
+If the S-NG-RAN node receives an S-NODE ADDITION REQUEST message containing in a *PDU Session Resource To Be Added Item* IE neither the *PDU Session Resource Setup Info – SN terminated* IE nor the *PDU Session Resource Setup Info – MN terminated* IE, the S-NG-RAN node shall fail the S-NG-RAN node Addition Preparation procedure indicating an appropriate cause.
+
+If the supported algorithms for encryption defined in the *NR Encryption Algorithms* IE in the *NR UE Security Capabilities* IE, plus the mandated support of NEA0 in all UEs (TS 33.501 [28]), do not match any algorithms defined in the configured list of allowed encryption algorithms in the S-NG-RAN node (TS 33.501 [28]), the S-NG-RAN node shall reject the procedure using the S-NODE ADDITION REQUEST REJECT message.
+
+If the supported algorithms for integrity defined in the *NR Integrity Protection Algorithms* IE in the *NR UE Security Capabilities* IE do not match any algorithms defined in the configured list of allowed integrity protection algorithms in the S-NG-RAN node (TS 33.501 [28]), the S-NG-RAN node shall reject the procedure using the S-NODE ADDITION REQUEST REJECT message.
+
+If the S-NG-RAN node receives an S-NODE ADDITION REQUEST message containing a *S-NG-RAN node UE XnAP ID* IE that does not match any existing UE Context that has such ID, the S-NG-RAN node shall reject the procedure using the S-NODE ADDITION REQUEST REJECT message.
+
+If the M-NG-RAN node receives an S-NODE ADDITION REQUEST ACKNOWLEDGE message containing a value for *PDU Session ID* in *PDU Session Resources Admitted List* IE and in *PDU Session Resources Not Admitted List* IE, the M-NG-RAN node shall regard setup of S-NG-RAN node resources of that PDU Session as being failed.
+
+If the S-NG-RAN node receives an S-NODE ADDITION REQUEST message containing, for a PDU session, a *PDU Session Resource Setup Info – SN terminated* IE for which the *Split Session Indicator* IE is included and set to "split", the *Security Result* IE is not included, and either the *Integrity Protection Indication* IE or the *Confidentiality Protection Indication* IE is set to "preferred", it shall reject the PDU session.
+
+#### **Interaction with the M-NG-RAN node initiated S-NG-RAN node Release procedure:**
+
+If the M-NG-RAN node receives an S-NODE ADDITION REQUEST ACKNOWLEDGE message containing in a *PDU Session Resource Admitted To Be Added Item* IE neither the *PDU Session Resource Setup Response Info – SN terminated* IE nor the *PDU Session Resource Setup Response Info – MN terminated* IE, the M-NG-RAN node shall trigger the M-NG-RAN node initiated S-NG-RAN node Release procedure indicating an appropriate cause.
+
+If the timer TXn<sub>DCprep</sub> expires before the M-NG-RAN node has received the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall regard the S-NG-RAN node Addition Preparation procedure as being failed and shall trigger the M-NG-RAN node initiated S-NG-RAN node Release procedure.
+
+#### **Interactions with the S-NG-RAN node Reconfiguration Completion and S-NG-RAN node initiated S-NG-RAN node Release procedure:**
+
+If the timer TXn<sub>DCoverall</sub> expires before the S-NG-RAN node has received the S-NODE RECONFIGURATION COMPLETE or the S-NODE RELEASE REQUEST message, the S-NG-RAN node shall regard the requested RRC connection reconfiguration as being not applied by the UE and shall trigger the S-NG-RAN node initiated S-NG-RAN node Release procedure.
+
+### **8.3.2 S-NG-RAN node Reconfiguration Completion**
+
+#### **8.3.2.1 General**
+
+The purpose of the S-NG-RAN node Reconfiguration Completion procedure is to provide information to the S-NG-RAN node whether the requested configuration was successfully applied by the UE.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.2.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE RECONFIGURATION COMPLETE
+ Note right of S-NG-RAN node:
+ Note left of M-NG-RAN node:
+ Note right of S-NG-RAN node:
+```
+
+The diagram illustrates the successful operation of the S-NG-RAN node reconfiguration complete procedure. It shows two vertical lifelines: 'M-NG-RAN node' on the left and 'S-NG-RAN node' on the right. A horizontal arrow labeled 'S-NODE RECONFIGURATION COMPLETE' points from the M-NG-RAN node to the S-NG-RAN node. Each lifeline has a thick horizontal bar at the bottom, representing the UE context.
+
+Sequence diagram showing the S-NODE RECONFIGURATION COMPLETE message flow from M-NG-RAN node to S-NG-RAN node.
+
+**Figure 8.3.2.2-1: S-NG-RAN node Reconfiguration Complete procedure, successful operation.**
+
+The M-NG-RAN node initiates the procedure by sending the S-NODE RECONFIGURATION COMPLETE message to the S-NG-RAN node.
+
+The S-NODE RECONFIGURATION COMPLETE message may contain information that
+
+- either the UE has successfully applied the configuration requested by the S-NG-RAN node. The M-NG-RAN node may also provide configuration information in the *M-NG-RAN node to S-NG-RAN node Container* IE.
+- or the configuration requested by the S-NG-RAN node has been rejected. The M-NG-RAN node shall provide information with sufficient precision in the included *Cause* IE to enable the S-NG-RAN node to know the reason for an unsuccessful reconfiguration. The M-NG-RAN node may also provide configuration information in the *M-NG-RAN node to S-NG-RAN node Container* IE.
+
+Upon reception of the S-NODE RECONFIGURATION COMPLETE message the S-NG-RAN node shall stop the timer $TXn_{DCoverall}$ if $TXn_{DCoverall}$ is running.
+
+### 8.3.2.3 Abnormal Conditions
+
+Void.
+
+## 8.3.3 M-NG-RAN node initiated S-NG-RAN node Modification Preparation
+
+### 8.3.3.1 General
+
+This procedure is used to enable an M-NG-RAN node to request an S-NG-RAN node to either modify the UE context at the S-NG-RAN node or to query the current SCG configuration for supporting delta signalling in M-NG-RAN node initiated S-NG-RAN node change, or to provide the S-RLF-related information to the S-NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.3.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE MODIFICATION REQUEST
+ Note right of S-NG-RAN node:
+ S-NG-RAN node-->>M-NG-RAN node: S-NODE MODIFICATION REQUEST ACKNOWLEDGE
+ Note left of M-NG-RAN node:
+
+```
+
+Sequence diagram showing the successful operation of S-NODE Modification Preparation. The M-NG-RAN node sends an S-NODE MODIFICATION REQUEST to the S-NG-RAN node, which responds with an S-NODE MODIFICATION REQUEST ACKNOWLEDGE.
+
+**Figure 8.3.3.2-1: M-NG-RAN node initiated S-NG-RAN node Modification Preparation, successful operation**
+
+The M-NG-RAN node initiates the procedure by sending the S-NODE MODIFICATION REQUEST message to the S-NG-RAN node.
+
+When the M-NG-RAN node sends the S-NODE MODIFICATION REQUEST message, it shall start the timer $T_{XnDCprep}$ .
+
+The S-NODE MODIFICATION REQUEST message may contain
+
+- within the *UE Context Information IE*;
+ - PDU session resources to be added within the *PDU Session Resources To Be Added Item IE*;
+ - PDU session resources to be modified within the *PDU Session Resources To Be Modified Item IE*;
+ - PDU session resources to be released within the *PDU Session Resources To Be Released Item IE*;
+ - the *S-NG-RAN node Security Key IE*;
+ - the *S-NG-RAN node UE Aggregate Maximum Bit Rate IE*;
+- the *M-NG-RAN node to S-NG-RAN node Container IE*;
+- the *PDCP Change Indication IE*;
+- the *SCG Configuration Query IE*;
+- the *Requested split SRBs IE*;
+- the *Requested split SRBs release IE*;
+- the *Requested fast MCG recovery via SRB3 IE*;
+- the *Requested fast MCG recovery via SRB3 Release IE*;
+- the *Additional DRB IDs IE*;
+- the *MR-DC Resource Coordination Information IE*.
+
+If the S-NODE MODIFICATION REQUEST message contains the *Selected PLMN IE*, the S-NG-RAN node may use it for RRM purposes. If the S-NODE MODIFICATION REQUEST message also contains the *Selected NID IE*, the S-NG-RAN node may decide to use the SNPN identified by the *Selected PLMN IE* and *Selected NID IE* for its own usage.
+
+If the S-NODE MODIFICATION REQUEST message contains the *Mobility Restriction List IE*, the S-NG-RAN node shall
+
+- replace the previously provided Mobility Restriction List by the received Mobility Restriction List in the UE context;
+- use this information to select an appropriate SCG.
+
+If the *S-NG-RAN node UE Aggregate Maximum Bit Rate* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall:
+
+- replace the previously provided S-NG-RAN node UE Aggregate Maximum Bit Rate by the received S-NG-RAN node UE Aggregate Maximum Bit Rate in the UE context;
+- use the received S-NG-RAN node UE Aggregate Maximum Bit Rate for Non-GBR Bearers for the concerned UE as defined in TS 37.340 [8].
+
+If the *S-NG-RAN node UE Slice Maximum Bit Rate* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported:
+
+- store and replace the previously provided S-NG-RAN node UE Slice Maximum Bit Rate, if any, by the received S-NG-RAN node UE Slice Maximum Bit Rate for each S-NSSAI for the concerned UE;
+- use the received S-NG-RAN node UE Slice Maximum Bit Rate for all PDU sessions associated with the S-NSSAI for the concerned UE as defined in TS 23.501 [7].
+
+If the S-NODE MODIFICATION REQUEST message contains the *Index to RAT/Frequency Selection Priority* IE, the S-NG-RAN node may use it for RRM purposes.
+
+If the S-NODE MODIFICATION REQUEST message contains the *S-NG-RAN node PDU Session Aggregate Maximum Bit Rate* IE, the S-NG-RAN node may use it for RRM purposes.
+
+If the S-NODE MODIFICATION REQUEST message contains the *MR-DC Resource Coordination Information* IE, the S-NG-RAN node should forward it to lower layers and it may use it for the purpose of resource coordination with the M-NG-RAN node, or to coordinate with sidelink resources used in the M-NG-RAN node. The S-NG-RAN node shall consider the value of the received *UL Coordination Information* IE valid until reception of a new update of the IE for the same UE. The S-NG-RAN node shall consider the value of the received *DL Coordination Information* IE valid until reception of a new update of the IE for the same UE. If the *E-UTRA Coordination Assistance Information* IE or the *NR Coordination Assistance Information* IE is contained in the *MR-DC Resource Coordination Information* IE, the S-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the S-NG-RAN node and the M-NG-RAN node.
+
+If the S-NODE MODIFICATION REQUEST message contains the *NE-DC TDM Pattern* IE, the S-NG-RAN node should forward it to lower layers and use it for the purpose of single uplink transmission. The S-NG-RAN node shall consider the value of the received *NE-DC TDM Pattern* IE valid until reception of a new update of the IE for the same UE.
+
+The allocation of resources according to the values of the *Allocation and Retention Priority* IE included in the *QoS Flow Level QoS Parameters* IE for each QoS flow shall follow the principles specified for the PDU Session Resource Setup procedure in TS 38.413 [5].
+
+If the *Additional QoS Flow Information* IE is included for a QoS flow in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [5].
+
+For each GBR QoS flow, if the *Alternative QoS Parameters Sets* IE is included in the *GBR QoS Flow Information* IE, the S-NG-RAN node shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure specified in TS 38.413 [5].
+
+If the *TSC Traffic Characteristics* IE is included for a QoS flow in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [5].
+
+For each PDU session, if the *Network Instance* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE and in the *PDU Session Resource Modification Info – SN terminated* IE and the *Common Network Instance* IE is not present, the S-NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].
+
+For each PDU session, if the *Common Network Instance* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE and in the *PDU Session Resource Modification Info – SN terminated* IE, the S-NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].
+
+For each GBR QoS flow, if the *Offered GBR QoS Flow Information* IE is included in the *QoS Flows To Be Setup List* IE contained in the *PDU Session Resource Setup Info – SN terminated* IE, the S-NG-RAN node may request the M-NG-RAN node to configure the DRB to which that QoS flow is mapped with MCG resources.
+
+For each PDU session, if the *Non-GBR Resources Offered* IE is included in the *PDU Session Resource Modification Info – SN terminated* IE contained in the *PDU Session Resources To Be Added List* IE and set to "true", the S-NG-RAN node may request the M-NG-RAN node to configure the DRBs to which non-GBR QoS flows of the PDU session are mapped with MCG resources.
+
+If at least one of the requested modifications is admitted by the S-NG-RAN node, the S-NG-RAN node shall modify the related part of the UE context accordingly and send the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message back to the M-NG-RAN node.
+
+The M-NG-RAN node shall include *RLC Mode* IE for each bearer offloaded from M-NG-RAN node to S-NG-RAN node in the *DRBs to QoS Flow Mapping List* IE within the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message, and the *RLC Mode* IE indicates the mode that the M-NG-RAN used for the DRB when it was hosted at the M-NG-RAN node.
+
+The S-NG-RAN node shall include the PDU sessions for which resources have been either added or modified or released at the S-NG-RAN node either in the *PDU Session Resources Admitted To Be Added List* IE or the *PDU Session Resources Admitted To Be Modified List* IE or the *PDU Session Resources Admitted To Be Released List* IE. The S-NG-RAN node shall include the PDU sessions that have not been admitted in the *PDU Session Resources Not Admitted List* IE with an appropriate cause value.
+
+If the M-NG-RAN node requests transfer of the PDCP hosting from the S-NG-RAN node to the M-NG-RAN node for a PDU session, in which case the S-NODE MODIFICATION REQUEST message contains an PDU session resource to be released which is configured with the SCG bearer option within the *PDU Session Resources To Be Released List* IE, the S-NG-RAN node shall include the *RLC Mode* IE within the *DRBs To Be Released List* IE in the *PDU Session Resources admitted to be released List – SN terminated* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. The *RLC Mode* IE indicates the RLC mode that the S-NG-RAN node uses for the DRB.
+
+If the *QoS Flow Mapping Indication* IE is included in the S-NODE MODIFICATION REQUEST message for a QoS flow to be modified, the S-NG-RAN node may replace and take it into account that only the uplink or downlink QoS flow is mapped to the DRB.
+
+If the S-NODE MODIFICATION REQUEST message contains for a PDU session resource to be modified which is configured with the SN terminated bearer option, the *UL NG-U UP TNL Information at UPF* IE the S-NG-RAN node shall use it as the new UL NG-U address.
+
+If the S-NODE MODIFICATION REQUEST message contains for a PDU session resource to be modified which is configured with the MN terminated bearer option, the *MN UL PDCP UP TNL Information* IE the S-NG-RAN node shall use it as the new UL Xn-U address.
+
+Redundant transmission:
+
+- If the S-NODE MODIFICATION REQUEST message contains for a PDU session resource to be modified which is configured with the SN terminated bearer option, the *Redundant UL NG-U UP TNL Information at UPF* IE, the S-NG-RAN node shall, if supported, use it as the new UL NG-U address for the redundant transmission as specified in TS 23.501 [7].
+- For each PDU session, if the *Redundant Common Network Instance* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE or in the *PDU Session Resource Modification Info – SN terminated* IE, the S-NG-RAN node shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [7].
+- For each PDU session, if the *Redundant QoS Flow Indicator* IE is set to false for all QoS flows, the S-NG-RAN node shall, if supported, stop the redundant transmission and release the redundant tunnel for the concerned PDU Session as specified in TS 23.501 [7].
+- For each PDU session for which the *Redundant QoS Flow Indicator* IE is included in the *S-NODE MODIFICATION REQUEST* message, the S-NG-RAN node shall, if supported, store and use it as specified in TS 23.501 [7].
+- For each PDU session, if the *Redundant PDU Session Information* IE is included in the *PDU Session Resource Setup Info - SN terminated* IE in the S-NODE MODIFICATION REQUEST message, the S-NODE-RAN node shall, if supported, store the received information in the UE context and setup the redundant user plane for the concerned PDU session, as specified in TS 23.501 [7]. If the *PDU Session Pair ID* IE is included in the *Redundant PDU Session Information* IE, the S-NG-RAN node may store and use it to identify the paired PDU sessions.
+- For each PDU session resource successfully setup for which the *Redundant PDU Session Information* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, include the *Used RSN Information* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+If the S-NODE MODIFICATION REQUEST message contains the *QoS flows To Be Released List* within the *PDU Session Resource Modification Info – SN terminated* IE, the S-NG-RAN node may propose to apply forwarding of UL data for the QoS flows for which in-order delivery is requested by including the *UL Forwarding Proposal* IE in the *Data Forwarding and Offloading Info from source NG-RAN node* IE within the *PDU Session Resource Modification Response Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+For a PDU session resource to be modified which is configured with the SN terminated bearer option the S-NG-RAN node may include in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message the *DL NG-U UP TNL Information at NG-RAN* IE.
+
+For a PDU session resource to be modified which is configured with the MN terminated bearer option the S-NG-RAN node may include in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message the *SN DL SCG UP TNL Information* IE.
+
+If the *PDCP Change Indication* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall act as specified in TS 37.340 [8].
+
+Upon reception of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message the M-NG-RAN node shall stop the timer TXn<sub>DCprep</sub>. If the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message has included the *S-NG-RAN node to M-NG-RAN node Container* IE, the M-NG-RAN node is then defined to have a Prepared S-NG-RAN node Modification for that Xn UE-associated signalling.
+
+If the *SCG Configuration Query* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall provide corresponding radio configuration information within the *S-NG-RAN node to M-NG-RAN node*
+
+*Container* IE and may provide the corresponding data forwarding related information within the *PDU Session Resources with Data Forwarding List* IE as specified in TS 37.340 [8].
+
+For each bearer for which allocation of the PDCP entity is requested at the S-NG-RAN node:
+
+- if applicable, the M-NG-RAN node may propose to apply forwarding of downlink data by including the *DL Forwarding* IE within the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message. For each bearer that it has decided to admit, the S-NG-RAN node may include the *DL Forwarding GTP Tunnel Endpoint* IE within the *PDU Session Resource Setup Response Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding of downlink data for this bearer.
+- the S-NG-RAN node may include for each bearer in the *PDU Session Resource Setup Response Info – SN terminated* IE the *UL Forwarding GTP Tunnel Endpoint* IE to indicate it requests data forwarding of uplink packets to be performed for that bearer.
+
+The M-NG-RAN node may propose to apply forwarding of UL data when offloading QoS flows for which in-order delivery is requested by including the *UL Forwarding Proposal* IE in the *Data Forwarding and Offloading Info from source NG-RAN node* IE within the *PDU Session Resource Setup Info – SN terminated* IE or *PDU Session Resource Modification Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message. The S-NG-RAN node may include the *PDU Session Level UL Data Forwarding UP TNL Information* IE in the *Data Forwarding Info from target NG-RAN node* IE within the *PDU Session Resource Setup Response Info – SN terminated* IE or *PDU Session Resource Modification Response Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding.
+
+If the S-NODE MODIFICATION REQUEST message contains the *Requested Split SRBs* IE, the S-NG-RAN node may use it to add split SRBs. If the S-NODE MODIFICATION REQUEST message contains the *Requested Split SRBs release* IE, the S-NG-RAN node may use it to release split SRBs.
+
+If the *Requested Fast MCG recovery via SRB3* IE set to "true" is included in the S-NODE MODIFICATION REQUEST message and the S-NG-RAN decides to configure fast MCG link recovery via SRB3 as specified in TS 37.340 [8], the S-NG-RAN node shall, if supported, include the *Available fast MCG recovery via SRB3* IE set to "true" in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message. If the *Requested Fast MCG recovery via SRB3 Release* IE set to "true" is included in the S-NODE MODIFICATION REQUEST message and the S-NG-RAN decides to release fast MCG link recovery via SRB3, the S-NG-RAN node shall, if supported, include the *Release fast MCG recovery via SRB3* IE set to "true" in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+If the *Lower Layer presence status change* IE set to "release lower layers" is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall act as specified in TS 37.340 [8].
+
+If the *Lower Layer presence status change* IE set to "re-establish lower layers" is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall act as specified in TS 37.340 [8].
+
+If the *Lower Layer presence status change* IE set to "suspend lower layers" is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall act as specified in TS 37.340 [8].
+
+If the *Lower Layer presence status change* IE set to "resume lower layers" is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall act as specified in TS 37.340 [8].
+
+The M-NG-RAN node may include for each bearer in the *DRBs To Be Modified List* IE in the S-NODE MODIFICATION REQUEST message the *RLC Status* IE to indicate that RLC has been reestablished at the M-NG-RAN node and the S-NG-RAN node may trigger PDCP data recovery.
+
+If the S-NODE MODIFICATION REQUEST message contains the *PDCP SN Length* IE in the *DRBs To Be Setup List* IE, the S-NG-RAN node shall, if supported, store this information and use it for lower layer configuration of the concerned MN terminated bearer.
+
+If the *PDCP Duplication Configuration* IE in the *PDU Session Resource Modification Info – MN terminated* IE is contained in the S-NODE MODIFICATION REQUEST message and set to "configured", the S-NG-RAN node shall, if supported, add the RLC entity of secondary path and the RLC entity of all additional path(s) for the indicated DRB. And if the S-NODE MODIFICATION REQUEST message contains the *Duplication Activation* IE, the S-NG-RAN node shall, if supported, store this information and use it for the purpose of PDCP duplication.
+
+If the S-NODE MODIFICATION REQUEST message contains *RLC Duplication Information* IE, the S-NG-RAN node shall, if supported, store this information and use it for the purpose of PDCP duplication for the indicated DRB with more than two RLC entities.
+
+If the *PDCP Duplication Configuration* IE in the *PDU Session Resource Modification Info – MN terminated* IE is contained in the S-NODE MODIFICATION REQUEST message and set to "de-configured", the S-NG-RAN node shall, if supported, delete the RLC entity of secondary path and the RLC entity of all additional path(s) for the indicated DRB.
+
+The S-NG-RAN node may include for each bearer in the *DRBs To Be Setup List* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message the *PDCP SN Length* IE to indicate the PDCP SN length for that DRB.
+
+The S-NG-RAN node may include the *QoS Flow Mapping Indication* IE for a QoS flow in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to indicate that only the uplink or downlink QoS flow is mapped to the DRB.
+
+If the *Additional DRB IDs* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall store this information and use it together with previously provided DRB IDs if any, for SN terminated bearers.
+
+If the S-NODE MODIFICATION REQUEST message contains the *S-NG-RAN node Maximum Integrity Protected Data Rate Uplink* IE or the *S-NG-RAN node Maximum Integrity Protected Data Rate Downlink* IE, the S-NG-RAN node shall use the received information when enforcing the maximum integrity protected data rate for the UE.
+
+If the *Security Indication* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message, the behaviour of the S-NG-RAN node shall be the same as specified for the same IE in the *PDU Session Resources To Be Setup List* IE in the Handover Preparation procedure, for the concerned PDU session, and the S-NG-RAN node shall include the *Security Result* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE. If either the S-NG-RAN node or the M-NG-RAN node is an ng-eNB, the S-NG-RAN node shall behave as specified in TS 33.501 [28].
+
+If the *Security Result* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node may take the information into account when deciding whether to perform user plane integrity protection or ciphering for the DRBs that it establishes for the concerned PDU session, except if the *Split Session Indicator* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE and set to "split", in which case it shall perform user plane integrity protection or ciphering according to the information in the *Security Result* IE.
+
+The S-NG-RAN node may include the *Location Information at S-NODE* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, if respective information is available at the S-NG-RAN node.
+
+If the *Location Information at S-NODE Reporting* IE set to "pscell" is included in the S-NODE MODIFICATION REQUEST, the S-NG-RAN node shall start providing information about the current location of the UE. If the *Location Information at S-NODE* IE is included in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE, the M-NG-RAN node shall store the included information so that it may be transferred towards the AMF.
+
+If the *S-NSSAI* IE is included in the *PDU Session Resources To Be Modified List* IE in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall replace the previously *S-NSSAI* IE by the received *S-NSSAI* IE.
+
+If the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message contains the *MR-DC Resource Coordination Information* IE, the M-NG-RAN node may use it for the purpose of resource coordination with the S-NG-RAN node. The M-NG-RAN node shall consider the value of the received *UL Coordination Information* IE valid until
+
+reception of a new update of the IE for the same UE. The M-NG-RAN node shall consider the value of the received *DL Coordination Information* IE valid until reception of a new update of the IE for the same UE. If the *E-UTRA Coordination Assistance Information* IE or the *NR Coordination Assistance Information* IE is contained in the *MR-DC Resource Coordination Information* IE, the M-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the M-NG-RAN node and the S-NG-RAN node.
+
+If the S-NODE MODIFICATION REQUEST message contains the *PCell ID* IE, the S-NG-RAN node may search for the target cell among the neighbour cells of the PCell indicated, as specified in the TS 37.340 [8].
+
+If the S-NG-RAN node applied a full configuration or delta configuration, e.g., as part of mobility procedure involving a change of DU, the S-NG-RAN node shall inform the M-NG-RAN node by including the *RRC config indication* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+If the *Default DRB Allowed* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE or *PDU Session Resource Modification Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message and set to "true", the S-NG-RAN node may configure the default DRB for the PDU session.
+
+If the *Default DRB Allowed* IE is included in the *PDU Session Resource Setup Info – SN terminated* IE or *PDU Session Resource Modification Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message and set to "false", the S-NG-RAN node shall not configure the default DRB for the PDU session and the S-NG-RAN node shall reconfigure the default DRB into a normal DRB if it has configured the default DRB before.
+
+If the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message includes the *DRB IDs taken into use* IE, the M-NG-RAN node, if applicable, shall act as specified in TS 37.340 [8].
+
+If the *QoS Monitoring Request* IE is included in the *QoS Flow Level QoS Parameters* IE for a QoS flow contained in the *DRBs To Be Setup List* IE or the *DRBs To Be Modified List* IE within the *PDU Session Resource Setup Info – MN terminated* IE or the *PDU Session Resource Modification Info – MN terminated* IE, the S-NG-RAN node shall, if supported, use it to configure lower layers for the purpose of delay measurement and QoS monitoring as specified in TS 23.501 [7]. If the *QoS Monitoring Reporting Frequency* IE is included in the *QoS Flow Level QoS Parameters* IE for a QoS flow contained in the *DRBs To Be Setup List* IE or the *DRBs To Be Modified List* IE within the *PDU Session Resource Setup Info – MN terminated* IE or the *PDU Session Resource Modification Info – MN terminated* IE, the S-NG-RAN node shall, if supported, use it for RAN part delay reporting.
+
+For each QoS flow which has been successfully added or modified in the S-NG-RAN node, if the *QoS Monitoring Request* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the *PDU Session Resource Setup Info – SN terminated* IE or the *PDU Session Resource Modification Info – SN terminated* IE, the S-NG-RAN node shall store this information, and shall, if supported, perform delay measurement and QoS monitoring as specified in TS 23.501 [7]. If the *QoS Monitoring Reporting Frequency* IE was included in the *QoS Flow Level QoS Parameters* IE contained in the *PDU Session Resource Setup Info – SN terminated* IE or the *PDU Session Resource Modification Info – SN terminated* IE, the S-NG-RAN node shall store this information, and shall, if supported, use it for RAN part delay reporting. In case such a QoS flow is included in the *DRBs To Be Setup List* IE or the *DRBs To Be Modified List* IE within the *PDU Session Resource Setup Response Info – SN terminated* IE or the *PDU Session Resource Modification Response Info – SN terminated* IE, the M-NG-RAN node shall, if supported, use it to configure lower layers for the purpose of delay measurement and QoS monitoring. If the *QoS Monitoring Reporting Frequency* IE is included in the *DRBs To Be Setup List* IE or the *DRBs To Be Modified List* IE within the *PDU Session Resource Setup Response Info – SN terminated* IE or the *PDU Session Resource Modification Response Info – SN terminated* IE, the M-NG-RAN node shall, if supported, use it for RAN part delay reporting.
+
+If the *PDU Session Expected UE Activity Behaviour* IE is included in the *PDU Session Resources To Be Added List* IE or the *PDU Session Resources To Be Modified List* IE of the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, use it for the concerned PDU session as specified in TS 23.501 [7].
+
+If the M-NG-RAN node receives in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message within the *PDU Session Resource Modification Response Info – MN terminated* IE a *DRBs Admitted to be Setup or Modified Item*
+
+with DRB ID(s) that it has not requested to be setup or modified, the M-NG-RAN node shall ignore the contained information.
+
+For each DRB configured as MN-terminated split bearer/SCG bearer, if the *QoS Mapping Information* IE is included in the *DRBs Admitted List* IE in the *PDU Session Resource Setup Response Info – MN terminated* IE of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets which are transmitted from M-NG-RAN node to S-NG-RAN node through the GTP tunnels indicated by the *UP Transport Layer Information* IE.
+
+For each DRB configured as MN-terminated split bearer/SCG bearer, if the *QoS Mapping Information* IE is included in the *DRBs Admitted to be Setup or Modified List* IE in the *PDU Session Resource Modification Response Info – MN terminated* IE of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets which are transmitted from M-NG-RAN node to S-NG-RAN node through the GTP tunnels indicated by the *UP Transport Layer Information* IE.
+
+For each DRB configured as SN-terminated split bearer/MCG bearer, if the *QoS Mapping Information* IE is included in the *DRBs To Be Modified List* IE in the *PDU Session Resource Modification Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets which are transmitted from S-NG-RAN node to M-NG-RAN node through the GTP tunnels indicated by the *UP Transport Layer Information* IE.
+
+If the *Security Indication* IE is included in the *PDU Session Resource Modification Info – SN terminated* IE of the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, replace any existing security indication, and enable/disable ciphering or integrity protection as specified in TS 38.331 [10], for the concerned PDU session, and the S-NG-RAN node shall include the *Security Result* IE in the *PDU Session Resource Modification Response Info – SN terminated* IE. If either the S-NG-RAN node or the M-NG-RAN node is an ng-eNB, the S-NG-RAN node shall behave as specified in TS 33.501 [28].
+
+If the *Target Node ID* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, include the *Direct Forwarding Path Availability* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message if the direct forwarding path is available between the S-NG-RAN node and the indicated target node.
+
+If the *PSCell History Information Retrieve* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, use this information as specified in TS 37.340 [8].
+
+If the *UE History Information from the UE* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, store this information.
+
+If the *CHO Information SN Modification* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall consider that the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure has been triggered as part of a conditional handover. If the *Estimated Arrival Probability* IE is contained in the *CHO Information SN Modification* IE included in the S-NODE MODIFICATION REQUEST message, then the S-NG-RAN node may use the information to allocate necessary resources for the UE.
+
+If the *SCG Activation Request* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node may use it to configure SCG resources as specified in TS 37.340 [8], and shall, if supported, include the *SCG Activation Status* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+If the *Conditional PSCell Change Information Update* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, consider that the request provides the list of PSCells prepared at the target S-NG-RAN node, as described in TS 37.340 [8].
+
+If the *Conditional PSCell Addition Information Modification Request* IE is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, consider that the request concerns an update of the previous CPAC preparation, as described in TS 37.340 [8]. Accordingly, the S-NG-RAN shall, if supported, include the
+
+*Conditional PSCell Addition Information Modification Acknowledge* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+If the *S-CPAC Request Information* IE is contained in the *Conditional PSCell Addition Information Modification Request* IE included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, consider that the procedure is triggered for S-CPAC preparation or modification.
+
+If the *S-CPAC Reference Configuration Request* IE set to "request" is contained in the *Conditional PSCell Addition Information Modification Request* IE included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, provide the SCG reference configuration for S-CPAC.
+
+If the *S-CPAC Multiple Target S-NG-RAN Node List* IE is contained within the *S-CPAC Request Information* IE in the *Conditional PSCell Addition Information Modification Request* IE included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, consider that the information pertains to a list of PSCells suggested for other candidate SN(s) also prepared for S-CPAC, and act as described in TS 37.340 [8].
+
+If the *S-CPAC Inter-SN Execution Notification* IE set to "true" is contained in the *Conditional PSCell Addition Information Modification Request* IE included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, consider that the UE has been moved to another candidate SN due to inter-SN S-CPAC execution and may stop data transmission to the UE. If the *Data Forwarding and Offloading Info from source NG-RAN node* IE within the *PDU Session Resource Modification Info – SN terminated* IE is also included for some PDU session in the *PDU Session Resources To Be Modified List* IE of the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node may include the *Data Forwarding Info from target NG-RAN node* IE within the *PDU Session Resource Modification Response Info – SN terminated* IE of the corresponding PDU sessions in the *PDU Session Resources Admitted To Be Modified List* IE of the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to provide the new data forwarding address information for S-CPAC.
+
+If the *CG-CandidateList* is included in the *S-NG-RAN node to M-NG-RAN node Container* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it for the purpose of CPAC.
+
+If the *Estimated Arrival Probability* IE is contained in the *Conditional PSCell Addition Information Modification Request* IE included in the S-NODE MODIFICATION REQUEST message, then the candidate target S-NG-RAN node may use the information to allocate necessary resources for the incoming CPAC procedure.
+
+If for a given QoS Flow the *Source DL Forwarding IP Address* IE is included within the *Data Forwarding and Offloading Info from source NG-RAN node* IE in the *PDU Session Resource Setup Info – SN terminated* IE and/or in the *PDU Session Resource Modification Info – SN terminated* IE contained in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.
+
+If for a given QoS Flow the *Source DL Forwarding IP Address* IE is included within the *QoS Flows Mapped To DRB List* IE in the *PDU Session Resource Setup Response Info – SN terminated* IE and/or in the *PDU Session Resource Modification Response Info – SN terminated* IE contained in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality to identify source TNL address for data forwarding in case of subsequent handover preparation, if such ACL functionality is deployed.
+
+If the *Management Based MDT PLMN Modification List* IE is contained in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, overwrite any previously stored Management Based MDT PLMN List information in the UE context and use the received information to determine subsequent selection of the UE for management based MDT defined in TS 32.422 [23].
+
+If the *QMC Coordination Request* IE is contained in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node may use it as specified in TS 37.340 [8], and shall, if supported, include the *QMC Coordination Response* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+If the *Source SN to Target SN QMC Information Inquiry* IE set to "true" is contained in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall, if supported, include the *Source SN to Target SN QMC Information* IE in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.
+
+#### **Interactions with the S-NG-RAN node Reconfiguration Completion procedure:**
+
+If the S-NG-RAN node admits a modification of the UE context requiring the M-NG-RAN node to report about the success of the RRC connection reconfiguration procedure, the S-NG-RAN node shall start the timer TXnDCoverall when sending the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the M-NG-RAN node except for a request for conditional configuration. The reception of the S-NG-RAN node RECONFIGURATION COMPLETE message shall stop the timer TXnDCoverall if TXnDCoverall is running.
+
+#### **Interaction with the Activity Notification procedure**
+
+Upon receiving an S-NODE MODIFICATION REQUEST message containing the *Desired Activity Notification Level* IE, the S-NG-RAN node shall, if supported, use this information to decide whether to trigger subsequent Activity Notification procedures, or stop or modify ongoing triggering of these procedures due to a previous request.
+
+#### **Interaction with the Xn-U Address Indication procedure**
+
+For QoS flow mapped to DRBs configured with an SN terminated bearer option and removed from the SDAP in the S-NG-RAN node the S-NG-RAN node may provides data forwarding related information in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE within the *Data Forwarding and offloading Info from source NG-RAN node* IE, in which case the M-NG-RAN node may decide to provide data forwarding addresses to the S-NG-RAN node and trigger the Xn-U Address Indication procedure as specified in TS 37.340 [8].
+
+For QoS flow offloading from the S-NG-RAN node to the M-NG-RAN, the S-NG-RAN node may provide the data forwarding related information in the S-NODE MODIFICATION REQUEST ACKNOWLEDGE within the *Data Forwarding and offloading Info from source NG-RAN node* IE, in which case the M-NG-RAN node may decide to provide data forwarding addresses to the S-NG-RAN node and trigger the Xn-U Address Indication procedure as specified in TS 37.340 [8].
+
+#### **Interactions with the S-NG-RAN node initiated S-NG-RAN node Modification:**
+
+If the *SN triggered* IE set to "TRUE" is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node shall consider that the procedure has been initiated in response to the previously initiated S-NG-RAN node initiated S-NG-RAN node Modification procedure.
+
+#### **Interaction with the Path Switch Request procedure as specified in TS 38.413 [5]:**
+
+For a split PDU session, if the *Integrity Protection Indication* IE and/or the *Confidentiality Protection Indication* IE included in the PATH SWITCH REQUEST ACKNOWLEDGE message is set to "preferred", the M-NG-RAN node may keep the current UP integrity protection and ciphering policy.
+
+### 8.3.3.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE MODIFICATION REQUEST
+ Note right of S-NG-RAN node:
+ S-NG-RAN node-->>M-NG-RAN node: S-NODE MODIFICATION REQUEST REJECT
+ Note left of M-NG-RAN node:
+
+```
+
+Sequence diagram showing an unsuccessful S-Node Modification Preparation. The M-NG-RAN node sends an S-NODE MODIFICATION REQUEST to the S-NG-RAN node, which responds with an S-NODE MODIFICATION REQUEST REJECT.
+
+**Figure 8.3.3.3-1: M-NG-RAN node initiated S-NG-RAN node Modification Preparation, unsuccessful operation**
+
+If the S-NG-RAN node does not admit any modification requested by the M-NG-RAN node, or a failure occurs during the M-NG-RAN node initiated S-NG-RAN node Modification Preparation, the S-NG-RAN node shall send the S-NODE MODIFICATION REQUEST REJECT message to the M-NG-RAN node. The message shall contain the *Cause* IE with an appropriate value.
+
+If the S-NG-RAN node receives a S-NODE MODIFICATION REQUEST message containing the *M-NG-RAN node to S-NG-RAN node Container* IE that does not include required information as specified in TS 37.340 [8], the S-NG-RAN node shall send the S-NODE MODIFICATION REQUEST REJECT message to the M-NG-RAN node.
+
+### 8.3.3.4 Abnormal Conditions
+
+If the S-NG-RAN node receives an S-NODE MODIFICATION REQUEST message including a *PDU Session Resources To Be Added Item* IE, containing neither the *PDU Session Resource Setup Info – SN terminated* IE nor the *PDU Session Resource Setup Info – MN terminated* IE, the S-NG-RAN node shall fail the S-NG-RAN node Modification Preparation procedure indicating an appropriate cause.
+
+If the S-NG-RAN node receives an S-NODE MODIFICATION REQUEST message including a *PDU Session Resources To Be Modified Item* IE, containing neither the *PDU Session Resource Modification Info – SN terminated* IE nor the *PDU Session Resource Modification Info – MN terminated* IE, the S-NG-RAN node shall fail the S-NG-RAN node Modification Preparation procedure indicating an appropriate cause.
+
+If the S-NG-RAN node receives an S-NODE MODIFICATION REQUEST message containing multiple *PDU Session ID* IEs (in the *PDU Session Resources To Be Released List* IE) set to the same value, the S-NG-RAN node shall initiate the release of one corresponding PDU Session and ignore the duplication of the instances of the selected corresponding PDU Sessions.
+
+If the supported algorithms for encryption defined in the *NR Encryption Algorithms* IE in the *NR UE Security Capabilities* IE in the *UE Context Information* IE, plus the mandated support of NEA0 in all UEs (TS 33.501 [58]), do not match any algorithms defined in the configured list of allowed encryption algorithms in the S-NG-RAN node (TS 33.501 [28]), the S-NG-RAN node shall reject the procedure using the S-NODE MODIFICATION REQUEST REJECT message.
+
+If the supported algorithms for integrity defined in the *NR Integrity Protection Algorithms* IE in the *NR UE Security Capabilities* IE in the *UE Context Information* IE do not match any algorithms defined in the configured list of allowed integrity protection algorithms in the S-NG-RAN node (TS 33.501 [28]), the S-NG-RAN node shall reject the procedure using the S-NODE MODIFICATION REQUEST REJECT message.
+
+If the timer TXn<sub>DCprep</sub> expires before the M-NG-RAN node has received the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall regard the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure as being failed and shall release the UE Context at the S-NG-RAN node.
+
+If the Lower Layer presence status change IE set to "re-establish lower layers" is included in the S-NODE MODIFICATION REQUEST message and was not set to "release lower layers" before, the S-NG-RAN node shall ignore the IE.
+
+If the S-NG-RAN node receives an S-NODE MODIFICATION REQUEST message containing, for a PDU session, a *PDU Session Resource Setup Info – SN terminated* IE for which the *Split Session Indicator* IE is included and set to "split", the *Security Result* IE is not included, and either the *Integrity Protection Indication* IE or the *Confidentiality Protection Indication* IE is set to "preferred", it shall reject the PDU session.
+
+#### **Interactions with the S-NG-RAN node Reconfiguration Completion and S-NG-RAN node initiated S-NG-RAN node Release procedure:**
+
+If the timer TXn<sub>DCoverall</sub> expires before the S-NG-RAN node has received the S-NODE RECONFIGURATION COMPLETE or the S-NODE RELEASE REQUEST message, the S-NG-RAN node shall regard the requested modification RRC connection reconfiguration as being not applied by the UE and shall trigger the S-NG-RAN node initiated S-NG-RAN node Release procedure.
+
+#### **Interaction with the S-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure:**
+
+If the M-NG-RAN node, after having initiated the M-NG-RAN node initiated S-NG-RAN node Modification procedure, receives the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall refuse the S-NG-RAN node initiated S-NG-RAN node Modification procedure with an appropriate cause value in the *Cause* IE.
+
+If the M-NG-RAN node has a Prepared S-NG-RAN node Modification and receives the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall respond with the S-NODE MODIFICATION REFUSE message to the S-NG-RAN node with an appropriate cause value in the *Cause* IE.
+
+#### **Interaction with the M-NG-RAN node initiated S-NG-RAN node Release procedure:**
+
+If the M-NG-RAN node receives an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message including a *PDU Session Resources Admitted To Be Added Item* IE, containing neither the *PDU Session Resource Setup Response Info – SN terminated* IE nor the *PDU Session Resource Setup Response Info – MN terminated* IE, the M-NG-RAN node shall trigger the M-NG-RAN node initiated S-NG-RAN node Release procedure indicating an appropriate cause.
+
+If the M-NG-RAN node receives an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message including a *PDU Session Resources Admitted To Be Modified Item* IE, containing neither the *PDU Session Resource Modification Response Info – SN terminated* IE nor the *PDU Session Resource Modification Response Info – MN terminated* IE, the M-NG-RAN node shall trigger the M-NG-RAN node initiated S-NG-RAN node Release procedure indicating an appropriate cause.
+
+If the timer TXn<sub>DCprep</sub> expires before the M-NG-RAN node has received the S-NODE MODIFICATION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall regard the S-NG-RAN node Modification Preparation procedure as being failed and may trigger the M-NG-RAN node initiated S-NG-RAN node Release procedure.
+
+### **8.3.4 S-NG-RAN node initiated S-NG-RAN node Modification**
+
+#### **8.3.4.1 General**
+
+This procedure is used by the S-NG-RAN node to modify the UE context in the S-NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.4.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: S-NODE MODIFICATION REQUIRED
+ Note right of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE MODIFICATION CONFIRM
+ Note right of S-NG-RAN node:
+
+```
+
+Sequence diagram showing the successful operation of S-NG-RAN node initiated S-NG-RAN node Modification. The diagram shows two nodes: M-NG-RAN node and S-NG-RAN node. The S-NG-RAN node sends an S-NODE MODIFICATION REQUIRED message to the M-NG-RAN node, and the M-NG-RAN node responds with an S-NODE MODIFICATION CONFIRM message.
+
+**Figure 8.3.4.2-1: S-NG-RAN node initiated S-NG-RAN node Modification, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the S-NODE MODIFICATION REQUIRED message to the M-NG-RAN node.
+
+When the S-NG-RAN node sends the S-NODE MODIFICATION REQUIRED message, it shall start the timer $TXn_{DCoverall}$ .
+
+The S-NODE MODIFICATION REQUIRED message may contain
+
+- the *S-NG-RAN node to M-NG-RAN node Container* IE.
+- PDU session resources to be modified within the *PDU Session Resources To Be Modified Item* IE;
+- PDU session resources to be released within the *PDU Session Resources To Be Released Item* IE;
+- the *PDCP Change Indication* IE;
+- the *Spare DRB IDs* IE;
+ - the *Required Number of DRB IDs* IE;
+ - the *QoS Flow Mapping Indication* IE;
+ - the *MR-DC Resource Coordination Information* IE.
+
+If the M-NG-RAN node receives a S-NODE MODIFICATION REQUIRED message containing the *PDCP Change Indication* IE, the M-NG-RAN node shall act as specified in TS 37.340 [8].
+
+If the S-NODE MODIFICATION REQUIRED message contains the *MR-DC Resource Coordination Information* IE, the M-NG-RAN node may use it for the purpose of resource coordination with the S-NG-RAN node. The M-NG-RAN node shall consider the value of the received *UL Coordination Information* IE valid until reception of a new update of the IE for the same UE. The M-NG-RAN node shall consider the value of the received *DL Coordination Information* IE valid until reception of a new update of the IE for the same UE. If the *E-UTRA Coordination Assistance Information* IE or the *NR Coordination Assistance Information* IE is contained in the *MR-DC Resource Coordination Information* IE, the M-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the M-NG-RAN node and the S-NG-RAN node.
+
+If the M-NG-RAN node receives an S-NODE MODIFICATION REQUIRED message containing the *Spare DRB IDs* IE, the M-NG-RAN node may take those into consideration to be used for MN-terminated bearers.
+
+If the M-NG-RAN node receives an S-NODE MODIFICATION REQUIRED message containing the *Required Number of DRB IDs* IE, the M-NG-RAN node shall provide new DRB IDs to be used by the S-NG-RAN node for SN-terminated bearers, if such DRB IDs are available, in the *Additional DRB IDs* IE included in the S-NODE MODIFICATION CONFIRM message.
+
+If the M-NG-RAN node is able to perform the modifications requested by the S-NG-RAN node, the M-NG-RAN node shall send the S-NODE MODIFICATION CONFIRM message to the S-NG-RAN node. The S-NODE MODIFICATION CONFIRM message may contain the *M-NG-RAN node to S-NG-RAN node Container* IE.
+
+If the *PDCP Duplication Configuration* IE in the *PDU Session Resource Modification Required Info – SN terminated* IE is contained in the S-NODE MODIFICATION REQUIRED message and set to "configured", the M-NG-RAN node shall, if supported, add the RLC entity of secondary path and the RLC entity of all additional path(s) for the indicated DRB. And if the S-NODE MODIFICATION REQUIRED message contains the *Duplication Activation* IE, the M-NG-RAN node shall, if supported, store this information and use it for the purpose of PDCP duplication.
+
+If the S-NODE MODIFICATION REQUIRED message contains the *RLC Duplication Information* IE, the S-NG-RAN node shall, if supported, store this information and use it for the purpose of PDCP duplication for the indicated DRB with more than two RLC entities.
+
+If the *PDCP Duplication Configuration* IE in the *PDU Session Resource Modification Required Info – SN terminated* IE is contained in the S-NODE MODIFICATION REQUIRED message and set to "de-configured", the M-NG-RAN node shall, if supported, delete the RLC entity of secondary path and the RLC entity of all additional path(s) for the indicated DRB.
+
+The S-NG-RAN node may include for each DRB in the *DRBs To Be Modified List* IE in the S-NODE MODIFICATION REQUIRED message the *RLC Status* IE to indicate that RLC has been reestablished at the S-NG-RAN node and the M-NG-RAN node may trigger PDCP data recovery.
+
+If the S-NODE MODIFICATION REQUIRED message contains the *QoS flows To Be Released List* within the *PDU Session Resource Modification Info – SN terminated* IE, the S-NG-RAN node may also propose to apply forwarding of UL data for which in-order delivery is requested by including the *UL Forwarding Proposal* IE in the *Data Forwarding and Offloading Info from source NG-RAN node* IE within the *PDU Session Resource Modification Required Info – SN terminated* IE of the S-NODE MODIFICATION REQUIRED message. The M-NG-RAN node may include the *PDU Session Level UL Data Forwarding UP TNL Information* IE in the *Data Forwarding Info from target NG-RAN node* IE within the *PDU Session Resource Modification Confirm Info – SN terminated* IE of the S-NODE MODIFICATION CONFIRM message to indicate that it accepts the proposed forwarding.
+
+Upon reception of the S-NODE MODIFICATION CONFIRM message the S-NG-RAN node shall stop the timer $TXnD_{Coverall}$ .
+
+If the S-NODE MODIFICATION CONFIRM message contains the *MR-DC Resource Coordination Information* IE, the S-NG-RAN node should forward it to lower layers and it may use it for the purpose of resource coordination with the M-NG-RAN node, or to coordinate with sidelink resources used in the M-NG-RAN node. The S-NG-RAN node shall consider the value of the received *UL Coordination Information* IE valid until reception of a new update of the IE for the same UE. The S-NG-RAN node shall consider the value of the received *DL Coordination Information* IE valid until reception of a new update of the IE for the same UE. If the *E-UTRA Coordination Assistance Information* IE or the *NR Coordination Assistance Information* IE is contained in the *MR-DC Resource Coordination Information* IE, the S-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the S-NG-RAN node and the M-NG-RAN node.
+
+If the S-NODE MODIFICATION REQUIRED message contains a PDU session resource to be released which is configured with the SCG bearer option within the *PDU sessions to be released List – SN terminated* IE, the S-NG-RAN node shall include the *RLC Mode* IE within the *DRBs To Be Released List* IE in the *PDU Session to be released List – SN terminated* IE in the S-NODE MODIFICATION REQUIRED message. The *RLC Mode* IE indicates the RLC mode used in the S-NG-RAN node for the DRB.
+
+If the *Location Information at S-NODE* IE is included in the S-NODE MODIFICATION REQUIRED, the M-NG-RAN node shall store the included information so that it may be transferred towards the AMF.
+
+If the *QoS Flows Mapped To DRB List* IE is included in the S-NODE MODIFICATION REQUIRED message for a DRB to be modified, the M-NG-RAN node shall replace any existing QoS flow mapping for that DRB with the one received.
+
+If the S-NG-RAN node applied a full configuration or delta configuration, e.g., as part of mobility procedure involving a change of DU, the S-NG-RAN node shall inform the M-NG-RAN node by including the *RRC config indication* IE in the S-NODE MODIFICATION REQUIRED message.
+
+If the S-NODE MODIFICATION CONFIRM message includes the *DRB IDs taken into use* IE, the S-NG-RAN node shall, if applicable, act as specified in TS 37.340 [8]
+
+If the *SCG Indicator* IE is contained in the S-NODE MODIFICATION REQUIRED message and it is set to "released", the M-NG-RAN node shall, if supported, deduce that the SCG is removed.
+
+For each DRB configured as MN-terminated split bearer/SCG bearer, if the *QoS Mapping Information* IE is included in the *DRBs To Be Modified List* IE in the *PDU Session Resource Modification Required Info – MN terminated* IE of the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets which are transmitted from M-NG-RAN node to S-NG-RAN node through the GTP tunnels indicated by the *UP Transport Layer Information* IE.
+
+For each DRB configured as SN-terminated split bearer/MCG bearer, if the *QoS Mapping Information* IE is included in the *DRBs Admitted to be Setup or Modified List* IE in the *PDU Session Resource Modification Confirm Info – SN terminated* IE of the S-NODE MODIFICATION CONFIRM message, the S-NG-RAN node shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets which are transmitted from S-NG-RAN node to M-NG-RAN node through the GTP tunnels indicated by the *UP Transport Layer Information* IE.
+
+If the S-NG-RAN node receives in the S-NODE MODIFICATION CONFIRM message within the *PDU Session Resource Modification Confirm Info – SN terminated* IE a *DRBs Admitted to be Setup or Modified Item* IE with DRB ID(s) that it has not requested to be setup or modified, the S-NG-RAN node shall ignore the contained information.
+
+If the S-NODE MODIFICATION REQUIRED message includes the *SCG UE History Information* IE, the M-NG-RAN node shall, if supported, use the information to update UE History Information with PSCell history.
+
+If the *SCG Activation Request* IE is included in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall consider that the S-NG-RAN node is about to reconfigure the SCG resources as specified in TS 37.340 [8].
+
+If the *CPAC Information Required* IE is included in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall, if supported, consider that the request provides the configuration update for the list of PSCells prepared at the target SN, as described in TS 37.340 [8].
+
+If the *CG-CandidateList* is included in the *S-NG-RAN node to M-NG-RAN node Container* IE in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall, if supported, use it for the purpose of CPAC.
+
+If the *SCG Reconfiguration Notification* IE is included in the S-NODE MODIFICATION REQUIRED message the M-NG-RAN node shall, if supported, consider the request is sent to coordinate CHO or MN-initiated CPC with SCG reconfigurations:
+
+- If the *SCG Reconfiguration Notification* IE is set to "executed", the M-NG-RAN node shall, if supported, consider that a reconfiguration of the SCG resources using SRB3 has been executed. If the *S-NG-RAN node to M-NG-RAN node Container* IE is also included in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall, if supported, consider that the received SCG configuration has already been applied in the UE and should not be forwarded to the UE.
+- If the *SCG Reconfiguration Notification* IE is set to "executed-deleted", the M-NG-RAN node shall, if supported, consider that a reconfiguration with sync of the SCG resources has been executed and earlier CHO or MN-initiated CPC configuration has been deleted in the UE. If the *S-NG-RAN node to M-NG-RAN node Container* IE is also included in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall, if supported, consider that the received SCG configuration has already been applied in the UE and should not be forwarded to the UE.
+
+- If the *SCG Reconfiguration Notification* IE is set to "deleted", the M-NG-RAN node shall, if supported, consider that an earlier CHO or MN-initiated CPC configuration will be deleted in the UE when the SCG configuration provided in the *S-NG-RAN node to M-NG-RAN node Container* IE is delivered to the UE and executed.
+
+If the *SPR availability in UE* IE is included in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node may consider that the UE has generated an SPR for a PSCell change, and may retrieve the SPR from the UE.
+
+#### Interaction with the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure:
+
+If applicable, as specified in TS 37.340 [8], the S-NG-RAN node may receive, after having initiated the S-NG-RAN node initiated S-NG-RAN node Modification procedure, the S-NODE MODIFICATION REQUEST message including the *measGapConfig* contained in the *CG-ConfigInfo* message as defined in TS 38.331 [10] within the *M-NG-RAN node to S-NG-RAN node Container* IE.
+
+If applicable, the S-NG-RAN node may receive, after having initiated the S-NG-RAN node initiated S-NG-RAN node Modification procedure, the S-NODE MODIFICATION REQUEST message including the *SN triggered* IE.
+
+If the *QMC Coordination Request* IE is contained in the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node may use it to determine how to configure the management-based QoE as specified in TS 37.340 [8], and shall, if supported, include the *QMC Coordination Response* IE in the S-NODE MODIFICATION CONFIRM message.
+
+### 8.3.4.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node: (Initiated procedure)
+ S-NG-RAN node->>M-NG-RAN node: S-NODE MODIFICATION REQUIRED
+ M-NG-RAN node-->>S-NG-RAN node: S-NODE MODIFICATION REFUSE
+
+```
+
+Sequence diagram showing an unsuccessful S-NG-RAN node initiated modification. The S-NG-RAN node sends an S-NODE MODIFICATION REQUIRED message to the M-NG-RAN node, which responds with an S-NODE MODIFICATION REFUSE message.
+
+**Figure 8.3.4.3-1: S-NG-RAN node initiated S-NG-RAN node Modification, unsuccessful operation.**
+
+In case the requested modification cannot be performed successfully the M-NG-RAN node shall respond with the S-NODE MODIFICATION REFUSE message to the S-NG-RAN node with an appropriate cause value in the *Cause* IE.
+
+In case that the *Required Number of DRB IDs* IE was included in the S-NODE MODIFICATION REQUIRED message and if the M-NG-RAN node is not able to provide additional DRB IDs, the M-NG-RAN node shall respond with the S-NODE MODIFICATION REFUSE with an appropriate cause value in the *Cause* IE.
+
+The M-NG-RAN node may also provide configuration information in the *M-NG-RAN node to S-NG-RAN node Container* IE.
+
+### 8.3.4.4 Abnormal Conditions
+
+If the M-NG-RAN node receives an S-NODE MODIFICATION REQUIRED message including a *PDU Session Resources To Be Modified Item* IE, containing neither the *PDU Session Resource Modification Required Info – SN terminated* IE nor the *PDU Session Resource Modification Required Info – MN terminated* IE, the M-NG-RAN node shall fail the S-NG-RAN node initiated S-NG-RAN node Modification procedure indicating an appropriate cause.
+
+If the timer TXN<sub>DCoverall</sub> expires before the S-NG-RAN node has received the S-NODE MODIFICATION CONFIRM or the S-NODE MODIFICATION REFUSE message, the S-NG-RAN node shall regard the requested modification as
+
+failed and may take further actions like triggering the S-NG-RAN node initiated S-NG-RAN node Release procedure to release all S-NG-RAN node resources allocated for the UE.
+
+If the value received in the *PDU Session ID* IE of any of the *PDU Sessions Resources To Be Released Items* IE is not known at the M-NG-RAN node, the M-NG-RAN node shall regard the procedure as failed and may take appropriate actions like triggering the M-NG-RAN node initiated S-NG-RAN node Release procedure.
+
+#### **Interaction with the S-NG-RAN node initiated S-NG-RAN node Release procedure:**
+
+If the S-NG-RAN node receives an S-NODE MODIFICATION CONFIRM message including a *PDU Session Resources Admitted To Be Modified Item* IE, containing neither the *PDU Session Resource Modification Confirm Info – SN terminated* IE nor the *PDU Session Resource Modification Confirm Info – MN terminated* IE, the S-NG-RAN node shall trigger the S-NG-RAN node initiated S-NG-RAN node Release procedure indicating an appropriate cause.
+
+#### **Interaction with the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure:**
+
+If the S-NG-RAN node, after having initiated the S-NG-RAN node initiated S-NG-RAN node Modification procedure, receives the S-NODE MODIFICATION REQUEST message including other IEs than an applicable *S-NG-RAN node Security Key* IE and/or *LCID* applicable for PDCP duplication and/or the *SN triggered* IE set to "TRUE", the S-NG-RAN node shall
+
+- regard the S-NG-RAN node initiated S-NG-RAN node Modification Procedure as being failed;
+- stop the *TXnDoverall*, which was started to supervise the S-NG-RAN node initiated S-NG-RAN node Modification procedure;
+- be prepared to receive the S-NODE MODIFICATION REFUSE message from the M-NG-RAN node and;
+- continue with the M-NG-RAN node initiated S-NG-RAN node Modification Preparation procedure as specified in section 8.3.
+
+#### **Interaction with the M-NG-RAN node initiated handover procedure:**
+
+If the M-NG-RAN node, after having initiated the handover procedure, receives the S-NODE MODIFICATION REQUIRED message, the M-NG-RAN node shall refuse the S-NG-RAN node modification procedure with an appropriate cause value in the *Cause* IE.
+
+### **8.3.5 S-NG-RAN node initiated S-NG-RAN node Change**
+
+#### **8.3.5.1 General**
+
+This procedure is used by the S-NG-RAN node to trigger the change of the S-NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.5.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: S-NODE CHANGE REQUIRED
+ Note right of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE CHANGE CONFIRM
+ Note right of S-NG-RAN node:
+
+```
+
+Sequence diagram showing the successful operation of an S-NG-RAN node initiated S-NG-RAN node Change. The diagram shows two nodes: M-NG-RAN node and S-NG-RAN node. The S-NG-RAN node sends an S-NODE CHANGE REQUIRED message to the M-NG-RAN node, and the M-NG-RAN node responds with an S-NODE CHANGE CONFIRM message.
+
+**Figure 8.3.5.2-1: S-NG-RAN node initiated S-NG-RAN node Change, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the S-NODE CHANGE REQUIRED message to the M-NG-RAN node including the *Target S-NG-RAN node ID* IE. When the S-NG-RAN node sends the S-NODE CHANGE REQUIRED message, it shall start the timer $TXn_{DCoverall}$ .
+
+The S-NODE CHANGE REQUIRED message may contain
+
+- the *S-NG-RAN node to S-NG-RAN node Container* IE.
+
+If the M-NG-RAN node is able to perform the change requested by the S-NG-RAN node, the M-NG-RAN node shall send the S-NODE CHANGE CONFIRM message to the S-NG-RAN node. For DRBs configured with the PDCP entity in the S-NG-RAN node, the M-NG-RAN node may include data forwarding related information in the *Data Forwarding Info from target NG-RAN node* IE.
+
+If the S-NODE CHANGE CONFIRM message includes the *DRB IDs taken into use* IE, the S-NG-RAN node shall, if applicable, act as specified in TS 37.340 [8].
+
+The S-NG-RAN node may start data forwarding and stop providing user data to the UE and shall stop the timer $TXn_{DCoverall}$ upon reception of the S-NODE CHANGE CONFIRM message.
+
+If the S-NODE CHANGE REQUIRED message includes the *SCG UE History Information* IE, the M-NG-RAN node shall, if supported, use the information to update UE History Information with PSCell history.
+
+If the S-NODE CHANGE REQUIRED message includes the *SN Mobility Information* IE, the M-NG-RAN node shall, if supported, store this information and use it as defined in TS 38.300 [9].
+
+If the S-NODE CHANGE REQUIRED message includes the *Source PSCell ID* IE, the M-NG-RAN node shall, if supported, store the information and act as specified in TS 38.300 [9].
+
+The M-NG-RAN node may also provide configuration information in the *M-NG-RAN node to S-NG-RAN node Container* IE.
+
+If the *Conditional PSCell Change Information Required* IE is included in the S-NODE CHANGE REQUIRED message, the M-NG-RAN node shall, if supported, consider that the requirement concerns CPAC, as described in TS 37.340 [8]. If the *S-CPAC Request* IE set to "initiation" is also contained in the *Conditional PSCell Change Information Required* IE included in the S-NODE CHANGE REQUIRED message, the M-NG-RAN node shall, if supported, consider that the procedure is triggered for S-CPAC preparation, as described in TS 37.340 [8]. The *S-NG-RAN node to M-NG-RAN node Container* IE within the *Conditional PSCell Change Information Required* IE contains at least the suggested PSCell list for each candidate target S-NG-RAN node. Accordingly, the M-NG-RAN node may include the *Conditional PSCell Change Information Confirm* IE in the S-NODE CHANGE CONFIRM message.
+
+If the *Estimated Arrival Probability* IE is contained in the *Conditional PSCell Change Information Required* IE included in the S-NODE CHANGE REQUIRED message, the M-NG-RAN node shall, if supported, forward this information to the candidate target S-NG-RAN node, then the candidate target S-NG-RAN node may use the information to allocate necessary resources for the incoming CPAC procedure.
+
+If the *Multiple Target S-NG-RAN Node List* IE is included in the S-NODE CHANGE REQUIRED message, if multiple Target S-NG-RAN nodes are prepared, the M-NG-RAN node may include the *Additional List of PDU Session Resource Change Confirm Info – SN Terminated* IE in the S-NODE CHANGE CONFIRM message to provide different data forwarding addresses for different Target S-NG-RAN nodes.
+
+If the *Source SN to Target SN QMC Information* IE is contained in the S-NODE CHANGE REQUIRED message, the M-NG-RAN node shall, if supported, use it for QoE measurements handling, as specified in TS 37.340 [8].
+
+#### Interaction with M-NG-RAN node initiated S-NG-RAN node Release:
+
+If the M-NG-RAN node receives the S-NODE CHANGE REQUIRED message indicating releasing target S-NG-RAN node(s) and cancelling all prepared PSCells in the target S-NG-RAN node(s), the M-NG-RAN shall, if supported, trigger the M-NG-RAN node initiated S-NG-RAN node release procedure to the target S-NG-RAN node(s) and cancel all the prepared PSCells at the target S-NG-RAN node(s).
+
+### 8.3.5.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: S-NODE CHANGE REQUIRED
+ Note right of M-NG-RAN node:
+ M-NG-RAN node-->>S-NG-RAN node: S-NODE CHANGE REFUSE
+
+```
+
+Sequence diagram showing an unsuccessful S-NG-RAN node change operation. The S-NG-RAN node sends an S-NODE CHANGE REQUIRED message to the M-NG-RAN node, which responds with an S-NODE CHANGE REFUSE message.
+
+Figure 8.3.5.3-1: S-NG-RAN node initiated S-NG-RAN node Change, unsuccessful operation.
+
+In case the request modification cannot accept the request to change the S-NG-RAN node the M-NG-RAN node shall respond with the S-NODE CHANGE REFUSE message to the S-NG-RAN node with an appropriate cause value in the *Cause* IE.
+
+### 8.3.5.4 Abnormal Conditions
+
+If the timer TXnD<sub>Coverall</sub> expires before the S-NG-RAN node has received the S-NODE CHANGE CONFIRM or the S-NODE CHANGE REFUSE message, the S-NG-RAN node shall regard the requested change as failed and may take further actions like triggering the S-NG-RAN node initiated S-NG-RAN node Release procedure to release all S-NG-RAN node resources allocated for the UE.
+
+If the M-NG-RAN node receives an S-NODE CHANGE REQUIRED message including a *PDU Session SN Change Required Item* IE, not containing the *PDU Session Resource Change Required Info – SN terminated* IE, the M-NG-RAN node shall fail the S-NG-RAN node initiated S-NG-RAN node Change procedure indicating an appropriate cause.
+
+#### Interaction with the M-NG-RAN node initiated Handover Preparation procedure:
+
+If the M-NG-RAN node, after having initiated the Handover Preparation procedure, receives the S-NODE CHANGE REQUIRED message, the M-NG-RAN node shall refuse the S-NG-RAN node initiated S-NG-RAN node Change procedure with an appropriate cause value in the *Cause* IE.
+
+#### Interaction with the S-NG-RAN node initiated S-NG-RAN node Release procedure:
+
+If the S-NG-RAN node receives an S-NODE CHANGE CONFIRM message including a *PDU Session SN Change Confirm Item* IE, not containing the *PDU Session Resource Change Confirm Info – SN terminated* IE, the S-NG-RAN node shall trigger the S-NG-RAN node initiated S-NG-RAN node Release procedure indicating an appropriate cause.
+
+## 8.3.6 M-NG-RAN node initiated S-NG-RAN node Release
+
+### 8.3.6.1 General
+
+The M-NG-RAN node initiated S-NG-RAN node Release procedure is triggered by the M-NG-RAN node to initiate the release of the resources for a specific UE.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.6.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE RELEASE REQUEST
+ S-NG-RAN node-->>M-NG-RAN node: S-NODE RELEASE REQUEST ACKNOWLEDGE
+ Note right of S-NG-RAN node:
+
+```
+
+Sequence diagram showing the successful operation of M-NG-RAN node initiated S-NG-RAN node Release. The M-NG-RAN node sends an S-NODE RELEASE REQUEST to the S-NG-RAN node, which responds with an S-NODE RELEASE REQUEST ACKNOWLEDGE.
+
+**Figure 8.3.6.2-1: M-NG-RAN node initiated S-NG-RAN node Release, successful operation**
+
+The M-NG-RAN node initiates the procedure by sending the S-NODE RELEASE REQUEST message. Upon reception of the S-NODE RELEASE REQUEST message the S-NG-RAN node shall stop providing user data to the UE.
+
+The *S-NG-RAN node UE XnAP ID* IE shall be included if it has been obtained from the S-NG-RAN node. The M-NG-RAN node shall provide appropriate information within the *Cause* IE. The M-NG-RAN node may also provide appropriate information per PDU session resource within the *Cause* IE of the *PDU Session Resources To Be Released List* IE.
+
+Upon reception of the S-NODE RELEASE REQUEST message containing *UE Context Kept Indicator* IE set to "True", the S-NG-RAN node shall, if supported, only initiate the release of the resources related to the UE-associated signalling connection between the M-NG-RAN node and the S-NG-RAN node.
+
+If the S-NG-RAN node confirms the request to release S-NG-RAN node resources, it shall send the S-NODE RELEASE REQUEST ACKNOWLEDGE message to the M-NG-RAN node.
+
+If the S-NODE RELEASE REQUEST message contains a PDU session resource to be released which is configured with the SCG bearer option within the *PDU Session Resources To Be Released List* IE, the S-NG-RAN node shall include the *RLC Mode* IE within the *DRBs To Be Released List* IE in the S-NODE RELEASE REQUEST ACKNOWLEDGE message. The *RLC Mode* IE indicates the RLC mode used in the S-NG-RAN node for the DRB.
+
+If the S-NODE RELEASE REQUEST ACKNOWLEDGE message includes the *SCG UE History Information* IE, the M-NG-RAN node shall, if supported, use the information to update UE History Information with PSCell history.
+
+If the S-NODE RELEASE REQUEST ACKNOWLEDGE message includes the *SN Mobility Information* IE, the M-NG-RAN node shall, if supported, store this information and use it as defined in TS 38.300 [9].
+
+#### Interaction with the Xn-U Address Indication procedure
+
+If the S-NG-RAN node provides data forwarding related information in the S-NODE RELEASE REQUEST ACKNOWLEDGE message for QoS flows mapped to DRBs configured with an SN terminated bearer option in the *PDU Sessions To Be Released List - SN terminated* IE, the M-NG-RAN node may decide to provide data forwarding addresses to the S-NG-RAN node and trigger the Xn-U Address Indication procedure as specified in TS 37.340 [8].
+
+If the S-NODE RELEASE REQUEST message concerns a UE for which a Conditional PSCell Change has been triggered, the S-NG-RAN node shall, if supported, consider that the triggered Conditional PSCell Change has been executed, and M-NG-RAN node triggers the Xn-U Address Indication procedure as specified in TS 37.340 [8].
+
+#### Interaction with the SN Status Transfer procedure
+
+If the *UE Context Kept Indicator* IE set to "True" and the *DRBs transferred to MN* IE are included in the S-NODE RELEASE REQUEST message, the S-NG-RAN node shall, if supported, provide the uplink/downlink PDCP SN and HFN status for the listed DRBs, as specified in TS 37.340 [8].
+
+### 8.3.6.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: S-NODE RELEASE REQUEST
+ Note right of S-NG-RAN node:
+ S-NG-RAN node-->>M-NG-RAN node: S-NODE RELEASE REJECT
+ Note left of M-NG-RAN node:
+
+```
+
+Sequence diagram showing an unsuccessful S-NG-RAN node release operation initiated by the M-NG-RAN node. The M-NG-RAN node sends an S-NODE RELEASE REQUEST to the S-NG-RAN node, which responds with an S-NODE RELEASE REJECT.
+
+**Figure 8.3.6.3-1: M-NG-RAN node initiated S-NG-RAN node Release, unsuccessful operation**
+
+If the S-NG-RAN node cannot confirm the request to release S-NG-RAN node resources, it shall send the S-NODE RELEASE REJECT message to the M-NG-RAN node with an appropriate cause indicated in the *Cause* IE.
+
+### 8.3.6.4 Abnormal Conditions
+
+If the S-NODE RELEASE REQUEST message refer to a context that does not exist, the S-NG-RAN node shall ignore the message.
+
+When the M-NG-RAN node has initiated the procedure and did not include the *S-NG-RAN node UE XnAP ID* IE the M-NG-RAN node shall regard the resources for the UE at the S-NG-RAN node as being fully released.
+
+#### Interactions with the UE Context Release procedure:
+
+If the M-NG-RAN node does not receive the reply from the S-NG-RAN node before it has to release the EN-DC connection, or it receives S-NODE RELEASE REQUEST REJECT, it may trigger the UE Context Release procedure. If the S-NG-RAN node received the UE CONTEXT RELEASE right after receiving the S-NODE RELEASE REQUEST (and before or after responding to it), the S-NG-RAN node shall consider the related M-NG-RAN node initiated S-NG-RAN node Release procedure as being the resolution of abnormal conditions and release the related UE context immediately.
+
+## 8.3.7 S-NG-RAN node initiated S-NG-RAN node Release
+
+### 8.3.7.1 General
+
+This procedure is triggered by the S-NG-RAN node to initiate the release of the resources for a specific UE.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.7.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: S-NODE RELEASE REQUIRED
+ Note right of M-NG-RAN node:
+ M-NG-RAN node-->>S-NG-RAN node: S-NODE RELEASE CONFIRM
+ Note right of S-NG-RAN node:
+
+```
+
+Sequence diagram showing the successful operation of S-NG-RAN node initiated S-NG-RAN node Release. The diagram shows two nodes: M-NG-RAN node and S-NG-RAN node. The S-NG-RAN node sends an S-NODE RELEASE REQUIRED message to the M-NG-RAN node, and the M-NG-RAN node responds with an S-NODE RELEASE CONFIRM message.
+
+**Figure 8.3.7.2-1: S-NG-RAN node initiated S-NG-RAN node Release, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the S-NODE RELEASE REQUIRED message to the M-NG-RAN node.
+
+Upon reception of the S-NODE RELEASE REQUIRED message, the M-NG-RAN node replies with the S-NODE RELEASE CONFIRM message.
+
+For each SN-terminated PDU session resource, the M-NG-RAN node may include the *DL Forwarding UP Address* IE and the *UL Forwarding UP Address* IE within the *PDU Session Resources To Be Released Item* IE to indicate that it requests data forwarding of uplink and downlink packets to be performed for that bearer.
+
+The S-NG-RAN node may start data forwarding and stop providing user data to the UE upon reception of the S-NODE RELEASE CONFIRM message,
+
+If the S-NODE RELEASE REQUIRED message contains an PDU session resource to be released which is configured with the SCG bearer option within the *PDU sessions to be released List – SN terminated* IE, the S-NG-RAN node shall include the *RLC Mode* IE within the *DRBs To Be Released List* IE in the *PDU Session to be released List – SN terminated* IE in the S-NODE RELEASE REQUIRED message. The *RLC Mode* IE indicates the RLC mode used in the S-NG-RAN node for the DRB.
+
+If the S-NODE RELEASE CONFIRM message includes the *DRB IDs taken into use* IE, the S-NG-RAN node shall, if applicable, act as specified in TS 37.340 [8].
+
+If the *S-NG-RAN node to M-NG-RAN node Container* IE is included in the S-NODE RELEASE REQUIRED message, the M-NG-RAN node may use the contained information to apply delta configuration.
+
+If the S-NODE RELEASE REQUIRED message includes the *SCG UE History Information* IE, the M-NG-RAN node shall, if supported, use the information to update UE History Information with PSCell history.
+
+### 8.3.7.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.7.4 Abnormal Conditions
+
+Void.
+
+## 8.3.8 S-NG-RAN node Counter Check
+
+### 8.3.8.1 General
+
+This procedure is initiated by the S-NG-RAN node to request the M-NG-RAN node to execute a counter check procedure to verify the value of the PDCP COUNTs associated with SCG bearers established in the S-NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.8.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of M-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: S-NODE COUNTER CHECK REQUEST
+ Note right of M-NG-RAN node:
+ Note right of S-NG-RAN node:
+```
+
+Sequence diagram showing the S-NG-RAN node Counter Check procedure, successful operation. The S-NG-RAN node sends an S-NODE COUNTER CHECK REQUEST message to the M-NG-RAN node.
+
+**Figure 8.3.8.2-1: S-NG-RAN node Counter Check procedure, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the S-NODE COUNTER CHECK REQUEST message to the M-NG-RAN node.
+
+Upon reception of the S-NODE COUNTER CHECK REQUEST message, the M-NG-RAN node may perform the RRC counter check procedure as specified in TS 33.401 [29] and 33.501 [28].
+
+### 8.3.8.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.8.4 Abnormal Conditions
+
+Void.
+
+## 8.3.9 RRC Transfer
+
+### 8.3.9.1 General
+
+The purpose of the RRC Transfer procedure is to deliver a PDCP-C PDU encapsulating an LTE RRC message or NR RRC message to the S-NG-RAN-NODE that it may then be forwarded to the UE, or from the S-NG-RAN-NODE, if it was received from the UE. The delivery status may also be provided from the S-NG-RAN-NODE to the M-NG-RAN-NODE using the RRC Transfer.
+
+The procedure is also used to enable transfer one of the following messages from the M-NG-RAN-NODE to the S-NG-RAN-NODE, when received from the UE:
+
+- the NR RRC message container with the NR measurements;
+- the E-UTRA RRC message container with the E-UTRA measurements;
+- the NR RRC message container with the NR failure information;
+- the NR RRC message container with the *RRReconfigurationComplete* message;
+- the NR RRC message container with the UE assistance information;
+- the NR RRC message container with the IAB other information.
+
+In case of RACH based SDT without UE context relocation, this procedure is also used to deliver a PDCP-C PDU encapsulating an NR RRC message between the new NG-RAN node and the old NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.9.2 Successful Operation
+
+
+
+Figure 8.3.9.2-1: RRC Transfer procedure for dual connectivity, successful operation. The diagram shows two nodes: M/S-NG-RAN node on the left and S/M-NG-RAN node on the right. A horizontal arrow labeled 'RRC TRANSFER' points from the M/S-NG-RAN node to the S/M-NG-RAN node. Both nodes are connected to a common horizontal line at the bottom, representing the UE.
+
+**Figure 8.3.9.2-1: RRC Transfer procedure for dual connectivity, successful operation.**
+
+
+
+Figure 8.3.9.2-2: RRC Transfer procedure for SDT, successful operation. The diagram shows two nodes: New/Old NG-RAN node on the left and Old/New NG-RAN node on the right. A horizontal arrow labeled 'RRC TRANSFER' points from the New/Old NG-RAN node to the Old/New NG-RAN node. Both nodes are connected to a common horizontal line at the bottom, representing the UE.
+
+**Figure 8.3.9.2-2: RRC Transfer procedure for SDT, successful operation.**
+
+#### Dual Connectivity
+
+The M-NG-RAN-NODE initiates the procedure by sending the RRC TRANSFER message to the S-NG-RAN-NODE or the S-NG-RAN-NODE initiates the procedure by sending the RRC TRANSFER message to the M-NG-RAN-NODE.
+
+If the S-NG-RAN-NODE receives an RRC TRANSFER message which does not include the *RRC Container* IE in the *Split SRB* IE, or the *RRC Container* IE in the *NR UE Report* IE, or the the *RRC Container* IE in the *Fast MCG Recovery via SRB3 from MN to SN* IE, or the the *RRC Container* IE in the *Fast MCG Recovery via SRB3 from SN to MN* IE, it shall ignore the message. If the S-NG-RAN-NODE receives an RRC TRANSFER message with the *Delivery Status* IE in the *Split SRB* IE, it shall ignore the message. If the S-NG-RAN-NODE receives the *RRC Container* IE in the *Split SRB* IE, it shall deliver the contained PDCP-C PDU encapsulating an RRC message to the UE. If the S-NG-RAN-NODE receives the *RRC Container* IE in the *Fast MCG Recovery via SRB3 from MN to SN* IE, the S-NG-RAN-NODE shall deliver the contained RRC container encapsulating an RRC message to the UE.
+
+If the M-NG-RAN-NODE receives the *Delivery Status* IE in the *Split SRB* IE, the M-NG-RAN-NODE shall consider RRC messages up to the indicated NR PDCP SN as having been successfully delivered to UE by S-NG-RAN-NODE. If the M-NG-RAN-NODE receives the *RRC Container* IE in the *Fast MCG Recovery via SRB3 from SN to MN* IE, the M-NG-RAN-NODE shall consider MCG link failure detected at the UE as specified in TS 37.340 [8].
+
+#### SDT
+
+The new NG-RAN-NODE initiates the procedure by sending the RRC TRANSFER message to the old NG-RAN-NODE or the old NG-RAN-NODE initiates the procedure by sending the RRC TRANSFER message to the new NG-RAN-NODE.
+
+If the new NG-RAN node receives the *RRC Container* IE in the *SDT SRB between New NG-RAN node and Old NG-RAN node* IE, it shall deliver the contained PDCP-C PDU encapsulating an RRC message to the UE. If the old NG-
+
+RAN-NODE receives the *RRC Container* IE in the *SDT SRB between New NG-RAN node and Old NG-RAN node* IE, it shall consider the contained PDCP-C PDU encapsulating an RRC message from the UE.
+
+### 8.3.9.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.9.4 Abnormal Conditions
+
+In case of the split SRBs, the receiving node may ignore the message, if the M-NG-RAN-NODE has not indicated possibility of RRC transfer at the bearer setup.
+
+## 8.3.10 Notification Control Indication
+
+### 8.3.10.1 General
+
+The purpose of the Notification Control indication procedure is to provide information that for already established GBR QoS flow(s) for which notification control has been requested, the NG-RAN node involved in Dual Connectivity cannot fulfil the GFBR anymore or that it can fulfil the GFBR again.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.10.2 Successful Operation – M-NG-RAN node initiated
+
+
+
+```
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: NOTIFICATION CONTROL INDICATION
+ Note right of S-NG-RAN node:
+```
+
+The diagram illustrates a sequence of two vertical lifelines. The left lifeline is labeled 'M-NG-RAN node' and the right is labeled 'S-NG-RAN node'. Both labels are in rectangular boxes. A horizontal arrow points from the M-NG-RAN node to the S-NG-RAN node, with the text 'NOTIFICATION CONTROL INDICATION' centered above it. Each lifeline has a thick horizontal bar at its base.
+
+Sequence diagram showing the Notification Control Indication procedure initiated by the M-NG-RAN node.
+
+**Figure 8.3.10.2-1: Notification Control Indication procedure, M-NG-RAN node initiated, successful operation.**
+
+The M-NG-RAN node initiates the procedure by sending the NOTIFICATION CONTROL INDICATION message to the S-NG-RAN node.
+
+This procedure is triggered to notify the S-NG-RAN node for SN-terminated bearers, that resources requested from the M-NG-RAN node can either not fulfil the GFBR anymore or that the GFBR can be fulfilled again, as specified in TS 37.340 [8]. For a QoS flow indicated as not fulfilled anymore the M-NG-RAN node may also indicate an alternative QoS parameter set which it can currently fulfil in the *Current QoS Parameters Set Index* IE.
+
+### 8.3.10.3 Successful Operation – S-NG-RAN node initiated
+
+
+
+```
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: NOTIFICATION CONTROL INDICATION
+ Note right of M-NG-RAN node:
+```
+
+The diagram illustrates a sequence of two vertical lifelines. The left lifeline is labeled 'M-NG-RAN node' and the right lifeline is labeled 'S-NG-RAN node'. Both lifelines have a thick horizontal bar at the bottom. A horizontal arrow points from the S-NG-RAN node lifeline to the M-NG-RAN node lifeline, with the text 'NOTIFICATION CONTROL INDICATION' centered above the arrow.
+
+Sequence diagram showing the Notification Control Indication procedure initiated by the S-NG-RAN node.
+
+**Figure 8.3.10.3-1: Notification Control Indication procedure, S-NG-RAN node initiated, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the NOTIFICATION CONTROL INDICATION message to the M-NG-RAN node.
+
+This procedure is triggered to notify the M-NG-RAN node that for MN-terminated bearers resources requested from the S-NG-RAN node can either not fulfil the GFBR anymore or that the GFBR can be fulfilled again, as specified in TS 37.340 [8]. For a QoS flow indicated as not fulfilled anymore the S-NG-RAN node may also indicate an alternative QoS parameters set which it can currently fulfil in the *Current QoS Parameters Set Index* IE.
+
+This procedure is triggered to notify the M-NG-RAN node that resources requested for SN-terminated bearers can either not fulfil the GFBR anymore or that the GFBR can be fulfilled again, as specified in TS 37.340 [8]. For a QoS flow indicated as not fulfilled anymore the S-NG-RAN node may also indicate an alternative QoS parameters set which it can currently fulfil in the *Current QoS Parameters Set Index* IE.
+
+### 8.3.10.4 Abnormal Conditions
+
+Void.
+
+## 8.3.11 Activity Notification
+
+### 8.3.11.1 General
+
+The purpose of the Activity Notification procedure is to allow an NG-RAN node to send notification to another NG-RAN node concerning:
+
+- user data traffic activity for the UE, or
+- user data traffic activity of already established QoS flows or PDU sessions, or
+- RAN Paging failure.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.11.2 Successful Operation
+
+
+
+```
+
+graph LR
+ node1[NG-RAN node1] -- "ACTIVITY NOTIFICATION" --> node2[NG-RAN node2]
+ node1 --- UP1[ ]
+ node2 --- UP2[ ]
+ style UP1 fill:black,stroke:none
+ style UP2 fill:black,stroke:none
+
+```
+
+Diagram illustrating the successful operation of an Activity Notification procedure. Two boxes, 'NG-RAN node1' and 'NG-RAN node2', are shown. A horizontal arrow labeled 'ACTIVITY NOTIFICATION' points from 'NG-RAN node1' to 'NG-RAN node2'. Each node is connected to a thick horizontal line at the bottom, representing the user plane.
+
+**Figure 8.3.11.2-1: Activity Notification, successful operation**
+
+NG-RAN node<sub>1</sub> initiates the procedure by sending the ACTIVITY NOTIFICATION message to NG-RAN node<sub>2</sub>.
+
+The ACTIVITY NOTIFICATION message may contain one or more of the below:
+
+- notification for UE context level user plane activity in the *UE Context level user plane activity report* IE.
+- notification of user plane activity for the already established PDU sessions within the *PDU Session Resource Activity Notify List* IE.
+- notification of user plane activity for the already established QoS flows within the *PDU Session Resource Activity Notify List* IE.
+- notification of RAN Paging failure.
+
+If the ACTIVITY NOTIFICATION message contains the *RAN Paging Failure* IE, NG-RAN node<sub>2</sub> shall consider that RAN Paging has failed in NG-RAN node<sub>1</sub> for the UE. NG-RAN node<sub>2</sub> may discard the user plane data for that UE and consider that the UE context is unchanged.
+
+NOTE: As specified in TS 37.340 [8], in case of user data activity notification, NG-RAN node<sub>1</sub> acts as a Secondary Node, while in case of RAN Paging failure indication, NG-RAN node<sub>1</sub> acts as a Master Node.
+
+### 8.3.11.3 Abnormal Conditions
+
+If the *User Plane traffic activity report* IE for a reporting object is reported by NG-RAN node<sub>1</sub> as "re-activated" and the reporting object was not reported as "inactive", the report for the concerned reporting object shall be ignored by NG-RAN node<sub>2</sub>.
+
+## 8.3.12 E-UTRA – NR Cell Resource Coordination
+
+### 8.3.12.1 General
+
+The purpose of the E-UTRA – NR Cell Resource Coordination procedure is to enable coordination of radio resource allocation between an ng-eNB and a gNB that are sharing spectrum and whose coverage areas are fully or partially overlapping. During the procedure, the ng-eNB and gNB shall exchange their intended resource allocations for data traffic, and, if possible, converge to a shared resource. The procedure is only to be used for the purpose of E-UTRA – NR spectrum sharing.
+
+The procedure uses non-UE-associated signalling.
+
+### 8.3.12.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant ng-eNB
+ participant gNB
+ Note left of ng-eNB:
+ ng-eNB->>gNB: E-UTRA - NR CELL RESOURCE COORDINATION REQUEST
+ Note right of gNB:
+ gNB-->>ng-eNB: E-UTRA - NR CELL RESOURCE COORDINATION RESPONSE
+ Note left of ng-eNB:
+
+```
+
+Sequence diagram for ng-eNB-initiated E-UTRA – NR Cell Resource Coordination request, successful operation. The ng-eNB sends a request to the gNB, and the gNB responds with a response.
+
+**Figure 8.3.12.2-1: ng-eNB-initiated E-UTRA – NR Cell Resource Coordination request, successful operation**
+
+
+
+```
+
+sequenceDiagram
+ participant ng-eNB
+ participant gNB
+ Note right of gNB:
+ gNB->>ng-eNB: E-UTRA - NR CELL RESOURCE COORDINATION REQUEST
+ Note left of ng-eNB:
+ ng-eNB-->>gNB: E-UTRA - NR CELL RESOURCE COORDINATION RESPONSE
+ Note right of gNB:
+
+```
+
+Sequence diagram for gNB-initiated E-UTRA – NR Cell Resource Coordination request, successful operation. The gNB sends a request to the ng-eNB, and the ng-eNB responds with a response.
+
+**Figure 8.3.12.2-2: gNB-initiated E-UTRA – NR Cell Resource Coordination request, successful operation**
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message and the E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message shall include the *Interface Instance Indication IE* to identify the corresponding interface instance.
+
+#### ng-eNB initiated E-UTRA – NR Cell Resource Coordination:
+
+An ng-eNB initiates the procedure by sending the E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message to an gNB over the Xn interface. The gNB extracts the *Data Traffic Resource Indication IE* and it replies by sending the E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message. The gNB shall calculate the full ng-eNB resource allocation by combining the *Data Traffic Resource Indication IE* and the *Protected E-UTRA Resource Indication IE* that were most recently received from the ng-eNB.
+
+In case of conflict between the most recently received *Data Traffic Resource Indication IE* and the most recently received *Protected E-UTRA Resource Indication IE*, the gNB shall give priority to the *Protected E-UTRA Resource Indication IE*.
+
+#### gNB initiated E-UTRA – NR Cell Resource Coordination:
+
+An gNB initiates the procedure by sending the E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message to an ng-eNB. The ng-eNB replies with the E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message.
+
+In case of conflict between the most recently received *Data Traffic Resource Indication IE* and the most recently received *Protected E-UTRA Resource Indication IE*, the gNB shall give priority to the *Protected E-UTRA Resource Indication IE*.
+
+## 8.3.13 Secondary RAT Data Usage Report
+
+### 8.3.13.1 General
+
+This procedure is initiated by the S-NG-RAN node to provide information on the used resources of the secondary RAT (e.g. NR resources during MR-DC operation) as specified in TS 23.501 [7].
+
+The procedure uses UE-associated signalling.
+
+### 8.3.13.2 Successful Operation
+
+
+
+Diagram illustrating the Secondary RAT Data Usage Report procedure, successful operation. The diagram shows two rectangular boxes at the top, representing the S-NG-RAN and M-NG-RAN nodes. Below these boxes is a large black rectangular area, which represents the signalling message exchange. The caption indicates this is the successful operation procedure.
+
+**Figure 8.3.13.2-1: Secondary RAT Data Usage Report procedure, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the SECONDARY RAT DATA USAGE REPORT message to the M-NG-RAN node.
+
+### 8.3.13.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.13.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.3.14 Trace Start
+
+### 8.3.14.1 General
+
+The purpose of the Trace Start procedure is to allow the M-NG-RAN node to request the S-NG-RAN node to initiate a trace session for a UE. The procedure uses UE-associated signalling.
+
+### 8.3.14.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of S-NG-RAN node:
+ Note right of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: TRACE START
+
+```
+
+Sequence diagram showing the successful operation of the Trace Start procedure. An M-NG-RAN node sends a TRACE START message to an S-NG-RAN node. Both nodes are represented by boxes with vertical lines extending downwards to horizontal bars representing the timeline of the UE.
+
+Figure 8.3.14.2-1: Trace Start, successful operation
+
+The Trace Start procedure is initiated by the M-NG-RAN sending the TRACE START message to the S-NG-RAN for that specific UE. Upon reception of the TRACE START message, the S-NG-RAN node shall initiate the requested trace session as described in TS 32.422 [23].
+
+If the *Trace Activation* IE includes
+
+- the *MDT Activation* IE set to "Immediate MDT and Trace", and if the S-NG-RAN node is a gNB, it shall, if supported, initiate the requested trace session and MDT session as described in TS 32.422[23].
+- the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", and if the S-NG-RAN node is a gNB, it shall, if supported, initiate the requested MDT session as described in TS 32.422[23] and the S-NG-RAN node shall ignore the *Interfaces To Trace* IE and the *Trace Depth* IE.
+- the *MDT Location Information* IE, within the *MDT Configuration* IE, and if the S-NG-RAN node is a gNB, it shall, if supported, store this information and take it into account in the requested MDT session.
+- the *MDT Activation* IE set to "Immediate MDT Only" or "Logged MDT only", and if the *Signalling based MDT PLMN List* IE is included in the *MDT Configuration* IE, and if the S-NG-RAN node is gNB, it may use it to propagate the MDT Configuration as described in TS 37.320 [43].
+- the *Bluetooth Measurement Configuration* IE, within the *MDT Configuration* IE, and if the S-NG-RAN node is a gNB, it shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *WLAN Measurement Configuration* IE, within the *MDT Configuration* IE, and if the S-NG-RAN node is a gNB, it shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *Sensor Measurement Configuration* IE, within the *MDT Configuration* IE, the S-NG-RAN node shall take it into account for MDT Configuration as described in TS 37.320 [43].
+- the *MDT Configuration* IE, and if the S-NG-RAN Node is a gNB at least the *MDT Configuration-NR* IE shall be present, while if the S-NG-RAN Node is an ng-eNB at least the *MDT Configuration-EUTRA* IE shall be present.
+
+If the *Area Scope* IE is not present in the *MDT Configuration* IE, the S-NG-RAN node shall consider that the MDT Configuration is applied to all PLMNs indicated in the MDT PLMN List, as described in TS 32.422 [23].
+
+If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE included in the TRACE START message, the S-NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN. Upon reception of the *PNI-NPN Area Scope of MDT* IE, the S-NG-RAN node shall consider that the area scope for MDT measurement collection of PNI-NPN areas is defined only by the areas included in the *PNI-NPN Area Scope of MDT* IE.
+
+### 8.3.14.3 Abnormal Conditions
+
+If the *Trace Activation* IE is not included in the TRACE START message, the S-NG-RAN node shall ignore the message.
+
+If both the *PNI-NPN Area Scope of MDT* IE and the *Area Scope of MDT-NR* IE are included in the *MDT Configuration-NR* IE in the TRACE START message, and the *Area Scope of MDT-NR* IE is set to "PNI-NPN based", the S-NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas, and ignore the *PNI-NPN Area Scope of MDT* IE.
+
+If the *PNI-NPN Area Scope of MDT* IE is included in the *MDT Configuration-NR* IE in the TRACE START message, and the *Area Scope of MDT-NR* IE is not included, the target NG-RAN node shall ignore the *PNI-NPN Area Scope of MDT* IE, and consider that the MDT Configuration for NR is applied to all PLMNs indicated in the MDT PLMN List described in TS 32.422 [23].
+
+## 8.3.15 Deactivate Trace
+
+### 8.3.15.1 General
+
+The purpose of the Deactivate Trace procedure is to allow the M-NG-RAN node to request the S-NG-RAN node to stop the trace session for the indicated trace reference. The procedure uses UE-associated signalling.
+
+### 8.3.15.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note right of M-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: DEACTIVATE TRACE
+ Note left of S-NG-RAN node:
+ S-NG-RAN node-->>M-NG-RAN node:
+ Note right of S-NG-RAN node:
+```
+
+The diagram illustrates the successful operation of the Deactivate Trace procedure. It features two vertical lifelines: 'S-NG-RAN node' on the left and 'M-NG-RAN node' on the right. A horizontal arrow labeled 'DEACTIVATE TRACE' points from the M-NG-RAN node to the S-NG-RAN node. Both lifelines have a small horizontal bar at the bottom, representing the user equipment (UE) context.
+
+Sequence diagram showing the Deactivate Trace procedure. An M-NG-RAN node sends a DEACTIVATE TRACE message to an S-NG-RAN node.
+
+Figure 8.3.15.2-1: Deactivate Trace, successful operation
+
+The Deactivate Trace procedure is initiated by the M-NG-RAN by sending the DEACTIVATE TRACE to the S-NG-RAN node for that specific UE. Upon reception of the DEACTIVATE TRACE message, the S-NG-RAN shall stop the trace session for the indicated trace reference in the *NG-RAN Trace ID* IE.
+
+### 8.3.15.3 Abnormal Conditions
+
+Void.
+
+## 8.3.16 Cell Traffic Trace
+
+### 8.3.16.1 General
+
+The purpose of the Cell Traffic Trace procedure is to send the allocated Trace Recording Session Reference and the Trace Reference to the M-NG-RAN node. The procedure uses UE-associated signalling.
+
+### 8.3.16.2 Successful Operation
+
+
+
+Sequence diagram for Cell Traffic Trace procedure, successful operation. It shows two nodes: S-NG-RAN node on the left and M-NG-RAN node on the right. A horizontal arrow labeled 'CELL TRAFFIC TRACE' points from the S-NG-RAN node to the M-NG-RAN node. Both nodes are represented by a box above a thick horizontal line representing the timeline.
+
+**Figure 8.3.16.2-1: Cell Traffic Trace procedure, successful operation**
+
+The procedure is initiated with a CELL TRAFFIC TRACE message sent from the S-NG-RAN node to the M-NG-RAN node.
+
+If the *Privacy Indicator* IE is included in the message, the M-NG-RAN node shall take the information into account for anonymisation of MDT data as specified in TS 32.422 [23].
+
+## 8.3.17 SCG Failure Information Report
+
+### 8.3.17.1 General
+
+The purpose of the SCG Failure Information Report procedure is to provide SCG mobility related information to the S-NG-RAN node.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.17.2 Successful Operation
+
+
+
+Sequence diagram for SCG Failure Information Report, successful operation. It shows two nodes: M-NG-RAN node on the left and S-NG-RAN node on the right. A horizontal arrow labeled 'SCG FAILURE INFORMATION REPORT' points from the M-NG-RAN node to the S-NG-RAN node. Both nodes are represented by a box above a thick horizontal line representing the timeline.
+
+**Figure 8.3.17.2-1: SCG Failure Information Report, successful operation**
+
+The M-NG-RAN node initiates the procedure by sending the SCG FAILURE INFORMATION REPORT message to the S-NG-RAN node. Upon receiving the message, the S-NG-RAN node shall assume that a PSCell change failure event was detected.
+
+The SCG FAILURE INFORMATION REPORT message may include:
+
+- the *SN Mobility Information* IE, if the *SN Mobility Information* IE was sent for the PSCell change procedure from the S-NG-RAN node;
+
+- the *Source PSCell CGI* IE, if the *Source PSCell CGI* IE was sent for the PSCell change procedure from the S-NG-RAN node.
+
+If the SCG FAILURE INFORMATION REPORT message includes the *Source PSCell CGI* IE, the S-NG-RAN node shall, if supported, store the information.
+
+If the SCG FAILURE INFORMATION REPORT message includes the *Failed PSCell CGI* IE, the S-NG-RAN node shall, if supported, store the information and act as specified in TS 38.300 [9].
+
+If received, the S-NG-RAN node uses the above information for SCG failure reason detection and optimisation.
+
+### 8.3.17.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.17.4 Abnormal Conditions
+
+Void.
+
+## 8.3.18 SCG Failure Transfer
+
+### 8.3.18.1 General
+
+The purpose of the SCG Failure Transfer procedure is to indicate to the M-NG-RAN node that the root cause of the SCG failure may have occurred in the other nodes.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.18.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant S-NG-RAN node
+ participant M-NG-RAN node
+ Note left of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: SCG FAILURE TRANSFER
+ Note right of M-NG-RAN node:
+ Note left of S-NG-RAN node:
+ Note right of M-NG-RAN node:
+```
+
+Sequence diagram showing the SCG Failure Information Transfer procedure. An S-NG-RAN node sends an SCG FAILURE TRANSFER message to an M-NG-RAN node.
+
+**Figure 8.3.18.2-1: SCG Failure Information Transfer, successful operation**
+
+S-NG-RAN node initiates the procedure by sending the SCG FAILURE TRANSFER message to M-NG-RAN node.
+
+If received, M-NG-RAN node uses the information according to TS 38.300 [9].
+
+### 8.3.18.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.18.4 Abnormal Conditions
+
+Void.
+
+## 8.3.19 Conditional PSCell Change Cancel
+
+### 8.3.19.1 General
+
+This procedure is used by the M-NG-RAN node to inform the source S-NG-RAN node that all the prepared PSCells are cancelled in the target S-NG-RAN node during a Conditional PSCell Change.
+
+The procedure uses UE-associated signalling.
+
+### 8.3.19.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ Note right of S-NG-RAN node:
+ M-NG-RAN node->>S-NG-RAN node: CONDITIONAL PSCELL CHANGE CANCEL
+```
+
+The diagram shows a sequence of two vertical lifelines. The left lifeline is labeled 'M-NG-RAN node' and the right is labeled 'S-NG-RAN node'. Both lifelines have a thick horizontal bar at the bottom. A horizontal arrow points from the M-NG-RAN node to the S-NG-RAN node, with the text 'CONDITIONAL PSCELL CHANGE CANCEL' centered above it.
+
+Sequence diagram for Conditional PSCell Change Cancel, successful operation
+
+**Figure 8.3.19.2-1: Conditional PSCell Change Cancel, successful operation**
+
+The M-NG-RAN node initiates the procedure by sending the CONDITIONAL PSCELL CHANGE CANCEL message to the S-NG-RAN node including the *Target S-NG-RAN node ID IE*.
+
+### 8.3.19.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.3.19.4 Abnormal Conditions
+
+Void.
+
+## 8.3.20 RACH Indication
+
+### 8.3.20.1 General
+
+This message is sent by the S-NG-RAN node to the M-NG-RAN node to inform of one or more performed random access procedures at the S-NG-RAN, due to which one or more RA reports are available at the UE.
+
+### 8.3.20.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant M-NG-RAN node
+ participant S-NG-RAN node
+ Note left of M-NG-RAN node:
+ Note right of S-NG-RAN node:
+ S-NG-RAN node->>M-NG-RAN node: RACH INDICATION
+```
+
+The diagram shows a sequence of two vertical lifelines. The left lifeline is labeled 'M-NG-RAN node' and the right is labeled 'S-NG-RAN node'. Both lifelines have a thick horizontal bar at the bottom. A horizontal arrow points from the S-NG-RAN node to the M-NG-RAN node, with the text 'RACH INDICATION' centered above it.
+
+Sequence diagram for RACH Indication procedure, successful operation
+
+**Figure 8.3.20.2-1: RACH Indication procedure, successful operation.**
+
+The S-NG-RAN node initiates the procedure by sending the RACH INDICATION message to M-NG-RAN node.
+
+The RACH INDICATION message contains information concerning one or more performed random access procedures and existence of one or more RA report at the UE.
+
+Upon reception of the RACH INDICATION message the M-NG-RAN node may fetch the RA report from the UE.
+
+### 8.3.20.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.4 Global procedures
+
+### 8.4.1 Xn Setup
+
+#### 8.4.1.1 General
+
+The purpose of the Xn Setup procedure is to exchange application level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface.
+
+NOTE 1: If Xn-C signalling transport is shared among multiple Xn-C interface instances, one Xn Setup procedure is issued per Xn-C interface instance to be setup, i.e. several Xn Setup procedures may be issued via the same TNL association after that TNL association has become operational.
+
+NOTE 2: Exchange of application level configuration data also applies between two NG-RAN nodes in case the SN (i.e. the gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [8]. How to use this information when this option is used is not explicitly specified.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.1.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: XN SETUP REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: XN SETUP RESPONSE
+ Note left of NG-RAN node1:
+```
+
+The diagram illustrates the successful operation of the Xn Setup procedure. It features two vertical lifelines representing 'NG-RAN node<sub>1</sub>' and 'NG-RAN node<sub>2</sub>'. A solid horizontal arrow labeled 'XN SETUP REQUEST' points from node<sub>1</sub> to node<sub>2</sub>. A return arrow labeled 'XN SETUP RESPONSE' points from node<sub>2</sub> back to node<sub>1</sub>. Both lifelines terminate in a thick horizontal bar at the bottom, indicating the end of the sequence.
+
+Sequence diagram showing the successful operation of Xn Setup between two NG-RAN nodes.
+
+**Figure 8.4.1.2: Xn Setup, successful operation**
+
+The NG-RAN node<sub>1</sub> initiates the procedure by sending the XN SETUP REQUEST message to the candidate NG-RAN node<sub>2</sub>. The candidate NG-RAN node<sub>2</sub> replies with the XN SETUP RESPONSE message.
+
+The *AMF Region Information* IE in the XN SETUP REQUEST message shall contain a complete list of Global AMF Region IDs to which the NG-RAN node<sub>1</sub> belongs. The *AMF Region Information* IE in the XN SETUP RESPONSE message shall contain a complete list of Global AMF Region IDs to which the NG-RAN node<sub>2</sub> belongs.
+
+The *List of Served Cells NR* IE and the *List of Served Cells E-UTRA* IE, if contained in the XN SETUP REQUEST message, shall contain a complete list of cells served by NG-RAN node<sub>1</sub> or, if supported, a partial list of served cells together with the *Partial List Indicator* IE. The *List of Served Cells NR* IE and the *List of Served Cells E-UTRA* IE, if
+
+contained in the XN SETUP RESPONSE message, shall contain a complete list of cells served by NG-RAN node<sub>2</sub> or, if supported, a partial list of served cells together with the *Partial List Indicator* IE.
+
+If Supplementary Uplink is configured at the NG-RAN node<sub>1</sub>, the NG-RAN node<sub>1</sub> shall include in the XN SETUP REQUEST message the *SUL Information* IE and the *Supported SUL band List* IE for each served cell where supplementary uplink is configured.
+
+If Supplementary Uplink is configured at the NG-RAN node<sub>2</sub>, the candidate NG-RAN node<sub>2</sub> shall include in the XN SETUP RESPONSE message the *SUL Information* IE and the *Supported SUL band List* IE for each served cell where supplementary uplink is configured.
+
+If the NG-RAN node<sub>1</sub> is an ng-eNB, it may include the *Protected E-UTRA Resource Indication* IE into the XN SETUP REQUEST. If the XN SETUP REQUEST sent by an ng-eNB contains the *Protected E-UTRA Resource Indication* IE, the receiving gNB should take this into account for cell-level resource coordination with the ng-eNB. The gNB shall consider the received *Protected E-UTRA Resource Indication* IE content valid until reception of a new update of the IE for the same ng-eNB.
+
+The protected resource pattern indicated in the *Protected E-UTRA Resource Indication* IE is not valid in subframes indicated by the *Reserved Subframes* IE, as well as in the non-control region of the MBSFN subframes i.e. it is valid only in the control region therein. The size of the control region of MBSFN subframes is indicated in the *Protected E-UTRA Resource Indication* IE.
+
+In case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the XN SETUP REQUEST message and the XN SETUP RESPONSE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+If the *Intended TDD DL-UL Configuration NR* IE is included in the XN SETUP REQUEST or XN SETUP RESPONSE message, the receiving NG-RAN node should take this information into account for cross-link interference management and/or NR-DC power coordination with the sending NG-RAN node. The receiving NG-RAN node shall consider the received *Intended TDD DL-UL Configuration NR* IE content valid until reception of an update of the IE for the same cell(s).
+
+If the *TNL Configuration Info* IE is contained in the XN SETUP REQUEST message, the NG-RAN node<sub>2</sub> shall, if supported, take this IE into account for IPSec establishment.
+
+If the *TNL Configuration Info* IE is contained in the XN SETUP RESPONSE message, the NG-RAN node<sub>1</sub> shall, if supported, take this IE into account for IPSec establishment.
+
+If the *Partial List Indicator NR* IE or the *Partial List Indicator E-UTRA* IE is set to "partial" in the XN SETUP REQUEST message the candidate NG-RAN node<sub>2</sub> shall, if supported, assume that the *List of Served Cells NR* IE or the *List of Served Cells E-UTRA* IE in the XN SETUP REQUEST message includes a partial list of cells.
+
+If the *Partial List Indicator NR* IE or the *Partial List Indicator E-UTRA* IE is set to "partial" in the XN SETUP RESPONSE message from the candidate NG-RAN node<sub>2</sub>, the NG-RAN node<sub>1</sub> shall, if supported, assume that the *List of Served Cells NR* IE or the *List of Served Cells E-UTRA* IE in the XN SETUP RESPONSE message includes a partial list of cells.
+
+If the *Cell and Capacity Assistance Information NR* IE or the *Cell and Capacity Assistance Information E-UTRA* IE is present in the XN SETUP REQUEST message the candidate NG-RAN node<sub>2</sub> shall, if supported, use it when generating the list of NG-RAN served cell information to include in the XN SETUP RESPONSE message.
+
+If the *Cell and Capacity Assistance Information NR* IE or the *Cell and Capacity Assistance Information E-UTRA* IE is present in the XN SETUP RESPONSE message from the candidate NG-RAN node<sub>2</sub>, the NG-RAN node<sub>1</sub> shall, if supported, store the collected information to be used for future NG-RAN node interface management.
+
+If the *CSI-RS Transmission Indication* IE is contained in the XN SETUP REQUEST message, the NG-RAN node<sub>2</sub> shall, if supported, take this IE into account for neighbour cell's CSI-RS measurement.
+
+If the *CSI-RS Transmission Indication* IE is contained in the XN SETUP RESPONSE message, the NG-RAN node<sub>1</sub> shall, if supported, take this IE into account for neighbour cell's CSI-RS measurement.
+
+The initiating NG-RAN node<sub>1</sub> may include the *PRACH Configuration* IE (for served E-UTRA cells) or the *NR Cell PRACH Configuration* IE (for served NR cells) or the *NPRACH Configuration* IE (for served NB-IoT cells) in the XN SETUP REQUEST message. The candidate NG-RAN node<sub>2</sub> may also include the *PRACH Configuration* IE (for served E-UTRA cells) or *NR Cell PRACH Configuration* IE (for served NR cells) or the *NPRACH Configuration* IE (for served NB-IoT cells) in the XN SETUP RESPONSE message. The NG-RAN node receiving the IE may use this information for RACH optimisation.
+
+The XN SETUP REQUEST message may contain for each cell served by NG-RAN node<sub>1</sub> NPN related broadcast information. The XN SETUP RESPONSE message may contain for each cell served by NG-RAN node<sub>2</sub> NPN related broadcast information.
+
+If the *SFN Offset* IE is included in the XN SETUP REQUEST or XN SETUP RESPONSE message, the receiving NG-RAN node shall, if supported, use this information to deduce the SFN0 time offset of the reported cell. The receiving NG-RAN node shall consider the received *SFN Offset* IE content valid until reception of an update of the IE for the same cell(s).
+
+The NG-RAN node receiving the *Supported MBS FSA ID List* IE in the XN SETUP REQUEST message or the in XN SETUP RESPONSE message may use it according to TS 38.300 [9].
+
+If the *Additional Measurement Timing Configuration List* IE is contained in the XN SETUP REQUEST message, the NG-RAN node<sub>2</sub> shall, if supported, take this IE into account for neighbour cell's CSI-RS measurement.
+
+If the *Additional Measurement Timing Configuration List* IE is contained in the XN SETUP RESPONSE message, the NG-RAN node<sub>1</sub> shall, if supported, take this IE into account for neighbour cell's CSI-RS measurement.
+
+If the *Local NG-RAN Node Identifier* IE is present in the XN SETUP REQUEST message, the NG-RAN node<sub>2</sub> shall, if supported, take this into account for future retrieval of the UE contexts from the NG-RAN node<sub>1</sub>.
+
+If the *Local NG-RAN Node Identifier* IE is present in the XN SETUP RESPONSE message, the NG-RAN node<sub>1</sub> shall, if supported, take this into account for future retrieval of the UE contexts from the NG-RAN node<sub>2</sub>.
+
+If the *Neighbour NG-RAN Node List* IE is present in the XN SETUP REQUEST message, the NG-RAN node<sub>2</sub> may take this into account for Local NG-RAN Node Identifier conflict detection.
+
+If the *Neighbour NG-RAN Node List* IE is present in the XN SETUP RESPONSE message, the NG-RAN node<sub>1</sub> may take this into account for Local NG-RAN Node Identifier conflict detection.
+
+If the *Served Cell Specific Info Request* IE is included in the XN SETUP REQUEST message and if the NG-RAN node<sub>2</sub> is a gNB, the NG-RAN node<sub>2</sub> shall, if supported, include the *Additional Measurement Timing Configuration List* IE for the requested NR cells in the XN SETUP RESPONSE message.
+
+If the *RedCap Broadcast Information* IE is included in the *Served Cell Information NR* IE in the XN SETUP REQUEST message or the XN SETUP RESPONSE message, the receiving NG-RAN node may use this information to determine a suitable target in case of subsequent outgoing mobility involving RedCap UEs.
+
+If the *TAI NSAG Support List* IE is contained in the XN SETUP REQUEST or in the XN SETUP RESPONSE message, the receiving NG-RAN node shall, if supported, take this IE into account for slice aware cell reselection.
+
+If the *TAI Slice Unavailable Cell List* IE is contained in the XN SETUP REQUEST or in the XN SETUP RESPONSE message, the receiving NG-RAN node shall, if supported, take this IE into account to deduce slice resource allocation.
+
+If the *eRedCap Broadcast Information* IE is included in the *Served Cell Information NR* IE in the XN SETUP REQUEST message or the XN SETUP RESPONSE message, the receiving NG-RAN node may use this information to determine a suitable target in case of subsequent outgoing mobility involving eRedCap UEs.
+
+If the *Mobile IAB Cell IE* is included in the *Served Cell Information NR IE* in the XN SETUP REQUEST message or in the XN SETUP RESPONSE message, the receiving NG-RAN node may use it accordingly.
+
+#### Interactions with other procedures:
+
+If the NG-RAN node<sub>1</sub> receives a XN SETUP RESPONSE message containing a Local NG-RAN Node Identifier identical to the Local NG-RAN Node Identifier included in the corresponding XN SETUP REQUEST message, the NG-RAN node<sub>1</sub> may initiate the NG-RAN node Configuration Update procedure including in the NG-RAN NODE CONFIGURATION UPDATE message a new Local NG-RAN Node Identifier, different from the Local NG-RAN Node Identifier of each of its neighbour NG-RAN Nodes.
+
+If the NG-RAN node<sub>1</sub> receives a XN SETUP RESPONSE message containing a Local NG-RAN Node Identifier within the *Neighbour NG-RAN Node List IE* identical to the Local NG-RAN Node Identifier included in the corresponding XN SETUP REQUEST message, the NG-RAN node<sub>1</sub> may initiate the NG-RAN node Configuration Update procedure including in the NG-RAN NODE CONFIGURATION UPDATE message a new Local NG-RAN Node Identifier, different from the Local NG-RAN Node Identifier of each of its neighbour NG-RAN Nodes.
+
+#### 8.4.1.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: XN SETUP REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: XN SETUP FAILURE
+ Note left of NG-RAN node1:
+
+```
+
+Sequence diagram showing an unsuccessful Xn Setup operation between NG-RAN node1 and NG-RAN node2. NG-RAN node1 sends an XN SETUP REQUEST to NG-RAN node2, and NG-RAN node2 responds with an XN SETUP FAILURE.
+
+Figure 8.4.1.3-1: Xn Setup, unsuccessful operation
+
+If the candidate NG-RAN node<sub>2</sub> cannot accept the setup it shall respond with the XN SETUP FAILURE message with appropriate cause value.
+
+If the XN SETUP FAILURE message includes the *Time To Wait IE*, the initiating NG-RAN node<sub>1</sub> shall wait at least for the indicated time before reinitiating the Xn Setup procedure towards the same NG-RAN node<sub>2</sub>.
+
+If case of network sharing with multiple Cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the XN SETUP REQUEST message and the XN SETUP FAILURE message shall include the *Interface Instance Indication IE* to identify the corresponding interface instance.
+
+If the *Message Oversize Notification IE* is included in the XN SETUP FAILURE, the initiating node shall, if supported, deduce that the failure is due to a too large XN SETUP REQUEST message and ensure that the total number of served cells in following XN SETUP REQUEST message is equal to or lower than the value of the *Maximum Cell List Size IE*.
+
+#### 8.4.1.4 Abnormal Conditions
+
+If the first message received for a specific TNL association is not an XN SETUP REQUEST, XN SETUP RESPONSE, or XN SETUP FAILURE message then this shall be treated as a logical error.
+
+If the initiating NG-RAN node<sub>1</sub> does not receive either XN SETUP RESPONSE message or XN SETUP FAILURE message, the NG-RAN node<sub>1</sub> may reinitiate the Xn Setup procedure towards the same NG-RAN node, provided that the content of the new XN SETUP REQUEST message is identical to the content of the previously unacknowledged XN SETUP REQUEST message.
+
+If the initiating NG-RAN node<sub>1</sub> receives an XN SETUP REQUEST message from the peer entity on the same Xn interface:
+
+- In case the NG-RAN node<sub>1</sub> answers with an XN SETUP RESPONSE message and receives a subsequent XN SETUP FAILURE message, the NG-RAN node<sub>1</sub> shall consider the Xn interface as non operational and the procedure as unsuccessfully terminated according to sub clause 8.4.1.3.
+- In case the NG-RAN node<sub>1</sub> answers with an XN SETUP FAILURE message and receives a subsequent XN SETUP RESPONSE message, the NG-RAN node<sub>1</sub> shall ignore the XN SETUP RESPONSE message and consider the Xn interface as non operational.
+
+## 8.4.2 NG-RAN node Configuration Update
+
+### 8.4.2.1 General
+
+The purpose of the NG-RAN node Configuration Update procedure is to update application level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface.
+
+NOTE: Update of application level configuration data also applies between two NG-RAN nodes in case the SN (i.e. the gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [8]. How to use this information when this option is used is not explicitly specified.
+
+The procedure uses non UE-associated signalling.
+
+### 8.4.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: NG-RAN NODE CONFIGURATION UPDATE
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE
+ Note left of NG-RAN node1:
+
+```
+
+The diagram illustrates the message exchange for a successful NG-RAN node Configuration Update. It starts with NG-RAN node<sub>1</sub> sending an 'NG-RAN NODE CONFIGURATION UPDATE' message to NG-RAN node<sub>2</sub>. NG-RAN node<sub>2</sub> then responds with an 'NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE' message back to NG-RAN node<sub>1</sub>. Both nodes are represented by rectangular boxes with a vertical line extending downwards, and a horizontal bar at the bottom of each line indicates the end of the sequence.
+
+Sequence diagram showing the successful operation of the NG-RAN node Configuration Update procedure between NG-RAN node1 and NG-RAN node2.
+
+**Figure 8.4.2.2-1: NG-RAN node Configuration Update, successful operation**
+
+The NG-RAN node<sub>1</sub> initiates the procedure by sending the NG-RAN NODE CONFIGURATION UPDATE message to a peer NG-RAN node<sub>2</sub>.
+
+If Supplementary Uplink is configured at the NG-RAN node<sub>1</sub>, the NG-RAN node<sub>1</sub> shall include in the NG-RAN NODE CONFIGURATION UPDATE message the *SUL Information* IE and the *Supported SUL band List* IE for each cell added in the *Served NR Cells To Add* IE and in the *Served NR Cells To Modify* IE.
+
+If Supplementary Uplink is configured at the NG-RAN node<sub>2</sub>, the NG-RAN node<sub>2</sub> shall include in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message the *SUL Information* IE and the *Supported SUL band List* IE for each cell added in the *Served NR Cells* IE if any.
+
+If the *TAI Support List* IE is included in the NG-RAN NODE CONFIGURATION UPDATE message, the receiving node shall replace the previously provided *TAI Support List* IE by the received *TAI Support List* IE.
+
+If the *Cell Assistance Information NR* IE is present, the NG-RAN node<sub>2</sub> shall, if supported, use it to generate the *Served NR Cells* IE and include the list in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.
+
+If the *Cell Assistance Information E-UTRA* IE is present, the NG-RAN node<sub>2</sub> shall, if supported, use it to generate the *Served E-UTRA Cells* IE and include the list in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.
+
+If the *Partial List Indicator NR* IE is included in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message and set to "partial" the NG-RAN node<sub>1</sub> shall, if supported, assume that the *Served NR Cells* IE in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message includes a partial list of NR cells.
+
+If the *Partial List Indicator E-UTRA* IE is included in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message and set to "partial" the NG-RAN node<sub>1</sub> shall, if supported, assume that the *Served E-UTRA Cells* IE in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message includes a partial list of NR cells.
+
+If the *Cell and Capacity Assistance Information NR* IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message from the candidate NG-RAN node<sub>2</sub>, the NG-RAN node<sub>1</sub> shall, if supported, store the collected information to be used for future NG-RAN node interface management.
+
+If the *Cell and Capacity Assistance Information E-UTRA* IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message from the candidate NG-RAN node<sub>2</sub>, the NG-RAN node<sub>1</sub> shall, if supported, store the collected information to be used for future NG-RAN node interface management.
+
+Upon reception of the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall update the information for NG-RAN node<sub>1</sub> as follows:
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the NG-RAN NODE CONFIGURATION UPDATE message and the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+If the *TNL Configuration Info* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall take this IE into account for IPSec establishment.
+
+If the *TNL Configuration Info* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the NG-RAN node<sub>1</sub> shall take this IE into account for IPSec establishment.
+
+If the *CSI-RS Transmission Indication* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall take this IE into account for neighbour cell's CSI-RS measurement.
+
+The NG-RAN NODE CONFIGURATION UPDATE message may contain for each cell served by NG-RAN node<sub>1</sub> NPN related broadcast information. The NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message may contain for each cell served by NG-RAN node<sub>2</sub> NPN related broadcast information.
+
+If the *Additional Measurement Timing Configuration List* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall take this IE into account for neighbour cell's CSI-RS measurement.
+
+If the *Local NG-RAN Node Identifier* IE is present in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall, if supported, take this into account for future retrieval of the UE contexts from the NG-RAN node<sub>1</sub>.
+
+If the *Local NG-RAN Node Identifier* IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the NG-RAN node<sub>1</sub> shall, if supported, take this into account for future retrieval of the UE contexts from the NG-RAN node<sub>2</sub>.
+
+If the *Neighbour NG-RAN Node List* IE is present in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> may take this into account for Local NG-RAN Node Identifier conflict detection.
+
+If the *Neighbour NG-RAN Node List* IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the NG-RAN node<sub>1</sub> may take this into account for Local NG-RAN Node Identifier conflict detection.
+
+If the *Local NG-RAN Node Identifier Removal* IE is present in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall, if supported, discard it from its context and not use it for future retrieval of the UE contexts from the NG-RAN node<sub>1</sub>.
+
+If the *Local NG-RAN Node Identifier Removal* IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the NG-RAN node<sub>1</sub> shall, if supported, discard it from its context and not use it for future retrieval of the UE contexts from the NG-RAN node<sub>2</sub>.
+
+If the *Served Cell Specific Info Request* IE is included in the NG-RAN NODE CONFIGURATION UPDATE message and if the NG-RAN node<sub>2</sub> is a gNB, the NG-RAN node<sub>2</sub> shall, if supported, include the *Additional Measurement Timing Configuration List* IE for the requested NR cells in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.
+
+If the *TAI NSAG Support List* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node shall, if supported, take this IE into account for slice aware cell reselection.
+
+If the *TAI Slice Unavailable Cell List* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall, if supported, take this IE into account to deduce slice resource allocation.
+
+#### Update of Served Cell Information NR:
+
+- If *Served Cells NR To Add* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall add cell information according to the information in the *Served Cell Information NR* IE.
+- If *Served Cells NR To Modify* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall modify information of cell indicated by *Old NR-CGI* IE according to the information in the *Served Cell Information NR* IE.
+- When either served cell information or neighbour information of an existing served cell in NG-RAN node<sub>1</sub> need to be updated, the whole list of neighbouring cells, if any, shall be contained in the *Neighbour Information NR* IE. The NG-RAN node<sub>2</sub> shall overwrite the served cell information and the whole list of neighbour cell information for the affected served cell.
+- If the *Deactivation Indication* IE is contained in the *Served Cells NR To Modify* IE, it indicates that the concerned cell was switched off to lower energy consumption.
+- If *Served Cells NR To Delete* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall delete information of cell indicated by *Old NR-CGI* IE.
+- If the *Intended TDD DL-UL Configuration NR* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> should take this information into account for cross-link interference management and/or NR-DC power coordination with the NG-RAN node<sub>1</sub>. The NG-RAN node<sub>2</sub> shall consider the received *Intended TDD DL-UL Configuration NR* IE content valid until reception of a new update of the IE for the same NG-RAN node<sub>2</sub>.
+- If the *NR Cell PRACH Configuration* IE is contained in the *Served Cell Information NR* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE may use this information for RACH optimisation.
+- If the *SFN Offset* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE shall, if supported, use this information to update the SFN0 time offset of the reported cell.
+- If the *Supported MBS FSA ID List* IE is contained in the *Served Cell Information NR* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE may use it according to TS 38.300 [9].
+
+- If the *RedCap Broadcast Information* IE is contained in the *Served Cell Information NR* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> may use this information to determine a suitable target in case of subsequent outgoing mobility involving RedCap UEs.
+- If the *eRedCap Broadcast Information* IE is contained in the *Served Cell Information NR* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> may use this information to determine a suitable target in case of subsequent outgoing mobility involving eRedCap UEs.
+- If the *Mobile IAB Cell* IE is included in the *Served Cell Information NR* IE in the NG-RAN NODE CONFIGURATION UPDATE message or the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the receiving NG-RAN node may use it accordingly.
+
+#### Update of Served Cell Information E-UTRA:
+
+- If *Served Cells E-UTRA To Add* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall add cell information according to the information in the *Served Cell Information E-UTRA* IE.
+- If *Served Cells E-UTRA To Modify* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall modify information of cell indicated by *Old ECGI* IE according to the information in the *Served Cell Information E-UTRA* IE.
+- When either served cell information or neighbour information of an existing served cell in NG-RAN node<sub>1</sub> need to be updated, the whole list of neighbouring cells, if any, shall be contained in the *Neighbour Information E-UTRA* IE. The NG-RAN node<sub>2</sub> shall overwrite the served cell information and the whole list of neighbour cell information for the affected served cell.
+- If the *Deactivation Indication* IE is contained in the *Served Cells E-UTRA To Modify* IE, it indicates that the concerned cell was switched off to lower energy consumption.
+- If the *Served Cells E-UTRA To Delete* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node<sub>2</sub> shall delete information of cell indicated by *Old ECGI* IE.
+- If the *Protected E-UTRA Resource Indication* IE is included into the NG-RAN NODE CONFIGURATION UPDATE (inside the *Served Cell Information E-UTRA* IE), the receiving gNB should take this into account for cell-level resource coordination with the ng-eNB. The gNB shall consider the received *Protected E-UTRA Resource Indication* IE content valid until reception of a new update of the IE for the same ng-eNB. The protected resource pattern indicated in the *Protected E-UTRA Resource Indication* IE is not valid in subframes indicated by the *Reserved Subframes* IE (contained in E-UTRA - NR CELL RESOURCE COORDINATION REQUEST messages), as well as in the non-control region of the MBSFN subframes i.e. it is valid only in the control region therein. The size of the control region of MBSFN subframes is indicated in the *Protected E-UTRA Resource Indication* IE.
+- If the *PRACH Configuration* IE is contained in the *Served Cell Information E-UTRA* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE may use this information for RACH optimisation.
+- If the *NPRACH Configuration* IE is contained in the *Served Cell Information E-UTRA* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE may use this information for RACH optimisation.
+- If the *SFN Offset* IE is contained in *Served Cell Information E-UTRA* IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE shall, if supported, use this information to update the SFN0 time offset of the reported cell.
+
+#### Update of TNL addresses for SCTP associations:
+
+If the *TNLA To Add List* IE is included in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall, if supported, use it to establish the TNL association(s) with the NG-RAN node<sub>1</sub>. If the *TNLA To Add List* IE does not include the *Port Number* IE, the NG-RAN node<sub>2</sub> shall assume that port number value 38422 is used for the endpoint. The NG-RAN node<sub>2</sub> shall report to the NG-RAN node<sub>1</sub>, in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the NG-RAN node<sub>1</sub> as follows:
+
+- A list of successfully established TNL associations shall be included in the *TNLA Setup List* IE;
+- A list of TNL associations that failed to be established shall be included in the *TNLA Failed to Setup List* IE.
+
+If the *TNLA To Remove List* IE is included in the NG-RAN NODE CONFIGURATION UPDATE message the NG-RAN node<sub>2</sub> shall, if supported, initiate removal of the TNL association(s) indicated by the received Transport Layer information towards the NG-RAN node<sub>1</sub>.
+
+- If the received *TNLA Transport Layer Address* IE includes the *Port Number* IE, the NG-RAN node<sub>1</sub> TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the NG-RAN node<sub>1</sub> TNL endpoints correspond to all NG-RAN node<sub>1</sub> TNL endpoints identified by the *Endpoint IP Address* IE and any Port Number(s).
+
+If the *TNLA To Update List* IE is included in the NG-RAN NODE CONFIGURATION UPDATE message the NG-RAN node<sub>2</sub> shall, if supported, update the TNL association(s) indicated by the received Transport Layer information towards the NG-RAN node<sub>1</sub>.
+
+- If the received *TNLA Transport Layer Address* IE includes the *Port Number* IE, the NG-RAN node<sub>1</sub> TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the NG-RAN node<sub>1</sub> TNL endpoints correspond to all NG-RAN node<sub>1</sub> TNL endpoints identified by the *Endpoint IP Address* IE and any Port Number(s).
+
+#### **Update of AMF Region Information:**
+
+- If *AMF Region Information To Add* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall add the AMF Regions to its AMF Region List.
+- If *AMF Region Information To Delete* IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> shall remove the AMF Regions from its AMF Region List.
+
+#### **Update of Cell Coverage:**
+
+If the *Coverage Modification List* IE is present in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> may use the information in the *Cell Coverage State* IE to identify the cell deployment configuration enabled by the NG-RAN node<sub>1</sub> and for configuring the mobility towards the cell(s) indicated by the *Global NG-RAN Cell Identity* IE, as described in TS 38.300 [9].
+
+- If the *Cell Deployment Status Indicator* IE is present in the *Coverage Modification List* IE, the NG-RAN node<sub>2</sub> shall consider the cell deployment configuration of the cell to be modified as the next planned configuration and shall remove any planned configuration stored for this cell.
+- If the *Cell Deployment Status Indicator* IE is present and the *Cell Replacing Info* IE contains non-empty cell list, the NG-RAN node<sub>2</sub> may use this list to avoid connection or re-establishment failures during the reconfiguration, e.g. consider the cells in the list as possible alternative handover targets.
+- If the *Cell Deployment Status Indicator* IE is not present, the NG-RAN node<sub>2</sub> shall consider the cell deployment configuration of cell to be modified as activated and replace any previous configuration for the cells indicated in the *Coverage Modification List* IE.
+
+If the *SSB Coverage Modification List* IE is present in the *Coverage Modification List* IE, the NG-RAN node<sub>2</sub> may use the information in the *SSB Coverage State* IE to identify the SSB beam deployment configuration enabled by the NG-
+
+RAN node<sub>1</sub> and for configuring the mobility towards the beam(s) indicated by the *SSB Index* IE, as described in TS 38.300 [9].
+
+If the *Coverage Modification Cause* IE set to "coverage" or "cell edge capacity" is present in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> may use the information for deducing the CCO issue detected at NG-RAN node<sub>1</sub> and for configuring coverage state of its served cell(s).
+
+If the *Coverage Modification Cause* IE set to "network energy saving" is present and the *SSB Coverage State* IE is zero for a set of SSB beams in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>2</sub> may use the information to decide the SSB beam activation for the concerned beams when necessary.
+
+#### Interactions with other procedures:
+
+If the NG-RAN node<sub>1</sub> receives a NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message containing a Local NG-RAN Node Identifier identical to the Local NG-RAN Node Identifier included in the corresponding NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>1</sub> may initiate the NG-RAN node Configuration Update procedure including in the NG-RAN NODE CONFIGURATION UPDATE message a new Local NG-RAN Node Identifier, different from the Local NG-RAN Node Identifier of each of its neighbour NG-RAN Nodes.
+
+If the NG-RAN node<sub>1</sub> receives a NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message containing a Local NG-RAN Node Identifier within the *Neighbour NG-RAN Node List* IE identical to the Local NG-RAN Node Identifier included in the corresponding NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node<sub>1</sub> may initiate the NG-RAN node Configuration Update procedure including in the NG-RAN NODE CONFIGURATION UPDATE message a new Local NG-RAN Node Identifier, different from the Local NG-RAN Node Identifier of each of its neighbour NG-RAN Nodes.
+
+### 8.4.2.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: NG-RAN NODE CONFIGURATION UPDATE
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: NG-RAN NODE CONFIGURATION UPDATE FAILURE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+The diagram illustrates a sequence of messages between two NG-RAN nodes, node<sub>1</sub> and node<sub>2</sub>. Node<sub>1</sub> sends a 'NG-RAN NODE CONFIGURATION UPDATE' message to node<sub>2</sub>. Node<sub>2</sub> responds with a 'NG-RAN NODE CONFIGURATION UPDATE FAILURE' message. Both nodes are represented by rectangular boxes with a horizontal line at the bottom, indicating their lifelines. The messages are shown as arrows between the lifelines.
+
+Sequence diagram showing an unsuccessful NG-RAN node Configuration Update operation between NG-RAN node 1 and NG-RAN node 2.
+
+**Figure 8.4.2.3-1: NG-RAN node Configuration Update, unsuccessful operation**
+
+If the NG-RAN node<sub>2</sub> cannot accept the update it shall respond with the NG-RAN NODE CONFIGURATION UPDATE FAILURE message and appropriate cause value.
+
+If the NG-RAN NODE CONFIGURATION UPDATE FAILURE message includes the *Time To Wait* IE, the NG-RAN node<sub>1</sub> shall wait at least for the indicated time before reinitiating the NG-RAN Node Configuration Update procedure towards the same NG-RAN node<sub>2</sub>. Both nodes shall continue to operate the Xn with their existing configuration data.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the NG-RAN NODE CONFIGURATION UPDATE message and the NG-RAN NODE CONFIGURATION UPDATE FAILURE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+#### 8.4.2.4 Abnormal Conditions
+
+If the NG-RAN node<sub>1</sub> after initiating NG-RAN node Configuration Update procedure receives neither NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message nor NG-RAN NODE CONFIGURATION UPDATE FAILURE message, the NG-RAN node<sub>1</sub> may reinitiate the NG-RAN node Configuration Update procedure towards the same NG-RAN node<sub>2</sub>, provided that the content of the new NG-RAN NODE CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged NG-RAN NODE CONFIGURATION UPDATE message.
+
+### 8.4.3 Cell Activation
+
+#### 8.4.3.1 General
+
+The purpose of the Cell Activation procedure is to enable an NG-RAN node to request a neighbouring NG-RAN node to switch on all the SSB beams or only some of the SSB beams within one or more cells, previously reported as inactive due to energy saving.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.3.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: CELL ACTIVATION REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: CELL ACTIVATION RESPONSE
+ Note left of NG-RAN node1:
+
+```
+
+Sequence diagram showing the successful operation of Cell Activation. NG-RAN node1 sends a CELL ACTIVATION REQUEST to NG-RAN node2, and NG-RAN node2 responds with a CELL ACTIVATION RESPONSE.
+
+Figure 8.4.3.2-1: Cell Activation, successful operation
+
+The NG-RAN node<sub>1</sub> initiates the procedure by sending the CELL ACTIVATION REQUEST message to the peer NG-RAN node<sub>2</sub>.
+
+If either the *NR Cells* IE or the *E-UTRA Cells* IE is included in the CELL ACTIVATION REQUEST message, the NG-RAN node<sub>2</sub> should activate the cell/s indicated in the CELL ACTIVATION REQUEST message and shall indicate in the CELL ACTIVATION RESPONSE message for which cells the request was fulfilled.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the CELL ACTIVATION REQUEST message and the CELL ACTIVATION RESPONSE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+If the *NR Cells and SSBs* IE is included in the CELL ACTIVATION REQUEST message
+
+- and for an NR cell the *SSBs to be Activated List* IE is included, the NG-RAN node<sub>2</sub> shall, if supported, activate only the SSB beams indicated by the *SSBs to be Activated List* IE. Otherwise, the NG-RAN node<sub>2</sub> shall, if supported, activate all the SSB beams in the cell.
+- and if at least one SSB beam requested in the *SSBs to be Activated List* IE is activated, the NG-RAN node<sub>2</sub> shall include the *SSBs Activated List* IE in the CELL ACTIVATION RESPONSE message. The NG-RAN node<sub>1</sub> shall consider only the SSB beams indicated by the *SSBs Activated List* IE as activated.
+
+**Interactions with NG-RAN Configuration Update procedure:**
+
+The NG-RAN node<sub>2</sub> shall not send the NG-RAN CONFIGURATION UPDATE message to the NG-RAN node<sub>1</sub> just for the reason of the cell(s) or the SSB beam(s) indicated in the CELL ACTIVATION REQUEST message changing cell or SSB beam activation state, as the receipt of the CELL ACTIVATION RESPONSE message by the NG-RAN node<sub>1</sub> is used to update the information about the activation state of NG-RAN node<sub>2</sub> cell(s) or SSB beam(s) in the NG-RAN node<sub>1</sub>.
+
+#### 8.4.3.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: CELL ACTIVATION REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: CELL ACTIVATION FAILURE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+The diagram illustrates a sequence of messages between two network nodes. On the left is 'NG-RAN node<sub>1</sub>' and on the right is 'NG-RAN node<sub>2</sub>'. A solid horizontal arrow points from node<sub>1</sub> to node<sub>2</sub> with the text 'CELL ACTIVATION REQUEST'. A return arrow points from node<sub>2</sub> back to node<sub>1</sub> with the text 'CELL ACTIVATION FAILURE'. Both nodes are represented by a rectangular box above a thick horizontal line representing the ground or base.
+
+Sequence diagram showing an unsuccessful cell activation operation between NG-RAN node1 and NG-RAN node2.
+
+**Figure 8.4.3.3-1: Cell Activation, unsuccessful operation**
+
+If the NG-RAN node<sub>2</sub> cannot activate any of the cells or any of the SSB beams indicated in the CELL ACTIVATION REQUEST message, it shall respond with the CELL ACTIVATION FAILURE message with an appropriate cause value.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the CELL ACTIVATION REQUEST message and the CELL ACTIVATION FAILURE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+#### 8.4.3.4 Abnormal Conditions
+
+Void.
+
+### 8.4.4 Reset
+
+#### 8.4.4.1 General
+
+The purpose of the Reset procedure is to align the resources in the NG-RAN node<sub>1</sub> and the NG-RAN node<sub>2</sub> in the event of an abnormal failure. The procedure either resets the Xn interface or selected UE contexts. This procedure doesn't affect the application level configuration data exchanged during, e.g., the Xn Setup procedure.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.4.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: RESET REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: RESET RESPONSE
+ Note left of NG-RAN node1:
+
+```
+
+Sequence diagram showing a successful reset operation between NG-RAN node1 and NG-RAN node2. NG-RAN node1 sends a RESET REQUEST to NG-RAN node2, and NG-RAN node2 responds with a RESET RESPONSE.
+
+**Figure 8.4.4.2-1: Reset, successful operation**
+
+The procedure is initiated with the RESET REQUEST message sent from the NG-RAN node<sub>1</sub> to the NG-RAN node<sub>2</sub>. Upon receipt of this message,
+
+- if the RESET REQUEST message indicates full reset the NG-RAN node<sub>2</sub> shall abort any other ongoing procedures over Xn between the NG-RAN node<sub>1</sub> and the NG-RAN node<sub>2</sub>. The NG-RAN node<sub>2</sub> shall delete all the context information related to the NG-RAN node<sub>1</sub>, except the application level configuration data exchanged during the Xn Setup or the NG-RAN node Configuration Update procedures and release the corresponding resources. After completion of release of the resources, the NG-RAN node<sub>2</sub> shall respond with the RESET RESPONSE message.
+- if the RESET REQUEST message indicates partial reset, the NG-RAN node<sub>2</sub> shall abort any other ongoing procedures only for the indicated UE associated signalling connections identified either by the *NG-RAN node1 UE XnAP ID IE* or the *NG-RAN node1 UE XnAP ID IE* or both, for which the NG-RAN node<sub>2</sub> shall delete all the context information related to the NG-RAN node<sub>1</sub> and release the corresponding resources. After completion of release of the resources, the NG-RAN node<sub>2</sub> shall respond with the RESET RESPONSE message indicating the UE contexts admitted to be released. The NG-RAN node<sub>2</sub> receiving the request for partial reset does not need to wait for the release or reconfiguration of radio resources to be completed before returning the RESET RESPONSE message. The NG-RAN node<sub>2</sub> receiving the request for partial reset shall include in the RESET RESPONSE message, for each UE association to be released, the same list of UE-associated logical Xn-connections over Xn. The list shall be in the same order as received in the RESET REQUEST message and shall include also unknown UE-associated logical Xn-connections.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the RESET REQUEST message and the RESET RESPONSE message shall include the *Interface Instance Indication IE* to identify the corresponding interface instance.
+
+##### Interactions with other procedures:
+
+If the RESET REQUEST message indicates full reset, the NG-RAN node<sub>2</sub> shall abort any other ongoing procedure (except for a Reset procedures).
+
+If the RESET REQUEST message indicates partial reset, the NG-RAN node<sub>2</sub> shall abort any other ongoing procedure (except for a Reset procedures) on the same Xn interface related to a UE associated signalling connection indicated in the RESET REQUEST message.
+
+#### 8.4.4.3 Unsuccessful Operation
+
+Void.
+
+#### 8.4.4.4 Abnormal Conditions
+
+If the RESET REQUEST message is received, any other ongoing procedure (except another Reset procedure) on the same Xn interface shall be aborted.
+
+If the Reset procedure is ongoing and the responding node receives the RESET REQUEST message from the peer entity on the same Xn interface, it shall respond with the RESET RESPONSE message as specified in 8.4.4.2.
+
+If the initiating node does not receive the RESET RESPONSE message, the initiating node may reinitiate the Reset procedure towards the same NG-RAN node, provided that the content of the new RESET REQUEST message is identical to the content of the previously unacknowledged RESET REQUEST message.
+
+### 8.4.5 Error Indication
+
+#### 8.4.5.1 General
+
+The Error Indication procedure is initiated by an NG-RAN node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message.
+
+If the error situation arises due to reception of a message utilising UE associated signalling, then the Error Indication procedure uses UE-associated signalling. Otherwise the procedure uses non UE-associated signalling.
+
+#### 8.4.5.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: ERROR INDICATION
+ Note right of NG-RAN node2:
+ activate NG-RAN node2
+ deactivate NG-RAN node2
+```
+
+The diagram illustrates a successful Error Indication operation. It features two vertical lifelines representing 'NG-RAN node<sub>1</sub>' and 'NG-RAN node<sub>2</sub>'. A horizontal arrow labeled 'ERROR INDICATION' points from node<sub>1</sub> to node<sub>2</sub>. Both nodes have a thick horizontal bar at the bottom of their lifelines, indicating active states.
+
+Sequence diagram showing a successful Error Indication operation between two NG-RAN nodes.
+
+**Figure 8.4.5.2-1: Error Indication, successful operation.**
+
+When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by the ERROR INDICATION message sent from the node detecting the error situation.
+
+The ERROR INDICATION message shall contain at least either the *Cause* IE or the *Criticality Diagnostics* IE.
+
+In case the Error Indication procedure is triggered by UE associated signalling, in the course of handover signalling and signalling for dual connectivity, the *Old NG-RAN node UE XnAP ID* IE and the *New NG-RAN node UE XnAP ID* IE shall be included in the ERROR INDICATION message. If any of the *Old NG-RAN node UE XnAP ID* IE and the *New NG-RAN node UE XnAP ID* IE is not correct, the cause shall be set to an appropriate value.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the ERROR INDICATION message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+#### 8.4.5.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.4.5.4 Abnormal Conditions
+
+Void.
+
+### 8.4.6 Xn Removal
+
+#### 8.4.6.1 General
+
+The purpose of the Xn Removal procedure is to remove the interface instance between two NG-RAN nodes in a controlled manner. If successful, this procedure erases any existing application level configuration data in the two nodes.
+
+NOTE: In case the signalling transport is shared among several Xn-C interface instances, and the TNL association is still used by one or more Xn-C interface instances, the initiating NG-RAN node should not initiate the removal of the TNL association.
+
+The procedure uses non UE-associated signaling.
+
+#### 8.4.6.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: XN REMOVAL REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: XN REMOVAL RESPONSE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+The diagram illustrates the successful operation of the Xn Removal procedure. It features two vertical lifelines representing 'NG-RAN node<sub>1</sub>' and 'NG-RAN node<sub>2</sub>'. A solid horizontal arrow labeled 'XN REMOVAL REQUEST' points from node<sub>1</sub> to node<sub>2</sub>. A return arrow labeled 'XN REMOVAL RESPONSE' points from node<sub>2</sub> back to node<sub>1</sub>. Both lifelines end with a thick horizontal bar at the bottom, indicating the completion of the procedure.
+
+Sequence diagram showing the successful operation of Xn Removal between two NG-RAN nodes.
+
+**Figure 8.4.6.2-1: Xn Removal, successful operation**
+
+An NG-RAN node<sub>1</sub> initiates the procedure by sending the XN REMOVAL REQUEST message to a candidate NG-RAN node<sub>2</sub>. Upon reception of the XN REMOVAL REQUEST message the candidate NG-RAN node<sub>2</sub> shall reply with the XN REMOVAL RESPONSE message. After receiving the XN REMOVAL RESPONSE message, the initiating NG-RAN node<sub>1</sub> shall initiate removal of the TNL association towards NG-RAN node<sub>2</sub> and may remove all resources associated with that interface instance. The candidate NG-RAN node<sub>2</sub> may then remove all resources associated with that interface instance.
+
+If the *Xn Removal Threshold* IE is included in the XN REMOVAL REQUEST message, the candidate NG-RAN node<sub>2</sub> shall, if supported, accept to remove the interface instance with NG-RAN node<sub>1</sub> if the Xn Benefit Value of the interface instance determined at the candidate NG-RAN node<sub>2</sub> is lower than the value of the *Xn Removal Threshold* IE.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the XN REMOVAL REQUEST message and the XN REMOVAL RESPONSE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+#### 8.4.6.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: XN REMOVAL REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: XN REMOVAL FAILURE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+Sequence diagram for Unsuccessful Operation of Xn Removal. NG-RAN node1 sends an XN REMOVAL REQUEST to NG-RAN node2, which responds with an XN REMOVAL FAILURE.
+
+**Figure 8.4.6.3-1: Xn Removal, unsuccessful operation**
+
+If the candidate NG-RAN node<sub>2</sub> cannot accept to remove the interface instance with NG-RAN node<sub>1</sub> it shall respond with an XN REMOVAL FAILURE message with an appropriate cause value.
+
+If case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the XN REMOVAL REQUEST message and the XN REMOVAL FAILURE message shall include the *Interface Instance Indication* IE to identify the corresponding interface instance.
+
+#### 8.4.6.4 Abnormal Conditions
+
+Void.
+
+### 8.4.7 Failure Indication
+
+#### 8.4.7.1 General
+
+The purpose of the Failure Indication procedure is to transfer information regarding RRC re-establishment attempts, or received RLF Reports, between NG-RAN nodes. The signalling takes place from the NG-RAN node at which a re-establishment attempt is made, or an RLF Report is received, to an NG-RAN node to which the UE concerned may have previously been attached prior to the connection failure. This may aid the detection of radio link failure, handover failure cases.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.7.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: FAILURE INDICATION
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+Sequence diagram for Successful Operation of Failure Indication. NG-RAN node2 sends a FAILURE INDICATION message to NG-RAN node1.
+
+**Figure 8.4.7.2-1: Failure Indication, successful operation**
+
+NG-RAN node<sub>2</sub> initiates the procedure by sending the FAILURE INDICATION message to NG-RAN node<sub>1</sub>, following a re-establishment attempt or an RLF Report reception from a UE at NG-RAN node<sub>2</sub>, when NG-RAN node<sub>2</sub> considers that the UE may have previously suffered a connection failure at a cell controlled by NG-RAN node<sub>1</sub>.
+
+If the *UE RLF Report Container* IE is included in the FAILURE INDICATION message, NG-RAN node<sub>1</sub> shall use it to derive failure case information.
+
+#### 8.4.7.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.4.7.4 Abnormal Conditions
+
+Void.
+
+### 8.4.8 Handover Report
+
+#### 8.4.8.1 General
+
+The purpose of the Handover Report procedure is to transfer mobility related information between NG-RAN nodes.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.8.2 Successful Operation
+
+
+
+Sequence diagram showing a successful handover report. Two vertical lines represent NG-RAN node 1 (left) and NG-RAN node 2 (right). A horizontal arrow points from node 1 to node 2. Above the nodes, a large black rectangle spans the width, with a smaller white rectangle on the right side of node 1's timeline.
+
+**Figure 8.4.8.2-1: Handover Report, successful operation**
+
+NG-RAN node<sub>1</sub> initiates the procedure by sending the HANDOVER REPORT message to NG-RAN node<sub>2</sub>. When receiving the message NG-RAN node<sub>2</sub> shall assume that a mobility-related problem was detected.
+
+If the *Handover Report Type* IE is set to "HO too early" or "HO to wrong cell", then NG-RAN node<sub>1</sub> indicates to NG-RAN node<sub>2</sub> that, following a successful handover from a cell of NG-RAN node<sub>2</sub> to a cell of NG-RAN node<sub>1</sub>, a radio link failure occurred and the UE attempted RRC Re-establishment or re-connected either at the original cell of NG-RAN node<sub>2</sub> (Handover Too Early), or at another cell (Handover to Wrong Cell). The detection of Handover Too Early and Handover to Wrong Cell events is made according to TS 38.300 [9].
+
+The HANDOVER REPORT message may include:
+
+- the *Mobility Information* IE, if the *Mobility Information* IE was sent for this handover from NG-RAN node<sub>2</sub> (in case the NG-RAN node<sub>2</sub> provided it more than once, the most recent *Mobility Information* IE is included in the HANDOVER REPORT message);
+- the *Source cell C-RNTI* IE.
+- the *CHO Configuration* IE, if the *CHO Configuration* IE was sent for this handover from NG-RAN node<sub>2</sub>.
+
+If received, NG-RAN node<sub>2</sub> uses the above information according to TS 38.300 [9].
+
+If the *Handover Report Type* IE is set to "Inter-system ping-pong", then NG-RAN node<sub>2</sub> shall deduce that a completed handover from a cell of NG-RAN node<sub>2</sub> to a cell in another system might have resulted in an inter-system ping-pong and the UE was successfully handed over to a cell of NG-RAN node<sub>1</sub> (indicated with *Target cell CGI* IE).
+
+If the *Target cell C-RNTI* IE and the *Time Since Failure* IE are received, NG-RAN node<sub>2</sub> uses the information as specified in TS 38.300 [9].
+
+#### Interaction with the Failure Indication procedure:
+
+If NG-RAN node<sub>1</sub> receives a UE RLF Report from an NG-RAN node via the FAILURE INDICATION message, as described in TS 38.300 [9], NG-RAN node<sub>1</sub> may also include it in the *UE RLF Report Container* IE included in the HANDOVER REPORT message.
+
+### 8.4.8.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.4.8.4 Abnormal Conditions
+
+Void.
+
+## 8.4.9 Mobility Settings Change
+
+### 8.4.9.1 General
+
+This procedure enables an NG-RAN node to negotiate the handover trigger settings with a peer NG-RAN node controlling neighbouring cells.
+
+The procedure uses non UE-associated signalling.
+
+### 8.4.9.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: MOBILITY CHANGE REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: MOBILITY CHANGE ACKNOWLEDGE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+The diagram illustrates a sequence of messages between two NG-RAN nodes. NG-RAN node<sub>1</sub> is on the left and NG-RAN node<sub>2</sub> is on the right. A solid horizontal arrow labeled "MOBILITY CHANGE REQUEST" points from NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub>. A dashed horizontal arrow labeled "MOBILITY CHANGE ACKNOWLEDGE" points from NG-RAN node<sub>2</sub> back to NG-RAN node<sub>1</sub>. Each node is represented by a rectangular box with a vertical line extending downwards to a thick horizontal bar at the bottom, representing the timeline of the procedure.
+
+Sequence diagram showing the successful operation of Mobility Settings Change between NG-RAN node1 and NG-RAN node2.
+
+**Figure 8.4.9.2-1: Mobility Settings Change, successful operation**
+
+NG-RAN node<sub>1</sub> initiates the procedure by sending the MOBILITY CHANGE REQUEST message to NG-RAN node<sub>2</sub>.
+
+Upon receipt, NG-RAN node<sub>2</sub> shall evaluate if the proposed NG-RAN node<sub>2</sub> handover trigger modification may be accepted. If NG-RAN node<sub>2</sub> is able to successfully complete the request it shall reply with MOBILITY CHANGE ACKNOWLEDGE message.
+
+If the *NG-RAN node1 SSB Offsets* IE is included in the MOBILITY CHANGE REQUEST, the NG-RAN node<sub>2</sub> should take into account the value of *SSB Offset* IE for UE measurements received for the SSB Area indicated by the *SSB Index* IE.
+
+If the *NG-RAN node2 Proposed SSB Offsets* IE is included in the MOBILITY CHANGE REQUEST, the NG-RAN node<sub>2</sub> shall, if supported, evaluate if the proposed value of *SSB Offset* IE may be accepted for the SSB Area indicated by
+
+the *SSB Index* IE. If NG-RAN node<sub>2</sub> is able to successfully complete the request it shall reply with MOBILITY CHANGE ACKNOWLEDGE message.
+
+#### 8.4.9.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: MOBILITY CHANGE REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: MOBILITY CHANGE FAILURE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+The diagram shows a sequence of messages between NG-RAN node<sub>1</sub> and NG-RAN node<sub>2</sub>. NG-RAN node<sub>1</sub> sends a MOBILITY CHANGE REQUEST message to NG-RAN node<sub>2</sub>. NG-RAN node<sub>2</sub> responds with a MOBILITY CHANGE FAILURE message. Both nodes are represented by rectangular boxes with a horizontal line at the bottom.
+
+Sequence diagram for Unsuccessful Operation of Mobility Settings Change
+
+Figure 8.4.9.3-1: Mobility Settings Change, unsuccessful operation
+
+If the requested parameter modification is refused by NG-RAN node<sub>2</sub>, or if NG-RAN node<sub>2</sub> is not able to complete the procedure, NG-RAN node<sub>2</sub> shall send the MOBILITY CHANGE FAILURE message with the *Cause* IE set to an appropriate value. NG-RAN node<sub>2</sub> may include the *Mobility Parameters Modification Range* IE in the MOBILITY CHANGE FAILURE message, for example in cases when the proposed change is out of the permitted range.
+
+NG-RAN node<sub>2</sub> may include the *SSB Offset Modification Range* IE in the MOBILITY CHANGE FAILURE message, for example in cases when the proposed change is out of the permitted range.
+
+#### 8.4.9.4 Abnormal Conditions
+
+Void.
+
+### 8.4.10 Resource Status Reporting Initiation
+
+#### 8.4.10.1 General
+
+This procedure is used by an NG-RAN node to request the reporting of load measurements to another NG-RAN node.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.10.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: RESOURCE STATUS REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: RESOURCE STATUS RESPONSE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+The diagram shows a sequence of messages between NG-RAN node<sub>1</sub> and NG-RAN node<sub>2</sub>. NG-RAN node<sub>1</sub> sends a RESOURCE STATUS REQUEST message to NG-RAN node<sub>2</sub>. NG-RAN node<sub>2</sub> responds with a RESOURCE STATUS RESPONSE message. Both nodes are represented by rectangular boxes with a horizontal line at the bottom.
+
+Sequence diagram for Successful Operation of Resource Status Reporting Initiation
+
+Figure 8.4.10.2-1: Resource Status Reporting Initiation, successful operation
+
+NG-RAN node<sub>1</sub> initiates the procedure by sending the RESOURCE STATUS REQUEST message to NG-RAN node<sub>2</sub> to start a measurement, stop a measurement or add cells to report for a measurement. Upon receipt, NG-RAN node<sub>2</sub>:
+
+- shall initiate the requested measurement according to the parameters given in the request in case the *Registration Request* IE set to "start"; or
+- shall stop all cells measurements and terminate the reporting in case the *Registration Request* IE is set to "stop"; or
+- shall add cells indicated in the *Cell To Report List* IE to the measurements initiated before for the given measurement IDs, in case the *Registration Request* IE is set to "add". If measurements are already initiated for a cell indicated in the *Cell To Report List* IE, this information shall be ignored.
+
+If the *Registration Request* IE is set to "start" in the RESOURCE STATUS REQUEST message and the *Report Characteristics* IE indicates cell specific measurements, the *Cell To Report List* IE shall be included.
+
+If *Registration Request* IE is set to "add" in the RESOURCE STATUS REQUEST message, the *Cell To Report List* IE shall be included.
+
+If NG-RAN node<sub>2</sub> is capable to provide all requested resource status information, it shall initiate the measurement as requested by NG-RAN node<sub>1</sub> and respond with the RESOURCE STATUS RESPONSE message.
+
+### Interaction with other procedures
+
+When starting a measurement, the *Report Characteristics* IE in the RESOURCE STATUS REQUEST indicates the type of objects NG-RAN node<sub>2</sub> shall perform measurements on. For each cell, NG-RAN node<sub>2</sub> shall include in the RESOURCE STATUS UPDATE message:
+
+- the *Radio Resource Status* IE, if the first bit, "PRB Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1". If NG-RAN node<sub>2</sub> is a gNB and if the cell for which *Radio Resource Status* IE is requested to be reported supports more than one SSB, the *Radio Resource Status* IE for such cell shall include the *SSB Area Radio Resource Status Item* IE for all SSB areas supported by the cell. If the *SSB To Report List* IE is included for a cell, the *Radio Resource Status* IE for such cell shall include the requested *SSB Area Radio Resource Status List* IE; If the cell for which *Radio Resource Status* IE is requested to be reported supports more than one slice, and if the *Slice To Report List* IE is included for a cell, the *Radio Resource Status* IE for such cell shall, if supported, include the requested *Slice Radio Resource Status Item* IE;
+- the *TNL Capacity Indicator* IE, if the second bit, "TNL Capacity Ind Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1". The received *TNL Capacity Indicator* IE represents the lowest TNL capacity available for the cell, only taking into account interfaces providing user plane transport.
+- the *Composite Available Capacity Group* IE, if the third bit, "Composite Available Capacity Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1". If the *Cell Capacity Class Value* IE is included within the *Composite Available Capacity Group* IE, this IE is used to assign weights to the available capacity indicated in the *Capacity Value* IE. If NG-RAN node<sub>2</sub> is a gNB and if the cell for which *Composite Available Capacity Group* IE is requested to be reported supports more than one SSB, the *Composite Available Capacity Group* IE for such cell shall include the *SSB Area Capacity Value List* for all SSB areas supported by the cell, providing the SSB area capacity with respect to the *Cell Capacity Class Value*. If the *SSB To Report List* IE is included for a cell, the *Composite Available Capacity Group* IE for such cell shall include the requested *SSB Area Capacity Value List* IE.
+
+If the cell for which *Composite Available Capacity Group* IE is requested to be reported supports more than one slice, and if the *Slice To Report List* IE is included for a cell, the *Slice Available Capacity* IE for such cell shall include the requested *Slice Available Capacity Value Downlink* IE and *Slice Available Capacity Value Uplink* IE, providing the slice capacity with respect to the *Cell Capacity Class Value*.
+
+- the *Number of Active UEs* IE, if the fourth bit, "Number of Active UEs Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1";
+
+- the *RRC Connections* IE, if the fifth bit, "RRC Connections Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1".
+- the *NR-U Channel List* IE, if the sixth bit, "NR-U Channel List Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1".
+
+If the *Reporting Periodicity* IE in the RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. the NG-RAN node<sub>2</sub> shall report only once, unless otherwise requested within the *Reporting Periodicity* IE.
+
+#### 8.4.10.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: RESOURCE STATUS REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: RESOURCE STATUS FAILURE
+
+```
+
+Sequence diagram showing an unsuccessful resource status reporting initiation. NG-RAN node1 sends a RESOURCE STATUS REQUEST to NG-RAN node2, and NG-RAN node2 responds with a RESOURCE STATUS FAILURE.
+
+**Figure 8.4.10.3-1: Resource Status Reporting Initiation, unsuccessful operation**
+
+If any of the requested measurements cannot be initiated, NG-RAN node<sub>2</sub> shall send the RESOURCE STATUS FAILURE message with an appropriate cause value.
+
+#### 8.4.10.4 Abnormal Conditions
+
+For the same Measurement ID, if the initiating NG-RAN node<sub>1</sub> does not receive either the RESOURCE STATUS RESPONSE message or the RESOURCE STATUS FAILURE message, the NG-RAN node<sub>1</sub> may reinitiate the Resource Status Reporting Initiation procedure towards the same NG-RAN node, provided that the content of the new RESOURCE STATUS REQUEST message is identical to the content of the previously unacknowledged RESOURCE STATUS REQUEST message.
+
+If the NG-RAN node<sub>2</sub> receives a RESOURCE STATUS REQUEST message which includes the *Registration Request* IE set to "add" or "stop" and if the NG-RAN node<sub>2</sub> Measurement ID value received in the RESOURCE STATUS REQUEST message is not used, the NG-RAN node<sub>2</sub> shall initiate RESOURCE STATUS FAILURE message with an appropriate cause value.
+
+If the *Report Characteristics* IE bitmap is set to "0" (all bits are set to "0") in the RESOURCE STATUS REQUEST message then NG-RAN node<sub>2</sub> shall initiate a RESOURCE STATUS FAILURE message with an appropriate cause value.
+
+If the NG-RAN node<sub>2</sub> receives a RESOURCE STATUS REQUEST message which includes the *Registration Request* IE set to "start" and the *NG-RAN node1Measurement ID* IE corresponding to an existing on-going load measurement reporting, then NG-RAN node<sub>2</sub> shall initiate a RESOURCE STATUS FAILURE message with an appropriate cause value.
+
+## 8.4.11 Resource Status Reporting
+
+### 8.4.11.1 General
+
+This procedure is initiated by an NG-RAN node to report the result of measurements admitted by the NG-RAN node following a successful Resource Status Reporting Initiation procedure.
+
+The procedure uses non UE-associated signalling.
+
+### 8.4.11.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+ NG-RAN node2->>NG-RAN node1: RESOURCE STATUS UPDATE
+```
+
+Sequence diagram showing a successful Resource Status Reporting operation. NG-RAN node2 sends a RESOURCE STATUS UPDATE message to NG-RAN node1.
+
+**Figure 8.4.11.2-1: Resource Status Reporting, successful operation**
+
+NG-RAN node<sub>2</sub> shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure.
+
+If some results of the admitted measurements in RESOURCE STATUS UPDATE message are missing, NG-RAN node<sub>1</sub> shall consider that these results were not available at NG-RAN node<sub>2</sub>.
+
+### 8.4.11.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.4.11.4 Abnormal Conditions
+
+Void
+
+## 8.4.12 Access And Mobility Indication
+
+### 8.4.12.1 General
+
+The purpose of the Access and Mobility Indication procedure is to transfer Access and Mobility related information between NG-RAN nodes.
+
+#### 8.4.12.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: ACCESS AND MOBILITY INDICATION
+ Note right of NG-RAN node2:
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+Sequence diagram for Figure 8.2.12.2-1: Access And Mobility Indication, successful operation. It shows a message labeled 'ACCESS AND MOBILITY INDICATION' being sent from NG-RAN node1 to NG-RAN node2.
+
+Figure 8.2.12.2-1: Access And Mobility Indication, successful operation
+
+NG-RAN node<sub>1</sub> initiates the procedure by sending the ACCESS AND MOBILITY INDICATION message sent to NG-RAN node<sub>2</sub>.
+
+If the *Successful HO Report IE* is included in the ACCESS AND MOBILITY INDICATION message, NG-RAN node<sub>2</sub> may use it to optimize handover configurations.
+
+If the *Successful PSCell Change Report List IE* is included in the ACCESS AND MOBILITY INDICATION message, NG-RAN node<sub>2</sub> may use it to optimize PSCell change and/or PSCell addition configurations.
+
+If the *PSCell List Container IE* is included in the ACCESS AND MOBILITY INDICATION message, NG-RAN node<sub>2</sub> may use it to identify the NG-RAN node to which the *RA Report Container IE* should be forwarded.
+
+#### 8.4.12.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.4.13 Data Collection Reporting Initiation
+
+#### 8.4.13.1 General
+
+This procedure is used by an NG-RAN node to request the reporting of information to another NG-RAN node to support, e.g., AI/ML in NG-RAN.
+
+The procedure uses non UE-associated signalling.
+
+#### 8.4.13.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: DATA COLLECTION REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: DATA COLLECTION RESPONSE
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+```
+
+Sequence diagram for Figure 8.4.13.2-1: Data Collection Reporting Initiation, successful operation. It shows a 'DATA COLLECTION REQUEST' message from NG-RAN node1 to NG-RAN node2, followed by a 'DATA COLLECTION RESPONSE' message from NG-RAN node2 back to NG-RAN node1.
+
+Figure 8.4.13.2-1: Data Collection Reporting Initiation, successful operation
+
+NG-RAN node<sub>1</sub> initiates the procedure by sending the DATA COLLECTION REQUEST message to NG-RAN node<sub>2</sub> to start information reporting or to stop information reporting. Upon receipt, NG-RAN node<sub>2</sub>:
+
+- shall initiate the requested information reporting according to the parameters given in the request in case the *Registration Request* IE is set to "start"; or
+- shall stop all measurements and predictions and terminate the reporting in case the *Registration Request* IE is set to "stop".
+
+If the *Registration Request* IE is set to "start" in the DATA COLLECTION REQUEST message and the *Report Characteristics* IE indicates cell-specific information reporting, the *Cell To Report List for Data Collection* IE shall be included.
+
+If NG-RAN node<sub>2</sub> is capable of providing all of the requested information, it shall initiate the information reporting as requested by NG-RAN node<sub>1</sub> and respond with the DATA COLLECTION RESPONSE message.
+
+If NG-RAN node<sub>2</sub> is capable of providing some but not all of the requested information, it shall initiate the information reporting for the admitted requested information and include the *Node Measurement Initiation Result List* IE or the *Per Cell Measurement Initiation Result List* IE or both in the DATA COLLECTION RESPONSE message.
+
+If the *Reporting Periodicity* IE in the DATA COLLECTION REQUEST message is present, this indicates the periodicity for the reporting of configured measurement objects. The NG-RAN node<sub>2</sub> shall report only once, unless otherwise requested within the *Reporting Periodicity* IE.
+
+If the *Requested Prediction Time* IE in the DATA COLLECTION REQUEST message is present, it indicates the specific point in time to which the prediction of the requested information applies. The NG-RAN node<sub>2</sub> shall take it into account when generating the requested predicted information.
+
+If the *UE Trajectory Collection Configuration* IE is present in the DATA COLLECTION REQUEST message, the NG-RAN node<sub>2</sub> shall take it into account for the configuration of UE trajectory collection and reporting. NG-RAN node<sub>2</sub> shall report the UE trajectory only once. NG-RAN node<sub>2</sub> shall terminate the collection when at least one of the following conditions is fulfilled:
+
+- the time since UE was successfully handed over to NG-RAN node<sub>2</sub> is equal to the value of the *Collection Time Duration* IE;
+- the number of visited cells within NG-RAN node<sub>2</sub> is equal to the value of the *Number of Visited Cells* IE, if included;
+- UE moves to RRC\_INACTIVE or RRC\_IDLE state;
+- UE is handed over to a cell belonging to an NG-RAN node different from NG-RAN node<sub>2</sub>.
+
+The result of the UE trajectory collection is reported at the next available DATA COLLECTION UPDATE message.
+
+If the *UE Performance Collection Configuration* IE is present in the DATA COLLECTION REQUEST message, the NG-RAN node<sub>2</sub> shall take it into account for the configuration of UE performance collection and reporting. NG-RAN node<sub>2</sub> shall terminate the collection when at least one of the following conditions is fulfilled:
+
+- the time since UE was successfully handed over to NG-RAN node<sub>2</sub> is equal to the value of the *Collection Time Duration* IE;
+- UE moves to RRC\_INACTIVE or RRC\_IDLE state;
+- UE is handed over to another cell.
+
+The result of the UE performance collection is reported at the next available DATA COLLECTION UPDATE message.
+
+#### Interaction with the Data Collection Reporting procedure
+
+When starting a measurement, the *Report Characteristics* IE in the DATA COLLECTION REQUEST message indicates the type of objects NG-RAN node<sub>2</sub> shall perform measurements or predictions on. NG-RAN node<sub>2</sub> shall include in the DATA COLLECTION UPDATE message:
+
+- the *SSB Area Radio Resource Status List* IE, excluding the *DL scheduling PDCCH CCE usage* IE and *UL scheduling PDCCH CCE usage* IE, included in the *Predicted Radio Resource Status* IE, if the first bit, "Predicted Radio Resource Status" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Predicted Number of Active UEs* IE, if the second bit, "Predicted Number of Active UEs" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Predicted RRC Connections* IE, if the third bit, "Predicted RRC Connections" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Average UE Throughput DL* IE, if the fourth bit, "Average UE Throughput DL" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Average UE Throughput UL* IE, if the fifth bit, "Average UE Throughput UL" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Average Packet Delay* IE, if the sixth bit, "Average Packet Delay" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Average Packet Loss DL* IE, if the seventh bit, "Average Packet Loss DL" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Energy Cost* IE, if the eighth bit, "Energy Cost" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+- the *Measured UE Trajectory* IE, if the ninth bit, "Measured UE Trajectory" of the *Report Characteristics* IE included in the DATA COLLECTION REQUEST message is set to "1".
+
+#### 8.4.13.3 Unsuccessful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ NG-RAN node1->>NG-RAN node2: DATA COLLECTION REQUEST
+ Note right of NG-RAN node2:
+ NG-RAN node2-->>NG-RAN node1: DATA COLLECTION FAILURE
+ Note left of NG-RAN node1:
+
+```
+
+The diagram illustrates a sequence of messages between two entities, NG-RAN node<sub>1</sub> and NG-RAN node<sub>2</sub>. NG-RAN node<sub>1</sub> sends a "DATA COLLECTION REQUEST" message to NG-RAN node<sub>2</sub>. In response, NG-RAN node<sub>2</sub> sends a "DATA COLLECTION FAILURE" message back to NG-RAN node<sub>1</sub>. Both nodes are represented by rectangular boxes with a small horizontal bar at the bottom, indicating their lifelines.
+
+Sequence diagram showing an unsuccessful data collection operation between NG-RAN node1 and NG-RAN node2.
+
+**Figure 8.4.13.3-1: Data Collection Reporting Initiation, unsuccessful operation**
+
+If none of the requested information can be initiated, NG-RAN node<sub>2</sub> shall send the DATA COLLECTION FAILURE message with an appropriate cause value.
+
+#### 8.4.13.4 Abnormal Conditions
+
+For the same Measurement ID, if the initiating NG-RAN node<sub>1</sub> does not receive either the DATA COLLECTION RESPONSE message or the DATA COLLECTION FAILURE message, the NG-RAN node<sub>1</sub> may reinitiate the Data Collection Reporting Initiation procedure towards the same NG-RAN node, provided that the content of the new DATA
+
+COLLECTION REQUEST message is identical to the content of the previously unacknowledged DATA COLLECTION REQUEST message.
+
+If the NG-RAN node<sub>2</sub> receives a DATA COLLECTION REQUEST message which includes the *Registration Request* IE set to "stop" and if the NG-RAN node<sub>2</sub> Measurement ID value received in the DATA COLLECTION REQUEST message is not used, the NG-RAN node<sub>2</sub> shall initiate DATA COLLECTION FAILURE message with an appropriate cause value.
+
+If in the *Report Characteristics* IE bitmap all bits are set to "0" in the DATA COLLECTION REQUEST message, then NG-RAN node<sub>2</sub> shall initiate a DATA COLLECTION FAILURE message with an appropriate cause value.
+
+If the NG-RAN node<sub>2</sub> receives a DATA COLLECTION REQUEST message which includes the *Registration Request* IE set to "start" and the *NG-RAN node<sub>1</sub> Measurement ID* IE corresponding to an existing on-going Data Collection reporting, then NG-RAN node<sub>2</sub> shall initiate a DATA COLLECTION FAILURE message with an appropriate cause value.
+
+## 8.4.14 Data Collection Reporting
+
+### 8.4.14.1 General
+
+This procedure is initiated by an NG-RAN node to report information accepted by the NG-RAN node following a successful Data Collection Reporting Initiation procedure for the purpose of, e.g., AI/ML in NG-RAN.
+
+The procedure uses non UE-associated signalling.
+
+### 8.4.14.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant NG-RAN node1
+ participant NG-RAN node2
+ Note left of NG-RAN node1:
+ Note right of NG-RAN node2:
+ NG-RAN node2->>NG-RAN node1: DATA COLLECTION UPDATE
+```
+
+Sequence diagram showing successful data collection reporting. NG-RAN node2 sends a DATA COLLECTION UPDATE message to NG-RAN node1.
+
+Figure 8.4.14.2-1: Data Collection Reporting, successful operation
+
+NG-RAN node<sub>2</sub> shall report the accepted information in DATA COLLECTION UPDATE message. The accepted information is the information that was successfully initiated during the preceding Data Collection Reporting Initiation procedure.
+
+### 8.4.14.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.4.14.4 Abnormal Conditions
+
+Void.
+
+## 8.5 IAB Procedures
+
+### 8.5.1 F1-C Traffic Transfer
+
+#### 8.5.1.1 General
+
+The purpose of the F1-C Traffic Transfer procedure is to deliver F1-C traffic between the M-NG-RAN node and the S-NG-RAN node serving a dual-connected IAB-node, where the F1-C traffic is either received from the IAB-node or sent to the IAB-node.
+
+The procedure uses UE-associated signalling. This procedure is only applicable to IAB-nodes.
+
+#### 8.5.1.2 Successful Operation
+
+
+
+The diagram illustrates the F1-C Traffic Transfer procedure between two network nodes. On the left is a box labeled 'M/S-NG-RAN Node' and on the right is a box labeled 'S/M-NG-RAN Node'. Both boxes have a vertical line extending downwards to a horizontal bar at the bottom. A horizontal arrow labeled 'F1-C TRAFFIC TRANSFER' points from the vertical line of the M/S-NG-RAN Node to the vertical line of the S/M-NG-RAN Node.
+
+Diagram of F1-C Traffic Transfer procedure, successful operation
+
+**Figure 8.5.1.2-1: F1-C Traffic Transfer procedure, successful operation**
+
+Either the M-NG-RAN Node initiates the procedure by sending the F1-C TRAFFIC TRANSFER message to the S-NG-RAN Node, or the S-NG-RAN Node initiates the procedure by sending the F1-C TRAFFIC TRANSFER message to the M-NG-RAN Node.
+
+Upon reception of the F1-C TRAFFIC TRANSFER message, the receiving node, not being the IAB-donor of the IAB-node, shall deliver the contained F1-C traffic to the IAB-node. Alternatively, the receiving node, being the IAB-donor of the IAB-node, shall handle the received F1-C traffic as specified in TS 38.473[41].
+
+#### 8.5.1.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.5.1.4 Abnormal Conditions
+
+Not Applicable.
+
+## 8.5.2 IAB Transport Migration Management
+
+### 8.5.2.1 General
+
+The purpose of the IAB Transport Migration Management procedure is to exchange information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, for the purpose of managing the migration of the boundary and descendant IAB-node traffic between the topologies managed by the two IAB-donors.
+
+The procedure is applicable to inter-donor partial migration, inter-donor RLF recovery and inter-donor topology redundancy cases. The procedure is initiated by the F1-terminating IAB-donor of the boundary IAB-node. The
+
+procedure can be used to set up, modify and release (e.g., for the purpose of revoking) the resources under the non-F1-terminating IAB-donor used for serving the offloaded traffic.
+
+The procedure uses UE-associated signalling.
+
+### 8.5.2.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant F1-terminating IAB donor
+ participant Non-F1-terminating IAB-donor
+ Note left of F1-terminating IAB donor:
+ F1-terminating IAB donor->>Non-F1-terminating IAB-donor: IAB TRANSPORT MIGRATION MANAGEMENT REQUEST
+ Note right of Non-F1-terminating IAB-donor:
+ Non-F1-terminating IAB-donor-->>F1-terminating IAB donor: IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE
+ Note left of F1-terminating IAB donor:
+
+```
+
+Sequence diagram showing the successful operation of IAB Transport Migration Management. The F1-terminating IAB donor sends a REQUEST message to the Non-F1-terminating IAB-donor, which responds with a RESPONSE message.
+
+**Figure 8.5.2.2-1: IAB Transport Migration Management triggered by the F1-terminating IAB-donor, successful operation**
+
+The F1-terminating IAB-donor initiates the procedure by sending the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the non-F1-terminating IAB-donor.
+
+The non-F1-terminating IAB-donor may respond with the IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message by indicating:
+
+- Traffic accepted for offloading, within the *Traffic Added List* IE;
+- Already offloaded traffic accepted for modification, within the *Traffic Modified List* IE;
+- Traffic not accepted for offloading, within the *Traffic Not Added List* IE;
+- Already offloaded traffic not accepted for modification within the *Traffic Not Modified List* IE.
+
+If the *Traffic To Be Released Information* IE is contained in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message, the non-F1-terminating IAB-donor should release all offloaded traffic if the *All Traffic Indication* IE in the *Traffic to Be Released Information* IE is set to "true", or release only the offloaded traffic indicated by the *Traffic to Be Released Item* IE in the *Traffic to Be Released Information* IE.
+
+If the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message contains the *Traffic to Be Released Information* IE, the non-F1-terminating IAB-donor shall include the *Traffic Released List* IE in the IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message.
+
+If the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message contains the *IAB IPv4 Addresses Requested* IE or the *IAB IPv6 Request Type* IE in the *IAB TNL Address Request* IE, the non-F1-terminating IAB-donor shall, if supported, provide the allocated TNL address via the *IAB TNL Address Response* IE in the IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message. If the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message contains the *IAB TNL Address To Remove List* IE in the *IAB TNL Address Request* IE, the non-F1-terminating IAB-donor shall consider that the TNL address(es) are no longer used by the F1-terminating IAB-donor.
+
+If the *IAB TNL Address Exception* IE is contained in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message, the non-F1-terminating IAB-donor shall, if supported, configure the related IAB-donor-DU to enable traffic re-routing over the inter-IAB-donor-DU tunnel.
+
+If the *IAB QoS Mapping Information* IE is contained in the IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message, the F1-terminating IAB-donor, shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets of the offloaded traffic.
+
+If the *Mobile IAB-MT BAP Address* IE is contained in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message and this is the first UE-associated signaling for the IAB-MT identified by the *Mobile IAB-MT BAP Address* IE, the non-F1-terminating IAB-donor, shall, if supported, ignore the *Non-F1-Terminating IAB-donor UE XnAP ID* IE and allocate an XnAP UE ID for the mobile IAB-MT to be used in the IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message and subsequent procedure(s) for this mobile IAB-MT.
+
+### 8.5.2.3 Unsuccessful Operation
+
+
+
+```
+sequenceDiagram
+ participant F1-terminating IAB donor
+ participant Non-F1-terminating IAB-donor
+ Note left of F1-terminating IAB donor:
+ F1-terminating IAB donor->>Non-F1-terminating IAB-donor: IAB TRANSPORT MIGRATION MANAGEMENT REQUEST
+ Note right of Non-F1-terminating IAB-donor:
+ Non-F1-terminating IAB-donor-->>F1-terminating IAB donor: IAB TRANSPORT MIGRATION MANAGEMENT REJECT
+ Note left of F1-terminating IAB donor:
+```
+
+Sequence diagram showing an unsuccessful IAB Transport Migration Management operation. The F1-terminating IAB donor sends a REQUEST to the Non-F1-terminating IAB-donor, which responds with a REJECT.
+
+**Figure 8.5.2.3-1: IAB Transport Migration Management triggered by the F1-terminating IAB-donor, unsuccessful operation**
+
+If the non-F1-terminating IAB-donor is not able to accept any traffic for offloading or modification from the F1-terminating IAB-donor, or a failure occurs during the IAB Transport Migration Management procedure, the non-F1-terminating IAB-donor sends the IAB TRANSPORT MIGRATION MANAGEMENT REJECT message with an appropriate cause value to the F1-terminating IAB-donor.
+
+### 8.5.2.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.5.3 IAB Transport Migration Modification
+
+### 8.5.3.1 General
+
+The purpose of the IAB Transport Migration Modification procedure is to modify the backhaul information of the offloaded traffic in the topology of the non-F1-terminating IAB-donor of a boundary IAB-node. The procedure can also be used to release the resources under the non-F1-terminating IAB-donor used for serving the offloaded traffic, and to transfer the authorization status of the boundary IAB-node. The procedure can also be used to transfer the authorization status information of the mobile IAB-node.
+
+The procedure is applicable to inter-donor partial migration, inter-donor RLF recovery and inter-donor topology redundancy cases. The procedure is initiated by the non-F1-terminating IAB-donor of the boundary IAB-node.
+
+The procedure uses UE-associated signalling.
+
+### 8.5.3.2 Successful Operation
+
+
+
+```
+
+sequenceDiagram
+ participant Non-F1-terminating donor
+ participant F1-terminating donor
+ Note left of Non-F1-terminating donor:
+ Note right of F1-terminating donor:
+ Non-F1-terminating donor->>F1-terminating donor: IAB TRANSPORT MIGRATION MODIFICATION REQUEST
+ F1-terminating donor-->>Non-F1-terminating donor: IAB TRANSPORT MIGRATION MODIFICATION RESPONSE
+
+```
+
+Sequence diagram showing the successful operation of IAB Transport Migration Modification. A Non-F1-terminating donor sends an IAB TRANSPORT MIGRATION MODIFICATION REQUEST to an F1-terminating donor, which responds with an IAB TRANSPORT MIGRATION MODIFICATION RESPONSE.
+
+**Figure 8.5.3.2-1: IAB Transport Migration Modification, successful operation**
+
+The non-F1-terminating IAB-donor initiates the procedure by sending the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message to the F1-terminating IAB-donor. The F1-terminating IAB-donor responds with the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message.
+
+If the *Traffic Required To Be Modified List* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor shall update the backhaul information in non-F1-terminating topology for each traffic indicated in the list, and include the *Traffic Required Modified List* IE in the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message.
+
+If the *Traffic To Be Released Information* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor shall consider that all offloaded traffic will be released by the non-F1-terminating IAB-donor if the *All Traffic Indication* IE in the *Traffic to Be Released Information* IE is set to "true", or that only the traffic indicated by the *Traffic to Be Released Item* IE will be released by the non-F1-terminating IAB-donor.
+
+If the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message contains the *Traffic To Be Released Information* IE, the F1-terminating IAB-donor shall include the *Traffic Released List* IE in the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message.
+
+If the *IAB TNL Address To Be Added* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor shall allocate the TNL address(es) contained in this IE to the boundary IAB-node or the descendant IAB-nodes.
+
+If the *IAB TNL Address To Be Released* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor shall release the TNL address(es) contained in this IE for the boundary IAB-node or the descendant IAB-nodes.
+
+If the *IAB QoS Mapping Information* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor, shall, if supported, use it to set DSCP and/or IPv6 flow label fields for the downlink IP packets of the offloaded traffic.
+
+If the *IAB Authorization Status* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor, shall, if supported, store it and use it accordingly. If the *IAB Authorization Status* IE is set to "not authorized", the F1-terminating IAB-donor, shall, if supported, initiate actions to ensure that the IAB-node will not serve any UE(s), as defined in TS 38.401[2].
+
+If the *Mobile IAB Authorization Status* IE is contained in the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message, the F1-terminating IAB-donor, shall, if supported, store it and use it as defined in TS 38.401[2]. If the *Mobile IAB-node Authorization Status* IE is set to "not authorized", the F1-terminating IAB-donor, shall, if supported, initiate actions to ensure that the mobile IAB node will not serve any UE(s), as defined in TS 38.401[2].
+
+### 8.5.3.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.5.3.4 Abnormal Conditions
+
+Not applicable.
+
+## 8.5.4 IAB Resource Coordination
+
+### 8.5.4.1 General
+
+The purpose of the IAB Resource Coordination procedure is to exchange the semi-static radio resource configuration pertaining to a boundary IAB-node and/or its parent node, between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, for the purpose of resource multiplexing between the IAB-MT and the IAB-DU of the boundary IAB-node. The procedure can be initiated by the F1-terminating or non-F1-terminating IAB-donor of the boundary IAB-node.
+
+The procedure uses UE-associated signalling.
+
+### 8.5.4.2 Successful Operation
+
+
+
+```
+sequenceDiagram
+ participant F1-terminating/non-F1-terminating IAB-donor
+ participant Non-F1-terminating/F1-terminating IAB-donor
+ Note left of F1-terminating/non-F1-terminating IAB-donor:
+ F1-terminating/non-F1-terminating IAB-donor->>Non-F1-terminating/F1-terminating IAB-donor: IAB RESOURCE COORDINATION REQUEST
+ Note right of Non-F1-terminating/F1-terminating IAB-donor:
+ Non-F1-terminating/F1-terminating IAB-donor-->>F1-terminating/non-F1-terminating IAB-donor: IAB RESOURCE COORDINATION RESPONSE
+ Note left of F1-terminating/non-F1-terminating IAB-donor:
+```
+
+The diagram illustrates a sequence of two messages between two entities. On the left is a box labeled 'F1-terminating/non-F1-terminating IAB-donor' with a vertical lifeline extending downwards. On the right is a box labeled 'Non-F1-terminating/F1-terminating IAB-donor' with a vertical lifeline extending downwards. A horizontal arrow points from the left lifeline to the right lifeline, labeled 'IAB RESOURCE COORDINATION REQUEST'. A return horizontal arrow points from the right lifeline to the left lifeline, labeled 'IAB RESOURCE COORDINATION RESPONSE'. Both lifelines end with a thick horizontal bar at the bottom.
+
+Sequence diagram of IAB Resource Coordination successful operation
+
+**Figure 8.5.4.2-1: IAB Resource Coordination triggered by the F1-terminating/non-F1-terminating IAB-donor, successful operation**
+
+The F1-terminating/non F1-terminating IAB-donor initiates the procedure by sending the IAB RESOURCE COORDINATION REQUEST message to the non-F1-terminating/F1-terminating IAB-donor. The non-F1-terminating/F1-terminating IAB-donor shall respond with the IAB RESOURCE COORDINATION RESPONSE message to the F1-terminating/non-F1-terminating IAB-donor.
+
+If the *Boundary Node Cells List IE* and/or *Parent Node Cells List IE* is included in the IAB RESOURCE COORDINATION REQUEST or in the IAB RESOURCE COORDINATION RESPONSE message, the receiving F1-terminating/non-F1-terminating IAB-donor should take this information into account for resource coordination with the sending non-F1-terminating/F1-terminating IAB-donor.
+
+### 8.5.4.3 Unsuccessful Operation
+
+Not applicable.
+
+### 8.5.4.4 Abnormal Conditions
+
+Not applicable.
+
+## 9 Elements for XnAP Communication
+
+### 9.0 General
+
+Sub clauses 9.1 and 9.2 describe the structure of the messages and information elements required for the XnAP protocol in tabular format. Sub clause 9.3 provides the corresponding ASN.1 definition.
+
+The following attributes are used for the tabular description of the messages and information elements: Presence, Range, Criticality and Assigned Criticality. Their definition and use can be found in TS 38.413 [5].
+
+NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [6].
+
+### 9.1 Message Functional Definition and Content
+
+#### 9.1.1 Messages for Basic Mobility Procedures
+
+##### 9.1.1.1 HANDOVER REQUEST
+
+This message is sent by the source NG-RAN node to the target NG-RAN node to request the preparation of resources for a handover.
+
+Direction: source NG-RAN node → target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------------|----------|-------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Source NG-RAN node<br>UE XnAP ID reference | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated at the source NG-RAN node | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | reject |
+| Target Cell Global ID | M | | 9.2.3.25 | Includes either an E-UTRA CGI or an NR CGI | YES | reject |
+| GUAMI | M | | 9.2.3.24 | | YES | reject |
+| <b>UE Context Information</b> | | 1 | | | YES | reject |
+| >NG-C UE associated Signalling reference | M | | AMF UE NGAP ID<br>9.2.3.26 | Allocated at the AMF on the source NG-C connection. | – | |
+| >Signalling TNL association address at source NG-C side | M | | CP Transport Layer Information<br>9.2.3.31 | This IE indicates the AMF's IP address of the SCTP association used at the source NG-C interface instance.<br>NOTE: If no UE TNLA binding exists at the source NG-RAN node, the source NG-RAN node indicates the TNL | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | association address it would have selected if it would have had to create a UE TNLA binding. | | |
+| >UE Security Capabilities | M | | 9.2.3.49 | | – | |
+| >AS Security Information | M | | 9.2.3.50 | | – | |
+| >Index to RAT/Frequency Selection Priority | O | | 9.2.3.23 | | – | |
+| >UE Aggregate Maximum Bit Rate | M | | 9.2.3.17 | | – | |
+| >PDU Session Resources To Be Setup List | | 1 | 9.2.1.1 | Similar to NG-C signalling, containing UL tunnel information per PDU Session Resource; and in addition, the source side QoS flow $\Leftrightarrow$ DRB mapping | – | |
+| >RRC Context | M | | OCTET STRING | Either includes the <i>HandoverPreparationInformation</i> message as defined in subclause 10.2.2. of TS 36.331 [14], or the <i>HandoverPreparationInformation-NB</i> message as defined in subclause 10.6.2 of TS 36.331 [14], if the target NG-RAN node is an ng-eNB, or the <i>HandoverPreparationInformation</i> message as defined in subclause 11.2.2 of TS 38.331 [10], if the target NG-RAN node is a gNB. | – | |
+| >Location Reporting Information | O | | 9.2.3.47 | Includes the necessary parameters for location reporting. | – | |
+| >Mobility Restriction | O | | 9.2.3.53 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------|------------|-------|------------------------------------------------------|---------------------------------------------------------------------|-------------|----------------------|
+| List | | | | | | |
+| >5GC Mobility Restriction List Container | O | | 9.2.3.100 | | YES | ignore |
+| >NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.2.3.107 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore |
+| >LTE UE Sidelink Aggregate Maximum Bit Rate | O | | 9.2.3.108 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore |
+| >Management Based MDT PLMN List | O | | MDT PLMN List 9.2.3.133 | | YES | ignore |
+| >UE Radio Capability ID | O | | 9.2.3.138 | | YES | reject |
+| >MBS Session Information List | O | | 9.2.1.36 | | YES | ignore |
+| >5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate 9.2.3.107 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore |
+| >UE Slice Maximum Bit Rate List | O | | 9.2.3.167 | | YES | ignore |
+| >NR A2X UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate 9.2.3.107 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore |
+| >LTE A2X UE PC5 Aggregate Maximum Bit Rate | O | | LTE UE Sidelink Aggregate Maximum Bit Rate 9.2.3.108 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore |
+| Trace Activation | O | | 9.2.3.55 | | YES | ignore |
+| Masked IMEISV | O | | 9.2.3.32 | | YES | ignore |
+| UE History Information | M | | 9.2.3.64 | | YES | ignore |
+| <b>UE Context Reference at the S-NG-RAN node</b> | O | | | | YES | ignore |
+| >Global NG-RAN Node ID | M | | 9.2.2.3 | | – | |
+| >S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | | – | |
+| <b>Conditional Handover Information Request</b> | O | | | | YES | reject |
+| >CHO Trigger | M | | ENUMERATED (CHO-initiation, CHO-replace, ...) | | – | |
+| >Target NG-RAN node UE XnAP ID | C-ifCHOmod | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the target NG-RAN node | – | |
+| >Estimated Arrival Probability | O | | INTEGER (1..100) | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|-------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >Conditional Handover Time Based Information | O | | | This IE only applies to NTN. | YES | ignore |
+| >>Handover Window Start | M | | INTEGER (0..549755813887) | Corresponds to information provided in the <i>t1-Threshold</i> contained in the <i>ReportConfigNR</i> IE as defined in TS 38.331 [10] | – | |
+| >>Handover Window Duration | M | | INTEGER (1..6000) | Corresponds to information provided in the <i>duration</i> contained in the <i>condEventT1</i> contained in the <i>ReportConfigNR</i> IE as defined in TS 38.331 [10] | – | |
+| >Maximum Number of Conditional Reconfigurations to Prepare | O | | INTEGER (1..8, ...) | Indicates that the target NG-RAN node may prepare for CHO with candidate PSCell(s) configuration and indicates the maximum number of conditional reconfigurations that the target NG-RAN node may prepare. | YES | reject |
+| NR V2X Services Authorized | O | | 9.2.3.105 | | YES | ignore |
+| LTE V2X Services Authorized | O | | 9.2.3.106 | | YES | ignore |
+| PC5 QoS Parameters | O | | 9.2.3.109 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore |
+| Mobility Information | O | | BIT STRING (SIZE (32)) | Information related to the handover; the source NG-RAN node provides it in order to enable later analysis of the conditions that led to a wrong HO. | YES | ignore |
+| UE History Information from the UE | O | | 9.2.3.110 | | YES | ignore |
+| IAB Node Indication | O | | ENUMERATED (true, ...) | | YES | reject |
+| No PDU Session | O | | ENUMERATED | This IE applies | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Indication | | | (true, ...) | only if the UE is an IAB-MT. | | |
+| Time Synchronisation Assistance Information | O | | 9.2.3.153 | | YES | ignore |
+| QMC Configuration Information | O | | 9.2.3.156 | | YES | ignore |
+| 5G ProSe Authorized | O | | 9.2.3.159 | | YES | ignore |
+| 5G ProSe PC5 QoS Parameters | O | | 9.2.3.160 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore |
+| DL LBT Failure Information Request | O | | ENUMERATED (inquiry, ...) | This IE indicates that information on DL LBT Failures occurring at the target gNB during handover execution that results in mobility failure is requested | YES | ignore |
+| Aerial UE Subscription Information | O | | 9.2.3.175 | | YES | ignore |
+| NR A2X Services Authorized | O | | 9.2.3.176 | | YES | ignore |
+| LTE A2X Services Authorized | O | | 9.2.3.177 | | YES | ignore |
+| A2X PC5 QoS Parameters | O | | 9.2.3.178 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore |
+| Cell Based UE Trajectory Prediction | O | | 9.2.3.180 | This IE contains information about cells that a UE is predicted to be connected to. | YES | ignore |
+| Data Collection ID | O | | 9.2.3.184 | | YES | ignore |
+| Candidate Relay UE Info List | O | | 9.2.3.188 | | YES | reject |
+| SN-related QMC Information at MN | O | | 9.2.3.199 | This IE contains the information that the M-NG-RAN node has about the QMC configurations at the S-NG-RAN node. | YES | ignore |
+| Source SN to Target SN QMC Information | O | | QMC Configuration Information 9.2.3.156 | This IE contains SN-related QMC configuration information to be forwarded to the target S-NG-RAN node. | YES | ignore |
+| Mobile IAB Authorization Status | O | | 9.2.2.105 | | YES | reject |
+
+| Condition | Explanation |
+|-----------|--------------------------------------------------------------------------------------------|
+| ifCHOmod | This IE shall be present if the <i>CHO Trigger</i> IE is present and set to "CHO-replace". |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------|
+| maxnoofMDTPLMNs | PLMNs in the Management Based MDT PLMN list. Value is 16. |
+
+### 9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE
+
+This message is sent by the target NG-RAN node to inform the source NG-RAN node about the prepared resources at the target.
+
+Direction: target NG-RAN node → source NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------------------|----------|-------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Source NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated at the source NG-RAN node | YES | ignore |
+| Target NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated at the target NG-RAN node | YES | ignore |
+| PDU Session<br>Resources Admitted<br>List | M | | 9.2.1.2 | Ignored, if the <i>CHO-CPAC Configuration Indicator</i> IE is included and set to "cho-only-not-prepared". | YES | ignore |
+| PDU Session<br>Resources Not<br>Admitted List | O | | 9.2.1.3 | | YES | ignore |
+| Target NG-RAN node<br>To Source NG-RAN<br>node Transparent<br>Container | M | | OCTET<br>STRING | Either includes the <i>HandoverCommand</i> message as defined in subclause 10.2.2 of TS 36.331 [14], if the target NG-RAN node is an ng-eNB, or the <i>HandoverCommand</i> message as defined in subclause 11.2.2 of TS 38.331 [10], if the target NG-RAN node is a gNB. Ignored if the <i>CHO-CPAC Configuration Indicator</i> IE is included within the <i>CHO-CPAC</i> | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|-------|-----------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>Information IE and set to "cho-only-not-prepared".</i> | | |
+| UE Context Kept Indicator | O | | 9.2.3.68 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| DRBs transferred to MN | O | | DRB List<br>9.2.1.29 | In case of DC, indicates that SN Status is needed for the listed DRBs from the S-NG-RAN node. | YES | ignore |
+| DAPS Response Information | O | | 9.2.1.34 | | YES | reject |
+| <b>Conditional Handover Information Acknowledge</b> | O | | | | YES | reject |
+| >Requested Target Cell ID | M | | Target Cell Global ID<br>9.2.3.25 | Target cell indicated in the corresponding HANDOVER REQUEST message | – | |
+| >Maximum Number of CHO Preparations | O | | 9.2.3.101 | | – | |
+| >CHO-CPAC Information | O | | 9.2.3.202 | | YES | reject |
+| MBS Session Information Response List | O | | 9.2.1.38 | | YES | ignore |
+| RRC Config Indication | O | | 9.2.3.72 | | YES | ignore |
+| PDU Set based Handling Indicator | O | | 9.2.3.206 | | YES | ignore |
+
+### 9.1.1.3 HANDOVER PREPARATION FAILURE
+
+This message is sent by the target NG-RAN node to inform the source NG-RAN node that the Handover Preparation has failed.
+
+Direction: target NG-RAN node → source NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|------------------------------------|---------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Source NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the source NG-RAN node | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Requested Target Cell ID | O | | Target Cell Global ID<br>9.2.3.25 | Target cell indicated in the corresponding HANDOVER REQUEST message | YES | reject |
+
+### 9.1.1.4 SN STATUS TRANSFER
+
+This message is sent by the source NG-RAN node to the target NG-RAN node to transfer the uplink/downlink PDCP SN, HFN status and MRO related information during a handover or for dual connectivity.
+
+Direction: source NG-RAN node → target NG-RAN node(handover),
+ NG-RAN node from which the DRB context is transferred → NG-RAN node to which the DRB context is transferred (RRC connection re-establishment or dual connectivity).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Source NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated for handover at the source NG-RAN node and for dual connectivity at the NG-RAN node from which the DRB context is transferred. | YES | reject |
+| Target NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated for handover at the target NG-RAN node and for dual connectivity at the NG-RAN node to which the DRB context is transferred. | YES | reject |
+| DRBs Subject To Status Transfer List | M | | 9.2.1.14 | | YES | ignore |
+| CHO Configuration | O | | 9.2.2.76 | | YES | ignore |
+| Mobility Information | O | | BIT STRING<br>(SIZE (32)) | | YES | ignore |
+
+### 9.1.1.5 UE CONTEXT RELEASE
+
+This message is sent by the target NG-RAN node to the source NG-RAN node to indicate that resources can be released.
+
+Direction: target NG-RAN node → source NG-RAN node, M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------|----------|-------|---------------------------------------|-------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Source NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated for handover at the source NG-RAN node or for dual connectivity at the S-NG-RAN node. | YES | reject |
+| Target NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated for handover at the target NG-RAN | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------|-------------|----------------------|
+| | | | | node or for dual connectivity at the M-NG-RAN node. | | |
+
+### 9.1.1.6 HANDOVER CANCEL
+
+This message is sent by the source NG-RAN node to the target NG-RAN node to cancel an ongoing handover.
+
+Direction: source NG-RAN node → target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|--------------------------|---------------------------------|--------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Source NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the source NG-RAN node. | YES | reject |
+| Target NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the target NG-RAN node. | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| <b>Candidate Cells To Be Cancelled List</b> | | 0 .. <maxnoofCellsInCHO> | | | YES | reject |
+| >Target Cell ID | M | | Target Cell Global ID 9.2.3.25 | | – | |
+
+| Range bound | Explanation |
+|-------------------|--------------------------------------------------------------------------------|
+| maxnoofCellsInCHO | Maximum no. cells that can be prepared for a conditional handover. Value is 8. |
+
+### 9.1.1.7 RAN PAGING
+
+This message is sent by the NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub> to page a UE.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE <i>UE Identity Index Value</i> | M | | | | YES | reject |
+| >Length-10 | | | | | | |
+| >>Index Length-10 | M | | BIT STRING (SIZE(10)) | Coded as specified in TS 38.304 [33] and TS 36.304 [34]. | – | |
+| UE RAN Paging Identity | M | | 9.2.3.43 | | YES | ignore |
+| Paging DRX | M | | 9.2.3.66 | Includes the RAN paging cycle as defined in TS 36.304 [34] and | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | 38.304 [33]. | | |
+| RAN Paging Area | M | | 9.2.3.38 | | YES | reject |
+| Paging Priority | O | | 9.2.3.44 | | YES | ignore |
+| Assistance Data for RAN Paging | O | | 9.2.3.41 | | YES | ignore |
+| UE Radio Capability for Paging | O | | 9.2.3.91 | | YES | ignore |
+| Extended UE Identity Index Value | O | | 9.2.3.141 | Coded as specified in TS 36.304 [34] and 38.304 [33]. | YES | ignore |
+| E-UTRA Paging eDRX Information | O | | 9.2.3.142 | | YES | ignore |
+| UE specific DRX | O | | 9.2.3.143 | Includes the UE specific paging cycle as defined in TS 36.304 [34] and 38.304 [33]. | YES | ignore |
+| NR Paging eDRX Information | O | | 9.2.3.161 | | YES | ignore |
+| NR Paging eDRX Information for RRC INACTIVE | O | | 9.2.3.162 | | YES | ignore |
+| Paging Cause | O | | ENUMERATED (voice, ...) | | YES | ignore |
+| PEIPS Assistance Information | O | | 9.2.3.166 | | YES | ignore |
+| Hashed UE Identity Index Value | O | | 9.2.3.144a | | YES | ignore |
+| MT-SDT Information | O | | 9.2.3.172 | | YES | ignore |
+| NR Paging Long eDRX Information for RRC INACTIVE | O | | 9.2.3.195 | | YES | ignore |
+
+### 9.1.1.8 RETRIEVE UE CONTEXT REQUEST
+
+This message is sent by the new NG-RAN node to request the old NG-RAN node to transfer the UE Context to the new NG-RAN.
+
+Direction: new NG-RAN node → old NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node | YES | reject |
+| UE Context ID | M | | 9.2.3.40 | | YES | reject |
+| Integrity protection | M | | BIT STRING (SIZE (16)) | <b>RRC Resume:</b> Corresponds to information provided either in the <i>resumeMAC-I</i> either contained in | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------|----------|-------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | the <i>RRC ResumeRequest</i> or the <i>RRCResumeRequest1</i> message as defined in TS 38.331 [10]) or in the <i>shortResumeMAC-I</i> in the <i>RRRConnection ResumeRequest</i> message as defined in TS 36.331 [14])<br><b>RRC Reestablishment:</b><br>Corresponds to information provided either in the <i>shortMAC-I</i> contained in the <i>RRRReestablishmentRequest</i> message as defined in TS 38.331 [10]) or in the <i>shortMAC-I</i> in the <i>RRRConnection ReestablishmentRequest</i> message as defined in TS 36.331 [14]).<br><b>RRC Resume for UP CIoT Optimization:</b><br>Corresponds to information provided in the <i>shortResumeMAC-I</i> in the <i>RRRConnection ResumeRequest</i> message or the <i>RRRConnection ResumeRequest-NB</i> message as defined in TS 36.331 [14]. | | |
+| New Cell Identifier | M | | NG-RAN Cell Identity 9.2.2.9 | <b>RRC Resume:</b><br>Corresponds to information provided either in the <i>targetCellIdentity</i> within the | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <p><i>VarResumeMAC-Input</i> as specified in TS 38.331 [10] or in the <i>cellIdentity</i> within the <i>VarShortINACTIV E-MAC-Input</i> as specified in TS 36.331 [14].</p> <p><b>RR</b></p> <p><b>Reestablishment:</b><br/>Corresponds to information provided in the <i>targetCellIdentity</i> within the <i>VarShortMAC-Input</i> as specified in TS 38.331 [10] or in the <i>cellIdentity</i> within the <i>VarShortMAC-Input</i> as specified in TS 36.331 [14].</p> <p><b>RR</b> <b>Resume for UP CIoT</b></p> <p><b>Optimization:</b><br/>Corresponds to information provided either in the <i>cellIdentity</i> within the <i>VarShortResume MAC-Input</i> or the <i>VarShortResume MAC-Input-NB</i> as specified in TS 36.331 [14].</p> | | |
+| RR <b>Resume Cause</b> | O | | 9.2.3.61 | In case of RNA Update, contains information provided in the <i>resumeCause</i> by the UE in the <i>RR</i> <b>ResumeRequ</b> est or the <i>RR</i> <b>ResumeRequ</b> est1 message, as defined in TS 38.331 [10], or information provided in the <i>resumeCause-r15</i> in the <i>RR</i> <b>Connection ResumeRequest</b> message, as | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------|----------|-------|-----------------------|----------------------------|-------------|----------------------|
+| | | | | defined in TS 36.331 [14]. | | |
+| SDT Support Request | O | | 9.2.3.163 | | YES | ignore |
+
+### 9.1.1.9 RETRIEVE UE CONTEXT RESPONSE
+
+This message is sent by the old NG-RAN node to transfer the UE context to the new NG-RAN node.
+
+Direction: old NG-RAN node → new NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node | YES | ignore |
+| Old NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the old NG-RAN node | YES | ignore |
+| GUAMI | M | | 9.2.3.24 | | YES | reject |
+| UE Context Information – Retrieve UE Context Response | M | | 9.2.1.13 | | YES | reject |
+| Trace Activation | O | | 9.2.3.55 | | YES | ignore |
+| Masked IMEISV | O | | 9.2.3.32 | | YES | ignore |
+| Location Reporting Information | O | | 9.2.3.47 | Includes the necessary parameters for location reporting. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| NR V2X Services Authorized | O | | 9.2.3.105 | | YES | ignore |
+| LTE V2X Services Authorized | O | | 9.2.3.106 | | YES | ignore |
+| PC5 QoS Parameters | O | | 9.2.3.109 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore |
+| UE History Information | O | | 9.2.3.64 | | YES | ignore |
+| UE History Information from the UE | O | | 9.2.3.110 | | YES | ignore |
+| Management Based MDT PLMN List | O | | MDT PLMN List 9.2.3.133 | | YES | ignore |
+| IAB Node Indication | O | | ENUMERATED (true, ...) | | YES | reject |
+| <b>UE Context Reference at the S-NG-RAN node</b> | O | | | | YES | ignore |
+| >Global NG-RAN Node ID | M | | 9.2.2.3 | | – | |
+| >S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | | – | |
+| Time Synchronisation Assistance Information | O | | 9.2.3.153 | | YES | ignore |
+| QMC Configuration | O | | 9.2.3.156 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------|-------------|----------------------|
+| Information | | | | | | |
+| 5G ProSe Authorized | O | | 9.2.3.159 | | YES | ignore |
+| 5G ProSe PC5 QoS Parameters | O | | 9.2.3.160 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore |
+| Aerial UE Subscription Information | O | | 9.2.3.175 | | YES | ignore |
+| NR A2X Services Authorized | O | | 9.2.3.176 | | YES | ignore |
+| LTE A2X Services Authorized | O | | 9.2.3.177 | | YES | ignore |
+| A2X PC5 QoS Parameters | O | | 9.2.3.178 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore |
+| Mobile IAB Authorization Status | O | | 9.2.2.105 | | YES | ignore |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------|
+| maxnoofMDTPLMNs | PLMNs in the Management Based MDT PLMN list. Value is 16. |
+
+### 9.1.1.10 RETRIEVE UE CONTEXT FAILURE
+
+This message is sent by the old NG-RAN node to inform the new NG-RAN node that the Retrieve UE Context procedure has failed.
+
+Direction: old NG-RAN node → new NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|-------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node | YES | ignore |
+| Old NG-RAN node To New NG-RAN node Resume Container | O | | OCTET STRING | Includes either the <i>RRCRelease</i> message as defined in TS 38.331 [10], or the <i>RRCConnectionRelease</i> message as defined in TS 36.331 [14], encapsulated in a PDCP-C PDU. | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.1.11 XN-U ADDRESS INDICATION
+
+This message is either sent by the new NG-RAN node to transfer data forwarding information to the old NG-RAN
+
+node, or by the M-NG-RAN node to provide either data forwarding or Xn-U bearer address related information for SN terminated bearers to the S-NG-RAN node.
+
+Direction: new NG-RAN node → old NG-RAN node, M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------|----------|--------------------------|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node | YES | ignore |
+| Old NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the old NG-RAN node | YES | ignore |
+| <b>Xn-U Address Information per PDU Session Resources List</b> | | 1 | | This IE is ignored if the <i>CHO DC Indicator</i> IE is included and set to "coordination-only", or if the <i>CPC Data Forwarding indicator</i> IE is included and set to "coordination-only", or if the <i>MBS Data Forwarding Indicator</i> IE is included and set to "MBS-only". | YES | reject |
+| > <b>Xn-U Address Information per PDU Session Resources Item</b> | | 1..<maxno ofPDUSessions> | | | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>Data Forwarding Info from target NG-RAN node | O | | Data Forwarding Info from target NG-RAN node 9.2.1.16 | | – | |
+| >>Secondary Data Forwarding Info from target NG-RAN node List | O | | 9.2.1.31 | This IE would be present only when the target M-NG-RAN node decide to split a PDU session between MN and SN | YES | ignore |
+| >>PDU Session Resource Setup Complete Info – SN terminated | O | | 9.2.1.30 | | – | |
+| >>DRB IDs taken into use | O | | DRB List 9.2.1.29 | Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8]. | YES | reject |
+| >>Data Forwarding | O | | 9.2.1.35 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Info from target E-UTRAN node | | | | | | |
+| CHO MR-DC Indicator | O | | ENUMERATED (true, ..., coordination-only) | Indicating that the XN-U ADDRESS INDICATION message is for Conditional Handover, as specified in TS 37.340 [8]. | YES | reject |
+| CHO MR-DC Early Data Forwarding Indicator | O | | ENUMERATED (stop, ...) | | YES | ignore |
+| CPC Data Forwarding indicator | O | | ENUMERATED (triggered, early data transmission stop, ..., coordination-only) | Indicating that the XN-U ADDRESS INDICATION message is for a Conditional PSCell Change. | YES | reject |
+| MBS Data Forwarding Indicator | O | | ENUMERATED (MBS-only, ...) | Indicating that the XN-U ADDRESS INDICATION message is for MBS session data forwarding. | YES | ignore |
+| MBS Session Information Response List | O | | 9.2.1.38 | | YES | ignore |
+
+| Range bound | Explanation |
+|---------------------|-------------------------------------------|
+| maxnoofPDUSsessions | Maximum no. of PDU sessions. Value is 256 |
+
+### 9.1.1.12 HANDOVER SUCCESS
+
+This message is sent by the target NG-RAN node to the source NG-RAN node to indicate the successful access of the UE toward the target NG-RAN node.
+
+Direction: target NG-RAN node → source NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|---------------------------------|---------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Source NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the source NG-RAN node. | YES | reject |
+| Target NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the target NG-RAN node. | YES | reject |
+| Requested Target Cell ID | M | | Target Cell Global ID 9.2.3.25 | Target cell indicated in the corresponding Handover Preparation procedure | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Accessed PSCell ID | O | | NR CGI<br>9.2.2.7 | | YES | ignore |
+
+### 9.1.1.13 CONDITIONAL HANDOVER CANCEL
+
+This message is sent by the target NG-RAN node to the source NG-RAN node to cancel an already prepared conditional handover or an already prepared conditional reconfiguration.
+
+Direction: target NG-RAN node → source NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------------|----------|--------------------------------|------------------------------------|--------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Source NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the source NG-RAN node. | YES | reject |
+| Target NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the target NG-RAN node. | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| <b>Candidate Cells To Be Cancelled List</b> | | 0 .. <maxnoofCellsInCHO> | | | YES | reject |
+| >Target Cell ID | M | | Target Cell Global ID<br>9.2.3.25 | | – | |
+| <b>Conditional Reconfigurations To Be Cancelled List</b> | | 0..1 | | Includes CHO-only (with or without SCG) and CHO with candidate PSCell(s) | YES | reject |
+| >Conditional Reconfigurations To Be Cancelled Item | | 1 .. <maxnoofPSCellCandidates> | | | – | |
+| >>Target PCell ID | M | | Target Cell Global ID<br>9.2.3.25 | | – | |
+| >>Target PSCell ID | O | | NR CGI<br>9.2.2.7 | If this IE is absent, indicates CHO only (with or without SCG) | – | |
+
+| Range bound | Explanation |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofCellsInCHO | Maximum no. cells that can be prepared for a conditional handover. Value is 8. |
+| maxnoofPSCellCandidates | Maximum no. conditional reconfigurations that the UE can store. Value is 8.<br>The total of maxnoofCellsInCHO and maxnoofPSCellCandidates should not exceed 8. |
+
+### 9.1.1.14 EARLY STATUS TRANSFER
+
+This message is sent by the source NG-RAN node to the target NG-RAN node to transfer the COUNT value related to the forwarded downlink SDUs during DAPS Handover or Conditional Handover.
+
+For MR-DC with 5GC, the message is also used, during a Conditional Handover, to transfer from the source S-NG-RAN node to the source M-NG-RAN node, the COUNT value related to the forwarded downlink SDUs.
+
+For MR-DC with NG SCG, this message is also used, during a CPAC, to transfer from the source S-NG-RAN node to the M-NG-RAN node, and from the M-NG-RAN node to the target S-NG-RAN node, the COUNT value related to the forwarded downlink SDUs.
+
+Direction: source NG-RAN node → target NG-RAN node (DAPS Handover or Conditional Handover).
+
+Direction: source S-NG-RAN node → source M-NG-RAN node (Conditional Handover)
+
+Direction: M-NG-RAN node → S-NG-RAN node (Conditional PSCell Addition)
+
+Direction: source S-NG-RAN node → M-NG-RAN node (Conditional PSCell Change)
+
+Direction: M-NG-RAN node → target S-NG-RAN node (Conditional PSCell Change)
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|---------------------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Source NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated for handover at the source NG-RAN node. | YES | reject |
+| Target NG-RAN node<br>UE XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated for handover at the target NG-RAN node. | YES | reject |
+| CHOICE <i>Procedure Stage</i> | M | | | | YES | reject |
+| > <i>First DL COUNT</i> | | | | | | |
+| >>DRBs Subject To<br>Early Status<br>Transfer List | M | 1 | | | – | |
+| >>>DRBs Subject<br>To Early Status<br>Transfer Item | | 1 ..<br><maxnoof<br>DRBs> | | | – | |
+| >>>>DRB ID | M | | 9.2.3.33 | | – | |
+| >>>>CHOICE<br><i>First DL COUNT</i> | M | | | | – | |
+| >>>>>12 bits | | | | | | |
+| >>>>>>FIRST<br>DL COUNT<br>Value | M | | COUNT Value<br>for PDCP SN<br>Length 12<br>9.2.3.36 | PDCP-SN and Hyper frame number of the first DL SDU forwarded to the receiving NG-RAN node in case of 12 bit long PDCP-SN | – | |
+| >>>>>18 bits | | | | | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|---------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>>>>FIRST<br>DL COUNT<br>Value | M | | COUNT Value<br>for PDCP SN<br>Length 18<br>9.2.3.37 | PDCP-SN and Hyper frame number of the first DL SDU forwarded to the receiving NG-RAN node in case of 18 bit long PDCP-SN | – | |
+| >DL Discarding | | | | | | |
+| >>DRBs Subject To<br>DL Discarding List | M | 1 | | | – | |
+| >>>DRBs Subject<br>To DL Discarding<br>Item | | 1 ..<br><maxnoof<br>DRBs> | | | – | |
+| >>>>DRB ID | M | | 9.2.3.33 | | – | |
+| >>>>CHOICE DL<br>Discarding | M | | | | – | |
+| >>>>>12 bits | | | | | | |
+| >>>>>>DISCA<br>RD DL COUNT<br>Value | M | | COUNT Value<br>for PDCP SN<br>Length 12<br>9.2.3.36 | PDCP-SN and Hyper frame number for which the receiving NG-RAN node should discard forwarded DL SDUs associated with lower values in case of 12 bit long PDCP-SN | – | |
+| >>>>>18 bits | | | | | | |
+| >>>>>>DISCA<br>RD DL COUNT<br>Value | M | | COUNT Value<br>for PDCP SN<br>Length 18<br>9.2.3.37 | PDCP-SN and Hyper frame number for which the receiving NG-RAN node should discard forwarded DL SDUs associated with lower values in case of 18 bit long PDCP-SN | – | |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+
+### 9.1.1.15 RAN MULTICAST GROUP PAGING
+
+This message is sent by the NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub> to page UEs for a multicast session.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+
+| | | | | | | |
+|-----------------------------------------|---|------------------------------------------------------|---------------------------|---------------------------------------------------------------------|-----|--------|
+| MBS Session ID | M | | 9.2.3.146 | | YES | reject |
+| <b>UE Identity Index List</b> | | 1 | | | YES | reject |
+| > <b>UE Identity Index Item</b> | | 1 ..<br><maxnoof<br>UEIDIndi<br>cesforMB<br>SPaging> | | | – | |
+| >>CHOICE <i>UE Identity Index Value</i> | M | | | | – | |
+| >>> <i>Length-10</i> | | | | | | |
+| >>>>Index Length-10 | M | | BIT STRING (SIZE(10)) | Coded as specified in TS 38.304 [33]. | – | |
+| >>Paging DRX | O | | UE Specific DRX 9.2.3.143 | Includes the UE specific paging cycle as defined in TS 38.304 [33]. | – | |
+| Multicast RAN Paging Area | M | | RAN Paging Area 9.2.3.38 | | YES | reject |
+
+| Range bound | Explanation |
+|--------------------------------|-------------------------------------------------------------------------------|
+| maxnoofUEIDIndicesforMBSPaging | Maximum no. of UE Identity Indices for multicast group paging. Value is 4096. |
+
+### 9.1.1.16 RETRIEVE UE CONTEXT CONFIRM
+
+This message is sent by the new NG-RAN node to the old NG-RAN node to inform the old NG-RAN node whether the S-NG-RAN node associated with the old NG-RAN node for the UE that was indicated during UE context retrieval is kept or not by the new NG-RAN node during RRC resumption.
+
+In case of RACH based SDT without UE context relocation, the Retrieve UE Context Confirm procedure is also used to request termination of SDT session from the new NG-RAN node to the old NG-RAN node.
+
+Direction: new NG-RAN node → old NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|-------------------------------------------------------------------------|---------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Old NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the old NG-RAN node | YES | ignore |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node | YES | ignore |
+| UE Context Kept Indicator | O | | 9.2.3.68 | | YES | ignore |
+| SDT Termination Request | O | | ENUMERATED (radio link problem, normal, ..., Large SDT volume from BSR) | Indicate the reason of request for termination of an ongoing SDT session. | YES | ignore |
+
+### 9.1.1.17 PARTIAL UE CONTEXT TRANSFER
+
+This message is sent by the old NG-RAN node to transfer part of the UE Context to the new NG-RAN node.
+
+Direction: old NG-RAN node → new NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-------|---------------------------------|-----------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node. | YES | reject |
+| Old NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the old NG-RAN node. | YES | ignore |
+| Partial UE Context Information for SDT | M | | 9.2.3.164 | | YES | ignore |
+| Partial UE Context Information for Positioning | O | | 9.2.3.173 | | YES | ignore |
+
+### 9.1.1.18 PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE
+
+This message is sent by the new NG-RAN node to acknowledge the transferring part of the UE context from the old NG-RAN node. This message is also used to provide data forwarding related information for NR SDT.
+
+Direction: new NG-RAN node → old NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------------------|-----------------------------------------|------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the new NG-RAN node | YES | ignore |
+| Old NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the old NG-RAN node | YES | ignore |
+| <b>SDT Data Forwarding DRB List</b> | | 0..1 | | | YES | ignore |
+| >SDT Data Forwarding DRB Item | | 1..<maxno ofDRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>DL TNL Information | O | | UP Transport Layer Information 9.2.3.30 | | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| SRS Configuration | O | | OCTET STRING | Includes the SRS Configuration IE, as defined in TS 38.455 [49]. | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs. Value is 32. |
+
+### 9.1.1.19 PARTIAL UE CONTEXT TRANSFER FAILURE
+
+This message is sent by the new NG-RAN node to inform the old NG-RAN node that the Partial UE Context Transfer procedure has failed.
+
+Direction: new NG-RAN node → old NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|------------------------------------|-----------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| New NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the new NG-RAN node | YES | ignore |
+| Old NG-RAN node UE XnAP ID reference | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the old NG-RAN node. | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+## 9.1.2 Messages for Dual Connectivity Procedures
+
+### 9.1.2.1 S-NODE ADDITION REQUEST
+
+This message is sent by the M-NG-RAN node to the S-NG-RAN node to request the preparation of resources for dual connectivity operation for a specific UE.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| UE Security Capabilities | M | | 9.2.3.49 | | YES | reject |
+| S-NG-RAN node Security Key | M | | 9.2.3.51 | This IE is ignored if the <i>S-CPAC Request Information</i> IE is present in the <i>Conditional PSCell Addition Information Request</i> IE. | YES | reject |
+| S-NG-RAN node UE Aggregate Maximum Bit Rate | M | | UE Aggregate Maximum Bit Rate<br>9.2.3.17 | The UE Aggregate Maximum Bit Rate is split into M-NG-RAN node UE Aggregate Maximum Bit Rate and S-NG-RAN node UE Aggregate Maximum Bit Rate which are enforced by M-NG-RAN node and | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------|----------|----------------------------|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | S-NG-RAN node respectively. | | |
+| Selected PLMN | O | | PLMN Identity 9.2.2.4 | The selected PLMN of the SCG in the S-NG-RAN node. | YES | ignore |
+| Mobility Restriction List | O | | 9.2.3.53 | | YES | ignore |
+| Index to RAT/Frequency Selection Priority | O | | 9.2.3.23 | | YES | reject |
+| <b>PDU Session Resources To Be Added List</b> | | 1 | | | YES | reject |
+| > <b>PDU Session Resources To Be Added Item</b> | | 1 .. <maxnoof PDUSessions> | | NOTE: If neither the <i>PDU Session Resource Setup Info – SN terminated</i> IE nor the <i>PDU Session Resource Setup Info – MN terminated</i> IE is present in a <i>PDU Session Resources To Be Added Item</i> IE, abnormal conditions as specified in clause 8.3.1.4 apply. | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>S-NSSAI | M | | 9.2.3.21 | | – | |
+| >>S-NG-RAN node PDU Session Aggregate Maximum Bit Rate | O | | PDU Session Aggregate Maximum Bit Rate 9.2.3.69 | | – | |
+| >>PDU Session Resource Setup Info – SN terminated | O | | 9.2.1.5 | | – | |
+| >>PDU Session Resource Setup Info – MN terminated | O | | 9.2.1.7 | | – | |
+| M-NG-RAN node to S-NG-RAN node Container | M | | OCTET STRING | Includes the <i>CG-ConfigInfo</i> message as defined in subclause 11.2.2 of TS 38.331 [10] | YES | reject |
+| S-NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Expected UE Behaviour | O | | 9.2.3.81 | | YES | ignore |
+| Requested Split SRBs | O | | ENUMERATED (srb1, srb2, | Indicates that resources for Split | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|------------------|-------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | srb1&2, ...) | SRBs are requested. | | |
+| PCell ID | O | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | reject |
+| Desired Activity Notification Level | O | | 9.2.3.77 | | YES | ignore |
+| Available DRB IDs | C-ifSNterminated | | DRB List 9.2.1.29 | Indicates the list of DRB IDs that the S-NG-RAN node may use for SN-terminated bearers. | YES | reject |
+| S-NG-RAN node Maximum Integrity Protected Data Rate Uplink | O | | Bit Rate 9.2.3.4 | The S-NG-RAN node Maximum Integrity Protected Data Rate Uplink is a portion of the UE's Maximum Integrity Protected Data Rate in the Uplink, which is enforced by the S-NG-RAN node for the UE's SN terminated PDU sessions. If the S-NG-RAN node Maximum Integrity Protected Data Rate Downlink IE is not present, this IE applies to both UL and DL. | YES | reject |
+| S-NG-RAN node Maximum Integrity Protected Data Rate Downlink | O | | Bit Rate 9.2.3.4 | The S-NG-RAN node Maximum Integrity Protected Data Rate Downlink is a portion of the UE's Maximum Integrity Protected Data Rate in the Downlink, which is enforced by the S-NG-RAN node for the UE's SN terminated PDU sessions. | YES | reject |
+| Location Information at S-NODE reporting | O | | ENUMERATED (pscell, ...) | Indicates that the user's Location Information at S-NODE is to be provided. | YES | ignore |
+| MR-DC Resource Coordination Information | O | | 9.2.2.33 | Information used to coordinate resource utilisation | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------|----------|-------|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | between M-NG-RAN node and S-NG-RAN node. | | |
+| Masked IMEISV | O | | 9.2.3.32 | | YES | ignore |
+| NE-DC TDM Pattern | O | | 9.2.2.38 | | YES | ignore |
+| SN Addition Trigger Indication | O | | ENUMERATED (SN change, inter-MN HO, intra-MN HO, ...) | This IE indicates the trigger for S-NG-RAN node Addition Preparation procedure | YES | reject |
+| Trace Activation | O | | 9.2.3.55 | | YES | ignore |
+| Requested Fast MCG recovery via SRB3 | O | | ENUMERATED (true, ...) | Indicates that the resources for fast MCG recovery via SRB3 are requested. | YES | ignore |
+| UE Radio Capability ID | O | | 9.2.3.138 | | YES | reject |
+| Source NG-RAN Node ID | O | | Global NG-RAN Node ID 9.2.2.3 | The NG-RAN Node ID of the source NG-RAN node, or the source SN in e.g. NR-DC to NR-DC (conditional) handover. | YES | ignore |
+| Management Based MDT PLMN List | O | | MDT PLMN List 9.2.3.133 | | YES | ignore |
+| UE History Information | O | | 9.2.3.64 | | YES | ignore |
+| UE History Information from the UE | O | | 9.2.3.110 | | YES | ignore |
+| PSCell Change History | O | | ENUMERATED (reporting full history, ...) | | YES | ignore |
+| IAB Node Indication | O | | ENUMERATED (true, ...) | | YES | reject |
+| No PDU Session Indication | O | | ENUMERATED (true, ...) | This IE applies only if the UE is an IAB-MT. | YES | ignore |
+| <b>CHO Information SN Addition</b> | O | | | | YES | reject |
+| >Source M-NG-RAN node ID | M | | Global NG-RAN Node ID 9.2.2.3 | | – | |
+| >Source M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the source M-NG-RAN node | – | |
+| >Estimated Arrival Probability | O | | INTEGER (1..100) | | – | |
+| SCG Activation Request | O | | 9.2.3.154 | | YES | ignore |
+| <b>Conditional PSCell Addition Information Request</b> | O | | | | YES | reject |
+| >Maximum Number of PSCells To Prepare | M | | INTEGER (1..8, ...) | Indicates the maximum number of PSCells that the target SN may | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | prepare. | | |
+| >Estimated Arrival Probability | O | | INTEGER (1..100) | Indicates the arrival probability for the UE towards the candidate target SN. | – | |
+| >S-CPAC Request Information | O | | 9.2.3.192 | Indicates that SN addition is for S-CPAC preparation. | YES | reject |
+| >S-CPAC Reference Configuration Request | O | | ENUMERATED (request, ...) | Indicates that the reference configuration for S-CPAC is requested. | YES | ignore |
+| S-NG-RAN node UE Slice Maximum Bit Rate | O | | UE Slice Maximum Bit Rate List 9.2.3.167 | This IE indicates the S-NG-RAN node portion of the UE Slice Aggregate Maximum Bit Rate as specified in TS 23.501 [7] | YES | reject |
+| F1-terminating IAB-donor Indicator | O | | ENUMERATED (true, ...) | This IE applies only if the UE is an IAB-MT. | YES | reject |
+| Selected NID | O | | NID 9.2.2.65 | This IE, together with the <i>Selected PLMN</i> IE, indicates the SNPN proposed for the SCG to the S-NG-RAN node. | YES | ignore |
+| QMC Coordination Request | O | | 9.2.3.197 | | YES | ignore |
+| Source SN to Target SN QMC Information | O | | QMC Configuration Information 9.2.3.156 | This IE contains SN related QMC Configuration Information to be forwarded to the target S-NG-RAN node. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+
+| Condition | Explanation |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ifSNterminated | This IE shall be present if there is at least one <i>PDU Session Resource Setup Info – SN terminated</i> in the <i>PDU Session Resources To Be Added List</i> IE. |
+
+## 9.1.2.2 S-NODE ADDITION REQUEST ACKNOWLEDGE
+
+This message is sent by the S-NG-RAN node to confirm the M-NG-RAN node about the S-NG-RAN node addition
+
+preparation.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|----------------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| <b>PDU Session Resources Admitted To Be Added List</b> | | 1 | | | YES | ignore |
+| > <b>PDU Session Resources Admitted To Be Added Item</b> | | 1 .. <maxnoof PDUSessions> | | NOTE: If neither the <i>PDU Session Resource Setup Response Info – SN terminated</i> IE nor the <i>PDU Session Resource Setup Response Info – MN terminated</i> IE is present in a <i>PDU Session Resources Admitted to be Added Item</i> IE, abnormal conditions as specified in clause 8.3.1.4 apply. | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>PDU Session Resource Setup Response Info – SN terminated | O | | 9.2.1.6 | | – | |
+| >>PDU Session Resource Setup Response Info – MN terminated | O | | 9.2.1.8 | | – | |
+| <b>PDU Session Resources Not Admitted List</b> | O | | | | YES | ignore |
+| >PDU Session Resources Not Admitted List – SN terminated | O | | PDU Session Resources Not Admitted List 9.2.1.3 | | – | |
+| >PDU Session Resources Not Admitted List – MN terminated | O | | PDU Session Resources Not Admitted List 9.2.1.3 | | – | |
+| S-NG-RAN node to M-NG-RAN node Container | M | | OCTET STRING | Includes the <i>CG-Config</i> message or the <i>CG-</i> | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|--------------------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>CandidateList</i> message as defined in subclause 11.2.2 of TS 38.331 [10]. | | |
+| Admitted Split SRBs | O | | ENUMERATED (srb1, srb2, srb1&2, ...) | Indicates admitted SRBs | YES | reject |
+| RRC Config Indication | O | | 9.2.3.72 | | YES | reject |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Location Information at S-NODE | O | | Target Cell Global ID 9.2.3.25 | Contains information to support localisation of the UE | YES | ignore |
+| MR-DC Resource Coordination Information | O | | 9.2.2.33 | Information used to coordinate resource utilisation between M-NG-RAN node and S-NG-RAN node. | YES | ignore |
+| Available fast MCG recovery via SRB3 | O | | ENUMERATED (true, ...) | Indicates the fast MCG recovery via SRB3 is enabled. | YES | ignore |
+| Direct Forwarding Path Availability | O | | ENUMERATED (direct path available, ...) | Indicates direct forwarding path is available between the target S-NG-RAN node and source NG-RAN node for intra-system handover, or between the target S-NG-RAN node and the source SN in e.g. NR-DC to NR-DC (conditional) handover. | YES | ignore |
+| SCG Activation Status | O | | 9.2.3.155 | | YES | ignore |
+| <b>Conditional PSCell Addition Information Acknowledge</b> | O | | | | YES | ignore |
+| >Candidate PSCell List | | 1 | | | – | |
+| >>Candidate PSCell Item | | 1 .. <maxnoof PSCellCandidate> | | | – | |
+| >>>PSCell ID | M | | NR CGI 9.2.2.7 | | – | |
+| >Candidate PSCell with Other Information List | | 0..1 | | | YES | reject |
+| >>Candidate PSCell with Other Information Item | | 1 .. <maxnoof PSCellCandidate> | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------------------------|----------|-------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>PSCell ID | M | | NR CGI<br>9.2.2.7 | | – | |
+| >>>S-CPAC<br>Complete<br>Configuration<br>Indicator | O | | Complete<br>Configuration<br>Indicator<br>9.2.3.194 | | – | |
+| SN Mobility Information | O | | BIT STRING<br>(SIZE (32)) | Information related to PSCell change; T-SN provides it in order to enable later analysis of the conditions that led to wrong PSCell change. | YES | ignore |
+| QMC Coordination<br>Response | O | | 9.2.3.198 | | YES | ignore |
+| <b>CHO Information SN<br/>Addition Acknowledge</b> | O | | | | YES | ignore |
+| >PCell ID | O | | Global NG-RAN<br>Cell Identity<br>9.2.2.27 | PCell indicated in the corresponding S-NODE ADDITION REQUEST message. | – | |
+| Direct Forwarding Path<br>Availability with source<br>M-NG-RAN node | O | | ENUMERATED<br>(direct path<br>available, ...) | Indicates direct forwarding path is available between the target S-NG-RAN node and source M-NG-RAN node. | YES | ignore |
+
+| Range bound | Explanation |
+|------------------------|---------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofPSCellCandidate | Maximum no. of PSCell candidate. Value is 8 |
+
+### 9.1.2.3 S-NODE ADDITION REQUEST REJECT
+
+This message is sent by the S-NG-RAN node to inform the M-NG-RAN node that the S-NG-RAN node Addition Preparation has failed.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------|-------|---------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE<br>XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE<br>XnAP ID | M | | NG-RAN node<br>UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+| | | | | | | |
+|----------|---|--|--------------------------------------|----------------------------------------------------------------------|-----|--------|
+| PCell ID | O | | Global NG-RAN Cell Identity 9.2.2.27 | PCell indicated in the corresponding S-NODE ADDITION REQUEST message | YES | ignore |
+|----------|---|--|--------------------------------------|----------------------------------------------------------------------|-----|--------|
+
+### 9.1.2.4 S-NODE RECONFIGURATION COMPLETE
+
+This message is sent by the M-NG-RAN node to the S-NG-RAN node to indicate whether the configuration requested by the S-NG-RAN node was applied by the UE.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|-------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| <b>Response Information</b> | M | | | | YES | ignore |
+| >CHOICE <i>Response Type</i> | M | | | | – | |
+| >>Configuration successfully applied | | | | | – | |
+| >>>M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>RRCReconfigurationComplete</i> message as defined in subclause 6.2.2 of TS 38.331 [10] or the <i>RRRConnectionReconfigurationComplete</i> message as defined in subclause 6.2.2 of TS 36.331 [14]. | – | |
+| >>Configuration rejected by the M-NG-RAN node | | | | | – | |
+| >>>Cause | M | | 9.2.3.2 | | – | |
+| >>>M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>CG-ConfigInfo</i> message as defined in as defined in subclause 11.2.2 of TS 38.331 [10]. | – | |
+
+### 9.1.2.5 S-NODE MODIFICATION REQUEST
+
+This message is sent by the M-NG-RAN node to the S-NG-RAN node to either request the preparation to modify S-NG-RAN node resources for a specific UE, or to query for the current SCG configuration, or to provide the S-RLF-related information to the S-NG-RAN node.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|----------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| PDCP Change Indication | O | | 9.2.3.74 | | YES | ignore |
+| Selected PLMN | O | | PLMN Identity<br>9.2.2.4 | The selected PLMN of the SCG in the S-NG-RAN node. | YES | ignore |
+| Mobility Restriction List | O | | 9.2.3.53 | | YES | ignore |
+| SCG Configuration Query | O | | 9.2.3.27 | | YES | ignore |
+| <b>UE Context Information</b> | | 0..1 | | | YES | reject |
+| >UE Security Capabilities | O | | 9.2.3.49 | | – | |
+| >S-NG-RAN node Security Key | O | | 9.2.3.51 | | – | |
+| >S-NG-RAN node UE Aggregate Maximum Bit Rate | O | | UE Aggregate Maximum Bit Rate<br>9.2.3.17 | | – | |
+| >Index to RAT/Frequency Selection Priority | O | | 9.2.3.23 | | – | |
+| >Lower Layer presence status change | O | | 9.2.3.60 | | – | |
+| >PDU Session Resources To Be Added List | | 0..1 | | | – | |
+| >>PDU Session Resources To Be Added Item | | 1 ..<br><maxnoof<br>PDUSessions> | | NOTE: If neither the <i>PDU Session Resource Setup Info – SN terminated</i> IE nor the <i>PDU Session Resource Setup Info – MN terminated</i> IE is present in a <i>PDU Session Resources To Be Added Item</i> IE, | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------------|----------|-----------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | abnormal conditions as specified in clause 8.3.3.4 apply. | | |
+| >>>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>>S-NSSAI | M | | 9.2.3.21 | | – | |
+| >>>S-NG-RAN node PDU Session Aggregate Maximum Bit Rate | O | | PDU Session Aggregate Maximum Bit Rate 9.2.3.69 | | – | |
+| >>>PDU Session Resource Setup Info – SN terminated | O | | 9.2.1.5 | | – | |
+| >>>PDU Session Resource Setup Info – MN terminated | O | | 9.2.1.7 | | – | |
+| >>>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour 9.2.3.82 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore |
+| <b>>PDU Session Resources To Be Modified List</b> | | 0..1 | | | – | |
+| <b>>>PDU Session Resources To Be Modified Item</b> | | 1 .. <maxnoof PDU Sessions> | | NOTE: If neither the <i>PDU Session Resource Modification Info – SN terminated</i> IE nor the <i>PDU Session Resource Modification Info – MN terminated</i> IE is present in a <i>PDU Session Resources To Be Modified Item</i> IE, abnormal conditions as specified in clause 8.3.3.4 apply. | – | |
+| >>>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>>S-NG-RAN node PDU Session Aggregate Maximum Bit Rate | O | | PDU Session Aggregate Maximum Bit Rate 9.2.3.69 | | – | |
+| >>>PDU Session Resource Modification Info – SN terminated | O | | 9.2.1.9 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|-------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>PDU Session Resource Modification Info – MN terminated | O | | 9.2.1.11 | | – | |
+| >>>S-NSSAI | O | | 9.2.3.21 | | YES | reject |
+| >>>PDU Session Expected UE Activity Behaviour | O | | Expected UE Activity Behaviour 9.2.3.82 | Expected UE Activity Behaviour for the PDU Session. | YES | ignore |
+| >PDU Session Resources To Be Released List | O | | PDU session List with Cause 9.2.1.26 | | – | |
+| M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>CG-ConfigInfo</i> message as defined in subclause 11.2.2. of TS 38.331 [10]. | YES | ignore |
+| Requested Split SRBs | O | | ENUMERATED (srb1, srb2, srb1&2, ...) | Indicates that resources for Split SRBs are requested. | YES | ignore |
+| Requested Split SRBs release | O | | ENUMERATED (srb1, srb2, srb1&2, ...) | Indicates that resources for Split SRBs are requested to be released. | YES | ignore |
+| Desired Activity Notification Level | O | | 9.2.3.77 | | YES | ignore |
+| Additional DRB IDs | O | | DRB List 9.2.1.29 | Indicates additional list of DRB IDs that the S-NG-RAN node may use for SN-terminated bearers. | YES | reject |
+| S-NG-RAN node Maximum Integrity Protected Data Rate Uplink | O | | Bit Rate 9.2.3.4 | The S-NG-RAN node Maximum Integrity Protected Data Rate Uplink is a portion of the UE's Maximum Integrity Protected Data Rate in the Uplink, which is enforced by the S-NG-RAN node for the UE's SN terminated PDU sessions. If the <i>S-NG-RAN node Maximum Integrity Protected Data Rate Downlink</i> IE is not present, this IE applies to both UL and DL. | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|----------|-------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| S-NG-RAN node Maximum Integrity Protected Data Rate Downlink | O | | Bit Rate 9.2.3.4 | The S-NG-RAN node Maximum Integrity Protected Data Rate Downlink is a portion of the UE's Maximum Integrity Protected Data Rate in the Downlink, which is enforced by the S-NG-RAN node for the UE's SN terminated PDU sessions. | YES | reject |
+| Location Information at S-NODE reporting | O | | ENUMERATED (pscell, ...) | Indicates that the user's Location Information at S-NODE is to be provided. | YES | ignore |
+| MR-DC Resource Coordination Information | O | | 9.2.2.33 | Information used to coordinate resource utilisation between M-NG-RAN node and S-NG-RAN node. | YES | ignore |
+| PCell ID | O | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | reject |
+| NE-DC TDM Pattern | O | | 9.2.2.38 | | YES | ignore |
+| Requested Fast MCG recovery via SRB3 | O | | ENUMERATED (true, ...) | Indicates that the resources for fast MCG recovery via SRB3 are requested. | YES | ignore |
+| Requested Fast MCG recovery via SRB3 Release | O | | ENUMERATED (true, ...) | Indicates that resources for fast MCG recovery via SRB3 are requested to be released. | YES | ignore |
+| SN triggered | O | | ENUMERATED (TRUE ...) | | YES | ignore |
+| Target Node ID | O | | Global NG-RAN Node ID 9.2.2.3 | Indicates the target node ID of the handover procedure decided by the M-NG-RAN node. | YES | ignore |
+| PSCell History Information Retrieve | O | | ENUMERATED (query, ...) | Indicates that the SN UE history information is requested. | YES | ignore |
+| UE History Information from the UE | O | | 9.2.3.110 | | YES | ignore |
+| <b>CHO Information SN Modification</b> | O | | | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------------------------|----------|--------------------------------|--------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >Conditional Reconfiguration | M | | ENUMERATED (intra-MN-CHO, ...) | | – | |
+| >Estimated Arrival Probability | O | | INTEGER (1..100) | | – | |
+| SCG Activation Request | O | | 9.2.3.154 | | YES | ignore |
+| <b>Conditional PSCell Addition Information Modification Request</b> | O | | | This IE may be sent to the target SN. | YES | ignore |
+| >Maximum Number of PSCells To Prepare | O | | INTEGER (1..8, ...) | Indicates the maximum number of PSCells that the target SN may prepare. | – | |
+| >Estimated Arrival Probability | O | | INTEGER (1..100) | Indicates the arrival probability for the UE towards the candidate target SN. | | |
+| >S-CPAC Request Information | O | | 9.2.3.192 | Indicates that SN modification is for S-CPAC preparation or modification. | YES | reject |
+| >S-CPAC Reference Configuration Request | O | | ENUMERATED (request, ...) | Indicates that the reference configuration for S-CPAC is requested. | YES | ignore |
+| >S-CPAC Inter-SN Execution Notification | O | | ENUMERATED (true, ...) | Indicates that inter-SN S-CPAC was executed. | YES | reject |
+| <b>Conditional PSCell Change Information Update</b> | O | | | This IE may be sent to the source SN in SN-initiated inter-SN CPC, or sent to a candidate SN in S-CPAC. | YES | ignore |
+| >Multiple Target S-NG-RAN Node List | | 1 | | | – | |
+| >>Multiple Target S-NG-RAN Node Item | | 1 .. <maxnoof TargetSN s> | | | – | |
+| >>>Target S-NG-RAN node ID | M | | Global NG-RAN Node ID 9.2.2.3 | | – | |
+| >>>Candidate PSCell List | | 1 | | | – | |
+| >>>>Candidate PSCell Item | | 1 .. <maxnoof PSCellCandidate> | | | – | |
+| >>>>>PSCell ID | M | | NR CGI 9.2.2.7 | | – | |
+| S-NG-RAN node UE Slice Maximum Bit Rate | O | | UE Slice Maximum Bit | This IE indicates the S-NG-RAN | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | Rate List<br>9.2.3.167 | node portion of the UE Slice Aggregate Maximum Bit Rate as specified in TS 23.501 [7] | | |
+| Management Based MDT PLMN Modification List | O | | MDT PLMN Modification List<br>9.2.3.169 | | YES | ignore |
+| Selected NID | O | | NID<br>9.2.2.65 | This IE, together with the <i>Selected PLMN</i> IE, indicates the SNPN proposed for the SCG to the S-NG-RAN node. | YES | ignore |
+| QMC Coordination Request | O | | 9.2.3.197 | | YES | ignore |
+| Source SN to Target SN QMC Information Inquiry | O | | ENUMERATED<br>(true, ...) | | YES | ignore |
+
+| Range bound | Explanation |
+|------------------------|------------------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofPSCellCandidate | Maximum no. of PSCell candidates. Value is 8 |
+| maxnoofTargetSNs | Maximum no. of the target S-NG-RAN nodes. Value is 8 |
+
+### 9.1.2.6 S-NODE MODIFICATION REQUEST ACKNOWLEDGE
+
+This message is sent by the S-NG-RAN node to confirm the M-NG-RAN node's request to modify the S-NG-RAN node resources for a specific UE.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------------|----------|-----------------------------|------------------------------------|------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| <b>PDU Session Resources Admitted List</b> | | 0..1 | | | YES | ignore |
+| > <b>PDU Session Resources Admitted To Be Added List</b> | | 0..1 | | | – | |
+| >> <b>PDU Session Resources Admitted To Be Added Item</b> | | 1..<br><maxnoofPDUSessions> | | NOTE: If neither the <i>PDU Session Resource Setup Response Info</i> – | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------------|----------|----------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>SN terminated IE nor the PDU Session Resource Setup Response Info – MN terminated IE is present in a PDU Session Resources Admitted To Be Added Item IE, abnormal conditions as specified in clause 8.3.3.4 apply.</i> | | |
+| >>>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>>PDU Session Resource Setup Response Info – SN terminated | O | | 9.2.1.6 | | – | |
+| >>>PDU Session Resource Setup Response Info – MN terminated | O | | 9.2.1.8 | | – | |
+| >PDU Session Resources Admitted To Be Modified List | | 0..1 | | | – | |
+| >>PDU Session Resources Admitted To Be Modified Item | | 1 .. <maxnoof PDUSessions> | | NOTE: If neither the <i>PDU Session Resource Modification Response Info – SN terminated IE nor the PDU Session Resource Modification Response Info – MN terminated IE is present in a PDU Session Resources Admitted To Be Modified Item IE, abnormal conditions as specified in clause 8.3.3.4 apply.</i> | – | |
+| >>>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>>PDU Session Resource Modification Response Info – SN terminated | O | | 9.2.1.10 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------------------------|----------|-------|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>PDU Session Resource Modification Response Info – MN terminated | O | | 9.2.1.12 | | – | |
+| <b>>PDU Session Resources Admitted To Be Released List</b> | | 0..1 | | | – | |
+| >>PDU Session Resources admitted to be released List – SN terminated | O | | PDU session List with data forwarding request info 9.2.1.24 | | – | |
+| >>PDU Session Resources admitted to be released List – MN terminated | O | | PDU session List with data Cause 9.2.1.26 | | – | |
+| <b>PDU Session Resources Not Admitted to be Added List</b> | O | | PDU session List 9.2.1.27 | | YES | ignore |
+| S-NG-RAN node to M-NG-RAN node Container | O | | OCTET STRING | Includes the <i>CG-Config</i> message or the <i>CG-CandidateList</i> message as defined in subclause 11.2.2 of TS 38.331 [10]. | YES | ignore |
+| Admitted Split SRBs | O | | ENUMERATED (srb1, srb2, srb1&2, ...) | Indicates admitted SRBs | YES | ignore |
+| Admitted Split SRBs release | O | | ENUMERATED (srb1, srb2, srb1&2, ...) | Indicates admitted SRBs release | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Location Information at S-NODE | O | | Target Cell Global ID 9.2.3.25 | Contains information to support localisation of the UE | YES | ignore |
+| MR-DC Resource Coordination Information | O | | 9.2.2.33 | Information used to coordinate resource utilisation between M-NG-RAN node and S-NG-RAN node. | YES | ignore |
+| <b>PDU Session Resources with Data Forwarding List</b> | | 0..1 | | | YES | ignore |
+| >PDU Session Resources with Data Forwarding List – SN terminated | M | | PDU session List with data forwarding request info 9.2.1.24 | | – | |
+| RRC Config Indication | O | | 9.2.3.72 | | YES | reject |
+| Available fast MCG | O | | ENUMERATED | Indicates the fast | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------------------|----------|-------------------------------|--------------------------------------------|------------------------------------------------------------------------------------------|-------------|----------------------|
+| recovery via SRB3 | | | (true, ...) | MCG recovery via SRB3 is enabled. | | |
+| Release fast MCG recovery via SRB3 | O | | ENUMERATED (true, ...) | Indicates the fast MCG recovery via SRB3 is released. | YES | ignore |
+| Direct Forwarding Path Availability | O | | ENUMERATED (direct path available,...) | Indicates direct path is available between the S-NG-RAN node and the target NG-RAN node. | YES | ignore |
+| SCG UE History Information | O | | 9.2.3.151 | | YES | ignore |
+| SCG Activation Status | O | | 9.2.3.155 | | YES | ignore |
+| <b>Conditional PSCell Addition Information Modification Acknowledge</b> | O | | | This IE may be sent from the target SN. | YES | ignore |
+| >Candidate PSCell List | | 1 | | Ignored, if the <i>Candidate PSCell with Other Information List</i> IE is included. | – | |
+| >>Candidate PSCell Item | | 1 .. <maxnoofPSCellCandidate> | | | – | |
+| >>>PSCell ID | M | | NR CGI 9.2.2.7 | | – | |
+| >Candidate PSCell with Other Information List | | 0..1 | | | YES | reject |
+| >>Candidate PSCell with Other Information Item | | 1 .. <maxnoofPSCellCandidate> | | | – | |
+| >>>PSCell ID | M | | NR CGI 9.2.2.7 | | – | |
+| >>>S-CPAC Complete Configuration Indicator | O | | Complete Configuration Indicator 9.2.3.194 | | – | |
+| QMC Coordination Response | O | | 9.2.3.198 | | YES | ignore |
+| Source SN to Target SN QMC Information | O | | QMC Configuration Information 9.2.3.156 | | YES | ignore |
+
+| Range bound | Explanation |
+|------------------------|----------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofPSCellCandidate | Maximum no. of PSCell candidates. Value is 8 |
+
+## 9.1.2.7 S-NODE MODIFICATION REQUEST REJECT
+
+This message is sent by the S-NG-RAN node to inform the M-NG-RAN node that the M-NG-RAN node initiated S-NG-RAN node Modification Preparation has failed.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.2.8 S-NODE MODIFICATION REQUIRED
+
+This message is sent by the S-NG-RAN node to the M-NG-RAN node to request the modification of S-NG-RAN node resources for a specific UE.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|---------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| PDCP Change Indication | O | | 9.2.3.74 | | YES | ignore |
+| <b>PDU Session Resources To Be Modified List</b> | | 0..1 | | | YES | ignore |
+| > <b>PDU Session Resources To Be Modified Item</b> | | 1..<br><maxnoof<br>PDUSessions> | | NOTE: If neither the <i>PDU Session Resource Modification Required Info – SN terminated</i> IE nor the <i>PDU Session Resource Modification Required Info – MN terminated</i> IE is present in a <i>PDU Session Resources To Be Modified Item</i> IE, abnormal conditions as | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------------|----------|----------------------------|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | specified in clause 8.3.4.4 apply. | | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>PDU Session Resource Modification Required Info – SN terminated | O | | 9.2.1.20 | | – | |
+| >>PDU Session Resource Modification Required Info – MN terminated | O | | 9.2.1.22 | | – | |
+| <b>PDU Session Resources To Be Released List</b> | | 0..1 | | | YES | ignore |
+| >PDU Session Resources To Be Released Item | | 1 .. <maxnoof PDUSessions> | | | – | |
+| >PDU sessions to be released List – SN terminated | O | | PDU session List with data forwarding request info 9.2.1.24 | | – | |
+| >PDU sessions to be released List – MN terminated | O | | PDU session List with Cause 9.2.1.26 | | – | |
+| S-NG-RAN node to M-NG-RAN node Container | O | | OCTET STRING | Includes the CG-Config message or the CG-CandidateList message as defined in subclause 11.2.2 of TS 38.331 [10]. | YES | ignore |
+| Spare DRB IDs | O | | DRB List 9.2.1.29 | Indicates the list of unnecessary DRB IDs that had been used by the S-NG-RAN node. | YES | ignore |
+| Required Number of DRB IDs | O | | Number of DRBs 9.2.3.78 | Indicates the number of DRB IDs that the S-NG-RAN node requests more. | YES | ignore |
+| Location Information at S-NODE | O | | Target Cell Global ID 9.2.3.25 | Contains information to support localisation of the UE | YES | ignore |
+| MR-DC Resource Coordination Information | O | | 9.2.2.33 | Information used to coordinate resource utilisation between M-NG-RAN node and S-NG-RAN node. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-------------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RRC Config Indication | O | | 9.2.3.72 | | YES | reject |
+| Available fast MCG recovery via SRB3 | O | | ENUMERATED (true, ...) | This IE is not used in this version of the specification. | YES | ignore |
+| Release fast MCG recovery via SRB3 | O | | ENUMERATED (true, ...) | This IE is not used in this version of the specification. | YES | ignore |
+| SCG Indicator | O | | ENUMERATED (released,...) | | YES | ignore |
+| SCG UE History Information | O | | 9.2.3.151 | | YES | ignore |
+| SCG Activation Request | O | | 9.2.3.154 | | YES | ignore |
+| <b>CPAC Information Required</b> | O | | | This IE may be sent from the target SN. | YES | ignore |
+| <b>>Candidate PSCell List</b> | | 1 | | Indicates the full list of candidate PSCells prepared at the target S-NG-RAN node. | – | |
+| <b>>>Candidate PSCell Item</b> | | 1 .. <maxnoofPSCellCandidate> | | | – | |
+| <b>>>>PSCell ID</b> | M | | NR CGI 9.2.2.7 | | – | |
+| SCG Reconfiguration Notification | O | | ENUMERATED (executed, ..., executed-deleted, deleted) | | YES | ignore |
+| SPR availability in UE | O | | ENUMERATED (spr-available, ...) | Indicates if an SPR is available in the UE. | YES | ignore |
+| QMC Coordination Request | O | | 9.2.3.197 | | YES | ignore |
+| Source SN to Target SN QMC Information | O | | QMC Configuration Information 9.2.3.156 | This IE contains SN related QMC Configuration Information to be forwarded to the target S-NG-RAN node. | YES | ignore |
+
+| Range bound | Explanation |
+|------------------------|---------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofPSCellCandidate | Maximum no. of PSCell candidate. Value is 8 |
+
+### 9.1.2.9 S-NODE MODIFICATION CONFIRM
+
+This message is sent by the M-NG-RAN node to inform the S-NG-RAN node about the successful modification.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------|----------|----------------------------|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| <b>PDU sessions Admitted To Be Modified List</b> | | 0..1 | | | YES | ignore |
+| >PDU sessions Admitted To Be Modified Item | | 1 .. <maxnoof PDUsessions> | | NOTE: If neither the <i>PDU Session Resource Modification Confirm Info – SN terminated</i> IE nor the <i>PDU Session Resource Modification Confirm Info – MN terminated</i> IE is present in a <i>PDU Session Resources Admitted To Be Modified Item</i> IE, abnormal conditions as specified in clause 8.3.4.4 apply. | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>PDU Session Resource Modification Confirm Info – SN terminated | O | | 9.2.1.21 | | – | |
+| >>PDU Session Resource Modification Confirm Info – MN terminated | O | | 9.2.1.23 | | – | |
+| <b>PDU sessions Released List</b> | | 0..1 | | | YES | ignore |
+| >PDU sessions released List – SN terminated | O | | PDU Session List with data forwarding info from the target node<br>9.2.1.25 | | – | |
+| >PDU sessions released List – MN terminated | O | | PDU session List<br>9.2.1.27 | | – | |
+| M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>RRCReconfigurationComplete</i> message as defined in | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | subclause 6.2.2 of TS 38.331 [10] or the <i>RRCConnectionReconfigurationComplete</i> message as defined in subclause 6.2.2 of TS 36.331 [14]. | | |
+| Additional DRB IDs | O | | DRB List 9.2.1.29 | Indicates additional list of DRB IDs that the S-NG-RAN node may use for SN-terminated bearers. | YES | reject |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| MR-DC Resource Coordination Information | O | | 9.2.2.33 | Information used to coordinate resource utilisation between M-NG-RAN node and S-NG-RAN node. | YES | ignore |
+| QMC Coordination Response | O | | 9.2.3.198 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+
+### 9.1.2.10 S-NODE MODIFICATION REFUSE
+
+This message is sent by the M-NG-RAN node to inform the S-NG-RAN node that the S-NG-RAN node initiated S-NG-RAN node Modification has failed.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------|---------------------------------|---------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>CG-ConfigInfo</i> message as defined in subclause 11.2.2 of TS 38.331 [10]. | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.2.11 S-NODE CHANGE REQUIRED
+
+This message is sent by the S-NG-RAN node to the M-NG-RAN node to trigger the change of the S-NG-RAN node.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Target S-NG-RAN node ID | M | | Global NG-RAN Node ID<br>9.2.2.3 | This IE shall be ignored if the <i>Conditional PSCell Change Information Required</i> IE is present. | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| <b>PDU Session SN Change Required List</b> | | 0..1 | | | YES | ignore |
+| >PDU Session SN Change Required Item | | 1..<br><maxnoof<br>PDUsessi<br>ons> | | NOTE: If the <i>PDU Session Resource Change Required Info – SN terminated</i> IE is not present in a <i>PDU Session SN Change Required Item</i> IE, abnormal conditions as specified in clause 8.3.5.4 apply. | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>PDU Session Resource Change Required Info – SN terminated | O | | 9.2.1.18 | | – | |
+| S-NG-RAN node to M-NG-RAN node Container | M | | OCTET STRING | Includes the <i>CG-Config</i> message as defined in subclause 11.2.2 of TS 38.331 [10]. This IE shall be ignored if the <i>Conditional PSCell Change Information Required</i> IE is present. | YES | reject |
+| SCG UE History Information | O | | 9.2.3.151 | | YES | ignore |
+| SN Mobility Information | O | | BIT STRING (SIZE (32)) | Information related to PSCell change; S-NG-RAN node | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|--------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | provides it in order to enable later analysis of the conditions that led to wrong PSCell change. | | |
+| Source PSCell ID | O | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | ignore |
+| Conditional PSCell Change Information Required | O | | | | YES | ignore |
+| >Multiple Target S-NG-RAN Node List | | 1 | | | – | |
+| >>Multiple Target S-NG-RAN Node Item | | 1 .. <maxnoof TargetSNs> | | | – | |
+| >>>Target S-NG-RAN node ID | M | | Global NG-RAN Node ID 9.2.2.3 | | – | |
+| >>>CPC Indicator | M | | ENUMERATED (CPC-initiation, CPC-modification, CPC-cancellation, ...) | | – | |
+| >>>Maximum Number of PSCells To Prepare | M | | INTEGER (1..8, ...) | Indicates the maximum number of PSCells that the target SN may prepare. | – | |
+| >>>Estimated Arrival Probability | O | | INTEGER (1..100) | Indicates the arrival probability for the UE towards the candidate target SN. | – | |
+| >>>S-NG-RAN node to M-NG-RAN node Container | M | | OCTET STRING | Includes the CG-Config message as defined in subclause 11.2.2 of TS 38.331 [10]. | – | |
+| >S-CPAC Request | O | | ENUMERATED (initiation, ...) | Indicates that SN change is for S-CPAC preparation. | YES | reject |
+| Source SN to Target SN QMC Information | O | | 9.2.3.156 | This IE contains SN related QMC Configuration Information to be forwarded to the target S-NG-RAN node. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|------------------------------------------------------|
+| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofTargetSNs | Maximum no. of the target S-NG-RAN nodes. Value is 8 |
+
+### 9.1.2.12 S-NODE CHANGE CONFIRM
+
+This message is sent by the M-NG-RAN node to inform the S-NG-RAN node that the preparation of the S-NG-RAN node initiated S-NG-RAN node change was successful.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------------------------------|----------|----------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| <b>PDU Session SN Change Confirm List</b> | | 0..1 | | | YES | ignore |
+| > <b>PDU Session SN Change Confirm Item</b> | | 1 .. <maxnoof PDUsessions> | | NOTE: If the <i>PDU Session Resource Change Confirm Info – SN terminated</i> IE is not present in a <i>PDU Session SN Change Confirm Item</i> IE, abnormal conditions as specified in clause 8.3.5.4 apply. | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>PDU Session Resource Change Confirm Info – SN terminated | O | | 9.2.1.19 | | – | |
+| >>Additional List of PDU Session Resource Change Confirm Info – SN Terminated | | 0..1 | | This IE would be present only if multiple candidate target SNs are prepared in case of SN initiated inter-SN CPC. | YES | ignore |
+| >>>Additional list of PDU Session Resource Change Confirm Info – SN Terminated-Item | | 1 .. <maxnoof TargetSNsMinusOne> | | | – | |
+| >>>>PDU Session Resource Change Confirm Info – SN terminated | M | | 9.2.1.19 | | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| <b>Conditional PSCell Change Information Confirm</b> | O | | | | YES | ignore |
+| > <b>Multiple Target S-NG-RAN Node List</b> | | 1 | | | – | |
+| >>Multiple Target | | 1 .. | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|--------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>S-NG-RAN Node Item</b> | | <maxnoof TargetSNs> | | | | |
+| >>>Target S-NG-RAN node ID | M | | Global NG-RAN Node ID 9.2.2.3 | | – | |
+| >>>>Candidate PSCell List | | 1 | | | – | |
+| >>>>>Candidate PSCell Item | | 1 .. <maxnoof PSCellCandidate> | | | – | |
+| >>>>>PSCell ID | M | | NR CGI 9.2.2.7 | | – | |
+| M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>RRCReconfigurationComplete</i> message as defined in subclause 6.2.2 of TS 38.331 [10]. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------------|--------------------------------------------------------------|
+| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofTargetSNs | Maximum no. of the target S-NG-RAN nodes. Value is 8 |
+| maxnoofPSCellCandidate | Maximum no. of PSCell candidate. Value is 8 |
+| maxnoofTargetSNsMinusOne | Maximum no. of the target S-NG-RAN nodes minus 1. Value is 7 |
+
+### 9.1.2.13 S-NODE CHANGE REFUSE
+
+This message is sent by the M-NG-RAN node to inform the S-NG-RAN node that the preparation of the S-NG-RAN node initiated S-NG-RAN node change has failed.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.2.14 S-NODE RELEASE REQUEST
+
+This message is sent by the M-NG-RAN node to the S-NG-RAN node to request the release of resources.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-------|-----------------------------------------|------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| PDU Session Resources To Be Released List | O | | PDU session List with Cause<br>9.2.1.26 | | YES | ignore |
+| UE Context Kept Indicator | O | | 9.2.3.68 | | YES | ignore |
+| M-NG-RAN node to S-NG-RAN node Container | O | | OCTET STRING | Includes the <i>CG-ConfigInfo</i> message as defined in subclause 11.2.2 of TS 38.331 [10]. | YES | ignore |
+| DRBs transferred to MN | O | | DRB List<br>9.2.1.29 | Indicates that the target M-NG-RAN node reconfigured the listed DRBs as MN-terminated bearers. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+
+### 9.1.2.15 S-NODE RELEASE REQUEST ACKNOWLEDGE
+
+This message is sent by the S-NG-RAN node to the M-NG-RAN node to confirm the request to release S-NG-RAN node resources.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|-------|----------------------------------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| PDU sessions To Be Released List | | 0..1 | | | YES | ignore |
+| >PDU Session Resources To Be Released List – SN terminated | O | | PDU Session List with data forwarding request info<br>9.2.1.24 | | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| SCG UE History | O | | 9.2.3.151 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Information | | | | | | |
+| SN Mobility Information | O | | BIT STRING (SIZE (32)) | Information related to PSCell change; T-SN provides it in order to enable later analysis of the conditions that led to wrong PSCell change. | YES | ignore |
+
+### 9.1.2.16 S-NODE RELEASE REJECT
+
+This message is sent by the S-NG-RAN node to the M-NG-RAN node to reject the request to release S-NG-RAN node resources.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.2.17 S-NODE RELEASE REQUIRED
+
+This message is sent by the S-NG-RAN node to request the release of all resources for a specific UE at the S-NG-RAN node.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|-------|-------------------------------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| <b>PDU sessions To Be Released</b> | | 0..1 | | | YES | ignore |
+| >PDU Session Resources to be released List – SN terminated | O | | PDU session List with data forwarding request info 9.2.1.24 | | – | |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------|-------------|----------------------|
+| S-NG-RAN node to M-NG-RAN node Container | O | | OCTET STRING | Includes the <i>CG-Config</i> message as defined in TS 38.331 [10]. | YES | ignore |
+| SCG UE History Information | O | | 9.2.3.151 | | YES | ignore |
+
+### 9.1.2.18 S-NODE RELEASE CONFIRM
+
+This message is sent by the M-NG-RAN node to confirm the release of all resources for a specific UE at the S-NG-RAN node.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|-----------------------------------------------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| <b>PDU Session Resources Released</b> | | 0..1 | | | YES | ignore |
+| >PDU sessions released List – SN terminated | O | | PDU Session List with data forwarding info from the target node<br>9.2.1.25 | | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+
+### 9.1.2.19 S-NODE COUNTER CHECK REQUEST
+
+This message is sent by the S-NG-RAN node to request the verification of the value of the PDCP COUNTs associated with SN terminated bearers established in the S-NG-RAN node.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------|----------|-------|------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| <b>Bearers Subject to</b> | | 1 | | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-------------------------|-----------------------|---------------------------------------------------------------|-------------|----------------------|
+| <b>Counter Check List</b> | | | | | | |
+| >Bearers Subject to Counter Check Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>UL COUNT | M | INTEGER (0..4294967295) | | Indicates the value of uplink COUNT associated to this DRB. | – | |
+| >>DL COUNT | M | INTEGER (0..4294967295) | | Indicates the value of downlink COUNT associated to this DRB. | – | |
+
+| Range bound | Explanation |
+|-------------|----------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs. Value is 32 |
+
+### 9.1.2.20 RRC TRANSFER
+
+This message is sent by the M-NG-RAN-NODE to the S-NG-RAN-NODE to transfer an RRC message or from the S-NG-RAN-NODE to the M-NG-RAN-NODE to report the DL RRC message delivery status.
+
+This message is also sent by the new NG-RAN-NODE to the old NG-RAN-NODE or from the old NG-RAN-NODE to the new NG-RAN-NODE to transfer an RRC message containing the SDT SRB in case of RACH based SDT without UE context relocation.
+
+This message is also sent by the M-NG-RAN-NODE to the S-NG-RAN node or from the S-NG-RAN node to the M-NG-RAN node to forward QoE measurement results and/or the RAN visible QoE measurement results received from the UE.
+
+Direction: M-NG-RAN node → S-NG-RAN node or S-NG-RAN node → M-NG-RAN node (Dual Connectivity).
+
+Direction: new NG-RAN node → old NG-RAN node or old NG-RAN node → new NG-RAN node (SDT).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| <b>Split SRB</b> | | 0..1 | | | YES | reject |
+| >RRC Container | O | | OCTET STRING | Contains a PDCP-C PDU encapsulating an RRC message as defined in subclause 6.2.1 of TS 38.331 [10] or TS 36.331 [14] and ciphered with | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|-------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | the key of the M-NG-RAN node | | |
+| >SRB Type | M | | ENUMERATED (srb1, srb2, ...) | The SRB type to be used | – | |
+| >Delivery Status | O | | 9.2.3.45 | DL RRC delivery status of split SRB | – | |
+| <b>UE Report</b> | | 0..1 | | | YES | reject |
+| >RRC Container | M | | OCTET STRING | For NGEN-DC and NR-DC, includes the <i>UL-DCCH-Message</i> as defined in subclause 6.2.1 of TS 38.331 [10] containing the <i>MeasurementReport</i> message or the <i>RRCReconfigurationComplete</i> message or the <i>FailureInformation</i> message or the <i>UEAssistanceInformation</i> message. For NR-DC, includes the <i>UL-DCCH-Message</i> as defined in subclause 6.2.1 of TS 38.331 [10] containing the <i>IABOtherInformation</i> message. For NE-DC, includes the <i>UL-DCCH-Message</i> as defined in subclause 6.2.1 of TS 36.331 [14] containing the <i>MeasurementReport</i> message. | – | |
+| <b>Fast MCG Recovery via SRB3 from SN to MN</b> | | 0..1 | | | YES | ignore |
+| >RRC Container | M | | OCTET STRING | For NR-DC, includes the <i>UL-DCCH-Message</i> as defined in subclause 6.2.1 of TS 38.331 [10] containing the <i>MCGFailureInformation</i> message. For NGEN-DC, includes the <i>UL-DCCH-Message</i> | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | as defined in subclause 6.2.1 of TS 36.331 [14] containing the <i>MCGFailureInformation</i> message. | | |
+| <b>Fast MCG Recovery via SRB3 from MN to SN</b> | | 0..1 | | | YES | ignore |
+| >RRC Container | M | | OCTET STRING | For NR-DC, includes the <i>DL-DCCH-Message</i> as defined in subclause 6.2.1 of TS 38.331 [10] containing the <i>RRCReconfiguration</i> message, or the <i>RRCRelease</i> message, or the <i>MobilityFromNRC ommand message</i> .<br>For NGEN-DC, includes the <i>DL-DCCH-Message</i> as defined in subclause 6.2.1 of TS 36.331 [14] containing the <i>RRCConnectionR econfiguration</i> message, or the <i>RRCConnectionR elease</i> message, or the <i>MobilityFromEUT RACommandmess age</i> . | – | |
+| <b>SDT SRB between New NG-RAN node and Old NG-RAN node</b> | | 0..1 | | | YES | ignore |
+| >RRC Container | M | | OCTET STRING | Contains a PDCP-C PDU encapsulating an RRC message as defined in subclause 6.2.1 of TS 38.331 [10]. | – | |
+| >SRB ID | M | | 9.2.3.165 | In this version of the specification, values "0", "1", "3", and "4" are not set by the sender and ignored by the receiver. | – | |
+| <b>QoE Measurement</b> | | 0..1 | | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Results</b> | | | | | | |
+| >QoE Reference | M | | OCTET STRING(SIZE(6)) | <i>QoE Reference</i> , as defined in clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. | – | |
+| >RRC Container for RAN Visible QoE Report | O | | OCTET STRING | Contains the RAN-VisibleMeasurements IE of the MeasurementReportAppLayer message as defined in TS 38.331 [10]. | – | |
+| >RRC Container for QoE Report | O | | OCTET STRING | Contains the measReportAppLayerContainer IE of the MeasurementReportAppLayer message as defined in TS 38.331 [10]. | – | |
+
+### 9.1.2.21 NOTIFICATION CONTROL INDICATION
+
+This message is sent to notify that the QoS requirements of already established GBR QoS flow(s) for a given UE for which notification control has been requested are either not fulfilled anymore or fulfilled again.
+
+Direction: S-NG-RAN node → M-NG-RAN node and M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| <b>PDU Session</b> | | 0..1 | | | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|--------------------------|-----------------------|-----------------------|-------------|----------------------|
+| <b>Resource Notify List</b> | | | | | | |
+| > <b>PDU Session Resource Notify Item</b> | | 1..<maxno ofPDUSessions> | | | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>QoS Flow Notification Control Indication Info | M | | 9.2.3.57 | | – | |
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions allowed towards one UE. Value is 256. |
+
+## 9.1.2.22 ACTIVITY NOTIFICATION
+
+This message is sent by a NG-RAN node to send notification to another NG-RAN node for one or several QoS flows or PDU sessions already established for a given UE.
+
+Direction: NG-RAN node → NG-RAN node
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|--------------------------|---------------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | ignore |
+| UE Context level user plane activity report | O | | User plane traffic activity report 9.2.3.59 | | YES | ignore |
+| <b>PDU Session Resource Activity Notify List</b> | | 0..1 | | | YES | ignore |
+| > <b>PDU Session Resource Activity Notify Item</b> | | 1..<maxno ofPDUSessions> | | | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>PDU Session level user plane activity report | O | | User plane traffic activity report 9.2.3.59 | | – | |
+| >> <b>QoS Flows Activity Notify List</b> | | 0..1 | | | – | |
+| >>> <b>QoS Flows Activity Notify Item</b> | | 1..<maxno ofQoSflows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>User plane traffic activity report | M | | 9.2.3.59 | | – | |
+| RAN Paging Failure | O | | ENUMERATED | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| | | | (true, ...) | | | |
+
+| Range bound | Explanation |
+|--------------------|-----------------------------------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.1.2.23 E-UTRA – NR CELL RESOURCE COORDINATION REQUEST
+
+This message is sent by a neighbouring ng-eNB to a peer gNB or by a neighbouring gNB to a peer ng-eNB, both nodes able to interact, to express the desired resource allocation for data traffic, for the sake of E-UTRA - NR Cell Resource Coordination.
+
+Direction: ng-eNB → gNB, gNB → ng-eNB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|----------|--------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE <i>Initiating Node Type</i> | M | | | | YES | reject |
+| >ng-eNB | | | | | | |
+| >>Data Traffic Resource Indication | M | | 9.2.2.30 | Indicates resource allocations for data traffic. | – | |
+| >>Spectrum Sharing Group ID | M | | INTEGER (1..maxnoofCellsInNG-RANnode) | Indicates the E-UTRA cells involved in resource coordination with the NR cells affiliated with the same <i>Spectrum Sharing Group ID</i> . | – | |
+| >>>List of E-UTRA Cells in E-UTRA Coordination Request | | 0..1 | | List of applicable E-UTRA cells. | – | |
+| >>>>List of E-UTRA Cells in E-UTRA Coordination Request Item | | 1.. <maxnoofCellsInNG-RANnode> | | | – | |
+| >>>>EUTRA Cell ID | M | | E-UTRA CGI 9.2.2.8 | | – | |
+| >gNB | | | | | | |
+| >>Data Traffic Resource Indication | M | | 9.2.2.30 | Indicates resource allocations for data traffic. | – | |
+| >>List of E-UTRA Cells in NR Coordination Request | | 0..1 | | List of applicable E-UTRA cells | – | |
+| >>>List of E-UTRA Cells in E-UTRA Coordination | | 1.. <maxnoofCellsInNG- | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|----------------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Request Item</b> | | <i>RANnode ></i> | | | | |
+| >>>>E-UTRA Cell ID | M | | E-UTRA CGI 9.2.2.8 | | – | |
+| >>Spectrum Sharing Group ID | M | | INTEGER (1..maxnoofCellsInNG-RANnode) | Indicates the NR cells involved in resource coordination with the E-UTRA cells affiliated with the same <i>Spectrum Sharing Group ID</i> . | – | |
+| >>List of NR Cells in NR Coordination Request | | 0..1 | | List of applicable NR cells | – | |
+| >>>List of NR Cells in NR Coordination Request Item | | 1.. <maxnoNRcellsSpectrumSharingwithE-UTRA > | | | – | |
+| >>>>NR-Cell ID | M | | NR CGI 9.2.2.7 | | – | |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| Range bound | Explanation |
+|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoNRcellsSpectrumSharingwithE-UTRA | Maximum no. of NR cells affiliated to a <i>Spectrum Sharing Group ID</i> involved in cell resource coordination with a number of E-UTRA cells affiliated with the same <i>Spectrum Sharing Group ID</i> . Value is 64. |
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+#### 9.1.2.24 E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE
+
+This message is sent by a neighbouring ng-eNB to a peer gNB or by a neighbouring gNB to a peer ng-eNB, both nodes able to interact, as a response to the E-UTRA – NR CELL RESOURCE COORDINATION REQUEST.
+
+Direction: ng-eNB → gNB, gNB → ng-eNB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|---------------------------------------|-------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE <i>Responding NodeType</i> | M | | | | YES | reject |
+| >ng-eNB | | | | | | |
+| >>Data Traffic Resource Indication | M | | 9.2.2.30 | Indicates resource allocations for data traffic. | – | |
+| >>Spectrum Sharing Group ID | M | | INTEGER (1..maxnoofCellsInNG-RANnode) | Indicates the E-UTRA cells involved in resource coordination with | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|----------|-----------------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | the NR cells affiliated with the same <i>Spectrum Sharing Group ID</i> . | | |
+| >>List of E-UTRA Cells in E-UTRA Coordination Response | | 0..1 | | List of applicable E-UTRA cells | – | |
+| >>>List of E-UTRA Cells in E-UTRA Coordination Response Item | | 1.. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>EUTRA Cell ID | M | | E-UTRA CGI 9.2.2.8 | | – | |
+| >gNB | | | | | | |
+| >>Data Traffic Resource Indication | M | | 9.2.2.30 | Indicates resource allocations for data traffic. | – | |
+| >>Spectrum Sharing Group ID | M | | INTEGER (1.. maxnoofCellsInNG-RANnode) | Indicates the NR cells involved in resource coordination with the E-UTRA cells affiliated with the same <i>Spectrum Sharing Group ID</i> . | – | |
+| >>List of NR Cells in NR Coordination Response | | 0..1 | | List of applicable NR cells | – | |
+| >>>List of NR Cells in NR Coordination Response Item | | 1.. < maxnoNRcellsSpectrumSharingwithE-UTRA > | | | – | |
+| >>>>NR Cell ID | M | | NR CGI 9.2.2.7 | | – | |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| Range bound | Explanation |
+|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoNRcellsSpectrumSharingwithE-UTRA | Maximum no. of NR cells affiliated to a <i>Spectrum Sharing Group ID</i> involved in cell resource coordination with a number of E-UTRA cells affiliated with the same <i>Spectrum Sharing Group ID</i> . Value is 64. |
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+## 9.1.2.25 SECONDARY RAT DATA USAGE REPORT
+
+This message is sent by the S-NG-RAN node to report data volumes for secondary RAT.
+
+Direction: S-NG-RAN node → M-NG-RAN node
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------|----------|--------------------------|------------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| <b>PDU Session Resource Secondary RAT Usage List</b> | | 1 | | | YES | reject |
+| > <b>PDU Session Resource Secondary RAT Usage Item</b> | | 1..<maxno ofPDUSessions> | | | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>Secondary RAT Usage Information | M | | 9.2.3.87 | | – | |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256. |
+
+### 9.1.2.26 TRACE START
+
+This message is sent by the M-NG-RAN node to initiate a trace session for a UE.
+
+Direction: M-NG-RAN node → S-NG-RAN node
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|------------------------------------|---------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node. | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node. | YES | reject |
+| Trace Activation | O | | 9.2.3.55 | This IE is always present. | YES | ignore |
+
+### 9.1.2.27 DEACTIVATE TRACE
+
+This message is sent by the M-NG-RAN node to deactivate a trace session.
+
+Direction: M-NG-RAN node → S-NG-RAN node
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|------------------------------------|---------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the M-NG-RAN node. | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | Allocated at the S-NG-RAN node. | YES | reject |
+
+| | | | | | | |
+|-----------------|---|--|------------------------|------------------------------------------------------|-----|--------|
+| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | As per NG-RAN Trace ID in <i>Trace Activation IE</i> | YES | ignore |
+|-----------------|---|--|------------------------|------------------------------------------------------|-----|--------|
+
+### 9.1.2.28 CELL TRAFFIC TRACE
+
+This message is sent by S-NG-RAN node to transfer the trace information to the M-NG-RAN node.
+
+Direction: S-NG-RAN node → M-NG-RAN node
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | As per NG-RAN Trace ID in <i>Trace Activation IE</i> | YES | ignore |
+| Trace Collection Entity IP Address | M | | Transport Layer Address 9.2.3.29 | For File based Reporting. Defined in TS 32.422 [23]. Should be ignored if the <i>Trace Collection Entity URI IE</i> is present. | YES | ignore |
+| Privacy Indicator | O | | ENUMERATED (Immediate MDT, ...) | | YES | ignore |
+| Trace Collection Entity URI | O | | URI 9.2.3.124 | For Streaming based Reporting. Defined in TS 32.422 [23] Replaces Trace Collection Entity IP Address if present | YES | ignore |
+
+### 9.1.2.29 SCG FAILURE INFORMATION REPORT
+
+This message is sent by M-NG-RAN node to S-NG-RAN node to report a PSCell change failure event.
+
+Direction: M-NG-RAN node → S-NG-RAN node .
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|---------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node. | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------|----------|-------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Source PSCell CGI | O | | Global NG-RAN Cell Identity 9.2.2.27 | NG-RAN CGI of source PSCell for PSCell change procedure | YES | ignore |
+| Failed PSCell CGI | O | | Global NG-RAN Cell Identity 9.2.2.27 | NG-RAN CGI of PSCell where SCG failure occurs for PSCell change procedure | YES | ignore |
+| SCG Failure Report Container | M | | OCTET STRING | The <i>SCGFailureInformation</i> message or the <i>SCGFailureInformationEUTRA</i> message as defined in TS 38.331 [10] or the <i>SCGFailureInformation</i> message or the <i>SCGFailureInformationNR</i> message as defined in TS 36.331 [14] | YES | ignore |
+| SN Mobility Information | O | | BIT STRING (SIZE (32)) | Information related to the PSCell change. It's provided by S-NG-RAN node in order to enable later analysis of the conditions that led to wrong PSCell change. | YES | ignore |
+| CPAC Configuration | O | | 9.2.2.103 | | YES | ignore |
+
+### 9.1.2.30 SCG FAILURE TRANSFER
+
+This message is sent by the S-NG-RAN node to the M-NG-RAN node to indicate that the root cause of the SCG failure may have occurred in the other nodes.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|---------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node. | YES | ignore |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node. | YES | ignore |
+
+### 9.1.2.31 CONDITIONAL PSCell CHANGE CANCEL
+
+This message is sent by the M-NG-RAN node to the source S-NG-RAN node to inform the cancellation of all the prepared PSCells in the target S-NG-RAN node during a Conditional PSCell Change.
+
+Direction: M-NG-RAN node → S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|---------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | YES | reject |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| Cause | O | | 9.2.3.2 | | YES | ignore |
+| Target S-NG-RAN node ID | M | | Global NG-RAN Node ID 9.2.2.3 | | YES | reject |
+
+### 9.1.2.32 RACH INDICATION
+
+This message is sent by the S-NG-RAN node to inform the M-NG-RAN node that one or more RA reports are available at the UE.
+
+Direction: S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|------------------------------------------|---------------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.3.1.1 | | YES | ignore |
+| RA Report Indication List | | 1 | | | YES | reject |
+| >RA Report Indication List Item | | 1 .. <maxno ofUEsforRAReportIndications> | | | – | - |
+| >>M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the M-NG-RAN node | – | |
+
+| Range bound | Explanation |
+|----------------------------------|-------------------------------------------------------------------------------------------------|
+| maxnoofUEsforRAReportIndications | Maximum number of UEs from which S-NG-RAN node is interested to collect RA report. Value is 64. |
+
+## 9.1.3 Messages for Global Procedures
+
+### 9.1.3.1 XN SETUP REQUEST
+
+This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer application data for an Xn-C interface instance.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Global NG-RAN Node ID | M | | 9.2.2.3 | | YES | reject |
+| TAI Support List | M | | 9.2.3.20 | List of supported TAs and associated characteristics. | YES | reject |
+| AMF Region Information | M | | 9.2.3.83 | Contains a list of all the AMF Regions to which the NG-RAN node belongs. | YES | reject |
+| <b>List of Served Cells NR</b> | | 0 ..<br><maxnoof<br>CellsInNG<br>-RAN<br>node> | | Contains a list of cells served by the gNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the gNB | YES | reject |
+| >Served Cell Information NR | M | | 9.2.2.11 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >Served Cell Specific Info Request | O | | 9.2.2.102 | | YES | ignore |
+| <b>List of Served Cells E-UTRA</b> | | 0 ..<br><maxnoof<br>CellsInNG<br>-RAN<br>node> | | Contains a list of cells served by the ng-eNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the ng-eNB | YES | reject |
+| >Served Cell Information E-UTRA | M | | 9.2.2.12 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >SFN Offset | O | | 9.2.2.75 | Associated with the <i>ECGI</i> IE in the <i>Served Cell Information E-UTRA</i> IE | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+| TNL Configuration Info | O | | 9.2.3.96 | | YES | ignore |
+| Partial List Indicator NR | O | | Partial List Indicator<br>9.2.2.46 | Value "partial" indicates that a partial list of cells is included in the <i>List of Served</i> | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|-------------------------------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>Cells NR IE.</i> | | |
+| Cell and Capacity Assistance Information NR | O | | 9.2.2.41 | Contains NR cell related assistance information. | YES | ignore |
+| Partial List Indicator E-UTRA | O | | Partial List Indicator 9.2.2.46 | Value "partial" indicates that a partial list of cells is included in the <i>List of Served Cells E-UTRA</i> . | YES | ignore |
+| Cell and Capacity Assistance Information E-UTRA | O | | 9.2.2.42 | Contains E-UTRA cell related assistance information. | YES | ignore |
+| Local NG-RAN Node Identifier | O | | 9.2.2.101 | | YES | ignore |
+| <b>Neighbour NG-RAN Node List</b> | | <i>0..<maxno ofNeighbourNG-RAN nodes></i> | | | YES | ignore |
+| >Global NG-RAN Node ID | M | | 9.2.2.3 | | – | |
+| >Local NG-RAN Node Identifier | M | | 9.2.2.101 | | – | |
+
+| Range bound | Explanation |
+|------------------------------|------------------------------------------------------------------------|
+| maxnoofCellsinNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxnoofNeighbourNG-RAN nodes | Maximum no. of neighbour NG-RAN nodes. Value is 256. |
+
+### 9.1.3.2 XN SETUP RESPONSE
+
+This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer application data for an Xn-C interface instance.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|------------------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Global NG-RAN Node ID | M | | 9.2.2.3 | | YES | reject |
+| TAI Support List | M | | 9.2.3.20 | List of supported TAs and associated characteristics. | YES | reject |
+| <b>List of Served Cells NR</b> | | <i>0 .. <maxnoof CellsinNG-RAN node></i> | | Contains a list of cells served by the gNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | gNB | | |
+| >Served Cell Information NR | M | | 9.2.2.11 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >Served Cell Specific Info Request | O | | 9.2.2.102 | This IE is not used in this version of the specification. | YES | ignore |
+| <b>List of Served Cells E-UTRA</b> | | 0 .. <maxnoof CellsinNG -RAN node> | | Contains a list of cells served by the ng-eNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the gNB | YES | reject |
+| >Served Cell Information E-UTRA | M | | 9.2.2.12 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >SFN Offset | O | | 9.2.2.75 | Associated with the <i>ECGI</i> IE in the <i>Served Cell Information E-UTRA</i> IE | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| AMF Region Information | O | | 9.2.3.83 | Contains a list of all the AMF Regions to which the NG-RAN node belongs. | YES | reject |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+| TNL Configuration Info | O | | 9.2.3.96 | | YES | ignore |
+| Partial List Indicator NR | O | | Partial List Indicator 9.2.2.46 | Value "partial" indicates that a partial list of cells is included in the <i>List of Served Cells NR</i> IE. | YES | ignore |
+| Cell and Capacity Assistance Information NR | O | | 9.2.2.41 | Contains NR cell related assistance information. | YES | ignore |
+| Partial List Indicator E-UTRA | O | | Partial List Indicator 9.2.2.46 | Value "partial" indicates that a partial list of cells is included in the <i>List of Served Cells E-UTRA</i> . | YES | ignore |
+| Cell and Capacity Assistance Information E-UTRA | O | | 9.2.2.42 | Contains E-UTRA cell related assistance | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|--------------------------------------|-----------------------|-----------------------|-------------|----------------------|
+| | | | | information. | | |
+| Local NG-RAN Node Identifier | O | | 9.2.2.101 | | YES | ignore |
+| <b>Neighbour NG-RAN Node List</b> | | 0..<maxno ofNeighbo urNG- RAN nodes> | | | YES | ignore |
+| >Global NG-RAN Node ID | M | | 9.2.2.3 | | – | |
+| >Local NG-RAN Node Identifier | M | | 9.2.2.101 | | – | |
+
+| Range bound | Explanation |
+|------------------------------|------------------------------------------------------------------------|
+| maxnoofCellsInNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxnoofNeighbourNG-RAN nodes | Maximum no. of neighbour NG-RAN nodes. Value is 256. |
+
+### 9.1.3.3 XN SETUP FAILURE
+
+This message is sent by the neighbouring NG-RAN node to indicate Xn Setup failure.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Time To Wait | O | | 9.2.3.56 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+| Message Oversize Notification | O | | 9.2.2.45 | | YES | ignore |
+
+### 9.1.3.4 NG-RAN NODE CONFIGURATION UPDATE
+
+This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer updated information for an Xn-C interface instance.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|-----------------------|-------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| TAI Support List | O | | 9.2.3.20 | List of supported TAs and associated characteristics. | GLOBAL | reject |
+| CHOICE <i>Initiating NodeType</i> | M | | | | YES | ignore |
+| >gNB | | | | | | |
+| >>Served Cells To | O | | 9.2.2.15 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|------------------------------|-----------------------------------------|-------------------------------------------------------------------|-------------|----------------------|
+| Update NR | | | | | | |
+| >>Cell Assistance Information NR | O | | 9.2.2.17 | | YES | ignore |
+| >>Cell Assistance Information E-UTRA | O | | 9.2.2.43 | | YES | ignore |
+| >>Served Cell Specific Info Request | O | | 9.2.2.102 | | YES | ignore |
+| >ng-eNB | | | | | | |
+| >>Served Cells to Update E-UTRA | O | | 9.2.2.16 | | YES | ignore |
+| >>Cell Assistance Information NR | O | | 9.2.2.17 | | YES | ignore |
+| >>Cell Assistance Information E-UTRA | O | | 9.2.2.43 | | YES | ignore |
+| <b>TNLA To Add List</b> | | 0..1 | | | YES | ignore |
+| > <b>TNLA To Add Item</b> | | 1..<maxno ofTNLAssociations> | | | – | |
+| >>TNLA Transport Layer Information | M | | CP Transport Layer Information 9.2.3.31 | CP Transport Layer Information of NG-RAN node <sub>1</sub> | – | |
+| >> TNL Association Usage | M | | 9.2.3.84 | | – | |
+| <b>TNLA To Update List</b> | | 0..1 | | | YES | ignore |
+| > <b>TNLA To Update Item</b> | | 1..<maxno ofTNLAssociations> | | | – | |
+| >>TNLA Transport Layer Information | M | | CP Transport Layer Information 9.2.3.31 | CP Transport Layer Information of NG-RAN node <sub>1</sub> | – | |
+| >> TNL Association Usage | O | | 9.2.3.84 | | – | |
+| <b>TNLA To Remove List</b> | | 0..1 | | | YES | ignore |
+| > <b>TNLA To Remove Item</b> | | 1..<maxno ofTNLAssociations> | | | – | |
+| >>TNLA Transport Layer Information | M | | CP Transport Layer Information 9.2.3.31 | CP Transport Layer Information of NG-RAN node <sub>1</sub> | – | |
+| Global NG-RAN Node ID | O | | 9.2.2.3 | | YES | reject |
+| AMF Region Information To Add | O | | AMF Region Information 9.2.3.83 | List of all added AMF Regions to which the NG-RAN node belongs. | YES | reject |
+| AMF Region Information To Delete | O | | AMF Region Information 9.2.3.83 | List of all deleted AMF Regions to which the NG-RAN node belongs. | YES | reject |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|-------------------------------------------|-----------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| TNL Configuration Info | O | | 9.2.3.96 | | YES | ignore |
+| <b>Coverage Modification List</b> | | 0 .. 1 | | List of cells with modified coverage. | GLOBAL | reject |
+| >Coverage Modification Item | | 0 .. <maxnoof CellsinNG-RAN node> | | | – | |
+| >>Global NG-RAN Cell Identity | M | | Global NG-RAN Cell Identity 9.2.2.27 | NG-RAN Cell Global Identifier of the cell to be modified. | – | |
+| >>Cell Coverage State | M | | INTEGER (0..63, ...) | Value '0' indicates that the cell is inactive. Other values Indicates that the cell is active and also indicates the coverage configuration of the concerned cell. | – | |
+| >>Cell Deployment Status Indicator | O | | ENUMERATED (pre-change-notification, ...) | Indicates the Cell Coverage State is planned to be used at the next reconfiguration. | – | |
+| >>Cell Replacing Info | C- ifCellDeploymentStatusIndicatorPresent | | | | – | |
+| >>>Replacing Cells | | 0 .. <maxnoof CellsinNG-RAN node> | | | – | |
+| >>>>Global NG-RAN Cell Identity | | | Global NG-RAN Cell Identity 9.2.2.27 | NG-RAN Cell Global Identifier of a cell that may replace all or part of the coverage of the cell to be modified. | – | |
+| >>>SSB Coverage Modification List | | 0.. 1 | | List of SSB beams with modified coverage. | – | |
+| >>>SSB Coverage Modification Item | | 0..<maxno ofSSBAreas> | | | – | |
+| >>>>SSB Index | M | | INTEGER (0..63) | Identifier of the SSB beam to be modified. | – | |
+| >>>>SSB Coverage State | M | | INTEGER (0..15, ...) | Value '0' indicates that the SSB beam is inactive. Other | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|--------------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | values Indicates that the SSB beam is active and also indicates the coverage configuration of the concerned SSB beam. | | |
+| >>Coverage Modification Cause | O | | ENUMERATED (coverage, cell edge capacity, ..., network energy saving) | Indicates the reason for the coverage modification in NG-RAN node <sub>1</sub> . | YES | ignore |
+| Local NG-RAN Node Identifier | O | | 9.2.2.101 | | YES | ignore |
+| <b>Neighbour NG-RAN Node List</b> | | 0..<maxno ofNeighbo urNG- RAN nodes> | | | YES | ignore |
+| >Global NG-RAN Node ID | M | | 9.2.2.3 | | – | |
+| >Local NG-RAN Node Identifier | M | | 9.2.2.101 | | – | |
+| Local NG-RAN Node Identifier Removal | O | | Local NG-RAN Node Identifier 9.2.2.101 | | YES | ignore |
+
+| Range bound | Explanation |
+|------------------------------|----------------------------------------------------------------------------|
+| maxnoofTNLAssociations | Maximum numbers of TNL Associations between the NG RAN nodes. Value is 32. |
+| maxnoofCellsInNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. |
+| maxnoofNeighbourNG-RAN nodes | Maximum no. of neighbour NG-RAN nodes. Value is 256. |
+
+| Condition | Explanation |
+|----------------------------------------|----------------------------------------------------------------------------------------|
+| ifCellDeploymentStatusIndicatorPresent | This IE shall be present if the <i>Cell Deployment Status Indicator</i> IE is present. |
+
+### 9.1.3.5 NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE
+
+This message is sent by a neighbouring NG-RAN node to a peer node to acknowledge update of information for a TNL association.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE Responding NodeType | M | | | | YES | ignore |
+| >ng-eNB | | | | | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------|----------|------------------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>>>Served E-UTRA Cells</b> | | <i>0 .. < maxnoofCellsinNG-RANnode ></i> | | Complete or limited list of cells served by an ng-eNB, if requested by NG-RAN node <sub>1</sub> . | YES | ignore |
+| >>>Served Cell Information E-UTRA | M | | 9.2.2.12 | | – | |
+| >>>Neighbour Information NR | O | | 9.2.2.13 | NR neighbours. | – | |
+| >>>Neighbour Information E-UTRA | O | | 9.2.2.14 | E-UTRA neighbours | – | |
+| >>>SFN Offset | O | | 9.2.2.75 | Associated with the <i>ECGI</i> IE in the <i>Served Cell Information E-UTRA</i> IE | YES | ignore |
+| >>Partial List Indicator E-UTRA | O | | Partial List Indicator 9.2.2.46 | Value "partial" indicates that a partial list of cells is included in the <i>Served E-UTRA Cells</i> IE | YES | ignore |
+| >>Cell and Capacity Assistance Information E-UTRA | O | | 9.2.2.42 | Contains E-UTRA cell related assistance information. | YES | ignore |
+| <b>>gNB</b> | | | | | | |
+| <b>>>Served NR Cells</b> | | <i>0 .. < maxnoofCellsinNG-RANnode ></i> | | Complete or limited list of cells served by a gNB, if requested by NG-RAN node <sub>1</sub> . | – | |
+| >>>Served Cell Information NR | M | | 9.2.2.11 | | – | |
+| >>>Neighbour Information NR | O | | 9.2.2.13 | NR neighbours. | – | |
+| >>>Neighbour Information E-UTRA | O | | 9.2.2.14 | E-UTRA neighbours | – | |
+| >>Partial List Indicator NR | O | | Partial List Indicator 9.2.2.46 | Value "partial" indicates that a partial list of cells is included in the <i>Served NR Cells</i> IE | YES | ignore |
+| >>Cell and Capacity Assistance Information NR | O | | 9.2.2.41 | Contains NR cell related assistance information. | YES | ignore |
+| <b>TNLA Setup List</b> | | <i>0..1</i> | | | YES | ignore |
+| <b>>TNLA Setup Item</b> | | <i>1..<maxnoofTNLAssociations></i> | | | – | |
+| >>TNLA Transport Layer Address | M | | CP Transport Layer Information | CP Transport Layer Information as received from | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|------------------------------------|-----------------------------------------|--------------------------------------------------------------------------|-------------|----------------------|
+| | | | 9.2.3.31 | NG-RAN node <sub>1</sub> | | |
+| <b>TNLA Failed to Setup List</b> | | 0..1 | | | YES | ignore |
+| > <b>TNLA Failed To Setup Item</b> | | 1..<maxno ofTNLAssociations> | | | – | |
+| >>TNLA Transport Layer Address | M | | CP Transport Layer Information 9.2.3.31 | CP Transport Layer Information as received from NG-RAN node <sub>1</sub> | – | |
+| >>Cause | M | | 9.2.3.2 | | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+| TNL Configuration Info | O | | 9.2.3.96 | | YES | ignore |
+| Local NG-RAN Node Identifier | O | | 9.2.2.101 | | YES | ignore |
+| <b>Neighbour NG-RAN Node List</b> | | 0..<maxno ofNeighbourNG-RAN nodes> | | | YES | ignore |
+| >Global NG-RAN Node ID | M | | 9.2.2.3 | | – | |
+| >Local NG-RAN Node Identifier | M | | 9.2.2.101 | | – | |
+| Local NG-RAN Node Identifier Removal | | | Local NG-RAN Node Identifier 9.2.2.101 | | YES | ignore |
+
+| Range bound | Explanation |
+|------------------------------|-------------------------------------------------------------------------|
+| maxnoofCellsinNGRANnode | Maximum no. cells that can be served by an NG-RAN node. Value is 16384. |
+| maxnoofTNLAssociations | Maximum numbers of TNL Associations between NG-RAN nodes. Value is 32. |
+| maxnoofNeighbourNG-RAN nodes | Maximum no. of neighbour NG-RAN nodes. Value is 256. |
+
+### 9.1.3.6 NG-RAN NODE CONFIGURATION UPDATE FAILURE
+
+This message is sent by the neighbouring NG-RAN node to indicate NG-RAN node Configuration Update failure.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Time To Wait | O | | 9.2.3.56 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+### 9.1.3.7 CELL ACTIVATION REQUEST
+
+This message is sent by the NG-RAN node<sub>1</sub> to the peer NG-RAN node<sub>2</sub> to request a previously switched-off cell(s) or SSB beam(s) to be re-activated.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-----------------------------------|-----------------------|-------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE <i>Served Cells To Activate</i> | M | | | | YES | reject |
+| >NR Cells | | | | | | |
+| >>NR Cells List | | 1 | | | – | |
+| >>>NR Cells item | | 1 .. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>NR CGI | M | | 9.2.2.7 | | – | |
+| >E-UTRA Cells | | | | | | |
+| >>E-UTRA Cells List | | 1 | | | – | |
+| >>>E-UTRA Cells item | | 1 .. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>E-UTRA CGI | M | | 9.2.2.8 | | – | |
+| >NR Cells and SSBs | | | | | YES | ignore |
+| >>To Be Activated NR Cells and SSBs List | | 1 | | | – | |
+| >>>To Be Activated NR Cells and SSBs item | | 1 .. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>NR CGI | M | | 9.2.2.7 | | – | |
+| >>>>SSBs to be Activated List | | 0..1 | | | – | |
+| >>>>>SSBs to be Activated Item | | 1 .. < maxnoofSBAreas > | | | – | |
+| >>>>>>SSB Index | M | | INTEGER (0..63) | Identifier of the SSB beam requested to be activated. | – | |
+| Activation ID | M | | INTEGER (0..255) | Allocated by the NG-RAN node <sub>1</sub> | YES | reject |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| Range bound | Explanation |
+|--------------------------|------------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by an NG-RAN node. Value is 16384. |
+| maxnoofSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+
+### 9.1.3.8 CELL ACTIVATION RESPONSE
+
+This message is sent by an NG-RAN node<sub>2</sub> to a peer NG-RAN node<sub>1</sub> to indicate that one or more cell(s) previously switched-off has (have) been activated.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-----------------------------------|-----------------------|-------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE <i>Activated Served Cells</i> | M | | | | YES | reject |
+| >NR Cells | | | | | | |
+| >>NR Cells List | | 1 | | | – | |
+| >>>NR Cells Item | | 1 .. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>NR CGI | M | | 9.2.2.7 | | – | |
+| >E-UTRA Cells | | | | | | |
+| >>E-UTRA Cells List | | 1 | | | – | |
+| >>>E-UTRA Cells Item | | 1 .. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>E-UTRA CGI | M | | 9.2.2.8 | | – | |
+| >NR Cells and SSBs | | | | | YES | ignore |
+| >>Activated NR Cells and SSBs List | | 1 | | | – | |
+| >>>Activated NR Cells and SSBs Item | | 1 .. < maxnoofCellsInNG-RANnode > | | | – | |
+| >>>>NR CGI | M | | 9.2.2.7 | | – | |
+| >>>>SSBs Activated List | | 0..1 | | | – | |
+| >>>>>SSB Activated Item | | 1 .. < maxnoofSSBAreas > | | | – | |
+| >>>>>>SSB Index | M | | INTEGER (0..63) | Identifier of the activated SSB beam. | – | |
+| Activation ID | M | | INTEGER (0..255) | Allocated by the NG-RAN node <sub>1</sub> | YES | reject |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| Range bound | Explanation |
+|--------------------------|------------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by an NG-RAN node. Value is 16384. |
+| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+
+### 9.1.3.9 CELL ACTIVATION FAILURE
+
+This message is sent by an NG-RAN node<sub>2</sub> to a peer NG-RAN node<sub>1</sub> to indicate cell activation failure.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|-------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Activation ID | M | | INTEGER (0..255) | Allocated by the NG-RAN node <sub>1</sub> | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+### 9.1.3.10 RESET REQUEST
+
+This message is sent from one NG-RAN node to another NG-RAN node and is used to request the Xn interface to be reset.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|---------------------------|---------------------------------|-------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE <i>Reset Request TypeInfo</i> | M | | | | YES | reject |
+| > <i>Full Reset</i> | | | | | | |
+| > <i>Partial Reset</i> | | | | | | |
+| >>UE contexts to be released List | | 1 | | | – | |
+| >>>UE Contexts to be released Item | | 1 .. <maxnoof UEcontexts> | | | – | |
+| >>>>NG-RAN node1 UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the NG-RAN node <sub>1</sub> | – | |
+| >>>>NG-RAN node2 UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the NG-RAN node <sub>2</sub> | – | |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| Range bound | Explanation |
+|-------------------|--------------------------------------------|
+| maxnoofUEContexts | Maximum no. of UE Contexts. Value is 8192. |
+
+### 9.1.3.11 RESET RESPONSE
+
+This message is sent by an NG-RAN node as a response to a RESET REQUEST message.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|------------------------------|---------------------------------|-------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| CHOICE Reset<br>Response Type Info | M | | | | YES | ignore |
+| >Full Reset | | | | | | |
+| >Partial Reset | | | | | | |
+| >>Admitted UE contexts to be released List | | 1 | | | – | |
+| >>>Admitted UE Contexts to be released Item | | 1 ..<br><maxnoof UEcontexts> | | | – | |
+| >>>>NG-RAN node1 UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the NG-RAN node <sub>1</sub> | – | |
+| >>>>NG-RAN node2 UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the NG-RAN node <sub>2</sub> | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+| Range bound | Explanation |
+|-------------------|--------------------------------------------|
+| maxnoofUEContexts | Maximum no. of UE Contexts. Value is 8192. |
+
+### 9.1.3.12 ERROR INDICATION
+
+This message is used to indicate that some error has been detected in the NG-RAN node.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|-------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Old NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated for handover at the source NG-RAN node and for dual connectivity at the S-NG-RAN node or for an SN Status Transfer procedure at the NG-RAN node from which a DRB is offloaded. | YES | ignore |
+| New NG-RAN node UE XnAP ID | O | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated for handover at the target NG-RAN node and for dual connectivity at the M-NG-RAN node | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | or for an SN Status Transfer procedure at the NG-RAN node to which a DRB is offloaded. | | |
+| Cause | O | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+### 9.1.3.13 XN REMOVAL REQUEST
+
+This message is sent by a NG-RAN node to a neighbouring NG-RAN node to initiate the removal of the interface instance.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|---------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Global NG-RAN Node ID | M | | 9.2.2.3 | | YES | reject |
+| Xn Removal Threshold | O | | Xn Benefit Value 9.2.3.54 | | YES | reject |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+### 9.1.3.14 XN REMOVAL RESPONSE
+
+This message is sent by a NG-RAN node to a neighbouring NG-RAN node to acknowledge the initiation of removal of the interface instance.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| Global NG-RAN Node ID | M | | 9.2.2.3 | | YES | reject |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+### 9.1.3.15 XN REMOVAL FAILURE
+
+This message is sent by the NG-RAN node to indicate that removing the interface instance cannot be accepted.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+
+| | | | | | | |
+|-------------------------------|---|--|----------|--|-----|--------|
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+| Interface Instance Indication | O | | 9.2.2.39 | | YES | reject |
+
+### 9.1.3.16 FAILURE INDICATION
+
+This message is sent by NG-RAN node<sub>2</sub> to indicate an RRC re-establishment attempt or a reception of an RLF Report from a UE that suffered a connection failure at NG-RAN node<sub>1</sub>.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| CHOICE <i>Initiating condition</i> | M | | | | YES | reject |
+| >RRC Reestab | | | | | | |
+| >>CHOICE RRC Reestab Initiated Reporting | M | | | | – | |
+| >>>RRC Reestab Reporting without RLF Report | | | | | | |
+| >>>>Failure cell PCI | M | | 9.2.2.10 | Physical Cell Identifier | – | |
+| >>>>Re-establishment cell CGI | M | | Global NG-RAN Cell Identity 9.2.2.27 | | – | |
+| >>>>C-RNTI | M | | BIT STRING (SIZE (16)) | Corresponds to information provided in the <i>c-RNTI</i> contained either in the <i>RRCRE-establishment Request</i> message (TS 38.331 [10]) or in the <i>RRConnectionReestablishmentRequest</i> message (TS 36.331 [14]) | – | |
+| >>>>ShortMAC-I | M | | BIT STRING (SIZE (16)) | Corresponds to information provided in the <i>shortMAC-I</i> contained either in the <i>RRCRE-establishment Request</i> message (TS 38.331 [10]) or in the <i>RRConnectionReestablishmentRequest</i> message (TS 36.331 [14]) | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>>RRC Conn Reestab Indicator | O | | ENUMERATED (reconfiguration Failure, handoverFailure, otherFailure, ...) | Corresponds to information provided in the <i>reestablishmentCause</i> contained in the <i>RRCReestablishmentRequest</i> message as defined in TS 38.331 [10] or in the <i>RRCConnectionReestablishmentRequest</i> message as defined in TS 36.331 [14]. | YES | ignore |
+| >>>RRC Reestab Reporting with RLF Report | | | | | | |
+| >>>>UE RLF Report Container | M | | 9.2.2.59 | | – | |
+| >RRC Setup | | | | | | |
+| >>CHOICE RRC Setup Initiated Reporting | M | | | | – | |
+| >>>RRC Setup Reporting with RLF Report | | | | | | |
+| >>>>UE RLF Report Container | M | | 9.2.2.59 | | – | |
+| >>UE RLF Report Container | O | | 9.2.2.59 | This IE is not used in this version of the specification. | | |
+
+### 9.1.3.17 HANDOVER REPORT
+
+This message is sent by NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub> to report a handover failure event, or other critical mobility problem.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|--------------------------------------------------------------------------|------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| Handover Report Type | M | | ENUMERATED (HO too early, HO to wrong cell, Inter-system ping-pong. ...) | | YES | ignore |
+| Handover Cause | M | | Cause 9.2.3.2 | Indicates handover cause employed for handover from NG-RAN node <sub>2</sub> | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------|---------------------------------------------------|-------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Source cell CGI | M | | Global NG-RAN Cell Identity 9.2.2.27 | NG-RAN CGI of source cell for handover procedure (in NG-RAN node <sub>2</sub> ) | YES | ignore |
+| Target cell CGI | M | | Global NG-RAN Cell Identity 9.2.2.27 | NG-RAN CGI of target cell for handover procedure (in NG-RAN node <sub>1</sub> ).<br>If the Handover Report Type is set to "Inter-system ping-pong", it contains the target cell of the inter system handover from the other system to NG-RAN node <sub>1</sub> cell | YES | ignore |
+| Re-establishment cell CGI | C-<br>ifHandoverReportType<br>HoToWrongCell | | Global Cell Identity 9.2.2.73 | CGI of cell where UE attempted re-establishment or where UE successfully re-connected after the failure | YES | ignore |
+| Target cell in E-UTRAN | C-<br>ifHandoverReportType<br>Intersystempingpong | | OCTET STRING | Encoded according to <i>Global Cell ID</i> in the <i>Last Visited E-UTRAN Cell Information</i> IE, as defined in TS 36.413 [31] | YES | ignore |
+| Source cell C-RNTI | O | | BIT STRING (SIZE (16)) | C-RNTI allocated at the source NG-RAN node (in NG-RAN node <sub>2</sub> ) | YES | ignore |
+| Mobility Information | O | | BIT STRING (SIZE (32)) | Information provided in the HANDOVER REQUEST message or in the SN STATUS TRANSFER message from NG-RAN node <sub>2</sub> . | YES | ignore |
+| UE RLF Report Container | O | | 9.2.2.59 | The UE RLF Report Container IE received in the FAILURE INDICATION message. | YES | ignore |
+| CHO Configuration | O | | 9.2.2.76 | | YES | ignore |
+| Target cell C-RNTI | O | | BIT STRING (SIZE (16)) | C-RNTI allocated at the target NG- | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------|----------|-------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Time Since Failure | O | | INTEGER (0..172800, ...) | RAN node.<br>Corresponds to the <i>TimeSinceFailure</i> IE received from the UE in RLF Report as defined in TS 36.331 [14]. | YES | ignore |
+
+| Condition | Explanation |
+|------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| ifHandoverReportType HoToWrongCell | This IE shall be present if the <i>Handover Report Type</i> IE is set to the value "HO to wrong cell" |
+| ifHandoverReportType Intersystempingpong | This IE shall be present if the <i>Handover Report Type</i> IE is set to the value "Inter-system ping-pong" |
+
+### 9.1.3.18 RESOURCE STATUS REQUEST
+
+This message is sent by NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub> to initiate the requested measurement according to the parameters given in the message.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------------------------------------|-------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1 Measurement ID | M | | INTEGER (1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2 Measurement ID | C-<br>ifRegistrationRequestStoporAdded | | INTEGER (1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | ignore |
+| Registration Request | M | | ENUMERATED (start, stop, add, ...) | Type of request for which the resource status is required. | YES | reject |
+| Report Characteristics | C-<br>ifRegistrationRequestStart | | BITSTRING (SIZE(32)) | Each position in the bitmap indicates measurement object the NG-RAN node <sub>2</sub> is requested to report.<br>First Bit = PRB Periodic,<br>Second Bit = TNL Capacity Ind Periodic,<br>Third Bit = Composite Available Capacity Periodic,<br>Fourth Bit = Number of Active UEs Periodic, | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------------------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | Fifth Bit = RRC connections Periodic,<br>Sixth Bit = NR-U Channel List Periodic.<br>Other bits shall be ignored by the NG-RAN node2. | | |
+| <b>Cell To Report List</b> | | 0..1 | | Cell ID list to which the request applies. | YES | ignore |
+| <b>>Cell To Report Item</b> | | 1 .. <maxnoof CellsinNG - RANnode > | | | – | |
+| <b>>>Cell ID</b> | M | | Global NG-RAN Cell Identity 9.2.2.27 | | – | |
+| <b>>>SSB To Report List</b> | | 0..1 | | SSB list to which the request applies. | – | |
+| <b>>>>SSB To Report Item</b> | | 1 .. <maxnoof SBAreas > | | | – | |
+| <b>>>>>SSB-Index</b> | M | | INTEGER (0..63..) | | – | |
+| <b>>>Slice To Report List</b> | | 0..1 | | S-NSSAI list to which the request applies. | – | |
+| <b>>>>Slice To Report Item</b> | | 1 .. <maxnoofB PLMNs > | | | – | |
+| <b>>>>>PLMN Identity</b> | M | | 9.2.2.4 | Broadcast PLMN | – | |
+| <b>>>>>S-NSSAI List</b> | | 1 | | | – | |
+| <b>>>>>>S-NSSAI Item</b> | | 1 .. <maxnoofS licItems > | | | – | |
+| <b>>>>>>>S-NSSAI</b> | M | | S-NSSAI 9.2.3.21 | | – | |
+| <b>Reporting Periodicity</b> | O | | ENUMERATED (500ms, 1000ms, 2000ms, 5000ms, 10000ms, ...) | Periodicity that can be used for reporting of indicated measurements. Also used as the averaging window length for all measurement object if supported. This IE is ignored | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|--------------------------------------------------------|-------------|----------------------|
+| | | | | if the <i>Registration Request</i> IE is set to "add". | | |
+
+| Condition | Explanation |
+|--------------------------------|-----------------------------------------------------------------------------------------------------|
+| ifRegistrationRequestStoporAdd | This IE shall be present if the <i>Registration Request</i> IE is set to the value "stop" or "add". |
+| ifRegistrationRequestStart | This IE shall be present if the <i>Registration Request</i> IE is set to the value "start". |
+
+| Range bound | Explanation |
+|--------------------------|------------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. |
+
+### 9.1.3.19 RESOURCE STATUS RESPONSE
+
+This message is sent by NG-RAN node<sub>2</sub> to NG-RAN node<sub>1</sub> to indicate that the requested measurement, for all of the measurement objects included in the measurement is successfully initiated.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|--------------------------|---------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | reject |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.3.20 RESOURCE STATUS FAILURE
+
+This message is sent by the NG-RAN node<sub>2</sub> to NG-RAN node<sub>1</sub> to indicate that for any of the requested measurement objects the measurement cannot be initiated.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|--------------------------|---------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.3.21 RESOURCE STATUS UPDATE
+
+This message is sent by NG-RAN node<sub>2</sub> to NG-RAN node<sub>1</sub> to report the results of the requested measurements.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | reject |
+| <b>Cell Measurement Result</b> | | 1 | | | YES | ignore |
+| <b>>Cell Measurement Result Item</b> | | 1 .. <<br>maxnoofC<br>ellsinNG-<br>RANnode<br>> | | | YES | ignore |
+| >>Cell ID | M | | Global NG-RAN<br>Cell Identity<br>9.2.2.27 | | – | |
+| >>Radio Resource Status | O | | 9.2.2.50 | | – | |
+| >>TNL Capacity Indicator | O | | 9.2.2.49 | | – | |
+| >>Composite Available Capacity Group | O | | 9.2.2.51 | | – | |
+| >>Slice Available Capacity | O | | 9.2.2.55 | | – | |
+| >>Number of Active UEs | O | | 9.2.2.62 | | – | |
+| >>RRC Connections | O | | 9.2.2.56 | | – | |
+| <b>>>NR-U Channel List</b> | | 0..1 | | | YES | ignore |
+| <b>>>>NR-U Channel Item</b> | | 1..<maxno<br>ofNR-<br>UChannel<br>IDs> | | | – | |
+| >>>>NR-U Channel ID | M | | INTEGER (1..<br>maxnoofNR-<br>UChannelIDs,<br>...) | The NR-U channel utilised in the last reporting period | – | |
+| >>>>Channel occupancy time percentage DL | M | | INTEGER<br>(0..100) | The percentage of time for which the channel resources have been utilised for DL traffic served by the corresponding NR-U Channel of the serving cell. Value 100 indicates that the channel resources have been utilized for DL traffic served by the | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | corresponding NR-U Channel of the serving cell for the whole duration between consecutive reporting. | | |
+| >>>>Energy Detection Threshold DL | M | | INTEGER (-100..-50,...) | Average ED Threshold used for DL channel sensing at the gNB. Value is in dBm. | – | |
+| >>>>Channel Occupancy Time Percentage UL | O | | INTEGER (0..100) | The percentage of time for which the channel resources have been utilised for UL traffic served by the corresponding NR-U Channel of the serving cell for UEs that transmit to the serving cell. Value 100 indicates that the channel resources have been utilized for UL traffic served by the corresponding NR-U Channel of the serving cell for the whole duration between consecutive reporting. | YES | ignore |
+| >>>>Energy Detection Threshold UL | O | | INTEGER (-100..-50,...) | Indicates the average of the maximum ED Threshold configured by the gNB for UL channel sensing. Value is in dBm. | YES | ignore |
+| >>>>Radio Resource Status NR-U | O | | 9.2.2.104 | Indicates the radio resource status per NR-U channel. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------------|------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxnoofNR-UChannelIDs | Maximum no. NR-U channel IDs in a cell. Value is 16. |
+
+### 9.1.3.22 MOBILITY CHANGE REQUEST
+
+This message is sent by NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub> to initiate adaptation of mobility parameters.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|------------------------|------------------------------------------|----------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1 Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | reject |
+| NG-RAN node2 Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | reject |
+| NG-RAN node1 Mobility Parameters | O | | Mobility Parameters Information 9.2.2.60 | Configuration change in NG-RAN node1 cell | YES | ignore |
+| NG-RAN node2 Proposed Mobility Parameters | M | | Mobility Parameters Information 9.2.2.60 | Proposed configuration change in NG-RAN node2 cell | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | reject |
+| <b>SSB Offsets List</b> | | 0..1 | | | YES | ignore |
+| > <b>SSB Offsets Item</b> | | 1 .. < maxnoofSBAreas> | | | – | |
+| >>NG-RAN node1 SSB Offset Information | O | | SSB Offset Information 9.2.2.77 | Configuration change in NG-RAN node 1 SSB | – | |
+| >>NG-RAN node2 SSB Offset Information | M | | SSB Offset Information 9.2.2.77 | Proposed configuration change in NG-RAN node2 SSB | – | |
+
+| Range bound | Explanation |
+|----------------|------------------------------------------------------------------------------|
+| maxnoofSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+
+### 9.1.3.23 MOBILITY CHANGE ACKNOWLEDGE
+
+This message is sent by NG-RAN node<sub>2</sub> to indicate to NG-RAN node<sub>1</sub> that Proposed Mobility Parameters proposed by NG-RAN node<sub>1</sub> were accepted.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|--------------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1 Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | reject |
+| NG-RAN node2 Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Criticality Diagnostics | O | | 9.2.3.2 | | YES | ignore |
+
+### 9.1.3.24 MOBILITY CHANGE FAILURE
+
+This message is sent by the NG-RAN node<sub>2</sub> to indicate to NG-RAN node<sub>1</sub> that Proposed Mobility Parameters proposed by NG-RAN node<sub>1</sub> were refused.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|-------------------------|--------------------------------------|-----------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1 Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | ignore |
+| NG-RAN node2 Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | | YES | ignore |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Mobility Parameters Modification Range | O | | 9.2.2.61 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.2 | | YES | ignore |
+| <b>NG-RAN node2 SSB Offsets Modification Range</b> | | 0 .. < maxnoofSSBAreas> | | | YES | ignore |
+| >SSB Offset Modification Range | M | | 9.2.2.78 | | – | |
+
+| Range bound | Explanation |
+|-----------------|------------------------------------------------------------------------------|
+| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+
+### 9.1.3.25 ACCESS AND MOBILITY INDICATION
+
+This message is sent by NG-RAN node<sub>1</sub> to transfer access and mobility related information to NG-RAN node<sub>2</sub>.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------|----------|---------------------------|------------------------|--------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| <b>RA Report List</b> | | 0..1 | | | YES | ignore |
+| >RA Report List Item | | 1 .. < maxnoofRAReports > | | | EACH | ignore |
+| >>RA Report Container | M | | OCTET STRING | Includes the RA-ReportList IE as defined in subclause 6.2.2 in TS 38.331 [10]. | YES | ignore |
+| >>UE Assistant Identifier | O | | NG-RAN node UE XnAP ID | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|----------------------------------------------------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | 9.2.3.16 | | | |
+| >>PSCell List Container | O | | OCTET STRING | Includes the <i>PSCellIdListNR</i> IE as defined in subclause 6.2.2 in TS 36.331 [14]. | YES | ignore |
+| <b>Successful HO Report List</b> | | 0..1 | | | YES | ignore |
+| >Successful HO Report List Item | | 1 ..<br><maxnoof<br>Successfu<br>lHORepor<br>ts> | | | – | |
+| >>Successful HO Report Container | M | | OCTET STRING | Includes the <i>SuccessHO-Report</i> IE as defined in subclause 6.2.2 in TS 38.331 [10]. | – | |
+| <b>Successful PSCell Change Report List</b> | | 0..1 | | | YES | ignore |
+| >Successful PSCell Change Report List Item | | 1 ..<br><maxnoof<br>Successfu<br>lPSCellCh<br>angeRepo<br>rts> | | | – | |
+| >>Successful PSCell Change Report Container | M | | OCTET STRING | Includes the <i>SuccessPSCell-Report</i> IE as defined in TS 38.331 [10] | – | |
+| >>SN Mobility Information | | | BIT STRING (SIZE (32)) | Mobility Information in the PSCell of the source SN in case this message is sent from the MN to the source SN; Mobility Information in the PSCell of the target SN in case this message is sent from the MN to the target SN. | – | |
+| <b>DL LBT Failure Information List</b> | | 0..1 | | | YES | ignore |
+| > DL LBT Failure Information Item | | 1 ..<br><maxnoof<br>LBTFailur<br>eInformati<br>on> | | | | |
+| >>DL LBT Failure Information | M | | 9.2.3.174 | | – | |
+
+| Range bound | Explanation |
+|--------------------------------------|--------------------------------------------------------------------------------------------|
+| maxnoofRACHReports | Maximum no. of RACH Reports, the maximum value is 64. |
+| maxnoofSuccessfulHOReports | Maximum no. of Successful HO Reports, the maximum value is 64. |
+| maxnoofSuccessfulPSCellChangeReports | Maximum no. of Successful PSCell Change Reports, the maximum value is 64. |
+| maxnoofLBTFailureInformation | Maximum no. of UEs for which LBT Failure Information is provided, the maximum value is 64. |
+
+### 9.1.3.26 DATA COLLECTION REQUEST
+
+This message is sent by NG-RAN node<sub>1</sub> to NG-RAN node<sub>2</sub> to initiate the requested information reporting according to the parameters given in the message.
+
+Direction: NG-RAN node<sub>1</sub> → NG-RAN node<sub>2</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------|------------------------------------------|-------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | C-<br>ifRegistrati<br>onRequest<br>Stop | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | ignore |
+| Registration Request | M | | ENUMERATED<br>(start, stop, ...) | Type of request for which the information is required. | YES | reject |
+| Report Characteristics | C-<br>ifRegistrati<br>onRequest<br>Start | | BITSTRING<br>(SIZE(32)) | Each position in the bitmap indicates the object the NG-RAN node <sub>2</sub> is requested to report.<br>First Bit = Predicted Radio Resource Status,<br>Second Bit = Predicted Number of Active UEs,<br>Third Bit = Predicted RRC Connections<br>Fourth Bit = Average UE Throughput DL,<br>Fifth Bit = Average UE Throughput UL,<br>Sixth Bit = Average Packet Delay,<br>Seventh Bit = Average Packet Loss DL<br>Eighth Bit = Energy Cost<br>Ninth Bit = Measured UE Trajectory<br>Other bits are ignored by the NG-RAN node <sub>2</sub> . | YES | reject |
+| Cell To Report List for<br>Data Collection | | 0..1 | | Cell ID list to which the request applies. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|----------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >Cell To Report Item for Data Collection | | 1 ..<br><maxno<br>ofCellsIn<br>NG-<br>RANnod<br>e> | | | – | |
+| >>Cell ID | M | | Global NG-RAN Cell Identity<br>9.2.2.27 | | – | |
+| Reporting Periodicity | O | | ENUMERATED(500ms,<br>1000ms,<br>2000ms,<br>5000ms,<br>10000ms,<br>...) | Periodicity that can be used for reporting of requested objects. Also used as the averaging window length for all objects if supported. | YES | ignore |
+| Requested Prediction Time | O | | INTEGER (1..60, ...) | For one time reporting, it indicates the point in time, measured from reception of the DATA COLLECTION REQUEST message, for which predictions are provided. For periodic reporting, it indicates the points in time, measured from the reception of the DATA COLLECTION REQUEST message and shifted by each reporting period, for which predictions are provided. (unit: second) | YES | ignore |
+| UE Trajectory Collection Configuration | O | | 9.2.3.185 | | YES | ignore |
+| UE Performance Collection Configuration | O | | 9.2.3.186 | | YES | ignore |
+
+| Condition | Explanation |
+|----------------------------|---------------------------------------------------------------------------------------------|
+| ifRegistrationRequestStop | This IE shall be present if the <i>Registration Request</i> IE is set to the value "stop". |
+| ifRegistrationRequestStart | This IE shall be present if the <i>Registration Request</i> IE is set to the value "start". |
+
+| Range bound | Explanation |
+|--------------------------|------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+### 9.1.3.27 DATA COLLECTION RESPONSE
+
+This message is sent by NG-RAN node<sub>2</sub> to NG-RAN node<sub>1</sub> to indicate that the requested information, for all or part of the measurement objects included in the reporting, is successfully initiated.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|----------------------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | reject |
+| <b>Node Measurement Initiation Result List</b> | | 0..1 | | List of measurement objects that failed to be initiated in the node. | YES | ignore |
+| > <b>Node Measurement Initiation Result Item</b> | | 1 ..<br><maxFailedMeasuresPerNode> | | | – | |
+| >>Node Measurement Failed Report Characteristics | M | | BITSTRING<br>(SIZE(128)) | Each position in the bitmap indicates measurement objects that failed to be initiated in the NG-RAN node2. First Bit = Energy Cost, Second Bit = Average UE Throughput DL, Third Bit = Average UE Throughput UL, Fourth Bit = Average Packet Delay, Fifth Bit = Average Packet Loss DL, Sixth Bit = Measured UE Trajectory. Other bits are ignored by the NG-RAN node1. | – | |
+| >>Cause | M | | 9.2.3.2 | Failure cause for measurement objects for which the measurement cannot be initiated. | – | |
+| <b>Cell Measurement Initiation Result List</b> | | 0..1 | | List of measurement objects that failed to be initiated per cell. | YES | ignore |
+| > <b>Cell Measurement Initiation Result Item</b> | | 1 ..<br><maxnumberOfCellsInNG-RANnode> | | | – | |
+| >>Cell ID | M | | Global NG-RAN Cell Identity<br>9.2.2.27 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------------------------|----------|-----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>>>Cell Measurement Failure Cause List</b> | | 0..1 | | Indicates that NG-RAN node <sub>2</sub> could not initiate the measurement for at least one of the requested measurement objects in the cell. | – | |
+| <b>>>>Cell Measurement Failure Cause Item</b> | | 1 .. <maxFailedMeasObjects> | | | – | |
+| <b>>>>>Cell Measurement Failed Report Characteristics</b> | M | | BITSTRING (SIZE(128)) | Each position in the bitmap indicates measurement objects that failed to be initiated in the NG-RAN node <sub>2</sub> .<br>First Bit = Predicted Radio Resource Status,<br>Second Bit = Predicted Number of Active UEs,<br>Third Bit = Predicted RRC Connections.<br><br>Other bits are ignored by the NG-RAN node <sub>1</sub> . | – | |
+| <b>>>>>Cause</b> | M | | 9.2.3.2 | Failure cause for measurement objects for which the measurement cannot be initiated. | – | |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------------|------------------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxFailedCellMeasObjects | Maximum number of measurement objects that can fail per measurement. Value is 124. |
+| maxFailedMeasPerNode | Maximum number of measurement objects that can fail per node. Value is 124. |
+
+### 9.1.3.28 DATA COLLECTION FAILURE
+
+This message is sent by the NG-RAN node<sub>2</sub> to NG-RAN node<sub>1</sub> to indicate that for all of the requested objects the reporting cannot be initiated.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|--------------------------|---------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.3.29 DATA COLLECTION UPDATE
+
+This message is sent by NG-RAN node<sub>2</sub> to NG-RAN node<sub>1</sub> to report the requested information.
+
+Direction: NG-RAN node<sub>2</sub> → NG-RAN node<sub>1</sub>.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|--------------------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | ignore |
+| NG-RAN node1<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>1</sub> | YES | reject |
+| NG-RAN node2<br>Measurement ID | M | | INTEGER<br>(1..4095,...) | Allocated by NG-RAN node <sub>2</sub> | YES | reject |
+| <b>Cell Measurement Result for Data Collection</b> | | 0..1 | | | YES | ignore |
+| >Cell Info Result for Data Collection Item | | 1 .. < maxnoofCells in NG-RAN node > | | | – | |
+| >>Cell ID | M | | Global NG-RAN Cell Identity<br>9.2.2.27 | | – | |
+| >>Predicted Radio Resource Status | O | | Radio Resource Status<br>9.2.2.50 | The IE only includes the SSB Area Radio Resource Status List IE, excluding the DL scheduling PDCCH CCE usage IE and UL scheduling PDCCH CCE usage IE. | – | |
+| >>Predicted Number of Active UEs | O | | Number of Active UEs<br>9.2.2.62 | | – | |
+| >>Predicted RRC Connections | O | | RRC Connections<br>9.2.2.56 | | – | |
+| <b>UE Associated Info Result List</b> | | 0..1 | | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|---------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >UE Associated Info Result Item | | 1 .. < maxnoofUEReports > | | | – | |
+| >>UE Assistant Identifier | M | | NG-RAN node UE XnAP ID 9.2.3.16 | NG-RAN node UE XnAP ID allocated by NG-RAN node <sub>1</sub> . | – | |
+| >>UE Performance | O | | 9.2.3.179 | | – | |
+| >>Measured UE Trajectory | O | | 9.2.3.182 | It contains information about cells that a UE has connected to. | – | |
+| Energy Cost | O | | INTEGER (0..10000,...) | The node level measured Energy Consumption index. Value 0 indicates the minimum measured Energy Consumption and 10000 indicates the maximum measured Energy Consumption. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------------|---------------------------------------------------------------------------------------|
+| maxnoofCellsInNG-RANnode | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+| maxnoofUEReports | Maximum no. UE s for which information can be reported by a NG-RAN node. Value is 16. |
+
+## 9.1.4 Messages for IAB Procedures
+
+### 9.1.4.1 F1-C TRAFFIC TRANSFER
+
+This message is sent by the M-NG-RAN node to the S-NG-RAN node or by the S-NG-RAN node to the M-NG-RAN node of a dual-connected IAB-node to transfer the F1-C traffic to and from the IAB-node.
+
+Direction: M-NG-RAN node → S-NG-RAN node or S-NG-RAN node → M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|------------------------|--------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| M-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID | Allocated at the M-NG-RAN node | YES | reject |
+
+| | | | | | | |
+|--------------------------|---|--|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|
+| | | | 9.2.3.16 | | | |
+| S-NG-RAN node UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | Allocated at the S-NG-RAN node | YES | reject |
+| F1-C Traffic Container | M | | OCTET STRING | Contains an F1-C interface SCTP CHUNK and IP header, or an IP packet to protect the traffic on the F1-C interface as defined in TS 33.501 [28]. | YES | reject |
+
+#### 9.1.4.2 IAB TRANSPORT MIGRATION MANAGEMENT REQUEST
+
+This message is sent by an F1-terminating IAB-donor to a non-F1-terminating IAB-donor of a boundary IAB-node, for the purpose of setting up, modifying, or releasing (e.g., for the purpose of revoking) the configuration for the migration of boundary and descendant node traffic between two IAB-donors.
+
+Direction: F1-terminating IAB-donor → non-F1-terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|--------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-Terminating IAB-donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Source NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID, or to the S-NG-RAN node UE XnAP ID. | YES | reject |
+| Non-F1-Terminating IAB-donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID, or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| Traffic To Be Added List | | 0..1 | | | YES | reject |
+| >Traffic To Be Added Item | | 1 .. <maxnoof TrafficInd exEntries > | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Traffic Profile | M | | 9.2.2.81 | | – | |
+| >>F1-terminating Topology BH Information | O | | 9.2.2.82 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-----------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Traffic To Be Modified List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic To Be Modified Item</b> | | 1 .. <maxnoofTrafficIndexEntries> | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Traffic Profile | O | | 9.2.2.81 | | – | |
+| >>F1-terminating Topology BH Information | O | | 9.2.2.82 | | – | |
+| Traffic To Be Released Information | O | | 9.2.2.84 | | YES | reject |
+| IAB TNL Address Request | O | | 9.2.2.85 | | YES | reject |
+| IAB TNL Address Exception | O | | 9.2.2.98 | | YES | reject |
+| Mobile IAB-MT BAP Address | O | | BAP Address 9.2.2.89 | This IE is only present when the F1-terminating IAB-donor only has the BAP address of the IAB-MT, but not the UE XnAP ID assigned by the Non-F1-Terminating IAB-donor for the IAB-MT. | YES | reject |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------------------------------------|
+| maxnoofTrafficIndexEntries | Maximum no. of traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+
+#### 9.1.4.3 IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE
+
+This message is sent by the non-F1-terminating IAB-donor to the F1-terminating IAB-donor of a boundary IAB-node to provide inter-donor transport related configurations for the offloaded traffic.
+
+Direction: non-F1-terminating IAB-donor → F1-terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|-------|---------------------------------|--------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-Terminating IAB-Donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Source NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID, or to the S-NG-RAN node UE | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|--------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | XnAP ID. | | |
+| Non-F1-Terminating IAB-Donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID, or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| <b>Traffic Added List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic Added Item</b> | | 1 ..<br><maxnoof<br>TrafficInd<br>exEntries<br>> | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Non-F1-terminating Topology BH Information | M | | 9.2.2.83 | | – | |
+| <b>Traffic Modified List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic Modified Item</b> | | 1 ..<br><maxnoof<br>TrafficInd<br>exEntries<br>> | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Non-F1-terminating Topology BH Information | M | | 9.2.2.83 | | – | |
+| <b>Traffic Not Added List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic Not Added Item</b> | | 1 ..<br><maxnoof<br>TrafficInd<br>exEntries<br>> | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Cause | O | | 9.2.3.2 | | – | |
+| <b>Traffic Not Modified List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic Not Modified Item</b> | | 1 ..<br><maxnoof<br>TrafficInd<br>exEntries<br>> | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Cause | O | | 9.2.3.2 | | – | |
+| IAB TNL Address Response | O | | 9.2.2.86 | | YES | reject |
+| <b>Traffic Released List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic Released Item</b> | | 1 ..<br><maxnoof<br>TrafficInd<br>exEntries<br>> | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>BH Info List | O | | 9.2.2.99 | | – | |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------------------------------------|
+| maxnoofTrafficIndexEntries | Maximum no. of traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+
+### 9.1.4.3a IAB TRANSPORT MIGRATION MANAGEMENT REJECT
+
+This message is sent by the non-F1-terminating IAB-donor to inform the F1-terminating IAB-donor that the IAB Transport Migration Management procedure has failed.
+
+Direction: Non-F1-terminating IAB-donor → F1-terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-Terminating IAB-Donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Source NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID, or to the S-NG-RAN node UE XnAP ID. | YES | reject |
+| Non-F1-Terminating IAB-Donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID, or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| Cause | M | | 9.2.3.2 | | YES | ignore |
+| Criticality Diagnostics | O | | 9.2.3.3 | | YES | ignore |
+
+### 9.1.4.4 IAB TRANSPORT MIGRATION MODIFICATION REQUEST
+
+This message is sent by a non-F1-terminating IAB-donor to an F1-terminating IAB-donor of a boundary IAB-node, for the purpose of modifying or releasing (e.g., for the purpose of revoking) the configuration for the migrated traffic of boundary IAB-node or descendant IAB-node.
+
+Direction: non-F1-terminating IAB-donor → F1-terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|-------|------------------------|----------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-Terminating IAB-donor UE XnAP ID | M | | NG-RAN node UE XnAP ID | This IE refers to the Source NG- | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|------------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | 9.2.3.16 | RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID, or to the S-NG-RAN node UE XnAP ID. | | |
+| Non-F1-Terminating IAB-donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID, or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| <b>Traffic Required To Be Modified List</b> | | 0..1 | | | YES | reject |
+| > <b>Traffic Required To Be Modified Item</b> | | 1 .. <maxnoof TrafficIndexEntries> | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>Non-F1-terminating topology BH information | M | | 9.2.2.83 | | – | |
+| Traffic To Be Released Information | O | | 9.2.2.84 | | YES | reject |
+| IAB TNL Address To Be Added | O | | IAB TNL Address Response 9.2.2.86 | | YES | reject |
+| <b>IAB TNL Address To Be Released List</b> | | 0..1 | | | YES | reject |
+| > <b>IAB TNL Address To Be Released Item</b> | | 1..<maxno ofTLAsIAB> | | | – | |
+| >>IAB TNL Address | M | | 9.2.2.92 | | – | |
+| IAB Authorization Status | O | | ENUMERATED (authorized, not authorized, ...) | Indicates the IAB node's authorization status. | YES | ignore |
+| Mobile IAB Authorization Status | O | | 9.2.2.105 | | YES | ignore |
+
+| Range bound | Explanation |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofTrafficIndexEntries | Maximum no. of traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+| maxnoofTLAsIAB | Maximum total no. of IPv4 address(es), IPv6 address(es) and IPv6 address prefix(es) that can be requested in one procedure execution. The value is 1024. |
+
+### 9.1.4.5 IAB TRANSPORT MIGRATION MODIFICATION RESPONSE
+
+This message is sent by the F1-terminating IAB-donor to the non-F1-terminating IAB-donor of a boundary IAB-node to acknowledge the update of configuration requested by the non-F1-terminating IAB-donor.
+
+Direction: F1-terminating IAB-donor → non-F1-terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-Terminating IAB-donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Source NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID, or to the S-NG-RAN node UE XnAP ID. | YES | reject |
+| Non-F1-Terminating IAB-donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID, or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| Traffic Required Modified List | | 0..1 | | | YES | reject |
+| >Traffic Required Modified Item | | 1 .. <maxnoof TrafficIndexEntries > | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| Traffic Released List IE | | 0..1 | | | YES | reject |
+| >Traffic Released Item | | 1 .. <maxnoof TrafficIndexEntries > | | | – | |
+| >>Traffic Index | M | | 9.2.2.80 | | – | |
+| >>BH Info List | O | | 9.2.2.99 | | – | |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------------------------------------|
+| maxnoofTrafficIndexEntries | Maximum no. of traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+
+### 9.1.4.6 IAB RESOURCE COORDINATION REQUEST
+
+This message is sent by an F1-terminating/non-F1-terminating IAB-donor to a non-F1-terminating/F1-terminating IAB-donor of a boundary IAB-node, for the purpose of coordination of the semi-static resources of a single or dual-
+
+connected boundary IAB-node.
+
+Direction: F1-terminating IAB-donor → non-F1-terminating IAB-donor, non-F1-terminating IAB-donor→F1-terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|------------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-terminating IAB-Donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Source NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID. | YES | reject |
+| Non F1-terminating IAB-Donor UE XnAP ID | M | | NG-RAN node UE XnAP ID 9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| <b>Boundary Node Cells List</b> | | 0..1 | | List of cells served by the boundary IAB-node IAB-DU. | YES | reject |
+| > <b>Boundary Node Cells List Item</b> | | 1 .. <maxnoofServedCellsIAB> | | | EACH | reject |
+| >>Boundary Node Cell Information | M | | IAB Cell Information 9.2.2.94 | | – | |
+| <b>Parent Node Cells List</b> | | 0..1 | | List of cells served by the parent node IAB-DU. | YES | reject |
+| > <b>Parent Node Cells List Item</b> | | 1 .. <maxnoofServingCells> | | | EACH | reject |
+| >>Parent Node Cell Information | M | | IAB Cell Information 9.2.2.94 | | – | |
+
+| Range bound | Explanation |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------|
+| maxnoofServedCellsIAB | Maximum number of cells served by an IAB-DU. Value is 512. |
+| maxnoofServingCells | Maximum no. of serving cells for an IAB-MT. Value is 32, as defined by the <i>maxNrofServingCells</i> in TS 38.331 [10]. |
+
+#### 9.1.4.7 IAB RESOURCE COORDINATION RESPONSE
+
+This message is sent by a non-F1-terminating/F1-terminating IAB-donor to an F1-terminating/non-F1-terminating IAB-donor of a boundary IAB-node, in response to an IAB RESOURCE COORDINATION REQUEST message.
+
+Direction: non-F1-terminating IAB-donor → F1-terminating IAB-donor, F1-terminating IAB-donor → non-F1-
+
+terminating IAB-donor.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type | M | | 9.2.3.1 | | YES | reject |
+| F1-terminating IAB-Donor node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | This IE refers to the Source NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID. | YES | reject |
+| Non F1-terminating IAB-Donor node UE XnAP ID | M | | NG-RAN node UE XnAP ID<br>9.2.3.16 | This IE refers to the Target NG-RAN node UE XnAP ID or to the S-NG-RAN node UE XnAP ID or to the M-NG-RAN node UE XnAP ID. | YES | reject |
+| <b>Boundary Node Cells List</b> | | 0..1 | | List of cells served by the boundary IAB-node IAB-DU. | YES | reject |
+| >Boundary Node Cells List Item | | 1 .. <maxnoofServedCellsIAB> | | | EACH | reject |
+| >>Boundary Node cell Information | M | | IAB Cell Information<br>9.2.2.94 | | – | |
+| <b>Parent-Node Cells List</b> | | 0..1 | | List of cells served by the parent node IAB-DU. | YES | reject |
+| >Parent-Node Cells List Item | | 1 .. <maxnoofServingCells> | | | EACH | reject |
+| >>Parent Node Cell Information | M | | IAB Cell Information<br>9.2.2.94 | | – | |
+
+| Range bound | Explanation |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------|
+| maxnoofServedCellsIAB | Maximum number of cells served by an IAB-DU. Value is 512. |
+| maxnoofServingCells | Maximum no. of serving cells for an IAB-MT. Value is 32, as defined by the <i>maxNrofServingCells</i> in TS 38.331 [10]. |
+
+## 9.2 Information Element definitions
+
+### 9.2.0 General
+
+When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:
+
+- The first bit (leftmost bit) contains the most significant bit (MSB);
+- The last bit (rightmost bit) contains the least significant bit (LSB);
+- When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information.
+
+## 9.2.1 Container and List IE definitions
+
+### 9.2.1.1 PDU Session Resources To Be Setup List
+
+This IE contains PDU session resource related information used at UE context transfer between NG-RAN nodes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|-----------------------------|-------------------------------------------------|------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>PDU Session Resources To Be Setup List</b> | | 1 | | | – | |
+| > <b>PDU Session Resources To Be Setup Item</b> | | 1 .. <maxnoof PDU sessions> | | | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >>S-NSSAI | M | | 9.2.3.21 | | – | |
+| >>PDU Session Resource Aggregate Maximum Bitrate | O | | PDU Session Aggregate Maximum Bit Rate 9.2.3.69 | This IE shall be present when at least one Non-GBR QoS Flow has been setup. | – | |
+| >>UL NG-U UP TNL Information at UPF | M | | UP Transport Layer Information 9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs | – | |
+| >>Source DL NG-U TNL Information | O | | UP Transport Layer Information 9.2.3.30 | Indicates the possibility to keep the NG-U GTP-U tunnel termination point at the target NG-RAN node. | – | |
+| >>Security Indication | O | | 9.2.3.52 | | – | |
+| >>PDU Session Type | M | | 9.2.3.19 | | – | |
+| >>Network Instance | O | | 9.2.3.85 | This IE is ignored if the <i>Common Network Instance</i> IE is present. | – | |
+| >>QoS Flows To Be Setup List | | 1 | | | – | |
+| >>>QoS Flows To Be Setup Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>QoS Flow Level QoS | M | | 9.2.3.5 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------------------|----------|-------|----------------------------------------------------|---------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Parameters | | | | | | |
+| >>>>E-RAB ID | O | | INTEGER (0..15, ...) | | – | |
+| >>>>TSC Traffic Characteristics | O | | 9.2.3.114 | Traffic pattern information associated with the QFI. Details in TS 23.501 [7]. | YES | ignore |
+| >>>>Redundant QoS Flow Indicator | O | | 9.2.3.118 | | YES | ignore |
+| >>>>ECN Marking or Congestion Information Reporting Request | O | | 9.2.3.205 | | YES | ignore |
+| >>Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | | – | |
+| >>Additional UL NG-U UP TNL Information at UPF List | O | | Additional UP Transport Layer Information 9.2.1.32 | Additional UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs | YES | ignore |
+| >> Common Network Instance | O | | 9.2.3.92 | | YES | ignore |
+| >>Redundant UL NG-U UP TNL Information at UPF | O | | UP Transport Layer Information 9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs for the redundant transmission | YES | ignore |
+| >>Additional Redundant UL NG-U UP TNL Information at UPF List | O | | Additional UP Transport Layer Information 9.2.1.32 | Additional Redundant UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs | YES | ignore |
+| >>Redundant Common Network Instance | O | | Common Network Instance 9.2.3.92 | | YES | ignore |
+| >>Redundant PDU Session Information | O | | 9.2.3.112 | | YES | ignore |
+| >>MBS Session Associated Information | O | | 9.2.1.37 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|----------------------------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value |
+
+| | |
+|--|--------|
+| | is 64. |
+|--|--------|
+
+### 9.2.1.2 PDU Session Resources Admitted List
+
+This IE contains PDU session resource related information to report success of the establishment of PDU session resources.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------------------|----------|-------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>PDU Session Resources Admitted List</b> | | 1 | | | – | |
+| > <b>PDU Session Resources Admitted Item</b> | | 1..<maxnoofPDUSessions> | | | – | |
+| >>PDU Session ID | M | | 9.2.3.18 | | – | |
+| >> <b>PDU Session Resource Admitted Info</b> | M | | | | – | |
+| >>>DL NG-U TNL Information Unchanged | O | | ENUMERATED (True, ...) | Indicates the NG-U tunnels that have been kept unchanged at the target NG-RAN node | – | |
+| >>> <b>QoS Flows Admitted List</b> | | 1 | | | – | |
+| >>>> <b>QoS Flows Admitted Item</b> | | 1..<maxnoofQoSFlows> | | | – | |
+| >>>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>>Current QoS Parameters Set Index | O | | 9.2.3.103 | Index to the currently fulfilled alternative QoS parameters set. | YES | ignore |
+| >>>QoS Flows not Admitted List | O | | QoS Flow List with Cause 9.2.1.4 | | – | |
+| >>>Data Forwarding Info from target NG-RAN node | O | | 9.2.1.16 | | – | |
+| >>>Secondary Data Forwarding Info from target NG-RAN node List | O | | 9.2.1.31 | This IE would be present only when the target M-NG-RAN node decide to split a PDU session between MN and SN | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-----------------------------------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.1.3 PDU Session Resources Not Admitted List
+
+This IE contains a list of PDU session resources which were not admitted to be added or modified.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|-------------------------|-----------------------|-----------------------|
+| <b>PDU Session Resources Not Admitted List</b> | | 1 | | |
+| >PDU Session Resources Not Admitted Item | | 1..<maxnoofPDUSessions> | | |
+| >>PDU Session ID | M | | 9.2.3.18 | |
+| >>Cause | O | | 9.2.3.2 | |
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------|
+| maxnoofPDUSessions | Maximum no. of PDU sessions. Value is 256 |
+
+### 9.2.1.4 QoS Flow List with Cause
+
+This IE contains a list of QoS flows with a cause value.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|----------------------|-----------------------|-----------------------|
+| <b>QoS Flow with Cause Item</b> | | 1..<maxnoofQoSFlows> | | |
+| >QoS Flow Identifier | M | | 9.2.3.10 | |
+| >Cause | O | | 9.2.3.2 | |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.1.4a QoS Flow List
+
+This IE contains a list of QoS flows.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|----------------------|-----------------------|-----------------------|
+| <b>QoS Flow Item</b> | | 1..<maxnoofQoSFlows> | | |
+| >QoS Flow Identifier | M | | 9.2.3.10 | |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.1.5 PDU Session Resource Setup Info – SN terminated
+
+This IE contains information for the addition of S-NG-RAN node resources related to a PDU session for DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------------|-------------|----------------------|
+| UL NG-U UP TNL Information at UPF | M | | UP Transport Layer Information 9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs | – | |
+| PDU Session Type | M | | 9.2.3.19 | | – | |
+| Network Instance | O | | 9.2.3.85 | This IE shall be ignored if the <i>Common Network Instance</i> IE is present. | – | |
+| <b>QoS Flows To Be Setup List</b> | | 1 | | | – | |
+| >QoS Flow To Be Setup Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>QoS Flow Level QoS Parameters | M | | 9.2.3.5 | For GBR QoS flows, this IE contains GBR QoS flow information as received at NG-C | – | |
+| >>Offered GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains M-Node offered GBR QoS Flow Information. | – | |
+| >>TSC Traffic Characteristics | O | | 9.2.3.114 | Traffic pattern information associated with the QFI. Details in TS 23.501 [7]. | YES | ignore |
+| >>Redundant QoS Flow Indicator | O | | 9.2.3.118 | | YES | ignore |
+| Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | | – | |
+| Security Indication | O | | 9.2.3.52 | | – | |
+| Security Result | O | | 9.2.3.67 | Indicates security activation status in MN. | YES | reject |
+| Common Network Instance | O | | 9.2.3.92 | | YES | ignore |
+| Default DRB Allowed | O | | 9.2.3.93 | | YES | ignore |
+| Split Session Indicator | O | | 9.2.3.94 | | YES | reject |
+| Non-GBR Resources Offered | O | | 9.2.3.98 | | YES | ignore |
+| Redundant UL NG-U UP TNL Information at UPF | O | | UP Transport Layer Information 9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs for the redundant transmission. | YES | ignore |
+| Redundant Common | O | | Common | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|---------------------------|--------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Network Instance | | | Network Instance 9.2.3.92 | | | |
+| Redundant PDU Session Information | O | | 9.2.3.112 | | YES | ignore |
+| Selected NID | O | | NID 9.2.2.65 | This IE, together with the <i>Selected PLMN IE</i> , indicates the SNPN proposed for the SCG to the S-NG-RAN node. | YES | ignore |
+
+| Range bound | Explanation |
+|-----------------|---------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows. Value is 64 |
+
+### 9.2.1.6 PDU Session Resource Setup Response Info – SN terminated
+
+This IE contains the result of the addition of S-NG-RAN node resources related to a PDU session for DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|---------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| DL NG-U UP TNL Information at NG-RAN | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of the NG transport bearer. For delivery of DL PDUs. | – | |
+| <b>DRBs To Be Setup List</b> | | 0..1 | | | – | |
+| >DRBs to Be Setup Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN UL PDCP UP TNL Information | M | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>DRB QoS | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>PDCP SN Length | O | | 9.2.3.63 | Indicates the PDCP SN length of the DRB. | – | |
+| >>RLC Mode | M | | 9.2.3.28 | Indicates the RLC mode to be used in the assisting node. | – | |
+| >>secondary SN UL | O | | UP Transport | S-NG-RAN node | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|-------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| PDCP UP TNL Information | | | Parameters 9.2.3.76 | endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP duplication. | | |
+| >>Duplication Activation | O | | 9.2.3.71 | Information on the initial state of UL PDCP duplication. This IE is ignored if the <i>RLC Duplication Information</i> IE is present. | – | |
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the M-NG-RAN node. This IE is used when the concerned DRB has both MCG resource and SCG resource configured i.e. the concerned DRB is configured as split bearer. | – | |
+| >>QoS Flows Mapped To DRB List | | 1 | | | – | |
+| >>>QoS Flows Mapped To DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>MCG requested GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains GBR QoS Flow Information necessary for the MCG part. | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >>>>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.2.3.103 | | YES | ignore |
+| >>>>Source DL Forwarding IP Address | O | | Transport Layer Address 9.2.3.29 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore |
+| >>Additional PDCP Duplication TNL | | 0..1 | | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|----------------------------------------------|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>List</b> | | | | | | |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP duplication. | – | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | . | – | |
+| Data Forwarding Info from target NG-RAN node | O | | 9.2.1.16 | | – | |
+| QoS Flows Not Admitted List | O | | QoS Flow List with Cause 9.2.1.4 | | – | |
+| Security Result | O | | 9.2.3.67 | | – | |
+| DRB IDs taken into use | O | | DRB List 9.2.1.29 | Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8]. | YES | reject |
+| Redundant DL NG-U UP TNL Information at NG-RAN | O | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of the NG transport bearer. For delivery of DL PDUs for the redundant transmission. | YES | ignore |
+| Used RSN Information | O | | Redundant PDU Session Information 9.2.3.112 | | YES | ignore |
+| Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | Contains data forwarding proposal for S-CPAC, to be used later when the S-NG-RAN node is selected for access. | YES | ignore |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows. Value is 64 |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.7 PDU Session Resource Setup Info – MN terminated
+
+This IE contains information for the addition of S-NG-RAN node resources related to a PDU session for DRBs configured with an MN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|---------------------|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| PDU Session Type | M | | 9.2.3.19 | | – | |
+| <b>DRBs To Be Setup List</b> | | 1 | | | – | |
+| >DRBs to Be Setup Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>MN UL PDCP UP TNL Information | M | | UP Transport Parameters 9.2.3.76 | M-NG-RAN node endpoint(s) of a DRB's Xn-U transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>RLC Mode | M | | 9.2.3.28 | Indicates the RLC mode to be used in the assisting node. | – | |
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the S-NG-RAN node. This IE is used when the concerned DRB has both MCG resource and SCG resource configured i.e. the concerned DRB is configured as split bearer. | – | |
+| >>DRB QoS | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>PDCP SN Length | O | | 9.2.3.63 | Indicates the PDCP SN length of the DRB. | – | |
+| >>secondary MN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP duplication. | – | |
+| >>Duplication Activation | O | | 9.2.3.71 | Information on the initial state of UL PDCP duplication. This IE is ignored | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | if the <i>RLC Duplication Information</i> IE is present. | | |
+| >>QoS Flows Mapped To DRB List | | 1 | | | – | |
+| >>>QoS Flows Mapped To DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>QoS Flow Level QoS Parameters | M | | 9.2.3.5 | | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >>>>TSC Traffic Characteristics | O | | 9.2.3.114 | Traffic pattern information associated with the QFI. Details in TS 23.501 [7]. | YES | ignore |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP duplication. | – | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------------------------------|-----------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.8 PDU Session Resource Setup Response Info – MN terminated
+
+This IE contains the result of the addition of S-NG-RAN node resources related to a PDU session for DRBs configured
+
+with an MN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|---------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>DRBs Admitted List</b> | | 1 | | | – | |
+| > <b>DRBs Admitted Item</b> | | 1 ..<br><maxnoof<br>DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN DL SCG UP<br>TNL Information | M | | UP Transport<br>Parameters<br>9.2.3.76 | S-NG-RAN node<br>GTP-U tunnel<br>endpoint(s) of the<br>DRB's Xn<br>transport at its<br>Lower Layer SCG<br>resource. For<br>delivery of DL<br>PDUs. | – | |
+| >>secondary SN DL<br>SCG UP TNL<br>Information | O | | UP Transport<br>Parameters<br>9.2.3.76 | S-NG-RAN node<br>GTP-U tunnel<br>endpoint(s) of the<br>DRB's Xn<br>transport at its<br>Lower Layer SCG<br>resource. For<br>delivery of DL<br>PDUs in case of<br>PDCP duplication. | – | |
+| >>LCID | O | | 9.2.3.70 | LCID for primary<br>path or LCID for<br>split secondary<br>path for fallback to<br>split bearer if<br>PDCP duplication<br>is applied | – | |
+| >>Additional PDCP<br>Duplication TNL<br>List | | 0..1 | | | YES | ignore |
+| >>>Additional<br>PDCP Duplication<br>TNL Item | | 1 ..<br><maxnoof<br>Additional<br>PDCPDup<br>licationTN<br>L> | | | – | |
+| >>>>Additional<br>PDCP Duplication<br>UP TNL<br>Information | M | | UP Transport<br>Layer<br>Information<br>9.2.3.30 | S-NG-RAN node<br>GTP-U tunnel<br>endpoint(s) of the<br>DRB's Xn<br>transport at its<br>Lower Layer SCG<br>resource. For<br>delivery of DL<br>PDUs in case of<br>additional PDCP<br>duplication. | – | |
+| >>QoS Flows<br>Mapped To DRB<br>List | | 0..1 | | | YES | ignore |
+| >>>QoS Flows | | 1 .. | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|---------------------|---------------------------------------------------|-----------------------|-------------|----------------------|
+| <b>Mapped To DRB Item</b> | | <maxnoof QoSFlows > | | | | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>Current QoS Parameters Set Index | M | | Alternative QoS Parameters Set Index<br>9.2.3.103 | | – | |
+| DRBs Not Admitted To Be Setup or Modified List | O | | DRB List with Cause<br>9.2.1.28 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------------------------------|------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2 |
+
+### 9.2.1.9 PDU Session Resource Modification Info – SN terminated
+
+This IE contains information related to a PDU session resource for an M-NG-RAN node initiated request to modify DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|--------------------------|--------------------------------------------|-----------------------------------------------------------------------------------|-------------|----------------------|
+| UL NG-U UP TNL Information at UPF | O | | UP Transport Layer Information<br>9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs | – | |
+| Network Instance | O | | 9.2.3.85 | This IE shall be ignored if the <i>Common Network Instance</i> IE is present. | – | |
+| <b>QoS Flows To Be Setup List</b> | | 0..1 | | | – | |
+| >QoS Flows To Be Setup Item | | 1 .. <maxnoof QoSFlows > | | | – | |
+| >>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>QoS Flow Level QoS Parameters | M | | 9.2.3.5 | For GBR QoS flows, this IE contains GBR QoS flow information as received at NG-C. | – | |
+| >>Offered GBR QoS Flow Information | O | | GBR QoS Flow Information<br>9.2.3.6 | This IE contains M-Node offered GBR QoS Flow Information. | – | |
+| >>TSC Traffic Characteristics | O | | 9.2.3.114 | Traffic pattern information associated with | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|-------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | the QFI. Details in TS 23.501 [7]. | | |
+| >>Redundant QoS Flow Indicator | O | | 9.2.3.118 | | YES | ignore |
+| Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | Applicable for the QoS flows contained in the <i>QoS Flows To Be Setup List</i> IE. | – | |
+| <b>QoS Flows To Be Modified List</b> | | 0..1 | | | – | |
+| > <b>QoS Flows To Be Modified Item</b> | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>QoS Flow Level QoS Parameters | O | | 9.2.3.5 | For GBR QoS flows, this IE contains GBR QoS flow information as received at NG-C. | – | |
+| >>Offered GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains M-Node offered GBR QoS Flow Information. | – | |
+| >>QoS Flow Mapping Indication | O | | 9.2.3.79 | This IE is not applicable in this version of the specification. | – | |
+| >>TSC Traffic Characteristics | O | | 9.2.3.114 | Traffic pattern information associated with the QFI. Details in TS 23.501 [7]. | YES | ignore |
+| >>Redundant QoS Flow Indicator | O | | 9.2.3.118 | | YES | ignore |
+| <b>QoS Flows To Be Released List</b> | | 0..1 | QoS Flow List with Cause 9.2.1.4 | | – | |
+| <b>DRBs To Be Modified List</b> | | 0..1 | | | – | |
+| > <b>DRBs to Be Modified Item</b> | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>MN DL CG UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | M-NG-RAN node GTP-U endpoint(s) of a DRB's Xn transport bearer at its lower layer CG resource. For delivery of DL PDUs. | – | |
+| >>secondary MN DL CG UP TNL | O | | UP Transport Parameters | M-NG-RAN node GTP-U endpoint(s) | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Information | | | 9.2.3.76 | of a DRB's Xn transport bearer at its lower layer CG resource. For delivery of DL PDUs in case of PDCP duplication. | | |
+| >>LCID | O | | 9.2.3.70 | LCID for primary path or LCID for split secondary path for fallback to split bearer if PDCP duplication is applied | – | |
+| >>RLC Status | O | | 9.2.3.80 | | – | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | M-NG-RAN node GTP-U endpoint(s) of a DRB's Xn transport bearer at its lower layer CG resource. For delivery of DL PDUs in case of additional PDCP duplication. | – | |
+| DRBs To Be Released List | O | | DRB List with Cause 9.2.1.28 | | – | |
+| Common Network Instance | O | | 9.2.3.92 | | YES | ignore |
+| Default DRB Allowed | O | | 9.2.3.93 | | YES | ignore |
+| Non-GBR Resources Offered | O | | 9.2.3.98 | | YES | ignore |
+| Redundant UL NG-U UP TNL Information at UPF | O | | UP Transport Layer Information 9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs for the redundant transmission | YES | ignore |
+| Redundant Common Network Instance | O | | Common Network Instance 9.2.3.92 | | YES | ignore |
+| Security Indication | O | | 9.2.3.52 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|-------------|
+|-------------|-------------|
+
+| | |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows. Value is 64. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.10 PDU Session Resource Modification Response Info – SN terminated
+
+This IE contains the PDU session resource related result of an M-NG-RAN node initiated request to modify DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|---------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| DL NG-U UP TNL Information at NG-RAN | O | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of the NG transport bearer. For delivery of DL PDUs. | – | |
+| <b>DRBs To Be Setup List</b> | | 0..1 | | | – | |
+| >DRBs to Be Setup Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN UL PDCP UP TNL Information | M | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>DRB QoS | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>PDCP SN Length | O | | 9.2.3.63 | Indicates the PDCP SN length of the DRB. | – | |
+| >>RLC Mode | M | | 9.2.3.28 | Indicates the RLC mode to be used in the assisting node. | – | |
+| >>secondary SN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP duplication. | – | |
+| >>Duplication Activation | O | | 9.2.3.71 | Information on the initial state of UL PDCP duplication. This IE is ignored if the <i>RLC Duplication Information</i> IE is present. | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the M-NG-RAN node. This IE is used when the concerned DRB has both MCG resource and SCG resource configured i.e. the concerned DRB is configured as split bearer. | – | |
+| >>QoS Flows Mapped To DRB List | | 1 | | | – | |
+| >>>QoS Flows Mapped To DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>MCG requested GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains GBR QoS Flow Information necessary for the MCG part. | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >>>>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.2.3.103 | | YES | ignore |
+| >>>>Source DL Forwarding IP Address | O | | Transport Layer Address 9.2.3.29 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-----------------------------------|------------------------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | duplication. | | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | | YES | ignore |
+| Data Forwarding Info from target NG-RAN node | O | | 9.2.1.16 | Applicable for the QoS flows in DRBs to be setup. | – | |
+| <b>DRBs To Be Modified List</b> | | 0..1 | | | – | |
+| >DRBs To Be Modified Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>DRB QoS | O | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>QoS Flows Mapped to DRB List | | 0..1 | | Overwriting the existing QoS Flow List | – | |
+| >>>QoS Flows Mapped to DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>MCG requested GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains GBR QoS Flow Information necessary for the MCG part. | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >>>>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.2.3.103 | | YES | ignore |
+| >>>>Source DL Forwarding IP Address | O | | Transport Layer Address 9.2.3.29 | Identifies the TNL address used by the source node for data forwarding. | YES | ignore |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDup> | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------|----------|------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | <i>licationTNL></i> | | | | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP duplication. | – | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | | YES | ignore |
+| >>secondary SN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP duplication. | YES | ignore |
+| >>PDCP Duplication Configuration | O | | 9.2.3.86 | | YES | ignore |
+| >>Duplication Activation | O | | 9.2.3.71 | | YES | ignore |
+| DRBs To Be Released List | O | | DRB List with Cause 9.2.1.28 | | – | |
+| Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | Contains DL Data Forwarding indications for QoS Flows removed from the SDAP in the SN. | – | |
+| QoS Flows Not Admitted to be Added List | O | | QoS Flow List with Cause 9.2.1.4 | | – | |
+| QoS Flows Released List | O | | QoS Flow List with Cause 9.2.1.4 | | – | |
+| DRB IDs taken into use | O | | DRB List 9.2.1.29 | Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8]. | YES | reject |
+| Redundant DL NG-U UP TNL Information at NG-RAN | O | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of the NG transport bearer. For delivery of DL PDUs for the redundant transmission. | YES | ignore |
+| Security Result | O | | 9.2.3.67 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows. Value is 64. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.11 PDU Session Resource Modification Info – MN terminated
+
+This IE contains information related to PDU session resource for an M-NG-RAN node initiated request to modify DRBs configured with an MN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|--------------------------|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| PDU Session Type | M | | 9.2.3.19 | | – | |
+| <b>DRBs To Be Setup List</b> | | 0..1 | | | – | |
+| >DRBs to Be Setup Item | | 1..<br><maxnoof<br>DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>MN UL PDCP UP TNL Information | M | | UP Transport Parameters 9.2.3.76 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>RLC Mode | M | | 9.2.3.28 | Indicates the RLC mode to be used in the assisting node. | – | |
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the S-NG-RAN node. This IE is used when the concerned DRB has both MCG resource and SCG resource configured i.e. the concerned DRB is configured as split bearer. | – | |
+| >>DRB QoS | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>PDCP SN Length | O | | 9.2.3.63 | Indicates the PDCP SN length of the DRB. | – | |
+| >>secondary MN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | delivery of UL PDUs in case of PDCP duplication. | | |
+| >>Duplication Activation | O | | 9.2.3.71 | Information on the initial state of UL PDCP duplication. This IE is ignored if the <i>RLC Duplication Information</i> IE is present. | – | |
+| >>QoS Flows Mapped to DRB List | | 1 | | | – | |
+| >>>QoS Flows Mapped To DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>QoS Flow Level QoS Parameters | M | | 9.2.3.5 | | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP duplication. | – | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | | YES | ignore |
+| <b>DRBs To Be Modified List</b> | | 0..1 | | | – | |
+| >DRBs to Be Modified Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>MN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|---------------------------------------------------|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | resource. For delivery of UL PDUs. | | |
+| >>DRB QoS | O | | QoS Flow Level<br>QoS Parameters<br>9.2.3.5 | | – | |
+| >>secondary MN UL PDCP UP TNL Information | O | | UP Transport Parameters<br>9.2.3.76 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP duplication. | – | |
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the S-NG-RAN node. | – | |
+| >>PDCP Duplication Configuration | O | | 9.2.3.86 | | – | |
+| >>Duplication Activation | O | | 9.2.3.71 | Information on the initial state of UL PDCP duplication. This IE is ignored if the <i>RLC Duplication Information</i> IE is present. | – | |
+| >>>QoS Flows Mapped To DRB List | | 0..1 | | Overwriting the existing QoS Flow List | – | |
+| >>>QoS Flows Mapped To DRB Item | | 1 ..<br><maxnoof QoS Flows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>QoS Flow Level QoS Parameters | M | | 9.2.3.5 | | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 ..<br><maxnoof Additional PDCP Duplication TNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information<br>9.2.3.30 | M-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|------------------------------|------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | its PDCP resource. For delivery of UL PDUs in case of additional PDCP duplication. | | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | | YES | ignore |
+| DRBs To Be Released List | O | | DRB List with Cause 9.2.1.28 | | – | |
+
+| Range bound | Explanation |
+|-------------------------------------|-----------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+## 9.2.1.12 PDU Session Resource Modification Response Info – MN terminated
+
+This IE contains the PDU session resource related result of an M-NG-RAN node initiated modification of DRBs configured with an MN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------|----------|---------------------|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>DRBs Admitted to be Setup or Modified List</b> | | 1 | | | – | |
+| >DRBs Admitted to be Setup or Modified Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN DL SCG UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node GTP-U tunnel endpoint(s) of the DRB's Xn transport at its Lower Layer SCG resource. For delivery of DL PDUs. | – | |
+| >>secondary SN DL SCG UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node GTP-U tunnel endpoint(s) of the DRB's Xn transport at its Lower Layer SCG resource. For delivery of DL PDUs in case of PDCP duplication. | – | |
+| >>LCID | O | | 9.2.3.70 | LCID for primary path or LCID for split secondary path for fallback to split bearer if | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | PDCP duplication is applied | | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node GTP-U tunnel endpoint(s) of the DRB's Xn transport at its Lower Layer SCG resource. For delivery of DL PDUs in case of additional PDCP duplication. | – | |
+| >>QoS Flows Mapped To DRB List | | 0..1 | | | YES | ignore |
+| >>>QoS Flows Mapped To DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.2.3.103 | | – | |
+| DRBs Released List | O | | DRB List 9.2.1.29 | | – | |
+| DRBs Not Admitted To Be Setup or Modified List | O | | DRB List with Cause 9.2.1.28 | | – | |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.13 UE Context Information – Retrieve UE Context Response
+
+This IE contains the UE context information within the RETRIEVE UE CONTEXT RESPONSE message.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------|-------------------------|--------------------------------------------------|-------------|----------------------|
+| NG-C UE associated Signalling reference | M | | AMF UE NGAP ID 9.2.3.26 | Allocated at the AMF on the old NG-C connection. | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------|----------|-------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Signalling TNL Association Address at source NG-C side | M | | CP Transport Layer Information 9.2.3.31 | This IE indicates the AMF's IP address of the SCTP association used at the source NG-C interface instance.<br>NOTE: If no UE TNLA binding exists at the source NG-RAN node, the source NG-RAN node indicates the TNL association address it would have selected if it would have had to create a UE TNLA binding. | – | |
+| UE Security Capabilities | M | | 9.2.3.49 | | – | |
+| AS Security Information | M | | 9.2.3.50 | | – | |
+| UE Aggregate Maximum Bit Rate | M | | 9.2.3.17 | | – | |
+| PDU Session Resources To Be Setup List | M | | 9.2.1.1 | | – | |
+| RRC Context | M | | OCTET STRING | Includes the <i>HandoverPreparationInformation</i> message as defined in subclause 11.2.2 of TS 38.331[10] if the old and new serving NG-RAN nodes are gNBs. Includes either the <i>HandoverPreparationInformation</i> message as defined in subclause 10.2.2 of TS 36.331 [14] or the <i>HandoverPreparationInformation-NB</i> message as defined in subclause 10.6.2 of TS 36.331 [14], if the old and new serving NG-RAN nodes are ng-eNBs. | – | |
+| Mobility Restriction List | O | | 9.2.3.53 | | – | |
+| Index to | O | | 9.2.3.23 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|-------|------------------------------------------------------|---------------------------------------------------------------------|-------------|----------------------|
+| RAT/Frequency Selection Priority | | | | | | |
+| 5GC Mobility Restriction List Container | O | | 9.2.3.100 | | YES | ignore |
+| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.2.3.107 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore |
+| LTE UE Sidelink Aggregate Maximum Bit Rate | O | | 9.2.3.108 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore |
+| UE Radio Capability ID | O | | 9.2.3.138 | | YES | reject |
+| MBS Session Information List | O | | 9.2.1.36 | | YES | ignore |
+| No PDU Session Indication | O | | ENUMERATED (true, ...) | This IE applies only if the UE is an IAB-MT. | YES | ignore |
+| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate 9.2.3.107 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore |
+| UE Slice Maximum Bit Rate List | O | | 9.2.3.167 | | YES | ignore |
+| Positioning Information | O | | 9.2.3.168 | | YES | ignore |
+| NR A2X UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate 9.2.3.107 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore |
+| LTE A2X UE PC5 Aggregate Maximum Bit Rate | O | | LTE UE Sidelink Aggregate Maximum Bit Rate 9.2.3.108 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore |
+
+### 9.2.1.14 DRBs Subject To Status Transfer List
+
+This IE contains a list of DRBs containing information about PDCP SN status.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|---------------------|-----------------------|--------------------------------------------------------------|-------------|----------------------|
+| <b>DRBs Subject To Status Transfer Item</b> | | 1 .. <maxnoof DRBs> | | | – | |
+| >DRB ID | M | | 9.2.3.33 | | – | |
+| >CHOICE PDCP Status Transfer UL | M | | | | – | |
+| >>12 bits | | | | | | |
+| >>>Receive Status Of PDCP SDU | O | | BIT STRING (1.. 2048) | The IE is used in case of 12-bit long PDCP-SN. The first bit | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | indicates the status of the SDU after the First Missing UL PDCP SDU.<br>The Nth bit indicates the status of the UL PDCP SDU in position (N + First Missing SDU Number) modulo (1 + the maximum value of the PDCP-SN).<br><br>0: PDCP SDU has not been received.<br>1: PDCP SDU has been received correctly. | | |
+| >>>UL COUNT Value | M | | COUNT Value for PDCP SN Length 12 9.2.3.36 | PDCP-SN and Hyper Frame Number of the first missing UL SDU in case of 12-bit long PDCP-SN | – | |
+| >>18 bits | | | | | | |
+| >>>Receive Status Of PDCP SDU | O | | BIT STRING (1.. 131072) | The IE is used in case of 18-bit long PDCP-SN.<br>The first bit indicates the status of the SDU after the First Missing UL PDCP SDU.<br>The Nth bit indicates the status of the UL PDCP SDU in position (N + First Missing SDU Number) modulo (1 + the maximum value of the PDCP-SN).<br><br>0: PDCP SDU has not been received.<br>1: PDCP SDU has been received correctly. | – | |
+| >>>UL COUNT Value | M | | COUNT Value for PDCP SN Length 18 9.2.3.37 | PDCP-SN and Hyper Frame Number of the first missing UL SDU in | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | case of 18-bit long PDCP-SN | | |
+| >CHOICE <i>PDCP Status Transfer DL</i> | M | | | | – | |
+| >>12 bits | | | | | | |
+| >>>DL COUNT Value | M | | COUNT Value for PDCP SN Length 12 9.2.3.36 | PDCP-SN and Hyper Frame Number that the target NG-RAN node (handover) or the NG-RAN node to which the DRB context is transferred (dual connectivity) should assign for the next DL SDU not having an SN yet in case of 12-bit long PDCP-SN. | – | |
+| >>18 bits | | | | | | |
+| >>>DL COUNT Value | M | | COUNT Value for PDCP SN Length 18 9.2.3.37 | PDCP-SN and Hyper Frame Number that the target NG-RAN node (handover) or the NG-RAN node to which the DRB context is transferred (dual connectivity) should assign for the next DL SDU not having an SN yet in case of 18-bit long PDCP-SN. | – | |
+| >Old QoS Flow List - UL End Marker expected | O | | QoS Flow List 9.2.1.4a | This IE is included to be used for indicating that the source NG-RAN node has initiated QoS flow re-mapping and has not yet received SDAP end markers, as described in TS 38.300 [9]. | YES | reject |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+
+### 9.2.1.15 DRB to QoS Flow Mapping List
+
+This IE contains a list of DRBs containing information about the mapped QoS flows.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|--------------------------|-----------------------|-----------------------------------------------------------------------------------|-------------|----------------------|
+| <b>DRBs to QoS Flow Mapping Item</b> | | 1..<br><maxnoof<br>DRBs> | | | – | |
+| >DRB ID | M | | 9.2.3.33 | | – | |
+| >QoS Flows List | | 1 | | | – | |
+| >>QoS Flow Item | | 1..<maxno<br>ofQoSFlows> | | | – | |
+| >>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| >RLC Mode | O | | 9.2.3.28 | Indicates the RLC mode for PDCP transfer between M-NG-RAN node and S-NG-RAN node. | – | |
+| >DAPS Request Information | O | | 9.2.1.33 | | YES | ignore |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.1.16 Data Forwarding Info from target NG-RAN node
+
+This IE contains TNL information for the establishment of data forwarding tunnels towards the target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------------------|----------|----------------------|-----------------------------------------|--------------------------------------------------|
+| <b>QoS Flows Accepted For Data Forwarding List</b> | | 1 | | |
+| >QoS Flows Accepted For Data Forwarding Item | | 1..<maxnoofQoSFlows> | | |
+| >>QoS Flow Identifier | M | | 9.2.3.10 | |
+| PDU Session level DL data forwarding UP TNL Information | O | | UP Transport Layer Information 9.2.3.30 | To forward NG-U DL SDAP SDUs to the target node. |
+| PDU Session level UL data forwarding UP TNL Information | O | | UP Transport Layer Information 9.2.3.30 | To forward NG-U UL SDAP SDU to the target node. |
+| <b>Data Forwarding Response DRB List</b> | | 0..1 | | |
+| >Data Forwarding Response DRB Item | | 1..<maxnoofDRBs> | | |
+| >>DRB ID | M | | 9.2.3.33 | |
+| >>DL Forwarding UP TNL Information | O | | UP Transport Layer Information 9.2.3.30 | |
+| >>UL Forwarding UP TNL Information | O | | UP Transport Layer Information 9.2.3.30 | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|-------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| Direct Forwarding Path Availability | O | | ENUMERATED<br>(direct path available, ...) | Indicates direct forwarding path is available between the target NG-RAN node and source S-NG-RAN node for the PDU session. |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.1.17 Data Forwarding and Offloading Info from source NG-RAN node
+
+This IE contains information from a source NG-RAN node regarding per QoS flow proposed data forwarding and offloading.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-----------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>QoS Flows To Be Forwarded List</b> | | 1 | | | – | |
+| <b>>QoS Flows To Be Forwarded Item</b> | | 1 ..<br><maxnoof<br>QoSFlows<br>> | | | – | |
+| >>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>DL Forwarding | M | | 9.2.3.34 | | – | |
+| >>UL Forwarding | M | | 9.2.3.90 | This IE shall be ignored. | – | |
+| >>UL Forwarding Proposal | O | | 9.2.3.95 | | YES | ignore |
+| >>Source DL Forwarding IP Address | O | | Transport Layer Address<br>9.2.3.29 | Identifies the TNL address for data forwarding allocated by the MN node for DC cases and by source NG-RAN node for mobility without MR-DC involved cases | YES | ignore |
+| >>Source Node DL Forwarding IP Address | O | | Transport Layer Address<br>9.2.3.29 | This IE is present only for the case of SA to MR-DC handover and it is used to identify the source TNL address allocated by the source NG-RAN node for data forwarding. | YES | ignore |
+| Source DRB to QoS Flow Mapping List | O | | DRB to QoS Flow Mapping List<br>9.2.1.15 | Usage of the DRB IDs indicated in the <i>Source DRB to QoS Flow Mapping List</i> IE is specified in TS | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| | | | | 37.340 [8]. | | |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.1.18 PDU Session Resource Change Required Info – SN terminated
+
+This IE contains information for the S-NG-RAN node initiated request for an S-NG-RAN node change related to a PDU session resource with DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | |
+
+### 9.2.1.19 PDU Session Resource Change Confirm Info – SN terminated
+
+This IE contains information for the M-NG-RAN node's confirmation of an S-NG-RAN node initiated request for an S-NG-RAN node change related to a PDU session resource with DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Data Forwarding Info from target NG-RAN node | O | | 9.2.1.16 | | – | |
+| DRB IDs taken into use | O | | DRB List 9.2.1.29 | Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8]. | YES | reject |
+
+### 9.2.1.20 PDU Session Resource Modification Required Info – SN terminated
+
+This IE contains PDU session resource information of an S-NG-RAN node initiated modification request of DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|-----------------------------------------|-------------------------------------------------------------------------------|-------------|----------------------|
+| DL NG-U UP TNL Information at NG-RAN | O | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of the NG-U transport bearer. For delivery of DL PDUs. | – | |
+| QoS Flows To Be Released List | O | | QoS Flow List with Cause 9.2.1.4 | | – | |
+| Data Forwarding and | O | | 9.2.1.17 | This IE only | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|----------------------------------|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Offloading Info from source NG-RAN node | | | | applies to QoS flows included in the <i>QoS FlowS To Be Released List</i> IE. | | |
+| <b>DRBs To Be Setup List</b> | | <i>0..1</i> | | | – | |
+| >DRBs to Be Setup Item | | <i>1 .. <maxnoof DRBs></i> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>PDCP SN Length | O | | 9.2.3.63 | Indicates the PDCP SN length of the DRB. | – | |
+| >>SN UL PDCP UP TNL Information | M | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>DRB QoS | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>secondary SN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP Duplication. | – | |
+| >>Duplication Activation | O | | 9.2.3.71 | Information on the initial state of UL PDCP duplication. This IE is ignored if the <i>RLC Duplication Information</i> IE is present. | – | |
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the S-NG-RAN node. This IE is used when the concerned DRB has both MCG resource and SCG resource configured i.e. the concerned DRB is configured as split bearer. | – | |
+| >>QoS Flows | | <i>1</i> | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Mapped To DRB List</b> | | | | | | |
+| >>>QoS Flows Mapped To DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>MCG requested GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains GBR QoS Flow Information necessary for the MCG part. | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | YES | ignore |
+| >>RLC Mode | M | | 9.2.3.28 | Indicates the RLC mode at the assisting node. | – | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP Duplication. | – | |
+| >>RLC Duplication Information | O | | 9.2.3.111 | | YES | ignore |
+| <b>DRBs To Be Modified List</b> | | 0..1 | | | – | |
+| >DRBs to Be Modified Item | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs. | – | |
+| >>DRB QoS | O | | QoS Flow Level QoS Parameters | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | 9.2.3.5 | | | |
+| >>secondary SN UL PDCP UP TNL Information | O | | UP Transport Parameters 9.2.3.76 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of PDCP Duplication. | – | |
+| >>UL Configuration | O | | 9.2.3.75 | Information about UL usage in the S-NG-RAN node. | – | |
+| >>PDCP Duplication Configuration | O | | 9.2.3.86 | | – | |
+| >>Duplication Activation | O | | 9.2.3.71 | This IE is ignored if the <i>RLC Duplication Information</i> IE is present. | – | |
+| >>QoS Flows Mapped to DRB List | | 0..1 | | Overwriting the existing QoS Flow List | – | |
+| >>>QoS Flows Mapped to DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>>>MCG requested GBR QoS Flow Information | O | | GBR QoS Flow Information 9.2.3.6 | This IE contains GBR QoS Flow Information necessary for the MCG part. | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | YES | ignore |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint(s) of a DRB's Xn transport bearer at its PDCP resource. For delivery of UL PDUs in case of additional PDCP Duplication. | – | |
+| >>RLC Duplication | O | | 9.2.3.111 | | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|-------|---------------------------------|-----------------------|-------------|----------------------|
+| Information | | | | | | |
+| <b>DRBs To Be Released List</b> | O | | DRB List with Cause<br>9.2.1.28 | | – | |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows. Value is 64. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.21 PDU Session Resource Modification Confirm Info – SN terminated
+
+This IE contains the PDU session resource related result of an S-NG-RAN node initiated modification of DRBs configured with an SN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------|----------|---------------------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| UL NG-U UP TNL Information at UPF | O | | UP Transport Layer Information<br>9.2.3.30 | UPF endpoint of the NG-U transport bearer. For delivery of UL PDUs | – | |
+| <b>DRBs Admitted to be Setup or Modified List</b> | | 1 | | | – | |
+| > <b>DRBs Admitted to be Setup or Modified Item</b> | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>MN DL CG UP TNL Information | O | | UP Transport Parameters<br>9.2.3.76 | M-NG-RAN node endpoint(s) of the DRB's Xn transport at its Lower Layer CG resource. For delivery of DL PDUs. | – | |
+| >>secondary MN DL CG UP TNL Information | O | | UP Transport Parameters<br>9.2.3.76 | M-NG-RAN node endpoint(s) of the DRB's Xn transport at its Lower Layer CG resource. For delivery of DL PDUs at the case of PDCP duplication. | – | |
+| >>LCID | O | | 9.2.3.70 | Shall be ignored by the S-NG-RAN node if received. | – | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication | | 1 .. <maxnoof | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|------------------------------------------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>TNL Item</b> | | <i>Additional PDCPDuplicationTNL></i> | | | | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | M-NG-RAN node endpoint(s) of the DRB's Xn transport at its Lower Layer CG resource. For delivery of DL PDUs at the case of additional PDCP duplication. | – | |
+| DRBs Not Admitted To Be Setup or Modified List | O | | DRB List with Cause 9.2.1.28 | | – | |
+| Data Forwarding Info from target NG-RAN node | O | | 9.2.1.16 | Forwarding Addresses for both, QoS flow and DRB level offloading. | – | |
+| DRB IDs taken into use | O | | DRB List 9.2.1.29 | Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8]. | YES | reject |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+| maxnoofQoSFlows | Maximum no. of QoS flows. Value is 64. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+## 9.2.1.22 PDU Session Resource Modification Required Info – MN terminated
+
+This IE contains PDU session resource information of an S-NG-RAN node initiated modification request of DRBs configured with an MN terminated bearer option.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|--------------------------------|-----------------------------------------|---------------------------------------------------------------------------------|-------------|----------------------|
+| <b>DRBs To Be Modified List</b> | O | | | | – | |
+| >DRBs To Be Modified Item | | <i>1..<maxno ofDRBs></i> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>SN DL SCG UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of a DRB's Xn transport bearer. For delivery of DL PDUs. | – | |
+| >>secondary SN DL SCG UP TNL | O | | UP Transport Layer | S-NG-RAN node endpoint of a | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------|----------|----------------------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Information | | | Information 9.2.3.30 | DRB's Xn transport bearer. For delivery of DL PDUs in case of PDCP Duplication | | |
+| >>LCID | O | | 9.2.3.70 | LCID for primary path or LCID for split secondary path for fallback to split bearer if PDCP duplication is applied | – | |
+| >>RLC Status | O | | 9.2.3.80 | | – | |
+| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore |
+| >>>Additional PDCP Duplication TNL Item | | 1 .. <maxnoof Additional PDCPDuplicationTNL> | | | – | |
+| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | S-NG-RAN node endpoint of a DRB's Xn transport bearer. For delivery of DL PDUs in case of additional PDCP Duplication | – | |
+| DRBs To Be Released List | O | | DRB List with Cause 9.2.1.28 | | – | |
+
+| Range bound | Explanation |
+|-------------------------------------|-------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs. Value is 32. |
+| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional PDCP Duplication TNL. Value is 2. |
+
+### 9.2.1.23 PDU Session Resource Modification Confirm Info – MN terminated
+
+This IE contains the PDU session resource related result of an S-NG-RAN node initiated modification of DRBs configured with an MN terminated bearer option.
+
+NOTE: In the current version of this specification, this IE has no content, apart from an extension container.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| | | | | |
+
+### 9.2.1.24 PDU Session List with data forwarding request info
+
+This IE contains a list of PDU session related data forwarding request information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------------------------|----------|----------------------------|---------------------------------------|------------------------------------------------------------------|-------------|----------------------|
+| <b>PDU Session List with data forwarding request info</b> | | 1 .. <maxnoof PDUsessions> | | | – | |
+| >PDU Session ID | M | | 9.2.3.18 | | – | |
+| >Data Forwarding and Offloading Info from source NG-RAN node | O | | 9.2.1.17 | | – | |
+| >DRBs To Be Released List | O | | DRB to QoS Flow Mapping List 9.2.1.15 | Indicate the QoS flow mapping and RLC mode of the released DRBs. | – | |
+| >Cause | O | | 9.2.3.2 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------|
+| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256. |
+
+### 9.2.1.25 PDU Session List with data forwarding info from the target node
+
+This IE contains a list of PDU session related data forwarding information from the target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------------------------|----------|----------------------------|-----------------------|-------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>PDU Session List with data forwarding from the target node</b> | | 1 .. <maxnoof PDUsessions> | | | – | |
+| >PDU Session ID | M | | 9.2.3.18 | | – | |
+| >Data Forwarding Info from target NG-RAN node | M | | 9.2.1.16 | | – | |
+| >DRB IDs taken into use | O | | DRB List 9.2.1.29 | Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8]. | YES | reject |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------|
+| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256. |
+
+### 9.2.1.26 PDU Session List with Cause
+
+This IE contains a list of PDU Sessions, a cause may accompany each list element.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|----------------------------|-----------------------|-----------------------|
+| <b>PDU Session List with Cause</b> | | 1 .. <maxnoofPDU sessions> | | |
+| >PDU Session ID | M | | 9.2.3.18 | |
+
+| | | | | |
+|--------|---|--|---------|--|
+| >Cause | O | | 9.2.3.2 | |
+|--------|---|--|---------|--|
+
+| Range bound | Explanation |
+|--------------------|-------------------------------------------|
+| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256 |
+
+### 9.2.1.27 PDU Session List
+
+This IE contains a list of PDU sessions.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|------------------------------|-----------------------|-----------------------|
+| <b>PDU Session List</b> | | 1 ..<br><maxnoofPDUsessions> | | |
+| >PDU Session ID | M | | 9.2.3.18 | |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------|
+| maxnoofPDUsessions | Maximum no. of PDU sessions. Value is 256. |
+
+### 9.2.1.28 DRB List with Cause
+
+This IE contains a list of DRBs, a cause may accompany each list element.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-----------------------|-----------------------|-----------------------------------------------------------------------------------|
+| <b>DRB List with Cause</b> | | 1 ..<br><maxnoofDRBs> | | |
+| >DRB ID | M | | 9.2.3.33 | |
+| >Cause | M | | 9.2.3.2 | |
+| >RLC Mode | O | | 9.2.3.28 | Indicates the RLC mode for PDCP transfer between M-NG-RAN node and S-NG-RAN node. |
+
+| Range bound | Explanation |
+|-------------|-------------------------------------------|
+| maxnoofDRBs | Maximum no. of PDU sessions. Value is 32. |
+
+### 9.2.1.29 DRB List
+
+This IE contains a list of DRBs.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-----------------------|-----------------------|-----------------------|
+| <b>DRB List</b> | | 1 ..<br><maxnoofDRBs> | | |
+| >DRB ID | M | | 9.2.3.33 | |
+
+| Range bound | Explanation |
+|-------------|-------------|
+|-------------|-------------|
+
+| | |
+|-------------|-----------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs. Value is 32. |
+|-------------|-----------------------------------|
+
+### 9.2.1.30 PDU Session Resource Setup Complete Info – SN terminated
+
+This IE contains information to complete the establishment of Xn-U bearers for SN terminated bearers.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|--------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>DRBs To Be Setup List</b> | | 1 | | | – | – |
+| >DRBs to Be Setup Item | | 1 .. <maxnoofDRBs> | | | – | – |
+| >>DRB ID | M | | 9.2.3.33 | | – | – |
+| >>MN DL Xn UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | M-NG-RAN node endpoint of a DRB's Xn-U transport. For delivery of DL PDUs. | – | – |
+| >>Secondary MN DL Xn UP TNL Information | O | | UP Transport Layer Information 9.2.3.30 | M-NG-RAN node endpoint of a DRB's Xn-U transport. For delivery of DL PDUs in case of PDCP Duplication. | YES | ignore |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+
+### 9.2.1.31 Secondary Data Forwarding Info from target NG-RAN node List
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------------------------|----------|---------------------------------------|-------------------------------------------------------|-----------------------|
+| <b>Secondary Data Forwarding Info from target NG-RAN node Item</b> | | 1..<maxnoofMultiConnectivityMinusOne> | | |
+| >Secondary Data Forwarding Info from target NG-RAN node | M | | Data Forwarding Info from target NG-RAN node 9.2.1.16 | |
+
+| Range bound | Explanation |
+|----------------------------------|----------------------------------------------------------------|
+| maxnoofMultiConnectivityMinusOne | Maximum no. of <i>MultiConnectivity minus one</i> . Value is 3 |
+
+### 9.2.1.32 Additional UL NG-U UP TNL Information at UPF List
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------|
+| <b>Additional UL NG-U UP TNL Information at</b> | | 1..<maxnoofMultiCo | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|----------|---------------------------------|-----------------------------------------|-----------------------|-------------|----------------------|
+| <b>UPF Item</b> | | <i>nnectivity MinusOne ></i> | | | | |
+| >Additional UL NG-U UP TNL Information at UPF | M | | UP Transport Layer Information 9.2.3.30 | | – | |
+| >Common Network Instance | O | | 9.2.3.92 | | YES | ignore |
+
+| Range bound | Explanation |
+|----------------------------------|----------------------------------------------------------------|
+| maxnoofMultiConnectivityMinusOne | Maximum no. of <i>MultiConnectivity minus one</i> . Value is 3 |
+
+### 9.2.1.33 DAPS Request Information
+
+The *DAPS Indicator* IE indicates that the source NG-RAN node requests a DAPS HO for the concerned DRB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|------------------------------------|-------------------------------------|
+| DAPS Indicator | M | | ENUMERATED (DAPS HO required, ...) | Indicates that DAPS HO is requested |
+
+### 9.2.1.34 DAPS Response Information
+
+The *DAPS Response Information* IE indicates, per DRB, the response to a requested DAPS Handover.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------|----------|-------------------------------|----------------------------------------------------------|--------------------------------------------------------|
+| <b>DAPS Response Information List</b> | | <i>1..<maxnoofDRBs></i> | | |
+| >DRB ID | M | | 9.2.3.33 | |
+| >DAPS Response Indicator | M | | ENUMERATED (DAPS HO accepted, DAPS HO not accepted, ...) | Indicates whether the DAPS Handover has been accepted. |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRBs allowed towards one UE. Value is 32. |
+
+### 9.2.1.35 Data Forwarding Info from target E-UTRAN node
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------------------|----------|---------------------------------------------|-----------------------|-----------------------|
+| <b>Data Forwarding Info from Target E-UTRAN node List</b> | | 1 | | |
+| >Data Forwarding Info from Target E-UTRAN node Item | | <i>1..<maxnoofDataForwardingTunn></i> | | |
+
+| | | | | |
+|---------------------------------------|---|--------------------------|--------------------------------------------|--|
+| | | eltoE-UTRAN<br>> | | |
+| >>DL Forwarding UP<br>TNL Information | M | | UP Transport Layer<br>Information 9.2.3.30 | |
+| >>QoS Flows To Be<br>Forwarded List | | 1 | | |
+| >>> QoS Flows To Be<br>Forwarded Item | | 1..<maxnoofQ<br>oSFlows> | | |
+| >>>>QoS Flow<br>Identifier | M | | 9.2.3.10 | |
+
+| Range bound | Explanation |
+|--------------------------------------|---------------------------------------------------------------------------|
+| maxnoofDataForwardingTunneltoE-UTRAN | Maximum no. of Data Forwarding Tunnels to E-UTRAN for a UE. Value is 256. |
+| maxnoofQoSflows | Maximum no. of QoS flows in a PDU Session. Value is 64. |
+
+### 9.2.1.36 MBS Session Information List
+
+This IE contains NG-RAN MBS session resource context related information used at UE context transfer between NG-RAN nodes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------------------------------------|----------|---------------------------------|---------------------------------------|-------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>MBS Session Information Item</b> | | 1..<maxno<br>ofMBSSes<br>sions> | | | – | |
+| >MBS Session ID | M | | 9.2.3.146 | | – | |
+| >MBS Area Session ID | O | | 9.2.3.148 | MBS Area Session ID of the UE at the NG-RAN node from which the UE context is transferred | – | |
+| >Active MBS Session Information | O | | | | – | |
+| >>MBS QoS Flows to Add List | | 1..<maxno<br>ofMBSQo<br>SFlows> | | | – | |
+| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.2.3.10 | | – | |
+| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>MBS Service Area | O | | 9.2.3.150 | | – | |
+| >>MBS Mapping and Data Forwarding Request Info from source NG-RAN node | O | | 9.2.1.39 | | – | |
+| >MBS Assistance Information | O | | 9.2.3.196 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|-----------------------------------------------------------------------|
+| maxnoofMBSSessions | Maximum no. of MBS Sessions. Value is 256. |
+| maxnoofMBSQoSFlows | Maximum no. of QoS flows allowed within one MBS session. Value is 64. |
+
+### 9.2.1.37 MBS Session Associated Information
+
+This IE contains MBS session resource related information about associated unicast QoS flows.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|-----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>MBS Session Associated Information List</b> | | 1..<maxnoofAssociatedMBSSessions> | | The NG-RAN node does not establish resources for the associated unicast QoS Flows included in the <i>MBS Session Information Item</i> IE and replicated in a QoS Flows To Be Setup Item. An Associated Unicast QoS Flow Identifier appears only once in the <i>MBS Session Information List</i> IE. |
+| >MBS Session ID | M | | 9.2.3.146 | |
+| > <b>Associated QoS Flow Information List</b> | | 1..<maxnoofMBSQoSFlows> | | |
+| >>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.2.3.10 | |
+| >>Associated Unicast QoS Flow Identifier | M | | QoS Flow Identifier 9.2.3.10 | |
+
+| Range bound | Explanation |
+|------------------------------|--------------------------------------------------------------------------|
+| maxnoofMBSQoSFlows | Maximum no. of QoS flows allowed within one MBS session. Value is 64. |
+| maxnoofAssociatedMBSSessions | Maximum no. of MBS Sessions allowed within one PDU session. Value is 32. |
+
+### 9.2.1.38 MBS Session Information Response List
+
+This IE contains NG-RAN MBS session resource context related information to be provided in response to information provided in the *MBS Session Information List* IE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------------------|----------|-------------------------|-----------------------|-----------------------|
+| <b>MBS Session Information Response List</b> | | 1..<maxnoofMBSSessions> | | |
+| >MBS Session ID | M | | 9.2.3.146 | |
+| >MBS Data Forwarding Response Info from target NG-RAN node | O | | 9.2.1.40 | |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------|
+| maxnoofMBSSessions | Maximum no. of MBS Sessions. Value is 256. |
+
+### 9.2.1.39 MBS Mapping and Data Forwarding Request Info from source NG-RAN node
+
+This IE contains information from a source NG-RAN node regarding MBS QoS flow to MRB mapping and data forwarding information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------------------------------------|----------|-------------------------|------------------------------|----------------------------------------------------------------------------------------------------|
+| <b>MBS Mapping and Data Forwarding Request Info from source NG-RAN node</b> | | 1 .. <maxnoofMRBs> | | |
+| >MRB ID | M | | 9.2.3.145 | Contains the MRB ID value allocated at the source NG-RAN node. |
+| >MBS QoS Flow List | | 1..<maxnoofMBSQoSflows> | | |
+| >>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.2.3.10 | |
+| >MRB Progress Information | O | | 9.2.3.147 | The PDCP SN information of the last packet which has already been delivered to the UE for the MRB. |
+
+| Range bound | Explanation |
+|--------------------|-----------------------------------------------------------------------|
+| maxnoofMBSQoSflows | Maximum no. of QoS flows allowed within one MBS session. Value is 64. |
+| maxnoofMRBs | Maximum no. of MRBs allowed for one MBS Session. Value is 32. |
+
+#### 9.2.1.40 MBS Data Forwarding Response Info from target NG-RAN node
+
+This IE contains TNL information for the establishment of data forwarding tunnels towards the target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------------------------|----------|------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------|
+| <b>MBS Data Forwarding Response Info from target NG-RAN node</b> | | 1..<maxnoofMRBs> | | |
+| >MRB ID | M | | 9.2.3.145 | Contains the MRB ID value allocated at the source NG-RAN node. |
+| >DL Forwarding UP TNL Information | M | | UP Transport Layer Information 9.2.3.30 | |
+| >MRB Progress Information | O | | 9.2.3.147 | This IE includes the information of the oldest packet available at the target NG-RAN node for the MRB. |
+
+| Range bound | Explanation |
+|-------------|-----------------------------------|
+| maxnoofMRBs | Maximum no. of MRBs. Value is 32. |
+
+### 9.2.2 NG-RAN Node and Cell Configuration related IE definitions
+
+#### 9.2.2.1 Global gNB ID
+
+This IE is used to globally identify a gNB (see TS 38.300 [9]).
+
+| IE/Group Name | Presence | Range | IE type and | Semantics description |
+|---------------|----------|-------|-------------|-----------------------|
+|---------------|----------|-------|-------------|-----------------------|
+
+| | | | reference | |
+|----------------------|---|--|---------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+| CHOICE <i>gNB ID</i> | M | | | |
+| > <i>gNB ID</i> | | | | |
+| >> <i>gNB ID</i> | M | | BIT STRING (SIZE(22..32)) | Equal to the leftmost bits of the <i>NR Cell Identity</i> IE contained in the <i>NR CGI</i> IE of each cell served by the gNB. |
+
+### 9.2.2.2 Global ng-eNB ID
+
+This IE is used to globally identify an ng-eNB (see TS 38.300 [9]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+| CHOICE <i>ng-eNB ID</i> | M | | | |
+| > <i>Macro ng-eNB ID</i> | | | | |
+| >>Macro ng-eNB ID | M | | BIT STRING (SIZE(20)) | Equal to the 20 leftmost bits of the <i>E-UTRA Cell Identity</i> IE contained in the <i>E-UTRA CGI</i> IE of each cell served by the ng-eNB. |
+| > <i>Short Macro ng-eNB ID</i> | | | | |
+| >>Short Macro ng-eNB ID | M | | BIT STRING (SIZE(18)) | Equal to the 18 leftmost bits of the <i>E-UTRA Cell Identity</i> IE contained in the <i>E-UTRA CGI</i> IE of each cell served by the ng-eNB. |
+| > <i>Long Macro ng-eNB ID</i> | | | | |
+| >>Long Macro ng-eNB ID | M | | BIT STRING (SIZE(21)) | Equal to the 21 leftmost bits of the <i>E-UTRA Cell Identity</i> IE contained in the <i>E-UTRA CGI</i> IE of each cell served by the ng-eNB. |
+
+### 9.2.2.3 Global NG-RAN Node ID
+
+This IE is used to globally identify an NG-RAN node (see TS 38.300 [9]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>NG-RAN node</i> | M | | | |
+| > <i>gNB</i> | | | | |
+| >>Global gNB ID | M | | 9.2.2.1 | |
+| > <i>ng-eNB</i> | | | | |
+| >>Global ng-eNB ID | M | | 9.2.2.2 | |
+
+### 9.2.2.4 PLMN Identity
+
+This IE indicates the PLMN Identity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M | | OCTET STRING (SIZE(3)) | <p>Digits 0 to 9 encoded 0000 to 1001, 1111 used as filler digit.</p> <p>Two digits per octet:<br/> - bits 4 to 1 of octet n encoding digit 2n-1<br/> - bits 8 to 5 of octet n encoding digit 2n</p> <p>PLMN Identity consists of 3 digits from MCC followed by either:<br/> - a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or<br/> - 3 digits from MNC (in case of 3 digit MNC).</p> |
+
+### 9.2.2.5 TAC
+
+This information element is used to uniquely identify a Tracking Area within a PLMN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-----------------------|
+| TAC | M | | OCTET STRING (SIZE (3)) | |
+
+### 9.2.2.6 RAN Area Code
+
+This IE defines the RAN Area Code.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RANAC | M | | INTEGER (0..255) | |
+
+### 9.2.2.7 NR CGI
+
+This IE is used to globally identify an NR cell (see TS 38.300 [9]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+| NR Cell Identity | M | | BIT STRING (SIZE(36)) | The leftmost bits of the <i>NR Cell Identity</i> IE correspond to the gNB ID (defined in subclause 9.2.2.1). |
+
+### 9.2.2.8 E-UTRA CGI
+
+This IE is used to globally identify an E-UTRA cell (see TS 36.300 [12]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+
+| | | | | |
+|----------------------|---|--|-----------------------|---------------------------------------------------------------------------------------------------------------------|
+| E-UTRA Cell Identity | M | | BIT STRING (SIZE(28)) | The leftmost bits of the <i>E-UTRA Cell Identity</i> IE correspond to the ng-eNB ID (defined in subclause 9.2.2.2). |
+|----------------------|---|--|-----------------------|---------------------------------------------------------------------------------------------------------------------|
+
+### 9.2.2.9 NG-RAN Cell Identity
+
+This IE contains either an NR or an E-UTRA Cell Identity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>Cell Identifier</i> | M | | | |
+| >NR | | | | |
+| >>NR Cell Identity | M | | BIT STRING (SIZE(36)) | The leftmost bits of the <i>NR Cell Identity</i> IE correspond to the gNB ID (defined in subclause 9.2.2.1). |
+| >E-UTRA | | | | |
+| >>E-UTRA Cell Identity | M | | BIT STRING (SIZE(28)) | The leftmost bits of the <i>E-UTRA Cell Identity</i> IE correspond to the ng-eNB ID (defined in subclause 9.2.2.8). |
+
+### 9.2.2.10 NG-RAN Cell PCI
+
+This IE defines physical cell ID of a cell served by an NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------|----------|-------|------------------------|-------------------------|
+| CHOICE <i>RAT</i> | M | | | |
+| >nr | | | | |
+| >>NR PCI | M | | INTEGER (0..1007, ...) | NR Physical Cell ID |
+| >e-utra | | | | |
+| >>E-UTRA PCI | M | | INTEGER (0..503, ...) | E-UTRA Physical Cell ID |
+
+### 9.2.2.11 Served Cell Information NR
+
+This IE contains cell configuration information of an NR cell that a neighbouring NG-RAN node may need for the Xn AP interface.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------|----------|---------------------|------------------------|-------------------------------------------------------------------------------------|-------------|----------------------|
+| NR-PCI | M | | INTEGER (0..1007, ...) | NR Physical Cell ID | – | |
+| NR CGI | M | | 9.2.2.7 | | – | |
+| TAC | M | | 9.2.2.5 | Tracking Area Code | – | |
+| RANAC | O | | RAN Area Code 9.2.2.6 | | – | |
+| <b>Broadcast PLMNs</b> | | 1..<maxno ofBPLMNs> | | Broadcast PLMNs contained in the <i>SIB1</i> message as specified in TS 38.331[10], | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | associated to the NR Cell Identity in the <i>NR CGI</i> IE. | | |
+| >PLMN Identity | M | | 9.2.2.4 | | – | |
+| CHOICE <i>NR-Mode-Info</i> | M | | | | – | |
+| >FDD | | | | | | |
+| >>FDD Info | | 1 | | | – | |
+| >>>UL NR Frequency Info | M | | NR Frequency Info<br>9.2.2.19 | This IE is ignored for NR operating bands for which uplink range of $N_{REF}$ is not defined in section 5.4.2.3 of TS 38.104 [24]. | – | |
+| >>>DL NR Frequency Info | M | | NR Frequency Info<br>9.2.2.19 | | – | |
+| >>>UL Transmission Bandwidth | M | | NR Transmission Bandwidth<br>9.2.2.20 | This IE is ignored for NR operating bands for which uplink range of $N_{REF}$ is not defined in section 5.4.2.3 of TS 38.104 [24]. | – | |
+| >>>DL Transmission Bandwidth | M | | NR Transmission Bandwidth<br>9.2.2.20 | | – | |
+| >>>UL Carrier List | O | | NR Carrier List<br>9.2.2.63 | If included, the <i>UL Transmission Bandwidth</i> IE shall be ignored. | YES | ignore |
+| >>>DL Carrier List | O | | NR Carrier List<br>9.2.2.63 | If included, the <i>DL Transmission Bandwidth</i> IE shall be ignored. | YES | ignore |
+| >>>gNB-DU Cell Resource Configuration-FDD-UL | O | | gNB-DU Cell Resource Configuration<br>9.2.2.95 | Contains FDD UL resource configuration of gNB-DU's cell. Only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU. | YES | ignore |
+| >>>gNB-DU Cell Resource Configuration-FDD-DL | O | | gNB-DU Cell Resource Configuration<br>9.2.2.95 | Contains FDD UL resource configuration of gNB-DU's cell. Only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU. | YES | ignore |
+| >TDD | | | | | | |
+| >>TDD Info | | 1 | | | – | |
+| >>>Frequency Info | M | | NR Frequency Info<br>9.2.2.19 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|----------------------------------|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>Transmission Bandwidth | M | | NR Transmission Bandwidth 9.2.2.20 | | – | |
+| >>>Intended TDD DL-UL Configuration NR | O | | 9.2.2.40 | | YES | ignore |
+| >>>TDD UL-DL Configuration Common NR | O | | OCTET STRING | Includes the <i>tdd-UL-DL-ConfigurationCommon</i> contained in the <i>SIB1</i> message as defined in TS 38.331 [10] | YES | ignore |
+| >>>Carrier List | O | | NR Carrier List 9.2.2.63 | If included, the <i>Transmission Bandwidth</i> IE shall be ignored. | YES | ignore |
+| >>>gNB-DU Cell Resource Configuration-TDD | O | | gNB-DU Cell Resource Configuration 9.2.2.95 | Contains FDD UL resource configuration of gNB-DU's cell. Only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU. | YES | ignore |
+| Measurement Timing Configuration | M | | OCTET STRING | Includes the <i>MeasurementTimingConfiguration</i> inter-node message for the served cell, as defined in TS 38.331 [10]. | – | |
+| Connectivity Support | M | | 9.2.2.28 | | – | |
+| <b>Broadcast PLMN Identity Info List NR</b> | | <i>0..<maxno ofBPLMNs></i> | | This IE corresponds to information provided in the <i>PLMN-IdentityInfoList</i> IE and the <i>NPN-IdentityInfoList</i> IE (if available) in <i>SIB1</i> as specified in TS 38.331 [10]. All PLMN Identities and associated information contained in the <i>PLMN-IdentityInfoList</i> IE and NPN identities and associated information contained in the | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|---------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>NPN-IdentityInfoList</i> IE (if available) are included and provided in the same order as broadcast in the <i>SIB1</i> message.<br>NOTE: In case of NPN-only cell, the PLMN Identities and associated information contained in the <i>PLMN-IdentityInfoList</i> IE are not included. | | |
+| <b>>Broadcast PLMNs</b> | | 1..<maxno ofBPLMNs> | | Broadcast PLMNs in the <i>SIB1</i> message, associated to the <i>NR Cell Identity</i> IE. | – | |
+| >>PLMN Identity | M | | 9.2.2.4 | | – | |
+| >TAC | M | | 9.2.2.5 | | – | |
+| >NR Cell Identity | M | | BIT STRING (SIZE(36)) | | – | |
+| >RANAC | O | | RAN Area Code 9.2.2.6 | | – | |
+| >Configured TAC Indication | O | | 9.2.2.39a | NOTE: This IE is associated with the TAC in the <i>Broadcast PLMN Identity Info List NR</i> IE | YES | ignore |
+| >NPN Broadcast Information | O | | 9.2.2.71 | If this IE is included the content of the <i>Broadcast PLMNs</i> IE in the <i>Broadcast PLMN Identity Info List NR</i> IE is ignored. | YES | reject |
+| Configured TAC Indication | O | | 9.2.2.39a | NOTE: This IE is associated with the TAC on top-level of the <i>Served Cell Information NR</i> IE | YES | ignore |
+| NPN Broadcast Information | O | | 9.2.2.71 | If this IE is included the content of the <i>Broadcast PLMNs</i> IE in the top <i>Served Cell Information NR</i> IE is ignored. | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|------------------------------|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| SSB Positions In Burst | O | | 9.2.2.64 | | YES | ignore |
+| NR Cell PRACH Configuration | O | | OCTET STRING | Includes the <i>NR Cell PRACH Configuration</i> IE as defined in section 9.3.1.139 in TS 38.473 [41]. | YES | ignore |
+| CSI-RS Transmission Indication | O | | ENUMERATED (activated, deactivated, ...) | This IE indicates the CSI-RS transmission status of the given cell.<br>If the <i>Additional Measurement Timing Configuration List</i> IE is present, this IE is ignored. | YES | ignore |
+| SFN Offset | O | | 9.2.2.75 | | YES | ignore |
+| <b>Supported MBS FSA ID List</b> | | 0..<maxno ofMBSFS As> | | Shall contain all MBS Frequency Selection Area Identities associated to the NR Cell Identity in the <i>NR CGI</i> IE. | YES | ignore |
+| >MBS Frequency Selection Area Identity | M | | OCTET STRING(3) | Corresponds to information provided in the <i>MBS-FSAI</i> IE as defined in TS 38.331 [10]. | – | |
+| <b>NR-U Channel Info List</b> | | 0..1 | | | YES | ignore |
+| >NR-U Channel Info Item | | 1..<maxno ofNR-UChannel IDs> | | | – | |
+| >>NR-U Channel ID | M | | INTEGER (1..maxnoofNR-UChannelIDs, ...) | Index to uniquely identify the part of the NR-U Channel Bandwidth consisting of a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in shared spectrum.<br><br>Value 1 represents the first part of the NR-U Channel Bandwidth on which a channel access procedure | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------------|----------|-------------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | is performed.<br>Value 2 represents the second part of the NR-U Channel Bandwidth on which a channel access procedure is performed, and so on. | | |
+| >>NR ARFCN | M | | INTEGER (0..maxNRARFCN) | It represents the centre frequency of the NR-U Channel Bandwidth for NR bands restricted to operation with shared spectrum channel access, as defined in TS 37.213 [51].<br>Allowed values are specified in 38.101-1 [52] in Table 5.4.2.3-2, Table 5.4.2.3-3 and Table 5.4.2.3-4. | – | |
+| >>Bandwidth | M | | ENUMERATED (10MHz, 20MHz, 40MHz, 60MHz, 80MHz, ...) | | – | |
+| <b>Additional Measurement Timing Configuration List</b> | O | 1 .. <maxnoof MTCItems> | | | YES | ignore |
+| >Measurement Timing Configuration Index | M | | INTEGER (0..16) | “0” refers to the configuration contained in the Measurement Timing Configuration IE. Any value between “1” and “16” refers to a configuration within the <i>Additional Measurement Timing Configuration List</i> IE. | – | |
+| >CSI- RS MTC Configuration List | M | 1 .. <maxnoof CSIRScon> | | This list explicitly expresses the CSI-RS | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|----------------------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | <i>configurations</i><br>> | | configurations contained in the MTC | | |
+| >>CSI-RS Index | M | | INTEGER (0..95) | Index of CSI-RS as in MTC | – | |
+| >>CSI-RS Status | M | | ENUMERATED (activated, deactivated, ...) | This IE indicates the CSI-RS transmission status of the configuration. | – | |
+| >>>CSI-RS Neighbour List | O | 1 .. <<br><i>maxnoofCSIRSneighbourCells</i> > | | This list expresses the cells and CSI-RSs neighbouring the CSI-RS in the CSI-RS Index IE. | – | |
+| >>>NR CGI | M | | 9.2.2.7 | | – | |
+| >>>>CSI-RS MTC Neighbour List | O | 1 .. <<br><i>maxnoofCSIRSneighbourCellsInMTC</i> > | | This list expresses the CSI-RSs served by the NR CGI, which are neighbouring the CSI-RS of the served cell and contained in the MTC indicated by the neighbouring NR cell. | – | |
+| >>>>>CSI-RS Index | M | | INTEGER (0..95) | | – | |
+| RedCap Broadcast Information | O | | BIT STRING (SIZE(8)) | The presence of this IE indicates that the <i>intraFreqReselectionRedCap</i> is broadcast in the <i>SIB1</i> message of the corresponding cell, see TS 38.331 [10]. Each position in the bitmap indicates which RedCap UEs are allowed access, according to the setting of RedCap barring indicators in the <i>SIB1</i> message, see TS 38.331 [10]. First bit = 1Rx, second bit = 2Rx, third bit = halfDuplex, other bits reserved for future use. Value '1' indicates | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | 'access allowed'.<br>Value '0' indicates 'access not allowed'. | | |
+| eRedCap Broadcast Information | O | | BIT STRING (SIZE(8)) | The presence of this IE indicates that the <i>intraFreqReselection-eRedCap</i> IE is broadcast in SIB1 of the corresponding cell, see TS 38.331 [10].<br>Each position in the bitmap indicates which eRedCap UEs are allowed access, according to the setting of the barring indicators in SIB1, see TS 38.331 [10].<br>First bit = 1Rx, second bit = 2Rx, third bit = half-duplex, other bits reserved for future use.<br>Value '1' indicates 'access allowed'.<br>Value '0' indicates 'access not allowed'. | YES | ignore |
+| Mobile IAB Cell | O | | 9.2.2.106 | | YES | ignore |
+
+| Range bound | Explanation |
+|----------------------------------|---------------------------------------------------------------------------------------------------|
+| maxnoofBPLMNs | Maximum no. of broadcast PLMNs by a cell. Value is 12. |
+| maxnoofMBSFSAs | Maximum no. of MBS FSAs by one gNB. Value is 256. |
+| maxnoofNR-UChannelIDs | Maximum no. NR-U channel IDs in a cell. Value is 16. |
+| maxnoofMTCItems | Maximum no. of measurement timing configurations associated with the neighbour cell. Value is 16. |
+| maxnoofCSI RSconfigurations | Maximum number of CSI RS configurations reported in the MTC. Value is 96 |
+| maxnoofCSI RSneighbourCells | Maximum number of cells neighbouring a CSI-RS coverage area. Value is 16 |
+| maxnoofCSI RSneighbourCellsInMTC | Maximum number of CSI-RS coverage areas neighbouring a specific CSI-RS coverage area. Value is 16 |
+
+## 9.2.2.12 Served Cell Information E-UTRA
+
+This IE contains cell configuration information of an E-UTRA cell that a neighbour NG-RAN node may need for the Xn AP interface.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|---------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| E-UTRA PCI | M | | INTEGER (0..503, ...) | E-UTRA Physical Cell ID | – | |
+| ECGI | M | | E-UTRA CGI 9.2.2.8 | | – | |
+| TAC | M | | 9.2.2.5 | Tracking Area Code | – | |
+| RANAC | O | | RAN Area Code 9.2.2.6 | | – | |
+| <b>Broadcast PLMNs</b> | | 1..<maxno ofBPLMNs> | | Broadcast PLMNs in the <i>SystemInformationBlockType1</i> message (SIB1) as specified in TS 36.331 [14], associated to the E-UTRA Cell Identity in the <i>ECGI</i> IE.<br>NOTE: In this version of the specification, it is possible to broadcast only up to 6 PLMN IDs. | – | |
+| >PLMN Identity | M | | 9.2.2.4 | | – | |
+| CHOICE <i>E-UTRA-Mode-Info</i> | M | | | | – | |
+| >FDD | | | | | – | |
+| >>FDD Info | | 1 | | | – | |
+| >>>UL EARFCN | M | | E-UTRA ARFCN 9.2.2.21 | Corresponds to <i>N<sub>UL</sub></i> in TS 36.104 [25] for E-UTRA operating bands for which it is defined; ignored for E-UTRA operating bands for which <i>N<sub>UL</sub></i> is not defined | – | |
+| >>>DL EARFCN | M | | E-UTRA ARFCN 9.2.2.21 | Corresponds to <i>N<sub>DL</sub></i> in TS 36.104 [25] | – | |
+| >>>UL E-UTRA Transmission Bandwidth | M | | E-UTRA Transmission Bandwidth 9.2.2.22 | Same as DL Transmission Bandwidth in this release; ignored in case UL EARFCN value is ignored | – | |
+| >>>DL E-UTRA Transmission Bandwidth | M | | E-UTRA Transmission Bandwidth 9.2.2.22 | | – | |
+| >>>Offset of NB-IoT Channel Number to DL EARFCN | O | | Offset of NB-IoT Channel Number to EARFCN | Corresponds to <i>M<sub>DL</sub></i> in TS 36.104 [25] | YES | reject |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|--------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | 9.2.2.47 | | | |
+| >>>Offset of NB-IoT Channel Number to UL EARFCN | O | | Offset of NB-IoT Channel Number to EARFCN 9.2.2.47 | Corresponds to $M_{UL}$ in TS 36.104 [25] | YES | reject |
+| >TDD | | | | | – | |
+| >>TDD Info | | 1 | | | – | |
+| >>>EARFCN | M | | E-UTRA ARFCN 9.2.2.21 | Corresponds to $N_{DL}/N_{UL}$ in TS 36.104 [25] | – | |
+| >>>E-UTRA Transmission Bandwidth | M | | 9.2.2.22 | | – | |
+| >>>Subframe Assignment | M | | ENUMERATED (sa0, sa1, sa2, sa3, sa4, sa5, sa6, ...) | Uplink-downlink subframe configuration information defined in TS 36.211 [26] | – | |
+| >>>Special Subframe Info | | 1 | | Special subframe configuration information defined in TS 36.211 [26] | – | |
+| >>>>Special Subframe Patterns | M | | ENUMERATED (ssp0, ssp1, ssp2, ssp3, ssp4, ssp5, ssp6, ssp7, ssp8, ssp9, ssp10, ...) | | – | |
+| >>>>Cyclic Prefix DL | M | | ENUMERATED (Normal, Extended,...) | | – | |
+| >>>>Cyclic Prefix UL | M | | ENUMERATED (Normal, Extended, ...) | | – | |
+| >>>Offset of NB-IoT Channel Number to DL EARFCN | O | | Offset of NB-IoT Channel Number to EARFCN 9.2.2.47 | Corresponds to $M_{DL}$ in TS 36.104 [25] | YES | reject |
+| >>>NB-IoT UL DL Alignment Offset | O | | 9.2.2.48 | | YES | reject |
+| Number of Antenna Ports E-UTRA | O | | 9.2.2.23 | | – | |
+| PRACH Configuration | O | | E-UTRA PRACH Configuration 9.2.2.25 | | – | |
+| <b>MBSFN Subframe Info</b> | | 0..<maxno ofMBSFN> | | Corresponds to information provided in the <i>MBSFN-SubframeConfig</i> IE as defined in | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|----------------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | TS 36.331 [14] | | |
+| >Radioframe Allocation Period | M | | ENUMERATED (n1, n2, n4, n8, n16, n32, ...) | | – | |
+| >Radioframe Allocation Offset | M | | INTEGER (0..7, ...) | | – | |
+| >MBSFN Subframe Allocation E-UTRA | M | | 9.2.2.26 | | – | |
+| E-UTRA Multiband Info List | O | | 9.2.2.24 | | – | |
+| FreqBandIndicatorPriority | O | | ENUMERATED (not-broadcast, broadcast, ...) | This IE indicates that the ng-eNB supports the <i>freqBandIndicatorPriority</i> , and whether the <i>freqBandIndicatorPriority</i> is broadcast in the <i>SystemInformationBlockType1</i> message (SIB1) (see TS 36.331 [14]) | – | |
+| BandwidthReducedSI | O | | ENUMERATED (scheduled, ...) | This IE indicates that the <i>SystemInformationBlockType1-BR</i> message is scheduled in the cell (see TS 36.331 [14]) | – | |
+| Protected E-UTRA Resource Indication | O | | 9.2.2.29 | This IE indicates which E-UTRA control/reference signal resources are protected and are not subject to E-UTRA - NR Cell Resource Coordination. | – | |
+| <b>Broadcast PLMN Identity Info List E-UTRA</b> | | <i>0..<maxno ofEUTRA BPLMNs></i> | | This IE corresponds to information provided in the <i>cellAccessRelatedInfoList-5GC</i> in the <i>SystemInformationBlockType1</i> message as specified in TS 36.331 [14]. All PLMN Identities and associated information contained in the | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|---------------------------------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>cellAccessRelatedInfoList-5GC</i> are included and provided in the same order as broadcast in the <i>SystemInformationBlockType1</i> message. | | |
+| <b>>Broadcast PLMNs</b> | | <i>1..<maxnoofEUTRA BPLMNs></i> | | Broadcast PLMNs in <i>SystemInformationBlockType1</i> message (SIB1) associated to the <i>E-UTRA Cell Identity</i> IE. | – | |
+| >>PLMN Identity | M | | 9.2.2.4 | | – | |
+| >TAC | M | | 9.2.2.5 | | – | |
+| >E-UTRA Cell Identity | M | | BIT STRING (SIZE(28)) | | – | |
+| >RANAC | O | | RAN Area Code 9.2.2.6 | | – | |
+| NPRACH Configuration | O | | NPRACH Configuration 9.2.2.74 | | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------------------------------|
+| maxnoofBPLMNs | Maximum no. of broadcast PLMNs by a cell. The value is 12. |
+| maxnoofMBSFN | Maximum no. of MBSFN frame allocation with different offset. Value is 8. |
+| maxnoofEUTRABPLMNs | Maximum no. of PLMN Ids.broadcast in an E-UTRA cell. Value is 6. |
+
+### 9.2.2.13 Neighbour Information NR
+
+This IE contains cell configuration information of NR cells that a neighbour NG-RAN node may need to properly operate its own served cells.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------|---------------------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Neighbour Information NR | | <i>1 .. <maxnoofNeighbours></i> | | | – | |
+| >NR PCI | M | | INTEGER (0..1007) | NR Physical Cell ID | – | |
+| >NR CGI | M | | 9.2.2.7 | | – | |
+| >TAC | M | | 9.2.2.5 | Tracking Area Code | – | |
+| >RANAC | O | | RAN Area Code 9.2.2.6 | | – | |
+| >CHOICE <i>NR-Mode-Info</i> | M | | | | – | |
+| >>FDD | | | | | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>>>>FDD Info</b> | | 1 | | | – | |
+| >>>>UL NR FreqInfo | M | | NR Frequency Info 9.2.2.19 | This IE is ignored for NR operating bands for which uplink range of N <sub>REF</sub> is not defined in section 5.4.2.3 of TS 38.104 [24]. | – | |
+| >>>>DL NR FreqInfo | M | | NR Frequency Info 9.2.2.19 | | – | |
+| <b>>>TDD</b> | | | | | | |
+| <b>>>>TDD Info</b> | | 1 | | | – | |
+| >>>>NR FreqInfo | M | | NR Frequency Info 9.2.2.19 | | – | |
+| >Connectivity Support | M | | 9.2.2.28 | | – | |
+| >Measurement Timing Configuration | M | | OCTET STRING | Includes the <i>MeasurementTimingConfiguration</i> inter-node message for the neighbour cell, as defined in TS 38.331 [10]. | – | |
+| >Mobile IAB Cell | O | | 9.2.2.106 | | YES | ignore |
+
+| Range bound | Explanation |
+|-------------------|----------------------------------------------------------------------------------|
+| maxnoofNeighbours | Maximum no. of neighbour cells associated to a given served cell. Value is 1024. |
+
+## 9.2.2.14 Neighbour Information E-UTRA
+
+This IE contains cell configuration information of E-UTRA cells that a neighbour NG-RAN node may need to properly operate its own served cells.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|--------------------------|-----------------------|-------------------------------------------------------|
+| <b>E-UTRA Neighbour Information E-UTRA</b> | | 1 .. <maxnoofNeighbours> | | |
+| >E-UTRA PCI | M | | INTEGER (0..503, ...) | E-UTRA Physical Cell Identifier of the neighbour cell |
+| >ECGI | M | | E-UTRA CGI 9.2.2.8 | |
+| >EARFCN | M | | E-UTRA ARFCN 9.2.2.21 | DL EARFCN for FDD or EARFCN for TDD |
+| >TAC | M | | 9.2.2.5 | Tracking Area Code |
+| >RANAC | O | | RAN Area Code 9.2.2.6 | |
+
+| Range bound | Explanation |
+|-------------------|-------------------------------------------------------------------|
+| maxnoofNeighbours | Maximum no. of neighbour cells associated to a given served cell. |
+
+| | |
+|--|----------------|
+| | Value is 1024. |
+|--|----------------|
+
+### 9.2.2.15 Served Cells To Update NR
+
+This IE contains updated configuration information for served NR cells exchanged between NG-RAN nodes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------|----------|-------------------------------------------------|-------------------------------|------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Served Cells NR To Add</b> | | <i>0 .. < maxnoofCellsInNG-RAN node></i> | | List of added cells served by the NG-RAN node. | GLOBAL | reject |
+| >Served Cell Information NR | M | | 9.2.2.11 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| <b>Served Cells To Modify NR</b> | | <i>0 .. < maxnoofCellsInNG-RAN node></i> | | List of modified cells served by the NG-RAN node. | YES | reject |
+| >Old NR CGI | M | | NR CGI 9.2.2.7 | | – | |
+| >Served Cell Information NR | M | | 9.2.2.11 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >Deactivation Indication | O | | ENUMERATED (deactivated, ...) | Indicates that the concerned cell is switched off for energy saving reasons. | – | |
+| <b>Served Cells To Delete NR</b> | | <i>0 .. < maxnoofCellsInNG-RAN node ></i> | | List of deleted cells served by the NG-RAN node. | YES | reject |
+| >Old NR-CGI | M | | NR CGI 9.2.2.7 | | – | |
+
+| Range bound | Explanation |
+|---------------------------|------------------------------------------------------------------------|
+| maxnoofCellsInNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+### 9.2.2.16 Served Cells to Update E-UTRA
+
+This IE contains updated configuration information for served E-UTRA cells exchanged between NG-RAN nodes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|------------------------------------|-------------------------------|------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Served Cells To Add E-UTRA</b> | | 0 .. < maxnoofCellsInNG-RAN node> | | List of added cells served by the NG-RAN node. | YES | reject |
+| >Served Cell Information E-UTRA | M | | 9.2.2.12 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >SFN Offset | O | | 9.2.2.75 | Associated with the <i>ECGI</i> IE in the <i>Served Cell Information E-UTRA</i> IE | YES | ignore |
+| <b>Served Cells To Modify E-UTRA</b> | | 0 .. < maxnoofCellsInNG-RAN node> | | List of modified cells served by the NG-RAN node. | YES | reject |
+| >Old ECGI | M | | E-UTRA CGI 9.2.2.8 | | – | |
+| >Served Cell Information E-UTRA | M | | 9.2.2.12 | | – | |
+| >Neighbour Information NR | O | | 9.2.2.13 | | – | |
+| >Neighbour Information E-UTRA | O | | 9.2.2.14 | | – | |
+| >Deactivation Indication | O | | ENUMERATED (deactivated, ...) | Indicates that the concerned cell is switched off for energy saving reasons. | – | |
+| >SFN Offset | O | | 9.2.2.75 | Associated with the <i>ECGI</i> IE in the <i>Served Cell Information E-UTRA</i> IE | YES | ignore |
+| <b>Served Cells To Delete E-UTRA</b> | | 0 .. < maxnoofCellsInNG-RAN node > | | List of deleted cells served by the NG-RAN node. | YES | reject |
+| >Old ECGI | M | | E-UTRA CGI 9.2.2.8 | | – | |
+
+| Range bound | Explanation |
+|---------------------------|------------------------------------------------------------------------|
+| maxnoofCellsInNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+## 9.2.2.17 Cell Assistance Information NR
+
+The *Cell Assistance Information* IE is used by the NG-RAN node to request information about NR cells.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------------------------|----------|-----------------------------------|------------------------------------|------------------------------------------------------------------------------------|
+| <i>CHOICE Cell Assistance Type</i> | M | | | |
+| >Limited NR List | | | | |
+| >>List of Requested NR Cells | | 1 .. < maxnoofCellsInNG-RAN node> | | Included when the NG-RAN node requests a limited list of served NR cells. |
+| >>>NR CGI | M | | 9.2.2.7 | NR cell for which served NR cell information is requested. |
+| >Full NR List | | | | |
+| >>Complete Information Request Indicator | M | | ENUMERATED (allServedCellsNR, ...) | Included when the NG-RAN node requests the complete list of served cells for a gNB |
+
+| Range bound | Explanation |
+|---------------------------|------------------------------------------------------------------------|
+| maxnoofCellsInNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+## 9.2.2.18 SUL Information
+
+This IE contains information about the SUL carrier.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|----------------------------|----------|-------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| SUL Frequency Info | M | | INTEGER (0..maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [24] section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block (Common RB 0) of the SUL carrier. Its lowest subcarrier is also known as Point A. | – | |
+| SUL Transmission Bandwidth | M | | NR Transmission Bandwidth 9.2.2.20 | | – | |
+| Carrier List | O | | NR Carrier List 9.2.2.63 | If included, the SUL Transmission Bandwidth IE shall be ignored. | YES | ignore |
+| Frequency Shift 7p5khz | O | | ENUMERATED (false, true, ...) | Indicate whether the value of $\Delta_{\text{shift}}$ is 0kHz or 7.5kHz when calculating $F_{\text{REF,shift}}$ as defined in Section 5.4.2.1 | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| | | | | of TS 38.104 [24]. | | |
+
+| Range bound | Explanation |
+|-------------|----------------------------------------------|
+| maxNRARFCN | Maximum value of NRARFCNs. Value is 3279165. |
+
+## 9.2.2.19 NR Frequency Info
+
+The NR Frequency Info defines the carrier frequency and bands used in a cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD or for SUL carrier.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|-------------------------------|----------|--------------------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| NR ARFCN | M | | INTEGER (0..maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [24], section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block (Common RB 0) of the carrier. Its lowest subcarrier is also known as Point A. | – | |
+| SUL Information | O | | 9.2.2.18 | | – | |
+| <b>NR Frequency Band List</b> | | 1 | | | – | |
+| >NR Frequency Band Item | | 1..<maxno ofNRCellBands> | | | – | |
+| >>NR Frequency Band | M | | INTEGER (1..1024, ...) | Primary NR Operating Band as defined in TS 38.104 [24], section 5.4.2.3. The value 1 corresponds e n1, value 2 corresponds to NR operating band n2, etc. | – | |
+| >>>Supported SUL band List | | 0..<maxno ofNRCellBands> | | | – | |
+| >>>Supported SUL band Item | M | | INTEGER (1..1024, ...) | Supplementary NR Operating Band as defined in TS 38.104 [24] section 5.4.2.3 | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------|----------|-------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | that can be used for SUL duplex mode as per TS 38.101-1 table 5.2-1.<br>The value 80 corresponds to NR operating band n80, value 81 corresponds to NR operating band n81, etc. | | |
+| Frequency Shift 7p5khz | O | | ENUMERATED (false, true, ...) | Indicate whether the value of $\Delta_{\text{shift}}$ is 0kHz or 7.5kHz when calculating $F_{\text{REF,shift}}$ as defined in Section 5.4.2.1 of TS 38.104 [24]. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------------|----------------------------------------------------------------------|
+| maxNRARFCN | Maximum value of NRARFCNs. Value is 3279165. |
+| maxnoofNRCellBands | Maximum no. of frequency bands supported for a NR cell. Value is 32. |
+
+## 9.2.2.20 NR Transmission Bandwidth
+
+The *NR Transmission Bandwidth* IE is used to indicate either the UL or the DL transmission bandwidth.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NR SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs480, scs960) | The values scs15, scs30, scs60 and scs120 corresponds to the sub carrier spacing in TS 38.104 [24]. |
+| NR NRB | M | | ENUMERATED (nrb11, nrb18, nrb24, nrb25, nrb31, nrb32, nrb38, nrb51, nrb52, nrb65, nrb66, nrb78, nrb79, nrb93, nrb106, nrb107, nrb121, nrb132, nrb133, nrb135, nrb160, nrb162, nrb189, nrb216, nrb217, nrb245, nrb264, nrb270, nrb273, ..., nrb33, nrb62, nrb124, nrb148, nrb248, nrb44, nrb58, nrb92, nrb119, nrb188, nrb242, nrb15) | This IE is used to indicate the UL or DL transmission bandwidth expressed in units of resource blocks " $N_{\text{RB}}$ " (TS 38.104 [24]). The values nrb11, nrb18, etc. correspond to the number of resource blocks " $N_{\text{RB}}$ " 11, 18, etc. |
+
+### 9.2.2.21 E-UTRA ARFCN
+
+The E-UTRA Absolute Radio Frequency Channel Number defines the carrier frequency used in an E-UTRAN cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|---------------------------|-------------------------------------------------------------------------------------------|
+| E-UTRA ARFCN | M | | INTEGER<br>(0..maxEARFCN) | The relation between EARFCN and carrier frequency (in MHz) are defined in TS 36.104 [25]. |
+
+| Range bound | Explanation |
+|-------------|--------------------------------------------|
+| maxEARFCN | Maximum value of EARFCNs. Value is 262143. |
+
+### 9.2.2.22 E-UTRA Transmission Bandwidth
+
+The *E-UTRA Transmission Bandwidth* IE is used to indicate the UL or DL transmission bandwidth expressed in units of resource blocks " $N_{RB}$ " (TS 36.104 [25]). The values bw1, bw6, bw15, bw25, bw50, bw75, bw100 correspond to the number of resource blocks " $N_{RB}$ " 6, 15, 25, 50, 75, 100.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------------|----------|-------|--------------------------------------------------------------|-----------------------|
+| E-UTRA Transmission Bandwidth | M | | ENUMERATED<br>(bw6, bw15, bw25, bw50, bw75, bw100,... , bw1) | |
+
+### 9.2.2.23 Number of Antenna Ports E-UTRA
+
+The *Number of Antenna Ports E-UTRA* IE is used to indicate the number of cell specific antenna ports supported by an E-UTRA cell.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------|----------|-------|-----------------------------------|-------------------------------------------------------------------------------|
+| Number of Antenna Ports | M | | ENUMERATED<br>(an1, an2, an4,...) | an1 = One antenna port<br>an2 = Two antenna ports<br>an4 = Four antenna ports |
+
+### 9.2.2.24 E-UTRA Multiband Info List
+
+The *E-UTRA Multiband Info List* IE contains the additional frequency band indicators that an E-UTRA cell belongs to listed in decreasing order of preference and corresponds to information provided in the *MultiBandInfoList* IE specified in TS 36.331 [14].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|----------------------------|-----------------------|----------------------------------------------------------|
+| <b>BandInfo</b> | | 1..<maxnoofE<br>utraBands> | | |
+| >Frequency Band Indicator | M | | INTEGER (1..256, ...) | E-UTRA operating band as defined in TS 36.101 [27, table |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| | | | | 5.5-1] |
+
+| Range bound | Explanation |
+|-------------------|------------------------------------------------------------------------------------|
+| maxnoofEUTRABands | Maximum number of frequency bands that an E-UTRA cell belongs to. The value is 16. |
+
+### 9.2.2.25 E-UTRA PRACH Configuration
+
+This IE indicates the E-UTRA PRACH resources used in an E-UTRA neighbour cell.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------|-------------------------------|-----------------------------------------------------------------------------------------------------------|
+| RootSequenceIndex | M | | INTEGER (0..837) | See section 5.7.2. in TS 36.211 [26] |
+| ZeroCorrelationZoneConfig uration | M | | INTEGER (0..15) | See section 5.7.2. in TS 36.211 [26] |
+| HighSpeedFlag | M | | ENUMERATED (true, false, ...) | "true" corresponds to Restricted set and "false" to Unrestricted set. See section 5.7.2 in TS 36.211 [26] |
+| PRACH-FrequencyOffset | M | | INTEGER (0..94) | See section 5.7.1 of TS 36.211 [26] |
+| PRACH-ConfigurationIndex | C-ifTDD | | INTEGER (0..63) | See section 5.7.1. in TS 36.211 [26] |
+
+| Condition | Explanation |
+|-----------|--------------------------------------------------------------------------------------------------------------------------------------|
+| ifTDD | This IE shall be present if the <i>EUTRA-Mode-Info</i> IE in the <i>Served Cell Information E-UTRA</i> IE is set to the value "TDD". |
+
+### 9.2.2.26 MBSFN Subframe Allocation E-UTRA
+
+The *MBSFN Subframe Allocation E-UTRA* IE is used to indicate the subframes that are allocated for MBSFN within the radio frame allocation period as specified for the *MBSFN-SubframeConfig* IE TS 36.331 [14].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>Subframe Allocation</i> | M | | | |
+| >oneframe | | | | |
+| >>Oneframe Info | M | | BITSTRING (SIZE(6)) | |
+| >fourframes | | | | |
+| >>Fourframes Info | M | | BITSTRING (SIZE(24)) | |
+
+### 9.2.2.27 Global NG-RAN Cell Identity
+
+This IE contains either an NR or an E-UTRA Cell Identity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+|---------------|----------|-------|-----------------------|-----------------------|
+
+| | | | | |
+|----------------------|---|--|---------|--|
+| PLMN Identity | M | | 9.2.2.4 | |
+| NG-RAN Cell Identity | M | | 9.2.2.9 | |
+
+### 9.2.2.28 Connectivity Support
+
+The *Connectivity Support* IE is used to indicate the connectivity supported by a NR cell.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------------------------------|-----------------------|
+| EN-DC Support | M | | ENUMERATED<br>(Supported, Not supported, ...) | |
+
+### 9.2.2.29 Protected E-UTRA Resource Indication
+
+This IE indicates the resources allocated for E-UTRA DL and UL reference and control signals (hereby referred to as protected resources). This information is used in the process of E-UTRA – NR Cell Resource Coordination.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|---------------------------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Activation SFN | M | | INTEGER (0..1023) | Indicates from which SFN of the receiving node the resource allocation is valid. |
+| <b>Protected Resource List</b> | | 1 | | The protected resource pattern is continuously repeated, and it is valid until stated otherwise or until replaced by a new pattern. The pattern does not apply in reserved subframes. |
+| > <b>Protected Resource List Item</b> | | 1..<maxnoofProtectedResourcePatterns> | | Each item describes one transmission pattern. A pattern may comprise several control signals. |
+| >>Resource Type | M | | ENUMERATED<br>(downlinknonCRS,C RS,uplink, ...) | Indicates whether the protected resource is E-UTRA DL non-CRS, E-UTRA CRS or E-UTRA UL. |
+| >>Intra-PRB Protected Resource Footprint | M | | BIT STRING (84, ...) | The bitmap of REs occupied by the protected signal within one PRB. Each position in the bitmap represents an RE in one PRB; value "0" indicates "resource not protected", value "1" indicates "resource protected ". The first bit of the string corresponds to the RE with the smallest time and frequency index in the PRB, where the indexing first goes into the frequency domain. The length of the bit string equals the product of $N_{RB}^{SC}$ and the length of PRB in time dimension, measured in REs. $N_{RB}^{SC}$ is defined in TS 36.211 [26]. The intra-PRB pattern consisting of all "1"s is equivalent to PRB-level |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | granularity. |
+| >>Protected Footprint Frequency Pattern | M | | BIT STRING(6..110, ...) | The bit string indicates in which PRBs inside carrier bandwidth the Intra-PRB Protected Resource Footprint applies. How often in time dimension this frequency pattern applies, depends on time periodicity of Intra-PRB Protected Resource Footprint. The first bit of the bit string corresponds to the PRB occupying the lowest subcarrier frequencies of the carrier bandwidth, where the indexing first goes into the frequency domain. Each position in the string represents a PRB; value "0" indicates " Intra-PRB Protected Resource Footprint does not appear in PRB", value "1" indicates "Intra-PRB Protected Resource Footprint appears in PRB". The length of the bit string equals the number of PRBs in the carrier bandwidth. |
+| >>Protected Footprint Time Pattern | M | | | The description of time periodicity of the Intra-PRB Protected Resource Footprint. |
+| >>>Protected Footprint Time-periodicity | M | | INTEGER(1..320, ...) | Periodicity with which the periodic Intra-PRB Protected Resource Footprint repeats in time-dimension (1= every PRB (i.e. slot), 2=every other PRB (i.e. slot) etc. |
+| >>>Protected Footprint Start Time | M | | INTEGER(1..20, ...) | The time-position of the PRB inside the frame in which the periodic Intra-PRB Protected Resource Footprint appears for the first time. The value "1" corresponds to the receiving node's slot 0 in subframe 0 in the receiving node's radio frame where SFN = Activation SFN. |
+| MBSFN Control Region Length | O | | INTEGER(0..3) | Length of control region in MBSFN subframes. Expressed in REs, in the time dimension. |
+| PDCCH Region Length | M | | INTEGER(1..3) | Length of PDCCH region in regular subframes. Expressed in REs, in the time dimension. |
+
+| Range bound | Explanation |
+|----------------------------------|-------------------------------------------------------|
+| maxnoofProtectedResourcePatterns | Maximum no. protected resource patterns. Value is 16. |
+
+## 9.2.2.30 Data Traffic Resource Indication
+
+This IE indicates the intended data traffic resource allocation for E-UTRA - NR Cell Resource Coordination.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|---------------------------------|------------------------------------------------------------------------|
+| Activation SFN | M | | INTEGER (0..1023) | Indicates from which SFN of the receiving node the agreement is valid. |
+| CHOICE <i>Shared Resource Type</i> | M | | | |
+| >UL Only Sharing | | | | |
+| >>UL Resource Bitmap | M | | Data Traffic Resources 9.2.2.31 | |
+| >UL and DL Sharing | | | | |
+| >>CHOICE <i>UL Resources</i> | M | | | |
+| >>>Unchanged | | | NULL | |
+| >>>Changed | | | | |
+| >>>>UL Resource Bitmap | M | | Data Traffic Resources 9.2.2.31 | |
+| >>CHOICE <i>DL Resources</i> | M | | | |
+| >>>Unchanged | | | NULL | |
+| >>>Changed | | | | |
+| >>>>DL Resource Bitmap | M | | Data Traffic Resources 9.2.2.31 | |
+| Reserved Subframe Pattern | O | | 9.2.2.32 | Indicates subframes in which the resource allocation does not hold. |
+
+### 9.2.2.31 Data Traffic Resources
+
+The *Data Traffic Resources* IE indicates the intended data traffic resource allocation for E-UTRA - NR Cell Resource Coordination.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Data Traffic Resources | M | | BIT STRING (6..17600) | The indication of resources allocated to E-UTRA PDSCH/PUSCH. Each position in the bit string represents a PRB pair in a subframe; value "0" indicates "resource not intended to be used for transmission", value "1" indicates "resource intended to be used for transmission ". The first bit of the bit string corresponds to the PRB pair occupying the lowest subcarrier frequencies of the carrier, where the indexing first goes into the frequency domain. The bit string may span across multiple contiguous subframes. The first position of the Data Traffic Resources IE corresponds to the receiving node's subframe 0 in a receiving node's radio frame where SFN = |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | Activation SFN.<br>The length of the bit string is an integer multiple of $N_{RB}^{DL}$ or $N_{RB}^{UL}$ , defined in TS 36.211 [26]. |
+
+### 9.2.2.32 Reserved Subframe Pattern
+
+The *Reserved Subframe Pattern* IE indicates the pattern of subframes in which the *Protected E-UTRA Resource Indication* and *Data Traffic Resource Indication* do not hold.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------|----------|-------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Subframe Type | M | | ENUMERATED(MB SFN, non-MBSFN, ...) | Indicates what type of non-regular subframes the <i>Reserved Subframe Pattern</i> refers to (e.g. MBSFN). |
+| Reserved Subframe Pattern | M | | BIT STRING (10..160) | Each position in the bitmap represents a subframe. Value '0' indicates "regular subframe". Value '1' indicates "reserved subframe". For MBSFN subframes, the exception refers only to the non-control region of the subframe. The bit string may span across multiple contiguous subframes. The first position of the Subframe Configuration IE corresponds to the receiving node's subframe 0 in a receiving node's radio frame where SFN = Activation SFN. The IE is ignored if received by the ng-eNB. |
+| MBSFN Control Region Length | O | | INTEGER(0..3) | Length of control region in MBSFN subframes. Expressed in REs, in the time dimension. |
+
+### 9.2.2.33 MR-DC Resource Coordination Information
+
+The *MR-DC Resource Coordination Information* IE is used to coordinate resource utilisation between the M-NG-RAN node and the S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------------------|----------|-------|-----------------------|------------------------------------------|
+| CHOICE <i>NG-RAN Node Resource Coordination Information</i> | M | | | |
+| >EUTRA | | | | |
+| >>E-UTRA Resource Coordination Information | | | 9.2.2.34 | E-UTRA resource coordination information |
+| >NR | | | | |
+| >>NR Resource | | | 9.2.2.35 | NR resource coordination |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------|-----------------------|
+| Coordination Information | | | | information |
+
+### 9.2.2.34 E-UTRA Resource Coordination Information
+
+The *E-UTRA Resource Configuration Information* IE indicates LTE resource allocation at ng-eNB used at the gNB to coordinate resource or sidelink resource utilisation between M-NG-RAN-node and S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------|----------|-------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| EUTRA Cell ID | M | | E-UTRA CGI<br>9.2.2.8 | This IE indicates the SpCell. |
+| UL Coordination Information | M | | BIT STRING<br>(6..4400, ...) | <p>Each position in the bitmap represents a PRB pair in a subframe; value "0" indicates "PCell resource not intended to be used for transmission by the sending node", value "1" indicates "PCell resource intended to be used for transmission by the sending node". The bit string spans from the first PRB pair of the first represented subframe to the last PRB pair of the same subframe and then moves to the following PRBs in the following subframes in the same order. Each position is applicable only in positions corresponding to UL subframes or SL subframes for sidelink transmission.</p> <p>The bit string may span across multiple contiguous subframes (maximum 40).</p> <p>The first position of the <i>UL Coordination Information</i> corresponds to subframe 0 in a radio frame where <i>SFN</i> = 0.</p> <p>The length of the bit string is an integer multiple of . is defined in TS 36.211 [26].</p> <p>The UL Coordination Information is continuously repeated.</p> |
+| DL Coordination Information | O | | BIT STRING<br>(6..4400, ...) | <p>Each position in the bitmap represents a PRB pair in a subframe; value "0" indicates "PCell resource not intended to be used for transmission by the sending node", value "1" indicates "PCell resource intended to be used for transmission by the sending node". The bit string spans from the first PRB pair of the first represented subframe to the last PRB pair of the same subframe</p> |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | and then moves to the following PRBs in the following subframes in the same order. Each position is applicable only in positions corresponding to DL subframes. The bit string may span across multiple contiguous subframes (maximum 40). The first position of the <i>DL Coordination Information</i> corresponds to the receiving node's subframe 0 in a receiving node's radio frame where <i>SFN</i> = 0. The length of the bit string is an integer multiple of $N_{RB}^{DL}$ . $N_{RB}^{DL}$ is defined in TS 38.211 [26]. The DL Coordination Information is continuously repeated. |
+| NR CGI | O | | 9.2.2.7 | This IE indicates the assumed SpCell. |
+| E-UTRA Coordination Assistance Information | O | | 9.2.2.36 | |
+
+### 9.2.2.35 NR Resource Coordination Information
+
+The *NR Resource Coordination Information* IE indicates resources within the bandwidth of the ng-eNB SpCell which are not available for use by the ng-eNB and is used at the ng-eNB to coordinate resource or sidelink resource utilisation between the gNB and the ng-eNB.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------|----------|-------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NR CGI | M | | 9.2.2.7 | This IE indicates the SpCell. |
+| UL Coordination Information | M | | BIT STRING (6..4400, ...) | Each position in the bitmap represents a PRB pair in a subframe; value "0" indicates "SpCell resource not intended to be used for transmission by the sending node", value "1" indicates "SpCell resource intended to be used for transmission by the sending node". The bit string spans from the first PRB pair of the first represented subframe to the last PRB pair of the same subframe and then moves to the following PRBs in the following subframes in the same order. Each position is applicable only in positions corresponding to UL subframes or SL subframes for sidelink transmission. The bit string may span across multiple contiguous subframes (maximum 40). The first position |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------------|----------|-------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | <p>of the <i>UL Coordination Information</i> corresponds to the receiving node's subframe 0 in a receiving node's radio frame where <math>SFN = 0</math>.</p> <p>The length of the bit string is an integer multiple of <math>N_{RB}^{DL}</math>. <math>N_{RB}^{DL}</math> is defined in TS 36.211 [26]. The UL Coordination Information is continuously repeated.</p> |
+| DL Coordination Information | O | | BIT STRING (6..4400, ...) | <p>Each position in the bitmap represents a PRB pair in a subframe; value "0" indicates "SpCell resource not intended to be used for transmission by the sending node", value "1" indicates "SpCell resource intended to be used for transmission by the sending node". The bit string spans from the first PRB pair of the first represented subframe to the last PRB pair of the same subframe and then moves to the following PRBs in the following subframes in the same order. Each position is applicable only in positions corresponding to DL subframes. The bit string may span across multiple contiguous subframes (maximum 40). The first position of the <i>DL Coordination Information</i> corresponds to the receiving node's subframe 0 in a receiving node's radio frame where <math>SFN = 0</math>.</p> <p>The length of the bit string is an integer multiple of <math>N_{RB}^{DL}</math>. <math>N_{RB}^{DL}</math> is defined in TS 36.211 [26]. The DL Coordination Information is continuously repeated.</p> |
+| EUTRA Cell ID | O | | ECGI 9.2.2.8 | Reference cell for <i>UL Coordination Information</i> IE and <i>DL Coordination Information</i> IE. |
+| NR Coordination Assistance Information | O | | 9.2.2.37 | |
+
+### 9.2.2.36 E-UTRA Coordination Assistance Information
+
+The *E-UTRA Coordination Assistance Information* IE is provided by the ng-eNB and used by the gNB to determine further coordination of resource utilisation between the gNB and the ng-eNB.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|-----------------------|-----------------------|
+|---------------|----------|-------|-----------------------|-----------------------|
+
+| | | | | |
+|--------------------------------------------|---|--|--------------------------------------------|--|
+| E-UTRA Coordination Assistance Information | M | | ENUMERATED(Coordination Not Required, ...) | |
+|--------------------------------------------|---|--|--------------------------------------------|--|
+
+### 9.2.2.37 NR Coordination Assistance Information
+
+The *NR Coordination Assistance Information* IE is provided by the gNB and used by the ng-eNB to determine further coordination of resource utilisation between the gNB and the ng-eNB.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------------|----------|-------|--------------------------------------------|-----------------------|
+| NR Coordination Assistance Information | M | | ENUMERATED(Coordination Not Required, ...) | |
+
+### 9.2.2.38 NE-DC TDM Pattern
+
+The *NE-DC TDM Pattern* IE is provided by the gNB and used by the ng-eNB to determine UL/DL reference configuration indicating the time during which a UE configured with NE-DC is allowed to transmit.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------------|----------|-------|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| Subframe Assignment | M | | ENUMERATED (sa0, sa1, sa2, sa3, sa4, sa5, sa6) | Indicates DL/UL subframe configuration where sa0 points to Configuration 0, sa1 to Configuration 1 etc. as specified in TS 36.331 [14]. |
+| Harq Offset | M | | INTEGER (0..9) | Indicates a HARQ subframe offset that is applied to the subframes designated as UL in the associated subframe assignment, see TS 36.331 [14] |
+
+### 9.2.2.39 Interface Instance Indication
+
+The Interface Instance Indication identifies the interface instance the XnAP message is destined for.
+
+NOTE: The Interface Instance Indication is allocated so that it can be associated with an Xn-C interface instance. The Interface Instance Indication may identify more than one interface instance.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------------|----------|-------|-----------------------|-----------------------|
+| Interface Instance Indication | M | | INTEGER (0..255, ...) | |
+
+### 9.2.2.39a Configured TAC Indication
+
+This IE indicates that in a NR cell served by the gNB, the TAC with which this IE is associated, is only configured but not broadcast.
+
+NOTE: This IE is defined in accordance to the possibility foreseen in TS 38.331 [10] to not broadcast the TAC if the NR cell only supports PSCell/SCell functionality.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|------------------------|-----------------------|
+| Configured TAC Indication | M | | ENUMERATED (true, ...) | |
+
+### 9.2.2.40 Intended TDD DL-UL Configuration NR
+
+This IE contains the subcarrier spacing, cyclic prefix and TDD DL-UL slot configuration of an NR cell that a neighbour NG-RAN node needs to take into account for cross-link interference mitigation, and/or for NR-DC power coordination, when operating its own cells.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|------------------------------------|----------|------------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| NR SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs480, scs960) | The values scs15, scs30, scs60 and scs120 corresponds to the sub carrier spacing in TS 38.104 [24]. | – | |
+| NR Cyclic Prefix | M | | ENUMERATED (Normal, Extended, ...) | The type of cyclic prefix, which determines the number of symbols in a slot. | – | |
+| NR DL-UL Transmission Periodicity | M | | ENUMERATED (ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms3, ms4, ms5, ms10, ms20, ms40, ms60, ms80, ms100, ms120, ms140, ms160, ...) | The periodicity is expressed in the format msXpYZ, and equals X.YZ milliseconds. | – | |
+| <b>Slot Configuration List</b> | | 1 | | | – | |
+| >Slot Configuration List Item | | 1..<maxnofslots> | | | – | |
+| >>Slot Index | | | INTEGER (0..5119) | | – | |
+| >>CHOICE Symbol Allocation in Slot | M | | | | – | |
+| >>>All DL | | | | | – | |
+| >>>All UL | | | | | – | |
+| >>>Both DL and UL | | | | | – | |
+| >>>>Number of DL Symbols | M | | INTEGER (0..13) | Number of consecutive DL symbols in the slot identified by Slot Index. If extended cyclic prefix is used, the maximum value is 11. The <i>Permutation IE</i> | – | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | indicates the location of DL symbols in the slot. | | |
+| >>>>Number of UL Symbols | M | | INTEGER (0..13) | Number of consecutive UL symbols in the slot identified by Slot Index. If extended cyclic prefix is used, the maximum value is 11. The <i>Permutation</i> IE indicates the location of UL symbols in the slot. | – | |
+| >>>>Permutation | O | | ENUMERATED (DFU, UFD, ...) | If not present, the default value is DFU. | YES | ignore |
+
+| Range bound | Explanation |
+|--------------|---------------------------------------------------------------------|
+| maxnoofslots | Maximum length of number of slots in a 10-ms period. Value is 5120. |
+
+#### 9.2.2.41 Cell and Capacity Assistance Information NR
+
+The *Cell and Capacity Assistance Information NR* IE is used by the NG-RAN node to request information about NR cells and it includes information about cell list size capacity.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------|----------|-------|-----------------------|-----------------------|
+| Maximum Cell List Size | O | | 9.2.2.44 | |
+| Cell Assistance Information NR | O | | 9.2.2.17 | |
+
+#### 9.2.2.42 Cell and Capacity Assistance Information E-UTRA
+
+The *Cell and Capacity Assistance Information E-UTRA* IE is used by the NG-RAN node to request information about E-UTRA cells and it includes information about cell list size capacity.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------------------|----------|-------|-----------------------|-----------------------|
+| Maximum Cell List Size | O | | 9.2.2.44 | |
+| Cell Assistance Information E-UTRA | O | | 9.2.2.43 | |
+
+#### 9.2.2.43 Cell Assistance Information E-UTRA
+
+The *Cell Assistance Information* IE is used by the NG-RAN node to request information about E-UTRA cells.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------------------------|----------|----------------------------------------------|-------------------------------------------|---------------------------------------------------------------------------------------|
+| <i>CHOICE Cell Assistance Type</i> | M | | | |
+| > <i>Limited EUTRA List</i> | | | | |
+| >>List of Requested E-UTRA Cells | | 1 .. <<br><i>maxnoofCellsInNG-RAN node</i> > | | Included when the NG-RAN node requests a limited list of served E-UTRA cells. |
+| >>>E-UTRA CGI | M | | 9.2.2.7 | E-UTRA cell for which served E-UTRA cell information is requested. |
+| > <i>Full E-UTRA List</i> | | | | |
+| >>Complete Information Request Indicator | M | | ENUMERATED<br>(allServedCellsE-UTRA, ...) | Included when the NG-RAN node requests the complete list of served cells for a ng-eNB |
+
+| Range bound | Explanation |
+|----------------------------------|------------------------------------------------------------------------|
+| <i>maxnoofCellsInNG-RAN node</i> | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+#### 9.2.2.44 Maximum Cell List Size
+
+This IE indicates the maximum size the sending node can handle for a given cell list.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|----------------------------|-----------------------|
+| Maximum Cell List Size | M | | INTEGER<br>(0..16384, ...) | |
+
+#### 9.2.2.45 Message Oversize Notification
+
+This IE indicates that a failure has occurred due to an excessive message size and it indicates the maximum number of cells that can be received in the *List of Served Cells NR* IE or in the *List of Served Cells E-UTRA* IE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-----------------------|-----------------------|
+| Maximum Cell List Size | M | | 9.2.2.44 | |
+
+#### 9.2.2.46 Partial List Indicator
+
+The *Partial List Indicator* IE is used by the NG-RAN node to indicate whether the served cell information contained in the same message is a partial list.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------|----------|-------|------------------------------|-----------------------|
+| Partial List Indicator | M | | ENUMERATED<br>(partial, ...) | |
+
+#### 9.2.2.47 Offset of NB-IoT Channel Number to EARFCN
+
+This IE is used to indicate the offset of the NB-IoT Channel Number to the EARFCN (TS 36.104 [25]).
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Offset of NB-IoT Channel Number to EARFCN | M | | ENUMERATED<br>(-10, -9, -8.5, -8, -7, -6, -5, -4.5, -4, -3, -2, -1, -0.5, 0, 1, 2, 3, 3.5, 4, 5, 6, 7, 7.5, 8, 9, ...) | |
+
+#### 9.2.2.48 NB-IoT UL DL Alignment Offset
+
+This IE is used to indicate the offset between the UL carrier frequency center with respect to DL carrier frequency center.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------------|----------|-------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| NB-IoT UL DL Alignment Offset | M | | ENUMERATED<br>(-7.5, 0, 7.5, ...) | Unit: kHz<br>Corresponds to information provided in the <i>TDD-UL-DL-AlignmentOffset-NB</i> IE as specified in TS 36.331 [14]. |
+
+#### 9.2.2.49 TNL Capacity Indicator
+
+The *TNL Capacity Indicator* IE indicates the offered and available capacity of the Transport Network experienced by the NG RAN cell
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| DL TNL Offered Capacity | M | | INTEGER (1.. 16777216,...) | Maximum capacity offered by the transport portion of the cell in kbps |
+| DL TNL Available Capacity | M | | INTEGER (0.. 100, ...) | Available capacity over the transport portion serving the cell in percentage. Value 100 corresponds to the offered capacity. |
+| UL TNL Offered Capacity | M | | INTEGER (1.. 16777216, ...) | Maximum capacity offered by the transport portion of the cell in kbps |
+| UL TNL Available Capacity | M | | INTEGER (0.. 100, ...) | Available capacity over the transport portion serving the cell in percentage. Value 100 corresponds to the offered capacity. |
+
+#### 9.2.2.50 Radio Resource Status
+
+The *Radio Resource Status* IE indicates the usage of the PRBs per cell for MIMO, per SSB area, and per slice for all traffic in Downlink and Uplink and the usage of PDCCH CCEs for Downlink and Uplink scheduling.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| CHOICE <i>Radio Resource Status Type</i> | M | | | | – | |
+| >ng-eNB | | | | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-----------------------|-----------------------|-------------------------------------------------------------------------------|-------------|----------------------|
+| >>DL GBR PRB usage | M | | INTEGER (0..100) | Per cell DL GBR PRB usage | – | |
+| >>UL GBR PRB usage | M | | INTEGER (0..100) | Per cell UL GBR PRB usage | – | |
+| >>DL non-GBR PRB usage | M | | INTEGER (0..100) | Per cell DL non-GBR PRB usage | – | |
+| >>UL non-GBR PRB usage | M | | INTEGER (0..100) | Per cell UL non-GBR PRB usage | – | |
+| >>DL Total PRB usage | M | | INTEGER (0..100) | Per cell DL Total PRB usage | – | |
+| >>UL Total PRB usage | M | | INTEGER (0..100) | Per cell UL Total PRB usage | – | |
+| >>DL scheduling PDCCH CCE usage | O | | INTEGER (0..100) | | YES | ignore |
+| >>UL scheduling PDCCH CCE usage | O | | INTEGER (0..100) | | YES | ignore |
+| >gNB | | | | | – | |
+| >>SSB Area Radio Resource Status List | | 1 | | | – | |
+| >>>SSB Area Radio Resource Status Item | | 1..<maxno ofSSBAreas> | | | – | |
+| >>>>SSB Index | M | | INTEGER (0..63) | | – | |
+| >>>>SSB Area DL GBR PRB usage | M | | INTEGER (0..100) | Per SSB area DL GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>SSB Area UL GBR PRB usage | M | | INTEGER (0..100) | Per SSB area UL GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>SSB Area DL non-GBR PRB usage | M | | INTEGER (0..100) | Per SSB area DL non-GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>SSB Area UL non-GBR PRB usage | M | | INTEGER (0..100) | Per SSB area UL non-GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>SSB Area DL Total PRB usage | M | | INTEGER (0..100) | Per SSB area DL Total PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>SSB Area UL Total PRB usage | M | | INTEGER (0..100) | Per SSB area UL Total PRB usage in percentage of the cell total PRB number. | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|-------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>>DL scheduling PDCCH CCE usage | O | | INTEGER (0..100) | | YES | ignore |
+| >>>>UL scheduling PDCCH CCE usage | O | | INTEGER (0..100) | | YES | ignore |
+| >>Slice Radio Resource Status List | | 0..1 | | | YES | ignore |
+| >>>Slice Radio Resource Status Item | | 1..<maxnoofB PLMNs> | | | – | |
+| >>>>PLMN Identity | M | | 9.2.2.4 | | – | |
+| >>>>S-NSSAI Radio Resource Status List | | 1 | | | – | |
+| >>>>>S-NSSAI Radio Resource Status Item | | 1..<maxno ofSliceItems> | | | – | |
+| >>>>>>S-NSSAI | M | | 9.2.3.21 | | – | |
+| >>>>>>Slice DL GBR PRB usage | M | | INTEGER (0..100) | Per slice DL GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>>>Slice UL GBR PRB usage | M | | INTEGER (0..100) | Per slice UL GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>>>Slice DL non-GBR PRB usage | M | | INTEGER (0..100) | Per slice DL non-GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>>>Slice UL non-GBR PRB usage | M | | INTEGER (0..100) | Per slice UL non-GBR PRB usage in percentage of the cell total PRB number. | – | |
+| >>>>>>Slice DL Total PRB allocation | M | | INTEGER (0..100) | Total amount of DL PRBs available per cell for the slice if all the resources the slice could access were usable. | – | |
+| >>>>>>Slice UL Total PRB allocation | M | | INTEGER (0..100) | Total amount of UL PRBs available per cell for the slice if all the resources the slice could access were usable. | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | usable. | | |
+| <b>>>MIMO PRB usage Information</b> | O | | | | YES | ignore |
+| >>>DL GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell DL GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [42]. | – | |
+| >>>UL GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell UL GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [42]. | – | |
+| >>>DL non-GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell DL non-GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [42]. | – | |
+| >>>UL non-GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell UL non-GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [42]. | – | |
+| >>>DL Total PRB usage for MIMO | M | | INTEGER (0..100) | Per cell DL Total PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [42]. | – | |
+| >>>UL Total PRB usage for MIMO | M | | INTEGER (0..100) | Per cell UL Total PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [42]. | – | |
+
+| Range bound | Explanation |
+|-------------------|------------------------------------------------------------------------------|
+| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. |
+| maxnoofBPLMNs | Maximum no. of broadcast PLMNs by a cell. Value is 12. |
+
+## 9.2.2.51 Composite Available Capacity Group
+
+The *Composite Available Capacity Group* IE indicates the overall available resource level per cell and per SSB area in the cell in Downlink, Uplink and Supplementary Uplink.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------|----------|-------|---------------------------------------|-----------------------------------------------------------|-------------|----------------------|
+| Composite Available Capacity Downlink | M | | Composite Available Capacity 9.2.2.52 | For the Downlink | – | |
+| Composite Available Capacity Uplink | M | | Composite Available Capacity 9.2.2.52 | For the Uplink, including both NUL and SUL (if available) | – | |
+| Composite Available Capacity Supplementary Uplink | O | | Composite Available Capacity 9.2.2.52 | For the SUL | YES | ignore |
+
+### 9.2.2.52 Composite Available Capacity
+
+The *Composite Available Capacity* IE indicates the overall available resource level in the cell in either Downlink or Uplink.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|---------------------------------------------------------------------|
+| Cell Capacity Class Value | O | | 9.2.2.53 | |
+| Capacity Value | M | | 9.2.2.54 | '0' indicates no resource is available, Measured on a linear scale. |
+
+### 9.2.2.53 Cell Capacity Class Value
+
+The *Cell Capacity Class Value* IE indicates the value that classifies the cell capacity with regards to the other cells. The *Cell Capacity Class Value* IE only indicates resources that are configured for traffic purposes.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Capacity Class Value | M | | INTEGER (1..100,...) | Value 1 indicates the minimum cell capacity, and 100 indicates the maximum cell capacity. There should be a linear relation between cell capacity and Cell Capacity Class Value. |
+
+### 9.2.2.54 Capacity Value
+
+The *Capacity Value* IE indicates the amount of resources per cell and per SSB area that are available relative to the total NG-RAN resources. The capacity value should be measured and reported so that the minimum NG-RAN resource usage of existing services is reserved according to implementation. The *Capacity Value* IE can be weighted according to the ratio of cell capacity class values, if available.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|--------------------------------|
+| Capacity Value | M | | INTEGER (0..100) | Value 0 indicates no available |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------|----------|----------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | capacity, and 100 indicates maximum available capacity with respect to the whole cell. Capacity Value should be measured on a linear scale. |
+| <b>SSB Area Capacity Value List</b> | | 0..1 | | |
+| > <b>SSB Area Capacity Value Item</b> | | 1..<maxnoofSSBAreas> | | |
+| >>SSB Index | M | | INTEGER (0..63) | |
+| >>SSB Area Capacity Value | M | | INTEGER (0..100) | Value 0 indicates no available capacity, and 100 indicates maximum available capacity . SSB Area Capacity Value should be measured on a linear scale. |
+
+| Range bound | Explanation |
+|-----------------|------------------------------------------------------------------------------|
+| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
+
+### 9.2.2.55 Slice Available Capacity
+
+The *Slice Available Capacity* IE indicates the amount of resources per network slice that are available per cell relative to the total NG-RAN resources per cell. The *Slice Available Capacity Value Downlink* IE and the *Slice Available Capacity Value Uplink* IE can be weighted according to the ratio of the corresponding cell capacity class values contained in the *Composite Available Capacity Group* IE, if available.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|--------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Slice Available Capacity</b> | | 1..<maxnoofBPLMNs> | | |
+| >PLMN Identity | M | | 9.2.2.4 | Broadcast PLMN |
+| > <b>S-NSSAI Available Capacity List</b> | | 1 | | |
+| >> <b>S-NSSAI Available Capacity Item</b> | M | 1 .. <maxnoofSliceItems> | | |
+| >>>S-NSSAI | | | 9.2.3.21 | |
+| >>>Slice Available Capacity Value Downlink | M | | INTEGER (0..100) | Value 0 indicates no available capacity, and 100 indicates maximum available capacity . Slice <i>Available Capacity Value Downlink</i> should be measured on a linear scale. |
+| >>>Slice Available Capacity Value Uplink | M | | INTEGER (0..100) | Value 0 indicates no available capacity, and 100 indicates maximum available capacity. Slice <i>Available Capacity Value Uplink</i> should be measured on a linear scale. |
+
+| Range bound | Explanation |
+|-------------|-------------|
+|-------------|-------------|
+
+| | |
+|-------------------|--------------------------------------------------------------|
+| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. |
+| maxnoofBPLMNs | Maximum no. of PLMN Ids.broadcast in a cell. Value is 12. |
+
+### 9.2.2.56 RRC Connections
+
+The *RRC Connections* IE indicates the overall status of RRC connections per cell.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-----------------------|-----------------------|
+| Number of RRC Connections | M | | 9.2.2.57 | |
+| Available RRC Connection Capacity Value | M | | 9.2.2.58 | |
+
+### 9.2.2.57 Number of RRC Connections
+
+The *Number of RRC Connections* IE indicates the maximum supported number of UEs in RRC\_CONNECTED mode.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|------------------------|-----------------------|
+| Number of RRC Connections | M | | INTEGER (1..65536,...) | |
+
+### 9.2.2.58 Available RRC Connection Capacity Value
+
+The *Available RRC Connection Capacity Value* IE indicates the residual percentage of the number of RRC connections, relative to the maximum number of RRC connections supported by the cell.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Available RRC Connection Capacity Value | M | | INTEGER (0..100) | Value 0 indicates no available capacity, and 100 indicates maximum available capacity with respect to the whole cell. Capacity Value should be measured on a linear scale. |
+
+### 9.2.2.59 UE RLF Report
+
+This IE contains the RLF Report to be transferred.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| CHOICE <i>type</i> | M | | | | – | |
+| >NR | | | | | – | |
+| >>NR UE RLF Report Container | M | | OCTET STRING | <i>Includes the nr-RLF-Report contained in the UEInformationResponse message as defined in TS 38.331 [10].</i> | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >LTE | | | | | – | |
+| >>LTE UE RLF Report Container | M | | OCTET STRING | Includes the <i>rLF-Report-r9</i> contained in the <i>UEInformationResponse</i> message defined in TS 36.331 [14] | – | |
+| >LTE Extension | | | | | YES | ignore |
+| >>LTE UE RLF Report Container | M | | OCTET STRING | Includes the <i>rLF-Report-r9</i> contained in the <i>UEInformationResponse</i> message as defined in TS 36.331 [14] | – | |
+| >>LTE UE RLF Report Container Extend Band | M | | OCTET STRING | Includes the <i>rLF-Report-v9e0</i> contained in the <i>UEInformationResponse</i> message as defined in TS 36.331 [14] | – | |
+
+### 9.2.2.60 Mobility Parameters Information
+
+The *Mobility Parameters Information* IE contains the change of the Handover Trigger as compared to its current value. The Handover Trigger corresponds to the threshold at which a cell initialises the handover preparation procedure towards a specific neighbour cell. Positive value of the change means the handover is proposed to take place later.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|----------------------------------------|
+| Handover Trigger Change | M | | INTEGER (-20 .. 20) | The actual value is IE value * 0.5 dB. |
+
+### 9.2.2.61 Mobility Parameters Modification Range
+
+The *Mobility Parameters Modification Range* IE contains the range of *Handover Trigger Change* values permitted by the NG-RAN node<sub>2</sub> at the moment the MOBILITY CHANGE FAILURE message is sent.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|-------|-----------------------|----------------------------------------|
+| Handover Trigger Change Lower Limit | M | | INTEGER (-20 .. 20) | The actual value is IE value * 0.5 dB. |
+| Handover Trigger Change Upper Limit | M | | INTEGER (-20 .. 20) | The actual value is IE value * 0.5 dB. |
+
+### 9.2.2.62 Number of Active UEs
+
+The *Number of Active UEs* IE indicates the mean number of active UEs as defined in TS 38.314 [42].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Mean number of Active UEs | M | | INTEGER (0..16777215, ...) | As defined in TS 38.314 [42] and where value "1" is equivalent to 0.1 Active UEs, value "2" is equivalent to 0.2 Active UEs, value <i>n</i> is equivalent to <i>n</i> /10 Active UEs. |
+
+### 9.2.2.63 NR Carrier List
+
+This IE indicates the SCS-specific carriers per TDD, per DL, per UL or per SUL of an NR cell.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------|----------|--------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>NR Carrier Item</b> | | 1..<maxnoofNRSCSs> | | |
+| >NR SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs480, scs960) | SCS for the corresponding carrier. |
+| >Offset to Carrier | M | | INTEGER (0.. 2199, ...) | Offset in frequency domain between Point A (lowest subcarrier of common RB 0) and the lowest usable subcarrier on this carrier in number of PRBs (using the <i>NR SCS</i> IE defined for this carrier). The maximum value corresponds to 275×8−1. See TS 38.211 [39], clause 4.4.2. |
+| >Carrier Bandwidth | M | | INTEGER (1..maxnoofPhysicalResourceBlocks, ...) | Width of this carrier in number of PRBs (using the <i>NR SCS</i> IE defined for this carrier). See TS 38.211 [39], clause 4.4.2. |
+
+| Range bound | Explanation |
+|-------------------------------|----------------------------------------------------------------------------------------------------|
+| maxnoofNRSCSs | Maximum no. of SCS-specific carriers per TDD, per DL, per UL or per SUL of an NR cell. Value is 5. |
+| maxnoofPhysicalResourceBlocks | Maximum no. of Physical Resource Blocks. Value is 275. |
+
+### 9.2.2.64 SSB Positions In Burst
+
+Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [40], clause 4.1.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>ssb-PositionsInBurst</i> | M | | | The first/ leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------|----------|-------|-----------------------|----------------------------------------------------------------|
+| | | | | indicates that the corresponding SS/PBCH block is transmitted. |
+| >ShortBitmap | | | | |
+| >>ShortBitmap | M | | BIT STRING (SIZE(4)) | |
+| >MediumBitmap | | | | |
+| >>MediumBitmap | M | | BIT STRING (SIZE(8)) | |
+| >LongBitmap | | | | |
+| >>LongBitmap | M | | BIT STRING (SIZE(64)) | |
+
+### 9.2.2.65 NID
+
+This IE is used to identify (together with a PLMN identifier) a Standalone Non-Public Network. The NID is specified in TS 23.003 [22].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| NID | M | | BIT STRING (SIZE(44)) | |
+
+### 9.2.2.66 CAG-Identifier
+
+This IE is used to identify (together with a PLMN identifier) a Public Network Integrated Non-Public Network. The CAG-Identifier is specified in TS 23.003 [22].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|-----------------------|
+| CAG-Identifier | M | | BIT STRING (SIZE(32)) | |
+
+### 9.2.2.67 Broadcast NID List
+
+This IE contains a list of NIDs.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|------------------|-----------------------|-----------------------|
+| <b>Broadcast NID List</b> | | 1..<maxnoofNIDs> | | |
+| >NID | M | | 9.2.2.65 | |
+
+| Range bound | Explanation |
+|-------------|-------------------------------------------------------|
+| maxnoofNIDs | Maximum no. of NIDs broadcast in a cell. Value is 12. |
+
+### 9.2.2.68 Broadcast SNPN ID List
+
+This IE contains a list of SNPN IDs.
+
+| IE/Group Name | Presence | Range | IE type and | Semantics description |
+|---------------|----------|-------|-------------|-----------------------|
+|---------------|----------|-------|-------------|-----------------------|
+
+| | | | reference | |
+|-------------------------------|---|-------------------------|-----------|--|
+| <b>Broadcast SNPN ID List</b> | | 1..<maxnoofS<br>NPNIDs> | | |
+| >PLMN Identity | M | | 9.2.2.4 | |
+| >Broadcast NID List | M | | 9.2.2.67 | |
+
+| Range bound | Explanation |
+|----------------|-----------------------------------------------------------|
+| maxnoofSNPNIDs | Maximum no. of SNPN IDs broadcast in a cell. Value is 12. |
+
+### 9.2.2.69 Broadcast CAG-Identifier List
+
+This IE contains a list of CAG-Identifiers.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|----------|----------------------|-----------------------|-----------------------|
+| <b>Broadcast CAG-Identifier List</b> | | 1..<maxnoofC<br>AGs> | | |
+| >CAG-Identifier | M | | 9.2.2.66 | |
+
+| Range bound | Explanation |
+|-------------|------------------------------------------------------------------|
+| maxnoofCAGs | Maximum no. of CAG-Identifiers broadcast in a cell. Value is 12. |
+
+### 9.2.2.70 Broadcast PNI-NPN ID Information
+
+This IE contains a list of PNI-NPN IDs.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|------------------------|-----------------------|-----------------------|
+| <b>Broadcast PNI-NPN ID Information</b> | | 1..<maxnoofB<br>PLMNs> | | Broadcast PLMNs |
+| >PLMN Identity | M | | 9.2.2.4 | |
+| >Broadcast CAG-Identifier List | M | | 9.2.2.69 | |
+
+| Range bound | Explanation |
+|---------------|--------------------------------------------------------|
+| maxnoofBPLMNs | Maximum no. of broadcast PLMNs by a cell. Value is 12. |
+
+### 9.2.2.71 NPN Broadcast Information
+
+This IE contains NPN related broadcast information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| <b>CHOICE NPN Broadcast Information per PLMN</b> | M | | | |
+| >SNPN Information | | | | |
+| >>Broadcast SNPN ID List | M | | 9.2.2.68 | |
+| >PNI-NPN Information | | | | |
+| >>Broadcast PNI-NPN ID Information | M | | 9.2.2.70 | |
+
+### 9.2.2.72 NPN Support
+
+This IE contains NPN related information associated with Network Slicing information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>NPN Support</i> | M | | | |
+| >SNPN | | | | |
+| >>NID | M | | 9.2.2.65 | This IE is associated with the PLMN Identity and the TAI Slice Support List contained in the <i>TAI Support List IE</i> . Together with the PLMN Identity it identifies the SNPN supported in the corresponding Tracking Area by the NG-RAN node. |
+
+### 9.2.2.73 Global Cell Identity
+
+This IE is used to globally identify an NG-RAN cell or an E-UTRAN cell (see TS 36.300 [12]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+| CHOICE <i>Cell Type</i> | M | | | |
+| >NG-RAN E-UTRA | | | | |
+| >>E-UTRA Cell Identity | M | | BIT STRING (SIZE(28)) | The leftmost bits of the <i>E-UTRA Cell Identity</i> IE correspond to the ng-eNB ID (defined in subclause 9.2.2.2). |
+| >NG-RAN NR | | | | |
+| >>NR Cell Identity | M | | BIT STRING (SIZE(36)) | The leftmost bits of the <i>NR Cell Identity</i> IE correspond to the gNB ID (defined in subclause 9.2.2.1). |
+| >E-UTRAN | | | | |
+| >>E-UTRAN Cell Identity | M | | BIT STRING (SIZE(28)) | The leftmost bits of the <i>E-UTRAN Cell Identity</i> IE value correspond to the eNB ID (defined in section 9.2.22 in TS 36.423 [44]). |
+
+### 9.2.2.74 NPRACH Configuration
+
+This IE indicates the NPRACH Configuration.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|-------|---------------------------------------|----------------------------------------------------------------------------------------|
+| CHOICE <i>FDDorTDD</i> | M | | | |
+| >FDD | | | | |
+| >>NPRACH-CP-Length | M | | ENUMERATED (us66dot7, us266dot7, ...) | |
+| >>Anchor Carrier<br>NPRACH Configuration | M | | OCTET STRING | Includes the <i>NPRACH-ParametersList-NB-r13</i> IE as defined in 6.7.3.2 of TS 36.331 |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------|----------|----------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------------|
+| | | | | [14]. |
+| >>Anchor Carrier EDT NPRACH Configuration | O | | OCTET STRING | Includes the <i>NPRACH-ParametersList-NB-r14</i> IE as defined in 6.7.3.2 of TS 36.331 [14]. |
+| >>Anchor Carrier Format 2 NPRACH Configuration | O | | OCTET STRING | Includes the <i>NPRACH-ParametersListFmt2-NB-r15</i> IE as defined in 6.7.3.2 of TS 36.331 [14]. |
+| >>Anchor Carrier Format 2 EDT NPRACH Configuration | O | | OCTET STRING | Includes the <i>NPRACH-ParametersListFmt2-NB-r15</i> IE as defined in 6.7.3.2 of TS 36.331 [14]. |
+| >>Non Anchor Carrier NPRACH Configuration | O | | OCTET STRING | Includes the <i>UL-ConfigCommonList-NB-r14</i> IE as defined in 6.7.3.1 of TS 36.331 [14]. |
+| >>Non Anchor Carrier Format 2 NPRACH Configuration | O | | OCTET STRING | Includes the <i>UL-ConfigCommonList-NB-v1530</i> IE as defined in 6.7.3.1 of TS 36.331 [14]. |
+| >TDD | | | | |
+| >>NPRACH-PreambleFormat | M | | ENUMERATED (fmt0, fmt1, fmt2, fmt0-a, fmt1-a, ...) | |
+| >>Anchor Carrier NPRACH Configuration TDD | M | | OCTET STRING | Includes the <i>NPRACH-ParametersListTDD-NB-r15</i> IE as defined in 6.7.3.2 of TS 36.331 [14]. |
+| >>Non Anchor Carrier Frequency Configuration list | | 0..<maxnoofNonAnchorCarrierFreqConfig> | | |
+| >>>Non Anchor Carrier Frequency | M | | OCTET STRING | Includes the <i>DL-CarrierConfigCommon-NB-r14</i> IE as defined in 6.7.3.2 of TS 36.331 [14]. |
+| >>Non Anchor Carrier NPRACH Configuration TDD | O | | OCTET STRING | Includes the <i>UL-ConfigCommonListTDD-NB-r15</i> IE as defined in 6.7.3.1 of TS 36.331 [14]. |
+
+| Range bound | Explanation |
+|-----------------------------------|--------------------------------------------------------------------------|
+| maxnoofNonAnchorCarrierFreqConfig | Maximum no. of non-Anchor Carrier Frequency Configurations. Value is 15. |
+
+## 9.2.2.75 SFN Offset
+
+This IE contains the time offset between an absolute time reference and the SFN0 start. The IE is calculated assuming that the SFN transmission started at the absolute time reference. The absolute time reference chosen is 1980-01-06 T00:00:19 International Atomic Time (TAI).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SFN Time Offset | M | | BIT STRING (SIZE(24)) | Time offset in microseconds between the absolute time reference "1980-01-06 T00:00:19 International Atomic Time (TAI)" and the SFN0 start. The maximum usable value is $(1024 \cdot 10^4 - 1)$ . Values higher than the maximum are discarded. |
+
+## 9.2.2.76 CHO Configuration
+
+This IE contains the CHO configuration information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|---------------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>CHO Candidate Cell List</b> | | 1 | | |
+| > <b>CHO Candidate Cell Item</b> | | 1 .. <maxnoofCells inCHO> | | |
+| >>CHO Candidate Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | |
+| >> <b>CHO Execution Condition List</b> | | 1 | | |
+| >>> <b>CHO Execution Condition Item</b> | | 1 .. <maxnoofCHO executioncond> | | |
+| >>>>MeasObject Container | M | | OCTET STRING | Includes the <i>measObjectToAddMod</i> contained in the <i>RRCReconfiguration</i> message (TS 38.331 [10]), which is configured for the CHO candidate cell |
+| >>>>ReportConfig Container | M | | OCTET STRING | Includes the <i>reportConfigToAddMod</i> contained in the <i>RRCReconfiguration</i> message (TS 38.331 [10]), which is configured for the CHO candidate cell |
+
+| Range bound | Explanation |
+|-------------------------|--------------------------------------------------------------------------------|
+| maxnoofCellsinCHO | Maximum no. cells that can be prepared for a conditional handover. Value is 8. |
+| maxnoofCHOexecutioncond | Maximum no. execution conditions for a conditional handover. Value is 2. |
+
+## 9.2.2.77 SSB Offset Information
+
+This IE represents the SSB Offset to apply to UE measurements received for the SSB Area identified by the SSB Index.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|------------------------------------------|-----------------------|
+| SSB Index | M | | INTEGER (0..63) | |
+| SSB Triggering Offset | M | | Mobility Parameters Information 9.2.2.60 | |
+
+### 9.2.2.78 SSB Offset Modification Range
+
+The *SSB Offset Modification Range* IE contains the range of *SSB Offset* values permitted by the NG-RAN node<sub>2</sub> at the moment the MOBILITY CHANGE FAILURE message is sent.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|-------------------------------------------------|-----------------------|
+| SSB Index | M | | INTEGER (0..63) | |
+| SSB Mobility Parameters Modification Range | M | | Mobility Parameters Modification Range 9.2.2.61 | |
+
+### 9.2.2.79 Multiplexing Info
+
+This IE contains information about the multiplexing capabilities between the IAB-DU's cell and the cells configured on the co-located IAB-MT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| <b>IAB-MT Cell List</b> | | 1 | | |
+| > <b>IAB-MT Cell Item</b> | | 1 ..<br><maxnoofServingCells> | | |
+| >>NR Cell Identity | M | | BIT STRING (SIZE(36)) | Cell identity of a serving cell configured for a co-located IAB-MT. |
+| >>DU_RX/MT_RX | M | | ENUMERATED (supported, not supported, supported and FDM required, ...) | An indication of whether the IAB-node supports simultaneous reception at its DU and MT side. |
+| >>DU_TX/MT_TX | M | | ENUMERATED (supported, not supported, supported and FDM required, ...) | An indication of whether the IAB-node supports simultaneous transmission at its DU and MT side. |
+| >>DU_TX/MT_RX | M | | ENUMERATED (supported, not supported, supported and FDM required, ...) | An indication of whether the IAB-node supports simultaneous transmission at its DU and reception at its MT side. |
+| >>DU_RX/MT_TX | M | | ENUMERATED (supported, not supported, supported and FDM required, ...) | An indication of whether the IAB-node supports simultaneous reception at its DU and transmission at its MT side. |
+
+| Range bound | Explanation |
+|---------------------|---------------------------------------------------------------------|
+| maxnoofServingCells | Maximum no. of serving cells for an IAB-MT. Value is 32, as defined |
+
+| | |
+|--|------------------------------------------------------|
+| | by the <i>maxNrofServingCells</i> in TS 38.331 [10]. |
+|--|------------------------------------------------------|
+
+### 9.2.2.80 Traffic Index
+
+This IE is used to identify the traffic offloaded to the topology of non-F1-terminating IAB-donor. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| Traffic Index | M | | INTEGER (1..1024,...) | |
+
+### 9.2.2.81 Traffic Profile
+
+This IE indicates the QoS parameters for F1-U traffic, or the non-UP traffic type. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>Traffic type</i> | M | | | |
+| >UP Traffic | | | | |
+| >>QoS Parameters | M | | 9.2.3.5 | |
+| >Non-UP Traffic | | | | |
+| >>Non-UP Traffic | M | | 9.2.2.100 | |
+
+### 9.2.2.82 F1-Terminating Topology BH Information
+
+This IE provides the BH information of the traffic used in F1-terminating IAB-donor's topology. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------|----------|--------------------|----------------------------|---------------------------------------------------------------------------|
+| <b>F1-terminating BH information list</b> | | 1 | | |
+| >F1-terminating BH Information item IEs | | 1..<maxnoofBHInfo> | | |
+| >>BH Info Index | M | | INTEGER (1..maxnoofBHInfo) | |
+| >>DL TNL Address | O | | IAB TNL Address 9.2.2.92 | |
+| >>DL F1 Terminating BH Info | | 0..1 | | This IE indicates the BH information for DL traffic of a descendant node. |
+| >>> Egress BAP Routing ID | M | | BAP Routing ID 9.2.2.87 | |
+| >>> Egress BH RLC CH ID | M | | BH RLC Channel ID 9.2.2.88 | |
+| >>UL F1 Terminating BH Info | | 0..1 | | This IE indicates the BH information for UL traffic of a descendant node. |
+| >>>Ingress BAP Routing ID | M | | BAP Routing ID 9.2.2.87 | |
+| >>>Ingress BH RLC CH ID | M | | BH RLC Channel ID 9.2.2.88 | |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofBHInfo | Maximum no. of BH information corresponding to one Traffic Index assigned to the traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+
+### 9.2.2.83 Non-F1-terminating Topology BH Information
+
+This IE provides the BH information of the traffic used in non-F1-terminating IAB-donor's topology. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------|----------|---------------------------------|----------------------------|-----------------------------------------------------|
+| <b>Non-F1-terminating BH Information List</b> | | 1 | | |
+| >Non-F1-terminating BH Information Item IEs | | 1..<maxnoofBHInfo> | | |
+| >> BH Info Index | M | | INTEGER (1..maxnoofBHInfo) | |
+| >>DL Non-F1 Terminating BH Info | | 0..1 | | This IE indicates the BH information for DL traffic |
+| >>>Ingress BAP Routing ID | M | | BAP Routing ID 9.2.2.87 | |
+| >>>Ingress BH RLC CH ID | M | | BH RLC Channel ID 9.2.2.88 | |
+| >>>Prior-hop BAP Address | M | | BAP Address 9.2.2.89 | |
+| >>>IAB QoS Mapping Information | O | | 9.2.2.91 | |
+| >>UL Non-F1 Terminating BH Info | | 0..1 | | This IE indicates the BH information for UL traffic |
+| >>>Egress BAP Routing ID | M | | BAP Routing ID 9.2.2.87 | |
+| >>>Egress BH RLC CH ID | M | | BH RLC Channel ID 9.2.2.88 | |
+| >>>Next-hop BAP Address | M | | BAP Address 9.2.2.89 | |
+| <b>BAP Control PDU RLC CH List</b> | | 0..1 | | |
+| >BAP Control PDU RLC CH Item IEs | | 1..<maxnoofBAPControlPDURLCCHs> | | |
+| >>BH RLC CH ID | M | | BH RLC Channel ID 9.2.2.88 | |
+| >>Next-hop BAP Address | M | | BAP Address 9.2.2.89 | |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofBHInfo | Maximum no. of BH information corresponding to one Traffic Index assigned to the traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+| maxnoofBAPControlPDURLCCHs | Maximum no. of BH RLC CHs to be used for the boundary IAB-node and its parent node in the non-F1-terminating topology. The value is 2. |
+
+### 9.2.2.84 Traffic To Be Released Information
+
+This IE is used to indicate the offloaded traffic to be released. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|--------------------------------------|--------------------------|-----------------------|
+| CHOICE <i>Traffic Release type</i> | M | | | |
+| >Full Release | | | | |
+| >>All Traffic Indication | M | | ENUMERATED<br>(true, ..) | |
+| >Partial Release | | | | |
+| >>Traffic To Be Released List | | 1 | | |
+| >>>Traffic To Be Released Item IE | | 1 ..<br><maxnoofTrafficIndexEntries> | | |
+| >>>>Traffic Index | M | | 9.2.2.80 | |
+| >>>>BH Info List | O | | 9.2.2.99 | |
+
+| Range bound | Explanation |
+|----------------------------|------------------------------------------------------------------------------------------|
+| maxnoofTrafficIndexEntries | Maximum no. of traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+
+### 9.2.2.85 IAB TNL Address Request
+
+This IE indicates the request of IP address assignment, and/or the request of IP address removal. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------|----------|---------------------|-----------------------------------------|-----------------------|
+| IAB IPv4 Addresses Requested | O | | IAB TNL Addresses Requested<br>9.2.2.93 | |
+| CHOICE <i>IAB IPv6 Request Type</i> | O | | | |
+| >IPv6 Address | | | | |
+| >>IAB IPv6 Addresses Requested | M | | IAB TNL Addresses Requested<br>9.2.2.93 | |
+| >IPv6 Prefix | | | | |
+| >>IAB IPv6 Address Prefixes Requested | M | | IAB TNL Addresses Requested<br>9.2.2.93 | |
+| IAB TNL Address To Remove List | | 0..1 | | |
+| >IAB TNL Address To Remove Item | | 1..<maxnoofTLAsIAB> | | |
+| >>IAB TNL Address | M | | 9.2.2.92 | |
+
+| Range bound | Explanation |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofTLAsIAB | Maximum total no. of IPv4 address(es), IPv6 address(es) and IPv6 address prefix(es) that can be requested in one procedure execution. The value is 1024. |
+
+### 9.2.2.86 IAB TNL Address Response
+
+This IE indicates the TNL address(es) assigned to IAB node(s).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|---------------------|-------------------------------------------|-----------------------------------------------------------------------------------|
+| <b>IAB Allocated TNL Address List</b> | | 1 | | |
+| > <b>IAB Allocated TNL Address Item</b> | | 1..<maxnoofTLAsIAB> | | |
+| >>IAB TNL Address | M | | 9.2.2.92 | |
+| >>IAB TNL Address Usage | O | | ENUMERATED (F1-C, F1-U, Non-F1, All, ...) | Indicates the usage of the allocated IPv4 or IPv6 address or IPv6 address prefix. |
+| >>Associated Donor DU Address | O | | BAP Address 9.2.2.89 | |
+
+| Range bound | Explanation |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofTLAsIAB | Maximum total no. of IPv4 address(es), IPv6 address(es) and IPv6 address prefix(es) that can be requested in one procedure execution. The value is 1024. |
+
+### 9.2.2.87 BAP Routing ID
+
+This IE indicates the BAP Routing ID. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| BAP Address | M | | 9.2.2.89 | |
+| Path ID | M | | BAP Path ID 9.2.2.90 | |
+
+### 9.2.2.88 BH RLC Channel ID
+
+This IE uniquely identifies a BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-node or IAB-donor-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| BH RLC CH ID | M | | BIT STRING (SIZE(16)) | |
+
+### 9.2.2.89 BAP Address
+
+This IE indicates the BAP address of an IAB-node or of an IAB-donor-DU, and it is part of the BAP Routing ID.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| BAP Address | M | | BIT STRING (SIZE(10)) | Corresponds to information provided in the <i>bap-Address</i> , defined in subclause 6.2.2 or subclause 6.3.2 of TS 38.331 [10], or the <i>iab-donor-DU-BAP-address</i> defined in subclause |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-------------------------|
+| | | | | 6.2.2 of TS 38.331[10]. |
+
+### 9.2.2.90 BAP Path ID
+
+This IE indicates the BAP Path ID, which is part of the BAP Routing ID. This IE is only applicable to IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------|
+| BAP Path ID | M | | BIT STRING (SIZE(10)) | Corresponds to information provided in the <i>bap-Pathid</i> defined in subclause 6.3.2 of TS 38.331 [10]. |
+
+### 9.2.2.91 IAB QoS mapping information
+
+This IE indicates the DSCP and/or IPv6 Flow Label field(s) of an IP packet of the traffic offloaded to the non-F1-terminating IAB-donor topology. This IE is only used for IAB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| DSCP | O | | BIT STRING (SIZE(6)) | |
+| Flow Label | O | | BIT STRING (SIZE(20)) | |
+
+### 9.2.2.92 IAB TNL Address
+
+This IE indicates an IPv4 or IPv6 address or an IPv6 address prefix assigned to an IAB-node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------|----------|-------|------------------------|---------------------------------------------------|
+| CHOICE <i>IAB TNL Address</i> | M | | | |
+| >IPv4 | | | | |
+| >>IPv4 Address | M | | BIT STRING (SIZE(32)) | The IPv4 address allocated to an IAB-node. |
+| >IPv6 | | | | |
+| >>IPv6 Address | M | | BIT STRING (SIZE(128)) | The IPv6 address allocated to an IAB-node. |
+| >IPv6prefix | | | | |
+| >>IPv6 Prefix | M | | BIT STRING (SIZE(64)) | The IPv6 address prefix allocated to an IAB-node. |
+
+### 9.2.2.93 IAB TNL Addresses Requested
+
+This IE indicates the number of IPv4 or IPv6 addresses or IPv6 address prefixes requested for the indicated usage.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------|
+| TNL Addresses or Prefixes Requested - All Traffic | O | | INTEGER (1..256) | The number of TNL addresses/ IPv6 prefixes requested for all traffic. |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------|
+| TNL Addresses or Prefixes Requested - F1-C traffic | O | | INTEGER (1..256) | The number of TNL addresses/IPv6 prefixes requested for F1-C traffic. |
+| TNL Addresses or Prefixes Requested - F1-U traffic | O | | INTEGER (1..256) | The number of TNL addresses/IPv6 prefixes requested for F1-U traffic. |
+| TNL Addresses or Prefixes Requested - Non-F1 traffic | O | | INTEGER (1..256) | The number of TNL addresses/IPv6 prefixes requested for non-F1 traffic. |
+
+### 9.2.2.9.4 IAB Cell Information
+
+This IE contains IAB-DU cell resource configuration, cell specific signal/channel configuration and multiplexing info of the cell of an IAB-node or IAB-donor-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------------------|----------|-------|---------------------------------------------|---------------------------------------------------------------------|
+| NR CGI | M | | 9.2.2.7 | |
+| CHOICE <i>IAB-DU Cell Resource Configuration-Mode-Info</i> | O | | | |
+| > <i>TDD</i> | | | | |
+| >>TDD Info | | 1 | | |
+| >>>gNB-DU Cell Resource Configuration-TDD | M | | gNB-DU Cell Resource Configuration 9.2.2.95 | Contains TDD resource configuration of gNB-DU's cell. |
+| >>>Frequency Info | O | | NR Frequency Info 9.2.2.19 | |
+| >>>Transmission Bandwidth | O | | NR Transmission Bandwidth 9.2.2.20 | |
+| >>>Carrier List | O | | NR Carrier List 9.2.2.63 | If included, the <i>Transmission Bandwidth</i> IE shall be ignored. |
+| > <i>FDD</i> | | | | |
+| >>FDD Info | | 1 | | |
+| >>>gNB-DU Cell Resource Configuration-FDD-UL | M | | gNB-DU Cell Resource Configuration 9.2.2.95 | Contains FDD UL resource configuration of gNB-DU's cell. |
+| >>>gNB-DU Cell Resource Configuration-FDD-DL | M | | gNB-DU Cell Resource Configuration 9.2.2.95 | Contains FDD DL resource configuration of gNB-DU's cell. |
+| >>>UL Frequency Info | O | | NR Frequency Info 9.2.2.19 | |
+| >>>DL Frequency Info | O | | NR Frequency Info 9.2.2.19 | |
+| >>>UL Transmission Bandwidth | O | | NR Transmission Bandwidth 9.2.2.20 | |
+| >>>DL Transmission Bandwidth | O | | NR Transmission Bandwidth 9.2.2.20 | |
+| >>>UL Carrier List | O | | NR Carrier List | If included, the <i>UL Transmission</i> |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|-----------------------------|------------------------------------------------------------------------------------------------------------|
+| | | | 9.2.2.63 | <i>Bandwidth</i> IE shall be ignored. |
+| >>>DL Carrier List | O | | NR Carrier List<br>9.2.2.63 | If included, the <i>DL Transmission Bandwidth</i> IE shall be ignored. |
+| IAB STC Info | O | | 9.2.2.96 | STC configuration of this gNB-DU's cell. |
+| RACH Config Common | O | | OCTET STRING | Includes the <i>rach-ConfigCommon</i> as defined in subclause 6.3.2 of TS 38.331 [10]. |
+| RACH Config Common IAB | O | | OCTET STRING | Includes the IAB-specific <i>rach-ConfigCommonIAB-r16</i> as defined in subclause 6.3.2 of TS 38.331 [10]. |
+| CSI-RS Configuration | O | | OCTET STRING | Includes the <i>NZP-CSI-RS-Resource</i> IE as defined in subclause 6.3.2 of TS 38.331 [10]. |
+| SR Configuration | O | | OCTET STRING | Includes the <i>SchedulingRequestResourceConfig</i> IE as defined in subclause 6.3.2 of TS 38.331 [10]. |
+| PDCCH Configuration SIB1 | O | | OCTET STRING | Includes the <i>PDCCH-ConfigSIB1</i> IE as defined in subclause 6.3.2 of TS 38.331 [10]. |
+| SCS Common | O | | OCTET STRING | Includes the <i>subCarrierSpacingCommon</i> as defined in subclause 6.2.2 of TS 38.331 [10]. |
+| Multiplexing Info | O | | 9.2.2.79 | Contains information on multiplexing with cells configured for collocated IAB-MT, if applicable. |
+
+| Range bound | Explanation |
+|-----------------------|-------------------------------------------------------------------------------|
+| maxnoofServedCellsIAB | Maximum number of cells served by an IAB-DU or an IAB-donor-DU. Value is 512. |
+
+## 9.2.2.95 gNB-DU Cell Resource Configuration
+
+This IE contains the resource configuration of the cells served by a gNB-DU, i.e. the TDD/FDD resource parameters for each activated cell (TS 38.213 [40], clause 11.1.1). This IE is only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------|----------|-------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------|
+| Subcarrier Spacing | M | | ENUMERATED<br>(kHz15, kHz30, kHz60, kHz120, kHz240, spare3, spare2, spare1, ...) | Subcarrier spacing used as reference for the TDD/FDD slot configuration. |
+| DU Transmission Periodicity | O | | ENUMERATED<br>(ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ...) | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------------|----------|-------------------------------|--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | ...) | |
+| <b>DUF Slot Configuration List</b> | | 0..1 | | |
+| > <b>DUF Slot Configuration Item</b> | | 1..<maxnoofD<br>UFSlots> | | |
+| >>CHOICE <i>DUF Slot Configuration</i> | M | | | |
+| >>> <i>Explicit Format</i> | | | | |
+| >>>>Permutation | M | | ENUMERATED<br>(DFU, UFD, ...) | |
+| >>>>Number of Downlink Symbols | O | | INTEGER (0..14) | |
+| >>>>Number of Uplink Symbols | O | | INTEGER (0..14) | |
+| >>> <i>Implicit Format</i> | | | | |
+| >>>>DUF Slot Format Index | M | | INTEGER (0..254) | Index into Table 11.1.1-1 and Table 14-2 in TS 38.213 [40], excluding the last row in Table 14-2. |
+| HSNA Transmission Periodicity | M | | ENUMERATED<br>(ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160, ...) | |
+| <b>HSNA Slot Configuration List</b> | | 0..1 | | |
+| > <b>HSNA Slot Configuration Item</b> | | 1..<maxnoofH<br>SNASlots> | | |
+| >>HSNA Downlink | O | | ENUMERATED<br>(HARD, SOFT, NOTAVAILABLE) | HSNA value for downlink symbols in a slot. |
+| >>HSNA Uplink | O | | ENUMERATED<br>(HARD, SOFT, NOTAVAILABLE) | HSNA value for uplink symbols in a slot. |
+| >>HSNA Flexible | O | | ENUMERATED<br>(HARD, SOFT, NOTAVAILABLE) | HSNA value for flexible symbols in a slot. |
+| RB Set Configuration | O | | 9.2.2.97 | Indicates the configuration for up to M non-overlapping RB sets for a given DU cell, used for frequency domain resource allocation. The maximum value of M is 8. |
+| <b>Frequency-domain HSNA Configuration List</b> | | 0..1 | | |
+| > <b>Frequency-domain HSNA Configuration Item</b> | | 1..<maxnoofR<br>BsetsPerCell> | | |
+| >>RB Set Index | M | | INTEGER (0..<br>maxnoofRBsetsPer<br>Cell1, ...) | Refers to an RB set defined by RB Set Configuration. The RB set indexes are consecutive (and increasing) starting at 0. |
+| >>Frequency-domain HSNA Slot Configuration List | | 1 | | |
+| >>>Frequency- | | 1..<maxnoofH | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|------------------------------------|------------------------------------------|------------------------------------------------------------------------------------------------|
+| <b>domain HSNA Slot Configuration item</b> | | <i>SNASlots></i> | | |
+| >>>>Slot Index | M | | INTEGER (..<br><i>maxnoofHSNASlots</i> ) | Index to a slot within the HSNA Transmission Periodicity. * |
+| >>>>HSNA Downlink | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for downlink symbols in a slot, for an RB set. |
+| >>>>HSNA Uplink | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for uplink symbols in a slot, for an RB set. |
+| >>>>HSNA Flexible | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for flexible symbols in a slot, for an RB set. |
+| <b>NA cell resource configuration List</b> | | <i>0..1</i> | | List of unavailable resources of this cell for the dual-connected boundary IAB-node. |
+| >NA cell resource configuration Item | | <i>1..<maxnoofHSNASlots></i> | | |
+| >>NA Downlink | O | | ENUMERATED (true, false, ...) | Indicates whether downlink symbols, in a slot, are unavailable to serve the boundary IAB-node. |
+| >>NA Uplink | O | | ENUMERATED (true, false, ...) | Indicates whether uplink symbols, in a slot, are unavailable to serve the boundary IAB-node. |
+| >>NA Flexible | O | | ENUMERATED (true, false, ...) | Indicates whether flexible symbols, in a slot, are unavailable to serve the boundary IAB-node. |
+
+| Range bound | Explanation |
+|------------------------------|---------------------------------------------------------------------------------------------------------------|
+| <i>maxnoofDUFSlots</i> | Maximum no. of slots in 10ms. Value is 320. Corresponds to the <i>maxNrofSlots</i> defined in TS 38.331 [10]. |
+| <i>maxnoofSymbols</i> | Maximum no. of symbols in a slot. Value is 14. |
+| <i>maxnoofHSNASlots</i> | Maximum no of "Hard", "Soft" or "Not available" slots in 160ms. Value is 5120. |
+| <i>maxnoofRBsetsPerCell</i> | Maximum no. of RB sets per DU cell. Value is 8. |
+| <i>maxnoofChildIABNodes</i> | Maximum number of child nodes served by an IAB-DU or IAB-donor-DU. Value is 1024. |
+| <i>maxnoofRBsetsPerCell1</i> | Maximum no. of RB sets per DU cell minus 1. Value is 7. |
+
+## 9.2.2.96 IAB STC Info
+
+This IE contains cell SSB Transmission Configuration (STC) information of an IAB-DU or an IAB-donor-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|--------------------------------------|-------------------------------------|----------------------------|
+| <b>IAB STC-Info List</b> | | <i>1</i> | | |
+| >IAB STC-Info Item | | <i>1 ..<maxnoofIABSTCInfo></i> | | |
+| >>SSB Frequency Info | M | | INTEGER (0..<br><i>maxNRARFCN</i> ) | The SSB central frequency. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|-------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|
+| >>SSB Subcarrier Spacing | M | | ENUMERATED (kHz15, kHz30, kHz120, kHz240, spare3, spare2, spare1, ...) | The SSB subcarrier spacing. |
+| >>SSB Transmission Periodicity | M | | ENUMERATED (sf5, sf10, sf20, sf40, sf80, sf160, sf320, sf640, ...) | |
+| >>SSB Transmission Timing Offset | M | | INTEGER (0.. 127, ...) | SSB transmission timing offset in number of half-frames. |
+| >>CHOICE SSB Transmission Bitmap | M | | | Corresponds to information provided in the <i>SSB-ToMeasure</i> IE defined in TS 38.331 [10]. |
+| >>>short bitmap | | | | |
+| >>>>Short Bitmap | M | | BIT STRING (SIZE (4)) | |
+| >>>medium bitmap | | | | |
+| >>>>Medium Bitmap | M | | BIT STRING (SIZE (8)) | |
+| >>>long bitmap | | | | |
+| >>>>Long Bitmap | M | | BIT STRING (SIZE (64)) | |
+
+| Range bound | Explanation |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofIABSTCInfo | Maximum no. of STC configurations. Value is 5. This includes 1 STC configuration for access and 4 STC configurations for backhaul. |
+| maxNRARFCN | Maximum value of NR ARFCNs. Value is 3279165. |
+
+## 9.2.2.97 RB Set Configuration
+
+This IE contains the configuration for up to M non-overlapping RB sets for a given gNB-DU cell, used for frequency domain resource allocation. This IE is only applicable if the gNB-DU is an IAB-DU. The maximum value of M is 8.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------|----------|-------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Subcarrier Spacing | M | | ENUMERATED (kHz15, kHz30, kHz60, kHz120, kHz240, spare3, spare2, spare1, ...) | Subcarrier spacing used as reference for the RB set configuration. |
+| RB Set Size | M | | ENUMERATED (rb2, rb4, rb8, rb16, rb32, rb64) | Number of PRBs in each RB set. If the RB sets of IAB-DU H/S/NA resource configuration do not cover the entire carrier bandwidth, the remaining RBs not part of an RB set configuration are considered as |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------|----------|-------|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Number of RB Sets | M | | INTEGER(1..<br><i>maxnoofRBsetsPerCell</i> ) | included in the last RB set.<br>Number of configured RB sets. The RB sets are contiguous and non-overlapping. If the <i>NR Carrier List</i> IE(9.2.2.63) is provided, the start RB index of the first RB set is the RB index of the lowest common RB with the SCS provided by <i>RB Set Configuration</i> IE, which overlaps with the lowest usable RB across all SCS-specific carriers provided by the <i>NR Carrier List</i> IE for the IAB-DU cell. Otherwise, the lowest subcarrier of the start RB of the first RB set is aligned with point A for the IAB-DU cell. |
+
+| Range bound | Explanation |
+|-----------------------------|-----------------------------------------------------|
+| <i>maxnoofRBsetsPerCell</i> | Maximum no. of RB sets per IAB-DU cell. Value is 8. |
+
+### 9.2.2.98 IAB TNL Address Exception
+
+This IE indicates the list of source TNL addresses carried on UL IP packets in an IAB network, which can be forwarded over the inter-IAB-donor-DU tunnel, and that are exempt from TNL address filtering, for the purpose of inter-donor-DU rerouting.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|---------------------------------|-----------------------|-----------------------|
+| <b>IAB TNL Address List</b> | | 1 | | |
+| > <b>IAB TNL Address Item IEs</b> | | 1..<<br><i>maxnoofTLAsIAB</i> > | | |
+| >>IAB TNL Address | M | | 9.2.2.92 | |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <i>maxnoofTLAsIAB</i> | Maximum total no. of IPv4 address(es), IPv6 address(es) and IPv6 address prefix(es) that can be requested in one procedure execution. The value is 1024. |
+
+### 9.2.2.99 BH Info List
+
+This IE indicates a list of BH information indices, where each index represents the offloaded traffic pertaining to, e.g., a certain BAP routing ID, BH RLC CH.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|--------------------------------|----------------------------------------|-----------------------|
+| <b>BH Info List</b> | | 1 | | |
+| > <b>BH Info Item IEs</b> | | 1..<<br><i>maxnoofBHInfo</i> > | | |
+| >>BH Info Index | M | | INTEGER (1..<br><i>maxnoofBHInfo</i> ) | |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofBHInfo | Maximum no. of BH information corresponding to one Traffic Index assigned to the traffic offloaded to the non-F1-terminating IAB-donor. The value is 1024. |
+
+### 9.2.2.100 Non-UP traffic
+
+This IE indicates the type of non-UP traffic.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|-------|---------------------------------------------------------------------|--------------------------------------------------------------------------------------|
+| CHOICE <i>non-UP Traffic</i> | | | | |
+| > <i>non-UP Traffic Type</i> | | | | |
+| >>Non-UP Traffic Type | M | | ENUMERATED(UE-associated F1AP, non-UE-associated F1AP, non-F1, ...) | |
+| > <i>control Plane Traffic Type</i> | | | | |
+| >>Control Plane Traffic Type | M | | INTEGER (1..3, ...) | Identified by the different codepoints in this IE, where 1 has the highest priority. |
+
+### 9.2.2.101 Local NG-RAN Node Identifier
+
+This IE is used to resolve a Global NG-RAN Node ID from an I-RNTI and obtain a reference to an UE context at RRC Resume.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| CHOICE <i>Local NG-RAN Node Identifier</i> | M | | | | – | |
+| > <i>Full I-RNTI profile</i> | | | | | | |
+| >>CHOICE <i>Full I-RNTI Profile</i> | M | | | | – | |
+| >>> <i>Full I-RNTI profile 0</i> | | | | | | |
+| >>>> Local NG-RAN Node Identifier Full I-RNTI profile 0 | M | | BIT STRING (SIZE(21)) | | – | |
+| >>> <i>Full I-RNTI profile 1</i> | | | | | | |
+| >>>>Local NG-RAN Node Identifier Full I-RNTI profile 1 | M | | BIT STRING (SIZE(18)) | | – | |
+| >>> <i>Full I-RNTI profile 2</i> | | | | | | |
+| >>>>Local NG-RAN Node Identifier Full I-RNTI profile 2 | M | | BIT STRING (SIZE(15)) | | – | |
+| >>> <i>Full I-RNTI profile 3</i> | | | | | | |
+| >>>>Local NG-RAN Node Identifier Full I- | M | | BIT STRING (SIZE(12)) | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| RNTI profile 3 | | | | | | |
+| > <i>Short I-RNTI Profile</i> | | | | | | |
+| >>CHOICE <i>Short I-RNTI profile</i> | M | | | | – | |
+| >>> <i>Short I-RNTI profile 0</i> | | | | | | |
+| >>>>Local NG-RAN Node Identifier Short I-RNTI profile 0 | M | | BIT STRING (SIZE(8)) | | – | |
+| >>> <i>Short I-RNTI profile 1</i> | | | | | | |
+| >>>>Local NG-RAN Node Identifier Short I-RNTI profile 1 | M | | BIT STRING (SIZE(6)) | | – | |
+| > <i>Full and Short I-RNTI profiles</i> | | | | | YES | ignore |
+| >>Full I-RNTI profile | M | | | | – | |
+| >>>CHOICE <i>Full I-RNTI Profile</i> | M | | | | – | |
+| >>>> <i>Full I-RNTI profile 0</i> | | | | | | |
+| >>>>>Local NG-RAN Node Identifier Full I-RNTI profile 0 | M | | BIT STRING (SIZE(21)) | | – | |
+| >>>> <i>Full I-RNTI profile 1</i> | | | | | | |
+| >>>>>Local NG-RAN Node Identifier Full I-RNTI profile 1 | M | | BIT STRING (SIZE(18)) | | – | |
+| >>>> <i>Full I-RNTI profile 2</i> | | | | | | |
+| >>>>>Local NG-RAN Node Identifier Full I-RNTI profile 2 | M | | BIT STRING (SIZE(15)) | | – | |
+| >>>> <i>Full I-RNTI profile 3</i> | | | | | | |
+| >>>>>Local NG-RAN Node Identifier Full I-RNTI profile 3 | M | | BIT STRING (SIZE(12)) | | – | |
+| >>Short I-RNTI Profile | M | | | | | |
+| >>>CHOICE <i>Short I-RNTI profile</i> | M | | | | – | |
+| >>>> <i>Short I-RNTI profile 0</i> | | | | | | |
+| >>>>>Local NG-RAN Node Identifier Short I-RNTI profile 0 | M | | BIT STRING (SIZE(8)) | | – | |
+| >>>> <i>Short I-RNTI profile 1</i> | | | | | | |
+| >>>>>Local NG-RAN Node Identifier Short I-RNTI profile 1 | M | | BIT STRING (SIZE(6)) | | – | |
+
+### 9.2.2.102 Served Cell Specific Info Request
+
+The *Served Cell Specific Info Request* IE is used by the NG-RAN node to request specific information about NR cells.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------------------------------------------|----------|----------------------------------|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>List of Requested NR Cells</b> | | 1 | | List of NR cells. |
+| > <b>List of Requested NR Cells item</b> | | 1 .. <maxnoofCellsinNG-RAN node> | | |
+| >>NR CGI | M | | 9.2.2.7 | NR cell for which specific served NR cell information is requested. |
+| >>Additional Measurement Timing Configuration List Request Indicator | O | | ENUMERATED (AdditionalMTCListequested, ...) | Included when the NG-RAN node requests the <i>Additional Measurement Timing Configuration List</i> IE to be included in the <i>Served Cell Information NR</i> IE for the requested cells. |
+
+| Range bound | Explanation |
+|---------------------------|------------------------------------------------------------------------|
+| maxnoofCellsinNG-RAN node | Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
+
+### 9.2.2.103 CPAC Configuration
+
+This IE contains the CPC or CPA configuration information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|---------------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>CPAC Candidate Cell List</b> | | 1 | | |
+| > <b>CPAC Candidate Cell Item</b> | | 1 .. <maxnoofPSCells inCPAC> | | |
+| >>CPAC Candidate Cell ID | M | | Global NG-RAN Cell Identity 9.2.2.27 | |
+| >> <b>CPAC Execution Condition List</b> | | 1 | | |
+| >>> <b>CPAC Execution Condition Item</b> | | 1 .. <maxnoofCPACexecutioncond> | | |
+| >>>>MeasObject Container | M | | OCTET STRING | Includes the <i>MeasObjectToAddMod</i> IE contained in the <i>RRCReconfiguration</i> message as specified in TS 38.331 [10], which is configured for the CPAC candidate cell |
+| >>>>ReportConfig Container | M | | OCTET STRING | Includes the <i>ReportConfigToAddMod</i> IE contained in the <i>RRCReconfiguration</i> message as specified in TS 38.331 [10], which is configured for the CPAC candidate cell |
+
+| Range bound | Explanation |
+|--------------------------|--------------------------------------------------------------------------|
+| maxnoofPSCellsinCPAC | Maximum no. cells that can be prepared for a CPAC handover. Value is 8. |
+| maxnoofCPACexecutioncond | Maximum no. execution conditions for a conditional handover. Value is 2. |
+
+### 9.2.2.104 Radio Resource Status NR-U
+
+The *Radio Resource Status NR-U* IE indicates the usage of the PRBs per NR-U Channel for all traffic in Downlink and Uplink.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------|
+| DL Total PRB Usage | M | | INTEGER (0..100) | Per NR-U Channel DL Total PRB usage in percentage of the cell total PRB number. |
+| UL Total PRB Usage | M | | INTEGER (0..100) | Per NR-U Channel UL Total PRB usage in percentage of the cell total PRB number. |
+
+### 9.2.2.105 Mobile IAB Authorization Status
+
+This IE indicates the authorization status of the mobile IAB node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-------|----------------------------------------------|-----------------------|
+| Mobile IAB Authorization Status | M | | ENUMERATED (authorized, not authorized, ...) | |
+
+### 9.2.2.106 Mobile IAB Cell
+
+This IE indicates that the cell is served by a mobile IAB-node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|------------------------|-----------------------|
+| Mobile IAB Cell | M | | ENUMERATED (true, ...) | |
+
+## 9.2.3 General IE definitions
+
+### 9.2.3.1 Message Type
+
+The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|-----------------------------------------------------------------------|-----------------------|
+| Procedure Code | M | | INTEGER (0..255) | |
+| Type of Message | M | | CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome) | |
+
+| | | | | |
+|--|--|--|-------------|--|
+| | | | me,<br>...) | |
+|--|--|--|-------------|--|
+
+### 9.2.3.2 Cause
+
+The purpose of the *Cause* IE is to indicate the reason for a particular event for the XnAP protocol.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| CHOICE <i>Cause Group</i> | M | | | |
+| > <i>Radio Network Layer</i> | | | | |
+| >>Radio Network Layer<br>Cause | M | | ENUMERATED<br>(<br>Cell not Available,<br>Handover Desirable<br>for Radio Reasons,<br>Handover Target not<br>Allowed,<br>Invalid AMF Set ID,<br>No Radio<br>Resources Available<br>in Target Cell,<br>Partial Handover,<br>Reduce Load in<br>Serving Cell,<br>Resource<br>Optimisation<br>Handover,<br>Time Critical<br>Handover,<br>TXn <sub>RELOCoverall</sub> Expiry,<br>TXn <sub>RELOCprep</sub> Expiry,<br>Unknown GUAMI<br>ID,<br>Unknown Local NG-<br>RAN node UE XnAP<br>ID,<br>Inconsistent Remote<br>NG-RAN node UE<br>XnAP ID,<br>Encryption And/Or<br>Integrity Protection<br>Algorithms Not<br>Supported,<br>Multiple PDU<br>Session ID<br>Instances,<br>Unknown PDU<br>Session ID,<br>Unknown QoS Flow<br>ID,<br>Multiple QoS Flow<br>ID Instances,<br>Switch Off Ongoing,<br>Not supported 5QI<br>value,<br>TXn <sub>DCoverall</sub> Expiry,<br>TXn <sub>DCprep</sub> Expiry, | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| | | | Action Desirable for Radio Reasons,<br>Reduce Load,<br>Resource Optimisation,<br>Time Critical action,<br>Target not Allowed,<br>No Radio Resources Available,<br>Invalid QoS combination,<br>Encryption Algorithms Not Supported,<br>Procedure cancelled,<br>RRM purpose,<br>Improve User Bit Rate,<br>User Inactivity,<br>Radio Connection With UE Lost,<br>Failure in the Radio Interface Procedure,<br>Bearer Option not Supported,<br>UP integrity protection not possible,<br>UP confidentiality protection not possible,<br>Resources not available for the slice(s),<br>UE Maximum integrity protected data rate reason,<br>CP Integrity Protection Failure,<br>UP Integrity Protection Failure,<br>Slice(s) not supported by NG-RAN,<br>MN Mobility,<br>SN Mobility,<br>Count reaches max value,<br>Unknown Old NG-RAN node UE XnAP ID,<br>PDCP Overload,<br>DRB ID not available,<br>Unspecified, | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| | | | ...,<br>UE Context ID not known, Non-relocation of context, CHO-CPC resources to be changed, RSN not available for the UP, NPN access denied, Report Characteristics Empty, Existing Measurement ID, Measurement Temporarily not Available, Measurement not Supported For The Object, UE Power Saving, Not existing NG-RAN node <sub>2</sub> Measurement ID, Insufficient UE Capabilities, Normal Release, Value out of allowed range, SCG activation deactivation failure, SCG deactivation failure due to data transmission, SSB not Available, LTM Triggered) | |
+| >Transport Layer | | | | |
+| >>Transport Layer Cause | M | | ENUMERATED (Transport Resource Unavailable, Unspecified, ...) | |
+| >Protocol | | | | |
+| >>Protocol Cause | M | | ENUMERATED (Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Abstract Syntax | |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| | | | Error (Falsely Constructed Message), Unspecified, ...) | |
+| >Misc | | | | |
+| >>Miscellaneous Cause | M | | ENUMERATED (Control Processing Overload, Hardware Failure, O&M Intervention, Not enough User Plane Processing Resources, Unspecified, ...) | |
+
+The meaning of the different cause values is specified in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action.
+
+| Radio Network Layer cause | Meaning |
+|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Cell not Available | The concerned cell is not available. |
+| Handover Desirable for Radio Reasons | The reason for requesting handover is radio related. |
+| Handover Target not Allowed | Handover to the indicated target cell is not allowed for the UE in question. |
+| Invalid AMF Set ID | The target NG-RAN node doesn't belong to the same AMF Set of the source NG-RAN node, i.e. NG handovers should be attempted instead. |
+| No Radio Resources Available in Target Cell | The target cell doesn't have sufficient radio resources available. |
+| Partial Handover | Provides a reason for the handover cancellation. The target NG-RAN node did not admit all PDU Sessions included in the HANDOVER REQUEST and the source NG-RAN node estimated service continuity for the UE would be better by not proceeding with handover towards this particular target NG-RAN node. |
+| Reduce Load in Serving Cell | Load in serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to load balancing. |
+| Resource Optimisation Handover | The reason for requesting handover is to improve the load distribution with the neighbour cells. |
+| Value out of allowed range | The action failed because the proposed Handover Trigger parameter change in the NG-RAN node <sub>2</sub> Proposed Mobility Parameters IE is too low or too high. |
+| Time Critical Handover | Handover is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection is likely to be dropped if handover is not performed. |
+| TXn <sub>RELOCoverall</sub> Expiry | The reason for the action is expiry of timer TXn <sub>RELOCoverall</sub> . |
+| TXn <sub>RELOCprep</sub> Expiry | Handover Preparation procedure is cancelled when timer TXn <sub>RELOCprep</sub> expires. |
+| Unknown GUAMI ID | The target NG-RAN node belongs to the same AMF Set of the source NG-RAN node and recognizes the AMF Set ID. However, the GUAMI value is unknown to the target NG-RAN node. |
+| Unknown Local NG-RAN node UE XnAP ID | The action failed because the receiving NG-RAN node does not recognise the local NG-RAN node UE XnAP ID. |
+
+| Radio Network Layer cause | Meaning |
+|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Inconsistent Remote NG-RAN node UE XnAP ID | The action failed because the receiving NG-RAN node considers that the received remote NG-RAN node UE XnAP ID is inconsistent.. |
+| Encryption And/Or Integrity Protection Algorithms Not Supported | The target NG-RAN node is unable to support any of the encryption and/or integrity protection algorithms supported by the UE. |
+| Multiple PDU Session ID Instances | The action failed because multiple instances of the same PDU Session had been provided to the NG-RAN node. |
+| Unknown PDU Session ID | The action failed because the PDU Session ID is unknown in the NG-RAN node. |
+| Unknown QoS Flow ID | The action failed because the QoS Flow ID is unknown in the NG-RAN node. |
+| Multiple QoS Flow ID Instances | The action failed because multiple instances of the same QoS flow had been provided to the NG-RAN node. |
+| Switch Off Ongoing | The reason for the action is an ongoing switch off i.e. the concerned cell will be switched off after offloading and not be available. It aides the receiving NG-RAN node in taking subsequent actions, e.g. selecting the target cell for subsequent handovers. |
+| Not supported 5QI value | The action failed because the requested 5QI is not supported. |
+| TXn <sub>DCoverall</sub> Expiry | The reason for the action is expiry of timer TXn <sub>DCoverall</sub> . |
+| TXn <sub>DCprep</sub> Expiry | The reason for the action is expiry of timer TXn <sub>DCprep</sub> . |
+| Action Desirable for Radio Reasons | The reason for requesting the action is radio related.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Reduce Load | Load in the cell(group) served by the requesting node needs to be reduced.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Resource Optimisation | The reason for requesting this action is to improve the load distribution with the neighbour cells.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Time Critical action | The action is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where radio resources are likely to be dropped if the requested action is not performed.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Target not Allowed | Requested action towards the indicated target cell is not allowed for the UE in question.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| No Radio Resources Available | The cell(s) in the requested node don't have sufficient radio resources available.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Invalid QoS combination | The action was failed because of invalid QoS combination.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Encryption Algorithms Not Supported | The requested NG-RAN node is unable to support any of the encryption algorithms supported by the UE.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Procedure cancelled | The sending node cancelled the procedure due to other urgent actions to be performed.<br>In the current version of this specification applicable for Dual Connectivity only. |
+
+| <b>Radio Network Layer cause</b> | <b>Meaning</b> |
+|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| RRM purpose | The procedure is initiated due to node internal RRM purposes.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Improve User Bit Rate | The reason for requesting this action is to improve the user bit rate.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| User Inactivity | The action is requested due to user inactivity on all PDU Sessions. The action may be performed on several levels: <ul style="list-style-type: none"> <li>- on UE Context level, if NG is requested to be released in order to optimise the radio resources; or S-NG-RAN node didn't see activity on the PDU session recently.</li> <li>- on PDU Session Resource or DRB or QoS flow level, e.g. if Activity Notification indicate lack of activity</li> </ul> In the current version of this specification applicable for Dual Connectivity only. |
+| Radio Connection With UE Lost | The action is requested due to losing the radio connection to the UE.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Failure in the Radio Interface Procedure | Radio interface procedure has failed.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| Bearer Option not Supported | The requested bearer option is not supported by the sending node.<br>In the current version of this specification applicable for Dual Connectivity only. |
+| UP integrity protection not possible | The PDU session cannot be accepted according to the required user plane integrity protection policy. |
+| UP confidentiality protection not possible | The PDU session cannot be accepted according to the required user plane confidentiality protection policy. |
+| Resources not available for the slice(s) | The requested resources are not available for the slice(s). |
+| UE Maximum integrity protected data rate reason | The request is not accepted in order to comply with the maximum data rate for integrity protection supported by the UE. |
+| CP Integrity Protection Failure | The request is not accepted due to failed control plane integrity protection. |
+| UP Integrity Protection Failure | The procedure is initiated because the SN (hosting node) detected an Integrity Protection failure in the UL PDU coming from the MN. |
+| Slice(s) not supported by NG-RAN | The failure is due to slice(s) not supported by the NG-RAN node. |
+| MN Mobility | The procedure is initiated due to relocation of the M-NG-RAN node UE context. |
+| SN Mobility | The procedure is initiated due to relocation of the S-NG-RAN node UE context. |
+| Count reaches max value, | Indicates the PDCP COUNT for UL or DL reached the max value and the bearer may be released. |
+| Unknown Old NG-RAN node UE XnAP ID | The action failed because the Old NG-RAN node UE XnAP ID or the S-NG-RAN node UE XnAP ID is unknown. |
+| PDCP Overload | The procedure is initiated due to PDCP resource limitation. |
+| DRB ID not available | The action failed because the M-NG-RAN node is not able to provide additional DRB IDs to the S-NG-RAN node. |
+| Unspecified | Sent for radio network layer cause when none of the specified cause values applies. |
+| UE Context ID not known | The context retrieval procedure cannot be performed because the UE context cannot be identified. |
+
+| <b>Radio Network Layer cause</b> | <b>Meaning</b> |
+|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Non-relocation of context | The context retrieval procedure is not performed because the old RAN node has decided not to relocate the UE context. |
+| CHO-CPC resources to be changed | The prepared resources for CHO or CPC for a UE are to be changed. |
+| RSN not available for the UP | The redundant user plane resources are not available. |
+| NPN Access denied | Access denied, or release is required, due to NPN reasons. |
+| Report Characteristics Empty | The action failed because there is no measurement object in the report characteristics. |
+| Existing Measurement ID | The action failed because the measurement ID is already used. |
+| Measurement Temporarily not Available | The NG-RAN node can temporarily not provide the requested measurement object. |
+| Measurement not Supported For The Object | At least one of the concerned object(s) does not support the requested measurement. |
+| UE Power Saving | The procedure is initiated to accommodate the preference indicated by UE to release the S-NG-RAN node for UE power saving purpose. |
+| Not existing NG-RAN node <sub>2</sub> Measurement ID | The action failed because the NG-RAN node <sub>2</sub> Measurement ID is not used. |
+| Insufficient UE Capabilities | The procedure can't proceed due to insufficient UE capabilities. |
+| Normal Release | The release is due to normal reasons. |
+| SCG activation deactivation failure | The action failed due to rejection of the SCG activation deactivation request. |
+| SCG deactivation failure due to data transmission | The SCG deactivation failure due to ongoing or arriving data transmission. |
+| SSB not Available | The concerned SSB is not available. |
+| LTM Triggered | The release is due to that LTM is triggered in M-NG-RAN node. |
+
+| <b>Transport Layer cause</b> | <b>Meaning</b> |
+|--------------------------------|----------------------------------------------------------------------------------------------------------|
+| Transport resource unavailable | The required transport resources are not available. |
+| Unspecified | Sent when none of the above cause values applies but still the cause is Transport Network Layer related. |
+
+| <b>Protocol cause</b> | <b>Meaning</b> |
+|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| Transfer Syntax Error | The received message included a transfer syntax error. |
+| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerning criticality indicated "reject". |
+| Abstract Syntax Error (Ignore And Notify) | The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". |
+| Message Not Compatible With Receiver State | The received message was not compatible with the receiver state. |
+| Semantic Error | The received message included a semantic error. |
+| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences. |
+| Unspecified | Sent when none of the above cause values applies but still the cause is Protocol related. |
+
+| <b>Miscellaneous cause</b> | <b>Meaning</b> |
+|--------------------------------------------|-------------------------------------------------------------------------|
+| Control Processing Overload | NG-RAN node control processing overload. |
+| Hardware Failure | NG-RAN node hardware failure. |
+| Not enough User Plane Processing Resources | NG-RAN node has insufficient user plane processing resources available. |
+| O&M Intervention | Operation and Maintenance intervention related to NG-RAN |
+
+| Miscellaneous cause | Meaning |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | node equipment. |
+| Unspecified | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol. |
+
+### 9.2.3.3 Criticality Diagnostics
+
+The *Criticality Diagnostics* IE is sent by the NG-RAN node when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------|----------|--------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error. |
+| Triggering Message | O | | ENUMERATED (initiating message, successful outcome, unsuccessful outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. |
+| Procedure Criticality | O | | ENUMERATED (reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). |
+| <b>Information Element Criticality Diagnostics</b> | | 0.. <i>maxNrOfErrors</i> | | |
+| >IE Criticality | M | | ENUMERATED (reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value "ignore" is not applicable. |
+| >IE ID | M | | INTEGER (0..65535) | The IE ID of the not understood or missing IE |
+| >Type Of Error | M | | ENUMERATED(not understood, missing, ...) | |
+
+| Range bound | Explanation |
+|---------------|------------------------------------------------------------------------------------------|
+| maxNrOfErrors | Maximum no. of IE errors allowed to be reported with a single message. The Value is 256. |
+
+### 9.2.3.4 Bit Rate
+
+This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN in DL or by the UE in sidelink within a period of time, divided by the duration of the period. It is used, for example, to indicate the maximum or guaranteed bit rate for a GBR QoS flow, or an aggregate maximum bit rate.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------------------|-----------------------|
+| Bit Rate | M | | INTEGER (0..4,000,000,000,000,...) | The unit is: bit/s |
+
+### 9.2.3.5 QoS Flow Level QoS Parameters
+
+This IE defines the QoS Parameters to be applied to a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| CHOICE QoS Characteristics | M | | | | – | |
+| >Non Dynamic 5QI | | | | | | |
+| >>Non dynamic 5QI Descriptor | M | | 9.2.3.8 | | – | |
+| >Dynamic 5QI | | | | | | |
+| >>Dynamic 5QI Descriptor | M | | 9.2.3.9 | | – | |
+| Allocation and Retention Priority | M | | 9.2.3.7 | | – | |
+| GBR QoS Flow Information | O | | 9.2.3.6 | This IE shall be present for GBR QoS flows and is ignored otherwise. | – | |
+| Reflective QoS Attribute | O | | ENUMERATED (subject to, ...) | Reflective QoS is specified in TS 23.501 [7]. This IE applies to Non-GBR bearers only and is ignored otherwise. | – | |
+| Additional QoS flow Information | O | | ENUMERATED (more likely, ...) | If this IE is set to "more likely", this indicates that traffic for this QoS flow is likely to appear more often than traffic for other flows established for the PDU session. This IE may be present in case of Non-GBR flows only and is ignored otherwise. | – | |
+| QoS Monitoring Request | O | | ENUMERATED (UL, DL, Both, ...) | Indicates to measure UL, or DL, or both UL/DL delays for the associated QoS flow. | YES | ignore |
+| QoS Monitoring Reporting Frequency | O | | INTEGER (1..1800, ...) | Indicates the Reporting Frequency for RAN part delay for QoS monitoring. Unit: second | YES | ignore |
+| QoS Monitoring Disabled | O | | ENUMERATED (true, ...) | Indicates to stop the QoS monitoring. | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------|----------|-------|-----------------------|---------------------------------------|-------------|----------------------|
+| PDU Set QoS Parameters | O | | 9.2.3.203 | Indicates the PDU Set QoS Parameters. | YES | ignore |
+
+### 9.2.3.6 GBR QoS Flow Information
+
+This IE indicates QoS Parameters for a GBR QoS Flow for downlink and uplink.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Maximum Flow Bit Rate Downlink | M | | Bit Rate 9.2.3.4 | Maximum Bit Rate in DL.<br>Flow Bit Rates are specified in TS 23.501 [7]. | – | |
+| Maximum Flow Bit Rate Uplink | M | | Bit Rate 9.2.3.4 | Maximum Bit Rate in UL.<br>Flow Bit Rates are specified in TS 23.501 [7]. | – | |
+| Guaranteed Flow Bit Rate Downlink | M | | Bit Rate 9.2.3.4 | Guaranteed Bit Rate (provided that there is data to deliver) in DL.<br>Flow Bit Rates are specified in TS 23.501 [7]. | – | |
+| Guaranteed Flow Bit Rate Uplink | M | | Bit Rate 9.2.3.4 | Guaranteed Bit Rate (provided that there is data to deliver).<br>Flow Bit Rates are specified in TS 23.501 [7]. | – | |
+| Notification Control | O | | ENUMERATED (notification requested, ...) | Notification control is specified in TS 23.501 [7] | – | |
+| Maximum Packet Loss Rate Downlink | O | | Packet Loss Rate 9.2.3.11 | Indicates the maximum rate for lost packets that can be tolerated in the downlink direction.<br>Maximum Packet Loss Rate is specified in TS 23.501 [7]. | – | |
+| Maximum Packet Loss Rate Uplink | O | | Packet Loss Rate 9.2.3.11 | Indicates the maximum rate for lost packets that can be tolerated in the uplink direction.<br>Maximum Packet Loss Rate is specified in TS | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------|-------------|----------------------|
+| | | | | 23.501 [7]. | | |
+| Alternative QoS Parameters Set List | O | | 9.2.3.102 | Indicates alternative sets of QoS Parameters for the QoS flow. | YES | ignore |
+
+### 9.2.3.7 Allocation and Retention Priority
+
+This IE specifies the relative importance compared to other QoS flows for allocation and retention of the NR RAN resource.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|----------|-------|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Allocation/Retention Priority</b> | | 1 | | |
+| >Priority Level | M | | INTEGER (0..15, ...) | <p><b>Desc.:</b> This defines the relative importance of a resource request. (see TS 23.501 [7]).</p> <p><b>Usage:</b><br/>Values between 1 and 15 are ordered in decreasing order of priority, i.e., 1 is the highest and 15 is the lowest.</p> |
+| >Pre-emption Capability | M | | ENUMERATED (shall not trigger pre-emption, may trigger pre-emption, ...) | <p><b>Desc.:</b> This IE indicates the pre-emption capability of the request on other QoS flows (see TS 23.501 [7]).</p> <p><b>Usage:</b><br/>The QoS flow shall not pre-empt other QoS flow or, the QoS flow may pre-empt other QoS flows.<br/>NOTE: The Pre-emption Capability indicator applies to the allocation of resources for a QoS flow and as such it provides the trigger to the pre-emption procedures/processes of the gNB.</p> |
+| >Pre-emption Vulnerability | M | | ENUMERATED (not pre-emptable, pre-emptable, ...) | <p><b>Desc.:</b> This IE indicates the vulnerability of the QoS flow to preemption of other QoS flows (see TS 23.501 [7]).</p> <p><b>Usage:</b><br/>The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows.<br/>NOTE: Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the pre-emption procedures/processes of the gNB.</p> |
+
+### 9.2.3.8 Non dynamic 5QI Descriptor
+
+This IE defines QoS characteristics for a standardized or pre-configured 5QI for downlink and uplink.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|-------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| 5QI | M | | INTEGER<br>(0..255, ...) | This IE contains the standardized or pre-configured 5QI as specified in TS 23.501 [7] | – | |
+| Priority Level | O | | 9.2.3.62 | Priority level is specified in TS 23.501 [7]. When included, it overrides standardized or pre-configured value. | – | |
+| Averaging Window | O | | 9.2.3.14 | Averaging window is specified in TS 23.501 [7]. When included, it overrides standardized or pre-configured value. | – | |
+| Maximum Data Burst Volume | O | | 9.2.3.15 | Maximum Data Burst Volume is specified in TS 23.501 [7]. When included, it overrides standardized or pre-configured value. | – | |
+| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget<br>9.2.3.113 | Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore |
+| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget<br>9.2.3.113 | Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore |
+
+### 9.2.3.9 Dynamic 5QI Descriptor
+
+This IE defines the QoS characteristics for a non-standardized or not pre-configured 5QI for downlink and uplink.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|-----------------|-------|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Priority Level | M | | 9.2.3.62 | Priority level is specified in TS 23.501 [7]. | – | |
+| Packet Delay Budget | M | | 9.2.3.12 | Packet Delay Budget is specified in TS 23.501 [7]. This IE is ignored if the <i>Extended Packet Delay Budget</i> IE is present. | – | |
+| Packet Error Rate | M | | 9.2.3.13 | Packet Error Rate is specified in TS 23.501 [7]. | – | |
+| 5QI | O | | INTEGER (0..255, ...) | This IE contains the dynamically assigned 5QI as specified in TS 23.501 [7]. | – | |
+| Delay Critical | C-<br>ifGBRflow | | ENUMERATED (Delay critical, Non-delay critical, ...) | This IE indicates whether the GBR QoS flow is delay critical as specified in TS 23.501 [7]. | – | |
+| Averaging Window | C-<br>ifGBRflow | | 9.2.3.14 | Averaging window is specified in TS 23.501 [7]. | – | |
+| Maximum Data Burst Volume | O | | 9.2.3.15 | Maximum Data Burst Volume is specified in TS 23.501 [7]. This IE shall be included if the <i>Delay Critical</i> IE is set to "delay critical" and is be ignored otherwise. | – | |
+| Extended Packet Delay Budget | O | | 9.2.3.113 | Packet Delay Budget is specified in TS 23.501 [7]. | YES | ignore |
+| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget 9.2.3.113 | Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore |
+| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.2.3.113 | Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore |
+
+| Condition | Explanation |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| ifGBRflow | This IE shall be present if the <i>GBR QoS Flow Information</i> IE is present in the <i>QoS Flow Level QoS Parameters</i> IE. |
+
+### 9.2.3.10 QoS Flow Identifier
+
+This IE identifies either a QoS Flow within a PDU Session or an MBS QoS flow within an MBS Session. Definition and use of the QoS Flow Identifier is specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|--------------------------|-----------------------|
+| QoS Flow Identifier | M | | INTEGER<br>(0 ..63, ...) | |
+
+### 9.2.3.11 Packet Loss Rate
+
+This IE indicates the Packet Loss Rate for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|---------------------------|----------------------------------------------------------------------------------|
+| Packet Loss Rate | M | | INTEGER<br>(0..1000, ...) | Ratio of lost packets per number of packets sent, expressed in tenth of percent. |
+
+### 9.2.3.12 Packet Delay Budget
+
+This IE indicates the Packet Delay Budget for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|---------------------------|-------------------------------------------------------------------------------------------|
+| Packet Delay Budget | M | | INTEGER<br>(0..1023, ...) | Upper bound value for the delay that a packet may experience expressed in units of 0.5ms. |
+
+### 9.2.3.13 Packet Error Rate
+
+This IE indicates the Packet Error Rate for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------|
+| Scalar | M | | INTEGER (0..9,...) | The packet error rate is expressed as $Scalar * 10^{-k}$ , whereas $k$ is the Exponent. |
+| Exponent | M | | INTEGER (0..9, ...) | |
+
+### 9.2.3.14 Averaging Window
+
+This IE indicates the Averaging Window for a QoS flow and applies to GBR QoS flows only.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|---------------------------|-----------------------|
+| Averaging Window | M | | INTEGER<br>(0..4095, ...) | Unit: ms. |
+
+### 9.2.3.15 Maximum Data Burst Volume
+
+This IE indicates the Maximum Data Burst Volume for a QoS flow and applies to delay critical GBR QoS flows only.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|----------------------------------------------|-----------------------|
+| Maximum Data Burst Volume | M | | INTEGER<br>(0..4095, ..., 4096..<br>2000000) | Unit: byte, |
+
+### 9.2.3.16 NG-RAN node UE XnAP ID
+
+The NG-RAN node UE XnAP ID uniquely identifies a UE over the Xn interface within the NG-RAN node.
+
+The use of this IE is defined in TS 38.401 [2].
+
+NOTE: If Xn-C signalling transport is shared among multiple interface instances, the value of the NG-RAN node UE XnAP ID is allocated so that it can be associated with the corresponding Xn-C interface instance.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-----------------------------------|-----------------------|
+| NG-RAN node UE XnAP ID | M | | INTEGER (0 .. 2 <sup>32</sup> -1) | |
+
+### 9.2.3.17 UE Aggregate Maximum Bit Rate
+
+The UE Aggregate Maximum Bitrate is applicable for all Non-GBR QoS flows per UE which is defined for the Downlink and the Uplink direction and a subscription parameter provided by the AMF to the NG-RAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------|
+| <b>UE Aggregate Maximum Bit Rate</b> | | 1 | | Applicable for Non-GBR QoS flows. |
+| >UE Aggregate Maximum Bit Rate Downlink | M | | Bit Rate 9.2.3.4 | This IE indicates the UE Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the downlink direction. |
+| >UE Aggregate Maximum Bit Rate Uplink | M | | Bit Rate 9.2.3.4 | This IE indicates the UE Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the uplink direction. |
+
+### 9.2.3.18 PDU Session ID
+
+This IE identifies a PDU Session for a UE. Definition and use of the PDU Session ID is specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|-----------------------|
+| PDU Session ID | M | | INTEGER (0 ..255) | |
+
+### 9.2.3.19 PDU Session Type
+
+This IE defines the PDU Session Type as specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|-----------------------------------------------------------------------|-----------------------|
+| PDU Session Type | M | | ENUMERATED<br>(IPv4, IPv6, IPv4v6,<br>Ethernet,<br>Unstructured, ...) | |
+
+### 9.2.3.20 TAI Support List
+
+This IE indicates the list of TAIs supported by NG-RAN node and associated characteristics e.g. supported slices.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|----------------------------------------|------------------------------------------|----------------------------------------------------------------------------|-------------|----------------------|
+| <b>TAI Support Item</b> | | 1..<maxno<br>ofsupport<br>edTACs> | | | – | |
+| >TAC | M | | 9.2.2.5 | Broadcast TAC | – | |
+| >> <b>Broadcast PLMNs</b> | | 1..<maxno<br>ofsupport<br>edPLMNs<br>> | | | – | |
+| >>PLMN Identity | M | | 9.2.2.4 | Broadcast PLMN | – | |
+| >>TAI Slice Support List | M | | Slice Support List<br>9.2.3.22 | Supported S-NSSAIs per TAC, per PLMN or per SNPN. | – | |
+| >>NPN Support | O | | 9.2.2.72 | | YES | reject |
+| >>Extended TAI Slice Support List | O | | Extended Slice Support List<br>9.2.3.139 | Additional Supported S-NSSAIs per TAC, per PLMN or per SNPN. | YES | reject |
+| >>TAI NSAG Support List | O | | 9.2.3.170 | NSAG information associated with the slices per TAC, per PLMN or per SNPN. | YES | ignore |
+| >>TAI Slice Unavailable Cell List | O | | 9.2.3.207 | Indicates the cells of the TAI configured with zero resources for a slice. | YES | ignore |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------|
+| maxnoofsupportedTACs | Maximum no. of TACs supported by an NG-RAN node. Value is 256. |
+| maxnoofsupportedPLMNs | Maximum no. of PLMNs supported by an NG-RAN node. Value is 12. |
+
+### 9.2.3.21 S-NSSAI
+
+This IE indicates the S-NSSAI as defined in TS 23.003 [22].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|------------------------|-----------------------|
+| SST | M | | OCTET STRING (SIZE(1)) | |
+| SD | O | | OCTET STRING (SIZE(3)) | |
+
+### 9.2.3.22 Slice Support List
+
+This IE indicates the list of supported slices.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|------------------------|-----------------------|-----------------------|
+| <b>Slice Support Item</b> | | 1..<maxnoofSliceItems> | | |
+| >S-NSSAI | M | | 9.2.3.21 | |
+
+| Range bound | Explanation |
+|-------------------|--------------------------------------------------------------|
+| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. |
+
+### 9.2.3.23 Index to RAT/Frequency Selection Priority
+
+The *Index to RAT/Frequency Selection Priority* IE is used to define local configuration for RRM strategies such as camp priorities and control of inter-RAT/inter-frequency mobility in RRC\_CONNECTED, as specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------|----------|-------|-----------------------|-----------------------|
+| Index to RAT/Frequency Selection Priority | M | | INTEGER (1..256) | |
+
+### 9.2.3.24 GUAMI
+
+This IE contains the Globally Unique AMF Identifier (GUAMI) as defined in TS 23.003 [22].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|------------------------|-----------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+| <b>AMF Identifier</b> | | 1 | | |
+| >AMF Region ID | M | | BIT STRING (SIZE (8)) | |
+| >AMF Set ID | M | | BIT STRING (SIZE (10)) | |
+| >AMF Pointer | M | | BIT STRING (SIZE (6)) | |
+
+### 9.2.3.25 Target Cell Global ID
+
+This IE contains either an NR CGI or an E-UTRA CGI.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>Target Cell</i> | M | | | |
+| >NR | | | | |
+| >>NR CGI | M | | 9.2.2.7 | |
+| >E-UTRA | | | | |
+| >>E-UTRA CGI | M | | 9.2.2.8 | |
+
+### 9.2.3.26 AMF UE NGAP ID
+
+This IE is defined in TS 38.413 [5] and used to uniquely identify the UE association over the source side NG interface instance.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------------------|-----------------------|
+| AMF UE NGAP ID | M | | INTEGER (0 .. 2 <sup>40</sup> -1) | |
+
+### 9.2.3.27 SCG Configuration Query
+
+The *SCG Configuration Query* IE is used to request the S-NG-RAN node to provide current SCG configuration.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------|----------|-------|------------------------|-----------------------|
+| SCG Configuration Query | M | | ENUMERATED (True, ...) | |
+
+### 9.2.3.28 RLC Mode
+
+The *RLC Mode* IE indicates the RLC Mode used for a DRB.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|-----------------------------------------------------------------------------------------------------|-----------------------|
+| RLC Mode | M | | ENUMERATED ( RLC-AM, RLC-UM-Bidirectional, RLC-UM-Unidirectional-UL, RLC-UM-Unidirectional-DL, ...) | |
+
+### 9.2.3.29 Transport Layer Address
+
+This IE is defined to contain an IP address.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|--------------------------|-----------------------|
+| Transport Layer Address | M | | BIT STRING (1..160, ...) | |
+
+### 9.2.3.30 UP Transport Layer Information
+
+This element is used to provide the transport layer information associated with NG or Xn user plane transport. In this release it corresponds to an IP address and a GTP Tunnel Endpoint Identifier. When the NR-DC UE is connected with an IAB, the QoS Mapping Information is used to set the IP header of packets in case that the S-NG-RAN node serves the IAB and the packets belonging to MN-terminated split bearer/SCG bearer are transmitted from M-NG-RAN node to S-NG-RAN node, and in case that the M-NG-RAN node serves the IAB and the packets belonging to SN-terminated split bearer/MCG bearer are transmitted from S-NG-RAN node to M-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------|-------------|----------------------|
+| CHOICE <i>UP Transport Layer Information</i> | M | | | | – | |
+| >GTP tunnel | | | | | | |
+| >>Transport Layer Address | M | | 9.2.3.29 | The Transport Layer Address is specified in TS 38.424 [19] and TS 38.414 [20]. | – | |
+| >>GTP-TEID | M | | OCTET STRING (4) | The Tunnel Endpoint Identifier (TEID) is specified in TS 29.281 [18] | – | |
+| >>QoS Mapping Information | O | | 9.2.3.144 | | YES | reject |
+
+### 9.2.3.31 CP Transport Layer Information
+
+This element is used to provide the transport layer information associated with NG or Xn control plane transport.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-------|----------------------------------|-----------------------|-------------|----------------------|
+| CHOICE <i>CP Transport Layer Information</i> | M | | | | – | |
+| >Endpoint-IP-address | | | | | | |
+| >>Endpoint IP Address | M | | Transport Layer Address 9.2.3.29 | | – | |
+| >Endpoint-IP-address-and-port | | | | | YES | reject |
+| >>Endpoint IP Address | M | | Transport Layer Address 9.2.3.29 | | – | |
+| >>Port Number | M | | BIT STRING (16) | | – | |
+
+### 9.2.3.32 Masked IMEISV
+
+This information element contains the IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+|---------------|----------|-------|-----------------------|-----------------------|
+
+| | | | | |
+|---------------|---|--|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Masked IMEISV | M | | BIT STRING (SIZE(64)) | Coded as the International Mobile station Equipment Identity and Software Version Number (IMEISV) defined in TS 23.003 [22] with the last 4 digits of the SNR masked by setting the corresponding bits to 1. |
+|---------------|---|--|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### 9.2.3.33 DRB ID
+
+This IE contains the DRB ID.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| DRB ID | M | | INTEGER (1..32, ...) | |
+
+### 9.2.3.34 DL Forwarding
+
+This element indicates a proposal for forwarding of downlink packets.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------------------------|-----------------------|
+| DL Forwarding | M | | ENUMERATED (DL forwarding proposed, ...) | |
+
+### 9.2.3.35 Data Forwarding Accepted
+
+This element indicates that data forwarding was accepted.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------|----------|-------|--------------------------------------------|-----------------------|
+| Data Forwarding Accepted | M | | ENUMERATED (data forwarding accepted, ...) | |
+
+### 9.2.3.36 COUNT Value for PDCP SN Length 12
+
+This information element indicates the 12-bit long PDCP sequence number and the corresponding 20 bits long Hyper Frame Number.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------|-----------------------|
+| PDCP-SN Length 12 | M | | INTEGER (0..4095) | |
+| HFN for PDCP-SN Length 12 | M | | INTEGER (0..1048575) | |
+
+### 9.2.3.37 COUNT Value for PDCP SN Length 18
+
+This information element indicates the 18-bit long PDCP sequence number and the corresponding 14 bits long Hyper Frame Number.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|------------------------|-----------------------|
+| PDCP-SN Length 18 | M | | INTEGER<br>(0..262143) | |
+| HFN for PDCP-SN Length 18 | M | | INTEGER<br>(0..16383) | |
+
+### 9.2.3.38 RAN Paging Area
+
+The *RAN Paging Area* IE defines the paging area within a PLMN for RAN paging a UE in RRC\_INACTIVE state.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|-----------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M | | 9.2.2.4 | |
+| CHOICE <i>RAN Paging Area</i><br><i>Choice</i> | M | | | |
+| > <i>Cell List</i> | | | | |
+| >> <i>Cell List Item</i> | | 1 .. <<br><i>maxnoofCellsInRNA</i> > | | |
+| >>>NG-RAN Cell Identity | M | | 9.2.2.9 | In this version of the specification, the RAN paging area should contain NG-RAN cells of the same RAT type. |
+| > <i>RAN Area ID List</i> | | | | |
+| >> <i>RAN Area ID List Item</i> | | 1 .. <<br><i>maxnoofRanAreasInRNA</i> > | | |
+| >>>RAN Area ID | M | | 9.2.3.39 | |
+
+| Range bound | Explanation |
+|-----------------------------|----------------------------------------------------------------------|
+| <i>maxnoofCellsInRNA</i> | Maximum no. of cells in a RAN notification area. Value is 32. |
+| <i>maxnoofRanAreasInRNA</i> | Maximum no. of RAN area IDs in a RAN notification area. Value is 16. |
+
+### 9.2.3.39 RAN Area ID
+
+This IE defines the RAN Area ID.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|--------------------------|-----------------------|
+| TAC | M | | 9.2.2.5 | Tracking Area Code |
+| RANAC | O | | RAN Area Code<br>9.2.2.6 | |
+
+### 9.2.3.40 UE Context ID
+
+This IE is used to address a UE Context within an NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>UE Context ID</i> | M | | | |
+| > <i>RRC Resume</i> | | | | |
+| >> <i>I-RNTI</i> | M | | 9.2.3.46 | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >>Allocated C-RNTI | M | | BIT STRING (SIZE (16)) | Temporary C-RNTI or C-RNTI allocated to the UE by the cell where the RRC connection has been requested to be resumed, contained in the MAC RAR or MAC MSGB as defined in TS 38.321 [35] or in TS 36.321 [36]. |
+| >>Access PCI | M | | NG-RAN Cell PCI 9.2.2.10 | The cell PCI where the RRC connection has been requested to be resumed. |
+| >RRC Reestablishment | | | | |
+| >>C-RNTI | M | | BIT STRING (SIZE (16)) | Corresponds to information provided either in the <i>c-RNTI</i> contained in the <i>RRCReestablishmentRequest</i> message (TS 38.331 [10]) or in the <i>RRCConnectionReestablishmentRequest</i> message (TS 36.331 [14]). |
+| >>Failure Cell PCI | M | | NG-RAN Cell PCI 9.2.2.10 | |
+
+### 9.2.3.41 Assistance Data for RAN Paging
+
+This IE provides assistance information for RAN paging.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| RAN Paging Attempt Information | O | | 9.2.3.42 | | – | |
+| NPN Paging Assistance Information | O | | 9.2.3.121 | | YES | ignore |
+
+### 9.2.3.42 RAN Paging Attempt Information
+
+This IE includes information related to the RAN paging attempt over Xn.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------|
+| Paging Attempt Count | M | | INTEGER (1..16,...) | Number of the RAN paging attempt. |
+| Intended Number of Paging Attempts | M | | INTEGER (1..16,...) | Intended number of RAN paging attempts. |
+| Next Paging Area Scope | O | | ENUMERATED (same, changed, ...) | Indicates whether the RAN paging area scope will change at next RAN paging attempt. |
+
+### 9.2.3.43 UE RAN Paging Identity
+
+The IE defines the UE Identity for RAN paging a UE in RRC\_INACTIVE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+|---------------|----------|-------|-----------------------|-----------------------|
+
+| | | | | |
+|-------------------------------|---|--|------------------------|--|
+| | | | <b>reference</b> | |
+| CHOICE UE RAN Paging Identity | M | | | |
+| >I-RNTI full | | | | |
+| >>I-RNTI full | M | | BIT STRING (SIZE (40)) | |
+
+### 9.2.3.44 Paging Priority
+
+This information element contains an indication of the priority to be considered for the paging request.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|
+| Paging Priority | M | | ENUMERATED (PrioLevel1, PrioLevel2, PrioLevel3, PrioLevel4, PrioLevel5, PrioLevel6, PrioLevel7, PrioLevel8, ...) | Lower value codepoint indicates higher priority. |
+
+### 9.2.3.45 Delivery Status
+
+This IE provides the delivery status of RRC PDUs provided by RRC Transfer message.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------|----------|-------|---------------------------------|--------------------------------------------------------------------------|
+| Delivery Status | M | | INTEGER (0..2 <sup>12</sup> -1) | Highest successfully delivered NR PDCP SN, as defined in TS 38.323 [11]. |
+
+### 9.2.3.46 I-RNTI
+
+The I-RNTI is defined for allocation in an NR or E-UTRA serving cell as a reference to a UE Context within an NG-RAN node. The I-RNTI is partitioned into two parts, the first part identifies the NG-RAN node that allocated the I-RNTI and the second part identifies the UE context stored in this NG-RAN node, refer to Annex C in TS 38.300 [9], or the I-RNTI is partitioned into three parts, the first part indicates the length of NG-RAN Node ID part of the NG-RAN Node that allocated the I-RNTI, the second part identifies the NG-RAN node that allocated the I-RNTI and the third part identifies the UE context stored in this NG-RAN node, refer to Annex F in TS 38.300[9].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE I-RNTI | | | | |
+| >I-RNTI full | | | | |
+| >>I-RNTI full | M | | BIT STRING (SIZE (40)) | This IE is used to identify the suspended UE context of a UE in RRC_INACTIVE using 40 bits and corresponds to information provided either in the <i>I-RNTI-Value</i> IE as defined in TS 38.331 [10] or in the <i>I-RNTI</i> IE as defined in TS 36.331 [14]. |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >I-RNTI short | | | | |
+| >>I-RNTI short | M | | BIT STRING (SIZE (24)) | This IE is used to identify the suspended UE context of a UE in RRC_INACTIVE using 24 bits and corresponds to information provided either in the <i>ShortI-RNTI-Value</i> IE as defined in TS 38.331 [10] or in the <i>ShortI-RNTI</i> IE as defined in TS 36.331 [14]. |
+
+### 9.2.3.47 Location Reporting Information
+
+This information element indicates how the location information should be reported.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------|
+| Event Type | M | | ENUMERATED (<br>report upon change of serving cell, report UE moving presence into or out of the Area of Interest, ..., report upon change of serving cell and Area of Interest) | | – | |
+| Report Area | M | | ENUMERATED (Cell, ...) | | – | |
+| Area of Interest Information | O | | 9.2.3.48 | | – | |
+| Additional Location Information | O | | ENUMERATED (Include PSCell, ...) | | YES | ignore |
+
+### 9.2.3.48 Area of Interest Information
+
+This IE contains indicates the Area of Interest information, which may contain multiple Areas of Interest, as specified in TS 23.502 [13].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------------------------------|-----------------------|-----------------------|
+| Area of Interest Item | | 1..<br><maxnoofAoIs<br>> | | |
+| >List of TAls in Area of Interest | | 0..1 | | |
+| >>TAI in Area of Interest Item | | 1..<<br>maxnoofTAIsinAoI<br>> | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|---------------------------|-----------------------|------------------------------------------|
+| >>>PLMN Identity | M | | 9.2.2.4 | |
+| >>>TAC | M | | 9.2.2.5 | |
+| >List of Cells in Area of Interest | | 0..1 | | This IE may need to be refined with SA2. |
+| >>Cell Item | | 1..<maxnoofcellsInAoI> | | |
+| >>>PLMN Identity | M | | 9.2.2.4 | |
+| >>>NG-RAN Cell Identity | M | | 9.2.2.9 | |
+| >List of Global NG-RAN Nodes in Area of Interest | | 0..1 | | |
+| >>Global NG-RAN Node in Area of Interest Item | | 1..<maxnoofRANNodesinAoI> | | |
+| >>>Global NG-RAN Node ID | M | | 9.2.2.3 | |
+| >Request Reporting Reference ID | M | | 9.2.3.58 | |
+
+| Range bound | Explanation |
+|----------------------|-------------------------------------------------------------------------|
+| maxnoofAOIs | Maximum no. of Areas of Interest. Value is 64. |
+| maxnoofTAlsInAoI | Maximum no. of tracking areas in an Area of Interest. Value is 16. |
+| maxnoofcellsInAoI | Maximum no. of cells in an Area of Interest. Value is 256. |
+| maxnoofRANNodesinAoI | Maximum no. of global NG-RAN nodes in an Area of Interest. Value is 64. |
+
+### 9.2.3.49 UE Security Capabilities
+
+The *UE Security Capabilities* IE defines the supported algorithms for encryption and integrity protection in the UE. Except as noted below, the NG-RAN nodes store and send the complete bitmaps without modification or truncation as specified in TS 38.300 [9].
+
+NOTE: There is a 1-bit circular shift between the bitmaps of the IE in this specification and the corresponding bitmaps in TS 38.413 [5].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------|----------|-------|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NR Encryption Algorithms | M | | BIT STRING {nea1-128(1), nea2-128(2), nea3-128(3)}<br>(SIZE(16, ...)) | Each position in the bitmap represents an encryption algorithm:<br>"all bits equal to 0" – UE supports no other NR algorithm than NEA0,<br>"second bit" – 128-NEA1,<br>"third bit" – 128-NEA2,<br>"fourth bit" – 128-NEA3,<br>"fifth to eighth bit" correspond to bit 4 to bit 1 of octet 3 in the <i>UE Security Capability</i> IE defined in TS 24.501 [30],<br>other bits reserved for future use.<br>Value '1' indicates support and value '0' indicates no support of the algorithm. |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------------|----------|-------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | | Algorithms are defined in TS 33.501 [28]. |
+| NR Integrity Protection Algorithms | M | | BIT STRING {nia1-128(1), nia2-128(2), nia3-128(3)}<br>(SIZE(16, ...)) | Each position in the bitmap represents an integrity protection algorithm:<br>"all bits equal to 0" – UE supports no other NR algorithm than NIA0,<br>"second bit" – 128-NIA1,<br>"third bit" – 128-NIA2,<br>"fourth bit" – 128-NIA3,<br>"fifth to eighth bit" correspond to bit 4 to bit 1 of octet 4 in the <i>UE Security Capability</i> IE defined in TS 24.501 [30],<br>other bits reserved for future use.<br>Value '1' indicates support and value '0' indicates no support of the algorithm.<br>Algorithms are defined in TS 33.501 [28]. |
+| E-UTRA Encryption Algorithms | M | | BIT STRING {eea1-128(1), eea2-128(2), eea3-128(3)}<br>(SIZE(16, ...)) | Each position in the bitmap represents an encryption algorithm:<br>"all bits equal to 0" – UE supports no other algorithm than EEA0,<br>"second bit" – 128-EEA1,<br>"third bit" – 128-EEA2,<br>"fourth bit" – 128-EEA3,<br>"fifth to eighth bit" correspond to bit 4 to bit 1 of octet 5 in the <i>UE Security Capability</i> IE defined in TS 24.501 [30],<br>other bits reserved for future use.<br>Value '1' indicates support and value '0' indicates no support of the algorithm.<br>Algorithms are defined in TS 33.401 [29]. |
+| E-UTRA Integrity Protection Algorithms | M | | BIT STRING {eia1-128(1), eia2-128(2), eia3-128(3)}<br>(SIZE(16, ...)) | Each position in the bitmap represents an integrity protection algorithm:<br>"all bits equal to 0" – UE supports no other algorithm than EIA0,<br>"second bit" – 128-EIA1,<br>"third bit" – 128-EIA2,<br>"fourth bit" – 128-EIA3,<br>"fifth to eighth bit" correspond to bit 4 to bit 1 of octet 6 in the <i>UE Security Capability</i> IE defined in TS 24.501 [30],<br>other bits reserved for future use.<br>Value '1' indicates support and value '0' indicates no support of the algorithm. |
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|-----------------------|-------------------------------------------|
+| | | | | Algorithms are defined in TS 33.401 [29]. |
+
+### 9.2.3.50 AS Security Information
+
+The *AS Security Information* IE is used to generate the key material to be used for AS security with the UE.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------------|----------|-------|-----------------------|---------------------------------------------------------|
+| Key NG-RAN Star | M | | BIT STRING (256) | $K_{\text{NG-RAN}}^*$ defined in TS 33.501 [28]. |
+| Next Hop Chaining Count | M | | INTEGER (0..7) | Next Hop Chaining Count (NCC) defined in TS 33.501 [28] |
+
+### 9.2.3.51 S-NG-RAN node Security Key
+
+The *S-NG-RAN node Security Key* IE is used to apply security in the S-NG-RAN node as defined in TS 33.501 [28].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------|----------|-------|------------------------|-----------------------------------------------------------------------------------|
+| S-NG-RAN node Security Key | M | | BIT STRING (SIZE(256)) | The $S-K_{\text{SN}}$ which is provided by the M-NG-RAN node, see TS 33.501 [28]. |
+
+### 9.2.3.52 Security Indication
+
+This IE contains the user plane integrity protection indication and confidentiality protection indication which indicates the requirements on UP integrity protection and ciphering for the corresponding PDU session, respectively.
+
+Additionally, this IE contains the maximum integrity protected data rate values (UL and DL) per UE for integrity protected DRBs.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------------------------------|------------------------------------------------------------|-------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Integrity Protection Indication | M | | ENUMERATED (required, preferred, not needed,...) | Indicates whether UP integrity protection shall apply, should apply, or shall not apply for the concerned PDU session. |
+| Confidentiality Protection Indication | M | | ENUMERATED (required, preferred, not needed, ...) | Indicates whether UP ciphering shall apply, should apply, or shall not apply for the concerned PDU session. |
+| Maximum Integrity Protected Data Rate | C-<br>ifIntegrityP<br>rotectionre<br>quiredorpr<br>eferred | | 9.2.3.73 | If present, this IE contains the values received from the CN for the overall UE capability. This IE may be ignored by the SN in the case of dual connectivity. |
+
+| Condition | Explanation |
+|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ifIntegrityProtectionrequiredorpreferred | This IE shall be present if the <i>Integrity Protection</i> IE within the <i>Security Indication</i> IE is present and set to “required” or “preferred”. |
+
+### 9.2.3.53 Mobility Restriction List
+
+This IE defines roaming or access restrictions for subsequent mobility actions for which the NG-RAN provides information about the target of the mobility action towards the UE, e.g., handover, or for SCG selection during dual connectivity operation or for assigning proper RNAs. If the NG-RAN receives the *Mobility Restriction List* IE, it shall overwrite previously received restriction information. NG-RAN behaviour upon receiving this IE is specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Serving PLMN | M | | PLMN Identity 9.2.2.4 | | – | |
+| <b>Equivalent PLMNs</b> | | 0..<maxno ofEPLMNs> | | Allowed PLMNs in addition to Serving PLMN.<br>This list corresponds to the list of "equivalent PLMNs" as defined in TS 24.501 [30].<br>This list is part of the roaming restriction information.<br>Roaming restrictions apply to PLMNs other than the Serving PLMN and Equivalent PLMNs. | – | |
+| >PLMN Identity | M | | 9.2.2.4 | | – | |
+| <b>RAT Restrictions</b> | | 0..<maxno ofPLMNs> | | This IE contains RAT restriction related information as specified in TS 23.501 [7]. | – | |
+| >PLMN Identity | M | | 9.2.2.4 | | – | |
+| >RAT Restriction Information | M | | BIT STRING {<br>e-UTRA (0),<br>nR (1), nR-unlicensed (2),<br>nR-LEO (3),<br>nR-MEO (4),<br>nR-GEO (5),<br>nR-OTHERSAT (6)}<br>(SIZE(8, ...)) | Each position in the bitmap represents a RAT.<br>If a bit is set to "1", the respective RAT is restricted for the UE.<br>If a bit is set to "0", the respective RAT is not restricted for the UE. Bit 7 is reserved for future use. | – | |
+| >Extended RAT Restriction Information | O | | 9.2.3.99 | If this IE is included, the <i>RAT Restriction Information</i> IE is ignored. | YES | ignore |
+| <b>Forbidden Area</b> | | 0..<maxno | | This IE contains | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------------|----------|-----------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>Information</b> | | <i>ofPLMNs></i> | | Forbidden Area information as specified in TS 23.501 [7]. | | |
+| >PLMN Identity | M | | 9.2.2.4 | | – | |
+| <b>>Forbidden TACs</b> | | <i>1..<maxno ofForbiddenTACs></i> | | | – | |
+| >>TAC | M | | 9.2.2.5 | The TAC of the forbidden TAI. | – | |
+| <b>Service Area Information</b> | | <i>0..<maxno ofPLMNs></i> | | This IE contains Service Area Restriction information as specified in TS 23.501 [7]. | – | |
+| >PLMN Identity | M | | 9.2.2.4 | | – | |
+| <b>>Allowed TACs</b> | | <i>0..<maxno ofAllowed Areas></i> | | | – | |
+| >>TAC | M | | 9.2.2.5 | The TAC of the allowed TAI. | – | |
+| <b>>Not Allowed TACs</b> | | <i>0..<maxno ofAllowed Areas></i> | | | – | |
+| >>TAC | M | | 9.2.2.5 | The TAC of the not-allowed TAI. | – | |
+| Last E-UTRAN PLMN Identity | O | | 9.2.2.4 | Indicates the E-UTRAN PLMN ID from where the UE formerly handed over to 5GS and which is preferred in case of subsequent mobility to EPS. | YES | ignore |
+| Core Network Type Restriction for serving PLMN | O | | ENUMERATED (EPCForbidden, ...) | Indicates whether the UE is restricted to connect to EPC for the Serving PLMN as specified in TS 23.501 [7]. | YES | ignore |
+| <b>Core Network Type Restriction for Equivalent PLMNs</b> | | <i>0..<maxno ofEPLMNs></i> | | | YES | ignore |
+| >PLMN Identity | M | | 9.2.2.4 | Includes any of the Equivalent PLMNs listed in the <i>Mobility Restriction List</i> IE for which CN Type restriction applies as specified in TS 23.501 [7]. | – | |
+| >Core Network Type Restriction | M | | ENUMERATED (EPCForbidden, ...) | Indicates whether the UE is | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|-----------------------|-------------------------------------------------------|-------------|----------------------|
+| | | | 5GCForbidden, ...) | restricted to connect to EPC or to 5GC for this PLMN. | | |
+| NPN Mobility Information | O | | 9.2.3.119 | | YES | reject |
+
+| Range bound | Explanation |
+|----------------------|--------------------------------------------------------------------|
+| maxnoofEPLMNs | Maximum no. of equivalent PLMNs. Value is 15. |
+| maxnoofPLMNs | Maximum no. of allowed PLMNs. Value is 16. |
+| maxnoofForbiddenTACs | Maximum no. of forbidden Tracking Area Codes. Value is 4096. |
+| maxnoofAllowedAreas | Maximum no. of allowed or not allowed Tracking Areas. Value is 16. |
+
+### 9.2.3.54 Xn Benefit Value
+
+The *Xn Benefit Value* IE indicates the quantified benefit of the signalling connection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|-----------------------|--------------------------------------------------------------------|
+| Xn Benefit Value | M | | INTEGER (1..8, ...) | Value 1 indicates lowest benefit, and 8 indicates highest benefit. |
+
+### 9.2.3.55 Trace Activation
+
+This IE defines parameters related to a trace activation.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------|----------|-------|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| NG-RAN Trace ID | M | | 9.2.3.97 | | – | |
+| Interfaces To Trace | M | | BIT STRING (SIZE(8)) | Each position in the bitmap represents an NG-RAN node interface:<br>first bit = NG-C,<br>second bit = Xn-C,<br>third bit = Uu,<br>fourth bit = F1-C,<br>fifth bit = E1:<br>other bits reserved for future use.<br>Value '1' indicates 'should be traced'.<br>Value '0' indicates 'should not be traced'. | – | |
+| Trace Depth | M | | ENUMERATED (minimum, medium, maximum, MinimumWithoutVendorSpecific Extension, ...) | Defined in TS 32.422 [23]. | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | MediumWithout VendorSpecific Extension, MaximumWithoutVendorSpecificExtension, ...) | | | |
+| Trace Collection Entity IP Address | M | | Transport Layer Address 9.2.3.29 | For File based Reporting. Defined in TS 32.422 [23] Should be ignored if the <i>Trace Collection Entity URI</i> IE is present. | – | |
+| Trace Collection Entity URI | O | | URI 9.2.3.124 | For Streaming based Reporting. Defined in TS 32.422 [23] Replaces Trace Collection Entity IP Address if present | YES | ignore |
+| MDT Configuration | O | | 9.2.3.125 | This IE defines the MDT configuration parameters. | YES | ignore |
+
+### 9.2.3.56 Time To Wait
+
+This IE defines the minimum allowed waiting times.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|---------------------------------------------|-----------------------|
+| Time To Wait | M | | ENUMERATED (1s, 2s, 5s, 10s, 20s, 60s, ...) | |
+
+### 9.2.3.57 QoS Flow Notification Control Indication Info
+
+This IE provides information about QoS flows of a PDU Session Resource for which notification control has been requested.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------------|----------|-----------------------|--------------------------------------------|----------------------------------|-------------|----------------------|
+| <b>QoS Flow Notification Indication Info</b> | | 1 | | | – | |
+| > <b>QoS Flows Notify Item</b> | | 1..<maxno ofQoSFlows> | | | – | |
+| >>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+| >>Notification Information | M | | ENUMERATED (fulfilled, not fulfilled, ...) | | – | |
+| >>Current QoS Parameters Set | O | | Alternative QoS Parameters Set | Index to the currently fulfilled | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Index | | | Notify Index 9.2.3.104 | alternative QoS parameters set.<br>Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative parameter set. | | |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.3.58 Request Reporting Reference ID
+
+This IE contains the Request Reporting Reference ID and is used for UE presence in Area of Interest reporting as specified in TS 23.502 [13].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------|----------|-------|-----------------------|-----------------------|
+| Request Reporting Reference ID | M | | INTEGER (1..64, ...) | |
+
+### 9.2.3.59 User plane traffic activity report
+
+This IE is used to indicate user plane traffic activity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|------------------------------------------|--------------------------------------------------------------------------------------------------|
+| User plane traffic activity report | M | | ENUMERATED (inactive, re-activated, ...) | "re-activated" is only set after "inactive" has been reported for the concerned reporting object |
+
+### 9.2.3.60 Lower Layer presence status change
+
+This IE is used to indicate that lower layer resources' presence status shall be changed. If the presence status is set to "release lower layers" or "suspend lower layers", SDAP entities, PDCP entities, Xn-U bearer resources, NG-U bearer resources and UE context information shall be kept.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Lower Layer presence status change | M | | ENUMERATED (release lower layers, re-establish lower layers, ..., suspend lower layers, resume lower layers) | "re-establish lower layers" is only set after "release lower layers" has been indicated.<br>"resume lower layers" shall restore SCG.<br>"resume lower layers" shall be only set after "suspend lower layers" has been indicated. |
+
+### 9.2.3.61 RRC Resume Cause
+
+The purpose of the *RRC Resume Cause* IE is to indicate to the old NG-RAN node the reason for the RRC Connection Resume as received from the UE in the *resumeCause-r15* defined in TS 36.331 [14] or in the *resumeCause* defined in TS 38.331 [10]. In this version of the specification, this is limited to the case of RNA update.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|---------------------------------|-----------------------|
+| RRC Resume Cause | M | | ENUMERATED<br>(rna-Update, ...) | |
+
+### 9.2.3.6.2 Priority Level
+
+This IE indicates the Priority Level for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|--------------------------|---------------------------------------------------------------------------------------------------------------------|
+| Priority Level | M | | INTEGER<br>(1..127, ...) | Values ordered in decreasing order of priority, i.e. with 1 as the highest priority and 127 as the lowest priority. |
+
+### 9.2.3.6.3 PDCP SN Length
+
+The *PDCP SN Length* IE is used to indicate the PDCP SN length configuration of the bearer.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-------------------|----------|-------|-------------------------------------|---------------------------------------------------------|
+| UL PDCP SN Length | M | | ENUMERATED<br>(12bits, 18bits, ...) | This IE indicates the PDCP sequence number size for UL. |
+| DL PDCP SN Length | M | | ENUMERATED<br>(12bits, 18bits, ...) | This IE indicates the PDCP sequence number size for DL. |
+
+### 9.2.3.6.4 UE History Information
+
+The *UE History Information* IE contains information about cells that a UE has been served by in active state prior to the target cell. The overall mechanism is described in TS 36.300 [12].
+
+NOTE: The definition of this IE is aligned with the definition of the *UE History Information* IE in TS 38.413 [5].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------|----------|----------------------------------|-----------------------|----------------------------------------------------------|
+| <b>Last Visited Cell List</b> | | 1..<maxnoofCellsinUEHistoryInfo> | | Most recent information is added to the top of this list |
+| >Last Visited Cell Information | M | | 9.2.3.6.5 | |
+
+| Range bound | Explanation |
+|-----------------------------|------------------------------------------------------------------------------------------------------|
+| maxnoofCellsinUEHistoryInfo | Maximum number of last visited cell information records that can be reported in the IE. Value is 16. |
+
+### 9.2.3.6.5 Last Visited Cell Information
+
+The Last Visited Cell Information may contain cell specific information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------|----------|-------|-----------------------|----------------------------|
+| CHOICE <i>Last Visited Cell Information</i> | M | | | |
+| >NG-RAN Cell | | | | |
+| >>Last Visited NG-RAN Cell Information | M | | OCTET STRING | Defined in TS 38.413 [5]. |
+| >E-UTRAN Cell | | | | |
+| >>Last Visited E-UTRAN Cell Information | M | | OCTET STRING | Defined in TS 36.413 [31]. |
+| >UTRAN Cell | | | | |
+| >>Last Visited UTRAN Cell Information | M | | OCTET STRING | Defined in TS 25.413 [32]. |
+| >GERAN Cell | | | | |
+| >>Last Visited GERAN Cell Information | M | | OCTET STRING | Defined in TS 36.413 [31]. |
+
+### 9.2.3.66 Paging DRX
+
+This IE indicates the RAN paging cycle as defined in TS 38.304 [33] and TS 36.304 [34].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------|----------|-------|------------------------------------------------|-----------------------|
+| Paging DRX | M | | ENUMERATED (32, 64, 128, 256, ... , 512, 1024) | Unit is radio frame. |
+
+### 9.2.3.67 Security Result
+
+This IE indicates whether the security policy indicated as "preferred" in the *Security Indication* IE is performed or not.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------------|----------|-------|--------------------------------------------|----------------------------------------------------------------------------------------------|
+| Integrity Protection Result | M | | ENUMERATED (performed, not performed, ...) | Indicates whether UP integrity protection is performed or not for the concerned PDU session. |
+| Confidentiality Protection Result | M | | ENUMERATED (performed, not performed, ...) | Indicates whether UP ciphering is performed or not for the concerned PDU session. |
+
+### 9.2.3.68 UE Context Kept Indicator
+
+This IE indicates whether the UE Context is kept at the S-NG-RAN node in case of an M-NG-RAN node handover without S-NG-RAN node change or inter-M-NG-RAN node RRC resume without S-NG-RAN node change.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------------------|----------|-------|------------------------|-----------------------|
+| UE Context Kept Indicator | M | | ENUMERATED (true, ...) | |
+
+### 9.2.3.69 PDU Session Aggregate Maximum Bit Rate
+
+This IE is applicable for all Non-GBR QoS flows per PDU session which is defined for the downlink and the uplink direction and is provided at the Handover Preparation procedure to the target NG-RAN node and at the Retrieve UE Context procedure to the new NG-RAN node as received by the 5GC, during dual connectivity related procedures to the to the S-NG-RAN node as decided by the M-NG-RAN node, as specified in TS 37.340 [8].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------|
+| <b>PDU session Aggregate Maximum Bit Rate</b> | | 1 | | Applicable for Non-GBR QoS flows. |
+| >PDU session Aggregate Maximum Bit Rate Downlink | M | | Bit Rate 9.2.3.4 | This IE indicates the PDU session Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the downlink direction. |
+| >PDU session Aggregate Maximum Bit Rate Uplink | M | | Bit Rate 9.2.3.4 | This IE indicates the PDU session Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the uplink direction. |
+
+### 9.2.3.70 LCID
+
+This IE uniquely identifies a logical channel ID for the associated DRB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------|
+| LCID | M | | INTEGER (1..32, ...) | Corresponds to information provided in the <i>LogicalChannelIdentity</i> IE as defined in TS 38.331 [10]. |
+
+### 9.2.3.71 Duplication Activation
+
+The *Duplication Activation* IE indicates the initial status of UL PDCP duplication, i.e., whether UL PDCP Duplication is activated or not.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------------|----------|-------|------------------------------------|-----------------------|
+| Duplication Activation | M | | ENUMERATED (Active, Inactive, ...) | |
+
+### 9.2.3.72 RRC Config Indication
+
+This IE indicates the type of RRC configuration used at the S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------|----------|-------|---------------------------------------------|-----------------------|
+| RRC Config Indication | M | | ENUMERATED (full config, delta config, ...) | |
+
+### 9.2.3.73 Maximum Integrity Protected Data Rate
+
+This IE indicates the maximum aggregate data rate for integrity protected DRBs for a UE as defined in TS 38.300 [9].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Maximum IP Rate Uplink | M | | Maximum IP Rate 9.2.3.89 | Indicates the maximum aggregate rate for integrity protected DRBs supported by the UE in UL. If the <i>Maximum IP Rate Downlink</i> IE is absent, this IE applies to both UL and DL. | – | |
+| Maximum IP Rate Downlink | O | | Maximum IP Rate 9.2.3.89 | Indicates the maximum aggregate rate for integrity protected DRBs supported by the UE in the DL. | YES | ignore |
+
+### 9.2.3.74 PDCP Change Indication
+
+The PDCP Change Indication IE is used for S-NG-RAN node to either initiate the security key update or to request PDCP data recovery in M-NG-RAN node. The PDCP Change Indication IE is also used for M-NG-RAN node to request PDCP data recovery in S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|-------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>PDCP Change Indication</i> | M | | | |
+| >From S-NG-RAN node | | | | |
+| >>Indication from S-NG-RAN node to M-NG-RAN node | M | | ENUMERATED (S-NG-RAN node key update required, PDCP data recovery required, ...) | S-NG-RAN node key update required indicates that the security key in S-NG-RAN node needs to be updated. The value of PDCP data recovery required indicates that the M-NG-RAN node needs to perform PDCP data recovery. |
+| >From M-NG-RAN node | | | | |
+| >>Indication from M-NG-RAN node to S-NG-RAN node | M | | ENUMERATED (PDCP data recovery required, ...) | The value of PDCP data recovery required indicates that the S-NG-RAN node needs to perform PDCP data recovery. |
+
+### 9.2.3.75 UL Configuration
+
+This IE indicates how the UL PDCP is configured for the corresponding node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-----------------------------------------|-------------------------------------------------------------|
+| UL UE Configuration | M | | ENUMERATED (no-data, shared, only, ...) | Indicates how the UE uses the UL at the corresponding node. |
+
+### 9.2.3.76 UP Transport Parameters
+
+This IE contains Xn-U related information related to a DRB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|--------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>UP Transport Parameters</b> | | 1 | | |
+| > <b>UP Transport Item</b> | | 1..<maxnoofS<br>CellGroupsplu<br>s1> | | |
+| >>UP Transport Layer Information | M | | 9.2.3.30 | |
+| >>Cell Group ID | M | | INTEGER<br>(0..maxnoofSCellGr<br>oups, ...) | This IE corresponds to information provided in the <i>CellGroupId</i> IE as defined in TS 38.331 [10] (0=MCG, 1=SCG). In this version of the specification, values "2" and "3" shall not be set by the sender and ignored by the receiver.<br>For E-UTRA Cell Groups, the same encoding is used as for NR Cell Groups.<br>NOTE: There is no corresponding IE defined in TS 36.331 [14]. |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------|
+| maxnoofSCellGroups | Maximum no of Secondary Cell Groups. Value is 3. |
+
+### 9.2.3.77 Desired Activity Notification Level
+
+This IE contains information on which level activity notification shall be performed.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|-------|------------------------------------------------------------|-----------------------|
+| Desired Activity Notification Level | O | | ENUMERATED<br>(None, QoS Flow,<br>PDU session, UE,<br>...) | |
+
+### 9.2.3.78 Number of DRB IDs
+
+This IE indicates the number of DRB IDs.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------|----------|-------|-----------------------|-----------------------|
+| Number of DRB IDs | M | | INTEGER (1..32, ...) | |
+
+### 9.2.3.79 QoS Flow Mapping Indication
+
+This IE is used to indicate whether only the uplink or the downlink of a QoS flow is mapped to a DRB.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------|----------|-------|--------------------------|-----------------------------------------------------------------------------------------|
+| QoS Flow Mapping Indication | M | | ENUMERATED (ul, dl, ...) | This IE indicates whether only the uplink or the downlink QoS flow is mapped to the DRB |
+
+### 9.2.3.80 RLC Status
+
+The *RLC Status* IE indicates about the RLC configuration change included in the container towards the UE.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------|
+| Reestablishment Indication | M | | ENUMERATED (reestablished, ...) | Indicates that following the change of the radio status, the RLC has been re-established. |
+
+### 9.2.3.81 Expected UE Behaviour
+
+This IE indicates the behaviour of a UE with predictable activity and/or mobility behaviour, to assist the NG-RAN node in determining the optimum RRC connection time and to help with the RRC\_INACTIVE state transition and RNA configuration (e.g. size and shape of the RNA).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------|----------|------------------------------------|-------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expected UE Activity Behaviour | O | | 9.2.3.82 | |
+| Expected HO Interval | O | | ENUMERATED (sec15, sec30, sec60, sec90, sec120, sec180, long-time, ...) | Indicates the expected time interval between inter NG-RAN node handovers.<br>If "long-time" is included, the interval between inter NG-RAN node handovers is expected to be longer than 180 seconds. |
+| Expected UE Mobility | O | | ENUMERATED (stationary, mobile, ...) | Indicates whether the UE is expected to be stationary or mobile. |
+| <b>Expected UE Moving Trajectory</b> | | 0..1 | | Indicates the UE's expected geographical movement. |
+| <b>>Expected UE Moving Trajectory Item</b> | | 1.<maxnoofCellsUEMovingTrajectory> | | Includes list of visited and non-visited cells, where visited cells are listed in the order the UE visited them with the most recent cell being the first in the list. Non-visited cells are included immediately after the visited cell they are associated with. |
+| >>Global NG-RAN Cell Identity | M | | 9.2.2.27 | |
+| >>Time Stayed in Cell | O | | INTEGER (0..4095) | Included for visited cells and indicates the time a UE stayed in a cell in seconds. If the UE stays in a cell more than 4095 seconds, this IE is set to 4095. |
+
+| Range bound | Explanation |
+|-------------|-------------|
+|-------------|-------------|
+
+| | |
+|--------------------------------|------------------------------------------------------------|
+| maxnoofCellsUEMovingTrajectory | Maximum no. of cells of UE moving trajectory. Value is 16. |
+|--------------------------------|------------------------------------------------------------|
+
+### 9.2.3.8.2 Expected UE Activity Behaviour
+
+This IE indicates information about the expected "UE activity behaviour" of the UE or the PDU session as defined in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------|----------|-------|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expected Activity Period | O | | INTEGER (1..30 40 50 60 80 100 120 150 180 181, ...) | If set to "181" the expected activity time is longer than 180 seconds.<br>The remaining values indicate the expected activity time in [seconds]. |
+| Expected Idle Period | O | | INTEGER (1..30 40 50 60 80 100 120 150 180 181, ...) | If set to "181" the expected idle time is longer than 180 seconds.<br>The remaining values indicate the expected idle time in [seconds]. |
+| Source of UE Activity Behaviour Information | O | | ENUMERATED (subscription information, statistics, ...) | If "subscription information" is indicated, the information contained in the <i>Expected Activity Period</i> IE and the <i>Expected Idle Period</i> IE, if present, is derived from subscription information.<br>If "statistics" is indicated, the information contained in the <i>Expected Activity Period</i> IE and the <i>Expected Idle Period</i> IE, if present, is derived from statistical information. |
+
+### 9.2.3.8.3 AMF Region Information
+
+This IE indicates the Global AMF Region IDs of the AMF Regions to which the NG-RAN node belongs.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|------------------------|-----------------------|-----------------------|
+| <b>AMF Region Information</b> | | 1 | | |
+| >Global AMF Region Information Item | | 1..<maxnoofAMFRegions> | | |
+| >>PLMN Identity | M | | 9.2.2.4 | |
+| >>AMF Region Identifier | | 1 | | |
+| >>>AMF Region ID | M | | BIT STRING (SIZE (8)) | |
+
+| Range bound | Explanation |
+|-------------------|-----------------------------------------------------------------------------|
+| maxnoofAMFRegions | Maximum no. of AMF Regions an NG-RAN node can be connected to. Value is 16. |
+
+### 9.2.3.8.4 TNL Association Usage
+
+This IE indicates the usage of the TNL association.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| TNL Association Usage | O | | ENUMERATED (ue, non-ue, both, ...) | Indicates whether the TNL association is only used for UE associated signalling, or non-UE associated signalling, or both. |
+
+### 9.2.3.85 Network Instance
+
+This IE provides the network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------|----------|-------|-----------------------|-----------------------|
+| Network Instance | M | | INTEGER (1..256, ...) | |
+
+### 9.2.3.86 PDCP Duplication Configuration
+
+The *PDCP Duplication Configuration* IE indicates whether PDCP Duplication is configured or de-configured.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------|----------|-------|----------------------------------------------|-----------------------|
+| PDCP Duplication Configuration | M | | ENUMERATED ( configured, de-configured, ...) | |
+
+### 9.2.3.87 Secondary RAT Usage Information
+
+This IE provides information on the Secondary RAT resources used by a PDU Session with MR-DC as specified in TS 37.340 [8].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|----------------------|---------------------------------------------------------------|-----------------------|
+| <b>PDU Session Usage Report</b> | | 0..1 | | |
+| >RAT Type | M | | ENUMERATED (nR, e-UTRA, ..., nR-unlicensed, eUTRA-unlicensed) | |
+| >PDU Session Timed Report List | M | | Volume Timed Report List 9.2.3.88 | |
+| <b>QoS Flows Usage Report List</b> | | 0..1 | | |
+| >QoS Flows Usage Report Item | | 1..<maxnoofQoSflows> | | |
+| >>QoS Flow Indicator | M | | 9.2.3.10 | |
+| >>RAT Type | M | | ENUMERATED (nR, eutra, ..., nR-unlicensed, eUTRA-unlicensed) | |
+| >>QoS Flows Timed | M | | Volume Timed | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|-----------------------|
+| Report List | | | Report List<br>9.2.3.88 | |
+
+| Range bound | Explanation |
+|-----------------|-----------------------------------------------------------------------|
+| maxnoofQoSFlows | Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
+
+### 9.2.3.88 Volume Timed Report List
+
+This IE provides information on the data usage.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-----------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Volume Timed Report Item</b> | | 1..<br><maxnoofTimePeriods> | | |
+| >Start Timestamp | M | | OCTET STRING<br>(SIZE(4)) | UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [37]. It indicates the start time of the collecting period of the included <i>Usage Count UL</i> IE and <i>Usage Count DL</i> IE. |
+| >End Timestamp | M | | OCTET STRING<br>(SIZE(4)) | UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [37]. It indicates the end time of the collecting period of the included <i>Usage Count UL</i> IE and <i>Usage Count DL</i> IE. |
+| >Usage Count UL | M | | INTEGER (0..2 <sup>64</sup> -1) | The unit is: octets. |
+| >Usage Count DL | M | | INTEGER (0..2 <sup>64</sup> -1) | The unit is: octets. |
+
+| Range bound | Explanation |
+|--------------------|----------------------------------------------------|
+| maxnoofTimePeriods | Maximum no. of time reporting periods. Value is 2. |
+
+### 9.2.3.89 Maximum IP Rate
+
+This IE indicates the maximum aggregate data rate for integrity protected DRBs for a UE as defined in TS 38.300 [9].
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------------------------------|----------|-------|------------------------------------------|--------------------------------------------------------------------------------------------|
+| Maximum Integrity Protected Data Rate | M | | ENUMERATED<br>(64kbps, max UE rate, ...) | Defines the upper bound of the aggregate data rate of user plane integrity protected data. |
+
+### 9.2.3.90 UL Forwarding
+
+This element indicates a proposal for forwarding of uplink packets.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------------------------|-----------------------|
+| UL Forwarding | M | | ENUMERATED (UL forwarding proposed, ...) | |
+
+### 9.2.3.91 UE Radio Capability for Paging
+
+This IE contains paging specific UE Radio Capability information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------|
+| UE Radio Capability for Paging of NR | O | | OCTET STRING | Includes the RRC <i>UERadioPagingInformation</i> message as defined in TS 38.331 [10]. |
+| UE Radio Capability for Paging of E-UTRA | O | | OCTET STRING | Includes the RRC <i>UERadioPagingInformation</i> message as defined in TS 36.331 [14]. |
+
+### 9.2.3.92 Common Network Instance
+
+This IE provides the common network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [7] in a format common with 5GC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|
+| Common Network Instance | M | | OCTET STRING | The octets of OCTET STRING are encoded as the Network Instance field of the <i>Network Instance</i> IE specified in TS 29.244 [45] |
+
+### 9.2.3.93 Default DRB Allowed
+
+This IE is used to indicate whether the SN is allowed to configure the default DRB for a PDU session or not.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-------------------------------|-----------------------|
+| Default DRB Allowed | M | | ENUMERATED (true, false, ...) | |
+
+### 9.2.3.94 Split Session Indicator
+
+This IE indicates whether admitting the requested resources results in a split PDU session.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-------------------------|-----------------------|
+| Split Session Indicator | M | | ENUMERATED (split, ...) | |
+
+### 9.2.3.95 UL Forwarding Proposal
+
+This IE indicates a proposal for forwarding of uplink packets.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-----------------------------------------------|-----------------------|
+| UL Forwarding Proposal | M | | ENUMERATED (UL data forwarding proposed, ...) | |
+
+### 9.2.3.96 TNL Configuration Info
+
+This IE is used for signalling IP addresses of IPSEC endpoints used for establishment of IPSEC tunnels.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------------|----------|---------------------|----------------------------------|---------------------------------------------------|
+| Extended UP Transport Layer Addresses To Add List | | 0..1 | | |
+| >Extended UP Transport Layer Addresses To Add Item | | 1..<maxnoofExtTLAs> | | |
+| >>IP-Sec Transport Layer Address | M | | Transport Layer Address 9.2.3.29 | Transport Layer Addresses for IP-Sec endpoint. |
+| >>>GTP Transport Layer Addresses To Add List | | 0..1 | | |
+| >>>>GTP Transport Layer Addresses To Add Item | | 1..<maxnoofGPTTLAs> | | |
+| >>>>>GTP Transport Layer Address Info | M | | Transport Layer Address 9.3.2.29 | GTP Transport Layer Addresses for GTP end-points. |
+| Extended UP Transport Layer Addresses To Remove List | | 0..1 | | |
+| >Extended UP Transport Layer Addresses To Remove Item | | 0..<maxnoofExtTLAs> | | |
+| >>IP-Sec Transport Layer Address | O | | Transport Layer Address 9.2.3.29 | Transport Layer Addresses for IP-Sec endpoint. |
+| >>>GTP Transport Layer Addresses To Remove List | | 0..1 | | |
+| >>>>GTP Transport Layer Addresses To Remove Item | | 1..<maxnoofGPTTLAs> | | |
+| >>>>>GTP Transport Layer Address Info | M | | Transport Layer Address 9.2.3.2 | GTP Transport Layer Addresses for GTP end-points. |
+
+| Range bound | Explanation |
+|----------------|--------------------------------------------------------------------------------|
+| maxnoofExtTLAs | Maximum no. of Extended Transport Layer Addresses in the message. Value is 16. |
+| maxnoofGPTTLAs | Maximum no. of GTP Transport Layer Addresses for a GTP end-point in |
+
+the message. Value is 16.
+
+### 9.2.3.97 NG-RAN Trace ID
+
+This IE defines the NG-RAN Trace ID.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NG-RAN Trace ID | M | | OCTET STRING (SIZE(8)) | This IE is composed of the following: Trace Reference defined in TS 32.422 [23] (leftmost 6 octets, with PLMN information encoded as in 9.2.2.4), and Trace Recording Session Reference defined in TS 32.422 [23] (last 2 octets). |
+
+### 9.2.3.98 Non-GBR Resources Offered
+
+This IE indicates whether the MCG offers non-GBR resources for non-GBR QoS flows of the PDU Session Resource.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|------------------------|-----------------------|
+| Non-GBR Resources Offered | M | | ENUMERATED (true, ...) | |
+
+### 9.2.3.99 Extended RAT Restriction Information
+
+This element provides RAT restrictions as specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Primary RAT Restriction | M | | BIT STRING {<br>e-UTRA (0),<br>nR (1), nR-unlicensed (2),<br>nR-LEO (3),<br>nR-MEO (4),<br>nR-GEO (5),<br>nR-OTHERSAT (6)}<br>(SIZE(8, ...)) | Each position in the bitmap represents a Primary RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bit 7 reserved for future use. The Primary RAT is the RAT used in the access cell, or target cell. |
+| Secondary RAT Restriction | M | | BIT STRING {<br>e-UTRA (0),<br>nR (1), e-UTRA-unlicensed (2),<br>nR-unlicensed (3)}<br>(SIZE(8, ...)) | Each position in the bitmap represents a Secondary RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bits 4-7 reserved for future use. A Secondary RAT is a RAT, distinct from the UE's primary RAT, used in any cell serving the UE excluding the PCell. |
+
+### 9.2.3.100 5GC Mobility Restriction List Container
+
+This IE contains the *Mobility Restriction List* IE specified in TS 38.413 [5] as received by the NG-RAN from the 5GC.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5GC Mobility Restriction List Container | M | | OCTET STRING | The octets of the OCTET STRING are encoded according to the specifications of the <i>Mobility Restriction List</i> IE specified in TS 38.413 [5]. |
+
+### 9.2.3.101 Maximum Number of CHO Preparations
+
+This IE indicates the maximum number of concurrently prepared CHO candidate cells for a UE at a candidate target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|-----------------------|-----------------------|
+| Maximum Number of CHO Preparations | M | | INTEGER (1..8, ...) | |
+
+### 9.2.3.102 Alternative QoS Parameters Set List
+
+This IE contains alternative sets of QoS parameters which the NG-RAN node can indicate to be fulfilled when notification control is enabled and it cannot fulfil the requested list of QoS parameters.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------------------------|-----------------------|-----------------------|
+| <b>Alternative QoS Parameters Set Item</b> | | 1..<maxnoofQoSparaSets> | | |
+| >Alternative QoS Parameters Set Index | M | | 9.2.3.103 | |
+| >Guaranteed Flow Bit Rate Downlink | O | | Bit Rate 9.2.3.4 | |
+| >Guaranteed Flow Bit Rate Uplink | O | | Bit Rate 9.2.3.4 | |
+| >Packet Delay Budget | O | | 9.2.3.12 | |
+| >Packet Error Rate | O | | 9.2.3.13 | |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------------------------------------------------|
+| maxnoofQoSparaSets | Maximum no. of alternative sets of QoS Parameters allowed for the QoS profile. Value is 8. |
+
+### 9.2.3.103 Alternative QoS Parameters Set Index
+
+This IE indicates the QoS parameters set which can currently be fulfilled.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------|
+| Alternative QoS Parameters Set Index | M | | INTEGER (1..8, ...) | Indicates the index of the item within the <i>Alternative QoS Parameters Set List</i> IE corresponding to the currently |
+
+| | | | | |
+|--|--|--|--|-------------------------------------------|
+| | | | | fulfilled alternative QoS parameters set. |
+|--|--|--|--|-------------------------------------------|
+
+### 9.2.3.104 Alternative QoS Parameters Set Notify Index
+
+This IE indicates the QoS parameters set which can currently be fulfilled.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Alternative QoS Parameters Set Notify Index | M | | INTEGER (0..8, ...) | Indicates the index of the item within the <i>Alternative QoS Parameters Set List</i> IE corresponding to the currently fulfilled alternative QoS parameters set. Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative QoS parameters set. |
+
+### 9.2.3.105 NR V2X Services Authorized
+
+This IE provides information on the authorization status of the UE to use the NR sidelink for V2X services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------------------------|---------------------------------------------------------|
+| Vehicle UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Vehicle UE |
+| Pedestrian UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Pedestrian UE |
+
+### 9.2.3.106 LTE V2X Services Authorized
+
+This IE provides information on the authorization status of the UE to use the LTE sidelink for V2X services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|----------------------------------------------|---------------------------------------------------------|
+| Vehicle UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Vehicle UE |
+| Pedestrian UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Pedestrian UE |
+
+### 9.2.3.107 NR UE Sidelink Aggregate Maximum Bit Rate
+
+This IE provides information on the Aggregate Maximum Bitrate of the UE's sidelink communication.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------|
+| NR UE Sidelink Aggregate Maximum Bit Rate | M | | Bit Rate 9.2.3.4 | Value 0 shall be considered as a logical error by the receiving NG-RAN node. |
+
+### 9.2.3.108 LTE UE Sidelink Aggregate Maximum Bit Rate
+
+This IE provides information on the Aggregate Maximum Bitrate of the UE's sidelink communication for LTE V2X services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------|
+| LTE UE Sidelink Aggregate Maximum Bit Rate | M | | Bit Rate<br>9.2.3.4 | Value 0 shall be considered as a logical error by the receiving NG-RAN node. |
+
+### 9.2.3.109 PC5 QoS Parameters
+
+This IE provides information on the PC5 QoS parameters of the UE's sidelink communication for NR PC5.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------|
+| <b>PC5 QoS Flow List</b> | | 1 | | |
+| > <b>PC5 QoS Flow Item</b> | | 1..<maxnoofPC5QoSFlows> | | |
+| >>PQI | M | | INTEGER (0..255, ...) | PQI is a special 5QI as specified in TS 23.501 [7]. |
+| >> <b>PC5 Flow Bit Rates</b> | O | | | Only applies for GBR QoS Flows. |
+| >>>Guaranteed Flow Bit Rate | M | | Bit Rate<br>9.2.3.4 | Guaranteed Bit Rate for the PC5 QoS flow. Details in TS 23.501 [7]. |
+| >>>Maximum Flow Bit Rate | M | | Bit Rate<br>9.2.3.4 | Maximum Bit Rate for the PC5 QoS flow. Details in TS 23.501 [7]. |
+| >>Range | O | | ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...) | Only applies for groupcast. |
+| PC5 Link Aggregate Bit Rates | O | | Bit Rate<br>9.2.3.4 | Only applies for non-GBR QoS Flows. |
+
+| Range bound | Explanation |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <i>maxnoofPC5QoSFlows</i> | Maximum no. of PC5 QoS flows allowed towards one UE. Value is 2048.<br>NOTE: ASN.1 value definition of the <i>maxnoofPC5QoSFlows</i> is 2064. The size of the PC5 QoS Flow List shall not exceed 2048 items. |
+
+### 9.2.3.110 UE History Information from the UE
+
+This IE contains information about mobility history report for a UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------|
+| CHOICE <i>UE History Information from the UE</i> | M | | | |
+| > <i>NR</i> | | | | |
+| >>NR Mobility History Report | M | | OCTET STRING | <i>Includes the VisitedCellInfoList IE provided in the</i> |
+
+| | | | | |
+|--|--|--|--|-------------------------------------------------------------|
+| | | | | UEInformationResponse message as defined in TS 38.331 [10]. |
+|--|--|--|--|-------------------------------------------------------------|
+
+### 9.2.3.111 RLC Duplication Information
+
+This IE indicates the RLC duplication configuration in case that the indicated DRB is configured with more than two RLC entities as specified in TS 38.331 [10].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|-------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>RLC Activation State List</b> | | 1 | | |
+| >RLC Activation State Items | | 1 .. < maxnoofRLCDuplicationstate > | | This IE indicates information on the initial secondary RLC activation state of UL PDCP duplication. Each position in the list represents a secondary RLC entity in ascending order by the LCH ID in the order of MCG and SCG. |
+| >>Duplication State | M | | ENUMERATED (Active, Inactive, ...) | |
+| Primary RLC Indication | O | | ENUMERATED ( True, False, ...) | This IE is present when DC based PDCP duplication is configured. This IE indicates whether the primary RLC entity located at the assisting node. |
+
+| Range bound | Explanation |
+|----------------------------|---------------------------------------------------|
+| maxnoofRLCDuplicationstate | Maximum no of Secondary RLC entities. Value is 3. |
+
+### 9.2.3.112 Redundant PDU Session Information
+
+This IE provides Redundancy information to be applied to a PDU Session.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------|----------|-------|--------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RSN | M | | ENUMERATED (v1, v2, ...) | | – | |
+| PDU Session Pair ID | O | | INTEGER (0..255, ...) | as defined in TS 23.501 [9]. This IE is not used in the response message. If received, the M-NG-RAN node shall ignore it. | YES | ignore |
+
+### 9.2.3.113 Extended Packet Delay Budget
+
+This IE indicates the Packet Delay Budget for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and | Semantics description |
+|---------------|----------|-------|-------------|-----------------------|
+|---------------|----------|-------|-------------|-----------------------|
+
+| | | | <b>reference</b> | |
+|------------------------------|---|--|-------------------------------------------|-------------------------------------------------------------------------------------------|
+| Extended Packet Delay Budget | M | | INTEGER<br>(0..65535, ..., 65536..109999) | Upper bound value for the delay that a packet may experience expressed in unit of 0.01ms. |
+
+### 9.2.3.114 TSC Traffic Characteristics
+
+This IE provides the traffic characteristics of TSC QoS flows.
+
+| <b>IE/Group Name</b> | <b>Presence</b> | <b>Range</b> | <b>IE type and reference</b> | <b>Semantics description</b> |
+|-------------------------------------|-----------------|--------------|-----------------------------------------|------------------------------|
+| TSC Assistance Information Downlink | O | | TSC Assistance Information<br>9.2.3.115 | |
+| TSC Assistance Information Uplink | O | | TSC Assistance Information<br>9.2.3.115 | |
+
+### 9.2.3.115 TSC Assistance Information
+
+This IE provides the TSC assistance information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [7]).
+
+| <b>IE/Group Name</b> | <b>Presence</b> | <b>Range</b> | <b>IE type and reference</b> | <b>Semantics description</b> | <b>Criticality</b> | <b>Assigned Criticality</b> |
+|-------------------------------|-----------------|--------------|------------------------------|---------------------------------------------------|--------------------|-----------------------------|
+| Periodicity | M | | 9.2.3.116 | Periodicity as specified in TS 23.501 [7]. | – | |
+| Burst Arrival Time | O | | 9.2.3.117 | Burst Arrival Time as specified in TS 23.501 [7]. | – | |
+| Survival Time | O | | 9.2.3.152 | | YES | ignore |
+| Capability for BAT Adaptation | O | | ENUMERATED<br>(true, ...) | | YES | ignore |
+| N6 Jitter Information | O | | 9.2.3.204 | | YES | ignore |
+
+### 9.2.3.116 Periodicity
+
+This IE indicates the Periodicity of the TSC QoS flow as defined in TS 23.501 [7].
+
+| <b>IE/Group Name</b> | <b>Presence</b> | <b>Range</b> | <b>IE type and reference</b> | <b>Semantics description</b> |
+|----------------------|-----------------|--------------|------------------------------|-----------------------------------------|
+| Periodicity | M | | INTEGER<br>(0..640000, ...) | Periodicity expressed in units of 1 us. |
+
+### 9.2.3.117 Burst Arrival Time
+
+This IE indicates the Burst Arrival Time of the TSC QoS flow as defined in TS 23.501 [7].
+
+| <b>IE/Group Name</b> | <b>Presence</b> | <b>Range</b> | <b>IE type and reference</b> | <b>Semantics description</b> |
+|----------------------|-----------------|--------------|------------------------------|------------------------------------------------------------------------------------------------------|
+| Burst Arrival Time | M | | OCTET STRING | Encoded in the same format as the <i>ReferenceTime</i> IE as defined in TS 38.331 [10]. The value is |
+
+| | | | | |
+|--|--|--|--|------------------------------|
+| | | | | provided with 1 us accuracy. |
+|--|--|--|--|------------------------------|
+
+### 9.2.3.118 Redundant QoS Flow Indicator
+
+This IE provides the Redundant QoS Flow Indicator for a QoS flows as specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Redundant QoS Flow Indicator | M | | ENUMERATED (true, false) | This IE indicates if this QoS flow is requested for the redundant transmission. Value "true" indicates that redundant transmission is requested for this QoS flow. Value "false" indicates that redundant transmission is requested to be stopped if started. |
+
+### 9.2.3.119 NPN Mobility Information
+
+This information element indicates the access restrictions related to an NPN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------------------|----------|---------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| CHOICE <i>NPN Mobility Information</i> | M | | | | – | |
+| > <i>SNPN Mobility Information</i> | | | | | | |
+| >>Serving NID | M | | NID 9.2.2.65 | | – | |
+| >>Equivalent SNPNs | | 0..<maxno ofESNPNs> | | Allowed SNPNs in addition to Serving SNPN. This list corresponds to the list of "equivalent SNPNs" as defined in TS 24.501 [30]. This list is part of the roaming restriction information. Roaming restrictions apply to SNPNs other than the Serving SNPN and Equivalent SNPNs. | YES | reject |
+| >>>PLMN Identity | M | | 9.2.2.4 | | – | |
+| >>>NID | M | | 9.2.2.65 | | – | |
+| > <i>PNI-NPN Mobility Information</i> | | | | | | |
+| >>Allowed PNI-NPN ID List | M | | 9.2.3.120 | | – | |
+
+| Range bound | Explanation |
+|--------------|-----------------------------------------------|
+| maxnoofESPNs | Maximum no. of equivalent ESPNs. Value is 15. |
+
+### 9.2.3.120 Allowed PNI-NPN ID List
+
+This IE contains information on allowed UE mobility in PNI-NPN including allowed PNI-NPNs and whether the UE is allowed to access non-CAG cells for each PLMN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------|----------|-------------------------|-----------------------|-----------------------|
+| <b>Allowed PNI-NPN ID List</b> | | 1..<maxnoofEPLMNs+1> | | |
+| >PLMN Identity | M | | 9.2.2.4 | |
+| >PNI-NPN Restricted Information | M | | 9.2.3.123 | |
+| >Allowed CAG-Identifier List per PLMN | | 1..<maxnoofCAGsperPLMN> | | |
+| >>CAG-Identifier | M | | 9.2.2.66 | |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------------------------------------|
+| maxnoofEPLMNs+1 | Maximum no. of equivalent PLMNs plus one serving PLMN. Value is 16. |
+| maxnoofCAGsperPLMN | Maximum number of CAGs per PLMN in UE's Allowed PNI-NPN ID List. Value is 256. |
+
+### 9.2.3.121 NPN Paging Assistance Information
+
+This IE contains NPN Paging Assistance Information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>NPN Mobility Information</i> | M | | | |
+| > <i>PNI-NPN Information</i> | | | | |
+| >>Allowed PNI-NPN ID List | M | | 9.2.3.120 | |
+
+### 9.2.3.122 Void
+
+Void.
+
+### 9.2.3.123 PNI-NPN Restricted Information
+
+This IE indicates whether the UE is allowed to access cells that support PNI-NPNs for a PLMN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|----------------------------------------------|---------------------------------------------------------------------------------------------------------|
+| PNI-NPN Restricted Information | M | | ENUMERATED (restricted, not-restricted, ...) | If set to "restricted", the IE indicates that the UE is not allowed to access non-CAG cells for a PLMN. |
+
+### 9.2.3.124 URI
+
+This IE is defined to contain a URI address.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-------------------------------------------------------|
+| URI | M | | VisibleString | String representing URI (Uniform Resource Identifier) |
+
+### 9.2.3.125 MDT Configuration
+
+The IE defines the MDT configuration parameters.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|-----------------------|
+| MDT Configuration-NR | O | | 9.2.3.126 | |
+| MDT Configuration-EUTRA | O | | 9.2.3.127 | |
+
+### 9.2.3.126 MDT Configuration-NR
+
+The IE defines the MDT configuration parameters of NR.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|---------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| MDT Activation | M | | ENUMERATED<br>(Immediate MDT only, Immediate MDT and Trace, Logged MDT only, ...) | | – | |
+| CHOICE <i>Area Scope of MDT-NR</i> | O | | | | – | |
+| >Cell based | | | | If <i>PNI-NPN Area Scope of MDT</i> IE is present, this IE covers non-CAG cells only, where non-CAG cells refer to cells that only provide public access. | | |
+| >>Cell ID List for MDT-NR | | 1 ..<br><maxnoof<br>CellIDforM<br>DT> | | | – | |
+| >>>NR CGI | M | | 9.2.2.7 | | – | |
+| >TA based | | | | If <i>PNI-NPN Area Scope of MDT</i> IE is present, this IE covers non-CAG cells only, where non-CAG cells refer to cells that only provide | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------|-----------------------------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | public access. | | |
+| >>TA List for MDT | | 1 ..<br><maxnoof<br>TAforMDT<br>> | | | – | |
+| >>>TAC | M | | OCTET STRING<br>(SIZE (3)) | The TAI is derived using the current serving PLMN. | – | |
+| >TAI based | | | | If PNI-NPN Area Scope of MDT IE is present, it covers non-CAG cells only, where non-CAG cells refer to cells that only provide public access. | | |
+| >>TAI List for MDT | | 1 | | | – | |
+| >>>TAI List for MDT Item | | 1 ..<br><maxnoof<br>TAforMDT<br>> | | | – | |
+| >>>>PLMN Identity | M | | 9.2.2.4 | | – | |
+| >>>>TAC | M | | 9.2.2.5 | | – | |
+| >PNI-NPN based | | | | | YES | ignore |
+| >>CAG List for MDT | | 1..<maxno<br>ofCAGforM<br>DT> | | | – | |
+| >>>PLMN ID | M | | 9.2.2.4 | | – | |
+| >>>CAG-Identifier | M | | 9.2.2.66 | | – | |
+| >SNPN Cell Based MDT | | | | | YES | ignore |
+| >>SNPN Cell ID List for MDT | | 1..<maxno<br>ofCellIDfor<br>MDT> | | | – | |
+| >>>NR CGI | M | | 9.2.2.7 | | – | - |
+| >>>NID | M | | 9.2.2.65 | Identifies an SNPN together with the PLMN Identity in the NR CGI IE. | – | - |
+| >SNPN TAI Based MDT | | | | | YES | ignore |
+| >>SNPN TAI List | | 1..<maxno<br>ofTAforMD<br>T> | | | – | - |
+| >>>PLMN Identity | M | | 9.2.2.4 | | – | - |
+| >>>TAC | M | | 9.2.2.5 | | – | - |
+| >>>NID | M | | 9.2.2.65 | Identifies an SNPN together with the PLMN Identity IE. | – | - |
+| >SNPN-ID Based MDT | | | | | YES | ignore |
+| >>MDT SNPN List | | 1..<maxno<br>ofMDTSN | | | – | - |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|----------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | <i>PNs></i> | | | | |
+| >>>PLMN Identity | M | | 9.2.2.4 | | – | - |
+| >>>NID | M | | 9.2.2.65 | Identifies an SNPN together with the <i>PLMN Identity</i> IE. | – | - |
+| CHOICE <i>MDT Mode</i> | M | | | | – | |
+| > <i>Immediate MDT-NR</i> | | | | | | |
+| >>Measurements to Activate | M | | BITSTRING (SIZE(8)) | Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [43].<br>First Bit = M1,<br>Second Bit= M2,<br>Fourth Bit = M4,<br>Fifth Bit = M5,<br>Sixth Bit = logging of M1 from event triggered measurement reports according to existing RRM configuration,<br>Seventh Bit = M6,<br>Eighth Bit = M7.<br>Value "1" indicates "activate" and value "0" indicates "do not activate".<br>This version of the specification does not use bits 3. | – | |
+| >>M1 Configuration | C-ifM1 | | 9.2.3.128 | | – | |
+| >>M4 Configuration | C-ifM4 | | 9.2.3.129 | | – | |
+| >>M5 Configuration | C-ifM5 | | 9.2.3.130 | | – | |
+| >>MDT Location Information | O | | BITSTRING(SIZE(8)) | Each position in the bitmap represents requested location information as defined in TS 37.320 [43].<br>First Bit = GNSS<br>Other bits are reserved for future use and are ignored if received.<br>Value "1" indicates "activate" and value "0" indicates "do not activate". | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | The eNB shall ignore the first bit unless the <i>Measurements to Activate</i> IE has the first bit or the sixth bit set to "1". | | |
+| >>M6 Configuration | C-ifM6 | | 9.2.3.131 | | – | |
+| >>M7 Configuration | C-ifM7 | | 9.2.3.132 | | – | |
+| >>Bluetooth Measurement Configuration | O | | 9.2.3.11 | | – | |
+| >>WLAN Measurement Configuration | O | | 9.2.3.12 | | – | |
+| >>Sensor Measurement Configuration | O | | 9.2.3.136 | | – | |
+| >Logged MDT-NR | | | | | | |
+| >>Logging interval | M | | ENUMERATED (ms320, ms640, ms1280, ms2560, ms5120, ms10240, ms20480, ms30720, ms40960, ms61440, infinity, ...) | Corresponds to information provided in the <i>LoggingInterval</i> IE as defined in TS 38.331 [10]. The value "infinity" represents one shot logging, i.e., only one log per event in the logged MDT report. | – | |
+| >>Logging duration | M | | ENUMERATED (10, 20, 40, 60, 90, 120) | Corresponds to information provided in the <i>LoggingDuration</i> IE as defined in TS 38.331 [10]. Unit: [minute]. | – | |
+| >>CHOICE <i>Report Type</i> | M | | | | – | |
+| >>> <i>Periodical</i> | | | | | | |
+| >>> <i>Event Triggered</i> | | | | | – | |
+| >>>>Logged Event Trigger Config | M | | 9.2.3.137 | | – | |
+| >>Bluetooth Measurement Configuration | O | | 9.2.3.134 | | – | |
+| >>WLAN Measurement Configuration | O | | 9.2.3.135 | | – | |
+| >>Sensor Measurement Configuration | O | | 9.2.3.136 | | – | |
+| >>Area Scope of | O | | 9.2.3.140 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Neighbour Cells | | | | | | |
+| >>Early Measurement | O | | ENUMERATED (true, ...) | This IE indicates whether the UE is allowed to log measurements on early measurement related frequencies in logged MDT as specified in TS 38.331 [10]. | – | |
+| Signalling based MDT PLMN List | O | | MDT PLMN List 9.2.3.133 | | – | |
+| PNI-NPN Area Scope of MDT | O | | 9.2.3.191 | | YES | ignore |
+
+| Range bound | Explanation |
+|---------------------|------------------------------------------------------------|
+| maxnoofCellIDforMDT | Maximum no. of Cell ID subject for MDT scope. Value is 32. |
+| maxnoofTAforMDT | Maximum no. of TA subject for MDT scope. Value is 8. |
+| maxnoofCAGforMDT | Maximum no. of CAG IDs for MDT scope. Value is 256. |
+| maxnoofMDTSNPNs | Maximum no. of SNPNS in the MDT SNPNS list. Value is 16. |
+
+| Condition | Explanation |
+|-----------|----------------------------------------------------------------------------------------------------|
+| ifM1 | This IE shall be present if the <i>Measurements to Activate</i> IE has the first bit set to "1". |
+| ifM4 | This IE shall be present if the <i>Measurements to Activate</i> IE has the fourth bit set to "1". |
+| ifM5 | This IE shall be present if the <i>Measurements to Activate</i> IE has the fifth bit set to "1". |
+| ifM6 | This IE shall be present if the <i>Measurements to Activate</i> IE has the seventh bit set to "1". |
+| ifM7 | This IE shall be present if the <i>Measurements to Activate</i> IE has the eighth bit set to "1". |
+
+### 9.2.3.127 MDT Configuration-EUTRA
+
+The IE defines the MDT configuration parameters of EUTRA.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|----------------------------|--------------------------------------------------------------------------------|-----------------------|
+| MDT Activation | M | | ENUMERATED(Im mediate MDT only, Immediate MDT and Trace, Logged MDT only, ...) | |
+| CHOICE Area Scope of MDT-E-UTRA | O | | | |
+| >Cell based | | | | |
+| >>Cell ID List for MDT | | 1 .. <maxnoofCellIDforMDT> | | |
+| >>>E-UTRA CGI | M | | 9.2.2.8 | |
+
+| | | | | |
+|--------------------------------|---|---------------------------|----------------------------|----------------------------------------------------|
+| >TA based | | | | |
+| >>TA List for MDT | | 1 ..<br><maxnoofTAforMDT> | | |
+| >>>TAC | M | | OCTET STRING<br>(SIZE (3)) | The TAI is derived using the current serving PLMN. |
+| >TAI based | | | | |
+| >>TAI List for MDT | | 1 | | |
+| >>>TAI List for MDT Item | | 1 ..<br><maxnoofTAforMDT> | | |
+| >>>>PLMN Identity | M | | 9.2.2.4 | |
+| >>>>TAC | M | | 9.2.2.5 | |
+| MDT Mode E-UTRA | M | | OCTET STRING | MDTMode IE defined in TS 36.413 [31]. |
+| Signalling based MDT PLMN List | O | | MDT PLMN List<br>9.2.3.133 | |
+
+| Range bound | Explanation |
+|---------------------|------------------------------------------------------------|
+| maxnoofCellIDforMDT | Maximum no. of Cell ID subject for MDT scope. Value is 32. |
+| maxnoofTAforMDT | Maximum no. of TA subject for MDT scope. Value is 8. |
+
+### 9.2.3.128 M1 Configuration
+
+This IE defines the parameters for M1 measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------|---------------------|-------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------|
+| M1 Reporting Trigger | M | | ENUMERATED<br>(periodic, A2event-triggered, A2event-triggered periodic, ...) | | – | |
+| M1 Threshold Event A2 | C-<br>ifM1A2trigger | | | Included in case of event-triggered or event-triggered periodic reporting for measurement M1. | – | |
+| >CHOICE Threshold | M | | | | – | |
+| >>RSRP | | | | | | |
+| >>>Threshold RSRP | M | | INTEGER<br>(0..127) | Corresponds to information provided in the <i>RSRP-Range</i> IE as defined in TS 38.331 [10]. | – | |
+| >>RSRQ | | | | | | |
+| >>>Threshold RSRQ | M | | INTEGER<br>(0..127) | Corresponds to information provided in the <i>RSRQ-Range</i> IE as defined in TS 38.331 [10]. | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------|---------------------------|-------|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>SINR | | | | | | |
+| >>>Threshold SINR | M | | INTEGER (0..127) | Corresponds to information provided in the <i>SINR-Range</i> IE as defined in TS 38.331 [10]. | – | |
+| <b>M1 Periodic reporting</b> | C-<br>ifperiodic<br>MDT | | | Included in case of periodic or event-triggered periodic reporting for measurement M1. | – | |
+| >Report interval | M | | ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60) | Corresponds to information provided in the <i>ReportInterval</i> IE as defined in TS 38.331 [10]. The value min60 is not used in the specification. | – | |
+| >Report amount | M | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity) | Corresponds to information provided in the <i>reportAmount</i> as defined in TS 38.331 [10] and represents the number of reports. | – | |
+| >Extended Report interval | O | | ENUMERATED (ms20480, ms40960,...) | This IE is the extension of <i>Report interval</i> IE and corresponds to information provided in the <i>ReportInterval</i> IE as defined in TS 38.331 [10]. If this IE is present, the <i>Report interval</i> IE is ignored. | YES | ignore |
+| Include Beam Measurements Indication | O | | ENUMERATED (true, ...) | To configure whether the UE should include beam level measurements. | YES | ignore |
+| <b>Beam Measurements Report Configuration</b> | C-<br>ifM1Beam<br>MeasInd | | | | YES | ignore |
+| >Beam Measurements Report Quantity | O | | | This IE indicates the beam measurement quantity and corresponds to information provided in the <i>MeasReportQuant</i> | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | <i>ity</i> IE as defined in TS 38.331 [10]. | | |
+| >>RSRP | M | | ENUMERATED (true, ...) | | – | |
+| >>RSRQ | M | | ENUMERATED (true, ...) | | – | |
+| >>SINR | M | | ENUMERATED (true, ...) | | – | |
+| >MaxNrofRS-IndexesTo Report | O | | INTEGER (1..64, ...) | Indicates the max number of beam measurements to be reported and corresponds to information provided in the <i>maxNrofRS-IndexesToReport</i> as defined in TS 38.331 [10]. | – | |
+
+| Condition | Explanation |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ifM1A2trigger | This IE shall be present if the <i>Measurements to Activate</i> IE has the first bit set to "1" and the <i>M1 Reporting Trigger</i> IE is set to "A2event-triggered" or to "A2event-triggered periodic". |
+| ifperiodicMDT | This IE shall be present if the <i>M1 Reporting Trigger</i> IE is set to "periodic", or to "A2event-triggered periodic". |
+| ifM1BeamMeasInd | This IE shall be present if the <i>Include Beam Measurements Indication</i> IE is set to "true". |
+
+### 9.2.3.129 M4 Configuration
+
+This IE defines the parameters for M4 measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|--------------------------------------------------------------|-----------------------|-------------|----------------------|
+| M4 Collection Period | M | | ENUMERATED (ms1024, ms2048, ms5120, ms10240, min1, ...) | | – | |
+| M4 Links to log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | – | |
+| M4 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity ...) | Number of reports. | YES | ignore |
+
+### 9.2.3.130 M5 Configuration
+
+This IE defines the parameters for M5 measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|--------------------------------------------------------------|-----------------------|-------------|----------------------|
+| M5 Collection Period | M | | ENUMERATED (ms1024, ms2048, ms5120, ms10240, min1, ...) | | – | |
+| M5 Links to log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | – | |
+| M5 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity ...) | Number of reports. | YES | ignore |
+
+### 9.2.3.131 M6 Configuration
+
+This IE defines the parameters for M6 measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------|
+| M6 Report Interval | M | | ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1, min6, min12, min30, ...) | | – | |
+| M6 Links to log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | – | |
+| M6 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity ...) | Number of reports. | YES | ignore |
+| Excess Packet Delay Threshold Configuration | O | | 9.2.3.171 | | YES | ignore |
+
+### 9.2.3.132 M7 Configuration
+
+This IE defines the parameters for M7 measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| M7 Collection Period | M | | INTEGER | Unit: minutes | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------|----------|-------|--------------------------------------------------------------|-----------------------|-------------|----------------------|
+| | | | (1..60, ...) | | | |
+| M7 Links to log | M | | ENUMERATED (uplink, downlink, both-uplink-and-downlink, ...) | | – | |
+| M7 Report Amount | O | | ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity ...) | Number of reports. | YES | ignore |
+
+### 9.2.3.133 MDT PLMN List
+
+The purpose of the *MDT PLMN List* IE is to provide the list of PLMN allowed for MDT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|----------------------|-----------------------|-----------------------|
+| <b>MDT PLMN List</b> | | 1..<maxnoofMDTPLMNs> | | |
+| >PLMN Identity | M | | 9.2.2.4 | |
+
+| Range bound | Explanation |
+|-----------------|---------------------------------------------------------|
+| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. |
+
+### 9.2.3.134 Bluetooth Measurement Configuration
+
+This IE defines the parameters for Bluetooth measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------------|----------|-----------------------------|------------------------------|--------------------------------------------------------------------------------------------|
+| Bluetooth Measurement Configuration | M | | ENUMERATED (Setup, ...) | |
+| <b>Bluetooth Measurement Configuration Name List</b> | | 0..1 | | This IE is present if the <i>Bluetooth Measurement Configuration</i> IE is set to "Setup". |
+| >Bluetooth Measurement Configuration Name Item IEs | | 1 .. <maxnoofBluetoothName> | | |
+| >>Bluetooth Measurement Configuration Name | M | | OCTET STRING (SIZE (1..248)) | |
+| BT RSSI | O | | ENUMERATED (True, ...) | In case of Immediate MDT, it corresponds to M8 measurement as defined in 37.320 [43]. |
+
+| Range bound | Explanation |
+|----------------------|--------------------------------------------------------------------------------------------|
+| maxnoofBluetoothName | Maximum no. of Bluetooth local name used for Bluetooth measurement collection. Value is 4. |
+
+### 9.2.3.135 WLAN Measurement Configuration
+
+This IE defines the parameters for WLAN measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------------|----------|------------------------|-----------------------------|---------------------------------------------------------------------------------------|
+| WLAN Measurement Configuration | M | | ENUMERATED (Setup, ...) | |
+| <b>WLAN Measurement Configuration Name List</b> | | 0..1 | | This IE is present if the <i>WLAN Measurement Configuration</i> IE is set to "Setup". |
+| > <b>WLAN Measurement Configuration Name Item IEs</b> | | 1 .. <maxnoofWLANName> | | |
+| >>WLAN Measurement Configuration Name | M | | OCTET STRING (SIZE (1..32)) | |
+| WLAN RSSI | O | | ENUMERATED (True, ...) | In case of Immediate MDT, it corresponds to M8 as defined in 37.320 [43]. |
+| WLAN RTT | O | | ENUMERATED (True, ...) | In case of Immediate MDT, it corresponds to M9 as defined in 37.320 [43]. |
+
+| Range bound | Explanation |
+|-----------------|----------------------------------------------------------------------------|
+| maxnoofWLANName | Maximum no. of WLAN SSID used for WLAN measurement collection. Value is 4. |
+
+### 9.2.3.136 Sensor Measurement Configuration
+
+This IE defines the parameters for Sensor measurement collection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------------------------------|----------|--------------------------|-------------------------|-----------------------|
+| Sensor Measurement Configuration | M | | ENUMERATED (Setup, ...) | |
+| <b>Sensor Measurement Configuration Name List</b> | | 0..1 | | |
+| > <b>Sensor Measurement Configuration Name Item IEs</b> | | 1 .. <maxnoofSensorName> | | |
+| >>Uncompensated Barometric Configuration | O | | ENUMERATED (True, ...) | |
+| >>UE Speed Configuration | O | | ENUMERATED (True, ...) | |
+| >>UE Orientation Configuration | O | | ENUMERATED (True, ...) | |
+
+| Range bound | Explanation |
+|-------------------|-------------------------------------------------------------------------------------|
+| maxnoofSensorName | Maximum no. of Sensor local name used for Sensor measurement collection. Value is 3 |
+
+### 9.2.3.137 Logged Event Trigger Config
+
+This IE configures with UE with specific events for triggering MDT configuration. Current specified event is based on
+
+out of coverage (OOC) detection.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>Event Type Trigger</i> | M | | | |
+| >Out of Coverage | | | | |
+| >>Out of Coverage Indication | | | ENUMERATED (true, ...) | |
+| >L1 Event | | | | |
+| >>CHOICE <i>L1 Event Threshold</i> | M | | | |
+| >>>RSRP | | | | |
+| >>>>Threshold RSRP | M | | INTEGER (0..127) | Corresponds to information provided in the <i>RSRP-Range</i> IE as defined in TS 38.331 [10]. |
+| >>>RSRQ | | | | |
+| >>>>Threshold RSRQ | M | | INTEGER (0..127) | Corresponds to information provided in the <i>RSRQ-Range</i> IE as defined in TS 38.331 [10]. |
+| >>Hysteresis | | | INTEGER (0..30) | This parameter is used within the entry and leave condition of an event triggered reporting condition and corresponds to information provided in the <i>Hysteresis</i> IE as defined in TS 38.331 [10]. |
+| >>Time to trigger | | | ENUMERATED (ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120) | Time during which specific criteria for the event needs to be met in order to trigger a measurement report. Corresponds to information provided in the <i>TimeToTrigger</i> IE as defined in TS 38.331 [10] |
+
+### 9.2.3.138 UE Radio Capability ID
+
+This IE contains UE Capability ID as defined in TS 23.003 [22].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|-----------------------|-----------------------|
+| UE Radio Capability ID | M | | OCTET STRING | |
+
+### 9.2.3.139 Extended Slice Support List
+
+This IE indicates a list of supported slices.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|---------------------------|-----------------------|-----------------------|
+| <b>Slice Support Item</b> | | 1..<maxnoofExtSliceItems> | | |
+| >S-NSSAI | M | | 9.2.3.21 | |
+
+| Range bound | Explanation |
+|----------------------|---------------------------------------------------------------|
+| maxnoofExtSliceItems | Maximum no. of signalled slice support items. Value is 65535. |
+
+### 9.2.3.140 Area Scope of Neighbour Cells
+
+This IE defines the area scope of neighbour cells for logged MDT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------|----------|----------------------------------|-----------------------|-----------------------|
+| <b>Area Scope of Neighbour Cells</b> | M | 1 ..<br><maxnoofFreqforMDT> | | |
+| >NR FreqInfo | M | | 9.2.2.19 | |
+| >PCI List for MDT | O | 1 ..<br><maxnoofNeighPCIforsMDT> | | |
+| >> NRPCI | M | | INTEGER (0..1007) | NR Physical Cell ID |
+
+| Range bound | Explanation |
+|------------------------|-------------------------------------------------------------------------|
+| maxnoofFreqforMDT | Maximum no. of Frequency Information subject for MDT scope. Value is 8. |
+| maxnoofNeighPCIforsMDT | Maximum no. of Neighbour cells subject for MDT scope. Value is 32. |
+
+### 9.2.3.141 Extended UE Identity Index Value
+
+This IE is used by the target NG-RAN node to calculate the Paging Frame and Paging Occasion as specified in TS 36.304 [34], the Paging Frame and Paging Occasion for eDRX and the UE\_ID based subgroup ID as specified in TS 38.304 [33].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|-------|-----------------------|-----------------------|
+| Extended UE Identity Index Value | M | | BIT STRING (SIZE(16)) | |
+
+### 9.2.3.142 E-UTRA Paging eDRX Information
+
+This IE indicates the E-UTRA Paging eDRX parameters for RRC\_IDLE as defined in TS 36.304 [34], if configured by higher layers.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| E-UTRA Paging eDRX Cycle | M | | ENUMERATED<br>(hfhalf, hf1, hf2, hf4, hf6, hf8, hf10, hf12, hf14, hf16, hf32, hf64, hf128, hf256, ...) | The DRX defined in TS 36.304 [34]. Unit: [number of hyperframes]. |
+| E-UTRA Paging Time Window | O | | ENUMERATED<br>(s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, ...) | Unit: [1.28 second]. |
+
+### 9.2.3.143 UE Specific DRX
+
+This IE indicates the UE specific paging cycle as defined in TS 36.304 [34] and 38.304 [33].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------|----------|-------|------------------------------------|-----------------------|
+| UE Specific DRX | M | | ENUMERATED (32, 64, 128, 256, ...) | Unit is radio frame. |
+
+### 9.2.3.144 QoS Mapping Information
+
+This IE indicates the DSCP and/or IPv6 Flow Label field(s) of IP packets sent in the corresponding GTP-U tunnel.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| DSCP | O | | BIT STRING (SIZE(6)) | |
+| Flow label | O | | BIT STRING (SIZE(20)) | |
+
+### 9.2.3.144a Hashed UE Identity Index Value
+
+This IE contains the 13 Most Significant Bits (MSBs) of the Hashed ID defined in TS 38.304 [33] or TS 36.304 [34].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|----------------------------|-----------------------|
+| Hashed UE Identity Index Value | M | | BIT STRING (SIZE(13, ...)) | |
+
+### 9.2.3.145 MRB ID
+
+This IE contains the MRB ID as specified in TS 38.401 [2].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| MRB ID | M | | INTEGER (1..512, ...) | |
+
+### 9.2.3.146 MBS Session ID
+
+This IE indicates the MBS Session ID uniquely identifies an MBS session.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-------------------------|---------------------------------------|
+| TMGI | M | | OCTET STRING (SIZE (6)) | Encoded as defined in TS 23.003 [22]. |
+| NID | O | | 9.2.2.65 | |
+
+### 9.2.3.147 MRB Progress Information
+
+This IE contains the MRB progress Information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>PDCP SN Status</i> | M | | | |
+| >12bits | | | | |
+| >>PDCP SN Length 12 | M | | INTEGER (0..4095) | |
+| >18bits | | | | |
+| >>PDCP SN Length 18 | M | | INTEGER (0..262143) | |
+
+### 9.2.3.148 MBS Area Session ID
+
+This IE indicates the Area Session ID for MBS Session with location dependent context.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|---------------------------|-----------------------|
+| MBS Area Session ID | M | | INTEGER (0 .. 65535, ...) | |
+
+### 9.2.3.149 MBS Service Area information
+
+This IE contains the MBS service area information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------------------------|-----------------------|-----------------------|
+| <b>MBS Service Area Cell List</b> | | 0..<maxnoofCellsforMBS> | | |
+| >NR CGI | M | | 9.2.2.7 | |
+| <b>MBS Service Area TAI List</b> | | 0..<maxnoofTAIforMBS> | | |
+| >PLMN Identity | M | | 9.2.2.4 | |
+| >TAC | M | | 9.2.2.5 | |
+
+| Range bound | Explanation |
+|--------------------|--------------------------------------------------------------------------|
+| maxnoofCellsforMBS | Maximum no. of cells allowed within one MBS Service Area. Value is 8192. |
+| maxnoofTAIforMBS | Maximum no. of TAs allowed within one MBS Service Area. Value is 1024. |
+
+### 9.2.3.150 MBS Service Area
+
+This IE contains the MBS service area.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------------------------|----------|---------------------------------------|-----------------------|-----------------------|
+| CHOICE <i>MBS Service Area</i> | M | | | |
+| >location independent | | | | |
+| >>MBS Service Area Information | M | | 9.2.3.149 | |
+| >location dependent | | | | |
+| >>> <b>MBS Service Area Information Location Dependent List</b> | | 1..<maxnoofMBSServiceAreaInformation> | | |
+| >>>MBS Area Session ID | M | | 9.2.3.148 | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-------|-----------------------|-----------------------|
+| >>>MBS Service Area Information | M | | 9.2.3.149 | |
+
+| Range bound | Explanation |
+|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| maxnoofMBSServiceAreaInformation | Maximum no. of MBS Service Area Information elements in the MBS Service Area Information LocationDependent List IE. Value is 256. |
+
+### 9.2.3.151 SCG UE History Information
+
+This IE contains information about the PSCells served by the secondary node in an active state.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------|----------|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------|
+| Last Visited PSCell List | | 0..<maxnoofPSCellsPerSN> | | List of cells configured as PSCells. Most recent PSCell related information is added to the top of the list. |
+| >Last Visited PSCell Information | M | | OCTET STRING | Defined in TS 38.413 [5] |
+
+| Range bound | Explanation |
+|---------------------|-------------------------------------------------------------------------------------------------------|
+| maxnoofPSCellsPerSN | Maximum number of last visited PSCell information records that can be reported in the IE. Value is 8. |
+
+### 9.2.3.152 Survival Time
+
+This IE provides the Survival Time for a TSC QoS flow (see TS 23.501 [7]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|------------------------------|-----------------------------|
+| Survival Time | M | | INTEGER<br>(0..1920000, ...) | Expressed in units of 1 us. |
+
+### 9.2.3.153 Time Synchronisation Assistance Information
+
+This IE indicates the 5G access stratum time distribution parameters as specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|-------------|-------|----------------------------------------|-----------------------------|-------------|----------------------|
+| Time Distribution indication | M | | ENUMERATED<br>(enabled, disabled, ...) | | – | |
+| Uu Time Synchronization Error Budget | C-ifEnabled | | INTEGER<br>(0..1000000, ...) | Expressed in units of 1 ns. | – | |
+| Clock Quality Reporting Control Information | O | | 9.2.3.189 | | YES | ignore |
+
+| Condition | Explanation |
+|-----------|----------------------------------------------------------------------------------|
+| ifEnabled | This IE shall be present if the <i>Time Distribution Indication</i> IE is set to |
+
+| | |
+|--|------------|
+| | "enabled". |
+|--|------------|
+
+### 9.2.3.154 SCG Activation Request
+
+This IE indicates whether the SCG resources are required to be activated or deactivated.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------|----------|-------|------------------------------------------------------|-----------------------|
+| SCG Activation Request | M | | ENUMERATED<br>(Activate SCG,<br>Deactivate SCG, ...) | |
+
+### 9.2.3.155 SCG Activation Status
+
+This IE indicates the status of the SCG resources.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------|----------|-------|-----------------------------------------------------------|-----------------------|
+| SCG Activation Status | M | | ENUMERATED<br>(SCG<br>activated, SCG<br>deactivated, ...) | |
+
+### 9.2.3.156 QMC Configuration Information
+
+This IE contains the information about the QoE Measurement Collection (QMC) configuration.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------------------|----------|----------------------------|-----------------------|-----------------------|
+| <b>UE Application Layer Measurement Information List</b> | | | | |
+| > <b>UE Application Layer Measurement Information Item</b> | | 1..<maxnoofUEAppLayerMeas> | | |
+| >>UE Application Layer Measurement Configuration Information | M | | 9.2.3.157 | |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------|
+| maxnoofUEAppLayerMeas | Maximum no. of simultaneous QoE measurement configurations at a UE. In this version of the specification, the value is 16. |
+
+### 9.2.3.157 UE Application Layer Measurement Configuration Information
+
+This IE defines the information about the QoE Measurement Collection (QMC) configuration.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|---------------------------|-------------------------------------------------------------|-------------|----------------------|
+| QoE Reference | M | | OCTET STRING<br>(SIZE(6)) | <i>QoE Reference</i> ,<br>as defined in<br>clause 5.2 of TS | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------------------------------------|----------|-------|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. | | |
+| Measurement Configuration Application Layer ID | O | | INTEGER (0..15, ...) | This IE indicates the identity of the application layer measurement configuration, and corresponds to information provided in the <i>MeasConfigAppLayerId</i> IE as defined in TS 38.331 [10]. | – | |
+| Service Type | M | | ENUMERATED (QMC for DASH streaming, QMC for MTSI, QMC for VR, ...) | This IE indicates the service type of QoE measurements. | – | |
+| QoE Measurement Status | O | | ENUMERATED (ongoing, ...) | Indicates whether the QoE measurement has started. | – | |
+| Container for Application Layer Measurement Configuration | O | | OCTET STRING (SIZE(1..8000)) | Contains the signalling based QoE measurement configuration, see Annex L in TS 26.247 [47], clause 16.5 in TS 26.114 [53] and clause 9 in TS 26.118 [54]. | – | |
+| CHOICE <i>MDT Alignment Information</i> | O | | | Indicates the MDT measurements with which alignment is required. | – | |
+| >S-based <i>MDT</i> | | | | | – | |
+| >>NG-RAN Trace ID | M | | 9.2.3.97 | Indicates the signalling-based | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|------------------------------|----------------------------------------|------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | MDT measurements with which alignment is required. | | |
+| Measurement Collection Entity IP Address | O | | Transport Layer Address 9.2.3.29 | The IP address of the entity receiving the QoE measurement report. | – | |
+| CHOICE Area Scope of QMC | O | | | | – | |
+| >Cell based | | | | | – | |
+| >>Cell ID List for QMC | | 1 .. <maxnoo fCellIDfor QMC> | | | – | |
+| >>>Global NG-RAN Cell Identity | M | | 9.2.2.27 | The included NG-RAN Cell Identity IE can only indicate the NR Cell Identity. | – | |
+| >TA based | | | | | – | |
+| >>TA List for QMC | | 1 .. <maxnoo fTAforQ MC> | | | – | |
+| >>>TAC | M | | 9.2.2.5 | The TAI is derived using the current serving PLMN. | – | |
+| >TAI based | | | | | – | |
+| >>TAI List for QMC | | 1 .. <maxnoo fTAforQ MC> | | | – | |
+| >>>PLMN Identity | M | | 9.2.2.4 | | – | |
+| >>>TAC | M | | 9.2.2.5 | | – | |
+| >PLMN based | | | | | – | |
+| >>PLMN List for QMC | | 1 .. <maxnoo fPLMNfo rQMC> | | | – | |
+| >>>PLMN Identity | M | | 9.2.2.4 | | – | |
+| <b>S-NSSAI List</b> | O | 0..1 | | | – | |
+| >S-NSSAI Item | | 1 .. <maxnoo fSNSSAI forQMC> | | | – | |
+| >>S-NSSAI | M | | S-NSSAI 9.2.3.21 | | – | |
+| Available RAN Visible QoE Metrics | O | | 9.2.3.158 | Present in case of signalling-based QoE. | – | |
+| MBS Communication Service Type | O | | ENUMERATED (multicast, broadcast, ...) | This IE indicates for which type of MBS communication | YES | ignore |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|-----------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| | | | | service the QoE measurement configuration pertains to. | | |
+| Assistance Information for QoE Measurement | O | | INTEGER (1..16, ...) | This IE indicates the suggested priority of the application layer measurement configuration. Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 16 as the lowest priority. | YES | ignore |
+| QoE and RVQoE Reporting Paths | O | 9.2.3.200 | | This IE indicates the SRBs currently used for QoE and RVQoE reporting. | YES | ignore |
+
+| Range bound | Explanation |
+|---------------------|-------------------------------------------------------------------|
+| maxnoofCellIDforQMC | Maximum no. of Cell IDs comprising the QMC scope. Value is 32. |
+| maxnoofTAforQMC | Maximum no. of TA comprising the QMC scope. Value is 8. |
+| maxnoofPLMNforQMC | Maximum no. of PLMNs in the PLMN list for QMC scope. Value is 16. |
+| maxnoofNSSAIforQMC | Maximum no. of S-NSSAIs comprising the QMC scope. Value is 16. |
+
+### 9.2.3.158 Available RAN Visible QoE Metrics
+
+This IE indicates which RAN visible QoE metrics can be configured by the NG-RAN for the RAN visible QoE measurement.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------------|----------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| Buffer Level | O | | ENUMERATED (true, ...) | This IE defines whether the Buffer Level can be collected as a RAN visible QoE metric by NG-RAN from UE, for DASH streaming and VR service types. |
+| Playout Delay for Media Startup | O | | ENUMERATED (true, ...) | This IE defines whether the Playout delay can be collected as a RAN visible QoE metric by NG-RAN from UE, for DASH streaming and VR service types. |
+
+### 9.2.3.159 5G ProSe Authorized
+
+This IE provides information on the authorization status of the UE to use the 5G ProSe services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|-------|----------------------------------------------|------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| 5G ProSe Direct Discovery | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Direct Discovery. | – | |
+| 5G ProSe Direct Communication | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Direct Communication. | – | |
+| 5G ProSe Layer-2 UE-to-Network Relay | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-Network Relay. | – | |
+| 5G ProSe Layer-3 UE-to-Network Relay | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-3 UE-to-Network Relay. | – | |
+| 5G ProSe Layer-2 Remote UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 Remote UE. | – | |
+| 5G ProSe Layer-2 Multi-path | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the 5G ProSe Layer-2 Remote UE is authorized for 5G ProSe Multi-path transmission. | YES | ignore |
+| 5G ProSe Layer-2 UE-to-UE Relay | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-UE Relay UE | YES | ignore |
+| 5G ProSe Layer-2 UE-to-UE Remote | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-UE Remote UE. | YES | ignore |
+
+### 9.2.3.160 5G ProSe PC5 QoS Parameters
+
+This IE provides information on the 5G ProSe PC5 QoS parameters of the UE's sidelink communication for 5G ProSe services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|-----------------------|-----------------------|
+| 5G ProSe PC5 QoS Flow List | | 1 | | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------------------------|-----------------------------------------------------------------------|------------------------------------------------------------------------------|
+| <b>>5G ProSe PC5 QoS Flow Item</b> | | 1..<maxnoofPC5QoSFlows> | | |
+| >>PQI | M | | INTEGER (0..255, ...) | PQI is a special 5QI as specified in TS 23.501 [7]. |
+| <b>>>5G ProSe PC5 Flow Bit Rates</b> | O | | | Only applies for GBR QoS Flows. |
+| >>>Guaranteed Flow Bit Rate | M | | Bit Rate 9.2.3.4 | Guaranteed Bit Rate for the 5G ProSe PC5 QoS flow. Details in TS 23.501 [7]. |
+| >>>Maximum Flow Bit Rate | M | | Bit Rate 9.2.3.4 | Maximum Bit Rate for the 5G ProSe PC5 QoS flow. Details in TS 23.501 [7]. |
+| >>Range | O | | ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...) | Only applies for groupcast. |
+| 5G ProSe PC5 Link Aggregate Bit Rates | O | | Bit Rate 9.2.3.4 | Only applies for non-GBR QoS Flows. |
+
+| Range bound | Explanation |
+|--------------------|------------------------------------------------------------------------------|
+| maxnoofPC5QoSFlows | Maximum no. of 5G ProSe PC5 QoS flows allowed towards one UE. Value is 2048. |
+
+### 9.2.3.161 NR Paging eDRX Information
+
+This IE indicates the NR Paging eDRX parameters as defined in TS 38.304 [33].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| NR Paging eDRX Cycle | M | | ENUMERATED (hfquarter, hfhalf, hf1, hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, ...) | T <sub>eDRX, CN</sub> defined in TS 38.304 [33]. Unit: [number of hyperframes]. |
+| NR Paging Time Window | O | | ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, ..., s17, s18, s19, s20, s21, s22, s23, s24, s25, s26, s27, s28, s29, s30, s31, s32) | Unit: [1.28 seconds] |
+
+### 9.2.3.162 NR Paging eDRX Information for RRC INACTIVE
+
+This IE indicates the NR Paging eDRX parameters for RRC\_INACTIVE as defined in TS 38.304 [33].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|-----------------------|---------------------------------------------|
+| NR Paging eDRX Cycle | M | | ENUMERATED | T <sub>eDRX, RAN</sub> defined in TS 38.304 |
+
+| | | | | |
+|----------|--|--|-------------------------------|--------------------------------------|
+| Inactive | | | (hfquarter, hfhalf, hf1, ...) | [33]. Unit: [number of hyperframes]. |
+|----------|--|--|-------------------------------|--------------------------------------|
+
+### 9.2.3.163 SDT Support Request
+
+This IE indicates that the UE requested for SDT and may include additional assistance information.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|---------------------------|----------|-------|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| SDT Indicator | M | | ENUMERATED (true,...) | |
+| SDT assistant information | O | | ENUMERATED (single packet, multiple packets, ...) | “Single packet” indicates no subsequent SDT transmission is expected;<br>“Multiple packets” indicates subsequent SDT transmission is expected. |
+
+### 9.2.3.164 Partial UE Context Information for SDT
+
+This IE contains the UE context information within the PARTIAL UE CONTEXT TRANSFER message for NR SDT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>SDT DRBs To Be Setup List</b> | | 0..1 | | | YES | ignore |
+| > <b>SDT DRBs to Be Setup Item</b> | | 1 .. <maxnoof DRBs> | | | – | |
+| >>DRB ID | M | | 9.2.3.33 | | – | |
+| >>UL TNL Information | M | | UP Transport Layer Information 9.2.3.30 | | – | |
+| >>DRB RLC Bearer Configuration | M | | OCTET STRING | Includes the <i>RLC-BearerConfig</i> IE as defined in subclause 6.3.2 of TS 38.331 [10] | – | |
+| >>DRB QoS | M | | QoS Flow Level QoS Parameters 9.2.3.5 | | – | |
+| >>RLC Mode | M | | 9.2.3.28 | | – | |
+| >>S-NSSAI | M | | 9.2.3.21 | | – | |
+| >>PDCP SN Length | M | | 9.2.3.63 | | – | |
+| >>Flows Mapped to DRB List | | 1 | | | – | |
+| >>>Flows Mapped to DRB Item | | 1 .. <maxnoof QoSFlows> | | | – | |
+| >>>>QoS Flow Identifier | M | | 9.2.3.10 | | – | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|---------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>>QoS Flow Level QoS Parameters | M | | 9.2.3.5 | | – | |
+| >>>>QoS Flow Mapping Indication | O | | 9.2.3.79 | | – | |
+| <b>SDT SRBs to Be Setup List</b> | | 1 | | SRB1 is always included. | YES | ignore |
+| <b>>SDT SRBs to Be Setup Item</b> | | 1 .. <maxnoof SRBs> | | | – | |
+| >>SRB ID | M | | 9.2.3.165 | In this version of the specification, values "0", "3", and "4" are not set by the sender and ignored by the receiver. | – | |
+| >>SRB RLC Bearer Configuration | M | | OCTET STRING | Includes the <i>RLC-BearerConfig</i> IE as defined in subclause 6.3.2 of TS 38.331 [10]. | – | |
+
+| Range bound | Explanation |
+|-------------|---------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 32. |
+| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 5. |
+
+### 9.2.3.165 SRB ID
+
+This IE uniquely identifies a SRB for a UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| SRB ID | M | | INTEGER (0..4, ...) | Corresponds to information provided either in the <i>SRB-Identity</i> IE or in the <i>SRB-Identity-v1700</i> IE as defined in TS 38.331 [10]. |
+
+### 9.2.3.166 PEIPS Assistance Information
+
+This IE provides the information related to CN paging subgrouping for a particular UE, as specified in TS 38.304 [33].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|-----------------------|
+| CN Subgroup ID | M | | INTEGER (0..7, ...) | |
+
+### 9.2.3.167 UE Slice Maximum Bit Rate List
+
+The UE Slice Maximum Bit Rate List includes a list of UE Slice Maximum Bit Rate, each UE Slice Maximum Bit Rate is applicable for all PDU Sessions associated with a specific S-NSSAI of that UE, which is defined for the Downlink
+
+and the Uplink direction as specified in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------|----------|----------------------|-----------------------|----------------------------------------------------------------------------------------------------------|
+| <b>UE Slice Maximum Bit Rate</b> | | 1..<maxnoofS<br>MBR> | | |
+| >S-NSSAI | M | | 9.3.1.24 | |
+| >UE Slice Maximum Bit Rate Downlink | M | | Bit Rate 9.2.3.4 | This IE indicates the UE Slice Maximum Bit Rate as specified in TS 23.501 [7] in the downlink direction. |
+| >UE Slice Maximum Bit Rate Uplink | M | | Bit Rate 9.2.3.4 | This IE indicates the UE Slice Maximum Bit Rate as specified in TS 23.501 [7] in the uplink direction. |
+
+| Range bound | Explanation |
+|-------------|-------------------------------------------------------------|
+| maxnoofSMBR | Maximum no. of SLICE MAXIMUM BIT RATE for a UE. Value is 8. |
+
+### 9.2.3.168 Positioning Information
+
+This IE contains positioning information that assists in the SRS configuration of the UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------|
+| Requested SRS Transmission Characteristics | M | | OCTET STRING | Requested SRS Transmission Characteristics, as defined in TS 38.455 [49]. |
+| Routing ID | M | | OCTET STRING | The maximum length corresponds to NflInstanceId defined in TS 29.571 [50]. |
+| NRPPa Transaction ID | M | | INTEGER (0..32767) | NRPPa Transaction ID, as defined in TS 38.455 [49] |
+
+### 9.2.3.169 MDT PLMN Modification List
+
+The purpose of the *MDT PLMN List Modification* IE is to provide the modified list of PLMN allowed for MDT.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|--------------------------|-----------------------|-----------------------------------------------------------|
+| <b>MDT PLMN Modification List</b> | | 0..<maxnoofM<br>DTPLMNs> | | An empty list indicates there is no PLMN allowed for MDT. |
+| >PLMN Identity | M | | 9.2.2.4 | |
+
+| Range bound | Explanation |
+|-----------------|---------------------------------------------------------|
+| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. |
+
+### 9.2.3.170 TAI NSAG Support List
+
+This IE indicates the slice group mapping for all groups supported at the NG-RAN node per TAI.
+
+| IE/Group Name | Presenc | Range | IE type and | Semantics description |
+|---------------|---------|-------|-------------|-----------------------|
+|---------------|---------|-------|-------------|-----------------------|
+
+| | e | | reference | |
+|--------------------------|---|-------------------|------------------------------------------|--------------------------------------------------------|
+| <b>NSAG Support Item</b> | | 1..<maxnoofNSAGs> | | |
+| >NSAG ID | M | | INTEGER (0..255, ...) | |
+| >NSAG Slice Support List | M | | Extended Slice Support List<br>9.2.3.139 | Indicates the list of slices which belong to the NSAG. |
+
+| Range bound | Explanation |
+|--------------|--------------------------------------------------------|
+| maxnoofNSAGs | Maximum no. of Slice Groups for the TAI. Value is 256. |
+
+### 9.2.3.171 Excess Packet Delay Threshold Configuration
+
+This IE defines the parameters for Excess Packet Delay Threshold configuration to support the calculation of the PDCP Excess Packet Delay in the UL per DRB as specified in TS 38.314 [42].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------|----------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| <b>Excess Packet Delay Threshold Item</b> | | 1..<maxnoofThresholds> | | |
+| >5QI | M | | INTEGER (0..255, ...) | Indicates the standardized or pre-configured 5QI as specified in TS 23.501 [7] |
+| >Excess Packet Delay Threshold Value | M | | ENUMERATED (ms0.25, ms0.5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70, ms80, ms90, ms100, ms150, ms300, ms500, ...) | |
+
+| Range bound | Explanation |
+|---------------------------------------|--------------------------------------------------------------------------------|
+| maxnoofThresholdsForExcessPacketDelay | Maximum no. of thresholds for Excess Packet Delay configuration. Value is 255. |
+
+### 9.2.3.172 MT-SDT Information
+
+This IE provides the assistance information for MT-SDT.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|------------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MT-SDT Indicator | M | | ENUMERATED (true, ...) | |
+| MT-SDT Data Size | M | | INTEGER (1..96000, ...) | Indicates the total data size for DL NAS signalling and user plane data for all SDT bearers. Unit: byte. Corresponds to the PDCP SDU size for the DL NAS signalling and the SDAP SDU size for the received DL user plane data. |
+
+### 9.2.3.173 Partial UE Context Information for Positioning
+
+This IE contains the UE context information within the PARTIAL UE CONTEXT TRANSFER message for NR Positioning.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------|
+| Requested SRS Transmission Characteristics | O | | OCTET STRING | Includes the <i>Requested SRS Transmission Characteristics</i> IE, as defined in TS 38.455 [49]. |
+
+### 9.2.3.174 DL LBT Failure Information
+
+This IE contains information on DL LBT Failures at the target gNB during handover execution.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| UE Assistant Identifier | M | | Source gNB UE XnAP ID<br>9.2.3.16 | |
+| Number of DL LBT Failures | O | | INTEGER<br>(1..1000,...) | This IE indicates the number of DL LBT Failures, if available, occurring at the target gNB during handover execution |
+
+### 9.2.3.175 Aerial UE Subscription Information
+
+This information element is used by the NG-RAN node to know if the UE is allowed to use aerial function, refer to TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|------------------------------------------|-----------------------|
+| Aerial UE Subscription Information | M | | ENUMERATED<br>(allowed, not allowed,...) | |
+
+### 9.2.3.176 NR A2X Services Authorized
+
+This IE provides information on the authorization status of the UE to use the NR A2X services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|-------------------------------------------------|-----------------------------------------------------------------|
+| Aerial UE | O | | ENUMERATED<br>(authorized, not authorized, ...) | Indicates whether the UE is authorized as Aerial UE. |
+| Aerial Controller UE | O | | ENUMERATED<br>(authorized, not authorized, ...) | Indicates whether the UE is authorized as Aerial Controller UE. |
+
+### 9.2.3.177 LTE A2X Services Authorized
+
+This IE provides information on the authorization status of the UE to use the LTE A2X services.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|----------------------------------------------|-----------------------------------------------------------------|
+| Aerial UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Aerial UE. |
+| Aerial Controller UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Aerial Controller UE. |
+
+### 9.2.3.178 A2X PC5 QoS Parameters
+
+This IE provides information on the A2X PC5 QoS parameters of the UE's PC5 communication for A2X service.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------------------------|-----------------------------------------------------------------------|-------------------------------------------------------------------------|
+| <b>A2X PC5 QoS Flow List</b> | | 1 | | |
+| > <b>A2X PC5 QoS Flow Item</b> | | 1..<maxnoofPC5QoSFlows> | | |
+| >>PQI | M | | INTEGER (0..255, ...) | PQI is a special 5QI as specified in TS 23.501 [7]. |
+| >> <b>A2X PC5 Flow Bit Rates</b> | O | | | Only applies for GBR QoS Flows. |
+| >>>Guaranteed Flow Bit Rate | M | | Bit Rate 9.2.3.4 | Guaranteed Bit Rate for the A2X PC5 QoS flow. Details in TS 23.501 [7]. |
+| >>>Maximum Flow Bit Rate | M | | Bit Rate 9.2.3.4 | Maximum Bit Rate for the A2X PC5 QoS flow. Details in TS 23.501 [7]. |
+| >>Range | O | | ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...) | Only applies for groupcast. |
+| <b>A2X PC5 Link Aggregate Bit Rates</b> | O | | Bit Rate 9.2.3.4 | Only applies for non-GBR QoS Flows. |
+
+| Range bound | Explanation |
+|---------------------------|-------------------------------------------------------------------------|
+| <i>maxnoofPC5QoSFlows</i> | Maximum no. of A2X PC5 QoS flows allowed towards one UE. Value is 2048. |
+
+### 9.2.3.179 UE Performance
+
+This IE indicates the UE performance measurements metrics.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------|----------|-------|------------------------------|-----------------------|
+| Average UE Throughput DL | O | | Bit Rate<br>9.2.3.4 | |
+| Average UE Throughput UL | O | | Bit Rate<br>9.2.3.4 | |
+| Average Packet Delay | O | | 9.2.3.187 | |
+| Average Packet Loss DL | O | | Packet Loss Rate<br>9.2.3.11 | |
+
+### 9.2.3.180 Cell Based UE Trajectory Prediction
+
+The *Cell Based UE Trajectory Prediction* IE contains the list of NG-RAN cells where the UE is predicted to connect.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------------------|----------|------------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Cell Based UE Trajectory Prediction</b> | | 1 | | List of cells where the UE is predicted to connect, in chronological order. The first predicted cell added to the top of this list, is the cell where the UE will move to after the serving cell at the source node. |
+| >Predicted UE Trajectory Item | | 1..<maxnoofCellsTrajectoryPredict> | | |
+| >>Predicted Trajectory Cell Information | M | | 9.2.3.181 | |
+
+| Range bound | Explanation |
+|-------------------------------|-------------------------------------------------------------------------------|
+| maxnoofCellsTrajectoryPredict | Maximum number of cells that can be predicted for UE trajectory. Value is 16. |
+
+### 9.2.3.181 Predicted Trajectory Cell Information
+
+The *Predicted Trajectory Cell Information* IE contains the cell IDs of the predicted NG-RAN cells for cell based UE trajectory prediction.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>Predicted Trajectory Cell Information</i> | M | | | |
+| >NG-RAN Cell | | | | |
+| >>Global NG-RAN Cell Identity | M | | 9.2.2.27 | |
+| >>Predicted Time UE Stays in Cell | O | | INTEGER (0..4095) | The duration of time the UE is expected to stay in the cell, in seconds. If the duration is more than 4095s, this IE is set to 4095. |
+
+### 9.2.3.182 Measured UE Trajectory
+
+The *Measured UE Trajectory* IE contains the list of NG-RAN cells where the UE connected after being handed over to the target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------------|----------|-----------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------|
+| <b>Measured UE Trajectory</b> | | 1 | | List of cells where the UE connected, in chronological order. Most recent information is added to the top of this list. |
+| > <b>Measured UE Trajectory Item</b> | | 1..<maxnoofCellsTrajectory> | | |
+| >>Measured Trajectory Cell Information | M | | 9.2.3.183 | |
+
+| Range bound | Explanation |
+|------------------------|------------------------------------------------------------------------------|
+| maxnoofCellsTrajectory | Maximum number of cells that can be reported for UE trajectory. Value is 16. |
+
+### 9.2.3.183 Measured Trajectory Cell Information
+
+The *Measured Trajectory Cell Information* contains the cell IDs of the NG-RAN cells where a UE connected after being handed over to the target NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>Measured Trajectory Cell Information</i> | | | | |
+| > <i>NG-RAN Cell</i> | | | | |
+| >>Global NG-RAN Cell Identity | M | | 9.2.2.27 | |
+| >>Time UE Stayed in Cell | M | | INTEGER (0..4095) | The duration of time the UE stayed in the cell If the duration is more than 4095s, this IE is set to 4095. |
+
+### 9.2.3.184 Data Collection ID
+
+This IE indicates the NG-RAN Node Measurement IDs which identify a Data Collection Reporting context.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|-----------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------|
+| NG-RAN node1 Measurement ID | M | | INTEGER (1..4095,...) | Together with NG-RAN node2 Measurement ID, identifies a Data Collection Reporting context. |
+| NG-RAN node2 Measurement ID | M | | INTEGER (1..4095,...) | Together with NG-RAN node1 Measurement ID, identifies a Data Collection Reporting context. |
+
+### 9.2.3.185 UE Trajectory Collection Configuration
+
+This IE contains additional conditions triggering the target node to report UE Trajectory after successful handover.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------|----------|-------|------------------------|-------------------------------------------------------------------------------------|
+| Collection Time Duration | M | | INTEGER (1..4096, ...) | The maximum time duration, in seconds, starting from successful handover execution. |
+| Number of Visited Cells | O | | INTEGER (1..16, ...) | Maximum number of intra-node visited cells. |
+
+### 9.2.3.186 UE Performance Collection Configuration
+
+This IE indicates the configuration for UE performance measurement collection.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Collection Time Duration | M | | INTEGER(1..5000, ...) | Time duration starting at successful handover execution within which the UE performance measurements are collected by NG-RAN node <sub>2</sub> .<br>Unit: millisecond |
+
+### 9.2.3.187 Average Packet Delay
+
+This IE indicates the RAN part of the average packet delay in the UL and DL directions.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------|-----------------------|-----------------------------------------------------|
+| Average Packet Delay UL | M | | INTEGER (0..10000) | Defined in TS 38.314 [42].<br>Unit: 0.1 millisecond |
+| Average Packet Delay DL | M | | INTEGER (0..10000) | Defined in TS 38.314 [42].<br>Unit: 0.1 millisecond |
+
+### 9.2.3.188 Candidate Relay UE Info List
+
+This IE contains the identity of the candidate relay UE(s) when the source NG-RAN decides to switch the UE to an indirect path at the target NG-RAN.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------|----------|-------------------------------|-----------------------|---------------------------------------------------------------------------------------------------|
+| Candidate Relay UE Info Item | | 1..<maxnoofCandidateRelayUEs> | | |
+| >Candidate Relay UE ID | M | | BIT STRING(SIZE(24)) | Includes the <i>SL-SourceIdentity</i> IE for the candidate relay UE as defined in TS 38.331 [10]. |
+
+| Range bound | Explanation |
+|--------------------------|-----------------------------------------------------------|
+| maxnoofCandidateRelayUEs | Maximum number of candidate relay UE(s). The value is 32. |
+
+### 9.2.3.189 Clock Quality Reporting Control Information
+
+This IE indicates the clock quality reporting control information as defined in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>Clock Quality Detail Level</i> | M | | | |
+| > <i>clock quality metrics</i> | | | NULL | |
+| > <i>acceptance indication</i> | | | | |
+| >>Clock Quality Acceptance Criteria | M | | 9.3.1.190 | |
+
+### 9.2.3.190 Clock Quality Acceptance Criteria
+
+This IE indicates the clock quality acceptance criteria as defined in TS 23.501 [7].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Synchronisation State | O | | BIT STRING {<br>locked (0),<br>holdover (1),<br>freeRun (2) }<br>(SIZE (8, ...)) | Each position in the bitmap represents a synchronisation state.<br>If a bit is set to "1", the respective synchronisation state is acceptable. If a bit is set to "0", the respective synchronisation state is not acceptable.<br>Bits 3-7 reserved for future use. |
+| Traceable to UTC | O | | ENUMERATED<br>(true, ...) | |
+| Traceable to GNSS | O | | ENUMERATED<br>(true, ...) | |
+| Clock Frequency Stability | O | | BIT STRING (SIZE (16)) | Indicates the offsetScaledLogVariance as specified in TS 23.501 [9]. |
+| Clock Accuracy | O | | INTEGER<br>(1..400000000, ...) | Clock accuracy expressed in units of 25 ns. |
+| Parent Time Source | O | | BIT STRING {<br>syncE (0),<br>pTP (1),<br>gNSS (2),<br>atomicClock (3),<br>terrestrialRadio (4),<br>serialTimeCode (5),<br>nTP (6),<br>handset (7),<br>other (8) }<br>(SIZE (16, ...)) | Each position in the bitmap represents a parent time source.<br>If a bit is set to "1", the respective parent time source is acceptable. If a bit is set to "0", the respective parent time source is not acceptable.<br>Bits 9-15 reserved for future use. |
+
+### 9.2.3.191 PNI-NPN Area Scope of MDT
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------|----------|-------------------------|-----------------------|-----------------------|
+| <b>CAG List for MDT</b> | | 1..< maxnoofCAGforMDT > | | |
+| >PLMN Identity | M | | 9.2.2.4 | |
+| >CAG-Identifier | M | | 9.2.2.66 | |
+
+| Range bound | Explanation |
+|------------------|----------------------------------------------------------|
+| maxnoofCAGforMDT | Maximum no. of CAG IDs for MDT area scope. Value is 256. |
+
+### 9.2.3.192 S-CPAC Request Information
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------------------------|----------|------------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| S-CPAC Security Configurations List | M | | 9.2.3.193 | Indicates the security configurations for S-CPAC, which will replace the previous configuration if any. |
+| <b>S-CPAC Multiple Target S-NG-RAN Node List</b> | | 0 ..<br><maxnoofTargetSNsMinusOne> | | |
+| >Target S-NG-RAN node ID | M | | Global NG-RAN Node ID<br>9.2.2.3 | Other candidate SN under preparation for S-CPAC. |
+| >Recommended Candidate PSCells | M | | OCTET STRING | Includes either the <i>candidateCellInfoListMN</i> in case of MN-initiated inter-SN S-CPAC or the <i>candidateCellListCPC</i> in case of SN-initiated inter-SN S-CPAC, contained in the <i>CG-ConfigInfo</i> message as defined in TS 38.331 [10], |
+
+| Range bound | Explanation |
+|--------------------------|--------------------------------------------------------------|
+| maxnoofTargetSNsMinusOne | Maximum no. of the target S-NG-RAN nodes minus 1. Value is 7 |
+
+### 9.2.3.193 S-CPAC Security Configurations List
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------------------|----------|-----------------------------------------|---------------------------|-----------------------------------------------------------------------------|
+| <b>S-CPAC Security Configurations List</b> | | 1 | | |
+| > <b>S-CPAC Security Configurations Item</b> | | 1 ..<br><maxnoofSecurityConfigurations> | | |
+| >>S-NG-RAN node Security Key | M | | BIT STRING<br>(SIZE(256)) | The S- $K_{SN}$ which is provided by the M-NG-RAN node, see TS 33.501 [28]. |
+| >>SK-counter | M | | INTEGER<br>(0..65535) | |
+
+| Range bound | Explanation |
+|-------------------------------|------------------------------------------------------------|
+| maxnoofSecurityConfigurations | Maximum no. of S-CPAC security configurations. Value is 8. |
+
+### 9.2.3.194 Complete Configuration Indicator
+
+This IE indicates the type of RRC configuration used at the S-NG-RAN node for S-CPAC.
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|----------------------------------|----------|-------|-------------------------------------------------|-----------------------|
+| Complete Configuration Indicator | M | | ENUMERATED (complete config, delta config, ...) | |
+
+### 9.2.3.195 NR Paging Long eDRX Information for RRC INACTIVE
+
+This IE indicates the NR Paging long eDRX parameters as defined in TS 38.304 [33].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|
+| NR Paging Long eDRX Cycle for RRC INACTIVE | M | | ENUMERATED (hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, ...) | $T_{\text{long-eDRX, RAN}}$ defined in TS 38.304 [33]. Unit: [number of hyperframes]. |
+| NR Paging Time Window for RRC_INACTIVE | M | | ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, s17, s18, s19, s20, s21, s22, s23, s24, s25, s26, s27, s28, s29, s30, s31, s32, ...) | Unit: [1.28 seconds] |
+
+### 9.2.3.196 MBS Assistance Information
+
+This IE provides the MBS Assistance Information as specified in TS 38.300 [9] and TS 23.247 [46].
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------|----------|-------|------------------------|-----------------------|
+| MBS Assistance Information | M | | ENUMERATED (true, ...) | |
+
+### 9.2.3.197 QMC Coordination Request
+
+This IE contains the information that the S-NG-RAN node needs to provide to the M-NG-RAN node, or the information that the M-NG-RAN node needs to provide to the S-NG-RAN node, for managing configuration and reporting of one or more QoE and/or RAN visible QoE measurements.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------|----------|-----------------------------|-----------------------|------------------------------|
+| <b>MN to SN QMC Coordination Request List</b> | | 0..1 | | |
+| > <b>MN to SN QMC Coordination Request Item</b> | | 1..<maxnoofUE AppLayerMeas> | | |
+| >>QoE Reference | M | | OCTET STRING | QoE Reference, as defined in |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|-----------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | | | (SIZE(6)) | clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. |
+| >>Measurement Configuration Application Layer ID | O | | INTEGER (0..15, ...) | |
+| >>Measurement Collection Entity IP Address | O | | Transport Layer Address 9.2.3.29 | The IP address of the entity receiving the QoE measurement report. |
+| >>QoE Reporting Path Request | O | | ENUMERATED (srb4, srb5, ...) | This IE indicates the preferred SRB for receiving the QoE reports. |
+| >>RAN Visible QoE Reporting Path Request | O | | ENUMERATED (srb4, srb5, ...) | This IE indicates the preferred SRB for receiving the RAN Visible QoE reports. |
+| >>Further RAN Visible QoE Interest Inquiry | O | | ENUMERATED (true, ...) | This IE is used to request from the S-NG-RAN node to indicate whether it is interested in receiving further RVQoE reports. |
+| >>Further RAN Visible QoE Reporting Path | O | | ENUMERATED (true, ...) | This IE indicates the preferred SRB for receiving further RAN Visible QoE reports. |
+| >>Current RAN Visible QoE Configuration | O | | RAN Visible QoE Configuration 9.2.3.201 | This IE is to indicate the current RAN Visible QoE configuration and inquire about the RAN Visible QoE Configuration preference of the S-NG-RAN node. |
+| <b>SN to MN QMC Coordination Request List</b> | | 0..1 | | |
+| > <b>SN to MN QMC Coordination Request Item</b> | | 1..<maxnoofUE AppLayerMeas> | | |
+| >>QoE Reference | M | | OCTET STRING (SIZE(6)) | QoE Reference, as defined in clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. |
+| >>Measurement Collection Entity IP Address | O | | Transport Layer Address 9.2.3.29 | The IP address of the entity receiving the QoE measurement report. |
+| >>QoE Reporting Path Request | O | | ENUMERATED (srb4, srb5, ...) | This IE indicates the preferred SRB for receiving the QoE reports. |
+| >>RAN Visible QoE | O | | ENUMERATED | This IE indicates the preferred |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------|----------|-------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Reporting Path Request | | | (srb4, srb5, ...) | SRB for receiving the RAN Visible QoE reports. |
+| >>Further RAN Visible QoE Interest Inquiry | O | | ENUMERATED (true, ...) | This IE is used to request from the M-NG-RAN node to indicate whether it is interested in receiving further RVQoE reports. |
+| >>Further RAN Visible QoE Reporting Path | O | | ENUMERATED (true, ...) | This IE indicates the preferred SRB for receiving further RAN Visible QoE reports. |
+| >>Current RAN Visible QoE Configuration | O | | RAN Visible QoE Configuration 9.2.3.201 | This IE is to indicate the current RAN Visible QoE configuration and inquire about the RAN Visible QoE Configuration preference of the M-NG-RAN node. |
+| >>Configuration Release Indication | O | | ENUMERATED (true, ...) | This IE indicates that the configuration has been released by the SN. |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------|
+| maxnoofUEAppLayerMeas | Maximum no. of simultaneous QoE measurement configurations at a UE. In this version of the specification, the value is 16. |
+
+### 9.2.3.198 QMC Coordination Response
+
+This IE contains the information that the M-NG-RAN node needs to provide to the S-NG-RAN node, or the information that the S-NG-RAN node needs to provide to the S-NG-RAN node in response to the QMC Coordination Request.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|----------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>MN to SN QMC Coordination Response List</b> | | 0..1 | | |
+| > <b>MN to SN QMC Coordination Response Item</b> | | 1..<maxnoofUEAppLayerMeas> | | |
+| >>QoE Reference | M | | OCTET STRING (SIZE(6)) | QoE Reference, as defined in clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. |
+| >>Measurement Configuration Application Layer ID | O | | INTEGER (0..15, ...) | |
+| >>QoE Configuration Sending Path | O | | ENUMERATED (mn, sn, ...) | |
+| >>QoE Reporting Path Response | O | | ENUMERATED (accepted, rejected, ...) | |
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------------------|----------|----------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >>RVQoE Reporting Path Response | O | | ENUMERATED (accepted, rejected, ...) | |
+| >>Further RAN Visible QoE Interest Response | O | | ENUMERATED (rvqoe reports desired, rvqoe reports not desired, ...) | This IE is to indicate whether the M-NG-RAN node is interested in receiving further RAN Visible QoE reports. |
+| >>Further RAN Visible QoE Reporting Path | O | | ENUMERATED (srb4, srb5, ...) | This IE is to indicate the preferred path for further RAN Visible QoE reporting. |
+| >>Preferred RAN Visible QoE Configuration | O | | RAN Visible QoE Configuration 9.2.3.201 | The RAN Visible QoE Configuration preference of the M-NG-RAN node. |
+| <b>SN to MN QMC Coordination Response List</b> | | 0..1 | | |
+| >SN to MN QMC Coordination Response Item | | 1..<maxnoofUEAppLayerMeas> | | |
+| >>QoE Reference | M | | OCTET STRING (SIZE(6)) | QoE Reference, as defined in clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. |
+| >>QoE Reporting Path Response | O | | ENUMERATED (accepted, rejected, ...) | |
+| >>RVQoE Reporting Path Response | O | | ENUMERATED (accepted, rejected, ...) | |
+| >>Further RAN Visible QoE Interest Response | O | | ENUMERATED (interested, not-interested, ...) | This IE is to indicate whether the S-NG-RAN node is interested in receiving further RAN Visible QoE reports. |
+| >>Further RAN Visible QoE Reporting Path | O | | ENUMERATED (srb4, srb5, ...) | This IE is to indicate the preferred path for further RAN Visible QoE reporting. |
+| >>Preferred RAN Visible QoE Configuration | O | | RAN Visible QoE Configuration 9.2.3.201 | The RAN Visible QoE Configuration preference of the S-NG-RAN node. |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------|
+| maxnoofUEAppLayerMeas | Maximum no. of simultaneous QoE measurement configurations at a UE. In this version of the specification, the value is 16. |
+
+### 9.2.3.199 SN-related QMC Information at MN
+
+This IE contains the information that the M-NG-RAN node has about the QoE configurations at the S-NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------------------------|----------|----------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>SN-related QMC Information at MN List</b> | | 0..1 | | |
+| <b>>SN-related QMC Information at MN Item</b> | | 1..<maxnoofUEAppLayerMeas> | | |
+| >>QoE Reference | M | | OCTET STRING (SIZE(6)) | QoE Reference, as defined in clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. |
+| >>QoE and RVQoE Reporting Paths | O | | 9.2.3.200 | This IE indicates the SRB for receiving the RAN Visible QoE reports. |
+
+| Range bound | Explanation |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------|
+| maxnoofUEAppLayerMeas | Maximum no. of simultaneous QoE measurement configurations at a UE. In this version of the specification, the value is 16. |
+
+### 9.2.3.200 QoE and RVQoE Reporting Paths
+
+This IE indicates the SRB currently used for receiving the QoE reports and RAN visible QoE reports.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------|----------|-------|------------------------------|-------------------------------------------------------------------------------------|
+| QoE Reporting Path | O | | ENUMERATED (srb4, srb5, ...) | This IE indicates the SRB currently used for receiving the QoE reports. |
+| RVQoE Reporting Path | O | | ENUMERATED (srb4, srb5, ...) | This IE indicates the SRB currently used for receiving the RAN Visible QoE reports. |
+
+### 9.2.3.201 RAN Visible QoE Configuration
+
+This IE provides information of RAN visible QoE configuration.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------|----------|-------|------------------------------------------------------|-----------------------|
+| Available RAN Visible QoE Metrics | O | | 9.2.3.158 | |
+| Reporting Periodicity | O | | ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ...) | |
+
+### 9.2.3.202 CHO-CPAC Information
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description |
+|--------------------------------------------------------|----------|--------------------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| CHO-CPAC Configuration Indicator | O | | ENUMERATED (cho-only-not-prepared, ...) | The value "cho-only-not-prepared" indicates that either CHO without SCG or CHO with SCG has not been prepared. |
+| <b>Multiple Target S-NG-RAN Node List</b> | | 0..1 | | |
+| > <b>Multiple Target S-NG-RAN Node Item</b> | | 1 .. <maxnoof TargetSNs> | | |
+| >>Target S-NG-RAN node ID | M | | Global NG-RAN Node ID 9.2.2.3 | |
+| >>PDU Session Resources Admitted List | M | | 9.2.1.2 | |
+| >> <b>Candidate PSCell List</b> | | 1 | | |
+| >>> <b>Candidate PSCell Item</b> | | 1 .. <maxnoof PSCellCandidate> | | |
+| >>>>PSCell ID | M | | NR CGI 9.2.2.7 | |
+| >>>>Target NG-RAN node To Source NG-RAN node Container | M | | OCTET STRING | Includes the <i>HandoverCommand</i> message as defined in subclause 11.2.2 of TS 38.331 [10], if the target NG-RAN node is a gNB. |
+
+| Range bound | Explanation |
+|------------------------|----------------------------------------------------------|
+| maxnoofTargetSNs | Maximum number of the target S-NG-RAN nodes. Value is 8. |
+| maxnoofPSCellCandidate | Maximum number of the candidate PSCells. Value is 8. |
+
+### 9.2.3.203 PDU Set QoS Parameters
+
+This IE defines the PDU Set QoS Parameters to be applied to a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------------------------|----------|-------|----------------------------------------|----------------------------------------------------------------------|
+| PDU Set Delay Budget | O | | Extended Packet Delay Budget 9.2.3.113 | PDU Set Delay Budget as defined in TS 23.501 [7]. |
+| PDU Set Error Rate | O | | Packet Error Rate 9.2.3.13 | PDU Set Error Rate as defined in TS 23.501 [7]. |
+| PDU Set Integrated Handling Information | O | | ENUMERATED(true, false, ...) | PDU Set Integrated handling Information as defined in TS 23.501 [7]. |
+
+### 9.2.3.204 N6 Jitter Information
+
+This IE indicates the N6 jitter information.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-----------------------|-----------------------------------------------------------------|
+| N6 Jitter Lower Bound | M | | INTEGER (-127..127) | Indicates the lower bound of the N6 jitter. The unit is: 0.5ms. |
+| N6 Jitter Upper Bound | M | | INTEGER (-127..127) | Indicates the upper bound of the N6 jitter. The unit is: 0.5ms. |
+
+### 9.2.3.205 ECN Marking or Congestion Information Reporting Request
+
+This IE indicates to the NG-RAN node to perform ECN marking or to report information for ECN marking or to report congestion information for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|-------------------------------------------------------------|----------|-------|--------------------------------------|-----------------------|
+| CHOICE <i>ECN Marking or Congestion Information Request</i> | M | | | |
+| > <i>ECN Marking at RAN</i> | | | | |
+| >>ECN Marking at RAN Request | M | | ENUMERATED (ul, dl, both, stop, ...) | |
+| > <i>ECN Marking at UPF</i> | | | | |
+| >>ECN Marking at UPF Request | M | | ENUMERATED (ul, dl, both, stop, ...) | |
+| > <i>Congestion Information</i> | | | | |
+| >>Congestion Information Request | M | | ENUMERATED (ul, dl, both, stop, ...) | |
+
+### 9.2.3.206 PDU Set based Handling Indicator
+
+This IE indicates whether PDU Set based handling is supported for by the NG-RAN node.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------|----------|-------|-----------------------------|-----------------------|
+| PDU Set based Handling Indicator | M | | ENUMERATED (supported, ...) | |
+
+### 9.2.3.207 TAI Slice Unavailable Cell List
+
+This IE is used by the NG-RAN to indicate resource configuration of a slice for the cells of the TA.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------|----------|--------------------------------------------|-----------------------|----------------------------------------------------------------------------------------|
+| <b>TAI Slice Unavailable Cell Item</b> | | 1.. <i><maxnoofExtSliceItems></i> | | |
+| >S-NSSAI | M | | 9.2.3.21 | |
+| > <b>Unavailable NR Cell List</b> | | 1 .. < <i>maxnoofCellsInNG-RANnode></i> | | |
+| >>NR-CGI | M | | 9.2.2.7 | Indicates the cells of the TAI configured with zero resources for the indicated slice. |
+
+| Range bound | Explanation |
+|---------------------------|---------------------------------------------------------------------------------------------------------|
+| maxnoofExtSliceItems | Maximum no. of signalled slice support items. Value is 65535. |
+| maxnoofCellsinNG-RAN node | Maximum no. of cells of the TAI configured with zero resources for the indicated slice. Value is 16384. |
+
+## 9.3 Message and Information Element Abstract Syntax (with ASN.1)
+
+### 9.3.1 General
+
+XnAP ASN.1 definition conforms to ITU-T Rec. X.680 [16] and ITU-T Rec. X.681 [17].
+
+Sub clause 9.3 presents the Abstract Syntax of the XnAP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this sub clause and the tabular format in sub clause 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, in which the tabular format shall take precedence.
+
+The ASN.1 definition specifies the structure and content of XnAP messages. XnAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct an XnAP message according to the PDU definitions module and with the following additional rules:
+
+- IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
+- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list in which the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
+
+NOTE: In the above, "IE" means an IE in the object set with an explicit ID. If one IE needs to appear more than once in one object set, then the different occurrences have different IE IDs.
+
+If an XnAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in clause 10.
+
+### 9.3.2 Usage of Private Message Mechanism for Non-standard Use
+
+The private message mechanism for non-standard use may be used:
+
+- for special operator (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor inter-operability.
+- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
+
+The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
+
+### 9.3.3 Elementary Procedure Definitions
+
+-- ASN1START
+
+-- \*\*\*\*\*
+
+--
+
+-- Elementary Procedure definitions
+
+--
+
+-- \*\*\*\*\*
+
+XnAP-PDU-Descriptions {
+
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+
+ngran-access (22) modules (3) xnap (2) version1 (1) xnap-PDU-Descriptions (0) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- \*\*\*\*\*
+
+--
+
+-- IE parameter types from other modules.
+
+--
+
+-- \*\*\*\*\*
+
+IMPORTS
+
+Criticality,
+ProcedureCode
+
+FROM XnAP-CommonDataTypes
+
+HandoverRequest,
+HandoverRequestAcknowledge,
+HandoverPreparationFailure,
+SNStatusTransfer,
+UEContextRelease,
+HandoverCancel,
+NotificationControlIndication,
+RANPaging,
+RetrieveUEContextRequest,
+RetrieveUEContextResponse,
+RetrieveUEContextConfirm,
+RetrieveUEContextFailure,
+XnUAddressIndication,
+SecondaryRATDataUsageReport,
+SNodeAdditionRequest,
+SNodeAdditionRequestAcknowledge,
+SNodeAdditionRequestReject,
+SNodeReconfigurationComplete,
+
+SNodeModificationRequest,
+SNodeModificationRequestAcknowledge,
+SNodeModificationRequestReject,
+SNodeModificationRequired,
+SNodeModificationConfirm,
+SNodeModificationRefuse,
+SNodeReleaseRequest,
+SNodeReleaseRequestAcknowledge,
+SNodeReleaseReject,
+SNodeReleaseRequired,
+SNodeReleaseConfirm,
+SNodeCounterCheckRequest,
+SNodeChangeRequired,
+SNodeChangeConfirm,
+SNodeChangeRefuse,
+RRCTransfer,
+XnRemovalRequest,
+XnRemovalResponse,
+XnRemovalFailure,
+XnSetupRequest,
+XnSetupResponse,
+XnSetupFailure,
+NGRANNodeConfigurationUpdate,
+
+NGRANNodeConfigurationUpdateAcknowledge,
+NGRANNodeConfigurationUpdateFailure,
+E-UTRA-NR-CellResourceCoordinationRequest,
+E-UTRA-NR-CellResourceCoordinationResponse,
+ActivityNotification,
+CellActivationRequest,
+CellActivationResponse,
+CellActivationFailure,
+ResetRequest,
+ResetResponse,
+ErrorIndication,
+PrivateMessage,
+DeactivateTrace,
+TraceStart,
+HandoverSuccess,
+ConditionalHandoverCancel,
+EarlyStatusTransfer,
+FailureIndication,
+HandoverReport,
+ResourceStatusRequest,
+ResourceStatusResponse,
+ResourceStatusFailure,
+ResourceStatusUpdate,
+
+MobilityChangeRequest,
+MobilityChangeAcknowledge,
+MobilityChangeFailure,
+AccessAndMobilityIndication,
+CellTrafficTrace,
+RANMulticastGroupPaging,
+ScgFailureInformationReport,
+ScgFailureTransfer,
+FlCTrafficTransfer,
+IABTransportMigrationManagementRequest,
+IABTransportMigrationManagementResponse,
+IABTransportMigrationManagementReject,
+IABTransportMigrationModificationRequest,
+IABTransportMigrationModificationResponse,
+IABResourceCoordinationRequest,
+IABResourceCoordinationResponse,
+CPCCancel,
+PartialUEContextTransfer,
+PartialUEContextTransferAcknowledge,
+PartialUEContextTransferFailure,
+RachIndication,
+DataCollectionRequest,
+DataCollectionResponse,
+
+DataCollectionFailure,
+DataCollectionUpdate
+
+FROM XnAP-PDU-Contents
+
+id-handoverPreparation,
+id-sNStatusTransfer,
+id-handoverCancel,
+id-notificationControl,
+id-retrieveUEContext,
+id-rANPaging,
+id-xnUAddressIndication,
+id-uEContextRelease,
+id-secondaryRATDataUsageReport,
+id-sNGRANnodeAdditionPreparation,
+id-sNGRANnodeReconfigurationCompletion,
+id-mNGRANnodeinitiatedSNGRANnodeModificationPreparation,
+id-sNGRANnodeinitiatedSNGRANnodeModificationPreparation,
+id-mNGRANnodeinitiatedSNGRANnodeRelease,
+id-sNGRANnodeinitiatedSNGRANnodeRelease,
+id-sNGRANnodeCounterCheck,
+
+id-sNGRANnodeChange,
+id-activityNotification,
+id-rRCTransfer,
+id-xnRemoval,
+id-xnSetup,
+id-nGRANnodeConfigurationUpdate,
+id-e-UTRA-NR-CellResourceCoordination,
+id-cellActivation,
+id-reset,
+id-errorIndication,
+id-privateMessage,
+id-deactivateTrace,
+id-traceStart,
+id-handoverSuccess,
+id-conditionalHandoverCancel,
+id-earlyStatusTransfer,
+id-failureIndication,
+id-handoverReport,
+id-resourceStatusReportingInitiation,
+id-resourceStatusReporting,
+id-mobilitySettingsChange,
+id-accessAndMobilityIndication,
+id-cellTrafficTrace,
+
+```
+
+id-RANMulticastGroupPaging,
+id-scgFailureInformationReport,
+id-scgFailureTransfer,
+id-f1CTrafficTransfer,
+id-iABTransportMigrationManagement,
+id-iABTransportMigrationModification,
+id-iABResourceCoordination,
+id-retrieveUEContextConfirm,
+id-cPCCancel,
+id-partialUEContextTransfer,
+id-rachIndication,
+id-dataCollectionReportingInitiation,
+id-dataCollectionReporting
+
+```
+
+FROM XnAP-Constants;
+
+```
+
+-- *****
+--
+-- Interface Elementary Procedure Class
+--
+-- *****
+
+```
+
+```
+
+XNAP-ELEMENTARY-PROCEDURE ::= CLASS {
+ &InitiatingMessage ,
+ &SuccessfulOutcome OPTIONAL,
+ &UnsuccessfulOutcome OPTIONAL,
+ &procedureCode ProcedureCode UNIQUE,
+ &criticality Criticality DEFAULT ignore
+}
+
+WITH SYNTAX {
+ INITIATING MESSAGE &InitiatingMessage
+ [SUCCESSFUL OUTCOME &SuccessfulOutcome]
+ [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]
+ PROCEDURE CODE &procedureCode
+ [CRITICALITY &criticality]
+}
+
+-- *****
+--
+-- Interface PDU Definition
+--
+-- *****
+
+XnAP-PDU ::= CHOICE {
+
+```
+
+```
+ initiatingMessage InitiatingMessage,
+ successfulOutcome SuccessfulOutcome,
+ unsuccessfulOutcome UnsuccessfulOutcome,
+ ...
+}
+
+InitiatingMessage ::= SEQUENCE {
+ procedureCode XNP-ELEMENTARY-PROCEDURE.&procedureCode ({XNP-ELEMENTARY-PROCEDURES}),
+ criticality XNP-ELEMENTARY-PROCEDURE.&criticality ({XNP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value XNP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({XNP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+SuccessfulOutcome ::= SEQUENCE {
+ procedureCode XNP-ELEMENTARY-PROCEDURE.&procedureCode ({XNP-ELEMENTARY-PROCEDURES}),
+ criticality XNP-ELEMENTARY-PROCEDURE.&criticality ({XNP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value XNP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({XNP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+UnsuccessfulOutcome ::= SEQUENCE {
+ procedureCode XNP-ELEMENTARY-PROCEDURE.&procedureCode ({XNP-ELEMENTARY-PROCEDURES}),
+ criticality XNP-ELEMENTARY-PROCEDURE.&criticality ({XNP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+ value XNP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({XNP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+```
+
+```
+
+-- **************************************************************
+--
+-- Interface Elementary Procedure List
+--
+-- **************************************************************
+
+```
+
+```
+
+XNAP-ELEMENTARY-PROCEDURES XNAP-ELEMENTARY-PROCEDURE ::= {
+ XNAP-ELEMENTARY-PROCEDURES-CLASS-1 |
+ XNAP-ELEMENTARY-PROCEDURES-CLASS-2 ,
+ ...
+}
+
+```
+
+```
+
+XNAP-ELEMENTARY-PROCEDURES-CLASS-1 XNAP-ELEMENTARY-PROCEDURE ::= {
+ handoverPreparation |
+ retrieveUEContext |
+ sNGRANnodeAdditionPreparation |
+ mNGRANnodeinitiatedSNGRANnodeModificationPreparation |
+ sNGRANnodeinitiatedSNGRANnodeModificationPreparation |
+ mNGRANnodeinitiatedSNGRANnodeRelease |
+ sNGRANnodeinitiatedSNGRANnodeRelease |
+ sNGRANnodeChange |
+ xnRemoval |
+}
+
+```
+
+```
+ xnSetup |
+ nGRANnodeConfigurationUpdate |
+ e-UTRA-NR-CellResourceCoordination |
+ cellActivation |
+ reset |
+ resourceStatusReportingInitiation |
+ mobilitySettingsChange |
+ iABTransportMigrationManagement |
+ iABTransportMigrationModification |
+ iABResourceCoordination |
+ partialUEContextTransfer |
+ dataCollectionReportingInitiation,
+ ...
+}
+```
+
+```
+XNAP-ELEMENTARY-PROCEDURES-CLASS-2 XNAP-ELEMENTARY-PROCEDURE ::= {
+ sNStatusTransfer |
+ handoverCancel |
+ rANPaging |
+ xnUAddressIndication |
+ uEContextRelease |
+ sNGRANnodeReconfigurationCompletion |
+ sNGRANnodeCounterCheck |
+}
+```
+
+| | |
+|-----------------------------|--|
+| rRCTransfer | |
+| errorIndication | |
+| privateMessage | |
+| notificationControl | |
+| activityNotification | |
+| secondaryRATDataUsageReport | |
+| deactivateTrace | |
+| traceStart | |
+| handoverSuccess | |
+| conditionalHandoverCancel | |
+| earlyStatusTransfer | |
+| failureIndication | |
+| handoverReport | |
+| resourceStatusReporting | |
+| accessAndMobilityIndication | |
+| cellTrafficTrace | |
+| rANMulticastGroupPaging | |
+| scgFailureInformationReport | |
+| scgFailureTransfer | |
+| flCTrafficTransfer | |
+| retrieveUEContextConfirm | |
+| cPCCancel | |
+| rachIndication | |
+
+```
+ dataCollectionReporting,
+ ...
+}
+
+-- *****
+--
+-- Interface Elementary Procedures
+--
+-- *****
+
+handoverPreparation XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE HandoverRequest
+ SUCCESSFUL OUTCOME HandoverRequestAcknowledge
+ UNSUCCESSFUL OUTCOME HandoverPreparationFailure
+ PROCEDURE CODE id-handoverPreparation
+ CRITICALITY reject
+}
+
+sNStatusTransfer XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SNStatusTransfer
+ PROCEDURE CODE id-sNStatusTransfer
+}
+```
+
+```
+ CRITICALITY ignore
+
+ }
+
+ handoverCancel XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE HandoverCancel
+
+ PROCEDURE CODE id-handoverCancel
+
+ CRITICALITY ignore
+
+ }
+
+ retrieveUEContext XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE RetrieveUEContextRequest
+
+ SUCCESSFUL OUTCOME RetrieveUEContextResponse
+
+ UNSUCCESSFUL OUTCOME RetrieveUEContextFailure
+
+ PROCEDURE CODE id-retrieveUEContext
+
+ CRITICALITY reject
+
+ }
+
+ rANPaging XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE RANPaging
+
+ PROCEDURE CODE id-rANPaging
+```
+
+```
+ CRITICALITY reject
+
+ }
+
+ xnUAddressIndication XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE XnUAddressIndication
+
+ PROCEDURE CODE id-xnUAddressIndication
+
+ CRITICALITY reject
+
+ }
+
+ uEContextRelease XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE UEContextRelease
+
+ PROCEDURE CODE id-uEContextRelease
+
+ CRITICALITY reject
+
+ }
+
+ sNGRANnodeAdditionPreparation XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE SNodeAdditionRequest
+
+ SUCCESSFUL OUTCOME SNodeAdditionRequestAcknowledge
+
+ UNSUCCESSFUL OUTCOME SNodeAdditionRequestReject
+
+ PROCEDURE CODE id-sNGRANnodeAdditionPreparation
+```
+
+```
+ CRITICALITY reject
+
+ }
+
+ sNGRANnodeReconfigurationCompletion XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE SNodeReconfigurationComplete
+
+ PROCEDURE CODE id-sNGRANnodeReconfigurationCompletion
+
+ CRITICALITY reject
+
+ }
+
+ mNGRANnodeinitiatedSNGRANnodeModificationPreparation XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE SNodeModificationRequest
+
+ SUCCESSFUL OUTCOME SNodeModificationRequestAcknowledge
+
+ UNSUCCESSFUL OUTCOME SNodeModificationRequestReject
+
+ PROCEDURE CODE id-mNGRANnodeinitiatedSNGRANnodeModificationPreparation
+
+ CRITICALITY reject
+
+ }
+
+ sNGRANnodeinitiatedSNGRANnodeModificationPreparation XNAP-ELEMENTARY-PROCEDURE ::= {
+
+ INITIATING MESSAGE SNodeModificationRequired
+
+ SUCCESSFUL OUTCOME SNodeModificationConfirm
+```
+
+```
+UNSUCCESSFUL OUTCOME SNodeModificationRefuse
+PROCEDURE CODE id-sNGRANnodeinitiatedSNGRANnodeModificationPreparation
+CRITICALITY reject
+}
+```
+
+```
+mNGRANnodeinitiatedSNGRANnodeRelease XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SNodeReleaseRequest
+ SUCCESSFUL OUTCOME SNodeReleaseRequestAcknowledge
+ UNSUCCESSFUL OUTCOME SNodeReleaseReject
+ PROCEDURE CODE id-mNGRANnodeinitiatedSNGRANnodeRelease
+ CRITICALITY reject
+}
+```
+
+```
+sNGRANnodeinitiatedSNGRANnodeRelease XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SNodeReleaseRequired
+ SUCCESSFUL OUTCOME SNodeReleaseConfirm
+ PROCEDURE CODE id-sNGRANnodeinitiatedSNGRANnodeRelease
+ CRITICALITY reject
+}
+```
+
+```
+sNGRANnodeCounterCheck XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SNodeCounterCheckRequest
+ PROCEDURE CODE id-sNGRANnodeCounterCheck
+ CRITICALITY reject
+}
+```
+
+```
+sNGRANnodeChange XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SNodeChangeRequired
+ SUCCESSFUL OUTCOME SNodeChangeConfirm
+ UNSUCCESSFUL OUTCOME SNodeChangeRefuse
+ PROCEDURE CODE id-sNGRANnodeChange
+ CRITICALITY reject
+}
+```
+
+```
+rRCTransfer XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RRCTransfer
+ PROCEDURE CODE id-rRCTransfer
+ CRITICALITY reject
+}
+```
+
+```
+xnRemoval XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE XnRemovalRequest
+ SUCCESSFUL OUTCOME XnRemovalResponse
+ UNSUCCESSFUL OUTCOME XnRemovalFailure
+ PROCEDURE CODE id-xnRemoval
+ CRITICALITY reject
+}
+
+xnSetup XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE XnSetupRequest
+ SUCCESSFUL OUTCOME XnSetupResponse
+ UNSUCCESSFUL OUTCOME XnSetupFailure
+ PROCEDURE CODE id-xnSetup
+ CRITICALITY reject
+}
+
+nGRANnodeConfigurationUpdate XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE NGRANNodeConfigurationUpdate
+ SUCCESSFUL OUTCOME NGRANNodeConfigurationUpdateAcknowledge
+ UNSUCCESSFUL OUTCOME NGRANNodeConfigurationUpdateFailure
+ PROCEDURE CODE id-nGRANnodeConfigurationUpdate
+```
+
+```
+ CRITICALITY reject
+
+ }
+
+ partialUEContextTransfer XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE PartialUEContextTransfer
+ SUCCESSFUL OUTCOME PartialUEContextTransferAcknowledge
+ UNSUCCESSFUL OUTCOME PartialUEContextTransferFailure
+ PROCEDURE CODE id-partialUEContextTransfer
+ CRITICALITY reject
+ }
+
+ e-UTRA-NR-CellResourceCoordination XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE E-UTRA-NR-CellResourceCoordinationRequest
+ SUCCESSFUL OUTCOME E-UTRA-NR-CellResourceCoordinationResponse
+ PROCEDURE CODE id-e-UTRA-NR-CellResourceCoordination
+ CRITICALITY reject
+ }
+
+ cellActivation XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE CellActivationRequest
+ SUCCESSFUL OUTCOME CellActivationResponse
+ UNSUCCESSFUL OUTCOME CellActivationFailure
+ }
+```
+
+```
+ PROCEDURE CODE id-cellActivation
+ CRITICALITY reject
+}
+
+reset XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ResetRequest
+ SUCCESSFUL OUTCOME ResetResponse
+ PROCEDURE CODE id-reset
+ CRITICALITY reject
+}
+
+errorIndication XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ErrorIndication
+ PROCEDURE CODE id-errorIndication
+ CRITICALITY ignore
+}
+
+notificationControl XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE NotificationControlIndication
+ PROCEDURE CODE id-notificationControl
+```
+
+```
+ CRITICALITY ignore
+
+ }
+
+ activityNotification XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ActivityNotification
+ PROCEDURE CODE id-activityNotification
+ CRITICALITY ignore
+ }
+
+ privateMessage XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE PrivateMessage
+ PROCEDURE CODE id-privateMessage
+ CRITICALITY ignore
+ }
+
+ secondaryRATDataUsageReport XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE SecondaryRATDataUsageReport
+ PROCEDURE CODE id-secondaryRATDataUsageReport
+ CRITICALITY reject
+ }
+```
+
+```
+deactivateTrace XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE DeactivateTrace
+ PROCEDURE CODE id-deactivateTrace
+ CRITICALITY ignore
+}
+
+traceStart XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE TraceStart
+ PROCEDURE CODE id-traceStart
+ CRITICALITY ignore
+}
+
+handoverSuccess XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE HandoverSuccess
+ PROCEDURE CODE id-handoverSuccess
+ CRITICALITY ignore
+}
+
+conditionalHandoverCancel XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ConditionalHandoverCancel
+ PROCEDURE CODE id-conditionalHandoverCancel
+ CRITICALITY ignore
+}
+```
+
+```
+earlyStatusTransfer XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE EarlyStatusTransfer
+ PROCEDURE CODE id-earlyStatusTransfer
+ CRITICALITY ignore
+}
+
+failureIndication XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE FailureIndication
+ PROCEDURE CODE id-failureIndication
+ CRITICALITY ignore
+}
+
+handoverReport XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE HandoverReport
+ PROCEDURE CODE id-handoverReport
+ CRITICALITY ignore
+}
+
+resourceStatusReportingInitiation XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ResourceStatusRequest
+ SUCCESSFUL OUTCOME ResourceStatusResponse
+ UNSUCCESSFUL OUTCOME ResourceStatusFailure
+}
+```
+
+```
+PROCEDURE CODE id-resourceStatusReportingInitiation
+CRITICALITY reject
+}
+```
+
+```
+resourceStatusReporting XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ResourceStatusUpdate
+ PROCEDURE CODE id-resourceStatusReporting
+ CRITICALITY ignore
+}
+```
+
+```
+mobilitySettingsChange XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE MobilityChangeRequest
+ SUCCESSFUL OUTCOME MobilityChangeAcknowledge
+ UNSUCCESSFUL OUTCOME MobilityChangeFailure
+ PROCEDURE CODE id-mobilitySettingsChange
+ CRITICALITY reject
+}
+```
+
+```
+accessAndMobilityIndication XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE AccessAndMobilityIndication
+ PROCEDURE CODE id-accessAndMobilityIndication
+ CRITICALITY ignore
+}
+```
+
+```
+}
+
+cellTrafficTrace XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE CellTrafficTrace
+ PROCEDURE CODE id-cellTrafficTrace
+ CRITICALITY ignore
+}
+
+rANMulticastGroupPaging XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RANMulticastGroupPaging
+ PROCEDURE CODE id-RANMulticastGroupPaging
+ CRITICALITY reject
+}
+
+scgFailureInformationReport XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ScgFailureInformationReport
+ PROCEDURE CODE id-scgFailureInformationReport
+ CRITICALITY ignore
+}
+
+scgFailureTransfer XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE ScgFailureTransfer
+ PROCEDURE CODE id-scgFailureTransfer
+```
+
+```
+ CRITICALITY ignore
+
+ }
+
+ f1CTrafficTransfer XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE F1CTrafficTransfer
+ PROCEDURE CODE id-f1CTrafficTransfer
+ CRITICALITY reject
+ }
+
+ iABTransportMigrationManagement XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE IABTransportMigrationManagementRequest
+ SUCCESSFUL OUTCOME IABTransportMigrationManagementResponse
+ UNSUCCESSFUL OUTCOME IABTransportMigrationManagementReject
+ PROCEDURE CODE id-iABTransportMigrationManagement
+ CRITICALITY reject
+ }
+
+ iABTransportMigrationModification XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE IABTransportMigrationModificationRequest
+ SUCCESSFUL OUTCOME IABTransportMigrationModificationResponse
+ PROCEDURE CODE id-iABTransportMigrationModification
+ CRITICALITY reject
+ }
+```
+
+```
+iABResourceCoordination XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE IABResourceCoordinationRequest
+ SUCCESSFUL OUTCOME IABResourceCoordinationResponse
+ PROCEDURE CODE id-iABResourceCoordination
+ CRITICALITY reject
+}
+
+retrieveUEContextConfirm XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RetrieveUEContextConfirm
+ PROCEDURE CODE id-retrieveUEContextConfirm
+ CRITICALITY ignore
+}
+
+cPCCancel XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE CPCCancel
+ PROCEDURE CODE id-cPCCancel
+ CRITICALITY ignore
+}
+
+rachIndication XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE RachIndication
+ PROCEDURE CODE id-rachIndication
+```
+
+```
+ CRITICALITY ignore
+
+ }
+
+ dataCollectionReportingInitiation XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE DataCollectionRequest
+ SUCCESSFUL OUTCOME DataCollectionResponse
+ UNSUCCESSFUL OUTCOME DataCollectionFailure
+ PROCEDURE CODE id-dataCollectionReportingInitiation
+ CRITICALITY reject
+ }
+
+ dataCollectionReporting XNAP-ELEMENTARY-PROCEDURE ::= {
+ INITIATING MESSAGE DataCollectionUpdate
+ PROCEDURE CODE id-dataCollectionReporting
+ CRITICALITY ignore
+ }
+
+END
+
+-- ASN1STOP
+```
+
+## 9.3.4 PDU Definitions
+
+```
+-- ASN1START
+```
+
+```
+-- *****
+--
+-- PDU definitions for XnAP.
+--
+-- *****
+```
+
+```
+XnAP-PDU-Contents {
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+ ngran-access (22) modules (3) xnap (2) version1 (1) xnap-PDU-Contents (1) }
+```
+
+```
+DEFINITIONS AUTOMATIC TAGS ::=
+```
+
+```
+BEGIN
+```
+
+```
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+```
+
+```
+IMPORTS
+```
+
+```
+ ActivationIDforCellActivation,
+```
+
+AMF-Region-Information,
+AMF-UE-NGAP-ID,
+AS-SecurityInformation,
+AssistanceDataForRANPaging,
+AerialUESubscriptionInformation,
+A2XPC5QoSParameters,
+BitRate,
+Cause,
+CellAndCapacityAssistanceInfo-EUTRA,
+CellAndCapacityAssistanceInfo-NR,
+CellAssistanceInfo-EUTRA,
+CellAssistanceInfo-NR,
+CHOinformation-Req,
+CHOinformation-Ack,
+CHOinformation-AddReq,
+CHOinformation-AddReqAck,
+CHOinformation-ModReq,
+CHO-MRDC-EarlyDataForwarding,
+CHO-MRDC-Indicator,
+CPTransportLayerInformation,
+TNLA-To-Add-List,
+TNLA-To-Update-List,
+TNLA-To-Remove-List,
+
+TNLA-Setup-List,
+TNLA-Failed-To-Setup-List,
+CriticalityDiagnostics,
+XnUAddressInfoperPDUSession-List,
+DAPSResponseInfo-List,
+DataTrafficResourceIndication,
+DeliveryStatus,
+DesiredActNotificationLevel,
+DRB-ID,
+DRB-List,
+DRB-Number,
+DRBsSubjectToDLDiscarding-List,
+DRBsSubjectToEarlyStatusTransfer-List,
+DRBsSubjectToStatusTransfer-List,
+DRBToQoSFlowMapping-List,
+E-UTRA-CGI,
+ExpectedUEActivityBehaviour,
+ExpectedUEBehaviour,
+ExtendedUEIdentityIndexValue,
+FiveGCMobilityRestrictionListContainer,
+GlobalCell-ID,
+GlobalNG-RANNode-ID,
+GlobalNG-RANCell-ID,
+
+GUAMI,
+InterfaceInstanceIndication,
+I-RNTI,
+Local-NG-RAN-Node-Identifier,
+LocationInformationSNReporting,
+LocationReportingInformation,
+LowerLayerPresenceStatusChange,
+LTEA2XServicesAuthorized,
+LTEUESidelinkAggregateMaximumBitRate,
+LTEV2XServicesAuthorized,
+MR-DC-ResourceCoordinationInfo,
+ServedCells-E-UTRA,
+ServedCells-NR,
+ServedCellsToUpdate-E-UTRA,
+ServedCellsToUpdate-NR,
+MAC-I,
+MaskedIMEISV,
+MDT-Configuration,
+MDTPLMNList,
+MobilityRestrictionList,
+Neighbour-NG-RAN-Node-List,
+NG-RAN-Cell-Identity,
+NG-RANnodeUEXnAPID,
+
+NR-CGI,
+NE-DC-TDM-Pattern,
+NRA2XServicesAuthorized,
+NRUESidelinkAggregateMaximumBitRate,
+NRV2XServicesAuthorized,
+PagingDRX,
+EUTRAPagingeDRXInformation,
+PagingPriority,
+PartialListIndicator,
+PLMN-Identity,
+PDCPChangeIndication,
+PDUSessionAggregateMaximumBitRate,
+PDUSession-ID,
+PDUSession-List,
+PDUSession-List-withCause,
+PDUSession-List-withDataForwardingFromTarget,
+PDUSession-List-withDataForwardingRequest,
+PDUSessionResourcesAdmitted-List,
+PDUSessionResourcesNotAdmitted-List,
+PDUSessionResourcesToBeSetup-List,
+PDUSessionResourceChangeRequiredInfo-SNterminated,
+PDUSessionResourceChangeRequiredInfo-MNterminated,
+PDUSessionResourceChangeConfirmInfo-SNterminated,
+
+PDUSessionResourceChangeConfirmInfo-MNterminated,
+PDUSessionResourceSecondaryRATUsageList,
+PDUSessionResourceSetupInfo-SNterminated,
+PDUSessionResourceSetupInfo-MNterminated,
+PDUSessionResourceSetupResponseInfo-SNterminated,
+PDUSessionResourceSetupResponseInfo-MNterminated,
+PDUSessionResourceModificationInfo-SNterminated,
+PDUSessionResourceModificationInfo-MNterminated,
+PDUSessionResourceModificationResponseInfo-SNterminated,
+PDUSessionResourceModificationResponseInfo-MNterminated,
+PDUSessionResourceModConfirmInfo-SNterminated,
+PDUSessionResourceModConfirmInfo-MNterminated,
+PDUSessionResourceModRqdInfo-SNterminated,
+PDUSessionResourceModRqdInfo-MNterminated,
+PDUSessionType,
+PC5QoSParameters,
+QoSFlowIdentifier,
+QoSFlowNotificationControlIndicationInfo,
+QoSFlows-List,
+RANPagingArea,
+ResetRequestTypeInfo,
+ResetResponseTypeInfo,
+RFSP-Index,
+
+RRRConfigIndication,
+RRRResumeCause,
+SCGConfigurationQuery,
+SCGreconfigNotification,
+SecurityIndication,
+S-NG-RANnode-SecurityKey,
+SpectrumSharingGroupID,
+SplitSRBsTypes,
+S-NG-RANnode-Addition-Trigger-Ind,
+S-NSSAI,
+TargetCellList,
+TAISupport-List,
+Target-CGI,
+TimeToWait,
+TraceActivation,
+UEAggregateMaximumBitRate,
+UEContextID,
+UEContextInfoRetrUECtxtResp,
+UEContextKeptIndicator,
+UEHistoryInformation,
+UEIdentityIndexValue,
+UERadioCapabilityForPaging,
+UERadioCapabilityID,
+
+UERANPagingIdentity,
+UESecurityCapabilities,
+UPTransportLayerInformation,
+UserPlaneTrafficActivityReport,
+XnBenefitValue,
+RANPagingFailure,
+TNLConfigurationInfo,
+MaximumCellListSize,
+MessageOversizeNotification,
+NG-RANTraceID,
+MobilityInformation,
+InitiatingCondition-FailureIndication,
+HandoverReportType,
+TargetCellinEUTRAN,
+C-RNTI,
+UERLFReportContainer,
+Measurement-ID,
+RegistrationRequest,
+ReportCharacteristics,
+CellToReport,
+ReportingPeriodicity,
+CellMeasurementResult,
+UEHistoryInformationFromTheUE,
+
+MobilityParametersInformation,
+MobilityParametersModificationRange,
+RAReport,
+IABNodeIndication,
+SNTriggered,
+SCGIndicator,
+UESpecificDRX,
+DirectForwardingPathAvailability,
+TransportLayerAddress,
+PrivacyIndicator,
+URIaddress,
+MBS-Session-ID,
+UEIdentityIndexList-MBSGroupPaging,
+MBS-SessionInformation-List,
+MBS-SessionInformationResponse-List,
+SuccessfulHOReportInformation,
+PSCellHistoryInformationRetrieve,
+SSBOffsets-List,
+NG-RANnode2SSBOffsetsModificationRange,
+Coverage-Modification-List,
+SCGFailureReportContainer,
+SNMobilityInformation,
+PSCellChangeHistory,
+
+CHOConfiguration,
+SCGUEHistoryInformation,
+FlCTrafficContainer,
+NoPDUSessionIndication,
+IAB-TNL-Address-Request,
+IAB-TNL-Address-Response,
+TrafficIndex,
+TrafficProfile,
+TrafficToBeReleaseInformation,
+Fl-TerminatingTopologyBHInformation,
+Non-Fl-TerminatingTopologyBHInformation,
+BHInfoList,
+IABTNLAddress,
+IABCellInformation,
+IABTNLAddressException,
+TimeSynchronizationAssistanceInformation,
+SCGActivationRequest,
+SCGActivationStatus,
+CPAInformationRequest,
+CPAInformationAck,
+CPCInformationRequired,
+CPCInformationConfirm,
+CPAInformationModReq,
+
+CPAInformationModReqAck,
+CPC-DataForwarding-Indicator,
+CPCInformationUpdate,
+CPACInformationModRequired,
+QMCConfigInfo,
+FiveGProSeAuthorized,
+FiveGProSePC5QoSParameters,
+ServedCellSpecificInfoReq-NR,
+NRPagingeDRXInformation,
+NRPagingeDRXInformationforRRCINACTIVE,
+SDTSupportRequest,
+SDT-Termination-Request,
+SDTPartialUEContextInfo,
+SDTDataForwardingDRBList,
+PEIPSassistanceInformation,
+UESliceMaximumBitRateList,
+PagingCause,
+MDTPLMNModificationList,
+F1-terminatingIAB-donorIndicator,
+SRB-ID,
+AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated,
+HashedUEIdentityIndexValue,
+MBS-DataForwarding-Indicator,
+
+IABAuthorizationStatus,
+NID,
+MT-SDT-Information,
+PosPartialUEContextInfo,
+SRSConfiguration,
+RaReportIndicationList,
+SuccessfulPSCellChangeReportInformation,
+CPACConfiguration,
+TimeSinceFailure,
+SPRAvailability,
+DLLBTFailureInformationRequest,
+DLLBTFailureInformationList,
+CellBasedUETrajectoryPrediction,
+DataCollectionID,
+RequestedPredictionTime,
+NodeMeasurementInitiationResult-List,
+CellMeasurementInitiationResult-List,
+UEAssociatedInfoResult-List,
+EnergyCost,
+UETrajectoryCollectionConfiguration,
+UEPerformanceCollectionConfiguration,
+CellMeasurementResultForDataCollection,
+CellToReportForDataCollection-List,
+
+CandidateRelayUEInfoList,
+NRPagingLongeDRXInformationforRRCINACTIVE,
+QMCCoordinationRequest,
+QMCCoordinationResponse,
+SNRelatedQMCInfoAtMN,
+QoERVQoEReportingPaths,
+DirectForwardingPathAvailabilityWithSourceMN,
+Conditional-Reconfig-List,
+PDUSetbasedHandlingIndicator,
+MobileIAB-AuthorizationStatus,
+BAPAddress
+
+FROM XnAP-IEs
+
+PrivateIE-Container{},
+ProtocolExtensionContainer{},
+ProtocolIE-Container{},
+ProtocolIE-ContainerList{},
+ProtocolIE-ContainerPair{},
+ProtocolIE-ContainerPairList{},
+ProtocolIE-Single-Container{},
+
+XNAP-PRIVATE-IES,
+XNAP-PROTOCOL-EXTENSION,
+XNAP-PROTOCOL-IES,
+XNAP-PROTOCOL-IES-PAIR
+
+FROM XnAP-Containers
+
+id-A2XPC5QoSParameters,
+id-ActivatedServedCells,
+id-ActivationIDforCellActivation,
+id-AdditionalDRBIDs,
+id-AerialUESubscriptionInformation,
+id-AMF-Region-Information,
+id-AMF-Region-Information-To-Add,
+id-AMF-Region-Information-To-Delete,
+id-AssistanceDataForRANPaging,
+id-AvailableDRBIDs,
+id-Cause,
+id-cellAssistanceInfo-EUTRA,
+id-cellAssistanceInfo-NR,
+id-CellAndCapacityAssistanceInfo-EUTRA,
+id-CellAndCapacityAssistanceInfo-NR,
+id-ConfigurationUpdateInitiatingNodeChoice,
+
+id-UEContextID,
+id-CriticalityDiagnostics,
+id-XnUAddressInfoperPDUSession-List,
+id-DesiredActNotificationLevel,
+id-DRBsSubjectToStatusTransfer-List,
+id-ExpectedUEBehaviour,
+id-ExtendedUEIdentityIndexValue,
+id-FiveGCMobilityRestrictionListContainer,
+id-GlobalNG-RAN-node-ID,
+id-GUAMI,
+id-indexToRatFrequSelectionPriority,
+id-List-of-served-cells-E-UTRA,
+id-List-of-served-cells-NR,
+id-LocationInformationSN,
+id-LocationInformationSNReporting,
+id-LocationReportingInformation,
+id-LTEA2XServicesAuthorized,
+id-LTEA2XUEPC5AggregateMaximumBitRate,
+id-LTEUESidelinkAggregateMaximumBitRate,
+id-LTEV2XServicesAuthorized,
+id-MAC-I,
+id-MaskedIMEISV,
+id-MDT-Configuration,
+
+id-MDTPLMNList,
+id-MN-to-SN-Container,
+id-MobilityRestrictionList,
+id-M-NG-RANnodeUEXnAPID,
+id-new-NG-RAN-Cell-Identity,
+id-newNG-RANnodeUEXnAPID,
+id-NRA2XServicesAuthorized,
+id-NRA2XUEPC5AggregateMaximumBitRate,
+id-NRUESidelinkAggregateMaximumBitRate,
+id-NRV2XServicesAuthorized,
+id-oldNG-RANnodeUEXnAPID,
+id-OldtoNewNG-RANnodeResumeContainer,
+id-PagingCause,
+id-PagingDRX,
+id-EUTRAPagingeDRXInformation,
+id-PagingPriority,
+id-PartialListIndicator-EUTRA,
+id-PartialListIndicator-NR,
+id-PCellID,
+id-PDUSessionResourceSecondaryRATUsageList,
+id-PDUSessionResourcesActivityNotifyList,
+id-PDUSessionResourcesAdmitted-List,
+id-PDUSessionResourcesNotAdmitted-List,
+
+id-PDUSessionResourcesNotifyList,
+id-PDUSessionToBeAddedAddReq,
+id-PDUSessionToBeReleased-RelReqAck,
+id-procedureStage,
+id-RANPagingArea,
+id-requestedSplitSRB,
+id-RequiredNumberOfDRBIDs,
+id-ResetRequestTypeInfo,
+id-ResetResponseTypeInfo,
+id-RespondingNodeTypeConfigUpdateAck,
+id-RRCResumeCause,
+id-SCGreconfigNotification,
+id-selectedPLMN,
+id-ServedCellsToActivate,
+id-servedCellsToUpdate-E-UTRA,
+id-ServedCellsToUpdateInitiatingNodeChoice,
+id-servedCellsToUpdate-NR,
+id-sourceNG-RANnodeUEXnAPID,
+id-SpareDRBIDs,
+id-S-NG-RANnodeMaxIPDataRate-UL,
+id-S-NG-RANnodeMaxIPDataRate-DL,
+id-S-NG-RANnodeUEXnAPID,
+id-TAISupport-list,
+
+id-Target2SourceNG-RANnodeTranspContainer,
+id-targetCellGlobalID,
+id-targetNG-RANnodeUEXnAPID,
+id-TimeToWait,
+id-TNLA-To-Add-List,
+id-TNLA-To-Update-List,
+id-TNLA-To-Remove-List,
+id-TNLA-Setup-List,
+id-TNLA-Failed-To-Setup-List,
+id-TraceActivation,
+id-UEContextInfoHORequest,
+id-UEContextInfoRetrUECtxtResp,
+id-UEContextKeptIndicator,
+id-UEContextRefAtSN-HORequest,
+id-UEHistoryInformation,
+id-UEIdentityIndexValue,
+id-UERANPagingIdentity,
+id-UESecurityCapabilities,
+id-UserPlaneTrafficActivityReport,
+id-XnRemovalThreshold,
+id-PDUSessionAdmittedAddedAddReqAck,
+id-PDUSessionNotAdmittedAddReqAck,
+id-SN-to-MN-Container,
+
+id-RRConfigIndication,
+id-SplitSRB-RRCTransfer,
+id-UEReportRRCTransfer,
+id-PDUSessionReleasedList-RelConf,
+id-BearersSubjectToCounterCheck,
+id-PDUSessionToBeReleasedList-RelRqd,
+id-ResponseInfo-ReconfCompl,
+id-initiatingNodeType-ResourceCoordRequest,
+id-respondingNodeType-ResourceCoordResponse,
+id-PDUSessionToBeReleased-RelReq,
+id-PDUSession-SNChangeRequired-List,
+id-PDUSession-SNChangeConfirm-List,
+id-PDCPChangeIndication,
+id-PC5QoSParameters,
+id-SCGConfigurationQuery,
+id-UEContextInfo-SNModRequest,
+id-requestedSplitSRBrelease,
+id-PDUSessionAdmitted-SNModResponse,
+id-PDUSessionNotAdmitted-SNModResponse,
+id-admittedSplitSRB,
+id-admittedSplitSRBrelease,
+id-PDUSessionAdmittedModSNModConfirm,
+id-PDUSessionReleasedSNModConfirm,
+
+id-s-ng-RANnode-SecurityKey,
+id-PDUSessionToBeModifiedSNModRequired,
+id-S-NG-RANnodeUE-AMBR,
+id-PDUSessionToBeReleasedSNModRequired,
+id-target-S-NG-RANnodeID,
+id-S-NSSAI,
+id-MR-DC-ResourceCoordinationInfo,
+id-RANPagingFailure,
+id-UERadioCapabilityForPaging,
+id-PDUSessionDataForwarding-SNModResponse,
+id-Secondary-MN-Xn-U-TNLInfoatM,
+id-NE-DC-TDM-Pattern,
+id-InterfaceInstanceIndication,
+id-S-NG-RANnode-Addition-Trigger-Ind,
+id-SNTriggered,
+id-DRBs-transferred-to-MN,
+id-TNLConfigurationInfo,
+id-MessageOversizeNotification,
+id-NG-RANTraceID,
+id-FastMCGRecoveryRRCTransfer-SN-to-MN,
+id-FastMCGRecoveryRRCTransfer-MN-to-SN,
+id-RequestedFastMCGRecoveryViaSRB3,
+id-AvailableFastMCGRecoveryViaSRB3,
+
+id-RequestedFastMCGRecoveryViaSRB3Release,
+id-ReleaseFastMCGRecoveryViaSRB3,
+id-CHOInformation-Req,
+id-CHOInformation-Ack,
+id-targetCellsToCancel,
+id-requestedTargetCellGlobalID,
+id-DAPSResponseInfo-List,
+id-CHO-MRDC-EarlyDataForwarding,
+id-CHO-MRDC-Indicator,
+id-MobilityInformation,
+id-InitiatingCondition-FailureIndication,
+id-UEHistoryInformationFromTheUE,
+id-HandoverReportType,
+id-HandoverCause,
+id-SourceCellCGI,
+id-TargetCellCGI,
+id-ReEstablishmentCellCGI,
+id-TargetCellinEUTRAN,
+id-SourceCellCRNTI,
+id-UERLFReportContainer,
+id-NGRAN-Node1-Measurement-ID,
+id-NGRAN-Node2-Measurement-ID,
+id-RegistrationRequest,
+
+id-ReportCharacteristics,
+id-CellToReport,
+id-ReportingPeriodicity,
+id-CellMeasurementResult,
+id-NG-RANnode1CellID,
+id-NG-RANnode2CellID,
+id-NG-RANnode1MobilityParameters,
+id-NG-RANnode2ProposedMobilityParameters,
+id-MobilityParametersModificationRange,
+id-RAReport,
+id-IABNodeIndication,
+id-UERadioCapabilityID,
+id-SCGIndicator,
+id-UESpecificDRX,
+id-PDUSessionExpectedUEActivityBehaviour,
+id-DirectForwardingPathAvailability,
+id-SourceNG-RAN-node-ID,
+id-TargetNodeID,
+id-ManagementBasedMDTPLMNList,
+id-PrivacyIndicator,
+id-TraceCollectionEntityIPAddress,
+id-TraceCollectionEntityURI,
+id-MBS-Session-ID,
+
+id-UEIdentityIndexList-MBSGroupPaging,
+id-MulticastRANPagingArea,
+id-MBS-SessionInformation-List,
+id-MBS-SessionInformationResponse-List,
+id-SuccessfulHOReportInformation,
+id-PSCellHistoryInformationRetrieve,
+id-SSBOffsets-List,
+id-NG-RANnode2SSBOffsetsModificationRange,
+id-Coverage-Modification-List,
+id-SourcePSCellCGI,
+id-FailedPSCellCGI,
+id-SCGFailureReportContainer,
+id-SNMobilityInformation,
+id-SourcePSCellID,
+id-SuitablePSCellCGI,
+id-PSCellChangeHistory,
+id-CHOConfiguration,
+id-SCGUEHistoryInformation,
+id-F1CTrafficContainer,
+id-NoPDUSessionIndication,
+id-F1-Terminating-IAB-DonorUEXnAPID,
+id-nonF1-Terminating-IAB-DonorUEXnAPID,
+id-IAB-TNL-Address-Request,
+
+id-IAB-TNL-Address-Response,
+id-TrafficToBeAddedList,
+id-TrafficToBeModifiedList,
+id-TrafficToBeReleaseInformation,
+id-TrafficAddedList,
+id-TrafficModifiedList,
+id-TrafficNotAddedList,
+id-TrafficNotModifiedList,
+id-TrafficRequiredToBeModifiedList,
+id-TrafficRequiredModifiedList,
+id-TrafficReleasedList,
+id-IABTNLAddressToBeAdded,
+id-IABTNLAddressToBeReleasedList,
+id-BoundaryNodeCellsList,
+id-ParentNodeCellsList,
+id-IABTNLAddressException,
+id-CHOinformation-AddReq,
+id-CHOinformation-AddReqAck,
+id-CHOinformation-ModReq,
+id-TimeSynchronizationAssistanceInformation,
+id-SCGActivationRequest,
+id-SCGActivationStatus,
+id-CPAInformationRequest,
+
+id-CPAInformationAck,
+id-CPCInformationRequired,
+id-CPCInformationConfirm,
+id-CPAInformationModReq,
+id-CPAInformationModReqAck,
+id-CPC-DataForwarding-Indicator,
+id-CPCInformationUpdate,
+id-CPACInformationModRequired,
+id-QMCConfigInfo,
+id-Local-NG-RAN-Node-Identifier,
+id-Neighbour-NG-RAN-Node-List,
+id-Local-NG-RAN-Node-Identifier-Removal,
+id-FiveGProSeAuthorized,
+id-FiveGProSePC5QoSParameters,
+id-FiveGProSeUEPC5AggregateMaximumBitRate,
+id-ServedCellSpecificInfoReq-NR,
+id-NRPagingeDRXInformation,
+id-NRPagingeDRXInformationforRRRCINACTIVE,
+id-SDTSupportRequest,
+id-SDT-SRB-between-NewNode-OldNode,
+id-SDT-Termination-Request,
+id-SDTPartialUEContextInfo,
+id-SDTDataForwardingDRBList,
+
+id-PEIPSassistanceInformation,
+id-UESliceMaximumBitRateList,
+id-S-NG-RANnodeUE-Slice-MBR,
+id-ManagementBasedMDTFLMNModificationList,
+id-F1-terminatingIAB-donorIndicator,
+id-AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated,
+id-HashedUEIdentityIndexValue,
+id-MBS-DataForwarding-Indicator,
+id-IABAuthorizationStatus,
+id-SelectedNID,
+id-MT-SDT-Information,
+id-PosPartialUEContextInfo,
+id-SRSConfiguration,
+id-RaReportIndicationList,
+id-SuccessfulPSCellChangeReportInformation,
+id-CPACConfiguration,
+id-TargetCellCRNTI,
+id-TimeSinceFailure,
+id-SPRAvailability,
+id-DLLBTFailureInformationRequest,
+id-DLLBTFailureInformationList,
+id-CellBasedUETrajectoryPrediction,
+id-DataCollectionID,
+
+id-RequestedPredictionTime,
+id-NodeMeasurementInitiationResult-List,
+id-CellMeasurementInitiationResult-List,
+id-UEAssociatedInfoResult-List,
+id-EnergyCost,
+id-UEtrajectoryCollectionConfiguration,
+id-UEPerformanceCollectionConfiguration,
+id-CellMeasurementResultForDataCollection,
+id-CellToReportForDataCollection-List,
+id-CandidateRelayUEInfoList,
+id-NRCellsAndSSBsList,
+id-ActivatedNRCellsAndSSBsList,
+id-NRPagingLongeDRXInformationforRRINACTIVE,
+id-QMCCoordinationRequest,
+id-QMCCoordinationResponse,
+id-QoE-Measurement-Results,
+id-SNRelatedQMCInfoAtMN,
+id-Src-SN-to-Tgt-SNQMCInfoInquiry,
+id-DirectForwardingPathAvailabilityWithSourceMN,
+id-accessed-PSCellID,
+id-conditional-Reconfig-ToCancel-List,
+id-PDUSetbasedHandlingIndicator,
+id-MobileIAB-AuthorizationStatus,
+
+```
+
+id-MIAB-MT-BAP-Address,
+
+maxnoofCellsinNG-RANnode,
+maxnoofDRBs,
+maxnoofPDUSessions,
+maxnoofQoSFlows,
+maxnoofServedCellsIAB,
+maxnoofTrafficIndexEntries,
+maxnoofTLAsIAB,
+maxnoofBAPControlPDURLCCHs,
+maxnoofServingCells,
+maxnoofSSBAreas
+
+```
+
+FROM XnAP-Constants;
+
+```
+
+-- *****
+--
+-- HANDOVER REQUEST
+--
+-- *****
+
+```
+
+HandoverRequest ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{HandoverRequest-IEs}},
+
+ ...
+
+}
+
+HandoverRequest-IEs XNAP-PROTOCOL-IES ::= {
+
+| | | | |
+|---------------------------------------|--------------------|------------------------------------|---------------------|
+| { ID id-sourceNG-RANnodeUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-Cause | CRITICALITY reject | TYPE Cause | PRESENCE mandatory} |
+| { ID id-targetCellGlobalID | CRITICALITY reject | TYPE Target-CGI | PRESENCE mandatory} |
+| { ID id-GUAMI | CRITICALITY reject | TYPE GUAMI | PRESENCE mandatory} |
+| { ID id-UEContextInfoHORequest | CRITICALITY reject | TYPE UEContextInfoHORequest | PRESENCE mandatory} |
+| { ID id-TraceActivation | CRITICALITY ignore | TYPE TraceActivation | PRESENCE optional } |
+| { ID id-MaskedIMEISV | CRITICALITY ignore | TYPE MaskedIMEISV | PRESENCE optional } |
+| { ID id-UEHistoryInformation | CRITICALITY ignore | TYPE UEHistoryInformation | PRESENCE mandatory} |
+| { ID id-UEContextRefAtSN-HORequest | CRITICALITY ignore | TYPE UEContextRefAtSN-HORequest | PRESENCE optional } |
+| { ID id-CHOinformation-Req | CRITICALITY reject | TYPE CHOinformation-Req | PRESENCE optional } |
+| { ID id-NRV2XServicesAuthorized | CRITICALITY ignore | TYPE NRV2XServicesAuthorized | PRESENCE optional } |
+| { ID id-LTEV2XServicesAuthorized | CRITICALITY ignore | TYPE LTEV2XServicesAuthorized | PRESENCE optional } |
+| { ID id-PC5QoSParameters | CRITICALITY ignore | TYPE PC5QoSParameters | PRESENCE optional } |
+| { ID id-MobilityInformation | CRITICALITY ignore | TYPE MobilityInformation | PRESENCE optional } |
+| { ID id-UEHistoryInformationFromTheUE | CRITICALITY ignore | TYPE UEHistoryInformationFromTheUE | PRESENCE optional } |
+| { ID id-IABNodeIndication | CRITICALITY reject | TYPE IABNodeIndication | PRESENCE optional } |
+| { ID id-NoPDUSessionIndication | CRITICALITY ignore | TYPE NoPDUSessionIndication | PRESENCE optional } |
+
+```
+
+{ ID id-TimeSynchronizationAssistanceInformation CRITICALITY ignore TYPE TimeSynchronizationAssistanceInformation PRESENCE optional }|
+{ ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional }|
+{ ID id-FiveGProSeAuthorized CRITICALITY ignore TYPE FiveGProSeAuthorized PRESENCE optional }|
+{ ID id-FiveGProSePC5QoSParameters CRITICALITY ignore TYPE FiveGProSePC5QoSParameters PRESENCE optional }|
+{ ID id-DLLBTFailureInformationRequest CRITICALITY ignore TYPE DLLBTFailureInformationRequest PRESENCE optional }|
+{ ID id-AerialUESubscriptionInformation CRITICALITY ignore TYPE AerialUESubscriptionInformation PRESENCE optional }|
+{ ID id-NRA2XServicesAuthorized CRITICALITY ignore TYPE NRA2XServicesAuthorized PRESENCE optional }|
+{ ID id-LTEA2XServicesAuthorized CRITICALITY ignore TYPE LTEA2XServicesAuthorized PRESENCE optional }|
+{ ID id-A2XPC5QoSParameters CRITICALITY ignore TYPE A2XPC5QoSParameters PRESENCE optional }|
+{ ID id-CellBasedUETrajectoryPrediction CRITICALITY ignore TYPE CellBasedUETrajectoryPrediction PRESENCE optional }|
+{ ID id-DataCollectionID CRITICALITY ignore TYPE DataCollectionID PRESENCE optional }|
+{ ID id-CandidateRelayUEInfoList CRITICALITY reject TYPE CandidateRelayUEInfoList PRESENCE optional }|
+{ ID id-SNRelatedQMCInfoAtMN CRITICALITY ignore TYPE SNRelatedQMCInfoAtMN PRESENCE optional }|
+{ ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional }|
+{ ID id-MobileIAB-AuthorizationStatus CRITICALITY reject TYPE MobileIAB-AuthorizationStatus PRESENCE optional },
+...
+}
+
+```
+
+```
+UEContextInfoHORequest ::= SEQUENCE {
+```
+
+```
+
+ ng-c-UE-reference AMF-UE-NGAP-ID,
+ cp-TNL-info-source CPTransportLayerInformation,
+ ueSecurityCapabilities USESecurityCapabilities,
+ securityInformation AS-SecurityInformation,
+
+```
+
+```
+
+indexToRatFrequencySelectionPriority RFSP-Index OPTIONAL,
+ue-AMBR UEAgregateMaximumBitRate,
+pduSessionResourcesToBeSetup-List PDUSessionResourcesToBeSetup-List,
+rrc-Context OCTET STRING,
+locationReportingInformation LocationReportingInformation OPTIONAL,
+mrl MobilityRestrictionList OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {UEContextInfoHORequest-ExtIEs} } OPTIONAL,
+...
+}
+
+```
+
+```
+UEContextInfoHORequest-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+
+{ ID id-FiveGCMobilityRestrictionListContainer CRITICALITY ignore EXTENSION FiveGCMobilityRestrictionListContainer PRESENCE optional }|
+{ ID id-NRUESidelinkAggregateMaximumBitRate CRITICALITY ignore EXTENSION NRUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+{ ID id-LTEUESidelinkAggregateMaximumBitRate CRITICALITY ignore EXTENSION LTEUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+{ ID id-MDTPLMNList CRITICALITY ignore EXTENSION MDTPLMNList PRESENCE optional }|
+{ ID id-UERadioCapabilityID CRITICALITY reject EXTENSION UERadioCapabilityID PRESENCE optional }|
+{ ID id-MBS-SessionInformation-List CRITICALITY ignore EXTENSION MBS-SessionInformation-List PRESENCE optional }|
+{ ID id-FiveGProSeUEPC5AggregateMaximumBitRate CRITICALITY ignore EXTENSION NRUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+{ ID id-UESliceMaximumBitRateList CRITICALITY ignore EXTENSION UESliceMaximumBitRateList PRESENCE optional }|
+{ ID id-NRA2XUEPC5AggregateMaximumBitRate CRITICALITY ignore EXTENSION NRUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+{ ID id-LTEA2XUEPC5AggregateMaximumBitRate CRITICALITY ignore EXTENSION LTEUESidelinkAggregateMaximumBitRate PRESENCE optional },
+...
+}
+
+```
+
+```
+
+UEContextRefAtSN-HORequest ::= SEQUENCE {
+ globalNG-RANNode-ID GlobalNG-RANNode-ID,
+ sN-NG-RANnodeUEXnAPID NG-RANnodeUEXnAPID,
+ iE-Extensions ProtocolExtensionContainer { {UEContextRefAtSN-HORequest-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+UEContextRefAtSN-HORequest-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- HANDOVER REQUEST ACKNOWLEDGE
+--
+-- *****
+
+```
+
+```
+
+HandoverRequestAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {HandoverRequestAcknowledge-IEs} },
+ ...
+}
+
+```
+
+```
+
+HandoverRequestAcknowledge-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionResourcesAdmitted-List CRITICALITY ignore TYPE PDUSessionResourcesAdmitted-List PRESENCE mandatory}|
+ { ID id-PDUSessionResourcesNotAdmitted-List CRITICALITY ignore TYPE PDUSessionResourcesNotAdmitted-List PRESENCE optional }|
+ { ID id-Target2SourceNG-RANnodeTranspContainer CRITICALITY ignore TYPE OCTET STRING PRESENCE mandatory}|
+ { ID id-UEContextKeptIndicator CRITICALITY ignore TYPE UEContextKeptIndicator PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-DRBs-transferred-to-MN CRITICALITY ignore TYPE DRB-List PRESENCE optional }|
+ { ID id-DAPSResponseInfo-List CRITICALITY reject TYPE DAPSResponseInfo-List PRESENCE optional }|
+ { ID id-CHOinformation-Ack CRITICALITY reject TYPE CHOinformation-Ack PRESENCE optional }|
+ { ID id-MBS-SessionInformationResponse-List CRITICALITY ignore TYPE MBS-SessionInformationResponse-List PRESENCE optional }|
+ { ID id-RRCConfigIndication CRITICALITY ignore TYPE RRCConfigIndication PRESENCE optional }|
+ { ID id-PDUSetbasedHandlingIndicator CRITICALITY ignore TYPE PDUSetbasedHandlingIndicator PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- HANDOVER PREPARATION FAILURE
+--
+-- *****
+
+```
+
+```
+
+HandoverPreparationFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{HandoverPreparationFailure-IEs}},
+ ...
+}
+
+```
+
+```
+
+HandoverPreparationFailure-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-requestedTargetCellGlobalID CRITICALITY reject TYPE Target-CGI PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- SN STATUS TRANSFER
+--
+-- *****
+
+```
+
+```
+
+SNStatusTransfer ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{SNStatusTransfer-IEs}},
+ ...
+}
+
+```
+
+```
+
+SNStatusTransfer-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-DRBsSubjectToStatusTransfer-List CRITICALITY ignore TYPE DRBsSubjectToStatusTransfer-List PRESENCE mandatory}|
+ { ID id-CHOConfiguration CRITICALITY ignore TYPE CHOConfiguration PRESENCE optional}|
+ { ID id-MobilityInformation CRITICALITY ignore TYPE MobilityInformation PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- UE CONTEXT RELEASE
+--
+-- *****
+
+```
+
+```
+
+UEContextRelease ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{UEContextRelease-IEs}},
+ ...
+}
+
+```
+
+```
+
+UEContextRelease-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+```
+
+```
+
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- HANDOVER CANCEL
+--
+-- *****
+
+```
+
+```
+
+HandoverCancel ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{HandoverCancel-IEs}},
+ ...
+}
+
+```
+
+```
+
+HandoverCancel-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE optional }|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-targetCellsToCancel CRITICALITY reject TYPE TargetCellList PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- HANDOVER SUCCESS
+--
+-- *****
+
+```
+
+```
+
+HandoverSuccess ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{HandoverSuccess-IEs}},
+ ...
+}
+
+```
+
+```
+
+HandoverSuccess-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-requestedTargetCellGlobalID CRITICALITY reject TYPE Target-CGI PRESENCE mandatory}|
+ { ID id-accessedPSCellID CRITICALITY ignore TYPE NR-CGI PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- CONDITIONAL HANDOVER CANCEL
+--
+-- *****
+
+```
+
+-- \*\*\*\*\*
+
+```
+
+ConditionalHandoverCancel ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ ConditionalHandoverCancel-IEs}},
+ ...
+}
+
+```
+
+```
+
+ConditionalHandoverCancel-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-targetCellsToCancel CRITICALITY reject TYPE TargetCellList PRESENCE optional}|
+ { ID id-conditional-Reconfig-ToCancel-List CRITICALITY reject TYPE Conditional-Reconfig-List PRESENCE optional},
+ ...
+}
+
+```
+
+-- \*\*\*\*\*
+
+--
+
+-- EARLY STATUS TRANSFER
+
+--
+
+-- \*\*\*\*\*
+
+```
+
+EarlyStatusTransfer ::= SEQUENCE {
+
+```
+
+```
+protocolIEs ProtocolIE-Container {{ EarlyStatusTransfer-IEs}},
+...
+}
+
+EarlyStatusTransfer-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-sourceNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-targetNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-procedureStage CRITICALITY reject TYPE ProcedureStageChoice PRESENCE mandatory},
+...
+}
+
+ProcedureStageChoice ::= CHOICE {
+ first-dl-count FirstDLCount,
+ dl-discarding DLDiscarding,
+ choice-extension ProtocolIE-Single-Container { ProcedureStageChoice-ExtIEs }
+}
+
+ProcedureStageChoice-ExtIEs XNAP-PROTOCOL-IES ::= {
+...
+}
+
+FirstDLCount ::= SEQUENCE {
+ dRBsSubjectToEarlyStatusTransfer DRBsSubjectToEarlyStatusTransfer-List,
+```
+
+```
+
+ iE-Extension ProtocolExtensionContainer { {FirstDLCount-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+FirstDLCount-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+DLDiscarding ::= SEQUENCE {
+ dRBsSubjectToDLDiscarding DRBsSubjectToDLDiscarding-List,
+ iE-Extension ProtocolExtensionContainer { {DLDiscarding-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+DLDiscarding-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- RAN PAGING
+--
+-- *****
+
+```
+
+RANPaging ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{RANPaging-IEs}},
+
+ ...
+
+}
+
+RANPaging-IEs XNAP-PROTOCOL-IES ::= {
+
+| | | | |
+|------------------------------------------------|--------------------|---------------------------------------------|---------------------|
+| { ID id-UEIdentityIndexValue | CRITICALITY reject | TYPE UEIdentityIndexValue | PRESENCE mandatory} |
+| { ID id-UERANPagingIdentity | CRITICALITY ignore | TYPE UERANPagingIdentity | PRESENCE mandatory} |
+| { ID id-PagingDRX | CRITICALITY ignore | TYPE PagingDRX | PRESENCE mandatory} |
+| { ID id-RANPagingArea | CRITICALITY reject | TYPE RANPagingArea | PRESENCE mandatory} |
+| { ID id-PagingPriority | CRITICALITY ignore | TYPE PagingPriority | PRESENCE optional } |
+| { ID id-AssistanceDataForRANPaging | CRITICALITY ignore | TYPE AssistanceDataForRANPaging | PRESENCE optional } |
+| { ID id-UERadioCapabilityForPaging | CRITICALITY ignore | TYPE UERadioCapabilityForPaging | PRESENCE optional } |
+| { ID id-ExtendedUEIdentityIndexValue | CRITICALITY ignore | TYPE ExtendedUEIdentityIndexValue | PRESENCE optional } |
+| { ID id-EUTRAPagingeDRXInformation | CRITICALITY ignore | TYPE EUTRAPagingeDRXInformation | PRESENCE optional } |
+| { ID id-UESpecificDRX | CRITICALITY ignore | TYPE UESpecificDRX | PRESENCE optional } |
+| { ID id-NRPagingeDRXInformation | CRITICALITY ignore | TYPE NRPagingeDRXInformation | PRESENCE optional } |
+| { ID id-NRPagingeDRXInformationforRRRCINACTIVE | CRITICALITY ignore | TYPE NRPagingeDRXInformationforRRRCINACTIVE | PRESENCE optional } |
+| { ID id-PagingCause | CRITICALITY ignore | TYPE PagingCause | PRESENCE optional } |
+| { ID id-PEIPSassistanceInformation | CRITICALITY ignore | TYPE PEIPSassistanceInformation | PRESENCE optional } |
+| { ID id-HashedUEIdentityIndexValue | CRITICALITY ignore | TYPE HashedUEIdentityIndexValue | PRESENCE optional } |
+| { ID id-MT-SDT-Information | CRITICALITY ignore | TYPE MT-SDT-Information | PRESENCE optional } |
+
+```
+
+ { ID id-NRPagingLongeDRXInformationforRRRCINACTIVE CRITICALITY ignore TYPE NRPagingLongeDRXInformationforRRRCINACTIVE PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- RETRIEVE UE CONTEXT REQUEST
+--
+-- *****
+
+```
+
+```
+
+RetrieveUEContextRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{RetrieveUEContextRequest-IEs}},
+ ...
+}
+
+```
+
+```
+
+RetrieveUEContextRequest-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-UEContextID CRITICALITY reject TYPE UEContextID PRESENCE mandatory}|
+ { ID id-MAC-I CRITICALITY reject TYPE MAC-I PRESENCE mandatory}|
+ { ID id-new-NG-RAN-Cell-Identity CRITICALITY reject TYPE NG-RAN-Cell-Identity PRESENCE mandatory}|
+ { ID id-RRRCResumeCause CRITICALITY ignore TYPE RRCResumeCause PRESENCE optional }|
+ { ID id-SDTSupportRequest CRITICALITY ignore TYPE SDTSupportRequest PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+}
+
+-- *****
+--
+-- RETRIEVE UE CONTEXT RESPONSE
+--
+-- *****
+
+```
+
+```
+
+RetrieveUEContextResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ RetrieveUEContextResponse-IEs}},
+ ...
+}
+
+```
+
+```
+
+RetrieveUEContextResponse-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-oldNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-GUAMI CRITICALITY reject TYPE GUAMI PRESENCE mandatory}|
+ { ID id-UEContextInfoRetrUECtxtResp CRITICALITY reject TYPE UEContextInfoRetrUECtxtResp PRESENCE mandatory}|
+ { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE optional }|
+ { ID id-MaskedIMEISV CRITICALITY ignore TYPE MaskedIMEISV PRESENCE optional }|
+ { ID id-LocationReportingInformation CRITICALITY ignore TYPE LocationReportingInformation PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-NRV2XServicesAuthorized CRITICALITY ignore TYPE NRV2XServicesAuthorized PRESENCE optional }|
+}
+
+```
+
+```
+
+{ ID id-LTEV2XServicesAuthorized CRITICALITY ignore TYPE LTEV2XServicesAuthorized PRESENCE optional }|
+{ ID id-PC5QoSParameters CRITICALITY ignore TYPE PC5QoSParameters PRESENCE optional }|
+{ ID id-UEHistoryInformation CRITICALITY ignore TYPE UEHistoryInformation PRESENCE optional }|
+{ ID id-UEHistoryInformationFromTheUE CRITICALITY ignore TYPE UEHistoryInformationFromTheUE PRESENCE optional }|
+{ ID id-MDTPLMNList CRITICALITY ignore TYPE MDTPLMNList PRESENCE optional }|
+{ ID id-IABNodeIndication CRITICALITY reject TYPE IABNodeIndication PRESENCE optional }|
+{ ID id-UEContextRefAtSN-HORequest CRITICALITY ignore TYPE UEContextRefAtSN-HORequest PRESENCE optional }|
+{ ID id-TimeSynchronizationAssistanceInformation CRITICALITY ignore TYPE TimeSynchronizationAssistanceInformation PRESENCE optional }|
+{ ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional }|
+{ ID id-FiveGProSeAuthorized CRITICALITY ignore TYPE FiveGProSeAuthorized PRESENCE optional }|
+{ ID id-FiveGProSePC5QoSParameters CRITICALITY ignore TYPE FiveGProSePC5QoSParameters PRESENCE optional }|
+{ ID id-AerialUESubscriptionInformation CRITICALITY ignore TYPE AerialUESubscriptionInformation PRESENCE optional }|
+{ ID id-NRA2XServicesAuthorized CRITICALITY ignore TYPE NRA2XServicesAuthorized PRESENCE optional }|
+{ ID id-LTEA2XServicesAuthorized CRITICALITY ignore TYPE LTEA2XServicesAuthorized PRESENCE optional }|
+{ ID id-A2XPC5QoSParameters CRITICALITY ignore TYPE A2XPC5QoSParameters PRESENCE optional }|
+{ ID id-MobileIAB-AuthorizationStatus CRITICALITY ignore TYPE MobileIAB-AuthorizationStatus PRESENCE optional },
+...
+}
+
+```
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- RETRIEVE UE CONTEXT CONFIRM
+
+--
+
+-- \*\*\*\*\*
+
+RetrieveUEContextConfirm ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{RetrieveUEContextConfirm-IEs}},
+
+ ...
+
+}
+
+RetrieveUEContextConfirm-IEs XNAP-PROTOCOL-IES ::= {
+
+ { ID id-oldNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+ { ID id-UEContextKeptIndicator CRITICALITY ignore TYPE UEContextKeptIndicator PRESENCE optional }|
+
+ { ID id-SDT-Termination-Request CRITICALITY ignore TYPE SDT-Termination-Request PRESENCE optional },
+
+ ...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- RETRIEVE UE CONTEXT FAILURE
+
+--
+
+-- \*\*\*\*\*
+
+RetrieveUEContextFailure ::= SEQUENCE {
+
+```
+
+protocolIEs ProtocolIE-Container {{ RetrieveUEContextFailure-IEs}},
+...
+}
+
+```
+
+```
+
+RetrieveUEContextFailure-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-OldtoNewNG-RANnodeResumeContainer CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- XN-U ADDRESS INDICATION
+--
+-- *****
+
+```
+
+```
+
+XnUAddressIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ XnUAddressIndication-IEs}},
+ ...
+}
+
+```
+
+XnUAddressIndication-IEs XNAP-PROTOCOL-IEs ::= {
+
+| | | | |
+|---------------------------------------------|--------------------|------------------------------------------|----------------------|
+| { ID id-newNG-RANnodeUEXnAPID | CRITICALITY ignore | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-oldNG-RANnodeUEXnAPID | CRITICALITY ignore | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-XnUAddressInfoperPDUSession-List | CRITICALITY reject | TYPE XnUAddressInfoperPDUSession-List | PRESENCE mandatory} |
+| { ID id-CHO-MRDC-Indicator | CRITICALITY reject | TYPE CHO-MRDC-Indicator | PRESENCE optional } |
+| { ID id-CHO-MRDC-EarlyDataForwarding | CRITICALITY ignore | TYPE CHO-MRDC-EarlyDataForwarding | PRESENCE optional } |
+| { ID id-CPC-DataForwarding-Indicator | CRITICALITY reject | TYPE CPC-DataForwarding-Indicator | PRESENCE optional } |
+| { ID id-MBS-DataForwarding-Indicator | CRITICALITY ignore | TYPE MBS-DataForwarding-Indicator | PRESENCE optional } |
+| { ID id-MBS-SessionInformationResponse-List | CRITICALITY ignore | TYPE MBS-SessionInformationResponse-List | PRESENCE optional }, |
+| ... | | | |
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- S-NODE ADDITION REQUEST
+
+--
+
+-- \*\*\*\*\*
+
+SNodeAdditionRequest ::= SEQUENCE {
+
+| | | |
+|-------------|----------------------|---------------------------------|
+| protocolIEs | ProtocolIE-Container | {{ SNodeAdditionRequest-IEs }}, |
+| ... | | |
+
+}
+
+```
+
+SNodeAdditionRequest-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-UESecurityCapabilities CRITICALITY reject TYPE UESecurityCapabilities PRESENCE mandatory}|
+ { ID id-s-ng-RANnode-SecurityKey CRITICALITY reject TYPE S-NG-RANnode-SecurityKey PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUE-AMBR CRITICALITY reject TYPE UEAgregateMaximumBitRate PRESENCE mandatory}|
+ { ID id-selectedPLMN CRITICALITY ignore TYPE PLMN-Identity PRESENCE optional }|
+ { ID id-MobilityRestrictionList CRITICALITY ignore TYPE MobilityRestrictionList PRESENCE optional }|
+ { ID id-indexToRatFrequSelectionPriority CRITICALITY reject TYPE RFSP-Index PRESENCE optional }|
+ { ID id-PDUSessionToBeAddedAddReq CRITICALITY reject TYPE PDUSessionToBeAddedAddReq PRESENCE mandatory}|
+ { ID id-MN-to-SN-Container CRITICALITY reject TYPE OCTET STRING PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE optional }|
+ { ID id-ExpectedUEBehaviour CRITICALITY ignore TYPE ExpectedUEBehaviour PRESENCE optional }|
+ { ID id-requestedSplitSRB CRITICALITY reject TYPE SplitSRBsTypes PRESENCE optional }|
+ { ID id-PCellID CRITICALITY reject TYPE GlobalNG-RANCell-ID PRESENCE optional }|
+ { ID id-DesiredActNotificationLevel CRITICALITY ignore TYPE DesiredActNotificationLevel PRESENCE optional }|
+ { ID id-AvailableDRBIDs CRITICALITY reject TYPE DRB-List PRESENCE conditional}
+
+-- The IE shall be present if there is at least one PDUSessionResourceSetupInfo-SNterminated included --|
+ { ID id-S-NG-RANnodeMaxIPDataRate-UL CRITICALITY reject TYPE BitRate PRESENCE optional }|
+ { ID id-S-NG-RANnodeMaxIPDataRate-DL CRITICALITY reject TYPE BitRate PRESENCE optional }|
+ { ID id-LocationInformationSNReporting CRITICALITY ignore TYPE LocationInformationSNReporting PRESENCE optional }|
+ { ID id-MR-DC-ResourceCoordinationInfo CRITICALITY ignore TYPE MR-DC-ResourceCoordinationInfo PRESENCE optional }|
+ { ID id-MaskedIMEISV CRITICALITY ignore TYPE MaskedIMEISV PRESENCE optional }|
+ { ID id-NE-DC-TDM-Pattern CRITICALITY ignore TYPE NE-DC-TDM-Pattern PRESENCE optional }|
+
+```
+
+```
+
+ { ID id-S-NG-RANnode-Addition-Trigger-Ind CRITICALITY reject TYPE S-NG-RANnode-Addition-Trigger-Ind PRESENCE optional }|
+ { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE optional }|
+ { ID id-RequestedFastMCRecoveryViaSRB3 CRITICALITY ignore TYPE RequestedFastMCRecoveryViaSRB3 PRESENCE optional }|
+ { ID id-UERadioCapabilityID CRITICALITY reject TYPE UERadioCapabilityID PRESENCE optional }|
+ { ID id-SourceNG-RAN-node-ID CRITICALITY ignore TYPE GlobalNG-RANNode-ID PRESENCE optional }|
+ { ID id-ManagementBasedMDTPLMNList CRITICALITY ignore TYPE MDTPLMNList PRESENCE optional }|
+ { ID id-UEHistoryInformation CRITICALITY ignore TYPE UEHistoryInformation PRESENCE optional }|
+ { ID id-UEHistoryInformationFromTheUE CRITICALITY ignore TYPE UEHistoryInformationFromTheUE PRESENCE optional }|
+ { ID id-PSCellChangeHistory CRITICALITY ignore TYPE PSCellChangeHistory PRESENCE optional }|
+ { ID id-IABNodeIndication CRITICALITY reject TYPE IABNodeIndication PRESENCE optional }|
+ { ID id-NoPDUSessionIndication CRITICALITY ignore TYPE NoPDUSessionIndication PRESENCE optional }|
+ { ID id-CHOinformation-AddReq CRITICALITY reject TYPE CHOinformation-AddReq PRESENCE optional }|
+ { ID id-SCGActivationRequest CRITICALITY ignore TYPE SCGActivationRequest PRESENCE optional }|
+ { ID id-CPAInformationRequest CRITICALITY reject TYPE CPAInformationRequest PRESENCE optional }|
+ { ID id-S-NG-RANnodeUE-Slice-MBR CRITICALITY reject TYPE UESliceMaximumBitRateList PRESENCE optional }|
+ { ID id-F1-terminatingIAB-donorIndicator CRITICALITY reject TYPE F1-terminatingIAB-donorIndicator PRESENCE optional }|
+ { ID id-SelectedNID CRITICALITY ignore TYPE NID PRESENCE optional }|
+ { ID id-QMCCoordinationRequest CRITICALITY ignore TYPE QMCCoordinationRequest PRESENCE optional }|
+ { ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+PDUSessionToBeAddedAddReq ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionToBeAddedAddReq-Item
+
+```
+
+```
+
+PDUSessionToBeAddedAddReq-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ s-NSSAI S-NSSAI,
+ sN-PDUSessionAMBR PDUSessionAggregateMaximumBitRate OPTIONAL,
+ sn-terminated PDUSessionResourceSetupInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceSetupInfo-MNterminated OPTIONAL,
+ -- NOTE: If neither the PDU Session Resource Setup Info - SN terminated IE
+ -- nor the PDU Session Resource Setup Info - MN terminated IE is present,
+ -- abnormal conditions as specified in clause 8.3.1.4 apply.
+ iE-Extension ProtocolExtensionContainer { {PDUSessionToBeAddedAddReq-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionToBeAddedAddReq-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RequestedFastMCGRecoveryViaSRB3 ::= ENUMERATED {true, ...}
+
+-- *****
+--
+-- S-NODE ADDITION REQUEST ACKNOWLEDGE
+
+```
+
+--
+-- \*\*\*\*\*
+
+SNodeAdditionRequestAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeAdditionRequestAcknowledge-IEs}},
+ ...
+}
+
+SNodeAdditionRequestAcknowledge-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionAdmittedAddedAddReqAck CRITICALITY ignore TYPE PDUSessionAdmittedAddedAddReqAck PRESENCE mandatory}|
+ { ID id-PDUSessionNotAdmittedAddReqAck CRITICALITY ignore TYPE PDUSessionNotAdmittedAddReqAck PRESENCE optional }|
+ { ID id-SN-to-MN-Container CRITICALITY reject TYPE OCTET STRING PRESENCE mandatory}|
+ { ID id-admittedSplitSRB CRITICALITY reject TYPE SplitSRBsTypes PRESENCE optional }|
+ { ID id-RRConfigIndication CRITICALITY reject TYPE RRConfigIndication PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-LocationInformationSN CRITICALITY ignore TYPE Target-CGI PRESENCE optional }|
+ { ID id-MR-DC-ResourceCoordinationInfo CRITICALITY ignore TYPE MR-DC-ResourceCoordinationInfo PRESENCE optional }|
+ { ID id-AvailableFastMCGRecoveryViaSRB3 CRITICALITY ignore TYPE AvailableFastMCGRecoveryViaSRB3 PRESENCE optional }|
+ { ID id-DirectForwardingPathAvailability CRITICALITY ignore TYPE DirectForwardingPathAvailability PRESENCE optional }|
+ { ID id-SCGActivationStatus CRITICALITY ignore TYPE SCGActivationStatus PRESENCE optional }|
+ { ID id-CPAInformationAck CRITICALITY ignore TYPE CPAInformationAck PRESENCE optional }|
+}
+
+```
+{ ID id-SNMobilityInformation CRITICALITY ignore TYPE SNMobilityInformation PRESENCE optional }|
+{ ID id-QMCCoordinationResponse CRITICALITY ignore TYPE QMCCoordinationResponse PRESENCE optional }|
+{ ID id-CHOinformation-AddReqAck CRITICALITY ignore TYPE CHOinformation-AddReqAck PRESENCE optional }|
+{ ID id-DirectForwardingPathAvailabilityWithSourceMN CRITICALITY ignore TYPE DirectForwardingPathAvailabilityWithSourceMN PRESENCE optional },
+...
+}
+```
+
+```
+PDUSessionAdmittedAddedAddReqAck ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionAdmittedAddedAddReqAck-Item
+```
+
+```
+PDUSessionAdmittedAddedAddReqAck-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceSetupResponseInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceSetupResponseInfo-MNterminated OPTIONAL,
+ -- NOTE: If neither the PDU Session Resource Setup Response Info - SN terminated IE
+ -- nor the PDU Session Resource Setup Response Info - MN terminated IE is present,
+ -- abnormal conditions as specified in clause 8.3.1.4 apply.
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmittedAddedAddReqAck-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+PDUSessionAdmittedAddedAddReqAck-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+
+PDUSessionNotAdmittedAddReqAck ::= SEQUENCE {
+ pduSessionResourcesNotAdmitted-SNterminated PDUSessionResourcesNotAdmitted-List OPTIONAL,
+ pduSessionResourcesNotAdmitted-MNterminated PDUSessionResourcesNotAdmitted-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSessionNotAdmittedAddReqAck-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionNotAdmittedAddReqAck-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+AvailableFastMCGRecoveryViaSRB3 ::= ENUMERATED {true, ...}
+
+```
+
+```
+
+-- *****
+--
+-- S-NODE ADDITION REQUEST REJECT
+--
+-- *****
+
+```
+
+```
+
+SNodeAdditionRequestReject ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeAdditionRequestReject-IEs}},
+ ...
+}
+
+```
+
+}
+
+SNodeAdditionRequestReject-IEs XNAP-PROTOCOL-IEs ::= {
+
+| | | | |
+|--------------------------------|--------------------|-----------------------------|----------------------|
+| { ID id-M-NG-RANnodeUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-S-NG-RANnodeUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-Cause | CRITICALITY ignore | TYPE Cause | PRESENCE mandatory} |
+| { ID id-CriticalityDiagnostics | CRITICALITY ignore | TYPE CriticalityDiagnostics | PRESENCE optional } |
+| { ID id-PCellID | CRITICALITY reject | TYPE GlobalNG-RANCell-ID | PRESENCE optional }, |
+
+...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- S-NODE RECONFIGURATION COMPLETE
+
+--
+
+-- \*\*\*\*\*
+
+SNodeReconfigurationComplete ::= SEQUENCE {
+
+protocolIEs ProtocolIE-Container {{ SNodeReconfigurationComplete-IEs}},
+
+...
+
+}
+
+SNodeReconfigurationComplete-IEs XNAP-PROTOCOL-IEs ::= {
+
+```
+
+{ ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+{ ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+{ ID id-ResponseInfo-ReconfCompl CRITICALITY ignore TYPE ResponseInfo-ReconfCompl PRESENCE mandatory},
+...
+}
+
+```
+
+```
+
+ResponseInfo-ReconfCompl ::= SEQUENCE {
+ responseType-ReconfComplete ResponseType-ReconfComplete,
+ iE-Extensions ProtocolExtensionContainer { {ResponseInfo-ReconfCompl-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ResponseInfo-ReconfCompl-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+ResponseType-ReconfComplete ::= CHOICE {
+ configuration-successfully-applied Configuration-successfully-applied,
+ configuration-rejected-by-M-NG-RANNode Configuration-rejected-by-M-NG-RANNode,
+ choice-extension ProtocolIE-Single-Container { {ResponseType-ReconfComplete-ExtIEs} }
+}
+
+```
+
+```
+
+ResponseType-ReconfComplete-ExtIEs XNAP-PROTOCOL-IES ::= {
+
+```
+
+```
+ ...
+}
+
+Configuration-successfully-applied ::= SEQUENCE {
+ m-NG-RANNode-to-S-NG-RANNode-Container OCTET STRING OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {Configuration-successfully-applied-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Configuration-successfully-applied-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Configuration-rejected-by-M-NG-RANNode ::= SEQUENCE {
+ cause Cause,
+ m-NG-RANNode-to-S-NG-RANNode-Container OCTET STRING OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {Configuration-rejected-by-M-NG-RANNode-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Configuration-rejected-by-M-NG-RANNode-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+
+-- *****
+--
+-- S-NODE MODIFICATION REQUEST
+--
+-- *****
+
+```
+
+```
+
+SNodeModificationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeModificationRequest-IEs}},
+ ...
+}
+
+```
+
+```
+
+SNodeModificationRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-PDCPChangeIndication CRITICALITY ignore TYPE PDCPChangeIndication PRESENCE optional }|
+ { ID id-selectedPLMN CRITICALITY ignore TYPE PLMN-Identity PRESENCE optional }|
+ { ID id-MobilityRestrictionList CRITICALITY ignore TYPE MobilityRestrictionList PRESENCE optional }|
+ { ID id-SCGConfigurationQuery CRITICALITY ignore TYPE SCGConfigurationQuery PRESENCE optional }|
+ { ID id-UEContextInfo-SNModRequest CRITICALITY reject TYPE UEContextInfo-SNModRequest PRESENCE optional }|
+ { ID id-MN-to-SN-Container CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+}
+
+```
+
+| | | | |
+|------------------------------------------------|--------------------|---------------------------------------------|---------------------|
+| { ID id-requestedSplitSRB | CRITICALITY ignore | TYPE SplitSRBTypes | PRESENCE optional } |
+| { ID id-requestedSplitSRBrelease | CRITICALITY ignore | TYPE SplitSRBTypes | PRESENCE optional } |
+| { ID id-DesiredActNotificationLevel | CRITICALITY ignore | TYPE DesiredActNotificationLevel | PRESENCE optional } |
+| { ID id-AdditionalDRBIDs | CRITICALITY reject | TYPE DRB-List | PRESENCE optional } |
+| { ID id-S-NG-RANnodeMaxIPDataRate-UL | CRITICALITY reject | TYPE BitRate | PRESENCE optional } |
+| { ID id-S-NG-RANnodeMaxIPDataRate-DL | CRITICALITY reject | TYPE BitRate | PRESENCE optional } |
+| { ID id-LocationInformationSNReporting | CRITICALITY ignore | TYPE LocationInformationSNReporting | PRESENCE optional } |
+| { ID id-MR-DC-ResourceCoordinationInfo | CRITICALITY ignore | TYPE MR-DC-ResourceCoordinationInfo | PRESENCE optional } |
+| { ID id-PCellID | CRITICALITY reject | TYPE GlobalNG-RANCell-ID | PRESENCE optional } |
+| { ID id-NE-DC-TDM-Pattern | CRITICALITY ignore | TYPE NE-DC-TDM-Pattern | PRESENCE optional } |
+| { ID id-RequestedFastMCGRecoveryViaSRB3 | CRITICALITY ignore | TYPE RequestedFastMCGRecoveryViaSRB3 | PRESENCE optional } |
+| { ID id-RequestedFastMCGRecoveryViaSRB3Release | CRITICALITY ignore | TYPE RequestedFastMCGRecoveryViaSRB3Release | PRESENCE optional } |
+| { ID id-SNTriggered | CRITICALITY ignore | TYPE SNTriggered | PRESENCE optional } |
+| { ID id-TargetNodeID | CRITICALITY ignore | TYPE GlobalNG-RANNode-ID | PRESENCE optional } |
+| { ID id-PSCellHistoryInformationRetrieve | CRITICALITY ignore | TYPE PSCellHistoryInformationRetrieve | PRESENCE optional } |
+| { ID id-UEHistoryInformationFromTheUE | CRITICALITY ignore | TYPE UEHistoryInformationFromTheUE | PRESENCE optional } |
+| { ID id-CHOinformation-ModReq | CRITICALITY ignore | TYPE CHOinformation-ModReq | PRESENCE optional } |
+| { ID id-SCGActivationRequest | CRITICALITY ignore | TYPE SCGActivationRequest | PRESENCE optional } |
+| { ID id-CPAInformationModReq | CRITICALITY ignore | TYPE CPAInformationModReq | PRESENCE optional } |
+| { ID id-CPCInformationUpdate | CRITICALITY ignore | TYPE CPCInformationUpdate | PRESENCE optional } |
+| { ID id-S-NG-RANnodeUE-Slice-MBR | CRITICALITY ignore | TYPE UESliceMaximumBitRateList | PRESENCE optional } |
+| { ID id-ManagementBasedMDTPLMNModificationList | CRITICALITY ignore | TYPE MDTPLMNModificationList | PRESENCE optional } |
+| { ID id-SelectedNID | CRITICALITY ignore | TYPE NID | PRESENCE optional } |
+
+```
+
+ { ID id-QMCCoordinationRequest CRITICALITY ignore TYPE QMCCoordinationRequest PRESENCE optional }|
+ { ID id-Src-SN-to-Tgt-SNQMCInfoInquiry CRITICALITY ignore TYPE Src-SN-to-Tgt-SNQMCInfoInquiry PRESENCE optional },
+ ...
+}
+
+```
+
+UEContextInfo-SNModRequest ::= SEQUENCE {
+
+```
+
+ ueSecurityCapabilities UESecurityCapabilities OPTIONAL,
+ s-ng-RANnode-SecurityKey S-NG-RANnode-SecurityKey OPTIONAL,
+ s-ng-RANnodeUE-AMBR UEAggregateMaximumBitRate OPTIONAL,
+ indexToRatFrequencySelectionPriority RFSP-Index OPTIONAL,
+ lowerLayerPresenceStatusChange LowerLayerPresenceStatusChange OPTIONAL,
+ pduSessionResourceToBeAdded PDUSessionsToBeAdded-SNModRequest-List OPTIONAL,
+ pduSessionResourceToBeModified PDUSessionsToBeModified-SNModRequest-List OPTIONAL,
+ pduSessionResourceToBeReleased PDUSessionsToBeReleased-SNModRequest-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {UEContextInfo-SNModRequest-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+UEContextInfo-SNModRequest-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+
+ ...
+}
+
+```
+
+PDUSessionsToBeAdded-SNModRequest-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionsToBeAdded-SNModRequest-Item
+
+```
+
+PDUSessionsToBeAdded-SNModRequest-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ s-NSSAI S-NSSAI,
+ sN-PDUSessionAMBR PDUSessionAggregateMaximumBitRate OPTIONAL,
+ sn-terminated PDUSessionResourceSetupInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceSetupInfo-MNterminated OPTIONAL,
+ -- NOTE: If neither the PDU Session Resource Setup Info - SN terminated IE
+ -- nor the PDU Session Resource Setup Info - MN terminated IE is present,
+ -- abnormal conditions as specified in clause 8.3.3.4 apply.
+ iE-Extension ProtocolExtensionContainer { PDUSessionsToBeAdded-SNModRequest-Item-ExtIEs } OPTIONAL,
+ ...
+}
+
+PDUSessionsToBeAdded-SNModRequest-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-PDUSessionExpectedUEActivityBehaviour CRITICALITY ignore EXTENSION ExpectedUEActivityBehaviour PRESENCE optional},
+ ...
+}
+
+PDUSessionsToBeModified-SNModRequest-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionsToBeModified-SNModRequest-Item
+
+PDUSessionsToBeModified-SNModRequest-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+}
+
+```
+
+```
+
+ sN-PDUSessionAMBR PDUSessionAggregateMaximumBitRate OPTIONAL,
+ sn-terminated PDUSessionResourceModificationInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceModificationInfo-MNterminated OPTIONAL,
+
+-- NOTE: If neither the PDU Session Resource Modification Info - SN terminated IE
+-- nor the PDU Session Resource Modification Info - MN terminated IE is present,
+-- abnormal conditions as specified in clause 8.3.3.4 apply.
+
+ iE-Extension ProtocolExtensionContainer { {PDUSessionsToBeModified-SNModRequest-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionsToBeModified-SNModRequest-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-S-NSSAI CRITICALITY reject EXTENSION S-NSSAI PRESENCE optional}|
+ {ID id-PDUSessionExpectedUEActivityBehaviour CRITICALITY ignore EXTENSION ExpectedUEActivityBehaviour PRESENCE optional},
+ ...
+}
+
+PDUSessionsToBeReleased-SNModRequest-List ::= SEQUENCE {
+ pdu-session-list PDUSession-List-withCause OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSessionsToBeReleased-SNModRequest-List-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionsToBeReleased-SNModRequest-List-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+
+```
+
+ ...
+ }
+
+ RequestedFastMCGRecoveryViaSRB3Release ::= ENUMERATED {true, ...}
+
+ Src-SN-to-Tgt-SNQMCInfoInquiry ::= ENUMERATED {true, ...}
+
+```
+
+```
+
+-- *****
+--
+-- S-NODE MODIFICATION REQUEST ACKNOWLEDGE
+--
+-- *****
+
+```
+
+```
+
+SNodeModificationRequestAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeModificationRequestAcknowledge-IEs}},
+ ...
+}
+
+```
+
+```
+
+SNodeModificationRequestAcknowledge-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionAdmitted-SNModResponse CRITICALITY ignore TYPE PDUSessionAdmitted-SNModResponse PRESENCE optional }|
+ { ID id-PDUSessionNotAdmitted-SNModResponse CRITICALITY ignore TYPE PDUSessionNotAdmitted-SNModResponse PRESENCE optional }|
+
+```
+
+```
+
+ { ID id-SN-to-MN-Container CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+ { ID id-admittedSplitSRB CRITICALITY ignore TYPE SplitSRBTypes PRESENCE optional }|
+ { ID id-admittedSplitSRBrelease CRITICALITY ignore TYPE SplitSRBTypes PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-LocationInformationSN CRITICALITY ignore TYPE Target-CGI PRESENCE optional }|
+ { ID id-MR-DC-ResourceCoordinationInfo CRITICALITY ignore TYPE MR-DC-ResourceCoordinationInfo PRESENCE optional }|
+ { ID id-PDUSessionDataForwarding-SNModResponse CRITICALITY ignore TYPE PDUSessionDataForwarding-SNModResponse PRESENCE optional }|
+ { ID id-RRCConfigIndication CRITICALITY reject TYPE RRCConfigIndication PRESENCE optional }|
+ { ID id-AvailableFastMCGRecoveryViaSRB3 CRITICALITY ignore TYPE AvailableFastMCGRecoveryViaSRB3 PRESENCE optional }|
+ { ID id-ReleaseFastMCGRecoveryViaSRB3 CRITICALITY ignore TYPE ReleaseFastMCGRecoveryViaSRB3 PRESENCE optional }|
+ { ID id-DirectForwardingPathAvailability CRITICALITY ignore TYPE DirectForwardingPathAvailability PRESENCE optional }|
+ { ID id-SCGUEHistoryInformation CRITICALITY ignore TYPE SCGUEHistoryInformation PRESENCE optional }|
+ { ID id-SCGActivationStatus CRITICALITY ignore TYPE SCGActivationStatus PRESENCE optional }|
+ { ID id-CPAInformationModReqAck CRITICALITY ignore TYPE CPAInformationModReqAck PRESENCE optional }|
+ { ID id-QMCoordinationResponse CRITICALITY ignore TYPE QMCoordinationResponse PRESENCE optional }|
+ { ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional },
+ ...
+}
+
+```
+
+```
+PDUSessionAdmitted-SNModResponse ::= SEQUENCE {
+```
+
+```
+
+ pduSessionResourcesAdmittedToBeAdded PDUSessionAdmittedToBeAddedSNModResponse OPTIONAL,
+ pduSessionResourcesAdmittedToBeModified PDUSessionAdmittedToBeModifiedSNModResponse OPTIONAL,
+ pduSessionResourcesAdmittedToBeReleased PDUSessionAdmittedToBeReleasedSNModResponse OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmitted-SNModResponse-ExtIEs} } OPTIONAL,
+
+```
+
+```
+...
+}
+
+PDUSessionAdmitted-SNModResponse-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PDUSessionAdmittedToBeAddedSNModResponse ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionAdmittedToBeAddedSNModResponse-Item
+PDUSessionAdmittedToBeAddedSNModResponse-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceSetupResponseInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceSetupResponseInfo-MNterminated OPTIONAL,
+ -- NOTE: If neither the PDU Session Resource Setup Response Info - SN terminated IE
+ -- nor the PDU Session Resource Setup Response Info - MN terminated IE is present,
+ -- abnormal conditions as specified in clause 8.3.3.4 apply.
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmittedToBeAddedSNModResponse-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionAdmittedToBeAddedSNModResponse-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+PDUSessionAdmittedToBeModifiedSNModResponse ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionAdmittedToBeModifiedSNModResponse-Item
+
+PDUSessionAdmittedToBeModifiedSNModResponse-Item ::= SEQUENCE {
+
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceModificationResponseInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceModificationResponseInfo-MNterminated OPTIONAL,
+
+-- NOTE: If neither the *PDU Session Resource Modification Response Info - SN terminated* IE
+
+-- nor the *PDU Session Resource Modification Response Info - MN terminated* IE is present,
+
+-- abnormal conditions as specified in clause 8.3.3.4 apply.
+
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmittedToBeModifiedSNModResponse-Item-ExtIEs} } OPTIONAL,
+ ...
+
+}
+
+PDUSessionAdmittedToBeModifiedSNModResponse-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+
+}
+
+PDUSessionAdmittedToBeReleasedSNModResponse ::= SEQUENCE {
+
+ sn-terminated PDUSession-List-withDataForwardingRequest OPTIONAL,
+
+ mn-terminated PDUSession-List-withCause OPTIONAL,
+
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmittedToBeReleasedSNModResponse-ExtIEs} } OPTIONAL,
+
+ ...
+
+}
+
+```
+PDUSessionAdmittedToBeReleasedSNModResponse-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PDUSessionNotAdmitted-SNModResponse ::= SEQUENCE {
+ pdu-Session-List PDUSession-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSessionNotAdmitted-SNModResponse-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionNotAdmitted-SNModResponse-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PDUSessionDataForwarding-SNModResponse ::= SEQUENCE {
+ sn-terminated PDUSession-List-withDataForwardingRequest,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionDataForwarding-SNModResponse-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionDataForwarding-SNModResponse-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+}
+
+ReleaseFastMCGRecoveryViaSRB3 ::= ENUMERATED {true, ...}
+
+-- \*\*\*\*\*
+
+--
+
+-- S-NODE MODIFICATION REQUEST REJECT
+
+--
+
+-- \*\*\*\*\*
+
+SNodeModificationRequestReject ::= SEQUENCE {
+
+protocolIEs ProtocolIE-Container {{ SNodeModificationRequestReject-IEs }},
+
+...
+}
+
+SNodeModificationRequestReject-IEs XNAP-PROTOCOL-IES ::= {
+
+{ ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory} |
+
+{ ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory} |
+
+{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory} |
+
+{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+
+...
+}
+
+```
+
+}
+
+-- *****
+--
+-- S-NODE MODIFICATION REQUIRED
+--
+-- *****
+
+```
+
+```
+
+SNodeModificationRequired ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeModificationRequired-IEs}},
+ ...
+}
+
+```
+
+```
+
+SNodeModificationRequired-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-PDCPChangeIndication CRITICALITY ignore TYPE PDCPChangeIndication PRESENCE optional }|
+ { ID id-PDUSessionToBeModifiedSNModRequired CRITICALITY ignore TYPE PDUSessionToBeModifiedSNModRequired PRESENCE optional }|
+ { ID id-PDUSessionToBeReleasedSNModRequired CRITICALITY ignore TYPE PDUSessionToBeReleasedSNModRequired PRESENCE optional }|
+ { ID id-SN-to-MN-Container CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+ { ID id-SpareDRBIDs CRITICALITY ignore TYPE DRB-List PRESENCE optional }|
+ { ID id-RequiredNumberOfDRBIDs CRITICALITY ignore TYPE DRB-Number PRESENCE optional }|
+}
+
+```
+
+```
+
+ { ID id-LocationInformationSN CRITICALITY ignore TYPE Target-CGI PRESENCE optional }|
+ { ID id-MR-DC-ResourceCoordinationInfo CRITICALITY ignore TYPE MR-DC-ResourceCoordinationInfo PRESENCE optional }|
+ { ID id-RRCConfigIndication CRITICALITY reject TYPE RRCConfigIndication PRESENCE optional }|
+ { ID id-AvailableFastMCGRecoveryViaSRB3 CRITICALITY ignore TYPE AvailableFastMCGRecoveryViaSRB3 PRESENCE optional }|
+ { ID id-ReleaseFastMCGRecoveryViaSRB3 CRITICALITY ignore TYPE ReleaseFastMCGRecoveryViaSRB3 PRESENCE optional }|
+ { ID id-SCGIndicator CRITICALITY ignore TYPE SCGIndicator PRESENCE optional }|
+ { ID id-SCGUEHistoryInformation CRITICALITY ignore TYPE SCGUEHistoryInformation PRESENCE optional }|
+ { ID id-SCGActivationRequest CRITICALITY ignore TYPE SCGActivationRequest PRESENCE optional }|
+ { ID id-CPACInformationModRequired CRITICALITY ignore TYPE CPACInformationModRequired PRESENCE optional }|
+ { ID id-SCGreconfigNotification CRITICALITY ignore TYPE SCGreconfigNotification PRESENCE optional }|
+ { ID id-SPRAvailability CRITICALITY ignore TYPE SPRAvailability PRESENCE optional }|
+ { ID id-QMCCoordinationRequest CRITICALITY ignore TYPE QMCCoordinationRequest PRESENCE optional }|
+ { ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional },
+ ...
+}
+
+```
+
+```
+PDUSessionToBeModifiedSNModRequired::= SEQUENCE (SIZE (1.. maxnoofPDUSessions)) OF PDUSessionToBeModifiedSNModRequired-Item
+```
+
+```
+
+PDUSessionToBeModifiedSNModRequired-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceModRqdInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceModRqdInfo-MNterminated OPTIONAL,
+}
+
+-- NOTE: If neither the PDU Session Resource Modification Required Info - SN terminated IE
+-- nor the PDU Session Resource Modification Required Info - MN terminated IE is present,
+
+```
+
+-- abnormal conditions as specified in clause 8.3.4.4 apply.
+
+```
+
+ iE-Extension ProtocolExtensionContainer { {PDUSessionToBeModifiedSNModRequired-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionToBeModifiedSNModRequired-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+PDUSessionToBeReleasedSNModRequired ::= SEQUENCE {
+ sn-terminated PDUSession-List-withDataForwardingRequest OPTIONAL,
+ mn-terminated PDUSession-List-withCause OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSessionToBeReleasedSNModRequired-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionToBeReleasedSNModRequired-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+-- \*\*\*\*\*
+
+--
+
+-- S-NODE MODIFICATION CONFIRM
+
+--
+-- \*\*\*\*\*
+
+SNodeModificationConfirm ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeModificationConfirm-IEs}},
+ ...
+}
+
+SNodeModificationConfirm-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionAdmittedModSNModConfirm CRITICALITY ignore TYPE PDUSessionAdmittedModSNModConfirm PRESENCE optional }|
+ { ID id-PDUSessionReleasedSNModConfirm CRITICALITY ignore TYPE PDUSessionReleasedSNModConfirm PRESENCE optional }|
+ { ID id-MN-to-SN-Container CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+ { ID id-AdditionalDRBIDs CRITICALITY reject TYPE DRB-List PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-MR-DC-ResourceCoordinationInfo CRITICALITY ignore TYPE MR-DC-ResourceCoordinationInfo PRESENCE optional }|
+ { ID id-QMCCoordinationResponse CRITICALITY ignore TYPE QMCCoordinationResponse PRESENCE optional },
+ ...
+}
+
+PDUSessionAdmittedModSNModConfirm ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionAdmittedModSNModConfirm-Item
+
+```
+PDUSessionAdmittedModSNModConfirm-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceModConfirmInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceModConfirmInfo-MNterminated OPTIONAL,
+ -- NOTE: If neither the PDU Session Resource Modification Confirm Info - SN terminated IE
+ -- nor the PDU Session Resource Modification Confirm Info - MN terminated IE is present,
+ -- abnormal conditions as specified in clause 8.3.4.4 apply.
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmittedModSNModConfirm-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionAdmittedModSNModConfirm-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PDUSessionReleasedSNModConfirm ::= SEQUENCE {
+ sn-terminated PDUSession-List-withDataForwardingFromTarget OPTIONAL,
+ mn-terminated PDUSession-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSessionAdmittedToBeReleasedSNModConfirm-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+PDUSessionAdmittedToBeReleasedSNModConfirm-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+-- *****
+```
+
+```
+--
+```
+
+```
+-- S-NODE MODIFICATION REFUSE
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+SNodeModificationRefuse ::= SEQUENCE {
+```
+
+```
+ protocolIEs ProtocolIE-Container {{ SNodeModificationRefuse-IEs}},
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+SNodeModificationRefuse-IEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+```
+
+```
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+```
+
+```
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+```
+
+```
+ { ID id-MN-to-SN-Container CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+```
+
+```
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+```
+
+```
+ ...
+```
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- S-NODE RELEASE REQUEST
+
+--
+
+-- \*\*\*\*\*
+
+SNodeReleaseRequest ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ SNodeReleaseRequest-IEs}},
+
+ ...
+}
+
+SNodeReleaseRequest-IEs XNAP-PROTOCOL-IES ::= {
+
+| | | | |
+|---------------------------------------|--------------------|--------------------------------|----------------------|
+| { ID id-M-NG-RANnodeUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-S-NG-RANnodeUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE optional } |
+| { ID id-Cause | CRITICALITY ignore | TYPE Cause | PRESENCE mandatory} |
+| { ID id-PDUSessionToBeReleased-RelReq | CRITICALITY ignore | TYPE PDUSession-List-withCause | PRESENCE optional } |
+| { ID id-UEContextKeptIndicator | CRITICALITY ignore | TYPE UEContextKeptIndicator | PRESENCE optional } |
+| { ID id-MN-to-SN-Container | CRITICALITY ignore | TYPE OCTET STRING | PRESENCE optional } |
+| { ID id-DRBs-transferred-to-MN | CRITICALITY ignore | TYPE DRB-List | PRESENCE optional }, |
+| ... | | | |
+
+}
+
+```
+-- *****
+--
+-- S-NODE RELEASE REQUEST ACKNOWLEDGE
+--
+-- *****
+```
+
+```
+SNodeReleaseRequestAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeReleaseRequestAcknowledge-IEs}},
+ ...
+}
+```
+
+```
+SNodeReleaseRequestAcknowledge-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE optional }|
+ { ID id-PDUSessionToBeReleased-RelReqAck CRITICALITY ignore TYPE PDUSessionToBeReleasedList-RelReqAck PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-SCGUEHistoryInformation CRITICALITY ignore TYPE SCGUEHistoryInformation PRESENCE optional }|
+ { ID id-SNMobilityInformation CRITICALITY ignore TYPE SNMobilityInformation PRESENCE optional },
+ ...
+}
+```
+
+```
+PDUSessionToBeReleasedList-RelReqAck ::= SEQUENCE {
+```
+
+```
+
+ pduSessionsToBeReleasedList-SNTerminated PDUSession-List-withDataForwardingRequest OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionToBeReleasedList-RelReqAck-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionToBeReleasedList-RelReqAck-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- S-NODE RELEASE REJECT
+--
+-- *****
+
+```
+
+```
+
+SNodeReleaseReject ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeReleaseReject-IEs}},
+ ...
+}
+
+```
+
+```
+
+SNodeReleaseReject-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE optional }|
+}
+
+```
+
+```
+
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+```
+
+-- \*\*\*\*\*
+
+--
+
+-- S-NODE RELEASE REQUIRED
+
+--
+
+-- \*\*\*\*\*
+
+```
+
+SNodeReleaseRequired ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeReleaseRequired-IEs}},
+ ...
+}
+
+```
+
+```
+
+SNodeReleaseRequired-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionToBeReleasedList-RelRqd CRITICALITY ignore TYPE PDUSessionToBeReleasedList-RelRqd PRESENCE optional }|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-SN-to-MN-Container CRITICALITY ignore TYPE OCTET STRING PRESENCE optional }|
+ { ID id-SCGUEHistoryInformation CRITICALITY ignore TYPE SCGUEHistoryInformation PRESENCE optional },
+
+```
+
+```
+
+ ...
+ }
+
+ PDUSessionToBeReleasedList-RelRqd ::= SEQUENCE {
+ pduSessionsToBeReleasedList-SNterminated PDUSession-List-withDataForwardingRequest OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionToBeReleasedList-RelRqd-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ PDUSessionToBeReleasedList-RelRqd-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ -- *****
+ --
+ -- S-NODE RELEASE CONFIRM
+ --
+ -- *****
+
+ SNodeReleaseConfirm ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { SNodeReleaseConfirm-IEs} },
+ ...
+ }
+
+```
+
+```
+
+}
+
+SNodeReleaseConfirm-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionReleasedList-RelConf CRITICALITY ignore TYPE PDUSessionReleasedList-RelConf PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+PDUSessionReleasedList-RelConf ::= SEQUENCE {
+ pduSessionsReleasedList-SNterminated PDUSession-List-withDataForwardingFromTarget OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionReleasedList-RelConf-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionReleasedList-RelConf-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- *****
+--
+
+```
+
+```
+-- S-NODE COUNTER CHECK REQUEST
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+SNodeCounterCheckRequest ::= SEQUENCE {
+```
+
+```
+ protocolIEs ProtocolIE-Container {{ SNodeCounterCheckRequest-IEs }},
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+SNodeCounterCheckRequest-IEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory} |
+```
+
+```
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory} |
+```
+
+```
+ { ID id-BearersSubjectToCounterCheck CRITICALITY ignore TYPE BearersSubjectToCounterCheck-List PRESENCE mandatory},
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+BearersSubjectToCounterCheck-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF BearersSubjectToCounterCheck-Item
+```
+
+```
+BearersSubjectToCounterCheck-Item ::= SEQUENCE {
+```
+
+```
+ drb-ID DRB-ID,
+```
+
+```
+ ul-count INTEGER (0.. 4294967295),
+```
+
+```
+ dl-count INTEGER (0.. 4294967295),
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {BearersSubjectToCounterCheck-Item-ExtIEs} } OPTIONAL,
+```
+
+...
+}
+
+BearersSubjectToCounterCheck-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+-- \*\*\*\*\*
+--
+-- S-NODE CHANGE REQUIRED
+--
+-- \*\*\*\*\*
+
+SNodeChangeRequired ::= SEQUENCE {
+protocolIEs ProtocolIE-Container {{ SNodeChangeRequired-IEs }},
+...
+}
+
+SNodeChangeRequired-IEs XNAP-PROTOCOL-IES ::= {
+{ ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory } |
+{ ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory } |
+{ ID id-target-S-NG-RANnodeID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE mandatory } |
+}
+
+```
+
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-PDUSession-SNChangeRequired-List CRITICALITY ignore TYPE PDUSession-SNChangeRequired-List PRESENCE optional }|
+ { ID id-SN-to-MN-Container CRITICALITY reject TYPE OCTET STRING PRESENCE mandatory}|
+ { ID id-SCGUEHistoryInformation CRITICALITY ignore TYPE SCGUEHistoryInformation PRESENCE optional }|
+ { ID id-SNMobilityInformation CRITICALITY ignore TYPE SNMobilityInformation PRESENCE optional }|
+ { ID id-SourcePSCellID CRITICALITY ignore TYPE GlobalNG-RANCell-ID PRESENCE optional }|
+ { ID id-CPCInformationRequired CRITICALITY ignore TYPE CPCInformationRequired PRESENCE optional }|
+ { ID id-QMCConfigInfo CRITICALITY ignore TYPE QMCConfigInfo PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+PDUSession-SNChangeRequired-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSession-SNChangeRequired-Item
+
+```
+
+```
+
+PDUSession-SNChangeRequired-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceChangeRequiredInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceChangeRequiredInfo-MNterminated OPTIONAL,
+ -- NOTE: If the PDU Session Resource Change Required Info - SN terminated IE is not present,
+ -- abnormal conditions as specified in clause 8.3.5.4 apply.
+ iE-Extension ProtocolExtensionContainer { {PDUSession-SNChangeRequired-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+PDUSession-SNChangeRequired-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+-- *****
+```
+
+```
+--
+```
+
+```
+-- S-NODE CHANGE CONFIRM
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+SNodeChangeConfirm ::= SEQUENCE {
+```
+
+```
+ protocolIEs ProtocolIE-Container {{ SNodeChangeConfirm-IEs}},
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+SNodeChangeConfirm-IEs XNAP-PROTOCOL-IES ::= {
+```
+
+| | | | |
+|-----------------------------------------|--------------------|--------------------------------------|----------------------|
+| { ID id-M-NG-RANnodeUEXnAPID | CRITICALITY ignore | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-S-NG-RANnodeUEXnAPID | CRITICALITY ignore | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-PDUSession-SNChangeConfirm-List | CRITICALITY ignore | TYPE PDUSession-SNChangeConfirm-List | PRESENCE optional } |
+| { ID id-CriticalityDiagnostics | CRITICALITY ignore | TYPE CriticalityDiagnostics | PRESENCE optional } |
+| { ID id-CPCInformationConfirm | CRITICALITY ignore | TYPE CPCInformationConfirm | PRESENCE optional } |
+| { ID id-MN-to-SN-Container | CRITICALITY ignore | TYPE OCTET STRING | PRESENCE optional }, |
+
+```
+
+ ...
+ }
+
+ PDUSession-SNChangeConfirm-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSession-SNChangeConfirm-Item
+
+ PDUSession-SNChangeConfirm-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ sn-terminated PDUSessionResourceChangeConfirmInfo-SNterminated OPTIONAL,
+ mn-terminated PDUSessionResourceChangeConfirmInfo-MNterminated OPTIONAL,
+ -- NOTE: If the PDUSessionResourceChangeConfirmInfo - SN terminated IE is not present,
+ -- abnormal conditions as specified in clause 8.3.5.4 apply.
+ iE-Extension ProtocolExtensionContainer { {PDUSession-SNChangeConfirm-Item-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ PDUSession-SNChangeConfirm-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated CRITICALITY ignore EXTENSION
+ AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated PRESENCE optional},
+ ...
+ }
+
+ -- *****
+ --
+ -- S-NODE CHANGE REFUSE
+
+```
+
+--
+-- \*\*\*\*\*
+
+```
+SNodeChangeRefuse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ SNodeChangeRefuse-IEs}},
+ ...
+}
+```
+
+```
+SNodeChangeRefuse-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+```
+
+-- \*\*\*\*\*
+--
+
+-- RRC TRANSFER
+
+--
+-- \*\*\*\*\*
+
+```
+RRCTransfer ::= SEQUENCE {
+```
+
+```
+
+protocolIEs ProtocolIE-Container {{ RRCTransfer-IEs}},
+...
+}
+
+RRCTransfer-IEs XNAP-PROTOCOL-IEs ::= {
+
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-SplitSRB-RRCTransfer CRITICALITY reject TYPE SplitSRB-RRCTransfer PRESENCE optional }|
+ { ID id-UEReportRRCTransfer CRITICALITY reject TYPE UEReportRRCTransfer PRESENCE optional }|
+ { ID id-FastMCGRecoveryRRCTransfer-SN-to-MN CRITICALITY ignore TYPE FastMCGRecoveryRRCTransfer PRESENCE optional }|
+ { ID id-FastMCGRecoveryRRCTransfer-MN-to-SN CRITICALITY ignore TYPE FastMCGRecoveryRRCTransfer PRESENCE optional }|
+ { ID id-SDT-SRB-between-NewNode-OldNode CRITICALITY ignore TYPE SDT-SRB-between-NewNode-OldNode PRESENCE optional }|
+ { ID id-QoE-Measurement-Results CRITICALITY ignore TYPE QoE-Measurement-Results PRESENCE optional },
+ ...
+}
+
+SplitSRB-RRCTransfer ::= SEQUENCE {
+
+ rrcContainer OCTET STRING OPTIONAL,
+ srbType ENUMERATED {srb1, srb2, ...},
+ deliveryStatus DeliveryStatus OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {SplitSRB-RRCTransfer-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+SplitSRB-RRCTransfer-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UEReportRRCTransfer ::= SEQUENCE {
+ rrcContainer OCTET STRING,
+ iE-Extensions ProtocolExtensionContainer { {UEReportRRCTransfer-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UEReportRRCTransfer-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+FastMCGRecoveryRRCTransfer ::= SEQUENCE {
+ rrcContainer OCTET STRING,
+ iE-Extensions ProtocolExtensionContainer { { FastMCGRecoveryRRCTransfer-ExtIEs} } OPTIONAL,
+ ...
+}
+
+FastMCGRecoveryRRCTransfer-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+
+SDT-SRB-between-NewNode-OldNode ::= SEQUENCE {
+ rrcContainer OCTET STRING,
+ srb-ID SRB-ID,
+ iE-Extensions ProtocolExtensionContainer { { SDT-SRB-between-NewNode-OldNode-ExtIEs } } OPTIONAL,
+ ...
+}
+
+SDT-SRB-between-NewNode-OldNode-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+QoE-Measurement-Results ::= SEQUENCE {
+ qOEReference OCTET STRING (SIZE(6)),
+ rrcContainerForRVQoEReport OCTET STRING OPTIONAL,
+ rrcContainerForQoEReport OCTET STRING OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { QoE-Measurement-Results-ExtIEs } } OPTIONAL,
+ ...
+}
+
+QoE-Measurement-Results-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+
+}
+
+-- *****
+--
+-- NOTIFICATION CONTROL INDICATION
+--
+-- *****
+
+NotificationControlIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{NotificationControlIndication-IEs}},
+ ...
+}
+
+NotificationControlIndication-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-PDUSessionResourcesNotifyList CRITICALITY reject TYPE PDUSessionResourcesNotifyList PRESENCE optional },
+ ...
+}
+
+PDUSessionResourcesNotifyList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourcesNotify-Item
+
+```
+
+```
+
+PDUSessionResourcesNotify-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ qosFlowsNotificationContrIndInfo QoSFlowNotificationControlIndicationInfo,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourcesNotify-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourcesNotify-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- ACTIVITY NOTIFICATION
+--
+-- *****
+
+```
+
+```
+
+ActivityNotification ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {ActivityNotification-IEs} },
+ ...
+}
+
+```
+
+```
+
+ActivityNotification-IEs XNAP-PROTOCOL-IEs ::= {
+
+```
+
+```
+
+{ ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+{ ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+{ ID id-UserPlaneTrafficActivityReport CRITICALITY ignore TYPE UserPlaneTrafficActivityReport PRESENCE optional }|
+{ ID id-PDUSessionResourcesActivityNotifyList CRITICALITY ignore TYPE PDUSessionResourcesActivityNotifyList PRESENCE optional }|
+{ ID id-RANPagingFailure CRITICALITY ignore TYPE RANPagingFailure PRESENCE optional },
+...
+}
+
+```
+
+```
+PDUSessionResourcesActivityNotifyList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourcesActivityNotify-Item
+```
+
+```
+
+PDUSessionResourcesActivityNotify-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ pduSessionLevelUPactivityreport UserPlaneTrafficActivityReport OPTIONAL,
+ qosFlowsActivityNotifyList QoSFlowsActivityNotifyList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourcesActivityNotify-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourcesActivityNotify-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+QoSFlowsActivityNotifyList ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsActivityNotifyItem
+```
+
+```
+
+QoSFlowsActivityNotifyItem ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ pduSessionLevelUPactivityreport UserPlaneTrafficActivityReport,
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowsActivityNotifyItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+QoSFlowsActivityNotifyItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- XN SETUP REQUEST
+--
+-- *****
+
+```
+
+```
+
+XnSetupRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { XnSetupRequest-IEs} },
+ ...
+}
+
+```
+
+```
+
+XnSetupRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-GlobalNG-RAN-node-ID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE mandatory}|
+ { ID id-TAISupport-list CRITICALITY reject TYPE TAISupport-List PRESENCE mandatory}|
+ { ID id-AMF-Region-Information CRITICALITY reject TYPE AMF-Region-Information PRESENCE mandatory}|
+ { ID id-List-of-served-cells-NR CRITICALITY reject TYPE ServedCells-NR PRESENCE optional }|
+ { ID id-List-of-served-cells-E-UTRA CRITICALITY reject TYPE ServedCells-E-UTRA PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional }|
+ { ID id-TNLConfigurationInfo CRITICALITY ignore TYPE TNLConfigurationInfo PRESENCE optional }|
+ { ID id-PartialListIndicator-NR CRITICALITY ignore TYPE PartialListIndicator PRESENCE optional }|
+ { ID id-CellAndCapacityAssistanceInfo-NR CRITICALITY ignore TYPE CellAndCapacityAssistanceInfo-NR PRESENCE optional }|
+ { ID id-PartialListIndicator-EUTRA CRITICALITY ignore TYPE PartialListIndicator PRESENCE optional }|
+ { ID id-CellAndCapacityAssistanceInfo-EUTRA CRITICALITY ignore TYPE CellAndCapacityAssistanceInfo-EUTRA PRESENCE optional }|
+ { ID id-Local-NG-RAN-Node-Identifier CRITICALITY ignore TYPE Local-NG-RAN-Node-Identifier PRESENCE optional }|
+ { ID id-Neighbour-NG-RAN-Node-List CRITICALITY ignore TYPE Neighbour-NG-RAN-Node-List PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- XN SETUP RESPONSE
+--
+-- *****
+
+```
+
+```
+
+XnSetupResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ XnSetupResponse-IEs}},
+ ...
+}
+
+XnSetupResponse-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-GlobalNG-RAN-node-ID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE mandatory}|
+ { ID id-TAISupport-list CRITICALITY reject TYPE TAISupport-List PRESENCE mandatory}|
+ { ID id-List-of-served-cells-NR CRITICALITY reject TYPE ServedCells-NR PRESENCE optional }|
+ { ID id-List-of-served-cells-E-UTRA CRITICALITY reject TYPE ServedCells-E-UTRA PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-AMF-Region-Information CRITICALITY reject TYPE AMF-Region-Information PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional }|
+ { ID id-TNLConfigurationInfo CRITICALITY ignore TYPE TNLConfigurationInfo PRESENCE optional }|
+ { ID id-PartialListIndicator-NR CRITICALITY ignore TYPE PartialListIndicator PRESENCE optional }|
+ { ID id-CellAndCapacityAssistanceInfo-NR CRITICALITY ignore TYPE CellAndCapacityAssistanceInfo-NR PRESENCE optional }|
+ { ID id-PartialListIndicator-EUTRA CRITICALITY ignore TYPE PartialListIndicator PRESENCE optional }|
+ { ID id-CellAndCapacityAssistanceInfo-EUTRA CRITICALITY ignore TYPE CellAndCapacityAssistanceInfo-EUTRA PRESENCE optional }|
+ { ID id-Local-NG-RAN-Node-Identifier CRITICALITY ignore TYPE Local-NG-RAN-Node-Identifier PRESENCE optional }|
+ { ID id-Neighbour-NG-RAN-Node-List CRITICALITY ignore TYPE Neighbour-NG-RAN-Node-List PRESENCE optional },
+ ...
+}
+
+```
+
+```
+-- *****
+--
+-- XN SETUP FAILURE
+--
+-- *****
+```
+
+```
+XnSetupFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ XnSetupFailure-IEs}},
+ ...
+}
+```
+
+```
+XnSetupFailure-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional }|
+ { ID id-MessageOversizeNotification CRITICALITY ignore TYPE MessageOversizeNotification PRESENCE optional },
+ ...
+}
+```
+
+```
+-- *****
+--
+-- NG-RAN NODE CONFIGURATION UPDATE
+```
+
+--
+-- \*\*\*\*\*
+
+NGRANNodeConfigurationUpdate ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ NGRANNodeConfigurationUpdate-IEs}},
+ ...
+}
+
+NGRANNodeConfigurationUpdate-IEs XNAP-PROTOCOL-IES ::= {
+
+ { ID id-TAISupport-list CRITICALITY reject TYPE TAISupport-List PRESENCE optional }|
+ { ID id-ConfigurationUpdateInitiatingNodeChoice CRITICALITY ignore TYPE ConfigurationUpdateInitiatingNodeChoice PRESENCE mandatory}|
+ { ID id-TNLA-To-Add-List CRITICALITY ignore TYPE TNLA-To-Add-List PRESENCE optional }|
+ { ID id-TNLA-To-Remove-List CRITICALITY ignore TYPE TNLA-To-Remove-List PRESENCE optional }|
+ { ID id-TNLA-To-Update-List CRITICALITY ignore TYPE TNLA-To-Update-List PRESENCE optional }|
+ { ID id-GlobalNG-RAN-node-ID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE optional }|
+ { ID id-AMF-Region-Information-To-Add CRITICALITY reject TYPE AMF-Region-Information PRESENCE optional }|
+ { ID id-AMF-Region-Information-To-Delete CRITICALITY reject TYPE AMF-Region-Information PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional }|
+ { ID id-TNLConfigurationInfo CRITICALITY ignore TYPE TNLConfigurationInfo PRESENCE optional }|
+ { ID id-Coverage-Modification-List CRITICALITY reject TYPE Coverage-Modification-List PRESENCE optional }|
+ { ID id-Local-NG-RAN-Node-Identifier CRITICALITY ignore TYPE Local-NG-RAN-Node-Identifier PRESENCE optional }|
+ { ID id-Neighbour-NG-RAN-Node-List CRITICALITY ignore TYPE Neighbour-NG-RAN-Node-List PRESENCE optional }|
+ { ID id-Local-NG-RAN-Node-Identifier-Removal CRITICALITY ignore TYPE Local-NG-RAN-Node-Identifier PRESENCE optional },
+
+```
+ ...
+}
+
+ConfigurationUpdateInitiatingNodeChoice ::= CHOICE {
+ gNB ProtocolIE-Container { {ConfigurationUpdate-gNB} },
+ ng-eNB ProtocolIE-Container { {ConfigurationUpdate-ng-eNB} },
+ choice-extension ProtocolIE-Single-Container { {ServedCellsToUpdateInitiatingNodeChoice-ExtIEs} }
+}
+
+ServedCellsToUpdateInitiatingNodeChoice-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+ConfigurationUpdate-gNB XNAP-PROTOCOL-IES ::= {
+ { ID id-servedCellsToUpdate-NR CRITICALITY ignore TYPE ServedCellsToUpdate-NR PRESENCE optional }|
+ { ID id-cellAssistanceInfo-NR CRITICALITY ignore TYPE CellAssistanceInfo-NR PRESENCE optional }|
+ { ID id-cellAssistanceInfo-EUTRA CRITICALITY ignore TYPE CellAssistanceInfo-EUTRA PRESENCE optional }|
+ { ID id-ServedCellSpecificInfoReq-NR CRITICALITY ignore TYPE ServedCellSpecificInfoReq-NR PRESENCE optional},
+ ...
+}
+
+ConfigurationUpdate-ng-eNB XNAP-PROTOCOL-IES ::= {
+```
+
+```
+
+ { ID id-servedCellsToUpdate-E-UTRA CRITICALITY ignore TYPE ServedCellsToUpdate-E-UTRA PRESENCE optional }|
+ { ID id-cellAssistanceInfo-NR CRITICALITY ignore TYPE CellAssistanceInfo-NR PRESENCE optional }|
+ { ID id-cellAssistanceInfo-EUTRA CRITICALITY ignore TYPE CellAssistanceInfo-EUTRA PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE
+--
+-- *****
+
+```
+
+```
+
+NGRANNodeConfigurationUpdateAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ NGRANNodeConfigurationUpdateAcknowledge-IEs }},
+ ...
+}
+
+```
+
+```
+
+NGRANNodeConfigurationUpdateAcknowledge-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-RespondingNodeTypeConfigUpdateAck CRITICALITY ignore TYPE RespondingNodeTypeConfigUpdateAck PRESENCE mandatory }|
+ { ID id-TNLA-Setup-List CRITICALITY ignore TYPE TNLA-Setup-List PRESENCE optional }|
+ { ID id-TNLA-Failed-To-Setup-List CRITICALITY ignore TYPE TNLA-Failed-To-Setup-List PRESENCE optional }|
+}
+
+```
+
+```
+{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+{ ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional }|
+{ ID id-TNLConfigurationInfo CRITICALITY ignore TYPE TNLConfigurationInfo PRESENCE optional }|
+{ ID id-Local-NG-RAN-Node-Identifier CRITICALITY ignore TYPE Local-NG-RAN-Node-Identifier PRESENCE optional }|
+{ ID id-Neighbour-NG-RAN-Node-List CRITICALITY ignore TYPE Neighbour-NG-RAN-Node-List PRESENCE optional }|
+{ ID id-Local-NG-RAN-Node-Identifier-Removal CRITICALITY ignore TYPE Local-NG-RAN-Node-Identifier PRESENCE optional },
+...
+}
+
+RespondingNodeTypeConfigUpdateAck ::= CHOICE {
+ ng-eNB RespondingNodeTypeConfigUpdateAck-ng-eNB,
+ gNB RespondingNodeTypeConfigUpdateAck-gNB,
+ choice-extension ProtocolIE-Single-Container { {RespondingNodeTypeConfigUpdateAck-ExtIEs} }
+}
+
+RespondingNodeTypeConfigUpdateAck-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+RespondingNodeTypeConfigUpdateAck-ng-eNB ::= SEQUENCE {
+ iE-Extension ProtocolExtensionContainer { {RespondingNodeTypeConfigUpdateAck-ng-eNB-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+
+RespondingNodeTypeConfigUpdateAck-ng-eNB-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-List-of-served-cells-E-UTRA CRITICALITY ignore EXTENSION ServedCells-E-UTRA PRESENCE optional }|
+ { ID id-PartialListIndicator-EUTRA CRITICALITY ignore EXTENSION PartialListIndicator PRESENCE optional }|
+ { ID id-CellAndCapacityAssistanceInfo-EUTRA CRITICALITY ignore EXTENSION CellAndCapacityAssistanceInfo-EUTRA PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+RespondingNodeTypeConfigUpdateAck-gNB ::= SEQUENCE {
+ served-NR-Cells ServedCells-NR OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {RespondingNodeTypeConfigUpdateAck-gNB-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+RespondingNodeTypeConfigUpdateAck-gNB-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-PartialListIndicator-NR CRITICALITY ignore EXTENSION PartialListIndicator PRESENCE optional }|
+ { ID id-CellAndCapacityAssistanceInfo-NR CRITICALITY ignore EXTENSION CellAndCapacityAssistanceInfo-NR PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+
+```
+
+-- NG-RAN NODE CONFIGURATION UPDATE FAILURE
+
+--
+
+-- \*\*\*\*\*
+
+NGRANNodeConfigurationUpdateFailure ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{NGRANNodeConfigurationUpdateFailure-IEs}},
+
+ ...
+
+}
+
+NGRANNodeConfigurationUpdateFailure-IEs XNAP-PROTOCOL-IES ::= {
+
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+
+ { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }|
+
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+
+ ...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- E-UTRA NR CELL RESOURCE COORDINATION REQUEST
+
+--
+
+-- \*\*\*\*\*
+
+```
+E-UTRA-NR-CellResourceCoordinationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{E-UTRA-NR-CellResourceCoordinationRequest-IEs}},
+ ...
+}
+
+E-UTRA-NR-CellResourceCoordinationRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-initiatingNodeType-ResourceCoordRequest CRITICALITY reject TYPE InitiatingNodeType-ResourceCoordRequest PRESENCE mandatory}|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+InitiatingNodeType-ResourceCoordRequest ::= CHOICE {
+ ng-eNB ResourceCoordRequest-ng-eNB-initiated,
+ gNB ResourceCoordRequest-gNB-initiated,
+ choice-extension ProtocolIE-Single-Container { {InitiatingNodeType-ResourceCoordRequest-ExtIEs} }
+}
+
+InitiatingNodeType-ResourceCoordRequest-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+ResourceCoordRequest-ng-eNB-initiated ::= SEQUENCE {
+```
+
+```
+ dataTrafficResourceIndication DataTrafficResourceIndication,
+ spectrumSharingGroupID SpectrumSharingGroupID,
+ listOfE-UTRACells SEQUENCE (SIZE(1.. maxnoofCellsinNG-RANnode)) OF E-UTRA-CGI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ResourceCoordRequest-ng-eNB-initiated-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ResourceCoordRequest-ng-eNB-initiated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ResourceCoordRequest-gNB-initiated ::= SEQUENCE {
+ dataTrafficResourceIndication DataTrafficResourceIndication,
+ listOfE-UTRACells SEQUENCE (SIZE(1.. maxnoofCellsinNG-RANnode)) OF E-UTRA-CGI OPTIONAL,
+ spectrumSharingGroupID SpectrumSharingGroupID,
+ listOfNRCells SEQUENCE (SIZE(1.. maxnoofCellsinNG-RANnode)) OF NR-CGI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ResourceCoordRequest-gNB-initiated-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ResourceCoordRequest-gNB-initiated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+```
+
+```
+-- **************************************************************
+```
+
+```
+--
+```
+
+```
+-- E-UTRA NR CELL RESOURCE COORDINATION RESPONSE
+```
+
+```
+--
+```
+
+```
+-- **************************************************************
+```
+
+```
+E-UTRA-NR-CellResourceCoordinationResponse ::= SEQUENCE {
+```
+
+```
+ protocolIEs ProtocolIE-Container {{E-UTRA-NR-CellResourceCoordinationResponse-IEs}},
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+E-UTRA-NR-CellResourceCoordinationResponse-IEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ { ID id-respondingNodeType-ResourceCoordResponse CRITICALITY reject TYPE RespondingNodeType-ResourceCoordResponse PRESENCE mandatory } |
+```
+
+```
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RespondingNodeType-ResourceCoordResponse ::= CHOICE {
+```
+
+```
+ ng-eNB ResourceCoordResponse-ng-eNB-initiated,
+```
+
+```
+ gNB ResourceCoordResponse-gNB-initiated,
+```
+
+```
+choice-extension ProtocolIE-Single-Container { {RespondingNodeType-ResourceCoordResponse-ExtIEs} }
+}
+
+RespondingNodeType-ResourceCoordResponse-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+ResourceCoordResponse-ng-eNB-initiated ::= SEQUENCE {
+ dataTrafficResourceIndication DataTrafficResourceIndication,
+ spectrumSharingGroupID SpectrumSharingGroupID,
+ listOfE-UTRACells SEQUENCE (SIZE(1.. maxnoofCellsinNG-RANnode)) OF E-UTRA-CGI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ResourceCoordResponse-ng-eNB-initiated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ResourceCoordResponse-ng-eNB-initiated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ResourceCoordResponse-gNB-initiated ::= SEQUENCE {
+ dataTrafficResourceIndication DataTrafficResourceIndication,
+ spectrumSharingGroupID SpectrumSharingGroupID,
+```
+
+```
+
+listOfNRCells SEQUENCE (SIZE(1.. maxnoofCellsinNG-RANnode)) OF NR-CGI OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {ResourceCoordResponse-gNB-initiated-ExtIEs} } OPTIONAL,
+...
+}
+
+```
+
+```
+
+ResourceCoordResponse-gNB-initiated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- SECONDARY RAT DATA USAGE REPORT
+--
+-- *****
+
+```
+
+```
+
+SecondaryRATDataUsageReport ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{SecondaryRATDataUsageReport-IEs}},
+ ...
+}
+
+```
+
+```
+
+SecondaryRATDataUsageReport-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory} |
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory} |
+
+```
+
+```
+
+ { ID id-PDUSessionResourceSecondaryRATUsageList CRITICALITY reject TYPE PDUSessionResourceSecondaryRATUsageList PRESENCE mandatory},
+ ...
+}
+
+-- *****
+--
+-- XN REMOVAL REQUEST
+--
+-- *****
+
+XnRemovalRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ XnRemovalRequest-IEs }},
+ ...
+}
+
+XnRemovalRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-GlobalNG-RAN-node-ID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE mandatory} |
+ { ID id-XnRemovalThreshold CRITICALITY reject TYPE XnBenefitValue PRESENCE optional } |
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- XN REMOVAL RESPONSE
+--
+-- *****
+
+```
+
+```
+
+XnRemovalResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ XnRemovalResponse-IEs}},
+ ...
+}
+
+```
+
+```
+
+XnRemovalResponse-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-GlobalNG-RAN-node-ID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- XN REMOVAL FAILURE
+--
+-- *****
+
+```
+
+```
+
+XnRemovalFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ XnRemovalFailure-IEs}},
+ ...
+}
+
+XnRemovalFailure-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+-- *****
+--
+-- CELL ACTIVATION REQUEST
+--
+-- *****
+
+CellActivationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ CellActivationRequest-IEs}},
+ ...
+}
+
+```
+
+```
+CellActivationRequest-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-ServedCellsToActivate CRITICALITY reject TYPE ServedCellsToActivate PRESENCE mandatory}|
+ { ID id-ActivationIDforCellActivation CRITICALITY reject TYPE ActivationIDforCellActivation PRESENCE mandatory}|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+ServedCellsToActivate ::= CHOICE {
+ nr-cells SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF NR-CGI,
+ e-utra-cells SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF E-UTRA-CGI,
+ choice-extension ProtocolIE-Single-Container { {ServedCellsToActivate-ExtIEs} }
+}
+
+ServedCellsToActivate-ExtIEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-NRCellsAndSSBsList CRITICALITY ignore TYPE ToBeActivatedNRCellsAndSSBsList PRESENCE mandatory},
+ ...
+}
+
+ToBeActivatedNRCellsAndSSBsList ::= SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF ToBeActivatedNRCellsAndSSBs-Item
+
+ToBeActivatedNRCellsAndSSBs-Item ::= SEQUENCE {
+ nrCGI NR-CGI,
+```
+
+```
+
+ssBstobeActivatedList SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF ssBsToBeActivated-Item OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { { ToBeActivatedNRCellsAndSSBs-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+```
+
+```
+
+ToBeActivatedNRCellsAndSSBs-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+ssBsToBeActivated-Item ::= SEQUENCE {
+ ssbIndex INTEGER(0..63),
+ iE-Extensions ProtocolExtensionContainer { { ssBsToBeActivated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ssBsToBeActivated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- CELL ACTIVATION RESPONSE
+--
+
+```
+
+-- \*\*\*\*\*
+
+```
+
+CellActivationResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{CellActivationResponse-IEs}},
+ ...
+}
+
+```
+
+```
+
+CellActivationResponse-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-ActivatedServedCells CRITICALITY reject TYPE ActivatedServedCells PRESENCE mandatory}|
+ { ID id-ActivationIDforCellActivation CRITICALITY reject TYPE ActivationIDforCellActivation PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+ActivatedServedCells ::= CHOICE {
+ nr-cells SEQUENCE (SIZE(1..maxnoofCellsInNG-RANnode)) OF NR-CGI,
+ e-utra-cells SEQUENCE (SIZE(1..maxnoofCellsInNG-RANnode)) OF E-UTRA-CGI,
+ choice-extension ProtocolIE-Single-Container { {ActivatedServedCells-ExtIEs} }
+}
+
+```
+
+```
+
+ActivatedServedCells-ExtIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-ActivatedNRCellsAndSSBsList CRITICALITY ignore TYPE ActivatedNRCellsAndSSBsList PRESENCE mandatory},
+}
+
+```
+
+```
+...
+}
+
+ActivatedNRCellsAndSSBsList ::= SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF ActivatedNRCellsAndSSBs-Item
+
+ActivatedNRCellsAndSSBs-Item ::= SEQUENCE {
+ nrCGI NR-CGI,
+ sSBsActivatedList SEQUENCE (SIZE(1..maxnoofSSBAreas)) OF SSBsActivated-Item OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ActivatedNRCellsAndSSBs-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ActivatedNRCellsAndSSBs-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SSBsActivated-Item ::= SEQUENCE {
+ ssbIndex INTEGER(0..63),
+ iE-Extensions ProtocolExtensionContainer { {SSBsActivated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SSBsActivated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- CELL ACTIVATION FAILURE
+
+--
+
+-- \*\*\*\*\*
+
+CellActivationFailure ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{CellActivationFailure-IEs}},
+
+ ...
+
+}
+
+CellActivationFailure-IEs XNAP-PROTOCOL-IEs ::= {
+
+ { ID id-ActivationIDforCellActivation CRITICALITY reject TYPE ActivationIDforCellActivation PRESENCE mandatory}|
+
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+
+ ...
+
+}
+
+-- \*\*\*\*\*
+
+```
+
+--
+-- RESET REQUEST
+--
+-- *****
+
+```
+
+```
+
+ResetRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ResetRequest-IEs}},
+ ...
+}
+
+```
+
+```
+
+ResetRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-ResetRequestTypeInfo CRITICALITY reject TYPE ResetRequestTypeInfo PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- RESET RESPONSE
+--
+-- *****
+
+```
+
+ResetResponse ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ResetResponse-IEs}},
+
+ ...
+
+}
+
+ResetResponse-IEs XNAP-PROTOCOL-IES ::= {
+
+ { ID id-ResetResponseTypeInfo CRITICALITY reject TYPE ResetResponseTypeInfo PRESENCE mandatory } |
+
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } |
+
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+
+ ...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- ERROR INDICATION
+
+--
+
+-- \*\*\*\*\*
+
+ErrorIndication ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ErrorIndication-IEs}},
+
+ ...
+
+}
+
+```
+
+ErrorIndication-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-oldNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE optional }|
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE optional }|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional }|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+ { ID id-InterfaceInstanceIndication CRITICALITY reject TYPE InterfaceInstanceIndication PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PRIVATE MESSAGE
+--
+-- *****
+
+```
+
+```
+
+PrivateMessage ::= SEQUENCE {
+ privateIEs PrivateIE-Container {{PrivateMessage-IEs}},
+ ...
+}
+
+```
+
+```
+
+PrivateMessage-IEs XNAP-PRIVATE-IEs ::= {
+ ...
+}
+
+```
+
+```
+-- *****
+--
+-- TRACE START
+--
+-- *****
+```
+
+```
+TraceStart ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {TraceStartIEs} },
+ ...
+}
+```
+
+```
+TraceStartIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE optional },
+ ...
+}
+```
+
+```
+-- *****
+--
+-- DEACTIVATE TRACE
+```
+
+--
+-- \*\*\*\*\*
+
+DeactivateTrace ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {DeactivateTraceIEs} },
+ ...
+}
+
+DeactivateTraceIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-NG-RANTraceID CRITICALITY ignore TYPE NG-RANTraceID PRESENCE mandatory},
+ ...
+}
+
+-- \*\*\*\*\*
+--
+
+-- FAILURE INDICATION
+
+--
+-- \*\*\*\*\*
+
+FailureIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{FailureIndication-IEs}},
+
+```
+
+ ...
+ }
+
+ FailureIndication-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-InitiatingCondition-FailureIndication
+ CRITICALITY reject TYPE InitiatingCondition-FailureIndication
+ PRESENCE mandatory},
+ ...
+ }
+
+ -- *****
+ --
+ -- HANDOVER REPORT
+ --
+ -- *****
+
+```
+
+```
+
+HandoverReport ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ HandoverReport-IEs}},
+ ...
+}
+
+```
+
+```
+
+HandoverReport-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-HandoverReportType CRITICALITY ignore TYPE HandoverReportType PRESENCE mandatory}|
+ { ID id-HandoverCause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-SourceCellCGI CRITICALITY ignore TYPE GlobalNG-RANCell-ID PRESENCE mandatory }|
+
+```
+
+```
+
+ { ID id-TargetCellCGI CRITICALITY ignore TYPE GlobalNG-RANCell-ID PRESENCE mandatory }|
+ { ID id-ReEstablishmentCellCGI CRITICALITY ignore TYPE GlobalCell-ID PRESENCE conditional }|
+
+-- This IE shall be present if the Handover Report Type IE is set to the value "HO to wrong cell"
+ { ID id-TargetCellinEUTRAN CRITICALITY ignore TYPE TargetCellinEUTRAN PRESENCE conditional }|
+
+-- This IE shall be present if the Handover Report Type IE is set to the value "Inter-system ping-pong"
+ { ID id-SourceCellCRNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional }|
+ { ID id-MobilityInformation CRITICALITY ignore TYPE MobilityInformation PRESENCE optional }|
+ { ID id-UERLFReportContainer CRITICALITY ignore TYPE UERLFReportContainer PRESENCE optional }|
+ { ID id-CHOConfiguration CRITICALITY ignore TYPE CHOConfiguration PRESENCE optional }|
+ { ID id-TargetCellCRNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional }|
+ { ID id-TimeSinceFailure CRITICALITY ignore TYPE TimeSinceFailure PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- RESOURCE STATUS REQUEST
+--
+-- *****
+
+```
+
+```
+
+ResourceStatusRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ResourceStatusRequest-IEs}},
+ ...
+}
+
+```
+
+```
+
+}
+
+ResourceStatusRequest-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY ignore TYPE Measurement-ID PRESENCE conditional}|
+-- This IE shall be present if the Registration Request IE is set to the value "stop" or "add".
+ { ID id-RegistrationRequest CRITICALITY reject TYPE RegistrationRequest PRESENCE mandatory}|
+ { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics PRESENCE conditional}|
+-- This IE shall be present if the Registration Request IE is set to the value "start".
+ { ID id-CellToReport CRITICALITY ignore TYPE CellToReport PRESENCE optional}|
+ { ID id-ReportingPeriodicity CRITICALITY ignore TYPE ReportingPeriodicity PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- RESOURCE STATUS RESPONSE
+--
+-- *****
+
+```
+
+```
+
+ResourceStatusResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ResourceStatusResponse-IEs}},
+
+```
+
+...
+}
+
+ResourceStatusResponse-IEs XNAP-PROTOCOL-IEs ::= {
+
+{ ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+{ ID id-NGRAN-Node2-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
+...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- RESOURCE STATUS FAILURE
+
+--
+
+-- \*\*\*\*\*
+
+ResourceStatusFailure ::= SEQUENCE {
+
+protocolIEs ProtocolIE-Container {{ResourceStatusFailure-IEs}},
+...
+
+}
+
+ResourceStatusFailure-IEs XNAP-PROTOCOL-IEs ::= {
+
+```
+
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- RESOURCE STATUS UPDATE
+--
+-- *****
+
+```
+
+```
+
+ResourceStatusUpdate ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ResourceStatusUpdate-IEs}},
+ ...
+}
+
+```
+
+```
+
+ResourceStatusUpdate-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-CellMeasurementResult CRITICALITY ignore TYPE CellMeasurementResult PRESENCE mandatory},
+
+```
+
+```
+
+ ...
+ }
+
+ -- *****
+ --
+ -- MOBILITY CHANGE REQUEST
+ --
+ -- *****
+
+```
+
+```
+
+MobilityChangeRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{MobilityChangeRequest-IEs}},
+ ...
+}
+
+```
+
+```
+
+MobilityChangeRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-NG-RANnode1CellID CRITICALITY reject TYPE GlobalNG-RANCell-ID PRESENCE mandatory}|
+ { ID id-NG-RANnode2CellID CRITICALITY reject TYPE GlobalNG-RANCell-ID PRESENCE mandatory}|
+ { ID id-NG-RANnode1MobilityParameters CRITICALITY reject TYPE MobilityParametersInformation PRESENCE optional}|
+ { ID id-NG-RANnode2ProposedMobilityParameters CRITICALITY reject TYPE MobilityParametersInformation PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-SSBOffsets-List CRITICALITY ignore TYPE SSBOffsets-List PRESENCE optional},
+ ...
+}
+
+```
+
+```
+-- *****
+--
+-- MOBILITY CHANGE ACKNOWLEDGE
+--
+-- *****
+```
+
+```
+MobilityChangeAcknowledge ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{MobilityChangeAcknowledge-IEs}},
+ ...
+}
+```
+
+```
+MobilityChangeAcknowledge-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-NG-RANnode1CellID CRITICALITY reject TYPE GlobalNG-RANCell-ID PRESENCE mandatory}|
+ { ID id-NG-RANnode2CellID CRITICALITY reject TYPE GlobalNG-RANCell-ID PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
+ ...
+}
+```
+
+```
+-- *****
+--
+```
+
+-- MOBILITY CHANGE FAILURE
+
+--
+
+-- \*\*\*\*\*
+
+MobilityChangeFailure ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{MobilityChangeFailure-IEs}},
+
+ ...
+
+}
+
+MobilityChangeFailure-IEs XNAP-PROTOCOL-IES ::= {
+
+| | | | |
+|------------------------------------------------|--------------------|---------------------------------------------|---------------------|
+| { ID id-NG-RANnode1CellID | CRITICALITY reject | TYPE GlobalNG-RANCell-ID | PRESENCE mandatory} |
+| { ID id-NG-RANnode2CellID | CRITICALITY reject | TYPE GlobalNG-RANCell-ID | PRESENCE mandatory} |
+| { ID id-Cause | CRITICALITY ignore | TYPE Cause | PRESENCE mandatory} |
+| { ID id-MobilityParametersModificationRange | CRITICALITY reject | TYPE MobilityParametersModificationRange | PRESENCE optional} |
+| { ID id-CriticalityDiagnostics | CRITICALITY ignore | TYPE CriticalityDiagnostics | PRESENCE optional} |
+| { ID id-NG-RANnode2SSBOffsetsModificationRange | CRITICALITY ignore | TYPE NG-RANnode2SSBOffsetsModificationRange | PRESENCE optional}, |
+| ... | | | |
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- ACCESS AND MOBILITY INDICATION
+
+--
+-- \*\*\*\*\*
+
+AccessAndMobilityIndication ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ AccessAndMobilityIndication-IEs}},
+ ...
+}
+
+AccessAndMobilityIndication-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-RAReport CRITICALITY ignore TYPE RAReport PRESENCE optional}|
+ { ID id-SuccessfulHOREportInformation CRITICALITY ignore TYPE SuccessfulHOREportInformation PRESENCE optional}|
+ { ID id-SuccessfulPSCellChangeReportInformation CRITICALITY ignore TYPE SuccessfulPSCellChangeReportInformation PRESENCE optional}|
+ { ID id-DLLBTFailureInformationList CRITICALITY ignore TYPE DLLBTFailureInformationList PRESENCE optional},
+ ...
+}
+
+-- \*\*\*\*\*
+
+--
+-- CELL TRAFFIC TRACE
+--
+
+-- \*\*\*\*\*
+
+CellTrafficTrace ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { {CellTrafficTraceIEs} },
+
+```
+
+ ...
+ }
+
+ CellTrafficTraceIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-NG-RANTraceID CRITICALITY ignore TYPE NG-RANTraceID PRESENCE mandatory}|
+ { ID id-TraceCollectionEntityIPAddress CRITICALITY ignore TYPE TransportLayerAddress PRESENCE mandatory}|
+ { ID id-PrivacyIndicator CRITICALITY ignore TYPE PrivacyIndicator PRESENCE optional }|
+ { ID id-TraceCollectionEntityURI CRITICALITY ignore TYPE URIaddress PRESENCE optional },
+ ...
+ }
+
+ -- *****
+ --
+ -- RAN MULTICAST GROUP PAGING
+ --
+ -- *****
+
+ RANMulticastGroupPaging ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{RANMulticastGroupPaging-IEs}},
+ ...
+ }
+
+```
+
+```
+
+RANMulticastGroupPaging-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-MBS-Session-ID CRITICALITY reject TYPE MBS-Session-ID PRESENCE mandatory}|
+ { ID id-UEIdentityIndexList-MBSGroupPaging CRITICALITY reject TYPE UEIdentityIndexList-MBSGroupPaging PRESENCE mandatory}|
+ { ID id-MulticastRANPagingArea CRITICALITY reject TYPE RANPagingArea PRESENCE mandatory},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- SCG FAILURE INFORMATION REPORT
+--
+-- *****
+
+```
+
+```
+
+ScgFailureInformationReport ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ ScgFailureInformationReport-IEs}},
+ ...
+}
+
+```
+
+```
+
+ScgFailureInformationReport-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-SourcePSCellCGI CRITICALITY ignore TYPE GlobalNG-RANCell-ID PRESENCE optional }|
+
+```
+
+```
+
+ { ID id-FailedPSCellCGI CRITICALITY ignore TYPE GlobalNG-RANCell-ID PRESENCE optional }|
+ { ID id-SCGFailureReportContainer CRITICALITY ignore TYPE SCGFailureReportContainer PRESENCE mandatory}|
+ { ID id-SNMobilityInformation CRITICALITY ignore TYPE SNMobilityInformation PRESENCE optional }|
+ { ID id-CPACConfiguration CRITICALITY ignore TYPE CPACConfiguration PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- SCG FAILURE TRANSFER
+--
+-- *****
+
+```
+
+```
+
+ScgFailureTransfer ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ ScgFailureTransfer-IEs}},
+ ...
+}
+
+```
+
+```
+
+ScgFailureTransfer-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- F1-C TRAFFIC TRANSFER
+--
+-- *****
+
+```
+
+```
+
+F1CTrafficTransfer ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ F1CTrafficTransfer-IEs}},
+ ...
+}
+
+```
+
+```
+
+F1CTrafficTransfer-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-F1CTrafficContainer CRITICALITY reject TYPE F1CTrafficContainer PRESENCE mandatory},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+
+```
+
+-- IAB TRANSPORT MIGRATION MANAGEMENT REQUEST
+
+--
+
+-- \*\*\*\*\*
+
+IABTransportMigrationManagementRequest ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ IABTransportMigrationManagementRequest-IEs}},
+
+ ...
+
+}
+
+IABTransportMigrationManagementRequest-IEs XNAP-PROTOCOL-IES ::= {
+
+| | | | |
+|---------------------------------------------|--------------------|------------------------------------|----------------------|
+| { ID id-F1-Terminating-IAB-DonorUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-nonF1-Terminating-IAB-DonorUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-TrafficToBeAddedList | CRITICALITY reject | TYPE TrafficToBeAddedList | PRESENCE optional } |
+| { ID id-TrafficToBeModifiedList | CRITICALITY reject | TYPE TrafficToBeModifiedList | PRESENCE optional } |
+| { ID id-TrafficToBeReleaseInformation | CRITICALITY reject | TYPE TrafficToBeReleaseInformation | PRESENCE optional } |
+| { ID id-IAB-TNL-Address-Request | CRITICALITY reject | TYPE IAB-TNL-Address-Request | PRESENCE optional } |
+| { ID id-IABTNLAddressException | CRITICALITY reject | TYPE IABTNLAddressException | PRESENCE optional } |
+| { ID id-MIAB-MT-BAP-Address | CRITICALITY reject | TYPE BAPAddress | PRESENCE optional }, |
+
+ ...
+
+}
+
+TrafficToBeAddedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficToBeAdded-Item
+
+```
+TrafficToBeAdded-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ trafficProfile TrafficProfile,
+ f1-TerminatingTopologyBHInformation Fl-TerminatingTopologyBHInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {TrafficToBeAdded-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficToBeAdded-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TrafficToBeModifiedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficToBeModified-Item
+
+TrafficToBeModified-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ trafficProfile TrafficProfile OPTIONAL,
+ f1-TerminatingTopologyBHInformation Fl-TerminatingTopologyBHInformation OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {TrafficToBeModified-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficToBeModified-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+
+ ...
+ }
+
+ -- *****
+ --
+ -- IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE
+ --
+ -- *****
+
+```
+
+```
+
+IABTransportMigrationManagementResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ IABTransportMigrationManagementResponse-IEs}},
+ ...
+}
+
+```
+
+```
+
+IABTransportMigrationManagementResponse-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-F1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-nonF1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-TrafficAddedList CRITICALITY reject TYPE TrafficAddedList PRESENCE optional }|
+ { ID id-TrafficModifiedList CRITICALITY reject TYPE TrafficModifiedList PRESENCE optional }|
+ { ID id-TrafficNotAddedList CRITICALITY reject TYPE TrafficNotAddedList PRESENCE optional }|
+ { ID id-TrafficNotModifiedList CRITICALITY reject TYPE TrafficNotModifiedList PRESENCE optional }|
+ { ID id-IAB-TNL-Address-Response CRITICALITY reject TYPE IAB-TNL-Address-Response PRESENCE optional }|
+ { ID id-TrafficReleasedList CRITICALITY reject TYPE TrafficReleasedList PRESENCE optional },
+
+```
+
+```
+ ...
+}
+
+TrafficAddedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficAdded-Item
+
+TrafficAdded-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ non-Fl-TerminatingTopologyBHInformation Non-Fl-TerminatingTopologyBHInformation,
+ iE-Extensions ProtocolExtensionContainer { {TrafficAdded-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficAdded-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TrafficModifiedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficModified-Item
+
+TrafficModified-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ non-Fl-TerminatingTopologyBHInformation Non-Fl-TerminatingTopologyBHInformation,
+ iE-Extensions ProtocolExtensionContainer { {TrafficModified-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+```
+
+```
+TrafficModified-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+TrafficNotAddedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficNotAdded-Item
+```
+
+```
+TrafficNotAdded-Item ::= SEQUENCE {
+```
+
+```
+ trafficIndex TrafficIndex,
+```
+
+```
+ casue Cause OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {TrafficNotAdded-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+TrafficNotAdded-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+TrafficNotModifiedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficNotModified-Item
+```
+
+```
+TrafficNotModified-Item ::= SEQUENCE {
+```
+
+```
+ trafficIndex TrafficIndex,
+```
+
+```
+ cause Cause OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {TrafficNotModified-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+TrafficNotModified-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+TrafficReleasedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficReleased-Item
+```
+
+```
+TrafficReleased-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ bHInfoList BHInfoList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { TrafficReleased-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+TrafficReleased-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+
+-- *****
+--
+-- IAB TRANSPORT MIGRATION MANAGEMENT REJECT
+--
+-- *****
+
+```
+
+```
+
+IABTransportMigrationManagementReject ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ IABTransportMigrationManagementReject-IEs}},
+ ...
+}
+
+```
+
+```
+
+IABTransportMigrationManagementReject-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-F1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-nonF1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+
+```
+
+-- IAB TRANSPORT MIGRATION MODIFICATION REQUEST
+
+--
+
+-- \*\*\*\*\*
+
+IABTransportMigrationModificationRequest ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ IABTransportMigrationModificationRequest-IEs}},
+
+ ...
+
+}
+
+IABTransportMigrationModificationRequest-IEs XNAP-PROTOCOL-IES ::= {
+
+| | | | |
+|---------------------------------------------|--------------------|--------------------------------------|----------------------|
+| { ID id-F1-Terminating-IAB-DonorUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-nonF1-Terminating-IAB-DonorUEXnAPID | CRITICALITY reject | TYPE NG-RANnodeUEXnAPID | PRESENCE mandatory} |
+| { ID id-TrafficRequiredToBeModifiedList | CRITICALITY reject | TYPE TrafficRequiredToBeModifiedList | PRESENCE optional } |
+| { ID id-TrafficToBeReleaseInformation | CRITICALITY reject | TYPE TrafficToBeReleaseInformation | PRESENCE optional } |
+| { ID id-IABTNLAddressToBeAdded | CRITICALITY reject | TYPE IAB-TNL-Address-Response | PRESENCE optional } |
+| { ID id-IABTNLAddressToBeReleasedList | CRITICALITY reject | TYPE IABTNLAddressToBeReleasedList | PRESENCE optional } |
+| { ID id-IABAuthorizationStatus | CRITICALITY ignore | TYPE IABAuthorizationStatus | PRESENCE optional } |
+| { ID id-MobileIAB-AuthorizationStatus | CRITICALITY ignore | TYPE MobileIAB-AuthorizationStatus | PRESENCE optional }, |
+
+ ...
+
+}
+
+TrafficRequiredToBeModifiedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficRequiredToBeModified-Item
+
+```
+TrafficRequiredToBeModified-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ non-fl-TerminatingTopologyBHInformation Non-Fl-TerminatingTopologyBHInformation,
+ iE-Extensions ProtocolExtensionContainer{ { TrafficRequiredToBeModified-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficRequiredToBeModified-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IABTNLAddressToBeReleasedList ::= SEQUENCE (SIZE(1..maxnoofTLAsIAB)) OF IABTNLAddressToBeReleased-Item
+
+IABTNLAddressToBeReleased-Item ::= SEQUENCE {
+ iabTNLAddress IABTNLAddress,
+ iE-Extensions ProtocolExtensionContainer{ { IABTNLAddressToBeReleased-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+IABTNLAddressToBeReleased-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+-- *****
+--
+-- IAB TRANSPORT MIGRATION MODIFICATION RESPONSE
+--
+-- *****
+```
+
+```
+IABTransportMigrationModificationResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ IABTransportMigrationModificationResponse-IEs}},
+ ...
+}
+```
+
+```
+IABTransportMigrationModificationResponse-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-F1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-nonF1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-TrafficRequiredModifiedList CRITICALITY reject TYPE TrafficRequiredModifiedList PRESENCE optional }|
+ { ID id-TrafficReleasedList CRITICALITY reject TYPE TrafficReleasedList PRESENCE optional },
+ ...
+}
+```
+
+TrafficRequiredModifiedList ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficRequiredModified-Item
+
+TrafficRequiredModified-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ iE-Extensions ProtocolExtensionContainer { { TrafficRequiredModified-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficRequiredModified-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- \*\*\*\*\*
+--
+-- IAB RESOURCE COORDINATION REQUEST
+--
+-- \*\*\*\*\*
+
+IABResourceCoordinationRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ IABResourceCoordinationRequest-IEs}},
+ ...
+}
+
+```
+IABResourceCoordinationRequest-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-F1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-nonF1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-BoundaryNodeCellsList CRITICALITY reject TYPE BoundaryNodeCellsList PRESENCE optional }|
+ { ID id-ParentNodeCellsList CRITICALITY reject TYPE ParentNodeCellsList PRESENCE optional },
+ ...
+}
+```
+
+```
+BoundaryNodeCellsList ::= SEQUENCE (SIZE(1..maxnoofServedCellsIAB)) OF BoundaryNodeCellsList-Item
+```
+
+```
+BoundaryNodeCellsList-Item ::= SEQUENCE {
+ boundaryNodeCellInformation IABCellInformation,
+ iE-Extensions ProtocolExtensionContainer { {BoundaryNodeCellsList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+BoundaryNodeCellsList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ParentNodeCellsList ::= SEQUENCE (SIZE(1..maxnoofServingCells)) OF ParentNodeCellsList-Item
+```
+
+```
+
+ParentNodeCellsList-Item ::= SEQUENCE {
+ parentNodeCellInformation IABCellInformation,
+ iE-Extensions ProtocolExtensionContainer { {ParentNodeCellsList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ParentNodeCellsList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- IAB RESOURCE COORDINATION RESPONSE
+--
+-- *****
+
+```
+
+```
+
+IABResourceCoordinationResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container { { IABResourceCoordinationResponse-IEs} },
+ ...
+}
+
+```
+
+```
+
+IABResourceCoordinationResponse-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-F1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-nonF1-Terminating-IAB-DonorUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-BoundaryNodeCellsList CRITICALITY reject TYPE BoundaryNodeCellsList PRESENCE optional }|
+ { ID id-ParentNodeCellsList CRITICALITY reject TYPE ParentNodeCellsList PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- CONDITIONAL PSCELL CHANGE CANCEL
+--
+-- *****
+
+```
+
+```
+
+CPCCancel ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ CPCCancel-IEs}},
+ ...
+}
+
+```
+
+```
+
+CPCCancel-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-M-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-S-NG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional }|
+ { ID id-target-S-NG-RANnodeID CRITICALITY reject TYPE GlobalNG-RANNode-ID PRESENCE mandatory},
+
+```
+
+```
+
+ ...
+ }
+
+ -- *****
+ --
+ -- PARTIAL UE CONTEXT TRANSFER
+ --
+ -- *****
+
+ PartialUEContextTransfer ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{ PartialUEContextTransfer-IEs }},
+ ...
+ }
+
+ PartialUEContextTransfer-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY reject TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-oldNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+ { ID id-SDTPartialUEContextInfo CRITICALITY ignore TYPE SDTPartialUEContextInfo PRESENCE mandatory}|
+ { ID id-PosPartialUEContextInfo CRITICALITY ignore TYPE PosPartialUEContextInfo PRESENCE optional },
+ ...
+ }
+
+ -- *****
+ --
+
+```
+
+-- PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE
+
+--
+
+-- \*\*\*\*\*
+
+PartialUEContextTransferAcknowledge ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ PartialUEContextTransferAcknowledge-IEs}},
+
+ ...
+
+}
+
+PartialUEContextTransferAcknowledge-IEs XNAP-PROTOCOL-IES ::= {
+
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+ { ID id-oldNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+ { ID id-SDTDataForwardingDRBList CRITICALITY ignore TYPE SDTDataForwardingDRBList PRESENCE optional }|
+
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
+
+ { ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional },
+
+ ...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- PARTIAL UE CONTEXT TRANSFER FAILURE
+
+--
+
+-- \*\*\*\*\*
+
+PartialUEContextTransferFailure ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ PartialUEContextTransferFailure-IEs}},
+
+ ...
+
+}
+
+PartialUEContextTransferFailure-IEs XNAP-PROTOCOL-IES ::= {
+
+ { ID id-newNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+ { ID id-oldNG-RANnodeUEXnAPID CRITICALITY ignore TYPE NG-RANnodeUEXnAPID PRESENCE mandatory}|
+
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
+
+ ...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- RACH INDICATION
+
+--
+
+-- \*\*\*\*\*
+
+RachIndication ::= SEQUENCE {
+
+ protocolIEs ProtocolIE-Container {{ RachIndication-IEs}},
+
+ ...
+
+```
+
+}
+
+RachIndication-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-RaReportIndicationList CRITICALITY reject TYPE RaReportIndicationList PRESENCE mandatory },
+ ...
+}
+
+-- *****
+--
+-- DATA COLLECTION REQUEST
+--
+-- *****
+
+DataCollectionRequest ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{DataCollectionRequest-IEs}},
+ ...
+}
+
+DataCollectionRequest-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY ignore TYPE Measurement-ID PRESENCE conditional}|
+ -- This IE shall be present if the Registration Request IE is set to the value "stop".
+ { ID id-RegistrationRequest CRITICALITY reject TYPE RegistrationRequest PRESENCE mandatory}|
+}
+
+```
+
+```
+
+ { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics PRESENCE conditional}|
+-- This IE shall be present if the Registration Request IE is set to the value "start".
+
+ { ID id-CellToReportForDataCollection-List CRITICALITY ignore TYPE CellToReportForDataCollection-List PRESENCE optional}|
+ { ID id-ReportingPeriodicity CRITICALITY ignore TYPE ReportingPeriodicity PRESENCE optional}|
+ { ID id-RequestedPredictionTime CRITICALITY ignore TYPE RequestedPredictionTime PRESENCE optional}|
+ { ID id-UETrajectoryCollectionConfiguration CRITICALITY ignore TYPE UETrajectoryCollectionConfiguration PRESENCE optional}|
+ { ID id-UEPerformanceCollectionConfiguration CRITICALITY ignore TYPE UEPerformanceCollectionConfiguration PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- DATA COLLECTION RESPONSE
+--
+-- *****
+
+```
+
+```
+
+DataCollectionResponse ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{DataCollectionResponse-IEs}},
+ ...
+}
+
+```
+
+```
+
+DataCollectionResponse-IEs XNAP-PROTOCOL-IEs ::= {
+
+```
+
+```
+
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NodeMeasurementInitiationResult-List CRITICALITY reject TYPE NodeMeasurementInitiationResult-List PRESENCE optional}|
+ { ID id-CellMeasurementInitiationResult-List CRITICALITY reject TYPE CellMeasurementInitiationResult-List PRESENCE optional}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- DATA COLLECTION FAILURE
+--
+-- *****
+
+```
+
+```
+
+DataCollectionFailure ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{DataCollectionFailure-IEs}},
+ ...
+}
+
+```
+
+```
+
+DataCollectionFailure-IEs XNAP-PROTOCOL-IES ::= {
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+
+```
+
+```
+
+ { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
+ { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
+ ...
+}
+
+```
+
+```
+-- *****
+```
+
+```
+--
+```
+
+```
+-- DATA COLLECTION UPDATE
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+
+DataCollectionUpdate ::= SEQUENCE {
+ protocolIEs ProtocolIE-Container {{DataCollectionUpdate-IEs}},
+ ...
+}
+
+```
+
+```
+
+DataCollectionUpdate-IEs XNAP-PROTOCOL-IEs ::= {
+ { ID id-NGRAN-Node1-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-NGRAN-Node2-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}|
+ { ID id-CellMeasurementResultForDataCollection CRITICALITY ignore TYPE CellMeasurementResultForDataCollection PRESENCE optional }|
+ { ID id-UEAssociatedInfoResult-List CRITICALITY ignore TYPE UEAssociatedInfoResult-List PRESENCE optional }|
+ { ID id-EnergyCost CRITICALITY ignore TYPE EnergyCost PRESENCE optional },
+
+```
+
+```
+
+ ...
+ }
+
+END
+
+-- ASN1STOP
+
+```
+
+### 9.3.5 Information Element definitions
+
+```
+
+-- ASN1START
+
+-- *****
+--
+-- Information Element Definitions
+--
+-- *****
+
+XnAP-IEs {
+
+ itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+
+ ngran-access (22) modules (3) xnap (2) version1 (1) xnap-IEs (2) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+```
+
+## IMPORTS
+
+id-CNTTypeRestrictionsForEquivalent,
+id-CNTTypeRestrictionsForServing,
+id-Additional-UL-NG-U-TNLatUPF-List,
+id-ConfiguredTACIndication,
+id-AlternativeQoSParaSetList,
+id-CurrentQoSParaSetIndex,
+id-DefaultDRB-Allowed,
+id-DLCarrierList,
+id-EndpointIPAddressAndPort,
+id-ExtendedReportIntervalMDT,
+id-ExtendedTAISliceSupportList,
+id-FiveGCMobilityRestrictionListContainer,
+id-SecondarydataForwardingInfoFromTarget-List,
+id-LastE-UTRANPLMNIdentity,
+id-LTEA2XUEPC5AggregateMaximumBitRate,
+id-IntendedTDD-DL-ULConfiguration-NR,
+id-MaxIPrate-DL,
+id-SecurityResult,
+id-OldQoSFlowMap-ULendmarkerexpected,
+id-PDUSessionCommonNetworkInstance,
+
+id-PDUSession-PairID,
+id-BPLMN-ID-Info-EUTRA,
+id-BPLMN-ID-Info-NR,
+id-DRBsNotAdmittedSetupModifyList,
+id-Secondary-MN-Xn-U-TNLInfoatM,
+id-ULForwardingProposal,
+id-DRB-IDs-takenintouse,
+id-SplitSessionIndicator,
+id-NonGBRResources-Offered,
+id-MDT-Configuration,
+id-TraceCollectionEntityURI,
+id-NPN-Broadcast-Information,
+id-NPNPagingAssistanceInformation,
+id-NPNMobilityInformation,
+id-NPN-Support,
+id-LTEUESidelinkAggregateMaximumBitRate,
+id-NRA2XUEPC5AggregateMaximumBitRate,
+id-NRUESidelinkAggregateMaximumBitRate,
+id-ExtendedRATRestrictionInformation,
+id-QoSMonitoringRequest,
+id-QoSMonitoringDisabled,
+id-QoSMonitoringReportingFrequency,
+id-DAPSRequestInfo,
+
+id-OffsetOfNbiotChannelNumberToDL-EARFCN,
+id-OffsetOfNbiotChannelNumberToUL-EARFCN,
+id-NBIoT-UL-DL-AlignmentOffset,
+id-TDDULDLConfigurationCommonNR,
+id-CarrierList,
+id-ULCarrierList,
+id-FrequencyShift7p5khz,
+id-SSB-PositionsInBurst,
+id-NRCellPRACHConfig,
+id-Redundant-UL-NG-U-TNLatUPF,
+id-Redundant-DL-NG-U-TNLatNG-RAN,
+id-CNPacketDelayBudgetDownlink,
+id-CNPacketDelayBudgetUplink,
+id-ExtendedPacketDelayBudget,
+id-Additional-Redundant-UL-NG-U-TNLatUPF-List,
+id-RedundantCommonNetworkInstance,
+id-TSCTrafficCharacteristics,
+id-RedundantQoSFlowIndicator,
+id-Additional-PDCP-Duplication-TNL-List,
+id-RedundantPDUSessionInformation,
+id-UsedRSNInformation,
+id-RLCDuplicationInformation,
+id-CSI-RSTransmissionIndication,
+
+id-UERadioCapabilityID,
+id-secondary-SN-UL-PDCP-UP-TNLInfo,
+id-pdcpDuplicationConfiguration,
+id-duplicationActivation,
+id-NPRACHConfiguration,
+id-QoSFlowsMappedtoDRB-SetupResponse-MNterminated,
+id-DL-scheduling-PDCCH-CCE-usage,
+id-UL-scheduling-PDCCH-CCE-usage,
+id-SFN-Offset,
+id-QoS-Mapping-Information,
+id-AdditionLocationInformation,
+id-dataForwardingInfoFromTargetE-UTRANnode,
+id-Cause,
+id-SecurityIndication,
+id-RRCConnReestab-Indicator,
+id-SourceDLForwardingIPAddress,
+id-SourceNodeDLForwardingIPAddress,
+id-M4ReportAmount,
+id-M5ReportAmount,
+id-M6ReportAmount,
+id-M7ReportAmount,
+id-BeamMeasurementIndicationM1,
+id-Supported-MBS-FSA-ID-List,
+
+id-MBS-AssistanceInformation,
+id-MBS-SessionAssociatedInformation,
+id-MBS-SessionInformation-List,
+id-SliceRadioResourceStatus-List,
+id-CompositeAvailableCapacitySupplementaryUplink,
+id-SSBOffsets-List,
+id-NG-RANnode2SSBOffsetsModificationRange,
+id-NR-U-Channel-List,
+id-NR-U-ChannelInfo-List,
+id-MIMOPRBusageInformation,
+id-UEAssistantIdentifier,
+id-IAB-MT-Cell-List,
+id-NoPDUSessionIndication,
+id-permutation,
+id-UL-GNB-DU-Cell-Resource-Configuration,
+id-DL-GNB-DU-Cell-Resource-Configuration,
+id-tdd-GNB-DU-Cell-Resource-Configuration,
+id-Additional-Measurement-Timing-Configuration-List,
+id-SurvivalTime,
+id-Local-NG-RAN-Node-Identifier,
+id-Neighbour-NG-RAN-Node-List,
+id-FiveGProSeUEPC5AggregateMaximumBitRate,
+id-Redcap-Bcast-Information,
+
+id-UESliceMaximumBitRateList,
+id-PositioningInformation,
+id-ServedCellSpecificInfoReq-NR,
+id-TAINSAGSupportList,
+id-earlyMeasurement,
+id-BeamMeasurementsReportConfiguration,
+id-CoverageModificationCause,
+id-UERLFReportContainerLTEExtension,
+id-ExcessPacketDelayThresholdConfiguration,
+id-Full-and-Short-I-RNTI-Profile-List,
+id-QosFlowMappingIndication,
+id-EquivalentSNPNs,
+id-CHOTimeBasedInformation,
+id-ChannelOccupancyTimePercentageUL,
+id-EnergyDetectionThresholdUL,
+id-PSCellListContainer,
+id-RadioResourceStatusNR-U,
+id-FiveGProSeLayer2Multipath,
+id-FiveGProSeLayer2UEtoUERelay,
+id-FiveGProSeLayer2UEtoUERemote,
+id-ClockQualityReportingControlInfo,
+id-CapabilityForBATAadaptation,
+id-PNI-NPNBasedMDT,
+
+id-PNI-NPN-AreaScopeofMDT,
+id-SNPN-CellBasedMDT,
+id-SNPN-TAIBasedMDT,
+id-SNPN-IDBasedMDT,
+id-S-CPAC-Request,
+id-S-CPAC-Request-Info,
+id-S-CPAC-ReferenceConfigRequest,
+id-S-CPAC-InterSN-ExecutionNotify,
+id-S-CPAC-dataforwardinginfofromSource,
+id-CPACcandidatePSCells-wotherInfo-list,
+id-eRedcap-Bcast-Information,
+id-NRPagingLongeDRXInformationforRRRCINACTIVE,
+id-MBSCommServiceType,
+id-AssistanceInformationQoE-Meas,
+id-QoERVQoEReportingPaths,
+id-DirectForwardingPathAvailability,
+id-CHO-CPAC-Info,
+id-CHO-Maxnoof-CondReconfig,
+id-PDUSetQoSParameters,
+id-N6JitterInformation,
+id-ECNMarkingorCongestionInformationReportingRequest,
+id-TAISliceUnavailableCellList,
+id-MobileIABCell,
+
+maxEARFCN,
+maxnoofAllowedAreas,
+maxnoofAMFRegions,
+maxnoofAoIs,
+maxnoofBPLMNs,
+maxnoofCAGs,
+maxnoofCAGsperPLMN,
+maxnoofCellsinAoI,
+maxnoofCellsinNG-RANnode,
+maxnoofCellsinRNA,
+maxnoofCellsinUEHistoryInfo,
+maxnoofCellsUEMovingTrajectory,
+maxnoofDRBs,
+maxnoofEPLMNs,
+maxnoofEPLMNsplu1,
+maxnoofEUTRABands,
+maxnoofEUTRABPLMNs,
+maxnoofForbiddenTACs,
+maxnoofMBSFNEUTRA,
+maxnoofMultiConnectivityMinusOne,
+maxnoofNeighbours,
+maxnoofNIDs,
+maxnoofNRCellBands,
+
+maxnoofPDUSessions,
+maxnoofPLMNs,
+maxnoofProtectedResourcePatterns,
+maxnoofQoSFlows,
+maxnoofQoSParaSets,
+maxnoofRANAreaCodes,
+maxnoofRANAreasinRNA,
+maxnoofSCellGroups,
+maxnoofSCellGroupsplus1,
+maxnoofSliceItems,
+maxnoofExtSliceItems,
+maxnoofSNPNIDs,
+maxnoofsupportedTACs,
+maxnoofsupportedPLMNs,
+maxnoofTAI,
+maxnoofTAIsinAoI,
+maxnoofTNLAssociations,
+maxnoofUEContexts,
+maxNRARFCN,
+maxNrOfErrors,
+maxnoofRANNodesinAoI,
+maxnooftimeperiods,
+maxnoofslots,
+
+maxnoofExtTLAs,
+maxnoofGTPTLAs,
+maxnoofCHOcells,
+maxnoofPC5QoSFlows,
+maxnoofSSBAreas,
+maxnoofNRSCSs,
+maxnoofPhysicalResourceBlocks,
+maxnoofRAReports,
+maxnoofAdditionalPDCPDuplicationTNL,
+maxnoofRLCDuplicationstate,
+maxnoofBluetoothName,
+maxnoofCellIDforMDT,
+maxnoofMDTPLMNs,
+maxnoofTAforMDT,
+maxnoofWLANName,
+maxnoofSensorName,
+maxnoofNeighPCIforMDT,
+maxnoofFreqforMDT,
+maxnoofNonAnchorCarrierFreqConfig,
+maxnoofDataForwardingTunneltoE-UTRAN,
+maxnoofUEIDIndicesforMBSPaging,
+maxnoofMBSFSA,
+maxnoofMBSQoSFlows,
+
+maxnoofMRBs,
+maxnoofCellsforMBS,
+maxnoofMBSServiceAreaInformation,
+maxnoofTAIforMBS,
+maxnoofAssociatedMBSSessions,
+maxnoofMBSSessions,
+maxnoofSuccessfulHOReports,
+maxnoofPSCellsPerSN,
+maxnoofNR-UChannelIDs,
+maxnoofCellsinCHO,
+maxnoofCHOexecutioncond,
+maxnoofServingCells,
+maxnoofBHInfo,
+maxnoofTLAsIAB,
+maxnoofTrafficIndexEntries,
+maxnoofBAPControlPDURLCCHs,
+maxnoofServedCellsIAB,
+maxnoofDUFSlots,
+maxnoofSymbols,
+maxnoofHSNASlots,
+maxnoofRBsetsPerCell,
+maxnoofChildIABNodes,
+maxnoofIABSTCInfo,
+
+maxnoofPSCellCandidates,
+maxnoofTargetSNs,
+maxnoofUEAppLayerMeas,
+maxnoofSNSSAIforQMC,
+maxnoofCellIDforQMC,
+maxnoofPLMNforQMC,
+maxnoofTAforQMC,
+maxnoofMTItems,
+maxnoofCSIRSconfigurations,
+maxnoofCSIRSneighbourCells,
+maxnoofCSIRSneighbourCellsInMTC,
+maxnoofNeighbour-NG-RAN-Nodes,
+maxnoofSRBs,
+maxnoofSMBR,
+maxnoofNSAGs,
+maxnoofRBsetsPerCell,
+maxnoofTargetSNsMinusOne,
+maxnoofThresholdsForExcessPacketDelay,
+maxnoofESPNs,
+maxnoofSuccessfulPSCellChangeReports,
+maxnoofUEsforRAReportIndications,
+maxnoofPSCellsinCPAC,
+maxnoofCPACexecutioncond,
+
+```
+maxnoofLBTFailureInformation,
+maxnoofCellsTrajectoryPredict,
+maxnoofCellsTrajectory,
+maxFailedCellMeasObjects,
+maxFailedMeasPerNode,
+maxnoofUEReports,
+maxnoofCandidateRelayUEs,
+maxnoofCAGforMDT,
+maxnoofMDTSNPNs,
+maxnoofSecurityConfigurations
+
+FROM XnAP-Constants
+
+Criticality,
+ProcedureCode,
+ProtocolIE-ID,
+TriggeringMessage
+FROM XnAP-CommonDataTypes
+
+ProtocolExtensionContainer{},
+ProtocolIE-Single-Container{},
+```
+
+```
+XNAP-PROTOCOL-EXTENSION,
+XNAP-PROTOCOL-IES
+FROM XnAP-Containers;
+
+-- A
+
+A2XPC5QoSParameters ::= SEQUENCE {
+ a2XPC5QoSFlowList A2XPC5QoSFlowList,
+ aA2XPC5LinkAggregateBitRates BitRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { A2XPC5QoSParameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+A2XPC5QoSParameters-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+A2XPC5QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofPC5QoSFlows)) OF A2XPC5QoSFlowItem
+
+A2XPC5QoSFlowItem ::= SEQUENCE {
+ a2XpQI FiveQI,
+ a2Xpc5FlowBitRates A2XPC5FlowBitRates OPTIONAL,
+```
+
+```
+ a2Xrange Range OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { A2XPC5QoSFlowItem-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+A2XPC5QoSFlowItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+A2XPC5FlowBitRates ::= SEQUENCE {
+ a2XguaranteedFlowBitRate BitRate,
+ a2XmaximumFlowBitRate BitRate,
+ iE-Extensions ProtocolExtensionContainer { { A2XPC5FlowBitRates-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+A2XPC5FlowBitRates-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+AdditionalListOfPDUSessionResourceChangeConfirmInfo-SNterminated ::= SEQUENCE (SIZE(1..maxnoofTargetSNsMinusOne)) OF
+AdditionalListOfPDUSessionResourceChangeConfirmInfo-SNterminated-Item
+```
+
+```
+AdditionalListOfPDUSessionResourceChangeConfirmInfo-SNterminated-Item ::= SEQUENCE {
+```
+
+```
+ pDUSessionResourceChangeConfirmInfo-SNterminated pDUSessionResourceChangeConfirmInfo-SNterminated,
+ iE-Extensions ProtocolExtensionContainer { { AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AveragePacketDelay ::= SEQUENCE {
+ uL-AveragePacketDelay AveragePacketDelayValue,
+ dL-AveragePacketDelay AveragePacketDelayValue,
+ iE-Extensions ProtocolExtensionContainer { {AveragePacketDelay-ExtIEs} } OPTIONAL,
+ ...
+}
+
+AveragePacketDelay-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AveragePacketDelayValue ::= INTEGER (0..10000)
+```
+
+```
+AdditionLocationInformation ::= ENUMERATED {
+ includePSCell,
+ ...
+}
+
+Additional-PDCP-Duplication-TNL-List ::= SEQUENCE (SIZE(1..maxnoofAdditionalPDCPDuplicationTNL)) OF Additional-PDCP-Duplication-TNL-Item
+
+Additional-PDCP-Duplication-TNL-Item ::= SEQUENCE {
+ additional-PDCP-Duplication-UP-TNL-Information UPTransportLayerInformation,
+ iE-Extensions ProtocolExtensionContainer { { Additional-PDCP-Duplication-TNL-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Additional-PDCP-Duplication-TNL-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Additional-UL-NG-U-TNLatUPF-Item ::= SEQUENCE {
+ additional-UL-NG-U-TNLatUPF UPTransportLayerInformation,
+ iE-Extensions ProtocolExtensionContainer { { Additional-UL-NG-U-TNLatUPF-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Additional-UL-NG-U-TNLatUPF-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-PDUSessionCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional},
+ ...
+}
+```
+
+Additional-UL-NG-U-TNLatUPF-List ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivityMinusOne)) OF Additional-UL-NG-U-TNLatUPF-Item
+
+Additional-Measurement-Timing-Configuration-List ::= SEQUENCE (SIZE(1.. maxnoofMTCItems)) OF Additional-Measurement-Timing-Configuration-Item
+
+Additional-Measurement-Timing-Configuration-Item ::= SEQUENCE {
+ additionalMeasurementTimingConfigurationIndex INTEGER (0..16),
+ csi-RS-MTC-Configuration-List CSI-RS-MTC-Configuration-List,
+ iE-Extensions ProtocolExtensionContainer { { Additional-Measurement-Timing-Configuration-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Additional-Measurement-Timing-Configuration-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ActivationIDforCellActivation ::= INTEGER (0..255)
+
+Active-MBS-SessionInformation ::= SEQUENCE {
+ mBS-QoSFlowsToAdd-List MBS-QoSFlowsToAdd-List,
+ mBS-ServiceArea MBS-ServiceArea OPTIONAL,
+ mBS-MappingandDataForwardingRequestInfofromSource MBS-MappingandDataForwardingRequestInfofromSource OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { Active-MBS-SessionInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+}
+
+Active-MBS-SessionInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DataCollectionID ::= SEQUENCE {
+ ng-ran-node1UEXnAPID NG-RANnodeUEXnAPID OPTIONAL,
+ ng-ran-node2UEXnAPID NG-RANnodeUEXnAPID OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { DataCollectionID-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DataCollectionID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AerialControllerUE ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+```
+
+```
+}
+
+AerialUE ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+AerialUESubscriptionInformation ::= ENUMERATED {
+ allowed,
+ not-allowed,
+ ...
+}
+
+AllocationandRetentionPriority ::= SEQUENCE {
+ priorityLevel INTEGER (0..15,...),
+ pre-emption-capability ENUMERATED {shall-not-trigger-preemption, may-trigger-preemption, ...},
+ pre-emption-vulnerability ENUMERATED {not-preemptable, preemptable, ...},
+ iE-Extensions ProtocolExtensionContainer { {AllocationandRetentionPriority-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+AllocationandRetentionPriority-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+ActivationSFN ::= INTEGER (0..1023)
+```
+
+```
+AllowedCAG-ID-List-perPLMN ::= SEQUENCE (SIZE(1..maxnoofCAGsperPLMN)) OF CAG-Identifier
+```
+
+```
+AllowedPNI-NPN-ID-List ::= SEQUENCE (SIZE(1..maxnoofEPLMNsplus1)) OF AllowedPNI-NPN-ID-Item
+```
+
+```
+AllowedPNI-NPN-ID-Item ::= SEQUENCE {
+```
+
+```
+ plmn-id PLMN-Identity,
+```
+
+```
+ pni-npn-restricted-information PNI-NPN-Restricted-Information,
+```
+
+```
+ allowed-CAG-id-list-per-plmn AllowedCAG-ID-List-perPLMN,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {AllowedPNI-NPN-ID-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+AllowedPNI-NPN-ID-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+AllTrafficIndication ::= ENUMERATED {true,...}
+
+AlternativeQoSParaSetList ::= SEQUENCE (SIZE(1..maxnoofQoSParaSets)) OF AlternativeQoSParaSetItem
+
+AlternativeQoSParaSetItem ::= SEQUENCE {
+ alternativeQoSParaSetIndex QoSParaSetIndex,
+ guaranteedFlowBitRateDL BitRate OPTIONAL,
+ guaranteedFlowBitRateUL BitRate OPTIONAL,
+ packetDelayBudget PacketDelayBudget OPTIONAL,
+ packetErrorRate PacketErrorRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {AlternativeQoSParaSetItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+AlternativeQoSParaSetItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AMF-Region-Information ::= SEQUENCE (SIZE (1..maxnoofAMFRegions)) OF GlobalAMF-Region-Information
+
+```
+GlobalAMF-Region-Information ::= SEQUENCE {
+ plmn-ID PLMN-Identity,
+ amf-region-id BIT STRING (SIZE (8)),
+ iE-Extensions ProtocolExtensionContainer { {GlobalAMF-Region-Information-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+GlobalAMF-Region-Information-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+AMF-UE-NGAP-ID ::= INTEGER (0..1099511627775)
+```
+
+```
+AreaOfInterestInformation ::= SEQUENCE (SIZE(1..maxnoofAoIs)) OF AreaOfInterest-Item
+```
+
+```
+AreaOfInterest-Item ::= SEQUENCE {
+ listOfTAIsinAoI ListOfTAIsinAoI OPTIONAL,
+ listOfCellsInAoI ListOfCells OPTIONAL,
+ listOfRANNodesinAoI ListOfRANNodesinAoI OPTIONAL,
+ requestReferenceID RequestReferenceID,
+ iE-Extensions ProtocolExtensionContainer { {AreaOfInterest-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+...
+}
+
+AreaOfInterest-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AreaScopeOfMDT-NR ::= CHOICE {
+ cellBased CellBasedMDT-NR,
+ tABased TABasedMDT,
+ tAIBased TAIBasedMDT,
+ ...
+ choice-extension ProtocolIE-Single-Container { {AreaScopeOfMDT-NR-ExtIEs} }
+}
+
+AreaScopeOfMDT-NR-ExtIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-PNI-NPNBasedMDT CRITICALITY ignore TYPE PNI-NPNBasedMDT PRESENCE mandatory}|
+ { ID id-SNPN-CellBasedMDT CRITICALITY ignore TYPE SNPN-CellBasedMDT PRESENCE mandatory}|
+ { ID id-SNPN-TAIBasedMDT CRITICALITY ignore TYPE SNPN-TAIBasedMDT PRESENCE mandatory}|
+ { ID id-SNPN-IDBasedMDT CRITICALITY ignore TYPE SNPN-IDBasedMDT PRESENCE mandatory},
+ ...
+}
+```
+
+}
+
+AreaScopeOfMDT-EUTRA ::= CHOICE {
+
+cellBased CellBasedMDT-EUTRA,
+
+tABased TABasedMDT,
+
+tAIBased TAIBasedMDT,
+
+...
+
+choice-extension ProtocolIE-Single-Container { {AreaScopeOfMDT-EUTRA-ExtIEs} }
+
+}
+
+AreaScopeOfMDT-EUTRA-ExtIEs XNAP-PROTOCOL-IES ::= {
+
+...
+
+}
+
+AreaScopeOfNeighCellsList ::= SEQUENCE (SIZE(1..maxnoofFreqforMDT)) OF AreaScopeOfNeighCellsItem
+
+AreaScopeOfNeighCellsItem ::= SEQUENCE {
+
+nrFrequencyInfo NRFrequencyInfo,
+
+pciListForMDT PCIListForMDT OPTIONAL,
+
+iE-Extensions ProtocolExtensionContainer { { AreaScopeOfNeighCellsItem-ExtIEs} } OPTIONAL,
+
+...
+
+}
+
+```
+AreaScopeOfNeighCellsItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+AreaScopeOfQMC ::= CHOICE {
+ cellBased CellBasedQMC,
+ tABased TABasedQMC,
+ tAIBased TAIBasedQMC,
+ pLMNAreaBased PLMNAreaBasedQMC,
+ choice-extension ProtocolIE-Single-Container { {AreaScopeOfQMC-ExtIEs} }
+}
+
+AreaScopeOfQMC-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+AS-SecurityInformation ::= SEQUENCE {
+ key-NG-RAN-Star BIT STRING (SIZE(256)),
+ ncc INTEGER (0..7),
+ iE-Extensions ProtocolExtensionContainer { {AS-SecurityInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+AS-SecurityInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+AssistanceDataForRANPaging ::= SEQUENCE {
+ ran-paging-attempt-info RANPagingAttemptInfo OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {AssistanceDataForRANPaging-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+AssistanceDataForRANPaging-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-NPNPagingAssistanceInformation CRITICALITY ignore EXTENSION NPNPagingAssistanceInformation PRESENCE optional },
+ ...
+}
+```
+
+```
+AssistanceInformationQoE-Meas ::= INTEGER (1..16, ...)
+```
+
+```
+Associated-QoSFlowInfo-List ::= SEQUENCE (SIZE(1..maxnoofMBSQoSFlows)) OF Associated-QoSFlowInfo-Item
+```
+
+```
+Associated-QoSFlowInfo-Item ::= SEQUENCE {
+ mBS-QoSFlowIdentifier QoSFlowIdentifier,
+```
+
+```
+ associatedUnicastQoSFlowIdentifier QoSFlowIdentifier,
+ iE-Extensions ProtocolExtensionContainer { { Associated-QoSFlowInfo-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+Associated-QoSFlowInfo-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+AvailableCapacity ::= INTEGER (1.. 100,...)
+```
+
+```
+AvailableRRConnectionCapacityValue ::= INTEGER (0..100)
+```
+
+```
+AvailableRVQoEMetrics ::= SEQUENCE {
+ bufferLevel ENUMERATED {true, ...} OPTIONAL,
+ playoutDelayForMediaStartup ENUMERATED {true, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {AvailableRVQoEMetrics-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+AvailableRVQoEMetrics-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+AveragingWindow ::= INTEGER (0..4095, ...)
+```
+
+```
+-- B
+```
+
+```
+BAPAddress ::= BIT STRING (SIZE(10))
+```
+
+```
+BAPPathID ::= BIT STRING (SIZE(10))
+```
+
+```
+BAPRoutingID ::= SEQUENCE {
+```
+
+```
+ bAPAddress BAPAddress,
+```
+
+```
+ bAPPathID BAPPathID,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {BAPRoutingID-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+BAPRoutingID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+
+BeamMeasurementIndicationM1 ::= ENUMERATED {true, ...}
+
+BeamMeasurementsReportConfiguration ::= SEQUENCE {
+ beamMeasurementsReportQuantity BeamMeasurementsReportQuantity OPTIONAL,
+ maxNrofRS-IndexesToReport MaxNrofRS-IndexesToReport OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { BeamMeasurementsReportConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+BeamMeasurementsReportConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+BeamMeasurementsReportQuantity ::= SEQUENCE {
+ rSRP ENUMERATED {true, ...},
+ rSRQ ENUMERATED {true, ...},
+ sINR ENUMERATED {true, ...},
+ iE-Extensions ProtocolExtensionContainer { { BeamMeasurementsReportQuantity-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+```
+
+```
+BeamMeasurementsReportQuantity-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+BHInfoIndex ::= INTEGER (1.. maxnoofBHInfo)
+```
+
+```
+BHInfoList ::= SEQUENCE (SIZE(1.. maxnoofBHInfo)) OF BHInfo-Item
+```
+
+```
+BHInfo-Item ::= SEQUENCE {
+```
+
+```
+ bBHInfoIndex BHInfoIndex,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { BHInfo-Item-ExtIEs } } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+BHInfo-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+BHRLCChannelID ::= BIT STRING (SIZE(16))
+```
+
+```
+BAPControlPDURLCH-List ::= SEQUENCE (SIZE(1.. maxnoofBAPControlPDURLCHs)) OF BAPControlPDURLCH-Item
+```
+
+```
+BAPControlPDURLCH-Item ::= SEQUENCE {
+ bHRLCCHID BHRLCChannelID,
+ nexthopBAPAddress BAPAddress,
+ iE-Extensions ProtocolExtensionContainer { { BAPControlPDURLCH-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+BAPControlPDURLCH-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+BluetoothMeasurementConfiguration ::= SEQUENCE {
+ bluetoothMeasConfig BluetoothMeasConfig,
+ bluetoothMeasConfigNameList BluetoothMeasConfigNameList OPTIONAL,
+ bt-rssi ENUMERATED {true, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { BluetoothMeasurementConfiguration-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+BluetoothMeasurementConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+BluetoothMeasConfigNameList ::= SEQUENCE (SIZE(1..maxnoofBluetoothName)) OF BluetoothName
+
+BluetoothMeasConfig ::= ENUMERATED {setup,...}
+
+BluetoothName ::= OCTET STRING (SIZE (1..248))
+
+BPLMN-ID-Info-EUTRA ::= SEQUENCE (SIZE(1..maxnoofEUTRABPLMNs)) OF BPLMN-ID-Info-EUTRA-Item
+
+BPLMN-ID-Info-EUTRA-Item ::= SEQUENCE {
+ broadcastPLMNs BroadcastEUTRAPLMNs,
+ tac TAC,
+ e-utraCI E-UTRA-Cell-Identity,
+ ranac RANAC OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {BPLMN-ID-Info-EUTRA-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+BPLMN-ID-Info-EUTRA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+BPLMN-ID-Info-NR ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF BPLMN-ID-Info-NR-Item
+
+BPLMN-ID-Info-NR-Item ::= SEQUENCE {
+ broadcastPLMNs BroadcastPLMNs,
+ tac TAC,
+ nr-CI NR-Cell-Identity,
+ ranac RANAC OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {BPLMN-ID-Info-NR-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+BPLMN-ID-Info-NR-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ConfiguredTACIndication CRITICALITY ignore EXTENSION ConfiguredTACIndication PRESENCE optional }|
+ { ID id-NPN-Broadcast-Information CRITICALITY reject EXTENSION NPN-Broadcast-Information PRESENCE optional },
+ ...
+}
+
+BitRate ::= INTEGER (0..400000000000000,...)
+```
+
+BroadcastCAG-Identifier-List ::= SEQUENCE (SIZE(1..maxnoofCAGs)) OF BroadcastCAG-Identifier-Item
+
+BroadcastCAG-Identifier-Item ::= SEQUENCE {
+ cag-Identifier CAG-Identifier,
+ iE-Extension ProtocolExtensionContainer { {BroadcastCAG-Identifier-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+BroadcastCAG-Identifier-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+BroadcastNID-List ::= SEQUENCE (SIZE(1..maxnoofNIDs)) OF BroadcastNID-Item
+
+BroadcastNID-Item ::= SEQUENCE {
+ nid NID,
+ iE-Extension ProtocolExtensionContainer { {BroadcastNID-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+BroadcastNID-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+BroadcastPLMNs ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF PLMN-Identity
+
+BroadcastEUTRAPLMNs ::= SEQUENCE (SIZE(1..maxnoofEUTRAPLMNs)) OF PLMN-Identity
+
+BroadcastPLMNinTAISupport-Item ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ tAISliceSupport-List SliceSupport-List,
+ iE-Extension ProtocolExtensionContainer { {BroadcastPLMNinTAISupport-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+BroadcastPLMNinTAISupport-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-NPN-Support CRITICALITY reject EXTENSION NPN-Support PRESENCE optional}|
+ { ID id-ExtendedTAISliceSupportList CRITICALITY reject EXTENSION ExtendedSliceSupportList PRESENCE optional}|
+ { ID id-TAINSAGSupportList CRITICALITY ignore EXTENSION TAINSAGSupportList PRESENCE optional}|
+ { ID id-TAISliceUnavailableCellList CRITICALITY ignore EXTENSION TAISliceUnavailableCellList PRESENCE optional},
+ ...
+}
+
+```
+
+BroadcastPNI-NPN-ID-Information ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF BroadcastPNI-NPN-ID-Information-Item
+
+BroadcastPNI-NPN-ID-Information-Item ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ broadcastCAG-Identifier-List BroadcastCAG-Identifier-List,
+ iE-Extension ProtocolExtensionContainer { BroadcastPNI-NPN-ID-Information-Item-ExtIEs } OPTIONAL,
+ ...
+}
+
+BroadcastPNI-NPN-ID-Information-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+BroadcastSNPNID-List ::= SEQUENCE (SIZE(1..maxnoofSNPNIDs)) OF BroadcastSNPNID
+
+BroadcastSNPNID ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ broadcastNID-List BroadcastNID-List,
+}
+
+```
+iE-Extension ProtocolExtensionContainer { {BroadcastSNPNID-ExtIEs} } OPTIONAL,
+...
+}
+
+BroadcastSNPNID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+-- C
+
+CAG-Identifier ::= BIT STRING (SIZE (32))
+
+CandidateRelayUEInfoList ::= SEQUENCE (SIZE(1..maxnoofCandidateRelayUEs)) OF CandidateRelayUEInfoItem
+
+CandidateRelayUEInfoItem ::= SEQUENCE {
+ candidateRelayUEID BIT STRING(SIZE(24)),
+ iE-Extensions ProtocolExtensionContainer { { CandidateRelayUEInfoItem-ExtIEs } } OPTIONAL,
+ ...
+}
+
+CandidateRelayUEInfoItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+CapacityValue ::= INTEGER (0..100)
+
+CapacityValueInfo ::= SEQUENCE {
+ capacityValue CapacityValue,
+ ssbAreaCapacityValueList SSBAreaCapacityValue-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {CapacityValueInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CapacityValueInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Cause ::= CHOICE {
+ radioNetwork CauseRadioNetworkLayer,
+ transport CauseTransportLayer,
+```
+
+```
+ protocol CauseProtocol,
+ misc CauseMisc,
+ choice-extension ProtocolIE-Single-Container { {Cause-ExtIEs} }
+}
+```
+
+```
+Cause-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+CauseRadioNetworkLayer ::= ENUMERATED {
+ cell-not-available,
+ handover-desirable-for-radio-reasons,
+ handover-target-not-allowed,
+ invalid-AMF-Set-ID,
+ no-radio-resources-available-in-target-cell,
+ partial-handover,
+ reduce-load-in-serving-cell,
+ resource-optimisation-handover,
+ time-critical-handover,
+ tXnRELOCoverall-expiry,
+ tXnRELOCprep-expiry,
+ unknown-GUAMI-ID,
+ unknown-local-NG-RAN-node-UE-XnAP-ID,
+```
+
+inconsistent-remote-NG-RAN-node-UE-XnAP-ID,
+encryption-and-or-integrity-protection-algorithms-not-supported,
+not-used-causes-value-1,
+multiple-PDU-session-ID-instances,
+unknown-PDU-session-ID,
+unknown-QoS-Flow-ID,
+multiple-QoS-Flow-ID-instances,
+switch-off-ongoing,
+not-supported-5QI-value,
+tXnDCoverall-expiry,
+tXnDCprep-expiry,
+action-desirable-for-radio-reasons,
+reduce-load,
+resource-optimisation,
+time-critical-action,
+target-not-allowed,
+no-radio-resources-available,
+invalid-QoS-combination,
+encryption-algorithms-not-supported,
+procedure-cancelled,
+rRM-purpose,
+improve-user-bit-rate,
+user-inactivity,
+
+radio-connection-with-UE-lost,
+failure-in-the-radio-interface-procedure,
+bearer-option-not-supported,
+up-integrity-protection-not-possible,
+up-confidentiality-protection-not-possible,
+resources-not-available-for-the-slice-s,
+ue-max-IP-data-rate-reason,
+cP-integrity-protection-failure,
+uP-integrity-protection-failure,
+slice-not-supported-by-NG-RAN,
+mN-Mobility,
+sN-Mobility,
+count-reaches-max-value,
+unknown-old-NG-RAN-node-UE-XnAP-ID,
+pDCP-Overload,
+drb-id-not-available,
+unspecified,
+...
+ue-context-id-not-known,
+non-relocation-of-context,
+cho-cpc-resources-tobechanged,
+rSN-not-available-for-the-UP,
+npn-access-denied,
+
+```
+ report-characteristics-empty,
+ existing-measurement-ID,
+ measurement-temporarily-not-available,
+ measurement-not-supported-for-the-object,
+ ue-power-saving,
+ unknown-NG-RAN-node2-Measurement-ID,
+ insufficient-ue-capabilities,
+ normal-release,
+ value-out-of-allowed-range,
+ scg-activation-deactivation-failure,
+ scg-deactivation-failure-due-to-data-transmission,
+ ssb-not-available,
+ lTM-triggered
+}
+```
+
+```
+CauseTransportLayer ::= ENUMERATED {
+ transport-resource-unavailable,
+ unspecified,
+ ...
+}
+```
+
+```
+CauseProtocol ::= ENUMERATED {
+ transfer-syntax-error,
+```
+
+```
+ abstract-syntax-error-reject,
+ abstract-syntax-error-ignore-and-notify,
+ message-not-compatible-with-receiver-state,
+ semantic-error,
+ abstract-syntax-error-falsely-constructed-message,
+ unspecified,
+ ...
+}
+
+CauseMisc ::= ENUMERATED {
+ control-processing-overload,
+ hardware-failure,
+ o-and-M-intervention,
+ not-enough-user-plane-processing-resources,
+ unspecified,
+ ...
+}
+
+CellAssistanceInfo-NR ::= CHOICE {
+ limitedNR-List SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF NR-CGI,
+ full-List ENUMERATED {all-served-cells-NR, ...},
+ choice-extension ProtocolIE-Single-Container { {CellAssistanceInfo-NR-ExtIEs} }
+}
+```
+
+```
+CellAssistanceInfo-NR-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+CellAndCapacityAssistanceInfo-NR ::= SEQUENCE {
+```
+
+```
+ maximumCellListSize MaximumCellListSize OPTIONAL,
+```
+
+```
+ cellAssistanceInfo-NR CellAssistanceInfo-NR OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { CellAndCapacityAssistanceInfo-NR-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+CellAndCapacityAssistanceInfo-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+CellAndCapacityAssistanceInfo-EUTRA ::= SEQUENCE {
+```
+
+```
+ maximumCellListSize MaximumCellListSize OPTIONAL,
+```
+
+```
+ cellAssistanceInfo-EUTRA CellAssistanceInfo-EUTRA OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { CellAndCapacityAssistanceInfo-EUTRA-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+CellAndCapacityAssistanceInfo-EUTRA-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellAssistanceInfo-EUTRA ::= CHOICE {
+ limitedEUTRA-List SEQUENCE (SIZE(1..maxnoofCellsInNG-RANnode)) OF E-UTRA-CGI,
+ full-List ENUMERATED {all-served-cells-E-UTRA, ...},
+ choice-extension ProtocolIE-Single-Container { {CellAssistanceInfo-EUTRA-ExtIEs} }
+}
+
+CellAssistanceInfo-EUTRA-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+CellBasedMDT-NR ::= SEQUENCE {
+ cellIdListforMDT-NR CellIdListforMDT-NR,
+ iE-Extensions ProtocolExtensionContainer { {CellBasedMDT-NR-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CellBasedMDT-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellIdListforMDT-NR ::= SEQUENCE (SIZE(1..maxnoofCellIDforMDT)) OF NR-CGI
+
+CellBasedQMC ::= SEQUENCE {
+ cellIdListforQMC CellIdListforQMC,
+ iE-Extensions ProtocolExtensionContainer { {CellBasedQMC-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CellBasedQMC-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellIdListforQMC ::= SEQUENCE (SIZE(1..maxnoofCellIDforQMC)) OF GlobalNG-RANCell-ID
+
+CellBasedMDT-EUTRA ::= SEQUENCE {
+ cellIdListforMDT-EUTRA CellIdListforMDT-EUTRA,
+ iE-Extensions ProtocolExtensionContainer { {CellBasedMDT-EUTRA-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+}
+
+CellBasedMDT-EUTRA-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+CellIdListforMDT-EUTRA ::= SEQUENCE (SIZE(1..maxnoofCellIDforMDT)) OF E-UTRA-CGI
+
+CellCapacityClassValue ::= INTEGER (1..100,...)
+
+CellDeploymentStatusIndicator ::= ENUMERATED {pre-change-notification, ...}
+
+CellGroupID ::= INTEGER (0..maxnoofSCellGroups)
+
+CellMeasurementResult ::= SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF CellMeasurementResult-Item
+
+CellMeasurementResult-Item ::= SEQUENCE {
+
+| | | |
+|---------------------------------|---------------------------------|-----------|
+| cell-ID | GlobalNG-RANCell-ID, | |
+| radioResourceStatus | RadioResourceStatus | OPTIONAL, |
+| tNLCapacityIndicator | TNLCapacityIndicator | OPTIONAL, |
+| compositeAvailableCapacityGroup | CompositeAvailableCapacityGroup | OPTIONAL, |
+| sliceAvailableCapacity | SliceAvailableCapacity | OPTIONAL, |
+
+```
+ numberOfActiveUEs NumberOfActiveUEs OPTIONAL,
+ rRCConnections RRCConnections OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CellMeasurementResult-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CellMeasurementResult-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-NR-U-Channel-List CRITICALITY ignore EXTENSION NR-U-Channel-List PRESENCE optional },
+ ...
+}
+```
+
+```
+CellReplacingInfo ::= SEQUENCE {
+ replacingCells ReplacingCells,
+ iE-Extensions ProtocolExtensionContainer { {CellReplacingInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CellReplacingInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+CellToReport ::= SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF CellToReport-Item
+
+CellToReport-Item ::= SEQUENCE {
+ cell-ID GlobalNG-RANCell-ID,
+ sSBToReport-List SSBToReport-List OPTIONAL,
+ sliceToReport-List SliceToReport-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CellToReport-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CellToReport-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellToReportForDataCollection-List ::= SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF CellToReportForDataCollection-Item
+
+CellToReportForDataCollection-Item ::= SEQUENCE {
+ cell-ID GlobalNG-RANCell-ID,
+ iE-Extensions ProtocolExtensionContainer { { CellToReportForDataCollection-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+CellToReportForDataCollection-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CellBasedUETrajectoryPrediction ::= SEQUENCE (SIZE(1..maxnoofCellsTrajectoryPredict)) OF PredictedUETrajectory-Item
+
+
+CellMeasurementInitiationResult-List ::= SEQUENCE (SIZE(1..maxnoofCellsInNG-RANnode)) OF CellMeasurementInitiationResult-Item
+
+CellMeasurementInitiationResult-Item ::= SEQUENCE {
+ cellID GlobalCell-ID,
+ cellMeasurementFailureCause-List CellMeasurementFailureCause-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CellMeasurementInitiationResult-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CellMeasurementInitiationResult-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+
+CellMeasurementResultForDataCollection ::= SEQUENCE (SIZE(1..maxnoofCellsInNG-RANnode)) OF CellInfoResultForDataCollection-Item
+```
+
+```
+CellInfoResultForDataCollection-Item ::= SEQUENCE {
+ cellID GlobalCell-ID,
+ predictedRadioResourceStatus RadioResourceStatus OPTIONAL,
+ predictedNumberOfActiveUEs NumberOfActiveUEs OPTIONAL,
+ predictedRRCConnections RRCConnections OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {CellInfoResultForDataCollection-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CellInfoResultForDataCollection-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Cell-Type-Choice ::= CHOICE {
+ ng-ran-e-utra E-UTRA-Cell-Identity,
+ ng-ran-nr NR-Cell-Identity,
+ e-utran E-UTRA-Cell-Identity,
+ choice-extension ProtocolIE-Single-Container { { Cell-Type-Choice-ExtIEs} }
+}
+
+Cell-Type-Choice-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+CellMeasurementFailureCause-List ::= SEQUENCE (SIZE(1..maxFailedCellMeasObjects)) OF CellMeasurementFailureCause-Item
+
+CellMeasurementFailureCause-Item ::= SEQUENCE {
+ cellmeasurementFailedReportCharacteristics BIT STRING(SIZE(128)),
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { CellMeasurementFailureCause-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CellMeasurementFailureCause-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CHOConfiguration ::= SEQUENCE {
+ choCandidateCell-List CHOCandidateCell-List,
+ iE-Extensions ProtocolExtensionContainer { { CHOConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CHOCandidateCell-List ::= SEQUENCE (SIZE(1..maxnoofCellsinCHO)) OF CHOCandidateCell-Item
+
+CHOCandidateCell-Item ::= SEQUENCE {
+ choCandidateCellID GlobalNG-RANCell-ID,
+ choExecutionCondition-List CHOExecutionCondition-List,
+ iE-Extensions ProtocolExtensionContainer { { CHOCandidateCell-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOCandidateCell-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CHOExecutionCondition-List ::= SEQUENCE (SIZE(1..maxnoofCHOexecutioncond)) OF CHOExecutionCondition-Item
+
+CHOExecutionCondition-Item ::= SEQUENCE {
+ measObjectContainer MeasObjectContainer,
+ reportConfigContainer ReportConfigContainer,
+ iE-Extensions ProtocolExtensionContainer { { CHOExecutionCondition-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+CHOExecutionCondition-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ClockQualityAcceptanceCriteria ::= SEQUENCE {
+ synchronisationState BIT STRING
+ {
+ locked(0), holdover(1), freeRun(2)
+ } (SIZE(8, ...)) OPTIONAL,
+ traceabletoUTC ENUMERATED {true, ...} OPTIONAL,
+ traceabletoGNSS ENUMERATED {true, ...} OPTIONAL,
+ clockFrequencyStability BIT STRING
+ {
+ syncE (0), pTP (1), gNSS (2), atomicClock (3), terrestrialRadio (4),
+ serialTimeCode (5), nTP (6), handset (7), other (8)
+ } (SIZE(16, ...)) OPTIONAL,
+ clockAccuracy INTEGER (1..400000000, ...) OPTIONAL,
+ parentTimeSource BIT STRING (SIZE(16)) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { ClockQualityAcceptanceCriteria-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ClockQualityAcceptanceCriteria-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+ClockQualityReportingControlInfo ::= SEQUENCE {
+```
+
+```
+ clockQualityDetailLevel ClockQualityDetailLevel,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {ClockQualityReportingControlInfo-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+ClockQualityReportingControlInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+ClockQualityDetailLevel ::= CHOICE {
+```
+
+```
+ clockQualityMetrics NULL,
+```
+
+```
+ acceptanceIndication ClockQualityAcceptanceCriteria,
+```
+
+```
+ choice-extension ProtocolIE-Single-Container { {ClockQualityDetailLevel-ExtIEs} }
+```
+
+```
+}
+```
+
+```
+ClockQualityDetailLevel-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+CapabilityForBATAdaptation ::= ENUMERATED {true, ...}
+
+CompositeAvailableCapacityGroup ::= SEQUENCE {
+ compositeAvailableCapacityDownlink CompositeAvailableCapacity,
+ compositeAvailableCapacityUplink CompositeAvailableCapacity,
+ iE-Extensions ProtocolExtensionContainer { { CompositeAvailableCapacityGroup-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CompositeAvailableCapacityGroup-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CompositeAvailableCapacitySupplementaryUplink CRITICALITY ignore EXTENSION CompositeAvailableCapacity PRESENCE optional },
+ ...
+}
+
+CompositeAvailableCapacity ::= SEQUENCE {
+ cellCapacityClassValue CellCapacityClassValue OPTIONAL,
+ capacityValueInfo CapacityValueInfo, -- this IE represents the IE "CapacityValue" in 9.2.2.a, it's used to distinguish the
+ "CapacityValue" in 9.2.2.c
+ iE-Extensions ProtocolExtensionContainer { { CompositeAvailableCapacity-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+}
+
+CompositeAvailableCapacity-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ControlPlaneTrafficType ::= INTEGER (1..3, ...)
+
+CHO-MRDC-EarlyDataForwarding ::= ENUMERATED {stop, ...}
+
+CHO-MRDC-Indicator ::= ENUMERATED {true, ..., coordination-only }
+
+CHOTrigger ::= ENUMERATED {
+ cho-initiation,
+ cho-replace,
+ ...
+}
+
+CHOinformation-Req ::= SEQUENCE {
+ cho-trigger CHOTrigger,
+```
+
+```
+
+ targetNG-RANnodeUEXnAPID NG-RANnodeUEXnAPID OPTIONAL
+
+ -- This IE shall be present if the cho-trigger IE is present and set to "CHO-replace" --,
+
+ cHO-EstimatedArrivalProbability CHO-Probability OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CHOinformation-Req-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOinformation-Req-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-CHOTimeBasedInformation CRITICALITY ignore EXTENSION CHOTimeBasedInformation PRESENCE optional}|
+ { ID id-CHO-Maxnoof-CondReconfig CRITICALITY reject EXTENSION CHO-Maxnoof-CondReconfig PRESENCE optional },
+ ...
+}
+
+CHOTimeBasedInformation ::= SEQUENCE {
+ cHO-HOWindowStart CHO-HandoverWindowStart,
+ cHO-HOWindowDuration CHO-HandoverWindowDuration,
+ iE-Extensions ProtocolExtensionContainer { {CHOTimeBasedInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOTimeBasedInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+CHOinformation-Ack ::= SEQUENCE {
+ requestedTargetCellGlobalID Target-CGI,
+ maxCHOoperations MaxCHOpreparations OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CHOinformation-Ack-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOinformation-Ack-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CHO-CPAC-Info CRITICALITY reject EXTENSION CHO-CPAC-Information PRESENCE optional },
+ ...
+}
+
+CHOinformation-AddReq ::= SEQUENCE {
+ source-M-NGRAN-node-ID GlobalNG-RANNode-ID,
+ source-M-NGRAN-node-UE-XnAP-ID NG-RANnodeUEXnAPID,
+ cHO-EstimatedArrivalProbability CHO-Probability OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CHOinformation-AddReq-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOinformation-AddReq-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+CHOinformation-AddReqAck ::= SEQUENCE {
+ pCell-ID GlobalNG-RANCell-ID OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CHOinformation-AddReqAck-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOinformation-AddReqAck-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CHOinformation-ModReq ::= SEQUENCE {
+ conditionalReconfig ENUMERATED {intra-mn-cho, ...},
+ cHO-EstimatedArrivalProbability CHO-Probability OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CHOinformation-ModReq-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHOinformation-ModReq-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+CHO-Maxnoof-CondReconfig ::= INTEGER (1..8, ...)
+
+CHO-CPAC-Information ::= SEQUENCE {
+ cCHO-CPAC-config-indicator CHO-CPAC-Config-Indicator OPTIONAL,
+ cCHO-target-SN-node-list CHO-target-SN-node-list OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {CHO-CPAC-Information-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHO-CPAC-Information-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CHO-CPAC-Config-Indicator ::= ENUMERATED {
+ cho-only-not-prepared,
+ ...
+}
+
+CHO-Probability ::= INTEGER (1..100)
+
+CHO-HandoverWindowStart ::= INTEGER (0.. 549755813887)
+
+CHO-HandoverWindowDuration ::= INTEGER (1..6000)
+
+CHO-target-SN-node-list ::= SEQUENCE (SIZE(1.. maxnoofTargetSNs)) OF CHO-target-SN-node-Item
+
+CHO-target-SN-node-Item ::= SEQUENCE {
+ target-S-NG-RANnodeID GlobalNG-RANNode-ID,
+ pduSessionResourcesAdmittedList PDUSessionResourcesAdmitted-List,
+ cho-Candidate-PSCells-list CHO-Candidate-PSCells-list,
+ iE-Extensions ProtocolExtensionContainer { {CHO-target-SN-node-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CHO-target-SN-node-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CHO-Candidate-PSCells-list ::= SEQUENCE (SIZE(1..maxnoofPSCellCandidates)) OF CHO-Candidate-PSCells-Item
+
+CHO-Candidate-PSCells-Item ::= SEQUENCE {
+ pscell-id NR-CGI,
+ target2source-NG-RANNode-Container OCTET STRING,
+
+```
+iE-Extensions ProtocolExtensionContainer { {CHO-Candidate-PSCells-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+CHO-Candidate-PSCells-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+CNsubgroupID ::= INTEGER (0..7, ...)
+
+CompleteConfig-Indicator ::= ENUMERATED {complete-config, delta-config, ...}
+
+Conditional-Reconfig-List ::= SEQUENCE (SIZE(1..maxnoofPSCellCandidates)) OF Conditional-Reconfig-Item
+
+Conditional-Reconfig-Item ::= SEQUENCE {
+ pCell-ID Target-CGI,
+ pSCell-ID NR-CGI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {Conditional-Reconfig-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Conditional-Reconfig-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+ConfiguredTACIndication ::= ENUMERATED {
+ true,
+ ...
+}
+
+Connectivity-Support ::= SEQUENCE {
+ eNDC-Support ENUMERATED {supported, not-supported, ...},
+ iE-Extensions ProtocolExtensionContainer { {Connectivity-Support-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Connectivity-Support-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ContainerAppLayerMeasConfig ::= OCTET STRING (SIZE (1..8000))
+
+COUNT-PDCP-SN12 ::= SEQUENCE {
+```
+
+```
+ pdcp-SN12 INTEGER (0..4095),
+ hfn-PDCP-SN12 INTEGER (0..1048575),
+ iE-Extensions ProtocolExtensionContainer { {COUNT-PDCP-SN12-ExtIEs} } OPTIONAL,
+ ...
+}
+
+COUNT-PDCP-SN12-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+COUNT-PDCP-SN18 ::= SEQUENCE {
+ pdcp-SN18 INTEGER (0..262143),
+ hfn-PDCP-SN18 INTEGER (0..16383),
+ iE-Extensions ProtocolExtensionContainer { {COUNT-PDCP-SN18-ExtIEs} } OPTIONAL,
+ ...
+}
+
+COUNT-PDCP-SN18-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CoverageModificationCause ::= ENUMERATED {
+```
+
+```
+coverage,
+cell-edge-capacity,
+...
+network-energy-saving}
+```
+
+```
+Coverage-Modification-List ::= SEQUENCE (SIZE (0..maxnoofCellsInNG-RANnode)) OF Coverage-Modification-List-Item
+```
+
+```
+Coverage-Modification-List-Item ::= SEQUENCE {
+ globalNG-RANCell-ID GlobalCell-ID,
+ cellCoverageState INTEGER (0..63, ...),
+ cellDeploymentStatusIndicator CellDeploymentStatusIndicator OPTIONAL,
+ cellReplacingInfo CellReplacingInfo OPTIONAL,
+ -- Included in case the Cell Deployment Status Indicator IE is present
+ sSB-Coverage-Modification-List SSB-Coverage-Modification-List,
+ iE-Extension ProtocolExtensionContainer { { Coverage-Modification-List-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+Coverage-Modification-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CoverageModificationCause CRITICALITY ignore EXTENSION CoverageModificationCause PRESENCE optional},
+ ...
+}
+```
+
+```
+CPTransportLayerInformation ::= CHOICE {
+ endpointIPAddress TransportLayerAddress,
+ choice-extension ProtocolIE-Single-Container { {CPTransportLayerInformation-ExtIEs} }
+}
+
+CPTransportLayerInformation-ExtIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-EndpointIPAddressAndPort CRITICALITY reject TYPE EndpointIPAddressAndPort PRESENCE mandatory},
+ ...
+}
+
+CPACcandidatePSCells-list ::= SEQUENCE (SIZE(1..maxnoofPSCellCandidates)) OF CPACcandidatePSCells-item
+
+CPACcandidatePSCells-item ::= SEQUENCE {
+ pscell-id NR-CGI,
+ iE-Extensions ProtocolExtensionContainer { {CPACcandidatePSCells-item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPACcandidatePSCells-item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CPACcandidatePSCells-wotherInfo-list ::= SEQUENCE (SIZE(1..maxnoofPSCellCandidates)) OF CPACcandidatePSCells-wotherInfo-item
+```
+
+```
+CPACcandidatePSCells-wotherInfo-item ::= SEQUENCE {
+ pscell-id NR-CGI,
+ s-CPAC-CompleteConfig-Indicator CompleteConfig-Indicator OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {CPACcandidatePSCells-wotherInfo-item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CPACcandidatePSCells-wotherInfo-item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+CPACConfiguration ::= SEQUENCE {
+ cpacCandidateCell-List CPACCandidateCell-List,
+ iE-Extensions ProtocolExtensionContainer { { CPACConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CPACConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+CPACCandidateCell-List ::= SEQUENCE (SIZE(1..maxnoofPSCellsinCPAC)) OF CPACCandidateCell-Item
+
+CPACCandidateCell-Item ::= SEQUENCE {
+ cpacCandidateCellID GlobalNG-RANCell-ID,
+ cpacExecutionCondition-List CPACExecutionCondition-List,
+ iE-Extensions ProtocolExtensionContainer { { CPACCandidateCell-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPACCandidateCell-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CPACExecutionCondition-List ::= SEQUENCE (SIZE(1..maxnoofCPACexecutioncond)) OF CPACExecutionCondition-Item
+
+CPACExecutionCondition-Item ::= SEQUENCE {
+ measObjectContainer MeasObjectContainer,
+ reportConfigContainer ReportConfigContainer,
+ iE-Extensions ProtocolExtensionContainer { { CPACExecutionCondition-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+CPACExecutionCondition-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+CPCindicator ::= ENUMERATED {cpc-initiation, cpc-modification, cpc-cancellation, ...}
+
+CPAInformationRequest ::= SEQUENCE {
+
+max-no-of-pscells INTEGER (1..maxnoofPSCellCandidates, ...),
+
+cpac-EstimatedArrivalProbability CHO-Probability OPTIONAL,
+
+iE-Extensions ProtocolExtensionContainer { { CPAInformationRequest-ExtIEs } } OPTIONAL,
+
+...
+
+}
+
+CPAInformationRequest-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+{ ID id-S-CPAC-Request-Info CRITICALITY reject EXTENSION S-CPAC-Request-Info PRESENCE optional } |
+
+{ ID id-S-CPAC-ReferenceConfigRequest CRITICALITY ignore EXTENSION S-CPAC-ReferenceConfig-Request PRESENCE optional },
+
+...
+
+}
+
+CPAInformationAck ::= SEQUENCE {
+
+candidate-pscells CPACcandidatePSCells-list,
+
+iE-Extensions ProtocolExtensionContainer { { CPAInformationAck-ExtIEs } } OPTIONAL,
+
+```
+...
+}
+
+CPAInformationAck-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CPACcandidatePSCells-wotherInfo-list CRITICALITY reject EXTENSION CPACcandidatePSCells-wotherInfo-list PRESENCE optional),
+ ...
+}
+
+CPCInformationRequired ::= SEQUENCE {
+ cpc-target-sn-required-list CPC-target-SN-required-list,
+ iE-Extensions ProtocolExtensionContainer { {CPCInformationRequired-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPCInformationRequired-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-S-CPAC-Request CRITICALITY reject EXTENSION S-CPAC-Request PRESENCE optional),
+ ...
+}
+
+CPC-target-SN-required-list ::= SEQUENCE (SIZE(1..maxnoofTargetSNs)) OF CPC-target-SN-required-list-Item
+
+CPC-target-SN-required-list-Item ::= SEQUENCE {
+ target-S-NG-RANnodeID GlobalNG-RANNode-ID,
+```
+
+```
+ cpc-indicator CPCindicator,
+ max-no-of-pscells INTEGER (1..maxnoofPSCellCandidates, ...),
+ cpac-EstimatedArrivalProbability CHO-Probability OPTIONAL,
+ sN-to-MN-Container OCTET STRING,
+ iE-Extensions ProtocolExtensionContainer { { CPC-target-SN-required-list-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPC-target-SN-required-list-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CPCInformationConfirm ::= SEQUENCE {
+ cpc-target-sn-confirm-list CPC-target-SN-confirm-list,
+ iE-Extensions ProtocolExtensionContainer { { CPCInformationConfirm-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPCInformationConfirm-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+CPC-target-SN-confirm-list ::= SEQUENCE (SIZE(1..maxnoofTargetSNs)) OF CPC-target-SN-confirm-list-Item
+```
+
+```
+CPC-target-SN-confirm-list-Item ::= SEQUENCE {
+ target-S-NG-RANnodeID GlobalNG-RANNode-ID,
+ candidate-pscells CPACcandidatePSCells-list,
+ iE-Extensions ProtocolExtensionContainer { { CPC-target-SN-confirm-list-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CPC-target-SN-confirm-list-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+CPAInformationModReq ::= SEQUENCE {
+ max-no-of-pscells INTEGER (1..8, ...) OPTIONAL,
+ cpac-EstimatedArrivalProbability CHO-Probability OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CPAInformationModReq-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+CPAInformationModReq-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-S-CPAC-Request-Info CRITICALITY reject EXTENSION S-CPAC-Request-Info PRESENCE optional} |
+```
+
+```
+{ ID id-S-CPAC-ReferenceConfigRequest CRITICALITY ignore EXTENSION S-CPAC-ReferenceConfig-Request PRESENCE optional}|
+{ ID id-S-CPAC-InterSN-ExecutionNotify CRITICALITY reject EXTENSION S-CPAC-InterSN-ExecutionNotify PRESENCE optional},
+...
+}
+
+CPAInformationModReqAck ::= SEQUENCE {
+ candidate-pscells CPACcandidatePSCells-list,
+ iE-Extensions ProtocolExtensionContainer { { CPAInformationModReqAck-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPAInformationModReqAck-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CPACcandidatePSCells-wotherInfo-list CRITICALITY reject EXTENSION CPACcandidatePSCells-wotherInfo-list PRESENCE optional},
+ ...
+}
+
+CPC-DataForwarding-Indicator ::= ENUMERATED {triggered, early-data-transmission-stop, ..., coordination-only}
+
+CPACInformationModRequired ::= SEQUENCE {
+ candidate-pscells CPACcandidatePSCells-list,
+ iE-Extensions ProtocolExtensionContainer { { CPACInformationModRequired-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+}
+
+CPACInformationModRequired-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+CPCInformationUpdate ::= SEQUENCE {
+
+cpc-target-sn-list CPC-target-SN-mod-list,
+
+iE-Extensions ProtocolExtensionContainer { { CPCInformationUpdate-ExtIEs} } OPTIONAL,
+
+...
+
+}
+
+CPCInformationUpdate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+CPC-target-SN-mod-list ::= SEQUENCE (SIZE(1..maxnoofTargetSNs)) OF CPC-target-SN-mod-item
+
+CPC-target-SN-mod-item ::= SEQUENCE {
+
+target-S-NG-RANnodeID GlobalNG-RANNode-ID,
+
+candidate-pscells CPCInformationUpdatePSCells-list,
+
+iE-Extensions ProtocolExtensionContainer { { CPC-target-SN-mod-item-ExtIEs} } OPTIONAL,
+
+```
+...
+}
+
+CPC-target-SN-mod-item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CPCInformationUpdatePSCells-list ::= SEQUENCE (SIZE(1..maxnoofPSCellCandidates)) OF CPCInformationUpdatePSCells-item
+
+CPCInformationUpdatePSCells-item ::= SEQUENCE {
+ pscell-id NR-CGI,
+ iE-Extensions ProtocolExtensionContainer { {CPCInformationUpdatePSCells-item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CPCInformationUpdatePSCells-item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CriticalityDiagnostics ::= SEQUENCE {
+ procedureCode ProcedureCode OPTIONAL,
+ triggeringMessage TriggeringMessage OPTIONAL,
+```
+
+```
+procedureCriticality Criticality OPTIONAL,
+iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL,
+...
+}
+
+CriticalityDiagnostics-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF
+ SEQUENCE {
+ iECriticality Criticality,
+ iE-ID ProtocolIE-ID,
+ typeOfError TypeOfError,
+ iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+CriticalityDiagnostics-IE-List-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+C-RNTI ::= BIT STRING (SIZE(16))
+
+CSI-RS-MTC-Configuration-List ::= SEQUENCE (SIZE(1.. maxnoofCSIRSconfigurations)) OF CSI-RS-MTC-Configuration-Item
+
+CSI-RS-MTC-Configuration-Item ::= SEQUENCE {
+ csi-RS-Index INTEGER(0..95),
+ csi-RS-Status ENUMERATED {activated, deactivated, ...},
+ csi-RS-Neighbour-List CSI-RS-Neighbour-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CSI-RS-MTC-Configuration-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CSI-RS-MTC-Configuration-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CSI-RS-Neighbour-List ::= SEQUENCE (SIZE(1.. maxnoofCSIRSneighbourCells)) OF CSI-RS-Neighbour-Item
+
+CSI-RS-Neighbour-Item ::= SEQUENCE {
+ nr-cgi NR-CGI,
+ csi-RS-MTC-Neighbour-List CSI-RS-MTC-Neighbour-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { CSI-RS-Neighbour-Item-ExtIEs} } OPTIONAL,
+
+```
+ ...
+}
+
+CSI-RS-Neighbour-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CSI-RS-MTC-Neighbour-List ::= SEQUENCE (SIZE(1.. maxnoofCSIRSneighbourCellsInMTC)) OF CSI-RS-MTC-Neighbour-Item
+
+CSI-RS-MTC-Neighbour-Item ::= SEQUENCE {
+ csi-RS-Index INTEGER(0..95),
+ iE-Extensions ProtocolExtensionContainer { { CSI-RS-MTC-Neighbour-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CSI-RS-MTC-Neighbour-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+CyclicPrefix-E-UTRA-DL ::= ENUMERATED {
+ normal,
+ extended,
+ ...
+}
+
+CyclicPrefix-E-UTRA-UL ::= ENUMERATED {
+ normal,
+ extended,
+ ...
+}
+
+CSI-RSTransmissionIndication ::= ENUMERATED {
+ activated,
+ deactivated,
+ ...
+}
+
+CAGListforMDT ::= SEQUENCE {
+ plmnID PLMN-Identity,
+ cAGID CAG-Identifier,
+ iE-Extensions ProtocolExtensionContainer { (CAGListforMDT-ExtIEs) } OPTIONAL,
+```
+
+```
+
+ ...
+ }
+
+```
+
+```
+
+CAGListforMDT-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- D
+
+```
+
+```
+
+XnUAddressInfoperPDUSession-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF XnUAddressInfoperPDUSession-Item
+
+```
+
+```
+
+XnUAddressInfoperPDUSession-Item ::= SEQUENCE {
+ pduSession-ID PDUSession-ID,
+ dataForwardingInfoFromTargetNGRANnode DataForwardingInfoFromTargetNGRANnode OPTIONAL,
+ pduSessionResourceSetupCompleteInfo-SNterm PDUSessionResourceBearerSetupCompleteInfo-SNterminated OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { { XnUAddressInfoperPDUSession-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+XnUAddressInfoperPDUSession-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-SecondarydataForwardingInfoFromTarget-List CRITICALITY ignore EXTENSION SecondarydataForwardingInfoFromTarget-List PRESENCE optional } |
+
+```
+
+```
+{ ID id-DRB-IDs-takenintouse CRITICALITY reject EXTENSION DRB-List PRESENCE optional}|
+{ ID id-dataForwardingInfoFromTargetE-UTRANnode CRITICALITY ignore EXTENSION DataForwardingInfoFromTargetE-UTRANnode PRESENCE optional},
+...
+}
+```
+
+```
+DataForwardingInfoFromTargetE-UTRANnode ::= SEQUENCE {
+ dataForwardingInfoFromTargetE-UTRANnode-List DataForwardingInfoFromTargetE-UTRANnode-List,
+ iE-Extension ProtocolExtensionContainer { { DataForwardingInfoFromTargetE-UTRANnode-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DataForwardingInfoFromTargetE-UTRANnode-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+DataForwardingInfoFromTargetE-UTRANnode-List ::= SEQUENCE (SIZE(1.. maxnoofDataForwardingTunneltoE-UTRAN)) OF DataForwardingInfoFromTargetE-UTRANnode-Item
+```
+
+```
+DataForwardingInfoFromTargetE-UTRANnode-Item ::= SEQUENCE {
+ dlForwardingUPTNLInformation UPTransportLayerInformation,
+ qosFlowsToBeForwarded-List QoSFlowsToBeForwarded-List,
+ iE-Extension ProtocolExtensionContainer { { DataForwardingInfoFromTargetE-UTRANnode-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DataForwardingInfoFromTargetE-UTRANnode-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+QoSFlowsToBeForwarded-List ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsToBeForwarded-Item
+QoSFlowsToBeForwarded-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ iE-Extension ProtocolExtensionContainer { { QoSFlowsToBeForwarded-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoSFlowsToBeForwarded-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DataForwardingInfoFromTargetNGRANnode ::= SEQUENCE {
+ qosFlowsAcceptedForDataForwarding-List QoSFlowsAcceptedToBeForwarded-List,
+ pduSessionLevelDLDataForwardingInfo UPTransportLayerInformation OPTIONAL,
+ pduSessionLevelULDataForwardingInfo UPTransportLayerInformation OPTIONAL,
+ dataForwardingResponseDRBItemList DataForwardingResponseDRBItemList OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {DataForwardingInfoFromTargetNGRANnode-ExtIEs} } OPTIONAL,
+```
+
+```
+...
+}
+
+DataForwardingInfoFromTargetNGRANnode-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DirectForwardingPathAvailability CRITICALITY ignore EXTENSION DirectForwardingPathAvailability PRESENCE optional },
+ ...
+}
+
+QoSFlowsAcceptedToBeForwarded-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoSFlowsAcceptedToBeForwarded-Item
+
+QoSFlowsAcceptedToBeForwarded-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ iE-Extension ProtocolExtensionContainer { {QoSFlowsAcceptedToBeForwarded-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoSFlowsAcceptedToBeForwarded-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DataforwardingandOffloadingInfofromSource ::= SEQUENCE {
+```
+
+```
+
+ qosFlowsToBeForwarded QoSFlowsToBeForwarded-List,
+ sourceDRBToQoSFlowMapping DRBToQoSFlowMapping-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {DataforwardingandOffloadingInfoproSource-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+DataforwardingandOffloadingInfoproSource-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+QoSFlowsToBeForwarded-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF QoSFlowsToBeForwarded-Item
+
+```
+
+```
+
+QoSFlowsToBeForwarded-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ dl-dataforwarding DLForwarding,
+ ul-dataforwarding ULForwarding,
+ iE-Extension ProtocolExtensionContainer { {QoSFlowsToBeForwarded-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+QoSFlowsToBeForwarded-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ULForwardingProposal CRITICALITY ignore EXTENSION ULForwardingProposal PRESENCE optional }|
+ { ID id-SourceDLForwardingIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional}|
+}
+
+```
+
+```
+{ ID id-SourceNodeDLForwardingIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional},
+ ...
+}
+```
+
+```
+DataForwardingResponseDRBItemList ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DataForwardingResponseDRBItem
+```
+
+```
+DataForwardingResponseDRBItem ::= SEQUENCE {
+ drb-ID DRB-ID,
+ dlForwardingUPTNL UPTransportLayerInformation OPTIONAL,
+ ulForwardingUPTNL UPTransportLayerInformation OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {DataForwardingResponseDRBItem-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DataForwardingResponseDRBItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+DataTrafficResources ::= BIT STRING (SIZE(6..17600))
+```
+
+```
+DataTrafficResourceIndication ::= SEQUENCE {
+ activationSFN ActivationSFN,
+ sharedResourceType SharedResourceType,
+ reservedSubframePattern ReservedSubframePattern OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {DataTrafficResourceIndication-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DataTrafficResourceIndication-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+DAPSRequestInfo ::= SEQUENCE {
+ dapsIndicator ENUMERATED {daps-HO-required, ...},
+ iE-Extensions ProtocolExtensionContainer { {DAPSRequestInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DAPSRequestInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+DAPSResponseInfo-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DAPSResponseInfo-Item
+
+DAPSResponseInfo-Item ::= SEQUENCE {
+ drbID DRB-ID,
+ dapsResponseIndicator ENUMERATED {daps-HO-accepted, daps-HO-not-accepted, ...},
+ iE-Extensions ProtocolExtensionContainer { {DAPSResponseInfo-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DAPSResponseInfo-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DeliveryStatus ::= INTEGER (0..4095, ...)
+
+DesiredActNotificationLevel ::= ENUMERATED {none, qos-flow, pdu-session, ue-level, ...}
+
+DefaultDRB-Allowed ::= ENUMERATED {true, false, ...}
+
+DirectForwardingPathAvailability ::= ENUMERATED {direct-path-available, ...}
+
+DirectForwardingPathAvailabilityWithSourceMN ::= ENUMERATED {direct-path-available, ...}
+
+DLCountChoice ::= CHOICE {
+ count12bits COUNT-PDCP-SN12,
+ count18bits COUNT-PDCP-SN18,
+ choice-extension ProtocolIE-Single-Container { DLCountChoice-ExtIEs }
+}
+
+DLCountChoice-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+DLForwarding ::= ENUMERATED {dl-forwarding-proposed, ...}
+
+DL-GBR-PRB-usage ::= INTEGER (0..100)
+
+DL-GBR-PRB-usage-for-MIMO ::= INTEGER (0..100)
+
+DL-non-GBR-PRB-usage ::= INTEGER (0..100)
+
+DL-non-GBR-PRB-usage-for-MIMO ::= INTEGER (0..100)
+
+DLF1Terminating-BHInfo ::= SEQUENCE {
+ egressBAPRoutingID BAPRoutingID,
+ egressBHRLCCHID BHRLCChannelID,
+ iE-Extensions ProtocolExtensionContainer { { DLF1Terminating-BHInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DLF1Terminating-BHInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DLLBTFailureInformationRequest ::= ENUMERATED {inquiry, ...}
+
+DLLBTFailureInformationList ::= SEQUENCE (SIZE(1.. maxnoofLBTFailureInformation)) OF DLLBTFailureInformationList-Item
+
+DLLBTFailureInformationList-Item ::= SEQUENCE {
+ uEAAssistantIdentifier NG-RANnodeUEXnAPID,
+ numberOfDLLBTFailures INTEGER (1..1000,...) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { DLLBTFailureInformationList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+DLBTFailureInformationList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+DLNonFlTerminating-BHInfo ::= SEQUENCE {
+```
+
+```
+ ingressBAPRoutingID BAPRoutingID,
+```
+
+```
+ ingressBHRLCCHID BHRLCChannelID,
+```
+
+```
+ priorhopBAPAddress BAPAddress,
+```
+
+```
+ iabqosMappingInformation IAB-QoS-Mapping-Information,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { DLNonFlTerminating-BHInfo-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+DLNonFlTerminating-BHInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+DL-Total-PRB-usage ::= INTEGER (0..100)
+```
+
+```
+DL-Total-PRB-usage-for-MIMO ::= INTEGER (0..100)
+```
+
+DRB-ID ::= INTEGER (1..32, ...)
+
+DRB-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRB-ID
+
+DRB-List-withCause ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRB-List-withCause-Item
+
+DRB-List-withCause-Item ::= SEQUENCE {
+ drb-id DRB-ID,
+ cause Cause,
+ rLC-Mode RLCMode OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {DRB-List-withCause-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DRB-List-withCause-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DRB-Number ::= INTEGER (1..32, ...)
+
+DRBsSubjectToDLDiscarding-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRBsSubjectToDLDiscarding-Item
+
+DRBsSubjectToDLDiscarding-Item ::= SEQUENCE {
+ drbID DRB-ID,
+ dlCount DLCountChoice,
+ iE-Extension ProtocolExtensionContainer { { DRBsSubjectToDLDiscarding-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DRBsSubjectToDLDiscarding-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DRBsSubjectToEarlyStatusTransfer-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRBsSubjectToEarlyStatusTransfer-Item
+
+DRBsSubjectToEarlyStatusTransfer-Item ::= SEQUENCE {
+ drbID DRB-ID,
+ dlCount DLCountChoice,
+ iE-Extension ProtocolExtensionContainer { { DRBsSubjectToEarlyStatusTransfer-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+}
+
+DRBsSubjectToEarlyStatusTransfer-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+DRBsSubjectToStatusTransfer-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRBsSubjectToStatusTransfer-Item
+
+DRBsSubjectToStatusTransfer-Item ::= SEQUENCE {
+
+drbID DRB-ID,
+
+pdcpStatusTransfer-UL DRBBStatusTransferChoice,
+
+pdcpStatusTransfer-DL DRBBStatusTransferChoice,
+
+iE-Extension ProtocolExtensionContainer { DRBsSubjectToStatusTransfer-Item-ExtIEs } OPTIONAL,
+
+...
+
+}
+
+DRBsSubjectToStatusTransfer-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+{ ID id-OldQoSFlowMap-ULendmarkerexpected CRITICALITY reject EXTENSION QoSFlows-List PRESENCE optional },
+
+...
+
+}
+
+```
+DRBBStatusTransferChoice ::= CHOICE {
+ pdcp-sn-12bits DRBBStatusTransfer12bitsSN,
+ pdcp-sn-18bits DRBBStatusTransfer18bitsSN,
+ choice-extension ProtocolIE-Single-Container { {DRBBStatusTransferChoice-ExtIEs} }
+}
+
+DRBBStatusTransferChoice-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+DRBBStatusTransfer12bitsSN ::= SEQUENCE {
+ receiveStatusofPDCPSDU BIT STRING (SIZE(1..2048)) OPTIONAL,
+ cOUNTValue COUNT-PDCP-SN12,
+ iE-Extension ProtocolExtensionContainer { {DRBBStatusTransfer12bitsSN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DRBBStatusTransfer12bitsSN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+DRBBStatusTransfer18bitsSN ::= SEQUENCE {
+ receiveStatusofPDCPSDU BIT STRING (SIZE(1..131072)) OPTIONAL,
+ cOUNTValue COUNT-PDCP-SN18,
+ iE-Extension ProtocolExtensionContainer { {DRBBStatusTransfer18bitsSN-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DRBBStatusTransfer18bitsSN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+DRBToQoSFlowMapping-List ::= SEQUENCE (SIZE (1..maxnoofDRBs)) OF DRBToQoSFlowMapping-Item
+```
+
+```
+DRBToQoSFlowMapping-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ qosFlows-List QoSFlows-List,
+ rLC-Mode RLCMode OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {DRBToQoSFlowMapping-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DRBToQoSFlowMapping-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+{ ID id-DAPSRequestInfo CRITICALITY ignore EXTENSION DAPSRequestInfo PRESENCE optional },
+...
+}
+```
+
+```
+DUF-Slot-Config-List ::= SEQUENCE (SIZE(1..maxnoofDUFSlots)) OF DUF-Slot-Config-Item
+```
+
+```
+DUF-Slot-Config-Item ::= CHOICE {
+ explicitFormat ExplicitFormat,
+ implicitFormat ImplicitFormat,
+ choice-extension ProtocolIE-Single-Container { { DUF-Slot-Config-Item-ExtIEs} }
+}
+```
+
+```
+DUF-Slot-Config-Item-ExtIEs XNAP-PROTOCOL-IES ::= {
+...
+}
+```
+
+```
+DUFSlotformatIndex ::= INTEGER(0..254)
+```
+
+```
+DUFTransmissionPeriodicity ::= ENUMERATED { ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ... }
+```
+
+DU-RX-MT-RX ::= ENUMERATED {supported, not-supported, supported-FDM-required, ...}
+
+DU-TX-MT-TX ::= ENUMERATED {supported, not-supported, supported-FDM-required, ...}
+
+DU-RX-MT-TX ::= ENUMERATED {supported, not-supported, supported-FDM-required, ...}
+
+DU-TX-MT-RX ::= ENUMERATED {supported, not-supported, supported-FDM-required, ...}
+
+DuplicationActivation ::= ENUMERATED {active, inactive, ...}
+
+Dynamic5QIDescriptor ::= SEQUENCE {
+ priorityLevelQoS PriorityLevelQoS,
+ packetDelayBudget PacketDelayBudget,
+ packetErrorRate PacketErrorRate,
+ fiveQI FiveQI OPTIONAL,
+ delayCritical ENUMERATED {delay-critical, non-delay-critical, ...} OPTIONAL,
+ -- This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE.
+ averagingWindow AveragingWindow OPTIONAL,
+ -- This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE.
+
+```
+ maximumDataBurstVolume MaximumDataBurstVolume OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {Dynamic5QIDescriptor-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Dynamic5QIDescriptor-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ExtendedPacketDelayBudget CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional}|
+ { ID id-CNPacketDelayBudgetDownlink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional}|
+ { ID id-CNPacketDelayBudgetUplink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional},
+ ...
+}
+
+-- E
+
+EarlyMeasurement ::= ENUMERATED {true, ...}
+
+ECNMarkingorCongestionInformationReportingRequest ::= CHOICE {
+ eCNMarkingAtRANRequest ECNMarkingAtRANRequest,
+ eCNMarkingAtUPFRequest ECNMarkingAtUPFRequest,
+ congestionInformationRequest CongestionInformationRequest,
+ choice-Extensions ProtocolIE-Single-Container { {ECNMarkingorCongestionInformationReportingRequest-ExtIEs} }
+}
+```
+
+```
+ECNMarkingorCongestionInformationReportingRequest-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+ECNMarkingAtRANRequest ::= ENUMERATED {ul, dl, both, stop,...}
+```
+
+```
+ECNMarkingAtUPFRequest ::= ENUMERATED {ul, dl, both, stop,...}
+```
+
+```
+CongestionInformationRequest ::= ENUMERATED {ul, dl, both, stop, ...}
+```
+
+```
+EnergyCost ::= INTEGER (0..10000, ...)
+```
+
+```
+EquivalentSNPNs ::= SEQUENCE (SIZE(1..maxnoofESPNs)) OF SNPNIdentity
+```
+
+```
+E-RAB-ID ::= INTEGER (0..15, ...)
+```
+
+E-UTRAARFCN ::= INTEGER (0..maxEARFCN)
+
+E-UTRA-Cell-Identity ::= BIT STRING (SIZE(28))
+
+ERedcap-Bcast-Information ::= BIT STRING(SIZE(8))
+
+E-UTRA-CGI ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ e-utra-CI E-UTRA-Cell-Identity,
+ iE-Extension ProtocolExtensionContainer { {E-UTRA-CGI-ExtIEs} } OPTIONAL,
+ ...
+}
+
+E-UTRA-CGI-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+E-UTRAFrequencyBandIndicator ::= INTEGER (1..256, ...)
+
+E-UTRAMultibandInfoList ::= SEQUENCE (SIZE(1..maxnoofEUTRABands)) OF E-UTRAFrequencyBandIndicator
+
+```
+EUTRAPagingeDRXInformation ::= SEQUENCE {
+ eutrapaging-eDRX-Cycle EUTRAPaging-eDRX-Cycle,
+ eutrapaging-Time-Window EUTRAPaging-Time-Window OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {EUTRAPagingeDRXInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+EUTRAPagingeDRXInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+EUTRAPaging-eDRX-Cycle ::= ENUMERATED {
+ hfhalf, hf1, hf2, hf4, hf6,
+ hf8, hf10, hf12, hf14, hf16,
+ hf32, hf64, hf128, hf256,
+ ...
+}
+```
+
+```
+EUTRAPaging-Time-Window ::= ENUMERATED {
+ s1, s2, s3, s4, s5,
+```
+
+```
+ s6, s7, s8, s9, s10,
+ s11, s12, s13, s14, s15, s16,
+ ...
+}
+```
+
+```
+E-UTRAPCI ::= INTEGER (0..503, ...)
+```
+
+```
+E-UTRAPRACHConfiguration ::= SEQUENCE {
+```
+
+```
+ rootSequenceIndex INTEGER (0..837),
+ zeroCorrelationIndex INTEGER (0..15),
+ highSpeedFlag ENUMERATED {true, false, ...},
+ prach-FreqOffset INTEGER (0..94),
+ prach-ConfigIndex INTEGER (0..63) OPTIONAL,
+```
+
+```
+-- C-iftDD: This IE shall be present if the EUTRA-Mode-Info IE in the Served Cell Information IE is set to the value "TDD" --
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {E-UTRAPRACHConfiguration-ExtIEs} } OPTIONAL,
+ ...
+```
+
+```
+}
+```
+
+```
+E-UTRAPRACHConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+E-UTRATransmissionBandwidth ::= ENUMERATED {bw6, bw15, bw25, bw50, bw75, bw100, ..., bw1}
+
+EndpointIPAddressAndPort ::=SEQUENCE {
+ endpointIPAddress TransportLayerAddress,
+ portNumber PortNumber,
+ iE-Extensions ProtocolExtensionContainer { { EndpointIPAddressAndPort-ExtIEs} } OPTIONAL
+}
+
+EndpointIPAddressAndPort-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+EventTriggered ::= SEQUENCE {
+ loggedEventTriggeredConfig LoggedEventTriggeredConfig,
+ iE-Extensions ProtocolExtensionContainer { { EventTriggered-ExtIEs} } OPTIONAL,
+ ...
+}
+
+EventTriggered-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+EventType ::= ENUMERATED {
+ report-upon-change-of-serving-cell,
+ report-UE-moving-presence-into-or-out-of-the-Area-of-Interest,
+ ...,
+ report-upon-change-of-serving-cell-and-Area-of-Interest
+}
+
+EventTypeTrigger ::= CHOICE {
+ outOfCoverage ENUMERATED {true, ...},
+ eventL1 EventL1,
+ choice-Extensions ProtocolIE-Single-Container { {EventTypeTrigger-ExtIEs} }
+}
+
+EventTypeTrigger-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+EventL1 ::= SEQUENCE {
+ l1Threshold MeasurementThresholdL1LoggedMDT,
+ hysteresis Hysteresis,
+ timeToTrigger TimeToTrigger,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { { EventL1-ExtIEs} } OPTIONAL,
+...
+}
+
+EventL1-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+MeasurementThresholdL1LoggedMDT ::= CHOICE {
+ threshold-RSRP Threshold-RSRP,
+ threshold-RSRQ Threshold-RSRQ,
+ ...
+ choice-extension ProtocolIE-Single-Container { {MeasurementThresholdL1LoggedMDT-ExtIEs} }
+}
+
+MeasurementThresholdL1LoggedMDT-ExtIEs XNAP-PROTOCOL-IES ::= {
+...
+}
+
+ExcessPacketDelayThresholdConfiguration ::= SEQUENCE (SIZE(1..maxnoofThresholdsForExcessPacketDelay)) OF ExcessPacketDelayThresholdItem
+
+ExcessPacketDelayThresholdItem ::= SEQUENCE {
+ fiveQI FiveQI,
+```
+
+```
+ excessPacketDelayThresholdValue ExcessPacketDelayThresholdValue,
+
+ iE-Extensions ProtocolExtensionContainer { { ExcessPacketDelayThresholdItem-ExtIEs } } OPTIONAL,
+
+ ...
+
+}
+
+ExcessPacketDelayThresholdItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+
+}
+
+ExcessPacketDelayThresholdValue ::= ENUMERATED {
+
+ ms0dot25, ms0dot5, ms1, ms2, ms4, ms5, ms10, ms20, ms30, ms40, ms50, ms60, ms70, ms80, ms90, ms100, ms150, ms300, ms500,
+
+ ...
+
+}
+
+ExpectedActivityPeriod ::= INTEGER (1..30|40|50|60|80|100|120|150|180|181, ...)
+
+ExpectedHOInterval ::= ENUMERATED {
+
+ sec15, sec30, sec60, sec90, sec120, sec180, long-time,
+
+ ...
+
+}
+
+ExpectedIdlePeriod ::= INTEGER (1..30|40|50|60|80|100|120|150|180|181, ...)
+```
+
+```
+ExpectedUEActivityBehaviour ::= SEQUENCE {
+ expectedActivityPeriod ExpectedActivityPeriod OPTIONAL,
+ expectedIdlePeriod ExpectedIdlePeriod OPTIONAL,
+ sourceOfUEActivityBehaviourInformation SourceOfUEActivityBehaviourInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ExpectedUEActivityBehaviour-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ExpectedUEActivityBehaviour-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ExpectedUEBehaviour ::= SEQUENCE {
+ expectedUEActivityBehaviour ExpectedUEActivityBehaviour OPTIONAL,
+ expectedHOInterval ExpectedHOInterval OPTIONAL,
+ expectedUEMobility ExpectedUEMobility OPTIONAL,
+ expectedUEMovingTrajectory ExpectedUEMovingTrajectory OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ExpectedUEBehaviour-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ExpectedUEBehaviour-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+
+ExpectedUEMobility ::= ENUMERATED {
+ stationary,
+ mobile,
+ ...
+}
+
+ExpectedUEMovingTrajectory ::= SEQUENCE (SIZE(1..maxnoofCellsUEMovingTrajectory)) OF ExpectedUEMovingTrajectoryItem
+
+ExpectedUEMovingTrajectoryItem ::= SEQUENCE {
+ nGRAN-CGI GlobalNG-RANCell-ID,
+ timeStayedInCell INTEGER (0..4095) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ExpectedUEMovingTrajectoryItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ExpectedUEMovingTrajectoryItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SourceOfUEActivityBehaviourInformation ::= ENUMERATED {
+ subscription-information,
+```
+
+```
+ statistics,
+ ...
+}
+
+ExplicitFormat ::= SEQUENCE {
+ permutation Permutation,
+ noofDownlinkSymbols INTEGER(0..14) OPTIONAL,
+ noofUplinkSymbols INTEGER(0..14) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { ExplicitFormat-ExtIEs } } OPTIONAL,
+ ...
+}
+
+ExplicitFormat-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ExtendedRATRestrictionInformation ::= SEQUENCE {
+ primaryRATRestriction BIT STRING (SIZE(8, ...)),
+ secondaryRATRestriction BIT STRING (SIZE(8, ...)),
+ iE-Extensions ProtocolExtensionContainer { { ExtendedRATRestrictionInformation-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+ExtendedRATRestrictionInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ExtendedPacketDelayBudget ::= INTEGER (0..65535, ..., 65536..109999)
+```
+
+```
+ExtendedSliceSupportList ::= SEQUENCE (SIZE(1..maxnoofExtSliceItems)) OF S-NSSAI
+```
+
+```
+ExtendedUEIdentityIndexValue ::= BIT STRING (SIZE(16))
+```
+
+```
+ExtTLAs ::= SEQUENCE (SIZE(1..maxnoofExtTLAs)) OF ExtTLA-Item
+```
+
+```
+ExtTLA-Item ::= SEQUENCE {
+ iPsecTLA TransportLayerAddress OPTIONAL,
+ gTPTransportLayerAddresses GTPTLAs OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ExtTLA-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ExtTLA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+```
+
+```
+GTPTLAs ::= SEQUENCE (SIZE(1.. maxnoofGTPTLAs)) OF GTPTLA-Item
+```
+
+```
+GTPTLA-Item ::= SEQUENCE {
+ gTPTransportLayerAddresses TransportLayerAddress,
+ iE-Extensions ProtocolExtensionContainer { { GTPTLA-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+GTPTLA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+-- F
+```
+
+```
+F1CTrafficContainer ::= OCTET STRING
+```
+
+```
+F1-terminatingIAB-donorIndicator ::= ENUMERATED {true, ...}
+```
+
+```
+F1-TerminatingTopologyBHInformation ::= SEQUENCE {
+```
+
+```
+ flTerminatingBHInformation-List flTerminatingBHInformation-List,
+ iE-Extensions ProtocolExtensionContainer { {Fl-TerminatingTopologyBHInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Fl-TerminatingTopologyBHInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+FlTerminatingBHInformation-List ::= SEQUENCE (SIZE(1..maxnoofBHInfo)) OF FlTerminatingBHInformation-Item
+
+FlTerminatingBHInformation-Item ::= SEQUENCE {
+ bHInfoIndex BHInfoIndex,
+ dLTNLAddress IABTNLAddress,
+ dlFlTerminatingBHInfo DLFlTerminating-BHInfo OPTIONAL,
+ ulFlTerminatingBHInfo ULFlTerminating-BHInfo OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { { FlTerminatingBHInformation-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+FlTerminatingBHInformation-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+FiveGCMobilityRestrictionListContainer ::= OCTET STRING
+
+-- This octets of the OCTET STRING contain the Mobility Restriction List IE as specified in TS 38.413 [5]. --
+
+FiveGProSeAuthorized ::= SEQUENCE {
+
+| | | |
+|------------------------------------|--------------------------------------------------------------|-----------|
+| fiveGProSeDirectDiscovery | FiveGProSeDirectDiscovery | OPTIONAL, |
+| fiveGProSeDirectCommunication | FiveGProSeDirectCommunication | OPTIONAL, |
+| fiveGnrProSeLayer2UEtoNetworkRelay | FiveGProSeLayer2UEtoNetworkRelay | OPTIONAL, |
+| fiveGnrProSeLayer3UEtoNetworkRelay | FiveGProSeLayer3UEtoNetworkRelay | OPTIONAL, |
+| fiveGnrProSeLayer2RemoteUE | FiveGProSeLayer2RemoteUE | OPTIONAL, |
+| iE-Extensions | ProtocolExtensionContainer { {FiveGProSeAuthorized-ExtIEs} } | OPTIONAL, |
+| ... | | |
+
+}
+
+FiveGProSeAuthorized-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+| | | | |
+|--------------------------------------|--------------------|----------------------------------------|---------------------|
+| { ID id-FiveGProSeLayer2Multipath | CRITICALITY ignore | EXTENSION FiveGProSeLayer2Multipath | PRESENCE optional} |
+| { ID id-FiveGProSeLayer2UEtoUERelay | CRITICALITY ignore | EXTENSION FiveGProSeLayer2UEtoUERelay | PRESENCE optional} |
+| { ID id-FiveGProSeLayer2UEtoUERemote | CRITICALITY ignore | EXTENSION FiveGProSeLayer2UEtoUERemote | PRESENCE optional}, |
+| ... | | | |
+
+}
+
+FiveGProSeDirectDiscovery ::= ENUMERATED {
+
+```
+ authorized,
+ not-authorized,
+ ...
+}
+
+FiveGProSeDirectCommunication ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+FiveGProSeLayer2UEtoNetworkRelay ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+FiveGProSeLayer3UEtoNetworkRelay ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+```
+
+```
+FiveGProSeLayer2RemoteUE ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+FiveGProSeLayer2Multipart ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+FiveGProSeLayer2UEtoUERelay ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+FiveGProSeLayer2UEtoUERemote ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+```
+
+```
+FiveGProSePC5QoSParameters ::= SEQUENCE {
+ fiveGProSePC5QoSFlowList FiveGProSePC5QoSFlowList,
+ fiveGProSePC5LinkAggregateBitRates BitRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { FiveGProSePC5QoSParameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+FiveGProSePC5QoSParameters-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+FiveGProSePC5QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofPC5QoSFlows)) OF FiveGProSePC5QoSFlowItem
+
+FiveGProSePC5QoSFlowItem ::= SEQUENCE {
+ fiveGProSePCQI FiveQI,
+ fiveGProSePC5FlowBitRates FiveGProSePC5FlowBitRates OPTIONAL,
+ fiveGProSeRange Range OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { FiveGProSePC5QoSFlowItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+FiveGProSePC5QoSFlowItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+FiveGProSePC5FlowBitRates ::= SEQUENCE {
+ fiveGProSeGuaranteedFlowBitRate BitRate,
+ fiveGProSeMaximumFlowBitRate BitRate,
+ iE-Extensions ProtocolExtensionContainer { { FiveGProSePC5FlowBitRates-ExtIEs} } OPTIONAL,
+ ...
+}
+
+FiveGProSePC5FlowBitRates-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+FiveQI ::= INTEGER (0..255, ...)
+
+Flows-Mapped-To-DRB-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF Flows-Mapped-To-DRB-Item
+
+Flows-Mapped-To-DRB-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ qosFlowLevelQoSParameters QoSFlowLevelQoSParameters,
+ qosFlowMappingIndication QoSFlowMappingIndication OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { Flows-Mapped-To-DRB-Item-ExtIEs} } OPTIONAL
+```
+
+```
+}
+
+Flows-Mapped-To-DRB-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+FreqDomainHSNAconfiguration-List ::= SEQUENCE (SIZE(1.. maxnoofHSNASlots)) OF FreqDomainHSNAconfiguration-List-Item
+
+FreqDomainHSNAconfiguration-List-Item ::= SEQUENCE {
+ rBsetIndex INTEGER(0.. maxnoofRBsetsPerCell, ...),
+ freqDomainSlotHSNAconfiguration-List FreqDomainSlotHSNAconfiguration-List,
+ iE-Extensions ProtocolExtensionContainer { { FreqDomainHSNAconfiguration-List-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+FreqDomainHSNAconfiguration-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+FreqDomainSlotHSNAconfiguration-List ::= SEQUENCE (SIZE(1.. maxnoofHSNASlots)) OF FreqDomainSlotHSNAconfiguration-List-Item
+
+FreqDomainSlotHSNAconfiguration-List-Item ::= SEQUENCE {
+```
+
+```
+ slotIndex INTEGER(1..maxnoofHSNASlots),
+ hSNADownlink HSNADownlink OPTIONAL,
+ hSNAUplink HSNAUplink OPTIONAL,
+ hSNAFlexible HSNAFlexible OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { FreqDomainSlotHSNAconfiguration-List-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+FreqDomainSlotHSNAconfiguration-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+FrequencyShift7p5khz ::= ENUMERATED {false, true, ...}
+```
+
+```
+-- G
+```
+
+```
+GBRQoSFlowInfo ::= SEQUENCE {
+ maxFlowBitRateDL BitRate,
+ maxFlowBitRateUL BitRate,
+ guaranteedFlowBitRateDL BitRate,
+ guaranteedFlowBitRateUL BitRate,
+ notificationControl ENUMERATED {notification-requested, ...} OPTIONAL,
+```
+
+```
+ maxPacketLossRateDL PacketLossRate OPTIONAL,
+ maxPacketLossRateUL PacketLossRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {GBRQoSFlowInfo-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ GBRQoSFlowInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ { ID id-AlternativeQoSParaSetList CRITICALITY ignore EXTENSION AlternativeQoSParaSetList PRESENCE optional },
+ ...
+ }
+
+ GlobalgNB-ID ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ gnb-id GNB-ID-Choice,
+ iE-Extensions ProtocolExtensionContainer { {GlobalgNB-ID-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ GlobalgNB-ID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+ }
+
+ GNB-DU-Cell-Resource-Configuration ::= SEQUENCE {
+```
+
+```
+ subcarrierSpacing SSB-subcarrierSpacing,
+ dUFTransmissionPeriodicity DUFTTransmissionPeriodicity OPTIONAL,
+ dUF-Slot-Config-List DUFSlotConfigList OPTIONAL,
+ hSNATransmissionPeriodicity HSNATransmissionPeriodicity,
+ hNSASlotConfigList HNSASlotConfigList OPTIONAL,
+ rBsetConfiguration RBsetConfiguration OPTIONAL,
+ freqDomainHSNAconfiguration-List FreqDomainHSNAconfiguration-List OPTIONAL,
+ nACellResourceConfigurationList NACellResourceConfigurationList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { GNB-DU-Cell-Resource-Configuration-ExtIEs } } OPTIONAL,
+ ...
+}
+
+GNB-DU-Cell-Resource-Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GNB-ID-Choice ::= CHOICE {
+ gnb-ID BIT STRING (SIZE(22..32)),
+ choice-extension ProtocolIE-Single-Container { {GNB-ID-Choice-ExtIEs} }
+}
+```
+
+```
+GNB-ID-Choice-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+GNB-RadioResourceStatus ::= SEQUENCE {
+```
+
+```
+ ssbAreaRadioResourceStatus-List SSBAreaRadioResourceStatus-List,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { GNB-RadioResourceStatus-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+GNB-RadioResourceStatus-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ { ID id-SliceRadioResourceStatus-List CRITICALITY ignore EXTENSION SliceRadioResourceStatus-List PRESENCE optional }|
+```
+
+```
+ { ID id-MIMO PRBusageInformation CRITICALITY ignore EXTENSION MIMO PRBusageInformation PRESENCE optional },
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+GlobalCell-ID ::= SEQUENCE {
+```
+
+```
+ plmn-id PLMN-Identity,
+```
+
+```
+ cell-type Cell-Type-Choice,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { GlobalCell-ID-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+GlobalCell-ID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+GlobalngNB-ID ::= SEQUENCE {
+```
+
+```
+ plmn-id PLMN-Identity,
+```
+
+```
+ enb-id ENB-ID-Choice,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {GlobalenB-ID-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+GlobalenB-ID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+ENB-ID-Choice ::= CHOICE {
+```
+
+```
+ enb-ID-macro BIT STRING (SIZE(20)),
+```
+
+```
+ enb-ID-shortmacro BIT STRING (SIZE(18)),
+```
+
+```
+ enb-ID-longmacro BIT STRING (SIZE(21)),
+```
+
+```
+choice-extension ProtocolIE-Single-Container { {ENB-ID-Choice-ExtIEs} }
+}
+
+ENB-ID-Choice-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+GlobalNG-RANCell-ID ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ ng-RAN-Cell-id NG-RAN-Cell-Identity,
+ iE-Extensions ProtocolExtensionContainer { {GlobalNG-RANCell-ID-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GlobalNG-RANCell-ID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+GlobalNG-RANNode-ID ::= CHOICE {
+ gNB GlobalgNB-ID,
+ ng-eNB GlobalngeNB-ID,
+```
+
+```
+ choice-extension ProtocolIE-Single-Container { {GlobalNG-RANNode-ID-ExtIEs} }
+}
+
+GlobalNG-RANNode-ID-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+GTP-TEID ::= OCTET STRING (SIZE(4))
+
+GTPtunnelTransportLayerInformation ::= SEQUENCE {
+ tnl-address TransportLayerAddress,
+ gtp-teid GTP-TEID,
+ iE-Extensions ProtocolExtensionContainer { {GTPtunnelTransportLayerInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GTPtunnelTransportLayerInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-QoS-Mapping-Information CRITICALITY reject EXTENSION QoS-Mapping-Information PRESENCE optional },
+ ...
+}
+```
+
+```
+GUAMI ::= SEQUENCE {
+ plmn-ID PLMN-Identity,
+ amf-region-id BIT STRING (SIZE (8)),
+ amf-set-id BIT STRING (SIZE (10)),
+ amf-pointer BIT STRING (SIZE (6)),
+ iE-Extensions ProtocolExtensionContainer { {GUAMI-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+GUAMI-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+-- H
+
+```
+HandoverReportType ::= ENUMERATED {
+ hoTooEarly,
+ hoToWrongCell,
+ intersystempingpong,
+ ...
+}
+```
+
+HashedUEIdentityIndexValue ::= BIT STRING (SIZE(13, ...))
+
+HSNASlotConfigList ::= SEQUENCE (SIZE(1..maxnoofHSNASlots)) OF HSNASlotConfigItem
+
+HSNASlotConfigItem ::= SEQUENCE {
+ hSNADownlink HSNADownlink OPTIONAL,
+ hSNAUplink HSNAUplink OPTIONAL,
+ hSNAFlexible HSNAFlexible OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { HSNASlotConfigItem-ExtIEs } } OPTIONAL,
+ ...
+}
+
+HSNASlotConfigItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+HSNADownlink ::= ENUMERATED { hard, soft, notavailable }
+
+hSNAFlexible ::= ENUMERATED { hard, soft, notavailable }
+
+HSNAUplink ::= ENUMERATED { hard, soft, notavailable }
+
+HSNATransmissionPeriodicity ::= ENUMERATED { ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160, ... }
+
+Hysteresis ::= INTEGER (0..30)
+
+-- I
+
+IABCellInformation ::= SEQUENCE{
+ nRCGI NR-CGI,
+ iAB-DU-Cell-Resource-Configuration-Mode-Info iAB-DU-Cell-Resource-Configuration-Mode-Info OPTIONAL,
+ iAB-STC-Info iAB-STC-Info OPTIONAL,
+ rACH-Config-Common RACH-Config-Common OPTIONAL,
+ rACH-Config-Common-IAB RACH-Config-Common-IAB OPTIONAL,
+ cSI-RS-Configuration OCTET STRING OPTIONAL,
+ sR-Configuration OCTET STRING OPTIONAL,
+ pDCCH-ConfigSIB1 OCTET STRING OPTIONAL,
+ sCS-Common OCTET STRING OPTIONAL,
+ multiplexingInfo MultiplexingInfo OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { IABCellInformation-ExtIEs } } OPTIONAL,
+ ...
+}
+
+```
+IABCellInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IAB-DU-Cell-Resource-Configuration-Mode-Info ::= CHOICE {
+ tDD IAB-DU-Cell-Resource-Configuration-TDD-Info,
+ fDD IAB-DU-Cell-Resource-Configuration-FDD-Info,
+ choice-extension ProtocolIE-Single-Container { { IAB-DU-Cell-Resource-Configuration-Mode-Info-ExtIEs} }
+}
+
+IAB-DU-Cell-Resource-Configuration-Mode-Info-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+IAB-DU-Cell-Resource-Configuration-FDD-Info ::= SEQUENCE {
+ gNB-DU-Cell-Resource-Configuration-FDD-UL GNB-DU-Cell-Resource-Configuration,
+ gNB-DU-Cell-Resource-Configuration-FDD-DL GNB-DU-Cell-Resource-Configuration,
+ uLFrequencyInfo NRFrequencyInfo OPTIONAL,
+ dLFrequencyInfo NRFrequencyInfo OPTIONAL,
+ uLTransmissionBandwidth NRTransmissionBandwidth OPTIONAL,
+```
+
+```
+ dlTransmissionBandwidth NRTransmissionBandwidth OPTIONAL,
+ uLCarrierList NRCarrierList OPTIONAL,
+ dlCarrierList NRCarrierList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {IAB-DU-Cell-Resource-Configuration-FDD-Info-ExtIEs} } OPTIONAL,
+ ...
+}
+
+IAB-DU-Cell-Resource-Configuration-FDD-Info-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IAB-DU-Cell-Resource-Configuration-TDD-Info ::= SEQUENCE {
+ gNB-DU-Cell-Resource-Configuration-TDD GNB-DU-Cell-Resource-Configuration,
+ frequencyInfo NRFrequencyInfo OPTIONAL,
+ transmissionBandwidth NRTransmissionBandwidth OPTIONAL,
+ carrierList NRCarrierList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {IAB-DU-Cell-Resource-Configuration-TDD-Info-ExtIEs} } OPTIONAL,
+ ...
+}
+
+IAB-DU-Cell-Resource-Configuration-TDD-Info-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+IAB-MT-Cell-List ::= SEQUENCE (SIZE(1..maxnooServingCells)) OF IAB-MT-Cell-List-Item
+
+IAB-MT-Cell-List-Item ::= SEQUENCE {
+ nRCellIdentity NR-Cell-Identity,
+ dU-RX-MT-RX DU-RX-MT-RX,
+ dU-TX-MT-TX DU-TX-MT-TX,
+ dU-RX-MT-TX DU-RX-MT-TX,
+ dU-TX-MT-RX DU-TX-MT-RX,
+ iE-Extensions ProtocolExtensionContainer { { IAB-MT-Cell-List-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+IAB-MT-Cell-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IABNodeIndication ::= ENUMERATED {true,...}
+
+IAB-QoS-Mapping-Information ::= SEQUENCE {
+ dscp BIT STRING (SIZE(6)) OPTIONAL,
+ flow-label BIT STRING (SIZE(20)) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { IAB-QoS-Mapping-Information-ExtIEs } } OPTIONAL,
+
+```
+...
+}
+
+IAB-QoS-Mapping-Information-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IAB-STC-Info ::= SEQUENCE{
+ iAB-STC-Info-List IAB-STC-Info-List,
+ iE-Extensions ProtocolExtensionContainer { { IAB-STC-Info-ExtIEs } } OPTIONAL,
+ ...
+}
+
+IAB-STC-Info-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IAB-STC-Info-List ::= SEQUENCE (SIZE(1..maxnoofIABSTCInfo)) OF IAB-STC-Info-Item
+
+IAB-STC-Info-Item ::= SEQUENCE {
+ sSB-freqInfo SSB-freqInfo,
+ sSB-subcarrierSpacing SSB-subcarrierSpacing,
+ sSB-transmissionPeriodicity SSB-transmissionPeriodicity,
+```
+
+```
+ sSB-transmissionTimingOffset SSB-transmissionTimingOffset,
+ sSB-transmissionBitmap SSB-transmissionBitmap,
+ iE-Extensions ProtocolExtensionContainer { { IAB-STC-Info-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+IAB-STC-Info-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IAB-TNL-Address-Request ::= SEQUENCE {
+ iABIPv4AddressesRequested IABTNLAddressesRequested,
+ iABIPv6RequestType IABIPv6RequestType,
+ iABTNLAddressToRemove-List IABTNLAddressToRemove-List,
+ iE-Extensions ProtocolExtensionContainer { { IAB-TNL-Address-Request-ExtIEs } } OPTIONAL,
+ ...
+}
+
+IAB-TNL-Address-Request-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IABIPv6RequestType ::= CHOICE {
+```
+
+```
+ iIPv6Address IABTNLAddressesRequested,
+ iIPv6Prefix IABTNLAddressesRequested,
+ choice-extension ProtocolIE-Single-Container { {IABIPv6RequestType-ExtIEs} }
+ }
+
+ IABIPv6RequestType-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+ }
+
+ IAB-TNL-Address-Response ::= SEQUENCE {
+ iABAllocatedTNLAddress-List IABAllocatedTNLAddress-List,
+ iE-Extensions ProtocolExtensionContainer { {IAB-TNL-Address-Response-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+ IAB-TNL-Address-Response-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+ }
+
+ IABAllocatedTNLAddress-List ::= SEQUENCE (SIZE(1..maxnoofTLAsIAB)) OF IABAllocatedTNLAddress-Item
+
+ IABAllocatedTNLAddress-Item ::= SEQUENCE {
+```
+
+```
+ iABTNLAddress IABTNLAddress,
+ iABTNLAddressUsage IABTNLAddressUsage OPTIONAL,
+ associatedDonorDUAddress BAPAddress OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {IABAllocatedTNLAddress-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+IABAllocatedTNLAddress-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IABTNLAddress ::= CHOICE {
+ iV4Address BIT STRING (SIZE(32)),
+ iV6Address BIT STRING (SIZE(128)),
+ iV6Prefix BIT STRING (SIZE(64)),
+ choice-extension ProtocolIE-Single-Container { {IABTNLAddress-ExtIEs} }
+}
+
+IABTNLAddress-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+IABTNLAddressesRequested ::= SEQUENCE {
+```
+
+```
+tNLAddressesOrPrefixesRequestedAllTraffic INTEGER (1..256) OPTIONAL,
+tNLAddressesOrPrefixesRequestedF1-C INTEGER (1..256) OPTIONAL,
+tNLAddressesOrPrefixesRequestedF1-U INTEGER (1..256) OPTIONAL,
+tNLAddressesOrPrefixesRequestedNoNFL INTEGER (1..256) OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {IABTNLAddressesRequested-ExtIEs} } OPTIONAL
+}
+
+IABTNLAddressesRequested-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+IABTNLAddressToRemove-List ::= SEQUENCE (SIZE(1..maxnoofTTLAsIAB)) OF IABTNLAddressToRemove-Item
+
+IABTNLAddressToRemove-Item ::= SEQUENCE {
+ iABTNLAddress IABTNLAddress,
+ iE-Extension ProtocolExtensionContainer { {IABTNLAddressToRemove-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+IABTNLAddressToRemove-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+IABTNLAddressUsage ::= ENUMERATED {
+
+fl-c,
+
+fl-u,
+
+non-fl,
+
+...,
+
+all
+
+}
+
+IABTNLAddressException ::= SEQUENCE (SIZE(1..maxnoofTTLAsIAB)) OF IABTNLAddress-Item
+
+IABTNLAddress-Item ::= SEQUENCE {
+
+iABTNLAddress
+
+IABTNLAddress,
+
+iE-Extensions
+
+ProtocolExtensionContainer { { IABTNLAddress-ItemExtIEs } } OPTIONAL,
+
+...}
+
+IABTNLAddress-ItemExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+ImmediateMDT-NR ::= SEQUENCE {
+
+```
+measurementsToActivate MeasurementsToActivate,
+m1Configuration M1Configuration OPTIONAL,
+m4Configuration M4Configuration OPTIONAL,
+m5Configuration M5Configuration OPTIONAL,
+mDT-Location-Info MDT-Location-Info OPTIONAL,
+m6Configuration M6Configuration OPTIONAL,
+m7Configuration M7Configuration OPTIONAL,
+bluetoothMeasurementConfiguration BluetoothMeasurementConfiguration OPTIONAL,
+wLANMeasurementConfiguration WLANMeasurementConfiguration OPTIONAL,
+sensorMeasurementConfiguration SensorMeasurementConfiguration OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { { ImmediateMDT-NR-ExtIEs } } OPTIONAL,
+...
+}
+
+ImmediateMDT-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+ImplicitFormat ::= SEQUENCE {
+ dUFSlotformatIndex DUFSlotformatIndex,
+ iE-Extensions ProtocolExtensionContainer { { ImplicitFormat-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+ImplicitFormat-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+InitiatingCondition-FailureIndication ::= CHOICE {
+```
+
+```
+ rRCReestab RRCReestab-initiated,
+```
+
+```
+ rRCSetup RRCSetup-initiated,
+```
+
+```
+ choice-extension ProtocolIE-Single-Container { {InitiatingCondition-FailureIndication-ExtIEs} }
+```
+
+```
+}
+```
+
+```
+InitiatingCondition-FailureIndication-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+IntendedTDD-DL-ULConfiguration-NR ::= SEQUENCE {
+```
+
+```
+ nrSCS NRSCS,
+```
+
+```
+ nrCyclicPrefix NRCyclicPrefix,
+```
+
+```
+ nrDL-ULTransmissionPeriodicity NRDL-ULTransmissionPeriodicity,
+```
+
+```
+ slotConfiguration-List SlotConfiguration-List,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {IntendedTDD-DL-ULConfiguration-NR-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+}
+
+```
+IntendedTDD-DL-ULConfiguration-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+InterfaceInstanceIndication ::= INTEGER (0..255, ...)
+```
+
+```
+I-RNTI ::= CHOICE {
+ i-RNTI-full BIT STRING (SIZE(40)),
+ i-RNTI-short BIT STRING (SIZE(24)),
+ choice-extension ProtocolIE-Single-Container { {I-RNTI-ExtIEs} }
+}
+```
+
+```
+I-RNTI-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+IABAuthorizationStatus ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+```
+
+}
+
+-- J
+
+-- K
+
+-- L
+
+```
+Local-NG-RAN-Node-Identifier ::= CHOICE {
+ full-I-RNTI-Profile-List Full-I-RNTI-Profile-List,
+ short-I-RNTI-Profile-List Short-I-RNTI-Profile-List,
+ choice-extension ProtocolIE-Single-Container { { Local-NG-RAN-Node-Identifier-ExtIEs} }
+}
+```
+
+```
+Local-NG-RAN-Node-Identifier-ExtIEs XNAP-PROTOCOL-IES ::= {
+ { ID id-Full-and-Short-I-RNTI-Profile-List CRITICALITY ignore TYPE Full-and-Short-I-RNTI-Profile-List PRESENCE mandatory},
+ ...
+}
+```
+
+```
+Full-and-Short-I-RNTI-Profile-List ::= SEQUENCE {
+
+ full-I-RNTI-Profile-List Full-I-RNTI-Profile-List,
+ short-I-RNTI-Profile-List Short-I-RNTI-Profile-List,
+ iE-Extensions ProtocolExtensionContainer { { Full-and-Short-I-RNTI-Profile-List-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Full-and-Short-I-RNTI-Profile-List-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+}
+
+Full-I-RNTI-Profile-List ::= CHOICE {
+
+ full-I-RNTI-Profile-0 BIT STRING (SIZE (21)),
+ full-I-RNTI-Profile-1 BIT STRING (SIZE (18)),
+ full-I-RNTI-Profile-2 BIT STRING (SIZE (15)),
+ full-I-RNTI-Profile-3 BIT STRING (SIZE (12)),
+ choice-extension ProtocolIE-Single-Container { { Full-I-RNTI-Profile-List-ExtIEs} }
+}
+
+Full-I-RNTI-Profile-List-ExtIEs XNAP-PROTOCOL-IES ::= {
+
+ ...
+}
+```
+
+}
+
+```
+Short-I-RNTI-Profile-List ::= CHOICE {
+ short-I-RNTI-Profile-0 BIT STRING (SIZE (8)),
+ short-I-RNTI-Profile-1 BIT STRING (SIZE (6)),
+ choice-extension ProtocolIE-Single-Container { { Short-I-RNTI-Profile-List-ExtIEs} }
+}
+```
+
+```
+Short-I-RNTI-Profile-List-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+LastVisitedCell-Item ::= CHOICE {
+ nG-RAN-Cell LastVisitedNGRANCellInformation,
+ e-UTRAN-Cell LastVisitedEUTRANCellInformation,
+ uTRAN-Cell LastVisitedUTRANCellInformation,
+ gERAN-Cell LastVisitedGERANCellInformation,
+ choice-extension ProtocolIE-Single-Container { { LastVisitedCell-Item-ExtIEs} }
+}
+```
+
+```
+LastVisitedCell-Item-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+}
+
+LastVisitedEUTRANCellInformation ::= OCTET STRING
+
+LastVisitedGERANCellInformation ::= OCTET STRING
+
+LastVisitedNGRANCellInformation ::= OCTET STRING
+
+LastVisitedUTRANCellInformation ::= OCTET STRING
+
+LastVisitedPSCellInformation ::= OCTET STRING
+
+LastVisitedPSCellList ::= SEQUENCE (SIZE(1..maxnoofPSCellsPerSN)) OF LastVisitedPSCellList-Item
+
+LastVisitedPSCellList-Item ::= SEQUENCE {
+
+ lastVisitedPSCellInformation LastVisitedPSCellInformation,
+
+ iE-Extensions ProtocolExtensionContainer { { LastVisitedPSCellList-Item-ExtIEs } } OPTIONAL,
+
+ ...
+
+}
+
+LastVisitedPSCellList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+
+}
+
+```
+SCGUEHistoryInformation ::= SEQUENCE {
+ lastVisitedPSCellList LastVisitedPSCellList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SCGUEHistoryInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SCGUEHistoryInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+LCID ::= INTEGER (1..32, ...)
+
+Links-to-log ::= ENUMERATED {uplink, downlink, both-uplink-and-downlink, ...}
+
+ListOfCells ::= SEQUENCE (SIZE(1..maxnoofCellsinAoI)) OF CellsinAoI-Item
+
+CellsinAoI-Item ::= SEQUENCE {
+ pLMN-Identity PLMN-Identity,
+ ng-ran-cell-id NG-RAN-Cell-Identity,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { {CellsInAoI-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+CellsInAoI-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+ListOfRANNodesInAoI ::= SEQUENCE (SIZE(1.. maxnoofRANNodesInAoI)) OF GlobalNG-RANNodesInAoI-Item
+
+GlobalNG-RANNodesInAoI-Item ::= SEQUENCE {
+ global-NG-RAN-Node-ID GlobalNG-RANNode-ID,
+ iE-Extensions ProtocolExtensionContainer { {GlobalNG-RANNodesInAoI-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+GlobalNG-RANNodesInAoI-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+ListOfTAIsInAoI ::= SEQUENCE (SIZE(1..maxnoofTAIsInAoI)) OF TAIsInAoI-Item
+```
+
+```
+TAIsinAoI-Item ::= SEQUENCE {
+ pLMN-Identity PLMN-Identity,
+ tAC TAC,
+ iE-Extensions ProtocolExtensionContainer { {TAIsinAoI-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TAIsinAoI-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+LocationInformationSNReporting ::= ENUMERATED {
+ pSCell,
+ ...
+}
+
+LocationReportingInformation ::= SEQUENCE {
+ eventType EventType,
+ reportArea ReportArea,
+ areaOfInterest AreaOfInterestInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {LocationReportingInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+
+LocationReportingInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-AdditionLocationInformation CRITICALITY ignore EXTENSION AdditionLocationInformation PRESENCE optional },
+ ...
+}
+
+LoggedEventTriggeredConfig ::= SEQUENCE {
+ eventTypeTrigger EventTypeTrigger,
+ iE-Extensions ProtocolExtensionContainer { { LoggedEventTriggeredConfig-ExtIEs } } OPTIONAL,
+ ...
+}
+
+LoggedEventTriggeredConfig-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+LoggedMDT-NR ::= SEQUENCE {
+ loggingInterval LoggingInterval,
+ loggingDuration LoggingDuration,
+ reportType ReportType,
+ bluetoothMeasurementConfiguration BluetoothMeasurementConfiguration OPTIONAL,
+ wlanMeasurementConfiguration WLANMeasurementConfiguration OPTIONAL,
+}
+```
+
+```
+ sensorMeasurementConfiguration SensorMeasurementConfiguration OPTIONAL,
+ areaScopeOfNeighCellsList AreaScopeOfNeighCellsList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {LoggedMDT-NR-ExtIEs} } OPTIONAL,
+ ...
+}
+
+LoggedMDT-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-earlyMeasurement CRITICALITY ignore EXTENSION EarlyMeasurement PRESENCE optional },
+ ...
+}
+
+LoggingInterval ::= ENUMERATED { ms320, ms640, ms1280, ms2560, ms5120, ms10240, ms20480, ms30720, ms40960, ms61440, infinity,...}
+
+LoggingDuration ::= ENUMERATED { m10, m20, m40, m60, m90, m120}
+
+LowerLayerPresenceStatusChange ::= ENUMERATED {
+ release-lower-layers,
+ re-establish-lower-layers,
+ ...
+ suspend-lower-layers,
+ resume-lower-layers
+}
+```
+
+```
+LTEA2XServicesAuthorized ::= SEQUENCE {
+ aerialUE AerialUE OPTIONAL,
+ aerialControllerUE AerialControllerUE OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {LTEA2XServicesAuthorized-ExtIEs} } OPTIONAL,
+ ...
+}
+
+LTEA2XServicesAuthorized-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+LTEV2XServicesAuthorized ::= SEQUENCE {
+ vehicleUE VehicleUE OPTIONAL,
+ pedestrianUE PedestrianUE OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {LTEV2XServicesAuthorized-ExtIEs} } OPTIONAL,
+ ...
+}
+
+LTEV2XServicesAuthorized-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+LTEUESidelinkAggregateMaximumBitRate ::= SEQUENCE {
+ uESidelinkAggregateMaximumBitRate BitRate,
+ iE-Extensions ProtocolExtensionContainer { {LTEUESidelinkAggregateMaximumBitRate-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+LTEUESidelinkAggregateMaximumBitRate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+-- M
+
+```
+MaxNrofRS-IndexesToReport ::= INTEGER (1..64, ...)
+```
+
+```
+MBServiceType ::= ENUMERATED {multicast, broadcast, ...}
+```
+
+```
+MDTAlignmentInfo ::= CHOICE {
+ s-BasedMDT S-BasedMDT,
+ choice-extension ProtocolIE-Single-Container { {MDTAlignmentInfo-ExtIEs} }
+}
+```
+
+```
+MDTAlignmentInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+MeasCollectionEntityIPAddress ::= TransportLayerAddress
+```
+
+```
+M1Configuration ::= SEQUENCE {
+```
+
+```
+ m1reportingTrigger M1ReportingTrigger,
+```
+
+```
+ m1thresholdEventA2 M1ThresholdEventA2 OPTIONAL,
+```
+
+```
+ -- Included in case of event-triggered, or event-triggered periodic reporting for measurement M1
+```
+
+```
+ m1periodicReporting M1PeriodicReporting OPTIONAL,
+```
+
+```
+ -- Included in case of periodic or event-triggered periodic reporting
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { M1Configuration-ExtIEs } } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+M1Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ {ID id-BeamMeasurementIndicationM1 CRITICALITY ignore EXTENSION BeamMeasurementIndicationM1 PRESENCE optional }|
+```
+
+```
+ {ID id-BeamMeasurementsReportConfiguration CRITICALITY ignore EXTENSION BeamMeasurementsReportConfiguration PRESENCE conditional },
+```
+
+```
+ -- The above IE shall be present if the BeamMeasurementIndicationM1 IE is set to "true"
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+M1PeriodicReporting ::= SEQUENCE {
+ reportInterval ReportIntervalMDT,
+ reportAmount ReportAmountMDT,
+ iE-Extensions ProtocolExtensionContainer { { M1PeriodicReporting-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M1PeriodicReporting-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-ExtendedReportIntervalMDT CRITICALITY ignore EXTENSION ExtendedReportIntervalMDT PRESENCE optional},
+ ...
+}
+
+M1ReportingTrigger ::= ENUMERATED{
+ periodic,
+ a2eventtriggered,
+ a2eventtriggered-periodic,
+ ...
+}
+
+M1ThresholdEventA2 ::= SEQUENCE {
+```
+
+```
+ measurementThreshold MeasurementThresholdA2,
+ iE-Extensions ProtocolExtensionContainer { { M1ThresholdEventA2-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M1ThresholdEventA2-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+M4Configuration ::= SEQUENCE {
+ m4period M4period,
+ m4-links-to-log Links-to-log,
+ iE-Extensions ProtocolExtensionContainer { { M4Configuration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M4Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-M4ReportAmount CRITICALITY ignore EXTENSION M4ReportAmountMDT PRESENCE optional },
+ ...
+}
+```
+
+M4ReportAmountMDT ::= ENUMERATED{r1, r2, r4, r8, r16, r32, r64, infinity, ...}
+
+M4period ::= ENUMERATED {ms1024, ms2048, ms5120, ms10240, min1, ... }
+
+M5Configuration ::= SEQUENCE {
+ m5period M5period,
+ m5-links-to-log Links-to-log,
+ iE-Extensions ProtocolExtensionContainer { { M5Configuration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M5Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-M5ReportAmount CRITICALITY ignore EXTENSION M5ReportAmountMDT PRESENCE optional },
+ ...
+}
+
+M5ReportAmountMDT ::= ENUMERATED{r1, r2, r4, r8, r16, r32, r64, infinity, ...}
+
+M5period ::= ENUMERATED {ms1024, ms2048, ms5120, ms10240, min1, ... }
+
+M6Configuration ::= SEQUENCE {
+ m6report-Interval M6report-Interval,
+ m6-links-to-log Links-to-log,
+
+```
+iE-Extensions ProtocolExtensionContainer { { M6Configuration-ExtIEs} } OPTIONAL,
+...
+}
+
+M6Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-M6ReportAmount CRITICALITY ignore EXTENSION M6ReportAmountMDT PRESENCE optional}|
+ { ID id-ExcessPacketDelayThresholdConfiguration CRITICALITY ignore EXTENSION ExcessPacketDelayThresholdConfiguration PRESENCE optional},
+...
+}
+
+M6ReportAmountMDT ::= ENUMERATED{r1, r2, r4, r8, r16, r32, r64, infinity, ...}
+
+M6report-Interval ::= ENUMERATED { ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1, min6, min12, min30,... }
+
+M7Configuration ::= SEQUENCE {
+ m7period M7period,
+ m7-links-to-log Links-to-log,
+ iE-Extensions ProtocolExtensionContainer { { M7Configuration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+M7Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+{ ID id-M7ReportAmount CRITICALITY ignore EXTENSION M7ReportAmountMDT PRESENCE optional },
+...
+}
+```
+
+```
+M7ReportAmountMDT ::= ENUMERATED{r1, r2, r4, r8, r16, r32, r64, infinity, ...}
+```
+
+```
+M7period ::= INTEGER(1..60, ...)
+```
+
+```
+MAC-I ::= BIT STRING (SIZE(16))
+```
+
+```
+MaskedIMEISV ::= BIT STRING (SIZE(64))
+```
+
+```
+MaxCHOp preparations ::= INTEGER (1..8, ...)
+```
+
+```
+MaximumDataBurstVolume ::= INTEGER (0..4095, ..., 4096.. 2000000)
+```
+
+```
+MaximumIPDataRate ::= SEQUENCE {
+ maxIPRate-UL MaxIPRate,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { {MaximumIPdatarate-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MaximumIPdatarate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-MaxIPrate-DL CRITICALITY ignore EXTENSION MaxIPrate PRESENCE optional},
+ ...
+}
+
+MaxIPrate ::= ENUMERATED {
+ bitrate64kbs,
+ max-UErate,
+ ...
+}
+
+MBSFNControlRegionLength ::= INTEGER (0..3)
+
+MBSFNSubframeAllocation-E-UTRA ::= CHOICE {
+ oneframe BIT STRING (SIZE(6)),
+ fourframes BIT STRING (SIZE(24)),
+ choice-extension ProtocolIE-Single-Container { {MBSFNSubframeAllocation-E-UTRA-ExtIEs} }
+```
+
+```
+}
+
+MBSFNSubframeAllocation-E-UTRA-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+MBSFNSubframeInfo-E-UTRA ::= SEQUENCE (SIZE(1..maxnoofMBSFNEUTRA)) OF MBSFNSubframeInfo-E-UTRA-Item
+
+MBSFNSubframeInfo-E-UTRA-Item ::= SEQUENCE {
+ radioframeAllocationPeriod ENUMERATED{n1,n2,n4,n8,n16,n32,...},
+ radioframeAllocationOffset INTEGER (0..7, ...),
+ subframeAllocation MBSFNSubframeAllocation-E-UTRA,
+ iE-Extensions ProtocolExtensionContainer { {MBSFNSubframeInfo-E-UTRA-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBSFNSubframeInfo-E-UTRA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MBS-FrequencySelectionArea-Identity ::= OCTET STRING (SIZE(3))
+```
+
+MBS-Area-Session-ID ::= INTEGER (0..65535, ...)
+
+MBS-MappingandDataForwardingRequestInfomSource ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MBS-MappingandDataForwardingRequestInfomSource-Item
+
+MBS-MappingandDataForwardingRequestInfomSource-Item ::= SEQUENCE {
+ mRB-ID MRB-ID,
+ mBS-QoSFlow-List mBS-QoSFlow-List,
+ mRB-ProgressInformation MRB-ProgressInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { MBS-MappingandDataForwardingRequestInfomSource-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBS-MappingandDataForwardingRequestInfomSource-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MBS-DataForwarding-Indicator ::= ENUMERATED{mbs-only, ...}
+
+MBS-DataForwardingResponseInfomTarget ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF MBS-DataForwardingResponseInfomTarget-Item
+
+MBS-DataForwardingResponseInfomTarget-Item ::= SEQUENCE {
+ mRB-ID MRB-ID,
+
+```
+dlForwardingUPTNL UPTransportLayerInformation,
+mRB-ProgressInformation MRB-ProgressInformation OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { { MBS-DataForwardingResponseInfotarget-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+MBS-DataForwardingResponseInfotarget-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+MBS-QoSFlow-List ::= SEQUENCE (SIZE(1..maxnoofMBSQoSFlows)) OF QoSFlowIdentifier
+
+MBS-QoSFlowsToAdd-List ::= SEQUENCE (SIZE(1..maxnoofMBSQoSFlows)) OF MBS-QoSFlowsToAdd-Item
+
+MBS-QoSFlowsToAdd-Item ::= SEQUENCE {
+ mBS-QoSFlowIdentifier QoSFlowIdentifier,
+ mBS-QoSFlowLevelQoSParameters QoSFlowLevelQoSParameters,
+ iE-Extensions ProtocolExtensionContainer { { MBS-QoSFlowsToAdd-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBS-QoSFlowsToAdd-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+```
+
+```
+}
+
+MBS-ServiceArea ::= CHOICE {
+ locationindependent MBS-ServiceAreaInformation,
+ locationdependent MBS-ServiceAreaInformationList,
+ choice-extension ProtocolIE-Single-Container { {MBS-ServiceArea-ExtIEs} }
+}
+
+MBS-ServiceArea-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+MBS-ServiceAreaCell-List ::= SEQUENCE (SIZE(1.. maxnoofCellsforMBS)) OF NR-CGI
+
+MBS-ServiceAreaInformation ::= SEQUENCE {
+ mBS-ServiceAreaCell-List MBS-ServiceAreaCell-List OPTIONAL,
+ mBS-ServiceAreaTAI-List MBS-ServiceAreaTAI-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBS-ServiceAreaInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+
+MBS-ServiceAreaInformationList ::= SEQUENCE (SIZE(1..maxnoofMBSServiceAreaInformation)) OF MBS-ServiceAreaInformation-Item
+
+MBS-ServiceAreaInformation-Item ::= SEQUENCE { mBS-Area-Session-ID MBS-Area-Session-ID,
+ mBS-ServiceAreaInformation MBS-ServiceAreaInformation,
+ iE-Extensions ProtocolExtensionContainer { { MBS-ServiceAreaInformation-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBS-ServiceAreaInformation-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MBS-ServiceAreaTAI-List ::= SEQUENCE (SIZE(1.. maxnoofTAIforMBS)) OF MBS-ServiceAreaTAI-Item
+
+MBS-ServiceAreaTAI-Item ::= SEQUENCE {
+ plmn-ID PLMN-Identity,
+ tAC TAC,
+ iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaTAI-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+MBS-ServiceAreaTAI-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+MBS-Session-ID ::= SEQUENCE {
+```
+
+```
+ tMGI TMGI,
+```
+
+```
+ nID NID OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {MBS-Session-ID-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+MBS-Session-ID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+MBS-AssistanceInformation ::= ENUMERATED {true, ...}
+```
+
+```
+MBS-SessionAssociatedInformation ::= SEQUENCE (SIZE(1..maxnoofAssociatedMBSSessions)) OF MBS-SessionAssociatedInformation-Item
+```
+
+```
+MBS-SessionAssociatedInformation-Item ::= SEQUENCE {
+```
+
+```
+ mBS-Session-ID MBS-Session-ID,
+```
+
+```
+ associated-QoSFlowInfo-List Associated-QoSFlowInfo-List,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { { MBS-SessionAssociatedInformation-Item-ExtIEs } } OPTIONAL,
+...
+}
+
+MBS-SessionAssociatedInformation-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+MBS-SessionInformation-List ::= SEQUENCE (SIZE(1..maxnoofMBSSessions)) OF MBS-SessionInformation-Item
+
+MBS-SessionInformation-Item ::= SEQUENCE {
+ mBS-Session-ID MBS-Session-ID,
+ mBS-Area-Session-ID MBS-Area-Session-ID OPTIONAL,
+ active-MBS-SessionInformation Active-MBS-SessionInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { MBS-SessionInformation-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+MBS-SessionInformation-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-MBS-AssistanceInformation CRITICALITY ignore EXTENSION MBS-AssistanceInformation PRESENCE optional },
+ ...
+}
+```
+
+MBS-SessionInformationResponse-List ::= SEQUENCE (SIZE(1..maxnoofMBSSessions)) OF MBS-SessionInformationResponse-Item
+
+MBS-SessionInformationResponse-Item ::= SEQUENCE {
+ mBS-Session-ID MBS-Session-ID,
+ mBS-DataForwardingResponseInfofromTarget MBS-DataForwardingResponseInfofromTarget OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { MBS-SessionInformationResponse-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MBS-SessionInformationResponse-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MRB-ID ::= INTEGER (1..512, ...)
+
+MRB-ProgressInformation ::= CHOICE {
+ pdcp-SN12 INTEGER (0..4095),
+ pdcp-SN18 INTEGER (0..262143),
+ choice-extension ProtocolIE-Single-Container { { MRB-ProgressInformation-ExtIEs} }
+}
+
+MRB-ProgressInformation-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+```
+}
+
+MDT-Activation ::= ENUMERATED {
+ immediate-MDT-only,
+ immediate-MDT-and-Trace,
+ logged-MDT-only,
+ ...
+}
+
+MDT-Configuration ::= SEQUENCE {
+ mDT-Configuration-NR MDT-Configuration-NR OPTIONAL,
+ mDT-Configuration-EUTRA MDT-Configuration-EUTRA OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MDT-Configuration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MDT-Configuration-NR ::= SEQUENCE {
+ mdt-Activation MDT-Activation,
+ areaScopeOfMDT-NR AreaScopeOfMDT-NR OPTIONAL,
+ mDTMode-NR MDTMode-NR,
+}
+```
+
+```
+ signallingBasedMDTPLMNList MDTPLMNList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-NR-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MDT-Configuration-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-PNI-NPN-AreaScopeOfMDT CRITICALITY ignore EXTENSION PNI-NPN-AreaScopeOfMDT PRESENCE optional },
+ ...
+}
+
+MDT-Configuration-EUTRA ::= SEQUENCE {
+ mdt-Activation MDT-Activation,
+ areaScopeOfMDT-EUTRA AreaScopeOfMDT-EUTRA OPTIONAL,
+ mDTMode-EUTRA MDTMode-EUTRA,
+ signallingBasedMDTPLMNList MDTPLMNList,
+ iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-EUTRA-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MDT-Configuration-EUTRA-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MDT-Location-Info ::= BIT STRING (SIZE (8))
+```
+
+MDTPLMNLList ::= SEQUENCE (SIZE(1..maxnoofMDTPLMNs)) OF PLMN-Identity
+
+MDTPLMNModificationList ::= SEQUENCE (SIZE(0..maxnoofMDTPLMNs)) OF PLMN-Identity
+
+MDTMode-NR ::= CHOICE {
+ immediateMDT ImmediateMDT-NR,
+ loggedMDT LoggedMDT-NR,
+ ...
+ mDTMode-NR-Extension MDTMode-NR-Extension
+}
+
+MDTMode-NR-Extension ::= ProtocolIE-Single-Container {{ MDTMode-NR-ExtensionIE }}
+
+MDTMode-NR-ExtensionIE XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+MDTMode-EUTRA ::= OCTET STRING
+
+MeasObjectContainer ::= OCTET STRING
+
+MeasurementsToActivate ::= BIT STRING (SIZE (8))
+
+MeasurementThresholdA2 ::= CHOICE {
+ threshold-RSRP Threshold-RSRP,
+ threshold-RSRQ Threshold-RSRQ,
+ threshold-SINR Threshold-SINR,
+ choice-extension ProtocolIE-Single-Container { { MeasurementThresholdA2-ExtIEs } }
+
+MeasurementThresholdA2-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+Measurement-ID ::= INTEGER (1..4095,...)
+
+MIMO PRB Usage Information ::= SEQUENCE {
+ dl-GBR-PRB-usage-for-MIMO DL-GBR-PRB-usage-for-MIMO,
+ ul-GBR-PRB-usage-for-MIMO UL-GBR-PRB-usage-for-MIMO,
+ dl-non-GBR-PRB-usage-for-MIMO DL-non-GBR-PRB-usage-for-MIMO,
+ ul-non-GBR-PRB-usage-for-MIMO UL-non-GBR-PRB-usage-for-MIMO,
+
+```
+ dl-Total-PRB-usage-for-MIMO DL-Total-PRB-usage-for-MIMO,
+ ul-Total-PRB-usage-for-MIMO UL-Total-PRB-usage-for-MIMO,
+ iE-Extensions ProtocolExtensionContainer { { MIMO PRBusageInformation-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+MIMO PRBusageInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+MobileIAB-AuthorizationStatus ::= ENUMERATED {authorized, not-authorized,...}
+```
+
+```
+MobileIABCell ::= ENUMERATED {
+ true,
+ ...
+}
+```
+
+```
+MobilityInformation ::= BIT STRING (SIZE(32))
+```
+
+```
+MobilityParametersModificationRange ::= SEQUENCE {
+ handoverTriggerChangeLowerLimit INTEGER (-20..20),
+ handoverTriggerChangeUpperLimit INTEGER (-20..20),
+ ...
+}
+```
+
+}
+
+MobilityParametersInformation ::= SEQUENCE {
+
+handoverTriggerChange INTEGER (-20..20),
+
+...
+
+}
+
+MobilityRestrictionList ::= SEQUENCE {
+
+serving-PLMN PLMN-Identity,
+
+equivalent-PLMNs SEQUENCE (SIZE(1..maxnoofEPLMNs)) OF PLMN-Identity OPTIONAL,
+
+rat-Restrictions RAT-RestrictionsList OPTIONAL,
+
+forbiddenAreaInformation ForbiddenAreaList OPTIONAL,
+
+serviceAreaInformation ServiceAreaList OPTIONAL,
+
+iE-Extensions ProtocolExtensionContainer { {MobilityRestrictionList-ExtIEs} } OPTIONAL,
+
+...
+
+}
+
+MobilityRestrictionList-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+| | | | | |
+|-----------------------------------------|--------------------|-------------------------------------------|-------------------|--|
+| { ID id-LastE-UTRANPLMNIdentity | CRITICALITY ignore | EXTENSION PLMN-Identity | PRESENCE optional | |
+| { ID id-CNTypeRestrictionsForServing | CRITICALITY ignore | EXTENSION CNTypeRestrictionsForServing | PRESENCE optional | |
+| { ID id-CNTypeRestrictionsForEquivalent | CRITICALITY ignore | EXTENSION CNTypeRestrictionsForEquivalent | PRESENCE optional | |
+| { ID id-NPNMobilityInformation | CRITICALITY reject | EXTENSION NPNMobilityInformation | PRESENCE optional | |
+
+```
+...
+}
+
+CNTypeRestrictionsForEquivalent ::= SEQUENCE (SIZE(1..maxnoofEPLMNs)) OF CNTypeRestrictionsForEquivalentItem
+
+CNTypeRestrictionsForEquivalentItem ::= SEQUENCE {
+ plmn-Identity PLMN-Identity,
+ cn-Type ENUMERATED {epc-forbidden, fiveGC-forbidden, ...},
+ iE-Extensions ProtocolExtensionContainer { {CNTypeRestrictionsForEquivalentItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+CNTypeRestrictionsForEquivalentItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+CNTypeRestrictionsForServing ::= ENUMERATED {
+ epc-forbidden,
+ ...
+}
+
+RAT-RestrictionsList ::= SEQUENCE (SIZE(1..maxnoofPLMNs)) OF RAT-RestrictionsItem
+```
+
+```
+RAT-RestrictionsItem ::= SEQUENCE {
+ plmn-Identity PLMN-Identity,
+ rat-RestrictionInformation RAT-RestrictionInformation,
+ iE-Extensions ProtocolExtensionContainer { {RAT-RestrictionsItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RAT-RestrictionsItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ExtendedRATRestrictionInformation CRITICALITY ignore EXTENSION ExtendedRATRestrictionInformation PRESENCE optional },
+ ...
+}
+
+RAT-RestrictionInformation ::= BIT STRING {e-UTRA (0),nR (1), nR-unlicensed (2), nR-LEO (3), nR-MEO (4), nR-GEO (5), nR-OTHERSAT (6)} (SIZE(8, ...))
+
+ForbiddenAreaList ::= SEQUENCE (SIZE(1..maxnoofPLMNs)) OF ForbiddenAreaItem
+
+ForbiddenAreaItem ::= SEQUENCE {
+ plmn-Identity PLMN-Identity,
+ forbidden-TACs SEQUENCE (SIZE(1..maxnoofForbiddenTACs)) OF TAC,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {ForbiddenAreaItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ForbiddenAreaItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ServiceAreaList ::= SEQUENCE (SIZE(1..maxnoofPLMNs)) OF ServiceAreaItem
+
+ServiceAreaItem ::= SEQUENCE {
+ plmn-Identity PLMN-Identity,
+ allowed-TACs-ServiceArea SEQUENCE (SIZE(1..maxnoofAllowedAreas)) OF TAC OPTIONAL,
+ not-allowed-TACs-ServiceArea SEQUENCE (SIZE(1..maxnoofAllowedAreas)) OF TAC OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ServiceAreaItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ServiceAreaItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+MR-DC-ResourceCoordinationInfo ::= SEQUENCE {
+ ng-RAN-Node-ResourceCoordinationInfo NG-RAN-Node-ResourceCoordinationInfo,
+ iE-Extension ProtocolExtensionContainer { {MR-DC-ResourceCoordinationInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MR-DC-ResourceCoordinationInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NG-RAN-Node-ResourceCoordinationInfo ::= CHOICE {
+ eutra-resource-coordination-info E-UTRA-ResourceCoordinationInfo,
+ nr-resource-coordination-info NR-ResourceCoordinationInfo
+}
+
+E-UTRA-ResourceCoordinationInfo ::= SEQUENCE {
+ e-utra-cell E-UTRA-CGI,
+ ul-coordination-info BIT STRING (SIZE (6..4400)),
+ dl-coordination-info BIT STRING (SIZE (6..4400)) OPTIONAL,
+ nr-cell NR-CGI OPTIONAL,
+ e-utra-coordination-assistance-info E-UTRA-CoordinationAssistanceInfo OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {E-UTRA-ResourceCoordinationInfo-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+}
+
+E-UTRA-ResourceCoordinationInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+E-UTRA-CoordinationAssistanceInfo ::= ENUMERATED {coordination-not-required, ...}
+
+NR-ResourceCoordinationInfo ::= SEQUENCE {
+ nr-cell NR-CGI,
+ ul-coordination-info BIT STRING (SIZE (6..4400)),
+ dl-coordination-info BIT STRING (SIZE (6..4400)) OPTIONAL,
+ e-utra-cell E-UTRA-CGI OPTIONAL,
+ nr-coordination-assistance-info
+ NR-CoordinationAssistanceInfo OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {NR-ResourceCoordinationInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NR-ResourceCoordinationInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+NR-CoordinationAssistanceInfo ::= ENUMERATED {coordination-not-required, ...}
+
+MessageOversizeNotification ::= SEQUENCE {
+ maximumCellListSize MaximumCellListSize,
+ iE-Extension ProtocolExtensionContainer { {MessageOversizeNotification-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MessageOversizeNotification-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MaximumCellListSize ::= INTEGER(1..16384, ...)
+
+MT-SDT-Information ::= SEQUENCE {
+ mT-SDT-Indicator MT-SDT-Indicator,
+ mT-SDT-DataSize MT-SDT-DataSize,
+ iE-Extensions ProtocolExtensionContainer { { MT-SDT-Information-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MT-SDT-Information-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+ ...
+}
+
+MT-SDT-DataSize ::= INTEGER (1..96000, ...)
+
+MT-SDT-Indicator ::= ENUMERATED {true, ...}
+
+MultiplexingInfo ::= SEQUENCE{
+ iAB-MT-Cell-List IAB-MT-Cell-List,
+ iE-Extensions ProtocolExtensionContainer { {MultiplexingInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+MultiplexingInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MeasuredUETrajectory ::= SEQUENCE (SIZE(1..maxnoofCellsTrajectory)) OF MeasuredUETrajectory-Item
+
+MeasuredUETrajectory-Item ::= SEQUENCE{
+ measuredtrajectoryCellInfo MeasuredTrajectroyCellInfo,
+ iE-Extensions ProtocolExtensionContainer { { MeasuredUETrajectory-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+...
+}
+
+MeasuredUETrajectory-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MeasuredTrajectroyCellInfo ::= CHOICE {
+ nG-RAN-Cell MeasuredTrajectoryNGRANCellInfo,
+ choice-extension ProtocolIE-Single-Container { { MeasuredTrajectroyCellInfo-ExtIEs} }
+}
+
+MeasuredTrajectroyCellInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+MeasuredTrajectoryNGRANCellInfo ::= SEQUENCE {
+ globalNG-RANCell-ID GlobalNG-RANCell-ID,
+ timeUEStaysInCell INTEGER (0..4095),
+ iE-Extensions ProtocolExtensionContainer { { MeasuredTrajectoryNGRANCellInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+MeasuredTrajectoryNGRANCellInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+-- N
+
+```
+N6JitterInformation ::= SEQUENCE {
+ n6JitterLowerBound INTEGER (-127..127),
+ n6JitterUpperBound INTEGER (-127..127),
+ iE-Extensions ProtocolExtensionContainer { { N6JitterInformationExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+N6JitterInformationExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+NACellResourceConfigurationList ::= SEQUENCE (SIZE(1..maxnoofHSHNASlots)) OF NACellResourceConfiguration-Item
+```
+
+```
+NACellResourceConfiguration-Item ::= SEQUENCE {
+ nAdownlink ENUMERATED {true, false, ...} OPTIONAL,
+ nAuplink ENUMERATED {true, false, ...} OPTIONAL,
+```
+
+```
+ nAfexible ENUMERATED {true, false, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { NACellResourceConfiguration-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NACellResourceConfiguration-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NBIoT-UL-DL-AlignmentOffset ::= ENUMERATED {
+ khz-7dot5,
+ khz0,
+ khz7dot5,
+ ...
+}
+
+NE-DC-TDM-Pattern ::= SEQUENCE {
+ subframeAssignment ENUMERATED {sa0, sa1, sa2, sa3, sa4, sa5, sa6},
+ harqOffset INTEGER (0..9),
+ iE-Extension ProtocolExtensionContainer { {NE-DC-TDM-Pattern-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+NE-DC-TDM-Pattern-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NeighbourInformation-E-UTRA ::= SEQUENCE (SIZE(1..maxnoofNeighbours)) OF NeighbourInformation-E-UTRA-Item
+```
+
+```
+NeighbourInformation-E-UTRA-Item ::= SEQUENCE {
+```
+
+```
+ e-utra-PCI E-UTRAPCI,
+```
+
+```
+ e-utra-cgi E-UTRA-CGI,
+```
+
+```
+ earfcn E-UTRAARFCN,
+```
+
+```
+ tac TAC,
+```
+
+```
+ ranac RANAC
+```
+
+```
+ OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {NeighbourInformation-E-UTRA-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NeighbourInformation-E-UTRA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NeighbourInformation-NR ::= SEQUENCE (SIZE(1..maxnoofNeighbours)) OF NeighbourInformation-NR-Item
+```
+
+```
+NeighbourInformation-NR-Item ::= SEQUENCE {
+ nr-PCI NRPCI,
+ nr-cgi NR-CGI,
+ tac TAC,
+ ranac RANAC OPTIONAL,
+ nr-mode-info NeighbourInformation-NR-ModeInfo,
+ connectivitySupport Connectivity-Support,
+ measurementTimingConfiguration OCTET STRING,
+ iE-Extensions ProtocolExtensionContainer { {NeighbourInformation-NR-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NeighbourInformation-NR-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-MobileIABCell CRITICALITY ignore EXTENSION MobileIABCell PRESENCE optional },
+ ...
+}
+
+NeighbourInformation-NR-ModeInfo ::= CHOICE {
+ fdd-info NeighbourInformation-NR-ModeFDDInfo,
+ tdd-info NeighbourInformation-NR-ModeTDDInfo,
+ choice-extension ProtocolIE-Single-Container { {NeighbourInformation-NR-ModeInfo-ExtIEs} }
+}
+```
+
+```
+NeighbourInformation-NR-ModeInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+NeighbourInformation-NR-ModeFDDInfo ::= SEQUENCE {
+ ul-NR-FreqInfo NRFrequencyInfo,
+ dl-NR-FeqInfo NRFrequencyInfo,
+ ie-Extensions ProtocolExtensionContainer { {NeighbourInformation-NR-ModeFDDInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+NeighbourInformation-NR-ModeFDDInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+NeighbourInformation-NR-ModeTDDInfo ::= SEQUENCE {
+ nr-FreqInfo NRFrequencyInfo,
+ ie-Extensions ProtocolExtensionContainer { {NeighbourInformation-NR-ModeTDDInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+NeighbourInformation-NR-ModeTDDInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+Neighbour-NG-RAN-Node-List ::= SEQUENCE (SIZE(0..maxnoofNeighbour-NG-RAN-Nodes)) OF Neighbour-NG-RAN-Node-Item
+```
+
+```
+Neighbour-NG-RAN-Node-Item ::= SEQUENCE {
+ globalNG-RANNodeID GlobalNG-RANNode-ID,
+ local-NG-RAN-Node-Identifier Local-NG-RAN-Node-Identifier,
+ ie-Extensions ProtocolExtensionContainer { {Neighbour-NG-RAN-Node-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+Neighbour-NG-RAN-Node-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+NID ::= BIT STRING (SIZE(44))
+```
+
+NRCarrierList ::= SEQUENCE (SIZE(1..maxnoofNRSCSs)) OF NRCarrierItem
+
+NRCarrierItem ::= SEQUENCE {
+ carrierSCS NRSCS,
+ offsetToCarrier INTEGER (0..2199, ...),
+ carrierBandwidth INTEGER (0..maxnoofPhysicalResourceBlocks, ...),
+ iE-Extension ProtocolExtensionContainer { {NRCarrierItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NRCarrierItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NRCellPRACHConfig ::= OCTET STRING
+
+NG-RAN-Cell-Identity ::= CHOICE {
+ nr NR-Cell-Identity,
+ e-utra E-UTRA-Cell-Identity,
+ choice-extension ProtocolIE-Single-Container { {NG-RAN-Cell-Identity-ExtIEs} }
+}
+
+```
+NG-RAN-Cell-Identity-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+NG-RAN-CellPCI ::= CHOICE {
+ nr NRPCI,
+ e-utra E-UTRAPCI,
+ choice-extension ProtocolIE-Single-Container { {NG-RAN-CellPCI-ExtIEs} }
+}
+```
+
+```
+NG-RAN-CellPCI-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+NG-RANnode2SSBOffsetsModificationRange ::= SEQUENCE (SIZE(1..maxnoofSSBAreas)) OF SSBOffsetModificationRange
+```
+
+```
+NG-RANnodeUEXnAPID ::= INTEGER (0.. 4294967295)
+```
+
+```
+NumberofActiveUEs ::= INTEGER(0..16777215, ...)
+```
+
+NodeMeasurementInitiationResult-List ::= SEQUENCE (SIZE(1..maxFailedMeasPerNode)) OF NodeMeasurementInitiationResult-Item
+
+NodeMeasurementInitiationResult-Item ::= SEQUENCE {
+ nodemeasurementFailedReportCharacteristics BIT STRING(SIZE(128)),
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { NodeMeasurementInitiationResult-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NodeMeasurementInitiationResult-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NoofRRRConnections ::= INTEGER (1..65536,...)
+
+NonDynamic5QIDescriptor ::= SEQUENCE {
+ fiveQI FiveQI,
+ priorityLevelQoS PriorityLevelQoS OPTIONAL,
+ averagingWindow AveragingWindow OPTIONAL,
+
+```
+ maximumDataBurstVolume MaximumDataBurstVolume OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {NonDynamic5QIDescriptor-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NonDynamic5QIDescriptor-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CNPacketDelayBudgetDownlink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional}|
+ { ID id-CNPacketDelayBudgetUplink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional},
+ ...
+}
+
+NRARFCN ::= INTEGER (0.. maxNRARFCN)
+
+NG-eNB-RadioResourceStatus ::= SEQUENCE {
+ dL-GBR-PRB-usage DL-GBR-PRB-usage,
+ uL-GBR-PRB-usage UL-GBR-PRB-usage,
+ dL-non-GBR-PRB-usage DL-non-GBR-PRB-usage,
+ uL-non-GBR-PRB-usage UL-non-GBR-PRB-usage,
+ dL-Total-PRB-usage DL-Total-PRB-usage,
+ uL-Total-PRB-usage UL-Total-PRB-usage,
+ iE-Extensions ProtocolExtensionContainer { { NG-eNB-RadioResourceStatus-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+}
+
+NG-eNB-RadioResourceStatus-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DL-scheduling-PDCCH-CCE-usage CRITICALITY ignore EXTENSION DL-scheduling-PDCCH-CCE-usage PRESENCE optional}|
+ { ID id-UL-scheduling-PDCCH-CCE-usage CRITICALITY ignore EXTENSION UL-scheduling-PDCCH-CCE-usage PRESENCE optional},
+ ...
+}
+
+DL-scheduling-PDCCH-CCE-usage ::= INTEGER (0.. 100)
+UL-scheduling-PDCCH-CCE-usage ::= INTEGER (0.. 100)
+
+TNLCapacityIndicator ::= SEQUENCE {
+ dLTNLOfferedCapacity OfferedCapacity,
+ dLTNLAvailableCapacity AvailableCapacity,
+ uLTNLOfferedCapacity OfferedCapacity,
+ uLTNLAvailableCapacity AvailableCapacity,
+ iE-Extensions ProtocolExtensionContainer { { TNLCapacityIndicator-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TNLCapacityIndicator-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+...
+}
+
+NonFl-TerminatingTopologyBHInformation ::= SEQUENCE {
+ nonFlTerminatingBHInformation-List NonFlTerminatingBHInformation-List,
+ bAPControlPDURLCCH-List BAPControlPDURLCCH-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {NonFl-TerminatingTopologyBHInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NonFl-TerminatingTopologyBHInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NonFlTerminatingBHInformation-List ::= SEQUENCE (SIZE(1..maxnoofBHInfo)) OF NonFlTerminatingBHInformation-Item
+
+NonFlTerminatingBHInformation-Item ::= SEQUENCE {
+ bHInfoIndex BHInfoIndex,
+ dlNonFlTerminatingBHInfo DLNonFlTerminating-BHInfo OPTIONAL,
+ ulNonFlTerminatingBHInfo ULNonFlTerminating-BHInfo OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { { NonFlTerminatingBHInformation-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+NonFlTerminatingBHInformation-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NonUPTraffic ::= CHOICE {
+ nonUPTrafficType NonUPTrafficType,
+ controlPlaneTrafficType ControlPlaneTrafficType,
+ choice-extension ProtocolIE-Single-Container { { NonUPTraffic-ExtIEs} }
+}
+
+NonUPTraffic-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+NonUPTrafficType ::= ENUMERATED {ueassociatedflap, noneueassociatedflap, nonfl, ...}
+
+NoPDUSessionIndication ::= ENUMERATED {true, ...}
+
+NPN-Broadcast-Information ::= CHOICE {
+ snpn-Information NPN-Broadcast-Information-SNPN,
+ pni-npn-Information NPN-Broadcast-Information-PNI-NPN,
+```
+
+```
+ choice-extension ProtocolIE-Single-Container { {NPN-Broadcast-Information-ExtIEs} }
+}
+
+NPN-Broadcast-Information-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+NPN-Broadcast-Information-SNPN ::= SEQUENCE {
+ broadcastSNPNID-List BroadcastSNPNID-List,
+ iE-Extension ProtocolExtensionContainer { {NPN-Broadcast-Information-SNPN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NPN-Broadcast-Information-SNPN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NPN-Broadcast-Information-PNI-NPN ::= SEQUENCE {
+ broadcastPNI-NPN-ID-Information BroadcastPNI-NPN-ID-Information,
+ iE-Extension ProtocolExtensionContainer { {NPN-Broadcast-Information-PNI-NPN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NPN-Broadcast-Information-PNI-NPN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+...
+}
+
+NPNMobilityInformation ::= CHOICE {
+ snpn-mobility-information NPNMobilityInformation-SNPN,
+ pni-npn-mobility-information NPNMobilityInformation-PNI-NPN,
+ choice-extension ProtocolIE-Single-Container { {NPNMobilityInformation-ExtIEs} }
+}
+
+NPNMobilityInformation-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+NPNMobilityInformation-SNPN ::= SEQUENCE {
+ serving-NID NID,
+ iE-Extension ProtocolExtensionContainer { {NPNMobilityInformation-SNPN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NPNMobilityInformation-SNPN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-EquivalentSNPNs CRITICALITY reject EXTENSION EquivalentSNPNs PRESENCE optional},
+ ...
+}
+```
+
+```
+NPNMobilityInformation-PNI-NPN ::= SEQUENCE {
+ allowedPNI-NPN-ID-List AllowedPNI-NPN-ID-List,
+ iE-Extension ProtocolExtensionContainer { {NPNMobilityInformation-PNI-NPN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NPNMobilityInformation-PNI-NPN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NPNPagingAssistanceInformation ::= CHOICE {
+ pni-npn-Information NPNPagingAssistanceInformation-PNI-NPN,
+ choice-extension ProtocolIE-Single-Container { {NPNPagingAssistanceInformation-ExtIEs} }
+}
+
+NPNPagingAssistanceInformation-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+NPNPagingAssistanceInformation-PNI-NPN ::= SEQUENCE {
+ allowedPNI-NPN-ID-List AllowedPNI-NPN-ID-List,
+```
+
+```
+ iE-Extension ProtocolExtensionContainer { {NPNPagingAssistanceInformation-PNI-NPN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NPNPagingAssistanceInformation-PNI-NPN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NPN-Support ::= CHOICE {
+ sNPN NPN-Support-SNPN,
+ choice-Extensions ProtocolIE-Single-Container { {NPN-Support-ExtIEs} }
+}
+
+NPN-Support-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+NPN-Support-SNPN ::= SEQUENCE {
+ nid NID,
+ ie-Extension ProtocolExtensionContainer { {NPN-Support-SNPN-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+NPN-Support-SNPN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NPRACHConfiguration ::= SEQUENCE {
+```
+
+```
+ fdd-or-tdd CHOICE {
+```
+
+```
+ fdd NPRACHConfiguration-FDD,
+```
+
+```
+ tdd NPRACHConfiguration-TDD,
+```
+
+```
+ choice-extension ProtocolIE-Single-Container { { FDD-or-TDD-in-NPRACHConfiguration-Choice-ExtIEs} }
+```
+
+```
+ },
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { NPRACHConfiguration-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NPRACHConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+FDD-or-TDD-in-NPRACHConfiguration-Choice-ExtIEs XNAP-PROTOCOL-IEs ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NPRACHConfiguration-FDD ::= SEQUENCE {
+ nprach-CP-length NPRACH-CP-Length,
+ anchorCarrier-NPRACHConfig OCTET STRING,
+ anchorCarrier-EDT-NPRACHConfig OCTET STRING OPTIONAL,
+ anchorCarrier-Format2-NPRACHConfig OCTET STRING OPTIONAL,
+ anchorCarrier-Format2-EDT-NPRACHConfig OCTET STRING OPTIONAL,
+ non-anchorCarrier-NPRACHConfig OCTET STRING OPTIONAL,
+ non-anchorCarrier-Format2-NPRACHConfig OCTET STRING OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { NPRACHConfiguration-FDD-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+NPRACHConfiguration-FDD-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+NPRACHConfiguration-TDD ::= SEQUENCE {
+ nprach-preambleFormat NPRACH-preambleFormat,
+ anchorCarrier-NPRACHConfigTDD OCTET STRING,
+ non-anchorCarrierFrequencyConfigList Non-AnchorCarrierFrequencyList OPTIONAL,
+ non-anchorCarrier-NPRACHConfigTDD OCTET STRING OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { NPRACHConfiguration-TDD-ExtIEs} } OPTIONAL,
+```
+
+...
+
+}
+
+NPRACHConfiguration-TDD-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+NPRACH-CP-Length ::= ENUMERATED {
+
+us66dot7,
+
+us266dot7,
+
+...
+
+}
+
+NPRACH-preambleFormat ::= ENUMERATED {fmt0,fmt1,fmt2,fmt0a,fmt1a,...}
+
+Non-AnchorCarrierFrequencyList ::= SEQUENCE (SIZE(1..maxnoofNonAnchorCarrierFreqConfig)) OF
+
+SEQUENCE {
+
+non-anchorCarrierFrquency OCTET STRING,
+
+iE-Extensions ProtocolExtensionContainer { { Non-AnchorCarrierFrequencyList-ExtIEs } } OPTIONAL,
+
+...
+
+}
+
+Non-AnchorCarrierFrequencyList-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+ ...
+}
+
+NR-Cell-Identity ::= BIT STRING (SIZE (36))
+
+NG-RAN-Cell-Identity-ListinRANPagingArea ::= SEQUENCE (SIZE (1..maxnoofCellsinRNA)) OF NG-RAN-Cell-Identity
+
+NR-CGI ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ nr-CI NR-Cell-Identity,
+ iE-Extension ProtocolExtensionContainer { {NR-CGI-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NR-CGI-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NR-U-Channel-List ::= SEQUENCE (SIZE (1..maxnoofNR-UChannelIDs)) OF NR-U-Channel-Item
+```
+
+```
+NR-U-Channel-Item ::= SEQUENCE {
+ nR-U-ChannelID NR-U-ChannelID,
+ channelOccupancyTimePercentageDL ChannelOccupancyTimePercentage,
+ energyDetectionThresholdDL EnergyDetectionThreshold,
+ iE-Extension ProtocolExtensionContainer { {NR-U-Channel-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NR-U-Channel-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ChannelOccupancyTimePercentageUL CRITICALITY ignore EXTENSION ChannelOccupancyTimePercentage PRESENCE optional}|
+ { ID id-EnergyDetectionThresholdUL CRITICALITY ignore EXTENSION EnergyDetectionThreshold PRESENCE optional}|
+ { ID id-RadioResourceStatusNR-U CRITICALITY ignore EXTENSION RadioResourceStatusNR-U PRESENCE optional},
+ ...
+}
+
+NR-U-ChannelID ::= INTEGER (1..maxnoofNR-UChannelIDs, ...)
+
+ChannelOccupancyTimePercentage ::= INTEGER (0..100,...)
+
+EnergyDetectionThreshold ::= INTEGER (-100..-50, ...)
+
+NR-U-ChannelInfo-List ::= SEQUENCE (SIZE (1..maxnoofNR-UChannelIDs)) OF NR-U-ChannelInfo-Item
+```
+
+```
+NR-U-ChannelInfo-Item ::= SEQUENCE {
+ nR-U-ChannelID NR-U-ChannelID,
+ nRARFCN NRARFCN,
+ bandwidth Bandwidth,
+ iE-Extension ProtocolExtensionContainer { {NR-U-ChannelInfo-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NR-U-ChannelInfo-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Bandwidth ::= ENUMERATED{mhz10, mhz20, mhz40, mhz60, mhz80, ...}
+
+NRA2XServicesAuthorized ::= SEQUENCE {
+ aerialUE AerialUE OPTIONAL,
+ aerialControllerUE AerialControllerUE OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {NRA2XServicesAuthorized-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+NRA2XServicesAuthorized-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+NRCyclicPrefix ::= ENUMERATED {normal, extended, ...}
+
+NRDL-ULTransmissionPeriodicity ::= ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms3, ms4, ms5, ms10, ms20, ms40, ms60, ms80, ms100, ms120, ms140, ms160, ...}
+
+NRFrequencyBand ::= INTEGER (1..1024, ...)
+
+NRFrequencyBand-List ::= SEQUENCE (SIZE(1..maxnoofNRCellBands)) OF NRFrequencyBandItem
+
+NRFrequencyBandItem ::= SEQUENCE {
+
+nr-frequency-band NRFrequencyBand,
+
+supported-SUL-Band-List SupportedSULBandList
+
+OPTIONAL,
+
+iE-Extension
+
+ProtocolExtensionContainer { {NRFrequencyBandItem-ExtIEs} }
+
+OPTIONAL,
+
+...
+
+}
+
+NRFrequencyBandItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+```
+NRFrequencyInfo ::= SEQUENCE {
+ nrARFCN NRARFCN,
+ sul-information SUL-Information OPTIONAL,
+ frequencyBand-List NRFrequencyBand-List,
+ iE-Extension ProtocolExtensionContainer { {NRFrequencyInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NRFrequencyInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-FrequencyShift7p5khz CRITICALITY ignore EXTENSION FrequencyShift7p5khz PRESENCE optional }, ...
+}
+
+NRMobilityHistoryReport ::= OCTET STRING
+
+NRModeInfo ::= CHOICE {
+ fdd NRModeInfoFDD,
+ tdd NRModeInfoTDD,
+ choice-extension ProtocolIE-Single-Container { {NRModeInfo-ExtIEs} }
+}
+```
+
+```
+NRModeInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NRModeInfoFDD ::= SEQUENCE {
+```
+
+```
+ ulNRFrequencyInfo NRFrequencyInfo,
+```
+
+```
+ dlNRFrequencyInfo NRFrequencyInfo,
+```
+
+```
+ ulNRTransmissionBandwidth NRTransmissionBandwidth,
+```
+
+```
+ dlNRTransmissionBandwidth NRTransmissionBandwidth,
+```
+
+```
+ iE-Extension ProtocolExtensionContainer { {NRModeInfoFDD-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NRModeInfoFDD-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ { ID id-ULCarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }|
+```
+
+```
+ { ID id-DLCarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }|
+```
+
+```
+ { ID id-UL-GNB-DU-Cell-Resource-Configuration CRITICALITY ignore EXTENSION GNB-DU-Cell-Resource-Configuration PRESENCE optional }|
+```
+
+```
+ { ID id-DL-GNB-DU-Cell-Resource-Configuration CRITICALITY ignore EXTENSION GNB-DU-Cell-Resource-Configuration PRESENCE optional },
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+NRModeInfoTDD ::= SEQUENCE {
+
+ nrFrequencyInfo NRFrequencyInfo,
+ nrTransmissionBandwidth NRTransmissionBandwidth,
+ iE-Extension ProtocolExtensionContainer { {NRModeInfoTDD-ExtIEs} } OPTIONAL,
+ ...
+ }
+
+NRModeInfoTDD-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ { ID id-IntendedTDD-DL-ULConfiguration-NR CRITICALITY ignore EXTENSION IntendedTDD-DL-ULConfiguration-NR PRESENCE optional }|
+ { ID id-TDDULDLConfigurationCommonNR CRITICALITY ignore EXTENSION TDDULDLConfigurationCommonNR PRESENCE optional }|
+ { ID id-CarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }|
+ { ID id-tdd-GNB-DU-Cell-Resource-Configuration CRITICALITY ignore EXTENSION GNB-DU-Cell-Resource-Configuration PRESENCE optional },
+ ...
+ }
+
+NRNRB ::= ENUMERATED { nrb11, nrb18, nrb24, nrb25, nrb31, nrb32, nrb38, nrb51, nrb52, nrb65, nrb66, nrb78, nrb79, nrb93, nrb106, nrb107, nrb121, nrb132, nrb133, nrb135, nrb160, nrb162, nrb189, nrb216, nrb217, nrb245, nrb264, nrb270, nrb273, ..., nrb33, nrb62, nrb124, nrb148, nrb248, nrb44, nrb58, nrb92, nrb119, nrb188, nrb242, nrb15 }
+
+NR Paging-eDRX Information ::= SEQUENCE {
+
+ nRPaging-eDRX-Cycle NRPaging-eDRX-Cycle,
+ nRPaging-Time-Window NRPaging-Time-Window OPTIONAL,
+
+```
+ iE-Extensions ProtocolExtensionContainer { {NRPagingeDRXInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NRPagingeDRXInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NRPaging-eDRX-Cycle ::= ENUMERATED {
+ hfquarter, hfhalf, hf1, hf2, hf4,
+ hf8, hf16,
+ hf32, hf64, hf128, hf256,
+ hf512, hf1024,
+ ...
+}
+
+NRPaging-Time-Window ::= ENUMERATED {
+ s1, s2, s3, s4, s5,
+ s6, s7, s8, s9, s10,
+ s11, s12, s13, s14, s15, s16,
+ ...,s17, s18, s19, s20, s21, s22,
+ s23, s24, s25, s26, s27, s28, s29,
+```
+
+```
+ s30, s31, s32
+}
+
+NRPageingDRXInformationforRRRCINACTIVE ::= SEQUENCE {
+ nRPaging-eDRX-Cycle-Inactive NRPaging-eDRX-Cycle-Inactive,
+ iE-Extensions ProtocolExtensionContainer { { NRPageingDRXInformationforRRRCINACTIVE-ExtIEs } } OPTIONAL,
+ ...
+}
+
+NRPageingDRXInformationforRRRCINACTIVE-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NRPaging-eDRX-Cycle-Inactive ::= ENUMERATED {
+ hfquarter, hfhalf, hf1,
+ ...
+}
+
+NRPagingLongeDRXInformationforRRRCINACTIVE ::= SEQUENCE {
+ nRPaging-long-eDRX-Cycle-Inactive NRPaging-long-eDRX-Cycle-Inactive,
+ nRPaging-Time-Window-Inactive NRPaging-Time-Window-Inactive,
+ iE-Extensions ProtocolExtensionContainer { { NRPagingLongeDRXInformationforRRRCINACTIVE-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+```
+
+```
+NR PagingLongeDRXInformationforRR CINACTIVE-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NR Paging-long-eDRX-Cycle-Inactive ::= ENUMERATED {
+```
+
+```
+ hf2, hf4, hf8, hf16,
+```
+
+```
+ hf32, hf64, hf128, hf256,
+```
+
+```
+ hf512, hf1024,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+NR Paging-Time-Window-Inactive ::= ENUMERATED {
+```
+
+```
+ s1, s2, s3, s4, s5,
+```
+
+```
+ s6, s7, s8, s9, s10,
+```
+
+```
+ s11, s12, s13, s14, s15, s16,
+```
+
+```
+ s17, s18, s19, s20, s21, s22,
+```
+
+```
+ s23, s24, s25, s26, s27, s28, s29,
+```
+
+```
+ s30, s31, s32, ...
+```
+
+```
+}
+```
+
+NRPCI ::= INTEGER (0..1007, ...)
+
+NRSCS ::= ENUMERATED { scs15, scs30, scs60, scs120, ..., scs480, scs960 }
+
+NRTransmissionBandwidth ::= SEQUENCE {
+ nRSCS NRSCS,
+ nRNRB NRNRB,
+ iE-Extensions ProtocolExtensionContainer { NRTransmissionBandwidth-ExtIEs } OPTIONAL,
+ ...
+}
+
+NRTransmissionBandwidth-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NumberOfAntennaPorts-E-UTRA ::= ENUMERATED { an1, an2, an4, ... }
+
+NG-RANTraceID ::= OCTET STRING (SIZE (8))
+
+NonGBRResources-Offered ::= ENUMERATED { true, ... }
+
+```
+NRV2XServicesAuthorized ::= SEQUENCE {
+ vehicleUE VehicleUE OPTIONAL,
+ pedestrianUE PedestrianUE OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {NRV2XServicesAuthorized-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NRV2XServicesAuthorized-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NRUESidelinkAggregateMaximumBitRate ::= SEQUENCE {
+ uESidelinkAggregateMaximumBitRate BitRate,
+ iE-Extensions ProtocolExtensionContainer { {NRUESidelinkAggregateMaximumBitRate-ExtIEs} } OPTIONAL,
+ ...
+}
+
+NRUESidelinkAggregateMaximumBitRate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+NSAG-ID ::= INTEGER (0..255, ...)
+```
+
+-- O
+
+OfferedCapacity ::= INTEGER (1.. 16777216,...)
+
+OffsetOfNbiotChannelNumberToEARFCN ::= ENUMERATED {
+ minusTen,
+ minusNine,
+ minusEightDotFive,
+ minusEight,
+ minusSeven,
+ minusSix,
+ minusFive,
+ minusFourDotFive,
+ minusFour,
+ minusThree,
+ minusTwo,
+ minusOne,
+ minusZeroDotFive,
+ zero,
+ one,
+}
+
+```
+ two,
+ three,
+ threeDotFive,
+ four,
+ five,
+ six,
+ seven,
+ sevenDotFive,
+ eight,
+ nine,
+ ...
+}
+
+-- P
+
+PositioningInformation ::= SEQUENCE {
+ requestedSRSTransmissionCharacteristics RequestedSRSTransmissionCharacteristics,
+ routingID RoutingID,
+ nRPPaTransactionID INTEGER (0..32767),
+ iE-Extension ProtocolExtensionContainer { { PositioningInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+PositioningInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+PacketDelayBudget ::= INTEGER (0..1023, ...)
+```
+
+```
+PacketErrorRate ::= SEQUENCE {
+```
+
+```
+ pER-Scalar PER-Scalar,
+```
+
+```
+ pER-Exponent PER-Exponent,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+PacketErrorRate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+PagingCause ::= ENUMERATED {
+```
+
+```
+ voice,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+PedestrianUE ::= ENUMERATED {
+ authorized,
+ not-authorized,
+ ...
+}
+
+PER-Scalar ::= INTEGER (0..9, ...)
+
+PER-Exponent ::= INTEGER (0..9, ...)
+
+PEIPSassistanceInformation ::= SEQUENCE {
+ cNsubgroupID CNsubgroupID,
+ iE-Extensions ProtocolExtensionContainer { {PEIPSassistanceInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PEIPSassistanceInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PacketLossRate ::= INTEGER (0..1000, ...)
+```
+
+```
+PagingDRX ::= ENUMERATED {
+ v32,
+ v64,
+ v128,
+ v256,
+ ... ,
+ v512,
+ v1024
+}
+
+PagingPriority ::= ENUMERATED {
+ prioLevel1,
+ prioLevel2,
+ prioLevel3,
+ prioLevel4,
+ prioLevel5,
+ prioLevel6,
+ prioLevel7,
+ prioLevel8,
+ ...
+}
+```
+
+PartialListIndicator ::= ENUMERATED {partial, ...}
+
+PC5QoSParameters ::= SEQUENCE {
+ pc5QoSFlowList PC5QoSFlowList,
+ pc5LinkAggregateBitRates BitRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { PC5QoSParameters-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PC5QoSParameters-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PC5QoSFlowList ::= SEQUENCE (SIZE(1..maxnoofPC5QoSFlows)) OF PC5QoSFlowItem
+-- The size of the PC5 QoS Flow List shall not exceed 2048 items.
+
+PC5QoSFlowItem ::= SEQUENCE {
+ pQI FiveQI,
+ pc5FlowBitRates PC5FlowBitRates OPTIONAL,
+ range Range OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { PC5QoSFlowItem-ExtIEs} } OPTIONAL,
+
+```
+ ...
+}
+
+PC5QoSFlowItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PC5FlowBitRates ::= SEQUENCE {
+ guaranteedFlowBitRate BitRate,
+ maximumFlowBitRate BitRate,
+ iE-Extensions ProtocolExtensionContainer { { PC5FlowBitRates-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PC5FlowBitRates-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PDCPChangeIndication ::= CHOICE {
+ from-S-NG-RAN-node ENUMERATED {s-ng-ran-node-key-update-required, pdcp-data-recovery-required, ...},
+ from-M-NG-RAN-node ENUMERATED {pdcp-data-recovery-required, ...},
+ choice-extension ProtocolIE-Single-Container { {PDCPChangeIndication-ExtIEs} }
+```
+
+}
+
+PDCPChangeIndication-ExtIEs XNAP-PROTOCOL-IES ::= {
+
+...
+
+}
+
+PDCPDuplicationConfiguration ::= ENUMERATED {
+
+configured,
+
+de-configured,
+
+...
+
+}
+
+PDCPSNLength ::= SEQUENCE {
+
+ulPDCPSNLength ENUMERATED {v12bits, v18bits, ...},
+
+dlPDCPSNLength ENUMERATED {v12bits, v18bits, ...},
+
+iE-Extension ProtocolExtensionContainer { {PDCPSNLength-ExtIEs} } OPTIONAL,
+
+...
+
+}
+
+PDCPSNLength-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+```
+}
+
+PDUSetQoSParameters ::= SEQUENCE {
+ pduSetDelayBudget ExtendedPacketDelayBudget OPTIONAL,
+ pduSetErrorRate PacketErrorRate OPTIONAL,
+ pduSetIntegratedHandlingInformation ENUMERATED {true, false, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { PDUSetQoSParameters-ExtIEs } } OPTIONAL
+}
+
+PDUSetQoSParameters-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PDUSetbasedHandlingIndicator ::= ENUMERATED {
+ supported,
+ ...
+}
+
+PDUSessionAggregateMaximumBitRate ::= SEQUENCE {
+ downlink-session-AMBR BitRate,
+ uplink-session-AMBR BitRate,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { {PDUSessionAggregateMaximumBitRate-ExtIEs} } OPTIONAL,
+...
+}
+```
+
+```
+PDUSessionAggregateMaximumBitRate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+```
+
+```
+PDUSession-List ::= SEQUENCE (SIZE (1.. maxnoofPDUSessions)) OF PDUSession-ID
+```
+
+```
+PDUSession-List-withCause ::= SEQUENCE (SIZE (1.. maxnoofPDUSessions)) OF PDUSession-List-withCause-Item
+```
+
+```
+PDUSession-List-withCause-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ cause Cause OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSession-List-withCause-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+PDUSession-List-withCause-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+```
+
+```
+}
+
+PDUSession-List-withDataForwardingFromTarget ::= SEQUENCE (SIZE (1.. maxnoofPDUSessions)) OF
+ PDUSession-List-withDataForwardingFromTarget-Item
+
+PDUSession-List-withDataForwardingFromTarget-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ dataforwardinginfoTarget DataForwardingInfoFromTargetNGRANnode,
+ iE-Extension ProtocolExtensionContainer { {PDUSession-List-withDataForwardingFromTarget-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSession-List-withDataForwardingFromTarget-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DRB-IDs-takenintouse CRITICALITY reject EXTENSION DRB-List PRESENCE optional},
+ ...
+}
+
+PDUSession-List-withDataForwardingRequest ::= SEQUENCE (SIZE (1.. maxnoofPDUSessions)) OF
+ PDUSession-List-withDataForwardingRequest-Item
+
+PDUSession-List-withDataForwardingRequest-Item ::= SEQUENCE {
+```
+
+```
+
+ pduSessionId PDUSession-ID,
+ dataforwardingInfoproSource DataforwardingandOffloadingInfoproSource OPTIONAL,
+ dRBToBeReleasedList DRBToQoSFlowMapping-List OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {PDUSession-List-withDataForwardingRequest-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSession-List-withDataForwardingRequest-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-Cause CRITICALITY ignore EXTENSION Cause PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session related message level IEs BEGIN
+--
+-- *****
+--
+-- *****
+--
+
+```
+
+```
+-- PDU Session Resources Admitted List
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+PDUSessionResourcesAdmitted-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourcesAdmitted-Item
+```
+
+```
+PDUSessionResourcesAdmitted-Item ::= SEQUENCE {
+```
+
+```
+ pduSessionId PDUSession-ID,
+```
+
+```
+ pduSessionResourceAdmittedInfo PDUSessionResourceAdmittedInfo,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourcesAdmitted-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+PDUSessionResourcesAdmitted-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+PDUSessionResourceAdmittedInfo ::= SEQUENCE {
+```
+
+```
+ dL-NG-U-TNL-Information-Unchanged ENUMERATED {true, ...} OPTIONAL,
+```
+
+```
+ qosFlowsAdmitted-List QoSFlowsAdmitted-List,
+```
+
+```
+ qosFlowsNotAdmitted-List QoSFlows-List-withCause OPTIONAL,
+```
+
+```
+
+ dataForwardingInfoFromTarget DataForwardingInfoFromTargetNGRANnode OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceAdmittedInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceAdmittedInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ID id-SecondarydataForwardingInfoFromTarget-List CRITICALITY ignore EXTENSION SecondarydataForwardingInfoFromTarget-List PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- PDU Session Resources Not Admitted List
+--
+-- *****
+
+PDUSessionResourcesNotAdmitted-List ::= SEQUENCE (SIZE (1..maxnoofPDUSessions)) OF PDUSessionResourcesNotAdmitted-Item
+
+PDUSessionResourcesNotAdmitted-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ cause Cause OPTIONAL,
+
+```
+
+```
+
+iE-Extension ProtocolExtensionContainer { {PDUSessionResourcesNotAdmitted-Item-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+```
+
+```
+
+PDUSessionResourcesNotAdmitted-Item-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resources To Be Setup List
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourcesToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourcesToBeSetup-Item
+
+```
+
+```
+
+PDUSessionResourcesToBeSetup-Item ::= SEQUENCE {
+ pduSessionId PDUSession-ID,
+ s-NSSAI S-NSSAI,
+ pduSessionAMBR PDUSessionAggregateMaximumBitRate OPTIONAL,
+ uL-NG-U-TNLatUPF UPTransportLayerInformation,
+}
+
+```
+
+```
+
+source-DL-NG-U-TNL-Information UPTransportLayerInformation OPTIONAL,
+securityIndication SecurityIndication OPTIONAL,
+pduSessionType PDUSessionType,
+pduSessionNetworkInstance PDUSessionNetworkInstance OPTIONAL,
+qosFlowsToBeSetup-List QoSFlowsToBeSetup-List,
+dataforwardinginfofromSource DataforwardingandOffloadingInfofromSource OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { {PDUSessionResourcesToBeSetup-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+PDUSessionResourcesToBeSetup-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-UL-NG-U-TNLatUPF-List CRITICALITY ignore EXTENSION Additional-UL-NG-U-TNLatUPF-List PRESENCE optional}|
+ { ID id-PDUSessionCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional}|
+ { ID id-Redundant-UL-NG-U-TNLatUPF CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional}|
+ { ID id-Additional-Redundant-UL-NG-U-TNLatUPF-List CRITICALITY ignore EXTENSION Additional-UL-NG-U-TNLatUPF-List PRESENCE optional}|
+ { ID id-RedundantCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional}|
+ { ID id-RedundantPDUSessionInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional}|
+ { ID id-MBS-SessionAssociatedInformation CRITICALITY ignore EXTENSION MBS-SessionAssociatedInformation PRESENCE optional}|
+ { ID id-ECNMarkingorCongestionInformationReportingRequest CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingRequest
+ PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Setup Info - SN terminated
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourceSetupInfo-SNterminated ::= SEQUENCE {
+ uL-NG-U-TNLatUPF UPTransportLayerInformation,
+ pduSessionType PDUSessionType,
+ pduSessionNetworkInstance PDUSessionNetworkInstance OPTIONAL,
+ qosFlowsToBeSetup-List QoSFlowsToBeSetup-List-Setup-SNterminated,
+ dataforwardinginfofromSource DataforwardingandOffloadingInfofromSource OPTIONAL,
+ securityIndication SecurityIndication OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupInfo-SNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourceSetupInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-SecurityResult CRITICALITY reject EXTENSION SecurityResult PRESENCE optional}|
+ { ID id-PDUSessionCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional}|
+ { ID id-DefaultDRB-Allowed CRITICALITY ignore EXTENSION DefaultDRB-Allowed PRESENCE optional}|
+ { ID id-SplitSessionIndicator CRITICALITY reject EXTENSION SplitSessionIndicator PRESENCE optional}|
+}
+
+```
+
+```
+{ ID id-NonGBRResources-Offered CRITICALITY ignore EXTENSION NonGBRResources-Offered PRESENCE optional}|
+{ ID id-Redundant-UL-NG-U-TNLatUPF CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional}|
+{ ID id-RedundantCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional}|
+{ ID id-RedundantPDUSessionInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional},
+...
+}
+
+QoSFlowsToBeSetup-List-Setup-SNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsToBeSetup-List-Setup-SNterminated-Item
+
+QoSFlowsToBeSetup-List-Setup-SNterminated-Item ::= SEQUENCE {
+ qfi QoSFlowIdentifier,
+ qosFlowLevelQoSParameters QoSFlowLevelQoSParameters,
+ offeredGBRQoSFlowInfo GBRQoSFlowInfo OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowsToBeSetup-List-Setup-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoSFlowsToBeSetup-List-Setup-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional}|
+ { ID id-RedundantQoSFlowIndicator CRITICALITY ignore EXTENSION RedundantQoSFlowIndicator PRESENCE optional},
+ ...
+}
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Setup Response Info - SN terminated
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourceSetupResponseInfo-SNterminated ::= SEQUENCE {
+ dL-NG-U-TNLatNG-RAN UPTransportLayerInformation,
+ dRBsToBeSetup DRBsToBeSetupList-SetupResponse-SNterminated OPTIONAL,
+ dataforwardinginfoTarget DataForwardingInfoFromTargetNGRANnode OPTIONAL,
+ qosFlowsNotAdmittedList QoSFlows-List-withCause OPTIONAL,
+ securityResult SecurityResult OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { PDUSessionResourceSetupResponseInfo-SNterminated-ExtIEs } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourceSetupResponseInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DRB-IDs-takenintouse CRITICALITY reject EXTENSION DRB-List PRESENCE optional}|
+ { ID id-Redundant-DL-NG-U-TNLatNG-RAN CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional}|
+ { ID id-UsedRSNInformation CRITICALITY ignore EXTENSION RedundantPDUSessionInformation PRESENCE optional}|
+ { ID id-S-CPAC-dataforwardinginfofromSource CRITICALITY ignore EXTENSION DataforwardingandOffloadingInfofromSource PRESENCE optional}|
+ ...
+}
+
+```
+
+}
+
+DRBsToBeSetupList-SetupResponse-SNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToBeSetupList-SetupResponse-SNterminated-Item
+
+DRBsToBeSetupList-SetupResponse-SNterminated-Item ::= SEQUENCE {
+
+| | | |
+|------------------------------------------------|-------------------------------------------------------------------------------------------|-----------|
+| drb-ID | DRB-ID, | |
+| sN-UL-PDCP-UP-TNLInfo | UPTransportParameters, | |
+| dRB-QoS | QoSFlowLevelQoSParameters, | |
+| pDCP-SNLength | PDCPSNLength | OPTIONAL, |
+| rLC-Mode | RLCMode, | |
+| uL-Configuration | ULConfiguration | OPTIONAL, |
+| secondary-SN-UL-PDCP-UP-TNLInfo | UPTransportParameters | OPTIONAL, |
+| duplicationActivation | DuplicationActivation | OPTIONAL, |
+| qoSFlowsMappedtoDRB-SetupResponse-SNterminated | QoSFlowsMappedtoDRB-SetupResponse-SNterminated, | |
+| iE-Extensions | ProtocolExtensionContainer { {DRBsToBeSetupList-SetupResponse-SNterminated-Item-ExtIEs} } | OPTIONAL, |
+| ... | | |
+
+}
+
+DRBsToBeSetupList-SetupResponse-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+| | | | |
+|----------------------------------------------|--------------------|------------------------------------------------|---------------------|
+| { ID id-Additional-PDCP-Duplication-TNL-List | CRITICALITY ignore | EXTENSION Additional-PDCP-Duplication-TNL-List | PRESENCE optional} |
+| { ID id-RLCDuplicationInformation | CRITICALITY ignore | EXTENSION RLCDuplicationInformation | PRESENCE optional}, |
+| ... | | | |
+
+}
+
+```
+
+QoSFlowsMappedtoDRB-SetupResponse-SNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF
+ QoSFlowsMappedtoDRB-SetupResponse-SNterminated-Item
+
+QoSFlowsMappedtoDRB-SetupResponse-SNterminated-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ mCGRequestedGBRQoSFlowInfo GBRQoSFlowInfo OPTIONAL,
+ qosFlowMappingIndication QoSFlowMappingIndication OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { (QoSFlowsMappedtoDRB-SetupResponse-SNterminated-Item-ExtIEs) } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+QoSFlowsMappedtoDRB-SetupResponse-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetIndex PRESENCE optional }|
+ { ID id-SourceDLForwardingIPAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Setup Info - MN terminated
+--
+
+```
+
+-- \*\*\*\*\*
+
+```
+PDUSessionResourceSetupInfo-MNterminated ::= SEQUENCE {
+ pduSessionType PDUSessionType,
+ dRBsToBeSetup DRBsToBeSetupList-Setup-MNterminated,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+PDUSessionResourceSetupInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+DRBsToBeSetupList-Setup-MNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToBeSetupList-Setup-MNterminated-Item
+```
+
+```
+DRBsToBeSetupList-Setup-MNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ mN-UL-PDCP-UP-TNLInfo UPTransportParameters,
+ rLC-Mode RLCMode,
+ uL-Configuration ULConfiguration OPTIONAL,
+ dRB-QoS QoSFlowLevelQoSParameters,
+ pDCP-SNLength PDCPSNLength OPTIONAL,
+```
+
+```
+
+secondary-MN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+duplicationActivation DuplicationActivation OPTIONAL,
+qoSFlowsMappedtoDRB-Setup-MNterminated QoSFlowsMappedtoDRB-Setup-MNterminated,
+iE-Extensions ProtocolExtensionContainer { {DRBsToBeSetupList-Setup-MNterminated-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+DRBsToBeSetupList-Setup-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional}|
+ { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional},
+ ...
+}
+
+QoSFlowsMappedtoDRB-Setup-MNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsMappedtoDRB-Setup-MNterminated-Item
+
+QoSFlowsMappedtoDRB-Setup-MNterminated-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ qosFlowLevelQoSParameters QoSFlowLevelQoSParameters,
+ qosFlowMappingIndication QoSFlowMappingIndication OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowsMappedtoDRB-Setup-MNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+QoSFlowsMappedtoDRB-Setup-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- PDU Session Resource Setup Response Info - MN terminated
+--
+-- *****
+
+PDUSessionResourceSetupResponseInfo-MNterminated ::= SEQUENCE {
+ dRBsAdmittedList dRBsAdmittedList-SetupResponse-MNterminated,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceSetupResponseInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceSetupResponseInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DRBsNotAdmittedSetupModifyList CRITICALITY ignore EXTENSION DRB-List-withCause PRESENCE optional},
+ ...
+}
+```
+
+DRBsAdmittedList-SetupResponse-MNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsAdmittedList-SetupResponse-MNterminated-Item
+
+DRBsAdmittedList-SetupResponse-MNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ sN-DL-SCG-UP-TNLInfo UPTransportParameters,
+ secondary-SN-DL-SCG-UP-TNLInfo UPTransportParameters OPTIONAL,
+ LCID LCID OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {DRBsAdmittedList-SetupResponse-MNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DRBsAdmittedList-SetupResponse-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional}|
+ { ID id-QoSFlowsMappedtoDRB-SetupResponse-MNterminated CRITICALITY ignore EXTENSION QoSFlowsMappedtoDRB-SetupResponse-MNterminated PRESENCE optional},
+ ...
+}
+
+QoSFlowsMappedtoDRB-SetupResponse-MNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsMappedtoDRB-SetupResponse-MNterminated-Item
+
+QoSFlowsMappedtoDRB-SetupResponse-MNterminated-Item ::= SEQUENCE {
+ qoSFlowIdentifier QoSFlowIdentifier,
+ currentQoSParaSetIndex QoSParaSetIndex,
+
+```
+
+iE-Extensions ProtocolExtensionContainer { {QoSFlowsMappedtoDRB-SetupResponse-MNterminated-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+```
+
+```
+
+QoSFlowsMappedtoDRB-SetupResponse-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Modification Info - SN terminated
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourceModificationInfo-SNterminated ::= SEQUENCE {
+ uL-NG-U-TNLatUPF UPTransportLayerInformation OPTIONAL,
+ pduSessionNetworkInstance PDUSessionNetworkInstance OPTIONAL,
+ qosFlowsToBeSetup-List QoSFlowsToBeSetup-List-Setup-SNterminated OPTIONAL,
+ dataforwardinginfromSource DataforwardingandOffloadingInfromSource OPTIONAL,
+ qosFlowsToBeModified-List QoSFlowsToBeSetup-List-Modified-SNterminated OPTIONAL,
+ qosFlowsToBeReleased-List QoSFlows-List-withCause OPTIONAL,
+}
+
+```
+
+```
+
+drbsToBeModifiedList DRBsToBeModified-List-Modified-SNterminated OPTIONAL,
+dRBsToBeReleased DRB-List-withCause OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { PDUSessionResourceModificationInfo-SNterminated-ExtIEs } OPTIONAL,
+...
+}
+
+```
+
+```
+
+PDUSessionResourceModificationInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-PDUSessionCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional}|
+ { ID id-DefaultDRB-Allowed CRITICALITY ignore EXTENSION DefaultDRB-Allowed PRESENCE optional}|
+ { ID id-NonGBRResources-Offered CRITICALITY ignore EXTENSION NonGBRResources-Offered PRESENCE optional}|
+ { ID id-Redundant-UL-NG-U-TNLatUPF CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional}|
+ { ID id-RedundantCommonNetworkInstance CRITICALITY ignore EXTENSION PDUSessionCommonNetworkInstance PRESENCE optional}|
+ { ID id-SecurityIndication CRITICALITY ignore EXTENSION SecurityIndication PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+QoSFlowsToBeSetup-List-Modified-SNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsToBeSetup-List-Modified-SNterminated-Item
+
+```
+
+```
+
+QoSFlowsToBeSetup-List-Modified-SNterminated-Item ::= SEQUENCE {
+ qfi QoSFlowIdentifier,
+ qosFlowLevelQoSParameters QoSFlowLevelQoSParameters OPTIONAL,
+ offeredGBRQoSFlowInfo GBRQoSFlowInfo OPTIONAL,
+ qosFlowMappingIndication QoSFlowMappingIndication OPTIONAL,
+}
+
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowsToBeSetup-List-Modified-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+QoSFlowsToBeSetup-List-Modified-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional}|
+ { ID id-RedundantQoSFlowIndicator CRITICALITY ignore EXTENSION RedundantQoSFlowIndicator PRESENCE optional},
+ ...
+}
+```
+
+```
+DRBsToBeModified-List-Modified-SNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToBeModified-List-Modified-SNterminated-Item
+```
+
+```
+DRBsToBeModified-List-Modified-SNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ mN-DL-SCG-UP-TNLInfo UPTransportParameters OPTIONAL,
+ secondary-MN-DL-SCG-UP-TNLInfo UPTransportParameters OPTIONAL,
+ LCID LCID OPTIONAL,
+ rlc-status RLC-Status OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {DRBsToBeModified-List-Modified-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+DRBsToBeModified-List-Modified-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional},
+ ...
+}
+
+```
+
+-- \*\*\*\*\*
+
+--
+
+-- PDU Session Resource Modification Response Info - SN terminated
+
+--
+
+-- \*\*\*\*\*
+
+```
+
+PDUSessionResourceModificationResponseInfo-SNterminated ::= SEQUENCE {
+ dL-NG-U-TNLatNG-RAN UPTransportLayerInformation OPTIONAL,
+ dRBsToBeSetup DRBsToBeSetupList-SetupResponse-SNterminated OPTIONAL,
+ dataforwardinginfoTarget DataForwardingInfoFromTargetNGRANnode OPTIONAL,
+ dRBsToBeModified DRBsToBeModifiedList-ModificationResponse-SNterminated OPTIONAL,
+ dRBsToBeReleased DRB-List-withCause OPTIONAL,
+ dataforwardinginfofromSource DataforwardingandOffloadingInfofromSource OPTIONAL,
+ qosFlowsNotAdmittedTBAAdded QoSFlows-List-withCause OPTIONAL,
+ qosFlowsReleased QoSFlows-List-withCause OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModificationResponseInfo-SNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourceModificationResponseInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DRB-IDs-takenintouse CRITICALITY reject EXTENSION DRB-List PRESENCE optional}|
+ { ID id-Redundant-DL-NG-U-TNLatNG-RAN CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional}|
+ { ID id-SecurityResult CRITICALITY ignore EXTENSION SecurityResult PRESENCE optional},
+ ...
+}
+
+DRBsToBeModifiedList-ModificationResponse-SNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF
+ DRBsToBeModifiedList-ModificationResponse-SNterminated-Item
+
+DRBsToBeModifiedList-ModificationResponse-SNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ sN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+ dRB-QoS QoSFlowLevelQoSParameters OPTIONAL,
+ qosFlowsMappedtoDRB-SetupResponse-SNterminated QoSFlowsMappedtoDRB-SetupResponse-SNterminated OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { DRBsToBeModifiedList-ModificationResponse-SNterminated-Item-ExtIEs } OPTIONAL,
+ ...
+}
+
+DRBsToBeModifiedList-ModificationResponse-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional}|
+ { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional}|
+}
+
+```
+
+```
+
+ { ID id-secondary-SN-UL-PDCP-UP-TNLInfo CRITICALITY ignore EXTENSION UPTransportParameters PRESENCE optional}|
+ { ID id-pdcpDuplicationConfiguration CRITICALITY ignore EXTENSION PDCPDuplicationConfiguration PRESENCE optional}|
+ { ID id-duplicationActivation CRITICALITY ignore EXTENSION DuplicationActivation PRESENCE optional},
+ ...
+}
+
+```
+
+```
+-- *****
+```
+
+```
+--
+```
+
+```
+-- PDU Session Resource Modification Info - MN terminated
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+PDUSessionResourceModificationInfo-MNterminated ::= SEQUENCE {
+```
+
+```
+
+ pduSessionType PDUSessionType,
+ dRBsToBeSetup DRBsToBeSetupList-Setup-MNterminated OPTIONAL,
+ dRBsToBeModified DRBsToBeModifiedList-Modification-MNterminated OPTIONAL,
+ dRBsToBeReleased DRB-List-withCause OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModificationInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+PDUSessionResourceModificationInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+DRBsToBeModifiedList-Modification-MNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF
+```
+
+```
+ DRBsToBeModifiedList-Modification-MNterminated-Item
+```
+
+```
+DRBsToBeModifiedList-Modification-MNterminated-Item ::= SEQUENCE {
+```
+
+```
+ drb-ID DRB-ID,
+```
+
+```
+ mN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+```
+
+```
+ dRB-QoS QoSFlowLevelQoSParameters OPTIONAL,
+```
+
+```
+ secondary-MN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+```
+
+```
+ uL-Configuration ULConfiguration OPTIONAL,
+```
+
+```
+ pdcpDuplicationConfiguration PDCPDuplicationConfiguration OPTIONAL,
+```
+
+```
+ duplicationActivation DuplicationActivation OPTIONAL,
+```
+
+```
+ qosFlowsMappedtoDRB-Setup-MNterminated QoSFlowsMappedtoDRB-Setup-MNterminated OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { DRBsToBeModifiedList-Modification-MNterminated-Item-ExtIEs } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+DRBsToBeModifiedList-Modification-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional } |
+```
+
+```
+ { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional },
+```
+
+```
+...
+}
+
+-- *****
+--
+-- PDU Session Resource Modification Response Info - MN terminated
+--
+-- *****
+
+PDUSessionResourceModificationResponseInfo-MNterminated ::= SEQUENCE {
+ dRBsAdmittedList dRBsAdmittedList-ModificationResponse-MNterminated,
+ dRBsReleasedList dRB-List OPTIONAL,
+ dRBsNotAdmittedSetupModifyList dRB-List-withCause OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModificationResponseInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceModificationResponseInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+DRBsAdmittedList-ModificationResponse-MNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsAdmittedList-ModificationResponse-MNterminated-Item
+
+DRBsAdmittedList-ModificationResponse-MNterminated-Item ::= SEQUENCE {
+
+drb-ID DRB-ID,
+sN-DL-SCG-UP-TNLInfo UPTransportParameters OPTIONAL,
+secondary-SN-DL-SCG-UP-TNLInfo UPTransportParameters OPTIONAL,
+LCID LCID OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { DRBsAdmittedList-ModificationResponse-MNterminated-Item-ExtIEs } OPTIONAL,
+
+... }
+
+DRBsAdmittedList-ModificationResponse-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+{ ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional}|
+
+{ ID id-QoSFlowsMappedtoDRB-SetupResponse-MNterminated CRITICALITY ignore EXTENSION QoSFlowsMappedtoDRB-SetupResponse-MNterminated PRESENCE optional},
+
+... }
+
+-- \*\*\*\*\*
+--
+-- PDU Session Resource Change Required Info - SN terminated
+--
+-- \*\*\*\*\*
+
+```
+
+PDUSessionResourceChangeRequiredInfo-SNterminated ::= SEQUENCE {
+ dataforwardinginfromSource DataforwardingandOffloadingInfromSource OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceChangeRequiredInfo-SNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourceChangeRequiredInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Change Confirm Info - SN terminated
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourceChangeConfirmInfo-SNterminated ::= SEQUENCE {
+ dataforwardinginfromTarget DataForwardingInfoFromTargetNGRANnode OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceChangeConfirmInfo-SNterminated-ExtIEs} } OPTIONAL,
+
+```
+
+...
+}
+
+PDUSessionResourceChangeConfirmInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DRB-IDs-takenintouse CRITICALITY reject EXTENSION DRB-List PRESENCE optional},
+ ...
+}
+
+-- \*\*\*\*\*
+--
+-- PDU Session Resource Change Required Info - MN terminated
+--
+-- \*\*\*\*\*
+
+PDUSessionResourceChangeRequiredInfo-MNterminated ::= SEQUENCE {
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceChangeRequiredInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceChangeRequiredInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+}
+
+-- *****
+--
+-- PDU Session Resource Change Confirm Info - MN terminated
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourceChangeConfirmInfo-MNterminated ::= SEQUENCE {
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceChangeConfirmInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourceChangeConfirmInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Modification Required Info - SN terminated
+
+```
+
+```
+
+--
+-- *****
+
+PDUSessionResourceModRqdInfo-SNterminated ::= SEQUENCE {
+ dL-NG-U-TNLatNG-RAN UPTransportLayerInformation OPTIONAL,
+ qosFlowsToBeReleased-List QoSFlows-List-withCause OPTIONAL,
+ dataforwardinginfromSource DataforwardingandOffloadingInfromSource OPTIONAL,
+ drbsToBeSetupList DRBsToBeSetup-List-ModRqd-SNterminated OPTIONAL,
+ drbsToBeModifiedList DRBsToBeModified-List-ModRqd-SNterminated OPTIONAL,
+ dRBsToBeReleased DRB-List-withCause OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModRqdInfo-SNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceModRqdInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DRBsToBeSetup-List-ModRqd-SNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToBeSetup-List-ModRqd-SNterminated-Item
+
+DRBsToBeSetup-List-ModRqd-SNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+
+```
+
+```
+
+ pDCP-SNLength PDCPSNLength OPTIONAL,
+ sn-UL-PDCP-UPTNLInfo UPTransportParameters,
+ dRB-QoS QoSFlowLevelQoSParameters,
+ secondary-SN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+ duplicationActivation DuplicationActivation OPTIONAL,
+ uL-Configuration ULConfiguration OPTIONAL,
+ qosFlowsMappedtoDRB-ModRqd-SNterminated QoSFlowsSetupMappedtoDRB-ModRqd-SNterminated,
+ rLC-Mode RLCMode,
+ iE-Extensions ProtocolExtensionContainer { {DRBsToBeSetup-List-ModRqd-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+DRBsToBeSetup-List-ModRqd-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional}|
+ { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLC Duplication Information PRESENCE optional},
+ ...
+}
+
+QoSFlowsSetupMappedtoDRB-ModRqd-SNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF
+ QoSFlowsSetupMappedtoDRB-ModRqd-SNterminated-Item
+
+QoSFlowsSetupMappedtoDRB-ModRqd-SNterminated-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+
+```
+
+```
+
+mCGRequestedGBRQoSFlowInfo GBRQoSFlowInfo OPTIONAL,
+iE-Extensions ProtocolExtensionContainer { (QoSFlowsSetupMappedtoDRB-ModRqd-SNterminated-Item-ExtIEs) } OPTIONAL,
+...
+}
+
+QoSFlowsSetupMappedtoDRB-ModRqd-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-QoSFlowMappingIndication CRITICALITY ignore EXTENSION QoSFlowMappingIndication PRESENCE optional},
+ ...
+}
+
+DRBsToBeModified-List-ModRqd-SNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToBeModified-List-ModRqd-SNterminated-Item
+
+DRBsToBeModified-List-ModRqd-SNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ sN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+ dRB-QoS QoSFlowLevelQoSParameters OPTIONAL,
+ secondary-SN-UL-PDCP-UP-TNLInfo UPTransportParameters OPTIONAL,
+ uL-Configuration ULConfiguration OPTIONAL,
+ pdcpDuplicationConfiguration PDCPDuplicationConfiguration OPTIONAL,
+ duplicationActivation DuplicationActivation OPTIONAL,
+ qoSFlowsMappedtoDRB-ModRqd-SNterminated QoSFlowsModifiedMappedtoDRB-ModRqd-SNterminated OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { (DRBsToBeModified-List-ModRqd-SNterminated-Item-ExtIEs) } OPTIONAL,
+ ...
+}
+
+```
+
+```
+}
+
+DRBsToBeModified-List-ModRqd-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional}|
+ { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional},
+ ...
+}
+
+QoSFlowsModifiedMappedtoDRB-ModRqd-SNterminated ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF
+ QoSFlowsModifiedMappedtoDRB-ModRqd-SNterminated-Item
+
+QoSFlowsModifiedMappedtoDRB-ModRqd-SNterminated-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ mCGRequestedGBRQoSFlowInfo GBRQoSFlowInfo OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { QoSFlowsModifiedMappedtoDRB-ModRqd-SNterminated-Item-ExtIEs } OPTIONAL,
+ ...
+}
+
+QoSFlowsModifiedMappedtoDRB-ModRqd-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-QoSFlowMappingIndication CRITICALITY ignore EXTENSION QoSFlowMappingIndication PRESENCE optional},
+ ...
+}
+```
+
+```
+
+-- *****
+--
+-- PDU Session Resource Modification Confirm Info - SN terminated
+--
+-- *****
+
+```
+
+```
+
+PDUSessionResourceModConfirmInfo-SNterminated ::= SEQUENCE {
+ uL-NG-U-TNLatUPF UPTransportLayerInformation OPTIONAL,
+ dRBsAdmittedList dRBsAdmittedList-ModConfirm-SNterminated,
+ dRBsNotAdmittedSetupModifyList dRB-List-withCause OPTIONAL,
+ dataforwardinginfoTarget DataForwardingInfoFromTargetNGRANnode OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModConfirmInfo-SNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+PDUSessionResourceModConfirmInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DRB-IDs-takenintouse CRITICALITY reject EXTENSION dRB-List PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+dRBsAdmittedList-ModConfirm-SNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF
+
+```
+
+DRBsAdmittedList-ModConfirm-SNterminated-Item
+
+```
+
+DRBsAdmittedList-ModConfirm-SNterminated-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ mN-DL-CG-UP-TNLInfo UPTransportParameters OPTIONAL,
+ secondary-MN-DL-CG-UP-TNLInfo UPTransportParameters OPTIONAL,
+ lCID LCID OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {DRBsAdmittedList-ModConfirm-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+DRBsAdmittedList-ModConfirm-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+-- **************************************************************
+--
+-- PDU Session Resource Modification Required Info - MN terminated
+--
+-- **************************************************************
+
+```
+
+```
+PDUSessionResourceModRqdInfo-MNterminated ::= SEQUENCE {
+ dRBsToBeModified dRBsToBeModified-List-ModRqd-MNterminated OPTIONAL,
+ dRBsToBeReleased dRB-List-withCause OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceModRqdInfo-MNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceModRqdInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+dRBsToBeModified-List-ModRqd-MNterminated ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF dRBsToBeModified-List-ModRqd-MNterminated-Item
+
+dRBsToBeModified-List-ModRqd-MNterminated-Item ::= SEQUENCE {
+ drb-ID dRB-ID,
+ sN-DL-SCG-UP-TNLInfo UPTransportLayerInformation,
+ secondary-SN-DL-SCG-UP-TNLInfo UPTransportLayerInformation OPTIONAL,
+ lCID lCID OPTIONAL,
+ rlc-status RLC-Status OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {dRBsToBeModified-List-ModRqd-MNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+}
+
+DRBsToBeModified-List-ModRqd-MNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+{ ID id-Additional-PDCP-Duplication-TNL-List CRITICALITY ignore EXTENSION Additional-PDCP-Duplication-TNL-List PRESENCE optional},
+...
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- PDU Session Resource Modification Confirm Info - MN terminated
+
+--
+
+-- \*\*\*\*\*
+
+PDUSSessionResourceModConfirmInfo-MNterminated ::= SEQUENCE {
+
+iE-Extensions ProtocolExtensionContainer { PDUSSessionResourceModConfirmInfo-MNterminated-ExtIEs } OPTIONAL,
+...
+
+}
+
+PDUSSessionResourceModConfirmInfo-MNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+```
+-- *****
+--
+-- PDU Session Resource Setup Complete Info - SN terminated
+--
+-- *****
+
+PDUSessionResourceBearerSetupCompleteInfo-SNterminated ::= SEQUENCE {
+ dRBsToBeSetupList SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBsToBeSetupList-BearerSetupComplete-SNterminated-Item,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionResourceBearerSetupCompleteInfo-SNterminated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceBearerSetupCompleteInfo-SNterminated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+DRBsToBeSetupList-BearerSetupComplete-SNterminated-Item ::= SEQUENCE {
+ dRB-ID DRB-ID,
+ mN-Xn-U-TNLInfoatM UPTransportLayerInformation,
+ iE-Extensions ProtocolExtensionContainer { {DRBsToBeSetupList-BearerSetupComplete-SNterminated-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+
+}
+
+DRBsToBeSetupList-BearerSetupComplete-SNterminated-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-Secondary-MN-Xn-U-TNLInfoatM CRITICALITY ignore EXTENSION UPTransportLayerInformation PRESENCE optional},
+ ...
+}
+
+-- *****
+--
+-- PDU Session related message level IEs END
+--
+-- *****
+
+PDUSessionResourceSecondaryRATUsageList ::= SEQUENCE (SIZE(1..maxnoofPDUSessions)) OF PDUSessionResourceSecondaryRATUsageItem
+
+PDUSessionResourceSecondaryRATUsageItem ::= SEQUENCE {
+ pDUSessionID PDUSession-ID,
+ secondaryRATUsageInformation SecondaryRATUsageInformation,
+ iE-Extensions ProtocolExtensionContainer { PDUSessionResourceSecondaryRATUsageItem-ExtIEs } OPTIONAL,
+ ...
+}
+
+PDUSessionResourceSecondaryRATUsageItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+
+```
+...
+}
+
+PDUSessionUsageReport ::= SEQUENCE {
+ rATType ENUMERATED {nr, eutra, ..., nr-unlicensed, e-utra-unlicensed},
+ pDUSessionTimedReportList VolumeTimedReportList,
+ iE-Extensions ProtocolExtensionContainer { {PDUSessionUsageReport-ExtIEs} } OPTIONAL,
+...
+}
+
+PDUSessionUsageReport-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+PDUSessionType ::= ENUMERATED {ipv4, ipv6, ipv4v6, ethernet, unstructured, ...}
+
+PDUSession-ID ::= INTEGER (0..255)
+
+PDUSessionNetworkInstance ::= INTEGER (1..256, ...)
+
+PDUSessionCommonNetworkInstance ::= OCTET STRING
+
+PDUSession-PairID ::= INTEGER (0..255, ...)
+```
+
+```
+Periodical ::= SEQUENCE {
+ iE-Extensions ProtocolExtensionContainer { { Periodical-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Periodical-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Permutation ::= ENUMERATED {dfu, ufd, ...}
+
+PLMN-Identity ::= OCTET STRING (SIZE(3))
+
+PLMNAreaBasedQMC ::= SEQUENCE {
+ plmnListforQMC PLMNListforQMC,
+ iE-Extensions ProtocolExtensionContainer { { PLMNAreaBasedQMC-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PLMNAreaBasedQMC-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+PLMNListforQMC ::= SEQUENCE (SIZE(1..maxnoofPLMNforQMC)) OF PLMN-Identity
+
+PCIListForMDT ::= SEQUENCE (SIZE(1.. maxnoofNeighPCIforMDT)) OF NRPCI
+
+PNI-NPN-Restricted-Information ::= ENUMERATED { restricted, not-restricted, ...}
+
+PortNumber ::= BIT STRING (SIZE (16))
+
+PosPartialUEContextInfo ::= SEQUENCE {
+ requestedSRSTransmissionCharacteristics RequestedSRSTransmissionCharacteristics OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { PosPartialUEContextInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PosPartialUEContextInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+PredictedUETrajectory-Item ::= SEQUENCE{
+ predictedTrajectoryCellInfo PredictedTrajectoryCellInfo,
+ iE-Extensions ProtocolExtensionContainer { { PredictedUETrajectory-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PredictedUETrajectory-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PredictedTrajectoryCellInfo ::= CHOICE {
+ nG-RAN-Cell-Predicted PredictedTrajectoryNGRANCellInfo,
+ choice-extension ProtocolIE-Single-Container { { PredictedTrajectoryCellInfo-ExtIEs} }
+}
+
+PredictedTrajectoryCellInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+PredictedTrajectoryNGRANCellInfo ::= SEQUENCE {
+ globalNG-RANCell-ID GlobalNG-RANCell-ID,
+ predictedTimeUEStaysInCell INTEGER (0..4095) OPTIONAL,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { { PredictedTrajectoryNGRANCellInfo-ExtIEs } } OPTIONAL,
+...
+}
+
+PredictedTrajectoryNGRANCellInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+PriorityLevelQoS ::= INTEGER (1..127, ...)
+
+ProtectedE-UTRAResourceIndication ::= SEQUENCE {
+ activationSFN ActivationSFN,
+ protectedResourceList ProtectedE-UTRAResourceList,
+ mbsfnControlRegionLength MBSFNControlRegionLength OPTIONAL,
+ pDCCHRegionLength INTEGER (1..3),
+ iE-Extensions ProtocolExtensionContainer { { ProtectedE-UTRAResourceIndication-ExtIEs } } OPTIONAL,
+ ...
+}
+
+ProtectedE-UTRAResourceIndication-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+...
+}
+
+ProtectedE-UTRAResourceList ::= SEQUENCE (SIZE (1.. maxnoofProtectedResourcePatterns)) OF ProtectedE-UTRAResource-Item
+
+ProtectedE-UTRAResource-Item ::= SEQUENCE {
+ resourceType ENUMERATED {downlinknonCRS, cRS, uplink, ...},
+ intra-PRBProtectedResourceFootprint BIT STRING (SIZE(84, ...)),
+ protectedFootprintFrequencyPattern BIT STRING (SIZE(6..110, ...)),
+ protectedFootprintTimePattern ProtectedE-UTRAFootprintTimePattern,
+ iE-Extensions ProtocolExtensionContainer { {ProtectedE-UTRAResource-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ProtectedE-UTRAResource-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ProtectedE-UTRAFootprintTimePattern ::= SEQUENCE {
+ protectedFootprintTimeperiodicity INTEGER (1..320, ...),
+ protectedFootprintStartTime INTEGER (1..20, ...),
+ iE-Extensions ProtocolExtensionContainer { {ProtectedE-UTRAFootprintTimePattern-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+}
+
+ProtectedE-UTRAFootprintTimePattern-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+PrivacyIndicator ::= ENUMERATED {
+ immediate-MDT,
+ logged-MDT,
+ ...
+}
+
+PSCellChangeHistory ::= ENUMERATED {reporting-full-history, ...}
+
+PSCellHistoryInformationRetrieve ::= ENUMERATED {query, ...}
+
+PSCellListContainer ::= OCTET STRING
+
+PNI-NPNBasedMDT ::= SEQUENCE (SIZE(1..maxnoofCAGforMDT)) OF PNI-NPNBasedMDT-Item
+
+PNI-NPN-AreaScopeofMDT ::= SEQUENCE (SIZE(1..maxnoofCAGforMDT)) OF CAGListforMDT
+```
+
+```
+PNI-NPNBasedMDT-Item ::= SEQUENCE {
+ plmnID PLMN-Identity,
+ cAGID CAG-Identifier,
+ iE-Extensions ProtocolExtensionContainer { {PNI-NPNBasedMDT-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+PNI-NPNBasedMDT-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- Q
+
+QMConfigInfo ::= SEQUENCE {
+ uEAppLayerMeasInfoList UEAppLayerMeasInfoList,
+ iE-Extensions ProtocolExtensionContainer { {QMConfigInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QMConfigInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+UEAppLayerMeasInfoList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF UEAppLayerMeasInfo-Item
+
+UEAppLayerMeasInfo-Item ::= SEQUENCE {
+ uEAppLayerMeasConfigInfo UEAppLayerMeasConfigInfo,
+ iE-Extensions ProtocolExtensionContainer { { UEAppLayerMeasInfo-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UEAppLayerMeasInfo-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+QMCCoordinationRequest ::= SEQUENCE {
+ mN-to-SN-QMCCoordRequestList MN-to-SN-QMCCoordRequestList,
+ sN-to-MN-QMCCoordRequestList SN-to-MN-QMCCoordRequestList,
+ iE-Extensions ProtocolExtensionContainer { {QMCCoordinationRequest-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QMCCoordinationRequest-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+
+ ...
+}
+
+MN-to-SN-QMCCoordRequestList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF MN-to-SN-QMCCoordRequestList-Item
+
+MN-to-SN-QMCCoordRequestList-Item ::= SEQUENCE {
+ qOEReference QOEReference,
+ qOEMeasConfigAppLayerID QOEMeasConfAppLayerID OPTIONAL,
+ measCollectionEntityIPAddress MeasCollectionEntityIPAddress OPTIONAL,
+ qoEReportingPathRequest ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ rVQoEReportingPathRequest ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ furtherRVQoEInterestInquiry ENUMERATED{true, ...} OPTIONAL,
+ furtherRVQoEReportingPath ENUMERATED{true, ...} OPTIONAL,
+ currentRVQoEConfig RVQoEConfig OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { MN-to-SN-QMCCoordRequestList-Item-ExtIEs } OPTIONAL,
+ ...
+}
+
+MN-to-SN-QMCCoordRequestList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+SN-to-MN-QMCCoordRequestList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF SN-to-MN-QMCCoordRequestList-Item
+```
+
+```
+SN-to-MN-QMCCoordRequestList-Item ::= SEQUENCE {
+ qOEReference QOEReference,
+ measCollectionEntityIPAddress MeasCollectionEntityIPAddress OPTIONAL,
+ qoEReportingPathRequest ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ rVQoEReportingPathRequest ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ furtherRVQoEInterestInquiry ENUMERATED{true, ...} OPTIONAL,
+ furtherRVQoEReportingPath ENUMERATED{true, ...} OPTIONAL,
+ currentRVQoEConfig RVQoEConfig OPTIONAL,
+ configReleaseIndication ENUMERATED{true, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { SN-to-MN-QMCCoordRequestList-Item-ExtIEs } OPTIONAL,
+ ...
+}
+```
+
+```
+SN-to-MN-QMCCoordRequestList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+QMCCoordinationResponse ::= SEQUENCE {
+```
+
+```
+
+ mN-to-SN-QMCCoordResponseList MN-to-SN-QMCCoordResponseList,
+ sN-to-MN-QMCCoordResponseList SN-to-MN-QMCCoordResponseList,
+ iE-Extensions ProtocolExtensionContainer { {QMCCoordinationResponse-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QMCCoordinationResponse-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+MN-to-SN-QMCCoordResponseList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF MN-to-SN-QMCCoordResponseList-Item
+
+MN-to-SN-QMCCoordResponseList-Item ::= SEQUENCE {
+ qOEReference QOEReference,
+ qOEMeasConfigAppLayerID QOEMeasConfAppLayerID OPTIONAL,
+ qoEConfigSendingPath ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ qoEReportingPathResponse ENUMERATED{accepted, rejected, ...} OPTIONAL,
+ rVQoEReportingPathResponse ENUMERATED{accepted, rejected, ...} OPTIONAL,
+ furtherRVQoEInterestResponse ENUMERATED{interested, not-interested, ...} OPTIONAL,
+ furtherRVQoEReportingPath ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ preferredRVQoEConfig RVQoEConfig OPTIONAL,
+}
+
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { MN-to-SN-QMCCoordResponseList-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+MN-to-SN-QMCCoordResponseList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SN-to-MN-QMCCoordResponseList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF SN-to-MN-QMCCoordResponseList-Item
+
+SN-to-MN-QMCCoordResponseList-Item ::= SEQUENCE {
+ qOEReference QOEReference,
+ qoEReportingPathResponse ENUMERATED{accepted, rejected, ...} OPTIONAL,
+ rVQoEReportingPathResponse ENUMERATED{accepted, rejected, ...} OPTIONAL,
+ furtherRVQoEInterestResponse ENUMERATED{rvqoe-reports-desired, rvqoe-reports-not-desired, ...} OPTIONAL,
+ furtherRVQoEReportingPath ENUMERATED{srb4, srb5, ...} OPTIONAL,
+ preferredRVQoEConfig RVQoEConfig OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SN-to-MN-QMCCoordResponseList-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+SN-to-MN-QMCCoordResponseList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+SNRelatedQMCInfoAtMN ::= SEQUENCE {
+ sNRelatedQMCInfoAtMNList sNRelatedQMCInfoAtMNList,
+ iE-Extensions ProtocolExtensionContainer { {SNRelatedQMCInfoAtMN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SNRelatedQMCInfoAtMN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SNRelatedQMCInfoAtMNList ::= SEQUENCE (SIZE(1..maxnoofUEAppLayerMeas)) OF SNRelatedQMCInfoAtMNList-Item
+
+SNRelatedQMCInfoAtMNList-Item ::= SEQUENCE {
+ qOEReference OCTET STRING (SIZE(6)),
+ qoERVQoEReportingPaths QoERVQoEReportingPaths OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SNRelatedQMCInfoAtMNList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SNRelatedQMCInfoAtMNList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+QoERVQoEReportingPaths ::= SEQUENCE {
+```
+
+```
+ qoEReportingPath ENUMERATED{srb4, srb5, ...} OPTIONAL,
+```
+
+```
+ rVQoEReportingPath ENUMERATED{srb4, srb5, ...} OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {QoERVQoEReportingPaths-ExtIEs} },
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+QoERVQoEReportingPaths-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RVQoEConfig ::= SEQUENCE {
+```
+
+```
+ availableRANVisibleQoEMetrics AvailableRVQoEMetrics OPTIONAL,
+```
+
+```
+ reportingPeriodicity RVQoEReportingPeriodicity OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {RVQoEConfig-ExtIEs} },
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RVQoEConfig-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RVQoEReportingPeriodicity ::= ENUMERATED {
+```
+
+```
+ ms120,
+```
+
+```
+ ms240,
+```
+
+```
+ ms480,
+```
+
+```
+ ms640,
+```
+
+```
+ ms1024,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+QOEMeasConfAppLayerID ::= INTEGER (0..15, ...)
+```
+
+```
+QOEMeasStatus ::= ENUMERATED {ongoing, ...}
+```
+
+```
+QOEReference ::= OCTET STRING (SIZE (6))
+```
+
+```
+QoSCharacteristics ::= CHOICE {
+```
+
+```
+ non-dynamic NonDynamic5QIDescriptor,
+```
+
+```
+ dynamic Dynamic5QIDescriptor,
+```
+
+```
+choice-extension ProtocolIE-Single-Container { {QoSCharacteristics-ExtIEs} }
+}
+```
+
+```
+QoSCharacteristics-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+QoSFlowIdentifier ::= INTEGER (0..63, ...)
+```
+
+```
+QoSFlowLevelQoSParameters ::= SEQUENCE {
+ qos-characteristics QoSCharacteristics,
+ allocationAndRetentionPrio AllocationandRetentionPriority,
+ gBRQoSFlowInfo GBRQoSFlowInfo OPTIONAL,
+ reflectiveQoS ReflectiveQoSAttribute OPTIONAL,
+ additionalQoSflowInfo ENUMERATED {more-likely, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowLevelQoSParameters-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+QoSFlowLevelQoSParameters-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ {ID id-QoSMonitoringRequest CRITICALITY ignore EXTENSION QosMonitoringRequest PRESENCE optional}|
+```
+
+```
+{ID id-QosMonitoringReportingFrequency CRITICALITY ignore EXTENSION QosMonitoringReportingFrequency PRESENCE optional}|
+{ID id-QoSMonitoringDisabled CRITICALITY ignore EXTENSION QoSMonitoringDisabled PRESENCE optional}|
+{ID id-PDUSetQoSParameters CRITICALITY ignore EXTENSION PDUSetQoSParameters PRESENCE optional},
+...
+}
+```
+
+```
+QoSFlowMappingIndication ::= ENUMERATED {
+ ul,
+ dl,
+ ...
+}
+```
+
+```
+QoSFlowNotificationControlIndicationInfo ::= SEQUENCE (SIZE (1..maxnoofQoSFlows)) OF QoSFlowNotify-Item
+```
+
+```
+QoSFlowNotify-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ notificationInformation ENUMERATED {fulfilled, not-fulfilled, ...},
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowNotificationControlIndicationInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+QoSFlowNotificationControlIndicationInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetNotifyIndex PRESENCE optional },
+ ...
+}
+
+QoSFlows-List ::= SEQUENCE (SIZE (1..maxnoofQoSFlows)) OF QoSFlow-Item
+
+QoSFlow-Item ::= SEQUENCE {
+ qfi QoSFlowIdentifier,
+ qosFlowMappingIndication QoSFlowMappingIndication OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { QoSFlow-Item-ExtIEs } OPTIONAL,
+ ...
+}
+
+QoSFlow-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+QoSFlows-List-withCause ::= SEQUENCE (SIZE (1..maxnoofQoSFlows)) OF QoSFlowwithCause-Item
+
+QoSFlowwithCause-Item ::= SEQUENCE {
+```
+
+```
+ qfi QoSFlowIdentifier,
+ cause Cause OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {QoSFlowwithCause-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoSFlowwithCause-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+QoS-Mapping-Information ::= SEQUENCE {
+ dscp BIT STRING (SIZE(6)) OPTIONAL,
+ flow-label BIT STRING (SIZE(20)) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {QoS-Mapping-Information-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoS-Mapping-Information-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+QoSParaSetIndex ::= INTEGER (1..8,...)
+
+QoSParaSetNotifyIndex ::= INTEGER (0..8,...)
+```
+
+QoSFlowsAdmitted-List ::= SEQUENCE (SIZE (1..maxnoofQoSFlows)) OF QoSFlowsAdmitted-Item
+
+QoSFlowsAdmitted-Item ::= SEQUENCE {
+ qfi QoSFlowIdentifier,
+ iE-Extension ProtocolExtensionContainer { {QoSFlowsAdmitted-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoSFlowsAdmitted-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetIndex PRESENCE optional },
+ ...
+}
+
+QoSFlowsToBeSetup-List ::= SEQUENCE (SIZE (1..maxnoofQoSFlows)) OF QoSFlowsToBeSetup-Item
+
+QoSFlowsToBeSetup-Item ::= SEQUENCE {
+ qfi QoSFlowIdentifier,
+ qoSFlowLevelQoSParameters QoSFlowLevelQoSParameters,
+ e-RAB-ID E-RAB-ID OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {QoSFlowsToBeSetup-Item-ExtIEs} } OPTIONAL,
+
+```
+...
+}
+
+QoSFlowsToBeSetup-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional}|
+ { ID id-RedundantQoSFlowIndicator CRITICALITY ignore EXTENSION RedundantQoSFlowIndicator PRESENCE optional},
+ ...
+}
+
+QoSFlowsUsageReportList ::= SEQUENCE (SIZE(1..maxnoofQoSFlows)) OF QoSFlowsUsageReport-Item
+
+QoSFlowsUsageReport-Item ::= SEQUENCE {
+ qosFlowIdentifier QoSFlowIdentifier,
+ RATType ENUMERATED {nr, eutra, ..., nr-unlicensed, e-utra-unlicensed},
+ qosFlowsTimedReportList VolumeTimedReportList,
+ iE-Extensions ProtocolExtensionContainer { {QoSFlowsUsageReport-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+QoSFlowsUsageReport-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+QosMonitoringRequest ::= ENUMERATED {ul, dl, both}
+
+QosMonitoringDisabled ::= ENUMERATED {true, ...}
+
+QosMonitoringReportingFrequency ::= INTEGER (1..1800, ...)
+
+-- R
+
+RACH-Config-Common ::= OCTET STRING
+
+RACH-Config-Common-IAB ::= OCTET STRING
+
+RAReport ::= SEQUENCE (SIZE(1.. maxnoofRAReports)) OF RAReportList-Item
+
+RAReportList-Item ::= SEQUENCE {
+
+ rAReport RAReportContainer,
+
+ iE-Extensions ProtocolExtensionContainer { { RAReportList-Item-ExtIEs} } OPTIONAL,
+
+ ...
+
+}
+
+RAReportList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ { ID id-UEAssistantIdentifier CRITICALITY ignore EXTENSION NG-RANnodeUEXnAPID PRESENCE optional}|
+
+ { ID id-PSCellListContainer CRITICALITY ignore EXTENSION PSCellListContainer PRESENCE optional},
+
+ ...
+
+}
+
+RAReportContainer ::= OCTET STRING
+
+RadioResourceStatus ::= CHOICE {
+ ng-eNB-RadioResourceStatus NG-eNB-RadioResourceStatus,
+ gNB-RadioResourceStatus GNB-RadioResourceStatus,
+ choice-extension ProtocolIE-Single-Container { { RadioResourceStatus-ExtIEs } }
+
+}
+
+RadioResourceStatus-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+RANAC ::= INTEGER (0..255)
+
+RANAreaID ::= SEQUENCE {
+ tAC TAC,
+ rANAC RANAC OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { RANAreaID-ExtIEs } } OPTIONAL,
+ ...
+}
+
+```
+}
+```
+
+```
+RANAreaID-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RANAreaID-List ::= SEQUENCE (SIZE(1..maxnoofRANAreasinRNA)) OF RANAreaID
+```
+
+```
+Range ::= ENUMERATED {m50, m80, m180, m200, m350, m400, m500, m700, m1000, ...}
+```
+
+```
+RANPagingArea ::= SEQUENCE {
+```
+
+```
+ pLMN-Identity PLMN-Identity,
+```
+
+```
+ rANPagingAreaChoice RANPagingAreaChoice,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { {RANPagingArea-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RANPagingArea-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RANPagingAreaChoice ::= CHOICE {
+```
+
+```
+cell-List NG-RAN-Cell-Identity-ListinRANPagingArea,
+rANAreaID-List RANAreaID-List,
+choice-extension ProtocolIE-Single-Container { {RANPagingAreaChoice-ExtIEs} }
+}
+
+RANPagingAreaChoice-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+RANPagingAttemptInfo ::= SEQUENCE {
+ pagingAttemptCount INTEGER (1..16, ...),
+ intendedNumberOfPagingAttempts INTEGER (1..16, ...),
+ nextPagingAreaScope ENUMERATED {same, changed, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RANPagingAttemptInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RANPagingAttemptInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RANPagingFailure ::= ENUMERATED {
+```
+
+```
+ true,
+ ...
+}
+
+RBsetConfiguration ::= SEQUENCE {
+ subcarrierSpacing SSB-subcarrierSpacing,
+ rBsetSize ENUMERATED {rb2, rb4, rb8, rb16, rb32, rb64},
+ numberOfRBsets INTEGER(1.. maxnoofRBsetsPerCell),
+ iE-Extensions ProtocolExtensionContainer { { RBsetConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RBsetConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Redcap-Bcast-Information ::= BIT STRING(SIZE(8))
+
+RedundantQoSFlowIndicator ::= ENUMERATED {true, false}
+
+RedundantPDUSessionInformation ::= SEQUENCE {
+ rSN RSN,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { {RedundantPDUSessionInformation-ExtIEs} } OPTIONAL,
+...
+}
+
+RedundantPDUSessionInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-PDUSession-PairID CRITICALITY ignore EXTENSION PDUSession-PairID PRESENCE optional },
+ ...
+}
+
+RSN ::= ENUMERATED {v1, v2, ...}
+
+ReflectiveQoSAttribute ::= ENUMERATED {subject-to-reflective-QoS, ...}
+
+RequestedSRSTransmissionCharacteristics ::= OCTET STRING
+
+RoutingID ::= OCTET STRING
+
+ReplacingCells ::= SEQUENCE (SIZE(0.. maxnoofCellsinNG-RANnode)) OF ReplacingCells-Item
+
+ReplacingCells-Item ::= SEQUENCE {
+ globalNG-RANCell-ID GlobalCell-ID,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { {ReplacingCells-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+ReplacingCells-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+ReportAmountMDT ::= ENUMERATED{r1, r2, r4, r8, r16, r32, r64, infinity, ...}
+
+ReportArea ::= ENUMERATED {
+cell,
+...
+}
+
+ReportConfigContainer ::= OCTET STRING
+
+ReportIntervalMDT ::= ENUMERATED {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60, ...}
+
+ReportType ::= CHOICE {
+periodical Periodical,
+eventTriggered EventTriggered,
+```
+
+```
+ ...
+ choice-extension ProtocolIE-Single-Container { {ReportType-ExtIEs} }
+}
+```
+
+```
+ReportType-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+ExtendedReportIntervalMDT ::= ENUMERATED {
+ ms20480,
+ ms40960,
+ ...
+}
+```
+
+```
+ReportCharacteristics ::= BIT STRING(SIZE(32))
+```
+
+```
+ReportingPeriodicity ::= ENUMERATED {
+ half-thousand-ms,
+ one-thousand-ms,
+ two-thousand-ms,
+```
+
+```
+ five-thousand-ms,
+ ten-thousand-ms,
+ ...
+}
+```
+
+```
+RequestedPredictionTime ::= INTEGER (0..60, ...)
+```
+
+```
+RegistrationRequest ::= ENUMERATED {start, stop, add, ... }
+```
+
+```
+RequestReferenceID ::= INTEGER (1..64, ...)
+```
+
+```
+ReservedSubframePattern ::= SEQUENCE {
+ subframeType ENUMERATED {mbsfn, non-mbsfn, ...},
+ reservedSubframePattern BIT STRING (SIZE(10..160)),
+ mbsfnControlRegionLength MBSFNControlRegionLength OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {ReservedSubframePattern-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ReservedSubframePattern-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+}
+
+```
+ResetRequestTypeInfo ::= CHOICE {
+ fullReset ResetRequestTypeInfo-Full,
+ partialReset ResetRequestTypeInfo-Partial,
+ choice-extension ProtocolIE-Single-Container { {ResetRequestTypeInfo-ExtIEs} }
+}
+```
+
+```
+ResetRequestTypeInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+ResetRequestTypeInfo-Full ::= SEQUENCE {
+ iE-Extension ProtocolExtensionContainer { {ResetRequestTypeInfo-Full-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ResetRequestTypeInfo-Full-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ResetRequestTypeInfo-Partial ::= SEQUENCE {
+ ue-contexts-ToBeReleasedList ResetRequestPartialReleaseList,
+ iE-Extension ProtocolExtensionContainer { {ResetRequestTypeInfo-Partial-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ResetRequestTypeInfo-Partial-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ResetRequestPartialReleaseList ::= SEQUENCE (SIZE(1..maxnoofUEContexts)) OF ResetRequestPartialReleaseItem
+
+ResetRequestPartialReleaseItem ::= SEQUENCE {
+ ng-ran-node1UEXnAPID NG-RANnodeUEXnAPID OPTIONAL,
+ ng-ran-node2UEXnAPID NG-RANnodeUEXnAPID OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ResetRequestPartialReleaseItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ResetRequestPartialReleaseItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+ResetResponseTypeInfo ::= CHOICE {
+ fullReset ResetResponseTypeInfo-Full,
+ partialReset ResetResponseTypeInfo-Partial,
+ choice-extension ProtocolIE-Single-Container { {ResetResponseTypeInfo-ExtIEs} }
+}
+
+ResetResponseTypeInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+ResetResponseTypeInfo-Full ::= SEQUENCE {
+ iE-Extension ProtocolExtensionContainer { {ResetResponseTypeInfo-Full-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ResetResponseTypeInfo-Full-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ResetResponseTypeInfo-Partial ::= SEQUENCE {
+ ue-contexts-AdmittedToBeReleasedList ResetResponsePartialReleaseList,
+ iE-Extension ProtocolExtensionContainer { {ResetResponseTypeInfo-Partial-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+}
+
+ResetResponseTypeInfo-Partial-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ResetResponsePartialReleaseList ::= SEQUENCE (SIZE(1..maxnoofUEContexts)) OF ResetResponsePartialReleaseItem
+
+ResetResponsePartialReleaseItem ::= SEQUENCE {
+ ng-ran-node1UEXnAPID NG-RANnodeUEXnAPID OPTIONAL,
+ ng-ran-node2UEXnAPID NG-RANnodeUEXnAPID OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ResetResponsePartialReleaseItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ResetResponsePartialReleaseItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RLCMode ::= ENUMERATED {
+ rlc-am,
+```
+
+```
+rlc-um-bidirectional,
+rlc-um-unidirectional-ul,
+rlc-um-unidirectional-dl,
+...
+}
+```
+
+```
+RLC-Status ::= SEQUENCE {
+ reestablishment-Indication Reestablishment-Indication,
+ iE-Extensions ProtocolExtensionContainer { {RLC-Status-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+RLC-Status-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+RLCDuplicationInformation ::= SEQUENCE {
+ rLCDuplicationStateList RLCDuplicationStateList,
+ rLC-PrimaryIndicator ENUMERATED {true, false} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {RLCDuplicationInformation-ItemExtIEs} } OPTIONAL
+}
+```
+
+```
+RLCDuplicationInformation-ItemExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RLCDuplicationStateList ::= SEQUENCE (SIZE(1..maxnoofRLCDuplicationstate)) OF RLCDuplicationState-Item
+
+RLCDuplicationState-Item ::= SEQUENCE {
+ duplicationState ENUMERATED {active,inactive, ...},
+ iE-Extensions ProtocolExtensionContainer { {RLCDuplicationState-ItemExtIEs} } OPTIONAL,
+ ...
+}
+
+RLCDuplicationState-ItemExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Reestablishment-Indication ::= ENUMERATED {
+ reestablished,
+ ...
+}
+
+RFSP-Index ::= INTEGER (1..256)
+```
+
+```
+RRRConfigIndication ::= ENUMERATED {
+ full-config,
+ delta-config,
+ ...
+}
+
+RRRConnections ::= SEQUENCE {
+ noofRRRConnections NoofRRRConnections,
+ availableRRRConnectionCapacityValue AvailableRRRConnectionCapacityValue,
+ iE-Extensions ProtocolExtensionContainer { { RRRConnections-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RRRConnections-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RRRConnReestab-Indicator ::= ENUMERATED { reconfigurationFailure, handoverFailure, otherFailure, ...}
+
+RRRReestab-initiated ::= SEQUENCE {
+```
+
+```
+rRRCReestab-initiated-reporting RRCReestab-Initiated-Reporting,
+iE-Extensions ProtocolExtensionContainer { { RRCReestab-initiated-ExtIEs} } OPTIONAL,
+...
+}
+
+RRCReestab-initiated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+RRCReestab-Initiated-Reporting ::= CHOICE {
+ rRCReestab-reporting-wo-UERLFRport RRCReestab-Initiated-Reporting-wo-UERLFRport,
+ rRCReestab-reporting-with-UERLFRport RRCReestab-Initiated-Reporting-with-UERLFRport,
+ choice-extension ProtocolIE-Single-Container { {RRCReestab-Initiated-Reporting-ExtIEs} }
+}
+
+RRCReestab-Initiated-Reporting-ExtIEs XNAP-PROTOCOL-IES ::= {
+...
+}
+
+RRCReestab-Initiated-Reporting-wo-UERLFRport ::= SEQUENCE {
+ failureCellPCI NG-RAN-CellPCI,
+ reestabCellCGI GlobalNG-RANCell-ID,
+ c-RNTI C-RNTI,
+```
+
+```
+ shortMAC-I MAC-I,
+ iE-Extensions ProtocolExtensionContainer { { RRCReestab-Initiated-Reporting-wo-UERLFReport-ExtIEs } } OPTIONAL,
+ ...
+}
+
+RRCReestab-Initiated-Reporting-wo-UERLFReport-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-RRCConnReestab-Indicator CRITICALITY ignore EXTENSION RRCConnReestab-Indicator PRESENCE optional },
+ ...
+}
+
+RRCReestab-Initiated-Reporting-with-UERLFReport ::= SEQUENCE {
+ uERLFReportContainer UERLFReportContainer,
+ iE-Extensions ProtocolExtensionContainer { { RRCReestab-Initiated-Reporting-with-UERLFReport-ExtIEs } } OPTIONAL,
+ ...
+}
+
+RRCReestab-Initiated-Reporting-with-UERLFReport-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RRCSsetup-initiated ::= SEQUENCE {
+ rRRCSsetup-Initiated-Reporting RRCSsetup-Initiated-Reporting,
+ uERLFReportContainer UERLFReportContainer OPTIONAL,
+```
+
+```
+ iE-Extensions ProtocolExtensionContainer { { RRCSetup-initiated-ExtIEs} } OPTIONAL,
+ ...
+}
+
+RRCSetup-initiated-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+RRCSetup-Initiated-Reporting ::= CHOICE {
+ rRCSetup-reporting-with-UERLFReport RRCSetup-Initiated-Reporting-with-UERLFReport,
+ choice-extension ProtocolIE-Single-Container { {RRCSetup-Initiated-Reporting-ExtIEs} }
+}
+
+RRCSetup-Initiated-Reporting-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+RRCSetup-Initiated-Reporting-with-UERLFReport ::= SEQUENCE {
+ uERLFReportContainer UERLFReportContainer,
+ iE-Extensions ProtocolExtensionContainer { {RRCSetup-Initiated-Reporting-with-UERLFReport-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+RRCSsetup-Initiated-Reporting-with-UERLReport-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RRCSResumeCause ::= ENUMERATED {
+```
+
+```
+ rna-Update,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RaReportIndicationList ::= SEQUENCE (SIZE(1..maxnoofUEsforRAReportIndications)) OF RaReportIndicationList-Item
+```
+
+```
+RaReportIndicationList-Item ::= SEQUENCE {
+```
+
+```
+ m-NG-RAN-node-UE-XnAP-ID
+```
+
+```
+ NG-RANnodeUEXnAPID,
+```
+
+```
+ iE-Extensions
+```
+
+```
+ ProtocolExtensionContainer { { RaReportIndicationList-Item-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RaReportIndicationList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+RadioResourceStatusNR-U ::= SEQUENCE {
+ dL-Total-PRB-usage INTEGER (0..100),
+ uL-Total-PRB-usage INTEGER (0..100),
+ iE-Extensions ProtocolExtensionContainer { RadioResourceStatusNR-U-ExtIEs } OPTIONAL,
+ ...
+}
+
+RadioResourceStatusNR-U-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- S
+
+SCGreconfigNotification ::= ENUMERATED {executed, ... , executed-deleted, deleted }
+
+S-NSSAIIstQoE ::= SEQUENCE (SIZE(1..maxnoofSNSSAIforQMC)) OF S-NSSAI
+
+S-BasedMDT ::= SEQUENCE {
+ ng-ran-TraceID NG-RANTraceID,
+ iE-Extension ProtocolExtensionContainer { S-BasedMDT-ExtIEs } OPTIONAL,
+```
+
+```
+ ...
+}
+
+S-BasedMDT-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+S-CPAC-Request ::= ENUMERATED {initiation, ...}
+
+S-CPAC-Request-Info ::= SEQUENCE {
+ s-CPAC-Security-Config-List S-CPAC-SecurityConfig-List,
+ s-CPAC-MultiTargetSN-List S-CPAC-MultiTargetSN-List OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {S-CPAC-Request-Info-ExtIEs} } OPTIONAL,
+ ...
+}
+
+S-CPAC-Request-Info-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+S-CPAC-ReferenceConfig-Request ::= ENUMERATED {request, ...}
+
+S-CPAC-SecurityConfig-List ::= SEQUENCE (SIZE(1..maxnoofSecurityConfigurations)) OF S-CPAC-SecurityConfig-Item
+```
+
+```
+S-CPAC-SecurityConfig-Item ::= SEQUENCE {
+ s-ng-RANnode-SecurityKey S-NG-RANnode-SecurityKey,
+ sk-counter SK-COUNTER,
+ iE-Extensions ProtocolExtensionContainer { {S-CPAC-SecurityConfig-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+S-CPAC-SecurityConfig-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+S-CPAC-MultiTargetSN-List ::= SEQUENCE (SIZE(1..maxnoofTargetSNsMinusOne)) OF S-CPAC-MultiTargetSN-Item
+
+S-CPAC-MultiTargetSN-Item ::= SEQUENCE {
+ target-S-NG-RANnodeID GlobalNG-RANNode-ID,
+ recommendedCandidatePSCells OCTET STRING,
+ iE-Extensions ProtocolExtensionContainer { {S-CPAC-MultiTargetSN-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+S-CPAC-MultiTargetSN-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+
+S-CPAC-InterSN-ExecutionNotify ::= ENUMERATED {true, ...}
+
+ServiceType ::= ENUMERATED{
+ qMC-for-streaming-service,
+ qMC-for-MTSI-service,
+ qMC-for-VR-service,
+ ...
+}
+
+SecondarydataForwardingInfoFromTarget-Item ::= SEQUENCE {
+ secondarydataForwardingInfoFromTarget DataForwardingInfoFromTargetNGRANnode,
+ iE-Extensions ProtocolExtensionContainer { { SecondarydataForwardingInfoFromTarget-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SecondarydataForwardingInfoFromTarget-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SecondarydataForwardingInfoFromTarget-List ::= SEQUENCE (SIZE(1..maxnoofMultiConnectivityMinusOne)) OF SecondarydataForwardingInfoFromTarget-Item
+```
+
+```
+SCGActivationRequest ::= ENUMERATED {activate-scg, deactivate-scg, ...}
+
+SCGActivationStatus ::= ENUMERATED {scg-activated, scg-deactivated, ...}
+
+SCGConfigurationQuery ::= ENUMERATED {true, ...}
+
+SCGIndicator ::= ENUMERATED{released, ...}
+
+SCGFailureReportContainer ::= OCTET STRING
+
+SDTSupportRequest ::= SEQUENCE {
+ sdtindicator SDTIndicator,
+ sdtAssistantInfo SDTAssistantInfo OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SDTSupportRequest-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SDTSupportRequest-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SDTIndicator ::= ENUMERATED {true, ...}
+```
+
+```
+SDTAssistantInfo ::= ENUMERATED {single-packet, multiple-packets, ...}
+```
+
+```
+SDT-Termination-Request ::= ENUMERATED {radio-link-problem, normal, ..., large-sdt-volume-BSR}
+```
+
+```
+
+SDTPartialUEContextInfo ::= SEQUENCE {
+ dRBsToBeSetup SDT-DRBsToBeSetupList OPTIONAL,
+ sRBsToBeSetup SDT-SRBsToBeSetupList,
+ iE-Extensions ProtocolExtensionContainer { { SDTPartialUEContextInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+SDTPartialUEContextInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+```
+SDT-DRBsToBeSetupList ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF SDT-DRBsToBeSetupList-Item
+```
+
+```
+
+SDT-DRBsToBeSetupList-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ uL-TNLInfo UPTransportLayerInformation,
+ dRB-RLC-Bearer-Configuration OCTET STRING,
+ dRB-QoS QoSFlowLevelQoSParameters,
+ rLC-Mode RLCMode,
+ s-nssai S-NSSAI,
+ ...
+}
+
+```
+
+```
+ pDCP-SNLength PDCPSNLength,
+ flows-Mapped-To-DRB-List Flows-Mapped-To-DRB-List,
+ iE-Extensions ProtocolExtensionContainer { { SDT-DRBsToBeSetupList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SDT-DRBsToBeSetupList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SDT-SRBsToBeSetupList ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SDT-SRBsToBeSetupList-Item
+
+SDT-SRBsToBeSetupList-Item ::= SEQUENCE {
+ srb-ID SRB-ID,
+ sRB-RLC-Bearer-Configuration OCTET STRING,
+ iE-Extensions ProtocolExtensionContainer { { SDT-SRBsToBeSetupList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SDT-SRBsToBeSetupList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+SRB-ID ::= INTEGER (0..4, ...)
+
+SDTDataForwardingDRBList ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF SDTDataForwardingDRBList-Item
+
+SDTDataForwardingDRBList-Item ::= SEQUENCE {
+ drb-ID DRB-ID,
+ dL-TNLInfo UPTransportLayerInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SDTDataForwardingDRBList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SDTDataForwardingDRBList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SecondaryRATUsageInformation ::= SEQUENCE {
+ pDUSessionUsageReport PDUSessionUsageReport OPTIONAL,
+ qoSFlowsUsageReportList QoSFlowsUsageReportList OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {SecondaryRATUsageInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SecondaryRATUsageInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+ ...
+}
+
+SecurityIndication ::= SEQUENCE {
+ integrityProtectionIndication ENUMERATED {required, preferred, not-needed, ...},
+ confidentialityProtectionIndication ENUMERATED {required, preferred, not-needed, ...},
+ maximumIPdatarate MaximumIPdatarate OPTIONAL,
+ -- This IE shall be present if the Integrity Protection IE within the Security Indication IE is present and set to "required" or "preferred". --
+ iE-Extensions ProtocolExtensionContainer { {SecurityIndication-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SecurityIndication-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SecurityResult ::= SEQUENCE {
+ integrityProtectionResult ENUMERATED {performed, not-performed, ...},
+ confidentialityProtectionResult ENUMERATED {performed, not-performed, ...},
+ iE-Extensions ProtocolExtensionContainer { {SecurityResult-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SecurityResult-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SensorMeasurementConfiguration ::= SEQUENCE {
+ sensorMeasConfig SensorMeasConfig,
+ sensorMeasConfigNameList SensorMeasConfigNameList OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SensorMeasurementConfiguration-ExtIEs } } OPTIONAL,
+ ...
+}
+
+SensorMeasurementConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SensorMeasConfigNameList ::= SEQUENCE (SIZE(1..maxnoofSensorName)) OF SensorName
+
+SensorMeasConfig ::= ENUMERATED {setup,...}
+
+SensorName ::= SEQUENCE {
+ uncompensatedBarometricConfig ENUMERATED {true, ...} OPTIONAL,
+ ueSpeedConfig ENUMERATED {true, ...} OPTIONAL,
+```
+
+```
+
+ ueOrientationConfig ENUMERATED {true, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {SensorNameConfig-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+SensorNameConfig-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+-- Served Cells E-UTRA IEs
+
+```
+
+ServedCellInformation-E-UTRA ::= SEQUENCE {
+ e-utra-pci E-UTRAPCI,
+ e-utra-cgi E-UTRA-CGI,
+ tac TAC,
+ ranac RANAC OPTIONAL,
+ broadcastPLMNs SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF ServedCellInformation-E-UTRA-perBPLMN,
+ e-utra-mode-info ServedCellInformation-E-UTRA-ModeInfo,
+ numberOfAntennaPorts NumberOfAntennaPorts-E-UTRA OPTIONAL,
+ prach-configuration E-UTRAPRACHConfiguration OPTIONAL,
+ mBSFNsubframeInfo MBSFNSubframeInfo-E-UTRA OPTIONAL,
+}
+
+```
+
+```
+
+ multibandInfo E-UTRAMultibandInfoList OPTIONAL,
+ freqBandIndicatorPriority ENUMERATED {not-broadcast, broadcast, ...} OPTIONAL,
+ bandwidthReducedSI ENUMERATED {scheduled, ...} OPTIONAL,
+ protectedE-UTRAResourceIndication ProtectedE-UTRAResourceIndication OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellInformation-E-UTRA-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ServedCellInformation-E-UTRA-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-BPLMN-ID-Info-EUTRA CRITICALITY ignore EXTENSION BPLMN-ID-Info-EUTRA PRESENCE optional }|
+ { ID id-NPRACHConfiguration CRITICALITY ignore EXTENSION NPRACHConfiguration PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+ServedCellInformation-E-UTRA-perBPLMN ::= SEQUENCE {
+ plmn-id PLMN-Identity,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellInformation-E-UTRA-perBPLMN-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+ServedCellInformation-E-UTRA-perBPLMN-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+```
+
+}
+
+```
+ServedCellInformation-E-UTRA-ModeInfo ::= CHOICE {
+ fdd ServedCellInformation-E-UTRA-FDDInfo,
+ tdd ServedCellInformation-E-UTRA-TDDInfo,
+ choice-extension ProtocolIE-Single-Container{ {ServedCellInformation-E-UTRA-ModeInfo-ExtIEs} }
+}
+```
+
+```
+ServedCellInformation-E-UTRA-ModeInfo-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+ServedCellInformation-E-UTRA-FDDInfo ::= SEQUENCE {
+ ul-earfcn E-UTRAARFCN,
+ dl-earfcn E-UTRAARFCN,
+ ul-e-utraTxBW E-UTRATransmissionBandwidth,
+ dl-e-utraTxBW E-UTRATransmissionBandwidth,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellInformation-E-UTRA-FDDInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ServedCellInformation-E-UTRA-FDDInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-OffsetOfNbiotChannelNumberToDL-EARFCN CRITICALITY reject EXTENSION OffsetOfNbiotChannelNumberToEARFCN PRESENCE optional}|
+ { ID id-OffsetOfNbiotChannelNumberToUL-EARFCN CRITICALITY reject EXTENSION OffsetOfNbiotChannelNumberToEARFCN PRESENCE optional},
+ ...
+}
+```
+
+```
+ServedCellInformation-E-UTRA-TDDInfo ::= SEQUENCE {
+ earfcn E-UTRAARFCN,
+ e-utraTxBW E-UTRATransmissionBandwidth,
+ subframeAssignmnet ENUMERATED {sa0,sa1,sa2,sa3,sa4,sa5,sa6,...},
+ specialSubframeInfo SpecialSubframeInfo-E-UTRA,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellInformation-E-UTRA-TDDInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ServedCellInformation-E-UTRA-TDDInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-OffsetOfNbiotChannelNumberToDL-EARFCN CRITICALITY reject EXTENSION OffsetOfNbiotChannelNumberToEARFCN PRESENCE optional}|
+ { ID id-NBiot-UL-DL-AlignmentOffset CRITICALITY reject EXTENSION NBiot-UL-DL-AlignmentOffset PRESENCE optional},
+ ...
+}
+```
+
+ServedCells-E-UTRA ::= SEQUENCE (SIZE (1..maxnoofCellsInNG-RANnode)) OF ServedCells-E-UTRA-Item
+
+ServedCells-E-UTRA-Item ::= SEQUENCE {
+ served-cell-info-E-UTRA ServedCellInformation-E-UTRA,
+ neighbour-info-NR NeighbourInformation-NR OPTIONAL,
+ neighbour-info-E-UTRA NeighbourInformation-E-UTRA OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ServedCells-E-UTRA-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ServedCells-E-UTRA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-SFN-Offset CRITICALITY ignore EXTENSION SFN-Offset PRESENCE optional },
+ ...
+}
+
+ServedCellsToUpdate-E-UTRA ::= SEQUENCE {
+ served-Cells-ToAdd-E-UTRA ServedCells-E-UTRA OPTIONAL,
+ served-Cells-ToModify-E-UTRA ServedCells-ToModify-E-UTRA OPTIONAL,
+ served-Cells-ToDelete-E-UTRA SEQUENCE (SIZE (1..maxnoofCellsInNG-RANnode)) OF E-UTRA-CGI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellsToUpdate-E-UTRA-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+ServedCellsToUpdate-E-UTRA-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ServedCells-ToModify-E-UTRA ::= SEQUENCE (SIZE (1..maxnoofCellsInNG-RANnode)) OF ServedCells-ToModify-E-UTRA-Item
+
+ServedCells-ToModify-E-UTRA-Item ::= SEQUENCE {
+ old-ECGI E-UTRA-CGI,
+ served-cell-info-E-UTRA ServedCellInformation-E-UTRA,
+ neighbour-info-NR NeighbourInformation-NR OPTIONAL,
+ neighbour-info-E-UTRA NeighbourInformation-E-UTRA OPTIONAL,
+ deactivation-indication ENUMERATED { deactivated, ... } OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {Served-cells-ToModify-E-UTRA-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+Served-cells-ToModify-E-UTRA-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-SFN-Offset CRITICALITY ignore EXTENSION SFN-Offset PRESENCE optional },
+ ...
+}
+```
+
+-- Served Cells NR IEs
+
+```
+ServedCellInformation-NR ::= SEQUENCE {
+ nrPCI NRPCI,
+ cellID NR-CGI,
+ tac TAC,
+ ranac RANAC OPTIONAL,
+ broadcastPLMN BroadcastPLMNs,
+ nrModeInfo NRModeInfo,
+ measurementTimingConfiguration OCTET STRING,
+ connectivitySupport Connectivity-Support,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellInformation-NR-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ServedCellInformation-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-BPLMN-ID-Info-NR CRITICALITY ignore EXTENSION BPLMN-ID-Info-NR PRESENCE optional }|
+ { ID id-ConfiguredTACIndication CRITICALITY ignore EXTENSION ConfiguredTACIndication PRESENCE optional }|
+ { ID id-SSB-PositionsInBurst CRITICALITY ignore EXTENSION SSB-PositionsInBurst PRESENCE optional }|
+ { ID id-NRCellPRACHConfig CRITICALITY ignore EXTENSION NRCellPRACHConfig PRESENCE optional }|
+ { ID id-NPN-Broadcast-Information CRITICALITY reject EXTENSION NPN-Broadcast-Information PRESENCE optional }|
+}
+```
+
+```
+
+ { ID id-CSI-RSTransmissionIndication CRITICALITY ignore EXTENSION CSI-RSTransmissionIndication PRESENCE optional }|
+ { ID id-SFN-Offset CRITICALITY ignore EXTENSION SFN-Offset PRESENCE optional }|
+ { ID id-Supported-MBS-FSA-ID-List CRITICALITY ignore EXTENSION Supported-MBS-FSA-ID-List PRESENCE optional }|
+ { ID id-NR-U-ChannelInfo-List CRITICALITY ignore EXTENSION NR-U-ChannelInfo-List PRESENCE optional }|
+ { ID id-Additional-Measurement-Timing-Configuration-List CRITICALITY ignore EXTENSION Additional-Measurement-Timing-Configuration-List
+ PRESENCE optional }|
+ { ID id-Redcap-Bcast-Information CRITICALITY ignore EXTENSION Redcap-Bcast-Information PRESENCE optional }|
+ { ID id-eRedcap-Bcast-Information CRITICALITY ignore EXTENSION ERedcap-Bcast-Information PRESENCE optional }|
+ { ID id-MobileIABCell CRITICALITY ignore EXTENSION MobileIABCell PRESENCE optional},
+ ...
+}
+
+SFN-Offset ::= SEQUENCE {
+ sFN-Time-Offset BIT STRING (SIZE(24)),
+
+ iE-Extensions ProtocolExtensionContainer { {SFN-Offset-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SFN-Offset-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ServedCells-NR ::= SEQUENCE (SIZE (1..maxnoofCellsinNG-RANnode)) OF ServedCells-NR-Item
+
+```
+
+```
+ServedCells-NR-Item ::= SEQUENCE {
+ served-cell-info-NR ServedCellInformation-NR,
+ neighbour-info-NR NeighbourInformation-NR OPTIONAL,
+ neighbour-info-E-UTRA NeighbourInformation-E-UTRA OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ServedCells-NR-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ServedCells-NR-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-ServedCellSpecificInfoReq-NR CRITICALITY ignore EXTENSION ServedCellSpecificInfoReq-NR PRESENCE optional },
+ ...
+}
+
+ServedCells-ToModify-NR ::= SEQUENCE (SIZE (1..maxnoofCellsinNG-RANnode)) OF ServedCells-ToModify-NR-Item
+
+ServedCells-ToModify-NR-Item ::= SEQUENCE {
+ old-NR-CGI NR-CGI,
+ served-cell-info-NR ServedCellInformation-NR,
+ neighbour-info-NR NeighbourInformation-NR OPTIONAL,
+ neighbour-info-E-UTRA NeighbourInformation-E-UTRA OPTIONAL,
+ deactivation-indication ENUMERATED {deactivated, ...} OPTIONAL,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { {Served-cells-ToModify-NR-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+Served-cells-ToModify-NR-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+ServedCellSpecificInfoReq-NR ::= SEQUENCE (SIZE(1..maxnoofCellsinNG-RANnode)) OF ServedCellSpecificInfoReq-NR-Item
+
+ServedCellSpecificInfoReq-NR-Item ::= SEQUENCE {
+ nRCGI NR-CGI,
+ additionalMTCTListRequestIndicator ENUMERATED {additionalMTCTListRequested, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { ServedCellSpecificInfoReq-NR-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ServedCellSpecificInfoReq-NR-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+ServedCellsToUpdate-NR ::= SEQUENCE {
+ served-Cells-ToAdd-NR ServedCells-NR OPTIONAL,
+```
+
+```
+ served-Cells-ToModify-NR ServedCells-ToModify-NR OPTIONAL,
+ served-Cells-ToDelete-NR SEQUENCE (SIZE (1..maxnoofCellsinNG-RANnode)) OF NR-CGI OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {ServedCellsToUpdate-NR-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ServedCellsToUpdate-NR-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+SharedResourceType ::= CHOICE {
+ ul-onlySharing SharedResourceType-UL-OnlySharing,
+ ul-and-dl-Sharing SharedResourceType-ULDL-Sharing,
+ choice-extension ProtocolIE-Single-Container { {SharedResourceType-ExtIEs} }
+}
+```
+
+```
+SharedResourceType-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+SharedResourceType-UL-OnlySharing ::= SEQUENCE {
+ ul-resourceBitmap DataTrafficResources,
+ iE-Extensions ProtocolExtensionContainer { {SharedResourceType-UL-OnlySharing-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SharedResourceType-UL-OnlySharing-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SharedResourceType-ULDL-Sharing ::= CHOICE {
+ ul-resources SharedResourceType-ULDL-Sharing-UL-Resources,
+ dl-resources SharedResourceType-ULDL-Sharing-DL-Resources,
+ choice-extension ProtocolIE-Single-Container { {SharedResourceType-ULDL-Sharing-ExtIEs} }
+}
+
+SharedResourceType-ULDL-Sharing-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+SharedResourceType-ULDL-Sharing-UL-Resources ::= CHOICE {
+ unchanged NULL,
+ changed SharedResourceType-ULDL-Sharing-UL-ResourcesChanged,
+}
+```
+
+```
+ choice-extension ProtocolIE-Single-Container { {SharedResourceType-ULDL-Sharing-UL-Resources-ExtIEs} }
+}
+
+SharedResourceType-ULDL-Sharing-UL-Resources-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+SharedResourceType-ULDL-Sharing-UL-ResourcesChanged ::= SEQUENCE {
+ ul-resourceBitmap DataTrafficResources,
+ iE-Extensions ProtocolExtensionContainer { {SharedResourceType-ULDL-Sharing-UL-ResourcesChanged-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SharedResourceType-ULDL-Sharing-UL-ResourcesChanged-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SharedResourceType-ULDL-Sharing-DL-Resources ::= CHOICE {
+ unchanged NULL,
+ changed SharedResourceType-ULDL-Sharing-DL-ResourcesChanged,
+ choice-extension ProtocolIE-Single-Container { {SharedResourceType-ULDL-Sharing-DL-Resources-ExtIEs} }
+}
+```
+
+```
+SharedResourceType-ULDL-Sharing-DL-Resources-ExtIEs XNAP-PROTOCOL-IEs ::= {
+ ...
+}
+
+SharedResourceType-ULDL-Sharing-DL-ResourcesChanged ::= SEQUENCE {
+ dl-resourceBitmap DataTrafficResources,
+ iE-Extensions ProtocolExtensionContainer { {SharedResourceType-ULDL-Sharing-DL-ResourcesChanged-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SharedResourceType-ULDL-Sharing-DL-ResourcesChanged-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SK-COUNTER ::= INTEGER (0..65535)
+
+SliceAvailableCapacity ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF SliceAvailableCapacity-Item
+
+SliceAvailableCapacity-Item ::= SEQUENCE {
+ pLMNIdentity PLMN-Identity,
+ sNSSAIAvailableCapacity-List SNSSAIAvailableCapacity-List,
+ iE-Extensions ProtocolExtensionContainer { { SliceAvailableCapacity-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+
+SliceAvailableCapacity-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SNSSAIAvailableCapacity-List ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SNSSAIAvailableCapacity-Item
+
+SNSSAIAvailableCapacity-Item ::= SEQUENCE {
+ sNSSAI S-NSSAI,
+ sliceAvailableCapacityValueDownlink INTEGER (0..100),
+ sliceAvailableCapacityValueUplink INTEGER (0..100),
+ iE-Extensions ProtocolExtensionContainer { { SNSSAIAvailableCapacity-Item-ExtIEs } } OPTIONAL
+}
+
+SNSSAIAvailableCapacity-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SliceRadioResourceStatus-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF SliceRadioResourceStatus-Item
+```
+
+```
+SliceRadioResourceStatus-Item ::= SEQUENCE {
+ plmn-Identity PLMN-Identity,
+ sNSSAIRadioResourceStatus-List SNSSAIRadioResourceStatus-List,
+ iE-Extensions ProtocolExtensionContainer { { SliceRadioResourceStatus-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SliceRadioResourceStatus-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+SNSSAIRadioResourceStatus-List ::= SEQUENCE (SIZE(1..maxnoofSliceItems)) OF SNSSAIRadioResourceStatus-Item
+```
+
+```
+SNSSAIRadioResourceStatus-Item ::= SEQUENCE {
+ sNSSAI S-NSSAI,
+ slice-DL-GBR-PRB-Usage Slice-DL-GBR-PRB-Usage,
+ slice-UL-GBR-PRB-Usage Slice-UL-GBR-PRB-Usage,
+ slice-DL-non-GBR-PRB-Usage Slice-DL-non-GBR-PRB-Usage,
+ slice-UL-non-GBR-PRB-Usage Slice-UL-non-GBR-PRB-Usage,
+ slice-DL-Total-PRB-Allocation Slice-DL-Total-PRB-Allocation,
+ slice-UL-Total-PRB-Allocation Slice-UL-Total-PRB-Allocation,
+ iE-Extensions ProtocolExtensionContainer { { SNSSAIRadioResourceStatus-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+
+SNSSAIRadioResourceStatus-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+Slice-DL-GBR-PRB-Usage ::= INTEGER (0..100)
+
+Slice-UL-GBR-PRB-Usage ::= INTEGER (0..100)
+
+Slice-DL-non-GBR-PRB-Usage ::= INTEGER (0..100)
+
+Slice-UL-non-GBR-PRB-Usage ::= INTEGER (0..100)
+
+Slice-DL-Total-PRB-Allocation ::= INTEGER (0..100)
+
+Slice-UL-Total-PRB-Allocation ::= INTEGER (0..100)
+
+SliceSupport-List ::= SEQUENCE (SIZE(1..maxnoofSliceItems)) OF S-NSSAI
+
+SliceToReport-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF SliceToReport-List-Item
+```
+
+```
+SliceToReport-List-Item ::= SEQUENCE {
+ pLMNIdentity PLMN-Identity,
+ sNSSAIlist SNSSAI-list,
+ iE-Extensions ProtocolExtensionContainer { { SliceToReport-List-Item-ExtIEs } } OPTIONAL,
+ ...
+}
+
+SliceToReport-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SNSSAI-list ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SNSSAI-Item
+
+SNSSAI-Item ::= SEQUENCE {
+ sNSSAI S-NSSAI,
+ iE-Extensions ProtocolExtensionContainer { { SNSSAI-Item-ExtIEs } } OPTIONAL
+}
+
+SNSSAI-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+SlotConfiguration-List ::= SEQUENCE (SIZE (1..maxnoofslots)) OF SlotConfiguration-List-Item
+
+SlotConfiguration-List-Item ::= SEQUENCE {
+ slotIndex INTEGER (0..5119),
+ symbolAllocation-in-Slot SymbolAllocation-in-Slot,
+ iE-Extensions ProtocolExtensionContainer { {SlotConfiguration-List-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SlotConfiguration-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+S-NG-RANnode-SecurityKey ::= BIT STRING (SIZE(256))
+
+S-NG-RANnode-Addition-Trigger-Ind ::= ENUMERATED {
+ sn-change,
+ inter-MN-HO,
+ intra-MN-HO,
+ ...
+}
+
+S-NSSAI ::= SEQUENCE {
+
+```
+ sst OCTET STRING (SIZE(1)),
+ sd OCTET STRING (SIZE(3)) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {S-NSSAI-ExtIEs} } OPTIONAL,
+ ...
+}
+
+S-NSSAI-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SNMobilityInformation ::= BIT STRING (SIZE(32))
+
+SNPNIdentity ::= SEQUENCE {
+ plmnID PLMN-Identity,
+ nid NID,
+ iE-Extensions ProtocolExtensionContainer { {SNPNIdentity-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SNPNIdentity-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+SNTriggered ::= ENUMERATED{
+ true,
+ ...
+}
+
+SpecialSubframeInfo-E-UTRA ::= SEQUENCE {
+ specialSubframePattern SpecialSubframePatterns-E-UTRA,
+ cyclicPrefixDL CyclicPrefix-E-UTRA-DL,
+ cyclicPrefixUL CyclicPrefix-E-UTRA-UL,
+ iE-Extensions ProtocolExtensionContainer { {SpecialSubframeInfo-E-UTRA-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SpecialSubframeInfo-E-UTRA-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SpecialSubframePatterns-E-UTRA ::= ENUMERATED {
+ ssp0,
+ ssp1,
+```
+
+```
+ ssp2,
+ ssp3,
+ ssp4,
+ ssp5,
+ ssp6,
+ ssp7,
+ ssp8,
+ ssp9,
+ ssp10,
+ ...
+}
+```
+
+```
+SpectrumSharingGroupID ::= INTEGER (1..maxnoofCellsinNG-RANnode)
+```
+
+```
+SplitSessionIndicator ::= ENUMERATED {
+ split,
+ ...
+}
+```
+
+```
+SplitSRBsTypes ::= ENUMERATED {srb1, srb2, srb1and2, ...}
+```
+
+```
+SPRAvailability ::= ENUMERATED {spr-available, ...}
+```
+
+SRSConfiguration ::= OCTET STRING
+
+SSBAreaCapacityValue-List ::= SEQUENCE (SIZE(1..maxnoofSSBAreas)) OF SSBAreaCapacityValue-List-Item
+
+SSBAreaCapacityValue-List-Item ::= SEQUENCE {
+ sSBIndex INTEGER(0..63),
+ ssbAreaCapacityValue INTEGER (0..100),
+ iE-Extensions ProtocolExtensionContainer { { SSBAreaCapacityValue-List-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SSBAreaCapacityValue-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SSBAreaRadioResourceStatus-List ::= SEQUENCE (SIZE(1..maxnoofSSBAreas)) OF SSBAreaRadioResourceStatus-List-Item
+
+SSBAreaRadioResourceStatus-List-Item ::= SEQUENCE {
+ sSBIndex INTEGER(0..63),
+ ssb-Area-DL-GBR-PRB-usage DL-GBR-PRB-usage,
+
+```
+
+ ssb-Area-UL-GBR-PRB-usage UL-GBR-PRB-usage,
+ ssb-Area-dL-non-GBR-PRB-usage DL-non-GBR-PRB-usage,
+ ssb-Area-uL-non-GBR-PRB-usage UL-non-GBR-PRB-usage,
+ ssb-Area-dL-Total-PRB-usage DL-Total-PRB-usage,
+ ssb-Area-uL-Total-PRB-usage UL-Total-PRB-usage,
+ iE-Extensions ProtocolExtensionContainer { { SSBAreaRadioResourceStatus-List-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+
+```
+
+SSBAreaRadioResourceStatus-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-DL-scheduling-PDCCH-CCE-usage CRITICALITY ignore EXTENSION DL-scheduling-PDCCH-CCE-usage PRESENCE optional}|
+ { ID id-UL-scheduling-PDCCH-CCE-usage CRITICALITY ignore EXTENSION UL-scheduling-PDCCH-CCE-usage PRESENCE optional},
+ ...
+}
+
+```
+
+```
+
+SSB-Coverage-Modification-List ::= SEQUENCE (SIZE (0..maxnoofSSBAreas)) OF SSB-Coverage-Modification-List-Item
+
+```
+
+```
+
+SSB-Coverage-Modification-List-Item ::= SEQUENCE {
+ sSBIndex INTEGER(0..63),
+ sSBCoverageState INTEGER (0..15, ...),
+ iE-Extension ProtocolExtensionContainer { { SSB-Coverage-Modification-List-Item-ExtIEs} } OPTIONAL,
+}
+
+```
+
+```
+...
+}
+
+SSB-Coverage-Modification-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SSB-PositionsInBurst ::= CHOICE {
+ shortBitmap BIT STRING (SIZE (4)),
+ mediumBitmap BIT STRING (SIZE (8)),
+ longBitmap BIT STRING (SIZE (64)),
+ choice-extension ProtocolIE-Single-Container { {SSB-PositionsInBurst-ExtIEs} }
+}
+
+SSB-PositionsInBurst-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+SSB-freqInfo ::= INTEGER (0..maxNRARFCN)
+
+SSB-subcarrierSpacing ::= ENUMERATED {kHz15, kHz30, kHz120, kHz240, spare3, spare2, spare1, ...}
+```
+
+SSBOffsets-List ::= SEQUENCE (SIZE(1..maxnoofSSBAreas)) OF SSBOffsets-Item
+
+SSBOffsets-Item ::= SEQUENCE {
+ nG-RANnode1SSBOffsets SSBOffsetInformation OPTIONAL,
+ nG-RANnode2ProposedSSBOffsets SSBOffsetInformation,
+ iE-Extensions ProtocolExtensionContainer { { SSBOffsets-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SSBOffsets-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SSBOffsetInformation ::= SEQUENCE {
+ sSBIndex INTEGER(0..63),
+ sSBTriggeringOffset MobilityParametersInformation,
+ iE-Extensions ProtocolExtensionContainer { { SSBOffsetInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SSBOffsetInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+ ...
+}
+
+SSBOffsetModificationRange ::= SEQUENCE {
+ sSBIndex INTEGER(0..63),
+ sSBmobilityParametersModificationRange MobilityParametersModificationRange,
+ iE-Extensions ProtocolExtensionContainer { { SSBOffsetModificationRange-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SSBOffsetModificationRange-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SSBToReport-List ::= SEQUENCE (SIZE(1..maxnoofSSBAreas)) OF SSBToReport-List-Item
+
+SSBToReport-List-Item ::= SEQUENCE {
+ sSBIndex INTEGER(0..63),
+ iE-Extensions ProtocolExtensionContainer { { SSBToReport-List-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SSBToReport-List-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SSB-transmissionPeriodicity ::= ENUMERATED {sf10, sf20, sf40, sf80, sf160, sf320, sf640, ...}
+
+SSB-transmissionTimingOffset ::= INTEGER (0..127, ...)
+
+SSB-transmissionBitmap ::= CHOICE {
+ shortBitmap BIT STRING (SIZE (4)),
+ mediumBitmap BIT STRING (SIZE (8)),
+ longBitmap BIT STRING (SIZE (64)),
+ choice-extension ProtocolIE-Single-Container { { SSB-transmisisonBitmap-ExtIEs } }
+}
+
+SSB-transmisisonBitmap-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+SuccessfulHOREportInformation ::= SEQUENCE (SIZE(1.. maxnoofSuccessfulHOREports)) OF SuccessfulHOREportList-Item
+
+SuccessfulHOREportList-Item ::= SEQUENCE {
+ successfulHOREport SuccessfulHOREportContainer,
+```
+
+```
+iE-Extensions ProtocolExtensionContainer { { SuccessfulHOREportList-Item-ExtIEs} } OPTIONAL,
+...
+}
+
+SuccessfulHOREportList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+SuccessfulHOREportContainer ::= OCTET STRING
+
+SuccessfulPSCellChangeReportInformation ::= SEQUENCE (SIZE(1.. maxnoofSuccessfulPSCellChangeReports)) OF SuccessfulPSCellChangeReportList-Item
+SuccessfulPSCellChangeReportList-Item ::= SEQUENCE {
+ successfulPSCellChangeReport SuccessfulPSCellChangeReportContainer,
+ sNMobilityInformation SNMobilityInformation OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { SuccessfulPSCellChangeReportList-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SuccessfulPSCellChangeReportList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+...
+}
+
+SuccessfulPSCellChangeReportContainer ::= OCTET STRING
+```
+
+SUL-FrequencyBand ::= INTEGER (1..1024)
+
+SUL-Information ::= SEQUENCE {
+ sulFrequencyInfo NRARFCN,
+ sulTransmissionBandwidth NRTransmissionBandwidth,
+ iE-Extensions ProtocolExtensionContainer { {SUL-Information-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SUL-Information-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-CarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }|
+ { ID id-FrequencyShift7p5khz CRITICALITY ignore EXTENSION FrequencyShift7p5khz PRESENCE optional },
+ ...
+}
+
+Supported-MBS-FSA-ID-List ::= SEQUENCE (SIZE(1..maxnoofMBSFSAs)) OF MBS-FrequencySelectionArea-Identity
+
+SupportedSULBandList ::= SEQUENCE (SIZE(1..maxnoofNRCellBands)) OF SupportedSULBandItem
+
+```
+SupportedSULBandItem ::= SEQUENCE {
+ sulBandItem SUL-FrequencyBand,
+ iE-Extensions ProtocolExtensionContainer { {SupportedSULBandItem-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SupportedSULBandItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+SurvivalTime ::= INTEGER (0..1920000, ...)
+```
+
+```
+SymbolAllocation-in-Slot ::= CHOICE {
+ allDL SymbolAllocation-in-Slot-AllDL,
+ allUL SymbolAllocation-in-Slot-AllUL,
+ bothDLandUL SymbolAllocation-in-Slot-BothDLandUL,
+ choice-extension ProtocolIE-Single-Container { {SymbolAllocation-in-Slot-ExtIEs} }
+}
+```
+
+```
+SymbolAllocation-in-Slot-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+SymbolAllocation-in-Slot-AllDL ::= SEQUENCE {
+ iE-Extension ProtocolExtensionContainer { {SymbolAllocation-in-Slot-AllDL-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SymbolAllocation-in-Slot-AllDL-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SymbolAllocation-in-Slot-AllUL ::= SEQUENCE {
+ iE-Extension ProtocolExtensionContainer { {SymbolAllocation-in-Slot-AllUL-ExtIEs} } OPTIONAL,
+ ...
+}
+
+SymbolAllocation-in-Slot-AllUL-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+SymbolAllocation-in-Slot-BothDLandUL ::= SEQUENCE {
+```
+
+```
+ numberOfDLSymbols INTEGER (0..13),
+ numberOfULSymbols INTEGER (0..13),
+ iE-Extension ProtocolExtensionContainer { {SymbolAllocation-in-Slot-BothDLandUL-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SymbolAllocation-in-Slot-BothDLandUL-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-permutation CRITICALITY ignore EXTENSION Permutation PRESENCE optional },
+ ...
+}
+```
+
+```
+SNPN-CellBasedMDT ::= SEQUENCE (SIZE(1.. maxnoofCellIDforMDT)) OF SNPN-CellBasedMDT-Item
+```
+
+```
+SNPN-CellBasedMDT-Item ::= SEQUENCE {
+ nRCGI NR-CGI,
+ nID NID,
+ iE-Extensions ProtocolExtensionContainer { {SNPN-CellBasedMDT-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+SNPN-CellBasedMDT-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+}
+
+SNPN-TAIBasedMDT ::= SEQUENCE (SIZE(1.. maxnoofTAforMDT)) OF SNPN-TAIBasedMDT-Item
+
+SNPN-TAIBasedMDT-Item ::= SEQUENCE {
+
+ plmn-ID PLMN-Identity,
+
+ tAC TAC,
+
+ nID NID,
+
+ iE-Extensions ProtocolExtensionContainer { {SNPN-TAIBasedMDT-Item-ExtIEs} } OPTIONAL,
+
+ ...
+
+}
+
+SNPN-TAIBasedMDT-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ ...
+
+}
+
+SNPN-IDBasedMDT ::= SEQUENCE (SIZE(1.. maxnoofMDTSNPNs)) OF SNPN-IDBasedMDT-Item
+
+SNPN-IDBasedMDT-Item ::= SEQUENCE {
+
+ plmn-ID PLMN-Identity,
+
+ nID NID,
+
+ iE-Extensions ProtocolExtensionContainer { {SNPN-IDBasedMDT-Item-ExtIEs} } OPTIONAL,
+
+```
+ ...
+}
+
+SNPN-IDBasedMDT-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+-- T
+
+TABasedMDT ::= SEQUENCE {
+ tAListforMDT TAListforMDT,
+ iE-Extensions ProtocolExtensionContainer { {TABasedMDT-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TABasedMDT-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+TAIBasedMDT ::= SEQUENCE {
+ tAIListforMDT TAIListforMDT,
+ iE-Extensions ProtocolExtensionContainer { {TAIBasedMDT-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TAIBasedMDT-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TAIListforMDT ::= SEQUENCE (SIZE(1..maxnoofTAforMDT)) OF TAIforMDT-Item
+
+TAIforMDT-Item ::= SEQUENCE {
+ plmn-ID PLMN-Identity,
+ tAC TAC,
+ iE-Extensions ProtocolExtensionContainer { {TAIforMDT-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TAIforMDT-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+TAC ::= OCTET STRING (SIZE (3))
+
+TAINSAGSupportList ::= SEQUENCE (SIZE(1..maxnoofNSAGs)) OF TAINSAGSupportItem
+
+TAINSAGSupportItem ::= SEQUENCE {
+ nSAG-ID NSAG-ID,
+ nSAGSliceSupportList ExtendedSliceSupportList,
+ iE-Extensions ProtocolExtensionContainer { {TAINSAGSupportItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TAINSAGSupportItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TAISliceUnavailableCellList ::= SEQUENCE (SIZE(1..maxnoofExtSliceItems)) OF TAISliceUnavailableCellItem
+
+TAISliceUnavailableCellItem ::= SEQUENCE {
+ sNSSAI S-NSSAI,
+ unavailableNRCellList UnavailableNRCellList,
+ iE-Extensions ProtocolExtensionContainer { {TAISliceUnavailableCellItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+```
+}
+
+TAISliceUnavailableCellItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UnavailableNRCellList ::= SEQUENCE (SIZE (1..maxnoofCellsinNG-RANnode)) OF NR-CGI
+
+TAISupport-List ::= SEQUENCE (SIZE (1..maxnoofsupportedTACs)) OF TAISupport-Item
+
+TAISupport-Item ::= SEQUENCE {
+ tac TAC,
+ broadcastPLMNs SEQUENCE (SIZE (1..maxnoofsupportedPLMNs)) OF BroadcastPLMNinTAISupport-Item,
+ iE-Extensions ProtocolExtensionContainer { { TAISupport-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TAISupport-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+TAListforMDT ::= SEQUENCE (SIZE(1..maxnoofTAforMDT)) OF TAC
+```
+
+```
+TABasedQMC ::= SEQUENCE {
+ tAListforQMC TAListforQMC,
+ iE-Extensions ProtocolExtensionContainer { {TABasedQMC-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+TABasedQMC-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+TAListforQMC ::= SEQUENCE (SIZE(1..maxnoofTAforQMC)) OF TAC
+```
+
+```
+TAIBasedQMC ::= SEQUENCE {
+ tAIListforQMC TAIListforQMC,
+ iE-Extensions ProtocolExtensionContainer { {TAIBasedQMC-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+TAIBasedQMC-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+}
+
+TAIListforQMC ::= SEQUENCE (SIZE(1..maxnoofTAforQMC)) OF TAI-Item
+
+TAI-Item ::= SEQUENCE {
+ tAC TAC,
+ pLMN-Identity PLMN-Identity,
+ iE-Extensions ProtocolExtensionContainer { {TAI-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TAI-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TargetCellinEUTRAN ::= OCTET STRING -- This IE is to be encoded according to Global Cell ID in the Last Visited E-UTRAN Cell Information IE, as defined in in TS 36.413 [31]
+
+Target-CGI ::= CHOICE {
+```
+
+```
+ nr NR-CGI,
+ e-utra E-UTRA-CGI,
+ choice-extension ProtocolIE-Single-Container { {TargetCGI-ExtIEs} }
+}
+```
+
+```
+TargetCGI-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+TDDULDLConfigurationCommonNR ::= OCTET STRING
+```
+
+```
+TargetCellList ::= SEQUENCE (SIZE(1..maxnoofCHOCells)) OF TargetCellList-Item
+```
+
+```
+TargetCellList-Item ::= SEQUENCE {
+ target-cell Target-CGI,
+ iE-Extensions ProtocolExtensionContainer { { TargetCellList-Item-ExtIEs} } OPTIONAL
+}
+```
+
+```
+TargetCellList-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+Threshold-RSRQ ::= INTEGER(0..127)
+
+Threshold-RSRP ::= INTEGER(0..127)
+
+Threshold-SINR ::= INTEGER(0..127)
+
+TimeSinceFailure ::= INTEGER (0..172800, ...)
+
+TimeSynchronizationAssistanceInformation ::= SEQUENCE {
+ timeDistributionIndication ENUMERATED {enabled, disabled, ...},
+ uuTimeSynchronizationErrorBudget INTEGER (0..1000000, ...) OPTIONAL,
+ -- The above IE shall be present if the Time Distribution Indication IE is set to the value "enabled"
+ ie-Extension ProtocolExtensionContainer { { TimeSynchronizationAssistanceInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TimeSynchronizationAssistanceInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+ { ID id-ClockQualityReportingControlInfo CRITICALITY ignore EXTENSION ClockQualityReportingControlInfo PRESENCE optional},
+ ...
+}
+
+TimeToTrigger ::= ENUMERATED {ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120}
+
+TimeToWait ::= ENUMERATED {
+
+v1s,
+
+v2s,
+
+v5s,
+
+v10s,
+
+v20s,
+
+v60s,
+
+...
+
+}
+
+TMGI ::= OCTET STRING (SIZE(6))
+
+TNLConfigurationInfo ::= SEQUENCE {
+
+extendedUPTransportLayerAddressesToAdd ExtTLAs OPTIONAL,
+
+extendedUPTransportLayerAddressesToRemove ExtTLAs OPTIONAL,
+
+iE-Extensions ProtocolExtensionContainer { {TNLConfigurationInfo-ExtIEs} } OPTIONAL,
+
+...
+
+}
+
+TNLConfigurationInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+```
+ ...
+}
+
+TNLA-To-Add-List ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF TNLA-To-Add-Item
+
+TNLA-To-Add-Item ::= SEQUENCE {
+ tNLAssociationTransportLayerAddress CPTransportLayerInformation,
+ tNLAssociationUsage TNLAssociationUsage,
+ iE-Extensions ProtocolExtensionContainer { { TNLA-To-Add-Item-ExtIEs} } OPTIONAL
+}
+
+TNLA-To-Add-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TNLA-To-Update-List ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF TNLA-To-Update-Item
+
+TNLA-To-Update-Item ::= SEQUENCE {
+ tNLAssociationTransportLayerAddress CPTransportLayerInformation,
+ tNLAssociationUsage TNLAssociationUsage OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { TNLA-To-Update-Item-ExtIEs} } OPTIONAL
+}
+```
+
+```
+TNLA-To-Update-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TNLA-To-Remove-List ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF TNLA-To-Remove-Item
+
+TNLA-To-Remove-Item ::= SEQUENCE {
+ tNLAssociationTransportLayerAddress CPTransportLayerInformation,
+ iE-Extensions ProtocolExtensionContainer { { TNLA-To-Remove-Item-ExtIEs} } OPTIONAL
+}
+
+TNLA-To-Remove-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TNLA-Setup-List ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF TNLA-Setup-Item
+
+TNLA-Setup-Item ::= SEQUENCE {
+ tNLAssociationTransportLayerAddress CPTransportLayerInformation,
+ iE-Extensions ProtocolExtensionContainer { { TNLA-Setup-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+}
+
+TNLA-Setup-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TNLA-Failed-To-Setup-List ::= SEQUENCE (SIZE(1..maxnoofTNLAssociations)) OF TNLA-Failed-To-Setup-Item
+
+TNLA-Failed-To-Setup-Item ::= SEQUENCE {
+ tNLAssociationTransportLayerAddress CPTransportLayerInformation,
+ cause Cause,
+ iE-Extensions ProtocolExtensionContainer { { TNLA-Failed-To-Setup-Item-ExtIEs} } OPTIONAL
+}
+
+TNLA-Failed-To-Setup-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TNLAssociationUsage ::= ENUMERATED {
+ ue,
+ non-ue,
+}
+```
+
+```
+both,
+...
+}
+```
+
+```
+TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...))
+```
+
+```
+TraceActivation ::= SEQUENCE {
+ ng-ran-TraceID NG-RANTraceID,
+ interfaces-to-trace BIT STRING { ng-c (0), x-nc (1), uu (2), fl-c (3), el (4) } (SIZE(8)),
+ trace-depth Trace-Depth,
+ trace-coll-address TransportLayerAddress,
+ ie-Extension ProtocolExtensionContainer { {TraceActivation-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+TraceActivation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ -- Extension to support MDT -
+ { ID id-TraceCollectionEntityURI CRITICALITY ignore EXTENSION URIaddress PRESENCE optional}|
+ { ID id-MDT-Configuration CRITICALITY ignore EXTENSION MDT-Configuration PRESENCE optional},
+ ...
+}
+```
+
+```
+Trace-Depth ::= ENUMERATED {
+ minimum,
+ medium,
+ maximum,
+ minimumWithoutVendorSpecificExtension,
+ mediumWithoutVendorSpecificExtension,
+ maximumWithoutVendorSpecificExtension,
+ ...
+}
+
+TrafficIndex ::= INTEGER (1..1024, ...)
+
+TrafficProfile ::= CHOICE {
+ uPTraffic QoSFlowLevelQoSParameters,
+ nonUPTraffic NonUPTraffic,
+ choice-extension ProtocolIE-Single-Container { {TrafficProfile-ExtIEs} }
+}
+
+TrafficProfile-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+TrafficReleaseType ::= CHOICE {
+ fullRelease AllTrafficIndication,
+ partialRelease TrafficToBeRelease-List,
+ choice-extension ProtocolIE-Single-Container { {TrafficReleaseType-ExtIEs} }
+}
+
+TrafficReleaseType-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+TrafficToBeReleaseInformation ::= SEQUENCE {
+ releaseType TrafficReleaseType,
+ ie-Extensions ProtocolExtensionContainer { {TrafficToBeReleaseInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficToBeReleaseInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TrafficToBeRelease-List ::= SEQUENCE (SIZE(1..maxnoofTrafficIndexEntries)) OF TrafficToBeRelease-Item
+```
+
+```
+TrafficToBeRelease-Item ::= SEQUENCE {
+ trafficIndex TrafficIndex,
+ bHInfoList BHInfoList OPTIONAL,
+ ie-Extension ProtocolExtensionContainer { {TrafficToBeRelease-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TrafficToBeRelease-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+TSCTrafficCharacteristics ::= SEQUENCE {
+ tSCAssistanceInformationDownlink TSCAssistanceInformation OPTIONAL,
+ tSCAssistanceInformationUplink TSCAssistanceInformation OPTIONAL,
+ ie-Extension ProtocolExtensionContainer { {TSCTrafficCharacteristics-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TSCTrafficCharacteristics-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+TSCAssistanceInformation ::= SEQUENCE {
+ periodicity INTEGER (0.. 640000, ...),
+ burstArrivalTime OCTET STRING OPTIONAL,
+ ie-Extension ProtocolExtensionContainer { { TSCAssistanceInformation-ExtIEs} } OPTIONAL,
+ ...
+}
+
+TSCAssistanceInformation-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-SurvivalTime CRITICALITY ignore EXTENSION SurvivalTime PRESENCE optional}|
+ { ID id-CapabilityForBATAdaptation CRITICALITY ignore EXTENSION CapabilityForBATAdaptation PRESENCE optional}|
+ { ID id-N6JitterInformation CRITICALITY ignore EXTENSION N6JitterInformation PRESENCE optional},
+ ...
+}
+
+TypeOfError ::= ENUMERATED {
+ not-understood,
+ missing,
+ ...
+}
+
+-- U
+```
+
+```
+UEAggregateMaximumBitRate ::= SEQUENCE {
+ dl-UE-AMBR BitRate,
+ ul-UE-AMBR BitRate,
+ iE-Extension ProtocolExtensionContainer { {UEAggregateMaximumBitRate-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+UEAggregateMaximumBitRate-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+UEAppLayerMeasConfigInfo ::= SEQUENCE {
+ qOEReference QOEReference,
+ qOEMeasConfigAppLayerID QOEMeasConfAppLayerID OPTIONAL,
+ serviceType ServiceType,
+ qOEMeasStatus QOEMeasStatus OPTIONAL,
+ containerAppLayerMeasConfig ContainerAppLayerMeasConfig OPTIONAL,
+ mDTAlignmentInfo MDTSalignmentInfo OPTIONAL,
+ measCollectionEntityIPAddress MeasCollectionEntityIPAddress OPTIONAL,
+ areaScopeOfQMC AreaScopeOfQMC OPTIONAL,
+```
+
+```
+
+s-NSSAIIListQoE S-NSSAIIListQoE OPTIONAL,
+availableRVQoEMetrics AvailableRVQoEMetrics OPTIONAL,
+iE-Extension ProtocolExtensionContainer { {UEAppLayerMeasConfigInfo-ExtIEs} } OPTIONAL,
+...
+}
+
+```
+
+```
+
+UEAppLayerMeasConfigInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ { ID id-MBSCommServiceType CRITICALITY ignore EXTENSION MBSCommServiceType PRESENCE optional }|
+ { ID id-AssistanceInformationQoE-Meas CRITICALITY ignore EXTENSION AssistanceInformationQoE-Meas PRESENCE optional }|
+ { ID id-QoERVQoEReportingPaths CRITICALITY ignore EXTENSION QoERVQoEReportingPaths PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+UEContextKeptIndicator ::= ENUMERATED {true, ...}
+
+```
+
+```
+
+UEContextID ::= CHOICE {
+ rRCResume UEContextIDforRRCResume,
+ rRCReestablishment UEContextIDforRRCReestablishment,
+ choice-extension ProtocolIE-Single-Container { {UEContextID-ExtIEs} }
+}
+
+```
+
+```
+UEContextID-ExtIEs XNAP-PROTOCOL-IES ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+UEContextIDforRRRCResume ::= SEQUENCE {
+```
+
+```
+ i-rnti I-RNTI,
+```
+
+```
+ allocated-c-rnti C-RNTI,
+```
+
+```
+ accessPCI NG-RAN-CellPCI,
+```
+
+```
+ iE-Extension ProtocolExtensionContainer { {UEContextIDforRRRCResume-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+UEContextIDforRRRCResume-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+ ...
+```
+
+```
+}
+```
+
+```
+UEContextIDforRRRCReestablishment ::= SEQUENCE {
+```
+
+```
+ c-rnti C-RNTI,
+```
+
+```
+ failureCellPCI NG-RAN-CellPCI,
+```
+
+```
+ iE-Extension ProtocolExtensionContainer { {UEContextIDforRRRCReestablishment-ExtIEs} } OPTIONAL,
+```
+
+```
+ ...
+```
+
+}
+
+UEContextIDforRRCREestablishment-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+UEContextInfoRetrUECtxtResp ::= SEQUENCE {
+
+| | | |
+|--------------------------------------|---------------------------------------------------------------------|-----------|
+| ng-c-UE-signalling-ref | AMF-UE-NGAP-ID, | |
+| signalling-TNL-at-source | CPTransportLayerInformation, | |
+| ueSecurityCapabilities | UESecurityCapabilities, | |
+| securityInformation | AS-SecurityInformation, | |
+| ue-AMBR | UEAggregateMaximumBitRate, | |
+| pduSessionResourcesToBeSetup-List | PDUSessionResourcesToBeSetup-List, | |
+| rrc-Context | OCTET STRING, | |
+| mobilityRestrictionList | MobilityRestrictionList | OPTIONAL, |
+| indexToRatFrequencySelectionPriority | RFSP-Index | OPTIONAL, |
+| iE-Extension | ProtocolExtensionContainer { {UEContextInfoRetrUECtxtResp-ExtIEs} } | OPTIONAL, |
+| ... | | |
+
+}
+
+UEContextInfoRetrUECtxtResp-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+| | | | |
+|------------------------------------------------|--------------------|--------------------------------------------------|---------------------|
+| { ID id-FiveGCMobilityRestrictionListContainer | CRITICALITY ignore | EXTENSION FiveGCMobilityRestrictionListContainer | PRESENCE optional } |
+|------------------------------------------------|--------------------|--------------------------------------------------|---------------------|
+
+```
+
+ { ID id-NRUESidelinkAggregateMaximumBitRate CRITICALITY ignore EXTENSION NRUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+ { ID id-LTEUESidelinkAggregateMaximumBitRate CRITICALITY ignore EXTENSION LTEUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+ { ID id-UERadioCapabilityID CRITICALITY reject EXTENSION UERadioCapabilityID PRESENCE optional }|
+ { ID id-MBS-SessionInformation-List CRITICALITY ignore EXTENSION MBS-SessionInformation-List PRESENCE optional }|
+ { ID id-NoPDUSessionIndication CRITICALITY ignore EXTENSION NoPDUSessionIndication PRESENCE optional }|
+ { ID id-FiveGProSeUEPC5AggregateMaximumBitRate CRITICALITY ignore EXTENSION NRUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+ { ID id-UESliceMaximumBitRateList CRITICALITY ignore EXTENSION UESliceMaximumBitRateList PRESENCE optional }|
+ { ID id-PositioningInformation CRITICALITY ignore EXTENSION PositioningInformation PRESENCE optional }|
+ { ID id-NRA2XUEPC5AggregateMaximumBitRate CRITICALITY ignore EXTENSION NRUESidelinkAggregateMaximumBitRate PRESENCE optional }|
+ { ID id-LTEA2XUEPC5AggregateMaximumBitRate CRITICALITY ignore EXTENSION LTEUESidelinkAggregateMaximumBitRate PRESENCE optional },
+ ...
+}
+
+```
+
+```
+
+UEHistoryInformation ::= SEQUENCE (SIZE(1..maxnoofCellsInUEHistoryInfo)) OF LastVisitedCell-Item
+
+```
+
+```
+
+UEHistoryInformationFromTheUE ::= CHOICE {
+ nR NRMobilityHistoryReport,
+ choice-extension ProtocolIE-Single-Container { {UEHistoryInformationFromTheUE-ExtIEs} }
+}
+
+```
+
+```
+
+UEHistoryInformationFromTheUE-ExtIEs XNAP-PROTOCOL-IES ::= {
+
+```
+
+```
+ ...
+}
+
+UEIdentityIndexValue ::= CHOICE {
+ indexLength10 BIT STRING (SIZE(10)),
+ choice-extension ProtocolIE-Single-Container { {UEIdentityIndexValue-ExtIEs} }
+}
+
+UEIdentityIndexValue-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+UEIdentityIndexList-MBSGroupPaging ::= SEQUENCE (SIZE(1..maxnoofUEIDIndicesforMBSPaging)) OF UEIdentityIndexList-MBSGroupPaging-Item
+
+UEIdentityIndexList-MBSGroupPaging-Item ::= SEQUENCE {
+ ueIdentityIndexList-MBSGroupPagingValue UEIdentityIndexList-MBSGroupPagingValue,
+ pagingDRX UESpecificDRX OPTIONAL,
+ iE-Extension ProtocolExtensionContainer { {UEIdentityIndexList-MBSGroupPaging-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UEIdentityIndexList-MBSGroupPaging-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+```
+
+```
+...
+}
+
+UEIdentityIndexList-MBSGroupPagingValue ::= CHOICE {
+ uEIdentityIndexValueMBSGroupPaging BIT STRING (SIZE(10)),
+ choice-extension ProtocolIE-Single-Container { {UEIdentityIndexValueMBSGroupPaging-ExtIEs} }
+}
+
+UEIdentityIndexValueMBSGroupPaging-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+UERadioCapabilityForPaging ::= SEQUENCE {
+ uERadioCapabilityForPagingOfNR UERadioCapabilityForPagingOfNR OPTIONAL,
+ uERadioCapabilityForPagingOfEUTRA UERadioCapabilityForPagingOfEUTRA OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { {UERadioCapabilityForPaging-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UERadioCapabilityForPaging-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+}
+
+UERadioCapabilityForPagingOfNR ::= OCTET STRING
+
+UERadioCapabilityForPagingOfEUTRA ::= OCTET STRING
+
+UERadioCapabilityID ::= OCTET STRING
+
+```
+UERANPagingIdentity ::= CHOICE {
+ i-RNTI-full BIT STRING ( SIZE (40)),
+ choice-extension ProtocolIE-Single-Container { {UERANPagingIdentity-ExtIEs} }
+}
+```
+
+```
+UERANPagingIdentity-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+```
+
+```
+UERLFReportContainer ::= CHOICE {
+ nR-UERLFReportContainer UERLFReportContainerNR,
+ lTE-UERLFReportContainer UERLFReportContainerLTE,
+ choice-Extension ProtocolIE-Single-Container { {UERLFReportContainer-ExtIEs} }
+}
+```
+
+```
+UERLFReportContainer-ExtIEs XNAP-PROTOCOL-IES ::= {
+ {ID id-UERLFReportContainerLTEExtension CRITICALITY ignore TYPE UERLFReportContainerLTEExtension PRESENCE mandatory},
+ ...
+}
+
+UERLFReportContainerLTE ::= OCTET STRING
+
+-- This IE is a transparent container and includes the RLF-Report-r9 IE contained in the UEInformationResponse message as defined in TS 36.331 [14].
+
+UERLFReportContainerLTEExtension ::= SEQUENCE {
+ ueRLFReportContainerLTE UERLFReportContainerLTE,
+ ueRLFReportContainerLTEExtendBand UERLFReportContainerLTEExtendBand,
+ iE-Extensions ProtocolExtensionContainer { { UERLFReportContainerLTEExtension-ExtIEs } } OPTIONAL,
+ ...
+}
+
+UERLFReportContainerLTEExtendBand ::= OCTET STRING
+
+-- This IE is a transparent container and includes the rLF-Report-v9e0 contained in the UEInformationResponse message as defined in TS 36.331 [14].
+
+UERLFReportContainerLTEExtension-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+}
+
+UERLFReportContainerNR ::= OCTET STRING
+
+-- This IE is a transparent container and includes the nr-RLF-Report-r16 IE contained in the UEInformationResponse message as defined in TS 38.331
+[10].
+
+UESliceMaximumBitRateList ::= SEQUENCE (SIZE(1.. maxnoofSMBR)) OF UESliceMaximumBitRate-Item
+
+UESliceMaximumBitRate-Item ::= SEQUENCE {
+ s-NSSAI S-NSSAI,
+ dl-UE-Slice-MBR BitRate,
+ ul-UE-Slice-MBR BitRate,
+ iE-Extensions ProtocolExtensionContainer { { UESliceMaximumBitRate-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UESliceMaximumBitRate-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UESecurityCapabilities ::= SEQUENCE {
+ nr-EncryptionAlgorithms BIT STRING {neal-128(1),
+```
+
+```
+ nea2-128(2),
+ nea3-128(3)} (SIZE(16, ...)),
+nr-IntegrityProtectionAlgorithms BIT STRING {nia1-128(1),
+ nia2-128(2),
+ nia3-128(3)} (SIZE(16, ...)),
+e-utra-EncryptionAlgorithms BIT STRING {eea1-128(1),
+ eea2-128(2),
+ eea3-128(3)} (SIZE(16, ...)),
+e-utra-IntegrityProtectionAlgorithms BIT STRING {eia1-128(1),
+ eia2-128(2),
+ eia3-128(3)} (SIZE(16, ...)),
+iE-Extension ProtocolExtensionContainer { {UESecurityCapabilities-ExtIEs} } OPTIONAL,
+...
+}
+
+UESecurityCapabilities-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UESpecificDRX ::= ENUMERATED {
+ v32,
+ v64,
+ v128,
+```
+
+```
+v256,
+...
+}
+
+ULConfiguration ::= SEQUENCE {
+ uL-PDCP UL-UE-Configuration,
+ iE-Extensions ProtocolExtensionContainer { {ULConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ULConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UL-UE-Configuration ::= ENUMERATED {no-data, shared, only, ...}
+
+ULFI terminating-BHInfo ::= SEQUENCE {
+ ingressBAPRoutingID BAPRoutingID,
+ ingressBHRLCCHID BHRLCChannelID,
+ iE-Extensions ProtocolExtensionContainer { { ULFI terminating-BHInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+ULF1Terminating-BHInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ULNonF1Terminating-BHInfo ::= SEQUENCE {
+ egressBAPRoutingID BAPRoutingID,
+ egressBHRLCCHID BHRLCChannelID,
+ nexthopBAPAddress BAPAddress,
+ iE-Extensions ProtocolExtensionContainer { { ULNonF1Terminating-BHInfo-ExtIEs} } OPTIONAL,
+ ...
+}
+
+ULNonF1Terminating-BHInfo-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+ULForwarding ::= ENUMERATED {ul-forwarding-proposed, ...}
+
+ULForwardingProposal ::= ENUMERATED {ul-forwarding-proposed, ...}
+
+UL-GBR-PRB-usage ::= INTEGER (0..100)
+```
+
+UL-GBR-PRB-usage-for-MIMO ::= INTEGER (0..100)
+
+UL-non-GBR-PRB-usage ::= INTEGER (0..100)
+
+UL-non-GBR-PRB-usage-for-MIMO ::= INTEGER (0..100)
+
+UL-Total-PRB-usage ::= INTEGER (0..100)
+
+UL-Total-PRB-usage-for-MIMO ::= INTEGER (0..100)
+
+UPTransportLayerInformation ::= CHOICE {
+ gtpTunnel GTPtunnelTransportLayerInformation,
+ choice-extension ProtocolIE-Single-Container { UPTransportLayerInformation-ExtIEs }
+}
+
+UPTransportLayerInformation-ExtIEs XNAP-PROTOCOL-IES ::= {
+ ...
+}
+
+UPTransportParameters ::= SEQUENCE (SIZE(1..maxnoofSCellGroupsplus1)) OF UPTransportParametersItem
+
+UPTransportParametersItem ::= SEQUENCE {
+ upTNLInfo UPTransportLayerInformation,
+ cellGroupID CellGroupID,
+ iE-Extension ProtocolExtensionContainer { {UPTransportParametersItem-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UPTransportParametersItem-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UserPlaneTrafficActivityReport ::= ENUMERATED {inactive, re-activated, ...}
+
+URIaddress ::= VisibleString
+
+UEAssociatedInfoResult-List ::= SEQUENCE (SIZE(1..maxnoofUEReports)) OF UEAssociatedInfoResult-Item
+
+UEAssociatedInfoResult-Item ::= SEQUENCE {
+
+```
+ ueAssistantIdentifier NG-RANnodeUEXnAPID,
+ uEPerformance UEPeformance OPTIONAL,
+ measuredUETrajectory MeasuredUETrajectory OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { UEAssociatedInfoResult-Item-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UEAssociatedInfoResult-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+
+UEPerformance ::= SEQUENCE {
+ dL-UE-AverageThroughput BitRate OPTIONAL,
+ uL-UE-AverageThroughput BitRate OPTIONAL,
+ uE-AveragePacketDelay AveragePacketDelay OPTIONAL,
+ uE-AveragePacketLossDL PacketLossRate OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { UEPeformance-ExtIEs} } OPTIONAL,
+ ...
+}
+
+UEPerformance-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+UEPerformanceCollectionConfiguration ::= SEQUENCE {
+ collectionTimeDuration INTEGER(1..5000, ...),
+ iE-Extensions ProtocolExtensionContainer { { UEPerformanceCollectionConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+UEPerformanceCollectionConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+UETrajectoryCollectionConfiguration ::= SEQUENCE {
+ collectionTimeDuration INTEGER (1..4096, ...),
+ numberOfVisitedCells INTEGER (1..16, ...) OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { UETrajectoryCollectionConfiguration-ExtIEs} } OPTIONAL,
+ ...
+}
+```
+
+```
+UETrajectoryCollectionConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+-- V
+
+VehicleUE ::= ENUMERATED {
+
+authorized,
+
+not-authorized,
+
+...
+
+}
+
+VolumeTimedReportList ::= SEQUENCE (SIZE(1..maxnooftimeperiods)) OF VolumeTimedReport-Item
+
+VolumeTimedReport-Item ::= SEQUENCE {
+
+startTimeStamp OCTET STRING (SIZE(4)),
+
+endTimeStamp OCTET STRING (SIZE(4)),
+
+usageCountUL INTEGER (0..18446744073709551615),
+
+usageCountDL INTEGER (0..18446744073709551615),
+
+iE-Extensions ProtocolExtensionContainer { {VolumeTimedReport-Item-ExtIEs} } OPTIONAL,
+
+...
+
+}
+
+VolumeTimedReport-Item-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+
+...
+
+}
+
+-- W
+
+```
+WLANMeasurementConfiguration ::= SEQUENCE {
+ wlanMeasConfig WLANMeasConfig,
+ wlanMeasConfigNameList WLANMeasConfigNameList OPTIONAL,
+ wlan-rssi ENUMERATED {true, ...} OPTIONAL,
+ wlan-rtt ENUMERATED {true, ...} OPTIONAL,
+ iE-Extensions ProtocolExtensionContainer { { WLANMeasurementConfiguration-ExtIEs } } OPTIONAL,
+ ...
+}
+```
+
+```
+WLANMeasurementConfiguration-ExtIEs XNAP-PROTOCOL-EXTENSION ::= {
+ ...
+}
+```
+
+```
+WLANMeasConfigNameList ::= SEQUENCE (SIZE(1..maxnoofWLANName)) OF WLANName
+```
+
+```
+WLANMeasConfig ::= ENUMERATED {setup, ...}
+```
+
+```
+WLANName ::= OCTET STRING (SIZE (1..32))
+```
+
+-- X
+
+XnBenefitValue ::= INTEGER (1..8, ...)
+
+-- Y
+
+-- Z
+
+END
+
+-- ASN1STOP
+
+### 9.3.6 Common definitions
+
+-- ASN1START
+
+-- \*\*\*\*\*
+
+--
+
+-- Common definitions
+
+--
+
+-- \*\*\*\*\*
+
+XnAP-CommonDataTypes {
+
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+
+ngran-access (22) modules (3) xnap (2) version1 (1) xnap-CommonDataTypes (3) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- \*\*\*\*\*
+
+--
+
+-- Extension constants
+
+--
+
+-- \*\*\*\*\*
+
+maxPrivateIEs INTEGER ::= 65535
+
+maxProtocolExtensions INTEGER ::= 65535
+
+maxProtocolIEs INTEGER ::= 65535
+
+-- \*\*\*\*\*
+
+--
+
+-- Common Data Types
+
+--
+
+-- \*\*\*\*\*
+
+Criticality ::= ENUMERATED { reject, ignore, notify }
+
+```
+
+Presence ::= ENUMERATED { optional, conditional, mandatory }
+
+PrivateIE-ID ::= CHOICE {
+ local INTEGER (0.. maxPrivateIEs),
+ global OBJECT IDENTIFIER
+}
+
+ProcedureCode ::= INTEGER (0..255)
+
+ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs)
+
+TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome}
+
+END
+
+-- ASN1STOP
+
+```
+
+### 9.3.7 Constant definitions
+
+```
+
+-- ASN1START
+
+-- *****
+
+--
+
+```
+
+-- Constant definitions
+
+--
+
+-- \*\*\*\*\*
+
+XnAP-Constants {
+
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+
+ngran-Access (22) modules (3) xnap (2) version1 (1) xnap-Constants (4) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+IMPORTS
+
+ProcedureCode,
+
+ProtocolIE-ID
+
+FROM XnAP-CommonDataTypes;
+
+-- \*\*\*\*\*
+
+--
+
+-- Elementary Procedures
+
+--
+
+-- \*\*\*\*\*
+
+| | |
+|---------------------------------------------------------|----------------------|
+| id-handoverPreparation | ProcedureCode ::= 0 |
+| id-sNStatusTransfer | ProcedureCode ::= 1 |
+| id-handoverCancel | ProcedureCode ::= 2 |
+| id-retrieveUEContext | ProcedureCode ::= 3 |
+| id-rANPaging | ProcedureCode ::= 4 |
+| id-xnUAddressIndication | ProcedureCode ::= 5 |
+| id-uEContextRelease | ProcedureCode ::= 6 |
+| id-sNGRANnodeAdditionPreparation | ProcedureCode ::= 7 |
+| id-sNGRANnodeReconfigurationCompletion | ProcedureCode ::= 8 |
+| id-mNGRANnodeinitiatedSNGRANnodeModificationPreparation | ProcedureCode ::= 9 |
+| id-sNGRANnodeinitiatedSNGRANnodeModificationPreparation | ProcedureCode ::= 10 |
+| id-mNGRANnodeinitiatedSNGRANnodeRelease | ProcedureCode ::= 11 |
+| id-sNGRANnodeinitiatedSNGRANnodeRelease | ProcedureCode ::= 12 |
+| id-sNGRANnodeCounterCheck | ProcedureCode ::= 13 |
+| id-sNGRANnodeChange | ProcedureCode ::= 14 |
+| id-rRCTransfer | ProcedureCode ::= 15 |
+| id-xnRemoval | ProcedureCode ::= 16 |
+| id-xnSetup | ProcedureCode ::= 17 |
+| id-nGRANnodeConfigurationUpdate | ProcedureCode ::= 18 |
+| id-cellActivation | ProcedureCode ::= 19 |
+| id-reset | ProcedureCode ::= 20 |
+| id-errorIndication | ProcedureCode ::= 21 |
+| id-privateMessage | ProcedureCode ::= 22 |
+
+| | |
+|---------------------------------------|----------------------|
+| id-notificationControl | ProcedureCode ::= 23 |
+| id-activityNotification | ProcedureCode ::= 24 |
+| id-e-UTRA-NR-CellResourceCoordination | ProcedureCode ::= 25 |
+| id-secondaryRATDataUsageReport | ProcedureCode ::= 26 |
+| id-deactivateTrace | ProcedureCode ::= 27 |
+| id-traceStart | ProcedureCode ::= 28 |
+| id-handoverSuccess | ProcedureCode ::= 29 |
+| id-conditionalHandoverCancel | ProcedureCode ::= 30 |
+| id-earlyStatusTransfer | ProcedureCode ::= 31 |
+| id-failureIndication | ProcedureCode ::= 32 |
+| id-handoverReport | ProcedureCode ::= 33 |
+| id-resourceStatusReportingInitiation | ProcedureCode ::= 34 |
+| id-resourceStatusReporting | ProcedureCode ::= 35 |
+| id-mobilitySettingsChange | ProcedureCode ::= 36 |
+| id-accessAndMobilityIndication | ProcedureCode ::= 37 |
+| id-cellTrafficTrace | ProcedureCode ::= 38 |
+| id-RANMulticastGroupPaging | ProcedureCode ::= 39 |
+| id-scgFailureInformationReport | ProcedureCode ::= 40 |
+| id-ProcedureCode41-NotToBeUsed | ProcedureCode ::= 41 |
+| id-scgFailureTransfer | ProcedureCode ::= 42 |
+| id-f1CTrafficTransfer | ProcedureCode ::= 43 |
+| id-iABTransportMigrationManagement | ProcedureCode ::= 44 |
+| id-iABTransportMigrationModification | ProcedureCode ::= 45 |
+
+```
+
+id-iABResourceCoordination ProcedureCode ::= 46
+id-retrieveUEContextConfirm ProcedureCode ::= 47
+id-cPCCancel ProcedureCode ::= 48
+id-partialUEContextTransfer ProcedureCode ::= 49
+id-rachIndication ProcedureCode ::= 50
+id-dataCollectionReportingInitiation ProcedureCode ::= 51
+id-dataCollectionReporting ProcedureCode ::= 52
+
+```
+
+```
+
+-- *****
+--
+-- Lists
+--
+-- *****
+
+```
+
+```
+
+maxEARFCN INTEGER ::= 262143
+maxnoofAllowedAreas INTEGER ::= 16
+maxnoofAMFRegions INTEGER ::= 16
+maxnoofAoIs INTEGER ::= 64
+maxnoofBluetoothName INTEGER ::= 4
+maxnoofBPLMNs INTEGER ::= 12
+maxnoofCAGs INTEGER ::= 12
+
+```
+
+| | |
+|----------------------------------|-------------------|
+| maxnoofCAGsperPLMN | INTEGER ::= 256 |
+| maxnoofCellIDforMDT | INTEGER ::= 32 |
+| maxnoofCellsinAoI | INTEGER ::= 256 |
+| maxnoofCellsineUEHistoryInfo | INTEGER ::= 16 |
+| maxnoofCellsineNG-RANnode | INTEGER ::= 16384 |
+| maxnoofCellsineRNA | INTEGER ::= 32 |
+| maxnoofCellsUEMovingTrajectory | INTEGER ::= 16 |
+| maxnoofDRBs | INTEGER ::= 32 |
+| maxnoofEUTRABands | INTEGER ::= 16 |
+| maxnoofEUTRABPLMNs | INTEGER ::= 6 |
+| maxnoofEPLMNs | INTEGER ::= 15 |
+| maxnoofExtSliceItems | INTEGER ::= 65535 |
+| maxnoofEPLMNsplus1 | INTEGER ::= 16 |
+| maxnoofForbiddenTACs | INTEGER ::= 4096 |
+| maxnoofFreqforMDT | INTEGER ::= 8 |
+| maxnoofMBSFNEUTRA | INTEGER ::= 8 |
+| maxnoofMDTPLMNs | INTEGER ::= 16 |
+| maxnoofMultiConnectivityMinusOne | INTEGER ::= 3 |
+| maxnoofNeighbours | INTEGER ::= 1024 |
+| maxnoofNeighPCIforMDT | INTEGER ::= 32 |
+| maxnoofNIDs | INTEGER ::= 12 |
+| maxnoofNRCellBands | INTEGER ::= 32 |
+| maxnoofPLMNs | INTEGER ::= 16 |
+
+maxnoofPDUSessions INTEGER ::= 256
+
+maxnoofProtectedResourcePatterns INTEGER ::= 16
+
+maxnoofQoSFlows INTEGER ::= 64
+
+maxnoofQoSParaSets INTEGER ::= 8
+
+maxnoofRANAreaCodes INTEGER ::= 32
+
+maxnoofRANAreasinRNA INTEGER ::= 16
+
+maxnoofRANNodesinAoI INTEGER ::= 64
+
+maxnoofSCellGroups INTEGER ::= 3
+
+maxnoofSCellGroupsplus1 INTEGER ::= 4
+
+maxnoofSensorName INTEGER ::= 3
+
+maxnoofSliceItems INTEGER ::= 1024
+
+maxnoofSNPNIDs INTEGER ::= 12
+
+maxnoofsupportedPLMNs INTEGER ::= 12
+
+maxnoofsupportedTACs INTEGER ::= 256
+
+maxnoofTAforMDT INTEGER ::= 8
+
+maxnoofTAI INTEGER ::= 16
+
+maxnoofTAIsinAoI INTEGER ::= 16
+
+maxnooftimeperiods INTEGER ::= 2
+
+maxnoofTNLAssociations INTEGER ::= 32
+
+maxnoofUEContexts INTEGER ::= 8192
+
+maxNRARFCN INTEGER ::= 3279165
+
+maxNrOfErrors INTEGER ::= 256
+
+maxnoofslots INTEGER ::= 5120
+
+maxnoofExtTLAs INTEGER ::= 16
+
+maxnoofGTPTLAs INTEGER ::= 16
+
+maxnoofCHOCells INTEGER ::= 8
+
+maxnoofPC5QoSFlows INTEGER ::= 2064
+
+maxnoofSSBAreas INTEGER ::= 64
+
+maxnoofRAReports INTEGER ::= 64
+
+maxnoofNRSCSs INTEGER ::= 5
+
+maxnoofPhysicalResourceBlocks INTEGER ::= 275
+
+maxnoofAdditionalPDCPDuplicationTNL INTEGER ::= 2
+
+maxnoofRLCDuplicationstate INTEGER ::= 3
+
+maxnoofWLANName INTEGER ::= 4
+
+maxnoofNonAnchorCarrierFreqConfig INTEGER ::= 15
+
+maxnoofDataForwardingTunneltoE-UTRAN INTEGER ::= 256
+
+maxnoofMBSFSAAs INTEGER ::= 256
+
+maxnoofUEIDIndicesforMBSPaging INTEGER ::= 4096
+
+maxnoofMBSQoSFlows INTEGER ::= 64
+
+maxnoofMRBs INTEGER ::= 32
+
+maxnoofCellsforMBS INTEGER ::= 8192
+
+maxnoofMBSServiceAreaInformation INTEGER ::= 256
+
+maxnoofTAIforMBS INTEGER ::= 1024
+
+maxnoofAssociatedMBSSessions INTEGER ::= 32
+
+maxnoofMBSSessions INTEGER ::= 256
+
+maxnoofSuccessfulHOReports INTEGER ::= 64
+
+maxnoofPSCellsPerSN INTEGER ::= 8
+
+maxnoofNR-UChannelIDs INTEGER ::= 16
+
+maxnoofCellsinCHO INTEGER ::= 8
+
+maxnoofCHOexecutioncond INTEGER ::= 2
+
+maxnoofServedCellsIAB INTEGER ::= 512
+
+maxnoofServingCells INTEGER ::= 32
+
+maxnoofBHInfo INTEGER ::= 1024
+
+maxnoofTrafficIndexEntries INTEGER ::= 1024
+
+maxnoofTLAsIAB INTEGER ::= 1024
+
+maxnoofBAPControlPDURLCCHs INTEGER ::= 2
+
+maxnoofIABSTCInfo INTEGER ::= 45
+
+maxnoofSymbols INTEGER ::= 14
+
+maxnoofDUFSlots INTEGER ::= 320
+
+maxnoofHSNASlots INTEGER ::= 5120
+
+maxnoofRBsetsPerCell INTEGER ::= 8
+
+maxnoofRBsetsPerCell1 INTEGER ::= 7
+
+maxnoofChildIABNodes INTEGER ::= 1024
+
+maxnoofPSCellCandidates INTEGER ::= 8
+
+maxnoofTargetSNs INTEGER ::= 8
+
+maxnoofUEAppLayerMeas INTEGER ::= 16
+
+maxnoofSNSSAIforQMC INTEGER ::= 16
+
+maxnoofCellIDforQMC INTEGER ::= 32
+
+maxnoofPLMNforQMC INTEGER ::= 16
+
+maxnoofTAforQMC INTEGER ::= 8
+
+maxnoofMTItems INTEGER ::= 16
+
+maxnoofCSIRSconfigurations INTEGER ::= 96
+
+maxnoofCSIRSneighbourCells INTEGER ::= 16
+
+maxnoofCSIRSneighbourCellsInMTC INTEGER ::= 16
+
+maxnoofNeighbour-NG-RAN-Nodes INTEGER ::= 256
+
+maxnoofSRBs INTEGER ::= 5
+
+maxnoofSMBR INTEGER ::= 8
+
+maxnoofNSAGs INTEGER ::= 256
+
+maxnoofTargetSNsMinusOne INTEGER ::= 7
+
+maxnoofThresholdsForExcessPacketDelay INTEGER ::= 255
+
+maxnoofESPNs INTEGER ::= 15
+
+maxnoofSuccessfulPSCellChangeReports INTEGER ::= 64
+
+maxnoofUEsforRAReportIndications INTEGER ::= 64
+
+maxnoofPSCellsinCPAC INTEGER ::= 8
+
+maxnoofCPACexecutioncond INTEGER ::= 2
+
+maxnoofLBTFailureInformation INTEGER ::= 64
+
+maxnoofCellsTrajectoryPredict INTEGER ::= 16
+
+maxnoofCellsTrajectory INTEGER ::= 16
+
+maxFailedCellMeasObjects INTEGER ::= 124
+
+maxFailedMeasPerNode INTEGER ::= 124
+
+maxnoofUERReports INTEGER ::= 16
+
+maxnoofCandidateRelayUEs INTEGER ::= 32
+
+maxnoofCAGforMDT INTEGER ::= 256
+
+maxnoofMDTSNPNs INTEGER ::= 16
+
+maxnoofSecurityConfigurations INTEGER ::= 8
+
+-- \*\*\*\*\*
+
+--
+
+-- IEs
+
+--
+
+-- \*\*\*\*\*
+
+id-ActivatedServedCells ProtocolIE-ID ::= 0
+
+id-ActivationIDforCellActivation ProtocolIE-ID ::= 1
+
+id-admittedSplitSRB ProtocolIE-ID ::= 2
+
+id-admittedSplitSRBrelease ProtocolIE-ID ::= 3
+
+id-AMF-Region-Information ProtocolIE-ID ::= 4
+
+id-AssistanceDataForRANPaging ProtocolIE-ID ::= 5
+
+id-BearersSubjectToCounterCheck ProtocolIE-ID ::= 6
+
+id-Cause ProtocolIE-ID ::= 7
+
+id-cellAssistanceInfo-NR ProtocolIE-ID ::= 8
+
+id-ConfigurationUpdateInitiatingNodeChoice ProtocolIE-ID ::= 9
+
+id-CriticalityDiagnostics ProtocolIE-ID ::= 10
+
+id-XnUAddressInfoperPDUSession-List ProtocolIE-ID ::= 11
+
+| | |
+|--------------------------------------------|----------------------|
+| id-DRBsSubjectToStatusTransfer-List | ProtocolIE-ID ::= 12 |
+| id-ExpectedUEBehaviour | ProtocolIE-ID ::= 13 |
+| id-GlobalNG-RAN-node-ID | ProtocolIE-ID ::= 14 |
+| id-GUAMI | ProtocolIE-ID ::= 15 |
+| id-indexToRatFrequSelectionPriority | ProtocolIE-ID ::= 16 |
+| id-initiatingNodeType-ResourceCoordRequest | ProtocolIE-ID ::= 17 |
+| id-List-of-served-cells-E-UTRA | ProtocolIE-ID ::= 18 |
+| id-List-of-served-cells-NR | ProtocolIE-ID ::= 19 |
+| id-LocationReportingInformation | ProtocolIE-ID ::= 20 |
+| id-MAC-I | ProtocolIE-ID ::= 21 |
+| id-MaskedIMEISV | ProtocolIE-ID ::= 22 |
+| id-M-NG-RANnodeUEXnAPID | ProtocolIE-ID ::= 23 |
+| id-MN-to-SN-Container | ProtocolIE-ID ::= 24 |
+| id-MobilityRestrictionList | ProtocolIE-ID ::= 25 |
+| id-new-NG-RAN-Cell-Identity | ProtocolIE-ID ::= 26 |
+| id-newNG-RANnodeUEXnAPID | ProtocolIE-ID ::= 27 |
+| id-UEReportRRCTransfer | ProtocolIE-ID ::= 28 |
+| id-oldNG-RANnodeUEXnAPID | ProtocolIE-ID ::= 29 |
+| id-OldtoNewNG-RANnodeResumeContainer | ProtocolIE-ID ::= 30 |
+| id-PagingDRX | ProtocolIE-ID ::= 31 |
+| id-PCellID | ProtocolIE-ID ::= 32 |
+| id-PDCPChangeIndication | ProtocolIE-ID ::= 33 |
+| id-PDUSessionAdmittedAddedAddReqAck | ProtocolIE-ID ::= 34 |
+
+| | |
+|------------------------------------------|----------------------|
+| id-PDUSessionAdmittedModSNModConfirm | ProtocolIE-ID ::= 35 |
+| id-PDUSessionAdmitted-SNModResponse | ProtocolIE-ID ::= 36 |
+| id-PDUSessionNotAdmittedAddReqAck | ProtocolIE-ID ::= 37 |
+| id-PDUSessionNotAdmitted-SNModResponse | ProtocolIE-ID ::= 38 |
+| id-PDUSessionReleasedList-RelConf | ProtocolIE-ID ::= 39 |
+| id-PDUSessionReleasedSNModConfirm | ProtocolIE-ID ::= 40 |
+| id-PDUSessionResourcesActivityNotifyList | ProtocolIE-ID ::= 41 |
+| id-PDUSessionResourcesAdmitted-List | ProtocolIE-ID ::= 42 |
+| id-PDUSessionResourcesNotAdmitted-List | ProtocolIE-ID ::= 43 |
+| id-PDUSessionResourcesNotifyList | ProtocolIE-ID ::= 44 |
+| id-PDUSession-SNChangeConfirm-List | ProtocolIE-ID ::= 45 |
+| id-PDUSession-SNChangeRequired-List | ProtocolIE-ID ::= 46 |
+| id-PDUSessionToBeAddedAddReq | ProtocolIE-ID ::= 47 |
+| id-PDUSessionToBeModifiedSNModRequired | ProtocolIE-ID ::= 48 |
+| id-PDUSessionToBeReleasedList-RelRqd | ProtocolIE-ID ::= 49 |
+| id-PDUSessionToBeReleased-RelReq | ProtocolIE-ID ::= 50 |
+| id-PDUSessionToBeReleasedSNModRequired | ProtocolIE-ID ::= 51 |
+| id-RANPagingArea | ProtocolIE-ID ::= 52 |
+| id-PagingPriority | ProtocolIE-ID ::= 53 |
+| id-requestedSplitSRB | ProtocolIE-ID ::= 54 |
+| id-requestedSplitSRBrelease | ProtocolIE-ID ::= 55 |
+| id-ResetRequestTypeInfo | ProtocolIE-ID ::= 56 |
+| id-ResetResponseTypeInfo | ProtocolIE-ID ::= 57 |
+
+| | |
+|---------------------------------------------|----------------------|
+| id-RespondingNodeTypeConfigUpdateAck | ProtocolIE-ID ::= 58 |
+| id-respondingNodeType-ResourceCoordResponse | ProtocolIE-ID ::= 59 |
+| id-ResponseInfo-ReconfCompl | ProtocolIE-ID ::= 60 |
+| id-RRConfigIndication | ProtocolIE-ID ::= 61 |
+| id-RRResumeCause | ProtocolIE-ID ::= 62 |
+| id-SCGConfigurationQuery | ProtocolIE-ID ::= 63 |
+| id-selectedPLMN | ProtocolIE-ID ::= 64 |
+| id-ServedCellsToActivate | ProtocolIE-ID ::= 65 |
+| id-servedCellsToUpdate-E-UTRA | ProtocolIE-ID ::= 66 |
+| id-ServedCellsToUpdateInitiatingNodeChoice | ProtocolIE-ID ::= 67 |
+| id-servedCellsToUpdate-NR | ProtocolIE-ID ::= 68 |
+| id-s-ng-RANnode-SecurityKey | ProtocolIE-ID ::= 69 |
+| id-S-NG-RANnodeUE-AMBR | ProtocolIE-ID ::= 70 |
+| id-S-NG-RANnodeUEXnAPID | ProtocolIE-ID ::= 71 |
+| id-SN-to-MN-Container | ProtocolIE-ID ::= 72 |
+| id-sourceNG-RANnodeUEXnAPID | ProtocolIE-ID ::= 73 |
+| id-SplitSRB-RRCTransfer | ProtocolIE-ID ::= 74 |
+| id-TAISupport-list | ProtocolIE-ID ::= 75 |
+| id-TimeToWait | ProtocolIE-ID ::= 76 |
+| id-Target2SourceNG-RANnodeTranspContainer | ProtocolIE-ID ::= 77 |
+| id-targetCellGlobalID | ProtocolIE-ID ::= 78 |
+| id-targetNG-RANnodeUEXnAPID | ProtocolIE-ID ::= 79 |
+| id-target-S-NG-RANnodeID | ProtocolIE-ID ::= 80 |
+
+| | |
+|-----------------------------------|-----------------------|
+| id-TraceActivation | ProtocolIE-ID ::= 81 |
+| id-UEContextID | ProtocolIE-ID ::= 82 |
+| id-UEContextInfoHORequest | ProtocolIE-ID ::= 83 |
+| id-UEContextInfoRetrUECtxtResp | ProtocolIE-ID ::= 84 |
+| id-UEContextInfo-SNModRequest | ProtocolIE-ID ::= 85 |
+| id-UEContextKeptIndicator | ProtocolIE-ID ::= 86 |
+| id-UEContextRefAtSN-HORequest | ProtocolIE-ID ::= 87 |
+| id-UEHistoryInformation | ProtocolIE-ID ::= 88 |
+| id-UEIdentityIndexValue | ProtocolIE-ID ::= 89 |
+| id-UERANPagingIdentity | ProtocolIE-ID ::= 90 |
+| id-UESecurityCapabilities | ProtocolIE-ID ::= 91 |
+| id-UserPlaneTrafficActivityReport | ProtocolIE-ID ::= 92 |
+| id-XnRemovalThreshold | ProtocolIE-ID ::= 93 |
+| id-DesiredActNotificationLevel | ProtocolIE-ID ::= 94 |
+| id-AvailableDRBIDs | ProtocolIE-ID ::= 95 |
+| id-AdditionalDRBIDs | ProtocolIE-ID ::= 96 |
+| id-SpareDRBIDs | ProtocolIE-ID ::= 97 |
+| id-RequiredNumberOfDRBIDs | ProtocolIE-ID ::= 98 |
+| id-TNLA-To-Add-List | ProtocolIE-ID ::= 99 |
+| id-TNLA-To-Update-List | ProtocolIE-ID ::= 100 |
+| id-TNLA-To-Remove-List | ProtocolIE-ID ::= 101 |
+| id-TNLA-Setup-List | ProtocolIE-ID ::= 102 |
+| id-TNLA-Failed-To-Setup-List | ProtocolIE-ID ::= 103 |
+
+| | |
+|-----------------------------------------------|-----------------------|
+| id-PDUSessionToBeReleased-RelReqAck | ProtocolIE-ID ::= 104 |
+| id-S-NG-RANnodeMaxIPDataRate-UL | ProtocolIE-ID ::= 105 |
+| id-PDUSessionResourceSecondaryRATUsageList | ProtocolIE-ID ::= 107 |
+| id-Additional-UL-NG-U-TNLatUPF-List | ProtocolIE-ID ::= 108 |
+| id-SecondarydataForwardingInfoFromTarget-List | ProtocolIE-ID ::= 109 |
+| id-LocationInformationSNReporting | ProtocolIE-ID ::= 110 |
+| id-LocationInformationSN | ProtocolIE-ID ::= 111 |
+| id-LastE-UTRANPLMNIdentity | ProtocolIE-ID ::= 112 |
+| id-S-NG-RANnodeMaxIPDataRate-DL | ProtocolIE-ID ::= 113 |
+| id-MaxIPrate-DL | ProtocolIE-ID ::= 114 |
+| id-SecurityResult | ProtocolIE-ID ::= 115 |
+| id-S-NSSAI | ProtocolIE-ID ::= 116 |
+| id-MR-DC-ResourceCoordinationInfo | ProtocolIE-ID ::= 117 |
+| id-AMF-Region-Information-To-Add | ProtocolIE-ID ::= 118 |
+| id-AMF-Region-Information-To-Delete | ProtocolIE-ID ::= 119 |
+| id-OldQoSFlowMap-ULendmarkerexpected | ProtocolIE-ID ::= 120 |
+| id-RANPagingFailure | ProtocolIE-ID ::= 121 |
+| id-UERadioCapabilityForPaging | ProtocolIE-ID ::= 122 |
+| id-PDUSessionDataForwarding-SNModResponse | ProtocolIE-ID ::= 123 |
+| id-DRBsNotAdmittedSetupModifyList | ProtocolIE-ID ::= 124 |
+| id-Secondary-MN-Xn-U-TNLInfoatM | ProtocolIE-ID ::= 125 |
+| id-NE-DC-TDM-Pattern | ProtocolIE-ID ::= 126 |
+| id-PDUSessionCommonNetworkInstance | ProtocolIE-ID ::= 127 |
+
+| | |
+|-------------------------------------------|-----------------------|
+| id-BPLMN-ID-Info-EUTRA | ProtocolIE-ID ::= 128 |
+| id-BPLMN-ID-Info-NR | ProtocolIE-ID ::= 129 |
+| id-InterfaceInstanceIndication | ProtocolIE-ID ::= 130 |
+| id-S-NG-RANnode-Addition-Trigger-Ind | ProtocolIE-ID ::= 131 |
+| id-DefaultDRB-Allowed | ProtocolIE-ID ::= 132 |
+| id-DRB-IDs-takenintouse | ProtocolIE-ID ::= 133 |
+| id-SplitSessionIndicator | ProtocolIE-ID ::= 134 |
+| id-CNTypeRestrictionsForEquivalent | ProtocolIE-ID ::= 135 |
+| id-CNTypeRestrictionsForServing | ProtocolIE-ID ::= 136 |
+| id-DRBs-transferred-to-MN | ProtocolIE-ID ::= 137 |
+| id-ULForwardingProposal | ProtocolIE-ID ::= 138 |
+| id-EndpointIPAddressAndPort | ProtocolIE-ID ::= 139 |
+| id-IntendedTDD-DL-ULConfiguration-NR | ProtocolIE-ID ::= 140 |
+| id-TNLConfigurationInfo | ProtocolIE-ID ::= 141 |
+| id-PartialListIndicator-NR | ProtocolIE-ID ::= 142 |
+| id-MessageOversizeNotification | ProtocolIE-ID ::= 143 |
+| id-CellAndCapacityAssistanceInfo-NR | ProtocolIE-ID ::= 144 |
+| id-NG-RANTraceID | ProtocolIE-ID ::= 145 |
+| id-NonGBRResources-Offered | ProtocolIE-ID ::= 146 |
+| id-FastMCGRecoveryRRCTransfer-SN-to-MN | ProtocolIE-ID ::= 147 |
+| id-RequestedFastMCGRecoveryViaSRB3 | ProtocolIE-ID ::= 148 |
+| id-AvailableFastMCGRecoveryViaSRB3 | ProtocolIE-ID ::= 149 |
+| id-RequestedFastMCGRecoveryViaSRB3Release | ProtocolIE-ID ::= 150 |
+
+| | |
+|-------------------------------------------|-----------------------|
+| id-ReleaseFastMCGRecoveryViaSRB3 | ProtocolIE-ID ::= 151 |
+| id-FastMCGRecoveryRRCTransfer-MN-to-SN | ProtocolIE-ID ::= 152 |
+| id-ExtendedRATRestrictionInformation | ProtocolIE-ID ::= 153 |
+| id-QoSMonitoringRequest | ProtocolIE-ID ::= 154 |
+| id-FiveGCMobilityRestrictionListContainer | ProtocolIE-ID ::= 155 |
+| id-PartialListIndicator-EUTRA | ProtocolIE-ID ::= 156 |
+| id-CellAndCapacityAssistanceInfo-EUTRA | ProtocolIE-ID ::= 157 |
+| id-CHOinformation-Req | ProtocolIE-ID ::= 158 |
+| id-CHOinformation-Ack | ProtocolIE-ID ::= 159 |
+| id-targetCellsToCancel | ProtocolIE-ID ::= 160 |
+| id-requestedTargetCellGlobalID | ProtocolIE-ID ::= 161 |
+| id-procedureStage | ProtocolIE-ID ::= 162 |
+| id-DAPSRequestInfo | ProtocolIE-ID ::= 163 |
+| id-DAPSResponseInfo-List | ProtocolIE-ID ::= 164 |
+| id-CHO-MRDC-Indicator | ProtocolIE-ID ::= 165 |
+| id-OffsetOfNbiotChannelNumberToDL-EARFCN | ProtocolIE-ID ::= 166 |
+| id-OffsetOfNbiotChannelNumberToUL-EARFCN | ProtocolIE-ID ::= 167 |
+| id-NBIoT-UL-DL-AlignmentOffset | ProtocolIE-ID ::= 168 |
+| id-LTEV2XServicesAuthorized | ProtocolIE-ID ::= 169 |
+| id-NRV2XServicesAuthorized | ProtocolIE-ID ::= 170 |
+| id-LTEUESidelinkAggregateMaximumBitRate | ProtocolIE-ID ::= 171 |
+| id-NRUESidelinkAggregateMaximumBitRate | ProtocolIE-ID ::= 172 |
+| id-PC5QoSParameters | ProtocolIE-ID ::= 173 |
+
+| | |
+|------------------------------------------|-----------------------|
+| id-AlternativeQoSParaSetList | ProtocolIE-ID ::= 174 |
+| id-CurrentQoSParaSetIndex | ProtocolIE-ID ::= 175 |
+| id-MobilityInformation | ProtocolIE-ID ::= 176 |
+| id-InitiatingCondition-FailureIndication | ProtocolIE-ID ::= 177 |
+| id-UEHistoryInformationFromTheUE | ProtocolIE-ID ::= 178 |
+| id-HandoverReportType | ProtocolIE-ID ::= 179 |
+| id-HandoverCause | ProtocolIE-ID ::= 180 |
+| id-SourceCellCGI | ProtocolIE-ID ::= 181 |
+| id-TargetCellCGI | ProtocolIE-ID ::= 182 |
+| id-ReEstablishmentCellCGI | ProtocolIE-ID ::= 183 |
+| id-TargetCellinEUTRAN | ProtocolIE-ID ::= 184 |
+| id-SourceCellCRNTI | ProtocolIE-ID ::= 185 |
+| id-UERLFReportContainer | ProtocolIE-ID ::= 186 |
+| id-NGRAN-Node1-Measurement-ID | ProtocolIE-ID ::= 187 |
+| id-NGRAN-Node2-Measurement-ID | ProtocolIE-ID ::= 188 |
+| id-RegistrationRequest | ProtocolIE-ID ::= 189 |
+| id-ReportCharacteristics | ProtocolIE-ID ::= 190 |
+| id-CellToReport | ProtocolIE-ID ::= 191 |
+| id-ReportingPeriodicity | ProtocolIE-ID ::= 192 |
+| id-CellMeasurementResult | ProtocolIE-ID ::= 193 |
+| id-NG-RANnode1CellID | ProtocolIE-ID ::= 194 |
+| id-NG-RANnode2CellID | ProtocolIE-ID ::= 195 |
+| id-NG-RANnode1MobilityParameters | ProtocolIE-ID ::= 196 |
+
+| | |
+|-----------------------------------------------|-----------------------|
+| id-NG-RANnode2ProposedMobilityParameters | ProtocolIE-ID ::= 197 |
+| id-MobilityParametersModificationRange | ProtocolIE-ID ::= 198 |
+| id-TDDULDLConfigurationCommonNR | ProtocolIE-ID ::= 199 |
+| id-CarrierList | ProtocolIE-ID ::= 200 |
+| id-ULCarrierList | ProtocolIE-ID ::= 201 |
+| id-FrequencyShift7p5khz | ProtocolIE-ID ::= 202 |
+| id-SSB-PositionsInBurst | ProtocolIE-ID ::= 203 |
+| id-NRCellPRACHConfig | ProtocolIE-ID ::= 204 |
+| id-RAReport | ProtocolIE-ID ::= 205 |
+| id-IABNodeIndication | ProtocolIE-ID ::= 206 |
+| id-Redundant-UL-NG-U-TNLatUPF | ProtocolIE-ID ::= 207 |
+| id-CNPacketDelayBudgetDownlink | ProtocolIE-ID ::= 208 |
+| id-CNPacketDelayBudgetUplink | ProtocolIE-ID ::= 209 |
+| id-Additional-Redundant-UL-NG-U-TNLatUPF-List | ProtocolIE-ID ::= 210 |
+| id-RedundantCommonNetworkInstance | ProtocolIE-ID ::= 211 |
+| id-TSCTrafficCharacteristics | ProtocolIE-ID ::= 212 |
+| id-RedundantQoSFlowIndicator | ProtocolIE-ID ::= 213 |
+| id-Redundant-DL-NG-U-TNLatNG-RAN | ProtocolIE-ID ::= 214 |
+| id-ExtendedPacketDelayBudget | ProtocolIE-ID ::= 215 |
+| id-Additional-PDCP-Duplication-TNL-List | ProtocolIE-ID ::= 216 |
+| id-RedundantPDUSessionInformation | ProtocolIE-ID ::= 217 |
+| id-UsedRSNInformation | ProtocolIE-ID ::= 218 |
+| id-RLCDuplicationInformation | ProtocolIE-ID ::= 219 |
+
+| | |
+|---------------------------------------------------|-----------------------|
+| id-NPN-Broadcast-Information | ProtocolIE-ID ::= 220 |
+| id-NPNPagingAssistanceInformation | ProtocolIE-ID ::= 221 |
+| id-NPNMobilityInformation | ProtocolIE-ID ::= 222 |
+| id-NPN-Support | ProtocolIE-ID ::= 223 |
+| id-MDT-Configuration | ProtocolIE-ID ::= 224 |
+| id-MDTPLMNList | ProtocolIE-ID ::= 225 |
+| id-TraceCollectionEntityURI | ProtocolIE-ID ::= 226 |
+| id-UERadioCapabilityID | ProtocolIE-ID ::= 227 |
+| id-CSI-RSTransmissionIndication | ProtocolIE-ID ::= 228 |
+| id-SNTriggered | ProtocolIE-ID ::= 229 |
+| id-DLCarrierList | ProtocolIE-ID ::= 230 |
+| id-ExtendedTAISliceSupportList | ProtocolIE-ID ::= 231 |
+| id-cellAssistanceInfo-EUTRA | ProtocolIE-ID ::= 232 |
+| id-ConfiguredTACIndication | ProtocolIE-ID ::= 233 |
+| id-secondary-SN-UL-PDCP-UP-TNLInfo | ProtocolIE-ID ::= 234 |
+| id-pdcpDuplicationConfiguration | ProtocolIE-ID ::= 235 |
+| id-duplicationActivation | ProtocolIE-ID ::= 236 |
+| id-NPRACHConfiguration | ProtocolIE-ID ::= 237 |
+| id-QosMonitoringReportingFrequency | ProtocolIE-ID ::= 238 |
+| id-QoSFlowsMappedtoDRB-SetupResponse-MNterminated | ProtocolIE-ID ::= 239 |
+| id-DL-scheduling-PDCCH-CCE-usage | ProtocolIE-ID ::= 240 |
+| id-UL-scheduling-PDCCH-CCE-usage | ProtocolIE-ID ::= 241 |
+| id-SFN-Offset | ProtocolIE-ID ::= 242 |
+
+| | |
+|--------------------------------------------|-----------------------|
+| id-QoSMonitoringDisabled | ProtocolIE-ID ::= 243 |
+| id-ExtendedUEIdentityIndexValue | ProtocolIE-ID ::= 244 |
+| id-EUTRAPagingeDRXInformation | ProtocolIE-ID ::= 245 |
+| id-CHO-MRDC-EarlyDataForwarding | ProtocolIE-ID ::= 246 |
+| id-SCGIndicator | ProtocolIE-ID ::= 247 |
+| id-UESpecificDRX | ProtocolIE-ID ::= 248 |
+| id-PDUSessionExpectedUEActivityBehaviour | ProtocolIE-ID ::= 249 |
+| id-QoS-Mapping-Information | ProtocolIE-ID ::= 250 |
+| id-AdditionLocationInformation | ProtocolIE-ID ::= 251 |
+| id-dataForwardingInfoFromTargetE-UTRANnode | ProtocolIE-ID ::= 252 |
+| id-DirectForwardingPathAvailability | ProtocolIE-ID ::= 253 |
+| id-SourceNG-RAN-node-ID | ProtocolIE-ID ::= 254 |
+| id-SourceDLForwardingIPAddress | ProtocolIE-ID ::= 255 |
+| id-SourceNodeDLForwardingIPAddress | ProtocolIE-ID ::= 256 |
+| id-ExtendedReportIntervalMDT | ProtocolIE-ID ::= 257 |
+| id-SecurityIndication | ProtocolIE-ID ::= 258 |
+| id-RRCConnReestab-Indicator | ProtocolIE-ID ::= 259 |
+| id-TargetNodeID | ProtocolIE-ID ::= 260 |
+| id-ManagementBasedMDTPLMNList | ProtocolIE-ID ::= 261 |
+| id-PrivacyIndicator | ProtocolIE-ID ::= 262 |
+| id-TraceCollectionEntityIPAddress | ProtocolIE-ID ::= 263 |
+| id-M4ReportAmount | ProtocolIE-ID ::= 264 |
+| id-M5ReportAmount | ProtocolIE-ID ::= 265 |
+
+| | |
+|--------------------------------------------------|-----------------------|
+| id-M6ReportAmount | ProtocolIE-ID ::= 266 |
+| id-M7ReportAmount | ProtocolIE-ID ::= 267 |
+| id-BeamMeasurementIndicationM1 | ProtocolIE-ID ::= 268 |
+| id-MBS-Session-ID | ProtocolIE-ID ::= 269 |
+| id-UEIdentityIndexList-MBSGroupPaging | ProtocolIE-ID ::= 270 |
+| id-MulticastRANPagingArea | ProtocolIE-ID ::= 271 |
+| id-Supported-MBS-FSA-ID-List | ProtocolIE-ID ::= 272 |
+| id-MBS-SessionInformation-List | ProtocolIE-ID ::= 273 |
+| id-MBS-SessionInformationResponse-List | ProtocolIE-ID ::= 274 |
+| id-MBS-SessionAssociatedInformation | ProtocolIE-ID ::= 275 |
+| id-SuccessfulHOReportInformation | ProtocolIE-ID ::= 276 |
+| id-SliceRadioResourceStatus-List | ProtocolIE-ID ::= 277 |
+| id-CompositeAvailableCapacitySupplementaryUplink | ProtocolIE-ID ::= 278 |
+| id-SCGUEHistoryInformation | ProtocolIE-ID ::= 279 |
+| id-SSBOffsets-List | ProtocolIE-ID ::= 280 |
+| id-NG-RANnode2SSBOffsetModificationRange | ProtocolIE-ID ::= 281 |
+| id-Coverage-Modification-List | ProtocolIE-ID ::= 282 |
+| id-NR-U-Channel-List | ProtocolIE-ID ::= 283 |
+| id-SourcePSCellCGI | ProtocolIE-ID ::= 284 |
+| id-FailedPSCellCGI | ProtocolIE-ID ::= 285 |
+| id-SCGFailureReportContainer | ProtocolIE-ID ::= 286 |
+| id-SNMobilityInformation | ProtocolIE-ID ::= 287 |
+| id-SourcePSCellID | ProtocolIE-ID ::= 288 |
+
+| | |
+|-------------------------------------------|-----------------------|
+| id-SuitablePSCellCGI | ProtocolIE-ID ::= 289 |
+| id-PSCellChangeHistory | ProtocolIE-ID ::= 290 |
+| id-CHOConfiguration | ProtocolIE-ID ::= 291 |
+| id-NR-U-ChannelInfo-List | ProtocolIE-ID ::= 292 |
+| id-PSCellHistoryInformationRetrieve | ProtocolIE-ID ::= 293 |
+| id-NG-RANnode2SSBOffsetsModificationRange | ProtocolIE-ID ::= 294 |
+| id-MIMO PRBusageInformation | ProtocolIE-ID ::= 295 |
+| id-FLCTrafficContainer | ProtocolIE-ID ::= 296 |
+| id-IAB-MT-Cell-List | ProtocolIE-ID ::= 297 |
+| id-NoPDUSessionIndication | ProtocolIE-ID ::= 298 |
+| id-IAB-TNL-Address-Request | ProtocolIE-ID ::= 299 |
+| id-IAB-TNL-Address-Response | ProtocolIE-ID ::= 300 |
+| id-TrafficToBeAddedList | ProtocolIE-ID ::= 301 |
+| id-TrafficToBeModifiedList | ProtocolIE-ID ::= 302 |
+| id-TrafficToBeReleaseInformation | ProtocolIE-ID ::= 303 |
+| id-TrafficAddedList | ProtocolIE-ID ::= 304 |
+| id-TrafficModifiedList | ProtocolIE-ID ::= 305 |
+| id-TrafficNotAddedList | ProtocolIE-ID ::= 306 |
+| id-TrafficNotModifiedList | ProtocolIE-ID ::= 307 |
+| id-TrafficRequiredToBeModifiedList | ProtocolIE-ID ::= 308 |
+| id-TrafficRequiredModifiedList | ProtocolIE-ID ::= 309 |
+| id-TrafficReleasedList | ProtocolIE-ID ::= 310 |
+| id-IABTNLAddressToBeAdded | ProtocolIE-ID ::= 311 |
+
+| | |
+|---------------------------------------------|-----------------------|
+| id-IABTNLAddressToBeReleasedList | ProtocolIE-ID ::= 312 |
+| id-nonFl-Terminating-IAB-DonorUEXnAPID | ProtocolIE-ID ::= 313 |
+| id-Fl-Terminating-IAB-DonorUEXnAPID | ProtocolIE-ID ::= 314 |
+| id-BoundaryNodeCellsList | ProtocolIE-ID ::= 315 |
+| id-ParentNodeCellsList | ProtocolIE-ID ::= 316 |
+| id-tdd-GNB-DU-Cell-Resource-Configuration | ProtocolIE-ID ::= 317 |
+| id-UL-GNB-DU-Cell-Resource-Configuration | ProtocolIE-ID ::= 318 |
+| id-DL-GNB-DU-Cell-Resource-Configuration | ProtocolIE-ID ::= 319 |
+| id-permutation | ProtocolIE-ID ::= 320 |
+| id-IABTNLAddressException | ProtocolIE-ID ::= 321 |
+| id-CHOinformation-AddReq | ProtocolIE-ID ::= 322 |
+| id-CHOinformation-ModReq | ProtocolIE-ID ::= 323 |
+| id-SurvivalTime | ProtocolIE-ID ::= 324 |
+| id-TimeSynchronizationAssistanceInformation | ProtocolIE-ID ::= 325 |
+| id-SCGActivationRequest | ProtocolIE-ID ::= 326 |
+| id-SCGActivationStatus | ProtocolIE-ID ::= 327 |
+| id-CPAInformationRequest | ProtocolIE-ID ::= 328 |
+| id-CPAInformationAck | ProtocolIE-ID ::= 329 |
+| id-CPCInformationRequired | ProtocolIE-ID ::= 330 |
+| id-CPCInformationConfirm | ProtocolIE-ID ::= 331 |
+| id-CPAInformationModReq | ProtocolIE-ID ::= 332 |
+| id-CPAInformationModReqAck | ProtocolIE-ID ::= 333 |
+| id-CPC-DataForwarding-Indicator | ProtocolIE-ID ::= 334 |
+
+| | |
+|-----------------------------------------------------|-----------------------|
+| id-CPCInformationUpdate | ProtocolIE-ID ::= 335 |
+| id-CPACInformationModRequired | ProtocolIE-ID ::= 336 |
+| id-QMCConfigInfo | ProtocolIE-ID ::= 337 |
+| id-ProtocolIE-ID338-NotToBeUsed | ProtocolIE-ID ::= 338 |
+| id-Additional-Measurement-Timing-Configuration-List | ProtocolIE-ID ::= 339 |
+| id-PDUSession-PairID | ProtocolIE-ID ::= 340 |
+| id-Local-NG-RAN-Node-Identifier | ProtocolIE-ID ::= 341 |
+| id-Neighbour-NG-RAN-Node-List | ProtocolIE-ID ::= 342 |
+| id-Local-NG-RAN-Node-Identifier-Removal | ProtocolIE-ID ::= 343 |
+| id-FiveGProSeAuthorized | ProtocolIE-ID ::= 344 |
+| id-FiveGProSePC5QoSParameters | ProtocolIE-ID ::= 345 |
+| id-FiveGProSeUEPC5AggregateMaximumBitRate | ProtocolIE-ID ::= 346 |
+| id-ServedCellSpecificInfoReq-NR | ProtocolIE-ID ::= 347 |
+| id-NRPagingDRXInformation | ProtocolIE-ID ::= 348 |
+| id-NRPagingDRXInformationforRRGINACTIVE | ProtocolIE-ID ::= 349 |
+| id-Redcap-Bcast-Information | ProtocolIE-ID ::= 350 |
+| id-SDTSupportRequest | ProtocolIE-ID ::= 351 |
+| id-SDT-SRB-between-NewNode-OldNode | ProtocolIE-ID ::= 352 |
+| id-SDT-Termination-Request | ProtocolIE-ID ::= 353 |
+| id-SDTPartialUEContextInfo | ProtocolIE-ID ::= 354 |
+| id-SDTDataForwardingDRBList | ProtocolIE-ID ::= 355 |
+| id-PagingCause | ProtocolIE-ID ::= 356 |
+| id-PEIPSassistanceInformation | ProtocolIE-ID ::= 357 |
+
+| | |
+|---------------------------------------------------------------------|-----------------------|
+| id-UESliceMaximumBitRateList | ProtocolIE-ID ::= 358 |
+| id-S-NG-RANnodeUE-Slice-MBR | ProtocolIE-ID ::= 359 |
+| id-PositioningInformation | ProtocolIE-ID ::= 360 |
+| id-UEAssistantIdentifier | ProtocolIE-ID ::= 361 |
+| id-ManagementBasedMDTPLMNModificationList | ProtocolIE-ID ::= 362 |
+| id-Fl-terminatingIAB-donorIndicator | ProtocolIE-ID ::= 363 |
+| id-TAINSAGSupportList | ProtocolIE-ID ::= 364 |
+| id-SCGreconfigNotification | ProtocolIE-ID ::= 365 |
+| id-earlyMeasurement | ProtocolIE-ID ::= 366 |
+| id-BeamMeasurementsReportConfiguration | ProtocolIE-ID ::= 367 |
+| id-CoverageModificationCause | ProtocolIE-ID ::= 368 |
+| id-AdditionalListofPDUSessionResourceChangeConfirmInfo-SNterminated | ProtocolIE-ID ::= 369 |
+| id-UERLFReportContainerLTEExtension | ProtocolIE-ID ::= 370 |
+| id-ExcessPacketDelayThresholdConfiguration | ProtocolIE-ID ::= 371 |
+| id-HashedUEIdentityIndexValue | ProtocolIE-ID ::= 372 |
+| id-QosFlowMappingIndication | ProtocolIE-ID ::= 373 |
+| id-Full-and-Short-I-RNTI-Profile-List | ProtocolIE-ID ::= 374 |
+| id-MBS-DataForwarding-Indicator | ProtocolIE-ID ::= 375 |
+| id-IABAuthorizationStatus | ProtocolIE-ID ::= 376 |
+| id-EquivalentSNPNs | ProtocolIE-ID ::= 377 |
+| id-SelectedNID | ProtocolIE-ID ::= 378 |
+| id-MT-SDT-Information | ProtocolIE-ID ::= 379 |
+| id-PosPartialUEContextInfo | ProtocolIE-ID ::= 380 |
+
+| | |
+|--------------------------------------------|-----------------------|
+| id-SRSConfiguration | ProtocolIE-ID ::= 381 |
+| id-CHOTimeBasedInformation | ProtocolIE-ID ::= 382 |
+| id-ChannelOccupancyTimePercentageUL | ProtocolIE-ID ::= 383 |
+| id-EnergyDetectionThresholdUL | ProtocolIE-ID ::= 384 |
+| id-SuccessfulPSCellChangeReportInformation | ProtocolIE-ID ::= 385 |
+| id-PSCellListContainer | ProtocolIE-ID ::= 386 |
+| id-RadioResourceStatusNR-U | ProtocolIE-ID ::= 387 |
+| id-CPACConfiguration | ProtocolIE-ID ::= 388 |
+| id-RaReportIndicationList | ProtocolIE-ID ::= 389 |
+| id-SPRAvailability | ProtocolIE-ID ::= 390 |
+| id-DLLBTFailureInformationRequest | ProtocolIE-ID ::= 391 |
+| id-DLLBTFailureInformationList | ProtocolIE-ID ::= 392 |
+| id-TargetCellCRNTI | ProtocolIE-ID ::= 393 |
+| id-TimeSinceFailure | ProtocolIE-ID ::= 394 |
+| id-AerialUESubscriptionInformation | ProtocolIE-ID ::= 395 |
+| id-LTEA2XServicesAuthorized | ProtocolIE-ID ::= 396 |
+| id-NRA2XServicesAuthorized | ProtocolIE-ID ::= 397 |
+| id-LTEA2XUEPC5AggregateMaximumBitRate | ProtocolIE-ID ::= 398 |
+| id-NRA2XUEPC5AggregateMaximumBitRate | ProtocolIE-ID ::= 399 |
+| id-A2XPC5QoSParameters | ProtocolIE-ID ::= 400 |
+| id-CellBasedUETrajectoryPrediction | ProtocolIE-ID ::= 401 |
+| id-DataCollectionID | ProtocolIE-ID ::= 402 |
+| id-RequestedPredictionTime | ProtocolIE-ID ::= 403 |
+
+| | |
+|-------------------------------------------|-----------------------|
+| id-NodeMeasurementInitiationResult-List | ProtocolIE-ID ::= 404 |
+| id-CellMeasurementInitiationResult-List | ProtocolIE-ID ::= 405 |
+| id-UEAssociatedInfoResult-List | ProtocolIE-ID ::= 406 |
+| id-EnergyCost | ProtocolIE-ID ::= 407 |
+| id-UETrajectoryCollectionConfiguration | ProtocolIE-ID ::= 408 |
+| id-UEPerformanceCollectionConfiguration | ProtocolIE-ID ::= 409 |
+| id-CellMeasurementResultForDataCollection | ProtocolIE-ID ::= 410 |
+| id-CellToReportForDataCollection-List | ProtocolIE-ID ::= 411 |
+| id-FiveGProSeLayer2Multipath | ProtocolIE-ID ::= 412 |
+| id-FiveGProSeLayer2UEtoUERelay | ProtocolIE-ID ::= 413 |
+| id-FiveGProSeLayer2UEtoUERemote | ProtocolIE-ID ::= 414 |
+| id-CandidateRelayUEInfoList | ProtocolIE-ID ::= 415 |
+| id-NRCellsAndSSBsList | ProtocolIE-ID ::= 416 |
+| id-ActivatedNRCellsAndSSBsList | ProtocolIE-ID ::= 417 |
+| id-ClockQualityReportingControlInfo | ProtocolIE-ID ::= 418 |
+| id-CapabilityForBATAdaptation | ProtocolIE-ID ::= 419 |
+| id-PNI-NPN-AreaScopeofMDT | ProtocolIE-ID ::= 420 |
+| id-PNI-NPNBasedMDT | ProtocolIE-ID ::= 421 |
+| id-SNPN-CellBasedMDT | ProtocolIE-ID ::= 422 |
+| id-SNPN-TAIBasedMDT | ProtocolIE-ID ::= 423 |
+| id-SNPN-IDBasedMDT | ProtocolIE-ID ::= 424 |
+| id-S-CPAC-Request | ProtocolIE-ID ::= 425 |
+| id-S-CPAC-Request-Info | ProtocolIE-ID ::= 426 |
+
+| | |
+|-------------------------------------------------|-----------------------|
+| id-S-CPAC-ReferenceConfigRequest | ProtocolIE-ID ::= 427 |
+| id-S-CPAC-InterSN-ExecutionNotify | ProtocolIE-ID ::= 428 |
+| id-S-CPAC-dataforwardinginfofromSource | ProtocolIE-ID ::= 429 |
+| id-CPACcandidatePSCells-wotherInfo-list | ProtocolIE-ID ::= 430 |
+| id-eRedcap-Bcast-Information | ProtocolIE-ID ::= 431 |
+| id-NRPagingLongeDRXInformationforRRRCINACTIVE | ProtocolIE-ID ::= 432 |
+| id-MBS-AssistanceInformation | ProtocolIE-ID ::= 433 |
+| id-QMCCoordinationRequest | ProtocolIE-ID ::= 434 |
+| id-QMCCoordinationResponse | ProtocolIE-ID ::= 435 |
+| id-QoE-Measurement-Results | ProtocolIE-ID ::= 436 |
+| id-MBSCommServiceType | ProtocolIE-ID ::= 437 |
+| id-AssistanceInformationQoE-Meas | ProtocolIE-ID ::= 438 |
+| id-SNRelatedQMCInfoAtMN | ProtocolIE-ID ::= 439 |
+| id-QoERVQoEReportingPaths | ProtocolIE-ID ::= 440 |
+| id-Src-SN-to-Tgt-SNQMCInfoInquiry | ProtocolIE-ID ::= 441 |
+| id-DirectForwardingPathAvailabilityWithSourceMN | ProtocolIE-ID ::= 442 |
+| id-CHO-Maxnoof-CondReconfig | ProtocolIE-ID ::= 443 |
+| id-accessed-PSCellID | ProtocolIE-ID ::= 444 |
+| id-conditional-Reconfig-ToCancel-List | ProtocolIE-ID ::= 445 |
+| id-CHOinformation-AddReqAck | ProtocolIE-ID ::= 446 |
+| id-CHO-CPAC-Info | ProtocolIE-ID ::= 447 |
+| id-PDUSetQoSParameters | ProtocolIE-ID ::= 448 |
+| id-N6JitterInformation | ProtocolIE-ID ::= 449 |
+
+```
+
+id-ECNMarkingorCongestionInformationReportingRequest ProtocolIE-ID ::= 450
+id-PDUSetbasedHandlingIndicator ProtocolIE-ID ::= 451
+id-TAISliceUnavailableCellList ProtocolIE-ID ::= 452
+id-MobileIAB-AuthorizationStatus ProtocolIE-ID ::= 453
+id-MIAB-MT-BAP-Address ProtocolIE-ID ::= 454
+id-MobileIABCell ProtocolIE-ID ::= 455
+
+```
+
+END
+
+-- ASN1STOP
+
+### 9.3.8 Container definitions
+
+-- ASN1START
+
+-- \*\*\*\*\*
+
+--
+
+-- Container definitions
+
+--
+
+-- \*\*\*\*\*
+
+XnAP-Containers {
+
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+
+ngran-access (22) modules (3) xnap (2) version1 (1) xnap-Containers (5) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- \*\*\*\*\*
+--
+-- IE parameter types from other modules.
+--
+-- \*\*\*\*\*
+
+IMPORTS
+
+maxPrivateIEs,
+maxProtocolExtensions,
+maxProtocolIEs,
+Criticality,
+Presence,
+PrivateIE-ID,
+ProtocolIE-ID
+
+FROM XnAP-CommonDataTypes;
+
+-- \*\*\*\*\*
+--
+-- Class Definition for Protocol IEs
+
+```
+
+--
+-- *****
+
+XNAP-PROTOCOL-IES ::= CLASS {
+ &id ProtocolIE-ID UNIQUE,
+ &criticality Criticality,
+ &Value,
+ &presence Presence
+}
+
+WITH SYNTAX {
+ ID &id
+ CRITICALITY &criticality
+ TYPE &Value
+ PRESENCE &presence
+}
+
+-- *****
+
+--
+-- Class Definition for Protocol IE pairs
+--
+-- *****
+
+XNAP-PROTOCOL-IES-PAIR ::= CLASS {
+
+```
+
+```
+
+ &id ProtocolIE-ID UNIQUE,
+ &firstCriticality Criticality,
+ &FirstValue,
+ &secondCriticality Criticality,
+ &SecondValue,
+ &presence Presence
+}
+
+WITH SYNTAX {
+ ID &id
+ FIRST CRITICALITY &firstCriticality
+ FIRST TYPE &FirstValue
+ SECOND CRITICALITY &secondCriticality
+ SECOND TYPE &SecondValue
+ PRESENCE &presence
+}
+
+-- *****
+--
+-- Class Definition for Protocol Extensions
+--
+-- *****
+
+XNAP-PROTOCOL-EXTENSION ::= CLASS {
+
+```
+
+```
+
+ &id ProtocolIE-ID UNIQUE,
+ &criticality Criticality,
+ &Extension,
+ &presence Presence
+}
+
+WITH SYNTAX {
+ ID &id
+ CRITICALITY &criticality
+ EXTENSION &Extension
+ PRESENCE &presence
+}
+
+-- *****
+--
+-- Class Definition for Private IEs
+--
+-- *****
+
+```
+
+```
+
+XNAP-PRIVATE-IES ::= CLASS {
+ &id PrivateIE-ID,
+ &criticality Criticality,
+ &Value,
+ &presence Presence
+}
+
+```
+
+}
+
+WITH SYNTAX {
+
+ ID &id
+ CRITICALITY &criticality
+ TYPE &Value
+ PRESENCE &presence
+
+}
+
+-- \*\*\*\*\*
+
+--
+
+-- Container for Protocol IEs
+
+--
+
+-- \*\*\*\*\*
+
+ProtocolIE-Container {XNAP-PROTOCOL-IES : IEsSetParam} ::=
+
+ SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+
+ ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Single-Container {XNAP-PROTOCOL-IES : IEsSetParam} ::= ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Field {XNAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {
+
+ id XNAP-PROTOCOL-IES.&id {{IEsSetParam}},
+ criticality XNAP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}},
+
+```
+value XNAP-PROTOCOL-IES.&Value {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container for Protocol IE Pairs
+--
+-- *****
+
+ProtocolIE-ContainerPair {XNAP-PROTOCOL-IES-PAIR : IEsSetParam} ::=
+ SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+ ProtocolIE-FieldPair {{IEsSetParam}}
+
+ProtocolIE-FieldPair {XNAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE {
+ id XNAP-PROTOCOL-IES-PAIR.&id {{IEsSetParam}},
+ firstCriticality XNAP-PROTOCOL-IES-PAIR.&firstCriticality {{IEsSetParam}{@id}},
+ firstValue XNAP-PROTOCOL-IES-PAIR.&FirstValue {{IEsSetParam}{@id}},
+ secondCriticality XNAP-PROTOCOL-IES-PAIR.&secondCriticality {{IEsSetParam}{@id}},
+ secondValue XNAP-PROTOCOL-IES-PAIR.&SecondValue {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+```
+
+```
+-- Container Lists for Protocol IE Containers
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, XNAP-PROTOCOL-IES : IEsSetParam} ::=
+```
+
+```
+ SEQUENCE (SIZE (lowerBound..upperBound)) OF
+```
+
+```
+ ProtocolIE-Container {{IEsSetParam}}
+```
+
+```
+ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, XNAP-PROTOCOL-IES-PAIR : IEsSetParam} ::=
+```
+
+```
+ SEQUENCE (SIZE (lowerBound..upperBound)) OF
+```
+
+```
+ ProtocolIE-ContainerPair {{IEsSetParam}}
+```
+
+```
+-- *****
+```
+
+```
+--
+```
+
+```
+-- Container for Protocol Extensions
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+ProtocolExtensionContainer {XNAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
+```
+
+```
+ ProtocolExtensionField {{ExtensionSetParam}}
+```
+
+```
+ProtocolExtensionField {XNAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
+```
+
+```
+ id XNAP-PROTOCOL-EXTENSION.&id {{ExtensionSetParam}},
+```
+
+```
+ criticality XNAP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}),
+ extensionValue XNAP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id})
+}
+```
+
+```
+-- *****
+```
+
+```
+--
+```
+
+```
+-- Container for Private IEs
+```
+
+```
+--
+```
+
+```
+-- *****
+```
+
+```
+PrivateIE-Container {XNAP-PRIVATE-IES : IEsSetParam} ::=
+```
+
+```
+ SEQUENCE (SIZE (1..maxPrivateIEs)) OF
+```
+
+```
+ PrivateIE-Field {IEsSetParam}
+```
+
+```
+PrivateIE-Field {XNAP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE {
+```
+
+```
+ id XNAP-PRIVATE-IES.&id ({IEsSetParam}),
+ criticality XNAP-PRIVATE-IES.&criticality ({IEsSetParam}{@id}),
+ value XNAP-PRIVATE-IES.&Value ({IEsSetParam}{@id})
+}
+```
+
+```
+END
+```
+
+```
+-- ASN1STOP
+```
+
+
+
+## 9.4 Message transfer syntax
+
+XnAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in ITU-T Rec. X.691 [15].
+
+## 9.5 Timers
+
+### TXn<sub>RELOCprep</sub>
+
+- Specifies the maximum time for the Handover Preparation procedure in the source NG-RAN node.
+
+### TXn<sub>RELOCoverall</sub>
+
+- Specifies the maximum time for the protection of the overall handover procedure in the source NG-RAN node.
+
+### TXn<sub>DCprep</sub>
+
+- Specifies the maximum time for the S-NG-RAN node Addition Preparation or M-NG-RAN node initiated S-NG-RAN node Modification Preparation.
+
+### TXn<sub>DCoverall</sub>
+
+- Specifies the maximum time in the S-NG-RAN node for either the S-NG-RAN node initiated S-NG-RAN node Modification procedure or the protection of the NG-RAN actions necessary to configure UE resources at S-NG-RAN node Addition or M-NG-RAN node initiated S-NG-RAN node Modification.
+
+---
+
+## 10 Handling of unknown, unforeseen and erroneous protocol data
+
+Section 10 of TS 38.413 [5] is applicable for the purposes of the present document.
+
+## Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|--------------|-----------|----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2017-04 | RAN3#95bis | R3-171316 | | | | Implementing agreements from meeting RAN3#95bis:<br>R3-171147 (removing last two IEs and FFS on NG-C UE), R3-171372, R3-171351 (only NSSAI related text), R3-171338 (with Editor's Note on text and message structure), R3-171371 (with Editor's Note in generic section and name for RAN Paging FFS), R3-171345, R3-171347 | 0.0.1 |
+| 2017-05 | RAN3#96 | | | | | Add SGNB MODIFICATION REQUEST in tabular. Editorial change | 0.0.2 |
+| 2017-05 | RAN3#96 | | | | | Implementing agreements from meeting RAN3#96:<br>R3-171925 (Handover messages – tabular format), R3-171928 (additions for RAN Paging)<br>Editorials (remove highlight, change style sheet assignments, correcting and adding references to other TSs and TRs, replacing some FFSs by Editor's Notes) | 0.1.0 |
+| 2017-06 | RAN3#adhoc2 | R3-172548 | | | | Submission | 0.1.1 |
+| 2017-06 | RAN3#adhoc2 | R3-173452 | | | | Implementing agreed R3-172612 and agreed node naming conventions. | 0.2.0 |
+| 2017-08 | RAN3#97 | R3-173462 | | | | Implement the agreed pCRs from RAN3#97 meeting: R3-173237, R3-173337, R3-173416, R3-173429, R3-173431 | 0.3.0 |
+| 2017-10 | RAN3#97bis | R3-174242 | | | | Implementing the agreed pCRs from RAN3#97bis meeting: R3-173976, R3-174097, R3-174183, R3-174192, R3-174205 | 0.4.0 |
+| 2017-12 | RAN3#98 | R3-175058 | | | | Implementing agreed pCRs from RAN3#98 meeting: R3-175024, R3-174817, R3-174920, R3-174920, R3-174924, R3-174934, R3-174837, R3-175077 | 0.5.0 |
+| 2018.01 | RAN3 AH 1801 | R3-180656 | | | | Implementing agreed pCRs from RAN3 AH 1801: R3-180114, R3-180545, R3-180548, R3-180561, R3-180569, R3-180601, R3-180607, R3-180615, R3-180629, R3-180631, R3-180638 | 0.6.0 |
+| 2018-03 | RAN3#99 | R3-181593 | | | | Implementing agreed pCRs from RAN3#99: R3-180850, R3-180980, R3-181247, R3-181280, R3-181350, R3-181385, R3-181390, R3-181415, R3-181418, R3-181461, R3-181504, R3-181509 | 0.7.0 |
+| 2018-04 | RAN3#99bis | R3-182527 | | | | Implementing agreements from RAN3#99bis: R3-182213, R3-182396, R3-182401, R3-181855, R3-182488, R3-182371, R3-182157, R3-182373, R3-182375, R3-182376, R3-182163, R3-182384, R3-182392, R3-181825, R3-182494, R3-181980, R3-182433, update along R3-182378, update along R3-182344, update along R3-181899 | 0.8.0 |
+| 2018-05 | RAN3#100 | R3-183597 | | | | Implementing agreements from RAN3#100: R3-182614, R3-182615, R3-182635, R3-182815, R3-182935, R3-183091, R3-183154, R3-183165, R3-183252, R3-183314, R3-183369, R3-183376, R3-183386, R3-183389, R3-183393, R3-183404, R3-183407, R3-183411, R3-183441, R3-183442, R3-183444, R3-183450, R3-183455, R3-183497, R3- | 0.9.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| | | | | | | 183511, R3-183517, R3-183519, R3-183534, R3-183541. Adding ASN.1 and performing editorial cleanups. | |
+| 2018-06 | RAN#80 | RP-180816 | | | | Submission to TSG RAN for approval | 1.0.0 |
+| 2018-06 | RAN#80 | | - | - | - | Specification approved at TSG-RAN and placed under change control | 15.0.0 |
+| 2018-09 | RAN#81 | RP-181922 | 0008 | 2 | F | Collected corrections for XnAP version 15.0.0 | 15.1.0 |
+| 2018-09 | RAN#81 | RP-181921 | 0002 | 1 | F | Addition of MCG cell ID to solve the PCI confusion at SN | 15.1.0 |
+| 2018-12 | RAN#82 | RP-182448 | 0011 | 4 | F | NR Corrections (TS 38.423 Baseline CR covering RAN3-101Bis and RAN3-102 agreements) | 15.2.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0012 | 3 | F | Correction to RRC transfer | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190201 | 0017 | 3 | F | Transfer of the PSCell information for LI purposes | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0023 | 1 | F | Missing causes for context retrieval failure | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190554 | 0024 | 1 | F | Data volume reporting for MR-DC with 5GC | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0025 | 2 | F | Separate UL/DL limits for UE's maximum IP rate | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0027 | 2 | F | LTE-NR UE Level Resource Coordination | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0029 | 2 | F | Support of PDU session split during handover procedure | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190554 | 0035 | - | F | Correction of RAN triggered PDU Session split | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0036 | - | F | Correction of Slice Support over Xn | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190556 | 0041 | 2 | F | Correction of QoS Flow Mapping Indication | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0042 | - | F | Correction for RRC container in SN MODIFICATION CONFIRM message | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0048 | - | F | Clarification on Inter-node message for NE-DC | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0050 | - | F | Introduce IMEISV to addition request to Xn | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0051 | 2 | F | Support of integrity protection for Option 4&7 | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0053 | 1 | F | Correction on partial reset | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0054 | 1 | F | Correction on TAI Support List | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190555 | 0061 | 1 | F | Rapporteur updates on version 15.2.0 | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190556 | 0065 | 2 | F | S-NSSAI update during EPS to 5GS handover | 15.3.0 |
+| 2019-03 | RAN#83 | RP-190556 | 0067 | 1 | F | Correction of EPC interworking | 15.3.0 |
+| 2019-07 | RAN#84 | RP-191394 | 0056 | 3 | F | Correction on AMF connectivity | 15.4.0 |
+| 2019-07 | RAN#84 | RP-191397 | 0059 | 2 | F | Support of ongoing re-mapping on source side during SDAP mobility | 15.4.0 |
+| 2019-07 | RAN#84 | RP-191397 | 0068 | 1 | F | XnAP Alignment of MN Triggered PDU Session Split | 15.4.0 |
+| 2019-07 | RAN#84 | RP-191395 | 0071 | 2 | F | CR38423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modification Request message | 15.4.0 |
+| 2019-07 | RP-84 | RP-191394 | 0076 | 1 | F | RAN paging failure handling in SN in case of MR-DC | 15.4.0 |
+| 2019-07 | RP-84 | RP-191397 | 0082 | 3 | F | Correction to behaviour of SN for security handling<br>This CR was not implemented as is was not based on the latest version of the spec. | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0083 | - | F | Support for delivering UE band information in RAN paging | 15.4.0 |
+| 2019-07 | RP-84 | RP-191396 | 0086 | - | F | Corrections for support of data forwarding for reestablishment UE | 15.4.0 |
+| 2019-07 | RP#84 | RP-191395 | 0096 | 2 | F | Rapporteur's corrections to version 15.3.0 | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0099 | 1 | F | Correction for SN terminated DRB To Be Setup in SN Addition Response | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0100 | 2 | F | CR for TS 38.423 for Data Forwarding Proposal | 15.4.0 |
+| 2019-07 | RP-84 | RP-191430 | 0102 | 5 | F | RAN sharing with multiple Cell ID broadcast | 15.4.0 |
+| 2019-07 | RP-84 | RP-191397 | 0104 | 1 | F | Correction of Core Network Type Restriction<br>This CR was not implemented as is was not based on the latest version of the spec. | 15.4.0 |
+| 2019-07 | RP-84 | RP-191397 | 0105 | 2 | F | Data forwarding and QoS flow remapping | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0112 | 1 | F | XnAP Correction of PDU Session Resource Setup | 15.4.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| | | | | | | Response Info – MN terminated | |
+| 2019-07 | RP-84 | RP-191395 | 0113 | 1 | F | XnAP Correction of PDU Session Resource Setup Complete Info – SN terminated | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0125 | - | F | Support of single UL transmission for NE-DC | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0126 | 1 | F | In-order delivery when QoS flows offloaded from SN | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0132 | - | F | Transferring of RRC message from Master node to Secondary node | 15.4.0 |
+| 2019-07 | RP-84 | RP-191395 | 0133 | 1 | F | Clarification on Retrieve UE Context procedure | 15.4.0 |
+| 2019-07 | RP-84 | RP-191394 | 0135 | 1 | F | PDCP SN length related clean-up over To Be Modified structure in MN initiated SN Modification procedure | 15.4.0 |
+| 2019-07 | RP-84 | RP-191397 | 0140 | | F | Correction of Network Instance | 15.4.0 |
+| 2019-09 | RP-85 | RP-192166 | 0121 | 2 | F | Correction of handling of the Location Information at the MN | 15.5.0 |
+| 2019-09 | RP-85 | RP-192167 | 0146 | | F | XnAP Rel-15 Leftover Clean-ups | 15.5.0 |
+| 2019-09 | RP-85 | RP-192167 | 0147 | 1 | F | XnAP Corrections of Activity Notification Usage | 15.5.0 |
+| 2019-09 | RP-85 | RP-192167 | 0153 | - | F | Critical correction to the presence of the TAC lists in the Service Area Item IE | 15.5.0 |
+| 2019-09 | RP-85 | RP-192167 | 0158 | 1 | F | CR38.423 for Correction on RRC configuration indication | 15.5.0 |
+| 2019-09 | RP-85 | RP-192166 | 0170 | 2 | F | Correction on source TNL ADDRESS in NG-C interface | 15.5.0 |
+| 2019-09 | RP-85 | RP-192166 | 0173 | 1 | F | Correction on Maximum Integrity Protected Data Rate | 15.5.0 |
+| 2019-09 | RP-85 | RP-192167 | 0197 | 1 | F | Rapporteur's corrections for TS 38.423 | 15.5.0 |
+| 2019-09 | RP-85 | RP-192166 | 0210 | 1 | F | Corrections regarding mandatory statements in Semantics Descriptions | 15.5.0 |
+| 2019-09 | RP-85 | RP-192167 | 0216 | 1 | F | Support of default DRB coordination in MR-DC with 5GC | 15.5.0 |
+| 2019-12 | RP-86 | RP-192916 | 0063 | 7 | F | Correction on DRB ID co-ordination between MN and SN | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0082 | 4 | F | Correction to behaviour of SN for security handling | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0104 | 2 | F | Correction of Core Network Type Restriction | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0236 | 2 | F | SN Status Transfer for bearer reconfiguration during HO with DC | 15.6.0 |
+| 2019-12 | RP-86 | RP-192915 | 0244 | 1 | F | Misalignment between tabular and ASN.1 | 15.6.0 |
+| 2019-12 | RP-86 | RP-192915 | 0249 | 1 | F | Correction of S-NSSAI coding | 15.6.0 |
+| 2019-12 | RP-86 | RP-192915 | 0252 | 2 | F | Correction to UL data forwarding | 15.6.0 |
+| 2019-12 | RP-86 | RP-192915 | 0262 | | F | Add the missing dynamic port support | 15.6.0 |
+| 2019-12 | RP-86 | RP-192915 | 0266 | - | F | Correction on the data forwarding in S-NG-RAN initiated S-NG-RAN Release | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0272 | | F | Correction of Xn handover | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0282 | 1 | F | Support of delta configuration in MR-DC | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0288 | 1 | F | Missing description of a cause value | 15.6.0 |
+| 2019-12 | RP-86 | RP-192916 | 0294 | 1 | F | Correction to SN Status Transfer considering MR-DC operations | 15.6.0 |
+| 2019-12 | RP-86 | RP-192908 | 0089 | 4 | B | BL CR to 38.423: CLI support on XnAP | 16.0.0 |
+| 2019-12 | RP-86 | RP-192693 | 0201 | 7 | F | Support for setting up IPSec a priori in Xn | 16.0.0 |
+| 2019-12 | RP-86 | RP-192913 | 0208 | 7 | F | Xn Setup message size limitation | 16.0.0 |
+| 2019-12 | RP-86 | RP-192915 | 0237 | 2 | F | Trace function in MR-DC | 16.0.0 |
+| 2019-12 | RP-86 | RP-192913 | 0253 | 1 | C | Extending the MDBV Range | 16.0.0 |
+| 2019-12 | RP-86 | RP-192910 | 0259 | 2 | B | Resuming SCG in RRC Resume | 16.0.0 |
+| 2019-12 | RP-86 | RP-192916 | 0283 | 3 | F | Correction on the offered non-GBR resources | 16.0.0 |
+| 2019-12 | RP-86 | RP-192910 | 0285 | 2 | B | Fast MCG link Recovery with SRB3 | 16.0.0 |
+| 2020-03 | RP-87-e | RP-200422 | 0274 | 2 | B | Introduction of NR-U | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200423 | 0300 | 1 | B | Supporting of RACS in XnAP<br>(The CR is not implemented. The CR was marked | 16.1.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| | | | | | | agreed by mistake while the WI is not yet complete) | |
+| 2020-03 | RP-87-e | RP-200428 | 0303 | - | A | Correction of the referred RRCResumeRequest1 name | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200476 | 0310 | 4 | B | E2E delay measurement for Qos monitoring for URLLC | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200427 | 0318 | 1 | F | Cleanup for Fast MCG link Recovery with SRB3 | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200428 | 0322 | 1 | A | Misalignment between the tabular and ASN.1 within the SN modification procedure | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200428 | 0327 | - | A | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200428 | 0329 | - | A | Correction of CR0236r2 to explicate procedural interaction | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200428 | 0331 | 1 | A | Correction of CR0282r1 – procedure text | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200429 | 0334 | 1 | F | Correction of CR0089r4: CLI Support on XnAP | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200425 | 0335 | - | F | Correction of CR0208 on Xn Setup Message Size Control | 16.1.0 |
+| 2020-03 | RP-87-e | RP-200425 | 0337 | 1 | D | Rapporteur Corrections Rel-16 | 16.1.0 |
+| 2020-07 | RP-88-e | RP-201075 | 0136 | 13 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201088 | 0144 | 7 | B | Introduction of CP UP NB-IoT Others | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201074 | 0151 | 13 | B | Support of NR V2X over Xn | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201086 | 0182 | 8 | B | Introduction of Suspend-Resume | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201082 | 0221 | 12 | B | Addition of SON features | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201077 | 0223 | 6 | B | BL CR to 38.423: Support for IAB | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201079 | 0230 | 11 | B | Introduction of NR_IIOT support to TS 38.423 | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201080 | 0289 | 7 | B | Introduction of Non-Public Networks | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201082 | 0291 | 10 | B | MDT Configuration support for XnAP | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201078 | 0300 | 5 | B | Supporting of RACS in XnAP | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201087 | 0343 | 2 | B | Introduction of eMTC connected to 5GC | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201076 | 0344 | 1 | B | CR38.423 on TDD pattern for NR-DC power control coordination for sol1 | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201073 | 0346 | 3 | F | Slot length correction in Intended TDD UL-DL Configuration | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201085 | 0348 | 1 | F | Introduction of CSI-RS configuration switch on Xn | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201090 | 0350 | 2 | A | Encoding PLMNs in served cell information NR | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201085 | 0359 | 1 | F | Rapporteur's Correction to XnAP version 16.1.0 | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201085 | 0360 | - | F | Corrections to Xn Setup message size limitation solution | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201091 | 0373 | | F | Correction on nested SN modification procedure | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201090 | 0375 | - | A | Encoding PLMNs in served cell information IEs - semantics corrections | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201090 | 0381 | 4 | A | Clarification on MIB only scenario | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201093 | 0382 | | A | TS38.423 Resolving Erroneous unknown-old-en-gNB-UE-X2AP-ID Rel-16 | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201076 | 0388 | - | B | Inter-RAT HO support for fast MCG recovery | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201085 | 0393 | 2 | F | Correction on RF parameters in NR cell information | 16.2.0 |
+| 2020-07 | RP-88-e | RP-201090 | 0394 | 4 | F | Correction of S-NSSAI range | 16.2.0 |
+| 2020-09 | RP-89-e | RP-201955 | 0358 | 2 | A | Support of PSCell/SCell-only operation mode | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201946 | 0389 | 2 | F | Further correction on fast MCG recovery via SRB3 | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0395 | 2 | F | Correction for TS38.423 on Unsuccessful Operation and Abnormal Conditions of MLB | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0405 | | B | Introduction of NR SCG Release for Power Saving | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0412 | 1 | F | Correction of NPN CAG Cells and non-CAG Cells | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0419 | 2 | F | SON Corrections | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0420 | 2 | F | Clarification of the TNL Capacity Indicator | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201950 | 0426 | 1 | F | Correction of CR0360 - Enabling an ng-eNB to reply to Cell Assistance Information E-UTRA. | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201950 | 0427 | - | F | Correction of CR 0393r2 | 16.3.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2020-09 | RP-89-e | RP-201949 | 0428 | - | F | Correcting Target Cell List for Rel-16 mobility enhancements | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201955 | 0429 | - | A | Missing QoS Flow Mapping Indication IE in PDU Session Resource Modification Info - SN terminated IE. | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0430 | 1 | F | Rapporteur's corrections to TS 38.423 v16.2.0 | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0431 | - | F | Restructuring FAILURE INDICATION message - avoid condition upon absence of IE | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201955 | 0432 | 1 | A | Correction CR0063 implementation - missing DRB-IDs-takenintouse in PDU Session Resource Setup Response Info - SN terminated | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201955 | 0436 | 1 | A | Multiple location reporting requests and report | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201955 | 0454 | 1 | A | Correction for Industrial IoT PDCP duplication for Carrier Aggregation | 16.3.0 |
+| 2020-09 | RP-89-e | RP-201949 | 0464 | - | F | Correction of mandatory ProtocolExtensionContainer | 16.3.0 |
+| 2020-12 | RP-90-e | RP-202314 | 0399 | 2 | F | NPRACH configuration exchanging | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202311 | 0466 | 1 | F | Correction on CPC Complete Transfer | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202312 | 0472 | 1 | F | CR38423 for NR SCG release for power saving | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202312 | 0485 | 2 | F | Support of release on CAG subscription change | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202313 | 0492 | 1 | F | Introduction of reporting frequency for Qos monitoring for URLLC | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202312 | 0493 | 1 | F | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202310 | 0494 | 1 | F | Correction of alternative QoS profile | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202312 | 0495 | 1 | F | Corrections of MLB and MDT | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202315 | 0501 | 1 | F | XnAP Rapporteur CR | 16.4.0 |
+| 2020-12 | RP-90-e | RP-202315 | 0514 | - | F | Correction on XnAP ASN.1 | 16.4.0 |
+| 2021-03 | RP-91-e | RP-210124 | 0206 | 7 | B | Introduction of SFN Offset per cell over Xn | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210239 | 0512 | 4 | F | Cause value on Xn for insufficient UE capabilities CR 38.423 | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210240 | 0519 | 1 | F | Update on QoS monitoring control | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210237 | 0529 | - | F | Correction on UE identity index for eMTC UE in RRC_INACTIVE | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210240 | 0534 | 2 | A | Correction of SN modification request ack message | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210240 | 0537 | 2 | A | Correction on UL Configuration handling | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210232 | 0548 | 1 | F | Correction of NPN related Cell Information | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210235 | 0554 | 2 | F | Clarification of Secondary RAT in mobility restrictions | 16.5.0 |
+| 2021-03 | RP-91-e | RP-210239 | 0555 | 1 | F | Cause value on Xn for normal release CR 38.423 | 16.5.0 |
+| 2021-06 | RP-92-e | RP-211323 | 0452 | 3 | F | Correction of the DAPS Response Information IE in the tabular | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211323 | 0465 | 3 | F | Clarification of the use of the max no of CHO preparations | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211315 | 0473 | 3 | F | Clarification on TAI Slice Support List | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211316 | 0504 | 2 | F | Correction of Allocated C-RNTI for 2-step RACH | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211324 | 0530 | 6 | F | Paging eDRX information delivery for RRC_INACTIVE UE in XnAP | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211317 | 0559 | 2 | F | Maximum Number of RRC Connections | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211323 | 0577 | 2 | F | 38.423 correction for CHO early data forwarding in MN to ng-eNB/gNB Change scenario | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211334 | 0582 | 1 | A | Correction on the RAT Restriction Information | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211317 | 0594 | 1 | F | Correction on description of RACH Report Container in ACCESS AND MOBILITY INDICATION | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211317 | 0609 | 3 | F | Correction of ASN.1 definition and semantics for Resource Status Reporting Initiation procedure | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211328 | 0624 | 1 | F | Addition of sidelink MR-DC resource coordination | 16.6.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2021-06 | RP-92-e | RP-211334 | 0631 | 1 | A | How to release SCG configuration between MN and SN CR 38.423 | 16.6.0 |
+| 2021-06 | RP-92-e | RP-211336 | 0632 | 1 | A | Rel-16 CR for UE specific DRX delivery | 16.6.0 |
+| 2021-09 | RP-93-e | RP-211881 | 0622 | 2 | F | Expected UE Activity Behaviour | 16.7.0 |
+| 2021-09 | RP-93-e | RP-211878 | 0643 | | F | Support for using IAB for a NR-DC UE | 16.7.0 |
+| 2021-09 | RP-93-e | RP-211884 | 0659 | 1 | F | Correction of RESOURCE STATUS UPDATE | 16.7.0 |
+| 2021-09 | RP-93-e | RP-211882 | 0672 | | A | Correction of Security | 16.7.0 |
+| 2021-09 | RP-93-e | RP-211882 | 0673 | | F | Correction CR on Network instance | 16.7.0 |
+| 2021-12 | RP-94-e | RP-212863 | 0677 | 1 | F | Adding reference for coding of Common Network Instance | 16.8.0 |
+| 2021-12 | RP-94-e | RP-212863 | 0689 | - | A | Transfer of PSCell Location Reporting control information at Xn mobility | 16.8.0 |
+| 2021-12 | RP-94-e | RP-212871 | 0696 | 1 | F | Redundant network instance for split PDU session | 16.8.0 |
+| 2021-12 | RP-94-e | RP-212863 | 0705 | 1 | F | Correction to the S-NODE MODIFICATION REQUIRED message | 16.8.0 |
+| 2021-12 | RP-94-e | RP-212860 | 0706 | 1 | F | Correction of Direct data forwarding from NR-DC to E-UTRAN | 16.8.0 |
+| 2021-12 | RP-94-e | RP-212864 | 0718 | - | A | Correction on Xn Removal for RAN Sharing in Rel-16 | 16.8.0 |
+| 2022-03 | RP-95-e | RP-220243 | 0553 | 7 | F | Direct data forwarding for mobility between DC and SA | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220279 | 0691 | 3 | F | Dynamic ACL over Xn CR 38.423 | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220278 | 0731 | 1 | A | Correction on UE XnAP ID in the ERROR INDICATION message | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220278 | 0736 | 1 | F | Correction of frequency information for DL only cell | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220280 | 0742 | 1 | F | Value range misalignment for MDT M1, M8 and M9 configuration | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220278 | 0744 | 1 | A | CR to 38.423 on UP security policy update | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220280 | 0753 | | F | MRO Correction | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220279 | 0756 | 1 | F | CR on direct data forwarding from MR-DC to SA | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220280 | 0760 | - | F | Unsuccessful Mobility Setting Change | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220279 | 0766 | | F | Correction of S-NODE MODIFICATION CONFIRM message | 16.9.0 |
+| 2022-03 | RP-95-e | RP-220221 | 0415 | 12 | B | BLCR to 38.423: Support of MDT enhancement | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220225 | 0488 | 8 | B | Introduction of NTN | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220224 | 0491 | 9 | B | Introduction of NR Multicast and Broadcast Services | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220221 | 0517 | 10 | B | BLCR to 38.423_Addition of SON features enhancement | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220222 | 0532 | 10 | B | BL CR to XnAP on Rel-17 eIAB | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0580 | 3 | C | Enabling CHO with SCG configuration [CHOwithDCkept] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0596 | 6 | B | Inter MN resume without SN change [InterMNResume] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220223 | 0620 | 8 | B | Introduction of Enhanced IIoT support over Xn | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220218 | 0633 | 8 | B | SCG BL CR to TS 38.423 | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220218 | 0634 | 9 | B | CPAC BL CR to TS 38.423 | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220229 | 0639 | 7 | B | Mobility Support for NR QoE Measurement Collection | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0653 | 1 | B | Signalling of Neighbour cell CSI-RS configuration information over Xn [CSIRSXn] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220294 | 0656 | 3 | B | Support for Enhancement of Redundant PDU Sessions [Paired_ID] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0674 | 4 | B | Support flexible I-RNTI partitioning [RRInactive] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0676 | 3 | C | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220231 | 0693 | 6 | B | Introduction of Sidelink Relay over Xn | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0700 | 2 | B | CSI-RS configuration request Indicator [CSIRSXn] | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220230 | 0716 | 5 | B | Support for Redcap UEs | 17.0.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2022-03 | RP-95-e | RP-220233 | 0720 | 3 | B | RA-SDT BLCR to TS 38.423 | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220219 | 0729 | 3 | B | Introduction of MultiSIM support over Xn | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220235 | 0732 | 4 | B | Supporting UE Power Saving Enhancements | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220232 | 0745 | 3 | B | (BL CR to TS38.423) RAN slicing enhancement | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220228 | 0748 | 3 | B | (BL CR to TS 38.423) Transfer of Positioning Context in XnAP | 17.0.0 |
+| 2022-03 | RP-95-e | RP-220236 | 0759 | 1 | D | XnAP Rapporteur Corrections | 17.0.0 |
+| 2022-06 | RP-96 | RP-221141 | 0770 | 1 | F | Correction of R17 SON features enhancement | 17.1.0 |
+| 2022-06 | RP-96 | RP-221135 | 0772 | - | F | Alignment of ASN.1 and tabular for CPC Cancel | 17.1.0 |
+| 2022-06 | RP-96 | RP-221145 | 0774 | - | F | Correction on CHO Information SN Modification [CHOwithDCkept] | 17.1.0 |
+| 2022-06 | RP-96 | RP-221135 | 0776 | 1 | F | Correction on CPAC to 38.423 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221135 | 0779 | 1 | F | Correction on CPAC | 17.1.0 |
+| 2022-06 | RP-96 | RP-221136 | 0780 | 1 | F | Correction for RA-SDT in XnAP | 17.1.0 |
+| 2022-06 | RP-96 | RP-221136 | 0782 | 1 | F | Correction of RACH-based SDT Stage 3 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221135 | 0785 | - | F | ASN.1 corrections for CPAC | 17.1.0 |
+| 2022-06 | RP-96 | RP-221136 | 0786 | - | F | SDT corrections over Xn | 17.1.0 |
+| 2022-06 | RP-96 | RP-221126 | 0794 | 1 | F | Correction on RedCap Broadcast Information for TS38.423 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221136 | 0799 | 1 | F | Correction on SRB SDT on XnAP | 17.1.0 |
+| 2022-06 | RP-96 | RP-221150 | 0804 | 1 | A | Dynamic ACL over Xn CR 38.423 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221145 | 0806 | 1 | F | Rapporteur's correction to XnAP version 17.0.0 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221153 | 0812 | 2 | A | Trace Activation IE support for the Retrieve UE Context procedure | 17.1.0 |
+| 2022-06 | RP-96 | RP-221141 | 0813 | 3 | F | XnAP corrections for NR-U | 17.1.0 |
+| 2022-06 | RP-96 | RP-221141 | 0814 | 1 | F | MRO for SN change failure correction | 17.1.0 |
+| 2022-06 | RP-96 | RP-221134 | 0815 | 2 | F | Correction of MBS Xn handover | 17.1.0 |
+| 2022-06 | RP-96 | RP-221129 | 0817 | 1 | F | Correction of the criticality of UE-Slice-MBR | 17.1.0 |
+| 2022-06 | RP-96 | RP-221141 | 0820 | 2 | F | ASN.1 corrections | 17.1.0 |
+| 2022-06 | RP-96 | RP-221141 | 0832 | 1 | F | Correction on update management based MDT user consent | 17.1.0 |
+| 2022-06 | RP-96 | RP-221134 | 0834 | - | F | Correction on NR MBS for 38423 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221134 | 0835 | 1 | F | Correction on ASN.1 in NR MBS | 17.1.0 |
+| 2022-06 | RP-96 | RP-221141 | 0839 | 1 | F | Correction to 38.423 for SON features enhancement | 17.1.0 |
+| 2022-06 | RP-96 | RP-221143 | 0840 | 2 | F | CR to 38.423 on corrections to QoE measurement continuity | 17.1.0 |
+| 2022-06 | RP-96 | RP-221143 | 0841 | 1 | F | CR to 38.423 on ASN.1 corrections of QoE measurement | 17.1.0 |
+| 2022-06 | RP-96 | RP-221143 | 0846 | 2 | F | ASN.1 Correction to 38.423 on NR QoE | 17.1.0 |
+| 2022-06 | RP-96 | RP-221128 | 0848 | 1 | F | Corrections on IAB in TS 38.423 | 17.1.0 |
+| 2022-06 | RP-96 | RP-221139 | 0850 | - | F | SL Relay corrections over Xn | 17.1.0 |
+| 2022-06 | RP-96 | RP-221135 | 0851 | - | F | Rel-17 Correction for XnAP on the interaction with SN-initiated SCG (de)activation and SN Addition procedure | 17.1.0 |
+| 2022-06 | RP-96 | RP-221141 | 0852 | - | F | Correction of the handling of Mobility Information in case of CHO | 17.1.0 |
+| 2022-09 | RP-97-e | RP-222184 | 0833 | 6 | F | Correction of Slice Group Configuration | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222193 | 0854 | 1 | F | Coordination of CHO and intra-SN SCG reconfiguration | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222199 | 0856 | 1 | A | CAG access control without mobility restrictions | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222195 | 0859 | - | F | Timer handling for CHO with SCG configuration [CHOwithDCkept] | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222183 | 0860 | - | F | Miscellaneous Correction on IAB | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222203 | 0865 | 1 | A | Correction of Xn Data Forwarding | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222188 | 0867 | - | F | Further Corrections for NR MBS | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222185 | 0868 | 2 | B | CR for TS38.423 on Extending NR Operation to 71GHz | 17.2.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2022-09 | RP-97-e | RP-222088 | 0874 | 1 | F | Correction to RedCap PTW | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222201 | 0891 | 1 | A | Correction on QoS Flow Mapping Indication | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222191 | 0895 | 1 | F | Correction to Report Characteristics | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222191 | 0898 | 1 | F | Correction for TS 38.423 on UHL in MR-DC | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222191 | 0900 | 1 | F | Correction on NR-U MLB | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222191 | 0901 | 1 | F | Correction to early measurement collection | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222628 | 0902 | 2 | F | Collection on beam measurement report configuration in M1 | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222192 | 0903 | - | F | Correction to R17 QoE | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222191 | 0905 | - | F | Clarification of PSCell ID handling for SCG MRO handling | 17.2.0 |
+| 2022-12 | RP-98-e | RP-222879 | 0908 | 3 | F | The inclusion of the CCO Issue Detection over Xn signalling | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222879 | 0909 | 1 | F | Further correction to Report Characteristics | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222881 | 0916 | 2 | F | Correction to TS 38.423 on RRC transfer | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222881 | 0917 | 1 | F | Correction on Resource configuration for IAB | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222879 | 0927 | 2 | F | Correction on SHR report | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222890 | 0929 | 1 | A | Correction on RACH report | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222879 | 0930 | 3 | F | Resource Status Reporting correction | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222877 | 0935 | 2 | F | Additional indicator for CHO-CPC coordination | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222881 | 0939 | - | F | Clarification on IAB TNL Address Request IE | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222877 | 0940 | 1 | F | Direct early data forwarding in SN initiated inter-SN CPC | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222889 | 0941 | 2 | F | Correction on providing partial UE context in small data transmission | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222890 | 0943 | 1 | A | Correction on UE RLF Report in TS38.423 | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222881 | 0944 | 1 | F | Correction on IAB STC Info | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222879 | 0946 | 4 | F | XnAP Corrections related to Excess Packet Delay | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222879 | 0947 | 3 | F | Correction related to Management Based MDT PLMN Modification List | 17.3.0 |
+| 2023-03 | RAN#99 | RP-230595 | 0960 | 1 | F | Tabular correction of MDT Activation | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230589 | 0964 | 2 | F | Correction on the UE identity index to TS38.423 | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230582 | 0965 | 1 | F | Completion of the work on CHO-CPC coordination | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230593 | 0966 | 1 | F | Correction of the presence in the ASN.1 definition of the REL REQ message | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230595 | 0971 | - | A | Correction of MDT Configuration-EUTRA IE | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230581 | 0974 | 1 | F | Correction on SDT Data Forwarding | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230586 | 0975 | - | F | Correction on Resource configuration for IAB | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230601 | 0977 | 2 | A | Correction of SFN offset in served cell information E-UTRA | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230593 | 0979 | 1 | F | XnAP corrections of references to RRC | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230595 | 0981 | 1 | F | Correction on FAILURE INDICATION | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230595 | 0983 | - | F | Slice Available Capacity tabular alignment | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230595 | 0991 | 1 | A | Correction on MDT area scope | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230600 | 0993 | 1 | A | Correction on Conditional Handover Cancel | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230595 | 0995 | 1 | A | ASN.1 Correction of MDT Configuration-NR | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230593 | 1003 | 1 | A | Correction on UP security procedure | 17.4.0 |
+| 2023-03 | RAN#99 | RP-230582 | 1007 | 1 | F | Correction on coordination of CHO and CPC over Xn | 17.4.0 |
+| 2023-06 | RAN#100 | RP-231073 | 0980 | 4 | F | Correction of Burst Arrival Time semantics description | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231081 | 1012 | 2 | A | Correction on Mobility Change procedure | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231072 | 1014 | 2 | F | Correction to TS 38.423 on RB Set Configuration | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231067 | 1015 | 2 | F | Introduction of the UE hashed ID to 38.423 | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231075 | 1017 | 2 | A | Clarifications on TNLA Addition/Removal/Modification procedures | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231084 | 1021 | 2 | B | Missing transmission bandwidth configurations in XnAP [NR_FR1_35MHz_45MHz_BW] | 17.5.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2023-06 | RAN#100 | RP-231071 | 1026 | 2 | F | XnAP Rel-17 correction for NR-U metrics | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231081 | 1033 | 2 | A | Correction on Trace Activation IE | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231081 | 1035 | 2 | A | Correction on the Area Scope IE in MDT Configuration | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231075 | 1041 | 2 | F | Correction for UP security policy update in modification procedure | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231075 | 1046 | 3 | F | Correction on behaviour procedure text for UP security procedure | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231076 | 1048 | 2 | F | Correction on Extended Packet Delay Budget | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231072 | 1057 | 1 | A | Correction on QoS mapping information | 17.5.0 |
+| 2023-06 | RAN#100 | RP-231084 | 1060 | | A | Correcting missing extension containers in CHOICE type definitions | 17.5.0 |
+| 2023-09 | RAN#101 | RP-231899 | 1071 | 1 | F | Correction on E-UTRA - NR Cell Resource Coordination | 17.6.0 |
+| 2023-09 | RAN#101 | RP-231903 | 1072 | 3 | F | Correction on the local NG-RAN Node Identifier on Xn [RRCInactive] | 17.6.0 |
+| 2023-09 | RAN#101 | RP-231899 | 1075 | - | A | Correction of QoS Flow Mapping Indication IE in PDU Session Resource Modification Required Info - SN terminated | 17.6.0 |
+| 2023-09 | RAN#101 | RP-231902 | 1077 | 1 | A | Correction of Additional PDCP Duplication TNL List | 17.6.0 |
+| 2023-09 | RAN#101 | RP-231902 | 1083 | - | F | Correction to misalignment of TAI between ASN.1 and tabular in QoE | 17.6.0 |
+| 2023-09 | RAN#101 | RP-231899 | 1084 | - | F | Correction of Served Cell Specific Info Request | 17.6.0 |
+| 2023-12 | RAN#102 | RP-233849 | 1092 | 3 | F | Correction on multicast data forwarding in case of UE context retrieval | 17.7.0 |
+| 2023-12 | RAN#102 | RP-233853 | 1105 | 1 | F | Correction on Fast MCG Recovery via SRB3 | 17.7.0 |
+| 2023-12 | RAN#102 | RP-233848 | 1106 | 1 | F | Correction on IAB authorization status transfer | 17.7.0 |
+| 2023-12 | RAN#102 | RP-233826 | 0933 | 12 | B | CR for NR NTN | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233832 | 0934 | 12 | B | Addition of SON features enhancement | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233824 | 0951 | 8 | B | NR support for UAV over Xn | 18.0.0 |
+| 2023-12 | RAN#102 | RP-234067 | 0959 | 13 | B | Support of AI/ML in NG-RAN | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233822 | 0967 | 9 | B | Support NR Sidelink Relay Enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233840 | 0978 | 11 | B | Introduction of equivalent SNPNS | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233819 | 1010 | 8 | B | Introduction of MT-SDT | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233817 | 1018 | 9 | B | Introduction of Network Energy Saving | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233838 | 1049 | 10 | B | Introduction of 5G Timing Resiliency and URLLC enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233832 | 1050 | 6 | B | Introduction of MDT enhancements to support Non-Public Networks | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233818 | 1051 | 7 | B | Introduction of Subsequent CPAC | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233816 | 1052 | 6 | B | Introduction of RedCap enhancement | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233828 | 1068 | 5 | B | Introduction of NR MBS enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233833 | 1069 | 8 | B | Introduction of R18 QoE measurement enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233845 | 1085 | 4 | B | Positioning inactive mode for SDT without anchor relocation [POS_SDT] | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233818 | 1090 | 4 | B | Introduction of CHO with SCG(s) | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233830 | 1091 | 6 | B | Introduction of XR enhancement | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233845 | 1093 | 2 | B | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233841 | 1094 | 2 | B | Introduction of 3 MHz channel bandwidth | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233839 | 1098 | 4 | B | Signalling cells configured with zero resources for a slice | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233834 | 1102 | 3 | B | Support for mobile IAB | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233818 | 1113 | 1 | B | (CR to 38.423) Introduction of L1/L2 triggered mobility | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38424/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38424/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d9d2513cf039cef9aac0def2bc9f0b4d23fbc565
--- /dev/null
+++ b/marked/Rel-18/38_series/38424/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04960319a82a56f29457c520fa5fb586775f78656972f5ca2c99a49ab8e07e46
+size 9536
diff --git a/marked/Rel-18/38_series/38424/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38424/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eacab349c614c357cebfb006b8bb2fb8e752f07d
--- /dev/null
+++ b/marked/Rel-18/38_series/38424/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aebecf6896a366f8447e93dcfcebac7f1cb454dbe40072e783cfcf1a956d3280
+size 6398
diff --git a/marked/Rel-18/38_series/38424/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Rel-18/38_series/38424/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..702fc346bef2633d2cbd86f015e815c1e9342497
--- /dev/null
+++ b/marked/Rel-18/38_series/38424/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d071074c563e0f4e43aeb784f0519a886d372d0b22e83bbd40bb8f7168b8d8d
+size 12997
diff --git a/marked/Rel-18/38_series/38424/raw.md b/marked/Rel-18/38_series/38424/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac39e648cec13d163f3f2c48ed26d05847507b58
--- /dev/null
+++ b/marked/Rel-18/38_series/38424/raw.md
@@ -0,0 +1,189 @@
+
+
+# 3GPP TS 38.424 V18.0.0(2024-03)
+
+Technical Specification
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn data transport (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<https://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+| | |
+|---------------------------------------------------|----------|
+| Foreword ..... | 4 |
+| 1 Scope..... | 5 |
+| 2 References..... | 5 |
+| 3 Definitions and abbreviations ..... | 5 |
+| 3.1 Definitions..... | 5 |
+| 3.2 Abbreviations ..... | 5 |
+| 4 Data link layer..... | 6 |
+| 5 Xn interface user plane protocol ..... | 6 |
+| 5.1 General ..... | 6 |
+| 5.2 GTP-U ..... | 6 |
+| 5.3 UDP/IP ..... | 6 |
+| 5.4 DiffServ code point marking..... | 7 |
+| <b>Annex A (informative): Change history.....</b> | <b>8</b> |
+
+# --- 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
+
+The present document specifies the standards for user data transport protocols and related signalling protocols to establish user plane transport bearers over the Xn interface.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
+- [3] IETF RFC 768 (1980-08): "User Datagram Protocol".
+- [4] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [5] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification".
+- [6] IETF RFC 791 (1981-09): "Internet Protocol".
+- [7] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions below apply. Terms and definitions not defined below can be found in TR 21.905 [1].
+
+**NG-RAN node:** as defined in TS 38.300 [7].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|----------------------------|
+| GTP | GPRS Tunnelling Protocol |
+| IP | Internet Protocol |
+| TEID | Tunnel Endpoint Identifier |
+| UDP | User Datagram Protocol |
+
+# 4 Data link layer
+
+Any data link protocol that fulfils the requirements toward the upper layer may be used.
+
+# 5 Xn interface user plane protocol
+
+## 5.1 General
+
+The transport layer for data streams over Xn is an IP based Transport. The following figure shows the transport protocol stacks over Xn.
+
+
+
+| |
+|---------------------------------------------|
+| GTP-U |
+| UDP |
+| IPv6 (RFC 2460)<br>and/or<br>IPv4 (RFC 791) |
+| Data link layer |
+| Physical layer |
+
+Figure 5.1: Transport network layer for data streams over Xn. The diagram shows a vertical stack of five layers: GTP-U, UDP, IPv6 (RFC 2460) and/or IPv4 (RFC 791), Data link layer, and Physical layer.
+
+**Figure 5.1: Transport network layer for data streams over Xn**
+
+The GTP-U (TS 29.281 [2]) protocol over UDP over IP shall be supported as the transport for data streams on the Xn interface. The data link layer is as specified in clause 4.
+
+The transport bearer is identified by the GTP-U TEID (TS 29.281 [3]) and the IP address (source TEID, destination TEID, source IP address, destination IP address).
+
+## 5.2 GTP-U
+
+The GTP-U (TS 29.281 [2]) protocol shall be used over the Xn interface between two NG-RAN nodes.
+
+## 5.3 UDP/IP
+
+The path protocol used shall be UDP (IETF RFC 768 [3]).
+
+The UDP port number for GTP-U shall be as defined in TS 29.281 [2].
+
+The NG-RAN nodes over the Xn interface shall support fragmentation and assembly of GTP packets at the IP layer.
+
+The NG-RAN nodes shall support IPv6 (IETF RFC 8200 [5]) and/or IPv4 (IETF RFC 791 [6]).
+
+There may be one or several IP addresses in both NG-RAN nodes. The packet processing function in the source NG-RAN node shall send downstream packets of a given flow to the target NG-RAN node IP address (received in XnAP) associated to the DL transport bearer of that particular flow. The packet processing function in the source NG-RAN node shall send upstream packets of a given flow to the target NG-RAN node IP address (received in XnAP) associated to the UL transport bearer of that particular flow.
+
+The Transport Layer Address signalled in XnAP messages is a bit string of:
+
+- 32 bits in case of IPv4 address according to IETF RFC 791 [6]; or
+- 128 bits in case of IPv6 address according to IETF RFC 8200 [5]; or
+
+- c) 160 bits if both IPv4 and IPv6 addresses are signalled, in which case the IPv4 address is contained in the first 32 bits.
+
+## 5.4 DiffServ code point marking
+
+IP Differentiated Services code point marking (IETF RFC 2474 [4]) shall be supported. The mapping between traffic categories and DiffServ code points shall be configurable by O&M based on 5G QoS Class Identifier (5QI) , the Priority Level (if explicitly signalled), and other NG-RAN traffic parameters (e.g. ARP). Traffic categories are implementation-specific and may be determined from the application parameters.
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38470/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-18/38_series/38470/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..826aef04e9c0c55cff64c93e9567cebfe72ec5ab
--- /dev/null
+++ b/marked/Rel-18/38_series/38470/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d72df68f2dfd4c58c24b2d53dd6661eb8602470c3fd84dc85ab0c6f0413d2f58
+size 21452
diff --git a/marked/Rel-18/38_series/38470/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38470/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2de10e09d952c4394ff2d9846687a64f997c2bb1
--- /dev/null
+++ b/marked/Rel-18/38_series/38470/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96175f8e48172245b865cc7a1cefbbd7301d79490ba83a634a905dd0b4815516
+size 9697
diff --git a/marked/Rel-18/38_series/38470/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38470/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fcb4a92985b28cbad62f0b122100b41c2299225
--- /dev/null
+++ b/marked/Rel-18/38_series/38470/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c16df0e2a5a78a9fcd369338761f45fd2c30ea29abc0f1d13f3b21da10c94ce
+size 7948
diff --git a/marked/Rel-18/38_series/38470/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/marked/Rel-18/38_series/38470/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c4719edf8a00d3982894200a81ddf812e4254064
--- /dev/null
+++ b/marked/Rel-18/38_series/38470/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b59b3905130f6d1e6b457af99c95b71aa07a1d2510f626b7515580d0d7e13d82
+size 22444
diff --git a/marked/Rel-18/38_series/38470/raw.md b/marked/Rel-18/38_series/38470/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a718fbec665ebadbb491bc82fc9870612dc63b75
--- /dev/null
+++ b/marked/Rel-18/38_series/38470/raw.md
@@ -0,0 +1,838 @@
+
+
+# 3GPP TS 38.470 V18.0.0 (2023-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 general aspects and principles (Release 18)**
+
+
+
+---
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black capital letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black capital letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+---
+
+NR-RAN
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+| | |
+|----------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 6 |
+| 3.1 Definitions..... | 6 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 General aspects ..... | 8 |
+| 4.1 F1 interface general principles ..... | 8 |
+| 4.2 F1 interface specification objectives..... | 8 |
+| 4.3 F1 interface capabilities ..... | 9 |
+| 4.4 Void..... | 9 |
+| 5 Functions of the F1 interface ..... | 9 |
+| 5.1 General ..... | 9 |
+| 5.2 F1-C functions..... | 9 |
+| 5.2.1 F1 interface management function ..... | 9 |
+| 5.2.2 System Information management function ..... | 10 |
+| 5.2.3 F1 UE context management function..... | 10 |
+| 5.2.4 RRC message transfer function ..... | 12 |
+| 5.2.5 Paging function..... | 12 |
+| 5.2.6 Warning messages information transfer function..... | 13 |
+| 5.2.7 Remote Interference Management (RIM) message transfer function ..... | 13 |
+| 5.2.8 Trace function..... | 13 |
+| 5.2.9 Load management function ..... | 13 |
+| 5.2.10 Self-optimisation support function ..... | 13 |
+| 5.2.11 Positioning function..... | 13 |
+| 5.2.12 IAB support function..... | 13 |
+| 5.2.13 NR MBS function..... | 14 |
+| 5.2.14 PDC measurement function..... | 14 |
+| 5.2.15 QMC support function..... | 14 |
+| 5.2.16 Timing Synchronisation Status Reporting function ..... | 14 |
+| 5.3 F1-U functions..... | 14 |
+| 5.3.1 Transfer of user data..... | 14 |
+| 5.3.2 Flow control function ..... | 15 |
+| 5.4 TEIDs allocation ..... | 15 |
+| 6 Procedures of the F1 interface ..... | 15 |
+| 6.1 Control plane procedures ..... | 15 |
+| 6.1.1 Interface Management procedures..... | 15 |
+| 6.1.2 Context Management procedures..... | 15 |
+| 6.1.3 RRC Message Transfer procedures ..... | 16 |
+| 6.1.3A Warning Message Transmission procedures ..... | 16 |
+| 6.1.4 System Information procedures..... | 16 |
+| 6.1.5 Paging procedures ..... | 16 |
+| 6.1.6 Void..... | 16 |
+| 6.1.7 Radio information transfer procedures ..... | 16 |
+| 6.1.8 UE Tracing procedures..... | 16 |
+| 6.1.9 Load management procedures..... | 17 |
+| 6.1.10 Self-optimisation support procedure ..... | 17 |
+| 6.1.11 Positioning procedures ..... | 17 |
+| 6.1.12 IAB procedures..... | 18 |
+| 6.1.13 NR MBS procedures..... | 18 |
+| 6.1.14 PDC Measurement procedures ..... | 18 |
+| 6.1.15 QMC procedures ..... | 18 |
+| 6.1.16 Timing Synchronisation Status Reporting procedures ..... | 18 |
+
+| | | |
+|-------------------------------|------------------------------------------------------------------------------------|-----------|
+| 6.2 | User plane procedures ..... | 19 |
+| 7 | F1 interface protocol structure ..... | 19 |
+| 7.1 | F1 Control Plane Protocol (F1-C) ..... | 19 |
+| 7.2 | F1 User Plane Protocol (F1-U)..... | 19 |
+| 8 | Other F1 interface specifications ..... | 20 |
+| 8.1 | NG-RAN F1 interface: layer 1 (3GPP TS 38.471) ..... | 20 |
+| 8.2 | NG-RAN F1 interface: signalling transport (3GPP TS 38.472) ..... | 20 |
+| 8.3 | NG-RAN F1 interface: F1AP specification (3GPP TS 38.473)..... | 20 |
+| 8.4 | NG-RAN F1 interface: data transport and transport signalling (3GPP TS 38.474)..... | 20 |
+| 8.5 | NG-RAN F1 interface: user plane protocol (3GPP TS 38.425)..... | 20 |
+| 8.6 | NG-RAN F1 interface: PDU Session user plane protocol (TS 38.415)..... | 20 |
+| <b>Annex A (informative):</b> | <b>Change history .....</b> | <b>21</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd 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
+
+The present document is an introduction to the 3GPP TS 38.47x series of technical specifications that define the F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.401: "NG-RAN; Architecture Description".
+- [3] 3GPP TS 38.471: "NG-RAN; F1 layer 1".
+- [4] 3GPP TS 38.472: "NG-RAN; F1 signalling transport".
+- [5] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (FIAP)".
+- [6] 3GPP TS 38.474: "NG-RAN; F1 data transport".
+- [7] 3GPP TS 38.425: "NG-RAN; Xn interface user plane protocol".
+- [8] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+- [9] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".
+- [10] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
+- [11] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
+- [12] 3GPP TS 38.415: "NG-RAN; PDU Session User Plane Protocol".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**BH RLC channel:** as defined in TS 38.300 [8].
+
+**en-gNB:** as defined in TS 37.340 [9].
+
+**gNB-CU:** as defined in TS 38.401 [2].
+
+**gNB-DU:** as defined in TS 38.401 [2].
+
+**gNB:** as defined in TS 38.300 [8].
+
+**IAB-MT:** as defined in TS 38.300 [8].
+
+**IAB-DU:** as defined in TS 38.300 [8].
+
+**IAB-node:** as defined in TS 38.300 [8].
+
+**IAB-donor:** as defined in TS 38.300 [8].
+
+**IAB-donor-CU:** as defined in TS 38.401 [2].
+
+**IAB-donor-DU:** as defined in TS 38.401 [2].
+
+**LTM:** as defined in TS 38.401 [2].
+
+**Mobile IAB-MT:** as defined in TS 38.300 [8].
+
+**Mobile IAB-DU:** as defined in TS 38.300 [8].
+
+**MP Relay UE:** as defined in TS 38.300 [8].
+
+**MP Remote UE:** as defined in TS 38.300 [8].
+
+**Multi-path:** as defined in TS 38.300 [8].
+
+**PC5 Relay RLC channel:** as defined in TS 38.300 [8].
+
+**U2N Relay UE:** as defined in TS 38.300 [8].
+
+**U2N Remote UE:** as defined in TS 38.300 [8].
+
+**Uu Relay RLC channel:** as defined in TS 38.300 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|---------|----------------------------------|
+| BH | Backhaul |
+| DRB | Data Radio Bearers |
+| eDRX | extended Discontinuous Reception |
+| eRedCap | Enhanced Reduced Capability |
+| F1-U | F1 User plane interface |
+| F1-C | F1 Control plane interface |
+| F1AP | F1 Application Protocol |
+| GTP-U | GPRS Tunnelling Protocol |
+| IAB | Integrated Access and Backhaul |
+| IP | Internet Protocol |
+| L2 | Layer-2 |
+| MBS | Multicast/Broadcast Service |
+| MP | Multi-Path |
+| N3C | Non-3GPP Connection |
+| NR-MIB | NR-Master Information Block |
+| NSAG | Network Slice AS Group |
+| O&M | Operation and Maintenance |
+| PA | Paging Area |
+| PDC | Propagation Delay Compensation |
+| PF | Paging Frame |
+| PH | Paging Hyperframes |
+| PO | Paging Occasion |
+| PTP | Point to Point |
+| PTM | Point to Multipoint |
+
+| | |
+|--------|--------------------------------------|
+| QMC | QoE Measurement Collection |
+| QoE | Quality of Experience |
+| QoS | Quality of Service |
+| RedCap | Reduced Capability |
+| RIM | Remote Interference Management |
+| RLC | Radio Link Control |
+| RRC | Radio Resource Control |
+| SCTP | Stream Control Transmission Protocol |
+| SRB | Signalling Radio Bearers |
+| SIB1 | System Information Block 1 |
+| SIB10 | System Information Block 10 |
+| SIB12 | System Information Block 12 |
+| SIB13 | System Information Block 13 |
+| SIB14 | System Information Block 14 |
+| SIB15 | System Information Block 15 |
+| SIB17 | System Information Block 17 |
+| SIB18 | System Information Block 18 |
+| SL | Sidelink |
+| TNL | Transport Network Layer |
+| U2N | UE-to-Network |
+| V2X | Vehicle-to-Everything |
+
+# --- 4 General aspects
+
+This clause captures the F1 interface principles and characteristics.
+
+## 4.1 F1 interface general principles
+
+The general principles for the specification of the F1 interface are as follows:
+
+- the F1 interface is open;
+- the F1 interface supports the exchange of signalling information between the endpoints, in addition the interface supports data transmission to the respective endpoints;
+- from a logical standpoint, the F1 is a point-to-point interface between the endpoints.
+
+NOTE: A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints.
+
+- the F1 interface supports control plane and user plane separation;
+- the F1 interface separates Radio Network Layer and Transport Network Layer;
+- the F1 interface enables exchange of UE associated information and non-UE associated information;
+- the F1 interface is designed in a future proof way to fulfil different new requirements, support new services and new functions;
+- one gNB-CU and a set of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the S1-U interfaces;
+- the gNB-CU may be separated in control plane (CP) and user plane (UP).
+
+## 4.2 F1 interface specification objectives
+
+The F1 interface specifications facilitate the following:
+
+- inter-connection of a gNB-CU and a gNB-DU supplied by different manufacturers.
+
+## 4.3 F1 interface capabilities
+
+The F1 interface supports:
+
+- procedures to establish, maintain and release radio bearers for the NG-RAN part of PDU sessions and MBS Sessions, and for E-UTRAN Radio Access Bearers;
+- procedures to establish, maintain and release BH RLC channels;
+- the separation of each UE on the protocol level for user specific signalling management;
+- the separation of each IAB-MT on the protocol level for IAB-MT specific signalling management;
+- the transfer of RRC signalling messages between the UE and the gNB-CU.
+- procedures to establish, maintain and release Uu Relay RLC channels and PC5 Relay RLC channels.
+
+## 4.4 Void
+
+# --- 5 Functions of the F1 interface
+
+## 5.1 General
+
+The following clauses describe the functions supported over F1-C and F1-U.
+
+## 5.2 F1-C functions
+
+### 5.2.1 F1 interface management function
+
+The error indication function is used by the gNB-DU or gNB-CU to indicate to the gNB-CU or gNB-DU that an error has occurred.
+
+The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-DU and the gNB-CU.
+
+The F1 setup function allows to exchange application level data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface, and exchange the intended TDD DL-UL configuration originating from the gNB-DU or destined to the gNB-DU. The F1 setup is initiated by the gNB-DU. The F1 setup function also allows to send the information of a mobile IAB-MT from the co-located mobile IAB-DU to the gNB-CU.
+
+The gNB-CU Configuration Update and gNB-DU Configuration Update functions allow to update application level configuration data needed between gNB-CU and gNB-DU to interoperate correctly over the F1 interface, and may activate or deactivate cells. The gNB-CU Configuration Update function may activate SSB beams of cells. For cross-link interference mitigation, the gNB-CU may coordinate the exchange of intended TDD DL-UL configuration by merging, forwarding and selective forwarding of intended TDD DL-UL configuration(s) between its gNB-DUs, or between its gNB-DUs and other gNBs, gNB-CUs. With the gNB-CU Configuration Update function, energy saving with cell activation/deactivation can be supported as defined in TS 38.300 [8]. The gNB-DU Configuration Update function also allows to send the information of a mobile IAB-MT from the co-located mobile IAB-DU to the gNB-CU.
+
+The F1 setup and gNB-DU Configuration Update functions allow to inform the S-NSSAI(s), NSAG(s), CAG ID(s) and NID(s) supported by the gNB-DU.
+
+The F1 setup and gNB-DU Configuration Update functions allow to provide information on either RedCap access configuration, or eRedCap access configuration, or both at the gNB-DU.
+
+The F1 setup and gNB-CU Configuration Update functions allow to inform the NID(s) available at the gNB-CU.
+
+The F1 resource coordination function is used to transfer information about frequency resource sharing between gNB-CU and gNB-DU. In case of split gNB architecture, the gNB-CU may consolidate the outgoing messages from multiple gNB-DUs and distribute the incoming messages to the involved gNB-DUs, to perform resource coordination.
+
+The gNB-DU status indication function allows the gNB-DU to indicate overload status to gNB-CU. In case of IAB, the IAB-donor-DU or IAB-DU can indicate the downlink congestion status to the IAB-donor-CU.
+
+The network access rate reduction function is used to indicate to the gNB-DU that the rate at which UEs are accessing the network need to be reduced.
+
+The F1 removal function is used to remove the interface instance and all related resources between the gNB-DU and the gNB-CU in a controlled manner.
+
+### 5.2.2 System Information management function
+
+Scheduling of system broadcast information is carried out in the gNB-DU. The gNB-DU is responsible for transmitting the system information according to the scheduling parameters available.
+
+The gNB-DU is responsible for the encoding of the NR-MIB message. In case broadcast of SIB1 and other SIBs is needed, the gNB-DU is responsible for the encoding of the SIB1 message, SIB10, SIB12, SIB13, SIB14, SIB15, SIB17, SIB18, SIB20 and SIBX, and the gNB-CU is responsible for the encoding of other SIBs. The gNB-DU may re-encode SIB9. The gNB-DU is responsible for the generation of the SystemInformation message.
+
+NOTE: The SIB19 is generated by the gNB-DU.
+
+The gNB-CU is responsible for receiving the positioning assistance information from LMF, e.g the positioning related SIBs. The gNB-CU transparently sends the positioning assistance information to the gNB-DU. The gNB-DU is responsible for broadcasting the positioning assistance information in Positioning SI message(s).
+
+To support Msg3 based on-demand SI and RRC Dedicated SIB Request as described in TS 38.331 [11], the gNB-CU can confirm the received SI request from the UE by including the UE identity, and command the gNB-DU to broadcast the requested *SystemInformation* messages including the other SI.
+
+To support UE RRC Positioning SI acquisition mechanism, as described in TS 38.331 [11], the gNB-CU can confirm the received positioning SI request from the UE by including the UE identity, and command the gNB-DU to broadcast the requested positioning SI messages.
+
+### 5.2.3 F1 UE context management function
+
+The F1 UE context management function supports the establishment and modification of the necessary overall UE context.
+
+The establishment of the F1 UE context is initiated by the gNB-CU and accepted or rejected by the gNB-DU based on admission control criteria (e.g., resource not available).
+
+The modification of the F1 UE context can be initiated by either gNB-CU or gNB-DU. The receiving node can accept or reject the modification. The F1 UE context management function also supports the release of the context previously established in the gNB-DU. The release of the context is triggered by the gNB-CU either directly or following a request received from the gNB-DU. The gNB-CU request the gNB-DU to release the UE Context when the UE enters RRC\_IDLE or RRC\_INACTIVE. In case of configured grant small data transmission, this function allows the gNB-CU to request the gNB-DU to keep part of the UE context, including at least the lower layer configuration for SDT DRB(s)/SRB(s), C-RNTI, CS-RNTI, F1AP association, and F1 tunnel information, when the gNB-CU sends the UE into RRC\_INACTIVE state. In case of positioning when the gNB-CU sends the UE into RRC\_INACTIVE state, this function allows the gNB-CU to request the gNB-DU to keep part of the positioning context, including the SRS configuration for the UE.
+
+This function can be also used to manage DRBs, SRBs and SL DRBs, i.e., establishing, modifying and releasing DRB, SRB and SL DRB resources. The establishment and modification of DRB, or SL DRB resources are triggered by the gNB-CU and accepted/rejected by the gNB-DU based on resource reservation information and QoS information to be provided to the gNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by gNB-CU to the gNB-DU in the UE Context Setup procedure and the UE Context Modification procedure. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (for SNPNs the serving SNPN ID) in the UE Context Setup procedure.
+
+This function is also used to manage a UE's configuration with multicast resources and to provide information about the multicast MRBs which are established for the multicast MBS Sessions the UE has joined.
+
+For Uu, the mapping between QoS flows and radio bearers is performed by gNB-CU and the granularity of bearer related management over F1 is radio bearer level. For NG-RAN, the gNB-CU decides an aggregated DRB QoS profile for each radio bearer based on received QoS flow profile, and provides both aggregated DRB QoS profile and QoS flow profile to the gNB-DU, and the gNB-DU either accepts the request or rejects it with appropriate cause value. With this function, gNB-DU could also notify gNB-CU whether the QoS for already established DRBs is not fulfilled any longer or it is fulfilled again. The function can be also used to inform the gNB-DU the alternative QoS Parameters Sets when available for a QoS flow. To support packet duplication for intra-gNB-DU CA and packet split/duplication for intra-DU multi-path relay as described in TS 38.300 [8], one data radio bearer should be configured with at least two GTP-U tunnels between gNB-CU and a gNB-DU.
+
+For SL, the mapping between QoS flows and radio bearers is performed by gNB-CU and the granularity of bearer related management over F1 is radio bearer level. For NG-RAN, the gNB-CU decides an aggregated SL DRB QoS profile for each radio bearer based on received QoS flow profile, and provides both aggregated SL DRB QoS profile and QoS flow profile to the gNB-DU, and the gNB-DU either accepts the request or rejects it with appropriate cause value.
+
+With this function, gNB-CU requests the gNB-DU to setup or change of the SpCell (as defined in TS 38.321 [10]) for the UE, and the gNB-DU either accepts or rejects the request with appropriate cause value. This function also enables the gNB-DU to inform the gNB-CU of which cell the UE has successfully accessed during conditional mobility.
+
+With this function, the gNB-CU requests the setup of the SCell(s) at the gNB-DU side, and the gNB-DU accepts all, some or none of the SCell(s) and replies to the gNB-CU. The gNB-CU requests the removal of the SCell(s) for the UE.
+
+With this function, the gNB-CU indicates the UL UE AMBR limit to the gNB-DU, and the gNB-DU enforces the indicated limit.
+
+With this function, the gNB-DU indicates that a bearer, or a UE is inactive or active. The gNB-CU consolidates all the serving gNB-DUs for the UE and takes further action.
+
+With this function, the gNB-CU indicates the gNB-DU that the UE context concerns mobility enhancement operation, and the gNB-DU takes corresponding actions.
+
+In addition, for IAB-nodes and IAB-donors:
+
+- The F1 UE context management function is used for managing BH RLC channels, i.e. establishing, modifying and releasing BH RLC channel resources. The establishment of BH RLC channels is triggered by the IAB-donor-CU. The establishment and modification is accepted/rejected by the IAB-node's parent, based on e.g. resource reservation information and QoS information provided to the IAB-node's parent.
+- The DRB QoS profile framework is reused for BH RLC channels carrying DRBs. Prioritization of traffic on the F1-C interface is based on traffic type (e.g. UE-associated F1AP signalling, non-UE-associated F1AP signalling) and is enforced in the IAB-donor-DU and in IAB-nodes, considering that the traffic on the F1-C interface has higher priority than other traffic; in-sequence delivery over the signaling connection is always ensured.
+- The IAB-donor-CU associates each BH RLC channel carrying control plane traffic with one of the signaled control plane traffic type values.
+
+For L2 U2N Relay:
+
+- The F1 UE context management function is used for managing Uu Relay RLC channels and PC5 Relay RLC channels for L2 U2N relay, i.e. establishing, modifying and releasing Uu Relay RLC channel and PC5 Relay RLC channel resources. The establishment of Uu Relay RLC channels and PC5 Relay RLC channels are triggered by the gNB-CU. The establishment and modification is accepted/rejected by the gNB-DU based on resource reservation information and QoS information provided to the gNB-DU. The modification of Uu/PC5 Relay RLC channels can be triggered by the gNB-CU or the gNB-DU.
+- The gNB-CU determines the QoS for the PC5 Relay RLC channel and the QoS for the Uu Relay RLC channel based on the received QoS profile for the L2 U2N Remote UE, and provides the QoS information to the gNB-DU.
+
+- The gNB-CU configures the gNB-DU about the SRB(s)/DRB(s) to Uu Relay RLC channel(s) mapping, which is used by the gNB-DU to perform data transfer of L2 U2N Remote UE. The mapping between DRB and Uu Relay RLC channel is configured at the granularity of GTP-U tunnel.
+- The gNB-CU is responsible for the local ID allocation and update for L2 U2N Remote UE.
+
+For Multi-Path relay:
+
+- The gNB-CU is responsible to determine the data split among two paths for a DRB for both intra-DU and inter-DU multi-path relay.
+- The gNB-CU takes the responsibility to decide the addition/modification/release of a path.
+- The functionality for the L2 U2N Relay can be applied to the L2 MP Relay using PC5 link.
+- Regarding the L2 MP Relay using N3C link,
+ - The F1 UE context management function is used for managing Uu Relay RLC channels for L2 MP Relay using N3C, i.e. establishing, modifying and releasing Uu Relay RLC channel resources. The establishment of Uu Relay RLC channels is triggered by the gNB-CU. The establishment or modification is accepted/rejected by the gNB-DU based on resource reservation information and QoS information provided to the gNB-DU. The modification of Uu Relay RLC channels can be triggered by the gNB-CU or the gNB-DU.
+ - The gNB-CU determines the QoS for the Uu Relay RLC channel based on the received QoS profile for the L2 MP Remote UE using N3C, and provides the QoS information to the gNB-DU.
+ - The gNB-CU configures the gNB-DU about the SRB(s)/DRB(s) to Uu Relay RLC channel(s) mapping, which is used by the gNB-DU to perform data transfer of L2 MP Remote UE using N3C. The mapping between DRB and Uu Relay RLC channel is configured at the granularity of GTP-U tunnel.
+
+With this function, the gNB-DU indicates the gNB-CU about the initiation of the cell switch command to the UE and the selected beam information, and the gNB-CU takes corresponding actions.
+
+With this function, the gNB-DU indicates the gNB-CU about the TA information, and the gNB-CU takes corresponding actions.
+
+With this function, the gNB-CU indicates the gNB-DU about the TA information, and the gNB-DU takes corresponding actions.
+
+### 5.2.4 RRC message transfer function
+
+This function allows to transfer RRC messages between gNB-CU and gNB-DU. RRC messages are transferred over F1-C. The gNB-CU is responsible for the encoding of the dedicated RRC message with assistance information provided by gNB-DU. This function also allows gNB-DU to report to gNB-CU if the downlink RRC message has been successfully delivered to UE or not. The function also allows the gNB-DU to report to the gNB-CU if the accessing UE is a Reduced Capability UE as defined in TS 38.300 [8]. This function also allows the gNB-DU to duplicate the downlink RRC message according to the duplication information provided by gNB-CU.
+
+For IAB-nodes, this function allows to transfer RRC messages for setting up and configuring the IAB-MT side of the BH RLC channel. These RRC messages are carried on F1-C between the IAB-donor-CU and the parent IAB-DU, i.e. the gNB-DU side of the BH RLC channel.
+
+### 5.2.5 Paging function
+
+The gNB-CU is responsible for filtering target cells for paging based on the UE Radio Capability for Paging. The gNB-CU may further send a list of recommended SSB beams to the gNB-DU for paging of UEs in RRC\_INACTIVE.
+
+The gNB-DU is responsible for transmitting the paging information according to the scheduling parameters provided. The gNB-DU also takes the UE paging capability into account for paging when provided by the gNB-CU.
+
+The gNB-CU provides paging information to enable the gNB-DU to calculate the exact PH, if the eDRX is configured, PO and PF. The gNB-CU determines the PA. The gNB-DU consolidates all the paging records for a particular PH, PO, PF and PA, and encodes the final RRC message and broadcasts the paging message on the respective PH, PO, PF in the PA.
+
+The paging function also supports CN controlled subgrouping paging for UE Power Saving.
+
+### 5.2.6 Warning messages information transfer function
+
+This function allows to cooperate with the warning message transmission procedures over NG interface. The gNB-CU is responsible for encoding the warning related SI message and sending it together with other warning related information for the gNB-DU to broadcast over the radio interface.
+
+### 5.2.7 Remote Interference Management (RIM) message transfer function
+
+This function enables the transfer of Remote Interference Management (RIM) backhaul messages between the gNB-CU and the gNB-DU. RIM messages are transferred over F1-C. The gNB-CU acts as a coordinator on behalf of its affiliated gNB-DUs, by merging the RIM information received from its gNB-DUs and forwarding the merged information to the target gNBs or gNB-CUs, transparently via the core network. Similarly, a gNB-CU distributes an incoming RIM backhaul message to all its concerned gNB-DUs.
+
+### 5.2.8 Trace function
+
+The Trace function provides means to control trace sessions for a UE over F1 interface.
+
+### 5.2.9 Load management function
+
+The load management function allows a gNB-CU to request the reporting of load measurements to gNB-DU and is used by gNB-DU to report the result of measurements admitted by gNB-DU.
+
+### 5.2.10 Self-optimisation support function
+
+This function allows the gNB-CU to provide information to the gNB-DU in order to support self-optimization functionality.
+
+This function also allows the gNB-DU to provide information to the gNB-CU in order to support self-optimization functionality.
+
+### 5.2.11 Positioning function
+
+This function allows to transfer location management messages between gNB-CU and gNB-DU. With this function, gNB-CU request TRP information from gNB-DU, and gNB-DU response to gNB-CU with the TRP information. With this function, gNB-CU request positioning measurements from gNB-DU, and gNB-DU response to gNB-CU with the positioning measurements.
+
+The function allows the gNB-CU to
+
+- transfer the positioning assistance data to gNB-DU. The gNB-DU is responsible for broadcasting the positioning assistance data according to the scheduling parameters available.
+- request the gNB-DU to configure SRS transmissions for UE.
+- request the gNB-DU to configure PRS transmissions.
+- request the gNB-DU to configure measurement gap or PRS processing window.
+- request the gNB-DU to activate or deactivate preconfigured measurement gap or PRS processing window.
+- request the gNB-DU to broadcast positioning system information.
+
+### 5.2.12 IAB support function
+
+The support for IAB comprises several functions.
+
+The BAP mapping configuration function allows the IAB-donor-CU to provide BAP mapping which includes the backhaul routing configuration and/or BH RLC channel mapping information for IAB-donor-DU or IAB-DU. This function also enables the IAB-donor-CU to provide the BAP header rewriting configuration, or other BAP related configurations to the IAB-DU. This function also enables the IAB-donor-CU to provide the BAP related configurations to the IAB-donor-DU.
+
+The gNB-DU resource configuration function is used by the IAB-donor-CU to provide cell resource configuration for an IAB-donor-DU or an IAB-DU, and/or NA resource configuration of a parent node IAB-DU or IAB-donor-DU serving the co-located IAB-MT for an IAB-DU, and/or information about the child node's cell resource configuration and other periodic configurations to a parent IAB-node or an IAB-donor-DU. This function also allows the IAB-donor-CU to provide the semi-static cell resource configuration of a neighbour node or a peer parent-node of a child node, whereas this neighbor node or a peer parent can be an IAB-donor-DU or an IAB-DU.
+
+The IAB TNL address configuration function enables the IAB-donor-CU to request IP address(es) to be used for IAB-node(s) from an IAB-donor-DU, or to request from an IAB-donor-DU the removal of IP address(es) used for IAB-node(s). This function is also used by the IAB-donor-CU to provide an IAB-donor-DU with the IP address information of the traffic to be transferred to a peer IAB-donor-DU via an inter-donor-DU tunnel.
+
+The IAB UP configuration update function allows the update of BH information or the UP TNL information between the IAB-donor-CU and an IAB-DU.
+
+The Mobile IAB F1 Setup Triggering function enables the IAB-donor-CU to trigger the new F1 interface establishment between a target logical mobile IAB-DU and a target F1-terminating IAB-donor-CU.
+
+The Mobile IAB F1 Setup Outcome Notification function enables the mobile IAB-DU to report the outcome of the F1 interface setup between a target logical mobile IAB-DU and a target F1-terminating IAB-donor-CU.
+
+### 5.2.13 NR MBS function
+
+The NR MBS function supports establishing, modifying and releasing the MRB resources and the user data transport.
+
+The multicast group paging function supports the sending of multicast group paging request to the gNB-DUs in order to group-page UEs that have joined the multicast MBS session.
+
+### 5.2.14 PDC measurement function
+
+The PDC measurement function allows the gNB-CU to request the gNB-DU to report measurements used for propagation delay compensation at the gNB-CU or UE.
+
+### 5.2.15 QMC support function
+
+This function enables the transfer of RAN visible QoE information from the gNB-CU to the gNB-DU.
+
+### 5.2.16 Timing Synchronisation Status Reporting function
+
+The Timing Synchronisation Status Reporting function enables the gNB-CU to request the gNB-DU node to report the RAN timing synchronisation status information.
+
+## 5.3 F1-U functions
+
+### 5.3.1 Transfer of user data
+
+This function allows to transfer of user data between gNB-CU and gNB-DU.
+
+This function also allows to transfer PDU Set Information of a QoS flow, and indication of End of Data Burst to the gNB-DU. The detailed protocol is specified in TS 38.415 [12].
+
+### 5.3.2 Flow control function
+
+This function allows to control the downlink user data flow to the gNB-DU. The detailed protocol is specified in TS 38.425 [7].
+
+## 5.4 TEIDs allocation
+
+The gNB-DU is responsible for the allocation of the F1-U DL GTP TEID for each data radio bearer.
+
+# --- 6 Procedures of the F1 interface
+
+## 6.1 Control plane procedures
+
+### 6.1.1 Interface Management procedures
+
+The F1 Interface management procedures are listed below:
+
+- Reset procedure
+- Error Indication procedure
+- F1 Setup procedure
+- gNB-DU Configuration Update procedure
+- gNB-CU Configuration Update procedure
+- gNB-DU Resource Coordination procedure
+- gNB-DU Status Indication procedure
+- F1 Removal procedure
+- Network Access Rate Reduction procedure
+
+### 6.1.2 Context Management procedures
+
+The F1 Context management procedures are listed below:
+
+- UE Context setup procedure
+- UE Context Release Request (gNB-DU initiated) procedure
+- UE Context Release (gNB-CU initiated) procedure
+- UE Context Modification (gNB-CU initiated) procedure
+- UE Context Modification Required (gNB-DU initiated) procedure
+- UE Inactivity Notification procedure
+- Notify procedure
+- Access Success procedure
+- DU-CU Cell Switch Notification procedure
+- CU-DU Cell Switch Notification procedure
+- DU-CU TA Information Transfer procedure
+
+- CU-DU TA Information Transfer procedure
+
+### 6.1.3 RRC Message Transfer procedures
+
+The F1 RRC message transfer procedures are listed below:
+
+- Initial UL RRC Message Transfer procedure
+- UL RRC Message Transfer procedure
+- DL RRC Message Transfer procedure
+- RRC Delivery Report procedure
+
+### 6.1.3A Warning Message Transmission procedures
+
+The F1 Warning message transmission procedures are listed below:
+
+- Write-Replace Warning procedure
+- PWS Cancel procedure
+- PWS Restart Indication procedure
+- PWS Failure Indication procedure
+
+### 6.1.4 System Information procedures
+
+The F1 System information procedures are listed below:
+
+- System Information Delivery procedure
+
+### 6.1.5 Paging procedures
+
+The F1 Paging procedures are listed below:
+
+- Paging procedure;
+- QoE Information Transfer Control procedure
+
+### 6.1.6 Void
+
+### 6.1.7 Radio information transfer procedures
+
+The F1 Radio information transfer procedures are listed below:
+
+- DU-CU Radio Information Transfer procedure
+- CU-DU Radio Information Transfer procedure
+
+### 6.1.8 UE Tracing procedures
+
+The following procedures are used to trace the UE:
+
+- Trace Start procedure
+- Deactivate Trace procedure
+- Cell Traffic Trace procedure
+
+### 6.1.9 Load management procedures
+
+The load management procedures are listed as below:
+
+- Resource Status Reporting Initiation procedure
+- Resource Status Reporting procedure
+
+### 6.1.10 Self-optimisation support procedure
+
+The self-optimisation support procedure is used to transfer failure and mobility related information from the gNB-CU to the gNB-DU to enable self-optimisation
+
+- Access and Mobility Indication procedure
+
+The following self-optimisation support procedure is used to indicate the availability of SON related information from the gNB-DU to the gNB-CU to enable self-optimisation.
+
+- RACH Indication
+
+### 6.1.11 Positioning procedures
+
+The F1 Positioning procedures are listed below:
+
+- Positioning Assistance Information Control procedure;
+- Positioning Assistance Information Feedback procedure;
+- Positioning Measurement procedure;
+- Positioning Measurement Report procedure;
+- Positioning Measurement Abort procedure;
+- Positioning Measurement Failure Indication procedure;
+- Positioning Measurement Update procedure;
+- TRP Information Exchange procedure;
+- Positioning Information Update;
+- Positioning Information Exchange procedure;
+- Positioning Activation procedure;
+- Positioning Deactivation procedure;
+- E-CID Measurement Initiation;
+- E-CID Measurement Failure Indication procedure;
+- E-CID Measurement Report procedure;
+- E-CID Measurement Termination procedure.
+- PRS Configuration Exchange procedure;
+- Measurement Preconfiguration;
+- Measurement Activation;
+- Positioning System Information Delivery procedure.
+
+### 6.1.12 IAB procedures
+
+The IAB procedures are listed below:
+
+- BAP Mapping Configuration procedure
+- gNB-DU Resource Configuration procedure
+- IAB TNL Address Allocation procedure
+- IAB UP Configuration Update procedure
+- Mobile IAB F1 Setup Triggering procedure
+- Mobile IAB F1 Setup Outcome Notification procedure
+
+### 6.1.13 NR MBS procedures
+
+The F1 MBS procedures are listed below:
+
+- Broadcast Context Setup;
+Broadcast Context Release (gNB-CU initiated);
+- Broadcast Context Modification;
+- Broadcast Context Release Request (gNB-DU initiated);
+- Multicast Group Paging procedure;
+- Multicast Context Setup;
+- Multicast Context Release (gNB-CU initiated);
+- Multicast Context Modification;
+- Multicast Context Release Request (gNB-DU initiated);
+- Multicast Distribution Setup;
+- Multicast Distribution Release;
+- Multicast Context Notification;
+- Broadcast Transport Resource Request;
+- Multicast Common Configuration.
+
+### 6.1.14 PDC Measurement procedures
+
+The PDC measurement procedures are listed below:
+
+- PDC Measurement Initiation procedure
+- PDC Measurement Report procedure
+
+### 6.1.15 QMC procedures
+
+The QMC procedures are listed below:
+
+- QoE Information Transfer procedure.
+
+### 6.1.16 Timing Synchronisation Status Reporting procedures
+
+The following procedures are used to report the RAN timing synchronisation status information:
+
+- Timing Synchronisation Status;
+- Timing Synchronisation Status Report;
+
+## 6.2 User plane procedures
+
+# 7 F1 interface protocol structure
+
+## 7.1 F1 Control Plane Protocol (F1-C)
+
+Figure 7.1-1 shows the protocol structure for F1-C. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as F1AP (F1 Application Protocol).
+
+
+
+The diagram illustrates the protocol stack for the F1 Control Plane (F1-C). At the top, the 'Control Plane' label is centered. Below it, the 'Radio Network Layer' is shown with a box containing 'F1AP'. A horizontal line with an oval in the center separates the Radio Network Layer from the Transport Network Layer. The Transport Network Layer is shown as a stack of four boxes: 'SCTP', 'IP', 'Data link layer', and 'Physical layer'.
+
+Figure 7.1-1: Interface protocol structure for F1-C
+
+Figure 7.1-1: Interface protocol structure for F1-C
+
+## 7.2 F1 User Plane Protocol (F1-U)
+
+Figure 7.2-1 shows the protocol structure for F1-U. The TNL is based on IP transport, comprising the UDP and GTP-U on top of IP.
+
+
+
+The diagram illustrates the protocol stack for the F1 User Plane (F1-U). At the top, the 'User Plane' label is centered. Below it, the 'Radio Network Layer' is shown with an empty box. A horizontal line with an oval in the center separates the Radio Network Layer from the Transport Network Layer. The Transport Network Layer is shown as a stack of five boxes: 'GTP-U', 'UDP', 'IP', 'Data link layer', and 'Physical layer'.
+
+Figure 7.2-1: Interface protocol structure for F1-U
+
+Figure 7.2-1: Interface protocol structure for F1-U
+
+# --- 8 Other F1 interface specifications
+
+This clause contains the description of the other related 3GPP specifications.
+
+## 8.1 NG-RAN F1 interface: layer 1 (3GPP TS 38.471)
+
+3GPP TS 38.471 [3] specifies the physical layer technologies that may be used to support the F1 interface.
+
+## 8.2 NG-RAN F1 interface: signalling transport (3GPP TS 38.472)
+
+3GPP TS 38.472 [4] specifies the signalling bearers for the F1AP for the F1-C interface.
+
+## 8.3 NG-RAN F1 interface: F1AP specification (3GPP TS 38.473)
+
+3GPP TS 38.473 [5] specifies the F1AP protocol for radio network control plane signalling over the F1 interface.
+
+## 8.4 NG-RAN F1 interface: data transport and transport signalling (3GPP TS 38.474)
+
+3GPP TS 38.474 [6] specifies the transport bearers for the user plane of the F1-U interface.
+
+## 8.5 NG-RAN F1 interface: user plane protocol (3GPP TS 38.425)
+
+3GPP TS 38.425 [7] specifies the user plane protocol being used over the F1-U interface.
+
+## 8.6 NG-RAN F1 interface: PDU Session user plane protocol (TS 38.415)
+
+3GPP TS 38.415 [12] specifies the PDU Set Information user plane protocol for sending PDU Set Information and indication of End of Data Burst over the F1-U interface.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------|-------------|--|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | |
+| 2017-06 | R3 NR#2 | R3-172492 | - | - | - | First version | 0.1.0 | |
+| 2017-07 | R3 NR#2 | R3-172639 | - | - | - | Incorporated agreed TPs from R3 NR#2 Adhoc | 0.2.0 | |
+| 2017-08 | R3#97 | R3-173450 | - | - | - | Incorporated agreed TPs from R3#97 | 0.3.0 | |
+| 2017-10 | R3#97b | R3-174244 | - | - | - | Incorporated agreed TPs from R3#97b | 0.4.0 | |
+| 2017-10 | R3#97b | R3-174259 | | | | Merged text from TS 38.401 v040 | 0.4.1 | |
+| 2017-12 | R3#98 | R3-175060 | | | | Incorporated agreed TPs from R3#98 | 0.5.0 | |
+| 2017-12 | RAN#78 | RP-172286 | | | | Submitted for approval to RAN | 1.0.0 | |
+| 2018-01 | RP-78 | | | | | TS approved by RAN plenary | 15.0.0 | |
+| 2018-03 | RP-79 | RP-180468 | 0002 | - | F | UE Context Management Procedure Related with EN-DC Operation - Stage 2 | 15.1.0 | |
+| 2018-03 | RP-79 | RP-180468 | 0006 | - | B | Correction of packet duplication | 15.1.0 | |
+| 2018-03 | RP-79 | RP-180468 | 0007 | 1 | B | SCell management | 15.1.0 | |
+| 2018-06 | RP-80 | RP-181237 | 0003 | 6 | B | Introduction of SA NR (38.470 Baseline CR covering RAN3 agreements) | 15.2.0 | |
+| 2018-06 | RP-80 | RP-181238 | 0008 | 3 | F | Adding new F1 procedure for UE Inactivity Notification | 15.2.0 | |
+| 2018-06 | RP-80 | RP-181237 | 0010 | - | B | Introduction of LTE-NR coexistence function | 15.2.0 | |
+| 2018-09 | RP-81 | RP-181922 | 0011 | 3 | F | NR Corrections (38.470 Baseline CR covering RAN3-101 agreements) | 15.3.0 | |
+| 2018-12 | RP-82 | RP-182446 | 0015 | 1 | F | F1 Load Management | 15.4.0 | |
+| 2018-12 | RP-82 | RP-182446 | 0016 | - | F | Alignment with stage3 | 15.4.0 | |
+| 2018-12 | RP-82 | RP-182446 | 0018 | 2 | F | CR to 38.470 on the introduction of RRC Delivery Report procedure | 15.4.0 | |
+| 2018-12 | RP-82 | RP-182448 | 0019 | - | F | Rapporteur CR to 38.470 | 15.4.0 | |
+| 2019-03 | RP-83 | RP-190556 | 0023 | 1 | | Energy Saving Support over F1 Interface | 15.5.0 | |
+| 2019-07 | RP-84 | RP-191396 | 0034 | 1 | F | Rapporteur updates | 15.6.0 | |
+| 2019-07 | RP-84 | RP-191396 | 0036 | 1 | F | Encoding of SIB9 in the gNB-DU | 15.6.0 | |
+| 2019-12 | RP-86 | RP-192915 | 0058 | 2 | F | E-UTRA-NR Cell-level Resource Coordination | 15.7.0 | |
+| 2019-12 | RP-86 | RP-192908 | 0035 | 2 | B | Remote Interference Management Message Transfer Support | 16.0.0 | |
+| 2019-12 | RP-86 | RP-192908 | 0038 | 1 | B | Intended DL&UL configuration for TS38.470 | 16.0.0 | |
+| 2019-12 | RP-86 | RP-192913 | 0040 | 2 | F | Trace function Support over F1 Interface | 16.0.0 | |
+| 2020-03 | RP-87-e | RP-200425 | 0062 | - | D | Rapporteur: Editorial updates | 16.1.0 | |
+| 2020-07 | RP-88-e | RP-201077 | 0026 | 15 | B | BL CR to 38.470: Support for IAB | 16.2.0 | |
+| 2020-07 | RP-88-e | RP-201080 | 0059 | 6 | B | CR to TS 38.470 on support of NPN | 16.2.0 | |
+| 2020-07 | RP-88-e | RP-201075 | 0063 | 4 | B | TS38.470 Stage2 Introduction of Mobility Enhancement Features | 16.2.0 | |
+| 2020-07 | RP-88-e | RP-201082 | 0064 | 3 | B | BLCR to 38.470: Addition of SON feature | 16.2.0 | |
+| 2020-07 | RP-88-e | RP-201074 | 0065 | 6 | B | Support of NR V2X SIB in gNB-DU | 16.2.0 | |
+| 2020-07 | RP-88-e | RP-201079 | 0067 | 2 | B | PDCP duplication with more than 2 entities for F1 stage 2 | 16.2.0 | |
+| 2020-07 | RP-88-e | RP-201082 | 0068 | 1 | B | BLCR to 38.470: Addition of MDT feature | 16.2.0 | |
+| 2020-09 | RP-89-e | RP-201945 | 0061 | 8 | B | Positioning support over F1AP | 16.3.0 | |
+| 2020-09 | RP-89-e | RP-201956 | 0069 | - | F | Rapporteur Corrections | 16.3.0 | |
+| 2021-03 | RP-91-e | RP-210231 | 0070 | 3 | F | Correction on IAB procedures | 16.4.0 | |
+| 2021-06 | RP-92-e | RP-211330 | 0075 | | F | Stage-2 CR on system information message over F1 (Rel-16) | 16.5.0 | |
+| 2022-03 | RP-95-e | RP-220276 | 0084 | | F | (Stage-2) Clarification on IAB Address Remove | 16.6.0 | |
+| 2022-03 | RP-95-e | RP-220224 | 0071 | 8 | B | Introduction of NR MBS | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220222 | 0076 | 5 | B | CP-based Congestion Mitigation for IAB Network | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220230 | 0078 | 4 | B | BL CR to 38.470 Support for Redcap UEs | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220228 | 0079 | 3 | B | Introduction of release 17 positioning enhancements | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220235 | 0080 | 2 | B | Support for UE Power Saving Enhancements | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220233 | 0081 | 2 | B | CG-SDT BLCR to TS 38.470 | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220236 | 0083 | 1 | D | Editorial corrections | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220231 | 0085 | 1 | B | (Stage-2 F1AP CR) support for NR Sidelink Relay | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220223 | 0086 | | B | Introduction of Propagation Delay Compensation Procedure | 17.0.0 | |
+| 2022-03 | RP-95-e | RP-220229 | 0087 | - | B | Support of QoE functionality | 17.0.0 | |
+| 2022-06 | RP-96 | RP-221134 | 0088 | 1 | F | Corrections on NR MBS in 38470 | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221142 | 0090 | 1 | F | CR on SIB18 signalling | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221154 | 0092 | - | A | Clarification on SRB duplication for TS38.470 (R17) | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221127 | 0093 | 2 | F | Correction to 38.470 for capturing SIB19 | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221133 | 0094 | 2 | F | Clarification on paging capability for TS38.470 | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221145 | 0096 | - | D | Editorial corrections | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221145 | 0097 | 1 | F | Supporting the disaster roaming information [MINT] | 17.1.0 | |
+| 2022-06 | RP-96 | RP-221143 | 0099 | - | F | QoE Rel-17 Corrections | 17.1.0 | |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2022-06 | RP-96 | RP-221128 | 0100 | 2 | F | IAB Rel-17 Corrections | 17.1.0 |
+| 2022-06 | RP-96 | RP-221131 | 0101 | | F | CR for Preconfiguration Activation/Deactivation | 17.1.0 |
+| 2022-09 | RP-97-e | RP-222187 | 0102 | 1 | F | Clarification on F1 Paging function | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222190 | 0104 | 1 | F | Correction on NR SL Relay for TS 38.470 | 17.2.0 |
+| 2022-09 | RP-97-e | RP-222184 | 0105 | 1 | F | Supporting network slice AS group | 17.2.0 |
+| 2022-12 | RP-98-e | RP-222887 | 0107 | 1 | A | Correction to 38.470 on Positioning System Information | 17.3.0 |
+| 2022-12 | RP-98-e | RP-222887 | 0108 | 1 | F | Stage 2 text addition on UE context management function for positioning | 17.3.0 |
+| 2023-03 | RAN#99 | RP-230588 | 0110 | - | A | Stage 2 text addition on SRS configuration for positioning | 17.4.0 |
+| 2023-06 | RAN#100 | RP-231075 | 0113 | 1 | A | Correction of SIType List | 17.5.0 |
+| 2023-09 | RAN#101 | RP-231900 | 0116 | - | A | Correction on Positioning SI handling over F1 | 17.6.0 |
+| 2023-12 | RAN#102 | RP-233829 | 0111 | 8 | B | Introduction of NR MBS enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233832 | 0114 | 5 | B | Addition of SON features enhancement | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233834 | 0117 | 5 | B | Support of mobile IAB | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233823 | 0118 | 3 | B | Support of NR SL relay enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233838 | 0119 | 3 | B | Introduction of 5G Timing Resiliency and URLLC enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233833 | 0120 | 4 | B | Introduction of R18 QoE measurement enhancements | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233817 | 0121 | 2 | B | Network energy saving techniques | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233818 | 0123 | 0 | B | Introduction of LTM | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233816 | 0124 | 0 | B | Introduction of NR RedCap Enhancement | 18.0.0 |
+| 2023-12 | RAN#102 | RP-233831 | 0125 | 0 | B | Support for XR UP design using new container | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38843/179c2b96202f20634ec21def17c1cd86_img.jpg b/marked/Rel-18/38_series/38843/179c2b96202f20634ec21def17c1cd86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a34bffaaa494e0d0b352b690bec76f4bc6af8710
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/179c2b96202f20634ec21def17c1cd86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7df37366e62e67e6c068c84eb1b36651e6ea5069dd612bd72872112b727664c
+size 24416
diff --git a/marked/Rel-18/38_series/38843/1ad662a678c4f002de911d403f00de8e_img.jpg b/marked/Rel-18/38_series/38843/1ad662a678c4f002de911d403f00de8e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..082dfe650e7bdf79f56fb4b44e69e5ea02b18b69
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/1ad662a678c4f002de911d403f00de8e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f583c8fcd00c433624de31b2486f7badf43816cc377bb3afac002ce44692722c
+size 9651
diff --git a/marked/Rel-18/38_series/38843/1f1ca53cce40d1c5f03ac6b5c94b4e6b_img.jpg b/marked/Rel-18/38_series/38843/1f1ca53cce40d1c5f03ac6b5c94b4e6b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eb7326f6f9570da9e9c6dabaedb17e41197d7a4f
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/1f1ca53cce40d1c5f03ac6b5c94b4e6b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5fe3bc98a62e8d39b9da8e1394ffd9c6c7da7f1773d3fddead1816692f0dad4
+size 19878
diff --git a/marked/Rel-18/38_series/38843/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-18/38_series/38843/29f586959675cafdf81cf934954908eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e618599a41b927693c9c84e88cebed88d68bd3ad
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/29f586959675cafdf81cf934954908eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e126eab8dd828e390ce6da45e8f789f0481442e1b3c02e68c4bf057798ba0ba
+size 52893
diff --git a/marked/Rel-18/38_series/38843/45578bd3ed11d45af63ce00e28bab2f8_img.jpg b/marked/Rel-18/38_series/38843/45578bd3ed11d45af63ce00e28bab2f8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..06ea17c5a97443b35148eb2449f0d2223d2cc772
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/45578bd3ed11d45af63ce00e28bab2f8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb5367f3c1e512c5393469ce9fbea7e48c94bbcb442549807dac2b34348bdc82
+size 26182
diff --git a/marked/Rel-18/38_series/38843/4f7470055bfc22c4aa6b007a4056940e_img.jpg b/marked/Rel-18/38_series/38843/4f7470055bfc22c4aa6b007a4056940e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34589a92f9f91eaa92605b32ba22919cb5aa2753
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/4f7470055bfc22c4aa6b007a4056940e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:03921bedb3b0a2d6e7097efdd0dfd13d396ec03dfc8dae372851c3e438db9a71
+size 25483
diff --git a/marked/Rel-18/38_series/38843/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38843/53d8bef47c63e0897de4cd058bad2cbd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cee41c67c2e99c4b905f70ad13d0379b5322ee47
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/53d8bef47c63e0897de4cd058bad2cbd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:299e1c51eefe98fdc5796aaa7be326a0b2aec2dabb8479466786700eb39d3000
+size 18815
diff --git a/marked/Rel-18/38_series/38843/5ae0af74768ab8a326191d61781d98e6_img.jpg b/marked/Rel-18/38_series/38843/5ae0af74768ab8a326191d61781d98e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82fdd4dcf49c7d313cc3202c5f23f0eefb254932
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/5ae0af74768ab8a326191d61781d98e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31e82ef3c610e942a9554393b8334e4becfd8c47e534ac21a4cf46158eb62917
+size 22625
diff --git a/marked/Rel-18/38_series/38843/5bba23cc120ad806779f82df1c01bebf_img.jpg b/marked/Rel-18/38_series/38843/5bba23cc120ad806779f82df1c01bebf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..497c97f30faa33af21d418bddca6034e18250fbf
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/5bba23cc120ad806779f82df1c01bebf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4ab26ff0ffe0aa64dbbb5df3abe6d5e4d07ecf1c52ada46200af986849b10948
+size 23720
diff --git a/marked/Rel-18/38_series/38843/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/marked/Rel-18/38_series/38843/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a789b768ecf07ece9386c385dc8d1a32f57158cb
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2200675dea9c6063dc9c6bb467c48376745fcc7675584bed3dfab0eacbec7f35
+size 29392
diff --git a/marked/Rel-18/38_series/38843/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38843/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0384b52849c0b8bdf9ab09c34bbac6c933420758
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b188f95f6516c6d1b8fd12682bd9831c73daeed1330fad3564886d68ebcd2bca
+size 9593
diff --git a/marked/Rel-18/38_series/38843/6231ba981d3d1ab7ce0cae71abd08c17_img.jpg b/marked/Rel-18/38_series/38843/6231ba981d3d1ab7ce0cae71abd08c17_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ea9eabe005bcc6e5103db5f0edd59d93c87084a
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/6231ba981d3d1ab7ce0cae71abd08c17_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1eb3579c3953a2f301baa041c3ca9e3aa2f77e256dc2ab1364d753467d2bc9e4
+size 26133
diff --git a/marked/Rel-18/38_series/38843/6381dcd91bf4636842734ec95bbd75d4_img.jpg b/marked/Rel-18/38_series/38843/6381dcd91bf4636842734ec95bbd75d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76744980f331476640d9394548ec0f96fff7c810
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/6381dcd91bf4636842734ec95bbd75d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86cd7bd29ffc9b73dc58c62e1fd8cab9d5f062d0410e0fed781ba8a9b6a0e0ea
+size 20713
diff --git a/marked/Rel-18/38_series/38843/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38843/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7c287eb22863c90947c68bcef75dc94f6f2fe7a4
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:379499a7ae621a6e616fec88afab262c0466982d0ee6aaa425202f0d9034bbe0
+size 5669
diff --git a/marked/Rel-18/38_series/38843/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-18/38_series/38843/6e15fc9ea763541c5913d26f85072ae1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0763f260595a9da8b7adb53c933f804b41c91cf1
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/6e15fc9ea763541c5913d26f85072ae1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c9c2118e4bfebc3275fec57850943665b508ca1dadae6a83edbda3822f3e662
+size 34731
diff --git a/marked/Rel-18/38_series/38843/70546cb98239089866510133c7fbc169_img.jpg b/marked/Rel-18/38_series/38843/70546cb98239089866510133c7fbc169_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13905f83f63d10e19db96c223de40b8086236bfc
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/70546cb98239089866510133c7fbc169_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88f1d5347686be62fa1b767ed36d1d784620e8ed03d99d08f8e0d5206391e853
+size 18557
diff --git a/marked/Rel-18/38_series/38843/70a07cbdcf39ad922c4f80528f12bc46_img.jpg b/marked/Rel-18/38_series/38843/70a07cbdcf39ad922c4f80528f12bc46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00933d8b7be2e4c27d0dd2c33a066f9feed1a9b6
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/70a07cbdcf39ad922c4f80528f12bc46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e35c92dceb93efc625f5b748f327f8847a51181312bd86b84a67289eba660fda
+size 20029
diff --git a/marked/Rel-18/38_series/38843/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-18/38_series/38843/72d448a65347c51989171748789c7d4b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3a065ff29b9e5475271dc3e0ff17383223b75147
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/72d448a65347c51989171748789c7d4b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0eb86c588c93223c9e91e90123a4bd71a4f52a467f6310934a24d03ab680ed77
+size 24432
diff --git a/marked/Rel-18/38_series/38843/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38843/7c0a9511fa02b6c2c125ff5be465186e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ab75e4706b85c13c8691ba2afd3f4c5dc9fa89b
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/7c0a9511fa02b6c2c125ff5be465186e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:47499ffcc4616564350b2e3c583de0c15fd89c792aeb8691366f5283b9a60fdf
+size 20817
diff --git a/marked/Rel-18/38_series/38843/7f950d8071cc74c5c726756baed72584_img.jpg b/marked/Rel-18/38_series/38843/7f950d8071cc74c5c726756baed72584_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c954385196dc322331b95a4e5761cda39a6ebae
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/7f950d8071cc74c5c726756baed72584_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f7e6339712c195c5320b968c223552ecf576c4d4061c07c8c1abf77a099efd2
+size 21058
diff --git a/marked/Rel-18/38_series/38843/809eec371620084c4b949c66d5d7bae0_img.jpg b/marked/Rel-18/38_series/38843/809eec371620084c4b949c66d5d7bae0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0338fbc0d06b145c4379220daa6a73f57b99bff5
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/809eec371620084c4b949c66d5d7bae0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7319fbe7b68e8b66500000986b45329c38bd5106232395f10e9cecaf802d2204
+size 23262
diff --git a/marked/Rel-18/38_series/38843/8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg b/marked/Rel-18/38_series/38843/8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8a379c7f89fa3eff40d7a809095b01d69ef25b54
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/8e6f0b87d128da8e5d79d274d0c14ed5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78896085ee5569fddc6e872d5dae9ef174513aef5316a361f91d5e153aa09938
+size 139883
diff --git a/marked/Rel-18/38_series/38843/94cf6c39e3a81645f7e5d3a289cf49f4_img.jpg b/marked/Rel-18/38_series/38843/94cf6c39e3a81645f7e5d3a289cf49f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6325e32d492edcf4c6e8c3a88479f824c4ad0b29
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/94cf6c39e3a81645f7e5d3a289cf49f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c043985525c6f3eeaccc8d940bc27c110c8ad5f367dae5f5c4619a8e26dc0b9
+size 43870
diff --git a/marked/Rel-18/38_series/38843/bde47102e9a0e563aaea7734738b8eea_img.jpg b/marked/Rel-18/38_series/38843/bde47102e9a0e563aaea7734738b8eea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa0d61bc4b8162c6caadd6fdeaee1383e0fb5f9e
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/bde47102e9a0e563aaea7734738b8eea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:655a6b424e421b5171c20335d43a778f29a862c2c9c353a92e703bcd6eaec25c
+size 60892
diff --git a/marked/Rel-18/38_series/38843/bfde27036f8cdbc8ed561e547f0a9483_img.jpg b/marked/Rel-18/38_series/38843/bfde27036f8cdbc8ed561e547f0a9483_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1a0db75b0d8f374ef85298f2cb6b04318ab68f4b
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/bfde27036f8cdbc8ed561e547f0a9483_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6c476441e9f023eeff1ccc6c2517f397d5f0598673e5273c2d94e043ce338df
+size 23389
diff --git a/marked/Rel-18/38_series/38843/c879d6feb77f5e629e8feb3b42d5a139_img.jpg b/marked/Rel-18/38_series/38843/c879d6feb77f5e629e8feb3b42d5a139_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44bcf8ce1dfa4ed10ae2aaccbdc34ad9d02d3517
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/c879d6feb77f5e629e8feb3b42d5a139_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72b9caa3751d0947786e2f20a6b253d0c95ccedecbcf82a0deef9b4924ba4dda
+size 23152
diff --git a/marked/Rel-18/38_series/38843/cc3cf220e0c191212afa284c6787da0a_img.jpg b/marked/Rel-18/38_series/38843/cc3cf220e0c191212afa284c6787da0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1201435e48c90d002ab146598f9f730a2105c4d
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/cc3cf220e0c191212afa284c6787da0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:274097cf54ab218723fc9562310545f88a03a0559646576ae74b0dca83f3214f
+size 18569
diff --git a/marked/Rel-18/38_series/38843/d884367c84ba50f250499f79c4b4b950_img.jpg b/marked/Rel-18/38_series/38843/d884367c84ba50f250499f79c4b4b950_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05211395e1ab2c4ce6868598351e2a94441f6311
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/d884367c84ba50f250499f79c4b4b950_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79e52597e9a8580e2a7edfe2030fa234daa5af81290f1718d6639569c6147689
+size 46136
diff --git a/marked/Rel-18/38_series/38843/e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg b/marked/Rel-18/38_series/38843/e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de9b56b244e131cbb7828546b92a836fdb2576b6
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/e034b0863f1ccdc3e0b3d0e2f449be66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e856d70f0178a0293b6fe18332213cc6ddfcc373eb1f1a92a25389520bedef4
+size 27192
diff --git a/marked/Rel-18/38_series/38843/ed1994bc0ee2985615e5b31df0b48534_img.jpg b/marked/Rel-18/38_series/38843/ed1994bc0ee2985615e5b31df0b48534_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8905b3251da60a55d1e2c48672cc20f5dc3c054e
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/ed1994bc0ee2985615e5b31df0b48534_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c300e7a3938b8ce987f6fcea3e7105241191740a1b84a98ad7cad3f548c8009b
+size 19974
diff --git a/marked/Rel-18/38_series/38843/f2c195cafc9541703723427873c93a64_img.jpg b/marked/Rel-18/38_series/38843/f2c195cafc9541703723427873c93a64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0832480ee0c8ae1ab8f5679254ef3a6b5c9f517
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/f2c195cafc9541703723427873c93a64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92b33a9730e6da70ddab2ca0db5a5175524e0d80bbaab981f2baebd7de683684
+size 14191
diff --git a/marked/Rel-18/38_series/38843/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-18/38_series/38843/f455955c4bc84005728b4138f19098dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9117c9e1745fdb76052b1e99695781cbc224983
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/f455955c4bc84005728b4138f19098dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a055611f162bd00bf691656a591861de4080462651f79f29aaeb0cf32addcaf
+size 23388
diff --git a/marked/Rel-18/38_series/38843/f68421f5d184c116a7061977a9057e63_img.jpg b/marked/Rel-18/38_series/38843/f68421f5d184c116a7061977a9057e63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bd8ef10abfc836cb5e7540532f6e11c51b66fa4
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/f68421f5d184c116a7061977a9057e63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cecfaad494a84a9bb7ba6a842925d76b61a252e46d6ec7380408d86e033f015c
+size 53452
diff --git a/marked/Rel-18/38_series/38843/fb73a07d61dc5c47709b9802b894d716_img.jpg b/marked/Rel-18/38_series/38843/fb73a07d61dc5c47709b9802b894d716_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa141a8937deaee26d2bcf98fd57cebdf98fe106
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/fb73a07d61dc5c47709b9802b894d716_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc1b7d737e93df677f88d7733833ef2ec23bfde5e9f8c1bc26ae9c116cb33e23
+size 30083
diff --git a/marked/Rel-18/38_series/38843/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/Rel-18/38_series/38843/ff7977984f2552f326b2089d7595fff3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4342a34abbefe2942c56630c306ad61b84a14ba6
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/ff7977984f2552f326b2089d7595fff3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0234413594fe267be3728b8dc674ea375501386e400dceb3177beb9e4c30f5e
+size 29699
diff --git a/marked/Rel-18/38_series/38843/raw.md b/marked/Rel-18/38_series/38843/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d89cd17a92781855a1b2915ae009dc09f0e835b
--- /dev/null
+++ b/marked/Rel-18/38_series/38843/raw.md
@@ -0,0 +1,6088 @@
+
+
+# 3GPP TR 38.843 V18.0.0 (2023-12)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|------------------------------------------------------------------------------------------------|-----|
+| Foreword ..... | 5 |
+| Introduction ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 9 |
+| 3 Definitions of terms, symbols and abbreviations..... | 9 |
+| 3.1 Terms..... | 9 |
+| 3.2 Symbols ..... | 11 |
+| 3.3 Abbreviations ..... | 11 |
+| 4 General AI/ML framework ..... | 12 |
+| 4.1 Description of AI/ML stages..... | 12 |
+| 4.2 Life cycle management ..... | 12 |
+| 4.3 Collaboration levels..... | 15 |
+| 4.4 Functional framework details ..... | 16 |
+| 5 Use cases..... | 16 |
+| 5.1 CSI feedback enhancement ..... | 16 |
+| 5.2 Beam management ..... | 19 |
+| 5.3 Positioning accuracy enhancements..... | 21 |
+| 6 Evaluations..... | 21 |
+| 6.1 Common evaluation methodology and KPIs..... | 22 |
+| 6.2 CSI feedback enhancement ..... | 23 |
+| 6.2.1 Evaluation assumptions, methodology and KPIs ..... | 23 |
+| 6.2.2 Performance results ..... | 33 |
+| 6.2.2.1 1-on-1 joint training for CSI compression ..... | 35 |
+| 6.2.2.2 Generalization evaluations for CSI compression..... | 45 |
+| 6.2.2.3 Scalability evaluations for CSI compression ..... | 48 |
+| 6.2.2.4 Multi-vendor joint training for CSI compression ..... | 50 |
+| 6.2.2.5 Separate training for CSI compression ..... | 51 |
+| 6.2.2.6 Basic performance for CSI prediction ..... | 55 |
+| 6.2.2.7 Generalization evaluations for CSI prediction..... | 58 |
+| 6.2.2.8 Summary of Performance Results for CSI feedback enhancement ..... | 59 |
+| 6.3 Beam management ..... | 59 |
+| 6.3.1 Evaluation assumptions, methodology and KPIs ..... | 59 |
+| 6.3.2 Performance results ..... | 69 |
+| 6.3.2.1 Basic performance for BM-Case1 ..... | 69 |
+| 6.3.2.1.1 Performance when Set B is a subset of Set A for DL Tx beam prediction ..... | 70 |
+| 6.3.2.1.2 Performance when Set B is different than Set A for DL Tx beam prediction ..... | 72 |
+| 6.3.2.1.3 Performance when Set B is a subset of Set A for DL Tx-Rx beam pair prediction..... | 73 |
+| 6.3.2.1.4 Performance when Set B is different to Set A for DL Tx-Rx beam pair prediction ..... | 76 |
+| 6.3.2.2 Basic performance for BM-Case2 ..... | 76 |
+| 6.3.2.2.1 Performance when Set A = Set B..... | 76 |
+| 6.3.2.2.2 Performance when Set B is a subset of Set A ..... | 85 |
+| 6.3.2.3 Performance under different assumptions/scenarios for BM-Case1 and/or BM-Case2 ..... | 93 |
+| 6.3.2.4 Generalization Performance for BM-Case1 and BM-Case2 ..... | 101 |
+| 6.3.2.5 Summary of Performance Results for Beam Management..... | 106 |
+| 6.4 Positioning accuracy enhancements..... | 108 |
+| 6.4.1 Evaluation assumptions, methodology and KPIs ..... | 108 |
+| 6.4.2 Performance results ..... | 115 |
+| 6.4.2.1 Training Data Collection..... | 116 |
+| 6.4.2.2 Generalization Aspects ..... | 116 |
+| 6.4.2.3 Fine-tuning..... | 120 |
+| 6.4.2.4 Model-input Size Reduction ..... | 127 |
+| 6.4.2.5 Non-ideal label(s)..... | 130 |
+| 6.4.2.6 Summary of Performance Results for Positioning accuracy enhancements..... | 131 |
+
+| | | |
+|-----------------------------------------------|-------------------------------------------------|------------|
+| 7 | Potential specification impact assessment ..... | 131 |
+| 7.1 | General observations ..... | 131 |
+| 7.2 | Physical layer aspects..... | 131 |
+| 7.2.1 | Common framework..... | 131 |
+| 7.2.2 | CSI feedback enhancement ..... | 132 |
+| 7.2.3 | Beam management ..... | 135 |
+| 7.2.4 | Positioning accuracy enhancements ..... | 139 |
+| 7.3 | Protocol aspects..... | 145 |
+| 7.3.1 | Common framework..... | 145 |
+| 7.3.2 | CSI feedback enhancement ..... | 145 |
+| 7.3.3 | Beam management ..... | 145 |
+| 7.3.4 | Positioning accuracy enhancements ..... | 145 |
+| 7.4 | Interoperability and testability aspects..... | 145 |
+| 7.4.1 | Common framework..... | 145 |
+| 7.4.2 | CSI feedback enhancement ..... | 145 |
+| 7.4.3 | Beam management ..... | 145 |
+| 7.4.4 | Positioning accuracy enhancements ..... | 145 |
+| 8 | Conclusions..... | 145 |
+| <b>Annex <X> : Change history .....</b> | | <b>146</b> |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The application of AI/ML to wireless communications has been thus far limited to implementation-based approaches, both, at the network and the UE sides. A study on enhancement for data collection for NR and ENDC (*FS\_NR\_ENDC\_data\_collect*) has examined the *functional framework for RAN intelligence enabled by further enhancement of data collection through use cases, examples etc. and identify the potential standardization impacts on current NG-RAN nodes and interfaces*. In SA WG2 AI/ML related study, a network functionality NWDAF (Network Data Analytics Function) was introduced in Rel-15 and has been enhanced in Rel-16 and Rel-17.
+
+This study explores the benefits of augmenting the air-interface with features enabling improved support of AI/ML. The 3GPP framework for AI/ML is studied for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.
+
+Through studying a few carefully selected use cases, assessing their performance in comparison with traditional methods and the associated potential specification impacts that enable their solutions, this study lays the foundation for future air-interface use cases leveraging AI/ML techniques.
+
+Sufficient use cases are targeted to enable the identification of a common AI/ML framework, including functional requirements of AI/ML architecture, which could be used in subsequent projects. The study also serves identifying areas where AI/ML could improve the performance of air-interface functions.
+
+The study serves identifying what is required for an adequate AI/ML model characterization and description establishing pertinent notation for discussions and subsequent evaluations. Various levels of collaboration between the gNB and UE are identified and considered.
+
+Evaluations to exercise the attainable gains of AI/ML based techniques for the use cases under consideration are carried out with the corresponding identification of KPIs with the goal to have a better understanding of the attainable gains and associated complexity requirements.
+
+Finally, specification impact are assessed in order to improve the overall understanding of what would be required to enable AI/ML techniques for the air-interface.
+
+The central objective of this project is to study the 3GPP framework for AI/ML for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.
+
+The use cases to focus include:
+
+- CSI feedback enhancement
+ - Spatial-frequency domain CSI compression using two-sided AI model
+ - Time domain CSI prediction using UE sided model
+- Beam management
+ - Spatial-domain Downlink beam prediction for Set A of beams based on measurement results of Set B of beams
+ - Temporal Downlink beam prediction for Set A of beams based on the historic measurement results of Set B of beams
+- Positioning accuracy enhancements
+ - Direct AI/ML positioning
+ - AI/ML assisted positioning
+
+Note: the selection of use cases for this study solely targets the formulation of a framework to apply AI/ML to the air-interface for these and other use cases. The selection itself does not intend to provide any indication of the prospects of any future normative project.
+
+This study also introduces AI/ML model terminology and description to identify common and specific characteristics for framework investigations, namely to:
+
+- Characterize the defining stages of AI/ML related algorithms and associated complexity:
+ - Model generation, e.g., model training (including input/output, pre-/post-process, online/offline as applicable), model validation, model testing, as applicable
+ - Inference operation, e.g., input/output, pre-/post-process, as applicable
+- Identify various levels of collaboration between UE and gNB pertinent to the selected use cases, e.g.,
+ - No collaboration: implementation-based only AI/ML algorithms without information exchange [for comparison purposes]
+ - Various levels of UE/gNB collaboration targeting at separate or joint ML operation.
+- Characterize lifecycle management of AI/ML model: e.g., model training, model deployment, model inference, model monitoring, model updating
+- Dataset(s) for training, validation, testing, and inference
+- Identify common notation and terminology for AI/ML related functions, procedures and interfaces
+- Note: the work done for *FS\_NR\_ENDC\_data\_collect* is considered when appropriate
+
+For the use cases under consideration:
+
+## 1) Performance benefits of AI/ML based algorithms for the agreed use cases are evaluated:
+
+- Methodology based on statistical models (from TR 38.901 and TR 38.857 [positioning]), for link and system level simulations.
+ - Extensions of 3GPP evaluation methodology for better suitability to AI/ML based techniques should be considered as needed.
+ - Whether field data are optionally needed to further assess the performance and robustness in real-world environments should be discussed as part of the study.
+ - Need for common assumptions in dataset construction for training, validation and test for the selected use cases.
+ - Consider adequate model training strategy, collaboration levels and associated implications
+ - Consider agreed-upon base AI model(s) for calibration
+ - AI model description and training methodology used for evaluation should be reported for information and cross-checking purposes
+- KPIs: Determine the common KPIs and corresponding requirements for the AI/ML operations. Determine the use-case specific KPIs and benchmarks of the selected use-cases.
+ - Performance, inference latency and computational complexity of AI/ML based algorithms should be compared to that of a state-of-the-art baseline
+ - Overhead, power consumption (including computational), memory storage, and hardware requirements (including for given processing delays) associated with enabling respective AI/ML scheme, as well as generalization capability should be considered.
+
+## 2) Potential specification impact, specifically for the agreed use cases and for a common framework, is assessed:
+
+- PHY layer aspects, e.g., (RAN1)
+ - Considering aspects related to, e.g., the potential specification of the AI Model lifecycle management, and dataset construction for training, validation and test for the selected use cases
+ - Use case and collaboration level specific specification impact, such as new signalling, means for training and validation data assistance, assistance information, measurement, and feedback
+
+- Protocol aspects, e.g., (RAN2) - RAN2 only starts the work after there is sufficient progress on the use case study in RAN1
+- Considering aspects related to, e.g., capability indication, configuration and control procedures (training/inference), and management of data and AI/ML model, per RAN1 input
+- Collaboration level specific specification impact per use case
+- Interoperability and testability aspects, e.g., (RAN4) - RAN4 only starts the work after there is sufficient progress on use case study in RAN1 and RAN2
+- Requirements and testing frameworks to validate AI/ML based performance enhancements and ensuring that UE and gNB with AI/ML meet or exceed the existing minimum requirements if applicable
+- Considering the need and implications for AI/ML processing capabilities definition
+
+Note 1: Specific AI/ML models are not expected to be specified and are left to implementation. User data privacy needs to be preserved.
+
+Note 2: The study on AI/ML for air interface is based on the current RAN architecture and new interfaces shall not be introduced.
+
+# --- 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] RP-213599: "New SI: Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface", Qualcomm (Moderator).
+- [3] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz".
+- [4] 3GPP TR 38.857: "Study on NR positioning enhancements".
+- [5] 3GPP TR 38.802: "Study on new radio access technology Physical layer aspects".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms 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].
+
+**AI/ML-enabled Feature:** refers to a Feature where AI/ML may be used.
+
+**AI/ML Model:** A data driven algorithm that applies AI/ML techniques to generate a set of outputs based on a set of inputs.
+
+**AI/ML model delivery:** A generic term referring to delivery of an AI/ML model from one entity to another entity in any manner. Note: An entity could mean a network node/function (e.g., gNB, LMF, etc.), UE, proprietary server, etc.
+
+**AI/ML model Inference:** A process of using a trained AI/ML model to produce a set of outputs based on a set of inputs.
+
+**AI/ML model testing:** A subprocess of training, to evaluate the performance of a final AI/ML model using a dataset different from one used for model training and validation. Differently from AI/ML model validation, testing does not assume subsequent tuning of the model.
+
+**AI/ML model training:** A process to train an AI/ML Model [by learning the input/output relationship] in a data driven manner and obtain the trained AI/ML Model for inference.
+
+**AI/ML model transfer:** Delivery of an AI/ML model over the air interface in a manner that is not transparent to 3GPP signalling, either parameters of a model structure known at the receiving end or a new model with parameters. Delivery may contain a full model or a partial model.
+
+**AI/ML model validation:** A subprocess of training, to evaluate the quality of an AI/ML model using a dataset different from one used for model training, that helps selecting model parameters that generalize beyond the dataset used for model training.
+
+**Data collection:** A process of collecting data by the network nodes, management entity, or UE for the purpose of AI/ML model training, data analytics and inference.
+
+**Federated learning / federated training:** A machine learning technique that trains an AI/ML model across multiple decentralized edge nodes (e.g., UEs, gNBs) each performing local model training using local data samples. The technique requires multiple interactions of the model, but no exchange of local data samples.
+
+**Functionality identification:** A process/method of identifying an AI/ML functionality for the common understanding between the NW and the UE. Note: Information regarding the AI/ML functionality may be shared during functionality identification. Where AI/ML functionality resides depends on the specific use cases and sub use cases.
+
+**Management instruction:** Information needed to ensure proper inference operation. This information may include selection/(de)activation/switching of AI/ML models or AI/ML functionalities, fallback to non-AI/ML operation, etc.
+
+**Model activation:** enable an AI/ML model for a specific AI/ML-enabled feature.
+
+**Model deactivation:** disable an AI/ML model for a specific AI/ML-enabled feature.
+
+**Model download:** Model transfer from the network to UE.
+
+**Model identification:** A process/method of identifying an AI/ML model for the common understanding between the NW and the UE. Note: The process/method of model identification may or may not be applicable. Note: Information regarding the AI/ML model may be shared during model identification.
+
+**Model monitoring:** A procedure that monitors the inference performance of the AI/ML model.
+
+**Model parameter update:** Process of updating the model parameters of a model.
+
+**Model selection:** The process of selecting an AI/ML model for activation among multiple models for the same AI/ML enabled feature. Note: Model selection may or may not be carried out simultaneously with model activation.
+
+**Model switching:** Deactivating a currently active AI/ML model and activating a different AI/ML model for a specific AI/ML-enabled feature.
+
+**Model update:** Process of updating the model parameters and/or model structure of a model.
+
+**Model upload:** Model transfer from UE to the network.
+
+**Network-side (AI/ML) model:** An AI/ML Model whose inference is performed entirely at the network.
+
+**Offline field data:** The data collected from field and used for offline training of the AI/ML model.
+
+**Offline training:** An AI/ML training process where the model is trained based on collected dataset, and where the trained model is later used or delivered for inference. Note: This definition only serves as a guidance. There may be cases that may not exactly conform to this definition but could still be categorized as offline training by commonly accepted conventions.
+
+**Online field data:** The data collected from field and used for online training of the AI/ML model.
+
+**Online training:** An AI/ML training process where the model being used for inference) is (typically continuously) trained in (near) real-time with the arrival of new training samples. Note: the notion of (near) real-time vs. non real-time is context-dependent and is relative to the inference time-scale. Note: This definition only serves as a guidance. There may be cases that may not exactly conform to this definition but could still be categorized as online training by commonly accepted conventions. Note: Fine-tuning/re-training may be done via online or offline training.
+
+**Reinforcement Learning (RL):** A process of training an AI/ML model from input (a.k.a. state) and a feedback signal (a.k.a. reward) resulting from the model's output (a.k.a. action) in an environment the model is interacting with.
+
+**Semi-supervised learning:** A process of training a model with a mix of labelled data and unlabelled data.
+
+**Supervised learning:** A process of training a model from input and its corresponding *labels*.
+
+**Test encoder/decoder for TE:** AI/ML model for UE encoder/gNB decoder implemented by TE.
+
+**Two-sided (AI/ML) model:** A paired AI/ML Model(s) over which joint inference is performed, where joint inference comprises AI/ML Inference whose inference is performed jointly across the UE and the network, i.e, the first part of inference is firstly performed by UE and then the remaining part is performed by gNB, or vice versa.
+
+**UE-side (AI/ML) model:** An AI/ML Model whose inference is performed entirely at the UE.
+
+**Unsupervised learning:** A process of training a model without labelled data.
+
+**Proprietary-format models:** ML models of vendor-/device-specific proprietary format, from 3GPP perspective. They are not mutually recognizable across vendors and hide model design information from other vendors when shared. Note: An example is a device-specific binary executable format.
+
+**Open-format models:** ML models of specified format that are mutually recognizable across vendors and allow interoperability, from 3GPP perspective. They are mutually recognizable between vendors and do not hide model design information from other vendors when shared.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| <symbol> | <Explanation> |
+|----------|---------------|
+|----------|---------------|
+
+## 3.3 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].
+
+| | |
+|---------|-----------------------------------------|
+| AI | Artificial Intelligence |
+| API | Application Programming Interface |
+| BM | Beam Management |
+| CDF | Cumulative Distribution Function |
+| CIR | Channel Impulse Response |
+| CNN | Convolutional Neural Network |
+| CQI | Channel Quality Indicator |
+| CSI | Channel State Information |
+| DL | Downlink |
+| DP | Delay profile |
+| EVM | Evaluation Methodology |
+| FLOP | Floating point Operation* |
+| GCS | Generalized Cosine Similarity |
+| KPI | Key Performance Indicator |
+| L1-RSRP | Layer 1 reference signal received power |
+| LCM | Life Cycle Management |
+| LLS | Link Level Simulations |
+| LMF | Location Management Function |
+| LOS | Line-of-Sight |
+
+| | |
+|-------|---------------------------------------|
+| LPP | LTE Positioning Protocol |
+| ML | Machine Learning |
+| NLOS | Non-Line-of-Sight |
+| NMSE | Normalized Mean Square Error |
+| NRPPa | NR Positioning Protocol A |
+| NW | Network |
+| PDP | Power Delay Profile |
+| PRS | Positioning Reference Signal |
+| PRU | Positioning Reference Unit |
+| RNN | Recurrent Neural Network |
+| RI | Rank Indicator |
+| RU | Resource Utilization |
+| SGCS | Squared Generalized Cosine Similarity |
+| SLS | System Level Simulations |
+| SQ | Scalar Quantization |
+| SRS | Sounding Reference Signal |
+| TRP | Transmission-Reception Point |
+| TxRU | Transceiver Unit |
+| UE | User Equipment |
+| UPT | User Perceived Throughput |
+| VQ | Vector Quantization |
+
+\* Note: Caution is advised not to confuse FLOPs (the plural form of FLOP), which a measure of model complexity, with FLOPS (FLoating point OPerations per Second), which is a measure of compute performance of a device.
+
+# 4 General AI/ML framework
+
+The purpose of this clause is to identify common notation and terminology for AI/ML related functions, procedures and interfaces.
+
+Note: The work done for FS\_NR\_ENDC\_data\_collect is considered when appropriate.
+
+## 4.1 Description of AI/ML stages
+
+In this clause, the defining stages of AI/ML related algorithms and associated complexity are characterized, namely:
+
+- Model generation, e.g., model training (including input/output, pre-/post-process, online/offline as applicable), model validation, model testing, as applicable
+- Inference operation, e.g., input/output, pre-/post-process, as applicable
+
+In addition, the treatment of dataset(s) for training, validation, testing, and inference is documented.
+
+## 4.2 Life Cycle Management
+
+In this clause, the life cycle management (LCM) of AI/ML model (e.g., model training, model deployment, model inference, model monitoring, model updating) and AI/ML functionality are characterized.
+
+The following aspects, including the definition of components (if needed) and necessity, are studied in LCM:
+
+- Data collection
+ - Note: This also includes associated assistance information, if applicable.
+- Model training
+- Functionality/model identification
+- Model delivery/transfer
+
+- Model inference operation
+- Functionality/model selection, activation, deactivation, switching, and fallback operation.
+ - Including: Decision by the network (either network initiated or UE-initiated and requested to the network), decision by the UE (event-triggered as configured by the network, UE's decision reported to the network, or UE-autonomous either with UE's decision reported to the network or without it)
+- Functionality/model monitoring
+- Model update
+- UE capability
+
+Note: Some aspects in the list may not have specification impact.
+
+### 4.2.1 LCM Flavours
+
+The LCM procedure is studied for the case that an AI/ML model has a *model ID* with associated information and/or for the case that a given *functionality* is provided by some AI/ML operations. Note: Applicability of functionality-based LCM and model-ID-based LCM is a separate discussion.
+
+From RAN1 perspective, an AI/ML model identified by a model ID may be *logical*, and how it maps to physical AI/ML model(s) may be up to implementation. When distinction is necessary for discussion purposes, companies may use the term a *logical AI/ML model* to refer to a model that is identified and assigned a model ID, and *physical AI/ML model(s)* to refer to an actual implementation of such a model.
+
+For UE-side models and UE-part of two-sided models:
+
+- For AI/ML functionality identification
+ - Legacy 3GPP framework of feature is taken as a starting point.
+ - UE indicates supported functionalities/functionality for a given sub-use-case.
+ - UE capability reporting is taken as starting point.
+- For AI/ML model identification
+ - Models are identified by model ID at the Network. UE indicates supported AI/ML models.
+
+In *functionality-based* LCM, network indicates activation/deactivation/fallback/switching of AI/ML functionality via 3GPP signalling (e.g., RRC, MAC-CE, DCI). Models may not be identified at the Network, and UE may perform model-level LCM. Whether and how much awareness/interaction NW should have about model-level LCM requires further study. For functionality identification, there may be either one or more than one Functionalities defined within an AI/ML-enabled feature, whereby AI/ML-enabled Feature refers to a Feature where AI/ML may be used. Note: UE may have one AI/ML model for the functionality, or UE may have multiple AI/ML models for the functionality.
+
+For *AI/ML functionality identification* and *functionality-based LCM* of UE-side models and/or UE-part of two-sided models, *functionality* refers to an AI/ML-enabled Feature/FG enabled by configuration(s), where configuration(s) is(are) supported based on conditions indicated by UE capability. Correspondingly, *functionality-based LCM* operates based on, at least, one configuration of AI/ML-enabled Feature/FG or specific configurations of an AI/ML-enabled Feature/FG.
+
+After *functionality identification*, necessity, mechanisms, for UE to report updates on applicable functionality(es) among functionality(es) are studied, where the applicable functionalities may be a subset of all functionalities. Applicable functionalities can be reported by the UE.
+
+In *model-ID-based* LCM, models are identified at the Network, and Network/UE may activate/deactivate/select/switch individual AI/ML models via model ID.
+
+For *AI/ML model identification* and *model-ID-based LCM* of UE-side models and/or UE-part of two-sided models, *model-ID-based LCM* operates based on identified models, where a model may be associated with specific configurations/conditions associated with UE capability of an AI/ML-enabled Feature/FG and additional conditions (e.g., scenarios, sites, and datasets) as determined/identified between UE-side and NW-side.
+
+After model identification, necessity, mechanisms, for UE to report updates on applicable UE part/UE-side model(s), are studied, where the applicable models may be a subset of all identified models. Applicable models can be reported by the UE.
+
+How to handle the impact of UE's internal conditions such as memory, battery, and other hardware limitations on functionality/model operations and AI/ML-enabled Feature is to be studied. Note: it does not preclude any existing solutions.
+
+For functionality/model-ID based LCM, once functionalities/models are identified, the same or similar procedures may be used for their activation, deactivation, switching, fallback, and monitoring.
+
+Model ID, if needed, can be used in a Functionality (defined in functionality-based LCM) for LCM operations.
+
+### 4.2.2 Model identification
+
+For *AI/ML model identification* of UE-side or UE-part of two-sided models, model identification is categorized in the following types:
+
+- Type A: Model is identified to NW (if applicable) and UE (if applicable) without over-the-air signalling
+ - The model may be assigned with a model ID during the model identification, which may be referred/used in over-the-air signalling after model identification.
+- Type B: Model is identified via over-the-air signalling,
+ - Type B1:
+ - Model identification initiated by the UE, and NW assists the remaining steps (if any) of the model identification
+ - the model may be assigned with a model ID during the model identification
+ - Type B2:
+ - Model identification initiated by the NW, and UE responds (if applicable) for the remaining steps (if any) of the model identification
+ - the model may be assigned with a model ID during the model identification
+- Note: This study does not imply that model identification is necessary.
+
+One example use case for Type B1 and B2 is model identification in model transfer from NW to UE. Another example is model identification with data collection related configuration(s) and/or indication(s) and/or dataset transfer. Note: Other example use cases are not precluded. Note: Offline model identification may be applicable for some of the example use cases.
+
+Once models are identified, at least for Type A, UE can indicate supported AI/ML model IDs for a given AI/ML-enabled Feature/FG in a UE capability report as starting point. Note: model identification using capability report is not precluded for type B1 and type B2.
+
+Model ID may or may not be globally unique, and different types of model IDs may be created for a single model for various LCM purposes. Note: Details can be studied in the WI phase.
+
+### 4.2.3 Additional conditions
+
+For an AI/ML-enabled feature/FG, *additional conditions* refer to any aspects that are assumed for the training of the model but are not a part of UE capability for the AI/ML-enabled feature/FG. It does not imply that *additional conditions* are necessarily specified. *Additional conditions* can be divided into two categories: NW-side additional conditions and UE-side additional conditions. Note: whether specification impact is needed is a separate discussion.
+
+For inference for UE-side models, to ensure consistency between training and inference regarding NW-side *additional conditions* (if identified), the following options can be taken as potential approaches (when feasible and necessary):
+
+- Model identification to achieve alignment on the NW-side additional condition between NW-side and UE-side
+
+- Model training at NW and transfer to UE, where the model has been trained under the additional condition
+- Information and/or indication on NW-side additional conditions is provided to UE
+- Consistency assisted by monitoring (by UE and/or NW, the performance of UE-side candidate models/functionalities to select a model/functionality)
+- Other approaches are not precluded
+- Note: the possibility that different approaches can achieve the same function is not denied
+
+### 4.2.4 Scenario/configuration specific Models
+
+Scenario/configuration specific (including site-specific configuration/channel conditions) models may provide performance benefits in some studied use cases (i.e., when a single model cannot generalize well to multiple scenarios/configurations/sites).
+
+- At least, when UE has limitation to store all related models, model delivery/transfer, if feasible, to UE may be beneficial, at the cost of overhead/latency associated with model delivery/transfer.
+- Note: On-device Finetuning/retraining, if feasible, of a single model may be an alternative to model delivery/transfer.
+- Note: a single model may generalize well in some studied use cases.
+- Note: Model transfer/delivery to UE may also face challenges, e.g., proprietary issues /burdens in some scenarios
+
+Various approaches for achieving good performance across different scenarios/configurations/sites are studied, including
+
+- *Model generalization*, i.e., using one model that is generalizable to different scenarios/configurations/sites
+- *Model switching*, i.e., switching among a group of models where each model is for a particular scenario/configuration/site
+ - Models in a group of models may have varying model structures, share a common model structure, or partially share a common sub-structure. Models in a group of models may have different input/output format and/or different pre-/post-processing.
+- *Model update*, i.e., using one model whose parameters are flexibly updated as the scenario/configuration/site that the device experiences changes over time. Fine-tuning is one example.
+
+### 4.2.5 Data collection
+
+Data collection may be performed for different purposes in LCM, e.g., model training, model inference, model monitoring, model selection, model update, etc. each may be done with different requirements and potential specification impact.
+
+For all types of offline model training (i.e., UE- /NW-/ two-sided model training), there is no latency requirement for data collection. For model inference, when required data comes from other entities, there is a latency requirement for data collection. For (real-time) performance monitoring, when required monitoring data (e.g., performance metric) comes from other entities, there is a latency requirement for data collection.
+
+At least for the use cases studied in this study item, it is assumed that the analysis/selection of the data collection frameworks should focus on the RRC\_CONNECTED state (for both data generation and reporting). Analysis and potential enhancement of the non-connected state can be revisited when needed. Note that existing specification supports DL PRS measurement and UE positioning in both RRC\_CONNECTED and RRC\_INACTIVE state.
+
+At least the following aspects, if applicable, are considered along with the corresponding specification impact:
+
+- Measurement configuration and reporting
+- Contents, type and format of data including:
+ - Data related to model input
+
+- Data related to ground-truth
+- Quality of the data
+- Other information
+- Signalling of assistance information for categorizing the data
+- Note: The study should consider the feasibility of disclosure of proprietary information
+- Signalling for data collection procedure
+
+## 4.3 Collaboration levels
+
+In this clause, various levels of collaboration between UE and Network are identified as found pertinent to the selected use cases, e.g.,
+
+- No collaboration: implementation-based only AI/ML algorithms without information exchange for comparison purposes
+- Various levels of UE/Network collaboration targeting at separate or joint ML operation
+
+The following Network-UE collaboration levels are considered as one aspect for defining collaboration levels
+
+1. **Level x:** No collaboration.
+2. **Level y:** Signalling-based collaboration without model transfer. Note: this level includes cases without model delivery.
+3. **Level z:** Signalling-based collaboration with model transfer.
+
+Level x/y boundary is understood such as Level x is implementation-based AI/ML operation without any dedicated AI/ML-specific enhancement (e.g., LCM related signalling, RS) collaboration between network and UE. (Note: The AI/ML operation may rely on future specification not related to AI/ML collaboration. The AI/ML approaches can be used as baseline for performance evaluation for future releases.)
+
+Level y/z boundary is defined based on whether model delivery over the air interface is done in a non-transparent manner to 3GPP signalling. Note: procedures other than model transfer/delivery are decoupled with collaboration Level y-z.
+
+Table 4.3-1 introduces different options for model delivery/transfer to UE, training location, and model delivery/transfer format combinations for UE-side models and UE-part of two-sided models:
+
+**Table 4.3-1: Model delivery/transfer cases**
+
+| Case | Model delivery/transfer | Model storage location | Training location |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------------------------|
+| <b>y</b> | model delivery (if needed) over-the-top. | Outside 3GPP Network | UE-side / NW-side / neutral site |
+| <b>z1</b> | model transfer in proprietary format. | 3GPP Network | UE-side / neutral site |
+| <b>z2</b> | model transfer in proprietary format. | 3GPP Network | NW-side |
+| <b>z3</b> | model transfer in open format. | 3GPP Network | UE-side / neutral site |
+| <b>z4</b> | model transfer in open format of a <i>known model structure</i> at UE, i.e., an exact model structure as has been previously identified between NW and UE and for which the UE has explicitly indicated its support. | 3GPP Network | NW-side |
+| <b>z5</b> | model transfer in open format of an <i>unknown model structure</i> at UE, i.e., any other model structure not covered in z4, including any model structure that is only partially known. | 3GPP Network | NW-side |
+| Note: | The definition of various Cases is only for the purpose of facilitating discussion and does not imply applicability, feasibility, entity mapping, architecture, signalling nor any prioritization. | | |
+
+When a model of a known structure at UE (e.g., Case z4) is transferred from the Network, the new model being identified (e.g., via Type B2) has the same structure as a previously identified model at the Network and UE.
+
+For model delivery/transfer to UE (for UE-side models and UE-part of two-sided models):
+
+- Model delivery/transfer to UE, if feasible, may be beneficial to handle scenario/configuration specific (including site-specific configuration/channel conditions) models (i.e., when a single model cannot generalize well to multiple scenarios/configurations/sites), to reduce the device storage requirement.
+- Model delivery/transfer to UE after offline compiling and/or testing may be friendlier from UE's implementation point of view compared to the case without offline compiling and/or testing. On the other hand, the case without offline compiling and/or testing (that can update parameter with known model structure), may have benefit at least in terms of shorter model parameter update timescale.
+- Model transfer/delivery of an unknown structure at UE has more challenges related to feasibility (e.g. UE implementation feasibility) compared to delivery/transfer of a known structure at UE.
+- For model trained at network side, Case y (w/ NW-side training) and Case z2 may incur the burden of offline cross-vendor collaboration such as sending a model to the UE-side and/or compiling a model.
+- For model trained at UE side/neutral site, Case z1 and Case z3 may incur the burden of offline cross-vendor collaboration to send the trained model from the UE-side to the network, compared to Case y (w/ UE-side training) which does not have such burden.
+- Model storage at the 3GPP network, compared to storing the model outside the 3GPP network, may come with 3GPP network side burden on model maintenance/storage.
+- Proprietary design disclosure concern may arise from model training and/or model storage at the network side compared to other cases (such as case y with UE side training) which does not have such issue.
+
+## 4.4 Functional framework details
+
+This section introduces the functional framework for AI/ML for NR air interface illustrated in Figure 4.4-1. The aim of this framework is to cover a general functional architecture addressing both model-ID-based LCM and functionality-based LCM, introduced in clause 4.2. Therefore, some of the functions or data/information/instruction flows (i.e., the arrows) shown in the Figure 4.4-1 might not always be relevant for a given LCM approach. As an illustrative example, consider a scenario where the network performs functionality-based LCM and where models are not identified in the network, while the UE concurrently performs model-level management (e.g., model selection/switching/(de)activation, etc...). In this hypothetical case, the "Model Training" or "Model Storage" functions with their respective procedures, may be regarded as irrelevant from the network's perspective.
+
+In clause 7, the functions and data/information/instruction flows (i.e., the arrows) depicted in Figure 4.4-1 are analysed for any standardization impact and its implications.
+
+Note: The functional framework and high-level procedures defined in this TR should not prevent from "thinking beyond" them during a normative phase if any use case requires so.
+
+
+
+```
+
+graph TD
+ DC[Data Collection] -- "Training Data" --> MT[Model Training]
+ DC -- "Monitoring Data" --> M[Management]
+ DC -- "Inference Data" --> I[Inference]
+ MT -- "Trained/Updated Model" --> MS[Model Storage]
+ M -- "Performance Feedback / Retraining Request" --> MT
+ M -- "Management Instruction" --> I
+ I -- "Inference Output" --> M
+ MS -- "Model Transfer/Delivery Request" --> M
+ MS -- "Model Transfer/Delivery" --> I
+
+```
+
+Figure 4.4-1: Functional framework for AI/ML for NR Air Interface. The diagram shows four main functional blocks: Data Collection, Model Training, Management, and Inference, along with Model Storage. Data Collection provides Training Data, Monitoring Data, and Inference Data to the other blocks. Model Training provides a Trained/Updated Model to Model Storage. Management provides Performance Feedback / Retraining Request to Model Training and Management Instruction to Inference. Inference provides Inference Output to Management. Model Storage provides Model Transfer/Delivery Request to Management and Model Transfer/Delivery to Inference.
+
+Figure 4.4-1: Functional framework for AI/ML for NR Air Interface
+
+As seen in Figure 4.4-1, the general framework consists of the following:
+
+- Data Collection is a function that provides input data to the Model Training, Management, and Inference functions.
+- Training Data: Data needed as input for the AI/ML Model Training function.
+- Monitoring Data: Data needed as input for the Management of AI/ML models or AI/ML functionalities.
+- Inference Data: Data needed as input for the AI/ML Inference function.
+- Model Training is a function that performs AI/ML model training, validation, and testing which may generate model performance metrics which can be used as part of the model testing procedure. The Model Training function is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Training Data delivered by a Data Collection function, if required.
+- Trained/Updated Model: In case of having a Model Storage function, this is used to deliver trained, validated, and tested AI/ML models to the Model Storage function, or to deliver an updated version of a model to the Model Storage function.
+- Management is a function that oversees the operation (e.g., selection/(de)activation/switching/fallback) and monitoring (e.g., performance) of AI/ML models or AI/ML functionalities. This function is also responsible for making decisions to ensure the proper inference operation based on data received from the Data Collection function and the Inference function.
+- Management Instruction: Information needed as input to manage the Inference function. Concerning information may include selection/(de)activation/switching of AI/ML models or AI/ML-based functionalities, fallback to non-AI/ML operation (i.e., not relying on inference process), etc...
+- Model Transfer/Delivery Request: Used to request model(s) to the Model Storage function.
+- Performance Feedback / Retraining Request: Information needed as input for the Model Training function, e.g., for model (re)training or updating purposes.
+- Inference is a function that provides outputs from the process of applying AI/ML models or AI/ML functionalities, using the data that is provided by the Data Collection function (i.e., Inference Data) as an input. The Inference function is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Inference Data delivered by a Data Collection function, if required.
+- Inference Output: Data used by the Management function to monitor the performance of AI/ML models or AI/ML functionalities.
+- Model Storage is a function responsible for storing trained/updated models that can be used to perform the Inference function.
+- Note: The Model Storage function in Figure 4.4-1 is only intended as a reference point (if any) when applicable for protocol terminations, model transfer/delivery, and related processes. It should be stressed that its purpose does not encompass restricting the actual storage locations of models. Therefore, the specification impact of all data/information/instruction flows (i.e., the arrows in Figure 4.4-1) to/from this function should be studied case by case.
+- Model Transfer/Delivery: Used to deliver an AI/ML model to the Inference function.
+
+# --- 5 Use cases
+
+Initial set of use cases includes:
+
+- CSI feedback enhancement, e.g., overhead reduction, improved accuracy, prediction [RAN1]
+- Beam management, e.g., beam prediction in time, and/or spatial domain for overhead and latency reduction, beam selection accuracy improvement [RAN1]
+- Positioning accuracy enhancements for different scenarios including, e.g., those with heavy NLOS conditions [RAN1]
+
+- The AI/ML approaches for the selected sub use cases need to be diverse enough to support various requirements on the gNB-UE collaboration levels
+
+Note: the selection of use cases for this study solely targets the formulation of a framework to apply AI/ML to the air-interface for these and other use cases. The selection itself does not intend to provide any indication of the prospects of any future normative project.
+
+## 5.1 CSI feedback enhancement
+
+### *Finalization of representative sub-use cases:*
+
+The following are selected as representative sub-use cases:
+
+- Spatial-frequency domain CSI compression using two-sided AI model. Note: All pre-processing/post-processing, quantization/de-quantization are within the scope of the sub use case.
+- The study of AI/ML based CSI compression should be based on the legacy CSI feedback signalling framework.
+- Time domain CSI prediction using UE-side model.
+
+For CSI compression using two-sided model use case, considered AI/ML model training collaborations include:
+
+- Type 1: Joint training of the two-sided model at a single side/entity, e.g., UE-sided or Network-sided.
+- Type 2: Joint training of the two-sided model at network side and UE side, respectively.
+- Type 3: Separate training at network side and UE side, where the UE-side CSI generation part and the NW-side CSI reconstruction part are trained by UE side and network side, respectively.
+- Note: Joint training means the generation model and reconstruction model should be trained in the same loop for forward propagation and backward propagation. Joint training could be done both at single node or across multiple nodes (e.g., through gradient exchange between nodes).
+- Note: Separate training includes sequential training starting with UE side training, or sequential training starting with NW side training
+- Note: training collaboration Type 2 over the air interface for model training (not including model update) is concluded to be deprioritized in Rel-18 SI.
+
+For Type 2 (Joint training of the two-sided model at network side and UE side, respectively), note that joint training includes both simultaneous training and sequential training, in which the pros and cons could be discussed separately. Further, note that Type 2 sequential training starts with NW side training.
+
+In CSI compression using two-sided model use case, for discussion of training collaboration Type 1, separate columns are shown for both known model structure, and unknown model structure separately for NW-sided and UE-sided, respectively. Table 5.1-1 captures the pros/cons of training collaboration Type 1 for CSI compression using two-sided model use case.
+
+**Table 5.1-1: Pros and Cons of training collaboration Type 1**
+
+| Characteristics \ Training Types | Type 1: NW side | | Type 1: UE side | |
+|------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|
+| | Unknown model structure at UE | Known model structure at UE | Unknown model structure at UE | Known model structure at UE |
+| Whether model can be kept proprietary | No | No | No | No |
+| Whether require privacy-sensitive dataset sharing | No (Note 1) | No (Note 1) | No (Note 1) | No (Note 1) |
+| Flexibility to support cell/site/scenario/configuration specific model | Flexible except for UE defined scenarios.<br><br>Not flexible for | Flexible except for UE defined scenarios.<br><br>Not flexible for | Flexible except for NW defined scenarios.<br><br>Not flexible for | Flexible except for NW defined scenarios.<br><br>Not flexible for |
+
+| | | | | |
+|---------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| | UE defined scenarios unless UE assistance information is supported and available.<br>(Note 6) | UE defined scenarios unless UE assistance information is supported and available.<br>(Note 6) | NW defined scenarios unless NW assistance information is supported and available.<br>(Note 6) | NW defined scenarios unless NW assistance information is supported and available.<br>(Note 6) |
+| Whether gNB/device specific optimization is allowed | gNB: Yes<br>UE: No | gNB: Yes<br>UE: less flexible compared to UE side | gNB: No<br>UE: Yes | gNB: less flexible compared to NW side<br>UE: Yes |
+| Model update flexibility after deployment | Flexible only if UE supports the new structure | Flexible for parameter update | Flexible, less flexible than Type 1 NW side | Flexible for parameter update, less flexible than Type 1 NW side |
+| Feasibility of allowing UE side and NW side to develop/update models separately | gNB: Feasible<br>UE: Not feasible due to Type 1 definition. | gNB: Feasible with restriction for CSI reconstruction model.<br>UE: Not feasible due to Type 1 definition. | gNB: Not feasible due to Type 1 definition.<br>UE: Feasible. | gNB: Not feasible due to Type 1 definition.<br>UE: Feasible with restriction for CSI generation model. |
+| Whether gNB can maintain/store a single/unified CSI reconstruction model over different UEs (Note 2) | Yes | Yes.<br>Performance refers to observations in "1 NW part model to M>1 UE part models" of clause 6.2.2.4 (Note 4) | No | No |
+| Whether UE device can maintain/store a single/unified CSI generation model over different NW vendors (Note 3) | No | No | Yes | Yes.<br>Performance refers to observations in "1 UE part model to N>1 NW part models" of clause 6.2.2.4 (Note 4) |
+| Extendibility: to train new UE-side model compatible with NW-side model in use; (Note 5) | Yes | Yes | No consensus | No consensus |
+| Extendibility: To train new NW-side model compatible with UE-side model in use; (Note 5) | No consensus | No consensus | Yes | Yes |
+| Whether training data distribution can match the inference device | Limited | Limited | Yes | Yes |
+| Software/hardware compatibility (Whether device capability can be considered for model development) | No for UE | Yes | No for NW | Yes |
+| Model performance | Performance refers to clause 6.2.2 | Performance refers to clause 6.2.2 | Performance refers to clause 6.2.2 | Performance refers to clause 6.2.2 |
+
+| | |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Note 1: | Assume precoding matrix is not privacy sensitive data. FFS: other information such as channel matrix and assisted information. |
+| Note 2: | Whether gNB/UE needs to maintain/store multiple CSI generation/reconstruction models respectively, is not discussed. |
+| Note 3: | For model inference, UE does not need to use multiple models from different NW vendors per cell. |
+| Note 4: | One to many joint trainings is assumed. |
+| Note 5: | The performance of the new model is similar to the performance of sequential training when training Type 1 support freezing a part of two sided model. |
+| Note 6: | For this table, NW defined scenarios are scenarios with NW defined dataset categorization. UE defined scenarios are scenarios with UE defined dataset categorization. |
+
+Table 5.1-2 captures the pros/cons of training collaboration Type 2 and Type 3 for CSI compression using two-sided model use case.
+
+**Table 5.1-2: Pros and Cons of training collaboration Type 2 and Type 3**
+
+| Characteristics \ Training Types | Type 2 | | Type 3 | |
+|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | Simultaneous | Sequential | NW first | UE first |
+| Whether model can be kept proprietary | Yes (Note 1) | Yes (Note 1) | Yes (Note 1) | Yes (Note 1) |
+| Whether requires privacy-sensitive dataset sharing | No (Note 2) | No (Note 2) | No (Note 2) | No (Note 2) |
+| Flexibility to support cell/site/scenario/configuration specific model | No consensus | No consensus | [Semi] flexible except for UE defined scenarios. (Note 3)<br><br>[Semi] flexible for UE defined scenarios if UE assistance information is supported and available. | [Semi] flexible except for NW defined scenarios (Note 3).<br><br>[Semi] flexible for NW defined scenarios if NW assistance information is supported and available. |
+| Whether gNB/device specific optimization is allowed | Yes | Yes | Yes | Yes |
+| Model update flexibility after deployment (Note 4) | Not flexible | No consensus | Semi-flexible | Semi-flexible |
+| Feasibility of allowing UE side and NW side to develop/update models separately | Infeasible | No consensus | Feasible | Feasible |
+| Whether gNB can maintain/store a single/unified model over different UE vendors (Note 5) | Yes. Performance refers to observations in "1 NW part model to M>1 UE part models" and "1 UE part model to N>1 NW part models" of clause 6.2.2.4. | Yes. Performance refers to observations in "1 NW part model to M>1 UE part models" of clause 6.2.2.4. | Yes. Performance refers to observations in "NW first training, 1 NW part model to 1 UE part model, same backbone" and "NW first training, 1 NW part model to 1 UE part model, different backbones" of clause 6.2.2.5. | Yes. Performance refers to observations in "UE first training, M>1 UE part models to 1 NW part model" of clause 6.2.2.5. |
+| Whether UE device can maintain/store a single/unified CSI generation model over different NW | Yes. Performance refers to | Yes. Performance refers to | Yes. Performance refers to | Yes. Performance refers to |
+
+| | | | | |
+|-----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| vendors (Note 6) | observations in "1 NW part model to M>1 UE part models" and "1 UE part model to N>1 NW part models" of clause 6.2.2.4. | observations in "1 NW part model to M>1 UE part models" of clause 6.2.2.4. | observations in "NW first training, 1 UE part model to N>1 NW part models" of clause 6.2.2.5. | observations in "UE first training, 1 NW part model to 1 UE part model, same backbone". And "UE first training, 1 NW part model to 1 UE part model, different backbones" of clause 6.2.2.5. |
+| Extendibility: to train new UE-side model compatible with NW-side model in use; | Not support | Support | Support | No consensus |
+| Extendibility: To train new NW-side model compatible with UE-side model in use | Not support | Not support | No consensus | Support |
+| Whether training data distribution can match the inference device | No consensus | Yes for UE-part model, limited for NW-part model | Limited | Yes |
+| Software/hardware compatibility (Whether device capability can be considered for model development) | Compatible | Compatible | Compatible | Compatible |
+| Model performance | Performance refers to clause 6.2.2 | Performance refers to clause 6.2.2 | Performance refers to clause 6.2.2 | Performance refers to clause 6.2.2 |
+| Note 1: | Assume information on model structure disclosed in training collaboration does not reveal proprietary information. | | | |
+| Note 2: | Assume precoding matrix is not privacy sensitive data. FFS: other information such as channel matrix and assisted information. | | | |
+| Note 3: | For this table, NW defined scenarios are scenarios with NW defined dataset categorization. UE defined scenarios are scenarios with UE defined dataset categorization. [Semi] means no consensus for including "semi". | | | |
+| Note 4: | Flexibility after deployment is evaluated by the amount of offline cross-vendor co-engineering effort. Flexible indicates minimum additional co-engineering between vendors, semi-flexible indicates additional co-engineering effort between vendors. | | | |
+| Note 5: | Whether gNB/UE needs to maintain/store multiple CSI generation/reconstruction models respectively, is not discussed. | | | |
+| Note 6: | For model inference, UE does not need to use multiple models from different NW vendors per cell. | | | |
+
+For CSI compression use case:
+
+- For *model training*, training data can be generated by UE/gNB
+- For NW-part of two-sided *model inference*, input data can be generated by UE and terminated at gNB.
+- For UE-part of two-sided *model inference*, input data is internally available at UE.
+- For *performance monitoring* at the NW side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) can be generated by UE and terminated at gNB
+
+In CSI compression using two-sided model use case, in order to select a CSI generation model compatible with the CSI reconstruction model used by the gNB, the following aspect has been proposed:
+
+- Pairing information can be established based on model identification
+
+For CSI prediction use cases:
+
+- For *model training*, training data can be generated by UE.
+- For UE-side *model inference*, input data is internally available at UE.
+
+- For *performance monitoring* at the NW side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) can be generated by UE and terminated at gNB.
+
+## 5.2 Beam management
+
+### *Finalization of representative sub-use cases:*
+
+The following are selected as representative sub-use cases:
+
+- BM-Case1: Spatial-domain Downlink beam prediction for Set A of beams based on measurement results of Set B of beams
+ - Consider: Alt. 1): AI/ML model training and inference at NW side. Alt. 2): AI/ML model training and inference at UE side.
+ - Consider: Alt. i): Set A and Set B are different (Set B is NOT a subset of Set A). Alt. ii): Set B is a subset of Set A. Note: Set A is for DL beam prediction. The codebook construction of Set A and Set B can be clarified by companies.
+ - AI/ML model input consider: Alt 1): Only L1-RSRP measurement based on Set B; Alt.2): L1-RSRP measurement based on Set B and assistance information; Alt. 3): CIR based on Set B; Alt. 4): L1-RSRP measurement based on Set B and the corresponding DL Tx and/or Rx beam ID.
+- BM-Case2: Temporal Downlink beam prediction for Set A of beams based on the historic measurement results of Set B of beams
+ - Consider: Alt. 1): AI/ML model training and inference at NW side. Alt. 2): AI/ML model training and inference at UE side.
+ - Consider: Alt. i): Set A and Set B are different (Set B is NOT a subset of Set A). Alt. ii): Set B is a subset of Set A (Set A and Set B are not the same). Alt. iii): Set A and Set B are the same.
+ - AI/ML model input consider: measurement results of K ( $K \geq 1$ ) latest measurement instances with the following alternatives: Alt. 1): Only L1-RSRP measurement based on Set B; Alt 2): L1-RSRP measurement based on Set B and assistance information; Alt. 3): L1-RSRP measurement based on Set B and the corresponding DL Tx and/or Rx beam ID.
+ - F predictions for F future time instances can be obtained based on the output of AI/ML model, where each prediction is for each time instance. At least $F=1$ .
+
+Set B is a set of beams whose measurements are taken as inputs of the AI/ML model.
+
+Note: Beams in Set A and Set B can be in the same Frequency Range.
+
+For both sub-use cases, the following alternatives are studied for the predicted beams:
+
+- Alt.1: DL Tx beam prediction
+- Alt.2: DL Rx beam prediction (deprioritized)
+- Alt.3: Beam pair prediction (a beam pair consists of a DL Tx beam and a corresponding DL Rx beam)
+
+Note: DL Rx beam prediction may or may not have spec impact.
+
+The following alternatives according to AI/ML model output are considered:
+
+- Alt.1: Tx and/or Rx Beam ID(s) and/or the predicted L1-RSRP of the N predicted DL Tx and/or Rx beams
+ - e.g., N predicted beams can be the Top-N predicted beams
+- Alt.2: Tx and/or Rx Beam ID(s) of the N predicted DL Tx and/or Rx beams and other information
+ - e.g., N predicted beams can be the Top-N predicted beams
+- Alt.3: Tx and/or Rx Beam angle(s) and/or the predicted L1-RSRP of the N predicted DL Tx and/or Rx beams
+
+- e.g., N predicted beams can be the Top-N predicted beams
+
+Notes: It is up to companies to provide other alternative(s). Beam ID is only used for discussion purposes. All the outputs are "nominal" and only for discussion purpose. The value of N is up to each company. All of the outputs in the above alternatives may vary based on whether the AI/ML model inference is at UE side or gNB side. The Top-N beam IDs might have been derived via post-processing of the ML-model output.
+
+For BM-Case1 and BM-Case2 with a UE-side AI/ML model, the necessity and potential BM-specific conditions/additional conditions for functionality(ies) and/or model(s) are considered at least from the following aspects:
+
+- information regarding model inference
+- Set A / Set B configuration
+- performance monitoring
+- data collection
+- assistance information
+
+For beam management use cases:
+
+- For *model training*, training data can be generated by UE/gNB.
+- For NW-side *model inference*, input data can be generated by UE and terminated at gNB.
+- For UE-side *model inference*, input data is internally available at UE.
+- For *performance monitoring* at the NW side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) can be generated by UE and terminated at gNB.
+
+## 5.3 Positioning accuracy enhancements
+
+**Finalization of representative sub-use cases:**
+
+The following are selected as representative sub-use cases:
+
+- Direct AI/ML positioning:
+ - AI/ML model output: UE location
+ - e.g., fingerprinting based on channel observation as the input of AI/ML model
+- AI/ML assisted positioning:
+ - AI/ML model output: new measurement and/or enhancement of existing measurement
+ - e.g., LOS/NLOS identification, timing and/or angle of measurement, likelihood of measurement
+
+More specifically, the following Cases are considered for the study:
+
+- Case 1: UE-based positioning with UE-side model, direct AI/ML or AI/ML assisted positioning
+- Case 2a: UE-assisted/LMF-based positioning with UE-side model, AI/ML assisted positioning
+- Case 2b: UE-assisted/LMF-based positioning with LMF-side model, direct AI/ML positioning
+- Case 3a: NG-RAN node assisted positioning with gNB-side model, AI/ML assisted positioning
+- Case 3b: NG-RAN node assisted positioning with LMF-side model, direct AI/ML positioning
+
+One-sided model whose inference is performed entirely at the UE or at the network is prioritized in Rel-18 SI.
+
+For all five positioning cases (Case 1/2a/2b/3a/3b), RAN1 has not considered prioritization.
+
+For positioning enhancement use case:
+
+- For *model training*, training data can be generated by UE/PRU/gNB/LMF.
+- For LMF-side *model inference* (Case 2b, Case 3b), input data can be generated by UE/gNB and terminated at LMF.
+- For gNB-side *model inference* (Case 3a), input data is internally available at gNB.
+- For UE-side *model inference* (Case 1, Case 2a), input data is internally available at UE.
+- For *performance monitoring* at the LMF side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) can be generated by UE/gNB and terminated at LMF.
+- For *performance monitoring* at the gNB side, calculated performance metrics (if needed) or data needed for performance metric calculation (if needed) can be generated by at least gNB.
+
+# --- 6 Evaluations
+
+In this clause, performance benefits of AI/ML based algorithms for the agreed use cases in the final representative set are evaluated.
+
+The evaluation methodology is based on statistical models (from TR 38.901 and TR 38.857 for positioning), for link and system level simulations.
+
+- Extensions of 3GPP evaluation methodology for better suitability to AI/ML based techniques should be considered as needed.
+- Whether field data are optionally needed to further assess the performance and robustness in real-world environments should be discussed as part of the study.
+- Need for common assumptions in dataset construction for training, validation and test for the selected use cases.
+- Consider adequate model training strategy, collaboration levels and associated implications
+- Consider agreed-upon base AI model(s) for calibration
+- AI model description and training methodology used for evaluation should be reported for information and cross-checking purposes
+
+Common KPIs and corresponding requirements for the AI/ML operations are to be determined. Also, use-case specific KPIs and benchmarks of the selected use-cases are to be determined.
+
+- Performance, inference latency and computational complexity of AI/ML based algorithms should be compared to that of a state-of-the-art baseline
+- Overhead, power consumption (including computational), memory storage, and hardware requirements (including for given processing delays) associated with enabling respective AI/ML scheme, as well as generalization capability should be considered.
+
+## 6.1 Common evaluation methodology and KPIs
+
+3GPP channel models (TR 38.901) are used as the baseline for evaluations. Note: additional results based on dataset other than that generated by 3GPP channel models are allowed.
+
+**Common KPIs** (if applicable):
+
+- Performance
+ - Intermediate KPIs
+ - Link and system level performance
+
+- Generalization performance
+- Over-the-air Overhead
+ - Overhead of assistance information
+ - Overhead of data collection
+ - Overhead of model delivery/transfer
+ - Overhead of other AI/ML-related signalling
+- Inference complexity, including complexity for pre- and post-processing
+ - Computational complexity of model inference: TOPs, FLOPs, MACs
+ - there may be a disconnect between the actual complexity and the complexity evaluated as captured in clause 6 using these KPIs due to the platform-dependency and implementation (hardware and software) optimization solutions
+ - Computational complexity for pre- and post-processing
+ - Model complexity: e.g., the number of parameters and/or size (e.g., Mbyte)
+ - Complexity shall be reported in terms of "*number of real-value model parameters*" and "*number of real-value operations*" regardless of underlying model arithmetic
+- Training complexity
+- LCM related complexity and storage overhead
+ - Storage/computation for training data collection
+ - Storage/computation for training and model update
+ - Storage/computation for model monitoring
+ - Storage/computation for other LCM procedures, e.g., model activation, deactivation, selection, switching, fallback operation
+
+For evaluation of performance monitoring approaches, the following model monitoring KPIs are considered as general guidance:
+
+- Accuracy and relevance (i.e., how well does the given monitoring metric/methods reflect the model and system performance)
+- Overhead (e.g., signalling overhead associated with model monitoring)
+- Complexity (e.g., computation and memory cost for model monitoring)
+- Latency (i.e., timeliness of monitoring result, from model failure to action, given the purpose of model monitoring)
+
+Note: Other KPIs are not precluded. Relevant KPIs may vary across different model monitoring approaches.
+
+## 6.2 CSI feedback enhancement
+
+### 6.2.1 Evaluation assumptions, methodology and KPIs
+
+For the performance evaluation of the AI/ML based CSI feedback enhancement, *system level simulation* approach is adopted as baseline. *Link level simulations* are optionally adopted.
+
+For calibration purposes on the dataset and/or AI/ML model across companies, companies were encouraged to align the parameters (e.g., for scenarios/channels) for generating the dataset in the simulation as a starting point.
+
+Performing intermediate evaluations on AI/ML model performance can be considered to derive the intermediate KPI(s) (e.g., accuracy of AI/ML output CSI) for the purpose of AI/ML solution comparison. If realistic DL channel estimation is considered, CSI accuracy is calculated using the target CSI from ideal channel and the output CSI from the realistic channel estimation. The target CSI from ideal channel equally applies to AI/ML based CSI feedback enhancement, and the baseline codebook.
+
+#### **KPIs and Evaluation metrics:**
+
+- Capability/complexity: Floating point operations (FLOPs), AI/ML memory storage in terms of AI/ML model size and number of AI/ML parameters reported by companies who may select either or both
+- Reported separately for the CSI generation part and the CSI reconstruction part (for CSI compression sub-use case)
+- When reporting the computational complexity including the pre-processing and post-processing, the complexity metric of FLOPs may be reported separately for the AI/ML model and the pre/post processing. While reporting the FLOPs of pre-processing and post-processing the following boundaries are considered:
+ - Estimated raw channel matrix per each frequency unit as an input for pre-processing of the CSI generation part.
+ - Precoding vectors per each frequency unit as an output of post-processing of the CSI reconstruction part.
+- CSI compression: Intermediate KPIs: SGCS and/or NMSE to evaluate the accuracy of the AI/ML output CSI
+- For rank>1 cases, SGCS calculation/extension methods are to be reported:
+ - SGCS separately calculated for each layer (e.g., for K layers, K SGCS values are derived respectively, and comparison is performed per layer). Companies to ensure the correct calculation of SGCS and to avoid disorder issue of the output eigenvectors. Note: Eventual KPI can still be used to compare the performance.
+- The granularity of the frequency unit for averaging operation is assumed to be:
+ - For 15kHz SCS: For 10MHz bandwidth: 4 RBs; for 20MHz bandwidth: 8 RBs
+ - For 30kHz SCS: For 10MHz bandwidth: 2 RBs; for 20MHz bandwidth: 4 RBs
+ - Other frequency unit granularities not precluded.
+- CSI compression: Intermediate KPI: model monitoring mechanism is considered as:
+ - Step 1: Generate test dataset including K test samples.
+ - Step 2: For each of the K test samples, a bias factor of monitored intermediate KPI ( $KPI_{Diff}$ ) is calculated as a function of $KPI_{Diff} = f(KPI_{Actual}, KPI_{Genie})$ , where $KPI_{Actual}$ is the actual intermediate KPI, and $KPI_{Genie}$ is the genie-aided intermediate KPI.
+ - $KPI_{Diff}$ is considered for:
+ - Case 1: NW side monitoring of intermediate KPI, where the monitoring accuracy is evaluated for a given ground-truth CSI format (e.g., quantized ground-truth CSI with 8 bits scalar, R16 eType II-like method, etc.) or SRS measurements, where
+ - $KPI_{Actual}$ is calculated with the output CSI at the NW side and the given ground-truth CSI format or SRS measurements.
+ - $KPI_{Genie}$ is calculated with output CSI (as for $KPI_{Actual}$ ) and the ground-truth CSI of Float32
+ - Note: if Float32 is used for $KPI_{Actual}$ , the monitoring accuracy is 100% if $KPI_{Actual}$ and $KPI_{Genie}$ are based on the same CSI sample.
+ - Case 2: UE side monitoring of intermediate KPI with a proxy model, where the monitoring accuracy is evaluated for the output of the proxy model at UE:
+ - Case 2-1: the proxy model is a proxy CSI reconstruction part, and $KPI_{Actual}$ is calculated based on the inference output of the proxy CSI reconstruction part at UE and the ground-truth CSI. Note: if
+
+the proxy CSI reconstruction model is the same as the actual CSI reconstruction model at the NW, the monitoring accuracy is 100%.
+
+- Case 2-2: the proxy model directly outputs intermediate KPI ( $KPI_{Actual}$ )
+- $KPI_{Genie}$ is calculated with the output CSI at the NW side and the same ground-truth CSI.
+- $KPI_{Diff} = f( KPI_{Actual} , KPI_{Genie} )$ can take the following forms:
+ - Option 1 (baseline for calibration): Gap between $KPI_{Actual}$ and $KPI_{Genie}$ , i.e. $KPI_{Diff} = (KPI_{Actual} - KPI_{Genie})$ ; Monitoring accuracy is the percentage of samples for which $|KPI_{Diff}| < KPI_{th\ 1}$ , where $KPI_{th\ 1}$ is a threshold of the intermediate KPI gap which can take the following values: 0.02, 0.05 and 0.1.
+ - Option 2 (optional and up to companies to report): Binary state where $KPI_{Actual}$ and $KPI_{Genie}$ have different relationships to their threshold(s), i.e., $KPI_{Diff} = (KPI_{Actual} > KPI_{th\ 2}, KPI_{Genie} < KPI_{th\ 3})$ OR $(KPI_{Actual} < KPI_{th\ 2}, KPI_{Genie} > KPI_{th\ 3})$ , where $KPI_{th\ 2}$ is considered to be the same as $KPI_{th\ 3}$ . Monitoring accuracy is the percentage of samples for which $KPI_{Diff} = 0$ .
+- Step 3: Calculate the statistical result of the $KPI_{Diff}$ over K test samples which represents the monitoring accuracy performance.
+- Note: $KPI_{Genie}$ is introduced for the evaluation and comparison purpose; it may not be available in the real network.
+- Note: the complexity, overhead and latency of the monitoring scheme are to be reported.
+- CSI prediction: Intermediate KPIs: calculated for each predicted instance if AI/ML model outputs multiple predicted instances
+ - If collaboration level x is reported as the benchmark, the EVM to distinguish level x and level y/z based AI/ML CSI prediction is considered from the generalization aspect, e.g., collaboration level y/z based CSI prediction is modelled as the fine-tuning case or generalization Case 1, while collaboration level x based CSI prediction is modelled as generalization Case 2 or Case 3.
+- Throughput including: average UPT, 5%-ile UE throughput, and CDF of UPT
+
+#### ***Model generalization:***
+
+The following cases are considered for verifying the generalization performance of an AI/ML model over *various scenarios/configurations*:
+
+- Case 1: The AI/ML model is trained based on training dataset from one Scenario#B/Configuration#B, and then the AI/ML model performs inference/test on a dataset from the same Scenario#B/Configuration#B
+- Case 2: The AI/ML model is trained based on training dataset from a different data set than Scenario#B/Configuration#B, e.g., Scenario#A/Configuration#A, Scenario#B/Configuration#A, Scenario#A/Configuration#B, and then the AI/ML model performs inference/test on Scenario#B/Configuration#B.
+- Case 3: The AI/ML model is trained based on training dataset constructed by mixing datasets from multiple scenarios/configurations including Scenario#B/Configuration#B and a different dataset than Scenario#B/Configuration#B, e.g., Scenario#A/Configuration#A, Scenario#B/Configuration#A, Scenario#A/Configuration#B, and then the AI/ML model performs inference/test on a dataset from a single Scenario/Configuration from Scenario#B/Configuration#B.
+ - Note: Companies to report the ratio for dataset mixing
+ - Note: number of the multiple scenarios/configurations can be larger than two
+
+To verify the generalization performance of an AI/ML model over various scenarios, the *set of scenarios* are considered focusing on one or more of the following aspects:
+
+- Various deployment scenarios (e.g., UMa, UMi, InH)
+- Various outdoor/indoor UE distributions for UMa/UMi (e.g., 10:0, 8:2, 5:5, 2:8, 0:10)
+
+- Various carrier frequencies (e.g., 2GHz, 3.5GHz)
+- Other aspects of scenarios are not precluded, e.g., various antenna spacing, various antenna virtualization (TxRU mapping), various ISDs, various UE speeds, etc.
+- Companies to report the selected scenarios for generalization verification
+
+To verify the generalization/scalability performance of an AI/ML model over various configurations (e.g., which may potentially lead to different dimensions of model input/output), the *set of configurations* are considered focusing on one or more of the following aspects:
+
+- Various bandwidths (e.g., 10MHz, 20MHz) and/or frequency granularities, (e.g., size of subband)
+- Various sizes of CSI feedback payloads
+- Various antenna port layouts, e.g., (N1/N2/P) and/or antenna port numbers (e.g., 32 ports, 16 ports)
+- Various UE speeds (e.g., 10km/h, 30km/h, 60km/h, 120km/h, etc.) for CSI prediction sub use case
+- Other aspects of configurations are not precluded, e.g., various numerologies, various rank numbers/layers, etc.
+- The selected configurations for generalization verification
+- The method to achieve generalization over various configurations to achieve scalability of the AI/ML input/output, including pre-processing, post-processing, etc
+
+For evaluating the generalization/scalability over various configurations for **CSI compression**, to achieve the scalability over *different input/output dimensions*, companies to report which case(s) are evaluated from the following list:
+
+- Case 0 (benchmark for comparison): One CSI generation part with fixed input and output dimensions to 1 CSI reconstruction part with fixed input and output dimensions for each of the different input and/or output dimensions.
+- Case 1: One CSI generation part with scalable input and/or output dimensions to $N > 1$ separate CSI reconstruction parts each with fixed and different output and/or input dimensions
+- Case 2: $M > 1$ separate CSI generation parts each with fixed and different input and/or output dimensions to one CSI reconstruction part with scalable output and/or input dimensions
+- Case 3: A pair of CSI generation part with scalable input/output dimensions and CSI reconstruction part with scalable output and/or input dimensions
+
+For CSI compression, to achieve the scalability over *different input dimensions* of CSI generation part (e.g., different bandwidths/frequency granularities, or different antenna ports), the generalization cases are elaborated as follows:
+
+- Case 1: The AI/ML model is trained based on training dataset from a fixed dimension X1 (e.g., a fixed bandwidth/frequency granularity, and/or number of antenna ports), and then the AI/ML model performs inference/test on a dataset from the same dimension X1.
+- Case 2: The AI/ML model is trained based on training dataset from a single dimension X1, and then the AI/ML model performs inference/test on a dataset from a different dimension X2.
+- Case 3: The AI/ML model is trained based on training dataset by mixing datasets subject to multiple dimensions of X1, X2, ..., Xn, and then the AI/ML model performs inference/test on a single dataset subject to the dimension of X1, or X2, ..., or Xn.
+- Note: For Case 2/3, the solutions to achieve the scalability between $X_i$ and $X_j$ , are reported by companies, including, e.g., pre-processing to angle-delay domain, padding, additional adaptation layer in AI/ML model, etc.
+
+For CSI compression, to achieve the scalability over *different output dimensions* of CSI generation part (e.g., different generated CSI feedback dimensions), the generalization cases of are elaborated as follows
+
+- Case 1: The AI/ML model is trained based on training dataset from a fixed output dimension Y1 (e.g., a fixed CSI feedback dimension), and then the AI/ML model performs inference/test on a dataset from the same output dimension Y1.
+
+- Case 2: The AI/ML model is trained based on training dataset from a single output dimension Y<sub>1</sub>, and then the AI/ML model performs inference/test on a dataset from a different output dimension Y<sub>2</sub>.
+- Case 3: The AI/ML model is trained based on training dataset by mixing datasets subject to multiple dimensions of Y<sub>1</sub>, Y<sub>2</sub>, ..., Y<sub>n</sub>, and then the AI/ML model performs inference/test on a single dataset of Y<sub>1</sub>, or Y<sub>2</sub>, ..., or Y<sub>n</sub>.
+- Notes: For Case 1/2/3, companies to report whether the output of the CSI generation part is before quantization or after quantization. For Case 2/3, the solutions to achieve the scalability between Y<sub>i</sub> and Y<sub>j</sub>, are reported by companies, including, e.g., truncation, additional adaptation layer in AI/ML model, etc.
+
+#### ***Model Fine-tuning:***
+
+For the evaluation of the potential performance benefits of model fine-tuning of CSI feedback enhancement, which is optionally assessed, the following case is considered:
+
+- The AI/ML model is trained based on training dataset from a different dataset than Scenario#B/Configuration#B, e.g., Scenario#A/Configuration#A, Scenario#A/Configuration#B, Scenario#B/Configuration#A, and then the AI/ML model is updated based on a fine-tuning dataset Scenario#B/Configuration#B. After that, the AI/ML model is tested on Scenario#B/Configuration#B.
+- In this case, the fine-tuning dataset setting (e.g., size of dataset) is to be reported along with the improvement of performance.
+
+#### ***Further details on evaluations including training collaboration types***
+
+For the evaluation of Type 2 (Joint training of the two-sided model at network side and UE side, respectively), following procedure is considered as an example:
+
+- For each FP/BP loop,
+ - Step 1: UE side generates the FP results (i.e., CSI feedback) based on the data sample(s), and sends the FP results to NW side
+ - Step 2: NW side reconstructs the CSI based on FP results, trains the CSI reconstruction part, and generates the BP information (e.g., gradients), which are then sent to UE side
+ - Step 3: UE side trains the CSI generation part based on the BP information from NW side
+- Note: the dataset between UE side and NW side is aligned.
+- Other Type 2 training approaches are not precluded and reported by companies
+
+For the evaluations of Type 2 (Joint training of the two-sided model at network side and UE side, respectively), the following evaluation cases are considered for *multi-vendors*,
+
+- Case 1 (baseline): Type 2 training between one NW part model to one UE part model
+- Case 2: Type 2 training between one NW part model and M>1 separate UE part models.
+ - Companies to report the AI/ML structures for the UE part model and the NW part model
+- Case 3: Type 2 training between one UE part model and N>1 separate NW part models.
+ - Companies to report the AI/ML structures for the UE part model and the NW part model
+
+For the evaluation of an example of Type 3 (Separate training at NW side and UE side), the following procedure is considered for the *sequential training starting with NW side training* (NW-first training):
+
+- Step1: NW side trains the NW side CSI generation part (which is not used for inference) and the NW side CSI reconstruction part jointly
+- Step2: After NW side training is finished, NW side shares UE side with a set of information (e.g., dataset) that is used by the UE side to be able to train the UE side CSI generation part
+ - Companies to report Dataset construction, e.g., the set of information includes the input and output of the Network side CSI generation part, or includes the output of the Network side CSI generation part only, or
+
+other information if applicable. Also report the Quantization behaviour, e.g., whether the shared output of the Network side CSI generation part is before or after quantization.
+
+- Step3: UE side trains the UE side CSI generation part based on the received set of information
+- Other Type 3 NW-first training approaches are not precluded
+
+For the evaluation of an example of Type 3 (Separate training at NW side and UE side), the following procedure is considered for the *sequential training starting with UE side training* (UE-first training):
+
+- Step1: UE side trains the UE side CSI generation part and the UE side CSI reconstruction part (which is not used for inference) jointly
+- Step2: After UE side training is finished, UE side shares NW side with a set of information (e.g., dataset) that is used by the NW side to be able to train the CSI reconstruction part
+ - Companies to report Dataset construction, e.g., the set of information includes the input and label of the UE side CSI reconstruction part, or includes the input of the UE side CSI reconstruction part only, or other information if applicable. Also, report the Quantization behaviour, e.g., whether the shared input of the UE side CSI reconstruction part is before or after quantization.
+- Step3: NW side trains the NW side CSI reconstruction part based on the received set of information
+- Other Type 3 UE-first training approaches are not precluded
+
+For the evaluation of an example of Type 3 (Separate training at NW side and UE side), the following evaluation cases for *sequential training* are considered for *multi-vendors*:
+
+- Case 1 (baseline): Type 3 training between one NW part model and one UE part model
+ - Note 1: Case 1 can be naturally applied to the NW-first training case where 1 NW part model to $M > 1$ separate UE part models
+ - Companies to report the dataset used between the NW part model and the UE part model, e.g., whether dataset for training UE part model is the same or a subset of the dataset for training NW part model
+ - Note 2: Case 1 can be naturally applied to the UE-first training case where 1 UE part model to $N > 1$ separate NW part models
+ - Companies to report the dataset used between the NW part model and the UE part model, e.g., whether dataset for training NW part model is the same or a subset of the dataset for training UE part model
+ - Companies to report the AI/ML structures for the combination(s) of UE part model and NW part model, which can be the same or different
+- Case 2: For UE-first training, Type 3 training between one NW part model and $M > 1$ separate UE part models
+ - Note: Case 2 can be also applied to the $M > 1$ UE part models to $N > 1$ NW part models
+ - Companies to report the AI/ML structures for the $M > 1$ UE part models and the NW part model
+ - Companies to report the dataset used at UE part models, e.g., same or different dataset(s) among $M$ UE part models
+- Case 3: For NW-first training, Type 3 training between one UE part model and $N > 1$ separate NW part models
+ - Note: Case 3 can be also applied to the $N > 1$ NW part models to $M > 1$ UE part models
+ - Companies to report the AI/ML structures for the UE part model and the $N > 1$ NW part models
+ - Companies to report the dataset used at NW part models, e.g., same or different dataset(s) among $N$ NW part models
+- Case 4: 1-on-1 training with joint training: benchmark/upper bound for performance comparison.
+
+For the evaluation of Type 3 (Separate training at NW side and UE side), the following cases are considered for evaluations:
+
+- Case 1 (baseline): Aligned AI/ML model structure between NW side and UE side
+- Case 2: Not aligned AI/ML model structures between NW side and UE side
+ - Companies to report the AI/ML structures for the UE part model and the NW part model, e.g., different backbone (e.g., CNN, Transformer, etc.), or same backbone but different structure (e.g., number of layers)
+ - For the evaluation of training Type 3 under CSI compression, for the benchmark case (1-on-1 joint training) for performance comparison, the structures for the pair of NW part model/UE part model for the new case are the same with the Type 3 case to be compared, e.g., if the Type 3 is Transformer#1 for NW part model and CNN#1 for UE part model, then the benchmark case for performance comparison is also Transformer#1 for NW part model and CNN#1 for UE part model with joint training.
+
+#### **Evaluation assumptions:**
+
+Table 6.2.1-1 presents the baseline system level simulation assumptions for AI/ML based CSI feedback enhancement evaluations.
+
+**Table 6.2.1-1: Baseline System Level Simulation assumptions for AI/ML based CSI feedback enhancement evaluations**
+
+| Parameter | Value |
+|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Duplex, Waveform | FDD (TDD is not precluded), OFDM |
+| Multiple access | OFDMA |
+| Scenario | Dense Urban (Macro only) is a baseline.<br>Other scenarios (e.g., UMi@4GHz 2GHz, Urban Macro) are not precluded. |
+| Frequency Range | FR1 only, 2GHz as baseline, optional for 4GHz (if R16 as baseline)<br><br>FR1 only, 2GHz with duplexing gap of 200MHz between DL and UL, optional for 4GHz (if R17 as baseline) |
+| Inter-BS distance | 200m |
+| Channel model | According to TR 38.901 |
+| Antenna setup and port layouts at gNB | Companies need to report which option(s) are used between <ul style="list-style-type: none"> <li>- 32 ports: (8,8,2,1,1,2,8), (dH,dV) = (0.5, 0.8)<math>\lambda</math></li> <li>- 16 ports: (8,4,2,1,1,2,4), (dH,dV) = (0.5, 0.8)<math>\lambda</math></li> </ul> Other configurations are not precluded. |
+| Antenna setup and port layouts at UE | 4RX: (1,2,2,1,1,1,2), (dH,dV) = (0.5, 0.5) $\lambda$ for (rank 1-4)<br>2RX: (1,1,2,1,1,1,1), (dH,dV) = (0.5, 0.5) $\lambda$ for (rank 1,2)<br>Other configuration is not precluded. |
+| BS Tx power | 41 dBm for 10MHz, 44dBm for 20MHz, 47dBm for 40MHz |
+| BS antenna height | 25m |
+| UE antenna height & gain | Follow TR36.873 |
+| UE receiver noise figure | 9dB |
+| Modulation | Up to 256QAM |
+| Coding on PDSCH | LDPC<br>Max code-block size=8448bit |
+| Numerology | Slot/non-slot: 14 OFDM symbol slot<br>SCS: 15kHz for 2GHz, 30kHz for 4GHz |
+| Simulation bandwidth | 10 MHz for 15kHz as a baseline, and configurations which emulate larger BW, e.g., same sub-band size as 40/100 MHz with 30kHz, may be optionally considered. Above 15kHz is replaced with 30kHz SCS for 4GHz (if R16 as baseline)<br><br>20 MHz for 15kHz as a baseline (optional for 10 MHz with 15kHz), and configurations which emulate larger BW, e.g., same sub-band size as 40/100 MHz with 30kHz, may be optionally considered. Above 15kHz is replaced with 30kHz SCS for 4GHz (if R17 as baseline) |
+| Frame structure | Slot Format 0 (all downlink) for all slots |
+| MIMO scheme | SU/MU-MIMO with rank adaptation. Companies are encouraged to report the SU/MU-MIMO with RU. |
+| MIMO layers | For all evaluation, companies to provide the assumption on the maximum MU layers (e.g., 8 or 12) |
+| CSI feedback | Feedback assumption at least for baseline scheme <ul style="list-style-type: none"> <li>- CSI feedback periodicity (full CSI feedback): 5 ms (baseline)</li> </ul> |
+
+| | |
+|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | - Scheduling delay (from CSI feedback to time to apply in scheduling): 4 ms |
+| Overhead | Companies shall provide the downlink overhead assumption (i.e., whether the CSI-RS transmission is UE-specific or not and take that into account for overhead computation) |
+| Traffic model | At least, FTP model 1 with packet size 0.5 Mbytes is assumed. Other options are not precluded |
+| Traffic load (Resource utilization) | 20/50/70%. Companies are encouraged to report the MU-MIMO utilization. |
+| UE distribution | CSI compression: 80% indoor (3 km/h), 20% outdoor (30 km/h)<br>CSI prediction: 100% outdoor (10, 20, 30, 60, 120 km/h) including outdoor-to-indoor car penetration loss per TR 38.901 if the simulation assumes UEs inside vehicles. No explicit trajectory modeling considered for evaluations. |
+| UE receiver | MMSE-IRC as the baseline receiver |
+| Feedback assumption | Realistic |
+| Channel estimation | Realistic as a baseline. Up to companies to choose the error modelling method for realistic channel estimation.<br>Ideal DL channel estimation is optionally taken into the baseline of evaluation methodology for the purpose of calibration and/or comparing intermediate results (e.g., accuracy of AI/ML output CSI, etc.). Up to companies to report whether/how ideal channel is used in the dataset construction and performance evaluation/inference.<br><br>Note: Eventual performance comparison with the benchmark release and drawing SI conclusions should be based on realistic DL channel estimation. |
+| Evaluation Metric | Throughput and CSI feedback overhead as baseline metrics.<br><br>The CSI feedback overhead is calculated as the weighted average of CSI payload per rank and the distribution of ranks reported by the UE.<br><ul style="list-style-type: none"> <li>- For AI/ML based solutions: The above-mentioned "CSI feedback overhead" is calculated as max allowed bits at the given rank.</li> <li>- For legacy Type II CB: Option 2b is mandatorily reported by companies, while Option 2a can be optionally reported up to companies if partial NZC report is assumed for the legacy Type II CB <ul style="list-style-type: none"> <li>- Option 2a: The above-mentioned "CSI feedback overhead" is calculated as each CSI reported payload with a given rank</li> <li>- Option 2b: The above-mentioned "CSI feedback overhead" is calculated as max allowed bits at the given rank</li> </ul> </li> </ul> Additional metrics, e.g., ratio between throughput and CSI feedback overhead, can be used.<br>Maximum overhead (payload size for CSI feedback) for each rank at one feedback instance is the baseline metric for CSI feedback overhead, and companies can provide other metrics. |
+| Baseline for performance evaluation | For CSI compression:<br>Companies need to report which option is used between:<br><ul style="list-style-type: none"> <li>- Rel-16 Type II Codebook as the baseline for performance and overhead evaluation.</li> <li>- Rel-17 Type II Codebook as the baseline for performance and overhead evaluation.</li> </ul> Additional assumptions from R17 Type II EVM: Same consideration with respect to utilizing angle-delay reciprocity should be considered for the AI/ML based CSI feedback and the baseline scheme if R17 Type II codebook is selected as baseline.<br><br>Optionally, Type I Codebook (if it outperforms Type II Codebook) can be considered for comparing AI/ML schemes.<br><br>For CSI-prediction:<br>Both of the following are taken as baseline: <ul style="list-style-type: none"> <li>- The nearest historical CSI without prediction</li> </ul> |
+
+| | |
+|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | <ul style="list-style-type: none"> <li>- Non-AI/ML or AI/ML with collaboration Level x based CSI prediction for which corresponding details would need to be reported</li> </ul> <p>Note: the specific non-AI/ML based CSI prediction is compatible with R18 MIMO; collaboration level x AI/ML based CSI prediction could be implementation based AI/ML compatible with R18 MIMO as an example.</p> <p>For the evaluation of CSI enhancements, companies can optionally provide the additional throughput baseline based on CSI without compression (e.g., eigenvector from measured channel), which is taken as an upper bound for performance comparison.</p> |
+| Note: | the baseline EVM is used to compare the performance with the benchmark release, while the AI/ML related parameters (e.g., dataset construction, generalization verification, and AI/ML related metrics) can be of additional/different assumptions. The conclusions for the use cases in the SI should be drawn based on generalization verification over potentially multiple scenarios/configurations. |
+
+Table 6.2.1-2 presents the baseline link level simulation assumptions for AI/ML based CSI feedback enhancement evaluations.
+
+**Table 6.2.1-2: Baseline Link Level Simulation assumptions for AI/ML based CSI feedback enhancement evaluations**
+
+| Parameter | Value |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Duplex, Waveform | FDD (TDD is not precluded), OFDM |
+| Carrier frequency | 2GHz as baseline, optional for 4GHz |
+| Bandwidth | 10MHz or 20MHz |
+| Subcarrier spacing | 15kHz for 2GHz, 30kHz for 4GHz |
+| Nt | 32: (8,8,2,1,1,2,8), (dH,dV) = (0.5, 0.8) $\lambda$ |
+| Nr | 4: (1,2,2,1,1,1,2), (dH,dV) = (0.5, 0.5) $\lambda$ |
+| Channel model | CDL-C as baseline, CDL-A as optional |
+| UE speed | 3kmhr, 10km/h, 20km/h or 30km/h to be reported by companies |
+| Delay spread | 30ns or 300ns |
+| Channel estimation | <p>Realistic channel estimation algorithms (e.g., LS or MMSE) as a baseline.</p> <p>Ideal DL channel estimation is optionally taken into the baseline of evaluation methodology for the purpose of calibration and/or comparing intermediate results (e.g., accuracy of AI/ML output CSI, etc.). Up to companies to report whether/how ideal channel is used in the dataset construction and performance evaluation/inference.</p> <p>Note: Eventual performance comparison with the benchmark release and drawing SI conclusions should be based on realistic DL channel estimation</p> |
+| Rank per UE | Rank 1-4. Companies are encouraged to report the Rank number, and whether/how rank adaptation is applied |
+| Note: | the baseline EVM is used to compare the performance with the benchmark release, while the AI/ML related parameters (e.g., dataset construction, generalization verification, and AI/ML related metrics) can be of additional/different assumptions. The conclusions for the use cases in the SI should be drawn based on generalization verification over potentially multiple scenarios/configurations. |
+
+#### *CSI compression sub use case specific aspects:*
+
+For the evaluation of the AI/ML based CSI compression sub use cases, a two-sided model is considered as a starting point, including an AI/ML-based CSI generation part to generate the CSI feedback information and an AI/ML-based CSI reconstruction part which is used to reconstruct the CSI from the received CSI feedback information. At least for inference, the CSI generation part is located at the UE side, and the CSI reconstruction part is located at the gNB side.
+
+Figure 6.2.1-1 provides an example for the inference procedure for CSI compression. For generating the input of CSI generation model, it may need some further pre-processing on the measured channel; for the output of the CSI reconstruction model, some further post-processing may also be applied. Besides CSI feedback of quantization output, there may also be other CSI/PMI related information transmitted. There may be other examples of merging quantization/dequantization into the inference for CSI generation/reconstruction, CSI generation model/CSI reconstruction model, respectively.
+
+
+
+Figure 6.2.1-1: An example of the CSI compression inference procedure. The diagram shows a flow from left to right. On the left, a dashed box labeled 'CSI generation part' and 'UE' contains two blocks: 'Inference for CSI generation' and 'Quantization'. An arrow labeled 'Input of CSI generation part' enters the first block. An arrow labeled 'Input of quantization' connects the first block to the second. An arrow labeled 'CSI feedback' exits the second block. On the right, a dashed box labeled 'CSI reconstruction part' and 'gNB' contains two blocks: 'Dequantization' and 'Inference for CSI reconstruction'. An arrow labeled 'CSI feedback' enters the 'Dequantization' block. An arrow labeled 'Output of dequantization' connects the 'Dequantization' block to the 'Inference for CSI reconstruction' block. An arrow labeled 'Output of CSI reconstruction part' exits the final block.
+
+**Figure 6.2.1-1: An example of the CSI compression inference procedure**
+
+For the evaluation of the AI/ML based **CSI compression** sub use case, the following details of models are reported:
+
+- The structure of the AI/ML model, e.g., type (CNN, RNN, Transformer, Inception, ...), the number of layers, branches, real valued or complex valued parameters, etc.
+- AI/ML model input (for CSI generation part)/output (for CSI reconstruction part) types for evaluations
+- Data pre-processing/post-processing
+- Loss function
+- Specific quantization/dequantization method, e.g., vector quantization, scalar quantization, etc,
+
+For the evaluation of the AI/ML based CSI compression sub use cases, at least the following types of AI/ML model input (for CSI generation part)/output (for CSI reconstruction part) are considered for evaluations:
+
+- Raw channel matrix, e.g., channel matrix with the dimensions of Tx, Rx, and frequency unit. Companies to report the raw channel is in frequency domain or delay domain.
+- Precoding matrix. Companies to report the precoding matrix is a group of eigenvector(s) or an eType II-like reporting (i.e., eigenvectors with angular-delay domain representation).
+
+For the evaluation of quantization aware/non-aware training, the following cases are considered and reported by companies:
+
+- Case 1: Quantization non-aware training, where the float-format variables are directly passed from CSI generation part to CSI reconstruction part during the training
+ - o Fixed/pre-configured quantization method/parameters is applied for the inference phase. Companies to report the design of the fixed/pre-configured quantization method/parameters, e.g., quantization resolution, vector quantization codebook, etc
+- Case 2: Quantization-aware training, where quantization/dequantization is involved in the training process
+ - o Case 2-1: Fixed/pre-configured quantization method/parameters are applied during the training phase; the same quantization codebook is applied for the inference phase. Companies to report the design of the fixed/pre-configured quantization method/parameters, e.g., quantization resolution, vector quantization codebook, etc.
+ - o Case 2-2: The quantization method/parameters are updated in together with the AI/ML models during the training; when training is finished, the final quantization codebook is applied for the inference phase. Companies to report how to update the quantization method/parameters during the training
+- Quantization methods including uniform vs non-uniform quantization, scalar versus vector quantization, and associated parameters, e.g., quantization resolution, etc.
+- How to use the quantization methods are reported by companies
+
+Considering performance impact of ground-truth quantization in the CSI compression, study high resolution quantization methods for ground-truth CSI, including at least the following options:
+
+- High resolution scalar quantization
+
+- High resolution codebook quantization, e.g., Rel-16 TypeII-like method with new parameters, in which case companies are to report the R16 Type II parameters with specified or new/larger values to achieve higher resolution of the ground-truth CSI labels, e.g., $L$ , $p_v$ , $\beta$ , reference amplitude, differential amplitude, phase, etc
+- Float32 adopted as the baseline/upper-bound for performance comparisons
+- Consider legacy values of PC6 & PC8 for performance comparison
+
+For CSI compression sub use case with rank $\geq 1$ , AI/ML model setting to adapt to ranks/layers to be reported amongst the following options:
+
+- Option 1-1 (rank specific): Separated AI/ML models are trained per rank value and applied for corresponding ranks to perform individual inference, any specific model operates on multi-layers jointly.
+- Option 1-2 (rank common): A unified AI/ML model is trained and applied for adaptive ranks to perform inference, the model operates on multi-layers jointly.
+- Option 2 (layer specific): Separated AI/ML models are trained per layer value and applied for corresponding layers to perform individual inference.
+ - o Note: input/output type is Precoding matrix
+ - o Companies to report the setting is
+ - Option 2-1: layer specific and rank common (different models applied for different layers; for a specific layer, the same model is applied for all rank values), or
+ - Option 2-2: layer specific and rank specific (different models applied for different layers; for a specific layer, different models are applied for different rank values)
+- Option 3 (layer common): A unified AI/ML model is trained and applied for each layer to perform individual inference.
+ - o Note: input/output type is Precoding matrix
+ - o Companies to report whether the setting is
+ - Option 3-1: layer common and rank common (A unified AI/ML model is applied for each layer under any rank value to perform individual inference), or
+ - Option 3-2: layer common and rank specific (different models applied for different rank values; for a specific rank, the same model is applied for all layers)
+
+For CSI compression sub use case with rank $> 1$ , for a given configured Max rank= $K$ , the complexity of FLOPs is reported as the maximum FLOPs over all ranks each includes the summation of FLOPs for inference per layer if applicable, e.g.,
+
+- Option 1-1 (rank specific): Max FLOPs over $K$ rank specific models.
+- Option 1-2 (rank common): FLOPs of the rank common model.
+- Option 2-1 (layer specific and rank common): Sum of the FLOPs of $K$ models (for the rank= $K$ ).
+- Option 2-2 (layer specific and rank specific): Max of the FLOPs over $K$ ranks, $k=1, \dots, K$ , each with a sum of $k$ models.
+- Option 3-1 (layer common and rank common): $K \times$ FLOPs of the common model.
+- Option 3-2 (layer common and rank specific): Max of the FLOPs over $K$ ranks, $k=1, \dots, K$ , each with $k \times$ FLOPs of the layer common model.
+
+For CSI compression sub use case with rank $> 1$ , the storage of memory storage/number of parameters is reported as the summation of memory storage/number of parameters over all models potentially used for any layer/rank, e.g.,
+
+- Option 1-1 (rank specific)/Option 3-2 (layer common and rank specific): Sum of memory storage/number of parameters over all rank specific models.
+
+- Option 1-2 (rank common): A single memory storage/number of parameters for the rank common model.
+- Option 2-1 (layer specific and rank common): Sum of memory storage/number of parameters over all layer specific models.
+- Option 2-2 (layer specific and rank specific): Sum of memory storage/number of parameters for the specific models over all ranks and all layers in per rank.
+- Option 3-1 (layer common and rank common): A single memory storage/number of parameters for the common model
+
+For the evaluation of CSI compression, the specific CQI determination method(s) for AI/ML can be reported by introducing an additional field in the template, e.g.,
+
+- Option 1a: CQI is calculated based on the target CSI from the realistic channel estimation.
+- Option 1b: CQI is calculated based on the target CSI from the realistic channel estimation and potential adjustment.
+- Option 1c: CQI is calculated based on traditional codebook.
+- Option 2a: CQI is calculated based on CSI reconstruction output, if CSI reconstruction model is available at the UE and UE can perform reconstruction model inference with potential adjustment.
+ - o Option 2a-1: The CSI reconstruction part for CQI calculation at the UE same as the actual CSI reconstruction part at the NW.
+ - o Option 2a-2: The CSI reconstruction part for CQI calculation at the UE is a proxy model, which is different from the actual CSI reconstruction part at the NW.
+- Option 2b: CQI is calculated using two stage approach, UE derives CQI using precoded CSI-RS transmitted with a reconstructed precoder.
+
+#### *CSI prediction sub use case specific aspects:*
+
+Figure 6.2.1-2 provides an example for the inference procedure for CSI prediction. For generating the input of CSI prediction model, it may need some further pre-processing on the measured channel; for the output of the CSI prediction model, some further post-processing may also be applied.
+
+
+
+```
+
+graph LR
+ subgraph UE
+ direction LR
+ A[Model input
+(historic CSI)] --> B[CSI prediction
+Model]
+ B --> C[Model output
+(predicted CSI)]
+ end
+
+```
+
+Diagram illustrating the CSI prediction inference procedure. A block labeled 'CSI prediction Model' is shown within a 'UE' (User Equipment) boundary. An arrow labeled 'Model input (historic CSI)' points into the model from the left. An arrow labeled 'Model output (predicted CSI)' points out of the model to the right.
+
+**Figure 6.2.1-2: An example of the CSI prediction inference procedure**
+
+For the evaluation of the AI/ML based **CSI prediction** sub use case, the following details of models are reported:
+
+- The structure of the AI/ML model, e.g., type (FCN, RNN, CNN,...), the number of layers, branches, format of parameters, etc.
+- The input CSI type, e.g., raw channel matrix, eigenvector(s) of the raw channel matrix, feedback CSI information, etc.
+ - Including assumptions on the observation window, i.e., number/time distance of historic CSI/channel measurements
+- The output CSI type, e.g., channel matrix, eigenvector(s), feedback CSI information, etc.
+ - Including assumptions on the prediction window, i.e., number/time distance of predicted CSI/channel
+- Data pre-processing/post-processing
+- Loss function
+
+For the input CSI type, both of the following types are considered for evaluations:
+
+- Raw channel matrices
+- Eigenvector(s)
+
+For SLS, spatial consistency Procedure A with 50m decorrelation distance from TR 38.901 is used (if not used, assumptions used need to be reported). UE velocity vector is assumed as fixed over time in Procedure A modelling.
+
+### 6.2.2 Performance results
+
+CSI\_Table 1 through CSI\_Table 7 in attached Spreadsheets for CSI feedback enhancement evaluations present the performance results for:
+
+- CSI\_Table 1. Evaluation results for CSI compression of 1-on-1 joint training without model generalization/scalability
+- CSI\_Table 2. Evaluation results for CSI compression with model generalization
+- CSI\_Table 3. Evaluation results for CSI compression with model scalability
+- CSI\_Table 4. Evaluation results for CSI compression of multi-vendor joint training without model generalization/scalability
+- CSI\_Table 5. Evaluation results for CSI compression of separate training without model generalization/scalability
+- CSI\_Table 6. Evaluation results for CSI prediction without model generalization/scalability
+- CSI\_Table 7. Evaluation results for CSI prediction with model generalization
+
+For the evaluation of CSI compression of 1-on-1 joint training without model generalization/scalability, the following baselines are recommended to facilitate calibration of results:
+
+- Benchmark: R16 eType II CB;
+ - Others can be additionally submitted, e.g., Type I CB.
+- Input/Output type: Eigenvectors of the current CSI
+ - Other can be additionally submitted, e.g., eigenvectors with additional past CSI, eType II-like input, raw channel matrix, etc.
+- Ground-truth CSI quantization method: Float32, i.e., without quantization (baseline/upper-bound for performance comparison)
+ - Other high resolution CSI quantization methods can be additionally submitted for comparison, e.g., R16 eType II-like method with new parameters, scalar quantization, etc.
+- Rank/layer adaptation settings for rank>1: Option 3-1, i.e., layer common and rank common.
+ - Other rank>1 options can be additionally submitted for comparison, e.g., Option 1-1/1-2/2-1/2-2/3-2.
+- Quantization method: quantization-aware training (Case 2-1 or Case 2-2)
+ - Quantization non-aware training can be additionally submitted for comparison
+ - SQ and/or VQ is up to companies; companies are encouraged to provide results of various cases for comparison.
+- Performance metric for intermediate KPI: SGCS
+ - NMSE can be additionally submitted
+
+The CSI feedback reduction is provided for three CSI feedback overhead ranges (CSI feedback overhead A, CSI feedback overhead B, CSI feedback overhead C), where for each CSI feedback overhead range of the benchmark, it is calculated as the gap between the CSI feedback overhead of benchmark and the CSI feedback overhead of AI/ML corresponding to the same mean UPT. The various CSI feedback overhead ranges are defined as:
+
+CSI feedback overhead A such that $A \leq \beta \cdot 80$ bits
+
+CSI feedback overhead B such that $\beta \cdot 100$ bits $\leq B \leq \beta \cdot 140$ bits
+
+CSI feedback overhead C $\geq \beta \cdot 230$ bits
+
+where, $\beta = 1$ for rank = 1 and $\beta = 1.5$ for rank $> 1$
+
+Note: companies report the exact CSI feedback overhead considered.
+
+Note: the CSI feedback overhead reduction and gain for mean/5%tile UPT are determined at the same payload size for benchmark scheme.
+
+Note: "Benchmark" means the type of Legacy CB used for comparison. "Quantization/dequantization method" includes the description of training awareness (Case 1/2-1/2-2), type of quantization/dequantization (SQ/VQ), etc. "Input type" means the input of the CSI generation part. "Output type" means the output of the CSI reconstruction part.
+
+For the evaluation of *CSI prediction* without model generalization/scalability verification, the following baselines are recommended to facilitate calibration of results:
+
+- UE speed: 10km/h, 30km/h, 60km/h;
+ - Others can be additionally submitted, e.g., 120km/h.
+- Input/Output type: Raw channel matrix
+ - Other can be additionally submitted, e.g., eigenvectors.
+- Observation window (number/distance): 5/5ms, 10/5ms
+ - Other observation window configurations can be additionally submitted for comparison, e.g., 3/5ms, 4/5ms, 8/2.5ms, 10/4ms, etc.
+- Prediction window (number/distance between prediction instances/distance from the last observation instance to the 1st prediction instance): 1/5ms/5ms
+ - Other prediction window configurations can be additionally submitted for comparison, e.g., 3/5ms/5ms, 5/5ms/5ms, 4/2.5ms/2.5ms, 5/4ms/4ms, etc.
+- Performance metric for intermediate KPI: SGCS
+ - NMSE can be additionally submitted.
+- Spatial consistency configuration (optional): procedure A with 50m decorrelation distance and channel updating periodicity of 1 ms.
+
+For the evaluation of *CSI prediction* with model generalization/scalability verification, the following baselines are recommended to facilitate calibration of results:
+
+- Performance metric for intermediate KPI: SGCS
+ - NMSE can be additionally submitted.
+
+#### 6.2.2.1 1-on-1 joint training for CSI compression
+
+##### *Input/output type*
+
+For the evaluation of CSI compression, for the type of AI/ML model input (for CSI generation part)/output (for CSI reconstruction part), a vast majority of companies adopt precoding matrix as model input/output.
+
+Note: For the evaluations of CSI compression with 1-on-1 joint training, 22 sources take precoding matrix without angular-delay domain conversion as the model input/output; 2 sources take precoding matrix with angular-delay domain representation as the model input/output. No company submitted explicit channel matrix as input.
+
+The complexity metric in terms of FLOPs and number of parameters of AI/ML models adopted in the evaluations of CSI compression are summarized in Figure 6.2.2.1-1, where the complexity for the CSI generation part and the complexity for the CSI reconstruction part are illustrated separately.
+
+- A majority of 25 sources adopt the CSI generation model subject to the FLOPs from 10M to 800M, and 26 sources adopt the CSI reconstruction model subject to the FLOPs from 10M to 1100M.
+- A majority of 21 sources adopt the CSI generation model subject to the number of parameters from 1M to 13M, and 22 sources adopt the CSI reconstruction model subject to the number of parameters from 1M to 17M.
+- Results refer to Table 1 of clause 7.3, R1-2310450.
+
+
+
+| Model Part | Number of Parameters (M) | FLOPs (M) |
+|-------------------------|--------------------------|------------|
+| CSI generation part | 1 to 13 | 10 to 800 |
+| CSI reconstruction part | 1 to 17 | 10 to 1100 |
+
+Scatter plot showing the complexity of AI/ML models for CSI compression. The Y-axis is FLOPs/M (log scale from 0.01 to 10000) and the X-axis is Number of parameters/M (log scale from 0.01 to 100). Blue dots represent the CSI generation part, and red dots represent the CSI reconstruction part. Most data points for both parts are clustered between 1M and 10M parameters and 10M and 1000M FLOPs.
+
+**Figure 6.2.2.1-1: Complexity of AI/ML models from evaluation results in terms of FLOPs and number of parameters for CSI compression**
+
+##### *SGCS performance*
+
+For the evaluation of AI/ML based CSI compression compared to the *benchmark in terms of SGCS*,
+
+For Max rank 1, Layer 1,
+
+- 14 sources observe the performance gain of 2.6%~ 8.8% at CSI payload X (small payload);
+- 18 sources observe the performance gain of 0.9%~ 8.1% at CSI payload Y (medium payload);
+- 16 sources observe the performance gain of 0.9%~ 7% at CSI payload Z (large payload);
+- Note: 3 sources observe the performance gain of 0%, 10.2%~11.6% at CSI payload X (small payload), 0.9% at CSI payload Y (medium payload), -0.3% at CSI payload Z (large payload) which biases from the majority range.
+
+For Max rank 2, Layer 1,
+
+- 15 sources observe the performance gain of 3.9%~ 11% at CSI payload X (small payload);
+- 13 sources observe the performance gain of 0.7%~ 4.5% at CSI payload Y (medium payload);
+- 14 sources observe the performance gain of -0.2%~ 6.5% at CSI payload Z (large payload);
+- Note: 4 sources observe the performance gain of 12.7%~15.6% at CSI payload X (small payload), 5%~10.6% at CSI payload Y (medium payload), 7.1% at CSI payload Z (large payload) which biases from the majority range.
+
+For Max rank 2, Layer 2, more gains are observed in general compared with Layer 1 of Max rank 2:
+
+- 13 sources observe the performance gain of 5.92%~ 30.2% at CSI payload X (small payload);
+- 13 sources observe the performance gain of 1.5%~ 23.08% at CSI payload Y (medium payload);
+
+- 11 sources observe the performance gain of 4.4%~ 12.99% at CSI payload Z (large payload);
+- Note: 5 sources observe the performance gain of -7.4%~1.1%, 49.3% at CSI payload X (small payload), - 0.3%~1.5%, 41.7% at CSI payload Y (medium payload), -0.4%~2.2%, 45.9% at CSI payload Z (large payload) which biases from the majority range.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix of the current CSI is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS for Layer 1 of Max rank 1 or Layer 1/2 of Max rank 2.
+- CSI payload X is $\leq 80$ bits; CSI payload Y is 100 bits - 140 bits; CSI payload Z is $\geq 230$ bits; where X, Y, Z are applicable per layer.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.6 of R1-2308340.
+
+###### ***Mean UPT for FTP traffic***
+
+For the evaluation of AI/ML based CSI compression compared to the *benchmark in terms of mean UPT under FTP traffic*, more gains are achieved by Max rank 2 compared with Max rank 1 in general:
+
+- For Max rank 1, in general the performance gain increases with the increase of RU:
+ - For $RU \leq 39\%$ , 7 sources observe the performance gain of 0.2%~2%
+ - 6 sources observe the performance gain of 0.29%~2% at CSI feedback overhead A (small overhead);
+ - 6 sources observe the performance gain of 0.2%~1% at CSI feedback overhead B (medium overhead)
+ - 4 sources observe the performance gain of 0.33%~1% at CSI feedback overhead C (large overhead);
+ - For $RU\ 40\% \text{--} 69\%$ , 7 sources observe the performance gain of 0.1%~4%
+ - 5 sources observe the performance gain of 1.09%~3% at CSI feedback overhead A (small overhead);
+ - 4 sources observe the performance gain of 0.80%~2% at CSI feedback overhead B (medium overhead);
+ - 7 sources observe the performance gain of 0.1%~4% at CSI feedback overhead C (large overhead);
+ - For $RU \geq 70\%$ , 9 sources observe the performance gain of 0.23%~9%
+ - 9 sources observe the performance gain of 0.38%~9% at CSI feedback overhead A (small overhead)
+ - 8 sources observe the performance gain of 0.62%~5% at CSI feedback overhead B (medium overhead)
+ - 8 sources observe the performance gain of 0.23%~6% at CSI feedback overhead C (large overhead);
+ - Note: 5 sources observe gain of 0.1%~0.2%, 1.7%~2.51% at $RU \leq 39\%$ , 0.5%~1%, 2.34%~21.21% at $RU\ 40\% \text{--} 69\%$ , 2.51%~21.5% at $RU \geq 70\%$ , which bias from the majority ranges.
+- For Max rank 2, in general the performance gain increases with the increase of RU:
+ - For $RU \leq 39\%$ , 8 sources observe the performance gain of -0.3%~6%
+ - 7 sources observe the performance gain of 1%~6% at CSI feedback overhead A (small overhead);
+ - 7 sources observe the performance gain of 0.5%~6% at CSI feedback overhead B (medium overhead);
+ - 8 sources observe the performance gain of -0.3%~6% at CSI feedback overhead C (large overhead);
+ - For $RU\ 40\% \text{--} 69\%$ , 10 sources observe the performance gain of -0.5%~10%
+
+- 8 sources observe the performance gain of 3%~10% at CSI feedback overhead A (small overhead);
+- 8 sources observe the performance gain of 1.2%~9% at CSI feedback overhead B (medium overhead)
+- 10 sources observe the performance gain of -0.5%~9% at CSI feedback overhead C (large overhead)
+- For $RU \geq 70\%$ , 11 sources observe the performance gain of -0.2%~15%
+ - 11 sources observe the performance gain of 5%~15% at CSI feedback overhead A (small overhead);
+ - 11 sources observe the performance gain of 3%~9% at CSI feedback overhead B (medium overhead);
+ - 10 sources observe the performance gain of -0.2%~12% at CSI feedback overhead C (large overhead);
+- Note: 5 sources observe gain of 0.3%, 7%~30% at $RU \leq 39\%$ , 1%, 18%~23% at $RU \ 40\% \sim 69\%$ , 12.71%~26.8% at $RU \geq 70\%$ , which bias from the majority ranges.
+- For Max rank 4:
+ - For $RU \leq 39\%$ , 2 sources observe the performance gain of -4%~6%
+ - 2 sources observe the performance gain of 2.5%~6% at CSI feedback overhead A (small overhead);
+ - 1 source observes the performance gain of 6% at CSI feedback overhead B (medium overhead);
+ - 2 sources observe the performance gain of -4%~0% at CSI feedback overhead C (large overhead);
+ - For $RU \ 40\% \sim 69\%$ , 3 sources observe the performance gain of -1.8%~12.22%
+ - 3 sources observe the performance gain of 3%~12.22% at CSI feedback overhead A (small overhead);
+ - 2 sources observe the performance gain of 7.04%~11% at CSI feedback overhead B (medium overhead);
+ - 3 sources observe the performance gain of -1.8%~8.19% at CSI feedback overhead C (large overhead);
+ - For $RU \geq 70\%$ , 3 sources observe the performance gain of -1%~17%
+ - 3 sources observe the performance gain of 3%~17% at CSI feedback overhead A (small overhead);
+ - 2 sources observe the performance gain of 6.64%~17% at CSI feedback overhead B (medium overhead);
+ - 3 sources observe the performance gain of -1%~8.40% at CSI feedback overhead C (large overhead);
+ - Note: 1 source observes significant gain or significant loss under Max rank 4 due to specific CQI/RI selection method (e.g., Option 1a/2a) for AI/ML and/or CQI/RI determination method for eType II benchmark.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix of the current CSI is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is mean UPT for Max rank 1, Max rank 2, or Max rank 4.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.12 of R1-2308342.
+
+###### 5% UPT for FTP traffic
+
+For the evaluation of AI/ML based CSI compression compared to the *benchmark in terms of 5% UPT under FTP*, more gains are achieved by Max rank 2 compared with Max rank 1 in general:
+
+- For Max rank 1, in general the performance gain increases with the increase of RU:
+ - For $RU \leq 39\%$ , 3 sources observe the performance gain of 0.8%~3%
+
+- 3 sources observe the performance gain of 1.72%~3% at CSI feedback overhead A (small overhead);
+- 3 sources observe the performance gain of 0.80%~1.2% at CSI feedback overhead B (medium overhead);
+- 3 sources observe the performance gain of 1.68%~3% at CSI feedback overhead C (large overhead);
+- For RU 40%~69%, 6 sources observe the performance gain of 0.1%~7%
+ - 6 sources observe the performance gain of 2.8%~7% at CSI feedback overhead A (small overhead);
+ - 3 sources observe the performance gain of 1.22%~2.7% at CSI feedback overhead B (medium overhead);
+ - 3 sources observe the performance gain of 0.1%~3.25% at CSI feedback overhead C (large overhead);
+- For RU $\geq$ 70%, 8 sources observe the performance gain of 0.85%~20.43%
+ - 8 sources observe the performance gain of 4%~20.43% at CSI feedback overhead A (small overhead);
+ - 7 sources observe the performance gain of 1%~10.13% at CSI feedback overhead B (medium overhead);
+ - 8 sources observe the performance gain of 0.85%~8% at CSI feedback overhead C (large overhead);
+- Note: 4 sources observe gain of 0% and 5.6%~5.7% at RU $\leq$ 39%, 4.2%~5.8% at RU 40%~69%, 23%~50% at RU $\geq$ 70%, which bias from the majority ranges.
+- For Max rank 2, in general the performance gain increases with the increase of RU:
+ - For RU $\leq$ 39%, 8 sources observe the performance gain of -2%~5%
+ - 5 sources observe the performance gain of 1.1%~5% at CSI feedback overhead A (small overhead);
+ - 6 sources observe the performance gain of -2%~3% at CSI feedback overhead B (medium overhead);
+ - 7 sources observe the performance gain of -0.5%~5% at CSI feedback overhead C (large overhead);
+ - For RU 40%~69%, 8 sources observe the performance gain of -4%~13%
+ - 6 sources observe the performance gain of 7%~13% at CSI feedback overhead A (small overhead);
+ - 7 sources observe the performance gain of 0.3%~8% at CSI feedback overhead B (medium overhead);
+ - 6 sources observe the performance gain of -4%~8% at CSI feedback overhead C (large overhead);
+ - For RU $\geq$ 70%, 9 sources observe the performance gain of -1.3%~24%
+ - 6 sources observe the performance gain of 10.26%~24% at CSI feedback overhead A (small overhead);
+ - 6 sources observe the performance gain of 9%~15.02% at CSI feedback overhead B (medium overhead);
+ - 8 sources observe the performance gain of -1.3%~13.67% at CSI feedback overhead C (large overhead);
+ - Note: 7 sources observe gain of 4.4%~13% at RU $\leq$ 39%, -8%~2% at RU 40%~69%, 10%~25.6% at RU $\geq$ 70%, -10%~8.1% at RU $\geq$ 70%, which bias from the majority ranges.
+- For Max rank 4:
+ - For RU $\leq$ 39%, 2 sources observe the performance gain of -1.6%~10%
+ - 2 sources observe the performance gain of 8%~10% at CSI feedback overhead A (small overhead);
+ - 1 source observes the performance gain of 5% at CSI feedback overhead B (medium overhead);
+ - 2 sources observe the performance gain of -1.6%~1% at CSI feedback overhead C (large overhead);
+ - For RU 40%~69%, 3 sources observe the performance gain of -1.7%~23%
+ - 3 sources observe the performance gain of 5%~17% at CSI feedback overhead A (small overhead);
+ - 2 sources observe the performance gain of 6.17%~23% at CSI feedback overhead B (medium overhead);
+
+- 3 sources observe the performance gain of -1.7%~9.47% at CSI feedback overhead C (large overhead);
+- For RU $\geq$ 70%, 3 sources observe the performance gain of 2%~31%
+- 3 sources observe the performance gain of 5.8%~31% at CSI feedback overhead A (small overhead);
+- 2 sources observe the performance gain of 10.2%~30% at CSI feedback overhead B (medium overhead);
+- 3 sources observe the performance gain of 2%~15% at CSI feedback overhead C (large overhead);
+- Note: 1 source observes significant gain or significant loss under Max rank 4 due to specific CQI/RI selection method (e.g., Option 1a/2a) for AI/ML and/or CQI/RI determination method for eType II benchmark
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix of the current CSI is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is 5% UPT for Max rank 1, Max rank 2, or Max rank 4.
+- Benchmark is Rel-16 Type II codebook.
+- Results refer to Table 5.13 of R1-2308342.
+
+###### ***Mean UPT for full buffer***
+
+For the evaluation of AI/ML based CSI compression compared to the *benchmark, in terms of mean UPT under full buffer*, more gains are achieved by Max rank 2 compared with Max rank 1 in general:
+
+- For Max rank 1, 8 sources observe the performance gain of 1.1%~11%
+ - 6 sources observe the performance gain of 6%~11% at CSI feedback overhead A (small overhead);
+ - 6 sources observe the performance gain of 3%~7% at CSI feedback overhead B (medium overhead);
+ - 8 sources observe the performance gain of 1.1%~11% at CSI feedback overhead C (large overhead);
+- For Max rank 2, 9 sources observe the performance gain of 0.2%~15%
+ - 9 sources observe the performance gain of 4%~15% at CSI feedback overhead A (small overhead);
+ - 9 sources observe the performance gain of 2%~10% at CSI feedback overhead B (medium overhead);
+ - 9 sources observe the performance gain of -0.2%~14% at CSI feedback overhead C (large overhead);
+- Note: For Max rank 4, 1 source observes gain of 7.44%~9.95% over CSI feedback overhead A/B/C.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix of the current CSI is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.7 of R1-2308340.
+
+###### ***5% UPT for full buffer***
+
+For the evaluation of AI/ML based CSI compression compared to the *benchmark in terms of 5% UPT under full buffer*,
+
+- For Max rank 1, 5 sources observe the performance gain of 0%~20.9%
+ - 5 sources observe the performance gain of 2.5%~20.9% at CSI feedback overhead A (small overhead);
+
+- 5 sources observe the performance gain of 2.3%~17.4% at CSI feedback overhead B (medium overhead);
+- 4 sources observe the performance gain of 0%~6.62% at CSI feedback overhead C (large overhead);
+- For Max rank 2, 6 sources observe the performance gain of -7%~14.9%
+ - 6 sources observe the performance gain of 4.1%~14.9% at CSI feedback overhead A (small overhead);
+ - 5 sources observe the performance gain of 0.3%~4% at CSI feedback overhead B (medium overhead);
+ - 6 sources observe the performance gain of -7%~6.03% at CSI feedback overhead C (large overhead);
+- Note: For Max rank 4, 1 source observes gain of 3.59%~6.15% over CSI feedback overhead A/B/C.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix of the current CSI is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.8 of R1-2308340.
+
+##### *CSI feedback reduction*
+
+For the evaluation of AI/ML based CSI compression, compared to the benchmark, in terms of CSI feedback reduction,
+
+- For Max rank = 1,
+ - For CSI feedback overhead A (small overhead), 1 source observes the CSI feedback reduction of 10.24% for FTP traffic;
+ - For CSI feedback overhead B (medium overhead), 3 sources observe the CSI feedback reduction of 15.62%~60% for FTP traffic, and 2 sources observe the CSI feedback reduction of 37%~66% for full buffer;
+ - For CSI feedback overhead C (large overhead), 2 sources observe the CSI feedback reduction of 14.37%~55% for FTP traffic, and 2 sources observe the CSI feedback reduction of 50%~53% for full buffer;
+ - Note: For CSI feedback overhead C (large overhead), 1 source observes CSI feedback reduction of 75% for FTP traffic.
+- For Max rank = 2,
+ - For CSI feedback overhead A (small overhead), 3 sources observe the CSI feedback reduction of 20.83%~54% for FTP traffic, and 1 source observes the CSI feedback reduction of 56% for full buffer;
+ - For CSI feedback overhead B (medium overhead), 3 sources observe the CSI feedback reduction of 22.22%~52% for FTP traffic, and 2 sources observe the CSI feedback reduction of 52% for full buffer;
+ - For CSI feedback overhead C (large overhead), 3 sources observe the CSI feedback reduction of 10%~58.33% for FTP traffic, and 2 sources observe the CSI feedback reduction of 22%~54% for full buffer;
+ - Note: For CSI feedback overhead B (medium overhead), 1 source observes CSI feedback reduction of up to ~83% for FTP traffic using particular VQ codebook solution.
+- For Max rank = 4,
+ - For CSI feedback overhead A (small overhead), 2 sources observe the CSI feedback reduction of 50%~79% for FTP traffic, and 1 source observes the CSI feedback reduction of 70.53% for full buffer;
+ - For CSI feedback overhead B (medium overhead), 2 sources observe the CSI feedback reduction of 36.10%~78% for FTP traffic, and 1 source observes the CSI feedback reduction of 47.74% for full buffer;
+ - For CSI feedback overhead C (large overhead), 2 sources observe the CSI feedback reduction of 8%~58% for FTP traffic, and 1 source observes the CSI feedback reduction of 42.59% for full buffer;
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix of the current CSI is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is CSI feedback overhead reduction for Max rank 1/2/4.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.30 of R1-2308344.
+
+##### ***Monitoring for intermediate KPI, NW side monitoring***
+
+For the evaluation of intermediate *KPI based monitoring* mechanism for CSI compression, for monitoring Case 1, in terms of monitoring accuracy with Option 1,
+
+- For ground-truth CSI format of R16 eType II CB, monitoring accuracy is increased with the increase of the resolution for the ground-truth CSI (number of bits for each sample of ground-truth CSI) in general, with the impact of increased overhead, wherein
+ - for ground-truth CSI format of R16 eType II CB with PC#6, 4 sources observe $KPI_{Diff}$ as 13.2%~71.6%/ 28.5%~100%/ 68.4%~100% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively.
+ - Note: two sources observed averaging on the test samples improves the monitoring accuracy.
+ - for ground-truth CSI format of R16 eType II CB with PC#8, 5 sources observe $KPI_{Diff}$ as 21%~43.0%/ 48.1%~79.1%/ 79.8%~97.1% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively.
+ - for ground-truth CSI format of R16 eType II CB with new parameter of 580-750bits CSI payload size, 2 sources observe $KPI_{Diff}$ as 35.4%~63%/ 77.9%~93.0%/ 99.5%~99.9% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively, which have 12.7%~20%/ 13.9%~29.8%/ 8%~31.1% gain over PC#8.
+ - for ground-truth CSI format of R16 eType II CB with new parameter of around 1000bits CSI payload size, 4 sources observe $KPI_{Diff}$ as 34.9%~89%/ 82.9%~100%/ 99.9%~100% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively, which have 12.2%~68%/ 18%~43.62%/ 2.9%~31% gain over PC#8 from 3 sources and 4.67%~10.6%/ 0%~5.88%/ 0%~0.49% gain over PC#6 from 1 source.
+ - for ground-truth CSI format of R16 eType II CB with new parameter of around 1600bits CSI payload size, 2 sources observe $KPI_{Diff}$ as 89.1%~97%/ 99.9%~100%/ 100% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively, which have 76%/33%/3% gain over PC#8 from 1 source.
+- For ground-truth CSI format of 4 bits scalar quantization, 2 sources observe $KPI_{Diff}$ as 9.4%~47%/ 96.3%~100%/ 100% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Time independency is assumed over the test samples for monitoring
+- Precoding matrix is used as the model input.
+- 1-on-1 joint training is assumed.
+- The performance metric is monitoring accuracy for Layer 1.
+- Note: Results refer to Table 5.21 of R1-2308343.
+
+##### ***Monitoring for intermediate KPI, UE side monitoring***
+
+For the evaluation of intermediate *KPI based monitoring* mechanism for CSI compression, for Case 2, in terms of monitoring accuracy with Option 1,
+
+- For Case 2-1 subject to generalization Case 1 for the proxy model, 5 sources observe $KPI_{Diff}$ as 31%~84%/ 65.63%~99.8%/ 95%~100% for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively;
+
+- Compared with monitoring Case 1 with ground-truth CSI format of R16 eType II CB with new parameter of around 1000bits CSI payload size,
+ - 2 sources observe +0.99%~+4.07% gain at $KPI_{th\_1}=0.02$ ;
+ - 3 sources observe -6.03%~-58% / -0.2%~-24% / 0%~-5% degradation for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively;
+- Compared with monitoring Case 1 with ground-truth CSI format of R16 eType II CB with new parameter of around 1600bits CSI payload size, 2 sources observe -16.35%~-66% / -0.4%~-24% / 0%~-24% degradation for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively.
+- Note: For Case 2-1 subject to generalization Case 2 for the proxy model, 2 sources observe -1.77%~-37.42% / -1.07%~-23.93% / -0.16%~-14% compared with generalization Case 1 with the same testing scenario.
+- Note: For Case 2-2, 1 source observes $KPI_{Diff}$ as 61%~72.1% / 91.2%~96.6% / 99.2%~99.75% under generalization Case 1 for the proxy model, and 60%~71.3% / 90.4%~99.3% / 99%~100% under generalization Case 3 for the proxy model, for $KPI_{th\_1}=0.02/0.05/0.1$ , respectively.
+- Note: for Case 2-1, 1 source observes that if different model backbone is adopted for proxy model as compared to the NW part model, it has negative impact to the monitoring performance.
+- Note: for the complexity and overhead analysis:
+ - Case 2-1/Case 2-2 have smaller air-interface overhead for UE report for monitoring compared with Case 1. Overhead of proxy model from LCM perspective, if any, is not evaluated.
+ - The complexity aspect for Case 1, Case 2-1 and Case 2-2 is not evaluated.
+- Note: "Generalization Case 1" means the proxy model is trained based on training dataset from one Scenario#B, and then tested for monitoring on a dataset from the same Scenario#B. "Generalization Case 2" means the proxy model is trained based on training dataset from one Scenario#A, and then tested for monitoring on a dataset from a different Scenario#B. "Generalization Case 3" means the proxy model is trained based on mixing datasets from multiple scenarios including Scenario#B, and then tested for monitoring on the dataset from Scenario#B.
+- Note: two sources observed averaging on the test samples improves the monitoring accuracy.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Time independency is assumed over the test samples for monitoring.
+- Precoding matrix is used as the model input.
+- 1-on-1 joint training is assumed.
+- The performance metric is monitoring accuracy for Layer 1.
+- Note: Results refer to Table 5.22 of R1-2308343.
+
+##### ***Quantization methods, quantization awareness for training***
+
+For the comparison of *quantization methods* for CSI compression, *quantization non-aware training* (Case 1) is in general inferior to the *quantization aware training* (Case 2-1/2-2), and may lead to lower performance than the benchmark:
+
+- For scalar quantization, compared with benchmark,
+ - -2.4%~-43.2% degradations are observed for quantization non-aware training (Case 1) from 6 sources.
+ - 3.9%~8.64% gains are observed for quantization aware training with fixed/pre-configured quantization method/parameters (Case 2-1) from 5 sources, which are 17.3%~83.2% gains over quantization non-aware training (Case 1) from 5 sources and 7.56%~11.55% gains over quantization non-aware training (Case 1) from 1 source.
+ - Note: 0.72% gains are observed for Case 2-1 from 1 source due to SQ parameter chosen without matching latent distribution, which achieves 13.9% gains over Case 1.
+
+- 8.91% gains are observed for quantization aware training with jointly updated quantization method/parameters (Case 2-2) from 1 source, which are 23.1% gains over quantization non-aware training (Case 1) from 1 source.
+- For vector quantization, compared with benchmark,
+ - -2%~10% degradations are observed for quantization non-aware training (Case 1) from 1 source.
+ - 5.64%~7.55% gains are observed for quantization aware training with fixed/pre-configured quantization method/parameters (Case 2-1) from 3 sources, which are 3%~21.6% gains over quantization non-aware training (Case 1) from 3 sources.
+ - 4.6%~13.01% gains are observed for quantization aware training with jointly updated quantization method/parameters (Case 2-2) from 7 sources, which are 10.7%~30% gains over quantization non-aware training (Case 1) from 4 sources and 3.66%~9.8% gains over quantization non-aware training (Case 1) from 2 sources.
+- In general, Case 2-2 outperforms Case 2-1 with 0.46%~5.1% gains, as observed by 6 sources.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS for Layer 1.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.14 of R1-2308342.
+
+##### ***Quantization methods, quantization format***
+
+For the comparison of *quantization methods* for CSI compression, in general vector quantization (VQ) has comparable performance with scalar quantization (SQ):
+
+- For SQ and VQ under the same training case, it is
+ - observed by 3 sources that VQ under Case 2-1 has -1%~4.5% degradation over SQ under Case 2-1,
+ - observed by 1 source that VQ under Case 2-1 has 1.1% gain over SQ under Case 2-1, and
+ - observed by 3 sources that VQ under Case 2-2 has 0.7%~3.8% gain over SQ under Case 2-2.
+ - Note: VQ under Case 2-1 has 8% gains over SQ under Case 2-1 as observed from 1 source due to SQ parameter chosen without matching latent distribution.
+- For SQ and VQ across training cases, it is
+ - observed by 6 sources that VQ under Case 2-2 has 0.46%~4% gain over SQ under Case 2-1, and
+ - observed by 1 source that VQ under Case 2-2 has -1.3% degradation over SQ under Case 2-1.
+ - observed by 1 source that VQ under Case 2-1 has -2.9%~6.4% degradation over SQ under Case 2-2.
+- Note: in general, more companies observing gain of VQ over SQ than companies observing loss.
+- Note: it is observed by 1 source that combined SQ and VQ under Case 2-2 has minor gain of 0.2% over VQ only under Case 2-2.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS for Layer 1.
+- Benchmark is Rel-16 Type II codebook.
+- Note: Results refer to Table 5.15 of R1-2308342.
+
+##### ***High resolution ground-truth CSI for training***
+
+For the evaluation of high-resolution quantization of the ground-truth CSI for the training of CSI compression, compared to the upper-bound of Float32, quantized high resolution ground-truth CSI can achieve significant overhead reduction with minor performance loss if the parameters are appropriately selected.
+
+- For high resolution scalar quantization,
+ - Float16 achieves 50% overhead reduction and -0.6% or less performance loss from 2 sources
+ - 8 bits scalar quantization achieves 75% overhead reduction and -0.14%~0.9% performance loss from 2 sources
+- For high resolution R16 eType II-like quantization,
+ - R16 eType II CB with legacy parameters can achieve significant overhead reduction while with performance loss compared to Float32, wherein:
+ - PC#6 achieves around 99% overhead reduction with -1.4% ~1.7% performance loss from 2 sources, and -3%~9.5% performance loss from 4 sources.
+ - PC#8 achieves around 98% overhead reduction with 0% ~1.7% performance loss from 3 sources, and -2.9%~5.5% performance loss from 5 sources.
+ - For R16 eType II CB with new parameters:
+ - R16 eType II CB with new parameter of 1000-1400bits CSI payload size achieves 95%~97.5% overhead reduction (3~4.1 times overhead compared to PC8) with performance gain of 0.7%~4.3% over PC#8 from 4 sources.
+ - R16 eType II CB with new parameter of 1500-2100bits CSI payload size achieves 94%~96.2% overhead reduction (4.8~6.1 times overhead compared to PC8) with performance gain of 1.3%~5.4% over PC#8 from 3 sources.
+ - Note: it is observed by 1 source that using R16 eType II-like quantization with legacy PC may achieve close performance to Float32 by dataset dithering.
+- Note: the new parameters include at least one from the follows:
+ - L= 8, 10, 12;
+ - pv = 0.8, 0.9, 0.95;
+ - reference amplitude = 6 bits, 8 bits; differential amplitude = 4bits; phase = 5 bits, 6 bits;
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix is used as the model input.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS for Layer 1.
+- Note: Results refer to Table 5.18 of R1-2308342.
+
+#### **6.2.2.2 Generalization evaluations for CSI compression**
+
+##### ***Generalization over deployment scenarios***
+
+From the results for the *generalization verification* of AI/ML based CSI compression *over various deployment scenarios* compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain deployment scenario#B and applied for inference with a same deployment scenario#B,
+
+- For *generalization Case 2*, generalized performance may be achieved for certain combinations of deployment scenario#A and deployment scenario#B but not for others:
+ - If deployment scenario#A is UMi & deployment scenario#B is UMa, deployment scenario#A is UMa & deployment scenario#B is UMi, or deployment scenario#A is UMa & deployment scenario#B is InH:
+ - 14 sources observe that generalized performance can be achieved:
+ - For deployment scenario#A is UMi & deployment scenario#B is UMa, 9 sources observe less than -1.6% degradation or positive gain.
+ - For deployment scenario#A is UMa & deployment scenario#B is UMi, 10 sources observe less than -1.5% degradation or positive gain.
+ - For deployment scenario#A is UMa & deployment scenario#B is InH, 2 sources observe less than -0.6% degradation or positive gain.
+ - 13 sources observe that moderate/significant degradations are suffered under generalization Case 2:
+ - For deployment scenario#A is UMi & deployment scenario#B is UMa, 10 sources observe -1.69%~21.1% degradation.
+ - For deployment scenario#A is UMa & deployment scenario#B is UMi, 9 sources observe -1.7%~8.1% degradation.
+ - For deployment scenario#A is UMa & deployment scenario#B is InH, 3 sources observe -1.74%~31.6% degradation.
+ - If deployment scenario#A is InH & deployment scenario#B is UMa/UMi, significant performance degradations are observed under generalization Case 2:
+ - For deployment scenario#A is InH & deployment scenario#B is UMa, 5 sources observe -5.55%~ -27.7% degradation.
+ - For deployment scenario#A is InH & deployment scenario#B is UMi, 3 sources observe -8.63%~20% degradation
+- For *generalization Case 3*, generalized performance of the AI/ML model can be achieved (0%~4% loss or positive gain) for deployment scenario#B subject to any of UMa, UMi, and InH, if the training dataset is constructed with data samples subject to multiple deployment scenarios including deployment scenario#B, as observed by 15 sources.
+ - Minor loss (0%~1.6%) are observed by 15 sources.
+ - Moderate loss (-1.69%~4%) are observed by 8 sources.
+ - Positive gains are observed by 10 sources.
+ - Note: Significant degradations of up to -6.7% are observed by 2 sources for deployment scenario#B subject to UMa, and by 2 sources for deployment scenario#B subject to UMi.
+ - Note: For generalization Case 2, if deployment scenario#A is UMi & deployment scenario#B is InH, 3 sources observe different trends, where significant performance degradations of -27.8%~32.86% are observed by two sources, while moderate performance degradations of -1.44%~2.41% are observed by another source.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+
+- The performance metric is SGCS in linear value for layer 1/2.
+- Note: Results refer to Table 5.1 of R1-2308340.
+
+##### ***Generalization over UE distributions***
+
+For the *generalization verification* of AI/ML based CSI compression *over various UE distributions* compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain UE distribution#B and applied for inference with a same UE distribution#B,
+
+- For generalization Case 2, generalized performance may be achieved for some certain combinations of UE distribution#A and UE distribution#B but not for others
+ - If UE distribution#A is Outdoor & UE distribution#B is Indoor, 7 sources observe that moderate/significant degradations of -1.9%~ -11.5% degradation are suffered,
+ - Note: 1 source observes minor degradation of -0.48%~ -0.93% for partial cases.
+ - If UE distribution#A is Indoor & UE distribution#B is Outdoor, 7 sources observe minor loss of less than -1.11% degradation or positive gain
+- For generalization Case 3, generalized performance of the AI/ML model can be achieved (0%~ -1.54% loss or positive gain) for UE distribution#B subject to any of Outdoor and Indoor, if the training dataset is constructed with data samples subject to multiple UE distributions including UE distribution#B, as observed by 6 sources.
+ - Minor loss (0%~ -1.54%) are observed by 5 sources.
+ - Positive gains are observed by 4 sources.
+ - Note: Moderate degradations of up to -3.9% are still observed by 2 sources for UE distribution#B subject to Indoor.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS in linear value for layer 1/2.
+- Note: Results refer to Table 5.9 of R1-2308340.
+
+##### ***Generalization over carrier frequencies***
+
+For the *generalization verification* of AI/ML based CSI compression *over various carrier frequencies* compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain carrier frequency#B and applied for inference with a same carrier frequency#B,
+
+- For generalization Case 2, generalized performance may be achieved in general
+ - If carrier frequency#A is 3.5/4GHz & carrier frequency#B is 2GHz, 3 sources observe generalized performance of less than -0.8% degradation.
+ - If carrier frequency#A is 2GHz & carrier frequency#B is 3.5/4GHz, 5 sources observe generalized performance of less than -1.06% degradation or positive gain.
+ - Note: 2 sources observes significant degradations up to -6.6%.
+- For generalization Case 3, generalized performance of the AI/ML model may be achieved (0%~ -1.2% loss or positive gain) for carrier frequency#B subject to any of 2GHz and 3.5/4GHz, if the training dataset is constructed with data samples subject to multiple carrier frequencies including carrier frequency#B, as observed by 4 sources.
+ - Minor loss (0%~ -1.2%) are observed by 4 sources.
+ - Positive gains are observed by 4 sources.
+
+- Note: Significant degradations of up to -4.9% are still observed by 1 source for carrier frequency#B subject to 3.5/4GHz
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS in linear value for layer 1.
+- Antenna layouts are assumed as the same over the different frequency carriers.
+- Note: Results refer to Table 5.2 of R1-2308340.
+
+##### ***Generalization over TxRU mappings***
+
+For the generalization verification of AI/ML based CSI compression over various TxRU mappings, compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain TxRU mapping#B and applied for inference with a same TxRU mapping#B,
+
+- For generalization Case 2, significant degradations are suffered in general from the perspective of the layouts of antenna ports, as observed by 2 sources:
+ - For TxRU mapping#A is [2,8,2] & TxRU mapping#B is [4,4,2] or TxRU mapping#A is [8,2,2] & TxRU mapping#B is [4,4,2], 2 sources observe -13%~-36.1% degradation.
+ - For TxRU mapping#A is [4,4,2] & TxRU mapping#B is [2,8,2] or TxRU mapping#A is [8,2,2] & TxRU mapping#B is [2,8,2], 2 sources observe -7%~-23.6% degradation.
+ - For TxRU mapping#A is [4,4,2] & TxRU mapping#B is [8,2,2] or TxRU mapping#A is [2,8,2] & TxRU mapping#B is [8,2,2], 1 source observes -19%~-27% degradation.
+- For generalization Case 2, generalized performance may be achieved for some certain combinations of TxRU mapping#A and TxRU mapping#B but not for others, from the perspective of the layouts of antenna element mapping, as observed by 2 sources:
+ - For TxRU mapping#A is 8x8x2 & TxRU mapping#B is 2x8x2, 2 sources observe minor/moderate degradation of -0.6%~-2.5%.
+ - For TxRU mapping#A is 2x8x2 & TxRU mapping#B is 8x8x2, 1 source observes moderate degradation of -3%.
+- For generalization Case 3, generalized performance of the AI/ML model can be achieved (0%~-4.4% loss or positive gain) for TxRU mapping#B subject to any of [2,8,2], [4,4,2], and [8,2,2] from the perspective of the layouts of antenna ports, or subject to any of 8x8x2 and 2x8x2 from the perspective of the layouts of antenna element mapping, if the training dataset is constructed with data samples subject to TxRU mappings including TxRU mapping#B, as observed by 4 sources.
+ - Minor loss (0%~-2%) are observed by 4 sources.
+ - Moderate loss (-2.5%~-4.4%) are observed by 1 source.
+ - Positive gains are observed by 1 source.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS in linear value for layer 1.
+
+- [x,y,z] for TxRU mapping: Vertical port number, Horizontal port number, polarization
+- AxBxC for TxRU mapping: AxBxC antenna elements virtualized to [2,8,2]
+- Note: Results refer to Table 5.19 of R1-2308342.
+
+#### 6.2.2.3 Scalability evaluations for CSI compression
+
+##### *Scalability over CSI payload sizes*
+
+For the scalability verification of AI/ML based CSI compression *over various CSI payload sizes*, compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain CSI payload size#B and applied for inference with a same CSI payload size#B,
+
+- For generalization Case 2, significant performance degradations are observed in general, as -5.3%~-14.7% degradations are observed by 2 sources.
+- Generalized performance of the AI/ML model can be achieved (-0%~-5.9%loss) under generalization Case 3 for the inference on CSI payload size#B, if the training dataset is constructed with data samples subject to multiple CSI payload sizes including CSI payload size#B, and an appropriate scalability solution is performed to scale the dimension of the AI/ML model, shown by 13 sources (10 sources showing -0%~-2.2% loss, 7 sources showing -2.3%~-5.9% loss, 5 sources showing positive gain). The scalability solution is adopted as follows:
+ - Pre/post-processing of truncation/padding, adopted by 6 sources, showing -0% ~-5.9% loss or positive gain.
+ - Various quantization granularities, adopted by 1 source, showing -0.7% loss or positive gain.
+ - Adaptation layer in the AL/ML model, adopted by 6 sources, showing -0%~-4.78% loss or positive gain.
+ - Note: Significant degradations of up to -14.22% are still observed by 2 sources for generalization Case 3.
+- Generalized performance of the AI/ML model can also be achieved by finetuning models on CSI payload size#B, showing loss 0%~-2.2% by 2 sources
+
+The above results are based on the following assumptions:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- Input/output scalability dimension Case 3 is adopted: A pair of CSI generation part with scalable input/output dimensions and CSI reconstruction part with scalable output and/or input dimensions.
+- The performance metric is SGCS in linear value for layer 1/2.
+- Note: Results refer to Table 5.10 of R1-2308340.
+
+##### *Scalability over bandwidths*
+
+For the scalability verification of AI/ML based CSI compression *over various bandwidths*, compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain bandwidth#B and applied for inference with a same bandwidth#B,
+
+- For generalization Case 2, if bandwidth#A is 20MHz & bandwidth#B is 10MHz, or bandwidth#A is 10MHz & bandwidth#B is 20MHz, or bandwidth#A is 10MHz & bandwidth#B is 5MHz:
+ - 2 sources observe that generalized performance can be achieved:
+ - For bandwidth#A is 20MHz & bandwidth#B is 10MHz, 1 source observes less than -1.28% degradation.
+ - For bandwidth#A is 10MHz & bandwidth#B is 20MHz, 2 sources observe less than -1.1% degradation.
+ - 1 source observe that moderate/significant degradations are suffered under generalization Case 2:
+ - For bandwidth#A is 10MHz & bandwidth#B is 5MHz, 1 source observes larger than -2.5% degradation.
+
+- For generalization Case 3, 3 sources observe that generalized performance of the AI/ML model can be achieved (0%~2.97% loss) for bandwidth#B subject to each of 10MHz/52RB and 20MHz and 48RB, if the training dataset is constructed with data samples subject to multiple bandwidths including bandwidth#B.
+- Minor loss (0%~1.7%) are observed by 2 sources.
+- Moderate loss (-1.91%~2.97%) are observed by 2 sources.
+- Positive gains are observed by 2 sources.
+- Note: Significant loss (-5.4%) is observed by 1 source.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS in linear value for layer 1/2.
+- Note: Results refer to Table 5.31 of R1-2308344.
+
+##### *Scalability over Tx port numbers*
+
+For the *scalability verification* of AI/ML based CSI compression *over various Tx port numbers* compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain Tx port number#B and applied for inference with a same Tx port number#B,
+
+- For generalization Case 2, significant performance degradations are observed in general, if Tx port number#A is 32 & Tx port number#B is 16, as -3.37%~21.8% degradations are observed by 4 sources
+- For generalization Case 3, generalized performance of the AI/ML model can be achieved (0%~3.94% loss or positive gains) for Tx port number#B subject to any of 16 and 32, if the training dataset is constructed with data samples subject to multiple Tx port numbers including Tx port number#B, and an appropriate scalability solution is performed to scale the dimension of the AI/ML model, as observed by 9 sources.
+ - Minor loss (0%~1.6%) are observed by 8 sources.
+ - Moderate loss (-2.02%~3.94%) are observed by 4 sources.
+ - Positive gains are observed by 5 sources.
+ - Note: Significant degradations of up to -9.76% are still observed by 2 sources for deployment scenario#B subject to 32 ports, and for deployment scenario#B subject to 16 ports
+ - Note: Pre/post-processing of truncation/padding is adopted by 6 sources, and adaptation layer in the AL/ML model is adopted by 1 source.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- 1-on-1 joint training is assumed.
+- The performance metric is SGCS in linear value for layer 1/2/3/4.
+- Note: Results refer to Table 5.3 of R1-2308340.
+
+#### 6.2.2.4 Multi-vendor joint training for CSI compression
+
+##### *1 NW part model to M>1 UE part models*
+
+For the evaluation of Type 2 training between 1 NW part model and $M > 1$ separate UE part models (Case 2), as compared to joint training between 1 NW part model and the 1 UE part model,
+
+- 7 sources observe minor degradation of -0%~1.67% or positive gain;
+- 3 sources observe moderate degradation of -2.5%~6.5%.
+- Note: among the above sources, 5 sources adopt simultaneous training, while 1 source adopts sequential training starting with NW side training.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1.
+- Same pair of NW part model and UE part model between 1-on-1 joint training and Type 2 training.
+- $M = 2, 3, \text{ or } 4$ are considered.
+- Note: Results refer to Table 5.23 of R1-2308343.
+
+##### ***1 UE part model to $N > 1$ NW part models***
+
+For the evaluation of Type 2 training between 1 UE part model and $N > 1$ separate NW part models (Case 3), as compared to joint training between 1 NW part model and the 1 UE part model,
+
+- 2 sources observe minor degradation of -0%~0.8% or positive gain;
+- 1 source observe moderate degradation of -1.4%~4.2%.
+- Note: among the above sources, 1 source adopts simultaneous training.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1.
+- Same pair of NW part model and UE part model between 1-on-1 joint training and Type 2 training.
+- $N = 2, 3, \text{ or } 4$ are considered.
+- Note: Results refer to Table 5.24 of R1-2308343.
+
+#### **6.2.2.5 Separate training for CSI compression**
+
+##### ***NW first training, 1 NW part model to 1 UE part model, same backbone***
+
+For the evaluation of Type 3 *NW first separate training with dataset sharing* manner for CSI compression for the pairing of 1 NW to 1 UE (Case 1), as compared to 1-on-1 joint training between the NW part model and the UE part model,
+
+- For the NW first separate training case where the *same backbone* is adopted for both the NW part model and the UE part model, minor degradation is observed for both the cases where the shared output of the Network side CSI generation part is before or after quantization:
+ - For the case where the shared output of the Network side CSI generation part is after quantization, 9 sources observe -0%~0.5% degradation, 10 sources observe -0.5%~1% degradation, and 2 sources observe -1%~1.3% degradation.
+ - For the case where the shared output of the Network side CSI generation part is before quantization, 6 sources observe -0%~0.8% degradation, and 1 source observes -1%~1.5% degradation.
+
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement "the set of information includes the input and output of the Network side CSI generation part, or includes the output of the Network side CSI generation part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1/2.
+- Same size of training dataset for benchmark, NW part training and the UE part training
+- Same pair of NW part model and UE part model between 1-on-1 joint training and NW first separate training.
+- Quantization/dequantization method/parameters between NW side and UE side are aligned.
+- Note: Results refer to Table 5.16 of R1-2308342.
+
+##### ***Impact of shared dataset under 1 NW part model to 1 UE part model***
+
+For the evaluation of Type 3 NW/UE first separate training with dataset sharing manner for CSI compression for the pairing of 1 NW to 1 UE (Case 1), as compared to the case where the same set of dataset is applied for training the NW part model and training the UE part model, if the dataset#2 applied for training the UE/NW part model is a subset of the dataset#1 applied for training the NW/UE part model,
+
+- If the dataset#2 is appropriately selected, minor additional performance degradation can be achieved, as -0%~0.59% gap is observed from 3 sources.
+- If the dataset#2 has a significantly reduced size compared to dataset#1, moderate/significant additional performance degradation may occur, as -0.6%~4.83% gap is observed from 4 sources.
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement where "the set of information includes the input and output of the Network side CSI generation part, or includes the output of the Network side CSI generation part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1/2.
+- Note: Results refer to Table 5.4 of R1-2308340.
+
+##### ***NW first training, 1 NW part model to 1 UE part model, different backbones***
+
+For the evaluation of Type 3 NW first separate training with dataset sharing manner for CSI compression, for the pairing of 1 NW to 1 UE (Case 1), as compared to 1-on-1 joint training between the NW part model and the UE part model,
+
+- For the NW first separate training case where different backbones are adopted for the NW part model and the UE part model, more degradations are observed in general than the situation where the same backbone is adopted for the NW part model and the UE part model.
+ - For the case where the shared output of the Network side CSI generation part is after quantization, 3 sources observe minor degradation of -0%~1.02%, and 3 sources observe moderate degradation of -1.46%~5.1%.
+ - For the case where the shared output of the Network side CSI generation part is before quantization, 2 sources observe minor degradation of -0%~0.1%, 1 source observes moderate degradation of -2.03%.
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement where "the set of information includes the input and output of the Network side CSI generation part, or includes the output of the Network side CSI generation part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1/2.
+- Same size of training dataset for benchmark, NW part training and the UE part training
+- Same pair of NW part model and UE part model between 1-on-1 joint training and NW first separate training.
+- Quantization/dequantization method/parameters between NW side and UE side are aligned.
+- Note: Results refer to Table 5.16 of R1-2308342.
+
+##### ***NW first training, 1 UE part model to $N > 1$ NW part models***
+
+For the evaluation of Type 3 NW first separate training with dataset sharing manner for CSI compression, for the pairing between 1 UE part model and $N > 1$ separate NW part models (Case 3), when taking 1-on-1 joint training between the NW part model and the UE part model as benchmark, larger performance loss is observed in general than the case of NW first separate training with 1 UE part model and 1 NW part model pairing (Case 1):
+
+- 6 sources observe minor loss of -0%~ -1.6% compared to the 1-on-1 joint training.
+- 3 sources observe moderate loss of -1.9%~ -6.64% compared to the 1-on-1 joint training.
+- 5 sources observe significant loss of -37.9%~ -87% compared to the 1-on-1 joint training.
+- Note: as opposed to companies which observe significant loss, the minor loss observed by other companies may due to the fact that special handling (e.g., adaptation layer) is performed to pair with $N > 1$ NW part models during the training at the UE side.
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement, where "the set of information includes the input and output of the Network side CSI generation part, or includes the output of the Network side CSI generation part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1.
+- Same size of training dataset for benchmark, NW part training and the UE part training
+- Same pair of NW part model and UE part model between 1-on-1 joint training and NW first separate training.
+- Quantization/dequantization method/parameters between NW side and UE side are aligned.
+- $N = 2, 3$ , or 4 are considered.
+- Note: Results refer to Table 5.20 of R1-2308342.
+
+##### ***UE first training, 1 NW part model to 1 UE part model, same backbone***
+
+For the evaluation of Type 3 UE first separate training with dataset sharing manner for CSI compression for the pairing of 1 NW to 1 UE (Case 1), as compared to 1-on-1 joint training between the NW part model and the UE part model,
+
+- For the UE first separate training case where the same backbone is adopted for both the UE part model and the NW part model, minor degradation is observed in general for both the cases where the shared input of the UE side CSI reconstruction part is before or after quantization:
+ - For the case where the shared input of the UE side CSI reconstruction part is after quantization, 9 sources observe -0%~ -0.42% degradation, 2 sources observe -0.7%~ -0.9% degradation, and 3 sources observe -1.05%~ -1.8% degradation.
+ - For the case where the shared input of the UE side CSI reconstruction part is before quantization, 3 sources observe -0%~ -0.8% degradation, and 2 sources observe -1.3%~ -2.9% degradation.
+
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement where "the set of information includes the input and label of the UE side CSI reconstruction part, or includes the input of the UE side CSI reconstruction part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1/2.
+- Same size of training dataset for benchmark, NW part training and the UE part training
+- Same pair of NW part model and UE part model between 1-on-1 joint training and UE first separate training.
+- Quantization/dequantization method/parameters between NW side and UE side are aligned.
+- Note: Results refer to Table 5.17 of R1-2308342.
+
+##### ***UE first training, 1 NW part model to 1 UE part model, different backbones***
+
+For the evaluation of Type 3 UE first separate training with dataset sharing manner for CSI compression, for the pairing of 1 NW to 1 UE (Case 1), as compared to 1-on-1 joint training between the NW part model and the UE part model,
+
+- For the UE first separate training case where different backbones are adopted for the NW part model and the UE part model, more degradations are observed in general than the situation where the same backbone is adopted for the NW part model and the UE part model.
+ - For the case where the shared input of the UE side CSI reconstruction part is after quantization, 5 sources observe minor degradation of -0.23%~-1.07%, and 1 source observes moderate degradation of -1.74%~-1.88%.
+ - For the case where the shared input of the UE side CSI reconstruction part is before quantization, 1 source observes moderate degradation of -1.58%~-2.73%.
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement, where "the set of information includes the input and label of the UE side CSI reconstruction part, or includes the input of the UE side CSI reconstruction part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1/2.
+- Same size of training dataset for benchmark, NW part training and the UE part training
+- Same pair of NW part model and UE part model between 1-on-1 joint training and UE first separate training.
+- Quantization/dequantization method/parameters between NW side and UE side are aligned.
+- Note: Results refer to Table 5.17 of R1-2308342.
+
+##### ***UE first training, $M > 1$ UE part models to 1 NW part model***
+
+For the evaluation of Type 3 UE first separate training with dataset sharing manner for CSI compression, for the pairing between $M > 1$ separate UE part models and 1 NW part model (Case 2), when taking 1-on-1 joint training between the NW part model and the UE part model as benchmark, larger performance loss is observed in general than the case of UE first separate training with 1 UE part model and 1 NW part model pairing (Case 1):
+
+- 8 sources observe minor loss of -0%~-1.82% compared to 1-on-1 joint training.
+- 4 sources observe moderate loss of -2.17%~-4.96% compared to 1-on-1 joint training.
+- 2 sources observe significant loss of -11.56%~-73.7% compared to 1-on-1 joint training.
+
+- Note: 1 source observes other UE first separate training implementations may achieve better performance.
+- Note: the dataset sharing behaviour from above sources follows the example of the agreement, where "the set of information includes the input and output of the Network side CSI generation part, or includes the output of the Network side CSI generation part only".
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Precoding matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS for Layer 1.
+- Same size of training dataset for benchmark, NW part training and the UE part training
+- Same pair of NW part model and UE part model between 1-on-1 joint training and UE first separate training.
+- Quantization/dequantization method/parameters between NW side and UE side are aligned.
+- $M=2, 3, \text{ or } 4$ are considered.
+- Note: Results refer to Table 5.25 of R1-2308343.
+
+#### 6.2.2.6 Basic performance for CSI prediction
+
+The complexity values in terms of FLOPs and number of parameters of AI/ML models adopted in the evaluations of CSI prediction are summarized in Figure 6.2.2.6-1.
+
+- Results refer to Table 2 of clause 7.3, R1-2310450.
+
+
+
+Figure 6.2.2.6-1: Complexity of AI/ML models from evaluation results in terms of FLOPs and number of parameters for CSI prediction. The plot is a scatter plot on a log-log scale. The x-axis is 'Number of parameters/M' ranging from 1 to 100. The y-axis is 'FLOPs/M' ranging from 0.01 to 10000. There are approximately 15 data points scattered across the plot, showing a general trend where models with more parameters tend to have higher FLOPs, though there is significant variation.
+
+**Figure 6.2.2.6-1: Complexity of AI/ML models from evaluation results in terms of FLOPs and number of parameters for CSI prediction.**
+
+##### *SGCS performance, impact of input type*
+
+For the AI/ML based CSI prediction, compared with the benchmark of the nearest historical CSI:
+
+- spatial consistency is not adopted in 15 sources, wherein:
+ - 15 sources observe the gain of 0.46% ~ 44.8% using raw channel matrix as input, wherein
+ - 4 sources observe the gain of 0.46%~6.3%.
+ - 14 sources observe the gain of 7.57%~26.47%.
+ - 5 sources observe the gain of 29.03%~44.8%.
+ - 4 sources observe the gain of 2.24% ~ 19.4% using precoding matrix as input, which is in general worse than using raw channel matrix as input
+
+- spatial consistency is adopted in 4 sources, all of which use raw channel matrix as input, wherein
+ - 3 sources observe the gain of 1.7%~35.51%.
+ - 1 source observe the gain of 76.6%.
+ - 1 source observe the loss of -5.5%.
+
+The above results are based on the following assumptions:
+
+- The observation window considers to start as early as 15ms~50ms.
+- A future 4ms or 5ms instance from the prediction output is considered for calculating the metric.
+- UE speed includes 10km/h, 30km/h, and 60km/h. The same fixed UE speed is assumed for both training and inference.
+- The performance metric is SGCS in linear value for layer 1.
+- Note: Results refer to Table 5.26 of R1-2308344.
+
+##### ***SGCS performance, impact of UE speed***
+
+For the AI/ML based CSI prediction, compared to the Benchmark#1 of the nearest historical CSI, *in terms of SGCS*, from UE speed perspective, in general the gain of AI/ML based solution is related with the UE speed:
+
+- For 10km/h UE speed, 6 sources observe 2.4%~12.5% gain (2.4%~12.5% gain for 5 sources who do not adopt spatial consistency, and 8.7% gain for 1 source who adopts spatial consistency), 1 source observes 21.93% gain (who does not adopt spatial consistency).
+- For 30km/h UE speed, 1 source observes loss of -5.5% (who adopts spatial consistency), 3 sources observe 6%~10.43% gain (who do not adopt spatial consistency), 8 sources observe 12.65%~33% gain (14.65%~33% gain for 7 sources who do not adopt spatial consistency, and 12.65% gain for 1 source who adopts spatial consistency), and 3 sources observe 41.75%~ 76.6% gain (41.75%~ 44.8% gain for 2 sources who do not adopt spatial consistency, and 76.6% gain for 1 source who adopts spatial consistency), which are in general larger than 10km/h UE speed.
+- For 60km/h UE speed, 3 sources observe 0.46%~2.6% gain (0.46%~2.3% gain for 2 sources who do not adopt spatial consistency, and 1.7%~2.6% gain for 1 source who adopts spatial consistency), 7 sources observe 9.1%~20.6% gain (9.1%~20.6% gain for 6 sources who do not adopt spatial consistency, and 13.8% gain for 1 source who adopts spatial consistency), 1 source observe 29.03% gain, which are in general smaller than 30km/h UE speed.
+
+The above results are based on the following assumptions:
+
+- The observation window considers to start as early as 15ms~50ms.
+- A future 4ms or 5ms instance from the prediction output is considered for calculating the metric.
+- Raw channel matrix is considered as model input
+- The performance metric is SGCS in linear value for layer 1.
+- No post processing is considered.
+- The same fixed UE speed is assumed for both training and inference.
+- Note: Results refer to Table 5.27 of R1-2308344.
+
+##### ***SGCS performance, impact of observation window***
+
+For the AI/ML based CSI prediction, compared to the Benchmark#1 of the nearest historical CSI, *in terms of SGCS*, from observation window length perspective, in general the gain of AI/ML based solution is slightly increased with the increase of the length for the observation window:
+
+- When the observation window is increased from 5/5ms to 8/5ms, the gain over benchmark is increased by 0.28%~2.19%, as observed by 2 sources.
+
+- When the observation window is increased from 5/5ms to 15/5ms, the gain over benchmark is increased by 5.59%~10.32%, as observed by 1 source.
+- When the observation window is increased from 4/5ms to 8/5ms and 10/5ms, the gain over benchmark is increased by 0.96%~4.23% and 1%~4.42%, respectively, as observed by 2 sources.
+
+The above results are based on the following assumptions:
+
+- The UE speed is 30km/h.
+- A future 4ms or 5ms instance from the prediction output is considered for calculating the metric.
+- Raw channel matrix is considered as model input
+- The performance metric is SGCS in linear value for layer 1.
+- No post processing is considered.
+- Note: Results refer to Table 5.32 of R1-2308344.
+
+##### ***SGCS performance, impact of prediction window***
+
+- For the AI/ML based CSI prediction, compared to the Benchmark#1 of the nearest historical CSI, *in terms of SGCS*, from prediction window length perspective, in general the gain of AI/ML based solution is related with the prediction length in terms of the distance to the applicable time of the predicted CSI:
+- When the prediction length is increased from 10ms to 15ms, the gain over benchmark is reduced (gap from -1.13%~-51%), as observed by 3 sources.
+- When the prediction length is increased from 2.5ms/3ms to 5ms, the gain over benchmark is increased (gap from +5.85%~+13%), as observed by 2 sources.
+- When the prediction length is increased from 5ms to 10ms, 5 sources observe the gain over benchmark is reduced (gap from -1%~-12.1%) while 2 sources observe the gain over benchmark is increased (+11.65%~+45.5%).
+
+The above results are based on the following assumptions:
+
+- The UE speed is 30km/h.
+- The observation window considers to start as early as 15ms~50ms.
+- Raw channel matrix is considered as model input.
+- The performance metric is SGCS in linear value for layer 1.
+- No post processing is considered.
+- Note: Results refer to Table 5.33 of R1-2308344.
+
+##### ***Mean UPT***
+
+For the AI/ML based CSI prediction, in terms of mean UPT, gains are observed compared to both Benchmark#1 of the nearest historical CSI and Benchmark#2 of a non-AI/ML based CSI prediction approach:
+
+- Compared to the benchmark of the nearest historical CSI:
+ - For FTP traffic:
+ - 4 sources observe 1.2%~4.9% gain;
+ - 2 sources observe 5.3%~10.58% gain;
+ - 2 sources observe 15.1%~23.5% gain.
+ - 1 source observes loss of -1.3%~-13.8%.
+ - For full buffer traffic:
+
+- 1 source observes 2%~3% gain;
+- 2 sources observe 7.6%~15.6% gain.
+- Compared to the benchmark of an auto-regression/Kalman filter based CSI prediction:
+ - For FTP traffic:
+ - 3 sources observe 0.7%~7.0% gain;
+ - 2 sources observe loss of -0.1%~2.4%.
+ - 1 source observe loss of -3%~17%.
+ - For full buffer traffic:
+ - 2 sources observes 0.6%~2.78% gain.
+ - 1 source observes 8.1%~11.5% gain.
+
+The above results are based on the following assumptions:
+
+- The same fixed UE speed of 30km/h or 60km/h is assumed for both training and inference
+- The observation window considers to start as early as 15ms~50ms.
+- A future 4ms or 5ms instance from the prediction output is considered for calculating the metric.
+- Raw channel matrix is considered as model input
+- The performance metric is mean UPT for Max rank 1.
+- No post processing is considered.
+- Note: Results refer to Table 5.28 of R1-2308344.
+
+###### 5% UPT
+
+For the AI/ML based CSI prediction, in terms of 5% UPT, gains are observed compared to both Benchmark#1 of the nearest historical CSI and Benchmark#2 of a non-AI/ML based CSI prediction approach:
+
+- Compared to the benchmark of the nearest historical CSI:
+ - For FTP traffic:
+ - 4 sources observe 1% ~9.7% gain;
+ - 5 sources observe 10%~26.4% gain;
+ - 1 source observes loss of -11.6%~14%;
+ - For full buffer traffic:
+ - 3 sources observe 3.5%~35.3% gain;
+- Compared to the benchmark of an auto-regression/Kalman filter based CSI prediction:
+ - For FTP traffic:
+ - 3 sources observe 0.18%~17.58% gain;
+ - 1 source observes -8.2%~12.4% degradation;
+ - For full buffer traffic:
+ - 1 source observes 6.7% ~15.4% gain.
+ - 1 source observes -2% degradation
+
+The above results are based on the following assumptions:
+
+- The same fixed UE speed of 30km/h or 60km/h is assumed for both training and inference
+- The observation window considers to start as early as 15ms~50ms.
+- A future 4ms or 5ms instance from the prediction output is considered for calculating the metric.
+- Raw channel matrix is considered as model input
+- The performance metric is 5% UPT for Max rank 1.
+- No post processing is considered.
+- Note: Results refer to Table 5.29 of R1-2308344.
+
+#### 6.2.2.7 Generalization evaluations for CSI prediction
+
+##### *Generalization over UE speeds*
+
+For the *generalization verification* of AI/ML based CSI prediction *over various UE speeds* compared to the generalization Case 1 where the AI/ML model is trained with dataset subject to a certain UE speed#B and applied for inference with a same UE speed#B,
+
+- For generalization Case 2, generalized performance may be achieved for certain combinations of UE speed#A and UE speed#B but not for others:
+ - If UE speed#B is 10 km/h & UE speed#A is 30 km/h, 2 sources observe a generalized performance of less than -1.4% degradation.
+ - Note: 1 company still observes significant degradation (-11.3%~-13.4% loss).
+ - If UE speed#B is either 30 km/h or 60 km/h or 120 km/h, or if UE speed#B is 10km/h and UE speed#A is either 60km/h or 120km/h, 11 sources observe that moderate/significant performance degradations are suffered:
+ - For UE speed#B is 10 km/h & UE speed#A is either 60 km/h or 120 km/h, 1 source observes moderate degradation (-2.3% loss), 3 sources observe significant degradation (-5.5%~-61% loss).
+ - For UE speed#B is 30 km/h & UE speed#A is either 10 km/h, 60 km/h or 120 km/h, 2 sources observe moderate degradation (-2.01%~-4.62% loss), 9 sources observe significant degradation (-5%~-72.37% loss).
+ - For UE speed#B is 60 km/h & UE speed#A is either 10 km/h, 30 km/h or 120 km/h, 1 source observes moderate degradation (-3% loss), 10 sources observe significant degradation (-7.8%~-76.85% loss).
+ - For UE speed#B is 120 km/h & UE speed#A is either 30 km/h or 60 km/h, 1 source observes moderate degradation (-3.4% loss), 5 sources observe significant degradation (-7.55%~-56.3% loss).
+- For generalization Case 3, generalized performance of the AI/ML model can be achieved in general (0%~-4.45% loss) for UE speed#B subject to any of 10 km/h, 30 km/h, 60 km/h and 120 km/h, if the training dataset is constructed with data samples subject to multiple UE speeds including UE speed#B, as observed by 11 sources.
+ - For UE speed#B is 10 km/h, minor loss (-0.2%~-1.7%) are observed by 4 sources.
+ - For UE speed#B is 30 km/h, minor loss (-0.2%~-1.34%) or positive gain are observed by 5 sources, moderate loss (-4.07%~-4.2%) are observed by 2 sources.
+ - For UE speed#B is 60 km/h, minor loss (-0.05%~-2%) are observed by 4 sources, moderate loss (-3.76%~-4.65%) are observed by 2 sources.
+ - For UE speed#B is 120 km/h, moderate loss (-2%~-4.45%) are observed by 4 sources.
+ - Note: For generalization Case 3, 6 sources observe significant performance degradations (-5%~-43.6% loss) for UE speed#B subject to 10 km/h, 30 km/h, 60 km/h, but compared with generalization Case 2, in general the performance is still improved.
+
+The above results are based on the following assumptions besides the assumptions of the agreed EVM table:
+
+- Raw channel matrix is used as the model input.
+- Training data samples are not quantized, i.e., Float32 is used/represented.
+- The performance metric is SGCS in linear value for layer 1/2/3/4.
+- No spatial consistency is considered.
+- Note: Results refer to Table 5.5 of R1-2308340.
+
+#### 6.2.2.8 Summary of Performance Results for CSI feedback enhancement
+
+The following aspects have been studied for the evaluation on AI/ML based **CSI compression** in Rel-18:
+
+- From the perspective of basic performance gain over non-AI/ML benchmark (assuming 1 on 1 joint training without considering generalization),
+ - o It has been studied with corresponding observations on:
+ - the metrics of SGCS, mean UPT, 5% UPT, CSI feedback overhead reduction
+ - the benchmark of R16 Type II codebook
+ - o It has been studied but is lack of observations on:
+ - the metric of NMSE
+ - the benchmarks of Type I codebook and R17 Type II codebook
+ - o It has been studied with corresponding observations on complexity but without comparison with non-AI/ML.
+- From the perspective of AI/ML solutions (assuming 1 on 1 joint training without considering generalization),
+ - o It has been studied with corresponding observations on: model input/output type, monitoring for intermediate KPI (including NW side monitoring and UE side monitoring), quantization methods (including quantization awareness for training, and quantization format), and high resolution ground-truth CSI for training, with the metric of SGCS.
+ - o It has been studied but is lack of observations on: the options of CQI/RI calculation, and the options of rank>1 solution
+- From the perspective of generalization over various scenarios (assuming 1 on 1 joint training),
+ - o It has been studied with corresponding observations on (with the metric of SGCS):
+ - the scenarios including various deployment scenarios, various outdoor/indoor UE distributions, various carrier frequencies, and various TxRU mappings
+ - the approach of dataset mixing (generalization Case 3)
+ - o It has been studied but is lack of observations on:
+ - other aspects of scenarios
+ - the approach of fine-tuning
+- From the perspective of scalability over various configurations (assuming 1 on 1 joint training),
+ - o It has been studied with corresponding observations on (with the metric of SGCS):
+ - the configurations including various bandwidths/frequency granularities, various CSI feedback payloads, and various antenna port numbers
+ - the approach of dataset mixing (generalization Case 3), and the approach of fine-tuning for CSI feedback payloads
+
+- the scalability solutions
+- It has been studied but is lack of observations on:
+ - other aspects of configurations
+ - the approach of fine-tuning for configurations other than CSI feedback payloads
+- From the perspective of multi-vendor joint training (without considering generalization),
+ - It has been studied with corresponding observations on (with the metric of SGCS):
+ - joint training between 1 NW part model and $M > 1$ UE part models, and joint training between 1 UE part model and $N > 1$ NW part models
+ - It has been studied but is lack of observations on:
+ - joint training between $N > 1$ NW part models and $M > 1$ UE part models
+ - performance comparison between simultaneous training and sequential training
+- From the perspective of separate training (without considering generalization),
+ - It has been studied with corresponding observations on (with the metric of SGCS):
+ - NW first training, including 1 NW part model to 1 UE part model with same backbone and with different backbones, and 1 UE part model to $N > 1$ NW part models
+ - UE first training, including 1 NW part model to 1 UE part model with same backbone and with different backbones, and 1 NW part model to $M > 1$ UE part models
+ - Impact of shared dataset under 1 NW part model to 1 UE part model for NW first training and UE first training
+ - It has been studied but is lack of observations on:
+ - the metric of air-interface overhead of information (e.g., dataset) sharing
+
+The following aspects have been studied for the evaluation on AI/ML based **CSI prediction**:
+
+- From the perspective of basic performance gain over non-AI/ML benchmark (without considering generalization),
+ - It has been studied with corresponding observations on:
+ - the metrics of SGCS, mean UPT, 5% UPT;
+ - the benchmarks of nearest historical CSI and auto-regression/Kalman filter based CSI prediction.
+ - Note: the benchmark of level x based CSI prediction is represented by generalization cases.
+ - It has been studied but is lack of observations on:
+ - the impact of modeling spatial consistency
+ - the metrics of NMSE
+ - It has been studied with corresponding observations on complexity but without comparison with non-AI/ML
+- From the perspective of AI/ML solutions (without considering generalization),
+ - It has been studied with corresponding observations on (with the metric of SGCS and the benchmark of nearest historical CSI): impact of input type, impact of UE speed, impact of prediction window, impact of observation window
+- From the perspective of generalization over various scenarios,
+
+- It has been studied with corresponding observations on (with the metric of SGCS):
+ - the scenario including various UE speeds
+ - the approach of dataset mixing (generalization Case 3)
+- It has been studied but is lack of observations on:
+ - various deployment scenarios, various carrier frequencies, and other aspects of scenarios.
+ - the approach of fine-tuning
+- From the perspective of scalability over various configurations, it has been studied but is lack of observations.
+
+Based on the evaluation for **CSI compression**, the following high-level observations are provided:
+
+- From the perspective of basic performance gain over non-AI/ML benchmark, AI/ML based CSI compression outperforms Rel-16 eType II CB in general under 1-on-1 joint training and generalization Case 1, where
+ - 0.2%~2%/-0.3%~6%/-4%~6% gains of mean UPT as shown in Figure 6.2.2.8-1 through Figure 6.2.2.8-3 are observed for Max rank 1/2/4, respectively, under $RU \leq 39\%$ .
+ - 0.1%~4%/-0.5%~10%/-1.8%~12.22% gains of mean UPT as shown in Figure 6.2.2.8-4 through Figure 6.2.2.8-6 are observed for Max rank 1/2/4, respectively, under $RU 40\% \sim 69\%$ .
+ - 0.23%~9%/-0.2%~15%/-1%~17% gains of mean UPT as shown in Figure 6.2.2.8-7 through Figure 6.2.2.8-9 are observed for Max rank 1/2/4, respectively, under $RU \geq 70\%$ .
+
+
+
+Mean UPT gain, Max Rank 1 ( $RU \leq 39\%$ )
+
+| Source Index | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|--------------|--------------------|--------------------|--------------------|
+| 1 | 2.0 | 0.0 | 1.0 |
+| 2 | 1.0 | 0.0 | 0.5 |
+| 3 | 0.5 | 0.0 | 0.5 |
+| 4 | 2.0 | 0.0 | 0.0 |
+| 5 | 0.0 | 0.8 | 0.7 |
+| 6 | 1.5 | 0.0 | 0.0 |
+| 7 | 0.0 | 0.5 | 0.0 |
+
+Scatter plot showing Mean UPT gain for Max Rank 1 (RU ≤ 39%) across 8 sources. The y-axis ranges from 0% to 3% in 0.5% increments. The x-axis represents the index of source from 0 to 8. Three data series are plotted: CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green).
+
+Figure 6.2.2.8-1: Mean UPT gain, Max Rank 1 ( $RU \leq 39\%$ ), x-axis means index of source
+
+
+
+Mean UPT gain, Max Rank 2 ( $RU \leq 39\%$ )
+
+| Source Index | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|--------------|--------------------|--------------------|--------------------|
+| 1 | 6.0 | 2.0 | 3.0 |
+| 2 | 2.0 | 0.5 | -0.5 |
+| 3 | 0.0 | 1.0 | 0.0 |
+| 4 | 0.0 | 0.0 | 1.0 |
+| 5 | 0.0 | 1.0 | 2.0 |
+| 6 | 3.0 | 3.0 | 4.0 |
+| 7 | 4.0 | 2.0 | 1.0 |
+| 8 | 0.0 | 2.5 | 3.0 |
+| 9 | 0.0 | 0.0 | 2.0 |
+
+Scatter plot showing Mean UPT gain for Max Rank 2 (RU ≤ 39%) across 10 sources. The y-axis ranges from -1% to 7% in 1% increments. The x-axis represents the index of source from 0 to 10. Three data series are plotted: CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green).
+
+Figure 6.2.2.8-2: Mean UPT gain, Max Rank 2 ( $RU \leq 39\%$ ), x-axis means index of source
+
+
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 0 | 6 | 0 |
+| 2 | 2.5 | -4 | -4 |
+
+Scatter plot titled 'Mean UPT gain, Max Rank 4 (RU≤39%)'. The y-axis represents Mean UPT gain from -6% to 8% in 2% increments. The x-axis represents index of source from 0 to 3. Data points are shown for CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green) at indices 1 and 2.
+
+Figure 6.2.2.8-3: Mean UPT gain, Max Rank 4 (RU≤39%), x-axis means index of source
+
+
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 3 | 2 | 4 |
+| 2 | 3 | 2 | 0 |
+| 3 | 1.5 | 1 | 1.5 |
+| 4 | 2.8 | 2.8 | 3 |
+| 5 | 2.8 | 2.8 | 3 |
+| 6 | 2 | 2 | 3.5 |
+| 7 | 1 | 1 | 1 |
+| 8 | 2.5 | 2 | 2.5 |
+
+Scatter plot titled 'Mean UPT gain, Max Rank 1 (RU 40%-69%)'. The y-axis represents Mean UPT gain from 0% to 5% in 1% increments. The x-axis represents index of source from 0 to 9. Data points are shown for CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green) at indices 1 through 8.
+
+Figure 6.2.2.8-4: Mean UPT gain, Max Rank 1 (RU40%-69%), x-axis means index of source
+
+
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 10 | 5 | 6 |
+| 2 | 4 | 1 | -1 |
+| 3 | 4 | 4 | 4.5 |
+| 4 | 3 | 4 | 1 |
+| 5 | 3 | 5 | 4 |
+| 6 | 4 | 4 | 1 |
+| 7 | 4 | 4 | 6 |
+| 8 | 9 | 4 | 2 |
+| 9 | 7 | 7 | 8 |
+| 10 | 6 | 3 | 3 |
+
+Scatter plot titled 'Mean UPT gain, Max Rank 2 (RU 40%-69%)'. The y-axis represents Mean UPT gain from -2% to 12% in 2% increments. The x-axis represents index of source from 0 to 12. Data points are shown for CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green) at indices 1 through 10.
+
+Figure 6.2.2.8-5: Mean UPT gain, Max Rank 2 (RU40%-69%), x-axis means index of source
+
+
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 12.5 | 7.5 | 8.5 |
+| 2 | 11.0 | 3.0 | 3.0 |
+| 3 | 3.0 | -1.5 | -1.5 |
+| 4 | 6.0 | 6.0 | 6.0 |
+| 5 | 5.0 | 5.0 | 5.0 |
+
+Scatter plot titled 'Mean UPT gain, Max Rank 4 (RU 40%-69%)'. The y-axis represents UPT gain from -4% to 14% in 2% increments. The x-axis represents the index of source from 0 to 6. Three data series are shown: CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green).
+
+Figure 6.2.2.8-6: Mean UPT gain, Max Rank 4 (RU40%-69%), x-axis means index of source
+
+
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 9.0 | 5.0 | 6.0 |
+| 2 | 4.5 | 3.5 | 1.0 |
+| 3 | 0.5 | 0.5 | 0.5 |
+| 4 | 2.5 | 1.5 | 2.5 |
+| 5 | 3.0 | 1.0 | 1.0 |
+| 6 | 7.0 | 7.0 | 7.0 |
+| 7 | 3.5 | 3.5 | 3.5 |
+| 8 | 6.5 | 3.5 | 1.5 |
+| 9 | 2.0 | 1.0 | 2.0 |
+
+Scatter plot titled 'Mean UPT gain, Max Rank 1 (RU≥70%)'. The y-axis represents UPT gain from 0% to 10% in 1% increments. The x-axis represents the index of source from 0 to 10. Three data series are shown: CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green).
+
+Figure 6.2.2.8-7: Mean UPT gain, Max Rank 1 (RU≥70%), x-axis means index of source
+
+
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 15.0 | 8.0 | 11.0 |
+| 2 | 13.0 | 7.0 | 0.0 |
+| 3 | 5.0 | 5.0 | 7.0 |
+| 4 | 5.0 | 6.0 | 2.0 |
+| 5 | 7.0 | 8.0 | 6.0 |
+| 6 | 12.0 | 8.0 | 2.0 |
+| 7 | 10.0 | 8.5 | 8.5 |
+| 8 | 6.0 | 6.0 | 4.5 |
+| 9 | 13.5 | 5.5 | 2.0 |
+| 10 | 10.0 | 9.0 | 4.5 |
+| 11 | 13.0 | 5.0 | 9.0 |
+
+Scatter plot titled 'Mean UPT gain, Max Rank 2 (RU≥70%)'. The y-axis represents UPT gain from -2% to 16% in 2% increments. The x-axis represents the index of source from 0 to 12. Three data series are shown: CSI overhead A (blue), CSI overhead B (red), and CSI overhead C (green).
+
+Figure 6.2.2.8-8: Mean UPT gain, Max Rank 2 (RU≥70%), x-axis means index of source
+
+
+
+Mean UPT gain, Max Rank 4 (RU $\geq$ 70%)
+
+| Index of source | CSI overhead A (%) | CSI overhead B (%) | CSI overhead C (%) |
+|-----------------|--------------------|--------------------|--------------------|
+| 1 | 15 | 7 | 8 |
+| 2 | 17 | 17 | 6 |
+| 3 | 3 | - | -1 |
+| 4 | - | - | 6 |
+
+Scatter plot showing Mean UPT gain for three CSI overhead levels (A, B, C) across five source indices. The y-axis represents UPT gain from -2% to 18% in 2% increments. The x-axis represents the index of source from 0 to 5. CSI overhead A (blue) has points at (1, 15%), (2, 17%), and (3, 3%). CSI overhead B (red) has points at (1, 7%) and (2, 17%). CSI overhead C (green) has points at (1, 8%), (2, 6%), (3, -1%), and (4, 6%).
+
+**Figure 6.2.2.8-9: Mean UPT gain, Max Rank 4 (RU $\geq$ 70%), x-axis means index of source**
+
+- From the perspective of CSI feedback overhead reduction over non-AI/ML, AI/ML based CSI compression achieves CSI feedback reduction compared with Rel-16 eType II CB in general under 1-on-1 joint training and generalization Case 1, where 4 sources observe the CSI feedback overhead reduction of 10.24%~60%/10%~58.33%/8%~79% for Max rank 1/2/4, respectively, under FTP traffic.
+- From the perspective of AI/ML complexity, a majority of 25 sources adopt the CSI generation model subject to the computational complexity in units of FLOPs from 10M to 800M, and 26 sources adopt the CSI reconstruction model subject to the FLOPs from 10M to 1100M. The actual model complexity may differ from the model complexity in the evaluation with respect to platform-dependent optimization on model implementations. In addition, the complexity between AI/ML and non-AI/ML benchmark is not compared.
+- From the perspective of model input/output type, it is more beneficial by considering precoding matrix as the model input (for CSI generation part)/output (for CSI reconstruction part) than explicit channel matrix.
+- From the perspective of intermediate KPI based monitoring.
+ - o For the monitoring at NW side, increased monitoring accuracy can be achieved by considering R16 eType II CB with new/larger parameter(s) as the ground-truth CSI format for monitoring. On the other hand, the new/larger parameter(s) would lead to increased air-interface overhead compared to R16 eType II CB with legacy parameters.
+ - o For the monitoring at UE side, performance can be monitored with smaller air-interface overhead by considering proxy model at UE compared with monitoring at NW side. On the other hand, the monitoring accuracy may be impacted by the design/robustness of the proxy model.
+ - o Note: the complexity aspect for Case 1, Case 2-1 and Case 2-2 is not evaluated.
+- From the perspective of quantization methods for CSI feedback,
+ - o For the quantization awareness for training, it is beneficial to consider quantization aware training with fixed/pre-configured quantization method/parameters (Case 2-1) or jointly updated quantization method/parameters (Case 2-2) to avoid severe performance degradation. In particular, it is more beneficial in performance for Case 2-2 over Case 2-1 under vector quantization format (VQ).
+ - o For the quantization format, VQ format achieves comparable performance with scalar quantization format (SQ) in general, where VQ achieves better performance than SQ in some cases while worse in some other cases.
+- From the perspective of high resolution ground-truth CSI for training, compared to unquantized ground-truth CSI (e.g., Float32), taking R16 eType II CB with new/larger parameter(s) as the ground-truth CSI format for training data collection can achieve significant overhead reduction without causing severe performance degradation; taking scalar quantization format for training data collection can achieve moderate overhead reduction without causing severe performance degradation. On the other hand, the R16 eType II CB with new/larger parameter(s) would lead to increased overhead compared to R16 eType II CB with legacy parameters
+
+- For ground-truth CSI format, 5 sources observe R16 eType II CB with new/larger parameter(s) outperforms R16 eType II CB with legacy parameter, while one source observes R16 eType II CB with legacy parameter is already close to Float32 with particular dataset processing technique.
+- Note: the complexity aspect is not evaluated.
+- From the perspective of generalization over scenarios, or scalability over configurations that have been evaluated, compared to generalization Case 1 where the AI/ML model is trained with dataset subject to a certain scenario#B/configuration#B and applied for inference with a same scenario#B/configuration#B,
+ - For generalization Case 2 where the AI/ML model is trained with dataset from a different scenario#A/configuration#A, generalized performance may be achieved for some certain combinations of scenario#A/configuration#A and scenario#B/configuration#B but not for others.
+ - For generalization Case 3 where the training dataset is constructed with data samples subject to more than one scenario/configuration (evaluations studied up to four scenarios/configurations) including scenario#B/configuration#B, generalized performance of the AI/ML model can be achieved.
+ - In particular, appropriate scalability solution (e.g., truncation/padding, adaptive quantization granularities, adaptation layer in the AI/ML model) may need to be performed to scale the dimensions of the AI/ML model when the training dataset includes data samples subject to configuration#A which has different input/output dimension than configuration#B.
+- From the perspective of training collaboration types, compared to 1-on-1 joint training, both multi-vendor joint training and separate training with procedures given in clause 6.2.1 may suffer performance loss.
+ - In particular, for multi-vendor joint training, minor or moderate degradation is observed.
+ - In particular, for separate training with procedure given in clause 6.2.1, the performance loss depends on the factors such as backbone alignment, and multi-vendor training behavior:
+ - For separate training of 1 NW part model and 1 UE part model, under both NW first training and UE first training, if backbones are aligned between the two sides, minor degradation is observed; otherwise, additional degradation is observed, leading to minor or moderate performance degradation.
+ - For NW first training with 1 UE part model to $N > 1$ NW part models, or UE first training with 1 NW part model to $M > 1$ UE part models, additional degradation is observed, leading to minor, moderate, or significant performance degradation, depending on the training approach.
+ - As a note, other procedures of separate training are not extensively evaluated.
+
+Based on the evaluation for **CSI prediction**, the following high-level observations are provided:
+
+- From the perspective of basic performance gain over non-AI/ML benchmark, under the same UE speed for training and inference,
+ - AI/ML based CSI prediction outperforms the benchmark of the nearest historical CSI in general, where the majority of sources observe up to 10.6% gain in terms of mean UPT.
+ - for AI/ML based CSI prediction over non-AI/ML based CSI prediction, 3 sources observe 0.7%~7% gain while 2 sources observe performance loss of -0.1%~-17% in terms of mean UPT.
+- From the perspective of AI/ML complexity, a majority of 16 sources adopt the model subject to the computational complexity in units of FLOPs from 0.1M to 1000M. The actual model complexity may differ from the model complexity in the evaluation with respect to platform-dependent optimization on model implementations. In addition, the complexity between AI/ML and non-AI/ML benchmark is not compared.
+- From the perspective of model input/output type, it is more beneficial in performance by considering raw channel matrix as the model input than precoding matrix
+- From the perspective of AI/ML solutions, the gain of AI/ML based CSI prediction over the benchmark of the nearest historical CSI is impacted by the observation window length, prediction window length, and UE speed
+
+- From the perspective of generalization over UE speeds that have been evaluated, compared to generalization Case 1 where the AI/ML model is trained with dataset subject to a certain UE speed#B and applied for inference with a same UE speed#B,
+ - o For generalization Case 2 where the AI/ML model is trained with dataset from a different UE speed#A, generalized performance may be achieved for some certain combinations of UE speed#A and UE speed#B but not for others
+ - o For generalization Case 3 where the training dataset is constructed with data samples subject to multiple UE speeds including UE speed#B, generalized performance of the AI/ML model can be achieved in general
+
+## 6.3 Beam management
+
+### 6.3.1 Evaluation assumptions, methodology and KPIs
+
+Figure 6.3.1-1 provides an example for the inference procedure for beam management for BM-Case1 and BM-Case2. Measurements based on Set B of beams are used as model input. In addition, beam ID information may be also provided as input to the AI/ML model. Based on model output (e.g., probability of each beam in Set A to be the Top-1 beam, predicted L1-RSRPs), Top-1/N beam(s) among Set A of beams can be predicted and/or potentially with predicted L1-RSRPs (depending on the labelling). In the evaluation, for BM-Case 1, the measurements of Set B (otherwise stated) are used as model input to predict Top-1/N beams from Set A, and for BM-Case2, the measurements from historic time instance(s) are used as model input for temporal DL beam prediction of beams from Set A. In the evaluation, the cases that Set A and Set B are different (Set B is NOT a subset of Set A), and Set B is a subset of Set A for both BM-Case1 and BM-Case2, and case that Set A and Set B are the same for BM-Case2 are considered. And the performance of DL Tx beam prediction and DL Tx-Rx beam pair prediction is evaluated.
+
+For both BM-Case1 and BM-Case2, UE can report the prediction result to NW based on the output of a UE-side model, or NW can predict the Top-1/N beam(s) based on the reported measurements of Set B for a NW-side model.
+
+
+
+```
+
+graph LR
+ subgraph Model_input [Model input:]
+ direction TB
+ M1[Measurements based on
+a) Set B of beams (BM-Case1)
+b) Set B of beams at historic
+time instance(s) (BM-Case2)]
+ end
+ M1 --> AI[AI/ML model]
+ AI --> Model_output [Model output:]
+ subgraph Model_output_desc [ ]
+ direction TB
+ O1[e.g., probability of each beam in
+Set A to be the Top-1 beam,
+predicted L1-RSRPs]
+ O2[Based on model output,
+obtain Top-1/N beams among
+Set A of beams]
+ end
+ style Model_output_desc fill:none,stroke:none
+
+```
+
+Diagram illustrating the inference procedure for beam management. It shows a flow from 'Model input' to an 'AI/ML model' box, which then produces 'Model output'. The model input consists of measurements based on Set B of beams (BM-Case1) or Set B of beams at historic time instance(s) (BM-Case2). The model output includes the probability of each beam in Set A to be the Top-1 beam and predicted L1-RSRPs. Based on this output, Top-1/N beams among Set A of beams are obtained.
+
+**Figure 6.3.1-1: An example of the inference procedure for beam management.**
+
+For dataset construction and performance evaluation (if applicable) in the AI/ML for beam management use case, *system level simulation* approach is adopted as baseline. *Link level simulation* is optionally adopted.
+
+#### KPIs:
+
+- Model complexity and computational complexity.
+
+Beam prediction accuracy related KPIs, including:
+
+- **Top-1 genie-aided Tx beam** considers the following definitions:
+ - Option A (baseline), the Top-1 genie-aided Tx beam is the Tx beam that results in the largest L1-RSRP over all Tx and Rx beams
+ - Option B (optional), the Top-1 genie-aided Tx beam is the Tx beam that results in the largest L1-RSRP over all Tx beams with specific Rx beam(s)
+ - Specific Rx beam(s) are to be reported. Note: specific Rx beams are a subset of all Rx beams.
+- **Top-1 genie-aided Tx-Rx beam pair** considers the following definitions:
+
+- Option A: The Tx-Rx beam pair that results in the largest L1-RSRP over all Tx and Rx beams
+- Other options not precluded and can be reported
+- Average L1-RSRP difference of Top-1 predicted beam:
+ - The difference between the ideal L1-RSRP of Top-1 predicted beam and the ideal L1-RSRP of the Top-1 genie-aided beam
+- Beam prediction accuracy (%):
+ - Top-1 (%): the percentage of "the Top-1 genie-aided beam is Top-1 predicted beam"
+ - Top-K/1 (%): the percentage of "the Top-1 genie-aided beam is one of the Top-K predicted beams"
+ - Top-1/K (%) (Optional): the percentage of "the Top-1 predicted beam is one of the Top-K genie-aided beams"
+ - Where $K > 1$ and values can be reported
+- CDF of L1-RSRP difference for Top-1 predicted beam
+- Beam prediction accuracy (%) with 1dB margin for Top-1 beam
+ - The beam prediction accuracy (%) with 1dB margin is the percentage of the Top-1 predicted beam "whose ideal L1-RSRP is within 1dB of the ideal L1-RSRP of the Top-1 genie-aided beam"
+- Other beam prediction accuracy related KPIs are not precluded and can be reported
+
+Impact of quantization error of imputed L1-RSRP (for training and inference) is to be studied. Existing quantization granularity of L1-RSRP (i.e., 1dB for the best beam, 2dB for the difference to the best beam) is the starting point for evaluation at least for NW-sided model.
+
+The performance impact of the relative L1-RSRP measurement error can be optionally evaluated for both DL Tx beam and beam pair prediction, where the relative L1-RSRP measurement error can be modelled as noise among beams as a starting point:
+
+- Additive Gaussian noise with 95% of the density function within the measurement accuracy range, and/or uniformly distributed noise for the error due to baseband and/or RF impairment.
+- Other modelling methods are not precluded and can be reported by companies.
+- Companies' report includes how to model the measurement error and the measurement accuracy range in training and test data and labels.
+- Companies' report includes the baseline performance with the relative L1-RSRP measurement error
+
+System performance related KPIs, including:
+
+- UE throughput: CDF of UE throughput, average and 5%-ile UE throughput
+- RS overhead reduction for BM-Case1:
+ - Option 1: "RS " OH reduction[%]" $= 1 - N/M$
+ - where N is the number of beams (pairs) (with reference signal (SSB and/or CSI-RS)) required for measurement for AI/ML
+ - where M is the total number of beams (pairs) to be predicted
+ - Option 2: "RS " OH reduction[%]" $= 1 - N/M$
+ - where N is the total number of beams (pairs) (with reference signal (SSB and/or CSI-RS)) required for measurement for AI/ML, including the beams (pairs) required for additional measurements before/after the prediction if applicable
+ - where M is the total number of beams (pairs) (with reference signal (SSB and/or CSI-RS)) required for measurement for baseline scheme, including the beams (pairs) required for additional measurements before/after the prediction if applicable
+
+- Companies report the assumption on additional measurements
+- RS overhead reduction for BM-Case2, when Top-1 and Top-K beam (pairs) are inferred:
+ - "RS " OH reduction[%]= $1-N/M$
+ - where N is the total number of beams (pairs) (with reference signal (SSB and/or CSI-RS)) required for measurement for AI/ML, including the beams (pairs) required for additional measurements before/after the prediction if applicable.
+ - where M is the total number of beams (pairs) (with reference signal (SSB and/or CSI-RS)) required for measurement for baseline scheme
+ - Companies report the assumption on additional measurements.
+ - Companies report the assumption on baseline scheme.
+ - Companies report the assumption on T1 and T2.
+- Other System performance related KPIs are not precluded and can be reported by companies
+
+To calculate the measurement/RS overhead reduction and summarize results for BM-Case 2, at least when Top-1 beam (pair) is inferred:
+
+- **Case A:** based on number of measurements/RSs and prediction time. An example is shown in Figure 6.3.1-2.
+ - where T2 is the time duration for beam prediction
+ - where Mt is the number of time instances for measurement as AI/ML inputs with a periodicity of Tper
+ - where Pt is the number of time instance(s) for prediction with a periodicity of Tper in T2
+ - **In this case**, the non-AI baseline is Option 1 (measured all the beams at each time instance(s) for prediction with a periodicity of Tper in T2)
+ - For Set B= Set A, the RS overhead reduction is $1-Mt/(Mt+Pt)$ .
+ - For Set B (N beams, same number in each time instance) is a subset of Set A (M beams), the RS overhead reduction is
+ - $N*Mt/(M*(Mt+Pt))$ if no sliding window
+ - $1-N/M$ if considering sliding window
+- **Case B:** based on a periodicity T of the required reference signals for measurements to achieve a certain beam prediction accuracy. An example is shown in Figure 6.3.1-3.
+ - For non-AI baseline (Option 2), every T=X ms reference signals for measurements are needed
+ - For AI, every T=Y ms, reference signals for measurements are needed
+ - **In this case**,
+ - For Set B = Set A, the RS overhead reduction is $1-X/Y$ .
+ - For Set B (N beams) is a subset of Set A (M beams), the RS overhead reduction is $[1-XN/(YM)]$ .
+- **Case B+:** based on Y times of a given minimal periodicity Tper of the reference signals for measurements. An example is shown in Figure 6.3.1-4.
+ - For non-AI baseline (Option 1), UE measures all the reference signals of Set A every Tper
+ - For AI, UE measures the reference signals of Set B every Y times of Tper
+ - In this case, prediction time is defined as the time from each measurement instance to the latest prediction instance before the next measurement instance.
+
+- **In this case**, the non-AI baseline is Option 1 (measured all the beams at each time instance(s) for prediction with a periodicity of $T_{per}$ , which is reported by companies)
+- For Set B= Set A, the RS overhead reduction is $1-1/Y$ .
+- For Set B (N beams) is a subset of Set A (M beams), the RS overhead reduction is $1-N/(YM)$ .
+
+
+
+Figure 6.3.1-2: Example for Case A. A timeline diagram showing periodic measurement and prediction instances. A horizontal line has five upward-pointing arrows. The first three are solid (measurements), and the last two are dashed (predictions). A bracket labeled 'Tper' spans the last three arrows. Below the line, a bracket from the first to the third arrow is labeled 'number of RS = Mt'. Another bracket from the third to the fifth arrow is labeled 'number of Tper = Pt' and 'prediction time T2'. A legend on the right shows a dashed arrow labeled 'time instance for beam prediction' and a solid arrow labeled 'time instance for measurement'.
+
+Figure 6.3.1-2: Example for Case A
+
+
+
+Figure 6.3.1-3: Example for Case B. A diagram comparing 'non-AI' and 'AI' beam prediction. The 'non-AI' part shows a bracket labeled 'X ms' containing three arrows: solid, dashed, and solid. The 'AI' part shows a bracket labeled 'Y ms' containing five arrows: solid, dashed, solid, dashed, and solid. A legend on the right shows a dashed arrow labeled 'time instance for beam prediction' and a solid arrow labeled 'time instance for measurement and prediction'.
+
+Figure 6.3.1-3: Example for Case B
+
+
+
+Figure 6.3.1-4: Example for Case B+. A timeline diagram showing a sequence of measurement and prediction instances. It starts with a bracket labeled 'Tper' containing one solid and one dashed arrow. This is followed by a bracket labeled 'Y times of Tper' containing four sets of (solid, dashed) arrows. Then, a bracket labeled 'One example of prediction time' contains one solid and one dashed arrow. A legend on the right shows a dashed arrow labeled 'time instance beam prediction' and a solid arrow labeled 'time instance for measurement'.
+
+Figure 6.3.1-4: Example for Case B+
+
+For both BM-Case1 and BM-Case2 when Set B is a subset of or different from Set A, a certain RS/measurement overhead is assumed to summarize the evaluation results for Top-1(%) beam prediction accuracy. With additional measurements among predicted Top-K beam (pairs) (i.e., with additional RS/measurement overhead), Top-1 beam (pair) can be obtained by finding a best beam (pair) among the K predicted beams (pairs) with the beam prediction accuracy of Top-K/1(%) if no genie-aid Top-1 beam change out of the K predicted beam (pairs) during the additional measurements.
+
+Note: This is to explain the potential implications and relations of Top-1(%) and Top-K/1(%) beam prediction accuracy metrics defined in evaluations agenda item with regards to RS overhead and additional measurement. The corresponding specification impact is a separate discussion.
+
+Other KPIs, including:
+
+- UCI report overhead (e.g., number of UCI reports and UCI payload size) and/or UCI overhead reduction for inference of AI/ML model can be reported, at least for NW side beam prediction
+- $\text{UCI overhead reduction} = 1 - \frac{\text{Total UCI payload size for AI/ML}}{\text{Total UCI payload size of baseline}}$ .
+- Companies expected to report detailed assumption of UCI for AI/ML and baseline, e.g., including quantization mechanism.
+- Latency reduction:
+ - $(1 - (\frac{\text{Total transmission time of N beams}}{\text{Total transmission time of M beams}}))$
+ - where N is the number of beams (with reference signal (SSB and/or CSI-RS)) in the input beam set required for measurement
+ - where M is the total number of beams
+- Power consumption reduction
+
+For AI/ML models, which provide L1-RSRP as the model output, the accuracy of predicted L1-RSRP is to be evaluated. Companies optionally report average (absolute value)/CDF of the predicted L1-RSRP difference, where the predicted L1-RSRP difference is defined as the difference between the predicted L1-RSRP of Top-1 predicted beam and the ideal L1-RSRP of the same beam.
+
+#### ***Model generalization:***
+
+In the context of model generalization, scenarios may mean various deployment scenarios, various outdoor/indoor UE distributions, various UE mobility assumptions. Similarly, configurations may mean various UE parameters, various gNB settings, Various Set B of beam(pairs). The selected scenarios/configurations for generalization verification may consider the AI model inference node (e.g., @UE or @gNB) and use case (e.g., BM-Case1, or BM-Case2). Specifically, the following generalizations could be considered and clause 6.3.2 presents those which have been actually simulated by companies:
+
+- Scenarios:
+ - Various deployment scenarios, e.g., UMa, UMi and others; e.g., 200m ISD or 500m ISD and others; e.g., same deployment, different cells with different configuration/assumption; e.g., gNB height and UE height;
+ - Various outdoor/indoor UE distributions, e.g., 100%/0%, 20%/80%, and others
+ - Various UE mobility, e.g., 3km/h, 30km/h, 60km/h and others
+- Configurations (parameters and settings):
+ - Various UE parameters, e.g., number of UE Rx beams (including number of panels and UE antenna array dimensions)
+ - Various gNB settings, e.g., DL Tx beam codebook (including various Set A of beam(pairs) and gNB antenna array dimensions)
+ - Various Set B of beam (pairs)
+ - T1 for measurement /T2 for prediction for BM-Case2
+- Other scenarios/configurations(parameters and settings) are not precluded and can be reported
+
+Companies to report the selected scenarios/configurations for generalization verification. Note: other approaches for achieving good generalization performance for AI/ML-based schemes are not precluded.
+
+The following cases are considered for verifying the *generalization performance* of an AI/ML model over various scenarios/configurations as a starting point:
+
+- **Case 1:** The AI/ML model is trained based on training dataset from one Scenario#A/Configuration#A, and then the AI/ML model performs inference/test on a dataset from the same Scenario#A/Configuration#A
+
+- **Case 2:** The AI/ML model is trained based on training dataset from one Scenario#A/Configuration#A, and then the AI/ML model performs inference/test on a different dataset than Scenario#A/Configuration#A, e.g., Scenario#B/Configuration#B, Scenario#A/Configuration#B
+- **Case 3:** The AI/ML model is trained based on training dataset constructed by mixing datasets from multiple scenarios/configurations including Scenario#A/Configuration#A and a different dataset than Scenario#A/Configuration#A, e.g., Scenario#B/Configuration#B, Scenario#A/Configuration#B, and then the AI/ML model performs inference/test on a dataset from a single Scenario/Configuration from the multiple scenarios/configurations, e.g., Scenario#A/Configuration#A, Scenario#B/Configuration#B, Scenario#A/Configuration#B.
+- Notes: Companies to report the ratio for dataset mixing. Number of the multiple scenarios/configurations can be larger than two.
+- The following case for generalization verification, can be optionally considered by companies:
+ - **Case 2A:** The AI/ML model is trained based on training dataset from one Scenario#A/Configuration#A, and then the AI/ML model is updated based on a fine-tuning dataset different than Scenario#A/Configuration#A, e.g., Scenario#B/Configuration#B, Scenario#A/Configuration#B. After that, the AI/ML model is tested on a different dataset than Scenario#A/Configuration#A, e.g., subject to Scenario#B/Configuration#B, Scenario#A/Configuration#B.
+ - Companies to report the fine-tuning dataset setting (e.g., size of dataset) and the improvement of performance.
+
+Further details on evaluation assumptions
+
+The following options are studied on the selection of Set B of beams (pairs):
+
+- **Option 1:** Set B is fixed across training and inference
+- **Option 2:** Set B is variable (e.g., different beams (pairs) patterns in each time instance/report/measurement during training and/or inference)
+ - **Opt 2A:** Set B is changed following a set of pre-configured patterns
+ - **Opt 2B:** Set B is randomly changed among pre-configured patterns
+ - **Opt 2C:** Set B is randomly changed among Set A beams (pairs)
+ - **Opt 2D:** Set B is a subset of measured beams (pairs) Set C (including Set B = Set C), e.g. Top-K beams(pairs) of Set C
+ - The number of beams(pairs) in Set B can be fixed or variable
+ - Companies report the number of pre-configured patterns used in the evaluation for Option 2: Set B is variable if applicable (e.g. Opt A and Opt B)
+- Note: BM-Case1 and BM-Case2 may be considered for different option.
+- Note: This does not preclude the alternative that Set B is different from Set A.
+
+For the evaluation of Option 2: Set B is variable (e.g., different beams (pairs) patterns in each time instance/report/measurement during training and/or inference), study the following options as AI/ML model inputs:
+
+- Alt 1: *Implicit* information of Tx beam ID and/or Rx beam ID
+ - e.g., measurements of Set B of beams together with default values (e.g., 0) for the beams not in Set B are used as AI inputs in a certain order/ matrix/ vector. Detailed assumption can be reported.
+- Alt 2: Tx beam ID and/or Rx beam ID is used as inputs of AI/ML *explicitly*.
+
+For the purpose of DL Tx beam prediction evaluations, consider the following options for Rx beam as AI/ML model input for training and/or inference if applicable:
+
+- Option 1: Measurements of the "best" Rx beam with exhaustive beam sweeping for each model input sample.
+
+- Companies expected to report how to select the "best" Rx beam(s).
+- Option 2: Measurements of specific Rx beam(s).
+ - Companies expected to report how to select specific Rx beam(s).
+- Option 3: Measurements of random Rx beam(s) per model input sample.
+- Option 4: Measurements of quasi-optimal Rx beam (i.e., not all the measurements as inputs of AI/ML are from the "best" Rx beam) with less measurement/RS overhead compared to exhaustive Rx beam sweeping.
+ - Identify the quasi-optimal Rx beams to be utilized for measuring Set B/Set C based on the previous measurements. Companies can report the time information and beam type (e.g., whether the same Tx beam(s) in Set B) of the reference signal to use. Companies expected to report the measurement/RS overhead together with the beam prediction accuracy, as well as, how to find the quasi-optimal Rx beam with "previous measurement".
+- Other options are not precluded and can be reported by companies.
+
+Performance with different types of labels are studied considering the following:
+
+- Option 1a: Top-1 beam(pair) in Set A
+- Option 1b: Top-K beam (pair)s in Set A
+- Option 2a: L1-RSRPs per beam of all the beams(pairs) in Set A
+- Option 2b: Top-K beam(pair)s in Set A and the corresponding L1-RSRPs
+- Option 2c: Top-1 beam(pair) in Set A and the corresponding L1-RSRP
+
+#### **Evaluation assumptions:**
+
+Table 6.3.1-1 presents the baseline system level simulation assumptions for AI/ML in beam management evaluations.
+
+**Table 6.3.1-1: Baseline System Level Simulation assumptions for AI/ML in beam management evaluations**
+
+| Parameter | Value |
+|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Frequency Range | FR2 @ 30 GHz; SCS: 120 kHz |
+| Deployment | 200m ISD, 2-tier model with wrap-around (7 sites, 3 sectors/cells per site)<br>Other deployment assumption is not precluded |
+| Channel model | UMa with distance-dependent LoS probability function defined in Table 7.4.2-1 in TR 38.901. |
+| System BW | 80MHz |
+| UE Speed | For spatial domain beam prediction: 3km/h<br>For time domain beam prediction: 30km/h (baseline), 60km/h (optional), 90km/h (optional), 120km/h (optional)<br>Other values are not precluded |
+| UE distribution | 10 UEs per sector/cell for system performance related KPI (if supported) [e.g., throughput] for full buffer traffic (if supported) evaluation (model inference).<br>X UEs per sector/cell for system performance related KPI for FTP traffic (if supported) evaluation (model inference).<br>Other values are not precluded.<br>Number of UEs per sector/cell during data collection (training/testing) is reported by companies if relevant.<br><br>For spatial domain beam prediction (optional to compare different UE distributions assumptions):<br><ul style="list-style-type: none"> <li>- Option 1: 80% indoor ,20% outdoor as in TR 38.901</li> <li>- Option 2: 100% outdoor</li> </ul> For time domain prediction: 100% outdoor |
+| Transmission Power | Maximum Power and Maximum EIRP for base station and UE as given by corresponding scenario in 38.802 (Table A.2.1-1 and Table A.2.1-2) |
+| BS Antenna Configuration | Antenna setup and port layouts at gNB: (4, 8, 2, 1, 1, 1, 1), (dV, dH) = |
+
+| | |
+|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | (0.5, 0.5) $\lambda$<br>Other assumptions are not precluded.<br><br>Companies to explain TXRU weights mapping.<br>Companies to explain beam selection.<br>Number of BS beams: 32 or 64 downlink Tx beams (max number of available beams) at NW side. Other values, e.g., 256 not precluded. |
+| BS Antenna radiation pattern | TR 38.802 Table A.2.1-6, Table A.2.1-7 |
+| UE Antenna Configuration | Antenna setup and port layouts at UE: (1, 4, 2, 1, 2, 1, 1), 2 panels (left, right)<br>Other assumptions are not precluded<br><br>Companies to explain TXRU weights mapping.<br>Companies to explain beam and panel selection.<br>Number of UE beams: 4 or 8 downlink Rx beams (max number of available beams) per UE panel at UE side. Other values, e.g., 16 not precluded. |
+| UE Antenna radiation pattern | TR 38.802 Table A.2.1-8, Table A.2.1-10 |
+| Beam correspondence | Companies to explain beam correspondence assumptions (in accordance to the two types agreed in RAN4) |
+| Link adaptation | Based on CSI-RS |
+| Traffic Model | For system performance related KPI (if supported) evaluation (model inference), companies report either of the following traffic model:<br>Option 1: Full buffer<br>Option 2: FTP model with detail assumptions (e.g., FTP model 1, FTP model 3) |
+| Inter-panel calibration for UE | Ideal, non-ideal following 38.802 (optional) – Explain any errors |
+| Control and RS overhead | Companies report details of the assumptions |
+| Control channel decoding | Ideal or Non-ideal (Companies explain how it is modelled) |
+| UE receiver type | MMSE-IRC as the baseline, other advanced receiver is not precluded |
+| BF scheme | Companies to explain what scheme is used |
+| Transmission scheme | Multi-antenna port transmission schemes<br>Note: Companies explain details of the using transmission scheme. |
+| Other simulation assumptions | Companies to explain serving TRP selection<br>Companies to explain scheduling algorithm |
+| Other potential impairments | Not modelled (assumed ideal).<br>If impairments are included, companies will report the details of the assumed impairments |
+| BS Tx Power | 40 dBm (baseline)<br>Other values (e.g., 34 dBm) not precluded |
+| Maximum UE Tx Power | 23 dBm |
+| BS receiver Noise Figure | 7 dB |
+| UE receiver Noise Figure | 10 dB |
+| Inter site distance | 200 m |
+| BS Antenna height | 25 m |
+| UE Antenna height | 1.5 m |
+| Car penetration Loss | 38.901, sec 7.4.3.2: $\mu = 9$ dB, $\sigma_p = 5$ dB |
+| UE measurements/reports | At least for Temporal Downlink beam prediction:<br>- Periodicity of time instance for each measurement/report in T1: 20ms, 40ms, 80ms, [100ms], 160ms, [960ms]. Other values can be reported.<br>- Number of time instances for measurement/report in T1 can be reported. Time instance(s) for prediction can be reported. |
+| Scenario | Dense Urban (macro-layer only, TR 38.913) is the basic scenario for dataset generation and performance evaluation. Other scenarios are not precluded. |
+| Spatial consistency | At least for BM-Case1, companies report the one of spatial consistency procedures:<br>- Procedure A in TR38.901<br>- Procedure B in TR38.901 |
+| UE trajectory model | UE trajectory model is defined at least for <i>temporal beam prediction</i> in initial phase of the evaluation. Further details below.<br><br>UE trajectory model is not necessarily to be defined at least for <i>spatial-domain beam prediction</i> in initial phase of the evaluation. |
+| UE rotation | UE speed to be reported. Note: UE rotation speed = 0, i.e., no UE rotation, is not precluded |
+
+| | |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Baseline for performance evaluation | <p>For <i>temporal beam prediction</i>:</p> <ul style="list-style-type: none"> <li>- Option 1: Select the best beam for T2 within Set A of beams based on the measurements of all the RS resources or all possible beams from Set A of beams at the time instants within T2</li> <li>- Option 2: Select the best beam for T2 within Set A of beams based on the measurements of all the RS resources from Set B of beams at the time instants within T1 <ul style="list-style-type: none"> <li>- Companies to explain the detail on how to select the best beam for T2 from Set A based on the measurements in T1.</li> </ul> </li> </ul> <p>where T2 is the time duration for the best beam selection, and T1 is a time duration to obtain the measurements of all the RS resource from Set B of beams. T1 and T2 are aligned with those for AI/ML based methods. Whether Set A and Set B are the same or different depend on the sub-use case. Other options are not precluded.</p> <p>For <i>spatial-domain beam prediction</i>:</p> <ul style="list-style-type: none"> <li>- Option 1: Select the best beam within Set A of beams based on the measurement of all RS resources or all possible beams of beam Set A (exhaustive beam sweeping)</li> <li>- Option 2: Select the best beam within Set A of beams based on the measurement of RS resources from Set B of beams</li> <li>- Other options are not precluded.</li> </ul> |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+For temporal beam prediction, the following options are considered as a starting point for *UE trajectory model*. Companies report further changes or modifications from those. Other options are not precluded. UE orientation can be independently modelled from UE moving trajectory. Other UE orientation model is not precluded:
+
+- Option 1: Linear trajectory model with random direction change.
+ - UE moving trajectory: UE will move straight along the selected direction to the end of an time interval, where the length of the time interval is provided by using an exponential distribution with average interval length, e.g., 5s, with granularity of 100 ms.
+ - UE moving direction change: At the end of the time interval, UE will change the moving direction with the angle difference $A\_diff$ from the beginning of the time interval, provided by using a uniform distribution within $[-45^\circ, 45^\circ]$ .
+ - UE moves straight within the time interval with the fixed speed.
+- Option 2: Linear trajectory model with random and smooth direction change.
+ - UE moving trajectory: UE will change the moving direction by multiple steps within an time internal, where the length of the time interval is provided by using an exponential distribution with average interval length, e.g., 5s, with granularity of 100 ms.
+ - UE moving direction change: At the end of the time interval, UE will change the moving direction with the angle difference $A\_diff$ from the beginning of the time interval, provided by using a uniform distribution within $[-45^\circ, 45^\circ]$ .
+ - The time interval is further broken into N sub-intervals, e.g. 100ms per sub-interval, and at the end of each sub-interval, UE change the direction by the angle of $A\_diff/N$ .
+ - UE moves straight within the time sub-interval with the fixed speed.
+- Option 3: Random direction straight-line trajectories.
+ - Initial UE location, moving direction and speed: UE is randomly dropped in a cell, and an initial moving direction is randomly selected, with a fixed speed.
+ - The initial UE location should be randomly drop within the following blue area:
+
+
+
+The diagram illustrates a hexagonal cell divided into three sectors by red lines radiating from the center. A green circle at the center represents the Base Station (BS). A blue rectangle labeled 'UE' is positioned in one of the sectors. A red line forms the outer boundary of the hexagon. A double-headed arrow labeled 'd1' indicates the minimum distance from the BS to the UE.
+
+Diagram of a hexagonal cell with three sectors. A central green circle represents the Base Station (BS). A blue rectangle represents the User Equipment (UE). A red line indicates the cell boundary. A double-headed arrow labeled 'd1' shows the minimum distance from the BS to the UE.
+
+where $d1$ is the minimum distance that UE should be away from the BS.
+
+- Each sector is a cell and that the cell association is geometry based.
+- During the simulation, inter-cell handover or switching should be disabled.
+
+For training data generation:
+
+- For each UE moving trajectory: the total length of the UE trajectory can be set as $T$ seconds if it is in time, or set as $D$ meter if it is in distance.
+- The trajectory sampling interval granularity depends on UE speed.
+- UE can move straight along the entire trajectory, or
+- UE can move straight during the time interval, where the time interval is provided by using an exponential distribution with average interval length $\Delta T$
+- UE may change the moving direction at the end of the time interval. UE will change the moving direction with the angle difference $A\_diff$ from the beginning of the time interval, provided by using a uniform distribution within $[-45^\circ, 45^\circ]$
+- If the UE trajectory hits the cell boundary (the red line), the trajectory should be terminated.
+- If the trajectory length (in time) is less than the length of observation window + prediction window, the trajectory should be discarded.
+- The length of observation window + prediction window is not fixed and companies can report their values.
+
+For AI/ML in beam management evaluation, RAN1 does not attempt to define any common AI/ML model as a baseline.
+
+Table 6.3.1-2 presents the baseline link level simulation assumptions for AI/ML in beam management evaluations.
+
+**Table 6.3.1-2: Baseline Link Level Simulation assumptions for AI/ML in beam management evaluations**
+
+| Parameter | Value |
+|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Frequency | 30GHz. |
+| Subcarrier spacing | 120kHz |
+| Data allocation | [8 RBs] as baseline, companies can report larger number of RBs<br>First 2 OFDM symbols for PDCCH, and following 12 OFDM symbols for data channel |
+| PDCCH decoding | Ideal or Non-ideal |
+| Channel model | FFS:<br>LOS channel: CDL-D extension, DS = 100ns<br>NLOS channel: CDL-A/B/C extension, DS = 100ns<br>Companies to explain details of extension methodology considering spatial consistency.<br>Other channel models are not precluded. |
+| BS antenna configurations | One panel: (M, N, P, Mg, Ng) = (4, 8, 2, 1, 1), (dV, dH) = (0.5, 0.5) $\lambda$ as baseline.<br>Other assumptions are not precluded.<br><br>Companies to explain TXRU weights mapping.<br>Companies to explain beam selection.<br>Companies to explain number of BS beams |
+| BS antenna element radiation pattern | Same as SLS |
+| BS antenna height and antenna array down-tilt angle | 25m, 110° |
+| UE antenna configurations | Panel structure: (M, N, P) = (1, 4, 2),<br><ul style="list-style-type: none"> <li>- 2 panels (left, right) with (Mg, Ng) = (1, 2) as baseline</li> <li>- 1 panel as optional</li> <li>- Other assumptions are not precluded</li> </ul><br>Companies to explain TXRU weights mapping.<br>Companies to explain beam and panel selection.<br>Companies to explain number of UE beams |
+| UE antenna element radiation pattern | Same as SLS |
+| UE moving speed | Same as SLS |
+| Raw data collection format | Depends on sub-use case and companies' choice. |
+
+### 6.3.2 Performance results
+
+BM\_Table 1 through BM\_Table 5 in attached Spreadsheets for Beam Management evaluations present the performance results for:
+
+- BM\_Table 1: Evaluation results for BMCase-1 without generalization
+- BM\_Table 2: Evaluation results for BMCase-2 without generalization
+- BM\_Table 3: Evaluation results for BMCase-1 with generalization for DL Tx beam prediction
+- BM\_Table 4. Evaluation results for BMCase-1 with generalization for beam pair prediction
+- BM\_Table 5. Evaluation results for BMCase-2 with generalization for DL Tx beam and beam pair prediction
+
+In the evaluation, SLS are used for data generation for training/inference unless otherwise stated.
+
+In the following performance results, Top-K/1(%) is used for Top-K DL Tx beam prediction accuracy or Top-K beam pair prediction accuracy.
+
+Figure 6.3.2-1 and Table 6.3.2-1 illustrate model parameter (M) and computational complexity in FLOPs (M) for BM-Case 1 and BM-Case 2, Tx beam prediction and beam pair prediction respectively, according to the reported assumption in BM\_Table 1 and BM\_Table 2.
+
+Note: Optimization of AI/ML model (e.g., in terms of model/computational complexity) was not discussed in the study.
+
+
+
+Scatter plot titled 'Model complexity' showing Computational complexity Flops(M) on the y-axis (logarithmic scale from 0.001 to 1000) versus model parameter(M) on the x-axis (logarithmic scale from 0.001 to 100). Four data series are plotted: BM-Case1 Tx beam (orange), BM-Case1 beam pair (blue), BM-Case2 Tx beam (grey), and BM-Case 2 beam pair (yellow). The data points show a positive correlation between model parameters and computational complexity, with BM-Case 2 beam pair showing the highest complexity for a given number of parameters.
+
+**Figure 6.3.2-1: Complexity of AI/ML models from evaluation results in terms of FLOPs and number of parameters for BM cases**
+
+**Table 6.3.2-1: AI/ML model complexity/computation complexity used in the evaluations for AI/ML in beam management**
+
+| | Model complexity in number of model parameters | Model complexity in number of model size | Computational complexity (FLOPs) |
+|------------------------|-----------------------------------------------------------------|------------------------------------------------------------------------|--------------------------------------------------------|
+| BM-Case 1 DL Tx beam | More than 1k to 4.9M majority reported less than 1M or about 1M | 50Kbytes to 20Mbytes majority reported less than 0.1Mbytes ~ 0.6Mbytes | ~2.7K to 222M majority reported less than 1M or 10s M |
+| BM-Case 1 DL beam pair | 72k to 4.9M majority reported less than 0.1s M ~ 1M | 0.17Mbytes to 21Mbytes majority reported less than 1Mbytes ~ 4Mbytes | 15K to 224M majority reported less than 1M ~ 4 M |
+| BM-Case 2 DL Tx beam | 35k to 11M majority reported less than 0.1s M ~ 1M | 0.5Mbytes to 15Mbytes majority reported about 1s Mbytes | ~90K to 54M majority reported less than 0.1s M or 1s M |
+| BM-Case 2 DL beam pair | 20k to 13M majority reported about 0.1M~1M | 0.08M to 15M majority reported about 1Mbytes | ~90K to 443M majority reported less than 0.4 M or 1s M |
+
+In the following performance results, Top-K/1(%) is used for Top-K DL Tx beam prediction accuracy or Top-K beam pair prediction accuracy.
+
+#### 6.3.2.1 Basic performance for BM-Case1
+
+*BM-Case1*: Spatial-domain Downlink beam prediction for Set A of beams based on measurement results of Set B of beams
+
+Note that in the following evaluations, ideal measurements are assumed
+
+- Beams could be measured regardless of their SNR.
+
+- No measurement error.
+- Measured in a single-time instance (within a channel-coherence time interval).
+- No quantization for the L1-RSRP measurements.
+- No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+
+##### 6.3.2.1.1 Performance when Set B is a subset of Set A for DL Tx beam prediction
+
+For **BM-Case1 DL Tx beam prediction**, when *Set B is a subset of Set A*, AI/ML can provide good beam prediction performance with less measurement/RS overhead comparing to using all measurements of Set A (which provides 100% beam prediction performance as non-AI baseline Option 1) without considering generalization aspects with the measurements from the best Rx beam without UE rotation.
+
+- (A)With measurements of fixed Set B of beams that of 1/4 of Set A of beams
+ - Top-1 DL Tx beam prediction accuracy:
+ - evaluation results from 9 sources indicate that, AI/ML can achieve about 70%~80% beam prediction accuracy
+ - evaluation results from 9 sources indicate that, AI/ML can achieve about 80%~90% beam prediction accuracy
+ - evaluation results from 7 sources indicate that, AI/ML can achieve more than 90% beam prediction accuracy
+ - evaluation results from 1 source indicates that AI/ML can achieve about 60% beam prediction accuracy when the DL Tx beam grid is generated with oversampling
+ - Note: 1 source reported that, AI/ML can achieve more than 90% beam prediction accuracy for 100% outdoor UE, and AI/ML can achieve less than 80% beam prediction accuracy for 80% indoor and 20% outdoor. All other results are with the assumption of 80% indoor and 20% outdoor.
+ - Note: 1 source reported that, AI/ML can achieve 97.3% beam prediction accuracy with the measurements from the best Rx beam based on the best Tx beam in Set A, and AI/ML can achieve 76.4% beam prediction accuracy with the measurements from the best Rx beam of on the best Tx beam in Set B, and 1 source reported that using the best Rx beam in Set A and Set B have similar performance, i.e., 84.84% and 84.59% respectively.
+ - Non-AI baseline Option 2 (exhaustive beam sweeping in Set B of beams) can achieve about 25% beam prediction accuracy.
+ - Top-1 DL Tx beam with 1dB margin:
+ - evaluation results from 15 sources indicate that, AI/ML can achieve more than or about 90% beam prediction accuracy.
+ - evaluation results from 3 sources indicate that, AI/ML can achieve about 80% beam prediction accuracy, wherein 1 source assumed the L1-RSRP of the Top-1 predicted beam is measured with the best Rx beam searched from the best Tx beam in set B.
+ - Top-K(=2) DL Tx beam prediction accuracy
+ - evaluation results from 7 sources indicate that, AI/ML can achieve 80%- 90% beam prediction accuracy.
+ - evaluation results from 14 sources indicate that, AI/ML can achieve more than 90% beam prediction accuracy.
+ - The beam prediction accuracy increases with K.
+ - evaluation results from indicate that Top-2 DL beam prediction accuracy can be more than 95%
+
+- evaluation results from 2 sources indicate that Top-3 DL beam prediction accuracy can be more than 95%
+- evaluation results from 3 sources indicate that Top-4 DL beam prediction accuracy can be more than 95%
+- evaluation results from 4 sources indicate that Top-5 DL beam prediction accuracy can be more than 95%
+- Average L1-RSRP difference of Top-1 predicted beam
+ - evaluation results from 17 sources indicate that it can be below or about 1dB
+ - evaluation results from 2 sources indicate that it can be 2.6~2.7dB with the assumption that the L1-RSRP of the Top-1 predicted beam is measured with the best Rx beam searched from the best Tx beam in set B
+- Average predicted L1-RSRP difference of Top-1 beam
+ - evaluation results from 5 sources indicate that it can be below or about 1dB
+ - evaluation results from 1 source indicates that it is about 2dB
+ - Note that this is assumed that all the L1-RSRPs of Set A of beams are used as the label in AI/ML training phase (e.g., regression AI/ML model)
+- UE average throughput
+ - evaluation results from 3 sources indicate that AI/ML achieves 96%~99% of the UE average throughput of the BM-Case1 baseline option 1 (exhaustive search over Set A beams).
+ - evaluation results from 1 source indicates that non-AI baseline option 2 (exhaustive search over Set B beams) achieves 89% of the UE average throughput of the BM-Case1 baseline option 1 (exhaustive search over Set A beams).
+- UE 5%ile throughput
+ - evaluation results from 2 sources indicate that, AI/ML achieves 95%~97% of the UE 5%ile throughput of the BM-Case1 baseline option 1 (exhaustive search over Set A beams).
+- (B) With measurements of fixed Set B of beams that of 1/8 of Set A of beams
+ - Top-1 DL Tx beam prediction accuracy:
+ - evaluation results from 7 sources indicate that, AI/ML can achieve about 50% beam prediction accuracy
+ - evaluation results from 4 sources indicate that, AI/ML can achieve about 60%~70% beam prediction accuracy
+ - evaluation results from 5 sources indicate that, AI/ML can achieve about 70%~80% beam prediction accuracy.
+ - evaluation results from 4 sources indicate that, AI/ML can achieve more than 80% beam prediction accuracy
+ - Note: 1 source reported that, AI/ML can achieve 89% beam prediction accuracy with the measurements from the best Rx beam based on the best Tx beam in Set A, and AI/ML can achieve 67.6% beam prediction accuracy with the measurements from the best Rx beam of on the best Tx beam in Set B.
+ - Non-AI baseline Option 2 (exhaustive beam sweeping in Set B of beams) can achieve about 12.5% beam prediction accuracy
+ - Top-1 DL Tx beam prediction with 1dB margin
+ - evaluation results from 7 sources indicate that, AI/ML can achieve 70%~80% beam prediction accuracy
+ - wherein 1 source assumed the L1-RSRP of the Top-1 predicted beam is measured with the best Rx beam searched from the best Tx beam in set B.
+
+- evaluation results from 1 source indicate that, AI/ML can achieve 80%-90% beam prediction accuracy
+- evaluation results from 5 sources indicate that, AI/ML can achieve more than 90% beam prediction accuracy
+- Top-K(=2) DL Tx beam prediction accuracy
+ - evaluation results from 6 sources indicate that, AI/ML can achieve about 70%~ 80% beam prediction accuracy
+ - evaluation results from 5 sources indicate that, AI/ML can achieve 80%~90% beam prediction accuracy
+ - evaluation results from 4 sources indicate that, AI/ML can achieve 90% beam prediction accuracy for Top-2 DL Tx beam.
+ - The beam prediction accuracy increases with K.
+ - evaluation results from 3 sources indicate that Top-3 DL beam prediction accuracy can be more than 95%
+ - evaluation results from 4 sources indicate that Top-5 DL beam prediction accuracy can be more than 90%
+- Average L1-RSRP difference of Top-1 predicted beam
+ - evaluation results from 8 sources indicate that it can be below or about 1dB
+ - evaluation results from 4 sources indicate that it can be 1dB~2dB
+ - evaluation results from 1 source indicates that it can be 3.4dB with the assumption that the L1-RSRP of the Top-1 predicted beam is measured with the best Rx beam searched from the best Tx beam in set B
+- Average predicted L1-RSRP difference of Top-1 beam
+ - evaluation results from 5 sources indicates that it can be 0.8~1.5dB
+ - Note that 4 sources assumed that all the L1-RSRPs of Set A of beams are used as the label in AI/ML training phase (e.g., regression AI/ML model) and 1 source assumed that only the L1-RSRP of the Top-1 beam in Set A is used as the label in training phase and the result is 0.82 dB.
+- UE average throughput
+ - evaluation results from 1 source indicates that AI/ML achieves 98% of the UE average throughput of the BMCase1 baseline option 1 (exhaustive search over Set A beams).
+ - evaluation results from 1 source indicates that AI/ML achieves 85% of the UE average throughput of the BMCase1 baseline option 1 (exhaustive search over Set A beams).
+- UE 5%ile throughput
+ - evaluation results from 1 source indicates that, AI/ML achieves 84% of the UE 5%ile throughput of the BMCase1 baseline option (exhaustive search over Set A beams).
+ - evaluation results from 1 source indicates that, AI/ML achieves 70% of the UE 5%ile throughput of the BMCase1 baseline option (exhaustive search over Set A beams).
+
+##### 6.3.2.1.2 Performance when Set B is different than Set A for DL Tx beam prediction
+
+For **BM-Case1 DL Tx beam prediction**, when *Set B is different than Set A*, with measurements of Set B of wide beams that are 1/4 or 1/6 or 1/8 of Set A beams, AI/ML can provide good beam prediction performance with less measurement/RS overhead comparing to using all measurements of Set A (which provides 100% beam prediction performance as non-AI baseline Option 1) without considering generalization aspects with the measurements from the best Rx beam without UE rotation.
+
+- Top-1 DL Tx beam
+
+- evaluation results from 3 sources indicate that, AI/ML can achieve more than 80% beam prediction accuracy
+- evaluation results from 5 sources indicate that, AI/ML can achieve more than 55% beam prediction accuracy
+- 2 sources reported more than 80% beam prediction accuracy with 100% outdoor UEs, and more than 60% beam prediction accuracy with 20% outdoor UEs.
+- Evaluation results from 1 source shows that, with limited measurements (e.g., 1 or 4) of narrow beams in Set A=32, AI/ML can increase 15% or 30% beam prediction accuracy [respectively] compared with 55% beam prediction accuracy with measurement of wide beams only.
+- Top-1 DL Tx beam with 1dB margin
+ - evaluation results from 4 sources indicate that, AI/ML can achieve more than 85% beam prediction accuracy
+ - evaluation results from 3 sources indicate that, AI/ML can achieve 57%~77% beam prediction accuracy
+ - One source reported more than 86% beam prediction accuracy with 100% outdoor UEs, and more than 70% beam prediction accuracy with 20% outdoor UEs.
+- Top-K(=3) DL Tx beam
+ - evaluation results from 3 sources indicate that, AI/ML can achieve more than 95% beam prediction accuracy
+ - evaluation results from 3 sources indicate that, AI/ML can achieve 85~94% beam prediction accuracy
+ - evaluation results from 1 source indicates that Top-5 DL beam prediction accuracy can be more than 90%.
+- Average L1-RSRP difference of Top-1 predicted beam
+ - evaluation results from 4 sources indicate that, the average L1-RSRP difference can be less or about 1dB
+- UE average throughput
+ - evaluation results from 1 source indicates that, AI/ML achieves 99% of the UE average throughput of the BMCase1 baseline option 1 (exhaustive search over Set A beams)
+- UE 5%ile throughput
+ - evaluation results from 1 source indicates that, AI/ML achieves 94% of the of the BMCase1 baseline option 1(exhaustive search over Set A beams)
+
+##### 6.3.2.1.3 Performance when Set B is a subset of Set A for DL Tx-Rx beam pair prediction
+
+For **BM-Case1 DL Tx-Rx beam pair prediction**, when *Set B is a subset of Set A*, AI/ML can provide good beam prediction performance with less measurement/RS overhead comparing to using all measurements of Set A (which provides 100% beam prediction performance as non-AI baseline Option 1) without considering generalization aspects and without UE rotation.
+
+- (A) With measurements of fixed Set B of beam pairs that of 1/4 of Set A of beam pairs
+ - Top-1 beam pair prediction accuracy:
+ - evaluation results from 8 sources indicate that, AI/ML can achieve about 50%~70% prediction accuracy
+ - evaluation results from 4 source indicate that, AI/ML can achieve 70%~80% prediction accuracy
+ - evaluation results from 5 sources indicate that, AI/ML can achieve about 80%~90% prediction accuracy
+ - evaluation results from 1 source indicates that, AI/ML can achieve more than 90% prediction accuracy
+ - Note: in the above evaluation and the rest of other KPIs, most of the sources used measurements from all Rx beams of a certain set of Tx beams, except 3 sources who use measurements from half of Rx beams of a certain set of Tx beams.
+ - The results from 3 sources indicate 60%~68% prediction accuracy in terms of Top-1 beam pair prediction accuracy.
+
+- 1 source additionally reports that, AI/ML can achieve 76.46% and 56.12% beam prediction accuracy with the measurements from all Rx beams and half of Rx beams of a certain set of Tx beams respectively.
+- Non-AI baseline Option 2 (exhaustive beam sweeping in Set B of beam pairs) can achieve about 25% prediction accuracy.
+- Top-1 beam pair prediction accuracy with 1dB margin:
+ - evaluation results from 5 sources indicate that, AI/ML can achieve more than 70% prediction accuracy
+ - evaluation results from 2 sources indicate that, AI/ML can achieve 80%~ about 90% prediction accuracy
+ - evaluation results from 6 sources indicate that, AI/ML can achieve more than 90% prediction accuracy.
+ - Note: 1 source reported that, AI/ML can achieve 91.6% and 74.57% beam prediction accuracy with 1dB margin with the measurements from all Rx beams of a certain set of Tx beams and with half of Rx beams of a certain set of Tx beams respectively.
+- Top-K(=2) beam pair prediction accuracy
+ - evaluation results from 2 sources indicate that, AI/ML can achieve 65%- 75% prediction accuracy.
+ - evaluation results from 6 sources indicate that, AI/ML can achieve 80%- 90% prediction accuracy
+ - evaluation results from 4 sources indicate that, AI/ML can achieve more than 90% prediction accuracy
+ - Note: 1 source reported that, AI/ML can achieve 91.34% and 78.06% Top-K(=2) beam prediction accuracy with the measurements from all Rx beams and half of Rx beams of a certain set of Tx beams respectively.
+ - The beam prediction accuracy increases with K.
+ - evaluation results from 1 source indicate that Top-3 beam pair prediction accuracy can be more than 95%
+ - evaluation results from 4 sources indicate that Top-4 beam pair prediction accuracy can be [more than 95%
+ - evaluation results from 2 sources indicate that Top-5 beam pair prediction accuracy can be more than 95%
+ - evaluation results from 1 source indicate that Top-10 beam pair prediction accuracy can be more than 95% for 32 Tx and 4 Rx with results from half Rx
+- Average L1-RSRP difference of Top-1 predicted beam pair
+ - evaluation results from 13 sources indicate that it can be below or about 1dB
+ - evaluation results from 1 source indicate that it can be about 1.5dB
+ - Note: 1 source reported that it can be 0.716dB and 1.611dB with the measurements from all Rx beams and half of Rx beams of a certain set of Tx beams respectively.
+- Predicted L1-RSRP difference of Top-1 beam pair
+ - 3 sources indicate that it can be below or about 1dB
+ - Note that this is assumed that all the L1-RSRPs of Set A of beams are used as the label in AI/ML training phase (e.g., regression AI/ML model)
+- (B) With measurements of fixed Set B of beam pairs that of 1/8 of Set A of beam pairs
+ - Top-1 beam pair prediction accuracy:
+ - evaluation results from 4 sources indicate that, AI/ML can achieve about 50% prediction accuracy
+ - evaluation results from 4 sources indicate that, AI/ML can achieve about 60%~70% prediction accuracy
+
+- evaluation results from 6 sources indicate that, AI/ML can achieve about 70%~80% prediction accuracy
+- Note: in the above evaluation and the rest of other KPIs, most of the sources used measurements from all Rx beams of a certain set of Tx beams, except 7 sources who use measurements from half of Rx beams of a certain set of Tx beams.
+- Non-AI baseline Option 2 (exhaustive beam sweeping in Set B of beam pairs) can achieve about 12.5% prediction accuracy
+- Top-1 beam pair prediction with 1dB margin
+ - evaluation results from 4 sources indicate that, AI/ML can achieve 60%-70% prediction accuracy
+ - evaluation results from 1 source indicate that, AI/ML can achieve 70%-80% prediction accuracy
+ - evaluation results from 4 sources indicate that, AI/ML can achieve 80%-90% prediction accuracy
+- Top-K( $K=2$ ) beam pair prediction accuracy
+ - evaluation results from 4 sources indicate that, AI/ML can achieve about 70%- 80% prediction accuracy.
+ - evaluation results from 6 sources indicate that, AI/ML can achieve 80%- 90% prediction accuracy
+ - evaluation results from 2 sources indicate that, AI/ML can achieve more than 90% prediction accuracy
+ - The beam prediction accuracy increases with K.
+ - evaluation results from 1 source indicate that Top-3 beam pair prediction accuracy can be 96%
+ - evaluation results from 1 source indicate that Top-4 beam pair prediction accuracy can be 96%
+ - evaluation results from 1 source indicate that Top-5 beam pair prediction accuracy can be 91%
+ - evaluation results from 1 source indicate that Top-5 beam pair prediction accuracy can be 94%
+- Average L1-RSRP difference of Top-1 predicted beam pair
+ - evaluation results from 5 sources indicate that it can be below or about 1dB
+ - evaluation results from 5 sources indicate that it can be 1dB~2dB
+- Average predicted L1-RSRP difference of Top-1 beam pair
+ - evaluation results from 2 sources indicate that it can be 0.7~1.3dB
+ - Note that this is assumed that all the L1-RSRPs of Set A of beams are used as the label in AI/ML training phase (e.g., regression AI/ML model).
+- (C) With measurements of fixed Set B of beams that of 1/16 of Set A of beams
+ - Top-1 beam pair prediction accuracy
+ - evaluation results from 5 sources indicate that, AI/ML can achieve less than 50% or about 50% prediction accuracy
+ - evaluation results from 2 source indicate that, AI/ML can achieve about 55%~57% prediction accuracy
+ - evaluation results from 3 sources indicate that, AI/ML can achieve about 60%~70% prediction accuracy
+ - evaluation results from 1 source indicate that, AI/ML can achieve about 70%~80% prediction accuracy
+ - Note: in the above evaluation and the rest of other KPIs, some 6 sources used measurements from all Rx beams of a certain set of Tx beams, and some other 6 sources use measurements from half or fourth of Rx beams of a certain set of Tx beams.
+ - Non-AI baseline Option 2 (exhaustive beam sweeping in Set B of beam pairs) can achieve about 6.25% prediction accuracy
+
+- Top-1 beam pair prediction with 1dB margin
+ - evaluation results from 4 sources indicate that, AI/ML can achieve less than 50% or about 50% prediction accuracy
+ - evaluation results from 1 source indicate that, AI/ML can achieve more than 50%~60% prediction accuracy
+ - evaluation results from 3 sources indicate that, AI/ML can achieve about 60%-70% prediction accuracy
+ - evaluation results from 2 sources indicate that, AI/ML can achieve 72%~85% prediction accuracy
+- Top-K(=2) beam pair prediction accuracy
+ - evaluation results from 3 sources indicate that, AI/ML can achieve less than 60% prediction accuracy.
+ - evaluation results from 5 sources indicate that, AI/ML can achieve about 70%- 80% prediction accuracy
+ - evaluation results from 1 source indicate that, AI/ML can achieve more than 85% prediction accuracy
+ - The beam prediction accuracy increases with K.
+- Average L1-RSRP difference of Top-1 predicted beam pair
+ - evaluation results from 3 sources indicate that it can be 1dB~2dB
+ - evaluation results from 2 sources indicate that it can be 2dB~3dB
+ - evaluation results from 2 sources indicate that it can be more than 3dB
+ - evaluation results from 1 source indicate that it can be about 6dB
+- Predicted L1-RSRP difference of Top-1 beam pair
+ - evaluation results from 2 sources indicates that it can be about 2.5dB
+ - Note that this is assumed that all the L1-RSRPs of Set A of beams are used as the label in AI/ML training phase (e.g., regression AI/ML model).
+- Note: in the above evaluations, 8 sources assumed 4 Rx, other sources assumed 8 Rx.
+
+##### 6.3.2.1.4 Performance when Set B is different to Set A for DL Tx-Rx beam pair prediction
+
+**For BM-Case1 beam pair prediction**, when *Set B is different to Set A*, with measurements of Set B of Tx wide beams that are 1/4 or 1/8 of Set A beams, evaluation results from 1 source indicate that AI/ML can provide good beam prediction performance with less measurement/RS overhead compared to using all measurements of Set A (which provides 100% beam prediction performance as non-AI baseline Option 1) without considering generalization and without UE rotation.
+
+- For Top-1 beam pair prediction accuracy, evaluation results from 1 source indicate that, AI/ML can achieve about 92.7%/92.5% beam prediction accuracy for 1/4 and 1/8 overhead respectively.
+- For Top-1 beam prediction accuracy with 1dB margin, evaluation results from 1 source indicate that, AI/ML can achieve about 97.6%/97.3% beam prediction accuracy for 1/4 and 1/8 overhead respectively.
+
+#### 6.3.2.2 Basic performance for BM-Case2
+
+*BM-Case2*: Temporal Downlink beam prediction for Set A of beams based on the historic measurement results of Set B of beams.
+
+##### 6.3.2.2.1 Performance when Set A = Set B
+
+**For BM-Case2**, when *Set B = Set A*, for DL Tx beam prediction with the measurements from the best Rx beam or Tx-Rx beam pair prediction, without considering generalization aspects, with the following assumptions:
+
+- UE speed: 30km/h (unless otherwise stated)
+
+- Prediction time: 80ms/160ms/320ms/640ms/800ms/others
+- With UE rotation and without UE rotation
+- Set B is the same as Set A in each time instance for measurement
+
+Note that ideal measurements are assumed.
+
+- Beams could be measured regardless of their SNR.
+- No measurement error.
+- No quantization for the L1-RSRP measurements.
+- No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+
+**(A) For Tx DL beam prediction**, based on most of the evaluation results, AI/ML provides some beam prediction accuracy gain for prediction time larger than or equal to 160ms, and some evaluation results show AI/ML may have similar performance or some degradation for 80ms or 160ms prediction time comparing with non-AI baseline (Option 2, sample and hold based on the previous measurements) with same RS/measurement overhead **without UE rotation**. For the longer the prediction time, the higher gain of beam prediction accuracy can be achieved by AI/ML:
+
+- For 80ms prediction time, evaluation results from 1 source show that AI/ML may **have similar performance or may decrease** about 4% beam prediction accuracy, evaluation results from 2 sources show that AI/ML may have similar performance or may **decrease** 0.4%~1% beam prediction accuracy, evaluation results from 1 source show that AI/ML can **increase** about 1%~2% prediction accuracy in terms of Top-1 beam prediction accuracy,
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 40ms. And it can decrease 4% beam prediction accuracy comparing with 98.23% achieved by non-AI baseline (Option 2-2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 80ms/160ms. And it may decrease up to 0.4%~1% beam prediction accuracy comparing with about 80%/78.7% achieved by non-AI baseline (Option 2) with 32 Tx beams.
+ - wherein, 1 source used measurements from 8 time instances with measurement periodicity of 40ms. And it can decrease about 0.5% beam prediction accuracy comparing with 67.4% achieved by non-AI baseline (Option 2) with 64 Tx beams
+ - wherein, 1 source used measurements from 5 time instances with measurement periodicity of 80ms. And it can increase 1% beam prediction accuracy gain comparing with 78.5% and 76.2% achieved by non-AI baseline (Option 2) with 32 Tx beams for 30km/h and 60km/h respectively.
+- For 160ms prediction time, evaluation results from 3 sources show that AI/ML may have similar performance or may decrease 1%~5% beam prediction accuracy in terms of Top-1 beam prediction accuracy, evaluation results from 3 sources show that AI/ML can increase 1%~2% prediction accuracy, evaluation results from 3 sources show that AI/ML can increase 4%~5% prediction accuracy and evaluation results from 2 sources show that AI/ML can increase about 10% prediction accuracy in terms of Top-1 beam prediction accuracy.
+ - wherein, 1 source used measurements from 3 time instances with measurement periodicity of 80ms. And AI/ML does not provide beam prediction accuracy gain comparing with 83.9% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 40ms. And it can decrease 5% beam prediction accuracy comparing with 97.18% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 80ms/160ms/240ms/320ms. And it may decrease up to 2% beam prediction accuracy comparing with about 73.8%~80.9% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 6 time instances with measurement periodicity of 40ms. And it can increase 4% beam prediction accuracy comparing with achieved 64.4% by non-AI baseline (Option 2) with 60km/h UE speed and 32 Tx beams
+
+- wherein, 1 source used measurements from 2 time instances with measurement periodicity of 160ms. And it can increase 4% beam prediction accuracy comparing with 52% achieved by non-AI baseline (Option 2) with 64 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 160ms. And it can increase 5% beam prediction accuracy comparing with 61.2% achieved by non-AI baseline (baseline 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 2 time instances with measurement periodicity of 80ms. And it can increase 1.9% beam prediction accuracy comparing with 93.2% achieved by non-AI baseline (baseline 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 5 time instances with measurement periodicity of 160ms. And it can increase 10.8% beam prediction accuracy comparing with achieved 82.2% by non-AI baseline (Option 2) with 30km/h UE speed and 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 40ms. And it can increase 1% beam prediction accuracy comparing with 85.8% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 8 time instances with measurement periodicity of 40ms. And it can increase about 2% beam prediction accuracy comparing with 67.4% achieved by non-AI baseline (Option 2) with 64 Tx beams
+ - wherein, 1 source used measurements from 3 time instances with measurement periodicity of 160ms. And it can increase about 9.2% and about 4.6% beam prediction accuracy comparing with 51.36% and 45.76% achieved by non-AI baseline (Option 2) with 30km/h and 60km/h UE speed respectively with 64 Tx beams
+- For 320ms prediction time, evaluation results from 7 sources show that AI/ML can increase about up to 3%~8% prediction accuracy, and evaluation results from 2 sources show that AI/ML can increase about 18.5%~23.5% prediction accuracy in terms of Top-1 beam prediction accuracy
+- wherein, 1 source used measurements from 2 time instances with measurement periodicity of 160ms. And it can increase 6% beam prediction accuracy comparing with 39.7% achieved by non-AI baseline (Option 2) with 64 Tx beams.
+ - wherein, 1 source used measurements from 6 time instances with measurement periodicity of 80ms. And it can increase 8% beam prediction accuracy comparing with achieved 55.5% by non-AI baseline (Option 2) with 60km/h UE speed and for 32 Tx beams
+ - wherein, 1 source used measurements from 3 time instances with measurement periodicity of 160ms. And it can increase 18.5% and 23.5% beam prediction accuracy comparing with 42.78% and 34.53% achieved by non-AI baseline (Option 2) with 30km/h and 60km/h UE speed respectively and for 64 Tx beams.
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 320ms. And it can increase 3.5% beam prediction accuracy comparing with 60.82% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 2 time instances with measurement periodicity of 80ms. And it can increase 3.2% beam prediction accuracy comparing with 90.1% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 5 time instances with measurement periodicity of 160ms. And it can increase 18.4% beam prediction accuracy comparing with 74.4% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 80ms. And it can increase 4.2% beam prediction accuracy comparing with 79.4% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 80ms/160ms/320ms/400ms /480ms/640ms. And it can increase up to 3.4% beam prediction accuracy comparing with about 69.5%~78.5% achieved by non-AI baseline (Option 2) with 32 Tx beams
+
+- wherein, 1 source used measurements from 8 time instances with measurement periodicity of 40ms. And it can increase about 3% beam prediction accuracy comparing with 29.1% achieved by non-AI baseline (Option 2) with 64 Tx beams
+- For 640ms prediction time, evaluation results from 5 sources show that AI/ML can increase 4.5~8% prediction accuracy, and evaluation results from 1 source show that AI/ML can increase up to 14.3% prediction accuracy in terms of Top-1 beam prediction accuracy, and evaluation results from 1 source show that AI/ML can increase up to 28.5% prediction accuracy in terms of Top-1 beam prediction accuracy
+ - wherein, 1 source used measurements from 2 time instances with measurement periodicity of 160ms. And it can increase 8% beam prediction accuracy comparing with 35.2% achieved by non-AI baseline (Option 2) with 64 Tx beams
+ - wherein, 1 source used measurements from 6 time instances with measurement periodicity of 160ms. And it can increase 14.3% beam prediction accuracy comparing with achieved 41.8% by non-AI baseline (Option 2) with 60km/h UE speed and 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 320ms. And it can increase 4.5% beam prediction accuracy comparing with 58% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 2 time instances with measurement periodicity of 80ms. And it can increase 5.4% beam prediction accuracy comparing with 84.4% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 5 time instances with measurement periodicity of 160ms. And it can increase 28.5% beam prediction accuracy comparing with 63.9% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 160ms. And it can increase 7.8% beam prediction accuracy comparing with 67.9% achieved by non-AI baseline (Option 2) with 32 Tx beams
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 160ms/320ms/640ms/800ms/960ms/1280ms. And it can increase up to 8.2% beam prediction accuracy comparing with about 62.7~74.3% achieved by non-AI baseline (Option 2) with 32 Tx beams
+- For 800ms prediction time, in terms of Top-1 beam prediction accuracy
+ - evaluation results from 1 source show that AI/ML can increase about 3.5% prediction accuracy comparing with 34.6% achieved by non-AI baseline (Option 2) with 64 Tx beams with measurements from 2 time instances in measurement periodicity of 160ms
+ - evaluation results from 1 source show that AI/ML can increase about 33.7% prediction accuracy comparing with achieved 58.6% by non-AI baseline (Option 2) 32 Tx beams with measurements from 5 time instances with measurement periodicity of 160ms
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 800ms/1600ms. And it can increase up to 9.1% beam prediction accuracy comparing with about 61.5~66.5% achieved by non-AI baseline (Option 2) with 32 Tx beams
+- For 960ms prediction time, in terms of Top-1 beam prediction accuracy
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 960ms/1920ms. And it can increase up to 10.6% beam prediction accuracy comparing with about 60.1~64.4% achieved by non-AI baseline (Option 2) with 32 Tx beams
+- For 1280ms prediction time, in terms of Top-1 beam prediction accuracy
+ - evaluation results from 1 source show that AI/ML can increase about 12.7% beam prediction accuracy comparing with 54.3% achieved by non-AI baseline (Option 2) with 32 Tx beams with measurements from 4 time instances with measurement periodicity of 320ms.
+
+- evaluation results from 1 source show that AI/ML can increase about 4%~13.4% beam prediction accuracy comparing with 54%~66.8% achieved by non-AI baseline (Option 2) with 32 Tx beams with measurements from 4 time instances with measurement periodicity of 320ms~2560ms.
+- evaluation results from 1 source show that AI/ML can increase up to 17.6% prediction accuracy for 3200ms prediction time.
+- evaluation results from 1 source show that AI/ML can increase up to 19.1% prediction accuracy for up to 12.8s prediction time.
+- Beam prediction accuracy gain in terms of Top-K prediction accuracy or Top-1 prediction accuracy with 1dB error is similar as or smaller than the beam prediction accuracy gain in terms of Top-1 prediction accuracy.
+- For the prediction time no larger than 1280ms, AI/ML and non-AI baseline (Option 2) can provide similar average L1-RSRP error, which are less than 1dB.
+
+**(B) For Tx DL beam prediction**, based on the evaluation from 2 sources, AI/ML **can** provide some beam prediction accuracy gain comparing with non-AI baseline (Option 2, sample-and-hold) **with UE rotation** and the performance of AI/ML compared to baseline (Option 2, sample-and-hold) improves with the increase of measurement periodicity:
+
+- **For 160ms/800ms/1200ms/1600ms prediction time**, evaluation results from 1 source show about 2%/8%/10%/13% prediction accuracy increase comparing with 74%/60%/53%/47.7% achieved by non-AI baseline (Option 2) with 32 Tx beam respectively in terms of Top-1 beam prediction accuracy, with measurements from 4 time instances in measurement periodicity of 160ms/800ms/ 1200ms/1600ms respectively.
+- In the evaluation, UE rotation is modelled every 20ms with a rotation speed uniformly distributed within {0, 60} RPM, and the rotation direction is {1/4 of data with randomly to left or right in horizontal, 1/4 of data always to left, 1/4 of data always to right, 1/4 of data to left and right in turn} with random initial directly.
+- **For 160ms/320ms/480ms/960ms prediction time**, evaluation results from 1 source show that AI/ML can increase 2%/3%/4.2%/7.3% Top-1 beam prediction accuracy compared to non-AI baseline (Option 2) with 78%/75.5%/73%/66.3% beam prediction accuracy with 12 Tx with measurement periodicity of 200ms/360ms/520ms/1000ms.
+- In the evaluation, UE rotation is modelled every 40ms with constant 10 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes.
+
+**(C) For Tx DL beam prediction (without UE rotation unless otherwise stated)**, AI/ML can provide good beam prediction accuracy with the less measurements/RS overhead:
+
+- Under the assumption of **setting Case A**, decent beam prediction accuracy can be achieved with **1/5~1/2** measurement/RS overhead reduction comparing the non-AI baseline (Option 1, with 100% prediction accuracy)
+- evaluation results from 1 source show that AI/ML can achieve 57% beam prediction accuracy, while non-AI baseline (Option 2) can only achieve 52% beam prediction accuracy in term of Top-1 beam prediction accuracy for 160ms prediction time,
+ - **1/3 RS/measurement overhead reduction** can be obtained with measurements from 2 time instances with measurement periodicity of 160ms.
+ - When prediction time increased to 320ms or larger, >50% Top-1 beam prediction accuracy is lower than 50% even with the help of AI/ML although it still can provide some gain compared with non-AI baseline (Option2).
+- evaluation results from 1 source show that AI/ML can achieve 60%~71% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 40ms up to 240ms prediction time
+ - **3/7 RS/measurement overhead reduction** can be obtained with measurements from 8 time instances with measurement periodicity of 40ms.
+ - When prediction time increased to 280ms or larger, >50% Top-1 beam prediction accuracy is lower than 50% even with the help of AI/ML
+- evaluation results from 1 source show that AI/ML can achieve 60.5% beam prediction accuracy in terms of Top-1 beam prediction accuracy for up to 320ms prediction time
+
+- **2/5 RS/measurement overhead reduction** can be obtained with measurements from 3 time instances with measurement periodicity of 160ms.
+- evaluation results from 1 source show that AI/ML can achieve 86.8%/83.6%/75.7%/67% beam prediction accuracy in terms of Top-1 beam prediction accuracy for up to 160ms/320ms/640ms/1280ms prediction time, respectively
+- **1/2 RS/measurement overhead reduction** can be obtained with measurements from 4 time instances with measurement periodicity of 40ms/80ms/160ms/320ms, respectively.
+- evaluation results from 1 source show that AI/ML can achieve 92% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms up to 800ms prediction time
+- **1/2 RS/measurement overhead reduction** can be obtained with measurements from 5 time instances with measurement periodicity of 160ms.
+- evaluation results from 1 source show that AI/ML can achieve 64%~68%/56%~63%/ 47%~56% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms/320ms/ 640ms prediction time respectively
+- **2/5 RS/measurement overhead reduction** can be obtained with measurements from 5 time instances with measurement periodicity of 40ms/80ms/160ms respectively.
+- evaluation results from 1 source show that AI/ML can achieve 62%~66% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms to 640ms prediction time
+- **1/5 RS/measurement overhead reduction** can be obtained with measurements from 4 time instances with measurement periodicity of 160ms to 640ms.
+- evaluation results from 1 source show that AI/ML can achieve 58.0%~80.1% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms to 12800ms prediction time
+- **up to 1/2 RS/measurement overhead reduction** can be obtained with measurements from 4 time instances with measurement periodicity of 160ms to 3200ms.
+- Under the assumption of **setting Case B**, evaluation results from 2 sources indicate that a certain beam prediction accuracy can be achieved with 1/2 ~ 7/10 measurement/RS overhead reduction comparing with non-AI schemes (Option 2)
+- evaluation results from 1 source show that AI/ML can provide **1/2 RS/measurement overhead reduction with UE rotation:**
+ - AI/ML can achieve ~65% beam prediction accuracy, while non-AI baseline (Option 2) can only achieve 48% beam prediction accuracy in term of Top-1 beam prediction accuracy for 1600ms prediction time/measurement periodicity
+ - With non-AI baseline (Option 2), similar prediction accuracy (~65% of Top-1 beam prediction accuracy) can be achieved with 800ms prediction time /measurement periodicity.
+ - In the evaluation, **UE rotation** is modelled every 20ms with a rotation speed of RPM = 60 R/M, and the rotation direction is {1/4 of data with randomly to left or right in horizontal, 1/4 of data always to left, 1/4 of data always to right, 1/4 of data to left and right in turn} with random initial directly.
+- evaluation results from 1 source show that AI/ML can provide **7/10 RS/measurement overhead reduction without UE rotation:**
+ - AI/ML can achieve ~64% beam prediction accuracy, while non-AI baseline (Option 2) can only achieve 46% beam prediction accuracy in term of Top-1 beam prediction accuracy for 3200ms prediction time
+ - With non-AI baseline (Option 2), similar prediction accuracy (~64% of Top-1 beam prediction accuracy) can be achieved with 960ms prediction time.
+- Under the assumption of **setting Case B+**, based on the evaluation results from 2 sources, good beam prediction accuracy can be achieved by AI/ML with measurement/RS overhead reduction compared to the non-AI baseline (Option 1, with 100% prediction accuracy) for which minimal periodicity of measurement is T<sub>per</sub>
+
+- evaluation results from 1 source with $T_{per} = 40\text{ms}$ show that AI/ML can provide 80%/88.9%/92.3%/96% RS/measurement overhead reduction:
+ - AI/ML can achieve 80%/78.5%/77.2%/73.6% beam prediction accuracy in terms of Top-1 beam prediction accuracy with 160ms/320ms/480ms/960ms prediction time 200ms/360ms/520ms/ 1000ms measurement periodicity.
+ - In the evaluation, UE rotation is modelled every 40ms with constant 10 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes.
+- evaluation results from 1 source with $T_{per} = 160\text{ms}\sim 3200\text{ms}$ show that AI/ML can provide 80% RS/measurement overhead reduction:
+ - AI/ML can achieve 50%~73% beam prediction accuracy in terms of Top-1 beam prediction accuracy with 640ms to 12800ms prediction time (4 prediction time instance) /800ms to 16000ms measurement periodicity (4 measurement time instance) without UE rotation.
+
+**(D) For beam pair prediction.** AI/ML may or may not provide beam prediction accuracy gain comparing with non-AI baseline (Option 2) for 160ms or less prediction time **without UE rotation**. For the longer the prediction time, the higher gain of beam prediction accuracy can be achieved by AI/ML:
+
+- For 160ms prediction time, evaluation results from 2 sources show AI/ML can provide similar performance or increase up to 1% prediction accuracy gain, evaluation results from 1 source show AI/ML may decrease 8% prediction accuracy, and evaluation results from 1 source show AI/ML can increase 13.8% prediction accuracy, in terms of Top-1 beam prediction accuracy.
+ - evaluation results from 1 source show that AI/ML decrease 8% prediction accuracy in terms of Top-1 beam prediction accuracy with measurements from 4 time instances with measurement periodicity of 160ms comparing with 68.1% achieved by non-AI baseline (Option 2) with 32 Tx beams and 8 Rx beams.
+ - evaluation results from 1 source show that AI/ML can increase 0.1% beam prediction accuracy in terms of Top-1 beam prediction accuracy with measurements from 4 time instances with measurement periodicity of 40ms comparing with 81.3% achieved by non-AI baseline (Option 2) with 32 Tx beams and 4 Rx beams.
+ - evaluation results from 1 source show that AI/ML decrease 0.1%~1% prediction accuracy in terms of Top-1 beam prediction accuracy with measurements from 4 time instances with measurement periodicity of 80ms~320ms comparing with 80.7%~83.4% achieved by non-AI baseline (Option 2) with 32 Tx beams and 8 Rx beams.
+ - evaluation results from 1 source show that AI/ML can increase 13.8% prediction accuracy in terms of Top-1 beam prediction accuracy with measurements from 5 time instances with measurement periodicity of 160ms comparing with 78.1% achieved by non-AI baseline (Option 2) with 32 Tx beams and 8 Rx beams.
+- For 320ms prediction time, evaluation results from 2 sources show that AI/ML can increase less than 3% prediction accuracy in terms of Top-1 beam prediction accuracy, and evaluation results from 1 source show that AI/ML can increase 22.5% prediction accuracy in terms of Top-1 beam prediction accuracy
+ - wherein, 1 source used measurements from 4 time instances with measurement periodicity of 80ms~640ms. With one AI/ML model to predict the beam at one or multiple time instances including 320ms, AI/ML may increase [less than 2%] beam prediction accuracy comparing with 78.8%~81.2% achieved by non-AI baseline (Option 2)
+ - Wherein, 1 source used measurements from 4 time instances with measurement periodicity of 80ms and it shows that AI/ML can increase 2.8% beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing with 74.5% achieved by non-AI baseline (Option 2).
+ - Wherein, 1 source used measurements from 5 time instances with measurement periodicity of 160ms and it shows that AI/ML can increase 22.5% prediction accuracy in terms of Top-1 beam prediction accuracy comparing with 69.2% achieved by non-AI baseline (Option 2) with 32 Tx beams and 8 Rx beams.
+- For 640ms prediction time, evaluation results from 2 sources show that AI/ML may be able to increase up to 7.5% prediction accuracy, and evaluation results from 1 source show that AI/ML can increase 34% prediction accuracy in terms of Top-1 beam prediction accuracy
+ - wherein, 1 source used measurements from 4 time instances
+
+- With one AI/ML model to predict the beam at 640ms with 640/1280ms as measurement periodicity, AI/ML can increase 6%/3.5% beam prediction accuracy comparing with 74.1%/73.5% achieved by non-AI baseline (Option 2).
+- With one AI/ML model to predict the beam at multiple prediction time instances (with two or more of 160ms 320ms, 480ms, 640ms) with different measurement periodicities (e.g., 160ms, 320ms, 800ms, 960ms), AI/ML can increase [0.7%~3.5%] beam prediction accuracy. From the evaluation results, the more target predicted time instances, the less performance gain can be obtained from AI/ML.
+- Wherein, 1 source used measurements from 4 time instances with measurement periodicity of 160ms and it shows that AI/ML can increase 7.5% beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing with 63.3% achieved by non-AI baseline (Option 2)
+- Wherein, 1 source used measurements from 5 time instances with measurement periodicity of 160ms and it shows that AI/ML can increase 34% prediction accuracy in terms of Top-1 beam prediction accuracy comparing with 57.16% achieved by non-AI baseline (Option 2) with 32 Tx beams and 8 Rx beams.
+
+###### - For 800ms prediction time,
+
+- evaluation results from 1 source show that AI/ML can to increase 6.7%~7.5% prediction accuracy in terms of Top-1 beam prediction accuracy
+ - wherein, measurements from 4 time instances with 800ms/1600ms as measurement periodicity were used and AI/ML can increase 6.7%/7.5% beam prediction accuracy respectively comparing with 72.9%/69.2% achieved by non-AI baseline (Option 2).
+- evaluation results from 1 source show that AI/ML can to increase 39.4% prediction accuracy in terms of Top-1 beam prediction accuracy
+ - wherein, measurements from 5 time instances with 160ms as measurement periodicity were used and AI/ML can increase 39.4% beam prediction accuracy comparing with 51.2% achieved by non-AI baseline (Option 2) with 32 Tx beams and 8 Rx beams.
+
+###### - For 960ms prediction time,
+
+- evaluation results from 1 source show that AI/ML may increase 12.8% beam prediction accuracy in terms of Top-1 beam prediction accuracy
+ - Wherein measurements from 5 time instances with measurement periodicity of 160ms, and predictions of 95 time instances with prediction periodicity of 10ms are assumed. AI/ML has 12.8% of beam prediction accuracy improvement in terms of Top 1 beam prediction accuracy comparing with 57.5% achieved by non-AI baseline (Option 2).
+- evaluation results from 1 source show that AI/ML may be able to increase up to 8.5% prediction accuracy in terms of Top-1 beam prediction accuracy
+ - measurements from 4 time instances with measurement periodicity of 960ms/1920ms were used respectively, with one model to predict single /multiple prediction time instances. AI/ML can increase 8.1%/8.5% beam prediction accuracy respectively comparing with 71.3%/67.7% achieved by non-AI baseline (Option 2).
+
+###### - For 1200ms/1600ms/2400ms/3200ms/4000ms prediction time, evaluation results from 1 source show that AI/ML may be able to increase up to 8.8%/ up to 10.7%/ up to 10.2%/up to 11.3%/up to 20.4% prediction accuracy in terms of Top-1 beam prediction accuracy respectively
+
+- measurements from 4 time instances were used with 1200ms/1600ms /1200ms/1600ms/4000ms as measurement periodicity respectively
+
+**(E)For beam pair prediction,** based on the evaluation results from 3 sources, AI/ML **may or may not** provide beam prediction accuracy gain comparing with non-AI baseline (Option 2) **with UE rotation:**
+
+###### - For 160ms prediction time, in terms of Top-1 beam prediction accuracy
+
+- evaluation results from 1 source show that AI/ML may decrease 10% prediction accuracy with measurements from 4 time instances with measurement periodicity of 160ms. In this case, non-AI baseline (option 2) can achieve 51.09% beam prediction accuracy.
+
+- In the evaluation, UE rotation is modelled every 20ms with a rotation speed uniformly distributed within {0, 60} RPM, and the rotation direction is {1/4 of data with randomly to left or right in horizontal, 1/4 of data always to left, 1/4 of data always to right, 1/4 of data to left and right in turn} with random initial directly.
+- For 200ms prediction time, in terms of Top-1 beam prediction accuracy with 10 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes
+ - evaluation results from 1 source show that AI/ML can increase [1%~1.6%] prediction accuracy with measurement periodicity of 240ms with different AI/ML models. In this case, non-AI baseline (option 2) can achieve 67.4% beam prediction accuracy
+- For 200ms prediction time, in terms of Top-1 beam prediction accuracy with 100 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes
+ - evaluation results from 1 source show that AI/ML can increase 23%~30% prediction accuracy with measurement periodicity of 240ms with different AI/ML models. In this case, non-AI baseline (option 2) can only achieve 17% beam prediction accuracy.
+- For 500ms prediction time, in terms of Top-1 beam prediction accuracy with 10 RPM rotation speed to fixed a direction
+ - evaluation results from 1 source show that AI/ML can increase 6%/8%/11% prediction accuracy with measurements from 1/2/5 time instances in measurement periodicity of 100ms respectively
+ - evaluation results from 1 source show that AI/ML can increase 11%/11.5%/12.5% prediction accuracy with measurements from 1/2/5 time instances in measurement periodicity of 50ms respectively
+- For 800ms prediction time, in terms of Top-1 beam prediction accuracy
+ - evaluation results from 1 source show that AI/ML may decrease 6% prediction accuracy with measurements from 4 time instances with measurement periodicity of 800ms. In this case, non-AI baseline (option 2) can achieve 30.19% prediction accuracy.
+ - In the evaluation, UE rotation is modelled every 20ms with a rotation speed uniformly distributed within {0, 60} RPM, and the rotation direction is {1/4 of data with randomly to left or right in horizontal, 1/4 of data always to left, 1/4 of data always to right, 1/4 of data to left and right in turn} with random initial directly.
+
+**(F) For beam pair prediction.** (without UE rotation unless otherwise stated), AI/ML can provide good beam prediction accuracy with the less measurements/RS overhead:
+
+- Under assumption of **setting Case A**, decent beam prediction accuracy can be achieved with up to 1/2 measurement/RS overhead comparing with no time domain prediction.
+- evaluation results from 1 source show that AI/ML can achieve 81.4%/77.3%/70.8%/61.8% beam prediction accuracy in terms of Top-1 beam prediction accuracy for up to 160ms/320ms/640ms/1280ms prediction time, respectively
+ - **1/2 RS/measurement overhead reduction** can be obtained with measurements from 4 time instances with measurement periodicity of 40ms/80ms/160ms/320ms.
+- evaluation results from 1 source show that AI/ML can achieve 90%~92% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms up to 800ms prediction time
+ - **1/2 RS/measurement overhead reduction** can be obtained with measurements from 5 time instances with measurement periodicity of 160ms.
+- evaluation results from 1 source show that AI/ML can achieve 79%~84% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 80ms to 640ms prediction time without UE rotation for beam pair
+ - **up to 1/2 RS/measurement overhead reduction** can be obtained with measurements from 4 time instances with measurement periodicity of 80ms or 160ms.
+
+- evaluation results from 1 source show that AI/ML can achieve 71.9% /67.4%/64.4% for 30km/h /60km/h /90km/h beam prediction accuracy respectively in terms of Top-1 beam prediction accuracy for 800ms prediction time.
+ - 1/2 RS/measurement overhead reduction can be obtained with measurements from 5 time instances with measurement periodicity of 160ms.
+- Under assumption of **setting Case B**, based on the evaluation from 2 sources a certain beam prediction accuracy can be achieved with 1/2 or 3/5 measurement/RS overhead reduction comparing with non-AI schemes with 30km/h respectively
+ - evaluation results from 1 source show that AI/ML can provide 1/2 or 2/3 or 3/4 RS/measurement overhead reduction without UE rotation for 30km/h /60km/h /90km/h respectively
+ - AI/ML can achieve 70.3%/77.1%/79.8% beam prediction accuracy with 30km/h /60km/h /90km/h respectively, while non-AI baseline (Option 2) can only achieve 57.2%/36%/36% beam prediction accuracy in term of Top-1 beam prediction accuracy for 960ms/960ms/640ms prediction time/measurement periodicity for 30km/h /60km/h /90km/h respectively.
+ - With non-AI baseline (Option 2), similar prediction accuracy (76.7% of Top-1 beam prediction accuracy) can be achieved with 480ms/320ms/160ms measurement periodicity for 30km/h /60km/h /90km/h respectively.
+ - evaluation results from 1 source show that AI/ML can provide 3/5 RS/measurement overhead reduction without UE rotation
+ - AI/ML can achieve 77.6% beam prediction accuracy, while non-AI baseline (Option 2) can only achieve 66.9% beam prediction accuracy in term of Top-1 beam prediction accuracy for 1600ms prediction time.
+ - With non-AI baseline (Option 2), similar prediction accuracy (74.1% of Top-1 beam prediction accuracy) can be achieved with 640ms prediction time.
+- Under the assumption of **setting Case B+**, based on the evaluation from 1 source decent beam prediction accuracy can be achieved with 80% measurement/RS overhead comparing the non-AI baseline (Option 1, with 100% prediction accuracy) with T<sub>per</sub>=160ms to 960ms as minimal periodicity of measurement
+ - evaluation results from 1 source show that AI/ML can provide 80% RS/measurement overhead reduction:
+ - AI/ML can achieve 68%~77% beam prediction accuracy in terms of Top-1 beam prediction accuracy with 640ms to 3840ms prediction time (4 prediction time instance) /800ms to 4800ms measurement periodicity (4 measurement time instance) without UE rotation.
+
+##### 6.3.2.2.2 Performance when Set B is a subset of Set A
+
+For **BM-Case2**, when *Set B pattern is a subset of Set A* in each time instance, for DL Tx beam prediction with the measurements from the best Rx beam or Tx-Rx beam pair prediction, without considering generalization aspects, with the following assumptions:
+
+- UE speed: 30km/h (unless otherwise stated)
+- Prediction time: 40ms/80ms/160ms/320ms/640ms/others
+- With and without UE rotation
+- Fixed Set B patterns or preconfigured Set B patterns in each measurement instances (unless otherwise stated)
+
+Note that ideal measurements are assumed:
+
+- Beams could be measured regardless of their SNR.
+- No measurement error.
+- No quantization for the L1-RSRP measurements.
+- No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+
+Note: In some evaluations results, non-AI baseline (Option 2) may have better performance in terms of Top-1 beam prediction accuracy than the ratio of Set B/Set A. This is because the Top-1 beam distribution among Set A of beams are not uniform while the Set B pattern may be well designed or happen to be the beams that have high probability to be the Top-1 beam.
+
+Note: non-AI baseline Option 2: sample and hold based on the measurements in the last time instance (unless otherwise stated)
+
+**(A) For Tx DL beam prediction without UE rotation.** AI/ML can provide good beam prediction accuracy and gain comparing with non-AI baseline (Option 2) with same RS/measurement overhead:
+
+- With measurements of **fixed Set B or variable Set B with pre-configured patterns** of beams that of 1/2 of Set A of beams in one time instance,
+ - **1/2 RS overhead** in spatial domain can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Top-1 DL Tx beam prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 86.4%/83.5% prediction accuracy for prediction time 40ms/160ms, with 32 Tx beam in Set A, and Set B is different in each time instance.
+ - wherein, measurements from 3 time instances with measurement periodicity of 80ms are used.
+ - wherein, 80.5%/70% prediction accuracy can be achieved by non-AI baseline (Option 2) with assumption that the selection of 1/2 of beams selected in baseline are the most frequently used in the evaluated scenario.
+ - evaluation results from 1 source show that AI/ML can achieve 94.5%/93.7%/92.1% prediction accuracy for prediction time 80ms/160ms/320ms with 32 Tx beam in Set A, and Set B is the same in each time instance.
+ - wherein, measurements from 2 time instances with measurement periodicity of 80ms are used
+ - wherein, 71%/69.9%/68% prediction accuracy can be achieved by non-AI baseline with the assumption that 16 Tx beams are measured in total and preferred beam pattern is used.
+ - where the Rx beam of best beam pair within Set A is assumed to obtained the measurement of Set B.
+ - evaluation results from 1 source show that AI/ML can achieve 67.1%/65.01% prediction accuracy for prediction time 80ms with 32 Tx beam in Set A for 30km/h/60km/h respectively, and Set B is the same in each time instance.
+ - wherein, measurements from 5 time instances with measurement periodicity of 80ms are used
+ - wherein, 44.35%/44.29% prediction accuracy can be achieved for 30km/h/60km/h respectively by non-AI baseline (Option 2)
+ - evaluation results from 1 source show that AI/ML can achieve 75.34% prediction accuracy for prediction time 160ms with 32 Tx beams in Set A for 30km/h, and Set B is the same in each time instance.
+ - wherein, measurements from 4 time instances with measurement periodicity of 160ms are used
+ - wherein, 44.36% prediction accuracy can be achieved for 30km/h by non-AI baseline (Option 2).
+- With measurements of **fixed Set B or variable Set B with pre-configured patterns** of beams that of 1/4 of Set A of beams in one time instance,
+ - **1/4 RS overhead** in spatial domain can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Top-1 DL Tx beam prediction accuracy:
+
+- evaluation results from 1 source show that AI/ML can achieve 93.4%/92.4%/90.5% and 91.3%/90.6%/89.1% prediction accuracy for prediction time 80ms/160ms/320ms, with 32 Tx beam in Set A, and Set B is different and same in each time instance respectively
+ - wherein, measurements from 2 instances with measurement periodicity of 80ms are used respectively.
+ - Wherein, 70.5%/69.4%/67.4% and 42.5%/42.2%/41.5% prediction accuracy can be achieved by non-AI baseline (Option 2) with the assumption that 16 Tx beams are measured in total and preferred beam pattern is used.
+ - Where the Rx beam of best beam pair within Set A is assumed to obtained the measurement of Set B.
+- evaluation results from 1 source show that AI/ML can achieve 56.4%/52.7% prediction accuracy for prediction time 80ms/160ms, with 64 Tx beam in Set A and Set B is the same in each time instance
+ - wherein, measurements from 2 time instances with measurement periodicity of 80ms/160ms are used respectively
+ - wherein, 63.25%/58.45% prediction accuracy can be achieved by non-AI baseline (Option 1) when measuring Set A during observation and then applying sample-and-hold
+- evaluation results from 1 source show that AI/ML can achieve 83.15%/79.53%/79.43% prediction accuracy for prediction time 40ms/80ms/160ms, with 32 Tx beam in Set A and Set B is the same in each time instance
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms are used,
+ - 32.8%/32.8%/32.7% prediction accuracy can be achieved by non-AI baseline (Option 2)
+ - Wherein, the Rx beam of best beam pair within Set A is assumed to obtained the measurement of Set B.
+- evaluation results from 1 source show that AI/ML can achieve 88%~90% prediction accuracy for prediction time 160ms/320ms/480ms/640ms/800ms, with 32 Tx beam in Set A and Set B is the same in each time instance
+ - wherein, measurements from 5 time instances with measurement periodicity of 160ms are used,
+ - 16%~22% prediction accuracy can be achieved by non-AI baseline (Option 2)
+ - Where the best Rx beam for each Tx beam within Set B is assumed to obtained the measurement of Set B.
+- evaluation results from 1 source show that AI/ML can achieve 88%/86%/ 82% prediction accuracy for prediction time 40ms/160ms/320ms, with 32 Tx beam in Set A and Set B is the same in each time instance
+ - wherein, measurements from 8 time instances with measurement periodicity of 40ms are used,
+ - 36.2%/35.8%/35.3% prediction accuracy can be achieved by non-AI baseline (Option 2) on the best Tx beam with highest L1-RSRP in the all time instances
+ - for random Set B pattern (Set B/Set A=1/4, the SetB is randomly changed in Set A in each time instance), compared to the above case, for Top-1 beam prediction accuracy, evaluation results show about 6% beam prediction accuracy degradation.
+ - wherein, the Rx beam of best beam pair within Set B is assumed to obtained the measurement of Set B
+- evaluation results from 1 source show that AI/ML can achieve 73.8%/73.3% and 76.9%/73.08% prediction accuracy for prediction time 160ms/320ms, with 32 Tx beam in Set A, and Set B is the same and different in each time instance respectively
+ - wherein, measurements from 4 time instances with measurement periodicity of 160ms/320ms are used respectively,
+ - 24%/24.7% and 18.1%/17% prediction accuracy can be achieved for same and different Set B pattern respectively with non-AI baseline (Option 2)
+
+- evaluation results from 1 source show that AI/ML can achieve 61.9%/56.35% prediction accuracy for prediction time 80ms with 32 Tx beam in Set A for 30km/h/60km/h respectively, and Set B is the same in each time instance.
+ - wherein, measurements from 5 time instances with measurement periodicity of 80ms are used
+ - wherein, 20.3%/22% prediction accuracy can be achieved for 30km/h/60km/h respectively by non-AI baseline (Option 2)
+- evaluation results from 1 source show that AI/ML can achieve 61.7%~55.6% prediction accuracy for prediction time 80ms~960ms, with 32 Tx beam in Set A, and Set B is the same in each time instance
+ - wherein, measurements from 4 time instances with measurement periodicity of equal to or 2 times of the prediction time are used respectively,
+ - 18.6%~8.8% prediction accuracy can be achieved for same Set B pattern with non-AI baseline (Option 2) based on the measurements of the last time instance
+ - Note: RS overhead reduction
+ - Under the assumption of setting Case A, AI/ML can achieve 57.8%~61.0% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms to 960ms prediction time
+ - up to 4/5 RS/measurement overhead reduction can be obtained with measurements from 4 time instances with measurement periodicity of 160ms to 960ms.
+ - Under the assumption of setting Case B, AI/ML can provide more than 90% RS/measurement overhead reduction:
+ - AI/ML can achieve 58% beam prediction accuracy, while non-AI baseline (Option 2) can only achieve 10% beam prediction accuracy in term of Top-1 beam prediction accuracy for 960ms prediction time
+ - with non-AI baseline (Option 2), 18.6% of Top-1 beam prediction accuracy can be achieved with 80ms prediction time.
+ - Under the assumption of setting Case B+, AI/ML can provide 87.5% RS/measurement overhead reduction:
+ - AI/ML can achieve 55.6%~59.5% beam prediction accuracy in terms of Top-1 beam prediction accuracy with 160ms to 960ms prediction time 320ms to 1920ms measurement periodicity (4 measurement time instance).
+- evaluation results from 1 source show that AI/ML can achieve 67.25% prediction accuracy for prediction time 160ms with 32 Tx beams in Set A for 30km/h, and Set B is the same in each time instance.
+ - wherein, measurements from 4 time instances with measurement periodicity of 160ms are used
+ - wherein, 23.95% prediction accuracy can be achieved for 30km/h by non-AI baseline (Option 2).
+- With measurements of fixed Set B or variable Set B with pre-configured patterns of beams that of 1/8 of Set A of beams in one time instance,
+ - **1/8 RS overhead** in spatial domain can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Top-1 DL Tx beam prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 67.4%/67.8%/70%/66.9%/67.5%/64.9%/62.9% prediction accuracy for prediction time 160ms/320ms/480ms/640ms/800ms/960ms, with 32 Tx beam in Set A, and Set B is the same in each time instance.
+ - wherein, measurements from 8 time instances with measurement periodicity of 160ms are used
+ - 9%/8.9%/8.8%/8.7%/8.5%/8.4% prediction accuracy can be achieved by non-AI scheme (Option 2)
+
+- evaluation results from 1 source show that AI/ML can achieve 94%/93.5%/92.6%/90.7% prediction accuracy for prediction time 40ms/80ms/160ms/320ms, with 32 Tx beam in Set A, and Set B is different in each time instance respectively
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms is used.
+ - wherein, 70.7%/70.2%/69.1%/67.2% prediction accuracy can be achieved by non-AI baseline (Option 2) with the assumption that 16 Tx beams are measured in total and preferred beam pattern is used.
+ - where the Rx beam of best beam pair within Set A is assumed to obtained the measurement of Set B.
+- evaluation results from 1 source show that AI/ML can achieve 76.1%/75.2%/70.7% prediction accuracy for prediction time 40ms/80ms/160ms, with 32 Tx beam in Set A and Set B is the same in each time instance
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms are used,
+ - 18.0%/17.9%/17.8% prediction accuracy can be achieved by non-AI baseline (Option 2)
+ - wherein the Rx beam of best beam pair within Set A is assumed to obtained the measurement of Set B.
+- evaluation results from 1 source show that AI/ML can achieve 81.7%/81.1%/80.6% prediction accuracy for prediction time 40ms/160ms/320ms, with 32 Tx beam in Set A and Set B is the same in each time instance
+ - wherein, measurements from 8 time instances with measurement periodicity of 40ms are used,
+ - 30.7%/30.4%/30% prediction accuracy can be achieved by non-AI baseline (Option 2) based on the best Tx beam with highest L1-RSRP in all the time instances
+ - for random Set B pattern (SetB/SetA=1/8, the SetB is randomly changed in Set A in each time instance), compared to the above case, for Top-1 beam prediction accuracy, evaluation results show about 5% beam prediction accuracy degradation.
+ - wherein, the Rx beam of best beam pair within Set B is assumed to obtained the measurement of Set B
+- evaluation results from 1 source show that AI/ML can achieve 56.91% prediction accuracy for prediction time 160ms with 32 Tx beams in Set A for 30km/h, and Set B is the same in each time instance.
+ - wherein, measurements from 4 time instances with measurement periodicity of 160ms are used
+ - wherein, 18.75% prediction accuracy can be achieved for 30km/h by non-AI baseline (Option 2).
+
+**(B) For Tx DL beam prediction with UE rotation**, based on evaluation from 2 sources, AI/ML can provide good beam prediction accuracy and gain comparing with non-AI baseline (Option 2) with same RS/measurement:
+
+- With measurements of **fixed Set B** of beams that of **1/3** of Set A of beams in one time instance. (Note that more RS overhead can be achieved considering additional temporal domain RS overhead reduction)
+ - **1/3 RS overhead** in spatial domain can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+- Evaluation results from 1 source show that AI/ML can achieve
+ - 77.5% Top-1 beam prediction accuracy for 160ms prediction time and 200ms measurement periodicity wherein, 33.4% prediction accuracy can be achieved by non-AI baseline (Option 2), and 43.3% beam prediction accuracy can be achieved by a combination of spatial interpolation (radial basis function interpolation) followed by sample-and-hold.
+ - Under the assumption of Case B+, 93.3% RS overhead reduction can be achieved compared to non-AI baseline (Option 1) assuming all Set A of beams needs to be measured every 40ms at each time instances for measurement and prediction.
+ - Wherein, UE rotation is modelled every 40ms with constant 10 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes.
+
+- With measurements of **variable Set B** (with preconfigured Set B pattern in each time instances) of beams that of **1/3** of Set A of beams in one time instance,
+ - **1/3 RS overhead** in spatial domain can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Evaluation results from 1 source show that AI/ML can achieve
+ - 78%/76%/73.8%/68.6% Top-1 beam prediction accuracy for 160ms/320ms/480ms/960ms prediction time and 200ms/360ms/520ms/1000ms measurement periodicity
+ - wherein, 71.5%/63%/56.5%/45.3% prediction accuracy can be achieved by non-AI baseline (Option 2), in which for each prediction instance, the latest measurement for each beam in Set A is used as the predicted value for that beam.
+ - wherein, Set B patterns in Set A/Set B consecutive time slots partition Set A.
+ - Under the assumption of Case B+, **93.3%/96.3%/97.4%/98.7% RS overhead reduction** can be achieved compared to non-AI baseline (Option 1) assuming all Set A of beams needs to be measured every 40ms at each time instances for measurement and prediction for 160ms/320ms/480ms/960ms prediction time.
+ - Wherein, UE rotation is modelled every 40ms with constant 10 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes.
+- With measurements of **fixed Set B** of beams that of **1/4** of Set A of beams in one time instance,
+ - **1/4 RS overhead** in spatial domain can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Top-1 DL Tx beam prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 71.8%/57.3% prediction accuracy for prediction time 160ms/320ms, with 32 Tx beam in Set A, and Set B is the same in each time instance respectively
+ - wherein, measurements from 4 time instances with measurement periodicity of 160ms/320ms are used respectively,
+ - 24.3%/14.2% prediction accuracy can be achieved for same and different Set B pattern respectively with non-AI baseline (Option 2)
+ - Wherein, UE rotation is modelled every 20ms with a rotation speed uniformly distributed within {0, 60} RPM, and the rotation direction is {1/4 of data with randomly to left or right in horizontal, 1/4 of data always to left, 1/4 of data always to right, 1/4 of data to left and right in turn} with random initial directly.
+
+**(C) For beam pair prediction without UE rotation.** based on evaluation of most sources, AI/ML can provide good beam prediction accuracy and gain comparing with non-AI baseline (Option 2) with same RS/measurement overhead.
+
+- With measurements of fixed Set B or variable Set B with preconfigured pattern in each time instance of beams that of **1/4** of Set A of beams in one time instance,
+ - **1/4 RS overhead** can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Top-1 beam pair prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 76.3%/74.7%/72% prediction accuracy for prediction time 40ms/80ms/160ms, with 32 Tx beams and 8 Rx beams in Set A, and Set B is the same in each time instance
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms are used
+
+- 32.7%/32.6%/32.5% prediction accuracy can be achieved by non-AI baseline (Option 2)
+- evaluation results from 1 source show that AI/ML can achieve 88%~90% prediction accuracy for prediction time 160ms/320ms/480ms/640ms/800ms, with 32 Tx beams and 8 Rx beams in Set A, and Set B is the same in each time instance
+ - wherein, measurements from 5 time instances with measurement periodicity of 160ms are used
+ - 19%~23% prediction accuracy can be achieved by non-AI baseline (Option 2)
+- evaluation results from 1 source show that AI/ML can achieve 80.97%/80.17%/75.86% prediction accuracy for prediction time 40ms/80ms/160ms, with 32 Tx beam and 4 Rx beam in Set A, and Set B is the same in each time instance
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms are used,
+ - 38.6%/38.0%/37.2% prediction accuracy can be achieved by non-AI baseline (Option 2)
+- evaluation results from 1 source show that AI/ML can achieve 63.2%/~57.7% prediction accuracy for prediction time 80ms~960ms, with 32 Tx beam and 8 Rx beam in Set A, and Set B is the same in each time instance
+ - wherein, measurements from 4 time instances with measurement periodicity same as or 2 times of the prediction time are used
+ - 22.3%~10.7% prediction accuracy can be achieved by non-AI baseline (Option 2)
+ - RS overhead reduction
+ - Under the assumption of setting Case A, AI/ML can achieve 58.1%~62.0% beam prediction accuracy in terms of Top-1 beam prediction accuracy for 160ms to 960ms prediction time, up to 4/5 RS/measurement overhead reduction can be obtained with measurements from 4 time instances with measurement periodicity of 160ms to 960ms.
+ - Under the assumption of setting Case B, AI/ML can provide more than 90% RS/measurement overhead reduction:
+ - AI/ML can achieve 58.1% beam prediction accuracy, while non-AI baseline (Option 2) can only achieve 12.7% beam prediction accuracy in term of Top-1 beam prediction accuracy for 960ms prediction time
+ - With non-AI baseline (Option 2), 22.3% of Top-1 beam prediction accuracy can be achieved with 80ms prediction time.
+ - Under the assumption of setting Case B+, AI/ML can provide 87.5% RS/measurement overhead reduction:
+ - AI/ML can achieve 57.1%~60.7% beam prediction accuracy in terms of Top-1 beam prediction accuracy with 160ms to 960ms prediction time /320ms to 1920ms measurement periodicity (4 measurement time instance).
+- evaluation results from 1 source show that AI/ML can achieve 48.2%/51.6% prediction accuracy for prediction time 160ms, with 32 Tx beam and 8 Rx beam in Set A, and Set B is the same and different in each time instance respectively
+ - wherein, measurements from 4 time instances with measurement periodicity of 160ms are used,
+ - 16.2%/22.9% prediction accuracy can be achieved by non-AI baseline (Option 2) based on the measurements of the last time instance
+- With measurements of fixed Set B of beams that of 1/8 of Set A of beams in one time instance,
+ - **1/8 RS overhead** can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+
+- Top-1 beam pair prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 76.7%/74.1%/73.6% prediction accuracy for prediction time 40ms/160ms/320ms, with 256 (32Tx\*8Rx) beam pairs in Set A and Set B (4Tx\*8Rx) is the same in each time instance
+ - wherein, measurements from 8 time instances with measurement periodicity of 40ms are used,
+ - 30.1%/29.7%/29.1% prediction accuracy can be achieved by non-AI baseline (Option 2) based on the measurements in all time instances
+ - evaluation results from 1 source show that AI/ML can achieve 77.0%/76.2%/72.0% and 74.2%/73.0%/69.8% prediction accuracy for prediction time 40ms/80ms/160ms, with 32 Tx beams and 4 Rx beams in Set A, and Set B is the same in each time instance with all measurements from all Rx beams and half of Rx beams respectively
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms are used,
+ - 9.88%/9.60%/8.95% and 14.57%/14.45%/14.27% prediction accuracy can be achieved by non-AI baseline (Option 2) for the case with all Rx beams and half of Rx beams respectively
+- With measurements of fixed Set B or variable Set B with pre-configured pattern in each time instance of beams that of **1/16** of Set A of beams in one time instance,
+ - **1/16 RS overhead** can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+- Top-1 beam pair prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 50.58%/48.71%/44.33% and 63.94%/63.31%/60.49% prediction accuracy for 40ms/80ms/160ms prediction time with 32 Tx beam in Set A, and Set B is the same in each time instance with {8 Tx and 2 Rx} and {4 Tx and all Rx} respectively.
+ - wherein, measurements from 4 time instances with measurement periodicity of 40ms are used
+ - 8.96%/8.91%/8.89% and 4.7%/4.56%/4.3% prediction accuracy can be achieved by non-AI scheme (Option 2) for the case with from all Rx beams and half of Rx beams respectively
+ - evaluation results from 1 source show that AI/ML can achieve 89.1% / 86.4% / 82.9% prediction accuracy for prediction time 40ms/160ms/320ms, with 256 (32Tx\*8Rx) beam pairs in Set A and Set B (2Tx\*8Rx) is different in each time instance
+ - wherein, measurements from 8 time instances with measurement periodicity of 40ms are used,
+ - 69.4%/67.8%/66% prediction accuracy can be achieved by non-AI baseline (Option 2) based on the measurements in all time instances
+
+**(D) For beam pair prediction with UE rotation,** evaluations from 2 sources show AI/ML can provide 44% or 15% beam prediction accuracy gain comparing with non-AI baseline (Option 2) with same RS/measurement overhead, with 78% or 30%~35% Top-1 beam prediction accuracy respectively.
+
+- With measurements of fixed Set B or variable Set B with pre-configured pattern in each time instance of beams that of **1/4** of Set A of beams in one time instance,
+ - **1/4 RS overhead** can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+- Top-1 beam pair prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 35.02%/29.2% prediction accuracy for prediction time 40ms/160ms, with 32 Tx beam and 8 Rx beam in Set A, and Set B is the same and different in each time instance respectively
+
+- wherein, measurements from 4 time instances with measurement periodicity of 40ms/160ms are used,
+- 19.7%/15.6% prediction accuracy can be achieved by non-AI baseline (Option 2) based on the measurements of the last time instance
+- UE rotation is modelled every 20ms with a rotation speed uniformly distributed within {0, 60} RPM, and the rotation direction is {1/4 of data with randomly to left or right in horizontal, 1/4 of data always to left, 1/4 of data always to right, 1/4 of data to left and right in turn} with random initial directly.
+- With measurements of variable Set B with pre-configured patterns in each time instance of beams that of 1/16 of Set A of beams in one time instance,
+ - **1/16 RS overhead** can be achieved comparing with non-AI baseline (Option 1) assuming all Set A of beams needs to be measured at each time instances for measurement and prediction. More RS overhead can be achieved considering additional temporal domain RS overhead reduction.
+ - Top-1 beam pair prediction accuracy:
+ - evaluation results from 1 source show that AI/ML can achieve 78.1% prediction accuracy for prediction time 40ms with 32 Tx beams and 8 Rx beams in Set A, Set B is different in each time instance and 10 RPM rotation speed to fixed a direction
+ - wherein, measurements from 3 time instances with measurement periodicity of 40ms or 80ms are used
+ - 42.4%/42.5% prediction accuracy can be achieved by non-AI scheme (Option 2).
+
+#### 6.3.2.3 Performance under different assumptions/scenarios for BM-Case1 and/or BM-Case2
+
+##### Performance with quantization:
+
+At least for BM-Case1 for inference of DL Tx beam with L1-RSRPs of all beams in Set B, existing quantization granularity of L1-RSRP (i.e., 1 dB for the best beam, 2 dB for the difference to the best beam) causes a minor loss in beam prediction accuracy compared to unquantized L1-RSRPs of beams in Set B.
+
+- Evaluation results from 13 sources show less than 5% beam prediction accuracy degradation in terms of Top-1 beam prediction accuracy.
+- Note: 1 source uses the data without quantization for training and data with quantization for inference. Other sources use the same quantization scheme for data for training and inference.
+
+At least for BM-Case1 for inference of DL Tx beam with L1-RSRPs of all beams in Set B,
+
+- Evaluation results from 4 sources show that, with 1dB quantization step for the absolute L1-RSRP of the best beam and 4dB quantization step differential L1-RSRP report with the existing quantization range, less than 5% beam prediction accuracy degradation in terms of Top-1 beam prediction accuracy compared to unquantized L1-RSRPs of beams in Set B.
+- Same quantization scheme is used for the input data for training and inference.
+- Note: 1 source used quantized L1-RSRPs with the same quantization scheme as labels in training.
+- Note: 1 source used unquantized L1-RSRPs as labels in training.
+- Note: 1 source used unquantized L1-RSRPs to determine Top-1 beam id as labels in training.
+
+##### Performance with measurement error
+
+**For BM-Case1 DL Tx beam prediction** (unless otherwise stated), when *Set B is a subset* (1/4 unless otherwise stated) *of Set A*, without differentiating **BB errors and RF errors** modelled as truncated Gaussian distribution (unless otherwise stated),
+
+- Considering $\pm 2$ dB relative measurement error,
+
+- evaluation results from 3 sources show that the beam prediction accuracy degrades 6%~10% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error. And 1 source shows that 95%ile of L1-RSRP diff can be about 1.4~2dB, 1 source shows that average L1-RSRP diff can be lower than 1dB.
+- evaluation results from 1 source show that
+ - for DL Tx beam prediction, the beam prediction accuracy degrades 28.8% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error, [and average L1-RSRP diff can be about 7.3dB.
+ - for Tx-Rx beam pair prediction when Set B is 1/8 of Set A, the beam prediction accuracy degrades 2.4% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error, and average L1-RSRP diff can be about 5.8dB
+ - wherein the measurement error is modelled as uniformed distribution.
+- evaluation results from 1 source show that considering different relative measurement error range in model training ( $\pm 2$ dB, $\pm 0$ dB), similar (less than 1% difference) Top-1 beam prediction accuracy can be achieved
+- Considering $\pm 3$ or $\pm 4$ dB relative measurement error,
+ - evaluation results from 4 sources show that the beam prediction accuracy degrades 14% (with 3dB error) ~20% (with 4dB error) in terms of Top-1 beam prediction accuracy comparing to the one without measurement error. And 1 source shows that the 95%ile of L1-RSRP diff can be about 2~3.2dB. 1 source shows that average L1-RSRP diff can be lower than 1dB.
+ - evaluation results from 1 source show that considering different relative measurement error range in model training (0dB, $\pm 2$ dB, $\pm 4$ dB), similar (less than 1% difference) Top-1 beam prediction accuracy can be achieved, and average L1-RSRP diff can be lower than 1dB when $\pm 2$ dB or $\pm 4$ dB relative measurement error is considered in model training
+- Considering up to $\pm 5$ dB relative measurement error when Set B is 1/8 of Set A,
+ - evaluation results from 1 source show that the beam prediction accuracy degrades 13.6% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error for DL Tx beam prediction.
+- Considering $\pm 6$ dB relative measurement error,
+ - evaluation results from 3 sources show that the beam prediction accuracy degrades 22%~30% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error. And the 95%ile of L1-RSRP diff can be about 3.1~7.5dB.
+ - evaluation results from 1 source show that the L1-RSRP difference in 90%ile degrades 7dB for the AI/ML model, compared to baseline 1 and 2 that degrades 3 dB respectively 1 dB at the same percentile.
+ - evaluation results from 1 source show that for both DL Tx beam prediction and beam pair prediction, the beam prediction accuracy degrades 42%~48% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error. And the average L1-RSRP diff can be about 1.6dB.
+ - However, comparing with the global search of all beams in Set A with the same measurement error level, for DL Tx beam prediction the beam prediction accuracy degrades less than 1% in terms of Top-1 beam prediction accuracy, and for Tx-Rx beam pair prediction the beam prediction accuracy degrades about 7% in terms of Top-1 beam prediction accuracy.
+ - Note: in this evaluation, measurement errors are considered in training and inference phase only for AI inputs with ideal labels in training phase.
+- evaluation results from 1 source show that
+ - for DL Tx beam prediction, the beam prediction accuracy degrades 32.4% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error, [and average L1-RSRP diff can be about 8.34dB.
+ - for Tx-Rx beam pair prediction, the beam prediction accuracy degrades 5.2% in terms of Top-1 beam prediction accuracy comparing to the one without measurement error, [and average L1-RSRP diff can be about 6.4dB.
+
+- evaluation results from 1 source show that considering different relative measurement error range in model training (0dB, $\pm 2$ dB, $\pm 6$ dB), similar less or than 2% Top-1 beam prediction accuracy can be achieved, and average L1-RSRP diff can be lower than 1dB when $\pm 6$ dB relative measurement error is considered in model training
+
+**For BM-Case1 DL Tx beam prediction or Tx-Rx beam pair prediction**, when *Set B is a subset (1/4 unless otherwise stated) of Set A, with separately modelled BB error and/or RF errors* modelled as truncated Gaussian distribution (unless otherwise stated),
+
+- Considering $\pm 3$ relative measurement error for BB and RF respectively,
+- evaluation results from 1 source show that for DL Tx beam prediction and beam pair prediction with Set B is $1/4$ of Set A, the beam prediction accuracy degrades 42% and 38% respectively in terms of Top-1 beam prediction accuracy comparing to the one without measurement error. And the average of L1-RSRP diff is about 1.1dB and 2.16dB respectively.
+- However, comparing with the global search of all beams in Set A with the same measurement error level, for DL Tx beam prediction the beam prediction accuracy degrades about 2 % in terms of Top-1 beam prediction accuracy, and for Tx-Rx beam pair prediction the beam prediction accuracy degrades about 8% in terms of Top-1 beam prediction accuracy.
+- Note: in this evaluation, measurement errors are considered in training and inference phase only for AI inputs with ideal labels in training phase.
+- evaluation results from 1 source show that for both DL Tx beam prediction with Set B is $1/4$ of Set A and beam pair prediction with Set B is $1/16$ Set A, the beam prediction accuracy degrades 4.3% and 6.3% respectively in terms of Top-1 beam prediction accuracy comparing to the one without measurement error. And the average of L1-RSRP diff becomes 0.7dB and 2.18dB larger respectively.
+- Note: in this evaluation, for DL Tx beam prediction, the measurements of Set B from each Rx beam of all Rx beams were used as AI inputs to obtain Top-K beams, followed by Top-K beam sweeping with that given Rx beam. This procedure repeats over all Rx beams, to obtain the best Tx beam at all Rx beams.
+- Considering 3.3 dB for standard deviation in relative measurement error without truncation for RF only, evaluations results from 1 source show with AI/ML:
+ - with a common measurement error for all Tx beams at a given Rx beam:
+ - Top-1 beam prediction accuracy with 1 dB margin performance has slight performance degradation (less than 0.2%) than that without measurement error.
+ - with independent measurement errors for all Tx beams,
+ - Top-1 beam prediction accuracy with 1 dB margin has 10% and 20% performance degradation than that without measurement error for Set B/Set A = $1/2$ and $1/4$ respectively.
+ - wherein, measurement errors are only considered in inference inputs
+
+Note that:
+
+- In the above results, measurement errors are considered in both training (input data and label) and inference phase (except the ground-truth) unless otherwise stated.
+- Beams could be measured regardless of their SNR.
+- Measured in a single-time instance (within a channel-coherence time interval).
+- No quantization for the L1-RSRP measurements.
+- No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+
+##### Performance with different Rx beam assumption for DL Tx beam prediction
+
+At least for BM-Case1 when Set B is a subset of Set A, and for **DL Tx beam prediction**, with the measurements of the "best" Rx beam with exhaustive beam sweeping for each model input sample, AI/ML provides the better performance than with measurements of random Rx beam(s).
+
+- Evaluation results from 12 sources show 20%~50% degradation with random Rx beam(s) comparing with the "best" Rx beam in terms of Top-1 prediction accuracy.
+- Evaluation results from 1 source shows 12% degradation with measurement of random Rx compared with measurement of best Rx in term of Top-1 beam prediction accuracy.
+
+Comparing performance with non-AI baseline option 2 (based on the measurement from Set B of beams), with measurements of random Rx beam(s) as AI/ML inputs:
+
+- Evaluation results from 7 sources show that AI/ML can still provide 7%~44% beam prediction accuracy gain in terms of Top-1 beam prediction accuracy.
+
+Note: In both training and inference, measurements of random Rx beams are used as AI/ML inputs.
+
+**For BM-Case 1 DL Tx beam prediction without UE rotation**, for Top-1 beam prediction accuracy, compared to the best Rx beams obtained from one shot measurements, with quasi-optimal Rx beam performance degradation is observed:
+
+- evaluation results from 1 source show 2% beam prediction accuracy degradation when Set B = 1/2 Set A and 7% beam prediction accuracy improvement when Set B = 1/4 or 1/8 Set A, when using the best Rx beams obtained from previous exhaustive sweeping (20ms ago) of all beams in Set A, comparing with using the best Rx beam for each Tx beams in Set B obtained from current exhaustive sweeping, without considering UE rotation for 3km/h UE speed. Such beam prediction accuracy improvement may not exist when considering UE rotation and higher UE speed.
+- evaluation results from 1 source show 2.5% beam prediction accuracy degradation using the best Rx of each Tx beams obtained from previous exhaustive sweeping (20ms ago) than using the best Rx of each Tx beams obtained from current exhaustive sweeping, without considering UE rotation for 3km/h UE speed.
+- evaluation results from 1 source shows 6.6%/6.9%/32.1%/45% degradation using a stochastic model in which the UE Rx beam is randomly selected with average probability that the best Rx beam is selected equal to 87.1%/75.1%/34.3%/10.9% compared to using the best Rx of each Tx beams obtained from current exhaustive sweeping, without considering UE rotation
+- evaluation results from 1 source show 13% beam prediction accuracy degradation, with the assumption of the best Rx beam for each Tx beam obtained from previous exhaustive sweeping over all beams in Set A in a SSB-like structure (in the past 160ms for each Rx beam with every 20ms a burst of Set A of beams) without considering UE rotation for 3km/h UE speed.
+- evaluation results from 1 source show 3%~11% beam prediction accuracy degradation, with the assumption of the best Rx beam obtained from one specific Tx beam which is 1st Tx beam in Set B.
+- evaluation results from 1 source show 12% beam prediction accuracy degradation with the assumption of the best Rx beams obtained from one specific Rx beam which is the best between the same Rx beam for different panels.
+- In addition, evaluation results from 3 sources show 1%~4% and 6%~12% beam prediction accuracy degradation, with the assumption of the best Rx beam is used for 90% and 80% of the model input samples and random Rx beam for the remaining samples respectively.
+- Even though, AI/ML can still provide better performance than non-AI baseline option 2 (exhaustive beam sweeping in Set B of beams), e.g., 50%~60% beam prediction accuracy difference in terms of Top-1 beam prediction accuracy based on the evaluation results from 2 sources, where non-AI baseline option 1 (exhaustive beam sweeping in Set A of beams) provides 100% prediction accuracy.
+
+**For BM-Case 2 DL Tx beam prediction with UE rotation**, for Top-1 beam prediction accuracy, with quasi-optimal Rx beam selection:
+
+- evaluation results from 1 source show 5~11% beam prediction accuracy improvement given the assumption of the best Rx beams obtained from previous round-robin sweep of beam pair links from beams in Set A, compared to sample-and-hold baselines.
+- In the evaluation, UE rotation is modelled every 40ms with constant 10 RPM rotation speed in all three rotational axes, with rotational direction chosen uniformly at random among the three axes.
+
+##### Performance with different label options
+
+Different label options may lead to different data collection overhead for training. At least for BMCase-1, for (Option 1a) Top-1 beam(pair) in Set A as the label and (Option 2a) all L1-RSRPs per beam of all the beams(pairs) in Set A as the label, with the comparable model complexity and computation complexity, the results across companies and the observed performance delta are summarized as below:
+
+- For Top 1 beam (pair) prediction accuracy,
+ - evaluation results from 7 sources show that an AI/ML model with Top-1 beam(pair) in Set A as the label (Option 1a) can provide better performance (e.g, 2~7% or 12%~18% higher for Top 1 beam prediction accuracy) than an AI/ML model with all L1-RSRPs per beam of all the beams(pairs) in Set A as the label (Option 2a)
+ - evaluation results from 1 source show that similar or slightly worse (e.g, 2% higher for Top 1 beam prediction accuracy)) can be achieved with Option 1a than Option 2a
+- For Top-K beam (pair) prediction accuracy or Top-1 beam prediction accuracy with 1dB margin,
+ - evaluation results from 2 sources show that Option 1a can provide similar performance than Option 2a
+ - evaluation results from 1 source show that Option 2a can provide 5%~12% better performance than Option 1a for Top-2/-4 beam pair prediction accuracy.
+ - evaluation results from 1 source show that show that Option 1a can provide 2%~5% better performance than Option 2a for Top-2/-6 beam pair prediction accuracy.
+ - evaluation results from 1 source show that show that Option 1a can provide 2%~7% /1%~5% better performance than Option 2a for Top-2/-4 beam prediction accuracy for DL Tx beam prediction.
+ - evaluation results from 1 source show that show that Option 1a can provide <1% or 9%~17% better performance than Option 2a for Top-2/-3 beam prediction accuracy for DL Tx beam prediction for Set B=1/2 Set A or Set B =1/4 or 1/8 Set A.
+- Detailed assumptions and results are listed as below:
+ - evaluation results from one source show that for both DL Tx beam prediction and beam pair prediction with Set B is 1/4 of Set A, with Top-1 beam in Set A as the label, AI/ML can provide 2%~3% higher beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label with comparable model complexity. The Top-K beam prediction accuracy is comparable for DL Tx beam prediction; however, the Top-K beam prediction accuracy is slightly better (<1%) with all L1-RSRPs as the label. The average L1-RSRP difference is similar (about 1.5dB) in the two cases.
+ - evaluation results from one source show that for Tx beam prediction with Set B is 1/2 Set A and Set B is 1/4 Set A, with Top-1 beam in Set A as the label, AI/ML can provide 2%~5% higher beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label with comparable model complexity. The Top- 1 beam with 1dB error and Top-K beam prediction accuracy is comparable for DL Tx beam prediction.
+ - evaluation results from one source show that for beam pair prediction with Set B is 1/8 or 1/16 of Set A, with Top-1 beam in Set A as the label, AI/ML can provide 4%~6% higher beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label even with larger model complexity.
+ - evaluation results from one source show that for beam pair prediction with Set B is 1/4 Set A, with Top-1 beam in Set A as the label, AI/ML can provide 12% higher beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing to the one with all L1-RSRPs of all the beams as the label with comparable model
+
+complexity. However, labelling with all L1-RSRPs can provide 5% and 12 % better for Top-3 or Top-4 beam prediction accuracy comparing with labelling with Top-1 beam ID.
+
+- evaluation results from one source show that for beam pair prediction with Set B is $\frac{1}{4}$ Set A, with Top-1 beam in Set A as the label, AI/ML can provide 15% higher beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label with comparable model complexity. The average L1-RSRP difference is similar (about 0.4dB) in the two cases.
+- evaluation results from one source show that for DL Tx beam prediction with Set B is $\frac{1}{4}$ of Set A, with Top-1 beam in Set A as the label, AI/ML can provide similar beam prediction accuracy in terms of Top-1 beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label. Using Top-1 beam as the label can provide 2%/5% better performance for Top-2/-6 beam prediction. The average L1-RSRP difference is similar (about 1dB) in the two cases.
+- evaluation results from one source show that for beam pair prediction with Set B is $\frac{1}{16}$ of Set A, with Top-1 beam in Set A as the label, 2% beam prediction accuracy degradation in terms of Top-1 beam prediction accuracy is achieved comparing to the one with all L1-RSRPs per beam of all the beams as the label.
+- evaluation results from one source show that for Tx beam prediction with Set B is $\frac{1}{4}$ of Set A or $\frac{1}{8}$ of Set A or $\frac{1}{16}$ of Set A, with Top-1 beam in Set A as the label, AI/ML can provide comparable or up to 7% higher beam prediction accuracy in terms of Top-K ( $K=1, 2, 4$ ) beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label with comparable model complexity. However, the performance of average L1-RSRP difference of Top-1 predicted beam and beam prediction accuracy with 1dB margin for Top-1 beam is comparable or better with all L1-RSRPs per beam of all the beams as the label.
+- Evaluation results from one source show that for Tx beam prediction with Set B is $\frac{1}{2}$ Set A, with Top-1 beam in Set A as the label, AI/ML can provide <1% higher beam prediction accuracy in terms of Top-K ( $K=1, 2, 3$ ) beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label with comparable model complexity. With Set B is $\frac{1}{4}$ Set A and $\frac{1}{8}$ Set A and Top-1 beam in Set A as the label, AI/ML can provide 10-18% higher beam prediction accuracy in terms of Top-K ( $K=1, 2, 3$ ) beam prediction accuracy comparing to the one with all L1-RSRPs per beam of all the beams as the label with comparable model complexity.
+
+In addition, 1 source show good performance with Top-K beam(pair)s in Set A and the corresponding L1-RSRPs as the label (Option 2b) can be achieved with two separate AI models. In the evaluation, one classification model (with Top-1/K beam(s) in Set A as the label(s)) is used to predict the Top-1/K beam and another regression model (with L1-RSRP(s) of Top-1/K beam(s) in Set A as the label(s)) is used to predict L1-RSRP(s).
+
+Note: The performance for beam predication accuracy with AI/ML may also depend on some other aspects, e.g., AI/ML model architecture choice, model training parameters (e.g., hyperparameter tuning), loss function corresponding to optimizing certain KPI(s). Assumptions on loss function are not indicated in the evaluations above.
+
+Note: ideal measurements are assumed
+
+- Beams could be measured regardless of their SNR.
+- No measurement error.
+- Measured in a single-time instance (within a channel-coherence time interval).
+- No quantization for the L1-RSRP measurements.
+- No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+
+##### Performance with different Set B pattern assumptions
+
+For BMCase-1 and for a fixed Set B pattern option, Set B pattern will affect the beam prediction accuracy with AI/ML for both DL Tx beam prediction and beam pair prediction.
+
+At least for BM-Case1 (unless otherwise stated) DL Tx beam with the measurements from the best Rx beam, and/or beam pair prediction, when Set B is a subset of Set A without considering other generalization aspects and without UE rotation.
+
+- **(Opt 2B)** For the case that Set B of beam(pair)s is changed among pre-configured patterns, compared to the case that Set B is fixed across training and inference (Opt 1), for Top-1 beam prediction accuracy
+ - evaluation results from 14 sources show no more than 10% or about 10% beam prediction accuracy degradation, wherein 2 sources used up to 24 pre-configured patterns and the rest of sources use 3 ~ 5 patterns;
+ - AI/ML still can provide better performance (e.g., >30%) of Top-1 beam prediction unless otherwise stated) than non-AI baseline option 2 (exhaustive beam sweeping in Set B of beams).
+ - Note: the above performance can also be treated as training with mixed patterns of Set B of beam, and testing with mixed patterns Set B of beams.
+- **(Opt 2C)** For the case that Set B of beam(pair)s is randomly changed in Set A of beams, compared to the case that Set B is fixed across training and inference (Opt 1), for Top-1 beam prediction accuracy
+ - evaluation results from 2 sources show 10%~20% beam prediction accuracy degradation.
+ - evaluation results from 7 sources show 20%~50% beam prediction accuracy degradation.
+ - AI/ML still can provide better performance (e.g., >25% of Top-1 beam prediction unless otherwise stated) than non-AI baseline option 2 (exhaustive beam sweeping in Set B of beams):
+- **(Opt 2D)** For the case that Set B of beams (pairs) is a subset of measured beams (pairs) Set C (where Set C is fixed across training and inference), compared to the case with all measurements of measured beam Set C as AI inputs
+ - **with Top K=1/2** of the measurements of Set C,
+ - For Top-1 beam prediction accuracy
+ - evaluation results from 5 sources show less than 4% the beam prediction accuracy degradation
+ - evaluation results from 3 sources show about 7% the beam prediction accuracy degradation
+ - evaluation results from 1 source show <1% and 7% beam prediction accuracy degradation with measuring 1/2 and 1/4 of Set A of beams respectively.
+ - evaluation results from 1 source show about 12% the beam prediction accuracy
+ - Note: all the above results are for DL Tx beam prediction
+ - For NW-side model, 1/2 UCI reporting overhead for inference inputs can be saved without considering quantization impact.
+ - In the above evaluation, 5 sources use L1-RSRPs of Top-4 measurements of 8 beams in Set C for 32 Tx beams in Set A.
+ - In the above evaluation, 3 sources use L1-RSRPs of Top-8 measurements of 16 beams in Set C for 64 Tx beams in Set A
+ - In the above evaluation, 1 source uses L1-RSRPs of Top-4/-8 measurements of 8/16 beams in Set C for 32 Tx beams in Set A.
+ - **with Top K=1/4** of the measurements of Set C,
+ - For Top-1 beam prediction accuracy
+ - evaluation results from 2 sources show 8~10% beam prediction accuracy degradation.
+ - evaluation results from 1 source show 15% beam prediction accuracy degradation.
+ - evaluation results from 1 source show 2% beam prediction accuracy degradation with measuring 1/2 of Set A of beams respectively.
+ - Note: all the above results are for DL Tx beam prediction
+
+- For NW-side model, 3/4 UCI reporting overhead for inference inputs can be saved without considering quantization impact.
+ - In the above evaluation, 1 source uses L1-RSRPs of Top-4 measurements of 16 beams in Set C for 32 Tx beams in Set A.
+ - In the above evaluation, 2 sources use L1-RSRPs of Top-4 measurements of 16 beams in Set C for 64 Tx beams in Set A.
+- **with Top K=1/8** of the measurements of Set C,
+ - evaluation results from 1 source show 7.5% beam prediction accuracy degradation in terms of Top-1 beam prediction accuracy for beam pair prediction.
+ - For NW-side model, 7/8 UCI reporting overhead for inference input can be saved.
+ - In the evaluation, 1 resource uses L1-RSRPs of Top-16 measurements of 128 beams in Set C for 64 Tx beams and 8 Rx beams in Set A.
+- **with Top K=1/6** of the measurements of Set C, for BM-Case 2, evaluation results [from 1 source] show 3.5% improvement in beam prediction accuracy compared to non-AI/ML baseline (Option 2, sample-and-hold) whose beam prediction accuracy is 78.2%.
+- **with the reported measurements within a given gap** of [5dB/ 10dB/ 14dB~20dB] to the best beam in Set C, evaluation results from 6 sources show 15%~28% / 4%~16.4% / 2%~6% respectively beam prediction accuracy degradation.
+ - 1 source Samsung simulated for BM-Case 2, and filled in the unreported measurements in Set C as (L1-RSRP of the best Rx beam in Set C-14dB) as the inputs for AI/ML.
+- **with Top-M measurements** in Set C or **with the reported measurements within a given gap** to the best beam in Set C (when Set C is larger than Set B), comparing with the case that using a smaller number of beams in Set B as the fixed pattern, the results show that comparable or better beam prediction accuracy can be achieved with the same reporting overhead or numbers of measurements as of AI inputs but larger measurement overhead.
+ - evaluation results from 1 source show similar Top-1 beam prediction accuracy for the case using the measurements of Top 8 beams of 16 beams in Set C and 64 beams in Set A comparing with using 8 fixed beams in Set B.
+ - evaluation results from 1 source show 16.5% and 43% gain in terms of Top-1 beam prediction accuracy for the case of using the measurements of Top 4 beams of 8 or 16 beams in Set C and 32 beam in Set A respectively comparing with using 4 fixed beams in Set B.
+ - evaluation results from 1 source show about 8% gain in terms of Top-1 beam prediction accuracy for the case using the measurements of Top 4 beams of 8 beams in Set C and 32 beams in Set A comparing with using 4 fixed beams in Set B.
+ - evaluation results from 1 source show about 12.5% gain in terms of Top-1 beam prediction accuracy for the case using the measurements of Top 4 beams of 8 beams in Set C and 32 beams in Set A comparing with using 4 fixed beams in Set B.
+ - evaluation results from 1 source show about 18% gain in terms of Top-1 beam prediction accuracy for the case using the measurements of Top 8 beams of 16 beams in Set C and 64 beams in Set A comparing with using 4 beams in Set B.
+ - evaluation results from 1 source show similar Top-1 beam prediction accuracy for the case using the measurements of Top 4 beams of 8 beams in Set C and 32 beams in Set A comparing with using 4 fixed beams in Set B
+ - evaluation results from 1 source show 17% gain in terms of Top-1 beam prediction accuracy for the case of using the measurements of Top 8 beams of 16 beams in Set C and 64 beams in Set A comparing with using 8 fixed beams in Set B. .
+
+- evaluation results from 1 source show 12% gain in terms of Top-1 beam prediction accuracy for the case of using the measurements of Top 4 beams of 8 in Set C and 32 beam in Set A comparing with using 4 fixed beams in Set B respectively.
+- The beam prediction accuracy increases with the number of measurements of Set B.
+- AI/ML still can provide better performance (e.g., >30% of Top-1 beam prediction unless otherwise stated) than non-AI baseline option 2 (exhaustive beam sweeping in Set B of beams).
+- Note that ideal measurements are assumed
+ - Beams could be measured regardless of their SNR.
+ - No measurement error.
+ - Measured in a single-time instance (within a channel-coherence time interval).
+ - No quantization for the L1-RSRP measurements.
+ - No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+ - This observation is based on Set B patterns that were chosen by each company.
+ - Implicit or explicit information of Tx beam ID and/or Rx beam ID are used as AI/ML model inputs
+
+#### 6.3.2.4 Generalization Performance for BM-Case1 and BM-Case2
+
+The following *generalization aspects* were evaluated for at least BMCase-1 when Set B is a subset of Set A (and BMCase-2 if stated),
+
+- Scenarios
+ - Various deployment scenarios,
+ - e.g., UMa, UMi
+ - e.g., 200m ISD or 500m ISD
+ - Various outdoor/indoor UE distributions, e.g., 100%/0%, 20%/80%, and others
+ - Various UE mobility (for BMCase-2 only),
+ - e.g., 30km/h, 60km/h and others
+- Configurations (parameters and settings)
+ - Various UE parameters,
+ - e.g., UE codebook
+ - e.g., UE antenna array dimensions
+ - e.g., different number beams in a seen UE codebook when inference using a subset of Rx beams of training
+ - Various gNB settings,
+ - e.g., DL Tx beam codebook
+ - e.g., gNB antenna array dimensions
+ - Various Set A of beam(pairs)
+ - Various Set B of beam (pairs)
+
+Note: the following are assumed in the simulation unless otherwise stated
+
+- For DL Tx beam prediction, the measurements from best Rx beam are used.
+- Fixed Set B pattern.
+- Without UE Rotation.
+- Beams could be measured regardless of their SNR.
+- No measurement error.
+- Measured in a single-time instance (within a channel-coherence time interval).
+- No quantization for the L1-RSRP measurements.
+- No constraint on UCI payload overhead for full report of the L1-RSRP measurements of Set B for NW-side models are assumed.
+- Observations are applicable for both Tx beam and beam pair.
+- The evaluation results are from BM-Case 1 and similar observation are expected for BM-Case 1 when Set B is different from Set A.
+
+Note that, in the following evaluation, model switching is not evaluated for generalization performance.
+
+Companies have provided evaluation results which show that Case 3 and/or Case 2A can provide better performance than Case 2. In most of the cases/evaluations, Case 3 has performance degradation than Case 1. From the evaluation results from some companies and for some scenarios, Case 3 may have similar or slightly higher performance than Case 1:
+
+- 2 sources: for various UE distribution with same or double training data size,
+- 1 source: for different ISDs with triple training data size.
+
+**(A) For some cases, Case 2 have some performance degradation** than Case 1 in most of the cases/evaluations. In Case 2, AI/ML still can provide better performance than non-AI baseline option 2 (based on the measurements from Set B of beams):
+
+- For various deployment scenarios: UMa/UMi (with the assumption of same down tilt, same or different NLOS probability, same or different ISD, same or different antenna height)
+ - (Case 2) For generalization Case 2 compared to Case 1,
+ - With the assumption of same ISD, antenna height and same NLOS probability for UMa/UMi, evaluation results from 4 sources show less than 5% degradation, evaluation results from 4 sources show 5%~10% degradation
+ - wherein 1 source assumed different UE distribution with same ISD, antenna height, its results show 5%~17% and less than 5% degradation for 100% outdoor UE and 80%/20% in/outdoor UE, respectively, for different combinations of Set B and Set A (i.e., different ratio of Set B/Set A and Set B could be either subset of Set A or different from Set A) for Top-1 beam prediction accuracy, for DL Tx beam prediction.
+ - With the assumption of different antenna height for UMa/UMi,
+ - evaluation results from 1 source show about 13% degradation for Top-1 beam prediction accuracy, for DL Tx beam prediction with same ISD
+ - evaluation results from 1 source show 16%, and 18% degradation for Top-1 beam prediction accuracy, for DL Tx beam and beam pair prediction respectively, with different ISD
+ - evaluation results from 1 source show about 13% degradation for Top-1 beam prediction accuracy, for both DL Tx beam and beam pair prediction with same ISD, different antenna heights and NLOS probabilities
+ - (Case 3) For generalization Case 3 compared to Case 1, the evaluation results from 5 sources show less than 5% degradation, and the evaluation results from 1 source show 8% degradation for Top-1 beam prediction accuracy, for DL Tx beam and/or beam pair prediction.
+
+- wherein 1 source assumed different ISD and antenna height and the results show about 8% degradation for Top-1 beam prediction accuracy for both DL Tx beam and beam pair prediction.
+
+###### - Various deployment scenarios: ISD 200m/ISD 500m
+
+- (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 3 sources show about 1%~2% degradation, evaluation results from 2 sources show ~9% degradation for Top-1 beam prediction accuracy for DL Tx beam and/or beam pair prediction.
+- (Case 3) For generalization Case 3 compared to Case 1, the evaluation results from 1 source show slightly better (1%~2% for Top-1 beam prediction accuracy) performance compared to Case 1 with triple size of training data for DL Tx beam prediction, and, the evaluation results from 1 source show about 1% degradation on Top-1 beam prediction accuracy for beam pair prediction with the same size of training data.
+
+###### - Various deployment scenarios: 100% outdoor/20%outdoor
+
+- (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 4 sources show less than 5% degradation, evaluation results from 3 sources show 5%~10% degradation, evaluation results from 3 sources show 10%~25% degradation for Top-1 beam prediction accuracy for DL Tx beam and/or beam pair prediction.
+ - In addition, 1 source evaluated the scenario with 80% outdoor/20% outdoor, and its evaluation results show about 20% degradation for Top-1 beam prediction accuracy for DL Tx beam prediction.
+ - In addition, 1 source evaluated the scenario with 100% outdoor/0% outdoor, and its evaluation results show 10%~25% degradation for Top-1 beam prediction accuracy for DL Tx beam prediction.
+ - In addition, evaluation results from 1 source show that the performance degradation becomes larger with smaller ratio of Set B/Set A.
+ - wherein, 1 source evaluated the scenario with ISD=200 in UMa for different combinations of Set B and Set A (i.e., different ratio of Set B/Set A and Set B could be either subset of Set A or different from Set A) and the results show 10%~17% degradation for Top-1 beam prediction accuracy for DL Tx beam prediction.
+- (Case 2A) For generalization Case 2A compared to Case 1, evaluation results from 1 source show 1%~6% degradation for Top-1 beam prediction accuracy for DL Tx beam prediction.
+ - wherein, 1 source evaluated the scenario ISD=200 in UMa for different number of epochs and number of data used for finetuning and the results show 1%~6% degradation for Top-1 beam prediction accuracy for DL Tx beam prediction.
+ - In addition, 1 source evaluated the scenario with 80% outdoor/20% outdoor, and its evaluation results show 3%~8% degradation for Top-1 beam prediction accuracy for DL Tx beam prediction.
+- (Case 3) For generalization Case 3 compared to Case 1, the evaluation results from 4 sources show less than 2% degradation, and the evaluation results from 2 sources show 10% degradation for Top-1 beam prediction accuracy compared to Case 1. However, the evaluation results from 1 source show slightly better (about 1% for Top-1 beam prediction accuracy) performance compared to Case 1 with double size of training data.
+ - In additional, 1 source evaluated the scenario with 80% outdoor/20% outdoor, and its evaluation results show slightly better (about 4% for Top-1 beam prediction accuracy) performance compared to Case 1 with same training data size for DL Tx beam prediction.
+ - In additional, the evaluation results from 1 source show that for generalization from 100% outdoor to 20% outdoor, 7% degradation for Top-1 beam prediction accuracy compared to Case 1. For generalization from 20% outdoor to 100% outdoor, about 4% degradation for Top-1 beam prediction accuracy compared to Case 1.
+
+##### - For DL Tx beam prediction only, various UE parameters: different UE codebooks, and/or different UE antenna array dimensions
+
+- (Case 2) For generalization Case 2 compared to Case 1, for Top-1 beam prediction accuracy
+ - evaluation results from 2 sources show less than 1% performance with different UE codebooks.
+
+- evaluation results from 1 source show about 4% degradation, with different UE codebook, different number of Rx elements and panel location.
+- evaluation results from 1 source show about 10% degradation with both different number of UE Rx beams, different number of Rx elements, and about 5% degradation with both different number of UE Rx beams (where in Configuration #A, UE Rx beams are subset of UE Rx beams in Configuration #B), and same number of Rx elements,
+- (Case 3) For generalization Case 3 compared to Case 1, the evaluation results from 1 source show 1~2.5% degradation with different number of UE Rx beams, different number of Rx elements and panel location, and evaluation results from 1 source show about 7.5% degradation with both different number of UE Rx beams, different number of Rx elements, for Top-1 beam prediction accuracy.
+- For beam pair prediction only, various UE parameters: different number of beams in a seen UE codebook when inference using a subset of Rx beams of training
+ - (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 2 sources show 2%~15% degradation Top-1 beam prediction accuracy
+ - wherein, evaluation results from 1 source show 2% with different number of beams in a seen UE codebook for Top-1 beam prediction accuracy based on the assumption that training by 8 Rx beam and inference by 4 of 8 Rx beam.
+ - wherein, evaluation results from 1 source show 15% degradation with different number of beams in a seen UE codebook for Top-1 beam prediction accuracy based on the assumption that training by 4 Rx beam and inference by 2 of 4 Rx beam.
+
+**(B) For some cases**, Case 2 have **significant performance degradation** than Case 1 in most of the cases/ evaluations. In Case 2, AI/ML can provide comparable or worse performance than non-AI baseline option 2 (based on the measurements from Set B of beams)
+
+- Various deployment scenarios: UMa/UMi (With the assumption of different ISD, antenna height, down tilt and NLOS probability)
+ - (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 3 sources show 20%~35% degradation for Top-1 beam prediction accuracy compared to Case 1, for DL Tx beam and/or beam pair prediction.
+ - (Case 3) For generalization Case 3 compared to Case 1, the evaluation results from 2 sources show less than 5% degradation,
+- Various configurations (parameters and settings): different gNB antenna array dimensions, and/or DL Tx beam codebook
+ - Note: different DL Tx beam codebooks will result in various Set A of beam(pairs)
+ - (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 2 source show 15%~40% degradation, evaluation results from 5 sources show 30%~50% degradation, evaluation results from 2 sources show about 60% degradation, evaluation results from 1 source show about 70% degradation, for Top-1 beam prediction accuracy for DL Tx beam and/or beam pair prediction. 1 source shows BM-AI can perform worse than the conventional approach's with mismatched set A design.
+ - Wherein 1 source show 15%~40% degradation for Top-1 beam accuracy assuming same DL Tx codebook (pointing angles) and different beam width, and 50%~60% degradation for Top-1 beam accuracy assuming different DL Tx codebooks (pointing angles) and same beam width for Tx beam and pair prediction
+ - wherein 2 sources assumed different Tx beam codebooks have different horizontal angles but the same gNB array/beamwidth and the results show about 56% degradation for Top-1 beam prediction accuracy with same training data size for DL Tx beam prediction.
+ - wherein 1 source assumed different Tx beam codebooks have different horizontal beam angles and the different gNB array/beamwidth and the results show about 57% degradation for Top-1 beam prediction accuracy with same training data size for beam pair prediction.
+
+- wherein 2 sources assumed different Tx beam codebooks have the same beam pointing angles but have different beamwidth (due to different gNB array sizes) and the results show about 30% degradation for Top-1 beam prediction accuracy.
+ - evaluation results from 1 source show performance degradation in terms of the top-1 beam accuracy from 73.9% to 34.2% at 4 beams in Set B, from 88.6% to 63.9% at 8 beams in set B, from 97.8% to 88.4% at 16 beams in set B.
+ - evaluation results from 5 sources show better performance than non-AI baseline option 2 (based on the measurements from Set B of beams). However, evaluation results from 5 sources similar or even worse performance than non-AI baseline option 2 (based on the measurements from Set B of beams).
+ - (Case 2A) For generalization Case 2A compared to Case 1, evaluation results from 1 source show 16%~20% for Top-1 beam prediction accuracy for DL Tx beam prediction with the assumption that different Tx beam codebooks have different horizontal angles but the same gNB array/beamwidth.
+ - (Case 3) For generalization Case 3 compared to Case 1, the evaluation results from 6 sources show less than 5% degradation, and the evaluation results from 2 sources show 10%~15% degradation for Top-1 beam prediction accuracy compared to Case 1. Evaluation results from 1 source show there is 2%~32% degradation for Top-1 beam with 1 dB margin.
+ - Wherein, 1 source assumes different beamwidth and double training data size
+- For Tx-Rx beam pair prediction only, various UE parameters: different UE codebooks, and/or different UE antenna array dimensions
+- Note: different UE Rx beam codebooks will result in various Set A of beam pairs for beam pair prediction
+ - (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 4 sources show large degradation (i.e., >40%) with different number of elements (different beamwidth) and different UE codebooks for Top-1 beam prediction accuracy.
+ - wherein, evaluation results from 1 source show 12% and 52% degradation with UE codebook is different for Top-1 beam prediction accuracy with 1x4 Rx beam and with 2x2 Rx beam pattern and 1x4 Rx beam respectively.
+ - (Case 3) For generalization Case 3 compared to Case 1, evaluation results from 1 source show less than 5% degradation, and evaluation results from 1 source show 16%~26% degradation for Top-1 beam prediction accuracy, with different number of elements and/or different number of UE Rx
+- Various Set B of beams: different fixed Set B pattern
+- (Case 2) For generalization Case 2 compared to Case 1, evaluation results from 9 sources show large degradation with different Set B pattern (different number and/or same number different Set B pattern) for DL Tx beam prediction and/or beam pair prediction.
+ - evaluation results from 1 source show 13%~21% degradation with same evenly spaced in beam(pair) ID dimension without providing beam ID information as AI/ML inputs.
+ - evaluation results from 1 source show 20%~40% degradation with different number of beams in Set B for BMCase-2
+ - evaluation results from 1 source show the AI-BM performance can be worse than the conventional approach's with mismatched set B design.
+ - (Case 3) For generalization Case 3 compared to Case 1,
+ - evaluation results from 5 sources show less than or about 5% degradation.
+ - evaluation results from 1 source show 14% degradation without providing beam ID information as AI/ML inputs.
+ - evaluation results from 1 source show 3%~10% degradation with different number of beams in Set B for BMCase-2
+ - evaluation results from 1 source show 8-10% degradation with different Set B pattern.
+
+**(C) For BMCase-2, various UE mobility**, different companies reported different observation for Case 2. In Case 2, AI/ML still can provide comparable or worse performance than non-AI baseline option 2 (based on the measurements from Set B of beams)]
+
+- For various UE mobility for BMCase-2: 30km/h / 60km/h / 90km/h 120km/h
+
+- (Case 2) For generalization Case 2 compared to Case 1,
+ - evaluation results from 3 sources show significant degradation i.e., >30% in terms of Top 1 prediction accuracy, and evaluation results from 1 source show about 19%~49% degradation for prediction time 160ms~800ms.
+ - evaluation results from 4 sources show >6% performance degradation in terms of Top 1 prediction accuracy and evaluation results from 3 sources show about 10~18% degradation
+- (Case 3) For generalization Case 3 compared to Case 1, for Top-1 beam prediction accuracy
+ - the evaluation results from 3 sources show 3~7% degradation for Top-1 beam prediction accuracy
+ - the evaluation results from 1 source show 8~14% degradation for Top-1 beam prediction accuracy
+ - the evaluation results from 1 source show <17% degradation for Top-1 beam prediction accuracy by training with same size of training data mixed of 30km/h, 60km/h and 90km/h.
+ - the evaluation results from 1 source show about 1% degradation for Top-1 beam prediction accuracy for 30km/h and 60km/h, and show about 4%/8% degradation for Top-1 beam prediction accuracy for 30km/h and 90km/h.
+ - the evaluation results from 1 source show comparable performance for Top-1 beam prediction accuracy for 30km/h and 60km/h
+ - the evaluation results from 3 sources show slightly better (1%~2% for Top-1 beam prediction accuracy) performance compared to Case 1 with double or triple size of training data for DL Tx beam prediction.
+
+#### 6.3.2.5 Summary of Performance Results for Beam Management
+
+##### Summary of evaluations and results for BM-Case1
+
+For BM-Case1 when Set B is a subset of Set A or when Set B is different than Set A, without UE rotation, AI/ML can achieve good performance with measurements of fixed Set B that is 1/4 or 1/8 of Set A of beam measured with best Rx beam for DL Tx beam prediction, and with measurements of fixed Set B that is 1/4 or 1/8 or 1/16 of Set A for beam pair prediction. In addition, based on the evaluation results from 2 or 3 sources, for BM-Case1 DL Tx beam prediction, with 1/4 or 1/8 measurement/RS overhead, 96%~99% or 85%~98% of UE average throughput and 95%~97% or 70%~84% of UE 5%ile throughput of non-AI baseline option 1 (exhaustive search over Set A beams) can be achieved according to the predicted beam from AI/ML. Note that, ideal measurements are assumed in the evaluations (in clause 6.3.2.1): beam could be measured regardless their SNR, no measurement error, and measurements obtained in a single-time instance (within a channel-coherence time interval), no quantization and no constraint on UCI payload (for NW-side model).
+
+With some realistic consideration (in clause 6.3.2.3):
+
+- Existing quantization granularity of L1-RSRP causes a minor loss in beam prediction accuracy compared to unquantized L1-RSRPs of beams in Set B at least for BM-Case1 for inference of DL Tx beam prediction.
+- Measurement errors degrade the beam prediction performance with AI/ML, while measurement errors also degrade the performance with non-AI baseline (both option 1 and option 2).
+- For DL Tx beam prediction, with the measurements from quasi-optimal Rx beam, some performance degradation (e.g., 2% to up to 12% Top-1 beam prediction accuracy loss based on most of results) is observed comparing to with measurements from best Rx beam. If the measurements are from random Rx beam, large performance degradation is observed.
+
+In addition, comparing with fixed Set B (Opt 1), in case of with Set B changed among pre-configured patterns (Opt 2B), some performance degradation (e.g., no more than or about 10% Top-1 beam prediction accuracy loss based on most of results) is observed; in case of with Set B randomly changed in Set A of beams (Opt 2C), large degradation (e.g., 20%~50% Top-1 beam prediction accuracy loss based on most of results) is observed. With reduced number of
+
+measurements of a fixed set of beams (Set C) as inputs of AI/ML (Opt 2D), some performance degradation (e.g., <10% Top-1 beam prediction accuracy loss based on most of results) is observed, comparing with using all measurements from Set C, in the meanwhile, UCI reporting overhead for inference inputs can be reduced (e.g., 1/2 to 7/8 UCI reporting overhead reduction) comparing with reporting all measurements of the fixed beam Set C.
+
+Moreover, the performance with different label options has been evaluated which may lead to different data collection overhead for training (for both BM-Case1 and BM-Case2).
+
+##### Summary of evaluations and result for BM-Case2
+
+Evaluation results for BM-Case2 when Set B= Set A for DL Tx beam prediction with the measurements from the best Rx beam and beam pair prediction are summarized in Table 6.3.2.5-1 and Table 6.3.2.5-2, without considering generalization aspects.
+
+**Table 6.3.2.5-1: Summary of the evaluation results for BM-Case2 when Set B=Set A for DL Tx beam prediction**
+
+| | Without rotation | With rotation |
+|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Beam prediction accuracy performance compared with non-AI baseline (option 2) | <p>For 80ms or 160ms prediction time:</p> <ul style="list-style-type: none"> <li>- Some evaluation results show AI/ML may have similar performance or some degradation</li> </ul> <p>For 160ms or larger prediction time:</p> <ul style="list-style-type: none"> <li>- Most evaluation results show AI/ML provides some beam prediction accuracy gain</li> <li>- The longer the prediction time, the higher gain of beam prediction accuracy can be achieved by AI/ML</li> </ul> | <p>AI/ML can provide some beam prediction accuracy gain:</p> <ul style="list-style-type: none"> <li>- The longer the prediction time, the higher gain of beam prediction accuracy can be achieved by AI/ML</li> </ul> <p>(2 sources)</p> |
+| RS overhead Case A, compared with non-AI baseline (option 1) | AI/ML can achieve decent beam prediction accuracy with 1/5~1/2 measurement/RS overhead reduction | N/A |
+| RS overhead Case B, comparing with non-AI baseline (option 2) with given prediction accuracy | AI/ML can achieve a certain beam prediction accuracy with 7/10 measurement/RS overhead reduction<br>(1 source) | AI/ML can achieve a certain beam prediction accuracy with 1/2 measurement/RS overhead reduction<br>(1 source) |
+| RS overhead Case B+, comparing with non-AI baseline (option 1) | AI/ML can achieve good beam prediction with 80% measurement/RS overhead reduction<br>(1 source) | AI/ML can achieve good beam prediction with more than 80% measurement/RS overhead reduction<br>(1 source) |
+
+**Table 6.3.2.5-2: Summary of the evaluation results for BM-Case2 when Set B=Set A for beam pair prediction**
+
+| | Without rotation | With rotation |
+|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|
+| Beam prediction accuracy performance compared with non-AI baseline (option 2) | <p>For 160ms or less prediction time:</p> <ul style="list-style-type: none"> <li>- AI/ML may or may not provide beam prediction accuracy gain</li> </ul> <p>The longer the prediction time,</p> <ul style="list-style-type: none"> <li>- the higher gain of beam prediction accuracy can be achieved by AI/ML</li> </ul> | <p>AI/ML may or may not provide beam prediction accuracy gain</p> <p>(3 sources)</p> |
+| RS overhead Case A, compared | AI/ML can provide good beam | N/A |
+
+| | | |
+|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----|
+| with non-AI baseline (option 1) | prediction accuracy with the less measurements/RS overhead (up to 1/2) | |
+| RS overhead Case B, comparing with non-AI baseline (option 2) with given prediction accuracy | AI/ML can achieve a certain beam prediction accuracy with 1/2 or 3/5 measurement/RS overhead reduction<br><br>(2 sources) | N/A |
+| RS overhead Case B+, comparing with non-AI baseline (option 1) | AI/ML can achieve good beam prediction accuracy with 80% measurement/RS overhead reduction<br><br>(1 source) | N/A |
+
+For BM-Case2 when Set B is a subset of Set A for DL Tx beam prediction with the measurements from the best Rx beam, without considering generalization aspects, AI/ML can achieve good prediction accuracy with 1/2, 1/3, 1/4, 1/8 RS overhead in spatial domain, for the case Set B is fixed or variable with pre-configured patterns of beams with or without UE rotation. More RS/measurements overhead reduction can be achieved considering overhead reduction in time domain.
+
+For BM-Case2 when Set B is a subset of Set A for beam pair prediction, without considering generalization aspects
+
+- without UE rotation, AI/ML can achieve good prediction accuracy with 1/4, 1/8, 1/16 RS overhead in spatial domain, for the case Set B is fixed or variable with pre-configured patterns of beams.
+- with UE rotation, from 2 sources, AI/ML can provide 15% or 44% prediction accuracy gain with 1/4, 1/16 RS overhead in spatial domain comparing with non-AI baseline (option 2), for the case Set B is fixed or variable with pre-configured patterns of beams. However, the Top-1 beam prediction accuracy may or may not be good enough.
+- More RS/measurements overhead reduction can be achieved considering overhead reduction in time domain.
+
+Note that, ideal measurements are assumed in the above evaluations (for BM-Case2): beam could be measured regardless their SNR, no measurement error, no quantization and no constraint on UCI payload (for NW-side model). With measurement error, quantization or measurements results from quasi-optimal Rx beam for DL Tx beam prediction, similar observations are observed (for some cases) or expected as for BM-Case1.
+
+Reduced measurement overhead can reduce measurement latency for beam prediction in some configurations.
+
+##### **Summary of evaluations and results for generalization**
+
+Different location of AI/ML model (e.g., NW side model, or UE side model) may have different generalization requirements:
+
+For NW side model,
+
+- generalization performance with various gNB settings and various Set B of beams may not be an issue since the gNB settings are most likely to be fixed or limited to a given gNB (at least seen by AI/ML before)
+- for DL Tx beam prediction, generalization performance with various unseen UE parameters is acceptable at least with the measurement from the best or fixed Rx beam.
+- Tx-Rx beam pair prediction, generalization performance with various UE parameters, i.e., different number of beams in a seen UE codebook when inference using a subset of Rx beams of training is acceptable-
+- for Tx-Rx beam pair prediction, the significant generalization performance degradation with unseen various UE parameters (i.e., different UE codebooks, and/or different UE antenna array dimensions) can be improved to achieve less than 5% degradation (2 sources) and 16%~26% degradation (1 source) in terms of Top-1 beam prediction accuracy with the model training with mixed data compared to generalization performance Case 1.
+ - Note: with same amount of data for training for different scenarios for Case 3
+
+- Alternatively, AI/ML model can be trained for different scenarios and rely on model switching based on applicable scenario which would improve generalization performance.
+
+For UE side model,
+
+- generalization performance with unseen various UE parameters may not be an issue
+- the significant generalization performance degradation with unseen various gNB setting (i.e., different gNB antenna array dimensions, and/or DL Tx beam codebook) or unseen various Set B of beam(pairs) can be improved to achieve
+ - (for gNB setting) less than 5% (6 sources), 10%~15% (2 sources), and 2%~32% (1 source) degradation in terms of Top-1 beam prediction accuracy compared with the model training with mixed data to generalization performance Case 1, and 16%~20% (1 source) degradation in terms of Top-1 beam prediction accuracy compared with the model finetune to generalization performance Case 1.
+ - (for Set B of beam(pairs)) less than 10% (all 7 sources) degradation in terms of Top-1 beam prediction accuracy compared with the model training with mixed data to generalization performance Case 1.
+ - Note: For gNB setting, generalization performance Case 3 may depend on how different the gNB settings are across training and inference
+ - Note: with same amount of data for training for different scenarios for Case 3
+ - Alternatively, AI/ML model can be trained for different scenarios and rely on model switching based on applicable scenario which would improve generalization performance.
+
+At least for BMCase-1, AI/ML (without considering model switching) has some performance degradation with some unseen scenarios including:
+
+- For DL Tx beam prediction,
+ - deployment scenarios: different ISD, UMi/UMa (at least with same down tilt)
+ - various outdoor/indoor UE distributions
+ - various UE parameters: different UE codebooks, and different UE antenna array dimensions.
+ - Note: at least with the measurement from the best Rx beam.
+- For beam pair prediction
+ - deployment scenarios: different ISD, UMi/UMa (at least with same down tilt)
+ - various outdoor/indoor UE distributions
+ - various UE parameters: when inference using a subset of Rx beams of training.
+
+However, the AI/ML (without considering model switching) has significant performance degradation with some other unseen scenarios, including:
+
+- For DL Tx beam prediction,
+ - deployment scenarios: UMi/UMa (at least with the assumption of different ISD, antenna height, down tilt and NLOS probability)
+ - various gNB setting: different gNB antenna array dimensions, and DL Tx beam codebook
+ - various Set B patterns
+ - various Set A patterns
+- For beam pair prediction
+ - various UE parameters: different UE codebooks, and different UE antenna array dimensions
+ - deployment scenarios: with the assumption of different ISD, antenna height, down tilt and NLOS probability
+
+- various gNB setting: different gNB antenna array dimensions, and DL Tx beam codebook
+- various Set B patterns
+- various Set A patterns
+
+In order to let AI/ML model see the data from a new setting which causes performance loss, the AI/ML model can be trained with mixed data or finetuned with the data from the new setting to improve the generalization performance. Alternatively, AI/ML model can be trained for different scenarios and rely on model switching based on applicable scenario which would improve generalization performance.
+
+For **BMCase-2**, for variable UE mobility, the collected data for training can be mixed and the generalization performance with mixed UE speeds is acceptable.
+
+## 6.4 Positioning accuracy enhancements
+
+### 6.4.1 Evaluation assumptions, methodology and KPIs
+
+For AI/ML-based positioning evaluation, RAN1 does not attempt to define any common AI/ML model as a baseline. In the evaluation, some results use UE measurement information as model input, other results use gNB measurement information as model input, and they are not distinguished for summarizing the results.
+
+For AI/ML based positioning, the following methods are evaluated.
+
+- (1) Direct AI/ML positioning, see an example illustrated in Figure 6.4.1-1.
+- (2) Assisted AI/ML positioning.
+ - (a) Assisted AI/ML positioning with multi-TRP construction, see an example illustrated in Figure 6.4.1-2.
+ - (b) Assisted positioning with single-TRP construction and one model for N TRPs, see an example illustrated in Figure 6.4.1-3.
+ - (c) Assisted positioning with single-TRP construction and N models for N TRPs, see an example illustrated in Figure 6.4.1-4.
+
+
+
+The diagram illustrates the Direct AI/ML positioning process. On the left, four horizontal arrows represent channel measurements from different TRPs: TRP 0, TRP 1, an ellipsis representing intermediate TRPs, and TRP (N-1). These arrows point into a central rectangular box labeled "AI/ML model". Above the first arrow is the text "Channel measurement associated with:". An arrow points out from the right side of the "AI/ML model" box, labeled "Model output: UE location".
+
+Diagram of Direct AI/ML positioning showing multiple TRPs (TRP 0, TRP 1, ..., TRP (N-1)) providing channel measurements to a central AI/ML model, which outputs the UE location.
+
+Figure 6.4.1-1: Direct AI/ML positioning
+
+
+
+This diagram illustrates the multi-TRP construction for assisted positioning. On the left, multiple horizontal arrows represent channel measurements associated with different TRPs, labeled TRP 0, TRP 1, an ellipsis, and TRP (N-1). These arrows point into a single, large vertical rectangular block labeled "AI/ML model". From the right side of this block, multiple horizontal arrows point outwards, representing the "Model output: intermediate positioning measurement". These output arrows are labeled with TRP 0, TRP 1, an ellipsis, and TRP (N-1) respectively.
+
+Diagram of assisted positioning with multi-TRP construction
+
+Figure 6.4.1-2: Assisted positioning with multi-TRP construction
+
+
+
+This diagram illustrates the single-TRP construction using a single model for N TRPs. On the left, horizontal arrows represent channel measurements for TRP 0, TRP 1, an ellipsis, and TRP (N-1). Each arrow points into its own separate rectangular block, all of which are labeled "AI/ML model". From the right side of each block, a horizontal arrow points outwards, representing the "Model output: intermediate positioning measurement".
+
+Diagram of assisted positioning with single-TRP construction and one model for N TRPs
+
+Figure 6.4.1-3: Assisted positioning with single-TRP construction, and one model for N TRPs.
+
+
+
+This diagram illustrates the single-TRP construction using N separate models for N TRPs. On the left, horizontal arrows represent channel measurements for TRP 0, TRP 1, an ellipsis, and TRP (N-1). Each arrow points into a distinct rectangular block labeled "AI/ML model 0", "AI/ML model 1", an ellipsis, and "AI/ML model (N-1)" respectively. From the right side of each block, a horizontal arrow points outwards, representing the "Model output: intermediate positioning measurement".
+
+Diagram of assisted positioning with single-TRP construction and N models for N TRPs
+
+Figure 6.4.1-4: Assisted positioning with single-TRP construction, and N models for N TRPs.
+
+#### **KPIs:**
+
+- For all scenarios and use cases, the main KPI is the CDF percentiles of horizontal accuracy
+- The CDF percentiles to analyse are: 90% (baseline) and {50%, 67%, 80%} (optional)
+- Vertical accuracy can be optionally reported
+- Target positioning requirements for horizontal accuracy and vertical accuracy are not defined for AI/ML-based positioning evaluation
+
+- Model complexity, e.g., number of model parameters, and computational complexity, e.g., FLOPs
+ - Model complexity is reported via the metric of "number of model parameters". Note: if complex value is used in modelling process, the number of the model parameters is doubled, which is also applicable for other AIs of AI/ML.
+ - Companies describe how their computational complexity values are obtained. It is out of 3GPP scope to consider computational complexity values that have platform-dependency and/or use implementation (hardware and software) optimization solutions.
+- For AI/ML assisted positioning, an intermediate performance metric of *model output*
+
+#### **Model generalization:**
+
+To investigate the model generalization capability, at least the following aspect(s) are considered for the evaluation for AI/ML based positioning:
+
+- Different drops: Training dataset from drops $\{A_0, A_1, \dots, A_{N-1}\}$ , test dataset from unseen drop(s) (i.e., different drop(s) than any in $\{A_0, A_1, \dots, A_{N-1}\}$ ). Here $N \geq 1$ .
+- Clutter parameters, e.g., training dataset from one clutter parameter (e.g., {40%, 2m, 2m}), test dataset from a different clutter parameter (e.g., {60%, 6m, 2m});
+- Network synchronization error, e.g., training dataset without network synchronization error, test dataset with network synchronization error;
+- UE/gNB RX and TX timing error;
+ - The baseline non-AI/ML method may enable the Rel-17 enhancement features (e.g., UE Rx TEG, UE RxTx TEG).
+- InF scenarios, e.g., training dataset from one InF scenario (e.g., InF-DH), test dataset from a different InF scenario (e.g., InF-HH)
+- The following issues related to measurements on the positioning accuracy of the AI/ML model. The simulation assumptions reflecting these issues are up to companies.
+ - SNR mismatch (i.e., SNR when training data are collected is different from SNR when model inference is performed).
+ - Time varying changes (e.g., mobility of clutter objects in the environment)
+ - Channel estimation error
+
+For both direct AI/ML approach and AI/ML assisted approach, for a given AI/ML model design (e.g., input, output, single-TRP vs multi-TRP), identify the generalization aspects where model fine-tuning/mixed training dataset/model switching is necessary.
+
+#### **Evaluation assumptions:**
+
+The IIoT indoor factory (InF) scenario is a prioritized scenario for evaluation of AI/ML based positioning. Specifically, InF-DH sub-scenario is prioritized for FR1 and FR2.
+
+Reuse the common scenario parameters defined in Table 6-1 of TR 38.857. For evaluation of InF-DH scenario, the parameters are modified from TR 38.857 Table 6.1-1 as shown in Table 6.4.1-1. The parameters in the table are applicable to InF-DH at least. If other InF sub-scenario is evaluated in addition to InF-DH, some parameters in Table 6-5 may be updated. If an InF scenario different from InF-DH is evaluated for the model generalization capability, the selected parameters (e.g., clutter parameters) are compliant with TR 38.901 Table 7.2-4 (Evaluation parameters for InF). Note: In TR 38.857 Table 6.1-1 (Parameters common to InF scenarios), InF-SH scenario uses the clutter parameter {20%, 2m, 10m} which is compliant with TR 38.901.
+
+**Table 6.4.1-1: Parameters common to InF scenario (Modified from TR 38.857 Table 6.1-1) for AI/ML based positioning evaluations**
+
+| | FR1 specific values | FR2 specific values |
+|---------------|---------------------|---------------------|
+| Channel model | InF-DH | InF-DH |
+
+| | | | |
+|------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Layout | Hall size | InF-DH:<br>(baseline) 120x60 m<br>(optional) 300x150 m | |
+| | BS locations | 18 BSs on a square lattice with spacing $D$ , located $D/2$ from the walls. <ul style="list-style-type: none"> <li>- for the small hall (<math>L=120\text{m} \times W=60\text{m}</math>): <math>D=20\text{m}</math></li> <li>- for the big hall (<math>L=300\text{m} \times W=150\text{m}</math>): <math>D=50\text{m}</math></li> </ul> <img alt="Diagram of a rectangular hall with length L and width W. A square lattice of 18 base stations (BSs) is shown as black dots. The spacing between BSs is D. The first and last BSs in each row and column are located at a distance of D/2 from the respective walls. The diagram shows the horizontal spacing D and the vertical spacing D, with the offset from the walls labeled D/2." data-bbox="651 387 1264 712" src="f2c195cafc9541703723427873c93a64_img.jpg"/> | |
+| | Room height | 10 m | |
+| Total gNB TX power, dBm | | 24dBm | 24dBm<br>EIRP should not exceed 58 dBm |
+| gNB antenna configuration | | (M, N, P, Mg, Ng) = (4, 4, 2, 1, 1),<br>$dH=dV=0.5\lambda$ according to Table A.2.1-7 in TR 38.802.<br>Note: Other gNB antenna configurations are not precluded for evaluation. | (M, N, P, Mg, Ng) = (4, 8, 2, 1, 1),<br>$dH=dV=0.5\lambda$ according to Table A.2.1-7 in TR 38.802.<br>One TXRU per polarization per panel is assumed. |
+| gNB antenna radiation pattern | | Single sector according to Table A.2.1-7 in TR 38.802. | 3-sector antenna configuration according to Table A.2.1-7 in TR 38.802 |
+| Penetration loss | | 0dB | |
+| Number of floors | | 1 | |
+| UE horizontal drop procedure | | Uniformly distributed over the horizontal evaluation area for obtaining the CDF values for positioning accuracy, The evaluation area should be selected from <ul style="list-style-type: none"> <li>- (baseline) the whole hall area, and the CDF values for positioning accuracy is obtained from whole hall area.</li> <li>- (optional) the convex hull of the horizontal BS deployment, and the CDF values for positioning accuracy is obtained from the convex hull.</li> </ul> | |
+| UE antenna height | | Baseline: 1.5m<br>(Optional): uniformly distributed within $[0.5, X2]$ m, where $X2 = 2\text{m}$ for scenario 1 (InF-SH) and $X2= h_c$ for scenario 2 (InF-DH) | |
+| UE mobility | | 3km/h | |
+| Min gNB-UE distance (2D), m | | 0m | |
+| gNB antenna height | | Baseline: 8m<br>(Optional): two fixed heights, either {4, 8} m, or {max(4, $h_c$ ), 8}. | |
+| Clutter parameters: {density $r$ , height $h_c$ , size $d_{clutter}$ } | | High clutter density: <ul style="list-style-type: none"> <li>- {60%, 6m, 2m}</li> <li>- {40%, 2m, 2m} - can be considered optional in the evaluations considering specific AI/ML designs.</li> </ul> | |
+| Channel Estimation | | Assumption, e.g., realistic or ideal channel estimation, error models, receiver algorithms should be reported. | |
+| Spatial consistency | | If enabled for the evaluations:<br>Model at least one of: large scale parameters, small scale parameters and absolute time of arrival, where: <ul style="list-style-type: none"> <li>- the large scale parameters are according to clause 7.5 of TR 38.901 and correlation distance = <math>d_{clutter}/2</math> for InF (clause 7.6.3.1 of TR 38.901)</li> <li>- the small scale parameters are according to clause 7.6.3.1 of TR 38.901</li> <li>- the absolute time of arrival is according to clause 7.6.9 of TR 38.901</li> </ul> | |
+
+| | |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | Baseline evaluation does not incorporate spatially consistent UT/BS mobility modelling (clause 7.6.3.2 of TR 38.901). It is optional to implement it. |
+| Baseline for performance evaluation | Existing Rel-16/Rel-17 positioning methods. Specific existing positioning method (e.g., DL-TDOA, Multi-RTT) used as comparison is to be reported. |
+
+For the evaluation of AI/ML based positioning, the study of model input due to different number of TRPs include the following approaches. Proponents of each approach are to provide analysis for model performance, signalling overhead (including training data collection and model inference), model complexity and computational complexity.
+
+- Approach 1: Model input size stays constant as $N_{\text{TRP}}=18$ . The number of TRPs ( $N'_{\text{TRP}}$ ) that provide measurements to model input varies. When $N'_{\text{TRP}} < N_{\text{TRP}}$ , the remaining ( $N_{\text{TRP}} - N'_{\text{TRP}}$ ) TRPs do not provide measurements to model input, i.e., measurement value is set such that the ( $N_{\text{TRP}} - N'_{\text{TRP}}$ ) TRPs do not affect model output.
+ - Approach 1-A. The set of TRPs ( $N'_{\text{TRP}}$ ) that provide measurements is fixed.
+ - Approach 1-B. The set of TRPs ( $N'_{\text{TRP}}$ ) that provide measurements can change dynamically.
+ - Note: for Approach 1, one model is provided to cover the entire evaluation area.
+- Approach 2: The TRP dimension of model input is equal to the number of TRPs ( $N'_{\text{TRP}}$ ) that provide measurements as model input. When $N'_{\text{TRP}} < N_{\text{TRP}}$ , the remaining ( $N_{\text{TRP}} - N'_{\text{TRP}}$ ) TRPs are ignored by the given model.
+ - Approach 2-A. The set of active TRPs ( $N'_{\text{TRP}}$ ) that provide measurements is fixed.
+ - For both Approach 1-A and 2-A: one model can be provided to cover the entire evaluation area, which is equivalent to deploying $N'_{\text{TRP}}$ TRPs in the evaluation area for positioning if ignoring the potential inference from the remaining ( $18 - N'_{\text{TRP}}$ ) TRPs.
+ - Approach 2-B: The set of active TRPs ( $N'_{\text{TRP}}$ ) that provide measurements can change dynamically.
+ - For Approach 2-B, one model is developed to handle various patterns of active TRPs.
+ - For Approach 2, if $N_{\text{model}} (N_{\text{model}} > 1)$ models are provided to cover the entire evaluation area, the total model complexity is the summation of the $N_{\text{model}}$ models.
+
+In the evaluation of AI/ML based positioning, if $N'_{\text{TRP}} < 18$ , the set of $N'_{\text{TRP}}$ TRPs that provide measurements to model input of an AI/ML model are reported using the TRP indices shown in Figure 6.4.1-5.
+
+
+
+Figure 6.4.1-5: TRP layout and their indices for the evaluation of AI/ML based positioning. The diagram shows a rectangular area of width L and height W. Inside, 18 TRPs are arranged in a grid-like pattern. The top row has TRPs 0, 3, 6, 9, 12, 15. The second row has TRPs 1, 4, 7, 10, 13, 16. The third row has TRPs 2, 5, 8, 11, 14, 17. Vertical spacing between rows is labeled D, with the bottom row at D/2 from the bottom edge. Horizontal spacing between columns is labeled D, with the rightmost column at D/2 from the right edge.
+
+Figure 6.4.1-5: TRP layout and their indices for the evaluation of AI/ML based positioning.
+
+For the evaluation of AI/ML based positioning method, the measurement size and signalling overhead for the model input are reported.
+
+Impact from implementation imperfections is to be studied. Further, how AI/ML positioning accuracy is affected by user density/size of the training dataset is to be also studied. Note: details of user density/size of training dataset to be reported in the evaluation.
+
+#### ***Model input, model output:***
+
+For the model input used in evaluations of AI/ML based positioning, if time-domain channel impulse response (CIR) or power delay profile (PDP) is used as model input in the evaluation, companies report the input dimension $N_{\text{TRP}} * N_{\text{port}} * N_t$ , where $N_{\text{TRP}}$ is the number of TRPs, $N_{\text{port}}$ is the number of transmit/receive antenna port pairs, $N_t$ is the number of consecutive time domain samples. If $N'_t$ ( $N'_t < N_t$ ) samples with the strongest power are selected as model input, with remaining ( $N_t - N'_t$ ) time domain samples set to zero, then companies report value $N'_t$ in addition to $N_t$ . It is also assumed that timing info for the $N'_t$ samples need to be provided as model input.
+
+For evaluation of AI/ML based positioning, when time domain samples are used as model input and sub-sampling is applied, the selection of $N'_t$ measurements is based on the strongest power, unless explicitly stated otherwise. When sub-sampling is applied the $N'_t$ measurement are not necessarily consecutive in time.
+
+- Training dataset and test dataset use the same measurement selection method (e.g., strongest power) unless explicitly stated otherwise.
+- Other selection methodologies for $N'_t$ measurements are also evaluated, and are not precluded.
+
+For evaluations, companies used the following values for sampling period:
+
+- 16 Sources used the following sampling period:
+ - Sampling period = $1/(N_f \times \Delta f)$ . For FR1, sampling period = $1/(4096 \times 30) = 8.14$ (ns), where $N_f = 4096$ according to 38.211, and $\Delta f = 30$ kHz is the subcarrier spacing.
+- 1 Source used: sampling period = 4.069 ns
+
+If the model input is the CIR, then each input value of the CIR is a complex number, i.e., it contains two real values, either {real, imaginary} or {magnitude, phase}. If the model input is the PDP, then each input value of the PDP is a real value. Optionally companies can use delay profile (DP) as a type of information for model input. DP is a degenerated version of PDP, where the path power is not provided.
+
+Note: CIR and PDP may have different dimensions. Companies to provide details on their assumption on how PDP is constructed and how (if applicable) it is mapped to $N_t$ samples.
+
+For evaluation of AI/ML based positioning, when timing information is included in model input (e.g., in CIR/PDP/DP), training dataset and test dataset use the same timing format (i.e., both are absolute time, or both are relative time) unless explicitly stated otherwise.
+
+For evaluation of AI/ML based positioning with multipath measurement for model input,
+
+- For a given set of parameters ( $N'_{\text{TRP}}$ , $N_t$ , $N'_t$ , $N_{\text{port}}$ )
+ - CIR has the largest measurement size, where CIR is composed of a list of measurements where each measurement contains the information of: (a) delay, (b) power and (c) phase.
+ - PDP has smaller measurement size than CIR, where PDP is composed of a list of measurements where each measurement contains the information of: (a) delay and (b) power.
+ - DP has the smallest measurement size, where DP is composed of a list of measurements where each measurement contains the information of: (a) delay.
+- For each model input type (CIR, PDP, DP)
+ - The measurement size increases (approximately) linearly as $N'_{\text{TRP}}$ increases, where $N'_{\text{TRP}}$ is the number of active TRPs that provide measurements for the positioning.
+ - The measurement size increases (approximately) linearly as $N_{\text{port}}$ increases, where $N_{\text{port}}$ is the number of transmit/receive antenna port pairs that provide measurements for the positioning.
+ - If $N'_t$ ( $N'_t < N_t$ ) measurements are selected as model input, measurement size for model input increases (approximately) linearly with $N'_t$ ;
+
+- For model input type CIR and PDP, if the full set of $N_t$ measurements in time domain is used as model input, measurement size for model input increases (approximately) linearly with $N_t$ ;
+- Note: if DP is used as model input, DP does not use full set of $N_t$ measurements in time domain (i.e., $N_t' < N_t$ always).
+- Note: for Case 2b and 3b, measurement size of model input has impact to signalling overhead for model inference, data collection, and monitoring.
+- Note: There are trade-offs between measurement size / signalling overhead and positioning accuracy when using different sets of parameters ( $N_t'_{TRP}$ , $N_t$ , $N_t'$ , $N_{port}$ ).
+
+For both the direct AI/ML positioning and AI/ML assisted positioning, the model input is studied, considering the trade-off among model performance, model complexity and computational complexity:
+
+- The type of information to use as model input. The candidates include at least: time-domain CIR, PDP.
+- The dimension of model input in terms of $N_{TRP}$ , $N_t$ , and $N_t'$ .
+- Note: For the direct AI/ML positioning, model input size has impact to signalling overhead for model inference
+
+At least for model inference of AI/ML assisted positioning, evaluate and report the AI/ML model output, including:
+
+- a) the type of information (e.g., ToA, RSTD, AoD, AoA, LOS/NLOS indicator) to use as model output,
+- b) soft information vs hard information,
+- c) whether the model output can reuse existing measurement report (e.g., NRPPa, LPP).
+
+#### **Labels:**
+
+The performance impact from availability of the ground-truth labels (i.e., some training data may not have ground-truth labels) is to be studied. The learning algorithm (e.g., supervised learning, semi-supervised learning) is to be reported by participating companies and, when providing evaluation results, data labelling details need to be described, including:
+
+- Meaning of the label (e.g., UE coordinates; binary identifier of LOS/NLOS; ToA)
+- Percentage of training data without label, if incomplete labelling is considered in the evaluation
+- Imperfection of the ground-truth labels, if any
+
+Whether, and if so how, an entity can be used to obtain ground-truth label and/or other training data is to be studied.
+
+For direct AI/ML positioning, the impact of labelling error to positioning accuracy is studied considering:
+
+- The ground-truth label error in each dimension of x-axis and y-axis can be modelled as a truncated Gaussian distribution with zero mean and standard deviation of L meters, with truncation of the distribution to the $[-2*L, 2*L]$ range. Value L is up to sources.
+
+For AI/ML assisted positioning with TOA as model output, study the impact of labelling error to TOA accuracy and/or positioning accuracy.
+
+- The ground-truth label error of TOA is calculated based on location error. The location error in each dimension of x-axis and y-axis can be modelled as a truncated Gaussian distribution with zero mean and standard deviation of L meters, with truncation of the distribution to the $[-2*L, 2*L]$ range.
+ - Value L is up to sources.
+- Other models of labelling error are not precluded
+- Other timing information, e.g., RSTD, as model output is not precluded.
+
+For AI/ML assisted positioning with LOS/NLOS indicator as model output, study the impact of labelling error to LOS/NLOS indicator accuracy and/or positioning accuracy.
+
+- The ground-truth label error of LOS/NLOS indicator can be modelled as m% LOS label error and n% NLOS label error. Value m and n are up to sources.
+
+- $m\% = FN/N_{LOS}$ is false negative rate of the training data label, where FN (False Negative) is the number of actual LOS links which are incorrectly labelled as NLOS, and $N_{LOS}$ is the total number of actual LOS links;
+- $n\% = FP/N_{NLOS}$ is the false positive rate of the training data label, FP (False Positive) is the number of actual NLOS links which are incorrectly labelled as LOS, and $N_{NLOS}$ is the total number of actual NLOS links
+- Companies consider at least hard-value LOS/NLOS indicator as model output.
+
+#### **Training dataset:**
+
+Synthetic dataset generated according to the statistical channel models in TR 38.901 is used for model training, validation, and testing. The dataset is generated by a system level simulator based on 3GPP simulation methodology.
+
+As a starting point, the training, validation and testing dataset are from the same large-scale and small-scale propagation parameters setting. Subsequent evaluations can study the performance when the training dataset and testing dataset are from different settings.
+
+Details of the training dataset generation are to be reported, including:
+
+- The size of training dataset, e.g., the total number of UEs in the evaluation area for generating training dataset;
+- The distribution of UE location for generating the training dataset may be one of the following:
+ - Option 1: grid distribution, i.e., one training data is collected at the center of one small square grid, where, for example, the width of the square grid can be 0.25/0.5/1.0 m.
+ - Option 2: uniform distribution, i.e., the UE location is randomly and uniformly distributed in the evaluation area.
+
+#### **Sub-use case specific:**
+
+For AI/ML-assisted positioning, companies report which construction is applied in their evaluation:
+
+- a) Single-TRP construction: the input of the ML model is the channel measurement between the target UE and a single TRP, and the output of the ML model is for the same pair of UE and TRP.
+- b) Multi-TRP construction: the input of the ML model contains N sets of channel measurements between the target UE and N ( $N > 1$ ) TRPs, and the output of the ML model contains N sets of values, one for each of the N TRPs.
+
+Notes: For a measurement (e.g., RSTD) which is a relative value between a given TRP and a reference TRP, the TRP in "single-TRP" and "multi-TRP" refers to the given TRP only. For single-TRP construction, companies report whether they consider same model for all TRPs or N different models for TRPs.
+
+When single-TRP construction is used for the AI/ML model, companies report at least the AI/ML complexity (Model complexity, Computation complexity) for N TRPs, which are used to determine the position of a target UE considering the various constructions in Table 6.4.1-2 below.
+
+**Table 6.4.1-2: Model complexity and computational complexity to support N TRPs for a target UE**
+
+| | Model complexity to support N TRPs | Computational complexity to process N TRPs |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
+| Single-TRP, same model for N TRPs | $P_S$<br>where $P_S$ is the model complexity for one TRP and the same model is used for N TRPs. | $N \times C_S$<br>where $C_S$ is the computation complexity of the same model for one TRP. |
+| Single-TRP, N models for N TRPs | $\sum_{i=1, \dots, N} P_{S,i}$<br>where $P_{S,i}$ is the model complexity for the i-th AI/ML model. | $\sum_{i=1, \dots, N} C_{S,i}$<br>where $C_{S,i}$ is the computation complexity for the i-th AI/ML model. |
+| Multi-TRP (i.e., one model for N TRPs) | $P_M$<br>where $P_M$ is the model complexity for the one model. | $C_M$<br>where $C_M$ is the computation complexity for the one model. |
+
+Note: The reported model complexity above is intended for inference and may not be directly applicable to complexity of other LCM aspects
+
+For evaluation of AI/ML assisted positioning, the following intermediate performance metrics are used:
+
+- LOS classification accuracy, if the model output includes LOS/NLOS indicator of hard values, where the LOS/NLOS indicator is generated for a link between UE and TRP;
+- Timing estimation accuracy (expressed in meters), if the model output includes timing estimation (e.g., ToA, RSTD).
+- Angle estimation accuracy (in degrees), if the model output includes angle estimation (e.g., AoA, AoD).
+- Companies provide info on how LOS classification accuracy and timing/angle estimation accuracy are estimated, if the ML output is a soft value that represents a probability distribution (e.g., probability of LOS, probability of timing, probability of angle, mean and variance of timing/angle, etc.)
+
+#### ***Model monitoring:***
+
+For AI/ML assisted approach, the performance of model monitoring metrics is studied at least where the metrics are obtained from inference accuracy of model output (i.e., label-based model monitoring methods). Further, the performance of label-free model monitoring methods, which do not require ground-truth label (or its approximation) for model monitoring, is to be studied.
+
+For direct AI/ML positioning, the performance of model monitoring methods is studied, including:
+
+- Label based methods, where ground-truth label (or its approximation) is provided for monitoring the accuracy of model output.
+- Label-free methods, where model monitoring does not require ground-truth label (or its approximation).
+
+#### ***Model Fine-tuning:***
+
+For evaluation of the potential performance benefits of model finetuning, training dataset setting (e.g., training dataset size necessary for performing model finetuning) and horizontal positioning accuracy (in meters) before and after model finetuning, are to be reported.
+
+For both direct and AI/ML assisted positioning methods, investigate at least the impact of the amount of fine-tuning data on the positioning accuracy of the fine-tuned model. The fine-tuning data is the training dataset from the target deployment scenario.
+
+### **6.4.2 Performance results**
+
+POS\_Table 1 through POS\_Table 5 in attached Spreadsheets for Positioning accuracy enhancements evaluations present the performance results for:
+
+- POS\_Table 1. Evaluation results for supervised learning without generalization considerations (i.e., same setting for training and testing).
+- POS\_Table 2. Evaluation results for supervised learning with generalization considerations (i.e., different setting for training and testing).
+- POS\_Table 3. Evaluation results for fine-tuning to handle various generalization aspects
+- POS\_Table 4. Evaluation results for supervised learning with label error
+- POS\_Table 5. Evaluation results for semi-supervised learning
+
+#### ***Observations:***
+
+Direct AI/ML positioning can significantly improve the positioning accuracy compared to existing RAT-dependent positioning methods when the generalization aspects are not considered.
+
+For InF-DH with clutter parameter setting {60%, 6m, 2m}, evaluation results indicate that the direct AI/ML positioning can achieve horizontal positioning accuracy of <1m at CDF=90%, as compared to >15m for conventional positioning methods.
+
+Based on evaluation results of 3 sources, direct AI/ML positioning and AI/ML assisted positioning can achieve comparable performance when simulation assumptions and parameters (e.g., clutter parameter, model input type, model input size, training dataset size, model complexity) are held the same, $E_{\text{direct}} = (0.57 \sim 1.14) \times E_{\text{assisted}}$ , where
+
+- $E_{\text{assisted}}$ (meters) is the horizontal positioning accuracy at CDF=90% of AI/ML assisted positioning with multi-TRP construction with timing information as model output,
+- $E_{\text{direct}}$ (meters) is the horizontal positioning accuracy at CDF=90% of direct AI/ML positioning
+
+AI/ML assisted positioning can significantly improve the positioning accuracy compared to existing RAT-dependent positioning methods when the generalization aspects are not considered.
+
+- For InF-DH with clutter parameter setting {40%, 2m, 2m}, evaluation results indicate that the AI/ML assisted positioning can achieve horizontal positioning accuracy of <0.4m at CDF=90%, as compared to >9m for conventional positioning method.
+- For InF-DH with clutter parameter setting {60%, 6m, 2m}, evaluation results indicate that the AI/ML assisted positioning can achieve horizontal positioning accuracy of <1m at CDF=90%, as compared to >15m for conventional positioning method.
+
+#### *Model monitoring*
+
+For AI/ML assisted positioning, evaluation results have been provided by sources for label-based model monitoring methods. With TOA and/or LOS/NLOS indicator as model output, the estimated ground-truth label (i.e., TOA and/or LOS/NLOS indicator) is provided by the location estimation from the associated conventional positioning method. The associated conventional positioning method refers to the method which utilizes the AI/ML model output to determine target UE location.
+
+For both direct AI/ML and AI/ML assisted positioning, evaluation results have been provided by sources to demonstrate the feasibility of label-free model monitoring methods.
+
+#### *Model complexity and computational complexity*
+
+For AI/ML based positioning method, companies have submitted evaluation results to show that for their evaluated cases, for a given company's model design, a lower complexity (model complexity and computational complexity) model can still achieve acceptable positioning accuracy (e.g., <1m), albeit degraded, when compared to a model with higher AI/ML complexity.
+
+In Figure 6.4.2-1 below, the model inference complexity reported by companies for the positioning use case is shown, including (a) on the x-axis: model complexity in number of real parameters (millions) and (b) on the y-axis: computational complexity in FLOPs (millions). Figure 6.4.2-1 shows the range of complexity for the following schemes: (1) direct positioning; (2) assisted positioning with multi-TRP; (3) assisted positioning with single-TRP and one-model for N TRPs; and (4) assisted positioning with single-TRP and N models for N TRPs. For details of the complexity values corresponding to Figure 6.4.2-1, please see POS\_Table 1.
+
+For the three schemes of AI/ML assisted positioning, the complexity is calculated according to Table 6.4.1-2. Both model complexity and computational complexity values are as reported by participating companies. There is no effort to align the procedure across companies on how the complexity values are obtained. In addition, optimizing AI/ML complexity (i.e., model complexity and computational complexity) is out of scope of the study item.
+
+
+
+Scatter plot titled 'Reported complexity' showing Computational complexity in FLOPs (Millions) on the y-axis (logarithmic scale from 10^-2 to 10^4) versus Model complexity in number of real parameters (Millions) on the x-axis (logarithmic scale from 10^-3 to 10^2). Four data series are plotted: Direct positioning (blue circles), Assisted positioning, multi-TRP (red crosses), Single-TRP, one model for N TRP (magenta inverted triangles), and single-TRP, N models for N TRP (black stars). The plot shows a general positive correlation between model complexity and computational complexity, with Direct positioning generally requiring the highest computational complexity for a given model complexity, while single-TRP, N models for N TRP generally requires the lowest.
+
+**Figure 6.4.2-1: Model complexity and computational complexity for four schemes of AI/ML based positioning.**
+
+#### 6.4.2.1 Training Data Collection
+
+##### *Observations:*
+
+For data collection of training dataset for AI/ML based positioning, for a given deployment scenario (e.g., InF-scenario, clutter parameter, drop) and with uniform UE distribution, the required sample density (e.g., #samples/m<sup>2</sup>) for achieving a given positioning accuracy target varies with AI/ML design choices including:
+
+- different positioning approach (direct AI/ML, AI/ML-assisted),
+- different type of model input,
+- the size of model input,
+- AI/ML complexity (model complexity and computational complexity).
+
+For AI/ML based positioning, the positioning accuracy is affected by the training dataset size for a given UE distribution area (or equivalently, sample density in #samples/m<sup>2</sup>), when the UE is distributed uniformly in training data collection.
+
+- There exists a tradeoff between the training dataset size and the achievable positioning accuracy. The larger the training dataset size (i.e., higher sample density), the smaller the positioning error (in meters), until a saturation point is reached where additional training data does not bring further improvement to the positioning accuracy.
+- Note: here a sample refers to the training data collected of one UE at one location. Sample density is equivalent to the density of UEs with data collected in the training dataset.
+
+Evaluation results demonstrate that the performance of AI/ML positioning with the evaluation area as the convex hull of the horizontal BS deployment shows better performance than that with the whole hall area as evaluation area. This is due to: (a) convex hull case has higher sample density if using the same training dataset size, since convex hull has smaller UE distribution area; (b) for whole hall area, the UEs located outside the convex hull have diminished access to TRPs.
+
+- For convex hull: UE distribution area = 100x40 m;
+- For whole hall area: UE distribution area = 120x60 m
+
+#### 6.4.2.2 Generalization Aspects
+
+##### *Observations:*
+
+##### *Direct AI/ML positioning*
+
+Evaluation of the following *generalization aspects* show that the positioning accuracy of direct AI/ML positioning deteriorates when the AI/ML model is trained with dataset of one deployment scenario, while tested with dataset of a different deployment scenario.
+
+- The generalization aspects include:
+ - Different drops
+ - Different clutter parameters
+ - Different InF scenarios
+ - Network synchronization error
+- Companies have provided evaluation results which show that the positioning accuracy on the test dataset can be improved by better training dataset construction and/or model fine-tuning/re-training.
+ - Better training dataset construction: The training dataset is composed of data from multiple deployment scenarios, which include data from the same deployment scenario as the test dataset.
+ - Model fine-tuning/re-training: the model is re-trained/fine-tuned with a dataset from the same deployment scenario as the test dataset.
+
+Note: Ideal model training and switching may provide the upper bound of achievable performance when the AI/ML model needs to handle different deployment scenarios.
+
+For direct AI/ML positioning, based on evaluation results of *timing error* in the range of 0-50 ns, when the model is trained by a dataset with UE/gNB RX and TX timing error $t_1$ (ns) and tested in a deployment scenario with UE/gNB RX and TX timing error $t_2$ (ns), for a given $t_1$ ,
+
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ smaller than $t_1$ is better than the cases with $t_2$ equal to $t_1$ . For example,
+ - For the case of $(t_1, t_2)=(50\text{ns}, 30\text{ns})$ , evaluation results show the positioning error of $(t_1, t_2)=(50\text{ns}, 30\text{ns})$ is 0.82~0.86 times that of $(t_1, t_2)=(50\text{ns}, 50\text{ns})$ .
+ - For the case of $(t_1, t_2)=(50\text{ns}, 0\text{ns})$ , evaluation results show the positioning error of $(t_1, t_2)=(50\text{ns}, 0\text{ns})$ is 0.80~0.82 times that of $(t_1, t_2)=(50\text{ns}, 50\text{ns})$ .
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ greater than $t_1$ is worse than the cases with $t_2$ equal to $t_1$ . The larger the difference between $t_1$ and $t_2$ , the more the degradation. For example,
+ - For the case of $(t_1, t_2)=(0\text{ns}, 10\text{ns})$ , evaluation results show the positioning error of $(t_1, t_2)=(0\text{ns}, 10\text{ns})$ is 1.25~18.7 times that of $(t_1, t_2)=(0\text{ns}, 0\text{ns})$ .
+ - For the case of $(t_1, t_2)=(0\text{ns}, 50\text{ns})$ , evaluation results show the positioning error of $(t_1, t_2)=(0\text{ns}, 50\text{ns})$ is 3.5~18.3 times that of $(t_1, t_2)=(0\text{ns}, 0\text{ns})$ .
+
+Note: Here the positioning error is the horizontal positioning error (meters) at CDF=90%.
+
+For direct AI/ML positioning, based on evaluation results of *network synchronization error* in the range of 0-50 ns, when the model is trained by a dataset with network synchronization error $t_1$ (ns) and tested in a deployment scenario with network synchronization error $t_2$ (ns), for a given $t_1$ ,
+
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ smaller than $t_1$ is better than the cases with $t_2$ equal to $t_1$ . For example,
+
+- For the case of $(t1, t2)=(50\text{ns}, 10\text{ns})$ , evaluation results show the positioning error of $(t1, t2)=(50\text{ns}, 10\text{ns})$ is 0.52~0.83 times that of $(t1, t2)=(50\text{ns}, 50\text{ns})$ .
+- For the case of $(t1, t2)=(50\text{ns}, 0\text{ns})$ , evaluation results show the positioning error of $(t1, t2)=(50\text{ns}, 0\text{ns})$ is 0.50~0.82 times that of $(t1, t2)=(50\text{ns}, 50\text{ns})$ .
+- For a case evaluated by a given source, the positioning accuracy of cases with $t2$ greater than $t1$ is worse than the cases with $t2$ equal to $t1$ . The larger the difference between $t1$ and $t2$ , the more the degradation. For example,
+ - For the case of $(t1, t2)=(0\text{ns}, 10\text{ns})$ , evaluation results show the positioning error of $(0\text{ns}, 10\text{ns})$ is 1.17~9.5 times that of $(0\text{ns}, 0\text{ns})$ .
+ - For the case of $(t1, t2)=(0\text{ns}, 50\text{ns})$ , evaluation results show the positioning error of $(0\text{ns}, 50\text{ns})$ is 10~40 times that of $(0\text{ns}, 0\text{ns})$ .
+
+Note: here the positioning error is the horizontal positioning error (meters) at CDF=90%.
+
+##### *AI/ML assisted positioning*
+
+For AI/ML assisted positioning with timing information (e.g., ToA) as model output, evaluation of the following *generalization aspects* show that:
+
+- the positioning accuracy deteriorates when the AI/ML model is trained with dataset of one deployment scenario, while tested with dataset of a different deployment scenario.
+ - Different drops
+ - Different clutter parameters
+ - Different InF scenarios
+- the positioning accuracy may or may not deteriorate when the AI/ML model is trained with dataset of one deployment scenario, while tested with dataset of a different deployment scenario.
+ - Network synchronization error
+ - UE/gNB RX and TX timing error
+ - SNR mismatch
+ - Channel estimation error
+
+For AI/ML assisted positioning, evaluation results demonstrate that for the *generalization aspects* of:
+
+- Different drops
+- Different clutter parameters
+- Different InF scenarios
+- Network synchronization error
+- UE/gNB RX and TX timing error
+- SNR mismatch
+- Channel estimation error
+
+if the positioning accuracy **would deteriorate** when the AI/ML model is trained with dataset of one deployment scenario and tested with dataset of a different deployment scenario, the positioning accuracy on the test dataset can be improved by better training dataset construction and/or model fine-tuning/re-training.
+
+- Better training dataset construction: The training dataset is composed of data from multiple deployment scenarios, which include data from the same deployment scenario as the test dataset.
+- Model fine-tuning/re-training: the model is re-trained/fine-tuned with a dataset from the same deployment scenario as the test dataset.
+
+Note: Ideal model training and switching may provide the upper bound of achievable performance when the AI/ML model needs to handle different deployment scenarios.
+
+For AI/ML assisted positioning with timing information (e.g., ToA) as model output, based on evaluation results of *network synchronization error* in the range of 0-50 ns, when the model is trained by a dataset with network synchronization error $t_1$ (ns) and tested in a deployment scenario with network synchronization error $t_2$ (ns), for a given $t_1$ ,
+
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ smaller than $t_1$ is better than the cases with $t_2$ equal to $t_1$ . For example,
+ - For the case of $(t_1, t_2)=(50\text{ns}, 20\sim 25\text{ns})$ , evaluation results show the positioning error of $(t_1, t_2)=(50\text{ns}, 20\sim 25\text{ns})$ is 0.64~0.85 times that of $(t_1, t_2)=(50\text{ns}, 50\text{ns})$ .
+ - For the case of $(t_1, t_2)=(50\text{ns}, 0\text{ns})$ , evaluation results show the positioning error of $(t_1, t_2)=(50\text{ns}, 0\text{ns})$ is 0.50~0.80 times that of $(t_1, t_2)=(50\text{ns}, 50\text{ns})$ .
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ greater than $t_1$ is worse than the cases with $t_2$ equal to $t_1$ . The larger the difference between $t_1$ and $t_2$ , the more the degradation. For example,
+ - For the case of $(t_1, t_2)=(0\text{ns}, 10\text{ns})$ , evaluation results show the positioning error of $(0\text{ns}, 10\text{ns})$ is 1.16~4.40 times that of $(0\text{ns}, 0\text{ns})$ .
+ - For the case of $(t_1, t_2)=(0\text{ns}, 20\sim 25\text{ns})$ , evaluation results show the positioning error of $(0\text{ns}, 20\sim 25\text{ns})$ is 2.19~10.11 times that of $(0\text{ns}, 0\text{ns})$ .
+ - For the case of $(t_1, t_2)=(0\text{ns}, 50\text{ns})$ , evaluation results show the positioning error of $(0\text{ns}, 50\text{ns})$ is 9.68~31.95 times that of $(0\text{ns}, 0\text{ns})$ .
+
+Note: Here the positioning error is the horizontal positioning error (meters) at CDF=90%.
+
+For AI/ML assisted positioning with timing information (e.g., ToA) as model output, based on evaluation results of *timing error* in the range of 0-50 ns, when the model is trained by a dataset with UE/gNB RX and TX timing error $t_1$ (ns) and tested in a deployment scenario with UE/gNB RX and TX timing error $t_2$ (ns), for a given $t_1$ ,
+
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ smaller than $t_1$ is better than the cases with $t_2$ equal to $t_1$ . For example,
+ - For the case of $(t_1, t_2)=(50\text{ns}, 20\sim 25\text{ns})$ , evaluation results ~~submitted to RAN1#113~~ show the positioning error of $(t_1, t_2)=(50\text{ns}, 20\sim 25\text{ns})$ is 0.75~1.00 times that of $(t_1, t_2)=(50\text{ns}, 50\text{ns})$ .
+ - For the case of $(t_1, t_2)=(50\text{ns}, 0\text{ns})$ , evaluation results ~~submitted to RAN1#113~~ show the positioning error of $(t_1, t_2)=(50\text{ns}, 0\text{ns})$ is 0.76~0.99 times that of $(t_1, t_2)=(50\text{ns}, 50\text{ns})$ .
+- For a case evaluated by a given source, the positioning accuracy of cases with $t_2$ greater than $t_1$ is worse than the cases with $t_2$ equal to $t_1$ . The larger the difference between $t_1$ and $t_2$ , the more the degradation. For example,
+ - For the case of $(t_1, t_2)=(0\text{ns}, 10\text{ns})$ , evaluation results ~~submitted to RAN1#113~~ show the positioning error of $(t_1, t_2)=(0\text{ns}, 10\text{ns})$ is 1.34~5.43 times that of $(t_1, t_2)=(0\text{ns}, 0\text{ns})$ .
+ - For the case of $(t_1, t_2)=(0\text{ns}, 20\sim 25\text{ns})$ , evaluation results ~~submitted to RAN1#113~~ show the positioning error of $(t_1, t_2)=(0\text{ns}, 20\sim 25\text{ns})$ is 5.66~13.0 times that of $(t_1, t_2)=(0\text{ns}, 0\text{ns})$ .
+ - For the case of $(t_1, t_2)=(0\text{ns}, 50\text{ns})$ , evaluation results ~~submitted to RAN1#113~~ show the positioning error of $(t_1, t_2)=(0\text{ns}, 50\text{ns})$ is 10.62~51.52 times that of $(t_1, t_2)=(0\text{ns}, 0\text{ns})$ .
+
+Note: Here the positioning error is the horizontal positioning error (meters) at CDF=90%.
+
+##### ***Both direct AI/ML positioning and AI/ML assisted positioning***
+
+For **both** direct AI/ML and AI/ML assisted positioning, evaluation results submitted show that with CIR model input for a trained model,
+
+- For two SNR/SINR values $S_1$ (dB) and $S_2$ (dB), $S_1 \geq S_2 + 15$ dB, positioning error of a model trained with data of $S_1$ (dB) and tested with data of $S_2$ (dB) is more than 5.75 times that of the model trained and tested with data of $S_1$ (dB).
+
+- For two SNR/SINR values S1 (dB) and S2 (dB), $S1 \leq S2 - 10$ dB, the generalization performance of a model trained with data of S1 (dB) and tested with data of S2 (dB) is better than the performance of a model trained with data of S2 (dB) and tested with data of S1 (dB). Positioning error of a model trained with data of S2 (dB) and tested with data of S1 (dB) is more than 2.97 times that of the model trained with data of S1 (dB) and tested with data of S2 (dB).
+
+Note: Here the positioning error is the horizontal positioning error (meters) at CDF=90%.
+
+It is concluded that no dedicated evaluation is needed for the positioning accuracy performance of model switching.
+
+#### 6.4.2.3 Fine-tuning
+
+##### *Observations:*
+
+##### *Direct AI/ML positioning*
+
+For **direct AI/ML positioning and different drops**, evaluation has been performed where the AI/ML model is (a) previously trained for drop A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for drop B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under drop B and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 6 sources when fine-tuning dataset size is $x\% = 1.3\% \sim 2.5\%$ of full training dataset size, the positioning error is $E = (3.15 \sim 10.89) \times E_{0,B}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = 4.0\% \sim 5.0\%$ of full training dataset size, the positioning error is $E = (2.20 \sim 8.82) \times E_{0,B}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = 6.3\% \sim 10.0\%$ of full training dataset size, the positioning error is $E = (1.99 \sim 7.21) \times E_{0,B}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = 12.0\% \sim 25.0\%$ of full training dataset size, the positioning error is $E = (1.58 \sim 5.13) \times E_{0,B}$ ; 1 source the positioning error is $E = (10.46) \times E_{0,B}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 34.0\% \sim 50.0\%$ of full training dataset size, the positioning error is $E = (1.22 \sim 2.70) \times E_{0,B}$ ; 1 source the positioning error is $E = (8.88) \times E_{0,B}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = 100.0\%$ of full training dataset size, the positioning error is $E = (1.00 \sim 1.19) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for drop B.
+
+For **direct AI/ML positioning and different drops**, evaluation has been performed where the AI/ML model is (a) previously trained for drop A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for drop B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under drop A and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 3 sources when fine-tuning dataset size is $x\% = 2.5\% \sim 5.0\%$ of full training dataset size, the positioning error is $E = (3.00 \sim 5.76) \times E_{0,A}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 10.0\% \sim 25.0\%$ of full training dataset size, the positioning error is $E = (3.35 \sim 5.96) \times E_{0,A}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 50.0\% \sim 100.0\%$ of full training dataset size, the positioning error is $E = (4.50 \sim 7.71) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for drop A.
+
+For **direct AI/ML positioning and different clutter parameters**, evaluation has been performed where the AI/ML model is (a) previously trained for clutter parameter A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for clutter parameter B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under clutter parameter B and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 8 sources when fine-tuning dataset size is $x\% = 1.3\% \sim 2.5\%$ of full training dataset size, the positioning error is $E = (1.8 \sim 10.18) \times E_{0,B}$ ;
+
+- 11 sources when fine-tuning dataset size is $x\% = 4.0\% \sim 8.0\%$ of full training dataset size, the positioning error is $E = (1.77 \sim 7.05) \times E_{0,B}$ ;
+- 9 sources when fine-tuning dataset size is $x\% = 10.0\% \sim 17.0\%$ of full training dataset size, the positioning error is $E = (1.50 \sim 5.34) \times E_{0,B}$ ; 1 source the positioning error is $E = (14.65) \times E_{0,B}$ ;
+- 5 sources when fine-tuning dataset size is $x\% = 20.0\% \sim 34.0\%$ of full training dataset size, the positioning error is $E = (1.01 \sim 1.75) \times E_{0,B}$ ; 1 source the positioning error is $E = (12.23) \times E_{0,B}$ ;
+- 5 sources when fine-tuning dataset size is $x\% = 50.0\%$ of full training dataset size, the positioning error is $E = (1.09 \sim 1.25) \times E_{0,B}$ ;
+- 4 sources when fine-tuning dataset size is $x\% = 95.0\% \sim 100.0\%$ of full training dataset size, the positioning error is $E = (0.82 \sim 1.84) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for clutter parameter B.
+
+For **direct** AI/ML positioning and **different clutter parameters**, evaluation has been performed where the AI/ML model is (a) previously trained for clutter parameter A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for clutter parameter B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under clutter parameter A and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 6 sources when fine-tuning dataset size is $x\% = 2.5\%$ of full training dataset size, the positioning error is $E = (2.24 \sim 22.11) \times E_{0,A}$ ;
+- 7 sources when fine-tuning dataset size is $x\% = (5.0\% \sim 5.6\%)$ of full training dataset size, the positioning error is $E = (2.02 \sim 19.49) \times E_{0,A}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = (10.0\% \sim 25.0\%)$ of full training dataset size, the positioning error is $E = (1.40 \sim 18.65) \times E_{0,A}$ ;
+- 5 sources when fine-tuning dataset size is $x\% = 50.0\%$ of full training dataset size, the positioning error is $E = (1.20 \sim 10.72) \times E_{0,A}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 95.0\% \sim 100.0\%$ of full training dataset size, the positioning error is $E = (2.08 \sim 12.58) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for clutter parameter A.
+
+For **direct** AI/ML positioning and **different network synchronization error**, evaluation has been performed where the AI/ML model is (a) previously trained for network synchronization error = A (ns) with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for network synchronization error = B (ns) with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under network synchronization error = B (ns) and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 5 sources when fine-tuning dataset size is $x\% = (1.3\% \sim 2.5\%)$ of full training dataset size, the positioning error is $E = (0.98 \sim 5.21) \times E_{0,B}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = (4.0\% \sim 8.0\%)$ of full training dataset size, the positioning error is $E = (0.84 \sim 10.70) \times E_{0,B}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = (10.0\% \sim 25.0\%)$ of full training dataset size, the positioning error is $E = (0.80 \sim 10.38) \times E_{0,B}$ ;
+- 1 source when fine-tuning dataset size is $x\% = (50.0\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (0.81 \sim 1.1) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for network synchronization error = B (ns).
+
+For **direct** AI/ML positioning and **different network synchronization error**, evaluation has been performed where the AI/ML model is (a) previously trained for network synchronization error = 0 ns with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for network synchronization error = 50 ns with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under network synchronization error = 0 ns and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 2 sources when fine-tuning dataset size is $x\% = (2.5\% \sim 10.0\%)$ of full training dataset size, the positioning error is $E = (5.08 \sim 23.44) \times E_{0,A}$ ;
+- 1 source when fine-tuning dataset size is $x\% = (25.0\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (2.28 \sim 3.92) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for network synchronization error = 0 ns.
+
+For **direct AI/ML positioning and different UE timing error**, evaluation has been performed where the AI/ML model is (a) previously trained **without UE timing error** with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning **with UE timing error** with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested **with UE timing error** and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 2 sources when fine-tuning dataset size is $x\% = 1.3\% \sim 20.0\%$ of full training dataset size, the positioning error is $E = (0.51 \sim 2.53) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for the case **with UE timing error**.
+
+For **direct AI/ML positioning and different InF scenarios**, evaluation has been performed where the AI/ML model is (a) previously trained for InF scenario A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for InF scenario B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under InF scenario B and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 5 sources when fine-tuning dataset size is $x\% = (2.0\% \sim 5.6\%)$ of full training dataset size, the positioning error is $E = (0.5 \sim 16.67) \times E_{0,B}$ ;
+- 5 sources when fine-tuning dataset size is $x\% = (8.0\% \sim 15.0\%)$ of full training dataset size, the positioning error is $E = (0.4 \sim 12.6) \times E_{0,B}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = 25.0\%$ of full training dataset size, the positioning error is $E = (1.60 \sim 1.67) \times E_{0,B}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = (50.0\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (0.92 \sim 1.41) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for InF scenario B.
+
+For **direct AI/ML positioning and different InF scenarios**, evaluation has been performed where the AI/ML model is (a) previously trained for InF scenario A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for InF scenario B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under InF scenario A and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 3 sources when fine-tuning dataset size is $x\% = (2.5\% \sim 10.0\%)$ of full training dataset size, the positioning error is $E = (2.28 \sim 30.2) \times E_{0,A}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = (25.0\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (1.7 \sim 9.24) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for InF scenario A.
+
+For **direct AI/ML positioning and different SNR value (dB)**, evaluation has been performed where the AI/ML model is (a) previously trained for SNR value A (dB) with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for SNR value B (dB) with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under SNR value B (dB) and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = (5.6\% \sim 11.1\%)$ of full training dataset size, the positioning error is $E = (1.60 \sim 1.90) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for SNR value B (dB).
+
+For **direct AI/ML positioning and different time varying assumptions**, evaluation has been performed where the AI/ML model is (a) previously trained for the scenario without time varying change with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for the scenario with time varying change with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under the scenario with time varying change and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = (3.7\% \sim 22.0\%)$ of full training dataset size, the positioning error is $E = (1.68 \sim 3.49) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for the scenario with time varying change.
+
+For **direct** AI/ML positioning and **different channel estimation error**, evaluation has been performed where the AI/ML model is (a) previously trained for channel estimation error = 20 dB with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for channel estimation error = 0 dB with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under channel estimation error = 0 dB and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = (2.5\% \sim 25.0\%)$ of full training dataset size, the positioning error is $E = (1.50 \sim 2.79) \times E_{0,B}$ ;
+- 1 source when fine-tuning dataset size is $x\% = (50.0\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (0.96 \sim 1.17) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for channel estimation error = 0 dB.
+
+For **direct** AI/ML positioning and **different channel estimation error**, evaluation has been performed where the AI/ML model is (a) previously trained for channel estimation error = 20 dB with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for channel estimation error = 0 dB with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under channel estimation error = 20 dB and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = (2.5\% \sim 25.0\%)$ of full training dataset size, the positioning error is $E = (4.22 \sim 5.95) \times E_{0,A}$ ;
+- 1 source when fine-tuning dataset size is $x\% = (50.0\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (3.08 \sim 3.94) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for channel estimation error = 20 dB.
+
+##### **AI/ML assisted positioning**
+
+For AI/ML **assisted** positioning with timing information as model output and for **different drops**, evaluation has been performed where the AI/ML model is (a) previously trained for drop A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for drop B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under drop B and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 2 sources when fine-tuning dataset size is $x\% = (2.0\% \sim 10.0\%)$ of full training dataset size, the positioning error is $E = (1.27 \sim 7.68) \times E_{0,B}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = (12.0\% \sim 34.0\%)$ of full training dataset size, the positioning error is $E = (5.59 \sim 12.88) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for drop B.
+
+For AI/ML **assisted** positioning with timing information as model output and for **different clutter parameters**, evaluation has been performed where the AI/ML model is (a) previously trained for clutter parameter A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for clutter parameter B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under clutter parameter B and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 5 sources when fine-tuning dataset size is $x\% = (2.0\% \sim 2.5\%)$ of full training dataset size, the positioning error is $E = (1.47 \sim 5.88) \times E_{0,B}$ ;
+- 6 sources when fine-tuning dataset size is $x\% = (4.0\% \sim 5.0\%)$ of full training dataset size, the positioning error is $E = (1.39 \sim 4.42) \times E_{0,B}$ ;
+- 7 sources when fine-tuning dataset size is $x\% = (8.0\% \sim 12.0\%)$ of full training dataset size, the positioning error is $E = (1.34 \sim 3.93) \times E_{0,B}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 25.0\%$ of full training dataset size, the positioning error is $E = (1.33 \sim 1.91) \times E_{0,B}$ ;
+
+- 3 sources when fine-tuning dataset size is $x\% = 50.0\%$ of full training dataset size, the positioning error is $E = (1.15 \sim 1.33) \times E_{0,B}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = 100.0\%$ of full training dataset size, the positioning error is $E = (0.89 \sim 1.15) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for clutter parameter B.
+
+For AI/ML **assisted** positioning with timing information as model output and for **different clutter parameters**, evaluation has been performed where the AI/ML model is (a) previously trained for clutter parameter A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for clutter parameter B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under clutter parameter A and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 4 sources when fine-tuning dataset size is $x\% = (2.5\% \sim 5.0\%)$ of full training dataset size, the positioning error is $E = (1.47 \sim 12.94) \times E_{0,A}$ ;
+- 5 sources when fine-tuning dataset size is $x\% = 10.0\%$ of full training dataset size, the positioning error is $E = (1.32 \sim 11.52) \times E_{0,A}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 25.0\%$ of full training dataset size, the positioning error is $E = (1.22 \sim 7.65) \times E_{0,A}$ ;
+- 3 sources when fine-tuning dataset size is $x\% = 50.0\%$ of full training dataset size, the positioning error is $E = (1.2 \sim 5.86) \times E_{0,A}$ ;
+- 2 sources when fine-tuning dataset size is $x\% = 100.0\%$ of full training dataset size, the positioning error is $E = (2.64 \sim 4.66) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for the clutter parameter A.
+
+For AI/ML **assisted** positioning and **different network synchronization error**, evaluation has been performed where the AI/ML model is (a) previously trained for network synchronization error A (ns) with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for network synchronization error B (ns) with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under network synchronization error B (ns) and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 5 sources when fine-tuning dataset size is $x\% = 2.0\% \sim 5.0\%$ of full training dataset size, the positioning error is $E = (1.28 \sim 5.44) \times E_{0,B}$ ;
+- 5 sources when fine-tuning dataset size is $x\% = 8.0\% \sim 25.0\%$ of full training dataset size, the positioning error is $E = (1.10 \sim 4.07) \times E_{0,B}$ ;
+- 1 source when fine-tuning dataset size is $x\% = 50.0\% \sim 100.0\%$ of full training dataset size, the positioning error is $E = (1.01 \sim 1.47) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for network synchronization error B (ns).
+
+For AI/ML **assisted** positioning and **different network synchronization error**,
+
+- evaluation has been performed where the AI/ML model is (a) previously trained for network synchronization error = 0 ns with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for network synchronization error = 50 ns with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under network synchronization error = 0 ns and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that, denoting $E_{0,A}$ (meters) as the full training accuracy at CDF=90% for network synchronization error = 0 ns,
+ - 2 sources when fine-tuning dataset size is $x\% = (2.5\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (3.71 \sim 5.97) \times E_{0,A}$ ;
+- evaluation has been performed where the AI/ML model is (a) previously trained for network synchronization error = 50 ns with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for network synchronization error = 0 ns with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under network synchronization error = 50 ns and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results
+
+show that, denoting $E_{0,A}$ (meters) as the full training accuracy at CDF=90% for network synchronization error = 50 ns,
+
+- 1 source when fine-tuning dataset size is $x\% = (2.5\% \sim 100.0\%)$ of full training dataset size, the positioning error is $E = (1.15 \sim 2.23) \times E_{0,A}$ ;
+
+For AI/ML **assisted** positioning and **different InF scenarios**, evaluation has been performed where the AI/ML model is (a) previously trained for InF scenario A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for InF scenario B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under InF scenario B and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 3 sources when fine-tuning dataset size is $x\% = (2.0\% \sim 12.0\%)$ of full training dataset size, the positioning error is $E = (1.20 \sim 6.0) \times E_{0,B}$ ;
+- 1 source when fine-tuning dataset size is $x\% = 25.0\% \sim 50.0\%$ of full training dataset size, the positioning error is $E = (2.55 \sim 2.91) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ (meters) is the full training accuracy at CDF=90% for InF scenario B.
+
+For AI/ML **assisted** positioning and **different InF scenarios**, evaluation has been performed where the AI/ML model is (a) previously trained for InF-DH{60%,6m,2m} with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for InF-SH{20%,2m,10m} with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under InF-DH{60%,6m,2m} and the horizontal accuracy at CDF=90% is $E$ meters. Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = 2.5\% \sim 50.0\%$ of full training dataset size, the positioning error is $E = (2.53 \sim 3.44) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ (meters) is the full training accuracy at CDF=90% for InF-DH{60%,6m,2m}.
+
+For AI/ML **assisted** positioning with LOS/NLOS indicator as model output and for **different clutter parameters**, evaluation has been performed where the AI/ML model is (a) previously trained for clutter parameter A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for clutter parameter B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under clutter parameter B and the LOS/NLOS indication accuracy is $E$ (using F1-score). Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = 10.0\%$ of full training dataset size, the accuracy (using F1-score) of LOS/NLOS indicator is $E = (0.56 \sim 0.974) \times E_{0,B}$ ;
+
+Here $E_{0,B}$ is the full training accuracy (using F1-score) for the clutter parameter B.
+
+For AI/ML **assisted** positioning with LOS/NLOS indicator as model output and for **different clutter parameters**, evaluation has been performed where the AI/ML model is (a) previously trained for clutter parameter A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for clutter parameter B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under clutter parameter A and the LOS/NLOS indication accuracy is $E$ (using F1-score). Evaluation results show that,
+
+- 1 source when fine-tuning dataset size is $x\% = 10.0\%$ of full training dataset size, the accuracy (using F1-score) of LOS/NLOS indicator is $E = (0.09 \sim 0.24) \times E_{0,A}$ ;
+
+Here $E_{0,A}$ is the full training accuracy (using F1-score) for the clutter parameter A.
+
+##### ***Both direct AI/ML positioning and AI/ML assisted positioning***
+
+As a summary of the observations above, for both direct AI/ML positioning and AI/ML assisted positioning, evaluation results show that:
+
+- Fine-tuning/re-training a previous model with dataset of the new deployment scenario improves the model performance for the new deployment scenario. For details on the amount of improvement, see the observations listed above.
+- After fine-tuning/re-training a previous model with dataset of the new deployment scenario, the performance of the updated model degrades for the previous deployment scenario (e.g., previous clutter parameter setting) that the previous model was trained for.
+
+- Examples of the deployment scenario include: different drops, different clutter parameter, different InF scenarios
+
+For both direct AI/ML positioning and AI/ML assisted positioning,
+
+- if the new deployment scenario is significantly different from the previous deployment scenario the model was trained for (e.g., different drops, different clutter parameter, different InF scenarios), fine-tuning a previous model requires similarly large training dataset size as training the model from scratch, in order to achieve the similar performance for the new deployment scenario.
+- If the new deployment scenario is NOT significantly different from the previous deployment scenario the model was trained for (e.g., 2ns difference in network synchronization error between the previous and the new deployment scenario), fine-tuning a previous model requires a small (e.g., $x\% = 10\%$ ) training dataset size as compared to training the model from scratch, in order to achieve the similar performance for the new deployment scenario.
+
+#### 6.4.2.4 Model-input Size Reduction
+
+**Observations:**
+
+##### **Direct AI/ML positioning**
+
+For the evaluation of direct AI/ML positioning, with $N_t$ consecutive time domain samples used as model input, evaluation results show that when CIR, PDP, or DP is used as model input, using different $N_t$ while holding other parameters the same,
+
+- Reducing $N_t$ from 256 to 128 does not appreciably degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/2 that of $N_t=256$ .
+- Positioning error of $N_t=128$ is 0.81 ~ 1.19 times the positioning error of $N_t=256$ ;
+- Reducing $N_t$ from 256 to 64~32 may degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/4 ~ 1/8 that of $N_t=256$ , respectively.
+- Positioning error of $N_t=64$ is 0.88 ~ 3.00 times the positioning error of $N_t=256$ ;
+- Positioning error of $N_t=32$ is 1.05 ~ 4.29 times the positioning error of $N_t=256$ ;
+- Note: the variation in the positioning accuracy depends on each company's simulation assumption (e.g., AI/ML complexity).
+
+For direct AI/ML positioning, the evaluation of positioning accuracy at model inference is affected by the type of model input and AI/ML complexity. For a given AI/ML model design, there is a tradeoff between model input, AI/ML complexity (model complexity and computational complexity), and positioning accuracy. Evaluation results show that if changing model input type while holding other parameters (e.g., $N_t$ , $N'_t$ , $N_{\text{port}}$ , $N'_{\text{TRP}}$ ) the same,
+
+- When comparing PDP and CIR as model input,
+ - 9 sources showed evaluation results where the positioning error of PDP as model input is 1.06 ~ 1.62 times the positioning error of CIR as model input.
+ - 5 sources showed evaluation results where the positioning error of PDP as model input is 0.61 ~ 0.96 times the positioning error of CIR as model input.
+- When comparing DP and CIR as model input,
+ - 4 sources showed evaluation results where the positioning error of DP as model input is 1.18 ~ 1.96 times the positioning error of CIR as model input.
+ - 2 sources showed evaluation results where the positioning error of DP as model input is 0.79~0.92 times the positioning error of CIR as model input.
+- Note: For one of the sources (R1-2306112), the difference in relative performance is due to the complexity of the AI/ML model.
+- Note: For another source (R1-2307920), the difference in relative performance is due to the parameter settings.
+
+- Note: the variation in the positioning accuracy depends on each company's simulation assumption (e.g., AI/ML complexity).
+
+For the evaluation of direct AI/ML positioning, when $N_t$ time domain samples with the strongest power are selected as model input, evaluation results show that:
+
+- For model input of CIR or PDP and $N_t=256$ , using different $N_t$ while holding other parameters constant,
+ - Reducing $N_t$ from 256 to 64 does not appreciably degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/4 that of $N_t=N_t'=256$ .
+ - Positioning error of $N_t'=128$ is 1.02 ~ 1.07 times the positioning error of $N_t=N_t'=256$ ;
+ - Positioning error of $N_t'=64$ is 1.02 ~ 1.21 times the positioning error of $N_t=N_t'=256$ ;
+ - Reducing $N_t$ from 256 to 32~16 degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/8 ~ 1/16 that of $N_t=N_t'=256$ .
+ - Positioning error of $N_t'=32$ is 1.14 ~ 2.03 times the positioning error of $N_t=N_t'=256$ ;
+ - Positioning error of $N_t'=16$ is 1.12 ~ 2.54 times the positioning error of $N_t=N_t'=256$ ;
+ - Reducing $N_t$ from 256 to 9~8 degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/32 that of $N_t=N_t'=256$ .
+ - Positioning error of $N_t'=9\sim 8$ is 1.42 ~ 3.29 times the positioning error of $N_t=N_t'=256$ ;
+- For model input of DP and $N_t=256$ , using different $N_t$ while holding other parameters constant,
+ - One source (R1-2304339) showed that reducing $N_t$ from 64 to 32 does not degrade the positioning accuracy while the measurement size and signalling overhead shrink by (approximately) 1/2.
+ - Positioning error of $N_t'=32$ is 1.03 times the positioning error of $N_t'=64$ .
+- Note: the evaluation results based on the other model input (e.g., multiple path) can be added in next meeting
+
+Based on evaluation results by 8 sources, for TRP reduction of **direct** AI/ML positioning, approaches supporting dynamic TRP pattern can achieve the horizontal positioning accuracy $E_{dynamic} = (0.80\sim 2.15) \times E_{fixed}$ (meters), when other design parameters are held the same, where:
+
+- $E_{dynamic}$ (meters) is the horizontal positioning accuracy at CDF=90% for approaches supporting dynamic TRP pattern (i.e., Approach 1-B and 2-B);
+- $E_{fixed}$ (meters) is the horizontal positioning accuracy at CDF=90% for approaches supporting fixed TRP pattern (i.e., Approach 1-A and 2-A);
+
+Based on evaluation results by 8 sources, for TRP reduction of **direct** AI/ML positioning, Approach 1-A and 2-A achieve similar performance. The horizontal positioning accuracy $E_{2A} = (0.87\sim 1.32) \times E_{1A}$ (meters), when other design parameters are held the same, where:
+
+- $E_{1A}$ (meters) is the horizontal positioning accuracy at CDF=90% for Approach 1-A;
+- $E_{2A}$ (meters) is the horizontal positioning accuracy at CDF=90% for Approach 2-A;
+
+Based on evaluation results by 11 sources, for TRP reduction of **direct** AI/ML positioning, the positioning accuracy degrades as the number of active TRPs are reduced from 18 TRPs to 3 TRPs. The degradation increases as the number of active TRPs decreases.
+
+- When the number of active TRP is reduced from $N_{TP} = 18$ to $N'_{TP} = 12\sim 8$ , the average horizontal positioning accuracy $E$ is in the range of $E = (1.48\sim 1.95) \times E_{18TRP}$ ;
+- When the number of active TRP is reduced from $N_{TP} = 18$ to $N'_{TP} = 6\sim 5$ , the average horizontal positioning accuracy $E$ is in the range of $E = (2.35\sim 3.04) \times E_{18TRP}$ ;
+- When the number of active TRP is reduced from $N_{TP} = 18$ to $N'_{TP} = 4\sim 3$ , the average horizontal positioning accuracy $E$ is in the range of $E = (2.13\sim 5.11) \times E_{18TRP}$ ;
+
+Here $E$ (meters) is the horizontal positioning accuracy at CDF=90% with $N'_{\text{TP}}$ active TRPs, $E_{18\text{TRP}}$ (meters) is the horizontal positioning accuracy at CDF=90% with $N_{\text{TP}} = 18$ active TRPs.
+
+Note: some results from 2 sources show $E > 11 \times E_{18\text{TRP}}$ for $N'_{\text{TP}} = 9$ and 6 when using Approach 2-B.
+
+##### *AI/ML assisted positioning*
+
+For AI/ML assisted positioning, the positioning accuracy at model inference is affected by the type of model input. Evaluation results show that if changing model input type while holding other parameters (e.g., $N_t$ , $N'_t$ , $N_{\text{port}}$ , $N'_{\text{TRP}}$ ) the same,
+
+- The positioning error of PDP as model input is 1.17 ~ 1.63 times the positioning error of CIR as model input.
+- The positioning error of DP as model input is 1.33 ~ 2.01 times the positioning error of CIR as model input.
+
+For AI/ML assisted positioning, with $N_t$ consecutive time domain samples used as model input, evaluation results show that when CIR or PDP are used as model input, using different $N_t$ while holding other parameters the same,
+
+- Reducing $N_t$ from 256 to 128 does not appreciably degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/2 that of $N_t=256$ .
+- Positioning error of $N_t=128$ is 1.00 ~ 1.42 times the positioning error of $N_t=256$ ;
+- Reducing $N_t$ from 256 to 64~32 may degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/4 ~ 1/8 that of $N_t=256$ , respectively.
+- Positioning error of $N_t=64$ is 1.09 ~ 3.02 times the positioning error of $N_t=256$ ;
+- Positioning error of $N_t=32$ is 2.43 ~ 5.10 times the positioning error of $N_t=256$ ;
+
+For AI/ML assisted positioning, when $N'_t$ time domain samples with the strongest power are selected as model input, evaluation results show that for model input of CIR or PDP and $N_t=256$ , using different $N'_t$ while holding other parameters the same,
+
+- Reducing $N'_t$ from 256 to 64 does not appreciably degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/4 that of $N_t=N'_t=256$ .
+- Positioning error of $N'_t=128$ is 1.00 ~ 1.33 times the positioning error of $N_t=N'_t=256$ ;
+- Positioning error of $N'_t=64$ is 0.98 ~ 1.23 times the positioning error of $N_t=N'_t=256$ ;
+- Reducing $N'_t$ from 256 to 32~16 may degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/8 ~ 1/16 that of $N_t=N'_t=256$ .
+- Positioning error of $N'_t=32$ is 1.15 ~ 1.69 times the positioning error of $N_t=N'_t=256$ ;
+- Positioning error of $N'_t=16$ is 1.04 ~ 2.67 times the positioning error of $N_t=N'_t=256$ ;
+- Reducing $N'_t$ from 256 to 9 degrade the positioning accuracy, while the measurement size and signalling overhead shrink to (approximately) 1/32 that of $N_t=N'_t=256$ .
+- Positioning error of $N'_t=9$ is 1.66 ~ 4.40 times the positioning error of $N_t=N'_t=256$ ;
+
+Based on evaluation results by 2 sources, for TRP reduction of AI/ML **assisted** positioning with multi-TRP construction, approaches supporting dynamic TRP pattern can achieve the horizontal positioning accuracy $E_{\text{dynamic}} = (1.03 \sim 1.74) \times E_{\text{fixed}}$ (meters), when other design parameters are held the same, where:
+
+- $E_{\text{dynamic}}$ (meters) is the horizontal positioning accuracy at CDF=90% for approaches supporting dynamic TRP pattern (i.e., Approach 1-B and 2-B);
+- $E_{\text{fixed}}$ (meters) is the horizontal positioning accuracy at CDF=90% for approaches supporting fixed TRP pattern (i.e., Approach 1-A and 2-A);
+
+Note: evaluation results of 1 source show $E_{\text{dynamic}} = (5.66 \sim 8.12) \times E_{\text{fixed}}$ when the number of active TRP is reduced from $N_{\text{TP}} = 18$ to $N'_{\text{TP}} = 9$ or 4.
+
+Based on evaluation results by 2 sources, for TRP reduction of AI/ML **assisted** positioning, Approach 1-A and 2-A achieve similar performance. The horizontal positioning accuracy $E_{2A} = (1 \sim 1.47) \times E_{1A}$ (meters), when other design parameters are held the same, where:
+
+- $E_{1A}$ (meters) is the horizontal positioning accuracy at CDF=90% for Approach 1-A;
+- $E_{2A}$ (meters) is the horizontal positioning accuracy at CDF=90% for Approach 2-A;
+
+Based on evaluation results by 4 sources, for TRP reduction of AI/ML **assisted** positioning, the positioning accuracy degrades as the number of active TRPs are reduced from 18 TRPs to 3 TRPs. The degradation increases as the number of active TRPs decreases.
+
+- When the number of active TRP is reduced from $N_{TP} = 18$ to $N'_{TP} = 9$ , the average horizontal positioning accuracy is $E = 2.01 \times E_{18TRP}$ ;
+- When the number of active TRP is reduced from $N_{TP} = 18$ to $N'_{TP} = 6$ , the average horizontal positioning accuracy is $E = 3.04 \times E_{18TRP}$ ;
+- When the number of active TRP is reduced from $N_{TP} = 18$ to $N'_{TP} = 3 \sim 4$ , the average horizontal positioning accuracy is $E = (5.01 \sim 6.53) \times E_{18TRP}$ ;
+
+Here $E$ (meters) is the horizontal positioning accuracy at CDF=90% with $N'_{TP}$ active TRPs, $E_{18TRP}$ (meters) is the horizontal positioning accuracy at CDF=90% with $N_{TP} = 18$ active TRPs.
+
+Note: some results from 1 source show $E > 7.54 \times E_{18TRP}$ for $N'_{TP} = 9$ and $E > 42.76 \times E_{18TRP}$ for $N'_{TP} = 6$ when using Approach 1-B/2-B.
+
+##### ***Both direct AI/ML positioning and AI/ML assisted positioning***
+
+Evaluation of TRP reduction for **both** direct AI/ML positioning and AI/ML assisted positioning shows that: identification of the active TRPs is beneficial for Approach 2-B. Otherwise, the model suffers from poor performance in terms of positioning accuracy.
+
+For example, evaluation results from 4 sources show that the horizontal positioning accuracy is greater than 10 m if TRP identification is not included as model input.
+
+#### 6.4.2.5 Non-ideal label(s)
+
+##### ***Observations:***
+
+##### ***Direct AI/ML positioning***
+
+For direct AI/ML positioning, for $L$ in the range of 0.25m to 5m, the positioning error increases approximately in proportion to $L$ , where $L$ (in meters) is the standard deviation of truncated Gaussian Distribution of the ground-truth label error.
+
+Evaluation shows that direct AI/ML positioning is robust to certain *label error* based on evaluation results of $L$ in the range of (0, 5) meter. The exact range of label error that can be tolerated depends on the positioning accuracy requirement, where tighter positioning accuracy requirement demands smaller label error.
+
+##### ***AI/ML assisted positioning***
+
+In evaluation of AI/ML assisted positioning with timing information (e.g., TOA) as model output, for $L$ in the range of 0.25m to 5m, the timing (e.g., TOA) estimation error and positioning error increases approximately in proportion to $L$ , where $L$ (in meters) is the standard deviation of truncated Gaussian distribution of the ground-truth label error.
+
+Evaluations show that AI/ML assisted positioning with timing information (e.g., ToA) as *model output* is robust to certain *label error* based on evaluation results of $L$ in the range of (0, 5) meter. The exact range of label error that can be tolerated depends on the positioning accuracy requirement, where tighter positioning accuracy requirement demands smaller label error.
+
+Based on evaluation results from 3 sources, for AI/ML assisted positioning where the model output includes the LOS/NLOS indicator, when the model is trained with dataset containing random LOS/NLOS label error, the models have no or minor degradation for LOS/NLOS identification accuracy up to at least $m\% = 20\%$ and at least $n\% = 20\%$ .
+
+When the training dataset has up to $m\%=20\%$ and $n\%=20\%$ , evaluation results show that the **LOS/NLOS identification accuracy** is $P_{\text{LablErr}} = P_{\text{noLablErr}} - d$ (percentage), where $d$ is in the range of $(-1.2\%\sim 3.1\%)$ .
+
+- $P_{\text{noLablErr}}$ (percentage) is the LOS/NLOS identification accuracy when $m\%=0\%$ and $n\%=0\%$ ;
+
+##### Other
+
+For AI/ML based positioning, evaluation results show that semi-supervised learning is helpful for improving the positioning accuracy when the same amount of ideal labelled data is used for supervised learning, and the number of ideal labelled data is limited.
+
+Regarding ground-truth label generation for AI/ML based positioning, multiple sources submitted evaluation results on the impact of ground-truth label for training obtained by existing NR RAT-dependent positioning methods. Feasibility and performance benefit of utilizing ground-truth label for training estimated by existing NR RAT-dependent positioning methods are observed.
+
+- Source 1 evaluated in InF-DH {40%, 2, 2} and showed that AI/ML model can be trained with noisy labels along with the corresponding quality estimated by the legacy positioning methods, to improve positioning performance from 3.73m@90% (5k ideal label) to 1.72m @90% (5k ideal label + 20k noisy label). It also showed that the performance benefit compared to semi-supervised training of 2.78m @90% (5k ideal label + 20k unlabeled data). Note that training data weighting is used with label quality indicator.
+- Source 2 evaluated in InF-DH {60%, 6, 2} and showed that the performance of direct AI/ML positioning with 1k clean labelled samples improves from 13.76m to 8.72m when considering additional 350 samples that are labelled using NR-RAT positioning method. Note that the label error is up to 3.5m.
+- Source 3 evaluated in both InF-DH {60%, 6, 2} and InF-DH {40%, 2, 2} and showed performance loss when compared to all ideal label case. For example it showed in InF-DH {40%, 2, 2} the accuracy degrades from 0.39m @90% (100% ideal label) to 2.10m @90% (50% ideal label and 50% label obtained by existing DL-TDOA scheme). Note that noisy label is treated the same as ideal label in training.
+
+#### 6.4.2.6 Summary of Performance Results for Positioning accuracy enhancements
+
+For the use case of positioning accuracy enhancement, extensive evaluations have been carried out. Both direct AI/ML positioning and AI/ML assisted positioning are evaluated using one-sided model. The following areas are investigated.
+
+- **Performance evaluation without generalization consideration**, where the AI/ML model is trained and tested with dataset of the same deployment scenario.
+ - o **AI/ML vs RAT-dependent positioning methods**. For the basic performance without generalization consideration, AI/ML based positioning can significantly improve the positioning accuracy compared to existing RAT-dependent positioning methods. For example, in InF-DH with clutter parameter setting {60%, 6m, 2m}, AI/ML based positioning can achieve horizontal positioning accuracy of <1m at CDF=90%, as compared to >15m for conventional positioning method.
+ - o **Impact of training data sample density** (i.e., training dataset size for a given evaluation area). Evaluation with uniform UE distribution shows that, the larger the training dataset size (i.e., higher sample density), the smaller the positioning error (in meters), until a saturation point is reached where additional training data does not bring further improvement to the positioning accuracy.
+- **AI/ML complexity**. For a given company's model design, in terms of model inference complexity (model complexity and computational complexity), a lower complexity model can still achieve acceptable positioning accuracy (e.g., <1m), albeit degraded, when compared to a higher complexity model.
+- **Generalization study**. Evaluations are carried out to investigate various generalization aspects, where the AI/ML model is trained with dataset of one deployment scenario, while tested with dataset of a different deployment scenario. The generalization aspects include: different drops; different clutter parameters; different InF scenarios; network synchronization error; UE/gNB RX and TX timing error; SNR mismatch; channel estimation error; time varying changes.
+
+Methods are evaluated which have been shown to be able to handle generalization issues, including:
+
+- **Better training dataset construction (i.e., mixed dataset)**, where the training dataset is composed of data from multiple deployment scenarios, which include data from the same deployment scenario as the test dataset.
+- **Fine-tuning/re-training**, where the model is re-trained/fine-tuned with a dataset from the same deployment scenario as the test dataset. The impact of the amount of fine-tuning data on the positioning accuracy of the fine-tuned model is evaluated for the various generalization aspects. Evaluation results are obtained for two experiments:
+ - The AI/ML model is (a) previously trained for scenario A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for scenario B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under scenario B. The horizontal positioning accuracy at CDF=90% is $E$ meters.
+ - The AI/ML model is (a) previously trained for scenario A with a dataset of sample density $N$ (#samples/m<sup>2</sup>), (b) followed by fine-tuning for scenario B with a dataset of sample density $x\% \times N$ (#samples/m<sup>2</sup>), (c) then tested under scenario A. The horizontal positioning accuracy at CDF=90% is $E$ meters.
+- **Model input size reduction**. Evaluations are carried out to examine various ways to change the model input size and its impact on positioning accuracy:
+ - Different measurement type, for example, CIR, PDP, DP.
+ - Different number of consecutive time domain samples, $N_t$ .
+ - Different number of non-zero samples $N'_t$ selected from the $N_t$ consecutive time domain samples ( $N'_t < N_t$ ).
+ - Different number of active TRPs, $N'_{\text{TRP}}$ .
+
+The model input size for various measurement type (CIR, PDP, DP) and dimensions ( $N'_{\text{TRP}}$ , $N_t$ , $N'_t$ , $N_{\text{port}}$ ) is analyzed. Evaluation results show that, model input of different measurement type and dimensions can have different reporting overhead and positioning accuracy.
+- **Fixed TRP pattern vs dynamic TRP pattern**. Evaluation results show that, approaches supporting dynamic TRP pattern may be able to achieve comparable horizontal positioning accuracy as approaches supporting fixed TRP pattern, when other design parameters are held the same.
+- **Model output of AI/ML assisted positioning**. For AI/ML assisted positioning, evaluations are carried out where the model output includes timing information and/or LOS/NLOS indicator, in the format of hard- or soft- value.
+- **Non-ideal label in the training dataset**. Evaluations are carried out to show the impact of:
+ - Label error, where the label in the training dataset is degraded from ground-truth label by an error.
+ - For direct AI/ML positioning and AI/ML assisted positioning with timing information as model output, location error in each dimension of x-axis and y-axis is modelled as a truncated Gaussian distribution.
+ - For AI/ML assisted positioning where the model output includes the LOS/NLOS indicator, random LOS/NLOS label error is applied.
+ - Absent label, where some data samples in the training dataset do not have associated labels. Semi-supervised learning is evaluated for this case.
+- **Model monitoring**. Preliminary evaluation of model monitoring methods are provided by individual companies. The following methods are shown to be feasible:
+ - Label based methods, where ground-truth label (or its approximation) is provided for monitoring the accuracy of model output.
+ - Label-free methods, where model monitoring does not require ground-truth label (or its approximation).
+
+Based on RAN1 evaluations of AI/ML based positioning,
+
+- It is beneficial to support both direct AI/ML and AI/ML assisted positioning approaches since they can significantly improve the positioning accuracy compared to existing RAT-dependent positioning methods in the evaluated indoor factory scenarios.
+- Both UE-side model and NW-side model can significantly improve the positioning accuracy compared to existing RAT-dependent positioning methods.
+- It is desired to apply methods to handle generalization aspects.
+- It is desired to consider training data collection requirements.
+- If AI/ML based positioning is considered for normative work, it is desired to further investigate model input design aspects: the model input type (e.g., CIR, PDP, DP), dimension (e.g., parameters $N'_{\text{TRP}}$ , $N_t$ , $N'_{\text{t}}$ , $N_{\text{port}}$ ) and related format (e.g., for the timing information: absolute time or relative time) considering the trade-off of positioning accuracy, signalling overhead, and AI/ML complexity.
+
+# 7 Potential specification impact assessment
+
+## 7.1 Physical layer aspects
+
+In this clause, aspects related to, e.g., the potential specification of the AI Model lifecycle management, and dataset construction for training, validation and test for the selected use cases are considered.
+
+In addition, use case and collaboration level specific specification impact is documented, such as new signalling, means for training and validation data assistance, assistance information, measurement, and feedback.
+
+### 7.1.1 Common framework
+
+*Items considered for studying the necessity, feasibility, potential specification impact:*
+
+*Performance monitoring*
+
+The following metrics/methods for AI/ML model monitoring in lifecycle management per use case are considered:
+
+- Monitoring based on inference accuracy, including metrics related to intermediate KPIs
+- Monitoring based on system performance, including metrics related to system performance KPIs
+- Other monitoring solutions, at least the following 2 options.
+ - Monitoring based on data distribution
+ - Input-based: e.g., Monitoring the validity of the AI/ML input, e.g., out-of-distribution detection, drift detection of input data, or SNR, delay spread, etc.
+ - Output-based: e.g., drift detection of output data
+ - Monitoring based on applicable condition
+
+Note: Monitoring metric calculation may be done at NW or UE
+
+Methods to assess/monitor the applicability and expected performance of an *inactive model/functionality*, including the following examples for the purpose of activation/selection/switching of UE-side models/UE-part of two-sided models /functionalities (if applicable):
+
+- Assessment/Monitoring based on the additional conditions associated with the model/functionality
+- Assessment/Monitoring based on input/output data distribution
+- Assessment/Monitoring using the inactive model/functionality for monitoring purpose and measuring the inference accuracy
+
+- Assessment/Monitoring based on past knowledge of the performance of the same model/functionality (e.g., based on other UEs)
+
+### 7.1.2 CSI feedback enhancement
+
+*Items considered for studying the necessity, feasibility, potential specification impact:*
+
+**In CSI compression using two-sided model use case:**
+
+*Performance monitoring:*
+
+- Model performance monitoring related assistance signalling and procedure.
+- Metrics/methods including:
+ - Intermediate KPIs (e.g., SGCS)
+ - Eventual KPIs (e.g., Throughput, hypothetical BLER, BLER, NACK/ACK).
+ - Legacy CSI based monitoring: schemes using additional legacy CSI reporting
+ - Other monitoring solutions, at least including the following option:
+ - Input or Output data based monitoring: such as data drift between training dataset and observed dataset and out-of-distribution detection
+- NW-side performance monitoring: NW monitors the performance and make decisions of model/functionality activation/ deactivation/updating/switching. Impact to enable performance monitoring using an existing CSI feedback scheme as the reference, including the association between AI/ML scheme and existing CSI feedback scheme for monitoring, are considered. Note: The metric for monitoring and comparison includes intermediate KPI and eventual KPI.
+- UE-side performance monitoring: UE monitors the performance and reports to Network, NW makes decisions of model/functionality activation/deactivation/updating/switching. Impact on triggering and means for reporting the monitoring metrics, including periodic/semi-persistent and aperiodic reporting, and other reporting initiated from UE, are not precluded.
+
+*Intermediate KPI based model monitoring:*
+
+The following intermediate KPI-based model monitoring options were proposed by companies:
+
+- NW-side monitoring based on the target CSI with realistic channel estimation associated to the CSI report, reported by the UE or obtained from the UE-side.
+- UE-side monitoring based on the output of the CSI reconstruction model, subject to the aligned format, associated to the CSI report, indicated by the NW or obtained from the network side.
+ - Network may configure a threshold criterion to facilitate UE to perform model monitoring.
+- UE-side monitoring based on the output of the CSI reconstruction model at the UE-side
+ - Note: CSI reconstruction model at the UE-side can be the same or different comparing to the actual CSI reconstruction model used at the NW-side. Network may configure a threshold criterion to facilitate UE to perform model monitoring.
+
+*Fallback mode:*
+
+- Potential specification impact for supporting co-existence and fallback mechanisms between AI/ML-based CSI feedback mode and legacy non-AI/ML-based CSI feedback mode
+
+*NW/UE alignment:*
+
+- Alignment of the quantization/dequantization method and the feedback message size between Network and UE, including the following:
+
+- For vector quantization scheme, the format and size of the VQ codebook, and the size and segmentation method of the CSI generation model output
+- For scalar quantization scheme, uniform and non-uniform quantization with format, e.g., quantization granularity, consisting of distribution of bits assigned to each float.
+- Quantization alignment for CSI feedback between CSI generation part at the UE and CSI reconstruction part at the NW is needed, e.g.,
+ - through model pairing process,
+ - alignment based on standardized quantization scheme.
+ - Additional methods not precluded.
+
+#### *Model input/output:*
+
+- Output-CSI-UE and input-CSI-NW at least for Precoding matrix
+- Option 1a: The precoding matrix in spatial-frequency domain
+- Option 1b: The precoding matrix represented using angular-delay domain projection
+- whether Option 2: Explicit channel matrix (i.e., full Tx \* Rx MIMO channel) is also studied depends on the performance evaluations:
+ - Option 2a: raw channel is in spatial-frequency domain
+ - Option 2b: raw channel is in angular-delay domain
+- CSI part 1 includes at least CQI for first codeword, RI, and information representing the part 2 size. CSI part 2 includes at least the content of CSI generation part output. Other CSI report formats are not precluded.
+
+#### *UE side data collection:*
+
+- Enhancement of CSI-RS configuration to enable higher accuracy measurement.
+- Assistance information for UE data collection for categorizing the data in forms of ID for the purpose of differentiating characteristics of data due to specific configuration, scenarios, site etc.
+ - The provision of assistance information needs to consider feasibility of disclosing proprietary information to the other side.
+- Signalling for triggering the data collection
+
+#### *NW side data collection:*
+
+- Enhancement of SRS and/or CSI-RS measurement and/or CSI reporting to enable higher accuracy measurement.
+- Contents of the ground-truth CSI including:
+ - Data sample type, e.g., precoding matrix, channel matrix etc.
+ - Data sample format: scalar quantization and/or codebook-based quantization (e.g., e-type II like).
+ - Assistance information (e.g., time stamps, and/or cell ID, Assistance information for Network data collection for categorizing the data in forms of ID for the purpose of differentiating characteristics of data due to specific configuration, scenarios, site etc., and data quality indicator)
+- Latency requirement for data collection
+- Signalling for triggering the data collection
+- Ground-truth CSI report for NW side data collection *for model performance monitoring*, including:
+ - Scalar quantization for ground-truth CSI
+ - Codebook-based quantization for ground-truth CSI
+
+- RRC signalling and/or L1 signalling procedure to enable fast identification of AI/ML model performance
+ - Aperiodic/semi-persistent or periodic ground-truth CSI report
+- Ground-truth CSI format *for model training*, including scalar or codebook-based quantization for ground-truth CSI. The number of layers for which the ground-truth data is collected, and whether UE or NW determine the number of layers for ground-truth CSI data collection, are considered.
+
+In CSI compression using two-sided model use case with training collaboration Type 3, for sequential training, at least the following aspects have been identified for dataset delivery from RAN1 perspective, including:
+
+- Dataset and/or other information delivery from UE side to NW side, which can be used at least for CSI reconstruction model training
+- Dataset and/or other information delivery from NW side to UE side, which can be used at least for CSI generation model training
+- Potential dataset delivery methods including offline delivery, and over the air delivery
+- Data sample format/type
+- Quantization/de-quantization related information
+
+#### *CSI configuration and report:*
+
+- NW configuration to determine CSI payload size, e.g., possible CSI payload size, possible rank restriction and/or other related configuration.
+- How UE determines/reports the actual CSI payload size and/or other CSI related information within constraints configured by the network.
+- Relevant UCI format considering the legacy CSI reporting principle with CSI Part 1 and Part 2 as a starting point, where Part 1 has a network configured fixed size and Part 2 size is dynamic, determined by information in Part 1.
+
+For CQI determination in CSI report, if CQI in CSI report is configured.
+
+- Option 1: CQI is NOT calculated based on the output of CSI reconstruction part from the realistic channel estimation, including
+ - Option 1a: CQI is calculated based on target CSI with realistic channel measurement
+ - Option 1b: CQI is calculated based on target CSI with realistic channel measurement and potential adjustment
+ - Option 1c: CQI is calculated based on legacy codebook
+- Option 2: CQI is calculated based on the output of CSI reconstruction part from the realistic channel estimation, including
+ - Option 2a: CQI is calculated based on CSI reconstruction output, if CSI reconstruction model is available at the UE and UE can perform reconstruction model inference with potential adjustment
+ - Note: CSI reconstruction part at the UE can be different comparing to the actual CSI reconstruction part used at the NW.
+ - Option 2b: CQI is calculated using two stage approach, UE derive CQI using precoded CSI-RS transmitted with a reconstructed precoder.
+- Notes: feasibility of different options should be evaluated. Gap analyses between the UE side CQI calculation results and the NW side results, as well as the impact on the scheduling performance should be evaluated. Complexity of CQI calculation needs to be evaluated, including the computing complexity and potential RS/signalling overhead.
+
+Feasibility and methods to support the legacy CSI reporting principles:
+
+- The priority rule regarding CSI collision handling and CSI omission
+- Codebook subset restriction
+
+- Input-CSI-NW/output-CSI-UE considered in angular-delay domain, beam restriction can be based on legacy SD basis vector-based input CSI in angular domain.
+- CSI processing Unit
+
+*Potential specification enhancement on:*
+
+- CSI-RS configurations (not including CSI-RS pattern design enhancements)
+- CSI configuration
+ - For network to indicate CSI reporting related information, e.g., gNB indication to the UE of one or more of following:
+ - Information indicating CSI payload size
+ - Information indicating quantization method/granularity
+ - Rank restriction
+ - Other payload related aspects
+- CSI reporting configurations
+ - For UE determination/reporting of the actual CSI payload size, UE reports related information as configured by the NW
+- CSI report UCI mapping/priority/omission
+- CSI processing procedures
+
+In CSI compression using two-sided model use case, feasibility and procedure to align the information that enables the UE to select a CSI generation model(s) compatible with the CSI reconstruction model(s) used by the gNB is studied. At least the following options have been proposed by companies to define the pairing information used to enable the UE to select a CSI generation model(s) that is compatible with the CSI reconstruction model(s) used by the gNB:
+
+- Option 1: The pairing information is in the forms of the CSI reconstruction model ID that NW will use.
+- Option 2: The pairing information is in the forms of the CSI generation model ID that the UE will use.
+- Option 3: The pairing information is in the forms of the paired CSI generation model and CSI reconstruction model ID.
+- Option 4: The pairing information is in the forms of by the dataset ID during type 3 sequential training.
+- Option 5: The pairing information is in the forms of a training session ID to a prior training session (e.g., API) between NW and UE.
+- Option 6: The pairing information is up to UE/NW offline co-engineering alignment, transparent to 3GPP specification.
+- Note: the disclosure of the vendor information during the model pairing procedure and model identification procedure should be considered.
+- Note: If each UE side model is compatible with all NW side model, the information is not needed for the UE.
+- Note: Above does not imply there is a need for a central entity for defining/storing/maintaining the IDs.
+
+#### **In CSI prediction using UE-sided model use case:**
+
+*Data collection:*
+
+In CSI prediction using UE sided model use case, at least the following aspects have been proposed by companies on data collection, including:
+
+- Signalling and procedures for the data collection
+ - Data collection indicated by NW
+
+- Requested from UE for data collection
+- CSI-RS configuration
+- Assistance information for categorizing the data, if needed
+ - The provision of assistance information needs to consider feasibility of disclosing proprietary information to the other side.
+
+#### *Performance monitoring:*
+
+For CSI prediction using UE side model use case, at least the following aspects have been proposed by companies on performance monitoring for functionality-based LCM:
+
+- Type 1:
+ - UE calculates the performance metric(s)
+ - UE reports performance monitoring output that facilitates functionality fallback decision at the network
+ - Performance monitoring output details can be further defined
+ - NW may configure threshold criterion to facilitate UE side performance monitoring (if needed).
+ - NW makes decision(s) of functionality fallback operation (fallback mechanism to legacy CSI reporting).
+- Type 2:
+ - UE reports *predicted CSI* and/or the corresponding *ground-truth*
+ - NW calculates the *performance metrics*.
+ - NW makes decision(s) of functionality fallback operation (fallback mechanism to legacy CSI reporting).
+- Type 3:
+ - UE calculates the *performance metric(s)*
+ - UE reports *performance metric(s)* to the NW
+ - NW makes decision(s) of functionality fallback operation (fallback mechanism to legacy CSI reporting).
+- Functionality selection/activation/deactivation/switching as defined for other UE side use cases can be reused, if applicable.
+- Configuration and procedure for performance monitoring
+- CSI-RS configuration for performance monitoring
+- Performance metric including at least intermediate KPI (e.g., NMSE or SGCS)
+- UE report, including periodic/semi-persistent/aperiodic reporting, and event driven report
+- Note: down selection is not precluded.
+- Note: UE may make decision within the same functionality on model selection, activation, deactivation, switching operation transparent to the NW.
+
+### 7.1.3 Beam management
+
+*Items considered for studying the necessity, feasibility, potential specification impact:*
+
+#### *Performance monitoring:*
+
+For the performance monitoring of BM-Case1 and BM-Case2:
+
+- Performance metric(s) with the following alternatives:
+
+- Alt.1: Beam prediction accuracy related KPIs, e.g., Top-K/1 beam prediction accuracy
+- Alt.2: Link quality related KPIs, e.g., throughput, L1-RSRP, L1-SINR, hypothetical BLER
+- Alt.3: Performance metric based on input/output data distribution of AI/ML
+- Alt.4: The L1-RSRP difference evaluated by comparing measured RSRP and predicted RSRP
+- Benchmark/reference for the performance comparison, including:
+ - Alt.1: The best beam(s) obtained by measuring beams of a set indicated by gNB (e.g., Beams from Set A)
+ - Alt.4: Measurements of the predicted best beam(s) corresponding to model output (e.g., Comparison between actual L1-RSRP and predicted RSRP of predicted Top-1/K Beams)
+- Signalling/configuration/measurement/report for model monitoring, e.g., signalling aspects related to assistance information (if supported), Reference signals
+
+For BM-Case1 and BM-Case2 with a UE-side AI/ML model:
+
+- Type 1 performance monitoring:
+ - Configuration/Signalling from gNB to UE for measurement and/or reporting
+ - UE may have different operations
+ - Option 1 (NW-side performance monitoring): UE sends reporting to NW (e.g., for the calculation of performance metric at NW)
+ - Option 2 (UE-assisted performance monitoring): UE calculates performance metric(s), either reports it to NW or reports an event to NW based on the performance metric(s)
+ - Indication from NW for UE to do LCM operations
+ - Note: At least the performance and reporting overhead of model monitoring mechanism should be considered
+- Type 2 performance monitoring:
+ - Indication/request/report from UE to gNB for performance monitoring
+ - Note: The indication/request/report may be not needed in some case(s)
+ - Configuration/Signalling from gNB to UE for performance monitoring measurement and/or reporting
+ - If it is for UE side model monitoring, UE makes decision(s) of model selection/activation/deactivation/switching/fallback operation
+- Mechanism that facilitates the UE to detect whether the functionality/model is suitable or no longer suitable
+
+For BM-Case1 and BM-Case2 with a NW-side AI/ML model
+
+- Beam measurement and report for model monitoring
+ - UE reporting of beam measurement(s) based on a set of beams indicated by gNB.
+ - Signalling, e.g., RRC-based, L1-based.
+ - Note: This may or may not have specification impact.
+- NW monitors the performance metric(s) and makes decision(s) of model selection/activation/deactivation/switching/ fallback operation
+- Note: Performance and UE complexity, power consumption should be considered.
+
+Table 7.2.3-1 summarizes applicability of various alternatives for performance metric(s) of AI/ML model monitoring for BM-Case1 and BM-Case2.
+
+**Table 7.2.3-1: Alternatives for Performance metric(s) of AI/ML model monitoring for BM-Case 1 and BM-Case 2**
+
+| <b>Alt. 1: Beam prediction accuracy related KPIs, e.g., Top-K/1 beam prediction accuracy</b> | <b>Alt. 2: Link quality related KPIs, .e.g., throughput, L1-RSRP, L1-SINR, hypothetical BLER</b> | <b>Alt.3: Performance metric based on input/output data distribution of AI/ML</b> | <b>Alt.4: The L1-RSRP difference evaluated by comparing measured RSRP and predicted RSRP</b> |
+|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|
+| Applicable to all studied AI models | Applicable to all studied AI models | Applicable to all studied AI models | May not applicable to some implementation of AI model (e.g., not output of predicted L1-RSRP) |
+| Reflect the prediction accuracy of AI model | Reflect the system/link performance | Reflect the change of the statics of the input/output data | Reflect accuracy of the predicted 1-RSRP |
+| Not reflect the system/link performance directly | Not reflect the prediction accuracy of AI model directly | Not reflect the prediction performance of AI model directly<br>Not reflect the system/link performance directly | Not reflect the system/link performance directly |
+
+Note1: The above analysis shall not give an indication about whether/which metric is supported or specified.
+
+Note2: Monitoring performance of the above alternatives are not addressed in the table.
+
+#### *Data collection:*
+
+At UE side for UE-side AI/ML model:
+
+- UE reporting to NW supported/preferred configurations of DL RS transmission.
+- Trigger/initiating data collection considering:
+ - Option 1: data collection initiated/triggered by configuration from NW.
+ - Option 2: request from UE for data collection.
+- Signalling/configuration/measurement/report for data collection, e.g., signalling aspects related to assistance information (if supported), Reference signals, content/type of the collected data, configuration related to Set A and/or Set B, information on association/mapping of Set A and Set B
+- Assistance information from Network to UE for UE data collection for categorizing the data for the purpose of differentiating characteristics of the data (if supported). The assistance information should preserve privacy/proprietary information.
+
+At NW side for NW-side AI/ML model:
+
+- Mechanism related to the reporting.
+- Additional information for content of the reporting.
+- Reporting overhead reduction.
+- Signalling/configuration/measurement/report for data collection, e.g., signalling aspects related to assistance information (if supported), Reference signals.
+
+Regarding data collection for NW-side AI/ML model regarding the contents of collected data:
+
+- Opt.1: M1 L1-RSRPs (corresponding to M1 beams) with the indication of beams (beam pairs) based on the measurement corresponding to a beam set, where M1 can be larger than 4, if applicable.
+- Opt.2: M2 L1-RSRPs (corresponding to M2 beams) based on the measurement corresponding to a beam set, where M2 can be larger than 4, if applicable.
+- Opt.3: M3 beam (beam pair) indices based on the measurement corresponding to a beam set, where M3 can be larger than 4, if applicable.
+- Note: Overhead, UE complexity and power consumption are to be considered for the above options.
+
+Regarding data collection for NW-side AI/ML model of BM-Case1 and BM-Case2, the following approaches have been identified for overhead reduction:
+
+- the omission/selection of collected data
+- the compression of collected data
+- Note1: For the different purposes of data collection, the overhead reduction mechanisms and corresponding specification impacts may be different.
+- Note2: Support of any mechanism(s) (if necessary) for each LCM purpose and the potential spec impact (if any) are separate discussions
+- Note 3: UE complexity and power consumption should be considered
+
+Regarding data collection for NW-side AI/ML model of BM-Case1 and BM-Case2, the following reporting signalling for beam-specific aspects maybe applicable:
+
+- L1 signalling to report the collected data
+- Higher-layer signalling to report the collected data
+ - At least not applicable to AI/ML model inference
+- Note1: Higher layer signalling design is up to RAN2
+- Note2: Whether each signalling applicable to each LCM purpose is a separate discussion
+- Note3: The legacy signalling principle (e.g. RSRP reporting for L1) can be re-used
+
+#### *Model Inference related:*
+
+In order to facilitate the AI/ML model inference:
+
+- Enhanced or new configurations/UE reporting/UE measurement, e.g., enhanced or new beam measurement and/or beam reporting
+- Enhanced or new signalling for measurement configuration/triggering
+- Signalling of assistance information (if applicable)
+
+For BM-Case1 and BM-Case2 with a UE-side AI/ML model:
+
+- Indication of the associated Set A from network to UE, e.g., association/mapping of beams within Set A and beams within Set B if applicable
+- Beam indication from network for UE reception, which may or may not have additional specification impact (e.g., legacy mechanism may be reused), particularly:
+ - how to perform beam indication of beams in Set A not in Set B. Note: also applicable to NW-side AI/ML model. Note: At least for BM-Case1 with a UE-side AI/ML model, the legacy TCI state mechanism can be used to perform beam indication of beams
+- Note: For DL beam pair prediction, there is no consensus to support the reporting of the predicted Rx beam(s) (e.g., Rx beam ID, Rx beam angle information, etc) from the UE to the network.
+- Predicted L1-RSRP(s) corresponding to the DL Tx beam(s) or beam pair(s)
+ - Whether/how to differentiate predicted L1-RSRP and measured L1-RSRP
+- Confidence/probability information related to the output of AI/ML model inference (e.g., predicted beams)
+
+For BM-Case1 and BM-Case2 with a NW-side AI/ML model:
+
+- L1 beam reporting enhancement for AI/ML model inference:
+ - UE to report the measurement results of more than 4 beams in one reporting instance
+
+- Other L1 reporting enhancements can be considered
+
+For BM-Case1 with a UE-side AI/ML model:
+
+- L1 signalling to report the following information of AI/ML model inference to NW:
+ - The beam(s) that is based on the output of AI/ML model inference.
+
+For BM-Case2 with a UE-side AI/ML model:
+
+- L1 signalling to report the following information of AI/ML model inference to NW:
+ - The beam(s) of N future time instance(s) that is based on the output of AI/ML model inference.
+ - Information about the timestamp corresponding the reported beam(s).
+
+For BM-Case 2:
+
+- Reporting information about measurements of multiple past time instances in one reporting instance. Notes: Only applicable to NW-side AI/ML model. The potential performance gains of measurement reporting should be justified by considering UCI payload overhead.
+
+*Assistance information:*
+
+Regarding the explicit assistance information from UE to network for NW-side AI/ML model, RAN1 has no consensus to support the following information
+
+- UE location
+- UE moving direction
+- UE Rx beam shape/direction
+
+Regarding the explicit assistance information from network to UE for UE-side AI/ML model, RAN1 has no consensus to support the following information
+
+- NW-side beam shape information
+ - E.g., 3dB beamwidth, beam boresight directions, beam shape, Tx beam angle, etc.
+- Note: Other information (e.g., relative information) of Tx beam(s) preserving sensitive proprietary information is a separate discussion
+ - e.g., some information following the same principle of Rel-17 positioning agreement
+
+For BM-Case1 and BM-Case2 with a UE-side AI/ML model, consistency / association of Set B beams and Set A beams across training and inference is beneficial from performance perspective.
+
+Note: Whether specification impact is needed is a separate discussion.
+
+### 7.1.4 Positioning accuracy enhancements
+
+*Items considered for studying the necessity, feasibility, potential specification impact:*
+
+*AI/ML functionality and model identification:*
+
+- Validity conditions, e.g., applicable area/[zone]/scenario/environment and time interval, etc.
+- Model capability, e.g., positioning accuracy quality and model inference latency.
+- Conditions and requirements, e.g., required assistance signalling and/or reference signals configurations, dataset information.
+- Note: the above-mentioned examples and terms "validity conditions", "model capability", and "Conditions and requirements" can be referred to the conditions and additional conditions discussed in the context of the model identification and functionality identification in clause 4.2.
+
+*Training data generation for AI/ML based positioning:*
+
+- The following options of entity and mechanisms to generate ground-truth label are identified:
+ - UE with estimated/known location generates ground-truth label and corresponding label quality indicator
+ - Based on non-NR and/or NR RAT-dependent and/or NR RAT-independent positioning methods
+ - At least for UE-based positioning with UE-side model (Case 1) and UE-assisted positioning with UE-side model (Case 2a)
+ - Network entity generates ground-truth label and corresponding label quality indicator
+ - Based on non-NR and/or NR RAT-dependent and/or NR RAT-independent positioning methods
+ - At least for UE-assisted/LMF-based positioning with LMF-side model (Case 2b), NG-RAN node assisted positioning with gNB-side model (Case 3a) and NG-RAN node assisted positioning with LMF-side model (Case 3b)
+ - At least PRU is identified to generate ground-truth label for UE-based positioning with UE-side model (Case 1) and UE-assisted positioning with UE-side model (Case 2a)
+ - At least LMF with known PRU location is identified to generate ground-truth label for UE-assisted/LMF-based positioning with LMF-side model (Case 2b) and NG-RAN node assisted positioning with LMF-side model (Case 3b)
+ - At least network entity with known PRU location is identified to generate ground-truth label for NG-RAN node assisted positioning with gNB-side model (Case 3a)
+- Note: User data privacy needs to be preserved
+- The following options of entity to generate other training data (at least measurement corresponding to model input) are identified:
+ - For UE-based with UE-side model (Case 1) and UE-assisted positioning with UE-side (Case 2a) or LMF-side model (Case 2b)
+ - PRU
+ - UE
+ - For NG-RAN node assisted positioning with Network-side model (Case 3a and Case 3b)
+ - TRP
+- Note: Transfer of training data from the entity generating training data to a different entity is not precluded and associated potential specification impact is to be considered
+
+*Data collection for AI/ML based positioning:*
+
+Regarding data collection for AI/ML based positioning, at least the following information of data with potential specification impact are identified.
+
+- Ground-truth label
+ - Report from the label data generation entity
+- Measurement (corresponding to model input)
+ - Report from the measurement data generation entity
+- Quality indicator
+ - For and/or associated with ground-truth label and/or measurement
+ - Report from the label and/or the measurement data generation entity and/or as request from a different (e.g., data collection, etc.) entity
+
+- RS configuration(s)
+ - At least for deriving measurement
+ - Request from data generation entity (UE/PRU/TRP) to LMF and/or as LMF assistance signalling to UE/PRU/TRP
+ - Note 1: There may not be any enhancements on top of existing RS configuration(s) or any new RS configuration(s) for positioning measurement
+- Time stamp
+ - At least for and/or associated with collected data
+ - Separate time stamp for measurement and ground-truth label, when measurement and ground-truth label are generated by different entities
+ - Report From data generation entity together with collected data and/or as LMF assistance signalling
+ - Note 2: There may not be any enhancements on top of time stamp in existing positioning measurement report or any new time stamp report for positioning measurement
+ - Note 3: Whether and how the above information can be applied to different aspects of AI/ML LCM (e.g., training, updating, monitoring, etc.) can be discussed
+- Note 4: Transfer of data from the entity generating data to a different entity is not precluded from RAN1 perspective
+- Note 5: If any specification impact is identified, the impact may be different between positioning use cases (Case 1/2a/2b/3a/3b).
+- Note 6: The necessity of other information (e.g., scenario identifier. LOS/NLOS condition, timing error, etc.) for data collection can be discussed
+- Details of request/report of label and/or other training data, and to enable delivering the collected label and/or other training data to the training entity when the training entity is not the same entity to obtain label and/or other training data
+- Assistance signalling indicating reference signal configuration(s) to derive label and/or other training data
+- Request/report of training data: Ground-truth label; Measurement corresponding to model input; Associated information of ground-truth label and/or measurement corresponding to model input
+- Assistance signalling and procedure to facilitate generating training data: Reference signal (e.g., PRS/SRS) configuration(s) and configuration identifier; Assistance information, e.g., between LMF and UE/PRU, for label calculation/generation, and label validity/quality condition, etc.
+ - Note: whether such assistance signalling and procedure can be applied to other aspect(s) of AI/ML model LCM can also be discussed
+- Notes: Study may consider different entity to generate training data as well as different types of training data when applicable. Study considers both of the following cases when applicable: when the training entity is the same entity to generate training data, and when the training entity is not the same entity to generate training data
+
+#### *Model monitoring:*
+
+- Assistance signalling and procedure at least for UE-side model
+- Report/feedback and procedure at least for Network-side model
+ - Note: study is applicable to both of the following cases:
+ - Model inference and model monitoring at the same entity
+ - Entity to perform the model monitoring is not the same entity for model inference
+- Data for computing monitoring metric:
+
+- If monitoring based on model output: e.g., estimated UE location corresponding to model output for direct AI/ML positioning, estimated intermediate parameter(s) corresponding to model output for AI/ML assisted positioning, ground-truth label corresponding to model inference output for both direct and AI/ML assisted positioning
+- If monitoring based on model input: e.g., measurement corresponding to model inference input.
+- Assistance signalling from LMF to UE/PRU/gNB for UE/gNB-side model monitoring.
+- Assistance signalling from UE/PRU for NW-side model monitoring.
+- If certain type of data is necessary for computing monitoring metric:
+ - How an entity can be used to provide the given type of data for calculating monitoring metric: companies requested to report their assumption of the entity (or entities) used to provide the given type of data for calculating monitoring metric for each case
+ - Potential signalling for provisioning of the given type of data for calculating associated monitoring metric
+ - Potential assistance signalling and procedure to facilitate an entity providing data for calculating monitoring metric
+ - Potential UE-network interaction: e.g., model monitoring decision indication between UE and network
+- Entity to derive monitoring metric
+ - UE at least for Case 1 and 2a (with UE-side model)
+ - gNB at least for Case 3a (with gNB-side model)
+ - LMF at least for Case 2b and 3b (with LMF-side model)
+ - For AI/ML based positioning, LMF for Case 2a (with UE-side model) and Case 3a (with gNB-side model) is identified as the entity to derive the monitoring metric at least when monitoring is based on provided ground-truth label (or its approximation).
+- If model monitoring does not require ground-truth label (or its approximation).
+ - Statistics of measurement(s) compared to the statistics associated with the training data. Note: the measurement(s) may or may not be the same as model input.
+ - Examples used in contributions: norm of model input, mean, min/max of some statistics related to measurement and/or model input, median or data temporal/spatial distribution
+ - Statistics of model output compared to the statistics associated with the training data and/or its own previous inference output
+ - Examples used in contributions: mean, standard deviation, variance, etc. of some statistics related to model output
+ - For monitoring UE-side and gNB-side model for AI/ML based positioning:
+ - Signalling from LMF to facilitate the monitoring entity to derive the monitoring metric (if needed)
+ - Signalling from monitoring entity to request measurement(s) (if needed)
+ - Signalling for potential request/report of monitoring metric (if needed)
+ - Note: there may not be any specification impact
+ - For monitoring LMF-side model for AI/ML based positioning
+ - Signalling from LMF to request measurement(s) (if needed)
+ - Assistance signalling and procedure, e.g., RS configuration(s) for measurement, measurement statistics as compared to the model input statistics of the training data, etc.
+ - Report of the calculated metric and/or model monitoring decision
+
+- If model monitoring requires and is provided ground-truth label (or its approximation)
+ - Monitoring metric: statistics of the difference between model output and provided ground-truth label.
+ - Examples used in contributions: mean, standard deviation, instantaneous value, threshold of ground-truth label (or its approximation)
+ - For monitoring UE-side and gNB-side model for AI/ML based positioning:
+ - Signalling from monitoring entity to request ground-truth label (if needed)
+ - Signalling from monitoring entity to request model output (if needed)
+ - Signalling for potential request/report of monitoring metric (if needed)
+ - For monitoring LMF-side model for AI/ML based positioning
+ - Signalling from LMF to request measurement(s) (if needed)
+ - Provisioning of ground-truth label and associated label quality.
+ - Assistance signalling and procedure, e.g., from LMF to UE/gNB indicating ground-truth label and/or measurement, etc.
+ - Report of the calculated metric and/or model monitoring decision
+- Note: No extensive evaluation results on model monitoring metric comparison have been carried out
+- Note: There is no consensus during SI on whether monitoring metric will have spec impact
+
+#### *Model Inference related:*
+
+- For direct AI/ML positioning (Case 2b and 3b), type of measurement(s) as model inference input considering performance impact and associated signalling overhead
+ - Potential new measurement: CIR/PDP
+ - Existing measurement: e.g., RSRP/RSRPP/RSTD
+ - Note: Details of potential new measurement and/or potential enhancement to existing measurement is to be studied.
+- For AI/ML assisted positioning with UE-assisted (Case 2a) and NG-RAN node assisted positioning (Case 3a):
+ - Measurement report to carry model output to LMF
+ - New measurement report: e.g., ToA, path phase
+ - Existing measurement report: e.g., RSTD, LOS/NLOS indicator, RSRPP
+ - Enhancement of existing measurement report: e.g., soft information/high resolution of RSTD
+ - At least the following types of model inference output are identified as candidates providing performance benefits:
+ - Timing estimation
+ - Note: the report to LMF is derived based on and maybe different from the model inference output
+ - LOS/NLOS indicator
+ - Assistance signalling and procedure to facilitate model inference for both UE-side and Network-side model
+ - RS configurations
+
+The specification impact related to the following items is assessed:
+
+- Types of measurement as model inference input
+
+- new measurement
+- existing measurement
+- UE is assumed to perform measurement as model inference input for Case 1, Case 2a and Case 2b; TRP is assumed to perform measurement as model inference input for Case 3a and Case 3b
+- Report of measurements as model inference input to LMF for LMF-side model (Case 2b and Case 3b)
+- For AI/ML assisted positioning, new measurement report and/or potential enhancement of existing measurement report as model output to LMF for UE-assisted (Case 2a) and NG-RAN node assisted positioning (Case 3a)
+- Assistance signalling and procedure to facilitate model inference for both UE-side and Network-side model
+- New and/or enhancement to existing assistance signalling
+- Note: Whether such assistance signalling and procedure can be applied to other aspect(s) of AI/ML model LCM can also be discussed
+
+For direct AI/ML positioning with LMF-side model (Case 2b and 3b), the following types of measurement report are identified if beneficial and necessary (e.g., tradeoff positioning accuracy requirement and signalling overhead),
+
+- Take into account that existing Rel-16/17 measurement and/or expected Rel-18 measurement report may contain timing, power and phase information of the channel response
+- measurement report, which contains timing, power and phase information of the channel response
+ - At least for Case 3b
+- Measurement report, which contains timing and power information of the channel response
+- Measurement report, which contains timing information of the channel response
+- Note: Combinations of multiple measurement reports and/or post processing of the measurement reports are not precluded
+
+For direct AI/ML positioning with LMF-side model (Case 2b and 3b), the following types of measurement report with potential specification impact have been studied for AI/ML based positioning accuracy enhancement
+
+- Measurement report, which contains timing, power and phase information of the channel response
+ - If support, potential specification impact including new measurement report or enhancement to existing measurement report
+ - E.g., truncation, [feature extraction,] alignment of sample/path determination
+- Measurement report, which contains timing and power information of the channel response
+ - If support, potential specification impact including new measurement report or enhancement to existing measurement report
+ - E.g., truncation, [feature extraction,] alignment of sample/path determination
+- Measurement report, which contains timing information of the channel response
+ - If support, potential specification impact including enhancement to existing measurement report
+ - E.g., alignment of sample/path determination
+
+*LCM:*
+
+- For AI/ML based positioning accuracy enhancement, at least for Case 1 and Case 2a (model is at UE-side)
+- which aspects should be specified as conditions of a Feature/FG available for functionality-based LCM.
+- which aspects should be considered as additional conditions, and how to include them into model description information during model identification for model ID-based LCM.
+
+## 7.2 Protocol aspects
+
+In this clause, considering the use cases and as per RAN1 input, aspects related to life cycle management signalling procedures, model identification, data collection, model transfer/delivery, UE capability reporting, and applicability-related reporting are studied.
+
+### 7.2.1 Common framework
+
+#### 7.2.1.1 Signalling procedures for model and functionality life cycle management
+
+As per the functional framework in Figure 4.4-1, in this clause the signalling procedures for different scenarios for model-ID-based management and/or functionality-based management are exemplified. The procedures can at least be considered for UE-side models. From clause 4.2, these can include scenarios for which the management decision is taken by the network or by the UE. For network-side decision, this can be either network-initiated, or UE-initiated and requested to the network. While for UE-side decision, this can be either event-triggered as configured by the network and where the UE's decision is reported to the network, or UE-autonomous, with or without UE's decision being reported to the network.
+
+- Note: The mapping of these scenarios to specific use cases can be left to RAN1.
+- Note: The scenarios discussed below shall not imply support for all potential functionality and/or model Management Instructions (e.g., (de)activation, selection, switching, fallback, etc.) for every use case.
+- Note: In the figures below, Management Request/Management Instruction/Management Decision Report may include details about the model/functionality selection, (de)activation, switching or fallback.
+
+##### - **Decision by the network**
+
+###### o **Network-initiated**
+
+
+
+```
+
+sequenceDiagram
+ participant UE
+ participant Network
+ Note right of Network: Management
+ Network->>UE: Configuration (e.g., measurement, reporting)
+ UE->>Network: Performance or Assistance Information (e.g., measurements)
+ Network->>UE: Management Instruction
+
+```
+
+Sequence diagram showing network-initiated AI/ML management. The diagram has two vertical lifelines: UE and Network. The sequence of messages is: 1. Network sends 'Configuration (e.g., measurement, reporting)' to UE. 2. UE sends 'Performance or Assistance Information (e.g., measurements)' to Network. 3. The Network lifeline has a box labeled 'Management'. 4. The Network sends 'Management Instruction' to UE.
+
+**Figure 7.2.1.1-1: Network decision, network-initiated AI/ML management**
+
+The case where the LCM decision is taken and initiated by the network is depicted in Figure 7.2.1.1-1.
+
+- Note: The Management Instruction may be a result of model/functionality performance monitoring at the network.
+- Note: The Management Instruction may include information about the model or functionality.
+- o **UE-initiated and requested to the network**
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant Network
+ Note left of UE: Management
+ Network->>UE: Configuration (e.g., measurement, reporting)
+ UE->>Network: Management Request
+ Network->>UE: Management Instruction
+```
+
+Sequence diagram for Figure 7.2.1.1-2: Network decision, UE-initiated AI/ML management. The diagram shows a UE and a Network. The Network sends a 'Configuration (e.g., measurement, reporting)' to the UE. The UE's 'Management' block sends a 'Management Request' to the Network. The Network responds with a 'Management Instruction' to the UE.
+
+**Figure 7.2.1.1-2: Network decision, UE-initiated AI/ML management**
+
+The case where the LCM decision is taken by the network but where the request is initiated by the UE is depicted in Figure 7.2.1.1-2.
+
+- Note: The Management Request may be a result of model/functionality monitoring at the UE.
+- Note: In response to the Management Request, the network may send a Management Instruction to the UE.
+- Note: The Management Request may include information about the model or functionality.
+- Note: The network may accept or reject the Management Request from the UE.
+- Note: The Management Request may include information related to model/functionality performance metrics.
+- Note: The Management Instruction may include information about the model or functionality.
+
+##### **- Decision by the UE**
+
+- o **Event-triggered as configured by the network, UE's decision is reported to the network**
+
+
+
+```
+sequenceDiagram
+ participant UE
+ participant Network
+ Note left of UE: Management
+ Network->>UE: Configuration (e.g., measurement, conditions for event triggering)
+ UE->>Network: Management Decision Report
+```
+
+Sequence diagram for Figure 7.2.1.1-3: UE decision, event-triggered as configured by the network. The diagram shows a UE and a Network. The Network sends a 'Configuration (e.g., measurement, conditions for event triggering)' to the UE. The UE's 'Management' block sends a 'Management Decision Report' to the Network.
+
+**Figure 7.2.1.1-3: UE decision, event-triggered as configured by the network**
+
+The case where the LCM decision is taken by the UE according to prior network configuration is depicted in Figure 7.2.1.1-3.
+
+Note: Use case-specific events/conditions may be configured by the network for event-triggered AI/ML management at the UE.
+
+Note: UE may send a Management Decision Report to the network following event-triggered AI/ML management at the UE.
+
+Note: The Management Decision Report may include information about the model or functionality.
+
+- **UE-autonomous, UE's decision is reported to the network**
+
+
+
+```
+sequenceDiagram
+ participant Network
+ participant UE
+ Note right of UE: Management
+ Network->>UE: Configuration on decision reporting
+ Note left of Network: Management
+ UE->>Network: Management Decision Report
+```
+
+The diagram illustrates a sequence of interactions between a UE and a Network. The UE has a 'Management' block. The Network sends a 'Configuration on decision reporting' message to the UE. The UE then sends a 'Management Decision Report' message back to the Network.
+
+Sequence diagram showing UE autonomous decision reporting to the network.
+
+**Figure 7.2.1.1-4: UE autonomous, decision reported to the network**
+
+The case where the LCM decision can autonomously be taken by the UE is depicted in Figure 7.2.1.1-4.
+
+Note: The UE may be configured to send a Management Decision Report to the network upon performing a model/functionality Management Decision.
+
+- **UE-autonomous, UE's decision is not reported to the network**
+
+For the case where the LCM decision can autonomously be taken by the UE and where the decision is not reported to the network, the AI/ML management is transparent from a network perspective.
+
+#### 7.2.1.2 Model identification and meta information
+
+According to the functional framework in Figure 4.4-1, a model ID can be used within functions and for different data/information/instruction flows to identify an AI/ML model. For example, a model ID could eventually be associated to the selection/(de)activation/switching of a model or linked to the "Model Transfer/Delivery" information.
+
+RAN2 assumes that a model ID can be globally unique, e.g., allowing for proper model validation and model testing procedures.
+
+Note: How to ensure model ID uniqueness is out of RAN2 scope.
+
+Note: Details of model training, validation and testing are out of RAN2 scope.
+
+Additionally, to manage or control AI/ML models, some meta information about the models may be needed.
+
+Note: Details on the relationship between model IDs and meta information for purposes of model control and management can be addressed during a normative phase.
+
+#### 7.2.1.3 Data collection
+
+Data collection plays a crucial role in enabling the different use cases. Therefore, it is important to define the best approaches for collecting data to support UE-side and network-side model inference, monitoring, and training.
+
+Table 7.3.1.2-1 lists existing data collection mechanisms available in current RAN specifications for the UE to report measurements to another entity acting as termination point for this data. As highlighted in clause 4.2, the analysis/selection of the data collection frameworks should focus on the RRC CONNECTED state for both data generation and reporting. As such, the Table can provide useful insights into existing methods with respect to various categories identified as relevant for data collection method selection.
+
+**Table 7.3.1.2-1. Existing data collection methods identified.**
+
+| Involved network entity (termination point) | RRC state to generate data | Max payload size per reporting* | Contents to be collected | End-to-End report latency** | Report type | Security and Privacy |
+|------------------------------------------------|----------------------------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| <b>Method: Logged MDT</b> | | | | | | |
+| TCE/OAM (Data can be utilized by gNB) | IDLE / INACTIVE | <9kbyte | <ul style="list-style-type: none"> <li>- L3 cell/beam measurements</li> <li>- location information</li> <li>- sensor information</li> <li>- timing information</li> </ul> | 1) Procedure latency***:<br><ul style="list-style-type: none"> <li>- Latency to enter CONNECTED state</li> <li>- Latency to receive gNB request signalling (~20ms)</li> </ul> 2) Air interface signalling latency****:<br><ul style="list-style-type: none"> <li>- ~20ms (RRC)</li> </ul> 3) Other latency:<br><ul style="list-style-type: none"> <li>- Forwarding latency between gNB and TCE</li> </ul> | Upon gNB request after entering RRC_CONNECTED | AS security via RRC message<br><br>Privacy via user consent |
+| <b>Method: Immediate MDT</b> | | | | | | |
+| TCE/OAM (Data can be utilized by gNB) | CONNECTED | <9kbyte | <ul style="list-style-type: none"> <li>- L3 cell/beam measurements</li> <li>- location information</li> <li>- sensor information</li> </ul> | 1) Procedure latency:<br><ul style="list-style-type: none"> <li>- Report interval: <ul style="list-style-type: none"> <li>• 120ms~30min for periodic report</li> <li>• TTT for event triggered report</li> </ul> </li> </ul> 2) Air interface signalling latency:<br><ul style="list-style-type: none"> <li>- ~20ms (RRC)</li> </ul> 3) Other latency:<br><ul style="list-style-type: none"> <li>- Forwarding latency between gNB and TCE</li> </ul> | <ul style="list-style-type: none"> <li>- Event triggered</li> <li>- Periodic reporting</li> </ul> | AS security via RRC message<br><br>Privacy via user consent |
+| <b>Method: L3 measurements</b> | | | | | | |
+| gNB | CONNECTED | <9kbyte | L3 cell/beam measurements | 1) Procedure latency:<br><ul style="list-style-type: none"> <li>- Report interval: <ul style="list-style-type: none"> <li>• 120ms~30min for periodic report</li> <li>• TTT for event triggered report</li> </ul> </li> </ul> 2) Air interface signalling latency:<br><ul style="list-style-type: none"> <li>- 20ms (RRC)</li> </ul> | <ul style="list-style-type: none"> <li>- Event triggered report</li> <li>- Periodic reporting</li> </ul> | AS security via RRC message |
+| <b>Method: L1 measurement (CSI reporting)</b> | | | | | | |
+| gNB | CONNECTED | <1706bit in PUCCH<br><br><3840bit in PUSCH | L1 CSI measurement | 1) Procedure latency:<br><ul style="list-style-type: none"> <li>- Report interval: <ul style="list-style-type: none"> <li>• 4-320 slot for periodic and semi-persistent report</li> <li>• 0-32 slot after reception of DCI for aperiodic report</li> </ul> </li> </ul> 2) Air interface signalling latency:<br><ul style="list-style-type: none"> <li>- 1 TTI (PUCCH)</li> </ul> | <ul style="list-style-type: none"> <li>- Aperiodic report</li> <li>- Semi-persistent report</li> <li>- Periodic report</li> </ul> | No AS security |
+| <b>Method: UE Assistance Information (UAI)</b> | | | | | | |
+
+| | | | | | | |
+|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|-----------------------------|
+| gNB | CONNECTED | <9kbyte | Assistance information to show UE preference | 1) Procedure latency:<br>- Upon generation of UE's preference<br>2) Air interface signalling latency:<br>- ~20ms (RRc) | Up to UE implementation when to report | AS security via RRC message |
+| <b>Method: Early measurements</b> | | | | | | |
+| gNB | IDLE / INACTIVE | <9kbyte | L3 cell/beam measurements | 1) Procedure latency:<br>- Latency to enter CONNECTED state<br>- Latency to receive gNB request signalling (~20ms)<br>2) Air interface signalling latency:<br>- ~20ms (RRc) | Upon gNB request after entering RRC_CONNECTED | AS security via RRC message |
+| <b>Method: LPP</b> | | | | | | |
+| LMF | CONNECTED | <9kbyte | Location information | 1) Procedure latency:<br>- Latency to get upper layer trigger (for UE triggered)<br>- Or latency to receive network request message (~20ms)<br>2) Air interface signalling latency:<br>- ~20ms (RRc)<br>3) Other latency:<br>- Forwarding latency between gNB and LMF | - UE-triggered<br>- Network-triggered | AS security via RRC message |
+| *: | The payload size doesn't consider signalling overhead. | | | | | |
+| **: | The End-to-End report latency is the latency from availability of the measurement report at the UE side to the availability of the measurement report at the terminated network entity. The time to generate data or perform measurements depends on RAN1/RAN4 specification. | | | | | |
+| ***: | Procedure latency is the latency caused by procedures, including procedure to ready for reporting (e.g., entering CONNECTED state, report interval). | | | | | |
+| ****: | Air interface signalling latency is the latency to transmit one report, e.g., RRC signalling latency or PUCCH signalling latency. | | | | | |
+
+##### 7.2.1.3.1 Considerations for network-side data collection
+
+A set of general data collection principles is expected to be considered for network-side model training. These include:
+
+- UE to support data logging,
+- UE to report the collected data periodically, event-based, and on-demand,
+- The UE memory, processing power, energy consumption, signalling overhead should be considered.
+
+Note: The above principles can be revised depending on RAN1 requirements.
+
+Furthermore, and regarding the use cases in this study, the following is considered.
+
+For CSI and beam management use cases, the training of network-side models can consider both gNB and OAM-centric data collection mechanisms. The gNB-centric data collection implies that the gNB can configure the UE to initiate/terminate the data collection procedure. The potential impact of L3 signalling for the reporting of collected data should be assessed.
+
+On the other hand, OAM-centric data collection implies that the OAM provides the configuration (via the gNB) needed for the UE to initiate/terminate the data collection procedure. MDT framework can be considered to achieve this. The potential impact on MDT for RRC\_CONNECTED state should be assessed.
+
+For positioning use cases, when considering LMF-side inference, it is assumed that the LPP protocol should be applied to the data collected by UE and terminated at LMF, while the NRPPa protocol should be applied to the data collected by gNB and terminated at LMF. While for LMF-side performance monitoring, it is assumed that the LPP protocol should
+
+be applied to the data collected by UE and terminated at LMF, while the NRPPa protocol should be applied to the data collected by gNB and terminated at LMF.
+
+Note: For gNB- and OAM-centric data collection, there may be a need to consult with RAN3 and SA5 whether/how OAM is to be involved.
+
+Note: For possible impacts due to positioning use cases, there may be a need to consult with RAN3 whether/how NRPPa is to be involved.
+
+##### 7.2.1.3.2 Data collection for UE-side model training
+
+The following proposals were discussed in RAN2:
+
+1. UE collects and directly transfers training data to the Over-The-Top (OTT) server;
+ - 1a) OTT (TRansparent)
+ - 1b) OTT (non-TRansparent)
+2. UE collects training data and transfers it to Core Network. Core Network transfers the training data to the OTT server.
+3. UE collects training data and transfers it to OAM. OAM transfers the needed data to the OTT server.
+
+RAN2 did not study or analyse these proposals and did not agree to requirements or recommendations.
+
+#### 7.2.1.4 Model transfer/delivery
+
+Whether there is a need to consider standardised solutions for transferring/delivering AI/ML model(s) is unclear from the outcome of the present study. Nonetheless, to support AI/ML model transfer/delivery, the following solutions are considered:
+
+- Solution 1a: gNB can transfer/deliver AI/ML model(s) to UE via RRC signalling.
+- Solution 2a: Core Network (except LMF) can transfer/deliver AI/ML model(s) to UE via NAS signalling.
+- Solution 3a: LMF can transfer/deliver AI/ML model(s) to UE via LPP signalling.
+- Solution 1b: gNB can transfer/deliver AI/ML model(s) to UE via UP data.
+- Solution 2b: Core Network (except LMF) can transfer/deliver AI/ML model(s) to UE via User Plane (UP) data.
+- Solution 3b: LMF can transfer/deliver AI/ML model(s) to UE via UP data.
+- Solution 4a: OTT server can transfer/deliver AI/ML model(s) to UE (e.g., transparent to 3GPP).
+- Solution 4b: OAM can transfer/deliver AI/ML model(s) to UE.
+
+Note: The relationships between model transfer/delivery solutions and use cases can be derived from what is captured in clauses 7.3.2, 7.3.3, and 7.3.4.
+
+The following areas are considered to evaluate the different model transfer/delivery solutions:
+
+- A1: Large, no upper limit model/model parameter size,
+- A2: Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs),
+- A3: Network controllability on model transfer/delivery (e.g., management decision at gNB),
+- A4: Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB).
+
+For every model transfer/delivery solution, each of the above areas is analysed, focusing on the current status and gaps, and the potential impacts on RAN specification. The analysis is shown in the Tables below.
+
+**Table 7.3.1.4-1 Analysis of current status and gaps, and potential RAN specification impact for Solution 1a**
+
+| Discussion Area | Current status and Gaps | Potential RAN specification impact |
+|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A1. Large, no upper limit model/model parameter size | Model size >45kBytes is not supported based on existing number of RRC segments | Extension of the number of RRC segments is required to support models larger than 45kBytes |
+| A2. Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs) | Transmission is restarted upon mobility | <ul style="list-style-type: none"> <li>- Requires service continuity support for SRBs with segmentations.</li> <li>- Xn/NGAP enhancement(s) for model transfer/delivery continuity</li> </ul> |
+| A3. Network controllability on model transfer/delivery and management at gNB | Management and interaction between UE and gNB is not supported | Requires management and interaction between UE and gNB (e.g., model identification, model transfer completion indication, etc.) when model management at gNB |
+| A4. Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB) | Procedure latency depends on model size and SRB priority | Impact on SRB in DL, e.g., a new SRB with configurable priority, etc. |
+
+**Table 7.3.1.4-2 Analysis of current status and gaps, and potential RAN specification impact for Solutions 2a and 3a**
+
+| Discussion Area | Current status and Gaps | Potential RAN specification impact |
+|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A1. Large, no upper limit model/model parameter size | <ul style="list-style-type: none"> <li>- Model size >45kBytes is not supported based on existing number of RRC segments</li> <li>- Core Network supports NAS signalling segmentation</li> <li>- LMF supports LPP signalling segmentation</li> </ul> | If NAS/LMF does not do segmentation for model transfer/delivery, it may need RRC segmentation, and extension of the number of RRC segments is required to support models larger than 45kBytes |
+| A2. Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs) | Supported with limitation: <ul style="list-style-type: none"> <li>- For Solution 2a, support within AMF coverage area based on NAS signalling segmentation</li> <li>- For Solution 3a, support within LMF coverage area based on LPP signalling segmentation</li> </ul> | Note: Supporting service continuity across AMF/LMF is out of RAN scope and needs coordination with Core Network groups |
+| A3. Network controllability on model transfer/delivery and management at gNB | <ul style="list-style-type: none"> <li>- For Solution 2a, gNB cannot perform management directly, considering model transfer is transparent to gNB</li> <li>- Management and interaction between UE and gNB is not supported</li> </ul> | <ul style="list-style-type: none"> <li>- Requires management and model transfer interaction between Core Network/LMF and gNB, e.g., via NAS signalling or NRPPa signalling when model management at gNB</li> <li>- Requires management and interaction between UE and gNB (e.g., model identification, model transfer completion indication, etc.) when model management at gNB</li> </ul> |
+| A4. Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB) | Procedure latency depends on model size and SRB priority; other latency includes forwarding NAS message latency from Core Network to gNB | Impact on SRB in DL, e.g., a new SRB with configurable priority, etc. |
+
+Note: NAS and LMF upper limits and potential impacts to NAS and LPP specifications have not been studied and feasibility on filling gaps is unknown.
+
+**Table 7.3.1.4-3 Analysis of current status and gaps, and potential RAN specification impact for Solutions 1b**
+
+| Discussion Area | Current status and Gaps | Potential RAN specification impact |
+|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A1. Large, no upper limit model/model parameter size | <ul style="list-style-type: none"> <li>- No model size limitation</li> <li>- PDU session termination at gNB is not supported</li> </ul> | Requires PDU session termination at gNB if needed |
+| A2. Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs) | Model transfer continuity if PDU session terminated at gNB is not studied | <ul style="list-style-type: none"> <li>- Identify a solution to support service continuity support between gNBs when PDU session is terminated at gNB if needed</li> <li>- Xn/NGAP enhancement(s) for model transfer/delivery continuity</li> </ul> |
+| A3. Network controllability on model transfer/delivery and management at gNB | Management and interaction between UE and gNB appear to be feasible but not supported | Requires management and interaction between UE and gNB (e.g., model identification, model transfer completion indication, etc.) when model management at gNB |
+| A4. Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB) | <ul style="list-style-type: none"> <li>- Procedure latency depends on model size, QoS requirement and DRB priority</li> <li>- QoS management at gNB if PDU session is terminated at gNB is not supported</li> </ul> | Identify a solution to support QoS management at gNB for model transfer when PDU session is terminated at gNB if needed |
+
+**Table 7.3.1.4-4 Analysis of current status and gaps, and potential RAN specification impact for Solutions 2b and 3b**
+
+| Discussion Area | Current status and Gaps | Potential RAN specification impact |
+|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A1. Large, no upper limit model/model parameter size | No model size limitation | <ul style="list-style-type: none"> <li>- No RAN impact</li> <li>- Note: The detail procedure of model transfer from Core Network/LMF to UE is out of RAN scope</li> </ul> |
+| A2. Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs) | <ul style="list-style-type: none"> <li>- For Solution 2b, supported</li> <li>- For Solution 3b, depends on Rel-18 CT1 solution LPP message over a user plane connection between UE and LMF</li> </ul> | Note: supporting service continuity across LMF is out of RAN scope |
+| A3. Network controllability on model transfer/delivery and management at gNB | gNB cannot perform model management directly | Requires management and model transfer interaction between Core Network/LMF and gNB when model management at gNB |
+| | Management and interaction between UE and gNB is not supported | Requires management and interaction between UE and gNB (e.g., model identification, model transfer completion, etc.) when model management at gNB |
+| A4. Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB) | <ul style="list-style-type: none"> <li>- Procedure latency depends on model size, QoS requirement and DRB priority</li> <li>- Other latency includes forwarding data from Core Network to gNB</li> </ul> | Note: The detail QoS requirement on Core Network for model transfer/delivery is out of RAN scope |
+
+**Table 7.3.1.4-5 Analysis of current status and gaps, and potential RAN specification impact for Solutions 4a**
+
+| Discussion Area | Current status and Gaps | Potential RAN specification impact |
+|------------------------------------------------------|--------------------------|------------------------------------|
+| A1. Large, no upper limit model/model parameter size | No model size limitation | No RAN impact |
+
+| | | |
+|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A2. Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs) | <ul style="list-style-type: none"> <li>- If model transfer/delivery from OTT server via Core Network, supported</li> <li>- If model transfer/delivery from OTT server via LMF, depends on Rel-18 CT1 solution LPP message over a User Plane connection between UE and LMF</li> </ul> | Note: supporting service continuity across LMF is out of RAN scope |
+| A3. Network controllability on model transfer/delivery and management at gNB | Model transfer/delivery is transparent to RAN | <ul style="list-style-type: none"> <li>- Requires management and model transfer interaction between OTT server and gNB when model management at gNB</li> <li>- Note: it is unclear whether this is within RAN scope</li> <li>- Requires interaction between UE and gNB for the network controllability of the model transfer/delivery (e.g., model identification, model transfer completion, etc.) if management is in gNB</li> </ul> |
+| A4. Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB) | <ul style="list-style-type: none"> <li>- Procedure latency depends on model size, QoS requirement and DRB priority</li> <li>- Other latency includes forwarding data from OTT server to gNB</li> </ul> | Note: The detail QoS requirement for model transfer/delivery of solution 4a is out of RAN scope |
+
+**Table 7.3.1.4-6 Analysis of current status and gaps, and potential RAN specification impact for Solutions 4b**
+
+| Discussion Area | Current status and Gaps | Potential RAN specification impact (Note: whether and how to support model transfer/delivery from OAM to gNB and OAM to UE directly is out of RAN scope) |
+|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A1. Large, no upper limit model/model parameter size | <ul style="list-style-type: none"> <li>- Over Control Plane (CP) signalling: model size >45kBytes is not supported based on existing number of RRC segments if OAM does not do segmentation for model transfer/delivery</li> <li>- Over, e.g., IP: no model size limitation, but direct connection between OAM and UE is not supported</li> </ul> | <ul style="list-style-type: none"> <li>- Over Control Plane (CP) signalling: If OAM does not do segmentation for model transfer/delivery, it may need RRC segmentation, and extend RRC segment number if model size larger than 45kBytes</li> <li>- Over, e.g., IP: NOTE: whether and how to support direct connection between OAM and UE is out of RAN scope</li> </ul> |
+| A2. Model transfer/delivery continuity (i.e., resume transmission of model (segments) across gNBs) | Support within OAM coverage | |
+| A3. Network controllability on model transfer/delivery and management at gNB | gNB cannot perform model management directly | Note: support management and model transfer interaction between OAM and gNB is out of RAN scope |
+| A4. Model transfer/delivery QoS (for DRB) (including latency, etc.) and priority (for SRB) | <ul style="list-style-type: none"> <li>- Over Control Plane (CP) signalling: <ol style="list-style-type: none"> <li>1) Procedure latency depends on model size and SRB priority</li> <li>2) other latency includes forwarding data from OAM to gNB</li> </ol> </li> </ul> | <ul style="list-style-type: none"> <li>- Over Control Plane (CP) signalling: <p>Note: The detail QoS requirement for model transfer/delivery of solution 4b is out of RAN scope</p> </li> <li>- Over, e.g., IP: <p>Note: whether and how to support latency, QoS</p> </li> </ul> |
+
+| | | |
+|--|-------------------------------------------------------------------------|----------------------------------------------------|
+| | - Over, e.g., IP: direct connection between OAM and UE is not supported | requirement between OAM and UE is out of RAN scope |
+|--|-------------------------------------------------------------------------|----------------------------------------------------|
+
+Note: For Solution 4b, RAN2 discussed the following two solutions but did not study or analyse their feasibility:
+
+- OAM can transfer/deliver AI/ML models to UE via OAM→RAN→UE, where Control Plane (CP) signalling is used for RAN→UE.
+- OAM can transfer/deliver AI/ML models to UE via OAM→UE, e.g., via IP tunnel.
+
+A reactive and a proactive approach for initiating a model transfer/delivery can be considered in a normative phase. For the reactive approach, an AI/ML model is transferred/delivered (i.e., downloaded) to the UE when needed. This could typically happen due to changes in scenarios, configurations, sites, etc. While for the proactive model transfer/delivery approach, an AI/ML model is pre-download to the UE, and a model switch can typically be performed due to changes in scenarios, configurations, sites, etc.
+
+#### 7.2.1.5 UE capability reporting
+
+The legacy UE capability framework serves as the baseline to report UE's supported AI/ML-enabled Feature/FG. Therefore, for CSI and beam management use cases, this information is indicated in UE AS capability in RRC (e.g., *UECapabilityEnquiry/UECapabilityInformation*). While for positioning use cases, it is indicated by the positioning capability as defined in LPP.
+
+Further discussions concerning UE capability details (e.g., granularity of Feature/FG, content, structure of the related UE capabilities, etc.) can be carried during a normative phase.
+
+#### 7.2.1.6 Reporting applicability-related information
+
+AI/ML models for a given use case may be tailored towards and applicable to specific scenarios, locations, configuration, deployments, among other factors. In this regard, it is acknowledged that AI/ML models may undergo updates, such as model changes, as an inherent part of their development. Therefore, to ensure efficient network control and management, especially associated to what concerns the UE-side, UEs might have the ability to indicate relevant information about their supported AI/ML models and concerning AI/ML functionalities to the network. This can allow the network to perform decisions regarding, e.g., the (de)activation, or switching of AI/ML functionalities and AI/ML models.
+
+The previously mentioned information could in principle be understood as "applicability-related information" in which the UE could, for example, report to the network conditions under which a model/functionality is applicable/suitable, or whether model(s)/functionality(ies) are (non)applicable under the current context. Note, however, that the existing UE capability reporting framework cannot be used for such purposes.
+
+Note: How and whether there is a need to enable UEs to report applicability-related information can be further discussed and defined in a normative phase. Mechanisms such as UE Assistance Information can eventually be used as example.
+
+Two UE reporting types are identified to convey this additional information:
+
+- "*reactive*" reporting, and
+- "*proactive*" reporting.
+
+A reactive reporting would involve the UE to provide information to the network upon receiving an action from it.
+
+While a proactive reporting would involve the UE to provide information to the network without necessarily receiving an action from it. For example, the UE might proactively inform the RAN of updates/changes to its supported model(s) or functionality(ies).
+
+Note: Whether necessary signalling from network is needed for proactive UE reporting can be discussed in a normative phase.
+
+Note: Whether there is a need for the network to report to the UE applicability-related information of AI/ML models and/or AI/ML functionalities can be discussed in a normative phase.
+
+### 7.2.2 CSI feedback enhancement
+
+The following set of objectives have been identified for the two-sided CSI compression use case. Firstly, to ensure that the UE part and network part of the models are configured and applied according to their applicable scenarios and configuration. Secondly, to ensure that models match properly, ensuring that the CSI generation part used at the UE corresponds to the CSI reconstruction part employed at the gNB. Thirdly, to allow for seamless operation, requiring the simultaneous (de)activation and switching of the two-sided model.
+
+Regarding the last point above, for the two-sided model CSI compression use cases, the selection, (de)activation, switching, and fallback of AI/ML models or AI/ML functionalities can be initiated by either the UE or the gNB. For which it is important to distinguish the various cases and understand their applicability to UE-side versus network-side models.
+
+For data collection, model transfer/delivery, and function-to-entity mapping analysis, various scenarios unfold for both the two-sided CSI compression use case, as well as for the UE-side CSI prediction use case, when the data generation and termination entities differ. For instance, for:
+
+- Model Training:
+ - For the two-sided CSI compression use case, training data can be generated by either the UE or the gNB, depending on specific requirements, while the termination point for training data may include the gNB, OAM, Over-The-Top (OTT) server or UE.
+ - Note: RAN2 identified the case in which Core Network may be used for model training. However, no study was conducted since this is beyond the scope of this Working Group.
+ - For the UE-side CSI prediction use case, training data can be generated by the UE, while the termination point for training data may include the UE or a UE-side OTT server.
+ - Note: RAN2 identified the cases in which OAM or Core Network may be used for UE-side model training. However, no study was conducted since this is beyond the scope of this Working Group.
+ - Note: RAN2 identified the case in which gNB may be used for UE-side model training. However, no conclusion was reached, as this depends on the RAN1 progress.
+- Inference:
+ - For the two-side CSI compression use case:
+ - For network part of two-sided model inference, the UE can generate the necessary input data while the termination point for this input data lies within the gNB, where the inference process is performed.
+ - For UE part of two-sided model inference, input data is internally available at UE, where the inference process is performed.
+ - For the UE-side CSI prediction use case:
+ - For UE-side model inference, input data is internally available at UE, where the inference process is performed.
+- Management:
+ - For the two-sided CSI compression use case, the model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) is performed by the gNB.
+ - Note: RAN2 identified the case in which the control is performed by the UE. However, no conclusion was reached, as this depends on the RAN1 progress.
+ - For the UE-side CSI prediction use case:
+ - The model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) may be performed by the UE when the monitoring resides within the UE.
+ - The model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) may be performed by the gNB when the monitoring resides within the gNB or UE.
+
+- Monitoring:
+ - The UE monitors the performance of its UE-side model.
+ - For monitoring at the network side of UE-side model, the UE can generate, if needed, calculated performance metrics or data required for performance metric calculation, while the termination point for these is the gNB.
+
+### 7.2.3 Beam management
+
+For beam management, the selection, (de)activation, switching, and fallback of models or functionalities can also be initiated by either the UE or the gNB. For which it is important to distinguish the various cases and understand their applicability to UE-side versus network-side models.
+
+For data collection, model transfer/delivery, and function-to-entity mapping analysis, various scenarios unfold when the data generation and termination entities differ. For instance, for:
+
+- Model Training:
+ - For UE-side models, training data can be generated by the UE, while the termination point for training data may include the UE or a UE-side OTT server.
+ - Note: RAN2 identified the cases in which OAM or Core Network may be used for UE-side model training. However, no study was conducted since this is beyond the scope of this Working Group.
+ - Note: RAN2 identified the case in which gNB may be used for UE-side model training. However, no conclusion was reached, as this depends on the RAN1 progress.
+ - For gNB-side models, training data can be generated by the gNB or UE, while the termination point for training data may include the gNB, or OAM.
+ - Note: RAN2 identified the case in which OTT server and Core Network may be used for gNB-side model training. However, no study was conducted since this is beyond the scope of this Working Group.
+- Inference:
+ - For UE-side model inference, input data is internally available at UE, where the inference process is performed.
+ - For network-side model inference, the UE can generate the necessary input data while the termination point for this input data lies within the gNB, where the inference process is performed.
+- Management:
+ - For UE-side model, the model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) may be performed by the UE when the monitoring resides within the UE.
+ - For UE-side model, the model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) may be performed by the gNB when the monitoring resides within the gNB or UE.
+ - Monitoring:
+ - The UE monitors the performance of its UE-side model.
+ - For monitoring at the network side of UE-side model, the UE can generate, if needed, calculated performance metrics or data required for performance metric calculation, while the termination point for these is the gNB.
+ - For network-side model, the monitoring resides within the gNB.
+
+### 7.2.4 Positioning accuracy enhancements
+
+For the positioning use cases, the selection, (de)activation, switching, and fallback of models or functionalities can be initiated by either the UE, the gNB, or the LMF. For which it is important to distinguish the various cases and understand their applicability to UE-side versus network-side models.
+
+For data collection, model transfer/delivery, and function-to-entity mapping analysis, various scenarios unfold when the data generation and termination entities differ. For instance, for:
+
+- Model Training:
+ - For UE-side models, training data can be generated by the UE, while the termination point for training data may include the UE or a UE-side OTT server.
+ - Note: RAN2 identified the cases in which OAM or Core Network may be used for UE-side model training. However, no study was conducted since this is beyond the scope of this Working Group.
+ - Note: RAN2 identified the case in which LMF may be used for UE-side model training. However, no conclusion was reached, as this depends on the RAN1 progress.
+ - For gNB-side model, training data can be generated by the gNB, while the termination point for training data may include the gNB, or OAM.
+ - Note: RAN2 identified the case in which LMF may be used for gNB-side model training. However, no conclusion was reached, as this depends on the RAN1 progress.
+ - For LMF-side model, the LMF is the termination point for training data.
+- Inference:
+ - For UE-side model inference, input data is internally available at UE, where the inference process is performed.
+ - For gNB-side model inference, input data is internally available at gNB. For this case, the UE can also generate the necessary input data while the termination point for this input data lies within the gNB where the inference process is performed.
+ - For LMF-side model inference, the UE or gNB can generate the necessary input data while the termination point for this input data lies within the LMF where the inference process is performed.
+- Management:
+ - For UE-side model, the model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) may be performed by the UE when the monitoring resides within the UE.
+ - For gNB-side model, the model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) is performed by the gNB.
+ - The model/functionality control (e.g., selection, (de)activation, switching, fallback, etc.) may be performed by the LMF when the monitoring resides within the LMF or UE.
+ - Monitoring:
+ - The UE monitors the performance of its UE-side model.
+ - For monitoring at the gNB side, and if needed, calculated performance metrics or data required for performance metric calculation, can at least be generated by the gNB.
+ - For monitoring at the LMF side, the gNB or UE can generate, if needed, calculated performance metrics or data required for performance metric calculation, while the termination points for these metrics is the LMF.
+
+## 7.3 Interoperability and testability aspects
+
+### 7.3.1 Introduction
+
+In this section, the study of requirements and testing frameworks to validate AI/ML based performance enhancements and ensuring that UE and gNB with AI/ML meet or exceed the existing minimum requirements, if applicable, are documented.
+
+The need and implications for AI/ML processing capabilities definition is considered.
+
+### 7.3.2 Common framework
+
+#### 7.3.2.1 General
+
+The general requirements and testing frameworks for AI/ML based performance enhancements mainly focus on
+
+- how to define requirements and tests for inference
+- evaluate feasibility and necessity of requirements/tests for LCM
+- requirements for data collection (in particular for training) could/need be defined
+
+Requirements/tests for training will not be studied unless training procedures are defined. The design of test should ensure performance is guaranteed and avoid that a UE can pass the test but perform poorly in the field.
+
+For testing goals, Option 1 and/or Option 2 below will be selected depending on the test
+
+- Option 1: The testing goal is to verify whether a specific AI/ML model (if model identification is possible)/functionality can be conducted in a proper way.
+ - FFS how to define the specific AI/ML model (e.g., a model captured in RAN4 spec as baseline)
+ - FFS how to define that the model is properly conducted (e.g., by defining AI/ML dedicated performance/core requirements associated with model outputs)
+- Option 2: The testing goal is to verify whether the minimum performance gain of AI/ML model (if model identification is possible)/functionality/feature can be achieved for a static scenario/configuration.
+ - FFS how to define a static scenario/configuration (e.g., by defining a related testing dataset based on channel models in TR 38.901)
+ - FFS whether and how to define non-static specific scenarios/configurations
+
+#### 7.3.2.2 Principles on the definition of requirements
+
+For the definition of AI/ML requirements, the following cases related to legacy performance should be considered
+
+- For the cases with the existing legacy performance
+ - Take the legacy performance as baseline for existing use cases/procedures/functionalities /measurements that are to be enhanced by AI/ML based methods
+ - Further study may be needed on what is baseline performance in conditions different to the requirement condition but within the expected range of operation.
+ - New or enhanced performance requirements/tests could be considered for existing use cases/procedures/functionalities/measurements that are to be enhanced by AI/ML based methods
+- For the cases without the existing legacy performance
+ - New performance requirements/tests could be considered for the use cases/procedures/functionalities/measurements that are carried out or are to be enhanced by AI/ML based methods
+
+The following procedure can be considered for defining core requirements:
+
+- Performance monitoring procedure, including performance evaluation and decision-making procedure for AI/ML functionalities/models
+- Functionality/Model management procedure, including functionality/model selection/activation/deactivation, and functionality/model switching/fallback/transfer/delivery/update
+- Latency/interruption requirement for above procedures
+
+The following LCM related requirements can be considered:
+
+- Model/Functionality select/switch/activate/deactivate/fallback
+- Model/Functionality monitoring
+- On whether requirements for data collection (in particular for training) could/need be defined:
+ - Data collection requirements would only be defined if data collection procedure is defined in 3GPP specifications.
+- On requirements for model transfer/update:
+ - Requirements would only be defined if model transfer/update would be defined in 3GPP specifications.
+
+The legacy framework for RRC/MAC-CE/DCI based core requirements (e.g., define delay requirements based on multiple delay components) can be used as the baseline for LCM procedures if the LCM related requirements are agreed to be introduced. If new procedures which legacy framework is not applicable to are introduced, additional core requirement framework can be discussed.
+
+LCM related tests should consider how the framework can address the possibility of updates/activation/deactivation/switching to the functionalities/models after the deployment of the devices in the field.
+
+#### 7.3.2.3 Reference block diagrams for testing
+
+Reference block diagrams provide test modules/functionalities of TE/DUT and testing framework for different use cases. Both reference block diagrams for 1-sided model and 2-sided model are studied.
+
+##### 7.3.2.3.1 Reference block diagram for 1-sided model
+
+Figure 7.3.2.3-1 provides the reference block diagram for 1-sided model. LCM in the figure includes functionality and/or model ID based LCM. The link between TE and DUT are physical and not logical. The logical link will depend on the functionality being tested. The scope of the figure includes both performance and potentially LCM tests. Offline training is assumed and some blocks may not be used in some of the tests. LCM may not be tested depending on the purpose of the test.
+
+
+
+This block diagram illustrates the reference architecture for a 1-sided model. It is divided into two main sections: the Test Equipment (TE) and the Device Under Test (DUT). The TE section contains a 'Signal generator' (red box), an 'AI/ML functions' block (white box) which includes an 'LCM' (green box), and a 'Verification' block (yellow box). All three are connected to a 'Test configuration/controller' (orange box). The DUT section contains an 'LCM' (green box) and an 'inference' block (blue box), which are bidirectionally connected. A physical link (solid line) connects the 'Test configuration/controller' in the TE to the 'LCM' in the DUT. A logical link (dashed line) connects the 'Verification' block in the TE to the 'inference' block in the DUT.
+
+Reference block diagram for 1-sided model
+
+Figure 7.3.2.3-1: Reference block diagram for 1-sided model
+
+##### 7.3.2.3.2 Reference block diagram for 2-sided model
+
+Figure 7.3.2.3-2 provides the reference block diagram for 2-sided model. LCM in the figure includes functionality and/or model ID based LCM. The link between TE and DUT are physical and not logical. The logical link will depend on the functionality being tested. The scope of the figure includes both performance and potentially LCM tests. Offline training is assumed and some blocks may not be used in some of the tests. LCM may not be tested depending on the purpose of the test.
+
+
+
+This block diagram illustrates the reference architecture for a 2-sided model. It is divided into two main sections: the Test Equipment (TE) and the Device Under Test (DUT). The TE section contains a 'Signal generator' (red box), an 'AI/ML functions' block (white box) which includes an 'inference' block (blue box) and an 'LCM' (green box), and a 'Verification' block (yellow box). All three are connected to a 'Test configuration/controller' (orange box). The DUT section contains an 'LCM' (green box) and an 'inference' block (blue box), which are bidirectionally connected. A physical link (solid line) connects the 'Test configuration/controller' in the TE to the 'LCM' in the DUT. A logical link (dashed line) connects the 'Verification' block in the TE to the 'inference' block in the DUT. Additionally, there is a bidirectional logical link between the 'LCM' in the TE and the 'LCM' in the DUT.
+
+Reference block diagram for 2-sided model
+
+Figure 7.3.2.3-2: Reference block diagram for 2-sided model
+
+#### 7.3.2.3 Test encoder/decoder for 2-sided model
+
+(NOTE: At the current stage the framework in this session applies to CSI compression case.)
+
+In order to determine the test encoder/decoder, the following issues are considered:
+
+- Common assumptions for proposals of the test decoder / encoder (and the paired encoder/ decoder) for tester
+- The need for and potential definition and derivation procedure of intermediate KPI for decoder evaluation and selection
+- Data collection/generation for decoder evaluation, and the common assumptions/environment needed for data collection/generation
+- How to minimize the impact of possible variations/differences in the test decoder/ test encoder design/implementation on UE/ gNB performance verification
+- The impact of test decoder/ encoder for testing complexity to UE/gNB performance verification, and the advantage/disadvantage analysis of high/low complexity decoders.
+
+The test decoder/encoder design should take into account complexity limitations based on e.g., feasibility of TE implementation and complexity levels considered feasible by network vendors/UE vendors for decoder/encoder deployment.
+
+The choice of test decoder/encoder should aim as much as possible to avoid limiting the implementation choices, including e.g. complexity, back-bone model etc, of UE/gNB encoders/decoders operating in the field (this principle may not be fully achievable in practice).
+
+Specification on the test may include some high-level parameters for the test decoder/encoder (e.g. parameters related to processing complexity, model structure, etc).
+
+Following the above principles, the considered options of test decoder are listed below
+
+- Option 1: DUT provides the decoder
+- Option 2: Infra vendor provides the decoder
+- Option 3: Full decoder specification in standard
+- Option 4: TE vendor provides the decoder
+
+Option 3 target is that a single decoder defined in the specifications for at least a single test for any DUTs.
+
+For option 4, the following aspects should be considered
+
+- TE vendor should be able to develop the decoder based on the specifications
+- Test repeatability should be ensured (variation among TE vendor implementations should be bound)
+- Other vendors should also be able to develop such a decoder and which can deliver similar performance
+- Interoperability should be ensured based on the parameters that need to be specified
+ - Parameters that need to be specified are FFS
+- Candidate parameters/conditions that may be considered for defining test decoder include
+ - Training data set for TE decoder training
+ - Model structure (Activation function is included in the model structure)
+ - Performance parameters for the TE decoder (e.g. cosine similarity, loss function, etc)
+ - Maximum FLOPs allowed for the test decoder
+ - Maximum number/size of model parameters
+ - Compression ratio of decoder (output size/input size)
+
+- Quantization level
+- Other parameters are not precluded and to be further discussed.
+- Note: Feasibility of definition of parameters needs further investigated.
+
+Option 4 target is that a single decoder implemented by each TE vendor will be enough for at least a single test for any DUTs. TE vendor should be able to implement the test decoder for Option 4 without any involvement from another party. If this is found infeasible, another option in which TE vendors need to collaborate with DUT/infra vendors to implement the decoder could be considered.
+
+Further clarifications and analysis of the four options of test decoder are included in Table 7.3.2.3-1. It is assumed that for Option 4 the TE vendors can implement the decoder just based on the specifications (no other party involved). The table would need to be revised if collaboration between TE vendor and DUT/infra vendor is needed.
+
+**Table 7.3.2.3-1: Comparison of the four options of test decoder**
+
+| | Option 1 | Option 2 | Option 3 | Option 4 |
+|---------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| <b>Clarification of options</b> | | | | |
+| Source of the test decoder | DUT vendor | Decoder vendor (infra vendor in case of testing UEs) | RAN4 specifications | TE vendor, decoder developed based on RAN4 specifications |
+| Source of decoder training data | Up to DUT vendors (no need to be specified) | Up to decoder implementer (infra vendor) | Not needed, decoder fully specified (used as part of the RAN4 procedure to specify the decoder) | FFS<br>Could be specified depending on how Option 4 will be defined |
+| DUT vendor knowledge of the test decoder | Full knowledge | No or partial or enough or full knowledge based on alignment with infra vendors or specifications | Full knowledge based on the specifications | Partial knowledge – based on RAN4 specification |
+| Supported training collaboration type between DUT and decoder provider (source of training data should be consistent with the collaboration type) | | | | |
+| Test decoder performance verification procedure at TE | Need to ensure that decoder performance is not degraded (as intended by the decoder provider) on the TE | Need to ensure that decoder performance is not degraded (as intended by the decoder provider) on the TE<br><br>Need to ensure that decoder performance is good enough to enable a DUT that meets the minimum requirements to pass the test | Not needed as long as the standardized model implementation can be similar enough between TE vendors | Not needed as long as the model implementation can be similar enough between TE vendors |
+| Feasibility of test decoder verification procedure | FFS | FFS | FFS | FFS |
+| <b>Pros/Cons analysis</b> | | | | |
+| Reflection on the real deployment (likelihood that test decoder would be used) | | | | |
+| TE requirements to deploy the decoder (e.g., training, complexity, interoperability) | Higher than Option 3/4 in terms of that maybe more than one decoder is | Higher than Option 3/4 in terms of that maybe more than one decoder is implemented by TE | Lower complexity than Option 1/2 in terms of that only one decoder is implemented by TE | Lower complexity than Option 1/2 in terms of that only one decoder is implemented by TE |
+
+| | | | | |
+|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| | implemented by TE<br><br>Lower than Option 3/4 in terms of that no training at TE is required | Lower than Option 3/4 in terms of that no training at TE is required | Lower than Option 4 in terms of that no training at TE is required | Higher than Option 3 in terms of that training at TE is required<br><br>Note: How to ensure compatibility/ interoperability between TE and DUT needs further study |
+| Specification effort (defining test decoder and requirements) | Low | Low | Highest<br><br>RAN4 needs to standardize the entire decoder | High<br><br>RAN4 needs to study and may decide on what to standardize |
+| Confidentiality/ IP issues in the testing procedure (after specs are published) | | | No | No |
+| Applicability to different scenarios/conditions/ configurations | | | | |
+| Complexity of testing for the ecosystem | Testing the encoder at DUT<br><br>Higher than Option 3/4<br><br>Need for interaction between TE vendor | Testing the encoder at DUT<br><br>Higher than Option 3/4<br><br>Testing complexity higher also than Option 1 | Testing the encoder at DUT<br><br>Low – no need for interaction between TE vendors and other parties | Testing the encoder at DUT<br><br>Low – no need for interaction between TE vendors and other parties |
+| Complexity of verifying/testing the test decoder | Higher than Option 3/4<br><br>FSS compared to Option 2 | Higher than Option 3/4<br><br>FSS compared to Option 1 | Low | Low |
+| Complexity of deploying for the ecosystem | | | | |
+| Friendly to STOA (state of the art) model test / Forward compatibility when new AI models are invented | | | | |
+| Relationship with reference decoder/encoder (used by RAN4 to define the performance requirements) for defining the requirement | | | | |
+| Whether model transfer/delivery is needed during the test procedure | | | | |
+
+The feasibility of any of the testing options has not concluded and more study is required. Other testing options are not precluded and different options might be required after RAN4 performs additional studies.
+
+#### 7.3.2.4 Data collection/generation for testing
+
+Different generating methods of test dataset can be used for different tests. The following candidate methods are to be considered:
+
+- Dataset based on TR 38.901, e.g. UMa channel, UMi channel, CDL channel, "legacy approach", etc.
+- "Legacy approach" refers legacy test in which a channel model is used
+
+- Field dataset (data collected directly from field measurements)
+- TE generates dataset for test based on assumptions/parameters defined by RAN4 (e.g. by defining some rules/function to generate data)
+- Other methods are not precluded
+
+#### 7.3.2.5 Data collection/generation for training
+
+Some conditions and/or accuracy requirements for the training dataset or training data generation could only be introduced if the training procedure is defined in 3GPP specifications.
+
+#### 7.3.2.6 Generalization/scalability aspects
+
+The necessity and feasibility of defining requirements or test to verify the generalization of AI/ML is studied.
+
+The goals of generalization test are to verify whether the minimum level of performance of AI/ML functionality/model can be achieved/maintain under the identified scenarios and/or configurations, while the performance won't be significantly degraded in other scenarios and/or configurations. The following aspects should be considered for generalization/scalability related testing:
+
+- details about the scenarios and/or configurations for test and the corresponding AI/ML models/functionality
+- what the minimum level performance for each identified scenario and/or configuration is
+- what the significant degradation for other scenarios and/or configurations is
+
+It should also be considered that generalization and/or scalability related requirements for different scenarios/configurations can be implicitly handled in the test case definition.
+
+As for the handling of generalization tests, the following option is considered as baseline:
+
+Signalling based LCM procedures and performance monitoring are considered in dedicated test cases and are excluded in tests verifying generalization. RAN4 may define multiple tests with different conditions. In each of the test, TE configures the same specified UE configuration, and therefore the same specified UE configuration is tested under different conditions to verify its generalizability. (environment differs in each test but not changing dynamically during the test)
+
+- Specified UE configuration includes functionality and/or model ID if defined
+
+#### 7.3.2.7 AI/ML processing capability
+
+The practical processing capability and implementation complexity for device under test should be assumed when specifying RAN4 requirements.
+
+- The UE capability may be needed to handle different complexity for one side and two-side models.
+- The complexity of UE should also be studied when making assumption on gNB side model, and vice versa.
+
+### 7.3.3 CSI feedback enhancement
+
+Both time domain CSI prediction and spatial-frequency domain CSI compression are considered.
+
+PMI reporting framework (follow PMI vs. random PMI test, use of $\gamma$ as criteria, etc.) is taken as starting point for CSI related tests. Other metrics/framework is not precluded.
+
+For metrics for CSI requirements/tests, the following test metrics are identified:
+
+- Option 1: Throughput/relative throughput
+- Option 2: SGCS, NMSE
+- Option 3: CSI prediction accuracy
+
+Option 1 should be used as baseline. For option 3, further discuss is needed on the feasibility to define the CSI prediction accuracy in WI. For metrics for CSI monitoring, further discussion is needed in WI.
+
+### 7.3.4 Beam management
+
+Both spatial-domain DL beam prediction and temporal DL beam prediction are considered.
+
+For metrics for beam management requirements/tests, the following test metrics are identified and could be considered
+
+- Option 1: RSRP accuracy
+- Option 2: Beam prediction accuracy
+ - Top-1 (%) : the percentage of "the Top-1 strongest beam is Top-1 predicted beam"
+ - Top-K/1 (%) : the percentage of "the Top-1 strongest beam is one of the Top-K predicted beams"
+ - Top-1/K (%) : the percentage of "the Top-1 predicted beam is one of the Top-K strongest beams"
+- Option 3: The successful rate for the correct prediction which is considered as maximum RSRP among top-K predicted beams is larger than the RSRP of the strongest beam – x dB,
+ - Related measurement accuracy can be considered to determine x
+- Option 4: combinations of above options
+
+The overhead/latency reduction should be considered for the requirements as the side condition.
+
+### 7.3.5 Positioning accuracy enhancements
+
+Both direct AI/ML positioning and AI/ML assisted positioning are considered.
+
+For metrics for positioning requirements/tests, the candidate options include
+
+- Option 1: positioning accuracy: Ground truth vs. reported
+ - only option available for direct positioning
+- Option 2: CIR/PDP, channel estimation accuracy
+- Option 3: ToA, RSTD and RSRP, and RSRPP
+- Option 4: others (e.g., intermediate KPIs, LoS/NLoS)/combinations of the above
+
+The feasibility and testability of different options should be further justified in WI.
+
+# --- 8 Conclusions
+
+The following aspects have been studied for the general framework of AI/ML over air interface for one-sided models and two-sided models:
+
+- Various Network-UE Collaboration Levels
+- Functionality-based LCM and model-ID-based LCM
+- Functionality/model selection, activation, deactivation, switching, fallback
+- Functionality identification and model identification
+- Data collection
+- Performance monitoring
+- Various model identification Types and their use cases
+
+- Reporting of applicable functionalities/models
+- Method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE
+- Model delivery/transfer and analysis of various model delivery/transfer Cases
+
+The above studied aspects for General Framework can be considered for developing/specifying AI/ML use cases and common framework (if needed for some aspects) across AI/ML use cases.
+
+## ***CSI feedback enhancement:***
+
+## **CSI compression sub use case:**
+
+The performance benefit and potential specification impact were studied for AI/ML based CSI compression sub use case.
+
+Evaluation has been performed to assess AI/ML based CSI compression from various aspects, including performance gain over non-AI/ML benchmark, model input/output type, CSI feedback quantization methods, ground-truth CSI format, monitoring, generalization, training collaboration types, etc. Some aspects were studied but not fully investigated, including the options of CQI/RI calculation, the options of rank>1 solution.
+
+Performance gain over baseline and computational complexity in FLOPs are summarized in clause 6.2.2.8.
+
+Potential specification impact on NW side/UE side data collection, dataset delivery, quantization alignment between CSI generation part at the UE and CSI reconstruction part at the NW, CSI report configuration, CSI report format, pairing information/procedure and monitoring approach were investigated but not all aspects were identified.
+
+The pros and cons are analysed for each training collaboration types, and each training collaboration type has its own benefits and limitations in different aspects. The study has investigated the feasibility of the studied training collaboration types and necessity of corresponding potential RAN1 specification impact. However, not all aspects have been concluded.
+
+Both NW side and UE side performance monitoring were studied, some but not all aspects were concluded.
+
+From RAN1 perspective, there is no consensus on the recommendation of CSI compression for normative work.
+
+At least the following aspects are the reasons for the lack of RAN1 consensus on the recommendation of CSI compression for normative work:
+
+- Trade-off between performance and complexity/overhead.
+- Issues related to inter-vendor training collaboration.
+
+Other aspects that require further study/conclusion are captured in the summary above.
+
+## **CSI prediction sub use case:**
+
+The performance and potential specification impact were studied for AI/ML based UE side CSI prediction sub use case.
+
+Evaluations have been performed to assess AI/ML based CSI prediction from various aspects, including performance compared to baseline, model input/output type, generalization over UE speed, etc. Some aspects are studied but lack observations, including scalability over various configurations and generalization over other scenarios and approach of fine tuning. Performance monitoring accuracy has not been evaluated.
+
+Performance compared with baseline is summarized in clause 6.2.2.8.
+
+Potential specification impact on data collection and performance monitoring are discussed in clause 7.2.2. Limited specification aspects were considered.
+
+From RAN1 perspective, there is no consensus on the recommendation of CSI prediction for normative work.
+
+The reason for the lack of RAN1 consensus on the recommendation of CSI prediction for normative work:
+
+- Lack of results on the performance gain over non-AI/ML based approach and associated complexity.
+
+Other aspects that require further study/conclusion are captured in the summary above.
+
+## ***Beam management:***
+
+This study focuses on evaluation of potential benefits of AI/ML-based beam management and analysis of potential enhancements to enable AI/ML for beam management.
+
+During the study, BM-Case1 (Spatial-domain downlink beam prediction) and BM-Case2 (Temporal-domain downlink beam prediction), as described in clause 5.2, are selected as the representative sub use cases.
+
+Evaluation scenarios and KPIs are described in clause 6.3.1, and the detailed evaluation results from different sources and the key observations are captured in clause 6.3.2. Evaluation results have shown that it is beneficial to enable AI/ML for beam management in the considered evaluation scenarios.
+
+The necessity, feasibility, benefit and potential specification impacts of potential enhancements to enable AI/ML for beam management were studied from different aspects, and the outputs are captured in clause 7.
+
+For AI-based beam management, from RAN1 perspective, at least the following are recommended for normative work:
+
+- Both BM-Case1 and BM-Case2:
+ - BM-Case1: Spatial-domain DL Tx beam prediction for Set A of beams based on measurement results of Set B of beams
+ - BM-Case2: Temporal DL Tx beam prediction for Set A of beams based on the historic measurement results of Set B of beams
+- DL Tx beam prediction for both UE-sided model and NW-sided model
+- Necessary signalling/mechanism(s) to facilitate data collection, model inference, and performance monitoring for both UE-sided model and NW-sided model
+- Signalling/mechanism(s) to facilitate necessary LCM operations via 3GPP signalling for UE-sided model
+
+## ***Positioning accuracy enhancements:***
+
+This study focused on the analysis of potential enhancements necessary to enable AI/ML for positioning accuracy enhancements with NR RAT-dependent positioning methods.
+
+Evaluation scenarios and KPIs were identified for system level analysis of AI/ML enabled RAT-dependent positioning techniques as described in clause 6.4.
+
+Direct AI/ML positioning and AI/ML assisted positioning were identified and selected as the representative sub-use cases. Evaluation results have shown that in considered evaluation scenarios (i.e., InF-DH, and other InF scenarios), both direct AI/ML positioning and AI/ML assisted can significantly improve the positioning accuracy compared to existing RAT-dependent positioning methods. Various aspects of AI/ML for positioning accuracy enhancement were investigated and evaluated as described in clause 6.4 that provides summary of evaluation results from different sources.
+
+Based on the conducted analysis, it is recommended to proceed with normative work for AI/ML based positioning.
+
+The necessity, feasibility and potential enhancements to facilitate the support of AI/ML for positioning accuracy enhancements with NR RAT-dependent positioning methods were studied and the outcome are outlined in clause 7.
+
+It is recommended to specify necessary measurement, signalling and procedure to facilitate training, inference, monitoring and/or other LCM operations for both direct AI/ML positioning and AI/ML assisted positioning, specifically:
+
+- specify necessary signalling of data collection; investigate the necessity of other information for supporting data collection, and if needed, specify during normative work
+- investigate on the necessity and signalling details of measurement enhancements, and if needed, specify during normative work
+- investigate on the necessity and signalling details of monitoring method(s), and if needed, specify during normative work
+
+A variety of enhancements for measurements (e.g., based on extensions to current positioning measurements or with new measurements) were also identified as potentially beneficial (e.g., trade-off positioning accuracy requirement and signalling overhead) and are recommended to be investigated further and if needed, specified during normative work.
+
+# Annex A: Change history
+
+| Change history | | | | | | | |
+|----------------|-----------|------------|----|-----|-----|-------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2022-05 | RAN1#109e | | | | | TR skeleton | 0.0.0 |
+| 2023-05 | RAN1#113 | R1-2306235 | | | | RAN1 agreement up to and including RAN1#112bis-e | 0.1.0 |
+| 2023-08 | RAN1#114 | R1-2308681 | | | | RAN1 agreements from RAN1#113 and RAN1#114 | 0.2.0 |
+| 2023-09 | RAN#101 | RP-231766 | | | | TR presented for information at RAN#101 [same as R1-2308681] | 1.0.0 |
+| 2023-10 | RAN1#114b | R1-2310163 | | | | Added clause numbering for CSI and BM performance results. | 1.1.0 |
+| 2023-11 | RAN1#115 | R1-2312055 | | | | RAN1 agreements from RAN1#114b | 1.2.0 |
+| 2023-11 | RAN1#115 | R1-2312764 | | | | Agreements from RAN1#115, RAN2#124 and RAN4#109 | 1.3.0 |
+| 2023-12 | RAN#102 | RP-233133 | | | | TR presented for approval at RAN#102 [same as R1-2312764] | 2.0.0 |
+| 2023-12 | RAN#102 | RP-233946 | | | | Editorial corrections for RAN approval, removal of square brackets in Scope clause. | 2.0.1 |
+| 2023-12 | RAN#102 | | | | | Rel-18 TR under change control further to RAN approval | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38844/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-18/38_series/38844/00504fc688ebcf131ccbeff94dfc9939_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4f73ff60532d3bdbe3f11bed65a1ab25c255c87
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/00504fc688ebcf131ccbeff94dfc9939_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e61555b365e52227d1bee8c3eff840e918ee7d75f2a3a37040572bb189fd3263
+size 8183
diff --git a/marked/Rel-18/38_series/38844/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-18/38_series/38844/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5908d3fe2afbcf45024c67f60f3658d7a65455b
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5787bf33adc884982716a8cbe2cc918ea7db32e367e905f992f98ee1f3af2074
+size 81293
diff --git a/marked/Rel-18/38_series/38844/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-18/38_series/38844/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d4e196ced294888d87796e204fb92122f145204
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a803ff98b22bf8b3db079b993ee5ef60d5cbf3045d82bb796c5cb83c06c37d1
+size 39578
diff --git a/marked/Rel-18/38_series/38844/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-18/38_series/38844/21ad58fee90f2be50708ff541d225507_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e676d1ff2daca8f8f7874ace18475781c4d6a6e
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/21ad58fee90f2be50708ff541d225507_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26b9252c608b819cbffb6990d130c7f4d9260458b48c294112ba759704b0440e
+size 77923
diff --git a/marked/Rel-18/38_series/38844/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-18/38_series/38844/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f20847a00805f83d3c95a3b2fb19159d82ad7de
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:afd4a2e83a73a4d9c5819d4d5fc62f77e2107826856131e608cd2353f4c5d87d
+size 27996
diff --git a/marked/Rel-18/38_series/38844/390120de4fe440c42fea8154fcaad334_img.jpg b/marked/Rel-18/38_series/38844/390120de4fe440c42fea8154fcaad334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53308322829adbe4b57fe34e26b7a95d81bce752
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/390120de4fe440c42fea8154fcaad334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8c16e6c417eaf59d3125b547f9a4a9e215c6d2beadd72a28336be7ed64d3cb9
+size 9563
diff --git a/marked/Rel-18/38_series/38844/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-18/38_series/38844/54fabc351eda5228d2fa28cd9ba07971_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..60b34fabd01568c5ec5f2f4c47885bb91656a0b3
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/54fabc351eda5228d2fa28cd9ba07971_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa06d3ae6a728a4ba6628a4026145c05449f8b9bf0b253093080fe39367922f9
+size 4332
diff --git a/marked/Rel-18/38_series/38844/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38844/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d478cd8e06099cf4be87b67337c4aba54760840
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0804d21f683c80fb7f8156f7d0a663beae7ec684768ae34e4fb56264537a3e13
+size 5725
diff --git a/marked/Rel-18/38_series/38844/5fbb4f0de01736f1293333e599410c99_img.jpg b/marked/Rel-18/38_series/38844/5fbb4f0de01736f1293333e599410c99_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..722ed0f247b394b596df9fdb09e242feb6694be4
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/5fbb4f0de01736f1293333e599410c99_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fd6d0ad74f86faf5403e7d7b57acbd4505bafeaaa70211910d6756102bca0ad
+size 25451
diff --git a/marked/Rel-18/38_series/38844/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-18/38_series/38844/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..611a76f1182447d413a8881e82e332d66b9b802f
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3297f9141f87f015e72cbf45bda9932479bf864b7cf67ad81f3dd0692e959093
+size 13379
diff --git a/marked/Rel-18/38_series/38844/6682c4376efdda007851175f3014eca3_img.jpg b/marked/Rel-18/38_series/38844/6682c4376efdda007851175f3014eca3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7813f7ab4dc3d9c8f90669e7abfba72980ce90f7
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/6682c4376efdda007851175f3014eca3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a03624030773671694dea4d1dab2e6ce4b071c85d259e5fad95432466b00f6b
+size 23149
diff --git a/marked/Rel-18/38_series/38844/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-18/38_series/38844/73dff6b45b2b9ffd384bab3235f869af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f7aff79159673faaabe1dd18dce1f28404d3a42
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/73dff6b45b2b9ffd384bab3235f869af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:070eca5f747bd246aa83113695fe71d485ae73c2fff671f9e884f8d07cde087e
+size 12770
diff --git a/marked/Rel-18/38_series/38844/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-18/38_series/38844/8307f6b04df072c9332f9987e034272c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e11b4087959229374c4975e96cb11e4274bb8e4
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/8307f6b04df072c9332f9987e034272c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:764fed47e2679e64adf833bd3c8fa98feb6e6c13a6e005785f40ebfd062b1293
+size 82540
diff --git a/marked/Rel-18/38_series/38844/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-18/38_series/38844/844077b3034f0030b404207db0ad76b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81a3494087c8051e7be4ffa202399432ac52081e
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/844077b3034f0030b404207db0ad76b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1acca4245ecfbbb4a96a17acabfa6efdb2521b5fa06cb0c8a334919935e23e5
+size 18115
diff --git a/marked/Rel-18/38_series/38844/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/38_series/38844/90ddb84c323b956e2d50a54d3f870566_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..37f2073be3ae1b665225a961440a1cdad37f4827
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/90ddb84c323b956e2d50a54d3f870566_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bab23745bfc54b722a0b27b81e21425bbf8b0db29f2da2f867f93c807159004
+size 74760
diff --git a/marked/Rel-18/38_series/38844/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-18/38_series/38844/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd42130eee85143b17a9b7d31bf2c35774c06c4e
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9b28ca7562a4eb4f357904d457d81ed864e1ecd0182edf6b71700496f682eca
+size 53238
diff --git a/marked/Rel-18/38_series/38844/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-18/38_series/38844/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c301d63aaa135157f96ee1e7003560ea8d2fc942
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5017e1168a338cf3c44c9f396457a6c0f8ea9140eda1bfc627d19d5407a608e
+size 74309
diff --git a/marked/Rel-18/38_series/38844/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-18/38_series/38844/bb3354f497635d15bef873577125c48d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b63e489dcc7df66ce9e4966257884dc5c9add809
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/bb3354f497635d15bef873577125c48d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb4e28c65955b1ff618702644600623fdb41883cac33d8781d3b467cfdc8254b
+size 19825
diff --git a/marked/Rel-18/38_series/38844/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-18/38_series/38844/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4c25cd3449fa3e16d601f81f0f6c42ad3261ed3
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:468024790402b40aa9166de4dbf5bd4b329b74f5a965bbf7d868dc9a6f249018
+size 78181
diff --git a/marked/Rel-18/38_series/38844/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-18/38_series/38844/d79d33da852cb7bca3e87b400a15c3e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f916fc86e2b2498c7e34c1bc79e9ec0e2d2af5f8
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/d79d33da852cb7bca3e87b400a15c3e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:743ce3a2409c280bdcd7e7c0ca086149d54267e61db569ecb242476921f9b9d1
+size 8309
diff --git a/marked/Rel-18/38_series/38844/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg b/marked/Rel-18/38_series/38844/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..538bd5932e402527971328ae655bbed53dd1eeaf
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc7157d10559a6866556a828b73cfa83d9f844254480bbc36dff6afa2d2d0bed
+size 26080
diff --git a/marked/Rel-18/38_series/38844/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-18/38_series/38844/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..52c57ef32781c94865d56e6f8735ef69a740e294
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd9d5cf5da8496ef98822b45eda144e25c8f9f03f24cdac992e2064a13509501
+size 24424
diff --git a/marked/Rel-18/38_series/38844/raw.md b/marked/Rel-18/38_series/38844/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7fe58a3411a686f5ab2d0572441d5ee27402018c
--- /dev/null
+++ b/marked/Rel-18/38_series/38844/raw.md
@@ -0,0 +1,1188 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths**
+
+**(Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|---------------------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| Introduction ..... | 6 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions of terms, symbols and abbreviations ..... | 7 |
+| 3.1 Terms..... | 7 |
+| 3.2 Symbols..... | 8 |
+| 3.3 Abbreviations ..... | 8 |
+| 4 Background ..... | 8 |
+| 4.1 Objectives..... | 8 |
+| 5 General..... | 9 |
+| 5.1 UE channel bandwidth ..... | 9 |
+| 6 Result, Analysis outcome..... | 10 |
+| 6.1 Study of larger Channel BW than licensed BW ..... | 10 |
+| 6.1.1 General Aspects..... | 10 |
+| 6.1.2 Signalling and configuration aspects..... | 11 |
+| 6.1.2.1 Method using a larger channel bandwidth is broadcast in SIB1..... | 11 |
+| 6.1.2.1.1 General ..... | 11 |
+| 6.1.2.1.2 FDD..... | 12 |
+| 6.1.2.1.3 TDD..... | 14 |
+| 6.1.2.2 Method using Next smaller channel bandwidth is broadcast in SIB1 ..... | 15 |
+| 6.1.2.3 Further Signalling and configuration aspects: Band Edge..... | 16 |
+| 6.1.2.4 Configuring a UE with a Channel not Fully Contained within the Operating Band ..... | 17 |
+| 6.1.3 UE channel filters ..... | 18 |
+| 6.2 Study of overlapping UE channel bandwidths..... | 20 |
+| 6.2.1 Overlapping UE CBWs from Network Perspective ..... | 20 |
+| 6.2.1.1 General..... | 20 |
+| 6.2.1.2 Detailed description ..... | 21 |
+| 6.2.1.3 Configuration and signalling aspects..... | 23 |
+| 6.2.1.4 Channel raster handling ..... | 23 |
+| 6.2.2 Combined UE CBW (one cell)..... | 23 |
+| 6.2.2.1 General Aspects..... | 23 |
+| 6.2.2.2 Signalling and configuration aspects ..... | 24 |
+| 6.2.2.3 UE architecture aspects..... | 24 |
+| 6.2.3 Overlapping CA (two cells)..... | 26 |
+| 6.2.3.1 General Aspects..... | 26 |
+| 6.2.3.2 Configuration and signalling aspects ..... | 27 |
+| 6.3 Complexity and efficiency study..... | 27 |
+| 6.3.1 Larger Channel BW than licensed BW ..... | 27 |
+| 6.3.2 Overlapping UE CBW from Network Perspective..... | 27 |
+| 6.3.3 Combined UE CBW (one cell)..... | 27 |
+| 6.3.4 Overlapping CA (two cells)..... | 28 |
+| 6.4 Generic solutions guidance ..... | 29 |
+| 6.4.1 Larger Channel BW than licensed BW ..... | 29 |
+| 6.4.2 Overlapping UE CBW from Network Perspective..... | 29 |
+| 6.4.3 Combined UE CBW (one cell)..... | 29 |
+| 6.4.4 Combined UE CBW (two cell)..... | 29 |
+| 6.5 RAN1 and RAN2 impact ..... | 30 |
+| 6.5.1 Larger Channel BW than licensed BW ..... | 30 |
+| 6.5.2 Void ..... | 30 |
+| 6.5.3 Void..... | 30 |
+| 6.5.4 Combined UE CBW (two cells)..... | 30 |
+| 6.6 Legacy UE impact..... | 30 |
+
+| | | |
+|------------------------------------------------------------|-----------------------------------------------------------------------------------------|-----------|
+| 6.6.1 | Void ..... | 30 |
+| 6.6.2 | Overlapping UE CBW from Network Perspective..... | 30 |
+| 6.6.3 | Combined UE CBW (one cell)..... | 30 |
+| 6.7 | RAN4 standard impact identification..... | 31 |
+| 6.7.1 | Larger Channel BW than licensed BW ..... | 31 |
+| 6.7.2 | Combined UE CBW (one cell)..... | 31 |
+| 6.7.3 | Overlapping CA (two cells)..... | 31 |
+| 6.7.4 | Overlapping UE CBWs from Network Perspective ..... | 32 |
+| 6.7.5 | Dedicated BS channel bandwidths ..... | 32 |
+| 6.7.6 | Additional enhancements ..... | 33 |
+| 6.7.6.1 | Channel raster enhancements..... | 33 |
+| 6.7.6.2 | UE channel larger than SIB1 channel enhancement..... | 33 |
+| 7 | Conclusion ..... | 34 |
+| 7.1 | Comparison Between Different Schemes ..... | 34 |
+| 7.2 | Study Item Conclusions ..... | 36 |
+| <b>Annex A (informative): The case of n12 and n85.....</b> | | <b>37</b> |
+| A.1 | Support for n12 and n85 at the lower edge of the bands ..... | 37 |
+| A.2 | Support for n12 and n85 overlap using the next wider channel bandwidth approach ..... | 37 |
+| A.3 | Support for n12 and n85 overlap using the overlapping channel bandwidth approaches..... | 37 |
+| <b>Annex B (informative): Change history .....</b> | | <b>38</b> |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- Introduction
+
+One of the aims of 5G is providing bandwidth flexibility. Although this is achieved in general, but for some spectrum allocations the ability to achieve such flexibility needs further study.
+
+# --- 1 Scope
+
+The present document is the Technical Report of the Study Item on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths, approved at TSG RAN #89-e [2]. The purpose of this document is to capture and document the outcome of the objectives stated in the SID.
+
+# --- 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] RP-202103: SID "Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths"
+- [3] R4-2200031: Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths, RAN2
+- [4] R4-2119411: Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths, RAN1
+- [5] R2-1902778, "Clarification to channel bandwidth signalling", Nokia, Nokia Shanghai Bell, Qualcomm
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Larger Channel BW than licensed BW:** Uses the closest NR channel bandwidth defined in Rel-17 which is larger/wider than the irregular bandwidth. Also referred to as Next Wider CBW.
+
+**Irregular bandwidth:** an NR bandwidth that is not defined in Rel-17
+
+**Overlapping UE channel BW from network perspective:** network supports the irregular bandwidth (either by a single carrier or by two overlapping carriers) while each UE operates in an existing lower regular NR channel bandwidth
+
+**Combined UE channel BW (one cell):** network supports the irregular bandwidth as well as some new UEs with support of two overlapping (RF) carriers. Also referred to as Overlapping UE channel BW from UE perspective.
+
+**Overlapping CA:** the irregular bandwidth is handled by two overlapping component carriers (CCs) with NR channel bandwidth defined in Rel-17. It is network responsibility to prevent collisions between the different component carriers.
+
+**Single BB carrier:** means that from baseband (RAN1) perspective, there is a single cell with a waveform according to a single carrier
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+<symbol> <Explanation>
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|------|------------------------------------------------------------------------|
+| ACLR | Adjacent Channel Leakage Ratio |
+| ACS | Adjacent Channel Selectivity |
+| BS | Base Station |
+| BW | Bandwidth |
+| CBW | Channel Bandwidth |
+| FR1 | Frequency Range 1 |
+| OBUE | Operating Band Unwanted Emissions |
+| RF | Radio Frequency |
+| SCBW | Smaller Channel Bandwidth (Existing immediate lower channel bandwidth) |
+| UE | User Equipment |
+| WCBW | Wider Channel Bandwidth (Existing immediate wider channel bandwidth) |
+
+# 4 Background
+
+One of the aims of 5G is providing bandwidth flexibility. Although this is achieved in general, for some spectrum allocations the ability to achieve such flexibility needs further study.
+
+Solutions for the following spectrum allocations have been requested so far:
+
+**Table 4-1: Summary of operators' input for irregular channel bandwidth**
+
+| Band (s) | Channel Bandwidth(s) |
+|----------|----------------------|
+| n5 | 7, 11 MHz |
+| n12, n85 | 6, 12 MHz |
+| n26 | 7 MHz |
+| n28 | 13 MHz |
+| n29 | 6, 11 MHz |
+
+Some techniques have been suggested for re-using existing channel bandwidths which can include but are not limited to overlapping UE channel bandwidths, and/or using larger bandwidths than operator licensed bandwidth. This Study Item is needed to evaluate where existing techniques can be used to efficiently utilize operator spectrum allocations, and whether and how new channel bandwidths should be created. The Study shall also analyse if a proprietary solution(s) is sufficient.
+
+## 4.1 Objectives
+
+The following objectives are listed in the SID [2]
+
+- 1) Identify operator licensed channel bandwidths in FR1 that do not align with existing NR channel bandwidths.
+ - Only licensed spectrum wider than 5 MHz to be considered in this SID.
+ - Spectrum block of 33MHz in n28 require further investigation since there is dual duplexer assumption (2x30MHz) for this band.
+ - 2) Evaluate the potential use of larger channel bandwidths than operator licensed bandwidth, including the impacts on regulatory emission requirements/UE output power implications and UE ACS/blocking impacts depending on the guard band and the SCS.
+ - 3) Study the use of overlapping UE channel bandwidths (from both UE and network perspective) to cover operator's license spectrum for both UL and DL, and if new gNB channel bandwidths are needed.
+- NOTE: For all considered solutions, new (dedicated) channel filters (e.g. non-integer-multiples of 5MHz) are not considered for the UE and not prioritized for the gNB.
+- 4) Identify operator licensed bandwidths that are not compatible with the use of techniques like overlapping UE channel bandwidths. Every proposed method shall be summarized with respect to whether all considered spectrum scenarios are supported or whether there are specific limitations. Some limitations for a specific method shall not disqualify such method if there is a trade-off between flexibility and implementation challenges.
+ - 5) Study the complexity and efficiency of adding new channel bandwidths vs. using other including testing aspects.
+ - 6) Generic solution(s) should be intended as much as possible, with priority should be given to approaches that avoid the introduction of new channel BWs on the UE side. Proprietary solutions if proven relevant should not be precluded. Spectrally efficient methods providing a fine channel bandwidth granularity as well as low to moderate guard band width and signalling overhead should be preferred
+ - 7) Impact on RAN1 and RAN2 should be considered and minimized
+ - 8) For any considered solution, Ues not supporting such solution (both legacy and new Ues) should be able to use the next lower supported channel bandwidth in the UL and DL without implications.
+ - 9) Impact (if any) on RAN4 requirements should be identified for the preferred solutions.
+
+# --- 5 General
+
+## 5.1 UE channel bandwidth
+
+The following text is copied from TS38.101-1 for information:
+
+The UE channel bandwidth supports a single NR RF carrier in the uplink or downlink at the UE. From a BS perspective, different UE channel bandwidths may be supported within the same spectrum for transmitting to and receiving from Ues connected to the BS. Transmission of multiple carriers to the same UE (CA) or multiple carriers to different Ues within the BS channel bandwidth can be supported.
+
+From a UE perspective, the UE is configured with one or more BWP / carriers, each with its own UE channel bandwidth. The UE does not need to be aware of the BS channel bandwidth or how the BS allocates bandwidth to different Ues.
+
+The placement of the UE channel bandwidth for each UE carrier is flexible but can only be completely within the BS channel bandwidth.
+
+# 6 Result, Analysis outcome
+
+## 6.1 Study of larger Channel BW than licensed BW
+
+### 6.1.1 General Aspects
+
+This clause describes, in general terms, how to utilize an irregular Channel Bandwidth by deploying the “larger channel Bandwidth” method.
+
+The premise idea is that the system is configured with the larger channel bandwidth, as indicated in the broadcast System Information (SIB1) as described in 6.1.2.1, or UE is reconfigured to the larger channel bandwidth in connected mode than SIB1 as described in 6.1.2.2, but the actual number of scheduled RBs is restricted so that it matches actual spectrum allocation ensuring sufficiently large guard bands.
+
+
+
+Diagram illustrating the use of a larger channel bandwidth. It shows two horizontal bars: a top grey bar labeled '7 MHz' and a bottom green bar labeled '10 MHz'. The green bar is wider than the grey bar, representing a larger channel bandwidth.
+
+**Figure 6.1.1-1: Using the next larger channel bandwidth (example for 7MHz).**
+
+**NOTE:** It should be checked further whether it is possible to configure the next larger channel so that it goes over the band edge and which implications it has.
+
+**NOTE:** The UE UL channel bandwidth is assumed to be the next-smaller regular channel bandwidth (in MHz) in this study.
+
+One of the first aspects for this approach is the size of guard bands and the anticipated number of schedulable RBs. For the standard channel bandwidths, both values are captured in the corresponding specification to avoid any misinterpretation on how many RBs can be configured and scheduled. Following the same principle for every irregular channel bandwidth would be feasible, but would create the same amount of technical specification work as if the corresponding irregular channel bandwidth were explicitly added to the specifications. Thus, the number of "available" RBs can be calculated based on certain assumptions.
+
+The maximum number of "available" or "schedulable" RBs for a particular irregular channel bandwidth can be calculated based on the assumption of using larger guard bands from a *larger* channel bandwidth. As an example, while considering the 7MHz channel bandwidth, the assumption is to consider next larger 10MHz channel guard bands at both ends, from which number of available RBs can be calculated.
+
+**NOTE:** Since a UE will be configured with the channel bandwidth, which is larger than the actual allocation, and it is not expected to provide the usual stop-band attenuation at the edges of the irregular channel bandwidth, it is necessary to verify the level of potential degradation of ACS/blocking. Sub-clause 6.1.3 provides further information on UE filters and potential performance.
+
+**NOTE:** Similarly, the gNB operating with wider channel filters cannot be expected to provide stop-band attenuation at the edges of the irregular channel bandwidth to guarantee the co-existence. It is assumed that the gNB channel filters are implemented such that regulatory unwanted emissions requirements are met outside any operator spectrum block of irregular bandwidth (this is a common case also in existing deployments).
+
+Table 6.1.1-1 below presents example maximum number of available RBs for different irregular channel bandwidths considered in this study item.
+
+**NOTE:** Number of available RBs and spectral utilisation are taken from R4-2112365. The gNB transmitter filter assumption used to derive the RB numbers is FFS.
+
+**Table 6.1.1-1: Exemplary number of RBs based on the next larger channel guard bands (15kHz SCS).**
+
+| Channel (MHz) | Next larger channel (MHz) | Next larger channel guard band (kHz) | Next larger channel Nrb | Channel Nrb | Utilisation (%) |
+|---------------|---------------------------|--------------------------------------|-------------------------|-------------|-----------------|
+| 6 | 10 | 312,5 | 52 | 29 | 87 |
+| 7 | 10 | 312,5 | 52 | 35 | 90 |
+| 11 | 15 | 382,5 | 79 | 56 | 91,6 |
+| 12 | 15 | 382,5 | 79 | 62 | 93 |
+| 13 | 15 | 382,5 | 79 | 67 | 92,8 |
+
+Table 6.1.1-2 below presents similar calculations for 30kHz SCS, from which one can see that combination of 30kHz SCS and the next larger channel is not generally a good approach for small channel bandwidths. The main reason is that 30kHz SCS has much larger guard bands, which immediately impacts number of available RBs. As a small summary, assuming using guard band from the next larger channel the resulting spectrum Utilization would range from 87 to 92.8% for an SCS of 15kHz and 72 to 88.6% for an SCS of 30kHz.
+
+NOTE: Number of available RBs and spectral utilisation are taken from R4-2112365. The gNB transmitter filter assumption used to derive the RB numbers is FFS.
+
+**Table 6.1.1-2: Exemplary number of RBs based on the next larger channel guard bands (30kHz SCS).**
+
+| Channel (MHz) | Next larger channel (MHz) | Next larger channel guard band (kHz) | Next larger channel Nrb | Channel Nrb | Utilisation (%) |
+|---------------|---------------------------|--------------------------------------|-------------------------|-------------|-----------------|
+| 6 | 10 | 665 | 24 | 12 | 72 |
+| 7 | 10 | 665 | 24 | 15 | 77,1 |
+| 11 | 15 | 645 | 38 | 26 | 85,1 |
+| 12 | 15 | 645 | 38 | 29 | 87 |
+| 13 | 15 | 645 | 38 | 32 | 88,6 |
+
+### 6.1.2 Signalling and configuration aspects
+
+In this section we provide further signaling details on how to support irregular channels in the DL. Two signaling methods are described. In 6.1.2.1 the next larger or next-after-next CBW is used for an FDD case with a 7 MHz allocation as an example. The use of the method for a TDD case with a larger irregular block size is also illustrated. In 6.1.2.2, the next smaller CBW is used during initial access, and then once RRC connection is established, the next larger CBW is used.
+
+#### 6.1.2.1 Method using a larger channel bandwidth is broadcast in SIB1
+
+##### 6.1.2.1.1 General
+
+The gNB broadcasts the DL carrier bandwidth and the bandwidth of the initial BWP (BWP#0) in SIB1. For the 7MHz allocation, SIB1 can indicate DL next larger standard channel bandwidth, i.e. 10 MHz, and that the initial DL BWP can be set to 5 MHz:
+
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> frequencyInfoDL-> scs-SpecificCarrierList-> carrierBandwidth = 52 PRBs / subcarrierSpacing = 15 kHz
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> initialDownlinkBWP-> genericParameters-> locationAndBandwidth = 25 PRBs
+
+Once the UE established the RRC connection, the gNB can account for the UE capabilities and configure the UE accordingly. At this point the gNB can configure the UE with the larger channel bandwidth (that used by the UE for initial access is not known to the gNB) and with an additional BWP with a bandwidth that differs from the bandwidth of BWP#0. gNB may configure a larger bandwidth part that will cover the whole 7MHz allocation.
+
+- ServingCellConfig-> downlinkChannelBW-PerSCS-List-> carrierBandwidth = 52 PRBs, subcarrierSpacing = 15 kHz
+
+- ServingCellConfig-> downlinkBWP-ToAddModList-> bwp-Common-> genericParameters-> locationAndBandwidth = 35 PRBs
+
+with the BWP size taken from Table 6.1.1-1. The PRBs within this BWP can be scheduled. the remaining PRBs in the downlink channel bandwidth are blanked. Alternatively, the BWP size is set to 52 PRB with 35 PRBs scheduled.
+
+NOTE: BWPs of sizes different from the already defined channel bandwidths are not currently tested within the RAN4 defined requirements. As such, UE behaviour under such configuration is not verified by RAN4 requirements. Furthermore, the above configuration does not consider the PRB grid alignment between SIB1 channel bandwidth and UE configured channel bandwidth based on the 100 kHz channel raster.
+
+For the UL the UE is configured with a UE channel bandwidth smaller than the irregular block or equal to the UL BWP#0 size such that this is the only possible channel bandwidth and location during initial access. For *uplinkChannelBW-PerSCS-List* and *scs-SpecificCarrierList* symmetric operation bands with fixed duplex distance and asymmetric UL/DL channel bandwidth is band specific aspect which is defined in TS 38.101-1 and TS 38.101-2. Bands which utilize the wider channel bandwidth approach for the irregular bandwidths may need to be adopted for this aspect.
+
+Another example of interest to some operators is 5 MHz at the bottom of n12 being shared with 6 MHz at the bottom of n85. The details can be found in Annex A.
+
+##### 6.1.2.1.2 FDD
+
+We begin by listing the prerequisites and assumptions for the method of using a larger channel bandwidth as described in this subclause to verify that these are consistent with existing specifications and features.
+
+There is one carrier of carrier bandwidth $N_{\text{grid}}^{\text{size},\mu}$ for subcarrier spacing configuration $\mu$ per serving cell and transmission direction (UL or DL), with $N_{\text{grid}}^{\text{size},\mu}$ as defined in [38.211]. The carrier bandwidth $N_{\text{grid}}^{\text{size},\mu}$ is indicated in SIB1 by the *carrierBandwidth* for subcarrier spacing configuration $\mu$ in the *scs-SpecificCarrierList* and is thus cell specific. Furthermore
+
+- the carrier bandwidth $N_{\text{grid}}^{\text{size},\mu}$ is the BS transmission bandwidth configuration for subcarrier spacing configuration $\mu$ (not necessarily the same as a BS maximum transmission configuration for a channel bandwidth specified in 38.104)
+- the gNB configures all UEs in a cell with an initial BWP (denoted BWP#0) and additional BWPs contained within the said carrier bandwidth indicated in SIB1 for the DL and UL
+- the fields *downlinkChannelBW-PerSCS-List* and *uplinkChannelBW-PerSCS-List* in dedicated signalling are only used for the purpose of configuring the UE with a size and location of a UE *regular* channel bandwidth in MHz to ensure compliance with regulatory requirements consistent with the clarification of the use of UE dedicated channel bandwidths (MHz) agreed in [5].
+
+The UE channel bandwidth must be located within the BS channel bandwidth as per the existing clause 5.3.1 or 38.104,
+
+- The *BS channel bandwidth* supports a single NR RF carrier in the uplink or downlink at the Base Station. Different *UE channel bandwidths* may be supported within the same spectrum for transmitting to and receiving from UEs connected to the BS. The placement of the *UE channel bandwidth* is flexible but can only be completely within the *BS channel bandwidth*.
+
+and its corresponding maximum bandwidth configuration must fall within the within the *BS transmission bandwidth configuration* of the BS channel bandwidth as per clause 5.3.4 of 38.104
+
+- For each numerology, all *UE transmission bandwidth configurations* indicated to UEs served by the BS by higher layer parameter *carrierBandwidth* defined in TS 38.331 [11] shall fall within the *BS transmission bandwidth configuration*.
+
+For irregular bandwidths implemented with larger bandwidths we assume that similar rules apply:
+
+- the transmission bandwidth configuration (PRB) corresponding to the irregular bandwidth is within the carrier bandwidths $N_{\text{grid}}^{\text{size},\mu}$ of the DL and UL carriers indicated to the UE by SIB1, that is, the BS transmission bandwidth configuration of the BS DL that also contain blanked PRBs if larger than the irregular block size
+
+- the BS does not configure a UE with any dedicated channel bandwidth (MHz) outside the carrier resource grid indicated in SIB1.
+- the *BS channel bandwidth* supports a single NR RF carrier in the uplink or downlink as specified in 38.104.
+
+The UE need not be aware of the actual BS channel bandwidth, the carrier location and bandwidth are indicated to the UE in SIB1:
+
+- From a UE perspective, the UE is configured with one or more BWP / carriers, each with its own UE channel bandwidth. The UE does not need to be aware of the BS channel bandwidth or how the BS allocates bandwidth to different UEs.
+
+The channel raster defines a subset of RF reference frequencies that can be used to identify the RF channel position in the uplink and downlink. The mapping between the channel raster and the corresponding resource element within a resource grid of a carrier within the RF channel is specified in the same way in 38.104 and 38.101-1:
+
+- The mapping between the *RF reference frequency* on the channel raster and the corresponding resource element is given in table 5.4.2.2-1 and can be used to identify the RF channel position. The mapping depends on the total number of RBs that are allocated in the channel and applies to both UL and DL. The mapping must apply to at least one numerology supported by the BS.
+
+**Table 5.4.2.2-1: Channel Raster to Resource Element Mapping**
+
+| | $N_{RB} \bmod 2 = 0$ | $N_{RB} \bmod 2 = 1$ |
+|------------------------------------------|---------------------------------------------------------|---------------------------------------------------------|
+| Resource element index $k$ | 0 | 6 |
+| Physical resource block number $n_{PRB}$ | $n_{PRB} = \left\lfloor \frac{N_{RB}}{2} \right\rfloor$ | $n_{PRB} = \left\lfloor \frac{N_{RB}}{2} \right\rfloor$ |
+
+$k$ , $n_{PRB}$ and $N_{RB}$ are as defined in TS 38.211 [...]
+
+We assume that the corresponding notions in 38.211 are $N_{RB} = N_{grid}^{size,\mu}$ and that $n_{PRB}$ is relative to a BWP starting at the start of the carrier resource grid indicated by the common resource block, $N_{BWP,i}^{start,\mu} = N_{grid}^{start,\mu}$ , $n_{PRB}$ is thus the index of the centre PRB within the resource grid of a numerology.
+
+For the configuration examples below, we make the assumption that the $N_{RB}$ can only take values corresponding to the maximum transmission bandwidth configurations corresponding to channel bandwidths in the respective conformance specifications for the BS and the UE. For an operating band with a 100kHz channel raster this implies that any regular BS and UE channel bandwidth are always mapped to the channel raster. For operations in the field this also means that a configured UE-specific bandwidth within a larger BS channel bandwidth must be on the channel raster just like the BS channel bandwidth.
+
+The assumption that UE performance can only be ensured for RRC configurations according to the conformance test specification implies restrictions on the location and bandwidth of UE specific CHBW in operating bands with a 100 kHz channel raster. If the *carrierBandwith* of the carrier resource grid is an odd/even number of PRBs and the maximum transmission bandwidth configuration for the UE CHBW is even/odd for SCS = 15k, then the corresponding UE-specific CHBW cannot be located anywhere within a wider BS carrier resource grid: the said transmission bandwidth configuration cannot both be PRB aligned and separated by a multiple of 100 kHz to the center SC of the resource grid on the channel raster for $m*180 + 90 = n*100$ has no solution for any integers. If, on the other hand, the *carrierBandwidth* of the carrier resource grid is an odd/even number and the maximum transmission bandwidth configuration for the UE CHBW is odd/even for SCS = 15k, then the UE-specific CHBW can only be located with 5 PRB granularity, solutions to $m*180 = n*100$ .
+
+Notwithstanding the above we assume that symmetric UE-specific channel bandwidths (MHz) can be set at the default duplex spacing: the centre frequencies of the UL and DL channel bandwidths as set by the parameters of the *downlinkChannelBW-PerSCS-List* and *uplinkChannelBW-PerSCS-List* should be at default duplex spacing that is, the default TX-RX *carrier* centre frequency separation as specified in clause 5.4.4 of 38.101-1. We also assume that the BWP#0 are configured such that the UE can locate symmetric CHBW at default duplex spacing during initial access.
+
+Next, we illustrate the method for a 7 MHz block within an operating band with a 100k channel raster and assuming the restrictions that
+
+- the SIB1 *carrierBandwidth* and any UE specific channel bandwidth on the 100k channel raster, carrier bandwidths and maximum transmission bandwidth configurations for UL and DL either all odd or all even, otherwise impossible to put a narrower channel inside a wider BS/cell bandwidth
+- the *BS channel bandwidth* supports a single NR RF carrier in the uplink or downlink as specified in 38.104. UL/DL *carrierBandwidth* in SIB1 only to a UE channel bandwidth (Rel-15)
+
+We also note that these restrictions may impact the number of PRB that can be scheduled within the irregular spectrum block (the number of blanked PRB within the carrier resource grid) or the actual irregular spectrum block size that can be supported.
+
+Figure 6.1.2.1.2-1 shows the configuration, the next-after-next larger bandwidth is used in this case such that the resource grid size of this and the smaller bandwidth used for the UL are both an odd number of PRBs. The size of the BWP#0 is 25 PRB in both the UL and DL, located at duplex spacing such that a UE only capable at locating its CHBW at the 100k channel raster can attach. UEs supporting the asymmetric channel bandwidth combination 5 MHz and 15 MHz can utilize the irregular block (the cell bandwidth) and legacy UEs not supporting this bandwidth combination can also be supported in the cell. UEs not supporting the 5 MHz channel bandwidth will not attach to the cell thus ensuring that unwanted emissions requirements in the UL are met by all capable UEs.
+
+
+
+The diagram shows the frequency domain representation of an FDD band with a 7 MHz irregular block. It is divided into four horizontal sections representing different UE capabilities and configurations:
+
+- Top section:** Shows two 7 MHz blocks separated by "Default duplex spacing".
+- SIB1 carrier grid:** Shows a 15 MHz BS CHBW with blanked PRB. It specifies SIB1 DL: *carrierBandwidth* = 79 PRB and UL: *carrierBandwidth* = 25 PRB. The duplex spacing is defined as $F_{REF,DL} - F_{REF,UL} = \text{Default duplex spacing}$ .
+- Legacy UE CHBW:** Shows two 5 MHz blocks. It specifies PRB alignment with the carrier grid. It also lists "Legacy UE dedicated CHBW" with downlinkChannelBW-PerSCS-List: 25 PRB and uplinkChannelBW-PerSCS-List: 25 PRB.
+- UE supporting asymmetric CHBW:** Shows a 5 MHz UL block and a 15 MHz DL block. The 15 MHz DL block is within the BS CHBW and carrierBandwidth. It lists "UE dedicated asymmetric CHBW" with downlinkChannelBW-PerSCS-List: 79 PRB and uplinkChannelBW-PerSCS-List: 25 PRB. The duplex spacing for this combination is also "Default duplex spacing (also for the 5 and 15 MHz combination)".
+
+Blanked PRBs are indicated by orange blocks within the 15 MHz BS CHBW. The 5 MHz blocks are labeled as "Containing UL BWP#0" and "Containing DL BWP#0".
+
+Figure 6.1.2.1.2-1: a 7 MHz irregular block within an FDD band. The diagram illustrates the frequency domain representation of an FDD band with a 7 MHz irregular block. It shows the SIB1 carrier grid, Legacy UE CHBW (5 MHz), and UE supporting asymmetric CHBW (5 MHz UL, 15 MHz DL). Key parameters include Default duplex spacing, F\_REF,DL - F\_REF,UL = Default duplex spacing, and various PRB counts for different UE types.
+
+Figure 6.1.2.1.2-1: a 7 MHz irregular block within an FDD band.
+
+The SIB1 procedure for initial attach is separate for the UL and DL. In case some UE implementations do not allow different carrier grid for the UL and DL (while still corresponding to UE CHBWs) then the next-after-next larger BW and PRB blanking can be used both in the UL and DL. The downside of this arrangement is that unwanted emissions are not ensured in case the UE uses a bandwidth wider than the BWP#0 (25 PRB) during initial access. The Point A of the UL and DL can be located with 5 kHz granularity.
+
+The arrangement in Figure 6.1.2.1.2-1 would not support the case of an irregular block 817-824/862-869 MHz at the lower part of n26. However, the DL carrier grid corresponding to the 15 MHz CHBW can be shifted upwards by $n \cdot 900$ MHz (5 PRB) such that the 15 MHz CHBW is within the band range (above 814 MHz) thus increasing the BS duplex spacing between the UL and DL carriers while maintaining PRB alignment and the default duplex spacing for the 2 x 5 MHz UE-specific bandwidths and the BWP#0. The default duplex spacing is not specified for the BS (cell) bandwidth and the SIB1 procedure for initial attach is separate for the UL and DL.
+
+The methods only require one specification change: the UE must support the asymmetric channel bandwidth pair 5/10 MHz or 5/15 MHz for Band n26. Regular CHBW bandwidths are used for UE conformance tests, while the BS must meet the unwanted emissions limits and other regulatory requirements also for the irregular spectrum block.
+
+##### 6.1.2.1.3 TDD
+
+The method can readily be applied to the TDD case. Most TDD bands have an SCS-based raster rather than a 100k raster for alignment with LTE and therefore not subject to any potential restrictions that UE-specific CHBW cannot be configured with PRB granularity within a carrier resource grid. However, TDD is subject to restrictions on the center frequency of BWPs and the location of the Point A. Asymmetric bandwidths are also supported for TDD in existing specification with restrictions.
+
+For the TDD case and bands we make the following additional assumptions:
+
+- the carrier resource grids indicated in SIB1 for the UL and DL, the BWPs configured and UE-specific CHBW are all PRB aligned and use the same center frequency
+- the carrier bandwidths for UL and DL (PRB) advertised in SIB1 are either both even or odd, the same applies for the transmission bandwidth configuration of the UE-specific CHBW are both either even or odd for PRB alignment
+- the UE dedicated regular channel bandwidths (MHz) with their corresponding maximum transmission bandwidth configurations (including the larger) are located within the DL and UL carrier bandwidths that may also include blanked PRBs
+
+This would also ensure that the UE-specific CHBW meet the existing conditions for asymmetric bandwidths (Rel-16):
+
+- both center frequency and BWP-ID shall match between DL and UL carriers as defined in 38.331
+- in a case a UE is configured with a full width of BWP within both UL/ DL channels, the center frequency of UL/ DL channels shall be same
+- a position of Point A is common between UL and DL carriers as defined in 38.331
+
+Figure 6.1.2.1.3-1 shows an example of a 55 MHz spectrum block with DL and UL carrier grids of different sizes for SCS = 30k, about 145 PRBs used (not blanked) in the DL. The DL carrier resource grid size of $m_{\text{PRB}} = 189$ PRB corresponds to the next-after-next larger DL bandwidth of 70 MHz, while the UL carrier bandwidth indicated in SIB1 is $m_{\text{PRB}} - 2u = 133$ PRB corresponds to the next smaller bandwidth of 50 MHz with $2u$ the symmetric DL extension (both the UL and DL carrier grids are thus either odd or even sized) also covering blanked PRB. The bandwidth of BWP#0 is equal for the DL and UL and sized 133 PRBs or smaller. Thus legacy UEs only supporting symmetric CHBW can also attach to the cell.
+
+
+
+The diagram shows a horizontal timeline representing a 55 MHz operator block (approx. 145 PRB). Below this, the DL carrier grid is shown as a white bar with orange blocks at the ends, labeled 'DL carrier grid'. To its right, text indicates 'DL: carrierBandwidth = $m_{\text{PRB}} = 189$ PRB'. Below the DL carrier grid is a green bar labeled 'DL CHBW 70 MHz'. To its right, text indicates 'downlinkChannelBW-PerSCS-List: 189 PRB' and 'Same offsetToCarrier w r t SIB1 carrier grid'. Below the DL CHBW is a white bar labeled 'UL carrier grid'. To its right, text indicates 'UL: carrierBandwidth = $m_{\text{PRB}} - 2u = 133$ PRB'. Below the UL carrier grid is a green bar labeled 'UL CHBW 50 MHz (and DL for legacy)'. To its right, text indicates 'uplinkChannelBW-PerSCS-List: 133 PRB'. Below the UL CHBW is a white bar labeled 'UL and DL BWP#0'. To its right, text indicates 'Same center frequency for UL and DL (can be smaller BW)'. At the bottom, a legend shows an orange block labeled 'Blanked PRB' and a vertical dashed line labeled 'Center PRB/frequency'. A note at the bottom left states 'All UL/DL UE dedicated CHBW, BWP and carrier grids PRB aligned and centered'.
+
+Figure 6.1.2.1.3-1: support of a 55 MHz irregular channel block for TDD. The diagram illustrates the alignment of DL and UL carrier grids within a 55 MHz operator block (approx. 145 PRB). The DL carrier grid is 189 PRB wide, and the UL carrier grid is 133 PRB wide. The DL CHBW is 70 MHz, and the UL CHBW is 50 MHz (and DL for legacy). The UL and DL BWP#0 is 133 PRB wide. The diagram shows that all UL/DL UE dedicated CHBW, BWP and carrier grids are PRB aligned and centered. A legend indicates that orange blocks represent blanked PRBs and a vertical dashed line represents the center PRB/frequency.
+
+**Figure 6.1.2.1.3-1: support of a 55 MHz irregular channel block for TDD.**
+
+It is recognised that the restrictions above can imply limitations on the transmission bandwidth configuration of an irregular block (PRBs not blanked) or the irregular spectrum block size supported. However, it suffices that UEs support asymmetric bandwidths for the TDD band, a 50/70 MHz combination for the case above.
+
+The method above also works for TDD bands with a 100k channel raster. The case of an irregular spectrum block at the band edge is described in section 6.1.2.4.
+
+#### 6.1.2.2 Method using Next smaller channel bandwidth is broadcast in SIB1
+
+The gNB broadcasts the DL carrier bandwidth and the bandwidth of the initial BWP (BWP#0) in SIB1. For the 7MHz allocation, SIB1 can indicate DL next smaller standard channel bandwidth, i.e., 5 MHz, and that the initial DL BWP can be set to 25PRBs:
+
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> frequencyInfoDL-> scs-SpecificCarrierList-> carrierBandwidth = 25 PRBs / subcarrierSpacing = 15 kHz
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> initialDownlinkBWP-> genericParameters-> locationAndBandwidth = 25 PRBs
+
+Once the UE established the RRC connection, the gNB can account for the UE capabilities and re-configure the UE accordingly. At this point the gNB will override the carrier bandwidth value that the UE obtained from SIB1 and configure a dedicated BWP with a bandwidth that differs from the bandwidth of BWP#0. For the 7MHz allocation, gNB will override the SIB1 channel bandwidth by 10MHz and configure a larger BWP that will cover the whole 7MHz irregular channel.
+
+- ServingCellConfig-> downlinkChannelBW-PerSCS-List-> carrierBandwidth = 52 PRBs, subcarrierSpacing = 15 kHz
+- ServingCellConfig-> downlinkBWP-ToAddModList-> bwp-Common-> genericParameters-> locationAndBandwidth = 35 PRBs
+
+While not ruled out by the RRC specification, configuration of a UE-specific CHBW wider than the carrier bandwidth indicated by SIB1 and BWPs wider than this resource grid require further consideration and may be subject to UE capability.
+
+It should be noted that BWPs of sizes different from the already defined channel bandwidths are not currently tested within the RAN4 defined requirements. As such, UE behaviour under such configuration is not verified by RAN4 requirements.
+
+The above configuration doesn't consider the PRB grid alignment between SIB1 channel bandwidth and UE configured channel bandwidth based on the 100 kHz channel raster.
+
+#### 6.1.2.3 Further Signalling and configuration aspects: Band Edge
+
+The network only configures channel bandwidth according to UE capabilities. RAN4 requirements do not cover the case when a UE is configured with a channel that is not contained within a specified band. Thus, if the network were to configure the UE channel bandwidth beyond the band edge, then the UE behavior would be unknown.
+
+However, one approach to avoid the unexpected UE behavior is for the NW to ensure that the UE CBW filter will not exceed the NR band edges. This can be achieved as long as the wider CBW is not wider than the NR band. The NW can control the UE CBW filter location near band edges by setting the CRB0 location (within RIV *locationAndBandwidth*) and *carrierBandwidth*. Then the NW can set BWP to utilize the RBs aligned to the left or right edge of the UE carrier bandwidth using $N_{BWP}^{size}$ , etc. In this manner there is no need or the NW to schedule the UE CBW filter outside the NR band edge, potentially leading to unknown UE behaviour. Further channel filter configuration examples can be seen in Section 6.1.3 which show how the NW can avoid setting the UE CBW filter outside the band edge.
+
+For the FDD case with a 7 MHz irregular block at the band edge, the arrangement in Figure 6.1.2.1.2-1 can be modified by shifting the DL carrier grid corresponding to the 15 MHz CHBW upwards by $n \cdot 900$ MHz (5 PRB) as shown in Figure 6.1.2.3-1 such that the 15 MHz CHBW is within the band range thus increasing the BS duplex spacing between the UL and DL carriers while maintaining PRB alignment and the default duplex spacing for the 2 x 5 MHz UE-specific bandwidths and the BWP#0. The default duplex spacing is not specified for the BS (cell) bandwidth and the SIB1 procedure for initial attach is separate for the UL and DL.
+
+
+
+Figure 6.1.2.3-1: FDD case with irregular spectrum block at the band edge. The diagram shows three horizontal spectrum representations. The top one shows a 7 MHz block, a gap labeled 'Default duplex spacing', and another 7 MHz block. Below this, the 'SIB1 carrier grid' is shown with a 15 MHz BS CHBW with a blanked PRB at the edge. Text on the right specifies SIB1 DL: carrierBandwidth = 79 PRB and UL: carrierBandwidth = 25 PRB. The middle section shows 'Legacy UE CHBW' with two 5 MHz blocks, one containing UL BWP#0 and the other DL BWP#0. Text on the right lists 'Legacy UE dedicated CHBW downlinkChannelBW-PerSCS-List: 25 PRB' and 'uplinkChannelBW-PerSCS-List: 25 PRB'. The bottom section shows 'UE supporting asymmetric CHBW' with a 5 MHz block and a 15 MHz block, with a blanked PRB at the 15 MHz edge. Text on the right lists 'UE dedicated asymmetric CHBW downlinkChannelBW-PerSCS-List: 79 PRB' and 'uplinkChannelBW-PerSCS-List: 25 PRB'. A note at the bottom indicates 'Variable duplex spacing (as allowed for the 5 and 15 MHz combination)'.
+
+Figure 6.1.2.3-1: the FDD case with the irregular spectrum block at the band edge.
+
+For the TDD case illustrated in Figure 6.1.2.1.3-2 with a 55 MHz irregular block at the band edge, a common center frequency for all CHBW and BWP can be maintained but with the bandwidths adjusted to optimize the transmission bandwidth configuration of the irregular block (PRBs not blanked) as shown in Figure 6.1.2.3-2. The additional BWP#1 configured for UEs supporting asymmetric bandwidth and the irregular channel bandwidth is also centred with the PRBs at the upper edge blanked. Legacy UEs are configured with the BWP#0 or any other BWP within the 40 MHz block, each additional BWP with common center frequency.
+
+
+
+Figure 6.1.2.3-2: TDD case with the irregular spectrum block at the band edge. The diagram shows a 55 MHz operator block (≈145 PRB) at the top. Below it, the 'DL carrier grid and BWP#1' is shown with a blanked PRB at the right edge. Text on the right specifies DL: carrierBandwidth = m\_PRB = 162 PRB and BWP#1 bandwidth 162 PRB. The next section shows 'DL CHBW 60 MHz' with text 'downlinkChannelBW-PerSCS-List: 162 PRB' and 'Same offsetToCarrier w r t SIB1 carrier grid'. Below that, the 'UL carrier grid' is shown with text 'UL: carrierBandwidth = m\_PRB - 2u = 106 PRB'. The next section shows 'UL CHBW 40 MHz (and DL for legacy)' with text 'uplinkChannelBW-PerSCS-List: 106 PRB'. The bottom section shows 'UL and DL BWP#0' with text 'Same center frequency for UL and DL BWP (can be smaller BW)'. A note at the bottom states 'All UL/DL UE dedicated CHBW, BWP and carrier grids PRB aligned and centered'. A legend at the bottom right shows an orange box for 'Blanked PRB' and a vertical line for 'Center PRB/frequency'.
+
+Figure 6.1.2.3-2: the TDD case with the irregular spectrum block at the band edge.
+
+#### 6.1.2.4 Configuring a UE with a Channel not Fully Contained within the Operating Band
+
+The possibility of configuring a UE with a channel that is not fully contained within the operating band supported by the UE was investigated in the context of using some spectrum allocation in n12 and n85 (See Annex <A>, the case of n12 and n85).
+
+RAN1 and RAN2 specifications are written agnostic to the operating bands and channel placements, hence, the current signaling supports configuring a channel that is not fully contained within the operating band. However, RAN1 and RAN2 clarified during the study that such a configuration was never discussed or analyzed, hence, the UE behavior under such a configuration is unknown.
+
+Current RAN4 requirements are defined under the assumption that the BS and UE channel bandwidths are fully contained within one of the operating bands defined in the specifications. For example, Table 5.4.2.3-1 which defines
+
+the channel raster for each band contains NOTE 1 which states that “The channel numbers that designate carrier frequencies so close to the operating band edges that the carrier extends beyond the operating band edge shall not be used.”
+
+In order to support such a configuration, at least a new UE capability would be needed. Also, in order to ensure that the UEs still meet the necessary requirements (including regulatory) the network would have to limit the RBs used by the UE to those that are confined within the operating band supported by the UE (see also Section 6.1.2.3). The note pointed out in the paragraph above would also have to be updated and any impact to legacy UEs should be avoided.
+
+### 6.1.3 UE channel filters
+
+A typical UE architecture utilises a number of filters of two major types – analogue and digital – and it is generally up to the UE implementation how they are combined. Nevertheless, it is often the case that a UE uses first the wideband analogue filter which typically covers a whole band. In addition to that, a UE may use another NR channel bandwidth specific analogue filter, premise function on which is to filter out non-adjacent blockers. However, since even the NR channel bandwidth specific analogue filter cannot ensure "brick-wall" like filtering, a UE also applies digital filter after ADC to eliminate adjacent interferer. Depending on the UE implementation, the digital filter is a combination of the hardware and software components that allow the UE to apply the corresponding filter coefficients to support a wide range of standard channels, e.g. from 5MHz to 100MHz in case of FR1.
+
+As an example, consider Figure 6.1.3-1. In this example, RBs are scheduled close to the NR band edge. The potential adjacent interferer below the band edge will be removed by the CBW filter with no degradation of ACS at the lower side of the irregular BW since the filters have the same capability as the regular CBW operation.
+
+
+
+Figure 6.1.3-1: Example of the NW utilizing the lower RBs near the NR band edge with BWP. The diagram shows a red 'Blocking Signal' to the left of a 'Band Edge' line. To the right of the band edge, there are green 'Wanted Signal RBs' numbered 0 to 51. A blue dashed line represents the '10MHz UE CBW Filter' which passes the wanted signal and blocks the signal to the left of the band edge.
+
+Figure 6.1.3-1: Example of the NW utilizing the lower RBs near the NR band edge with BWP
+
+However, for the scenario in the Figure 6.1.3-2 the wider channel filter cannot protect against adjacent interferer(s) when the irregular spectrum block is narrower than the channel filter and/or there are adjacent interferers on both sides.
+
+NOTE: for the text above multi-operator scenario can be considered further in this example.
+
+Current specifications do not define how a UE configures its digital filter within the configured channel bandwidth. So, in the provided example below, a UE implementation may configure the digital filter in accordance with the carrier bandwidth "ignoring" the actual smaller bandwidth part size. This is illustrated further in Figure 6.1.3-2. The wanted signal is smaller than 10MHz, but the UE filter is always set to 10MHz as signalled by the network. As can be seen, if there is an adjacent interferer, then it can "leak" into the wanted signal region.
+
+
+
+Figure 6.1.3-2: Possible scenarios for the 10MHz channel filter. The figure shows three scenarios. In the first, a 5 MHz 'Blocking signal' is adjacent to a 10 MHz channel containing a 5.00MHz (25 RBs) wanted signal; the 10 MHz filter passes both. In the second, a 5 MHz 'Blocking signal' is adjacent to a 9 MHz channel containing an 8.25MHz (40 RBs) wanted signal; the 10 MHz filter passes both. In the third, a 5 MHz 'Blocking signal' is adjacent to an 8 MHz channel containing a 5.25MHz (20 RBs) wanted signal; the 10 MHz filter passes both, causing leakage from the blocker.
+
+Figure 6.1.3-2: Possible scenarios for the 10MHz channel filter.
+
+To estimate anticipated performance described in Figure 6.1.3-2 when a UE configures its digital filter according to the channel bandwidth potentially allowing the adjacent interferer to "leak" into the wanted signal area, a series of measurements were conducted using the same testbed and setup as used for the commercial device conformance testing. The adjacent interfering signal is always set in such a way that it is right next to the wanted irregular channel bandwidth signal. Table 6.1.3-1 below summarises adjacent interfering channel parameters used in measurements, where adjacent interferer offset is the offset from the wanted signal center to the adjacent interfering signal center.
+
+**Table 6.1.3-1: Summary of adjacent interfering signal parameters.**
+
+| Irregular channel (MHz) | Effective bandwidth (MHz) | Adjacent interferer offset (MHz) | Adjacent interferer bandwidth (MHz) |
+|-------------------------|---------------------------|----------------------------------|-------------------------------------|
+| 9 | 8.28 | 7 | 5 |
+| 8 | 7.2 | 6.5 | |
+| 7 | 6.3 | 6 | |
+| 6 | 5.22 | 5.5 | |
+
+The following common parameters were applied:
+
+- Center frequency: 1850MHz
+- UE channel: 10MHz
+- Wanted signal level at UE antenna: -82dBm
+- Adjacent interferer level at UE antenna: from -120dBm to -50dBm in step of 1dB
+- Adjacent interferer: 5MHz, 16QAM, SCS 15kHz (3GPP standard ACS test)
+
+Intermediate irregular channel bandwidths are considered – from 9MHz to 6MHz – and the adjacent interferer offset is set accordingly. As the main performance indicator, the resulting SNR is estimated over the whole 10MHz region irrespective of the actual irregular channel size. This approach provides the worst-case estimation of the resulting SNR because in the real life a UE will most likely estimate SNR over the configured bandwidth part corresponding to the irregular channel size or its sub-part.
+
+As can be seen from Figure 6.1.3-3 below, when the adjacent interferer level is low then the estimated SNR is around 39dB for all irregular channels (if the wanted signal is -82dBm and the adjacent interferer is -120dBm, then the theoretical SNR would be around 38dB, but in our case the adjacent interferer is not even fully inside the wanted signal bandwidth). The 9MHz irregular channel bandwidth has same SNR of 39dB even when the adjacent interferer level is same as the wanted signal. SNR degradation starts at the adjacent interferer level of approximately -72dBm, i.e. 10dB higher than the wanted signal. When the adjacent interferer level is 32dB higher than the wanted signal, i.e. -50dBm, the estimated SNR is around 27dB for the 9MHz irregular channel.
+
+As for the opposite extreme case of the 6MHz irregular channel, SNR degradation can be already observed at the adjacent interferer level of around -100dBm, i.e. 18dB lower than the wanted signal. When the adjacent interferer level becomes as high as the wanted signal, the estimated SNR drops down to 27dB. Finally, when the adjacent interferer is 32dB higher than the wanted signal, the SNR becomes -5dB.
+
+These results show the relative degradation in SNR that can occur due to adjacent channel interferers leaking through the next larger BW filter, and the actual performance degradation will depend on a particular scenario, especially ACI strength and the UE channel filter overlap with the interfering signal. Typical 3GPP ACS requirements are conducted so that a UE should be able to meet 95% of the target throughput of the reference QPSK level when the adjacent interferer is 32dB higher than the wanted signal (and which corresponds to approximately -1.5dB SNR). Referring to the right-most point on the X-axis of Figure 6.1.3-3, it can be seen that 9MHz and 8MHz irregular channel SNR is above -1.5dB, while the 6MHz channel SNR is clearly below -1.5dB.
+
+NOTE: The corresponding throughput measurements should be also provided to assess throughput degradation, if any, in the QPSK reference channel.
+
+
+
+Figure 6.1.3-3: A line graph showing Estimated SNR (dB) on the y-axis (ranging from -10 to 45) versus Blocker level (dBm) on the x-axis (ranging from -120 to -50). Four curves are plotted for different channel bandwidths: 9MHz (blue), 8MHz (orange), 7MHz (grey), and 6MHz (yellow). All curves start at an SNR of approximately 39 dB at -120 dBm. As the blocker level increases, the SNR decreases for all bandwidths. The 9MHz curve maintains the highest SNR throughout, while the 6MHz curve drops to the lowest SNR of approximately -5 dB at -50 dBm.
+
+**Figure 6.1.3-3: Estimated SNR depending on the adjacent interferer level.**
+
+To further reduce the risk of ACS reduction, as shown in this second example in Figure 6.1.3-2 and Figure 6.1.3-3, it is possible for new UEs to align their digital filter to the actual smaller bandwidth part within the wider analogue CBW filter bandwidth.
+
+**NOTE:** It is FFS whether it will require new UE capability and/or configuration signalling for the NW to indicate the adjacent interferer location, left, right of the BWP.
+
+## 6.2 Study of overlapping UE channel bandwidths
+
+### 6.2.1 Overlapping UE CBWs from Network Perspective
+
+#### 6.2.1.1 General
+
+One way to utilise the whole chunk of irregular spectrum of a particular size is to combine several overlapping channels of next lower standard channel bandwidth. As an example, Figure 6.2.1.1-1 shows a case when two overlapping 10MHz carriers cover 13MHz channel bandwidth. From an individual UE perspective, each UE is configured with existing immediately lower channel bandwidth following legacy procedures and signalling: one UE can use the first 10MHz carrier, while another UE can use another carrier. In fact, both UEs can use overlapping part of the spectrum provided that the BS takes care that the overlapping region is allocated to one particular carrier at a time. It should be also noted that from the UE perspective, an existing immediately lower channel bandwidth will be always used, either for initial access (as the channel bandwidth advertised by the network) or as a dedicated channel bandwidth configured by RRC. From the network perspective, the BS will/can use the whole irregular channel bandwidth.
+
+
+
+Figure 6.2.1.1-1: A diagram illustrating the use of overlapping carriers. At the top, a grey bar represents a 13 MHz channel bandwidth. Below it, a green bar represents a 10 MHz carrier. At the bottom, a red bar represents another 10 MHz carrier. The green and red bars overlap in the center, and their combined width covers the 13 MHz bandwidth of the top bar. Arrows above each bar indicate their respective widths: 13 MHz for the top bar, 10 MHz for the green bar, and 10 MHz for the red bar.
+
+**Figure 6.2.1.1-1: Using overlapping carriers (example for 13MHz).**
+
+It is worth noting that overall capacity of the cell will be according to the irregular channel bandwidth because the BS can use the full bandwidth. However, since a particular UE will use only one carrier of a smaller bandwidth within the irregular channel bandwidth, the maximum throughput for a single UE will be less than the theoretically possible within the spectrum in case there is only a single UE in the cell. Nevertheless, since there will be multiple UEs in the cell the overall system throughput will not decrease.
+
+#### 6.2.1.2 Detailed description
+
+One of the challenges associated with configuring overlapping carriers for the same frequency allocation is that both carriers should have aligned grid so that the BS can perform same FFT and schedule resources in the overlapping region.
+
+While aligning RB grids is not an issue for bands above 3GHz that have the SCS based raster, it becomes more challenging for the sub-3GHz band that have 100kHz raster. As a result, carriers can be configured on raster points that correspond to the least common multiple of the channel raster and the RB size. As an example, the least common multiple will be 900kHz in case of the 15kHz SCS, which corresponds to 5RBs. It effectively means that overlapping carriers will not be able to address efficiently any irregular spectrum size and in some case maybe will not be applicable at all. Of course one way to improve spectrum utilisation is to allow shifting carriers in multiples of 1RB, but that will require introduction of new raster points, which will not be supported by legacy UEs.
+
+Figure 6.2.1.2-1 presents an example for the 6MHz channel comprising two 5MHz channels. As can be seen from the figure, centre frequency distance between carriers is 900kHz, which is a multiple of 100kHz channel raster and 180kHz RB size. From an individual UE perspective, it is just a normal 5MHz carrier comprising 25RBs and having the 5MHz channel guard bands. From the BS perspective, it is a 6MHz channel with 30RBs. Figure 6.2.1.2-2 exemplifies how this approach can be used to support the 7MHz irregular channel bandwidth, in which the distance between the carriers is 1800kHz. Finally, Figure 6.2.1.2-3 shows the 11MHz channel that is supported with two 10MHz channels. Referring to Figure 6.2.1.2-1, 6.2.1.2-2 and 6.2.1.2-3, it should be noted that guard bands will not necessarily be symmetrical and the exact guard band size will depend on a particular spectrum allocation, its size, and how the overlapping channels are placed.
+
+
+
+The diagram illustrates two overlapping 5MHz carriers within a 6MHz channel. The top carrier is labeled '5.4 MHz' and the bottom carrier is labeled '5.5 MHz'. Both carriers consist of 25 Resource Blocks (RBs), numbered 0 to 24. The distance between the center frequencies of the two carriers is 900 kHz. The overall channel width is 6 MHz. The RB grids are aligned, with the 5.5 MHz carrier shifted by 5 RBs (900 kHz) relative to the 5.4 MHz carrier.
+
+Figure 6.2.1.2-1: Detailed overview of overlapping carriers (6MHz channel with 5MHz carriers).
+
+Figure 6.2.1.2-1: Detailed overview of overlapping carriers (6MHz channel with 5MHz carriers).
+
+
+
+The diagram illustrates two overlapping 5MHz carriers within a 7MHz channel. The top carrier is labeled '5.3 MHz' and the bottom carrier is labeled '5.7 MHz'. Both carriers consist of 25 Resource Blocks (RBs), numbered 0 to 24. The distance between the center frequencies of the two carriers is 1800 kHz. The overall channel width is 7 MHz. The RB grids are aligned, with the 5.7 MHz carrier shifted by 10 RBs (1800 kHz) relative to the 5.3 MHz carrier.
+
+Figure 6.2.1.2-2: Detailed overview of overlapping carriers (7MHz channel with 5MHz carriers).
+
+Figure 6.2.1.2-2: Detailed overview of overlapping carriers (7MHz channel with 5MHz carriers).
+
+
+
+The diagram illustrates two overlapping 10MHz carriers within an 11MHz channel. The top carrier is labeled '10.25 MHz' and the bottom carrier is labeled '10.75 MHz'. The top carrier consists of 51 Resource Blocks (RBs), numbered 0 to 50. The bottom carrier consists of 25 Resource Blocks (RBs), numbered 0 to 24. The distance between the center frequencies of the two carriers is 900 kHz. The overall channel width is 11 MHz. The RB grids are aligned, with the 10.75 MHz carrier shifted by 5 RBs (900 kHz) relative to the 10.25 MHz carrier.
+
+Figure 6.2.1.2-3: Detailed overview of overlapping carriers (11MHz channel with 10MHz carriers).
+
+Figure 6.2.1.2-3: Detailed overview of overlapping carriers (11MHz channel with 10MHz carriers).
+
+Table 6.2.1.2-1 below summarises potential number of schedulable RBs for a scenario when the next smaller overlapping channels are used. To calculate them, it is assumed that distance between individual carriers is a multiple of 900kHz and that the resulting guard bands must meet at least next smaller channel requirements. So, "Channel Nrb", and "Utilisation" represent the network view, while from the UE perspective all the parameters are the same as for the next smaller channel.
+
+**Table 6.2.1.2-1: Exemplary number of RBs based on the next smaller overlapping channel (15kHz SCS).**
+
+| Channel (MHz) | Next smaller channel (MHz) | Next smaller channel guard band (kHz) | Next smaller channel Nrb | Channel Nrb | Utilisation (%) |
+|---------------|----------------------------|---------------------------------------|--------------------------|-------------|-----------------|
+| 6 | 5 | 242,5 | 25 | 30 | 90 |
+| 7 | 5 | 242,5 | 25 | 35 | 90 |
+| 11 | 10 | 312,5 | 52 | 57 | 93,3 |
+| 12 | 10 | 312,5 | 52 | 62 | 93 |
+| 13 | 10 | 312,5 | 52 | 67 | 92,8 |
+
+Table 6.2.1.2-2 presents similar calculations for the number of available RBs with overlapping carriers, but for the 30kHz SCS. As can be seen from the table, a solution based on the 30kHz SCS overlapping carriers does not provide a good spectral utilisation for certain non-standard channel bandwidths due to the reason that the "distance" between carriers raster points must be a multiple of 1800kHz. Because of that, channel bandwidths such as 7 and 12MHz have more or less good utilisation, whereas 6 and 11MHz do not provide any benefit at all.
+
+**Table 6.2.1.2-2: Exemplary number of RBs based on the next smaller overlapping channel (30kHz SCS).**
+
+| Channel (MHz) | Next smaller channel (MHz) | Next smaller channel guard band (kHz) | Next smaller channel Nrb | Channel Nrb | Utilisation (%) |
+|---------------|----------------------------|---------------------------------------|--------------------------|-------------|-----------------|
+| 6 | 5 | 505 | 11 | 11 | 66 |
+| 7 | 5 | 505 | 11 | 16 | 82,3 |
+| 11 | 10 | 665 | 24 | 24 | 78,5 |
+| 12 | 10 | 665 | 24 | 29 | 87 |
+| 13 | 10 | 665 | 24 | 29 | 80,3 |
+
+To support two overlapping carriers, the network can consider using one or two SSBs. To be more precise, since the SSB bandwidth is 3.6MHz and the CORESET#0 bandwidth is 4.32MHz, a single SSB/CORESET#0 can be placed into a common part between two overlapping channels. However, this approach works only if the overlapping part is at least 4.32MHz, e.g. it is not applicable to irregular channels smaller than 10MHz. So, some irregular channel bandwidth will need two SSB/CORESET#0. In this case, at least for irregular channel bandwidths smaller than 10MHz the network broadcasts two separate SSBs, one for each overlapping regular carrier. If a particular irregular channel bandwidth does not allow for placing two SSBs in the same time slots, then the network will have to ensure that they are "multiplexed" accordingly in the time domain.
+
+NOTE: It may create the challenge of aligning SSBs in the time and frequency domain so that they do not overlap thus complicating the gNB scheduling, i.e. for this approach complexity increases to coordinate the overlapping SSBs for different UEs.
+
+From the RAN2 specifications perspective, a single cell has a single cell-defining SSB, the channel bandwidth configuration broadcast in SIB1, CORESET#0, and the initial BWP. Thus, a single "common" SSB for two overlapping channels will effectively define only one of the overlapping channels as perceived by the UE (refer to sub-clause 6.2.1.3 for more information on configuration and signalling aspects with one and two SSBs).
+
+NOTE: It is up to the network implementation whether to configure two SSBs for overlapping channels or one "common" SSB if the overlapping part is large enough (refer to Table 6.2.1.2-3).
+
+**Table 6.2.1.2-3: Summary of how many SSB/CORESET#0 needed for different channel bandwidths.**
+
+| Channel (MHz) | Number of SSB/CORESET#0 | Time multiplexing for 2 SSBs is needed |
+|---------------|-------------------------|----------------------------------------|
+| 6 | 2 | yes |
+| 7 | 2 | yes |
+| 11 | 1 or 2 | no |
+| 12 | 1 or 2 | no |
+| 13 | 1 or 2 | no |
+
+Figure 6.2.1.2-5 shows an example for the 13MHz irregular channel with a single/common SSB configured in the overlapping part of two 10MHz carriers.
+
+
+
+Diagram illustrating the configuration of overlapping carriers with a single overlapping SSB for a 13MHz channel. The diagram shows a horizontal axis representing frequency. At the top, a double-headed arrow labeled '(BS) carrierBandwidth' spans the entire width. Below it, another double-headed arrow labeled 'Block size (e.g. 13 MHz)' also spans the entire width. A solid grey rectangle represents the base station channel. Below this, two dashed rectangles represent 'UE dedicated CHBW (contains BWP#1)' and 'UE dedicated CHBW (contains BWP#2)'. At the bottom, a solid grey rectangle represents the 'Initial BWP (BWP#0)'. The Initial BWP is shown as a subset of the UE dedicated CHBWs, which are themselves subsets of the base station carrier bandwidth.
+
+**Figure 6.2.1.2-4: Using overlapping carriers with single overlapping SSB (example for 13MHz).**
+
+#### 6.2.1.3 Configuration and signalling aspects
+
+Since from an individual UE perspective each overlapping carrier is just a legacy channel bandwidth, the existing signalling applies. As an example, for the 7MHz allocation the UE can be configured with the 5MHz channel bandwidth, and the initial bandwidth part can be also 5MHz.
+
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> frequencyInfoDL-> scs-SpecificCarrierList-> carrierBandwidth = 25 PRBs / subcarrierSpacing = 15 kHz
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> initialDownlinkBWP-> genericParameters-> locationAndBandwidth = 25 PRBs
+
+If the network configures two SSBs for an overlapping channel, then from the UE perspective each overlapping channel is perceived as an independent cell and a UE can camp on each cell following the existing cell (re-)selection procedures. If the network configures one "common" SSB, then from the UE perspective only one of the overlapping channels is perceived as a cell and some UEs will be re-configured with a dedicated channel bandwidth to another overlapping channel.
+
+NOTE: From the signalling perspective, it is possible to override the SIB1 channel bandwidth by the dedicated channel bandwidth signalling in the RRC\_CONNECTED state.
+
+#### 6.2.1.4 Channel raster handling
+
+The UE channel BWs have to be backwards compatible such that this scheme works for existing UEs, hence, they would have to be deployed on the 100kHz raster used in the low FR1 bands. As such, the UE channels have to be deployed at a distance which is a multiple of 900kHz (common denominator between the RB size of 180kHz and 100kHz channel raster granularity).
+
+The base station channel encompasses the overlapping UE channels. In the case that the distance between the UE channel centers is an even multiple of 900kHz, the center of the base station channel will also fall on a 100kHz multiple. In the case of an odd 900kHz multiple, the center of the base station transmission bandwidth configuration would fall in the middle of the 900kHz interval between the overlapping UE channel centers. This might require some additional specification work for BS.
+
+### 6.2.2 Combined UE CBW (one cell)
+
+#### 6.2.2.1 General Aspects
+
+- Studied spectrum blocks covered by "main RF carrier" and "additional RF carrier"
+- The "main RF carrier" is Rel-15 compatible and contains the SSB as well as all necessary broadcast information, legacy UEs and UEs which do not support this solution are able to camp on it and be connected without being aware of the "additional RF carrier"
+
+- The “additional RF carrier”, which is partially overlapping with the “main RF carrier”, is aligned to the “main RF carrier” PRB grid and utilizes further PRBs that fit in relevant spectrum block. UEs which support this solution would be reconfigured (once UE capabilities are known) in RRC\_CONNECTED to use wider CBW and BWP than used for initial access.
+- The “main RF carrier” and the “additional RF carrier” are treated as single cell (one carrier from baseband perspective) to allow for a single BWP to cover studied spectrum block in RRC\_CONNECTED
+- Both the “main RF carrier” and the “additional RF carrier” would clearly define the size and position of the guard band which allows for an unambiguous placement of the overlapping channel filters and thus prevents problems with OBUE, ACS or in-band blocking
+- From UE perspective, supported in downlink only
+
+#### 6.2.2.2 Signalling and configuration aspects
+
+In this section we provide further signaling details on how to support irregular channels given the 7MHz allocation as an example.
+
+The gNB broadcasts the DL carrier bandwidth and the bandwidth of the initial BWP (BWP#0) in SIB1. For the 7MHz allocation, SIB1 would indicate DL standard channel bandwidth (i.e. 5 MHz), the initial DL BWP would be set to 5 MHz to accommodate legacy and new UEs:
+
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> frequencyInfoDL-> scs-SpecificCarrierList-> carrierBandwidth = 25 PRBs / subcarrierSpacing = 15 kHz
+
+- SIB1-> servingCellConfigCommon-> downlinkConfigCommon-> initialDownlinkBWP-> genericParameters-> locationAndBandwidth = 25 PRBs
+
+Once the UE established the RRC connection, the gNB can account for the UE capabilities and re-configure the UE accordingly. At this point the gNB may override the carrier bandwidth value that the UE obtained from SIB1 and configure a dedicated BWP with a bandwidth that differs from the bandwidth of BWP#0. gNB may configure a larger bandwidth part that will cover the whole 7MHz allocation.
+
+- ServingCellConfig-> downlinkChannelBW-PerSCS-List-> carrierBandwidth = 36 PRBs, subcarrierSpacing = 15 kHz
+
+- ServingCellConfig-> downlinkBWP-ToAddModList-> bwp-Common-> genericParameters-> locationAndBandwidth = 36 PRBs
+
+It should be noted that 36 PRBs do not correspond to any channel bandwidth currently defined in TS 38.101-1.
+
+It is possible from signalling point of view to override the SIB1 channel bandwidth by the dedicated channel bandwidth signalling in RRC\_CONNECTED if the UE is capable of the dedicated channel bandwidth, and if the network ensures the SIB1 channel bandwidth and dedicated channel bandwidth use the same PRB grid. New capability might be needed to support such configuration [3].
+
+#### 6.2.2.3 UE architecture aspects
+
+With respect to the UE architecture, the following assumptions are made (according to SID objectives):
+
+- New (dedicated) channel filters (e.g. non-integer-multiples of 5 MHz) are not considered
+- UEs not supporting this solution (both legacy and new UEs) should be able to use the next lower supported channel bandwidth in the UL and DL without implications
+
+Two different UE architecture scenarios are explained (legacy UEs using next smaller bandwidth in section 6.6.2 and UEs supporting two receive chains for reception described below):
+
+This option is for new UEs that contain transceiver architectures and configurations that have flexibility in local oscillator and receive chain assignments. The flexibility in the configuration allows the UEs to configure their receive paths (Antenna to FFT) similarly to non-contiguous carrier aggregation, allowing the two LO and receive chains to down-convert the spectrum of the irregular bandwidth as if it consisted of two separate carriers on the UE side. Based on the channel center of the main RF carrier and the configured irregular bandwidth, the UE would know where to place the center frequency of the additional RF carrier that follows the PRB grid (which overlaps with the main RF carrier and includes the remaining agreed PRBs for the irregular BW). The UE down-converts two different sets of PRBs, with an overlapping segment and may use for irregular bandwidth below 15MHz the next smaller bandwidth channel filtering on both of the receive chains as shown in Figure 6.2.2.3-1 (“DigRF” serves as an example only and corresponds to the interface between RF and baseband chipset). This allows the UE to benefit from channel filtering designed for the specific bandwidth. Using the next smaller bandwidth channel filtering on both of the two carrier parts, the baseband signal processing following the FFTs must be modified such that the signals from these two carrier parts are combined and processed as a single codeword instead of being process separately. Since the LOs on the UE will operate at different frequencies, there will be a phase difference of the two signals contained in the two receive chains for the separate carriers.
+
+In order to prevent problems in the channel estimation if there is an averaging or interpolation across reference signals at different subcarriers, the phases of the symbols in the frequency domain from both RF receive chains caused by the UE's use of separate LOs should be aligned. This can be achieved by a new function comparing the overlapping symbols from both FFT outputs and phase shifting one FFT output accordingly before the FFT outputs are merged.
+
+
+
+The diagram shows the UE architecture for full BW support. It is divided into three main sections: Baseband, Transceiver, and FEM/Tuner. The Baseband section contains a 'Combiner (New)' block with three FFT outputs. The Transceiver section is split into two receive chains. The top chain consists of a DAC, a mixer, and a filter, followed by a 'DigRF' interface. The bottom chain consists of an ADC, a mixer, and a filter, also followed by a 'DigRF' interface. The FEM and Tuner are connected to the Transceiver. The Tuner output shows two possible configurations: 'Contiguous CA' and 'Non contiguous CA'. A legend on the left shows '1 RF- or component carrier per receive chain' with 'irregular BW' (RF carrier 1 and RF carrier 2), 'Contiguous CA' (CC1 and CC2), and 'Non contiguous CA' (CC1 and CC2). A note indicates 'Same split as used in L-L CA, Intra and NonC Intra Band CA'.
+
+Figure 6.2.2.3-1: UE architecture for full BW support showing split by the use of two LOs. The diagram illustrates the signal flow from the Baseband to the Transceiver and then to the FEM and Tuner. The Baseband contains a 'Combiner (New)' with three FFT outputs. The Transceiver is split into two receive chains. The top chain uses a DAC and a mixer to down-convert RF carrier 1. The bottom chain uses an ADC and a mixer to down-convert RF carrier 2. Both chains then pass through a 'DigRF' interface. The FEM and Tuner are connected to the Transceiver. The Tuner output shows two possible configurations: 'Contiguous CA' and 'Non contiguous CA'. The diagram also includes a legend for '1 RF- or component carrier per receive chain' showing 'irregular BW' (RF carrier 1 and RF carrier 2), 'Contiguous CA' (CC1 and CC2), and 'Non contiguous CA' (CC1 and CC2). A note indicates 'Same split as used in L-L CA, Intra and NonC Intra Band CA'.
+
+Figure 6.2.2.3-1: UE architecture for full BW support showing split by the use of two LOs
+
+Depending on the receiver architecture and the distribution of the channel filtering between the analogue and the digital domain, it is also possible to A/D convert a frequency range that accommodates the entire irregular BW and to split the signal afterwards by means of NCOs (instead of LOs) into the 2 RF carriers with their individual channel filter positions as shown in Figure 6.2.2.3-2.
+
+
+
+Figure 6.2.2.3-2: UE architecture for full BW support showing split by the use of NCOs. The diagram shows a Baseband unit connected to a Transceiver, which is connected to an FEM and a Tuner. The Baseband unit contains a 'Combiner (New)' and 'FFT' blocks. The Transceiver contains 'DigRF' blocks with 'DAC' and 'ADC' components. A note indicates 'Use of NCOs in ADC to split the signal into two receive chains on the standardized interface'. The output of the Transceiver is split into two receive chains. The first chain shows '1 RF- or component carrier per receive chain' with 'irregular BW' (RF carrier 1 and RF carrier 2). The second chain shows 'Contiguous CA' (CC1 and CC2) and 'Non contiguous CA' (CC1 and CC2). The FEM and Tuner are connected to an antenna. A note indicates 'Depending on bands' for the FEM and Tuner. The Tuner output shows 'Contiguous CA' and 'Non contiguous CA' represented by green blocks.
+
+Figure 6.2.2.3-2: UE architecture for full BW support showing split by the use of NCOs
+
+### 6.2.3 Overlapping CA (two cells)
+
+#### 6.2.3.1 General Aspects
+
+Using the Overlapping CA approach to support irregular spectrum is one of the methods without the need of introduction of new dedicated channel bandwidths for both UE and BS. Figure 6.2.3-1 shows overlapping CA from network perspective, in which BS supports the intra-band overlapping CA, while UEs only supports the single CC with the existing channel bandwidth. And figure 6.2.3-2 shows overlapping CA from UE perspective, in which both BS and UE support the intra-band overlapping CA to use all RBs, and the UE supports intra-band non-contiguous CA for the combination as well.
+
+Even two CCs are overlapped in frequency domain, the network can configure different CCs with non-overlapping BWP to avoid the conflict of physical signals or channels.
+
+
+
+Figure 6.2.3-1: Overlapping CA from network perspective. The diagram shows three horizontal bars representing bandwidths. The top bar is green and labeled 'Overlapping CA for gNB'. The middle bar is blue and labeled 'UE1: legacy channel bandwidth'. The bottom bar is blue and labeled 'UE2: legacy channel bandwidth'. The bars are aligned such that the blue bars are subsets of the green bar, indicating overlapping in the frequency domain.
+
+Figure 6.2.3-1: Overlapping CA from network perspective
+
+
+
+Diagram illustrating Overlapping CA from UE perspective. It shows four horizontal bars representing different channel configurations. The top bar is a green bar labeled 'Overlapping CA for gNB'. The second bar is a blue bar labeled 'UE3: overlapping CA of CC1 and CC2'. The third bar is a grey bar labeled 'CC1: BWP#1' with a dashed blue outline. The fourth bar is a grey bar labeled 'CC2: BWP#2' with a dashed blue outline. The bars are stacked vertically, with the top two bars being wider than the bottom two, which are partially overlapping each other.
+
+**Figure 6.2.3-2: Overlapping CA from UE perspective**
+
+In summary,
+
+- No new gNB channel bandwidth is required
+- Legacy UE using existing lower regular NR channel bandwidth can operate in either carrier
+- Overlapping CA approach needs to have PRB grid alignment between overlapping CCs
+- From UE perspective, overlapping CA is optional supported in DL only
+- Irregular bandwidth utilizing overlapping CA approach cannot be combined with NR CA combinations
+- From UE perspective, the solution requires UE support of intra-band non-contiguous CA for the combination
+
+#### 6.2.3.2 Configuration and signalling aspects
+
+In this approach, network configures two cell-defining SSB in the allocated irregular spectrum block and the two cells are configured with overlapping regular channel bandwidth. From procedure wise, the network can indicate UE the location and bandwidth by using the existing procedures on individual CC. From UE perspective, there are two independent cells with overlapped bandwidth. For a particular UE, CA with overlapped cells can be configured to fully utilize the network bandwidth.
+
+## 6.3 Complexity and efficiency study
+
+### 6.3.1 Larger Channel BW than licensed BW
+
+UE needs to support the asymmetric bandwidth combinations where UL CBW is SmallerCBW and DL CBW is WiderCBW. The asymmetric UL and DL channel bandwidth combination set should be specified in the specification TS 38.101-1.
+
+### 6.3.2 Overlapping UE CBW from Network Perspective
+
+gNB has to support the irregular channel BW. It is up to the network implementation how it can be implemented, e.g. through a new channel bandwidth, or through RF combining of 2 existing regular channel bandwidths.
+
+### 6.3.3 Combined UE CBW (one cell)
+
+- Does not require new channel filters for UE and gNB to be designed and tested
+- Requires support of two RF carriers phase aligned on the Tx side to ensure phase continuity on the Rx side
+- Requires split of the irregular bandwidth into two sets of PRBs that may be filtered through the next smaller bandwidth after which the signal is combined at the receiver's baseband as a single carrier. For such processing, UE may benefit from supporting intra-band non-contiguous CA.
+
+- Requires UE architecture with capability to split LNA output signal to two separate LO paths for down-conversion. Also requires UE architecture with the ability to combine baseband signals.
+- Possible UE architecture alternative to requiring a split LNA, is to use an ADC with a large dynamic range and a subsequent split of the digital signal in two paths with separate NCOs and digital channel filters. Also requires UE architecture with the ability to combine baseband signals.
+- For scenarios with less than 10 MHz, second SSB is not excluded but not recommended due to significant additional overhead (duplicated SSB transmission as well as other radio resources such as PDCCH, CSI-RS, PDSCH (for SIB), CSI for Tracking, etc.). However, second SSB could enable or improve the legacy UEs' use of the further PRBs provided by the additional RF carrier in spectrum scenarios with less than 10 MHz.
+- "Additional RF carrier" not to be on the channel raster to increase spectrum utilization (up to 2 PRBs), it should be noted that the complete "additional RF carrier" is used only by UEs which support this solution "additional RF carrier" can be used partially (with up to 2 PRBs not available) by legacy UEs which are on the channel raster.
+- Proposed BWPs size of the irregular spectrum chunk may have an impact on performance requirements and additional testing
+- High spectrum utilization:
+ - due to low internal guard band. The spectrum utilization values in the table below use guard band values according to the minimum guard bands defined for the smallest possible channel bandwidths that could be theoretically considered as part of each combined UE CBW. The actual minimum guard band requirements for combined UE CBW configurations would require further discussion in any follow-up WI.
+ - as well as no additional CA overhead (duplicated common channels and signals such as SSB, PDCCH and CSI-RS configured both in Pcell and Scell, in addition of the MAC processes associated with CA) due to single baseband carrier usage:
+
+**Table 6.3.3-1: spectrum utilization**
+
+| <b>Spectrum block [MHz]</b> | <b>Number of PRBs (15kHz SCS without 100kHz raster alignment)</b> | <b>Spectrum utilization for new UE (without 100kHz raster alignment) [%]</b> | <b>Number of PRBs (15kHz SCS with 100kHz raster alignment)</b> | <b>Spectrum utilization for new UE (with 100kHz raster alignment) [%]</b> |
+|-----------------------------|-------------------------------------------------------------------|------------------------------------------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------|
+| 6 | 30 | 90 | 30 | 90 |
+| 7 | 36 | 92.6 | 35 | 90 |
+| 11 | 58 | 94.9 | 57 | 93.3 |
+| 12 | 63 | 94.5 | 62 | 93 |
+| 13 | 69 | 95.5 | 67 | 92.8 |
+
+### 6.3.4 Overlapping CA (two cells)
+
+From network perspective:
+
+For gNB, no new filter for RF channel is needed. The CA implementation can be reused. The only update is to allow the configuration that the two carriers can be partially overlapped by adjusting the channel spacing. The network can prevent collisions between the two component carriers.
+
+For UE, there is no impact and fully backwards compatible.
+
+From UE perspective:
+
+For gNB, the two RF carriers aggregated by the UE would need to be time-aligned by the gNB to at least the same level required for existing intra-band contiguous CA (TS 38.104 Timing Adjustment Error) to allow UE reception. It is FFS as to whether finer timing alignment would be required.
+
+For UE, it is optional support in DL only. For the UE supports DL intra-band non-contiguous CA with corresponding channel bandwidth(s), overlapping CA can be considered by support the configuration with partially overlapping carriers. And in the case no new channel filter for UE is needed.
+
+For overlapping CA solution, the legacy channel bandwidth should be supported, hence the minimum guardband should not be less than the minimum guardband of lower UE channel bandwidth than operator licensed bandwidth. To support legacy UEs, channel raster should be applied for each UE channels. And in order to simplify the resource schedule and make the use of single SSB (for irregular bandwidths larger than 10MHz) for CA operation, RB alignment is required. Table 6.3.4-1 shows the channel spacing and spectrum utilization for the example channel bandwidths assuming symmetric CA channel bandwidth.
+
+**Table 6.3.4-1: channel spacing and spectrum utilization**
+
+| Irregular Bandwidth(MHz) | SCS(kHz) | CA combos | Nominal channel spacing (MHz) | Transmission bandwidth configuration NRB | Spectrum utilization (%) |
+|--------------------------|----------|-----------|-------------------------------|------------------------------------------|--------------------------|
+| 6 | 15 | 5+5 | 0.9 | 30 | 90 |
+| 7 | 15 | 5+5 | 1.8 | 35 | 90 |
+| 11 | 15 | 10+10 | 0.9 | 57 | 93.3 |
+| 12 | 15 | 10+10 | 1.8 | 62 | 93 |
+| 13 | 15 | 10+10 | 2.7 | 67 | 92.8 |
+
+## 6.4 Generic solutions guidance
+
+### 6.4.1 Larger Channel BW than licensed BW
+
+Does not require new channel filters for UE to be designed and tested.
+
+### 6.4.2 Overlapping UE CBW from Network Perspective
+
+This approach can be also be applied to all irregular channel bandwidths with only consideration of different spectral utilization considerations. However the single CORESET#0 and SSB is only applicable for bandwidths greater than 10 MHz. For all irregular channel bandwidths two SSBs can be used (in irregular channel bandwidths < 10 MHz SSB can be TDM).
+
+Does not require new channel filters for UE to be designed and tested.
+
+### 6.4.3 Combined UE CBW (one cell)
+
+- Given the availability of a new UE with the required architecture, a future proof solution, the channel bandwidth can be tailored with the resolution of 1PRB. Able to support any irregular channel bandwidth even to the band edge.
+- Ensured co-existence with very limited specification impact since both the “main RF carrier” and the “additional RF carrier” and the separate signal processing paths before the equalization would conform to existing 3GPP requirements
+- Does not require new channel filters for UE and gNB to be designed and tested
+
+### 6.4.4 Combined UE CBW (two cell)
+
+This approach can be applied to various size of irregular channel bandwidths, and it does not require to define new channel filters to be designed and tested for BS and UE.
+
+Does not require new channel filters for UE to be designed and tested.
+
+## 6.5 RAN1 and RAN2 impact
+
+### 6.5.1 Larger Channel BW than licensed BW
+
+For TDD bands RAN1 requires that the active UL and DL BWP pair must have the same centre frequency.
+
+### 6.5.2 Void
+
+### 6.5.3 Void
+
+### 6.5.4 Combined UE CBW (two cells)
+
+CSI-RS measurement and reporting for the component carriers are specified in TS 38.213 and to be performed independently per-carrier, similarly for PDCCH. It is up to the gNB scheduler to avoid collisions of different transmissions for the overlapping part with overlapping CA cross-carrier scheduling.
+
+Existing UE capability signalling does not provide any possibility for UE to indicate support of overlapped CA. New signalling would be required in order for this approach to become feasible.
+
+## 6.6 Legacy UE impact
+
+### 6.6.1 Void
+
+### 6.6.2 Overlapping UE CBW from Network Perspective
+
+Overlapping channels from the network perspective works with all the legacy UEs. As presented in previous sub-clauses, from an individual UE perspective, this is just a standard Rel-15 channel and no special UE side enhancements are needed. Thus an operator can use this solution with the whole ecosystem of available devices.
+
+### 6.6.3 Combined UE CBW (one cell)
+
+- No impact to legacy UEs. UEs which support this solution would be reconfigured in RRC\_CONNECTED, there is no change to UE behaviour in IDLE mode which could create potential issue with legacy UE compatibility
+
+This option is for UEs that have no support for using an irregular bandwidth. Such a UE will apply the next smaller bandwidth referring to the channel filtering. It will never receive more than the PRBs defined for the next smaller bandwidth and it follows the conventional way of aligning the center frequency of the channel in both DL and UL. These UEs will camp on the same frequency part of the channel since the SIB1 only has one allocation. In CONNECTED mode, the network can configure UE with the UE specific *ServingCellConfig* IE which configures the point A reference that may shift the UE to operate either at the lower side or the upper side of the irregular bandwidth. In most of the configurations with an irregular BW below 10 MHz, legacy UEs can only use one side of the irregular BW unless – as in the case of overlapping CBWs from network perspective – a second, time-staggered SSB is spent.
+
+
+
+Figure 6.6.3-1: Legacy UE may be configured for either of the two carriers. The diagram shows three horizontal bars representing frequency bands. The top bar is grey and labeled '13 MHz'. The middle bar is green and labeled '10 MHz'. The bottom bar is red and labeled '10 MHz'. The green and red bars are aligned at their left edges, indicating they are configured for different carriers within the same frequency range.
+
+Figure 6.6.3-1: Legacy UE may be configured for either of the two carriers
+
+### 6.6.4 Overlapping CA (two cells)
+
+This approach works with legacy UEs in single carrier operation. It is unclear whether legacy UEs would support a CA configuration or UE behavior is undefined with overlapping channel bandwidths as this has not been discussed in RAN2 when designing current UE capabilities and therefore do not consider any frequency overlap in the CA case. Current channel spacing in RAN4 does not assume overlapping carriers so RAN4 specs do not support overlapping CA.
+
+## 6.7 RAN4 standard impact identification
+
+### 6.7.1 Larger Channel BW than licensed BW
+
+UE asymmetric bandwidth combinations for the corresponding spectrum scenarios are needed, handled on band by band basis or by generic requirement.
+
+### 6.7.2 Combined UE CBW (one cell)
+
+Overall impact limited since both the “main RF carrier” and the “additional RF carrier” would conform to existing 3GPP requirements, to guarantee co-existence
+
+### 6.7.3 Overlapping CA (two cells)
+
+The CA framework defines the transmitter emission and receiver blocking at the edge of carriers. Limited impacted is expected to enable coexistence with neighbouring channels for this scenario. Overlapping CA channel spacing need to be updated to consider channel raster, minimum guard band and RB alignment.
+
+For 15 KHz SCS and 100 KHz channel raster,
+
+$$\text{Channel spacing} = \left\lceil \frac{2 * BW - (BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})}{1.8} \right\rceil 0.9 \text{ (MHz)}$$
+
+For NR operating bands with 15 kHz channel raster,
+
+$$\text{Channel spacing} = \left\lceil \frac{2 * BW - (BW_{\text{Channel}(1)} + BW_{\text{Channel}(2)})}{0.18 * 2^{n+1}} \right\rceil 0.18 * 2^n \text{ (MHz)}$$
+
+with
+
+$$n = \mu_0$$
+
+Where BW is the bandwidth not aligned with the existing NR channel bandwidths, $BW_{\text{Channel}(1)}$ and $BW_{\text{Channel}(2)}$ are channel bandwidths of the overlapping carriers respectively.
+
+For overlapping CA approach, the only difference compared to normal CA is that overlapping CA can further adjust the channel spacing to fit the irregular spectrum. Hence gNB supporting the corresponding normal CA could also meet the
+
+existing unwanted emission and ACS requirement when operating in overlapping CA case and no need to redo Base Station conformance testing.
+
+### 6.7.4 Overlapping UE CBWs from Network Perspective
+
+The required guard band is based on the next smaller channel bandwidth for the legacy UE. Hence BS can use the same implementation as overlapping CA, i.e. to use two existing BS filters (other implementations are not excluded). If manufacturer declares to use two existing filter implementation, and gNB supports the corresponding normal CA, the gNB could also meet the existing unwanted emission and ACS requirement and hence no need to redo conformance testing.
+
+### 6.7.5 Dedicated BS channel bandwidths
+
+If the irregular channel bandwidths are explicitly defined in the specification, it will create huge technical specification work. For each channel bandwidth, the guard band size and the transmission bandwidth configuration need to be specified and used as a basis for defining transmitter and receiver requirements. The identified impact to BS core specification for a new channel BW is shown in following Table 6.7.5-1.
+
+**Table 6.7.5-1 Analysis on the impact to BS core specification for a new channel BW**
+
+| Subject | Clause in 38.104 | Requirement | Assessment for new channel BW |
+|-------------|------------------|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| General | 5.3.2 | Transmission bandwidth configuration | the Transmission bandwidth configuration $N_{RB}$ for the new CBW need to be defined |
+| | 5.3.3 | Minimum guardband and transmission bandwidth configuration | The minimum guardband for the new CBW need to be defined |
+| | 5.3.5 | BS channel bandwidth per operating band | new CBW need defined per band |
+| Transmitter | 6.3.3 | Total power dynamic range | it is a $N_{RB}$ related requirement |
+| | 6.6.2 | Occupied bandwidth | BS channel bandwidth should be defined |
+| | 6.6.3 | ACLR | The filter are set using transmission bandwidth configuration ( $BW_{Config}$ ). It need to be defined for testing |
+| | 6.7 | Transmitter intermodulation | the interfering is defined according to BS channel bandwidth |
+| Receiver | 7.2 | Reference sensitivity level | for 15 KHz SCS, 25 RB and 106 RB FRC which can be reused |
+| | 7.3 | Dynamic range | interfering signal level is according to BS channel bandwidth |
+| | 7.4 | In-band selectivity and blocking | the position of interfering signal is defined according to BS channel bandwidth/transmission bandwidth configuration |
+| | 7.7 | Receiver intermodulation | the position of interfering signal is defined according to BS channel bandwidth/transmission bandwidth configuration |
+| | 7.8 | In-channel selectivity | it is defined according to BS channel bandwidth |
+
+It is concluded that new dedicated BS channel bandwidths for irregular channel bandwidths are not defined explicitly in the specification.
+
+### 6.7.6 Additional enhancements
+
+#### 6.7.6.1 Channel raster enhancements
+
+All FR1 low-frequency bands have channel raster in steps of 100kHz defined by RAN WG4 as the global raster (5kHz) x 20. RAN WG2 signalling also uses the global raster of 5kHz in principle not preventing a channel of being on any 5kHz channel raster point. While configuring the NR channel on the 100kHz raster is not a big limitation for standard spectrum blocks, such as 5 or 10MHz, it may result in less efficient spectrum utilisation in certain irregular channels. Furthermore, it might be difficult (and sometimes even impossible) to configure the dedicated UE channel bandwidth so that it is aligned on the 100kHz raster and at the same time is the RB aligned with the SIB1 channel bandwidth if the latter is also on the 100kHz raster.
+
+One exemplary benefit of allowing carriers on the non-100kHz raster is presented in Figure x-1 below for the 7MHz irregular channel. If, for the sake of example, we assume overlapping carriers from the network perspective as potential solution, then the first and the second carrier must have offsets in multiple of 900kHz, whereupon 900kHz is the common multiplier between the 100kHz raster and 180kHz RB size. So, for the 7MHz channel we can shift the second carrier by 1800kHz, i.e., 10RBs; but the resulting guard bands will be noticeably larger than the minimum requirements for the 5MHz carrier. If there is a way to put the carrier on the non-100kHz raster, then the overall system capacity can be increased to 36 RBs still ensuring the minimum guard-band requirements of the 5MHz carrier.
+
+
+
+The diagram illustrates three overlapping carrier configurations within a 7 MHz total bandwidth. Each carrier is represented by a row of 25 Resource Blocks (RBs), numbered 0 to 24.
+
+- Top Carrier:** Labeled "6.3 MHz (35 RB)". It consists of 25 RBs starting at the beginning of the 7 MHz band. Above the RBs, a double-headed arrow indicates a width of "1980 kHz".
+- Middle Carrier:** Labeled "6.48 MHz (36 RB)". It consists of 25 RBs shifted to the right, starting at RB index 10 of the top carrier's sequence. Above this carrier, a double-headed arrow indicates a width of "1800 kHz".
+- Bottom Carrier:** Labeled "7 MHz". It consists of 25 RBs shifted further right, starting at RB index 20 of the top carrier's sequence. Below this carrier, a double-headed arrow indicates a total width of "7 MHz".
+
+The diagram shows how the carriers overlap: the top carrier occupies RBs 0-24, the middle carrier occupies RBs 10-34, and the bottom carrier occupies RBs 20-44 (relative to the top carrier's RB indexing). The 100kHz raster alignment is shown for the top and middle carriers, while the bottom carrier is on a non-100kHz raster.
+
+Figure 6.7.6.1-1: Exemplary usage of overlapping carriers with 100kHz and non-100kHz alignment (7MHz irregular channel).
+
+**Figure 6.7.6.1-1: Exemplary usage of overlapping carriers with 100kHz and non-100kHz alignment (7MHz irregular channel).**
+
+Thus, a potential enhancement is to extend available channel raster points so that the 100kHz raster alignment is not mandated at least for the dedicated UE channel bandwidth. It can be implemented as a common feature of the whole release or as a UE capability. Nevertheless, irrespective how it is introduced, once the network knows the UE capabilities, it can decide whether the dedicated UE channel bandwidth should stay on the 100kHz raster (for legacy devices) or can be re-configured to a non-100kHz raster channel.
+
+In the example of Figure x-1, the network can configure two carriers (each with its own SSB, shown at the top and in the middle of Figure x-1) in accordance with the 100kHz requirement and these carriers will serve legacy devices. And since the network is aware of the UE capabilities, it can always consider configuring another overlapping carrier on the non-100kHz raster after the UE completed the attachment procedure through the legacy carrier shown in the middle row of Figure x-1. This way the network can handle both legacy and new devices and it will be the network scheduler responsibility to decide how to schedule resources over three overlapping carriers.
+
+#### 6.7.6.2 UE channel larger than SIB1 channel enhancement
+
+When a UE camps on the cell, it reads the corresponding system information to understand the position of the channel, its size, the initial bandwidth part configuration, etc. Once a UE enters the cell, the network has an ability to re-configure the UE whereupon the network can also provide a new channel configuration that will be specific to that UE.
+
+While the most common re-configuration case is to configure a UE with the dedicated channel and/or bandwidth part that is within the SIB1 channel bandwidth, there are also use cases when a UE might be configured with the channel size or position of which is outside the SIB1 configuration. Thus, to enable better utilisation of irregular channels it would be preferable that UEs can support a re-configuration scenario when the dedicated UE channel is outside the SIB1 boundaries.
+
+# 7 Conclusion
+
+## 7.1 Comparison Between Different Schemes
+
+This section provides a comparison of the proposed schemes using different criteria.
+
+The comparison between different schemes is summarized Table 7.2.1.
+
+**Table 7.2.1. Comparison of different schemes**
+
+| Comparison Criteria | Overlapping CA (two cells) – described in Section 6.2.3 | Combined UE CBW (One cell) – described in Section 6.2.2 | Overlapping UE CBW – described in Section 6.2.1 | Larger CBW (one cell) – described in Section 6.1 |
+|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Regulatory requirement | No issue | No issue | No issue | Potential issue on the BS side, gNB filters will be needed depending on BS implementation. |
+| UE performance degradation relative to minimum requirements | Possible impact on Rx sensitivity vs regular CBW, if single carrier Tx-Rx separation is not maintained. | Possible impact on Rx sensitivity vs regular CBW, if single carrier Tx-Rx separation is not maintained. | No issue | UE ACS and in-band blocking degradation.<br><br>Possible impact on Rx sensitivity vs regular CBW, if single carrier Tx-Rx separation is not maintained. |
+| gNB complexity | gNB has to support CA and schedule the data without collision in the two CC's overlapping PRBs | gNB has to support splitting the signal into 2 RF carriers with a predefined phase relationship | gNB has to support the irregular channel BW (can also be implemented through RF combining of 2 channels) | No changes needed if the BS can meet regulatory requirements with the RF front end of the wider channel BW. Otherwise, gNB has to support the irregular channel BW |
+| UE complexity | UE has to support intra-band NC CA.<br><br>1 less CC can be supported when irregular BW is used in combination from other bands, or more total CCs needed. | UE has to support RF architecture as in intra-band NC CA.<br><br>Needs new capability to aggregate 2 RF channels in baseband.<br><br>Complexity higher than CA because the | No changes needed, supported by legacy UEs | No changes needed, supported by legacy UE |
+
+| | | | | |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| | | baseband will need a new "combiner" module.<br><br>1 less CC can be supported when irregular BW is used in combination from other bands, or more total CCs needed. | | |
+| UE throughput | UEs supporting the feature can use the entire spectrum allocation, legacy UEs can use an already supported channel BW | UEs supporting the feature can use the entire spectrum allocation, legacy UEs can use an already supported channel BW | UE throughput based on existing channel BWs (5MHz for holdings <10MHz, 10MHz for holdings <15MHz, etc) | UE throughput based on how many RBs can be used |
+| Spectral utilization | Channel edge guardband based on the aggregated channel BW (5MHz for <10MHz, 10MHz for <15MHz, etc), 2 SSBs are needed | Channel edge guardband based on the aggregated RF carrier BW (5MHz for <10MHz, 10MHz for <15MHz, etc), single SSB needed | Channel edge guardband based on the actual holding (can be same as Overlapping CA), 2 SSBs are needed | Depends on the usable number of RBs, single SSB needed |
+| Cell Spectral utilization | Entire spectrum holding can be used even only with legacy UEs | Entire spectrum holding can be used even only with legacy UEs for some scenarios depending on whether a single SSB can be used to configure legacy channels at both edges of the spectrum holding. Otherwise, entire spectrum can be used only by new UEs, all legacy UEs have to use the same regular channel BW part of the spectrum holding. | Entire spectrum holding can be used even only with legacy UEs | Entire spectrum holding, but with wider guard bands than in the other methods, can be used even only with legacy UEs |
+| Network capacity | Entire spectrum can be used by multiplexing different UEs(even legacy UEs) | Entire spectrum can only be used for new UEs, whether legacy UEs can be multiplexed to cover entire channel depends on the configuration and bandwidth | Entire spectrum can be used by multiplexing different UEs in the frequency domain | Entire spectrum can be used by any UE |
+| Legacy UE support | Legacy UEs supported, can use one of the aggregated CCs | Legacy UEs can use part of the spectrum that contains the SSB | Legacy UEs supported | Legacy UEs supported |
+
+| | | | | |
+|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| RAN1/2/4<br>Specification impact | RAN1/2 – new UE capabilities needed,<br><br>RAN4 – new band combinations, changes to channel spacing definition, Overlapping CA reqs applicability, new demod requirements for UEs | RAN2 – impact on new capability<br><br>RAN4 –core requirements equivalent to new channel BW for BS, new demod requirements for UEs | RAN4 – BS requirements for new channel BW | RAN4 – BS requirements for new channel BW, possibly restrictions of the suitable scenarios.<br><br>New asymmetric bandwidth combinations for UE are needed. However these combinations would be “regular” BW combinations, so existing process. |
+|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+## 7.2 Study Item Conclusions
+
+The method of using a larger Channel BW than the licensed BW is based on blanking (not scheduling) PRBs within the larger BW but outside the irregular BW. If applied for the DL only, this method can be supported by specifying an asymmetric UE CHBW bandwidth configuration for band such that its UL CHBW is contained within the irregular UL block and the DL CHBW is larger than the irregular DL block. In this way UE unwanted emission requirement in the UL can be met by means of the regular UE CHBW. The larger DL UE CHBW implies a degraded UE adjacent channel selectivity and blocking performance when the interferer is close to the irregular DL block. However, the method can be supported by using existing UE architectures (since asymmetric bandwidths are supported by the current standard) in combination with new asymmetric CHBW combinations. The method works for both FDD and TDD.
+
+Overlapping channels from the network perspective can be used to support irregular spectrum allocations. This method can provide the full network capacity improvement in DL and UL to a spectrum utilization $\geq 90\%$ of the irregular BW (at 15 kHz SCS). This method can be used with legacy UE, even Rel-15, not requiring any changes at the UE side. Since a UE is configured with standard channel bandwidth, there are no issues with UE performance degradation relative to minimum requirements and all the regulatory requirements can be met as per legacy operation. The ACS and the blocking performance are not affected, hence there will be no impact on the network planning. The gNB has to support the irregular channel BW because from the network perspective RBs are scheduled across the whole spectrum block. That might also require new BS requirements for new irregular channels. This method provides a fast, generic, safe, and efficient solution for FDD and TDD bands.
+
+# Annex A (informative): The case of n12 and n85
+
+## A.1 Support for n12 and n85 at the lower edge of the bands
+
+In the USA the lower 700 MHz band is licensed in 6 MHz blocks. The lower 700 MHz A block covers 698-704 MHz UL and 728-734 MHz in the downlink. NR band n12 covered all but the lowest 1 MHz of the A block. NR band n85 covers the entire A Block. Hence, NR band n85 extends 1 MHz lower than NR band n12. Because some devices will support n12 while others will support n85, it would be beneficial if n12 capable UEs could use the 5 MHz at the bottom of n12 downlink while n85 capable UEs are able to use the 6 MHz at the bottom of the n85 downlink.
+
+
+
+The diagram shows frequency bands and their overlaps:
+
+- A pink box labeled "5 MHz" is aligned with a white box labeled "n12". This band starts at 729 MHz and ends at 734 MHz.
+- A pink box labeled "6 MHz" is aligned with a white box labeled "n85". This band starts at 728 MHz and ends at 734 MHz.
+- A white box labeled "10 MHz" spans from 728 MHz to 738 MHz.
+- Frequency markers on the horizontal axis: 728 MHz, 729 MHz, 738 MHz, and 746 MHz.
+
+Diagram showing the overlap of n12 and n85 bands at the lower edge of the 700 MHz band.
+
+**Figure 6.1.4-1: Overlap at the bottom of n12 and n85**
+
+## A.2 Support for n12 and n85 overlap using the next wider channel bandwidth approach
+
+One way to allow n12 UEs to use 729-734 MHz DL and n85 UEs to use 728-734 MHz DL would be to use the next wider channel bandwidth approach. The network could configure an n85 cell with a downlink of 729-734 MHz and include n12 in the MultiFrequencyBandListNR in the SIB. Then both n12 capable and n85 capable UEs could access the cell. After the gNB processes the UE capabilities, the network could assign n85 capable UEs a UE-Specific downlink channel bandwidth covering 728-738 MHz. Based on feedback from RAN2 in R4-2200031 signalling supports the configuration of a channel that is larger than the channel bandwidth in the SIB and/or extends beyond the edge of the channel in the SIB as long as it is within the band. However, since this behavior might not be supported by all UEs, new capability signalling may be required to enable the n85 capable UE to indicate that it supports such a configuration. Also, because the uplink configuration would be 5 MHz, the n85 UEs would also need to indicate support to an asymmetric channel bandwidth.
+
+## A.3 Support for n12 and n85 overlap using the overlapping channel bandwidth approaches
+
+One way to allow n12 UEs to use 729-734 MHz DL and n85 UEs to use 728-734 MHz DL would be to use one of the overlapping channel bandwidth approaches. The network could configure an n85 cell with a downlink of 729-734 MHz and include n12 in the MultiFrequencyBandListNR in the SIB. Then both n12 capable and n85 capable UEs could access the cell. After the gNB processes the UE capabilities, the network could configure n85 capable UEs with one of the overlapping channel bandwidth approaches using the 5 MHz at the bottom of n85 (728-733 MHz) and the next 5 MHz (734-739 MHz). Legacy UEs would only use 729-734 MHz.
+
+# --- Annex B (informative): Change history
+
+## **Change history**
+
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+|---------|----------------|------------|----|-----|-----|-------------------------------------------------------------------------------------------------|-------------|
+| 2020-11 | RAN4#97 | R4-2015722 | | | | TR Skeleton | 0.0.1 |
+| 2020-11 | RAN4#97 | R4-2016930 | | | | TR Skeleton (revised) | 0.0.1 |
+| 2021-01 | RAN4#98 | R4-2101555 | | | | Updated TR 38.844 | 0.0.2 |
+| 2021-01 | RAN4#98 | R4-2103262 | | | | Updated TR 38.844 (revised) | 0.0.2 |
+| 2021-04 | RAN4#98bis | R4-2106690 | | | | TP to the TR 38.844: Terminology | 0.0.2 |
+| 2021-04 | RAN4#98bis | R4-2105420 | | | | TP to the TR 38.844: Terminology (revised) | 0.0.2 |
+| 2021-05 | RAN4#99-e | R4-2110487 | | | | Update TR 38.844 with TP | 0.0.3 |
+| 2021-05 | RAN4#99-e | R4-2108021 | | | | TP on the use of overlapping channel bandwidths from UE perspective | 0.0.3 |
+| 2021-05 | RAN4#99-e | R4-2107885 | | | | TP to TR38.844 on wider channel BW method | 0.0.3 |
+| 2021-05 | RAN4#99-e | R4-2108022 | | | | TP to TR38.844 on wider channel BW method (revised) | 0.0.3 |
+| 2021-05 | RAN4#99-e | R4-2109436 | | | | TP on using overlapping channels from the network perspective solution | 0.0.3 |
+| 2021-05 | RAN4#99-e | R4-2107887 | | | | TP on using overlapping channels from the network perspective solution (revised) | 0.0.3 |
+| 2021-05 | RAN4#99-e | R4-2108112 | | | | TP on using overlapping channels from the network perspective solution (revised) | 0.0.3 |
+| 2021-08 | RAN4#100-e | R4-2113948 | | | | Updated TR 38.844 | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2114239 | | | | TP for TR 38.844: 6 MHz for n85 with overlapping CHBW | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2112365 | | | | TP on using next larger channel bandwidth solution | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2114999 | | | | TP on using next larger channel bandwidth solution (revised) | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2115114 | | | | TP on using next larger channel bandwidth solution (revised) | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2113046 | | | | TP on overlapping UE channel bandwidths (Overlapping CA) | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2115000 | | | | TP on overlapping UE channel bandwidths (Overlapping CA) (revised) | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2113949 | | | | TP to TR 38.844: Section 6.2 Overlapping UE Channel BWs | 0.0.4 |
+| 2021-08 | RAN4#100-e | R4-2115050 | | | | TP to TR 38.844: Section 6.2 Overlapping UE Channel BWs (revised) | 0.0.4 |
+| 2021-11 | RAN4#101-e | R4-2118777 | | | | Updated TR 38.844 | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2120012 | | | | TP to TR 38.844 Section 6.3.2 | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2117954 | | | | TP with further information on UE channel filter assumptions | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2120013 | | | | TP with further information on UE channel filter assumptions (revised) | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2117955 | | | | TP with corrections for overlapping channels from the network perspective | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2120015 | | | | TP with corrections for overlapping channels from the network perspective (revised) | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2119230 | | | | TP to TR 38.844: on the use of overlapping channel bandwidths from UE perspective | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2120016 | | | | TP to TR 38.844: on the use of overlapping channel bandwidths from UE perspective (revised) | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2118778 | | | | TP to TR 38.844: Overlapping CBW from UE perspective utilizing intra-band CA approach | 0.0.5 |
+| 2021-11 | RAN4#101-e | R4-2120017 | | | | TP to TR 38.844: Overlapping CBW from UE perspective utilizing intra-band CA approach (revised) | 0.0.5 |
+| 2022-01 | RAN4#101-bis-e | R4-2201485 | | | | Updated TR 38.844 | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2201794 | | | | Revision on TR 38.344 Section 6.2.3 | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202046 | | | | TP for TR 38.844: Proposal for n12 and n85 | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202416 | | | | TP for TR 38.844: Proposal for n12 and n85 (revised) | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2201511 | | | | On overlapping CBWs from Network perspective | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202377 | | | | On overlapping CBWs from Network perspective (revised) | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2201993 | | | | TP to TR 38.844: on combined UE CBW (one cell) – signalling aspects | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202378 | | | | TP to TR 38.844: on combined UE CBW (one cell) – signalling aspects (revised) | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2201487 | | | | TP to TR 38.844: Section 6.1.2 Signalling for Overlapping CA Approach | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202379 | | | | TP to TR 38.844: Section 6.1.2 Signalling for Overlapping CA Approach (revised) | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2201885 | | | | TP to TR 38.844: Wider CBW method | 0.0.6 |
+
+| | | | | | | | |
+|---------|----------------|------------|--|--|--|--------------------------------------------------------------------------------------------------------------------------|-------|
+| 2022-01 | RAN4#101-bis-e | R4-2202375 | | | | TP to TR 38.844: Wider CBW method | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202423 | | | | TP to TR 38.844: Wider CBW method (revised) | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202381 | | | | TP to TR 38.844: Clause 6.1.2 Signalling and configuration aspects | 0.0.6 |
+| 2022-01 | RAN4#101-bis-e | R4-2202382 | | | | TP to TR 38.844: Clause 7 | 0.0.6 |
+| 2022-02 | RAN4#102-e | R4-2206552 | | | | Updated TR 38.844 | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2203668 | | | | Further corrections to the solution based on overlapping channels from the network perspective | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2206554 | | | | TP to TR 38.844: Editorial clean up | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2206555 | | | | TP to TR 38.844: corrections | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2206557 | | | | TP to TR 38.844 on Larger CBW approach: Signalling and configuration aspects | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2206558 | | | | TP for overlapping CA | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2206595 | | | | TP to TR 38.844: Clause 6.1.2.x Spec impact identification | 0.0.7 |
+| 2022-02 | RAN4#102-e | R4-2209136 | | | | Updated TR 38.844 | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2208041 | | | | TP to TR 38.844: General Updates | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210796 | | | | TP to TR 38.844: General Updates (revised) | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2208554 | | | | TP for wider channel bandwidth | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210797 | | | | TP for wider channel bandwidth (revised) | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210343 | | | | Further input on performance when using the next larger channel | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210798 | | | | Further input on performance when using the next larger channel (revised) | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2209031 | | | | Further discussion on the Wider CBW approach | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210802 | | | | Further discussion on the Wider CBW approach (revised) | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2208555 | | | | TP for Overlapping UE CBWs from Network Perspective | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210804 | | | | TP for Overlapping UE CBWs from Network Perspective (revised) | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2208556 | | | | TP for overlapping CA | 0.0.8 |
+| 2022-05 | RAN4#103-e | R4-2210808 | | | | TP for overlapping CA (revised) | 0.0.8 |
+| 2022-08 | RAN4#104-e | R4-2212866 | | | | Updated TR 38.844 | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2300371 | | | | TP on additional enhancements for irregular channels | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2303497 | | | | TP on additional enhancements for irregular channels (revised) | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2300750 | | | | TP for 38.844: Configuration for the case of larger channel bandwidths than licensed bandwidth and conclusions | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2303501 | | | | TP for 38.844: Configuration for the case of larger channel bandwidths than licensed bandwidth and conclusions (revised) | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2301606 | | | | TP on the larger channel bandwidth approach (Section 6.1.1) for TR 38.844 | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2303502 | | | | TP on the larger channel bandwidth approach (Section 6.1.1) for TR 38.844 (revised) | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2300202 | | | | TP to TR 38.844 on Overlapping UE CBWs from Network Perspective | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2303503 | | | | TP to TR 38.844 on Overlapping UE CBWs from Network Perspective (revised) | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2302436 | | | | TP for 38.844: conclusions for overlapping CBWs from network perspective | 0.0.9 |
+| 2023-02 | RAN4#106 | R4-2302237 | | | | Updated draft TR 38.844 | 0.1.0 |
+| 2023-03 | RAN#99 | RP-230580 | | | | TR 38.844 provided for approval | 1.0.0 |
+| 2023-03 | RAN#99 | RP-230750 | | | | TR 38.844 provided for approval (revised) | 1.0.1 |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2023-03 | RAN#99 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38872/078a3a06b76da57667ffb30934eb9712_img.jpg b/marked/Rel-18/38_series/38872/078a3a06b76da57667ffb30934eb9712_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08f8ca67811b5f775a4adf5c82584366a3dd42c7
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/078a3a06b76da57667ffb30934eb9712_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77dd696acb946dad58ed324e85da821491edce9053f25cdba5ee71d9eea77c3b
+size 19558
diff --git a/marked/Rel-18/38_series/38872/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/Rel-18/38_series/38872/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4888eeb5c5cd8899ff2bdaa4531646997d1297d8
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8e8821aea288395a75f6d7e78d23763051773152292c8aa0eecb0270c3647b6
+size 47283
diff --git a/marked/Rel-18/38_series/38872/0bf2828d4a6f0cba93b620a843e771d3_img.jpg b/marked/Rel-18/38_series/38872/0bf2828d4a6f0cba93b620a843e771d3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ced5de466602551d4408790af174a954a61e8169
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/0bf2828d4a6f0cba93b620a843e771d3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:893f39f380106e2cd13659f02a39e98a77c5c6c72f7d62ad02d320df209ef226
+size 53931
diff --git a/marked/Rel-18/38_series/38872/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-18/38_series/38872/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9316f43496eabde58b7ae6739d9fa1dc9a8b1c4c
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:190752b68ecb05a6edd59137305a57e2a8726085a13a07b2e06bc14a7815a385
+size 78332
diff --git a/marked/Rel-18/38_series/38872/146d3888c39166a3a81fcedb7d9f6b3d_img.jpg b/marked/Rel-18/38_series/38872/146d3888c39166a3a81fcedb7d9f6b3d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3669c555deee597f6183ffc6fb94d1cc9abc85d1
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/146d3888c39166a3a81fcedb7d9f6b3d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e853a9733c21f02fe6842dcca8d71c1ee106c8d4ecbd82d96f73bde6710d8e3d
+size 41498
diff --git a/marked/Rel-18/38_series/38872/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-18/38_series/38872/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef81b54c2888b542f984f784e391a82faab25dfe
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4cd27c3cd1906891fa0aef25a475f265c513ad5e4eb4246cbed1041fc11f52b6
+size 37824
diff --git a/marked/Rel-18/38_series/38872/1a09fb1ec1922a373a14bff45ebf433e_img.jpg b/marked/Rel-18/38_series/38872/1a09fb1ec1922a373a14bff45ebf433e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ffd1d6a371be1ade48cfd4bc6994b2215402e6e6
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/1a09fb1ec1922a373a14bff45ebf433e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80818fe440264432c83e6a021814a9f5c48e4f7b36151f8b2c980e02b572cc55
+size 20643
diff --git a/marked/Rel-18/38_series/38872/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-18/38_series/38872/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4fb68b99275c5563659a5a31ec10fd51905b4ee0
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a6ea15b2995bb5cee6d4c0e83c2dbd43b4e47347b497d2ecbe3dce44fa9712a
+size 23052
diff --git a/marked/Rel-18/38_series/38872/20cb2d2cc18d663dc1b82453c67250bb_img.jpg b/marked/Rel-18/38_series/38872/20cb2d2cc18d663dc1b82453c67250bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7843c3cf966408a535475b000454ffbf26fe8546
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/20cb2d2cc18d663dc1b82453c67250bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be7b965963f779f78f3c4b1f25edb73e16068a996192d66d5a4c3e9f7dc68cc0
+size 26416
diff --git a/marked/Rel-18/38_series/38872/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-18/38_series/38872/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c6611c8d1716ef904ffd4b58df339675cf6aba4
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f79fc131107cdce4f7c79aa444411007f682d2df7fb034c5296a63123a286126
+size 41092
diff --git a/marked/Rel-18/38_series/38872/2b6886fb185564eb8b6ff86d856a672a_img.jpg b/marked/Rel-18/38_series/38872/2b6886fb185564eb8b6ff86d856a672a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1cbb959745d2919f5b98b14dfb8451ef753cb13
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/2b6886fb185564eb8b6ff86d856a672a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b42c64910a0a52add61a6530c69b0c38b5837f964a42ea4db61a4407a21f86c1
+size 19868
diff --git a/marked/Rel-18/38_series/38872/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-18/38_series/38872/347010b7ac06d3ae97927fde0f784d7c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c048406f9dd76e4b86eec478854eaa3fd15eec6b
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/347010b7ac06d3ae97927fde0f784d7c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8152fdd31cb74243b13360ab0fc75266ba19cf25e5565ccbe222dc6a1a85730a
+size 49120
diff --git a/marked/Rel-18/38_series/38872/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-18/38_series/38872/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7e281a72add83f1e2b4e1a51becec494df47a20
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45b0df0ccd431a4a558a05878a6d1aee15291fbba460e8fde522c5ad372d1530
+size 40484
diff --git a/marked/Rel-18/38_series/38872/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-18/38_series/38872/408c4798ea60469e0728a7cbbd598668_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aae67d153b3f65b90a391a1c7ba0e6c05d896461
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/408c4798ea60469e0728a7cbbd598668_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9152edd6f8dc5d3db43c9b82d336db1cb1be46aeedfabbd818adc1056913c057
+size 47797
diff --git a/marked/Rel-18/38_series/38872/411fa16c3211377525ba37c57784fee0_img.jpg b/marked/Rel-18/38_series/38872/411fa16c3211377525ba37c57784fee0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..673e26bdcb6eab422bc9d005b806769fb18c4ede
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/411fa16c3211377525ba37c57784fee0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2232130e9a976e0aaf63a6e8d0e114180c6ea3266f1ecdab337e4603697a059c
+size 26365
diff --git a/marked/Rel-18/38_series/38872/4a390493f601ce1ac6b9201db4e28b5a_img.jpg b/marked/Rel-18/38_series/38872/4a390493f601ce1ac6b9201db4e28b5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21db736191611fcbca4b0f4b1da14e1d3f4e6e1b
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/4a390493f601ce1ac6b9201db4e28b5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fb345b3e063fbe91431e4865408b447102c7c1a57338c9f19dcca516b9652a9
+size 45083
diff --git a/marked/Rel-18/38_series/38872/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-18/38_series/38872/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e195c3597155994711c1bd3552d0fcc9e872217a
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:004d14146056a5617c9ad11055dbc75536f9efcbb8ad70baa4fcbebd2d857a3a
+size 27370
diff --git a/marked/Rel-18/38_series/38872/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-18/38_series/38872/575d7d345b3ec04393bb2ec720ebabca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2eb2db7c7aa4bf7fdf133b5a123af84581c79ecd
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/575d7d345b3ec04393bb2ec720ebabca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97b3fa51359cd2893fbd391474665cdbf31a687e633bb7546645a7416f57035d
+size 23356
diff --git a/marked/Rel-18/38_series/38872/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38872/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02b13108b1f606b9a10d22a0e2558fd1508d4f47
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7db101b4fef06ea2ae6986eda539640b42ea02d77a6d656e415f117e6e77781a
+size 9531
diff --git a/marked/Rel-18/38_series/38872/61396fdb4cfbcf3c7164a00b0fa7b658_img.jpg b/marked/Rel-18/38_series/38872/61396fdb4cfbcf3c7164a00b0fa7b658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..83963803860a80d9f47fb2184e740b1b0fff4588
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/61396fdb4cfbcf3c7164a00b0fa7b658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cc05df2eac6bd0c48384373b829a2dd7e9de38764cfa47f100ea72c59f09cd2
+size 43027
diff --git a/marked/Rel-18/38_series/38872/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-18/38_series/38872/61a7f401eb46fe99a71f27bc37493f04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b777ed1937fce1efb23fb6a4b4556fecada85e30
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/61a7f401eb46fe99a71f27bc37493f04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fedb1f2e33c32ccbf7474c706fedcd645e499d04e85dd0682f330e92fde0a98a
+size 26652
diff --git a/marked/Rel-18/38_series/38872/63fc2a3d211283bdef0682dbd6d01a9c_img.jpg b/marked/Rel-18/38_series/38872/63fc2a3d211283bdef0682dbd6d01a9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f05d18451dea5be4b7c0a9c780bb64014bfa5f8c
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/63fc2a3d211283bdef0682dbd6d01a9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:543f85dc990914e46eb33d76d7ef6b10694f38e2e98ba9b6dd8b7342412bc0b8
+size 34864
diff --git a/marked/Rel-18/38_series/38872/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38872/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3ff30bcc0e2dcdac4bc88f2f3cb81734810a273
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0b16f7824582efd278c44cc7e415d6cd0a032a8d2f77188b997023af867c2f16
+size 5732
diff --git a/marked/Rel-18/38_series/38872/671a9a08b8506e113012e056945fd8f3_img.jpg b/marked/Rel-18/38_series/38872/671a9a08b8506e113012e056945fd8f3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb503dd9867a0c8c0a114cfdf82ab16bf0a4a5ff
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/671a9a08b8506e113012e056945fd8f3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc9f5320e51219fc1d6d2df7cef7f6783db53955fbf15dd3104d041b2a15f4f7
+size 82533
diff --git a/marked/Rel-18/38_series/38872/695068a37ee8ec4b395658c3ff2209f2_img.jpg b/marked/Rel-18/38_series/38872/695068a37ee8ec4b395658c3ff2209f2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..09622598114855022155b555cb7641fbcf7f8a51
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/695068a37ee8ec4b395658c3ff2209f2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3d1a2732c8a2f7d6f133d15cc06ab262a145a1e22aa38177a98a91dd19c7dd4
+size 21348
diff --git a/marked/Rel-18/38_series/38872/6ba2b00e9434aa86af566824b1c1446b_img.jpg b/marked/Rel-18/38_series/38872/6ba2b00e9434aa86af566824b1c1446b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4fba39ec6b9597fa82811b0af61cc0135e93393e
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/6ba2b00e9434aa86af566824b1c1446b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c14437be7667a4aa291abacb5df1eef48f91dfbabb9fb54ac579eb5dcd911e5
+size 22395
diff --git a/marked/Rel-18/38_series/38872/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/Rel-18/38_series/38872/742a5484e7dd016256ab99921bbd635d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf664968a412c4759021b384033b0c0eeb4967bd
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/742a5484e7dd016256ab99921bbd635d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c095a0b530ca2e2280cb5612c815dd8bdc57619a981e33d60d38c75bd2a69787
+size 26707
diff --git a/marked/Rel-18/38_series/38872/747516f5861a0ddf31e3851da8e34b95_img.jpg b/marked/Rel-18/38_series/38872/747516f5861a0ddf31e3851da8e34b95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff513c550e3db5101453c37ef59206a75e129686
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/747516f5861a0ddf31e3851da8e34b95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:078e7a1ab50a8a4f20251d98f1a222aefc646cf013f51fc671ea5d0e7daf6dad
+size 31996
diff --git a/marked/Rel-18/38_series/38872/75ea47f7730ba5f85110850f4cf5f193_img.jpg b/marked/Rel-18/38_series/38872/75ea47f7730ba5f85110850f4cf5f193_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..385d78ef3b6d1636d4a4a23412af96570d236531
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/75ea47f7730ba5f85110850f4cf5f193_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3ac959eaba7bbbe7cc63ac989d82e86eaf6380df4ec44cae386a2870da58b6f
+size 26877
diff --git a/marked/Rel-18/38_series/38872/762a17cd79880dbca172bcbbe9375223_img.jpg b/marked/Rel-18/38_series/38872/762a17cd79880dbca172bcbbe9375223_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6da3fc573223f3fefcd7707970d9409a66b6a3fe
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/762a17cd79880dbca172bcbbe9375223_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5970e7072e3381e826a6d43049963e4f0769e5cc753f3ca642b0e8bf4d1cf938
+size 30510
diff --git a/marked/Rel-18/38_series/38872/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-18/38_series/38872/7b2d685b805535c1e94aee1365753b92_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d1b8b58ba1ff0c6d1f35565b97b77a5edf1d4fc
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/7b2d685b805535c1e94aee1365753b92_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d66252c0be75f48e89c5c123a7b885871f026c34c7afa6ed3a4785fbc98177de
+size 34330
diff --git a/marked/Rel-18/38_series/38872/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38872/7c0a9511fa02b6c2c125ff5be465186e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..734ac127ee73161aa6cde8de32a50e69315b8ce6
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/7c0a9511fa02b6c2c125ff5be465186e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6073b12884f28439c69b5a393608c137cc29251cbb01d70acdc884ffc213f010
+size 110861
diff --git a/marked/Rel-18/38_series/38872/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-18/38_series/38872/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ade91a3bc2f60e6b4961b34610d4c4b4e80756e1
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32865b5c0e289cbc99f7492b6975dc34b1ec1674e3a2d8f1a378f654d57bf98d
+size 64761
diff --git a/marked/Rel-18/38_series/38872/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/Rel-18/38_series/38872/94fd137860c16c8dfd75512f10161fe8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0209866d9fe161cb867d7fd09f7cc8299a8d37c7
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/94fd137860c16c8dfd75512f10161fe8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:172deb5f3db5116cd38b8c319e49b14a9876f9225a9478b3c08e454b448be05f
+size 58207
diff --git a/marked/Rel-18/38_series/38872/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-18/38_series/38872/977811d1c73b74f801be9f4c376694ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..181d3536b651265c6bab76f60f81a21f6bcac496
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/977811d1c73b74f801be9f4c376694ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:241ddbeab1089b5d676cd6df2abd0b25df2493febf2deae648ba653e872e4a7a
+size 25798
diff --git a/marked/Rel-18/38_series/38872/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-18/38_series/38872/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bb1c91e20fc7b2a19bbda4b88ef233d5e908d87
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74d6657a75f06a1877ccce3f34600118c084a44bca6346e8ca146a02301a544f
+size 49120
diff --git a/marked/Rel-18/38_series/38872/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-18/38_series/38872/9c45844d796e85ae05505870a54e4eb4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..199350d0628ef818d75d322c06050c134f252087
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/9c45844d796e85ae05505870a54e4eb4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc49f3bbc2b73a5253efc5452be9bf8f28f8d9fbcf81aacf1f6a483917e2d891
+size 41284
diff --git a/marked/Rel-18/38_series/38872/9cd7ec4a653f07d02def283cb6f2309e_img.jpg b/marked/Rel-18/38_series/38872/9cd7ec4a653f07d02def283cb6f2309e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2b9950ccc5ddd7a35a370c3e2f8f47cf44663aa
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/9cd7ec4a653f07d02def283cb6f2309e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:704bc45acc88cbea1ca6dfdfc57222a21a86ea8b0e9f272402e282005748beee
+size 31998
diff --git a/marked/Rel-18/38_series/38872/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Rel-18/38_series/38872/9f51a76cae7309a296cbc6997941eb3f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..afe899817995c60b9b11cab433a61b51a91e5916
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/9f51a76cae7309a296cbc6997941eb3f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de87aabeb257d6ce973314971ecf7764f2d84f7b379f8a6dbd4fb2e65a840630
+size 45025
diff --git a/marked/Rel-18/38_series/38872/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-18/38_series/38872/b904ac2472cab80892d1e783e6230d6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45e5bd74960caede740f0fceb2a24822fb527f53
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/b904ac2472cab80892d1e783e6230d6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b595e2ad3ecba5ae0a39259390974c3fe20e7d70aace2f2e01e78c4f96067832
+size 43447
diff --git a/marked/Rel-18/38_series/38872/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-18/38_series/38872/c036e2540a94b31357ceb0002f0cacab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8313f94c7e236b2ea5526519905cdf7e857f782
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/c036e2540a94b31357ceb0002f0cacab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba6857460326797841c40dbce90a3b3d3d1795bdd6354316a318111ed85319b4
+size 32865
diff --git a/marked/Rel-18/38_series/38872/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Rel-18/38_series/38872/c2f36c545b190860d04e1d84e58d22cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e21c6fc86da55c18ebe7ac36dbb2453888b287c
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/c2f36c545b190860d04e1d84e58d22cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cd9fde6b3eadfa5a93be511ba36296c573786c0f05a14b7fe9e1164b8fcbccb
+size 34376
diff --git a/marked/Rel-18/38_series/38872/c342101b8c2e923d817ba75426f82ef4_img.jpg b/marked/Rel-18/38_series/38872/c342101b8c2e923d817ba75426f82ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9070faa73af9adba6c703d8723f97cfa53ac2d0b
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/c342101b8c2e923d817ba75426f82ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c1da7e29682cebc26a08f3de418f8a3a7da4cd6f3a8b9deb1ead5e7d9687f89
+size 15926
diff --git a/marked/Rel-18/38_series/38872/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/Rel-18/38_series/38872/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61e78c067f27a130c2c2595c7c19a7ab69258a15
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d4b1a618ae94b6e7e9b0347a2ed4ae620e769303683400d174127264951056c
+size 44971
diff --git a/marked/Rel-18/38_series/38872/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-18/38_series/38872/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62ccb46be0f9e6b84939ae013d6a97b8b525a4bb
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:142ff2f50ed189abcc80b1632f254183f73ac42c0e8e99413fb90345c09ba0d5
+size 44592
diff --git a/marked/Rel-18/38_series/38872/dc37a040cf9e2add7488c7c37cbf3687_img.jpg b/marked/Rel-18/38_series/38872/dc37a040cf9e2add7488c7c37cbf3687_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88fd78e06f78f59c9d29a3b41fc33d9dd64efb21
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/dc37a040cf9e2add7488c7c37cbf3687_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:330a528a79a16dc4d6e83192a2406ef0d50068176b40cf105f03ff14dff2f7a4
+size 19566
diff --git a/marked/Rel-18/38_series/38872/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/Rel-18/38_series/38872/dd6c544ab685b25dd17f59456efcfbfc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7bcf9c295916039f02479ffdda5b8f6120186692
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/dd6c544ab685b25dd17f59456efcfbfc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d0d8291f8417f6b9e80d268661162d488b784c0b6e9f68ff599c3c8809e418e
+size 27471
diff --git a/marked/Rel-18/38_series/38872/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-18/38_series/38872/dfaa8b98082261913dac00eae86b2889_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1dc2dfb3a47688491bf8e788520acb7d77462675
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/dfaa8b98082261913dac00eae86b2889_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51103d17147de99b209046b887cacb118f6f42f6b4ceb7904272a8965ac191e3
+size 30344
diff --git a/marked/Rel-18/38_series/38872/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-18/38_series/38872/e7010c66da16316c2935dfbbef5056b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62a310ee845957cbd4f55fb1d930dbf6b12f5d36
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/e7010c66da16316c2935dfbbef5056b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4e8b14bf5f21d3354d7d289d82a75cf58f3f6f70175858d7c8a7a4cc8199509
+size 38557
diff --git a/marked/Rel-18/38_series/38872/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38872/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18229af28b0638af70893799da925188569e0a1c
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/ff0952ef692c9d960ce5f6708bcc9711_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:584cd90907f9a1956f6318d2bd4b072343539b4256d7b8f597b163cf5152cc07
+size 34035
diff --git a/marked/Rel-18/38_series/38872/raw.md b/marked/Rel-18/38_series/38872/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fba40118fc45097d81dd1beba167007defee5c44
--- /dev/null
+++ b/marked/Rel-18/38_series/38872/raw.md
@@ -0,0 +1,3471 @@
+
+
+# 3GPP TR 38.872 V18.3.0 (2023-12)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on enhancement for 700/800/900MHz band combinations (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon, and below the entire logo is the text 'A GLOBAL INITIATIVE'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-------------------------------------------------------------------|----|
+| Foreword ..... | 8 |
+| 1 Scope..... | 10 |
+| 2 References..... | 10 |
+| 3 Definitions of terms, symbols and abbreviations ..... | 11 |
+| 3.1 Terms..... | 11 |
+| 3.2 Symbols..... | 11 |
+| 3.3 Abbreviations ..... | 11 |
+| 4 Background..... | 11 |
+| 4.1 TR Maintenance ..... | 13 |
+| 5 Specific Band combinations..... | 13 |
+| 5.1 CA_n5-n8..... | 13 |
+| 5.1.0 General ..... | 13 |
+| 5.1.1 UE RF architecture assumption..... | 13 |
+| 5.1.2 Common for 1 band UL and 2 bands UL of CA_n5-n8..... | 18 |
+| 5.1.2.1 Operating bands for CA..... | 18 |
+| 5.1.2.2 Channel bandwidths per operating band for CA ..... | 18 |
+| 5.1.2.3 UE co-existence studies ..... | 18 |
+| 5.1.2.4 $\Delta$ TIB,c and $\Delta$ RIB,c values..... | 19 |
+| 5.1.2.5 REFSENS evaluation..... | 19 |
+| 5.1.3 Specific for 2 bands UL of CA_n5-n8 ..... | 20 |
+| 5.1.3.0 General..... | 20 |
+| 5.1.3.1 Maximum output power for inter-band CA ..... | 20 |
+| 5.1.3.2 UE co-existence studies ..... | 20 |
+| 5.1.3.3 REFSENS evaluation..... | 21 |
+| 5.1.4 Feasible RF implementations ..... | 21 |
+| 5.1.5 Output for 2UL/2DL CA_n5-n8 during the work item phase..... | 22 |
+| 5.2 CA_n5-n28..... | 25 |
+| 5.2.1 UE RF architecture assumption..... | 25 |
+| 5.2.1.1 UE RF architecture with two antennas ..... | 26 |
+| 5.2.1.2 UE RF architecture with three antennas ..... | 27 |
+| 5.2.2 Common for 1 band UL and 2 bands UL of CA_n5-n28..... | 27 |
+| 5.2.2.0 General..... | 27 |
+| 5.2.2.1 Operating bands for CA..... | 27 |
+| 5.2.2.2 Channel bandwidths per operating band for CA ..... | 27 |
+| 5.2.2.3 UE co-existence studies ..... | 28 |
+| 5.2.2.4 $\Delta$ TIB,c and $\Delta$ RIB,c values..... | 28 |
+| 5.2.2.5 REFSENS evaluation..... | 28 |
+| 5.2.3 Specific for 2 bands UL of fallback CA_n5-n28..... | 29 |
+| 5.2.3.1 Maximum output power for inter-band CA ..... | 29 |
+| 5.2.3.2 UE co-existence studies ..... | 29 |
+| 5.2.3.3 REFSENS evaluation..... | 31 |
+| 5.3 CA_n8-n20-n28..... | 33 |
+| 5.3.1 UE RF architecture assumption..... | 33 |
+| 5.3.1.0 General..... | 33 |
+| 5.3.1.1 UE RF architecture with three antennas ..... | 33 |
+| 5.3.1.2 UE RF architecture with two antennas ..... | 34 |
+| 5.3.1.3 UE RF architecture with four antennas..... | 35 |
+| 5.3.2 CA_n8-n20 ..... | 36 |
+| 5.3.2.0 General..... | 36 |
+| 5.3.2.1 Operating bands for CA..... | 36 |
+| 5.3.2.2 Channel bandwidths per operating band for CA ..... | 36 |
+| 5.3.2.3 UE co-existence studies ..... | 36 |
+| 5.3.2.4 $\Delta$ TIB,c and $\Delta$ RIB,c values..... | 36 |
+| 5.3.2.5 REFSENS requirements ..... | 36 |
+| 5.3.2.6 Maximum output power for UL inter-band CA..... | 36 |
+
+| | | |
+|---------|----------------------------------------------------------------------------------------------|----|
+| 5.3.2.7 | UE co-existence studies for UL inter-band CA ..... | 36 |
+| 5.3.2.8 | REFSENS evaluation for UL inter-band CA ..... | 38 |
+| 5.3.3 | CA_n8-n28 ..... | 38 |
+| 5.3.3.0 | General ..... | 38 |
+| 5.3.3.1 | Operating bands for CA ..... | 38 |
+| 5.3.3.2 | Channel bandwidths per operating band for CA ..... | 39 |
+| 5.3.3.3 | UE co-existence studies ..... | 39 |
+| 5.3.3.4 | $\Delta$ TIB,c and $\Delta$ RIB,c values ..... | 39 |
+| 5.3.3.5 | REFSENS requirements ..... | 39 |
+| 5.3.3.6 | Maximum output power for UL inter-band CA ..... | 39 |
+| 5.3.3.7 | UE co-existence studies for UL inter-band CA ..... | 39 |
+| 5.3.3.8 | REFSENS requirements for UL inter-band CA ..... | 41 |
+| 5.3.4 | CA_n20-n28 ..... | 41 |
+| 5.3.4.1 | General ..... | 41 |
+| 5.3.5 | CA_n8-n20-n28 ..... | 42 |
+| 5.3.5.1 | Operating bands for CA ..... | 42 |
+| 5.3.5.2 | Channel bandwidths per operating band for CA ..... | 42 |
+| 5.3.5.3 | $\Delta$ TIB,c and $\Delta$ RIB,c values ..... | 42 |
+| 5.3.5.4 | UE co-existence studies for UL inter-band CA ..... | 43 |
+| 5.3.5.5 | REFSENS evaluation ..... | 46 |
+| 5.4 | CA_n5-n105 ..... | 47 |
+| 5.4.1 | General ..... | 47 |
+| 5.4.2 | UE RF architecture assumption ..... | 47 |
+| 5.4.2.1 | UE RF architecture with two antennas ..... | 47 |
+| 5.4.2.2 | UE RF architecture with three antennas ..... | 48 |
+| 5.4.3 | Common for 1 band UL and 2 bands UL of CA_n5-n105 ..... | 49 |
+| 5.4.3.1 | Operating bands for CA ..... | 49 |
+| 5.4.3.2 | Channel bandwidths per operating band for CA ..... | 49 |
+| 5.4.3.3 | Identify the potential MSD issues due to harmonic/harmonic mixing/cross band isolation ..... | 49 |
+| 5.4.3.4 | $\Delta$ TIB,c and $\Delta$ RIB,c values ..... | 50 |
+| 5.4.3.5 | REFSENS exception evaluation for one UL band ..... | 50 |
+| 5.4.4 | Specific for 2 bands UL of CA_n5-n105 ..... | 55 |
+| 5.4.4.1 | Maximum output power for inter-band CA ..... | 55 |
+| 5.4.4.2 | UE co-existence studies ..... | 55 |
+| 5.4.4.3 | REFSENS exception evaluation for two UL band ..... | 57 |
+| 5.5 | CA_n28-n105 ..... | 57 |
+| 5.5.1 | General ..... | 57 |
+| 5.5.2 | UE RF architectures assumption ..... | 57 |
+| 5.5.2.1 | UE RF architectures with two antennas ..... | 57 |
+| 5.5.2.2 | UE RF architectures with three antennas ..... | 58 |
+| 5.5.2.3 | 2UL IMD issue ..... | 59 |
+| 5.5.2.4 | Cross-band interference ..... | 59 |
+| 5.5.3 | Common for 1 band UL and 2 bands UL of CA_n28-n105 ..... | 60 |
+| 5.5.3.0 | General ..... | 60 |
+| 5.5.3.1 | Operating bands for CA ..... | 60 |
+| 5.5.3.2 | Channel bandwidths per operating band for CA ..... | 60 |
+| 5.5.3.3 | UE co-existence studies ..... | 60 |
+| 5.5.3.4 | $\Delta$ TIB,c and $\Delta$ RIB,c values ..... | 61 |
+| 5.5.3.5 | REFSENS evaluation ..... | 61 |
+| 5.5.4 | Specific for 2 bands UL of fallback CA_n28-n105 ..... | 62 |
+| 5.5.4.1 | Maximum output power for inter-band CA ..... | 62 |
+| 5.5.4.2 | UE co-existence studies ..... | 62 |
+| 5.5.4.3 | REFSENS evaluation ..... | 63 |
+| 5.6 | CA_n26-n28 ..... | 64 |
+| 5.6.1 | General ..... | 64 |
+| 5.6.2 | UE RF architecture assumption ..... | 65 |
+| 5.6.2.1 | UE RF architecture with lower 30MHz of n28 supporting ..... | 65 |
+| 5.6.2.2 | UE RF architecture with entire n28 frequency range supporting ..... | 66 |
+| 5.6.3 | Common for 1 band UL and 2 bands UL of CA_n26-n28 ..... | 68 |
+| 5.6.3.1 | Operating bands for CA ..... | 68 |
+| 5.6.3.2 | Channel bandwidths per operating band for CA ..... | 68 |
+| 5.6.3.3 | Identify the potential MSD issues due to harmonic/harmonic mixing/cross band isolation ..... | 68 |
+
+| | | |
+|---------|------------------------------------------------------|----|
+| 5.6.3.4 | $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values..... | 69 |
+| 5.6.3.5 | REFSENS exception evaluation for one UL band..... | 69 |
+| 5.6.4 | Specific for 2 bands UL of CA_n26-n28 ..... | 78 |
+| 5.6.4.1 | Maximum output power for inter-band CA ..... | 78 |
+| 5.6.4.2 | UE co-existence studies ..... | 78 |
+| 5.6.4.3 | REFSENS exception evaluation for two UL band ..... | 80 |
+| 5.7 | CA_n5-n28-n105..... | 83 |
+| 5.7.1 | UE RF architecture assumption..... | 83 |
+| 5.7.1.1 | General..... | 83 |
+| 5.7.1.2 | UE RF architecture with two antennas ..... | 83 |
+| 5.7.1.3 | UE RF architecture with three antennas ..... | 85 |
+| 5.7.1.4 | UE RF architecture with four antennas..... | 87 |
+| 5.7.2 | Operating bands for CA..... | 88 |
+| 5.7.3 | Channel bandwidths per operating band for CA ..... | 88 |
+| 5.7.4 | $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values ..... | 88 |
+| 5.7.5 | UE co-existence studies for UL inter-band CA..... | 89 |
+| 5.7.6 | REFSENS evaluation ..... | 91 |
+
+# **Annex A: Change history 93**
+
+# Foreword
+
+This Technical Report has been produced by the 3rd 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document is the technical report for the study on enhancement for 700/800/900MHz band combinations [2] and sub-1GHz NR band combinations [5] under R18 time frame. The purpose is to gather the relevant background information and studies in order to address the study on enhancement for 600/700/800/900MHz band combinations in Table 1-1.
+
+**Table 1-1: Band combinations in the SI**
+
+| Configuration | Uplink configuration |
+|-------------------|----------------------------------|
+| CA n8-n20-n28 | CA n8-n20, CA n8-n28, CA n20-n28 |
+| CA n5-n8 | CA n5-n8 |
+| CA n5-n28 | CA n5-n28 |
+| CA n5A-n105A | CA n5A-n105A |
+| CA n28A-n105A | single UL in either n28 or n105 |
+| CA n26A-n28A | CA n26A-n28A |
+| CA n5A-n28A-n105A | CA n5A-n28A |
+| CA n5A-n28A-n105A | CA n5A-n105A |
+| CA n5A-n28A-n105A | single UL in either n28 or n105 |
+
+# 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] RP-221464, "Revised SI: Study on enhancement for 700/800/900MHz band combinations for NR", RAN#96
+- [3] TS 38.101-1
+- [4] TS 38.101-3
+- [5] RP-230789, " Study on enhancement for sub-1Ghz NR band combinations". RAN 99
+- [6] 3GPP TR 38 892 , APT 600 MHz NR band.
+- [7] R4-2308581, Discussion on RF architecture and potential MSD issues for CA\_n5-n105, Huawei, HiSilicon, Spark NZ
+- [8] R4-2309299, Input on CA\_n5-n105 cross-band MSD and DeltaT/R, Skyworks Solutions Inc.
+- [9] R4-2309356, Considerations on CA\_n5-n105, Qualcomm France
+- [10] R4-2309358, Considerations on CA\_n26-n28, Qualcomm France
+- [11] R4-2306468, WF on CA\_n5-n28 and CA\_n8-n20-n28, Huawei, HiSilicon
+- [12] R4-2308583, Discussion on RF architecture and potential MSD issues for CA\_n26-n28, Huawei, HiSilicon
+- [13] R4-2307477, Input on CA\_n26-n28 requirements, Skyworks Solutions Inc.
+
+- [14] R4-2306470, WF on RF architecture and critical issues for CA\_n28-n105
+- [15] R4-2312979, Discussion on RF architecture and potential MSD issues for CA\_n5-n28-n105
+- [16] R4-2311755, requirements for LBLBLB CA\_n5-n28-n105
+- [17] R4-2303576 TP for CA\_n26-n28, MediaTek Inc.
+- [18] R4-2311116 CA\_n26-n28 cross band MSD based on measurements, Skyworks Solutions Inc.
+- [19] R4-2311753 MSD analysis for CA\_n5-n105, CA\_n28-n105, and CA\_n26-n28, Apple Inc.
+- [20] R4-2313371 Considerations on CA\_n26-n28, Qualcomm France
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms 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].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| | |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $\Delta R_{IB,c}$ | Allowed reference sensitivity relaxation due to support for inter-band CA operation, for serving cell $c$ |
+| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for inter-band CA operation, inter-band NR-DC operation and due to support for SUL operations, for serving cell $c$ |
+
+## 3.3 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].
+
+| | |
+|-----|---------------------------------|
+| MRC | Maximum Ratio Combining |
+| MSD | Maximum Sensitivity Degradation |
+| RB | Resource Block |
+| UE | User Equipment |
+
+# --- 4 Background
+
+In RAN#95e, SI “enhancement for 700800900MHz band combinations” was approved. The objectives of SI are as follows:
+
+- 1 Investigate the feasibility and solutions to enable simultaneous transmission on two UL bands and simultaneous reception on two or three bands for the band combination of 700, 800 and 900MHz spectrum for smart phone form factor
+- 2 The following band combinations will be considered. And the feasibility study on three band combination will start after the completion of feasibility study of all the fallback band combinations.
+ - CA\_n8-n20-n28 with uplink configurations of CA\_n8-n20, CA\_n8-n28, CA\_n20-n28, and the fallback modes
+ - CA\_n5-n8 with uplink configuration of CA\_n5-n8, and the fallback modes
+
+Note1: Spectrum restrictions should be studied to solve overlap of band n5 downlink and band n8 uplink
+
+Note2: The current filter is used as the baseline. Further study whether or not to have new solutions.
+
+- CA\_n5-n28 (full range) with uplink configuration of CA\_n5-n28.
+
+In RAN 99 a new SI [5] was approved. This SI concerns the consideration of the APT 600 MHz band (n105) that has been recently introduced into 3GPP specifications [6]. After the completion of APT 600MHz band, operators have the further demands to combine this 600MHz band with other sub-1GHz bands together to achieve a good performance for the real deployment. However, some challenges were identified for a device with a smart phone form factor to support the combinations of those low bands including 600MHz band. For example, UE RF architecture need to be further studied due to larger antenna size for 600MHz band and some RF requirements need to be evaluated, e.g. MSD. The previous SI on Enhancement for 700/800/900MHz band combinations didn't include the evaluation and studies for 600MHz band. Additionally band 26 is also considered.
+
+## Summary of band combinations considered in the SI
+
+| Configuration | Uplink configuration | Supported operators | The status of fallback mode |
+|--------------------------------|----------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
+| CA_n8-n20-n28 | CA_n8-n20,<br>CA_n8-n28,<br>CA_n20-n28 | Vodafone, Telecom Italia, Orange, Deutsche Telekom | |
+| CA_n5-n8 | CA_n5-n8 | China Telecom, Spark NZ, China Unicom | |
+| CA_n5-n28 | CA_n5-n28 | Spark NZ | |
+| CA_n5A-n105A | CA_n5A-n105A | Spark NZ | DL_n5A-n105A_UL_n5A_BCS0 (New)<br>DL_n5A-n105A_UL_n105A_BCS0 (New) |
+| CA_n28A-n105A | CA_n28A-n105A | Spark NZ | DL_n28A-n105A_UL_n28A_BCS0 (New)<br>DL_n28A-n105A_UL_n105A_BCS0 (New) |
+| CA_n26A-n28A | CA_n26A-n28A | Telstra | DL_n26A-n28A_UL_n28A_BCS0 (Completed in RAN4#106)<br>DL_n26A-n28A_UL_n26A_BCS0 (New) |
+| CA_n5A-n28A-n105A <sup>1</sup> | CA_n5A-n28A | Spark NZ | DL_n5A-n28A_UL_n5A-n28A_BCS0 (Ongoing in a separate WI)<br>DL_n5A-n28A-n105A_UL_n5A_BCS0 (New)<br>DL_n5A-n28A-n105A_UL_n28A_BCS0 (New) |
+| CA_n5A-n28A-n105A <sup>1</sup> | CA_n5A-n105A | Spark NZ | DL_n5A-n105A_UL_n5A-n105A_BCS0 (New)<br>DL_n5A-n28A-n105A_UL_n5A_BCS0 (New)<br>DL_n5A-n28A-n105A_UL_n105A_BCS0 (New) |
+| CA_n5A-n28A-n105A <sup>1</sup> | CA_n28A-n105A | Spark NZ | DL_n28A-n105A_UL_n28A-n105A_BCS0 (New)<br>DL_n5A-n28A-n105A_UL_n28A_BCS0 (New)<br>DL_n5A-n28A-n105A_UL_n105A_BCS0 (New) |
+
+NOTE 1: The study of 3 band combination can only start after completion of 2 bands fallbacks
+
+NOTE 2: Check at RAN4#107 whether CA\_n5A-n28A-n105A could be included in the SI based on study progress for the fall back combinations listed in the above table.
+
+The following aspects need be studied
+
+- UE architecture including n-plexing, PA
+- Study feasibility of low band wideband antenna
+- Performance due to impacts including inter-modulation products
+- Method to manage the inter-modulation product impacts
+
+Note: Revisit in RAN#98 whether additional aspects need to be added.
+
+Power class 3 (PC3) is considered in this study
+
+- 3 Identify potential impacts to relevant RAN4 requirements.
+
+The present document is the technical report for this Study Item.
+
+## 4.1 TR Maintenance
+
+A single company is responsible for introducing all approved TPs in the current TR, i.e. TR editor.
+
+# --- 5 Specific Band combinations
+
+## 5.1 CA\_n5-n8
+
+### 5.1.0 General
+
+Generally, in this study item, some high level implementations were discussed and shown as below.
+
+- 1) Full band n5 and n8 RF filters implementation with option 1 and option2:
+ - Option 1: Only support 1UL/2DL CA. Single UL in n5
+ - Option 2: Support both 1UL/2DL and 2UL/2DL CA. Non-concurrent n5 DL and n8 UL
+
+Note: Potential impacts on RAN2 are observed
+
+- 2) Dedicated RF filters implementation with partial frequency range
+ - Option 3: Support both 1UL/2DL and 2UL/2DL CA. Dedicated filter to allow simultaneous n5 DL and n8 UL
+
+### 5.1.1 UE RF architecture assumption
+
+The following UE RF architectures can be assumed in the future meetings' analysis for CA\_n5-n8: 2 antenna, 3 antenna. The antenna number is the total number of antennas to support Main UL/DL and diversity DL for all bands.
+
+Due to the frequency range overlap between n5 DL and n8 UL, one possibility to enable CA\_n5-n8 operation with 2-antenna implementation is to allow non-simultaneous Rx/Tx between n5 DL and n8 UL or single UL in n5 only to avoid n5 REFSENS impact due to n8 UL transmission. With that the filter isolation between n5 DL and n8 UL would no longer be needed and a triplexer can be used to provide the semi-full-duplex carrier aggregation to a single antenna in the main path, as is shown in Figure 5.1.1-1. On the other hand, since the triplexer center band range is over 5%
+
+bandwidth ratio (band range divided by center frequency) and the frequency gap between center band and n8 DL is only 10 MHz which may pose design challenge on achieving acceptable filter isolation and insertion loss, the feasibility of a single triplexer for CA\_n5-n8 needs to be studied.
+
+
+
+The diagram illustrates the UE architecture for semi-full-duplex CA\_n5-n8. The Main TRx path consists of an antenna connected to a duplexer, which is then connected to two switches (sPnT). These switches are connected to a triplexer, which is further connected to two antennas labeled n5 and n8. The Diversity Rx path follows a similar structure but uses a duplexer instead of a triplexer for the n5 and n8 bands. Below the architecture, two frequency band diagrams are provided for time points @t1 and @t2. The bands are defined as follows: n5 UL (824-835 MHz), n5 DL (880-894 MHz), n8 UL (894-904 MHz), and n8 DL (925-949 MHz). At @t1, the n5 UL band is active, the n5 DL and n8 UL bands are active, and the n8 DL band is active. At @t2, the n5 UL band is active, the n5 DL and n8 UL bands are active, and the n8 DL band is active.
+
+Figure 5.1.1-1: Possible CA\_n5-n8 UE architecture and operation diagram for semi-full-duplex CA. The diagram shows two radio paths: Main TRx and Diversity Rx. The Main TRx path includes an antenna, a duplexer, two switches (sPnT), a triplexer, and two antennas (n5 and n8). The Diversity Rx path includes an antenna, a duplexer, two switches (sPnT), a duplexer, and two antennas (n5 and n8). Below the architecture, two frequency band diagrams are shown for time points @t1 and @t2. The bands are n5 UL (824-835 MHz), n5 DL (880-894 MHz), n8 UL (894-904 MHz), and n8 DL (925-949 MHz). At @t1, n5 UL is active, n5 DL and n8 UL are active, and n8 DL is active. At @t2, n5 UL is active, n5 DL and n8 UL are active, and n8 DL is active.
+
+Figure 5.1.1-1 Possible CA\_n5-n8 UE architecture and operation diagram for semi-full-duplex CA
+
+Another architecture variant with 2-antenna implementation is to move n8 UL to the diversity path as is shown in Figure 5.1.1-2 which may potentially ease the triplexer design in the main TRx path owing to the narrower middle band range and wider frequency separation between n5 DL and n8 DL. The filter design challenge however would be shifted to the diversity TRx path duplexer due to the wider band range to cover n5 DL and n8 UL.
+
+
+
+Figure 5.1.1-2: Possible CA\_n5-n8 UE architecture based on 2-antenna implementation. The diagram shows two transceivers, 'Main TRx' and 'Diversity TRx'. Each is connected to two 'sPnT' (power amplifier) blocks. The 'Main TRx' sPnT blocks are connected to a 3-way multiplexer, which outputs to three antennas labeled 'n5', 'n5', and 'n8'. The 'Diversity TRx' sPnT blocks are connected to a 2-way multiplexer, which outputs to two antennas labeled 'n5' and 'n8'. The 'n5' antenna from the Diversity TRx path is connected to a switch that can select between the Diversity TRx path and the Main TRx path for the n5 signal.
+
+**Figure 5.1.1-2 Possible CA\_n5-n8 UE architecture based on 2-antenna implementation**
+
+For the 3-antenna implementation, the two of the three antenna are used in the main path to aggregate the n5 and n8 signals over the air, as shown in Figure 5.1.1-3. As n5 and n8 signals do not need to be combined through a multiplexer, there is no additional insertion loss in both n5 and n8 main signal paths as compared to single-band implementation.
+
+Having two antenna in the main signal path not only avoids the more complicated multiplexer implementation and the associated additional insertion losses, but also allows narrower frequency coverage for each of the two antenna as compared to single-antenna implementation which can be up to 348 MHz (from n105 to n8) to support all the sub-1GHz bands above 600 MHz as defined in 3GPP. On the other hand, the additional antenna cannot be added without occupying more phone space. Therefore, the feasibility on placing more than two low-band antenna in a smartphone needs to be investigated with the concern of the expected narrower bandwidth and regressed radiating performance due to the limitation in form factor.
+
+
+
+Figure 5.1.1-3: CA\_n5-n8 UE architecture based on the 3-antenna implementation. The diagram shows three transceivers: 'Main TRx 1', 'Main TRx 2', and 'Diversity Rx'. 'Main TRx 1' is connected to two 'sPnT' blocks, which are connected to a 2-way multiplexer, which outputs to two antennas labeled 'n5' and 'n5'. 'Main TRx 2' is connected to two 'sPnT' blocks, which are connected to a 2-way multiplexer, which outputs to two antennas labeled 'n8' and 'n8'. 'Diversity Rx' is connected to two 'sPnT' blocks, which are connected to a 2-way multiplexer, which outputs to two antennas labeled 'n5' and 'n8'.
+
+**Figure 5.1.1-3 CA\_n5-n8 UE architecture based on the 3-antenna implementation**
+
+Despite the 3-antenna implementation can help reduce n8 UL interfering n5 DL via antenna isolation which however is far from sufficient even under the restricted frequency ranges for CA operation where n8 UL does not overlap with n5 DL. Therefore, semi-full-duplex operation with non-simultaneous Rx/Tx between n5 DL and n8 UL as diagramed in Figure 5.1.1-1 is still required for the CA combination.
+
+In consideration of the operation frequency ranges restriction for this specific band combination as is shown below,
+
+- n5r: UL 824 - 835 MHz; DL 869 - 880 MHz
+
+- n8r: UL 904 - 915 MHz; DL 949 - 960 MHz
+
+
+
+The diagram shows the following frequency bands and ranges:
+
+- n5 UL:** 824 - 835 MHz (Yellow block)
+- n5 DL:** 869 - 880 MHz (Yellow block)
+- n8 UL:** 904 - 915 MHz (Green block)
+- n8 DL:** 925 - 949 MHz (Green block)
+- Additional frequencies:** 835, 849, 880, 894, 915, 960 MHz are marked at the boundaries of the blocks.
+- Total Range:** A double-headed arrow at the bottom indicates a range from 824 MHz to 960 MHz, labeled as 136 MHz.
+
+Frequency spectrum diagram showing n5 and n8 bands. n5 UL is 824-835 MHz (yellow), n5 DL is 869-880 MHz (yellow), n8 UL is 904-915 MHz (green), and n8 DL is 925-949 MHz (green). A 136 MHz range is indicated from 824 to 960 MHz.
+
+Figure 5.1.1-4 CA\_n5-n8 restricted spectrum range
+
+Dedicated filter implementation may be considered to potentially enable 2UL/2DL simultaneous operation. Due to the frequency range restriction on the dedicated filters, additional full-band duplexers for either or both n5 and n8 would be required in order to support the single-band full-band operation. Figure 5.1.1-5 and Figure 5.1.1-6 show the architecture diagrams with dedicated quadplexer in main TRx path based on 2-antenna implementation where the former uses both partial ranges for n5 and n8 in the quadplexer and the latter uses partial range only for n8 UL in the quadplexer.
+
+
+
+The diagram illustrates the RF architecture for CA\_n5-n8. It consists of two main paths: **Main TRx** and **Diversity Rx**.
+
+- Main TRx Path:**
+ - Antenna → Duplexer → Two **sPnT** blocks.
+ - The first **sPnT** block connects to a set of filters for **n5** (two filters) and **n5r** (two filters).
+ - The second **sPnT** block connects to a set of filters for **n8r** (two filters) and **n8** (two filters).
+ - Each filter connects to an antenna (represented by a triangle).
+ - Labels at the bottom: n5, n5, n5r, n5r, n8r, n8r, n8, n8.
+- Diversity Rx Path:**
+ - Antenna → Duplexer → Two **sPnT** blocks.
+ - The first **sPnT** block connects to a filter for **n5**.
+ - The second **sPnT** block connects to a filter for **n8**.
+ - Labels at the bottom: n5, n8.
+
+Block diagram of CA\_n5-n8 architecture with dedicated quadplexer using partial ranges in both n5 and n8. It shows Main TRx and Diversity Rx paths with sPnT and various filter/antenna configurations for n5, n5r, n8r, and n8.
+
+Figure 5.1.1-5 CA\_n5-n8 architecture with dedicated quadplexer using partial ranges in both n5 and n8
+
+
+
+This diagram is similar to Figure 5.1.1-5 but with a different filter configuration for the Main TRx path. It also consists of **Main TRx** and **Diversity Rx** paths.
+
+- Main TRx Path:**
+ - Antenna → Duplexer → Two **sPnT** blocks.
+ - The first **sPnT** block connects to a set of filters for **n5** (two filters) and **n8r** (one filter).
+ - The second **sPnT** block connects to a set of filters for **n8** (two filters).
+ - Labels at the bottom: n5, n5, n8r, n8, n8, n8.
+- Diversity Rx Path:**
+ - Antenna → Duplexer → Two **sPnT** blocks.
+ - The first **sPnT** block connects to a filter for **n5**.
+ - The second **sPnT** block connects to a filter for **n8**.
+ - Labels at the bottom: n5, n8.
+
+Block diagram of CA\_n5-n8 architecture with dedicated quadplexer using partial ranges in both n5 and n8. It shows Main TRx and Diversity Rx paths with sPnT and various filter/antenna configurations for n5, n5r, n8r, and n8.
+
+**Figure 5.1.1-6 CA\_n5-n8 architecture with dedicated quadruplexer using partial range in n8 UL only**
+
+Figure 5.1.1-7 and Figure 5.1.1-8 show the architecture diagrams with dedicated duplexers for both n5 and n8 and n8 UL only respectively in main TRx path based on 3-antenna implementation.
+
+Dedicated filter based on specific frequency range restriction for operation bands usually is not a common practice in UE implementation as it adds additional cost and area to the devices.
+
+
+
+The diagram illustrates the RF architecture for CA\_n5-n8 with a dedicated quadruplexer. It consists of three antenna paths:
+
+
+- Main TRx 1:** Antenna → Duplexer → sPnT → Quadruplexer → n5r (Tx), n5r (Rx), n5 (Tx), n5 (Rx).
+- Main TRx 2:** Antenna → Duplexer → sPnT → Quadruplexer → n8r (Tx), n8r (Rx), n8 (Tx), n8 (Rx).
+- Diversity Rx:** Antenna → Duplexer → sPnT → Quadruplexer → n5 (Rx), n8 (Rx).
+
+Figure 5.1.1-6: CA\_n5-n8 architecture with dedicated quadruplexer using partial range in n8 UL only. The diagram shows three antenna paths: Main TRx 1, Main TRx 2, and Diversity Rx. Each path has a duplexer connected to an sPnT block. Main TRx 1 and 2 have quadruplexers that connect to n5r/n5 and n8r/n8 bands. Diversity Rx has a quadruplexer that connects to n5 and n8 bands.
+
+**Figure 5.1.1-7 CA\_n5-n8 architecture using dedicated duplexers with partial ranges in both n5 and n8**
+
+
+
+The diagram illustrates the RF architecture for CA\_n5-n8 using dedicated duplexers. It consists of three antenna paths:
+
+
+- Main TRx 1:** Antenna → Duplexer → sPnT → Duplexer → n5 (Tx), n5 (Rx).
+- Main TRx 2:** Antenna → Duplexer → sPnT → Duplexer → n8r (Tx), n8r (Rx) → Duplexer → n8 (Tx), n8 (Rx).
+- Diversity Rx:** Antenna → Duplexer → sPnT → Duplexer → n5 (Rx), n8 (Rx).
+
+Figure 5.1.1-7: CA\_n5-n8 architecture using dedicated duplexers with partial ranges in both n5 and n8. The diagram shows three antenna paths: Main TRx 1, Main TRx 2, and Diversity Rx. Each path has a duplexer connected to an sPnT block. Main TRx 1 has a duplexer for n5. Main TRx 2 has duplexers for n8r and n8. Diversity Rx has a duplexer for n5 and n8.
+
+**Figure 5.1.1-8 CA\_n5-n8 architecture using dedicated duplexers with partial range in n8 UL only**
+
+
+
+Figure 5.1.1-9: CA\_n5-n8 architecture using dedicated triplexers with partial range in n8 and n5. The diagram shows two identical antenna architectures. Each consists of a DIP (Duplexer) connected to two SPNT (Single Pole, Double Throw) switches. The first SPNT is connected to an n5r TX (Transceiver) and the second SPNT is connected to an n8r RX (Receiver). The n5r TX is connected to an antenna, and the n8r RX is connected to another antenna. This configuration allows for simultaneous transmission and reception on different bands (n5 and n8) using dedicated triplexers.
+
+Figure 5.1.1-9 CA\_n5-n8 architecture using dedicated triplexers with partial range in n8 and n5
+
+In the architecture of Figure 5.1.1-9, dedicated triplexers are used. In this architecture, UL's are transmitted from different antennas, which may help in optimizing the TRP for each of the UL's resulting in better coverage.
+
+### 5.1.2 Common for 1 band UL and 2 bands UL of CA\_n5-n8
+
+#### 5.1.2.1 Operating bands for CA
+
+UE should support the full range of spectrum for single band operations on both n5 and n8
+
+Use the following frequency ranges for further discussion for spectrum restriction to support uplink CA\_n5-n8.
+
+Table 5.1.2.1-1: CA band combination of band n5+n8
+
+| | UL | DL |
+|----------------------|-----------------|-----------------|
+| Frequency 1 (800MHz) | 824MHz - 835MHz | 869MHz - 880MHz |
+| Frequency 2 (900MHz) | 904MHz - 915MHz | 949MHz - 960MHz |
+
+The frequency relation between band n8 and n5 is shown below as UL band n8 is overlapping with DL band n5
+
+
+
+Figure 5.1.2.1-1: The frequency relation between band n8 and n5. The diagram shows a frequency spectrum from 824 MHz to 960 MHz. The n5 UL band is shown from 824 MHz to 835 MHz. The n5 DL band is shown from 869 MHz to 880 MHz. The n8 UL band is shown from 904 MHz to 915 MHz. The n8 DL band is shown from 949 MHz to 960 MHz. The diagram also indicates the overlap between the n8 UL band and the n5 DL band, which is highlighted in orange. A horizontal double-headed arrow at the bottom indicates a total span of 136 MHz.
+
+Figure 5.1.2.1-1: The frequency relation between band n8 and n5
+
+#### 5.1.2.2 Channel bandwidths per operating band for CA
+
+Based on WF R4-2214445, BCS0 for CA\_n5A-n8A can be specified as below.
+
+Table 5.1.2.2-1: Supported bandwidths per CA band combination of band n5+n8
+
+| NR CA configuration | Uplink CA configuration or single uplink carrier | NR Band | Channel bandwidth (MHz) | Bandwidth combination set |
+|---------------------|--------------------------------------------------|---------|-------------------------|---------------------------|
+| CA_n5A-n8A | CA_n5A-n8A | n5 | 5, 10 | 0 |
+| | | n8 | 5, 10 | |
+
+#### 5.1.2.3 UE co-existence studies
+
+Table 5.1.2.3-1/2 summarizes frequency ranges where harmonics and/or harmonics mixing occur for CA\_n5-n8.
+
+Table 5.1.2.3-1: Impact of UL/DL Harmonic
+
+| Band | UL Low Band Edge | UL High Band Edge | DL Low Band Edge | DL High Band Edge | 2nd Harmonic | | 3rd Harmonic | | 4th Harmonic | | 5th Harmonic | |
+|------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|
+| | | | | | UL Low Band Edge | UL High Band Edge | UL Low Band Edge | UL High Band Edge | UL Low Band Edge | UL High Band Edge | UL Low Band Edge | UL High Band Edge |
+| n5 | 824 | 849 | 869 | 894 | 1648 | 1698 | 2472 | 2547 | 3296 | 3396 | 4120 | 4245 |
+| n8 | 880 | 915 | 925 | 960 | 1760 | 1830 | 2640 | 2745 | 3520 | 3660 | 4400 | 4575 |
+
+Table 5.1.2.3-2: Impact of UL/DL Harmonic mixing
+
+| Band | UL Low Band Edge | UL High Band Edge | DL Low Band Edge | DL High Band Edge | 2nd Harmonic | | 3rd Harmonic | | 4th Harmonic | | 5th Harmonic | |
+|------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|
+| | | | | | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge |
+| n5 | 824 | 849 | 869 | 894 | 1738 | 1788 | 2607 | 2682 | 3476 | 3576 | 4345 | 4470 |
+| n8 | 880 | 915 | 925 | 960 | 1850 | 1920 | 2775 | 2880 | 3700 | 3840 | 4625 | 4800 |
+
+Based on the analysis above, there is no need to specify harmonics and harmonics mixing exception for CA\_n5-n8 as we didn't specify them in current spec.
+
+#### 5.1.2.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n5-n8, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ are given in the tables below considering both 2-antenna and 3-antenna implementations. If 3-antenna implementation is assumed, there isn't any additional insertion loss observed for CA\_n5-n8 compared with single carrier operation. If it's assumed to derive the the delta Tib and Rib requirements for CA\_n5-n8 based on 3-antenna implementation, all the values can be zero. If 2-antenna implementation is assumed to derive these values, the some delta Tib and Rib values for CA\_n5-n8 are provided from interested companies as below.
+
+Table 5.1.2.4-1: $\Delta T_{IB,c}$ for 2-antenna implementation
+
+| Inter-band CA Configuration | NR Band | Huawei | Skyworks | Qualcomm |
+|-----------------------------|---------|--------|----------|----------|
+| CA_n5-n8 | n5 | 0.4 | 0.2 | 0.5 |
+| | n8 | 0.4 | 0.4 | 0.5 |
+
+Table 5.1.2.4-2: $\Delta R_{IB,c}$ for 2-antenna implementation
+
+| Inter-band CA Configuration | NR Band | Huawei | Skyworks | Qualcomm |
+|-----------------------------|---------|--------|----------|----------|
+| CA_n5-n8 | n5 | 0 | 0.3 | 0.5 |
+| | n8 | 0 | 0.2 | 0.5 |
+
+#### 5.1.2.5 REFSENS evaluation
+
+For option 1 of full band n5 and n8 RF filters implementation, the scheduling is restricted as DL\_n5-n8\_UL\_n5 and the concurrent operation between DL band n5 and UL band n8 can't work. There may be some MSD for band n8 DL due to band n5 UL interference. Some legacy filters exhibit the flyback effect into n8 DL reducing the rejection of the n5 TX OOB leakage for no MSD
+
+For option 3 of dedicated RF filters implementation with partial frequency range, the MSD test point and values due to cross band isolation between DL band n5 and UL band n8 in Table 5 are provided referring to R4-2300759.
+
+Table 5.1.2.5-1: n8R UL cross band MSD in n5 for CA\_n5-n8
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|--------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n8 | n5 | 909 | 10 | 15 | 25 (RBstart=0) | 877.5 | 5 | [12.3] | ACLR2 |
+
+### 5.1.3 Specific for 2 bands UL of CA\_n5-n8
+
+#### 5.1.3.0 General
+
+Option 2 full band n5 and n8 RF filters implementation can support both DL\_n8\_UL\_n5-n8 and DL\_n5-n8\_UL\_n5 features.
+
+Option 3 dedicated RF filter(s) implementation with partial frequency range can support DL\_n5-n8\_UL\_n5-n8 feature.
+
+Thus, the following technical analysis in clause 5.1.3 is based on these kinds of candidate options and implementations.
+
+#### 5.1.3.1 Maximum output power for inter-band CA
+
+Power class 3 is assumed for UL CA\_n5-n8.
+
+#### 5.1.3.2 UE co-existence studies
+
+Table 5.1.3.2-1 lists Band n5 + Band n8 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis.
+
+**Table 5.1.3.2-1: Band n5 and Band n8 UL IMD products with frequency range restriction**
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------|-----------------------|----------------------|-----------------------|
+| UL frequency (MHz) | 824 | 835 | 904 | 915 |
+| 2 <sup>nd</sup> order IMD products | fy_low – fx_high | fy_high – fx_low | fy_low + fx_low | fy_high + fx_high |
+| IMD frequency limits (MHz) | 69 | 91 | 1728 | 1750 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low – fy_high | 2*fx_high – fy_low | 2*fy_low – fx_high | 2*fy_high – fx_low |
+| IMD frequency limits (MHz) | 733 | 766 | 973 | 1006 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high |
+| IMD frequency limits (MHz) | 2552 | 2585 | 2632 | 2665 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low – 1*fy_high | 3*fx_high – 1*fy_low | 3*fy_low – 1*fx_high | 3*fy_high – 1*fx_low |
+| IMD frequency limits (MHz) | 1557 | 1601 | 1877 | 1921 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low + 1*fy_low | 3*fx_high + 1*fy_high | 3*fy_low + 1*fx_low | 3*fy_high + 1*fx_high |
+| IMD frequency limits (MHz) | 3376 | 3420 | 3536 | 3580 |
+| Two-tone 4 <sup>th</sup> order IMD products | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low | 2*fy_low + 2*fy_low | 2*fy_high + 2*fy_high |
+| IMD frequency limits (MHz) | 182 | 138 | 3456 | 3500 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low – 4*fy_high | fx_high – 4*fy_low | fy_low – 4*fx_high | fy_high – 4*fx_low |
+| IMD frequency limits (MHz) | 2836 | 2781 | 2436 | 2381 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low – | 2*fx_high – | 2*fy_low – | 2*fy_high – |
+
+| | $3*f_y\_high $ | $3*f_y\_low $ | $3*f_x\_high $ | $3*f_x\_low $ |
+|---------------------------------------------|-----------------------------|-------------------------------|-----------------------------|-------------------------------|
+| IMD frequency limits (MHz) | 1097 | 1042 | 697 | 642 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low + 4*f_y\_low $ | $ f_x\_high + 4*f_y\_high $ | $ f_y\_low + 4*f_x\_low $ | $ f_y\_high + 4*f_x\_high $ |
+| IMD frequency limits (MHz) | 4440 | 4495 | 4200 | 4255 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low + 3*f_y\_low $ | $ 2*f_x\_high + 3*f_y\_high $ | $ 2*f_y\_low + 3*f_x\_low $ | $ 2*f_y\_high + 3*f_x\_high $ |
+| IMD frequency limits (MHz) | 4360 | 4415 | 4280 | 4335 |
+
+Based on Table 5.1.3.2-1, there is no IMD issue for CA\_n5-n8 with the following frequency range restriction.
+
+n5 UL: 824 MHz – 835 MHz DL: 869 MHz – 880 MHz;
+
+n8 UL: 904 MHz – 915 MHz DL: 949 MHz – 960 MHz.
+
+Table 5.1.3.2-2 lists the protected bands required for the 2UL bands CA configuration.
+
+**Table 5.1.3.2-2: Protected bands for the 2UL bands CA configuration**
+
+| NR CA Configuration | Spurious emission | | | | | |
+|---------------------|-----------------------------------------------------------|-----------------------|------------------|---------------------|-----------|------|
+| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE |
+| CA_n5-n8 | E-UTRA Band 1, 28, 31, 34, 38, 40, 45, 50, 51, 65, 73, 74 | $F_{DL\_low}$ | - $F_{DL\_high}$ | -50 | 1 | |
+| | E-UTRA Band 3, 7, 41, 42, 43, 52<br>NR Band n77, n78, n79 | $F_{DL\_low}$ | - $F_{DL\_high}$ | -50 | 1 | 2 |
+| | E-UTRA Band 8 | $F_{DL\_low}$ | - $F_{DL\_high}$ | -50 | 1 | 4 |
+| | E-UTRA Band 11, 21 | $F_{DL\_low}$ | - $F_{DL\_high}$ | -50 | 1 | |
+| | Frequency range | 1884.5 | - 1915.7 | -41 | 0.3 | 3 |
+
+NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{CRB} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.
+
+NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 -1915.7 MHz
+
+NOTE 4: These requirements also apply for the frequency ranges that are less than $F_{OOb}$ (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth.
+
+#### 5.1.3.3 REFSSENS evaluation
+
+Based on the assumption of restricted frequency range for CA\_n5-n8, there is no MSD issue due to intermodulation interference. 2UL Cross-band MSD may be needed.
+
+### 5.1.4 Feasible RF implementations
+
+Referring to clause 5.1.0 and 5.1.1 UE RF architecture assumption, it can be observed that two sets of different RF implementations are included currently:
+
+One is full band n5 and n8 RF filters implementation.
+
+Another one is dedicated RF filters implementation with partial frequency range.
+
+These two implementation may have different RF requirements and scheduling restriction. In study phase, we list all the implementations on the table and further trade off each implementation as below.
+
+**Table 5.1.4-1: Trade-off between the feasible RF implementations**
+
+| Type of implementation | Options | Pros | Cons |
+|------------------------------------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Full band n5 and n8 RF filters implementation | Option 1 | 1. Current RF components can be reused easily.<br>2. The same RF filters can support both single carrier operation and CA operation.<br>3. UE cost may not be improved too much. | 1. UL_n5-n8 can't be supported. Only DL_n5-n8_UL_n5 can be supported. |
+| | Option 2 | 1. Current RF components can be reused.<br>2. The same RF filters can support both single carrier operation and CA operation.<br>3. Compared to option 1, DL_n8_UL_n5-n8 can be supported additionally. | 1. Non-concurrent n5 DL and n8 UL limiting DL throughput<br>2. At least one additional n8 RX filter is required compared to option 1<br>3. There may be RF additional performance impacts caused by managing the non-concurrency between n5DL and n8UL<br>4. Potential impacts on RAN2 are observed |
+| Dedicated RF filters implementation with partial frequency range | Option 3 | 1. DL_n5-n8_UL_n5-n8 can be supported by UE within partial frequency range. Operators' demands can be met.<br>2. There is no scheduling restriction for CA operation, but the specific partial frequency range. | 1. At least, but not necessary limited to one n8 UL dedicated filter with UL partial frequency range need to be developed for this specific CA operation.<br>2. n5 RX filtering may be impacted to avoid n8 UL at 904-914 blocking n5RX<br>3. Dedicated filter and full band filter need to be switched between single carrier operation and CA operation. |
+
+As all the implementations are not excluded and UE can support them optionally, a solution is needed to further distinguish these different implementations. The following options can be further discussed.
+
+- Option 1: New bands would be required.
+- Option 2: New bands would not be required. An optional signalling/capability solution can be designed for the BS and UE to distinguish these different implementations.
+- Option 3: Other are not precluded.
+
+### 5.1.5 Output for 2UL/2DL CA\_n5-n8 during the work item phase
+
+#### Three UE implementations for CA\_n5-n8:
+
+In the discussion for UE implementations for CA\_n5-n8, there were three options from the SI phase:
+
+- 1) Full band n5 and n8 RF filters implementation with option 1 and option2:
+ - Option 1: Only support 1UL/2DL CA. Single UL in n5
+ - Option 2: Support both 1UL/2DL and 2UL/2DL CA. Non-concurrent n5 DL and n8 UL
+- 2) Dedicated RF filters implementation with partial frequency range
+ - Option 3: Support both 1UL/2DL and 2UL/2DL CA. Dedicated filter to allow simultaneous n5 DL and n8 UL
+
+According to the updated WID for 700/800/900MHz band combinations in RAN#101, uplink is only in band n5 for CA\_n5-n8. Thus, only Option 1 is specified in Rel-18 specification. However, if operator requests this 2UL/2DL CA\_n5-n8 in future release, it should be further decided whether option 2, option 3 or both are specified.
+
+If UE capabilities need to be updated or defined to distinguish different implementations, it's encouraged to send LS to RAN2 for UE capabilities as soon as RAN4 has decided which options to specify.
+
+#### CA\_n5-n8 MSD values:
+
+The following test configuration and MSD from n5 UL to n8 DL are agreed in Table 5.1.3.4-1 and the requirements are already specified in Rel-18 specification.
+
+**Table 5.1.3.4-1: CA\_n5-n8 MSD value for 1U/2D n5UL/n8DL**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n5 | n8 | 844 | 10 | 15 | 25 (RBstart=27) | 951.5 | 5 | 2.8 | >ACLR2 |
+
+The following test configuration and MSD from n8 UL to n5 DL are agreed in Table 5.1.3.4-2 and the requirements apply if the Option 3 is specified.
+
+**Table 5.1.3.4-2: CA\_n5-n8 MSD value for 1U/2D n8UL/n5DL**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n8 | n5 | 909 | 10 | 15 | 25 (RBstart=0) | 877.5 | 5 | 12.3 | >ACLR2 |
+
+##### Clarification on the scenario:
+
+The RAN4 discussion for the 2UL scenario for CA\_n5-n8 with the scheduling restriction of non-concurrent n5 DL and n8 UL is based on the assumption that UE is configured by RRC with two UL and two DL, i.e. not two UL and one DL. Based on that assumption, RAN4 has the following answers for the questions in the LS R2-2306862.
+
+**Question 1:** Does RAN4 see problem if cross carrier scheduling is used in this scenario i.e. PCell (n8) scheduling SCell (n5)?
+
+##### Answer to Question 1:
+
+Cross carrier scheduling is transparent from RAN4's perspective. RAN4 didn't see any impact to RAN4 specifications.
+
+**Question 2:** What are RAN4 understanding regarding RRM measurements in this kind of scenario? Does UE need to measure the cell with UL only (n5) (e.g. for SCell addition/change/release purpose)?
+
+##### Answer to Question 2:
+
+RAN4 expects measurement of the SCell (n5) in this scenario is needed.
+
+In RAN4 understanding, network would avoid the collision with the DL transmission of SCell (n5) when scheduling the UL in n8.
+
+No impact to existing RRM specifications is seen from RAN4 perspective.
+
+##### How to distinguish UE implementation for CA\_n5-n8?
+
+###### Situation 1: if Option 1 is supported in Rel-18, then
+
+| Implementation | Applicable RRC configuration | How to distinguish UE implementation |
+|------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------|
+| Full band n5 and n8 RF filters implementation:<br>Option 1: Only support 1UL/2DL CA. Single UL in n5 | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+
+In addition, one note can be added in RAN4 that band n8 can only be configured as DL Scell for band combinations including DL CA\_n5-n8.
+
+##### **Situation 2: if Option 1 and option 2 are supported in Rel-18.**
+
+| Implementation | Applicable RRC configuration | How to distinguish UE implementation |
+|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Full band n5 and n8 RF filters implementation:<br>Option 1: Only support 1UL/2DL CA. Single UL in n5 | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+| Full band n5 and n8 RF filters implementation:<br>Option 2: Support both 1UL/2DL and 2UL/2DL CA. Non-concurrent n5 DL and n8 UL | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+| | (UL: n5+n8, DL: n5+n8) or potential (UL: n5+n8, DL: n5+n8+n78) in future | <b>Alt1:</b> One UE capability <b>AA</b> is needed to indicate that UE can't support Non-concurrent n5 DL and n8 UL.<br><b>Alt2:</b> No need to introduce UE capability. But it should be clarified that Non-concurrent n5 DL and n8 UL is supported by default in RAN4 general spec, only if UE reports UL CA_n5-n8. |
+
+###### **Situation 3: if Option 1 and option 3 are supported in Rel-18.**
+
+| Implementation | Applicable RRC configuration | How to distinguish UE implementation |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Full band n5 and n8 RF filters implementation:<br>Option 1: Only support 1UL/2DL CA. Single UL in n5 | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+| Dedicated RF filters implementation with partial frequency range<br>Option 3: Support both 1UL/2DL and 2UL/2DL CA. Dedicated filter to allow simultaneous n5 DL and n8 UL | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE can just report this applicable RRC configuration. |
+| | (UL: n8, DL: n5+n8) or (UL: n5+n8, DL: n5+n8) or potential (UL: n5+n8, DL: n5+n8+n78) in future | <b>Alt1:</b> One UE capability <b>BB</b> is needed to indicate that the UL frequency range of band n8 is restricted as 904~915 MHz.<br><b>Alt2:</b> No need to introduce UE capability. But it should be clarified that UL frequency range of band n8 is restricted as 904~915 MHz is supported by default in RAN4 general spec only if UE report n5 DL and n8 UL in one Band combination simultaneously.<br><b>Alt3:</b> One UE capability <b>BB</b> is introduced. The applicability of the UE capability in 38.306 refers to a NOTE in RAN4 spec to elaborate the UL frequency range of band n8 is restricted as 904~915 MHz and supported channel bandwidths. |
+
+##### **Situation 4: if Option 1, option 2 and option 3 are supported in Rel-18.**
+
+| Implementation | Applicable RRC configuration | How to distinguish UE implementation |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Full band n5 and n8 RF filters implementation:<br>Option 1: Only support 1UL/2DL CA. Single UL in n5 | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+| Full band n5 and n8 RF filters implementation:<br>Option 2: Support both 1UL/2DL and 2UL/2DL CA. Non-concurrent n5 DL and n8 UL | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+| | (UL: n5+n8, DL: n5+n8) or potential (UL: n5+n8, DL: n5+n8+n78) in future | One UE capability <b>AA</b> is needed to indicate that UE can't support Non-concurrent n5 DL and n8 UL. |
+| Dedicated RF filters implementation with partial frequency range<br>Option 3: Support both 1UL/2DL and 2UL/2DL CA. Dedicated filter to allow simultaneous n5 DL and n8 UL | (UL: n5, DL: n5+n8) | There is no need to indicate additional UE capability. UE just reports the applicable CA configuration. |
+| | (UL: n8, DL: n5+n8) or (UL: n5+n8, DL: n5+n8) or potential (UL: n5+n8, DL: n5+n8+n78) in future | <b>Alt 1:</b> One UE capability <b>BB</b> is needed to indicate that the UL frequency range of band n8 is restricted as 904~915 MHz.<br><b>Alt 2:</b> One UE capability <b>AA</b> is needed to indicate that UE can't support Non-concurrent n5 DL and n8 UL, which means UE will support 2UL CA based on dedicated RF filters with band n8 restricted as 904~915 MHz.<br><b>Alt3:</b> One UE capability <b>BB</b> is introduced. The applicability of the UE capability in 38.306 refers to a NOTE in RAN4 spec to elaborate the UL frequency range of band n8 is restricted as 904~915 MHz and supported channel bandwidths.<br>NOTE: Other options to distinguish between options are not precluded |
+
+## 5.2 CA\_n5-n28
+
+### 5.2.1 UE RF architecture assumption
+
+The n5 filter parameter assumption in the analysis is based on without sharing path of band n26.
+
+The UE RF architectures with 2 antenna and 3 antenna can be assumed in the feasibility study for CA\_n5-n28. The antenna number is the total number of antennas to support Main UL/DL and diversity DL for all bands. Figure 5.2.1.0-1 shows the aggregated spectrum allocation for CA\_n5-n28 where no frequency range restriction has been indicated for either of the constituent bands.
+
+
+
+Figure 5.2.1.0-1: CA\_n5-n28 aggregated spectrum allocation diagram. The diagram shows four frequency blocks: n28 UL (703-748 MHz), n28 DL (758-803 MHz), n5 UL (824-849 MHz), and n5 DL (869-894 MHz). A horizontal double-headed arrow at the bottom indicates a total aggregated spectrum width of 191 MHz, spanning from 703 MHz to 894 MHz.
+
+**Figure 5.2.1.0-1 CA\_n5-n28 aggregated spectrum allocation**
+
+#### 5.2.1.1 UE RF architecture with two antennas
+
+For CA\_n5-n28 with 2-antenna implementation, there are two potential UE RF architectures as shown in Figure 5.2.1.1-1.
+
+
+
+Figure 5.2.1.1-1: Potential UE architecture variants to support CA\_n5-n28 with 2 antenna. The diagram shows two variants, (a) and (b). Variant (a) shows a 'Main TRx' connected to a 'Diversity Rx'. The Main TRx is connected to a quadplexer (n28UL+n28DL+n5UL+n5DL) which is then connected to two antennas. The Diversity Rx is connected to a duplexer (n5DL+n28DL) which is also connected to two antennas. Variant (b) shows a 'Main TRx' connected to a 'Diversity TRx'. The Main TRx is connected to a triplexer (n5UL+n5DL+n28DL) which is then connected to two antennas. The Diversity TRx is connected to a triplexer (n28UL+n28DL+n5DL) which is also connected to two antennas.
+
+**Figure 5.2.1.1-1 Potential UE architecture variants to support CA\_n5-n28 with 2 antenna**
+
+The topology for 2 antenna architecture a is listed as below.
+
+- 1) n28UL+n28DL+n5UL+n5DL quadplexer on antenna 1
+- 2) n5DL+n28DL duplexer on antenna 2
+
+The topology for 2 antenna architecture b is listed as below.
+
+- 1) n5UL+n5DL+n28DL triplexer on antenna 1
+- 2) n28UL+n28DL+n5DL triplexer on antenna 2
+
+[Considering the maximum simultaneously covered spectrum range and closely spaced UL and DL bands, the following challenges and issues impacting UE RF performance for 2-antenna architecture variant (a) can be anticipated:
+
+- The main antenna design needs to cover the entire spectrum range of 191 MHz simultaneously as shown in Figure 5.2.1.1-1, which is equivalent to a 24% bandwidth ratio and that would exceed the bandwidth ratio for a typical planar antenna design in a smartphone. As a result, the radiative performance for the combination likely would be compromised.
+- The feasibility of a single quadplexer is questionable as n28 alone already requires a dual duplexer to reduce the band range to duplex gap ratio in order to achieve the acceptable filter isolation and insertion loss performance. Dual quadplexer has the implication on UE front-end design complexity, area, and cost impacts.
+- RESENS degradation (MSD) on n28 DL caused by frequency proximity between n5 UL and n28 DL and insufficient cross-band isolation.
+
+For 2-antenna architecture variant (b), the following challenges and issues impacting UE RF performance can be anticipated:
+
+- Compared to variant (a), though the main path frequency range is reduced from 191 MHz to 136 MHz, the diversity path frequency range however is increased from 136 MHz to 191 MHz. From antenna design perspective, the same challenge with 24% antenna bandwidth ratio as in variant (a) is expected.
+- The feasibility of a single triplexer for diversity path is questionable as n28 alone already requires a dual duplexer to reduce the band range to duplex gap ratio in order to achieve the acceptable filter isolation and insertion loss performance. Dual triplexer in diversity path in conjunction with a single or dual triplexer in main path has the implication on UE front-end design complexity, area, and cost impacts.
+
+- REFSENS degradation (MSD) on n28 DL caused by frequency proximity between n5 UL and n28 DL and insufficient cross-band isolation.]
+
+#### 5.2.1.2 UE RF architecture with three antennas
+
+For CA\_n5-n28 with 3-antenna implementation, the following UE RF architectures can be considered, as shown in Figure 5.2.1.2-1.
+
+
+
+Figure 5.2.1.2-1: CA\_n5-n28 UE architecture based on the 3-antenna implementation. The diagram shows three antenna paths. Antenna 1 (Main TRx 1) is connected to a duplexer for n28 (UL and DL) and a switch that selects between n28 and n5. Antenna 2 (Main TRx 2) is connected to a duplexer for n5 (UL and DL) and a switch that selects between n5 and n28. Antenna 3 (Diversity Rx) is connected to a duplexer for n28 (UL and DL) and a switch that selects between n28 and n5. Each antenna path includes an sPnT (Switch/Power Network) block.
+
+Figure 5.2.1.2-1 CA\_n5-n28 UE architecture based on the 3-antenna implementation
+
+The topology for the above 3 antenna architecture is listed as below:
+
+- 1) n28UL+n28DL duplexer on antenna 1
+- 2) n5UL+n5DL duplexer on antenna 2
+- 3) n5DL+n28DL duplexer on antenna 3
+
+### 5.2.2 Common for 1 band UL and 2 bands UL of CA\_n5-n28
+
+#### 5.2.2.0 General
+
+According to the current spec TS 38.101-1, DL CA\_n5A-n28A\_BCS0 has been specified. Thus, some of RF requirements can be reused as below.
+
+#### 5.2.2.1 Operating bands for CA
+
+Table 5.2.2.1-1: CA band combination of band n5+n28
+
+| NR Band | Uplink (UL) band | | Downlink (DL) band | | Duplex mode | |
+|---------|------------------------------|---|------------------------------|---------|-------------|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low} - F_{UL\_high}$ | | $F_{DL\_low} - F_{DL\_high}$ | | | |
+| n5 | 824 MHz | – | 849 MHz | 869 MHz | FDD | |
+| n28 | 703 MHz | – | 748 MHz | 758 MHz | FDD | |
+
+#### 5.2.2.2 Channel bandwidths per operating band for CA
+
+Referring to table 5.5A.3.1-1e of TS 38.101-1, DL\_n5A-n28A\_BCS0 has been specified
+
+#### 5.2.2.3 UE co-existence studies
+
+There is no need to specify harmonics and harmonics mixing exception for CA\_n5-n28 as we didn't specify them in current spec.
+
+#### 5.2.2.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n5-n28 with 2 antenna implementation, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values has been specified in TS 38.101-1.
+
+Referring to contribution R4-2300657, it is suggest to reuse the DC\_28\_n5 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values with an additional 0.2dB to all to enable the two-antenna n-plexers in the future and including the support of full band n28, which are shown below:
+
+**Table 5.2.2.4-0: $\Delta T_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5A-n28A | n5 | 0.7 |
+| | n28 | 0.7 |
+
+**Table 5.2.2.4-0a: $\Delta R_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5A-n28A | n5 | 0.2 |
+| | n28 | 0.2 |
+
+For CA\_n5-n28 with 3 antenna implementation, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values are shown below.
+
+**Table 5.2.2.4-1: $\Delta T_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5A-n28A | n5 | 0 |
+| | n28 | 0 |
+
+**Table 5.2.2.4-2: $\Delta R_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5A-n28A | n5 | 0 |
+| | n28 | 0 |
+
+#### 5.2.2.5 REFSENS evaluation
+
+For CA\_n5-n28 with 2 antennas implementation, referring to contribution R4-2202036, the n28 MSD evaluation for CA\_n5-n28 is shown as below.
+
+| | | n28A MSD due to n5 20MHz L <sub>crb</sub> =20RB0 noise | | | | | | | | | |
+|-------------------------------------------------------|----------|--------------------------------------------------------|-------|------------------|-------|------------------|-------|------------------|-------|------------------|-------|
+| | | n28A upper 5MHz | | n28A upper 10MHz | | n28A upper 15MHz | | n28A upper 20MHz | | n28A upper 30MHz | |
+| Measured Tx noise in Rx band in channel level (PAout) | [dBm] | -35.7 | | -34.5 | | -34.3 | | -34.2 | | -34.2 | |
+| Tx-Rx duplexer isolation | [dB] | 45 | | 45 | | 45 | | 45 | | 45 | |
+| Tx-Antenna duplexer isolation | [dB] | 40 | | 40 | | 40 | | 40 | | 40 | |
+| Diplexer isolation / LNA to ant insertion loss | [dB] | 4 | | 4 | | 4 | | 4 | | 4 | |
+| Antenna isolation | [dB] | 0 | 10 | 0 | 10 | 0 | 10 | 0 | 10 | 0 | 10 |
+| in channel levels: primary/diversity (antenna) | [dB] | -76.7 | -81.7 | -75.5 | -80.5 | -75.3 | -80.3 | -75.2 | -80.2 | -75.2 | -80.2 |
+| n28A REFSENS | [dBm] | -98.5 | | -95.5 | | -93.5 | | -90.8 | | -78.5 | |
+| noise floor | [dBm] | -94.5 | -94.5 | -91.5 | -91.5 | -89.5 | -89.5 | -86.8 | -86.8 | -74.5 | -74.5 |
+| n28A composite noise | [dBm] | -76.6 | -81.5 | -75.4 | -80.2 | -75.1 | -79.8 | -74.9 | -79.3 | -71.8 | -73.5 |
+| n28A de-sense | [dB] | 17.9 | 13.0 | 16.1 | 11.3 | 14.36 | 9.69 | 11.9 | 7.5 | 2.7 | 1.0 |
+| after MRC | cor [dB] | 17.5 | | 15.8 | | 14.0 | | 11.7 | | 2.9 | |
+
+Figure 5.2.2.5-1 the n28 MSD evaluation for CA\_n5-n28
+
+Based on the agreed CR R4-2206134, one MSD test configuration (n28 30MHz) can be a reference considering the impacts from band n5 UL.
+
+Table 5.2.2.5-1 MSD due to cross band isolation for CA\_n5-n28
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n5 | n28 | 834 | 20 | 15 | 20 (RBstart=0) | 800.5 | 5 | 17.5 | ACLR2 |
+
+For CA\_n5-n28 with 3 antennas implementation, referring to contribution R4-2301266, the n28 MSD evaluation on the same MSD test configuration (n28 30MHz) as 2 antennas implementation is shown as below.
+
+Table 5.2.2.5-2 MSD due to cross band isolation for CA\_n5-n28
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n5 | n28 | 834 | 20 | 15 | 20 (RBstart=0) | 800.5 | 5 | 18.6 | ACLR2 |
+
+### 5.2.3 Specific for 2 bands UL of fallback CA\_n5-n28
+
+#### 5.2.3.1 Maximum output power for inter-band CA
+
+Power class 3 is assumed for UL CA\_n5-n28.
+
+#### 5.2.3.2 UE co-existence studies
+
+Table 5.2.3.2-1 lists Band n5 + Band n28 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis.
+
+Table 5.2.3.2-1: Band n5 and Band n28 UL IMD products
+
+| UE UL carriers | f <sub>x_low</sub> | f <sub>x_high</sub> | f <sub>y_low</sub> | f <sub>y_high</sub> |
+|------------------------------------|------------------------------------------|------------------------------------------|-----------------------------------------|-------------------------------------------|
+| UL frequency (MHz) | 824 | 869 | 703 | 748 |
+| 2 <sup>nd</sup> order IMD products | f <sub>y_low</sub> – f <sub>x_high</sub> | f <sub>y_high</sub> – f <sub>x_low</sub> | f <sub>y_low</sub> + f <sub>x_low</sub> | f <sub>y_high</sub> + f <sub>x_high</sub> |
+
+| | | | | |
+|---------------------------------------------|----------------------------|-----------------------------|----------------------------|-----------------------------|
+| IMD frequency limits (MHz) | 166 | 76 | 1527 | 1617 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low - fy\_high $ | $ 2*fx\_high - fy\_low $ | $ 2*fy\_low - fx\_high $ | $ 2*fy\_high - fx\_low $ |
+| IMD frequency limits (MHz) | 900 | 1035 | 537 | 672 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low + fy\_low $ | $ 2*fx\_high + fy\_high $ | $ 2*fy\_low + fx\_low $ | $ 2*fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 2351 | 2486 | 2230 | 2365 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low - 1*fy\_high $ | $ 3*fx\_high - 1*fy\_low $ | $ 3*fy\_low - 1*fx\_high $ | $ 3*fy\_high - 1*fx\_low $ |
+| IMD frequency limits (MHz) | 1724 | 1904 | 1240 | 1420 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low + 1*fy\_low $ | $ 3*fx\_high + 1*fy\_high $ | $ 3*fy\_low + 1*fx\_low $ | $ 3*fy\_high + 1*fx\_high $ |
+| IMD frequency limits (MHz) | 3175 | 3355 | 2933 | 3113 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*fx\_low - 2*fy\_high $ | $ 2*fx\_high - 2*fy\_low $ | $ 2*fx\_low + 2*fy\_low $ | $ 2*fx\_high + 2*fy\_high $ |
+| IMD frequency limits (MHz) | 152 | 332 | 3054 | 3234 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low - 4*fy\_high $ | $ fx\_high - 4*fy\_low $ | $ fy\_low - 4*fx\_high $ | $ fy\_high - 4*fx\_low $ |
+| IMD frequency limits (MHz) | 2168 | 1943 | 2773 | 2548 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low - 3*fy\_high $ | $ 2*fx\_high - 3*fy\_low $ | $ 2*fy\_low - 3*fx\_high $ | $ 2*fy\_high - 3*fx\_low $ |
+| IMD frequency limits (MHz) | 596 | 371 | 1201 | 976 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low + 4*fy\_low $ | $ fx\_high + 4*fy\_high $ | $ fy\_low + 4*fx\_low $ | $ fy\_high + 4*fx\_high $ |
+| IMD frequency limits (MHz) | 3636 | 3861 | 3999 | 4224 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low + 3*fy\_low $ | $ 2*fx\_high + 3*fy\_high $ | $ 2*fy\_low + 3*fx\_low $ | $ 2*fy\_high + 3*fx\_high $ |
+| IMD frequency limits (MHz) | 3757 | 3982 | 3878 | 4103 |
+
+Based on Table 5.2.3.2-1, there is no IMD issue for CA\_n5-n28.
+
+Table 5.2.3.2-2 lists the protected bands required for the 2UL bands CA configuration.
+
+Table 5.2.3.2-2: Protected bands for the 2UL bands CA configuration
+
+| NR CA Configuration | Spurious emission | | | | | |
+|---------------------|------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|-------------|
+| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE |
+| CA_n5-n28 | E-UTRA Band 2, 3, 5, 7, 8, 18, 19, 25, 26, 31, 34, 38, 40, 73<br>NR Band n79 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | |
+| | E-UTRA Band 4, 41, 42, 43, 50, 51, 52, 65, 66, 74<br>NR Band n77, n78 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 2 |
+| | E-UTRA Band 1 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 2, 11, 15 |
+| | E-UTRA Band 11, 21 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 2, 11, 12 |
+| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 3, 11 |
+| | Frequency range | 470 | - | 694 | -42 | 8 4, 14 |
+| | Frequency range | 470 | - | 710 | -26.2 | 6 13 |
+| | Frequency range | 662 | - | 694 | -26.2 | 6 4 |
+| | Frequency range | 758 | - | 773 | -32 | 1 4 |
+| | Frequency range | 773 | - | 803 | -50 | 1 |
+
+NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{\text{CRB}} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.
+
+NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 -1915.7 MHz
+
+NOTE 4: These requirements also apply for the frequency ranges that are less than F<sub>oob</sub> (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth.
+
+NOTE 11: Applicable when the assigned NR carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz.
+
+NOTE 12: As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned NR carrier used in the measurement due to 2nd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.3.1-1) for which the 2nd harmonic totally or partially overlaps the measurement bandwidth (MBW).
+
+NOTE 13: This requirement is applicable for 5 and 10 MHz NR channel bandwidth allocated within 718 - 728 MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with RBstart > 1 and RBstart < 48.
+
+NOTE 14: This requirement is applicable in the case of a 10 MHz NR carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies.
+
+NOTE 15: As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3rd harmonic totally or partially overlaps the measurement bandwidth (MBW).
+
+#### 5.2.3.3 REFSSENS evaluation
+
+Since there is no two UL IMD issue for CA\_n5-n28, no need to specify the MSD due to two UL IMD interference. The following reference exception can be further studied.
+
+Referring to contribution R4-2300657, the estimation of the n5+n28 UL interference in band n28 DL versus n5 and n28 1UL case can be found in table 5.2.3.3-1.
+
+Table 5.2.3.3-1: Estimation of the n5+n28 UL interference in band n28 DL versus n5 and n28 1UL case
+
+| n28DL CBW (MHz) at the top of band 28 | 5 | 15 | 20 | 25 | 30 |
+|------------------------------------------------------------|--------|--------|--------|-------|-------|
+| n28 UL transmitter output noise at 23dBm (dBm) | -58.5 | -52.2 | -50.0 | -42.3 | -28.1 |
+| 38.101-1 n28 REFSSENS de-sense due to Tx (dB) | 0.0 | 0.0 | 1.4 | 7.0 | 11.9 |
+| n28 UL transmitter output noise at 20dBm (dBm) | -61.5 | -55.3 | -53.8 | -50.5 | -39.2 |
+| n5 UL transmitter output noise at 23dBm (dBm) | -45.2 | -41.1 | -41.0 | -40.8 | -40.7 |
+| n5 UL transmitter output noise at 20dBm (dBm) | -53.8 | -49.6 | -48.9 | -47.8 | -48.9 |
+| n28UL -> n28DL quadruplexer isolation (dB) | 50 | 50 | 50 | 50 | 50 |
+| n5UL -> n28DL quadruplexer isolation (dB) | 45 | 45 | 45 | 45 | 45 |
+| n28 transmitter output noise at 23dBm (dBm) at main LNA | -108.5 | -102.2 | -100.0 | -92.3 | -78.1 |
+| n5+n28 transmitter output noise at 23dBm (dBm) at main LNA | -90.4 | -94.8 | -94.1 | -93.3 | -88.0 |
+| delta n5+n28 vs n28 at 23dBm output noise at main LNA | 18.1 | 7.4 | 5.8 | -1.0 | -9.9 |
+
+The resulting MSD (on top of n28 without self de-sense) with MRC calculations is provided in Table 5.2.3.3-1 to enable a two-antenna architecture in the long-term.
+
+Table 5.2.3.3-2: 2UL cross band MSDs for CA\_n5-n28
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD (dB) | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|----------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | | |
+| n5 | n28 | 834 | 20 | 15 | 20 (Rbstart=0) | 793 | 20 | [3.6] | ACLR2 |
+| n28 | | 738 | 20 | 15 | 25 (Rbstart=81) | | | | ACLR2 |
+
+Referring to contribution R4-2302097, the relationship for n28 DL impacted by both band n5 UL and n28 UL is shown in figure 1, when both band n5 UL and n28 UL are configured for CA\_n5-n28, band n28 DL receiver will be impacted by the leakage interference from band n5 UL and n28 UL.
+
+
+
+Figure 5.2.3.3-1: Frequency spectrum diagram showing the relationship between n28 UL, n28 DL, n5 UL, and n5 DL bands. The diagram illustrates the 30MHz CBW of n28 DL and the adjacent channel leakage from n28 UL and n5 UL bands. The n28 UL band is shown in yellow, n28 DL in orange, n5 UL in blue, and n5 DL in light blue. The n28 DL band is centered at 793 MHz. The n28 UL band is centered at 738 MHz. The n5 UL band is centered at 834 MHz. The n5 DL band is centered at 869 MHz. The diagram shows the first and second adjacent channel leakage from the n28 UL band and the first and second adjacent channel leakage from the n5 UL band into the n28 DL band.
+
+Figure 5.2.3.3-1 The relationship for band n28 DL impacted by both band n5 UL and n28 UL
+
+Some measurement results were proposed in R4-2202036 for band n28 30MHz case. -32.4dBm Tx noise in n28 Rx band can be observed from band n5 PAout. Since 45dB Tx-Rx isolation between n5 UL band and n28 DL band was assumed, 2.9dB MSD can be observed based on n28 30MHz -78.5dBm REFSSENS for 2 antenna implementation, which is shown in Table 5.2.3.3-3:
+
+Table 5.2.3.3-3: 2UL cross band MSDs for CA\_n5-n28
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n5 | n28 | 834 | 20 | 15 | 20 (RBstart=0) | 788 | 30 | 2.9 | ACLR2 from n5 UL band |
+| n28 | | 733 | 30 | 15 | 25 (RBstart=135) | | | | ACLR1+ACLR2 from n28 UL band |
+
+Referring to contribution R4-2302253, the most straightforward way would be to use the same test point for 2UL MSD due to Cross-Band Isolation as has been used for 1UL Cross-band Isolation for 2 antenna implementation, which is shown in Table 5.2.3.3-4:
+
+Table 5.2.3.3-4: 2UL cross band MSDs for CA\_n5-n28
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n5 | n28 | 834 | 20 | 15 | 20 (Rbstart=0) | 800.5 | 5 | 17.5 | n5 ACLR2 |
+| n28 | | 5 | 5 | 15 | 25 (Rbstart=0) | | | | |
+
+Referring to contribution R4-2218129, for 2UL MSD due to Cross-Band Isolation as has been used for 1UL Cross-band Isolation for 3 antenna implementation is shown in Table 5.2.3.3-5. It includes a legacy filter rejection for n5 TX OOB leakage in n28DL. The antenna isolation helps attenuate the TX leakage to give a similar MSD result specified in Table 5.2.3.3-3 for a 30MHz DL.
+
+Table 5.2.3.3-5: 2UL cross band MSDs for CA\_n5-n28
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n5 | n28 | 834 | 20 | 15 | 20 (RBstart=0) | 788 | 30 | 4.5 | ACLR2 from n5 UL band |
+| n28 | | 733 | 30 | 15 | 25 (RBstart=135) | | | | ACLR1+ACLR2 from n28 UL band |
+
+## 5.3 CA\_n8-n20-n28
+
+### 5.3.1 UE RF architecture assumption
+
+#### 5.3.1.0 General
+
+The UE RF architectures with 2 antenna, 3 antenna, 4 antenna can be assumed to analyze and study for CA\_n8-n20-n28. The antenna number is the total number of antennas to support Main UL/DL and diversity DL for all bands. UE RF architecture with three antennas for CA\_n8-n20-n28 is used as baseline for evaluation. The UE RF architectures with two or four antennas are not precluded in the study item.
+
+#### 5.3.1.1 UE RF architecture with three antennas
+
+The assumption 1A for UE RF architecture with three antennas for CA\_n8-n20-n28 are shown as below.
+
+- 1) n28UL/n20+n28DL/n20UL triplexer on antenna 1
+- 2) n8UL/n8DL duplexer on antenna 2
+- 3) n20+n28DL/n8DL duplexer on antenna 3
+- 4) 10dB antenna isolation is used for MSD calculations
+
+The assumption 1B for UE RF architecture with three antennas for CA\_n8-n20-n28 are shown as below. Comparing to assumption 1a, n8UL/n8DL duplexer on antenna 2 was replaced by n8UL/n8DL/n20UL/n20DL quadplexer.
+
+- 1) n28UL/n20+n28DL/n20UL triplexer on antenna 1
+- 2) n8UL/n8DL/n20UL/n20DL quadplexer on antenna 2
+- 3) n20+n28DL/n8DL duplexer on antenna 3
+- 4) 10dB antenna isolation is used for MSD calculations
+
+The assumption 1C for UE RF architecture with three antennas for CA\_n8-n20-n28 are shown as Figure 5.3.1.1-1. These are two other variants based on assumption 1a. They may allow easier implementation of either triplexer or duplexer in main path owing to that the frequency separations between the sub-bands are wider than the architecture assumed for DC\_8-20\_n28. However, the downside with two variants is that the widest frequency range which needs to be covered by any of the antenna is still relatively wide at 212 MHz and 257 MHz respectively.
+
+
+
+Figure 5.3.1.1-1: Potential UE architecture variants to support CA\_n8-n20-n28 with 3 antenna. The diagram shows two variants, (a) and (b), for a UE RF architecture with three antennas. Each variant includes three main transceivers (Main TRx 1, Main TRx 2, Diversity Rx) connected to antennas. Each transceiver is connected to a series of filters and switches (sPnT) that route signals to different frequency bands (n28, n20, n8). Variant (a) shows a configuration where Main TRx 1 and Main TRx 2 are connected to n28, n20, and n8 bands, while Diversity Rx is connected to n20/n28 and n8 bands. Variant (b) shows a configuration where Main TRx 1 and Main TRx 2 are connected to n20/n28 and n8 bands, while Diversity Rx is connected to n28, n20, and n8 bands.
+
+**Figure 5.3.1.1-1 Potential UE architecture variants to support CA\_n8-n20-n28 with 3 antenna**
+
+#### 5.3.1.2 UE RF architecture with two antennas
+
+The assumption 2A for UE RF architecture with two antennas for CA\_n8-n20-n28 are shown as below. Pentaplexer design is considered.
+
+- 1) n28UL/n20+n28DL/n20UL/n8UL/n8DL pentaplexer on antenna 1
+- 2) n20+n28DL/n8DL duplexer on antenna 2
+- 3) 10dB antenna isolation is used for MSD calculations
+
+The assumption 2B for UE RF architecture with two antennas for CA\_n8-n20-n28 are shown as below. Quadplexer design is considered.
+
+- 1) n28UL/n20+n28DL/n20UL/n8DL quadplexer on antenna 1
+- 2) n20+n28DL/n8UL/n8DL triplexer or n20+n28DL/n20UL/n8UL/n8DL quadplexer on antenna 2
+- 3) 10dB antenna isolation is used for MSD calculations
+
+There are two potential implementation challenges with 2-antenna architectures. The first challenge is that the antenna design needs to cover the entire spectrum range of 257 MHz simultaneously as shown in Figure 5.3.1-1 for either of the variants, which is equivalent to a 31% bandwidth ratio and that would far exceed the bandwidth ratio for a typical
+
+planar antenna design in a smartphone. As a result, the radiative performance for the combination is expected to be compromised.
+
+The second challenge is on the feasibility of a pentaplexer design for variant (a) to aggregate five closely spaced spectrum ranges as shown in Figure 5.3.1-1, not only with sufficient filter isolation between self-band and cross-band but also with acceptable insertion loss. The variant (b) though avoids the use of pentaplexer, the design of the intended quadruplexer is still relatively challenging considering the closely spaced spectrum ranges with nearly 8% bandwidth ratio for the n20/n28 combined DL range.
+
+#### 5.3.1.3 UE RF architecture with four antennas
+
+The assumption 3A and 3B for UE RF architecture with four antennas for CA\_n8-n20-n28 are shown as below.
+
+
+
+Figure 5.3.1.3-1: RF architecture diagram for assumption 3A. It shows four antenna paths. The first three are labeled 'Main TRx 1', 'Main TRx 2', and 'Main TRx 3'. Each has a duplexer connected to an antenna, followed by two 'sPnT' blocks. Below the first 'sPnT' block is another duplexer connected to two amplifiers labeled 'n28' and 'n28'. The second 'Main TRx' path has amplifiers labeled 'n20' and 'n20'. The third 'Main TRx' path has amplifiers labeled 'n8' and 'n8'. The fourth path is labeled 'Diversity Rx' and has a duplexer connected to an antenna, followed by two 'sPnT' blocks. Below the first 'sPnT' block is another duplexer connected to two amplifiers labeled 'n20/n28' and 'n8'.
+
+Figure 5.3.1.3-1 The assumption 3A for UE RF architecture to support CA\_n8-n20-n28 with 4 antenna
+
+
+
+Figure 5.3.1.3-2: RF architecture diagram for assumption 3B. It shows four antenna paths. The first three are labeled 'Antenna switch', 'Antenna switch', and 'Antenna switch'. Each is connected to a 'Duplexer', which is then connected to two amplifiers. The first path has amplifiers labeled 'n8' and 'n8'. The second path has amplifiers labeled 'n20/n28' and 'n28'. The third path has amplifiers labeled 'n20/n28' and 'n20'. The fourth path is labeled 'Antenna switch' and is connected directly to an amplifier labeled 'n8'.
+
+Figure 5.3.1.3-2 The assumption 3B for UE RF architecture to support CA\_n8-n20-n28 with 4 antenna
+
+For the 4-antenna implementation, the three of the four antenna are used in the main path to aggregate the n8, n20, and n28 signals over the air, as shown in Figures 5.3.1.3-1 and 5.3.1.3-2. As n8, n20, and n28 signals do not need to be combined through a multiplexer, there is no additional insertion loss in n8, n20, and n28 main signal paths as compared to single-band implementation.
+
+Having 3 antenna in the main signal path not only avoids the more complicated multiplexer implementation and the associated additional insertion losses, but also allows narrower frequency coverage for each of the 3 antenna as compared to single-antenna implementation. However, the additional antenna cannot be added without occupying more phone space.
+
+### 5.3.2 CA\_n8-n20
+
+#### 5.3.2.0 General
+
+According to the current spec TS 38.101-1, DL CA\_n8A-n20A\_BCS0 has been specified. Thus, some of RF requirements can be reused as below. Both DL\_n8A-n20A\_BCS0 and DL\_n8A-n20A\_UL\_n8A-n20A are fallback CA band combinations of DL\_n8A-n20A-n28A\_UL\_n8A-n20A.
+
+#### 5.3.2.1 Operating bands for CA
+
+**Table 5.3.2.1-1: CA band combination of band n8+n20**
+
+| | Uplink (UL) band | | Downlink (DL) band | | | |
+|-----|------------------------------|---|------------------------------|---------|-----|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low} - F_{UL\_high}$ | | $F_{DL\_low} - F_{DL\_high}$ | | | |
+| n8 | 880 MHz | – | 915 MHz | 925 MHz | FDD | |
+| n20 | 832 MHz | – | 862 MHz | 791 MHz | FDD | |
+
+#### 5.3.2.2 Channel bandwidths per operating band for CA
+
+Referring to table 5.5A.3.1-1e of TS 38.101-1, DL\_n8A-n20A\_BCS0 has been specified.
+
+#### 5.3.2.3 UE co-existence studies
+
+There is no need to specify harmonics and harmonics mixing exception for CA\_n8-n20 as we didn't specify them in current spec.
+
+#### 5.3.2.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n8-n20, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values have been specified in TS 38.101-1.
+
+#### 5.3.2.5 REFSENS requirements
+
+As CA\_n8-n20 has been specified into current spec TS 38.101-1, there is no harmonics, cross band isolation and harmonics mixing exception.
+
+#### 5.3.2.6 Maximum output power for UL inter-band CA
+
+Power class 3 is assumed for UL CA\_n8-n20.
+
+#### 5.3.2.7 UE co-existence studies for UL inter-band CA
+
+Table 5.3.2.7-1 lists Band n8 + Band n20 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis.
+
+**Table 5.3.2.7-1: Band n8 and Band n20 UL IMD products**
+
+| UE UL carriers | $f_{x\_low}$ | $f_{x\_high}$ | $f_{y\_low}$ | $f_{y\_high}$ |
+|------------------------------------|------------------------------|------------------------------|-----------------------------|-------------------------------|
+| UL frequency (MHz) | 880 | 915 | 832 | 862 |
+| 2 <sup>nd</sup> order IMD products | $ f_{y\_low} - f_{x\_high} $ | $ f_{y\_high} - f_{x\_low} $ | $ f_{y\_low} + f_{x\_low} $ | $ f_{y\_high} + f_{x\_high} $ |
+| IMD frequency limits (MHz) | 83 | 18 | 1712 | 1777 |
+
+| | | | | |
+|---------------------------------------------|------------------------------|-------------------------------|------------------------------|-------------------------------|
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*f_x\_low - f_y\_high $ | $ 2*f_x\_high - f_y\_low $ | $ 2*f_y\_low - f_x\_high $ | $ 2*f_y\_high - f_x\_low $ |
+| IMD frequency limits (MHz) | 898 | 998 | 749 | 844 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*f_x\_low + f_y\_low $ | $ 2*f_x\_high + f_y\_high $ | $ 2*f_y\_low + f_x\_low $ | $ 2*f_y\_high + f_x\_high $ |
+| IMD frequency limits (MHz) | 2592 | 2692 | 2544 | 2639 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*f_x\_low - 1*f_y\_high $ | $ 3*f_x\_high - 1*f_y\_low $ | $ 3*f_y\_low - 1*f_x\_high $ | $ 3*f_y\_high - 1*f_x\_low $ |
+| IMD frequency limits (MHz) | 1778 | 1913 | 1581 | 1706 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*f_x\_low + 1*f_y\_low $ | $ 3*f_x\_high + 1*f_y\_high $ | $ 3*f_y\_low + 1*f_x\_low $ | $ 3*f_y\_high + 1*f_x\_high $ |
+| IMD frequency limits (MHz) | 3472 | 3607 | 3376 | 3501 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*f_x\_low - 2*f_y\_high $ | $ 2*f_x\_high - 2*f_y\_low $ | $ 2*f_x\_low + 2*f_y\_low $ | $ 2*f_x\_high + 2*f_y\_high $ |
+| IMD frequency limits (MHz) | 36 | 166 | 3424 | 3554 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low - 4*f_y\_high $ | $ f_x\_high - 4*f_y\_low $ | $ f_y\_low - 4*f_x\_high $ | $ f_y\_high - 4*f_x\_low $ |
+| IMD frequency limits (MHz) | 2568 | 2413 | 2828 | 2658 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low - 3*f_y\_high $ | $ 2*f_x\_high - 3*f_y\_low $ | $ 2*f_y\_low - 3*f_x\_high $ | $ 2*f_y\_high - 3*f_x\_low $ |
+| IMD frequency limits (MHz) | 826 | 666 | 1081 | 916 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low + 4*f_y\_low $ | $ f_x\_high + 4*f_y\_high $ | $ f_y\_low + 4*f_x\_low $ | $ f_y\_high + 4*f_x\_high $ |
+| IMD frequency limits (MHz) | 4208 | 4363 | 4352 | 4522 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low + 3*f_y\_low $ | $ 2*f_x\_high + 3*f_y\_high $ | $ 2*f_y\_low + 3*f_x\_low $ | $ 2*f_y\_high + 3*f_x\_high $ |
+| IMD frequency limits (MHz) | 4256 | 4416 | 4304 | 4469 |
+
+Based on Table 5.3.2.6-1, 3<sup>rd</sup> and 5<sup>th</sup> order IMD may also fall into Rx frequencies of bands n8 or band n20.
+
+Table 5.3.2.7-2 lists the protected bands required for the 2UL bands CA configuration.
+
+**Table 5.3.2.7-2: Protected bands for the 2UL bands CA configuration**
+
+| NR CA Configuration | Spurious emission | | | | | |
+|---------------------|---------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|------|
+| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE |
+| CA_n8-n20 | E-UTRA Band 1, 31, 32, 33, 34, 40, 50, 51, 65, 67, 68, 72, 74, 75, 76<br>NR Band n100, n104 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 |
+| | E-UTRA Band 3, 7, 22, 38, 42, 43, 52, 69<br>NR band n77, n78 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 2 |
+| | E-UTRA Band 8, 20 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 4 |
+| | Frequency range | 758 | - | 788 | -50 | 1 |
+
+NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{\text{CRB}} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.
+
+NOTE 4: These requirements also apply for the frequency ranges that are less than F<sub>OOB</sub> (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth.
+
+#### 5.3.2.8 REFSENS evaluation for UL inter-band CA
+
+IMD3 MSD of DC\_20\_n8A in band 20 and n8 specified in TS 38.101-3 is a good reference for CA\_n8-n20 as below.
+
+**Table 5.3.2.8-1: REFSENS exceptions due to IMD interference for CA\_n8-n20**
+
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL L <sub>CRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n8-n20 | n8 | 892.5 | 5 | 25 | 937.5 | 25 | FDD | IMD3 |
+| | n20 | 849.5 | 5 | 25 | 808.5 | 25 | FDD | IMD3 |
+
+### 5.3.3 CA\_n8-n28
+
+#### 5.3.3.0 General
+
+According to the current spec TS 38.101-1, DL CA\_n8A-n28A\_BCS0 has been specified. Thus, some of RF requirements can be reused as below. Both DL\_n8A-n28A\_BCS0 and DL\_n8A-n28A\_UL\_n8A-n28A are fallback CA band combinations of DL\_n8A-n20A-n28A\_UL\_n8A-n28A.
+
+#### 5.3.3.1 Operating bands for CA
+
+**Table 5.3.3.1-1: CA band combination of band n8+n28**
+
+| | Uplink (UL) band | Downlink (DL) band | |
+|--|--------------------------------------------|--------------------------------------------|--|
+| | BS receive / UE transmit | BS transmit / UE receive | |
+| | F <sub>UL_low</sub> – F <sub>UL_high</sub> | F <sub>DL_low</sub> – F <sub>DL_high</sub> | |
+
+| | | | | |
+|-----|---------|---|---------|-----|
+| | | | | |
+| n8 | 880 MHz | – | 915 MHz | FDD |
+| n28 | 703 MHz | – | 748 MHz | FDD |
+
+#### 5.3.3.2 Channel bandwidths per operating band for CA
+
+Referring to table 5.5A.3.1-1e of TS 38.101-1, DL\_n8A-n28A\_BCS0 has been specified as below.
+
+**Table 5.3.3.2-1: Supported bandwidths per CA band combination of band n8+n28**
+
+| NR CA configuration | Uplink CA configuration or single uplink carrier | NR Band | Channel bandwidth (MHz) | Bandwidth combination set |
+|---------------------|--------------------------------------------------|---------|-------------------------|---------------------------|
+| CA_n8A-n28A | CA_n8A-n28A | n8 | 5, 10, 15, 20 | 0 |
+| | | n28 | 5, 10, 15, 20, 30 | |
+
+#### 5.3.3.3 UE co-existence studies
+
+There is no need to specify harmonics and harmonics mixing exception for CA\_n8-n28 as we didn't specify them in current spec.
+
+#### 5.3.3.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n8-n28, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values have been specified in TS 38.101-1.
+
+#### 5.3.3.5 REFSENS requirements
+
+As CA\_n8-n28 has been specified into current spec TS 38.101-1, there is no harmonics, cross band isolation and harmonics mixing exception.
+
+#### 5.3.3.6 Maximum output power for UL inter-band CA
+
+Power class 3 is assumed for UL CA\_n8-n28.
+
+#### 5.3.3.7 UE co-existence studies for UL inter-band CA
+
+Table 5.3.3.7-1 lists Band n8 + Band n28 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis.
+
+**Table 5.3.3.7-1: Band n8 and Band n28 UL IMD products**
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|--------------------------|---------------------------|--------------------------|---------------------------|
+| UL frequency (MHz) | 880 | 915 | 703 | 748 |
+| 2 <sup>nd</sup> order IMD products | $ fy\_low - fx\_high $ | $ fy\_high - fx\_low $ | $ fy\_low + fx\_low $ | $ fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 212 | 132 | 1583 | 1663 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low - fy\_high $ | $ 2*fx\_high - fy\_low $ | $ 2*fy\_low - fx\_high $ | $ 2*fy\_high - fx\_low $ |
+| IMD frequency limits (MHz) | 1012 | 1127 | 491 | 616 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low + fy\_low $ | $ 2*fx\_high + fy\_high $ | $ 2*fy\_low + fx\_low $ | $ 2*fy\_high + fx\_high $ |
+
+| IMD frequency limits (MHz) | 2463 | 2578 | 2286 | 2411 |
+|---------------------------------------------|------------------------------|-------------------------------|------------------------------|-------------------------------|
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*f_x\_low - 1*f_y\_high $ | $ 3*f_x\_high - 1*f_y\_low $ | $ 3*f_y\_low - 1*f_x\_high $ | $ 3*f_y\_high - 1*f_x\_low $ |
+| IMD frequency limits (MHz) | 1892 | 2042 | 1194 | 1364 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*f_x\_low + 1*f_y\_low $ | $ 3*f_x\_high + 1*f_y\_high $ | $ 3*f_y\_low + 1*f_x\_low $ | $ 3*f_y\_high + 1*f_x\_high $ |
+| IMD frequency limits (MHz) | 3343 | 3493 | 2989 | 3159 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*f_x\_low - 2*f_y\_high $ | $ 2*f_x\_high - 2*f_y\_low $ | $ 2*f_x\_low + 2*f_y\_low $ | $ 2*f_x\_high + 2*f_y\_high $ |
+| IMD frequency limits (MHz) | 264 | 424 | 3166 | 3326 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low - 4*f_y\_high $ | $ f_x\_high - 4*f_y\_low $ | $ f_y\_low - 4*f_x\_high $ | $ f_y\_high - 4*f_x\_low $ |
+| IMD frequency limits (MHz) | 2112 | 1897 | 2957 | 2772 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low - 3*f_y\_high $ | $ 2*f_x\_high - 3*f_y\_low $ | $ 2*f_y\_low - 3*f_x\_high $ | $ 2*f_y\_high - 3*f_x\_low $ |
+| IMD frequency limits (MHz) | 484 | 279 | 1339 | 1144 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low + 4*f_y\_low $ | $ f_x\_high + 4*f_y\_high $ | $ f_y\_low + 4*f_x\_low $ | $ f_y\_high + 4*f_x\_high $ |
+| IMD frequency limits (MHz) | 3692 | 3907 | 4223 | 4408 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low + 3*f_y\_low $ | $ 2*f_x\_high + 3*f_y\_high $ | $ 2*f_y\_low + 3*f_x\_low $ | $ 2*f_y\_high + 3*f_x\_high $ |
+| IMD frequency limits (MHz) | 3869 | 4074 | 4046 | 4241 |
+
+Based on Table 5.3.3.7-1, there is no IMD issue for CA\_n8-n28.
+
+Table 5.3.3.7-2 lists the protected bands required for the 2UL bands CA configuration.
+
+**Table 5.3.3.7-2: Protected bands for the 2UL bands CA configuration**
+
+| NR CA Configuration | Spurious emission | | | | | | |
+|---------------------|---------------------------------------------------------------------------------------------|-----------------------|---|----------------------|---------------------|-----------|-----------|
+| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE |
+| CA_n8-n28 | E-UTRA Band 20, 31, 34, 38, 40, 72 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | |
+| | E-UTRA band 3, 7, 22, 41, 42, 43, 50, 51, 65, 73, 74, 75, 76<br>NR Band n77, n78, n79, n100 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 2 |
+| | E-UTRA Band 1 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 2, 11, 15 |
+| | E-UTRA Band 8 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 4 |
+| | E-UTRA Band 11, 21 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 11, 12 |
+| | Frequency range | 470 | - | 694 | -42 | 8 | 4, 14 |
+| | Frequency range | 470 | - | 710 | -26.2 | 6 | 13 |
+
+| | | | | | | | |
+|--|-----------------|--------|---|--------|-------|-----|-------|
+| | Frequency range | 662 | - | 694 | -26.2 | 6 | 4 |
+| | Frequency range | 758 | - | 773 | -32 | 1 | 4 |
+| | Frequency range | 773 | - | 803 | -50 | 1 | |
+| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 11 |
+
+NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{\text{CRB}} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.
+
+NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 -1915.7 MHz
+
+NOTE 4: These requirements also apply for the frequency ranges that are less than $F_{\text{oob}}$ (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth.
+
+NOTE 11: Applicable when the assigned NR carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz.
+
+NOTE 12: As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned NR carrier used in the measurement due to 2<sup>nd</sup> harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.3.1-1) for which the 2<sup>nd</sup> harmonic totally or partially overlaps the measurement bandwidth (MBW).
+
+NOTE 13: This requirement is applicable for 5 and 10 MHz NR channel bandwidth allocated within 718 - 728 MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with $\text{RBstart} > 1$ and $\text{RBstart} < 48$ .
+
+NOTE 14: This requirement is applicable in the case of a 10 MHz NR carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies.
+
+NOTE 15: As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3rd harmonic totally or partially overlaps the measurement bandwidth (MBW).
+
+#### 5.3.3.8 REFSSENS requirements for UL inter-band CA
+
+There is no REFSSENS exception due to IMD interference for CA\_n8A-n28A.
+
+### 5.3.4 CA\_n20-n28
+
+#### 5.3.4.1 General
+
+According to the current spec TS 38.101-1, DL\_n20A-n28A\_UL\_n20A-n28A\_BCS0 and DL\_n20A-n28A\_UL\_n20A-n28A\_BCS1 have already been specified. Thus, all of the related RF requirements have been analysed in clause 6.31 from TR 38.716-02-00 and can be reused as below. Both DL\_n20A-n28A\_BCS0 and DL\_n20A-n28A\_UL\_n20A-n28A\_BCS0 are fallback CA band combinations of DL\_n8A-n20A-n28A\_UL\_n20A-n28A.
+
+- 1) The operating bands for CA\_n20-n28 were specified in table 5.2A.2.1-1 from TS 38.101-1 with note 2 that The frequency range in band n28 is restricted for this band combination to 703-733 MHz for the UL and 758-788 MHz for the DL.
+- 2) The UL/DL configurations and bandwidth combination sets for DL\_n20A-n28A\_UL\_n20A-n28A\_BCS0 and DL\_n20A-n28A\_UL\_n20A-n28A\_BCS1 were specified in table 5.5A.3.1-1g from TS 38.101-1.
+- 3) 23dBm Power class 3 for UL CA\_n20A-n28A was specified in Table 6.2A.1.3-1 from TS 38.101-1.
+- 4) 0.5dB $\Delta T_{\text{IB,c}}$ for CA\_n20-n28 was specified in Table 6.2A.4.2.3-1 from TS 38.101-1.
+- 5) Spurious emissions for UE co-existence for Inter-band CA\_n20-n28 were specified in Table 6.5A.3.2.3-1 from TS 38.101-1.
+- 6) Referring to UE co-existence studies in clause 6.31.2.1 from TR 38.716-02-00, there are no harmonic/harmonic mixing or IMD issues affecting own Rx frequencies of either band n20 or n28. Therefore, there is no need to specify the additional REFSSENS exceptions for CA\_n20-n28.
+- 7) 0dB $\Delta R_{\text{IB,c}}$ for CA\_n20-n28 was specified in Table 6.31.1.4-2 from TR 38.716-02-00.
+
+### 5.3.5 CA\_n8-n20-n28
+
+#### 5.3.5.1 Operating bands for CA
+
+**Table 5.3.5.1-1: Inter-band CA operating bands involving FR1 (three bands)**
+
+| | Uplink (UL) band | | Downlink (DL) band | | | |
+|-----|------------------------------|-----------|------------------------------|-----------|-----|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low} - F_{UL\_high}$ | | $F_{DL\_low} - F_{DL\_high}$ | | | |
+| n8 | 880 MHz | – 915 MHz | 925 MHz | – 960 MHz | FDD | |
+| n20 | 832 MHz | – 862 MHz | 791 MHz | – 821 MHz | FDD | |
+| n28 | 703 MHz | – 748 MHz | 758 MHz | – 803 MHz | FDD | |
+
+It's noted that the following sentence was clarified in clause 5.5A.0 from TS 38.101-1.
+
+*“For a higher order band combination of which CA\_n20-n28 is a subset, the frequency range in band n28 is restricted for the higher order band combination to 703-733 MHz for the UL and 758-788 MHz for the DL.”*
+
+Thus, this frequency range restriction is also applicable to CA\_n8-n20-n28.
+
+#### 5.3.5.2 Channel bandwidths per operating band for CA
+
+**Table 5.3.5.2-1: Supported bandwidths per CA band combination of band n8+n20+n28**
+
+| NR CA configuration | Uplink CA configuration or single uplink carrier | NR Band | Channel bandwidth (MHz) | Bandwidth combination set |
+|---------------------|--------------------------------------------------|---------|-------------------------|---------------------------|
+| CA_n8A-n20A-n28A | CA_n8A-n20A | n8 | 5, 10, 15, 20 | 0 |
+| | CA_n8A-n28A | n20 | 5, 10, 15, 20 | |
+| | CA_n20A-n28A | n28 | 5, 10, 15, 20 | |
+
+#### 5.3.5.3 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n8-n20-n28, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values for 2-antenna and 3-antenna architectures are captured in this part. However, only one set of values will be defined in the specification in the follow-up WI allowing all possible UE RF architectures.
+
+For CA\_n8-n20-n28, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values are derived from the existing CA\_n8-n28 and CA\_n20-n28 based on 3-antennas UE architecture as the baseline.
+
+**Table 5.3.5.3-1: $\Delta T_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ (dB) |
+|-----------------------------|---------|------------------------|
+| CA_n8-n20-n28 | n8 | 0.6 |
+| | n20 | 0.5 |
+| | n28 | 0.5 |
+
+Table 5.3.5.3-2: $\Delta R_{IB,c}$
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ (dB) |
+|-----------------------------|---------|------------------------|
+| CA_n8-n20-n28 | n8 | 0.2 |
+| | n20 | 0 |
+| | n28 | 1 |
+
+For CA\_n8-n20-n28, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values are derived in Table 5.3.5.3-3 and Table 5.3.5.3-4 and enable a two-antenna architecture in the long-term.
+
+Table 5.3.5.3-3: $\Delta T_{IB,c}$
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ (dB) |
+|-----------------------------|---------|------------------------|
+| CA_n8-n20-n28 | n8 | 0.8 |
+| | n20 | 0.7 |
+| | n28 | 0.7 |
+
+Table 5.3.5.3-4: $\Delta R_{IB,c}$
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ (dB) |
+|-----------------------------|---------|------------------------|
+| CA_n8-n20-n28 | n8 | 0.3 |
+| | n20 | 0.2 |
+| | n28 | 0.2 |
+
+#### 5.3.5.4 UE co-existence studies for UL inter-band CA
+
+Table 5.3.5.4-1 lists Band n8 + Band n20 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis, which may fall into the Rx receiver of DL band n28.
+
+Table 5.3.5.4-1: Band n8 and Band n20 UL IMD products
+
+| UE UL carriers | $f_{x\_low}$ | $f_{x\_high}$ | $f_{y\_low}$ | $f_{y\_high}$ |
+|---------------------------------------------|----------------------------------|-----------------------------------|----------------------------------|-----------------------------------|
+| UL frequency (MHz) | 880 | 915 | 832 | 862 |
+| 2 <sup>nd</sup> order IMD products | $ f_{y\_low} - f_{x\_high} $ | $ f_{y\_high} - f_{x\_low} $ | $ f_{y\_low} + f_{x\_low} $ | $ f_{y\_high} + f_{x\_high} $ |
+| IMD frequency limits (MHz) | 83 | 18 | 1712 | 1777 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*f_{x\_low} - f_{y\_high} $ | $ 2*f_{x\_high} - f_{y\_low} $ | $ 2*f_{y\_low} - f_{x\_high} $ | $ 2*f_{y\_high} - f_{x\_low} $ |
+| IMD frequency limits (MHz) | 898 | 998 | 749 | 844 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*f_{x\_low} + f_{y\_low} $ | $ 2*f_{x\_high} + f_{y\_high} $ | $ 2*f_{y\_low} + f_{x\_low} $ | $ 2*f_{y\_high} + f_{x\_high} $ |
+| IMD frequency limits (MHz) | 2592 | 2692 | 2544 | 2639 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*f_{x\_low} - 1*f_{y\_high} $ | $ 3*f_{x\_high} - 1*f_{y\_low} $ | $ 3*f_{y\_low} - 1*f_{x\_high} $ | $ 3*f_{y\_high} - 1*f_{x\_low} $ |
+| IMD frequency limits (MHz) | 1778 | 1913 | 1581 | 1706 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*f_{x\_low} + 1*f_{y\_low} $ | $ 3*f_{x\_high} + 1*f_{y\_high} $ | $ 3*f_{y\_low} + 1*f_{x\_low} $ | $ 3*f_{y\_high} + 1*f_{x\_high} $ |
+
+| | | | | |
+|---------------------------------------------|----------------------------|-----------------------------|----------------------------|-----------------------------|
+| IMD frequency limits (MHz) | 3472 | 3607 | 3376 | 3501 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*fx\_low - 2*fy\_high $ | $ 2*fx\_high - 2*fy\_low $ | $ 2*fx\_low + 2*fy\_low $ | $ 2*fx\_high + 2*fy\_high $ |
+| IMD frequency limits (MHz) | 36 | 166 | 3424 | 3554 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low - 4*fy\_high $ | $ fx\_high - 4*fy\_low $ | $ fy\_low - 4*fx\_high $ | $ fy\_high - 4*fx\_low $ |
+| IMD frequency limits (MHz) | 2568 | 2413 | 2828 | 2658 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low - 3*fy\_high $ | $ 2*fx\_high - 3*fy\_low $ | $ 2*fy\_low - 3*fx\_high $ | $ 2*fy\_high - 3*fx\_low $ |
+| IMD frequency limits (MHz) | 826 | 666 | 1081 | 916 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low + 4*fy\_low $ | $ fx\_high + 4*fy\_high $ | $ fy\_low + 4*fx\_low $ | $ fy\_high + 4*fx\_high $ |
+| IMD frequency limits (MHz) | 4208 | 4363 | 4352 | 4522 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low + 3*fy\_low $ | $ 2*fx\_high + 3*fy\_high $ | $ 2*fy\_low + 3*fx\_low $ | $ 2*fy\_high + 3*fx\_high $ |
+| IMD frequency limits (MHz) | 4256 | 4416 | 4304 | 4469 |
+
+Table 5.3.5.4-2 lists Band n8 + Band n28 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis, which may fall into the Rx receiver of DL band n20.
+
+**Table 5.3.5.4-2: Band n8 and Band n28 UL IMD products**
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------------|-----------------------------|----------------------------|-----------------------------|
+| UL frequency (MHz) | 880 | 915 | 703 | 748 |
+| 2 <sup>nd</sup> order IMD products | $ fy\_low - fx\_high $ | $ fy\_high - fx\_low $ | $ fy\_low + fx\_low $ | $ fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 212 | 132 | 1583 | 1663 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low - fy\_high $ | $ 2*fx\_high - fy\_low $ | $ 2*fy\_low - fx\_high $ | $ 2*fy\_high - fx\_low $ |
+| IMD frequency limits (MHz) | 1012 | 1127 | 491 | 616 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low + fy\_low $ | $ 2*fx\_high + fy\_high $ | $ 2*fy\_low + fx\_low $ | $ 2*fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 2463 | 2578 | 2286 | 2411 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low - 1*fy\_high $ | $ 3*fx\_high - 1*fy\_low $ | $ 3*fy\_low - 1*fx\_high $ | $ 3*fy\_high - 1*fx\_low $ |
+| IMD frequency limits (MHz) | 1892 | 2042 | 1194 | 1364 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low + 1*fy\_low $ | $ 3*fx\_high + 1*fy\_high $ | $ 3*fy\_low + 1*fx\_low $ | $ 3*fy\_high + 1*fx\_high $ |
+
+| | | | | |
+|---------------------------------------------|----------------------------|-----------------------------|----------------------------|-----------------------------|
+| IMD frequency limits (MHz) | 3343 | 3493 | 2989 | 3159 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*fx\_low - 2*fy\_high $ | $ 2*fx\_high - 2*fy\_low $ | $ 2*fx\_low + 2*fy\_low $ | $ 2*fx\_high + 2*fy\_high $ |
+| IMD frequency limits (MHz) | 264 | 424 | 3166 | 3326 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low - 4*fy\_high $ | $ fx\_high - 4*fy\_low $ | $ fy\_low - 4*fx\_high $ | $ fy\_high - 4*fx\_low $ |
+| IMD frequency limits (MHz) | 2112 | 1897 | 2957 | 2772 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low - 3*fy\_high $ | $ 2*fx\_high - 3*fy\_low $ | $ 2*fy\_low - 3*fx\_high $ | $ 2*fy\_high - 3*fx\_low $ |
+| IMD frequency limits (MHz) | 484 | 279 | 1339 | 1144 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low + 4*fy\_low $ | $ fx\_high + 4*fy\_high $ | $ fy\_low + 4*fx\_low $ | $ fy\_high + 4*fx\_high $ |
+| IMD frequency limits (MHz) | 3692 | 3907 | 4223 | 4408 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low + 3*fy\_low $ | $ 2*fx\_high + 3*fy\_high $ | $ 2*fy\_low + 3*fx\_low $ | $ 2*fy\_high + 3*fx\_high $ |
+| IMD frequency limits (MHz) | 3869 | 4074 | 4046 | 4241 |
+
+Table 5.3.5.4-3 lists Band n20 + Band n28 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis, which may fall into the Rx receiver of DL band n8.
+
+**Table 5.3.5.4-3: Band n20 and Band n28 UL IMD products**
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------------|-----------------------------|----------------------------|-----------------------------|
+| UL frequency (MHz) | 832 | 862 | 703 | 733 |
+| 2 <sup>nd</sup> order IMD products | $ fy\_low - fx\_high $ | $ fy\_high - fx\_low $ | $ fy\_low + fx\_low $ | $ fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 159 | 99 | 1535 | 1595 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low - fy\_high $ | $ 2*fx\_high - fy\_low $ | $ 2*fy\_low - fx\_high $ | $ 2*fy\_high - fx\_low $ |
+| IMD frequency limits (MHz) | 931 | 1021 | 544 | 634 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low + fy\_low $ | $ 2*fx\_high + fy\_high $ | $ 2*fy\_low + fx\_low $ | $ 2*fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 2367 | 2457 | 2238 | 2328 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low - 1*fy\_high $ | $ 3*fx\_high - 1*fy\_low $ | $ 3*fy\_low - 1*fx\_high $ | $ 3*fy\_high - 1*fx\_low $ |
+| IMD frequency limits (MHz) | 1763 | 1883 | 1247 | 1367 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low + 1*fy\_low $ | $ 3*fx\_high + 1*fy\_high $ | $ 3*fy\_low + 1*fx\_low $ | $ 3*fy\_high + 1*fx\_high $ |
+
+| | | | | |
+|---------------------------------------------|------------------------------|-------------------------------|------------------------------|-------------------------------|
+| IMD frequency limits (MHz) | 3199 | 3319 | 2941 | 3061 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*f_x\_low - 2*f_y\_high $ | $ 2*f_x\_high - 2*f_y\_low $ | $ 2*f_x\_low + 2*f_y\_low $ | $ 2*f_x\_high + 2*f_y\_high $ |
+| IMD frequency limits (MHz) | 198 | 318 | 3070 | 3190 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low - 4*f_y\_high $ | $ f_x\_high - 4*f_y\_low $ | $ f_y\_low - 4*f_x\_high $ | $ f_y\_high - 4*f_x\_low $ |
+| IMD frequency limits (MHz) | 2100 | 1950 | 2745 | 2595 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low - 3*f_y\_high $ | $ 2*f_x\_high - 3*f_y\_low $ | $ 2*f_y\_low - 3*f_x\_high $ | $ 2*f_y\_high - 3*f_x\_low $ |
+| IMD frequency limits (MHz) | 535 | 385 | 1180 | 1030 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ f_x\_low + 4*f_y\_low $ | $ f_x\_high + 4*f_y\_high $ | $ f_y\_low + 4*f_x\_low $ | $ f_y\_high + 4*f_x\_high $ |
+| IMD frequency limits (MHz) | 3644 | 3794 | 4031 | 4181 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*f_x\_low + 3*f_y\_low $ | $ 2*f_x\_high + 3*f_y\_high $ | $ 2*f_y\_low + 3*f_x\_low $ | $ 2*f_y\_high + 3*f_x\_high $ |
+| IMD frequency limits (MHz) | 3773 | 3923 | 3902 | 4052 |
+
+Based on Table 5.3.5.4-1, 3<sup>rd</sup> and 5<sup>th</sup> order IMD may also fall into Rx frequencies of third DL band n28 when CA\_n8-n20 is the UL configuration.
+
+Based on Table 5.3.5.4-2, there is no IMD interference which may also fall into Rx frequencies of third DL band n20 when CA\_n8-n28 is the UL configuration.
+
+Based on Table 5.3.5.4-3, 3<sup>rd</sup> order IMD may also fall into Rx frequencies of third DL band n8 when CA\_n20-n28 is the UL configuration.
+
+#### 5.3.5.5 REFSSENS evaluation
+
+The MSD test configurations can be evaluated as below for band n8 MSD due to IMD3 of Tx band n20 + band n28 and band n28 MSD due to IMD3 of Tx band n8 + band n20.
+
+**Table 5.3.5.5-1: REFSSENS exceptions due to IMD interference for CA\_n8-n20-n28**
+
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n8-n20-n28 | n20 | 834.5 | 5 | 25 | 793.5 | N/A | FDD | N/A |
+| | n28 | 715.5 | 5 | 25 | 770.5 | N/A | FDD | N/A |
+| | n8 | 908.5 | 5 | 25 | 953.5 | 23.5 | FDD | IMD3 |
+| | n8 | 887.5 | 5 | 25 | 932.5 | N/A | FDD | N/A |
+| | n20 | 834.5 | 5 | 25 | 793.5 | N/A | FDD | N/A |
+| | n28 | 726.5 | 5 | 25 | 781.5 | 23 | FDD | IMD3 |
+
+CA\_n8-n20-n28 2UL IMD3 MSDs are derived in Table 5.3.5.5-2 and enable a two-antenna architecture in the long-term.
+
+Table 5.3.5.5-2: 3DL/2UL IMD3 MSDs for CA\_n8-n20-n28
+
+| NR CA band combination | Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | Source of IMD |
+|------------------------|----------------------------------------------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n8-n20-n28 | n8 | N/A | 5 | 25 | 951.5 | [25] | FDD | IMD3 |
+| | n20 | 834.5 | 5 | 25 | 793.5 | N/A | FDD | N/A |
+| | n28 | 717.5 | 5 | 25 | 772.5 | N/A | FDD | N/A |
+| | n8 | 887.5 | 5 | 25 | 932.5 | N/A | FDD | N/A |
+| | n20 | 834.5 | 5 | 25 | 793.5 | N/A | FDD | N/A |
+| | n28 | N/A | 5 | 25 | 781.5 | [25] | FDD | IMD3 |
+
+## 5.4 CA\_n5-n105
+
+### 5.4.1 General
+
+In this configuration the uplink is also CA\_n5A-n105A, but there are two fall back options:
+
+DL\_n5A-n105A\_UL\_n5A\_BCS0
+
+UL\_n5A-n105A\_UL\_n105A\_BCS0
+
+The aggregated spectrum allocation for CA\_n5A-n105A is illustrated in Figure 5.4.1-1.
+
+
+
+Figure 5.4.1-1: Aggregated spectrum allocation for CA\_n5A-n105A. The diagram shows a frequency spectrum from 612 MHz to 894 MHz. It is divided into four segments: n105 DL (612-652 MHz), n105 UL (663-703 MHz), n5 UL (824-849 MHz), and n5 DL (869-894 MHz). A double-headed arrow below the segments indicates a total bandwidth of 282 MHz.
+
+Figure 5.4.1-1: Aggregated spectrum allocation for CA\_n5A-n105A
+
+### 5.4.2 UE RF architecture assumption
+
+The UE RF architectures with 2 antenna and 3 antenna are assumed in the feasibility study for CA\_n5-n105. The antenna number is the total number of antennas to support Main UL/DL and diversity DL for all bands.
+
+#### 5.4.2.1 UE RF architecture with two antennas
+
+For CA\_n5-n105 with 2-antenna implementation, there are two potential UE RF architectures as shown in Figure 5.4.2.1-1.
+
+
+
+Figure 5.4.2.1-1a: Potential UE architecture with 2 antenna to support CA\_n5-n105. The diagram shows two RF architecture options. The left option, labeled 'Main TRx', has a single TRx connected to two sPnT units, which are then connected to four antennas labeled n105, n105, n5, and n5. The right option, labeled 'Diversity TRx', has a single TRx connected to two sPnT units, which are then connected to two antennas labeled n105 and n5.
+
+Figure 5.4.2.1-1a: Potential UE architecture with 2 antenna to support CA\_n5-n105
+
+
+
+Figure 5.4.2.1-1b: Potential UE architecture with 2 antenna to support CA\_n5-n105. The diagram shows two transceivers, 'Main TRx' and 'Diversity TRx', each connected to two 'sPnT' (switch/pole) blocks. Each 'sPnT' block is connected to a triplexer. The 'Main TRx' triplexer outputs are connected to antennas labeled 'n105', 'n5', and 'n105'. The 'Diversity TRx' triplexer outputs are connected to antennas labeled 'n105', 'n105', and 'n5'.
+
+**Figure 5.4.2.1-1b: Potential UE architecture with 2 antenna to support CA\_n5-n105**
+
+The topology for 2-antenna architecture illustrated in Figure 5.4.2.1-1a is listed as below.
+
+- 1) n105UL+n105DL+n5UL+n5DL quadplexer on antenna 1
+- 2) n5DL+n105DL duplexer on antenna 2
+
+The topology for 2-antenna architecture illustrated in Figure 5.4.2.1-1b is listed as below.
+
+- 1) n5UL+n5DL+n105DL triplexer on antenna 1
+- 2) n105UL+n105DL+n5DL triplexer on antenna 2
+
+#### 5.4.2.2 UE RF architecture with three antennas
+
+Figure 5.4.2.2-1 illustrates the potential UE RF architecture for CA\_n5-n105 with a 3-antenna implementation.
+
+
+
+Figure 5.4.2.2-1: Potential UE architecture with 3 antenna to support CA\_n5-n105. The diagram shows three transceivers: 'Main TRx 1', 'Main TRx 2', and 'Diversity TRx'. Each is connected to two 'sPnT' blocks, which are in turn connected to duplexers. 'Main TRx 1' duplexers output to antennas labeled 'n5' and 'n5'. 'Main TRx 2' duplexers output to antennas labeled 'n105' and 'n105'. 'Diversity TRx' duplexers output to antennas labeled 'n105' and 'n5'.
+
+**Figure 5.4.2.2-1: Potential UE architecture with 3 antenna to support CA\_n5-n105**
+
+The topology for 3-antenna architecture illustrated in Figure 5.4.2.2-1 is listed as below:
+
+- 1) n105UL+n105DL duplexer on antenna 1
+- 2) n5UL+n5DL duplexer on antenna 2
+- 3) n5DL+n105DL duplexer on antenna 3
+
+### 5.4.3 Common for 1 band UL and 2 bands UL of CA\_n5-n105
+
+#### 5.4.3.1 Operating bands for CA
+
+The operating bands for CA\_n5-n105 are provided in Table 5.4.3.1-1.
+
+**Table 5.4.3.1-1: CA band combination of band n5+n105**
+
+| NR Band | Uplink (UL) band | | Downlink (DL) band | | Duplex mode | |
+|---------|------------------------------|-----------|------------------------------|-----------|-------------|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low} - F_{UL\_high}$ | | $F_{DL\_low} - F_{DL\_high}$ | | | |
+| n5 | 824 MHz | – 849 MHz | 869 MHz | – 894 MHz | FDD | |
+| n105 | 663 MHz | – 703 MHz | 612 MHz | – 652 MHz | FDD | |
+
+#### 5.4.3.2 Channel bandwidths per operating band for CA
+
+The supported channel bandwidths for CA\_n5-n105 are provided in Table 5.4.3.2-1.
+
+**Table 5.4.3.2-1: Supported bandwidths per CA band combination of band n5+n105**
+
+| NR CA configuration | Uplink CA configuration or single uplink carrier | NR Band | Channel bandwidth (MHz) | Bandwidth combination set |
+|---------------------|--------------------------------------------------|---------|---------------------------|---------------------------|
+| CA_n5A-n105A | CA_n5A-n105A | n5 | 5, 10, 15, 20 | 0 |
+| | | n105 | 5, 10, 15, 20, 25, 30, 35 | |
+
+#### 5.4.3.3 Identify the potential MSD issues due to harmonic/harmonic mixing/cross band isolation
+
+Table 5.4.3.3-1/2 summarizes frequency ranges where harmonics/harmonics mixing occur for CA\_n5-n105.
+
+**Table 5.4.3.3-1: Impact of UL/DL Harmonic**
+
+| Band | UL Low Band Edge | UL High Band Edge | DL Low Band Edge | DL High Band Edge | 2nd Harmonic | | 3rd Harmonic | | 4th Harmonic | | 5th Harmonic | |
+|------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|
+| | | | | | UL Low Band Edge | UL High Band Edge | UL Low Band Edge | UL High Band Edge | UL Low Band Edge | UL High Band Edge | UL Low Band Edge | UL High Band Edge |
+| n5 | 824 | 849 | 869 | 894 | 1648 | 1698 | 2472 | 2547 | 3296 | 3396 | 4120 | 4245 |
+| n105 | 663 | 703 | 612 | 652 | 1326 | 1406 | 1989 | 2109 | 2652 | 2812 | 3315 | 3515 |
+
+**Table 5.4.3.3-2: Impact of UL/DL Harmonic mixing**
+
+| Band | UL Low Band Edge | UL High Band Edge | DL Low Band Edge | DL High Band Edge | 2nd Harmonic | | 3rd Harmonic | | 4th Harmonic | | 5th Harmonic | |
+|------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|------------------|-------------------|
+| | | | | | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge |
+| n5 | 824 | 849 | 869 | 894 | 1738 | 1788 | 2607 | 2682 | 3476 | 3576 | 4345 | 4470 |
+| n105 | 663 | 703 | 612 | 652 | 1224 | 1304 | 1836 | 1956 | 2448 | 2608 | 3060 | 3260 |
+
+Based on the above analysis, there is no need to study MSD due to harmonics and harmonics mixing for CA\_n5-n105.
+
+#### 5.4.3.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+Two-antenna architecture with dual triplexer can be used as a baseline to study $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ . By referring to contribution [7], it seems that two-antenna solutions with quadplexer or triplexer are not very challenging for CA\_n5-n105 as the frequency gap between band n5 UL part and band n105 DL part is larger than 100MHz. Thus, general values for low band combinations can be used for Delta Tib and Rib.
+
+**Table 5.4.3.4-1: $\Delta T_{IB,c}$ for 2-antenna implementation**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5-n105 | n5 | 0.5 |
+| | n105 | 0.5 |
+
+**Table 5.4.3.4-2: $\Delta R_{IB,c}$ for 2-antenna implementation**
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5-n105 | n5 | 0 |
+| | n105 | 0 |
+
+By referring to contribution [8], the two antenna implementation should drive the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values for CA\_n5-n105. Based on other LB-LB cases, and especially DC\_5\_n71, a Delta T of 0.5dB for both bands can be used. For Delta Rib, CA\_n5-n12 values can be reused.
+
+**Table 5.4.3.4-3: $\Delta T_{IB,c}$ for 2-antenna implementation**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5-n105 | n5 | 0.5 |
+| | n105 | 0.5 |
+
+**Table 5.4.3.4-4: $\Delta R_{IB,c}$ for 2-antenna implementation**
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5-n105 | n5 | 0.5 |
+| | n105 | 0.3 |
+
+By referring to contribution [9], the following values are derived for $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ :
+
+**Table 5.4.3.4-5: $\Delta T_{IB,c}$ for 2-antenna implementation**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5-n105 | n5 | 0.5 |
+| | n105 | 0.5 |
+
+**Table 5.4.3.4-6: $\Delta R_{IB,c}$ for 2-antenna implementation**
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ [dB] |
+|-----------------------------|---------|------------------------|
+| CA_n5-n105 | n5 | 0.2 |
+| | n105 | 0.2 |
+
+#### 5.4.3.5 RESENS exception evaluation for one UL band
+
+By referring to contribution [7], the following evaluation for MSD due to cross band isolation is provided for CA\_n5-n105.
+
+Table 5.4.3.5-1 MSD due to Cross band isolation from n5 to n105
+
+| | parameters | n105 main path | n105 diversity path |
+|----------------------------------------------------------------------|------------|----------------|---------------------|
+| transmit power for n5, dBm | | 23 | 23 |
+| Tx band n5 BW(MHz, Lcrb) | 20 | | |
+| RFFE loss, dB | 4 | | |
+| Diplexer isolation at n5 uplink freq, dB | 10 | | |
+| antenna isolation, dB | 10 | | |
+| n105 receiver signal at ANT port, dBm | | 13 | 13 |
+| | | | |
+| n105 filter rejection at 814~849MHz, dB | 40 | | |
+| signal After n105 filter, dBm | | -31 | -31 |
+| Typical receiver IIP2, dB | 50 | | |
+| TX IM2 noise level refer to RX LNA input, dBm | | -112 | -112 |
+| front-end loss | 4 | | |
+| TX IM2 noise level at ANT port, dBm | | -108 | -108 |
+| | | | |
+| noise figure dB | 11.8 | | |
+| Thermal noise at RX ant port(dBm/Hz) | -162.2 | | |
+| Rx band n105 BW(MHz, NRB) | 4.5 | | |
+| Thermal noise, dBm | | -95.67 | -95.67 |
+| | | | |
+| ACLR1, dB | 30 | | |
+| ACLR2, dB | 43 | | |
+| n5 PA leakage PSD at PA output port at 1st adjacent channel, dBm/MHz | | -20.01 | |
+| n5 PA leakage PSD at PA output port at 2nd adjacent channel, dBm/MHz | | -33.01 | |
+| n5 PA noise PSD at PA output port, dBm/Hz | -130 | | |
+| n5 PA noise PSD at PA output port, dBm/RxBW | | -63.47 | |
+| n5 Tx filter rejection at 612~652MHz, dB | 30 | | |
+| n5 PA noise power at Rx n105 ant port at 612~652MHz, dBm | | -103.47 | -103.47 |
+| | | | |
+| | | | |
+| | | | |
+| Total noise level at ANT port | | -94.79 | -94.79 |
+| SNR requirement for QPSK | -1 | | |
+| REFSENSE (referred to antenna)(5MHz BW) | | -95.79 | -95.79 |
+| Implementation Margin, dB | 2 | | |
+| combined REFSENS(5MHz BW), dBm | -96.80 | | |
+| MSD | 0.40 | | |
+
+Table 5.4.3.5-2 MSD due to Cross band isolation from n105 to n5
+
+| | parameters | n5 main path | n5 diversity path |
+|------------------------------------------------------------------------|------------|--------------|-------------------|
+| transmit power for n105, dBm | | 23 | 23 |
+| Tx band n105 BW(MHz, Lcrb) | 20 | | |
+| RFFE loss, dB | 4 | | |
+| Diplexer isolation at n105 uplink freq, dB | 10 | | |
+| antenna isolation, dB | 10 | | |
+| n5 receiver signal at ANT port, dBm | | 13 | 13 |
+| | | | |
+| n5 filter rejection at 663~703MHz, dB | 40 | | |
+| signal After n5 filter, dBm | | -31 | -31 |
+| Typical receiver IIP2, dB | 50 | | |
+| TX IM2 noise level refer to RX LNA input, dBm | | -112 | -112 |
+| front-end loss | 4 | | |
+| TX IM2 noise level at ANT port, dBm | | -108 | -108 |
+| | | | |
+| noise figure dB | 11 | | |
+| Thermal noise at RX ant port(dBm/Hz) | -163 | | |
+| Rx band n5 BW(MHz, NRB) | 4.5 | | |
+| Thermal noise, dBm | | -96.47 | -96.47 |
+| | | | |
+| ACLR1, dB | 30 | | |
+| ACLR2, dB | 43 | | |
+| n105 PA leakage PSD at PA output port at 1st adjacent channel, dBm/MHz | | -20.01 | |
+| n105 PA leakage PSD at PA output port at 2nd adjacent channel, dBm/MHz | | -33.01 | |
+| n105 PA noise PSD at PA output port, dBm/Hz | -130 | | |
+| n105 PA noise PSD at PA output port, dBm/RxBW | | -63.47 | |
+| n105 Tx filter rejection at 869~894MHz, dB | 30 | | |
+| n105 PA noise power at Rx n105 ant port at 869~894MHz, dBm | | -103.47 | -103.47 |
+| | | | |
+| | | | |
+| | | | |
+| Total noise level at ANT port | | -95.43 | -95.43 |
+| SNR requirement for QPSK | -1 | | |
+| REFSENSE (referred to antenna)(5MHz BW) | | -96.43 | -96.43 |
+| Implementation Margin, dB | 2 | | |
+| combined REFSENS(5MHz BW), dBm | -97.44 | | |
+| MSD | 0.56 | | |
+
+Based on the above evaluation, the REFSENS degradation can be neglected. Thus, there is no need to specify MSD due to cross band isolation for CA\_n5-n105.
+
+By referring to contribution [8], the 1UL cross band interference is as follows for the IMD orders of the allocated UL Resource blocks (RBs) and its image:
+
+For the n105 20MHz maximum UL CBW, the IMD interference order to n5 is >9 RBs
+
+For the n5 20MHz maximum UL CBW, the IMD interference order to n105 is >9 RBs
+
+Given this, there is no MSD due to IMDs. Nonetheless, the transmitter noise floor must be considered.
+
+With the architecture aspects discussed above and the need to support multiple LBLB cases, conservative values should be considered:
+
+45dB cross band Tx-Rx isolation for the triplexers
+
+40dB Tx rejection in the other DL band
+
+10dB antenna couplingf
+
+4dB post PA losses
+
+Transmitter noise floor of -125dBm/Hz.
+
+Based on these assumptions, the MSD with MRC combining is calculated in Table 5.4.3.5-3.
+
+**Table 5.4.3.5-3: MRC calculations for band n5 and n105 Cross-band MSD.**
+
+| CBW/NRB | band<br>[MHz]/# | n105 | | n5 | |
+|-------------------------------------------------------------|-----------------|-------|--------|-------|--------|
+| | | 5 | 25 | 5 | 25 |
+| transmitter noise floor | [dBm/CBW] | -58.5 | | -58.5 | |
+| 5MHz CBW REFSENS | [dBm/CBW] | -97.2 | | -98.0 | |
+| RX noise floor wo Tx noise: <b>Main/Div</b> | [dBm/CBW] | -93.2 | -93.2 | -94.0 | -94.0 |
+| <b>Tx-Rx / Tx-Ant duplexer isolation/rejection</b> | [dB] | 45 | 40 | 45 | 40 |
+| LNA to antenna insertion loss | [dB] | 4 | | 4 | |
+| Antenna isolation | [dB] | 0 | 10 | 0 | 10 |
+| PC3 1Tx interference levels: <b>Main/Div</b> | [dBm/CBW] | -99.5 | -104.5 | -99.5 | -104.5 |
+| noise floor degradation due to Tx noise:<br><b>Main/Div</b> | [dB] | 0.9 | 0.3 | 1.1 | 0.4 |
+| noise floor degradation due to Tx noise:<br><b>Main/Div</b> | [lin] | 1.2 | 1.1 | 1.3 | 1.1 |
+| REFSENS degradation after MRC | uncor [dB] | 0.6 | | 0.7 | |
+| REFSENS degradation after MRC | cor [dB] | 1.1 | | 1.3 | |
+
+1UL cross-band MSD for CA\_n5-n105 is proposed in Table 5.4.3.5-4.
+
+**Table 5.4.3.5-4: CA\_n5-n105 1UL cross-band MSD**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n105 | n5 | 693 | 20 | 15 | 20 (RBstart=86) | 871.5 | 5 | 1.3 | >ACLR2 |
+| n5 | n105 | 834 | 20 | 15 | 20 (RBstart=0) | 649.5 | 5 | 1.1 | >ACLR2 |
+
+By referring to contribution [9], one aspect that needs to be pointed out is that n105 is a recently standardised band, with very challenging frequency arrangements from RF filtering point of view. Hence, especially given the band is new and implementations are just under development, we don't see it possible to optimize the CA characteristics at the expense of attenuation at US CH36 and n105 TX/RX isolations. Please note that the numbers are not derived from dedicated triplexers, but instead from what can be achieved by matching DPX and RX filters together, without optimizations which may offer improved performance over time.
+
+The MSD with MRC combining is calculated in Table 5.4.3.5-5 and Table 5.4.3.5-6.
+
+Table 5.4.3.5-5 MSD due to cross band isolation n105 to n5
+
+| <b>n5 Cross-band MSD</b> | <b>PRX</b> | <b>DRX</b> |
+|------------------------------|------------|------------|
+| BW | | 4.5 |
+| FE Loss | 4.0 | 4.0 |
+| Output Power | | 23 |
+| TX Noise per BW at PA Output | -57.9 | |
+| RX_IIP2, dBm | 54 | 54 |
+| Antenna Isolation | | 10 |
+| RX Isolation | -42 | -38 |
+| TX Isolation | -50 | -40 |
+| TX_IM2 | -102.0 | -110.0 |
+| Tx_noise | -95.9 | -101.9 |
+| TX_total | -95.0 | -101.3 |
+| Thermal noise | -94.0 | -94.0 |
+| Composite | -91.5 | -93.3 |
+| MRC REFSENS | | -95.4 |
+| n5 REFSENS | | -98 |
+| n5 MSD | | 2.6 |
+
+Table 5.4.3.5-6 MSD due to cross band isolation n5 to n105
+
+| <b>n105 Cross-band MSD</b> | <b>PRX</b> | <b>DRX</b> |
+|------------------------------|------------|------------|
+| BW | | 4.5 |
+| FE Loss | 4.0 | 4.0 |
+| Output Power | | 23 |
+| TX Noise per BW at PA Output | -56.9 | |
+| RX_IIP2, dBm | 54 | 54 |
+| Antenna Isolation | | 10 |
+| RX Isolation | -37 | -32 |
+| TX Isolation | -30 | -40 |
+| TX_IM2 | -62.0 | -110.0 |
+| Tx_noise | -89.9 | -94.9 |
+| TX_total | -62.0 | -94.7 |
+| Thermal noise | -93.2 | -93.2 |
+| Composite | -62.0 | -90.9 |
+| MRC REFSENS | | -91.6 |
+| n105 REFSENS | | -97.2 |
+| n105 MSD | | 5.6 |
+
+1UL cross-band MSD for CA\_n5-n105 is proposed in Table 5.4.3.5-7.
+
+**Table 5.4.3.5-7: CA\_n5-n105 1UL cross-band MSD**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n105 | n5 | 693 | 20 | 15 | 20 (RBstart=86) | 871.5 | 5 | 2.6 | >ACLR2 |
+| n5 | n105 | 834 | 20 | 15 | 20 (RBstart=0) | 649.5 | 5 | 5.6 | >ACLR2 |
+
+### 5.4.4 Specific for 2 bands UL of CA\_n5-n105
+
+#### 5.4.4.1 Maximum output power for inter-band CA
+
+Power class 3 is assumed for UL CA\_n5-n105
+
+#### 5.4.4.2 UE co-existence studies
+
+Table 5.4.4.2-1 lists Band n5 + Band n105 2UL bands CA 2nd, 3rd, 4th and 5th order IMD for the UE-to-UE coexistence analysis.
+
+Table 5.4.4.2-1: Band n5 and Band n105 UL IMD products
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------|-----------------------|----------------------|-----------------------|
+| UL frequency (MHz) | 663 | 703 | 824 | 849 |
+| 2 <sup>nd</sup> order IMD products | fy_low – fx_high | fy_high – fx_low | fy_low + fx_low | fy_high + fx_high |
+| IMD frequency limits (MHz) | 121 | 186 | 1487 | 1552 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low – fy_high | 2*fx_high – fy_low | 2*fy_low – fx_high | 2*fy_high – fx_low |
+| IMD frequency limits (MHz) | 477 | 582 | 945 | 1035 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high |
+| IMD frequency limits (MHz) | 2150 | 2255 | 2311 | 2401 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low – 1*fy_high | 3*fx_high – 1*fy_low | 3*fy_low – 1*fx_high | 3*fy_high – 1*fx_low |
+| IMD frequency limits (MHz) | 1140 | 1285 | 1769 | 1884 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low + 1*fy_low | 3*fx_high + 1*fy_high | 3*fy_low + 1*fx_low | 3*fy_high + 1*fx_high |
+| IMD frequency limits (MHz) | 2813 | 2958 | 3135 | 3250 |
+| Two-tone 4 <sup>th</sup> order IMD products | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low | 2*fx_low + 2*fy_low | 2*fx_high + 2*fy_high |
+| IMD frequency limits (MHz) | 372 | 242 | 2974 | 3104 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low – 4*fy_high | fx_high – 4*fy_low | fy_low – 4*fx_high | fy_high – 4*fx_low |
+| IMD frequency limits (MHz) | 2733 | 2593 | 1988 | 1803 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low |
+| IMD frequency limits (MHz) | 1221 | 1066 | 461 | 291 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low + 4*fy_low | fx_high + 4*fy_high | fy_low + 4*fx_low | fy_high + 4*fx_high |
+| IMD frequency limits (MHz) | 3959 | 4099 | 3476 | 3661 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low + 3*fy_low | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low | 2*fy_high + 3*fx_high |
+| IMD frequency limits (MHz) | 3798 | 3953 | 3637 | 3807 |
+
+Based on the above analysis, there is no IMD issue for CA\_n5-n105 with 2UL configuration. Table 5.4.4.2-2 lists the protected bands required for CA\_n5-n105 with 2UL configuration.
+
+Table 5.4.4.2-2: Band n5 and Band n105 UL IMD products
+
+| NR CA Configuration | Spurious emission | | | | | |
+|---------------------|----------------------------------------------------------------------------------------------------------|-----------------------|---|----------------------|-----------|-------|
+| | Protected band | Frequency range (MHz) | | Maximum Level (dBm) | MBW (MHz) | NOTE |
+| CA_n5-n105 | E-UTRA Band 1, 3, 4, 5, 8, 11, 18, 19, 21, 26, 28, 31, 38, 40, 43, 50, 51, 65, 66, 73, 74<br>NR Band n79 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | |
+| | E-UTRA Band 41, 52<br>NR Band n77, n78 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 2 |
+| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 8 |
+
+NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{\text{CRB}} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.
+
+NOTE 8: Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz.
+
+#### 5.4.4.3 REFSSENS exception evaluation for two UL band
+
+It is not required to study the MSD due to two UL IMD interference since there is no two UL IMD issue for CA\_n5-n105.
+
+## 5.5 CA\_n28-n105
+
+### 5.5.1 General
+
+Figure 5.5.1-1 shows the aggregated spectrum allocation for CA\_n28A-n105A where no frequency range restriction has been indicated for either of the constituent bands.
+
+
+
+Figure 5.5.1-1 CA\_n28A-n105A spectrum allocation diagram showing four contiguous blocks: n105 DL (612-652 MHz), n105 UL (652-663 MHz), n28 UL (663-748 MHz), and n28 DL (748-803 MHz). A double-headed arrow at the bottom indicates a total bandwidth of 191 MHz from 612 MHz to 803 MHz.
+
+Figure 5.5.1-1 CA\_n28A-n105A spectrum allocation
+
+In this study item, only a single UL configuration is considered for the combination due to the concern of 2UL IMD issue as described in sub-clause 5.5.2.3.
+
+### 5.5.2 UE RF architectures assumption
+
+Both 2-antenna and 3-antenna implementations are considered in the study item where the corresponding UE RF architectures are further detailed in the following sub-clauses.
+
+#### 5.5.2.1 UE RF architectures with two antennas
+
+For CA\_n28A-n105A with 2-antenna implementation, there can be two potential architecture variants, one with a triplexer and a quadplexer in the main signal path and a duplexer in the diversity signal path, as shown in Figure
+
+5.5.2.1-1, the other is with dual triplexers in main signal path and a triplexer in diversity signal path, as shown in Figure 5.5.2.1-2.
+
+
+
+Figure 5.5.2.1-1: CA\_n28A-n105A UE RF first architecture variant with 2-antenna implementation. The diagram shows a 'Main TRx' connected to two 'SPnT' blocks. The first 'SPnT' block is connected to a triplexer that feeds three antennas labeled 'n105', 'n105/n28A', and 'n28A'. The second 'SPnT' block is connected to a triplexer that feeds four antennas labeled 'n105', 'n105', 'n28B', and 'n28B'. A 'Diversity Rx' is connected to two 'SPnT' blocks. The first 'SPnT' block is connected to a triplexer that feeds two antennas labeled 'n105' and 'n28'.
+
+Figure 5.5.2.1-1 CA\_n28A-n105A UE RF first architecture variant with 2-antenna implementation
+
+
+
+Figure 5.5.2.1-2: CA\_n28A-n105A second architecture variant with 2-antenna implementation. The diagram shows a 'Main TRx' connected to two 'SPnT' blocks. The first 'SPnT' block is connected to a triplexer that feeds three antennas labeled 'n105', 'n28A', and 'n28A'. The second 'SPnT' block is connected to a triplexer that feeds three antennas labeled 'n105', 'n28B', and 'n28B'. A 'Diversity Rx' is connected to two 'SPnT' blocks. The first 'SPnT' block is connected to a triplexer that feeds three antennas labeled 'n105', 'n105', and 'n28'.
+
+Figure 5.5.2.1-2 CA\_n28A-n105A second architecture variant with 2-antenna implementation
+
+The first architecture variant, due to the relatively wide frequency range (a single filter covering both n28 and n105) in the middle sub-band for the main signal path triplexer, is considered rather challenging and impracticable for implementation and will not be further pursued in this study item.
+
+For the second architecture variant, both the main antenna and diversity antenna design need to cover the entire spectrum range of 191 MHz simultaneously as shown in Figure 5.5.1-1, which is equivalent to a 27% bandwidth ratio and that would exceed the bandwidth ratio for a typical planar antenna design in a smartphone. As a result, the radiative performance for the combination likely would be compromised.
+
+#### 5.5.2.2 UE RF architectures with three antennas
+
+For the 3-antenna implementation, the two of the three antennas are used in the main path to aggregate the n28 and n105 signals over the air, as shown in Figure 5.5.2.2-1. As n28 and n105 signals do not need to be combined through a
+
+multiplexer, there is no additional insertion loss in both n28 and n105 main signal paths as compared to the single-band implementation.
+
+
+
+Figure 5.5.2.2-1: CA\_n28A-n105A UE RF architecture with 3-antenna implementation. The diagram shows three antenna configurations. The first configuration has a 'Main TRx' connected to two 'SPnT' blocks, which are then connected to two 'n105' antennas. The second configuration has a 'Main TRx' connected to two 'SPnT' blocks, which are then connected to two 'n28A' antennas and two 'n28B' antennas. The third configuration has a 'Diversity Rx' connected to two 'SPnT' blocks, which are then connected to an 'n105' antenna and an 'n28' antenna.
+
+**Figure 5.5.2.2-1 CA\_n28A-n105A UE RF architecture with 3-antenna implementation**
+
+Having two antenna in the main signal path not only avoids the more complicated multiplexer implementation and the associated additional insertion losses, but also allows narrower frequency coverage for each of the two antennas as compared to single-antenna implementation. However, the additional antenna cannot be added without occupying more phone space. Therefore, the feasibility on placing more than two low-band antennas in a smartphone needs to be investigated, with narrower bandwidth and regressed radiating performance expected due to the limitation in form factor.
+
+#### 5.5.2.3 2UL IMD issue
+
+2UL IMD3/IM5 may fall into either n105 DL or n28 DL or both DL bands simultaneously to cause REFSSENS degradation (MSD), as conceptually illustrated in Figure 5.5.2.3-1.
+
+
+
+Figure 5.5.2.3-1: Conceptual illustration on 2UL IMD3/IMD5 impact to DL bands for CA\_n28A-n105A. The figure shows two rows of frequency band diagrams. The top row illustrates IMD3 impact: the first diagram shows n105 DL (612-652 MHz) with IMD3 at 652 MHz; the second diagram shows n105 UL (663-703 MHz) and n28 UL (703-748 MHz) with IMD3 at 748 MHz; the third diagram shows n28 DL (758-803 MHz) with IMD3 at 803 MHz. The bottom row illustrates IMD5 impact: the first diagram shows n105 DL (612-652 MHz) with IMD5 at 652 MHz; the second diagram shows n105 UL (663-703 MHz) and n28 UL (703-748 MHz) with IMD5 at 748 MHz; the third diagram shows n28 DL (758-803 MHz) with IMD5 at 758 MHz.
+
+**Figure 5.5.2.3-1 Conceptual illustration on 2UL IMD3/IMD5 impact to DL bands for CA\_n28A-n105A**
+
+For both 2-antenna and 3-antenna implementations, depending on the carrier allocation and Tx filter isolation on the two UL carriers, the MSD caused by two simultaneous up links (2UL) IMD3 to n105 DL carrier could potentially be higher than 30 dB; especially when the n28 UL carrier is close to n105 UL band where the n105 Tx filter does not provide any rejection to n28 UL carrier and the n105 PA reverse IMD would dominate the MSD. For carrier allocations where both Tx filters can provide sufficient isolation to the cross-band UL carriers, the MSD caused by 2UL IMD3 could still be around 20 dB to either or both of the DL carriers which would be dominated by PA forward IMD.
+
+Due to the concern of the 2UL IMD issue, only single UL configuration is considered in this study item where UL can be in either n28 or n105.
+
+#### 5.5.2.4 Cross-band interference
+
+Apart from the 2UL IMD concern, the combination may also be subject to cross-band UL to DL interference issue due to frequency proximity even under single UL operation where the REFSSENS impact needs to be further analyzed.
+
+### 5.5.3 Common for 1 band UL and 2 bands UL of CA\_n28-n105
+
+#### 5.5.3.0 General
+
+This band combination is similar to the case of CA\_n71-n85 with the two UL bandwidths having no frequency gap between them. CA\_n71-n85 is being specified for 1UL only as 2 ULs showed significant MSD challenges.
+
+#### 5.5.3.1 Operating bands for CA
+
+**Table 5.5.3.1-1: CA band combination of band n28+n105**
+
+| NR Band | Uplink (UL) band | | Downlink (DL) band | | Duplex mode | |
+|---------|------------------------------|-----------|------------------------------|-----------|-------------|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low} - F_{UL\_high}$ | | $F_{DL\_low} - F_{DL\_high}$ | | | |
+| n28 | 703 MHz | – 748 MHz | 758 MHz | – 803 MHz | FDD | |
+| n105 | 663 MHz | – 703 MHz | 612 MHz | – 652 MHz | FDD | |
+
+#### 5.5.3.2 Channel bandwidths per operating band for CA
+
+Based on WF [14], it was agreed that only 1UL configuration will be supported, the 2UL issues will be described in section 5.5.4. Thus, BCS0 for CA\_n28A-n105A can be specified as below.
+
+**Table 5.5.3.2-1: Supported bandwidths per CA band combination of band n28+n105**
+
+| NR CA configuration | Uplink CA configuration or single uplink carrier | NR Band | Channel bandwidth (MHz) | Bandwidth combination set |
+|---------------------|--------------------------------------------------|---------|--------------------------------------------------------------------|---------------------------|
+| CA_n28A-n105A | - | n28 | 5, 10, 15, 20, 25, 30 | 0 |
+| | | n105 | 5, 10, 15, 20, 25 <sup>1</sup> , 30 <sup>1</sup> , 35 <sup>1</sup> | |
+
+NOTE 1: These n105 channel bandwidths are valid in DL only
+
+#### 5.5.3.3 UE co-existence studies
+
+Table 5.5.3.3-1/2 summarizes frequency ranges where UL harmonics and/or harmonic mixing occur for CA\_n28-n105.
+
+**Table 5.5.3.3-1: Impact of UL/DL Harmonic**
+
+| | UL | | DL | | 2 <sup>nd</sup> Harmonic | | 3 <sup>rd</sup> Harmonic | | 4 <sup>th</sup> Harmonic | | 5 <sup>th</sup> Harmonic | |
+|------|---------------|----------------|---------------|----------------|--------------------------|----------------|--------------------------|----------------|--------------------------|----------------|--------------------------|----------------|
+| | Low Band Edge | High Band Edge | Low Band Edge | High Band Edge | Low Band Edge | High Band Edge | Low Band Edge | High Band Edge | Low Band Edge | High Band Edge | Low Band Edge | High Band Edge |
+| n28 | 703 | 748 | 758 | 803 | 1406 | 1496 | 2109 | 2244 | 2812 | 2992 | 3515 | 3740 |
+| n105 | 663 | 703 | 612 | 652 | 1326 | 1406 | 1989 | 2109 | 2652 | 2812 | 3315 | 3515 |
+
+Based on the above table, there is no UL harmonic issue for CA\_n28-n105.
+
+**Table 5.5.3.3-2: Impact of UL/DL Harmonic mixing**
+
+| Band | UL | | DL | | 2 <sup>nd</sup> Harmonic | | 3 <sup>rd</sup> Harmonic | | 4 <sup>th</sup> Harmonic | | 5 <sup>th</sup> Harmonic | |
+|------|---------------|----------------|---------------|----------------|--------------------------|-------------------|--------------------------|-------------------|--------------------------|-------------------|--------------------------|-------------------|
+| | Low Band Edge | High Band Edge | Low Band Edge | High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge | DL Low Band Edge | DL High Band Edge |
+| n28 | 703 | 748 | 758 | 803 | 1516 | 1606 | 2274 | 2409 | 3032 | 3212 | 3790 | 4015 |
+| n105 | 663 | 703 | 612 | 652 | 1224 | 1304 | 1836 | 1956 | 2448 | 2608 | 3060 | 3260 |
+
+Based on the above table, there is no harmonic mixing issue for CA\_n28-n105.
+
+Since the two bands are very close, cross-band isolation may be an issue as shown in Figure 5.5.3.3-3 below, the Table 5.5.3.3-4 provides the analysis for the potential IMD order of the UL configuration and its image for the largest channel bandwidths.
+
+
+
+Figure 5.5.3.3-3: IMD landscape for 1UL and 2UL configurations of CA\_n28-n105. The figure shows a frequency spectrum from 610 to 870 MHz with various bands and their interactions. It includes labels for n71, n105, n28, n26, n5, n85, n29, n77, n80, n79, n78, n76, n75, n74, n73, n72, n71, n70, n69, n68, n67, n66, n65, n64, n63, n62, n61. It also shows UL and DL configurations with their respective bandwidths and edge frequencies. The IMD landscape is divided into four rows (1, 2, 3, 4) showing different UL configurations and their resulting IMD products.
+
+Figure 5.5.3.3-3: IMD landscape for 1UL and 2UL configurations of CA\_n28-n105
+
+Table 5.5.3.3-4: Cross band isolation issues
+
+| UL Band | UL Low Band Edge | UL High Band Edge | DL Band | DL Low Band Edge | DL High Band Edge | UL to DL distance | Maximum UL BW | Source of interference (IMD order of UL RBs and their image) |
+|---------|------------------|-------------------|---------|------------------|-------------------|-------------------|---------------|--------------------------------------------------------------|
+| n28 | 703 | 748 | n105 | 612 | 652 | 51 | 30 | ACLR2 (IMD5) |
+| n105 | 663 | 703 | n28 | 758 | 803 | 55 | 20 | ACLR3 (IMD7) |
+
+As shown in the above Table 5.5.3.3-4, the band n28 30MHz CBW UL ACLR2 overlaps with the band n105 DL while the band n105 20MHz CBW UL ACLR3 overlaps with band n28 DL. Both MSDs need to be evaluated.
+
+#### 5.5.3.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n28-n105 the 2 antenna implementation should drive the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values, three companies provided input that is summarized in the two tables below.
+
+Table 5.5.3.4-1: $\Delta T_{IB,c}$ due to NR CA (two bands)
+
+| Inter-band CA combination | $\Delta T_{IB,c}$ for NR bands (dB) <sup>9</sup> | |
+|---------------------------|-----------------------------------------------------------------|--------------------------------------|
+| | Component band in order of bands in configuration <sup>10</sup> | Proposed values by company A / B / C |
+| CA_n28-n105 | 1.0 / 0.7 / 0.8 | 1.0 / 0.7 / 0.8 |
+
+NOTE 9: “-” denotes $\Delta T_{IB,c} = 0$ .
+NOTE 10: The component band order in the configuration should be listed by the order of NR bands, such as for CA\_n1-n3 the band order from left to right is n1 and n3.
+
+Table 5.5.3.4-2: $\Delta R_{IB,c}$ due to NR CA (two bands)
+
+| Inter-band CA combination | $\Delta R_{IB,c}$ for NR bands (dB) <sup>8</sup> | |
+|---------------------------|----------------------------------------------------------------|--------------------------------------|
+| | Component band in order of bands in configuration <sup>9</sup> | Proposed values by company A / B / C |
+| CA_n28-n105 | 1.0 / 0.4 / 0.2 | 1.0 / 0.4 / 0.2 |
+
+NOTE 8: “-” denotes $\Delta R_{IB,c} = 0$ .
+NOTE 9: The component band order in the configuration should be listed by the order of NR bands, such as for CA\_n1-n77 the band order from left to right is n1 and n77.
+
+#### 5.5.3.5 REFSSENS evaluation
+
+For CA\_n28-n105, the 2 antennas implementation n28 and n105 MSDs related to cross band isolation described in Table 5.5.3.3-4 must be evaluated.
+
+Three companies provided their evaluation for both cross band MSDs.
+
+For n28 MSD due to n105 UL, one company suggested that no MSD was needed while the two other companies' input can be found in Table 5.5.3.5-1a and b respectively.
+
+**Table 5.5.3.5-1a n28 MSD due to cross band isolation for CA\_n28-n105 with n105 UL (company A)**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n105 | n28 | 693 | 20 | 15 | 20 (RBstart=86) | 760.5 | 5 | 3.7 | >ACLR2 |
+
+**Table 5.5.3.5-1b n28 MSD due to cross band isolation for CA\_n28-n105 with n105 UL (company B)**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n105 | n28 | 693 | 20 | 15 | 20 (RBstart=86) | 760.5 | 5 | 10.8 | >ACLR2 |
+
+Similarly, for n105 MSD due to n28 UL, the three companies' input can be found in Table 5.5.3.5-1a, b and c.
+
+**Table 5.5.3.5-2a n105 MSD due to cross band isolation for CA\_n28-n105 with n28 UL (company A)**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n28 | n105 | 718 | 30 | 15 | 25 (RBstart=0) | 649.5 | 5 | 17 | ACLR2 |
+
+**Table 5.5.3.5-2b n105 MSD due to cross band isolation for CA\_n28-n105 with n28 UL (company B)**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n28 | n105 | 718 | 30 | 15 | 25 (RBstart=0) | 649.5 | 5 | 12.7 | ACLR2 |
+
+**Table 5.5.3.5-2c n105 MSD due to cross band isolation for CA\_n28-n105 with n28 UL (company C)**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n28 | n105 | 718 | 30 | 15 | 25 (RBstart=0) | 649.5 | 5 | 10.1 | ACLR2 |
+
+### 5.5.4 Specific for 2 bands UL of fallback CA\_n28-n105
+
+#### 5.5.4.1 Maximum output power for inter-band CA
+
+Power class 3 was assumed for UL CA\_n28-n105, but as discussed in the next clauses, it was decided that the two UL configuration will not be supported due to significant IMD3 MSD and potential co-existence issues with DTV channels.
+
+#### 5.5.4.2 UE co-existence studies
+
+Table 5.5.4.2-1 lists Band n28 + Band n105 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis.
+
+**Table 5.5.4.2-1 IMD interference analysis for CA\_n28-n105 with 2 ULs**
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|--------------------------------------|----------------------|-----------------------|----------------------|-----------------------|
+| UL frequency (MHz) | 663 | 703 | 703 | 748 |
+| 2nd harmonics frequency limits | 2*fx_low | 2*fx_high | 2*fy_low | 2*fy_high |
+| 2nd harmonics frequency limits (MHz) | 1326 | 1406 | 1406 | 1496 |
+| 3rd harmonics frequency limits | 3*fx_low | 3*fx_high | 3*fy_low | 3*fy_high |
+| 3rd harmonics frequency limits (MHz) | 1989 | 2109 | 2109 | 2244 |
+| 4th harmonics frequency limits | 4*fx_low | 4*fx_high | 4*fy_low | 4*fy_high |
+| 4th harmonics frequency limits (MHz) | 2652 | 2812 | 2812 | 2992 |
+| 5th harmonics frequency limits | 5*fx_low | 5*fx_high | 5*fy_low | 5*fy_high |
+| 5th harmonics frequency limits (MHz) | 3315 | 3515 | 3515 | 3740 |
+| 6th harmonics frequency limits | 6*fx_low | 6*fx_high | 6*fy_low | 6*fy_high |
+| 6th harmonics frequency limits (MHz) | 3978 | 4218 | 4218 | 4488 |
+| 7th harmonics frequency limits | 7*fx_low | 7*fx_high | 7*fy_low | 7*fy_high |
+| 7th harmonics frequency limits (MHz) | 4641 | 4921 | 4921 | 5236 |
+| 2nd order IMD products | fy_high - fx_low | fy_low - fx_high | fy_low + fx_low | fy_high + fx_high |
+| IMD frequency limits (MHz) | 85 | 0 | 1366 | 1451 |
+| 3rd order IMD products | fy_high - 2*fx_low | fy_low - 2*fx_high | 2*fy_low - fx_high | 2*fy_high - fx_low |
+| IMD frequency limits (MHz) | 578 | 703 | 703 | 833 |
+| 3rd order IMD products | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high |
+| IMD frequency limits (MHz) | 2029 | 2154 | 2069 | 2199 |
+| Two-tone 4th order IMD products | 2*fx_low - 2*fy_high | 2*fx_high - 2*fy_low | 2*fx_low + 2*fy_low | 2*fx_high + 2*fy_high |
+| IMD frequency limits (MHz) | 170 | 0 | 2732 | 2902 |
+| Two-tone 4th order IMD products | 3*fx_low - 1*fy_high | 3*fx_high - 1*fy_low | 3*fy_low - 1*fx_high | 3*fy_high - 1*fx_low |
+| IMD frequency limits (MHz) | 1241 | 1406 | 1406 | 1581 |
+| Two-tone 4th order IMD products | 3*fx_low + 1*fy_low | 3*fx_high + 1*fy_high | 3*fy_low + 1*fx_low | 3*fy_high + 1*fx_high |
+| IMD frequency limits (MHz) | 2692 | 2857 | 2772 | 2947 |
+| Two-tone 5th order IMD products | fx_low - 4*fy_high | fx_high - 4*fy_low | fy_low - 4*fx_high | fy_high - 4*fx_low |
+| IMD frequency limits (MHz) | 2329 | 2109 | 2109 | 1904 |
+| Two-tone 5th order IMD products | fx_low + 4*fy_low | fx_high + 4*fy_high | fy_low + 4*fx_low | fy_high + 4*fx_high |
+| IMD frequency limits (MHz) | 3475 | 3695 | 3355 | 3560 |
+| Two-tone 5th order IMD products | 2*fx_low - 3*fy_high | 2*fx_high - 3*fy_low | 2*fy_low - 3*fx_high | 2*fy_high - 3*fx_low |
+| IMD frequency limits (MHz) | 918 | 703 | 703 | 493 |
+| Two-tone 5th order IMD products | 2*fx_low + 3*fy_low | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low | 2*fy_high + 3*fx_high |
+| IMD frequency limits (MHz) | 3435 | 3650 | 3395 | 3605 |
+
+From the above table, it can be found that both n28 DL and n105 DL are subject to MSD due to dual-uplink IMD3 and IMD5 of 2UL CA n28-n105 configuration. Furthermore, the DTV channels below 608 MHz are also victims of the CA\_n28-n105 IMD3 and higher orders and thus the coexistence between UL CA\_n28-n105 and DTV channels may be compromised.
+
+#### 5.5.4.3 REFSSENS evaluation
+
+Based on the above IMD analysis, the IMD3 and IMD5 MSD test points in Table 5.5.4.2-1 were discussed. Some estimations of the IMD3 MSD ranged between 25 dB and 44dB depending on the performance of the filters and antenna coupling assumptions. Based on this large MSD and the potential coexistence issue with (US) DTV channels, it was agreed together with the band combination proponent, that 2UL configuration will not be supported. This agreement is captured in way forward [14].
+
+**Table 5.5.4.3-1 potential MSD test points due to IMD3 and IMD5 if 2UL configuration would be specified.**
+
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|-------------------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n28-n105 | n28 | 745.5 | 5 | 25 | 800.5 | 2UL not specified | FDD | IMD3 |
+| | n105 | 690.5 | 5 | 25 | 639.5 | N/A | FDD | N/A |
+| | n28 | 745.5 | 5 | 25 | 800.5 | N/A | FDD | IMD3 |
+| | n105 | 694.5 | 5 | 25 | 643.5 | 2UL not specified | FDD | N/A |
+| | n28 | 715 | 5 | 25 | 770 | 2UL not specified | FDD | IMD5 |
+| | n105 | 687.5 | 5 | 25 | 636.5 | N/A | FDD | N/A |
+| | n28 | 715.5 | 5 | 25 | 770.5 | N/A | FDD | IMD5 |
+| | n105 | 690 | 5 | 25 | 639 | 2UL not specified | FDD | N/A |
+
+## 5.6 CA\_n26-n28
+
+### 5.6.1 General
+
+In this configuration the uplink is also CA\_n26A-n28A, but there are two fall back options:
+
+DL\_n26A-n28A\_UL\_n28A\_BCS0 (already completed)
+
+UL\_n26A-n28A\_UL\_n26A\_BCS0
+
+The implementation of the band n28 of CA\_n26\_n28 has been discussed, and the pros and cons of the following two cases can be further traded-off, whether and/or how to do the down-selection in the future is for further study.
+
+Case 1: lower 30MHz of n28 (UL: 703~733MHz, DL: 758~788MHz) is supported.
+
+Case 2: entire n28 frequency range (UL: 703~748MHz, DL: 758~803MHz) is supported.
+
+
+
+Figure 5.6.1-1: CA\_n26-n28 frequency ranges. The diagram shows two cases for the frequency ranges of bands n28 and n26. Case 1 (top) shows n28AUL (703-733 MHz), n28ADL (758-788 MHz), n26UL (814-849 MHz), and n26DL (859-894 MHz). Case 2 (bottom) shows n28UL (703-748 MHz), n28DL (758-803 MHz), n26UL (814-849 MHz), and n26DL (859-894 MHz). Both cases show a total bandwidth of 191 MHz.
+
+Figure 5.6.1-1 CA\_n26-n28 frequency ranges
+
+Besides, as a reference for further study, proponent operator provided some related information about the allocated spectrum in the 700MHz and extended 850 MHz bands as sketched in the following figure and table.
+
+
+
+| Band 28 / 700MHz | | | | | | | | | | | | | | | | | | | | |
+|------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|
+| | UL | | | | | | | | DL | | | | | | | | | | | |
+| | 703 | 708 | 713 | 718 | 723 | 728 | 733 | 738 | 743 | 748 | 758 | 763 | 768 | 773 | 778 | 783 | 788 | 793 | 798 | 803 |
+| Metro | | | | | | | | | | | | | | | | | | | | |
+| Regional | | | | | | | | | | | | | | | | | | | | |
+| Spectrum Share | | | | | | | | | | | | | | | | | | | | |
+
+
+
+| Band 26 / 850MHz | | | | | | | | | | | | | | | | | | | | |
+|------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|--|--|--|--|
+| | UL | | | | | | | | DL | | | | | | | | | | | |
+| | 814 | 819 | 824 | 829 | 834 | 839 | 844 | 849 | 859 | 864 | 869 | 874 | 879 | 884 | 889 | 894 | | | | |
+| Metro | | | | | | | | | | | | | | | | | | | | |
+| Regional | | | | | | | | | | | | | | | | | | | | |
+| Spectrum Share | | | | | | | | | | | | | | | | | | | | |
+
+Figure 5.6.1-2: n26 and n28 spectrum allocation. The figure contains two tables showing spectrum allocation for Band 28 (700MHz) and Band 26 (850MHz). The top table for Band 28 shows UL (703-748 MHz) and DL (758-803 MHz) bands. The bottom table for Band 26 shows UL (814-849 MHz) and DL (859-894 MHz) bands. Both tables have rows for Metro, Regional, and Spectrum Share, with blue blocks indicating allocated spectrum.
+
+Figure 5.6.1-2 n26 and n28 spectrum allocation
+
+Table 5.6.1-1 n26 and n28 spectrum allocation
+
+| | Uplink | Downlink |
+|--------------------|----------------------------------------|----------------------------------------|
+| n28 (national) | 713 MHz – 733 MHz | 768 MHz – 788 MHz |
+| n26 (Metropolitan) | 814 MHz – 824 MHz<br>835 MHz – 845 MHz | 859 MHz – 869 MHz<br>880 MHz – 890 MHz |
+| n26 (Regional) | 814 MHz – 824 MHz<br>830 MHz – 845 MHz | 859 MHz – 869 MHz<br>875 MHz – 890 MHz |
+
+### 5.6.2 UE RF architecture assumption
+
+The potential UE RF architectures for CA\_n26A-n28A case 1 and case 2 can be considered as shown below. Baseline architecture for UE RF requirements development will be further discussed. As the performance of band n26 is similar to band n28, after the development of CA\_n5-n28, some architectures could be used as a reference to CA\_n26-n28.
+
+#### 5.6.2.1 UE RF architecture with lower 30MHz of n28 supporting
+
+Architecture of case 1 (lower 30MHz of n28 (UL: 703~733MHz, DL: 758~788MHz) is supported) is listed as below. Entire n28 presents a greater challenge to filter implementation, so further research on feasibility and applicable filtering techniques should be considered.
+
+The topology for architecture 1 with 2 antenna, as shown in Figure 5.6.2.1-1:
+
+- 1) antenna 1 with quadruplexer supporting n26DL+n26UL+n28AUL+n28ADL
+- 2) antenna 2 with duplexer supporting n26DL+n28ADL
+
+The topology for architecture 2 with 2 antenna, as shown in Figure 5.6.2.1-2:
+
+- 1) antenna 1 with triplexer supporting n26DL+n28AUL+n28ADL
+- 2) antenna 2 with triplexer supporting n26DL+n26UL+n28ADL
+
+The topology for architecture 3 with 3 antenna, as shown in Figure 5.6.2.1-3:
+
+- 1) antenna 1 with duplexer supporting n28AUL+n28ADL
+- 2) antenna 2 with duplexer supporting n26UL+n26DL
+- 3) antenna 3 with duplexer supporting n26DL+n28ADL
+
+
+
+Figure 5.6.2.1-1: Architecture 1: Quadruplexer solution for CA\_n26-n28 with two antennas. The diagram shows two antenna paths. The 'Main TRx' path on the left connects to a quadruplexer (represented by a box with four ports). Below the quadruplexer are two 'sPnT' (switch/pole) blocks. The left 'sPnT' block connects to a series of four filters, which are then connected to four antennas labeled 'n26', 'n26', 'n28A', and 'n28A'. The right 'sPnT' block connects to a single antenna. The 'Diversity TRx' path on the right connects to a duplexer (represented by a box with two ports). Below the duplexer are two 'sPnT' blocks. The left 'sPnT' block connects to a series of two filters, which are then connected to two antennas labeled 'n26' and 'n28A'. The right 'sPnT' block connects to a single antenna.
+
+Figure 5.6.2.1-1 Architecture 1: Quadruplexer solution for CA\_n26-n28 with two antennas
+
+
+
+Figure 5.6.2.1-2: Architecture 2: Triplexer solution for CA\_n26-n28 with two antennas. The diagram shows two transceivers, 'Main TRx' and 'Diversity TRx', each connected to a triplexer. Each triplexer is connected to two 'sPnT' (single-pole, double-throw) switches. Each 'sPnT' switch is connected to a duplexer. Each duplexer is connected to two antennas. The 'Main TRx' side has antennas labeled n26, n28A, and n28A. The 'Diversity TRx' side has antennas labeled n26, n26, and n28A.
+
+Figure 5.6.2.1-2 Architecture 2: Triplexer solution for CA\_n26-n28 with two antennas
+
+
+
+Figure 5.6.2.1-3: Architecture 3: Three-antenna solution for CA\_n26-n28. The diagram shows three transceivers: 'Main TRx 1', 'Main TRx 2', and 'Diversity TRx'. Each is connected to a triplexer, which is connected to two 'sPnT' switches, which are connected to duplexers, which are connected to antennas. 'Main TRx 1' has antennas labeled n28A and n28A. 'Main TRx 2' has antennas labeled n26 and n26. 'Diversity TRx' has antennas labeled n26 and n28A.
+
+Figure 5.6.2.1-3 Architecture 3: Three-antenna solution for CA\_n26-n28
+
+#### 5.6.2.2 UE RF architecture with entire n28 frequency range supporting
+
+Architecture of case 2 (entire n28 frequency range (UL: 703~748MHz, DL: 758~803MHz) is supported) is listed as below.
+
+The topology for architecture 4 with 2 antenna, as shown in Figure 5.6.2.2-1:
+
+- 1) antenna 1 with dual-quadruplexer supporting n26UL+ n26DL+ n28AUL+ n28ADL\_ n26UL+ n26DL+ n28BUL+ n28BDL
+- 2) antenna 2 with duplexer supporting n26DL+n28DL
+
+The topology for architecture 5 with 2 antenna, as shown in Figure 5.6.2.2-2:
+
+- 1) antenna 1 with dual-triplexer supporting n26DL+ n28AUL+n28ADL\_ n26DL+ n28BUL+n28BDL
+- 2) antenna 2 with triplexer supporting n26DL+n26UL+n28UL
+
+The topology for architecture 6 with 3 antenna, as shown in Figure 5.6.2.2-3:
+
+- 1) antenna 1 with dual-duplexer supporting n28AUL+n28ADL\_ n28BUL+n28BDL
+- 2) antenna 2 with duplexer supporting n26UL+n26DL
+- 3) antenna 3 with duplexer supporting n26DL+n28ADL
+
+
+
+Figure 5.6.2.2-1: Architecture 4: Dual-quadruplexer solution for CA\_n26-n28 with two antennas. The diagram shows a 'Main TRx' connected to two 'sPnT' blocks, which are then connected to two 'quadruplexer' blocks. Each quadruplexer is connected to two antennas labeled n26, n26, n28A, n28A and n26, n26, n28B, n28B. A 'Diversity TRx' is connected to two 'sPnT' blocks, which are then connected to two 'quadruplexer' blocks. Each quadruplexer is connected to two antennas labeled n26, n28.
+
+Figure 5.6.2.2-1 Architecture 4: Dual-quadruplexer solution for CA\_n26-n28 with two antennas
+
+
+
+Figure 5.6.2.2-2: Architecture 5: Dual-triplexer solution for CA\_n26-n28 with two antennas. The diagram shows a 'Main TRx' connected to two 'sPnT' blocks, which are then connected to two 'triplexer' blocks. Each triplexer is connected to three antennas labeled n26, n28A, n28A and n26, n28B, n28B. A 'Diversity TRx' is connected to two 'sPnT' blocks, which are then connected to two 'triplexer' blocks. Each triplexer is connected to three antennas labeled n26, n26, n28.
+
+Figure 5.6.2.2-2 Architecture 5: Dual-triplexer solution for CA\_n26-n28 with two antennas
+
+
+
+Figure 5.6.2.2-3: Architecture 6: Three-antenna solution for CA\_n26-n28. The diagram shows three transceivers: 'Main TRx 1', 'Main TRx 2', and 'Diversity TRx'. 'Main TRx 1' is connected to two 'sPnT' blocks, which are then connected to two 'quadruplexer' blocks. Each quadruplexer is connected to two antennas labeled n28A, n28A and n28B, n28B. 'Main TRx 2' is connected to two 'sPnT' blocks, which are then connected to two 'quadruplexer' blocks. Each quadruplexer is connected to two antennas labeled n26, n26. 'Diversity TRx' is connected to two 'sPnT' blocks, which are then connected to two 'quadruplexer' blocks. Each quadruplexer is connected to two antennas labeled n26, n28.
+
+Figure 5.6.2.2-3 Architecture 6: Three-antenna solution for CA\_n26-n28
+
+For architecture 4 with 2 antenna, there are some potential implementation challenges:
+
+- The main antenna should simultaneously cover the whole band from n28UL to n26DL with the length of 191MHz, the bandwidth ratio is as high as 23.9%, it would far exceed the bandwidth ratio for a typical planar antenna design in a smartphone, therefore the radiative performance for CA\_n26A-n28A is expected to be compromised.
+- The performance requirements of quadruplexer such as filter isolation and insertion loss are strict, posing challenge to the implementation and cost of the UE front-end, and the feasibility of two quadruplexers may need further study.
+
+For architecture 5 with 2 antenna, there are some advantages and potential implementation challenges:
+
+- A two-antenna architecture with three triplexers can be easier to design with proper delta T and delta R, so architecture 2 seems to be more feasible.
+
+- The difficulties of triplexer implementation still remain with two gaps of 10MHz, n26 BW of 35MHz and n28DL of 45MHz.
+
+For architecture 6 with 3 antenna, there are some advantages and potential implementation challenges:
+
+- For the 3-antenna architecture, there are two antennas on the main signal path, which eases the difficulty of multiplexer design and implement. The frequency range for each main antenna is narrower compared with 2-antenna architecture, and the antenna BW ratios of the two antennas would be close to the current devices.
+- 3 LB antennas present a greater challenge to the dimension of the mobile phone than 2-antenna architecture.
+
+### 5.6.3 Common for 1 band UL and 2 bands UL of CA\_n26-n28
+
+#### 5.6.3.1 Operating bands for CA
+
+**Table 5.6.3.1-1: CA band combination of band n26+n28**
+
+| NR Band | Uplink (UL) band | | Downlink (DL) band | | Duplex mode | |
+|---------|------------------------------|---|------------------------------|---------|-------------|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low} - F_{UL\_high}$ | | $F_{DL\_low} - F_{DL\_high}$ | | | |
+| n26 | 814 MHz | – | 849 MHz | 859 MHz | FDD | |
+| n28 | 703 MHz | – | 748 MHz | 758 MHz | FDD | |
+
+A note may be needed if case 1 is considered for CA\_n26-n28, e.g. band n28 is restricted at lower 30MHz (UL: 703~733MHz, DL: 758~788MHz).
+
+In addition, referring to the contribution [10], the following options about different frequency range restrictions are listed to trade-off the pros and cons. From a high level perspective, based on the proponent operator's feedback, one possibility is that RAN4 move forward with option 4 (i.e. both options 1 and 3 being captured in the specification) which would allow maximum implementation flexibility.
+
+Option 1 Keep current CA\_n26A-n28A with entire n28 frequency range and specify n26 UL and UL CA support for entire frequency range
+
+Option 2 Modify current CA\_n26A-n28A to include only lower 30MHz of n28 and specify n26 UL and UL CA support for lower 30MHz frequency range
+
+Option 3 Keep current CA\_n26A-n28A with entire n28 frequency range and specify n26 UL and UL CA support for lower 30MHz frequency range
+
+Option 4 Combination of options 1 and 3
+
+#### 5.6.3.2 Channel bandwidths per operating band for CA
+
+Referring to table 5.5A.3.1-1h of TS 38.101-1, DL\_n26A-n28A\_BCS0 and BCS1 has been specified
+
+#### 5.6.3.3 Identify the potential MSD issues due to harmonic/harmonic mixing/cross band isolation
+
+There is no need to specify harmonics and harmonics mixing exception for CA\_n26-n28 as we didn't specify them in current spec.
+
+For cross band isolation issue:
+
+Case 1: The 2<sup>nd</sup> adjacent channel leakage from band n26 may fall into band DL frequency range (774~788) when 20MHz UL CBW is assumed for band n26.
+
+Case 2: the 1<sup>st</sup> adjacent channel leakage from band n26 may fall into n28 DL frequency range (796~803) when 20MHz UL CBW is assumed for band n26.
+
+#### 5.6.3.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+Option 1 is proposed based on the agreed $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values for CA\_n5-n28 in WF [11] which can be reused for CA\_n26-n28.
+
+Option 2 is proposed in the contribution [10].
+
+**Table 5.6.3.4-1: $\Delta T_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] option 1 | $\Delta T_{IB,c}$ [dB] option 2 |
+|-----------------------------|---------|---------------------------------|---------------------------------|
+| CA_n26A-n28A | n26 | 0.7 | 0.5 |
+| | n28 | 0.7 | 0.5 |
+
+**Table 5.6.3.4-2: $\Delta R_{IB,c}$**
+
+| Inter-band CA Configuration | NR Band | $\Delta R_{IB,c}$ [dB] option 1 | $\Delta R_{IB,c}$ [dB] option 2 |
+|-----------------------------|---------|---------------------------------|---------------------------------|
+| CA_n26A-n28A | n26 | 0.2 | 0.3 |
+| | n28 | 0.2 | 0.3 |
+
+#### 5.6.3.5 REFSENS exception evaluation for one UL band
+
+1) Referring to the contribution [12], the following band n28A MSD evaluations, assuming 35dB and 45dB Tx filter rejection of band n26.
+
+**Table 5.6.3.5-1: band n28A MSD evaluations due to cross band isolation for CA\_n26-n28**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD (dB) | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|----------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | | |
+| n26 | n28A | 824 | 20 | 15 | 25 (RBstart=0) | 785.5 | 5 | 25.6 | ACLR2 |
+| n26 | n28A | 824 | 20 | 15 | 25 (RBstart=0) | 785.5 | 5 | 15.9 | ACLR2 |
+
+Referring to the contribution [12], we have the following band n28B MSD evaluations, assuming filter performance with set 1 and set 2 in Table 5.6.3.5-3.
+
+**Table 5.6.3.5-2: band n28B MSD evaluations due to cross band isolation for CA\_n26-n28**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD (dB) | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|--------------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | | |
+| n26 | n28B | 824 | 20 | 15 | 25 (RBstart=0) | 801.5 | 5 | 45.9 (Set 1) | ACLR1 |
+| n26 | n28B | 824 | 20 | 15 | 25 (RBstart=0) | 801.5 | 5 | 28.5 (Set 2) | ACLR1 |
+
+**Table 5.6.3.5-3: Filter performance assumption**
+
+| | Set 1 | Set 2 |
+|----------------------------------------|-------|-------|
+| n28B Rx filter rejection at 814~849MHz | 12 dB | 33 dB |
+| n26 Tx filter rejection at 773~803MHz | 35 dB | 45 dB |
+
+2) Referring to the contribution [13], the following analysis were provided.
+
+To evaluate the potential 1UL and 2UL for CA\_n26-n28 with band n28 full (n28F) or the lower 30MHz (n28A), it is useful to compare existing cases for CA\_n5-n28F and CA\_n18-n28F and CA\_n18-n28A. This can be done by observing the IMD landscape provided in Figure 5.6.3.5-1, and the related wanted UL RB allocation and its image IMDs overlaps for 5MHz and 30MHz n28DL for n28F or n28A scenarios that are collected in Table 5.6.3.5-4.
+
+In addition, 1UL cross band MSD for n28F and n28A were proposed in 1UL cross band MSD for n28F and n28A.
+
+
+
+Figure 5.6.3.5-1: IMD landscape of n5, n18, n26 and n28 for n28F and n28A cases. The diagram shows a frequency spectrum from 690 to 890 MHz. It illustrates various bandwidths (BW) for bands n28A, n28F, n26, n18, and n5. Key parameters like 'i' (interference), 'w' (wanted), and '3' (third order intermodulation) are marked. IMD products are shown for n28F (IMDs i, w, 3, 5, 7, 5/7, 3/5) and n28A (IMDs i, w, 3, 5, 7, 5/7, 3/5).
+
+Figure 5.6.3.5-1: IMD landscape of n5, n18, n26 and n28 for n28F and n28A cases.
+
+Table 5.6.3.5-4: Distance to n28 victim DL and IMD overlap for different UL and DL scenarios
+
+| Band | Max UL BW | #RB | Distance to (MHz) | | IMD overlap | | | |
+|------|-----------|-----|-------------------|------|-------------|-----------|------------|------------|
+| | | | n28A | n28F | n28A 5MHz | n28F 5MHz | n28A 30MHz | n28F 30MHz |
+| n26 | 20MHz | 25 | 26 | 11 | IMD5/7 | IMD3 | IMD5/7 | IMD3/5/7 |
+| n5 | 20MHz | 20 | 21 | 36 | IMD5/7 | IMD5 | IMD5/7 | IMD5/7 |
+| n18 | 15MHz | 25 | 17 | 12 | IMD5/7 | IMD3/5 | IMD5/7 | IMD3/5/7 |
+| n28A | 30MHz | 25 | 25 | na | na | na | IMD3/5 | na |
+| n28F | 30MHz | 25 | na | 10 | na | na | na | IMD3/5 |
+
+Table 5.6.3.5-5: 1UL cross band MSD for n28F and n28A
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|-------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | LCRB | (MHz) | (MHz) | (dB) | |
+| n26 | n28 | 822.5 | 20 | 15 | 25 (RBstart=0) | 800.5 | 5 | [>30] | ACLR1 |
+| n26 | n28 | 822.5 | 20 | 15 | 25 (RBstart=0) | 785.5 | 5 | [18] | ACLR2 |
+
+3) Referring to the contribution [10], the technical analysis for two cases (case 1: n28 Cross-band MSD for lower 30MHz of n28 / case 2: n28 Cross-band MSD for entire n28) are shown below.
+
+Table 5.6.3.5-6: Cross-band MSD for lower 30MHz of n28
+
+| n28 Cross-band MSD | PRX | DRX |
+|------------------------------|-------|-------|
+| BW | | 4.5 |
+| FE Loss | 4.0 | 4.0 |
+| Output Power | | 23 |
+| TX Noise per BW at PA Output | -41.3 | |
+| RX_IIP2, dBm | 54 | 54 |
+| Antenna Isolation | | 10 |
+| RX Isolation | -45 | -38 |
+| TX Isolation | -45 | -25 |
+| TX_IM2 | -92.0 | -80.0 |
+| Tx_noise | -82.3 | -85.3 |
+| TX_total | -81.8 | -78.9 |
+| Thermal noise | -94.5 | -94.5 |
+| Composite | -81.6 | -78.7 |
+| MRC REFSENS | | -81.5 |
+| n28 REFSENS | | -98.5 |
+| n28 MSD | | 17.0 |
+
+**Table 5.6.3.5-7: n28 Cross-band MSD for entire n28**
+
+| n28 Cross-band MSD | PRX | DRX |
+|------------------------------|-------|-------|
+| BW | | 4.5 |
+| FE Loss | 4.0 | 4.0 |
+| Output Power | | 23 |
+| TX Noise per BW at PA Output | -21.0 | |
+| RX_IIP2, dBm | 54 | 54 |
+| Antenna Isolation | | 10 |
+| RX Isolation | -45 | -38 |
+| TX Isolation | -45 | -25 |
+| TX_IM2 | -92.0 | -80.0 |
+| Tx_noise | -62.0 | -65.0 |
+| TX_total | -62.0 | -64.9 |
+| Thermal noise | -94.5 | -94.5 |
+| Composite | -62.0 | -64.9 |
+| MRC REFESENS | | -64.8 |
+| n28 REFESENS | | -98.5 |
+| n28 MSD | | 33.7 |
+
+It's observed that MSD is about 15-20dB higher if the entire n28 must be supported, compared to case when only lower 30MHz of n28 is supported.
+
+**Table 5.6.3.5-8: n28 Cross-band MSD test point for lower 30MHz of n28 and entire n28**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 785.5 | 5 | 17.0 | ACLR2 |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 800.5 | 5 | 33.7 | ACLR |
+
+4) Referring to the contribution [17], the following analysis were provided.
+
+The combo is a L-L band combination with small gap between uplink range of n26 and downlink range of n28. The maximum uplink bandwidth of n26 is up to 20MHz that its ACP1 would fall into DL range of n28 directly if uplink is allocated full RB. Below table lists our assumption for MSD characterization. Here we consider three-antenna implementation since the frequency gap between n26 uplink and n28 downlink is only 11MHz that we don't think a low band diplexer is feasible with existing technology. Based on previous RAN4 agreement, there shall not be frequency range constraint on n28 thus MSD shall be characterized with full frequency range.
+
+**Table 5.6.3.5-9 Receiver performance parameters for MSD analysis**
+
+| Parameter | Value | Unit |
+|--------------------------------------|--------|--------|
+| Antenna isolation | 10 | dB |
+| n28 filter rejection at n26 UL range | 15 | dB |
+| n26 ACP1 | -30 | dBc |
+| n26 CIM3 | -60 | dBc |
+| Front-end loss | 4 | dB |
+| PCB isolation | 67 | dB |
+| PA RXBN noise | -115 | dBm/Hz |
+| Thermal noise at n28 RX ANT port | -165.5 | dBm/Hz |
+| Transceiver effective phase noise | -144 | dBc/Hz |
+| SNR requirement for QPSK | -1 | dB |
+
+With above parameters, we calculate MSD due to cross band isolation as below:
+
+**Table 5.6.3.5-10 Link analysis for Band 28 5MHz REFSSENS calculation at fc = 800.5 MHz**
+
+| Direct Signal Path | | | |
+|------------------------------------------------|--------|-----------|----------|
+| Parameter | Main | Diversity | |
+| n26 TX power at antenna port (Primary path) | 23 | 23 | dBm |
+| n26PA output noise power at n28 LNA input port | -71.3 | -71.3 | dBm/5MHz |
+| n28 LNA IM2 due to n26 uplink | -53 | -53 | dBm/5MHz |
+| Thermal noise at RX ant port | -162.5 | | dBm/Hz |
+| CIM3 noise at n28 LNA input port | -55.8 | -55.8 | dBm |
+| Total noise level refer to B28 LNA input port | -51.1 | -51.1 | |
+| Combined | | | |
+| MSD (5MHz BW) | | 47.4 | dB |
+
+**Table 5.6.3.5-11: band n28B MSD evaluations due to cross band isolation for CA\_n26-n28**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n26 | n28B | 824 | 20 | 15 | 25 (RBstart=0) | 800.5 | 5 | 47.4 | ACLR1 |
+
+5) Referring to the contribution [18], new evaluation based on measurements were provided compared to [13] which was based on extrapolated from similar combination:
+
+- 20MHz band n26 output noise in n28A (first 30MHz of band n28) and n28B (last 30MHz of band n28) for:
+ - 5, 20, 25 and 30MHz band n28 CBW
+ - At 23dBm for 1UL and 20dBm for 2UL
+- Band n28 self-desense for 5, 20, 25 and 30MHz band n28 CBW at 23dBm for 1UL and 20dBm for 2UL.
+
+Based on the chosen architecture, the following RF front-end performance is assumed:
+
+- Post PA and pre LNA losses = 4dB
+- Antenna isolation 10dB
+- Band n26 UL filter from n26UL/n26DL/n28DL triplexer performance:
+ - n26 UL to n28A DL T/R isolation = 38dB
+ - n26UL to n28A DL antenna rejection = 35dB
+ - n26 UL to n28A DL T/R isolation = 35dB (11MHz distance)
+
+- n26UL to n28A DL antenna rejection = 32dB (11MHz distance)
+- These performances are justified by the fact that band n26 is one of the most critical low band duplexers (35MHz BW with 10MHz duplexer gap)
+- Band n28 UL filter from n28AorBUL/n26DL/n28AorBDL triplexer performance
+- n28 UL to n26 DL T/R isolation = 40dB
+- n28 UL to n26 DL antenna rejection = 38dB
+
+These performances are justified for a full band n28 design and the proximity of band n26.
+
+For CA\_n26-n28, the 1UL scenario is using the largest n28 and n26 UL CBW (respectively 30MHz and 20MHz) closest to the victim band with a 5MHz Rx CBW. Still, in previous meetings, there was discussion regarding whether the 30MHz lower band n28 or the full band n28 should be considered, for this we evaluated n28A and n28B (representative of full band) cases:
+
+- n28B (upper 30MHz) is victim of IMD3 of band n26 UL wanted RBs and their image including its peak
+- n28A (lower 30MHz) is victim of IMD5 of band n26 UL wanted RBs and their image including its peak
+- n26 is victim of n28B IMD9 and n28A IMD11, at these high IMD offsets, the noise is dominated by the wideband transmitter white noise floor.
+
+We performed measurements for both sub-band n28A and n28B cases and the MSD after MRC results are summarized in Table 3.
+
+**Table 5.6.3.5-12: Post MRC MSD calculations based on measured transmitter noise.**
+
+| UL/BW/IM-DL | | n26/20/5-n28A | | n26/20/3-n28B | | n28AB/30/9-n26 | |
+|----------------------------------------------|-----------|---------------|-------|---------------|-------|----------------|--------|
+| CBW/NRB | [MHz]/# | 5 | 25 | 5 | 25 | 5 | 25 |
+| Meas Tx noise / transmitter noise floor | [dBm/CBW] | -43.1 | -63.5 | -23.3 | -63.5 | -85.0 | -63.5 |
+| REFSENS | [dBm/CBW] | -98.5 | | -98.5 | | -97.5 | |
+| RX noise floor wo Tx noise : Main/Div | [dBm/CBW] | -94.5 | -94.5 | -94.5 | -94.5 | -93.5 | -93.5 |
+| Tx-Rx / Tx-Ant duplexer isolation/rejection | [dB] | 38 | 35 | 35 | 32 | 37 | 34 |
+| LNA to antenna insertion loss | [dB] | 4 | | 4 | | 4 | |
+| Antenna isolation | [dB] | 0 | 10 | 0 | 10 | 0 | 10 |
+| PC3 1Tx interference levels: Main/Div | [dBm/CBW] | -77.1 | -84.1 | -54.3 | -61.3 | -96.4 | -103.4 |
+| Noise degradation due to Tx noise : Main/Div | [dB] | 17.5 | 10.8 | 40.2 | 33.2 | 1.8 | 0.4 |
+| REFSENS degradation after MRC | cor [dB] | 15.3 | | 37.8 | | 1.7 | |
+
+##### Observations:
+
+- With only the transmitter noise floor contributing, the band n26 MSD due to band n28 is small
+- The MSD of band n28B victim of band n26 UL IMD3 is confirmed to be significantly above 30dB
+- The MSD of band n28A victim of band n26 UL IMD5 is slightly lower than estimated in [2].
+
+These observations lead to the following 1UL cross band isolation MSD proposals, which provides MSD for full band and lower 30MHz of band n28 as spectrum availability varies in different regions.
+
+**Table 5.6.3.5-13: 1UL cross band MSD for CA\_n26-n28 accounting for both full band and lower 30MHz only of band n28.**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | LCRB | (MHz) | (MHz) | (dB) | |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 800.5 | 5 | 37.8 | ACLR1 |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 785.5 | 5 | 15.3 | ACLR2 |
+| n28 | n26 | 733 | 30 | 15 | 25 (RBstart=135) | 861.5 | 5 | 1.7 | >ACLR2 |
+
+6) Referring to the contribution [19], new evaluation for one uplink is provided:
+
+During the study phase for the CA\_n26-n28 band combination, there was no agreement on whether to consider only the lower 30MHz section of n28 or the entire band, as captured in the following WF:
+
+- Case 1: lower 30MHz of n28 (UL: 703~733MHz, DL: 758~788MHz) is supported.
+- Case 2: entire n28 frequency range (UL: 703~748MHz, DL: 758~803MHz) is supported.
+
+As a consequence of this, we will do the MSD analysis and access the $\Delta TIB,c$ and $\Delta RIB,c$ for both cases. The corresponding aggregated spectrums are shown in Figures 2.3-1 and 2.3-2 below:
+
+
+
+Figure 5.6.3.5-2: Aggregated spectrum allocation for the CA\_n26-n28 combination (full n28 band). The diagram shows four contiguous blocks: n28 UL (703-748 MHz), n28 DL (758-803 MHz), n26 UL (814-849 MHz), and n26 DL (859-894 MHz). A double-headed arrow below indicates a total aggregated bandwidth of 191 MHz.
+
+**Figure 5.6.3.5-2: Aggregated spectrum allocation for the CA\_n26-n28 combination (full n28 band)**
+
+
+
+Figure 5.6.3.5-3: Aggregated spectrum allocation for the CA\_n26-n28 combination (lower 30MHz of n28 band). The diagram shows four contiguous blocks: n28 UL (703-733 MHz), n28 DL (758-788 MHz), n26 UL (814-849 MHz), and n26 DL (859-894 MHz). A double-headed arrow below indicates a total aggregated bandwidth of 191 MHz.
+
+**Figure 5.6.3.5-3: Aggregated spectrum allocation for the CA\_n26-n28 combination (lower 30MHz of n28 band)**
+
+The two-antenna architecture is captured in the following figure.
+
+
+
+```
+
+graph TD
+ subgraph Main_Antenna_Path
+ ANT1[Main ANT] --> T1[Triplexer]
+ T1 --> sPnT1[sPnT]
+ T1 --> sPnT2[sPnT]
+ sPnT1 --> F1[n26 Filter]
+ sPnT1 --> F2[n28A Filter]
+ sPnT1 --> F3[n28A Filter]
+ sPnT2 --> F4[n26 Filter]
+ sPnT2 --> F5[n28B Filter]
+ sPnT2 --> F6[n28B Filter]
+ end
+ subgraph Diversity_Antenna_Path
+ ANT2[Diversity ANT] --> T2[Triplexer]
+ T2 --> sPnT3[sPnT]
+ T2 --> sPnT4[sPnT]
+ sPnT3 --> F7[n26 Filter]
+ sPnT3 --> F8[n26 Filter]
+ sPnT3 --> F9[n28 Filter]
+ sPnT4 --> F10[sPnT]
+ end
+
+```
+
+Figure 5.6.3.5-4: CA\_n26-n28 RF front-end architecture based on 2 antennas and 2 triplexers. The diagram shows two antennas, 'Main ANT' and 'Diversity ANT', each connected to a triplexer. Each triplexer is connected to two 'sPnT' (switch/pole) units. Each 'sPnT' unit is connected to three bandpass filters. The filters are labeled with carrier frequencies: n26, n28A, n28A, n26, n28B, n28B, n26, n26, and n28. The architecture is designed to support carrier aggregation between n26 and n28 bands.
+
+Figure 5.6.3.5-4: CA\_n26-n28 RF front-end architecture based on 2 antennas and 2 triplexers
+
+##### CA\_n26-n28 MSD Analysis
+
+As can be seen from the MSD contributor table below, for n28 UL → n26 DL, there is more than 110MHz of spectrum gap. Therefore, the cross-band interference for that case will be minimum and so the MSD for n26 DL will be small. However, for the n26 UL → n28 DL, there is only 11MHz of separation when the n28 full 45MHz band is considered and 26MHz when the lower 30MHz of n28 (n28A) is assumed. Due to that small frequency separation, there is a strong cross-band interference that will affect the n28 DL. Next, we will examine the n28 DL MSD for both cases.
+
+Table 5.6.3.5-14: CA\_n26-n28 MSD cross-band interference sources
+
+| Interference Source | 1 Uplink (n26UL or n28UL) | 2 Uplinks (n26UL+n28UL) |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| Harmonic/harmonic mixing | No issue | No issue |
+| Intermodulation | No issue | No significant issue |
+| Cross-band isolation | <p><b>Option # 1: Entire n28 band</b></p> <p>Image: Frequency diagram for Option #1. Top row: n28 UL (703-748 MHz) and n26 DL (859-904 MHz) with a 111MHz gap. Bottom row: n28 DL (758-803 MHz) and n26 UL (814-859 MHz) with an 11MHz gap.</p> <p>Significant ACLR1 and cross band noise issue for n26UL → n28DL case</p> <p>Potential TX noise leakage issue</p><br><p><b>Option # 2: Lower 30MHz of 28 band</b></p> <p>Image: Frequency diagram for Option #2. Top row: n28 UL (703-733 MHz) and n26 DL (859-904 MHz) with a 126MHz gap. Bottom row: n28 DL (758-788 MHz) and n26 UL (814-859 MHz) with a 26MHz gap.</p> <p>Significant ACLR2 and cross band noise issue for n26UL → n28DL case</p> | |
+
+| | | |
+|--|----------------------------------|--|
+| | Potential TX noise leakage issue | |
+|--|----------------------------------|--|
+
+For the n28 DL MSD analysis, we will use the following worst-case assumptions for the RF front-end performance parameters:
+
+- n26 Tx filter rejection at n28 RX (758MHz-803MHz): 30dB
+- Cross-band TX to RX isolation: 40dB
+- ACLR2 sideband level: 30dBc
+- ACLR3 sideband level: 30dBc
+- Front-end insertion loss: 4.5dB
+- Antenna coupling: 10dB
+- RxBW: 4.5MHz
+- Output Power at antenna: 23dBm
+
+Given the assumptions above, the MSD analysis is summarized in the table below.
+
+**Table 5.6.3.5-15: CA\_n26-n28 MSD analysis**
+
+| MSD Source | Parameter | Unit | n26 Tx → n28 RX Case 1<br>(Full 45MHz BW) | | n26 Tx → n28 RX Case 2<br>(Lower 30MHz BW only) | |
+|-----------------|--------------------------------------------------|-----------|-------------------------------------------|-----------------|-------------------------------------------------|---------------|
+| | | | n28 main path | n28 div. path | n28 main path | n28 div. path |
+| PA noise + ACLR | TX noise leakage at PA output due to ACLR2 (PC3) | dBm/RxBW | -14 | | -39.5 | |
+| | Total PA noise @ ANT | dBm/RxBW | <b>-48.5</b> | <b>-58.5</b> | <b>-79</b> | <b>-89</b> |
+| IIP2 effects | Typical Rx IIP2 | dBm | 54 | 54 | 54 | 54 |
+| | TX IM2 noise level @ ANT | dBm | <b>-98</b> | <b>-108</b> | <b>-98</b> | <b>-108</b> |
+| Thermal Noise | 3GPP REFSSENS | dBm | -98.5 | -98.5 | -98.5 | -98.5 |
+| | SNR | dB | -1 | -1 | -1 | -1 |
+| | Thermal noise | dBm | <b>-97.5</b> | <b>-97.5</b> | <b>-97.5</b> | <b>-97.5</b> |
+| Composite | Composite noise | dBm | -48.5 | -58.5 | -78.9 | -88.3 |
+| | Composite noise after MRC | dBm | | <b>-65.7</b> | | <b>-88.7</b> |
+| <b>MSD</b> | | <b>dB</b> | | <b>>31.0</b> | | <b>8.7</b> |
+
+##### CA\_n26-n28 ΔTIB,c and ΔRIB,c Values
+
+For CA\_n26-n28, we can reuse the values already derived for the CA\_n5-n28 as proposed in [10].
+
+**Table 5.6.3.5-16: ΔTIB,c for CA\_n26-n28**
+
+| Inter-band CA Configuration | NR Band | ΔT <sub>IB,c</sub> [dB] |
+|-----------------------------|---------|-------------------------|
+| CA_n26-n28 | n26 | 0.7 |
+| | n28 | 0.7 |
+
+**Table 5.6.3.5-17: ΔRIB,c for CA\_n26-n28**
+
+| Inter-band CA Configuration | NR Band | RIB <sub>c</sub> [dB] |
+|-----------------------------|---------|-----------------------|
+| CA_n26-n28 | n26 | 0.2 |
+| | n28 | 0.2 |
+
+7) Referring to the contribution [20], new evaluation for one uplink is provided:
+
+We did further MSD analyses, resulting in slightly different MSD numbers.
+
+Conventional 3GPP assumptions for the TX for the PA noise measurements were used, as well as in factoring the CIM3/CIM5 contributions:
+
+- 20 MHz 100RB DFT-s-OFDM
+- 30dBc ACLR
+- 4dB Post-PA loss
+- Image -28dB
+- LO -28dBc
+- CIM3 -60dBc
+- CIM5 -70dBc
+
+| <b>n28 Cross-band MSD</b> | <b>PRX</b> | <b>DRX</b> |
+|------------------------------|------------|------------|
+| BW | 4.5 | |
+| FE Loss | 4.0 | 4.0 |
+| Output Power | 23 | |
+| TX Noise per BW at PA Output | -38.2 | |
+| RX_IIP2, dBm | 54 | 54 |
+| Antenna Isolation | 10 | |
+| RX Isolation | -45 | -38 |
+| TX Isolation | -45 | -30 |
+| TX_IM2 | -92.0 | -90.0 |
+| Tx_noise | -79.2 | -82.2 |
+| TX_total | -79.0 | -81.5 |
+| Thermal noise | -94.5 | -94.5 |
+| Composite | -78.8 | -81.3 |
+| | | |
+| MRC RESENS | -81.4 | |
+| | | |
+| n28 RESENS | -98.5 | |
+| | | |
+| n28 MSD | 17.1 | |
+
+Figure 5.6.3.5-5 n28 Cross-band MSD for lower 30MHz of n28
+
+| <b>n28 Cross-band MSD</b> | <b>PRX</b> | <b>DRX</b> |
+|------------------------------|------------|------------|
+| BW | | 4.5 |
+| FE Loss | 4.0 | 4.0 |
+| Output Power | | 23 |
+| TX Noise per BW at PA Output | -23.3 | |
+| RX_IIP2, dBm | 54 | 54 |
+| Antenna Isolation | | 10 |
+| RX Isolation | -45 | -38 |
+| TX Isolation | -45 | -30 |
+| TX_IM2 | -92.0 | -90.0 |
+| Tx_noise | -64.3 | -67.3 |
+| TX_total | -64.3 | -67.3 |
+| Thermal noise | -94.5 | -94.5 |
+| Composite | -64.3 | -67.3 |
+| | | |
+| MRC RESENS | | -67.1 |
+| | | |
+| n28 RESENS | | -98.5 |
+| | | |
+| n28 MSD | | 31.4 |
+
+Figure 5.6.3.5-5 n28 Cross-band MSD for entire n28
+
+Table 5.6.3.5-17 MSD test points when deciding the specifications for CA\_n26A-n28A
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 785.5 | 5 | 17.1 | ACLR2 |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 800.5 | 5 | 31.4 | ACLR |
+
+### 5.6.4 Specific for 2 bands UL of CA\_n26-n28
+
+#### 5.6.4.1 Maximum output power for inter-band CA
+
+Power class 3 is assumed for UL CA\_n26-n28
+
+#### 5.6.4.2 UE co-existence studies
+
+Table 5.6.4.2-1 lists Band n26 + Band n28 2UL bands CA 2<sup>nd</sup>, 3<sup>rd</sup>, 4<sup>th</sup> and 5<sup>th</sup> order IMD for the UE-to-UE coexistence analysis.
+
+Table 5.6.4.2-1: Band n26 and Band n28 UL IMD products
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------|-----------------------|----------------------|-----------------------|
+| UL frequency (MHz) | 814 | 849 | 703 | 748 |
+| 2 <sup>nd</sup> order IMD products | fy_low – fx_high | fy_high – fx_low | fy_low + fx_low | fy_high + fx_high |
+| IMD frequency limits (MHz) | 146 | 66 | 1517 | 1597 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low – fy_high | 2*fx_high – fy_low | 2*fy_low – fx_high | 2*fy_high – fx_low |
+| IMD frequency limits (MHz) | 880 | 995 | 557 | 682 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high |
+| IMD frequency limits (MHz) | 2331 | 2446 | 2220 | 2345 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low – 1*fy_high | 3*fx_high – 1*fy_low | 3*fy_low – 1*fx_high | 3*fy_high – 1*fx_low |
+| IMD frequency limits (MHz) | 1694 | 1844 | 1260 | 1430 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low + 1*fy_low | 3*fx_high + 1*fy_high | 3*fy_low + 1*fx_low | 3*fy_high + 1*fx_high |
+| IMD frequency limits (MHz) | 3145 | 3295 | 2923 | 3093 |
+| Two-tone 4 <sup>th</sup> order IMD products | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low | 2*fx_low + 2*fy_low | 2*fx_high + 2*fy_high |
+| IMD frequency limits (MHz) | 132 | 292 | 3034 | 3194 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low – 4*fy_high | fx_high – 4*fy_low | fy_low – 4*fx_high | fy_high – 4*fx_low |
+| IMD frequency limits (MHz) | 2178 | 1963 | 2693 | 2508 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low |
+| IMD frequency limits (MHz) | 616 | 411 | 1141 | 946 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low + 4*fy_low | fx_high + 4*fy_high | fy_low + 4*fx_low | fy_high + 4*fx_high |
+| IMD frequency limits (MHz) | 3626 | 3841 | 3959 | 4144 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low + 3*fy_low | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low | 2*fy_high + 3*fx_high |
+| IMD frequency limits (MHz) | 3737 | 3942 | 3848 | 4043 |
+
+3rd order IMD may also fall into Rx frequencies of bands n26 when both Band n26 and Band n28 transmit the UL signals.
+
+Table 5.6.4.2-2: Protected bands for the 2UL bands CA configuration
+
+| NR CA Configuration | Spurious emission | | | | | | |
+|---------------------|----------------------------------------------------------------------------|-----------------------|---|----------------------|---------------------|-----------|-----------|
+| | Protected band | Frequency range (MHz) | | | Maximum Level (dBm) | MBW (MHz) | NOTE |
+| CA_n26-n28 | E-UTRA Band 2, 3, 5, 18, 19, 25, 26, 31, 34, 40, 73<br>NR Band n79 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | | |
+| | E-UTRA Band 4, 41, 42, 43, 50, 51, 52, 65, 66, 74<br>NR Band n77, n78, n79 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 2 |
+| | E-UTRA Band 1 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 2, 11, 15 |
+| | E-UTRA Band 11, 21 | F <sub>DL_low</sub> | - | F <sub>DL_high</sub> | -50 | 1 | 2, 11, 12 |
+| | Frequency range | 1884.5 | - | 1915.7 | -41 | 0.3 | 3, 11 |
+| | Frequency range | 470 | - | 694 | -42 | 8 | 4, 14 |
+| | Frequency range | 470 | - | 710 | -26.2 | 6 | 13 |
+| | Frequency range | 662 | - | 694 | -26.2 | 6 | 4 |
+| | Frequency range | 758 | - | 773 | -32 | 1 | 4 |
+| | Frequency range | 773 | - | 799 | -50 | 1 | |
+| | Frequency range | 799 | - | 803 | -40 | 1 | 4 |
+| | Frequency range | 945 | - | 960 | -50 | 1 | |
+
+NOTE 2: As exceptions, measurements with a level up to the applicable requirements defined in Table 6.5.3.1-2 are permitted for each assigned NR carrier used in the measurement due to 2nd, 3rd, 4th or 5th harmonic spurious emissions. Due to spreading of the harmonic emission the exception is also allowed for the first 1 MHz frequency range immediately outside the harmonic emission on both sides of the harmonic emission. This results in an overall exception interval centred at the harmonic emission of $(2 \text{ MHz} + N \times L_{\text{CRB}} \times 180 \text{ kHz})$ , where N is 2, 3, 4, 5 for the 2nd, 3rd, 4th or 5th harmonic respectively. The exception is allowed if the measurement bandwidth (MBW) totally or partially overlaps the overall exception interval.
+
+NOTE 3: Applicable when co-existence with PHS system operating in 1884.5 -1915.7 MHz
+
+NOTE 4: These requirements also apply for the frequency ranges that are less than F<sub>oob</sub> (MHz) in Table 6.5.3.1-1 from the edge of the channel bandwidth.
+
+NOTE 11: Applicable when the assigned NR carrier is confined within 718 MHz and 748 MHz and when the channel bandwidth used is 5 or 10 MHz.
+
+NOTE 12: As exceptions, measurements with a level up to the applicable requirement of -38 dBm/MHz is permitted for each assigned NR carrier used in the measurement due to 2nd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.3.1-1) for which the 2nd harmonic totally or partially overlaps the measurement bandwidth (MBW).
+
+NOTE 13: This requirement is applicable for 5 and 10 MHz NR channel bandwidth allocated within 718 - 728 MHz. For carriers of 10 MHz bandwidth, this requirement applies for an uplink transmission bandwidth less than or equal to 30 RB with $\text{RBstart} > 1$ and $\text{RBstart} < 48$ .
+
+NOTE 14: This requirement is applicable in the case of a 10 MHz NR carrier confined within 703 MHz and 733 MHz, otherwise the requirement of -25 dBm with a measurement bandwidth of 8 MHz applies.
+
+NOTE 15: As exceptions, measurements with a level up to the applicable requirement of -36 dBm/MHz is permitted for each assigned E-UTRA carrier used in the measurement due to 3rd harmonic spurious emissions. An exception is allowed if there is at least one individual RB within the transmission bandwidth (see Figure 5.6-1) for which the 3rd harmonic totally or partially overlaps the measurement bandwidth (MBW).
+
+#### 5.6.4.3 REFSSENS exception evaluation for two UL band
+
+##### 1) MSD due to IMD
+
+If the following test frequency range was assumed, we can calculate the frequency range which is hit by IMD3 from UL CA\_n26-n28 as 880~895 MHz. It can be observed the IMD3 missed the DL channel of band n26 by 5MHz.
+
+n26: UL 814~819 DL 859~864
+
+n28: UL 743~748 DL 798~803
+
+IMD3 range is 880~895 MHz
+
+That means there is no direct test frequency point which can be found for IMD3 MSD definition.
+
+##### 2) MSD due to two UL cross band isolation
+
+Even if the performance of duplexer/filter's isolation can be guaranteed by one UL cross band isolation MSD, two PA linearity performance should be guaranteed simultaneously by two UL cross band isolation MSD requirements especially for the case that two 1<sup>st</sup> / 2<sup>nd</sup> adjacent channel interferences from two different UL aggressor bands hit the DL part of victim band. The following test points were proposed in contribution R4-2307477 for further discussion.
+
+**Table 5.6.4.3-1: 2UL cross band MSD for n28F and n28A**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | LCRB | (MHz) | (MHz) | (dB) | |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 788 | 30 | [>6] | ACLR1 from n26 UL band and |
+| n28 | | 733 | 30 | 15 | 25 (RBstart=135) | | | | ACLR1+ACLR2 from n28 UL band |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 773 | 30 | [3] | ACLR2 from n26 UL band and |
+| n28 | | 718 | 30 | 15 | 25 (RBstart=135) | | | | ACLR1+ACLR2 from n28 UL band |
+
+New evaluation based on measurement in [16] is also provided as below:
+
+Since CA\_n26-n28 UL configuration is also considered and, similar to the work performed for CA\_n5-n28, the MSD due to the addition of the band n28 UL and band n26 UL noises must be evaluated. For this, we measured the noise levels at 20dBm for the band n26UL for 20/25/30MHz CBW of band n28 and again looking at the lower or upper 30MHz.
+
+This time we had to measure the transmitter noise, evaluate the corresponding noise leaking to the receiver for each UL accounting for the front-end performance and assuming 3dB lower noise floor at 20dBm than 23dBm.
+
+This resulted in the interference levels at the receiver in:
+
+- Table 5.6.4.3-2 for 20dBm band n26 UL in band n28A which correspond to an IMD5 case (ACLR2)
+- Table 5.6.4.3-3 for 20dBm band n26 UL in band n28B which correspond to an IMD3 case (ACLR1)
+- Table 5.6.4.3-4 for the 20dBm band n28 UL self desense. It corresponds to an IMD5 case for 20 and 25MHz CBW and IMD3 case for 30MHz CBW.
+
+**Table 5.6.4.3-2: 20dBm band n26 UL noise in band n28A for 20/25/30MHz CBW.**
+
+| UL/BW/IM-DL | | n26/20/5-n28A | | n26/20/5-n28A | | n26/20/5-n28A | |
+|---------------------------------------------|-----------|---------------|-------|---------------|-------|---------------|-------|
+| CBW/NRB | [MHz]/# | 20 | 106 | 25 | 133 | 30 | 160 |
+| Meas Tx noise / transmitter noise floor | [dBm/CBW] | -48.3 | -60.2 | -46.5 | -59.2 | -45.7 | -58.4 |
+| Tx-Rx / Tx-Ant duplexer isolation/rejection | [dB] | 38 | 35 | 38 | 35 | 38 | 35 |
+| LNA to antenna insertion loss | [dB] | 4 | | 4 | | 4 | |
+| Antenna isolation | [dB] | 0 | 10 | 0 | 10 | 0 | 10 |
+| PC3 1Tx interference levels: Main/Div | [dBm/CBW] | -81.1 | -88.1 | -80.3 | -87.3 | -79.5 | -86.5 |
+
+**Table 5.6.4.3-3: 20dBm band n26 UL noise in band n28B for 20/25/20MHz CBW.**
+
+| UL/BW/IM-DL | | n26/20/3-n28B | | n26/20/3-n28B | | n26/20/3-n28B | |
+|----------------------------------------------------|-----------|---------------|-------|---------------|-------|---------------|-------|
+| CBW/NRB | [MHz]/# | 20 | 106 | 25 | 133 | 30 | 160 |
+| <b>Meas Tx noise / transmitter noise floor</b> | [dBm/CBW] | <b>-33.4</b> | -60.2 | <b>-28.8</b> | -59.2 | <b>-28.2</b> | -58.4 |
+| <b>Tx-Rx / Tx-Ant duplexer isolation/rejection</b> | [dB] | <b>35</b> | 32 | <b>35</b> | 32 | <b>35</b> | 32 |
+| LNA to antenna insertion loss | [dB] | 4 | | 4 | | 4 | |
+| Antenna isolation | [dB] | <b>0</b> | 10 | <b>0</b> | 10 | <b>0</b> | 10 |
+| PC3 1Tx interference levels: <b>Main/Div</b> | [dBm/CBW] | <b>-64.4</b> | -71.4 | <b>-59.8</b> | -66.8 | <b>-59.2</b> | -66.2 |
+
+**Table 5.6.4.3-4: 20dBm band n28 UL noise for 20/25/20MHz CBW.**
+
+| CBW/NRB | [MHz]/# | 20 | 106 | 25 | 133 | 30 | 160 |
+|----------------------------------------------------|-----------|--------------|--------|--------------|-------|--------------|-------|
+| <b>Meas Tx noise / transmitter noise floor</b> | [dBm/CBW] | <b>-55.0</b> | -60.2 | <b>-43.0</b> | -59.2 | <b>-36.6</b> | -58.4 |
+| <b>Tx-Rx / Tx-Ant duplexer isolation/rejection</b> | [dB] | <b>50</b> | 46 | <b>50</b> | 46 | <b>50</b> | 46 |
+| LNA to antenna insertion loss | [dB] | 4 | | 4 | | 4 | |
+| Antenna isolation | [dB] | <b>0</b> | 10 | <b>0</b> | 10 | <b>0</b> | 10 |
+| PC3 1Tx interference levels: <b>Main/Div</b> | [dBm/CBW] | <b>-99.9</b> | -105.9 | <b>-88.9</b> | -94.9 | <b>-82.6</b> | -88.6 |
+
+From the above, we can derive the MSD post MRC accounting for the addition of n26 and n28 UL noises, but also considering that the main and diversity antennas are swapped between the two bands in the proposed architecture. The calculations are provided for the three band n28 victim bandwidths in Table 5.6.4.3-5 for n28A and Table 5.6.4.3-6 for n28B.
+
+**Table 5.6.4.3-5: REFSENS degradation in n28A.**
+
+| n28CBW | 20MHz n28A | | 25MHz n28A | | 30MHz n28A | |
+|----------------------------------------|--------------|--------------|--------------|--------------|--------------|--------------|
+| | main | div | main | div | main | div |
+| n28 20dBm UL noise [dBm/CBW] | -99.9 | -105.9 | -88.9 | -94.9 | -82.6 | -88.6 |
+| n26 20dBm UL noise [dBm/CBW] | -89.0 | -82.0 | -87.3 | -80.3 | -86.5 | -79.5 |
+| n28 REFSENS [dBm/CBW] | -90.8 | | -84.2 | | -78.5 | |
+| 2UL interference levels [dBm/CBW] | <b>-88.7</b> | <b>-82.0</b> | <b>-85.0</b> | <b>-80.1</b> | <b>-81.1</b> | <b>-79.0</b> |
+| Noise degradation due to Tx noise [dB] | <b>2.7</b> | 6.1 | <b>3.3</b> | 3.5 | <b>3.6</b> | 2.1 |
+| REFSENS degradation after MRC [dB] | <b>5.4</b> | | <b>3.3</b> | | <b>1.9</b> | |
+
+**Table 5.6.4.3-6: REFSENS degradation in n28B.**
+
+| n28CBW | 20MHz n28B | | 25MHz n28B | | 30MHz n28B | |
+|----------------------------------------|--------------|--------------|--------------|--------------|--------------|--------------|
+| | main | div | main | div | main | div |
+| n28 20dBm UL noise [dBm/CBW] | -99.9 | -105.9 | -88.9 | -94.9 | -82.6 | -88.6 |
+| n26 20dBm UL noise [dBm/CBW] | -71.4 | -64.4 | -66.8 | -59.8 | -66.2 | -59.2 |
+| n28 REFSENS [dBm/CBW] | -90.8 | | -84.2 | | -78.5 | |
+| 2UL interference levels [dBm/CBW] | <b>-71.4</b> | <b>-64.4</b> | <b>-66.8</b> | <b>-59.8</b> | <b>-66.1</b> | <b>-59.2</b> |
+| Noise degradation due to Tx noise [dB] | <b>15.5</b> | 22.4 | <b>13.6</b> | 20.4 | <b>9.0</b> | 15.4 |
+| REFSENS degradation after MRC [dB] | <b>20.1</b> | | <b>18.2</b> | | <b>13.5</b> | |
+
+##### **Observations:**
+
+- Even in the n28A case, the 2UL noise is above the band n28 REFSENS levels that already suffers from IMD3 or IMD5 self-desense.
+- In many n28A cases the band n26 UL noise dominates
+
+- In the n28B case the band n26 noise dominates compared to band n28 self desense and although significantly lower than the n26 1UL case, it still results in significant MSD
+- Given that it shows the contribution from both UL the 30MHz CBW for band n28 is preferred.
+
+With the above, the following 2UL MSD is proposed considering both full band n28 and upper 30MHz cases as spectrum availability varies in different regions.
+
+**Table 5.6.4.3-7: 2UL cross band MSD for CA\_n26-n28 accounting for both full band and lower 30MHz only of band n28.**
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|-----------------------------------|
+| | | (MHz) | (MHz) | (kHz) | LCRB | (MHz) | (MHz) | (dB) | |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 788 | 30 | 13.5 | ACLR1 from n26 and n28 |
+| n28 | | 733 | 30 | 15 | 25 (RBstart=135) | | | | |
+| n26 | n28 | 824 | 20 | 15 | 25 (RBstart=0) | 773 | 30 | 1.9 | ACLR2 from n26 and ACLR1 from n28 |
+| n28 | | 718 | 30 | 15 | 25 (RBstart=135) | | | | |
+
+## 5.7 CA\_n5-n28-n105
+
+### 5.7.1 UE RF architecture assumption
+
+#### 5.7.1.1 General
+
+The UE RF architectures with 2 antenna, 3 antenna, 4 antenna can be assumed to analyze and study for CA\_n5-n28-n105. The antenna number is the total number of antennas to support Main UL/DL and diversity DL for all bands. UE RF architecture with three antennas for CA\_n5-n28-n105 is used as baseline for evaluation. The UE RF architectures with two or four antennas are not precluded in the study item. In addition, simultaneous 2-band transmission for UL CA\_n28-n105 has been precluded in this combination which can be leveraged to potentially simplify the RF front-end architecture.
+
+#### 5.7.1.2 UE RF architecture with two antennas
+
+For UE RF architecture with two antennas, three types (a) (b) and (c) are provided below for CA\_n5-n28-n105.
+
+
+
+The diagram illustrates a two-antenna RF architecture for CA\_n5-n28-n105. It features a 'Main TRx' (Transceiver) connected to two 'SPnT' (Switch/Power Network) units. These units are connected to a series of filters and antennas. The 'Diversity Rx' (Receiver) is also connected to two 'SPnT' units, which are connected to a series of filters and antennas. The antennas are labeled with bands: n105, n105/n28A, n28A, n5, n5, n105, n105, n28B, n28B, n5, n5, n105, n28, n5. The architecture is designed to support multiple band combinations while maintaining signal integrity and performance.
+
+Figure 5.7.1.2-1: two-antenna RF architecture (a) for CA\_n5-n28-n105. The diagram shows a 'Main TRx' connected to two 'SPnT' units, which are further connected to a series of filters and antennas. The 'Diversity Rx' is also connected to two 'SPnT' units, which are connected to a series of filters and antennas. The antennas are labeled with bands: n105, n105/n28A, n28A, n5, n5, n105, n105, n28B, n28B, n5, n5, n105, n28, n5.
+
+**Figure 5.7.1.2-1 two-antenna RF architecture (a) for CA\_n5-n28-n105**
+
+
+
+Figure 5.7.1.2-2: two-antenna RF architecture (b) for CA\_n5-n28-n105. The diagram shows two transceivers, Main TRx and Diversity TRx, each connected to a duplexer. Each duplexer is connected to two sPnT (switch/pole) units. Each sPnT unit is connected to a pentaplexer. The Main TRx pentaplexers are connected to antennas labeled n105, n28A, n28A, n5, n5. The Diversity TRx pentaplexers are connected to antennas labeled n105, n28B, n28B, n5, n5.
+
+Figure 5.7.1.2-2 two-antenna RF architecture (b) for CA\_n5-n28-n105
+
+
+
+Figure 5.7.1.2-3: two-antenna RF architecture (c) for CA\_n5-n28-n105. The diagram shows a Main TRx and a Diversity Rx, each connected to a duplexer. Each duplexer is connected to two sPnT (switch/pole) units. Each sPnT unit is connected to a pentaplexer. The Main TRx pentaplexers are connected to antennas labeled n5, n5, n105, n105, n28. The Diversity Rx pentaplexers are connected to antennas labeled n28, n28, n105, n5.
+
+Figure 5.7.1.2-3 two-antenna RF architecture (c) for CA\_n5-n28-n105
+
+The antenna relative bandwidth ratio for two-antenna RF architecture (a), (b) and (c) is shown below.
+
+Table 5.7.1.2-1: the antenna relative bandwidth ratio for two-antenna RF architecture (a), (b) and (c)
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|-----------------------------|--------------------------|
+| Main TRx antenna | 612~894MHz | 37% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+For two-antenna UE RF architecture, although only two low band antennas are kept due to the compact size of smartphone, UE has to face the difficulties of wide bandwidth low-band antenna and complex multiplexer. Specifically,
+
+- 1) For CA\_n5A-n28A-n105A with 2-antenna implementation, the pentaplexer and hexaplexer with 5 and 6 closely spaced frequency ranges could be relatively challenging for filter implementation with acceptable insertion loss and isolation.
+- 2) For CA\_n5A-n28A-n105A with 2-antenna implementation, both main and diversity antennas need to cover the entire spectrum range of 282 MHz simultaneously, which is equivalent to a 37.5% bandwidth ratio and that would far exceed the bandwidth ratio for a typical planar antenna design in a smartphone. As a result, the radiative performance for the combination likely would be highly compromised.
+
+In addition, the other difficulties can be observed, e.g.
+
+- Uses the lower the entire band n28
+- Need the two most critical low bands n28 and n105 in terms on BW and duplex gap
+
+- No gap between n105 and n28
+- No option for co-banding
+- n5 very close to n28 (even more if implemented with a band 26 filter)
+
+#### 5.7.1.3 UE RF architecture with three antennas
+
+For three-antenna RF architecture, three types (a) (b) and (c) are provided below for CA\_n5-n28-n105.
+
+
+
+Figure 5.7.1.3-1: three-antenna RF architecture (a) for CA\_n5-n28-n105. The diagram shows three antenna paths. Main TRx 1 is connected to two sPnT units, which are further connected to four quadruplexers. These quadruplexers are connected to antennas labeled n5, n5, n105, and n105. Main TRx 2 is connected to two sPnT units, which are further connected to four quadruplexers. These quadruplexers are connected to antennas labeled n28A, n28A, n28B, and n28B. Diversity TRx is connected to two sPnT units, which are further connected to three quadruplexers. These quadruplexers are connected to antennas labeled n105, n28, and n5.
+
+Figure 5.7.1.3-1 three-antenna RF architecture (a) for CA\_n5-n28-n105
+
+For a three-antenna RF architecture in Figure 5.7.1.3-1, the UE has also to implement a quadruplexer (n5UL/n5DL/n105DL/n105UL). In addition, wide bandwidth antenna is another challenge for this type of UE RF architecture to cover frequency range from 612MHz to 894MHz. The antenna relative bandwidth ratio for three-antenna RF architecture (a) is shown Table 5.7.1.3-1.
+
+Table 5.7.1.3-1 the antenna relative bandwidth ratio for three-antenna RF architecture (a)
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|-----------------------------|--------------------------|
+| Main TRx antenna 1 | 612~894MHz | 37% |
+| Main TRx antenna 2 | 703~803MHz | 13% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+
+
+Figure 5.7.1.3-2: three-antenna RF architecture (b) for CA\_n5-n28-n105. The diagram shows three antenna paths. Main TRx (left) is connected to two SPnT units, which are further connected to four quadruplexers. These quadruplexers are connected to antennas labeled n105, n105, n105, and n28. Main TRx (middle) is connected to two SPnT units, which are further connected to four quadruplexers. These quadruplexers are connected to antennas labeled n28, n5, n5, and n105. Diversity Rx is connected to two SPnT units, which are further connected to three quadruplexers. These quadruplexers are connected to antennas labeled n105, n28, and n5.
+
+Figure 5.7.1.3-2 three-antenna RF architecture (b) for CA\_n5-n28-n105
+
+The three-antenna RF architecture (b) is shown in Figure 5.7.1.3-2. The antenna relative bandwidth ratio for three-antenna RF architecture (b) is shown in 5.7.1.3-2.
+
+Table 5.7.1.3-2 the antenna relative bandwidth ratio for three-antenna RF architecture (b)
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|------------------------------------------------------------------------|--------------------------|
+| Main TRx antenna 1 | 612~748MHz (UL band n28 is active)<br>612~703MHz (band n105 is active) | 20%<br>13.8% |
+| Main TRx antenna 2 | 758~894MHz | 16.5% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+
+
+Figure 5.7.1.3-3: three-antenna RF architecture (c) for CA\_n5-n28-n105. The diagram shows three main TRx antennas (Main TRx 1, Main TRx 2, and Diversity TRx) connected to a network of filters and switches. Each TRx is connected to two sPnT blocks. The sPnT blocks are further connected to a network of filters and switches that lead to the antenna ports. The antenna ports are labeled with bands: n5, n28A, n28B, n105, n105, n28, and n5. The architecture is designed for CA\_n5-n28-n105.
+
+Figure 5.7.1.3-3 three-antenna RF architecture (c) for CA\_n5-n28-n105
+
+For three-antenna RF architecture Fig 5.7.1.3-3, only single UL is supported for CA\_n5-n28-n105. Two Rx filter groups are considered and the antenna efficiency can be compromised for pure Rx wide bandwidth antenna. This kind of implementation can be achieved more easily to reuse the existing components as soon as possible. The antenna relative bandwidth ratio for three-antenna RF architecture (c) is shown in table 5.7.1.3-3.
+
+Table 5.7.1.3-3 the antenna relative bandwidth ratio for three-antenna RF architecture (c)
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|-------------------------------------------------------------------------------------------------------|--------------------------|
+| Main TRx antenna 1 | 824~894MHz (band n5 is active)<br>703~803MHz (band n28 is active)<br>612~703MHz (band n105 is active) | 8%<br>13%<br>13.8% |
+| Main TRx antenna 2 | 612~894MHz | 37% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+
+
+Figure 5.7.1.3-4: three-antenna RF architecture (d) for CA\_n5-n28-n105. The diagram shows three main TRx antennas (Main TRx 1, Main TRx 2, and Diversity TRx) connected to a network of filters and switches. Each TRx is connected to two sPnT blocks. The sPnT blocks are further connected to a network of filters and switches that lead to the antenna ports. The antenna ports are labeled with bands: n5, n105, n28, n5, n105, n28, and n5, n28, n105. The architecture is designed for CA\_n5-n28-n105.
+
+Figure 5.7.1.3-4 three-antenna RF architecture (d) for CA\_n5-n28-n105
+
+The three-antenna RF architecture (d) is shown in Figure 5.7.1.3-4. The antenna relative bandwidth ratio for three-antenna RF architecture (d) is shown in 5.7.1.3-4.
+
+**Table 5.7.1.3-4 the antenna relative bandwidth ratio for three-antenna RF architecture (b)**
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|-----------------------------|--------------------------|
+| Main TRx antenna 1 | 612~849MHz | 32.4% |
+| Main TRx antenna 2 | 663~894MHz | 29.7% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+
+
+Figure 5.7.1.3-5: three-antenna RF architecture (e) for CA\_n5-n28-n105. The diagram shows three main TRx units (Main TRx 1, Main TRx 2, Diversity TRx) connected to various antennas. Main TRx 1 is connected to two sPnT units, which are further connected to two sets of three antennas (n105, n105, n28). Main TRx 2 is connected to two sPnT units, which are further connected to two antennas (n5, n5). Diversity TRx is connected to two sPnT units, which are further connected to three antennas (n105, n28, n5).
+
+**Figure 5.7.1.3-5 three-antenna RF architecture (e) for CA\_n5-n28-n105**
+
+The three-antenna RF architecture (e) is shown in Figure 5.7.1.3-5. The antenna relative bandwidth ratio for three-antenna RF architecture (e) is shown in 5.7.1.3-5. On concept level, this is basically building on top of CA\_n28-n105, by adding one new antenna (n5 Duplexer) and n5 DRX into n28-n105 DX antenna.
+
+**Table 5.7.1.3-5 the antenna relative bandwidth ratio for three-antenna RF architecture (b)**
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|-----------------------------|--------------------------|
+| Main TRx antenna 1 | 612~803MHz | 27% |
+| Main TRx antenna 2 | 824~894MHz | 8.1% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+For three-antenna UE RF architecture, one more low-band antenna can help ease the design of wide bandwidth antenna and avoid to implement the most complicated multiplexer comparing to two-antenna UE RF architecture. For CA\_n5A-n28A-n105A with 3-antenna implementation under architecture variant (b), the main TRx front-end design is eased by leveraging the non-concurrent UL transmission configuration between n28 and n105.
+
+#### 5.7.1.4 UE RF architecture with four antennas
+
+UE RF architecture with four antennas for CA\_n5-n28-n105 is shown below.
+
+
+
+Figure 5.7.1.4-1: four-antenna RF architecture for CA\_n5-n28-n105. The diagram shows four transceivers (Main TRx 1, Main TRx 2, Main TRx 3, and Diversity TRx) connected to various antennas. Main TRx 1 is connected to two sPnT units, which are further connected to two n105 antennas. Main TRx 2 is connected to two sPnT units, which are further connected to two n5 antennas. Main TRx 3 is connected to two sPnT units, which are further connected to two n28A and two n28B antennas. Diversity TRx is connected to two sPnT units, which are further connected to one n105, one n28, and one n5 antenna.
+
+Figure 5.7.1.4-1 four-antenna RF architecture for CA\_n5-n28-n105
+
+The antenna relative bandwidth ratio for four-antenna RF architecture is shown below.
+
+Table 5.7.1.4-1: the antenna relative bandwidth ratio for two-antenna RF architecture
+
+| Antenna | The covered frequency range | Relative bandwidth ratio |
+|-----------------------|----------------------------------|--------------------------|
+| Main TRx antenna 1 | 612~703MHz (band n105 is active) | 13.8% |
+| Main TRx antenna 2 | 824~894MHz (band n5 is active) | 8% |
+| Main TRx antenna 3 | 703~803MHz (band n28 is active) | 13% |
+| Diversity TRx antenna | 612~894MHz | 37% |
+
+For four-antenna UE RF architecture, even if UE can avoid implementing wide bandwidth low-band antenna and complex multiplexer, UE pays the price of space and antenna performance. Four-antenna RF architecture will not be used to specify the requirement for this band combination.
+
+### 5.7.2 Operating bands for CA
+
+Table 5.7.2-1: CA band combination of band n5+n28+n105
+
+| NR Band | Uplink (UL) band | | Downlink (DL) band | | Duplex mode | |
+|---------|--------------------------|----------------|--------------------------|----------------|-------------|--|
+| | BS receive / UE transmit | | BS transmit / UE receive | | | |
+| | $F_{UL\_low}$ | $F_{UL\_high}$ | $F_{DL\_low}$ | $F_{DL\_high}$ | | |
+| n5 | 824 MHz | 849 MHz | 869 MHz | 894 MHz | FDD | |
+| n28 | 703 MHz | 748 MHz | 758 MHz | 803 MHz | FDD | |
+| n105 | 612 MHz | 652 MHz | 663 MHz | 703 MHz | FDD | |
+
+### 5.7.3 Channel bandwidths per operating band for CA
+
+Table 5.7.3-1: Supported bandwidths per CA band combination of band n8+n20+n28
+
+| NR CA configuration | Uplink CA configuration or single uplink carrier | NR Band | Channel bandwidth (MHz) | Bandwidth combination set |
+|---------------------|--------------------------------------------------|---------|---------------------------|---------------------------|
+| CA_n5A-n28A-n105A | CA_n5A-n105A<br>CA_n5A-n28A | n5 | 5, 10, 15, 20 | 0 |
+| | | n28 | 5, 10, 15, 20, 25, 30 | |
+| | | n105 | 5, 10, 15, 20, 25, 30, 35 | |
+
+### 5.7.4 $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values
+
+For CA\_n5-n28-n105, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values are derived from the existing CA\_n5-n28 and CA\_n28-n105. The following $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values for CA\_n5-n28-n105 can be further considered referring to the contribution [15].
+
+**Table 5.7.4-1: $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ for CA\_n5-n28-n105**
+
+| Inter-band CA Configuration | NR Band | $\Delta T_{IB,c}$ [dB] | $\Delta R_{IB,c}$ [dB] |
+|-----------------------------|---------|--------------------------------------|--------------------------------------|
+| CA_n5A-n28A-n105A | n5 | 0.7 | 0.2 |
+| | n28 | Max(0.7, the value from CA_n28-n105) | Max(0.2, the value from CA_n28-n105) |
+| | n105 | the value from CA_n28-n105 | the value from CA_n28-n105 |
+
+Referring to the contribution [16], the following $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ values in table 5.7.4-2 were proposed after considering the factors:
+
+- Co-banding of n5 with n26
+- The critical design of the band n105, n28 and n26 duplexers to be further multiplexed in a LBLBLB configuration
+- A two-antenna architecture in the future
+- Potential split approach for band n28
+- Existing Delta T and Delta R from 2 band fallbacks
+
+**Table 5.7.4-1: $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ for CA\_n5-n28-n105**
+
+| Inter-band CA combination | $\Delta T_{IB,c}$ for NR bands (dB) | | | $\Delta R_{IB,c}$ for NR bands (dB) | | |
+|---------------------------|----------------------------------------------------------------|-----|-----|-------------------------------------|-----|-----|
+| | Component band in order of bands in configuration <sup>9</sup> | | | | | |
+| CA_n5-n28-n105 | 0.7 | 1.1 | 1.1 | 0.5 | 0.7 | 0.7 |
+
+### 5.7.5 UE co-existence studies for UL inter-band CA
+
+Table 5.7.5-1 lists Band n5 + Band n105 2UL bands CA 2nd, 3rd, 4th and 5th order IMD for the UE-to-UE coexistence analysis, which may fall into the Rx receiver of DL band n28.
+
+Table 5.7.5-1: UL CA\_n5-n105 IMD product
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------------|-----------------------------|----------------------------|-----------------------------|
+| UL frequency (MHz) | 663 | 703 | 824 | 849 |
+| 2 <sup>nd</sup> order IMD products | $ fy\_low - fx\_high $ | $ fy\_high - fx\_low $ | $ fy\_low + fx\_low $ | $ fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 121 | 186 | 1487 | 1552 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low - fy\_high $ | $ 2*fx\_high - fy\_low $ | $ 2*fy\_low - fx\_high $ | $ 2*fy\_high - fx\_low $ |
+| IMD frequency limits (MHz) | 477 | 582 | 945 | 1035 |
+| Two-tone 3 <sup>rd</sup> order IMD products | $ 2*fx\_low + fy\_low $ | $ 2*fx\_high + fy\_high $ | $ 2*fy\_low + fx\_low $ | $ 2*fy\_high + fx\_high $ |
+| IMD frequency limits (MHz) | 2150 | 2255 | 2311 | 2401 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low - 1*fy\_high $ | $ 3*fx\_high - 1*fy\_low $ | $ 3*fy\_low - 1*fx\_high $ | $ 3*fy\_high - 1*fx\_low $ |
+| IMD frequency limits (MHz) | 1140 | 1285 | 1769 | 1884 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 3*fx\_low + 1*fy\_low $ | $ 3*fx\_high + 1*fy\_high $ | $ 3*fy\_low + 1*fx\_low $ | $ 3*fy\_high + 1*fx\_high $ |
+| IMD frequency limits (MHz) | 2813 | 2958 | 3135 | 3250 |
+| Two-tone 4 <sup>th</sup> order IMD products | $ 2*fx\_low - 2*fy\_high $ | $ 2*fx\_high - 2*fy\_low $ | $ 2*fx\_low + 2*fy\_low $ | $ 2*fx\_high + 2*fy\_high $ |
+| IMD frequency limits (MHz) | 372 | 242 | 2974 | 3104 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low - 4*fy\_high $ | $ fx\_high - 4*fy\_low $ | $ fy\_low - 4*fx\_high $ | $ fy\_high - 4*fx\_low $ |
+| IMD frequency limits (MHz) | 2733 | 2593 | 1988 | 1803 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low - 3*fy\_high $ | $ 2*fx\_high - 3*fy\_low $ | $ 2*fy\_low - 3*fx\_high $ | $ 2*fy\_high - 3*fx\_low $ |
+| IMD frequency limits (MHz) | 1221 | 1066 | 461 | 291 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ fx\_low + 4*fy\_low $ | $ fx\_high + 4*fy\_high $ | $ fy\_low + 4*fx\_low $ | $ fy\_high + 4*fx\_high $ |
+| IMD frequency limits (MHz) | 3959 | 4099 | 3476 | 3661 |
+| Two-tone 5 <sup>th</sup> order IMD products | $ 2*fx\_low + 3*fy\_low $ | $ 2*fx\_high + 3*fy\_high $ | $ 2*fy\_low + 3*fx\_low $ | $ 2*fy\_high + 3*fx\_high $ |
+| IMD frequency limits (MHz) | 3798 | 3953 | 3637 | 3807 |
+
+Table 5.7.5-2 lists Band n5 + Band n28 2UL bands CA 2nd, 3rd, 4th and 5th order IMD for the UE-to-UE coexistence analysis, which may fall into the Rx receiver of DL band n105.
+
+Table 5.7.5-2: UL CA\_n5-n28 IMD product
+
+| UE UL carriers | fx_low | fx_high | fy_low | fy_high |
+|---------------------------------------------|----------------------|-----------------------|----------------------|-----------------------|
+| UL frequency (MHz) | 703 | 748 | 824 | 849 |
+| 2 <sup>nd</sup> order IMD products | fy_low – fx_high | fy_high – fx_low | fy_low + fx_low | fy_high + fx_high |
+| IMD frequency limits (MHz) | 76 | 146 | 1527 | 1597 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low – fy_high | 2*fx_high – fy_low | 2*fy_low – fx_high | 2*fy_high – fx_low |
+| IMD frequency limits (MHz) | 557 | 672 | 900 | 995 |
+| Two-tone 3 <sup>rd</sup> order IMD products | 2*fx_low + fy_low | 2*fx_high + fy_high | 2*fy_low + fx_low | 2*fy_high + fx_high |
+| IMD frequency limits (MHz) | 2230 | 2345 | 2351 | 2446 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low – 1*fy_high | 3*fx_high – 1*fy_low | 3*fy_low – 1*fx_high | 3*fy_high – 1*fx_low |
+| IMD frequency limits (MHz) | 1260 | 1420 | 1724 | 1844 |
+| Two-tone 4 <sup>th</sup> order IMD products | 3*fx_low + 1*fy_low | 3*fx_high + 1*fy_high | 3*fy_low + 1*fx_low | 3*fy_high + 1*fx_high |
+| IMD frequency limits (MHz) | 2933 | 3093 | 3175 | 3295 |
+| Two-tone 4 <sup>th</sup> order IMD products | 2*fx_low – 2*fy_high | 2*fx_high – 2*fy_low | 2*fy_low + 2*fy_low | 2*fy_high + 2*fy_high |
+| IMD frequency limits (MHz) | 292 | 152 | 3054 | 3194 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low – 4*fy_high | fx_high – 4*fy_low | fy_low – 4*fx_high | fy_high – 4*fx_low |
+| IMD frequency limits (MHz) | 2693 | 2548 | 2168 | 1963 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low – 3*fy_high | 2*fx_high – 3*fy_low | 2*fy_low – 3*fx_high | 2*fy_high – 3*fx_low |
+| IMD frequency limits (MHz) | 1141 | 976 | 596 | 411 |
+| Two-tone 5 <sup>th</sup> order IMD products | fx_low + 4*fy_low | fx_high + 4*fy_high | fy_low + 4*fx_low | fy_high + 4*fx_high |
+| IMD frequency limits (MHz) | 3999 | 4144 | 3636 | 3841 |
+| Two-tone 5 <sup>th</sup> order IMD products | 2*fx_low + 3*fy_low | 2*fx_high + 3*fy_high | 2*fy_low + 3*fx_low | 2*fy_high + 3*fx_high |
+| IMD frequency limits (MHz) | 3878 | 4043 | 3757 | 3942 |
+
+There is no IMD interference which fall into Rx frequencies of third DL band n28 when CA\_n5-n105 is the UL configuration.
+
+3<sup>rd</sup> order IMD may also fall into Rx frequencies of third DL band n105 when CA\_n5-n28 is the UL configuration.
+
+### 5.7.6 RESENS evaluation
+
+For MSD due to cross band isolation, cross-band analysis done for 2-band cases are sufficient, and no new cross-band analysis are needed for 3-band case
+
+For MSD due to IMD interference on 3<sup>rd</sup> band, the following inputs were provided.
+
+1) The MSD test configurations were evaluated as below for band n105 MSD due to IMD3 of Tx band n5 + band n28 referring to contribution [15].
+
+| Table 5.7.6-1: REFSENS exceptions due to IMD interference for CA_n5-n28-n105Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|--------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n5-n28-n105 | n5 | 845 | 5 | 25 | 890 | N/A | FDD | N/A |
+| | n28 | 740 | 5 | 25 | 795 | N/A | FDD | N/A |
+| | n105 | 686 | 5 | 25 | 635 | 22.9 | FDD | IMD3 |
+
+Generally, there are some network deployment methods to avoid the IMD product hitting the DL carrier directly. For example, if the UL carrier in band n28 is configured in 703~718MHz, no matter which UL frequency carrier in band n5 is configured, the IMD3 products will not hit the DL carrier in band n105 directly.
+
+2) In addition, another contribution [16] proposed to derive the MSD due to IMD3 from CA\_n8-n20-n28 with additional scaling factor. The scaling factor mainly consider the following reasons:
+
+- n28 UL distance to n105 is smaller than n20 to n8
+- n28 UL filter is more critical than band n20 and the lower side is more critical resulting in lower cross-band isolation
+- The lower IMD3 is often higher since the PA has higher gain at lower frequencies.
+
+It's suggested to increase the MSD level by (6) dBs: 2dB for higher level lower IMD3 vs upper and 4dB for lower isolation compared with the MSD of CA\_n8-n20-n28 as below.
+
+**Table 5.7.6-2: REFSENS exceptions due to IMD interference for CA\_n5-n28-n105**
+
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n5-n28-n105 | n5 | 826.5 | 5 | 25 | 871.5 | N/A | FDD | N/A |
+| | n28 | 738.0 | 5 | 25 | 793 | N/A | FDD | N/A |
+| | n105 | N/A | 5 | 25 | 649.5 | 30.3 | FDD | IMD3 |
+
+# Annex A: Change history
+
+| Change history | | | | | | | | |
+|----------------|------------|------------|----|-----|-----|-----------------|-------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2022-10 | RAN4#104be | R4-2217712 | | | | | TR skeleton | 0.1.0 |
+| 2022-10 | RAN4#104be | R4-2217713 | | | | | TP and discussion on CA_n5-n28 | 0.2.0 |
+| 2022-10 | RAN4#104be | R4-2217714 | | | | | TP and discussion on CA_n8-n20-n28 | 0.2.0 |
+| 2022-10 | RAN4#104be | R4-2217715 | | | | | TP and discussion on CA_n5-n8 | 0.2.0 |
+| 2022-11 | RAN4#105 | R4-2220504 | | | | | TP for TR 38.872 on CA_n5-n8 architectures | 0.3.0 |
+| 2022-11 | RAN4#105 | R4-2220505 | | | | | TP on CA_n5-n28 | 0.3.0 |
+| 2022-11 | RAN4#105 | R4-2220506 | | | | | TP for TR 38.872 to capture the RF architecture assumption and IMD evaluation for CA_n8-n20-n28 | 0.3.0 |
+| 2023-03 | RAN4#106 | R4-2300560 | | | | | TP for TR 38.872: scope and references | 0.4.0 |
+| 2023-03 | RAN4#106 | R4-2303544 | | | | | TP for TR 38.872 to complete the open issues for CA_n5-n8 | 0.4.0 |
+| 2023-03 | RAN4#106 | R4-2303545 | | | | | TP for TR 38.872 to complete the open issues for CA_n5-n28 | 0.4.0 |
+| 2023-03 | RAN4#106 | R4-2303546 | | | | | TP for TR 38.872 to complete the open issues for CA_n8-n20-n28 | 0.4.0 |
+| 2023-03 | RAN#99 | RP-230425 | | | | | Editorial update for 1.0.0 version | 1.0.0 |
+
+| Change history | | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|-----------------|------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version |
+| 2023-03 | RAN#99 | | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 |
+| 2023-06 | RAN#100 | RP-231366 | 0001 | | B | | Big CR for TR 38.872 to introduce outcomes of CA_n5-n105 CA_n28-n105 CA_n26-n28 in sub-1GHz SI | 18.1.0 |
+| 2023-09 | RAN#101 | RP-232512 | 0002 | 1 | F | | CR for TR 38.872 to introduce some potential RF impacts for for CA_n26-n28 | 18.2.0 |
+| 2023-09 | RAN#101 | RP-232512 | 0003 | 1 | B | | CR for TR 38.872 to introduce some potential RF impacts for for CA_n5-n28-n105 | 18.2.0 |
+| 2023-12 | RAN#102 | RP-233368 | 0004 | 1 | B | | Draft CR for capturing the output for 2UL/2DL CA_n5-n8 | 18.3.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/38_series/38881/042af54276c75e7b7b48a3af1f0a84e5_img.jpg b/marked/Rel-18/38_series/38881/042af54276c75e7b7b48a3af1f0a84e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c5edccb189bca837f5fbc413b3a8ae7bd0971709
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/042af54276c75e7b7b48a3af1f0a84e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1268f89a238d834820f2197a3bb3f2ca2835c0574c1bd39bfc5d7b51dfbe8e4f
+size 42279
diff --git a/marked/Rel-18/38_series/38881/051638d871c75230edb3d005fa668810_img.jpg b/marked/Rel-18/38_series/38881/051638d871c75230edb3d005fa668810_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bdf2ffbca679a7f0a261b2acaccd2e8b4ed0cce5
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/051638d871c75230edb3d005fa668810_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd8c23dbe31a297eebbd432eff6ce3176f0ae7084e7ba63a6ad32261743aa727
+size 26118
diff --git a/marked/Rel-18/38_series/38881/06ccd604e7eac77c7a5a323b6a913f15_img.jpg b/marked/Rel-18/38_series/38881/06ccd604e7eac77c7a5a323b6a913f15_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4c18dd0e3f507d20b406be11fe5788044f33528
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/06ccd604e7eac77c7a5a323b6a913f15_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61a3b1136a4b503ad5b51dc0d2d8ca9b950e6fc0f2066b68b945d9381ebda7d1
+size 45854
diff --git a/marked/Rel-18/38_series/38881/0a8d173734e4e46c344178e8d21bcbc3_img.jpg b/marked/Rel-18/38_series/38881/0a8d173734e4e46c344178e8d21bcbc3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..600db054bf41869230e27079a470393326522e90
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/0a8d173734e4e46c344178e8d21bcbc3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32ea50a244dac2b27084dce5c70fc1e6785f4912d76f792b01e092ceb169e709
+size 16992
diff --git a/marked/Rel-18/38_series/38881/146d3888c39166a3a81fcedb7d9f6b3d_img.jpg b/marked/Rel-18/38_series/38881/146d3888c39166a3a81fcedb7d9f6b3d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5988b3456573cb06900bbe40302cbb6470089e8
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/146d3888c39166a3a81fcedb7d9f6b3d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ed1986e565ca25f8ed1295cba89f255fd8bfe7346907907139597c91cf2e07ec
+size 27983
diff --git a/marked/Rel-18/38_series/38881/198d076da025c516aec8122a6ab7db20_img.jpg b/marked/Rel-18/38_series/38881/198d076da025c516aec8122a6ab7db20_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5d3ef4e91a286283c3e633ebc1f0a34c61c5434
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/198d076da025c516aec8122a6ab7db20_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aca1d63a1f80730afb5fd426c5fc525b31dfca29c4a467d4b5e656a7648e62aa
+size 45292
diff --git a/marked/Rel-18/38_series/38881/1a6a826cc13d4e964b7bda69508d78e6_img.jpg b/marked/Rel-18/38_series/38881/1a6a826cc13d4e964b7bda69508d78e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ceceb394b764ba40d03f160c055f9f6218a2b31
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/1a6a826cc13d4e964b7bda69508d78e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:811c7f9326bdf8456cdb12e2b2a7457feeda5dc5fc3ecdd0172b9e8999bbecdc
+size 18237
diff --git a/marked/Rel-18/38_series/38881/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-18/38_series/38881/2cf3896394a2342a2b46c504ab9a8830_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e037a79c89dfa22ade0aea22c170884d66087951
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/2cf3896394a2342a2b46c504ab9a8830_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70df98a35dc05a2fb9ea51acc527665c71b1111ef4d9d54620987f00c10ea9e6
+size 34025
diff --git a/marked/Rel-18/38_series/38881/2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg b/marked/Rel-18/38_series/38881/2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6479b523ea1c8f286d11b64b18254a24c208db11
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aecba68a6ad516065995259b1d5cd57402c5b3d164961be6ae2573b8b667f653
+size 32324
diff --git a/marked/Rel-18/38_series/38881/3621e1493d508bd789fec58ba8be9a40_img.jpg b/marked/Rel-18/38_series/38881/3621e1493d508bd789fec58ba8be9a40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0258fde3135fab05c177271d099ff73ca0b12325
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/3621e1493d508bd789fec58ba8be9a40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2278a2ddecbd1814996753ade645aa07c92126c3b10ab159ce9c40df57ce17a7
+size 32474
diff --git a/marked/Rel-18/38_series/38881/3d7e0eb9c7e514f3026945a039354da4_img.jpg b/marked/Rel-18/38_series/38881/3d7e0eb9c7e514f3026945a039354da4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7d3abf5dd05ea537a515746a07f9844d6895492
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/3d7e0eb9c7e514f3026945a039354da4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14fe020ec6b2a38933d37a2c4dc812e1626cb537a04ac742bd2645e6e698e0d7
+size 28169
diff --git a/marked/Rel-18/38_series/38881/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg b/marked/Rel-18/38_series/38881/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c509f38f64280143d42b25aa155a93435f97234
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37f6113ebbcaa63b0310e37e50c8285b7b54822788b38afd7f9f56fcaf99eeb2
+size 27112
diff --git a/marked/Rel-18/38_series/38881/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-18/38_series/38881/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dd086ddd4404410d18a9c3731fe159d38bd34520
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3f48fcbf69db0c6cf8b99a81d3d896eccba435160b8479cba210af2e0418449
+size 31456
diff --git a/marked/Rel-18/38_series/38881/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38881/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5
+size 9571
diff --git a/marked/Rel-18/38_series/38881/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg b/marked/Rel-18/38_series/38881/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aecad942caf13a39976b180d28b8c5829fde7686
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/645cfdb7a7e02c3b04b20d83aed890c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00e6c1596202e1988fc41e42a6b260174dcc1838f22d8b17c453366659e28e26
+size 23552
diff --git a/marked/Rel-18/38_series/38881/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38881/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11e456ef5b6988eefac25582f38d7b3a2da05626
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9200919ca1e3794b1d71c4461eb92b1d02106be28fd43ac3fc4e7c9cfacf6ed8
+size 6791
diff --git a/marked/Rel-18/38_series/38881/6b09b11992389190c93c33a3e80d6fa9_img.jpg b/marked/Rel-18/38_series/38881/6b09b11992389190c93c33a3e80d6fa9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b72fca5b0c81c4a086d6e3a1cb60709dc35c98e3
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/6b09b11992389190c93c33a3e80d6fa9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5b4da19c9d7d978ceab19124f6f78a0f7721363ea9a84feb7a42c1822577657
+size 44252
diff --git a/marked/Rel-18/38_series/38881/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/Rel-18/38_series/38881/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6a0a3d39645bf12c615e123a014533bf4d9ff2a
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eff8d31a2520f4f051878343cfdf911358707b4ccf60d38ed90381fb305bcb51
+size 35392
diff --git a/marked/Rel-18/38_series/38881/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-18/38_series/38881/853ef5420f0432e626e83987e3f38a0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..400fb5137e2a01755b3afac6ee1cbd62631eb302
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/853ef5420f0432e626e83987e3f38a0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a16fa1a9bd4c91889424c883bce33b22a72149cc2ecfbf9bced426f4477c4b36
+size 26565
diff --git a/marked/Rel-18/38_series/38881/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Rel-18/38_series/38881/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2256be96d41299bc0c208661ae01f99413152215
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3c6dabbba8892daf6bd5aca0d01afbc705aae50606d77779777e036b500a769
+size 20987
diff --git a/marked/Rel-18/38_series/38881/933151db66eefe2e64a0a4da5d37e05e_img.jpg b/marked/Rel-18/38_series/38881/933151db66eefe2e64a0a4da5d37e05e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1ae7a45d63f7adda2b3eee4368e48211452d9b0
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/933151db66eefe2e64a0a4da5d37e05e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1da00487687ea340bf9fc45918ac8e291dc6ce0dfecc66a70961928e4c02514
+size 45110
diff --git a/marked/Rel-18/38_series/38881/94389c644d3c25d99db7bc6d87bf5779_img.jpg b/marked/Rel-18/38_series/38881/94389c644d3c25d99db7bc6d87bf5779_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..592337fb1974c973b88a077b28e66967a1c976d1
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/94389c644d3c25d99db7bc6d87bf5779_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f656bf27ee5a88176d12b2341be7f48f8a92757f6ad291ee358a8dacba16ad9
+size 42539
diff --git a/marked/Rel-18/38_series/38881/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg b/marked/Rel-18/38_series/38881/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dd2d5b2a3b9f1fadc86fbf32b9c86762f3dcc036
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33f1989762532df73aeef569e3f81f598b681dfea4165b9f9ee95ea53a327033
+size 50440
diff --git a/marked/Rel-18/38_series/38881/9a0dacb540bed1811d90cc1555c3fe7a_img.jpg b/marked/Rel-18/38_series/38881/9a0dacb540bed1811d90cc1555c3fe7a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..059cc5d600a22ad73af722b63e775ced845d6a8a
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/9a0dacb540bed1811d90cc1555c3fe7a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9931fdbbd9a9375c2f3914c8cd02e5c36cde52815d1d75acaeeb93d3afed6b3
+size 32346
diff --git a/marked/Rel-18/38_series/38881/9a7ddc3cf0bd440c55f10ec3dd532961_img.jpg b/marked/Rel-18/38_series/38881/9a7ddc3cf0bd440c55f10ec3dd532961_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15d124806e5bde77811c98823550060e2de20f29
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/9a7ddc3cf0bd440c55f10ec3dd532961_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9ceb3ad0c198ec8e62a620b956b6062468a041c60bc189ee90401cf7f50bbea
+size 24469
diff --git a/marked/Rel-18/38_series/38881/a1545557e366b6302109d13360b199c3_img.jpg b/marked/Rel-18/38_series/38881/a1545557e366b6302109d13360b199c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d6e4b69ce276cd5813edb0e7c12aadda0e06271
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/a1545557e366b6302109d13360b199c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac869a30b047fd73714abdece2cef4dde106db6d987d56d6be3f110553c3cb96
+size 33998
diff --git a/marked/Rel-18/38_series/38881/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-18/38_series/38881/a289b64f80c6df506c0c55d553fc4496_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b31524c364ee4dfe34cd3e43f163acc4b66635a
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/a289b64f80c6df506c0c55d553fc4496_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:104d07c443a173f19a9e1353a0b905414cad44968ea5fdb48879c99ce43ee8ce
+size 23612
diff --git a/marked/Rel-18/38_series/38881/a706c91f074ac2840c161a3d4a7c0f91_img.jpg b/marked/Rel-18/38_series/38881/a706c91f074ac2840c161a3d4a7c0f91_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18983ea64a441ae1403db6729fbb894d131bc7dc
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/a706c91f074ac2840c161a3d4a7c0f91_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d8e9b0cea421aeb4cee02a77ea8b00fd27d9ab81a7cbe941a02b49ca6b9e652
+size 16554
diff --git a/marked/Rel-18/38_series/38881/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-18/38_series/38881/ad555483986d7170a46ce72d164b5bc8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88b915382af22a2e27da5bbed91ce204d708360d
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/ad555483986d7170a46ce72d164b5bc8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da4559c3beb5d0a5f7a7371957f0402bf2589219613784ec80e65014f3485e20
+size 18866
diff --git a/marked/Rel-18/38_series/38881/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/Rel-18/38_series/38881/b2f5606b9c7184c1c6070a290080a3e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70ba2bc43244c06cbdaf90ad67aecdd5f5bddca0
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/b2f5606b9c7184c1c6070a290080a3e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bbd0e7f8bce59466806bf46e62d87803c9fde5be2283f83d1fe1c83c95a19ce
+size 25279
diff --git a/marked/Rel-18/38_series/38881/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg b/marked/Rel-18/38_series/38881/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c386e6bb07cb436fa060bec9201162c5ffdeb01
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dff6f61e3ca6375a144578471cb9869a3f45e1aef5888c0fe5a7c294e29afa09
+size 27447
diff --git a/marked/Rel-18/38_series/38881/ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg b/marked/Rel-18/38_series/38881/ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..551f0b8967db14ebc3b81fbe2c6822c831f4568a
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/ba2fa04727a9b45fb9afd1af3e3e905b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:82df4db01cebd74b9ecbeebb31d6f0cde88588dbf68b4909593d606239c83b93
+size 15710
diff --git a/marked/Rel-18/38_series/38881/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg b/marked/Rel-18/38_series/38881/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..883c117f19111fdda9f50a6d8539a9b048b88451
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78c54a5571c36003cef5a570f483b38df56d591b1329e2e7c17ecb01040e16f4
+size 47553
diff --git a/marked/Rel-18/38_series/38881/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-18/38_series/38881/c53adc66eab40abd5f8b9107d950ad04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95486944d1bdc462cf6b292179d0b4ccaaad8429
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/c53adc66eab40abd5f8b9107d950ad04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f52a92d453a0481bfd2fb165ddea8adbb788b195f4957507b33dcee25733e88
+size 36262
diff --git a/marked/Rel-18/38_series/38881/e046996962d6740cf050a5640e0c6b40_img.jpg b/marked/Rel-18/38_series/38881/e046996962d6740cf050a5640e0c6b40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f42ec452a12ce380b0ac78d6d604d023e5402e11
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/e046996962d6740cf050a5640e0c6b40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c1a826bbd1343996a5b056854146cfa88ee29a0e1aa0b177e34ed836d232c23
+size 45715
diff --git a/marked/Rel-18/38_series/38881/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-18/38_series/38881/e90b25c8d90cadc3f76c376701cf27ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5015a7ead1db621ef5244ff014dbf502f8b607ee
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/e90b25c8d90cadc3f76c376701cf27ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b0f82a9a276bc5daa61cb6b1cae6feb99bde1818857833ef508aceac61fe8e4
+size 19035
diff --git a/marked/Rel-18/38_series/38881/e999b14cdba9a4824937bb35d8489a03_img.jpg b/marked/Rel-18/38_series/38881/e999b14cdba9a4824937bb35d8489a03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24d80d2486f6076c3b846481b9126d83972663b9
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/e999b14cdba9a4824937bb35d8489a03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:069b1d1e7cccaddf54c1bb456d62ecbf26b4dd38216aef00cd7cb2418cbb9444
+size 32555
diff --git a/marked/Rel-18/38_series/38881/f0cab3794e09131ff0a91cabe163ca16_img.jpg b/marked/Rel-18/38_series/38881/f0cab3794e09131ff0a91cabe163ca16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5f6ad0261e4a904a61bf2800a9f6285eef0cd7c
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/f0cab3794e09131ff0a91cabe163ca16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbee64e94c792972ba505a4a7da4fef7ed5d080d0024973738f28a781cc482e8
+size 29700
diff --git a/marked/Rel-18/38_series/38881/f732d3320afe06d979aabbd366184254_img.jpg b/marked/Rel-18/38_series/38881/f732d3320afe06d979aabbd366184254_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f91a8aa63a6cadf26af88cd4094f57a1c51042e3
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/f732d3320afe06d979aabbd366184254_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ca7f7fdf0ba846606f1d44dcb2e1550da16d602b8c6c153a1f5768f71820fda3
+size 39982
diff --git a/marked/Rel-18/38_series/38881/fc857414626a8d94d132e12d9afe52a4_img.jpg b/marked/Rel-18/38_series/38881/fc857414626a8d94d132e12d9afe52a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..510f8d402d9e078a2bcb997a9abdf42d9772dc35
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/fc857414626a8d94d132e12d9afe52a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ae70c061a36531a1d1f884081244d30f3a7efdb23553f6a469a02cc70e28ced
+size 14958
diff --git a/marked/Rel-18/38_series/38881/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/38_series/38881/fd8369b549b3d1a5c848cbd83659cae9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d0e04c09253923d2ef3bf8cdf5636e6ebd92bdc
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/fd8369b549b3d1a5c848cbd83659cae9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0c88abb81aafdef57079d61b73f61015a09fc0dfb1ab4b2e14a3bf868619746
+size 24498
diff --git a/marked/Rel-18/38_series/38881/raw.md b/marked/Rel-18/38_series/38881/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a25426d6fc3dab943d50217cd098202245247510
--- /dev/null
+++ b/marked/Rel-18/38_series/38881/raw.md
@@ -0,0 +1,2748 @@
+
+
+# 3GPP TR 38.881 V18.0.0 (2023-12)
+
+*Technical Report*
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Networks; Lower MSD for inter-band CA/EN-DC/DC combinations (Release 18)**
+
+
+
+The logo for 5G Advanced, featuring a large black '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right.
+
+5G Advanced logo
+
+
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized black font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller black letters below the logo.
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles – Sophia Antipolis
+Valbonne – FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+| | |
+|-----------------------------------------------------------------------------------|----|
+| Foreword ..... | 5 |
+| 1 Scope..... | 7 |
+| 2 References..... | 7 |
+| 3 Definitions of terms, symbols and abbreviations..... | 8 |
+| 3.1 Terms..... | 8 |
+| 3.2 Symbols..... | 8 |
+| 3.3 Abbreviations ..... | 8 |
+| 4 Background..... | 9 |
+| 4.1 Objective ..... | 9 |
+| 5 Band combinations selected for lower MSD analysis ..... | 9 |
+| 6 Study of MSD improvement..... | 9 |
+| 6.1 General ..... | 9 |
+| 6.2 Feasibility study ..... | 10 |
+| 6.2.1 Evaluation from Huawei [8]..... | 10 |
+| 6.2.1.1 MSD analysis assumptions ..... | 10 |
+| 6.2.1.2 MSD by Harmonic Mixing..... | 10 |
+| 6.2.1.3 MSD by Cross-band Isolation..... | 10 |
+| 6.2.1.4 MSD by Harmonic Interference ..... | 11 |
+| 6.2.1.5 MSD by Dual-UL Inter-Modulation Distortion..... | 12 |
+| 6.2.1.6 Summary of MSD ..... | 13 |
+| 6.2.2 Evaluation from Samsung [9]..... | 14 |
+| 6.2.2.1 CA_n3-n78 MSD Analysis on IMD2 ..... | 14 |
+| 6.2.2.2 CA_n3-n78 MSD Analysis on IMD4..... | 15 |
+| 6.2.2.3 CA_n3-n78 MSD Analysis on 2nd Harmonic..... | 15 |
+| 6.2.2.4 CA_n28-n40 MSD Analysis on 3rd Harmonic mixing..... | 16 |
+| 6.2.2.5 CA_n1-n3 MSD Analysis on cross band isolation ..... | 17 |
+| 6.2.3 Evaluation from Nokia [10]..... | 18 |
+| 6.2.3.1 2nd UL harmonic for CA_3-n78 ..... | 18 |
+| 6.2.3.1.1 MSD improvement by single RF component performance improvement ..... | 18 |
+| 6.2.3.1.2 Possible way to achieve 20 dB MSD improvement..... | 20 |
+| 6.2.3.1.3 20 dB MSD improvement with less isolation improvement in Path 2 &3..... | 20 |
+| 6.2.3.1.4 How to achieve MSD = 0 dB ..... | 21 |
+| 6.2.3.2 2nd order harmonic mixing for CA_n3-n78 ..... | 22 |
+| 6.2.3.3 IMD2 for CA_n3-n78 ..... | 23 |
+| 6.2.3.4 MSD improvement and MSD types..... | 24 |
+| 6.2.4 Evaluation from Qualcomm [11]..... | 25 |
+| 6.2.5 Evaluation from Apple [12]..... | 30 |
+| 6.2.5.1 CA_n3-n78 UL 2nd harmonic MSD analysis..... | 30 |
+| 6.2.5.2 CA_n3-n78 2UL IMD2 MSD analysis..... | 32 |
+| 6.2.5.3 CA_n28-n40 3rd order harmonic mixing MSD analysis..... | 34 |
+| 6.2.6 Evaluation from ZTE [13] ..... | 36 |
+| 6.2.7 Evaluation from LGE [14]..... | 41 |
+| 6.2.8 Evaluation from Xiaomi [15] ..... | 42 |
+| 6.2.8.1 2nd harmonic MSD analysis for CA_n3-n78 ..... | 42 |
+| 6.2.8.2 IMD MSD analysis for CA_n3-n78..... | 43 |
+| 6.2.8.2.1 IMD2 MSD ..... | 44 |
+| 6.2.8.2.2 IMD4 MSD ..... | 45 |
+| 6.2.8.3 Comparison of MSD improvement for different MSD types ..... | 46 |
+| 6.2.8.4 Cross band isolation for CA_n1-n3 (R4-2219037)..... | 46 |
+| 6.2.9 Evaluation from Meta [16] ..... | 47 |
+| 6.2.9.1 MSD evaluation results by Harmonic problem ..... | 47 |
+| 6.2.9.2 MSD evaluation results by cross band isolations ..... | 48 |
+| 6.2.9.3 MSD evaluation results by dual uplink transmission ..... | 49 |
+
+| | | |
+|------------------------|---------------------------------------------------------------------------------------------------------|----|
+| 6.3 | Conclusion..... | 50 |
+| 7 | Study of signalling for improved lower MSD ..... | 50 |
+| 7.1 | Possible MSD reporting approaches ..... | 50 |
+| 7.1.1 | Candidate solution 1: MSD reporting depending on frequency region..... | 50 |
+| 7.1.2 | Candidate solution 2: MSD reporting for frequency regions affected by self-interference ..... | 53 |
+| 7.1.2.1 | Basic MSD information unit..... | 53 |
+| 7.1.2.2 | Reporting of low-MSD information ..... | 54 |
+| 7.1.2.2.1 | Aspect of higher order band combinations ..... | 54 |
+| 7.1.2.2.2 | Aspect of power classes ..... | 54 |
+| 7.1.2.2.3 | Network query based reporting..... | 55 |
+| 7.1.2.2.3.1 | Effect of introducing frequency range as one of the filtering conditions ..... | 56 |
+| 7.1.2.2.3.2 | Effect of introducing network preferred minimum Lower MSD class as one of the filtering conditions..... | 57 |
+| 7.1.3 | Candidate solution 3: MSD reporting for frequency regions affected by self-interference ..... | 58 |
+| 7.1.3.1 | Basic MSD information unit..... | 58 |
+| 7.1.3.2 | Reporting of low-MSD information ..... | 60 |
+| 7.2 | Conclusion..... | 61 |
+| Annex A (informative): | Change history..... | 64 |
+
+# Foreword
+
+This Technical Report 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.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions “shall” and “shall not” are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions “must” and “must not” are not used as substitutes for “shall” and “shall not”. Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction “may not” is ambiguous and is not used in normative elements. The unambiguous constructions “might not” or “shall not” are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions “can” and “cannot” are not substitutes for “may” and “need not”.
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions “is” and “is not” do not indicate requirements.
+
+# --- 1 Scope
+
+The present document is a technical report for study of lower MSD for inter-band CA/EN-DC/DC combinations.
+
+# --- 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] RP-210890, "New WID on New WID on simultaneous Rx/Tx band combinations for CA, SUL, MR-DC and NR-DC".
+- [3] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [4] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone".
+- [5] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios".
+- [6] R4-2214452, "WF on study for lower MSD", Huawei, HiSilicon
+- [7] R4-2217723, "WF on study for lower MSD", Huawei, HiSilicon
+- [8] R4-2216776, "Further discussion on the feasibility of improving MSD", Huawei, HiSilicon
+- [9] R4-2215734, "Views on feasibility of improved MSD", Samsung
+- [10] R4-2215792, "Feasibility study on amount of MSD improvement", Nokia
+- [11] R4-2215379, "Investigation of band combinations for MSD reduction", Qualcomm
+- [12] R4-2215666, "Further analyses and views on MSD improvement for inter-band CA and DC", Apple
+- [13] R4-2215889, "Discussion on lower MSD for inter-band CA/ENDC", ZTE
+- [14] R4-2216187, "MSD evaluation considering the high PCB isolation for CA n1-n3", LG Electronics
+- [15] R4-2216145, "Discussion on lower MSD for inter-band CA/EN-DC/DC", Xiaomi
+- [16] R4-2218297, "On MSD evaluation with new assumptions for MSD improvement", Meta
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| | |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+| | |
+|---------|-------------------------------------------------------------------------------------------------------|
+| ACLR | Adjacent Channel Leakage Ratio |
+| ACS | Adjacent Channel Selectivity |
+| A-MPR | Additional Maximum Power Reduction |
+| BCS | Bandwidth Combination Set |
+| CA | Carrier Aggregation |
+| CC | Component Carrier |
+| DC | Dual Connectivity |
+| EIRP | Equivalent Isotropically Radiated Power |
+| EN-DC | E-UTRA/NR DC |
+| EVM | Error Vector Magnitude |
+| FDM | Frequency Division Multiplexing |
+| FR | Frequency Range |
+| ENBW | The aggregated bandwidth of an E-UTRA sub-block and an adjacent NR sub-block |
+| ITS | Intelligent Transportation System |
+| ITU-R | Radiocommunication Sector of the International Telecommunication Union |
+| MBW | Measurement bandwidth defined for the protected band |
+| MPR | Allowed maximum power reduction |
+| MSD | Maximum Sensitivity Degradation |
+| MCG | Master Cell Group |
+| NR | New Radio |
+| NS | Network Signalling |
+| NSA | Non-Standalone, a mode of operation where operation of an other radio is assisted with an other radio |
+| OOB | Out-of-band |
+| OOBE | Out-of-band emission |
+| OTA | Over The Air |
+| PRB | Physical Resource Block |
+| PSCCH | Physical Sidelink Control Channel |
+| PSSCH | Physical Sidelink Shared Channel |
+| RE | Resource Element |
+| REFSENS | Reference Sensitivity |
+| RF | Radio Frequency |
+| Rx | Receiver |
+| SCG | Secondary Cell Group |
+| SCS | Subcarrier spacing |
+| SEM | Spectrum Emission Mask |
+| SL | Sidelink |
+| SUL | Supplementary uplink |
+| TDM | Time Division Multiplex |
+
+| | |
+|---------|---------------------------------------|
+| Tx | Transmitter |
+| UE | User Equipment |
+| UL MIMO | Up Link Multiple Antenna transmission |
+| ULSUP | Uplink sharing from UE perspective |
+
+# --- 4 Background
+
+## 4.1 Objective
+
+The objectives of the lower MSD objective in the Rel-18 UE RF FR1 WI are as follows:
+
+### **Investigate the feasibility of lower MSD for inter-band CA/EN-DC/DC combinations [RAN4]**
+
+- Select a limited set of band combinations (2-4 combinations) to cover all types of MSD (harmonic, harmonic mixing, IMD and cross band isolation)
+- Study how the MSD performance can be improved for the example band combinations
+- Study of MSD improvement with different MSD sources (harmonics, IMD2/3/4/5, cross band isolation and harmonic mixing)
+- Study the feasibility of and options for allowing a UE to signal improved lower MSD performance capability for combinations where MSD is allowed
+- Aim to conclude the study phase by RAN#99, and further discuss in RAN#99 how to handle the objective based on the study progress.
+
+# --- 5 Band combinations selected for lower MSD analysis
+
+The following example band combinations are used to study the feasibility of MSD improvement for different MSD types:
+
+- CA\_n28-n40 (harmonic mixing)
+- CA\_n41-n77 (cross band isolation)
+- CA\_n1-n3-n78 and fallback combinations (IMD on the 3<sup>rd</sup> band, cross band isolation on CA\_n1-n3 using 50MHz channel bandwidth, IMD2/4 and 2<sup>nd</sup> harmonic and harmonic mixing on CA\_n3-n78)
+
+Note 1: All supported power classes for the above example band combinations can be analyzed.
+
+# --- 6 Study of MSD improvement
+
+## 6.1 General
+
+The purpose of study of MSD improvement is to justify whether it is feasible to improve the MSD for a band combination with reasonable implementation assumptions, which is the basis for the next stage study of signaling part of the WI objective for lower MSD.
+
+It was agreed in WF [7] that no unified assumptions are needed for the evaluation of MSD improvement, e.g. reference architectures, antenna isolation, PCB isolation, component linearity, etc. The following feasibility study are carried out by companies separately with own analysis assumptions for reference. Apart from the assumptions, if listed, the evaluation results for the example band combinations as well as the observations are captured in the feasibility study respectively.
+
+## 6.2 Feasibility study
+
+### 6.2.1 Evaluation from Huawei [8]
+
+#### 6.2.1.1 MSD analysis assumptions
+
+Some common RF assumptions are listed in Table 6.2.1.1-1 below, which are the baseline for the following MSD analysis. Some parameters such as PCB/antenna isolation may be varied to evaluate their effect on the MSD performance. Other parameters related to certain types of MSD are described in the individual sub-sections.
+
+**Table 6.2.1.1-1: Common RF assumptions**
+
+| | |
+|------------------------------|-----------|
+| Diplexer/Triplexer Isolation | 15 dB |
+| Antenna Isolation | 10 dB |
+| PCB isolation | 70 dB |
+| Front-end insertion loss | 4~5 dB |
+| PA output power | 27~28 dBm |
+
+#### 6.2.1.2 MSD by Harmonic Mixing
+
+The L-H band combinations such as CA\_n20-n40, CA\_n28-n40 and CA\_n18-n41 are susceptible to harmonic mixing problems. More than 30dB MSD is specified for CA\_n28-n40 when the mixing product of the UL in band n40 and the 3<sup>rd</sup> harmonic of the DL LO in band n28 falls within the receiver channel bandwidth. The MSD requirements reuse those for LTE CA\_28-40, which were defined based on the study of several contributions.
+
+According to the analysis, the conductive path from the aggressor band transmitter to the victim band receiver dominates the interference level. And the victim band receiver **duplexer/filter rejection** at the aggressor frequency is the key factor in addition to the victim band receiver **mixer harmonic suppression**. Figure 6.2.1.2-1 shows the MSD variation with the optimization of the two key factors.
+
+
+
+| Receiver Filter Rejection (dB) | Harmonic Suppression=30dB (MSD in dB) | Harmonic Suppression=40dB (MSD in dB) | Harmonic Suppression=50dB (MSD in dB) |
+|--------------------------------|---------------------------------------|---------------------------------------|---------------------------------------|
+| 30 | 40 | 30 | 20 |
+| 35 | 35 | 25 | 15 |
+| 40 | 30 | 20 | 10 |
+| 45 | 25 | 15 | 7 |
+
+Figure 6.2.1.2-1: MSD by harmonic mixing varies with the receiver filter rejection and the mixer harmonic rejection. The PCB isolation of 70 dB is assumed. The graph shows MSD (dB) on the y-axis (0 to 45) versus Receiver Filter Rejection (dB) on the x-axis (30 to 45). Three lines represent different Harmonic Suppression levels: 30dB (red), 40dB (green), and 50dB (purple). All lines show a downward trend as filter rejection increases.
+
+**Figure 6.2.1.2-1: MSD by harmonic mixing varies with the receiver filter rejection and the mixer harmonic rejection. The PCB isolation of 70 dB is assumed.**
+
+#### 6.2.1.3 MSD by Cross-band Isolation
+
+As seen from the REFSENS requirements in TS 38.101-1, the MSD is usually more severe when the source of cross-band isolation interference is “ACLR1” or “ACLR2” (e.g. CA\_n18-n28, CA\_n5-n28). If the aggressor channel BW is large (e.g. 50/100MHz), the MSD may increase to more than 10 or even above 20 dB (e.g. CA\_n1-n3, CA\_n1-n40),
+
+even if the source is classified as “>ACLR2”. It’s worth noting that the spec requirements target the worst cases, where the aggressor carrier frequency is set as close as possible to that of the victim.
+
+As shown by the previous analysis, the PA noise and cross-band isolation are the main factors affecting the MSD when the carrier frequencies and UL RB allocation are fixed.
+
+#### 6.2.1.4 MSD by Harmonic Interference
+
+The band combination of CA\_n3-n78 or DC\_3\_n78 may suffer from MSD caused by H2 of the UL in band 3/n3 falling into the DL of band n78. All the RF components in the front-end of band 3/n3 could contribute to the generation of H2, including: duplexer, antenna switch, diplexer/triplexer and etc. It was identified that the main factors are:
+
+- PA linearity
+- Total filter attenuation (including Harmonic Trap Filter and B3 duplexer)
+- PCB isolation.
+
+The filter survey shows that the B3 duplexer attenuation at B42 ranges from 10 to 27 dB, and the discussions indicates that 30 dB is possible for future design. Additionally, the following assumptions were considered optimistic at that time: PA H2 = -35 dBc, HTF = 30dB and PCB isolation (@3.5GHz) = 70dB.
+
+By tuning the total filter attenuation and the PCB isolation while fixing the PA H2=-35dBc, the MSD trend is obtained as shown in Figure 6.2.1.4-1.
+
+
+
+| Total Filter Attenuation (dB) | MSD (dB) for PCB ISO=70dB | MSD (dB) for PCB ISO=75dB | MSD (dB) for PCB ISO=80dB | MSD (dB) for PCB ISO=85dB |
+|-------------------------------|---------------------------|---------------------------|---------------------------|---------------------------|
+| 45 | 25 | 24 | 23 | 22 |
+| 50 | 22 | 20 | 19 | 18 |
+| 55 | 20.5 | 17.5 | 15.5 | 14.5 |
+| 60 | 20 | 16 | 13.5 | 12 |
+| 65 | 19.5 | 15 | 11.5 | 8.5 |
+| 70 | 19.5 | 14.5 | 11 | 7.5 |
+
+Figure 6.2.1.4-1: MSD by Tx harmonic varies with the Tx filter attenuation and the PCB isolation. The PA H2 is assumed to be -35dBc. The graph shows MSD (dB) on the y-axis (0 to 30) versus Total Filter Attenuation (dB) on the x-axis (45 to 70). Four curves are shown for different PCB isolation levels: 70dB (blue), 75dB (red), 80dB (green), and 85dB (purple). All curves show a decreasing trend in MSD as filter attenuation increases. Higher PCB isolation results in lower MSD values.
+
+**Figure 6.2.1.4-1: MSD by Tx harmonic varies with the Tx filter attenuation and the PCB isolation. The PA H2 is assumed to be -35dBc.**
+
+Figure 6.2.1.4-2 illustrates the combination of carrier frequencies that may suffer from MSD caused by Tx harmonic.
+
+
+
+Figure 6.2.1.4-2: A 2D plot showing carrier frequency combinations for Band n3 and Band n78. The x-axis is 'Band n78 Carrier Frequency (MHz)' from 3400 to 3700. The y-axis is 'Band n3 Carrier Frequency (MHz)' from 1720 to 1780. A red diagonal band labeled 'H2' represents the region affected by MSD. A legend on the right shows a red rectangle for 'MSD' and a green rectangle for 'Free'.
+
+Figure 6.2.1.4-2: Illustration of carrier frequency combinations that may be affected by MSD caused by H2. CBW: 10MHz for n3, 20MHz for n78.
+
+#### 6.2.1.5 MSD by Dual-UL Inter-Modulation Distortion
+
+When both uplinks are active, the DL band n3 of CA\_n3-n78 may suffer from IMD2 and IMD4 of the dual-UL. It has been identified that PCB isolation and antenna isolation are the main factors. The MSD trend is reproduced in Figure 6.2.1.5-1 below.
+
+
+
+| PCB Isolation (dB) | ANT ISO=10dB (MSD dB) | ANT ISO=15dB (MSD dB) | ANT ISO=20dB (MSD dB) | ANT ISO=40dB (MSD dB) |
+|--------------------|-----------------------|-----------------------|-----------------------|-----------------------|
+| 60 | 27 | 24 | 23 | 22 |
+| 65 | 24 | 19 | 16 | 13 |
+| 70 | 23 | 17 | 12 | 4 |
+| 75 | 23 | 17 | 11 | 0 |
+| 80 | 23 | 17 | 11 | 0 |
+| 85 | 23 | 17 | 11 | 0 |
+
+Figure 6.2.1.5-1: A line graph titled 'CA\_n3-n78' showing MSD (dB) vs PCB Isolation (dB). Four lines represent different antenna isolation levels: ANT ISO=10dB (blue), ANT ISO=15dB (red), ANT ISO=20dB (green), and ANT ISO=40dB (purple). The graph shows that as PCB isolation increases, MSD decreases. Higher antenna isolation leads to lower MSD.
+
+Figure 6.2.1.5-1: MSD caused by IMD2 for CA\_n3-n78 varies with different PCB isolation and antenna isolation. The 40dB antenna isolation is impractical for small form-factor UEs but serves as a performance indicator for conductive measurements.
+
+In order for the self-interference to fall within the own receiver, the aggressors' carrier frequencies and the victims' carrier frequencies need to satisfy certain mathematical constraints, subject to the order of the IMD. Figure 6.2.1.5-2 indicates the occurrences of IM interferences for CA\_n3-n78.
+
+
+
+Figure 6.2.1.5-2: Illustration of the relationship between IMD and the carrier frequencies. The figure contains two plots. The left plot is titled 'IMD2' and the right plot is titled 'IMD4'. Both plots show 'Band n3 Carrier Frequency (MHz)' on the y-axis (ranging from 1720 to 1780) and 'Band n78 Carrier Frequency (MHz)' on the x-axis (ranging from 3400 to 3700). A red diagonal band represents the 'MSD' (Mobile Station Desensitization) region, while the green areas represent 'Free' regions. The legend on the right of each plot indicates that red is 'MSD' and green is 'Free'.
+
+**Figure 6.2.1.5-2: Illustration of the relationship between IMD and the carrier frequencies. The red color indicates that the IM product may fall into the victim Rx channel, assuming CBW: 10MHz for n3, 20MHz for n78.**
+
+It can be seen that for the majority of the carrier frequency configurations of CA\_n3-n78, there's no self-interference from IMD2 or IMD4 or H2. Furthermore, when MSD from IMD2 happens for a given deployment, MSD from IMD4 does not, or vice versa. Since n78 is a TDD band, the MSD caused by H2 of n3 will not happen at the same time as the MSD caused by IMD2 or IMD4 of the dual UL.
+
+#### 6.2.1.6 Summary of MSD
+
+Based on the above discussions, the key contributors for different types of MSDs are summarized in Table below.
+
+**Table 6.2.1.6-1: Key contributors for different MSD types**
+
+| MSD Types | Key Contributors |
+|-----------------------------------------------------------|---------------------------------------------------------------------------------|
+| Harmonic Mixing (e.g. UL1/DL3, UL1/DL5, UL2/DL3, UL3/DL2) | Victim filter rejection and mixer harmonic suppression |
+| Tx Harmonic (e.g. H2/3/4/5) | Aggressor PA linearity, harmonic filter and duplexer attenuation, PCB isolation |
+| Cross-band Isolation (e.g. ALCR1/2, >ACLR2) | Aggressor PA noise and filter attenuation |
+| Dual-UL IMD (e.g. IMD2/3/4/5/7) | PCB isolation, antenna isolation |
+
+It has been shown that the MSD may be improved by optimizing the key contributors listed in Table 6.2.1.6-1. However, it can also be seen that for large MSD values (>20dB) it would be very challenging to reduce them to below 10dB. Furthermore, we can make the following observations:
+
+**Observation 1:** Different types of MSDs may have different limiting factors. Which one can be improved for what band combinations are design choices of the UE implementation.
+
+**Observation 2:** For large MSD values (>20dB) it's very challenging to reduce them to below 10dB. The relatively small MSD values (<10 dB) may be further improved depending on UE implementation.
+
+**Observation 3:** The antenna isolation plays an important role in MSD performance. However, the effect is not verified by the existing conductive tests.
+
+**Observation 4:** For a given band combination, MSD from different sources are unlikely to happen simultaneously, depending on the configuration of carrier frequencies, duplex mode of the component bands, the order of IMD or harmonics and etc.
+
+### 6.2.2 Evaluation from Samsung [9]
+
+#### 6.2.2.1 CA\_n3-n78 MSD Analysis on IMD2
+
+The component linearity parameters and initial isolation parameters adopted in our calculation was summarized in Table 6.2.2.1-1 and Table 6.2.2.1-2 respectively.
+
+**Table 6.2.2.1-1 Front-end component linearity parameters for MSD calculation**
+
+| Component | IP2(dBm) | IP3(dBm) | IP4(dBm) | IP5(dBm) |
+|-------------|----------|----------|----------|----------|
+| Ant. Switch | 112 | 68 | 56 | 53 |
+| Triplexer | 115 | 86 | 55 | 53 |
+| Duplexer | 100 | 74 | 55 | 53 |
+| PA Forward | 28 | 30 | 32 | 27 |
+| PA Reversed | 40 | 28 | 33 | 32 |
+| LNA | 5 | -6 | -6 | -10 |
+
+**Table 6.2.2.1-2 Front-end component isolation**
+
+| Isolation Parameter | Value (dB) | Comment |
+|----------------------|------------|--------------------------------------------|
+| Antenna to Antenna | 10 | Main antenna to diversity antenna |
+| PA (out) to PA (in) | 65 | PCB isolation (PA forward mixing) |
+| Triplexer | 15 | Low/high/very high band isolation |
+| PA (out) to PA (out) | 65 | PCB isolation (PA reverse mixing) |
+| LNA (in) to PA (out) | 65 | Cross-band (B42 filter + triplexer) |
+| LNA (in) to PA (out) | 65 | PCB isolation (B42 PA leakage into B3 LNA) |
+| Duplexer | 50 | Tx band rejection at Rx band |
+
+It is observed that PCB isolation, antenna isolation and duplexer isolation are the main contributors for MSD due to IMD2, the affected dominant items are marked as blue in the link budget calculation process of IMD2 presented in Table 6.2.2.1-3.
+
+**Table 6.2.2.1-3 Link budget analysis for CA\_n3-n78 IMD2**
+
+| Main Path | | | | | Diversity path | | | | | Main Path (dBm) | Thermal | IMD | Total |
+|--------------------|-----------|------------|-----------|------------|--------------------|-----------|------------|-----------|------------|----------------------|---------|-------|-------|
+| Component | PB3 (dBm) | PB42 (dBm) | IP2 (dBm) | IMD2 (dBm) | Component | PB3 (dBm) | PB42 (dBm) | IP2 (dBm) | IMD2 (dBm) | | | | |
+| Antenna Switch | 20 | 5 | 112 | -87 | From Main Path | | | | | Diversity Path (dBm) | -94 | -62.7 | -62.7 |
+| Triplexer | 20 | 20 | 115 | -75 | Antenna Switch | 10 | -5 | 112 | -107 | After MRC (dBm) | -94 | -73.3 | -73.2 |
+| B3 Duplexer | 23 | 5 | 100 | -72 | Triplexer | 10 | 10 | 115 | -95 | MSD (dB) | | | 26.2 |
+| B3 PA Forward | 23 | -12 | 28 | -64 | B3 Filter | 10 | -5 | 100 | -95 | | | | |
+| B42 PA Forward | -12 | 23 | 28 | -79 | B3 LNA | -40 | -55 | 5 | -97 | | | | |
+| B3 PA Reversed | 23 | -42 | 40 | -106 | Total IMD | | | | -72.9 | | | | |
+| B42 PA Reversed | -42 | 23 | 40 | -121 | Total IMD after CF | | | | -73.3 | | | | |
+| Tx Total | | | | -62.9 | | | | | | | | | |
+| B3 LNA | -27 | -42 | 5 | -71 | | | | | | | | | |
+| Total IMD | | | | -62.3 | | | | | | | | | |
+| Total IMD after CF | | | | -62.7 | | | | | | | | | |
+
+As recorded in WF, the feasible antenna isolation used in Lower MSD study is 10-20dB, while the feasible range of PCB isolation need further discussion. Under this premise we have evaluated the MSD improvement over antenna isolation up to 20dB and PCB isolation up to 85dB which are the two contributors to all kinds of MSD improvement, as Figure 6.2.2.1-1 without taking into account the practical implementation. Note that the feasibility of PCB isolation is subject to the group's further confirmation.
+
+
+
+Figure 6.2.2.1-1: IMD2 MSD trend analysis over better PCB isolation and antenna isolation. The graph shows MSD(dB) on the y-axis (13 to 27) versus PCB isolation(dB) on the x-axis (65 to 85). Three lines represent different antenna isolation levels: Ant ISO=10 (blue), Ant ISO=15 (red), and Ant ISO=20 (green). All lines show a downward trend as PCB isolation increases. The green line (Ant ISO=20) reaches the lowest MSD of approximately 15.5 dB at 85 dB PCB isolation.
+
+Figure 6.2.2.1-1 IMD2 MSD trend analysis over better PCB isolation and antenna isolation
+
+Observation 1: It is observed that in terms of PC3, MSD due to IMD2 of CA\_n3-n78 could be reduced to around 15dB with 85dB PCB isolation and 20dB antenna isolation, in contrast to 26dB specified MSD.
+
+#### 6.2.2.2 CA\_n3-n78 MSD Analysis on IMD4
+
+The link budget calculation process of IMD4 is presented in Table 6.2.2.2-1 and the MSD improvement over antenna isolation up to 20 dB and PCB isolation up to 85 dB is presented in Figure 6.2.2.2-1.
+
+Table 6.2.2.2-1 Link budget analysis for CA\_n3-n78 IMD4
+
+| Main Path | | | | | Diversity path | | | | | Main Path (dBm) | Thermal | IMD | Total |
+|--------------------|-----------|------------|-----------|------------|--------------------|-----------|------------|-----------|------------|----------------------|---------|-------|-------|
+| Component | PB3 (dBm) | PB42 (dBm) | IP2 (dBm) | IMD2 (dBm) | Component | PB3 (dBm) | PB42 (dBm) | IP2 (dBm) | IMD2 (dBm) | | | | |
+| Antenna Switch | 20 | 5 | 56 | -103 | From Main Path | | | | | -91.9 | -94 | -82.2 | -81.9 |
+| Triplexer | 20 | 20 | 55 | -85 | Antenna Switch | 10 | -5 | 56 | -143 | Diversity Path (dBm) | -94 | -92.3 | -90.0 |
+| B3 Duplexer | 23 | 5 | 55 | -91 | Triplexer | 10 | 10 | 55 | -125 | After MRC (dBm) | | | -85.8 |
+| B3 PA Forward | 23 | -12 | 32 | -86 | B3 Filter | 10 | -5 | 55 | -140 | MSD (dB) | | | 8.0 |
+| B42 PA Forward | -12 | 23 | 32 | -171 | B3 LNA | -40 | -55 | -6 | -154 | | | | |
+| B3 PA Reversed | 23 | -42 | 33 | -119 | Total IMD | | | | -91.9 | | | | |
+| B42 PA Reversed | -42 | 23 | 33 | -264 | Total IMD after CF | | | | -92.3 | | | | |
+| Tx Total | | | | -81.9 | | | | | | | | | |
+| B3 LNA | -27 | -42 | -6 | -102 | | | | | | | | | |
+| Total IMD | | | | -81.8 | | | | | | | | | |
+| Total IMD after CF | | | | -82.2 | | | | | | | | | |
+
+
+
+Figure 6.2.2.2-1: IMD4 MSD analysis over better PCB isolation and antenna isolation. The graph shows MSD(dB) on the y-axis (5 to 10) versus PCB isolation(dB) on the x-axis (65 to 85). Three lines represent different antenna isolation levels: Ant ISO=10 (blue), Ant ISO=15 (red), and Ant ISO=20 (green). All lines show a downward trend as PCB isolation increases. The green line (Ant ISO=20) reaches the lowest MSD of approximately 5.5 dB at 85 dB PCB isolation.
+
+Figure 6.2.2.2-1 IMD4 MSD analysis over better PCB isolation and antenna isolation
+
+Observation 2: It is observed that in terms of PC3, MSD due to IMD4 of CA\_n3-n78 could be reduced to around 5dB with 85dB PCB isolation and 20dB antenna isolation, in contrast to 8dB specified MSD.
+
+#### 6.2.2.3 CA\_n3-n78 MSD Analysis on 2nd Harmonic
+
+It is observed that PCB isolation, antenna isolation and PA harmonic rejection are the main contributors of the MSD due to harmonic, the link budget calculation process and its initial adopted RF component assumption are presented in Table 6.2.2.3-1 and similar as above the MSD improvement over antenna isolation up to 20 dB and PCB isolation up to 85 dB is presented in Figure 6.2.2.3-1.
+
+**Table 6.2.2.3-1 RF Component assumption and Link budget analysis for CA\_n3-n78 2nd harmonic MSD**
+
+| Path | Parameter | PRX | DRX | Path | H2 level | PRx(dBm) | DRX(dBm) | | Composite H2 at LNA port, dBm | -75.0 | -76.6 |
+|--------|-----------------------------------|--------|--------|--------|------------------------------------|----------|----------|--|-------------------------------|-------|-------|
+| | B3 PA output power, dBm | 28 | 28 | | H2 at B3 PA | -7 | -7 | | Composite noise, dBm | -75.0 | -76.6 |
+| | B3 Duplexer IL, dB | 2.5 | 2.5 | | H2 post B3 Duplexer | -37 | -37 | | MSD, dB | 25.3 | 23.7 |
+| | Harmonics Filter IL, dB | 0.5 | 0.5 | | H2 at B3 Duplexer H2 | -62 | -62 | | Combined MSD, dB | 24.5 | |
+| | HB Switch IL, dB | 0.7 | 0.7 | | H2 at Duplexer output | -37.0 | -37.0 | | | | |
+| | Triplexer IL, dB | 1.3 | 1.3 | | H2 post Harmonics Filter | -62.0 | -57.0 | | | | |
+| | B3 PA H2, dBc | 35 | 35 | | H2 at HB Switch | -75.7 | -75.7 | | | | |
+| | B3 Duplexer Rejection, dB | 30 | 30 | | H2 at HB Switch output | -61.8 | -56.9 | | | | |
+| | B3 Duplexer H2, dBc | 90 | 90 | | H2 post Triplexer | -76.8 | -76.9 | | | | |
+| | Harmonics Filter Rejection, dB | 25 | 20 | | H2 at DRX Antenna connector | | -86.9 | | | | |
+| | HB Switch H2, dBc | 100 | 100 | Path 1 | H2 at LNA from Tx to Rx Chain path | -79.8 | -89.9 | | | | |
+| | Triplexer Rejection&Isolation, dB | 15 | 20 | | H2 post PA | -7 | -7 | | | | |
+| | Antenna Isolation, dB | | 10 | Path 2 | H2 at LNA from PA | -77 | -77 | | | | |
+| | UHB Switch IL, dB | 1 | 1 | Path 3 | H2 at LNA from Single Chip DA | -90 | -90 | | | | |
+| PATH 1 | B42 Saw Filter IL, dB | 2 | 2 | | | | | | | | |
+| | B3 PA output power, dBm | 28 | 28 | | | | | | | | |
+| | B3 PA H2, dBm | 35 | 35 | | | | | | | | |
+| PATH 2 | PA to LNA isolation, dB | 70 | 70 | | | | | | | | |
+| PATH 3 | Single Chip DA to LNA, dBm | -90 | -90 | | | | | | | | |
+| Common | Chip Noise Figure, dB | 4 | 4 | | | | | | | | |
+| | Noise Floor (10M, 52RB), dBm | -100.3 | -100.3 | | | | | | | | |
+
+
+
+| PCB isolation(dB) | Ant ISO-10 (MSD dB) | Ant ISO-15 (MSD dB) | Ant ISO-20 (MSD dB) |
+|-------------------|---------------------|---------------------|---------------------|
+| 65 | 28.5 | 28.5 | 28.5 |
+| 70 | 24.5 | 24.5 | 24.5 |
+| 75 | 20.5 | 20.5 | 20.5 |
+| 80 | 17.5 | 17.5 | 17.5 |
+| 85 | 15.5 | 14.5 | 13.0 |
+
+Figure 6.2.2.3-1: Harmonic MSD analysis over better PCB isolation and antenna isolation. The graph shows MSD(dB) on the y-axis (10 to 30) versus PCB isolation(dB) on the x-axis (65 to 85). Three lines represent different antenna isolation levels: Ant ISO-10 (blue), Ant ISO-15 (red), and Ant ISO-20 (green). All lines show a downward trend as PCB isolation increases. The green line (Ant ISO-20) reaches the lowest MSD of approximately 13 dB at 85 dB PCB isolation.
+
+**Figure 6.2.2.3-1 Harmonic MSD analysis over better PCB isolation and antenna isolation**
+
+Observation 3: It is observed that in terms of PC3, MSD due to 2nd harmonic of CA\_n3-n78 could be reduced to around 13dB with 85dB PCB isolation and 20dB antenna isolation, in contrast to 23.9dB specified MSD.
+
+#### 6.2.2.4 CA\_n28-n40 MSD Analysis on 3rd Harmonic mixing
+
+It is observed that PCB isolation, lower band Rx filter selectivity and Rx 3<sup>rd</sup> order harmonic rejection are the main contributors of the MSD due to harmonic mixing, the link budget calculation process and its initial adopted RF component assumption are presented in Table 6.2.2.4-1, based on our analysis larger antenna isolation has almost no contribution to the MSD improvement since it only affects the diversity conductive path which has less influence on Diversity MSD.
+
+The MSD improvement over Rx 3<sup>rd</sup> harmonic rejection up to 30 dB and PCB isolation up to 85 dB is presented in Figure 6.2.2.4-1, without taking into account the practical implementation. Note that the antenna isolation assumption is 10dB considering antenna isolation has almost no contribution to the MSD improvement.
+
+**Table 6.2.2.4-1 RF Component assumption and Link budget analysis for CA\_n28-n40 3rd harmonic mixing MSD**
+
+| RF Parameters | | Direct Signal Path | | | Combine MSD | | |
+|---------------------------------------------|-------|-----------------------------|-----------|----------------|------------------------------------------------|-------|-------|
+| | | Parameter | Main(dBm) | Diversity(dBm) | Tx power at LNA input | | |
+| Antenna isolation | 10 dB | Tx power at antenna port | 23 | 13 | Tx power after Rx mixing (referred to antenna) | -42.5 | -42.9 |
+| Frond end loss | 6 dB | Tx power at diplexer output | 8 | -2 | Single band Reference noise floor | -58.5 | -58.9 |
+| Diplexer isolation | 15 dB | Tx power at LNA input | -52 | -62 | Combined noise floor | -95.0 | |
+| Band 28 DUP Rx filter rejection at b40 | 60 dB | PCB Coupling Path | | | MSD | -58.5 | -58.9 |
+| PCB isolation | 70 dB | Parameter | Main(dBm) | Diversity(dBm) | MSD after uncorrelated MRC (5-MHz carrier) | 36.5 | 36.1 |
+| Rx 3 <sup>rd</sup> order harmonic rejection | 20 dB | Tx power at HB PA output | 27 | 27 | | 36.3 | |
+| | | Tx power at LNA input | -43 | -43 | | | |
+| | | Combined | | | | | |
+| | | Tx power at LNA input | -42.5 | -42.9 | | | |
+
+
+
+| PCB isolation (dB) | MSD (dB) at 20 dB Rx rejection | MSD (dB) at 25 dB Rx rejection | MSD (dB) at 30 dB Rx rejection |
+|--------------------|--------------------------------|--------------------------------|--------------------------------|
+| 65 | 41 | 36 | 31 |
+| 70 | 37 | 32 | 27 |
+| 75 | 33 | 28 | 23 |
+| 80 | 29 | 24 | 19 |
+| 85 | 25 | 20 | 15 |
+
+Figure 6.2.2.4-1: Harmonic mixing MSD analysis over better PCB isolation and Rx harmonic rejection. The graph shows MSD(dB) on the y-axis (10 to 45) versus PCB isolation(dB) on the x-axis (65 to 85). Three lines represent different Rx harmonic rejection levels: 20 dB (blue), 25 dB (red), and 30 dB (green). All lines show a downward trend as PCB isolation increases. The 30 dB rejection line is the lowest, reaching approximately 15 dB at 85 dB PCB isolation.
+
+**Figure 6.2.2.4-1 Harmonic mixing MSD analysis over better PCB isolation and Rx harmonic rejection**
+
+**Observation 4:** It is observed that in terms of PC3, MSD due to 3rd harmonic mixing of CA\_n28-n40 could be reduced to around 25dB with 85dB PCB isolation and 20dB antenna isolation, in contrast to 37.8dB specified MSD. Note that antenna isolation has almost no contribution to the MSD improvement.
+
+**Observation 5:** It is observed that in terms of PC3, MSD due to 3rd harmonic mixing of CA\_n28-n40 could be reduced to around 15dB with 85dB PCB isolation and 30dB Rx harmonic rejection, in contrast to 37.8dB specified MSD.
+
+#### 6.2.2.5 CA\_n1-n3 MSD Analysis on cross band isolation
+
+The link budget calculation process and its initial adopted RF component assumption are presented in Table 6.2.2.5-1, similar as above the MSD improvement trend over antenna isolation up to 20 dB and PCB isolation up to 85 dB is presented in Figure 6.2.2.5-1.
+
+**Table 6.2.2.5-1 RF Component assumption and Link budget analysis for CA\_n1-n3 cross band isolation MSD**
+
+| RF parameter assumptions and link calculation process | | |
+|---------------------------------------------------------------|-----|-------------|
+| Measured n1 TX noise level at n3 FC=1877.5MHz in 5MHz(PA out) | dBm | -23 |
+| PA to Rx noise quadplexer rejection at n3 DL frequency | dB | 50 |
+| PA to Antenna quadplexer noise rejection at n3 DL frequency | dB | 45 |
+| LNA to antenna insertion loss | dB | 4 |
+| PCB isolation | dB | 65 |
+| Antenna isolation | dB | 0 10 |
+| Direct signal Path1 @n3 LNA : primary | dBm | -73 |
+| Direct signal Path2 @n3 LNA : primary/diversity | dBm | -68 -78 |
+| Coupling Path: primary/diversity: primary/diversity | dBm | -88 -88 |
+| In channel interference levels: primary/diversity | dBm | -66.8 -77.6 |
+| n3 ideal RB scaled Refsens spec | dBm | -97 |
+| noise floor | dBm | -93 -93 |
+| Composite interference levels:primary/diversity | dBm | -66.8 -77.5 |
+| n3 degradation | dB | 26.2 15.5 |
+| n3 5M MSD after MRC | dB | 19.5 |
+
+
+
+| PCB isolation(dB) | Ant ISO=10 (MSD(dB)) | Ant ISO=15 (MSD(dB)) | Ant ISO=20 (MSD(dB)) |
+|-------------------|----------------------|----------------------|----------------------|
+| 65 | 19.7 | 16.0 | 13.0 |
+| 70 | 19.5 | 15.5 | 11.5 |
+| 75 | 19.3 | 15.0 | 10.5 |
+| 80 | 19.2 | 14.8 | 10.2 |
+| 85 | 19.1 | 14.7 | 10.0 |
+
+Line graph titled 'PC3' showing MSD(dB) vs PCB isolation(dB) for three antenna isolation levels: Ant ISO=10, Ant ISO=15, and Ant ISO=20. The graph shows that as PCB isolation increases from 65 dB to 85 dB, the MSD decreases for all antenna isolation levels. The lowest MSD is achieved with 85 dB PCB isolation and 20 dB antenna isolation, reaching approximately 10 dB.
+
+Figure 6.2.2.5-1 Cross band isolation analysis over better PCB isolation and antenna isolation
+
+Observation 6: It is observed that in terms of PC3, MSD due to cross band isolation of CA\_n1-n3 could be reduced to around 10dB with 85dB PCB isolation and 20dB antenna isolation, in contrast to [19.7]dB specified MSD.
+
+### 6.2.3 Evaluation from Nokia [10]
+
+#### 6.2.3.1 2nd UL harmonic for CA\_3-n78
+
+##### 6.2.3.1.1 MSD improvement by single RF component performance improvement
+
+There would be multiple ways to improve MSD due to UL harmonics. In order to show a specific example, we assume a following condition captured in Table 6.2.3.1.1-1.
+
+Table 6.2.3.1.1-1: MSD calculation where PA H2 is 35 dBc.
+
+| Table 1-1 | | | | Table 1-2 | | | |
+|-----------|-------------------------------------|--------|-------------|------------------------------------|-------------------------------|------------------------------------------|---------------------------------------------------------|
+| Parameter | PRX | DRX | | H2 level | PRX(dBm) | DRX(dBm) | |
+| Path 1 | B3 PA output power, dBm | 28 | 28 (1) | H2 at B3 PA | -7 | -7 (a) = (1) - (6) | |
+| | B3 Duplexer IL, dB | 2.5 | 2.5 (2) | H2 post B3 Duplexer | -37 | -37 (b) = (a) - (7) | |
+| | Harmonics Filter IL, dB | 0.5 | 0.5 (3) | H2 at B3 Duplexer H2 | -62 | -62 (c) = (1) - (8) | |
+| | HB Switch IL, dB | 0.7 | 0.7 (4) | H2 at Duplexer output | -37.0 | -37.0 (d) = (b) + (c) | |
+| | Triplexer IL, dB | 1.3 | 1.3 (5) | H2 post Harmonics Filter | -62.0 | -62.0 (e) = (d) - (9) | |
+| | B3 PA H2, dBc | 35 | 35 (6) | H2 at HB Switch | -75.7 | -75.7 (f) = (1) - (2) - (3) - (4) - (10) | |
+| | B3 Duplexer Rejection, dB | 30 | 30 (7) | H2 at HB Switch output | -61.8 | -61.8 (g) = (e) + (11) | |
+| | B3 Duplexer H2, dBc | 90 | 90 (8) | H2 post Triplexer | -76.8 | -76.8 (h) = (g) - (11) | |
+| | Harmonics Filter Rejection, dB | 25 | 25 (9) | H2 at DRX Antenna connector | | | (i) = (h) - (12) |
+| | HB Switch H2, dBc | 100 | 100 (10) | H2 at LNA from Tx to Rx chain path | -79.8 | | (j) = (i) - (13) - (14) * *Replace (j) with (h) for PRX |
+| | Triplexer Rejection&Isolation, dB | 15 | 15 (11) | Path 2 | H2 post PA | -7 | -7 (k) = (15) - (16) |
+| | Antenna Isolation, dB | | (12) | | H2 at LNA through PA | -77 | -77 (l) = (k) - (17) |
+| | UFB Switch IL, dB | 1 | 1 (13) | Path 3 | H2 post BB output | -20 | -20 (m) = (18) - (19) |
+| | B42 Saw Filter IL, dB | 2 | 2 (14) | | H2 at LNA through PA | -90 | -90 (n) = (m) - (20) |
+| Path 2 | B3 PA output power, dBm | 28 | 28 (15) | Table 1-3 | | | |
+| | B3 PA H2, dBc | 35 | 35 (16) | MSD | Composite H2 at LNA port, dBm | -75.0 | (o) = (j) + (l) + (n) |
+| | PA to LNA Isolation, dB | 70 | 70 (17) | | Composite noise, dBm | -75.0 | (p) |
+| Path 3 | BB output, dBm | 0 | 0 (18) | | MSD, dB | 23.3 | (q) |
+| | BB output H2, dBc | 20 | 20 (19) | | Combined MSD, dB | 24.3 | (r) |
+| | Isolation from BB output to LNA, dB | 70 | 70 (20) | | | | |
+| Common | Chip Noise Figure, dB | 4 | 4 (21) | | | | |
+| | Noise Floor (10M,52RB), dBm | -100.3 | -100.3 (22) | | | | |
+
+The derived MSD is almost the same as that of specified MSD, i.e., 23.9 dB. The further proposed improved MSD value by assuming PA H2 of 48 dBc and the MSD becomes 14.3 dB as shown in Table 6.2.3.1.1-2, which means 10 dB improvement is possible.
+
+Table 6.2.3.1.1-2: MSD calculation where PA H2 is 48 dBc.
+
+| Table 2-1 | | | | Table 2-2 | | | |
+|-----------|-------------------------------------|--------|--------|------------------------------------|-------------------------------|----------|---------------------------------------------------------|
+| Parameter | PRX | DRX | | H2 level | PRX(dBm) | DRX(dBm) | |
+| Path 1 | B3 PA output power, dBm | 28 | 28 | H2 at B3 PA | -20 | -20 | (a) = (1) - (6) |
+| | B3 Duplexer IL, dB | 2.5 | 2.5 | H2 post B3 Duplexer | -50 | -50 | (b) = (a) - (7) |
+| | Harmonics Filter IL, dB | 0.5 | 0.5 | H2 at B3 Duplexer H2 | -62 | -62 | (c) = (1) - (8) |
+| | HB Switch IL, dB | 0.7 | 0.7 | H2 at Duplexer output | -49.7 | -49.7 | (d) = (b) + (c) |
+| | Triplexer IL, dB | 1.3 | 1.3 | H2 post Harmonics Filter | -74.7 | -74.7 | (e) = (d) - (9) |
+| | B3 PA H2, dBc | 48 | 48 | H2 at HB Switch | -75.7 | -75.7 | (f) = (1) - (2) - (3) - (4) - (10) |
+| | B3 Duplexer Rejection, dB | 30 | 30 | H2 at HB Switch output | -72.2 | -72.2 | (g) = (e) + (f) |
+| | B3 Duplexer H2, dBc | 90 | 90 | H2 post Triplexer | -87.2 | | (h) = (g) - (11) |
+| | Harmonics Filter Rejection, dB | 25 | 25 | H2 at DRX Antenna connector | | | (i) = (h) - (12) |
+| | HB Switch H2, dBc | 100 | 100 | H2 at LNA from Tx to Rx chain path | -90.2 | | (j) = (i) - (13) - (14) * *Replace (j) with (h) for PRX |
+| | Triplexer Rejection&Isolation, dB | 15 | | Path 2 | | | (k) = (15) - (16) |
+| | Antenna Isolation, dB | | | H2 post PA | -20 | -20 | (l) = (k) - (17) |
+| | UHB Switch IL, dB | 1 | 1 | H2 at LNA through PA | -90 | -90 | (m) = (18) - (19) |
+| | B42 Saw Filter IL, dB | 2 | 2 | Path 3 | | | (n) = (m) - (20) |
+| Path 2 | B3 PA output power, dBm | 28 | 28 | Table 2-3 | | | |
+| | B3 PA H2, dBc | 48 | 48 | MSD | Composite H2 at LNA port, dBm | -85.3 | -86.9 (o) = (j) + (l) + (n) |
+| | PA to LNA Isolation, dB | 70 | 70 | | Composite noise, dBm | -85.2 | -86.7 (p) |
+| Path 3 | BB output, dBm | 0 | 0 | | MSD, dB | 15.1 | 13.6 (q) |
+| | BB output H2, dBc | 20 | 20 | | Combined MSD, dB | | 14.3 (r) |
+| | Isolation from BB output to LNA, dB | 70 | 70 | | | | |
+| Common | Chip Noise Figure, dB | 4 | 4 | | | | |
+| | Noise Floor (10M,52RB), dBm | -100.3 | -100.3 | | | | |
+
+**Observation 1: Feasibility of MSD improvement by PA H2 performance improvement was already proposed by a UE vendor in reference contribution, where it showed 10 dB improvement is possible.**
+
+Now the question is what if PA H2 with even better performance is used, whether the amount of MSD is further improved or not. The amount of the MSD improvement by PA H2 performance improvement **alone** starts to saturate when PA H2 approaches to 50 dBc and the MSD couldn't be lower than 11.4 dB even if PA H2 was infinite. This is because as the noise in Path 1 becomes lower thanks to PA H2 improvement, the noise from Path 3 appears as the next gating factor since PA H2 doesn't reduce noise in Path 3 at all. Hence, in order to improve MSD further, the noise from Path 3 must be also reduced.
+
+Next, we'll take a look at the amount of MSD improvement by assuming that isolations like PCB in Path 2 and Path 3 alone or PA H2 alone is improved in Figure 1 which shows how much MSD improvement can be obtained by improving PA H2 from 35 dBc to 75 dBc or isolation in Path 2 and Path 3 from 70 to 110 dB. It's noted that we don't have an intention to discuss if 75 dBc and 110 dB are feasible or not. They are just used to see the trend of MSD improvement by PA H2 or isolation improvement. Regarding MSD improvement vs PA H2 improvement, as mentioned before, the MSD improvement is saturated at around 50 dBc. With respect to MSD improvement vs isolation improvement, the amount of MSD improvement starts to saturate at around 90 dB and even if isolation was infinity, the MSD couldn't be lower than 9.4 dB.
+
+**Observation 2: Around 10 dB MSD improvement for CA\_n3-n78 2<sup>nd</sup> UL harmonics is feasible at least e.g., by PA H2 suppression of 48 dBc or isolation like PCB in Path 2 and Path 3 of 85 dB. Single RF component performance improvement alone, however, cannot achieve even better MSD like 20 dB since other gating factor(s) appears in one or two of the three Paths once noise in two or one of the three Paths is improved.**
+
+
+
+| Component performance improvement (dB) | MSD improvement by isolation improvement in Path 2/3 (dB) | MSD improvement by H2 PA suppression from 35 dBc (dB) |
+|----------------------------------------|-----------------------------------------------------------|-------------------------------------------------------|
+| 0 | 24.5 | 24.5 |
+| 5 | 20.5 | 20.5 |
+| 10 | 16.5 | 16.5 |
+| 15 | 12.5 | 12.5 |
+| 20 | 10.5 | 11.4 |
+| 25 | 9.8 | 11.4 |
+| 30 | 9.4 | 11.4 |
+| 35 | 9.4 | 11.4 |
+| 40 | 9.4 | 11.4 |
+
+Figure 6.2.3.1.1-1: MSD improvement by H2 PA suppression or isolation improvement by the same amount in Path 2&3. The graph shows Combined MSD (dB) on the y-axis (0 to 25) versus Component performance improvement (H2 PA suppression or isolation improvement in Path 2&3) (dB) on the x-axis (0 to 40). Two curves are plotted: a blue line for 'MSD improvement by isolation improvement in Path 2/3' and an orange line for 'MSD improvement by H2 PA suppression from 35 dBc'. Both curves show a linear decrease in MSD until they reach a plateau. The blue curve plateaus at approximately 9.4 dB, and the orange curve plateaus at approximately 11.4 dB.
+
+Figure 6.2.3.1.1-1: MSD improvement by H2 PA suppression or isolation improvement by the same amount in Path 2&3
+
+##### 6.2.3.1.2 Possible way to achieve 20 dB MSD improvement
+
+With consideration of Observation 2, we take into account multiple components performance improvement impact on combined MSD. Figure 2 shows relation between the combined MSD improvement and improvements due to combinations of PA H2 suppression in Path 1, antenna isolation in DRX Path 1 and an isolation in Path 2 and Path 3.
+
+![Figure 6.2.3.1.2-1: Impact of antenna isolation, PA H2 suppression and isolation in Path 2/3 on combined MSD. The graph plots Combined MSD [dB] on the y-axis (0 to 25) against Isolation improvement in Path 2&3 [dB] on the x-axis (0 to 30). Six data series are shown: 1) Ant Iso=10 dB with H2 suppression=35 dBc (blue line with circles), 2) Ant Iso=15 dB with H2 suppression=35 dBc (orange line with circles), 3) Ant Iso=20 dB with H2 suppression=35 dBc (grey line with circles), 4) Ant Iso=10 dB with H2 suppression=48 dBc (yellow line with circles), 5) Ant Iso=15 dB with H2 suppression=48 dBc (light blue line with circles), and 6) Ant Iso=20 dB with H2 suppression=48 dBc (green line with circles). All series show a decreasing trend as isolation improvement increases, with the 48 dBc H2 suppression series reaching lower MSD values faster than the 35 dBc series.](c531b0e7e06671c980f2ed0d753d2fbc_img.jpg)
+
+Figure 6.2.3.1.2-1: Impact of antenna isolation, PA H2 suppression and isolation in Path 2/3 on combined MSD. The graph plots Combined MSD [dB] on the y-axis (0 to 25) against Isolation improvement in Path 2&3 [dB] on the x-axis (0 to 30). Six data series are shown: 1) Ant Iso=10 dB with H2 suppression=35 dBc (blue line with circles), 2) Ant Iso=15 dB with H2 suppression=35 dBc (orange line with circles), 3) Ant Iso=20 dB with H2 suppression=35 dBc (grey line with circles), 4) Ant Iso=10 dB with H2 suppression=48 dBc (yellow line with circles), 5) Ant Iso=15 dB with H2 suppression=48 dBc (light blue line with circles), and 6) Ant Iso=20 dB with H2 suppression=48 dBc (green line with circles). All series show a decreasing trend as isolation improvement increases, with the 48 dBc H2 suppression series reaching lower MSD values faster than the 35 dBc series.
+
+**Figure 6.2.3.1.2-1: Impact of antenna isolation, PA H2 suppression and isolation in Path 2/3 on combined MSD**
+
+From Figure 6.2.3.1.2-1, in order to achieve around 20 dB MSD improvement, in case PA H2 suppression is 48 dBc, around 20 dB isolation improvement for Path 2 and Path 3 is needed. In case PA H2 suppression is 35 dBc, even if antenna isolation is 20 dB, 20 dB MSD is not possible (around 19 dB seems possible) under the assumption of Table 6.2.3.1.1-1.
+
+**Observation 3: In case of PA H2 suppression of 35 dB, 20 dB MSD improvement is not possible even if antenna isolation is 20 dB and isolation improvement of Path 2&3 was infinity if the other assumptions are the same as those in Table 6.2.3.1.1-1.**
+
+**Observation 4: In order to achieve 20 dB MSD improvement with PA H2 suppression of 48 dBc, around 25 dB isolation improvement, i.e., 95 dB isolation, for Path 2 &3 is required if the other assumptions are the same as those in Table 6.2.3.1.1-1.**
+
+Next, we discuss the impact of antenna isolation performance improvement on the combined MSD. One of the important aspects of antenna isolation in terms of MSD improvement is that the contribution of it to MSD improvement applies to only MSD for DRX under the UE architecture assumption in reference, which is achieved by reducing the composite H2 level at LNA (and hence MSD) in Path 1 for “DRX”. It’s noted that even if a UE architecture to enable a UE to obtain antenna isolation for PRX is assumed, the conclusion does not change that much for at least MSD due to UL harmonics since it only improves H2 levels at LNA for PRX and DRX for Path 1 only. Therefore, antenna isolation does not help improve combined MSD if DRX H2 level at LNA for Path 1 is lower than those for Path 2 and 3 and helps improve combined MSD a little if DRX H2 level at LNA for Path 1 is higher than those for Path 2 and 3, though the help can be around 5 dB at maximum with antenna isolation of 20 dB.
+
+**Observation 5: Antenna isolation improvement helps improve combined MSD more when DRX H2 levels at LNA for Paths 2 and 3 are even lower than DRX H2 level at LNA for Path 1 while the amount of maximum improvement by antenna isolation is around 5 dB with antenna isolation of 20 dB.**
+
+##### 6.2.3.1.3 20 dB MSD improvement with less isolation improvement in Path 2 &3
+
+In this sub-section, we discuss a way to mitigate the required isolation improvement in Path 2 and 3 by reducing respective MSDs (composite H2 levels) for PRX and DRX in a similar level from the conditions in Table 6.2.3.1.1-1. It is noted that in order to achieve 20 dB improved combined MSD, i.e., MSD = around 4 dB, H2 levels at LNA from
+
+each of the paths for both PRX and DRX must be lower than approximately -103 dBm, i.e., values in (j), (l) and (n) must be lower than or equal to -103 dBm except for DRX H2 level at (j) whose value is already -105.2 dBm. A specific example is summarized in Table 6.2.3.1.3-1, where combined MSD is 3.67 dB can be obtained.
+
+**Table 6.2.3.1.3-1: A way to 20 dB MSD improvement with less isolation improvement of Path 2&3 than Figure 2**
+
+| Table 1-1 | | | Table 1-2 | | | Table 1-3 | | |
+|-----------|-----------------------------------|-------------|------------------------------------|-------------------------------|---------------|---------------------------------------------------------|-----------------------|------------------|
+| Parameter | PRX | DRX | H2 level | PRX(dBm) | DRX(dBm) | | | |
+| Path 1 | B3 PA output power, dBm | 28 (1) | H2 at B3 PA | -20 | -20 | (a) = (1) - (6) | | |
+| | B3 Duplexer IL, dB | 2.5 (2) | H2 post B3 Duplexer | -50 | -50 | (b) = (a) - (7) | | |
+| | Harmonics Filter IL, dB | 0.5 (3) | H2 at B3 Duplexer H2 | -62 | -62 | (c) = (1) - (8) | | |
+| | HB Switch IL, dB | 0.7 (4) | <b>H2 at Duplexer output</b> | <b>-49.7</b> | <b>-49.7</b> | (d) = (b) + (c) | | |
+| | Triplexer IL, dB | 1.3 (5) | H2 post Harmonics Filter | -82.7 | -82.7 | (e) = (d) - (9) | | |
+| | B3 PA H2, dBc | 48 (6) | H2 at HB Switch | -83.7 | -83.7 | (f) = (1) - (2) - (3) - (4) - (10) | | |
+| | B3 Duplexer Rejection, dB | 30 (7) | <b>H2 at HB Switch output</b> | <b>-80.2</b> | <b>-80.2</b> | (g) = (e) + (f) | | |
+| | B3 Duplexer H2, dBc | 90 (8) | H2 post Triplexer | -100.2 | -100.2 | (h) = (g) - (11) | | |
+| | Harmonics Filter Rejection, dB | 33 (9) | H2 at DRX Antenna connector | | -110.2 | (i) = (h) - (12) | | |
+| | HB Switch H2, dBc | 108 (10) | H2 at LNA from Tx to Rx chain path | <b>-103.2</b> | <b>-113.2</b> | (j) = (i) - (13) - (14) * *Replace (i) with (h) for PRX | | |
+| | Triplexer Rejection&Isolation, dB | 20 (11) | Path 2 | H2 post PA | -20 | -20 | (k) = (15) - (16) | (l) = (k) - (17) |
+| | Antenna Isolation, dB | 10 (12) | | | | | | |
+| | UHB Switch IL, dB | 1 (13) | Path 3 | H2 at LNA through PA | -103 | -103 | (m) = (18) | |
+| | B42 Saw Filter IL, dB | 2 (14) | | | | | | |
+| Path 2 | B3 PA output power, dBm | 28 (15) | MSD | Composite H2 at LNA port, dBm | -98.3 | -99.8 | (o) = (j) + (l) + (n) | |
+| | B3 PA H2, dBc | 48 (16) | | | | | | |
+| | PA to LNA Isolation, dB | 83 (17) | | | | | | |
+| | Single Chip DA to LNA, dBm | -103 (18) | | | | | | |
+| Path 3 | Single Chip DA to LNA, dBm | -103 (18) | | Composite noise, dBm | -96.2 | -97.0 | (p) | |
+| | Chip Noise Figure, dB | 4 (19) | | MSD, dB | 4.1 | 3.3 | (q) | |
+| Common | Noise Floor (10M,52RB), dBm | -100.3 (20) | | Combined MSD, dB | | 3.665 | (r) | |
+
+**Observation 6: If harmonic filter rejection, HB switch H2 and Triplexer Rejection towards H2 are improved by 8 dB, 8 dB and 5 dB, respectively, all the LNA H2 levels at the three Paths are almost equally lower than or equal to -103 dBm, as shown in Table 3, the required isolation of Path 2 & 3 can be reduced to 83 dB from 95 dB.**
+
+##### 6.2.3.1.4 How to achieve MSD = 0 dB
+
+It is not hard to anticipate that achieving MSD improvement of 24 dB, i.e., MSD = 0 dB, even more challenging than achieving that of 20 dB. When MSD improvement of 20 dB is achieved, H2 levels from all the paths for PRX and DRX must be already similar levels or composite H2 level for DRX is even smaller than that for PRX. The former means that even if a component performance is improved and one or some of H2 levels at LNA at Path 1, 2 and/or 3 for PRX and/or DRX are improved, the other H2 levels stay as a gating factor. The latter means that the composite level for PRX must be improved. In any case, multiple components performance must be improved, but cost for MSD improvement becomes higher. For more specific, Figure 3 shows relation between respective H2 levels improvement and combined MSD assuming that H2 levels from the three Paths are improved in the same amount from the condition shown in Table 6.2.3.2-1. For example, 1 dB in the horizontal line means -116 (-115 dBm - 1 dB) dBm for Path 1 DRX and -106 (-105 dBm - 1 dB) dBm for Path 1/2/3 PRX and Path 2/3 DRX and so on.
+
+![Line graph showing Combined MSD [dB] vs Respective H2 levels improvement from -115 for Path 1 DRX or -105 dBm for all others [dB]. The y-axis ranges from 0 to 3 dB, and the x-axis ranges from 0 to 15 dB. A blue line with circular markers, labeled 'MSD', starts at approximately 2.7 dB at 0 dB improvement and decreases steadily to about 0.2 dB at 15 dB improvement.](f0cab3794e09131ff0a91cabe163ca16_img.jpg)
+
+| Respective H2 levels improvement [dB] | Combined MSD [dB] |
+|---------------------------------------|-------------------|
+| 0 | 2.7 |
+| 1 | 2.3 |
+| 2 | 1.9 |
+| 3 | 1.6 |
+| 4 | 1.3 |
+| 5 | 1.1 |
+| 6 | 0.9 |
+| 7 | 0.7 |
+| 8 | 0.6 |
+| 9 | 0.5 |
+| 10 | 0.4 |
+| 11 | 0.3 |
+| 12 | 0.25 |
+| 13 | 0.2 |
+| 14 | 0.15 |
+| 15 | 0.1 |
+
+Line graph showing Combined MSD [dB] vs Respective H2 levels improvement from -115 for Path 1 DRX or -105 dBm for all others [dB]. The y-axis ranges from 0 to 3 dB, and the x-axis ranges from 0 to 15 dB. A blue line with circular markers, labeled 'MSD', starts at approximately 2.7 dB at 0 dB improvement and decreases steadily to about 0.2 dB at 15 dB improvement.
+
+**Figure 6.2.3.1.4-1: Required LNA PRX or DRX H2 levels for all the three path**
+
+Figure 6.2.3.1.4-1 says that to improve MSD from 1 dB to almost 0 dB, the respective H2 levels must be improved by at least 10 dB, which means that an additional 10 dB isolation improvement for path 2 and 3 is needed and H2 levels in path 1 somehow need to be improved by 10 dB, but the options are very limited since triplexer would have challenges in having more attention than 20 dB so that RF components performance prior to the triplexer must be improved.
+
+**Observation 7: Theoretically it is not impossible to achieve MSD = 0dB for CA\_n3-n78 for 2<sup>nd</sup> UL harmonic. However, as MSD approaches 0 dB, it requires more cost, i.e., components performance improvement compared to the cost to improve MSD by 20 dB.**
+
+#### 6.2.3.2 2nd order harmonic mixing for CA\_n3-n78
+
+Regarding CA\_n3-n77, MSD for this CA band combination has not been specified in 38.101-1 while that for corresponding EN-DC, MSD is defined in 38.101-3. The values for MSD for EN-DC are extracted from Table 7.3B.2.3.2-1 in 38.101-3 as follows.
+
+**Table 6.2.3.2-1: Extract from Table 7.3B.2.3.2-1 in TS38.101-3**
+
+| UL band | DL band | E-UTRA or NR Band / Channel bandwidth of the affected DL band / MSD | | | | | | | | | | |
+|---------|---------|---------------------------------------------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|
+| | | 5 MHz (dB) | 10 MHz (dB) | 15 MHz (dB) | 20 MHz (dB) | 25 MHz (dB) | 40 MHz (dB) | 50 MHz (dB) | 60 MHz (dB) | 80 MHz (dB) | 90 MHz (dB) | 100 MHz (dB) |
+| n77 | 3 | 5.7 | 4.0 | 3.0 | 2.7 | | | | | | | |
+| n78 | 3 | 5.7 | 4.0 | 3.0 | 2.7 | | | | | | | |
+
+A technical analysis to justify MSD = 0 dB for CA\_n3-n78 was submitted in a reference contribution, where Tx power at LNA input are summarized in Table 5, where Direct Signal Path corresponds to Path 1 in Section 6.2.3.1.1 and PCB Coupling Path corresponds to Path 2 in Section 6.2.3.1.1, respectively. It should be noted that in case of analysis for harmonic mixing, consideration of Path 3 in Section 6.2.3.1.1 is not necessary since the BB output power is always even lower than that PA output power in Path 2 by PA gain as far as the same PCB isolation is assumed. The contribution shared the fact that there is a mixer with the spur rejection of about 66 dBc for mixing with 2LO and it enables UEs to have MSD = 0 dB. Moreover, the reference contribution implies that MSD = 0 dB for CA\_n3-n78 can be achieved with PCB isolation of 84 (70 dB + 14 dB) dB instead of using the mixer with 66 dBc rejection.
+
+**Table 6.2.3.2-2: Extract of Table 1 from [4]**
+
+| Direct Signal Path | | | | → Corresponding Path 1 in Section 2.1 |
+|-----------------------------|-------|-----------|-----|---------------------------------------|
+| Parameter | Main | Diversity | | |
+| Tx power at antenna port | 23 | 13 | dBm | |
+| Tx power at duplexer output | 8 | -2 | dBm | |
+| Tx power at LNA input | -57 | -67 | dBm | |
+| PCB Coupling Path | | | | → Corresponding Path 2 in Section 2.1 |
+| Parameter | Main | Diversity | | |
+| Tx power at HB PA output | 27 | 27 | dBm | |
+| Tx power at LNA input | -43 | -43 | dBm | |
+| Combined | | | | |
+| Tx power at LNA input | -42.8 | -43 | dBm | |
+
+As can be seen in Table 6.2.3.2-2, RF components like antenna isolation, filter isolations in Path 1 cannot contribute to improving combined MSD since noise level from Path 2 is higher by 14 dB for PRX and 24 dB for DRX until the noise level in Path 2 approaches close to that in Path 1. 14 dB noise reduction for Path 2 means that PCB isolation must be improved from 70 dB to 84 dB. However, as can be seen in Figure 4, when PCB isolation is 85 dB, combined MSD itself is almost zero dB (Combined MSD is below 1 dB even with mixer spur rejection is 45 dBc) so that there is no room for antenna isolation to contribute to the improvement.
+
+
+
+Figure 6.2.3.2-1: MSD relation b/w PCB isolation and Mixer spur rejection for 2nd harmonic mixing. The graph plots Combined MSD (dB) on the y-axis (0 to 7) against Mixer spur rejection, dBc on the x-axis (45 to 65). Four curves are shown for different PCB isolation levels: 70 dB (blue), 75 dB (orange), 80 dB (grey), and 85 dB (yellow). All curves show a decreasing trend as mixer spur rejection increases. Horizontal dashed lines are present at 4 dB (red), 3 dB (orange), 2 dB (grey), and 1 dB (yellow).
+
+**Figure 6.2.3.2-1: MSD relation b/w PCB isolation and Mixer spur rejection for 2nd harmonic mixing**
+
+Figure 6.2.3.2-1 also shares the information that combined MSD is almost the same if the same amount of PCB isolation improvement or Mixer spur rejection improvement is achieved, though Mixer spur rejection improvement can give a little bit larger MSD improvement by PCB isolation improvement (see e.g., the top red horizontal dashed line. A point where PCB isolation of 70 dB line has 50 dBc(45+5) mixer spur rejection is lower than a point where PCB isolation of 75 dB(70+5) line has 45 dBc mixer spur rejection). This is theoretically valid since mixer spur rejection applies to the composite noise consisting of Path 1 and Path 2 while PCB isolation only improves noise from Path 2. Finally, although MSD = 0 dB is possible, the cost performance becomes worse as the MSD approaches 0 dB. For instance, in order to achieve 5 dB MSD improvement, i.e., MSD = 2 dB, PCB isolation, mixer spur rejection or the sum of both requires around from 8 dB to 12 dB improvement while to achieve 6 dB MSD improvement, i.e., MSD = 1 dB, PCB isolation, mixer spur rejection or the sum of both requires around 12 to 15 dB improvement.
+
+**Observation 8: MSD of 0 dB for CA\_n3-n78 harmonic mixing is feasible by PCB isolation improvement, e.g., 84 dB, mixer spur rejection improvement, e.g., 66 dBc or combination of the two RF components performance improvement, e.g., PCB isolation is 75 dB and mixer spur rejection is 60 dBc. Antenna isolation improvement doesn't help improve MSD for 2<sup>nd</sup> harmonic mixing for CA\_n3-n78.**
+
+#### 6.2.3.3 IMD2 for CA\_n3-n78
+
+MSD due to IMD2 for CA\_n3-n78 were discussed intensively. Table 6.2.3.3-1 is a summary of IMD2 analysis from a reference, where yellow cells are affected by PCB isolation, aqua cells are affected by antenna isolation, green cells are affected by PCB isolation as well as antenna isolation. Hence, under the conditions in Table 6.2.3.3-1, it is expected that if only PCB isolation is improved, MSD improvement would start to saturate when the PCB isolation approaches to approximately 80 dB, since IMD2 from antenna switch and diplexer stay at -75 dBm in PRX. Antenna isolation improvement can contribute to reduce IMD2 in DRX so that the combined MSD can be improved accordingly. Hence, if both PCB isolation and antenna isolation are improved, the MSD can be further improved. However, even if PCB isolation as well as antenna isolation are improved, IMD2 from antenna switch and diplexer stay at -75 dBm in PRX. Hence, in order to reduce the combined MSD significantly, IP2 for these RF components needs to be improved.
+
+**Table 6.2.3.3-1: IMD2 analysis for CA\_n3-n78 from [5]**
+
+| parameters | value |
+|-------------------------------------------------------------------|-------|
+| RF front end IL for n3 and n78, dB | 3 |
+| PA output for n3 and n78, dBm | 23 |
+| PA gain for n3 and n78, dB | 30 |
+| n3 Tx band rejection at Rx band, dB | 50 |
+| n3 filter rejection over n78, dB | 38 |
+| Diplexer Rejection&Isolation, dB | 20 |
+| PA (out) to PA (in) (PCB isolation (PA forward mixing)) | 65 |
+| PA (out) to PA (out) (PCB isolation (PA reverse mixing)) | 65 |
+| LNA (in) to PA (out) (PCB isolation (n78 PA leakage into B3 LNA)) | 65 |
+| LNA (in) to PA (out) (Cross-band (n78 filter + diplexer)) | 50 |
+| Antenna Isolation, dB | 10 |
+| IP2: Ant. Switch, dBm | 115 |
+| IP2: Diplexer, dBm | 115 |
+| IP2: n3 Duplexer/filter, dBm | 100 |
+| IP2: PA Forward, dBm | 27 |
+| IP2: PA Reversed, dBm | 38 |
+| IP2: LNA, dBm | 6 |
+| Thermal noise, dBm | -93 |
+
+
+
+| PRX | P <sub>a3</sub> (dBm) | P <sub>a78</sub> (dBm) | IMD2(dBm) |
+|-------------------------------|-----------------------|------------------------|-----------|
+| Antenna Switch | 20 | 20 | -75 |
+| Diplexer | 20 | 20 | -75 |
+| n3 Duplexer | 23 | -27 | -104 |
+| n3 PA Forward | 23.0 | -12.0 | -63.0 |
+| n78 PA Forward | -12.0 | 23.0 | -63.0 |
+| n3 PA Reversed | 23 | -42 | -104.0 |
+| n78 PA Reversed | -42.0 | 23.0 | -104.0 |
+| Net except for IMD2 at n3 LNA | | | -59.7 |
+| n3 LNA | -27.0 | -42.0 | -72.0 |
+| Total IMD | | | -59.5 |
+| Total IMD after CF | | | -59.9 |
+
+
+
+| DRX | P <sub>a3</sub> (dBm) | P <sub>a78</sub> (dBm) | IMD2(dBm) |
+|---------------------|-----------------------|------------------------|-----------|
+| From Main Path | | | -69.9 |
+| Antenna Switch | 10 | 10 | -95 |
+| Diplexer | 10 | 10 | -95 |
+| n3 filter | -10 | 10 | -100 |
+| n3 LNA (radiative) | -28.0 | -48.0 | -79.0 |
+| n3 LNA (conductive) | -42.0 | -42.0 | -87.0 |
+| Total IMD | | | -69.3 |
+| Total IMD after CF | | | -69.7 |
+
+
+
+| | PRX | DRX |
+|------------------|-------|-------|
+| Total noise, dBm | -59.9 | -69.7 |
+| MSD, dB | 33.1 | 23.3 |
+| Combined MSD, dB | 25.9 | |
+
+![Figure 6.2.3.3-1: A line graph showing Combined MSD [dB] on the y-axis (0 to 25) versus PCB [dB] on the x-axis (65 to 100). Four data series are plotted: 1) Blue line with circles: Ant Iso=10 dB, AS and Diplexer IP2=115 dBm. 2) Grey line with circles: Ant Iso=20 dB, AS and Diplexer IP2=115 dBm. 3) Yellow line with circles: Ant Iso=10 dB, AS and Diplexer IP2=125 dBm. 4) Green line with circles: Ant Iso=20 dB, AS and Diplexer IP2=125 dBm. All series show a downward trend as PCB isolation increases, with the green series reaching the lowest MSD of approximately 4 dB at 100 dB PCB isolation.](06ccd604e7eac77c7a5a323b6a913f15_img.jpg)
+
+Figure 6.2.3.3-1: A line graph showing Combined MSD [dB] on the y-axis (0 to 25) versus PCB [dB] on the x-axis (65 to 100). Four data series are plotted: 1) Blue line with circles: Ant Iso=10 dB, AS and Diplexer IP2=115 dBm. 2) Grey line with circles: Ant Iso=20 dB, AS and Diplexer IP2=115 dBm. 3) Yellow line with circles: Ant Iso=10 dB, AS and Diplexer IP2=125 dBm. 4) Green line with circles: Ant Iso=20 dB, AS and Diplexer IP2=125 dBm. All series show a downward trend as PCB isolation increases, with the green series reaching the lowest MSD of approximately 4 dB at 100 dB PCB isolation.
+
+Figure 6.2.3.3-1: relation b/w IMD, PCB isolation, Ant Iso and IP2 of Antenna switch & Diplexer
+
+From Figure 6.2.3.3-1, it can be seen that the around 20 dB MSD improvement is possible if IP2 for diplexer and Antenna switch are 125 dBm, PCB isolation is 80 dB and antenna isolation is 20 dB under the conditions of Table 6.2.3.3-2. Theoretically MSD of 0 dB is possible while the cost is significantly high but the gain = “the amount of MSD improvement”/“the amount of RF component improvement” becomes less and less.
+
+**Observation 9:** Around 10 dB MSD improvement of IMD2 for CA\_n3-n78 is possible if antenna isolation is around 20 dB or PCB isolation is around 80 dB. Around 20 dB improvement is also possible, if IP2 of antenna switch as well as diplexer is around 125 dBm. Further MSD improvement is also possible while the cost and performance = “the amount of MSD improvement”/“the amount of RF component performance improvement” becomes less and less.
+
+#### 6.2.3.4 MSD improvement and MSD types
+
+The below Figure 6.2.3.4-1 shows relation between the amount of the MSD improvements and the amount of PCB isolation improvement for different MSD types. It should be noted that assumed UE RF architecture is basically the same across the MSD evaluations for MSD types while some device performance assumptions, e.g., RF front end loss are different across MSD types so that this can be used only as a guide.
+
+![Figure 6.2.3.4-1: A line graph showing 'The amount of MSD improvement[dB]' on the y-axis (0 to 30) versus 'PCB Iso [dB]' on the x-axis (65 to 100). Four data series are plotted: IMD2 (blue line with circles), 2nd UL harmonics: PA H2 is 35 dBc (orange line with circles), 2nd UL harmonics: PA H2 is 48 dBc (grey line with circles), and 2nd harmonic mixing: Spur rejection=45 dBc (yellow line with circles). All series show an upward trend as PCB isolation increases, with the grey line reaching the highest improvement of approximately 25 dB at 100 dB PCB isolation.](a1545557e366b6302109d13360b199c3_img.jpg)
+
+Figure 6.2.3.4-1: A line graph showing 'The amount of MSD improvement[dB]' on the y-axis (0 to 30) versus 'PCB Iso [dB]' on the x-axis (65 to 100). Four data series are plotted: IMD2 (blue line with circles), 2nd UL harmonics: PA H2 is 35 dBc (orange line with circles), 2nd UL harmonics: PA H2 is 48 dBc (grey line with circles), and 2nd harmonic mixing: Spur rejection=45 dBc (yellow line with circles). All series show an upward trend as PCB isolation increases, with the grey line reaching the highest improvement of approximately 25 dB at 100 dB PCB isolation.
+
+**Figure 6.2.3.4-1: The amount of MSD improvement vs PCB isolation improvement**
+
+From the Figure 6.2.3.4-1, all the three MSD types has a similar trend when PCB isolation is roughly up to 75 dB. Then, gradually, 2<sup>nd</sup> UL harmonic starts to show a different trend than the other 2<sup>nd</sup> harmonic mixing and IMD2. Moreover, grey line is the case that PCB isolation as well as PA H2 improvement for 2nd UL harmonic are considered. The amount of the MSD improvement is quite different from the other MSD types as well as the same MSD type whose PA H2 performance is 35 dBc. Moreover, given that it is not always the case that UE vendors will always use PCB isolation alone to improve MSD, the amount of MSD improvement can be very different from MSD types to types.
+
+**Observation 10: The amount of the MSD improvement is not always the same or similar across MSD types even if one common RF component performance improvement is considered. Provided that it is not always the case that UE vendors will always use one single RF component performance improvement, e.g., only PCB isolation, to improve MSD, the amount of MSD improvement can be very different from MSD types to types.**
+
+### 6.2.4 Evaluation from Qualcomm [11]
+
+For the band combination CA\_n1-n3-n78 it is seen that CA\_n3-n78 has IMD2, IMD4 and HD2 impairments.
+
+Based on typical numbers Table 6.2.4-1 gives an analysis for IMD2 for CA-n3\_n78 where the IMD2 product of n78 Tx and n3 Tx fall into n3 Rx.
+
+**Table 6.2.4-1: CA-n3\_n78 budget for IMD2**
+
+| | | | | | |
+|--------------------------|-------|-----|--|--|--|
+| Ant-Ant Isolation | 10 | dB | | | |
+| PCB Isolation | 70 | dB | | | |
+| Power class | PC2 | | | | |
+| n77 PA output power | 30 | dBm | | | |
+| IMD2 at n78 PA output | -71 | dBm | | | |
+| Diplexer attenuation | 15 | dB | | | |
+| Total IMD2 @n78 ANT | -86.0 | dBm | | | |
+| Total IMD2 @n3 ANT | -96.0 | dBm | | | |
+| n77 jammer @ n3 PA input | -40.0 | dBm | | | |
+| IMD2 at n3 PA output | -65.0 | dBm | | | |
+| Post PA IL | 2.0 | dB | | | |
+| Total IMD2 @n3 ANT | -63.0 | dBm | | | |
+
+| | | | | | |
+|----------------------------------|-------|-----|--|-------------|-----|
+| PRX n3 path | | | | DRX n3 path | |
+| | | | | | |
+| Mixer IIP2 | 72.0 | dB | | 72.0 | dB |
+| LNA IIP2 | 30.0 | dBm | | 30.0 | dBm |
+| Noise from mixer IIP2 distortion | -96.0 | dBm | | -96.0 | dBm |
+| Rx IMD @ ANT | -94.0 | dBm | | -94.0 | dBm |
+| Total distortion @ n3 ANT | -63.0 | dBm | | -73.0 | dBm |
+| Reference sensitivity | -98.0 | dBm | | -98.0 | dBm |
+| Thermal noise | -94.0 | dBm | | -94.0 | dBm |
+| total noise @ n3 ANT | -63.0 | | | -72.9 | dBm |
+| MRC Sensitivity | -72.4 | | | | dBm |
+| MSD | 25.6 | | | | dB |
+
+Based on the above numbers it is seen that for improvement in PCB and antenna isolation the MSD due to IMD2 behaves as indicated in table 6.2.4-2.
+
+**Table 6.2.4-2: CA-n3\_n78 MSD for IMD2 as a function of PCB and antenna isolation**
+
+| Ant (dB) | ISO | PCB (dB) | ISO | MSD (dB) |
+|----------|-----|----------|-----|----------|
+| 10 | | 70 | | 25.6 |
+| 10 | | 80 | | 17.3 |
+| 10 | | 90 | | 13.0 |
+| 20 | | 70 | | 24.6 |
+| 20 | | 80 | | 14.4 |
+| 20 | | 90 | | 8.1 |
+
+From the results in table 6.2.4-2 it can be clearly seen that the MSD for IMD2 can be reduced by increasing both the PCB and antenna isolations.
+
+**Observation 1: For CA-n3\_n78 the MSD due to IMD2 where n78 Tx and n3 Tx mix and fall into n3 Rx shows the following behaviour with PCB and antenna isolation:**
+
+| Ant (dB) | ISO | PCB (dB) | ISO | MSD (dB) |
+|----------|-----|----------|-----|----------|
+| 10 | | 70 | | 25.6 |
+| 10 | | 80 | | 17.3 |
+| 10 | | 90 | | 13.0 |
+| 20 | | 70 | | 25.6 |
+| 20 | | 80 | | 14.4 |
+| 20 | | 90 | | 8.1 |
+
+Similar analysis for CA-n3\_n78 for IMD4 where the IMD4 of n78 Tx and 3\*n3 Tx falls into n3 Rx shows the following behaviour of MSD with PCB and antenna isolation given in table 6.2.4-3.
+
+**Table 6.2.4-3: CA-n3\_n78 MSD for IMD4 as a function of PCB and antenna isolations**
+
+| Ant (dB) | ISO | PCB (dB) | ISO | MSD (dB) |
+|----------|-----|----------|-----|----------|
+| | | | | |
+| 10 | | 70 | | 9.5 |
+| 10 | | 80 | | 5.5 |
+| 10 | | 90 | | 4.0 |
+| 20 | | 70 | | 4.8 |
+| 20 | | 80 | | 3.9 |
+| 20 | | 90 | | 2.7 |
+
+From the results in table 6.2.4-3 it is seen that the MSD for IMD4 can be reduced by increasing both the PCB and antenna isolations.
+
+**Observation 2: For CA-n3\_n78 the MSD due to IMD4 where n78 Tx and 3\*n3 Tx mix and fall into n3 Rx shows the following behaviour with PCB and antenna isolation:**
+
+| Ant (dB) | ISO | PCB (dB) | ISO | MSD (dB) |
+|----------|-----|----------|-----|----------|
+| 10 | | 70 | | 9.5 |
+| 10 | | 80 | | 5.5 |
+| 10 | | 90 | | 4.0 |
+| 20 | | 70 | | 4.8 |
+| 20 | | 80 | | 3.9 |
+| 20 | | 90 | | 2.7 |
+
+For CA-n3\_n78 for the 2<sup>nd</sup> harmonic of n3 Tx falling into n78 Rx we have the following typical budget
+
+**Table 6.2.4-4: CA-n3\_n78 budget for HD2**
+
+| | | | | | |
+|---------------------------|-------|--|-----|--------------|-----|
+| Band | n3 | | | | |
+| HD order | 2 | | | | |
+| Rx BW | 100 | | | | MHz |
+| PC | 2 | | | | |
+| Ant-Ant Isolation | 10 | | | | dB |
+| PCB Isolation | 70 | | | | dB |
+| n3 PA HD2 | -6 | | | | dBm |
+| HD2 filtering in Tx chain | 48 | | | | dB |
+| Triplexer attenuation | 25 | | | | dB |
+| n3 HD2 @Ant | -79 | | | | dB |
+| PRX n78 path | | | | DRX n78 path | |
+| Rx FE loss | 3 | | dB | 3 | dB |
+| Total HD pwr at Ant input | -72.9 | | dBm | -72.9 | dBm |
+| Thermal noise @RX Ant | -81.5 | | dBm | -81.5 | dBm |
+| total noise @ n3 ANT | -72.3 | | dBm | -72.3 | dBm |
+| Reference sensitivity | -85.5 | | dBm | -85.5 | dBm |
+| MRC Sensitivity | -73.6 | | | | dBm |
+| MSD | 11.9 | | | | dB |
+
+It is seen that for improvement in PCB and antenna isolation the MSD due to HD2 behaves as indicated in table 6.2.4-5.
+
+**Table 6.2.4-5: CA-n3\_n78 MSD for HD2 as a function of PCB and antenna isolation**
+
+| PCB (dB) | ISO | Ant (dB) | ISO | MSD (dB) |
+|----------|-----|----------|-----|----------|
+| 70 | | 10 | | 11.9 |
+| 80 | | 10 | | 4.4 |
+| 90 | | 10 | | 1.7 |
+| 70 | | 20 | | 11.8 |
+| 80 | | 20 | | 3.9 |
+| 90 | | 20 | | 0.7 |
+
+**Observation 3: For CA-n3\_n78 the MSD due to HD2 where the second harmonic of n3 falls into n78 Rx shows the following behaviour with PCB and antenna isolation:**
+
+| PCB (dB) | ISO | Ant (dB) | ISO | MSD (dB) |
+|----------|-----|----------|-----|----------|
+| 70 | | 10 | | 11.9 |
+
+| | | |
+|----|----|------|
+| 80 | 10 | 4.4 |
+| 90 | 10 | 1.7 |
+| 70 | 20 | 11.8 |
+| 80 | 20 | 3.9 |
+| 90 | 20 | 0.7 |
+
+For CA-n41\_n77 where cross band isolation is an issue with Tx noise from n41 falling into n77 and vis-a-versa. The below table shows the budget for n77 Tx noise falling into n41.
+
+**Table 6.2.4-6: CA-n41\_n77 budget for cross band isolation with n41 victim**
+
+| | | | | | |
+|--------------------------------|--------|--------|--|------------------|-----|
+| Aggressor band | n77 | PC3 | | | |
+| Victim band | n41 | | | | |
+| Transceiver noise at PA output | -154.5 | dBm/Hz | | | |
+| PA output noise | -150 | dBm/Hz | | | |
+| Total noise at PA output | -148.7 | dBm/Hz | | | |
+| Antenna iso | 15 | dB | | | |
+| Tx noise @Rx | -163.7 | dBm/Hz | | | |
+| PRX path for n41 | | | | DRX path for n41 | |
+| DL BW | 10.0 | MHz | | 10 | MHz |
+| Rx thermal noise @ LNA input | -91.1 | dBm | | -91.1 | dBm |
+| DAC images at Tx output | -91.7 | dBm | | -91.7 | dBm |
+| DAC images at RX input | -106.7 | dBm | | -106.7 | dBm |
+| Total interference @ Rx | -93.5 | dBm | | -93.5 | dBm |
+| Total noise @ Rx | -89.1 | dBm | | -89.1 | dBm |
+| n41 Reference sensitivity | -95.1 | dBm | | | |
+| MRC sensitivity | -91.8 | dBm | | | |
+| MSD | 3.3 | dBm | | | |
+
+The MSD in the current specifications for this combination is only 4.5dB and currently with 15 dB of antenna isolation the MSD is 3.3 dB. Therefore, even with large increases in antenna isolation the maximum MSD reduction that can be achieved is only a further 3.3 dB. The below table gives the variation in MSD with antenna isolation. As the lower MSD feature is meant to address band combinations with large MSDs we think that the low MSD of this band combination does not make it a candidate for this feature.
+
+**Table 6.2.4-7: CA-n41\_n77 variation of MSD with antenna isolation for n41 victim**
+
+| Ant ISO (dB) | MSD (dB) |
+|--------------|----------|
+| 15 | 3.3 |
+| 20 | 1.3 |
+| 25 | 0.5 |
+
+**Observation 4: For CA-n41\_n77 the MSD due to cross band isolation where n77 Tx noise falls into n41 Rx the following behaviour is observed with antenna isolation:**
+
+| Ant ISO (dB) | MSD (dB) |
+|--------------|----------|
+| 15 | 3.3 |
+| 20 | 1.3 |
+| 25 | 0.5 |
+
+In our opinion the low MSD for this band combination does not make it a candidate for the low MSD feature
+
+For CA-n28\_n40 for the 3<sup>rd</sup> RX LO harmonic of n28 mixing with n40 Tx and falling in the n28 Rx band we can have the following typical budget.
+
+**Table 6.2.4-8: CA-n28\_n40 budget for Rx LO harmonic mixing with n40 Tx falling into n28 Rx**
+
+| | | | | |
+|-----------------------------------------------------------|-------|-----|-------|-----|
+| n40 Tx output power at ANT | 23 | dBm | | |
+| n40 Tx FE loss | 3 | dB | | |
+| Antenna isolation | 10 | dB | | |
+| n28 Duplexer attenuation for n40 Tx | 15 | dB | | |
+| n28 FE attenuation for n40 Tx | 50 | dB | | |
+| n28 FE gain | 15 | dB | | |
+| PCB isolation From n40 PA output to n28 transceiver input | 70 | dB | | |
+| PRX | | | DRX | |
+| n28 RX BW | 10 | MHz | 10 | MHz |
+| Total interferer at n28 RX input | -43.4 | dBm | -43.4 | dBm |
+| 3LO harmonic rejection | 10 | dB | 10 | dB |
+| Total interference at ANT | -68.4 | dBm | -68.4 | dBm |
+| Thermal noise | -91.5 | dBm | -91.5 | dBm |
+| Total noise | -68.3 | dBm | -68.3 | dBm |
+| Sensitivity | -95.5 | dBm | | |
+| MRC sensitivity | -69.4 | | | |
+| MSD | 26.1 | dB | | |
+
+It is seen that for improvement in PCB and antenna isolation the MSD behaves as indicated in table 6.2.4-8.
+
+**Table 6.2.4-9: CA-n28\_n40 MSD for Rx LO harmonic falling into n28 Rx as a function of PCB and antenna isolation**
+
+| PCB iso (dB) | Ant iso(dB) | MSD (dB) |
+|--------------|-------------|----------|
+| 70 | 10 | 26.1 |
+| 80 | 10 | 19.7 |
+| 90 | 10 | 17.8 |
+| 70 | 20 | 25.6 |
+| 80 | 20 | 16.2 |
+| 90 | 20 | 10.1 |
+
+From the above table it is observed that the MSD is dominated by the PCB isolation and that the antenna isolation has very little impact.
+
+**Observation 5: For CA-n28\_n40 the MSD due to 3<sup>rd</sup> RX LO harmonic of n28 mixing with n40 Tx and falling into 28 Rx the following behaviour is observed with PCB and antenna isolation:**
+
+| PCB iso (dB) | Ant iso(dB) | MSD (dB) |
+|--------------|-------------|----------|
+| 70 | 10 | 26.1 |
+| 80 | 10 | 19.7 |
+| 90 | 10 | 17.8 |
+
+| | | |
+|----|----|------|
+| 70 | 20 | 25.6 |
+| 80 | 20 | 16.2 |
+| 90 | 20 | 10.1 |
+
+For most band combinations that have large MSDs an increase in the PCB and/or antenna isolation will enable a reduction in MSD.
+
+**Observation 6: The band combinations analysed in this study shows that MSD can be lowered by increasing PCB and or antenna isolations**
+
+### 6.2.5 Evaluation from Apple [12]
+
+#### 6.2.5.1 CA\_n3-n78 UL 2nd harmonic MSD analysis
+
+Figure 6.2.5.1-1 shows the MSD improvement over the harmonic filter rejection ratio. It can be seen that when harmonic filter rejection is above 20 dB, the MSD would be dominated by other impairments.
+
+
+
+| Harmonic Filter Rejection Ratio (dB) | MSD (dB) |
+|--------------------------------------|----------|
+| 0 | 28.5 |
+| 5 | 26.0 |
+| 10 | 24.5 |
+| 15 | 24.2 |
+| 20 | 24.0 |
+| 25 | 24.0 |
+| 30 | 24.0 |
+| 35 | 24.0 |
+| 40 | 24.0 |
+| 45 | 24.0 |
+| 50 | 24.0 |
+| 55 | 24.0 |
+| 60 | 24.0 |
+
+Figure 6.2.5.1-1: A line graph showing MSD (dB) on the y-axis (ranging from 20 to 30) versus Harmonic Filter Rejection Ratio (dB) on the x-axis (ranging from 0 to 60). The curve starts at approximately 28.5 dB at 0 dB rejection and decreases sharply to about 24.5 dB at 10 dB rejection. It then levels off, reaching a plateau of approximately 24 dB for rejection ratios of 20 dB and above. The data points are marked with blue dots, and the point at 30 dB rejection is highlighted with a white circle.
+
+**Figure 6.2.5.1-1 CA\_n3-n78 UL 2<sup>nd</sup> harmonic MSD improvement over improved harmonic filter rejection**
+
+**Observation 1: When harmonic filter rejection is above 20 dB, the MSD would be dominated by other impairments.**
+
+Figure 6.2.5.1-2 shows the MSD improvement over the combined diplexer/n78 filter rejection ratio to n3 Tx. It can be seen that when the combined rejection ratio is above 60 dB, the MSD would be dominated by other impairments.
+
+
+
+| Diplexer+n78 Filter Rejection Ratio to n3 Tx (dB) | MSD (dB) |
+|---------------------------------------------------|----------|
+| 40 | 32.5 |
+| 45 | 26.0 |
+| 50 | 24.0 |
+| 55 | 23.0 |
+| 60 | 22.5 |
+| 65 | 22.5 |
+| 70 | 22.5 |
+| 75 | 22.5 |
+| 80 | 22.5 |
+
+Figure 6.2.5.1-2: UL 2nd harmonic MSD improvement over improved diplexer+n78 filter rejection to n3 Tx. The graph shows MSD (dB) on the y-axis (20 to 40) versus Diplexer+n78 Filter Rejection Ratio to n3 Tx (dB) on the x-axis (40 to 80). The curve starts at 32.5 dB at 40 dB rejection and decreases to approximately 22.5 dB at 80 dB rejection, leveling off after 60 dB.
+
+**Figure 6.2.5.1-2 UL 2<sup>nd</sup> harmonic MSD improvement over improved diplexer+n78 filter rejection to n3 Tx**
+
+**Observation 2:** When the combined diplexer+n78 filter rejection ratio to n3 Tx is above 60 dB, the MSD would be dominated by other impairments.
+
+Figure 6.2.5.1-3 shows the MSD improvement over the PA 2nd harmonic rejection ratio. It can be seen that when the PA 2nd harmonic rejection ratio is above 56 dB, the MSD would be dominated by other impairments.
+
+
+
+| PA 2nd Harmonic Rejection Ratio (dB) | MSD (dB) |
+|--------------------------------------|----------|
+| 30 | 28.5 |
+| 32 | 27.0 |
+| 34 | 25.5 |
+| 36 | 24.0 |
+| 38 | 22.5 |
+| 40 | 21.5 |
+| 42 | 20.5 |
+| 44 | 20.0 |
+| 46 | 19.5 |
+| 48 | 19.0 |
+| 50 | 18.8 |
+| 52 | 18.5 |
+| 54 | 18.5 |
+| 56 | 18.5 |
+| 58 | 18.5 |
+| 60 | 18.5 |
+
+Figure 6.2.5.1-3: UL 2nd harmonic MSD improvement over improved PA 2nd harmonic rejection ratio. The graph shows MSD (dB) on the y-axis (10 to 30) versus PA 2nd Harmonic Rejection Ratio (dB) on the x-axis (30 to 60). The curve starts at 28.5 dB at 30 dB rejection and decreases to approximately 18.5 dB at 60 dB rejection, leveling off after 56 dB.
+
+**Figure 6.2.5.1-3 UL 2<sup>nd</sup> harmonic MSD improvement over improved PA 2<sup>nd</sup> harmonic rejection ratio**
+
+**Observation 3:** When the PA 2nd harmonic rejection ratio is above 56 dB, the MSD would be dominated by other impairments.
+
+Figure 6.2.5.1-4 shows the MSD improvement over LNA IP2 performance. It can be seen that the MSD though improved with increasing LNA IP2, the improvement is quite limited even with LNA IP2 up to 30 dBm.
+
+**Observation 4:** MSD though improved with increasing LNA IP2, the improvement is quite limited even with LNA IP2 up to 30 dBm.
+
+
+
+| LNA IP2 (dBm) | MSD (dB) |
+|---------------|----------|
+| 0 | 24.8 |
+| 2 | 24.5 |
+| 4 | 24.2 |
+| 6 | 24.0 |
+| 8 | 23.8 |
+| 10 | 23.6 |
+| 12 | 23.4 |
+| 14 | 23.2 |
+| 16 | 23.0 |
+| 18 | 22.8 |
+| 20 | 22.6 |
+| 22 | 22.5 |
+| 24 | 22.4 |
+| 26 | 22.3 |
+| 28 | 22.2 |
+| 30 | 22.1 |
+
+Figure 6.2.5.1-4: UL 2nd harmonic MSD improvement over improved LNA IP2. A line graph showing MSD (dB) on the y-axis (20 to 30) versus LNA IP2 (dBm) on the x-axis (0 to 30). The data points show a gradual decrease in MSD as LNA IP2 increases, starting at approximately 24.8 dB at 0 dBm and leveling off at approximately 22.8 dB at 30 dBm. One data point at 6 dBm is highlighted with a white circle.
+
+**Figure 6.2.5.1-4 UL 2<sup>nd</sup> harmonic MSD improvement over improved LNA IP2**
+
+Based on the above observations, we can conclude that without PCB and antenna isolations improvement, the MSD from other improved RF parameters alone cannot be reduced to below 18 dB.
+
+**Observation 5: Without PCB and antenna isolations improvement, the UL 2nd harmonic MSD from other improved RF parameters alone cannot be reduced to below 18 dB.**
+
+#### 6.2.5.2 CA\_n3-n78 2UL IMD2 MSD analysis
+
+Figure 6.2.5.2-1 shows the MSD improvement over the duplexer rejection ratio for IMD2 at n3 DL. It can be seen that when the duplexer rejection ratio is above 70 dB, the MSD would be dominated by other impairments.
+
+
+
+| Duplexer Isolation (dB) | MSD (dB) |
+|-------------------------|----------|
+| 40 | 33 |
+| 45 | 29 |
+| 50 | 26 |
+| 55 | 24.5 |
+| 60 | 24 |
+| 65 | 23.8 |
+| 70 | 23.6 |
+| 75 | 23.5 |
+| 80 | 23.4 |
+
+Figure 6.2.5.2-1: CA\_n3-n78 2UL IMD2 MSD improvement over improved duplexer rejection ratio at n3 DL. A line graph showing MSD (dB) on the y-axis (20 to 40) versus Duplexer Isolation (dB) on the x-axis (40 to 80). The data points show a sharp decrease in MSD from 33 dB at 40 dB isolation to 26 dB at 50 dB isolation, then a more gradual decrease to 24 dB at 60 dB isolation, after which it remains relatively flat. One data point at 50 dB isolation is highlighted with a white circle.
+
+**Figure 6.2.5.2-1 CA\_n3-n78 2UL IMD2 MSD improvement over improved duplexer rejection ratio at n3 DL**
+
+**Observation 6: When the duplexer rejection ratio for IMD2 at n3 DL is above 70 dB, the MSD would be dominated by other impairments.**
+
+Figure 6.2.5.2-2 shows the MSD improvement over PA forward mixing IP2. It can be seen that when the PA forward mixing IP2 is above 45 dB, the MSD would be dominated by other impairments.
+
+
+
+| PA Forward IP2 (dBm) | MSD (dB) |
+|----------------------|----------|
+| 25 | 28.0 |
+| 27.5 | 26.5 |
+| 30 | 25.0 |
+| 32.5 | 24.0 |
+| 35 | 23.0 |
+| 37.5 | 22.0 |
+| 40 | 21.5 |
+| 42.5 | 21.0 |
+| 45 | 20.5 |
+| 47.5 | 20.0 |
+| 50 | 19.5 |
+| 52.5 | 19.0 |
+| 55 | 18.5 |
+
+Figure 6.2.5.2-2: A line graph showing MSD (dB) on the y-axis (ranging from 10 to 30) versus PA Forward IP2 (dBm) on the x-axis (ranging from 25 to 55). The data points show a decreasing trend in MSD as PA Forward IP2 increases, starting at approximately 28 dB at 25 dBm and leveling off at approximately 18.5 dB at 55 dBm. One data point at 27.5 dBm is highlighted with a white circle.
+
+Figure 6.2.5.2-2 CA\_n3-n78 2UL IMD2 MSD improvement over improved PA forward mixing IP2
+
+**Observation 7:** When the PA forward mixing IP2 is above 45 dB, the MSD would be dominated by other impairments.
+
+Figure 6.2.5.2-3 shows the MSD improvement over LNA IP2 performance. It can be seen that the MSD though improved with increasing LNA IP2, the improvement is quite limited even with LNA IP2 up to 20 dBm.
+
+
+
+| LNA IP2 (dBm) | MSD (dB) |
+|---------------|----------|
+| 0 | 27.5 |
+| 2.5 | 26.8 |
+| 5 | 26.2 |
+| 6.25 | 26.0 |
+| 10 | 25.8 |
+| 12.5 | 25.7 |
+| 15 | 25.6 |
+| 17.5 | 25.5 |
+| 20 | 25.5 |
+
+Figure 2.2-3: A line graph showing MSD (dB) on the y-axis (ranging from 20 to 30) versus LNA IP2 (dBm) on the x-axis (ranging from 0 to 20). The data points show a slight decreasing trend in MSD as LNA IP2 increases, starting at approximately 27.5 dB at 0 dBm and leveling off at approximately 25.5 dB at 20 dBm. One data point at 6.25 dBm is highlighted with a white circle.
+
+Figure 2.2-3 CA\_n3-n78 2UL IMD2 MSD improvement over improved LNA IP2
+
+**Observation 8:** MSD though improved with increasing LNA IP2, the improvement is quite limited even with LNA IP2 up to 20 dBm.
+
+Figure 6.2.5.2-4 shows the MSD improvement over diversity n3 filter rejection ratio to n3 and n78 UL. It can be seen that when the n3 diversity Rx filter rejection ratio to n3 and n78 UL is above 46 dB, the MSD would be dominated by other impairments.
+
+**Observation 9:** when the n3 diversity Rx filter rejection ratio to n3 and n78 UL is above 46 dB, the MSD would be dominated by other impairments.
+
+
+
+| Diversity Rx Filter Rejection (dB) | MSD (dB) |
+|------------------------------------|----------|
+| 30 | 32 |
+| 32 | 30 |
+| 34 | 28 |
+| 36 | 27 |
+| 38 | 26 |
+| 40 | 26 |
+| 42 | 26 |
+| 44 | 26 |
+| 46 | 26 |
+| 48 | 26 |
+| 50 | 26 |
+
+Figure 6.2.5.2-4: A line graph showing MSD (dB) on the y-axis (ranging from 20 to 40) versus Diversity Rx Filter Rejection (dB) on the x-axis (ranging from 30 to 50). The data points show a decreasing trend from approximately 32 dB at 30 dB rejection to about 26 dB at 38 dB rejection, after which the values remain relatively flat around 26 dB up to 50 dB rejection. One data point at 38 dB rejection is highlighted with a white circle.
+
+**Figure 6.2.5.2-4 UL 2<sup>nd</sup> harmonic MSD improvement over improved LNA IP2**
+
+Based on the above observations, we can conclude that without PCB and antenna isolations improvement, the MSD from other improved RF parameters alone cannot be reduced to below 18 dB.
+
+**Observation 10: Without PCB and antenna isolations improvement, the 2UL IMD2 MSD from other improved RF parameters alone cannot be reduced to below 18 dB.**
+
+#### 6.2.5.3 CA\_n28-n40 3rd order harmonic mixing MSD analysis
+
+To assess the potential MSD improvement for CA\_n28-n40 due to n28 Rx 3rd order harmonic mixing, we have performed the link analysis based on the reference architecture as shown in Figure 6.2.5.3-1 and a set of front-end component isolation parameters as summarized in Table 6.2.5.3-1.
+
+Table 6.2.5.3-2 presents the link analysis to derive the equivalent interference power levels at n28 main and diversity Rx inputs. The MSD for n28 5MHz DL channel BW after MRC assuming uncorrelated noise is summarized in Table 2.3-3.
+
+
+
+Figure 6.2.5.3-1: Reference architecture diagram for CA\_n28-n40 n28 Rx 3rd order harmonic mixing MSD analysis. The diagram shows two parallel receiver paths: 'Main TRx' and 'Diversity Rx'. Each path consists of an antenna, a duplexer, an sPnT (Switch/Pole/Notch Transformer), a filter, and an sPdT (Switch/Pole/Notch Transformer). The Main TRx path includes a 'Victim DL' (n28) and an 'Aggressor UL' (n40) input. The Diversity Rx path includes a 'Victim DL' (n28) and an 'Aggressor UL' (n40) input. The diagram illustrates the signal flow and component isolation parameters for the analysis.
+
+**Figure 6.2.5.3-1 Reference architecture for CA\_n28-n40 n28 Rx 3<sup>rd</sup> order harmonic mixing MSD analysis**
+
+**Table 6.2.5.3-1 Front-end component isolation parameters for MSD calculation**
+
+| | |
+|---------------------------------|----|
+| Isolation | dB |
+| Diplexer | 20 |
+| n28 duplexer to n40 | 40 |
+| n28 diversity Rx filter to n40 | 33 |
+| PCB | 65 |
+| Antenna | 10 |
+| Rx 3rd harmonic rejection ratio | 25 |
+
+**Table 6.2.5.3-2 Link analysis to derive the interference power levels at n28 main and diversity Rx inputs**
+
+| | | | |
+|--------------------------------------------------------------|-------|---------------------------------------------|-------|
+| Insertion loss (dB) | 3 | | |
+| PA output power (dBm) | 26 | | |
+| Main Path | dBm | Diversity Path | dBm |
+| n40 UL power at antenna port | 23 | n40 UL power at antenna port | 13 |
+| n40 UL power after diplexer | 3 | n40 UL power after diplexer | -7 |
+| n40 UL power at n28 LNA input (filter path) | -40 | n40 UL power at n28 LNA input (filter path) | -40 |
+| n40 UL power at n28 LNA input (PCB) | -39 | n40 UL power at n28 LNA input (PCB) | -39 |
+| Total n40 UL power at n28 LNA input | -36.5 | Total n40 UL power at n28 LNA input | -36.5 |
+| Total equivalent interference power after harmonic rejection | -58.5 | LNA H2 referred to antenna | -58.5 |
+
+**Table 6.2.5.3-3 MSD for 5MHz DL channel BW after MRC**
+
+| BW | | Floor | H2 | Total |
+|-------|----------------------|-------|-------|-------|
+| 5 MHz | Main Path (dBm) | -95.5 | -58.5 | -58.5 |
+| | Diversity Path (dBm) | -95.5 | -58.5 | -58.5 |
+| | After MRC (dBm) | -98.5 | | -61.5 |
+| | MSD (dB) | | | 37.0 |
+
+Though there are many factors affecting the MSD value, from the link analysis we have observed that the most effective way to reduce the MSD due to UL 2nd harmonic interference is to improve PCB isolation and antenna isolation simultaneously. Thereby without taking into account the practical implementation feasibility, we have evaluated the MSD improvement over the improved PCB isolation up to 100 dB and antenna isolation up to 20 dB. The result for 5MHz DL channel BW is shown in Figure 6.2.5.3-2.
+
+Based on the above analysis, it can be seen that even with 20dB antenna isolation and 100 PCB isolation, the improved MSD is still above 25 dB. As a result, it would be rather challenging to improve MSD caused by 3rd order harmonic mixing to below 30 dB based on practical UE implementation.
+
+**Observation 11: It would be rather challenging to improve MSD caused by 3rd order harmonic mixing to below 30 dB based on practical UE implementation.**
+
+
+
+| PCB Isolation (dB) | Ant Iso = 10 dB (MSD dB) | Ant Iso = 15 dB (MSD dB) | Ant Iso = 20 dB (MSD dB) |
+|--------------------|--------------------------|--------------------------|--------------------------|
+| 60 | 40.5 | 40.0 | 40.0 |
+| 65 | 37.5 | 36.0 | 35.5 |
+| 70 | 35.0 | 33.5 | 32.0 |
+| 75 | 34.0 | 31.5 | 29.5 |
+| 80 | 33.5 | 30.5 | 27.5 |
+| 85 | 33.5 | 30.5 | 26.5 |
+| 90 | 33.5 | 30.5 | 26.0 |
+| 95 | 33.5 | 30.5 | 26.0 |
+| 100 | 33.5 | 30.5 | 26.0 |
+
+Figure 6.2.5.3-2: A line graph showing the 3rd order harmonic mixing MSD improvement over improved PCB and antenna isolations. The x-axis represents PCB Isolation (dB) from 60 to 100. The y-axis represents MSD (dB) from 20 to 45. Three lines are plotted for different antenna isolation levels: Ant Iso = 10 dB (blue), Ant Iso = 15 dB (orange), and Ant Iso = 20 dB (grey). All lines show a decrease in MSD as PCB isolation increases, with the 20 dB antenna isolation line showing the lowest MSD values.
+
+**Figure 6.2.5.3-2 3<sup>rd</sup> order harmonic mixing MSD improvement over improved PCB and antenna isolations**
+
+Though the RF parameter assumptions for MSD analyses may vary among companies, when considering the potential improvement, company shall present their assumptions for link analysis or measurement results instead of only showing the MSD numbers, otherwise, it would not be conceivable for other companies to envision how the MSD had been derived.
+
+### 6.2.6 Evaluation from ZTE [13]
+
+In this section, we share some analysis on how much MSD can be improved for some of the agreed candidate band combination by using more aggressive values of PCB isolation and antenna isolation.
+
+Actually, there are several methods to improve the MSD. The MSD defined in the specification are largely depends on the calculation, especially for the larger MSD. Of course, few of the companies provided the measurements on some MSD but such MSD values are usually small.
+
+Considering the lower MSD issue are somehow triggered by the survey of the commercial UE from some operators that high MSD (more than 20dB) are defined in the specification for some band combinations. Therefore, we think how much the MSD can be improved in practical should be based on the commercial UE measurement.
+
+#### Observation 1. How much the MSD can be improved in practical should be based on the commercial UE measurement.
+
+Without the commercial UE measurements, some rough analysis can also be done based on the budget calculations which was extensive adopted in the past. Nevertheless, it would be foreseen different companies may use different input parameters, different calculation methods, even with different RF architecture, all of these factors will impact the results.
+
+In the following part of the section, we use CA\_n3-n78 as an example.
+
+#### CA n3-n78
+
+As CA\_n1-n3-n78 and fallback combinations were agreed to used as the candidate band combination. For CA\_n3-n78, there are IMD2/4 and 2<sup>nd</sup> harmonic and harmonic mixing issues.
+
+##### IMD2/4 MSD
+
+The IMD2/4 MSD in TS38.101-1 for CA\_n3-n78 are defined as:
+
+| | | | | | | PC3 | PC2 | | |
+|-----------|-----|------|----|----|------|-----|------|-----|-------|
+| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | 31.9 | FDD | IMD24 |
+| | n78 | 3575 | 10 | 25 | 3575 | N/A | N/A | TDD | N/A |
+| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | 18.5 | FDD | IMD44 |
+
+| | | | | | | | | | |
+|--|-----|------|----|----|------|-----|-----|-----|-----|
+| | n78 | 3435 | 10 | 25 | 3435 | N/A | N/A | TDD | N/A |
+|--|-----|------|----|----|------|-----|-----|-----|-----|
+
+Harmonic Trap filter(HTF) is used for n3-n78, so the RF architecture used for calculation is in Figure 6.2.6-1.
+
+
+
+```
+
+graph TD
+ Antenna((Antenna)) --> Switch1[Switch]
+ Switch1 --> OtherBands[Other bands]
+ Switch1 --> Diplexer[Diplexer]
+ Diplexer --> HTF[HTF]
+ Diplexer --> HBFilter[HB filter]
+ HTF --> Duplexer[Duplexer]
+ HBFilter --> Switch2[Switch]
+ Duplexer --> n3TxRx[n3 Tx/Rx]
+ Switch2 --> n78TxRx[n78 Tx/Rx]
+
+```
+
+Figure 6.2.6-1: n3-n78 primarily Tx/Rx RF architecture diagram. The diagram shows an antenna connected to a Switch. The Switch has two outputs: one labeled 'Other bands' and another leading to a Diplexer. The Diplexer has two outputs: one leading to an HTF (Harmonic Trap Filter) and another leading to an HB filter (High Band filter). The HTF output is connected to a Duplexer, which is connected to two antennas labeled 'n3 Tx/Rx'. The HB filter output is connected to a Switch, which is connected to two antennas labeled 'n78 Tx/Rx'.
+
+Figure 6.2.6-1: n3-n78 primarily Tx/Rx
+
+And the general IPx RF parameters used in calculation are in Table 6.2.6-1.
+
+Table 6.2.6-1: General IPx parameters
+
+| Component | IP2 (dBm) | IP3 (dBm) | IP4 (dBm) | IP5 (dBm) |
+|-------------|-----------|-----------|-----------|-----------|
+| Ant. Switch | 112 | 68 | 56 | 53 |
+| Diplexer | 115 | 86 | 55 | 53 |
+| Duplexer | 100 | 74 | 55 | 53 |
+| Triplexer | 110 | 82 | 55 | 52 |
+| Quadplexer | 113 | 74 | 55 | 50 |
+| PA Forward | 27 | 32 | 31 | 28 |
+| PA Reversed | 40 | 30 | 33 | 30 |
+| LNA | 6 | -6 | -6 | -10 |
+
+The IMD2/IMD4 values at the condition of PCB isolation=65dB and antenna isolation = 10dB are calculated as in Table 6.2.6-2 and 6.2.6-3.
+
+Table 6.2.6-2: IMD2 MSD for n3-n78
+
+| | Main path | Diversity path |
+|-----------------------------------|-----------|----------------|
+| IMD2 (without CF) (dBm) | -59.4 | -69.2 |
+| Band n3 Thermal noise (dBm) | -94 | -94 |
+| Total Noise (dBm) | -59.3 | -69.1 |
+| After MRC sensitivity @ Ant (dBm) | -69.6 | |
+| MSD (dB) | 27.4 | |
+
+**Table 6.2.6-3: IMD4 MSD for n3-n78**
+
+| | Main path | Diversity path |
+|-----------------------------------|-----------|----------------|
+| IMD2 (without CF) (dBm) | -80.1 | -90.1 |
+| Band n3 Thermal noise (dBm) | -94 | -94 |
+| Total Noise (dBm) | -79.9 | -88.6 |
+| After MRC sensitivity @ Ant (dBm) | -89.1 | |
+| MSD (dB) | 7.9 | |
+
+With other PCB isolation and antenna isolation values, where the antenna isolation values are [10, 15, 20]dB, and the PCB isolation values are [60, 65, 70, 75, 80, 85, 90]dB, the IMD2/4 MSD values are summarized in Table 6.2.6-4.
+
+**Table 6.2.6-4: IMD2/4 MSD values with different antenna isolation, and different PCB isolation**
+
+###### **(a). PC3(without CF)**
+
+| | Antenna iso.=10dB | | Antenna iso.=15dB | | Antenna iso.=20dB | |
+|-----------------|-------------------|------|-------------------|------|-------------------|------|
+| | IMD2 | IMD4 | IMD2 | IMD4 | IMD2 | IMD4 |
+| PCB iso. = 60dB | 31.9 | 10.4 | 27.1 | 7.0 | 22.2 | 4.7 |
+| PCB iso. = 65dB | 27.4 | 7.9 | 22.6 | 5.2 | 17.8 | 3.8 |
+| PCB iso. = 70dB | 23.8 | 6.5 | 18.9 | 4.4 | 14.1 | 3.4 |
+| PCB iso. = 75dB | 21.5 | 6.0 | 16.5 | 4.1 | 11.8 | 3.2 |
+| PCB iso. = 80dB | 20.4 | 5.8 | 15.3 | 4.0 | 10.7 | 3.2 |
+| PCB iso. = 85dB | 20.0 | 5.7 | 14.8 | 3.9 | 10.3 | 3.1 |
+| PCB iso. = 90dB | 19.8 | 5.7 | 14.7 | 3.9 | 10.1 | 3.1 |
+
+###### **(b). PC2 (without CF)**
+
+| | Antenna iso.=10dB | | Antenna iso.=15dB | | Antenna iso.=20dB | |
+|-----------------|-------------------|------|-------------------|------|-------------------|------|
+| | IMD2 | IMD4 | IMD2 | IMD4 | IMD2 | IMD4 |
+| PCB iso. = 60dB | 37.9 | 21.8 | 33.1 | 17.2 | 28.2 | 12.6 |
+| PCB iso. = 65dB | 33.4 | 18.6 | 28.6 | 14.1 | 23.7 | 9.9 |
+| PCB iso. = 70dB | 29.8 | 16.8 | 24.8 | 12.4 | 19.9 | 8.4 |
+| PCB iso. = 75dB | 27.5 | 16.0 | 22.3 | 11.7 | 17.4 | 7.9 |
+| PCB iso. = 80dB | 26.4 | 15.7 | 21.1 | 11.4 | 16.1 | 7.7 |
+| PCB iso. = 85dB | 25.8 | 15.6 | 20.6 | 11.4 | 15.6 | 7.6 |
+| PCB iso. = 90dB | 19.8 | 5.7 | 20.5 | 11.3 | 15.5 | 7.6 |
+
+If considering CF, the MSD would be smaller than the values in table 6.2.6-4 due to the IMD2/4 product bandwidth will not occupy the whole IMD2/4 frequency range considering the UL/DL IMD MSD test point.
+
+For n3-n78 IMD2/4 MSD, the PA non-linear factor is dominated factor when the PCB isolation is about 75dB. However, when PCB isolation is larger than 75dB, the other RF parameters like diplexer/LNA become the domination. So in this case, if PCB isolation continue to increase, the MSD improved is quite limited. It should be noted that the situations are similar for PC2.
+
+##### **H2 harmonic MSD**
+
+For H2 harmonic requirements, the MSD values at the condition of PCB isolation=65dB and antenna isolation = 10dB, and HTF isolation equals to 30dB are calculated as in table 6.2.6-5. Note that only MSD test points of channel bandwidth@n78=10MHz and channel bandwidth@n3 =5MHz is considered since it is the worst case compared to the other MSD test points of channel bandwidth@n78=100MHz and channel bandwidth@n3 =10MHz.
+
+**Table 6.2.6-5: H2 MSD for n3-n78**
+
+| | Main path | Diversity path |
+|------------------------------------|-----------|----------------|
+| IMD2 (without CF) (dBm) | -67.1 | -70.4 |
+| Band n78 Thermal noise@10MHz (dBm) | -92.3 | -92.3 |
+| Total Noise (dBm) | -67.1 | -70.4 |
+| After MRC sensitivity @ Ant (dBm) | -72.0 | |
+| MSD (dB) | 23.3 | |
+
+Similar as IMD2/4 MSD, using the combinations of different PCB isolation values and different antenna isolation values, the H2 MSD values are summarized in Table 6.2.6-6.
+
+**Table 6.2.6-6: H2 MSD values with different antenna isolation, and different PCB isolation (PC3 and PC2)(without CF)**
+
+| | Antenna iso.=10dB | Antenna iso.=15dB | Antenna iso.=20dB |
+|-----------------|-------------------|-------------------|-------------------|
+| PCB iso. = 60dB | 27.2 | 27.1 | 27.1 |
+| PCB iso. = 65dB | 23.3 | 23.0 | 22.9 |
+| PCB iso. = 70dB | 20.0 | 19.2 | 18.8 |
+| PCB iso. = 75dB | 17.7 | 15.8 | 14.8 |
+| PCB iso. = 80dB | 16.5 | 13.4 | 11.4 |
+| PCB iso. = 85dB | 16.0 | 12.1 | 9.3 |
+| PCB iso. = 90dB | 15.8 | 11.7 | 8.2 |
+
+##### Harmonic mixing MSD
+
+In current 38.101-1 spec, there is no harmonic mixing MSD defined for PC3 n3-n78 inter-band CA but 8.1dB harmonic mixing MSD was defined for PC2 n3-n78 when aggressor UL is PC2 n78.
+
+Noted that harmonic mixing MSD was defined for ENDC 3-n78, where 5.7dB is defined for 3@5MHz. Actually 5.7dB harmonic mixing MSD was the comprised value from references due to different parameters were used by different companies. Also, it can be found that this values were derided from antenna isolation is 10dB and PCB isolation is 70dB.
+
+Ignoring the mistakes for PC3 n3-n78 harmonic mixing MSD, here we assume the same PC3 3\_n78 harmonic mixing MSD of 5.7dB was reused.
+
+For harmonic mixing requirements, the MSD values at the condition of PCB isolation=70dB and antenna isolation = 10dB, are calculated as in Table 6.2.6-7.
+
+**Table 6.2.6-7: Harmonic mixing MSD for n3-n78 (PC3&PC2)**
+
+| | PC3 | | PC2 | |
+|---------------------------------------------------------|-----------|-----------|-----------|-----------|
+| | Main path | Div. path | Main path | Div. path |
+| n78 Tx power at n3 LNA input (dBm) | -42.9 | -46.4 | -39.9 | -43.4 |
+| After Rx harmonic rejection (referred to antenna) (dBm) | -87.9 | -91.4 | -84.9 | -88.4 |
+| Band n3 Thermal noise (dBm) | -94 | -94 | -94 | -94 |
+| Total Noise (dBm) | -86.9 | -89.5 | -84.4 | -87.3 |
+| After MRC sensitivity @ Ant (dBm) | -91.4 | | -89.1 | |
+| MSD (dB) | 5.6 | | 7.9 | |
+
+Similar as above, different combination of antenna isolation and PCB isolation are used to see how much MSD can be improved, as summarized in Table 6.2.6-8.
+
+**Table 6.2.6-8: Harmonic mixing MSD values different antenna isolation, and different PCB isolation (PC3 and PC2)**
+
+| | Antenna iso.=10dB | | Antenna iso.=15dB | | Antenna iso.=20dB | |
+|-----------------|-------------------|------|-------------------|------|-------------------|------|
+| | PC3 | PC2 | PC3 | PC2 | PC3 | PC2 |
+| PCB iso. = 60dB | 12.6 | 15.5 | 12.6 | 15.4 | 12.6 | 15.4 |
+| PCB iso. = 65dB | 8.6 | 11.3 | 8.5 | 11.2 | 8.5 | 11.2 |
+| PCB iso. = 70dB | 5.6 | 7.9 | 5.4 | 7.7 | 5.4 | 7.6 |
+| PCB iso. = 75dB | 3.9 | 5.7 | 3.6 | 5.2 | 3.4 | 5.0 |
+| PCB iso. = 80dB | 3.1 | 4.5 | 2.7 | 3.8 | 2.5 | 3.5 |
+| PCB iso. = 85dB | 2.8 | 4.0 | 2.3 | 3.2 | 2.2 | 2.9 |
+| PCB iso. = 90dB | 2.7 | 3.9 | 2.2 | 3.0 | 2.1 | 2.6 |
+
+In terms of the above, considering the existing MSD minimum requirements defined in the spec, we can observe:
+
+**Observation 2.** PCB isolation for harmonic/IMD and harmonic mixing are used to derive the corresponding MSD values are different.
+
+**Observation 3.** For IMD2 and H2 MSD, it is difficult to improve 20dB MSD by only increasing PCB isolation or antenna isolation.
+
+**Observation 4.** For IMD2 and H2 MSD, to achieve ~10dB MSD value, the antenna isolation needs to better than 20dB associated with PCB isolation better than 85dB.
+
+**Observation 5.** For IMD4, the improved MSD is less than 5dB when the antenna isolation is 20dB associated with PCB isolation is 85dB.
+
+**Observation 6.** For IMD2/4, H2 and harmonic mixing MSD, the improved MSD is limited when PCB isolation >75dB for a certain antenna isolation.
+
+##### CA n28-n40
+
+For n28-n40, harmonic mixing, i.e. $n40\ DL = 3 * n28\ UL$ , should be considered. Actually, the harmonic mixing MSD value for ENDC 28-n40 and NR CA n28-n40 are reused from LTE CA 28-n40, while it seems the MSD value for LTE CA 28-40 are the leverage value from companies.
+
+The RF architecture used in the calculation is shown below.
+
+
+
+```
+
+graph TD
+ Antenna((Antenna)) --> Diplexer[Diplexer]
+ Diplexer --> SwitchL[Switch]
+ Diplexer --> SwitchR[Switch]
+ SwitchL --> OtherBandsL[Other bands]
+ SwitchL --> Duplexer[Duplexer]
+ Duplexer --> 28TxRx[28 Tx/Rx]
+ SwitchR --> OtherBandsR[Other bands]
+ SwitchR --> HBFilter[HB filter]
+ HBFilter --> SwitchR2[Switch]
+ SwitchR2 --> n40TxRx[n40 Tx/Rx]
+
+```
+
+RF architecture diagram for CA n28-n40. A Diplexer at the top connects to an antenna. Below the Diplexer, the signal splits into two parallel paths. The left path goes through a Switch to 'Other bands' and a Duplexer to '28 Tx/Rx'. The right path goes through a Switch to 'Other bands' and an HB filter to another Switch, which then connects to 'n40 Tx/Rx'.
+
+The Rx 3rd order harmonic rejection = 20dB and n28 Rx filter selectivity at B40 = 60dB, the MSD values at the condition of PCB isolation=70dB and antenna isolation = 10dB, are calculated as in Table 6.2.6-9.
+
+**Table 6.2.6-9: Harmonic mixing MSD for n28-n40(PC3)**
+
+| | Main path | Div. path |
+|---------------------------------------------------------|-----------|-----------|
+| n40 Tx power at n28 LNA input (dBm) | -42.5 | -42.9 |
+| After Rx harmonic rejection (referred to antenna) (dBm) | -58.5 | -58.9 |
+| Band n28 Thermal noise (dBm) | -95.5 | -95.5 |
+| Total Noise (dBm) | -58.5 | -58.9 |
+| After MRC sensitivity @ Ant (dBm) | -61.7 | |
+| MSD (dB) | 36.8 | |
+
+Similar as above, using the combinations of different PCB isolation values and different antenna isolation values, the H2 MSD values are summarized in Table 6.2.6-10.
+
+**Table 6.2.6-10: Harmonic mixing MSD values with different antenna isolation, and different PCB isolation (PC3)(without CF)**
+
+| | Antenna iso.=10dB | Antenna iso.=15dB | Antenna iso.=20dB |
+|-----------------|-------------------|-------------------|-------------------|
+| PCB iso. = 60dB | 46.5 | 46.5 | 46.5 |
+| PCB iso. = 65dB | 41.6 | 41.6 | 41.6 |
+| PCB iso. = 70dB | 36.8 | 36.8 | 36.8 |
+| PCB iso. = 75dB | 32.3 | 32.2 | 32.2 |
+| PCB iso. = 80dB | 28.3 | 28.0 | 28.0 |
+| PCB iso. = 85dB | 24.9 | 24.2 | 23.9 |
+| PCB iso. = 90dB | 22.4 | 20.6 | 19.8 |
+
+The tendency is quite similar as n3-n78 harmonic mixing, where the MSD value is almost keep unchanged when the antenna isolation is increased up to 20dB as antenna isolation play less role on improving the MSD.
+
+For n28-n40 harmonic mixing, although PCB isolation is up to 90dB, the MSD would be still 'high'. So to further improve the MSD value, some other method may need to be adopted.
+
+**Observation 7. For n28-n40 harmonic mixing, some other method may need to be adopted to further improving the MSD value.**
+
+For harmonic mixing, no matter for n3-n78 and n28-n40, the MSD value is almost keep unchanged when the antenna isolation is increased up to 20dB, that's mainly because the aggressor PA output power appears at victim LNA input via PCB path is the dominated factor.
+
+**Observation 8. For harmonic mixing MSD, antenna isolation play less role on improving the MSD.**
+
+So far, there were no agreements on the antenna isolation and PCB isolation values. Some concerns from UE vendor that higher PCB isolation (>75dB?) is challenge in practice. So it would be better to discuss the achievable PCB isolation/antenna isolation values in practice when companies re-evaluate how much the MSD can be improved. Otherwise, the re-evaluated may big different among companies by using difference assumption.
+
+### 6.2.7 Evaluation from LGE [14]
+
+MSD values are analyzed for CA\_n1-n3 based on Table1 and Table2. Table 6.2.7-1 shows the component linearity parameter and Table 6.2.7-2 shows the isolation factor used in this analysis.
+
+**Table 6.2.7-1: Front-end component linearity parameter**
+
+| Component | IP2 (dBm) | IP3 (dBm) | IP4 (dBm) | IP5 (dBm) |
+|-------------|-----------|-----------|-----------|-----------|
+| Ant. Switch | 112 | 68 | 55 | 55 |
+| Duplexer | 100 | 75 | 55 | 53 |
+| PA | 28.5 | 30 | 30 | 28 |
+| LNA | 10 | 0 | 0 | -10 |
+
+**Table 6.2.7-2: Isolation factor**
+
+| Isolation parameter | Case1 | Case2 |
+|---------------------|-------|-------|
+| Antenna to antenna | 10 dB | 10 dB |
+| PCB | 60 dB | 70 dB |
+
+The MSD value for CA\_n1-n3 in TS 38.101-1is shown in Table 6.2.7-3, and the analyzed MSD values in this paper are shown in Table 6.2.7-4.
+
+**Table 6.2.7-3: 2DL/2UL interband Reference sensitivity QPSK PREFSENS and uplink/downlink configurations for PC3 CA [TS 38.101-1]**
+
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD3 |
+| | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A |
+
+**Table 6.2.7-4: Analyzed MSD values considering two types of PCB isolation**
+
+| Isolation factor | MSD |
+|------------------|---------|
+| Case1 | 23.1 dB |
+| Case2 | 5 dB |
+
+In case 1, assuming PCB isolation of 60 dB, the MSD value is 23.1 dB, which is similar to the MSD value of TS38.101-1. In case 2, assuming PCB isolation of 70 dB, the MSD value is 5 dB, which is 18.1 dB lower than case 1.
+
+**Observation1: In CA\_n1-n3, when the PCB isolation is 70 dB, it has a much lower MSD value than 60 dB PCB isolation. Further analysis is required for other combinations using 70 dB PCB isolation.**
+
+### 6.2.8 Evaluation from Xiaomi [15]
+
+#### 6.2.8.1 2nd harmonic MSD analysis for CA\_n3-n78
+
+In order to evaluate the effect of improving PCB isolation as well as antenna isolation, the parameters for the MSD analysis list in the below.
+
+**Table 6.2.8.1-1, the parameters for the MSD analysis for CA\_n3-n78**
+
+| | value |
+|----------------------------------|-----------|
+| Band 3 PA | 27.8 dBm |
+| Band 3 PA in H2 | -8 dBm |
+| Band 3 duplexer in H2 | 25 dB |
+| diplexer | 15 dB |
+| Harmonic filter | 25 dB |
+| Antenna isolation | 10 ~20 dB |
+| PCB isolation | 60~100 dB |
+| duplexer, switch, diplexer in H2 | -85dBc |
+
+Based on above parameter, the MSD improvement over improving PCB isolation and antenna isolation could be illustrated in Figure 6.2.8.1-1.
+
+
+
+| PCB isolation (dB) | MSD (dB) for antenna isolation=10dB | MSD (dB) for antenna isolation=15dB | MSD (dB) for antenna isolation=20dB |
+|--------------------|-------------------------------------|-------------------------------------|-------------------------------------|
+| 60 | 27 | 27 | 27 |
+| 65 | 23 | 23 | 23 |
+| 70 | 21 | 20 | 19 |
+| 75 | 20 | 18 | 16 |
+| 80 | 19 | 16 | 14 |
+| 85 | 18.5 | 15.5 | 13 |
+| 90 | 18.5 | 15.5 | 12.5 |
+| 95 | 18.5 | 15.5 | 12.5 |
+| 100 | 18.5 | 15.5 | 12.5 |
+
+Figure 6.2.8.1-1: MSD improvement over improving PCB isolation and antenna isolation. The graph shows MSD (dB) on the y-axis (0 to 30) versus PCB isolation (dB) on the x-axis (60 to 100). Three curves are shown for antenna isolation levels of 10dB (blue), 15dB (orange), and 20dB (grey). All curves show a decrease in MSD as PCB isolation increases, with the 20dB antenna isolation curve showing the lowest MSD values.
+
+Figure 6.2.8.1-1 MSD improvement over improving PCB isolation and antenna isolation
+
+As seen from above figure 1, the following observations could be made for the harmonic MSD of band combination n3 and n78.
+
+**Observation 1:** improving the PCB isolation can reduce the MSD, but when PCB isolation is above 80dB, the impact becomes very small.
+
+**Observation 2:** improving the antenna isolation can reduce the MSD, especially when PCB isolation is high.
+
+#### 6.2.8.2 IMD MSD analysis for CA\_n3-n78
+
+According to the spec, there are IMD2 and IMD4 issues for CA\_n3-n78 due to 2UL. To assess the potential MSD improvement, the following parameters in table 6.2.8.2-1 and table 6.2.8.2-2 are assumed.
+
+Table 6.2.8.2-1: RF-front component linearity IP2 and IP4 parameters
+
+| | IP2 (dBm) | IP4 (dBm) |
+|-------------|-----------|-----------|
+| Ant. Switch | 112 | 56 |
+| Diplexer | 115 | 55 |
+| Duplexer | 100 | 55 |
+| PA Forward | 27 | 32 |
+| PA Reversed | 38 | 33 |
+| LNA | 5 | -6 |
+
+Table 6.2.8.2-2: the isolation parameters
+
+| Isolation Parameter | Value (dB) | Comment |
+|----------------------|------------|----------------------------------------------|
+| Antenna to Antenna | 10~20 | Main antenna to diversity antenna |
+| PA (out) to PA (in) | | PCB isolation (PA forward mixing and n78 PA |
+| PA(out) to LNA (in) | 60~100 | leakage into B3 LNA |
+| PA (out) to PA (out) | 60 | L-H/H-L cross-band (diplexer + duplexer) |
+| PA (out) to LNA (in) | 50 | L-H/H-L cross-band (diplexer + filter @ n78) |
+| Duplexer | 45 | Tx band rejection at Rx band |
+| diplexer | 15 | |
+
+##### 6.2.8.2.1 IMD2 MSD
+
+With above assumptions, we have made some calculations for IMD2, and the results for PC2 and PC3 are summarized in Figure 6.2.8.2.1-1 and Figure 6.2.8.2.1-2 separately.
+
+
+
+| PCB Isolation (dB) | antenna isolation=10dB | antenna isolation=15dB | antenna isolation=20dB |
+|--------------------|------------------------|------------------------|------------------------|
+| 60 | 37 | 35 | 33 |
+| 65 | 32 | 29 | 27 |
+| 70 | 28 | 25 | 21 |
+| 75 | 26 | 22 | 18 |
+| 80 | 25 | 21 | 17 |
+| 85 | 24.5 | 20.5 | 16 |
+| 90 | 24.5 | 20.5 | 16 |
+| 95 | 24.5 | 20.5 | 16 |
+| 100 | 24.5 | 20.5 | 16 |
+
+Figure 6.2.8.2.1-1: IMD2 MSD improvement over improving PCB isolation and antenna isolation for PC2. The graph shows Total Tx power=PC2 on the y-axis (0 to 40) versus PCB isolation on the x-axis (60 to 100). Three lines represent antenna isolation levels of 10dB (blue), 15dB (orange), and 20dB (grey). All lines show a decrease in IMD2 MSD as PCB isolation increases, with the 20dB antenna isolation line showing the lowest IMD2 MSD.
+
+Figure 6.2.8.2.1-1: IMD2 MSD improvement over improving PCB isolation and antenna isolation for PC2
+
+
+
+| PCB Isolation (dB) | antenna isolation=10dB | antenna isolation=15dB | antenna isolation=20dB |
+|--------------------|------------------------|------------------------|------------------------|
+| 60 | 31 | 29 | 27 |
+| 65 | 26 | 23 | 20 |
+| 70 | 22 | 19 | 15 |
+| 75 | 20 | 16 | 12 |
+| 80 | 19 | 15 | 10 |
+| 85 | 19 | 15 | 10 |
+| 90 | 19 | 15 | 10 |
+| 95 | 19 | 15 | 10 |
+| 100 | 19 | 15 | 10 |
+
+Figure 6.2.8.2.1-2: IMD2 MSD improvement over improving PCB isolation and antenna isolation for PC3. The graph shows Total Tx power=PC3 on the y-axis (0 to 35) versus PCB isolation on the x-axis (60 to 100). Three lines represent antenna isolation levels of 10dB (blue), 15dB (orange), and 20dB (grey). All lines show a decrease in IMD2 MSD as PCB isolation increases, with the 20dB antenna isolation line showing the lowest IMD2 MSD.
+
+Figure 6.2.8.2.1-2: IMD2 MSD improvement over improving PCB isolation and antenna isolation for PC3
+
+As seen from above Figure 6.2.8.2.1-1 and Figure 6.2.8.2.1-2, the following observations could be made for the IMD2 MSD of the combination n3 and n78.
+
+**Observation 1:** improving the PCB isolation can reduce the MSD, but when PCB isolation is above 80dB, the impact becomes very small.
+
+**Observation 2: improving the antenna isolation can reduce the MSD, especially when PCB isolation is high.**
+
+##### 6.2.8.2.2 IMD4 MSD
+
+The similar calculations are also made for IMD4, and the results for PC2 and PC3 are summarized in Figure 6.2.8.2.2-1 and Figure 6.2.8.2.2-2 separately.
+
+
+
+| PCB Isolation (dB) | Antenna Isolation = 10dB (IMD4 MSD) | Antenna Isolation = 15dB (IMD4 MSD) | Antenna Isolation = 20dB (IMD4 MSD) |
+|--------------------|-------------------------------------|-------------------------------------|-------------------------------------|
+| 60 | 21 | 17.5 | 12.5 |
+| 65 | 18.5 | 14.5 | 9.5 |
+| 70 | 17 | 13 | 8.5 |
+| 75 | 16.5 | 12.5 | 8 |
+| 80 | 16 | 12 | 7.5 |
+| 85 | 16 | 12 | 7.5 |
+| 90 | 16 | 12 | 7.5 |
+| 95 | 16 | 12 | 7.5 |
+| 100 | 16 | 12 | 7.5 |
+
+Figure 6.2.8.2.2-1: IMD4 MSD improvement over improving PCB isolation and antenna isolation for PC2. The graph shows Total Tx power=PC2 on the y-axis (0 to 25) versus PCB isolation on the x-axis (60 to 100 dB). Three lines represent antenna isolation levels of 10dB (blue), 15dB (orange), and 20dB (grey). All lines show a decrease in IMD4 MSD as PCB isolation increases, with the 20dB antenna isolation line showing the lowest IMD4 MSD values.
+
+**Figure 6.2.8.2.2-1: IMD4 MSD improvement over improving PCB isolation and antenna isolation for PC2**
+
+
+
+| PCB Isolation (dB) | Antenna Isolation = 10dB (IMD4 MSD) | Antenna Isolation = 15dB (IMD4 MSD) | Antenna Isolation = 20dB (IMD4 MSD) |
+|--------------------|-------------------------------------|-------------------------------------|-------------------------------------|
+| 60 | 10 | 6 | 3 |
+| 65 | 8 | 4.5 | 2 |
+| 70 | 7 | 4 | 1.8 |
+| 75 | 6.8 | 3.8 | 1.6 |
+| 80 | 6.8 | 3.6 | 1.5 |
+| 85 | 6.8 | 3.6 | 1.5 |
+| 90 | 6.8 | 3.6 | 1.5 |
+| 95 | 6.8 | 3.6 | 1.5 |
+| 100 | 6.8 | 3.6 | 1.5 |
+
+Figure 6.2.8.2.2-2: IMD4 MSD improvement over improving PCB isolation and antenna isolation for PC3. The graph shows Total Tx power=PC3 on the y-axis (0 to 12) versus PCB isolation on the x-axis (60 to 100 dB). Three lines represent antenna isolation levels of 10dB (blue), 15dB (orange), and 20dB (grey). All lines show a decrease in IMD4 MSD as PCB isolation increases, with the 20dB antenna isolation line showing the lowest IMD4 MSD values.
+
+**Figure 6.2.8.2.2-2: IMD4 MSD improvement over improving PCB isolation and antenna isolation for PC3**
+
+As seen from above figures, the following observations could be made for the IMD4 MSD of the combination n3 and n78.
+
+**Observation 1: improving the PCB isolation can reduce the MSD, but when PCB isolation is above 80dB, the impact becomes very small.**
+
+**Observation 2: improving the antenna isolation can reduce the MSD.**
+
+#### 6.2.8.3 Comparison of MSD improvement for different MSD types
+
+In order to compare with MSD improvement for different MSD types, we made the following table based on above calculations.
+
+| MSD types | MSD in current spec (dB) | MSD improvement when antenna isolation=20dB and PCB isolation=80dB | delta MSD value |
+|--------------|--------------------------|--------------------------------------------------------------------|------------------------------|
+| 2nd harmonic | 23.9 | 12.2 | 11.7 dB |
+| IMD2 | PC2: 31.9<br>PC3: 26 | PC2: 16.7<br>PC3: 10.5 | PC2: 15.2 dB<br>PC3: 15.5 dB |
+| IMD4 | PC2: 18.5<br>PC3: 8.0 | PC2: 7.3<br>PC3: 1.4 | PC2: 11.2 dB<br>PC3: 6.6 dB |
+
+**Observation 3: even when antenna isolation is 20dB and PCB isolation is 80dB, the MSD value is still above 15dB for IMD2 for CA\_n3-n78**
+
+**Observation 4: the delta MSD value due to MSD improvement for different MSD types is different. When the minimum requirement of MSD is high, the delta MSD value could be above 10 dB.**
+
+#### 6.2.8.4 Cross band isolation for CA\_n1-n3 (R4-2219037)
+
+According to the spec, there are IMD3 issues for CA\_n1-n3 due to 2UL. To assess the potential MSD improvement, the following parameters in table 6.2.8.4-1 and table 6.2.8.4-2 are assumed.
+
+**Table 6.2.8.4-1: RF-front component linearity IP3 parameters**
+
+| RF component | IP2 (dBm) |
+|--------------|-----------|
+| Ant. Switch | 68 |
+| Quadplexer | 74 |
+| PA Forward | 30 |
+| PA Reversed | 28 |
+| LNA | -6 |
+
+**Table 6.2.8.4-2: the isolation parameters**
+
+| Isolation Parameter | Value (dB) | Comment |
+|--------------------------------------------|------------|-----------------------------------------------------------------|
+| Antenna to Antenna | 10~20 | Main antenna to diversity antenna |
+| PA (out) to PA (in)<br>PA(out) to LNA (in) | 60~100 | PCB isolation (PA forward mixing and n3 PA leakage into B1 LNA) |
+| PA (out) to PA (out) | 45 | cross-band (Quadplxer) |
+| PA (out) to LNA (in) | 45 | cross-band (Quadplxer) |
+
+With above assumptions, we have made the calculations for IMD3, and the results for PC3 are summarized in figure 6.2.8.4-1.
+
+[TBD]
+
+**Figure 6.2.8.4-1: MSD improvement over improving PCB isolation and antenna isolation**
+
+As seen from above figure, the following observations could be made for the IMD3 MSD of the combination n1 and n3. From the paper [15], these two observations are the same as those for CA\_n3-n78
+
+**Observation 1:** improving the PCB isolation can reduce the MSD, but when PCB isolation is above 80dB, the impact becomes very small.
+
+**Observation 2:** improving the antenna isolation can reduce the MSD, especially when PCB isolation is high.
+
+### 6.2.9 Evaluation from Meta [16]
+
+#### 6.2.9.1 MSD evaluation results by Harmonic problem
+
+For CA\_n1-n3-n78, the 2<sup>nd</sup> harmonic from n3 UL will fall into n78 spectrum in DL slot. Based on the following RF parameters in Table 6.2.9.1-1, the expected MSD levels are evaluated in Table 6.2.9.1-2.
+
+**Table 6.2.9.1-1: NR CA\_n3A-n78A UE RF FE component isolation parameters**
+
+| | Attenuation Value |
+|----------------------------|-----------------------------|
+| n3 Tx in PA output | 28 |
+| n3 PA H2 attenuation | 35/ 40 |
+| n3 duplexer H2 attenuation | 32 |
+| Harmonic filter | 20/25 |
+| HB switch H2 | 110 |
+| Diplexer attenuation | 25 |
+| Antenna isolation | 10/15 |
+| Diplexer pathloss | 0.7 |
+| UHB switch attenuation | 0.7 |
+| UHB switch | 130/110 (primary/secondary) |
+| n78 Rx filter attenuation | 1.5 |
+| n78 Rx filter | 110/110 (primary/secondary) |
+| n3 PA to n78 LNA isolation | 70/75 |
+
+The Table 6.2.9.1-2 is shown the expected MSD levels for NR CA\_n3A-n78A.
+
+**Table 6.2.9.1-2: Comparison of MSD of NR CA\_n3A-n78A with different RF components**
+
+| Parameter | Considering different Filter/isolation | | | |
+|----------------------------|----------------------------------------|-----------|-----------|-----------|
+| | Primary | | Diversity | |
+| | Value | H2 level | Value | H2 level |
+| n3 Tx in PA output | 28 | | 28 | |
+| n3 PA H2 attenuation | 35 | -7 | 35 | -7 |
+| n3 duplexer H2 attenuation | 32 | -39 | 32 | -39 |
+| Harmonic filter | 20/25 | -59 / -64 | 20/25 | -59 / -64 |
+| HB switch H2 | -110 | -59/ -64 | -110 | -59/ -64 |
+| Diplexer attenuation | 25 | -84/ -89 | 25 | -84/ -89 |
+| Antenna isolation | 0 | -84/ -89 | 10/15 | -94/ -99 |
+
+| | | | | |
+|-----------------------------------|------------------------|----------------------------|--------------|----------------------------|
+| Diplexer pathloss | 0.7 | -84.7/ -89.7 | 0.7 | -94.7/ -99.7 |
+| UHB switch attenuation | 0.7 | -85.4/ -90.4 | 0.7 | -95.4/ -100.4 |
+| UHB switch | -130 | -85.4/ -90.4 | -110 | -95.2/ -99.9 |
+| n78 Rx filter attenuation | 1.5 | -86.9/ -91.9 | 1.5 | -96.7/ -101.4 |
+| n78 Rx filter | -110 | -86.9/ -91.8 | -110 | -96.5/ -100.9 |
+| <b>n3 PA to n78 LNA isolation</b> | <b>70/75</b> | <b>-77/ -82</b> | <b>70/75</b> | <b>-77/ -82</b> |
+| Composite | | <b>-76.85 –<br/>-81.54</b> | | <b>-76.98 –<br/>-81.93</b> |
+| MSD (dB) | <b>18.5dB – 23.4dB</b> | | | |
+
+Observation #1: Antenna isolation, attenuation of harmonic filter and PA H2 performance improvement are not dominant factors for the 2<sup>nd</sup> harmonic product to reduce the MSD requirements.
+
+Observation #2: The aggressor PA to victim LNA isolation improvement is a dominant factor due to the 2<sup>nd</sup> Harmonic product to improve MSD levels.
+
+#### 6.2.9.2 MSD evaluation results by cross band isolations
+
+For CA\_n41-n77, expected MSD levels are evaluated in Table 6.2.9.2-2 based on the common RF parameters are in Table 6.2.9.2-1.
+
+**Table 6.2.9.2-1: Basic RF parameters for CA\_n41A\_n77A**
+
+| | |
+|---------------------------------------------------------|--------------|
+| Band n77 PA noise @Band 41 Rx (dBm/Hz) | -115 |
+| CBW at n77 for UL | 100MHz |
+| n77 front end filter Loss (dB) | 4 |
+| n41 front end filter Loss (dB) | 4 |
+| PA to antenna and LNA to antenna IL (dB) | 4 |
+| <b>n41/n77 diplexer isolation (dB)</b> | <b>10/15</b> |
+| n77 filter attenuation @ B41 RX (dB) | 30 |
+| <b>Cross-band isolation (dB) (n77 Tx --> n41 Rx)</b> | <b>40/45</b> |
+| <b>Rx Antenna isolation (dB)</b> | <b>10/15</b> |
+
+**Table 6.2.9.2-2: Comparison of MSD of NR CA\_n41A-n77A with different RF components**
+
+| Parameter | Primary | Diversity |
+|------------------------------------|---------------------|---------------|
+| | Value | Value |
+| Total noise at PA output (dBm/Hz) | -148 | -148 |
+| Antenna isolation (10dB/ 15dB) | -148 | -158 / -163 |
+| Rx thermal noise @ LNA input (dBm) | -84 | -88.2 / -92.5 |
+| Total Interference @ Rx | -82.4 | -87.0/ -91.2 |
+| MRC | -88.3 / -91.7 | |
+| REFSENS at n41 (dBm/CBW) | -95.1 | |
+| MSD (dB) | <b>3.4 – 6.8 dB</b> | |
+
+Observation #3: For the MSD improvement due to cross band isolation, a larger antenna isolation could improve a required MSD level, but this is difficult to achieve in a small form-factor and not verifiable by conducted tests.
+
+**Observation #4: An RB restriction (e.g., restriction of RB length or RB position) also could reduce MSD levels. A specific uplink configuration will improve MSD levels.**
+
+#### 6.2.9.3 MSD evaluation results by dual uplink transmission
+
+For CA\_n1-n3-n78, the 2<sup>nd</sup> & 4<sup>th</sup> IMDs products by 2UL\_CA\_n1-n3 are falling into n78 DL slot. Also 2<sup>nd</sup> IMD product by 2UL\_CA\_n3-n78 is falling into n3 Rx band. Therefore, we consider the specific RF component improvement to enhance the MSD requirements in Table 5 and Table 6.
+
+Table 6.2.9.3-1 shows the RF component isolation parameters to derive MSD level for CA\_n1A-n3A-n78A.
+
+**Table 6.2.9.3-1: UE RF Front-end component parameters**
+
+| UE ref. architecture Component | Cascaded Diplexer-Duplexer Architecture w/ single ant. or dual ant. | | | |
+|--------------------------------|---------------------------------------------------------------------|-----------|-----------|-----------|
+| | CA_n1A-n3A-n78A | | | |
+| | IP2 (dBm) | IP3 (dBm) | IP4 (dBm) | IP5 (dBm) |
+| Ant. Switch | 110 | 65 | 55 | 45 |
+| Triplexer | 110 | 72 | 55 | 45 |
+| Diplexer | 112 | 85 | 55 | 45 |
+| Duplexer | 95 | 75 | 55 | 45 |
+| PA Forward | 27 | 30 | 28 | 27 |
+| PA Reversed | 38 | 28 | 33 | 32 |
+| LNA | 5 | -5 | -5 | -10 |
+
+Table 6.2.9.3-2 shows the isolation levels based on the RF component in Table 6.2.9.3-1.
+
+**Table 6.2.9.3-2: UE RF Front-end component isolation parameters**
+
+| Isolation Parameter | Value (dB) | Comment |
+|-----------------------|------------|-----------------------------------|
+| Antenna to Antenna | 10/15 | Main antenna to diversity antenna |
+| PA (out) to PA (in) | 60/70 | PCB isolation (PA forward mixing) |
+| Triplexer | 20 | High/low band isolation |
+| Diplexer | 25 | High/low band isolation |
+| PA (out) to PA (out) | 60 | L-H/H-L cross-band |
+| PA (out) to PA (out) | 50 | L-L/H-H cross-band |
+| LNA (in) to PA (out) | 60 | L-H/H-L cross-band |
+| LNA (in) to PA (out) | 50 | L-L/H-H cross-band |
+| Duplexer | 50 | Tx band rejection at Rx band |
+| Rx filter attenuation | 38 | n3 filter rejection over n78 |
+
+**Table 6.2.9.3-3: Comparison of MSD in n3 Rx band of NR CA\_n3A-n78A UE with different RF parameters**
+
+| | Thermal | IMD w/ ant. ISO 10dB, PCB 60dB | IMD w/ ant. ISO 10dB, PCB 60dB | IMD w/ ant. ISO 10dB, PCB 70dB | IMD w/ ant. ISO 15dB, PCB 70dB |
+|----------------------|---------|--------------------------------|--------------------------------|--------------------------------|--------------------------------|
+| Main Path (dBm) | -93 | -57.2 | -57.2 | -59.8 | -59.8 |
+| Diversity Path (dBm) | -93 | -67.1 | -71.9 | -69.4 | -74.1 |
+| After MRC (dBm) | -96 | -67.5 | -72.0 | -69.8 | -74.2 |
+| MSD (dB) | | <b>28.5</b> | <b>24.0</b> | <b>26.2</b> | <b>21.8</b> |
+
+Considering unit-to-unit variation in mass productions, it is necessary that more than 80 dB PCB isolation is supposed to be guaranteed, i.e., > 85 dB PCB isolation. In our view, it is excessive and overly tightens the implementation complexity.
+
+**Observation #5:** For the MSD improvement by dual uplink transmission, 10 dB or less improvements are feasible by enhancing antenna isolation and PCB isolation. However, 80 dB PCB isolation and 20 dB antenna isolation are quite challenging to achieve in a smart phone form-factor.
+
+## 6.3 Conclusion
+
+According to the available evaluation from companies, it was concluded in RAN4#104-bis meeting that MSD improvement is feasible [7].
+
+# 7 Study of signalling for improved lower MSD
+
+## 7.1 Possible MSD reporting approaches
+
+### 7.1.1 Candidate solution 1: MSD reporting depending on frequency region
+
+On the way to feasibility study on how much MSD improvement to be expected, it was found that it is feasible to reduce drastically MSD, in some cases, it takes a cost, e.g., increasing PCB isolation alone may not be able to achieve MSD to be zero. With this outcome in mind, there were discussion on how many thresholds to be defined for reporting MSD as well as how reported lower MSD value(s) to be utilized by gNB. All the aforementioned discussion is based on MSD in Block A according to a specified test scenario as illustrated in top right in Figure 7.1.1-1, where RAN4 has selected a combination of an aggressor UE channel bandwidth (also # of RBs) and a victim channel bandwidth so as to enable 2nd order harmonic to hit the entire spectrum in Block A as well as most of the power to be contained in Block A.
+
+
+
+The diagram illustrates the test condition for the 2nd order UL harmonic. It is divided into two frequency bands:
+
+
+- Lower band:** Contains a 5 MHz CBW (Channel Bandwidth) at frequency $f_1$ MHz.
+- Higher band:** Contains a 10 MHz bandwidth, divided into five blocks: C, B, A, B, C. Block A is the central block, centered at frequency $f_2 = 2 \times f_1$ MHz. The total width of the higher band is 60 MHz.
+- Offsets:** There are offsets of 20 MHz between the blocks in the higher band.
+- Test cases:**
+ - Case 1:** RSRP not enough high compared to MSD @ A, while MSD=0dB@B, but UE doesn't report that info. The diagram shows a status bar with 'OK', 'NG', and 'OK'.
+ - Case 2:** RSRP not enough high compared to MSD @ A, but the info of MSD=0dB@B is reported to NW. The diagram shows a status bar with 'OK', 'NG', and 'OK'.
+
+ Additional notes indicate that in Case 1, the network may use only DL resources in regions C, but if resources are reserved for other users, CA may not be configured. In Case 2, the network can get more flexibility to schedule DL resources than in Case 1.
+
+Figure 7.1.1-1: MSD test condition for 2nd UL harmonic. The diagram shows a 'Lower band' with a 5 MHz CBW at frequency f1 MHz and a 'Higher band' with a 10 MHz bandwidth divided into blocks C, B, A, B, C. Block A is centered at f2 = 2 \* f1 MHz. Offsets of 20 MHz are shown between blocks. Below the frequency diagram, two cases are shown: Case 1 where RSRP is not high enough compared to MSD @ A, and Case 2 where RSRP is not high enough but MSD info is reported to the network (NW).
+
+**Figure 7.1.1-1: MSD test condition for 2nd UL harmonic**
+
+It's noted that with respect to 2nd order harmonic case for at least PC3, it is very likely that MSD in Block C would be zero if lower MSD capability is reported provided that specified MSD for this region would be a few dB. Still, however, MSD at least in Block B remains undefined or unpredicted. It is noted that MSD undefined region is undefined is wider than Block B. When the lower edge frequency of victim channel bandwidth of X MHz is larger than $-20 - X/2 + 2 \cdot f_1$ and the higher edge frequency of victim channel bandwidth is less than $20 + X/2 + 2 \cdot f_1$ , MSD is undefined, and the value is somewhere between MSD for near-miss and MSD for direct-hit. This is quite an unfortunate situation since even if a lower MSD, e.g., 15 dB is reported, if e.g., RSRP doesn't reach a threshold, the network may avoid configuring the UE with CA, may try to configure the UE with CA using DL resource in Region C as shown in Case 1 in Figure 7.x.x-1, and/or may try to schedule UL resources in a way to minimize 2nd order harmonic impact on scheduled DL resources, but if there are other users in the same network, it may not be possible for the network to take
+
+any measures to the UE. If the network, however, clearly knows that e.g., Block B has no MSD, the UE might get higher possibility to configured with CA using DL resource in Block B and/or C as shown in Case 2 in Figure 7.1.1-1 since the network can have more flexibility in terms of available resources. Hence, clarifying MSD = 0 dB region gives network more flexibility in terms of resource allocation and UE higher possibility in terms of CA configuration as depicted in case 2 in Figure 7.1.1-1.
+
+Observation 1: Reporting from where MSD = 0 dB with respect to the center of a victim channel bandwidth in the specification(s) provides a network more flexibility to decide CA configuration as well as frequency resource scheduling, and this would increase possibility for the UE to get CA configured with.
+
+Another aspect would be there may be cases, e.g., an operator whose band doesn't have MSD in a way that the entire channel bandwidth is impacted by an MSD root cause, but rather only an upper part of the channel has MSD as can be seen in Figure 7.1.1-2.
+
+
+
+| | |
+|---------------------------------------------------------------------------|--|
+| An operator's spectrum holding | |
+| Suppose that spec says an upper part of the band has large MSD e.g., 30dB | |
+| A UE with lower MSD capability saying the MSD is 15 dB | |
+| UE with lower MSD capability and MSD zero region | |
+
+Diagram showing an operator's spectrum as a horizontal bar with a pink segment in the middle. A label 'An operator's spectrum' points to the bar. Diagram showing the operator's spectrum with a blue semi-circular shape on the right side, labeled 'Impacted by MSD, e.g., 2nd UL Harmonic'. The pink segment is still visible on the left. Diagram showing the operator's spectrum with a smaller blue semi-circular shape on the right side, labeled 'NW still may assume that this part may have MSD'. The pink segment is visible on the left. Diagram showing the operator's spectrum with a dashed line separating the pink segment from the rest, labeled 'NW can assume that MSD is zero. Hence, the NW can have more flexibility in scheduling resources in frequency domain'.
+
+**Figure 7.1.1-2: A case where a part of victim channel bandwidth is affected by MSD**
+
+Observation 2: Reporting MSD = 0 dB region can provide NW with more flexibility in terms of resource scheduling even if an operator has MSD in a limited part of their spectrum.
+
+If a UE doesn't have so-called lower MSD capability being discussed, a network may assume that the upper part of the channel bandwidth is affected by the specified MSD, e.g., 30 dB as the worst case. Even if a UE has the lower MSD capability of e.g., 15 dB, still network may consider that the upper part of the operator's spectrum has 15 dB MSD as the worst case while actually, the UE may not have MSD in the upper part of the operator's spectrum at all, i.e., MSD = 0 dB. If somehow this information is reported to the network, the operator's network resource schedule can be released from a restriction due to MSD at least within MSD = 0 dB region.
+
+Observation 3: Reporting MSD = 0 dB region can provide NW with more flexibility in terms of resource scheduling even if an operator has MSD in a limited part of their spectrum.
+
+A question may arise that if a noise due to MSD root cause is actually not flat? Figure 7.1.1-3 shows 2nd order harmonic spectrum, where horizontal axis of -1 to +1 is corresponding to a victim channel bandwidth size. It can be seen that the noise due to 2nd order harmonic sharply decrease as the position becomes close to the channel edges from the center. Hence, it would be likely that a UE with lower MSD capability can have wider MSD zero region than the UE without lower MSD capability.
+
+
+
+Figure 1: Simulated Spectral Estimate of the H2 of a near ACER limited 50RB signal. The graph shows Magnitude dB on the y-axis (from -50 to 0) versus Frequency in Hz on the x-axis (from -4 to 4, scaled by 10^7). A blue curve labeled 'squared' shows a peak magnitude near 0 dB at 0 Hz, with a sharp drop-off on both sides, reaching -50 dB at approximately ±3.5 x 10^7 Hz.
+
+Figure 7.1.1-3: H2 spectral extracted from [3]
+
+Hence, even if a UE cannot indicate $MSD = 0$ dB based on the existing MSD test condition, i.e., in the entire Block A in the top in Figure 7.1.1-4, some part of Block B may have $MSD = 0$ dB as shown in the middle in Figure 7.1.1-4. Or if a UE has better lower MSD capability, the UE may have $MSD = 0$ dB region even in inside Block A as shown in the bottom in Figure 7.1.1-4.
+
+
+
+| | Near miss | Undefined region | direct hit | Undefined region | Near miss |
+|--------------------------------------------------------------|---------------------------------------------|------------------|------------|------------------|-----------|
+| E.g., 2 <sup>nd</sup> UL harmonic | Block A | Block B | Block A | Block B | Block A |
+| A UE with Lower MSD capability, but still slightly large MSD | Distance from the center to be reported<br> | | | | |
+| A UE with Lower MSD capability, and MSD is very low | Distance from the center to be reported<br> | | | | |
+
+Diagram showing MSD regions for a UE with slightly large MSD. It consists of three blocks: MSD=0 dB (blue), Some MSD (pink), and MSD=0 dB (blue). A double-headed arrow indicates the distance from the center of the 'Some MSD' block to the start of the 'MSD=0 dB' blocks. Diagram showing MSD regions for a UE with very low MSD. It consists of three blocks: MSD=0 dB (blue), Some MSD (pink), and MSD=0 dB (blue). A double-headed arrow indicates the distance from the center of the 'Some MSD' block to the start of the 'MSD=0 dB' blocks. The 'Some MSD' block is narrower than in the previous case.
+
+Figure 7.1.1-4: relationship of MSD existence region between specification and a UE with lower MSD
+
+Observation 4: Even if a UE with better isolation still may have challenges in achieving $MSD = 0$ dB based on the existing MSD definition, i.e., Block A in Figure 7.1.1-4, but still the UE can extend $MSD = 0$ dB region with the same isolation.
+
+The information that $MSD$ is $0$ dB can be easily treated by a network since as far as a network allocates frequency resources to $MSD = 0$ dB region in the victim channel bandwidth or adjacent channel bandwidth (if CA is possible) on the side of the victim channel bandwidth that is the farthest from $MSD$ non-zero region, the resources are not affected by aggressor' uplink power(s) in the UE.
+
+With respect to test configurations, this approach does not require something special compared to the existing test configurations expect for the position of victim channel bandwidth. As can be seen in Figure 7.1.1-4, the victim channel bandwidth is placed just adjacent to $MSD$ non-zero region (lower, higher or both sides). Under this condition, UE needs to meet reference sensitivity requirements with no $MSD$ allowance.
+
+Observation 5: The information on where $MSD = 0$ dB outside a victim channel bandwidth or even inside the victim channel bandwidth can be treated by a network since $MSD$ in this region is not affected by aggressor's power(s) in a UE.
+
+Conclusion: Reporting distance between the centre of a defined victim channel bandwidth and a starting point of $MSD = 0$ dB region can be a possible way to enable network to utilize the reported information and to produce a complementary effect with a case that reported $MSD$ is a non-zero value base on existing test configurations.
+
+### 7.1.2 Candidate solution 2: MSD reporting for frequency regions affected by self-interference
+
+#### 7.1.2.1 Basic MSD information unit
+
+Based on the survey of the existing MSD specifications, the essential MSD information for a band combination includes: the cause of the MSD (such as harmonic interference, intermodulation, cross-band isolation and etc), the aggressor band(s), the victim band and the amount of MSD in dB.
+
+The first three pieces of information are correlated. After reducing the redundancy, the basic MSD information unit can be described as a 3-tuple of <MSD value, MSD source, Victim band >.
+
+The details of the basic MSD information unit are shown in Table 7.1.2.1-1 below. Note that MSD=0dB indicates no degradation of the receiver sensitivity.
+
+**Table 7.1.2.1-1: Basic MSD Information Unit for a band combination**
+
+| MSD 3-tuple | <MSD value, MSD source, Victim band> |
+|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>MSD Value</b> | The index within the set of {MSD=0dB, MSD≤Th <sub>1</sub> dB, MSD≤Th <sub>2</sub> dB, ..., MSD≤Th <sub>i</sub> dB, ..., MSD≤Th <sub>M-1</sub> dB }, where M is the total number of thresholds |
+| <b>MSD Source</b> | The index within the set of {Harmonic, Harmonic mixing, cross-band ISO, IMD <sub>n</sub> (n=2, ..., K)}, where K is the highest IMD order up to 5 in Rel-18. [Handling of order for Harmonic and Harmonic mixing is FFS]. |
+| <b>Victim Band</b> | Band number or the band index within the DL band combination |
+
+More explicitly, as per the latest 3GPP specifications, the MSD sources can be summarised in Table 7.1.2.1-2 below. However, not all the details are to be reported in order to reduce the signalling overhead.
+
+**Table 7.1.2.1-2: MSD sources**
+
+| Interference source | 3GPP notations |
+|-----------------------------|------------------------------------------------------------------|
+| <b>UL harmonic</b> | UL2/DL1, UL3/DL1, UL4/DL1, UL5/DL1 (Only direct-hit is counted.) |
+| <b>Harmonic mixing</b> | UL1/DL2, UL1/DL3, UL1/DL4, UL1/DL5, UL2/DL3, UL3/DL2, UL4/DL3 |
+| <b>Intermodulation</b> | IMD2, IMD3, IMD4, IMD5, IMD7, IMD9 |
+| <b>Cross-band Isolation</b> | ACLR1, ACLR2, >ACLR2 |
+
+In the following, some examples are given to demonstrate the basic MSD information to be reported by a UE. For different types of MSD sources, the MSD information units to be reported are shown in Table 7.1.2.1-3.
+
+**Table 7.1.2.1-3: Examples of MSD information unit.**
+
+| MSD in TS 38.101-1 | | | | | | | | MSD information unit |
+|----------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|----------------------|
+| Table 7.3A.5-1: 2DL/2UL inter-band Reference sensitivity QPSK P <sub>REFSENS</sub> and uplink/downlink configurations for PC3 CA | | | | | | | | |
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | |
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | Source of IMD |
+| CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD3 |
+| | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A |
+| CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 |
+| | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A |
+| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 <sup>4</sup> |
+| | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A |
+| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 <sup>4</sup> |
+| | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A |
+| | n3 | N/A | 5 | N/A | 1877.5 | 2.2 | FDD | IMD7 |
+| | n78 | 3305 | 10 | 1<br>(RBstart =3) | 3305 | N/A | TDD | N/A |
+| | n78 | 3780 | 10 | 1<br>(RBstart =0) | 3780 | N/A | TDD | N/A |
+| | | | | | | | | |
+
+For CA\_n1-n3:
+<MSD≤25, IMD3, n1>
+
+For CA\_n1-n78:
+<MSD≤10, IMD4, n1>
+
+For CA\_n3-n78:
+<MSD≤30, IMD2, n3>
+<MSD≤10, IMD4, n3>
+<MSD≤5, IMD7, n3>
+
+| Table 7.3A.5-2: 3DL/2UL interband Reference sensitivity QPSK PREFSENS and uplink/downlink configurations | | | | | | | | | For CA n1-n3-n78:<br><MSD≤30, IMD2, n78><br><MSD≤15, IMD4, n78><br><MSD≤30, IMD2, n3> |
+|----------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------|--------------------|-------------------------|----------|-------------|---------------|---------------------------------------------------------------------------------------|
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | |
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>RB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | | |
+| CA n1-n3-n78 | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A | |
+| | n3 | 1750 | 5 | 25 | 1845 | N/A | FDD | N/A | |
+| | n78 | 3700 | 10 | 52 | 3700 | 28.4 | TDD | IMD2 | |
+| | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A | |
+| | n3 | 1770 | 5 | 25 | 1865 | N/A | FDD | N/A | |
+| | n78 | 3360 | 10 | 52 | 3360 | 11.2 | TDD | IMD4 | |
+| | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A | |
+| | n3 | 1735 | 5 | 25 | 1830 | 27.9 | FDD | IMD2 | |
+| | n78 | 3780 | 10 | 52 | 3780 | N/A | TDD | N/A | |
+
+
+
+| Table 7.3A.4-1: Reference sensitivity exceptions and uplink/downlink configurations due to UL harmonic from a PC3 aggressor NR UL band for NR DL CA FR1 | | | | | | | | | For CA n3-n78:<br><MSD≤25, Harmonic, n78> | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------|----------------|------------------|-------|------|--------------------|----------------------|-------------------------------------------|--|
+| UL band | DL band | UL BW | SCS of UL band | UL RB Allocation | DL BW | MSD | UL/DL fc condition | UL/DL harmonic order | | |
+| | | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (dB) | | | | |
+| n3 | n78 | 5 | 15 | 25 (RBstart=0) | 10 | 23.9 | NOTE 2 | UL2/DL1 direct-hit | | |
+| n3 | n78 | 10 | 15 | 50 (RBstart=0) | 100 | 13.8 | NOTE 2 | UL2/DL1 direct-hit | | |
+| n3 | n78 | 5 | 15 | 25 (RBstart=0) | 10 | 1.1 | NOTE 6 | UL2/DL1 near-miss | | |
+
+
+
+| Table 7.3A.6-1: Reference sensitivity exceptions (MSD) and uplink/downlink configurations due to cross band isolation from a PC3 aggressor NR UL band for NR CA FR1 | | | | | | | | | | For CA n1-n3:<br><MSD≤20, Cross-band ISO, n3> | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|-----------------------------------------------|--|
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source | | |
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | | | |
+| n1 | n3 | 1922.5 | 5 | 15 | 25 (RBstart=0) | 1877.5 | 5 | 3 | >ACLR2 | | |
+| n1 | n3 | 1945 | 50 | 15 | 128 (RBstart=0) | 1877.5 | 5 | 19.7 | ACLR1 | | |
+
+Note that for the purpose of MSD improvement, a UE should perform better than the minimum requirement in order to claim the low-MSD capability. For example, if the minimum requirement falls into the interval of $MSD \leq Th_i$ dB, the UE should be able to support at least one-level lower (e.g., $MSD \leq Th_{i-1}$ dB) in order to report the low-MSD capability. If the actual MSD is larger than the maximum threshold $Th_{M-1}$ (i.e. out of range), the UE cannot report low-MSD capability for this REFSENS exception case
+
+#### 7.1.2.2 Reporting of low-MSD information
+
+##### 7.1.2.2.1 Aspect of higher order band combinations
+
+When a UE supports higher order band combinations, 3GPP specifies $\Delta T_{IB,c}$ to allow certain relaxation in Tx power requirements as well as $\Delta R_{IB,c}$ for relaxation in Rx sensitivity. Both factors can contribute to the relaxation of the MSD requirements for higher order band combinations. Hence, it's reasonable to assume that higher order band combinations supported by the UE can inherit the low-MSD capabilities from the fall-back band combinations. As a result, a UE only needs to report low-MSD information for the following types of band combinations as shown in Table 7.1.2.2.1-1.
+
+Table 7.1.2.2.1-1: Band combinations targeted for reporting low-MSD information
+
+| MSD Source | Band combination type | | |
+|---------------------------------------------------------------------------|-----------------------|---------|----------------|
+| | 1UL/2DL | 2UL/2DL | 2UL/3DL |
+| UL Harmonic | X | | |
+| Harmonic mixing | X | | |
+| Cross band isolation | X | | |
+| IMD | X <sup>2</sup> | X | X <sup>1</sup> |
+| NOTE 1: Only MSD caused by the dual-UL IMD on the third band is reported. | | | |
+| NOTE 2: IMD may occur for intra-band non-contiguous CA. | | | |
+
+##### 7.1.2.2.2 Aspect of power classes
+
+The Tx power can have significant effect on MSD, especially for that caused by high order IMD. Some examples are shown in Table 7.1.2.2.2-1. For example, regarding CA n1-n78, the MSD for IMD4 on band n1 deteriorates from 8.0dB to 17.8dB when the Tx power class is upgraded from PC3 to PC2.
+
+Table 7.1.2.2.2-1: Example MSD requirements for different power classes
+
+| MSD in TS 38.101-1 | | | | | | | | Power Class | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|----------------------------------------------------------|--|--|--|--|--|--|--|---------------|------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|--|-----------|----|------|---|----|------|------|-----|------|-----|------|----|----|------|-----|-----|-----|-----------|----|------|---|----|------|------|-----|------|-----|--------|----|----|--------|-----|-----|-----|-----------|----|------|---|----|------|------|-----|-------------------|-----|------|----|----|------|-----|-----|-----|----|------|---|----|------|------|-----|-------------------|-----|------|----|----|------|-----|-----|-----|-----|-----|---|-----|--------|-----|-----|------|-----|------|----|---|------|-----|-----|-----|--|--|------|----|--------------|------|--|--|--|--|--|--|--|---|--|--|--|--|--|--|--|--|--------------|--|--|--|--|-----|
+| <b>Table 7.3A.5-1: 2DL/2UL inter-band Reference sensitivity QPSK P<sub>REFSENS</sub> and uplink/downlink configurations for PC3 CA</b> <table border="1"> <thead> <tr> <th colspan="8">Band / Channel bandwidth / N<sub>RB</sub> / Duplex mode</th><th>Source of IMD</th></tr> <tr> <th>NR CA band combination</th><th>NR band</th><th>UL F<sub>c</sub> (MHz)</th><th>UL/DL BW (MHz)</th><th>UL C<sub>LRB</sub></th><th>DL F<sub>c</sub> (MHz)</th><th>MSD (dB)</th><th>Duplex mode</th><th></th></tr> </thead> <tbody> <tr> <td rowspan="2">CA_n1-n78</td><td>n1</td><td>1950</td><td>5</td><td>25</td><td>2140</td><td>8.0</td><td>FDD</td><td>IMD4</td></tr> <tr> <td>n78</td><td>3710</td><td>10</td><td>50</td><td>3710</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td rowspan="2">CA_n3-n41</td><td>n3</td><td>1740</td><td>5</td><td>25</td><td>1835</td><td>8.2</td><td>FDD</td><td>IMD4</td></tr> <tr> <td>n41</td><td>2657.5</td><td>10</td><td>50</td><td>2657.5</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td rowspan="6">CA_n3-n78</td><td>n3</td><td>1740</td><td>5</td><td>25</td><td>1835</td><td>26</td><td>FDD</td><td>IMD2<sup>4</sup></td></tr> <tr> <td>n78</td><td>3575</td><td>10</td><td>25</td><td>3575</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td>n3</td><td>1765</td><td>5</td><td>25</td><td>1860</td><td>8.0</td><td>FDD</td><td>IMD4<sup>4</sup></td></tr> <tr> <td>n78</td><td>3435</td><td>10</td><td>25</td><td>3435</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td>n3</td><td>N/A</td><td>5</td><td>N/A</td><td>1877.5</td><td>2.2</td><td>FDD</td><td>IMD7</td></tr> <tr> <td>n78</td><td>3305</td><td>10</td><td>1</td><td>3305</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td></td><td></td><td>3780</td><td>10</td><td>(RBstart =3)</td><td>3780</td><td></td><td></td><td></td></tr> <tr> <td></td><td></td><td></td><td></td><td>1</td><td></td><td></td><td></td><td></td></tr> <tr> <td></td><td></td><td></td><td></td><td>(RBstart =0)</td><td></td><td></td><td></td><td></td></tr> </tbody> </table> | | | | | | | | Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | | CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 8.2 | FDD | IMD4 | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 <sup>4</sup> | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 <sup>4</sup> | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A | n3 | N/A | 5 | N/A | 1877.5 | 2.2 | FDD | IMD7 | n78 | 3305 | 10 | 1 | 3305 | N/A | TDD | N/A | | | 3780 | 10 | (RBstart =3) | 3780 | | | | | | | | 1 | | | | | | | | | (RBstart =0) | | | | | PC3 |
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 8.2 | FDD | IMD4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 <sup>4</sup> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 <sup>4</sup> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n3 | N/A | 5 | N/A | 1877.5 | 2.2 | FDD | IMD7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3305 | 10 | 1 | 3305 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | 3780 | 10 | (RBstart =3) | 3780 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | | | | (RBstart =0) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| <b>Table 7.3A.5-1a: 2DL/2UL inter-band Reference sensitivity QPSK P<sub>REFSENS</sub> and uplink/downlink configurations for PC2 CA</b> <table border="1"> <thead> <tr> <th colspan="8">Band / Channel bandwidth / N<sub>RB</sub> / Duplex mode</th><th>Source of IMD</th></tr> <tr> <th>NR CA Configuration</th><th>NR band</th><th>UL F<sub>c</sub> (MHz)</th><th>UL/DL BW (MHz)</th><th>UL C<sub>LRB</sub></th><th>DL F<sub>c</sub> (MHz)</th><th>MSD (dB)</th><th>Duplex mode</th><th></th></tr> </thead> <tbody> <tr> <td rowspan="2">CA_n1-n78</td><td>n1</td><td>1950</td><td>5</td><td>25</td><td>2140</td><td>17.8</td><td>FDD</td><td>IMD4</td></tr> <tr> <td>n78</td><td>3710</td><td>10</td><td>50</td><td>3710</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td rowspan="2">CA_n3-n41</td><td>n3</td><td>1740</td><td>5</td><td>25</td><td>1835</td><td>18.4</td><td>FDD</td><td>IMD4</td></tr> <tr> <td>n41</td><td>2657.5</td><td>10</td><td>50</td><td>2657.5</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td rowspan="4">CA_n3-n78</td><td>n3</td><td>1740</td><td>5</td><td>25</td><td>1835</td><td>31.9</td><td>FDD</td><td>IMD2</td></tr> <tr> <td>n78</td><td>3575</td><td>10</td><td>50</td><td>3575</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> <tr> <td>n3</td><td>1765</td><td>5</td><td>25</td><td>1860</td><td>18.5</td><td>FDD</td><td>IMD4</td></tr> <tr> <td>n78</td><td>3435</td><td>10</td><td>50</td><td>3435</td><td>N/A</td><td>TDD</td><td>N/A</td></tr> </tbody> </table> | | | | | | | | Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | NR CA Configuration | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | | CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 17.8 | FDD | IMD4 | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 18.4 | FDD | IMD4 | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 31.9 | FDD | IMD2 | n78 | 3575 | 10 | 50 | 3575 | N/A | TDD | N/A | n3 | 1765 | 5 | 25 | 1860 | 18.5 | FDD | IMD4 | n78 | 3435 | 10 | 50 | 3435 | N/A | TDD | N/A | PC2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| NR CA Configuration | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 17.8 | FDD | IMD4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 18.4 | FDD | IMD4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 31.9 | FDD | IMD2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3575 | 10 | 50 | 3575 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n3 | 1765 | 5 | 25 | 1860 | 18.5 | FDD | IMD4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3435 | 10 | 50 | 3435 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+One option is to report the low-MSD information for each power class, or for the power class requested by the network. Effectively, a UE may be requested to report low-MSD information for Tx power at 23dBm, 26dBm or 29dBm (i.e., PC3, PC2 or PC1.5).
+
+Since each power class corresponds to one particular Tx power level, other options have been proposed to support wider range of Tx power. One option is to report the low-MSD information at a given Tx power level which is requested by the network. The Tx power level for the UE is predicted by the network using path loss estimate before a band combination is configured.
+
+##### 7.1.2.2.3 Network query based reporting
+
+A UE may support a large number of band combinations across a wide frequency range. However, a practical network uses pre-planned frequency resources and may be interested in a very limited number of band combinations. To reduce the unnecessary signalling overhead, one solution is for the network to specify certain filter conditions when enquiring the UE about its low-MSD information, for example via *UE-CapabilityRequestFilterNR* or some similar mechanism. The filter conditions may include: frequency band(s), MSD source (such as IMD order), power class, frequency range, [minimum Lower MSD class] and etc.
+
+The query of the UE low-MSD information could happen before a band combination is configured, which could help the network scheduler to optimise its resource allocation according to the reported UE capabilities.
+
+
+
+```
+
+sequenceDiagram
+ participant gNB
+ participant UE
+ Note right of gNB: With filter on e.g., band n3, n78, IMD4, PC3.
+ gNB->>UE: Enquiry on low-MSD information
+ Note left of UE: Response for low-MSD information
+ UE-->>gNB: CA_n3-n78: <MSD ≤ 10, IMD4, n3>
+ UE-->>gNB: CA_n1-n3-n78: <MSD ≤ 15, IMD4, n78>
+
+```
+
+Sequence diagram illustrating a network query on low-MSD information between a UE and a gNB. The gNB sends an 'Enquiry on low-MSD information' to the UE. The UE responds with 'Response for low-MSD information', which includes details about filters for bands n3 and n78, such as IMD4 and PC3, and specific CA configurations (CA\_n3-n78 and CA\_n1-n3-n78) with their respective MSD limits.
+
+Figure 7.1.2.2.3-1: Illustration of network query on low-MSD information
+
+###### 7.1.2.2.3.1 Effect of introducing frequency range as one of the filtering conditions
+
+When RAN4 discusses whether an MSD type like IMD falls into a victim band, RAN4 considers the respective bands' entire UL and DL frequency range(s). More specifically, when IMD2 for CA\_n3A-n77A was studied, $f_{n77} - f_{n3\_UL}$ was calculated assuming that $3300 \leq f_{n77} \leq 4200$ MHz, $1710 \leq f_{n3\_UL} \leq 1785$ MHz as UL frequency ranges by the two bands. Accordingly, $1515 \leq f_{n77} - f_{n3\_UL} \leq 2490$ MHz was derived. Since the frequency range overlaps with $1805 \leq f_{n3\_DL} \leq 1880$ MHz, MSD due to IMD2 was defined. Each operator, however, has limited frequency range(s) per operating band. Hence, MSD capabilities associated with MSD types and the associated orders that each operator is interested in may be very limited.
+
+Assume that an operator has following frequency ranges in n3 and n77, respectively.
+
+Table 7.1.2.2.3.1-1: Hypothetical frequency ranges for an operator with n3 and n77
+
+| | UL (MHz) | DL (MHz) | Width (MHz) |
+|-----|-------------|-------------|-------------|
+| n3 | 1710 - 1730 | 1805 - 1825 | 20 x 2 |
+| n77 | 3520 - 3560 | 3520 - 3560 | 40 |
+| n77 | 3700 - 3800 | 3700 - 3800 | 100 |
+| n77 | 4000 - 4100 | 4000 - 4100 | 100 |
+
+As defined in 38.101-1, CA\_n3A-n77A has multiple MSD due to several MSD types and associated orders, i.e.,
+
+- 2nd order harmonic:
+- IMD2, IMD4 and IMD7
+- Harmonic mixing (UL1/DL2)
+
+However, both IMD7 ( $5 \cdot f_{n3\_UL} - 2 \cdot f_{n77}$ ) and harmonic mixing (UL1/DL2) don't hit n3 DL if the calculation is conducted with frequency ranges in Table 7.1.2.2.3.1-1.
+
+For 2nd order harmonic and IMD2 and IMD4, according to below Figure 7.1.2.2.3.1-1, only IMD2 hits n3 DL. The frequency region to cause IMD2 is enclosed in red lines. It's noted that 4100 – 4200 MHz is clearly irrelevant so that
+
+the range is omitted from the Figure 7.1.2.2.3.1-1. Hence, in the example with Table 7.1.2.2.3.1-1, MSD values and associated information that a UE needs to report can be reduced to only one (IMD2) from five specified MSDs for CA-n3A-n78 per power class.
+
+
+
+Figure 7.1.2.2.3.1-1: Rough sketch of MSD regions for specific frequency ranges. The graph plots frequency (F\_n3\_UL in MHz) on the y-axis (1710 to 1785) against frequency (F\_n77 in MHz) on the x-axis (3250 to 3800). It shows several regions: IMD4 (3\*f\_n3\_UL - f\_n77) region (orange shaded area), 2nd UL harmonic (2\*f\_n3\_UL) with 1710 MHz+20 MHz CBW region (purple shaded area), and IMD2 (f\_n77 - f\_n3\_UL) region (blue shaded area). A small green box highlights a region around 3520-3560 MHz on the x-axis and 1730-1750 MHz on the y-axis.
+
+Figure 7.1.2.2.3.1-1: Rough sketch of MSD regions for specific frequency ranges
+
+###### 7.1.2.2.3.2 Effect of introducing network preferred minimum Lower MSD class as one of the filtering conditions
+
+It has already been agreed that the following MSD thresholds would be defined as following in Table 7.1.2.2.3.2-1:
+
+Table 7.1.2.2.3.2-1: Actual lower MSD capability signalling index
+
+| Index | Maximum allowed actual MSD (i.e. Thresholds) | Lower MSD Capability classes | Note |
+|-------|----------------------------------------------|------------------------------|------------------------|
+| 0 | 0dB | I | No degradation |
+| 1 | 3 dB | II | Actual MSD $\leq$ 3dB |
+| 2 | 6 dB | III | Actual MSD $\leq$ 6dB |
+| 3 | 9 dB | IV | Actual MSD $\leq$ 9dB |
+| 4 | 12 dB | V | Actual MSD $\leq$ 12dB |
+| 5 | 15 dB | VI | Actual MSD $\leq$ 15dB |
+| 6 | 18 dB | VII | Actual MSD $\leq$ 18dB |
+| 7 | 22dB | VIII | Actual MSD $\leq$ 22dB |
+
+However, there are still views that this granularity is much finer than the network really needs, depending on how to use this capability by the network. For example, the network may simply use one MSD value as a threshold to set different scheduling method for a particular band / BC, and some minor refinements such as a few dB in relative higher region, e.g 18dB -> 15 or 12 dB, may not that meaningful for the network. In this case, even the UE may be qualified for “Lower MSD” in a certain scenario including band/MSD type etc, the network may simply treat this UE the same to a UE which only satisfy minimum MSD requirement, and the signalling of Lower MSD for this particular scenario, might actually not be needed by the network.
+
+In another word, depending on how the network would utilize Lower MSD capability class, the lower MSD capable UE for a certain scenario may not be differentiated by the network with UE only satisfy minimum MSD requirements, particularly if the lower MSD capability class is relatively large.
+
+Based on this condition, a network preferred minimum Lower MSD capability class can be considered as another filter parameter for reducing capability reporting. For example, if network would only consider a maximum allowed 6dB MSD for harmonic interference for n3-n78 harmonics interference for n78, it can consider using the lower MSD capability class as a filtering parameter, and set up the maximum allowed report class as III (index 2), which corresponds to a maximum allowed actual MSD of 6dB. In this case, the UE would report the lower MSD class for this scenario if it can satisfy class I or II or III. If the UE support lower MSD but can only achieve lower MSD class larger than III, the UE would not report the capability since anyway the network would treat it the same to UE only support minimum requirements.
+
+In this way, the signalling overhead is saved based on network needs. Though the UE may lose the opportunity to report in the condition, those reporting would anyway be meaningless since network would no use it and explicitly indicted. Furthermore, the whole scheme is well controlled by the network.
+
+### 7.1.3 Candidate solution 3: MSD reporting for frequency regions affected by self-interference
+
+#### 7.1.3.1 Basic MSD information unit
+
+Based on the survey of the existing MSD specifications, there are types of MSD mechanism includes: uplink(aggressor) harmonic, receiver harmonic mixing, cross-band isolation, intermodulation and etc. The aggressor power class also have direct impact on the victim band and the amount of MSD in dB.
+
+The improved lower MSD capability signalling shall include its mechanism, aggressor order, aggressor power class and improved MSD values per victim band. The lower MSD capability signalling can be specified as per victim band per BC as a 2-tuple of < MSD mechanism/Aggressor power class and its order, MSD value >. This can save 1-tuple signaling overhead on adaptive network signalling approach comparing to 3-tuple signalling element.
+
+Some examples are given below to demonstrate the improved MSD reporting information for different types of MSD mechanisms. Table 7.1.3.1-1 referred from [3] for ease of understanding. For one mechanism same aggressor power class, order and victim order, only the worst MSD value after improvement is reported to reduce unnecessary signalling overhead. All the MSD in existing specs are within the scope of lower MSD capability reporting. Further, if new MSD type is identified and specified by RAN4 in the future, the new MSD type can also be considered for indicating lower MSD capability
+
+UE would not be allowed to report the lower MSD capability if there's no improvement.
+
+**Table 7.1.3.1-1: Information element examples of improved MSD reporting per BC for non-threshold based approach**
+
+| MSD in TS 38.101-1 | MSD information unit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------|---------------------------------|-------------------------|----------|-------------|-------------------|--|----------------------------------------------------------|--|--|--|--|--|--|--|---------------|------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|----------|----|------|---|----|------|----|-----|------|----|------|---|----|------|-----|-----|-----|-----------|----|------|---|----|------|-----|-----|------|-----|------|----|----|------|-----|-----|-----|-----------|----|------|---|----|------|----|-----|-------------------|-----|------|----|----|------|-----|-----|-----|----|------|---|----|------|-----|-----|-------------------|-----|------|----|----|------|-----|-----|-----|----|-----|---|-----|--------|-----|-----|------|-----|------|----|---|------|-----|-----|-----|-----|------|----|---------------------------------|------|-----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <table border="1" style="width: 100%; border-collapse: collapse;"> <thead> <tr> <th colspan="9"><b>Table 7.3A.5-1: 2DL/2UL inter-band Reference sensitivity QPSK P<sub>REFSENS</sub> and uplink/downlink configurations for PC3 CA</b></th> </tr> <tr> <th colspan="8">Band / Channel bandwidth / N<sub>RB</sub> / Duplex mode</th> <th rowspan="2">Source of IMD</th> </tr> <tr> <th>NR CA band combination</th> <th>NR band</th> <th>UL F<sub>c</sub> (MHz)</th> <th>UL/DL BW (MHz)</th> <th>UL C<sub>LRB</sub></th> <th>DL F<sub>c</sub> (MHz)</th> <th>MSD (dB)</th> <th>Duplex mode</th> </tr> </thead> <tbody> <tr> <td rowspan="2">CA_n1-n3</td> <td>n1</td> <td>1950</td> <td>5</td> <td>25</td> <td>2140</td> <td>23</td> <td>FDD</td> <td>IMD3</td> </tr> <tr> <td>n3</td> <td>1760</td> <td>5</td> <td>25</td> <td>1855</td> <td>N/A</td> <td>TDD</td> <td>N/A</td> </tr> <tr> <td rowspan="2">CA_n1-n78</td> <td>n1</td> <td>1950</td> <td>5</td> <td>25</td> <td>2140</td> <td>8.0</td> <td>FDD</td> <td>IMD4</td> </tr> <tr> <td>n78</td> <td>3710</td> <td>10</td> <td>50</td> <td>3710</td> <td>N/A</td> <td>TDD</td> <td>N/A</td> </tr> <tr> <td rowspan="7">CA_n3-n78</td> <td>n3</td> <td>1740</td> <td>5</td> <td>25</td> <td>1835</td> <td>26</td> <td>FDD</td> <td>IMD2<sup>4</sup></td> </tr> <tr> <td>n78</td> <td>3575</td> <td>10</td> <td>25</td> <td>3575</td> <td>N/A</td> <td>TDD</td> <td>N/A</td> </tr> <tr> <td>n3</td> <td>1765</td> <td>5</td> <td>25</td> <td>1860</td> <td>8.0</td> <td>FDD</td> <td>IMD4<sup>4</sup></td> </tr> <tr> <td>n78</td> <td>3435</td> <td>10</td> <td>25</td> <td>3435</td> <td>N/A</td> <td>TDD</td> <td>N/A</td> </tr> <tr> <td>n3</td> <td>N/A</td> <td>5</td> <td>N/A</td> <td>1877.5</td> <td>2.2</td> <td>FDD</td> <td>IMD7</td> </tr> <tr> <td>n78</td> <td>3305</td> <td>10</td> <td>1</td> <td>3305</td> <td>N/A</td> <td>TDD</td> <td>N/A</td> </tr> <tr> <td>n78</td> <td>3780</td> <td>10</td> <td>(RBstart=3)<br/>1<br/>(RBstart=0)</td> <td>3780</td> <td>N/A</td> <td>TDD</td> <td>N/A</td> </tr> </tbody> </table> | <b>Table 7.3A.5-1: 2DL/2UL inter-band Reference sensitivity QPSK P<sub>REFSENS</sub> and uplink/downlink configurations for PC3 CA</b> | | | | | | | | | Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD3 | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A | CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 <sup>4</sup> | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 <sup>4</sup> | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A | n3 | N/A | 5 | N/A | 1877.5 | 2.2 | FDD | IMD7 | n78 | 3305 | 10 | 1 | 3305 | N/A | TDD | N/A | n78 | 3780 | 10 | (RBstart=3)<br>1<br>(RBstart=0) | 3780 | N/A | TDD | N/A | For CA_n1-n3:<br>Victim n1: <PC3IMD3, 17><br><br>For CA_n1-n78:<br>Victim n1: <PC3IMD4, 4><br><br>For CA_n3-n78:<br>Victim n3: <PC3IMD2, 19><br>Victim n3: <PC3IMD4, 4><br>Victim n3: <PC3IMD7, 0> |
+| <b>Table 7.3A.5-1: 2DL/2UL inter-band Reference sensitivity QPSK P<sub>REFSENS</sub> and uplink/downlink configurations for PC3 CA</b> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 <sup>4</sup> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 <sup>4</sup> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n3 | N/A | 5 | N/A | 1877.5 | 2.2 | FDD | IMD7 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3305 | 10 | 1 | 3305 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+| | n78 | 3780 | 10 | (RBstart=3)<br>1<br>(RBstart=0) | 3780 | N/A | TDD | N/A | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
+
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------|
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n1-n3-n78 | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A |
+| | n3 | 1750 | 5 | 25 | 1845 | N/A | FDD | N/A |
+| | n78 | 3700 | 10 | 52 | 3700 | 28.4 | TDD | IMD2 |
+| | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A |
+| | n3 | 1770 | 5 | 25 | 1865 | N/A | FDD | N/A |
+| | n78 | 3360 | 10 | 52 | 3360 | 11.2 | TDD | IMD4 |
+| | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A |
+| | n3 | 1735 | 5 | 25 | 1830 | 27.9 | FDD | IMD2 |
+| | n78 | 3780 | 10 | 52 | 3780 | N/A | TDD | N/A |
+
+For CA\_n1-n3-n78:
+Victim n78: <PC3IMD2, 19>
+Victim n78: <PC3IMD4, 6>
+Victim n3: <PC3IMD2, 19>
+
+| UL band | DL band | UL BW | SCS of UL band | UL RB Allocation | DL BW | MSD | UL/DL fc condition | UL/DL harmonic order |
+|---------|---------|-------|----------------|------------------|-------|------|--------------------|----------------------|
+| | | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (dB) | | |
+| n3 | n78 | 5 | 15 | 25 (RBstart=0) | 10 | 23.9 | NOTE 2 | UL2/DL1 direct-hit |
+| n3 | n78 | 10 | 15 | 50 (RBstart=0) | 100 | 13.8 | NOTE 2 | UL2/DL1 direct-hit |
+| n3 | n78 | 5 | 15 | 25 (RBstart=0) | 10 | 1.1 | NOTE 6 | UL2/DL1 near-miss |
+
+For CA\_n3-n78:
+Victim n78: <PC3UL2DL1, 17>
+
+| UL band | DL band | UL F <sub>c</sub> | UL BW | SCS of UL band | UL RB Allocation | DL F <sub>c</sub> | DL BW | MSD | Cross-band Interference source |
+|---------|---------|-------------------|-------|----------------|------------------|-------------------|-------|------|--------------------------------|
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | |
+| n1 | n3 | 1922.5 | 5 | 15 | 25 (RBstart=0) | 1877.5 | 5 | 3 | >ACLR2 |
+| n1 | n3 | 1945 | 50 | 15 | 128 (RBstart=0) | 1877.5 | 5 | 19.7 | ACLR1 |
+
+For CA\_n1-n3:
+Victim n3: <PC3XB, 11>
+
+An alternative expression on the information element of low-MSD reporting can also be a few bits index that pointed to some actual MSD values like the examples below,
+
+**Table 7.1.3.1-2: Information element examples of improved MSD reporting per BC for threshold-based approach**
+
+| MSD in TS 38.101-1 | | | | | | | | MSD information unit |
+|----------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|----------------------|
+| Table 7.3A.5-1: 2DL/2UL inter-band Reference sensitivity QPSK P <sub>REFSENS</sub> and uplink/downlink configurations for PC3 CA | | | | | | | | |
+| Band / Channel bandwidth / N <sub>RB</sub> / Duplex mode | | | | | | | | Source of IMD |
+| NR CA band combination | NR band | UL F <sub>c</sub> (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL F <sub>c</sub> (MHz) | MSD (dB) | Duplex mode | |
+| CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD3 |
+| | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A |
+| CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 |
+| | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A |
+| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 <sup>a</sup> |
+| | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A |
+| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 <sup>a</sup> |
+| | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A |
+| | n3 | N/A | 5 | N/A | 1877.5 | 2.2 | FDD | IMD7 |
+| | n78 | 3305 | 10 | 1 (RBstart=3) | 3305 | N/A | TDD | N/A |
+| | n78 | 3780 | 10 | 1 (RBstart=0) | 3780 | | | |
+| | n78 | 3780 | 10 | 1 (RBstart=0) | 3780 | | | |
+
+For CA\_n1-n3:
+Victim n1: <PC3IMD3, index 7>
+
+For CA\_n1-n78:
+Victim n1: <PC3IMD4, index 2>
+
+For CA\_n3-n78:
+Victim n3: <PC3IMD2, index 7>
+Victim n3: <PC3IMD4, index 3>
+Victim n3: <PC3IMD7, index 2>
+
+| Table 7.3A.5-2: 3DL/2UL interband Reference sensitivity QPSK PREFSENS and uplink/downlink configurations | | | | | | | | For CA_n1-n3-n78:<br>Victim n78: <PC3IMD2, index 7><br>Victim n78: <PC3IMD4, index 2><br>Victim n3: <PC3IMD2, index 7> |
+|----------------------------------------------------------------------------------------------------------|---------|-------------|----------------|---------------------|-------------|----------|-------------|------------------------------------------------------------------------------------------------------------------------|
+| Band / Channel bandwidth / NRB / Duplex mode | | | | | | | | |
+| NR CA band combination | NR band | UL Fc (MHz) | UL/DL BW (MHz) | UL C <sub>LRB</sub> | DL Fc (MHz) | MSD (dB) | Duplex mode | Source of IMD |
+| CA_n1-n3-n78 | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A |
+| | n3 | 1750 | 5 | 25 | 1845 | N/A | FDD | N/A |
+| | n78 | 3700 | 10 | 52 | 3700 | 28.4 | TDD | IMD2 |
+| | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A |
+| | n3 | 1770 | 5 | 25 | 1865 | N/A | FDD | N/A |
+| | n78 | 3360 | 10 | 52 | 3360 | 11.2 | TDD | IMD4 |
+| | n1 | 1950 | 5 | 25 | 2140 | N/A | FDD | N/A |
+| | n3 | 1735 | 5 | 25 | 1830 | 27.9 | TDD | IMD2 |
+| | n78 | 3780 | 10 | 52 | 3780 | N/A | TDD | N/A |
+
+
+
+| Table 7.3A.4-1: Reference sensitivity exceptions and uplink/downlink configurations due to UL harmonic from a PC3 aggressor NR UL band for NR DL CA FR1 | | | | | | | | | For CA_n3-n78:<br>Victim n78: <PC3UL2DL1, index 6> | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------|----------------|------------------|-------|------|--------------------|----------------------|----------------------------------------------------|--|
+| UL band | DL band | UL BW | SCS of UL band | UL RB Allocation | DL BW | MSD | UL/DL fc condition | UL/DL harmonic order | | |
+| | | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (dB) | | | | |
+| n3 | n78 | 5 | 15 | 25 (RBstart=0) | 10 | 23.9 | NOTE 2 | UL2/DL1 direct-hit | | |
+| n3 | n78 | 10 | 15 | 50 (RBstart=0) | 100 | 13.8 | NOTE 2 | UL2/DL1 direct-hit | | |
+| n3 | n78 | 5 | 15 | 25 (RBstart=0) | 10 | 1.1 | NOTE 6 | UL2/DL1 near-miss | | |
+
+
+
+| Table 7.3A.6-1: Reference sensitivity exceptions (MSD) and uplink/downlink configurations due to cross band isolation from a PC3 aggressor NR UL band for NR CA FR1 | | | | | | | | | | For CA_n1-n3:<br>Victim n3: <PC3XB, index 4> | |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--------|-------|----------------|------------------|--------|-------|------|--------------------------------|----------------------------------------------|--|
+| UL band | DL band | UL Fc | UL BW | SCS of UL band | UL RB Allocation | DL Fc | DL BW | MSD | Cross-band Interference source | | |
+| | | (MHz) | (MHz) | (kHz) | L <sub>CRB</sub> | (MHz) | (MHz) | (dB) | | | |
+| n1 | n3 | 1922.5 | 5 | 15 | 25 (RBstart=0) | 1877.5 | 5 | 3 | >ACLR2 | | |
+| n1 | n3 | 1945 | 50 | 15 | 128 (RBstart=0) | 1877.5 | 5 | 19.7 | ACLR1 | | |
+
+where the reported index can be pointed to an agreed MSD values in Table 7.1.2.2.3.2-1.
+
+#### 7.1.3.2 Reporting of low-MSD information
+
+As for how to report the lower MSD capability, several promising options for allowing a UE to signal improved lower MSD performance have been discussed [R4-2306590]. It is also agreed that the MSD mechanisms, orders and values in existing specs shall all be considered as starting point. Considering there are many MSD mechanisms and the order of aggressor could be up to 9 in existing specs, if UE need to signal all improved MSD information, the signaling overhead might be quite large. One approach with signaling the essential information as well as the idea to reduce signaling overhead is network can require UE only to report the top K largest MSD values together with its mechanism indexing and improved MSD values. For example K = 1,
+
+If K=1, Network scheduling with reference on top largest value of reported lower MSD
+
+
+
+The diagram shows a gNB (blue rectangle) sending an enquiry to two UEs, UE1 (green rectangle) and UE2 (green rectangle). The enquiry is labeled 'Enquiry on top largest(K=1) low-MSD information'. UE1 responds with 'UE1<PC3XB, value 1>' and UE2 responds with 'UE2<PC3IMD4, value 2>'. The gNB then performs 'Adaptive scheduling' (indicated by a double-headed arrow). The victim bands are identified as 'Victim band per BC'.
+
+Diagram illustrating network query on low-MSD information for K=1. A gNB sends an 'Enquiry on top largest(K=1) low-MSD information' to UE1 and UE2. UE1 responds with 'UE1' and UE2 responds with 'UE2'. The gNB then performs 'Adaptive scheduling' based on these values. The victim bands are identified as 'Victim band per BC'.
+
+Figure 7.1.3.2-1 Example illustration of network query on low-MSD information, K=1
+
+If K=2, Network scheduling with reference on top two largest value of reported lower MSD
+
+
+
+Figure 7.1.3.2-2: Example illustration of network query on low-MSD information, K=2. The diagram shows a gNB (blue rectangle) sending an 'Enquiry on top largest(K=2) low-MSD information' (yellow arrow) to UE1 (green rectangle) and UE2 (green rectangle). A double-headed arrow labeled 'Adaptive scheduling' connects the gNB to the UEs. To the right, under 'Victim band per BC', UE1 reports 'UE1' and ''. UE2 reports 'UE2' and ''. Vertical ellipsis indicates more UEs.
+
+Figure 7.1.3.2-2 Example illustration of network query on low-MSD information, K=2
+
+Or alternative low-MSD signaling expression:
+
+If K=1, Network scheduling with reference on top largest value of reported lower MSD
+
+
+
+Figure 7.1.3.2-3: Example illustration of network query on low-MSD information, K=1. The diagram shows a gNB (blue rectangle) sending an 'Enquiry on top largest(K=1) low-MSD information' (yellow arrow) to UE1 (green rectangle) and UE2 (green rectangle). A double-headed arrow labeled 'Adaptive scheduling' connects the gNB to the UEs. To the right, under 'Victim band per BC', UE1 reports 'UE1'. UE2 reports 'UE2'. Vertical ellipsis indicates more UEs.
+
+Figure 7.1.3.2-3 Example illustration of network query on low-MSD information, K=1
+
+
+
+Figure 7.1.3.2-4: Example illustration of network query on low-MSD information, K=2. The diagram shows a gNB (blue rectangle) sending an 'Enquiry on top largest(K=2) low-MSD information' (yellow arrow) to UE1 (green rectangle) and UE2 (green rectangle). A double-headed arrow labeled 'Adaptive scheduling' connects the gNB to the UEs. To the right, under 'Victim band per BC', UE1 reports 'UE1' and ''. UE2 reports 'UE2' and ''. Vertical ellipsis indicates more UEs.
+
+Figure 7.1.3.2-4 Example illustration of network query on low-MSD information, K=2
+
+With such adaptive signalling approach, UE does not need to report all low-MSD information over all supported band combinations. UE may also not need to restore all improved low-MSD points, it only needs to restore top K largest low-MSD information which can save the size of UE memory to smaller one. Network also does not need to restore large amount of low-MSD information that only a few of them are interested band combinations.
+
+## 7.2 Conclusion
+
+With the conclusion that MSD improvement is feasible, RAN4 continues the study on approaches for a UE to indicate the improved lower MSD performance based on the progress of the study phase and reached the following agreements which could be utilized to specify the related signaling:
+
+- Essential information considered by RAN4 for the capability
+ - Victim band
+ - MSD type (harmonic; harmonic mixing; cross band isolation; IMD) with orders
+ - MSD indication of corresponding threshold (or capability class)
+
+- Power class
+- MSD for different power classes
+ - UE reports the lower MSD capability class per MSD type for the highest supported power class for the band combination
+ - UE can additionally report lower MSD capability class per MSD type for other power classes if requested by the network/regulator
+- MSD orders
+ - No need to report the order for harmonic/ harmonic mixing/cross band isolation MSD types
+ - Lower MSD capability class reported should apply for all specified orders of the MSD type
+ - IMD order is up to 5 in Rel-18
+- MSD types
+ - The following MSD types/orders are agreed to be reported based on the existing spec
+ - Harmonic, harmonic mixing, crossband isolation, IMD with order=2/3/4/5
+ - It is agreed to add a new special lower MSD type as “ALL”, which means all above mentioned MSD types/orders could meet the reported lower MSD threshold/lower MSD capability class. “ALL” is defined per victim band per BC
+ - Type “ALL” denotes the actual MSD values for harmonic/harmonic mixing/cross band isolation/IMD2,3,4,5 if any existing are all under the reported lower MSD capability threshold for a victim band with a band combination
+ - It is noted that for a certain victim band per BC, additional MSD type(s) and/or new MSD types could be introduced in future releases.
+ - If UE reports “ALL” MSD type, it does not mean that UE always suffer from all MSD types included in the LS to RAN2 in R4-2310276. There is no change in the applicable MSD types for the “ALL” type as communicated to RAN2 previously.
+ - All above mentioned MSD types could be related to different UL configurations, e.g.
+
+| UL configuration | MSD type | Support of reporting in Rel-18 |
+|-------------------------------------|----------------------------------------------------------|--------------------------------|
+| 1UL with 1CC in one aggressor band | UL harmonic, harmonic mixing and crossband isolation MSD | Yes |
+| 1UL with 2CC in one aggressor band | IMD MSD by Intra-band UL CA | No |
+| 2UL with 2CC in two aggressor bands | IMD MSD by Inter-band UL CA | Yes |
+| 2UL with 3CC in two aggressor bands | Triple beat MSD | No |
+
+It was agreed by RAN4 that MSD caused by triple beat and intra-band UL CA as well as UL configurations are not considered by RAN4 for lower MSD reporting in Rel-18, but some additional MSD types caused by different UL configurations may be considered in future release.
+
+- Candidate MSD thresholds
+ - 3-bit signalling will be used for reporting thresholds
+ - The maximum value of threshold is 22 dB
+ - The minimum reporting value for threshold is 0 dB, i.e., no degradation relative to REFSENS
+
+| Index | Maximum allowed actual MSD<br>(i.e. Thresholds) | Lower MSD<br>Capability classes | Note |
+|-------|-------------------------------------------------|---------------------------------|------------------------|
+| 0 | 0 dB | I | No degradation |
+| 1 | 3 dB | II | Actual MSD $\leq$ 3dB |
+| 2 | 6 dB | III | Actual MSD $\leq$ 6dB |
+| 3 | 9 dB | IV | Actual MSD $\leq$ 9dB |
+| 4 | 12 dB | V | Actual MSD $\leq$ 12dB |
+| 5 | 15 dB | VI | Actual MSD $\leq$ 15dB |
+| 6 | 18 dB | VII | Actual MSD $\leq$ 18dB |
+| 7 | 22 dB | VIII | Actual MSD $\leq$ 22dB |
+
+- Lower MSD capability for higher order combination
+ - For 2-bands combination, the MSD indication of corresponding threshold (or capability class) are supposed to be reported separately as per victim band per MSD type per band combination
+ - For 3-bands combination, the MSD indication of corresponding threshold (or capability class) are only reported for IMD of dual UL falling into the third band DL whose UL band is not configured with, other kinds of Lower MSD capability (harmonic/ harmonic mixing/cross band isolation/IMD due to dual UL falling into own DL) could inherit from 2-band combinations with the same power class.
+ - For combination with more than 3 bands, no need to report the Lower MSD capability any more, the capability could inherit from the fallback combinations with the same power class.
+- Others
+ - No dynamic signaling scheme will be introduced for lower MSD report in Rel-18
+
+Apart from the above agreements reached in RAN4 to facilitate the lower MSD capability signaling design, RAN4 also had some discussion for the possible MSD reporting approaches, which can refer to clauses 7.1.1-7.1.3.
+
+In addition, RAN4 had extensive discussion on signaling overhead reduction, which would be left to RAN2 for further consideration during the signaling design.
+
+# Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-----------------|------------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2022-08 | RAN4 #104-e | R4-2213728 | | | | TR skeleton for lower MSD for inter-band CA/EN-DC/DC combinations | 0.0.1 |
+| 2022-10 | RAN4 #104-bis-e | R4-2216675 | | | | R4-2217724, TP for TR 38.881 Example band combinations for lower MSD | 0.1.0 |
+| 2022-11 | RAN4 #105 | R4-2219568 | | | | R4-2220513, TP for TR 38.881 Feasibility study for lower MSD improvement | 0.2.0 |
+| 2023-02 | RAN4 #106 | R4-2302370 | | | | R4-2301097, TP for 38.881 on feasible study<br>R4-2303520, TR handling and TP on possible Lower MSD signaling for TR 38.881 | 0.3.0 |
+| 2023-04 | RAN4 #106-bis-e | R4-2305563 | | | | R4-2306593, TP for TR38881 on the signalling design for low-MSD capability | 0.4.0 |
+| 2023-05 | RAN4 #107 | R4-2307145 | | | | R4-2307089, TP for TR 38.881 update of MSD 0 dB region approach<br>R4-2308926, TP for TR 38.881 on the signalling design for low-MSD capability | 0.5.0 |
+| 2023-08 | RAN4 #108 | R4-2312246 | | | | R4-2311054, TP for TR 38.881 on a possible signaling overhead reduction approach | 0.6.0 |
+| 2023-10 | RAN4 #108bis | R4-2315237 | | | | R4-2315833, TP for TR 38.881 on a possible scheme for signaling overhead reduction<br>R4-2315241, TP for TR 38.881: draft conclusion for lower MSD capability | 0.7.0 |
+| 2023-11 | RAN4 #109 | R4-2319732 | | | | R4-2318444, TP on TR38.881 to update contents based on agreements | 0.8.0 |
+| 2023-12 | RAN#102 | RP-233187 | | | | Presentation of TR 38.881 v1.0.0 to TSG RAN | 1.0.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2023-12 | RAN#102 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/41_series/41101/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/41_series/41101/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05425a22b62855d2530d0df668ac0ef8e9e01e93
--- /dev/null
+++ b/marked/Rel-18/41_series/41101/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c966fafec375fad50350b0db0c2999ee0b40e3b2564a19e770c88b8700ff483
+size 8164
diff --git a/marked/Rel-18/41_series/41101/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/41_series/41101/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7b69246f9f4146e1e189541a907b72466d220fb
--- /dev/null
+++ b/marked/Rel-18/41_series/41101/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6964801ebb4ca8d410c346cbd01ba57d99aa1d72d65fc8f03dabbb509bfa48aa
+size 17336
diff --git a/marked/Rel-18/41_series/41101/raw.md b/marked/Rel-18/41_series/41101/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9a68e09599dcbb52bdd07973d1ce966243a5551f
--- /dev/null
+++ b/marked/Rel-18/41_series/41101/raw.md
@@ -0,0 +1,187 @@
+
+
+# 3GPP TS 41.101 V18.1.0 (2025-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for a GERAN-based 3GPP system (Release 18)**
+
+
+
+**GSMA<sup>®</sup>**
+GLOBAL SYSTEM FOR
+MOBILE COMMUNICATIONS
+
+GSMA logo
+
+
+
+**3GPP<sup>™</sup>**
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>™</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP<sup>™</sup> system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## --- **Keywords**
+
+GSM, architecture
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+- Foreword ..... 4
+- 1 Scope..... 5
+- 2 References..... 5
+- 3 Abbreviations ..... 5
+- 4 General ..... 5
+- 5 Specifications and Reports..... 5
+- Annex A (informative): Change history..... 6**
+
+## --- 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
+
+The present document identifies the 3GPP system specifications for Release 18. The specifications and reports of this Release have a major version number 18 (i.e. 18.x.y). The listed Specifications are required to build a system based on GERAN radio technology.
+
+## --- 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 21.900: "Technical Specification Group working methods".
+
+## --- 3 Abbreviations
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] apply.
+
+## --- 4 General
+
+The numbering scheme for specifications is described in 3GPP TR 21.900 [2].
+
+## --- 5 Specifications and Reports
+
+The list of Technical Specifications and Technical Reports can be found at <https://portal.3gpp.org/Specifications.aspx?q=1&tbid=All&releases=193&draft=False&underCC=True&withACC=False&withBCC=False&tech=1&numberNYA=False>
+
+NOTE 1: The padlock icon on the right of each row indicates whether or not the documents are intended for adoption by the partner Standards Development Organizations as their own publications. Those with a padlock icon are internal working documents of the 3GPP TSGs.
+
+NOTE 2: Some of the algorithm specifications in the 35.-series are available only under licence.
+
+NOTE 3: "Type" indicates Technical Specification (TS) or Technical Report (TR).
+
+NOTE 4: Void.
+
+## Annex A (informative): Change history
+
+| Change history | | | | | | | |
+|----------------|-------|-----------|-----|-----|-------------------------------------------------------------------|------------------------------|--|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New version | |
+| 2001-06 | SP-12 | SP-010278 | - | - | First draft | 3GPP TS 41.103 version 0.0.0 | |
+| 2001-06-20 | SP-12 | SP-010384 | | | updates table of specs | 0.1.0 | |
+| 2001-09-12 | SP-13 | SP-010421 | | | updates table of specs | 1.0.0 | |
+| 2002-03-04 | SP-15 | SP-020098 | | | updates table of specs; adds columns for freeze info | 1.1.0 | |
+| 2002-03-13 | SP-15 | SP-020203 | | | updates table of specs | 1.2.0 | |
+| 2002-06-03 | SP-16 | SP-020274 | | | updates table of specs, minor corrections | 2.0.0 | |
+| 2002-06-11 | SP-16 | SP-020401 | | | updates table of specs, minor corrections | 2.1.0 | |
+| 2002-06-12 | SP-16 | SP-020411 | | | updates table of specs; sets unknown freeze target dates blank | 2.2.0 | |
+| | SP-16 | | | | approved | 5.0.0 | |
+| 2002-09 | SP-17 | SP-020616 | 001 | 1 | update list of specs; editorial corrections to spec titles | 5.1.0 | |
+| 2002-12 | SP-18 | SP-020833 | 002 | 1 | Correction to list of specs, editorial corrections to spec titles | 5.2.0 | |
+| 2003-03 | SP-19 | SP-030077 | 003 | 1 | Correction to list of specs, editorial corrections to spec titles | 5.3.0 | |
+| 2003-06 | SP-20 | SP-030229 | 004 | | Correction to list of specs | 3GPP TS 41.101 version 5.4.0 | |
+| | | SP-030235 | | | Renumber from 41.103 to 41.101 | | |
+| 2003-12 | SP-22 | SP-030574 | 001 | | Correction to list of specs, editorial corrections to spec titles | 5.5.0 | |
+| 2004-01 | | | | | Correction to typo in previous line of this table. | 5.5.1 | |
+| 2004-01 | | | | | Correction to typo on cover page | 5.5.2 | |
+| 2004-03 | SP-23 | SP-040221 | 003 | | Corrections to list of specifications | 5.6.0 | |
+| 2004-06 | SP-24 | SP-040358 | 005 | | Corrections to list of specifications | 5.7.0 | |
+| 2004-09 | SP-25 | SP-040604 | 007 | | Corrections to list of specifications | 5.8.0 | |
+| 2004-12 | SP-26 | SP-040880 | 009 | 1 | Corrections to list of specifications | 6.0.0 | |
+| 2005-03 | SP-27 | SP-050126 | 012 | | Corrections to list of specifications | 6.1.0 | |
+| 2005-06 | SP-28 | SP-050356 | 013 | | Corrections to list of specifications | 6.2.0 | |
+| 2005-09 | SP-29 | SP-050470 | 014 | | Change instances of Release 5 to Release 6 | 6.3.0 | |
+| | | SP-050462 | 016 | | Corrections to list of specifications | | |
+| 2005-12 | SP-30 | SP-050845 | 017 | 1 | Corrections to list of specifications | 6.4.0 | |
+| 2006-03 | SP-31 | SP-060167 | 019 | | Corrections to list of specifications | 6.5.0 | |
+| 2006-09 | SP-33 | SP-060613 | 020 | | Corrections to list of specifications | 6.6.0 | |
+| 2006-12 | SP-34 | SP-060901 | 021 | | Correction to list of Specs | 6.7.0 | |
+| 2007-03 | SP-35 | SP-070188 | 024 | | Correction to list of Specs | 6.8.0 | |
+| 2007-06 | SP-36 | SP-070344 | 025 | | Correction to list of Specs | 6.9.0 | |
+| 2007-09 | SP-37 | SP-070519 | 026 | | Upgrade to Rel-7 | 7.0.0 | |
+| 2007-12 | SP-38 | SP-070770 | 030 | | Correction to list of Specs | 7.1.0 | |
+| | | | 034 | | Update of informative text | | |
+| 2008-12 | SP-42 | SP-080722 | 035 | 1 | Correction to list of Specs | 7.2.0 | |
+| 2009-03 | SP-43 | SP-090033 | 038 | 1 | List of Rel-8 specifications | 8.0.0 | |
+| 2009-06 | SP-44 | SP-090382 | 039 | 1 | Correction to list of specifications | 8.1.0 | |
+| 2009-12 | SP-46 | SP-090695 | 044 | 1 | Correction to list of specifications | 8.2.0 | |
+| 2010-03 | SP-47 | SP-10012 | 045 | | Update list of specs | 9.0.0 | |
+| 2011-03 | SP-51 | | | | Upgrade on freezing of Release | 10.0.0 | |
+| 2011-06 | SP-52 | SP-110298 | 047 | | Correction to list of specifications | 10.1.0 | |
+| 2012-03 | SP-55 | SP-120114 | 051 | 1 | Changes to list of Specs: GERAN systems | 10.2.0 | |
+| 2013-03 | SP-59 | SP-130155 | 052 | | Update to list of specs | 10.3.0 | |
+| 2013-03 | SP-59 | SP-130155 | 053 | | Update to list of specs | 11.0.0 | |
+| 2014-06 | SP-64 | SP-140200 | 55 | | Update to list of specs | 11.1.0 | |
+
+| Change history | | | | | | | |
+|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------|---------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2016-03 | SA#71 | SP-160129 | 0057 | | F | Update to list of specs | 12.0.0 |
+| 2016-05 | | | | | | Deletion of blank table in clause 5 | 12.0.1 |
+| 2016-12 | SA#74 | SP-160972 | 0058 | 1 | F | Update to list of specs | 13.0.0 |
+| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 |
+| 2017-06 | SA#76 | SP-170458 | 0059 | | F | Replace list of specs with pointer to web page showing up to date list | 14.1.0 |
+| 2018-06 | SA#80 | | | | | Promotion to Release 15 without technical change | 15.0.0 |
+| 2018-06 | | | | | | Include v15.0.0 line accidentally omitted from change history | 15.0.1 |
+| 2020-07 | SA#88-e | | | | | Upgrade on freezing of Release 16. | 16.0.0 |
+| 2022-03 | SA#95-e | | | | | Upgrade on freezing of Release 17. | 17.0.0 |
+| 2024-03 | SA#103 | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
+| 2025-03 | SA#107 | SP-250241 | 0070 | 1 | A | Replacing list with 3GU specifications link | 18.1.0 |
\ No newline at end of file
diff --git a/marked/Rel-18/51_series/51026/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/51_series/51026/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82d6d00475be0c52ab1a566a54a9248fee6b1fc0
--- /dev/null
+++ b/marked/Rel-18/51_series/51026/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab548d9cd6e97e61dd3d06e76975e9d500c33099592fcf78c5c80e663e71aeed
+size 8137
diff --git a/marked/Rel-18/51_series/51026/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/51_series/51026/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b48dc45b7ff9add7a4dfa335943624ce583d6ac
--- /dev/null
+++ b/marked/Rel-18/51_series/51026/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee64c94b3dcede42072af847fc974b62adcecefbb9ccbb84a64797c451e0e021
+size 15049
diff --git a/marked/Rel-18/51_series/51026/raw.md b/marked/Rel-18/51_series/51026/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..23550f6c2d4a05df7f983ca930cdd986d22a7464
--- /dev/null
+++ b/marked/Rel-18/51_series/51026/raw.md
@@ -0,0 +1,588 @@
+
+
+# 3GPP TS 51.026 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station System (BSS) equipment specification; Part 4: Repeaters (Release 18)**
+
+
+
+---
+
+**GSM**<sup>®</sup>
+GLOBAL SYSTEM FOR
+MOBILE COMMUNICATIONS
+
+GSM logo
+
+
+
+**3GPP**<sup>™</sup>
+
+3GPP logo
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP<sup>™</sup>) and may be further elaborated for the purposes of 3GPP.
+
+The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
+This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
+Specifications and reports for implementation of the 3GPP<sup>™</sup> system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+GSM, radio, BSS
+
+## **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis
+Valbonne - FRANCE
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+| | |
+|---------------------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Abbreviations ..... | 7 |
+| 4 General..... | 7 |
+| 4.1 Radio frequency bands..... | 8 |
+| 4.2 Test environments ..... | 8 |
+| 4.2.1 Normal test environment ..... | 8 |
+| 4.2.2 Extreme test environment..... | 8 |
+| 4.2.3 Extreme temperature..... | 8 |
+| 4.3 Manufacturers declarations ..... | 9 |
+| 4.4 Methods of measurement ..... | 9 |
+| 5 Spurious emissions..... | 9 |
+| 5.1 Test purpose ..... | 9 |
+| 5.2 Test case..... | 9 |
+| 5.3 Conformance requirement..... | 10 |
+| 5.4 Reference requirement ..... | 11 |
+| 6 Intermodulation attenuation ..... | 11 |
+| 6.1 Test purpose ..... | 11 |
+| 6.2 Test case..... | 11 |
+| 6.3 Conformance requirement..... | 11 |
+| 6.4 Reference requirement ..... | 11 |
+| 7 Out of band gain..... | 12 |
+| 7.1 Test purpose ..... | 12 |
+| 7.2 Test case..... | 12 |
+| 7.3 Conformance requirement..... | 12 |
+| 7.4 Reference requirement ..... | 12 |
+| 8 Frequency error ..... | 12 |
+| 8.1 Test purpose ..... | 12 |
+| 8.2 Test case..... | 13 |
+| 8.3 Conformance requirement..... | 13 |
+| 8.4 Reference requirement ..... | 13 |
+| 9 Modulation accuracy at GMSK modulation ..... | 13 |
+| 9.1 Test purpose ..... | 13 |
+| 9.2 Test case..... | 13 |
+| 9.3 Conformance requirement..... | 14 |
+| 9.4 Reference requirement ..... | 14 |
+| 10 Modulation accuracy at 8-PSK, QPSK, 16-QAM, 32-QAM or AQPSK modulation ..... | 14 |
+| 10.1 Test purpose ..... | 14 |
+| 10.2 Test case..... | 14 |
+| 10.3 Conformance requirement..... | 15 |
+| 10.4 Reference requirement ..... | 15 |
+| <b>Annex A (informative): Testing of gain for part band repeaters .....</b> | <b>16</b> |
+| A.1 Rationale for this test ..... | 16 |
+| A.2 Gain outside pass band..... | 16 |
+| A.2.1 Test purpose ..... | 16 |
+| A.2.2 Test case..... | 16 |
+
+A.2.3 Conformance requirement..... 16
+**Annex B (informative): Change history..... 17**
+
+# --- 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
+
+The present document describes the Radio Frequency (RF) tests for GSM repeaters (frequency bands according to clause 4.1) which receive, amplify, and retransmit a received Mobile Station (MS) signal in the GSM MS transmit band and simultaneously receive, amplify and retransmit a received Base Transceiver Station (BTS) RF signal in the GSM BTS transmit band.
+
+The present document is applicable to repeaters meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to repeaters meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
+
+# 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] ETS 300 019-1-0: "Equipment Engineering (EE): Environmental conditions and environmental tests for telecommunications equipment Part 1-0; Classification of environmental conditions; Introduction".
+- [3] ETS 300 019-1-3: "Equipment Engineering (EE): Environmental conditions and environmental tests for telecommunications equipment Part 1-3; Classification of environmental conditions, Stationary use at weather-protected locations".
+- [4] ETS 300 019-1-4: "Equipment Engineering (EE): Environmental conditions and environmental tests for telecommunications equipment Part 1-4; Classification of environmental conditions, Stationary use at non-weather-protected locations".
+- [5] ITU-R Rec. SM.329: "Spurious emissions".
+- [6] void.
+- [7] IEC 60068-2: "Basic environmental testing procedures: Part 2 Tests".
+- [8] IEC 721: "Classification of environmental conditions".
+- [9] 3GPP TS 51.010-1: "Mobile Station (MS) conformity specification".
+- [10] 3GPP TS 51.021: "Base Station System (BSS) equipment specification; Radio aspects".
+- [11] ETSI ETR 027: "Methods of measurement for private mobile radio equipment".
+- [12] ETSI ETR 028: "Uncertainties in the measurement of mobile radio equipment characteristics".
+- [13] 3GPP TS 45.005: "Radio transmission and reception".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**broadband repeater:** repeater which is designed for operation on any combination of ARFCNs (up to a specified maximum number) within the operating band of the repeater.
+
+**channelized repeater:** repeater which is designed for operation on a specified subset of ARFCNs within the operating band of the repeater. The subset of ARFCNs may be determined during the manufacture of the repeater, or may be programmable.
+
+**GSM:** Unless otherwise specified, references to GSM include all radio frequency bands according to clause 4.1.
+
+**operating band:** the frequency range in which GSM operates.
+
+**pass band:** frequency range that the repeater operates in with operational configuration.
+
+NOTE 1: This frequency range can correspond to one or several consecutive nominal channels. If they are not consecutive each subset of channels shall be considered as an individual pass band.
+
+NOTE 2: A repeater can have one or several pass bands.
+
+**repeater:** bi-directional Radio Frequency (RF) amplifier which can amplify and transmit a received Mobile Station (MS) signal in the GSM MS transmit band, simultaneously it can amplify and transmit a received Base Transceiver Station (BTS) RF signal in the GSM BTS transmit band.
+
+**repeater system using frequency shift:** repeater system consisting of two different elements, a master unit close to the BTS and at least one remote unit close to the area to be covered.
+
+NOTE 3: The master unit amplifies the channels from the BTS and shifts them to different GSM channels. In the remote unit the shifted channels from the master unit will be transferred back to the original channels and amplified. This is valid for the downlink signals as well as for the uplink signals.
+
+**spurious emissions:** emissions at frequencies other than those of the carrier and sidebands associated with normal modulation and switching.
+
+**subchannel power imbalance ratio on downlink:** as defined in 3GPP TS 45.004 [21].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+| | |
+|----------|----------------------------------------------|
+| BTS | Base Transceiver Station |
+| MS | Mobile Station |
+| RF | Radio Frequency |
+| SCPIR_DL | Subchannel Power Imbalance Ratio on DownLink |
+
+Abbreviations used within the GSM specifications are given in 3GPP TR 21.905 [1].
+
+# 4 General
+
+A repeater can be designed to amplify the whole transmit RF band or just a part of the band. In the latter case the repeater can be either Broadband, with frequency band selective filtering, or channelized, with channel selective filtering.
+
+## 4.1 Radio frequency bands
+
+A repeater, as having a bi-directional amplifier capability, can amplify and transmit a received MS signal in the MS transmit band, simultaneously it can amplify and transmit a received BTS signal in the BTS transmit band. The relevant MS and BTS transmit bands for the present document are the MS and BTS transmit bands as defined in 3GPP TS 45.005 [13], clause 2. A repeater is designed to operate in one or several pass bands within the MS and BTS transmit bands as defined in 3GPP TS 45.005 [13], clause 2. In this document, such MS and BTS relevant bands are herein referred as the repeater operating bands, as defined in clause 3.1. Repeater operating band(s) and repeater pass band(s) are part of clause 4.3 Manufacturers declarations.
+
+**Table 1: void**
+
+NOTE: In some circumstances, for instance when an operator (or more than one operator who co-ordinate the use of repeaters), is not allocated a complete band, it may be necessary to restrict the frequency range of operations of repeaters. In these circumstances, the test of "Gain outside pass band" in annex A may be used to verify the performance of the repeater.
+
+## 4.2 Test environments
+
+For each test in the present document, the environmental conditions under which the repeater is to be tested are defined.
+
+### 4.2.1 Normal test environment
+
+When a normal test environment is specified for a test, the test should be performed under any combination of conditions between the minimum and maximum limits stated in table 2.
+
+**Table 2: Limits of conditions for Normal Test Environment**
+
+| Condition | Minimum | Maximum |
+|---------------------|------------------------------------------|---------|
+| Barometric pressure | 86 kPa | 106 kPa |
+| Temperature | 15°C | 30°C |
+| Relative Humidity | 20 % | 85 % |
+| Power supply | Nominal, as declared by the manufacturer | |
+| Vibration | Negligible | |
+
+The ranges of barometric pressure, temperature and humidity represent the maximum variation expected in the uncontrolled environment of a test laboratory. If it is not possible to maintain these parameters within the specified limits, the actual values shall be recorded in the test report.
+
+NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site.
+
+### 4.2.2 Extreme test environment
+
+The manufacturer shall declare one of the following:
+
+- the equipment class for the equipment under test, as defined in ETS 300 019-1-3 [3];
+- the equipment class for the equipment under test, as defined in ETS 300 019-1-4 [4];
+- for equipment that does not comply to an ETS 300 019-1 [2] class, the relevant classes from IEC 721 [8] documentation for temperature, humidity and vibration shall be declared.
+
+NOTE: Reduced functionality for conditions that fall out side of the standard operational conditions are not tested in the present document. These may be stated and tested separately.
+
+### 4.2.3 Extreme temperature
+
+When an extreme temperature test environment is specified for a test, the test shall be performed at the standard minimum and maximum operating temperatures defined by the manufacturer's declaration for the equipment under test.
+
+Minimum temperature:
+
+- the test shall be performed with the environmental test equipment and methods of inducing the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60068-2-1 [7]. The equipment shall be maintained at the stabilized condition for the duration of the test sequence.
+
+Maximum temperature:
+
+- the test shall be performed with the environmental test equipment and methods of inducing the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60068-2-2 [7]. The equipment shall be maintained at the stabilized condition for the duration of the test sequence.
+
+NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature.
+
+## 4.3 Manufacturers declarations
+
+The manufacturer shall declare:
+
+- a) the operating band or bands of the repeater;
+- b) for each operating band, the pass band or bands within the operating band;
+- c) the maximum rated output power per channel;
+- d) the number of channels supported by the repeater;
+- e) the supported modulation methods.
+
+## 4.4 Methods of measurement
+
+The general methods of measurement and measurement uncertainty shall be according to ETSI ETR 027 [11] and ETSI ETR 028 [12] except where they conflict with the present document.
+
+# --- 5 Spurious emissions
+
+## 5.1 Test purpose
+
+This test measures the conducted spurious emissions (see clause 3.1) at the antenna ports and the effective power of spurious emissions radiated by the cabinet and structure.
+
+## 5.2 Test case
+
+The repeater shall be set to maximum gain. All measurement steps, as described in this clause, apply to all antenna ports of the repeater.
+
+- a) Spurious emissions from the antenna port:
+ - one antenna port of the repeater shall be connected to a selective RF measurement device presenting to the repeater a load with an impedance of 50 ohms. An average power measurement of spurious emissions shall be performed for frequency offsets from the carrier frequency greater than 600 kHz under the following two conditions:
+ - i) without any RF input signal. The relevant input antenna port of the repeater shall be terminated with 50 ohms;
+ - ii) with an RF input signal. The relevant antenna input port of the repeater shall be connected to an RF signal generator. A continuous sinusoidal RF signal shall be input at a level which will result, when measured, in the maximum rated RF output power per channel, as declared by the manufacturer. The RF input signal
+
+shall be set to the centre frequency of the repeaters pass band. In the case of a channelized repeater, the RF input signal shall be set to the centre of the supported ARFCN closest to the centre of the range of ARFCNs supported by the repeater.
+
+### b) Radiated spurious emissions:
+
+- a test site fulfilling the requirements of ITU-R SM.329 [5] shall be used, except when it conflicts with the present document. The repeater shall be placed on a non-conducting support and shall be operated from a power source as recommended by the manufacturer via an RF filter, to prevent the power source or cable from influencing the result of the measurement;
+- the relevant output antenna port of the repeater shall be terminated with 50 ohms. The relevant antenna input port of the repeater shall be connected to a RF signal generator in such a way that the connection does not influence the result of the measurement. The RF input signal shall be set to the centre frequency of the repeaters pass band. A continuous sinusoidal RF signal shall be input at a level which will result, when measured, in the maximum rated output power per channel, as declared by the manufacturer.
+- an average RF power measurement shall be performed for frequency offsets from the carrier frequency greater than 600 kHz over the frequency range 30 MHz to 4 GHz. The repeater shall be rotated through 360° in the horizontal plane and the test antenna shall be raised or lowered until the maximum spurious signal level is detected. The effective radiated power of each spurious component shall be determined by a substitution measurement;
+- the measurements shall be repeated with orthogonal polarization of the test antenna;
+- the measurements shall be repeated with no RF input signal, in this case the relevant antenna input port of the repeater shall be terminated with 50 ohms.
+
+**Table 3: Measurement bandwidth for spurious emissions**
+
+| Band | Frequency offset<br>(offset from carrier) | Measurement bandwidth |
+|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|
+| In the relevant BTS transmit Band or MS transmit band | $\geq 100$ kHz | 3 kHz |
+| 100 kHz to 50 MHz | - | 10 kHz |
+| 50 MHz to 500 MHz outside the relevant transmit band | (offset from edge of the relevant transmit band)<br>$> 0$ MHz<br>$\geq 2$ MHz<br>$\geq 5$ MHz | 10 kHz<br>30 kHz<br>100 kHz |
+| Above 500 MHz outside the Relevant transmit band | (offset from edge of the relevant transmit band)<br>$> 0$ MHz<br>$\geq 2$ MHz<br>$\geq 5$ MHz<br>$\geq 10$ MHz<br>$\geq 20$ MHz<br>$\geq 30$ MHz | 10 kHz<br>30 kHz<br>100 kHz<br>300 kHz<br>1 MHz<br>3 MHz |
+
+Test environment: Normal
+
+## 5.3 Conformance requirement
+
+The measured power in test case clause 5.2.a) as well as the effective radiated power in test case clause 5.2.b) shall not exceed:
+
+- -36 dBm (250 nW) in the frequency band 9 kHz to 1 GHz;
+- -30 dBm (1 $\mu$ W) in the frequency band 1 GHz to 12,75 GHz.
+
+## 5.4 Reference requirement
+
+3GPP TS 45.005 [13], annex E.
+
+# --- 6 Intermodulation attenuation
+
+## 6.1 Test purpose
+
+To verify that the level of intermodulation products, generated in non-linear elements of the repeater, in the presence of two RF input signals, do not exceed the specified limits.
+
+## 6.2 Test case
+
+The repeater shall be set to maximum gain. Two continuous sinusoidal RF signals shall be fed to the input antenna port of the repeater using a combining device. The frequencies of both RF signals shall be within the repeater's pass band. The spacing between both RF signals shall be the minimum possible spacing applied in a network, i.e. 600 kHz.
+
+The level of both RF input signals shall be increased, until the maximum rated output power per channel, as declared by the manufacturer, is reached.
+
+In case of a repeater only supporting one channel, one RF input signal shall be set to the operating frequency and the other RF input signal at an offset of 400 kHz to either side successively. In this case the input signal at the repeater's operating frequency shall be increased, until the maximum rated output power per channel, as declared by the manufacturer, is reached. The second signal shall be set to the same input level.
+
+The level of the third order intermodulation products shall be measured by means of a selective measurement device presenting to the repeater a load with an impedance of 50 ohms.
+
+The test shall be repeated with both RF input signals increased by 10 dB each.
+
+NOTE: In this case, the automatic gain (level) control may reduce the gain to a value less than maximum gain in order to keep the maximum rated output power per channel, as declared by the manufacturer.
+
+An average power measurement shall be performed using a bandwidth of 3 kHz.
+
+The measurements shall apply to all antenna ports of the repeater.
+
+Test environment: Normal
+
+## 6.3 Conformance requirement
+
+The maximum level of intermodulation product shall be not greater than:
+
+- -36 dBm (250 nW) in the frequency band 9 kHz to 1 GHz;
+- -30 dBm (1 $\mu$ W) in the frequency band 1 GHz to 12,75 GHz.
+
+## 6.4 Reference requirement
+
+3GPP TS 45.005 [13], annex E.
+
+# 7 Out of band gain
+
+## 7.1 Test purpose
+
+To test the net gain of the repeater outside the relevant MS or BTS transmit band. This test shall also check the net gain at harmonic frequencies.
+
+## 7.2 Test case
+
+The repeater shall be set to maximum gain. In case of a channel selective repeater, two of the channel selective modules shall be set to the lowermost and the uppermost ARFCN within the repeater's pass band.
+
+A continuous sinusoidal RF signal shall be fed successively at frequency offsets Y from the edges of the relevant MS or BTS transmit frequency band into the relevant input port of the repeater. The frequency offsets Y shall have the following values:
+
+400 kHz, 600 kHz, 800 kHz, 1 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz.
+
+This shall be repeated with an RF input signal successively set to all harmonic frequencies of the repeaters pass band up to 12.75 GHz (i.e. multiples of the centre frequency of the repeaters pass band up to 12,75 GHz).
+
+The power level of the RF input signal shall be at least 5 dB below the power level which would produce, when applied within the pass band, maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range.
+
+The average output power in each case shall be measured and the net gain shall be recorded.
+
+The measurements shall apply to all antenna ports of the repeater.
+
+Test environment: Normal
+ Extreme temperature
+
+## 7.3 Conformance requirement
+
+The net gain in both directions through the repeater shall be less than:
+
+- 50 dB at 400 kHz offset and greater;
+- 40 dB at 600 kHz offset and greater;
+- 35 dB at 1 MHz offset and greater;
+- 25 dB at 5 MHz offset and greater;
+
+from the edges of the relevant MS or BTS transmit bands.
+
+## 7.4 Reference requirement
+
+3GPP TS 45.005 [13], annex E.
+
+# 8 Frequency error
+
+## 8.1 Test purpose
+
+This clause applies only to repeater systems using frequency shift and describes the test of the frequency error.
+
+## 8.2 Test case
+
+The repeater system shall be levelled according to the recommendations of the manufacturer. For the purpose of the frequency synchronisation of the repeater system it might be necessary to connect the system to a BTS or equivalent test equipment like a mobile tester. In all cases an accurate frequency synchronisation source has to be used to synchronise the measurement setup.
+
+The test of the repeater system shall be performed at the lowest and the highest ARFCN supported by the repeater system. For the measurement of the frequency error a continuous, sinusoidal and synchronised RF signal shall be fed successively at a frequency of the relevant MS or BTS transmit frequency band into the relevant input port of the repeater. The power level of the RF input signal shall be at least 5 dB below the power level which would produce, when applied within the pass band, maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range.
+
+The average output frequency shall be measured with a frequency counter.
+
+The frequency error of single elements within the repeater system such as master unit or remote unit may be measured as well.
+
+Test environment: Normal
+ Extreme temperature
+
+## 8.3 Conformance requirement
+
+The average frequency error of the repeater system shall not exceed 0,1 ppm. If tested, the average frequency error of a single repeater shall not exceed 0,05 ppm.
+
+## 8.4 Reference requirement
+
+3GPP TS 45.005 [13], annex E.
+
+# --- 9 Modulation accuracy at GMSK modulation
+
+## 9.1 Test purpose
+
+This clause applies only to repeater systems using frequency shift and describes the test of the phase error.
+
+## 9.2 Test case
+
+The repeater system shall be levelled according to the recommendations of the manufacturer. For the purpose of the frequency synchronisation of the repeater system it might be necessary to connect the system to a BTS or equivalent test equipment like a mobile tester. In all cases an accurate frequency synchronisation source has to be used to synchronise the measurement setup.
+
+For the measurement of the phase error a continuous and synchronised GMSK signal modulated with a pseudo random bit sequence shall be fed successively at one frequency of the relevant MS or BTS transmit frequency band into the relevant input port of the repeater. The power level of the RF input signal shall be at least 5 dB below the power level which would produce, when applied within the pass band, maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range.
+
+The phase trajectory shall be measured at the equivalent output of the repeater system and the calculation of the phase error shall be performed according to 3GPP TS 51.010-1 [9] or 3GPP TS 51.021 [10].
+
+The phase error of single elements within the repeater system such as master unit or remote unit may be measured as well.
+
+The GMSK signal source shall have a phase error below the following values:
+
+- 5 degrees rms;
+- 20 degrees peak.
+
+Test environment: Normal
+ Extreme temperature
+
+## 9.3 Conformance requirement
+
+The phase error of a complete repeater system shall not exceed:
+
+- 7 degrees rms;
+- 28 degrees peak.
+
+If tested, the phase error of a single repeater unit shall not exceed:
+
+- 6.1 degrees rms;
+- 24.5 degrees peak.
+
+## 9.4 Reference requirement
+
+3GPP TS 45.005 [13], annex E.
+
+# --- 10 Modulation accuracy at 8-PSK, QPSK, 16-QAM, 32-QAM or AQPSK modulation
+
+## 10.1 Test purpose
+
+This clause applies only to repeater systems supporting 8-PSK, QPSK, 16-QAM, 32-QAM or AQPSK modulation and describes the test of the modulation accuracy.
+
+## 10.2 Test case
+
+The repeater system shall be levelled according to the recommendations of the manufacturer. For the purpose of the frequency synchronisation of the repeater system it might be necessary to connect the system to a BTS or equivalent test equipment like a mobile tester. In all cases an accurate frequency synchronisation source has to be used to synchronise the measurement setup.
+
+For the measurement of the modulation accuracy a continuous and synchronised 8-PSK, QPSK, 16-QAM, 32-QAM or AQPSK signal modulated with a pseudo random bit sequence shall be fed successively at one frequency of the relevant MS or BTS transmit frequency band into the relevant input port of the repeater. For the AQPSK modulation the SCPIR\_DL is set at 0dB. The power level of the RF input signal shall be at least 5 dB below the power level which would produce, when applied within the pass band, maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range.
+
+The EVM shall be measured at the equivalent output of the repeater system and the calculation of the EVM shall be performed according to 3GPP TS 51.021 [10].
+
+Test environment: Normal
+ Extreme temperature
+
+## 10.3 Conformance requirement
+
+For a repeater as defined in the first column of the table below the RMS EVM shall not exceed:
+
+| | | Normal symbol rate | | | | Higher symbol rate | | |
+|-----------------------------------------------------------------------|--------------------------|----------------------|-------|--------|--------|--------------------|--------|--------|
+| | | AQPSK <sup>(1)</sup> | 8-PSK | 16-QAM | 32-QAM | QPSK | 16-QAM | 32-QAM |
+| For a single repeater with no shift in frequency from input to output | under normal conditions | 4,0% | 8,0 % | 4,0 % | 4,0 % | 8,0 % | 4,0 % | 4,0 % |
+| For a single repeater with no shift in frequency from input to output | under extreme conditions | 5,0% | 8,0 % | 5,0 % | 5,0 % | 8,0 % | 5,0 % | 5,0 % |
+| For a complete repeater system using frequency shift | under normal conditions | 6,0% | 11 % | 6,0 % | 6,0 % | 11 % | 6,0 % | 6,0 % |
+| For a complete repeater system using frequency shift | under extreme conditions | 7,0% | 11 % | 7,0 % | 7,0 % | 11 % | 7,0 % | 7,0 % |
+| NOTE 1: Only for downlink | | | | | | | | |
+
+## 10.4 Reference requirement
+
+3GPP TS 45.005 [13], annex E.
+
+# --- Annex A (informative): Testing of gain for part band repeaters
+
+## A.1 Rationale for this test
+
+The normative provisions of the present document specify the out-of band gain relative to the edge of one of the GSM bands specified in clause 4.1. The purpose of this informative annex is to define a test method which may be used to measure the out-of-band gain for a repeater which is designed to operate only over part of one of these bands. This test may be used for acceptance testing or for regulatory purposes.
+
+Since 3GPP TS 45.005 [13] does not specify the out-of-band gain requirements within a GSM band for such a repeater, the performance requirements for the repeater must be agreed prior to this test being performed. Normally, the requirements for the uplink and downlink directions will be similar, but with the frequencies offset by 45 MHz or 95 MHz.
+
+## --- A.2 Gain outside pass band
+
+### A.2.1 Test purpose
+
+To determine the net gain of the repeater outside its specified pass band (or bands), when this is less than a GSM band defined in clause 4.1 of the present document. The requirements of clause 7 of the present document shall always be met, whether or not this test is also performed.
+
+This test is not a normative requirement of the present document.
+
+### A.2.2 Test case
+
+The repeater shall be set to maximum gain. In case of a channel selective repeater, two of the channel selective modules shall be set to the lowermost and the uppermost ARFCN within the repeaters pass band.
+
+A continuous sinusoidal RF signal shall be fed successively at each specified frequency into the relevant input port of the repeater. The power level of the RF input signal shall be at least 5 dB below the power level which would produce, when applied within the specified pass band, maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range.
+
+The average output power in each case shall be measured and the net gain shall be recorded.
+
+The measurements shall apply to all antenna ports of the repeater.
+
+Test environment: Normal
+ Extreme temperature
+
+### A.2.3 Conformance requirement
+
+At each frequency specified to be measured, the gain through the repeater shall be less than the specified value.
+
+# Annex B (informative): Change history
+
+This annex lists all change requests approved for the present document since the first phase 2 version was approved by ETSI SMG.
+
+| SMG# | SMG tdoc | SMG8 tdoc | VERS | CR | RV | PH | CAT | SUBJECT | Resulting Version |
+|------|----------|-----------|-------|------|----|-----|-----|---------------------------------------------------------------------|-------------------|
+| S17 | 095/96 | | 4.0.0 | 001 | | 2 | B | Editorial additions and changes to comply with ETSI style | 4.1.0 |
+| | 095/96 | | 4.0.0 | 002 | | 2 | D | Addition of definition of normal and extreme conditions for testing | 4.1.0 |
+| | 095/96 | | 4.0.0 | 003 | | 2 | | Definition of test method for part band repeaters | 4.1.0 |
+| S18 | 257/96 | | 4.1.0 | A004 | | 2 | F | Intermodulation attenuation | 4.2.0 |
+| S20 | 606/96 | 58/96 | 4.2.0 | A005 | | 2 | D | Correction of reference title | 4.2.1 |
+| s23 | 783/97 | 031/97 | 4.2.2 | A006 | | R96 | B | Addition of references to the R-GSM band | 5.0.0 |
+| s25 | 98-0168 | 98p007 | 5.0.1 | A007 | | R96 | F | Minimum offset for spurious emissions measurements | 5.1.0 |
+| s26 | 98-395 | 98p051 | 5.1.0 | A008 | | R96 | B | Repeater systems using frequency shift | 5.2.0 |
+| s26 | 98-395 | 98p056 | 5.1.0 | A009 | | R96 | D | Addition of reference to ETR 027 and ETR 028 | 5.2.0 |
+| | | | 5.2.0 | | | | | Version update for publication | 5.2.1 |
+| s31b | P-00-190 | 866/00 | 5.2.1 | A011 | 2 | R99 | B | Repeater EDGE & GSM 400 test cases | 8.0.0 |
+| | | | 8.0.1 | | | | | Update to Version 8.0.2 for Publication | 8.0.2 |
+
+| Change history | | | | | | | | | | |
+|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------|--|--|--|--------|--------|
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | | | Old | New |
+| 2002-01 | | | | | New version for Release 4 | | | | 8.0.2 | 4.0.0 |
+| 2002-06 | | | | | New version for Release 5 | | | | 4.0.0 | 5.0.0 |
+| 2005-01 | | | | | New version for Release 6 | | | | 5.0.0 | 6.0.0 |
+| 2005-06 | 25 | GP-051706 | 003 | 1 | Addition of new frequency band (e.g. T-GSM810) to the repeater test specification | | | | 6.0.0 | 6.1.0 |
+| 2007-07 | 35 | | | | Version for Release 7 | | | | 6.1.0 | 7.0.0 |
+| 2008-12 | 40 | | | | Version for Release 8 | | | | 7.0.0 | 8.0.0 |
+| 2009-05 | 42 | GP-090970 | 0006 | 1 | Introduction of EVM requirement for EGPRS2 for Repeater | | | | 8.0.0 | 8.1.0 |
+| 2009-05 | 42 | GP-091038 | 0007 | 1 | Update of reference documents from ETS GSM to 3GPP | | | | 8.0.0 | 8.1.0 |
+| 2009-09 | 43 | GP-091133 | 0010 | | Introduction of EVM requirement for EGPRS2 for Repeater | | | | 8.1.0 | 8.2.0 |
+| 2009-12 | 44 | | | | Version for Release 9 | | | | 8.2.0 | 9.0.0 |
+| 2010-03 | 45 | GP-100093 | 0016 | | EGPRS2 EVM requirements for repeater | | | | 9.0.0 | 9.1.0 |
+| 2011-03 | 49 | | | | Version for Release 10 | | | | 9.1.0 | 10.0.0 |
+| 2011-09 | 51 | GP-111375 | 0018 | 1 | EVM for AQPSK for Repeater | | | | 10.0.0 | 10.1.0 |
+| 2011-11 | 52 | GP-111775 | 0020 | 1 | On EVM requirements and SCPIR_DL in the case of AQPSK Modulation | | | | 10.1.0 | 10.2.0 |
+| 2012-03 | 53 | GP-120114 | 0022 | | Brackets removal from the SCPIR_DL value for AQPSK modulation accuracy test | | | | 10.2.0 | 10.3.0 |
+| 2012-03 | 53 | GP-120406 | 0024 | 1 | Update of Definition clause with repeater's pass band definition | | | | 10.2.0 | 10.3.0 |
+| 2012-09 | 55 | | | | Version for Release 11 | | | | 10.3.0 | 11.0.0 |
+| 2014-09 | 63 | | | | Version for Release 12 (frozen at SP-65) | | | | 11.0.0 | 12.0.0 |
+| 2015-12 | 68 | | | | Version for Release 13 (frozen at SP-70) | | | | 12.0.0 | 13.0.0 |
+
+| Change history | | | | | | | |
+|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------|
+| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
+| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 |
+| 2018-06 | RP-80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 |
+| 2022-03 | RP-95e | - | - | - | - | Upgrade to Rel-17 version without technical change | 17.0.0 |
+| 2024-03 | RP-103 | - | - | - | - | Upgrade to Rel-18 version without technical change | 18.0.0 |
\ No newline at end of file